I have few clarifications to make , appreciate if someone could help me -
1) We are upgrading isilon code from 8.0.0.4 to 8.1.0.4 , Does it require a reboot prior to starting the upgrade and since it is a major upgrade will it reboot all the nodes simultaneously ?
2) We have a Prod and DR environment , is it advisable to do the DR first and then Prod to be on a safer side ?
3) I understand the there used to be interruption of services in older codes 7.0 & 7.1when upgrading , does it still stand for new 8.0 to 8,1 code
4)The manual mentioned that the customer needs to backup any custom configuration prior to upgrade . could some one site few examples on such instances where customer needs to backup as I am new to this customer environment and I am not sure what custom configuration in place
1) i just did this upgrade on 4 clusters. It's a normal rolling reboot, one node at a time. I don't ever reboot my clusters prior to the upgrade.
2) I always upgrade DR first and Prod the next day
3) Not sure what you mean, same as before where CIFS clients get disconnected and NFS clients get moved to other nodes
4) I can't think of customer configuration that would not survive an upgrade, my custom sysctl settings seem to survive between upgrades. For example a sysctl settings for session TTL.
just like to agree with Dynamox, did a 20 node last weekend, other than the complete guesstimate of time for the upgrade ( out by 40 % ). Upgrade was seemless to end users and no config was lost.
Few followup uestions, appreciate if you guys could help.
1) I have seen customers doing DR upgrade first, is this because it is a safe approach and does rebooting the DR cluster has same result , i,e SMB users will get disconnected ?
2)Also, We are going for a major upgrade , ie. 8.0 to 8.1 and the document says it needs to be a simultaneous upgrade . Can we still do a rolling upgrade ?
3)finally , CE is asking to better power cycle the cluster as it has not been done since one year ..In case we have to do a powercycle should I inform the SMB clients about the activity ? It will be done during off hours(weekend if possible) and I am not expecting users getting impacted ,but wanted to know if SMB and NFS users need to be notified for the upgrades ?
From where can we download the tool -EMC Assessment Workbench, which has a sub-component , File System Assessment included in this tool (FSA), exceptionally useful when trying to determine workloads, file types, file sizes, access trends, growth, etc.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
2973
1
Posted August 16th, 2018 04:00
1) i just did this upgrade on 4 clusters. It's a normal rolling reboot, one node at a time. I don't ever reboot my clusters prior to the upgrade.
2) I always upgrade DR first and Prod the next day
3) Not sure what you mean, same as before where CIFS clients get disconnected and NFS clients get moved to other nodes
4) I can't think of customer configuration that would not survive an upgrade, my custom sysctl settings seem to survive between upgrades. For example a sysctl settings for session TTL.