NOTE:
Copy operations that are stopped by the Copy Threshold option will resume once the
load on the storage system becomes light.
Effects of Auto LUN on other program products
When differential data is being copied, longer copying time can be expected for the following
program products:
Auto LUN
Business Copy
Business Copy Z
Compatible FlashCopy
The following table shows the amount of additional copy time expected for the affected program
products. The increase in copy time may be as much as doubled and depends on the number of
pairs set to the program product.
Table 15 Estimated Delay in Copy Time for Auto LUN and Other Program Products
Capacity of Migrated Volume (MB)
0 - 1,000
1,001 - 5,000
5,001 - 10,000
10,001 - 50,000
50,001 - 100,000
100,001 - 500,000
500,001 - 1,000,000
1,000,001 - 2,150,400
The estimates in
for update I/Os for the migrated volume is 50 IOPS for one volume.
Best practices
Do not perform Auto LUN operations during storage system maintenance activities (such as,
installation, replacement, removal of cache or drives, configuration changes, or replacement of
the microcode).
Before turning off the power on the storage system, confirm that all Auto LUN operations are
complete. If you turn off the power of the storage system during Auto LUN operations, and power
is later restored, Auto LUN operations resume, but there is a risk that data may be lost from the
shared memory. If this happens, Auto LUN begins recopying all data, both the differential data
not yet migrated as well as the data previously copied to the target volume before the power
interruption.
34
Auto LUN monitoring
Table 15 (page 34)
are calculated based on the assumption that the workload
Estimated delay in copying speed (in minutes)
4
18
37
186
372
1,860
3,720
9,667
Need help?
Do you have a question about the StorageWorks P9000 - Disk Arrays and is the answer not in the manual?
Questions and answers