OFPEC Forum
OFPEC The Editing Center => General Announcements => Topic started by: macguba on 05 Feb 2007, 10:48:32
-
What the headline says.
Details in bedges' news post. (http://www.ofpec.com/index.php)
Get posting! :good:
-
Welcome back OFPEC, I'm so happy to see forums back up and running. I take it you lads have had a bit of a nightmare of late!
Anyway I've re-registered and look forward to the invaluable info this site provides, thanks for all the hard work.
Turk.
-
Yay! This is "Jack" btw, I've taken this chance to put my name what I wanted it to be when I first registered and didn't by accident.
-
Hello, hello guys!
That was a long month :).
Hopefully we can get OFPEC back up running in all it's glory really fast.
-
What happened to the sql backups?
Ahh well your back now, welcome back 8)
-
What happened to the sql backups?
All the backups since 24th of October were incomplete, caused by the sql server crapping out, caused by a horrifyingly big error log. Here's an example.
Normal OFPEC Database
table_A -- normal size
table_B -- normal size
errorlogs table -- normal size
messages table -- normal size
table_F -- normal size
table_G -- normal size
...
full backup containing everything
OFPEC database with huge error log
table_A -- normal size
table_B -- normal size
errorlogs table -- HUUUUUUGE BIG ASS SIZE -- server makes backup and thinks "whoa this is enough for me, I'll just cut it from here"
messages table -- normal size -- doesn't make it in the backup
table_G -- normal size -- doesn't make it in the backup
...
backup contains everything before the logs table and some of the logs table, but nothing that comes after the logs table, like message data.
-
Thats a shame, a lot of important information was lost during the downtime with Armed Assault. Let's hope we can a lot of it back.
-
just a lil hint.
When importing those info in the db, did any-1 ever thought of NOT importing the errors table? ( there is NO important info there )
im happy to help out if allowed to....
removed unnecessary quote... bedges
-
It wasn't importing that caused the dump to be cut, it was cut during exporting, ie. while the server was writing the dump. Unfortunately our host doesn't offer a way to export selected tables only. In the future, we'll just have to check each backup dump by hand.