Introduction to NonStop Operations Management

Operations Documentation
Introduction to NonStop Operations Management–125507
4-14
Outage Logs
The log book should remain by the system console or system cabinets.
Outage Logs
Tandem recommends maintaining outage logs to help you assess system availability.
Outage logs provide a history of any failure or upgrade that causes a system outage. This
historical data can be used for trend analysis, which in turn can be used to determine
where improvements are needed. Improvements could include operator training, change
management, operational tools and utilities, or additional system software or hardware.
Outage logs should be maintained by lead operators. An outage log should be tailored to
meet the specific needs of your particular environment. Even though you will customize
your outage log, you still need to be aware that it should also contain the following types
of crucial information:
•
The date and time that the outage occurred
•
The duration of the outage
•
The suspected cause of the outage and the objects involved (for example, disk
failure, database needs rollforward, and so on)
•
The actions taken to recover from the outage, including:
•
The name of the persons initiating recovery
•
The date and time when the persons initiating recovery were notified of the
outage
•
The type of procedure followed to perform the recovery
•
The applications, number of users, and business services affected by the outage
•
Any follow-up actions that were taken when the recovery was completed
Figure 4-5 shows a sample outage log form.