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-71-1941549.1
Update Date:2017-09-26
Keywords:

Solution Type  Technical Instruction Sure

Solution  1941549.1 :   FS System: How to Switch to Backup Persistence  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  


System haltpoints are used to troubleshoot boot issues.  Setting a haltpoint will cause the system to halt the boot sequence at a certain point giving the user an opportunity to work around the problem.

In this Document
Goal
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Commands should not be executed by customers.

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

There may be times when the active copy of Persistence becomes corrupted. When this happens recovery can often be accomplished by using a backup copy. Below are the steps to switch to backup Persistence on a Flash Storage System FS1-2

Solution

The procedure below should only be attempted after you have engaged Engineering for your issue. Once they have confirmed a corrupt Persistence, use the following steps to recover depending on what version of the code is running on the FS1:

  • For Systems running R6.2.x (halt point not required):
    1. Reenable the excluded Controller:
      # fscli controller -reenable
       
    2. Restart the FS1-2:
      # fscli system -restart -emergencyPreserveFbm -backupPersistence
       
  • For Systems running R6.1.x:
    1. Execute the cli command to reenable an excluded controller:
      # fscli controller -reenable
        

    2. Set the haltpoint:
      # fscli haltpoint -add -haltpoint PDS_COMP_NP:STOP_BEFORE_COMMON_NODE_LIST
        
      NOTE: Ignore error message: "Error - The command timed out.  (CONTROLER_CONNECTION_LOST) Command Failed"
       
    3. Restart the FS1 to force a cold start or execute the following CLI command:
      fscli system -restart -emergencyPreserveFbm
       
    4. After approximately 20 minutes, the system should hit the cold start haltpoint.  System Status in the GUI should say Boot State NP.  Then execute the following commands:
      fscli system -useBackupPersistence
      fscli haltpoint -delete -all
      fscli haltpoint -resume
       
      System should resume cold start and boot successfully.

 


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