Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

Re: [wp-hackers] Haven't installed WordPress yet - run install.php

  • To: wp-hackers@xxxxxxxxxxxxxxxxxxxx
  • Subject: Re: [wp-hackers] Haven't installed WordPress yet - run install.php
  • From: Roy Schestowitz <r@xxxxxxxxxxxxxxx>
  • Date: Fri, 19 Aug 2005 05:17:35 +0100
  • Delivery-date: Fri, 19 Aug 2005 05:17:37 +0100
  • Envelope-to: s@schestowitz.com
  • In-reply-to: <a491f91d05081820387116ed44@mail.gmail.com>
  • References: <43049BE1.7070009@cameraontheroad.com> <e6ec604d05081815201de80e8b@mail.gmail.com> <20050819032932.sv3itxgqpwgg4o84@banana.catalyst2.com> <a491f91d05081820387116ed44@mail.gmail.com>
  • User-agent: Internet Messaging Program (IMP) H3 (4.0)
Quoting Robert Deaton <false.hopes@xxxxxxxxx>:

If the databases are messed up, having a backup of your home directory
is useless.... Reverting to a backup of your home directory would do
nothing towards restoring a working WordPress system.

Yes, but it has been suggested that the problem lies somewhere among the files and not the database. If the database has reached a morbid state, it is possible to follow a similar type of strategy. Always make sure you get frequent backups of your database (it is very light anyway). I personally have cron job set up to retain a stack of database backups in ~/tmp. If a part of the database ever breaks, the first thing to try and and do is repair it (cPanel provides a front-end to this function). If failed, the database in its older state can be restored from backup. If changes have been made since the last backup, download the database in its latest state, merge with the old one (paying careful attention to changes) and then restore the result of the merger.

Roy

--
Roy S. Schestowitz
http://Schestowitz.com


[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index