HA Solutions for Windows SQL and Exchange Servers.pdf

(1057 KB) Pobierz
Aelita.Exchange.01_
IT Pro SERIES
Solutions
for Windows, SQL and Exchange Servers
by Sameer Dandage
Daragh Morrissey
Jeremy Moskowitz
Paul Robichaux
Mel Shum
Ben Smith
Bill Stewart
HA
104590060.027.png 104590060.028.png 104590060.029.png 104590060.030.png 104590060.001.png 104590060.002.png 104590060.003.png 104590060.004.png 104590060.005.png 104590060.006.png 104590060.007.png 104590060.008.png 104590060.009.png 104590060.010.png 104590060.011.png 104590060.012.png 104590060.013.png 104590060.014.png 104590060.015.png 104590060.016.png 104590060.017.png 104590060.018.png 104590060.019.png
i
Contents
Ben Smith
A 6-Step Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Step 1: Identify Critical Business Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Step 2: Map IT Systems to Critical Business Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Step 4: Develop Plans and Procedures for Preserving Business Continuity . . . . . . . . . . . . 2
Step 5: Develop Plans and Procedures for Recovering from Disaster . . . . . . . . . . . . . . . . 3
Jeremy Moskowitz
A Little History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bill Stewart
Sameer Dandage
Distributor Database Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
104590060.020.png 104590060.021.png 104590060.022.png 104590060.023.png
ii HA Solutions for Windows, SQL, and Exchange Servers
Mel Shum
SAN Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
I’m Ready for a SAN. Now What? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Running SQL Server on Raid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Michelle A. Poolet
High Availability in Analysis Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Carl Rabeler
Michael Otey
Michael Otey
Kalen Delaney
Brian Moran
Paul Robichaux
Daragh Morrissey
Exchange Virtual Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Exchange Cluster Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Before You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
104590060.024.png
1
Chapter 1:
Surviving the Worst
Ben Smith
It’s 2:00 A.M. on a Monday morning, and your cell phone rings. The water fountain on the floor
directly over your server room has malfunctioned, and your organization’s servers and routers are
standing in water, as are most of your employees’ workstations. The office opens at 8:00 A.M. What
do you do in the meantime?
Situations like this one separate IT departments that have planned for disaster from those that
haven’t. For the latter group, the situation I’ve described is more than a disaster—it’s an absolute
disaster. When total data loss is possible, the absence of a disaster recovery program can put a
business at risk, particularly small-to-midsized businesses (SMBs), which often don’t have the financial
wherewithal to survive unexpected catastrophic events. Although disasters are inevitable and, to a
degree, unavoidable, being prepared for them is completely within your control. Increasingly, IT has
become the focal point of many companies’ disaster planning. Creating a program to preserve
business continuity and recover from disaster is one of the central value propositions that an IT
department can contribute to an organization.
A 6-Step Plan
In the terminology of disaster planning, two phrases are common: Business Continuity Planning (BCP)
and Disaster Recovery Planning (DRP). Although many people use these phrases interchangeably,
they represent different concepts. BCP traditionally defines planning that ensures an organization can
continue operating when faced with adverse events. DRP is actually a subset of BCP and traditionally
focuses on recovering information and systems in the event of a disaster. As an example, the failure
of a hard disk in a database server is an event that potentially affects business continuity but doesn’t
result from a disaster. However, a water-pipe break that floods a server room and submerges the
database server is a threat to business continuity and within the scope of disaster recovery planning.
BCP and DRP can be complex; in fact, large organizations dedicate groups of people to them.
But without getting into detailed risk analyses and other complexities that usually accompany BCP
and DRP in large companies, all organizations can benefit by following six steps to create a program
that will preserve business continuity and facilitate recovery in the event of disaster.
Step 1: Identify Critical Business Activities
The first step in BCP and DRP is to identify your organization’s critical business activities—those
things that must occur on a daily basis in order for your business to stay in business. For example, a
customer service call center must be able to receive calls, look up customer records, and create new
incident records for customers calling in. A law firm will need to be able to access client information
and electronic schedules, send and receive email, research online law libraries, and make and receive
telephone calls. As you work through this step, you’ll need to partner with your organization’s key
Brought to you by Neverfail and Windows IT Pro eBooks
104590060.025.png
2 HA Solutions for Windows, SQL, and Exchange Servers
business decision makers to identify the activities that are essential to your organization’s continued
functioning. Your organization’s BCP will center on preserving continuity of operations by recovering
these services.
Step 2: Map IT Systems to Critical Business Activities
With the identification of your organization’s key business activities, you can determine which IT
systems these activities depend on. For example, to enable the customer service call center to look
up customer records and create new records for incoming calls, the database servers that store the
records and the line-of-business applications that access them must be available. In turn, some degree
of core network infrastructure will also need to be operable for this critical business activity to take
place. These are the IT systems that you must be able to keep operating by quickly recovering them
after a disaster.
Step 3: Model Threats Posed by Predictable and Plausible Events
Nearly all disasters and failures in business continuity are predictable to a certain degree of precision
and plausible within a certain degree of reason. Such events can be natural, such as an earthquake or
flooding; human-caused, such as an accidental fire or deliberate sabotage; or mechanical, such as a
hard disk failure or a water pipe bursting. For example, if a customer service call center is located in
Wakita, Oklahoma, it is plausible that the center’s IT systems could be in the direct path of a tornado.
Likewise, for any company that relies on technology, it is predictable that computer hardware will
eventually fail.
After you identify your critical IT systems, you can begin modeling the threats posed to these
systems by predictable and plausible events. Threat modeling lets you apply a structured approach to
identifying threats with the greatest potential impact to your business continuity and their mitigation.
List all the ways that critical IT systems might be disrupted and which events must happen for each
threat to be realized. For example, something that would disrupt the call center’s business continuity
might be the customer record database’s inaccessibility. Events that could cause such inaccessibility
include computer hardware failure, a power failure, or something more severe, such as destruction of
the data center by a tornado.
Step 4: Develop Plans and Procedures for
Preserving Business Continuity
Now that you’ve listed your critical business activities, identified the IT systems your business
depends on for carrying out those activities, and brainstormed the possible and plausible events that
could disrupt IT services, you can use your threat model to determine countermeasures to preserve
business continuity. Four primary BCP countermeasures exist: fault tolerance and failover, backup,
cold spares and sites, and hot spares and sites.
Fault tolerance and failover. This countermeasure relies on the use of redundant hardware to
enable a system to operate when individual components fail. In IT, the most common fault tolerance
and failover solutions for preserving IT operations are hard disk arrays, clustering technologies, and
battery or generator power supplies.
Brought to you by Neverfail and Windows IT Pro eBooks
104590060.026.png

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika:

Zgłoś jeśli naruszono regulamin