06-05-2012 12:41 PM
Dear all,
We have installed BE 2012 to backup a VMed (VMware vSphere 5.1) Exchange 2010 SP1 (both are 64bit W2K8 R2 SP1) at a customer datacenter. Currently, we can backup that server using RAWS (and not AVVI) although at a really slow rate (about 80MB/min, I would like to discuss this issue in another thread) to a DAS Array (3 SATA disks).
We have tried backing it up using AVVI but it always throws this exception:
Solved! Go to Solution.
06-05-2012 12:57 PM
Did you remove the Vmware VSS provider:
http://www.symantec.com/business/support/index?page=content&id=TECH129864
And install the Symantec Backup Exec VSS provider ?
06-05-2012 12:57 PM
Did you remove the Vmware VSS provider:
http://www.symantec.com/business/support/index?page=content&id=TECH129864
And install the Symantec Backup Exec VSS provider ?
06-05-2012 01:01 PM
Hmmm...I'll take a look right now.
Will keep you posted.
06-05-2012 01:02 PM
06-05-2012 01:09 PM
Check to see how long a snapshot request takes if you just make the request via the vSphere Client - as it might be taking too long and Backup Exec then timing out. Remove the test snaphot when you have done this.
Also remove any existing snapshots from the VM in question as this can speed up the snapshot and backup processes
06-05-2012 01:28 PM
Snapshots using AVVI are fast (4.8GB/min). I have the performance problem using RAWS (it drops to 88.00MB/min).
It seems performance issues are not only on BE2012 as there are reportes on BE2010 as well. Still don't have the answer for it either.
06-05-2012 01:49 PM
I was refering to how long it takes to make the snapshot when I referred to how fast it was and timeouts - was not referring to transfer speed.
06-05-2012 02:13 PM
Oww...it is fast...no timeouts are displayed. The requested time is the same as the start time.
06-05-2012 02:35 PM
Ok so if it is the fast doing a manual snapshot then BE won't be timing out when it makes a request to VMware to take a snapshot which means it is not likely to be that causing the original problem.
06-05-2012 09:21 PM
As I couldn't get my hands on the Exchange VM, I tested it with and SQL VM (which gave me the same result).
I did the following, according to ZeroC00l:
Still got the same exception, however, this time, in the event viewer, there was a logon error to SQL server using the DOMAIN\administrator credentials followed by a BeVSSprov error.
It happened that the Agent service account didn't have privileges over the SQL server. Once I set those privileges, the backup job finished flawlessly.
However, that means BE 2012 vCenter account is not used (we are using DOMAIN\unique for that, not administrator). Instead, it uses RAWS' service account. I set up privileges for DOMAIN\unique on the SQL server but no joy. I had to use RAWS'. Is that correct?
06-09-2012 04:28 PM
After doing that, everything's is fine now. Jobs are without errors.
Thanks for your help!