You can create a snapshot based on a specific LFCID. You can use this snapshot for data mining and object repair on the production server.
-
On the recovery server, make sure all snapshot file systems are unmounted before trying to release the snapshot.
rtumnt -C <Context ID>
-
Make sure that no snapshot already exists on the recovery server.
scrt_ra -C <Context ID> -W
-
On the recovery server, create a snapshot based on a LFCID. The LFCID should precede the sequence of the current redo log, but should not be so far in the past that it has been archived to media such as tape.
scrt_ra -C <Context ID> -t <LFCID>
If the LFCID is 30, then the output is similar to the following:
Making SNAP /dev/vx/rdsk/rootdg/snvol2, 215.6 Making SNAP /dev/vx/rdsk/rootdg/snvol1, 215.10 Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_1, 215.14 Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_2, 215.18 Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_3, 215.22 Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_1, 215.26 Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_2, 215.30 Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_3, 215.34 Making SNAP /dev/vx/rdsk/rootdg/vol2, 215.4 Making SNAP /dev/vx/rdsk/rootdg/vol1, 215.8 Fetching LFC #33 Applying LFC #33 Fetching LFC #31 Applying LFC #31 The BackingStore Vdevs are at level 30. ABA is at level 34. -
Mount the volumes on the recovery server.
rtmnt -C <Context ID> -f
You should see output similar to the following:
log redo processing for /dev/rtestlv
syncpt record at 9028
end of log 9028
syncpt record at 9028
syncpt address 9028
number of log records = 1
number of do blocks = 0
number of nodo blocks = 0
/dev/rtestlv (/test): ** Unmounted cleanly - Check suppressed
Mounting /test...For information on database repair and database resurrection, refer to Chapter 11, Working with Assure MIMIX for AIX Applications.