Valid on Windows platforms.
Symptom:
A raw (full VM) mount operation or a file level VM mount operation failed.
Solutions:
To perform a raw (full VM) mount operation or a file level VM mount operation, VCB first takes a snapshot of a VM and then exports the files to the backup proxy system. There are several reasons this problem can occur and actions you can take to remedy this problem.
Action 1: Clean up the disk or change the mount path to a different volume that has enough space.
Action 2: Take corrective action if the VMware ESX Host system on which the VM resides is down.
Action 3: Run vcbMounter utility for the VM on the backup proxy system, if the VM has become temporarily unmountable.
You can run the utility using the command-line by navigating to the directory where VMware VCB framework is installed. To view the syntax for the utility, type the following in the command line:
vcbMounter -help
If the vcbMounter utility fails to mount the specified VM, then the problem could be with the VMware VCB framework. Restart the backup proxy system and resubmit the VM backup job.
Action 4: Clear or Remove the Independent disk mode setting for all virtual disks associated with the VM.
Action 5: Resubmit the VM backup job with valid credentials. You must provide valid VMware ESX Host system credentials or vCenter Server system credentials, and backup proxy system credentials on the Security and Agent Information dialog.
Action 6: Run the ARCserve VMware Configuration Tool or ca_vcbpopulatedb utility to populate the CA ARCserve Backup database with updated information about your VMware environment.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |