[Home] [Catalog] [Category] [Previous Item] [Next Item] [Checkout] [Review Cart] [Button]

The Disaster Center Bookstore

Disaster Center Bookstore-a service of Rothstein Associates

Software, CD/Diskette Products

GO.RECOVER DATA CENTER [Item Image]
Qty:
Data Center Disaster Recovery Plan on
CD-ROM, by Persson Associates. 2008, 6th
Edition.
CD662
$99.95
GO.RECOVER-DATA CENTER:
DATA CENTER DISASTER RECOVERY PLAN ON CD-ROM
by PERSSON ASSOCIATES
2008 - 6th Edition
ISBN #1-931332-48-7 (978-1-931332-48-4)
- - - - - - - - -
Published by Rothstein Associates Inc.
In stock for immediate shipment!
- - - - - - - - -

GO.RECOVER-DATA CENTER is a complete, easy-to-use and understand Data
Center Disaster Recovery Plan Development Methodology and Template for the
Information Technology Infrastructure. Each chapter addresses a plan development
topic and provides the necessary instructions, worksheets (for data collection),
plus additional hints and suggestions.

- - - - - - - - -

“I like your document. It is very straight forward and clear without all the fluff of
some of the other offerings I have seen. We will be able to use this right out of the
box.”
- Terry Thornton, Principal
RT Global LLC

- - - - - - - - -

- 10 comprehensive, plan development chapters
- 40 formatted, pre-defined data collection Worksheets
- A total of 114 pages
- Microsoft Word format.

- - - - - - - - -

BENEFITS

- Easy to use
- Easy to read
- Easy to understand
- No special software is needed. Only a PC and MS Word (or other word
processor) software are needed
- Presents plan development in a logical progression following 10 specific
chapters
- Makes data collection easy by including worksheets that are ready to fill
in
- In all, 40 specific data collection Worksheets make the job of building the
plan document faster and easier
- Extremely low-cost alternative to plan development.

- - - - - - - - -

COMMENTS ABOUT GO.RECOVER-DATA CENTER

“Extremely easy to use. We simply loaded the CD and started filling out the
worksheets. And, we were able to add our specific information as we went through
the process without a problem.”

“It was laid out in a logical sequence of tasks to complete. It was like a "By the
Numbers" approach.”

“One chapter at a time allowed us to focus on specific tasks and to see progress
sooner.”

“The low price attracted us to the product and we got more than we really
expected. Great value!”

- - - - - - - - -

GO.RECOVER-DATA CENTER is targeted for use in developing a disaster
recovery plan for small, medium, and medium/large Data Centers. It addresses all
of the components (i.e. Infrastructure) that need to be in place for a recovery to
take place at an alternate location. Most recovery efforts (initial disaster recovery
plans) must start with this plan. Without the infrastructure in place, it is difficult to
implement a recovery effort that would be able to provide service to the end users
of the data center technology.

- - - - - - - - -

INFORMATION TECHNOLOGY INFRASTRUCTURE

Most data centers contain numerous technology components. For example,
CPUs, Disk, Tape, Communications (LAN, WAN, Voice), data networks (lines,
hubs, routers, etc), Database software, Servers, PC's, Operational software
packages, Application Packages, Internet services (eCommerce), etc. All of the
technology components that are needed in order to implement an operational
computer service can be thought of as the “I/T Infrastructure.”

- - - - - - - - -

CONTENTS

1. Identify Recovery Leadership Teams
- Template 1.1 = Recovery Leadership Team
- Template 1.2 = Detailed Recovery Teams

2. Document Emergency & Notification Steps
- Template 2.1 = Immediate Emergency Tasks
- Template 2.2 = Local Emergency Services
- Template 2.3 = Company Personnel Call List
- Template 2.4 = Vendor Call List
- Template 2.5 = Escalation Procedure
- Template 2.6 = Damage Assessment Summary

3. Identify Plan Scope and Assumptions
- Template 3.1 = Plan Scope
- Template 3.2 = Plan Assumptions

4. Inventory Computer Equipment and Software
- Template 4.1 = Computer Equipment
- Template 4.2 = Operating System Software
- Template 4.3 = Application Software
- Template 4.4 = BIA - Business Impact Analysis
- Template 4.5 = List of "All" Applications
- Template 4.6 = Critical Application List

5. Inventory Network & LAN Equipment and Software
- Template 5.1 = Data Communications Equipment
- Template 5.2 = Voice Communications
- Template 5.3 = PBX Documentation
- Template 5.4 = Procedure to Redirect Communications Circuits
- Template 5.5 = Backup Network Schematic

6. Document Recovery Environment
- Template 6.1 = Recovery Equipment Requirements
- Template 6.2 = Production Network Schematic
- Template 6.3 = Recovery Network Schematic

7. Document Offsite Storage Requirements
- Template 7.1 = Vital Records
- Template 7.2 = Offsite Storage Audit Table for Data Backups
- Template 7.3 = Offsite Storage Facility Checklist

8. Document Alternate Site
- Template 8.1 = Current Facility
- Template 8.2 = Site Floor Plan
- Template 8.3 = Alternate Site Options
- Template 8.4 = Alternate Site Analysis - Vendor Evaluation
Checklist

9. Plan Testing and Plan Maintenance
- Template 9.1 = Activation Preparation Checklist
- Template 9.2 = Test Plan
- Template 9.3 = Draft Test Steps
- Template 9.4 = Test Results
- Template 9.5 = Maintenance Checklist

10. Implement Operation Restoration
- Template 10.1 = Basic Restoration Steps
- Template 10.2 = Alternate Site Operation Steps
- Template 10.3 = Return to Primary Site
- Template 10.4 = Reference Recovery Procedure List

11. A "Short Course" in Disaster Recovery Planning

12. Reference Recovery Procedures List


- - - - - - - - -

DETAILED PROJECT WORK PLAN

GO.RECOVER-DATA CENTER also includes a detailed project development Work
Plan. The steps to complete the plan are laid out in a logical, orderly manner.
Each step provides a brief description along with a reference to the required
worksheets. It makes the task of organizing the project simpler than ever.

- - - - - - - - -

Many people faced with the task of developing a disaster recovery plan have a
number of questions and frequently a number of fears about the project. "How do I
know if I'm covering all the right tasks?" "Where do I begin and is there an order to
the required project steps?" "Are there any analysis steps that could change the
results of the recovery effort?" "This is all new to me and I really don't know what
the end product should look like".

The good news is that Disaster Recovery Planning (DRP) is a very logical,
straightforward "Process". The steps, once presented, fall into a definite sequence
of events, analysis points, and development tasks. This product,
GO.RECOVER-Data Center, is a step-by-step guide to developing a DRP.

In terms of an overview, which is always helpful to start with, the process can be
outlined as follows:

- One of the first tasks is to simply identify the personnel that will be
included in the DRP process. These are usually the people responsible for the
computer Operations, Network, Applications, and a few more (Facilities, Security,
and often key vendors). A number of these people form the Recovery Team.

- Once the team is identified is it always a requirement to make sure the
basic precautions and emergency procedures are known and included in the DRP.
This would include emergency evacuation steps, notification procedures,
escalation procedures and a process to assess the damage. These constitute the
next set of tasks in defining the DRP. Safety of personnel is very important and a
good plan includes the necessary procedures.

- Following the personnel identification process and emergency steps
documentation, the next step is to set the project scope and establish the
assumptions. These are necessary to be sure the expectations about what the
DRP will cover are well documented and known. This is usually a fairly quick
process. Often, the initial scope is simply the computer center. Later, once this is
competed, the scope can be expanded.

- No DRP can be completed without a very thorough and complete inventory
of the installed computer hardware, software, and applications. This inventory step
serves to make sure the complete environment if known and documented. For
Insurance purposes it is mandatory in order to recoup any loss. From a recovery
standpoint, it is a basis on which to determine exactly what components are
required to backup the mission critical applications. It is in effect a straightforward
inventory step with some degree of analysis to determine which applications are
critical.

- The following next tasks move on to the somewhat more complex
"Network" inventories. The network components are often viewed as complex and
difficult to understand. In order to make the tasks easier; a set of specific
worksheets is included. They can be discussed with the people that have the
network experience (and/or with specific vendors) in order to document what
components are in place. This includes the LAN (Local Area Network) and WAN
(Wide Area Network) components.

- Based on the above steps, the next logical task is to identify what the
"Recovery Environment" will include. This actually is a list of all components
needed to support a recovery effort for the critical business applications.

- Moving along, the next task is to make sure that all of the necessary data
is backed up and stored offsite (often at an Offsite Storage Vendor). It is often said
that any recovery effort becomes impossible without the proper data and software
to restore to. What the task involves is simply to evaluate the current backup
process (daily, weekly, monthly, etc) and make sure copies (usually on tape or
cartridges) are sent off for safekeeping.

- Once the recovery environment is known (defined in the DRP) the next
step is to fit the proper alternate site strategy. This involves evaluating how closely
the alternate site strategy can provide recovery to meet the critical business
applications requirements. The traditional alternate site options include a Hot Site,
Cold Site, internal location, outsourcing, and more recently a mirrored location
(redundant facility and equipment, ready to process quickly). The matching
process simply evaluates the required recovery time (for example, 24 hours)
against the alternate site solution (Hot Site). Once that is done the costing and
funding process can be started.

- After the decisions are made, the alternate site is selected the actual
restoration tasks (Operations Restoration) can be developed. These are the
specify tasks which each team member is expected to carry out at the time a
recovery effort is required or during the testing of the DRP. These can be thought
of as a checklist of tasks.

- Finally, the process of developing a DRP must include a Maintenance
Process. This is absolutely required or the DRP will fall into obsolescence due to
lack of updates. If the DRP becomes out of date (a year old) the possible chance
that it will be effective at a recovery event is very small. The data and contents
simply change too fast.

This brief DRP development description should set the stage for a smooth plan
development process. In the end it is a very logical process, one containing a
specific set of steps that build on each one in sequence. Once again, welcome to
GO.RECOVER-Data Center.

- - - - - - - - -

EXCERPT FROM THE PLAN DEVELOPMENT PROJECT WORK PLAN

Task Worksheets to
Complete

Read through entire Methodology (takes 2 hours) None

Identify project team and recovery teams 1.1, 1.2

Review and customize emergency and notification steps 2.1, 2.2, 2.3,
2.4, 2.5, 2.6

Review, discuss and finalize plan scope and assumptions 3.1, 3.2

Circulate final scope and assumptions to team and project
sponsor for confirmation 3.1, 3.2

Inventory computer equipment and software and applications 4.1, 4.2, 4.3

...etc.

- - - - - - - - -

THE GO.RECOVER-DATA CENTER PLAN DEVELOPMENT
APPROACH:

Each Chapter is very structured in approach. An opening page in each chapter
spells out the following:
A. Objective
B. Purpose
C. Directions
D. Comments
E. Supporting Documentation

Each of these sections contains easy-to-follow text instructions and comments. In
addition, each data collection Worksheet is referenced and is included following
page one of each chapter. A sample follows.

- - - - - - - - -

A SAMPLE OF HOW EACH CHAPTER IS STRUCTURED:

Each chapter contains specific instructions on what must be done, what
worksheets to fill out, and what must be included. The following is a sample of how
each chapter is laid out. A sample of one of the data collection Worksheets is also
attached. In total, there are ten Chapters and forty Data Collection Worksheets.

SAMPLE - CHAPTER SEVEN

"DOCUMENT OFFSITE STORAGE (VITAL RECORDS) REQUIREMENTS"

Note: This step is mandatory.

A. OBJECTIVE:

Identify any items that should be copied and stored offsite to prevent total
loss if main business site is damaged. These items are frequently referred to as
"Vital Records."

B. PURPOSE:

List all key recovery elements to be retrieved from offsite to re-establish
operations in a backup facility.

C. DIRECTIONS:

1. Identify on Worksheet 7.1 all data backups that need to be stored
offsite. Include Full, Mirrored, and Incremental backups and software copies, and
send offsite.
2. List all key procedures, make copies, and send offsite.
3. Ask for copies of any "Special Forms / Supplies." Send a supply
or copy offsite.
4. After offsite is completed, do an audit of data / software using
Worksheet 7.2.

D. COMMENTS:

If an offsite storage facility is not available, use Worksheet 7.3 to identify
appropriate location.



E. SUPPORTING DOCUMENTATION:

If an offsite facility is in use, include a copy of the access and retrieval
procedures in this step behind Worksheet 7.1.


WORKSHEET 7.1 : VITAL RECORDS
Main Contact Person: ____________________ Phone: __________

ITEM ....................
DESCRIPTION ....................
FREQUENCY (How often sent off-site?) ....................
CRITICAL (Yes / No) ....................
OFFSITE STORAGE LOCATION ....................

REMEMBER TO INCLUDE: Computer system tapes, PC diskettes, CD's,
software copies, key operational procedures, documentation, network schematics,
restore jobs, source document samples, manual processing procedures (if
appropriate), etc.

COMMENT: Data backup tapes are critical to any recovery effort. Be sure
to include "Full System" copies, daily "Incrementals," and any file backups done
by specific applications. Identify "mirrored" data as a separate line item.

- - - - - - - - -

AN ADDED "BONUS" WITH GO.RECOVER-DATA CENTER:
A SHORT COURSE ON DISASTER RECOVERY PLANNING

Often, a part of the plan development process really requires some up-front training
so that the people involved in the project understand the concepts of Disaster
Recovery Planning. The GO.RECOVER-DATA CENTER Product recognizes that
requirement and has included training material that can be used at the start of the
project. The table of contents of the training materials is as follows:

A SHORT COURSE ON DISASTER RECOVERY PLANNING

1. Disaster Loss Impact
2. Disaster Recovery Definitions
3. Business Operations Impact
4. Major Recovery Planning Requirements
5. Project Elements Overview
6. Plan Development Process
7. Risk Analysis
8. Data Collection Tasks
9. Alternate Site Options
10. Alternate Site Requirements
11. Recovery Plan Development
12. Plan Maintenance and Testing
13. Helpful Hints
14. Critical Success Factors

- - - - - - - - -

ABOUT THE AUTHOR

Jan Persson has been in the Information Technology arena since 1967. In 1985
Mr. Persson established his consulting practice, Persson Associates, which
specializes in assisting all size companies, create and test disaster recovery
plans. He has worked closely with the three leading Business Recovery
companies (Comdisco, SunGard & IBM). He has been a speaker at the Disaster
Recovery Journal (DRJ) annual conferences and also contributes articles to the
DRJ trade journal. He also conducts Disaster Recovery Seminars, I/T, and BRP
Plan Development Workshops. In addition, he is certified (holds a CDP Title) by
the Institute for the Certification of Computer Professionals (ICCP) along with a
CBCP title from the Disaster Recovery Institute..

Mr. Persson has worked both for and with the three leading Business Recovery
companies (Comdisco, SunGard & IBM) and has been a speaker at the Disaster
Recovery Journal annual conferences. He also conducts regularly scheduled
Disaster Recovery Plan Development workshops for a major business recovery
vendor.

He is certified (holds a CDP Title) by the Institute for the Certification of Computer
Professionals.

He is the author of GO.RECOVER-EUC, GO.RECOVER-MID, and,
GO.RECOVER-EBIZ for small and mid-range data centers and e-businesses,
respectively (all published by Rothstein Associates Inc.).

- - - - - - - - -
Published by Rothstein Associates Inc.
In stock for immediate shipment!
- - - - - - - - -

2008, CD-ROM (Microsoft Word format)
ISBN #1-931332-48-7 (978-1-931332-48-40
Order #DR662.
- - - - - - - - -
[Home] [Catalog] [Category] [Previous Item] [Next Item] [Checkout] [Review Cart] [Button]

Disaster Center Bookstore-a service of Rothstein Associates

Rothstein Associates Inc.
4 Arapaho Rd.
Brookfield, CT 06804-3104
1-888-ROTHSTEin
Telephone: 203.740.7444; 888.768.4783
Fax: 203.740.7401
E-Mail: info@rothstein.com

Google
 
The Disaster Center