Testing the recovery appliance

You can test that the recovery appliance in a disaster recovery configuration is operating correctly without disrupting the main site.

About this task

You test the recovery appliance by disabling the replication interface between main and recovery appliances. You make the secondary queue manager into the primary and remove it from the disaster recovery configuration. You can then test the stand-alone queue manager. After testing is complete, you restore the replication interface and delete the queue manager. You then re-create the queue manager as the secondary queue manager in the disaster recovery configuration.

Note: The procedure assumes you are using the default eth20 as the replication interface. If you specified a different interface for replication when you created the DR configuration, substitute that interface in the instructions.

Procedure

Disable the replication link on the recovery appliance:
```
# ethernet eth20
Modify Ethernet Interface configuration
# admin-state disabled
# exit
```
You can now work on the recovery appliance without affecting the main appliance.
On the recovery appliance, make the queue manager the primary:
```
makedrprimary -m QMname
```
Where QMname is the name of the queue manager.
Remove the queue manager from the disaster recovery configuration:
```
dltdrprimary -m QMname
```
Start the queue manager:
```
strmqm QMname
```
Connect applications to the queue manager and test that they work as expected.
End the queue manager:
```
endmqm QMname
```
Delete the queue manager:
```
dltmqm QMname
```

Restore the replication link between the main and recovery appliances:

# ethernet eth20
Modify Ethernet Interface configuration
# admin-state enabled
# exit

On the main appliance, run the dspdrsecondary command to retrieve the crtdrsecondary command that you used when you first configured disaster recovery. Run the resulting crtdrsecondary command on the recovery appliance to recreate the secondary queue manager. The primary queue manager on the main appliance synchronizes its data with the secondary queue manager to bring it up to date.