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

Asset ID: 1-71-1011303.1
Update Date:2010-06-22
Keywords:

Solution Type  Technical Instruction Sure

Solution  1011303.1 :   Sun Storage[TM] 6130/6140/6180/6540/6580/6780: How to Change RAID Level for a VDisk Using CAM or the sscs CLI  


Related Items
  • Sun Storage 6780 Array
  •  
  • Sun Storage 6540 Array
  •  
  • Sun Storage 6580 Array
  •  
  • Sun Storage 6130 Array
  •  
  • Sun Storage 6180 Array
  •  
  • Sun Storage 6140 Array
  •  
  • Sun Storage Common Array Manager (CAM)
  •  
Related Categories
  • GCS>Sun Microsystems>Storage Software>Modular Disk Device Software
  •  

PreviouslyPublishedAs
215510


Applies to:

Sun Storage 6140 Array - Version: Not Applicable and later   [Release: NA and later ]
Sun Storage 6130 Array - Version: Not Applicable and later    [Release: NA and later]
Sun Storage 6540 Array - Version: Not Applicable and later    [Release: NA and later]
Sun Storage 6180 Array - Version: Not Applicable and later    [Release: NA and later]
Sun Storage 6580 Array - Version: Not Applicable and later    [Release: NA and later]
All Platforms

Goal

This document provides the steps necessary to perform Dynamic RAID Migration (DRM) for a given VDisk, using Common Array Manager (CAM) or the sscs CLI (Command Line).

The requirements for this are as follows:

  • There can be only one VDisk in a Pool, if you are changing the level at the pool level.
  • There can only a single volume in a VDisk, if you are changing the level at the volume level.
  • Migrations to a RAID 1+0 require an even number of drives.
  • The volume sizes remain unchanged, so a migration from a RAID 5+1 to 3+3 would
    require that the volumes can be contained within the space of 3 drives of the 
    original 5+1 VDisk.
If these requirements are not met, you should expand your VDisk.

Solution

1) List out current profile for a given volume or pool.

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click Volumes.
  4. Click on the Volume Link for your volume name.
  5. Note the Pool for this volume.
  6. Click Pools in the left menu panel.
  7. Click Pool Link for the name of the pool from step 5.
  8. Note the currently selected Profile for this pool.
  9. Click Profiles from the left menu panel.
  10. Click Profile Link for the name of the profile in step 8.
  11. Note all settings for:
  • RAID Level.
  • Segment Size.
  • Read Ahead Cache setting.
  • Number of drives.
  • Drive type.
SSCS CLI:
  1. Get the profile name from the volume:

    sscs list -a <array_name> volume <volume_name> | grep Profile

  2. List profile details:

    sscs list -a <array_name> profile <profile_name>

  3. Note all settings for:
  • RAID Level.
  • Segment Size.
  • Read Ahead Cache setting.
  • Number of drives.
  • Drive type.
2) Create a new profile with the desired transition RAID Level.

Browser:
  1. Select Storage Systems.
  2. Select Profiles.
  3. Click the New button.
  4. Define the profile like the current one for the volume, changing the name and RAID Level.
  5. Click OK.
SSCS CLI:
  1. Create the new profile based on the following options for sscs:

    sscs create -a <array_name> -r <raid_level> -s <segment_size> -h <read_ahead> -n <number_of_drive> -k <drive_type> profile <profile_name>

    Example:

    sscs create -a myarray -r 1 -s 256K -h off -n variable -k any profile new_RAID1_profile

3) Create a new pool for this profile.

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click Pools.
  4. Click New button.
  5. Fill in Pool name and select the profile that you created above.
SSCS CLI:

sscs create -a <array_name> -p <profile_name> pool <new_pool_name>

Example:

sscs create -a myarray -p new_RAID1_profile pool new_RAID1_pool

4) Change the pool of the volume of the VDisk to the new pool.

For the volume:

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click Volumes.
  4. Click on the Volume Link for your volume name.
  5. Change the Pool Drop-down to the new pool name.
  6. Click Save.
SSCS CLI:

sscs modify -a <array_name> -p <new_pool_name> volume <volume_to_be_modified>

Example:

sscs modify -a myarray -p new_RAID1_pool volume MyVol

For the VDisk:

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click VDisk.
  4. Click on the Vdisk Link for the vdisk of your set of volumes.
  5. Change the Pool Drop-down to the new pool name.
  6. Click Save.
SSCS CLI:

sscs modify -a <array_name> -p <new_pool_name> vdisk <vdisk_to_be_modified>

Example:

sscs modify -a myarray -p new_RAID1_pool vdisk 1

5) Review the job completion.

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click Jobs.
SSCS CLI:

sscs list -a <array_name> jobs

Note: DRM, DVE (Dynamic Volume Expansion), DCE (Dynamic Capacity Expansion) or DSS (Dynamic Segment Sizing) cannot be run at the same time. Only one long running job can run on a volume or VDisk at a given time.

6) Check the change.

Browser:
  1. Select Storage Systems.
  2. Expand Your Array Name.
  3. Click Volumes.
  4. Note the VDisk for your volume.
  5. Click VDisks.
  6. Note the RAID Level of the VDisk.
SSCS CLI:
  1. Get the VDisk number for the volume:

    sscs list -a <array_name> volume <volume_name> | grep "Virtual Disk"

    Example:

    sscs list -a myarray volume MyVol | grep "Virtual Disk"

    Virtual Disk: 4

  2. Get the RAID Level of the VDisk:

    sscs list -a <array_name> vdisk <vdisk_number> | grep "RAID Level"

    Example:

    sscs list -a myarray vdisk 4 | grep "RAID Level"

    RAID Level 5


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