volumes from horcm.conf and Inquiry result. Inquiry result is based on
configuration of Data Retention Utility. When controlling pair volumes,
requests to protected volumes are rejected with error code EX_ENPERM.
• The Data Protection Facility is based on the host side view at the result of
Data Retention Utility. You need to configure Data Retention Utility before
CCI operation. CCI checks Data Retention Utility by Inquiry within CCI.
• The Data Protection Facility can be enabled separately for each command
device. If you want to use protection and non-protection modes in the
same storage system at the same time, you can define two (or more)
command devices: one with protection ON, one with protection OFF.
Protection mode is enabled for the host that has Data Retention Utility
and ON command device.
Examples for configuration and protected volumes
Case (1): Two Hosts (
Figure 7-2 Example for the two-host configuration on
page 7-8). In protect mode Ora2 are rejected to operate the paired
volume, because of Unknown for Grp4 on HOST2.
Case (2): One Host (Figure 7-3 Example for the one-host configuration on
page 7-9). In protect mode Ora1 and Ora2 are rejected to operate the
paired volume, because of Unknown for Grp2 and Grp4 on HOST1. If HOST1
has a protection OFF command device, then Ora1 and Ora2 are permitted to
operate the paired volume.
Note: The Data Protection Facility is implemented by only CCI. CCI needs to
know the protection attribute for the command device whether should be
permitted the operation for paired volume. If HORCM has protection ON
command device at its time, then HORCM checks a permission for a paired
volume.
Figure 7-2 Example for the two-host configuration
7-8
Data protection operations with CCI
Command Control Interface User and Reference Guide
To Next Page
Loading...
Need help?
General