Troubleshooting: Resync/repair replication issues for resiliency group configured using Multi-RPO recovery of hosts service objective
The following table lists some of the issues that you may come across while resync/repair replication issues for resiliency group configured using Multi-RPO recovery of hosts service objective. Below are the scenarios where resync operation is not supported after performing the restore operation from NetBackup console
Table: Resync / repair replication issues for resiliency group configured using multi-RPO recovery of hosts service objective
Description | Solution |
|---|---|
Resync/repair operation is not supported for this scenario as the original virtual machine is replaced with new virtual machine which has different identity due to change in either instance UUID or BIOS ID. | Solution: Edit the resiliency group. Remove such affected virtual machine(s) and re-add them. If all the virtual machine(s) are affected, then re-create the resiliency group. |
Unable to repair the replication in case of restored virtual machine from NetBackup console where the disk configuration does not match with existing disk configuration. Resync/repair is not supported if the disk configuration of the restored virtual machine differs in terms of disk count, disks SCSI locations, and disk sizes as compared to existing disk configuration. Existing disk configuration is the information obtained at the time of configuring resiliency group for respective virtual machine. | Solution:
|
Virtual machines that are restored on the local data center with new instance or BIOS UUID with Do not overwrite VM settings, the current protected virtual machine is intact. | Edit the resiliency group to remove the current virtual machines and add a new virtual machine. If all the virtual machines in the resiliency group are restored, delete the resiliency group and recreate it. |
Virtual machines that are restored on remote data center with new instance or BIOS UUID, the current protected virtual machine remains intact on local data center. | Delete the resiliency group and recreate it so that the new restored virtual machine is protected. Note: 1. Creating or editing resiliency group having multiple recovery points on remote data center works only if there is NetBackup AIR configuration setup from target data center to source data center. To configure resiliency group with multiple recovery points, create a resiliency group with replication technology, migrate back to the source data center. Then change the service objective to multi-RPO recovery of hosts and recover back to the target data center. Note: 2. If the backup image is restored keeping the same virtual machine name and which is already restored on the remote data center, during the replication DR operation with the current protected virtual machine, the DR operation fails at Register virtual machine step due to VMware error. Note: 3. If the backup image is restored using different virtual machine name and which is already restored on the remote data center, during the replication DR operation with the current protected virtual machine, the DR operation succeeds but the vCenter server shows VmMacConflictAlarm for the virtual machine. |
Virtual machines that are restored with same instance or BIOS UUID on remote data center, resiliency group displays the restored virtual machine as active on source and target data centers. This behavior is not supported. | Remove the virtual machine from the target data center if you want to continue with source data center. If you want the protection with resiliency group having multiple recovery points, delete the resiliency group and recreate it. Note: Creating or editing resiliency group having multiple recovery points on remote data center works only if there is NetBackup AIR configuration setup from target data center to source data center. To configure resiliency group with multiple recovery points, create a resiliency group with replication technology, migrate back to the source data center. Then change the service objective to multi-RPO recovery of hosts and recover back to the target data center. |