[Bacula-users] Job migration - documentation nit

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?

Another question:

After the job migration has been run, is the expected status of the
destination Volume = 'Append'?  All other things being equal (such as max
size etc, use once, etc).

-- 
Dan Langille -- http://langille.org/


------------------------------------------------------------------------------
Download Intel&#174; 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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users