11-13-2015 07:05 AM
HI,
We are backing up different Linux VMs. Almost all linux backups are finishing successfully. Just two FreeeBSD appliances are reporting:
A quiesced snapshot could not be created for the virtual machine machinename
Completed status: Failed
Final error: 0xe00095a7 - The operation failed because the vCenter or ESX server reported that the virtual machine's configuration is invalid.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-38311
Is there a possibility to tell backup exec not to try a quiesced snapshot? Any other ideas?
Thanks for any help.
Solved! Go to Solution.
12-08-2015 06:40 AM
Disabling the "vmt" kernel tools on the FreeBSD vm does solve the problem...
here the FreeBSD documentation:
11-13-2015 12:29 PM
FreeBSD doesn't show on the list of supported Linux distributions, and I suspect this is why you're getting this issue. You can try backing them up on a file level, but no guarantee it will work...
https://www.veritas.com/support/en_US/article.TECH227896
Thans!
11-13-2015 04:55 PM
A snapshot is needed so that the VM is consistent when it is backed up so there is no way to avoid that.
11-14-2015 09:15 AM
You should start by ruling out if this is a vmware issue. Try to take a manual snapshot of this vm and see if any errors show up in vcenter. Then delete the snap. Then make sure you have the latest vmware tools installed in that guest. Reboot that guest.
On your BE jobs for those freebsd clients, make sure grt is disabled, since its not a supported client OS
11-16-2015 04:52 AM
Yes the vCenter is able to take a quiesced snapshot of the VM. So it is an issue of bakcup exec.
Is there a possibility to tell backup exec to ignore that error, that the backup shows successfull? Because the snapshot works!
11-16-2015 04:58 AM
...I still suspect it is down to that OS not being supported by Backup Exec. Log a call with support and see what they say.
Thanks!
12-08-2015 06:40 AM
Disabling the "vmt" kernel tools on the FreeBSD vm does solve the problem...
here the FreeBSD documentation: