Scheduled Cl1 Win20, Win26 and Win30 migration to new Hardware node. Saturday & Sunday @00:00 AM CDT

ashwaniyadav

ashwaniyadav

Perch
This weekend, we shall move three cluster 1 servers ( Win20, Win26 and Win30) to a new upgraded hardware node. So services of these servers will down, while moving data. We shall perform only one server migration at a time and post detailed updates of each, before we start.

We will plan maintenance on 8 hour windows starting at midnight Saturday, and if we can move all in this time, we will strive to do so, if we cannot any remaining will move on Sunday starting at midnight.

We will move in the order of Win20, Win26, Win30. Each will have 1 to 2 hours of downtime if all goes according to plan. We cannot live move these due to some architectural differences in the hardware and network layouts.
 
Last edited by a moderator:
Win26, will not be moved in order, it has some delay in move due to the node needing a piece of software installed.

Win20 will be going down in the next 20 minutes, andonly down for a few minutes and then back up, Win30 will be next in about 1.5 hours or less. Also only a few minutes down. We've found a good way to minimize downtime and get the nodes moved even with the network and hardware differences!
 
Win26, we are going to wait and move tomorrow with the method that requires very little downtime. Less than a minute in most cases. We already had to reboot the server for win26 for software installs, and it won't be required again until the move it completed and only a few pings down.


We will move Win26 between 0:00 (midnight) and the 1:00am hour, so a one hour window tomorrow morning.
 
The server is up, there are a couple updates needed on it and we are going to proceed in doing them and it will reboot for those.
 
You must log in or register to reply here.
Back
Top