HP P6000 Replication Solutions Manager Administrator Guide (T3680-96069, June 2012)

Cross-operating-system mounting
Cross-operating-system mounting is supported on Windows 2003 x86 64-bit, Windows 2003
x86 32-bit, Windows 2008 x86 64-bit, and Windows 2008 x86 32-bit systems.
Cross-operating-system mounting requires the systems run the same operating system version. For
example, mounting across Windows 2008 x86 64-bit to Windows 2008 x86 32-bit systems or
mounting across Windows 2003 x86 64-bit to Windows 2003 x86 32-bit. Also, HostVolumes
on basic disks on Windows 2003 can be replicated and mounted on Windows 2008.
For all other operating system configurations, snapshots, snapclones, and mirrorclones created by
the replication manager can be dynamically mounted via a replication manager job to hosts that
are running the same operating system version as the host that owns the source volume. Variations
in volume managers and file system implementations prevent cross-operating-system mounting.
HP-UX
This section describes special replication procedures for HP-UX hosts.
Assigning multiple paths to new host volumes on HP-UX
The job commands CreateHostVolume and CreateHostVolumeGroup assign only one path
to new host volumes. If you use HP-UX PVLinks and need multiple paths, use PVLinks to add paths
after the host volumes are created.
The replication manager allows coexistence, but does not create the link. See the HP P6000
Replication Solutions Manager online help for more information.
Avoiding long delays or time-outs on HP-UX
If an HP-UX host has multiple disk devices with failed or no longer presented LUNs behind them,
it can take an increasingly long time to gather host information as the number of disk devices
increases. If an HP-UX host exhibits time-outs on host discovery or failed jobs while waiting for host
operations to complete, take the following actions:
• Check the disk devices showing long time-outs. For HP-UX versions earlier than 11.31, Secure
Path can display the status of the disk devices it is managing. For disk devices not managed
by Secure Path, check for I/O time-outs by running an OS tool such as diskinfo on each
disk device.
Remove any disk devices that show long time-outs, if they are no longer needed. See manpages
insf(1M) and rmsf(1M).
• If the disk devices are in this state intentionally, improve performance by modifying the I/O
time-out setting for those disks with the pvchange –t command. HP-UX has a default I/O
time-out of 30 seconds for SCSI disks. The pvchange –t command allows you to reduce the
amount of time before a time-out on a given disk occurs. Reducing the time-out decreases the
amount of time a host discovery takes.
LUN cannot be reused with different worldwide ID
The HP-UX 11.31 (11i v3) operating system security feature prevents a LUN from being reused
with a different worldwide ID (WWID). This can cause an authentication failure when presenting
snapshots to a host.
Resolution 1: Use the replication manager to present snapshots.
Resolution 2: If you are not using the replication manager to present snapshots, manually issue the
rmsf command on the devices that are being unpresented.
36 Working with operating systems