I believe you are really talking about an SLA. An SLA is a business specific interpretation of availbility.
On Mon, Apr 28, 2008 at 1:13 AM, Osama Salah <[EMAIL PROTECTED]> wrote: > Hi, > > I was wondering if there is a best practice for a systems availability > metric? > > For example, if I just measure how long Exchange was available per month > that might not be a good indicator. If it was down during office hours it > would have a higher impact than if it was done at the weekend. > If it's working great all over the year but fails for several days in one > of the months, that might be worse than it failing a couple of times per > year for a few minutes. etc. > Then there are the planned downtimes for maintenance etc., should those be > excluded and then we list a reliability figure instead of availability? > I'm trying to look if there are any best practices. > If you have any hints please let me know. > > regards > OS > > ------------------------------ > *Disclaimer:*This communication contains information that is confidential > and may also be legally privileged. It is for the exclusive use of the > intended recipient(s). If you are not the intended recipient,disclosure, > copying, distribution or other use of, or taking of any action in reliance > upon, this communication or the information in it is prohibited and may be > unlawful. If you have received this communication in error please notify the > sender by return email, delete it from your system and destroy any copies. > ------------------------------ > > > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
