CAPÍTULO II MARCO TEÓRICO
CUADRO DE DETALLE POBLACIONAL
This matrix is for Tiers 2 and 1 and Transaction Integrity.
Table A-21 Tiers 2 and 1 and Transaction Integrity matrix
Additional business requirements questions
Following is a list of additional business requirement questions that can and should be answered prior to entering the Disaster Recovery Solution Selection Methodology.
Justifying business continuance to the business
Because Disaster Recovery solutions are by their very nature
insurance
, the following questions can help identify the ongoing daily payback value of a proposed Disaster Recovery solution.You might partially or fully justify the requested investment for Disaster Recovery to senior management by quantifying the following values, and then portraying the proposed Disaster Recovery solution cost as only a portion of the anticipated ongoing daily benefits, as identified by these questions.
Tangible, compelling IT values
Tangible, compelling IT values include the following benefits.
Savings due to Planned Outage reductions
1. Benefits and savings, revenue increases, due to business being able to operate without the Planned Outage
2. Benefits in personnel productivity
3. Savings in removing overtime compensation, overtime savings for Planned Outages
Solution Database-level recovery using physical tape transport
Platform Software, application, and database specific
Distance Software, application, and database specific
Connectivity N/A
Supported disk storage (primary site)
Any Supported disk storage (secondary site) Any Recovery Point Objective
- Hours to days hours - Dependent on user policy
Amount of data Any
Savings due to better testability/maintainability of recovery solution
1. Lowered cost for every test:
– Savings due to lowered system resource impact for test – Savings due to better control of testing
– Savings due to better reliability in testing – Savings due to better speed in test completion
2. Savings in maintainability costs, because GDPS insulates the Disaster Recovery method: – From application changes
– From hard to define/hard to manage applications – From hard to manage/inability to manage data
Benefits of absolute confidence in switch or cutover
1. Better information flow to decision team due to automation messaging of status 2. Lowered cost of maintaining solution
3. Increased accuracy of test and switch due to automation
Savings due to personnel cost reductions
1. Savings due to reduced labor and cost of a custom roll-your-own implementation. 2. Savings due to reduces labor costs due to automation.
3. Automation reduces salary/overtime cost of personnel to perform a recovery.
4. Pre-install and post-install difference in amount of staff required for change windows, Unplanned Outages, and practice and execute Disaster Recovery.
5. Savings because less costly and more available “B” and “C” personnel team can perform Planned/Unplanned Outage recovery.
6. Lowered skill requirements for operations or recovery team. 7. Survivability without requiring key personnel.
Benefit of providing DR after large storage or server consolidation
1. Benefits of providing efficient, trustable recovery of large consolidated data center of servers / storage.
Cost savings of bringing DR in-house versus out-sourced service provider
1. For same expenditure: Better recoverability, removal of dependencies on other service provider clients, no expiration time limit in recovery center.
2. Savings due to removal of out-sourced recovery center for equivalent functionality.
Tangible, compelling business values
Tangible, compelling business values include the following benefits.
Strategic and competitive advantage
1. 24x7 Internet client availability required on new applications 2. Worldwide client availability required on new applications 3. Meet mandatory regulatory requirements
4. Avoidance of large $ impact to business of a disaster (client $1000/hr.) 5. Exploit existing investment in installed equipment
Confidence
1. Regulatory agency confidence 2. Shareholder confidence 3. Financial markets confidence
4. Senior management confidence and trust in the recovery 5. Maintenance of brand image
6. Willingness to use the recovery or switch because of the switch
Tactical
1. Employee idling labor cost
2. Cost of re-creation and recovery of lost data
3. Salaries paid to staff unable to undertake billable work
4. Salaries paid to staff to recover work backlog and maintain deadlines 5. Interest value on deferred billings
6. Penalty clauses invoked for late delivery and failure to meet service levels 7. Loss of interest on overnight balances; cost of interest on lost cash flow 8. Delays in client accounting, accounts receivable and billing/invoicing
9. Additional cost of working; administrative costs; travel and subsistence; and so on
Intangible, compelling values: IT
Intangible compelling values for IT include the following:
1. Value of Disaster Recovery strategy that resolves failed previous Disaster Recovery methods.
2. Personnel:
– Savings due to reduced number of storage administrators required per TB of disk storage
– Recruitment costs for new staff on staff turnover – Training/retraining costs for staff
3. Confidence in recoverability because of: – More frequent tests
– Success of tests
4. Planned Outage reductions creates new options in testing or site maintenance: – Confidence and accuracy value due to more frequent testing
– Savings due to less expensive cost for testing – High confidence in switch
– Value of prior and post “Planned Outage minutes/year”
– Business impact of Planned Outages/year (Planned Outage client cost * Planned Outage minutes)
5. Testing:
– Assuring successful recovery through increased frequency of testing – Catching errors in recovery through increased frequency of testing – Repeatability
6. Automation value: – Repeatability
– Trustability
Intangible compelling values: Business
Intangible compelling business values include the following benefits.
Unplanned Outage revenue loss avoidances
1. Lost revenue 2. Loss of cash flow
3. Loss of clients (lifetime value of each) and market share 4. Loss of profits
Unplanned Outage cost avoidances: IT
1. Cost of replacement of buildings and plant 2. Cost of replacing equipment
3. Cost of replacing software
Unplanned Outage business impacts
1. Brand image recovery.
2. Fines and penalties for noncompliance. 3. Liability claims.
4. Additional cost of advertising, PR, and marketing to reassure clients and prospects to retain market share.
5. Loss of share value.
6. Loss of control over debtors.
7. Loss of credit control and increased bad debt.
8. Delayed achievement of benefits of profits from new projects or products.
9. Loss of revenue for service contracts from failure to provide service or meet service levels. 10.Lost ability to respond to contract opportunities.
11.Penalties from failure to produce annual accounts or produce timely tax payments. 12.Where company share value underpins loan facilities, share prices could drop and loans
be called in or be re-rated at higher interest levels. 13.Additional cost of credit through reduced credit rating.
Business requirements questions for detailed evaluation team
The following list of questions and answers will need to be addressed by the detailed evaluation team in the course of quantifying, justifying, and designing the Disaster Recovery solution. Some questions are business in nature, others are IT or infrastructure in nature. They are the expanded super-set from which the basic starter set business requirements questions in “Starter set of business requirement questions” on page 30 are derived. We provide them here so that you can have a guideline for the types of information that will need to be gathered and analyzed by the detailed evaluation teams to finalize an in-depth recommendation.
Business profile
1. What is the client business/industry?
2. What is the compelling reason for the client to act at this time? 3. Who is the sponsor within the organization?
4. What is the budget that is allocated for this project? 5. When do they expect to have this implemented?
6. What are your goals that you feel are important for a successful project?
7. Which business sponsors do we need to engage with to properly determine the critical success factors for the project?
8. Will funding come from these mission-critical business sponsors or from within the previously constructed IT budget? Are funds allocated?
9. Have you designed an IT recovery program, which incorporates various “speeds” of recovery in the event of interruption? Who is your current business continuance provider? Current contract expiration date?
10.Does your recovery plan take into account any acceptable level of transaction data loss and data unrecoverable? Explain.
11.What would the financial impact be on the interruption to your company due to some unexpected, unplanned catastrophic event?
12.Which business processes require an advanced level of recoverability in the event of an unplanned medium to a long-term interruption of I/T services?
13.Do you back up all of your company’s critical data on a regular basis? Frequency? If a declared disaster occurred, would you be ready and able to restore your company’s critical data to the point of failure?
14.Are critical applications replicated offsite in case of disaster? Can you access the site quickly with your staff in the time you have established?
15.If you don’t have a business continuance program in place, what is the motivating factor associated with this change in strategy? Why are you interested in doing this now? 16.What is your current yearly cost associated with business continuance? If internal,
approximate cost.
17.What is your current time frame for the business continuance project?
18.What type of disk do you currently use? Manufacturer? Total capacity? Mixed environment? Utility S/W? Upgrade plans? Explain.
19.Can you supply a total inventory list of all current server hardware? 20.Is your company a current IBM Hot Site client?
Disaster Recovery planning and infrastructure sizing
21.Has a sizing exercise been done? (Disk Magic for PPRC or XRC sizing, or both)? 22.Is the implementation for data migration or Disaster Recovery?
23.If the implementation is for data migration, is the plan to minimize the amount of time in duplex by using the hardware bit maps?
24.Has the client been made aware of the various Disaster Recovery documents and tools? 25.Will IBM Global Services or a Business Partner be involved in the implementation? 26.Has FlashCopy or some other Point in Time (PiT) copy been considered?
27.What is the current Disaster Recovery Objective (RTO or RPO)?
28.Recovery Time Objective (RTO)? What is your desired elapsed time objective from time of disaster until time of full recovery and accessibility to end users? (Includes database recovery time.)
29.Recovery Point Objective (RPO)? At the time that the RPO is complete, how much data is possible to recreate? (Measured in terms of seconds, minutes, and hours.)
30.How long does it take to Initial Program Load (IPL) the system following an unplanned system failure?
31.What is the critical application restart time after a system failure (after the system is IPLed)?
32.What is the planned system restart time under normal conditions (length of time to bring up your system)?
33.What is the planned system shutdown time (length of time to stop all applications and the system)?
34.What platforms are required to be recovered? – z/OS – S/390® – OS/390® – VM – VSE – TPF – Linux/390 – UNIX®
– IBM Sserver pSeries – RS/6000®
– AIX (non-clustered or clustered?)
– Sun Solaris (non-clustered or clustered?) – HP-UX (non-clustered or clustered?) – IBM Sserver iSeries (AS/400®, OS/400®) – IBM Sserver xSeries
– Microsoft Windows NT® – Microsoft Windows 2000 – Linux
– Other
35.What storage mirroring technologies will be used (ESS XRC, ESS PPRC, PtP VTS, other)?
36.Are coupling facilities being used? 37.How many/type/model/vendor?
38.Are facilities to handle data integrity included?
39.Are there adequate resources for managing Internet security and intrusion, with ongoing monitoring and management?
40.Is the IT recovery strategy in line with the business objectives? Does the business /or IT operations, or both, hinge on the availability of an individual person’s skills?
Primary side hardware
41.How many primary control units will be installed? 42.Who is the vendor?
44.What processors are installed? 45.How many/type/model/vendor?
46.Are there tape drives involved in this proposal? (If yes, describe.)
Secondary side hardware
47.Is the secondary site client owned or are you using a business recovery center? If so, which one? Client owned?
48.How many secondary control units will be installed? 49.Who is the vendor?
50.How many volumes are expected? 51.What processors are installed? 52.How many/type/model/vendor?
53.Are there tape drives? (If yes, describe.)
Performance
54.Has a bandwidth analysis been performed by collecting and analyzing data on the production applications?
55.What percentage of the workload is required to be mirrored? 56.What is the method of automation to be used (GDPS, other)? 57.Is cross-platform data consistency required?
58.What platforms?
59.What level of consistency?
Connectivity
60.What is the distance to the remote site (miles or kilometers)?
61.What is the infrastructure to the remote site (Dark Fibre, Fibre provider/DWDM, Telecom line - what speed and flavor, T1 - 128 KBytes/sec., T3 - 5 Mbytes/sec, OC3 - 19
Mbytes/sec, IP)?
62.Will channel extenders be used? If so, which channel extender vendor is preferred (CNT, Cisco, McData, Brocade, other)?
Related publications
The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this Redpaper.
IBM Redbooks
For information about ordering these publications, see “How to get IBM Redbooks” on page 55. Note that some of the documents referenced here may be available in softcopy only.
IBM TotalStorage Solutions for Disaster Recovery, SG24-6547
The IBM TotalStorage Solutions Handbook, SG24-5250
How to get IBM Redbooks
You can search for, view, or download Redbooks, Redpapers, Hints and Tips, draft
publications and Additional materials, as well as order hardcopy Redbooks or CD-ROMs, at this Web site:
ibm.com/redbooks
Help from IBM
IBM Support and downloads ibm.com/support
IBM Global Services ibm.com/services
Index
D
Disaster Recovery
business requirements questions 47 challenge in selecting a solution 2 eliminate non-solutions 32
example of Solution Selection Methodology 13 hourglass concept in methodology 8
nature of solutions 2
Solution Selection Methodology 6 Solution Selection Methodology steps 9 Tiers 3
usage of methodology 7
value of Solution Selection Methodology 12 Disaster Recovery Solution Selection Methodology
hourglass concept 8 tutorial 6
H
hourglass concept 8M
Methodology example 13 steps 9R
Redbooks Web site 55 Contact us viii
T
Tier 2,1
Planned Outage matrix 45 Transaction Integrity matrix 47 Unplanned Outage matrix 46 Tier 3
Transaction Integrity matrix 44 Unplanned Outage matrix 43 Tier 4
Transaction Integrity matrix 43 Unplanned Outage matrix 42 Tier 4,3
Planned Outage matrix 42 Tier 5
Planned Outage 39
Transaction Integrity matrix 41 Unplanned Outage matrix 40 Tier 6
Planned Outage matrix 35 Transaction Integrity matrix 38 Unplanned Outage matrix 36 Tier 7
Planned Outage matrix 32
Transaction Integrity matrix 34 Unplanned Outage matrix 33 Tiers
blending 4
Disaster Recovery 3 tutorial
®