we have a snapshot of a lun taken by snapmanager v6.x
no clones however snapshot states as busy,lun
have a case open with netapp, but am getting nowhere.
anybody have any clues ?
Hi Chaim,
On Wed, Jul 15, 2009 at 8:14 PM, Chaim Riegerlists@up-south.com wrote:
we have a snapshot of a lun taken by snapmanager v6.x
no clones however snapshot states as busy,lun
have a case open with netapp, but am getting nowhere.
anybody have any clues ?
Looks like a typical case of https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb16908
If not, check if SIS is active, if the volume has been involved in a snapmirror/snapvault relation that hasn't been cleaned up right, and that NDMP isn't keeping snapshots busy.
HTH & HAND!
Nils Vogels wrote:
Hi Chaim,
On Wed, Jul 15, 2009 at 8:14 PM, Chaim Riegerlists@up-south.com wrote:
we have a snapshot of a lun taken by snapmanager v6.x
no clones however snapshot states as busy,lun
have a case open with netapp, but am getting nowhere.
anybody have any clues ?
Looks like a typical case of https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb16908
If not, check if SIS is active, if the volume has been involved in a snapmirror/snapvault relation that hasn't been cleaned up right, and that NDMP isn't keeping snapshots busy.
HTH & HAND!
cant delete this lun, it contains an active db. [root@mon1 ~]# ssh fl1 snap list Account Volume Account working...
%/used %/total date name ---------- ---------- ------------ -------- 2% ( 2%) 1% ( 1%) Jul 14 23:00 sqlsnap__Account.0 6% ( 4%) 3% ( 2%) Jul 13 23:00 sqlsnap__Account.1 9% ( 3%) 5% ( 2%) Jul 12 19:25 nls1-sys-adm1-clisys(0118044480)_irfl1_Account_nonqtree-src.0 (snapvault) 13% ( 5%) 7% ( 2%) Jul 10 18:35 sqlsnap__iraccount_07-10-2009_21.35.04__daily (busy,LUNs)
[root@mon1 ~]# ssh fl1 lun clone split status [root@mon1 ~]#
root@mon1 ~]# ssh fl1 snap delete Account sqlsnap__iraccount_07-10-2009_21.35.04__daily Snapshot sqlsnap__iraccount_07-10-2009_21.35.04__daily is busy because of LUN clone
bluezman wrote:
Nils Vogels wrote:
Hi Chaim,
On Wed, Jul 15, 2009 at 8:14 PM, Chaim Riegerlists@up-south.com wrote:
we have a snapshot of a lun taken by snapmanager v6.x
no clones however snapshot states as busy,lun
have a case open with netapp, but am getting nowhere.
anybody have any clues ?
Looks like a typical case of https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb16908
If not, check if SIS is active, if the volume has been involved in a snapmirror/snapvault relation that hasn't been cleaned up right, and that NDMP isn't keeping snapshots busy.
HTH & HAND!
cant delete this lun, it contains an active db. [root@mon1 ~]# ssh fl1 snap list Account Volume Account working...
%/used %/total date name
2% ( 2%) 1% ( 1%) Jul 14 23:00 sqlsnap__Account.0 6% ( 4%) 3% ( 2%) Jul 13 23:00 sqlsnap__Account.1 9% ( 3%) 5% ( 2%) Jul 12 19:25 nls1-sys-adm1-clisys(0118044480)_irfl1_Account_nonqtree-src.0 (snapvault) 13% ( 5%) 7% ( 2%) Jul 10 18:35 sqlsnap__iraccount_07-10-2009_21.35.04__daily (busy,LUNs)
[root@mon1 ~]# ssh fl1 lun clone split status [root@mon1 ~]#
root@mon1 ~]# ssh fl1 snap delete Account sqlsnap__iraccount_07-10-2009_21.35.04__daily Snapshot sqlsnap__iraccount_07-10-2009_21.35.04__daily is busy because of LUN clone
Maybe you had a clone in the past, new snapshot were created of the volume and then the clone was deleted?
If this happened, you can check with the following command which snapshots need to be removed before you delete the locked snapshot.
lun snap usage account sqlsnap__iraccount_07-10-2009_21.35.04__daily
Hi Charm,
On Wed, Jul 15, 2009 at 8:39 PM, Chaim Riegerlists@up-south.com wrote:
Nils Vogels wrote:
Hi Chaim,
On Wed, Jul 15, 2009 at 8:14 PM, Chaim Riegerlists@up-south.com wrote:
we have a snapshot of a lun taken by snapmanager v6.x
no clones however snapshot states as busy,lun
Looks like a typical case of https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb16908
cant delete this lun, it contains an active db.
Didn't say you needed to ;)
Check why the snapshot is busy using lun snap usage, and delete snapshots (not the LUN!) to free up the busy state. The kb item pretty much tells you how to do it.
Greetings,
Nils
-
Chaim Rieger -
Nils Vogels -
Pascal Dukers