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.
Great hack, one question: I turned on Log Entries, and I looked in the folder where the backup was (after it had backed up), and it had a file called "05-18-04-error.txt." It had nothing on it.
not hard, just unzip/untar, upload, change the variables in config.inc.php and thats it. You have to set up a cron though. You can either do it using telnet or cpanel.
So this is all done and I can download it? Like it should work on my system? And I should download the db back up but only put it on my server when I need to back up?
The only problem I experienced with this script was when a database copy was already there, and it tried backing it up again, which caused the new backup to increase in size ridicuously (monitored by refreshing on WSFTP) until it just stalled. I have a cron setup obviously.. any advice?
As for this hack, I had no success in getting my backup. It makes a .tar the size of 1KB without any files.
Noone using this error got this except me.
i guess, my hosting provider has banned/blocked something or its me ?
Here is the Error. no db backup is created in my backup dir which is properly CHMOD.
Code:
Warning: exec() has been disabled for security reasons in /forums/includes/cron/vbcron_db_backup_131.php on line 38Warning: exec() has been disabled for security reasons in /forums/includes/cron/vbcron_db_backup_131.php on line 47
Database backup script was invoked without error, to check that it was done correctly see if the file was written to the folder you specified in the configuration variables. It may take some time before your server finishes backing up depending on the size of your database
Noone using this error got this except me.
i guess, my hosting provider has banned/blocked something or its me ?
Here is the Error. no db backup is created in my backup dir which is properly CHMOD.
Code:
Warning: exec() has been disabled for security reasons in /forums/includes/cron/vbcron_db_backup_131.php on line 38Warning: exec() has been disabled for security reasons in /forums/includes/cron/vbcron_db_backup_131.php on line 47
Database backup script was invoked without error, to check that it was done correctly see if the file was written to the folder you specified in the configuration variables. It may take some time before your server finishes backing up depending on the size of your database
need help.
Thnx.
Sandy...
I forgot what this was called..
I think its something with php.. like php(exec) or something..
Your host may have it disabled.. let me check into this further.