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.

[sparky5693]

For those of you that wanted this to delete old backups, you can change the format it names the saved file to accomplish something close. Using the method below, the output file is named Sun, Mon, Tue... etc. By doing this, it would just overwrite the correct the 7 day old file on each save.

change mysqlbackupconfig.php

change this

$backup['DATE'] = 'Y-m-d';  // Backup file date format

to this

$backup['DATE'] = 'D';  // Backup file date format

Remember... you'll only have 7 days of backups on hand like this. If something goes wrong, you need to get to it before your backup is overwritten.

[Phaedrus]

Well, I was able to get it to work, but no matter what path I put in, it saves it to the public directory.

Dangit.

[Phaedrus]

Sweet. I set permissions so nobody can see the folder, but this can write to it...

Excellent.

What is the best setting to put so it can write but nobody can see your backups?...

Forget it. I used ../Backupfile

This brought it off the public file. Now they have no access.

However it works on chmod 722, which allows it to write, but nobody can really see it, unless you are logged into your CPanel, if you can only load it to a public file...

[BadgerDog]

Originally Posted by sparky5693

For those of you that wanted this to delete old backups, you can change the format it names the saved file to accomplish something close. Using the method below, the output file is named Sun, Mon, Tue... etc. By doing this, it would just overwrite the correct the 7 day old file on each save.

change mysqlbackupconfig.php

change this

$backup['DATE'] = 'Y-m-d';  // Backup file date format

to this

$backup['DATE'] = 'D';  // Backup file date format

Remember... you'll only have 7 days of backups on hand like this. If something goes wrong, you need to get to it before your backup is overwritten.

Thank you.... :up:

I've been doing it manually....

Does this also work for file-by-file mode (table by table?) , besides one single file?

Regards,
Badger

[Paul M]

Originally Posted by BadgerDog

Does this also work for file-by-file mode (table by table?) , besides one single file?

Yes, it should do.

[BadgerDog]

Originally Posted by Paul M

Yes, it should do.

Thanks Paul ... :up:

I made the change this morning, although at this point I left it for singles file, so I'll see what it does tonight...

Regards,
Badger

[jscieza]

Hi Paul,

I have a few questions, hope you can help me

The first one is about the parameter to shutdown the forum during backups. Why I would need to setup it to '1'? It makes backups more reliable? Do you recommend to shutdown forums during backups?

The second is about the lock tables during bump. The same question... it makes the backups more reliable?

And the three one is related to split backups in independent files for each table. I manually download my backups everyday and it's easier for me to make the backup in one unique file... it's a bad practice to backup in one SQL file all the tables?

Finally, how I tell you lines above, I download my SQL backup file via FTP. It's secure to download my backup file using FTP? I heard about it's better to use SSH to download a backup file .

Thank you for your time... and your patience

[|Jordan|]

Paul, it worked! So far javascript hasn't disabled.

Any idea's why it was disabling it when "close forum" was enabled?

[Paul M]

Originally Posted by jscieza

The first one is about the parameter to shutdown the forum during backups. Why I would need to setup it to '1'? It makes backups more reliable? Do you recommend to shutdown forums during backups?

The second is about the lock tables during bump. The same question... it makes the backups more reliable?

And the three one is related to split backups in independent files for each table. I manually download my backups everyday and it's easier for me to make the backup in one unique file... it's a bad practice to backup in one SQL file all the tables?

Finally, how I tell you lines above, I download my SQL backup file via FTP. It's secure to download my backup file using FTP? I heard about it's better to use SSH to download a backup file

1. There is no need to close the forum, I don't (and in rare cases it can cause issues - see below).

2. Again, there is no need to, and it will stop you forum being used while the backup runs.

3. Its purely personal preference.

4. I use FTP, technically its more insecure, but in the real world its not likely that anyone will intercept your download.

Originally Posted by |Jordan|

Paul, it worked! So far javascript hasn't disabled.

Any idea's why it was disabling it when "close forum" was enabled?

Yes, the way the current system works appears to occasionally screw up some vb options.

[jscieza]

Paul, thank you very much for your reply :up: