You can perform a production restore from archived LFCs when the LFCs on the recovery server do not go back far enough or when they are unavailable. Like any other production restore, you must stop the application on the Production Server and unmount the protected volumes before you roll them back.
To perform a production restore from archived LFCIDs, do the following:
-
Stop the application on the production server.
-
Unmount the protected volumes on the production server. Enter the following command:
rtumnt -C <Context ID><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. Enter the following command:
scrt_rc -C <Context ID>
This results in output similar to the following:
------------------------------------------------ Assure MIMIX DR 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> -
To display available restore target windows. Enter targets.
This should result in output similar to the following:
Current Snap Time: 1529922170 (LFCID: 1466): Mon Jun 25 10:22:50 2018 Available internal & external (tape) rollback windows: -------------------------------------------------------- Start: 1529922170 (LFCID: 1466): Mon Jun 25 10:22:50 2018 End: 1529920798 (LFCID: 1352): Mon Jun 25 09:59:58 2018 Available VFBs: -------------------------------------------------------- 1529916625 (LFCID: 1342): Mon Jun 25 08:50:25 2018 1526957343 (LFCID: 1986): Tue May 22 14:49:03 2018 1526609678 (LFCID: 1456): Fri May 18 14:14:38 2018 rc> -
Enter restore. This results in the following output:
Restore target type: t - time e - event marker l - lfc a - abort > -
Choose l for Log File Container.
This results in the following output:
LFC target >
If you are restoring from archived data, then the LFCID that you choose identifies data that is no longer stored on the recovery server.
-
Enter a LFCID <example 1360>
This results in the following output:
You have requested an incremental LFC restore from Fri Jun 22 10:22:50 2018 (1529662970) to Fri Jun 23 10:01:26 2018 (1529661686), LFCID’s 1466+ to 1360. c(ontinue) or a(bort)? -
Enter c to continue.
This should result in output similar to the following:
Rolling LFC restore status. --------------------------- Production at LFCID 1464. Production at LFCID 1462. Production at LFCID 1460. Production at LFCID 1458. Production restored to LFCID 1360. Backingstore remains stable at LFCID 1466. rc>Note: Although you have rolled back the production server to LFCID 1360, the snapshot on the recovery server still contains information up to and including LFCID 1464. This allows you to verify that LFCID 1360 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 on page 268. -
If you are satisfied that LFCID 1360 is correct, enter commit.
You will 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/rtestlv
The current volume is: /dev/testlv
Primary superblock is valid.
J2_LOGREDO:log redo processing for /dev/testlv
Primary superblock is valid.
Mounting /test...