Whether the hosts can read from or write to the P-VOLs or S-VOLs depends on the status of the Thin Image Advanced pairs.
The following table explains the host access and pair status for snapshot pairs.
| Thin Image Advanced pair status | Access to the P-VOL | Access to the S-VOL | |||
|---|---|---|---|---|---|
| CCI | HDvM - SN | Read | Write | Read | Write |
| COPY | COPY(PD) | Yes | Yes | No | No |
| PAIR or PFUL | PAIR or PFUL | Yes | Yes | No | No |
| PSUP | PSUP(SP) | Yes | Yes | No | No |
| PSUS or PFUS | PSUS or PFUS | Yes | Yes | Yes | Yes |
| COPY | COPY(RS) | Yes | Yes | No | No |
| RCPY | COPY(RS-R) | No | No | No | No |
| CPYP | COPY(SP) | Yes | Yes | No | No |
| SMPP* | SMPL(PD) | Yes | Yes | No | No |
| PSUE | PSUE | Yes | Yes | No | No |
| * SMPP is displayed if the -key detail option is specified for the raidcom get snapshot command | |||||
CAUTION:
If a host uses a software
application other than Thin Image Advanced to monitor Thin Image Advanced pair volumes, the S-VOL status might determine if
the software application ends abnormally. For example, because the S-VOL in a status
other than "PSUS" or "PFUS" rejects host access, an abnormality might occur in the
monitoring application whose access is rejected by the S-VOL.
If a host connects to at least two ports, an abnormality can occur with ports that are not connected to S-VOLs rejecting access from hosts. To resolve these issues, close the software application that monitors volumes.