Software Manual

B.49
setvv
InForm OS Version 2.3.1 Remote Copy User’s Guide
–pol <policy>[,<pol>...]
Specifies the policy is implemented by a virtual volume. Valid policies are as follows:
stale_ss
Specifies that invalid (stale) snapshot volumes are permitted. Failures to update
snapshot data occur when there is not sufficient administration or snapshot space.
Failures to update snapshot data does not affect the write to the base volume.
However, the snapshot is considered invalid.
no_stale_ss
Specifies that stale snapshot volumes are not permitted. A failure to update a
snapshot is considered a failure to write to the base volume. Existing stale snapshots
remain stale.
one_host
Constrains the export of a volume to one host or one host cluster (when cluster
names may be used as a host name).
no_one_host
This policy should only be used when exporting a virtual volume to multiple hosts
for use by a cluster-aware application, or when “port presents” VLUNs are used. This
is the default policy setting.
tp_bzero
Specifies that if a host write results in the allocation of a new data page that is only
partially filled by the host write, then a zero-fill is performed on the unwritten
portion of the data page to ensure that the host cannot read data from deleted
volumes or snapshot. The default allocation page size is 16 KB.
no_tp_bzero
Specifies that the zero-fill operation is bypassed on the allocation of partially
written data pages.
zero_detect
Enables the InServ Storage Server to scan for zeros in the incoming write data. When
used during a physical copy to a Thinly Provisioned Virtual Volume (TPVV) avoids
allocating space for blocks containing zero. When used with a Thin Persistence
license, reclaims allocated space when zero blocks are written to a TPVV. This policy
is applicable for base TPVVs.