10 more common server management errors

Error | server

The job of network management is to ensure the normal work of the network, so that the work of workers are not interrupted. The problem is that things do not always go according to ideal conditions, and in fact there is often a disturbance in the ground. There are many reasons for this, and here we discuss only 10 of the more common network management errors.

1.UPS (uninterruptible power supply) Usage problem

A store is squeezing the last life of its network system. Although that very old server is almost impossible to meet the needs of the store operation, the operator is not even willing to replace the battery in the UPS, in fact the battery should be replaced every two years. Finally one day suddenly a power outage, and this ups is too old, it has been unable to control the server security shutdown. Most of the battery's energy has been depleted, so it soon ran out of power. As a result, controllers that prevent and control anomalies do not function properly to shut down the server. The daily operation and trading of the store depend on this server. Repairing the server took three days, and it took longer to make up for the damage. In fact, a battery worth only 75 dollars can effectively prevent this from happening.

2. There is no need to tidy up the things that have gone wrong, the network manager rushed out of the office, drove an hour to reach the scene of the accident. As a result, he found that the operating system file was partially destroyed, so that all he could do was reinstall the operating system. The branch's network administrator could not find the installation disk, it doesn't matter, the headquarters of the administrator has, but in his office-a one-way one-hour, round trip two hours. Pack up a backpack and carry it with you. All the things you might need, including the backup of the operating system your users use, should be in your backpack. This is easy to do and does not cost anything, but it can play a key role in issues such as updating the operating system.

3. There is no installation patch connection out of the problem, so that all staff and their own documents have lost contact, production was forced to stop for two days. The damage is serious! A newly hired network administrator is responsible for resolving the crisis. He soon found that the previous network administrator installed the system three years ago without installing patches.

Patches are provided free of charge and may not be open, but they are usually easy to configure and can be done by any system administrator. The previous administrator said that because the system is running well, it does not need to be patched. This is clearly a very irresponsible statement.

4. The backup work improperly failed. Because no information on the server can be accessed, the operation of the office is basically stopped. The network administrator immediately takes out a tape of the backup document and tries to fix it. When she found the tape was empty, the heart sank down. She checked the other backup tapes and it was all empty! She checked the office logs and found that colleagues had changed their backup belts every day for two years, only that the tapes had been put into a server that had never been installed with backup software, and no one knew that the backup was problematic because no one had ever checked it, but only two years on a daily basis. The incident cost the hospital dearly. In fact, as long as any one of the database administrator to do a simple backup check to avoid this major problem occurred. As a matter of fact, they are doing it every day.

5. Inferior Cable Line Engineering

A bank's network often goes wrong, for which they checked the wiring box and found that many RJ-11 and RJ-12 plugs were plugged into the RJ-45 socket. and in each socket inserted a toothpick, so that the cable lines of cloth is no wonder that there is a problem. Many network problems are due to improper cabling, so savvy managers would be better off with a licensed, secured and trustworthy cable contractor to rack up cable lines.

6. The equipment changed hands too many times, the internal composition of the problem, but it began to work on the problem. The network administrator requests help from the operating system manufacturer and hardware manufacturer. It was later found that the resale merchant, which provided the "brand" server, configured the server with a brand-name memory, a non-branded disk controller, and an external disk drive that was not brand-name, because the components were cheaper. The hardware manufacturer and the operating system manufacturer refused to provide support because the server was confused by some of the non-designer components and its structure was not easily identified.

7. No authorization contract has been signed. The system has a RAID 5 redundancy protection, dual power supply and 24x7 support, and a year later, the drive has broken down. The staff who guaranteed 24x7 support arrived, he called the hardware manufacturer, and the manufacturer asked him what the contract number was, and the office did not sign an authorization contract. "It doesn't matter," the manufacturer said, "They are two years away from the expiration date and I will give you a replacement drive within five or six days." ”

However, the tolerance of manufacturers is not enough, it is best to ensure that you have full 24x7 support, go to an office supply store to buy labels, on each label to write the license contract number and technical support of the phone number, and then put them on each machine.

8. No test environment established

A few years ago, a software development company installed a new workstation that used the fastest random access memory, the fastest hard drive and the fastest processor, and it would serve as the Chairman's new workstation. Shortly after the installation was completed, the Chairman accepted a request from his largest partner to test the communications platform for the new man-made cosmic station, with the result of a blue screen. When he was surprised to restart the computer, there was nothing in the information that was kept inside. After rebuilding the system, it took him another four days to get out of that pile of operating instructions.

The chairman of another company was smarter and built a test network. Before the system is upgraded, they do experiments on the test network, again and again to find errors, and repeatedly set the network to experiment until it is completely correct. Only when the test results are completely correct do they actually expand the system.

The chairman of the first company never used his server as a tester anymore.

9. When storage capacity is poorly planned, the server can support six 8g-byte RAID Array 5 drives. To save money, the company insists on buying only four 4g-byte drives. The network administrator said that soon they would need more space, the company finally compromised, bought more than two drives, so the end of the matter. After three years they had a serious lack of space, and they even had to delete small files that were only 50K byte. They desperately need to expand capacity, while 8g-byte drives are not available, and larger servers are not supported. A new additional subsystem that solves the problem will require more money than the original server. In this way, they have to replace the server two years ahead of schedule. Therefore, a good storage capacity plan, you can save money, and may even greatly extend your system life.

10. Error operation is the biggest hidden trouble

In the afternoon the office power was suddenly cut off, and the nervous office manager thought it would damage their two servers, so he took quick action-he went over and turned off the servers. When he got home, he was proud of his quick action. But the next morning, when he returned to his office to open two servers, he found nothing in the contents. In fact, when he pressed the server switch yesterday, the server was working on a complex update of critical files, and when he stopped working on one server, it affected the disk of another server's critical database. As a result, it took two days to repair the network work.

This is the most unpredictable of all the issues that protect network work. Therefore, it is necessary to improve the technical quality of the users of the network.