![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 1642285.1 : VSM or VLE - How to Perform a Clean or Erase and What They Are
In this Document
Created from <SR 3-8786165311> Applies to:StorageTek Virtual Storage Manager System 6 (VSM6) - Version All Versions to All Versions [Release All Releases]Sun Virtual Library Extension (VLE) - Version 1.2 to 1.4 [Release 1.0] Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0] Sun StorageTek VSM5 System - Version All Versions to All Versions [Release All Releases] Sun StorageTek VSM4 System - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. GoalThis document describes the current process for the field engineer or TSC to acquire VSM clean code or erase code. It will also provide a brief explanation of what each one does. SolutionVSM6, VSM7: 1. Review the VSM6_7 CLEAN Warning document and/or the VSM6 ERASE Warning document on the VSM6 - VSM7 Workspace. 2. Read and Understand the entire document before selecting the link at the bottom of the page. Note: VSM6 ERASE requires a minimum code of 6.2.0.07.000
VLE: 1. Review the VLE CLEAN Warning document and/or the VLE ERASE Warning document. 2. Read and Understand the entire document before selecting the link at the bottom of the page.
VSM4, VSM5, VSM5C, SVA (V2X, or V2Xf): 1. Review the VSM4-5_SVA CLEAN-ERASE Warning document. 2. Open a collaboration SR to Level 2 for verification and code access. The Level 2 Specialist will need to:
OPERATION Functional code writes customer data to backend storage. Mapping tables (pointers) contained in the functional track table are used to link customer data with physical locations on the back-end disks (array and cylinder). Without accurate mapping table information, customer data becomes unaddressable.
CLEAN CODE CLEAN code is a special code release with the sole purpose of making all customer data on the subsystem unaddressable. CLEAN code can be applied (or IML'ed) into the machine when the VTSS product is deinstalled to ensure that customer data cannot be accessed when the subsystem is re-installed at another location. When this code is IML'ed it destroys the machine's configuration information. This includes the VTV inventory table, HDA grouping, and access to the functional track-mapping table. Without this information, there is no longer access to the customer's data. the data CANNOT be recovered from the cleaned machine. This is a billable process. Please note: For legacy VSMs CLEAN is performed via a code load. For VSM6 or VLE products this same function is performed via scripts and a special code load is not required.
ERASE CODE ERASE code is a special code release that actually performs a secure erase on the back-end hard drives. Once the ERASE code is IML'ed, the data no longer exists on the subsystem and CANNOT be recovered from the machine. This is a billable process. Please note: For legacy VSMs ERASE is performed via a code load. For VLE and VSM6 this same function is performed via scripts and a special code load is not required.
Attachments This solution has no attachment |
||||||||||||||
|