Using the mmrecov Command

Use the mmrecov command to recover the Backup server indexes and configuration files in the /nsr directory. Information in this section only applies to Backup servers.

The mmrecov command prompts you for the bootstrap save set identification number (ssid or save set ID). If you followed the recommended procedures to prepare for loss of critical data, you have a copy of the bootstrap file (either hardcopy or an electronic file) with the name of the needed backup media you need and the bootstrap ssid. (Never run the mmrecov command from root (/); you can use any other directory.)

In the following example, ssid 17851237 is the most recent bootstrap backup:

Jun 17  22:21 1997 mars's Backup bootstrap information
date    time    level   ssid    file    record                  volume
6/14/92 23:46:13        full    17826163        48      0       mars.1
6/15/92 22:45:15        9       17836325        87      0       mars.2
6/16/92 22:50:34        9       17846505        134     0       mars.2
6/17/92 22:20:25        9       17851237        52      0       mars.3

If you do not have this information, you can still recover the indexes by finding the ssid using the scanner -B command. See "Bootstrap Save Set ID".

With the operating system and Backup software in place, recover the indexes and configuration files from the backup media:

1. Find the bootstrap information.

   This information is needed for the following steps.

2. Mount the backup media that contains the most recent backup named bootstrap in a storage device.

3. Use the mmrecov command to extract the contents of the bootstrap backup. (Never run the mmrecov command from root (/); you can use any other directory.)

   For example:

   # mmrecov mmrecov: Using mars.sun.com as server NOTICE: mmrecov is used to recover the Backup server's on-line file and media indexes from media (backup tapes or disks) when either of the server's on-line file or media index has been lost or damaged. Note that this command will OVERWRITE the server's existing on- line file and media indexes. mmrecov is not used to recover Backup clients' on-line indexes; normal recover procedures may be used for this purpose. See the mmrecov(8) and nsr_crash(8) man pages for more details. Enter the latest bootstrap save set id []: 17851237 Enter starting file number (if known) [0]: 52 Enter starting record number (if known) [0]: 0 Please insert the volume on which save set id 17851237 started into /disk1/file.tape. When you have done this, press <RETURN>: Scanning /disk1/file.tape for save set 17851237; this may take a while... scanner: scanning file disk file.tape on /disk1/file.tape scanner: ssid 17851237: scan complete scanner: ssid 17851237: 28 KB, 11 file(s) /nsr/res/nsr.res /nsr/res/nsr.res: file exists, overwriting /nsr/res/nsrjb.res /nsr/res/nsrjb.res: file exists, overwriting /nsr/res/nsrla.res /nsr/res/nsrla.res: file exists, overwriting /nsr/res/ /nsr/mm/ /nsr/index/mars.sun.com/ /nsr/index/ /nsr/ / # nsrmmdbasm -r /nsr/mm/mmvolume/ nsrindexasm -r /nsr/index/mars.sun.com/db/ /disk1/file.tape: mount operation in progress mars.sun.com: 7 records recovered, 0 discarded. /disk1/file.tape: mounted file disk file.tape The bootstrap entry in the on-line index for mars.sun.com has been recovered. The complete index is now being reconstructed from the various partial indexes which were saved during the normal save for this server.

   If your resource files were lost, they are now recovered in the 'res.R' directory. Copy or move them to the 'res' directory, after the index has been reconstructed and you have shut down the daemons. Then restart the daemons. Otherwise, just restart the daemons after the index has been reconstructed. nsrindexasm: Pursuing index pieces of /nsr/index/mars.sun.com/db from mars.sun.com. Recovering files into their original locations. nsrindexasm -r ./mars.sun.com/db/ merging with existing mars.sun.com index mars.sun.com: 753 records recovered, 0 discarded. Received 1 matching file(s) from NSR server `mars.sun.com' Recover completion time: Wed Jan 28 08:37:38 1998 The index for `mars.sun.com' is now fully recovered.

   You can use Backup commands such as nsrwatch or nwadmin to watch the progress of the server during the recovery of the indexes and configuration files. Open a new window (shell tool) to monitor the recovery so that the mmrecov output is not displayed on top of the nsrwatch output. For example:

   mars# nsrwatch Server: mars.sun.com Wed Jan 28 08:53:54 1998 Up since: Wed Jan 28 08:35:15 1998 Version: Backup 5.1.Build.63 Eval Saves: 0 session(s) Recovers: 1 session(s), 131 KB total Device type volume Disk1/file.tape file file.tape reading, done Sessions: Messages: Wed 08:35:11 server notice: started Wed 08:35:22 index notice: completed checking 1 client(s) Wed 08:36:44 /disk1/file.tape mount operation in progress Wed 08:36:48 /disk1/file.tape mounted file disk file.tape Wed 08:37:36 /disk1/file.tape mounted file disk file.tape Wed 08:37:36 mars.sun.com:/nsr/index/mars.sun.com (1/28/98) starting read from file.tape of 131 KB Wed 08:37:37 mars.sun.com:/nsr/index/mars.sun.com (1/28/98) done reading 1 31 KB Pending: