Data Backup and Recovery System Ensures the Protection of This Data in Most Circumstances

Total Page:16

File Type:pdf, Size:1020Kb

Data Backup and Recovery System Ensures the Protection of This Data in Most Circumstances Data Backups and Disaster Recovery Planning Michelle M. Howell November 11, 2003 CS 5780 - Systems Administration University of Missouri at St. Louis Introduction The collapse of the World Trade Center on September 11, 2001 reinforces the importance of backing up critical data, protecting the backups, and planning for disastrous data losses. It is estimated that the cost to replace technology and systems lost in the World Trade Center (WTC) disaster could be $3.2 billion (1). However, some companies that occupied the WTC, such as Morgan Stanley, were able to quickly recover. The financial giant was able to start running again because in addition to having the usual data backups that most companies keep on site, it also maintained real-time copies of its data in a second location miles away. All transactions occurring on the company WTC servers and mainframes were continuously transferred through high-speed telecommunications lines to computers in Teaneck, New Jersey. An event as unimaginable as the WTC collapse is not the only way to have a data loss disaster. There are countless ways to loose critical data. Human error is among the leading causes of data loss. For example, mistakes as simple as typing “rm *” at the UNIX command prompt can have disastrous results. In addition, software failure, hardware failure, computer viruses, malicious or disgruntled employees, and natural disasters such as fire and flood can cause a catastrophic system failure. The Disaster Recovery Institute International estimates that 90 percent of companies that experience a significant data loss are out of business within three years (2). Making backups of all data seems like the obvious solution. However, many small companies have inadequate backup practices or technology. The problem could be insufficient storage capacity, an inability to use backup solutions, a lack of backup testing, no offsite data storage, or inconsistent backup procedures. Unfortunately, backing up data is simply given a very low priority at a number of small firms. According to a survey conducted by storage media vendor Imation, 30% of small businesses lack formal data backup and storage procedures or do not implement those practices consistently. In fact, thirty-nine percent of the small firms surveyed admitted that they review their storage procedures only after a problem occurs. In addition, more than one third of the respondents said they do a fair or poor job of storing backup data offsite, and over half rate their disaster recovery plan as fair or poor (3). It is very difficult and in fact sometimes impossible to function normally during a crisis. It if for this reason that it is important to think about data backups before a disaster strikes. This paper provides some guidance for developing a data backup plan by summarizing data backup media and hardware technologies, data backup procedures and services, and data recovery services. It also provides an outline for disaster recovery planning. Data Backup Media and Hardware One of the first decisions to make when preparing a data backup plan is to decide what physical medium will be used to store the data backups. The speed, capacity, cost, and life expectancy of the medium are all considerations that should be taken into account when making this decision. 1 In terms of backup media life expectancy, a number of factors should be considered. For long term storage situations, the media may become obsolete due to changing technologies before it physically degrades. The information on this media would therefore become unusable. Similarly, the life expectancy of the media may be much longer than the amount of time it takes for the information on the media to degrade. Due to these considerations, care must be given when choosing media based on it’s life expectancy. Hard Drives Data storage onto hard disk media is becoming more and more prevalent in corporate data centers, according to a survey of more than 1,000 information technology managers conducted by Peripheral Concepts, Inc. (4). Hard drives (magnetic disks) have a very high data capacity, currently holding over 100GB of data (5). A typical hard drive consists of platters that are coated with magnetic film. These platters spin while data is accessed by small heads situated on drive arms. This geometry enables data to be accessed randomly, and thus very quickly. In addition to a high storage capacity and speedy access, magnetic disks are estimated to have an expected life span of 5-10 years (6). Although hard disks used to be the most expensive backup media, prices have dropped exponentially in the last few years. Removable hard disks are becoming even more affordable, and have capacities of over 2GB. The Orb Drive, by Castlewood Corporation, is an example of such a product (7). Hard drives can be used for data backups by mirroring. Disk mirroring is a technique in which data is written to two duplicate disks simultaneously. If one of the disks fails, the system can quickly switch to the other disk without any loss of data or service. Mirroring is commonly used for systems such as Internet databases, where it is critical that data be accessible at all times. However, there is a problem with this technique: if both disks are a part of the same machine and the disk controller (or the whole machine) fails, neither disk would be accessible. One possible solution to this problem is to implement a mirroring scheme that involves multiple machines. The backup machine duplicates all of the processes of the primary machine. This is effective because if the primary machine fails, the backup machine can immediately take its place without any down time. Although this is a good solution for the problem of a failed machine, the possibility still exists for loss of both machines, for example due to fire. To prevent this situation, some companies have network mirroring. These companies mirror their main disks with disks in remote locations via a network connection. However, this type of mirroring is expensive. Each machine must be mirrored by an identical machine whose only purpose is to be there in the event of a failure. Of course, mirroring does not provide total protection against data loss. If a computer virus destroys files or files are accidentally deleted, the mirrored files will also be destroyed or deleted. Having a previously stored copy of the data is important, therefore traditional data backup media will still be required. The Peripheral Concepts survey (7) also shows that a large majority of data is still backed up and archived the traditional way: on tape. Magnetic tapes Magnetic tape is the most realistic and traditional medium for creating backups. The tape is actually a Mylar film strip on which information is magnetically stored. Because magnetic tapes 2 are a sequential storage device (tape drives cannot randomly access data like other storage devices, such as disk drives), they are much slower. However, high storage capacity and low cost make magnetic tapes the storage medium of choice for archiving large amounts of data. Helical scan devices are also magnetic tapes, but the data heads spin at an angle to the strip of tape, thus creating denser data storage and higher capacity. Life expectancy and the number of times a tape can be reused depends not only on the quality of the tape itself, but also the environment in which it is stored and the quality and maintenance of the tape drive heads. An estimate of magnetic tape life expectancy is 1 year (6). QIC (quarter inch cartridge, pronounced “quick”) is a technology standard for magnetic tapes developed by a consortium of manufacturers called the Quarter-Inch Cartridge Drive Standards, Inc. (8). Travan tapes, developed by 3M Corporation, are a high density form of QIC standard tapes. Travan tapes were widely used by companies several years ago, but are now often used for personal computer backup Also called floppy tape because they can use a PC’s floppy disk controller instead of requiring their own special controller, the drives are inexpensive and reliable. The current maximum storage capacity of Travan tapes is up to 10GB, but they are relatively slow. DAT (digital audio tape) come in two standard sizes, 8mm and 4mm. 4mm DAT's are helical scan devices and therefore can support storage capacities up to 20GB. 8mm DAT's have storage capacities of only about 7GB. The 4mm tapes have a great advantage over other tape media; they are physically the smallest and therefore take up less storage room. A disadvantage of these tapes is that they are very sensitive to heat damage, thus complicating the selection of a storage location. DAT tapes come in two formats. One format is for recording video or audio, the other is for binary data. The video/audio tapes work for making data backups, but they are less reliable than the binary format in terms of retaining data. The 4mm DAT is currently the most widely used tape type, but it is being replaced by digital linear tapes (DLT). DLT tapes have a storage capacity of up to 40GB. The drives are quite fast and are the newest standard backup media technology. Quantum Corporation (www.quantum.com), the manufacturer of the Super DLTtape II, claims a shelf life of 30 years on their product. Besides this unbeatable life expectancy, the DLT tape has another advantage. Like 4mm DAT’s, DLT’s are small. The DLT dimensions are approximately 1" X 4" X 4" and they weigh only about 8 ounces (9). DLT’s are currently a very popular medium, even though they are still relatively expensive. Other Media Optical disks, such as recordable CD-RW’s have a much longer lifespan than do tapes (except for DLT’s).
Recommended publications
  • IBM Hyperswap: an Automated Disaster Recovery Solution Disaster Recovery at Different Geographical Sites
    IBM Systems Technical white paper June 2020 IBM HyperSwap: An automated disaster recovery solution Disaster recovery at different geographical sites Table of contents Introduction.......................................................................................... 2 Problem statement .............................................................................. 3 Validating the system for HyperSwap failures ................................ 6 Generic best practices for IBM HyperSwap ..................................... 7 Summary............................................................................................... 8 Get more information .......................................................................... 8 About the author .................................................................................. 8 Acknowledgments ............................................................................... 9 1 IBM Systems Technical white paper June 2020 Introduction Overview This technical paper is based on a client engagement and is developed to assist Challenge IBM® Business Partners, field sales representatives, technical specialists, and How to configure an automated IBM clients to understand when can IBM HyperSwap® be deployed on IBM disaster recovery solution Spectrum Virtualize systems and the steps to validate the configuration for between existing IBM Storwize failure cases. It also includes the best practices involved for the specific client V7000 control enclosures at engagement and can be applied in a similar environment.
    [Show full text]
  • AIX Disaster Recovery with IBM Power Virtual Server
    AIX Disaster Recovery with IBM Power Virtual Server An IBM Systems Lab Services Tutorial Primitivo Cervantes Vess Natchev [email protected] TABLE OF CONTENTS CHAPTER 1: SOLUTION OVERVIEW............................. 1 1.1 Introduction .......................................................................... 1 1.2 Use Cases ............................................................................. 1 1.2.1 Geographic Logical Volume Manager (GLVM) Replication .... 1 1.2.2 Geographic Logical Volume Manager (GLVM) Replication with PowerHA ............................................................................... 2 1.3 Solution Components and Requirements ................................... 2 1.3.1 Components ................................................................. 2 1.3.2 Requirements ............................................................... 2 1.4 Solution Diagram ................................................................... 3 CHAPTER 2: IMPLEMENTATION .................................. 4 2.1 Base IBM Cloud PowerVSI and Networking setup ....................... 4 2.1.1 Open an IBM Cloud account ............................................ 4 2.1.2 Create PowerVS location Service and Subnet(s) ................ 5 2.1.3 Provision AIX and IBM i VSIs in each PowerVS location ....... 5 2.1.4 Order Direct Link Connect Classic to connect PowerVS location to IBM Cloud ............................................................. 5 2.1.5 Order two Vyatta Gateways, one in each datacenter .......... 6 2.1.6 Request a Generic
    [Show full text]
  • Data Center Disaster Recovery
    Data Center Disaster Recovery KwaiSeng Consulting Systems Engineer Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1 Agenda Data Center—The Evolution Data Center Disaster Recovery Objectives Failure Scenarios Design Options Components of Disaster Recovery Site Selection—Front End GSLB Server High Availability—Clustering Data Replication and Synchronization—SAN Extension Data Center Technology Trends Summary © 2006 Cisco Systems, Inc. All rights reserved. 2 The Evolution of Data Centers © 2006 Cisco Systems, Inc. All rights reserved. 3 Data Center Evolution Networked Data Center Phase Data Center Continuous Data Center Availability Virtualization Data Center Network Consolidation Optimization Compute Internet Evolution Computing Data Center Client/ Networking Server 1. Consolidation Mainframes 2. Integration Content 3. Virtualization Networking 4. High Availability Thin Client: HTTP Business Agility Business TCP/IP Network Terminal Evolution 1960 1980 2000 2010 © 2006 Cisco Systems, Inc. All rights reserved. 4 Today’s Data Center Integration of Many Systems and Services Storage N-Tier Front End Network Applications Network Application/Server WAN/ Optimization FC Security Internet Switch Web Servers Resilient Cache IP Firewall DR Data Center Scalable Infrastructure Application and Server Optimization NAS App Servers Content Data Center Security IDS Switch MAN/ DC Storage Networks Internet VSANs Distributed Data Centers DB Servers FC Switch Mainframe IP Comm. Operations FC Switch RAID Metro Network
    [Show full text]
  • Small Business Disaster Recovery
    QUICK GUIDES Small Business Disaster Recovery When a disaster occurs, businesses must take care of their employees’ needs, communicate the impact, address financial matters (e.g., insurance, disaster assistance), restore operations, and organize recovery. Below are resources to help reopen your business and make progress through long-term recovery. For more details, visit: www.uschamberfoundation.org/ccc. TOP 10 TIPS FOR RECOVERY Keep detailed 1. Implement your disaster plan. Assess damage and consider if a backup location is needed. records of business 2. Shift your team and leadership from preparedness to recovery. activity and the 3. Implement a communications strategy to ensure that the facts go directly to extra expenses employees, suppliers, customers, and the media. of keeping your 4. Encourage employees to take appropriate actions and communicate. business operating 5. Document damage, file insurance claim, and track recovery. in a temporary 6. Cultivate partnerships in the community with businesses, government, and location during the nonprofits. interruption period. 7. Provide employee support and assistance. 8. Connect with chambers of commerce, economic development, and other community If you are forced to support organizations. close down, include 9. Document lessons learned and update your plan. expenses that 10. Consider disaster assistance. Contact the Disaster Help Desk for support at continue during the 1-888-MY-BIZ-HELP (1-888-692-4943), or visit www.facebook.com/USCCFhelpdesk or time that the business https://twitter.com/USCCFhelpdesk. is closed, such as advertising and the cost of utilities. RECOVERY RESOURCES The Insurance Information Institute This is a checklist for reopening your business after a disaster.
    [Show full text]
  • Azure Disaster Recovery- As-A-Service: Plan, Implement, Manage Help Ensure Speed and Ease of Cloud Recovery Through Proven Azure Disaster Recovery Solutions
    Education IT Professional Services Azure Disaster Recovery- as-a-Service: Plan, Implement, Manage Help ensure speed and ease of cloud recovery through proven Azure disaster recovery solutions From power outages to natural disasters or human error, unplanned disruptions can be costly and detrimental to your district’s educational and business priorities. In the event of a Highlights disaster, you need a reliable, tested and cost-effective solution to respond with speed and agility while reducing the financial losses • Leverage the cloud, at an affordable price that result from these outages. point, to maintain business continuity. Most school districts do not have a DR strategy or plan because • Run disaster recovery drills annually with no the cost of a secondary data centre is prohibitive and technically business or application impact. very complex. Performing a DR drill can be difficult and carries with it the risk of impacting production workloads. Data loss and • Minimize errors when failing over and drastically reduce downtime. application errors are a common occurrence when failing over to a secondary site. • Save money by using Azure as your secondary data centre. In addition, traditional DR requires constant updating and maintenance in order ensure the environment continues to • Realize a tested and proven Recovery Plan. function and perform optimally. This requires dedicated cycles • Protect heterogeneous environments with a from IT staff. single solution: Hyper-V, VMware, physical servers. Minimize risks and avoid costly incidents • Achieve Ministry mandate for DR IBM K-12’s Microsoft Azure Site Recovery is a Disaster Recovery as a Service (DRaaS) solution. It removes the complexity of traditional DR, and greatly reduces the cost to implement and maintain it.
    [Show full text]
  • SAP on Google Cloud: Disaster Recovery Strategies
    SAP on Google Cloud: Disaster-recovery strategies Overview © 2020 Google LLC. All rights reserved. Contents About this document 3 Introduction 3 Disaster recovery 3 Architecture considerations 4 Disaster-recovery strategies 5 Scenario 1: RTO within days, RPO dependent on business function 6 Scenario 2: RTO less than a day, RPO within minutes 7 Scenario 3: RTO in minutes, RPO close to zero 9 Disaster-recovery planning and testing 11 Recommendations 11 Capacity planning 11 Automation 12 Disaster-recovery plan 12 Summary 12 Further reading 13 2 © 2020 Google LLC. All rights reserved. About this document This document is part of a series about working with SAP on Google Cloud. The series includes the following documents: ● High availability ● Migration strategies ● Backup strategies and solutions ● Disaster-recovery strategies (this document) Introduction This document helps architects to make smart decisions when designing disaster-recovery (DR) architectures and strategies. The document considers not just the criticality of individual solutions, but also the different components of a typical SAP system. A good disaster-recovery strategy begins with a business impact analysis that defines two key metrics: ● Recovery Time Objective (RTO): How long you can afford to have your business offline. ● Recovery Point Objective (RPO): How much data loss you can sustain before you run into compliance issues due to financial losses. For both cases, you must determine the costs to your business while the system is offline or for data loss and re-creation. Typically, the smaller your RTO and RPO values are (that is, the faster your application must recover from an interruption), the more your application will cost to run.
    [Show full text]
  • Storage Disaster Recovery Service
    Storage Disaster Recovery Service Product Introduction Issue 09 Date 2021-06-21 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 09 (2021-06-21) Copyright © Huawei Technologies Co., Ltd. i Storage Disaster Recovery Service Product Introduction Contents Contents 1 SDRS Introduction..................................................................................................................
    [Show full text]
  • Disaster Recovery As a Service Using IBM Spectrum Virtualize and Vmware Site Recovery Manager Integration a Technical Report
    IBM Systems Technical White Paper December 2016 Disaster recovery as a service using IBM Spectrum Virtualize and VMware Site Recovery Manager integration A technical report Overview This technical paper demonstrates how IBM® Spectrum Virtualize™ Software Only V7 with VMware Site Recovery Challenge Manager can provide key components for disaster recovery as a service (DRaaS) and benefits in data mobility across sites in a Cloud and managed service providers private cloud environment. It provides a simple and automated looking to implement DRaaS to users with business continuity with low risk between sites having heterogeneous or dissimilar storage heterogeneous storage infrastructure infrastructures are met with various challenges, such as: The target audience for this paper are technical leaders, system and storage administrators, managed service providers (MSPs) and How to reduce capital expenditure cloud service providers (CSPs) to implement disaster recovery (DR) (CAPEX) and operational cost for as a service between heterogeneous storage infrastructures. DR? The solution is developed on IBM Spectrum Virtualize Software How to integrate with client’s Only V7 which is deployed on x86 processor-based Lenovo server cloud orchestration and hardware. The solution uses the VMware Site Recovery Manager interoperate with on-premises integration using IBM Storwize® Family Storage Replication existing storage systems? Adapters (SRAs) How to deliver centralized storage management? This solution provides key components for simplified automation for business continuity with the specified recovery point objective Solution (RPO) and recovery time objective (RTO) requirements for both planned and unplanned outages. IBM Spectrum Virtualize is a software- The solution also provides benefits for data mobility between defined storage solution which provides virtualization layer to decouple storage heterogeneous storage infrastructures using IBM Spectrum hardware and software management.
    [Show full text]
  • The Definitive Disaster Recovery Plan Checklist
    The Definitive Disaster Recovery Plan Checklist Every day there are new horror stories of tech outages, associated expenses. While a simple file-level backup system downtime, and data loss — even at the best of companies. When might be sufficient for some applications, your mission-critical disaster strikes, engineering teams are dispatched to repair the applications will likely need a DR technology based on real- damage, while PR teams work overtime to restore customer time continuous data replication, to enable you to achieve confidence. It’s a time-consuming and often expensive effort. near-zero RPO and RTO. No matter what the cause of the disaster, the organizations that manage them most effectively, and with the least amount #2: Identify Stakeholders of collateral damage, are those with a comprehensive, easy- to-follow, and regularly tested disaster recovery (DR) plan. The next step is to identify all those who need to be updated Whether you already have a DR plan or you are just beginning once disaster strikes. In addition to those involved with the process of creating one for your organization, this Definitive performing the actual recovery from a disaster (e.g., engineers, Disaster Recovery Plan Checklist will help you ensure you’ve support, executives), you should also pinpoint members of included all the crucial components in your plan. your PR and marketing team, vendors, third-party suppliers, and even key customers. Many companies keep a register of #1: Determine Recovery Objectives stakeholders, a good starting point for identifying all of the (RTO and RPO) stakeholders you’ll want to notify if there is a disaster.
    [Show full text]
  • Solution Brief: Huawei All in One Backup Solution
    Solution Brief: Huawei All in One Backup Solution Huawei All-in-One Backup Solution brings enterprise class seamless, KEY FEATURES automated backup to SMB customers. Commvault and Huawei offer a portfolio of data protection solutions that fit small and medium • Preconfigured, scalable architecture businesses as well as the remote office to the data center in large • Snapshot orchestration enterprises. • Deduplicated, encrypted copies • Any tier Huawei All-In-One Backup node is an integrated backup solution • Any platform designed for Small to Medium sized Businesses (SMBs), enterprise • Any data type companies, and branches of large enterprises. It deploys Huawei • Orchestrated disaster recovery RH2288H V3 as hardware and industry-leading Commvault® software as • Advanced search and eDiscovery backup software; it assembles backup server, backup media, and backup • Built-in analytics software in one package, saving construction cost and simplifying • Powerful User Interface backup management. • Universal access Our strategic alliances unlock unique value for our CHALLENGES SOLVED Partners, available nowhere else. • Modernizing virtual environments • Maintaining operational consistency at remote locations • Addressing data protection needs without additional staffing WHERE TO LEARN MORE • Simplifying data infrastructure complexity • Addressing disaster recovery planning For more information, please visit Huawei online at • Unifying departmental systems or follow us on: • Achieving regulatory compliance www.huawei.com From simple backup to cloud gateway, Huawei offers a solution that can http://www.linkedin.com/company/Huawei be applied in a number of use cases such as: http://www.twitter.com/Huawei • For small to medium sized companies, Huawei offers an All-in-One http://www.facebook.com/Huawei Backup Solution for backup and disaster recovery.
    [Show full text]
  • Disaster Recovery in Cloud Computing
    International Journal of Advanced Research in Computer Engineering & Technology (IJARCET) Volume 4 Issue 5, May 2015 Disaster Recovery in Cloud Computing Mr.Akshay A. Gharat, Mr. Devendra E. Mhamunkar ASM INSTITUTE OF MANAGEMENT & COMPUTER STUDIES (IMCOST), THANE, MUMBAI University Of Mumbai to protect the data from loss. Cloud providing companies Abstract: Nowadays , data has been generated in large like Google, Amazon, Microsoft etc., experienced cloud amount that required the data recovery services. We know disaster with a huge loss of data and servers. When disaster that the cloud computing introduces a new type of computing occurs at client side backup will be stored in cloud but if platform in today’s world. This type of computing will disaster occurs in cloud data will be lost. Natural disasters generates a large amount of private data on main cloud. may occur due to bad weather results in disaster To Therefore, the necessity of data recovery services are growing overcome these disasters there are some disaster recovery day-by-day and it requires a development of an efficient and techniques which are used to recover data. effective data recovery technique. The purpose of recovery technique is to help user to collect information from any Disaster recovery techniques as required to their backup server when server lost his data and unable to provide business continuity. Dedicated and shared models are the data to the user. To achieve this purpose, many different two approaches for disaster recovery based on cost and techniques have been proposed till date. In this review paper, speed. Storing the data from cloud infrastructure in order to we mention few recent techniques that are the solutions in the recover when disaster occur.
    [Show full text]
  • Disaster Recovery Strategies
    Disaster Recovery Strategies From the Experts at Scale Computing Technical Whitepaper Understanding how to survive and respond to I.T. threats Table of Contents Introduction ....................................................................................................................................................3 HC3 Data Protection Suite .......................................................................................................................3-5 Backup ..........................................................................................................................................................3 Replication ...................................................................................................................................................4 Failover .........................................................................................................................................................4 Recovery ......................................................................................................................................................5 ROBO and Small Environments ..................................................................................................................6 Distributed Enterprise ................................................................................................................................6 Small Environments ....................................................................................................................................6
    [Show full text]