netapp 7-mode lun usage -s and lun clone dependency

create a lun and create a busy lun situation.
by default snapshot_clone_dependency is switched to off

If you switch it to on before the below actions then
you can delete a snapshot even if there are more recent
snapshots having pointers to lunblocks.
vol options volume_name snapshot_clone_dependency [on][off]

filer1> snap create lunvol_n1 snapbeforelun

filer1> options licensed_feature.iscsi.enable on
filer1> iscsi start
filer1> lun setup
This setup will take you through the steps needed to create LUNs
and to make them accessible by initiators. You can type ^C (Control-C)
at any time to abort the setup and no unconfirmed changes will be made
to the system.
---output skipped---
Do you want to create another LUN? [n]:

filer1> lun show -m
LUN path Mapped to LUN ID Protocol
/vol/lunvol_n1/lun1 win 0 iSCSI
On the windows system connect to the filer target with iscsi initiator and
use computer->manage->storage to rescan disks and initialise the new disk and
put ntfs filesystem disk.

filer1> snap create lunvol_n1 snapafterlun

filer1> lun clone create /vol/lunvol_n1/lunclone -b /vol/lunvol_n1/lun1 snapafterlun

filer1> lun map /vol/lunvol_n1/lunclone win
On windows rescan disks, mark partition as active and specify drive letter.
Now you can restore any files from the new (cloned) lun to the already existing lun

filer1> snap create lunvol_n1 snaprandom

filer1>snap delete lunvol_n1 snapafterlun
Snapshot snapafterlun is busy because of snapmirror, sync mirror, volume clone, snap restore, dump, CIFS share, volume copy, ndmp, WORM volume, SIS Clone, LUN clone

filer1> lun snap usage -s lunvol_n1 snapafterlun
You need to delete the following LUNs before deleting the snapshot
You need to delete the following snapshots before deleting the snapshot
Snapshot - hourly.0
Snapshot - snaprandom

This entry was posted in Uncategorized. Bookmark the permalink.

Comments are closed.