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.

[Distance]

Amazing

Thanks

[Paul M]

Originally Posted by Tigratrus

IS there a way to feed in multiple files? Doing it individually works but that?s a LOT of files to run though. O.o

I don't think the source command will accept wildcards - join the files into one big one with the windows copy command.

[RFViet]

Limited time = 3600 => what does mean 3600 ??

[Tigratrus]

Thanks... I'm kind of surprised that there isn't wildcard functionality, you'd think it would make things a lot easier. ::shrug:: I did a quick

copy *.sql 2006-12-19.sql

And then

source c:\2006-12-19\2006-12-19.sql

And it seemed to restore fine. Thanks for the help... I thought it might be useful to post the specifics back in case any other non-linux fossils like myself come looking for an answer in the future ;-).

I assume there's a comparable command in linux to concatenate the files into a single .sql so that you can restore from a backup without going through (in the case of my particular DB) 182 source commands?

Adding a backup to single file option might be helpful, though I can see how having each table individually would be useful too...

Anyway, thx for the help!

[Paul M]

Originally Posted by RFViet

Limited time = 3600 => what does mean 3600 ??

3600 seconds (1 hour).

Originally Posted by Tigratrus

I assume there's a comparable command in linux to concatenate the files into a single .sql so that you can restore from a backup without going through (in the case of my particular DB) 182 source commands?

If there is I don't know what it is - I have to join them in windows.

[Tigratrus]

::stunned shock::

How dreadfully ironic. In order to do a restore we have to ftp the files to a WINDOWS host to run a *command line* utility so we can put the file back up on the Linux host and run the restore? ::laughter::

I'd think the MySQL community would add wildcards just for that reason.

Sorry... I realize nobody else might find that amusing but I can't help it...

Thanks again Paul!

::wanders off chuckling::

[BeaLzeBuB]

worked fine

thank you

clicked

[ezekiel97]

I get this error,

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

What do I do? Make a file for it to write too?

[Paul M]

No, it means your web server does not have write permission to the folder you have chosen.

[ezekiel97]

Nevermind! THANKS!!