-- Posted by ManicD at 5:08 pm on July 18, 2008 Seems strange to me that livewires database tables corrupted a lil while ago and there were no backups to restore from, I'm aware that several topics would have been lost by doing this, but i would rather have lost a single days topics, than several months worth of past topics. Are liveWire databases backed up? why was a restore not made? and yes, i know restoring at this stage would be very time consuming but when it first happened, it would have been a case of taking LW down and deleting the old tables and restoring the new tables, and bringing it back up. -- Posted by Permious at 5:10 pm on July 18, 2008 Wouldn't LW lose some ad money when it's down? David likes ad money. -- Posted by circa at 5:10 pm on July 18, 2008 Quote: from ManicD at 8:08 pm on July 18, 2008 Are liveWire databases backed up? why was a restore not made? because davjs is the administrator. that's why nothing is ever done. -- Posted by bighead1991 at 5:10 pm on July 18, 2008 Through the way LiveWire stores topics it splits it into different tables, around 16 different ones for topics, its too hard to put any back in correctly. -- Posted by Macropiper at 5:11 pm on July 18, 2008 It would be a pain to back up the database tables up, it would also not be too helpful if they had been corrupted for a while. -- Posted by marshmellowman at 5:13 pm on July 18, 2008 Restoring from a backup that is weeks old would have deleted a lot of new topics and replies. Clearly he didn't want to do that (assuming that backups were made - which would be unfeasibly large). It's better just to lose the old replies. He could have matched the incorrectly assigned replies, but the problem is that the tables are spread across multiple databases (like a RAID) for faster access. This would have made it extremely tedious and hard to manually change the replies and usernames by hand. Then there's also the problem that David wouldn't know who made what reply. He instead deleted corrupted replies from the database together, albeit removing many topics that were fine. If there was a backup, I guess David didn't restore it immediately when it happened because he was trying to find out what caused the problem and see if he could fix it an easier way than restoring a motherload of a database. If there wasn't well then he couldn't. -- Posted by ManicD at 9:44 am on July 19, 2008 Quote: from Tangaroa at 1:11 am on July 19, 2008 It would be a pain to back up the database tables up, it would also not be too helpful if they had been corrupted for a while. Its can be automated process that can runs each day, its not hard. And normally corruption is seen pretty rapidly on LW. Quote: from marshmellowman at 1:13 am on July 19, 2008 Restoring from a backup that is weeks old would have deleted a lot of new topics and replies Then use regular backups, every 24 hours, it wouldn't be the end of the world to lose a days worth of data on a service that nobody pays for anyway. And i understand why the database corrupted and could not be repaired, but a restore would have taken a few hours at most, and recovered all but about 24Hours of data. Currently we have lost MONTHS of data. (and its annoying the shit outta me every time i look through my topics, lol)