The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
Best way to backup?
Currently I download my 'forum' folder from the ftp, is this sufficent? Whats best way to back up? I tried in the vb admin bit but got loads of errors
Thanks |
#2
|
|||
|
|||
Usually your MySQL database will not be located in your forum folder. Looks to me that you are backing up the software, but never the data.
|
#3
|
||||
|
||||
See this page for information about backing up your database: http://www.vbulletin.com/docs/html/m...nce_ssh_backup
|
#4
|
|||
|
|||
Quote:
|
#5
|
|||
|
|||
Quote:
|
#6
|
|||
|
|||
Please start by either looking into that hack, or read the chapter on backup in the vBulletin manual. A backup is something that has to be done regular, not so much use to pay someone to do it 1 time. You really should learn to do it yourself, so you can repeat it on a regular basis.
|
#7
|
|||
|
|||
Quote:
I got burned last night because of this and am still fuming about it vB.com is apparently aware of the issue and is yet to let their customers know the pre-cautions needed, if they ever will. As far as I'm concerned, this is a huge failure of communication on their part. |
#8
|
|||
|
|||
The topic of that is titled ' Backing Up The Database via SSH/Telnet'.
These are instructions on how to backup your database. Everything not in the database is obviously not covered by that topic. There is 1 issue with MySQL 4.1 and certain fieldtypes, but this is a bug in MySQL and has nothing to do with vB. |
#9
|
|||
|
|||
Quote:
vB is aware of the issue and has not warned their customers through proper channels. A developer has even given 3 queries to run on your vB database in order to combat the so-called MySQL bug. These instructions are hidden in some obscure thread over on vB.com and a search would only turn them up after it may be 'too late'. I cannot believe that you would even attempt to discredit my advise above in light of the known facts. Where's your head at? |
#10
|
|||
|
|||
Those instructions have been acurate and are still acurate for any backup/restore situation within the same MySQL version AFAIK. There is a bug in MySQL causing problems moving from MySQL 4.0 (and maybe before) to 4.1, and Jelsoft (not MySQL!!!) have spend a lot of time in finding what have been causing this problem and find a work around for it. The majority of the customers will never encounter this problem, only when they try to move to 4.1.
Once again the bug is in MySQL and not in vBulletin, and the reason and work around for it have only recently been found. The way your warning is put in your thread above make it looks like all vB customers will run into this issue, and that it is Jelsoft's fault that it is happening. I didn't deny the problem, i only tried to put your post in the correct perspective. If you feel that Jelsoft makes a mistake on this issue, please contact Jelsoft about this, or post at the official support forum vBulletin.com. vB.org has nothing to do with official support, and is not the place to make complaint about that. |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|