i did actually follow this document because my snapshots are in busy state, but the issue is when i try to run the command [lun snap usage [-s] vol_name snap_name ] i get LUNs that are locking the deletion, when i try to destroy the LUN the systems shows that LUN doesn't exists, thats why i am asking if there is a way to ignore the snapshot owner in 7mode or maybe delete those LUNs somehow ?
When you compare the lun snap usage to the lun show output do you see the lun that you are trying to delete in "lun show"? The lun may already be deleted and you need to just delete the snapshot. Here is some additional information on deleting backing snapshot copies when a lun is deleted.
It sounds like there are some additional snapshots that might first need to be deleted before you can delete the original snapshot that is showing (busy, LUN). Let us know if turning on the snapshot_clone_dependency helps clear up the busy,LUN snapshot so it can be deleted.
I cannot see the lun when I use the command [lun show] and when I show the specific lun the output is [lun doesn't exists], I have deleted all the snapshots related to that volume except for the busy ones which cannot be deleted (the issue I am trying to solve) and I cannot find the option [snapshot_clone_dependency] on the system -> in advanced and regular mode I used the command [options] to view them all of them but I cannot find it.
Are you looking for the snapshot_clone_dependency in the options list for the ONTAP system?
fas01> options snap
If you are looking at the options you will not see the snapshot_clone_dependency option there. This is an option in the vol options. See below:
fas01> vol options
vol options: No volume name supplied.
vol options <vol-name> <option-name> <option-val>
The following commands are available; for more information
type "vol help options <command>"
acdirmax flexcache_autogrow nosnap snaplock_default_period
acdisconnected flexcache_min_reserve nosnapdir snaplock_maximum_period
acregmax fractional_reserve nvfail snaplock_minimum_period
acsymmax fs_size_fixed raidsize snapmirrored
actimeo guarantee raidtype snapshot_clone_dependency
convert_ucode maxdirsize read_realloc svo_allow_rman
create_ucode minra resyncsnaptime svo_checksum
disconnected_mode nbu_archival_snap root svo_enable
dlog_hole_reserve no_atime_update schedsnapname svo_reject_errors
extent no_i2p snaplock_autocommit_period try_first
What you want to do is run the following command: vol options <vol-name> snapshot_clone_dependency <on | off>
This is off by default so you will want to set it to on for the volume in question. Once it is on you should be able to go in and delete the snapshot in question.
I found the option is set to [on] so I made it [off] but still have the same issue, there is a lun locking the snapshot deletion which I can view by the command [lun snap usage] but I can't find or destroy that lun
If you have already followed it, then could you share the 'snap list' and 'vol status -v' output from your filer ? If you cannot share the details, you may try raising a ticket, engineer might help you resolve this via remote session.
The snapshot naming 'sqlsnap__*' indicates that these snaps are by-product of "SnapManager for SQL Server". Could you login to your SMSQL (Windows) box (Which would also have snapdrive installed) and take a look at the cloned luns. It may not be connected to hosts but it will be existing inside a snap. You can try splitting,deleting clone using 'snapdrive' first and then snaps could be deleted.