To do replication group operations such as start, stop, failover or failback, on the
Main Menu move the cursor to Operations and press enter. The Operations menu will appear.
Start Replication Group
- Move the cursor to Start a Replication Group and press enter.
Select a replication group to start from the resulting Select Replication Group panel, and press enter.
Replication groups can be started either Normal (default) or non-Disruptive
modes.Normal - Is intended to start a Replication Group if file systems are not mounted.
Non-Disruptive - Is intended to start a Replication Group if file systems are mounted.
Select the pertinent mode and press enter. The request to start the replication
group is submitted.
Stop Replication Group
- Move the cursor to Stop a Replication Group and press enter.
- Select a replication group to stop on the resulting Select Replication Group panel, and press enter.Note: Stopping a replication group will attempt to unmount protected filesystems, potentially resulting in an application/database outage.Replication groups can be stopped via modes Sync (default), No-Sync or Agent-Only.
Sync - Stop processes will synchronize all dirty regions and then stop a Replication Group. This means that agents will be stopped and drivers
unloaded.
No-Sync - Stop processes stop the replication group. This means that agents will be stopped and drivers unloaded. Processing will not synchronize dirty regions prior to stopping.
Agent-Only - Stop processes will stop the agents and keep drivers
loaded.
Select the pertinent mode and press enter. The request to stop the replication group is submitted.
Failover Replication Group
- Move the cursor to Failover a Replication Group and press enter.
Select a replication group to failover from the resulting Select Replication Group panel, and press enter.
Replication groups can failover through modes Planned (default), Unplanned, Migration or One-Sided.Planned - Failover processes will synchronize all dirty regions from production node to recovery and complete the failover. Replication will flow in the opposite direction after the operation is completed.
Unplanned - Failover processes will failover a recovery node only since it is assumed that production node is down. After a production node is back up “Resync after Unplanned Failover” should be performed to start replication in the opposite direction.
Migration - Failover processes will stop a Replication Group on the production node with Sync-option and failover the recovery node. No sync in the opposite direction is done.
One-Sided - Is intended to failover the recovery node while theproduction still has primary context active. The replication is not running after the operation is completed. It can be used for testing purposes on the recovery node. After testing is completed Failback with “After One Sided Failover” should be performed.
Select the pertinent mode and press enter. The request to failover the
replication group is submitted.
Failback Replication Group
- Move the cursor to Failback a Replication Group and press enter.
Select a replication group to failover from the resulting Select Replication Group panel, and press enter.
Replication groups can failback through modes Normal (default) or After One-Sided Failover.
Normal - Failback processes will synchronize over all dirty regions from the configured recovery, current production to the configured production, current recovery and perform Failback so that replication will take place from the configured production to the configured recovery
After One-Sided Failover - Failback processes will failback the configured recovery node only. The configured production node still has primary context active.
LCA/ABA Hard Reset and Synchronize Logical Volumes should be performed after After One-Sided Failover Failback operation to resume replication from the configured production to the configured recovery.
Select the pertinent mode and press enter. The request to failback the replication group is submitted.