Remote storage volume requirements
Volumes used for imports must meet the requirements for size, status, and other criteria.
Remote storage volume
Cannot be part of another import
Must have an online status
After the import begins, the controller firmware creates a remote storage volume in the background. Due to that background process, the remote storage volume is not manageable in System Manager and can only be used for the import operation.
Can be used as proxies to the remote storage device.
Cannot be used as candidates for other volume copies or snapshots.
Cannot have the Data Assurance setting changed while the import is in progress.
Cannot be mapped to any hosts, because they are reserved strictly for the import operation.
Remote storage object identifier
Remote storage device LUN number
Target volume candidates
Must be a RAID/DDP volume.
Must have a capacity that is equal to or larger than the remote storage volume.
Must have a block size that is the same as the remote storage volume.
Must have a valid state (optimal).
Cannot have any of the following relationships: volume copy, snapshot copies, asynchronous or synchronous mirroring.
Cannot be undergoing any reconfiguration operations: Dynamic Volume Expansion, Dynamic Capacity Expansion, Dynamic Segment Size, Dynamic RAID Migration, Dynamic Capacity Reduction, or Defragmentation.
Cannot be mapped to a host before the import starts (however, it can be mapped after import completes).
Cannot have Flash Read Cached (FRC) enabled.
System Manager automatically checks these requirements as part of the Import Remote Storage wizard. Only volumes that meet all the requirements are displayed for destination volume selection.