[cooper82]

Hey,

Working on a new Wordpress site that needs a back up after every change to the site, big or small. So I guess I should back up the WP database too? I've never done that before - does a WP database backup just save posts and comments? Is there any other purpose to it? This site doesn't have a blog so just wondering if the database backup is necessary?

Cheers

[pat24]

cooper82, on 31 January 2012 - 01:26 AM, said:

Hey,

Working on a new Wordpress site that needs a back up after every change to the site, big or small. So I guess I should back up the WP database too? I've never done that before - does a WP database backup just save posts and comments? Is there any other purpose to it? This site doesn't have a blog so just wondering if the database backup is necessary?

Cheers

Put it this way, if you lost your database how long would it take to get back and how much work would be involved, if the answer is very little then its up to you, if it would mean a lot of work then back it up.

[MikeChipshop]

All content and admin functions such as custom menus are stored in the database as well as the admins login credentials. My advice would be back up the database.

[FizixRichard]

I agree with MikeChipshop, I'd backup the entire database. But I'd look at some kind of automated backup methodology to do so.


Typical methodologies are ones like Grandfather, Father, Son backups, whereby you have a big monthly backup (the GF), a weekly update which is smaller (F) and a smaller daily update (S).

What gets backed up in each cycle (and whether each of those backups are full or partials) depends on the system and the requirements.

That methodology and ones like it are 'efficient', as the backups are fairly progressive (you don't have a daily full backup, more daily commits) so it makes the backup size smaller and the backup process faster.


Another method would be a redundancy type affair, looking at RAID type methodologies where a mirror of the database is stored, so whenever the database changes, the mirror is updated. That mirror is then regularly backed up.


Anyway...
I would look at various backup methodologies, find one that suits you (the type and frequency and what your hardware/host constraints deal you). Maybe discuss with your host as well, some hosting companies offer automated RAID backups so you don't need to worry about it.

BTW one point of note is, a server side backup system will be more reliable than a built in backup system, for obvious reasons.

[eCenica]

cooper82, on 31 January 2012 - 01:26 AM, said:

Hey,

Working on a new Wordpress site that needs a back up after every change to the site, big or small. So I guess I should back up the WP database too? I've never done that before - does a WP database backup just save posts and comments? Is there any other purpose to it? This site doesn't have a blog so just wondering if the database backup is necessary?

Cheers

Just to affirm the good advice already posted.

Yes 100% you should take your own backups of your WordPress database. It's holds not only your page content but all the other settings - even your WordPress username and password.

The database does not contain the contents of your WordPress Media Library so our advice to our users is to use the backup tool in their Ecenica control panel to take a full backup of their account. This is very easy to do if your host offers cPanel.

If you just want to backup your database we recommend the WP-DBManager plugin (we use it ourselves).

I also came across WP Remote this week. It's a 3rd-party service that offers to backup your WordPress website for free (at least for now). Not sure how secure it is though so use at your own risk

Cheers,

Richard