稼働時間の調査ツール
Uptime.exe Tool Allows You to Estimate Server Availability with Windows NT 4.0 SP4 or Higher
http://support.microsoft.com/kb/232243/en-us
uptime.exe
http://uptimeexe.codeplex.com/
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 |
C:\>uptime.exe /help UPTIME, Version 1.01 (C) Copyright 1999, Microsoft Corporation Uptime [server] [/s ] [/a] [/d:mm/dd/yyyy | /p:n] [/heartbeat] [/? | /help] server Name or IP address of remote server to process. /s Display key system events and statistics. /a Display application failure events (assumes /s). /d: Only calculate for events after mm/dd/yyyy. /p: Only calculate for events in the previous n days. /heartbeat Turn on/off the system's heartbeat /? Basic usage. /help Additional usage information. Description: UPTIME is a utility that processes the machine's event log to determine system availability and current uptime. The target system can either be the local system or a remote system. No special privileges are required for basic operation although it is most accurate to run the tool under an administrative account. Many factors affect these calculations, and the results displayed by this tool should be considered estimates. Requirements: Availability calculations require: Windows NT 4.0 Service Pack 4 or higher, including Windows 2000. Additionally the system "heartbeat" must be active. The system "heartbeat" is a date/time stamp that is written to the system registry at a fixed interval. This heartbeat is available in Service Pack 4 or higher. It is enabled by default on Windows NT Server. Since the heartbeat causes the registry to be written to the disk at regular intervals, it can interfere with systems running various forms of power management. It is not recommended to enable the heartbeat of laptop systems. To enable the heartbeat use: UPTIME /heartbeat [\\Machine] If the heartbeat is disabled, or if you are not running Service Pack 4 or greater, UPTIME may report that the event logs do not contain sufficient information to calculate system availability. This is because UPTIME detects an abnormal shutdown (for instance a bluescreen or power failure) but cannot determine how long the system was down during this abnormal outage. It is best to run uptime as an administrator, since much more information is available to calculate system uptime and availability. For instance the time zone of the system is important to many of the calculations, but this information can only be reliably obtained by an administrator. Additionally, when calculating the Current System Uptime, this tool attempts to use the System Performance Counter for Uptime. However, if the user is not an administrator, this counter may be unavailable. In this case an estimate is made based on the last recorded boot noted in the event log. Application Failures: Application Failure event detection is dependent upon Dr Watson being enabled. Bluescreens: Bluescreen detection is dependent upon the system being configured to write an event to the event log if the system stops unexpectedly. To enable bluescreen event logging for Windows NT 4.0: Go to the Control Panel and double click the System Icon. Next select the startup/shutdown tab. Finally check the "Write an event to the system log." check box. To enable bluescreen event logging for Windows 2000 Systems do the following: Go to the Control Panel and double click the System Icon. Next select the "Advanced" tab. From the "Advanced" property sheet select the "Startup and Recovery" button. Finally check the "Write an event to the system log." check box. Potential sources of error: All calculations are based on the entries in the event log. If the system time is altered significantly, this can have a dramatic affect on the calculations made. Additionally if the event logs have been cleared, or have filled, such that additional events cannot be written, this will also affect this tools ability to accurately estimate system availability. The heartbeat is generally written every 5 minutes, so the amount of downtime calculated for abnormal outages is limited in accuracy to this window. Systems that are a member of a cluster are currently unsupported by UPTIME. If UPTIME detects that the target system may be a member of a cluster, UPTIME will display a message stating that the results may be in error. Where to go for more help: For further information about this tool please see: http://support.Microsoft.com/support and reference KB Article: Q232243 |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 |
C:\work><strong>uptime.exe /s</strong> Uptime Report for: \\WIN2003SV Current OS: Microsoft Windows Server 2003 R2, Service Pack 2, Uniprocessor Free. Time Zone: System Events as of 2012/10/26 13:54:23: Date: Time: Event: Comment: ---------- ----------- ------------------- ----------------------------------- 2011/02/10 3:06:00 Shutdown 2011/02/10 3:07:28 Boot Prior downtime:0d 0h:1m:28s 2011/03/17 18:53:09 Abnormal Shutdown Prior uptime:35d 15h:45m:41s 2011/03/20 14:47:36 Boot Prior downtime:2d 19h:54m:27s 2011/03/22 18:29:33 Abnormal Shutdown Prior uptime:2d 3h:41m:57s 2011/03/22 20:33:30 Boot Prior downtime:0d 2h:3m:57s 2011/03/23 15:29:44 Abnormal Shutdown Prior uptime:0d 18h:56m:14s 2011/03/23 18:42:04 Boot Prior downtime:0d 3h:12m:20s 2011/04/21 3:08:58 Shutdown Prior uptime:28d 8h:26m:54s 2011/04/21 3:10:21 Boot Prior downtime:0d 0h:1m:23s 2011/09/24 9:52:47 Abnormal Shutdown Prior uptime:156d 6h:42m:26s 2011/09/24 10:35:14 Boot Prior downtime:0d 0h:42m:27s 2011/09/24 11:05:39 Shutdown Prior uptime:0d 0h:30m:25s 2011/09/24 11:06:25 Boot Prior downtime:0d 0h:0m:46s 2011/09/29 3:11:42 Shutdown Prior uptime:4d 16h:5m:17s 2011/09/29 3:12:57 Boot Prior downtime:0d 0h:1m:15s 2011/10/13 3:07:59 Shutdown Prior uptime:13d 23h:55m:2s 2011/10/13 3:09:17 Boot Prior downtime:0d 0h:1m:18s 2011/11/10 3:03:48 Shutdown Prior uptime:27d 23h:54m:31s 2011/11/10 3:05:07 Boot Prior downtime:0d 0h:1m:19s 2011/11/24 3:02:59 Shutdown Prior uptime:13d 23h:57m:52s 2011/11/24 3:04:16 Boot Prior downtime:0d 0h:1m:17s 2011/12/15 3:05:14 Shutdown Prior uptime:21d 0h:0m:58s 2011/12/15 3:06:33 Boot Prior downtime:0d 0h:1m:19s 2012/01/12 3:07:32 Shutdown Prior uptime:28d 0h:0m:59s 2012/01/12 3:08:52 Boot Prior downtime:0d 0h:1m:20s 2012/02/02 3:03:04 Shutdown Prior uptime:20d 23h:54m:12s 2012/02/02 3:04:20 Boot Prior downtime:0d 0h:1m:16s 2012/02/16 3:06:09 Shutdown Prior uptime:14d 0h:1m:49s 2012/02/16 3:07:28 Boot Prior downtime:0d 0h:1m:19s 2012/03/15 3:04:31 Shutdown Prior uptime:27d 23h:57m:3s 2012/03/15 3:05:52 Boot Prior downtime:0d 0h:1m:21s 2012/04/09 17:01:11 Shutdown Prior uptime:25d 13h:55m:19s 2012/04/09 17:20:28 Boot Prior downtime:0d 0h:19m:17s 2012/04/09 17:32:29 Abnormal Shutdown Prior uptime:0d 0h:12m:1s 2012/04/09 17:53:52 Boot Prior downtime:0d 0h:21m:23s 2012/04/09 18:03:51 Shutdown Prior uptime:0d 0h:9m:59s 2012/04/09 18:04:35 Boot Prior downtime:0d 0h:0m:44s 2012/04/12 3:06:49 Shutdown Prior uptime:2d 9h:2m:14s 2012/04/12 3:08:07 Boot Prior downtime:0d 0h:1m:18s 2012/04/21 9:19:25 Shutdown Prior uptime:9d 6h:11m:18s 2012/04/21 12:10:19 Boot Prior downtime:0d 2h:50m:54s 2012/04/21 12:25:49 Shutdown Prior uptime:0d 0h:15m:30s 2012/04/21 12:26:50 Boot Prior downtime:0d 0h:1m:1s 2012/04/26 3:15:35 Shutdown Prior uptime:4d 14h:48m:45s 2012/04/26 3:16:34 Boot Prior downtime:0d 0h:0m:59s 2012/05/01 19:28:56 Abnormal Shutdown Prior uptime:5d 16h:12m:22s 2012/05/01 19:45:31 Boot Prior downtime:0d 0h:16m:35s 2012/05/01 20:39:36 Shutdown Prior uptime:0d 0h:54m:5s 2012/05/01 21:10:30 Boot Prior downtime:0d 0h:30m:54s 2012/05/17 3:10:04 Shutdown Prior uptime:15d 5h:59m:34s 2012/05/17 3:11:31 Boot Prior downtime:0d 0h:1m:27s 2012/06/07 3:15:54 Shutdown Prior uptime:21d 0h:4m:23s 2012/06/07 3:17:21 Boot Prior downtime:0d 0h:1m:27s 2012/06/11 15:59:53 Shutdown Prior uptime:4d 12h:42m:32s 2012/06/11 16:03:42 Boot Prior downtime:0d 0h:3m:49s 2012/06/14 3:23:00 Shutdown Prior uptime:2d 11h:19m:18s 2012/06/14 3:24:02 Boot Prior downtime:0d 0h:1m:2s 2012/06/17 10:16:17 Abnormal Shutdown Prior uptime:3d 6h:52m:15s 2012/06/17 10:50:30 Boot Prior downtime:0d 0h:34m:13s 2012/07/12 3:04:57 Shutdown Prior uptime:24d 16h:14m:27s 2012/07/12 3:06:34 Boot Prior downtime:0d 0h:1m:37s 2012/08/16 3:04:31 Shutdown Prior uptime:34d 23h:57m:57s 2012/08/16 3:06:17 Boot Prior downtime:0d 0h:1m:46s 2012/08/16 14:52:43 Shutdown Prior uptime:0d 11h:46m:26s 2012/08/16 16:02:55 Boot Prior downtime:0d 1h:10m:12s 2012/09/15 10:47:00 Abnormal Shutdown Prior uptime:29d 18h:44m:5s 2012/09/15 11:31:53 Boot Prior downtime:0d 0h:44m:53s 2012/09/15 19:42:29 Shutdown Prior uptime:0d 8h:10m:36s 2012/09/15 20:18:35 Boot Prior downtime:0d 0h:36m:6s 2012/09/17 10:40:15 Shutdown Prior uptime:1d 14h:21m:40s 2012/09/17 10:52:44 Boot Prior downtime:0d 0h:12m:29s 2012/09/17 11:55:46 Abnormal Shutdown Prior uptime:0d 1h:3m:2s 2012/09/17 12:06:49 Boot Prior downtime:0d 0h:11m:3s 2012/09/17 12:16:07 Shutdown Prior uptime:0d 0h:9m:18s 2012/09/17 12:18:30 Boot Prior downtime:0d 0h:2m:23s 2012/09/19 20:57:22 Shutdown Prior uptime:2d 8h:38m:52s 2012/09/19 21:00:23 Boot Prior downtime:0d 0h:3m:1s 2012/09/27 3:03:13 Shutdown Prior uptime:7d 6h:2m:50s 2012/09/27 3:04:35 Boot Prior downtime:0d 0h:1m:22s 2012/10/11 3:18:33 Shutdown Prior uptime:14d 0h:13m:58s 2012/10/11 3:19:29 Boot Prior downtime:0d 0h:0m:56s Current System Uptime: 15 day(s), 10 hour(s), 35 minute(s), 27 second(s) -------------------------------------------------------------------------------- Since 2011/02/10: System Availability: 99.4507% Total Uptime: 621d 0h:29m:0s Total Downtime: 3d 10h:19m:23s Total Reboots: 41 Mean Time Between Reboots: 15.23 days Total Bluescreens: 0 |