Planned Failover for 2-node non-clustered replication groups - assure_mimix - 6.0

Assure MIMIX for AIX Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software for AIX
Version
6.0
ft:locale
en-US
Product name
Assure MIMIX for AIX
ft:title
Assure MIMIX for AIX Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2025-03-12
ft:lastPublication
2025-03-12T05:07:12.494000

The Steps portlet shows the steps that you must manually run to perform a planned failover for 2-node non-clustered replication groups. Select Run on the Action toolbar on the Steps portlet.

Table 4  on page 281 shows the commands that are run on the servers, while you execute the procedure steps with the Assure UI portal.

Table 4: Run Planned Failover for 2-node non-clustered replication groups

Sequence Number

Step

Dialog for this step

Command for this step

10

Unmount the file systems on the current production server;

Run Planned Failover Procedure dialog for 2-node non-clustered replication groups: Unmount file systems on current production server

rtumnt -R -C <Primary Context id> 

20

Stop replication on the current production server

Resume Planned Failover Procedure dialog for 2-node non-clustered replication groups: Stop replication on current production server

rtstop -S -F -C <Primary Context id> 

30

Failover the replication group. Server roles change

Resume Planned Failover Procedure dialog for 2-node non-clustered replication groups: Failover replication group: Server roles change

rtdr -q -C <Primary Context id> failover

40

Start replication on the new recovery server

Resume Planned Failover Procedure dialog for 2-node non-clustered replication groups: Start replication on the new recovery server

rtdr -q -C <Primary Context id> resync

50

Start replication on the new production server

Resume Planned Failover Procedure dialog for 2-node non-clustered replication groups: Start replication on new production server

rtdr -q -C <Primary Context id> resync

Note: When the procedure completes, and you are ready to move production back to the configured production server, run the failback procedure.