07-11-2017 04:28 AM
Hi All, before raising a case with Veritas just wanted to get straight in my mind how backup exec works.
So the background. We have two identical Windows 2012r2 servers running off the same vmware 6.1 host using the same shared storage. I wanted to test backups before the servers went into production so I created two identical VMware based backups (no GRT). One of the servers backups at a decent rate, the other is half the speed. Bearing in mind these servers are on the same vmware host and the same storage (neither of which are under any load at all) and running identical backup exec jobs why would that be?
I have no idea where to even start looking.
Cheers,
Ed.
07-11-2017 06:01 PM
Did you include both the VM's in same job or different jobs? What is the transport mode used (SAN, NBD, etc.) ?
I would suggest making buffer adjustments as mentioned in following article to get the best speed :
http://www.veritas.com/docs/000085311
Thanks and Regards,
Riyaj
07-12-2017 01:06 AM
Thanks for your reply Riyaj.
The jobs have been set up as two seperate jobs, but they are identical except for the virtual server that is backed up.
Transport mode for both jobs is NBD
I don't see much point in chaning the buffer settings when one of the jobs is running as fast as the network can but the other is running at less that half the speed. (only one job runs at a time).
07-12-2017 02:22 AM
Okay, monitoring performance on both ESX and Backup Exec server would help in identifying the bottleneck resource:
Backup Server: https://technet.microsoft.com/en-us/library/cc749249(v=ws.11).aspx
Collecting performance data while running each job and comparing would help.
Thanks and Regards,
Riyaj