Avamar for VMware contains the following common restore problems and solutions.
Preexisting snapshots cause restores to fail
Virtual machine restores fails if a snapshot for that virtual machine exists. In this scenario, the restore operation will return an error message similar to the following:
2012-12-07 09:30:26 avvcbimage FATAL <0000>: The pre-existing snapshots from VMX '[VNXe3300-Datastore1] vm-example/vm-example.vmx' will not permit a restore.
2012-12-07 09:30:26 avvcbimage FATAL <0000>: If necessary, use the '--skip_snapshot_check' flag to override this pre-existing snapshot check.
To resolve this, clean up existing user created snapshots before restoring to original.
NOTE:Logs may suggest to skip the snapshot check, but do not use
--skip_snapshot_check
flag to override the pre-existing snapshot check.
Restore to new virtual machine not available when physical RDM disks are involved
If you back up a virtual machine that has both virtual disks and physical Raw Device Mapping (RDM) disks, the backup will successfully process the virtual disks, bypass the RDM disks.
While restoring data from one of these backups, you can restore the data to the original virtual machine. You can redirect it to another existing virtual machine. However, you cannot restore data to a new virtual machine.
NOTE:As the physical RDM disks were not processed during the backup, data residing on the physical RDM disks cannot be restored at all.
If it is required for you to restore data to a new virtual machine, you must:
Manually create a new virtual machine in vCenter.
This new virtual machine must have the same number of virtual disks as the original virtual machine from which the backup was taken.
Manually add the new virtual machine to Avamar.
Restore the data to this virtual machine.
FLR browse of a granular disk backup without a partition table is not supported
When a non-LVM granular disk backup is performed on a disk that does not have a partition table, FLR browsing of the backup fails with the following error:
Failed to mount disks. Verify that all the disks on the VM have valid/supported partitions.
The workaround for this issue is to perform a full image backup of all disks on the VM, then restore the files or folders from the disk that does not have a partition table.
Fault tolerance disabled when restore to new virtual machine is performed
When a fault-tolerant virtual machine is restored to a new virtual machine, fault tolerance is disabled. You will need to enable fault tolerance after the machine is restored to a new virtual machine. VMware documentation contains information regarding how to enable fault tolerance.
Restore to new virtual machine to Virtual SAN 5.5 will fail
Restore to new virtual machine to a Virtual SAN 5.5 will fail with the message
unable to access file if the restore is of a multiple disk VM using a combination of datastore types (VSAN and VMFS or NFS and the restore of first disk is to a non-VSAN datastore. To workaround this issue, select a VSAN datastore for the first disk of the VM. This issue is not seen in VSAN 6.0.
Powering on an instant access vFlash-VM backup to a host without flash capacity configured fails
Powering on an instant access vFlash-VM backup to a host without flash capacity configured fails with the following error:
The available virtual flash resource '0' MB ('0' bytes) is not sufficient for the requested operation
To workaround this issue, disable flash cache in VM before powering on.
Maximum number of NFS mounts with instant access issue
When using the instant access feature, if the following error message is displayed, the maximum number of NFS mounts as configured in vSphere may be insufficient.
vmir Error <0000>: Mount NFS datastore failed to start with error: Failed to create Data Domain
A related message may be displayed in vSphere as well:
vmir Error <0000>: NFS has reached the maximum number of supported volumes.
When using HTTPS for enhanced FLR performance on RHEL 5.x, ACLs will be incorrect after restore unless the standard C++ library is installed.
FLR of a folder or file name that contains certain special characters fails
Avamar for VMware does not support a backslash (\), a double quote ("), or an ampersand (&) in folder and file names for an FLR.
FLR to user profile fails when Admin Approval Mode is enabled
When the Microsoft Windows Admin Approval Mode (AAM) is enabled (FilterAdministratorToken=1), the administrator user cannot use FLR to restore a file or folder to an end user's profile.
A restore attempt results in the following error:
Unable to browse Destination
The directory cannot be browsed. Please check the directory of the VM
To overcome this issue, the administrator user should open the end user's folder from within
C:\Users\. The following Windows UAC message appears:
You don't currently have permission to access this folder.
To permanently give the administrator user access to the folder, click
Continue.
A VM-based FLR fails in the virtual machine interface
When you use the virtual machine interface to perform a VM-based FLR, the operation fails because of the following reasons:
The virus scanner restrictions on the VM, on which you perform the FLR blocks all the .exe files.
The security software on the VM blocks file transfers of the .exe files.
Workaround: Disable the firewall.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\