Archive:Drives 4.4: Difference between revisions

From SEPsesam
(Update in progress.)
(Update/rewrite in progress.)
(One intermediate revision by the same user not shown)
Line 7: Line 7:


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.
{{tip|It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured tape devices you should check their configuration and in some cases enable persistent naming 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|shared drives}}Shared drives====   
===={{anchor|shared drives}}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 [[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#media_manager|List of Licenses]].  


''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.
''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.
{{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====
===={{anchor|drive_group}}Drive groups====
SEP sesam enforces you to organize drives into different groups. This is useful when several drives are used on one SEP sesam Server; if the drives are of the same type, it is recommended to bind them into one drive group and perform a backup using this group. SEP sesam then selects which drive to use for running the backup task. A backup is performed automatically on a drive that is currently free. In the event of a drive failure, each backup is automatically executed only on the available or operable drives. This is particularly true in cases of large autoloaders with multiple drives.
SEP sesam enforces you to organize drives into different groups. Grouping the drives of the same type into one group facilitates and optimizes backup operation. SEP sesam selects which drive from the group will be used for running a backup job. A backup is performed automatically on the drive that is currently free. In the event of a drive failure, each backup is automatically executed on other available drives.
 
[[Image:Drives_overview.png|center]]
 
===={{anchor|button properties}}Button properties====
 
Here the parameters of the selected element are shown and changed if necessary (Group or Drive).
 
===={{anchor|new group}}New Group====
 
The button '''New Group''' is used to configure a new group.
 
[[Image:Drives_new_drive_group.png|center]]
 
;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.
 
===={{anchor|new drive}}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.
 
[[Image:Drives_new_drive.png|center]]
 
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:  
Even in case you have only one standalone drive, you have to create a drive group first and attach a drive to it. The drive group is directly connected to the media pool. By connecting a media pool to the drive group, you specify ''whereto'' SEP sesam saves the backup. Later in the process when configuring a backup, you select a target media pool (which is already connected to the drive group) to which the data will be backed up by [[Special:MyLanguage/Creating_a_Backup_Event|creating a backup event]] (where the connected drive group is determined automatically by media pool selection). For details on backup configuration, see [[Special:MyLanguage/Standard_Backup_Procedure|Standard Backup Procedure]].


You can use the same command to determine the necessary device files:
[[Image:Drives_overview.png|center|link=]]
<br clear=all>
===={{anchor|new_group}}New Group====


<SESAM_BIN>/sesam/slu scan
The option '''New Group''' is used to configure a new group.


Example output:
[[Image:Drives_new_drive_group.png|center|link=]]
<br clear=all>


ID=0000 other:   ATA      ST380013AS
;Name : A meaningful name for the new drive group which is easily recognizable by administrators, support personnel, and users. This should be part of a general design that can be referred to and expanded at any time.
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).
;Description : Additional information for the user, e.g., input of the loader's location and the relevant employee contact for assistance.


Disk Type are automatically entered with the disk{Drive Number} (see below).
===={{anchor|new_drive}}New Drive==== 


Properties - Options
The option '''New Drive''' is used to configure a new drive. Each drive must be assigned to a drive group, therefore a drive group must be created first.


Path for Removable media
[[Image:Drives_new_drive.png|center|link=]]
        for Type DISK_CHNG you just enter the Device Description/Label, e.g. /dev/media/USB or F:
<br clear=all>
Block Size 
In the ''New Drive'' window, the following fields are available:
        for Type DISK_CHNG you need to enter the Block Size
<ul><li>'''''Drive Number''''': The number is automatically assigned by SEP sesam and determines internal number of the drive.</li>
 
<li>'''''Drive Name''''': Optional description, e.g., logical identifier of a drive. In case of a shared drive within SAN, the name must be the same for all client shared drives, e.g., ''SAN-Drive-LUN-0''. </li>
SMS Number  
<li>'''''Drive Type''''': Depending on storage type, the relevant drive type must be selected from the drop-down list.</li>
        Shows the internally assigned SMS Number
<ul><li>For tape drives, select the relevant tape type (LTO, DLT, SLR etc.).</li>
SMS Channel 
<li>If you plan to use the drive in the virtual disk storage, select '''DISK_STORE'''. The data will be stored to SEP sesam [[Special:MyLanguage/SEP sesam Glossary#data_store|data store]].</li>
        Sets the maximum number of parallel streams that can be used during backup to the backup drive
<li>If the drive is removable media, select '''DISK_CHNG'''.</li></ul></li>
 
<li>'''''Loader''''': Available options are ''No loader'', ''0'' and ''1''. If the drive belongs to the loader, select '''1'''. If it is a single tape drive, select '''No loader''' option. Number '''0''' defines the virtual loader. </li>
 
<li>'''''Drive No. in loader''''': Determines how the drives are used within the loader. It is set automatically by saving the new drive configuration. It can also be set manually, but it is strongly advised not to; this order depends on the hardware vendor's numbering scheme for all installed drives. If the order is entered incorrectly, SEP sesam will not be able to access the correct drive.</li>
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.)
<li>'''''Device Server''''': The name of the server or RDS to which the drive is connected. The drop-down list displays all available hosts.</li>
 
<li>'''''Drive Group''''': The relevant drive group have to be selected from the drop-down list of all available drive groups.</li>
Example of SMS Stream Limitation
<li>'''''Device (non-rewinding)''''': Operating system specific SCSI designation for the device, for example: on Linux (<tt>/dev/nst0</tt>), on Windows (<tt>Tape0</tt>). In the drive is installed properly, you can determine its SCSI ID by using a SCSI loader utility <tt>slu topology</tt> which shows information about the loaders and drives connected to the system as well as their relation.</li>
 
To list all attached SCSI devices, run <tt>slu topology</tt>:
SEP sesam ONE Server License
  <SESAM_BIN>/sesam/slu topology
 
For details on its usage, see [[Special:MyLanguage/Using slu topology for detecting devices|Using slu topology for detecting devices]].
The system has a drive and a tape drive connected. Multiple backup tasks will be started simultaneously for execution after the close of business.
{{tip|It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured backup devices you should check their configuration by using <tt>slu topology</tt>. SCSI addresses may be changed during reboots, especially in environments with several tape libraries attached to a server, and the operating system might mix the SCSI addresses between different loaders and library tape drives. Consequently, SEP sesam may have problems accessing devices. In such cases, consider enabling persistent naming. For details, see [[Special:MyLanguage/Configuring Loaders and Drives|Configuring Loaders and Drives]].}}</li>
 
<li>'''''Path''''': Applicable only for data store and removable media; specifies the path for connecting the device, e.g., ''/dev/media/USB'' or simply ''F:''. </li>
Result: The backups one after another to either the disk or tape drive, whichever has been specified. Only one backup stream is active.
<li>'''''Tape in drive''''': If a medium is loaded into the drive, SEP sesam label is displayed.</li>
 
<li>'''''Information''''': If indicated, the messages from the drive hardware are displayed.</li>
SEP sesam Standard Server License
<li>'''''Max. channels''''': The number of parallel streams that can be used during backup to the backup drive. The number of data streams available for backup depends on [[Special:MyLanguage/SEP_sesam_Glossary#license|license]]. </li>
 
For example, with ''SEP sesam ONE Server'' license only one backup stream is active. Multiple backup tasks are scheduled to start simultaneously, but will be performed one after another because of only one backup stream. In another example, ''SEP sesam Standard Server'' license is purchased for the environment that has has one disk drive and two tape drives attached. The SMS channels are connected to all drives. Multiple backup jobs (e.g., 10) are scheduled to start simultaneously. Backups may run in parallel to either one or both tape drives, but only 5 data streams are open for data transfer. For details, see [[Special:MyLanguage/Licensing#srv_comparison|Licensing: ''SEP sesam Server comparison'']].
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.
<li>'''''Encryption capable''''': For already configured drives, it shows whether they are encryption capable. The field is shaded for new drives. Note that SEP sesam provides native support for managing LTO-based encryption; the LTO encryption of tape drives can be enabled on a media pool level. For details, see [[Special:MyLanguage/LTO_Encryption|LTO Encryption]].</li>
 
<li>Click '''OK''' to configure the drive.</li></ul>
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 ).


{{note|With some drive types, such as ''DISK_CHNG'', the name is automatically assigned based on ''disk + drive number''.}}
Here is an example of an already configured drive.
[[Image:Drives_drive_number.png|center]]
[[Image:Drives_drive_number.png|center]]
<br clear=all>


;Drive Number: Number automatically assigned by SEP sesam, for a new drive it can be changed.
===={{anchor|drive action}}Drive action====   
;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. </translate>
<translate>
;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 (<tt>/dev/nst0</tt>), Windows (<tt>Tape0</tt>).
;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.
 
===={{anchor|drive action}}Drive Action====   
 
Selecting this option from the drive-group window shows following screen.
 
[[Image:Drives_drive_action.png|center]]
 
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'''  
In the ''Drives'' content window selecting a specific drive and then  '''Drive action''' from the menu, allows to manage the specific drive and media in the drive.
After manual changes to the drive ( tapes removal or insertion), the drive must be dismounted.
[[Image:Drives_drive_action.png|center|link=]]
<br clear=all>


'''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 ).
;Get label : Shows the label of the medium in the drive.
;Mount media : Mount is a special reservation of the tape media to prevent unnecessary spooling.
;Dismount media : Cancels the ''mount'' status.
;Dismount and unload media : Cancels the ''mount'' status and unloads the tape.
{{warning|If you have manually removed or inserted the tape from/into the drive, the drive must be dismounted. ''Dismount and unload media'' should not be confused with unloading from an auto-loader. While the loader can re-acquire the tape and re-enter it (option Unload via Loader), this option only means that the tape in the drive will be released and ejected.}}
;Release drive: Cancels all activities that are running on the drive.
;Release drive group:Cancels all jobs that are running on the drives that belong to the respective drive group.


Release Drive
The execution and progress of the activity is shown in the lower, cyclically updated information window.
    All activities will be halted
===={{anchor|properties}}Drive group and drive properties====
Reconfigure Drive 
By double-clicking the ''drive group'' or ''selected drive'', its properties are shown and can be modified.
    Used after a change in the drive parameters
</translate>
Release Drive Group 
    All jobs running on the Drive Group are canceled.</translate>

Revision as of 19:11, 18 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.

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


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.

Drive groups

SEP sesam enforces you to organize drives into different groups. Grouping the drives of the same type into one group facilitates and optimizes backup operation. SEP sesam selects which drive from the group will be used for running a backup job. A backup is performed automatically on the drive that is currently free. In the event of a drive failure, each backup is automatically executed on other available drives.

Even in case you have only one standalone drive, you have to create a drive group first and attach a drive to it. The drive group is directly connected to the media pool. By connecting a media pool to the drive group, you specify whereto SEP sesam saves the backup. Later in the process when configuring a backup, you select a target media pool (which is already connected to the drive group) to which the data will be backed up by creating a backup event (where the connected drive group is determined automatically by media pool selection). For details on backup configuration, see Standard Backup Procedure.

Drives overview.png


New Group

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

Drives new drive group.png


Name
A meaningful name for the new drive group which is easily recognizable by administrators, support personnel, and users. This 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

The option New Drive is used to configure a new drive. Each drive must be assigned to a drive group, therefore a drive group must be created first.

Drives new drive.png


In the New Drive window, the following fields are available:

  • Drive Number: The number is automatically assigned by SEP sesam and determines internal number of the drive.
  • Drive Name: Optional description, e.g., logical identifier of a drive. In case of a shared drive within SAN, the name must be the same for all client shared drives, e.g., SAN-Drive-LUN-0.
  • Drive Type: Depending on storage type, the relevant drive type must be selected from the drop-down list.
    • For tape drives, select the relevant tape type (LTO, DLT, SLR etc.).
    • If you plan to use the drive in the virtual disk storage, select DISK_STORE. The data will be stored to SEP sesam data store.
    • If the drive is removable media, select DISK_CHNG.
  • Loader: Available options are No loader, 0 and 1. If the drive belongs to the loader, select 1. If it is a single tape drive, select No loader option. Number 0 defines the virtual loader.
  • Drive No. in loader: Determines how the drives are used within the loader. It is set automatically by saving the new drive configuration. It can also be set manually, but it is strongly advised not to; this order depends on the hardware vendor's numbering scheme for all installed drives. If the order is entered incorrectly, SEP sesam will not be able to access the correct drive.
  • Device Server: The name of the server or RDS to which the drive is connected. The drop-down list displays all available hosts.
  • Drive Group: The relevant drive group have to be selected from the drop-down list of all available drive groups.
  • Device (non-rewinding): Operating system specific SCSI designation for the device, for example: on Linux (/dev/nst0), on Windows (Tape0). In the drive is installed properly, you can determine its SCSI ID by using a SCSI loader utility slu topology which shows information about the loaders and drives connected to the system as well as their relation.
    • To list all attached SCSI devices, run slu topology: <SESAM_BIN>/sesam/slu topology For details on its usage, see Using slu topology for detecting devices.
    SEP Tip.png Tip
    It is recommended that SEP sesam auto-configures backup devices, but even for the automatically configured backup devices you should check their configuration by using slu topology. SCSI addresses may be changed during reboots, especially in environments with several tape libraries attached to a server, and the operating system might mix the SCSI addresses between different loaders and library tape drives. Consequently, SEP sesam may have problems accessing devices. In such cases, consider enabling persistent naming. For details, see Configuring Loaders and Drives.
  • Path: Applicable only for data store and removable media; specifies the path for connecting the device, e.g., /dev/media/USB or simply F:.
  • Tape in drive: If a medium is loaded into the drive, SEP sesam label is displayed.
  • Information: If indicated, the messages from the drive hardware are displayed.
  • Max. channels: The number of parallel streams that can be used during backup to the backup drive. The number of data streams available for backup depends on license.
    • For example, with SEP sesam ONE Server license only one backup stream is active. Multiple backup tasks are scheduled to start simultaneously, but will be performed one after another because of only one backup stream. In another example, SEP sesam Standard Server license is purchased for the environment that has has one disk drive and two tape drives attached. The SMS channels are connected to all drives. Multiple backup jobs (e.g., 10) are scheduled to start simultaneously. Backups may run in parallel to either one or both tape drives, but only 5 data streams are open for data transfer. For details, see Licensing: SEP sesam Server comparison.
  • Encryption capable: For already configured drives, it shows whether they are encryption capable. The field is shaded for new drives. Note that SEP sesam provides native support for managing LTO-based encryption; the LTO encryption of tape drives can be enabled on a media pool level. For details, see LTO Encryption.
  • Click OK to configure the drive.
Information sign.png Note
With some drive types, such as DISK_CHNG, the name is automatically assigned based on disk + drive number.

Here is an example of an already configured drive.

Drives drive number.png


Drive action

In the Drives content window selecting a specific drive and then Drive action from the menu, allows to manage the specific drive and media in the drive.

Drives drive action.png


Get label
Shows the label of the medium in the drive.
Mount media
Mount is a special reservation of the tape media to prevent unnecessary spooling.
Dismount media
Cancels the mount status.
Dismount and unload media
Cancels the mount status and unloads the tape.
SEP Warning.png Warning
If you have manually removed or inserted the tape from/into the drive, the drive must be dismounted. Dismount and unload media should not be confused with unloading from an auto-loader. While the loader can re-acquire the tape and re-enter it (option Unload via Loader), this option only means that the tape in the drive will be released and ejected.
Release drive
Cancels all activities that are running on the drive.
Release drive group
Cancels all jobs that are running on the drives that belong to the respective drive group.

The execution and progress of the activity is shown in the lower, cyclically updated information window.

Drive group and drive properties

By double-clicking the drive group or selected drive, its properties are shown and can be modified.

Retrieved from "https://wiki.sep.de/wiki/index.php?title=Archive:Drives_4.4&oldid=48733"