My 2 pence:
Let everyone know well in advance and schedule a time when everything front end can be shut down/disconnected. It's more painful and requires more scheduling but it reduces any risk of lost data/corruption if anyone is in the middle of an operations. Remember to check is any backups are still running, we got caught on this last week and took 1/2 hour to check that that all the TSM sessions had been disconnected. Disable autosupport before you reboot the filer each time, and check if it renables after booting. Saves a lot of calls and open support cases from NetApp support.
Regards Martin
Enterprise Storage Architect/Enterprise Server Group
"Endeavours succeed or fail because of the people involved. Only by attracting the best people will you accomplish great deeds."
email/Blackberry: mailto:martin.hughes@halliburton.com cellphone: +1 713 303 9214 office: +1 713 676 5921 pager: mailto:7243058655@pagebb.com
-----Original Message----- From: Ambrose_Earle@shamrockfoods.com [mailto:Ambrose_Earle@shamrockfoods.com] Sent: Wednesday, May 01, 2002 7:43 PM To: toasters@mathworks.com Subject: Data ONTAP Upgrade Procedures
We are getting ready to upgrade to 6.2R1 on our F840C's and I was wondering what procedures some of you follow when doing upgrades. I am especially interested in hearing from those with Oracle databases NFS mounted to UNIX servers.
Do you shutdown the databases before doing anything? Do you leave everything NFS mounted running as normal during the entire procedure? Do you leave clustering enabled and just takeover-giveback to complete the reboot after the download?
Any pros/cons and horror stories are greatly appreciated,