SOURCE: Bruce Boyers Marketing Services

October 21, 2010 07:42 ET

System Reliability Means Being Proactive

BURBANK, CA--(Marketwire - October 21, 2010) -  Most people want reliability in anything, from a car to a relationship. Yet many fail to stop and think that for anything to be reliable, there must be a proactive (rather than mainly reactive) approach to its maintenance. For an automobile, you must make sure it has oil and other fluids, that its belts are in good shape, that the tires are decent, and so on. In the case of a relationship, maintaining interest in the other person's life and making sure to spend quality time together are but two of the many factors that keep it on the rails.

In the case of a computer system, the proactive approach all too often disappears in a mass of demands and emergencies. It's not that IT personnel aren't aware of the necessity of being proactive -- on the contrary, they are usually painfully aware of it. But when undermanned, underbudgeted and overworked, sometimes the closest system staff come to being proactive is to look across the room to a server and realize it needs to be checked into -- while fielding the 37th help desk call that day.

File fragmentation is an issue that can all-too-easily become reactive instead of proactive. This is especially true when manual or scheduled defragmentation, held over from days past when one could actually find time to schedule and run it, is the only method an enterprise has at its disposal. In such a case, fragmentation is just not being addressed, and hence a good number of the "emergencies" and help desk calls are actually related to fragmentation. While reacting to these various issues, IT staff may realize that system reliability has fallen by the wayside; performance is dragging, there are unexpected hangs, crashes, freezes or disk failures, and overall HDD life has grown considerably shorter.

In the case of fragmentation, a proactive approach today is much easier than it once was. For example, technology now exists that allows system personnel to simply install a fragmentation solution, start it up, and it will automatically address the fragmentation issue from that point forward. No scheduling is required -- and system reliability is maintained and maximized.

But probably most proactive of all is the solution of preventing a majority of fragmentation before it occurs, which is also now possible. Not only is fragmentation automatically addressed and off the list of problems for system staff to tackle, most of it fails to even show up.

System reliability means a proactive approach. While such an approach may not be possible in all cases, it is at least possible -- and easily so -- in the case of fragmentation.

Contact Information