This article describes how to restore the SEP sesam Server from tape via sbc without using sm_recover. For details on SBC CLI usage and available commands, see SBC CLI. The described procedure works only if the SESAM_BACKUP saveset is on ONE tape.
- Operating system with working tape drive or loader device.
- Installed SEP sesam Server (identical version to the preceding system): Install the same SEP sesam Server package that was installed on the old system and set up the new server system in the same way as the previous one. For details on installation, see SEP sesam Quick Install Guide. If your tape drive / tape library is connected to an RDS, configure the RDS in the sesam database.
- A medium that contains correctly saved SESAM_BACKUP (containing <SESAM_VAR> and <SESAM_ROOT>/bin/sesam directories). For details, see Configuring SESAM_BACKUP.
The restore of the SEP sesam Server described below is a two-step procedure consisting of determining the required saveset information and restoring via sbc.
Listing the savesets on the tape via sm_sms_interface
Use the sm_sms_interface command to access the SMS Server and identify the available savesets on tape. Insert the tape with the SESAM_BACKUP backup savesets and identify the savesets on the tape device by using the command:
sm_sms_interface dir -d <tape_device>
|On Windows, replace the tape device identifier (/dev/nst0) with the corresponding Windows device (Tape0).
Obtain the required information from the output as shown in the example below:
- The first number in the highlighted line is the segment number; in our example: 4.
- The SavesetName is SEP sesam unique identification assigned to a saveset; in our example: SC20090610105624.
- The Tapelabel in the header displays the <tape_name>; in our example: cefix00001.
- The TapeID in the header displays the <tape_id>; in our example: (1)