1 and Disaster Recovery Solutions by Keith Vanden Eynden Investing in a source code management application, like, protects your code from accidental overwrites, deleted versions, and other common errors. The next step in protecting your code is investing time and money in an effective backup and disaster recovery solution for. The challenge is to schedule backup and recovery activities so they minimally impact access to data. This paper outlines several methods of protecting and the assets it contains. The method you choose depends on your configuration, the size of your organization and your budget. Choosing the right method In 2009 and later, the server database and mainline branches are stored in an RDBMS database. The server and mainline database tables are stored in the same RDBMS database on the computer by default. The following backup methods use the default database configuration as an example, but you may be able to use the same concepts for distributed configurations. If you have an RDBMS backup strategy, you may be able to use the existing processes to back up. If you are implementing a new backup strategy, consult any backup procedures and best practices provided by the RDBMS vendor. Your DBA can help you determine the best way to include Surround SCM databases in regular backups. Single server methods Back up to tape The simplest way to back up your database is to connect a tape drive to the server. Use the following steps to perform the backup. 1. Lock the database. Locking the database allows you to create backup copies without stopping the. It also prevents users from making any changes to the data during the backup. Some configurations may require you to stop the and RDBMS server before performing a backup. 2. Back up the database on the drive to tape. (For simplicity, drive letters and are used throughout this paper.) The database location varies based on the RDBMS. 3. When the backup is complete, unlock the database or restart the and RDBMS server. The entire process can be scheduled by using a script, Surround SCM s CLI commands, and a scheduling utility such as Cron or Windows Scheduled Tasks. While this method is straightforward, it can be time consuming and the database may remain locked for long periods of time. The amount of time it takes to back up is related to the size and number of files in the database. This may not be an issue if all users are centrally located and you can back up the files overnight. If users are dispersed across several time zones or your database is so large that it cannot be backed up in the available time period, you should use one of the other methods discussed in this paper. Copy to an internal volume If your external storage device is slow, you can possibly reduce downtime by copying the database to an internal volume and then backing up the copy.
2 The following scenario uses separate drives or volumes on the same server. 1. Lock the database on the drive. 2. Break the mirror between the two drives so that the software does not try to synchronize with the drive while you are backing up the mirrored volume. Copy 3. Unlock the drive. 4. Add a volume name for the mirror (for example, ). 5. Back up the mirrored volume to tape. At a time when the has the least amount of traffic, use the following steps to back up the database. 1. Lock the database on the drive. 2. Copy the database from to. 3. Unlock the database on the drive. 4. Back up the drive to tape at your convenience. You can use Robocopy, rsync, or a similar utility to copy between the and drives. Copy time is directly related to the speed of the hardware, the operating system, and the database size. mirroring If you want to increase the regularity of backups without investing in an additional server, you can use an application like Veritas Volume Manager or Symantec s Storage Foundations for Windows to create and synchronize two mirrored drives. 6. When the back up is complete, detach. 7. Reattach the mirror with the drive. With this method, the downtime for users is minimal because the database is only locked for as long as it takes to break the mirror. mirroring with multiple drives In the previous example, there is a primary volume and a mirrored volume. When you break the mirror between the two drives, you run the risk of losing changes while the mirror is backed up. For example, suppose that you break the mirror at 10:00 p.m. and it takes four hours to back up the mirrored drive to tape. If corruption occurs on the drive at 1:30 a.m., you will have to restore from the 10:00 p.m. copy and will lose three and a half hours of changes because no mirroring occurred during the backup. You can reduce the likelihood of losing changes while the mirror is being backed up by using two mirrored drives in the following arrangement. For this type of solution, the underlying software layer should be set up before installing. When you install the mirroring software, it creates an initial copy of the drive. You can then schedule the software to synchronize the mirror with another volume. The benefit of this method is that the mirroring software only copies the changes instead of copying the entire volume. Data is also copied at the block level instead of the file level, which provides a significant performance improvement. To use two mirror volumes, first lock the database on the drive and break the mirror for. Then attach the mirroring software to the second volume. After the mirror is established and the synchronization process is scheduled, use the following steps to back up the data.
3 The mirroring software will resynchronize the data with. While is attached, simply mount and back up that data to tape. 1. Lock the database on the drive of the primary server. 2. Break the mirror. 3. Unlock the database on the drive. 4. Add the volume for the mirror on the (). 5. Attach to the backup server. 6. Attach the mirroring software to the second volume. After the backup is complete, detach (). When you are ready for the next back up, break the mirror for and reestablish it for. Primary You can continue the process of rotating mirrored volumes as you perform backups to ensure that users always have access to current data. options All of the examples presented so far can be implemented with a single server and are appropriate for smaller companies with centrally located employees and a limited hardware budget. Larger companies with multiple locations require a Storage Area Network (). After the drive is attached to the backup server, you can back it up to tape. When the backup is complete, detach the drive from the backup server and re-establish the mirror. You can then name the second volume and attach it to the backup server. Primary Local The basic principle behind the local is the same as the software mirroring method. The following configuration builds off the method that mirrors to multiple drives. The backup procedure is similar to the one used with a single server.
4 Primary To keep the backup in Los Angeles more up to date, you can create mirrored volumes on two different s, one in and one in Los Angeles. Los Angeles Los Angeles with remote publication or replication If you have multiple locations, you may want to publish the mirrored volume to a remote location to protect against a disaster. In the following example, a company has offices in and Los Angeles. All users access using the server. The database is mirrored to a volume on the and that mirrored volume is replicated over a wide area network () to the Los Angeles server, which acts as a remote backup server. In this case, however, and will not be completely synchronized because mirroring is performed over a. (Seapine validated these configurations using an EMC CLARiiON CX3 model 80.) Remote disaster recovery The with remote publication or replication method provides the best disaster recovery solution because the mirrored copy of the database is stored on separate hardware in a remote location. Building on that, we will consider the recovery process, which is a manual process and not an automatic failover routine. The following diagram shows an example of a remote environment. Los Angeles Los Angeles Publish/Relicate Publish/Relicate Each manufacturer has different methods for replication and publication. Consult with your vendor for the solution that is most appropriate for your environment. All users connect to the server, which houses the Surround SCM and database. There are mirrored copies of the database on the server and the Los Angeles server.
5 Suppose that the server experiences a fatal crash. To recover the data, the is installed on the Los Angeles server and configured to point at the local mirrored copy of the database. The users in both locations then configure their clients to use the in Los Angeles. If the server is restored or a new server implemented, the database can be moved from Los Angeles back to. Users would configure their clients to access the server again. To minimize manual configuration, client computers can also access the server via a name instead of a specific IP address. In the cutover situation, you can modify the DNS server to have the name point to the new instead of requiring users to configure their client settings. Fibre channel Los Angeles Conclusion You can greatly improve your disaster recovery efforts using any of the methods outlined in this paper. Your goal should be to make your architecture as redundant as your budget allows. The solution you choose depends on the size of your organization, the backup frequency you require, and your hardware budget. Cincinnati, Ohio I London, England I Melbourne, Australia I Munich, Germany I Vienna, Austria 2009 Seapine, Inc. All rights reserved. 0209
Acronis Backup & Recovery 11.5 Update 2 Backing Up Microsoft Exchange Server Data Copyright Statement Copyright Acronis International GmbH, 2002-2013. All rights reserved. Acronis and Acronis Secure Zone
Disk-to-Disk-to-Offsite Backups for SMBs with Retrospect Abstract Retrospect backup and recovery software provides a quick, reliable, easy-to-manage disk-to-disk-to-offsite backup solution for SMBs. Use
EMC NetWorker Version 8.2 SP1 Server Disaster Recovery and Availability Best Practices Guide 302-001-572 REV 01 Copyright 1990-2015 EMC Corporation. All rights reserved. Published in USA. Published January,
TECHNICAL WHITE PAPER: DATA AND SYSTEM PROTECTION Achieving High Availability with Symantec Enterprise Vault Chris Dooley January 3, 2007 Technical White Paper: Data and System Protection Achieving High
Backup and Recovery With Isilon IQ Clustered Storage An Isilon Systems Best Practices Guide August 2007 ISILON SYSTEMS 1 Table of Contents 1. Assumptions... 4 2. Introduction... 4 3. Data Protection Strategies...
Cloud Services for Backup Exec Planning and Deployment Guide Chapter 1 Introducing Cloud Services for Backup Exec This chapter includes the following topics: About Cloud Services for Backup Exec Security
Backup and Recovery of SAP Systems on Windows / SQL Server Author: Version: Amazon Web Services sap- on- firstname.lastname@example.org 1.1 May 2012 2 Contents About this Guide... 4 What is not included in this guide...
Introduction to Windows Storage Server 2003 Architecture and Deployment Microsoft Corporation Published: July 2003 Abstract Microsoft Windows Storage Server 2003 is the latest version of Windows Powered
DeltaV Distributed Control System Whitepaper October 2014 DeltaV Virtualization High Availability and Disaster Recovery This document describes High Availiability and Disaster Recovery features supported
Contents Preparing to create a Microsoft SQL backup policy... 2 Adjusting the SQL max worker threads option... 2 Preparing for Log truncation... 3 Best Practices... 3 Microsoft SQL Server 2005, 2008, or
DeltaV Distributed Control System Product Data Sheet Backup and Recovery Best-in-class offering. Easy-to-use Backup and Recovery solution. Data protection and disaster recovery in a single solution. Scalable
BrightStor ARCserve Backup for Windows Tape RAID Option Guide r11.5 D01183-1E This documentation and related computer software program (hereinafter referred to as the "Documentation") is for the end user's
May 2013 Page 1 This document answers frequently asked questions regarding the Emerson system Backup and Recovery application. www.deltav.com May 2013 Page 2 Table of Contents Introduction... 6 General
Technical Considerations in a Windows Server Environment INTRODUCTION Cloud computing has changed the economics of disaster recovery and business continuity options. Accordingly, it is time many organizations
Recommended Backup Strategy for FileMaker Server 10 and 11 for Macintosh & Windows Updated September 2010 This document provides a single cohesive resource for managing and understanding the backup strategy
HP B6200 Backup System Recommended Configuration Guidelines Introduction... 3 Purpose of this guide... 4 Executive summary... 4 Challenges in Enterprise Data Protection... 4 A summary of HP B6200 Backup
NDMP Backup of Dell EqualLogic FS Series NAS using CommVault Simpana A Dell EqualLogic Reference Architecture Dell Storage Engineering June 2013 Revisions Date January 2013 June 2013 Description Initial
Microsoft Exchange 2003 Disaster Recovery Operations Guide Microsoft Corporation Published: December 12, 2006 Author: Exchange Server Documentation Team Abstract This guide provides installation and deployment
WHITE PAPER Intelligent Disaster Recovery VERITAS Backup Exec 10 for Windows Servers Intelligent Disaster Recovery Option 1/17/2005 1 TABLE OF CONTENTS Executive Summary...3 Disaster Preparation Plan (DPP)...4
EMC SourceOne Version 7.2 Disaster Recovery Solution Guide 302-000-951 REV 01 Copyright 2005-2015 EMC Corporation. All rights reserved. Published in USA. Published April 30, 2015 EMC believes the information