Migrating To A Devoted Server - 0 views
started by Melendez Jenkins on 08 Dec 13
started by Melendez Jenkins on 08 Dec 13
Start a New Topic » « Back to the How You Can Pick Quality New Elements for Lawn Mower group
Over the years Ive typically had to move websites from a single server to one more. I found out about when_to_choose_a_dedicated_server [IIS Asproni - Wiki documents] by searching newspapers. Its not rocket science, but if you dont have a program and a extremely clear image in your thoughts of specifically what you need to have to achieve then it can go pear shaped relatively rapidly. So, heres my standard program for moving a server that runs some sort of script (i.e. directory internet site, site visitors exchange etc) and a MySQL database. Lets assume the old domain is domain.com and the new IP number is 1.2.three.four.
Step 1: Send an e mail to your member list 48 hours just before the move.
Step 2: Create the domain.com account (CPanel and so on) on the new server.
Step three: Take a full backup of all data 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 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 confident, spot 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 genuinely are on the new server.
Step 7: Test Almost everything. Test the script. If it has an admin region, test the admin functions. Stick to all the hyperlinks and make sure that every thing is operating properly.
Step 8: Once you are sure the new site is operating appropriately, spot 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 cause. Now reboot the (old) server. This will kick any individual out that is at the moment logged in.
Step 9: The files ought to 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 require to take a backup of the database again at the point 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 existing database information and absolutely everyone ought to be pleased 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 actions 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 one particular once more. That will be one thing to do with the DNS propagation and can be safely responded to with give it a tiny although longer and all will be properly. Be taught further on our partner web resource by clicking website. If you nevertheless see or are alerted to troubles after 72 hours then there may possibly be something 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 situation.