避免停机！ 无缝的网站/博客移动-车辆定位系统圣经＃19

迁移您的网站或博客，以最小的问题或无法使用新的服务器。 证明了搬迁过程本指南的步骤。

当我提出我的共享主机上我的网站我在Linode闪亮新的VPS，这是对我的关心，特别是因为我有一个不断变化的数据库。 洗毛网络，我发现了一些很少，但没有详细说明，也没有教程，给了我信心。 所以我问了Linode论坛，并制定了以下的过程是由一种乡亲那里提供的意见总的来说，以及我自己的经验。

.. 因此，对于这个过程中，你应该感谢Linode论坛用户btmorex，Lykaon，kirbysdl和hybinet。

本指南是指共同对车辆定位系统移动，但可以适用于任何服务器到服务器移动。

一是建立，自助服务

别告诉你的老主机，你打算搬走。

注册一个新的Web主机

如果你不知道你需要的主机， 车辆定位系统圣经第1部分：车辆定位系统（虚拟专用服务器）类型的队队专用共享将帮助您选择。

如果你要非托管车辆定位系统的路线，读这从头到脚圣经 。 如果您是托管，就本指南的其余部分，我假设你已经建立的框。 对于共享，管理车辆定位系统或专用，你的箱子是建立无论如何，所以让我们跳过。

创建DNS记录

基本上，这告诉服务器来查找一个域。

如果你的新主机不允许DNS配置，这是非常不好。 否则你的共享服务器，在这种情况下你得到什么您支付。 对于那些谁可以执行DNS管理..

添加在控制面板中的DNS记录的话，例如在Linode或Slicehost，那所做的DNS管理器。 你可以向车辆定位系统圣经第9部分：添加域开发区 ，详细您的VPS和解释性视频。 让一切真正低的TTL（生存时间）值。 如果您有任何的MX或与当前的其他DNS主机记录，复制的。

不要担心，这不会使您的域名解析到新的主机过早，但不准备迁移。

双旧网站或博客

重复新的服务器上的您的网站或博客的文件结构，建立和连接任何数据库，并在您的数据导入。

修改Hosts文件来测试网站或博客

顶技巧，这一点。 你可以改变一个PC上的文件，您的URI重定向到新的服务器，将为您。 这并不影响原来的网站，还是其总流量（除非他们已经改变了他们的主机文件呢！）

视窗

转到我的C：“窗口”> system32>“驱动程序”等，并用一个文本编辑器中打开主机。

Linux的

后藤等“，并用一个文本编辑器中打开主机。

苹果

我不知道。 请lemme知道！

你会知道它是正确的文件，因为这将有1项或2如： -

127.0.0.1	localhost

... and that is the format you want for the new lines you have to add to the file. So add something like:-

12.34.56.78  domain.com
12.34.56.78  www.domain.com

... swapping the IP for your new IP, and the domain for yours.

Upon saving the file, when you surf to domain.com, instead of taking you to your old server, it will take you to the new one, and you can fully test your site's functionality.

(I told you that was top )

NOW TEST YOUR NEW SITE'S FUNCTIONALITY.

But don't administer the wrong site: after testing, don't forget to delete the new hosts entry, else comment it out with a # at the beginning of the line. And restart your web browser.

Resolve Email

Move your email accounts from your current host.

If you want a simple, spam-free solution with no web server resource cost (ie no personal mail server), check out the VPS Bible Part 18: Google Apps for Domain-Specific Email .

Test your email.

Create A or AAAA Records

This is the key to a seamless move, which is particularly important if, for example, you host a forum or receive a lot of blog comments.

What we're going to do is to set up your new host to resolve the domain call to your old host. Basically, this eliminates the possibility of writing to more than one database while, for example, the nameservers propagate or Google's global servers refresh your new domain details.

In the new server's DNS settings, add two A/AAAA records using these guidelines:-

When you save your options, you may find one of the hostname fields is blank. That's normal.

Point Domain to Nameservers

Goto your domain registrar account and look for the Nameserver option. Renew the data.

For example, with Linode, bless, change to ns1.linode.com, ns2.linode.com, ns3.linode.com and ns4.linode.com. You'll find your new web host's nameserver details easily enough.

Now we are awaiting full propagation, at all server points around the world. I have no idea how long that takes, but about 72 hours is generally reckoned, so allow for 4-5 days to be safe.

MOVING DAY!

Go back to those A Records we created, replacing the old host IP to your new host IP. Set the TTL to the shortest possible 'time to live'. But before you click OK ..

Take a final backup of your old database and import the data into your new one.

.. And now you can click OK on those new A records.

While your A record changes will update the new host nameservers within minutes, it takes up to 72 hours for full web-wide propagation. You may find new data records in the old database, so you'll have to export and import those strays.

Note: At Linode, updated DNS records take effect every 15 minutes. So if you edit an A record at 2:32, it'll take until 2:45, plus the time period specified in the TTL, for the update to be visible to the world. Careful timing will give you the least downtime.

Final Checks

If you completed the previous testing properly, there should be no surprises. Then again ..

After the time period specified in the TTL, check your site to ensure everything works. Because your local nameservers may not yet have resolved with the new A record data, and so that you can be sure you're looking at the new, not the old, web application, use the host file trick.

Shed Shared, Viva Virtual!

Whatever kind of web host you've moved to, you can cancel the old host 4-5 days after moving day. Your breathing will gradually shallow out. Take tea!

Virtually Done

This series is pretty much complete, and I'm definitely gonna be spending more time down the pub.

However, as a round-up, VPS Bible Part 20: Blogroll, Links, Credits, Resources will list some of the best resources on the web for anything Linux or VPS. Plus it's a bit of a thank you to all those whose advice has helped me to go from VPS newbie, a few months ago to, well, senior newbie. Hey, you be the judge, but I sure ain't a sysmin.

By way of a follow up, and as promised in VPS Bible Part 17: Nginx Control Panel Workarounds , I'll be publishing some appendix guides too, showing you how to administer your VPS without relying on bloatware like cPanel.

Here's the you-know-what ...