I would agree with Peter. PowerShell is the ticket. This is the one liner I have setup. This assumes you have a network share called server with a network share of netapp_luns.. It creates a text file with the server name, dumps to the local C:\, then copies to a network share..
@echo off
sdcli disk
list >"c:\%computername%_disks.txt"
From someone who told me once.. hint Peter..
“Share and
enjoy!”
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Learmonth, Peter
Sent: Tuesday, October 09, 2012 4:48 AM
To: steve klise; Raj Patel; Andrew Laurence
Cc: toasters@teaparty.net
Subject: RE: LUNs lost initiator setting after a power
outage
Igroups and LUN mappings are captured in autosupport. You might consider adding a data capture email that receives things like autosupports and having your NetApp devices copy asup there as well as to NetApp. Even if you don’t capture it yourself, anybody at NetApp including support and your account team should be able to look that up and send it back to you.
Another thought is PowerShell toolkit has cmdlets (Get-NaLun, Get-NaLunMap,
Get-NaIgroup) for capturing this data. You could probably even save it as an object or XML and use that to audit changes or even script fixes for when weird stuff happens.
For those unfamiliar with the NetApp PowerShell Toolkit, check out the following:
I hope this
helps!
Peter
For what its worth, I have a scheduled AT job on the windows box that dumps the snapdrive connected LUN info to the local C:\ as well as a network share. That way if I loose a server, I know what was mapped, drive letters (if applicable).. Its my self
documentation for LUNS on my windows boxes.
Real easy to setup..
http://www.gossamer-threads.com/lists/netapp/toasters/10436#10436
The initiators disappeared and I spent a decent chunk of a weekend putting them back. Lucky I had screenshots and terminal dumps as I didn't have backups of this info.
So, this was fun.
After a power outage on Saturday, our Exchange 2010 mailbox servers (all hosted on VMWare ESX) came up with only some of their LUNs.
These LUNs are hosted on our HA-paired FAS2040 (OnTAP 7.3.4); each LUN hosts an Exchange database. Try as we might, we couldn't get these LUNs to mount.
After opening a support case with each of NetApp and Microsoft, and conferencing in both engineers, and several hours, the Microsoft engineer finally suggested we check the target LUNs on the filer. Turns out that each of the missing LUNs no longer had the setting for the mailbox servers' initiators. After checking that box the LUNs mounted without issue.
Anyone seen this happen before? The NetApp engineer didn't have any immediate ideas, and I haven't had luck finding a match in the list archives or in NOW.
Thanks,
Andrew
--
Andrew Laurence Office of Information
Technology
atlauren@uci.edu University of California, Irvine
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters