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.
Date: Tue, 9 Oct 2012 17:02:10 +1300
Subject: Re: LUNs lost initiator setting after a power outage
From: phigmov@gmail.com
To: atlauren@me.com
CC: toasters@teaparty.net
Sounds similar to my experience a few years ago after a controller upgrade.
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.
Cheers,
Raj.
On Tue, Oct 9, 2012 at 2:54 PM, Andrew Laurence
<atlauren@me.com> wrote:
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
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters