Beruflich Dokumente
Kultur Dokumente
A run book should contain all of the information you and your staff need to perform day-to-day
operations and to respond to emergency situations. This information should include the following:
Resource information about the data center and its hardware and software
The run book should contain all necessary information to enable a staff member to perform any
process, from performing a backup to failing over to a remote site.
On This Page
Resource Information
Procedural Information
Resource Information
The run book should contain the following types of detailed resource information to help your staff
perform routine operational tasks and respond quickly and efficiently to data center emergencies:
Contact information — Detailed information about each database administrator (DBA), the
building facilities staff, utility companies, and all hardware and software vendors
Keeping this critical resource information current and readily available to your staff reduces
downtime when disaster strikes.
Contact Information
Record detailed information regarding each individual or company that you or your staff may need
to contact in an emergency. This detailed contact information should include the following:
Contact information for each DBA at the primary site, including his or her role in the
operational and disaster recovery process
Contact information for the building facilities staff, the power company, the phone company,
and other applicable utilities companies
Contact information for your remote site, if you have one, and for all DBAs at that site
Hardware, software, and service vendor support phone numbers, e-mail addresses, account
numbers, and login and password information for related Web sites
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 2 of 7
Contact information for other server applications on the server, including developers,
analysts, testers, and managers affected by a change to the application, related systems, or
processes
In addition, record any additional contact information that might be useful in troubleshooting and
repairing the data center, such as useful e-mail discussion lists and Web sites.
Hardware Components
Record detailed information regarding each hardware component in the data center, including the
following:
Server hardware
SCSI host adapter or fiber channel cards, including their vendors and model numbers
RAID levels
Type, size, and number of drives, including cache if any, and controller to which the
disk is connected
RAID level
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 3 of 7
In addition, record all additional information about the data center hardware that might be useful in
troubleshooting and repairing the data center. For example, record a map of the physical wiring of
specific drives to specific array controllers.
Software Components
Record detailed information about each software component in the data center:
All software
The network share location for all software installed on the server, including all service
packs, hardware drivers, and hot fixes
The onsite and offsite location of all software CDs, including license keys and serial
numbers
Windows 2000
Operating system version, with service pack level and hot fixes
MSCS
Cluster configuration, including all cluster IP addresses, cluster name, cluster nodes,
and cluster resource groups
Installation information, including service pack levels, hot fixes, instance names, server
collation, ports, pipes, configuration options, virtual IP name and address, database file
locations, file groups, service logins and passwords, e-mail account, and enabled
network protocols
Information about file shares used by the SQL Server and SQL Server Agent service
accounts and the associated permissions on those shares
Server roles, database schemas, user accounts, permissions, database roles, custom
error messages, and the location of scripts to recreate these objects
List of all automated SQL Server Agent jobs (specifically including all backup jobs),
what they do, who is notified, their corresponding code for each job step, the time or
times they run, and the location of scripts to recreate the jobs
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 4 of 7
List of all alerts, what they do, the associated error number or performance condition,
who is notified, and the location of scripts to recreate the alerts
List and location of all DTS Packages, including associated login and password
information
List, location, and purpose of all custom code that runs on the server, and the location
of a backup copy of this code
Names and locations of client tools installed to connect to remote database connections
(for example, to heterogeneous data sources), and necessary configuration and
connection information
Analysis Services
In addition, record all additional information about the software that might be useful in
troubleshooting and repairing the data center. For example, record the staff members who are most
familiar with custom applications.
Top Of Page
Procedural Information
Develop and document procedures for each operational and emergency task that you and your staff
perform. Whenever possible, develop Transact-SQL scripts for each of these tasks and automate
the execution of these scripts by using SQL Server jobs or DTS packages. The procedural
information should include the detailed steps and scripts for performing the following tasks utilizing
both SQL Server Enterprise Manager and Transact-SQL scripts:
Operational Tasks
The DBA staff performs many routine operational tasks. To avoid problems, your staff should
perform these tasks by using the same procedures each time. Record step-by-step procedures for
performing each of the following types of routine operational tasks:
Security tasks
Changing the domain user account and password used by SQL Server and SQL Server
Agent
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 5 of 7
Monitoring tasks
Archiving SQL Server error logs and SQL Server Agent logs
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 6 of 7
Troubleshooting tasks
Troubleshooting deadlocks
Troubleshooting replication
In addition to the foregoing, add step-by-step instructions for other tasks that you and your staff
perform regularly.
Emergency Tasks
Record the appropriate response to each type of emergency that may affect the data center.
Although the precise tasks vary depending upon the high availability solutions implemented, have a
planned and tested response to each of the following types of emergencies:
Natural disasters
Power outages
Server failures
Application failures
Network failures
Depending upon the high availability solutions implemented for the data center, the detailed steps
will include MSCS failover and failback steps, log-shipping role change steps, transactional
replication role change steps, and database restoration steps. These procedures should document
the process of determining when to initiate a failover or a role change and how affected users are
notified. These procedures must include steps to verify the system's state before bringing a
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011
Contents of a Run Book Page 7 of 7
restored system or database online. They should also include escalation steps in case the first
attempt to restore availability fails.
Top Of Page
http://technet.microsoft.com/en-us/library/cc917702(printer).aspx 3/31/2011