3 ms·
How else can they explain this outage? I guess it could be "we accidentally deleted the production database." But at that point they would just be euphemizing
by roflc0ptic 11y ago
How else can they explain this outage?
I guess it could be "we accidentally deleted the production database." But at that point they would just be euphemizing - clearly someone pulled the trigger. If they were naming the person, that would be pretty terrible on their part. But they're not. It seems perfectly fine to my eyes.
- ninju 11y agoThey could have initially said that we are encountering a database issue requiring a database restore. Once the system has been fully restored they can provide more details as to the "database issue"
- abluecloud 11y ago"faulty SQL queries caused us to have to restore the database"
- ww520 11y agoThe person might be under the gun from someone else to fix the prior problem, and made a mistake under pressure. Singling out the admin just absolves management from any blame. And it shows the lack of leadership and the lack of willingness to take on responsibility for the organization. And the problem is clearly a organizational problem. There's no clear backup and restore procedure. It's probably never tested for restore. There's no failover. There's no disaster recovery. Even if it's there, it has not been fire-drilled periodically. There's no clear access procedure in protecting the production servers. There's no prior spell out of definite steps to address production problems before doing them. There's no rollback procedure. There's no review. There's no approval process.
- roflc0ptic 11y agoThat is a good explanation. I see why blaming the admin is problematic. Thanks.