Overlooked the " 1 file " setting , as i read that default settings where the way to go and assumed that 1 file would be default.

So if anyone encounters a simular problem , try setting :

to " Yes " as it appears to be on no by default.

Result :


Processed Database in 50.898 seconds

Backup Completed Successfully
Done

;)

Well that's me lost already, sorry but I haven't a clue what this means.

I haven't seen it mentioned, does this do a recovery as well ?

If you mean a database recovery, this mechanism just creates the backup files.

For me, I would do a recovery via phpMyAdmin in my server control panel, using the backup file I selected.

Having a problem. VB 4.1.12. No idea where to look. When I try to run a backup by clicking Run Now from the Scheduled Task Manager, I immediately get a message that says:

Automatic Database Backup for vBulletin
Backup Aborted : vBulletin Options Error

Any help would be appreciated.

Thanks!

Are you using some form of datastore cache ?

Basically that means the code failed to load your options.

I'm new altogether to this "cron job" and don't understand how to run the backup.

I already have the Mod marked as Installed as well as the mod installed through my FTP.

So my questions are:

- What do I do from here?

- How do I access this "cron jobs" and set it up?

- How do I make it automated to run per week basis?

Do you install the product as well ? That create the cron job for you.

For the settings go to:
AdminCP > Options > vBulletin Automatic Backup

For the cron job schedule go to:
AdminCP > Scheduled Task Manager > Automatic Database Backup for vBulletin

And I know this thread has 56 pages so far, but trust me from experience, most questions you could ask are in here somewhere.

It took me about two times reading all the pages to figure it out.

I'm kinda slow sometimes. :o

Just tried this on a larger database and though I had timeout issues but it turns out that the database backup file gets too large for the file system and the server kills the script.

This is an issue which could be affecting people with large databases. If the backup file gets to 2Gigabytes (2,147,483,648 Bytes) it will stop creating the file and you will see "child pid xxxxx exit signal File size limit exceeded (25)" in the server error log. The backup file will be stuck at 2,147,483,647 Bytes.

This is because linux can only create files up to 2GB on a 32bit operating system.

To get around this just change the "Combine Files" setting to "No" and each table will be backed up individually. So long as an individual table is no large than 2GB it will work :)