Migrating To A Devoted Server

出典: くみこみックス

Step 1: S...

More than the years Ive frequently had to move sites from a single server to yet another. Its not rocket science, but if you dont have a program and a extremely clear picture in your thoughts of exactly what you need to achieve then it can go pear shaped relatively rapidly. So, heres my common program for moving a server that runs some sort of script (i.e. directory site, traffic exchange and so on) and a MySQL database. Lets assume the old domain is domain.com and the new IP quantity is 1.two.three.four.

Step 1: Send an e mail to your member list 48 hours just before the move.

Step 2: Produce the ev certificate domain.com account (CPanel and so forth) on the new server.

Step three: Take a full backup of all information on the server and all information in the MySQL database(s) and restore them on the new server. Restore the MySQL database(s).

Step four: Edit your windows hosts file (C:\WINDOWS\system32\drivers\etc\hosts) and add an entry for domain.com with one ssl certificate for multiple domains the new IP address.

Step five: Flush your windows DNS cache (open a CMD window and enter the command ipconfig /flushdns).

Step 6: Open your browser to domain.com. It ought to now be opening on the new server due to the hosts file entry. Just to be certain, place a comment in the house page file (index.html/index.php) like . That way, you can just view the source of the homepage to verify that you actually are on the new server.

Step 7: Test Almost everything. Test the uc ssl certificate script. If it has an admin place, test the admin functions. Follow all the hyperlinks and make certain that almost everything is operating appropriately.

Step 8: When you are positive the new web site is operating correctly, place an alternate homepage on the old server that says one thing like We are moving to a new, more rapidly server. We apologize for any inconvenience this could result in. Now reboot the (old) server. This will kick anyone out that is presently logged in.

Step 9: The files must all be okay (unless you have some sort of funky file-based database). Now its time to take the genuine database backup. You dont want any individual losing something, so you need to take a backup of the database once more at the point exactly where you prevented people from logging in.

Step ten: Delete the database on the new server and do a restore of the database backup that you just did from the old server. You now have the most present database data and everybody must be content when they get to log back in.

Step 11: Update the DNS at your registrar to point at the new DNS servers.

There you have it. Eleven easy measures to a smooth server move :). You might get the odd person who says that they got to the new server but then it went to the old a single again. That will be something to do with the DNS propagation and can be safely responded to with give it a small while longer and all will be well. If you nevertheless see or are alerted to problems following 72 hours then there may possibly be some thing up with the DNS config on the new server but it would have to be a pretty apparent mistake and very easily rectified if that were the case.