Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Uptime and availability stats

Answered Uptime and availability stats

  • Friday, November 30, 2012 1:20 PM
     
     
    Sign In to Vote
    0

    A few questions on availability and stats;

    1. If you manage file servers for clients, do you have to provide them with availability/uptime statistics of your servers to the client? If so how do you derive these statistics? And how often do you provide the statistics.
    2. If you have a server go down or become unavailable for a significant period of time, do you have to report as to why that was, what went wrong, and how you will ensure it wont happen again. Or not really.
    3. Can you give me a few examples of common reasons servers “go down” or their availability/performance becomes compromised. Specific to lets say file servers. These are ESXi hosts running server 2008. The more examples of what goes wrong the better.
     

All Replies

  • Friday, November 30, 2012 2:15 PM
    Moderator
     
     Answered
    Sign In to Vote
    0

    It's really difficult to answer your questions ! But still I would try to give my personal views...

    1. & 2. It depends on the agreement between your company and clients whether or not to share availability reports of servers. Here is a catch, you might be able to to provide File server up time statistics ( might want use Monitoring applications to know the Server uptime statistics ) However, suppose your File Shares become unavailable for any reason, it's really hard to maintain or provide the reasons.

    If Server goes down due to hardware failures or due to network outage, you might want to report an incident to your client.

    File Shares on file server might not be available for some time due to manual mistakes, in that case would you like to share the actual reason with your client and put your company's business on stake ?

    how you will ensure it wont happen again. Or not really. -> Learn from the mistakes, analyse the root cause and do not repeat.

    3. Reasons could be in-numerous... few which I can think of are

    Manual errors, Hardware Failure, Network outage, virus breakout etc...

    Regards, Santosh

    I do not represent the organisation I work for, all the opinions expressed here are my own.

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Whenever you see a helpful reply, click on Alternate TextVote As Helpful & click on Alternate TextMark As Answer if a post answers your question.