What this does
This is a port of Brad's hack that can be found here. This will backup your database using the vBCron system in vBulletin and send the file to a directory that you specified in the vBulletin Options area.
IMPORTANT NOTE TO ALL THAT USE THIS SCRIPT
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.
To do list...
Time to install: 5 minutes
Queries to run: 0
File Mods: 0
Templates to edit: 0
Templates to add: 0
New Phrases: 5
New Plugins: 0
Credits
Thanks to Brad for allowing me to port this.
Testing Information
I've been using this for vBHackers.com since I first upgrade. I have all my backups being sent to a directory, outside of the public_html. I've yet to experiance any problems. I have had to use one of the backups before, and all worked well.
Product History
Wednesday, April 26, 2006 - Public Released
Help & Support
Before asking for support, please make sure you have done all the necessary changes! If you still need support, please post a reply here and double check that you have clicked the Install Button. I will try to support this hack the best I can. Support is not guaranteed!
Please post any bugs and errors here. Hope you like it, feedback is always welcomed!
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Both XMLs are the same, the only diffrence was on of the XML files had an extra setting in the Admincp asking you for the name of the file that you want your backup to be called. That setting was a test I was trying, but I never added the code in the databack.php. So everything will work no matter which XML you used. You might just have an extra setting in the admincp that won't work anyways, because I deleted the code before I ever released it.
Both XMLs are the same, the only diffrence was on of the XML files had an extra setting in the Admincp asking you for the name of the file that you want your backup to be called. That setting was a test I was trying, but I never added the code in the databack.php. So everything will work no matter which XML you used. You might just have an extra setting in the admincp that won't work anyways, because I deleted the code before I ever released it.
Actually, that might be a setting that would be good. On the same principal of renaming the admin and mod cp directories in the config.php file, if you get my meaning.
I was making it so it would be the name you selceted in the admincp, then the date. For example: vbhbackup-4-23-06.sql. They have to be unique names for when updating it each day, or they will over-right each other
I was making it so it would be the name you selceted in the admincp, then the date. For example: vbhbackup-4-23-06.sql. They have to be unique names for when updating it each day, or they will over-right each other
Couldn't you do a setting for the name if it is NOT an hourly backup? I backup once a week. I think that is more than enough and doesn't flood the directory with a lot of files of size. Most users won't do more than one backup a day, anyway. No real need to.
Automatic Database Back-up Details »»
About Developer
Additional Files 
Is in Beta Stage 
04-26-2006, 07:15 PM
