I would'nt complain about the documentation. "Migration is only implemented for a single Storage daemon. You cannot read on one Storage daemon and write on another."
Is a direct quote from the docs. See link below. On Tue, 2009-06-16 at 22:54 -0400, Phil Stracchino wrote: > Dirk Bartley wrote: > > On Tue, 2009-06-16 at 17:37 -0400, Phil Stracchino wrote: > >> I'm trying to set up my first Copy job, and running into a problem. I > >> don't know whether it's a configuration issue, a documentation > >> shortfall, a Bacula limitation, or a combination of the three. > >> > >> > >> I have two SDs on two different machines. > > > > Unfortunately. > > > > http://www.bacula.org/manuals/en/concepts/concepts/Migration_Copy.html > > > > Migration (also copy because a copy is just a special case of migration) > > is only implemented for a single Storage daemon. You cannot read on one > > Storage daemon and write on another. > > > > As a new feature, there are limitations. > > I suspected that might be the case, but the documentation isn't clear > about it and it certainly APPEARS to accept the settings. It just > doesn't act on them correctly. > > If it's limited to acting within a single SD, that will drastically > reduce its usefulness. > > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
