About resiliency groups with assets
Resiliency groups are the unit of management and control in Veritas Resiliency Platform. After assets are added to Resiliency Platform, you organize related assets into a resiliency group that you can protect and manage as a single entity. A resiliency group can have only physical machines or only virtual machines, a mix of physical and virtual machines is not supported. Similarly it can contain either all applications or all InfoScale applications but not a mix of both.
For example, you can organize several physical or virtual machines into a resiliency group, and name it VM_Finance. When you perform an operation on the VM_Finance resiliency group using the Resiliency Platform console, the operation is performed on all the assets that belong to the resiliency group. For example if you run the Start operation on the resiliency group, all the assets (physical machines or virtual machines) that belong to the resiliency group start booting. Or if you perform any of the disaster recovery operations such as Migrate on the resiliency group, all the assets within the group are migrated to the selected target data center.
Ensure that the following prerequisites are met while creating a resiliency group for remote recovery:
Ensure that all the virtual machines that are to be grouped in a single resiliency group belong to a single hypervisor or virtualization server (if not clustered), or to a single cluster.
Encryption and compression are disabled on Hyper-V servers.
Refresh the virtualization server (vCenter server or Hyper-V server), the host, and the cloud discovery before proceeding to create the resiliency group.
If the recovery is on Azure, then ensure that the virtual machine names should always start and end with alphanumeric characters. The name can contain periods (.), hyphens(-), or underscores(_) in the middle.
If you are using third-party replication, ensure that the assets consume storage from the same consistency groups. E.g. EMC SRDF device group, NetApp Volume, 3PAR replication group, and so on.
The operations available for a resiliency group depend on how it is configured. While configuring a resiliency group, you need to select a service objective. If you select a service object that supports remote recovery, then you can perform disaster recovery operations such as Migrate and Take over on the resiliency group.
Optionally you can use a service objective that only monitors the assets or the applications and provides only basic operation capabilities like start and stop operations and no remote recovery operations. Using the Copy service objective, you can recover the virtual machines from NetBackup generated backup images to the target data center.