VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 132
Step 2. Using the information discovered in the previous step, identify the
volumes to which the snapshot plexes originally belonged, and
reattach them to those original volume as in the following command:
# vxplex att original_volume plex1 [plex2 ...]
Crash Recovery after using vxassist -o resyncfromreplica snapback
snapvol
• Problem: When you use the following command:
# vxassist -o resyncfromreplica snapback snapvol
to execute a snapback operation (resynchronizing from the replica volume),
and the system crashes while the operation is still in progress, you will find,
when the system comes back up, that the original volume fails with the
following error message:
vxvm:vxvol: ERROR: Volume original_volume has no CLEAN or \ non-volatile
ACTIVE plexes
• Workaround: To correct this situation, you should use the following
procedure:
Step 1. Disassociate all STALE plexes from the original volume:
# vxplex dis staleplex1 [staleplex2 ...]
Step 2. Convert all SNAPTMP plexes in the original volume to ACTIVE:
# vxplex convert state=ACTIVE tmpplex1 [tmpplex2 ...]
Step 3. Restart the original volume:
# vxvol start original_volume
Step 4. Reattach the plexes that you disassociated in step 1:
# vxplex att original_volume staleplex1 [staleplex2 ...]
This procedure results in a full synchronization of these plexes from the original
volume.
VEA Issues
The following issues have been identified as VEA problems, and will be
fixed in either patches or a future release of VxVM.
Connecting to X Windows The following X Window System error
may occur when starting VEA:
Xlib: connection to "hostname:0.0" refused by server
Xlib: Client is not authorized to connect to Server