Virtual Machine Backup and Restore Related
This section includes the following troubleshooting topics related to the recovery point server (RPS), data store, and database:
- Add Permission for VDDK at vCenter Server Level
- Backup job for VM template is always converted to full backup
- Independent disks are skipped by backup job of VM template
- Backup job for VM on Microsoft SMB 3.0 share fails with error message
- VM recovery job fails when restoring VM to a Windows default file share
- Volume information unavailable for recovery point
- Permissions for Host-based Agentless Backup and Virtual Standby at vCenter Server Level
- Convert Incremental Backup to a Verify Backup Because the Virtual Machine Snapshot Either Changed from the Last Backup Job or Needs Consolidation
- Agentless backup for VMware VM fails for CD/DVD device of VM
- Agentless Host-based Backup for Hyper-V Fails after Upgrading Arcserve UDP
- Host-based Agentless Backup Fails in VMware ESXi 6.0
- Failed to Create a Snapshot for Hyper-V Virtual Machines when Multiple Jobs are Running
- Failed to Perform Backup of a Virtual Disk. System error=[The device is not ready(21)]
- Backup Job Fails
- Failing to import VMware VMs from vCenter
- Unable to Apply Backup Settings to Node
- Backups Fail Due to ESXi License
- Host-based Agentless Backup does not Use HotAdd Transport Mode
- HotAdd Transport Mode does not Work when Attempting to Back Up a VMware VM
- Host-based Agentless Backup or Restore Job Uses NBD or NBDSSL Transport Mode even when SAN Mode is Possible
- Recovery Operations Fail when Recovering Data Using the HotAdd or SAN Transport Mode
- Recover VM Operation fails when a non-default port is specified
- Scheduled Incremental or Full Backup Job Fails for Hyper-V VM
- Hyper-V VSS NTDS Writer Fails while Taking the VSS Snapshot in the VM
- MAC Address Changes are not Retained After VM Recovery
- Hyper-V Failed to Create VSS Snapshot
- Unable to Open VMDK Files
- Problems Caused by Duplicate VM UUID
- File System Catalog Job Fails or Recovery Point Check Fails for Host-Based Agentless Backup
- Incremental Backup Converts to Verify Backup or the Backup Size Increases in Hyper-V
- Host-Based Agentless Backup Fails Hyper-V VM That has a Special Differencing Disk Configuration
- Backup Job Fails for a VMware Virtual Machine
- Disable Rescan of Host Bus Adapters when the Source and Proxy are in Different VMware ESX Servers
- Disable the Consecutive Snapshot Creation in VMware VM for a Backup
- Agentless Host-based Backup crashes when using Windows 2003 R2 64-bit as Backup Proxy
- When Restored from a Higher Version of ESXi host to a Lower version ESXi host, VM gets stuck at booting stage
- RAM Utilization reaches 99% When Backup Jobs are Submitted to VM
- Hyper-V Restore Job Fails, Cannot Connect to Utility on Host
- Automatic Protection Fails to Detect and Protect VM
- Set Read block size when backing up VMDK file