Estää seisokkeja! Saumaton Site / Blog Move - VPS Raamattu # 19

Siirrä Web-sivusto tai blogi uuteen palvelimeen vähäisiä ongelmia tai hankala. Tämä opas astuu osoittautunut siirtämisen menettely.

Kun muutin sivustoni jaetut isäntä minun upouuden VPS klo Linode, tämä oli huolissaan minusta, varsinkin kun olin jatkuvasti muuttuviin tietokantaan. Pesu Web, löysin joitakin vähän ohjeita, mutta ei mitään perusteellista, eikä opetusohjelmia, joka antoi minulle luottamusta. Joten pyysin Linode foorumilla, ja prosessi hahmoteltu alla on kertaus antamaa neuvontaa jollaisia ihmiset siellä, sekä omasta kokemuksestani.

.. Niin, tämä prosessi, voit kiittää Linode foorumin käyttäjät btmorex, Lykaon, kirbysdl ja hybinet.

Tässä oppaassa viitataan yhteisesti to-VPS siirtää, mutta niitä voidaan soveltaa mihin tahansa palvelin-palvelin siirtää.

Ensimmäisenä, Self-Service

Älä kerro VANHA ISÄNTÄ että aiotte luopua.

Rekisteröidy uuden Web Host

Jos et tiedä, millainen isäntä tarvitaan, VPS Raamattu Osa 1: VPS (Virtual Private Server) vs Yhteiset vs Dedicated auttaa sinua valitsemaan.

Jos aiot valvomaton VPS reitti, lue tämä Raamatun kiireestä kantapäähän. Jos olet hallitsemattomia, ja loput tämän oppaan, I'll olettaa olet rakennettu laatikko. Jaettujen onnistui VPS tai omistettu, laatikko on rakennettu joka tapauksessa, joten let's ohitus.

Luo DNS Records

Pohjimmiltaan nämä kertovat palvelimen etsiä verkkotunnuksen.

Jos uusi isäntä ei salli DNS-kokoonpano, joka on melko huono. Muuten olet kanssa yhteinen palvelin, jolloin saat mistä maksat. Niille, jotka voivat suorittaa DNS hallinnon ..

Lisää DNS-tietueet oman ohjauspaneelissa niin, esimerkiksi, on Linode tai Slicehost, joka on tehnyt DNS Manager. Voit viitata VPS Raamatun Osa 9: Lisää Domain Zone Sinun VPS lisätietoja ja selittävä video. Anna kaikki todella alhainen TTL (time to live) arvosta. Jos sinulla on MX-tai muita DNS-tietueet nykyinen isäntä, jäljitellä niitä.

Älä huolestu, tämä ei tee verkkotunnuksen ratkaista uuden isäntä ennenaikaisesti, mutta se valmistaa sitä maahanmuuttoa.

Twin Vanha sivusto tai blogi

Kahtena sivustosi tai blogisi tiedoston rakenne uuden palvelimen, luoda ja linkitä tietokannat ja tuoda tietoja kuluessa.

Muuta Hosts File Test-sivusto tai blogi

Top temppu, tämä. Voit muuttaa tiedoston tietokoneeseen ja ohjata URI uudelle palvelimelle, juuri sinua varten. Tämä ei ole vaikutusta alkuperäisen sivuston, eikä sen yleisen liikenteen (paitsi jos he ovat muuttaneet vastaanottavan tiedostoja too!)

Ikkunoiden

Goto minun C:> Windows> system32> ajurit> jne. ja avaa isännät tekstieditorilla.

Linux

Goto jne.> ja avaa isännät tekstieditorilla.

Maciin

En tiedä. Please Lemme know!

Tiedät se oikea tiedosto, koska se täytyy merkintä tai kaksi, kuten: --

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 n Tiedät se oikea tiedosto, koska se täytyy merkintä tai kaksi, kuten: --

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