Veritas Volume Manager 5.1 SP1 Troubleshooting Guide (5900-1507, April 2011)

To recover from the failure of the vxsnap make command for space-optimized

instant snapshots

◆

Type the following command:

# 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.

Recovering from the failure of vxsnap restore

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

DISABLED state.

To recover from the failure of the vxsnap restore command

◆

Type the following command:

# vxvol [-g diskgroup] start volume

Recovering from the 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.

To recover from the failure of the vxsnap reattach or refresh commands

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

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

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

# vxmend [-g diskgroup] clear tutil0 volume

Recovering from instant snapshot failure

Recovering from the failure of vxsnap restore