Acronis backup for vmware virtual appliance reboots

#ACRONIS BACKUP FOR VMWARE VIRTUAL APPLIANCE REBOOTS DRIVER#

Message: Awaiting task 'CreateSnapshot' has failed. Message: VMware error: 'An internal error.'. Message: Failed to open the virtual machine ( vcenter/vcenter.vmx). Message: Failed to perform the requested operation. Message: SOAP 1.1 fault: SOAP-ENV:ClientР”Вetail: get host by name failed in tcp_connect() Message: Failed to obtain server object 'parent' (resgroup-9). Message: Failed to get the object's property 'ResourcePoolID'. Message: Failed to serialize object 'ResourcePool'. I just checked my vmProtect 7 console and I also had a backup job for 2 other servers fail with these cryptic errors:

#ACRONIS BACKUP FOR VMWARE VIRTUAL APPLIANCE REBOOTS DRIVER#

They keep placing the blame on VMWare or VMWare tools, but you know what, I updated those tools numerous times, and its a Windows 2008 server so it's not using the legacy SYNC driver like 2000 server would. It sporadically refuses to quiese a snapshot. I hate to have to use Symantec BackupExec on it when I SHOULD be able to do it natively in VMWare. The biggest issue is our one server (583.69 GB used storage) will not consistently back up. I'm also running a small handful of machines on version 8 beta, and that has not had the same problem either. I had to setup my 30+ backup jobs by hand one by one and made all new archives. What solved that issue :knock on wood: was an updated build from version 7 and I deployed it as a new appliance (instead of an upgrade). I read some horror stories where people completely ran out of storage due to that problem and all their VM's halted.

but luckily we caught it before our storage filled up. Usually V2V is required to make a whole new machine using VMWare Converter.

Anymore than that, its VERY tricky and time consuming to do a consolidation. VMWare only supports a maximum of 32 snapshots. We had to do a V2V conversion on some machines because we ended up with more than 32+ snapshots on some machines. It has a lot of potential, but it's quite not ready yet.Р”Р„ big problem we had with Acronis is that it would not correctly remove the snapshot disk from itself, so VMWare could not consolidate the snapshot after the job was finished. as I continue to send info to Acronis, I hope that they can resolve the issues with this product. However because it is not 100% consistent with good backups, we are going to budget for Veeam next year and see if the money is approved for it. If everything would back up consistently 100%, it would be an outstanding product due to its simplicity and price point. I keep hammering away at it and participate in the beta's because really the product is priced right and is simple to use. Message: VMware error: 'Remote method call failed.'. Solarwinds virtual appliance is impossible to backup on any version (6, 7, 8 beta). It's more common it does not back up though.Р”Р€. Some nights it backs up, some nights it doesn't. We have an ongoing ticket open since May 2012 for this machine in vmProtect 7. To back up the machine, power off the machine before the process or uninstall the Volume Shadow Copy Services Support feature of VMware Tools from the VM. Random backup failures on a virtual server due to VMware failed to create a quiesced snapshot of the selected virtual machine. Random MFT corrupt warnings on a machine (but yet machine works fine, backup even restores fine). I only have 3 machines that have 'issues' with vmProtect8.Р”РЋ. vmProtect7 got a little better, then there was an updated build for vmProtect7, and now I'm beta testing vmProtect8. I think we only had a 10% sucess rate with our backup jobs. Yeah its pretty buggy but it has gotten better.

Acronis backup for vmware virtual appliance reboots