but I'll keep that for another forum and another day.
I have many things I want to say now, a tirade about releasing incomplete products, another tirade about promoting heavily features that don't work, a smaller tirade about the IT industry and its current risk of becoming the used car salesmen of the 21st century. Now I haven’t tested what issues that may create for backup and restore jobs, if for example I don’t want to back up or restore an entire host, but I'm guessing if you motion anything and don’t put it back where it's "supposed" to be you're going to have issues. not technically a work around.Ģ) Back up directly to each of your ESX hosts. We should all talk to a Symantec salesperson if we want to get it fixed. Symantec are aware of the issue but have no concrete plans to fix it. It will work if you backup directly from an ESX host
#BACKUP EXEC 2010 LIVE UPDATE FULL#
If you read the support document carefully you will see that Ī restore of the full vm is possible. This is the support document that describes the problem.
When I say doesn't work, it backs up, but it will not restore individual files. Symantec GRT in Backup Exec in 2010 does not work with vSphere.
#BACKUP EXEC 2010 LIVE UPDATE UPGRADE#
We upgraded to vSphere a little over 2 weeks ago, and the upgrade went very well, except in one area. so forgive me if seem a little tired and cross.
0 kommentar(er)
