Today I’ve upgraded our vCenter Server from 5.5 to 6.0. Our BackupAdmin has upgraded the Backup Server one week before and all worked fine.
The upgrade on my nested vSphere test environment works fine too. The backup and restore tests runs over the vCenter 6 with all the ESXi 5.5 and 6 servers. *damn*
Now in our production environment the upgrade runs an all services works. After starting the test backup for one virtual machine i get the following error:
123456 Job ended: Wednesday, 17 Jun 2015 at 9:03:05 PMCompleted status: FailedFinal error: 0x200095bf - A failure occured while locking the virtual machine in place for backup/restore operations.Final error category: Resource ErrorsFor additional information regarding this error refer to link <a href="http://entced.symantec.com/entt?product=BE&version=14.2.1180&module=eng-no_fs-backup&error=V-79-8192-38335&language=EN&build=Retail&os=Windows_V-6.2.9200_SP-0.0_PL-0x2_SU-0x110_PT-0x3" target="_blank">V-79-8192-38335</a>
I don’t know which combination causing this error. Backup Exec tried to make a snapshot, but at vCenter comes no response, no task in the activity section, nothing.
An upgrade of an ESXi host didn’t solve the problem.
After rollback the upgrade of vCenter to 5.5 and restore of all databases everthing works again.
Symantec had acknowledged this failure https://support.symantec.com/en_US/article.TECH230127.html but don’t have a solution. The workaround is to use the backup exec agent to backup the machine.
At the moment i think the combination of vCenter Server 6.0 and Backup Exec 2015 is not ready for production environments.