I have this problem, and it's not a happy one. I have one client that is
so huge that migration takes all day and all night, with one process and
one tape drive. It is already getting very dicey to schedule things such
that migration does not happen during client backup, but that involves
some
On Sun, 23 Apr 2006 13:52:50 -0500, Roger Deschner [EMAIL PROTECTED] said:
The only solution is policy. (Quick! Grab the Aspirin!) Put it in
its own copygroup etc, or even its own server image, and then turn
off collocation completely for it, so that it can migrate on more
than one drive at
I'm a little confused as to how data is migrated to tape with collocation
groups configured. Let's say I have 2 collocation groups in a single domain
each with 10 computers, and I have configured the disk pool to migrate using
8 processes, how many processes should I see migrating data?
What I
