Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1578303.1
Update Date:2013-08-21
Keywords:

Solution Type  Problem Resolution Sure

Solution  1578303.1 :   VLE 1.2.16 code De-duplication problem with VSM6 Data  


Related Items
  • Sun Virtual Library Extension (VLE)
  •  
  • StorageTek Virtual Storage Manager System 6 (VSM6)
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VLE
  •  




In this Document
Symptoms
 On VLE 1.2.16 systems, while migrating VTVs from a VSM6, with de-duplication enabled on the target VLE 1.2.16 system, the migrate job will result in RTDs being put offline. VSM6 will not be able to communicate with VLE. VLE will encounter repeated re-start of VLE-Service and will result in the sending of ASRs, every 20-30 minutes.
Changes
 The addition of VSM6 connectivity to a previously installed VLE running VLE 1.1.14 or VLE 1.2.16 code.
Cause
 The de-dupe cracker checks the formats of the VTVs, validates them and if there are incompatibilities they will result in errors.  The de-duplication format cracking engine for VLE 1.2.16 was tested and released long before the release of VSM6. Some of the formats of the newly released VSM6 will result in the 1.2.16 cracker engine throwing exceptions.
Solution
 Customer Action if Exposed:
At the VTCS Storage Class, turn off the de-duplication feature of the VMVC that contains the offending VTV.
 Resolution:
Upgrade to VLE 1.3.12 code to run de-dupe operations with VSM6.  VTV format changes in VSM6 have been tested and addressed in VLE 1.3.12 code.


Applies to:

Sun Virtual Library Extension (VLE) - Version 1.1 to 1.2 [Release 1.0]
StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions and later
Information in this document applies to any platform.

Symptoms

On VLE 1.2.16 systems, while migrating VTVs from a VSM6, with de-duplication enabled on the target VLE 1.2.16 system, the migrate job will result in RTDs being put offline. VSM6 will not be able to communicate with VLE. VLE will encounter repeated re-start of VLE-Service and will result in the sending of ASRs, every 20-30 minutes.

Changes

The addition of VSM6 connectivity to a previously installed VLE running VLE 1.1.14 or VLE 1.2.16 code.

Cause

The de-dupe cracker checks the formats of the VTVs, validates them and if there are incompatibilities they will result in errors.  The de-duplication format cracking engine for VLE 1.2.16 was tested and released long before the release of VSM6. Some of the formats of the newly released VSM6 will result in the 1.2.16 cracker engine throwing exceptions.

Solution

Customer Action if Exposed:
At the VTCS Storage Class, turn off the de-duplication feature of the VMVC that contains the offending VTV.

Resolution:
Upgrade to VLE 1.3.12 code to run de-dupe operations with VSM6.  VTV format changes in VSM6 have been tested and addressed in VLE 1.3.12 code.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback