Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Corrupt index,need to restore from older tape
- Thread starter mcguirep
- Start date
I have scanned some pages from the Solstice Backup (Legato) disaster Recovery Guide. I hope it will be of assiatance to you
Backup Index and Configuration File Recovery
If the Backup indexes and con-figuration files that reside in the Insr/res directory have been destroyed, you will need to use the mmrecov command to recover them. This applies only to Backup servers; you do not need to perform this procedure for Backup clients because indexes and configuration files do not reside there.
If the operating system and the Backup software were also destroyed, they must be reinstalled prior to recovering the insr/res directory contents. See "System and Backup Software Recovery' on page 19.
When you use the mmrecov command to recover the Insr directory, you actually recover the contents of three important directories:
a /nsr/mm (media manager) directory - contains the Backup media index that tracks all of the Backup backup volumes.
a Insr/ index/ server-name directory - contains the server indexes, which has a list of all the server files that were backed up prior to the disaster. You recover the client indexes later, using the nwrecover program.
m /nsr/res directory - contains special Backup configuration files. The nsr. res file includes the list of clients that belong to the server, customized client configurations or selections, and device and registration information. The
nsrj b. res file includes the location of the backup volumes in the jukebox and label ternplate information. Unlike the indexes, the contents of this directory can not be reliably overwritten while Backup is running. Therefore, mmrecov recovers the Insr/res directory as Insr/res. R.
The mmrecov Command
Use the mmrecov command to recover the Backup server indexes and configuration files residing in the insr/res directory.
The mmrecov command asks you for the bootstrap save set identification number (ssid). 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 backup media you need and the bootstrap ssid.
In the following example, ssid 17851237 is the most recent bootstrap backup:
March 12 18:09 2001 mars's bootstrap information Page 1
date time level ssid file record volume
02/07/01 14:53:20 full 17826163 48 0 mars.1
02/07/01 18:15:38 9 17836325 87 0 mars.2
02/08/01 18:12:23 9 17846505 134 0 mars.2
02/09/01 10:49:13 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 'The Bootstrap Save Set ID" on page 5.
How to Recover Backup Server Indexes and Configuration Files
With the operating system and Backup software in place, recover the indexes and configuration files from the backup media:
1. Find the bootstrap information, which you need for the next two 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. For ezample
# mmrecov
Doing mmrecov operation as root on the server
mmrecov: Using mars 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(S) and nsr_crash(8) man pages for more details.
rd=mars:lspacel/DISKDEV1 rd=mars@-Ispacel/DISKDEv2 Ispacel/DISKDEVI Ispacell DISKDEV2
What is the name of the device you plan on using trd=mars:lspacel/DISKDEVI]? lopacel/DISXDZVI
Enter the latest bootstrap save set id [1: 17851237
Enter starting file number (if known) tO]: 52
Enter starting record number (if known) (01: 0
Please insert the volume on which save set id 17851237 started into Ispacell DISKDEV1. When you have done this, press <RETURN>: [Return]
Scanning Ispacel/DISKDEVI for save set 17851237; this may take a while... scanner: scanning optical disk TestBackup.199 on /spacel/DISKDEVI Insr/res/nsr.res
/nsr/res/nsrjb.res
scanner: ssid 17851237: scan complete
scanner: ssid 17851237: 44 KB, 11 file(s)
/nsr/res/nsrla.res
/nsr/res/
/nsrlmm/
/nsr/indexlmars/
/nsr/indexl
/nsr/
nsrmmdbasm -r /nsr/mm/mmvolume/
nsrindexasm -r /nsr/index/mars/db/
/spacel/DISKDEV1: mount operation in progress
/spacel/DISKDEVI: mounted optical disk TestBackup.199 (write protected)
The bootstrap entry in the on-line index for mars 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 1 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.
7 records recovered, 0 discarded.
nsrindexasm: Pursuing index pieces of /nsr/index/mars/db from mars.
Recovering files into their original locations.
nsrindexasm -r /mars/db/
merging with existing mars index
mars: 2035 records recovered, 0 discarded.
Received 1 matching file(s) from NSR server 'mars'
Recover completion time: Tue Jun 24 16:46:38 1997
Cross checking index for client mars to remove duplicate records
The index for mars is now fully recovered
Unlike the Insr/indexes directory, the /nsri'res directory containing the configuration files cannot be reliably overwritten while Backup is running. Therefore, mmrecov recovers the /nsr/res directory as /nsr/res. R.
To complete the recovery of the Backup configuration files:
1. Shutdown Backup.
2. Renaine the existing /nsr/res directory to nsr/Res. orig.
3. Rename the recovered ires. R directory to Insr/res.
4. Restart Backup.
Complete these steps after mmrecov has finished and this final message appears:
The on-line index for 'server' is now fully recovered.
1. Shut down the Backup server using the nsr@_shutdown command:
# nsr-shutdown
2. Save the original res directory as res. orig, and rename the recovered file (res. R) to res.
26
6. Run save set recover, and enter the save set ID, for example, given the information above, one would run the following command:
1 # recover -a server -S 18196
When the recover is finished, the rnessage be displayed.
"The index is now fully recovered" will
Unlike the Insr/indexes directory, the /nsri'res directory containing the configuration files cannot be reliably overwritten while Backup is running. Therefore, mmrecov recovers the Insr/res directory as /nsr/res. R.
To complete the recovery of the Backup configuration files:
1. Shutdown Backup.
2. Renaine the existing /nsr/res directory to nsr/Res. orig.
3. Rename the recovered /res. R directory to /nsr/res.
4. Restart Backup.
Complete these steps after mmrecov has finished and this final message appears:
The on-line index for 'server' is now fully recovered.
1. Shut down the Backup server using the nsr@_shutdown command:
# nsr-shutdown
2. Save the original res directory as res. orig, and rename the recovered file (res. R) to res.
Solstice Backup 5.0.1 Disaster Recovery Guide . September 1997
Backup Index and Configuration File Recovery
If the Backup indexes and con-figuration files that reside in the Insr/res directory have been destroyed, you will need to use the mmrecov command to recover them. This applies only to Backup servers; you do not need to perform this procedure for Backup clients because indexes and configuration files do not reside there.
If the operating system and the Backup software were also destroyed, they must be reinstalled prior to recovering the insr/res directory contents. See "System and Backup Software Recovery' on page 19.
When you use the mmrecov command to recover the Insr directory, you actually recover the contents of three important directories:
a /nsr/mm (media manager) directory - contains the Backup media index that tracks all of the Backup backup volumes.
a Insr/ index/ server-name directory - contains the server indexes, which has a list of all the server files that were backed up prior to the disaster. You recover the client indexes later, using the nwrecover program.
m /nsr/res directory - contains special Backup configuration files. The nsr. res file includes the list of clients that belong to the server, customized client configurations or selections, and device and registration information. The
nsrj b. res file includes the location of the backup volumes in the jukebox and label ternplate information. Unlike the indexes, the contents of this directory can not be reliably overwritten while Backup is running. Therefore, mmrecov recovers the Insr/res directory as Insr/res. R.
The mmrecov Command
Use the mmrecov command to recover the Backup server indexes and configuration files residing in the insr/res directory.
The mmrecov command asks you for the bootstrap save set identification number (ssid). 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 backup media you need and the bootstrap ssid.
In the following example, ssid 17851237 is the most recent bootstrap backup:
March 12 18:09 2001 mars's bootstrap information Page 1
date time level ssid file record volume
02/07/01 14:53:20 full 17826163 48 0 mars.1
02/07/01 18:15:38 9 17836325 87 0 mars.2
02/08/01 18:12:23 9 17846505 134 0 mars.2
02/09/01 10:49:13 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 'The Bootstrap Save Set ID" on page 5.
How to Recover Backup Server Indexes and Configuration Files
With the operating system and Backup software in place, recover the indexes and configuration files from the backup media:
1. Find the bootstrap information, which you need for the next two 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. For ezample
# mmrecov
Doing mmrecov operation as root on the server
mmrecov: Using mars 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(S) and nsr_crash(8) man pages for more details.
rd=mars:lspacel/DISKDEV1 rd=mars@-Ispacel/DISKDEv2 Ispacel/DISKDEVI Ispacell DISKDEV2
What is the name of the device you plan on using trd=mars:lspacel/DISKDEVI]? lopacel/DISXDZVI
Enter the latest bootstrap save set id [1: 17851237
Enter starting file number (if known) tO]: 52
Enter starting record number (if known) (01: 0
Please insert the volume on which save set id 17851237 started into Ispacell DISKDEV1. When you have done this, press <RETURN>: [Return]
Scanning Ispacel/DISKDEVI for save set 17851237; this may take a while... scanner: scanning optical disk TestBackup.199 on /spacel/DISKDEVI Insr/res/nsr.res
/nsr/res/nsrjb.res
scanner: ssid 17851237: scan complete
scanner: ssid 17851237: 44 KB, 11 file(s)
/nsr/res/nsrla.res
/nsr/res/
/nsrlmm/
/nsr/indexlmars/
/nsr/indexl
/nsr/
nsrmmdbasm -r /nsr/mm/mmvolume/
nsrindexasm -r /nsr/index/mars/db/
/spacel/DISKDEV1: mount operation in progress
/spacel/DISKDEVI: mounted optical disk TestBackup.199 (write protected)
The bootstrap entry in the on-line index for mars 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 1 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.
7 records recovered, 0 discarded.
nsrindexasm: Pursuing index pieces of /nsr/index/mars/db from mars.
Recovering files into their original locations.
nsrindexasm -r /mars/db/
merging with existing mars index
mars: 2035 records recovered, 0 discarded.
Received 1 matching file(s) from NSR server 'mars'
Recover completion time: Tue Jun 24 16:46:38 1997
Cross checking index for client mars to remove duplicate records
The index for mars is now fully recovered
Unlike the Insr/indexes directory, the /nsri'res directory containing the configuration files cannot be reliably overwritten while Backup is running. Therefore, mmrecov recovers the /nsr/res directory as /nsr/res. R.
To complete the recovery of the Backup configuration files:
1. Shutdown Backup.
2. Renaine the existing /nsr/res directory to nsr/Res. orig.
3. Rename the recovered ires. R directory to Insr/res.
4. Restart Backup.
Complete these steps after mmrecov has finished and this final message appears:
The on-line index for 'server' is now fully recovered.
1. Shut down the Backup server using the nsr@_shutdown command:
# nsr-shutdown
2. Save the original res directory as res. orig, and rename the recovered file (res. R) to res.
26
6. Run save set recover, and enter the save set ID, for example, given the information above, one would run the following command:
1 # recover -a server -S 18196
When the recover is finished, the rnessage be displayed.
"The index is now fully recovered" will
Unlike the Insr/indexes directory, the /nsri'res directory containing the configuration files cannot be reliably overwritten while Backup is running. Therefore, mmrecov recovers the Insr/res directory as /nsr/res. R.
To complete the recovery of the Backup configuration files:
1. Shutdown Backup.
2. Renaine the existing /nsr/res directory to nsr/Res. orig.
3. Rename the recovered /res. R directory to /nsr/res.
4. Restart Backup.
Complete these steps after mmrecov has finished and this final message appears:
The on-line index for 'server' is now fully recovered.
1. Shut down the Backup server using the nsr@_shutdown command:
# nsr-shutdown
2. Save the original res directory as res. orig, and rename the recovered file (res. R) to res.
Solstice Backup 5.0.1 Disaster Recovery Guide . September 1997
- Status