When you spend Friday night and half of Saturday debugging a "server problem" that was caused by operator error two days ago, and them not owning up to it on the spot has just made the problem significantly worse.
-
Show this thread
-
Oh it gets better. Storage snapshots show a few lines of .bash_history mysteriously disappearing... The next day. Someone's getting fired.
8 replies 4 retweets 50 likesShow this thread -
Replying to @marcan42
They always forget the backups, snapshots or shadow copies
1 reply 0 retweets 2 likes -
Replying to @littlesteve
I designed this storage infrastructure and I'm pretty sure I'm the only one who knows how to nuke the snapshots.
1 reply 0 retweets 4 likes -
Replying to @marcan42
Heh that’s how it should be, but I’m not talking about nuking the snapshots, I’m talking about when they try and cover their tracks, forgetting that backups give them up
1 reply 0 retweets 1 like -
Replying to @littlesteve
I know, I'm just saying that even if they'd known/remembered they exist I'd be surprised if they could figure out how to wipe them :-) (and it's practically impossible to fake/surgically edit them - you'd need to develop bespoke tools)
1 reply 0 retweets 1 like -
Replying to @marcan42
Hehe... for me owning up to your mistake wouldn’t be something sackable, but trying to hide it?pic.twitter.com/E1aTbP6tdA
1 reply 1 retweet 2 likes
Exactly. You fuck up? Cool, we restore from backup. You fuck up and try to hide it and lead people to waste their time looking for it meanwhile recovery becomes more difficult? Well...
-
-
Replying to @marcan42
Yep, and that’s the key issue. Even if recovery wasn’t getting harder, hiding it is straight up grounds for dismissal IMO
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.