BreunigSandusky427

Step 1: S... Over the years Ive frequently had to move sites from 1 server to yet another. Its not rocket science, but if you dont have a program and a really clear image in your thoughts of specifically what you need to attain then it can go pear shaped relatively speedily. So, heres my standard strategy for moving a server that runs some sort of script (i.e. directory site, visitors exchange and so on) and a MySQL database. Lets assume the old domain is domain.com and the new IP quantity is 1.2.3.four. Step 1: Send an email to your member list 48 hours ahead of the move. Step two: Produce the domain.com account (CPanel etc) on the new server. Step three: Take a full backup of all data 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 the new IP address. Step 5: Flush your windows DNS cache (open a CMD window and enter the command ipconfig /flushdns). Step 6: Open your browser to domain.com. It should now be opening on the new server due to the hosts file entry. Just to be certain, location a comment in the property page file (index.html/index.php) like . That way, you can just view the source of the homepage to verify that you really are on the new server. Step 7: Test Almost everything. Test the script. If it has an admin region, test the admin functions. Comply with all the hyperlinks and make certain that almost everything is operating correctly. Step 8: As soon as you are certain the new web site is working properly, place an alternate homepage on the old server that says one thing like We are moving to a new, faster server. We apologize for any inconvenience this might result in. Now reboot the (old) server. This will kick any person out that is at present logged in. Step 9: The files really should 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 person losing anything at all, so you require to take a backup of the database once again at the point where you prevented individuals from logging in. Step 10: 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 existing database information and everybody should be happy 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 straightforward steps to a smooth server move :). You may possibly get the odd person who says that they got to the new server but then it went to the old one once more. That will be something to do with the DNS propagation and can be safely responded to with give it a small even though longer and all will be properly. If you nevertheless see or are alerted to problems right after 72 hours then there could be some thing up with the DNS config on the new server but it would have to be a fairly apparent mistake and very easily rectified if that had been the case. entrust