Veritas InfoScale™ Operations Manager 7.3.1 Add-ons User's Guide

Understanding the Setup Storage operation

In this operation, the storage tasks are taken care of.

If you chose to create mirror disk groups, the mirror disk groups are created and data sync is ensured.

The operation aborts if all volumes of all the disk groups being migrated is mirrored with the corresponding volumes in the mirror disk group. In this scenario, 100% sync between all volumes is not verified. This check is performed as part of the Rehearse or Migrate operation. If only some volumes are mirrored, the system is cleaned up so that the Setup Storage operation can be performed again. Only for the disk groups where the mirror was created by the application migration plan are cleaned up; mirrors created earlier are not cleaned up.

In this operation, Replication configuration is created and replication is established between the source cluster node and target cluster for disk groups marked as Create New. Initially, a basic verification is done to ensure that all disk groups marked Use Existing has RVGs configured and secondaries added and disk groups marked with Create New should have RVG configuration only if it was pre-created before creating the plan. All verifications are done in par with the configuration discovered during plan creation. Once verification is complete, DCM log is added to all volumes in the disk group after which SRL Volume is created as per the size calculations. Primary RVG is then created on the disk groups marked as Create New.

Migration plan creates a single RVG for each disk group and will have all volumes of the disk group made part of it. If RVGs are already pre-created on a disk group, these RVGs are used. Disk groups, volumes, and volume sets (if present) are then created on the target cluster node according to its size calculated from the source cluster node. After this is done, the target cluster node is added as a secondary site to the Primary RVG after which the replication is started.

Setup Storage operation completes only when Replication Sync is 100% complete. If any application writes are happening to the volumes on the source, it may take more time for the sync to complete. If you notice the sync is not progressing for a long time, check whether SRL has not overflowed in the logs and if so, it is recommended to reduce or stop application writes so that sync gets completed. Replication configuration created by the plan will be with default values and finetuning is also not performed.

On the source cluster, IP resources are added to the service group where the disk group resource is configured. These resources monitors the IPs used for replication. If the disk group is shared (CVM), IP resource and RVGLogowner resources are created in a separate failover service group with the name amVvR_sg_failover_plan_name and is linked to the service group which has the CVMVolDG resource configured.

On the target cluster, a service group is created by the name amVvR_sg_plan_name. IP and disk group resources for the entities created by the plan is added to this service group. In case of a shared disk group, a parallel service group by the name amVvR_sg_parallel_plan_name is created in which CVMVolDG resource is added and another failover service group is created amVvR_sg_failover_plan_name which contains the IP and RVGLogowner resources. The operation aborts if all RVGs in all disk groups which are part of the migration have secondaries added to it.