A place where the Joyent community can gather, help each other out, and stay informed.
You are not logged in.
Ok, so looking back at the last time we moved servers (a little further down in this forum) I think the best way to handle a schedule is to give y'all a flexible window, and update things as we perform the migrations.
Here's our schedule, and depending on how smoothly/roughly things go (should be a breeze) we may move schedules up (yay) or back (hopefully not).
Wednesday: one.textdrive.com first, barclay.textdrive.com second
Thursday: bidwell.textdrive.com first, nelson.textdrive.com second
Friday: pendrell.textdrive.com first, davie.textdrive.com second
Saturday: gilford.textdrive.com first, beers.textdrive.com second
(get it? beers.textdr..... it's a joke, laugh please...)
We'll be commencing things roughly 14:00 GMT on each of these days, and will be disabling webmin/usermin for the period of time in which we're moving the configurations, so as not to have to worry about missing a last minute change made by anyone. I'd expect that Wednesday will take most of the day as we get our migratin' legs again, and the rest of the week should go quicker. Per server should take anywhere from 4-8 hours to completely finish off everything and get things rsync'd before we flip the DNS switch and give you third party DNS folks the go-ahead. Watch the forums (http://forum.textdrive.com) for updates during the days. We'll open an announcements thread for each server as we work through the process.
As with previous migrations, we'll be disabling Urchin log tracking for a bit while we work out the license migrations, and we'll set the scheduler to pull in all the logfiles so that any days missed in transition will not be blank.
As always, please feel free to email migration@textdrive.com with any questions, concerns or comments you may have about this process.
Offline
ryanschwartz wrote:
(get it? beers.textdr..... it's a joke, laugh please...)
Hee?
I'll likely be on a plane while my server is migrated, so sounds good to me. Hopefully I can resist the urge to find 'net when I land to see how things have progressed.
Offline
Hee Haw!
One is first huh!
Offline
Guess i'm last. Oh well, good things come to those who wait.
Offline
Yep, One is the alpha test, Barclay is the beta, then the rest of y'all get to reap the benefits of all the accumulated "Okay, let's not do THAT again" knowledge... :)
Offline
My thoughts exactly Nukenin. Hopefully those 'migrating legs' will come back quickly and lessons learned from the last server swap will come rushing back.
Offline
What are the chances of downtime for this type of move? It's more of a replacement than a move, isn't it?
If so, when does the possibility for downtime come in?
Offline
If I undertand this correctly, there should not be any downtime since the old & new servers will both be online. The potential problems are that you might update the old one after the new one has been sync'd, so you might lose that information. That's why they've asked for us to hold off on updates, etc. during the move.
Once the servers are in sync they flip the DNS pointers and the new servers are off to the races.
I'm sure that an Admin will correct this if I'm wrong. ...right guys?? :)
Offline
that's right Moon, and since the DNS is done at DNSME, the TTL is very very short.
there will be no routing issues - except for those who don't have DNS handled by TextDrive. any people in that camp have decided to take the matter into their own hands and should know enough to mash the right buttons at the right time.
Offline
In the West, the firsts they called the pioneers.
Offline
What can I do to minimize the amount of email delivered to the old server while DNS propagates? I'm using 3rd party DNS and have set the TTL on all the records to 60. Anything else I should do?
Offline
except for those who don't have DNS handled by TextDrive
By "DNS handled by TextDrive" do you mean having nameservers dns{1-4}.textdrive.com ?
If I have those as my nameservers, is my DNS thus handled by TextDrive?
Last edited by odinsdream (2005-08-23 17:01:31)
Offline
odinsdream wrote:
except for those who don't have DNS handled by TextDrive
By "DNS handled by TextDrive" do you mean having nameservers dns{1-4}.textdrive.com ?If I have those as my nameservers, is my DNS thus handled by TextDrive?
Yes!
Offline
ryanschwartz wrote:
I'd expect that Wednesday will take most of the day as we get our migratin' legs again, and the rest of the week should go quicker. Per server should take anywhere from 4-8 hours to completely finish off everything and get things rsync'd before we flip the DNS switch and give you third party DNS folks the go-ahead
One question... just for the sake of asking a question... what's the theory/rational in picking the migration order? I'm just using my thinking/logic here, which is often flawed, but why wouldn't one migrate the lower density servers first as a way to get the "migratin' legs again"?
Offline
riscky wrote:
One question... just for the sake of asking a question... what's the theory/rational in picking the migration order? I'm just using my thinking/logic here, which is often flawed, but why wouldn't one migrate the lower density servers first as a way to get the "migratin' legs again"?
More cranky people on higher density servers?
EDIT: This was a throwaway joke!
Last edited by Alex (2005-08-23 22:01:50)
Offline
the order is historical. one was the first one here, barclay was second. It's just wired in the brain that way. It's how updates occur etc.
Offline
jason wrote:
the order is historical. one was the first one here, barclay was second. It's just wired in the brain that way. It's how updates occur etc.
That said, as I said above, this is not a bus schedule. We'll be doing initial rsyncs tonight so that the incremental changes pulled over the wire are smaller when we actually get to the point of doing the 'real' migration. If things take longer, cut us some slack. If things go quicker, be ready to change your DNS (if that applies to you), and cheer loud.
Here's hoping for good winds and fair weather for the hefty job ahead. Thanks in advance to all the staffers for an incredible outpouring of energy and expertise. We love ya!
Offline
Alex wrote:
More cranky people on higher density servers?
Which is why I would think you would want to do them last... less down turn the crankyness down... and address any potential issues else where...
jason wrote:
the order is historical. one was the first one here, barclay was second. It's just wired in the brain that way. It's how updates occur etc.
I assumed that was the reason...
ryanschwartz wrote:
We'll be doing initial rsyncs tonight so that the incremental changes pulled over the wire are smaller when we actually get to the point of doing the 'real' migration. If things take longer, cut us some slack. If things go quicker, be ready to change your DNS (if that applies to you), and cheer loud.
I would think lower density servers less crany people (see Alex statement above) more slack... I know you guys know what your doing... so no worries here.
Offline
Ryan: Here's hoping for good winds and fair weather for the hefty job ahead. Thanks in advance to all the staffers for an incredible outpouring of energy and expertise. We love ya!
Second!
Ryan: (get it? beers.textdr..... it's a joke, laugh please...)
Darn. And I thought I was getting a server named after me.
Last edited by cameron (2005-08-23 21:54:19)
Offline
Just curious... how are you guys planning on moving stuff like mysql databases? I mean, if the database is getting updated when the move is occuring, how on earth do you sync that?
Offline
ryanschwartz wrote:
That said, as I said above, this is not a bus schedule. We'll be doing initial rsyncs tonight so that the incremental changes pulled over the wire are smaller when we actually get to the point of doing the 'real' migration. If things take longer, cut us some slack. If things go quicker, be ready to change your DNS (if that applies to you), and cheer loud.
Don't know how public transportation is in the US, but over here that's pretty much what a bus schedule is.
Offline
I just have to say how happy and proud I am of TXD. First hand (I'm on the staff lists, but don't help out as much as I'd like to) I can tell how hard all the staff has been working. This is gonna be a great big step for TXD.
Last edited by noel (2005-08-23 23:59:42)
Offline
rainbowsheep wrote:
Just curious... how are you guys planning on moving stuff like mysql databases? I mean, if the database is getting updated when the move is occuring, how on earth do you sync that?
Easy. Rsync the data directory, and restart mysql on the receiving box.
Offline
Marten wrote:
Don't know how public transportation is in the US, but over here that's pretty much what a bus schedule is.
Public Transportation in most of the US is about as reliable and fun to use as Windows.
Offline
So after all this moving business is done, you guys can start accepting new customers get on the list, right?
Last edited by Hans (2005-08-24 03:49:48)
Offline
ryanschwartz wrote:
rainbowsheep wrote:
Just curious... how are you guys planning on moving stuff like mysql databases? I mean, if the database is getting updated when the move is occuring, how on earth do you sync that?
Easy. Rsync the data directory, and restart mysql on the receiving box.
I hope you flush the data to disk before the sync ;)
Offline
Where's One?
Offline
I'm not sure which server I'm on but SFTP isn't working - I do have access to my website publicly. Pairnic does my DNS management BUT the nameservers are set for DNS1.TEXTDRIVE.COM etc.
I assume I don't need to do anything with DNS as per Christopher's response above? But I also thought from above posts that this would mean no downtime.
Not frustrated; TextDrive rocks; just wondering and planning.
(UPDATE: Connection working as of 10:11 AM PDT; down again at 10:15 A.M. Okay, time to kick back for a couple of hours.).
Last edited by RussLipton (2005-08-24 17:18:18)
Offline
One is up. Mail and everything.
Offline
In light of some problems today, we're going to be postponing the migration 2 days. I'll post a more concrete schedule later tonight, but we won't be starting the 'lock down webmin and start everything flipping over' until Friday PM, shooting for a bit before 00:00. More details to follow and terribly sorry for the delay. We want to have things go as smoothly as possible, and in the midst of all the issues today, we thought it better to wait until the 'quiet time' that is typically Friday night and the weekend.
Offline
