Atempo, Inc. LIVE BACKUP DEPLOYMENT GUIDE PLANNING AND DEPLOYING LIVE BACKUP IN YOUR CORPORATE ENTERPRISE. Author: Amy Gracer,

Transcription

1 ... Atempo, Inc. LIVE BACKUP DEPLOYMENT GUIDE PLANNING AND DEPLOYING LIVE BACKUP IN YOUR CORPORATE ENTERPRISE Date: May 2011 Author: Amy Gracer, Version: alb.lbdg en

2 . Copyright Atempo Inc. All rights reserved. Atempo and the Atempo logo are trademarks or registered trademarks of Atempo Inc. All other trademarks, icons and logos are the property of their respective holders. Other product and company names mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Atempo Incorporated on the issues discussed as of the date of publication. Due to inevitable changes, it should not be interpreted as a commitment on the part of Atempo, and Atempo cannot guarantee the accuracy of any information presented after the date of publication. This document is for information purposes only. Atempo makes no warranties express or implied, in this document.

3 Table of Contents PREFACE... 1 WHAT WILL YOU LEARN FROM THIS GUIDE?... 1 WHO SHOULD READ THIS GUIDE?... 2 OTHER LIVE BACKUP DOCUMENTATION YOU WILL NEED PLANNING A DEPLOYMENT OF LIVE BACKUP ON WINDOWS... 3 WHAT S INVOLVED?... 3 LIVE BACKUP DEPLOYMENT PROCESS... 4 SCHEDULING RESOURCES... 5 Installation and configuration... 5 Estimate time to replicate client PCs... 5 Deployment ANALYZING CLIENT REQUIREMENTS... 7 CLIENT SYSTEM REQUIREMENTS... 7 Hardware... 7 Software... 7 CLIENT READINESS... 8 Perform virus scan... 8 Check disk space... 8 Analyze potential software conflicts DETERMINING SERVER REQUIREMENTS... 9 LIVE BACKUP SERVER MINIMUM SOFTWARE REQUIREMENTS Software requirements for Live Backup Server Software requirements for Live Backup Console SERVER STORAGE SPACE Temporary Space for Installation Client data How many clients Types of protection Size of the data on each client SQL Server Live Backup system databases Number of server computers NETWORK ARCHITECTURE Network connectivity Dial-up connections Broadband connections Local Area Network (LAN) connections Network impact expectations Server throughput... 15

4 . DISK REQUIREMENTS CPU/MEM/SQL REQUIREMENT EXAMPLES Example 1: Mixed protection; 24 hour connection Example 2: Full protection, partial connection INITIAL REPLICATION CONSIDERATIONS OVERVIEW DEPLOYMENT TIPS FOR EASE OF REPLICATION Deployment methods and auto-creation Seed your database Groups Disk space Replication rate INSTALLING THE LIVE BACKUP SERVER MICROSOFT SQL SERVER SETUP Important notes Installing SQL Server Install SQL Server Install SQL Server Configuring Microsoft SQL Server Processor configuration Disks and drives Database drive Database configuration SQL services SQL user account setup SQL Server shut down time Service packs INSTALLING LIVE BACKUP SERVER Before you install To install Live Backup Server POST INSTALLATION CHECKS IIS configuration IIS IIS User accounts CONFIGURING LIVE BACKUP SERVER MANUAL VS. AUTOMATIC CLIENT ACCOUNT CREATION MANUAL CREATION Create a group Create clients AUTOMATIC CREATION Create a group for auto-creation Define auto-creation policies Configure client auto-creation Configure group auto-creation... 45

5 How to manage deployment with clients auto-creation DETERMINE PROTECTION AND CONFIGURATION PROPERTIES General Protection Protected Data Discardable Data Storage Data Aging Feature Lockdown Expiration Auto-creation DEPLOYING THE CLIENTS DEPLOYING LIVE BACKUP CLIENTS FOR WINDOWS Manual installation Web installation Enable the Live Backup Client Web installation Notify clients of the Web installation Run a Live Backup Client Web installation Command line installation To run a command line installation of Live Backup Client: Installation batch file Make the Live Backup distribution files available on a network Prepare the installation batch file Execute the batch file Symantec GHOST or cloning software DEPLOYING LIVE BACKUP CLIENT FOR MAC Install the Live Backup for Mac Windows Service Configure protection for your Mac clients Create a group for Mac clients and configure protection settings Configure auto-creation policies Install the Live Backup Client for Mac software System Requirements To deploy the Live Backup Client for Mac software To install the Live Backup Client for Mac software manually Perform a silent install of Live Backup Client for Mac To notify clients of an upgrade automatically Reconfigure auto-creation policies CHANGING PORTS USED FOR SERVER/CLIENT COMMUNICATION ALLOW THE LIVE BACKUP CLIENT FOR WINDOWS TO CONNECT OVER A NON-STANDARD PORT Under Windows Server 2003 and IIS Under Windows Server 2008 and IIS7: Live backup Client for Windows Installation ALLOW THE MAC CLIENT TO CONNECT TO THE LIVE BACKUP SERVER OVER A NON-STANDARD PORT 76 Configure a port for delivery of Live Backup for Mac Client software updates... 76

6 . Configure a port for data communication between the Live Backup Server and the Live Backup for Mac Client To configure a non-standard port on Live Backup Server To modify the port configuration file: TESTING AND TUNING CHECK THAT CLIENTS ARE INSTALLED PROPERLY CHECK THAT CLIENTS ARE CONNECTED PROPERLY CHECK THAT CLIENTS ARE REPLICATING CHECK THE AMOUNT OF DISK SPACE BEING CONSUMED CHECK DISK SPACE FOR DATA AGING CREATE A CHECKPOINT PERFORM A TEST RECOVERY OF A FILE... 84

7 . Preface Atempo Live Backup Deployment Guide This guide provides preparation information for intermediate and advanced administrators who are planning to deploy Atempo Live Backup in their enterprise. This document is a companion to the Live Backup Installation and Setup Guide. Although that book describes basic system requirements, installation, and initial configuration procedures, this book guides you through planning your deployment within specific configurations. This book includes information you should consider before you deploy and recommendations for setting up prerequisite hardware and software, depending on the number of clients as well as the amount and type of data you want to protect. NOTE Your Atempo Live Backup deployment plan should reflect your understanding of how Live Backup, SQL Server, and Windows Server operating systems interoperate. It should encompass the relationships between Windows Server sites and domains, domain controllers, and Active Directory. Ideally, the deployment is performed by the Windows Administrator in conjunction with the Microsoft SQL Server administrator. WHAT WILL YOU LEARN FROM THIS GUIDE? In this guide, you will learn about the following: Analyzing key elements of your current environment Planning hardware and software for the best performance Planning protection configuration Planning initial replication Installing Live Backup Server Configuring Live Backup Server for the deployment Deploying Live Backup Client Testing and tuning your configuration 1

8 . WHO SHOULD READ THIS GUIDE? This document is designed for information technology professionals who are responsible for deploying Live Backup in their corporation. Such professionals may be in the following roles: Systems administrators responsible for planning and deploying technology across Windows Servers, including domain and Active Directory configurations. SQL administrators responsible for setting up and maintaining SQL Server. NOTE This guide is not intended for Live Backup Client users; rather, it is intended for administrators responsible for planning and deploying Live Backup Server and Client to the client computers in the enterprise. OTHER LIVE BACKUP DOCUMENTATION YOU WILL NEED In addition to this Deployment Guide, you will also need the following documents to complete the deployment: Live Backup Installation and Setup Guide: Provides system requirements and detailed instructions for installing Live Backup Server and Live Backup Client. Also details the initial configuration of the Live Backup Server, including how to add clients and initiate protection. Live Backup Administrator s Companion: Describes the Live Backup architecture and details how to configure and maintain Live Backup Server using the Live Backup Console. Live Backup Group Administrators Guide: Describes the Web-based Live Backup Clients Management Console for managing groups of clients remotely through role based administration. Live Backup Client User Guide: Provides full instructions on how to use Live Backup Client on Windows operating systems. Live Backup Express Client Guide: Provides instructions for the user document only version of Live Backup Client. Live Backup Client for Mac User Guide: Provides instructions for using Live Backup Client on Mac operating systems. The guides are referenced within this document where they are required. You can find all documentation in the DOCS folder of the Live Backup product CD-ROM, or you can download them from the Knowledge Base. 2

9 1 Planning a deployment of Live Backup on Windows Analyzing needs This section provides an overview of what s involved in a Live Backup deployment on Windows operating systems, as well as recommendations for scheduling your resources. WHAT S INVOLVED? As in any large scale software installation, the most important step for a successful deployment is planning making sure the hardware, network infrastructure, and third-party software are all prepared for your installation. You will also need to plan for both personnel resources to perform the deployment as well as the additional network load to perform the initial replication. Although this guide describes how to deploy Live Backup in your production environment, Atempo highly recommends that you first deploy a small group (5-10) of representative clients to a test server, and analyze the data storage requirements and network resource usage. This guide provides guidelines for determining these requirements without the test bed; however, the best way to determine your corporation s unique requirements is through a test environment. The basic steps for a Live Backup deployment are as follows. Each step is described in a separate chapter in this guide: 1. Analyze client readiness, protection requirements, and prepare the client computers 2. Analyze server readiness 3. Plan for the initial replication 4. Install Live Backup Server and supporting software 5. Configure Live Backup Server for your chosen deployment method and client protection 6. Deploy Live Backup Client 7. Test and tune your configuration See the flowchart, on the following page. 3

10 . LIVE BACKUP DEPLOYMENT PROCESS 4

11 SCHEDULING RESOURCES Use the following estimates to schedule the necessary personnel for a full Live Backup deployment. INSTALLATION AND CONFIGURATION The steps for installing and configuring Live Backup Server for 100 clients include the following: Task Time Estimate 1. Install Windows Server 2003 and Service Pack 2 or Windows Server Install MS SQL Server 2008 (or R2); or Install MS SQL Server 2005; or Install MS SQL Server 2000 and Service Pack 3a 2 hours 1 hour 3. Install Live Backup Server 15 minutes 4. Configure for client protection and deployment 1 hour Total 4 hours, 15 minutes ESTIMATE TIME TO REPLICATE CLIENT PCS The time required to replicate a client depends on many factors: Network technology (10 Mbps versus 100 Mbps, switched versus shared, etc.), client processing power, the nature of the data being replicated, and server performance all have significant influence on the outcome. Assuming Live Backup Server is able to accept 2 MBps of input data traffic, Live Backup Clients with full protection and 2 GB of protected data will replicate at an approximate rate of 50 to 100 clients per day. TIP You should configure the size of your replication groups depending on your needs. If you want the overall replication time to be as short as possible, and you have a powerful server, then configure groups of clients for replication. If it is more important that each individual client replicates as quickly as possible, then configure smaller groups. In this configuration, the overall replication time will be longer. DEPLOYMENT Resources required for deployment depend on the deployment method that you choose. Live Backup offers the following options for deploying Live Backup Client across your enterprise. These methods are described in detail in Chapter 7: Deploy the clients on page 55. Manual installation: Use this method if you want to install the Live Backup Client software individually at each computer. This method installs all prerequisite software as well as the Live Backup Client software. 5

12 . Time estimate: 15 minutes per client computer. Web installation: Use this method to deploy Live Backup to a large number of clients via an intranet or Internet Web link. It enables each end-user simple access to the Live Backup Client installation or upgrade, while you control which installation options are available. This method installs all prerequisite software as well as the Live Backup Client software. Time estimate: About 5 minutes to run the client installation manually, which can occur concurrently, depending on user response. Command line installation: Use this method to install clients via a batch file. This method does not install prerequisite software. Time estimate: 15 minutes to configure batch file; 15 minutes to configure deployment. Ghost or cloning software installation: Use this method if you have a Ghost or other clone image that you deploy to all clients in your enterprise. Note that this method requires a modification to Windows registry. Time estimate: 15 minutes to configure Live Backup Client on cloning software, then time to configure and deploy the image, which is dependent on the third-party software used. 6

13 2 Analyzing client requirements Now that you are ready to begin planning your deployment of Live Backup, the first step is to analyze the client computers that you want to protect with Live Backup. You will need to make sure all clients meet the system requirements, check for viruses, and determine if there are any potential conflicts. Next, you will need to decide the type of protection you want to apply to the clients. CLIENT SYSTEM REQUIREMENTS Make sure your clients meet the following system requirements, and if not, update them accordingly. HARDWARE PC or compatible with a Pentium Pro Processor (Pentium II or later recommended). For Mac clients, PowerPC or Intel Processor SOFTWARE 128 MB RAM (512 MB required for network disaster recovery). 1 GB for Mac OS. 100 MB free disk space (1 GB recommended) Network connection (LAN, modem, WAN, and wireless are supported) Operating systems-full Protection Windows XP Professional or Home Edition 32-bit Windows Vista SP2 32- or 64-bit Windows 7 Professional, Enterprise, or Ultimate, 32 bit or 64-bit Operating systems Document protection only Windows Server 2003 Service Pack 2, 32-bit Standard or 64-bit Enterprise editions (see Windows Server Protection notes, below) Windows Server 2008 R2, Standard or Enterprise editions (see Windows Server Protection notes, below) Mac OS X (Tiger) 32-bit 7

14 . Mac OS X 10.5.x (Leopard) 32-bit Mac OS X (Snow Leopard) 32- or 64-bit Microsoft Internet Explorer 6.0 or later for Windows clients TCP/IP for Windows clients Windows Installer 2.0 (included) for Windows clients Local administrative privileges for installation only Windows Server Protection notes * T he total number of files protected on one Windows Server must not exceed two million. *The total protected file size must not exceed 250 GB. * Live Backup supports only individual file protection on servers; protection of server applications/services that require mutual consistency such as databases, directories, etc. is not certified. Full system protection is not supported. CLIENT READINESS Make sure all clients are ready for the Live Backup installation: PERFORM VIRUS SCAN All clients should be free of viruses before installing Live Backup Client (or any other software). Run a virus scan on your client computers to make sure they are clean, eliminating any viruses you find. CHECK DISK SPACE Make sure each client computer has adequate disk space to install both Live Backup Client and its cache files. Live Backup caches files in a local client folder temporarily, until it detects both a connection to the server and adequate network bandwidth to transfer backup files to the Live Backup Server. A minimum of 50 MB of free disk space is required for the drive where you will install Live Backup Client. On the cache drive, you should have free disk space equal to twice the size of the largest file to be protected plus 3% of the total disk size. For example, if your largest file is 1 GB and you have a 50 GB cache drive, then you should have disk space equal to (1 GB * 2) + (50GB *.03)=3.5 GB. ANALYZE POTENTIAL SOFTWARE CONFLICTS For information on certified applications and potential compatibility conflicts, check the Live Backup Compatibility guide at Backup/compatibility.asp. 8

15 3 Determining server requirements Live Backup Server s requirements are based directly on the requirements of the Live Backup Clients to be protected. The number and location of clients, type of protection, and amount of data on each client all directly affect the requirements of the Live Backup Server. This chapter includes information based on statistics gathered from existing deployments of Live Backup in different environments. This information is based on the sum of the aggregate daily volume of backup data over the expected population of clients, and then maps that sum to the backend throughput required, and hence the CPU, memory, and disk required., The only way to obtain accurate information for your deployment is to measure the actual data traffic between the protected client computers and the Live Backup Server. The traffic varies greatly from site to site. The following information should be used as an initial estimate only. You can find examples of how to apply this information at the end of this chapter. To estimate Live Backup Server requirements in any given environment, you must complete the following steps: 1. Make sure your server meets the minimum software requirements 2. Determine the required storage space, including Volume of protected data SQL Server requirements System database requirements Archiving requirements Number of server computers 3. Consider the network architecture and server throughput, including Network connectivity Network impact expectations Server throughput 9

16 . 4. Determine disk requirements 5. Determine the CPU/MEM/SQL requirement This chapter details information on each of these steps. LIVE BACKUP SERVER MINIMUM SOFTWARE REQUIREMENTS This section lists the minimum requirements for Live Backup Server software. SOFTWARE REQUIREMENTS FOR LIVE BACKUP SERVER Operating Systems o Windows Server with Service Pack 2: Note that the Active Server Pages feature of the World Wide Web Service must also be installed. For details on how to install the Active Server Pages feature of the World Wide Web Service, see the Knowledge Base: o Windows Server 2008, o Windows Server 2008 R2 IIS 6.0 for Windows Server 2003 or IIS 7.0 for Windows Server 2008, 32-bit. Note that the IIS World Wide Web Publishing Service must be started and set to Automatic Startup..NET Framework 3.5, SP1. Live Backup installs for you for all operating systems except Windows Server 2008 R2. For instructions on installing in Windows Server 2008 R2, see the Live Backup Installation and Setup Guide. TCP/IP Internet Explorer 6.0 or higher Microsoft SQL Server 2000 Standard Edition with Service Pack 3a 2, Microsoft SQL Server 2005, Microsoft SQL Server 2008, or 2008 R2, 32- or 64-bit editions Windows Installer 2.0 (included) 1 Windows Server 2003 Web Edition is not supported. 2 SQL 2005 and 2008 Standard, Enterprise, Developer, or Workgroup editions supported. SQL Server 2005 Express edition not supported. SQL 2000 Standard and Enterprise Editions supported; SQL 2000 Personal Edition and Desktop Engine (MSDE 2000) not supported. During evaluation, you may use SQL 2005 or 2000 Evaluation Edition; however, the evaluation edition supports only Service Pack 3a, which you can download from the following site: Note that Service Pack 3a is required for full functionality of Live Backup during an evaluation. 10

17 SOFTWARE REQUIREMENTS FOR LIVE BACKUP CONSOLE Either Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows XP Professional, Windows Vista, or Windows or 64-bit edition. Internet Explorer 6.0 or higher MMC HTML Help update (for help viewing, included) Computer membership in the Windows domain or trusted domain of the Live Backup Server (required for remote administration) Administrator privileges on the Live Backup Server computer and the local computer Windows Installer 2.0 (included) SERVER STORAGE SPACE To determine the total storage required on the Live Backup Server, you must consider the following factors: Temporary space for installation Storage for client data Storage for SQL Server Storage for Live Backup system databases Disk space for archiving Number of server computers TEMPORARY SPACE FOR INSTALLATION The installation program requires 645 MB of free disk space on the Windows installation drive to store temporary files. Most of this disk space will be freed when installation completes; the remaining 93 will be used to store uninstall information. CLIENT DATA To determine the total storage required for the Live Backup Server, gather the following information: The total number of clients The type of protection: Full or User Document only How much data is on the client computers 11

18 . HOW MANY CLIENTS Gather an exact count of the client computers that Live Backup will protect. For ease of deployment, you may want to gather this information by department or location, which you can then later use to group the clients. The amount of storage required is directly based on the number of clients that you have. TYPES OF PROTECTION The type of protection you provide each client PC in your organization will determine the recovery features available to those clients as well as the total disk space required for protection. There are two basic types of protection offered by Live Backup: Full Protection and User Document Protection, each of which may be customized to suit your particular corporation s needs. Different types of protection are also more suited to the different types of computers, specifically desktop workstations and mobile laptops. You may choose to group clients based on the type of protection you choose, as described below. Full Protection: Full Protection protects the client computer s entire system, including Windows, application, program, system data, and user document files. Obviously, this type of protection requires the most disk space for storage, but it provides the most complete protection as well. Live Backup System Rollback and Disaster Recovery are available only to clients with Full Protection enabled. User Document Protection: User Document Protection protects only those files that the user creates. User Documents are defined as files located in the My Documents folder, Office documents, audio-video files, boxes, graphics files, application development files, compressed files, and text documents. In addition, you may define any file type as a user document. Although this type of protection does not provide complete coverage, eliminating the availability of Disaster Recovery and System Rollback, it requires the least disk space. Therefore clients with a standard operating system and generic applications, but limited free disk space are good candidates for this type of protection. Note: Live Backup Express supports user document protection only. SIZE OF THE DATA ON EACH CLIENT Finally, to determine the required storage space, you must estimate the volume of protected data. This volume is defined as the sum of all data that you want to protect on all client computers. 12

19 You can then compute the required server storage space. The required storage is defined as a linear function of the protected data size: Required Storage = Protected Data * k where k is a constant that depends on protected computers, sites, and the mode of protection. The mean value of k is between 0.5 and 1.0. The weighted average value of k depends on the protection mode: User document protection: k=0.9. Full system protection: k= 0.8. Warning :This formula is based on the size of protected storage. When sizing the required storage space, be mindful that the total protected storage usually grows quickly. Note that the required storage is also dependent on Live Backup s methods of redundancy elimination. For more information on how redundancy elimination works, and for tips on how to best configure it for your deployment, see the document Live Backup Redundancy Elimination. SQL SERVER On the SQL home disk where SQL s MasterDB, Temp, and other internal databases are located, there should be free disk space roughly equal to the largest protected client. LIVE BACKUP SYSTEM DATABASES In addition to the client databases, which you allocated space for in the section on client data, you must allocate space for the Live Backup system databases. For the system databases, make sure to reserve space roughly equal to the size of the largest protected file. NUMBER OF SERVER COMPUTERS The number of server computers required is based on the expected throughput, therefore, distributing clients across multiple servers provides you with the following benefits: Distribution of network bandwidth usage Lower hardware and storage requirements per server If you are planning a deployment for 1,000 or more clients, contact Atempo Support for further guidance on configuring server hardware. 13

20 . NETWORK ARCHITECTURE Live Backup transmits data between the server and the client using HTTP over any type of network connection. This section discusses the different types of network connections as well as the impact you can expect during initial replication and normal operation. NOTE Live Backup is compatible with all domain configurations. Although you can install Live Backup Server on a domain controller, you should not promote the server to a domain controller after Live Backup Server has already been installed. NETWORK CONNECTIVITY Live Backup supports client/server connections through dial-up, broadband, and LAN connections. DIAL-UP CONNECTIONS Although you can use standard dial-up connections from remote users, they are recommended only for small amounts of data transfer. Ideally, only clients configured for User Document Only protection with files no larger than 2 MB would use dial-ups. BROADBAND CONNECTIONS For remote users, broadband connections provide markedly better performance than dialup. However, keep in mind that the upstream bandwidth, which is usually the lower figure for home broadband connections, will be the determining factor. This factor is most pronounced with cable modems. LOCAL AREA NETWORK (LAN) CONNECTIONS As expected, LAN connections offer the fastest data transfer and are recommended whenever possible, particularly during the initial replication of a Live Backup Client. NOTE In most cases, the server acts as a natural limiter on bandwidth usage. NETWORK IMPACT EXPECTATIONS The data transfer between client and server should be negligible during normal operation. Normal operation is defined as post-deployment activity level. This can be attributed to two important aspects inherent in Live Backup: Random distribution of trigger events. In Live Backup s real-time system, the event that triggers backup activity for any particular client is actual disk I/O ostensibly, this maps to end-user activity on the client PC. Such events are almost never synchronous across a wide sample of clients, so that very rarely are many Live Backup clients actively communicating with the server at a given time. Delta-block elimination. Statistically speaking, the amount of data that changes prior to a user-initiated save operation is small relative to the total size of the file/dataset. Therefore, you can expect that the actual volume of data associated 14

21 with a trigger event will be sufficiently small that it will not introduce significant network load. SERVER THROUGHPUT The daily network traffic per client usually varies from 40 to 250 MB depending on the level of activity on the machine computer. The weighted average of daily traffic depends on the mode of protection: User Document Only (Express): 50 MB/day Full System Protection: 100 MB/day This statistical data shows how much average daily throughput is required per client. The total throughput that the server will be required to support depends on: the number of clients and their protection mode the connection time to the server For example: Given 700 clients with full system protection and an average daily change of 250 MB, the total daily traffic will be 250*700 = MB. Considering an 8 hour (28800 sec) daily connection, the required throughput will be MB /28800 s = 6.08 MB/s. With a client connection of 24 hours a day, the required throughput would be MB / 86400s = 2.02 MB/s Note: The average traffic per client ranges from 2 to 10 KB/s with a weighted average between 3 and 4 KB/s. 15

22 . DISK REQUIREMENTS When determining disk requirements, note that Live Backup manages data in small blocks to optimize network traffic and redundancy elimination. These small blocks require a significant amount of CPU, as well as a disk configuration that handles small and random IO calls. With this in mind, note that the standard disk performance advertised by manufacturers do not apply to a Live Backup Server, because these statistics are usually based on raw disk performance in sequential mode and in the best conditions not the conditions under which Live Backup operates. As a rule, you can expect up to 2 to 3 MB/s of inbound network traffic per RAID 5 set. When a higher throughput is required, then you should create several RAID-5 arrays using different physical disks. The less sophisticated way of taking advantage of these RAID-5 arrays is to distribute the client databases across them. A much more flexible way is to create a stripe volume (RAID-0) composed of RAID-5 arrays. This can be achieved either by logical means (software RAID) or by hardware configuration (RAID-50). Note: You can approximate a particular configuration using disk performance tools such as IOmeter. For more information and correct parameters, contact Customer Support. CPU/MEM/SQL REQUIREMENT Now that you have determined the required server storage, average data throughput, and disk requirements, you can determine the server requirements. The table below shows the server configuration required for a given sustained throughput. Required Server Throughput Recommended Memory Recommended SQL edition Number of SQL CPU license(s) Recommended number of CPUs (>2GHz) Up to 0.5 MB/s 4GB Workgroup 1 1 CPU Up to 1 MB/s 8GB Workgroup 1 1 CPU Up to 2 MB/s 8GB Standard 1 2 CPU Up to 4 MB/s 8GB Standard 1 2 CPU Up to 6 MB/s 8GB Standard 2 4 CPU Up to 8 MB/s 16GB Standard 2 4 CPU Note: In the table above, ignore hyperthreading: consider a processor using hyperthreading technology as one processor, not two. 16

23 EXAMPLES The following examples show how to apply the information provided above. In a real world situation, you must account for both the increase in storage growth over time as well as changes to throughput when protected computers are added or removed. EXAMPLE 1: MIXED PROTECTION; 24 HOUR CONNECTION Consider the following customer deployment: # of clients Protection mode Protected data (GB) 10 Full Full User document User document 2 The clients are always connected to the server (24 hours/day) Here are the steps for the configuration: 1. Determine the required storage Full protection: The overall protected storage in full protection mode will be: (10 clients *20GB) + (30 clients *10 GB) = 500 GB The storage needed for clients in full protection mode will be: 500 GB * 0.8 = 400GB. User document protection The overall protected storage in user document mode will be: (50 clients * 5GB) +(100 clients * 2 GB) = 450 GB. The storage needed for clients in user document mode will be: 450 GB * 0.9 = 405 GB. Total storage The required server storage will be 400GB+405GB = 805GB 17

24 . 2. Required throughput The best way to determine the average daily change is to prototype. In absence of real data, an estimate can be made based on the above statistical data. Assuming 100MB/day for full protection and 50 MB/day for user document protection, you have: Full protection The daily change generated by the clients in full protection mode will be: (10+30)*100MB/day = 4000 MB User document protection The daily changes generated by the clients in user document mode will be: (50+100)*50MB/day = 7500 MB Total change The total estimate for daily changes is = MB If the clients are always connected to the server and never switched off then the transfer windows will be 24 hours (86400 seconds). Required server throughput 11500/86400 = MB/s 3. Disk configuration A single RAID-5 configuration 4. Server configuration Following the server configuration table, under 0.5 MB/s we will have: 1 CPU 2GB memory SQL2005 workgroup edition 18

25 EXAMPLE 2: FULL PROTECTION, PARTIAL CONNECTION Consider the following customer deployment: # of clients Protection mode Protected data (GB) 700 Full 8 The clients are connected to the server during standard working hours: 8 hours/day The average daily change of data is 250 MB/day. Here are the steps for the configuration: 1. Required storage The required server storage will be (700 clients * 8 GB) * 0.8 = 4480 GB (~ 4.5 TB) 2. Required throughput Given an average daily change of 250 MB, the total daily change will be 700 clients * 250 MB = MB Considering a 8 hours daily connection will give seconds. The required throughput will be /28800 = 6.08 MB/s. 3. Disk configuration To support the 6 MB/s required throughput, configure three RAID 5 sets. To achieve the global space requirement of 4.5 TB, set up each RAID 5 as a set of six 300 GB disks yielding an available storage for each RAID-5 of (5 * 300) * 3 = 4.5 TB Then define a RAID-0 configuration on top of the 3 RAID-5, and thus meet the required throughput (for example define hardware RAID-50). 4. Server configuration Following the server configuration table, for a 6 MB/s we will have: 4 CPU 6 GB memory SQL 2005 standard edition 2 CPU license for SQL

26 . 4 Initial replication considerations OVERVIEW Live Backup provides centralized storage management and administration of distributed data on desktop and laptop workstations throughout the enterprise. To provide this protection, Live Backup must make sure a copy of every required file from each protected client exists on the Live Backup Server. Required client files include all Windows system files, application files, and user document files such as Microsoft Office documents. These files are required for a full system recovery, should one ever be necessary. For the first client installations, this means that virtually every file, with the exception of temporary files and other discardable data is backed up to the server. This process is called the initial replication. But once a Windows system file or application file (by default), is copied to the server, it will never be copied again. Rather, a pointer to the backed up file will be saved. This process is called redundancy elimination or data de-duplication. Therefore, for subsequent client installations, less data will be transferred to the server, as more data will be eligible for block and file redundancy elimination. See Also: For more information about redundancy elimination, see the document Live Backup Redundancy Elimination (PDF). The initial replication of client data is the most resource intensive step in the Live Backup protection process in terms of network bandwidth, client, and server hits. After the initial replication, the network and system usage decreases significantly. Since the Live Backup Server limits replication based on its capabilities, the effective rate at which a workstation will replicate depends on the number of workstations replicating simultaneously. Consider the performance implications for your network and for your users if the initial replication is invoked by all workstations simultaneously. Clearly, you must carefully plan, execute, and monitor Live Backup Client deployment according to your production schedules, network configurations, and user demographics. To help plan client replication, you can create clients automatically, and then specify the time when they will begin replication: immediately following creation, at a specific time, in a specific number of hours, or not until you manually launch replication. 20

27 DEPLOYMENT TIPS FOR EASE OF REPLICATION The manner in which you deploy Live Backup Clients is going to have a significant effect on the replication time, performance, and network saturation. Consider the following tips and tricks to help plan for a smooth and successful replication. DEPLOYMENT METHODS AND AUTO-CREATION Live Backup supports five methods for deploying Live Backup Client. It supports a manual create as well as an auto-create option for client accounts. For large deployments, the client and group autocreation options are highly recommended. You should review the methods of deployment and choose the best one now, before you begin any installation. For details on deployment methods and how to choose the best one for you, see Deploy the clients on page 55. SEED YOUR DATABASE Seed your database with common files first, before launching replication of a large group of clients. The replication of the first 10 clients or so is the slowest because Live Backup cannot yet take advantage of the shared database or redundancy elimination. To help the performance of the remainder of the replication, it is recommended that you create an initial group for replication that contains sample clients. Make sure that your group represents clients with all versions of Windows that you plan to protect. Then add as many applications to these sample clients as possible. Once the clients are configured, replicate those computers locally. By keeping a large number of applications and operating systems in the shared database, you ensure that each client will not need to replicate their operating system and application files to the Live Backup Server. GROUPS Group your clients! Live Backup provides powerful client grouping tools. For each group that you create (or auto-create), you can configure protection settings including level of protection, discardable data, custom user document types, storage, data aging, feature lockdown, and expiration dates. These settings apply to every member of your group. Therefore, it is logical to group clients by the protection settings you want applied. For more information on protection properties, see Determine protection properties on page 47. It is also reasonable to group clients by location. Client computers in a similar location tend to belong to the same departments, and have similar protection requirements. By grouping according to location, it will be easier for you to track and schedule deployments. You can also delegate administration of groups to IT staff at each location. Live Backup enables you to create nested groups to build a hierarchy that corresponds to any department structure. When you group clients, you should determine the best group size. We recommend starting with 10 clients, and then modifying that number up or down depending on performance. If you find that 10 21

28 . clients are taking 24 hours to replicate, you may want to adjust it down to 5. Likewise, if 10 clients are replicating in 2 hours, you may want to increase it to 20. It is impossible for Atempo to predict the replication rates you will receive on a per client basis, since the rate is related directly to the amount and type of data in your company, as well as the hardware and network connections available. Finally, we strongly recommend that you take advantage of Live Backup s scheduled replication feature. This feature enables you to schedule when you want replication to begin for each group. You can create all groups, and then schedule their replication to occur on off hours. You can also stagger the replication, launching the replication of group 1 on Monday at Midnight, group 2 on Tuesday at Midnight, group 3 on Wednesday, and so on. For more information on scheduled replication, see Automatic client creation on page 42. DISK SPACE To lower the disk space used on client computers during caching on the Live Backup Client computer, set the Cache Space Usage setting in the Control Center to the minimum. REPLICATION RATE If replication is slow, you may be able to improve rates by modifying the TCP/IP settings on the Live Backup Server. This process is described in the following Knowledge Base article: 22

29 5 Installing the Live Backup Server After you have analyzed client requirements, determined server requirements, and configured and planned appropriately for the ensuing replication, you can begin your deployment of Live Backup with installation of the server software. This section assumes that you have installed and properly configured Windows Server 2003 on the target system. You should make sure that this server is set up with TCP/IP and 32-bit IIS support. The remainder of this section describes: Microsoft SQL Server installation Live Backup Server installation Post installation checks SEE ALSO The Atempo Live Backup Quick Install card and the Live Backup Installation and Setup Guide, both available within the /DOCs folder of the Live Backup software or downloadable from the Web site. MICROSOFT SQL SERVER SETUP You must install Microsoft SQL Server 2008, 2005, or 2000 prior to installing Live Backup Server. If you choose to use SQL Server 2000, then after installation, you must apply SQL Server 2000 Service Pack 3a, before installing a production version of Live Backup. SQL Server Service Pack 3a provides support for multiple CPU's, which is required for Live Backup's data aging process. IMPORTANT NOTES Before and during the installation of SQL Server, please keep the following important points in mind: SQL Server 2005, 2008, and 2008 R2 32-and 64-bit editions are supported. 23

30 . SQL Server 2008 and 2008 R2 are supported only on Windows Server 2008 and Windows Server 2008 R2 When you install SQL Server2000 Service Pack 3a, you must enable Crossdatabase ownership chaining. If it is disabled, Live Backup will not function properly. For tips on a successful upgrade to SQL Server Service Pack 3(a) on the Live Backup Server computer, see the Knowledge Base at Make sure that databases are not set up on compressed disks or directories with NTFS compression or third-party software compression. This configuration will cause Live Backup to fail. After installation, make sure that Microsoft SQL Server's Use Windows NT fibers option is disabled. Live Backup supports both SQL Server Standard and Enterprise editions. If you are installing Live Backup on a dual-processor system, then Microsoft requires the Enterprise edition. For recommendations on which edition of SQL Server to use with Live Backup, see CPU/MEM/SQL Requirements on page 16. SEE ALSO Microsoft SQL Server Introduction guide and Microsoft SQL Server online help, as well as the Microsoft SQL Server Web site at INSTALLING SQL SERVER When you install SQL server 2008 or 2005, consider the installation instructions below. Specific configuration is required for Live Backup Server functionality. INSTALL SQL SERVER 2008 Microsoft SQL Server is required for Live Backup. Following are instructions for installing Microsoft SQL Server 2008 for proper functionality with Live Backup Server, including instructions for installing the SQL Server 2005 Backward Compatibility Components. Live Backup Supports SQL Server 2008 only on Windows Server 2008 operating systems. Note that if you are upgrading an existing Live Backup Server from Microsoft SQL Server 2005 to 2008, there is a special procedure to follow within Live Backup. See Upgrading Microsoft SQL Server. Make sure to install Service Packs as instructed during the Microsoft SQL Server installation. Important Make sure that databases are not set up on compressed disks or directories with NTFS compression or third-party software compression. This configuration is not supported by Microsoft SQL Server and will cause many 24

31 Live Backup functions such as creating clients to fail. For more information, see SQL Server 2000 Administrator's Pocket Consultant: Core Database Administration at c04ppcsq.mspx. Note Consider enabling the AWE option in SQL Server when LiveBackup Server is installed on a 32-bit operating system. This option enables SQL Server to use more than 2 GBs of memory, as available. If AWE is disabled, then SQL Server is limited to 2 GB of memory. If you choose to enable AWE, then we recommend that you follow Microsoft's guideline on setting the Max Server Memory option. For more information on AWE and other SQL Server options, see your Microsoft SQL Server documentation 1. On the computer where you plan to install Live Backup Server, insert the Microsoft SQL Server installation disc. The Microsoft SQL Server installation begins. 2. Follow the instructions on your screen. 3. On the SQL Server Installation Center page, click Installation tab, and then click New SQL Server stand-alone installation or add features to an existing installation. 4. During the installation, make sure you select the following options: On the Features Selection page, make sure to choose o Instance Features: Database Engine Services (clear SQL Server Replication and Full Text Search); 25

32 . o Shared Features: SQL Server books online, Management Tools - Basic; Management tools - complete, and Client Tools Connectivity. On the Instance Name page, choose the Default instance of SQL Server (not a named instance). On the Server Configuration page, choose Use the same account for all SQL Server services, then choose the account NT Authority\System. Then click OK. On the same page, select the startup type Automatic for SQL Server Agent and SQL Server Database Engine. The SQL Server Browser Service is not required. On the page, click the Collation Settings tab. Under Database Engine, click Customize, and then choose the Windows collation designator and sort order option, and select Latin1_General from the drop down list. On the same page, select the Binary check box. On the Database Engine Configuration page, choose Windows Authentication mode. To specify the current user as the SQL Server administrators, click Add Current User; otherwise, click Add to specify any other user as the administrator. 5. Allow installation to complete. 6. After installation completes, install SQL Server 2005 Backward Compatibility Components: run SQLServer2005_BC.msi available on SQL Server installation media in the following folder: SQL Server 2008: o o 32-bit: \\x86\setup\x86 64-bit: \\x64\setup\x64 SQL Server 2008 R2: 32-bit: \\1033_ENU_LP\x86\Setup\x86 64-bit: \\\1033_ENU_LP\x86\Setup\x64 7. Make sure that the SQL Distributed Management Objects (SQL-DMO) option is selected, and then allow installation to complete. INSTALL SQL SERVER On the computer where you plan to install Live Backup Server, insert the Microsoft SQL Server installation disc. 26

33 The Microsoft SQL Server installation begins. 2. Follow the instructions on your screen. You will need to insert the Microsoft SQL Server media. 3. During the installation, make sure you select the following options: On the Components to install page, make sure to choose SQL Server Database Services and Workstation Components, Books Online and development tools. On the Instance Name page, choose the Default instance of SQL Server (not a named instance). On the Service Account page, choose Use the built-in System account: Local System (recommended). Then... On the same page, Start services at the end of setup: SQL Server and SQL Server Agent. On the Authentication page, choose Windows Authentication. On the Collation Settings page, choose the Collation designator and sort order option, and select Latin1_General from the drop down list. On the same page, select the Binary check box (recommended). 4. Make sure to install Service Packs as prompted. 5. Allow installation to complete. CONFIGURING MICROSOFT SQL SERVER After installing SQL Server and all Service Packs, you can tune SQL Server to achieve the best performance with Live Backup. This section describes the following best practices: Processor configuration Disks and drives Database configuration SQL services SQL user account setup 27