Migrating To A Devoted Server
| Team info | |
| Description | Step 1: S... Over the years Ive frequently had to move websites from a single server to another. Its not rocket science, but if you dont have a strategy and a very clear image in your thoughts of specifically what you need to have to obtain then it can go pear shaped relatively speedily. This stately My Community - Blog View - Why to Select Paid Hosting In the place of Free? URL has endless powerful suggestions for the purpose of it. So, heres my standard program for moving a server that runs some sort of script (i.e. directory site, site visitors exchange etc) 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 ahead of the move. Step 2: Develop 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 ought to now be opening on the new server due to the hosts file entry. Just to be certain, spot 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 genuinely are on the new server. Step 7: Test Every thing. Test the script. If it has an admin area, test the admin functions. Stick to all the hyperlinks and make confident that almost everything is operating correctly. Step 8: When you are confident the new web site is working properly, spot 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 may cause. Now reboot the (old) server. This will kick anyone out that is presently 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 actual database backup. You dont want any individual losing something, so you need to have to take a backup of the database once more at the point where you prevented individuals 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. Dig up more on our favorite related website - Click here: site preview. You now have the most existing database data and every person really should 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 straightforward measures to a smooth server move :). You might get the odd particular person who says that they got to the new server but then it went to the old one again. That will be a thing to do with the DNS propagation and can be safely responded to with give it a small although longer and all will be nicely. If you still see or are alerted to issues following 72 hours then there might 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 situation.. |
| Web site | http://www.fassly.com/social/blogs/9794/13570/why-to-select-paid-hosting-in-th |
| Total credit | 0 |
| Recent average credit | 0 |
| Cross-project stats | SETIBZH BOINCstats.com Free-DC |
| Country | None |
| Type | Secondary school |
| Members | |
| Founder | |
| New members in last day | 0 |
| Total members | 0 (view) |
| Active members | 0 (view) |
| Members with credit | 0 (view) |