Source:Enabling persistent naming for tape devices: Difference between revisions
mNo edit summary |
(Added What's next and links.) |
||
| Line 7: | Line 7: | ||
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;" | ||
| rowspan="2" style="padding:0px 10px 0px;" | | | rowspan="2" style="padding:0px 10px 0px;" | | ||
[[File:SEP_next.png|45px|link= | [[File:SEP_next.png|45px|link=Configuring_Loaders_and_Drives|Configuring Loaders and Drives]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
What is next: [[Special:MyLanguage/Configuring_Loaders_and_Drives|Configuring Loaders and Drives]] | |||
|} | |} | ||
| Line 23: | Line 23: | ||
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]] | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]] | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
Problems? Check | Problems? Check [[Special:MyLanguage/Troubleshooting_Guide#Tape_and_tape_devices_issues|Troubleshooting Tape and Tape Devices Issues]]. | ||
|} | |} | ||
| Line 32: | Line 32: | ||
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | | ||
If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Archive:How_to_set_up_a_loader|previous document version]]. | If you are using an older SEP sesam version, refer to [[Special:MyLanguage/Archive:How_to_set_up_a_loader|previous document version]]. | ||
|}</div></noinclude> | |}</div></noinclude>Persistent naming or binding is an option that enforces file names for loaders and tape drives, thus making them persist across reboots of the operating system. Without this feature the 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, such as unloading incorrect drives, read/open errors, volume errors, lost connections ... | ||
Persistent naming or binding is an option that enforces file names for loaders and tape drives, thus making them persist across reboots of the operating system. Without this feature the 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, such as unloading incorrect drives, read/open errors, volume errors, lost connections ... | |||
Persistent naming means using symbolic names for loaders, tape drives in autoloaders and tape libraries, as well as for single tape drives. These names stay unique during server reboots, regardless of the order in which the operating system discovers the tape hardware. For example, while ''Tape0'' is a logical name that could change during system restart, the persistent name ''Tape2147483644'' is unique and will not change. | Persistent naming means using symbolic names for loaders, tape drives in autoloaders and tape libraries, as well as for single tape drives. These names stay unique during server reboots, regardless of the order in which the operating system discovers the tape hardware. For example, while ''Tape0'' is a logical name that could change during system restart, the persistent name ''Tape2147483644'' is unique and will not change. | ||
Configuration of persistent naming depends on the used driver. | Configuration of persistent naming depends on the used driver. Once OS is configured for persistence naming, update SEP sesam configuration with the help of [[Special:MyLanguage/Configuring_Loaders_and_Drives#slu topology|<tt>slu topology</tt>]]. | ||
{{note|Persistent naming is not part of SEP sesam as each hardware vendor handles it differently. If you need any assistance, consult your respective OS and hardware vendor support. The following information are only for reference and are not meant to replace the official vendor documentation.}} | {{note|Persistent naming is not part of SEP sesam as each hardware vendor handles it differently. If you need any assistance, consult your respective OS and hardware vendor support. The following information are only for reference and are not meant to replace the official vendor documentation.}} | ||
| Line 64: | Line 63: | ||
;HP LTO drivers:For HP LTO drivers, follow the procedure as provided by [https://www.data-protector.org/wordpress/2013/05/persistent-binding-hp-lto-tape-drives-windows/ data-protector.org]: | ;HP LTO drivers:For HP LTO drivers, follow the procedure as provided by [https://www.data-protector.org/wordpress/2013/05/persistent-binding-hp-lto-tape-drives-windows/ data-protector.org]: | ||
<ol><li>Make sure that you have installed the required HP tape drivers.</li> | <ol><li>Make sure that you have installed the required HP tape drivers.</li> | ||
<li>Copy the following code and insert it into text editor, then save the content as <tt>.reg</tt> file.</li> | <li>Copy the following code and insert it into text editor, then save the content as <tt>.reg</tt> file.</li> | ||
| Line 78: | Line 76: | ||
"Persistence"=dword:00000001 | "Persistence"=dword:00000001 | ||
<li>Execute the <tt>.reg</tt> file and restart the system.</li></ol> | <li>Execute the <tt>.reg</tt> file and restart the system.</li></ol> | ||
====Configuring persistent naming on Linux==== | ====Configuring persistent naming on Linux==== | ||
Device persistence on Linux is based on preconfigured <tt>udev</tt> rules. These rules create aliases in the device filesystem in <tt>/dev/tape</tt>. The name of the alias is not fixed, but it will remain consistent across reboots on different hosts. For more details, refer to your hardware manufacturer documentation; for example, IBM article [http://www-01.ibm.com/support/docview.wss?uid=swg21664258 Configuring drives with persistent naming for IBM devices on Linux]. | Device persistence on Linux is based on preconfigured <tt>udev</tt> rules. These rules create aliases in the device filesystem in <tt>/dev/tape</tt>. The name of the alias is not fixed, but it will remain consistent across reboots on different hosts. For more details, refer to your hardware manufacturer documentation; for example, IBM article [http://www-01.ibm.com/support/docview.wss?uid=swg21664258 Configuring drives with persistent naming for IBM devices on Linux].<noinclude> | ||
==What is next?== | |||
Enabling persistent naming is only one step in a sequence for (re-)configuring storage hardware. For full procedure, including using <tt>slu topology</tt> for identifying the name of the tape hardware and re-configuring loaders and drives, refer to [[Special:MyLanguage/Configuring_Loaders_and_Drives|Configuring Loaders and Drives]]. | |||
==See also== | |||
[[Special:MyLanguage/ | [[Special:MyLanguage/FAQ#storage_etc|FAQ about storage, devices & media management]] – [[Special:MyLanguage/Media_pools_4.4|Media Pools]] – [[Special:MyLanguage/Media_4.4|Media]] – [[Special:MyLanguage/LTO_Encryption|LTO Encryption]] – [[Special:MyLanguage/Troubleshooting_Guide#Tape_and_tape_devices_issues|Troubleshooting Tape and Tape Devices Issues]]</noinclude> | ||
Revision as of 11:23, 19 October 2017
Overview
|
|
What is next: Configuring Loaders and Drives |
|
|
|
|
Problems? Check Troubleshooting Tape and Tape Devices Issues. |
|
|
If you are using an older SEP sesam version, refer to previous document version. |
Persistent naming or binding is an option that enforces file names for loaders and tape drives, thus making them persist across reboots of the operating system. Without this feature the 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, such as unloading incorrect drives, read/open errors, volume errors, lost connections ...
Persistent naming means using symbolic names for loaders, tape drives in autoloaders and tape libraries, as well as for single tape drives. These names stay unique during server reboots, regardless of the order in which the operating system discovers the tape hardware. For example, while Tape0 is a logical name that could change during system restart, the persistent name Tape2147483644 is unique and will not change.
Configuration of persistent naming depends on the used driver. Once OS is configured for persistence naming, update SEP sesam configuration with the help of slu topology.
|
Note |
| Persistent naming is not part of SEP sesam as each hardware vendor handles it differently. If you need any assistance, consult your respective OS and hardware vendor support. The following information are only for reference and are not meant to replace the official vendor documentation. |
Configuring persistent naming on Windows
To enable persistent bindings of symbolic tape and library names, you have to modify the registry key. Make sure that you have a valid SEP sesam and operating system backup before proceeding!
- Standard Windows drivers
- For standard Windows drivers, proceed as follows:
- Open Registry Editor: use Start and type regedit.
- Locate and select the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Tape
- From the Edit menu, select New and then DWORD Value.
- Type Persistence and then press ENTER.
- Right-click the Persistence registry entry, then click Modify.
- Type 1 in the Value data box, and then click OK.
- Close Registry Editor and restart the computer.
When you set the Persistence registry entry to 1, symbolic names become persistent. For example, if your tape drive has the name \\.\\tape1, this name is reserved for use by that device even after your server reboots.
- IBM drivers
- For IBM drivers, proceed as follows:
- Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ibmtp2k<x> where the value <x> in ibmtp2k specifies the Windows Server version, for example, ibmtp2k8 for Windows Server 2008, ibmtp2k12 for Windows 2012, and ibmtp2k16 for Windows 2016, respectively.
- Add DWORD:PersistentNaming=1.
- Close Registry Editor and ensure that AutoRun is set to 0 for the driver prior to rebooting; for details, see official Microsoft documentation, e.g., Windows Server 2003 cannot perform backup jobs to tape devices on a storage area network or refer to the article Disable Autorun/Autoplay.
- Restart the computer.
For more details, see IBM article Configuring drives with persistent naming with IBM devices on Windows.
- HP LTO drivers
- For HP LTO drivers, follow the procedure as provided by data-protector.org:
- Make sure that you have installed the required HP tape drivers.
- Copy the following code and insert it into text editor, then save the content as .reg file.
- Tape drives:
- Changer:
- Execute the .reg file and restart the system.
Configuring persistent naming on Linux
Device persistence on Linux is based on preconfigured udev rules. These rules create aliases in the device filesystem in /dev/tape. The name of the alias is not fixed, but it will remain consistent across reboots on different hosts. For more details, refer to your hardware manufacturer documentation; for example, IBM article Configuring drives with persistent naming for IBM devices on Linux.
What is next?
Enabling persistent naming is only one step in a sequence for (re-)configuring storage hardware. For full procedure, including using slu topology for identifying the name of the tape hardware and re-configuring loaders and drives, refer to Configuring Loaders and Drives.
See also
FAQ about storage, devices & media management – Media Pools – Media – LTO Encryption – Troubleshooting Tape and Tape Devices Issues