guide to Windows disaster recovery and backup.pdf

(708 KB) Pobierz
Aelita.Exchange.01_
IT Pro SERIES
Windows
Disaster
Disaster
Recovery
and
Backup
by Bob Chronister, Jerry Cochran, Kalen Delaney, Paul Robichaux,
Ed Roth, John Savill, Bill Stewart, and Alan Sugano
Sponsored by
A Guide to
A Guide to
Windows
Recovery
Backup
104590057.006.png 104590057.007.png
i
Contents
By Alan Sugano
1. Review Your Backup Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
2. Make Lots of Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
5. Assign a Disaster Recovery Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Create a Disaster Recovery Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9. Develop a Hacking Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
By Ed Roth
Configuring Backup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Scheduling Backup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
By Jerry Cochran
Better Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Improving the Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
104590057.008.png 104590057.009.png 104590057.001.png 104590057.002.png
ii A Guide to Windows Certification and Public Keys
By Kalen Delaney
Strategies for Disaster Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Setting Up a Disaster-Recovery Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
—Bob Chronister
Setting NTBackup to Not Use VSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
—Bob Chronister
—John Savill
—Bill Stewart
—Paul Robichaux
—Paul Robichaux
—Bob Chronister
—John Savill
Speed Up an Authoritative Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
—Brian Taché
—Bob Chronister
—John Savill
—John Savill
—Kalen Delaney
104590057.003.png
1
Chapter 1:
10 Steps to Building a Sound Disaster
—By Alan Sugano
You need only take a quick look at the news on any given day to remind you of why your company
needs a disaster recovery plan. Chances are, you won’t ever experience a Level Four disaster, such as
a terrorist bombing or natural disaster like a hurricane or flood. But even the smaller-scale Level One,
Two, or Three disasters that you’ll more likely encounter, such as power outages and server malfunc-
tions, can paralyze business operations unless you’ve developed a plan for rapidly restoring IT ser-
vices. Table 1 lists and describes the four disaster levels. You probably already have a disaster
recovery plan, but it’s wise to review it periodically and update it to accommodate changes in your
business. Drawing on my experience in developing disaster recovery plans for clients, I’ve compiled a
list of the 10 steps an organization of any size should follow when creating a new disaster recovery
plan or revising an existing plan.
Table 1: Disaster Levels
Level
Downtime
Typical Causes
Business Location Number of
Business Impact
Available?
People Affected
One
4 hours or less
Single workstation failure Yes
Three or fewer Low
Two
24 hours or less
Server failure,
Yes
Four or more
Low
WAN disruption
Three
72 hours or less
Water leak,
No
10 or more
Moderate
extended power failure
Four
More than 72 hours Earthquake, flood,
No
10 or more
High
terrorist attack, war
1. Review Your Backup Strategy
I generally recommend that clients perform full daily backups of all essential servers and data
resources. Stay away from incremental and differential backups. In an emergency, you don’t want to
have to search for not only the last good full backup but also the five incremental backups necessary
to complete the restore.
If you’re running Microsoft Exchange Server or Microsoft SQL Server, consider making hourly
backups of transaction logs so that you’ll be able to restore your system to within 1 hour of when it
crashed. One-step restore backup solutions are useful, but make sure you know how to manually
recover the server should you have to restore your data on a different server platform. Store at least
one tape off site weekly and store on-site tapes in a data-approved fireproof safe. Always ensure that
Brought to you by Symantec and Windows IT Pro eBooks
Recovery Plan
104590057.004.png
2 A Guide to Windows Disaster Recovery and Backup
you have on hand a new tape drive that can read your existing tapes. You don’t want to discover
that you no longer have a tape drive that can read your outdated tape format. Consider leveraging
built-in features of Windows Server 2003 and Windows 2000 Server—such as Microsoft Remote
Installation Services (RIS), offline folders, Microsoft Volume Shadow Copy Service (VSS), and
Windows Server Update Services (WSUS)—to aid in the recovery process and help get your network
up and running again.
2. Make Lots of Lists
Your disaster recovery plan can’t have too much documentation. To recover gracefully from a
disaster, you need to adequately document equipment, network layouts, applications, and technical
and business procedures that you’ll need to reconstruct your business. Here are some items you
should document and make available and accessible to those who need this information (employees,
consultants, service providers):
Business locations. Document the business address, phone number, fax number, and building
management contact information. I suggest including a map to the business’s location(s) that includes
surrounding geographic areas.
Equipment list. Compile an inventory listing of all the network components at each business
location. Include the model, manufacturer, description, serial number, and cost for each network
component. Many software products are available that can help you create and maintain such an
inventory. Often this type of list is necessary for insurance purposes, so it might already exist at your
company (e.g., in the financial department). Should a disaster affect your company, this list will be
useful for determining what IT will need to order to replace damaged equipment.
Application list. Make a list of business-critical applications running at each location. If neces-
sary, include in this list specific recovery instructions for ERP applications. For major applications,
include technical support contact information, account numbers, and—for applications that have a
maintenance agreement—service contract information.
Essential vendor list. Compile a list of essential vendors—that is, those necessary for your
business operations. Consider establishing lines of credit with these vendors in case bank funds aren’t
readily available after a disaster occurs.
Critical customer list. Compile a list of customers for whom your company provides business-
critical services. Designate someone in your company to notify these customers of your business
status after a disaster has occurred and provide estimates of when your firm will become fully
operational.
3. Diagram Your Network
Use a software package such as Microsoft Office Visio 2003 to draw detailed diagrams for all
networks in your organization, including both LANs and WANs.
LAN diagram. Construct a detailed diagram of the network layout for each business location,
such as the sample diagram that Figure 1 shows. Make sure the diagram corresponds to the physical
layout of the office (as opposed to a logical diagram of the network) to make it easier for someone
who’s unfamiliar with the office layout to find items. This diagram should show all network compo-
nents and briefly describe each component and the OS version.
Brought to you by Symantec and Windows IT Pro eBooks
104590057.005.png

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika:

Zgłoś jeśli naruszono regulamin