Source:Restore from tape via SBC without a valid SEP sesam database: Difference between revisions
(Removed incorrect info (proposed by EE).) |
|||
Line 35: | Line 35: | ||
'''sbc -r -l FULL -C <control_host>:11001 -S <storage_host>:11001 -d SMS:<tape_device> -t <tape_name>:<tape_id> -s <saveset_id> -n <segmentnummer> -R / -o overwrite''' | '''sbc -r -l FULL -C <control_host>:11001 -S <storage_host>:11001 -d SMS:<tape_device> -t <tape_name>:<tape_id> -s <saveset_id> -n <segmentnummer> -R / -o overwrite''' | ||
'''control_host''' is always the Sesam server itself | '''control_host''' is always the Sesam server itself |
Revision as of 15:15, 25 November 2020
Restore with SESAM Backup from tape without sm_recover.
Goals
Restore of a SESAM server without sm_recover only with sbc directly off a tape.
Prerequisite
1) Correctly set up OS with working Tape drive or loader device 2) Correctly installed SEP Sesam server (identical version to the preceding system) 3) Medium which contains a corretly saved SESAM-BACKUP
Displaying the savesets on the tape via sm_sms_interface
Note | |
In case of a Windows System replace the tape device identifier (/dev/nst0) with the corresponding Windows Device (Tape0) |
Important information here: 1) Segment number (4) 2) Saveset name (SC20090610105624) 3) Tape Label (cefix00001) 4) Tape ID (1)
Restore of the saveset via sbc
Note | |
The example command overwrites existing data files (-o overwrite)! Be sure to remove that option if you do not want to overwrite files. Also, the restore target can be changed with -R <path> |
Restore is done with the sbc command which contains the following information: sbc -r -l FULL -C <control_host>:11001 -S <storage_host>:11001 -d SMS:<tape_device> -t <tape_name>:<tape_id> -s <saveset_id> -n <segmentnummer> -R / -o overwrite
control_host is always the Sesam server itself
storage_host can be the Sesam server or a Remote Device Server (RDS), where the medium is attached at.