Xest wrote:A statement like that coming from you who's still QQing about years old ranger arguments is ****ing hilarious

I suppose I should feel honoured that I mean so much to you that you just can't let go thinking about me after like 2 yrs
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?
As for your comments about not knowing about GOA's backup system, you've merely proven you know nothing about running an IT based service. There should be systems in place to detect corruption, and then roll back to a time where data was non-corrupted
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.
Backupsystems do nothing but make a 'safe'backup of an existing file. If the integrity of the file is broken, the backupsystem does not know about this.
- the point is non-corrupted data shouldn't date back as far as 4 weeks, it's just a precaution in case the data was irrecoverable, after all what if the problem had got worse and the entire database had been corrupted?
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.
They'd have to write off Prydwen. A proper backup system isn't just about keeping a copy of data - it's about maintaining integrity of the backed up data - if you lose data integrity in your backups then your backup system is flawed.
No, no. There's no way a backupsystem knows IF the data which it is backing up is valid or not.
What a lot of people are failing to understand is that had GOA been slightly more unlucky this problem could've potentially escalated to the point of Prydwen being completely obliterated. 10 day downtime is appalling service, but would you still be coming here saying GOA works fine if GOA hadn't been so lucky? It could have just as easily happened purely because as shown here, GOA don't have systems in place to ensure it doesn't if there's a problem.
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 !