01-22-2012 01:58 PM
Hi,
We recently P2Ved one of our fileservers, prior to which we were able to backup with a job rate of 2GB+/min and a total backup runtime of around 15 hours.
Since P2Ving the server, we now only get a job rate of around 900MB/min and the total runtime is now around 32 hours.
Does anybody know why the job rate would have drop so significantly?
Environment Details:
We have gigabit ethernet between the VM host and iSCSI SAN (Dell Powervault MD3200i) and we backup to tape (a Dell PowerVault TL2000)
The VM is a Hyper-V VM running on a Hyper-V cluster but we are not using the Hyper-V agent for backing up, just the standard RAWS agent, OS is W2K8 R2 Standard
The server BE is installed on is physical with the tape library connect via SAS, BE version is 2010 R3 SP1, OS is W2K8 R2 Enterprise
Cheers
Adam.
Solved! Go to Solution.
01-29-2012 04:45 PM
When you go from physical resources, to virtual resources, more likely you lost "horsepower."
Either grant it more resources to do the backup, or backup the VHD file itself. Backing up the VDH is almost faster than a normal file level backup. The Hyper-V agent being preferred!
01-23-2012 03:24 PM
Was the file server a media server when it was physical?
01-29-2012 02:46 AM
As part of testing for a case I had open with Symantec, it was at one point a media server.
Cheers
Adam.
01-29-2012 04:45 PM
When you go from physical resources, to virtual resources, more likely you lost "horsepower."
Either grant it more resources to do the backup, or backup the VHD file itself. Backing up the VDH is almost faster than a normal file level backup. The Hyper-V agent being preferred!
01-30-2012 03:49 PM
So before it was virtualised it was being backed up by another media server, it did not backup itself to tape?
Is the iSCSI traffic between the file server nad the SAN separate from the normal network? or is it on the same network?