|
SAP
Disaster Recovery
Geus Technology has the solutions, technical leadership and staff
necessary to successfully guide your organization through the process
of establishing an effective Disaster Recovery strategy for your SAP
systems. Our experience in Disaster Recovery of SAP systems is
unsurpassed in the industry. Our consultants are unrivaled in the
marketplace, they will provide you with knowledgeable answers and
insight, and they will provide you with the assurance that your systems
will be able to be successful operational should a disaster occur.
Why Disaster Recovery?
Disasters
come in many flavors.
Unfortunately, we do not get to choose our favorite flavors, nor do we
get to select the time when we will be ready to sample their varieties.
By their very nature, disasters are sudden, unexpected, and unwanted.
A
written disaster recovery
plan is very important to a successful strategy. The very process of
writing the plan is an exercise in sound information management.
Disaster recovery is important for these aspects:
 |
Improved protection of vital
assets |
|
- More cost-effective protection of vital information
|
|
- The disaster plan is a close partner of business insurance and employee security.
|
 |
Reduction of the Risk of Human
Disasters |
|
- Disaster plans serve as a catalyst
for improved safety and security measures to reduce the risk of
preventable, man-made disasters.
|
 |
Improved
Management |
The plan encourages the
organization to review its essential requirements of the SAP system to
the total organization, identify and correct potentially hazardous
situations, measure the impact of specific disasters on personnel and
operations, and assess its own ability to function effectively after a
disaster.
Geus'™
Solution for Disaster
Recovery
Geus
Technology has been actively
involved in the processes, procedures, solutions, and advances in
disaster recovery planning and testing of SAP systems. Geus has
developed a solution that ensures our customers receive the Industry
Best solution for their environment. Geus'™ unique approach to
archiving projects comprise the following 2 elements:
 |
Disaster Recovery Plan Development |
 |
Disaster Recovery Testing |
Disaster
Recovery Plan
Development
Geus focuses on the SAP system(s) for the development of the Disaster
Recovery Plan. Interfaces, Add-ons, and associated systems that
interact with the SAP system(s) are taken into consideration when
developing the plan. The following 7- step process is utilized to
analyze, develop and test your Disaster Recovery:
1. Risk Assessment:
The process of identifying and minimizing the exposures
that may challenge an organization.
2. Business
Impact Analysis:
The process of analyzing appropriate business functions and the effect
that a specific disaster may impose.
3. Recovery
Strategy Development:
The process of developing recovery strategies for the
continuation of critical business functions.
4. Plan
Development: The
process of developing the document that defines the resources, actions,
tasks and data required to manage Emergency Responses and the business
recovery process. The goal of the plan is a timely recovery within
stated recovery objectives.
5. Plan Implementation
and Test:
The process of putting into place the recovery plan
elements
that makes recovery viable. Testing will validate the recovery plan
capability, and identify areas for improvement.
6. Plan
Administration Procedures and
Guidelines Development:
The process of developing the
course of action for administering the recovery plan.
7. Training
and Awareness:
The process of developing a program for periodic training and awareness
of business recovery issues and requirements.
Disaster Recovery Testing
Geus can provide you with a complete and thorough test of Disaster
Recovery processes and procedures. Whether you want a single test today
or utilize our program for an actual disaster and for testing on an
annual or semi-annual basis. We test the plan that either we have
developed with you or your own test plan completely. We will
successfully test your plan and provide recommendations for
improvements, direction on corrective measures and modify your plan to
ensure success should it be needed in a real disaster.
Below
are the tasks that
we complete during a Disaster recovery test:
Task
1: Disaster
Recovery
Plan Roll-out
Activities
Publish and distribute the Disaster Recovery Plan to authorized
personnel and implement access levels to the repository. Coordinate the
acquisition of required plan resources.
Task
2: Determine Test
Frequency and Methods
Based on the expected volatility of the recovery environment, staff
turnover, and audit requirements determine how frequently the plan
should be tested and identify the type of test methods to be used.
These methods include: full recovery site test, major component tests,
back-up media tests, round-table sessions, call-tree validation and
whether these tests will be announced or unannounced.
Task
3: Create Test
Administration Tools
Create a method to track the test schedule, objectives, activities,
results and resultant action items for each test. Determine the
retention schedule for test results and associated plan updates.
Task
4: Plan Initial
Recovery Tests and, Develop and document a plan for testing the
continuity plan. Schedule the
tests and synchronize multiple
participants, if any, to optimize test time.
Task
5: Review Plan to
Validate Procedures
Assemble recovery teams and others with key business recovery roles and
responsibilities and walk through the documented
draft
procedures. Refine business recovery procedures as required.
Geus will provide the following in case of an actual disaster or a test:
 |
Perform disaster recovery services in responses to disaster or test |
 |
Provide resources during disaster or DR test |
 |
Manage the complete recovery process |
 |
Provide for recovery of database and application in a DR event |
 |
Provide application, database, and systems administration resources during disaster or test |
 |
Administration of resources during disaster or DR test |
 |
Provide emergency operational or application/database monitoring support |
 |
Migrate the application back to the primary production facility for post disaster stabilization |
|