If I wanted to measure the downtine of my servers would it make a difference if the downtime is planned or unplanned. I have heard somesay downtime is downtime.
Downtime is downtime and should be measured. But is it when the server is not in use anyways? or When there is a back up server to take its place during the downtime if planned. If not and it effects work hours then yeah its downtime still and should be measured as such. But you can separate the measurements to show reliability of your system by having most downtime as planned and hardly any unplanned downtime.
Last Wiki Answer Submitted: November 10, 2010 2:52 pm by FrankTheTank1,200 pts.
All Answer Wiki Contributors: FrankTheTank1,200 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
…would it make a difference if the downtime is planned or unplanned.
That would depend on the purpose of the measurement.
If you simply need to measure how much time the system was available for handling business processing, it doesn’t matter much what the reason was for downtime. You aren’t actually measuring downtime in that case; you’re actually measuring uptime.
If you are attempting to quantify how much downtime is used for administrative (planned) work and how much is used for unplanned work, then of course the difference is important.
A higher amount of unplanned downtime might indicate there are reliability problems with hardware, software or people. A higher amount of planned downtime (that is troublesome) might indicate that processes need to be changed.
It depends on why you are gathering measurements in the first place.
Unplanned downtime means that server has some issues. Planned downtime usually belongs to hardware upgrade/ backup/ server maintenance/etc … but one thing is clear downtime is downtime, however, if this your main concern, then you can opt load balancing servers or server mirroring solution, where one server play the role of master server and second one act like a slave server. So in case master server goes down due to any reason slave server takes it place without any downtime. For more information you can check this link : Load Balanced Servers … Hopefully helpful.
…would it make a difference if the downtime is planned or unplanned.
That would depend on the purpose of the measurement.
If you simply need to measure how much time the system was available for handling business processing, it doesn’t matter much what the reason was for downtime. You aren’t actually measuring downtime in that case; you’re actually measuring uptime.
If you are attempting to quantify how much downtime is used for administrative (planned) work and how much is used for unplanned work, then of course the difference is important.
A higher amount of unplanned downtime might indicate there are reliability problems with hardware, software or people. A higher amount of planned downtime (that is troublesome) might indicate that processes need to be changed.
It depends on why you are gathering measurements in the first place.
Tom
TomLiotta, Thanks for your response. If you have the time look at my new question about the relationship of uptime to downtime. Jim4522
Unplanned downtime means that server has some issues. Planned downtime usually belongs to hardware upgrade/ backup/ server maintenance/etc … but one thing is clear downtime is downtime, however, if this your main concern, then you can opt load balancing servers or server mirroring solution, where one server play the role of master server and second one act like a slave server. So in case master server goes down due to any reason slave server takes it place without any downtime. For more information you can check this link : Load Balanced Servers … Hopefully helpful.