- Upgrade backup exec 16 to 20 upgrade#
- Upgrade backup exec 16 to 20 full#
- Upgrade backup exec 16 to 20 software#
Also switch from SAN mode to NBD something resolve the issue. But you have to plan other solution for the application backup level. The big issue is not the broken task itself, but the locking in the VM properties: you can have a stale snapshot (or need to consolidate) and also if you fix the snapshot, you probably cannot move the VM with Storage vMotion until a successful backup (see this previous post).įor this issue there isn’t a simple solution… In most cases disabling the GRT on the affected VM could work. It’s quite nice and useful, but sometimes does not work with vSphere 5.1 and you can have broken tasks: One interesting function is the integration with the vCenter Server recent tasks, where you can see the backup task progress. Remain a pity that only the VM & Template view it’s available (in some cases could be interesting also choose from other inventories).Īnother big issue (described in several post, like this one) is the one related with this error: A general system error occurred: solution is not responding. The best way is deselect the root node and create an inclusion list, by only select the desired folders. The issue is well described in the TECH186742, not related to a virtual environment, but that explain the concept: if you deselect a single folder (red sign) you are doing an exclusion and does not work (or could not work) if you are excluding some empty folder. If you deselect some folder in the selection list you can get this error: “0xe000942a – Backup Exec did not find any resources to include in the backup – v-79-57344-37930”. The missing support does not mean that does not work, but it’s quite boring because you have a lot of minor issues, some not easy to understand.įirst issue is in the selection (but I think that it’s a general issue not related with the vSphere version).
Upgrade backup exec 16 to 20 full#
The full support will be available with the 2012 R2 release and/or with the 2012 SP2 (seems confirmed according with this post, but no official date has been announced yet).
Upgrade backup exec 16 to 20 software#
The current version of Symantec Backup Exec is still not supported with VMware vSphere 5.1, according with the Software Compatibility List (SCL). The workaround is to use the backup exec agent to backup the machine.Īt the moment i think the combination of vCenter Server 6.0 and Backup Exec 2015 is not ready for production environments.This post is also available in: Italian Reading Time: 4 minutes Symantec had acknowledged this failure but don’t have a solution.
Upgrade backup exec 16 to 20 upgrade#
Backup Exec tried to make a snapshot, but at vCenter comes no response, no task in the activity section, nothing.Īn upgrade of an ESXi host didn’t solve the problem.Īfter rollback the upgrade of vCenter to 5.5 and restore of all databases everthing works again. I don’t know which combination causing this error. I also could reproduce it in my environment and the error is away. With Backup Exec 15 revision 1180 Feature Pack 1 the problem could be solved. After starting the test backup for one virtual machine i get the following error: Job ended: Wednesday, at 9:03:05 PMįinal error: 0x200095bf - A failure occured while locking the virtual machine in place for backup/restore operations.įor additional information regarding this error refer to link V-79-8192-38335 Now in our production environment the upgrade runs an all services works. The backup and restore tests runs over the vCenter 6 with all the ESXi 5.5 and 6 servers. The upgrade on my nested vSphere test environment works fine too. Our BackupAdmin has upgraded the Backup Server one week before and all worked fine. Today I’ve upgraded our vCenter Server from 5.5 to 6.0.
0 kommentar(er)
