Planned Failover for 3-node non-clustered broadcast replication groups - assure_mimix - assure_mimix_for_aix - 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-10-08
ft:lastPublication
2025-10-08T06:18:25.453000

The Steps portlet shows the steps that you must manually run to perform a planned failover for 3-node non-clustered broadcast replication groups.

  1. Select Run on the Action toolbar on the Steps portlet.

Note: In the first step of the Planned Failover Procedure dialog, you can select either Recovery 1 or Recovery 2 to be the New production server.

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

Table 8: Run Planned Failover for 3-node non-clustered broadcast replication groups

Sequence Number

Step

Dialog for this step

Command for this step

10

Unmount the file systems on the current production server;

Note: You can select the failover recovery server on this dialog.

Run Planned Failover Procedure dialog for 3-node non-clustered broadcast 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 3-node non-clustered broadcast replication groups: Stop replication on current production server

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

30

Prepare current recovery server for failover

Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast replication groups: Prepare current recovery server for failover

rtdr -q -C <Primary Context id> -F <Failover Context ID> -t <new production server> setup

40

Prepare current production server for failover

Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast replication groups: Prepare current production server for failover

rtdr -q -C <Primary Context id> -F <Failover Context ID> -t <new production server> setup

50

Failover the replication group. Server roles change

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

rtdr -q -C <Primary Context id> -F <Failover Context ID> -t <new production server> setup

60

Start replication on the new recovery server

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

rtdr -q -C <Failover Context ID> resync

70

Start replication on the new recovery server

Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast replication groups: Start replication on new recovery server 1

rtdr -q -C <Primary Context id> resync

80

Start replication on the new production server

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

rtdr -q -C <Failover 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.