11.29.2003 and 11.30.2003 - ns, mail, mysql, cp and pg.hsphere.cc

[bigdave]

ns.hsphere.cc, mail.hsphere.cc, mysql.hsphere.cc and pg.hsphere.cc will be going down this Saturday, November 29th, 2003 approx. 10AM EST. We will be separating these machines from logical servers to physical servers. They will be down for approx. 3 hours but it could be longer. Please read the forums for updates. Also on Sunday, November 30th, 2003 at approx. 10AM EST we will be doing the same move for cp.hsphere.cc and ns1.hsphere.cc. Again please keep and eye HERE!! For updates

The new IP address for the machines are as follows:

mysql.hsphere.cc = 216.157.145.40

pg.hsphere.cc = 216.157.145.50

mail.hsphere.cc = 216.157.145.20

If you have any scripts that use the IP address of these machines instead of the host name you will need to update them

[antic]

Thank Dave. Will the IP address of ns1 be changing then?

Eventually, but we changed the IP for CP for now. The old IPs will be moved with NS and NS1

[gadgetgal99]

Is this really a good weekend to do this? It is Thanksgiving weekend in the US and is the official start of the Christmas shopping season. Won't taking mail and mysql down during the day on that Sat and Sun cause quite a disruption for e-commerce sites? I could see at night or much earlier in the AM but not at 10am EST on Thanksgiving weekend.

[admin]

Originally Posted by gadgetgal99

Is this really a good weekend to do this? It is Thanksgiving weekend in the US and is the official start of the Christmas shopping season. Won't taking mail and mysql down during the day on that Sat and Sun cause quite a disruption for e-commerce sites? I could see at night or much earlier in the AM but not at 10am EST on Thanksgiving weekend.

Good question, but we would get that all the way up to xmas.. We really need to get the stuff moved over, as you can see from the NT26 NT27 move users asked why we did it night our time day there time, now we get why are we doing in the day and night..

We try and do it when we are best staffed for it for the most part to make sure it goes as smooth and as fast as it can, from what matt has said the down times might end up being a lot less as he may of found a way to do it with rsync that may cut the time down but this will be the first time trying that so we will see..

3 Hours was very giving, I'm going to get mail up first, then ns, then mysql.

mysql will only be down becuase I need to use the hard drive to move ns and mail :/

[thecomputerpro]

I am behind you guys! Whatever you think is best.

My main customer of hosting and other services are on NT26 and NT27 and they did "not even notice downtime" during the switch. Not to mention, the next day when they got to work, all their stuff worked!

So, I am all for making the changes and I think that I would rather it be on a Saturday this week, then midweek any other time!

Go Matrix!

[antic]

heh... I was only joshin with you about the day/night thing Brad - I put a smiley on the end and everything!

My only concern here is that - if you change the IP addresses for NS and NS1, doesn't that mean that all us resellers will have to modify our name server IP addresses with GoDaddy or whomever, making all our sites go down for up to 24 hours?

If both IPs are on the machine, they wont go down. Thats why we are keeping the old IPs (65.57.231.100 for ns and 65.57.231.120 for ns1) with the namesevers

[antic]

Sorry, my misunderstanding; I thought you were going to change ns and ns1 to different IP addresses. doh!

[Webatvantage]

What will the new IP-adress of ns.hsphere.cc and ns1.hsphere.cc be?
Will these changes also affect my nameservers which point to the same IP-addresses?
Thanks,
Lieven

We are currently working on upgrading these servers the expected downtime is around 3 hours.

Threads Merged

[ark2000]

Are the messages that were being sent to those mail servers preserved?

or are they returned as undeliverable?

The remote MTA should defer the message if they follow the rules.

[ark2000]

would be great if you had a back up plan in case they didn't and the message would bounce.... no?