The top ten mistakes that server management is most likely to make

1. Problems with the use of UPS (Uninterruptible Power Supply)

A store is crushing the last life of its network system. Although the 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 power outage, and this UPS is too old, it can not control the server safely shut down. Most of the battery energy is exhausted, so it quickly loses power. As a result, the controller that prevents the abnormal situation does not function as a normal shutdown server. The daily operation and transactions of the store depend on this server. It took three days to repair the server, and it took longer to make up for the damage. In fact, a battery worth only $75 can effectively prevent this from happening.

2. Didn't sort out what you need

A phone call into the company headquarters said that a server in a branch had a problem, the network administrator flew out of the office and drove for an hour. The location of the accident. As a result, he found that the operating system file was destroyed a part, so that all he could do was reinstall the operating system. The network administrator of the branch couldn't find the installation disk at the moment. It doesn't matter. The administrator of the headquarters has it, but in his office - one hour from here and two hours from round-trip. Pack up a backpack and take it with you. Everything you might need, including the operating system backups your users use, should be in your backpack. This is easy to do, does not require anything, but can play a key role in updating the operating system and the like.

3. No patch installed

A toy manufacturer's server connection has gone wrong, causing all staff to lose contact with their files and production was forced to stop for two days. The loss is serious! A newly hired network administrator is responsible for resolving this crisis. He soon discovered that the previous network administrator did not install the patch when he installed the system three years ago.

Patches are freely available, maybe they are not open, but they are usually very easy to configure and can be done by any system administrator. The former administrator said that because the system is running very well, there is no need to patch. This statement is obviously very irresponsible.

4. Improper backup work

A server in the hospital office that stores a lot of medical documents and medical records has failed. Because there is no information on the server that can be accessed, the operations of the office basically stop. The network administrator immediately took out a tape backing up the document and tried to fix it. When she found out that the belt was empty, the heart sank. She checked the other backup tapes, which were all empty! She checked the office log and found that the same time they replaced the backup tape every day for two years, but the tape was placed in the server where the backup software was never installed. No one knew that the backup had problems because no one had ever checked it, but only two. In the year, insist on replacing the blank backup tape every day. This incident caused the hospital to suffer a lot. In fact, as long as any database administrator does a simple backup check, this major problem can be avoided. In fact, they are doing this every day.

5. Inferior cable line engineering

A bank's network often has problems. For this reason, they specifically checked the wiring box. The inspection found that many RJ-11 and RJ- The plug of 12 is inserted into the RJ-45 socket. Moreover, a toothpick is inserted in each socket, so that the cable route of the cloth is no problem. Many network problems are attributed to improper cable connections, so savvy managers should have a licensed, secured, and trustworthy cable line contractor to route the cable.

6. There are too many devices to change hands and internal problems.

A professional sports group bought a brand-name server, but it started to work when it started to work. The network administrator makes a request for assistance to operating system vendors and hardware vendors. It was later discovered that the resellers who provided this "branded server" were configured with non-branded memory, non-branded disk controllers, and non-branded external disk drives, simply because these components were cheaper. The hardware vendor and operating system vendor refused to provide support because the server was confused by some non-branded components and its structure was not easily identifiable.

7. No authorization contract signed

An office spent a lot of cash on the server last year. The system has RAID 5 redundancy protection, dual power supplies and 24× 7 support, and a year later, the drive is broken. Guaranteed 24× 7 support staff came, he called the hardware manufacturer, the manufacturer asked him what the contract number is, and the office did not sign the authorization contract before. “It’s okay, the vendor said, “They have two years from the expiration of the license, and I will give you a replacement drive within five or six days.

However, the tolerance of the manufacturer is not enough. It is best to ensure that you have a full set of 24× 7 support, go to an office supply store to buy labels, write the license number and technical support on each label. Phone numbers and then stick them on each machine.

8. No test environment established

A few years ago, a software development company installed a new workstation, which uses the fastest random access memory, the fastest hard drive. The drive and the fastest processor will be the new workstation for the chairman. Shortly after the installation was completed, the chairman accepted a request from his largest partner company to test the communication platform of the new artificial space station. The result was a blue screen. When he restarted the computer with surprise, the information stored internally was gone. After rebuilding the system, it took him another four days to get rid of the pile of operating guides.

The chairman of another company is smarter and built a test network. Before the system is upgraded, they will do the experiment on the test network, find the error again and again, and repeatedly set the network to test until it is completely correct. Only when the test results are completely correct will they really start the system upgrade.

The chairman of the first company no longer uses his own server as a tester.

9. Storage capacity planning is not good

When an art company bought a server five years ago, the server can support six 8G-byte RAID Array 5 drives. In order to save money, the company insisted on buying only four 4G-byte drives. The network administrator said that they would need more space soon, and the company eventually compromised and bought two more drives, which ended the matter. After three years they had a serious lack of space, they even had to delete small files with only 50K bytes. They urgently need to expand their capacity, and at that time 8G-byte drives could not be bought, and larger servers could not support them. A new extra subsystem that solves this problem will require more money than the original server. In this way, they have to replace the server two years ahead of schedule. Therefore, doing a storage capacity plan will save you money and may even greatly extend the life of your system.

10. The wrong operation is the biggest hidden danger

The power of the office in the afternoon suddenly broke, and the nervous office manager thought it would damage their two servers, so he took quick action- ―He went over and turned off the server. When he got home, he was also proud of his quick action. But the next morning, when he returned to the office to open two servers, he found that nothing was inside. In fact, when he pressed the server switch yesterday, the server was doing complex updates of critical files. When he stopped working on one server, it affected the storage of another server's critical database. It took two days to repair the network work.

This is the most unpredictable of all the problems of protecting the network. Therefore, the technical quality of network users must be improved.