HomCone654

出典: くみこみックス

Step 1: S... unified communications certificate security certificate More than the years Ive often had to move sites from one particular server to an additional. Its not rocket science, but if you dont have a program and a extremely clear image in your mind of exactly what you need to obtain then it can go pear shaped relatively quickly. So, heres my normal program for moving a server that runs some sort of script (i.e. directory internet site, traffic exchange and so forth) 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 before the move. Step 2: Generate the domain.com account (CPanel etc) on the new server. ssl Step 3: Take a total 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 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). Step 6: Open your browser to domain.com. It really should now be opening on the new server due to the hosts file entry. Just to be sure, location a comment in the house 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 Almost everything. Test the script. If it has an admin region, test the admin functions. Follow all the hyperlinks and make positive that every thing is operating appropriately. Step 8: As soon as you are confident the new site is working correctly, location an alternate homepage on the old server that says a thing like We are moving to a new, more quickly server. We apologize for any inconvenience this may lead to. Now reboot the (old) server. This will kick any person out that is presently 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 real database backup. You dont want anyone losing anything at all, so you need to take a backup of the database again at the point where you prevented men and women 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 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 effortless actions to a smooth server move :). You may get the odd individual who says that they got to the new server but then it went to the old one particular once again. That will be something to do with the DNS propagation and can be safely responded to with give it a tiny while longer and all will be effectively. If you still see or are alerted to difficulties right after 72 hours then there may be something up with the DNS config on the new server but it would have to be a relatively apparent mistake and effortlessly rectified if that had been the case.