Undgå nedetid! Problemfri Site / Blog Flyt - VPS Bibelen # 19

Migrere din hjemmeside eller blog til en ny server med minimale problemer eller utilgængelighed. Denne vejledning træder ud en dokumenteret flytning procedure.

Da jeg flyttede mit websted fra min delte vært til min skinnende nye VPS på Linode, dette var et problem for mig, især da jeg havde en konstant skiftende database. Vaskning nettet, fandt jeg nogle sparsomme anvisninger, men intet grundig, og ingen tutorials, der gav mig tillid. Så spurgte jeg på Linode forum, og processen skitseret nedenfor er et resumé af den rådgivning, som den slags folk der, sammen med min egen erfaring.

.. Så for denne proces, kan du takke Linode forum brugere btmorex, Lykaon, kirbysdl og hybinet.

Denne guide henviser til en fælles-til-VPS flytte, men kan anvendes på enhver server-til-server flytte.

Første op, Self-Service

Don't Tell DIN GAMLE HOST, man ønsker at flytte væk.

Tilmeld dig med en ny Web Host

Hvis du ikke er sikker på, hvilken type vært, du har brug for, VPS Bibelen Del 1: VPS (Virtual Private Server) vs Delt vs Dedikeret vil hjælpe dig med at vælge.

Hvis du går den forvaltede VPS rute, kan du læse denne bibel fra top til tå. Hvis du er styrede, for resten af denne vejledning, vil jeg antage, at du har bygget din boks. For delt lykkedes VPS eller dedikeret, din boks er bygget under alle omstændigheder, så lad os springe på.

Opret DNS Records

Dybest set er disse fortælle en server for at lede efter et domæne.

Hvis dit nye vært ikke tillader DNS-konfiguration, det er temmelig dårlige. Else du er med en delt server, i hvilket tilfælde du får hvad du betaler for. For dem, der kan udføre DNS administration ..

Tilføj DNS-registreringer i dit kontrolpanel, så for eksempel, med Linode eller Slicehost det er gjort i DNS Manager. Du kan henvise til VPS Bibelen Del 9: Tilføj et domæne Område til din VPS for detaljer og en forklarende video. Giv alt en virkelig lav TTL (time to live) værdi. Hvis du har nogen MX eller anden DNS-poster med din nuværende vært, kopiere dem.

Don't worry, er dette ikke gør dit domæne løsning til den nye vært for tidligt, men er klar til den migration.

Twin den gamle hjemmeside eller blog

Duplicate din hjemmeside eller blog's filstruktur på den nye server, skabe & link nogen databaser og importere dine data inden.

Tallene hosts fil til Test hjemmeside eller blog

Top trick, dette. Du kan ændre en fil på din pc til at omdirigere din URI til den nye server, bare for dig. Dette udelukker ikke effekt det oprindelige websted, eller dens generelle trafik (medmindre de har ændret deres vært filer også!)

Windows

Goto min c:> Windows> system32> drivere> etc og åbne vært med en teksteditor.

Linux

Goto etc> og åbne vært med en teksteditor.

Mac

Jeg ved det ikke. Please Lemme know!

Du ved, det er den korrekte fil, fordi det vil have en post eller to kan godt lide: --

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