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

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.

See this page for information about backing up your database: http://www.vbulletin.com/docs/html/m...nce_ssh_backup

you might want to check this out for a simple, automated solution..

Thanks, can anyone help me with it pls and maybe back up my forum?? I can pay something small if need be.

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.

If you value your attachments/avatars/profile pictures, DO NOT use those instructions for backing up your database unless you do some further investigation (version of MySQL being used would be the main one apparently).

I got burned last night because of this and am still fuming about it :mad:

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.

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.

Don't attempt to gloss this over and say everything is hunky-dory :mad:

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?

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.

I have made a post on the official support forums

The majority? How the heck would you know this? I upgraded to a MySQL v4.x last year (straight from v3.x.x whatever)... I had been doing mysqldump's all the time since... and only now do I know that they were useless backups if I valued my attachments/images in the database.

I was and still am angry because I found out that, as you said, Jelsoft was aware of the problem and did not warn customers about the potential problems. I was affected by this 'bug' greatly. I lost over 5 years worth of "data".

Now, as I see it, you are pushing a user here to use the mysqldump facility to back-up their database. You did not warn the user at all that there could be a serious potential problem, a problem that you admit you are aware of.

Jelsoft has identified the problem and have provided the necessary "fix" of 3 queries to run. Why has this not been packaged up into an "patch/upgrade" file, posted in the members download area, and a E-bulletin sent out? It is Jelsoft's duty to protect all their customers. If there is a known issue and a fix for it is available made by Jelsoft, that needs to be conveyed to their customer base immediately through appropriate channels.

What is the difference between this and a PHP "bug" that can cause a security breach? Both can result in huge ammounts of data loss, no?

Now, my original post told the thread starter to be careful as there could be potential problems using the method(s) you linked to for backing up the database. This is a known fact.

But I will retract that statement and just let my fellow customer possibly lose data because apparently that is the more helpful thing to do here on vb.org

Like i said before, Jelsoft is only aware that there is this problem with MySQL for a very short time now (a few weeks maximum).

And i can understand that you feel angry about this happening to you, but please use the proper channels if you feel that Jelsoft is anything to blame for this. vB.org is not the place for that.

OK, forget everything I've said.

@whateveramen,

There is a known issue that may affect the use of backing up your database using the mysqldump facility through SSH. Please do a search on vB.com using the terms "bad attachments" and you will find a thread that discusses the problem and the fix supplied by Jelsoft staff. It is better to be safe than sorry in the horrific event that you are one of the so-called few affected by this bug and your forums get wiped out for whatever reason.

I hope this helps you in determining the best way to back up your forums safely and that you don't, God forbid, lose any data that is valuable to you.

Good luck!

@everyone,

This is the last time I will try and share potential problems that I am aware of when using vB and associated tasks. This is not the place for it and I apologise for the inconvenience.

Cheers,

~Regs.