Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1463949.1
Update Date:2012-08-12
Keywords:

Solution Type  Technical Instruction Sure

Solution  1463949.1 :   Pillar Axiom: How to perform a RAID Data Consistency Check  


Related Items
  • Pillar Axiom 600 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
  •  




In this Document
Goal
Fix
References


Created from <SR 3-5565265711>

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

This document outlines the steps needed to perform a RAID Data Consistency check (when instructed to perform)

Fix

For systems running pre-R5:

Instructions on how to run RAID Consistency Check against a specific Brick. Please be aware of the following when you pursue this (via the Axiom GUI):
1) This is activated by going to the Support Tab > Tools > Verify System Operation > Click the Data Consistency link > Choose Brick (from puldown) > Choose Low or High Priority > Click Ok
2) It is best to run this during a period of expected low IO for any storage objects that exist in that Brick, only because performance will take between a 10-30% hit (depending on the Priority mode you choose)
3) For a typical brick (under 2TB capacity) this activity may take less than 2 hours, so plan accordingly. Re-engage Support with the results once done.

For systems running post-R5:

Instructions on how to run Data Consistency Check against a specific Brick. Please be aware of the following when you pursue this (via the Axiom GUI):
1) This is activated by going to the Support Tab > Tools > Data Consistency > Right-Click on Brick choice (to bring up a sub-menu) > Choose Verify Data Consistency > Choose Low or High Priority > Click Ok
2) It is best to run this during a period of expected low IO for any storage objects that exist in that Brick, only because performance will take between a 10-30% hit (depending on the Priority mode you choose)
3) For a typical brick (under 2TB capacity) this activity may take less than 2 hours, so plan accordingly. Re-engage Support with the results once done.

References

<BUG:13946777> - ORACLE DATA BLOCK CORRUPTIONS AFTER EXPERIENCING FC BRICK001 DRIVE6 FAILURE

Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback