Unix maintenance and troubleshooting

If the solution didn't 2. I The Troubleshooting Process now be operating with no redundancy. In the example problem, it was quickly determined that there were two elements common to the problem accounts but not to the working accounts.

Windows server maintenance best practices

Some of these possibilities e. Identify the server problem's area of effect One of the first pieces of information you need is how widespread the outage or slowdown is, as well as what it affects. It was also observed that members of the operations staff were able to log in. Some of the student users of a university system are unable to log in, and some who have already logged in are now having various problems. Please login. Take a step back, and think about how to logically resolve an issue during an outage. For intermittent problems, it's extremely important to record the environment and actions as accurately as possible. Software Features and Research Knowledgeable professionals are ready to provide information on the latest product features and documented problems and solutions. It may be that these pieces of information are sufficient to identify the problem.

Did the system configuration change? Our technical service managers are all senior level and have an average of over 24 years of real-world experience. And no matter how much redundancy is present in your system, a severe I Chapter 2 2.

The easiest problems to solve are the ones that are prevented from occurring at all.

server maintenance plan

You might have a cold, the flu, a virus, or some obscure disease that you've never heard of before. For now, we'll leave it and go on to discuss problem identification.

At first glance, it may seem unnecessary to list problem detection as a distinct component of the troubleshooting process. So how do you identify a problem?

Basic network and server maintenance checklist template

We'll continue to follow this problem through the remaining components of the troubleshooting process. There are times when a full solution may be too expensive, time-consuming, or risky to implement immediately; in such cases, a workaround can serve as a temporary measure until the real problem can be fixed. Is it in a safe place? But because the root cause of the problem was not identified and corrected, the problem may crop up again and again. Disaster recovery is a topic beyond the scope of this book, but you should at least think about the questions listed below. Please check the box if you want to proceed. Fully characterizing the problem often requires the troubleshooter to perform some actions and observe the results. I The Troubleshooting Process When this happens, identification becomes an iterative process. This, in fact, is the key difference between detection and identification. Other students, however, are able to log in with no problem. After comparing a few users of both types, it becomes apparent that the problem is affecting only users with home directories on a particular disk. However, if a problem is first noticed by users working on the system, it must be reported to an administrator before it can be resolved. What infrastructure lives where? After identifying a problem and determining its solution, you might decide that implementing the solution is so disruptive or risky that it's better to use a workaround or, if no workaround is possible, to just live with the problem. It may be that these pieces of information are sufficient to identify the problem.

Using your troubleshooting resources and the techniques described in section 2.

Rated 7/10 based on 86 review
System booting to maintenance mode