How to protect Hyper-V Virtual machines in Backup Exec using the Resilient Change Tracking (RCT) method

book

Article ID: 100045546

calendar_today

Updated On:

Description

Description

Following are the notes to protect Hyper-V Virtual machines in Backup Exec using the Resilient Change Tracking (RCT) method:

  • It is recommended that after a VM has been restored, the user ensures that the next backup of that VM is a FULL backup.
  • Backup Exec does not restore user defined checkpoints, when a virtual machine is protected using the RCT method and the virtual machine had user defined checkpoints at the time of the backup. All of the data present in the VM disks including the checkpoint disks are restored but the checkpoints will not be visible in the Hyper-V manager.
  • Restore of a VM hosted on a SMB share/Scale Out File Server share can only be done to original location or to a locally hosted volume on the Hyper-V host. Redirected restore to a different SMB share/Scale Out File Server share is not supported.
  • If the backup solution, has both Incremental and Differential backup templates added along with Full backup then the incremental/differential backup will backup changes with respect to the last backup done in that backup policy irrespective of whether that backup was a full backup or not.

RCT is enabled by default. To verify settings, go to Backup Exec settings --> Virtual Machines --> Hyper-V --> Use Resilient Change Tracking.

 

For details on faster processing method and standard processing method review article: https://www.veritas.com/support/en_US/article.100031826

Troubleshooting:

  • Snapshot failures may be seen during backup of a Linux VM, if the integration services are not running inside the virtual machine. Refer to Microsoft documentation and ensure the latest integration services are deployed and running correctly inside the virtual machine.
  • Access denied  errors maybe seen when doing backup browse or backup of a VM hosted on a SMB or Scale Out File Server share. This is likely because the logon account provided in Backup Exec does not have access to the SMB share. Refer to Microsoft documentation and ensure that the logon account has been given required permissions to the SMB share.

Issue/Introduction

How to protect Hyper-V Virtual machines in Backup Exec using the Resilient Change Tracking (RCT) method