Version: 1.00, by Birdie501
Developer Last Online: Feb 2011
Version: 2.2.x
Rating:
Released: 04-19-2002
Last Update: Never
Installs: 57
Is in Beta Stage
No support by the author.
################################################## ###############
MySQL Database Backup/Restore Hack Ver. 1.0
for all versions! tested with vb 2.2.5
Release Date: 20.04.2002
by Birdie501
Credits to: Jens Dutzi
################################################## ################
What this hack does:
You can backup and restore your mysql database via Admin CP!
Lot of people have problems to restore their database du to server timeouts!
With this hack you will never have any problems!
But anyhow you will use this hack with your own risk!
Requirements: Unix, GZIP, MySQL, MySQLDump
I am not a programmer! I just tried to implement this feature into my vbulletin and it works!
Maybe some of you, have the possibility to improve this hack! You are welcome!
Enjoy guys=))
Birdie501
just updated the instructions for the root path!
zip file updated!
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
guess what man i payed for vbultin just to download ur hack lol
man i swear iam not ++++ing u i have diffrant forums and our hosting servers dont alow ssh or tel net
i have aproblem iam not geting any errors at all
every thing is cool the back up but in restore it says every thing restored
you go to the forum and boof nothing restored i did that over
4 times hosting on free bsd and all is cool as i told u no erros
just that the restore goes ok but in real it wont restore any thing
any idea will be so much happy 2 hear it
regards :glasses:
my backup worked perfectly, but the restore doesn't work at all. I wanted to move servers using this, uploaded the compressed sql-file to my admin/backup directory on the new server, changed the variables, and clicked restore.
decompress backup: done!
restore file to database: done!
is the answer, but actually the db isn't restored.
never mind, I discovered the problem was a mistake in the hack code that wasn't even updated in the original instruction file, so if you're going to install be sure to read all the post and look for the area of the code that needs to be changed.
Today at 01:52 AM laycomp said this in Post #127 never mind, I discovered the problem was a mistake in the hack code that wasn't even updated in the original instruction file, so if you're going to install be sure to read all the post and look for the area of the code that needs to be changed.
I read the whole thread and I must have missed the code change you were talking about. Can you point me to it, please?
mmm... I tried going to the whole thread too to point out the changes, but sorry, maybe I didn't look good enough, anyways, I made the change in my install file and attached it, if you use it you shouldn't go wrong -at least I didn't.
Compare mine with the original install txt file and when you see the difference then you can search for the text and find the original posts that talks about the change in code. This I suggest you do.
I'd wish that whenever changes were made, developers took the time to upload the new files, so many people's time is plain wasted