Restore of a VMWare Virtual Machine with two or more disks on different datastores fails if the backup set is not backed up through vCenter Unable to restore and RAWS stops unexpectedly when Japanese character is included in virtual machine name No Virtual Machines are showing under VirtualCenter in Backup Selection Unable to mount the virtual disk when backup is done through the vCenter that the name of Data Center is configured with Japanese character Beremote.exe process can crash when restoring a VMware virtual machine from a differentia/incremental backup set Symantec released a hotfix that will fix a couple of problems with vm backup. I will post back if/when I hear anything. I think that would also enable me to use the SAN transport when doing vmware agent backups. I don't mean to jump the gun but I am working with a new vSphere setup 's not too late for me to switch from NFS back to iSCSI/vmfs. I am going to get back in touch with Symantec and try to get them to reproduce it in the lab. The backup data size was 12GB and went very quickly.
#Backup exec 16 recover from expired data set full
Job #2 - Full backup with vmware agent, granular for files/folders only, ESX/Vcenter 4.0u1 VMFS datastore, 100GB thin-provisioned disk, 12GB used. The backup data size was 100GB and the backup took a long time, but the IMG file that was created was only 10GB. Job #1 - Full backup with vmware agent, granular for files/folders only, ESX/Vcenter 4.1 NFS datastore, 100GB allocated, 10GB used. They don't seem to know their products very well, and don't even know about existing issues which they have published articles for. That's honestly all they ever do whenever I call with a problem, they just tell me that is working as designed, even when it's clearly not. Symantec tried to convince me it was normal. VMWare told me they knew nothing about Symantec's VADP implementation so I needed to talk to them. I was on the phone today with both VMWare and Symantec. I am working on two theories - 1) that this is a problem only affecting NFS datastores and not VMFS thin-provisioned disks or 2) it is a problem with 4.1 only.
0 kommentar(er)
