In this post I am going to shed some light on a very common error in Backup Exec 2010, 2012 and 2014 when performing VM backups from a VMware Hypervisor. The error experienced is:
V-79-57344-38260 - Unable to create a snapshot of the virtual machine. The virtual machine no longer exists or may be too busy to quiesce to take the snapshot.
This error is extremely generic and can be one of 10 possible problems. For a list of all possible problems see the following knowledge base article from Symantec:
http://www.symantec.com/business/support/index?page=content&id=TECH146397
The most common cause which is not documented heavily on the Internet is the lack of the Storage APIs. The Storage APIs are only available in VMware vSphere Standard Edition and higher. If your using the free version of ESXi, you will not have the Storage API and hence your backups will not work. Check the licensing page on your ESX host to see if you have the Storage API in your license key:
If you don't have it, upgrade your license key and success will be yours :).
V-79-57344-38260 - Unable to create a snapshot of the virtual machine. The virtual machine no longer exists or may be too busy to quiesce to take the snapshot.
This error is extremely generic and can be one of 10 possible problems. For a list of all possible problems see the following knowledge base article from Symantec:
http://www.symantec.com/business/support/index?page=content&id=TECH146397
The most common cause which is not documented heavily on the Internet is the lack of the Storage APIs. The Storage APIs are only available in VMware vSphere Standard Edition and higher. If your using the free version of ESXi, you will not have the Storage API and hence your backups will not work. Check the licensing page on your ESX host to see if you have the Storage API in your license key:
It is really amazing! So many new things that I even didn't hear about them. Difficult to follow for a not professional, a private individual. The world goes on progressing by innovating and inventing.
ReplyDeleteI just wanted to say thanks for this information. I spent most of a day troubleshooting what I thought were domain issues and digging around Symantec's site with no luck. - IT Guy from Baltimore, MD
ReplyDeleteThank You, very useful info!
ReplyDeleteThank you ! it solved my problem
ReplyDeleteMuito obrigado resolveu o problema e no próprio site da veritas não tem o caso!!!!!
ReplyDelete