Resolving a partitioned problem in a disaster recovery configuration

A partitioned problem is when the queue manager data on one of the appliances in a disaster recovery pair is out of step with the data on the other appliance.

A partitioned problem can arise when the replication link between the two appliances has been lost. It might be the case that a disaster has occurred, and the secondary queue manager has been started on the recovery appliance. When the main site is restored, the queue manager on the appliance there will be out of step with the queue manager on the recovery appliance.

Depending on how the partitioning occurred, your two appliances could show any of the statuses listed in the following table (this is the status when the previously disconnected connection is restored, but the queue manager is running on the recovery appliance):

Table 1. Partitioned statuses
Main site DR status	Recovery site DR status
Remote appliance(s) unavailable	Partitioned
Partitioned	Remote appliance(s) unavailable
Partitioned	Partitioned

In a partitioned situation you must decide whether to keep the data from the original queue manager, and copy this to the recovery queue manager, or keep the data from the recovery queue manager and copy this to the original queue manager. You use the makedrprimary and makedrsecondary commands to achieve the required outcome.

To keep the data from the queue manager on the recovery appliance:
1. Ensure the queue managers are stopped.
2. Specify that the queue manager on the main appliance is the secondary, for example:
```
makedrsecondary -m myqueuemanager
```
3. Specify that the queue manager on the recovery appliance is the primary, for example:
```
makedrprimary -m myqueuemanager
```
  Synchronization begins, with the data from the recovery appliance being copied to the main appliance.
4. When the synchronization is complete, run the makedrsecondary command on the queue manager on the recovery appliance, for example:
```
makedrsecondary -m myqueuemanager
```
5. Specify that the queue manager on the main appliance is now the primary, for example:
```
makedrprimary -m myqueuemanager
```
6. Start the queue manager on the main appliance, for example:
```
strmqm myqueuemanager
```
To keep the data from the queue manager on the main appliance:
1. Ensure the queue managers are stopped
2. Specify that the queue manager on the recovery appliance is the secondary, for example:
```
makedrsecondary -m myqueuemanager
```
3. Specify that the queue manager on the main appliance is the primary, for example:
```
makedrprimary -m myqueuemanager
```
  Synchronization begins, with the data from the main appliance being copied to the recovery appliance.
4. When synchronization is complete, start the queue manager on the main appliance, for example:
```
strmqm myqueuemanager
```