Currently using Backup Exec 2010 R3 Build 5204 64 bit
Running on a Windows Server 2008 R2 SP1 box, dedicated (not on any of my Hyper-V hosts)
Backup is "across the wire" (yes, slow)
I have a 3 node Hyper-V cluster and am trying to determine the best way to accomplish this:
I run strictly tape...way too much disk required to to B2D.
My tape library is a 4 drive LTO5 changer. Previously I have just divided up all my targets (both physical and virtual) into 7 or 8 different jobs and just did a normal agent level backup. This has worked well but I know I need to get into the Hyper-V agent backups to easily facilitate disaster recovery.
I have never paid much attention to what targets were running at the same time since I've had 4 parallel data streams going at the same time and the agent didn't care. Now however, due to the "Online (Backup in progress, Redirected access" issue/limitation it would appear that I am going to have to change tracks.
I could set up a single job for each of my 3 hosts, which is *supposed* to automatically catch whatever Hyper-V guests happen to be running on it at the time...but guests are liable to be migrated around and at any point in time the backup of 1 host would "cross" the boundary into another host's CSV area... which from what I gether will cause those jobs to fail.
What is everybody doing to accomodate this issue of parallel backups to multiple Hyper-V hosts?
