If you have restored the database on the source or target server, you should perform reconciliation between the virtual volumes on the source server and the archive files on the target server. You should also perform reconciliation if you have any other reason to suspect inconsistencies. For example, frequent communication errors between target and source servers could introduce a problem.
To perform reconciliation, issue the RECONCILE VOLUMES command specifying a device class of the device type of SERVER. In the following example TARGETCLASS is a server device class:
reconcile volumes targetclass fix=yes
The reconciliation action is determined by the FIX parameter as shown in
the following table:
| FIX= | At the Source Server | At the Target Server | Action |
|---|---|---|---|
| NO | Volumes exist | No files exist | Report error |
| Files exist but are marked for deletion | |||
| Active files exist but attributes do not match | |||
| Volumes do not exist | Active files exist | Report error | |
| Files exist but are marked for deletion | None | ||
| YES | Volumes exist | No files exist | Report error
For storage pool volumes: Mark volumes as unavailable |
| Files exist but marked for deletion | Report error
For storage pool volumes: If attributes match, mark files on the target server as active again, mark volumes on the source server as unavailable, and recommend that an AUDIT VOLUME be done to further verify the data. If attributes do not match, mark volumes as unavailable. | ||
| Active files exist but attributes do not match | Report error
For storage pool volumes: Mark volumes as unavailable and recommend that an AUDIT VOLUME be done to further verify the data. | ||
| Volumes do not exist | Active files exist | Mark files for deletion on the target server. | |
| Files exist but marked for deletion | None |