If the failover from the production server to the recovery server was necessary because all protected data was lost on the production server, then the data must be restored to the production server before doing a failback. This data loss could occur if a disk or disk subsystem failed or was destroyed on the production server.
The data can be restored to the production server from the recovery using the following procedure after the necessary volume groups and logical volumes have been recreated.
-
On the recovery server stop the application.
-
On the production server execute the following command which will start scrt_aba:
rtdr -qC <Failover Context> resync -
On the recovery server execute the following command which will unmount any filesystems if the context has filesystems and unload the drivers.
rtstop -FC <failover context> -
On the recovery server execute the following command which will mark the state maps dirty.
scconfig -MC <failover context> -
On the recovery server execute the following command which will synchronize the data to the production server.
rtdr -qC <Failover Context ID> resync -
On the recovery server execute the following command which will show the state maps.
scconfig -PC <failover context> -
If the state maps are not clean on the recovery server wait until all the data is synchronized to the production server.
-
On the production server execute the following command which will create a snapshot to allow the integrity of the data to be checked.
scrt_ra -XC <failover context> -
On the production server execute the following command if the context has filesystems. This command will mount the filesystems.
rtmnt -C <failover context> -
On the production server verify the validity of the data.
-
On the production server execute the following command which will unmount any filesystems which were mounted in step 9.
rtumnt -C <failover context> -
On the production server execute the following command which will remove the snapshot created in step 8.
scrt_ra -WC <failover context> -
On the recovery servers execute the following command which will failback to the primary context.
rtdr -qC <Failover Context ID> failback -
On the production server execute the following command which will failback to the primary context.
rtdr -qC <Failover Context ID> failback