Netapp locked or busy snapshots. 'Busy because of LUN clone'

Netapp are locked/busy snapshots due to LUN clone, initiator mappings. Netapp on ONTAP 8.x, using FCP initiators.

>snap list

  %/used       %/total  date          name
----------  ----------  ------------  --------
 27% (27%)   14% (14%)  Jan 1 08:15  {360e0a4e-c746-43b4-2eb0b56a2} (busy,LUNs)


netapp90> snap delete Data05 {360e0a4e-c746-43b4-2eb099eb56a2}
Snapshot {360e0a4e-c746-43b4-2eb099eb56a2} is busy because of LUN clone

-At this point verify no mappings to initiators, if there are mappings remove them

netapp90> Sat Jan 1 08:29:50 [netapp90: lun.map.unmap:info]: LUN /vol/Data05/{0854e947-10d3-4ab5-86d511f3d741}.rws unmapped from initiator group viaRPC.51:00:01:24:4f:01:ae:2e
Jan  1 08:29:50 [netapp90: lun.map.unmap:info]: LUN /vol/Data05/{0854e947-10d3-4ab5-86d511f3d741}.rws unmapped from initiator group viaRPC.51:00:01:24:4f:01:ae:2e
Jan  1 08:29:50 [netapp90: lun.destroy:info]: LUN /vol/Data05/{0854e947-10d3-4ab5-86d511f3d741}.rws destroyed

netapp90> snap list Data05
Volume Data05
working...

  %/used       %/total  date          name
----------  ----------  ------------  --------
 27% (27%)   14% (14%)  Jan 1 08:15  {360e0a4e-c746-43b4-2eb099eb56a2}

netapp90> snap delete Data05 {360e0a4e-c746-43b4-2eb099eb56a2}
Jan  1 08:30:48 [netapp90: wafl.snap.delete:info]: Snapshot copy {360e0a4e-c746-43b4-2eb099eb56a2} on volume Data05 NetApp was deleted by the Data ONTAP function snapcmd_delete. The unique ID for this Snapshot copy is (35, 289451).

Commvault SnapBackup/ Netapp SnapProtect Configuration

Commvault's description:

"Simpana 8 - SnapBackup
New SnapBackup feature integrates seamlessly with hardware-based snapshot technologies to create persistent application and data consistent recovery copies directly from snapshots, bypassing the production server and virtually eliminating the need for an operational backup window. Simpana software removes the configuration and management complexity normally associated with snapshot management, creates a unified policy management framework for multiple pre-certified storage vendors including EMC and NetApp and offers point and click recovery points from any storage tier (online, nearline, offline)..........."

-For the actual commvault configuration so that it can manage the netapp array(s) and snapshots, commvault will have to be setup to talk to Netapp DFM host IP, and netapp credentials will be needed as per the screenshot below from the commvault management console:



-From there you can snap a host's lun (srv204) and restore the netapp lun snapshot to another host(srv4) [Following is the netapp output]:

netapp32> Jan 1 16:06:56 [netapp32: lun.map:info]: LUN /vol/srv204/MP_srv4_132408814_srv4 was mapped to initiator group cv_srv4_132_FC=2
Jan 1 16:07:24 [netapp32: lun.map.unmap:info]: LUN /vol/srv204/MP_srv4_132408814_srv4 unmapped from initiator group cv_srv4_132_FC
Jan 1 16:07:24 [netapp32: lun.destroy:info]: LUN /vol/srv204/MP_srv4_132408814_srv4 destroyed

Upgrading Brocade FOS and adding new Brocade FC switch

Steps to adding a new brocade(B-series) switch to an existing fabric. The new switch in will be an edge/subordinate switch in a core-edge topology.

Prerequisites:

• Brocade firmware version on new switch should be upgraded/downgraded as required by fabric/interop

Downgrade/Upgrade step if required:
swd21:admin> firmwaredownload
Server Name or IP Address: 10.2.1.3
User Name: anonymous
File Name: /v622b
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2
Password:
Server IP: 10.2.1.3, Protocol IPv4
Checking system settings for firmwaredownload...
System settings check passed.

You can run firmwaredownloadstatus to get the status
of this command.

This command will cause a warm/non-disruptive boot on the switch,
but will require that existing telnet, secure telnet or SSH sessions
be restarted.


Do you want to continue [Y]: y
Firmware is being downloaded to the switch. This step may take up to 30 minutes.
Preparing for firmwaredownload...
Start to install packages...
dir                         ##################################################
ldconfig                    ##################################################
 -------------------------output cut---------------------------------------
[5]: Jan 1 17:44:34 2012
Firmwaredownload command has completed successfully. Use firmwareshow to verify the firmware versions.

swd21:admin> firmwareshow
Appl     Primary/Secondary Versions
------------------------------------------
FOS      v6.2.2b
             v6.2.2b

• Setup 'switchname', snmp as required.
• Check date. set ntp server with 'tsclockserver set timezone' & 'tstimezone --interactive'
  
• Disable switch and set Domain ID (DID must unique)
• Check/clear config : cfgshow
• sw21:admin> cfgclear
  The Clear All action will clear all Aliases, Zones, FA Zones
  and configurations in the Defined configuration.
  cfgSave may be run to close the transaction or cfgTransAbort
  may be run to cancel the transaction.
  Do you really want to clear all configurations?  (yes, y, no, n): [no] yes 
• Now enable switch with 'switchenable'
 

Connecting new switch:

• You can connect the new switch via an ISL to the Core switch. ISL should be created similar SNMP message. You can also confirm via 'islsow' on both switches.

Info    Fabric Event    ISL [ Domain 21 (16) Port 16 (10) - Domain10 (a) Port29 (1c) ] Created    Jan 1 19:41:35 2012   

•  Clear port counters/errors on ISL and monitor.

Brocade Console cable

Brocade console cable pinouts for 200e and 5100s (tested). Works for DB9 to DB9 or RJ45 to DB9.

Cable Pinout

2 <----> 2
3 <----> 3
5 <----> 5

Netapp upgrade 8.0.1 7 mode

So the upgrade to 8.0.1, why would you want to goto 8.0.1 (general) here is a list. Please check other sources besides Netapp as well.

https://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/rnote/GUID-5A3E2A88-F6FA-4473-8127-81ED0C39FE89.html


If already at a 8.0 (like an RC) this should be easy enough, but run the upgrade adivisor.

Step 1: 

-Download 801_q_image.tgz (from link above) and copy to the netapp filers in /etc/software. Use CIFS to mount /etc$ from the netapp
-On netapp run sofware list to confirm that the filer sees the new image

Step 2:

-Check netapp syslog messages for errors or issues on filers, stop and confirm it is ok to go ahead with upgrade with Netapp support. Suggestion is to replace failed HDDs before starting upgrade.

Step 3:
-Generate autosupport with non-disruptive as syntax:  options autosupport.doit starting_NDU

Step 4:

From the filer backup to a machine other than the netapp filer
/etc/hosts
/etc/rc 

Step 5:

On filer run 'version -b', which will show the current firmwares and ontap version on the cfcard:

/cfcard/x86_64/diag/diag.krn:  5.4.7
/cfcard/x86_64/firmware/excelsio/firmware.img: Firmware 1.7.0
/cfcard/x86_64/firmware/DrWho/firmware.img: Firmware 2.4.0
/cfcard/x86_64/firmware/SB_XV/firmware.img: Firmware 4.3.0
/cfcard/x86_64/firmware/SB_XVI/firmware.img: Firmware 5.0.0
/cfcard/x86_64/firmware/SB_XVIII/firmware.img: Firmware 7.0.1
/cfcard/boot/loader: Loader 1.7
/cfcard/common/firmware/zdi/zdi_fw.zpk: PAM II Firmware 1.8 (Build )
/cfcard/common/firmware/zdi/zdi_fw.zpk: X1936A FPGA Configuration PROM 1.0 (Build 0x201558)

Step 6 (Do this on both filers):

We start the upgrade. Cifs will break and NFS may or may not.
netappA*> software update 801_q_image.tgz -r
software: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.
software: Depending on system load, it may take many minutes
software: to complete this operation. Until it finishes, you will
software: not be able to use the console.
cmd = ngsh -c system image update -node local -package file://localhost/mroot/etc/software/801_q_image.tgz -setdefault true
Software update started on node calnetapp1a. Updating image2 package: file://localhost/mroot/etc/software/801_q_image.tgz current image: image1
Listing package contents.
Untarring package contents.
Invoking script (validation phase).
INSTALL running in check only mode
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Available space on boot device is 594 MB
Required  space on boot device is 379 MB
Kernel binary matches install machine type
Package MD5 checksums pass
Versions are compatible
Invoking script (install phase). This may take up to 30 minutes.
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Available space on boot device is 594 MB
Required  space on boot device is 379 MB

Package MD5 checksums pass
Versions are compatible
Getting ready to install image
Directory /cfcard/x86_64/freebsd/image2 created
Syncing device...
Extracting to /cfcard/x86_64/freebsd/image2...
x BUILD
x CHECKSUM
x COMPAT.TXT
x INSTALL
x README.TXT
x VERSION
x cap.xml
x diags.tgz
x kernel
x perl.tgz
x platform.ko
x platfs.img
x rootfs.img
Installed MD5 checksums pass
Installing diagnostics and firmware files
Installation complete. image2 updated on node calnetapp1a
image2 has been set as the default
software: installation of 801_q_image.tgz completed.
Please type "reboot" for the changes to take effect.


Step 7: 
After installing the above on both filers
netappA> cf takeover [netappB will reboot at this time]
---------cut---------------
Wed Apr 13 22:24:55 PDT [netappA (takeover): cf.fm.takeoverComplete:notice]: Failover monitor: takeover completed
Wed Apr 13 22:24:55 PDT [netappA (takeover): cf.fm.takeoverDuration:info]: Failover monitor: takeover duration time is 6 seconds
Wed Apr 13 22:25:01 PDT [netappA (takeover): monitor.globalStatus.critical:CRITICAL]: This node has taken over netappB.
--------cut----------------

Step 8:

Netapp suggests waiting about 10 minutes between cf takeover and giveback.
netappA> cf giveback -f
--------cut----------------
Wed Apr 13 22:37:04 PDT [netappA: cf.fm.givebackComplete:notice]: Failover monitor: giveback completed
Wed Arp 13 22:37:04 PDT [netappA: cf.fm.givebackDuration:notice]: Failover monitor: giveback duration time is 3 seconds
--------cut----------------
-Run version on the filer that just rebooted and confirm the new version.

Step 9:

Do the same steps for the other filer in the cluster.

Step 10:

Check services, I found CIFS had to be restarted.

Moving Exchange 2007 CCR storage group

Scenario: Certain mail store for needs to be moved to another drive. We will move West21 Users current on D: maibox to the G:\Exchdata\West 21 Users path

Steps required:
1.Suspend storage group copy. Can be done from Exchange Management console.
2.Dismount database
3.Move Database to new path (G:\Exchdata\West 21 Users)
4.From Exchange Management Shell run:

[PS] C:\Windows\System32>move-DatabasePath -ConfigurationOnly -Identity 'west
-cms\West21 Users\West21 Mailbox' -EdbFilePath 'G:\ExchData\West21 Users\West21 Mailbox.edb' 

5. Mount new database
6. Resume storage group copy