Netapp – Solving busy Snapshot error.

Recently, i came across this weird issue of busy snapshot at the destination volume. Whenever the Netapp’s snapmirror gets invoked and tries to delete the old snapshots at the destination and if it finds any snapshot to be busy, it will throw following error.

Snapshot snapshot_name in destination volume volume_name is in use, cannot delete.

Most of the times, this happens if one uses a software like SMVI to take a snapshot and then invoke the snapmirror to have a consistent data at the destination side. Although i didn’t find the exact reason behind this problem, i guess the erroneous condition occurs when these software try to remove the snapshot and at the same time face some connectivity issues with destination filer, interrupting the snapshot deletion and timeout in the process. The snapshot in question will be seen mounted as a Lun on destination filer in this case. ENSURE TO NOTE DOWN THE EXACT NAME OF THIS SNAPSHOT. In order to get this resolved the Lun associated with this snapshot needs to be deleted. Following steps will do that. However, ensure to double check whatever you will be doing, don’t hold me responsible for any data loss resulting through inaccurate execution of these commands.

First, break the snapmirror relation. This will make the destination volume writable.

snapmirror break <destination volume>

Next, use following command to show the path of Lun in question and copy that path.

lun snap usage -s <volumename> <snapshotname>

This will show the name of the LUN associated with the snapshot. NOTE DOWN THE NAME OF THIS LUN and execute

lun show  

Which will show the full path of the LUN.

Then destroy the Lun using following command

lun destroy <Path to the snapshot Lun>

Now verify the snapshot is not in use through filerview. If it isn’t then it’s good to go ahead and establish the snapmirror relationship.

snapmirror resync -S <srcfiler>:<srcvolume> <destfiler>:<destvolume>

Finally check using snapmirror status whether the replication is started properly.


Leave a Reply