Unix4 Migration 5/22/06

[Dean]

On Monday 5/22/06 we will be migrating user data and settings from Unix4 to a new server.

Start time (Eastern): 2:00 PM Monday 5/22/06

End time (Eastern): 10:00 PM Monday 5/22/06

This is being done in response to a quota issue which can only be corrected by reinstalling the server's OS.

In an effort to minimize downtime for users, we have installed a new server which will run in parallel with Unix4. The user data will be copied while the server is live. When the data migration is complete, we will set Unix4's IPs on the new server.

The FTP service on Unix4 will be disabled at the start of the data migration in order to minimize content changes. All other services will remain online during the procedure.

Since the majority of the migration will be done while the server is live, we expect less than 1 hour of total downtime.

[TicoGrande]

I am not sure why this is being done in the daytime. Something like this, where you know the server will be offline should be scheduled so that any downtime for the USA occurs in the middle of the night.

Yes, I know there are users in other countries, but the last I heard, the vast majority of resellers were in the US time zones.

Why cannot this change be started at 6PM EST and finished at 2AM EST with the expected downtime (I am guessing here) being the last hour and thus minimizing the possible complaints?

TG

[Dean]

Yes, I know..everyone would love for all maintenance to take place on Sunday mornings at 2AM.

I don't want to sound rude, but this comes up every time we do maintenance no matter when its scheduled. We DO think about how downtime will affect customers and we DO take steps to minimize it...such as investing in a second server for an OS reinstall.

Something few resellers take into account is that our labor is also a limited resource, so we can't have all maintenance done in the middle of the night. Sometimes we need to schedule procedures when we have the best coverage and the right staff on hand. If this were something that would cause significant downtime, then yes, it would probably be scheduled differently. Since the original server will remain intact the entire time, the downtime for this operation is about as minimal as you can get.

The hour in the original notice is worst case. In all likelyhood, the downtime will be as long as it takes the core switch to accept the new ARP for Unix4 2.0.

[mresell]

I don't think it was rude Dean.

[Silverbug]

hmm i agree too, there is usally a reason why things are done at the times they are, esp if the time isnt at 2am on sunday morning.

[Dean]

The Unix4 maintenance is now starting. FTP will be taken offline shortly.

[Dean]

Believe it or not, we're done. Quotas have been restored and they are being reported properly in the CP.

[mdallarosa]

Great job!!. Thank You