Moving servers

M

MtK

Verified User
Joined
Aug 2, 2007
Messages
405
Hi,
I am about to install a new machine (on another datacenter), with DirectAdmin.
This machine will obviously have a different set of IPs, and therefore a different set of NS records.

what is the best way to move all the clients from one server to another without having to:
1. move the clients one-by-one.
2. having to stop any server to the clients (at least minimize the damage).

Thanks,
Mati
 
You need to determine what downtime is acceptable to you.

and therefore a different set of NS records
Click to expand...

Not necessarily. The old server can still be the DNS server even though you have moved a client to another server.

This is what I do. This is a basic outline. As a system administrator it is assumed you know some basic things.

First Change the TTL of the zone files to a few minutes and then either wait past what the TTL was previously or wait until the next day.

You may not have to do one at a time if the size of the clients are small. I would do one first using the method below to determine how much downtime there will be for a client of a certain size. Only you can determine if it is acceptable or not.

Suspend the client.
Use the Admin Backup/Transfer to make the backup.
Transfer the backup to the new server.
Run the restore on the new server.
Unsuspend the client on the new server.
Change the ip for the client on the old server to the ip on the new server

After all clients are done then change the ip's for the nameservers.
 
floyd said:
You need to determine what downtime is acceptable to you.



Not necessarily. The old server can still be the DNS server even though you have moved a client to another server.

This is what I do. This is a basic outline. As a system administrator it is assumed you know some basic things.

First Change the TTL of the zone files to a few minutes and then either wait past what the TTL was previously or wait until the next day.

You may not have to do one at a time if the size of the clients are small. I would do one first using the method below to determine how much downtime there will be for a client of a certain size. Only you can determine if it is acceptable or not.

Suspend the client.
Use the Admin Backup/Transfer to make the backup.
Transfer the backup to the new server.
Run the restore on the new server.
Unsuspend the client on the new server.
Change the ip for the client on the old server to the ip on the new server

After all clients are done then change the ip's for the nameservers.
Click to expand...
thanks, that seems very straight forward.

let's assume I have on server1 (OLD):
ns1.SERVER.COM
ns2.SERVER.COM

how should I set the NS records for server2 (NEW)?
 
You set them the same way since you are going to be using the same nameservers.

It will not matter until you change the ip's at the registrar for the nameservers anyway. There will be no dns traffic on the new server until you do this.

Also change the ip's on the old servers for the nameservers last. You do have A records for the nameservers in your zone file right?

You might wait a day or so after this to make sure everything is working on the new server and little or no traffic on the old server and then shut down the old server.
 
floyd said:
You set them the same way since you are going to be using the same nameservers.

It will not matter until you change the ip's at the registrar for the nameservers anyway. There will be no dns traffic on the new server until you do this.

Also change the ip's on the old servers for the nameservers last. You do have A records for the nameservers in your zone file right?

You might wait a day or so after this to make sure everything is working on the new server and little or no traffic on the old server and then shut down the old server.
Click to expand...
OK so I should have:

server1:
NS1 -> OLD_IP1
NS2 -> OLD_IP2

server1:
NS1 -> NEW_IP1
NS2 -> NEW_IP2

right?



so how could I test this with a single client/site, if the nameservers don't point to the new sever?
 
You don't want to do anything with nameserver records until the last thing.
 
@floyd:

some great advice there.

@Mtk:

I always do a test user first - to see if it all works, iron out any issues. Then do the real live run.

Let us know how you go .. and if you need anymore help.
 
thanks!

just out of curiosity, what if I have both servers RSYNCed?
so they both basically have similar information, including all clients sites, right?
 
You must log in or register to reply here.
Back
Top