Archive:Drives 4.4: Difference between revisions

From SEPsesam
(Marked this version for translation)
(Update in progress, removed translation tags.)
Line 1: Line 1:
<noinclude><languages />
<noinclude><languages />
<translate>
<translate>
<!--T:96-->
 
{{Template:Navigator en 4.4|Loaders|Media pools}}</translate></noinclude><translate>
{{Template:Navigator en 4.4|Loaders|Media pools}}</translate></noinclude><translate>


==={{anchor|drives}}Drives=== 


==={{anchor|drives}}Drives=== <!--T:97--> 
<!--T:98-->
Drives are devices used for data storage that read from or write data to media. They are either local drives, connected to the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]], or remote drives, connected to another computer on the local or wide area network. These can be tape devices with removable tape cartridges or disk-based storage devices. Remote drives enable the storage devices, which are used by SEP sesam, to be distributed over WAN.
Drives are devices used for data storage that read from or write data to media. They are either local drives, connected to the [[Special:MyLanguage/SEP_sesam_Glossary#SEP sesam Server|SEP sesam Server]], or remote drives, connected to another computer on the local or wide area network. These can be tape devices with removable tape cartridges or disk-based storage devices. Remote drives enable the storage devices, which are used by SEP sesam, to be distributed over WAN.


===={{anchor|shared drives}}Shared drives==== <!--T:99-->
===={{anchor|shared drives}}Shared drives====


<!--T:100-->
SEP sesam provides dynamic drive sharing option in SAN environments. Note that a proper ''SEP sesam SAN Dynamic Drive Sharing'' (SDD) license is required for each drive you intend to share. For more information, see [[Special:MyLanguage/List_of_Licenses#Classic_licenses|List of Licenses]].  
SEP sesam provides dynamic drive sharing option in SAN environments. Note that a proper ''SEP sesam SAN Dynamic Drive Sharing'' (SDD) license is required for each drive you intend to share. For more information, see [[Special:MyLanguage/List_of_Licenses#Classic_licenses|List of Licenses]].  


<!--T:101-->
''Drive sharing'' option allows the drives to be available to multiple [[Special:MyLanguage/SEP_sesam_Glossary#RDS|Remote Device Servers]] (RDS) at any time. A physical drive can be seen by any number of RDSs and can be used by relevant systems to store data. Shared drives can be defined by a unique drive designation. This means that multiple drives are labeled with the same device identifier, which is specific SCSI designation, for example: ''/dev/nst0'' (Linux ), ''Tape0'' (Windows). While executing SEP sesam tasks, such as backup and restore, the drives are being shared by multiple servers based on a shared timing.
Shared drives option allows the drives to be available to multiple remote device servers (RDS) at any time. A physical drive can be seen by any number of RDSs and can be used by relevant systems to store data. Shared drives can be defined by assigning a unique drive designation. This means that multiple drives are labeled with the same device identifier, which is specific SCSI designation, for example: ''/dev/nst0'' (Linux ), ''Tape0'' (Windows). While executing SEP sesam tasks, such as backup and restore, the drives are being shared by multiple servers based on a shared timing.


<!--T:102-->
{{tip|It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured tape devices you should enable persistent naming and check their configuration to avoid errors in SEP sesam operation. For details, see [[Special:MyLanguage/4_4_3:Configuring_a_Loader#persistent_naming|Enabling persistent naming for tape devices]].}}
 
===={{anchor|drive_group}}Drive groups====
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.
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.


<!--T:103-->
Large autoloaders 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.
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.</translate>


<!-- TODO-TEXT Ins Englische übersetzen. -->
<translate>
<!--T:104-->
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.
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.


<!--T:105-->
[[Image:Drives_overview.png|center]]
[[Image:Drives_overview.png|center]]</translate>


<translate>===={{anchor|button properties}}Button Properties==== <!--T:106-->
===={{anchor|button properties}}Button properties====  


<!--T:107-->
Here the parameters of the selected element are shown and changed if necessary (Group or Drive).
Here the parameters of the selected element are shown and changed if necessary   (Group or Drive).


===={{anchor|new group}}New Group==== <!--T:108-->
===={{anchor|new group}}New Group====  


<!--T:109-->
The button '''New Group''' is used to configure a new group.
The button '''New Group''' is used to configure a new group.


<!--T:110-->
[[Image:Drives_new_drive_group.png|center]]
[[Image:Drives_new_drive_group.png|center]]


<!--T:111-->
;Name : An arbitrary name of the drive group
;Name : An arbitrary name of the drive group


<!--T:112-->
* Please select a description/name that is easily recognizable by all administrators, support personnel and users. This can and should be part of a general design that can be referred to and expanded at any time.
* Please select a description/name that is easily recognizable by all administrators, support personnel and users. This can and should be part of a general design that can be referred to and expanded at any time.


<!--T:113-->
;Description : additional information for the user
;Description : additional information for the user
* e.g. Input of the loader's location and the relevant employee contact for assistance.
* e.g. Input of the loader's location and the relevant employee contact for assistance.


===={{anchor|new drive}}New Drive==== <!--T:114-->
===={{anchor|new drive}}New Drive====


<!--T:115-->
Here the new drives are configured. Each drive must be assigned to a drive group; the drive group must have been previously created.
Here the new drives are configured. Each drive must be assigned to a drive group; the drive group must have been previously created.


<!--T:116-->
[[Image:Drives_new_drive.png|center]]
[[Image:Drives_new_drive.png|center]]


<!--T:117-->
The Sesam-internal number of the drive '''drive-number'''  is pre-set.
The Sesam-internal number of the drive '''drive-number'''  is pre-set.


<!--T:118-->
Field '''Loader'''  specifies whether the drive is served by a loader or not. The loaders configured and accepted
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 Sesam appear in a drop down menu. When selecting "'no Loader"' sesam configures a manually operated standalone drive.


<!--T:119-->
In the drop down '''Drive Type'''  the type of the drive is set  ( DISK-Types see below ).
In the drop down '''Drive Type'''  the type of the drive is set  ( DISK-Types see below ).


<!--T:120-->
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.
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.


<!--T:121-->
Configuration Example
Configuration Example


<!--T:122-->
Drive 1 and 2 are local drives
Drive 1 and 2 are local drives


<!--T:123-->
Drive 11 through 21 are remote Devices at various locations
Drive 11 through 21 are remote Devices at various locations</translate>


<translate>
Drive 1:  
<!--T:124-->
Drive 1:</translate> 
   08:00:18  I001-START  Start on Drive 1 finished
   08:00:18  I001-START  Start on Drive 1 finished
   08:00:18  Retrieves BACKUP Tasks from the SEPuler Event Calender
   08:00:18  Retrieves BACKUP Tasks from the SEPuler Event Calender
<translate>
 
<!--T:125-->
Drive 2:
Drive 2:</translate>
   09:08:58  Automatic Backup TEST_BACKUP finished
   09:08:58  Automatic Backup TEST_BACKUP finished
   09:10:39   
   09:10:39   
<translate>
 
<!--T:126-->
Drive 11:
Drive 11:</translate>
   09:05:57  Automatic Backup TEST_BACKUP finished
   09:05:57  Automatic Backup TEST_BACKUP finished
   09:07:37   
   09:07:37   
<translate>
 
<!--T:127-->
Drive 21:
Drive 21:</translate>
   10:32:47  Automatic Backup elektrik_orcl finished
   10:32:47  Automatic Backup elektrik_orcl finished
   10:34:54   
   10:34:54   


<translate>
 
<!--T:128-->
In the event an expansion of one drive at location 1, Drive 12 will entered into the backup scheme.
In the event an expansion of one drive at location 1, Drive 12 will entered into the backup scheme.


<!--T:129-->
Drive Name  
Drive Name  
     Freely selected or specified and if it is a shared drive within a SAN it must be the same for all client shared drives
     Freely selected or specified and if it is a shared drive within a SAN it must be the same for all client shared drives
     e.g. SAN-Drive-LUN-0. </translate>
     e.g. SAN-Drive-LUN-0.  
<translate>
 
<!--T:130-->
Loader   
Loader   
     This specifies whether the drive is controlled by a loader or not.  
     This specifies whether the drive is controlled by a loader or not.  
     Loaders configured allowed as devices within SEP sesam appear in the drop-down menu.  
     Loaders configured allowed as devices within SEP sesam appear in the drop-down menu.  
     'No Loader' simply means that it is a single drive and must be handled manually. </translate>
     'No Loader' simply means that it is a single drive and must be handled manually.  
<translate>
 
<!--T:131-->
Drive Type  
Drive Type  
     Choice of drive technology (e.g. DISK, DISK_HARD, DLT, LTO,...).
     Choice of drive technology (e.g. DISK, DISK_HARD, DLT, LTO,...).
     You can specify DISK_HARD und DISK_CHNG for hard disk drives.  
     You can specify DISK_HARD und DISK_CHNG for hard disk drives.  
     Hard drives in NAS or DAS architecture are treated as ''DISK_HARD''. </translate>
     Hard drives in NAS or DAS architecture are treated as ''DISK_HARD''.  
<translate>   
 
<!--T:132-->
DISK_CHNG is used for all backups to USP hard drives removable drives.  
DISK_CHNG is used for all backups to USP hard drives removable drives.  
     Using this configuration, e.g. a daily update is made and a new, initiated drive is used for backup.  
     Using this configuration, e.g. a daily update is made and a new, initiated drive is used for backup.  
     (This is similar to a tape drive with daily inserted tape).  
     (This is similar to a tape drive with daily inserted tape).  


<!--T:133-->
Attention
Attention


<!--T:134-->
The utilization of Removable Devices requires the insertion of the device path (Direct Option)!
The utilization of Removable Devices requires the insertion of the device path (Direct Option)!


<!--T:135-->
Tape Server   
Tape Server   
     In the field ''Tape Server'' you need to enter the backup server or remote device server where the drive is located/connected.
     In the field ''Tape Server'' you need to enter the backup server or remote device server where the drive is located/connected.
     The Drop down Menu shows everything on the configured clients.
     The Drop down Menu shows everything on the configured clients.
     The selection of the local/remote server either creates a local or remote device. </translate>
     The selection of the local/remote server either creates a local or remote device.  
<translate>
 
<!--T:136-->
Drive Group
Drive Group
     Every drive must be assigned to a drive group;
     Every drive must be assigned to a drive group;
     the assignment of multiple drives to a similar Drive Type is possible,
     the assignment of multiple drives to a similar Drive Type is possible,
     e.g. in the same auto loader with multiple drives.</translate>
     e.g. in the same auto loader with multiple drives.
<translate>
 
<!--T:137-->
Drive Number in Loader
Drive Number in Loader
     shows the sequence within in the Loader how drives will be used.
     shows the sequence within in the Loader how drives will be used.
     The order is dependent upon the hardware vendor's numbering scheme for all installed drives.
     The order is dependent upon the hardware vendor's numbering scheme for all installed drives.
     If the order is entered improperly SEP will not be able to access the correct drive or cassette.
     If the order is entered improperly SEP will not be able to access the correct drive or cassette.
     If there is only one drive in the Loader, '0' is automatically entered. </translate>
     If there is only one drive in the Loader, '0' is automatically entered.  
<translate>
 
<!--T:138-->
Device (non-rewinding)  
Device (non-rewinding)  
     Device Label, where the device has been configured.
     Device Label, where the device has been configured.
     For Tape Drives the Operating System specific SCSI designation is selected, e.g. /dev/nst0 or Tape0 (see the description below) </translate>
     For Tape Drives the Operating System specific SCSI designation is selected, e.g. /dev/nst0 or Tape0 (see the description below)  
<translate>
<!--T:139-->
Info   
Info   
     Status log for the drive. e.g. Read/Write Error  
     Status log for the drive. e.g. Read/Write Error  


<!--T:140-->
Operating System Specific Designation
Operating System Specific Designation


<!--T:141-->
* Windows:  
* Windows:  


<!--T:142-->
If the drive has been installed properly you can determine (output) the SCSI ID using the "sesam loader utility" (slu).
If the drive has been installed properly you can determine (output) the SCSI ID using the "sesam loader utility" (slu).</translate>


<SESAM_BIN>\sesam\slu.exe scan
<SESAM_BIN>\sesam\slu.exe scan


<translate>
<!--T:143-->
You will now see a list all SCSI connected devices.
You will now see a list all SCSI connected devices.


 
Example output:
<!--T:144-->
Example output:</translate>


ID=0000 other:  WDC WD3000JD-55KLB0 (HardDisk)
ID=0000 other:  WDC WD3000JD-55KLB0 (HardDisk)
Line 191: Line 143:
ID=4031 Loader: Quantum 1x8            E456 (Changer)
ID=4031 Loader: Quantum 1x8            E456 (Changer)


<translate>
<!--T:145-->
The visible ID must now be entered under "Device (SCSI-ID)".
The visible ID must now be entered under "Device (SCSI-ID)".


<!--T:146-->
* Linux:  
* Linux:  


<!--T:147-->
You can use the same command to determine the necessary device files:
You can use the same command to determine the necessary device files:</translate>


<SESAM_BIN>/sesam/slu scan
<SESAM_BIN>/sesam/slu scan


<translate>
Example output:
<!--T:148-->
Example output:</translate>


ID=0000 other:  ATA      ST380013AS
ID=0000 other:  ATA      ST380013AS
Line 214: Line 160:
STATUS=SUCCESS MSG="OK"
STATUS=SUCCESS MSG="OK"


<translate>
<!--T:149-->
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).
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).


<!--T:150-->
Disk Type are automatically entered with the disk{Drive Number} (see below).
Disk Type are automatically entered with the disk{Drive Number} (see below).


<!--T:151-->
Properties - Options
Properties - Options


<!--T:152-->
Path for Removable media  
Path for Removable media  
         for Type DISK_CHNG you just enter the Device Description/Label, e.g. /dev/media/USB or F:
         for Type DISK_CHNG you just enter the Device Description/Label, e.g. /dev/media/USB or F:
Block Size   
Block Size   
         for Type DISK_CHNG you need to enter the Block Size</translate>
         for Type DISK_CHNG you need to enter the Block Size
<translate>   
 
<!--T:153-->
SMS Number   
SMS Number   
         Shows the internally assigned SMS Number  
         Shows the internally assigned SMS Number  
Line 236: Line 176:
         Sets the maximum number of parallel streams that can be used during backup to the backup drive
         Sets the maximum number of parallel streams that can be used during backup to the backup drive


<!--T:154-->
 
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.)  
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.)  


<!--T:155-->
Example of SMS Stream Limitation
Example of SMS Stream Limitation


<!--T:156-->
SEP sesam ONE Server License
SEP sesam ONE Server License


<!--T:157-->
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 a drive and a tape drive connected. Multiple backup tasks will be started simultaneously for execution after the close of business.


<!--T:158-->
Result: The backups one after another to either the disk or tape drive, whichever has been specified. Only one backup stream is active.
Result: The backups one after another to either the disk or tape drive, whichever has been specified.
    Only one backup stream is active.


<!--T:159-->
SEP sesam Standard Server License
SEP sesam Standard Server License


<!--T:160-->
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 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.


<!--T:161-->
Result: Backups run parallel to either one of the drives or to both using 5 data streams depending on the desired backup path scheme.
Result: Backups run parallel to either one of the drives or to both using 5 data streams depending on the desired backup path scheme.
     Either one or both tape drives can be used simultaneously but only 5 data streams are open for data transfer.  
     Either one or both tape drives can be used simultaneously but only 5 data streams are open for data transfer.  


<!--T:162-->
SEP sesam Advanced Server License
SEP sesam Advanced Server License


<!--T:163-->
The system has one disk drive and three tape drives available for backup. The SMS channel is set to 8 data streams per tape drive. Multiple tasks (e.g.) are started after close of business and within multiple Task Groups.
The system has one disk drive and three tape drives available for backup. The SMS channel is set to 8 data streams per tape drive. Multiple tasks (e.g.) are started after close of business and within multiple Task Groups.


<!--T:164-->
Result: The backups run in parallel on all three drives.
Result: The backups run in parallel on all three drives.
     There is no limitation to the number of data streams that may be used or the SMS channels.
     There is no limitation to the number of data streams that may be used or the SMS channels.
     The configuration and number of streams used for backup is dependent upon the system capability and throughput (pipe) available.  
     The configuration and number of streams used for backup is dependent upon the system capability and throughput (pipe) available.  


<!--T:165-->
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.  
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.  


<!--T:166-->
On Windows-Systems the identification to be entered is displayed in brackets at the end of the row  - Tape\Number\
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 ).
( from the registry ). On UNIX- and LINUX-Systems the device representation is /dev/n ( test with the mt-command suggested ).


<!--T:167-->
DISK-Types are automatically entered with disk{Drive Nr} ( see below ).  
DISK-Types are automatically entered with disk{Drive Nr} ( see below ).  


<!--T:168-->
[[Image:Drives_drive_number.png|center]]
[[Image:Drives_drive_number.png|center]]


<!--T:169-->
;Drive Number: Number automatically assigned by SEP sesam, for a new drive it can be changed.
;Drive Number: Number automatically assigned by SEP sesam, for a new drive it can be changed.
;Drive Name: Logical identifier for drive (optional).
;Drive Name: Logical identifier for drive (optional).
Line 297: Line 221:
;Drive No. in loader: It will be set automatically by saving. If needed, it can be set up here. </translate>
;Drive No. in loader: It will be set automatically by saving. If needed, it can be set up here. </translate>
<translate>
<translate>
<!--T:170-->
;Device Server: The host which is connected with the drive.
;Device Server: The host which is connected with the drive.
;Drive Group: Selection of drive group (since every drive must be assigned to a drive group).
;Drive Group: Selection of drive group (since every drive must be assigned to a drive group).
Line 307: Line 230:
;Encryption capable:
;Encryption capable:


<!--T:171-->
A special case are the virtual drives already mentioned above where no physical drives and moveable media (tapes) exist.
A special case are the virtual drives already mentioned above where no physical drives and moveable media (tapes) exist.


<!--T:172-->
'''Type DISK_HARD'''  
'''Type DISK_HARD'''  
Configuration by selection of drive type DISK_HARD and loader 0 .
Configuration by selection of drive type DISK_HARD and loader 0 .
The device is not editable, it is automatically '''disk''' + drive-number.
The device is not editable, it is automatically '''disk''' + drive-number.


<!--T:173-->
The assignment of directories to virtual media is performed through the media-pool which also specifies the maximum
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.
capacity (in KB) for this pool. This later prevents the unsupervised writing to the disk.


<!--T:174-->
'''Type DISK_CHNG'''  
'''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.
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.


===={{anchor|drive action}}Drive Action==== <!--T:175-->
===={{anchor|drive action}}Drive Action====


<!--T:176-->
Selecting this option from the drive-group window shows following screen.
Selecting this option from the drive-group window shows following screen.


<!--T:177-->
[[Image:Drives_drive_action.png|center]]
[[Image:Drives_drive_action.png|center]]


<!--T:178-->
From the GUI, the following 7 actions may be taken for the selected drive. The execution and progress of the
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.
activity is shown in the lower, cyclically updated information window.


<!--T:179-->
;Get label : shows the label of media, currently in the drive
;Get label : shows the label of media, currently in the drive
;Mount media : the MOUNT Status is reserved for the tape media to prevent unnecessary spooling.
;Mount media : the MOUNT Status is reserved for the tape media to prevent unnecessary spooling.
Line 341: Line 256:
;Unload media : cancels the MOUNT Status and ejects the cassette
;Unload media : cancels the MOUNT Status and ejects the cassette


<!--T:180-->
'''CAUTION'''  
'''CAUTION'''  
After manual changes to the drive ( tapes removal or insertion), the drive must be dismounted.
After manual changes to the drive ( tapes removal or insertion), the drive must be dismounted.


<!--T:181-->
'''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 ).
'''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 ).


<!--T:182-->
Release Drive  
Release Drive  
     All activities will be halted  
     All activities will be halted  

Revision as of 15:23, 17 October 2017


<<<Back
Loaders
User Manual
Next>>>
Media pools

Drives

Drives are devices used for data storage that read from or write data to media. They are either local drives, connected to the SEP sesam Server, or remote drives, connected to another computer on the local or wide area network. These can be tape devices with removable tape cartridges or disk-based storage devices. Remote drives enable the storage devices, which are used by SEP sesam, to be distributed over WAN.

Shared drives

SEP sesam provides dynamic drive sharing option in SAN environments. Note that a proper SEP sesam SAN Dynamic Drive Sharing (SDD) license is required for each drive you intend to share. For more information, see List of Licenses.

Drive sharing option allows the drives to be available to multiple Remote Device Servers (RDS) at any time. A physical drive can be seen by any number of RDSs and can be used by relevant systems to store data. Shared drives can be defined by a unique drive designation. This means that multiple drives are labeled with the same device identifier, which is specific SCSI designation, for example: /dev/nst0 (Linux ), Tape0 (Windows). While executing SEP sesam tasks, such as backup and restore, the drives are being shared by multiple servers based on a shared timing.

SEP Tip.png Tip
It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured tape devices you should enable persistent naming and check their configuration to avoid errors in SEP sesam operation. For details, see Enabling persistent naming for tape devices.

Drive groups

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 autoloaders 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.

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.

Drives overview.png

Button properties

Here the parameters of the selected element are shown and changed if necessary (Group or Drive).

New Group

The button New Group is used to configure a new group.

Drives new drive group.png
Name
An arbitrary name of the drive group
  • Please select a description/name that is easily recognizable by all administrators, support personnel and users. This can and should be part of a general design that can be referred to and expanded at any time.
Description
additional information for the user
  • e.g. Input of the loader's location and the relevant employee contact for assistance.

New Drive

Here the new drives are configured. Each drive must be assigned to a drive group; the drive group must have been previously created.

Drives new drive.png

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.

Configuration Example

Drive 1 and 2 are local drives

Drive 11 through 21 are remote Devices at various locations

Drive 1:

 08:00:18  I001-START   Start on Drive 1 finished
 08:00:18  Retrieves BACKUP Tasks from the SEPuler Event Calender

Drive 2:

 09:08:58  Automatic Backup TEST_BACKUP finished
 09:10:39   

Drive 11:

 09:05:57  Automatic Backup TEST_BACKUP finished
 09:07:37   

Drive 21:

 10:32:47  Automatic Backup elektrik_orcl finished
 10:34:54   


In the event an expansion of one drive at location 1, Drive 12 will entered into the backup scheme.

Drive Name

   Freely selected or specified and if it is a shared drive within a SAN it must be the same for all client shared drives
   e.g. SAN-Drive-LUN-0. 

Loader

   This specifies whether the drive is controlled by a loader or not. 
   Loaders configured allowed as devices within SEP sesam appear in the drop-down menu. 
   'No Loader' simply means that it is a single drive and must be handled manually. 

Drive Type

   Choice of drive technology (e.g. DISK, DISK_HARD, DLT, LTO,...).
   You can specify DISK_HARD und DISK_CHNG for hard disk drives. 
   Hard drives in NAS or DAS architecture are treated as DISK_HARD. 

DISK_CHNG is used for all backups to USP hard drives removable drives.

   Using this configuration, e.g. a daily update is made and a new, initiated drive is used for backup. 
   (This is similar to a tape drive with daily inserted tape). 

Attention

The utilization of Removable Devices requires the insertion of the device path (Direct Option)!

Tape Server

   In the field Tape Server you need to enter the backup server or remote device server where the drive is located/connected.
   The Drop down Menu shows everything on the configured clients.
   The selection of the local/remote server either creates a local or remote device. 

Drive Group

   Every drive must be assigned to a drive group;
   the assignment of multiple drives to a similar Drive Type is possible,
   e.g. in the same auto loader with multiple drives.

Drive Number in Loader

   shows the sequence within in the Loader how drives will be used.
   The order is dependent upon the hardware vendor's numbering scheme for all installed drives.
   If the order is entered improperly SEP will not be able to access the correct drive or cassette.
   If there is only one drive in the Loader, '0' is automatically entered. 

Device (non-rewinding)

   Device Label, where the device has been configured.
   For Tape Drives the Operating System specific SCSI designation is selected, e.g. /dev/nst0 or Tape0 (see the description below) 

Info

   Status log for the drive. e.g. Read/Write Error 

Operating System Specific Designation

  • Windows:

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)".

  • Linux:

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

Path for Removable media

       for Type DISK_CHNG you just enter the Device Description/Label, e.g. /dev/media/USB or F:

Block Size

       for Type DISK_CHNG you need to enter the Block Size

SMS Number

       Shows the internally assigned SMS Number 

SMS Channel

       Sets the maximum number of parallel streams that can be used during backup to the backup drive


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

SEP sesam ONE Server License

The system has a drive and a tape drive connected. Multiple backup tasks will be started simultaneously for execution after the close of business.

Result: The backups one after another to either the disk or tape drive, whichever has been specified. Only one backup stream is active.

SEP sesam Standard Server License

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.

Result: Backups run parallel to either one of the drives or to both using 5 data streams depending on the desired backup path scheme.

   Either one or both tape drives can be used simultaneously but only 5 data streams are open for data transfer. 

SEP sesam Advanced Server License

The system has one disk drive and three tape drives available for backup. The SMS channel is set to 8 data streams per tape drive. Multiple tasks (e.g.) are started after close of business and within multiple Task Groups.

Result: The backups run in parallel on all three drives.

   There is no limitation to the number of data streams that may be used or the SMS channels.
   The configuration and number of streams used for backup is dependent upon the system capability and throughput (pipe) available. 

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 ).

Drives drive number.png
Drive Number
Number automatically assigned by SEP sesam, for a new drive it can be changed.
Drive Name
Logical identifier for drive (optional).
Drive Type
Selection of type
  • Tape drives (LTO, DLT, SLR etc.)
  • If it is planned to use the drive in a virtual disk storage, select DISK_STORE. The data will be stored in a SEP sesam Data Store.
  • If the drive is a removable media, select DISK_CHNG.
  • DISK_HARD is the old style of backup to disk and should not be used anymore.
Loader
The drive belongs to this loader. If it is a single tape drive, select No loader option.
Drive No. in loader
It will be set automatically by saving. If needed, it can be set up here.
Device Server
The host which is connected with the drive.
Drive Group
Selection of drive group (since every drive must be assigned to a drive group).
Device
SCSI-Identification, under which the device is configured at system level, example: Linux (/dev/nst0), Windows (Tape0).
Path (for data store/removable media)
Operating system's on wich the SEP sesam can connect the device.
Tape in drive
If a medium is loaded into the drive, the SEP sesam label will be displayed.
Info
If indicated the messages from the drive hardware will be displayed.
Max. channels
The count of simultaneous backups that can be operated through this drives.
Encryption capable

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.

Drive Action

Selecting this option from the drive-group window shows following screen.

Drives drive action.png

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.

Get label
shows the label of media, currently in the drive
Mount media
the MOUNT Status is reserved for the tape media to prevent unnecessary spooling.
Dismount media
cancels the MOUNT Status.
Unload media
cancels the MOUNT Status and ejects the cassette

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

   All activities will be halted 

Reconfigure Drive

   Used after a change in the drive parameters 

Release Drive Group

   All jobs running on the Drive Group are canceled.