Limitations: Resync/repair replication for resiliency groups
For resiliency groups which are recovered using backup path i.e Copy (Netbackup) technology, you need to perform resync/repair operation to reconfigure the replication for those resiliency groups. Below are the scenarios where resync operation is not supported after performing the restore operation from NetBackup console.
Virtual machines that are restored on the local data center with new instance or BIOS UUID with Overwrite VM settings, the current protected virtual machine is deleted.
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.
Virtual machines that are that are restored with same instance or BIOS UUID on local data center and the disk count or size or SCSI locations are changed.
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.
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.
Even though the above mentioned points are limitations, there are workaround for the limitations. Refer Troubleshooting: Resync/repair replication issues for resiliency group configured using Multi-RPO recovery of hosts service objective for more details.