Tivoli Storage Manager server version 6.3.3 users may not be able to restore data from tape volumes or append data to existing tape volumes

Flash (Alert)


Abstract

The logical block protection attribute might be incorrectly set to "yes" for some tape volumes. As a result, users who upgrade the Tivoli Storage Manager server to version 6.3.3 might not be able to restore data or append data to existing tape volumes. Restore operations might fail with error message ANR1330E . Backup operations might fail with error message ANR0530W.

Content


PROBLEM SUMMARY:

IBM Tivoli Storage Manager server versions 6.2.4, 6.2.5, 6.3.0, 6.3.1, and 6.3.2 incorrectly set the logical block protection attribute for tape volumes. As a result, when users upgrade Tivoli Storage Manager server to version 6.3.3, they might not be able to append to tape or restore data if the attribute is incorrectly set to "yes" for the volume.


WHO IS AFFECTED:

All Tivoli Storage Manager server version 6.3.3 users with non-IBM tape devices. Affected volumes are volumes that were created with Tivoli Storage Manager server versions 6.2.4, 6.2.5, 6.3.0, 6.3.1, and 6.3.2.


SYMPTOMS

The symptoms surface when you upgrade Tivoli Storage Manager server to version 6.3.3.

For Oracle StorageTek T10000C devices

  • If the volume was created with Tivoli Storage Manager server versions 6.2.4, 6.2.5, 6.3.0, 6.3.1, or 6.3.2, and the logical block protection attribute for the volume is incorrectly set to "yes," Tivoli Storage Manager version 6.3.3 continues to write data to the volume with logical block protection. You will not encounter an error when appending data to this volume. The volume ends up with mixed data. Data at the beginning of the tape that was written with a Tivoli Storage Manager server version prior to version 6.3.3 does not have logical block protection. Data that was appended to the volume later with Tivoli Storage Manager server version 6.3.3 has logical block protection. You might encounter an error when restoring data that was written to the tape without logical block protection.
  • If the volume was created with Tivoli Storage Manager server versions 6.2.4, 6.2.5, 6.3.0, 6.3.1, or 6.3.2, you might not be able to restore data with Tivoli Storage Manager version 6.3.3 if the logical block protection attribute is incorrectly set to "yes" for the volume. You might encounter an error similar to the following when restoring data:
    ANR0510I Session 1 opened input volume TTC125TT.
    ANR1330E The server has detected possible corruption in an object that is being restored or moved. The actual values for the incorrect frame are: magic 65644979 hdr version 29806 hdr length 29801 sequence number 168640121 data length 20202020 server ID 1701064508 segment ID 4716516091519460720 crc 6D657373.
    ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000102 server id 00000000 segment id 0000000000003123.

For all other tape devices
  • For devices that are controlled by the Tivoli Storage Manager device driver and do not have logical block protection support, if the logical block protection attribute of the volume is set to "yes," you might encounter the following error when backing up data to the volume:
    ANR0406I Session 3 started for node BA (Linux86) (Tcp/Ip localhost(33263)).
    ANR8337I LTO volume 08C392L4 mounted in drive LTO_DRIVE (/dev/tsmscsi/mt3).
    ANR8468I LTO volume 08C392L4 dismounted from drive LTO_DRIVE (/dev/tsmscsi/mt3) in library LTO_LIB.
    ANR9999D_2231172434 OpenActiveVol(asvolmnt.c:4746) Thread<127>: Unknown result code (2855) from pvrOpen.
    ANR9999D Thread<127> issued message 9999 from:
    ANR9999D Thread<127> 0x00000000dab963 OutDiagToCons
    ANR9999D Thread<127> 0x00000000dae7e5 outDiagfExt
    ANR9999D Thread<127> 0x00000000caec40 AsOpenVol
    ANR9999D Thread<127> 0x00000000caca02 AsAcquireAnyWritableVol
    ANR9999D Thread<127> 0x00000000d2d0f0 AllocNewVol
    ANR9999D Thread<127> 0x00000000d320af AsAllocSeg
    ANR9999D Thread<127> 0x00000000cff8a9 DoAllocSeg
    ANR9999D Thread<127> 0x00000000cffb2f SsAuxSinkThread
    ANR9999D Thread<127> 0x00000000e42f16 StartThread
    ANR9999D Thread<127> 0x002b6438443193 *UNKNOWN*
    ANR9999D Thread<127> 0x002b643b10f0dd *UNKNOWN*
    ANR0530W Transaction failed for session 3 for node BA (Linux86) - internal server error detected.
    ANR0403I Session 3 ended for node BA (Linux86).
  • You might also encounter the following error when restoring data from an affected volume:
    ANR0510I Session 1 opened input volume TTC125TT.
    ANR1330E The server has detected possible corruption in an object that is being restored or moved. The actual values for the incorrect frame are: magic 65644979 hdr version 29806 hdr length 29801 sequence number 168640121 data length 20202020 server ID 1701064508 segment ID 4716516091519460720 crc 6D657373.
    ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000102 server id 00000000 segment id 0000000000003123.


RECOMMENDATION:

Apply Tivoli Storage Manager server version 6.3.3.100. If you still encounter the symptoms described in the Symptoms section above, follow the action described in the Circumvention section for each tape volume that has the problem.

Once the fix for APAR IC90153 is available and you have applied the fix, complete the following steps for Oracle T10000C drives and HP Ultrium 6 drive.

For users with Oracle T10000C drives

Complete the following steps if you have never enabled logical block protection for Oracle T10000C drives:

1. Issue the following SQL statement to obtain a list of volumes that have the logical block protection attribute set to "yes":

    select volume_name, block_protect from volumes where block_protect='Yes' and devclass_name=' xxx'

    where xxx is the device class name
2. Issue the MOVE DATA command to move data from the affected volume to another available volume in the same storage pool.

Complete the following steps if you enabled logical block protection for Oracle T10000C drives:

1. Issue the following SQL statement to obtain a list of volumes that have the logical block protection attribute set to "yes:
    select volume_name, block_protect from volumes where block_protect='Yes' and devclass_name=' xxx'

    where xxx is the device class name

2. Issue the following SQL statement to look at the volume history of each volume to see when the volume was created. If the volume was created after you installed Tivoli Storage Manager server version 6.3.3, the volume is not affected.

  • select * from volhistory where volume_name='xxxxxxxx' and type='STGNEW'

    where xxxxxxxx is the volume name

3. For the affected volumes, update the LBProtect parameter of the device class to WRITEOnly or No, and issue the MOVE DATA command to move data from the affected volume to another available volume in the same storage pool.

For users with HP Ultrium 6 drives

Complete the following steps after applying the fix for APAR IC90153:

1. Issue the following SQL statement to obtain a list of volumes that have the logical block protection attribute set to "yes":

    select volume_name, block_protect from volumes where block_protect='Yes' and devclass_name=' xxx'

    where xxx is the device class name
2. Issue the MOVE DATA command to move data from the affected volume to another available volume in the same storage pool.


PROBLEM RESOLUTION:

With the fix for APAR IC90153, Tivoli Storage Manager server automatically corrects the logical block protection attribute for all volumes that are not supported with logical block protection.


CIRCUMVENTION:

If unable to restore data, users can move data from an affected volume to another volume in the same storage pool.

If unable to append data to a volume, mark the volume read-only and the Tivoli Storage Manager server will select a new scratch volume for writing.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

6.2, 6.3

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1624784

Modified date:

2014-01-06

Translate my page

Machine Translation

Content navigation