Contents |
Drives are devices saving data onto media within, i.e. Disk - Platter, Tape - Tape cartridge. They can be connected either to a Sesam computer (local drive) or to other computers that can be accessed through the network (remote drive). These are normally tape devices, with removable tape cartridges. It is also possible to back up data to disk or other directory oriented devices.
According to the grouping principle of Sesam the organization in drive groups is required here as well. Even standalone drives must belong to a group.
Large auto loaders can have several internal drives which are loaded from one magazine. It is recommended that these drives are organised into one group. A backup is delegated only to this group. Sesam searches for the particular drive to be used for the backup.
In addition to offering backup to standard tape drives, SEP sesam allows the full utilization of high capacity disk drives to fully complement and support growing bandwidth availability. These are noted as Virtual Drives. SEP sesam simulates media on these drives to fully utilize the directory and file structure to enhance backup performance. For the user there is no difference, except during configuration and setup, between virtual and physical tape loaders.
By using the Shared Drives option drives are designated for sharing to fully utilize newer Network technologies, e.g. SAN's, which allows the disks to be available to multiple servers at any time. A physical drive can be seen by any number of servers and can likewise be used by the relevant systems to store data. In this example, Shared Drives can only be written to by one client at a time as opposed to standard drive configurations. Parallel backups from separate clients are not possible. SEP sesam Shared Drives uses specific drive identifiers to monitor and track the drives and the attached servers. This means that multiple drives will be labeled similarly and various backup clients will be apportioned to them. The SEPuler will perform sequential backups from the outstanding event list.
Most often large Tape Loaders and Libraries have multiple drives installed to operate media cassettes. It is recommended to organize these multiple drives into a single group. A backup will then be delegated to only this Group. SEP sesam will select which drive to use for the backup task. Scheduled backup tasks will thus be distributed to the available drives within the Drive Group. These allow the optimal resource management in the event of a drive failure. In this case SEP sesam moves the backup tasks to the remaining drives within the Group.
Here the parameters of the selected element are shown and changed if necessary (Group or Drive).
New Drive Group is used to configure a new group.
Here the new drives are configured. Each drive must be assigned to a drive group; the drive group must have been previously created.
The Sesam-internal number of the drive drive-number is pre-set.
Field Loader specifies whether the drive is served by a loader or not. The loaders configured and accepted in Sesam appear in a drop down menu. When selecting "'no Loader"' sesam configures a manually operated standalone drive.
In the drop down Drive Type the type of the drive is set ( DISK-Types see below ).
In the field Device Server the client to which the drive is connected is entered. The drop down shows all clients configured in SEP sesam. The selection of the local computer creates a local connection, a remote device can also be specified.
Drive 1 and 2 are local drives
Drive 11 through 21 are remote Devices at various locations
Drive 1:
Drive 2:
Drive 11:
Drive 21:
In the event an expansion of one drive at location 1, Drive 12 will entered into the backup scheme.
Drive Name
Loader
Drive Type
Attention
The utilization of Removable Devices requires the insertion of the device path (Direct Option)!
Tape Server
Drive Group
Drive Number in Loader
Device (non-rewinding)
Info
Operating System Specific Designation
If the drive has been installed properly you can determine (output) the SCSI ID using the "sesam loader utility" (slu).
<SESAM_BIN>\sesam\slu.exe scan
You will now see a list all SCSI connected devices.
Example output:
ID=0000 other: WDC WD3000JD-55KLB0 (HardDisk) ID=3000 other: TSSTcorp DVD-ROM SH-D162C (CdRom0) ID=4030 Tape: Quantum DLT4000 D67E (Tape0) ID=4031 Loader: Quantum 1x8 E456 (Changer)
The visible ID must now be entered under "Device (SCSI-ID)".
You can use the same command to determine the necessary device files:
<SESAM_BIN>/sesam/slu scan
Example output:
ID=0000 other: ATA ST380013AS ID=1000 other: TOSHIBA ODD-DVD SD-M1802 ID=7040 Tape: Quantum DLT4000 D67E (/dev/nst0) ID=7050 Tape: Quantum DLT4000 D67E (/dev/nst1) ID=7060 Loader: HP C1194F 1.04 (/dev/sg4) STATUS=SUCCESS MSG="OK"
In addition to the SCSI-ID the Device File used will also be entered under "Device (SCSI-ID)" (you can test this wit the mt command).
Disk Type are automatically entered with the disk{Drive Number} (see below).
Properties - Options
The number of data streams available for backup have also been assigned pre-determined limits based on the type of Server License in use, e.g ONE (1), Standard (5) or Advanced (unlim.)
Example of SMS Stream Limitation
The system has a drive and a tape drive connected. Multiple backup tasks will be started simultaneously for execution after the close of business.
The system has one disk drive and two tape drives attached. The SMS channels are connected to all drives. Multiple jobs (e.g. 10) have been set to start in one Backup Series.
The system has one disk drive and three tape drives available for backup. The SMS channel is set to 8 datastreams per tape drive. Multiple tasks (e.g.) are started after close of business and within multiple Task Groups.
In Device the operating system specific SCSI-identification of the storage device is inserted. With the command ID/bin/sesam/sm_slu scan a list of the connected SCSI-devices can be created.
On Windows-Systems the identification to be entered is displayed in brackets at the end of the row - Tape\Number\ ( from the registry ). On UNIX- and LINUX-Systems the device representation is /dev/n ( test with the mt-command suggested ).
DISK-Types are automatically entered with disk{Drive Nr} ( see below ).
A special case are the virtual drives already mentioned above where no physical drives and moveable media (tapes) exist.
Type DISK_HARD Configuration by selection of drive type DISK_HARD and loader 0 . The device is not editable, it is automatically disk + drive-number.
The assignment of directories to virtual media is performed through the media-pool which also specifies the maximum capacity (in KB) for this pool. This later prevents the unsupervised writing to the disk.
Type DISK_CHNG Configuration by selection of drive type DISK_CHNG and no loader or physical loader if available. The device is not editable, it is automatically named "'disk"' + drive number. In Options the path for the virtual media is defined.
Selecting this option from the drive-group window shows following screen.
From the GUI, the following 7 actions may be taken for the selected drive. The execution and progress of the activity is shown in the lower, cyclically updated information window.
CAUTION After manual changes to the drive ( tapes removal or insertion), the drive must be dismounted.
Unload Media should not be confused with unloading from an Auto Loader. It means, in this case, that the tape in the drive should be released and ejected. The loader can re-acquire the tape and re-enter it into its cassette ( = Unload via Loader ).
Release Drive
Reconfigure Drive
Release Drive Group
Our sales team would be happy to assist you!
Browse and discover videos by SEP.