Wednesday night/Thursday morning I'll be upgrading the sixth and final node in the Novell cluster to NW6.5. Since this node hosts the Software volume, during this upgrade the W: drive will not be available. As this will be in the 1am-3am range, I don't expect many people to notice this.
However, since this is the last node in the cluster to get upgraded, this upgrade has an extra step. After Netware has rebooted after the file-copy and then starts the upgrade in ernest, it will then take a step guaranteed to cause heart-stoppage during term.
It'll take every single cluster resource off-line. All of 'em.
Then it'll mount the volumes on the node I'm upgrading, but in an unusable 'UPGRADE' state. It'll then upgrade the data structures in the partition tables and NSS trees to the format for NW6.5. Reportedly, this doesn't take long. When this is complete, it'll move all the volumes back to where they came from and put them online. Clearly, this isn't something we could do during term.
However, since this is the last node in the cluster to get upgraded, this upgrade has an extra step. After Netware has rebooted after the file-copy and then starts the upgrade in ernest, it will then take a step guaranteed to cause heart-stoppage during term.
It'll take every single cluster resource off-line. All of 'em.
Then it'll mount the volumes on the node I'm upgrading, but in an unusable 'UPGRADE' state. It'll then upgrade the data structures in the partition tables and NSS trees to the format for NW6.5. Reportedly, this doesn't take long. When this is complete, it'll move all the volumes back to where they came from and put them online. Clearly, this isn't something we could do during term.