Veritas Storage Foundation Intelligent Storage Provisioning 5.0.1 Administrators Guide, HP-UX 11i v3, First Edition, November 2009

exclude
multipath
select
separateby
strong separateby
You can limit the scope of interpretation of rules to the components of an
application volume, such as its plexes, columns and logs.
See Compound rules on page 162.
Multiple arguments to the confineto, exclude and select storage selection
rules can be combined by using operators. If an operator is not specified, ISP uses
the default operator for the rule.
See Storage selection rule operators on page 159.
The =, !=, <, <=, > and >= comparative operators can be used with the confineto,
exclude and select storage selection rules. However, the operand arguments to
the <, <=, > and >= operators must be signed or unsigned integers that are capable
of being represented by 64 or fewer bits. If the operands are character strings,
real numbers, or are integers longer than 64 bits, the result of the comparison
may be incorrect.
affinity
An affinity rule expresses attraction between VxVM objects. Objects that conform
to this rule share as many attribute values as possible.
The affinity rule does not take any rule operators.
The following example demonstrates the application of affinity rules, by
allocating storage from as few enclosures as possible:
desired affinity "Enclosure"
confineto
A confineto rule restricts a VxVM object, such as volume or mirror, to being
configured from a specific set of LUNs. The scope of the rule determines the VxVM
object for which the restrictions apply. When a confineto rule is used at the top
level, it usually applies to the volume.
You can use compound rules to confine a mirror, column or log to a set of LUNs.
See Compound rules on page 162.
Using capabilities, templates and rules
Storage selection rules
154