| Skip Navigation Links | |
| Exit Print View | |
|
Sun Blade Storage Module M2 Product Documentation |
About This Documentation (PDF and HTML)
Overview of the Sun Blade Storage Module M2
Installing the Storage Module Into the Chassis
Assigning and Managing Storage
Overview of the Sun Blade Storage Module M2 Product Notes
Supported Firmware, Hardware and Software
Solaris Operating System Issues
Performing Maintenance and Hot Plug Actions
Replacing a REM on a SPARC System
Replacing a REM on an x86 System
Storage Module Sensors and Indicators
Introduction to the Sun Blade Storage Module M2
Maintaining the Sun Blade Storage Module M2
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:
|