Moving between servers best practices


SUBMITTED BY: Guest

DATE: Aug. 6, 2019, 9:23 a.m.

FORMAT: Text only

SIZE: 3.3 kB

HITS: 436

  1. Moving between servers best practices
  2. I need to move some websites between two servers which are pointing to the same nameservers.
  3. This is what I am thinking of doing:
  4. ++++++++++++++++++++++++++++
  5. list of top cheapest hosting http://listtop.pw/
  6. Top 200 best traffic exchange sites http://listtop.pw/surf
  7. list of top gpt sites
  8. list of top ptc sites
  9. list of top ptp sites
  10. list of top crypto currency Wallets sites
  11. Listtop.pw
  12. Listtop.pw
  13. Listtop.pw
  14. +++++++++++++++++++++++++++++
  15. Duplicate site to the new WHM account on new server and then delete the old one.
  16. They are e-commerce sites and don't want to get orders on the old site whilst I am moving it.
  17. Are there anythings I need to be aware of and if there are best practices to follow?
  18. Cheers
  19. You need to put the billing/order system into maintenance mode for a few minutes, live migrate the website data and then point the nameservers to the new one with a lower TTL setting and then on the new hosting remove the maintenance mode. This should allow all the orders to flow into the new system and if people are still viewing the old website the ordering system will show as offline.
  20. if you have root on bother servers. use Express Transfer from WHM transfer tool. this will change .htaccess of old website to show a nice page informing visitors that the website was moved to new server.
  21. it also change the A records and point them to new server IP automatically .
  22. XSL.TEL - A Lonewolf Fully managed hosting provider since 2011
  23. From the little experience I have (hope I'd get corrected if wrong):
  24. 1)
  25. I'm using Cloudflare (the free package). Apart from the little extra protection and a sort of CDN (not "real" one for most data, but up to a point, images etc, - paid packages and/or MaxCDN are more "serious" solutions for that), it lets me use Cloudflare's DNS.
  26. That means I don't have to rely on provider's nameservers.
  27. It also means that any DNS (IP) changes get propagated withing minutes, not hours. This part is important when moving sites in my opinion.
  28. 2)
  29. Copy all the files, databases etc. to the new server, set it all up.
  30. 3)
  31. Choose a time of day/week when the traffic (sales) are the lowest.
  32. Set the "old" site to: "maintenance" (stopping/disabling sales).
  33. Make a fresh "inventory" database copy to the new server.
  34. Change all the DNS records to point to the new server IP and all the other relevant fields.
  35. TEST everything (inventory changes, sales, e-mail sending/recieving etc.).
  36. 4)
  37. Light a candle for good luck.
  38. Thanks for all the replies, in my case I should mention that there will be no need to change nameservers or IPs it is just moving to another server within the same hosting company. I am not sure how that will work and which website it'll go to if the website exists on two servers which point to the same nameserver.
  39. In that case it's hardware migration. Your website will be migrated to the new server but IPs will remain same, in the mean time old server will go offline.
  40. crucialhosting.com
  41. hitleap.com
  42. host 2019 oscars
  43. o hostio ?wi?ta chwyty
  44. badbitcoin.org
  45. u host game
  46. host ukraine
  47. a hosting home
  48. hosting oscars
  49. domain 3d danielson
  50. make money typing
  51. www.picturepunches.com
  52. hosting vs cloud

comments powered by Disqus