|
|
|
|
|
A Primary RLINK enters the fail state when the corresponding Secondary RLINK enters the FAIL state for any reason. This happens if there is an unrecoverable I/O error on one of the Secondary data volumes.
There are two ways for a Secondary RLINK to fail. One is if it encounters an I/O error that cannot be corrected. This is less likely to happen if the data volumes have been configured in a redundant fashion.
The second way for a Secondary RLINK to fail is if you enter the vxrlink -w pause command on the Secondary. This command must be used with great care because it enables data volumes on the Secondary to be written. The command must be used if a data volume must be restored from backup.
When the restore operation is complete, execute the following command:
# vxrlink -g diskgroup -c checkpoint_name restore rlink_name
This will return both the Primary and Secondary RLINKs to the active state.
Secondaries can also be restored from a Primary checkpoint if a Secondary checkpoint is not available, but the Primary checkpoint and corresponding backup are available.
If the Secondary RLINK cannot be restored, or if it is no longer needed, then vxrlink det can be used on either the Primary or the Secondary to detach the Primary RLINK and make it stale.
Note
In some cases after an RLINK has been moved from the fail state back to the active state, the RVG may remain in the fail state. This can be corrected by entering:
# vxrvg -g diskgroup start rvg_name