W2KSP4 Virtual Machine Backup Failures
Hey all,
After reinstalling ABR 11.5 Virtual Edition, I am trying to perform a simple, full backup of a collection of Windows 2000 Server Service Pack 4 virtual machines to a Centralized Unmanaged Vault. The VMs are running on a Windows Server 2008 R2 Datacenter Edition Failover Cluster and the VMs reside on a Cluster Shared Volume, C:\ClusterStorage\Volume1\.
I am attaching the log for the Backup Plan (BackupPlanLog.txt) as well as the log for one of the VMs (VMBackupLog.txt). The BackupPlanLog.txt errors are repeated for each of the 3 VMs I am trying to backup and the errors for the 3 virtual machines are identical.
I am not sure if the problem lies with the CSV, or perhaps the Default Backup Plan VSS option. I am using the default VSS Option (Software - System Provider).
Also, I reinstalled ABR 11.5 Virtual Edition directly, I did not install version 11 and then install 11.5. I made sure to import the 11.5 license key.
Thanks,
Vint
Attachment | Size |
---|---|
vmbackuplog.txt | 3.17 KB |
backupplanlog.txt | 889 bytes |

- Log in to post comments

UPDATE: I tried to perform a backup after turning of the Change Block Tracking default backup option, no joy. I have tried also tried backing up some Windows Server 2003 R2 VMs and they too fail. I think this has something to do with the cluster and/or the VM agent.
When I edit any backup plan, I am selecting the VMs through the 'Hosts and cluster' tree but it is not saving. When I go back and re-edit the plans, it still shows the VMs being backup via the individual cluster node.
Any thoughts?
Thanks,
Vint
- Log in to post comments

When I edit any backup plan, I am selecting the VMs through the 'Hosts and cluster' tree but it is not saving. When I go back and re-edit the plans, it still shows the VMs being backup via the individual cluster node.
It doesn't matter. What is recorded in backup plan is the same in both cases - "VM with guid X"
- Log in to post comments

RESOLUTION:
I uninstalled the 11.5 Agent on the VM hosts, then reinstalled 11, updated to 11.5 and things are going again.
- Log in to post comments