trasnfer of domains from one VPS to another
- Thread starter Alvin M.
- Start date
It depends on several factors and needs to be broken down into two steps.
1. Transferring the actual files, databases, email accounts, etc.
2. Managing the DNS so that it's a crisp transition.
Step 1 depends greatly on the control panels used.
If both use the same panel, there's usually backup/restore function that allows you to backup the site on one server then restore it to the other.
If there are two different control panels in use, there may exist an import function or a script to convert the backups and restore them on another panel using a different control panel.
Last resort, if there are no conversion scripts available, one will need to do everything manually.
Step 2 is a matter of managing the VPS. Several days or even a week before you plan to transfer the site, the zone's TTL must be set to a very low value. This will allow the TTL to propagate throughout the internet. Once you have the accounts set up on the other server, you edit the original server's DNS zone with the new server information (IP address's etc.) Since you've previously set the TTL to a low value, changes to the zone will propagate faster. In other words, requests for the domain will be forwarded to the domains nameserver versus an ISP's cache. You can minimize your down time to minutes using this method.
Once steps 1 and 2 are complete, you may go to your registrar and update the domains nameservers to that of the new server.
The only problem that exists is that changes made to the files or databases after uploading the backup to the new server will, of course, not exist on the new server. There are a few methods to make sure these files are updated, however the simplest is to shut the original site down for the brief period it takes to upload the changes to the new server. A simple 'our site is currently undergoing maintenance' page on both servers will suffice for that short period.
1. Transferring the actual files, databases, email accounts, etc.
2. Managing the DNS so that it's a crisp transition.
Step 1 depends greatly on the control panels used.
If both use the same panel, there's usually backup/restore function that allows you to backup the site on one server then restore it to the other.
If there are two different control panels in use, there may exist an import function or a script to convert the backups and restore them on another panel using a different control panel.
Last resort, if there are no conversion scripts available, one will need to do everything manually.
Step 2 is a matter of managing the VPS. Several days or even a week before you plan to transfer the site, the zone's TTL must be set to a very low value. This will allow the TTL to propagate throughout the internet. Once you have the accounts set up on the other server, you edit the original server's DNS zone with the new server information (IP address's etc.) Since you've previously set the TTL to a low value, changes to the zone will propagate faster. In other words, requests for the domain will be forwarded to the domains nameserver versus an ISP's cache. You can minimize your down time to minutes using this method.
Once steps 1 and 2 are complete, you may go to your registrar and update the domains nameservers to that of the new server.
The only problem that exists is that changes made to the files or databases after uploading the backup to the new server will, of course, not exist on the new server. There are a few methods to make sure these files are updated, however the simplest is to shut the original site down for the brief period it takes to upload the changes to the new server. A simple 'our site is currently undergoing maintenance' page on both servers will suffice for that short period.
InternetVPS.com
New member
In short, there will always be a down time when you move things around with a vps. There will be issues with IP address, DNS, any other things. Think about it.
In short it depends. If it's a static content site, then there will be no apparent downtime, the visitor will be served up the original site or the new site.
On the other hand if it's a dynamic content site, such as a forum, you would need to disable the original site just before the transfer, so that visitors couldn't make any updates on the old site. Once the DNS resolves, and it may be different times for each visitor, they would be served the new site.
infinitienet
New member
I am not sure about Virtuozzo but if you have CPanel also with that server you should be able to do a Live Migrate.
~ServerPoint~
Account Disabled
I think that you will be able to do dump of you databases and copy all content. In case of dinamic pages part of your content might be lost during that transfering.
~ServerPoint~
Account Disabled
Hello Dan!
To be honest I little bit misunderstood you here. What did you mean?
ldcdc
New member
I don't really think I can say it any better than I did earlier, but I'll try. Applcations usually have a config file, where the details about the database (server, user, pass) are stored. In most hosting configurations one uses "localhost" as the server, but when changing hosts, the new server could be specified, using the IP. This whole thing can work if the new database server accepts remote connections of course.
~ServerPoint~
Account Disabled
Well. You are right, but you can do dump of DB and install it in new place and you will have nothing to change
-
HostingDiscussion
A community for web hosting professionals and enthusiasts, since 2002.
