symantec continuous protection server 12.5 administration

Symantec Backup ExecContinuousProtectionServer

Administrator's Guide

13897293

The software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version 12.5

PN: 13897293

Legal NoticeCopyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and Backup Exec are trademarks or registered trademarksof Symantec Corporation or its affiliates in the U.S. and other countries. Other names maybe trademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

http://www.symantec.com

Printed in the United States of America.

10 9 8 7 6 5 4 3 2 1

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’s Maintenance Programs, you can visit our Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introducing Symantec Continuous ProtectionServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Symantec Backup Exec Continuous Protection Server ... . . . . . . . . . . . . . 13Components of Continuous Protection Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14How Continuous Protection Server works .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16What you can do with Continuous Protection Server ... . . . . . . . . . . . . . . . . . . . . . . . . 19About backup strategies and planning .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Data protection considerations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About backup job schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Where to find more information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Accessing the Continuous Protection Server documentation .... . . . . . . 23Accessing the online Help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Accessing the Symantec Technical Support Web site ... . . . . . . . . . . . . . . . . . 25Accessing the Symantec Backup Exec Web site ... . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 2 Installing Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . . . . 27

Before you install .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Guidelines for installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Checking your environment before installation .... . . . . . . . . . . . . . . . . . . . . . . . 29Continuous Protection Server and Backup Exec compatibility ... . . . . . 30File system filter driver compatibility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Understanding the Continuous Protection Server service

account ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31System requirements for the product ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

System requirements for Business Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32System requirements for Continuous Management Service and

Protection Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33System requirements for Administration Console ... . . . . . . . . . . . . . . . . . . . . . 34System requirements for Web Restore Server Component ... . . . . . . . . . . 35System requirements for Indexing Component ... . . . . . . . . . . . . . . . . . . . . . . . . . 36System requirements for Backup Exec Retrieve .... . . . . . . . . . . . . . . . . . . . . . . . 36Firewall support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

What gets installed and where .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Contents

Folders that are installed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Drivers that are installed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Continuous Protection Server services that are installed .... . . . . . . . . . . . 39Registry entries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Performing an initial installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Viewing installation logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Push-installing Continuous Protection Server components ... . . . . . . . . . . . . . . . 47Upgrading to Continuous Protection Server 12.5 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Modifying Continuous Protection Server installations .... . . . . . . . . . . . . . . . . . . . . 51Uninstalling the Continuous Protection Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Uninstalling a Continuous Protection Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 3 Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

About the Continuous Protection Server Administration Console ... . . . . . . . 55Starting the Continuous Protection Server Administration

Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56About the general Administration Console features ... . . . . . . . . . . . . . . . . . . . . . . . . . 56About the Administration Console views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Overview view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Setup view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Restore view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Job Monitor view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Alerts view .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4 Configuring Continuous Protection Server . . . . . . . . . . . . . . . . . . . . 63

Configuring Business Servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Reviewing the general properties of a Business Server ... . . . . . . . . . . . . . . . 64Reviewing the volume properties of a Business Server ... . . . . . . . . . . . . . . . 65

Moving of servers between Backup Groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Managing the Continuous Protection Server Services ... . . . . . . . . . . . . . . . . . . . . . . 67

Stopping or starting Continuous Protection Server services ... . . . . . . . . 67Adding or removing servers from the Service Manager ... . . . . . . . . . . . . . . 68Changing service account credentials ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Managing backup destinations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Adding a backup destination .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Configuring a backup destination for Shadow Storage .... . . . . . . . . . . . . . . 70Renaming backup destinations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Deleting backup destinations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Managing snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Creating snapshots on demand .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Creating a snapshot schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Editing a snapshot schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Contents8

Defining a retention policy for a snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Viewing snapshot history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76States of snapshot indexing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Deleting snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configuring registry entries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Accessing the Settings Utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About the Settings Utility tunable parameters ... . . . . . . . . . . . . . . . . . . . . . . . . . . 79Changing Settings Utility parameters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 5 Backing up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

About CPS backup jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91About backing up System State and Shadow Copy

Components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92How encrypted files are handled .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Creating CPS backup jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Editing backup job configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Moving a backup job to a different backup destination .... . . . . . . . . . . . . . . . . . . . . 95

Including and excluding information from backup jobs ... . . . . . . . . . . . . . . 95Changing a backup job schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Limiting the network bandwidth of a backup job .... . . . . . . . . . . . . . . . . . . . . 100Adding a script that runs before or after backup jobs ... . . . . . . . . . . . . . . . 100

Starting, stopping, and canceling backup jobs manually ... . . . . . . . . . . . . . . . . . 101

Chapter 6 Restoring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

About restoring data with Continuous Protection Server ... . . . . . . . . . . . . . . . . 103Restoring files and folders ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Restoring system information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Restoring System State to an Active Directory system .... . . . . . . . . . . . . . . . . . . . 106Restoring network shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 7 Using Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

About Backup Exec Retrieve .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Features of Backup Exec Retrieve .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

About reparse points ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Security and credentials for Backup Exec Retrieve .... . . . . . . . . . . . . . . . . . . . . . . . . 111

Internet Explorer security on Windows Server 2003 .... . . . . . . . . . . . . . . . 111Retrieving files by using Backup Exec Retrieve .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Using CPS with Backup Exec Desktop and Laptop Option .... . . . . . . . . . . . . . . . 113

Securing data that is not retrievable ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

9Contents

Chapter 8 Monitoring CPS processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

About the Job Monitor ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Monitoring jobs and job pairs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

About job states ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Viewing the status of a job and job pairs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Viewing a job report ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119CPS job report details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Managing CPS job alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Viewing and filtering active alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Viewing and filtering alert history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Viewing alert properties ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Responding to active alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Deleting alerts from alert history .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 9 Using Continuous Protection Server with BackupExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

How Continuous Protection Server works with Backup Exec .... . . . . . . . . . . . 125Protecting your Exchange Servers with Continuous Protection Server

and Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Protecting CPS with Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Configuring CPS for Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Backing up CPS with Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Restoring Continuous Protection Server with Backup Exec .... . . . . . . . 129

Monitoring CPS jobs in Backup Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Understanding the credentials for using Backup Exec

SmartLink .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Setting up a SmartLink connection between CPS and Backup

Exec .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Viewing Backup Exec alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Viewing Backup Exec job logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137About CPS backup job log details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Chapter 10 Troubleshooting Continuous Protection Server . . . . . . . . . . 143

Troubleshooting Continuous Protection Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Installation and upgrade issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Component issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Configuration issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146General issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Backup and restore job issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Backup Exec Retrieve issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Database maintenance utilities ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Contents10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Resetting the standard logon .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Appendix A Third-Party Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

About Third-Party Legal Notices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158ACE and TAO are governed under the same license provided

below. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158ACE (The Adaptive Communication Environment) ... . . . . . . . . . . . . . . . . . . . . . . . . . 158TAO .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Apache Struts, Xerces C++ and Tomcat are governed under the same

license provided below .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Apache Struts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Xerces C++ .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Tomcat ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Definitions. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Grant of Copyright License. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Grant of Patent License. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Redistribution. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Submission of Contributions. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Trademarks. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Disclaimer of Warranty. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Limitation of Liability ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Accepting Warranty or Additional Liability. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Blowfish Encryption .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Curl/LibCurl ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Digital Encryption Standard (DES) - MIT .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165ICU .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166MD5 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Open SSL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Original SSLeay License .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168ReportCtrl.h.2.0.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170STLport ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Java 2 Runtime Environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

DEFINITIONS. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172LICENSE TO USE. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172RESTRICTIONS. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172LIMITED WARRANTY. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173DISCLAIMER OF WARRANTY. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173LIMITATION OF LIABILITY. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SOFTWARE UPDATES FROM SUN. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SOFTWARE FROM SOURCES OTHER THAN SUN. ... . . . . . . . . . . . . . . . . . . . 174TERMINATION. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

11Contents

EXPORT REGULATIONS. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174TRADEMARKS AND LOGOS. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175U.S. GOVERNMENT RESTRICTED RIGHTS. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 175GOVERNING LAW. .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175SEVERABILITY. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175INTEGRATION. ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175SUPPLEMENTAL LICENSE TERMS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Appendix B Maintaining accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

About accessibility in Continuous Protection Server ... . . . . . . . . . . . . . . . . . . . . . . 179About general keyboard navigation in Continuous Protection

Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180About keyboard navigation in dialog boxes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

List Boxes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Using keyboard shortcuts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Setting accessibility options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Contents12

Introducing SymantecContinuous ProtectionServer

This chapter includes the following topics:

■ About Symantec Backup Exec Continuous Protection Server

■ Components of Continuous Protection Server

■ How Continuous Protection Server works

■ What you can do with Continuous Protection Server

■ About backup strategies and planning

■ Where to find more information

About Symantec Backup Exec Continuous ProtectionServer

Symantec Backup Exec Continuous Protection Server helps ensure thatbusiness-critical data is always protected and always available. It combines provenBackup Exec data protection with replication technology and disk-based dataprotection to provide fast and reliable data backup and retrieval. It providescontinuous data protection and lets you restore data at a granular level frompoints in time throughout the day. You can also perform simultaneous backupsof multiple servers. Continuous Protection Server integrates with SymantecBackup Exec for Windows Servers for traditional tape-based data protection. Itdelivers integrated management through Backup Exec SmartLink technology.

1Chapter

Continuous Protection Server lets users restore their own data through aWeb-based data-retrieval tool. Users can safely retrieve their own files withoutIT assistance. Because the tool is Web-based, users do not need to install anysoftware or clients on their computers. Thus, no client software has to be updatedor maintained.

Continuous Protection Server is compatible with the following Symantec products:

Protects your application servers such asMicrosoft Exchange, SQL, and theContinuous Management Service. It alsoprovides long-term storage to various media.

Backup Exec (10d or later) for WindowsServers

Protects information that is created onremote and mobile personal computers.

Backup Exec (10d or later) Desktop andLaptop Option

Provides easy-to-use online disk storagemanagement for mission-critical, enterpriseWindows environments.

Storage Foundation for Windows

Components of Continuous Protection ServerTable 1-1 describes the components of Continuous Protection Server.

Table 1-1 Components of Continuous Protection Server

DescriptionComponent

The Backup Group includes the following components:

■ One Continuous Management Service

■ At least one Business Server

■ At least one Protection Server

■ CPS Administration Console

■ Web Restore Server Component (optional)

Backup Group

The Business Servers store the data that users save during the course of their dailyoperations. Once data is saved to the Business Server, the data can be backed up to aProtection Server. The Business Servers must reside in the same Backup Group as theProtection Server. You must install a Continuous Protection Agent on each Business Server.

Business Servers

The Protection Server is the destination of the CPS backup data. It is typically installed ata primary location or a central office. The Protection Server hosts the backup destinationswhere snapshots are taken and indexed. Also, the Web Restore Server Component lets usersretrieve data by Backup Exec Retrieve. More than one Protection Server can be installed inthe Backup Group.

Protection Server

Introducing Symantec Continuous Protection ServerComponents of Continuous Protection Server

14

Table 1-1 Components of Continuous Protection Server (continued)


The Continuous Management Service does the following:

■ Provides primary control of the CPS processes

■ Retains configuration settings from the Administration Console

■ Manages the CPS system

Note: You can install only one Continuous Protection Server in a Backup Group. You mustinstall the Continuous Protection Server before you install any other components. Also,the Continuous Protection Server should be installed on a server that has a fixed IP address.

See “Performing an initial installation” on page 41.

ContinuousManagement Service

The Continuous Protection Agent manages data collection during backup and restore jobs.You must install it on all Business Servers and Protection Servers in the Backup Group.

Continuous ProtectionAgent

The Administration Console controls all aspects of CPS, including defining data sourcesand destinations, creating backup and restore jobs, and defining backup and snapshotschedules. Additionally, the Administration Console is used to view and respond to alerts,monitor backup and restore jobs, and obtain product updates from Symantec.

AdministrationConsole

The Web Restore Server Component is a feature of the CMS that presents a Web view ofprotected data and the search interface. This snapshoting is accomplished withoutadministrator assistance on a Protection Server, although the administrator creates theschedule.

Web Restore ServerComponent

Backup Exec Retrieve is the gateway by which users access the Web Restore ServerComponent to retrieve files. Backup Exec Retrieve uses Internet browsers (Internet Explorer6.0 or later, and others). You do not need to install the Continuous Protection Server softwareon the users’ workstations.

Users can search by full or partial file name or browse to the location where their files arestored. They can also view all versions of a file that were backed up and select a copy of thefile they need. Users can select a file, and then download a copy of it without assistancefrom system administrators.

Backup Exec Retrieve

The Indexing component maintains a directory of files that are available to users for fileretrieval using the Web Restore Server Component and Backup Exec Retrieve. The Indexingcomponent is an optional feature that is installed on any Protection Server that users accessfor file retrieval using Backup Exec Retrieve. The Indexing component allows searches byfile name, file versions, and recent activity.

Indexing Component

This component lets users view the combined status of CPS and Backup Exec jobs in theBackup Exec Administration Console.

Backup ExecSmartLink

15Introducing Symantec Continuous Protection ServerComponents of Continuous Protection Server

Table 1-1 Components of Continuous Protection Server (continued)


Continuous Protection Server uses the Symantec Backup Exec Remote Agent for WindowsSystems (Remote Agent) to access System State information for backup and restore. RemoteAgent also enables Backup Exec to back up Protection Servers and the CMS to tape efficiently.

Remote Agent is an optional component.

You should install the Remote Agent on the following servers:

■ On Business Servers if you want to back up System State

■ On Protection Servers that you want to back up with Backup Exec

■ On servers that host the CMS and that you back up with Backup Exec

Remote Agent is not required when CPS is installed on Backup Exec because the serveralready contains Remote Agent functionality. However, the Remote Agents that are usedby CPS and Backup Exec must be the same version (11d or later).

Remote Agent forWindows Systems(Remote Agent)

Symantec LiveUpdate is installed with the Administration Console. LiveUpdate notifiesadministrators when updates to installed Symantec products become available for download.LiveUpdate connects to the Symantec LiveUpdate server by the Internet.

Symantec LiveUpdate

See “How Continuous Protection Server works” on page 16.

How Continuous Protection Server worksFigure 1-1 shows an example of how Continuous Protection Server works withBackup Exec to protect your business data.

Introducing Symantec Continuous Protection ServerHow Continuous Protection Server works

16

Figure 1-1 Overview of the Continuous Protection Server model

WebServer

End-User Workstations(Connected to a localBusiness Server)

Business Servers(Local or Remote Offices)

(ContinuousProtectionAgent)

Protection Server

(ContinuousProtectionAgent)

Snapshotsand

Indexing

Copy

Center

Backup Execmedia server

DataArchived toTape or DiskStorage

CPSAdmin

Console

Backup ExecAdmin

Console

ContinuousManagementServer

1

2

3 6

4

7 9

8

5

The following scenario provides an example of how you can use ContinuousProtection Server with Backup Exec to back up and restore data:

17Introducing Symantec Continuous Protection ServerHow Continuous Protection Server works

Users save files and folders to local file servers (Business Servers) as part oftheir normal daily work. Business Servers are interconnected and together forma common Backup Group.

See “Configuring Business Servers” on page 63.

1

The Continuous Protection Server Backup Destination Wizard designates aspecific directory on a specific Protection Server where the data is backed up.The backup-destination definition includes the schedule for the data snapshotsand the policies for snapshot retention.

Different servers can be designated as backup destinations based on your needs.For example, separate destinations can be created for financial data on a serverin the accounting department, employee data on a server in human resources,and customer records on a server in the sales department.

See “Managing backup destinations” on page 69.

2

You can use the Backup Job Wizard to create Continuous Protection Serverbackup jobs to back up data from one or more Business Servers to a ProtectionServer. When you create a job, you select the data to be backed up and theschedule for the backup job. You can schedule CPS backup jobs to run at specifictimes (periodically), as files incur any changes (continuously), or as needed (ondemand).

See “Creating CPS backup jobs” on page 92.

3

As soon as the data is backed up to the Protection Server, scheduled snapshotsof the data are made. The data is then indexed and made available to the WebRestore Server.

See “Managing snapshots” on page 72.

4

Users retrieve specific files and folders from the Web Restore Server to theirworkstations by using Backup Exec Retrieve and their Internet browsers. Becausethe data was backed up with specified snapshots, users can select specificversions of their data to be restored.

5

If a system failure occurs at one or more Business Servers, the backed up datacan be quickly restored from the Protection Server to the Business Server.

See “About restoring data with Continuous Protection Server” on page 103.

6

After the data is backed up to the Protection Server, you can back up the datato Backup Exec to archive the data to tape or disk for long-term storage.

See “Backing up CPS with Backup Exec” on page 127.

7

Introducing Symantec Continuous Protection ServerHow Continuous Protection Server works

18

If a system failure or data loss occurs at a Protection Server, Backup Exec canquickly restore the data back to the Protection Server or back to a BusinessServer.

See “Restoring Continuous Protection Server with Backup Exec” on page 129.

See “Retrieving files by using Backup Exec Retrieve” on page 111.

8

The Backup Exec SmartLink component lets you view the status of ContinuousProtection Server backup jobs in the Backup Exec Job Logs and Alerts. Thisoption lets administrators determine the quality and completion of theContinuous Protection Server jobs before or during the Backup Exec backup job.

See “Monitoring CPS jobs in Backup Exec” on page 131.

9

What you can do with Continuous Protection ServerTable 1-2 describes the features and benefits of Continuous Protection Server.

Table 1-2 Features and benefits of Continuous Protection Server

DescriptionFeature

CPS backs up files on a network (LAN or WAN) and writes them immediately to a ProtectionServer with no wait time. You do not need to take incremental or differential backups onservers that are protected by CPS. This feature keeps productivity high while protectingthe organization’s information.

Continuous dataprotection

Only the changed data is captured and protected. This granular (or byte-level) protectionreduces the amount of data moving across the network, thereby increasing efficiency.

Byte-level protection

Backup Exec Retrieve enables users to retrieve their own files without contacting IT, whichreduces administrator requests and improves service levels. To retrieve files, you use aWeb-based search engine to search for and download a file from the Internet. Because youonly need a standard Web browser to retrieve files, there is no client software or agent toinstall on computers.

Web-based user fileretrieval

Entire servers can be backed up, including system files. In the event of a system-wide failure,such as a virus attack, Business Servers (sources) can be quickly restored to a previousstate.

Full system restore

Provides multi-streaming, which enables multiple file servers to be continuously backedup at one time to a single Protection Server.

Simultaneous backups

The Administration Console enables users to define backup destinations, customize jobs,view status, and learn of any issues that arise.

AdministrationConsole

19Introducing Symantec Continuous Protection ServerWhat you can do with Continuous Protection Server

Table 1-2 Features and benefits of Continuous Protection Server (continued)

DescriptionFeature

CPS leverages Volume Shadow Copy Service (VSS) snapshots to provide versioning of files.This allows users or administrators to recover a previous version of a document. Snapshotsettings provide administrators with greater flexibility in managing and retaining snapshots.

Point-in-timesnapshots

Existing Symantec Backup Exec users can view some CPS activities from within the BackupExec Administration Console. For example, you can view logs for CPS backup jobs. You alsocan use Backup Exec to move disk-based backups to tape for long-term storage.

SmartLink toSymantec Backup Exec

Back up only the specific data you need. Save on system resources by backing up only theinformation that needs to be recovered.

Flexible backupoptions

Back up files on demand, or schedule periodic and continuous backups to run automatically.Customized backupschedules

Administrators can set the maximum amount of bandwidth to be used for continuous dataprotection jobs.

Bandwidth throttling

Continuous Protection Server protects open files during continuous protection.Open file protection

Retention properties define how long to keep daily, weekly, and monthly backups on disk.Customized retentionproperties

Automatically resumes a continuous protection job when lost connections are restoredwithout requiring intervention from an administrator.

Auto job resume

Continuous Protection Agents can be push installed to remote servers from a central console.IT resources do not need to be at that office or location where continuous protection isinstalled or taking place.

Push installation

Intuitive search capabilities enable users to find files by file name, modification date, specificfile type, or file size.

Discovery

Information can be backed up from sources in the current network, as well as from newservers as they are added to the Backup Group.

Scalable protection

Continuous Protection Server captures system state information, reducing the time andeffort to recover server configuration information.

System State backup

Uses Symantec LiveUpdate to provide periodic product updates.Symantec LiveUpdate

Supports 64-bit native processors for Business and Protection servers.64-bit native support

Supports Internet Protocol 6 (IPv6).IPv6 support

Includes a Settings utility where user-configurable registry settings can be managed.Settings Utility

Introducing Symantec Continuous Protection ServerWhat you can do with Continuous Protection Server

20

Table 1-2 Features and benefits of Continuous Protection Server (continued)

DescriptionFeature

Backup Exec Retrieve allows users of Backup Exec Desktop and Laptop Option (DLO) torestore files that were backed up by DLO directly back to their workstations.

DLO file recovery

Supports continuous protection of Exchange servers to the Backup Exec AdministrationConsole.

Continuous protectionof Exchange

About backup strategies and planningOne of the most important assets to any business is the information that is storedon its computers.

Having a strategic backup plan can save time and money by requiring less timefor reconstructing information in the event of a failure or loss. ContinuousProtection Server can help streamline backup and file recovery strategies.

The main purpose of your backup strategy is to recover and restore informationas quickly as possible after a loss. Secondarily, you need to manage your resourceseffectively to save money. A well-designed backup strategy plays a key role inyour ability to restore lost files quickly.

Data protection considerationsBefore you install and use CPS, you should consider the following questions tohelp assess your backup requirements:

■ How much information needs to be saved and protected?

■ How many servers need to be backed up?

■ How much information can you store and which servers should store it?

■ How long should the data be retained and available?

■ Has the System Information for the server been modified so that it warrantsbackup protection?

■ What information is business-critical and needs to be backed up continuously(every time the information changes)?

■ What information you back up hourly, daily, weekly, monthly, or at irregularintervals?

■ What information should you back up on an as-needed (manual) basis only?

■ Are shared folders being used, or do all users have unique folders in whichtheir files are stored?

21Introducing Symantec Continuous Protection ServerAbout backup strategies and planning

■ Who should have access to the Continuous Protection Server AdministrationConsole for the purpose of changing settings, scheduling backups, restoringinformation, and managing system alerts?

■ Who should have access to various backup destinations for the purpose ofrestoring data?

■ How should the backup destinations be organized for access?

■ How often should data snapshots be captured and how many should beretained?

About backup job schedulesPerhaps the most important part in developing a strong backup strategy is decidingwhat to back up and when.

The frequency with which you back up files can affect many things including thefollowing:

■ The quality of the backup

■ The resources that are required to process and store the information

■ The process of locating information that you need to restore

There are multiple levels of backup schedules that work well together and eachorganization might use a combination of these practices. Most importantly, allinformation on your servers should be backed up on a regular basis. Less-essentialinformation should be backed up periodically. Pertinent data, such as data thatis used for compliance purposes or that is related to your core products or services,should be backed up continually.

See “Creating CPS backup jobs” on page 92.

See “Changing a backup job schedule” on page 98.

Table 1-3 describes the types of scheduled backup jobs that you can create.

Table 1-3 Types of scheduled backups

DescriptionScheduled backup type

Files that are manually backed up by a user on an “as needed”basis.

On demand

Introducing Symantec Continuous Protection ServerAbout backup strategies and planning

22

Table 1-3 Types of scheduled backups (continued)

DescriptionScheduled backup type

Files that are backed up on a routine basis. You select thedays the backups are run and the time the backups begin.For example, you can back up your personnel data each day,Monday through Friday, at 5:00 P.M. Another example wouldbe to back up all of the Business Servers every Saturday,beginning at 1:00 A.M.

Regular

Files that are backed up on certain days of the week and runperiodically on timed intervals. For example, you can backup your sales proposals every hour, your development dataevery three hours, your quality assurance data every fourhours, and so on.

Periodic

Critical business files, such as customer data, that are backedup continuously. Every time a file changes, the changes arecopied to the Protection Server. There is no wait time orpreset interval when the information is copied. The backuptakes place immediately, even while files are open.

Continuous

Where to find more informationThe product documentation provides assistance for using Backup Exec ContinuousProtection Server to your advantage. You can access the information that youneed from the product CD and the Symantec Web site.

See “Accessing the Continuous Protection Server documentation” on page 23.

See “Accessing the online Help” on page 24.

See “Accessing the Symantec Technical Support Web site” on page 25.

See “Accessing the Symantec Backup Exec Web site” on page 25.

Accessing the Continuous Protection Server documentationThe Backup Exec Continuous Protection Server documentation is available on theproduct CD and installed with each Administration Console.

Table 1-4 describes the manuals and help that comprise the Continuous ProtectionServer documentation set.

23Introducing Symantec Continuous Protection ServerWhere to find more information

Table 1-4 Continuous Protection Server documentation set

DescriptionDocument title

Continuous Protection Server is written for systemadministrators and delivered in Adobe Acrobat (PDF) format.

Continuous ProtectionServer Administrator’sGuide

(CPSadmin_XX.pdf)

The Continuous Protection Server Quick Installation Guideis intended to assist you while installing the product andcomponents. It is delivered in Adobe Acrobat (PDF) format.

Continuous ProtectionServer Quick InstallationGuide

(CPSquick_xx.pdf)

Installed and stored on the server, the Help file is accessiblefrom the Administration Console.

Continuous ProtectionServer Help files

(CPSconsole_XX.chm)

An HTML file containing any product changes andinstallation issues that should be reviewed before installingthe Continuous Protection Server product.

Continuous ProtectionServer Readme files

(Readme_XX.html)

The “XX” in the filename indicates the language of the file. The choices are EN(English), ES (Spanish), FR (French), IT (Italian), DE (German), JP (Japanese), KO(Korean), CH (Traditional Chinese), and ZH (Simplified Chinese).

To access the Continuous Protection Server documentation

1 Insert the product CD into the CD-ROM drive.

2 Using Windows Explorer, navigate to and open the Docs directory.

3 Double-click the file to open it.

Accessing the online HelpOnline Help is installed with the Continuous Protection Server software.

To access the online Help

1 Install the Continuous Protection Server software.

2 Click Help.

Introducing Symantec Continuous Protection ServerWhere to find more information

24

Accessing the Symantec Technical Support Web siteOn the Symantec Technical Support Web site, you can find the latest programupdates, patches, online tutorials, Knowledge Base articles, and virus removaltools.

To access the Symantec Support Web site

◆ On the Internet, go to the following URL:

www.symantec.com/techsupp

Accessing the Symantec Backup Exec Web siteOn the Symantec Backup Exec Web site, you can find online technical information,user forums, as well as links to product information, white papers and tutorials.

To access the Symantec Backup Exec web site

◆ On the Internet, go to the following URL:

http://backupexec.com

25Introducing Symantec Continuous Protection ServerWhere to find more information

Introducing Symantec Continuous Protection ServerWhere to find more information

26

Installing ContinuousProtection Server


■ Before you install

■ System requirements for the product

■ What gets installed and where

■ Performing an initial installation

■ Push-installing Continuous Protection Server components

■ Upgrading to Continuous Protection Server 12.5

■ Modifying Continuous Protection Server installations

■ Uninstalling the Continuous Protection Server

■ Uninstalling a Continuous Protection Agent

Before you installYou should do the following tasks before you install Continuous Protection Server:

See “Guidelines for installation” on page 28.Review the guidelines for installingContinuous Protection Server forinformation about the order in whichthe components should be installed.

2Chapter

See “Checking your environment beforeinstallation” on page 29.

Run the Environment Check tool tocheck for issues that could affect theinstallation.

See “Upgrading to Continuous Protection Server12.5” on page 50.

If you are upgrading from a previousversion, review the productdocumentation for any compatibilityissues that could affect the installation.

See “File system filter driver compatibility”on page 31.

Review the Readme file for informationabout incompatible products thatshould be turned off or uninstalledbefore you install ContinuousProtection Server.

See “Understanding the Continuous ProtectionServer service account” on page 31.

Review the product documentation forinformation about setting up theservice account for ContinuousProtection Server.

See “System requirements for the product”on page 32.

Verify that the systems on which youwant to install Continuous ProtectionServer and its components meet thesystem requirements.

See “Firewall support ” on page 36.Configure your firewall to allow trafficthrough the ports that are used byContinuous Protection Server.

Guidelines for installationYou should install Continuous Protection Server as follows:

■ Install the Continuous Management Service and an Administration Consolebefore you install other Continuous Protection Server components.

■ You should install the Continuous Management Service and the AdministrationConsole on a dedicated server if possible.See “Performing an initial installation” on page 41.

■ Use the Administration Console to push-install additional AdministrationConsoles and Continuous Protection Agents to other Business Servers orProtection Servers.See “Push-installing Continuous Protection Server components” on page 47.

■ As necessary, use the Administration Console to install additional components.

Installing Continuous Protection ServerBefore you install

28

Checking your environment before installationThe Symantec Backup Exec Environment Check tool lets you assess your existinghardware and software resources for compatibility with the Continuous ProtectionServer software installation.

The Environment Check tool assesses and reports on the following pre-installationconfigurations:

■ If the computer meets the minimum requirements for installation, such as theoperating system, disk and memory space, and sufficient logon accountprivileges.See “System requirements for the product” on page 32.

■ If third-party software that uses Continuous Protection Server ports isconfigured correctly.

■ If required components are installed, and if they are versions that arecompatible with Continuous Protection Server.

■ If previous versions of Continuous Protection Server are installed.

■ If storage device hardware and associated drivers are properly installed andrecognized by the Windows operating system.

Table 2-1 lists the results that are reported for each flagged item.

Table 2-1 Results of flagged items

ResultFlagged item

There are no incompatibilities to prevent the Continuous ProtectionServer installation. For hardware, this result indicates that thehardware configuration is recognized by Continuous Protection Server.

Passed

An incompatibility with Continuous Protection Server exists, but canbe resolved. Or, a condition of which you should be aware.

Warning

An incompatibility with Continuous Protection Server exists, and theinstallation failed. Some action is required before you can successfullyinstall Continuous Protection Server.

Failed

Although the Environment Check runs automatically during installation, you maywant to run it manually before installing Continuous Protection Server or beforebacking up data with Continuous Protection Server.

29Installing Continuous Protection ServerBefore you install

To check your environment before installation

1 In the CD browser, click Installation, and then click Start the Backup ExecContinuous Protection Server Environment Check.

2 Click Next.

3 Select one of the following:

Checks the configuration of the local computerLocal Environment Check

Checks the configuration of a remote computerRemote Environment Check

4 Click Next.

5 If you checked Remote Environment Check in step 3, do one of the following:

■ To select the name of computer from a list, click Add Server FromList.Select the computer from the list, and then click Next.

■ To add the name of a computer manually, click Add ServerManually.Type the name of the domain and the computer name, and then click OK.Type the user name and password for this computer, and then click OK.

■ To remove the name of a computer from the list of computers on whichthe Environment Check will run, select the computer from the list, andthen click Remove.

6 Review the results of the Environment Check, especially those items thatwere flagged as Failed or Warning.

To save the results of the Environment Check, check SaveResults To.

7 To change the location where the Environment Check results are saved, clickChange Path to browse to a new location.

8 Click Finish.

Continuous Protection Server and Backup Exec compatibilityBe careful when installing the CPS Protection Agent on the servers that have olderversions of Remote Agent installed. The CPS installer can optionally upgrade theRemote Agent components to version 12. However, this upgrade breaks existingbackup functionality if the Backup Exec Media Sever is a 10.x or earlier version.The installer will always alert you before upgrading the Remote Agent. The sameconsideration should be given when upgrading Backup Exec if that is where theContinuous Management Service will run. If Backup Exec version 10.x is upgradedto 12, then it is no longer able to back up any of its existing 10.x clients.

Installing Continuous Protection ServerBefore you install

30

File system filter driver compatibilitySoftware that uses file system filter drivers, such as disk defragmenter utilities,certain open file agents and some virus protection software, cannot be used withthis product as there could be conflicts with the CPS file system filter driver.

If an incompatible product is found on a CPS server, starting both CPS and theincompatible product could cause the system to become unstable or crash. Likewise,enabling both products at system start time could prevent the system fromstarting. System Restore allows the system to return to its previous configuration.

You must remove incompatible products or make them unavailable before youinstall CPS. If CPS is already installed on the system, do not enable or start theother product while CPS is running.

For more information, see the Readme file accompanying this release for the mostcurrent list of products with incompatible filter drivers.

Understanding the Continuous Protection Server service accountSome CPS services are run in the context of a user account that is configured forthe CPS system services. To specify an account for CPS, enter a name and passwordof an Administrator account for the CPS services to use.

The services will not start if the account password has expired. Also, if the servicestry to start too many times with an expired password, the user may get locked outof the account.

If the computer that is hosting the CPS services is in a domain, enter a Domainuser’s account. The CPS installer adds the account to the local Administrator’sgroup.

If this computer is in a workgroup, enter an Administrator’s account, or anequivalent account that is part of the Administrator’s group on the computer.

The account that is designated for the CPS services (whether it is a new accountor an existing account) will be assigned the following rights:

■ Log on as a service.

■ Administrator rights (provides complete and unrestricted rights to thecomputer).

On a computer running Windows Server 2003, you cannot install CPS using aservice account that has a blank password. If you attempt to do so, an errormessage is displayed. You can configure Windows to allow for blank passwords.

For more information, see the Windows documentation.

31Installing Continuous Protection ServerBefore you install

The account that is used must be valid on each node in the Backup Group. Thisaccount may require establishing a Domain Trust relationship.

If a cross domain trust exists between the computers push installing from and to,the account that is running from the installing computer must be present in thelocal administrators group of the computer being push installed to.

When operating in a workgroup environment, all nodes in the backup group mustrun in non-secure mode. (Pre and post-job scripts run under the service account,although additional rights may be required.)

System requirements for the productTo install and use this product, your hardware and software requirements mustmeet the minimum requirements for each Continuous Protection Servercomponent.

Actual production requirements may require greater resources than the notedminimum requirements. Additionally, where several components exist on thesame server, the requirements are cumulative.

See “System requirements for Business Servers” on page 32.

See “System requirements for Continuous Management Service and ProtectionServers” on page 33.

See “System requirements for Administration Console” on page 34.

See “System requirements for Web Restore Server Component” on page 35.

See “System requirements for Indexing Component” on page 36.

See “System requirements for Backup Exec Retrieve” on page 36.

See “Firewall support ” on page 36.

System requirements for Business ServersBusiness Servers store data that is routinely used and saved by users to file servers,and that is backed up to a Protection Server.

Table 2-2 lists the system requirements for Business Servers.

Installing Continuous Protection ServerSystem requirements for the product

32

Table 2-2 System requirements for Business Servers

RequirementsComponent

This component is supported on the following operating systems:

■ Microsoft Windows 2000 Server with Service Pack 4

■ Microsoft Windows 2000 Advanced Server with Service Pack 4

■ Microsoft Windows Server 2003 x64 Editions

■ Microsoft Windows Server 2003 (including R2, but not Data Center) with ServicePack 1

■ Microsoft Windows Server 2003, Small Business Server with Service Pack 1

■ Microsoft Windows Storage Server 2003 with Service Pack 1

■ Microsoft Windows Server 2008, including Windows Server Core

Supported OperatingSystems

512 MB, 1 GB recommendedRAM

25 MBDisk Space: ContinuousProtection Server Software

100 MB (10 GB or more recommended)Disk Space: Journals

100 MBDisk Space: Logs and Alerts

100 MB or more depending on server configuration (minimum 1 GB recommendedif backing up System State)

Disk Space: Named Objects

Uninterruptible power supply (UPS) such as battery backup power, recommendedUPS

Microsoft Data Access Components (MDAC) version 2.5 or laterUtilities

System requirements for Continuous Management Service andProtection Servers

Data is backed up from Business Servers to Protection Servers.

Table 2-3 lists the system requirements for Continuous Management Server andProtection Servers.

33Installing Continuous Protection ServerSystem requirements for the product

Table 2-3 System requirements for Continuous Management Service andProtection Servers


The Continuous Management Service and Protection Servers are supported on thefollowing operating systems:

■ Microsoft Windows Server 2003 x64 Editions

■ Microsoft Windows Server 2003 family (including R2, but not Data Center) withService Pack 1

■ Microsoft Windows Server 2003, Small Business Server with Service Pack 1

■ Microsoft Windows Storage Server 2003 with Service Pack 1




58 MBDisk Space: ContinuousProtection Server Software

100 MBDisk Space: Logs and Alerts

1 GB or more as requiredDisk Space: IndexingComponent

The Protection Server should have at least four separate volumes for idealperformance, such as the following:

■ System volume

■ Journals volume

■ Backup destination volume

■ Snapshot storage volume for backup destination

Volumes

Uninterruptible power supply (UPS) such as battery backup power, recommendedUPS


System requirements for Administration ConsoleAny number of Administration Consoles may be installed in the Backup Group.

Table 2-4 lists the system requirements for the Administration Console.


34

Table 2-4 System requirements for Administration Console


The Administration Console is supported on the following operating systems:

■ Microsoft Windows 2000 Professional with Service Pack 4




■ Microsoft Windows XP Professional

■ Microsoft Windows XP Professional x64 Edition



512 MB, 1GB recommendedRAM

35 MB for Console alone, plus the following:

■ 250 MB for 32-bit push-install files

■ 275 MB for 64-bit push-install files

10MB for Settings Utility, plus (if not already installed) the following:

■ 300 MB for .Net framework 2.0 (32-bit version)

■ 600 MB for .Net framework 2.0 (64-bit version)

Disk Space

Microsoft Data Access Components (MDAC) version 2.5 or later.

Net Framework 2.0 is installed for Settings Utility, if needed

Utilities

System requirements for Web Restore Server ComponentWeb Restore Server component is installed on the computer that hosts theContinuous Management Service.

Table 2-5 lists the system requirements for Web Restore Server Component.

Table 2-5 System requirements for Web Restore Server Component

DescriptionItem


25 MBDisk Space: InstalledSoftware



System requirements for Indexing ComponentThe Indexing Component is installed with each Continuous Protection Agent.

Table 2-6 lists the system requirements for Indexing Component.

Table 2-6 System requirements for Indexing Component

DescriptionItem


40 MBDisk Space: InstalledSoftware

As requiredDisk Space: Index


System requirements for Backup Exec RetrieveBackup Exec Retrieve is the gateway by which users access the Web Restore ServerComponent to retrieve files.

Table 2-7 lists the system requirements for Backup Exec Retrieve.

Table 2-7 System requirements for Backup Exec Retrieve

DescriptionItem

Backup Exec Retrieve is supported on the following operating systems:

■ Microsoft Windows 2000 Professional with Service Pack 4




■ Microsoft Windows XP Professional Service Pack 1 or later

■ Microsoft Windows Vista



Internet Explorer (6.0 or later). Backup Exec Retrieve also works with other Internetbrowsers, although screen layouts and other functionality may vary.

Supported Browsers

Firewall supportFirewalls must be configured to allow the following ports through to supportContinuous Protection Server. CPS automatically creates a firewall exception list.


36

If any of the default port settings are changed on one computer, they must bechanged on all computers in the Continuous Protection Server Backup Group.

Warning: Incorrectly editing registry keys may severely damage your system.Before making changes to the registry, you should back up any valued data on thecomputer.

Table 2-8 lists the default port settings for Continuous Protection Server.

Table 2-8 Default port settings for Continuous Protection Server

Editable Registry KeyPort TypeDefault PortNumberService Name

HKLM\Software\Symantec\ENL\Network.TCPIPUDP1804Network HelperService (ENL)

HKLM\Software\Symantec\Backup ExecCPS\Parameters\Communications\FFXport

TCP20481CPA Data

HKLM\Software\Symantec\Backup ExecCPS\Parameters\RPC Interface\RxRsaStaticPort

TCP20483CPA RPC

HKLM\Software\Symantec\Backup ExecCPS\Parameters\RPC Interface\RxRmsStaticPort

TCP20485CMS RPC

You can change the Web Restore Server Componentport numbers.

For information about how to configure the BackupExec Continuous Protection Server Web Server, go tothe following URL:

http://seer.entsupport.symantec.com/docs/278249.htm

TCP8181Web Restore ServerComponent (http)

You can change the Web Restore Server Componentport numbers.

For more information about how to configure theBackup Exec Continuous Protection Server Web Server,go to the following URL:


TCP8443Web Restore ServerComponent (https)

Additionally, the Continuous Protection Server Services Manager, push-install,and Settings Utility utilize Windows file sharing (NetBIOS or SMB) ports. In orderfor these services to function, you must configure the ports.

Table 2-9 lists the ports that you should not open to the Internet.


Table 2-9 Ports that should not be opened to the Internet

Editable Registry KeyPort TypeDefault PortNumberService Name

NoTCP445Windows

(NetBIOS over TCP/IP)

NoUDP

UDP

TCP

137

138

139

Windows

(NetBIOS

Continuous Protection Server also uses the following ports on the local server:

■ 2638

■ 9000-9003

■ 10000

■ 13730

■ 14300

■ 20487

Because these ports are only used on the local server, it is not necessary (orrecommended) that they be opened through your firewall.

What gets installed and whereAfter the Continuous Protection Server installation completes, depending on theContinuous Protection Server components that are installed, a number of files,services, drivers, and registry entries are made to the system.

See “Folders that are installed” on page 38.

See “Drivers that are installed” on page 39.

See “Continuous Protection Server services that are installed” on page 39.

See “Registry entries” on page 40.

See “Understanding the Continuous Protection Server service account” on page 31.

Folders that are installedBy default, Continuous Protection Server installs files and folders to C:\ProgramFiles\Symantec\Continuous Protection Server\.

Table 2-10 describes the folders that are installed.

Installing Continuous Protection ServerWhat gets installed and where

38

Table 2-10 Folders that are installed

DescriptionFolder

The ASA folder contains the Win32 and Charsets folders. The Win32 folder contains theASA database engine and its backup files, DBMS service, ASA support files, and ASA querytool. The database backup (cpsDBBackup.exe) and validation (cpsDBValidate.exe) utilitiesare also contained in this folder.

The Charsets folder contains ASA Unicode support files.

ASA (Adaptive ServerAnywhere)

Continuous Protection Server uses a third-party indexing service that is called Autonomy.The Autonomy folder contains all the files and services that are used by the indexing service.The Autonomy log files are also maintained in this folder.

Autonomy

The Database folder contains the Continuous Management Service (rms.db) and ContinuousProtection Agent (rsa.db) databases, their backup copies, and the related database files.

Database

The Drivers folder contains the Continuous Protection Server filter driver.Drivers

The Install folder contains Continuous Protection Server, Remote Agent, and SymantecLiveUpdate installation files for push installs.

Install

The Services folder contains Continuous Protection Server service executable files andassociated support files.

Services

The Logs folder contains the Network Helper (ENL) log and trace logs.Logs

Drivers that are installedContinuous Protection Server installs the filter driver CpsFsJnl.sys. This driverdetects changes in protected files and records the changes to the Protection Server.

Continuous Protection Server services that are installedTable 2-11 describes the services that Continuous Protection Server installs.

Table 2-11 Services that are installed

DescriptionShort nameService name

The Continuous Management Service service is present only on the serverhosting the Continuous Management Service. It manages theconfiguration for all Backup Exec Continuous Protection Agents in theBackup Group.

RxRMSBackup ExecContinuous ProtectionAdministration Service

39Installing Continuous Protection ServerWhat gets installed and where

Table 2-11 Services that are installed (continued)

DescriptionShort nameService name

The Continuous Protection Agent service is present on all servers onwhich the Continuous Protection Agent is installed. It enables ContinuousProtection Server to back up data from the server or move the backed-updata on the server.

RxRSABackup ExecContinuous ProtectionAgent

Allows communication between Continuous Protection Server and BackupExec to facilitate continuous protection of Microsoft Exchange transactionlogs.

RepBrokerSvcBackup ExecContinuous ProtectionBroker Service

Communicates with Volume Shadow Services to save and store theContinuous Protection Server’s configuration information.

rxWriterSvcBackup ExecContinuous ProtectionConfiguration Writer

Controls the configuration database for all Continuous Protection Serverinformation.

RxASABackup ExecContinuous ProtectionDatabase

Captures system information and file share information.RxNoServiceBackup ExecContinuous ProtectionSystem State Manager

Enables the Continuous Management Service to group and discoverContinuous Protection Agents and communicate with them.

ENLBackup ExecContinuous ProtectionNetwork Helper (ENL)

Indexes files that are backed up using Continuous Protection Server andpresents these files after a search operation from the Web RetrievalInterface or the Administration Console.

SUIRBackup ExecContinuous ProtectionIndexing Service

Controls the Continuous Protection Server Web Restore backend interface.RxWRGBackup ExecContinuous ProtectionWeb Restore Backend

Controls the Continuous Protection Server Web Restore frontendinterface.

RxWebAppBackup ExecContinuous ProtectionWeb Restore Frontend

The Web Server service.VRTSwebSymantec Web Server

Registry entriesContinuous Protection Server adds the following registry keys:

■ HKLM\SOFTWARE\Symantec\Backup Exec CPS

Installing Continuous Protection ServerWhat gets installed and where

40

This location stores information about the journal directories, ContinuousProtection Server installation path, Continuous Management Service databaseinstallation directory, Continuous Protection Server parameters, andContinuous Protection Server build details.

■ HKLM\SYSTEM\CurrentControlSet\Services\This location stores information about the Continuous Protection Serverdatabase technology (Adaptive Server Anywhere, version 9), file system filterdriver, file system journal writer driver, and the file system recognizer driverconfiguration.

Registry entries can be changed using the Settings Utility.

See “Accessing the Settings Utility” on page 79.

Performing an initial installationA typical and fully functional Continuous Protection Server Backup Group includesthe following components:

■ A server that has the Continuous Management Service, the ContinuousProtection Agent, the Administration Console, the Web Restore ServerComponent, and Indexing Component installed. This server becomes the centralmanagement point in the Backup Group.

■ A Continuous Protection Agent on each Business and Protection Server withthe Indexing Component installed on each Protection Server.

■ Any number of Administration Consoles.

Note: The Continuous Management Service components can be installed on aBackup Exec server or on a stand-alone server. If Continuous Protection Serveris installed on Backup Exec, then that Backup Exec installation must be upgradedto Backup Exec version 12.5. If Continuous Protection Server is installed on astand-alone server, then the 12.5 version of Remote Agent is also installed. ARemote Agent is not installed on Backup Exec.

The first step in creating a fully functional environment is configuring the serverthat hosts the Continuous Management Service. Establishing the ContinuousManagement Service is usually accomplished by performing an initial installationfrom the CD.

Continuous Protection Server application files that should be installed during theinitial installation include the Continuous Management Service and anAdministration Console. If the server hosting the Continuous Management Servicewill also be a Business or Protection Server, a Continuous Protection Agent must

41Installing Continuous Protection ServerPerforming an initial installation

also be installed. The Web Restore Server Component, Indexing Component, andthe SmartLink application are also installed. The Remote Agent is installedoptionally during the initial installation with a Continuous Protection Agent.Symantec LiveUpdate is installed automatically with an Administration Console.

Firewalls need to be manually reconfigured for CD installation and pushinstallation. Alternatively, firewalls can be turned off during the installationprocess.



To use the versioning capabilities of Backup Exec Retrieve, Protection Serversmust be running Windows Server 2003.

See “System requirements for Continuous Management Service and ProtectionServers” on page 33.

Note: After installing Continuous Protection Server on a computer runningWindows Server 2003, you might receive an error message that the Network LoadBalancing Service failed to start. Microsoft reports the cause as: “Although networkLoad Balancing (NLB) is not currently installed, some NLB registry keys might bepresent in the registry.” Although Microsoft Knowledge Base Article 268437describes the problem as applying to Windows 2000 Advanced Server, the fix alsoworks for Windows Server 2003.

For more information, see the Microsoft article entitled “Network Load Balancing,Windows 2000 Advanced Server” at the following URL:

www.microsoft.com

Administrator rights are required on the computer where the software is beinginstalled when performing a CD installation.

To perform an initial installation

1 Close all other programs that may be running.

2 If Autoplay is enabled, the Install should automatically launch when theCD-ROM is inserted in the drive. If Autoplay is not enabled, double-clickbrowser.exe file from the CD-ROM or download directory.

3 Select the language, and then click OK.

4 The welcome screen for Backup Exec Continuous Protection Server CDprovides links to access various areas of the installation CD. After reviewingthe various product information, click Installation.

Installing Continuous Protection ServerPerforming an initial installation

42

5 Click Start the Backup Exec Continuous Protection Server EnvironmentCheck, and then click Next.

6 Select either Local Environment Check or Remote environment check.

7 Do one of the following:

■ If the Environment Check does not reveal any issues that may prevent asuccessful installation of Continuous Protection Server, click Finish.

■ If the Environment Check reveals issues that may prevent a successfulinstallation of Continuous Protection Server, correct the issues beforeattempting to install again.

8 Select Start the BackupExec Continuous Protection Server Installation toinstall Continuous Protection Server, and then click Next.

Continuous Protection Server will determine whether the computer is a 32-bitor 64-bit server and install the appropriate version of the software.

9 Review the Continuous Protection Server Installation Wizard welcome screen,and then click Next.

10 Read and accept the license agreement on the License Agreement screen, andthen click Next.

11 Select one of the following methods to enter license keys, and then clickNext.

In the License Key box, type the license keynumber, and then clickAdd. Repeat this stepfor each license key for each option or agentyou want to add.

To enter license keys manually

Click Import, and then select thecpssernum.xml file.

To import license keys from a file

Leave the license key field blank, and thencontinue with step 14.

To install an evaluation version

The license keys you entered are saved to the cpssernum.xml file, located inthe Windows or WINNT directory.


12 On the Local Features screen, select the Continuous Protection Servercomponents that you want to install, and then click Next.

Check to install an Administration Console that allows for the managementand monitoring of activities within the Backup Group. This option will alsoinstall Symantec LiveUpdate 3.0.

Administration Console

Check to install the Continuous Protection Server Settings Utility, whichallows changes to be made to various registry settings on this computer.

Settings Utility

If it is not already installed, this option will also install .Net Framework2.0.

Check this option to install the files needed to push install othercomponents.

Push install Support

x86 Support to install components needed to push-install to 32-bitcomputers.

x64 Support to install components needed to push-install to 64-bitcomputers.

Check to install a Continuous Management Service, which must be installedto create and manage the Backup Group.

Continuous Management Service

Only one Continuous Management Service may be installed in each BackupGroup, and it must be installed before other Continuous Protection Servercomponents.

The CMS must have a fixed IP address. If the IP address changes while theCMS is running, the CMS and the Network Helper (ENL) service must berestarted (for example, net stop RxRMS, net stop Network Helper, net startRxRMS).

Additionally, if Protection Agents exist on subnets different from the CMS,the CMS should be registered with the Domain Name Service (DNS).

Check this component to allow end users to view and restore files via theirWeb browser.

Web Restore Server Components

Check this option to install a Continuous Protection Agent on the computer.Continuous Protection Agent

A Continuous Protection Agent must be installed on all computers that willact as Business Servers or Protection Servers.

Check this option to allow files stored on this server to be indexed andsearchable.

Indexing Component

Check this option to perform an install of the Remote Agent on the localcomputer.

Backup Exec Remote Agent forWindows Systems


44

Check this option to allow for continuous protection of Microsoft ExchangeServers.

An Exchange Protection Agent with the Continuous Management Serviceand a Continuous Protection Agent must be installed on the Backup Execmedia server.

An Exchange Protection Agent must be installed with the Remote Agentand a Continuous Protection Agent on the Microsoft Exchange system.

If you cannot select this option, check your DNS for proper settings.

Exchange Protection Agent

13 On the Backup Group screen, enter a name of the Backup Group and the nameof the Continuous Management Service, and then click Next.

When you click Next, you may be prompted with a Windows Security Alertscreen with options of Keep Blocking, Unblock, or Ask Me Later. This securityscreen is displayed due to the installer looking for an existing ContinuousManagement Service that already has the specified Backup Group nameregistered. Select Unblock to continue.

14 On the Services screen, enter the credentials for the Backup Exec ContinuousProtection Server Service Account, including user name, password anddomain.

15 Click Next.

16 If a Continuous Management Service was selected for this installation andthe Continuous Management Service server has multiple NIC cards, theNetwork Interface Selection screen is shown. Select the Network interfaceto use for the Backup Group management and verify the displayed settings.

17 Click Next.


18 On the Support Folder screen, accept the default directories or change thedirectories, and then click Next.

Select or browse to the directory whereContinuous Protection Server can storeSystem Information (System State andShadow Copy Components) data to be backedup. The System Cache is a holding area forthe system information and shareinformation.

At a minimum, System information requiresat least 5 GB of disk space. If the serverperforms additional roles, such as also actingas a domain controller, more space isrequired.

System Cache Directory

Select the default journal directory or browseto another directory to hold the backupjournals. The Journal Folders contain thedynamic changes of the data that occurduring continuous backups.

Journal Directory

Select the default directory or browse toanother directory to hold the indexingdatabase. The indexing component holdsindexes of the snapshots that are capturedon the Protection Server.

Indexing Directory

You should install these directories on separate volumes.

19 On the Ready to Install the Program screen, review the selections, and thenclick Install.

20 Following the Continuous Protection Server installation, you are promptedto restart the computer. Click Yes to complete the installation.

If a Continuous Protection Agent was installed, you must restart the serverafter the initial installation. The restart ensures that the filter driver iscorrectly installed and ensures proper detection of all open files. If you usethe Microsoft Shutdown Event Tracker, you must restart the server manuallyafter installation.

Viewing installation logsFor installation troubleshooting purposes, you can view the installation logs in%allusersprofile%\application data\symantec\Backup Exec CPS\logs. Oncomputers that run Windows Server 2008, the installation logs are located in


46

C:\ProgramData\Symantec\Continuous Protection Server\logs. The file name isCpsinst.log

Push-installing Continuous Protection Servercomponents

After you perform the initial installation, use the CPS Administration Console toinstall additional components remotely. Components that may be push-installedconsist of additional Administration Consoles, Continuous Protection Agents, orboth. Any number of Consoles can be installed in the Backup Group, and aContinuous Protection Agent must be installed on each Business Server andProtection Server.

If CMS is installed on a computer that runs Windows Server 2008, you canpush-install the CPA and the Administration Console components to computersthat run various operating systems.

Note: You cannot protect a Business Server that runs Windows Server 2008 witha Protection Server that runs Windows Server 2003. This configuration resultsin loss of data.

Table 2-12 lists the operating systems to which you can push-install CPScomponents if CMS is installed on a computer that runs Windows Server 2008.

Table 2-12 Components you can push-install from Windows Server 2008

CPS componentOperating system

CPA or the Administration Console. Youcannot install the Administration Consoleon a computer that runs the Windows ServerCore installation option of Windows Server2008.

Windows Server 2008

CPA or the Administration ConsoleWindows Server 2003

CPA or the Administration ConsoleWindows 2000 Server

Administration ConsoleWindows Vista

Administration ConsoleWindows XP

If CMS is installed on a computer that runs Windows Server 2003, you canpush-install the CPA and the Administration Console components to computersthat run various operating systems.

47Installing Continuous Protection ServerPush-installing Continuous Protection Server components

Table 2-13 lists the operating systems to which you can push-install CPScomponents if CMS is installed on a computer that runs Windows Server 2003.

Table 2-13 Components you can push-install from Windows Server 2003

CPS componentOperating system

CPA or the Administration ConsoleWindows Server 2003

CPA or the Administration ConsoleWindows 2000 Server

Administration ConsoleWindows Vista

Administration ConsoleWindows XP

Administration ConsoleWindows Server 2008

Firewalls need to be manually reconfigured for CD installation andpush-installation. Alternatively, firewalls can be turned off during the installationprocess.



Administrator rights are required when push installing components to remotecomputers, as well as backup rights to the computer hosting the ContinuousManagement Service (CMS).

If a cross domain trust exist between the computers push installing from and to,the account that is running from the installing computer must be present in thelocal administrators group of the computer being push installed to.

Push-installing Continuous Protection Server components

1 On the Windows taskbar, click Start >Programs>Symantec >BackupExecCPS >Backup Exec CPS Console.

2 On the navigation bar, click Setup.

3 On the task pane, under Server Tasks, click Push install CPS componentsusingwizard.

4 Review the introduction on the Welcome to the Push Install CPS ComponentsWizard screen, and then click Next.

Installing Continuous Protection ServerPush-installing Continuous Protection Server components

48

5 On the Select a Computer screen, type or browse to the name of the computeron which to install the components. Alternatively, type the IP address for thecomputer.

If the computer to which the components are installed is located on a differentsubnet, naming services such as Dynamic Name Service (DNS) or WindowsInternet Naming Service (WINS) must be established across the routes forproper product operation and communication to occur.

6 Click Next.

7 On the Select Components screen, select the components you want to install.By default, all options are pre-selected for installation.

For optimal performance, some Continuous Protection Server componentsshould be installed in separate volumes from one another. The Journal Folder,Indexing Component, Backup Destination, and System volume should all bein separate volumes.

8 Click Next.

9 Enter the Credentials for the Backup Exec CPS Service Account, includinguser name, password and domain.

10 Enter the License Key provided, and then click Next.

11 On the Local System Object Cache Path screen, select or browse to thedirectory where Continuous Protection Server can store System Information(System State and Shadow Copy Components) data to be backed up.

The Local System Object Cache is a holding area for the system informationand share information.

At a minimum, System Information will require at least 2 GB of disk space(larger for Windows Server 2008). If the server performs additional roles,such as also acting as a domain controller, more space is required.

12 Click Next.

13 On the Select Journal Path screen, select the default journal directory orbrowse to another directory to hold the backup journals.

The Journal Folders contain the dynamic changes that occur duringcontinuous backups.

14 Click Next.

15 On the Select Indexing Database Path screen, select the default directory orbrowse to another directory to hold the indexing database.

The indexing component holds indexes of the snapshots that are capturedon the Protection Server.

49Installing Continuous Protection ServerPush-installing Continuous Protection Server components

16 Click Next.

17 Type or browse to the installation path on the remote computer where theservices will be installed.

Installation must occur on one of the drives that are shown in the drop-downlist although the rest of the path may be modified.

18 Click Next.

19 If a Protection Agent is being installed, the server must be restarted for theinstallation to complete. Select Restart the computer if required for this tooccur automatically at the end of the installation. If not, the system must bemanually restarted before this server is part of the Backup Group.

20 On the Push Install Summary screen, verify that the settings are satisfactory,and then click Next.

21 On the Completing the Push Install CPS Components Wizard screen, clickFinish to begin the installation. A screen appears showing the installationprogress.

22 Verify that the Protection Agent was properly installed by noting that theBusiness Server shows in the server list on the Servers tab. This step maytake some time due to the configuration and system restart.

The server you add to the Continuous Protection Server Backup Group mustbe restarted. If you use Microsoft’s Shutdown Event Tracker, you must restartthe server manually after installation.

Upgrading to Continuous Protection Server 12.5The Continuous Protection Server (CPS) installer upgrades CPS 12 to CPS 12.5.

You can upgrade only portions of the CPS products or run CPS 12.5 concurrentlywith CPS 12.

You can perform a rolling upgrade. A rolling upgrade allows you to upgrade serversin a backup group one at a time. You can protect all servers in a backup groupduring the upgrade process, even though different servers may use differentversions of Backup Exec.

After CPS 12.5 is installed on one server, you can use the Administration Consoleon that server to install or update Continuous Protection Agents and Consoles toother remote servers.

Installing Continuous Protection ServerUpgrading to Continuous Protection Server 12.5

50

Note: When upgrading a CPS database, all job schedules are disabled to allowContinuous Protection Agents to be upgraded before the Continuous ManagementService attempts to start the scheduled jobs. As soon as the Continuous ProtectionAgents are upgraded, the job schedules must be re-enabled from the Console.

To upgrade to Continuous Protection Server 12.5

1 Before performing the upgrade, close all other programs that may be running.

2 Insert the Continuous Protection Server 12.5 CD into the CD-ROM drive.

If AutoPlay is not enabled, navigate the installation CD and double-clickbrowser.exe.

If an earlier version of Continuous Protection Server is detected, a promptappears noting that the earlier version must be manually uninstalled beforeContinuous Protection Server 12.5 can be installed.

3 Click Update to continue.

4 If you are upgrading a Continuous Protection Agent, when prompted, enterthe license keys for CPS 12.5, and then click Next to continue.

The installation wizard detects which earlier components are already installedon that server, and then updates them to Continuous Protection Server 12.5.

Modifying Continuous Protection Server installationsUse the Push-installation option for Continuous Protection Server AdministrationConsoles or Continuous Protection Agents to reinstall components.

To detect and repair Continuous Protection Server component problems, rerunbrowser.exe, or use the Change option of the Add and Remove Programs controlpanel in Windows.

Uninstalling the Continuous Protection ServerUninstalling Continuous Protection Server removes all components that wereinstalled as part of the Complete installation. These components include theAdministration Console, Continuous Management Service, and ContinuousProtection Agents.

Symantec LiveUpdate is uninstalled automatically if you do not have otherSymantec products installed that use this technology. The Remote Agent and.NET Framework 2.0 are not removed. If we do not need these tools for otherapplications, you can uninstall them manually.

51Installing Continuous Protection ServerModifying Continuous Protection Server installations

To uninstall the Continuous Protection Server

1 On the Windows Start menu, click Control Panel.

2 Click Add orRemove Programs.

3 In the Currently Installed Programs list, selectContinuousProtectionServer.

4 Click Remove.

5 Click Yes to confirm that you want to remove the program.

6 A message prompts you to verify that you want to remove all data associatedwith Backup Exec Continuous Protection Server, which includes ContinuousManagement Service or Continuous Protection Agent databases, data storedwithin backup destinations, web restore indexing database, and the local datacache.

Click Yes to all removal of all data, or click No to remove the data manuallyafter the uninstallation process has completed.

7 If applicable, restart the server to complete the software removal process.

A system restart is required if you uninstall a Continuous Protection Agent.

Uninstalling a Continuous Protection AgentBefore uninstalling a Continuous Protection Agent, consider the following:

■ Snapshots cannot be deleted after a Protection Server is uninstalled. Beforeuninstalling a Protection Server, you need to delete all snapshots.See “Deleting snapshots” on page 77.

■ After the Protection Server is uninstalled, snapshots must be manually deleted.

■ If a Business Server or Protection Server is being removed from a BackupGroup, you must first uninstall the software from the server, and then theserver can be removed from the Backup Group.

■ If the Continuous Protection Agent is uninstalled, the user will be promptedto reboot after the uninstall is completed.

To uninstall a Continuous Protection Agent

1 On the Windows Start menu, click Control Panel.

2 On the Control Panel, click Add orRemove Programs.

3 In the Currently Installed Programs list, selectContinuousProtectionServer.

4 Click Remove.

5 Click Yes to confirm that you want to remove the program.

Installing Continuous Protection ServerUninstalling a Continuous Protection Agent

52

6 Click Yes to restart the server.

You will now delete the unavailable Business Server.

7 On the navigation bar of the Administration Console, click Setup.

8 In the selection pane, click Servers.

9 In the results pane, right-click the unavailable source, and then click DeleteUnavailable Server.

The data that is located on the backup destination and all the snapshots arenot removed during the uninstall process. Snapshots should be deletedmanually before uninstalling the CPA. If the CPA is uninstalled, the user willbe prompted to reboot after the uninstall is completed.

53Installing Continuous Protection ServerUninstalling a Continuous Protection Agent

Installing Continuous Protection ServerUninstalling a Continuous Protection Agent

54

Using the AdministrationConsole


■ About the Continuous Protection Server Administration Console

■ Starting the Continuous Protection Server Administration Console

■ About the general Administration Console features

■ About the Administration Console views

About the Continuous Protection ServerAdministration Console

The Administration Console lets you do the following tasks:

■ Add servers to the Backup Group

■ Designate servers that will receive the backup data (Protection Servers)

■ Create and schedule backup jobs

■ Create restore jobs

■ Monitor jobs

■ View alerts

3Chapter

Starting the Continuous Protection ServerAdministration Console

The Administration Console is the centralized point of management for allContinuous Protection Server activities. Administrator rights are required on thesystem running the Administration Console when you use the console.

To start the Continuous Protection Server Administration Console

1 On the Windows task bar, click Start>Programs>Symantec>BackupExecCPS.

2 Click Backup Exec CPS Console.

You can add the option to the Start menu and access it from there. Right-clickBackup Exec CPS Console, and then click Pin to Startmenu.

About the general Administration Console featuresThe Administration Console has a variety of features to help you work efficiently.

Table 3-1 describes the features of the Administration Console.

Table 3-1 General Continuous Protection Server Administration Consolefeatures

DescriptionFeature

You can access Continuous Protection Server features by usingthe menu bar that appears across the top of the AdministrationConsole window. All features, menu options, wizards, and onlinehelp can be accessed by using navigation buttons and links in theConsole. However, the menu bar offers a traditional approach tousing the program’s features. Some options are available onlyafter an item is selected.

Menu bar

The navigation bar groups together common that tasks you canperform. It appears under the menu bar across the top of theAdministration Console window. The navigation bar buttonsalways appear in the same place and in the same order.

Navigation bar

The contents of the task pane change based on the view that youselect from the navigation bar. A list of tasks you can perform atany given time appears on the left side of the AdministrationConsole window. Using the View menu, you can show or hide thetask pane at any time. Using the arrow, you can show or hide taskgroupings within the task pane at any time as well.

Task pane

Using the Administration ConsoleStarting the Continuous Protection Server Administration Console

56

Table 3-1 General Continuous Protection Server Administration Consolefeatures (continued)

DescriptionFeature

You can select the item that you want to work with from theselection pane. After the item is selected, all associated featuresare enabled. The selection pane appears to the right of the taskpane. However, if you hide the task pane, the selection paneappears on the left side of the Administration Console window.

Selection pane

In the Preview pane in the bottom-right corner of the window,detailed information appears about the items that are selected inthe results pane. You can show or hide the Preview pane by usingthe View menu or by dragging the divider to a new position.

Preview pane

The status bar provides computer processing information aboutthe task that is being performed. It appears across the bottom ofthe Administration Console window. You can show or hide thestatus bar at any time by using the View menu.

Status bar

About the Administration Console viewsContinuous Protection Server groups similar tasks together by using a variety ofbuilt-in Console views. When you select a view from the navigation bar, relatedtasks appear in the task pane. Changing views enables you to selectively accessthe various Continuous Protection Server features.

Overview viewYou can access the Getting Started, CPS Assistant, or System Summary viewsfrom the Overview view.

Table 3-2 describes the different views that are available in Overview.

Table 3-2 Views available in Overview

DescriptionView

This view provides information about the processes required toset up and use Continuous Protection Server. The Getting Startedview also provides links to the Backup Exec Retrieve feature, alertsand notifications, and product updates and patches.

Getting Started view

57Using the Administration ConsoleAbout the Administration Console views

Table 3-2 Views available in Overview (continued)

DescriptionView

This view provides links to information about the setup, use, andsupport of Continuous Protection Server.

The information desk provides links to a variety of informationsuch as the following:

■ Documentation, getting started, configuration and ContinuousProtection Server wizards.

■ Continuous Protection Server Technical Support Web sitesand Knowledge Base.

■ Symantec learning tools and sites.

Continuous ProtectionServer Assistant view

This view displays information about backup jobs, ContinuousProtection Server alerts, and backup servers. This view alsoenables you to get a comprehensive summary of your BackupGroup and backup jobs.

System Summary view

Setup viewThe Setup view lets you perform many of the functions of Continuous ProtectionServer, including setting up servers, backup destinations, and backup jobs. Youcan also create and view snapshots in this view.

Table 3-3 describes the common tasks that are available in the task pane of theSetup view.

Table 3-3 Task pane options in the Setup view

DescriptionTask name

Allows you to push-install additional Continuous ProtectionAgents, Continuous Protection Server Administration Consoles,or both.

Push install CPScomponents usingwizard

Allows you to configure servers within the Backup Group to bethe Protection Servers of backup jobs.

New backupdestination

Allows you to use the Backup Destination Wizard to designateservers within the Backup Group as Protection Servers for backupjobs.

New backupdestination usingwizard

Allows you to view the snapshot history for a given backupdestination by launching the Backup Destination Propertieswindow. This option is only available if a specific BackupDestination is selected in the results pane.

View snapshots

Using the Administration ConsoleAbout the Administration Console views

58

Table 3-3 Task pane options in the Setup view (continued)

DescriptionTask name

Allows you to create snapshots for the selected backupdestinations. This option is only available if a specific BackupDestination is selected in the results pane.

Create snapshot now

Allows you to create a new backup job manually.New backup job

Allows you to create a new backup job by using the New BackupJob Wizard.

New backup job usingwizard

Viewing properties in the Setup viewYou can view or change properties for servers, backup destinations, and backupjobs. Each of these tasks has one or more associated properties windows that allowyou to manage Continuous Protection Server configurations.

Table 3-4 describes the server properties that are available in Setup view.

Table 3-4 Server properties in the Setup view

DescriptionFeatureArea

Provides specific information on the server, includingserver name, status (online or offline), IP address,domain, operating system information, build number,installed components, and time zone.

GeneralSettings

Provides specific information on the available volumesof the server, including volume name (drive), filesystem type, total capacity, and free space.

Volumes

Provides a check box to remove server logs after adesignated number of days.

Advanced

Provides the license key information for the selectedserver, including the type, the actual license key, andthe days remaining for evaluation and demonstrationkeys. A text box is included to enter a new license key.

License Keys

Provides a log of activity for the specified server. Thelog can be filtered to show entries for the last 24hours, last 7 days, or all entries. The server historylog shows the date/time and description of each logentry.

Server LogHistory

Table 3-5 describes the backup destination properties.


Table 3-5 Backup destination properties


Provides information on the backup destination,including backup destination name, description,server name, and path.

GeneralSettings

Provides the schedule when snapshots are taken. Theschedule allows specific days of the week and snapshotfrequency to be specified.

ScheduleSnapshot

Allows the retention of snapshots to be set. Theretention policy defines how long snapshots areretained. For example, snapshots are retained for agiven number of hours, and a specified numberretained per day, per week, or per month.

Retention Policy

Provides a list of snapshots for the specified backupdestination, including the date, age, and IndexingState of each snapshot. Buttons are also included tocreate a new snapshot or to delete one of the existingsnapshots on the destination.

SnapshotsHistory

Table 3-6 describes the backup job properties.

Table 3-6 Backup job properties


Provides specific information on the backup job,including backup job name, description, andProtection Server details.

GeneralSettings

Allows you to select the specific backup server,volumes, and System Information to be backed up.

BackupSelections

Allows you to specify when the backup job will run.The options are to run the job whenever a file changes,according to a schedule, or manually.

Schedule

Allows you to add or modify the bandwidth limitationfor a specified job. This screen allows you to specifythe Business Server, and the bandwidth usage for aselected network connection.

Bandwidth


60

Table 3-6 Backup job properties (continued)


Allows you to specify a command script to be runbefore or after the backup job. You may enter orbrowse to the script. A limiting feature allows thescript to be cancelled if not completed after a specifiedamount of time (minutes). A check box allows you toenable the script asynchronously with the backup job.

Commands

To view properties in the Setup view

1 Select one of the options in the Settings pane.

2 Right-click the server, destination, or job.

3 Click Properties.

To reveal specific properties or options, select the property from the propertiespane.

Restore viewThe Restore view lets you search for or select files to restore and is the best wayto restore large sets of files. You can filter the list of files by specific points in timeor view all versions of backed up files. If a small number of files need to be restored,use Backup Exec Retrieve.

Job Monitor viewThe Job Monitor view lets you view current jobs, job properties, and job history.You can also view information about source and destination pairs that aresynchronized during the backup process.

You can monitor the job pairs for the Continuous Protection Server job by selectingMonitor job pairs from the Task pane.

See “About the Job Monitor” on page 115.

Alerts viewThe Alerts view lets you respond to notification about the status of the ContinuousProtection Server jobs on all servers. In the event that a job does not runsuccessfully, you can read a message that alerts you to the problem encountered.Various levels of errors, warnings, and information are built into ContinuousProtection Server to enable you to manage your backup jobs successfully.


Selecting Properties for the Alerts view provides detailed information on theselected alerts.


62

Configuring ContinuousProtection Server


■ Configuring Business Servers

■ Moving of servers between Backup Groups

■ Managing the Continuous Protection Server Services

■ Managing backup destinations

■ Managing snapshots

■ Configuring registry entries

Configuring Business ServersYou can use Properties to add or modify the Business Servers in the Backup Group.Business Servers are the servers where files are copied from during the CPS backupprocess. Business Servers may be configured when the Continuous ProtectionAgent is installed, when your Backup Group changes, or when resources arereallocated.

To configure Business Servers



3 In the results pane, right-click the server, and then click Properties.

4 Under Settings, click Advanced.

4Chapter

5 Check Remove log records after (days) to define the number of days to savethe backup records.

6 Specify the number of days to keep the records.

7 Under Settings, click LicenseKeys, and then define the options you want.

License key of installed Continuous Protection Serversoftware, including demonstration licenses and permanentlicenses. To delete a license key (such as an evaluationlicense key), select the license key, and then clickRemove.

Server license keys

New Continuous Protection Server software licensenumber. To add a new license, such as when upgrading toa permanent license, type the new software license number,and then click Add.

New license key

8 Under History, click Server Log, and then define the options you want.

Save the log to a file.Save As

Narrows the list of server log entries to the following:

■ All Entries

■ Last 7 Days

■ Last 24 Hours

Show entries

Date and time the log record was written. The time isconverted to your local time for display purposes.

Time

Information about the server log entry or a note for theadministrator, such as the number of days remaining in alicense period.

Description

9 Click OK.

Reviewing the general properties of a Business ServerYou can review various general properties of a Business Server.

Table 4-1 describes the general properties that are available.

Configuring Continuous Protection ServerConfiguring Business Servers

64

Table 4-1 General properties of a Business Server

DescriptionGeneral property

The server’s name, which comes from the system informationon the computer.

Server

The server’s status (online, offline, or unavailable).Status

The Internet Protocol (IP) address that is used by CPS whencommunicating with this computer.

IP address

Directory location of the computers in this network.Domain

The operating system that is installed on this computer.Operating system

The build number of the Continuous Protection Server softwarethat is installed on this computer.

Version

Indicates whether a CMS, CPA, or both are installed on thiscomputer.

Installed Components

Indicates the international time zone where this computer islocated.

Time Zone

Indicates the ports that this server is currently using.Ports in use

To review the general properties of a Business Server




4 Under Settings, click General.

Reviewing the volume properties of a Business ServerYou can review various volume properties of a Business Server.

Table 4-2 describes the volume properties that are available.

Table 4-2 Volume properties of a Business Server

DescriptionVolume property

The Name of the Windows NT volume on this server wherebackup files from a Business Server are stored.

Name

65Configuring Continuous Protection ServerConfiguring Business Servers

Table 4-2 Volume properties of a Business Server (continued)

DescriptionVolume property

The file system that is used when formatting the volume (usuallyNTFS).

File System

The number of bytes of disk space that are associated with theserver.

Total Capacity

The number of bytes of disk space that are currently availablefor use on the server.

Free Space

To review the volume properties of a Business Server




4 Under Settings, click Volume.

Moving of servers between Backup GroupsIn some cases, one or more Business or Protection Servers may need to be movedto a different Backup Group. This condition may occur if an existing Backup Grouphas become too large and the amount of data being protected is excessive for thenetwork system.

If the Backup Group does not exist, you must create it before you move the server.A new Backup Group requires the creation of a new Continuous ManagementService (CMS) using the Complete or Custom installation procedures.

When a new Backup Group is created, it must have a unique name and uniqueCMS. Each Backup Group can only have one CMS. After a new Backup Group hasbeen created, the Business Servers and Protection Servers can be migrated to thenew group.

When a server has been moved to a different Backup group, all jobs involving thatserver must be recreated.

Note: You can move a Business Server that runs on Windows Server 2008 to abackup group that runs on Windows Server 2008 only.

Configuring Continuous Protection ServerMoving of servers between Backup Groups

66

To move servers between Backup Groups



3 In the results pane, right-click the server name that you want to move, andthen click ChangeManagement Server.

4 On the Choose Change Management Server dialog box, type the name of thenew CMS, and then click OK.

The name cannot be the same as the existing CMS.

Additionally, select the check box if you want to delete the job pairs and rulesthat are associated with the old CMS.

5 When you are prompted to verify that you want to change the CMS, click Yesto proceed or click No to cancel the operation.

If you clicked Yes, the Administration Console that is still connected to theoriginal CMS deletes all jobs that were involved with the server. If the jobdeletions were not successful, a message box notes the failure.

Managing theContinuous Protection Server ServicesThe Service Manager is a CPS utility that lets you start and stop the CPS servicesand change the Service Account credentials on the protected server.

Stopping or starting Continuous Protection Server servicesYou can use the Service Manager to stop or start CPS services.

To stop or start CPS services

1 On the Tools menu of the Administration Console, click CPS Services.

2 Select any of the following options:

Starts all CPS services for the selected serverStart all services

Stops all CPS services for the selected serverStop all services

Stops all CPS services and then restart the services for theselected server

Restart all services

Refreshes this dialog boxRefresh

67Configuring Continuous Protection ServerManaging the Continuous Protection Server Services

Adding or removing servers from the Service ManagerYou can use the Service Manager to add or remove servers.

To add or remove servers from the Service Manager



■ To add a server, click Server Type.Type the name of a server to add to the list, and then click Add.

■ To import a list of servers, click Import List, and then select the file thatcontains the server list.

■ To remove a server, select one or more servers from the server list, andthen click Remove Servers.

Changing service account credentialsYou can edit service account credentials on the protected server. Every node inthe Backup Group must be running in the same mode.


See “Resetting the standard logon” on page 154.

To change service account credentials


2 Click Services credentials.

3 In the Security Mode list box, select one of the following modes.

The user account must be a domain account that isrecognized by every node that participates in backup. Theaccount must be a member of the local administrator'sgroup on the computer running the services. Symantecstrongly recommends that customers use Domain mode,which is more secure than Workgroup mode. The user musthave administrative credentials to run the CPS services.

Domain mode

A user account is not required to run in Workgroup mode.Workgroup mode may be necessary for customers who arerunning outside of a Domain.

Workgroup mode

Configuring Continuous Protection ServerManaging the Continuous Protection Server Services

68

Managing backup destinationsContinuous Protection Server lets you back up data to a specific location on aspecific Protection Server. This server and location are referred to as the backupdestination. Before you can create backup jobs, you need to create one or morebackup destinations where the backed up files are stored. The backup destinationdesignates a specific Protection Server and volume where the data is stored.

Create a backup destination naming strategy that makes it easy to determine whatkind of content is in each location. For example, if you plan to store marketingproposals, you might create a destination such as Marketing. If you have marketingdepartments in different locations, create a destination for each location by addinga prefix to the department name. For example, a destination for the West CoastMarketing department could be WCMarketing.

There are additional details for managing backup destinations such as thefollowing:

■ Permissions for backup destination folders or permissions on objects withina backup destination should not be changed after backup jobs have been run.

■ If you are unable to delete some files from a backup destination, the task shouldbe performed by a user with Administrator rights.Additionally, Administrators may not be able to delete the folder tree whendeleting backup destinations. In this case, local ownership must be assignedto the Domain Admin on the files and all related subfolders if they originatefrom another local system.

■ CPS cannot be used to back up a Protection Server's data to a backup destinationon the same Protection Server.

■ Backup destinations can only be created on servers that run Windows Server2003/2008 operating systems and have a Continuous Protection Agent (CPA)installed. In addition, only one backup destination is allowed for each logicalvolume or drive letter.

■ Symantec recommends that CPS backup destinations be created on volumesseparate from the Backup Exec backup-to-disk volumes to prevent redundantuse of storage.

Adding a backup destinationYou need at least one backup destination before you can start backing upinformation from your sources.

See “Defining a retention policy for a snapshot” on page 75.

See “Creating a snapshot schedule” on page 74.

69Configuring Continuous Protection ServerManaging backup destinations

To add a backup destination


2 In the task pane, under Backup Destination Tasks, click Newbackupdestination.

3 Define the appropriate options.

Abbreviated name of this backup destination.

For example: SLOMKT1.

Backup destination name

Full name or brief description of this backupdestination.

For example: San Luis Obispo MarketingPresentations.

Description

Name of the server on which the backup destinationresides. Leave the default server or select from alist of servers in the Backup Group.

The server cannot be changed after the backupdestination is saved.

Server

Location on the Protection Server where you wantthe backup files to be stored. Type or browse to thelocation of the backup destination in the BackupGroup.

The path cannot be changed after the backupdestination is saved.

Path

4 Click OK.

Configuring a backup destination for Shadow StorageYou may want to configure a specific backup destination for Shadow Storage,which is the location where changed bytes between snapshots are stored. Foroptimal performance, Shadow Storage should be on a separate volume from yourdata backup destination.

To configure a backup destination for Shadow Storage

1 Using Windows Explorer or My Computer, navigate to the drive containingthe backup destination. For example, “E:\”.

2 Right-click the drive, and then click Properties.

3 Click the ShadowCopies tab.

Configuring Continuous Protection ServerManaging backup destinations

70

4 Select the drive containing the backup destination. For example, “E:\”.

5 Click Settings.

The Volume should indicate the drive E:\.

6 Under Storage Area, select the volume where Shadow Storage should belocated.

For example, select “F:\”.

7 Optionally, you can modify the Maximum size of the storage area toaccommodate its intended use.

8 Click OK twice.

Renaming backup destinationsIf your naming convention changes, or you made a typographical error in adestination name, you can rename the backup destination that displays in CPS.The name change affects the display only and not the actual name on the disk.

To rename a backup destination


2 In the selection pane, click BackupDestinations.

3 In the results pane, right-click the backup destination, and then clickProperties.

4 Edit the appropriate options.

Abbreviated name of this backup destination.

For example, WCMKT1.

Backup destination name

Full name or brief description of this backupdestination.

For example, West Coast Marketing Presentations.

Description

5 Click OK.

Deleting backup destinationsYou might want to delete a backup destination to retire a server or change thearchitecture of your Backup Group. When you delete a backup destination, it isremoved from Continuous Protection Server. However, the backup destinationfolder and files remain on the server.

71Configuring Continuous Protection ServerManaging backup destinations

All backup jobs that are assigned to the destination must be deleted before deletingthe backup destination.

Additionally, although the backup destination directory and files remain on theserver, the CPS restore tools will not retrieve the data from these files. NeitherCPS restore jobs nor Backup Exec Retrieve can access a backup destination afterit has been deleted.

After a Protection Server is uninstalled, you must manually delete the data thatis contained in the backup destination. Be sure to note the location of the backupdestination data before uninstalling the Protection Server.


To delete a backup destination



3 In the results pane, right-click the backup destination, and then click Delete.


Deletes all snapshots automatically when thebackup destination is deleted.

Delete all snapshots associated withthis Backup Destination

Opens Windows Explorer so that data may bedeleted manually.

To manually delete the data, you must haveadequate permissions. Refer to MicrosoftWindows security help.

Open backup destination folder inexplorer view

5 Click OK to delete the backup destination.

Managing snapshotsA snapshot is a consistent, point-in-time image of the contents of the backupdestination.

Note: Because snapshots are volume-based, any changes on the volume arecaptured in the snapshot, including the CPS data. Therefore, to achieve maximumperformance, you should create a volume that contains only a backup destination.

Continuous backup jobs use a filter driver to capture changed bytes in the datafiles on the source and move the changed bytes to the backup destination whenever

Configuring Continuous Protection ServerManaging snapshots

72

the information changes. CPS takes snapshots of the backup destination atscheduled intervals.

Administrators schedule snapshots based on the importance of the data beingbacked up. Users can then select the specific versions of files to retrieve. Thelatest files on the backup destination can also be restored, although the latestversion might not have been captured in a snapshot.

Administrators define retention policies to save snapshots for specific periods oftime. When the snapshot expires, it is removed automatically. If the destinationreaches the limit of its disk space, the oldest snapshot is overwritten by newsnapshots. In addition, a history of the snapshots can be viewed and unnecessarysnapshots can be manually deleted from within the CPS Administration Console.However, when snapshots are deleted, the disk space may not be immediatelyfreed.

Additional details about managing snapshots include the following:

■ Snapshots can be stored up to a limit that is determined by the underlyingsnapshot technology. This limit may vary considerably if alternative snapshotproviders are installed.

■ Snapshots that are scheduled to be taken over a period of time where the endtime is earlier than the start time, may continue to be taken until the end timeon the next day. For example, snapshots that are scheduled to run every 1 hourbeginning at 8:00 a.m. and ending at 7:00 a.m. on Thursday, may result insnapshots being created until Friday at 7:00 a.m.

■ When backing up data from a single Business Server to multiple backupdestinations, the snapshot schedules should be consistent so that all files thatare protected by CPS are included in the snapshots.

■ When scheduling snapshots, the minutes and seconds that are specified forthe start and end times must be identical.

See “Components of Continuous Protection Server” on page 14.

See “How Continuous Protection Server works with Backup Exec” on page 125.


Creating snapshots on demandSnapshots can be created on demand (manually started by the user) or by aschedule. Snapshot schedules are defined when the backup destination is created,and can be modified as needed.

73Configuring Continuous Protection ServerManaging snapshots

To create snapshots on demand



3 In the results pane, select the backup destination.

4 In the task pane, under Backup Destination Tasks, clickCreatesnapshotnow.

5 Click Yes to confirm that you want to create the snapshot.

Creating a snapshot scheduleSnapshots can be scheduled to run on a specific schedule or periodically at timedintervals. The files available for restore display from the snapshots. To ensurethe files are available with minimal delay, snapshots should be captured asfrequently as your system resources allow.

Snapshots cannot be captured more frequent than hourly.

When you back up data from a single Business Server to multiple backupdestinations, the snapshot schedules should be consistent so that all files that areprotected by Continuous Protection Server are included in the scheduled snapshots.

Also, related data sets, such as the data and log files of a given database, shouldalways be backed up to the same backup destination.

To create a snapshot schedule




4 In the Properties pane, under Snapshot, click Schedule.


74

5 Select one of the following snapshot schedule options:

Select the check box next to each day that you want thesnapshot to occur.

Run on these days

Select and define a specific time for the snapshot to occur.Run only at

Select and define the intervals at which the snapshotoccurs.

Run

Snapshot schedules are always shown in the local time of the user who iscreating the snapshot schedule. If snapshot schedules are created for serversthat are located in other time zones, the specified time must be converted toyour local time.

6 Click OK.

Editing a snapshot scheduleSnapshot schedules can be modified to meet your backup and restore needs. Youcan change snapshot schedules to include any day of the week. You can also runthe snapshot on a schedule or run the snapshot periodically on timed intervals.

To edit a snapshot schedule


2 In the selection pane, click Backup destinations.


4 In the Properties pane, under Snapshot, click Schedule.

5 Select the scheduling option you want.

6 Click OK.

Defining a retention policy for a snapshotBackup snapshots are saved on the Protection Server for 24 hours unless youspecify otherwise. You have the option to set the frequency that snapshots arepurged. A copy of the snapshots can be saved on an hourly, daily, weekly, andmonthly basis.

To define a retention policy for a snapshot





4 In the Properties pane, under Snapshot, click Retention Policy.


The minimum duration that each snapshot isretained.

Keep each snapshot for

Retain a daily snapshot for this period of time. Thedaily retained snapshot is the last snapshot of theday.

and one daily for

Retain a weekly snapshot for this period of time. Theweekly retained snapshot is the last daily snapshoton the last day of the week.

and one weekly for

Retain a monthly snapshot for this period of time.The monthly retained snapshot is the last dailysnapshot of the last day of the month.

and one monthly for

If the volume becomes full, the operating system will delete snapshots.

6 Click OK.

Viewing snapshot historyYou can view certain historical information about the snapshots that are retainedon disk. The snapshot history includes the date snapshots were created and theirage.

If you select Show deleted snapshots, two additional columns are added to thesnapshot listings: the date deleted and the reason the snapshot was deleted.

To view snapshot history




76


4 In the Properties pane, under History, click Snapshots.

The snapshot retention policy expired and the snapshot wasautomatically deleted.

Policy

The snapshot was manually deleted by a user.Manual

If the system is running out of disk space, the system mightautomatically delete snapshots to free up space.

External

States of snapshot indexingEach snapshot is indexed so that it may be searched from Backup Exec Retrieve.Only the snapshots that have been indexed appear in the search results. Theindexing state provides the current status of the snapshot.

The indexing state is listed next to the snapshot in the Backup Destinationproperties window.

Table 4-3 displays the different states of snapshot indexes.

Table 4-3 State of snapshot indexing

DescriptionIndex state

Something went wrong during indexing and this snapshot has notbeen indexed

Not indexed

This snapshot has been indexed.Indexed

This snapshot is currently being indexed.Indexing

This snapshot is queued to be indexed (only one snapshot is indexedat a time).

Pending

See “Configuration issues” on page 146.

Deleting snapshotsYou can keep snapshots for a certain number of hours, days, weeks, or monthsbefore being automatically deleted. You should define the retention period toindicate the length of time that snapshots are retained. If you need to free harddisk space on the destination, you can manually remove unnecessary snapshots.


Note: You can store snapshots up to a limit that is determined by your underlyingsnapshot technology. This limit may vary considerably if alternative snapshotproviders are installed.

Snapshots that are associated with a given backup destination can also be deletedwhen the backup destination itself is deleted.

See “Deleting backup destinations” on page 71.

To delete snapshots




4 In the Properties pane, under History, click Snapshots.

5 In the Available snapshots for backup destination list, select the snapshot,and then click Delete.

6 Click Yes to confirm you want to delete the snapshot.

7 Click OK.

Configuring registry entriesCPS includes a Settings Utility that lets users change a number of CPS tunableparameters. These parameters could previously only be changed by manuallymodifying entries in the system registry.

You can use the Settings Utility to change the parameters for the followingsettings:

■ CPS trace and indexing logs

■ Journal root directory

■ Named Objects (System Cache) directory

■ Job Retry Intervals

■ Selected Network Interface

■ TCP and UDP ports

The parameters that are included in the Settings Utility are often updated. Seethe Symantec Web site for a current list and description of configurableparameters.

Configuring Continuous Protection ServerConfiguring registry entries

78

Accessing the Settings UtilityTable 4-4 describes the settings that are available in the Settings Utility.

Table 4-4 Settings Utility

DescriptionSetting

The Servers selection pane shows all of the servers in the BackupGroup. Select a server to view the existing parameters and valuesfor that server.

Servers pane

Location is the registry path for each parameter.

Value Name is the specific name of the registry value.

Current Value is the current value of the registry entry.

See “About the Settings Utility tunable parameters” on page 79.

Parameters pane

Lets you update the values in the Parameter pane after makingchanges.

Refresh

Lets you access the online help for the Settings Utility.Help

Lets you restore all parameters to their original default values.Restore Defaults

To access the Settings Utility

◆ Do one of the following:

■ Navigate to the CPS Services folderC:\Program Files\Symantec\Continuous Protection Server\Services, andthen double-click settingsutility.exe.

■ In the Administration Console, click Tools > Settings Utility.

About the Settings Utility tunable parametersTable 4-5 describes the tunable parameters that are available in the SettingsUtility.

79Configuring Continuous Protection ServerConfiguring registry entries

Table 4-5 Settings Utility tunable parameters

DescriptionParameter name

Specifies how often a grooming cycle will be run to remove outdated alerts fromthe system. The 'DaysToKeepAlertItems' key sets the number of days an alertwill remain on a system before it is outdated.

The default value is 86400 seconds (every 24 hours).

Changes to this value will not require systems or services to be restarted.

AlertGroomFrequency

To cause CPS to use region analysis regardless of file size, set this string valueto 1 (default is 0).

Changing this value requires that the Continuous Protection Agent Service berestarted on the server.

AlwaysDoRegionAnalysis

Specifies the IPv6 Multicast address where all discovery traffic is sent.

The default value is ff02:0:0:0:0:0:0:1, which signifies all nodes on the local link.

Changes to this value will require the ENL and dependent services, such as theCMS, CPA, Broker Service, and Continuous Protection System State ManagerService, to be restarted.

BroadcastAddress

Specifies the maximum number of router hops for IPv6 discovery broadcasts.

The default value is 1.


BroadcastHops

Enables ODBC connection pooling.

The default value is 0. A 1 value enables connection pooling.

Changing this value requires that the CPS Database Service be restarted on theserver.

ConnectionPooling

The number of days that alert items are kept on the server.


Changing this value will not require systems or services to be restarted.

DaysToKeepAlertItems

Specifies the number of days that deleted snapshot entries are kept on the server.

The default value is 30 days.


DaysToKeepDeletedSnapshots


80

Table 4-5 Settings Utility tunable parameters (continued)


If set to 1, this parameter prevents the CPS filter driver from delaying thecompletion of Directory Change Notifications. The only time it is necessary iswhen the Windows “Services for Macintosh” (SFM) is running on the server whereCPS is installed. Under conditions of heavy usage, SFM may fail if this setting isnot made. However, there are no known issues with SFM after the setting is made.

The default value is 1. Set a value of 0 only when the Microsoft Services forMacintosh is running on the system.

Although making this setting will allow SFM to run, it will also create a problemfor the Windows “Simple Mail Transport Protocol” (SMTP) service. It will preventSMTP from “picking up” (i.e., noticing the appearance of) new mail items in its“pickup” folder. There is no way to get both SMTP and SFM working on the samesystem where CPS is installed. The user must make a choice as to which Windowsservice that will run.

Changing this value requires that the server be restarted.

DelayDirChangeNotifications

If this value is set to 1, certain internal errors in CPS components will write anentry in the Windows application event log. If it is set to 0, no event log entrywill be written.



DoEventLog

For Symantec Technical Support use only.



EnableDebugConsole

Enables trace logging.

The default value is 1 to enable diagnostic trace logging, or 0 to disable.


EnableLogFile

If this value is set to 1, a timestamp is printed on each line of diagnostic tracelogs recorded by CPS components.



EnableTimestamp




Continuous Protection Agent data port.


Changes to this value must be made on all computers in the Backup Group. Inaddition, the Continuous Protection Agent Service must be restarted on allcomputers.

FFXPort

Specifies a list of status or alert IDs that will be filtered from the Alert Database.The list should contain the IDs in either hexadecimal or decimal form separatedby either commas or semicolons. Only new alerts will be filtered from the AlertDatabase after an addition to this list. No existing alerts will be removed fromthe database.

The default value is an empty string.


FilteredIDList

Either the host name, Fully Qualified Domain Name, or IP address of the ENLmaster.

The default value is usually the CMS name.


Gateway

(ENL\Network.TCPIP)

Either the host name, Fully Qualified Domain Name, or IP address of the ENLmaster.

The default value is usually the CMS name.


Gateway

(ENL\Network.UDPv6)

Specifies whether or not this server will act as a router for ENL network traffic.

The default value is Yes for a CMS computer and No for all non-CMS computers(except in special situations where a non-CMS may be used to route ENL trafficto a CMS on another subnet).


Gateway

(ENL\System)


82



Location of files that hold index information about the data that has been backedup by CPS. The location must have at least 120 MB of free space (1GB or morerecommended).

The default value is set by the CPS installer.

Changing this value will require that the Continuous Protection Indexing Servicebe restarted on the server. In addition, indexing files will be moved from theirprevious location to the newly specified path.

IndexingRoot

Location of the dynamic changes of data during continuous backups. The locationmust have at least 120 MB of free space (10 GB or more recommended).



JournalRoot

Controls whether the filter driver writes a table of open file entries into the firstoutbound dynamic journal file only once (when a job starts), or writes this tableat the start of every new outbound journal file.

The default value is 0. Set to 1 if journal writing errors occur during continuousbackup jobs owing to an Open File Table (OFT) overflow, as can happen on systemswhere a great many files are opened in rapid succession.

Changing this value requires that the system be restarted.

LogOpenFileTableOncePerSet

Location of the CPS trace log files. The location must have at least 100 MB of freespace. The location can be specified during installation, such as the following.

C:\Program Files\Symantec\Continuous Protection Server\Logs


LogPath

Specifies the directory where the ENL logs (efc.log) will be written to.

The default value is set at install time.


LogPath

(located in EFC)




A complex hexadecimal mask used to specify the type of entries that will bewritten to the 'EFC.log' file.

The default value is 0x00300100. A value of 0xFFFFFFFF signifies that All ENLlogging information will be written to the log file. This optional setting can beuseful in debugging situations, but will quickly create very large amounts of logdata.


LogText

Specifies whether the ENL Service will start up in Master mode.

The default value is Yes for a CMS computer and No otherwise.


Master

(located in ENL\System)

The maximum number of files to show for a single directory in the Backup ExecRetrieve ‘browse’ view.



MaxDirSize

The maximum size (in bytes) that the diagnostic trace log can grow before a newfile is started.

The default value is 10485760 (10 MB).


MaxLogSize

The maximum size of the ENL log in bytes.

Default is 1048576 bytes (1 MB).

Changing this value requires the ENL service and its dependent to be restarted.

MaxLogSize

(ENL\System)

Sets the maximum size for a UDP packet. Useful on networks that have a smallMTU.



MaxPacketSize

(ENL\Network.TCPIP)


84



Sets the maximum size for a UDP packet. Useful on networks that have a smallMTU.



MaxPacketSize

(ENL\Network.UDPv6)

To change the maximum percentage difference in file size for region analysis (inpercent). Larger values mean region analysis will still take place, even if file sizesdiffer by a larger percentage.



MaxRAPerCentChange

To change the minimum file size for Region Analysis (in KB).



MinRASizeInKb

This parameter specifies the time that a job will attempt to be restarted after ithas failed.

The default value is 120000 ms (2 minutes).


MsBetweenRallyChecks

Holding location for the System State and share information. The location shouldhave at least 100MB of free space (1GB or more recommended).


Changing this value requires that the Continuous Protection Agent Service andContinuous Protection System State Manager Service must both be restarted onthe server. In addition, named objects files will be moved from their previouslocation to the newly specified path.

NamedObjectsRoot

The name of the CPS Backup Group that this computer is associated.

The default value (Backup Group) is set at install time.


Netgroup (ENL\System)




To disable region analysis for all files, set this value to 1. When region analysisis disabled, files are synchronized by copying the entire source file to the targetsystem. If both this value and “AlwaysDoRegionAnalysis” are set to 1, the“AlwaysDoRegionAnalysis” value takes precedence.



NeverDoRegionAnalysis

This parameter specifies the number of diagnostic trace log files to keep. Whenthe number of trace log files exceeds this number, older log files are deleted. Setthis value larger than the default value to preserve more logs, and contain morejob history.



NumberOfLogs

Size of the journal at which a switchover to the next journal may begin. Thisvalue must be less than the journal size by at least 1MB.

This value must be an exact multiple of 1 MB (1048576 bytes).



OutboundJournalCleanupSize

This parameter is the default size in bytes of an outbound journal file when it isfirst created. The nominal size of journal files should be made larger than thedefault size only when necessary to avoid job cancellations owing to Open FileTable (OFT) overflows.

This value must be an exact multiple of 1 MB (1048576 bytes).



OutboundJournalNominalSize

If the number of outstanding sync journal files exceeds theOutboundSyncJournalLimit, the CPA service slows down the creation of syncjournals during initial synchronization between two systems.



OutboundSyncJournalLimit


86



Specifies the IP address that the node will use when registering with the nameservice. This value must be an IPv4 compatible IP address.



PreferredAddress

(ENL\Network.TCPIP)

Specifies the IP address that the node will use when registering with the nameservice. This value must be an IPv6 compatible IP address.



PreferredAddress

(ENL\Network.UDPv6)

Specifies the NIC that will be used to find the preferred IP address if it is notexplicitly set through the PreferredAddress key. The preferred NIC is specifiedby the MAC address of the NIC.



PreferredNIC

(ENL\Network.TCPIP)

Specifies the NIC that will be used to find the preferred IP address if it is notexplicitly set through the PreferredAddress key. The preferred NIC is specifiedby the MAC address of the NIC.



PreferredNIC

(ENL\Network.UDPv6)

If the amount of free disk space on the volume containing CPS journals falls belowthis number of bytes, CPS jobs will be cancelled.



ReservedFreeDiskSpace




Continuous Management Service RPC port.


Changing this value must be made on all computers in the Backup Group. Inaddition, the Continuous Protection Agent Service must be restarted on allcomputers, and the Continuous Management Service must be restarted on theCMS server.

RxRmsStaticPort

Continuous Protection Agent RPC port.


Changing this value must be made on all computers in the Backup Group. Inaddition, the Continuous Protection Agent Service must be restarted on allcomputers.

RxRsaStaticPort

Specifies the frequency with which the System State Manager Service regeneratesNamed Object data.

The default value is 0 3 5 4 0 1439.


Schedule

Set this value to 1 to prevent the CPS filter driver from queueing too many i/orequests for journaling.

The default value is 0. Set to 1 only on very slow, single-CPU systems if continuousbackup jobs are failing owing to journal writing errors.

Changing this value will require that the system be restarted.

SerializeIrpLogging

Groups all shares for a business server under a single entry for faster display andsnapshot processing.

The default value is 0 for multiple components. Set to 1 for single component.


ShareInfoAsSingleComponent

Specifies the UDP port used by ENL. Changing this value affects both the IPv4and IPv6 functions of the ENL service.


Changes to this value must be made on all computers in the Backup Group. Inaddition, the ENL Service must be restarted on all computers.

Socket


88



Set this value to 0 to force CPS to use the standard Win32 methods of findingfiles.



UsePrivateFindFileMethod

Changes the amount of data that will be sent to the ENL logs. Default value is No.A value of Yes will send much more detailed data to the ENL logs.

Changing this value requires the ENL service and its dependent to be restarted.

Verbose

(ENL\System)

This parameter controls the level of detail shown in diagnostic trace log messages.A lower number means less detail.



VolumeLevel

Note: Modifying multiple parameters may have unpredictable and adverseconsequences. Symantec recommends that these parameters be changed only byknowledgeable users or at the guidance of Symantec Technical Support.

Changing Settings Utility parametersChanging Settings Utility parameters may require restarting CPS services orsystems on one or more servers in the Backup Group. Before changing anyparameter, please review the cautions associated with that parameter in the CPStunable parameters list. This information will also be displayed during theparameter changing procedure.

To change Settings Utility parameters

1 Open the Settings Utility.

2 In the Server pane, select the server whose parameters you want to reviewor change.

3 In the Parameters pane, double-click anywhere in the row of the parameterthat you want to change, and then enter the new value.

4 Click OK to continue.


5 Review the warning information, and then click OK to change the parametervalue.

6 Restart the services or computers as noted in the warning prompt.


90

Backing up data


■ About CPS backup jobs

■ Creating CPS backup jobs

■ Editing backup job configurations

■ Moving a backup job to a different backup destination

■ Starting, stopping, and canceling backup jobs manually

About CPS backup jobsContinuous Protection Server lets you create a variety of backup jobs to protectyour data. As the needs of your business change, you can add or delete backupjobs, or set new properties for existing backup jobs.

After a CPS backup job has been created, you can further modify the job by definingadditional functionality such as the following:

■ You can define exceptions to backup rules. For example, if you want to backup everything in the Marketing Proposals folder except temporary files,exceptions can be defined for the temporary files.

■ You can filter drivers to capture changed bytes in files and copy the changedbytes to the destination. Snapshots of the destination are taken at regularintervals. Each snapshot is saved for 24 hours unless you specify otherwise.

■ You can run scripts before or after a backup job. Advanced settings are availablefor defining pre- and post-scripts to run before and after backup jobs. Forexample, you can close a database or run a virus scan on a folder before abackup job starts.

5Chapter

■ You can limit bandwidth so a job uses fewer resources. Advanced options areavailable for setting bandwidth restrictions.

About backing up System State and Shadow Copy ComponentsThe Windows operating system includes data that requires special handling sothat you can backup and restore it properly. This data, referred to as SystemInformation in CPS, contains different information depending on the version ofWindows that is installed on the computer.

CPS can protect system information (System State and Shadow Copy Components)as you would protect other data sets. This is accomplished by creating a CPSbackup job and selecting the System State or Shadow Copy Components for backup.

CPS treats the System State and Shadow Copy Components as separate, but related,data sets. If you need to back up or restore either of them, all of the data containedin each set will be backed up or restored.

If a continuous job is created to back up system information, it is captured bydefault once every four hours at 3:05 A.M., 7:05 A.M., 11:05 A.M., 3:05 P.M., 7:05P.M., and 11:05 P.M. Do not attempt to restore System State data around thesesame times. The restore may fail because a System State restore does not interrupta System State data capture that is in progress.

When System State or Shadow Copy components and unrelated files are backedup in the same backup job and the System State or Shadow Copy backup job fails,the unrelated files are not backed up. System State or Shadow Copy backups shouldbe configured separately from regular file backups to better control schedulingconflicts and possible lapses in protection.

See “Restoring system information” on page 105.



How encrypted files are handledFiles that are encrypted using Microsoft’s Encrypting File System (EFS) are notcopied over the network from the Business Server to the Protection Server, andtherefore are not backed up.

Creating CPS backup jobsJobs can be created from any Administration Console within the Backup Group.Usually, new jobs are created to back up data from a Business Server to a ProtectionServer using the Backup Job Wizard. The information that is required and general

Backing up dataCreating CPS backup jobs

92

steps for creating a backup job manually or using the wizard are essentially thesame.

When you create a backup job, you can specify the following information:

■ Name and description of the backup job

■ Backup destination

■ Location of the data to be backed up

■ Schedule for the backup to occur

Before you can create a backup job, be sure that you have already defined a backupdestination.


See “Adding a backup destination” on page 69.

All regular shares are backed up automatically by the backup job. The share backupjob backs up the information about the share, but not the underlying data for theshare. If you want to back up the data that the share points to, you must selectthe folder containing that data when you configure the backup job. When youselect the folder containing the data, the share and the data are both backed up.You can restore the data, the share information, or both.

The data in the tree view is selected for inclusion or exclusion, and the status isreflected with icons.

Table 5-1 describes the status icons that are used in the tree view.

Table 5-1 Status icons

DescriptionStatus icon

Everything under this directory is selected for backup. Anything new addedto this directory (or its subdirectories) is automatically selected for backup.

This directory is excluded from the backup. If this directory was previouslybacked up, it is removed from the backup destination.

Some or all of the subdirectories of this node can be selected for backup.Anything new added to this directory may or may not automatically bebacked up. For example, a folder may contain an exclude rule for *.exe. Ifthe file word.exe is added to the folder, it is not backed up, but the filework.doc is backed up.

This node has not been selected for backup, and neither have any of itssubdirectories. Some subdirectories may have been excluded (see the red‘x’), which causes them to be removed.

93Backing up dataCreating CPS backup jobs

Backup rights are required to all referenced servers of a CPS backup job, includingthe server hosting the Continuous Management Service.

To create a CPS backup job


2 In the task pane, under Backup Job Tasks, clickNewbackupjobusingwizard.

3 Review the text on the Welcome to Backup Job Wizard screen, and then clickNext.

4 On the Name the Backup Job screen, type a name and optional descriptionfor the backup job.

5 On the Select a Backup Destination screen, select one of the defined backupdestinations. This selection is the Protection Server where the data is backedup.

6 On the Select Data to Back Up screen, select the information that you wantto back up.

7 On the Select When to Backup screen, designate when the backup shouldoccur.

Initiates a continuous backup of the folder orfile. That is, a file or folder is backed upwhenever changes are made to it. This jobstarts as soon as the user clicks OK.

Whenever a file changes

Lets you set a regularly scheduled or periodicbackup of the folder or file. If this option isselected, you need to define the backupschedule. This job starts if it is in the backupwindow and the user clicks OK.

Backup job schedules are always shown in thelocal time of the user who is creating thebackup job. If backup jobs are created forservers that are located in other time zones,you must convert that server’s time to yourlocal time.

According to a schedule

Lets you back up the contents of the folder orfile on demand. This job will not startautomatically.

Initiate the backup job manually

8 Verify that the backup job was created by observing that the Job shows onthe list of jobs from the Job Monitor.

Backing up dataCreating CPS backup jobs

94

Editing backup job configurationsBackup jobs are restarted if the job is modified while it is running.

To edit backup job configurations


2 In the selection pane, click Backup Jobs.

3 In the results pane, right-click the backup job, and then click Properties.

4 Under Settings, click General.

5 Edit the entries as needed.

Moving a backup job to a different backupdestinationBackup jobs can be moved to a different backup destination after they have beencreated.

Moving a job between backup destinations does not delete the data from theoriginal backup destination. Instead, after the backup destination has been changedand the job has run, a dialog box is displayed informing the user of the change.The user can launch Windows Explorer to display the root folder of the originalbackup destination. In the Explorer window, the user can delete the job datamanually or leave it there. Also, when a backup destination resides on a remotecomputer, the admin share is used as a path to this folder.

To move a backup job to a different backup destination




4 Select the new backup destination for the job from the Backup destinationdrop-down list.

5 Click OK to save the backup destination and run the job.

Including and excluding information from backup jobsBackup selections define what data you want to back up. Exceptions to theselections are defined by including and excluding information from the selection.For example, you select a marketing proposals folder to back up. To save resources,you may want to exclude temporary files.

95Backing up dataEditing backup job configurations

Note:When files or directories are explicitly excluded, they are removed from thebackup destination. If files or directories are not selected, they are not removed.

You can add any combination of include and exclude filters to each backupselection. This enables you to select files to back up whose names match anarbitrary combination of patterns.

For example, if you want to exclude all tmp files from the backup, except for thosewhose names contain the letter Q or the letter X, you can specify the followinglist of filters:

■ Include *Q*.tmp

■ Include *X*.tmp

■ Exclude *.tmp

Be sure you specify the parameters in the right order. Parameters are appliedtop-to-bottom as listed, and the first rule matching a file name is the one that isused to decide whether or not to back up a file.

When initially adding a filter, you can enter a semi-colon delimited list to specifymultiple filters to add. Each item on the list is added as a separate filter. If youlater edit an existing filter, you are not able to add a semi-colon delimited list.

To include and exclude information from backup jobs




4 Under Settings, click Backup Selections.

5 Expand the tree to expose the files that are selected for the backup job.

6 Right-click the file or folder that is selected for the backup job, and then clickIncludes/Excludes.

7 Click Add.

Backing up dataMoving a backup job to a different backup destination

96

8 Select the options you want.

Kind of filter. Your options are Include or Exclude.

Inclusive filters define the kinds of information toinclude. For example, if all temporary files are excludedfrom backups, you can include temporary files withthe letter Q in the file name.

Exclusive filters define the kinds of information toexclude. For example, if a marketing proposals folderis included in a backup, you can exclude the folder’stemporary files.

The information you want to include or exclude isdefined in the Filter field.

Type

Criteria that specifies what information to include orexclude.

For example, your backup selections include amarketing proposals folder, and you are excludingtemporary files. The type of rule is Exclude and thefilter is *.tmp. Use a semicolon-delimited list to addseveral items at once.

Filter

Select this option if the include or exclude filters applyto subdirectories of the backup selection.

Apply to Subdirectories

9 Click OK.

10 If you want to change the priority of a filter, select the filter, and then clickMoveUp or MoveDown.

11 Click OK.

12 On the Backup Job Properties dialog box, click OK.

Editing filtersYou can edit the include and exclude filters to refine what gets backed up.

To edit filters



3 In the results pane, right-click the job, and then click Properties.


97Backing up dataMoving a backup job to a different backup destination

5 Expand the tree to expose the files or folders that are selected for the backupjob.


7 Select a filter, and then click Edit.

8 Select the appropriate options.

9 Click OK.

10 If you want to change the priority of a filter, select the filter, and then clickMoveUp or MoveDown.

11 Click OK.


Deleting filtersYou can delete include and exclude filters that you no longer use.

To delete filters





5 Expand the tree to expose the files or folders that are selected for the backupjob.


7 Select a filter, and then click Delete.

8 Confirm that you want to delete the selected filter.

9 Click OK.


Changing a backup job scheduleAs your data protection needs change, you may need to change the backupschedule.

Backups can be scheduled to run as the following:

■ Continuously (whenever changes are made to a file)


98

■ Periodically (according to a schedule)

■ As needed (manually)

Backup job schedules are always shown in the local time of the user who is creatingthe backup job. If backup jobs are created for servers that are located in othertime zones, the specific time must be converted to your local time.

You can review descriptions of the various backup job schedules.

See “About backup job schedules” on page 22.

To change a backup job schedule




4 Under Settings, click Schedule.

5 Under Back up the selected files and folders, select the option that you want.

Initiates a continuous backup of the folder orfile.

Whenever a file changes

Enables you to set a regularly scheduled orperiodic backup of the folder or file. You needto define the backup schedule.

According to a schedule

Requires you to manually start the backup jobfrom the CPS Console.

Initiate the backup job manually

6 Under Back up the selected files and folders, select According toa schedule.

7 Click Edit Schedule.

8 Select the options you want.

Select the check box next to each day that youwant the snapshot to occur.

Run on these days

Select and define a specific time for thesnapshot to occur.

Run only at

Select and define the intervals at which thesnapshot occurs.

Run

9 Click OK.

10 Click OK in the Backup Job Properties dialog box.

99Backing up dataMoving a backup job to a different backup destination

Limiting the network bandwidth of a backup jobContinuous Protection Server lets you specify network bandwidth properties tobetter manage your resources during backup jobs.

The network bandwidth setting applies to all active backup jobs running betweentwo computers. The most restrictive bandwidth setting is applied to all runningjobs.

To limit the network bandwidth of a backup job



3 In the results pane, select the backup job.

4 In the task pane, under Backup Job Tasks, click Properties.

5 Under Settings, click Bandwidth.

6 Click Add.

7 Complete the options that you want.

Select the server from which the files are copiedduring the backup job.

Source server

Select the bandwidth that is allocated to the backupjob process.

Limit bandwidth usage to

Select the type of connection existing between theBusiness Server and Protection Server.

Network connection type

8 Click OK.

9 Click OK in the Backup Job Properties dialog box.

Adding a script that runs before or after backup jobsYou can run a script before running a backup job to perform a task such as closinga database. Similarly, you can run a script after a backup job is completed toperform a task such as running a virus scan.

Running a script requires certain user rights and credentials.


To add a script that runs before or after backup jobs




100

3 In the results pane, select the backup job.

4 In the task pane, under Backup Job Tasks, click Properties.

5 Under Settings, click Commands.

6 Click Add.

7 Specify the following options:

Select the server on which to run the script.Server

Select when the script will run. Your choices arePre-backup or Post-backup.

Event

Type the path to the script file that will run beforeor after this backup job. If necessary, you can browseto the file.

Script

Select the number of minutes before the backup jobis canceled if it is not completed.

Cancel command if notcompleted within xx minutes

Select this option to start a script and continueprocessing.

To run the pre-command script to completion beforestarting the backup, or to run the backup tocompletion before starting the post-command script,uncheck this option.

Run asynchronously

Starting, stopping, and canceling backup jobsmanually

You can manually manage CPS jobs, including starting, stopping, and cancelingjobs.

Stopping a job ends the job after all of the files are copied to the destination.Canceling a job ends the job immediately. Canceling a job that is running canresult in an incomplete file on the destination.

To start, stop, or cancel backup jobs manually

1 On the navigation bar, click JobMonitor.

2 In the Current Job Filter box, click All jobs, Backup jobs, or Restore jobs.

3 In the results pane, right-click the job.


101Backing up dataStarting, stopping, and canceling backup jobs manually

To start the job, click Start Job.■

■ To stop the job, click Stop Job.

■ To cancel the job, click Cancel Job.

Backing up dataStarting, stopping, and canceling backup jobs manually

102

Restoring data


■ About restoring data with Continuous Protection Server

■ Restoring files and folders

■ Restoring system information

■ Restoring System State to an Active Directory system

■ Restoring network shares

About restoring data with Continuous ProtectionServer

Continuous Protection Server lets you quickly restore information. Administratorscan view all backups when selecting files to restore.

Note:Restore selections are used for the current session only. If you end a sessionwithout restoring selected files, the files must be selected again. ContinuousProtection Server refreshes the selections at the end of a session to ensure thateach user begins the restore job with a new record.

If Business Servers in the Backup Group are running Microsoft Windows Server2003, data can be restored back to the Business Servers directly from Backup Exec.If Business Servers are running under other operating systems, files from BackupExec must be restored to a Protection Server. You can then use CPS to restore thefiles to the Business Servers.

6Chapter

When an alternate restore destination path is chosen, be careful not to select anypath with data that needs to be saved. Continuous Protection Server overwritesthe data in the selected folder.

See “Protecting CPS with Backup Exec” on page 126.


See “Restoring Continuous Protection Server with Backup Exec” on page 129.

Restoring files and foldersYou can restore files and folders using CPS Administration Console. Selected filesin a restore job are copied from any backup destination to any computer in theBackup Group. You can restore data only, the share only, or both. Select datacarefully to ensure the restore job copies the information you want.

Note: If data has been backed up from a Business Server to a Protection Server,and the Business Server is later deleted from the Backup Group, the data cannotbe restored, even to another Business Server.

See “Restoring network shares” on page 107.

When an alternate restore destination path is chosen, be careful not to select anypath with data that needs to be saved. Continuous Protection Server overwritesthe data in the selected folder.

To restore files and folders

1 On the navigation bar, click Restore.

2 In the selection pane, select the information to restore.

3 In the task pane, under Restore Tasks, click Restore files.

Restoring dataRestoring files and folders

104

4 Specify the options that you want.

Abbreviated name of this restore job.

For example, WCMKTProposals.

Restore job name

Full name or brief description of the restore job.

For example, West Coast Marketing ProposalsRestore Job.

Description

Location where the selected files and folders willbe copied.

Restore to

Restore to original folder - Restores the selectedfiles to the folder where they originated.

Redirect the restore to an alternate folder -Restores the selected files to the folder of yourchoice. Type the path to the folder in the text box.

Options

Maintains the tree structure of the selected filesand folders during the restore. This check box isselected for redirected restore jobs. If this optionis not selected, the contents of the restore folderare added to the alternate restore folder.

When restoring folders containing reparse points,you must either select the Preserve folderstructure option or restore the folder to an emptyfolder.

Preserve folder structure

5 Click OK.

6 Click OK to clear the confirmation message.

Restoring system informationRestoring system information (System State or Shadow Copy Components) involvescopying specific files from a Protection Server back to a Business Server.

Note: You should not restore system information to servers other than the serverfrom which the information was originally backed up. Redirecting systeminformation restores to other servers will have unpredictable results.

System Information is captured once every four hours at 3:05 A.M., 7:05 A.M.,11:05 A.M., 3:05 P.M., 7:05 P.M., and 11:05 P.M. If you attempt to restore System

105Restoring dataRestoring system information

State data at or near these same times, the restore may fail because a System Staterestore does not interrupt a System State data capture that is in progress. In thiscase, the System State restore jobs should be started well before or about 10minutes after the backup times.

See “About backing up System State and Shadow Copy Components” on page 92.

To restore system information


2 In the selection pane, select the System State or Shadow Copy Components.



Abbreviated name of the restore job.

For example, WCSRCSystem.

Restore job name


For example, West Coast Source Server System State.

Description

System State will always be restored to its original location.Restore to

5 Click OK.


When the System Information is restored, the server will automaticallyrestart.

Restoring SystemState to anActiveDirectory systemSystem State can be restored to a system that is an Active Directory.

Before restoring System State to an Active Directory system, you must have orcreate a Directory Services Restore Mode (DSRM) password. For information onDSRM passwords, see the Microsoft support article “How To Reset the DirectoryServices Restore Mode Administrator Account Password in Windows Server 2003”on the Web.

Symantec does not recommend restoring System State to servers other than theserver from which the System State was originally backed up. Redirecting SystemState to other servers will have unpredictable results.

For more information about how to restore System State in Continuous ProtectionServer, go to the following URL:

Restoring dataRestoring System State to an Active Directory system

106


To restore System State to an Active Directory system


2 In the selection pane, select SystemState.


4 Specify the options you want.


For example, WCSRCSystem.

Restore job name


For example, West Coast Source Server System State.

Description

System State will always be restored to its original location.Restore to

5 Click OK.

6 Click OK to clear the confirmation message. The computer will restart inDSRM mode.

7 Log on using your DSRM password.

8 Double-click the symantec dsrm system state restore.bat file, which is locatedon the Desktop. You can monitor the progress in the command window.

When the System State restore has completed, the server will automaticallyrestart back in normal mode.

Restoring network sharesRestoring network shares involves restoring the data, the share, or both. If youprotect a server, users of Backup Exec Retrieve can only access files and foldersthat were originally written to a share. After restoring shared folders, the screenmust be refreshed before the shared folder icon appears.

Network shares cannot be restored if they are in use at the time of the restore.

See “Restoring files and folders” on page 104.


To restore network shares


2 In the task pane, under Views, click Console restore.

107Restoring dataRestoring network shares

3 In the results pane, select the restore job.


■ To restore the share only, in the selection tree pane, do not select anyinformation to restore.

■ To restore the data and the share, in the selection tree pane, select thefiles and folders to restore.

5 In the selection list pane, select the shared folder.

Items in the list view belong to the share. Selecting items in the selection listpane restores the share. If any attribute in the share changes, the share mustbe disabled before restoring. Attributes appear in the Microsoft WindowsProperties dialog box for the shared item and include the share name,comments, user limits, and permissions.




For example, WCMKTShare.

Restore job name


For example, West Coast Marketing Shared Folders.

Description

Location where the selected files and folders willbe copied.

Shares can only be restored to their originallocation, although the files in a share can berestored elsewhere.

Restore to

Restore to original folder - Restores the selectedfiles to the folder from which they originated.

Redirect the restore to an alternate folder -Restores the selected files to the folder of yourchoice. Type the path to the folder in the text box.

Options

Maintains the tree structure of the selected filesand folders during the restore. This check box isenabled for redirected restore jobs.

Preserve folder structure

8 Click OK.


Restoring dataRestoring network shares

108

Using Backup Exec Retrieve


■ About Backup Exec Retrieve

■ Features of Backup Exec Retrieve

■ Security and credentials for Backup Exec Retrieve

■ Retrieving files by using Backup Exec Retrieve

■ Using CPS with Backup Exec Desktop and Laptop Option

About Backup Exec RetrieveContinuous Protection Server lets users restore files directly back to theirworkstation through the Web Retrieval Interface and a Web browser. Users canview and retrieve the contents of shared folders to which they have permission.

Web Retrieval Interface is optimized for Microsoft Internet Explorer (6.0 or later).Web Retrieval Interface also works with other Internet browsers, although screenlayouts may vary. Likewise, Web Retrieval Interface uses Windows security andInternet Explorer download features. Thus, Web Retrieval Interface is limited toWindows-based platforms.

Web Retrieval Interface is designed to enable users to restore their everyday files,such as spreadsheets, word processor documents, and PST files. It is not designedto restore system databases or other system-level files. Likewise, users cannotdelete files by using Backup Exec Retrieve.

Features of Backup Exec RetrieveBackup Exec Retrieve enables desktop and laptop users to recover their own fileson demand. You can search for files by name, browse through files in shared

7Chapter

folders, or view recently changed or deleted files. Downloading selected filesrestores the selected copy to the user’s computer.

Table 7-1 describes the features that are available in Backup Exec Retrieve.

Table 7-1 Backup Exec Retrieve features

DescriptionFeature

Find files by name. Use standard Windows-like search capabilitiesto find a file when the file name is unknown or only partiallyknown.

Search

Navigate through shared folders to which you have permissions,and view any of the files that were backed up. When a file islocated, you can view all stored versions of that file. Review thedate, time, and file size to determine the version of the file thatyou want to retrieve.

Browse

View a list of files that were recently modified or deleted. Recentactivity includes files from the earliest through the latest snapshoton record. The file list is sorted in order by files from today,yesterday, last week, two weeks ago, and older.

The Recent Activity list does not show any files that have beenmodified or deleted after the last snapshot was taken.

Recent Activity

Restore files in a manner similar to buying items in an onlinestore. Select files for download while searching, browsing, orviewing recent activity. Review the list of files, and then downloadall of the files at once. Unless specified otherwise, the files aresaved to My Documents\My Restored Files.

Download List

About reparse pointsContinuous Protection Server detects files on sources in the Continuous ProtectionServer Backup Group that were given reparse points as place holders from anapplication such as Single Instance Storage (SIS) or Hierarchical StorageManagement (HSM). Continuous Protection Server copies the raw informationinside the reparse point to the Protection Server. This information is generallynot useful until it is restored to the same server from which it originated.

Files with reparse points are not displayed or available in Backup Exec Retrieve.

Using Backup Exec RetrieveFeatures of Backup Exec Retrieve

110

Security and credentials for Backup Exec RetrieveWeb Retrieval Interface is protected by Windows-level security. You will beprompted for your Windows domain logon information. This information is usedto restrict the files that you can view and retrieve.

If you protect a server, users of Web Retrieval Interface can only access files andfolders that were originally written to a share. That is, unless a folder is sharedon a file server, you cannot see or retrieve the files.

Internet Explorer security on Windows Server 2003This topic only applies to user workstations operating on Windows Server 2003.When restoring files as a desktop user, Continuous Protection Server is optimizedto display Web Retrieval Interface through the Microsoft Internet Explorer (IE)browser. To ensure the retrieval process runs smoothly, you must define thedestination as a trusted site in IE. Alternatively, you can lower the security settingsfrom High to Medium. However, the security settings should be lowered at yourown risk. By setting the Protection Server in IE as a trusted site, the higher levelof security is maintained and the Web Retrieval Interface appears correctly.

Refer to the Microsoft Internet Explorer documentation for information aboutadding a trusted site to IE or changing the level of security. The site to added ishttps://<CMSServerName>:8443

Retrieving files by using Backup Exec RetrieveDesktop users can restore files using Backup Exec Retrieve, which is accessedthrough your Web browser and a designated URL.

Files that are downloaded with Backup Exec Retrieve are saved with the defaultpermissions of the folder they are placed into. This is like other files that aredownloaded from the Internet.

To retrieve files using Backup Exec Retrieve


■ On the Tools menu, click Backup Exec Web Retrieve.

■ In the Web browser address bar, type the URL of your ContinuousManagement Service.

The default URL is https://<CMSServerName>:8443/BERetrieve where<CMSServerName> is the name of the server hosting the ContinuousManagement Service, and 8443 is the port number.

111Using Backup Exec RetrieveSecurity and credentials for Backup Exec Retrieve

The term BERetrieve at the end of the path is case sensitive. Contact yoursystem administrator if you do not know the name of the CMS server.

2 If the standard Windows Security Alert screens are displayed, click Yes orOK to continue.

3 If a message appears with information about the security certificate, it isrelated to SSL Certificates. Click Yes to continue.

4 Type the user name, password, and domain (or computer name if in aworkgroup).

5 Click Log on.

6 Select one of the following tabs to locate and specify the data to be retrieved.

Lets you search for the data by file name.Search

Lets you browse for the data.Browse

Lets you select data from the files that were recentlymodified.

Recent Activity

7 Click the computer name to display the folders that have been backed up.Subsequent clicks on the folder name allow you to navigate deeper intosubdirectories. At any level, you can use the check box to select that folderand subordinate folders and files.

The Versions field is added to the data listing whenever filesare displayed. Click the versions icon to show all the versionsof a particular file.

8 To view recently modified or deleted files, on the Recent Activity tab, do oneof the following:

■ Click RecentlyModified to view modified files.

■ Click RecentlyDeleted to view deleted files.

9 Click Add toDownloadList to add the file to your list of data to be retrieved.

10 If necessary, add more files to the download list using the Browse tab.

11 Select the Retrieve List tab to view a list of all selected files.

12 In the Internet Explorer File Download screen, click Open (or Run) todownload a small executable file (downloadmanager.exe) that restores theselected files.

Using Backup Exec RetrieveRetrieving files by using Backup Exec Retrieve

112

13 In the File Restore screen, select the default <user>\My Documents\RestoredFiles, or browse to a location.

14 Click Next to begin the file retrieval.

15 Verify that the selected files were restored.

Using CPS with Backup Exec Desktop and LaptopOption

With CPS, Backup Exec Web Retrieve may be associated with Backup Exec Desktopand Laptop Option (DLO) so that users can restore their data that was copied toa network share by DLO.

To enable DLO integration with CPS, the Continuous Management Service (CMS)must be installed on the same computer as Backup Exec. Additionally, theadministrator needs to install a Continuous Protection Agent (CPA) on each DLOfile server. The CPA installation can be performed by manually running setup oneach computer, or by using the push-install mechanism in the CPS AdministrationConsole. The Console helps the administrator with this task by indicating DLOfile servers in the CPS push-install computer selection list.

See “Push-installing Continuous Protection Server components” on page 47.

The initial indexing of the DLO file server may take significant time, during whichthe search results may be incomplete. The CPS Console will display an alert whenthe initial indexing is completed. Additionally, the user sees a warning to thiseffect while the initial indexing is running.

When searching for files, you can find DLO files based on their filenames, and allversions of the DLO file that match the criteria (excluding local revisions). RecentActivity searches include DLO files and files that were written directly to shares.Additionally, DLO results in both search and recent activity display a unique iconto distinguish them as DLO results.

Files are indexed nearly immediately after being copied to the DLO file server.Snapshots are not required or recommended on the DLO file server to begin theindexing. If there are snapshots of the DLO file server, they are ignored forDLO/CPS integration purposes.

You can restore DLO data.


113Using Backup Exec RetrieveUsing CPS with Backup Exec Desktop and Laptop Option

Securing data that is not retrievableBackup Exec Retrieve does not restore Windows Encrypted File System (EFS) files.Likewise, compressed or sparse files are restored in their entirety (not compressedand not sparse). Reparse points are also not restorable using Backup Exec Retrieve.

Permissions and other information are lost as a side-effect of Web downloads.DLO unencrypts EFS files, and then re-encrypts them (optionally) with their ownkey. Thus, users can restore EFS files that are protected by DLO using BackupExec Retrieve, but the restored file is no longer encrypted on the user’s computer.

PST and Lotus Notes files can also be restored, but only the entire file.

Files on DLO file servers that are located on FAT32 partitions are browsable, butnot searchable.

Using Backup Exec RetrieveUsing CPS with Backup Exec Desktop and Laptop Option

114

Monitoring CPS processes


■ About the Job Monitor

■ Monitoring jobs and job pairs

■ Viewing a job report

■ Managing CPS job alerts

About the Job MonitorYou can monitor CPS jobs that are active, scheduled, or completed. The Job Monitoralso allows you to manually start, stop, or cancel jobs. You can narrow the list ofjobs by showing only jobs from the last seven days or the last 24 hours.

The list of jobs that appears in the Job Monitor view can be filtered to include thefollowing:

■ All jobs

■ Backup jobs only

■ Restore jobs only

Likewise, each column in the Job Monitor view can be sorted and the columns canbe rearranged by dragging a column heading to the left or right.

The following terms need to be documented in this chapter:

■ View job log

■ Monitor pair

■ View pair log

8Chapter

Monitoring jobs and job pairsA CPS backup job can contain one or more CPS job pairs. At the most basic level,a job pair is a one-to-one relationship between a single source server and singledestination server.

In the case of a CPS backup job containing four Business Servers backing up to asingle Protection Server, the following job pairs exist:

■ Business Server #1 to Protection Server #1 (1:1)




In CPS, the job represents the process that maintains the activity of each of thespecific job pairs. You can view properties and change the status of an active job.The CPS job controls the job pairs and reflects what the job is supposed to bedoing. The job pair states, however, reflect what is actually occurring.

About job statesA job has errors if any error occurs on any job pair; that is, Business Server orProtection Server. To determine the status of an active CPS job, you must viewthe job status and any associated errors or alerts.

Table 8-1 lists the various job states.

Table 8-1 Continuous Protection Server job states

DescriptionJob state

The job is attempting to start every job pair for the first time.

Errors and alerts indicate if one or more pairs were unable to startor stopped before completing.

Starting

The starting phase has completed. That is, all job pairs haveattempted to start.

Errors or alerts indicate if any pairs are attempting to restart.

For a continuous job, the job remains in this state until the useror schedule cancels the job.

For a scheduled, non-continuous job, the job remains in this stateuntil the job is completed, or the user or schedule cancels the job.

Running

Monitoring CPS processesMonitoring jobs and job pairs

116

Table 8-1 Continuous Protection Server job states (continued)

DescriptionJob state

The job is attempting to stop. The user or schedule has commandedthat each pair complete synchronization and then stop running.

Errors and alerts indicate failures of one or more pairs to respondto the stop request or to have reached full synchronization.

Stopping

The job has stopped and all pairs have completed synchronization.

A stopped job state does not affect the schedule of a job. That is,the job will run at the next scheduled time.

Stopped

The job is attempting to stop abruptly. That is, the user or schedulehas commanded that each pair stop running whether or not theyhave achieved synchronization.

Errors and alerts indicate failures of one or more pairs to respondto the cancel request.

Canceling

The job has canceled and all pairs have stopped running.

A canceled job state does not affect the schedule of a job. That is,the job will run at the next scheduled time.

Canceled

If the job is a scheduled, non-continuous job, all pairs havecompleted.

If the job is continuous, the job never completes. A continuous jobmust be stopped or canceled.

Completed

Viewing the status of a job and job pairsA backup job may consist of several Business Servers being backed up to aProtection Server. Each Business Server-Protection Server connection for a specificjob constitutes a job pair. The status of each job and job pair can be monitored toprovide job details and logs.

The current jobs appear in the upper results pane, and the pairs that are associatedwith a selected job appear in the lower results pane.

Table 8-2 lists the status information that is provided for the job listings columns.

Table 8-2 CPS job status

DescriptionColumn

Current jobs status

117Monitoring CPS processesMonitoring jobs and job pairs

Table 8-2 CPS job status (continued)

DescriptionColumn

The name that was given for the job.Job name

Description

The job type can be one of the following:

■ Backup

■ Restore

■ Exchange Log

Type

See “About job states” on page 116.Status

The instantaneous rate that the job is running. For example, 21Kbytes/Second.

Transfer Rate

The cumulative rate since the job (or pair) started. For example,21.3 MB

Transferred

Indicates whether errors are associated with the job. Possiblevalues are Yes or No.

Errors

Indicates the number of errors or warnings to which no oneresponded.

Alerts

Indicates the type of schedule that was designated for the job.Schedule Type

Indicates the time that the job was last started.Last Start Time

Table 8-3 identifies status information that is provided for job pair listings(columns).

Table 8-3 CPS pair status

DescriptionColumn

Current jobs status

The name of the source computer.Source

The name and path to the destination computer.Destination

See “About job states” on page 116.Status

The instantaneous rate that the job is running. For example, 21Kbytes/Second.

Transfer Rate

Monitoring CPS processesMonitoring jobs and job pairs

118

Table 8-3 CPS pair status (continued)

DescriptionColumn

The cumulative rate since the job (or pair) started. For example,21.3 MB

Transferred

Indicates the number of errors or warnings to which no oneresponded.

Alerts

Indicates the time that the job pair was started.Start Time

Indicates the time when the job pair last stopped.Stop Time

To view the status of a job and job pairs


2 Check to see if this step is still true. To narrow or expand the job history, inthe Job History Filter box, select one of the following:

■ Last 24 hours

■ Last 7 days

■ All

Viewing a job reportYou can view detailed information about CPS jobs in the Job Report.

To view a job report


2 In the results pane, under Current Job Tasks, select one or more jobs.

3 In the task pane, select View job report.

A Job Report is generated and displayed in a separate window.

4 Expand the report headings by clicking the plus sign [+] to the left of theheading.

CPS job report detailsThe information that is contained in the CPS Job Report consists of various topicboxes that are arranged by the information presented.

119Monitoring CPS processesViewing a job report

Job Report topic boxThe first topic box, Job Report, provides a summary statement on the quality ofthe CPS jobs. There are two possible states for CPS jobs: all CPS jobs are good andone or more problems exist with the CPS jobs.

CPS jobs topic boxesEvery CPS job has a topic box that displays in the job report and contains all theinformation that is related to that job. The title of the box is the name of the CPSjob. This box contains a header and a details box. If the Job has any exceptions,the box will be orange (warning color).

Table 8-4 lists the subordinate topic boxes that are available for each CPS job.

Table 8-4 Subordinate jobs topic boxes

DescriptionTopic box

Contains a summary of the job at the time the report ran. It showsthe job name, description, type, state, last started time, and laststopped time.

Backup Job Header

Contains the job properties that define how the job was configured.The Job Details boxes contain most of the job properties that arefound on the CPS Job Properties page.

Backup Job Details

Provides a list of the files and folders that are included andexcluded from the job.

Backup Job Selections

Displays any pre- or post-commands that were assigned to thejob. The information that is provided includes the server name,command, triggering event, whether the command is runningasynchronously, and the timeout period.

Backup Job Pre/PostCommands

Contains CPS job log entries for the period since the job last ran.

Job entries with warnings are displayed in orange text, and jobentries with associated errors are shown in red text. Jobs withwarnings or errors are also linked to the Symantec Support Website for possible solutions.

Backup Job Log

One Backup Pair box exists for each pair of the associated CPSjob. The title of the box is the name of the actual CPS pair. If thereis an exception associated with the pair, the box title contains thestate of the pair along with a description of the exceptioncondition.

Backup Pair

Monitoring CPS processesViewing a job report

120

Table 8-4 Subordinate jobs topic boxes (continued)


Contains a summary of the pair at the time the job was run. Itshows the source and destination server names, pair state, laststarted time, last stopped time, destination consistency, anddestination latency.

Destination latency can only be calculated when both servers ina pair are running Continuous Protection Server version 10d orlater.

Pair Header

Contains CPS pair log entries.

Pair entries with warnings are displayed in orange text, and pairentries with associated errors are shown in red text. Pairs withwarnings or errors are also linked to the Symantec Support Website for possible solutions.

Pair Log

Exception topic boxThe Exception topic box provides a summary of warning messages for the variousjobs and pairs. The messages are linked back to the specific incident in the report.

Error topic boxThe Error topic box provides a summary of error messages for the various jobsand pairs. The messages are linked back to the specific incident in the report

Managing CPS job alertsAlerts are messages about a job, source server, or destination server in the BackupGroup, and indicate that a problem exists that requires a response from the user.You can respond to one alert at a time, multiple alerts, or to all alerts at once.

Alerts can be informational or can indicate a warning or an error such as thefollowing:

■ Errors: Red icons

■ Warnings: Yellow icons

■ Informational: Blue icons

Alert history lists the alerts to which an administrator responded. Alerts remainin history for 30 days by default unless you delete them. You can delete one ormore alerts in history.

121Monitoring CPS processesManaging CPS job alerts

When you view active alerts or alert history, you can change the order in whichthe information displays. The list can be sorted in ascending or descending orderby any column.

You can also change the order in which the columns display to view the informationin order by the following:

■ Category

■ Job name

■ Message

■ Server name

■ Time alert received

■ Type

Viewing and filtering active alertsAlerts contain detailed information about the jobs that were run in the BackupGroup and the computers on which they were run. Whether viewing active alertsor history, you can filter alert messages to show all alerts, only errors, onlywarnings, or only informational messages.

To view and filter active alerts

1 On the navigation bar, click Alerts.

2 Click the ActiveAlerts tab.

3 In the Active Alerts Filter box, click an alert whose details you want to view.

4 In the selection pane, select the alert to view the details.

5 Click a column heading to sort the list in ascending or descending order.

6 Click and drag a column to a new position in the list, and then drop it intoplace to change the order in which columns are displayed.

Viewing and filtering alert historyAlert history lists the alerts to which an administrator responded. The alertsremain in history for up to 30 days or until you delete them. When you view thealert history, you can filter the list to show errors, warnings, or informationalmessages only.

To view and filter alert history


2 Click the AlertHistory tab.

Monitoring CPS processesManaging CPS job alerts

122

3 In the Alert History Filter box, click one of the alerts you want.

4 In the selection pane, select the alert to view details.

Alerts older than 30 days are removed by the system.

5 Click a column heading to sort the list in ascending or descending order.

6 Click and drag a column to a new position in the list, and then drop it intoplace to change the order in which columns are displayed.

Viewing alert propertiesAlert properties provide detailed information about each alert. In addition to themessage details, response information appears for alerts in history.

To view alert properties


2 Click the ActiveAlerts or the AlertHistory tab.

3 In the selection pane, right-click the alert, and then click Properties.

Title of the alert.Category

Name of the Business Server or Protection Server onwhich the alert occurred.

Server

Date and time the alert occurred. The time is the localtime of the server.

Time alert received

Name of the backup or restore job, if a job is associatedwith the alert.

Job name

Alert text.Message

4 Click OK.

Responding to active alertsResponses indicate that an administrator received and cleared informational,warning, or error messages about the jobs that were run in the Backup Group.You can respond to one alert at a time, multiple selected alerts, or all alerts atonce. Multiple alerts are selected by pressing <Ctrl>.

123Monitoring CPS processesManaging CPS job alerts

To respond to active alerts


2 On the Active Alerts tab, select the alerts to which you want to respond.

3 Right-click an alert, and then do one of the following:

■ To respond to one selected alert, clickRespond, and then click a response.

■ To respond to all selected alerts, click RespondOK toAll.

If the alerts have an OK response available, they are cleared from the list andmoved to the alert history. If multiple alerts were selected, respond separatelyto each alert that is displayed.

Deleting alerts from alert historyThe alert history contains the alerts that received a response. Alerts remain inhistory for 30 days by default unless you delete them manually. You can deleteone alert at a time, multiple selected alerts, or all alerts at once. Multiple alertsare selected by pressing <Ctrl>.

See “Changing Settings Utility parameters” on page 89.

To delete alerts from alert history


2 On the Alert History tab, select the alerts that you want to delete.


■ To delete an alert, right-click the alert, and then click Delete.

■ To delete all alerts from history, click DeleteAll.

4 Click Yes.

Monitoring CPS processesManaging CPS job alerts

124

Using ContinuousProtection Server withBackup Exec


■ How Continuous Protection Server works with Backup Exec

■ Protecting your Exchange Servers with Continuous Protection Server andBackup Exec

■ Protecting CPS with Backup Exec

■ Monitoring CPS jobs in Backup Exec

HowContinuousProtectionServerworkswithBackupExec

Symantec Backup Exec for Windows Servers enables administrators to performbackup and restore operations between Continuous Protection Server (CPS) andBackup Exec. For example, CPS Protection Server data can be backed up to tape,which provides an additional layer of data protection as well as long-term storageof critical business data.

Using SmartLink technology, CPS jobs can be associated with existing BackupExec jobs. You can view alerts and log entries for CPS jobs through the BackupExec Administration Console.

When you create a job in Backup Exec, each server that is affiliated with CPS islisted as a Continuous Protection Server node in the backup selection tree. If anew Protection Server is added to the CPS Backup Group after backup jobs are

9Chapter

created, you can add a new job or modify an existing job to capture CPS data fromthe new server.

In the event of a system failure or data loss, Backup Exec enables you to restoredata to the CPS Protection Server or a Business Server in the Backup Group.

Additionally, SmartLink technology may be used to check the status of CPS backupjobs, and then view any alerts in Backup Exec. Otherwise, CPS jobs can bemonitored independently through the CPS Administration Console.

Protecting your Exchange Servers with ContinuousProtection Server and Backup Exec

Symantec Backup Exec uses Continuous Protection Server to continuously protectMicrosoft Exchange servers. The association between Backup Exec and CPS isachieved through the Backup Exec Continuous Protection Broker Service that isinstalled with each Continuous Protection Agent.

See “Continuous Protection Server services that are installed” on page 39.

The Broker Service is installed only if the option for the Exchange ProtectionAgent is installed. After the Exchange Protection Agent is installed, Backup Execusers can create a backup job to protect the Exchange database and transactionlogs. The protected transaction logs are part of the Backup Exec Exchange fullbackup set, as well as Recovery Point backups. Recovery Point jobs protect onlythe transaction logs. When the transaction logs are coupled with the Exchangefull backups, more point-in-time restore points are available. In addition, thetransaction log growth on the Exchange server is contained.

Although Exchange protection jobs can only be created from the Backup ExecAdministration Console, CPS users can monitor the status of these jobs in the joblog/report details from the Monitor view of the CPS Administration Console.

For more information about viewing the status of a job or the job pairs, see theSymantec Backup Exec for Windows Servers Administrator’s Guide.

Protecting CPS with Backup ExecYou can back up several types of CPS data with Backup Exec.

CPS data that you can select for Backup Exec backup jobs includes the following:

■ CPS databases that contain information, such as CPS configuration settings,the CMS, and the indexing database.

■ Protection Servers and Business Servers.

Using Continuous Protection Server with Backup ExecProtecting your Exchange Servers with Continuous Protection Server and Backup Exec

126

■ File shares on Business Servers in the Backup Group.

■ Data from specific volumes on Business Servers in the Backup Group.

■ System-level files from Business Servers in the Backup Group.

Procedures for selecting data for backup or restore jobs in Backup Exec are detailedin the Symantec Backup Exec for Windows Servers Administrator’s Guide.

Depending on the kind of data that is backed up, you can use Backup Exec torestore the data to the CPS Protection Server or the Business Server in the BackupGroup from which it was backed up, or to redirect the data to an alternatedestination.


See “Backing up the Continuous Management Service (CMS)” on page 128.

See “Backing up a Protection Server” on page 128.

See “Restoring the Continuous Protection Server ” on page 130.

See “Restoring a CPS Business Server” on page 131.

Configuring CPS for Backup ExecContinuous Protection Server is compatible with Backup Exec for Windows Servers,or Remote Agent for Windows Systems (Remote Agent) version 12 and later.Installing version 12 and later of Backup Exec or Remote Agent is the onlyrequirement to integrate CPS and Backup Exec.

If Remote Agent was not installed with the original CPS installation, install itbefore creating backup and restore jobs with Backup Exec.

See “Performing an initial installation” on page 41.

Backing up CPS with Backup ExecThe procedures for backing up CPS data are the same as backing up other datausing Backup Exec. To protect all CPS data, ensure that backup jobs includeselections from all servers in the Backup Group.

The Continuous Protection Server node is the gateway to all CPS data on the localBackup Exec server. When the Continuous Protection Server node is expanded,Backup Exec displays nodes for databases, protected resources, Business Servers,volumes, shares, and system-level files.

Table 9-1 describes the elements that are found in the expanded ContinuousProtection Server tree view.

127Using Continuous Protection Server with Backup ExecProtecting CPS with Backup Exec

Table 9-1 Continuous Protection Server tree view elements

DescriptionElement

The Continuous Protection Server node is the gateway to all CPSdata on the local server. The Continuous Protection Server orProtected Resources root nodes could be selected for backup.

Continuous ProtectionServer

Databases reside on the Continuous Management Service (CMS).The CMS can be installed on a dedicated server or on a ProtectionServer. If the local server is not the CMS, the Databases node doesnot display.

See “Backing up CPS databases” on page 128.

CPS Databases

Protection Servers are listed in order by name and contain nodesfor the Business Servers on the local server.

See “Backing up a Protection Server” on page 128.

Protection Servers

Business Servers are listed in order by name under the BackupDestination node and contain nodes for CPS Backup data on thelocal server.

See “Backing up Business Servers” on page 129.

Business Servers

Snapshots are listed in order by date and time.

See “Backing up snapshots” on page 129.

Snapshots

Backing up CPS databasesBacking up the CPS databases involves selecting information about the CPSenvironment as it pertains to the installation, CMS, Network Helper, and indexingservice. Select the entire CPS Databases node, or a specific database. Backup Execdisplays the Databases node under the Continuous Protection Server node. Toback up databases, access the tree view from the CMS server and select theDatabases node. The Databases node displays on the CMS server and BusinessServer with a backup destination.

Backing up the Continuous Management Service (CMS)Backing up the CMS involves selecting the server that hosts the CMS, the CMSdatabases, and Network Helper databases.

Backing up a Protection ServerYou can back up the entire Protection Server, one or more backup destinations,one or more Business Servers, or specific volumes, shares, or system-level data

Using Continuous Protection Server with Backup ExecProtecting CPS with Backup Exec

128

from the available Business Servers. To keep critical business data only, selectivelychoose information from specific volumes. Regular backups of the ProtectionServer can help you restore your CPS environment in the event of a disaster.

Backing up Business ServersYou can back up a full Business Server, or selectively back up data from specificvolumes. File shares and system-level files should be backed up whenever theychange, such as when a new share is added.

Backing up snapshotsSnapshots are created by CPS using Microsoft Volume Shadow Copy Service (VSS).They contain copies of the Backup Destination at various points in time. Dependingon your configuration, a snapshot of the CPS Backup Destination may containdata from multiple Business Servers.

It is not necessary to select the root of the Continuous Protection Server node orto back up snapshots regularly. Most of the data that is captured from snapshotto snapshot is redundant because the majority of the data on the server does notchange between snapshots. Back up snapshots only as needed. For example, if aserver is running out of disk space, it might be prudent to back up the oldestsnapshot for archival.

Snapshot data should be backed up from the Continuous Protection Server nodeon an as needed basis. This is because of the quantity of redundant data that thesnapshots typically contain.

Restoring Continuous Protection Server with Backup ExecRestoring CPS and Backup Group data involves selecting information from BackupExec and then doing the following:

■ Restoring the data to a Protection Server.

■ Restoring the data directly back to the Business Server from which it wasbacked up.

When you restore CPS data, you must have rights to the selected servers.

Create or modify restore jobs by selecting data on the Restore Job PropertiesSelections screen.

Restoring the Continuous Management ServiceThe CMS can be hosted on the Protection Server or another server. If the serverthat hosts the CMS fails, Backup Exec can restore the CMS from tape or disk.

129Using Continuous Protection Server with Backup ExecProtecting CPS with Backup Exec

Restoring the CMS includes restoring the CMS and Network Helper databases. Ifthe CMS is also a Protection Server, the CMS, CPA, indexing, and Network Helperdatabases are restored.

All CPS configurations, including servers, backup destinations and jobs, that aremodified after the backup was created revert to their previous state when restored.

Restoring the Continuous Protection ServerUsing Backup Exec, you can restore data to the Protection Server. Restoring aProtection Server involves selecting the Protection Server, the CPS components,and replicas that you want to restore. Backup Exec displays Protection Serverslisted by name under the Continuous Protection Server node.

Backup Exec restores data to the Protection Server from which it originated. Forexample, if you are replacing a Protection Server, you should redirect the restorejob to the new server.

Note: Before restoring data from Backup Exec to CPS, stop all continuous jobs onthe CPS Protection Server and its associated Business Servers. In ContinuousProtection Server, change the scheduled jobs to manual, and then in Backup Exec,restore the selected data.

You should also consider the following points when you restore ContinuousProtection Server from Backup Exec:

■ SmartLink enables communication between Continuous Protection Server andBackup Exec for Windows Servers. That is, SmartLink enables backed up filesthat are stored on the CPS destination to be backed up using Backup Exec.Backup Exec users can restore those files from Backup Exec to a ContinuousProtection Server destination through the Backup Exec Administration Console.Features in Microsoft Windows Server 2003, such as the VSS writer, are usedto back up and restore the files.

■ Restoring files from Backup Exec directly to a CPS source, bypassing the CPSdestination, can be performed under certain circumstances. For example, youcan restore files directly from Backup Exec to a CPS source running WindowsServer 2003.

■ When restoring CPS from Backup Exec, only the whole volume can be restored.

■ To restore to a CPS source running Windows Server 2000, you must first restorethe files from Backup Exec to the Continuous Protection Server destination.The files can then be restored from the destination to the source. The abilityto restore from Backup Exec to a Continuous Protection Server source requiresthe features that are not available in Windows Server 2000.

Using Continuous Protection Server with Backup ExecProtecting CPS with Backup Exec

130

For more information about using Backup Exec Intelligent Disaster Recovery torecover Continuous Protection Server, go to the following URL:


Restoring a CPS Business ServerBackup Exec restores the data back to the Business Server from which it wasbacked up. If you back up a CPS Business Server, you can restore the entire server,the system-level files, individual folders, or individual files. You can redirect CPSbackup data to an alternate destination. System-level files can be restored to theserver from which they originated; however, they cannot be restored to an alternatedestination.

Monitoring CPS jobs in Backup ExecYou can establish a link between CPS and Backup Exec so that you can view alertsand job logs for CPS jobs in the Backup Exec Administration Console. Theconnection between CPS and Backup Exec is established by using the SmartLinkWizard in CPS. SmartLink technology integrates Backup Exec with other Symantecproducts, such as CPS.

The SmartLink Wizard generates a pre-command in Backup Exec, which is acommand that runs before a Backup Exec backup job runs. Using the pre-command,Backup Exec can verify whether the CPS job completed successfully the last timeit ran. This allows Backup Exec administrators to check the status of CPS jobsbefore a backup job is run in Backup Exec to protect CPS data.

See “Understanding the credentials for using Backup Exec SmartLink” on page 131.

See “Setting up a SmartLink connection between CPS and Backup Exec” on page 132.

See “Viewing Backup Exec alerts” on page 134.

See “Viewing Backup Exec job logs” on page 137.

Understanding the credentials for using Backup Exec SmartLinkThe most important criteria in understanding security credentials is to determinethe security context under which SmartLink operates.

SmartLink runs as a pre-command of Backup Exec’s jobs. Backup Exec uses theresource-level credential of the Backup Exec media server to run the pre/postcommands. If the computer level credential is not available, the default logonaccount of Backup Exec is used to run the pre/post commands. The user can changethe computer level credential through the Backup Exec Administration Console.

131Using Continuous Protection Server with Backup ExecMonitoring CPS jobs in Backup Exec

If SmartLink cannot be authenticated by the servers containing the CMS or JobControl Delegate (JCD), the user must create the proper CPS credentials forSmartLink to access the remote CMS or JCD servers.

At a minimum, backup rights are required, which may be created in one of thefollowing ways:

■ Logon as the user that SmartLink will run under.

■ Use the SmartLink command line to create the proper CPS credential. Typethe following:

srbeslnkhost.exe /createcredential /server "server-name" /

domain "domain-name" /user "user-name" /password "password"

Setting up a SmartLink connection between CPS and Backup ExecTo view alerts and job logs for CPS jobs in Backup Exec, you must first establisha SmartLink connection between the two products.


See “Understanding the credentials for using Backup Exec SmartLink” on page 131.

If SmartLink is run with multiple Backup Exec servers with a potential for failoverfrom one server to another, the batch file must be copied to each server fromwhich it might be run. Additionally, it must exist in the same path.

After completing the SmartLink wizard, the status of the CPS job appears in theBackup Exec job log for the associated job. If errors are detected in the status ofthe CPS job, then an alert is generated.

For more information about the command-line syntax, go to the following URL:


The Pre/Post Commands dialog box contains a setting to cancel the command ifit is not completed within a specified time. The specified run time is for all pre-or post-commands that have been defined for the backup job. Thus, if theSmartLink command is contained within a batch file with other commands,sufficient time must be allotted to run all commands. The most significantconstraint on the time that is required to run SmartLink is the amount of logsthat are needed for the backup job. After a backup job is run, the time that isrequired for the actual CPS data gathering is shown in the Continuous Protectionsection of the Backup Exec job log.

See “Monitoring CPS jobs in Backup Exec” on page 131.

See “Viewing Backup Exec alerts” on page 134.

Using Continuous Protection Server with Backup ExecMonitoring CPS jobs in Backup Exec

132

See “Viewing Backup Exec job logs” on page 137.

Note: When creating a SmartLink association with Backup Exec, the ProtectionServer must be specified using the actual name of the server and not an IP address.

To set up a SmartLink connection between CPS and Backup Exec

1 Create a backup job in CPS.

2 Create a backup job in Backup Exec that protects the backup destination ofa CPS Protection Server.

3 On the CPS navigation bar, click Setup.

4 In the task pane, under General Tasks, click CreateSmartLinkusingwizard.

5 Review the information that displays, and then click Next.

6 When the Enter a Backup Exec Media Server screen opens, SmartLink checksthe local server to determine if it is a Backup Exec media server. If it is, thelocal server name is posted in the text box.

If the local server is not a Backup Exec media server (or the appropriate mediaserver), enter the actual name of the server where the CPS backup job islocated.

If a Backup Exec Central Administration Server (CAS) server is specified,SmartLink must be installed on all managed media servers that are selectedfor the job processing. Additionally, if SmartLink is run from a batch file, thebatch file must exist on each managed media server where it might potentiallybe run.

If the selected server is unavailable, a warning screen is posted.

7 Click Next to continue.


8 Enter the appropriate credentials for the selected server, and then click OKto continue. If the credentials are not valid for the specified server, a warningappears and the wizard does not proceed.

The credentials that are required to access the media server may not be validto access the CPS Backup Group registry key on the Backup Exec media server.This registry key is required to verify that the media server is in the sameBackup Group as the Continuous Management Server (CMS).

If the credentials are not valid for the Backup Group registry key, a warningis presented that SmartLink is unable to determine the validity of the Group.

If the credentials are valid, SmartLink determines the extent of the BackupGroup. If the CMS and media server are in the same Backup Group, SmartLinkproceeds. If the CMS and media server are not in the same Backup Group,SmartLink does not proceed.

9 Select the backup job to associate with the CPS job.

Only the jobs that protect the backup destination appear in the Select a BackupExec Job screen.

10 Select the CPS jobs to be monitored, and then click Next to continue.

11 To reduce the number of CPS job log entries, select Limit Log Entries andenter the maximum number of entries per individual CPS job and pair. ClickNext.

SmartLink determines the state of the CPS jobs and pairs, and enters thestates into the Backup Exec Log entries. By default, the CPS Log entries arenot limited between backups. This may result in a very large Backup Exec logfile.

12 Click Finish to transfer the CPS job information to the Backup Execpre-command.

You can verify that the pre-command was successfully associated with theBackup Exec job by viewing the job properties in Backup Exec.

Viewing Backup Exec alertsYou can access and view alerts that are posted to Backup Exec.

The CPS-related alerts are organized by fatal events and CPS job or pair problems.

An alert is not warranted or posted if the CPS jobs are successfully backed up andall the specified CPS jobs are in a good (consistent) state. CPS alerts themselvesare not posted to the Backup Exec alert system.


134

To view Backup Exec alerts

1 On the Backup Exec navigation bar, click Alerts.

2 Select the alert from either the Active Alerts pane or the Alert History pane.

3 Under General Tasks in the task pane, click Properties.

All CPS-related alerts posted to Backup Exec areWarnings (yellow icon) and indicate a problem.

Type and category name

A message or statement describing the conditionthat prompted the alert.

Message

The name of the Backup Exec server being backedup, which is also CPS’s Protection Server.

Server name

The name of the Backup Exec job.Job name

About fatal alertsCertain errors prevent SmartLink from performing its analysis or some part ofits expected behavior, such as retrieving log entries. Each of these conditionsgenerates a Warning alert, and more than one alert can be generated during asingle run of SmartLink.

Table 9-2 describes the fatal alert messages and conditions.

Table 9-2 Fatal alert messages

SolutionConditionMessage

Check network connectivity andthat the CMS is running.

SmartLink is unable to connectto the CMS.

SmartLink is unable to contact the ContinuousManagement Service (CMS). The server maybe down or a network issue may be preventingSmartLink from contacting the CMS. No CPSBackup data validation is possible.

Verify credentials to CMS.

See “Understanding thecredentials for using Backup ExecSmartLink” on page 131.

SmartLink cannot authenticateto the CMS.

SmartLink has failed to authenticate to theContinuous Management Service<CMSservername>. No CPS Backup datavalidation is possible. Check the user nameand password provided to SmartLink.

Attempt to restart the services,and if not successful, contactSymantec Technical Support.

General failure CMS errors. Thisalert is a catch-all fornon-network and non-credentialsbased errors.

SmartLink is unable to contact the ContinuousManagement Service (CMS)


Table 9-2 Fatal alert messages (continued)


Verify credentials to JCD server.

See “Understanding thecredentials for using Backup ExecSmartLink” on page 131.

Failure to authenticate to a JCDindicates that SmartLink isunable to acquire log entries.However, an alert is generatedbecause it is a correctableconfiguration error.

CPS Backup Job <Cpsjobname> - SmartLinkhas failed to authenticate to the JCD Server<JCDservername>. The Job and Pair Logs areUnavailable.

Check network connectivity andthat the JCD server is runningproperly.

JCD is unreachable, which has thesame effect as the failure toauthenticate.

CPS Backup Job <Cpsjobname> - SmartLink isunable to contact the JCD Server<JCDservername>. The server may be down ora network issue may be preventing SmartLinkfrom contacting the JCD. The Job and Pair Logsare Unavailable.

Attempt to restart the JCDservices, and if not successful,contact Symantec TechnicalSupport.

General failure for non-networkand non-credentials based JCDerrors.

CPS Backup Job <Cpsjobname> - SmartLink isunable to contact the JCD server <JCDservername>. The Job and Pair Logs areUnavailable.

Verify that the correct job ID hasbeen entered.

A specified CPS Job ID is invalid.This condition is a correctableSmartLink configuration errorand thus generates a top-levelAlert.

CPS Backup Job <invalidjobid> - Invalid CPSBackup Job ID.

Verify that the correct job namehas been entered.

A specified Job name is invalid.This condition is a correctableSmartLink configuration errorand thus generates a top-levelAlert.

CPS Backup Job <Invalidjobname> - InvalidCPS Backup Job Name

Check the connectivity betweenthe CMS and JCD, and verify thateach is running.

The CPS job is in an unknownstate. In this case, the CMS doesnot have the latest informationregarding a job's run state.

CPS Backup Job <Cpsjobname> - TheContinuous Management Service (CMS) andthe CPS Backup JCD server do not haveconsistent Job State information. The actualstate of Job is unknown.


Unable to get Pair information.CPS Backup Job <Cpsjobname> - Unable to getpair information.


Unable to get JCD information.CPS Backup Job <Cpsjobname> - Unable to getJCD information.


136

Table 9-2 Fatal alert messages (continued)



Unable to get job log information.CPS Backup Job <Cpsjobname> - Unable to getjob log details Information.

About backup pair alertsIf one or more Jobs were discovered to be in an inconsistent state duringSmartLink’s qualification of the CPS job, a pair alert is generated.

SmartLink generates an alert in Backup Exec for every job that has exceptions(errors). Only one alert per job is generated for the entire run of SmartLink. Thisis because there may be hundreds of pairs that are inconsistent and SmartLinkcould easily overwhelm the Backup Exec alerts. Additionally, the Alert messagehas limited space (400 characters) to report the error. Consequently, this alert isa general aggregation of the qualification of all pairs in all of the CPS jobs.

Table 9-3 provides information about the CPS backup pair alert.

Table 9-3 CPS backup pair alert

DescriptionConditionAlert

Review the information forthe Exceptions topic box.

See “Exceptions topic box”on page 140.

One or more pairs in one ormore of the CPS jobs areinconsistent.

CPS Backup Job<cpsjobname> - Exception inOne or More CPS Pairs.

Viewing Backup Exec job logsSmartLink posts detailed information about the CPS backup job in the BackupExec Job Logs.

To view Backup Exec job logs

1 On the Backup Exec navigation bar, click JobMonitor.

2 In the Job History pane, select the Backup Exec jobs that are associated withthe CPS job.


3 Click the Job Log tab to view detailed information about the job.

Under Job Information, details about the job server, job name, date and timethat the job started, the job type, and the job log name appear.

4 Click the plus sign [+] to the left of Job Operation - Continuous Protection Jobto expand the headings.

About CPS backup job log detailsThe CPS job logs contained in the Backup Exec Job Logs consists of various topicboxes.

You can review more details about what displays in the various topic boxes on thejob log.

See “Job Operation - Continuous Protection job topic box” on page 138.

See “Command Line Syntax Error topic box” on page 139.

See “Exceptions topic box” on page 140.

See “Backup Exec SmartLink Options topic box” on page 140.

See “Backup Exec SmartLink Run Log topic box” on page 141.

See “CPS Jobs topic boxes” on page 141.

Job Operation - Continuous Protection job topic boxThe first topic box, Job Operation - Continuous Protection, provides a summarystatement on the quality of the CPS job.

The three possible states for CPS jobs are the following:

■ All CPS jobs are good.

■ One or more problems exist with the CPS jobs.

■ Fatal errors occurred that prevent SmartLink from running.

Table 9-4 provides more information about the summary log messages that mightappear for each state.

Table 9-4 CPS summary log messages

DescriptionMessage

All CPS backup jobs are good

This message appears if all CPS jobs have completed or are running withouterrors.

CPS Backup Jobs are complete or arerunning without errors.


138

Table 9-4 CPS summary log messages (continued)

DescriptionMessage

There are one or more problems

If there are any problems with the CPS jobs or pairs, this message appearsin the CPS Log. Additionally, the Exceptions topic box appears later in theJob Log, which provides details on the specific problems that are encounteredin the CPS jobs.

See “Exceptions topic box” on page 140.

Exception in One or More CPS BackupJobs.

A fatal error has occurred

This message appears when syntax errors are encountered in the SmartLinkcommand line. Additionally, if this message is posted, the Command LineSyntax Error topic box appears later in the Job Log, which provides detailson the nature of the error.

See “Command Line Syntax Error topic box” on page 139.

The SmartLink Command Line HasSyntax Errors.

This error might occur for one of the following reasons:

■ SmartLink may be invoked using invalid Backup Exec credentials, whichprevents SmartLink from connecting to Backup Exec. For example, thismessage appears if all CPS Jobs are good, but invalid Backup Execcredentials were provided.

■ SmartLink was not able to acquire the Backup Exec job information fromBackup Exec.

SmartLink is unable to connect to theBackup Exec server. (Server:<servername> User: <username>Pwd: xxxx ... Error:<errorcode>Errors

The server may be down or a network issue may prevent SmartLink fromcontacting the CMS. No CPS Backup data validation is possible.

SmartLink is unable to contact theContinuous Management Server. Theserver may be down or a networkissue may be preventing SmartLinkfrom contacting the ContinuousManagement Server. No backup datavalidation on Protection Server ispossible.

The server may be down or a network issue may prevent SmartLink fromcontacting the CMS. No CPS Backup data validation is possible.

SmartLink is unable to contact theContinuous Management Server.

Command Line Syntax Error topic boxIf a syntax error was identified in the command line, the message was posted inthe Job Operation - Continuous Protection topic box. The Command Line SyntaxError topic box is provided. This topic box contains details of any syntax errorsthat are encountered in the SmartLink command line.


Exceptions topic boxIf any errors are associated with the CPS jobs or pairs, the message “SmartLinkCommand Line has error . . . .” appears in the Job Operation - Continuous Protection(Summary) topic box.

Additionally, the Exceptions topic box appears, which contains more detail aboutthe exceptions. If the job is a valid job, the CPS Job section is a warning box(orange). Any CPS Pair sections that have exceptions are also in a warning boxthat is nested in their respective CPS Job section.

Exceptions can be one of the following:

■ Pair did not meet goodness criteria.

■ Job name or ID was not found.

■ Unknown Job State.

■ Failure to connect to the Job Control Delegate (JCD) to retrieve log details

Table 9-5 provides more information about the exceptions.

Table 9-5 Exceptions

DescriptionException

The criteria that are evaluated to determine the consistency of ajob are the following:

■ Each pair must be in a consistent state.

■ Each pair must have been consistent since the last time theassociated Backup Exec job was run.

Goodness Criteria

This exception is given when one or more job names or IDs on theSmartLink command line cannot be found on the CMS.

Job Name or ID NotFound

An invalid job that is specified on the SmartLink command linethat does not exist in the CMS database.

Invalid CPS Job

The JCD of a job and the CMS may be unsynchronized. Thus, thereis no way for SmartLink to get an authoritative measure of thestate of the job or any of the pairs in the job. Thus, the job inquestion has an entry in the Exceptions error box but does nothave a “Continuous Protection Job” section.

Unknown Job State

Backup Exec SmartLink Options topic boxThe Backup Exec SmartLink Options topic box provides general information onthe CPS backup job such as the following:


140

■ Log Entry Limit

■ Show Latest Log Entry First

■ Issue Warning If Backup Data is Inconsistent

■ Backup Exec Job Name

■ Log File Name

Backup Exec SmartLink Run Log topic boxThe Run Log topic box is accessed when the -RunLog parameter is included in thecommand line.

This topic box provides detailed information on the CPS and backup jobs. Theinformation that is displayed in this topic box is generally only required byTechnical Support for troubleshooting purposes.

The topic box provides information such as the following:

■ Backup Exec information

■ Backup Exec Job information

■ Continuous Management Service information

■ CPS Job information

■ Continuous Protection Log information

CPS Jobs topic boxesEvery CPS job that is specified on the SmartLink command line has a topic boxthat is displayed in the job logs. This topic box contains all the information thatis related to that job. The title of the box is the name of the CPS job. This boxalways contains a header and a details box. If the job has exceptions, then the boxis orange (warning color). Subordinate topic boxes to the CPS jobs topic box areas follows.

Jobs that have exceptions are listed before any successful jobs.

Table 9-6 describes subordinate job topic boxes.

Table 9-6 Subordinate jobs topic boxes


Contains a summary of the job at the time SmartLink ran. It shows the job name, description,type, state, last started time, and last stopped time.

Job Header


Table 9-6 Subordinate jobs topic boxes (continued)


Contains job properties that define how the job was configured when the SmartLink commandline was started. The Job Details boxes contain most of the job properties that are found on theCPS Job Properties page.

Job Details

Contains CPS job log entries for the period starting when the Backup Exec job last ran, andending with the current run.

Log entries are presented based on the following:

■ The log entries are sorted in the same order as the Backup Exec log entries. They are sortedin descending order with the latest entries at the bottom of the log.

■ The date/time portions of CPS log entries are presented in the same format as the date/timefields in the rest of the Backup Exec log (12 versus 24-hour clock, UTC versus local time,international time format, and so forth.)

The number of entries is optionally configured with the -logLimit command line parameter.

Job Log

One Backup Pair box exists for each pair of the associated CPS job. The title of the box is thename of the actual CPS pair. If there is an exception associated with the pair, the box titlecontains the state of the pair along with a description of the exception condition.

Backup Pair

Contains a summary of the pair at the time SmartLink ran. It shows the source and destinationserver names, pair state, last started time, last stopped time, destination consistency, anddestination latency.

Destination latency can only be calculated when both servers in a pair are running ContinuousProtection Server version 10 or later.

Pair Header

Contains CPS pair log entries for the time period starting from when the owning Backup Execjob ran, and ending with the current run.

Log entries are presented based on the following:

■ The log entries are sorted in the same order as the Backup Exec log entries. They are sortedin descending order with the latest entries at the bottom of the log.

■ The date/time portions of our log entries is presented in the same format as the date/timefields in the rest of the Backup Exec log (12 versus 24 hour clock, UTC versus local time,international time format, and so forth.)

The number of entries is optionally configured with the -logLimit command line parameter.

Pair Log


142

TroubleshootingContinuous ProtectionServer


■ Troubleshooting Continuous Protection Server

■ Installation and upgrade issues

■ Component issues

■ Configuration issues

■ General issues

■ Backup and restore job issues

■ Backup Exec Retrieve issues

■ Database maintenance utilities

Troubleshooting Continuous Protection ServerUse the troubleshooting information to find solutions to problems that mightoccur in using the product.

For additional troubleshooting information, see the Readme.txt file on the productCD or go to the Symantec Website.

10Chapter

Installation and upgrade issuesTable 10-1 describes CPS installation issues.

Table 10-1 CPS installation issues

DescriptionIssue

Symantec does not recommend or support mixing the servers hosting the ContinuousManagement Service and Continuous Protection Agent between workgroups and domains.

Workgroups anddomains

Before you install CPS, you should disable any anti-spyware software. If you are promptedfor permission to install CPS, click Yes. This is particularly relevant for computers wherethe Continuous Protection Agent was push installed, and their users tend to select theBlock option since they may not know what is being installed and may think it is spywarefrom the Internet.

Anti-spyware software

If the Web Restore Server Component is installed during the installation of the CMS, amodified version of Apache Tomcat Web Server 5.5.7 is also installed. All Web serversare common targets for malicious attacks. Thus, in the event that any future issues arisewith this product, contact Symantec Technical Support for corrective information.

Apache Tomcat WebServer

If a cross-domain trust exists between the computers that you are installing from and to,the account that is running from the installing computer must be present in the local“administrators” group of the computer being push installed to.

Push installing overdomain trust

If a NIC card fails after installing CPS, the registry key for the new NIC card must beupdated for CPS to work properly.

NIC failure afterinstalling CPS

CPS fails to start if CPS has been installed in a directory whose pathname includescharacters from Asian languages, including Japanese, Chinese, and Korean. To avoid thisproblem, either install CPS in the default installation directory or choose a directorywhose pathname, netgroup name and master server name only includes English characters(a-z, A-Z, 0-9).

Pathnames with Asiancharacters

After installing Continuous Protection Server on a computer running Windows Server2003, you might receive an error message that the Network Load Balancing Service failedto start. Microsoft reports the cause as: “Although network Load Balancing (NLB) is notcurrently installed, some NLB registry keys might be present in the registry.” AlthoughMicrosoft Knowledge Base Article 268437 describes the problem as applying to Windows2000 Advanced Server, the fix also works for Windows Server 2003.

For more information about network load balancing on Windows Server 2003, go to thefollowing URL:

www.microsoft.com/technet/prodtechnol/windows2000serv/support/nlbcontb.mspx

Network load balancingservice fails to start

Table 10-2 describes a CPS uninstall issue.

Troubleshooting Continuous Protection ServerInstallation and upgrade issues

144

Table 10-2 CPS uninstall issue

DescriptionIssue

If CPS is uninstalled and reinstalled, information in the job logsand pair logs is not saved.

For more information about this issue, go to the following URL:


Uninstall and reinstallloses job history and pairlogs

Component issuesTable 10-3 describes CPS administration console issues.

Table 10-3 Administration Console issues

DescriptionIssue

The first time that you select a server to do a CPS restore, a waitcursor appears and it may take several minutes before anythingis displayed. Nothing in the console indicates that anything ishappening and a user might think that nothing can be restored.This delay is caused by the mounting of the snapshots asvolumes. The amount of time it takes to mount a snapshot isproportional to the size of the snapshot.

Administration Consolemay run slowly whenfirst run

Consoles running on computers without the correspondinglanguage pack that is installed is not able to properly interpretthe job name or description. For example, when a job name iscreated with Japanese characters, these characters show asmeaningless square boxes when the job is viewed on an EnglishConsole. Be sure that the language packs are installed for alllanguages of job names and descriptions that may be used inthe Console.

Job name and descriptionare in a differentlanguage than theAdministration Console

Table 10-4 describes a Business Server issue.

145Troubleshooting Continuous Protection ServerComponent issues

Table 10-4 Business Server issues

DescriptionIssue

If a Business Server is deleted from the Backup Group, all restoreselections also disappear. If the deleted Business Server isbrought back into the Backup Group or another server is addedwith the same name as the deleted server, a new CPS backupjob of at least one file can be created and run to resynchronizethe restore selections. This situation requires reinstalling theContinuous Protection Agent and restarting thereplaced/restored server.

Recovering restoreselections to a restoredor replaced BusinessServer

Configuration issuesTable 10-5 describes snapshot and indexing issues.

Table 10-5 Snapshot and indexing issues

DescriptionIssue

To troubleshoot indexing of snapshots

1 Click Run > Control Panel > Administrative Tools >Services.

2 Verify that the Backup Exec Continuous ProtectionIndexing Component is running (started).

3 Stop and restart the Indexing Component to start areindexing of any snapshots that are not indexed.

4 Check the logs for any erroneous entries.

5 Contact Symantec Technical Support.

Snapshots fail to indexproperly

Troubleshooting Continuous Protection ServerConfiguration issues

146

Table 10-5 Snapshot and indexing issues (continued)

DescriptionIssue

The ability to search for files is accomplished by a built-inindexing service. The indexing database requires 1 GB of freedisk space on the destination to search for files to restore or todisplay a list of recent activity. The number of files with whichyou work can vary widely. Without enough free disk space tohandle the number of files, the search is not performed and thelist of files that are found, or the list of recent activity, appearsempty.

If your destination servers do not have 1 GB of free disk space,the amount of space CPS looks for can be minimized. You canadjust the amount of free disk space that CPS looks for by addingthe following line to the [SERVER] section of theAutonomy\suir.cfg file in the product installation folder.

MinFreeSpaceMB=XX

Where XX is the number of free megabytes that are required onthe server to start the indexing service.

Adjusting the free diskspace for indexing

General issuesTable 10-6 describes processing efficiency issues.

Table 10-6 Processing efficiency issues

DescriptionIssue

Bandwidth throttling can be implemented using Quality ofService (QOS) with network switches and routers. QOS shouldbe implemented on TCP/IP port 20481.

Bandwidth throttlingand Quality of Service(QOS)

147Troubleshooting Continuous Protection ServerGeneral issues

Table 10-6 Processing efficiency issues (continued)

DescriptionIssue

A chronic “nearly out of memory” condition may exist duringperiods of intensive input/output processing.

To determine the state of the system

1 Start the Windows Task Manager.

2 Select the Performance tab.

3 Look at the Physical Memory (K) control group.

4 Verify the amount of available memory to see if the amountdrops to 4000 or less (that is, 4 MB) and tends to stay there.

In this state, the system is unresponsive to user input and shouldbe corrected.



System may run out ofmemory during intensiveinput/output processing

An input/output deadlock can occur for the following reasons:

■ CPS is used to continuously back up large databases.

■ The input/output activity on these database files is high.

■ The host server has fewer than 4 logical CPUs (that is, 4physical CPUs without hyperthreading, or 2 CPUs withhyperthreading).



File system input/outputdeadlocks may occurwhen continuouslybacking up largedatabase files

Table 10-7 describes miscellaneous issues.

Table 10-7 Miscellaneous issues

DescriptionIssue

CPS does not recognize utility partitions.Utility partitions

If the Windows SNMP service is installed on the computer whenCPS was installed, CPS's SNMP support is automaticallyinstalled.

For more information how to turn off SNMP support in CPS, goto the following URL:


Disabling CPS SNMPsupport

Troubleshooting Continuous Protection ServerGeneral issues

148

Table 10-7 Miscellaneous issues (continued)

DescriptionIssue

CPS throttles the data transmission for all pairs at theleast-restrictive rate. For example, if a backup job is configuredto run between two nodes with the bandwidth limited to 20%of a T1 line and another job is configured to run between thesame two computers with bandwidth limited to 50% of a T1 line,the throughput of both jobs will be combined and run at a rateof 50% of the T1 line. That is, each job will not run at the 50%rate, but rather both jobs combined.

Multiple pairs areconfigured to runbetween the same twocomputers

If the free space of a CPS database volume is exhausted, theSybase Adaptive Server Anywhere 9 server may assert andrefuse all new connections until the CPS services on thatcomputer are restarted.

The free space on a CPSdatabase volume isexhausted

Database backup and restore capabilities are based on VolumeShadow Copy Service (VSS) Writer Technology. The followingutilities can be used in lieu of using Backup Exec with VSScapabilities for configuration database backups, or if the userwants to perform manual backups and verification.

Use cpsDBBackup to create a validated backup image of the CMSor CPA database.

Use cpsDBValidate to validate and repair the CMS or CPAdatabase. Only corrupt indexes can be repaired. Restore is amanual procedure.

For more information about the CPS database maintenanceutilities, go to the following URL:


CPS database backup andrestore

Backup and restore job issuesTable 10-8 describes a CPS backup job issue.

149Troubleshooting Continuous Protection ServerBackup and restore job issues

Table 10-8 CPS backup issues

DescriptionIssue

If the backup job is configured to use the schedule optionWhenever a file changes, it means the “continue backup aftersynchronization” is turned on. In this configuration, the job canbecome stalled in the running or expiring state if a connectionoutage occurs under certain rare conditions.

In addition, the pair state (available in the Job Monitor view)remains in the completing state. The outage has to occur duringthe interval between when a source of the job finishes sendingall synchronization data and a destination of the job finishesreplaying all synchronization data. To resolve this situation,manually cancel the job.

Connection outages

Table 10-9 describes a CPS restore job issue.

Table 10-9 CPS restore job issues

DescriptionIssue

CPS does not allow protected files on a Protection Server to berestored to a different location on the Protection Server. Tomove files to different locations on the Protection Server, usethe copy and paste features of Windows Explorer.

CPS does not allow fileson a Protection Serversto be restored to adifferent location on theProtection Server

Backup Exec Retrieve issuesTable 10-10 describes Backup Exec Retrieve issues.

Table 10-10 Backup Exec Retrieve issues

DescriptionIssue

CPS does not need to store the credentials to connect to Backup Exec. However, the CPAon the DLO file servers and the CMS must all run as an account that is a member of theAdministrators group on Backup Exec. No additional software is needed on the BackupExec server.

Backup Exec Desktopand Laptop Option

Backup Exec Retrieve does not work if the Business Servers, Protection Servers, and CMSare not located in the same (or trusted) domains. However, the client (Web browser)computers do not need to be in the same (or any) domain.

Trusted domains

Troubleshooting Continuous Protection ServerBackup Exec Retrieve issues

150

Table 10-10 Backup Exec Retrieve issues (continued)

DescriptionIssue

Set up accounts with the same user name and password on the source, destination, andthe Web Restore Server Component. Log on to the Web retrieval site, and select the localcomputer as the domain.

Files on the source that use customized permissions are not accessible through BackupExec Retrieve. Users can view and download files accessible to everyone.

Non-domainenvironments

When searching for files to restore, if the window of the search (From date to To date)are the same, no files are listed. The from and to dates in the search window should bedifferent by at least one day.

Same-date searches

If you restore a file using Backup Exec Retrieve that has multi-byte characters, you mayfind that the filename of the downloaded file does not match the original file name. Thisoccurs if the Web browser computer is not running in the same language as the file youare trying to download (that is, downloading a file with Japanese characters to an Englishcomputer). This behavior is exhibited for both the single-file download using InternetExplorer and the multi-file download using the Download Manager.

Multi-byte filenames

When browsing folders in Backup Exec Retrieve, you may encounter folders that haveno contents.

Folders may appear empty for the following reasons:

■ The user does not have access to this folder.

■ The backup destination that protects this folder is offline.

■ The folder is actually empty.

Folders without contents

The source does not have any accessible shares. Start sharing the folder on the source,and then refresh Backup Exec Retrieve.

No files are listed for ashown source computer

Permissions should be configured on the share, and then each destination should bebacked up. CPS applies the most recent permissions to shared folders. If confidentialinformation is accidentally shared, correct the permissions on the share, and then backup the files again.

Protecting confidentialfiles from being viewedor downloaded by otherusers

The results pane displays shared folders to which users have Read permissions or higher,and which were backed up from the selected source. Administrator shares do not displayin Backup Exec Retrieve, which is intended for user access.

The files that appear in Backup Exec Retrieve results pane originate from snapshots ofthe backup destination. For example, if a file is saved three times in an hour, and snapshotsare scheduled to take place every two hours, the saved files appear after the snapshot ofthe backup destination is taken.

Search results pane isblank

151Troubleshooting Continuous Protection ServerBackup Exec Retrieve issues

Table 10-10 Backup Exec Retrieve issues (continued)

DescriptionIssue

On some computers, opening a file directly from Web Retrieval Interface results in a FileNot Found error from the application that was launched to view the file. This conditionresults when the option Do not save encrypted pages to disk is enabled in Internet Explorer.If this option is enabled, the file is never saved to the disk, so the application is unableto open it.

To disable Do not save encrypted pages to disk in Internet Explorer

1 On the Internet Explorer Tools menu, click Internet Options.

2 Click the Advanced tab.

3 Under Security, verify that the Do not save encrypted pages to disk check box isdeselected.

4 Alternatively, when prompted by the browser to open or save the file, click Save,and then open the file from the saved location.

File Not Found Errors

The default Backup Exec Retrieve URL (https://server:8443/BERetrieve) can be modifiedto a simpler form, such as http://server.

When open up your browser to http://server, you will automatically be redirected to theBackup Exec Retrieve login page.

To edit the default Backup Exec Retrieve address

1 Make sure you are not running another Web server on port 80, such as IIS, Apache,and so forth. If you are, then you will need to disable that Web server.

2 Open a command prompt, and browse to C:\Program Files\Symantec\ContinuousProtection Server\VRTSweb\bin.

3 Run the command webgui addport 80 HTTP

4 From a command prompt, browse to C:\Program Files\Symantec\ContinuousProtection Server\VRTSweb\admin\root5\ROOT5.

5 Open index.html in a plain text editor such as Microsoft Notepad.

6 Change URL=Home.do to URL=/BERetrieve

7 Save the file.

Modifying the BackupExec Retrieve URL

Database maintenance utilitiesCPS includes several powerful utilities for assessing, backing up, restoring, andrepairing the CPS databases.

These utilities include the following:

Troubleshooting Continuous Protection ServerDatabase maintenance utilities

152

■ CPS Database Backup and Restore

■ CPS Database Validation and Repair

Any procedures that are associated with CPS database maintenance utilities maybe superseded by the Backup Exec backup and restore jobs. However, if theContinuous Management Service (CMS) is operating on a server using Windows2000 (without the Shadow Copy components), these procedures apply.

See “Protecting CPS with Backup Exec” on page 126.

The Database Maintenance utilities are run from the CPS utilities command lineprompt.

To start the CPS utilities

◆ On the Windows taskbar, click Start >All Programs > Symantec > BackupExec CPS > CPSUtilities.

This para is intentionally added.

CPS database backup and restoreAll CPS job configurations are stored in the CMS database. Any loss or corruptionof this information without a backup will require the user to recreate every lostjob. Thus, it is highly recommended that the CMS database be periodically backedup for data protection and data redundancy.

Likewise, historical information is logged into a database at every ContinuousProtection Agent (CPA). While backing up these databases is not necessary, someusers may wish to maintain CPA database backups to protect this information.

Either way, loss of the CMS or a CPA database will require replacing the database,either from a backup image or via a repair install. In the latter case, the databasewill be empty and all job configuration (CMS) and historical information (CPA)will be lost.

For more information about the CPS database maintenance utilities, go to thefollowing URL:


CPS database validation and repairThe cpsDBValidate utility validates and optionally repairs or rebuilds a CMS orCPA database. However this tool requires exclusive access to the database andthus will restart the CMS or CPA services.

For more information about the CPS database maintenance utilities, go to thefollowing URL:

153Troubleshooting Continuous Protection ServerDatabase maintenance utilities


Resetting the standard logonIt is possible to convert the CMS or CPA servers in an existing CPS installation touse integrated logons.

When running in integrated logon mode the CMS and CPA servers no longerprovide database credentials when connecting to their respective databases. Thisis because access has been granted to the account under whose context the servicesare running. This provides an added level of security to your installation.

Integrated logons cannot be enabled on systems that were installed in non-securemode. The CMS or CPA service's log on or run as account must be set to a domainaccount and not the local system or a local system account.

All CMS and CPA servers may have integrated logons enabled by running theSetIntegratedLogin utility. This must be done for each server, and one server ata time. If integrated logons is enabled on a combined CMS/CPA server, it is enabledfor both services at the same time. Enabling integrated logons requires restartingthe affected CPS services.

After integrated logons have been enabled, it is possible to reset standard logons,again using the SetIntegratedLogin utility. This results in a server running in thesame configuration as it was after installation. This is required if the “log on”account name is changed for any CMS or CPA service for whom integrated logonshas been enabled.

The SetIntegratedLogin utility is run from the CPS Utilities command line prompt.

Note: It is necessary to run SetIntegratedLogin only if the services run as accountname is changed, not the run as password.

To reset the standard logon:

1 Run SetIntegratedLogin to reset the standard logons.

2 Change the services in question to the run-as account name.

3 Run SetIntegratedLogin to re-enable integrated logons.

Issues with integrated logon and database backupsAttempts to restore a CMS or CPA database from a backup image that was createdbefore integrated logon was enabled will cause the service in question to fail tostart. This is because the just restored image was never configured for integratedlogons and the current ODBC Data Source is currently configured for integrated


154

logons. To overcome this issue, you will need to reconfigure the ODBC Data Sourcefor standard logon.

To recover after restoring a pre-integrated logon database

1 Run the ODBC Data Source Administrator (odbcad32).

2 Click the SystemDSN tab.

3 Select the CPA DSN, and then click Configure.

4 Click the Login tab.

5 Select Supply user ID and password, and then click OK.

6 Repeat steps 1-5, but this time for the CMS DSN, if there is one.

7 Exit the ODBC Data Source Administrator.

The CMS and/or CPS services can now run.

You must now reconfigure the services for integrated logon.

8 Run the SetIntegratedLogin utility to re-enable integrated logons. For example,SetIntegratedLogin Watchword.

The services will now run in integrated logon mode.

Restoring a combined CMS/CPA serverThe login configurations of a combined CMS/CPA server must be kept insynchronization. That is, both must be configured for integrated login or neithermust be so configured. This creates a problem with restoring old databases thatare backup images taken before the server was reconfigured to use integratedlogin.

See “Database maintenance utilities” on page 152.

To restore a combined CMS/CPA server

1 Restore the CMS database from a pre-integrated login backup image. TheCMS server does not start.

2 Edit the ODBC CMS DSN to use standard logins.

See “Issues with integrated logon and database backups” on page 154.

The CMS service can start.

155Troubleshooting Continuous Protection ServerDatabase maintenance utilities

3 SetIntegratedLogin determines that the CMS and the CPA differ and returnsan error.


Currently the only way to overcome this error is to restore both the CMS andCPA databases from the same backup image set. That is, both databases mustbe backed up at the same time, and the backup images should be kept andrestored together as a set.

4 Restore the CMS and CPA databases from a pre integrated login backup imageset.

Neither service will start.

5 Modify the ODBC DSN for the CMS and the CPA to use standard logins.


The services can start.

6 SetIntegratedLogin (step 2) succeeds and the CMS and the CPA services willnow run in integrated login mode.


156

Third-Party Legal Notices

This appendix includes the following topics:

■ About Third-Party Legal Notices

■ ACE and TAO are governed under the same license provided below.

■ ACE (The Adaptive Communication Environment)

■ TAO

■ Apache Struts, Xerces C++ and Tomcat are governed under the same licenseprovided below

■ Apache Struts

■ Xerces C++

■ Tomcat

■ Blowfish Encryption

■ Curl/LibCurl

■ Digital Encryption Standard (DES) - MIT

■ ICU

■ MD5

■ Open SSL

■ ReportCtrl.h.2.0.1

■ STLport

■ Java 2 Runtime Environment

AAppendix

About Third-Party Legal NoticesCertain third-party software may be distributed, embedded, or bundled with theSymantec product or recommended for use in conjunction with the installationand operation of this Symantec product. Such third-party software is separatelylicensed by its copyright holder. Use of the third-party software must be inaccordance with its license terms. This appendix contains the licenses whichgovern the use of third-party software and its copyright holder's proprietarynotices. Symantec makes no representation or warranty of any kind regardingsuch third-party software. Symantec offers no support for such third-partysoftware and shall have no liability associated with its use.

ACE and TAO are governed under the same licenseprovided below.


ACE (The Adaptive Communication Environment)Douglas C. Schmidt and his research group at Washington University andUniversity of California, Irvine and Vanderbuilt Univerity.

ACE(TM) is copyrighted by Douglas C. Schmidt and his research group atWashington University, University of California, Irvine, and Vanderbilt UniversityCopyright (c) 1993-2003, all rights reserved.

TAODouglas C. Schmidt and his research group at Washington University andUniversity of California, Irvine and Vanderbuilt Univerity.

TAO(TM) is copyrighted by Douglas C. Schmidt and his research group atWashington University, University of California, Irvine, and Vanderbilt UniversityCopyright (c) 1993-2003, all rights reserved.

Copyright and Licensing Information for ACE(TM), TAO(TM), CIAO(TM), andCoSMIC(TM):

ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM) (henceforth referred to as "DOCsoftware") are copyrighted by Douglas C. Schmidt and his research group atWashington University, University of California, Irvine, and Vanderbilt University,Copyright (c) 1993-2004, all rights reserved. Since DOC software is open-source,free software, you are free to use, modify, copy, and distribute--perpetually and

Third-Party Legal NoticesAbout Third-Party Legal Notices

158

irrevocably--the DOC software source code and object code produced from thesource, as well as copy and distribute modified versions of this software.

You must, however, include this copyright statement along with code built usingDOC software. You can use DOC software in proprietary software and are underno obligation to redistribute any of your source code that is built using DOCsoftware. Note, however, that you may not do anything to the DOC software code,such as copyrighting it yourself or claiming authorship of the DOC software code,that will prevent DOC software from being distributed freely using an open-sourcedevelopment model. You needn't inform anyone that you're using DOC softwarein your software, though we encourage you to let us know so we can promote yourproject in the DOC software success stories.

DOC software is provided as is with no warranties of any kind, including thewarranties of design, merchantability, and fitness for a particular purpose,noninfringement, or arising from a course of dealing, usage or trade practice.Moreover, DOC software is provided with no support and without any obligationon the part of Washington University, UC Irvine, Vanderbilt University, theiremployees, or students to assist in its use, correction, modification, orenhancement. A number of companies around the world provide commercialsupport for DOC software, however. DOC software is Y2K-compliant, as long asthe underlying OS platform is Y2K-compliant.

Washington University, UC Irvine, Vanderbilt University, their employees, andstudents shall have no liability with respect to the infringement of copyrights,trade secrets or any patents by DOC software or any part thereof. Moreover, inno event will Washington University, UC Irvine, or Vanderbilt University, theiremployees, or students be liable for any lost revenue or profits or other special,indirect and consequential damages.

The ACE, TAO, CIAO, and CoSMIC web sites are maintained by the DOC Group atthe Institute for Software Integrated Systems (ISIS) and the Center for DistributedObject Computing of Washington University, St. Louis for the development ofopen-source software as part of the open-source software community. Bysubmitting comments, suggestions, code, code snippets, techniques (includingthat of usage), and algorithms, submitters acknowledge that they have the rightto do so, that any such submissions are given freely and unreservedly, and thatthey waive any claims to copyright or ownership. In addition, submittersacknowledge that any such submission might become part of the copyrightmaintained on the overall body of code, which comprises the DOC software. Bymaking a submission, submitter agree to these terms. Furthermore, submittersacknowledge that the incorporation or modification of such submissions is entirelyat the discretion of the moderators of the open-source DOC software projects ortheir designees.

159Third-Party Legal NoticesTAO

The names ACE(TM), TAO(TM), CIAO(TM), CoSMIC(TM), Washington University,UC Irvine, and Vanderbilt University, may not be used to endorse or promoteproducts or services derived from this source without express written permissionfrom Washington University, UC Irvine, or Vanderbilt University. Further,products or services derived from this source may not be called ACE(TM), TAO(TM),CIAO(TM), or CoSMIC(TM) nor may the name Washington University, UC Irvine,or Vanderbilt University appear in their names, without express written permissionfrom Washington University, UC Irvine, and Vanderbilt University.

If you have any suggestions, additions, comments, or questions, please let meknow.

Douglas C. Schmidt

Apache Struts, Xerces C++ and Tomcat are governedunder the same license provided below


Apache StrutsThis para is intentionally added.

Xerces C++This para is intentionally added.

TomcatApache Software Foundation

Portions of this program contain components from the Apache SoftwareFoundation. These components are made available under the Apache License 2.0,a copy of which is provided below.

License:

Apache License, Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

Third-Party Legal NoticesApache Struts, Xerces C++ and Tomcat are governed under the same license provided below

160

Definitions.“License” shall mean the terms and conditions for use, reproduction, anddistribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyrightowner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities thatcontrol, are controlled by, or are under common control with that entity. For thepurposes of this definition, “control” means (i) the power, direct or indirect, tocause the direction or management of such entity, whether by contract orotherwise, or (ii) ownership of fifty percent (50%) or more of the outstandingshares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissionsgranted by this License.

“Source” form shall mean the preferred form for making modifications, includingbut not limited to software source code, documentation source, and configurationfiles.

“Object” form shall mean any form resulting from mechanical transformation ortranslation of a Source form, including but not limited to compiled object code,generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form,made available under the License, as indicated by a copyright notice that is includedin or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, thatis based on (or derived from) the Work and for which the editorial revisions,annotations, elaborations, or other modifications represent, as a whole, an originalwork of authorship. For the purposes of this License, Derivative Works shall notinclude works that remain separable from, or merely link (or bind by name) to theinterfaces of, the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original versionof the Work and any modifications or additions to that Work or Derivative Worksthereof, that is intentionally submitted to Licensor for inclusion in the Work bythe copyright owner or by an individual or Legal Entity authorized to submit onbehalf of the copyright owner. For the purposes of this definition, "submitted"means any form of electronic, verbal, or written communication sent to theLicensor or its representatives, including but not limited to communication onelectronic mailing lists, source code control systems, and issue tracking systemsthat are managed by, or on behalf of, the Licensor for the purpose of discussingand improving the Work, but excluding communication that is conspicuously

161Third-Party Legal NoticesTomcat

marked or otherwise designated in writing by the copyright owner as "Not aContribution."

“Contributor” shall mean Licensor and any individual or Legal Entity on behalfof whom a Contribution has been received by Licensor and subsequentlyincorporated within the Work.

Grant of Copyright License.Subject to the terms and conditions of this License, each Contributor hereby grantsto You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocablecopyright license to reproduce, prepare Derivative Works of, publicly display,publicly perform, sublicense, and distribute the Work and such Derivative Worksin Source or Object form.

Grant of Patent License.Subject to the terms and conditions of this License, each Contributor hereby grantsto You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable(except as stated in this section) patent license to make, have made, use, offer tosell, sell, import, and otherwise transfer the Work, where such license appliesonly to those patent claims licensable by such Contributor that are necessarilyinfringed by their Contribution(s) alone or by combination of their Contribution(s)with the Work to which such Contribution(s) was submitted. If You institute patentlitigation against any entity (including a cross-claim or counterclaim in a lawsuit)alleging that the Work or a Contribution incorporated within the Work constitutesdirect or contributory patent infringement, then any patent licenses granted toYou under this License for that Work shall terminate as of the date such litigationis filed.

Redistribution.You may reproduce and distribute copies of the Work or Derivative Works thereofin any medium, with or without modifications, and in Source or Object form,provided that You meet the following conditions:

■ You must give any other recipients of the Work or Derivative Works a copy ofthis License; and

■ You must cause any modified files to carry prominent notices stating that Youchanged the files; and

■ You must retain, in the Source form of any Derivative Works that Youdistribute, all copyright, patent, trademark, and attribution notices from the

Third-Party Legal NoticesTomcat

162

Source form of the Work, excluding those notices that do not pertain to anypart of the Derivative Works; and

■ If the Work includes a "NOTICE" text file as part of its distribution, then anyDerivative Works that You distribute must include a readable copy of theattribution notices contained within such NOTICE file, excluding those noticesthat do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of the DerivativeWorks; within the Source form or documentation, if provided along with theDerivative Works; or, within a display generated by the Derivative Works, ifand wherever such third-party notices normally appear. The contents of theNOTICE file are for informational purposes only and do not modify the License.

You may add Your own attribution notices within Derivative Works that Youdistribute, alongside or as an addendum to the NOTICE text from the Work,provided that such additional attribution notices cannot be construed as modifyingthe License. You may add Your own copyright statement to Your modificationsand may provide additional or different license terms and conditions for use,reproduction, or distribution of Your modifications, or for any such DerivativeWorks as a whole, provided Your use, reproduction, and distribution of the Workotherwise complies with the conditions stated in this License.

Submission of Contributions.Unless You explicitly state otherwise, any Contribution intentionally submittedfor inclusion in the Work by You to the Licensor shall be under the terms andconditions of this License, without any additional terms or conditions.Notwithstanding the above, nothing herein shall supersede or modify the termsof any separate license agreement you may have executed with Licensor regardingsuch Contributions.

Trademarks.This License does not grant permission to use the trade names, trademarks, servicemarks, or product names of the Licensor, except as required for reasonable andcustomary use in describing the origin of the Work and reproducing the contentof the NOTICE file.

Disclaimer of Warranty.Unless required by applicable law or agreed to in writing, Licensor provides theWork (and each Contributor provides its Contributions) on an “AS IS” BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express orimplied, including, without limitation, any warranties or conditions of TITLE,

163Third-Party Legal NoticesTomcat

NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULARPURPOSE. You are solely responsible for determining the appropriateness ofusing or redistributing the Work and assume any risks associated with Yourexercise of permissions under this License.

Limitation of LiabilityIn no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberate andgrossly negligent acts) or agreed to in writing, shall any Contributor be liable toYou for damages, including any direct, indirect, special, incidental, or consequentialdamages of any character arising as a result of this License or out of the use orinability to use the Work (including but not limited to damages for loss of goodwill,work stoppage, computer failure or malfunction, or any and all other commercialdamages or losses), even if such Contributor has been advised of the possibilityof such damages.

Accepting Warranty or Additional Liability.While redistributing the Work or Derivative Works thereof, You may choose tooffer, and charge a fee for, acceptance of support, warranty, indemnity, or otherliability obligations and/or rights consistent with this License. However, inaccepting such obligations, You may act only on Your own behalf and on Yoursole responsibility, not on behalf of any other Contributor, and only if You agreeto indemnify, defend, and hold each Contributor harmless for any liability incurredby, or claims asserted against, such Contributor by reason of your accepting anysuch warranty or additional liability.

END OF TERMS AND CONDITIONS

Blowfish EncryptionBruce Schneier

Copyright 2003 by George Anescu

The code in this project is Copyright 2003 by George Anescu. You have the rightto use and distribute the code in any way you see fit as long as this paragraph isincluded with the distribution. No warranties or claims are made as to the validityof the information and [Blowfish] code contained herein, so use it at your ownrisk.

Third-Party Legal NoticesBlowfish Encryption

164

Curl/LibCurlDaniel Stenberg

Copyright (c) 1996 - 2004, Daniel Stenberg, <[email protected]>.

All rights reserved.

Permission to use, copy, modify, and distribute this software for any purpose withor without fee is hereby granted, provided that the above copyright notice andthis permission notice appear in all copies.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGESOR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OROTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not beused in advertising or otherwise to promote the sale, use or other dealings in thisSoftware without prior written authorization of the copyright holder.

Digital Encryption Standard (DES) - MITMIT and Dennis Ferguson

Copyright (c) 1990 Dennis Ferguson. All rights reserved.

Commercial use is permitted only if products which are derived from or includethis software are made available for purchase and/or use in Canada. Otherwise,redistribution and use in source and binary forms are permitted.

Copyright 1985, 1986, 1987, 1988, 1990 by the Massachusetts Institute ofTechnology. All Rights Reserved.

Export of this software from the United States of America may require a specificlicense from the United States Government. It is the responsibility of any personor organization contemplating export to obtain such a license before exporting.

WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distributethis software and its documentation for any purpose and without fee is herebygranted, provided that the above copyright notice appear in all copies and thatboth that copyright notice and this permission notice appear in supportingdocumentation, and that the name of M.I.T. not be used in advertising or publicitypertaining to distribution of the software without specific, written prior

165Third-Party Legal NoticesCurl/LibCurl

permission. M.I.T. makes no representations about the suitability of this softwarefor any purpose. It is provided “as is” without express or implied warranty.

ICUInternational Business Machines Corporation

Copyright (c) 1995-2003 International Business Machines Corporation and others.All rights reserved.

ICU License - ICU 1.8.1 and later

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2003 International Business Machines Corporation and others.All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy ofthis software and associated documentation files (the “Software”), to deal in theSoftware without restriction, including without limitation the rights to use, copy,modify, merge, publish, distribute, and/or sell copies of the Software, and to permitpersons to whom the Software is furnished to do so, provided that the abovecopyright notice(s) and this permission notice appear in all copies of the Softwareand that both the above copyright notice(s) and this permission notice appear insupporting documentation.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIESOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THECOPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FORANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, ORANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA ORPROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHERTORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE ORPERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not beused in advertising or otherwise to promote the sale, use or other dealings in thisSoftware without prior written authorization of the copyright holder.

All trademarks and registered trademarks mentioned herein are the property oftheir respective owners.

MD5RSA Data Security, Inc.

Third-Party Legal NoticesICU

166

Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.

Ronald L. Rivest

Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.

License to copy and use this software is granted provided that it is identified asthe “RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all materialmentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such worksare identified as “derived” from the RSA Data Security, Inc.

“MD5 Message-Digest Algorithm” in all material mentioning or referencing thederived work.

RSA Data Security, Inc. makes no representations concerning either themerchantability of this software or the suitability of this software for anyparticular purpose. It is provided “as is” without express or implied warranty ofany kind.

These notices must be retained in any copies of any part of this documentationand/or software.

Open SSLThe OpenSSL Project

Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

LICENSE ISSUES:

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of theOpenSSL License and the original SSLeay license apply to the toolkit. See belowfor the actual license texts. Actually both licenses are BSD-style Open Sourcelicenses. In case of any license issues related to OpenSSL please [email protected].

OpenSSL License

Copyright (c) 1998-2003 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

■ Redistributions of source code must retain the above copyright notice, thislist of conditions and the following disclaimer.

■ Redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

167Third-Party Legal NoticesOpen SSL

■ All advertising materials mentioning features or use of this software mustdisplay the following acknowledgment:

■ “This product includes software developed by the OpenSSL Project for use inthe OpenSSL Toolkit. (http://www.openssl.org/)”

■ The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used toendorse or promote products derived from this software without prior writtenpermission. For written permission, please contact [email protected].

■ Products derived from this software may not be called “OpenSSL” nor may“OpenSSL” appear in their names without prior written permission of theOpenSSL Project.

■ Redistributions of any form whatsoever must retain the followingacknowledgment:

■ “This product includes software developed by the OpenSSL Project for use inthe OpenSSL Toolkit (http://www.openssl.org/)”

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODSOR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young([email protected]). This product includes software written by Tim Hudson([email protected]).

Original SSLeay LicenseCopyright (C) 1995-1998 Eric Young ([email protected]). All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]).

The implementation was written so as to conform with Netscape’s SSL.

This library is free for commercial and non-commercial use as long as the followingconditions are adhered to. The following conditions apply to all code found in thisdistribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The

Third-Party Legal NoticesOpen SSL

168

SSL documentation included with this distribution is covered by the same copyrightterms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the codeare not to be removed.

If this package is used in a product, Eric Young should be given attribution as theauthor of the parts of the library used. This can be in the form of a textual messageat program startup or in documentation (online or textual) provided with thepackage.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

■ Redistributions of source code must retain the copyright notice, this list ofconditions and the following disclaimer.

■ Redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

■ All advertising materials mentioning features or use of this software mustdisplay the following acknowledgement:

■ "This product includes cryptographic software written by Eric Young([email protected])"

■ The word 'cryptographic' can be left out if the routines from the library beingused are not cryptographic related :-).

■ If you include any Windows specific code (or a derivative thereof) from theapps directory (application code) you must include an acknowledgement:

■ "This product includes software written by Tim Hudson([email protected])"

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

169Third-Party Legal NoticesOpen SSL

The licence and distribution terms for any publically available version or derivativeof this code cannot be changed. i.e. this code cannot simply be copied and putunder another distribution licence [including the GNU Public Licence.]

ReportCtrl.h.2.0.1Maarten Hoeben

Copyright Maarten Hoeben

Author: Maarten Hoeben

E-mail: [email protected]

Implementation of the CReportCtrl and associated classes.

This code may be used in compiled form in any way you desire. This file may beredistributed unmodified by any means PROVIDING it is not sold for profit withoutthe authors written consent, and providing that this notice and the authors nameand all copyright notices remains intact.

An email letting me know how you are using it would be nice as well.

This file is provided "as is" with no expressed or implied warranty.

The author accepts no liability for any damage/loss of business that this productmay cause.

STLportBoris Fomitchev

Copyright 1999,2000 Boris Fomitchev

Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-freelicense to use STLport and its documentation without fee.

By downloading, using, or copying STLport or any portion thereof, Licensee agreesto abide by the intellectual property laws and all other applicable laws of theUnited States of America, and to all of the terms and conditions of this Agreement.

Licensee shall maintain the following copyright and permission notices on STLportsources and its documentation unchanged :

Copyright 1999,2000 Boris Fomitchev

This material is provided "as is", with absolutely no warranty expressed or implied.Any use is at your own risk.

Permission to use or copy this software for any purpose is hereby granted withoutfee, provided the above notices are retained on all copies. Permission to modify

Third-Party Legal NoticesReportCtrl.h.2.0.1

170

the code and to distribute modified code is granted, provided the above noticesare retained, and a notice that the code was modified is included with the abovecopyright notice.

The Licensee may distribute binaries compiled with STLport (whether original ormodified) without any royalties or restrictions.

The Licensee may distribute original or modified STLport sources, provided that:

■ The conditions indicated in the above permission notice are met;

■ The following copyright notices are retained when present, and conditionsprovided in accompanying permission notices are me :

■ Copyright 1994 Hewlett-Packard Company

■ Copyright 1996,97 Silicon Graphics Computer Systems, Inc.

■ Copyright 1997 Moscow Center for SPARC Technology.

Permission to use, copy, modify, distribute and sell this software and itsdocumentation for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright noticeand this permission notice appear in supporting documentation. Hewlett-PackardCompany makes no representations about the suitability of this software for anypurpose. It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and itsdocumentation for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright noticeand this permission notice appear in supporting documentation. Silicon Graphicsmakes no representations about the suitability of this software for any purpose.It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and itsdocumentation for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright noticeand this permission notice appear in supporting documentation. Moscow Centerfor SPARC Technology makes no representations about the suitability of thissoftware for any purpose. It is provided "as is" without express or implied warranty.

Java 2 Runtime EnvironmentSun Microsystems, Inc.

© 2005 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc.

171Third-Party Legal NoticesJava 2 Runtime Environment

Binary Code License Agreement for the JAVA(TM) 2 RUNTIME ENVIRONMENT(J2RE), STANDARD EDITION, VERSION 1.4.2_X

SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWAREIDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPTALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENTAND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASEREAD THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THISSOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT.

INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THEBOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BYALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THEAGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOTCONTINUE.

DEFINITIONS."Software" means the identified above in binary form, any other machine readablematerials (including, but not limited to, libraries, source files, header files, anddata files), any updates or error corrections provided by Sun, and any user manuals,programming guides and other documentation provided to you by Sun under thisAgreement. "Programs" mean Java applets and applications intended to run onthe Java 2 Platform, Standard Edition (J2SETM platform) platform on Java-enabledgeneral purpose desktop computers and servers.

LICENSE TO USE.Subject to the terms and conditions of this Agreement, including, but not limitedto the Java Technology Restrictions of the Supplemental License Terms, Sungrants you a non-exclusive, non-transferable, limited license without license feesto reproduce and use internally Software complete and unmodified for the solepurpose of running Programs. Additional licenses for developers and/or publishersare granted in the Supplemental License Terms.

RESTRICTIONS.Software is confidential and copyrighted. Title to Software and all associatedintellectual property rights is retained by Sun and/or its licensors. Unlessenforcement is prohibited by applicable law, you may not modify, decompile, orreverse engineer Software. You acknowledge that Licensed Software is not designedor intended for use in the design, construction, operation or maintenance of anynuclear facility. Sun Microsystems, Inc. disclaims any express or implied warrantyof fitness for such uses. No right, title or interest in or to any trademark, service

Third-Party Legal NoticesJava 2 Runtime Environment

172

mark, logo or trade name of Sun or its licensors is granted under this Agreement.Additional restrictions for developers and/or publishers licenses are set forth inthe Supplemental License Terms.

LIMITED WARRANTY.Sun warrants to you that for a period of ninety (90) days from the date of purchase,as evidenced by a copy of the receipt, the media on which Software is furnished(if any) will be free of defects in materials and workmanship under normal use.Except for the foregoing, Software is provided "AS IS". Your exclusive remedyand Sun's entire liability under this limited warranty will be at Sun's option toreplace Software media or refund the fee paid for Software. Any implied warrantieson the Software are limited to 90 days. Some states do not allow limitations onduration of an implied warranty, so the above may not apply to you. This limitedwarranty gives you specific legal rights. You may have others, which vary fromstate to state.

DISCLAIMER OF WARRANTY.UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANYIMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENTTHAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

LIMITATION OF LIABILITY.TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITSLICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FORSPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISINGOUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVENIF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In noevent will Sun's liability to you, whether in contract, tort (including negligence),or otherwise, exceed the amount paid by you for Software under this Agreement.The foregoing limitations will apply even if the above stated warranty fails of itsessential purpose. Some states do not allow the exclusion of incidental orconsequential damages, so some of the terms above may not be applicable to you.

SOFTWARE UPDATES FROM SUN.You acknowledge that at your request or consent optional features of the Softwaremay download, install, and execute applets, applications, software extensions,


and updated versions of the Software from Sun ("Software Updates"), which mayrequire you to accept updated terms and conditions for installation. If additionalterms and conditions are not presented on installation, the Software Updates willbe considered part of the Software and subject to the terms and conditions of theAgreement.

SOFTWARE FROM SOURCES OTHER THAN SUN.You acknowledge that, by your use of optional features of the Software and/or byrequesting services that require use of the optional features of the Software, theSoftware may automatically download, install, and execute software applicationsfrom sources other than Sun ("Other Software"). Sun makes no representationsof a relationship of any kind to licensors of Other Software. TO THE EXTENT NOTPROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLEFOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT,CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSEDREGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATEDTO THE USE OF OR INABILITY TO USE OTHER SOFTWARE, EVEN IF SUN HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states do notallow the exclusion of incidental or consequential damages, so some of the termsabove may not be applicable to you.

TERMINATION.This Agreement is effective until terminated. You may terminate this Agreementat any time by destroying all copies of Software. This Agreement will terminateimmediately without notice from Sun if you fail to comply with any provision ofthis Agreement. Either party may terminate this Agreement immediately shouldany Software become, or in either party's opinion be likely to become, the subjectof a claim of infringement of any intellectual property right. Upon Termination,you must destroy all copies of Software.

EXPORT REGULATIONS.All Software and technical data delivered under this Agreement are subject to USexport control laws and may be subject to export or import regulations in othercountries. You agree to comply strictly with all such laws and regulations andacknowledge that you have the responsibility to obtain such licenses to export,re-export, or import as may be required after delivery to you.


174

TRADEMARKS AND LOGOS.You acknowledge and agree as between you and Sun that Sun owns the SUN,SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS,JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos andother brand designations ("Sun Marks"), and you agree to comply with the SunTrademark and Logo Usage Requirements currently located athttp://www.sun.com/policies/trademarks. Any use you make of the Sun Marksinures to Sun's benefit.

U.S. GOVERNMENT RESTRICTED RIGHTS.If Software is being acquired by or on behalf of the U.S. Government or by a U.S.Government prime contractor or subcontractor (at any tier), then the Government'srights in Software and accompanying documentation will be only as set forth inthis Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4(for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212(for non-DOD acquisitions).

GOVERNING LAW.Any action related to this Agreement will be governed by California law andcontrolling U.S. federal law. No choice of law rules of any jurisdiction will apply.

SEVERABILITY.If any provision of this Agreement is held to be unenforceable, this Agreementwill remain in effect with the provision omitted, unless omission would frustratethe intent of the parties, in which case this Agreement will immediately terminate.

INTEGRATION.This Agreement is the entire agreement between you and Sun relating to its subjectmatter. It supersedes all prior or contemporaneous oral or written communications,proposals, representations and warranties and prevails over any conflicting oradditional terms of any quote, order, acknowledgment, or other communicationbetween the parties relating to its subject matter during the term of thisAgreement. No modification of this Agreement will be binding, unless in writingand signed by an authorized representative of each party.


SUPPLEMENTAL LICENSE TERMSThese Supplemental License Terms add to or modify the terms of the Binary CodeLicense Agreement. Capitalized terms not defined in these Supplemental Termsshall have the same meanings ascribed to them in the Binary Code LicenseAgreement . These Supplemental Terms shall supersede any inconsistent orconflicting terms in the Binary Code License Agreement, or in any license containedwithin the Software.

■ A. Software Internal Use and Development License Grant. Subject to the termsand conditions of this Agreement, including, but not limited to the JavaTechnology Restrictions of these Supplemental Terms, Sun grants you anon-exclusive, non-transferable, limited license without fees to reproduceinternally and use internally the Software complete and unmodified (unlessotherwise specified in the applicable README file) for the purpose of designing,developing, and testing your Programs.

■ B. License to Distribute Software. Subject to the terms and conditions of thisAgreement, including, but not limited to the Java Technology Restrictions ofthese Supplemental Terms, Sun grants you a non-exclusive, non-transferable,limited license without fees to reproduce and distribute the Software, providedthat (i) you distribute the Software complete and unmodified (unless otherwisespecified in the applicable README file) and only bundled as part of, and forthe sole purpose of running, your Programs, (ii) the Programs add significantand primary functionality to the Software, (iii) you do not distribute additionalsoftware intended to replace any component(s) of the Software (unlessotherwise specified in the applicable README file), (iv) you do not remove oralter any proprietary legends or notices contained in the Software, (v) you onlydistribute the Software subject to a license agreement that protects Sun'sinterests consistent with the terms contained in this Agreement, and (vi) youagree to defend and indemnify Sun and its licensors from and against anydamages, costs, liabilities, settlement amounts and/or expenses (includingattorneys' fees) incurred in connection with any claim, lawsuit or action byany third party that arises or results from the use or distribution of any andall Programs and/or Software.

■ C. License to Distribute Redistributables. Subject to the terms and conditionsof this Agreement, including but not limited to the Java Technology Restrictionsof these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,limited license without fees to reproduce and distribute those files specificallyidentified as redistributable in the Software "README" file ("Redistributables")provided that: (i) you distribute the Redistributables complete and unmodified(unless otherwise specified in the applicable README file), and only bundledas part of Programs, (ii) you do not distribute additional software intended tosupersede any component(s) of the Redistributables (unless otherwise specified


176

in the applicable README file), (iii) you do not remove or alter any proprietarylegends or notices contained in or on the Redistributables, (iv) you onlydistribute the Redistributables pursuant to a license agreement that protectsSun's interests consistent with the terms contained in the Agreement, (v) youagree to defend and indemnify Sun and its licensors from and against anydamages, costs, liabilities, settlement amounts and/or expenses (includingattorneys' fees) incurred in connection with any claim, lawsuit or action byany third party that arises or results from the use or distribution of any andall Programs and/or Software.

■ D. Java Technology Restrictions. You may not modify the Java PlatformInterface ("JPI", identified as classes contained within the "java" package orany subpackages of the "java" package), by creating additional classes withinthe JPI or otherwise causing the addition to or modification of the classes inthe JPI. In the event that you create an additional class and associated API(s)which (i) extends the functionality of the Java platform, and (ii) is exposed tothird party software developers for the purpose of developing additionalsoftware which invokes such additional API, you must promptly publish broadlyan accurate specification for such API for free use by all developers. You maynot create, or authorize your licensees to create, additional classes, interfaces,or subpackages that are in any way identified as "java", "javax", "sun" or similarconvention as specified by Sun in any naming convention designation.

■ E. Source Code. Software may contain source code that, unless expresslylicensed for other purposes, is provided solely for reference purposes pursuantto the terms of this Agreement. Source code may not be redistributed unlessexpressly provided for in this Agreement.

■ F. Third Party Code. Additional copyright notices and license terms applicableto portions of the Software are set forth in theTHIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditionsof any third party opensource/freeware license identified in theTHIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty andlimitation of liability provisions in paragraphs 5 and 6 of the Binary CodeLicense Agreement shall apply to all Software in this distribution.

For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, SantaClara, California 95054, U.S.A. (LFI#135955/Form ID#011801)



178

Maintaining accessibility

This appendix includes the following topics:

■ About accessibility in Continuous Protection Server

■ About general keyboard navigation in Continuous Protection Server

■ About keyboard navigation in dialog boxes

■ Using keyboard shortcuts

■ Setting accessibility options

About accessibility in Continuous Protection ServerSymantec products meet federal accessibility requirements for software as definedin Section 508 of the Rehabilitation Act.

Keyboard shortcuts are available for all graphical user interface (GUI) operationsand menu items. Symantec products are compatible with operating systemaccessibility settings as well as a variety of assistive technologies. All manualsare provided as accessible PDF files, and the online help is HTML displayed in ahelp viewer window.

All program functions and menu items are accessible using the keyboardexclusively. Continuous Protection Server uses standard operating systemnavigation keys and keyboard shortcuts. For its unique functions, ContinuousProtection Server uses its own keyboard shortcuts.

Items in the task pane that do not have keyboard shortcuts are accessed by usingthe operating system’s “mouse keys”. This enable you to control the mouse throughthe numerical keyboard.

BAppendix

About general keyboard navigation in ContinuousProtection Server

You can navigate and use Continuous Protection Server with only the keyboard.In the GUI, the current active tree or table has a dark blue highlight, and thecurrent active tab, radio button, or check box is enclosed within a rectangle thatis formed by dotted lines. These areas are said to have focus and respond tocommands.

All Symantec GUIs use keyboard navigation standards for the following:

■ The TAB key moves the focus to the next active area, field, or control, followinga preset sequence. SHIFT+TAB moves the focus in the reverse direction throughthe sequence.

■ CTRL+TAB switches to the next Console view.

■ CTRL+SHIFT+TAB switches to the previous Console view.

■ UP and DOWN ARROW keys move focus up and down the items of a list.

■ The ALT key in combination with the underlined mnemonic letter for a fieldor command button shifts the focus to that field or button.

■ Either ENTER or the SPACEBAR activates your selection. For example, afterpressing the TAB key to select Next in a wizard panel, press the SPACEBAR todisplay the next screen.

■ SHIFT+F10 provides access to context menus.

About keyboard navigation in dialog boxesDialog boxes contain groups of controls that are necessary to set options or settingsfor programs.

The following are some general rules about dialog box navigation:

■ The TAB key moves focus between controls within the dialog box along a presetsequence.

■ Controls displaying a mnemonic (an underlined letter) can be selectedregardless of focus by typing ALT and the underlined letter.

■ A dark border indicates the default command button. Press Enter at any timeto choose the button with a dark border.

■ ESC chooses the Cancel button if one exists.

■ SPACEBAR chooses a control you select with the TAB key.

Maintaining accessibilityAbout general keyboard navigation in Continuous Protection Server

180

■ SPACEBAR changes the state of a check box that has focus. Typing a mnemonic(if one is available) moves the focus to the check box and change its state.

■ Arrow keys move focus within radio buttons, list boxes, sliders, groups ofoption controls, or groups of page tabs.

■ Items that cannot be changed are not visited by the TAB key sequence. Optionsthat are unavailable are grayed-out and can neither be selected nor given focus.

While the controls described here are typically found in dialog boxes, they alsocan occur in other contexts. The same navigation standards apply.

List BoxesList boxes display a column of available choices.

Different kinds of list boxes exist with additional navigation conventions such asthe following:

■ Drop-down list boxes by default show only the selected item. A small buttonto the right of the control will show a downward-pointing arrow. Select thearrow to display more items from the list box. If there are more choices thancan fit in the preset list box area, a slider appears along the side of the list box.Show or hide the list using ALT+DOWN ARROW, ALT+UP ARROW, or F4. TheTAB key selects an item.

■ Extended selection list boxes support selecting single items, blocks of items,or combinations of the two. After an item is selected, hold downCTRL+navigation keys to select or clear additional items or blocks of items.

Using keyboard shortcutsAll menu items can be selected by using accelerator or mnemonic keyboardshortcuts. An accelerator is a key combination that provides shortcut access to aGUI function. A mnemonic (sometimes referred to as a “hot key”) is a single-keyequivalent (used in combination with the ALT key) for selecting GUI componentssuch as menu items. The mnemonic “hot key” letter is underlined in the GUI.

Routine functions such as opening, saving, and printing files can be performedusing the standard Microsoft keyboard shortcuts. Other menu items are uniqueto Continuous Protection Server.

Table B-1 describes the keyboard shortcuts that are unique to ContinuousProtection Server.

181Maintaining accessibilityUsing keyboard shortcuts

Table B-1 Keyboard shortcuts that are unique to Continuous Protection Server

ResultContinuousProtection Servermnemonic

ContinuousProtection Serveraccelerator

The File menu expands. On the File menu, you can create new jobs,devices and media, print selected items, view properties, or exitContinuous Protection Server.

FALT

The Edit menu expands. On the Edit menu, you can rename, delete,copy, and select items. In addition, you can work with selection listsand search catalogs.

EALT

The View menu expands. On the View menu, you can change theinformation that displays on the screen. The options on the View menuchange according to which item is selected on the navigation bar.

VALT

The Tools menu expands. The Tools menu provides many importantoptions for working with Continuous Protection Server, includingstarting and stopping services, using device and media operations,using Wizards, and setting default options.

TALT

The Window menu expands. Use the Window menu to move to a newwindow or view.

WALT

The Help menu expands. Use the Help menu to access ContinuousProtection Server documentation and various Symantec Web sites.

HALT

Select secondary menu items by opening the main menu and using the UP orDOWN ARROW key until the item you want to work with is highlighted. Press theRIGHT ARROW key to open a submenu, and ENTER to select your choice.

Setting accessibility optionsSymantec software responds to operating system accessibility settings.

Symantec products are compatible with Microsoft's accessibility utilities. InWindows 2000, accessibility options involving keyboard responsiveness, displaycontrast, alert sounds, and mouse operation can be set through the Control Panel.

Accessibility features are primarily for the English version. Localized versions ofthis product include support for keyboard (mouseless) navigation using acceleratorkeys and mnemonic keys.

While all graphics in Symantec documentation are readable- by screen readers,setting your screen reader to ignore graphics improves performance.

Maintaining accessibilitySetting accessibility options

182

To set accessibility options

◆ Do one of the following:

■ On the Windows taskbar, click Start > Settings > Control Panel >Accessibility Options.

■ On the Windows taskbar, click Programs >Accessories >Accessibility>AccessibilityWizard.

183Maintaining accessibilitySetting accessibility options

Maintaining accessibilitySetting accessibility options

184

Administration Console The interface that the administrator uses to manage operations in CPS, such assetting backup destinations, creating backup or restore jobs, and monitoring CPSprocesses and alerts.

administrator rights The credentials that enable a person to make systemwide changes to a domain orcomputer, install programs, and access all files. The administrator user accounthas full access to other user accounts. Administrator rights also enable the personto manage user and group accounts, assign passwords, and grant permissions.

alert An event, such as a completed backup job, that usually requires some form of userinteraction or acknowledgment.

backup destination The location on a Protection Server where the files that are backed up from aBusiness Server are stored. The destination is defined in the backup job properties.Only one backup destination is allowed per volume.

Backup Exec Retrieve The gateway by which users access the Web Restore Server Component to retrievefiles. Backup Exec Retrieve uses Internet browsers (Internet Explorer 6.0 or later,and others). CPS software is not required on the user workstations.

Backup Group A group of computers that are managed by a single Continuous ManagementService. Files can be backed up only to a Protection Server that is in the sameBackup Group as the Business Server.

backup job An operation that has been scheduled for processing by the ContinuousManagement Service. For example, if you make selections and submit a backupthat is based on those selections, you have created a backup job. Jobs containsource and destination information, settings, and a schedule. Every type of backupjob backs up the selected data and all regular shares.

backup schedule The specific days and times when backup jobs are run. These can be one-timeevents, periodically run jobs, or continuous processes. Administrators can set orchange backup schedules in the CPS Administration Console.

backup schedule types This para is intentionally added.

backup strategies The procedures you implement for backing up your information on the network.A good backup strategy requires minimal time to get your information back inthe event of a loss.

Glossary

Business Server A local or remote server where users save files and folders as part of their dailywork. A Business Server is the source of a backup job and must have a ContinuousProtection Agent installed.

CMS (Continuous

Management Service)

The primary control of the Continuous Protection Server processes. The CMSmaintains a database with all command and control information, and configuresthe Protection Agents according to settings that are sent from the AdministrationConsole.

continuous backup A backup job that runs continuously, thereby allowing any changes to be backedup as they occur.

CPA (Continuous

Protection Agent)

The Continuous Protection Agent is a software collection that must be installedon each computer in a Backup Group. This agent uses a file system componentand file replication technology to enable continuous data protection betweencomputers in the Backup Group.

CPS Network Helper

Service

A CPS component that allows communications within Continuous ProtectionServer and with Backup Exec. The Network Helper Service was formerly knownas the Enterprise Network Layer (ENL).

destination server The server in the Continuous Protection Server network to which information iswritten during the job process. In a backup job, the information is copied fromthe Business Servers (sources) to a Protection Server (destination).

EFS (Encrypting File

System)

A Microsoft Windows technology that lets you store information on disk in anencrypted format. The encryption is enabled through the advanced file attributes.CPS skips over files that are encrypted with EFS.

history file A file on the Continuous Management Service where snapshots are stored.Continuous Protection Server stores each snapshot for 24 hours unless specifiedotherwise in the retention settings.

Indexing component The Indexing component maintains a directory for the files that are available touser file retrieval using the Web Restore Server Component and Backup ExecRetrieve. The Indexing component is an optional feature and should be installedon any server that will be accessed by users for file retrieval using Backup ExecRetrieve. The Indexing component supports searches by file, file versions andrecent activity.

infrastructure The underlying foundation or basic framework of the Backup Group. ContinuousProtection Server runs on an infrastructure of Windows-based servers.

job A job defines what data is to be backed up, which server the data will be backedup from and to, when the data will be backed up, and other settings. Similar jobsare defined to restore the data.

job log The results of a job and are created when a job runs. You can review job logs tofind job errors and details.

Glossary186

periodic backup A backup job that runs on timed intervals, such as Monday through Friday, every12 hours.

permissions The credentials that enable a particular user to access a particular resource in ashared network environment. For example, users are granted permissions toaccess files, directories, and printers.

Protection Server A Protection Server is the destination of data that is backed up by CPS fromBusiness Servers.

regular backup A backup job that is run on a regular schedule, such as every Friday at 6:00 P.M.

Remote Agent for

Windows Systems

A CPS uses the Symantec Backup Exec Remote Agent for Windows Systems(Remote Agent) to access System State information for backup and restore. RemoteAgent is an optional component and should be installed on any CPS BusinessServer that needs to have its System State protected. Remote Agent should alsobe installed on the Protection Server and Continuous Management Service if theywill be protected by Symantec Backup Exec.

restore job A job defines what data is to be restored, from what computers the data will berestored from and back to, when the data will be restored, and other settings.

retention properties The length of time you want to save snapshots on the backup destination. Youcan store snapshots up to a limit that is determined by your underlying snapshottechnology. For most installations, this limit is approximately 64 snapshots perdestination. This limit may vary considerably if alternative snapshot providersare installed.

scheduled backup A backup job that runs on a set schedule. Three kinds of scheduled backup jobsare used in Continuous Protection Server: regularly scheduled, periodicallyscheduled, and continuous. Regularly scheduled backup jobs run on specific daysat a specific time, every week. Periodically scheduled backup jobs run on specificdays at timed intervals, such as every 12 hours. Continuously scheduled backupjobs are ongoing.

service account The Windows user account under which the CPS services run.

shadow A point-in-time, fixed representation, or copy of a specified volume.

shadow storage A volume that is specified where snapshots are stored.

SmartLink A technology that integrates Backup Exec with other Symantec products, such asCPS. SmartLink enables the status of backup jobs that are created in ContinuousProtection Server to display in the Backup Exec Administration Console.

snapshot A point-in-time, fixed representation, or copy of a specified volume.

source computer A server in the Continuous Protection Server Backup Group that contains the filesto be backed up. This computer must have a Continuous Protection Agent installed.

187Glossary

storage space The disk drive space on the servers in the Continuous Protection Server BackupGroup. Storage space generally refers to available disk space.

strategic backup plan The philosophy of using multiple types of backup jobs to protect yourorganization’s information. A strategic backup plan generally uses several layersof backups to protect different types of information.

strategic naming

conventions

The philosophy of naming files and backup destinations in a meaningful way.Rather than naming backup destinations sequentially such as Backup01, Backup02,and Backup03, destination names are based on physical office locations, functionalbusiness units, or other meaningful criteria. Therefore, when viewing a list ofbackup destinations, the destinations are differentiated from each other and areeasier to find information.

system information The Windows operating system includes data that requires special handling toprotect and restore properly. This data, referred to as “system information” inCPS, contains different information depending on the specific version of Windowsthat is installed on the system. For Windows 2000 systems, this includes a set ofdata that is called System State and that includes various operating system filesand registry information. For those systems that support Volume Shadow CopyServices (VSS), the system information consists of key elements of Shadow CopyComponents including System State and Service State.

system resources The parts that make up or operate computer systems or networks such as clientcomputers, servers, printers, cables, modems, bandwidth, memory, or motherboards. Resources are allocated to programs or processes while they are running.

System State backup A snapshot of system-specific data on the source that is comprised of the registry,the COM+ Class Registration database, and start and system files. If the source isa Certificate Services database, the Certificate Services database is also included.If the server is a domain controller, the data also includes the Active Directoryservices database and SYSVOL directory. The System State data is backed up andrestored only as a collection, never individually.

Web Restore Server

component

The Web Restore Server component is a feature of the CMS that makes availableversioned copies (snapshots) of files for user retrieval to their workstations.

Glossary188

Symbols64-bit support 20

Aaccessibility

dialog boxes 180keyboard shortcuts 181overview 179settings 182

Active Directory 106Adaptive Server Anywhere 39, 41adding scripts 100Administration Console

alerts view 61assistant view 57backup job properties 61credentials 56defined 15general features 56information desk view 58job monitor view 61menu bar 56minimum requirements 34navigation bar 56preview pane 57restore view 61selection pane 57server properties 59setup view 58setup view properties 59starting 56status bar 57system summary view 58task pane 56views

general 57Administration Service 39AlertGroomFrequency parameter 80alerts 121

deleting 124fatal 134

alerts (continued)messages 134properties 134responding to 123SmartLink

pairs 137viewing 122

active 122history 122properties 123

alerts view 61AlwaysDoRegionAnalysis parameter 80ASA directory 39assistant view 57autonomy directory 39

Bbackup destinations

adding 69credentials 69deleting 71description 69managing 69properties 60renaming 71

Backup Execalerts 134Desktop and Laptop option 21job logs

accessing 137job selection for backup 134media server credentials 134protecting

Business Servers 129Continuous Management Service 128Continuous Protection Server 126CPS databases 128Protection Servers 128snapshots 129

restoringBusiness Servers 131

Index

Backup Exec (continued)restoring (continued)

Continuous Management Service 129CPS 129Protection Servers 130

specifying a media server 133Backup Exec Retrieve

browse 110description 15–16, 109download list 110features 109minimum requirements 36recent activity 110search 110security and credentials 111URL 111

backup groupdefined 14moving servers between 66

backup jobsadding scripts 100alert history 122alert properties 123alerts posted to Backup Exec 134changing bandwith 100changing schedules 98creating 92credentials 94filtering alerts 122filters 95including and excluding information 95managing

alerts 121statuses 116

manual operation 101pairs 116properties 61schedules 22states 117status 116storing snapshots 75viewing the status 116

backup schedulescontinuous

description 23periodic

description 23scheduled

description 23

backup strategiesconsiderations 21periodic backups 23regular backups 23

bandwidth limiting 100bandwith

limiting 100batch files 132BroadcastAddress parameter 80BroadcastHops parameter 80Broker Services, services 40Business Servers

configuring 63description 14installing 47managing 63minimum requirements 32uninstalling 52

CCentral Admin Server environments 133command-line syntax

errors 139complete installation 41configuration troubleshooting 146Configuration Writer, services 40ConnectionPooling parameter 80continuous backups

description 23plans 23

Continuous Management Servicedefined 15system requirements 33

Continuous Protection Servercomponents 14credentials 42database backup and restore 149databases 128documentation 23drivers 39firewall support 36installation modification 51installation upgrade 50installing 41integrating with Backup Exec 125invalid jobs 140job report 119jobs topic box 120, 141key tasks 19

Index190

Continuous Protection Server (continued)monitoring jobs 116overview 13service account 31, 45Services 39Services Manager 67starting 56tunable parameters 79uninstalling 51use model 16

cpssernum.xml file 43credentials

Administration Console 56backup destinations 69Backup Exec DLO 150Backup Exec media server 134CPS service account 31creating backup jobs 94installing CPS 42Internet Explorer security 111push installing CPS 48SmartLink 131

Ddata protection 21database backup and restore 153database directory 39database maintenance utilities 152database services 40database validation and repair 153DaysToKeepAlertItems parameter 80DaysToKeepDeletedSnapshots parameter 80DelayDirChangeNotifications parameter 81Desktop and Laptop option 21, 113destinations

installing 41uninstalling 51

Directory Services Restore Mode 106DoEventLog parameter 81domain security mode 68domain trust 32drivers directory 39

EEnableDebugConsole parameter 81EnableLogFile parameter 81EnableTimestamp parameter 81encrypted files 110

Encrypting File Systemdefined 92

Environment Check 29Evaluation version 43exceptions topic box 140Exchange protection 21

FFFXPort parameter 82files and directories

restoring 104FilteredIDList parameter 82filters

deleting 98description 95include and exclude 96modifying 97

firewall support 36

GGateway (ENL\System) parameter 82Gateway (Network.TCPIP) parameter 82Gateway (Network.UDPv6) parameter 82

Hhardware requirements 33Help

online 24Hierarchical Storage Management 110history

alerts 122

Iindexing component

description 15minimum requirements 36

Indexing directory 46Indexing Root parameter 83indexing services 40indexing state

snapshots 77information desk view 58install directory 39installation

about 28complete 41Environment Check 29Evaluation version 43

191Index

installation (continued)modifying 51prerequisites 27push install 47upgrading 50

installation logsviewing 46

Internet Explorersecurity 111

Jjob details topic box 142job ID

not found 140job logs

job header 141SmartLink 138topic box 142viewing 137

job monitor view 61job name

not found 140job pairs

alerts 137description 116exceptions 140

job report 119job state

unknown 140job states 116job status 118jobs

monitoring 116Journal directory 46JournalRoot parameter 83

Llatency

target 121, 142license keys 43limiting bandwidth 100LiveUpdate 20local system object cache 49log entries

limiting 134parameter 142

LogOpenFileTableOncePerSet parameter 83LogPath (EFC) parameter 83

LogPath parameter 83logs

viewing installation 46Logs directory 39LogText parameter 84

MMaster (ENL\System) parameter 84MaxDirSize parameter 84MaxLogSize (ENL) parameter 84MaxLogSize parameter 84MaxPacketSize (Network.TCPIP) parameter 84MaxPacketSize (Network.UDPv6) parameter 85MaxRAPerCentChange parameter 85menu bar 56MinRASizeInKb parameter 85monitoring processes 116MsBetweenRallyChecks parameter 85

NNamedObjectsRoot parameter 85navigation bar 56NetBios 37Network (ENL\System) parameter 85Network Helper services 37–38, 40network load balancing service 42, 144network shares

restoring 107NeverDoRegionAnalysis parameter 86NumberOfLogs parameter 86

OOutboundJournalCleanupSize parameter 86OutboundJournalNominalSize parameter 86OutboundSyncJournalLimit parameter 86

Ppair header topic box 142pair log topic box 142pair status 118pairs

job 116parameters

tunableAlertGroomFrequency 80AlwaysDoRegionAnalysis 80BroadcastAddress 80BroadcastHops 80

Index192

parameters (continued)tunable (continued)

changing values 89ConnectionPooling 80DaysToKeepAlertItems 80DaysToKeepDeletedSnapshots 80DelayDirChangeNotifications 81DoEventLog 81EnableDebugConsole 81EnableLogFile 81EnableTimestamp 81FFXPort 82FilteredIDList 82Gateway (ENL\System) 82Gateway (Network.TCPIP) 82Gateway (Network.UDPv6) 82IndexingRoot 83JournalRoot 83LogOpenFileTableOncePerSet 83LogPath 83LogPath (EFC) 83LogText 84Master (ENL\System) 84MaxDirSize 84MaxLogSize 84MaxLogSize (ENL) 84MaxPacketSize (Network.TCPIP) 84MaxPacketSize (Network.UDPv6) 85MaxRAPerCentChange 85MinRASizeInKb 85MsBetweenRallyChecks 85NamedObjectsRoot 85Network (ENL\System) 85NeverDoRegionAnalysis 86NumberOfLogs 86OutboundJournalCleanupSize 86OutboundJournalNominalSize 86OutboundSyncJournalLimit 86PreferredAddress (Network.TCPIP) 87PreferredAddress (Network.UDPv6) 87PreferredNIC (Network.UDPv6) 87PreferredNIC(Network.TCPIP) 87registry entries 78ReservedFreeDiskSpace 87RxRmsStaticPort 88RxRsaStaticPort 88Schedule 88SerializeIrpLogging 88ShareInfoAsSingleComponent 88

parameters (continued)tunable (continued)

Socket 88UsePrivateFindFileMethod 89using Settings Utility 79Verbose (ENL) 89VolumeLevel 89

periodic backupdescription 23

permissionsbackup destinations 69media server 134

port settingsServices Manager 37Settings Utility 37

pre/post commandsadding 100runtime settings 132

PreferredAddress (Network.TCPIP) parameter 87PreferredAddress (Network.UDPv6) parameter 87PreferredNIC (Network.TCPIP) parameter 87PreferredNIC (Network.UDPv6) parameter 87preview pane 57properties

alerts 123backup destination 60backup jobs 61server 59, 63

Protection Agentdefined 15service 40

Protection Serverdescription 14minimum requirements 33

push installation 47

Rregistry entries 78Remote Agent for Windows Systems 16renaming backup folders 69reparse points 110report

job 119ReservedFreeDiskSpaceparameter 87responding to alerts 123restore view 61retention policies

snapshots 73, 75run log topic box 141

193Index

RunLog parameter 141RxRmsStaticPort parameter 88RxRsaStaticPort parameter 88

SSchedule parameter 88scheduled backups

description 23schedules

changing 98changing for snapshots 75continuous backups 92snapshots 74

schedules for jobstroubleshooting 94

scripts 100security

Internet Explorer 111security modes

domain 68workgroup 68

selection pane 57SerializeIrpLogging parameter 88server properties 59servers

managing properties 63moving between backup groups 66

service account 31Services

Administration Service 39Broker Services 40Configuration Writer 40database 40indexing 40Network Helper 40Protection Agent 40System State Manager 40Web restore backend 40Web restore frontend 40Web server 40

services manager 67setintegratedlogin utility 154Settings Utility 20, 78–79setup view 58setup view properties 59Shadow Copy Components 92Shadow Storage

changing location 70ShareInfoAsSingleComponent parameter 88

Single Instance Storage 110SmartLink

alertscategories 134

credentials 131description 131fatal alerts 134job log descriptions 138job logs

summary messages 139job topic box 138options topic box 140topic boxes

command-line syntax errors 139CPS jobs 141exceptions 140job details 142job log 142options 140pair header 142run log 141

snapshotschanging schedules 75creating 73creating on demand 73deleting 77indexing state 77managing 72reasons for deleting 76reindexing 146retention 75retention policies 73scheduling 74storing 75viewing history 76

Socket parameter 88source properties 63status

job and pair 118status bar 57Symantec

knowledge base 25LiveUpdate 20Technical Support 23

System Cache directory 46System Information 106system requirements

hardware 33minimum 32

Index194

System Statebackup schedule 106Manager 40restore to an Active Directory 106restoring 105

system summary view 58

Ttarget latency 121, 142task pane 56Technical Support 23troubleshooting 143troubleshooting issues

Administration Console 145anti-spyware software 144Apache Tomcat Web Server 144Backup Exec compatibility 30Backup Exec Retrieve 150browsers supported 144business servers 146configuration 146connection outages 150CPS backup jobs 150CPS components 145CPS configurations 146CPS restore jobs 150database backup and restore 149, 153database maintenance 152database validationa nd repair 153disk space for indexing 147file system filter drivers 31installation 144network load balance 144NIC failure 144pathnames with Asian characters 144processing efficiency 148push installing over domain trust 144services account 31setintegratedlogin utility 154snapshot schedules 94SNMP support 148system state backup and restore 150uninstalling CPS 144utility partitions 148workgroups and domains 144

Uuninstallation

Business Server 52Continuous Protection Server 51destinations 51sources 52

UsePrivateFindFileMethod parameter 89

VVerbose (ENL) parameter 89VolumeLevel parameter 89

WWeb restore

backend services 40frontend services 40server component 15, 35

Web server service 40Windows File Sharing 37workgroup

environment 32security mode 68

195Index

symantec continuous protection server 12.5 administration

Documents

party software

symantec product

licensed software

symantec logo

free software licenses

technical support group

documentation version

party programs