Source:Troubleshooting Tape and Tape Devices: Difference between revisions

From SEPsesam
m (Implemented comments (EE))
(Inserted translation tags.)
Line 1: Line 1:
__FORCETOC__
__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 ==
<noinclude><languages />{{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>
<translate>== Tape and tape devices issues ==</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>
<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>
Additional resources</translate></b></center>
{|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=Special:MyLanguage/Managing_Devices_and_Media]]
<translate>
[[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;" |  
| 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>See also: [[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</translate>
|}
|}


Line 24: Line 28:
[[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;" |  
Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].
<translate>Other problems? Check the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate>
|}
|}
</div></noinclude>
</div></noinclude>
=== Problem with tape drives ===
<translate>=== Problem with tape drives ===</translate>
 
'''<translate>Problem</translate>'''
 
*<translate>There are problems with LTO tape drives which repeatedly request cleaning tape. Additionally, backups fail with I/O errors. </translate>
 
&rArr; '''<translate>Solution</translate>'''
 
<translate>
There are two possible causes for this:</translate>
 
*<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:</translate>


'''Problem'''
<ol><li><translate>Disable HPE Version Control Agent.</translate></li>
*There are problems with LTO tape drives which repeatedly request cleaning tape. Additionally, backups fail with I/O errors.  
<li><translate>Disable all tape agents for HPE Insight Management Agents as shown below.</translate></li>
&rArr; '''Solution'''
<translate>[[image:HPE_Insight-disable_tape_agent.jpg|link=]]</translate>
<br clear=all>
<li><translate>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>


There are two possible causes for this:
*<translate>Similar issues may be caused by '''common hardware-related problems'''. Refer to your hardware vendor documentation for details about hardware configuration and troubleshooting.</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 ===
==={{anchor|27422}} <translate>Restore fails due to a missing block that was not written to tape, but no error is generated during backup</translate> ===


'''Problem'''
'''<translate>Problem</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.  
*<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.</translate>


&rArr; '''Solution''': Detect whether your tapes are affected by following the procedure [[Tape_and_Tape_Devices_Troubleshooting#detect_error_tape|''How to detect affected savesets'']] below and install a patch for Beefalo V2. Make sure that:
&rArr; '''<translate>Solution</translate>''': <translate>Detect whether your tapes are affected by following the procedure [[Tape_and_Tape_Devices_Troubleshooting#detect_error_tape|''How to detect affected savesets'']] below and install a patch for Beefalo V2. Make sure that:</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>
<ul><li><translate>Check <tt>gv_rw_lis</tt> in <tt>sm.ini</tt> to see if your LIS folder destination was changed. Example:</translate></li>
  [PATHES]
  [PATHES]
  gv_rw_lis=D:\SEPsesam\var\lis\
  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>If your tape device is attached to a Windows RDS, you have to install the update to that RDS.</translate></li></ul>


===={{anchor|detect_error_tape}} ''How to detect affected savesets'' ====
===={{anchor|detect_error_tape}} ''<translate>How to detect affected savesets</translate>'' ====


<ol><li>Open the command-line interface and issue the following command in your LIS folder:
<ol><li><translate>Open the command-line interface and issue the following command in your LIS folder:</translate>
<ul><li>Linux: <code>/var/opt/sesam/var/lis</code></li>
<ul><li>Linux: <code>/var/opt/sesam/var/lis</code></li>
  grep "^.*:.*:0:.*:1$" *.sgm
  grep "^.*:.*:0:.*:1$" *.sgm
Line 63: Line 74:
</li></ul>
</li></ul>


<li>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 the lost block.</li>
<li><translate>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 the lost block.</translate></li>
  1:140479734912:1088:MP_File_Full00001:38956
  1:140479734912:1088:MP_File_Full00001:38956
  1:143030262144:1089:MP_File_Full00001:48605
  1:143030262144:1089:MP_File_Full00001:48605
Line 69: Line 80:
  10:146212594176:1:MP_File_Full00010:55536
  10: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>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>
</ol>


<noinclude>== See also ==
<noinclude><translate>==See also ==
[[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</noinclude>
[[Special:MyLanguage/Managing_Devices_and_Media|Managing Devices and Media]]</translate></noinclude>

Revision as of 14:18, 22 July 2020


Other languages:

Template:Copyright SEP AG en

Docs latest icon.png 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

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:
  1. Disable HPE Version Control Agent.
  2. Disable all tape agents for HPE Insight Management Agents as shown below.
  3. HPE Insight-disable tape agent.jpg
  4. 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 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.

Solution: Detect whether your tapes are affected by following the procedure How to detect affected savesets below and install a patch for Beefalo V2. Make sure that:

  • Check gv_rw_lis in sm.ini to see if your LIS folder destination was changed. Example:
  • [PATHES] gv_rw_lis=D:\SEPsesam\var\lis\
  • If your tape device is attached to a Windows RDS, you have to install the update to that RDS.

How to detect affected savesets

  1. Open the command-line interface and issue the following command in your LIS folder:
    • Linux: /var/opt/sesam/var/lis
    • grep "^.*:.*:0:.*:1$" *.sgm
    • Windows: C:\ProgramData\SEPsesam\var\lis
    • findstr /R /C:"^.*:.*:0:.*:1$" *.sgm
  2. If the command retrieves some lines then inspect the related sgm files. In the following example, the third line (marked in red) shows the lost block.
  3. 1:140479734912:1088:MP_File_Full00001:38956 1:143030262144:1089:MP_File_Full00001:48605 1:146212528704:0:MP_File_Full00010:1 10: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 0 that is not a real segment number but caused by error, ending by :1 block that is actually lost.

See also

Managing Devices and Media