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]

If I read ONE MORE POST about how to set the path correctly or receiving the

Error I'm going to explode!

I'm not sure I understand. So what IS the correct path?

[SkyCatcher]

Originally Posted by djbaxter

I'm not sure I understand. So what IS the correct path?

*poof*

[Kirk Y]

What's the importance of the postindex table -- is it a necessity to have in a backup or can it be skipped, as I notice my forum hangs and sometimes errors leaving the forum offline when the postindex table is being processed.

[Paul M]

It's part of the vb search system, you don't need to back it up as you can rebuild it from within the ACP.

[Kirk Y]

I just realized that I'd yet to switch to fulltext searching - I thought I did, so that cut my backup size down.

Thanks Paul, I'll remember that.

[djbaxter]

Originally Posted by acidburn0520

I just realized that I'd yet to switch to fulltext searching - I thought I did, so that cut my backup size down.

Thanks Paul, I'll remember that.

Switching to full text searching cuts the backup size down? I would have thought it would be the other way 'round...

[Paul M]

Nope, indexes are never backed up.

Using FT searching means you can forget the word and postindex tables (or just empty them).

[TrIn@dOr]

Ok, trying it (because needed) for the second time.

Inside my destination backup directory, after running the task manually, a dir is created.

That dir is Y-m-d format, but the task stoped and no SQL is generated.

Error: An error occurred during the MySQL backup. Details (Could not open Destination SQL file for writing.)

The dir is correct set, but why not the sql?

Thanks.

[djbaxter]

Originally Posted by TrIn@dOr

Ok, trying it (because needed) for the second time.

Inside my destination backup directory, after running the task manually, a dir is created.

That dir is Y-m-d format, but the task stoped and no SQL is generated.

Error: An error occurred during the MySQL backup. Details (Could not open Destination SQL file for writing.)

The dir is correct set, but why not the sql?

Thanks.

That usually means:

1. you haven't set the backup directory to be wirteable, OR more likely

2. you haven't correctly specified the path to the directory: note that this is the "physical" path on your server, not the URL - read previous posts in this thread by Paul M for specific instructions

[antiekeradio]

well; here is what I get.....

Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/../../db_backup/2007-03-08) is not within the allowed path(s): (/tmp:/home/etc/etc:/usr/lib/php:/var/etc/etc/etc) in /includes/mysqlbackup.php on line 225

and another 4 times an equivalent error

whatever i fill in the backup dir, the error remains the same....

is there something wrong with the server setup?