Administrative and Maintenance Tools - vBulletin Cron Based Database Backup

As of 23 Nov 2017 this modification has been withdrawn.

This is a cut down version based on a backup system written by Trigunflame for vb 3.0. It is a simple vBulletin cron trigged php system that does a dump of your database - either as one complete file, or as one file per table. Especially useful now that IB removed the old ACP backup option in vBulletin 4. Files can be (G)Zipped to save space.

All the options are located in the ACP in vBulletin Options >> vBulletin Automatic Backup

To install, download and unzip the files, and follow the instructions in the text file.


History:

v4.0.1 : 28-Dec-2009 : Initial release for vb 4.0.0 Gold.
v4.0.2 : 29-Dec-2009 : Added ability to block process larger tables.
v4.0.3 : 27-Jun-2010 : Added Gzip option.

v4.1.0 : 04-Dec-2010 : Updated for vBulletin 4.1.0.

v4.1.7.0 : 16-Oct-2011 : Updated for vBulletin 4.1.7.

v4.2.0.0 : 24-May-2012 : Updated for vBulletin 4.2.0.
v4.2.0.1 : 17-Mar-2013 : Removed vboptions from backup call..
v4.2.0.2 : 25-Nov-2013 : Fix php 5.3 deprecated warnings, added mysqldump backup.

[Leica.Robbiani]

Hi there,

for a long time I used this mod, but I found out I have a war with the mysql console. I had a solution for this, but the problem was the wrong one. So I was searching for another solution.

But this mod conveniently performs the backup service automatically , replaces older files by your discretion settings, and stores them in a non-public fashion ready for you to ftp off site at your convenience. All within the vb cron mechanism.

mysqldumper does his work also automatically, but not within the vB cron. I think this is not a problem. You can use an external cronjob service (there are many sites of them for free in the net) or you can write your own file.

I have configured my server in the way where mysqldumper is not reachable from the document root of any website, and it stores the backups in a private directoy.

You can configure the dumper, how many backup's it stores.

At least everyone has to decide for himself what he wants to use. The dumper is an easier way for me.

Best regards

L.R.

[smirkley]

Originally Posted by djbaxter

That's actually pretty clever if you have plenty of diskspace.

What would be better is a cron job to delete backups older than X days.

I suppose if you are running a very popular forum and a large database, you would already have the headroom in your account. My database isnt huge but isnt small. And I still have plenty of headroom left on my drives. I run on a basic vps and my backups delete and rewrite each date of the month. I suppose you could just set your date format for day of the week and that way you would be limiting your backup files to 7 total before overwrite. You would just hafta download ftp your weekly backups once a week.

[smirkley]

Originally Posted by Leica.Robbiani

for a long time I used this mod, but I found out I have a war with the mysql console. I had a solution for this, but the problem was the wrong one. So I was searching for another solution.

...

At least everyone has to decide for himself what he wants to use. The dumper is an easier way for me.

And for that you are correct.

This mod works exceptionally well for me, maybe because I am on a vps I have complete control in my mysql and server in general. I dunno. But not a solution for everyone I suppose. I am glad that works for you.

[Deuces73]

I always get :

Backup Error : Could not write to destination file ( ../../backups/2013-03-12/Forum-2013-03-12-Access.sql )

What's wrong here ?

[djbaxter]

Originally Posted by smirkley

you could just set your date format for day of the week and that way you would be limiting your backup files to 7 total before overwrite.

Excellent suggestion. This works very well.

[djbaxter]

Originally Posted by Deuces73

I always get :

Backup Error : Could not write to destination file ( ../../backups/2013-03-12/Forum-2013-03-12-Access.sql )

What's wrong here ?

Either the file path is incorrect or the directory is lacking write permissions.

[Deuces73]

Originally Posted by djbaxter

Either the file path is incorrect or the directory is lacking write permissions.

Ok , was thinking the same.

But what folder does the ../../backups/ point to ?

I mean that as is what does the " ../../ " stand for ? Normally (thinking in DOS terms) , it should be up 2 directories from forum root , but that doesn't make much sense to me because why would it do that.

Secondly , i tried removing the " ../../ " so it says " backups/2013-03-12/Forum-2013-03-12-Access.sql " wich should point to the forum root directory , correct ? (the one with diretory adminCP and so on)

Even put it on 777 , but still doesn't write ...

[djbaxter]

Originally Posted by Deuces73

Ok , was thinking the same.

But what folder does the ../../backups/ point to ?

I mean that as is what does the " ../../ " stand for ? Normally (thinking in DOS terms) , it should be up 2 directories from forum root , but that doesn't make much sense to me because why would it do that.

Secondly , i tried removing the " ../../ " so it says " backups/2013-03-12/Forum-2013-03-12-Access.sql " wich should point to the forum root directory , correct ? (the one with diretory adminCP and so on)

Even put it on 777 , but still doesn't write ...

What you want is the path to the DIRECTORY not to a file.

Delete the "2013-03-12/Forum-2013-03-12-Access.sql " part so your entry ends in backups/ (or if that folder is from the root of where your forum is installed then all you need is "backups/").

And the permissions fopr that folder should not be 0777 (777) but rather 0755 (755).

[Deuces73]

Originally Posted by djbaxter

What you want is the path to the DIRECTORY not to a file.

Delete the "2013-03-12/Forum-2013-03-12-Access.sql " part so your entry ends in backups/ (or if that folder is from the root of where your forum is installed then all you need is "backups/").

And the permissions fopr that folder should not be 0777 (777) but rather 0755 (755).

Ok , i copied the whole link with file in my explanation but i actually used the path to the directory , not the file.

It seems that atleast " backups/ " now works since the folder " 2013-03-12 " is created.

But it stays empty and i still get :

Backup Error : Could not write to destination file ( backups/2013-03-12/Forum-2013-03-12-Access.sql )


Now , i've been reading up in this topic and found a simular problem and the answer was :

" that's a permission problem , talk to your host "

What should i ask / say to my host if this is my problem ?

[djbaxter]

Print out or copy/paste what you've written here and send that along. It may have to do with the way your directories are set up on the server, or with various security systems.