HADR Best Practices Guide

1
HADR Best Practices
(High Availability Disaster Recovery)
Stephen M. O’Neal
WW Multi Value Principal Solutions Architect
HADR Best Practices

2
Credits and Acknowledgements
Presenters
• Stephen M. O’Neal
Developers
• Kirk Kaynor, Practice Director
Rocket MV Professional Services
• Stephen M. O’Neal
©2015 Rocket Software, Inc. All Rights Reserved.

3
Abstract
Learn from the many HADR implementations where
Rocket has assisted! Best Practices for stability,
replication, emergency failover, maintenance and many
other uses will be presented.

4
Agenda
HADR Best Practices
• Design
• Build
• Test
• Document
• Review
Additional Resources

5
Agenda
• Design
• Build
• Test
• Document
• Review
Additional Resources
SLA Deep Dives
(Service Level Agreements)
• Recovery
• Security
• Monitoring
• Building test data

6
Agenda
• Design
• Build
• Test
• Document
• Review

7
Agenda
• Design
• Build
• Test
• Document
• Review

9
Design
Determine Availability and Performance SLAs
• Business need for availability and performance
• Identify possible scheduled and unscheduled outages
 Maintenance
 Be realistic on unscheduled outages
• Establish:
 Recovery Time Objectives (RTOs) and,
 Recovery Point Objectives (RPOs) or data loss tolerance

10
Design
How requirements accomplished
• Recoverable File System (RFS)
• U2 Replication
Local and Remote Disaster Failover
High Availability for scheduled outages
• Maintenance and upgrades

11
Design
Flexibility
Improved performance
• Reporting and Extracts on Subscribing Servers
Building Development and QA environments
• From replicated production data
All this in the context of your SLAs

12
Design the HADR Environment
Application/Devices
Security
Database
Network
Operating System
Virtualization Software
Hardware/Storage

13
Design the HADR Environment
Application/Devices
Security
Database
Network
Operating System
Virtualization Software
Hardware/Storage
Overlay with SLAs
Review w/others - Collectively
Use experienced professionals
• Not the place for On the Job Training
Learn from Rocket
• Rocket MV HADR Portal
Document what you have now

14
SLA Deep Dive - Recovery
Local = High Availability
• RFS/U2 Replication
Remote = Disaster Recovery
• U2 Replication Immediate = Failover
• U2 Replication Deferred = recovery from processing error
 Defer (say) for 2 hours
 Recovery from inadvertent CLEAR.FILE or wrong program run
 UV has the capability to roll forward up to a point in time

15
SLA Deep Dive - Security
U2 Replication and Security
• Protects from cyber attacks
• Sends the changed record
HW Based Replication does not protect for extortion
• Replicates data immediately on the system
• U2 Replication protects you in this case

16
SLA Deep Dive - Security
If using Automatic Data Encryption (ADE)
• Plan for wallets and keys from Publisher/Subscriber
• U2 Replication takes the data across in the same format
Security may be different on reporting and extract
servers
• There may be a completely different security setup when data
context changes

17
Monitoring the Infrastructure with MVCure
Plan to implement System Management by Exception
• The system should notify you when something is amiss
 Full directory
 Locks being held too long
MVCure will enable the monitoring of many items
• Looking to implement more and more capabilities
Heuristics to “Heal Thyself”
• Restart a process/release a lock
These statements represent Rocket Software’s current intentions. Rocket development plans are subject to change or withdrawal without further notice.
Any reliance on these statements is at the relying party’s sole risk and will not create any liability or obligation for Rocket

18
SLA Deep Dive – Building Test Data
Trends in Building Anonymous Test Data
Two Tier Standards
• Make Customer/Vendors unrecognizable – we want to move this way
• Make Customer data unrecognizable – extremely expensive

19
SLA Deep Dive – Building Test Data
What you MUST DO when building Test Data
• On UniVerse
Protect from INDEXES Updating into Production
• Physically/Logically away from Production!!!
• Restore into separate system!!!
• Change the Security – Change Groups immediately
• Use SET.INDEX to change the path – Otherwise points to
production

21
Build
Build in a separate environment
• Such as Test or Quality Assurance
• Similar as much as possible to production
• Ensures, in advance, production implementation is performant
Automate implementation as much as possible
• Accuracy through automation
• If unsure, build again

22
Build
Biggest Issue
• Maintaining performance while meeting SLA objectives
• Performance depends on the modes of replication
 Real-Time, Immediate, or Deferred
• Publisher and subscriber configurations
 Replications groups definitions
• Only validated through testing

24
Test
Vary mix of processing
• Online
• Batch Processing
Processing volumes
• Same as production during functional tests

25
Test – Personnel and Acceptance
Quantify results
• Removes personalities and ‘assessments’
 “It’s a lot slower than production”
Use objective observers
• Ask (not involved) staff people to watch and make comments
• We’ve been amazed at the insights
• Ask observers to validate processing

27
Document
Develop “Recovery Blueprint”
• Document “As Built”
• Share with everyone who provides support
• Review with everyone and ask for input
Use documentation
• For education of operations staff
• Audit and compliance

28
Document
Strive for automation
• Increase accuracy through automation
• There will always be manual steps
• Revise as you gain experience

30
Review
Annual Testing of the Plan (Minimum)
• Some organizations semiannual or quarterly
 Varies by cost of being down, or compliance
• Some organizations alternate between sites
 ½ year one site, ½ year the other
• If your staff forgets, recover more frequently
 You have a test environment, use it!

31
Review
Annual External HealthCheck
• Use resource external to your organization
• A second set of eyes
• Attempting to avoid 40% failure rate due to someone
making a mistake on a server
Update the “Recovery Blueprint”
• Whenever changes are made to the environment
• And make sure you reboot the server

33
Additional Resources
HADR Portal
http://info.rocketsoftware.com/hadr.html
Product Availability Matrix
• States minimum release level for U2 Replication
• Matched to the release of the Operating System
https://u2tc.rocketsoftware.com/matrix.asp

34
Next Steps
Do Something!
Read the HADR Portal Information
Ask for Help

35
Summary

36
Disclaimer
THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED
IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
IN ADDITION, THIS INFORMATION IS BASED ON ROCKET SOFTWARE’S CURRENT PRODUCT PLANS AND STRATEGY,
WHICH ARE SUBJECT TO CHANGE BY ROCKET SOFTWAREWITHOUT NOTICE.
ROCKET SOFTWARE SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR
OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
• CREATING ANY WARRANTY OR REPRESENTATION FROM ROCKET SOFTWARE(OR ITS AFFILIATES OR ITS OR
THEIR SUPPLIERS AND/OR LICENSORS); OR
• ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF
ROCKET SOFTWARE.

37
Trademarks and Acknowledgements
The trademarks and service marks identified in the following list are the exclusive properties of Rocket Software,
Inc. and its subsidiaries (collectively, “Rocket Software”). These marks are registered with the U.S. Patent and
Trademark Office, and may be registered or pending registration in other countries. Not all trademarks owned by
Rocket Software are listed. The absence of a mark from this page neither constitutes a waiver of any intellectual
property rights that Rocket Software has established in its marks nor means that Rocket Software is not owner of
any such marks.
Aldon, CorVu, Dynamic Connect, D3, FlashConnect, Pick, mvBase, MvEnterprise, NetCure,
Rocket, SystemBuilder, U2, U2 Web Development Environment, UniData, UniVerse, and
wIntegrate
Other company, product, and service names mentioned herein may be trademarks or service marks of
others.

HADR Best Practices Guide

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a HADR Best Practices Guide

Semelhante a HADR Best Practices Guide (20)

Último

Último (20)

HADR Best Practices Guide