Sun Storage Common Array Manager: How to Save an Array Configuration for Duplication or Restoration

Asset ID:	1-71-1007142.1
Update Date:	2012-07-17
Keywords:

Solution Type Technical Instruction Sure

Solution 1007142.1 : Sun Storage Common Array Manager: How to Save an Array Configuration for Duplication or Restoration

Applies to:

Sun Storage 2510 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6130 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6140 Array - Version Not Applicable to Not Applicable [Release N/A]
All Platforms
***Checked for relevance on 06-May-2011***

Goal

This document explains how to export an array configuration or a storage profile for the purposes of duplicating the configuration to another array, or for the case where the array configuration was reset.

NOTE: This is not a document that describes how to recover the array configuration without overwriting data. This process is designed to be applied to an array where the configuration has either been reset, or has not been configured at all.

Fix

The export and import of the configuration is handled by the sscs CLI.

Solaris: /opt/SUNWstkcam/bin/
Linux: /opt/sun/cam/bin/
Windows: C:\Program Files\Sun\Common Array Manager\bin

Export the array configuration in XML:

a. Using sscs:

sscs export array <array-name> > /tmp/array-config.xml

Example:

# sscs export array 2530-LCA > /tmp/array-config.xml

b. Using CAM Browser:
Under the Array Name in the left hand tree > Administration > Import/Export > Under Export Device Configuration > Enter Configuration File Name > Click Export
Export the array profile configuration into an XML file:

a. Using sscs:
```
sscs export -a <array-name> profile > /tmp/array-profile.xml
```
Example:

# sscs export -a 2530-LCA profile > /tmp/array-profile.xml
Import an Array Configuration:

Import the configuration of an array saved as an XML file using the export array command and apply the configuration to the specified array.

This overwrites the existing configuration on this array, destroying any data!!!

a. Using sscs:

sscs import -x xml-location array <array-name>

Example:

# sscs import -x array-config.xml array New-2530-LCANew-2530-LCA: : The xml was validated, and the array configuration cleared. An array import job was started.

b. Using CAM Browser:

Under the Array Name in the left hand tree > Administration > Import/Export > Under Import Device Configuration > Browse to the saved Configuration file > Click Import

Monitor the Job:

a. Using sscs:

# sscs list -a New-2530-LCA jobs 

Job ID: 2007.09.11.00.05.15.933 Status: In progress
# ./sscs list -a New-2530-LCA jobs 2007.09.11.00.05.15.933

Job ID: 2007.09.11.00.05.15.933

Type:                Import Array

Status:              In progress

% Complete:          78

Time to Completion:  00:00:12

Priority:            Medium
# ./sscs list -a New-2530-LCA jobs 2007.09.11.00.05.15.933

Job ID: 2007.09.11.00.05.15.933

Type:                Import Array

Status:              Done

% Complete:          100

Time to Completion:  00:00:00

Priority:            Unknown

b. Using CAM Browser:

Under the Array Name in the left hand tree > Jobs > Current Jobs

Once the imort job is completed, verify all volumes, initiators, and mappings are back:

a. Using sscs:

# sscs list -a New-2530-LCA volume


Volume: vol1-Raid1 Seg 64k  Type: Standard  Pool: Raid 1 pool  Profile: Raid 1 seg 64k

Volume: vol0-Raid5-64k  Type: Standard  Pool: Raid 5 pool  Profile: Raid 5 Seg 64k
# sscs list -a New-2530-LCA volume vol0-Raid5-64k

Volume: vol0-Raid5-64k

Type:                            Standard

WWN:                             ---hidden---

Pool:                            Raid 5 pool

Profile:                         Raid 5 Seg 64k

Virtual Disk:                    2

Size:                            100.000 GB

State:                           Mapped

Status:                          Online

Action:                          Initializing... <----*

Condition:                       Optimal

Read Only:                       No

Controller:                      A

Preferred Controller:            A

Modification Priority:           High

Write Cache:                     Enabled

Write Cache with Replication:    Enabled

Write Cache without Batteries:   Disabled

Flush Cache After:               10 s

Disk Scrubbing:                  Enabled

Disk Scrubbing with Redundancy:  Disabled

Associations:

Host: hostname.xxxx  LUN: 1  Initiator: v4v-T2000b-HBA2  WWN: 50:06:05:B0:00:25:1F:E0  Permission: Read/Write

Host: hostname.xxxx  LUN: 1  Initiator: v4v-T2000b-HBA1  WWN: 50:06:05:B0:00:25:1F:E4  Permission: Read/Write
# sscs list -a New-2530-LCA initiator

Initiator: v4v-T2000b-HBA2

Initiator: v4v-T2000b-HBA1
# sscs list -a New-2530-LCA initiator v4v-T2000b-HBA2

Initiator: v4v-T2000b-HBA2

WWN:      50:06:05:B0:00:25:1F:E0

Host:     v4v-T2000b.singapore

OS Type:  SOLAVT - Solaris (with Veritas DMP or other)

b. Using CAM Browser:

Under the Array Name in the left hand tree > Volumes/Mappings

Restore/Import Array Profile Configuration:

Imports one or more profiles from a specified XML file. This allows you to import the configuration profile from one array to overwrite the configuration profile for this array.

sscs import -a <array-name> -f -x file:///tmp/all_profiles.xml profile

NOTE: When (-f) force option is used Existing and In Use profiles are not imported. New profiles, profiles with duplicate settings and conflicting profiles are imported.
If the force option is not specified, then Existing, Duplicate, Conflicting and In Use profiles are not imported, only new profiles are imported.
In all cases, both successful and failed imports are reported.

Example:
# sscs import -a New-2530-LCA -x file:///tmp/array-profile.xml profile
```
Oracle_OLTP_HA: Existing profile not imported

Raid 1 seg 64k: Existing profile not imported

Raid 5 Seg 64k: Existing profile not imported

test: New profile imported

Random_1: Existing profile not imported
```

Attachments

This solution has no attachment