On Fri, Mar 26, 2010 at 3:05 PM, Dan Langille <d...@langille.org> wrote: > A bit of confusion regarding job migration today on IRC: > > >From : http://www.bacula.org/5.0.x-manuals/en/main/main/Migration_Copy.html > > "The term Migration, as used in the context of Bacula, means moving data > from one Volume to another" > > Strictly speaking, the data is always copied as far as I can tell. The > source Volume remains unchanged. Catalog data is moved around (for a > Migration; not a Copy). > > I think that first sentence is misleading some people who are expecting > their source Volumes to be reduced in size. > > Agreed? > Originally I did not have a problem with the first sentence because I know bacula does not reduce the size of a volume except in the special case where a disk volume is purged. But I can see how some users will be confused.
> > Another question: > Not sure about that. I have never done a Migration or Copy yet. John ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
