Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Chapter 2, Recovery from Failure of Instant Snapshot Operations

Failure of vxsnap make for Space-Optimized Instant Snapshots

Failure of vxsnap make for Space-Optimized Instant

Snapshots

If a vxsnap make operation fails during the creation of a space-optimized instant

snapshot, the snapshot volume may go into the INSTSNAPTMP state. VxVM can usually

recover the snapshot volume without intervention. However, in certain situations, this

recovery may not succeed. If this happens, use the following command to delete the

snapshot volume:

# vxedit [-g diskgroup] rm snapshot_volume

Alternatively, the snapshot volume is removed automatically when the system is next

restarted.

If the vxsnap make operation was being performed on a prepared cache object by

specifying the cache attribute, the cache object remains intact after deleting the snapshot.

If the cachesize attribute was used to specify a new cache object, the cache object does

not exist after deleting the snapshot.

Failure of vxsnap restore

If a vxsnap restore operation fails, the volume being restored may go into the

DISABLED state. Use the following command to start the volume:

# vxvol [-g diskgroup] start volume

Failure of vxsnap reattach or refresh

If a vxsnap reattach or refresh operation fails, the volume being refreshed may go into

the DISABLED state, be marked invalid and be rendered unstartable. You can use the

following command to check that the inst_invalid flag is set to on:

# vxprint [-g diskgroup] -F%inst_invalid volume

Use the following steps to recover the volume:

1. Use the vxmend command to clear the volume’s tutil0 field:

# vxmend [-g diskgroup] clear tutil0 volume

2. Use the vxsnap command to dissociate the volume from the snapshot hierarchy:

# vxsnap [-g diskgroup] dis volume