|Legato Storage Manager Administrator's Guide
Use save set recover to recover backed up data that has passed the period of its browse policy but is still in the media database. Save set recover can be initiated either from the command line by executing the
recover program and providing specific save set identification numbers (ssid) as options, or from the LSM administration program (
nwadmin). Individual files or directories can be specified by including the exact path along with the ssid. Permission to perform a save set
Use save set recover only when the entries have been removed from the online file index (when the save set has passed its browse policy). When you perform a save set recover, you must recover the level full backup first, then recover the other backups in level order, 1 through 9, then recover the incremental backups.
scanner program to re-create client file index entries or re-create media database entries, if no entries for the volume exist in the media database. The
scanner program can read the storage volume directly, without assistance from LSM.
To find the volume that contains the file you want, use the
mminfo program if the volume is still in the media database or the
scanner program, if the volume is no longer in the media database. The
mminfo and the
scanner programs provide detailed information of the contents of the volume. This information includes:
If the file is not browsable (which means that the save set's browse policy has expired), but its save set is still tracked by LSM in the media database (which means that the save set's retention policy has not expired), follow these steps to recover the save set's entry back into the client file index:
mminfooutput, find the save set ID that you believe contains the file you want. Make sure it is not the bootstrap save set ID.
recoverprogram to mark the file for recovery.
If the save set that contains the file is not browsable, and the save set is not represented in the media database, both the browse and retention policies have expired. Follow these steps to rebuild the save set's entry in both the client file index and the media database:
scannerprogram on the backup volume that you believe contains the file you want (make a guess based on the adhesive label on the volume).
scannerprogram to decide whether to re-introduce the contents of this volume into the client file indexes and whether the save set you want to rebuild is on this volume. You must locate all of the volumes that contain this save set ID.
scanner command asks for a new volume until you terminate it. To rebuild the indexes completely, you must scan in all of the volumes that contain the save set ID.
nwrecoverprogram to browse the file index for the file you want to recover.
To recover an entire save set directly to your disk volume, use the following options to invoke the
This command reads all the information associated with the save set ID from the volume and place a copy of this data on the LSM server in the exact way that it is stored on the backup volume. In other words, the backup volume may contain files for a client, but will be recovered to the LSM server's hard drive.
If you want to be sure this action is correct before you actually perform it, add the
-n flag to the uasm command. The
-n flag sends the output from
scanner to /dev/null and lists all the filenames contained in the save set.
You could also use
rsh (or its equivalent) in conjunction with the following command in order to recover the save set to the client, if the save set originated on a LSM client instead of the LSM server.
To recover a single file from a volume, run one of the following commands:
-m option of uasm maps (relocates) the recovered file from the source to the dest (destination) directory.
scanner program directly reads LSM media (such as backup tapes, optical disks, or files) to confirm the contents of a volume, to extract a save set from a volume, or to rebuild the LSM online indexes. You can only run this command as root. You must specify a device, which is usually one of the device names used by the LSM server. If the device is a tape drive, it must be a nonrewinding type.
If the scanner program is invoked without options (or only the -v option), the volume on the specified device is scanned and a table of contents is generated. The table of contents contains information about each save set found on the volume. By default, one line of information is written to standard output for each save set found on the volume. The information provides the client name, save set name, save time, level, size, files, save set ID, and a flag.
The following example describes the format and options available for the
scanner [ -Bimnpqv ] [ -s server ] [ -S ssid ]
[ -c client ] [ -N name ] [ -f file ] [ -r record ]
[ -t type ] [ -b pool ] device [ -x command argument-list ]
-bpool option to specify the pool that the volume should belong to. This option only applies to volumes backed up by versions of LSM that did not store pool information on the media.
-Boption, without the
-Soption, to quickly scan the tape to the location of the start of the bootstrap save sets. When the entire tape has been scanned, the save set ID and tape file location of the most recent bootstrap save set is printed to standard output.
-cclient option to instruct
scannerto only process save sets that came from the machine specified by client. You can specify more than one client name in the same command line. The
-coption can also be used in conjunction with the
-Noption, but only if the
-xoption are also specified.
-ffile option to start the scan at a specific media file number.
-ioption to instruct
scannerto rebuild both the client file indexes and media database from the volumes that are read. If you specify a single save set with the
-Sssid option, only the entries from the specified save set are made to the client file index.
-moption to instruct
scannerto rebuild only the media database for the volumes that are read.
-noption to run scanner without rebuilding the client file indexes or media database. This option provides a way to check the media without modifying the client file indexes or media database.
-Nname option to process only save sets that match the specified name. The value of name should be a literal string. You can specify multiple names when this option is used in conjunction with the
-cclient option, but only if the
-xoption are also specified.
-poption to print out information about each save set as it is processed.
-qoption to only display error messages or messages of significance.
-rrecord option to start the scan at a specific media record number, to avoid a scan of potentially unused information.
-sserver option, when you run the
scannerprogram on a storage node, to specify the controlling LSM server.
-Sssid option to extract the save set specified by ssid. When this option is used in conjunction with the
-xoptions, you can specify multiple ssid values. The save sets selected are in addition to any selected by the use of the
-Noptions. If the
-Boption is also specified, the value of ssid is assumed to be that of the bootstrap save set; only one
ssidcan be specified in this case.
-xcommand option, with an optional list of command arguments, to specify a UNIX command to execute on each save set scanned. This option can only be specified once per
scannercommand line, after the device specification.
Refer to the
scanner(1m) man page for examples of
scanner command usage and a list of common error messages.
If you use the
scanner program with the
-s option but without an
-m option, and you the following message:
The number in the bracket [xx] is the entry from the last query.
scanner command always rewinds the tape and reads the volume label to determine the block size. If the volume label is corrupted or unreadable, you will see a message asking you to enter the block size (in kilobytes).
Type in the block size; it must be an integer equal to or greater than 32. If you enter an integer that is less than 32, you receive the following message:
scanner program reads the volume directly, without accessing information that may be available in the media database. If no entries exist in the media database, you must take an educated guess at which volume contains the data to recover.
Mount the volume and execute the
scanner command with any of its options. The most commonly used
scanner options are as follows:
scanner -mdevice) and perform a save set recovery.
scanner -idevice) and perform either a save set recovery or a client file index-based recovery.
-idevice) and perform a save set recovery.
-mdevice) and perform either a save set recovery or a client file index-based recovery.
-Nsave-set-name options, along with any other of the options previously described to further specify the save sets by client or name.
scanner -ssave-set-id to send a specific save set to standard output.
-xoption to introduce further processing commands on a per save set basis.