172 Alphabetical list of commands
On System2, set secondary volume rData to be the primary volume:
# set replication-primary-volume volume rData primary-volume rData
Info: Started setting the primary volume of the replication set. (RS)
Info: Setting the primary volume of the replication set. This may take a
couple of minutes... (RS)
Info: Successfully set primary volume: (rData)
Info: The primary volume of the replication set was changed. (RS)
Success: Command completed successfully. (2012-13-23 11:48:30)
On System2, view the set’s status and notice that the primary volume has changed and that a
primary-volume conflict exists:
# show replication-sets RS
Replication Set [Name (RS) Serial Number (<SN>) ] Primary Volume:
Name ... Status ... Location Primary-Volume ... Primary-Volume-Status
-----------------------------------------------------------------------
Data ... Online ... Remote Data ... Conflict
rData ... Online ... Local rData ... Conflict
On System1, view the set’s status and notice that it does not reflect the primary-volume change,
thereby causing the conflict:
# show replication-sets RS
Replication Set [Name (RS) Serial Number (<SN>) ] Primary Volume:
Name ... Status ... Location Primary-Volume ... Primary-Volume-Status
-----------------------------------------------------------------------
Data ... Online ... Local Data ... Conflict
rData ... Online ... Remote Data ... Conflict
On System1, as already done on System2, set rData to be the primary volume:
# set replication-primary-volume volume Data primary-volume rData
Info: Started setting the primary volume of the replication set. (RS)
Info: Setting the primary volume of the replication set. This may take a
couple of minutes... (RS)
Info: Successfully set primary volume: (rData)
Info: The primary volume of the replication set was changed. (RS)
Success: Command completed successfully. (2012-13-23 11:55:50)
On System1 (the new secondary system), view the set’s status and notice that the system is set to
use the new primary volume and the conflict is resolved:
# show replication-sets RS
Replication Set [Name (RS) Serial Number (<SN>) ] Primary Volume:
Name ... Status ... Location Primary-Volume ... Primary-Volume-Status
-----------------------------------------------------------------------
Data ... Online ... Local rData ... Online
rData ... Online ... Remote rData ... Online
Wait a couple of minutes for processing to complete. Then, on System2 (the new primary system),
view the set’s status and notice that the system is set to use the new primary volume and that the
conflict is resolved:
# show replication-sets
Replication Set [Name (RS) Serial Number (<SN>) ] Primary Volume:
Name ... Status ... Location Primary-Volume ... Primary-Volume-Status
-----------------------------------------------------------------------
Data ... Online ... Local rData ... Online
rData ... Online ... Remote rData ... Online
Map the new primary volume to hosts.