Administrative and Maintenance Tools - vB Database Backup (Lite)

As of 24 Nov 2017 this modification has been withdrawn.

Note: I did not write the original version, but rather have modified & adapted it.

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, first for vb 3.6, 3.7 and now for vb3.8.

The original version was by Trigunflame and the rights to the code were bought by Zoints (David Chapman) in January 2007. Later in 2007 David gave me permission to release my adaptation.

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.

As of version 3.8.002, most of the options have moved to the ACP in vBulletin Options >> vBulletin Automatic Backup

Notes:
* I will not be adding anything new to this modification.
* This is a Lite version to allow people to use the basic backup functionality on 3.8.


History:

v3.8.001 : First version for vB 3.8.
v3.8.002 : Moved most of options to ACP.
v3.8.003 : Moved more options to ACP.
v3.8.004 : Gzip option backported from vb4 version.
v3.8.005 : Split option backported from vb4 version, close option removed.
v3.8.006 : Fix php 5.3 deprecated warning.

[Bob_R]

My backup directory is empty this AM. So, obviously nothing was backed up.

What could be wrong?

Thanks.

[Paul M]

First of all, turn safe mode off.

Then run it manually to see what happens.

[Bob_R]

Isn't safe mode off a security issue?

Secondly, how can I put safe mode off for my forums but leave it on for my other sites. Which I believe need safe mode on if I'm not mistaken.

Thanks.

[Paul M]

Its not really a security risk, Safe Mode is just a nuisance that stops things working, it doesnt even exist in PHP 6.

I cannot help you with your own server set-up, contact your host.

[Bob_R]

I got this when I tried to run manually:

Automatic Database Backup for vBulletin 3.8
An error occured during the Backup : Could not open Destination SQL file for writing.

Is this the result of safe mode?

Thanks!

[Paul M]

Quite possibly - or your backup path could be wrong, or the folder permissions wrong, or some other reason. All the message means is apache does not have permission to write the file, you need to investigate why.

[Bob_R]

Just tried to run manually.

I have Safe Mode Off
The backup folder is named backups and is set to 777
And, I'm quite sure the path is correct

and I still get the error.

Automatic Database Backup for vBulletin 3.8
An error occured during the Backup : Could not open Destination SQL file for writing.

Here's my path:

$backup['DUMP_PATH'] = 'home/xxxxx/public_html/dumontnjforum.com/forums/backups/'; // Path to backups folder, must have a trailing slash, folder must be writable.

[Markos]

first of all thanks Paul i just upgraded to the new one worked first time

why not put your "backups" folder in home/xxxxx/ and change the path to that and see if that works and change the path to

$backup['DUMP_PATH'] = 'home/xxxxx/backups/';

Originally Posted by Bob_R

Just tried to run manually.

I have Safe Mode Off
The backup folder is named backups and is set to 777
And, I'm quite sure the path is correct

and I still get the error.

Automatic Database Backup for vBulletin 3.8
An error occured during the Backup : Could not open Destination SQL file for writing.

Here's my path:

$backup['DUMP_PATH'] = 'home/xxxxx/public_html/dumontnjforum.com/forums/backups/'; // Path to backups folder, must have a trailing slash, folder must be writable.

[Bob_R]

Originally Posted by Markos

why not put your "backups" folder in home/xxxxx/ and change the path to that and see if that works and change the path to

$backup['DUMP_PATH'] = 'home/xxxxx/backups/';

Same story didn't work.

[Bob_R]

I just noticed that I have 2 php.ini files.

Could this be causing the problem?

One is in public_html and the other is in forum root.