Version: 1.00, by Brad
Developer Last Online: Nov 2023
Version: 3.0.0
Rating:
Released: 03-03-2004
Last Update: Never
Installs: 73
Re-useable Code Translations
No support by the author.
This script will allow you to automaticly back-up your vBulletin database (or any database you have access to).
Current Stable Version: 1.3.1
System Requirements-
vBulletin RC 2 or later
Unix/Linux server with MySQL Dump support
Ability to chmod folders to 777 (775 works on some servers)
[high]IMPORTANT NOTE TO ALL THAT USE THIS SCRIPT[/high]
This script invokes an outside process that runs in the backround on your server to backup and compress your database. It is important to remember that this is not an instant process, do not enter you ftp as soon as the script says it is done and try to download your backup. It will likely be incomplete and your server will probbly still be writting the file to disk.
I ussally give the process an hour or two before I mess with the file, larger databases will take more time of course.
Installing the script-
1. You will need to change the information here for it to work correctly on your server:
PHP Code:
// ######################## Begin edits ######################
define('DB_HOST', 'localhost'); // database host
define('DB_NAME', 'db_name'); // vbulletins database name
define('DUMP_PATH', '/path/to/dump/folder'); // path to where db backup will be stored
define('DUMP_MAKE_TAR', 1); // set this to 1 for the backup to be compressed in a .tar.gz file
// ####################### End Edits ##########################
2. CHMOD the folder you specified in DUMP_PATH to 777
3. Upload the vbcron_db_backup_131.php file to the /vbroot/includes/cron directory
4. Enter you admin control panel, under Scheduled Tasks click [high]Add New Scheduled Task[/high]
Enter the information has follows:
Title: Automatic Database Back-up
Day of the Week:
This is the day of the week the task should run on. Set this to * to have it not apply, or for it to run every day (if Day of the Month is set to * below). Otherwise select a specific day. Note that this will override the day of the month option, unless this is set to *.
Day of the Month:
Set this to the specific day of the month the task should run. This is overridden by the Day of the Week setting above. Set this to * to have it not apply.
Hour:
This is the hour of the day the task should run. Set it to * to have it run every hour.
Minute:
This is the minute of the hour the task should run. Set it to * to have it run every minute (not really recommended!).
Log Actions:
If this is set to Yes, every time the scheduled task runs, a log will be made indicating that the task was run, and in certain cases, additional information will be provided (e.g. for the Birthday Email task, the usernames who were sent birthday wishes will be noted).
Filename:
Enter the path to vbcron_db_backup_131.php, ./includes/cron/vbcron_db_backup_131.php should work in most cases
What was added in 1.3.1
- Fixed all bugs reported in 1.3
What was added in 1.3
- Added ability for script to leave logs
Improvments to come:
- Email alert when db is begin backed up
- Close board when back-up is in process
- 'Lock down' db durring backup so no one can access it
- Table, by table back-up
- Clear session table before backup
- Make script more windows friendly
- Delete last .sql (or .tar.gz) file when doing current back-up
- [high]Ability to use hashed file names for back-ups[/high]
- [high]Save back-up to forgin server[/high]
To come: version 2.0
2.0 will introduce most, if not all the fetures listed above.
Public beta testing will begin in the next few days, expect a stable version in at least 2 weeks time.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
another question.
What about to include /includes/config.php in your db_backup script and just add the two lines to the config.php
PHP Code:
$DUMP_PATH = '/path/to/dump/folder'; // path to where db backup will be stored
$DUMP_MAKE_TAR = '1'; // set this to 1 for the backup to be compressed in a .tar.gz file
then change in your db_backup script DUMP_PATH with $DUMP_PATH and DUMP_MAKE_TAR with $DUMP_MAKE_TAR
This will reduce the time for implement this script to another vB and also the paramters for the DB are centralized in the config.php and not twice in your script too.
I didn't try it right now, but I think this will work.
another question.
What about to include /includes/config.php in your db_backup script and just add the two lines to the config.php
PHP Code:
$DUMP_PATH = '/path/to/dump/folder'; // path to where db backup will be stored
$DUMP_MAKE_TAR = '1'; // set this to 1 for the backup to be compressed in a .tar.gz file
then change in your db_backup script DUMP_PATH with $DUMP_PATH and DUMP_MAKE_TAR with $DUMP_MAKE_TAR
This will reduce the time for implement this script to another vB and also the paramters for the DB are centralized in the config.php and not twice in your script too.
I didn't try it right now, but I think this will work.
Could you show me how to set it up like that? I'd like to try it and see how it works.
another question.
What about to include /includes/config.php in your db_backup script and just add the two lines to the config.php
PHP Code:
$DUMP_PATH = '/path/to/dump/folder'; // path to where db backup will be stored
$DUMP_MAKE_TAR = '1'; // set this to 1 for the backup to be compressed in a .tar.gz file
then change in your db_backup script DUMP_PATH with $DUMP_PATH and DUMP_MAKE_TAR with $DUMP_MAKE_TAR
This will reduce the time for implement this script to another vB and also the paramters for the DB are centralized in the config.php and not twice in your script too.
I didn't try it right now, but I think this will work.
It is set up this way to allow you to have multiple copies to back up multiple databases, even ones that arent associated with vBulletin.
As for the DATE define it was replaced by a var, unless you spotted an old call to it that I missed?
Could you show me how to set it up like that? I'd like to try it and see how it works.
I tested it a few minutes ago and it works fine
This change is used to get the db_data directly from config.php without having this data in more scripts.
Okay, here we go:
step1:
open your /includes/config.php file and find:
PHP Code:
// ****** DATABASE NAME ******
// This is the name of the database where your vBulletin will be located.
// This must be created by your webhost.
$dbname = 'your_db_name_here';
below that add:
PHP Code:
// ****** DATABASE BACKUP HACK VIA CRON ******
// This is the absolute Path to your folder where the db backup will be stored.
// Use DUMP_MAKE_TAR = 1 for compressed tar.gz file
// Use DUMP_MAKE_TAR = 0 for normale .sql file
$DUMP_PATH = '/path/to/dump/folder';
$DUMP_MAKE_TAR = '1';
Don't forget to place your /path/to/dump/folder folder in this code !
Save and store config.php
step2:
now open your db_backup Script in /includes/cron folder. Should be named vbcron_db_backup_131.php
and replace:
PHP Code:
// ######################## Begin edits ######################
define('DB_HOST', 'localhost'); // database host
define('DB_NAME', 'db_name'); // vbulletins database name
define('DUMP_PATH', '/path/to/dump/folder'); // path to where db backup will be stored
define('DUMP_MAKE_TAR', 1); // set this to 1 for the backup to be compressed in a .tar.gz file
// ####################### End Edits ##########################
// for some reason beyound me query was un-defined for some users, so this is here as an attempt to fix it...
require_once('./global.php');
with:
PHP Code:
// for some reason beyound me query was un-defined for some users, so this is here as an attempt to fix it...
require_once('./global.php');
// get db requirements from config.php
require('./includes/config.php');
There's something wrong because it isn't doing anything now. It says it made the backup, but it was alot quicker than normal and there is no file there. I followed your instructions exactly.
Boofo, you are right
I was in a hurry while posting the changes and do a mistake in step3 !
Please do again step 3 and the change will work, I forgot to replace the old variables with the new one from config.php
Sorry !