Meanwhile, a number of people from Knowing (https://www.zhihu.com/question/58802374) were horrified by the libraries that had been deleted, and are still haunted to this day by.
A new graduate in the company is very weak at work and doesn't know how to do anything. Just start by asking her to help inventory the equipment assets in the server room.
Just because there was an asset tag that was hard to read, she pulled the blade server right out, and the person next to her with her saw it and was instantly petrified. The business system was down for ten minutes and the leader didn't say anything, he just wouldn't let her continue the inventory, and she, for one, didn't even know she was in trouble.
Years ago (2001), when it was still a Unix character interface, I was doing routine maintenance in the middle of the night and deleted a library containing 200,000 books. After ten minutes of confirming to myself that something was wrong, I started sweating and my stomach felt like it had been punched so hard it started cramping and hurt so much I couldn't sit down.
It took a while for me to go over to the channel and smoke two cigarettes before I recalled that I'd done a full system backup the day before and not much data had been lost!
It was a feeling that will last a lifetime.
The server is on Vultr, with more than 1000 users and a lot of visitors. One day I opened another test machine on Vultr, and when I was done testing and ready to delete it, I deleted the wrong machine and deleted the one with the website ...... (Need to gripe about Vultr's server interface, I thought the newly opened machine must be the one at the bottom, then deleted it without looking, not realising the one at the bottom wasn't the latest one opened! )
At that time, I can only say that I was very panicked, as if in a dream, sweating, I could only watch a message indicating the success of the deletion, then immediately submitted a ticket, Vultr told me that the deleted machine is not recoverable, instantly felt that a long time of business all for naught, it is hard to imagine that after operating for so long a mistake operation is all finished.
I found out later that that machine had been backed up before, and opened another machine to restore the image to the new one, a week ago, so at least it was saved, and the lost data was later replaced manually by myself.
The moment I deleted it, so many users came to me, I could only reply calmly that it was under maintenance, in actual panic, after the problem was almost solved, my own back was wet, never want to have it again, remember to make a backup, remember remember remember!
What else could we have done in those years, before running away?
Compared with the above deletion of the library incident, many netizens questioned the results and system of Shunfeng, have said: dismissed the engineers involved, Shunfeng itself is completely free of responsibility? All those lessons spent to train an OPM and just give it away?
Dissecting the surface, we can't help but think deeply, can Sooner really set aside its responsibility for the process issues due to the sacking? The accident, the good news is that the impact has not yet caused irreparable consequences, Shunfeng should do is not the first time to dismiss the employees involved, but through the lesson to see the internal problems:.
The deletion of the library incident occurred on the one hand due to the engineer's own mistakes, on the other hand, does it reflect the laxity of the daily management process, and the irregularity of the operation?
There is no separation of safety responsibilities and their direct supervisors should not be held responsible, except for the employee involved?
Confusing permissions control, where only one Ops engineer can directly manipulate the database?
Weak disaster recovery capabilities, and the incident took 590 minutes from occurrence to recovery for the large SF enterprise?
Therefore, in view of the above problems, how can we avoid the recurrence of incidents such as "running away" from the deletion of banks again?
In this regard, while companies first do a good job of managing permissions and multiple auditing mechanisms, CSDN has also taught many programmers how to
Use rm carefully on Linux
To avoid the tragedy of running from deletion of the library to.
One option is to redirect the rm command to be grafted to the mv command, which is the equivalent of a custom recycle bin for Linux systems. This is achieved as follows.