The way I read it, you didn't destroy anything. You had a moment of panic, and could have created real problems.
Regardless, same lessons learned right? :) Whether the server is gone or not, it could have been, and the way we work changes drastically after a real world scare like this.
Did you ever tell the boss, or did you just let it ride? There's nothing like going to the boss in a cold sweat and the old "I f*ed up" look on your face.
I just let it ride at the time. When I joined the company there wasn't any other tech guy around except me (our tech guy was on a vacation). So I was left alone for a while, and had to sort out of lot of craziness :)
He put himself in a position where only chance protected him from a disaster. (Imagine if the update did trash the running server.) That's reason enough for a good sysadmin to be worried, IMO.
Comments
The way I read it, you didn't destroy anything. You had a moment of panic, and could have created real problems.
Regardless, same lessons learned right? :) Whether the server is gone or not, it could have been, and the way we work changes drastically after a real world scare like this.
Did you ever tell the boss, or did you just let it ride? There's nothing like going to the boss in a cold sweat and the old "I f*ed up" look on your face.
I just let it ride at the time. When I joined the company there wasn't any other tech guy around except me (our tech guy was on a vacation). So I was left alone for a while, and had to sort out of lot of craziness :)
He put himself in a position where only chance protected him from a disaster. (Imagine if the update did trash the running server.) That's reason enough for a good sysadmin to be worried, IMO.