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

34 . PROCESSOR CONFIGURATION If you have a single processor system, you can install Microsoft SQL Server Standard Edition. This version of SQL Server is included with the Live Backup Product CD-ROM set. If you have a multiprocessor system, you must use SQL Server Enterprise Edition, unless you dedicate only one processor to SQL Server. Contact Microsoft about obtaining this version. If you have a multi-processor system, then we recommend that you configure Microsoft SQL Server to use 1 processor for parallel execution of queries. To do so, 1. Run Enterprise Manager. 2. Expand Microsoft SQL Servers, then SQL Server Group. 3. Right-click the SQL Server name, and then click Properties. 4. Click the Processor tab. 5. Under Parallelism, click the Use option, and then from the processor(s) drop-down list, select Click OK, and close Enterprise Manager. DISKS AND DRIVES You can improve the performance of SQL Server, and in turn, of Live Backup Server by configuring the type of disks and storage used specifically for Live Backup. First, it is recommended that you install the following on four separate dedicated physical drives: Windows with its pagefile 28

35 SQL Server Live Backup Server s system databases Several arrays for user databases. For more information, see Server throughput on page 15. Note Live Backup does not support Network Attached Storage. This configuration is also prohibited unless specifically approved by Microsoft for SQL Server database use. DATABASE DRIVE RAID 10 hardware arrays yield the best performance for storing database files (*.mdf, *.ndf, and *.ldf). Distribute physical disks across the available arrays: the more arrays, the better the performance. Also make sure that you do not set up databases on compressed disks or directories with either NTFS compression or any other third-party software compression program. This configuration will cause Live Backup to fail. DATABASE CONFIGURATION You can improve database performance by configuring the location of the Live Backup database and the Windows application response. When you install Live Backup Server, Live Backup creates a SQL database for storing all shared files. During the installation, you can configure the location of the database. Make sure that SQL s tempdb is on a different physical volume than the Live Backup database. You can also improve SQL Server database performance by configuring Windows system performance options to optimize for background services. This configuration enables SQL Server, a background application, to run at equal priority to other applications running in the foreground. You can set this option under System Properties in the Control Panel. SQL SERVICES Consider configuring SQL services as follows. For best performance, do not install any SQL Server services that you don t need. The following services are not required by Live Backup and will only add unnecessary overhead to the server: Do not install o o Microsoft Search OLAP 29

36 . Optional o English Query Services If your applications are not using the following service, set it to manual under Services in the Control Panel. o Microsoft Distributed Transaction Coordinator (MS DTC) Required Finally, after installation, make sure that the following SQL services are set to AutoStart mode, as they are required for full Live Backup functionality: o o MSSQLServer SQLServerAgent SQL USER ACCOUNT SETUP Live Backup recommends thatyou use the local system account. SQL SERVER SHUT DOWN TIME By default, SQL Server is allocates 20 seconds to shut down completely when you restart Windows. During this shut down time, SQL Server must write all changes to disk. If it cannot finish this task in the time provided, it then recovers its databases during the next startup. The database recovery occurs in a random order and therefore may disrupt Live Backup startup activity. This problem occurs most frequently with large (500+ clients) deployments. If you notice a disruption in Live Backup startup, you can increase the SQL Server shut down time. This issue is described in detail in the following Knowledge Base article: SERVICE PACKS If you use Microsoft SQL Server 2000, then Live Backup requires SQL Service Pack 3a. Before you install Service Pack 3a, make sure you stop IIS. Then during installation, you must enable Cross-database ownership chaining. If it is disabled, Live Backup will not function properly. For more tips on a successful upgrade to SQL Server Service Pack 3(a) on the Live Backup Server computer, see Finally, After installation, make sure that Microsoft SQL Server's Use Windows NT fibers option is disabled. 30

37 INSTALLING LIVE BACKUP SERVER You can now install Live Backup Server. This installation procedure will install the following components: Live Backup Console: This Microsoft Management Console (MMC) snap-in enables you to manage clients, change disk space usage quotas, configure protection settings, lock down features on a per-user and/or per-client basis, and generate system recovery images for disaster protection. Live Backup Server: This component receives data from clients and stores it in a Microsoft SQL Server database. It also transmits files back to the clients upon a file, folder, or system recovery request. This installation includes an evaluation license good for five Windows clients, five Mac clients, and 5 Small Server clients. This evaluation license enables file and system recovery for only 30 days. Although protection will continue after the 30 days have expired, you will not be able to recover client files without a valid license code. You will be reminded of this expired state every time you start Live Backup Console and any time you attempt to create clients or access recovery features. To obtain a valid license code, contact Atempo. Upon upgrading to the full version, you will receive instructions for unlocking Live Backup recovery features. For more information on entering a permanent license key, see Chapter 5 in the Live Backup Administrator's Companion Guide. BEFORE YOU INSTALL Before you install, perform the following last minute checks: Make sure the default SQL Server instance is not, and has not, been shared by another application. If you are running Microsoft SQL Server 2000, then enable cross-database chaining with Microsoft SQL Server SP3a. Make sure 32-bit IIS is installed before installing Live Backup. You must install on Microsoft Windows Server 2003, 2008, or 2008 R2. TO INSTALL LIVE BACKUP SERVER 1. Login to the server using a domain account that has local administrative privileges. 2. Insert the Live Backup Disc 1 CD-ROM into your CD-ROM drive. 31

38 . The Welcome to the Live Backup Installation Wizard screen appears. 3. Click Next. The Select Component Type screen appears. 4. Select Install Live Backup components, and then click Next. The Install Live Backup screen appears. 5. Click Install Live Backup Server. The Prerequisites Check screen appears. 6. Make sure all prerequisites are installed, and then click Next. The Live Backup Server installation begins. 7. Read the Welcome screen and click Next. The Select your Location page appears. 8. From the Location list, choose the country in which your company is located. The License Agreement screen appears. 9. In the License Agreement screen that appears, select I accept the terms in the license agreement, and then click Next. The Custom Setup screen appears. 10. Select the Live Backup Server components that you want to install. Click the down arrow beside a component name, and choose how you want to install: To install the selected component to the local hard drive, select This feature will be installed on local hard drive. If you are modifying the installation, and this feature was installed previously, then this selection does nothing. If you are repairing the installation, this selection reinstalls the feature. If you don't want to install a particular feature, or if you want to uninstall an existing feature during a modify or repair, then select This feature will not be available. To change the folder location where any Live Backup component will be installed, click the component name, and then click Change. In the Change folder dialog box, select a new location, and then click OK. 32

39 Click Next. The Destination Folder screen appears. 11. Choose the location where you want to store Live Backup system database files. By default, these files are saved in an LBDATA folder on the local drive with the most free disk space. To change this location, click Change, and select a path. Click Next. 12. In the Ready to Install the Program screen, click Install. A progress screen appears as Live Backup Server is installed onto your computer. 13. If.NET Framework 3.5 SP1 is not installed on the server computer, a message appears. To install it now, click Install on the message window. When the installation is complete, The InstallShield Wizard Completed screen appears. 14. Click Finish. 15. The Live Backup for Mac - Windows Service installation now begins. Click Next, and then on the Ready to Install page, click Install. POST INSTALLATION CHECKS During installation of Live Backup Server, several Windows components are configured for use with Live Backup Server. This section describes that configuration and how to verify that it completed properly. It covers IIS configuration Live Backup Server user account 33

40 . IIS CONFIGURATION Live Backup configures IIS for running its Web-based utilities. The configuration is different for IIS 6, which is part of Windows Server 2003, and IIS 7, which is part of Windows Server IIS 6 1. Run Internet Information Services Manager as follows: Click Start, point to Programs, and then point to Administrative Tools. Click Internet Services Manager. 2. Expand servername. 3. Expand Default Web Site. 4. Verify that the following Virtual Directory was created: WLB 5. Verify the properties of the WLB folder: Virtual Directory tab Local path: % Live BackupServerInstallationPath%\WLB Access flags under Local path: Select Read, but clear all others Application name: Blank Execute permissions: Scripts only Application protection: Low (IIS Process) Directory Security page\edit Anonymous access: enabled Integrated Windows authentication: enabled Authentication Methods\Edit User name: [DOMAINNAME]\LBU_[COMPUTERNAME] Allow IIS to control password: enabled 6. Make sure that the Default Web Site is started. 7. Exit Internet Information Services Manager. 34

41 IIS 7-WINDOWS SERVER Run Internet Services Manager as follows: 2. Click Start, point to Programs, and then point to Administrative Tools. Click Internet Services Manager. 3. Expand servername. 4. Expand Default Web Site. 5. Verify that the following Virtual Directory was created: WLB 6. Under Actions, click Edit Permissions. Click the Sharing tab: WLB is not shared. Click the Security tab, and then under Group or user names, select Creator Owner, and then click Edit. Special permissions are allowed. All other permissions cleared. Click OK. Back on the Security page, click Advanced.Check the following options: o o o o o TrustedInstaller: Special permissions System: Full control Administrators: Full control Users: Read and execute Creator owner: Special permissions Click OK. Click OK to close the WLB Properties dialog box. 7. Under Actions, click Basic Settings. Check the following options: o Site name: Default Web site o Path: / o Alias: WLB 35

42 o o o. Application pool: DefaultAppPool Physical path: %Live BackupServerInstallationPath%\WLB Pass-through authentication 7. Under Actions, click Advanced Settings. The Advanced Settings should be identical to the Basic Settings, with the addition of the Enabled Protocol: http. Make sure that the Default Web Site is started. Exit Internet Services Manager. IIS 7-WINDOWS SERVER 2008 R2 1. Start the Server Manager by clicking the Server Manager icon on the Quick Launch toolbar or by clicking Start, Administrative Tools, Server Manager. 2. In the left pane, expand Server Manager, and then click Features. 3. Under Feature Summary in the right pane, click Add Features. The Add Features Wizard appears. 4. In the Features list, expand Remote Server Administration Tools, then expand Role Administration Tools, and then select the Web Server (IIS) Tools check box. Click Next. 5. Click Install, and then allow installation to complete. 6. In Server Manager, select the Roles node in the left pane, and then under Roles Summary, click Add Roles. 7. In the Add Roles Wizard Welcome page, click Next. 8. On the Select Server Roles page, select the Web Server (IIS) role. Click Next. 9. Review the information under Introduction to Web Server (IIS), and then click Next. 10. The Add Features Required For Web Server page, which lists the features that are required to install a Web server appears. Click Add Required Features to close the dialog box and add the Windows Activation Service components to the Web server installation. Click Next twice to continue. On the Select Role Services page, add the following role services to those selected by default: Under Web Management Tools, select IIS 6.0 Management Compatibility, including all subservices. Under Application Development Features, select ASP. Also under Application Development Features, make sure that ASP.NET is selected. Under Security Features, select Windows Authentication. 36

43 Click Next. 11. On the Confirm Installation Options page, click Install. 12. When Setup finishes installing the application server with the features you ve selected, you ll see the Installation Results page. Review the installation details to ensure that all phases of the installation completed successfully. For more information on IIS 7.0 Configuration, see the Microsoft Web site Deploying IIS 7.0 in the Enterprise at USER ACCOUNTS During installation, Live Backup adds the user account LBU_servername to the local SAM. This local account is used for anonymous access from the Web and is required for proper functionality of the Live Backup Server. Depending on your server configuration, this account may expire automatically after a certain number of days. To prevent expiration, go to the Users section under Windows Computer Management or Windows Active Directory Users and Computers and make sure that the Password Never Expires option is selected for this account. 37

44 . 6 Configuring Live Backup Server After the Live Backup Server is installed, you can begin creating and setting up the groups in which you want to create client accounts, planning client account creation, and then installing Live Backup Client on computer systems that Live Backup protects. Each computer protected by Live Backup must have an account on the Live Backup Server. Adding the client accounts enables Live Backup to recognize the client computers and collect their data, track the changes, and store their files once Live Backup Client software is installed on the workstation or laptop computer. You can add client accounts manually or automatically. You can also group clients to enable the power and flexibility of protection property inheritance. Each client account created within a group inherits the properties of the group by default. Later, if you choose, you can turn off the inheritance and customize protection properties for each client account individually. You may also create groups manually or automatically. Each individual client account and group is identified by a group hierarchy, with a full compound name of [email protected]. By identifying client accounts using their full compound name, Live Backup enables you to give client accounts the same name as long as they are located in different groups. This chapter describes how to Decide between manual and automatic client account creation Configure and create groups and client accounts manually Configure and create groups and client accounts automatically Determine the appropriate protection settings and properties 38

45 MANUAL VS. AUTOMATIC CLIENT ACCOUNT CREATION Live Backup enables you to create client accounts and groups manually or automatically. In manual creation, you create each client account individually in the Live Backup Console and configure its settings either individually or based on its group membership. Once you install Live Backup Client on the protected workstation, it connects to the existing account and begins replication. Manual creation is recommended for very small customized deployments or initial test deployments. In automatic creation, Live Backup creates an account for the client computer once that computer has the Live Backup Client software installed and attempts an initial connection. The benefits of using automatic client creation are You can select the groups in which client accounts are created, thereby automatically applying the correct protection settings. You can schedule when the replication of clients within each group will begin, thereby enabling you to better stage and plan your deployment. You can better control resources by leaving the Client Activation policy do not start for the selected group, which means that Live Backup will wait for a manual activate signal before replicating any data from each client that belongs to this group. However, since the client accounts are created, this enables you to see all clients in the Live Backup Console, even before any replication begins. Fewer manual operations are required, saving you time. For these reasons, automatic client creation is highly recommended for large deployments of Live Backup Client. MANUAL CREATION When you manually create client accounts and groups, you create each account individually in the Live Backup Console and set protection properties. Although described here, manual creation is not recommended for large deployments of Live Backup. By this time you should have already planned your groups as described on page 21. With that plan in hand, create groups and add clients as follows: 39

46 . CREATE A GROUP 1. Run Live Backup Console. 2. Expand Live Backup Servers, and then expand servername. 3. Right-click Clients or any group to which you want to add a group, and point to New. Click Group. The New Group dialog box appears. 4. In the Group name box, type a unique name describing the group you want to add. This name may identify the type of protection you are configuring, such as Full Protection, or it might represent a company department, such as Accounting. Note that the group name must not contain the ( at symbol) or. (period). The group name may be up to 50 characters, but the full compound group and client name must not exceed 255 characters. 5. In the Comment box, type a description and details about the group you are creating. This information may include the type of clients contained within the group, client users, contact information, as well as any other custom details about the group. You may type up to 4,000 characters. 6. You can now configure advanced protection properties, or you can create the group with the properties inherited from its parent group. To view or set protection properties for this group, click the Advanced button. Live Backup creates the group, and then displays the Group Properties dialog box, in which you can configure protection. To learn how, see Chapter 6: Configuring clients in the Live Backup Administrator s Companion guide. To create the group with the default or inherited properties, click OK. You can now add individual clients to the group. Each client that you create within the group will inherit all of the settings you configured for the group. 40

47 CREATE CLIENTS You can add each client account in your network individually to the Live Backup Server. Although this process may take a while, adding the client accounts individually enables you to configure unique protection settings for each client. You can also use this procedure to add clients to an existing group. 1. In Live Backup Console, expand Live Backup Servers, and then expand servername. 2. Right-click Clients or any group to which you want to add a client account, and point to New. Click Client. The New Client dialog box appears. 3. In the Client name box, type the name of the computer you want Live Backup to protect. You may give the client any name: it may be the same as the NetBIOS computer name, which is the default, or any other name you choose. Note that the client name must not contain the ( at symbol) or. (period). Atempo recommends using the client computer name for ease of setup. If you choose another name, this name must be explicitly specified during Live Backup Client installation. The client name you enter will be appended to the group name to create the full compound name with the format [email protected]. Each individual client and group name must not exceed 50 characters, and the compound name must not exceed 255 characters. 4. In the Comment box, type a description and details about the client you are creating. This information may include the type of client computer, location, client users, or contact information. You may type up to 4,000 characters. 5. You can now configure advanced protection properties, or you can create the client with the properties inherited from its parent group. To view or set protection properties for this client, click the Advanced button. Live Backup creates the client, and then displays the Client Properties dialog box, in which you can configure protection. To learn how, see Chapter 6: Configuring clients in the Live Backup Administrator s Companion guide. To create the client with the group properties, click OK. Live Backup adds the client to the Live Backup Console with an Activating status, and then creates a database to store the client's files as soon as possible. The client icon appears disabled until the client connects to the Live Backup Server. 41

48 . TIP You can also add clients automatically to manually created groups. See Automatic creation, below. AUTOMATIC CREATION Live Backup can create both clients and groups automatically. This method is recommended for large deployments of Live Backup. When you configure auto-creation, Live Backup Server creates an account for each installed client as soon as it tries to connect. You can specify in which group the account will be created, and determine when client replication begins. If you do not configure Live Backup to create clients automatically, then when a connection is attempted, Live Backup Server will reject the client and post an alert. You can then create the client manually, if you wish. By default, clients that have been deleted are refused for auto-creation. To create clients automatically, you must first configure groups to enable clients to be created automatically within them and specify when those clients will begin replication. You can then configure Live Backup to automatically create clients within specified groups. We recommend that you use this method to create Mac clients and Windows clients separately, so that you can configure settings appropriate for each OS type. Client installation and deployment, which comes after this configuration, is described in Chapter 7: Deploy the clients on page 55. This section covers the following required steps: Create or configure a group for automatic creation Define auto-creation policies Configure client auto-creation Configure group auto-creation CREATE A GROUP FOR AUTO-CREATION 1. In the Live Backup Console, expand Live Backup Servers, and then expand servername. 2. Expand Clients. 3. To create a new group, follow the procedure Create a group on page 40, and then click the Advanced button to open Group Properties. To configure an existing group, right-click the group, and then click Properties. 42

49 4. Click the Auto-Creation tab. 5. To enable clients to be created automatically within this group, clear the Deny auto-creation requests to this group check box. 6. In the Client activation area, schedule when to begin copying files from the automatically created client to the Live Backup Server. Select one of the following options: Start immediately after auto-creation Begins copying files to the Live Backup Server as soon as the client account is created. Select this option if you expect only a few clients to be replicating simultaneously, and therefore have no concerns about network traffic or performance. Start at specific time Begins copying files at the time and date you specify. Select this option to delay replication to off-peak days and/or hours such as weekends or the middle of the night. Note that if you specify any time previous to the current date and time, then replication begins immediately after account creation. Start in Begins copying files a fixed number of hours after creating the client account. Select this option to delay replication by only several hours or so. Do not start Does not copy files to the Live Backup Server. Select this option if you want to manually launch replication for the client by selecting Activate from its action menu. NOTE: Client accounts retain their original replication settings; changing this option will not affect previously created client accounts. Therefore, if a client account was created with the Do not start 43

50 . option, then it will not start immediately upon changing the option to Start immediately after autocreation. 7. Click OK. DEFINE AUTO-CREATION POLICIES After you have configured at least one group to accept automatically created clients, you can configure Live Backup auto-creation policies: 1. In Live Backup Console, expand Live Backup Servers, and then expand servername. 2. Expand Server Tools, and then click System Settings. 3. Right-click Client Account Creation Policies, and then click Configure. The Client Account Creation Policies dialog box appears. 4. Select the Enable automatic client account creation check box. 5. To enable creation of the new groups that are specified during client installation, select the Create groups automatically check box. If a new group name is specified during client installation, then Live Backup will create both the group and the client. 6. To enable Live Backup Server to automatically rename a client whose default name already exists in Live Backup Server, select the Resolve duplicate client names check box. 44

51 If the client that is being created has the same name as an existing client account, then the new client will have a ~X appended to its name, where X is replaced with a number. 7. To create clients within a specified group, select the Enable Auto-creation for clients that don't specify a group check box. Then, in the Place such clients in the following group box, input the name of the group in which you want to create these clients. To do this, click Choose, and then select it from the Select Group dialog box. Note that this option applies only to clients that attempt to connect to the Live Backup Server without a group specification. The group name may be specified during client installation. Note also that the group you specify here must be configured to accept automatic client creation, as described in Create a group for auto-creation on page Click OK. Once a newly installed client tries to connect to the Live Backup Server, Live Backup creates the client account with an Activation pending status. The status changes to Activating at the time specified in the Auto-Creation page of the Group Properties. Once activation completes, the client will begin copying files. CONFIGURE CLIENT AUTO-CREATION After you configure auto-creation policies, Live Backup is ready to accept client requests for account creation. These requests occur after the Live Backup Client software has been installed and attempts a connection to the server. For more information, see Chapter 7: Deploy the clients on page 55. CONFIGURE GROUP AUTO-CREATION Live Backup can create groups automatically with the default protection configuration. To create groups automatically, first you must configure Live Backup to accept these requests. In the Client Account Creation Policies dialog box, make sure the Create groups automatically check box is selected. See Define auto-creation policies on page 44. Then when you install the Live Backup Client software, specify the group as well as the client in the Client Name page of the Installation Wizard. You can do this by typing both the client name and the group name as follows: [email protected]. You can also specify this group name during Web installations by sending a link to the full group and client name specification as part of the Web URL as follows: servername/lbclient?clientname@groupname. 45

52 . For more information, see Chapter 7: Deploy the clients on page 55. TIP For improved security, you may want to prevent Live Backup from creating particular clients automatically. By default, deleted clients are excluded from auto-creation. To prevent automatic creation of specific clients, you can prepare a list of clients refused for auto-creation. See the Live Backup Installation and Setup Guide for details. HOW TO MANAGE DEPLOYMENT WITH CLIENTS AUTO-CREATION Suppose you want to build the clients/groups hierarchy in accordance with the departmental structure of your company. Such an approach is reasonable because of the ease of handling deployment and managing protection settings. If you are going to use Web installation for Live Backup Client deployment you just need to send a URL string to all users in each department: servername/lbclient?@department where Department is the name of the Group that corresponds to the particular department. Each user should then run a Web browser, open this URL, and complete the installation accepting all defaults. There s no need to worry about client or group names. Live Backup will create an account for each computer in the department as soon as Live Backup Client is installed. By default account name will correspond to the name of the user s computer. The only required steps are 1. Enable client auto-creation 2. Enable group auto-creation or create group hierarchy in advance. 3. Allow client auto-creation in any group in hierarchy 46

53 DETERMINE PROTECTION AND CONFIGURATION PROPERTIES When you create a group or client, you can configure how Live Backup will protect the files on each client. You can also modify these settings in the Properties of each group and client. These Properties have a direct effect on the level of protection you provide your clients, as well as the amount of storage required. You can configure protection properties as follows: Edit name and comments Specify level of protection Choose which drives to protect Define user documents Define discardable data Allocate storage space Configure data aging Configure default user access Set an expiration date Enable auto-creation within a group (groups only) How to define each of these properties is described in Chapter 7 of the Live Backup Administrator s Companion, as well as in the Help for Live Backup Servers, which you can access by clicking Help in the Client or Group Properties page. Below are some tips and tricks for deciding how to define these properties, organized by each Properties page. NOTE Storage and Auto-Creation properties are inherited from the group to the subgroup, but do not apply to existing clients. Storage properties may be configured independently for each client. 47

54 . GENERAL On the General page, you can specify a unique name comments for a group or client account. The full internal client and group name appears in page as well. This name is a combination of the individual client name and the parent group's name follows: [email protected]. For example, a client named John that is located in Outside Sales group under the Sales and Marketing, John@Outside Sales.Sales and Marketing and this as the is You can also use the Comment area to specify up to 4,000 characters of additional information about the client or group. This information may include the type of client computer, location, client users and contact information. PROTECTION On the Protection page of Client/Group Properties, you can specify whether to apply Full System Protection or User Document Only Protection, and you can specify which local drives you want to protect on each client. For tips on specifying information on this page, see Types of protection on page 12. If these options are not available, then Live Backup Client supports User Document Protection only on this client. Live Backup Client for Mac and Live Backup Express support user document protection only. 48

55 PROTECTED DATA Under Full System protection, Live Backup protects all your clients files, except those files that are excluded from protection in the Discardable Data page. However, under User Document Protection, Live Backup protects only those files defined as user documents. User documents are defined on the Protected Data page in Client or Group Properties. By default, Live Backup includes the following groups of files as user documents: My Documents Directory, Office Documents, Streaming Audio/Video Files, Inboxes, Graphics Files, Application Development Files, Compressed Files, and Text Documents. These groups of files are defined by macros within Live Backup. To learn about the specific file types included with each Macro, see Appendix A: Predefined macros in the Live Backup Administrator s Companion Guide. On the Protected Data page, you may define your own user document types for Live Backup to protect under User Document Protection mode. You can define protection masks for individual files, file types, or entire folders and subfolders. To define masks specific to Mac clients, prefix the mask with Mac: (no space). If you have Full System Protection enabled, the Protected Data page contains no configurable options, as all data will be protected equally. Important To support full system protection on Windows 7, Live Backup requires that an existing System Reserved Partition have a drive label. Full Protection User Document Protection 49

56 . 50

57 DISCARDABLE DATA Live Backup defines file types that are excluded from protection as discardable data. This discardable data consists of files that are completely unnecessary for full system backups, including Windows temporary files that are recreated at boot time, such as swap files, and cached files from the Internet. It also includes local temporary directories, the Windows Recycle Bin, and temporary download directories. You can define discardable data on the Discardable Data page of Client or Group Properties. Defining discardable data is one of the most powerful tools you can use to control storage space on the server storing protected client data. Consider defining discardable data as follows: temporary files created by the operating system or an application; large files that change often, but do not need versioning, such as logs; custom temporary folders, such as C:\TEMP\*.*; screen saver configuration files that write out the same file repeatedly; large backup or archive files that you do not want to protect, such as Ghost (*.gho) or *.iso images, which Live Backup includes as discardable data by default; user-determined discardable files, which can be placed in a globally predefined folder such as */discardable/*. Create this macro, and then instruct users to create a folder named discardable anywhere on their systems. Files placed within it will be ignored by Live Backup. Discarding such files saves disk space on Live Backup Server and diminishes network traffic. To define discardable data masks specific to Mac clients, prefix the mask with Mac: (no space). WARNING Designating any file types other than the defaults as discardable data could prevent a full system recovery on the client computer. Even if a full system recovery appears to be successful, it may be missing files that are required for stable system functionality. Exercise extreme caution when defining any file types as discardable. 51

58 . STORAGE On the Storage page, you can specify how much disk space is allocated to each client as soon as it is created, how the disk space increases when necessary, and what the maximum space limit will be. Plan initial database sizes and growth increments carefully. If you decide to increase the default initial size, then the client replication may proceed more smoothly, but client creation will take longer. The incremental growth size also has performance effects: If set too low, then file fragmentation results. This fragmentation slows down overall performance. If set too high, you may waste disk space. Atempo recommends an initial database size about 20-30% of the expected database size, with growth increments of about 10% of the client database. It is critical that you determine storage requirements before creating clients and adding groups. When you first create a client, it inherits storage properties from its group. However, later changes to the group configuration do not apply to the client. Therefore, if you want to change the storage settings on an entire group, you must configure the group and each client individually. DATA AGING On the Data Aging page, you can define policies for when older protected data is removed from the client database by either deleting it. As a result, Data Aging is another powerful tool for controlling storage space requirements. Carefully consider how long you need to preserve protected files., 52

59 FEATURE LOCKDOWN On the Feature Lockdown page, you can configure which recovery tools are available on a client computer. All users who log in to the Live Backup Client computer will have access to the Live Backup Control Center as well as at least the access rights assigned to the client as follows: No access User Power User Super User Protect files X X X X Recover files/folders X X X Tune performance X X X Configure notifications X X Disable/enable connection X X Roll back the system and application folders Pause/resume versioning X X X Configure update X In addition, the administrator may assign each user individual access privileges. These users will have the same access on every Live Backup Client computer. If a user is granted individual privileges, then when s/he logs into a Live Backup Client computer, then s/he receives whichever privileges (user or client) are greater. Feature Lockdown functionality is not available to Live Backup Clients for Mac. SEE ALSO Configuring user privileges in the Live Backup Installation and Setup Guide. 53

60 . EXPIRATION On the Expiration page, you can set a date at which the client account will expire. Expired clients are stopped: no new versions are created and no local or remote recovery operations are available. AUTO-CREATION On the Auto-creation page of Group properties, you specify policies for creating clients automatically within a group, including scheduling when to begin replication of automatically created clients. For more information, see Automatic creation on page

61 7 Deploying the clients After the Live Backup Server is installed and appropriately configured, you can install the Live Backup Client software and deploy to the client computers in your company. You should deploy Windows clients and Mac clients separately. The remainder of this chapter provides details on Deploying Live Backup Clients for Windows Deploying Live Backup Clients for Mac DEPLOYING LIVE BACKUP CLIENTS FOR WINDOWS You should decide which deployment method you will use and the desired configuration during the planning phase of Live Backup deployment, described in the previous chapters of this guide. To deploy the Live Backup Client software to the computers in your company, you have the following choices. 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. 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. Command line installation Use this method to install clients via a batch file. This method does not install prerequisite software. 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. The remainder of this chapter describes each of these deployment methods in detail. 55

62 . MANUAL INSTALLATION Before installing, make sure the computers where you want to install Live Backup Client meet the system requirements as described in System requirements on page 7. Live Backup must have full access to both the Live Backup cache folder and the Live Backup program folder. You can select locations for these folders during installation. Do not encrypt the folders or otherwise restrict rights, or Live Backup protection will stop. Install Live Backup Client from a network or CD-ROM drive 1. Click the Start button, and then click Run. 2. In the Run dialog box, type n:\lbsetup.exe, where n is replaced with the full path to the Live Backup installation program. This program may be located on a CD-ROM, a network drive such as N, a local drive, such as C, or some other media. 3. Click Next. The Welcome to the Live Backup Installation Wizard screen appears. The Select Component Type screen appears. 4. Select Install Live Backup components, and then click Next. The Install Live Backup screen appears. 5. Click Install Live Backup Client. The Prerequisites Check screen appears. 6. Make sure all prerequisites are installed, and then click Next. The Live Backup Client installation begins. 7. On the Welcome screen that appears, click Next. 8. Read the License agreement that appears, and then click I accept the terms in the license agreement. Click Next. 56

63 9. On the Destination Folder page that appears, you can select the folder in which you want to install Live Backup and the folder you want to use to cache files locally. The default installation folder is C:\Program Files\Atempo\Live Backup To install in a different location, click Change. In the Change Current Destination Folder dialog, type the full path into the Folder name box, or click the Browse button and select a path. Live Backup uses the cache folder to store backup files until a connection with the server is established for copying the files. A typical path to the cache folder is D:\Live Backup Cache Where D is the drive with the most free disk space. To save backups in a different location, click Change. In the Change Current Destination Folder dialog, type the full path into the Folder name box, or click the Browse button and select a path. Click Next. 10. On the Live Backup Server page, specify information about the Live Backup Server. In the Connect Live Backup to the following Live Backup Server box, type the name, IP address, or DNS Host Name of the computer on which Live Backup Server is installed. Click Next. 11. On the Live Backup Client Name page, specify the name given to this client on the Live Backup Console. If a specific name was assigned, type it here; if not, accept the default name that appears. You may also specify the group in which to create the client as well as the client name. To specify the group, use the following format: [email protected]. The default name is the same as the computer's NetBIOS name. Click Next. For more information, see Notify clients of the Web installation on page On the Ready to Install the Program screen, click Install. A progress screen appears. When the installation is complete, the InstallShield Wizard Completed screen appears. 13. Click Finish. The Restart dialog box appears. 14. To restart the computer now, click Yes. To restart later, click No. 57

64 . WEB INSTALLATION Once you have installed Live Backup Server, you may notify all clients of the new Live Backup protection and have each user install the Live Backup Client over an intranet connection. This process enables you to specify both a name and group (or only a group) for each client, lets your users install Live Backup Client at their convenience, and saves you the time of visiting every client computer. It also provides remote users a quick and easy way of installing Live Backup Client. The Web installation package is located in the LBClient virtual directory within the Web site. All required setup files are located in the ClientWebSetup subfolder of the Live Backup Server application folder. For clients to access this setup, they must have access to the LBClient virtual folder on the Live Backup Server. This section describes how to Enable the Web installation. Notify clients of the Web installation. Run a Live Backup Client Web installation. TIP You can modify the Web installation pages from \\LBServer\Program Files\Atempo\Live Backup Server\ClientWebSetup. Be careful to edit only the displayed text portions of the Web installation pages. If you edit anything else, Web installations may stop working. ENABLE THE LIVE BACKUP CLIENT WEB INSTALLATION 1. Expand Live Backup Servers, and then expand servername. 2. Expand Server Tools, and then click Web-based Client Deployment. 3. To enable clients to access the Web setup program, select the Enable Web-based Client distribution point check box. To lock out access to the Web client setup, make sure this check box is cleared. 4. In the Installation user interface group box, select whether to run the installation silently or give client users control over the installation options. To install the client silently, displaying only a progress bar and cancel button during the installation, select the Simple: Display only a progress bar and cancel button during installation option button. This option uses the default settings and is recommended for most deployments. To give the client users control over the installation options, select the Complete: Display all pages and options in the Installation Wizard option. Select this option only if your users need to modify installation paths. 58

65 5. If you have recently upgraded the Live Backup Server, and you want to notify Live Backup Clients of the available client software upgrade, select the Notify clients of available upgrade check box. Once you click Apply, all installed clients with a supported version older than the Live Backup Server will either receive the Live Backup Client upgrade and begin installation automatically, or will receive a notification about the upgrade version with instructions to install. This notification will appear every time a user logs into the client computer, until the upgrade has been completed. Note that only Live Backup Super Users may modify the update settings to receive a notification rather than an automatic installation. New installations will need to be notified manually: see the next section. 6. If you have edited the Web installation page, and you want your Live Backup Client users to access this updated version, click Refresh. 7. Click Apply. NOTIFY CLIENTS OF THE WEB INSTALLATION You must notify your users of the Live Backup Client installation that is available over the corporate intranet. We suggest that you use , but you may use any means available to your organization. If you choose , then compose an to all users of client computers you have added to Live Backup Server for protection. In this , provide a link to the Web installation of Live Backup Client. In this link, you may specify both the client name and the group name. See the options for how to format the link, below: To send a link to the basic installation, using the default client name and group, use the following format: To send a link to the installation and specify the client name only, use the following format: To send a link to the installation and specify that the client name be created in the root group, use the following format: To send a link to the installation and specify the group in which you want to create the client, but still use the default client name, use the following format: In this case all clients will be created in the same group. Note that each client may still provide its own group name during the installation. This group will be created as a subgroup within the group specified by the URL. Use this option if you want to group clients automatically, but do not want to specify the full compound name for 59

66 . each client. It enables client users to create a local group hierarchy within the one parent group that you define. To send a link to the installation and specify both the client name and the group in which it should be created, use the following format: Instruct the users to click this link to launch the installation. Remember to warn them that they should exit all applications before running the installation and must restart their computers after installation. You can verify that the clients have been installed by checking their status in the Live Backup Console. Expand Clients, and then check the details pane. If the client icon is active, then the Live Backup Client has been installed on that computer and has successfully connected to the server. RUN A LIVE BACKUP CLIENT WEB INSTALLATION 1. On the Live Backup Client computer, run Internet Explorer and go to (See the previous page for how to specify group and client names.) 2. Read the Welcome page, and then click the link at the bottom of the page. The Checking Prerequisites page appears. 3. Live Backup checks the computer for the prerequisite software. If it does not find any of the prerequisites, it will prompt their installation. Follow the directions on the screen. 4. Once all prerequisites are set up, begin installation. Refresh the Web page, and then click the Install link. Follow the directions on the screen. 5. Click Yes. A status bar appears indicating the progress of the Live Backup Client installation. Once it completes, a message appears instructing you to restart the computer. COMMAND LINE INSTALLATION Live Backup uses the standard Windows Installer to install the Live Backup Client application. You can run this installer interactively as described in Manual installation on page 56, or with any level of interaction, including silently, using a command line. From the command line, Live Backup installs the Live Backup Client and all prerequisites except Internet Explorer. Make sure the Live Backup Client meets the software requirements before continuing with the command line installation. See Live Backup Client system requirements on page 7. 60

67 TO RUN A COMMAND LINE INSTALLATION OF LIVE BACKUP CLIENT: From the installation directory, \\Live Backup\Client, type msiexec /i Client.msi /q PROPERTY=Value The properties and command line switches determine the Live Backup Client installation options. For more details on the available options, see Chapter 5: Installing Live Backup Clients in the Live Backup Installation and Setup Guide. TIP Use command line installation as part of the installation batch file, described below, to deploy Live Backup to a large number of client computers with custom options. INSTALLATION BATCH FILE Using the command line installation option, you can create a batch file that will install Live Backup Client on the computers throughout your enterprise. The installation will be automatic and silent, and will save you time deploying Live Backup. The process of running a batch installation is comprised of the following steps: 1. Make the Live Backup distribution files available on a network. 2. Prepare a batch file with the correct command line. 3. Execute the batch file using your network administrative system, such as a logon file. This process is described in more detail, below. MAKE THE LIVE BACKUP DISTRIBUTION FILES AVAILABLE ON A NETWORK From the Live Backup product CD-ROM, copy the contents of the \\Live Backup\Client folder to a network drive. All client computers on which you want to install Live Backup Client must have at least read access to this drive. For example, at a command prompt, type copy e:\live Backup\Client n: PREPARE THE INSTALLATION BATCH FILE The batch file must contain all the instructions necessary to install Live Backup Client on a computer. The sample batch file detailed below is intended to be run as a logon script. To prepare the installation batch file, create a TXT file and save it with a BAT extension for example, LBInstal.bat. In any text editor, type the batch file as follows. Note that there should be no carriage returns within the MSIEXEC command: REM ********Live Backup Client Install**************** 61

68 . REM ******** Please set LBSETUPDIR for fresh installation of client only set LBSETUPDIR=C:\Program Files\Atempo\LiveBackup REM ********** SETUP ************ REM ********** The three lines below (MSIEXEC command line) must be typed as a single line entry with no line breaks. MSIEXEC /i "\\ServerName\Live Backup\Client\Client.msi" /q INSTALLDIR="%LBSETUPDIR%" LBDATADIR="C:" LBSERVER=CorporateServerName REBOOT=FORCE REM **********End of MSIEXEC command line. :EXIT set LBSETUPDIR= REM*******************End of File************************* Note After this batch file is run, the computer will be restarted automatically to complete the Live Backup Client installation. If you do not want the computer to restart automatically, then remove REBOOT=FORCE from MSIEXEC command line. If you want to generate installation log then add /lv+ <LOGFILE_PATH>\Client_Install.log at the end of MSIEXEC command line. EXECUTE THE BATCH FILE There are many ways to execute the batch file on many computers. You may send it as an attachment with instructions on how to run it, or you may run it as part of a logon script. To execute the batch file during logon, you must modify each user s domain account. To run the batch file at logon: 1. Logon to the Primary Domain Controller. 2. Copy the batch file you created, LBInstal.bat, to the following folder: C:\\WINNT\SYSTEM32\REPL\IMPORTS\SCRIPTS 3. Run Windows Active Directory Users and Computers. 4. Expand the Users node, and then go to the Properties for a user account. 5. Click the Profile button. 6. Type the name of the batch file into the Logon Script Name box. 7. Close the User Properties box. 8. Repeat steps 3 through 6 for each user on whose computer you want to install Live Backup Client. The next time the user logs on to the network, the batch file will run automatically. The batch file is set up to run only this one time, so the installation will be performed only once. 62

69 SYMANTEC GHOST OR CLONING SOFTWARE Symantec Ghost is a comprehensive enterprise tool for OS deployment and software distribution. Using it, you can deploy an image containing the Operating System as well as other software applications onto a PC in minutes. To ease your deployment of Live Backup Client, you can include the Live Backup Client software on your Ghost image as well. If you choose to do so, please note the following: Before you create the Ghost image, stop Live Backup Client services. Then from the same computer from which you will create the image, delete the following key from the system registry: HKEY_LOCAL_MACHINE\SOFTWARE\Atempo\Live Backup\InstallationId You can now create the Ghost image. Before deploying this image to computers in your enterprise, you must enable client auto-creation, and make sure to enable the Resolve duplicate client names option, as follows: 1. Run Live Backup Console. 2. Expand Live Backup Servers, and then expand servername. 3. Expand Server Tools, and then expand System Settings. 4. Right-click Client Account Creation Policies and select Configure. 5. In the Client Account Creation Policies dialog box, select the Enable automatic client account creation check box. 6. Select the Resolve duplicate client names check box. 7. Click OK. For more information, see Automatic creation on page

70 . DEPLOYING LIVE BACKUP CLIENT FOR MAC To complete the installation and deployment of Live Backup Client for Mac, you must complete the following steps: 1. Install the Live Backup for Mac Windows Service 2. Configure protection for your Mac clients 3. Install the Live Backup Client for Mac software Each step is described in detail, below. INSTALL THE LIVE BACKUP FOR MAC WINDOWS SERVICE If you installed Live Backup 3.20 Client for Mac, then you installed a separate service on the Live Backup Server: Live Backup for Mac Windows Service. This service is still required in Live Backup 3.31; however, it is fully integrated in the Live Backup Server installation. If you are installing Live Backup 3.31 for the first time, or you are upgrading to Live Backup 3.31,, the Live Backup for Mac Windows Service will be installed. CONFIGURE PROTECTION FOR YOUR MAC CLIENTS Before deploying Live Backup Clients for Mac, you should configure protection settings that will give you the best performance during initial replication, while protecting the most important folders and files on your Macs. To simplify the procedure, we recommend that you deploy all Mac clients separately from your Windows clients. When you are ready to begin, 1. Create a group for Mac clients and configure protection settings. 2. Configure auto-creation policies to place newly installed clients into your Mac group. These steps are described below. CREATE A GROUP FOR MAC CLIENTS AND CONFIGURE PROTECTION SETTINGS 1. In the Live Backup Console, expand Live Backup Servers, and then expand servername. 2. Right-click Clients, and point to New. Click Group. The New Group dialog box appears. 3. In the Group name box, type a unique name describing the group: for example Mac clients. 4. In the Comment box, type a description and any other details you want. 64

71 5. You can now configure advanced protection properties: click Advanced. 65

72 . 6. Click the Protection tab. Clear the Inherit these properties from the parent group check box, and then click the User Document Protection option. 66

73 7. Click the Protected Data tab. On this page, you specify which folders and file types will be protected on all Mac clients. Initially, we recommend that you clear all the Predefined macro types. The macros may result in protection of more data than you really want. For details on macro definitions, see Appendix A: Macros in the Live Backup Administrator s Companion Guide and Error! Reference source not found. on page Error! Bookmark not defined.. We do recommend that you add the Users folder. You will later exclude subfolders of the Users folder that should not be protected. In the New mask box, type Mac:/Users*, and then click Add. 67

74 . 8. Click the Discardable Data tab. This page specifies the folders and files that will be excluded from protection. We recommend that you select the following Predefined discardable data: Internal discardable data Local temporary directories Recycle bin directories Temporary internet directories Temporary download directories We also recommend that you consider adding the following Other discardable data. These masks specify folders that contain either very large files, such as music and photos, or files that you probably do not want to protect, such as /Library. Make sure you preface all Mac specific masks with Mac: Mac:*.iso Mac:/Applications Mac:/Developer Mac:/Library Mac:/opt Mac:/System 68

75 Mac:/Users/*/Music Mac:/Users/*/Pictures Mac:/Users/*/Documents/Virtual Machines 9. Click the Auto-Creation tab. Make sure the Inherit these properties from the parent group and the Deny autocreation requests to this group check boxes are cleared. Choose when you want to create new clients. You may want to set a specific time during off hours for the replication to begin. 10. You can keep the defaults in the other Properties pages. Click OK to create the group. 69

76 . CONFIGURE AUTO-CREATION POLICIES You can now configure auto-creation policies to ensure that any Mac clients that you deploy will be created in this new group. After all Mac clients are deployed, you can reconfigure your autocreation policies. 1. In the Live Backup Console, expand Live Backup Servers, and then expand servername. 2. Expand Server Tools, and then click System Settings. 3. Right-click Client Account Creation Policies, and then click Configure. The Client Account Creation Policies dialog box appears. 4. Select the Enable automatic client account creation check box. 5. To rename a client whose default name already exists in Live Backup Server, select the Resolve duplicate client names check box. 6. Select the Enable auto-creation for clients that do not specify a group check box. Then in the Place such clients in the following group box, specify the name of the Mac clients group that you created: click Choose, and then select it from the Select Group dialog box. 7. Click OK. 8. Once you deploy the Live Backup Client for Mac software, a client account for each will be created automatically in the group you created. 70

77 INSTALL THE LIVE BACKUP CLIENT FOR MAC SOFTWARE You can deploy the Live Backup Client for Mac to your client computers over the Web, and then run a standard installation program to set it up. Live Backup also provides upgrade notifications automatically to your clients. SYSTEM REQUIREMENTS Hardware Mac PC with a PowerPC or Intel processor 1 GB RAM 100 MB of free disk space (500 MB recommended) Network connection (modem, WAN, and wireless are supported) Software Mac OS X (Tiger) and 10.5.x (Leopard) 32-bit; Mac 10.6.x (Snow Leopard) 32- and 64-bit Administrative permissions on the client workstation (for installation only) TO DEPLOY THE LIVE BACKUP CLIENT FOR MAC SOFTWARE 1. Point Safari (or other Web browser) to The Mac Downloads window appears and shows progress of the download. 2. When the download completes, a message appears: Live Backup for Mac.pkg contains an application. Are you sure you want to continue downloading? Click Continue. 3. If another message appears, This package contains a program that determines if the software can be installed. Are you sure you want to continue? then click Continue. 4. If the Mac client security allows it, the installation begins now. If the security settings prevent it, users will have to run the installation manually. See below. 5. After installation completes, the user may go to the Downloads folder and trash the "Live Backup for Mac.pkg" file. 71

78 . TO INSTALL THE LIVE BACKUP CLIENT FOR MAC SOFTWARE MANUALLY If the client installation does not start automatically after Web deployment, or you decide to deliver the installation package to the client via any other means, you can run the installation manually. 1. Run Live Backup for Mac.pkg. 2. Read the Welcome screen that appears, and then click Continue. 3. Read the License agreement that appears, and then click Continue. In the confirmation message that appears, click the Agree button. 4. On the Live Backup Server and Client Names page that appears, specify connection information about the Live Backup Server. In the Live Backup Server box, type the name or the IP address of the computer on which Live Backup Server is installed, followed by the port designation. By default, the port is :8080. If you are not sure of the required server information, check with your Live Backup Administrator. In the Client Name box, type the name given to this client on the Live Backup Console. If the Live Backup Administrator gave you a name, type it here. If not, accept the default name that appears. The default name is the same as your computer's name. Click Continue. 5. On the Select a Destination page that appears, select the volume on which you want to install Live Backup. Click Continue. 6. On the Installation Type page, click Upgrade. 7. If an Authenticate dialog box appears, type your Password, and then click OK. 8. You will then see a confirmation message that warns you that you will have to restart the computer at the end of the installation. If it is all right to restart the computer, and you want to continue the installation, click Continue Installation. Otherwise, click Cancel: you can restart the installation later. The Live Backup installation program copies the Live Backup program files to the selected volume. 9. Click Restart. Once your computer has restarted and connected to the Live Backup Server, Live Backup immediately begins the mirroring process, protecting your files from corruption and loss. 72

79 PERFORM A SILENT INSTALL OF LIVE BACKUP CLIENT FOR MAC You can perform a silent installation of Live Backup Client for Mac from the command line. The silent installation requires two files: AutoConfig.txt: specifies the name of the Live Backup Server, ports, and Group name. AutoInstallScript: A shell script that runs the installation and restarts the computer. These files are located in the AutoInstall folder of the LiveBackup for Mac.pkg. Administrative rights on the client computer are required to complete the following procedure. 1. From within the LiveBackup for Mac.pkg file, open AutoInstall/AutoConfig.txt in a text editor. 2. [Required] Edit the SERVER_IP= line as follows: Type the IP address of the Live Backup Server to which you want the client to connect. Make sure no spaces or special characters are added before or after the IP address. 3. [Optional] Edit the GROUP_NAME= line as follows: Type the name of the group in which you want to place the Live Backup Client account on the server. Do not use any special characters. If you do not edit the group name, the default group will be used. 4. [Optional] Edit the CLIENT_NAME= line as follows: Type the name you want to give to the client account. Do not use any special characters. If you do not specify a client name, then the client will be created using the host name of the computer in the group you specify. 5. You can now install the client by running the AutoInstallScript: o From a Terminal window, go to the LiveBackup for Mac.pkg directory. o Type: sh AutoInstallScript, and then press Return. Live Backup Client for Mac will be installed in the default location, and will use the connection parameters you specified in the AutoConfig.txt file. 73

80 . Note Live Backup Client communicates with the Live Backup Server over port If you want to change this communication port, see Allow the Mac client to connect to the Live Backup Server over a non-standard port on page 76. TO NOTIFY CLIENTS OF AN UPGRADE AUTOMATICALLY Atempo may periodically make maintenance updates available to you. After you download these updates, you can notify your clients of their availability automatically. 1. Download the update and install on the Live Backup Server. 2. Once installed, Live Backup delivers an upgrade notification to the client: An update for Live Backup Client for Mac is available. Would you like to install it now? 3. To launch the upgrade immediately, click Yes. Otherwise, click Remind me Later. RECONFIGURE AUTO-CREATION POLICIES After all Mac clients are deployed, and before you deploy any more Windows clients, reconfigure auto-creation policies to place newly created clients in a group configured with protection settings appropriate to the clients being protected. To learn more about deploying Live Backup Clients, see the Live Backup Deployment Guide and the Live Backup Installation and Setup Guide. 74

81 8 Changing ports used for server/client communication Since Live Backup Server communicates with its clients using the HTTP protocol with standard port assignments, it requires no special configuration for communicating through a firewall. If your company is already setup to use the Internet, you should have no difficulties using Live Backup. You may, however, change the port assignments if you so choose. The process of changing ports differs for Windows and Mac Live Backup Clients. ALLOW THE LIVE BACKUP CLIENT FOR WINDOWS TO CONNECT OVER A NON-STANDARD PORT Although the default HTTP port for Live Backup for Windows Clients is 80, you may change it on the Live Backup Server before installing Live Backup Clients. Note, however, that changing the port for Live Backup for Windows Clients data communication will also change the port used to deliver the Live Backup for Mac Clients software updates. To accommodate this change, additional configuration is necessary. See Configure a port for delivery of Live Backup for Mac Client software updates. UNDER WINDOWS SERVER 2003 AND IIS 6 If Live Backup Server is the only Web application on the server, you can change the port for the Default Web site under Web Site Properties in the IIS Manager. If you change the port of the Default Web site, all communication will happen through the new port. UNDER WINDOWS SERVER 2008 AND IIS7: If Live Backup Server is the only Web application on the server, you can change the port for the Default Web site by editing the Bindings in IIS Manager: Select the Default Web site, and then in the Action pane, click Edit Bindings. In the Site Bindings dialog box, modify the HTTP port. If you change the port of the Default Web site, all communication will happen through the new port. 75

82 . LIVE BACKUP CLIENT FOR WINDOWS INSTALLATION If you change the port of the Default Web site, then when you install the Live Backup Clients, you must also specify the new port number. For example, if the new port number you chose was 777, you would specify the following in the Server screen of the Live Backup Client installation: lbserver:777 lbserver.company.com: :777 Note If you create and configure new Web directories, they will not be deleted if you uninstall Live Backup. You must remove them manually. If you uninstall Live Backup while IIS is running, then IIS will prevent you from removing any files that it is currently using. At the end of the uninstall, you will need to restart your computer to remove those files. You will then need to reconfigure IIS, to prevent errors about missing directories. ALLOW THE MAC CLIENT TO CONNECT TO THE LIVE BACKUP SERVER OVER A NON-STANDARD PORT You can configure Live Backup Server to communicate with the Live Backup for Mac Client over a non standard port. To do so, you must configure two separate ports: one for software installation and updates and another for data backup and recovery. CONFIGURE A PORT FOR DELIVERY OF LIVE BACKUP FOR MAC CLIENT SOFTWARE UPDATES The port that you configure for the delivery of the Live Backup for Mac Client software is the same port that is used for Live Backup for Windows Client data communication. Therefore, before you modify this port, make sure that your Windows clients are also configured properly. For more information on how to configure the port in IIS and how to configure the Live Backup for Windows Clients, see Allow the Live Backup Client for Windows to connect over a non-standard port. After you modify the port in IIS, you must also modify a configuration file that is included with the Live Backup for Mac Client package. 1. On the Live Backup Server, navigate to the following file: C:\Program Files\Atempo\LiveBackup Server\MacClient\LBMacSetup.zip 2. From the zip file, extract AutoInstall\AutoConfig.txt and open it in a text editor. 76

83 This file contains the following lines: SERVER_IP= WinFE_Port=8080 IIS_Port=80 GROUP_NAME= CLIENT_NAME= 3. Edit the IIS_Port= line with the port number configured in IIS. 4. Save the file. 5. Add the modified version of AutoConfig.txt back to the archive file LBMacSetup.zip. 6. Repeat this procedure with the following file: C:\Program Files\Atempo\LiveBackup Server\MacUpdate\LBMacnnn.zip Both new installations and updates to the Live Backup for Mac Client software will be delivered over this new port. CONFIGURE A PORT FOR DATA COMMUNICATION BETWEEN THE LIVE BACKUP SERVER AND THE LIVE BACKUP FOR MAC CLIENT By default, Live Backup Server communicates with the Live Backup for Mac Client over port 8080 for backup and recovery. You may change this default port by modifying a registry setting on the Live Backup Server and a configuration file included with the Live Backup for Mac Client package. TO CONFIGURE A NON-STANDARD PORT ON LIVE BACKUP SERVER 1. Live Backup Server communication with the Mac Client is managed by the WinFE service. To configure a port, you must first stop this service: o On the Live Backup Server, run Services.msc. o In the Local Services list, right-click WinFE, point to All Tasks, and then click Stop. 2. Now you must edit a key to the Windows Registry: o Run Regedit o Navigate to the following key: 32-bit Windows HKEY_LOCAL_MACHINE\SOFTWARE\Atempo\LiveBackup Server\ 77

84 . 64-bit Windows HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Atempo\LiveBackup Server\ o Right-click the registry key, WinFEPort, point to Modify, and then replace the Value "8080" with the port number that you want to assign. o Close Regedit. 3. Restart the WinFE service, and then close Services.msc. You can now modify the configuration file. TO MODIFY THE PORT CONFIGURATION FILE: 1. On the Live Backup Server, navigate to the following file: C:\Program Files\Atempo\LiveBackup Server\MacClient\LBMacSetup.zip 2. From the zip file, extract AutoConfig.txt and open it in a text editor. This file contains the following lines: SERVER_IP= WinFE_Port=8080 IIS_Port=80 GROUP_NAME= CLIENT_NAME= 3. Edit the WinFEPort= line with the port number configured in the registry. 4. Save the file. 5. Add the modified version of AutoConfig.txt file back to the archive file LBMacSetup.zip. 6. Repeat this procedure with the following file: C:\Program Files\Atempo\LiveBackup Server\MacUpdate\LBMacnnn.zip Both new installations and updates to the Live Backup for Mac Client software will use this port for data backup and recovery. 7. If you are modifying this port assignment after installation, you must modify the ServerConfig file on each Live Backup for Mac Client computer at the following location: 78

85 /Library/Application Support/Atempo/LiveBackup/ After editing and saving AutoConfig.txt, restart the Mac computer to reset the port configuration. 79

86 . 9 Testing and tuning After you have installed and deployed Live Backup, you should test for a successful installation, and then tune your network and server hardware and software configuration for optimum speed and reliability. Consider checking the following: Check that clients are installed properly Check that clients are connected properly Check that clients are replicating Assess network performance under the strain of replication Check the amount of disk space being consumed Check disk space for archiving Create a checkpoint Perform a test recovery of a file CHECK THAT CLIENTS ARE INSTALLED PROPERLY If Live Backup Client is installed properly, a blue or orange Atempo Live Backup icon appears in the task tray of the client computer. If this icon is not present, then the installation did not complete properly, and you should Make sure the installation completed successfully: open Add/Remove Programs from the Control Panel, and make sure Atempo Live Backup Client appears in the installed applications list. Make sure that the client computer has been restarted after the installation. 80

87 CHECK THAT CLIENTS ARE CONNECTED PROPERLY Clients should connect to the Live Backup Server immediately after installation. To check the connection, click Start and point to Programs. Point to Atempo Live Backup, and then click Live Backup Server Connectivity Test. After the test completes, the status Tested successfully should appear. This option is also available in from the Network page of the Live Backup Control Center: click Check Connection. You can also check the Live Backup Console for an active status. If the clients do not appear to be connected, you should Make sure the client s connection is not manually disabled. Make sure TCP/IP is set up properly. Make sure the Live Backup Server is running. Ping the Live Backup Server from the client. Verify that Live Backup Client is attempting to access the correct Live Backup Server name. This server name appears on the Network page of the Live Backup Control Center. CHECK THAT CLIENTS ARE REPLICATING Shortly after the client computers connect to Live Backup Server, they should begin replicating files to the server. When Live Backup Client is replicating files to the server, the Live Backup tasktray icon changes from orange to blue. To determine if a client has fully replicated, right-click the Live Backup task tray icon and choose Control Center. Click the Client Engine tab. If replication is complete, Mode displays Normal, and the local cache will be empty (Cache in use shows 0 MB). If the Live Backup Client appears to be connected, but does not appear to be replicating, note that the server might be busy, preventing replication at the moment. If this is the case, replication will begin shortly. If replication is not running for quite a while, then you should check the Live Backup Console to ensure that the appropriate client account has been created for this client. If no account appears, 81

88 . then create the account manually or enable auto-creation from both System Tools and the parent group. If the client account exists, but replication still has not started, then check the status of the client in the Live Backup Console. If the status is Activation pending, then right-click the client account and click Activate. Note that the client may not activate immediately. Wait several minutes and refresh the screen to see the updated status. You should also make sure that the Live Backup Service has been started. 1. Click Start, point to Settings, and then click Control Panel. 2. Double-click the Services icon. 3. In the Services list, highlight Live Backup Network Service. Make sure the service is Started, if not, click the Start button. 4. Click OK. CHECK THE AMOUNT OF DISK SPACE BEING CONSUMED In the Live Backup Console under Reports, check the Space Consumption to make sure it is in line with your expectations. Note that when data aging is run, there will be a temporary increase in database log file size. Since these log files consume additional disk space, you should run Data Aging well before running out of free space on the database server. WARNING Data Aging is a preventative tool. Do not run Data Aging if the Live Backup Server is already running out of space. If you do get into trouble and need free space to proceed, delete one or more clients. Run Data Aging on some other clients, and then compact the server to free more disk space. You can then create a new database for the deleted client and replicate again. CHECK DISK SPACE FOR DATA AGING Check your disk space usage periodically to make sure that all your available disk resources are not filling up. If you catch a disk space problem in time, you can use Data Aging to remove older data and free disk space. However, if you run out of disk space entirely, you will not be able to use Data Aging. Data Aging requires some free disk space for its temporary transaction logs. If there is no more disk space, the transaction logs cannot grow with the required information, and Data Aging will fail. You will have no means of recovering disk space other than deleting clients, which is undesirable. 82

89 CREATE A CHECKPOINT Once the clients are fully replicated, restart each client computer to create a Static Checkpoint. Static Checkpoints provide the greatest stability for system rollback or recovery operations. It is recommended that you create at least one Static Checkpoint following full system replication. You may also create a Dynamic Checkpoint. Dynamic Checkpoints are created without requiring Windows to restart. They are convenient because no restart is required, but they are more likely to be missing files than static checkpoints. You can create either type of checkpoint using the Save System Checkpoint utility of the Live Backup Client. To confirm that a checkpoint was created, check each client from the Live Backup Console: Rightclick a client name and choose System Image Wizard. If a checkpoint was created, you will see it in the first page of the System Image Wizard (click Cancel). If not, a message informing you that there are no checkpoints appears, and the System Image Wizard exits. There may be several reasons why a checkpoint was not generated. See the table below for possible causes and workarounds: Why checkpoint failed If you did not create a Dynamic Checkpoint using Save System Checkpoint, then the client must be restarted to create a system checkpoint. If you have not yet restarted this client, then no checkpoints have been created yet. The end-user may have aborted the startup system scan by pressing the Alt key. This automatically invalidates a checkpoint. The client may not have had sufficient time to send the checkpoint to the server. Checkpoints are not visible while they are still in the local cache. The client s database on the server may Next steps Restart the Live Backup Client computer. Restart the Live Backup Client computer, and allow the checkpoint creation process to complete (do not press Alt). You might have a lot of data on the client (greater than a few gigabytes) that will take a while to replicate. Allow for more time for the checkpoint to be sent to the server and check again later. Make sure the Live Backup database for the 83

90 . Why checkpoint failed be full, preventing the client from transferring data to the server The client may be unable to reach the server due to network connectivity issues Next steps client has adequate room for the client system s data. Check the Live Backup Application Log for space allocation errors related to the specific client. If necessary, increase the Maximum Size of the client s database. You can set this value under Clients within the Live Backup Console. Allow a few minutes for the database to expand after the changes have been made. You might have connectivity problems with the server. Live Backup uses Microsoft Internet Explorer s network libraries and local settings to communicate with Live Backup Server. To troubleshoot: Make sure the client can ping the Live Backup server computer. Access the web page Check that the values for Local Area Network (LAN) Settings in your IE Browser s Tools--Internet Options Connections page are correct. The client may not have sufficient local cache space You may have a small amount of free space for caching. For optimum performance on initial replication, we recommend twice the amount of data on the system in free space (this is assuming you leave the cache setting in the client Control Center at 50%. Increasing this value will use a greater percentage of your free space.) PERFORM A TEST RECOVERY OF A FILE After the initial replication and checkpoint generation, Live Backup should be protecting the client files. To verify this protection, perform a test file recovery. A complete description of recovering files appears in the Live Backup Client User Guide. 84