HP StorageWorks XP Remote Web Console Software User Manual
Page 47
volumes, see
“Whether Non-XP Continuous Access and Non-XP Continuous Access Asynchronous
Volumes Can Be Used as XP Continuous Access and XP Continuous Access Asynchronous Volumes”
(page 36)
.
Table 19 Whether XP Continuous Access and XP Continuous Access Asynchronous Volumes Can
Be Used as XP Auto LUN Volumes
Can the Volumes be Used as XP Auto LUN Volumes?
Functions and Volumes
XP Continuous Access
No
P-VOL in Duplex Pending status
Yes
P-VOL in Duplex status
Yes
P-VOL in Suspend status
–
P-VOL in Suspending status
No
S-VOL in Duplex Pending status
Yes
S-VOL in Duplex status
Yes
S-VOL in Suspend status
–
S-VOL in Suspending status
XP Continuous Access Asynchronous
No
P-VOL in Duplex Pending status
No
P-VOL in Duplex status
Yes
P-VOL in Suspend status
No
P-VOL in Suspending status
No
S-VOL in Duplex Pending status
No
S-VOL in Duplex status
Yes
S-VOL in Suspend status
No
S-VOL in Suspending status
Make sure the following restrictions are followed when you use XP Continuous Access volumes in
Duplex status as XP Auto LUN volumes.
•
Set I/O rates less than 50 IOPS while migrating volumes.
If the I/O rate is 50 IOPS or more, volumes may not be migrated.
•
If a connection failure has occurred between the MCU and the RCU, remove the failure, and
then migrate the volume.
•
If an external volume or a TP-VOL is used, information about the volume is displayed on the
Remote Web Console of the remote storage system. When the volume migration is completed
and the XP Continuous Access Asynchronous pair is suspended and resynchronized, the
information about the volume will be updated.
•
Do not migrate P-VOLs and S-VOLs at the same time.
Timeout of the host I/O occurs if you migrate P-VOLs and S-VOLs at the same time.
•
Do not change the status of the volume while migrating volumes.
While migrating volumes, even if you try to change the status of the volume, the status may
not change.
Interoperability with Other Products and Functions
47