Source:Troubleshooting Tape and Tape Devices: Difference between revisions

Revision as of 12:10, 28 July 2020

Other languages:

Deutsch
English

Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check documentation archive.

Tape and tape devices issues

Additional resources

Problem with tape drives

Problem

There are problems with LTO tape drives which repeatedly request cleaning tape. Additionally, backups fail with I/O errors.

⇒ Solution

There are two possible causes for this:

SEP sesam has problems communicating properly with tape devices if hardware vendor's tape diagnostic tools are still installed after the tape read/write diagnostic test is successful. To stop the tape drives from repeatedly issuing the cleaning request and ensure that backups successfully complete, remove the tape diagnostic tools immediately after the diagnostic tests are complete. For example, there are some problems with different tape drives LTO5 and LTO7. In our example, you will disable or remove the following components:

Disable HPE Version Control Agent.
Disable all tape agents for HPE Insight Management Agents as shown below.

Uninstall HP Library and Tape Tools (L&TT) from your server by using the Add/Remove Program in the Window's Control Panel.

Similar issues may be caused by common hardware-related problems. Refer to your hardware vendor documentation for details about hardware configuration and troubleshooting.

Restore fails due to a missing block that was not written to tape, but no error is generated during backup

Problem

(Applies only to Windows SEP sesam Server or RDS, ≤ SEP sesam Beefalo V2) When backing up to tape, a data block is not written to tape when the segment size is reached at End of Media (EOM), therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.

⇒ Solution:

Detect whether your tapes are affected by following the procedure How to detect affected savesets below.
Update your Windows SEP sesam Server with a fix for Beefalo V2. If your tape device is attached to a Windows RDS, you have to install the update to the respective RDS.

How to detect affected savesets

The following steps must be executed on your SEP sesam Server.

Check the path behind the variable gv_rw_lis in sm.ini to see if your LIS folder's destination was changed. Example with modified LIS folder – set to D:\SEPsesam\var\lis\:
Open the command prompt ('Windows Command Processor' or Linux 'Terminal') and issue the following commands. Change to the directory of your LIS folder according to sm.ini gv_rw_lis=... :
- Windows (default): C:\ProgramData\SEPsesam\var\lis
- Linux (default): /var/opt/sesam/var/lis
If the command retrieves some lines then inspect the related sgm files. In the following example, the third line (marked in red) shows an occurrence of a lost block.

1:146212528704:0:MP_File_Full00010:1

0

:1

@@ Line 1: / Line 1: @@
 __FORCETOC__
-<noinclude>{{Copyright SEP AG en}}
-{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></noinclude>
+<translate>
-== Tape and tape devices issues ==
+<!--T:1-->
+<noinclude><languages />{{Copyright SEP AG en}}
+<!--T:2-->
+{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|documentation archive]]}}<br /></noinclude></translate>
+<translate>== Tape and tape devices issues == <!--T:3--></translate>
 <noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>
-Additional resources</b></center>
+<translate>
+<!--T:4-->
+Additional resources</translate></b></center>
 {|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 | rowspan="2" style="padding:0px 10px 0px;" |
-[[File:SEP_next.png|45px|link=Special:MyLanguage/Managing_Devices_and_Media]]
+<translate>
+<!--T:5-->
+[[File:SEP_next.png|45px|link=Special:MyLanguage/Managing_Devices_and_Media]]</translate>
 | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
-See also: [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]
+<translate><!--T:6--> See also: [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</translate>
 |}
@@ Line 17: / Line 25: @@
 [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]
 | style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |
-Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.
+<translate><!--T:31--> Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.</translate>
 |}
@@ Line 24: / Line 32: @@
 [[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;" |
-Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].
+<translate><!--T:7--> Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate>
 |}
 </div></noinclude>
-=== Problem with tape drives ===
+<translate>=== Problem with tape drives === <!--T:8--></translate>
+'''<translate><!--T:9--> Problem</translate>'''
+*<translate><!--T:10--> There are problems with LTO tape drives which repeatedly request cleaning tape. Additionally, backups fail with I/O errors. </translate>
+&rArr; '''<translate><!--T:11--> Solution</translate>'''
-'''Problem'''
+<translate>
-*There are problems with LTO tape drives which repeatedly request cleaning tape. Additionally, backups fail with I/O errors.
+<!--T:12-->
-&rArr; '''Solution'''
+There are two possible causes for this:</translate>
-There are two possible causes for this:
+*<translate><!--T:13--> SEP sesam has problems communicating properly with tape devices if hardware vendor's '''tape diagnostic tools''' are still installed after the tape read/write diagnostic test is successful. To stop the tape drives from repeatedly issuing the cleaning request and ensure that backups successfully complete, remove the tape diagnostic tools immediately after the diagnostic tests are complete. For example, there are some problems with different tape drives LTO5 and LTO7. In our example, you will disable or remove the following components:</translate>
-*SEP sesam has problems communicating properly with tape devices if hardware vendor's '''tape diagnostic tools''' are still installed after the tape read/write diagnostic test is successful. To stop the tape drives from repeatedly issuing the cleaning request and ensure that backups successfully complete, remove the tape diagnostic tools immediately after the diagnostic tests are complete. For example, there are some problems with different tape drives LTO5 and LTO7. In our example, you will disable or remove the following components:
-<ol><li>Disable HPE Version Control Agent.</li>
-<li>Disable all tape agents for HPE Insight Management Agents as shown below.</li>
-[[image:HPE_Insight-disable_tape_agent.jpg|link=]]
-<li>Uninstall HP Library and Tape Tools (L&TT) from your server by using the ''Add/Remove Program'' in the Window's Control Panel.</li></ol>
-*Similar issues may be caused by '''common hardware-related problems'''. Refer to your hardware vendor documentation for details about hardware configuration and troubleshooting.
-==={{anchor|27422}} Restore fails due to a missing block that was not written to tape, but no error is generated during backup ===
+<ol><li><translate><!--T:14--> Disable HPE Version Control Agent.</translate></li>
+<li><translate><!--T:15--> Disable all tape agents for HPE Insight Management Agents as shown below.</translate></li>
+<translate><!--T:16--> [[image:HPE_Insight-disable_tape_agent.jpg|link=]]</translate>
+<br clear=all>
+<li><translate><!--T:17--> Uninstall HP Library and Tape Tools (L&TT) from your server by using the ''Add/Remove Program'' in the Window's Control Panel.</translate></li></ol>
-'''Problem'''
+*<translate><!--T:18--> Similar issues may be caused by '''common hardware-related problems'''. Refer to your hardware vendor documentation for details about hardware configuration and troubleshooting.</translate>
-*(''Applies only to Windows'', [[Release_Notes_4.4.3_Beefalo_V2|SEP sesam Beefalo V2]]) When backing up to tape, a data block is not written to tape when the segment size is reached at EOM, therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.
-&rArr; '''Solution''': Detect whether you tapes are affected by following the procedure [[Special:MyLanguage/Tape_and_Tape_Devices_Troubleshooting|''How to detect affected savesets'']] below and install a patch for Beefalo V2. Make sure that:
+==={{anchor|27422}} <translate><!--T:19--> Restore fails due to a missing block that was not written to tape, but no error is generated during backup</translate> ===
-<ul><li>Check <tt>gv_rw_lis</tt> in <tt>sm.ini</tt> to see if your LIS folder destination was changed. Example:</li>
+'''<translate><!--T:20--> Problem</translate>'''
+*<translate><!--T:21--> (''Applies only to Windows SEP sesam Server or RDS'', [[Release_Notes_4.4.3_Beefalo_V2|≤ SEP sesam Beefalo V2]]) When backing up to tape, a data block is not written to tape when the segment size is reached at End of Media (EOM), therefore a restore of data referencing this block is not possible. While a Path Archive can still be restored until EOM is reached, a complete restore or migration will fail.</translate>
+&rArr; '''<translate><!--T:22--> Solution</translate>''':
+<ol><li><translate><!--T:23--> Detect whether your tapes are affected by following the procedure [[Tape_and_Tape_Devices_Troubleshooting#detect_error_tape|''How to detect affected savesets'']] below.</translate>
+<li><translate><!--T:25--> Update your Windows SEP sesam Server with a fix for Beefalo V2. If your tape device is attached to a Windows RDS, you have to install the update to the respective RDS.</translate></li></ol>
+===={{anchor|detect_error_tape}} ''<translate><!--T:26--> How to detect affected savesets</translate>'' ====
+<translate><!--T:32--> The following steps must be executed on your SEP sesam Server. </translate>
+<ol><li><translate><!--T:24--> Check the path behind the variable <tt>gv_rw_lis</tt> in <tt>sm.ini</tt> to see if your LIS folder's destination was changed. Example with modified LIS folder – set to {{path|D:\SEPsesam\var\lis\}}:</translate></li>
   [PATHES]
   gv_rw_lis=D:\SEPsesam\var\lis\
-<li>If your tape device is attached to a Windows RDS, you have to install the update to that RDS.</li></ul>
+<li><translate>
+<!--T:27-->
+Open the command prompt ('Windows Command Processor' or Linux 'Terminal') and issue the following commands. Change to the directory of your LIS folder according to <tt>sm.ini gv_rw_lis=...</tt> :</translate>
-===={{anchor|detect_error_tape}} ''How to detect affected savesets'' ====
+<ul>
+<li>Windows (default): {{path|C:\ProgramData\SEPsesam\var\lis}}</li>
+ cd C:\ProgramData\SEPsesam\var\lis
+ findstr /R /C:"^.*:.*:0:.*:1$" *.sgm
+</li>
-<ol><li>Open the command-line interface and issue the following command in your LIS folder:
+<li>Linux (default): <code>/var/opt/sesam/var/lis</code> </li>
-<ul><li>Linux: <code>/var/opt/sesam/var/lis</code></li>
+ cd /var/opt/sesam/var/lis
   grep "^.*:.*:0:.*:1$" *.sgm
+</ul>
-<li>Windows: {{path|C:\ProgramData\SEPsesam\var\lis}}</li>
+<li><translate><!--T:28--> If the command retrieves some lines then inspect the related <tt>sgm</tt> files. In the following example, the third line (marked in red) shows an occurrence of a lost block.</translate></li>
-  findstr /R /C:"^.*:.*:0:.*:1$" *.sgm
-</li></ul>
-<li>Inspect the log file and determine whether your saveset is corrupted. In the following example, the third line (marked in red) shows the lost block.</li>
 :140479734912:1088:MP_File_Full00001:38956
 :143030262144:1089:MP_File_Full00001:48605
@@ Line 69: / Line 96: @@
 :146212594176:1:MP_File_Full00010:55536
-The third line shows the following: On tape with ID 1: there are 146212528704 bytes written, but then it shows the segment <span style="color:red">0</span> that is not a real segment number but caused by error, ending by <span style="color:red">:1</span> block that is actually lost.
+<translate><!--T:29--> The third line shows the following: On tape with ID 1: there are 146212528704 bytes written, but then it shows the segment <span style="color:red">0</span> that is not a real segment number but caused by error, ending by <span style="color:red">:1</span> block that is actually lost.</translate>
 </ol>
-<noinclude>== See also ==
+<noinclude><translate>==See also == <!--T:30-->
-[[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</noinclude>
+[[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</translate></noinclude>