Disaster Recovery (DR) strategies are many and varied.
Editor's note: This article introduces the white paper "DR Strategy Guide from Maxava" available free from the MC White Paper Center.
The components of your business impact analysis and mission-critical server rankings will be used as the basis for the development and implementation of a supporting recovery strategy.
Ensure the following information is absolutely clear:
• The critical business processes have all been identified.
• The availability and recovery requirements for these critical processes have been identified.
• The backup and recovery strategies reflect the assumed disaster recovery scenarios.
• The availability and recovery strategies are scalable, flexible, and compliant.
• The assumptions behind each availability and recovery strategy are clearly stated.
• The recovery timeframe objectives (RTOs) for the critical processes have been identified.
• The recovery point objectives (RPOs) for the critical processes have been identified.
The DR planning team needs to examine the technology strategies available to ensure their organization is successful if a recovery is required in a disaster. The appropriate technology solution supporting the recovery and availability strategies must meet the business objectives as agreed to during the initial analysis. This will include supporting procedures and effective DR planning, data backup requirements, off-site tape media storage, recovery restoration procedures, system redundancy, resiliency, network analysis and communications, infrastructure redundancy, replication software implementation, and infrastructure review. The IT recovery team will ensure that all availability requirements are completed in a timely manner to achieve the RTO for all the critical business functions as stated in the mission statement of the Disaster Recovery Plan.
Disaster Recovery Strategies
The challenge in selecting DR solutions from an infrastructure standpoint is that there is a tendency to view the DR solutions as individual product technologies and piece together the total solution. Instead, DR solutions need to be viewed as a complete, integrated potentially multi-product solution.
For many organizations, the all-encompassing DR strategy is to simply back up everything to tape daily, send the tapes off site, and count on the historical uptime of the IBM i platform to guarantee that it will never go down. However, when a severe hardware failure does occur in the server or a primary facility is damaged or totally lost, the 48 hours it takes to bring up the system and 24 hours minimal amount of data loss should be challenged by both IT and the business.
Companies today understand the true cost of downtime and data loss. The most important consideration remains that the survival of the organization is dependent on IT to deliver an appropriate timely response. The technology solution in place should support the recovery response needs.
To identify recovery strategies, you should consider the immediate, short- and long-term outages caused by the occurrence of a disaster. The question only remains if the outage is an incident or a disaster. Strategies also differ on the basis of long-term and short-term recovery goals. You can adopt various strategies, ranging from basic off-site tape storage, tape backup and recovery to HA with multiple sites.
General Guidelines for Selecting Recovery Strategies
Disaster Recovery Strategies are many and varied. Some organizations rely on daily tape backups, others have moved to off-site remote backups or vaulting, while yet others have embraced real-time data replication and mirroring. Cost is obviously an important factor in choosing a strategy. Generally the higher the protection required, the more a strategy will cost.
If your organization cannot afford to invest in a high-level data recovery strategy, then you must accept some data loss and downtime as inevitable after a disaster. The Disaster Recovery Strategy must be accepted by both IT and the Business, and the risks must be well understood, signed off, and accepted. Often in the past the CEO of a company left the decisions on recovery strategy to the IT department, but increasingly these decisions are now made at board level.
Want to Know More?
Download the free white paper "DR Strategy Guide from Maxava" from the MC White Paper Center.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online