Recovering from the failure of vxsnap refresh


Recovering from the failure of vxsnap refresh
Prev	Recovering from instant snapshot failure	Next

If a vxsnap refresh operation fails, VxVM attempts to restart the resynchronization when the volume is recovered. The volume starts with the synchronization in the background.

This procedure requires that the disk group version is 170 or later.

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 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
```
Use the following command to start the volume:
```
# vxvol [-g diskgroup] start volume
```
Clear the source volume's tutil0 field (if it is set). Enter the following command:
```
# vxmend [-g diskgroup] clear tutil0 source_volume
```
Rerun the failed vxsnap refresh command.
This results in a full resynchronization of the volume. Alternatively, remove the snapshot volume and recreate it if required.

Prev	Up	Next
Recovering from the failure of vxsnap restore	Home	Recovering from copy-on-write failure