To perform a production restore, complete the following tasks:
-
Stop the application on the production server.
-
Unmount the protected volumes on the production server. Enter the following command:
rtumnt -C <Context ID>
You should see output similar to the following:
rtumnt -C <Context ID> Determining Filesystems to unmount... Unmounting /dev/testlv from /test... Sync: transferring current LFC to Recovery Server. Waiting for synchronization of data to complete. All data has been synchronized to the Recovery Server. -
On the recovery server, start the production restore shell.
scrt_rc -C <Context ID>
This should result in output similar to the following:
------------------------------------------------ Assure MIMIX for AIX Production Restore Shell ------------------------------------------------ Ensuring LCA and ABA are up. LCA checked in. ABA checked in. Checking initial conditions... Checking production status... Bringing up restore server... RestoreServer checked in. Checking backend status... Initializing LCA restore session... LCA is in restore mode. Initializing RS restore session... Session is in production lead restore mode. --- Restore session initialized! --- type "help" at the prompt for a list of available commands. rc> -
Enter restore. This results in the following output:
Restore target type: t - time e - event marker l - lfc a - abort -
You can choose to rollback the production server to a specific time or a specific LFCID. If the current redo LFCID is 36 and you choose to rollback to LFCID 30, you should see output similar to the following:
You have requested an incremental LFC restore from Tue May 15 15:02:08 2018 (1526396528) to Mon May 14 15:38:03 2018 (1526312283), LFCIDs 36+ to 30. c(ontinue) or a(bort)? -
Enter c to continue.
Rolling LFC restore status -------------------------- Production at LFCID 34 Production at LFCID 32 Production at LFCID 30 Production restored to LFCID 30. Backingstore remains stable at LFCID 36 rc>Note: Although you have rolled back the production server to LFCID 30, the snapshot on the recovery server still contains information up to and including LFCID 36. This allows you to verify that LFCID 30 is the one you want to rollback to. If it is not, enter abort. Determine the proper LFCID and start the production restore shell as described in step 3. -
If you are satisfied that LFCID 30 is correct, then enter commit. You should see output similar to the following:
committing.... RestoreServer is down, exit code 0. Restore Client session complete. -
On the production server, mount the protected volumes. Enter the following command:
rtmnt -C <Context ID> -f
You should see output similar to the following:
Determining Filesystems to mount...
fsck -fp -y /dev/rlvesp00
/dev/rlvesp00 (/pfs00): ** Unmounted cleanly - Check suppressed
Mounting /pfs00...
fsck -fp -y /dev/rlvesp01
The current volume is: /dev/lvesp01
Primary superblock is valid.
Mounting /pfs01...