PREVENT Nedetid! Sømløs Site / Blog Flytt - VPS Bibelen # 19

Migrere din nettside eller blogg til en ny server med minimale problemer eller forhindringer. Denne veiledningen går ut en bevist flytting prosedyre.

Da jeg flyttet nettstedet mitt fra mine delte vert til min flunkende nye VPS på linode, var dette et problem for meg, spesielt ettersom jeg hadde et stadig skiftende database. Scouring nettet fant jeg noen snaue instruksjoner men ingenting grundig, og ingen opplæring som ga meg tillit. Så jeg spurte på linode forumet, og prosessen kartlagt ut nedenfor er en oppsummering av de råd gitt av den typen folk der, sammen med min egen erfaring.

.. Så, for denne prosessen, kan du takke linode forumbrukerne btmorex, Lykaon, kirbysdl og hybinet.

Denne guiden viser til en delt-til-VPS flytte, men kan brukes på alle server-til-server flytte.

Først opp, Self-Service

Don't Tell DINE GAMLE vert det du har tenkt å bevege seg bort.

Registrer deg med en ny Web Host

Hvis du ikke er sikker på hvilken maskin du trenger, VPS Bibelen Part 1: VPS (Virtual Private Server) vs Delt vs Dedikerte hjelper deg å velge.

Hvis du går den uovervåkede VPS rute, lese denne bibelen fra topp til tå. Hvis du er administrerte, for resten av denne veiledningen, vil jeg anta at du har bygget din boks. For delte klarte VPS eller dedikert blir din boks bygget uansett, så la oss hoppe på.

Lag DNS Records

I utgangspunktet er disse fortelle en server for å lete etter et domene.

Hvis den nye verten ikke tillater DNS-konfigurasjon, det er ganske dårlig. Else du med en felles server, hvor du får det du betaler for. For de som kan utføre DNS administrasjon ..

Legg til DNS-poster i kontrollpanelet slik, for eksempel med linode eller Slicehost det er gjort i DNS Manager. Du kan referere til VPS Bibelen Del 9: Legg til et domene Zone til din VPS for detaljer og en forklarende video. Gi alt et veldig lavt TTL (time to live) verdi. Hvis du har noen MX eller annen DNS-poster hos din nåværende host, reprodusere dem.

Ikke bekymre deg, betyr ikke at domenet løse den nye verten tidlig, men forberede det for migrering.

Twin Gamle nettstedet eller bloggen

Duplicate nettstedet eller bloggen sin filstrukturen på den nye serveren, lage og koble noen databaser og importere data innenfor.

Oppdater Hosts-fil som skal testes nettstedet eller bloggen

Topp knep, dette. Du kan endre en fil på PCen for å viderekoble URI til ny server, bare for deg. Dette Påvirker ikke det opprinnelige stedet, eller den generelle trafikken (med mindre de har endret sin vert filer også!)

Windows

Goto min c:> windows> system32> drivere> osv. og åpne vertene med en tekst editor.

Linux

Goto etc> og åpne vertene med en tekst editor.

Mac

Jeg vet ikke. Vennligst lemme know!

Du vet det er den riktige filen fordi den får en oppføring eller to som: --

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, w Du vet det er den riktige filen fordi den får en oppføring eller to som: --

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