About This Documentation (PDF and HTML)
SAS Device Access to the Chassis SAS-2 Domain
Host Access to Storage Module Resources Using the Sun Blade Zone Manager
How to Assign Storage to Hosts Using the CMM ILOM Web Interface
How to Assign Storage to Hosts Using the CMM ILOM CLI
Overview of Storage Module Management
Management Options Using the CMM ILOM
Management Options Using the Sun Storage 6Gb SAS REM RAID HBA (SGX-SAS6-R-REM-Z)
Management Options Using the Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z)
Performing Maintenance and Hot Plug Actions
Preparing for Hot Plug Actions
Recovering Zoning Configurations
Upgrading Storage Module Firmware
Replacing a REM on a SPARC System
Replacing a REM on an x86 System
Storage Module Sensors and Indicators
Displaying Sensor and Indicator Information Using the CMM ILOM Web Interface
Displaying Sensor and Indicator Information Using the CMM ILOM CLI
At the release of this document, the importing of virtual drives from one SAS–2 REM to another is only supported if you are replacing a failed REM with an identical REM. For example, if you have a Sun Storage 6Gb SAS REM HBA (SGX-SAS6–REM-Z) connected to the Sun Blade Storage Module M2 and the REM fails (but the drives are good), you can import the existing virtual drives to a replacement Sun Storage 6Gb SAS REM HBA (SGX-SAS6–REM-Z).
Caution - Importing virtual drives between different technology REMs, such as importing IR virtual drives created using an LSI Fustion-MPT IR REM (SGX-SAS6–REM-Z) to an LSI MegaRAID REM (SGX-SAS6–R-REM-Z). is not supported. This is because a mismatch in metadata size can cause an import operation to fail and data to be lost. To migrate virtual disk data from one type of REM to another, first do a full backup. Next, attach the drives to the new REM. Then, clear the existing virtual drive configuration and create a new virtual drive using the new REM. Once that is done, the data can be restored from backup to the new virtual drive. |
Perform one of the following procedures: