Thats good to know. We were about to upgrade our primary filers to 8.1.1 and we just finished an effort to upgrade SD on all our windows hosts to 6.3.1.x.. I hate how they keep updating this software. Its almost as bad a microsoft updates coming out all the time. Thanks
Date: Sat, 22 Sep 2012 12:53:23 -0700 From: rrue@fhcrc.org To: G.Milazzo@sinergy.it Subject: Re: R: Upgrading SnapDrive without reconnecting LUNs? CC: toasters@teaparty.net; klises@sutterhealth.org
Our DBA upgraded the passive node first, that's when the LUNs all disconnected.
BTW, I got confirmation from our NA SE that while older versions of SD might definitely work with DOT 8.1.1, the support matrix does require SD 6.4+
----- Original Message ----- From: "Milazzo Giacomo" G.Milazzo@sinergy.it To: "Randy Rue" rrue@fhcrc.org Cc: "Steve Klise" klises@sutterhealth.org, toasters@teaparty.net Sent: Saturday, September 22, 2012 12:24:58 PM Subject: R: Upgrading SnapDrive without reconnecting LUNs?
Mh. Sound strange. SD is a service running on top of volume manager...I've never had issue upgrading it: this does not cause communication interruption with LUNs I read about iSCSI, maybe something is wrong in the service dependency so that SD kill the iSCSI initiator too?
Anyway the road to upgrade the passive node first is the good one.
Regards,
-----Messaggio originale----- Da: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Per conto di Klise, Steve Inviato: mercoledì 19 settembre 2012 16:52 A: Randy Rue; toasters@teaparty.net Oggetto: RE: Upgrading SnapDrive without reconnecting LUNs?
What I have done in the past, was to get on the active node, update snapdrive, then update the passive node (assuming you are doing active/passive). All nodes should be at the same version. So, these are the steps I have done. You will also have to update the SMSQL to the same version as well.
Update snapdrive (may need to install hot fixes) update SnapManager If you are using MPIO, update (may need to install hotfixes) last step, install Netapp Host Utilities
I hate Microsoft clustering.. Sucks, and it can be complicated and a pain when it breaks.
Hope this helps.
Regards Steve Klise Storage Engineer, NCDA __________________________ PALO ALTO MEDICAL FOUNDATION SUTTER HEALTH INFORMATION SERVICES PENINSULA COASTAL REGION
Office: 408-523-3163 · Fax: 408-328-1406 e-mail: klises@sutterhealth.org
WARNING: "All e-mail sent to or from this address will be received or otherwise recorded by the Palo Alto Medical Foundation e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient." ________________________________________ From: toasters-bounces@teaparty.net [toasters-bounces@teaparty.net] On Behalf Of Randy Rue [rrue@fhcrc.org] Sent: Wednesday, September 19, 2012 7:49 AM To: toasters@teaparty.net Subject: Upgrading SnapDrive without reconnecting LUNs?
Hello All,
We're preparing to upgrade a v3170 running 7.3.5 to 8.1.1 and will first need to upgrade a number of SnapDrive clients to 6.4 or higher.
Our DBA's are testing the SnapDrive upgrade and so far have been unable to do so without needing to recreate all their connections (essentially the iSCSI disks mounted in the SQL cluster go away and they need to reconnect to the LUNs).
Is there a better way to do this? Seems like in a perfect world, we'd just run some .exe to upgrade SnapDrive, reboot and find all as it was?
Hope to hear from you,
Randy
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
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters