Version: 2.12, by Paul M
Developer Last Online: Nov 2023
Category: Administrative and Maintenance Tools -
Version: 3.6.x
Rating:
Released: 09-17-2006
Last Update: 10-09-2006
Installs: 582
Auto-Templates
Re-useable Code Additional Files Translations
No support by the author.
This modification is no longer available or supported.
When vb 3.5 first came out I was using this backup system on my vb 3.0 - and having nothing better to use - I converted it to work on vb 3.5 (here) and since then I have cut it down and adapted it for vb 3.6.
The original version was by Trigunflame and the rights to the code were bought by Zoints (D.Chapman) in January. A while ago David gave me permission to release my adaption, but until now I haven't got round to it. Trigunflame did mention a few months ago he was working on a new version, but nothing ever appeared.
I have stripped out much of the extra stuff that I do not use (or indeed, could not get to work). This is a simple (lite) version that does a php based dump of your database either as one file, or one file per table. It's been in use on our forum since the day 3.6 was installed.
Notes:
* I will not add anything new to this, or spend vast amounts of time supporting it.
* This is a Lite version to allow people to use the basic 3.0 backup functionality on 3.6.
History:
v2.10 : First internal version. v2.11 : Bug fixes, some code changes. v2.12 : Initial Public Release.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Are you trying to execute this backup from phpMyAdmin or from within vBulletin?
If it's the former, I have justed tested the export function and it worked successfully - you just need to remember to compress the database in a zipped archive at export. If it's the latter, then vBulletin need to explain what it is that needs to be changed, as we cannot be expected to support the workings of their application.
However, judging by the error message you kindly supplied, I would guess that vBulletin requires a bigger PHP memory limit in order to run the backup function. It could be that vBulletin's backup function doesn't compress the database sufficiently or requires a large memory limit - you can increase PHP memory limit using php.ini.
In any event, executing the backup from phpMyAdmin works. If there are functions within vBulletin that are being limited by your current server configuration, please obtain details from vBulletin as to the necessary server requirements so that we can assist you in making the necessary changes. If you have any further questions, please don't hesitate to contact us.
With kind regards from Berlin
Above is the reply I got from my hosts.
I managed to download a backup via vbulletin where I can save to the pc, however if I try to use this mod, or use vbulletins feature and try to save to my webspace it comes back with the memory error.
Would increasing the PHP memory limit using php.ini help? If it would i'll get back in touch with them as I have no idea what it is!
Failing that, anything else I need to ask the hosts?
Quite possibly yes, it would. What is your current limit (check in your ACP, at the top of the index page).
Quote:
Server Type SunOS
Web Server Apache v1.3.37 (cgi)
PHP 4.4.7 P
PHP Max Post Size 8.00 MB
PHP Maximum Upload Size 2.00 MB
PHP Memory Limit 20.00 MB
MySQL Version 4.0.27-log
MySQL Packet Size 1.00 MB
I tried using MySqlDumper as well and that timed out as well. That showed I had a Max Execution Time of 30 seconds.
However the chap I spoke to wasnt sure where you would need to place this in the vbulletin directory. Any ideas where I would need to place it? The male was also quite shocked at the size of my DB - currentyl 65MB - Is this large in terms of forums?
You need to ask your host about where to put your ini file.
65M is a fairly small database.
BTW, I would suggest you change the php memory limit to 64M, it's normally set in multiples of 2 (i.e. 4,8,16,32,64,128 etc) - and is not related to the database size.
You need to ask your host about where to put your ini file.
65M is a fairly small database.
BTW, I would suggest you change the php memory limit to 64M, it's normally set in multiples of 2 (i.e. 4,8,16,32,64,128 etc) - and is not related to the database size.
Thanks, I'll alter to 64.
He said as he's never used vbulletin before he had no idea what directory it had to go in. I'll check over on vb.com
Thank for all your help, hopefully i'll get this to work!