multi server setup

lkbryant

Verified User
Joined
Aug 16, 2005
Messages
283
in multi server setup, do i have to enable multi server on both machines? or just one?
 
i just want to migrate everything from one server to another with the least down time.
 
Multi-server is not what you want.

I wrote a HOWTO for migrating accounts from one server to another.
Search the forum and you will find the quickest way for migration.

Regards,
 
yeah i figured but you see, i have way too many accounts on the server over 400....

if i just use the standard "manage admin/reseller backups"
it takes over 3 hours just to finish the backup process and another 3 hours to transfer all the files and import the backups...

i need a more 'quick solution' rather than waiting for everything to finish out in bulk.

thats why i wanted to go with this approach.

so then by what you mean, does this mean that, this multi server approach will not work as I expected it to?
 
Multi-server does not replicate anything other than DNS. What you could try is to do a backup and restore and then keep the servers in sync with rsync until you're ready to change over.

Regards,
 
well with multi server setup, you can have both servers up and running with virtually zero down time while doing the backups.

keep in mind im trying to backup and transfer over 200 accounts in one go.

if i do this without multi server setup, while its doing the backup and transfering and importing, thats atleast 2-3 hours of down time let alone testing to see if everything is working or not.
 
well with multi server setup, you can have both servers up and running with virtually zero down time while doing the backups.

Not quite sure what you mean by this as the only thing that might be answering on the 2nd server is DNS and that's pointless if the WebServer (running on the first server) cannot respond to any requests.

keep in mind im trying to backup and transfer over 200 accounts in one go.

I understand the issues as I have done this several times in the past.

if i do this without multi server setup, while its doing the backup and transfering and importing, thats atleast 2-3 hours of down time let alone testing to see if everything is working or not.

Believe me multi-server will not solve these issues for you. I recommend you make the move in the time your servers are least busy and go accross in 1 go, chances are that things will go well. Remember that the IP address in the DNS zone file will be rewritten, I believe there is an option in the restore to keep the IP's but I think the bulk of your users are probably hosting on your server... If you have users who point their DNS to other servers or if you changed the DNS template you may have more work in getting the DNS configured properly.

Your alternative is to move a couple of accounts at a time.

Regards,
 
im sorry i think you may have mis-understood my post.

basically, the multi-server setup, lets me move certain accounts first to my other server, to check if everything is working.

this is a great way to test if everything is working or not instead of just hoping and praying to see if everything works.

i have done a lot of updates and upgrades, especially on the security aspect of the system and can not guarantee if everything will work.

functions like exec, fpassthru have now been disabled and need to check if any of the scripts utilize those functions.

with that said, everything is now working fine, it is easy to use multi-server to move accounts across servers.
 
lkbryant, I'm not sure how DirectAdmin's multiserver DNS ability helps you do that.

I also worry about sites with user input through MySQL files, as they must be reachable by clients on one server or the other; if they're ever available on both the databases will be out of sync.

Jeff
 
Jeff / lkbyrant,

Multi-server does not help at all as it only replicates DNS and (if configured) ensures that domain names are not duplicated across servers. The last feature will cause problems when transferring accounts as you will have to backup, then delete the account and then restore it on the other server. This is not the best solution as you cannot go back to a working situation if you have a problem restoring the backup.

Regards,
 
Onno,

How does mult-server fail if the backup from one server is restored on the other?

If it simply leaves out DNS for the domain, that's okay; as soon as you test the restore manually (that's what your hosts file is for :)) you can delete the domain from the original server and the DNS should start working again.

What happens if duplicate check is on? What if it's off?

Jeff
 
Onno,

How does mult-server fail if the backup from one server is restored on the other?

DA checks to see if the domain exists on any of the servers, if it exists the domain will not be created. This means your restore will give an error.

There is an option to disable this feature but then you will have problems with DNS updates, a change on 1 server will be propagated to the other overwriting the DNS records for the domain.

If it simply leaves out DNS for the domain, that's okay; as soon as you test the restore manually (that's what your hosts file is for :)) you can delete the domain from the original server and the DNS should start working again.

What happens if duplicate check is on? What if it's off?

Jeff
 
Still leaving it disabled might be acceptable during a move.

What do you think?

PS: you might want to update some of the sites at the links in your siglines :D.

Jeff
 
I got situations here ...

Server A.
5 ips

Server B
1 ips

Server A have 2 nameserver while server B cannot make nameserver because it only have 1 ips.
I want to host a domain.info at server B, but i got problem because server B don't have nameserver. Can i use nameserver from server A to add at my domain registery and i open server B and at domain.info into this server ...

Can this propogate domain.info into server B ???
 
It was a bit hard to understand you; that may have been why you've gotten no replies.

You can certainly set up a nameserver on your second box; just make sure that BIND is running and create the nameserver as a virtual nameserver so it won't need IP#s.

Jeff
 
Back
Top