Im not surprised you really think like that. Tell me Xest, do you ever leave the house or is the ego not fitting through the door anymore?
No, I took my photos of Canada and the US from hacking into a NASA spy satellite. Funny how you comment on me not going out yet you're the one who still holds a grudge against me and can't let go after all this time, if your life is so exciting and busy you'd have forgotten about any problems with me long ago.
An intrigueing point. Obviously times available where rollbacks are available from are times when a backup is made. There's no easy feasible way for a system to 'know' if the data is corrupted or not. For a dynamic, continously changing set of data you cannot create hashes or CRC-checksums. The amount of 'AI' required for a system to see if a database is corrupted is very hard to create. Trash would be relatively easy to recognize (tho not even realmtime most likely) but dupes and cross-links on a big database is almost impossible to do.
This was true around 10 years ago, but modern systems are more than capable of performing error checking and highlighting issues long before 66,000 records become corrupted

Corruption of a database should be noticed long before that. Do you really beleive all the fortune 500 companies for example have database systems that are equally prone to corrupted backup data that's entirely unrecoverable?
Well 4 weeks was a number you came up with (how far backups of the system should made). I already pointed out 4 weeks is silly - as restoring a 4-week old database is something nobody really wants.
4 weeks old data is a billion times better than no data at all.
Ehmmm.. What makes you think they DONT have a backup of 4 weeks old? More to the point: The current solution offered is considered better by GOA then a (bigger) rollback. In the worst case scenario they could have been forced to rollback to a time where the database wasnt corrupted (yet). Your jumping to conclusions that there is no backup at all available. More likely then not there is, but GOA decided NOT to rollback to that backup. Most likely GOA figured (for example) a rollback of a week would been worse then 66.000 items purged. I dont know the exact details on that decision, and nobody does except GOA-employees. I do know for a fact Im far happier with the current solution then a week-rollback. I could have kissed my new druid-template goodbye and remake it. Including asking guildies to craft MP for me... again !
Fair comments - my point is that either way this is unacceptable, this amount of downtime and data loss isn't possible in a company with proper systems in place to deal with this kind of problem and that's the core issue here - it doesn't matter the details, it's the amount of downtime and data loss that's the real issue and shouldn't be possible.