GavinWooley478

Step 1: S... Over the years Ive typically had to move sites from one server to another. Its not rocket science, but if you dont have a strategy and a really clear picture in your mind of precisely what you need to obtain then it can go pear shaped fairly swiftly. So, heres my common strategy for moving a server that runs some sort of script (i.e. directory website, traffic exchange and so on) and a MySQL database. Lets assume the old domain is domain.com and the new IP number is 1.two.3.4. Step 1: Send an e-mail to your member list 48 hours before the move. buy ssl Step two: Develop the domain.com account (CPanel etc) on the new server. entrust Step three: Take a total backup of all information on the server and all data in the MySQL database(s) and restore them on the new server. Restore the MySQL database(s). Step 4: Edit your windows hosts file (C:\WINDOWS\system32\drivers\etc\hosts) and add an entry for domain.com with the new IP address. Step five: Flush your windows DNS cache (open a CMD window and enter the command ipconfig /flushdns). security certificate 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 confident, location a comment in the property page file (index.html/index.php) like. That way, you can just view the supply of the homepage to verify that you actually are on the new server. Step 7: Test Everything. Test the script. If it has an admin area, test the admin functions. Follow all the hyperlinks and make confident that everything is working properly. Step 8: Once you are confident the new site is operating properly, place an alternate homepage on the old server that says some thing like We are moving to a new, faster server. We apologize for any inconvenience this may possibly cause. Now reboot the (old) server. This will kick any person out that is at the moment logged in. Step 9: The files 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, so you need to take a backup of the database again at the point where you prevented people 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 present database data and everyone ought to 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 might get the odd person who says that they got to the new server but then it went to the old 1 once again. That will be some thing to do with the DNS propagation and can be safely responded to with give it a tiny even though longer and all will be effectively. If you nevertheless see or are alerted to issues right after 72 hours then there might be one thing up with the DNS config on the new server but it would have to be a pretty obvious mistake and very easily rectified if that had been the case.