Administrative and Maintenance Tools - vB Database Backup Pro (Lite) for vb 3.6

This modification is no longer available or supported.

When vb 3.5 first came out I was using this backup system on my vb 3.0 - and having nothing better to use - I converted it to work on vb 3.5 (here) and since then I have cut it down and adapted it for vb 3.6.

The original version was by Trigunflame and the rights to the code were bought by Zoints (D.Chapman) in January. A while ago David gave me permission to release my adaption, but until now I haven't got round to it. Trigunflame did mention a few months ago he was working on a new version, but nothing ever appeared.

I have stripped out much of the extra stuff that I do not use (or indeed, could not get to work). This is a simple (lite) version that does a php based dump of your database either as one file, or one file per table. It's been in use on our forum since the day 3.6 was installed.

Notes:
* I will not add anything new to this, or spend vast amounts of time supporting it.
* This is a Lite version to allow people to use the basic 3.0 backup functionality on 3.6.


History:

v2.10 : First internal version.
v2.11 : Bug fixes, some code changes.
v2.12 : Initial Public Release.

[djbaxter]

Originally Posted by stejoh

Have two questions about the config file: What does the options below mean and what effects has the value 1 on these settings?

The first two are self-explanatory: LOCK prevents new data from being added to a tanle while it is being backed up and "REPAIR" checks for and fixes any errors before the backup.

The third combines all of the individual tables into a single SQL file if set to 1; if left at 0, you get separate files for each table in the database.

[stejoh]

Originally Posted by djbaxter

The first two are self-explanatory: LOCK prevents new data from being added to a tanle while it is being backed up and "REPAIR" checks for and fixes any errors before the backup.

The third combines all of the individual tables into a single SQL file if set to 1; if left at 0, you get separate files for each table in the database.

Aha, I understand then!
* It feels "safest to have LOCK and REPAIR set to 1, but is it really so?
* Are there any disadvantages to backup into one single SQL file?

[djbaxter]

Originally Posted by stejoh

Aha, I understand then!
* It feels "safest to have LOCK and REPAIR set to 1, but is it really so?

I believe it is safer, yes.

Originally Posted by stejoh

* Are there any disadvantages to backup into one single SQL file?

If you are running your own MySQL queries that may have the possibility of messing up one of the tables, it's a good idea to do a backup first. If it's NOT a combined-file backup, it's easier to restore just that single table. Beyond that, it's normally easier to have the backup in one file for restore operations and for disk space reasons.

[Paul M]

Points to note;

If you lock the tables then your forum will not be usable during a backup.

On larger databases, a repair can take a long time to run.

[kontrabass]

Originally Posted by Paul M

Points to note;

If you lock the tables then your forum will not be usable during a backup.

On larger databases, a repair can take a long time to run.

Question: I didn't know that *not* locking the tables during a mysqldump was even an option... In your opinion is it relatively safe, provided that my board is OFF, to not lock tables during a dump? If so then this will be better than MysqlHotCopy for me, which locks the whole shebang and results in dropped/timeout connections even when the board is turned off, during a live backup)...

[eoc_Jason]

Usually if your board is off / closed, the only inserts it will still try to make is for session stuff. Of course your staff needs to know that when the board is closed not to make posts or anything as that could lead to data inconsistencies.

[kontrabass]

Thanks, that makes sense.

Last question I promise

Is this method of backing up recommended on dual-server setups (www + db)? I guess all the backup .sql ends up on the www server..

[Paul M]

Originally Posted by kontrabass

Is this method of backing up recommended on dual-server setups (www + db)? I guess all the backup .sql ends up on the www server..

It ends up wherever you point the backup path.

[cajunboy2208]

I don't think I am having problems. I am just totally confused. I installed it. I have it showing up on my Manage Products. I only changed one line in the mysqlbackupconfig.php, which was where I wanted my backups to go.

As to: Alter the timing of the cron job to suit.
I have no idea how to do that, or where to access it at.

Also I don't know how to access the profuct either, I don't see it anywhere on my ACP.
I would like to set it to where it backs up every day at a certain time, at like 4am if that is possible.

And one more thing... is this like the Database Backup, where it incudes every table and such?

EDIT: Ok, I didn't know it was under Scheduled Task Manager, I was looking in Scheduled Task Log.
I ran it, it ran good, but one thing, I don't want every single line of sql. I would like it to just be one file, just like on the Maintaince Database Backup. How do I go about that?

EDIT x2: Read up, and got my answer.
ONE LAST THING!
I ran the complete back up, and it came to be 12220k using the Task Manager backup.
When using the Maintaince Database Backup, it comes to be 12485k. Anything to be worried about here?

[Paul M]

Originally Posted by cajunboy2208

I ran the complete back up, and it came to be 12220k using the Task Manager backup.
When using the Maintaince Database Backup, it comes to be 12485k. Anything to be worried about here?

Nope, nothing to worry about.