Host server stoppages and device recognition issues

If you boot or reboot host servers, such as HP-UX or Solaris, or if you use the host server to run the read command on a V-VOL to recognize a device, keep the following items in mind.

• You cannot change the volume of the device recognized by the host server to a V-VOL.
• Before booting or rebooting the host server or running the command for recognizing devices, complete the following:
  1. Create the Thin Image pair.
  2. Store the snapshot data (or clone pairs).
  3. Ensure the V-VOL pair recognized by the host server is in "PSUS" status or an unpaired volume.

If you do not fulfill all of the conditions listed above, the devices may not be recognized, or failures can occur and the host server can stop.

If you booted or rebooted host servers, or if you used the host server to run the commands to recognize devices and the host server was stopped, use the following workflow to run the commands:

1. Forcibly stop the process of the command and those of its parent process.
2. Create the Thin Image pair.
3. Store the snapshot data (or clone pairs).
4. Rerun the command to recognize devices.

On the server (including CCI), the emulation type of the V-VOL is shown with a zero (0), such as OPEN-0V. If you create a Thin Image pair, specify a volume whose emulation type is shown with a zero (0) for the S-VOL, such as OPEN-0V.