WordPress: Disaster Recovery

WordPress brutsen

Hindenburg-rampDe lêste in pear dagen I've been working furiously on getting my good friend Pat Coyle's blog back up. (My vacation continues to get more interesting – today it's snowing slightly… in April! Whatever happened to Global Warming?)

Ik wol diele wat der bard is en besprek dan de previntive maatregels dy't ik naam en hoe't it waard korrizjearre.

Hjir is wat barde:

  1. A DNS server gie op 'e fritz. IN DNS server oerset ynkommende ferkear nei in domeinnamme en trochferwiist it nei de passende server. Mei dit foarkommen hat it eins 2 middel foar kommunikaasje ôfbrutsen - de domeinnamme nei de side en de side nei de database (syn database is op it stuit yn in dielde omjouwing).
  2. I complicated things by quickly moving his blog over to another server, not realizing that there was a DNS issue. This adds another level of complexity. Passwords in WordPress (and most other database applications) are uniquely encrypted by the server that they are on. If you move the site to another server, you've just disabled your ability to decrypt that password. Thankfully, WordPress (another great feature) has a password recovery system where you can reset your password via a link in an email.

Here's the immediate action that I took:

  1. Before this ever occurred, I have to say that I'm with a fantastic web hosting company who does comprehensive backups. I've never had an issue that they weren't able to correct through backups. I've heard nightmares from other folks on their blogs and sites being totally lost. I can't imagine what it's like to go through that. (Abonnearje op myn RSS-feed en jo kinne in bon krije foar in fergees jier frij mei myn host).
  2. Ik koe my by de Webserver oanmelde FTP en helje sawol de side op en de databank. In oar skaaimerk fan myn hostingpakket is dat ik tagong kin krije ta it gehiel VDS foarby de eigentlike webside sels. MySQL bewarret de databases yn in bestânmap (/ var / lib / mysql /). Ik koe de database gewoan downloade troch de map lokale te kopiearjen. Sprek oer in geweldige reservekopy! Gjin ymport, gjin eksport, gjin maksimale bestânsgrutte om mei te meitsjen ... gewoan FTP.

No't ik de side en database lokaal hie, sykhelle ik sucht fan ferromming. As ik hjir gewoan stopte en geduld hie, soe it DNS-probleem himsels útwurke hawwe en Pat soe earder opnij wêze. Ik ferifieare dat de Domeinnamme noch wiist nei de passende Nameservers fan myn host dy't brûkt Whois.net, As jo ​​jo domein dêr kontrolearje, steane de nammeservers heul ûnderoan yn it rapport.

Dit late my ta leauwen dat de side mooglik hackd wêze koe. De nammeserver wie korrekt, mar de kommende pagina wie in ferskriklike side dy't op spam like. Ik benutte de Live Headers tafoeging to Firefox to ensure I actually wasn't being redirected – the typical hack that many people see. The site wasn't being redirected. I could have done some additional troubleshooting; however, I entered a support ticket with my host so their experts could begin investigating.

Jo side werstelle nei in oar akkount of host:

Ik hie Pat noch net bywurke nei de lêste ferzje fan WordPress 2.1, PHP en MySQL, dat ik besleat dat d'r gjin bettere tiid wie dan de hjoeddeiske! Ik haw syn âlde akkount wiske en in nij akkount lansearre. Ik haw syn e-postaliasynformaasje opnij ynfierd en de database laden, WordPress 2.1 and Pat's content:

  • wp-ynhâld uploadmap - dit is wêr't al jo uploadde ôfbyldings wenje.
  • wp-content plugins directory - al jo plugins (doch dit lykwols lêst, om't jo miskien problemen hawwe mei ferzjes.
  • wp-ynhâld tema's map - jo tema.

I hope in a future release of WordPress that these 3 directories are root directories rather than sub-directories. It would make upgrading much easier! By this time, my host had found the DNS issue and properly redirected the site. Whew! Now Pat's page was coming back up with a WordPress Upgrade message. I clicked through to upgrade the database and he was back up… almost.

Remember the encryption issue I spoke about? Yea, Pat couldn't login because of it. His password no longer decrypted the value in the database properly so I had one more correction to make. I physically logged into the database and changed Pat's reply email address in the user table to my email address. I then utilized the “Lost my Password” feature to email myself a link to reset the password. After resetting the password, I logged in and changed Pat's email address back.

And now Pat is back up! Hindsight is 20/20… had I simply waited on my host, the issue would have been corrected. I really complicated the issue. However, Pat's now upgraded and running the best versions of everything. I'm sorry he was down so long, though. It doesn't take long to bounce back from downtime, but it is a nasty inconvenience! Sorry, Pat!

Lessen leard:

  1. Make sure you're with a host that has great backups.
  2. Backup jo side en databank en bewarje se op in feilige lokaasje.
  3. If you're with a good host, rely on them to find and correct the issue.
  4. As jo ​​dat nedich binne, ferpleatse jo nei in nije host of akkount en begripe hoe't jo de side, database kinne herstelle en jo wachtwurd weromhelje.

Wat ekstra ynfo

Tsjintwurdich is de fraach nei snelle ynternetferbining mannichfâldich tanommen. Wis, yn dizze bewegende wrâld fan ynternet, satellyt tillefoan hat syn wearde bewiisd. As it giet om triedleas ynternet, steane minsken noch altiten op it spul en freegje it triedleas ynternet hoe in soad wurdearre foar har. Benammen foar webmasters is it belang fan triedleas DSL is gjin fraach mear. Meastentiids hawwe dizze webmasters it foarkar web design studio foar ûntwerp en dan dizze hege snelheidferbining nedich om it te uploaden. As folgjende stap is dizze snelle ferbining ek ferplicht yn it proses fan search engine marketing, In persoan dy't hat Microsoft-sertifikaasje kin maklik alle problemen yn 'e netwurking fan dizze ferbiningen behannelje.

Wat tinksto?

Dizze side brûkt Akismet om spam te ferleegjen. Learje hoe't jo kommentaargegevens ferwurke wurde.