Zapobiec przestojom! Jednolite strony / bloga Move - VPS Biblia # 19

Migracja witryny internetowej lub w blogu na nowym serwerze z minimalnymi problemami lub niedostępność. Ten przewodnik kroki na sprawdzonej procedury przeniesienia.

Kiedy przeniósł mojej strony My Shared przyjmującego do mojego całkiem nowego VPS na Linode było to problemem dla mnie, szczególnie jak się ciągle zmieniających się danych. Czyszczenie sieci, znalazłem niewiele instrukcji, ale nic dokładnego, a nie tutoriale, które dał mi zaufanie. Więc poprosiłem na forum Linode, a proces nakreślone poniżej zakręcić z porad udzielanych przez ludzi naturze istnieją, wraz z własnego doświadczenia.

.. Tak więc, na ten proces, możesz podziękować Linode btmorex użytkowników forum, Lykaon, kirbysdl i hybinet.

Przewodnik ten odnosi się do wspólnych przejść do VPS, ale może mieć zastosowanie do wszelkich serwer-serwer przenieść.

Najpierw, Self-Service

DON'T TELL YOUR OLD hostów, które zamierzają odchodzić.

Zarejestruj się w New Web Host

Jeśli nie jesteś pewien jaki typ hosta trzeba, VPS Biblii Część 1: VPS (Virtual Private Server) vs Wspólna vs Dedykowany pomogą Ci wybrać.

Jeśli zamierzasz niekontrolowana trasy VPS, przeczytaj tę biblię od stóp do głów. Jeśli niekontrolowana, do końca tego przewodnika, to sądzę masz budowy pola. Do wspólnego, zarządzane lub dedykowane VPS, pole jest zbudowany tak czy owak, so let's przejść dalej.

Tworzenie rekordów DNS

Zasadniczo te powiedzieć serwera szukać domeny.

Jeśli nowy host nie pozwala konfiguracji DNS, że jest zbyt dobra. Inaczej jesteś ze wspólnego serwera, w tym przypadku masz za co płacisz. Dla tych, którzy mogą wykonywać .. zarządzania DNS

Dodaj rekordów DNS w panelu sterowania tak, na przykład z Linode lub Slicehost to zrobić w Menedżerze DNS. Można odwoływać się do Biblii VPS Część 9: Dodanie domeny do Strefa Twoje VPS szczegóły i wyjaśniających wideo. Daj wszystko naprawdę niski TTL (czas życia) wartości. Jeśli masz jakiekolwiek MX lub innych rekordów DNS z aktualny host naśladują tych.

Nie martw się, to nie czyni domenę rozwiązania do nowego hosta przedwcześnie, ale ma przygotować go do migracji.

Twin Stara strona lub blog

Duplicate swojej stronie lub blogu struktury plików na nowy serwer, tworzenie i link w bazach danych i import danych w.

Zmień pliku Hosts do testowania witryny lub blogu

Najlepsze sztuczki to. Możesz zmienić plik na komputerze, aby przekierować URI na nowy serwer, tylko dla Ciebie. Nie ma to wpływu pierwotnym miejscu, ani jego ogólnego ruchu (chyba że już zmienili plików hosta też!)

Windows

Goto MY C:> Windows> system32> drivers> etc i otwórz gospodarze z edytora tekstu.

Linux

Goto etc> hosts i otworzyć w edytorze tekstu.

Mac

Nie wiem. Proszę lemingi znać!

Dowiesz się, to nic odpowiedniego pliku, ponieważ będziesz mieć wejścia lub dwa, jak: --

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 Dowiesz się, to nic odpowiedniego pliku, ponieważ będziesz mieć wejścia lub dwa, jak: --

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 ...