You should still upgrade to 4.2.2 for both security and bug fixes.
I agree we should upgrade to 4.2.2 - but I would prefer to upgrade an error free version of vBulletin. I think upgrading while having potential corruption issues would just cause more trouble then it would be worth.
It is definitely something we will look at after getting over this obstacle though.
Actually yes, the back-up happens around the same time.
My host has moved the scheduled backup to an earlier time for tonight - seeing if that makes a difference.
Do you know of an issue that relates to the backup?
Yes, we had something similiar. We found out that our ftp/server-repository had no space left and the backup task was setup to lock the tables and site until the backup was complete. Esp. the last point locked us out, flagged the site as inactive and we had to set the status back to active (deleting the unfinished backup task and restarting the server) via ssl first. Because there was no space left on the repository device (misconfiguration 6 yrs ago ) we had to alter the partition sizes used.
Yes, we had something similiar. We found out that our ftp/server-repository had no space left and the backup task was setup to lock the tables and site until the backup was complete.
Hi Marv,
Some great information there. Really appreciate it.
I have been speaking with my host and we are going to try a few things to hopefully isolate the cause of the crashes.
cPanel doesn't do a good job with large databases. Currently I use R1Soft CDP backup with the mysql extension and have no issues. I haven't used it to restore from any issues but I would like a more traditional backup option myself. It would be interesting to see whatever everyone else is using.
MSQLD is a great tool. Unfortunal, MySQLDump wasn?t really helpful in our case. We had to repair some tables and a few were about 1.6 to 2.4GB. MSQLD couldn?t write this table back to the database, just because of the sheer amount of data. In the end we had to do this via the console. Any known workaround for MSQLD and big tables?
I agree we should upgrade to 4.2.2 - but I would prefer to upgrade an error free version of vBulletin. I think upgrading while having potential corruption issues would just cause more trouble then it would be worth.
It is definitely something we will look at after getting over this obstacle though.
Sometimes such issues may be caused by bugs in earlier versions.
At the risk of sounding like a stuck record - you really need to upgrade.
It's not just about bugs, your site is *definitely* insecure at the moment due to unpatched security issues. To patch those you need to upgrade.