symclone and priority

not exactly what you are looking for but what if you create the first set with -precopy option, so when you activate both sessions ..the first one will probably be done by then.

The default priority is 0 for BCV, RDF, MIR, and CLONE.

in symqos terms (1-16) ..what is the default priority on CLONE synchronization ?

No problem dynamox.

Yes, the hostio_priority command is part of Symmetrix Priority Controls, which is separately licensed. This is for setting the priority of host I/O.

The -cp command (also part of symqos), is for Dynamic Cache Partitioning, which is also a separate license. DCP allows you to logically divide your DMX cache into separate partitions, and place logical devices into these separate partitions. These partitions can be static (fixed size) or dynamic (size varies automatically based on workload and the parameters you set).

The set pace/priority commands are included with the BASE Solutions Enabler license, and is used primarily for setting the copy priorities of TimeFinder and SRDF activity.

Thanks,

- Sean

Dynamox,

This only has a direct effect on the speed of the timefinder copy operations. Of course, timefinder itself can have an indirect effect on overall device performance (e.g. due to the read activity on the prod disks during establishes, or due to COFW/COFA, or due to write activity where clones and STDs are mixed on the same physicals). But the default QoS value for CLONE & BCV is 0 (the fastest possible), so setting a higher QoS value (slowing down the TF copy) would generally improve the performance of production I/O during copy activity.

There is a way to directly change priorities for production I/O with QoS -- it is a separately licensed feature called Symmetrix Priority Controls. This allows you to modify the service time priority for host I/O associated with individual volumes. This feature (as well as symqos dynamic cache partitioning) is available on 5772 and higher microcode.

Thanks,

- Sean

Sean,

does this only affect timefinder operation ..or will it have an impact on overall device performance ?

With symqos you can change different QOS aspects ...

You can change BCV, CLONE, RDF priorities
You can also change MIR priority (mirroring process inside the storage) however I suggest you NOT to change this parameter

thanks Sean. Is -hostio_priority parameter part of the "Symmetrix Priority Controls" set ..or it's available as part of the standard symqos functionality set ? If these two are separate features ..what is the difference between the two ?

You can use QoS to set clone priority values on each of the BCVs. The lower the priority, the faster the clone will go -- 0 = fastest and 16 = slowest. So you could set a high priority on your first clone (dev 01E8) and a lower priority on your second clone (0381).

For example:

symqos set CLONE priority 0 -g BCV001
symqos set CLONE priority 8 --g BCV002

You can find more information in the Solutions Enabler Symmetrix Array Controls CLI guide as well.

Good to know about these clone settings

NOT both of them. But just the different clone volumes or time finder copies.