Backup Exec Continuous Protection Server 2010 Guide

Symantec Backup Exec
Continuous Protection Server

2010
Administrator's Guide
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Documentation version: 2010
Legal Notice
Copyright © 2009 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec

Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks
of their respective owners.
This Symantec product may contain third party software for which Symantec is required
to provide attribution to the third party (“Third Party Programs”). Some of the Third Party
Programs are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under
those open source or free software licenses. Please see the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information 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 document
may be reproduced in any form by any means without prior written authorization of
Symantec 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 OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as 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 in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, 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 Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Printed in the United States of America.
10 9 8 7 6 5 4 3 2 1
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality. The Technical Support group also creates content for our online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. For example, the Technical Support group works with Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.
Symantec’s maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the right
amount of service for any size organization
■ Telephone and Web-based support that provides rapid response and
up-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 Web
site at the following URL:
www.symantec.com/techsupp/
Contacting Technical Support

Customers with a current maintenance agreement may access Technical Support
information at the following URL:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be
at the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
■ 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 registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
Customer service
Customer 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 resources
If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
Asia-Pacific and Japan customercare_apac@symantec.com
Europe, Middle-East, and Africa semea@symantec.com
North America and Latin America supportsolutions@symantec.com
Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber attacks, comprehensive threat
analysis, and countermeasures to prevent attacks before they occur.
Managed Security Services These services remove the burden of managing and monitoring security devices
and events, ensuring rapid response to real threats.
Consulting Services Symantec Consulting Services provide on-site technical expertise from
Symantec and its trusted partners. Symantec Consulting Services offer a variety
of prepackaged and customizable options that include assessment, design,
implementation, monitoring, and management capabilities. Each is focused on
establishing and maintaining the integrity and availability of your IT resources.
Educational Services Educational Services provide a full array of technical training, security
education, security certification, and awareness communication programs.
To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.
Contents
Technical Support ............................................................................................... 4

Chapter 1 Introducing Symantec Continuous Protection
Server ............................................................................... 13
About Symantec Backup Exec Continuous Protection Server ................ 13
Components of Continuous Protection Server ................................... 14
How Continuous Protection Server works ......................................... 16
What you can do with Continuous Protection Server ........................... 19
About backup strategies and planning ............................................. 20
Data protection considerations ................................................. 21
About backup job schedules ..................................................... 21
Where to find more information ..................................................... 23
Accessing the Continuous Protection Server
documentation ................................................................ 23
Accessing the online Help ........................................................ 24
Accessing the Symantec Technical Support Web site .................... 24
Accessing the Symantec Backup Exec Web site ............................ 24
Chapter 2 Installing Continuous Protection Server ........................ 25

Before you install ......................................................................... 25
Guidelines for installation ....................................................... 26
Checking your environment before installation ........................... 27
Continuous Protection Server and Backup Exec
compatibility ................................................................... 28
File system filter driver compatibility ........................................ 29
Understanding the Continuous Protection Server service
account .......................................................................... 29
System requirements for the product ............................................... 30
System requirements for Business Servers .................................. 30
System requirements for Continuous Management Service and
Protection Servers ............................................................ 31
System requirements for Administration Console ........................ 32
Firewall support .................................................................... 33
What gets installed and where ........................................................ 35
Folders that are installed ......................................................... 35
8 Contents
Drivers that are installed ......................................................... 36

Continuous Protection Server services that are installed ............... 36
Registry entries ..................................................................... 36
Performing an initial installation .................................................... 37
Viewing installation logs ......................................................... 42
Push-installing Continuous Protection Server components .................. 43
Upgrading to Continuous Protection Server 2010 ............................... 46
Modifying Continuous Protection Server installations ........................ 47
Uninstalling the Continuous Protection Server .................................. 47
Uninstalling a Continuous Protection Agent ..................................... 48
Chapter 3 Using the Administration Console ................................... 51

About the Continuous Protection Server Administration
Console ................................................................................ 51
Starting the Continuous Protection Server Administration
Console ................................................................................ 52
About the general Administration Console features ............................ 52
About the Administration Console views .......................................... 53
Overview view ....................................................................... 53
Setup view ............................................................................ 54
Restore view ......................................................................... 57
Job Monitor view .................................................................... 57
Alerts view ............................................................................ 57
Chapter 4 Configuring Continuous Protection Server .................... 59

Configuring Business Servers ......................................................... 59
Reviewing the general properties of a Business Server .................. 60
Reviewing the volume properties of a Business Server .................. 61
Moving of servers between Backup Groups ....................................... 62
Managing the Continuous Protection Server Services ......................... 63
Stopping or starting Continuous Protection Server services ........... 63
Adding or removing servers from the Service Manager ................. 64
Changing service account credentials ........................................ 64
Managing backup destinations ....................................................... 65
Adding a backup destination .................................................... 65
Configuring a backup destination for Shadow Storage .................. 66
Renaming backup destinations ................................................. 67
Deleting backup destinations ................................................... 67
Managing snapshots ..................................................................... 68
Creating snapshots on demand ................................................. 69
Creating a snapshot schedule ................................................... 70
Editing a snapshot schedule ..................................................... 71
Contents 9
Defining a retention policy for a snapshot .................................. 71

Viewing snapshot history ........................................................ 72
States of snapshot indexing ..................................................... 73
Deleting snapshots ................................................................. 73
Configuring registry entries ........................................................... 74
Accessing the Settings Utility ................................................... 74
About the Settings Utility tunable parameters ............................. 75
Changing Settings Utility parameters ........................................ 85
Chapter 5 Backing up data ................................................................... 87

About CPS backup jobs .................................................................. 87
About backing up System State and Shadow Copy
Components .................................................................... 88
How encrypted files are handled ............................................... 88
Creating CPS backup jobs .............................................................. 88
Editing backup job configurations ................................................... 91
Moving a backup job to a different backup destination ........................ 91
Including and excluding information from backup jobs ................. 91
Changing a backup job schedule ................................................ 94
Limiting the network bandwidth of a backup job .......................... 96
Adding a script that runs before or after backup jobs .................... 96
Starting, stopping, and canceling backup jobs manually ...................... 97
Chapter 6 Restoring data ...................................................................... 99

About restoring data with Continuous Protection Server ..................... 99
Restoring files and folders ........................................................... 100
Restoring system information ...................................................... 101
Restoring System State to an Active Directory system ....................... 102
Restoring network shares ............................................................ 103
Chapter 7 Using Backup Exec Retrieve ............................................ 105

About Backup Exec Retrieve ......................................................... 105
How Backup Exec Retrieve works .................................................. 106
What end users can do with Backup Exec Retrieve ............................ 108
Before you install Backup Exec Retrieve .......................................... 110
Requirements for installing Backup Exec Retrieve on a Web
server ................................................................................. 110
Requirements for using Backup Exec Retrieve on end users'
computers ........................................................................... 112
About deploying the Silverlight run time in your
organization .................................................................. 113
10 Contents
Installing Backup Exec Retrieve .................................................... 113

About configuring Backup Exec Retrieve ......................................... 115
Adding a data source ............................................................. 115
Editing a data source ............................................................. 117
Deleting a data source ........................................................... 117
Uninstalling Backup Exec Retrieve ................................................ 118
Troubleshooting Backup Exec Retrieve ........................................... 118
Chapter 8 Monitoring CPS processes ............................................... 121

About the Job Monitor ................................................................. 121
Monitoring jobs and job pairs ....................................................... 122
About job states ................................................................... 122
Viewing the status of a job and job pairs ................................... 123
Viewing a job report .................................................................... 125
CPS job report details ............................................................ 125
Managing CPS job alerts .............................................................. 127
Viewing and filtering active alerts ........................................... 128
Viewing and filtering alert history ........................................... 128
Viewing alert properties ........................................................ 129
Responding to active alerts .................................................... 129
Deleting alerts from alert history ............................................ 130
Chapter 9 Using Continuous Protection Server with Backup

Exec ................................................................................ 131
How Continuous Protection Server works with Backup Exec ............... 131
Protecting your Exchange Servers with Continuous Protection Server
and Backup Exec .................................................................. 132
Protecting CPS with Backup Exec .................................................. 132
Configuring CPS for Backup Exec ............................................ 133
Backing up CPS with Backup Exec ............................................ 133
Restoring Continuous Protection Server with Backup Exec ........... 135
Monitoring CPS jobs in Backup Exec .............................................. 137
Understanding the credentials for using Backup Exec
SmartLink ..................................................................... 137
Setting up a SmartLink connection between CPS and Backup
Exec ............................................................................. 138
Viewing Backup Exec alerts .................................................... 140
Viewing Backup Exec job logs ................................................. 143
About CPS backup job log details ............................................. 143
Contents 11
Chapter 10 Troubleshooting Continuous Protection Server .......... 149

Troubleshooting Continuous Protection Server ................................ 149
Installation and upgrade issues ..................................................... 149
Component issues ....................................................................... 151
Configuration issues ................................................................... 151
General issues ............................................................................ 152
Backup and restore job issues ....................................................... 154
Database maintenance utilities ..................................................... 155
CPS database backup and restore ............................................. 156
CPS database validation and repair .......................................... 156
Resetting the standard logon .................................................. 156
Appendix A Third-Party Legal Notices ................................................ 161

About Third-Party Legal Notices ................................................... 162
ACE and TAO are governed under the same license provided
below. ................................................................................ 162
ACE (The Adaptive Communication Environment) ............................ 162
TAO ......................................................................................... 162
Apache Struts, Xerces C++ and Tomcat are governed under the same
license provided below .......................................................... 164
Apache Struts ............................................................................ 164
Xerces C++ ................................................................................ 164
Tomcat ..................................................................................... 164
Definitions. ......................................................................... 165
Grant of Copyright License. .................................................... 166
Grant of Patent License. ......................................................... 166
Redistribution. ..................................................................... 166
Submission of Contributions. .................................................. 167
Trademarks. ........................................................................ 167
Disclaimer of Warranty. ........................................................ 167
Limitation of Liability ........................................................... 168
Accepting Warranty or Additional Liability. .............................. 168
Blowfish Encryption ................................................................... 168
Curl/LibCurl .............................................................................. 169
Digital Encryption Standard (DES) - MIT ......................................... 169
ICU .......................................................................................... 170
MD5 ......................................................................................... 170
Open SSL .................................................................................. 171
Original SSLeay License ......................................................... 172
ReportCtrl.h.2.0.1 ....................................................................... 174
STLport .................................................................................... 174
Java 2 Runtime Environment ........................................................ 175
12 Contents
DEFINITIONS. ..................................................................... 176

LICENSE TO USE. ................................................................. 176
RESTRICTIONS. ................................................................... 176
LIMITED WARRANTY. .......................................................... 177
DISCLAIMER OF WARRANTY. ................................................ 177
LIMITATION OF LIABILITY. ................................................... 177
SOFTWARE UPDATES FROM SUN. .......................................... 177
SOFTWARE FROM SOURCES OTHER THAN SUN. ...................... 178
TERMINATION. ................................................................... 178
EXPORT REGULATIONS. ....................................................... 178
TRADEMARKS AND LOGOS. .................................................. 179
U.S. GOVERNMENT RESTRICTED RIGHTS. .............................. 179
GOVERNING LAW. ............................................................... 179
SEVERABILITY. ................................................................... 179
INTEGRATION. .................................................................... 179
SUPPLEMENTAL LICENSE TERMS .......................................... 180
Appendix B Maintaining accessibility ................................................. 183

About accessibility in Continuous Protection Server ......................... 183
About general keyboard navigation in Continuous Protection
Server ................................................................................ 184
About keyboard navigation in dialog boxes ...................................... 184
List Boxes ........................................................................... 185
Using keyboard shortcuts ............................................................ 185
Setting accessibility options ......................................................... 186
Glossary ............................................................................................................. 189

Index ................................................................................................................... 193
Chapter 1
Introducing Symantec
Continuous Protection
Server
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 Protection

Server
Symantec Backup Exec Continuous Protection Server helps ensure that
business-critical data is always protected and always available. It combines proven
Backup Exec data protection with replication technology and disk-based data
protection to provide fast and reliable data backup and retrieval. It provides
continuous data protection and lets you restore data at a granular level from
points in time throughout the day. You can also perform simultaneous backups
of multiple servers. Continuous Protection Server integrates with Symantec
Backup Exec for Windows Servers for traditional tape-based data protection. It
delivers integrated management through Backup Exec SmartLink technology.
14 Introducing Symantec Continuous Protection Server
Components of Continuous Protection Server
Continuous Protection Server lets end users restore their own data through Backup
Exec Retrieve, a Web-based data-retrieval tool. End users can retrieve their own
files without IT assistance, and you do not need to install any software or clients
on their computers.
Continuous Protection Server is compatible with the following Symantec products:
Backup Exec (11d or later) for Windows Protects your application servers such as
Servers Microsoft Exchange, SQL, and the
Continuous Management Service. It also
provides long-term storage to various media.
Storage Foundation for Windows Provides easy-to-use online disk storage

management for mission-critical, enterprise
Windows environments.

Table 1-1 describes the components of Continuous Protection Server.
Table 1-1 Components of Continuous Protection Server
Component Description
Backup Group The Backup Group includes the following components:
■ One Continuous Management Service

■ At least one Business Server
■ At least one Protection Server
■ CPS Administration Console
Business Servers The Business Servers store the data that users save during the course of their daily operations.
Once data is saved to the Business Server, the data can be backed up to a Protection Server.
The Business Servers must reside in the same Backup Group as the Protection Server. You
must install a Continuous Protection Agent on each Business Server.
Protection Server The Protection Server is the destination of the CPS backup data. It is typically installed at
a primary location or a central office. The Protection Server hosts the backup destinations
where snapshots are taken and indexed. More than one Protection Server can be installed
in the Backup Group.
Introducing Symantec Continuous Protection Server 15
Table 1-1 Components of Continuous Protection Server (continued)
Continuous The Continuous Management Service does the following:

Management Service
■ 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 must
install 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 37.
Continuous The Continuous Protection Agent manages data collection during backup and restore jobs.
Protection Agent You must install it on all Business Servers and Protection Servers in the Backup Group.
Administration The Administration Console controls all aspects of CPS, including defining data sources and
Console destinations, creating backup and restore jobs, and defining backup and snapshot schedules.
Additionally, the Administration Console is used to view and respond to alerts, monitor
backup and restore jobs, and obtain product updates from Symantec.
Backup Exec Retrieve Backup Exec Retrieve allows workstation users to find and retrieve the files that were backed
up with CPS, without requiring any assistance from system administrators. Workstations
only require Web browsers to use this feature, so you do not need to install the Continuous
Protection Server software on the users’ workstations.
Users can browse all of their backed up files, or they can search for files by using full or
partial file names. They can also view and restore versions of backed up files.
Backup Exec This component lets users view the combined status of CPS and Backup Exec jobs in the
SmartLink Backup Exec Administration Console.
Remote Agent for Continuous Protection Server uses the Symantec Backup Exec Remote Agent for Windows
Windows Systems Systems (Remote Agent) to access System State information for backup and restore. Remote
(Remote Agent) Agent 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 server
already contains Remote Agent functionality. However, the Remote Agents that are used
by CPS and Backup Exec must be the same version (11d or later).
How Continuous Protection Server works
Table 1-1 Components of Continuous Protection Server (continued)
Symantec LiveUpdate Symantec LiveUpdate is installed with the Administration Console. LiveUpdate notifies
administrators when updates to installed Symantec products become available for download.
LiveUpdate connects to the Symantec LiveUpdate server by the Internet.
See “How Continuous Protection Server works” on page 16.

Figure 1-1 shows an example of how Continuous Protection Server works with
Backup Exec to protect your business data.
Figure 1-1 Overview of the Continuous Protection Server model
End-User Workstations
(Connected to a local
Business Server)
Business Servers
(Local or Remote Offices)
(Continuous
Protection
5
Agent)
CPS
Admin
Console
3 6
Protection Server Continuous
Management
(Continuous Server
Copy Center
Protection
Agent)
4
2
Snapshots Web
and Server
Indexing
7
9
Backup Exec Backup Exec

Admin media server
Console Data
8 Archived to
Tape or Disk
Storage
The following scenario provides an example of how you can use Continuous
Protection Server with Backup Exec to back up and restore data:
1 Users save files and folders to local file servers (Business Servers) as part of
their normal daily work. Business Servers are interconnected and together form
a common Backup Group.
See “Configuring Business Servers” on page 59.
2 The Continuous Protection Server Backup Destination Wizard designates a

specific directory on a specific Protection Server where the data is backed up.
The backup-destination definition includes the schedule for the data snapshots
and 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 server
in 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 65.
3 You can use the Backup Job Wizard to create Continuous Protection Server
backup jobs to back up data from one or more Business Servers to a Protection
Server. When you create a job, you select the data to be backed up and the
schedule for the backup job. You can schedule CPS backup jobs to run at specific
times (periodically), as files incur any changes (continuously), or as needed (on
demand).
See “Creating CPS backup jobs” on page 88.
4 As soon as the data is backed up to the Protection Server, scheduled snapshots

of the data are made. The data is then indexed and made available in Backup
Exec Retrieve.
See “Managing snapshots” on page 68.
5 Users retrieve specific files and folders to their workstations by using Backup
Exec Retrieve. Users can select specific versions of their data to be restored.
6 If a system failure occurs at one or more Business Servers, the backed up data
can be quickly restored from the Protection Server to the Business Server.
See “About restoring data with Continuous Protection Server” on page 99.
7 After the data is backed up to the Protection Server, you can back up the data
to Backup Exec to archive the data to tape or disk for long-term storage.
See “Backing up CPS with Backup Exec” on page 133.
8 If a system failure or data loss occurs at a Protection Server, Backup Exec can
quickly restore the data back to the Protection Server or back to a Business
Server.
See “Restoring Continuous Protection Server with Backup Exec” on page 135.
What you can do with Continuous Protection Server
9 The Backup Exec SmartLink component lets you view the status of Continuous
Protection Server backup jobs in the Backup Exec Job Logs and Alerts. This
option lets administrators determine the quality and completion of the
Continuous Protection Server jobs before or during the Backup Exec backup job.
See “Monitoring CPS jobs in Backup Exec” on page 137.
What you can do with Continuous Protection Server

Table 1-2 describes the features and benefits of Continuous Protection Server.
Table 1-2 Features and benefits of Continuous Protection Server
Feature Description
Continuous data CPS backs up files on a network (LAN or WAN) and writes them immediately to a Protection
protection Server with no wait time. You do not need to take incremental or differential backups on
servers that are protected by CPS. This feature keeps productivity high while protecting
the organization’s information.
Byte-level protection Only the changed data is captured and protected. This granular (or byte-level) protection
reduces the amount of data moving across the network, thereby increasing efficiency.
Backup Exec Retrieve Backup Exec Retrieve allows workstation users to find and retrieve the files that were
backed up with CPS, without requiring any assistance from system administrators.
Workstations only require Web browsers to use this feature, so you do not need to install
the Continuous Protection Server software on the users’ workstations.
Full system restore 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 previous
state.
Simultaneous backups Provides multi-streaming, which enables multiple file servers to be continuously backed
up at one time to a single Protection Server.
Administration The Administration Console enables users to define backup destinations, customize jobs,
Console view status, and learn of any issues that arise.
Point-in-time CPS leverages Volume Shadow Copy Service (VSS) snapshots to provide versioning of files.
snapshots This allows users or administrators to recover a previous version of a document. Snapshot
settings provide administrators with greater flexibility in managing and retaining snapshots.
SmartLink to Existing Symantec Backup Exec users can view some CPS activities from within the Backup
Symantec Backup Exec Exec Administration Console. For example, you can view logs for CPS backup jobs. You also
can use Backup Exec to move disk-based backups to tape for long-term storage.
Flexible backup Back up only the specific data you need. Save on system resources by backing up only the
options information that needs to be recovered.
About backup strategies and planning
Table 1-2 Features and benefits of Continuous Protection Server (continued)
Feature Description
Customized backup Back up files on demand, or schedule periodic and continuous backups to run automatically.
schedules
Bandwidth throttling Administrators can set the maximum amount of bandwidth to be used for continuous data
protection jobs.
Open file protection Continuous Protection Server protects open files during continuous protection.
Customized retention Retention properties define how long to keep daily, weekly, and monthly backups on disk.
properties
Auto job resume Automatically resumes a continuous protection job when lost connections are restored
without requiring intervention from an administrator.
Push installation 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 is
installed or taking place.
Discovery Intuitive search capabilities enable users to find files by file name, modification date, specific
file type, or file size.
Scalable protection Information can be backed up from sources in the current network, as well as from new
servers as they are added to the Backup Group.
System State backup Continuous Protection Server captures system state information, reducing the time and
effort to recover server configuration information.
Symantec LiveUpdate Uses Symantec LiveUpdate to provide periodic product updates.
64-bit native support Supports 64-bit native processors for Business and Protection servers.
IPv6 support Supports Internet Protocol 6 (IPv6).
Settings Utility Includes a Settings utility where user-configurable registry settings can be managed.
Continuous protection Supports continuous protection of Microsoft Exchange servers to Backup Exec.
of Exchange

One of the most important assets to any business is the information that is stored
on its computers.
Having a strategic backup plan can save time and money by requiring less time
for reconstructing information in the event of a failure or loss. Continuous
Protection Server can help streamline backup and file recovery strategies.
The main purpose of your backup strategy is to recover and restore information
as quickly as possible after a loss. Secondarily, you need to manage your resources
effectively to save money. A well-designed backup strategy plays a key role in
your ability to restore lost files quickly.
Data protection considerations

Before you install and use CPS, you should consider the following questions to
help 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 warrants
backup 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 irregular
intervals?
■ 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 which
their files are stored?
■ Who should have access to the Continuous Protection Server Administration
Console for the purpose of changing settings, scheduling backups, restoring
information, and managing system alerts?
■ Who should have access to various backup destinations for the purpose of
restoring data?
■ How should the backup destinations be organized for access?
■ How often should data snapshots be captured and how many should be
retained?
About backup job schedules

Perhaps the most important part in developing a strong backup strategy is deciding
what to back up and when.
The frequency with which you back up files can affect many things including the
following:
■ 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 each
organization might use a combination of these practices. Most importantly, all
information on your servers should be backed up on a regular basis. Less-essential
information should be backed up periodically. Pertinent data, such as data that
is 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 88.
See “Changing a backup job schedule” on page 94.
Table 1-3 describes the types of scheduled backup jobs that you can create.
Table 1-3 Types of scheduled backups
Scheduled backup type Description
On demand Files that are manually backed up by a user on an “as needed”

basis.
Regular Files that are backed up on a routine basis. You select the
days 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 would
be to back up all of the Business Servers every Saturday,
beginning at 1:00 A.M.
Periodic Files that are backed up on certain days of the week and run
periodically on timed intervals. For example, you can back
up your sales proposals every hour, your development data
every three hours, your quality assurance data every four
hours, and so on.
Continuous Critical business files, such as customer data, that are backed
up continuously. Every time a file changes, the changes are
copied to the Protection Server. There is no wait time or
preset interval when the information is copied. The backup
takes place immediately, even while files are open.
Where to find more information

The product documentation provides assistance for using Backup Exec Continuous
Protection Server to your advantage. You can access the information that you
need from the installation media 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 24.
See “Accessing the Symantec Backup Exec Web site” on page 24.
Accessing the Continuous Protection Server documentation

The Backup Exec Continuous Protection Server documentation is available on the
product CD and installed with each Administration Console.
Table 1-4 describes the manuals and help that comprise the Continuous Protection
Server documentation set.
Table 1-4 Continuous Protection Server documentation set
Document title Description
Continuous Protection Continuous Protection Server is written for system

Server Administrator’s administrators and delivered in Adobe Acrobat (PDF) format.
Guide
(CPSadmin_XX.pdf)
Continuous Protection The Continuous Protection Server Quick Installation Guide

Server Quick Installation is intended to assist you while installing the product and
Guide components. It is delivered in Adobe Acrobat (PDF) format.
(CPSquick_xx.pdf)
Continuous Protection Installed and stored on the server, the Help file is accessible
Server Help files from the Administration Console.
(CPSconsole_XX.chm)
Continuous Protection An HTML file containing any product changes and

Server Readme files installation issues that should be reviewed before installing
the Continuous Protection Server product.
(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), PT (Brazilian Portuguese) and ZH (Simplified

Chinese).
To access the Continuous Protection Server documentation
1 Insert the installation media.
2 Using Windows Explorer, navigate to and open the Docs directory.
3 Double-click the file to open it.
Accessing the online Help

Online Help is installed with the Continuous Protection Server software.
To access the online Help
1 Install the Continuous Protection Server software.
2 Click Help.
Accessing the Symantec Technical Support Web site

On the Symantec Technical Support Web site, you can find the latest program
updates, patches, online tutorials, Knowledge Base articles, and virus removal
tools.
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 site

On 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
Chapter 2
Installing Continuous
Protection 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 2010
■ Modifying Continuous Protection Server installations
■ Uninstalling the Continuous Protection Server
■ Uninstalling a Continuous Protection Agent
Before you install

You should do the following tasks before you install Continuous Protection Server:
Review the guidelines for installing See “Guidelines for installation” on page 26.
Continuous Protection Server for
information about the order in which
the components should be installed.
26 Installing Continuous Protection Server
Before you install
Run the Environment Check tool to See “Checking your environment before
check for issues that could affect the installation” on page 27.
installation.
If you are upgrading from a previous See “Upgrading to Continuous Protection Server
version, review the product 2010” on page 46.
documentation for any compatibility
issues that could affect the installation.
Review the Readme file for information See “File system filter driver compatibility”
about incompatible products that on page 29.
should be turned off or uninstalled
before you install Continuous
Protection Server.
Review the product documentation for See “Understanding the Continuous Protection
information about setting up the Server service account” on page 29.
service account for Continuous
Protection Server.
Verify that the systems on which you See “System requirements for the product”
want to install Continuous Protection on page 30.
Server and its components meet the
system requirements.
Configure your firewall to allow traffic See “Firewall support ” on page 33.
through the ports that are used by
Continuous Protection Server.
Guidelines for installation

You should install Continuous Protection Server as follows:
■ Install the Continuous Management Service and an Administration Console
before you install other Continuous Protection Server components.
■ You should install the Continuous Management Service and the Administration
Console on a dedicated server if possible.
■ Use the Administration Console to push-install additional Administration
Consoles and Continuous Protection Agents to other Business Servers or
Protection Servers.
See “Push-installing Continuous Protection Server components” on page 43.
■ As necessary, use the Administration Console to install additional components.
Installing Continuous Protection Server 27
Before you install
Checking your environment before installation

The Symantec Backup Exec Environment Check tool lets you assess your existing
hardware and software resources for compatibility with the Continuous Protection
Server software installation.
The Environment Check tool assesses and reports on the following pre-installation
configurations:
■ If the computer meets the minimum requirements for installation, such as the
operating system, disk and memory space, and sufficient logon account
privileges.
See “System requirements for the product” on page 30.
■ If third-party software that uses Continuous Protection Server ports is
configured correctly.
■ If required components are installed, and if they are versions that are
compatible with Continuous Protection Server.
■ If previous versions of Continuous Protection Server are installed.
■ If storage device hardware and associated drivers are properly installed and
recognized 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
Flagged item Result
Passed There are no incompatibilities to prevent the Continuous Protection

Server installation. For hardware, this result indicates that the
hardware configuration is recognized by Continuous Protection Server.
Warning An incompatibility with Continuous Protection Server exists, but can

be resolved. Or, a condition of which you should be aware.
Failed An incompatibility with Continuous Protection Server exists, and the

installation failed. Some action is required before you can successfully
install Continuous Protection Server.
Although the Environment Check runs automatically during installation, you may
want to run it manually before installing Continuous Protection Server or before
backing up data with Continuous Protection Server.
Before you install
To check your environment before installation

1 Insert the installation media, click Pre-installation, and then click Start the
Backup Exec Continuous Protection Server Environment Check.
2 Click Next.
3 Select one of the following:
Local Environment Check Checks the configuration of the local computer
Remote Environment Check Checks the configuration of a remote computer
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 From List.
Select the computer from the list, and then click Next.
■ To add the name of a computer manually, click Add Server Manually.
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 which
the Environment Check will run, select the computer from the list, and
then click Remove.
6 Review the results of the Environment Check, especially those items that
were flagged as Failed or Warning.
To save the results of the Environment Check, check Save Results To.
7 To change the location where the Environment Check results are saved, click
Change Path to browse to a new location.
8 Click Finish.
Continuous Protection Server and Backup Exec compatibility

Be careful when installing the CPS Protection Agent on the servers that have older
versions of Remote Agent installed. The CPS installer can optionally upgrade the
Remote Agent components. However, this upgrade breaks existing backup
functionality if the Backup Exec Media Sever is a 11d or earlier version. The
installer will always alert you before upgrading the Remote Agent. The same
consideration should be given when upgrading Backup Exec if that is where the
Continuous Management Service will run.
Before you install
File system filter driver compatibility

Software that uses file system filter drivers, such as disk defragmenter utilities,
certain open file agents and some virus protection software, cannot be used with
this 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 the
incompatible product could cause the system to become unstable or crash. Likewise,
enabling both products at system start time could prevent the system from
starting. System Restore allows the system to return to its previous configuration.
You must remove incompatible products or make them unavailable before you
install CPS. If CPS is already installed on the system, do not enable or start the
other product while CPS is running.
For more information, see the Readme file accompanying this release for the most
current list of products with incompatible filter drivers.
Understanding the Continuous Protection Server service account

Some CPS services are run in the context of a user account that is configured for
the CPS system services. To specify an account for CPS, enter a name and password
of an Administrator account for the CPS services to use.
The services will not start if the account password has expired. Also, if the services
try to start too many times with an expired password, the user may get locked out
of the account.
If the computer that is hosting the CPS services is in a domain, enter a Domain
user’s account. The CPS installer adds the account to the local Administrator’s
group.
If this computer is in a workgroup, enter an Administrator’s account, or an
equivalent 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 account
or an existing account) will be assigned the following rights:
■ Log on as a service.
■ Administrator rights (provides complete and unrestricted rights to the
computer).
On a computer running Windows Server 2003, you cannot install CPS using a
service account that has a blank password. If you attempt to do so, an error
message is displayed. You can configure Windows to allow for blank passwords.
For more information, see the Windows documentation.
System requirements for the product
The account that is used must be valid on each node in the Backup Group. This
account 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 the
local administrators group of the computer being push installed to.
When operating in a workgroup environment, all nodes in the backup group must
run in non-secure mode. (Pre and post-job scripts run under the service account,
although additional rights may be required.)

To install and use this product, your hardware and software requirements must
meet the minimum requirements for each Continuous Protection Server
component.
Actual production requirements may require greater resources than the noted
minimum requirements. Additionally, where several components exist on the
same server, the requirements are cumulative.
See “System requirements for Business Servers” on page 30.
See “System requirements for Continuous Management Service and Protection
Servers” on page 31.
See “System requirements for Administration Console” on page 32.
See “Firewall support ” on page 33.
System requirements for Business Servers

Business 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.
Table 2-2 System requirements for Business Servers
Component Requirements
Supported Operating This component is supported on the following operating systems:

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 Service
Pack 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 and Windows 2008 R2, including Windows Server
Core
RAM 512 MB, 1 GB recommended
Disk Space: Continuous 25 MB

Protection Server Software
Disk Space: Journals 100 MB (10 GB or more recommended)
Disk Space: Logs and Alerts 100 MB
Disk Space: Named Objects 100 MB or more depending on server configuration (minimum 1 GB recommended
if backing up System State)
UPS Uninterruptible power supply (UPS) such as battery backup power, recommended
Utilities Microsoft Data Access Components (MDAC) version 2.5 or later
System requirements for Continuous Management Service and

Protection Servers
Data is backed up from Business Servers to Protection Servers.
Table 2-3 lists the system requirements for Continuous Management Server and
Protection Servers.
Table 2-3 System requirements for Continuous Management Service and

Protection Servers
Supported Operating The Continuous Management Service and Protection Servers are supported on the
Systems following operating systems:
■ Microsoft Windows Server 2003 x64 Editions

■ Microsoft Windows Server 2003 family (including R2, but not Data Center) with
Service Pack 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 and Windows Server 2008 R2, including Windows
Server Core
RAM 512 MB, 1 GB recommended
Disk Space: Continuous 58 MB

Protection Server Software
Disk Space: Logs and Alerts 100 MB
Disk Space: Indexing 1 GB or more as required

Component
Volumes The Protection Server should have at least four separate volumes for ideal
performance, such as the following:
■ System volume
■ Journals volume
■ Backup destination volume
■ Snapshot storage volume for backup destination
UPS Uninterruptible power supply (UPS) such as battery backup power, recommended
Utilities Microsoft Data Access Components (MDAC) version 2.5 or later
System requirements for Administration Console

Any number of Administration Consoles may be installed in the Backup Group.
Table 2-4 lists the system requirements for the Administration Console.
Table 2-4 System requirements for Administration Console
Supported Operating The Administration Console is supported on the following operating systems:
Systems
■ Microsoft Windows 2000 Professional with Service Pack 4
■ Microsoft Windows 2000 Server with Service Pack 4
■ Microsoft Windows 2000 Advanced Server with Service Pack 4
■ Microsoft Windows Server 2003 family (including R2, but not Data Center) with
Service Pack 1
■ Microsoft Windows XP Professional
■ Microsoft Windows XP Professional x64 Edition
■ Microsoft Windows Vista
■ Microsoft Windows Server 2008 and Windows Server 2008 R2, including Windows
Server Core
■ Microsoft Windows 7 (all versions)
RAM 512 MB, 1GB recommended
Disk Space 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)
Utilities Microsoft Data Access Components (MDAC) version 2.5 or later.
Net Framework 2.0 is installed for Settings Utility, if needed
Firewall support
Firewalls must be configured to allow the following ports through to support
Continuous Protection Server. CPS automatically creates a firewall exception list.
If any of the default port settings are changed on one computer, they must be
changed 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 the
computer.
Table 2-5 lists the default port settings for Continuous Protection Server.
Table 2-5 Default port settings for Continuous Protection Server
Service Name Default Port Number Port Type Editable Registry Key
Network Helper 1804 UDP HKLM\Software\Symantec\ENL\Network.TCPIP

Service (ENL)
CPA Data 20481 TCP HKLM\Software\Symantec\Backup Exec

CPS\Parameters\Communications\FFXport
CPA RPC 20483 TCP HKLM\Software\Symantec\Backup Exec

CPS\Parameters\RPC Interface\RxRsaStaticPort
CMS RPC 20485 TCP HKLM\Software\Symantec\Backup Exec

CPS\Parameters\RPC Interface\RxRmsStaticPort
Additionally, the Continuous Protection Server Services Manager, push-install,

and Settings Utility utilize Windows file sharing (NetBIOS or SMB) ports. In order
for these services to function, you must configure the ports.
Table 2-6 lists the ports that you should not open to the Internet.
Table 2-6 Ports that should not be opened to the Internet
Service Name Default Port Number Port Type Editable Registry Key
Windows 445 TCP No
(NetBIOS over TCP/IP)
Windows 137 UDP No
(NetBIOS 138 UDP
139 TCP
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 (or
recommended) that they be opened through your firewall.
What gets installed and where

After the Continuous Protection Server installation completes, depending on the
Continuous 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 35.
See “Drivers that are installed” on page 36.
See “Continuous Protection Server services that are installed” on page 36.
See “Registry entries” on page 36.
See “Understanding the Continuous Protection Server service account” on page 29.
Folders that are installed

By default, Continuous Protection Server installs files and folders to C:\Program
Files\Symantec\Continuous Protection Server\.
Table 2-7 describes the folders that are installed.
Table 2-7 Folders that are installed
Folder Description
ASA (Adaptive Server The ASA folder contains the Win32 and Charsets folders. The Win32 folder contains the
Anywhere) ASA database engine and its backup files, DBMS service, ASA support files, and ASA query
tool. The database backup (cpsDBBackup.exe) and validation (cpsDBValidate.exe) utilities
are also contained in this folder.
The Charsets folder contains ASA Unicode support files.
Autonomy 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.
Database The Database folder contains the Continuous Management Service (rms.db) and Continuous
Protection Agent (rsa.db) databases, their backup copies, and the related database files.
Drivers The Drivers folder contains the Continuous Protection Server filter driver.
Install The Install folder contains Continuous Protection Server, Remote Agent, and Symantec
LiveUpdate installation files for push installs.
Services The Services folder contains Continuous Protection Server service executable files and
associated support files.
Logs The Logs folder contains the Network Helper (ENL) log and trace logs.
Drivers that are installed

Continuous Protection Server installs the filter driver CpsFsJnl.sys. This driver
detects changes in protected files and records the changes to the Protection Server.
Continuous Protection Server services that are installed

Table 2-8 describes the services that Continuous Protection Server installs.
Table 2-8 Services that are installed
Service name Short name Description
Backup Exec RxRMS The Continuous Management Service service is present only on the server
Continuous Protection hosting the Continuous Management Service. It manages the
Administration Service configuration for all Backup Exec Continuous Protection Agents in the
Backup Group.
Backup Exec RxRSA The Continuous Protection Agent service is present on all servers on
Continuous Protection which the Continuous Protection Agent is installed. It enables Continuous
Agent Protection Server to back up data from the server or move the backed-up
data on the server.
Backup Exec RepBrokerSvc Allows communication between Continuous Protection Server and Backup
Continuous Protection Exec to facilitate continuous protection of Microsoft Exchange transaction
Broker Service logs.
Backup Exec rxWriterSvc Communicates with Volume Shadow Services to save and store the
Continuous Protection Continuous Protection Server’s configuration information.
Configuration Writer
Backup Exec RxASA Controls the configuration database for all Continuous Protection Server
Continuous Protection information.
Database
Backup Exec RxNoService Captures system information and file share information.
System State Manager
Backup Exec ENL Enables the Continuous Management Service to group and discover
Continuous Protection Continuous Protection Agents and communicate with them.
Network Helper (ENL)
Registry entries
Continuous Protection Server adds the following registry keys:
■ HKLM\SOFTWARE\Symantec\Backup Exec CPS
Performing an initial installation
This location stores information about the journal directories, Continuous

Protection Server installation path, Continuous Management Service database
installation directory, Continuous Protection Server parameters, and
Continuous Protection Server build details.
■ HKLM\SYSTEM\CurrentControlSet\Services\
This location stores information about the Continuous Protection Server
database technology (Adaptive Server Anywhere, version 9), file system filter
driver, file system journal writer driver, and the file system recognizer driver
configuration.
Registry entries can be changed using the Settings Utility.
See “Accessing the Settings Utility” on page 74.

A typical and fully functional Continuous Protection Server Backup Group includes
the following components:
■ A server that has the Continuous Management Service, the Continuous
Protection Agent, and the Administration Console installed. This server
becomes the central management point in the Backup Group.
■ A Continuous Protection Agent on each Business and Protection Server with
the Indexing Component installed on each Protection Server.
■ Any number of Administration Consoles.
Note: The Continuous Management Service components can be installed on a

Backup Exec server or on a stand-alone server. If Continuous Protection Server
is installed on Backup Exec, then that Backup Exec installation must be upgraded
to Backup Exec 2010. If Continuous Protection Server is installed on a stand-alone
server, then the latest version of the Remote Agent is also installed. A Remote
Agent is not installed on Backup Exec.
The first step in creating a fully functional environment is configuring the server
that hosts the Continuous Management Service. Establishing the Continuous
Management Service is usually accomplished by performing an initial installation
from the installation media.
Continuous Protection Server application files that should be installed during the
initial installation include the Continuous Management Service and an
Administration Console. If the server hosting the Continuous Management Service
will also be a Business or Protection Server, a Continuous Protection Agent must
also be installed. Backup Exec Retrieve is also installed. The Remote Agent is
installed optionally 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 installation media and push
installation. Alternatively, firewalls can be turned off during the installation
process.
To use the versioning capabilities of Backup Exec Retrieve, Protection Servers
must be running Windows Server 2003.
See “System requirements for Continuous Management Service and Protection
Servers” on page 31.
Note: After installing Continuous Protection Server on a computer running

Windows Server 2003, you might receive an error message that the Network Load
Balancing Service failed to start. Microsoft reports the cause as: “Although network
Load Balancing (NLB) is not currently installed, some NLB registry keys might be
present in the registry.” Although Microsoft Knowledge Base Article 268437
describes the problem as applying to Windows 2000 Advanced Server, the fix also
works 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 being
installed when performing a 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 the -ROM
is inserted in the drive. If Autoplay is not enabled, double-click browser.exe
file from the -ROM or download directory.
3 Select the language, and then click OK.
4 The welcome screen for Backup Exec Continuous Protection Server provides
links to access various areas of the installation . After reviewing the various
product information, click Pre-installation.
5 Click Start the Backup Exec Continuous Protection Server Environment
Check, 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 a
successful installation of Continuous Protection Server, click Finish.
■ If the Environment Check reveals issues that may prevent a successful
installation of Continuous Protection Server, correct the issues before
attempting to install again.
8 Select Start the Backup Exec Continuous Protection Server Installation to

install Continuous Protection Server, and then click Next.
Continuous Protection Server will determine whether the computer is a 32-bit
or 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, and
then click Next.
11 Select one of the following methods to enter license keys, and then click Next.
To enter license keys manually In the License Key box, type the license key
number, and then click Add. Repeat this step
for each license key for each option or agent
you want to add.
To import license keys from a file Click Import, and then select the
cpssernum.xml file.
To install an evaluation version Leave the license key field blank, and then
continue with step 14.
The license keys you entered are saved to the cpssernum.xml file, located in
the Windows or WINNT directory.
12 On the Local Features screen, select the Continuous Protection Server

components that you want to install, and then click Next.
Administration Console Check to install an Administration Console that allows for the management
and monitoring of activities within the Backup Group. This option will also
install Symantec LiveUpdate 3.0.
Settings Utility Check to install the Continuous Protection Server Settings Utility, which
allows changes to be made to various registry settings on this computer.
If it is not already installed, this option will also install .Net Framework
2.0.
Push install Support Check this option to install the files needed to push install other
components.
x86 Support to install components needed to push-install to 32-bit

computers.
x64 Support to install components needed to push-install to 64-bit

computers.
Continuous Management Service Check to install a Continuous Management Service, which must be installed
to create and manage the Backup Group.
Only one Continuous Management Service may be installed in each Backup

Group, and it must be installed before other Continuous Protection Server
components.
The CMS must have a fixed IP address. If the IP address changes while the
CMS is running, the CMS and the Network Helper (ENL) service must be
restarted (for example, net stop RxRMS, net stop Network Helper, net start
RxRMS).
Additionally, if protection agents exist on subnets different from the CMS,

the CMS should be registered with the Domain Name Service (DNS).
Continuous Protection Agent Check this option to install a Continuous Protection Agent on the computer.
A Continuous Protection Agent must be installed on all computers that will

act as Business Servers or Protection Servers.
Indexing Component Check this option to allow files stored on this server to be indexed and
searchable.
Backup Exec Remote Agent for Check this option to perform an install of the Remote Agent on the local
Windows Systems computer.
Exchange Protection Agent Check this option to allow for continuous protection of Microsoft Exchange
Servers.
An Exchange Protection Agent with the Continuous Management Service

and a Continuous Protection Agent must be installed on the Backup Exec
media server.
An Exchange Protection Agent must be installed with the Remote Agent

and a Continuous Protection Agent on the Microsoft Exchange system.
If you cannot select this option, check your DNS for proper settings.
13 On the Backup Group screen, enter a name of the Backup Group and the name
of the Continuous Management Service, and then click Next.
When you click Next, you may be prompted with a Windows Security Alert
screen with options of Keep Blocking, Unblock, or Ask Me Later. This security
screen is displayed due to the installer looking for an existing Continuous
Management Service that already has the specified Backup Group name
registered. Select Unblock to continue.
14 On the Services screen, enter the credentials for the Backup Exec Continuous
Protection Server Service Account, including user name, password and
domain.
15 Click Next.
16 If a Continuous Management Service was selected for this installation and
the Continuous Management Service server has multiple NIC cards, the
Network Interface Selection screen is shown. Select the Network interface
to 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 the
directories, and then click Next.
System Cache Directory Select or browse to the directory where

Continuous Protection Server can store
System Information (System State and
Shadow Copy Components) data to be backed
up. The System Cache is a holding area for
the system information and share
information.
At a minimum, System information requires

at least 5 GB of disk space. If the server
performs additional roles, such as also acting
as a domain controller, more space is
required.
Journal Directory Select the default journal directory or browse

to another directory to hold the backup
journals. The Journal Folders contain the
dynamic changes of the data that occur
during continuous backups.
Indexing Directory Select the default directory or browse to

another directory to hold the indexing
database. The indexing component holds
indexes of the snapshots that are captured
on the Protection Server.
You should install these directories on separate volumes.

19 On the Ready to Install the Program screen, review the selections, and then
click Install.
20 Following the Continuous Protection Server installation, you are prompted
to restart the computer. Click Yes to complete the installation.
If a Continuous Protection Agent was installed, you must restart the server
after the initial installation. The restart ensures that the filter driver is
correctly installed and ensures proper detection of all open files. If you use
the Microsoft Shutdown Event Tracker, you must restart the server manually
after installation.
Viewing installation logs

For installation troubleshooting purposes, you can view the installation logs in
%allusersprofile%\application data\symantec\Backup Exec CPS\logs. On
computers that run Windows Server 2008 and Windows Server 2008 R2, the
Push-installing Continuous Protection Server components
installation logs are located in %allusersprofile%\symantec\Backup Exec CPS\logs.

The file name is Cpsinst.log
Push-installing Continuous Protection Server

components
After you perform the initial installation, use the CPS Administration Console to
install additional components remotely. Components that may be push-installed
consist of additional Administration Consoles, Continuous Protection Agents, or
both. Any number of Consoles can be installed in the Backup Group, and a
Continuous Protection Agent must be installed on each Business Server and
Protection Server.
If CMS is installed on a computer that runs Windows Server 2008 or Windows
Server 2008 R2, you can push-install the CPA and the Administration Console
components to computers that run various operating systems.
Note: You cannot protect a Business Server that runs Windows Server 2008 with
a Protection Server that runs Windows Server 2003. This configuration results
in loss of data.
Table 2-9 lists the operating systems to which you can push-install CPS
components if CMS is installed on a computer that runs Windows Server 2008.
Table 2-9 Components you can push-install from Windows Server 2008 and
Windows Server 2008 R2
Operating system CPS component
Windows Server 2008 and Windows Server CPA or the Administration Console. You
2008 R2 cannot install the Administration Console
on a computer that runs the Windows Server
Core installation option of Windows Server
2008.
Windows Server 2003 CPA or the Administration Console
Windows 2000 Server CPA or the Administration Console
Windows Vista Administration Console
Windows XP Administration Console
Windows 7 Administration Console

If CMS is installed on a computer that runs Windows Server 2003, you can
push-install the CPA and the Administration Console components to computers
that run various operating systems.
Table 2-10 lists the operating systems to which you can push-install CPS
components if CMS is installed on a computer that runs Windows Server 2003.
Table 2-10 Components you can push-install from Windows Server 2003
Operating system CPS component
Windows Server 2003 CPA or the Administration Console
Windows 2000 Server CPA or the Administration Console
Windows Vista Administration Console
Windows XP Administration Console
Windows Server 2008 and Windows Server Administration Console

2008 R2
Windows 7 Administration Console
Firewalls need to be manually reconfigured for installation from media and

push-installation. Alternatively, firewalls can be turned off during the installation
process.
Administrator rights are required when push installing components to remote
computers, as well as backup rights to the computer hosting the Continuous
Management 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 the
local administrators group of the computer being push installed to.
1 On the Windows taskbar, click Start > Programs > Symantec > Backup Exec
CPS > Backup Exec CPS Console.
2 On the navigation bar, click Setup.
3 On the task pane, under Server Tasks, click Push install CPS components
using wizard.
4 Review the introduction on the Welcome to the Push Install CPS Components
Wizard screen, and then click Next.
5 On the Select a Computer screen, type or browse to the name of the computer
on which to install the components. Alternatively, type the IP address for the
computer.
If the computer to which the components are installed is located on a different
subnet, naming services such as Dynamic Name Service (DNS) or Windows
Internet Naming Service (WINS) must be established across the routes for
proper 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 components
should be installed in separate volumes from one another. The Journal Folder,
Indexing Component, Backup Destination, and System volume should all be
in separate volumes.
8 Click Next.
9 Enter the Credentials for the Backup Exec CPS Service Account, including
user 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 the
directory 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 information
and 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 or
browse to another directory to hold the backup journals.
The Journal Folders contain the dynamic changes that occur during
continuous backups.
14 Click Next.
15 On the Select Indexing Database Path screen, select the default directory or
browse to another directory to hold the indexing database.
The indexing component holds indexes of the snapshots that are captured
on the Protection Server.
Upgrading to Continuous Protection Server 2010
16 Click Next.
17 Type or browse to the installation path on the remote computer where the
services will be installed.
Installation must occur on one of the drives that are shown in the drop-down
list 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 the
installation to complete. Select Restart the computer if required for this to
occur automatically at the end of the installation. If not, the system must be
manually 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, click
Finish to begin the installation. A screen appears showing the installation
progress.
22 Verify that the Protection Agent was properly installed by noting that the
Business Server shows in the server list on the Servers tab. This step may
take some time due to the configuration and system restart.
The server you add to the Continuous Protection Server Backup Group must
be restarted. If you use Microsoft’s Shutdown Event Tracker, you must restart
the server manually after installation.
Upgrading to Continuous Protection Server 2010

The Continuous Protection Server (CPS) installer upgrades CPS 12 and CPS 12.5
to CPS 2010.
You can upgrade only portions of the CPS products or run CPS 2010 concurrently
with CPS 12.5 or CPS 12.
You can perform a rolling upgrade. A rolling upgrade allows you to upgrade servers
in a backup group one at a time. You can protect all servers in a backup group
during the upgrade process, even though different servers may use different
versions of Backup Exec.
After CPS 2010 is installed on the Protection Server server, you can use the
Administration Console on that Protection Server to install or update Continuous
Protection Agents and Consoles on remote business servers.
Modifying Continuous Protection Server installations
Note: When upgrading a CPS database, all job schedules are disabled to allow
Continuous Protection Agents to be upgraded before the Continuous Management
Service attempts to start the scheduled jobs. As soon as the Continuous Protection
Agents are upgraded, the job schedules must be re-enabled from the Console.
To upgrade to Continuous Protection Server 2010

1 Before performing the upgrade, close all other programs that may be running.
2 Insert the Continuous Protection Server installation media into the drive.
If AutoPlay is not enabled, navigate the installation media and double-click
browser.exe.
If an earlier version of Continuous Protection Server is detected (version 11.x
or 10.x), a prompt appears noting that the earlier version must be manually
uninstalled before Continuous Protection Server 2010 can be installed.
3 Click Update to continue.
4 If you are upgrading a Continuous Protection Agent, when prompted, enter
the license keys for CPS and then click Next to continue.
The installation wizard detects which earlier components are already installed
on that server, and then updates them to Continuous Protection Server 2010.
Modifying Continuous Protection Server installations

Use the Push-installation option for Continuous Protection Server Administration
Consoles or Continuous Protection Agents to reinstall components.
To detect and repair Continuous Protection Server component problems, rerun
browser.exe, or use the Change option of the Add and Remove Programs control
panel in Windows.
Uninstalling the Continuous Protection Server

Uninstalling Continuous Protection Server removes all components that were
installed as part of the Complete installation. These components include the
Administration Console, Continuous Management Service, and Continuous
Protection Agents.
Symantec LiveUpdate is uninstalled automatically if you do not have other
Symantec 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 other
applications, you can uninstall them manually.
Uninstalling a Continuous Protection Agent
To uninstall the Continuous Protection Server

1 On the Windows Start menu, click Control Panel.
2 Click Add or Remove Programs.
3 In the Currently Installed Programs list, select Continuous Protection Server.
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 associated
with Backup Exec Continuous Protection Server, which includes Continuous
Management Service or Continuous Protection Agent databases, data stored
within backup destinations, and the local data cache. Backup Exec Retrieve
must be uninstalled separately.
Click Yes to all removal of all data, or click No to remove the data manually
after 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.

Before uninstalling a Continuous Protection Agent, consider the following:
■ Snapshots cannot be deleted after a Protection Server is uninstalled. Before
uninstalling a Protection Server, you need to delete all snapshots.
See “Deleting snapshots” on page 73.
■ After the Protection Server is uninstalled, snapshots must be manually deleted.
■ If a Business Server or Protection Server is being removed from a Backup
Group, you must first uninstall the software from the server, and then the
server can be removed from the Backup Group.
■ If the Continuous Protection Agent is uninstalled, the user will be prompted
to 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 or Remove Programs.
3 In the Currently Installed Programs list, select Continuous Protection Server.
4 Click Remove.
5 Click Yes to confirm that you want to remove the program.
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 Delete
Unavailable Server.
The data that is located on the backup destination and all the snapshots are
not removed during the uninstall process. Snapshots should be deleted
manually before uninstalling the CPA. If the CPA is uninstalled, the user will
be prompted to reboot after the uninstall is completed.
Chapter 3
Using the Administration
Console
■ 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 Server

Administration 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
52 Using the Administration Console
Starting the Continuous Protection Server Administration Console
Starting the Continuous Protection Server

Administration Console
The Administration Console is the centralized point of management for all
Continuous Protection Server activities. Administrator rights are required on the
system 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 > Backup Exec
CPS.
2 Click Backup Exec CPS Console.
You can add the option to the Start menu and access it from there. Right-click
Backup Exec CPS Console, and then click Pin to Start menu.
About the general Administration Console features

The 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 Console

features
Feature Description
Menu bar You can access Continuous Protection Server features by using
the menu bar that appears across the top of the Administration
Console window. All features, menu options, wizards, and online
help can be accessed by using navigation buttons and links in the
Console. However, the menu bar offers a traditional approach to
using the program’s features. Some options are available only
after an item is selected.
Navigation bar The navigation bar groups together common that tasks you can
perform. It appears under the menu bar across the top of the
Administration Console window. The navigation bar buttons
always appear in the same place and in the same order.
Task pane The contents of the task pane change based on the view that you
select from the navigation bar. A list of tasks you can perform at
any given time appears on the left side of the Administration
Console window. Using the View menu, you can show or hide the
task pane at any time. Using the arrow, you can show or hide task
groupings within the task pane at any time as well.
Using the Administration Console 53
About the Administration Console views
Table 3-1 General Continuous Protection Server Administration Console

features (continued)
Feature Description
Selection pane You can select the item that you want to work with from the
selection pane. After the item is selected, all associated features
are enabled. The selection pane appears to the right of the task
pane. However, if you hide the task pane, the selection pane
appears on the left side of the Administration Console window.
Preview pane In the Preview pane in the bottom-right corner of the window,
detailed information appears about the items that are selected in
the results pane. You can show or hide the Preview pane by using
the View menu or by dragging the divider to a new position.
Status bar The status bar provides computer processing information about
the task that is being performed. It appears across the bottom of
the Administration Console window. You can show or hide the
status bar at any time by using the View menu.

Continuous Protection Server groups similar tasks together by using a variety of
built-in Console views. When you select a view from the navigation bar, related
tasks appear in the task pane. Changing views enables you to selectively access
the various Continuous Protection Server features.
Overview view
You can access the Getting Started, CPS Assistant, or System Summary views
from the Overview view.
Table 3-2 describes the different views that are available in Overview.
Table 3-2 Views available in Overview
View Description
Getting Started view This view provides information about the processes required to
set up and use Continuous Protection Server. The Getting Started
view also provides links to alerts and notifications, and product
updates and patches.
Table 3-2 Views available in Overview (continued)
View Description
Continuous Protection This view provides links to information about the setup, use, and
Server Assistant view support of Continuous Protection Server.
The information desk provides links to a variety of information
such as the following:
■ Documentation, getting started, configuration and Continuous

Protection Server wizards.
■ Continuous Protection Server Technical Support Web sites
and Knowledge Base.
■ Symantec learning tools and sites.
System Summary view This view displays information about backup jobs, Continuous
Protection Server alerts, and backup servers. This view also
enables you to get a comprehensive summary of your Backup
Group and backup jobs.
Setup view
The Setup view lets you perform many of the functions of Continuous Protection
Server, including setting up servers, backup destinations, and backup jobs. You
can also create and view snapshots in this view.
Table 3-3 describes the common tasks that are available in the task pane of the
Setup view.
Table 3-3 Task pane options in the Setup view
Task name Description
Push install CPS Allows you to push-install additional Continuous Protection

components using Agents, Continuous Protection Server Administration Consoles,
wizard or both.
New backup Allows you to configure servers within the Backup Group to be
destination the Protection Servers of backup jobs.
New backup Allows you to use the Backup Destination Wizard to designate
destination using servers within the Backup Group as Protection Servers for backup
wizard jobs.
View snapshots Allows you to view the snapshot history for a given backup
destination by launching the Backup Destination Properties
window. This option is only available if a specific Backup
Destination is selected in the results pane.
Table 3-3 Task pane options in the Setup view (continued)
Task name Description
Create snapshot now Allows you to create snapshots for the selected backup
destinations. This option is only available if a specific Backup
Destination is selected in the results pane.
New backup job Allows you to create a new backup job manually.
New backup job using Allows you to create a new backup job by using the New Backup
wizard Job Wizard.
Viewing properties in the Setup view

You can view or change properties for servers, backup destinations, and backup
jobs. Each of these tasks has one or more associated properties windows that allow
you 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
Area Feature Description
Settings General Provides specific information on the server, including

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

of the server, including volume name (drive), file
system type, total capacity, and free space.
Advanced Provides a check box to remove server logs after a

designated number of days.
License Keys Provides the license key information for the selected
server, including the type, the actual license key, and
the days remaining for evaluation and demonstration
keys. A text box is included to enter a new license key.
History Server Log Provides a log of activity for the specified server. The
log can be filtered to show entries for the last 24
hours, last 7 days, or all entries. The server history
log shows the date/time and description of each log
entry.
Table 3-5 describes the backup destination properties.

Table 3-5 Backup destination properties
Settings General Provides information on the backup destination,

including backup destination name, description,
server name, and path.
Snapshot Schedule Provides the schedule when snapshots are taken. The
schedule allows specific days of the week and snapshot
frequency to be specified.
Retention Policy Allows the retention of snapshots to be set. The

retention policy defines how long snapshots are
retained. For example, snapshots are retained for a
given number of hours, and a specified number
retained per day, per week, or per month.
History Snapshots Provides a list of snapshots for the specified backup

destination, including the date, age, and Indexing
State of each snapshot. Buttons are also included to
create a new snapshot or to delete one of the existing
snapshots on the destination.
Table 3-6 describes the backup job properties.
Table 3-6 Backup job properties
Settings General Provides specific information on the backup job,

including backup job name, description, and
Protection Server details.
Backup Allows you to select the specific backup server,

Selections volumes, and System Information to be backed up.
Schedule 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.
Bandwidth Allows you to add or modify the bandwidth limitation

for a specified job. This screen allows you to specify
the Business Server, and the bandwidth usage for a
selected network connection.
Table 3-6 Backup job properties (continued)
Commands Allows you to specify a command script to be run

before or after the backup job. You may enter or
browse to the script. A limiting feature allows the
script to be cancelled if not completed after a specified
amount of time (minutes). A check box allows you to
enable the script asynchronously with the backup job.
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 properties
pane.
Restore view
The Restore view lets you search for or select files to restore and is the best way
to restore large sets of files. You can filter the list of files by specific points in time
or view all versions of backed up files. If a small number of files need to be restored,
use Backup Exec Retrieve.
Job Monitor view

The Job Monitor view lets you view current jobs, job properties, and job history.
You can also view information about source and destination pairs that are
synchronized during the backup process.
You can monitor the job pairs for the Continuous Protection Server job by selecting
Monitor job pairs from the Task pane.
See “About the Job Monitor” on page 121.
Alerts view
The Alerts view lets you respond to notification about the status of the Continuous
Protection Server jobs on all servers. In the event that a job does not run
successfully, you can read a message that alerts you to the problem encountered.
Various levels of errors, warnings, and information are built into Continuous
Protection Server to enable you to manage your backup jobs successfully.
Selecting Properties for the Alerts view provides detailed information on the
selected alerts.
Chapter 4
Configuring Continuous
Protection 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 Servers

You 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 backup
process. Business Servers may be configured when the Continuous Protection
Agent is installed, when your Backup Group changes, or when resources are
reallocated.
To configure Business Servers
3 In the results pane, right-click the server, and then click Properties.
4 Under Settings, click Advanced.
60 Configuring Continuous Protection Server
5 Check Remove log records after (days) to define the number of days to save
the backup records.
6 Specify the number of days to keep the records.
7 Under Settings, click License Keys, and then define the options you want.
Server license keys License key of installed Continuous Protection Server

software, including demonstration licenses and permanent
licenses. To delete a license key (such as an evaluation
license key), select the license key, and then click Remove.
New license key New Continuous Protection Server software license

number. To add a new license, such as when upgrading to
a permanent license, type the new software license number,
and then click Add.
8 Under History, click Server Log, and then define the options you want.
Save As Save the log to a file.
Show entries Narrows the list of server log entries to the following:
■ All Entries
■ Last 7 Days
■ Last 24 Hours
Time Date and time the log record was written. The time is
converted to your local time for display purposes.
Description Information about the server log entry or a note for the
administrator, such as the number of days remaining in a
license period.
9 Click OK.
Reviewing the general properties of a Business Server

You can review various general properties of a Business Server.
Table 4-1 describes the general properties that are available.
Configuring Continuous Protection Server 61
Table 4-1 General properties of a Business Server
General property Description
Server The server’s name, which comes from the system information
on the computer.
Status The server’s status (online, offline, or unavailable).
IP address The Internet Protocol (IP) address that is used by CPS when
communicating with this computer.
Domain Directory location of the computers in this network.
Operating system The operating system that is installed on this computer.
Version The build number of the Continuous Protection Server software

that is installed on this computer.
Installed Components Indicates whether a CMS, CPA, or both are installed on this
computer.
Time Zone Indicates the international time zone where this computer is
located.
Ports in use Indicates the ports that this server is currently using.
To review the general properties of a Business Server

4 Under Settings, click General.
Reviewing the volume properties of a Business Server

You 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
Volume property Description
Name The Name of the Windows NT volume on this server where

backup files from a Business Server are stored.
Moving of servers between Backup Groups
Table 4-2 Volume properties of a Business Server (continued)
Volume property Description
File System The file system that is used when formatting the volume (usually
NTFS).
Total Capacity The number of bytes of disk space that are associated with the
server.
Free Space The number of bytes of disk space that are currently available
for use on the server.
To review the volume properties of a Business Server

4 Under Settings, click Volume.
Moving of servers between Backup Groups

In some cases, one or more Business or Protection Servers may need to be moved
to a different Backup Group. This condition may occur if an existing Backup Group
has become too large and the amount of data being protected is excessive for the
network 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 Management
Service (CMS) using the Complete or Custom installation procedures.
When a new Backup Group is created, it must have a unique name and unique
CMS. Each Backup Group can only have one CMS. After a new Backup Group has
been created, the Business Servers and Protection Servers can be migrated to the
new group.
When a server has been moved to a different Backup group, all jobs involving that
server must be recreated.
Note: You can move a Business Server that runs on Windows Server 2008 (or
Windows Server 2008 R2) to a backup group that runs on Windows Server 2008
(or Windows Server 2008 R2) only.
Managing the Continuous Protection Server Services
To move servers between Backup Groups

3 In the results pane, right-click the server name that you want to move, and
then click Change Management Server.
4 On the Choose Change Management Server dialog box, type the name of the
new 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 rules
that are associated with the old CMS.
5 When you are prompted to verify that you want to change the CMS, click Yes
to proceed or click No to cancel the operation.
If you clicked Yes, the Administration Console that is still connected to the
original CMS deletes all jobs that were involved with the server. If the job
deletions were not successful, a message box notes the failure.

The Service Manager is a CPS utility that lets you start and stop the CPS services
and change the Service Account credentials on the protected server.
Stopping or starting Continuous Protection Server services

You 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:
Start all services Starts all CPS services for the selected server
Stop all services Stops all CPS services for the selected server
Restart all services Stops all CPS services and then restart the services for the
selected server
Refresh Refreshes this dialog box

Adding or removing servers from the Service Manager

You 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 that
contains the server list.
■ To remove a server, select one or more servers from the server list, and
then click Remove Servers.
Changing service account credentials

You can edit service account credentials on the protected server. Every node in
the Backup Group must be running in the same mode.
See “Resetting the standard logon” on page 156.
To change service account credentials
2 Click Services credentials.
3 In the Security Mode list box, select one of the following modes.
Domain mode The user account must be a domain account that is

recognized by every node that participates in backup. The
account must be a member of the local administrator's
group on the computer running the services. Symantec
strongly recommends that customers use Domain mode,
which is more secure than Workgroup mode. The user must
have administrative credentials to run the CPS services.
Workgroup mode A user account is not required to run in Workgroup mode.

Workgroup mode may be necessary for customers who are
running outside of a Domain.
Managing backup destinations

Continuous Protection Server lets you back up data to a specific location on a
specific Protection Server. This server and location are referred to as the backup
destination. Before you can create backup jobs, you need to create one or more
backup destinations where the backed up files are stored. The backup destination
designates a specific Protection Server and volume where the data is stored.
Create a backup destination naming strategy that makes it easy to determine what
kind of content is in each location. For example, if you plan to store marketing
proposals, you might create a destination such as Marketing. If you have marketing
departments in different locations, create a destination for each location by adding
a prefix to the department name. For example, a destination for the West Coast
Marketing department could be WCMarketing.
There are additional details for managing backup destinations such as the
following:
■ Permissions for backup destination folders or permissions on objects within
a 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 should
be performed by a user with Administrator rights.
Additionally, Administrators may not be able to delete the folder tree when
deleting backup destinations. In this case, local ownership must be assigned
to the Domain Admin on the files and all related subfolders if they originate
from another local system.
■ CPS cannot be used to back up a Protection Server's data to a backup destination
on the same Protection Server.
■ Backup destinations can only be created on servers that run Windows Server
2003/2008/2008 R2 operating systems and have a Continuous Protection Agent
(CPA) installed. In addition, only one backup destination is allowed for each
logical volume or drive letter.
■ Symantec recommends that CPS backup destinations be created on volumes
separate from the Backup Exec backup-to-disk volumes to prevent redundant
use of storage.
Adding a backup destination

You need at least one backup destination before you can start backing up
information from your sources.
See “Defining a retention policy for a snapshot” on page 71.
See “Creating a snapshot schedule” on page 70.
To add a backup destination

2 In the task pane, under Backup Destination Tasks, click New backup
destination.
3 Define the appropriate options.
Backup destination name Abbreviated name of this backup destination.
For example: SLOMKT1.
Description Full name or brief description of this backup

destination.
For example: San Luis Obispo Marketing

Presentations.
Server Name of the server on which the backup destination

resides. Leave the default server or select from a
list of servers in the Backup Group.
The server cannot be changed after the backup

destination is saved.
Path Location on the Protection Server where you want

the backup files to be stored. Type or browse to the
location of the backup destination in the Backup
Group.
The path cannot be changed after the backup

destination is saved.
4 Click OK.
Configuring a backup destination for Shadow Storage

You may want to configure a specific backup destination for Shadow Storage,
which is the location where changed bytes between snapshots are stored. For
optimal performance, Shadow Storage should be on a separate volume from your
data backup destination.
To configure a backup destination for Shadow Storage
1 Using Windows Explorer or My Computer, navigate to the drive containing
the backup destination. For example, “E:\”.
2 Right-click the drive, and then click Properties.
3 Click the Shadow Copies tab.
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 be
located.
For example, select “F:\”.
7 Optionally, you can modify the Maximum size of the storage area to
accommodate its intended use.
8 Click OK twice.
Renaming backup destinations

If your naming convention changes, or you made a typographical error in a
destination 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 Backup Destinations.
3 In the results pane, right-click the backup destination, and then click
Properties.
4 Edit the appropriate options.
Backup destination name Abbreviated name of this backup destination.
For example, WCMKT1.
Description Full name or brief description of this backup

destination.
For example, West Coast Marketing Presentations.
5 Click OK.
Deleting backup destinations

You might want to delete a backup destination to retire a server or change the
architecture of your Backup Group. When you delete a backup destination, it is
removed from Continuous Protection Server. However, the backup destination
folder and files remain on the server.
Managing snapshots
All backup jobs that are assigned to the destination must be deleted before deleting
the backup destination.
Additionally, although the backup destination directory and files remain on the
server, the CPS restore tools will not retrieve the data from these files. Neither
CPS restore jobs nor Backup Exec Retrieve can access a backup destination after
it has been deleted.
After a Protection Server is uninstalled, you must manually delete the data that
is contained in the backup destination. Be sure to note the location of the backup
destination 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.
Delete all snapshots associated with Deletes all snapshots automatically when the
this Backup Destination backup destination is deleted.
Open backup destination folder in Opens Windows Explorer so that data may be
explorer view deleted manually.
To manually delete the data, you must have

adequate permissions. Refer to Microsoft
Windows security help.
5 Click OK to delete the backup destination.
Managing snapshots
A snapshot is a consistent, point-in-time image of the contents of the backup
destination.
Note: Because snapshots are volume-based, any changes on the volume are
captured in the snapshot, including the CPS data. Therefore, to achieve maximum
performance, you should create a volume that contains only a backup destination.
Continuous backup jobs use a filter driver to capture changed bytes in the data
files on the source and move the changed bytes to the backup destination whenever
Managing snapshots
the information changes. CPS takes snapshots of the backup destination at

scheduled intervals.
Administrators schedule snapshots based on the importance of the data being
backed up. Users can then select the specific versions of files to retrieve. The
latest files on the backup destination can also be restored, although the latest
version might not have been captured in a snapshot.
Administrators define retention policies to save snapshots for specific periods of
time. When the snapshot expires, it is removed automatically. If the destination
reaches the limit of its disk space, the oldest snapshot is overwritten by new
snapshots. In addition, a history of the snapshots can be viewed and unnecessary
snapshots can be manually deleted from within the CPS Administration Console.
However, when snapshots are deleted, the disk space may not be immediately
freed.
Additional details about managing snapshots include the following:
■ Snapshots can be stored up to a limit that is determined by the underlying
snapshot technology. This limit may vary considerably if alternative snapshot
providers are installed.
■ Snapshots that are scheduled to be taken over a period of time where the end
time is earlier than the start time, may continue to be taken until the end time
on the next day. For example, snapshots that are scheduled to run every 1 hour
beginning at 8:00 a.m. and ending at 7:00 a.m. on Thursday, may result in
snapshots being created until Friday at 7:00 a.m.
■ When backing up data from a single Business Server to multiple backup
destinations, the snapshot schedules should be consistent so that all files that
are protected by CPS are included in the snapshots.
■ When scheduling snapshots, the minutes and seconds that are specified for
the 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 131.
Creating snapshots on demand

Snapshots can be created on demand (manually started by the user) or by a
schedule. Snapshot schedules are defined when the backup destination is created,
and can be modified as needed.
To create snapshots on demand
Managing snapshots
3 In the results pane, select the backup destination.

4 In the task pane, under Backup Destination Tasks, click Create snapshot now.
5 Click Yes to confirm that you want to create the snapshot.
Creating a snapshot schedule

Snapshots can be scheduled to run on a specific schedule or periodically at timed
intervals. The files available for restore display from the snapshots. To ensure
the files are available with minimal delay, snapshots should be captured as
frequently 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 backup
destinations, the snapshot schedules should be consistent so that all files that are
protected 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, should
always be backed up to the same backup destination.
To create a snapshot schedule
Properties.
4 In the Properties pane, under Snapshot, click Schedule.
5 Select one of the following snapshot schedule options:
Run on these days Select the check box next to each day that you want the
snapshot to occur.
Run only at Select and define a specific time for the snapshot to occur.
Run Select and define the intervals at which the snapshot

occurs.
Snapshot schedules are always shown in the local time of the user who is
creating the snapshot schedule. If snapshot schedules are created for servers
that are located in other time zones, the specified time must be converted to
your local time.
6 Click OK.
Managing snapshots
Editing a snapshot schedule

Snapshot schedules can be modified to meet your backup and restore needs. You
can change snapshot schedules to include any day of the week. You can also run
the 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.
Properties.
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 snapshot

Backup snapshots are saved on the Protection Server for 24 hours unless you
specify otherwise. You have the option to set the frequency that snapshots are
purged. A copy of the snapshots can be saved on an hourly, daily, weekly, and
monthly basis.
To define a retention policy for a snapshot
Properties.
4 In the Properties pane, under Snapshot, click Retention Policy.
Managing snapshots
Keep each snapshot for The minimum duration that each snapshot is
retained.
and one daily for Retain a daily snapshot for this period of time. The
daily retained snapshot is the last snapshot of the
day.
and one weekly for Retain a weekly snapshot for this period of time. The
weekly retained snapshot is the last daily snapshot
on the last day of the week.
and one monthly for Retain a monthly snapshot for this period of time.
The monthly retained snapshot is the last daily
snapshot of the last day of the month.
If the volume becomes full, the operating system will delete snapshots.
6 Click OK.
Viewing snapshot history

You can view certain historical information about the snapshots that are retained
on disk. The snapshot history includes the date snapshots were created and their
age.
If you select Show deleted snapshots, two additional columns are added to the
snapshot listings: the date deleted and the reason the snapshot was deleted.
To view snapshot history
Properties.
4 In the Properties pane, under History, click Snapshots.
Policy The snapshot retention policy expired and the snapshot was
automatically deleted.
Manual The snapshot was manually deleted by a user.
External If the system is running out of disk space, the system might
automatically delete snapshots to free up space.
Managing snapshots
States of snapshot indexing

Each 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. The
indexing state provides the current status of the snapshot.
The indexing state is listed next to the snapshot in the Backup Destination
properties window.
Table 4-3 displays the different states of snapshot indexes.
Table 4-3 State of snapshot indexing
Index state Description
Not indexed Something went wrong during indexing and this snapshot has not
been indexed
Indexed This snapshot has been indexed.
Indexing This snapshot is currently being indexed.
Pending This snapshot is queued to be indexed (only one snapshot is indexed

at a time).
See “Configuration issues” on page 151.
Deleting snapshots
You can keep snapshots for a certain number of hours, days, weeks, or months
before being automatically deleted. You should define the retention period to
indicate the length of time that snapshots are retained. If you need to free hard
disk space on the destination, you can manually remove unnecessary snapshots.
Note: You can store snapshots up to a limit that is determined by your underlying
snapshot technology. This limit may vary considerably if alternative snapshot
providers are installed.
Snapshots that are associated with a given backup destination can also be deleted
when the backup destination itself is deleted.
See “Deleting backup destinations” on page 67.
To delete snapshots
Configuring registry entries
Properties.
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.

CPS includes a Settings Utility that lets users change a number of CPS tunable
parameters. These parameters could previously only be changed by manually
modifying entries in the system registry.
You can use the Settings Utility to change the parameters for the following
settings:
■ 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. See
the Symantec Web site for a current list and description of configurable
parameters.
Accessing the Settings Utility

Table 4-4 describes the settings that are available in the Settings Utility.
Table 4-4 Settings Utility
Setting Description
Servers pane The Servers selection pane shows all of the servers in the Backup
Group. Select a server to view the existing parameters and values
for that server.
Table 4-4 Settings Utility (continued)
Setting Description
Parameters 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 75.
Refresh Lets you update the values in the Parameter pane after making
changes.
Help Lets you access the online help for the Settings Utility.
Restore Defaults Lets you restore all parameters to their original default values.
To access the Settings Utility

◆ Do one of the following:
■ Navigate to the CPS Services folder
C:\Program Files\Symantec\Continuous Protection Server\Services, and
then double-click settingsutility.exe.
■ In the Administration Console, click Tools > Settings Utility.
About the Settings Utility tunable parameters

Table 4-5 describes the tunable parameters that are available in the Settings
Utility.
Table 4-5 Settings Utility tunable parameters
Parameter name Description
AlertGroomFrequency Specifies how often a grooming cycle will be run to remove outdated alerts from
the system. The 'DaysToKeepAlertItems' key sets the number of days an alert
will 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.
AlwaysDoRegionAnalysis To cause CPS to use region analysis regardless of file size, set this string value
to 1 (default is 0).
Changing this value requires that the Continuous Protection Agent Service be
restarted on the server.
Table 4-5 Settings Utility tunable parameters (continued)
BroadcastAddress 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 the
CMS, CPA, Broker Service, and Continuous Protection System State Manager
Service, to be restarted.
BroadcastHops Specifies the maximum number of router hops for IPv6 discovery broadcasts.
The default value is 1.
ConnectionPooling 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 the
server.
DaysToKeepAlertItems The number of days that alert items are kept on the server.
Changing this value will not require systems or services to be restarted.
DaysToKeepDeletedSnapshots Specifies the number of days that deleted snapshot entries are kept on the server.
The default value is 30 days.

DelayDirChangeNotifications If set to 1, this parameter prevents the CPS filter driver from delaying the
completion of Directory Change Notifications. The only time it is necessary is
when the Windows “Services for Macintosh” (SFM) is running on the server where
CPS is installed. Under conditions of heavy usage, SFM may fail if this setting is
not 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 for
Macintosh is running on the system.
Although making this setting will allow SFM to run, it will also create a problem
for the Windows “Simple Mail Transport Protocol” (SMTP) service. It will prevent
SMTP 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 same
system where CPS is installed. The user must make a choice as to which Windows
service that will run.
Changing this value requires that the server be restarted.
DoEventLog If this value is set to 1, certain internal errors in CPS components will write an
entry in the Windows application event log. If it is set to 0, no event log entry
will be written.
EnableDebugConsole For Symantec Technical Support use only.

EnableLogFile Enables trace logging.
The default value is 1 to enable diagnostic trace logging, or 0 to disable.
EnableTimestamp If this value is set to 1, a timestamp is printed on each line of diagnostic trace
logs recorded by CPS components.

FFXPort Continuous Protection Agent data port.
Changes to this value must be made on all computers in the Backup Group. In
addition, the Continuous Protection Agent Service must be restarted on all
computers.
FilteredIDList 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 separated
by either commas or semicolons. Only new alerts will be filtered from the Alert
Database after an addition to this list. No existing alerts will be removed from
the database.
The default value is an empty string.
Gateway Either the host name, Fully Qualified Domain Name, or IP address of the ENL
master.
(ENL\Network.TCPIP)
The default value is usually the CMS name.
Gateway Either the host name, Fully Qualified Domain Name, or IP address of the ENL
master.
(ENL\Network.UDPv6)
The default value is usually the CMS name.
Gateway Specifies whether or not this server will act as a router for ENL network traffic.
(ENL\System) 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 traffic
to a CMS on another subnet).
IndexingRoot Location of files that hold index information about the data that has been backed
up by CPS. The location must have at least 120 MB of free space (1GB or more
recommended).
The default value is set by the CPS installer.
Changing this value will require that the Continuous Protection Indexing Service
be restarted on the server. In addition, indexing files will be moved from their
previous location to the newly specified path.
JournalRoot Location of the dynamic changes of data during continuous backups. The location
must have at least 120 MB of free space (10 GB or more recommended).
LogOpenFileTableOncePerSet Controls whether the filter driver writes a table of open file entries into the first
outbound dynamic journal file only once (when a job starts), or writes this table
at the start of every new outbound journal file.
The default value is 0. Set to 1 if journal writing errors occur during continuous
backup jobs owing to an Open File Table (OFT) overflow, as can happen on systems
where a great many files are opened in rapid succession.
Changing this value requires that the system be restarted.
LogPath Location of the CPS trace log files. The location must have at least 100 MB of free
space. 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.
(located in EFC) The default value is set at install time.
LogText A complex hexadecimal mask used to specify the type of entries that will be
written to the 'EFC.log' file.
The default value is 0x00300100. A value of 0xFFFFFFFF signifies that All ENL
logging information will be written to the log file. This optional setting can be
useful in debugging situations, but will quickly create very large amounts of log
data.
Master Specifies whether the ENL Service will start up in Master mode.
(located in ENL\System) The default value is Yes for a CMS computer and No otherwise.
MaxDirSize The maximum number of files to show for a single directory in the Backup Exec
Retrieve ‘browse’ view.
MaxLogSize The maximum size (in bytes) that the diagnostic trace log can grow before a new
file is started.
The default value is 10485760 (10 MB).
MaxLogSize The maximum size of the ENL log in bytes.
(ENL\System) Default is 1048576 bytes (1 MB).
Changing this value requires the ENL service and its dependent to be restarted.
MaxPacketSize Sets the maximum size for a UDP packet. Useful on networks that have a small
MTU.
(ENL\Network.TCPIP)
MaxPacketSize Sets the maximum size for a UDP packet. Useful on networks that have a small
MTU.
(ENL\Network.UDPv6)
MaxRAPerCentChange To change the maximum percentage difference in file size for region analysis (in
percent). Larger values mean region analysis will still take place, even if file sizes
differ by a larger percentage.
MinRASizeInKb To change the minimum file size for Region Analysis (in KB).
MsBetweenRallyChecks This parameter specifies the time that a job will attempt to be restarted after it
has failed.
The default value is 120000 ms (2 minutes).

NamedObjectsRoot Holding location for the System State and share information. The location should
have at least 100MB of free space (1GB or more recommended).
Changing this value requires that the Continuous Protection Agent Service and
Continuous Protection System State Manager Service must both be restarted on
the server. In addition, named objects files will be moved from their previous
location to the newly specified path.
Netgroup (ENL\System) The name of the CPS Backup Group that this computer is associated.
The default value (Backup Group) is set at install time.
NeverDoRegionAnalysis To disable region analysis for all files, set this value to 1. When region analysis
is disabled, files are synchronized by copying the entire source file to the target
system. If both this value and “AlwaysDoRegionAnalysis” are set to 1, the
“AlwaysDoRegionAnalysis” value takes precedence.
NumberOfLogs This parameter specifies the number of diagnostic trace log files to keep. When
the number of trace log files exceeds this number, older log files are deleted. Set
this value larger than the default value to preserve more logs, and contain more
job history.
OutboundJournalCleanupSize Size of the journal at which a switchover to the next journal may begin. This
value must be less than the journal size by at least 1MB.
This value must be an exact multiple of 1 MB (1048576 bytes).
OutboundJournalNominalSize This parameter is the default size in bytes of an outbound journal file when it is
first created. The nominal size of journal files should be made larger than the
default size only when necessary to avoid job cancellations owing to Open File
Table (OFT) overflows.
This value must be an exact multiple of 1 MB (1048576 bytes).
OutboundSyncJournalLimit If the number of outstanding sync journal files exceeds the

OutboundSyncJournalLimit, the CPA service slows down the creation of sync
journals during initial synchronization between two systems.
PreferredAddress Specifies the IP address that the node will use when registering with the name
service. This value must be an IPv4 compatible IP address.
(ENL\Network.TCPIP)
PreferredAddress Specifies the IP address that the node will use when registering with the name
service. This value must be an IPv6 compatible IP address.
(ENL\Network.UDPv6)
PreferredNIC Specifies the NIC that will be used to find the preferred IP address if it is not
explicitly set through the PreferredAddress key. The preferred NIC is specified
(ENL\Network.TCPIP)
by the MAC address of the NIC.
PreferredNIC Specifies the NIC that will be used to find the preferred IP address if it is not
explicitly set through the PreferredAddress key. The preferred NIC is specified
(ENL\Network.UDPv6)
by the MAC address of the NIC.
ReservedFreeDiskSpace If the amount of free disk space on the volume containing CPS journals falls below
this number of bytes, CPS jobs will be cancelled.
RxRmsStaticPort Continuous Management Service RPC port.
Changing this value must be made on all computers in the Backup Group. In
computers, and the Continuous Management Service must be restarted on the
CMS server.
RxRsaStaticPort Continuous Protection Agent RPC port.
Changing this value must be made on all computers in the Backup Group. In
computers.
Schedule Specifies the frequency with which the System State Manager Service regenerates
Named Object data.
The default value is 0 3 5 4 0 1439.
SerializeIrpLogging Set this value to 1 to prevent the CPS filter driver from queueing too many i/o
requests for journaling.
The default value is 0. Set to 1 only on very slow, single-CPU systems if continuous
backup jobs are failing owing to journal writing errors.
Changing this value will require that the system be restarted.
ShareInfoAsSingleComponent Groups all shares for a business server under a single entry for faster display and
snapshot processing.
The default value is 0 for multiple components. Set to 1 for single component.
Socket Specifies the UDP port used by ENL. Changing this value affects both the IPv4
and IPv6 functions of the ENL service.
Changes to this value must be made on all computers in the Backup Group. In
addition, the ENL Service must be restarted on all computers.
UsePrivateFindFileMethod Set this value to 0 to force CPS to use the standard Win32 methods of finding
files.
Verbose 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.
(ENL\System)
Changing this value requires the ENL service and its dependent to be restarted.
VolumeLevel This parameter controls the level of detail shown in diagnostic trace log messages.
A lower number means less detail.
Note: Modifying multiple parameters may have unpredictable and adverse

consequences. Symantec recommends that these parameters be changed only by
knowledgeable users or at the guidance of Symantec Technical Support.
Changing Settings Utility parameters

Changing Settings Utility parameters may require restarting CPS services or
systems on one or more servers in the Backup Group. Before changing any
parameter, please review the cautions associated with that parameter in the CPS
tunable parameters list. This information will also be displayed during the
parameter 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 review
or change.
3 In the Parameters pane, double-click anywhere in the row of the parameter
that 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 parameter
value.
6 Restart the services or computers as noted in the warning prompt.
Chapter 5
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 jobs

Continuous Protection Server lets you create a variety of backup jobs to protect
your data. As the needs of your business change, you can add or delete backup
jobs, or set new properties for existing backup jobs.
After a CPS backup job has been created, you can further modify the job by defining
additional functionality such as the following:
■ You can define exceptions to backup rules. For example, if you want to back
up 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 changed
bytes to the destination. Snapshots of the destination are taken at regular
intervals. Each snapshot is saved for 24 hours unless you specify otherwise.
■ You can run scripts before or after a backup job. Advanced settings are available
for defining pre- and post-scripts to run before and after backup jobs. For
example, you can close a database or run a virus scan on a folder before a
backup job starts.
88 Backing up data
Creating CPS backup jobs
■ You can limit bandwidth so a job uses fewer resources. Advanced options are
available for setting bandwidth restrictions.
About backing up System State and Shadow Copy Components

The Windows operating system includes data that requires special handling so
that you can backup and restore it properly. This data, referred to as System
Information in CPS, contains different information depending on the version of
Windows 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 CPS
backup 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 contained
in each set will be backed up or restored.
If a continuous job is created to back up system information, it is captured by
default 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. Do not attempt to restore System State data around these
same times. The restore may fail because a System State restore does not interrupt
a System State data capture that is in progress.
When System State or Shadow Copy components and unrelated files are backed
up 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 should
be configured separately from regular file backups to better control scheduling
conflicts and possible lapses in protection.
See “Restoring system information” on page 101.
How encrypted files are handled

Files that are encrypted using Microsoft’s Encrypting File System (EFS) are not
copied over the network from the Business Server to the Protection Server, and
therefore are not backed up.

Jobs 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 Protection
Server using the Backup Job Wizard. The information that is required and general
Backing up data 89
steps for creating a backup job manually or using the wizard are essentially the
same.
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 backup
destination.
See “Adding a backup destination” on page 65.
All regular shares are backed up automatically by the backup job. The share backup
job backs up the information about the share, but not the underlying data for the
share. If you want to back up the data that the share points to, you must select
the folder containing that data when you configure the backup job. When you
select 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 is
reflected with icons.
Table 5-1 describes the status icons that are used in the tree view.
Table 5-1 Status icons
Status icon Description
Everything under this directory is selected for backup. Anything new added
to this directory (or its subdirectories) is automatically selected for backup.
This directory is excluded from the backup. If this directory was previously
backed 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 be
backed up. For example, a folder may contain an exclude rule for *.exe. If
the file word.exe is added to the folder, it is not backed up, but the file
work.doc is backed up.
This node has not been selected for backup, and neither have any of its
subdirectories. Some subdirectories may have been excluded (see the red
‘x’), which causes them to be removed.
90 Backing up data
Backup rights are required to all referenced servers of a CPS backup job, including
the server hosting the Continuous Management Service.
To create a CPS backup job
2 In the task pane, under Backup Job Tasks, click New backup job using wizard.
3 Review the text on the Welcome to Backup Job Wizard screen, and then click
Next.
4 On the Name the Backup Job screen, type a name and optional description
for the backup job.
5 On the Select a Backup Destination screen, select one of the defined backup
destinations. This selection is the Protection Server where the data is backed
up.
6 On the Select Data to Back Up screen, select the information that you want
to back up.
7 On the Select When to Backup screen, designate when the backup should
occur.
Whenever a file changes Initiates a continuous backup of the folder or

file. That is, a file or folder is backed up
whenever changes are made to it. This job
starts as soon as the user clicks OK.
According to a schedule Lets you set a regularly scheduled or periodic

backup of the folder or file. If this option is
selected, you need to define the backup
schedule. This job starts if it is in the backup
window and the user clicks OK.
Backup job schedules are always shown in the

local time of the user who is creating the
backup job. If backup jobs are created for
servers that are located in other time zones,
you must convert that server’s time to your
local time.
Initiate the backup job manually Lets you back up the contents of the folder or
file on demand. This job will not start
automatically.
8 Verify that the backup job was created by observing that the Job shows on
the list of jobs from the Job Monitor.
Backing up data 91
Editing backup job configurations
Editing backup job configurations

Backup 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 backup destination

Backup jobs can be moved to a different backup destination after they have been
created.
Moving a job between backup destinations does not delete the data from the
original backup destination. Instead, after the backup destination has been changed
and 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 original
backup destination. In the Explorer window, the user can delete the job data
manually or leave it there. Also, when a backup destination resides on a remote
computer, 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 destination
drop-down list.
5 Click OK to save the backup destination and run the job.
Including and excluding information from backup jobs

Backup selections define what data you want to back up. Exceptions to the
selections 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.
92 Backing up data
Note: When files or directories are explicitly excluded, they are removed from the
backup destination. If files or directories are not selected, they are not removed.
You can add any combination of include and exclude filters to each backup
selection. This enables you to select files to back up whose names match an
arbitrary combination of patterns.
For example, if you want to exclude all tmp files from the backup, except for those
whose names contain the letter Q or the letter X, you can specify the following
list of filters:
■ Include *Q*.tmp
■ Include *X*.tmp
■ Exclude *.tmp
Be sure you specify the parameters in the right order. Parameters are applied
top-to-bottom as listed, and the first rule matching a file name is the one that is
used to decide whether or not to back up a file.
When initially adding a filter, you can enter a semi-colon delimited list to specify
multiple filters to add. Each item on the list is added as a separate filter. If you
later 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 click
Includes/Excludes.
7 Click Add.
Backing up data 93
8 Select the options you want.
Type Kind of filter. Your options are Include or Exclude.
Inclusive filters define the kinds of information to

include. For example, if all temporary files are excluded
from backups, you can include temporary files with
the letter Q in the file name.
Exclusive filters define the kinds of information to

exclude. For example, if a marketing proposals folder
is included in a backup, you can exclude the folder’s
temporary files.
The information you want to include or exclude is

defined in the Filter field.
Filter Criteria that specifies what information to include or

exclude.
For example, your backup selections include a

marketing proposals folder, and you are excluding
temporary files. The type of rule is Exclude and the
filter is *.tmp. Use a semicolon-delimited list to add
several items at once.
Apply to Subdirectories Select this option if the include or exclude filters apply
to subdirectories of the backup selection.
9 Click OK.
10 If you want to change the priority of a filter, select the filter, and then click
Move Up or Move Down.
11 Click OK.
12 On the Backup Job Properties dialog box, click OK.
Editing filters
You 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.
94 Backing up data
5 Expand the tree to expose the files or folders that are selected for the backup
job.
Includes/Excludes.
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 click
Move Up or Move Down.
11 Click OK.
Deleting filters
You 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 backup
job.
Includes/Excludes.
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 schedule

As your data protection needs change, you may need to change the backup
schedule.
Backups can be scheduled to run as the following:
■ Continuously (whenever changes are made to a file)
Backing up data 95
■ Periodically (according to a schedule)

■ As needed (manually)
Backup job schedules are always shown in the local time of the user who is creating
the backup job. If backup jobs are created for servers that are located in other
time 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 21.
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.
Whenever a file changes Initiates a continuous backup of the folder or

file.
According to a schedule Enables you to set a regularly scheduled or

periodic backup of the folder or file. You need
to define the backup schedule.
Initiate the backup job manually Requires you to manually start the backup job
from the CPS Console.
6 Under Back up the selected files and folders, select According to a schedule.
7 Click Edit Schedule.
8 Select the options you want.
Run on these days Select the check box next to each day that you
want the snapshot to occur.
Run only at Select and define a specific time for the

snapshot to occur.
Run Select and define the intervals at which the

snapshot occurs.
9 Click OK.
10 Click OK in the Backup Job Properties dialog box.
96 Backing up data
Limiting the network bandwidth of a backup job

Continuous Protection Server lets you specify network bandwidth properties to
better manage your resources during backup jobs.
The network bandwidth setting applies to all active backup jobs running between
two computers. The most restrictive bandwidth setting is applied to all running
jobs.
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.
Source server Select the server from which the files are copied
during the backup job.
Limit bandwidth usage to Select the bandwidth that is allocated to the backup
job process.
Network connection type Select the type of connection existing between the
Business Server and Protection Server.
8 Click OK.
9 Click OK in the Backup Job Properties dialog box.
Adding a script that runs before or after backup jobs

You can run a script before running a backup job to perform a task such as closing
a database. Similarly, you can run a script after a backup job is completed to
perform 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
Backing up data 97
Starting, stopping, and canceling backup jobs manually
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:
Server Select the server on which to run the script.
Event Select when the script will run. Your choices are
Pre-backup or Post-backup.
Script Type the path to the script file that will run before
or after this backup job. If necessary, you can browse
to the file.
Cancel command if not Select the number of minutes before the backup job
completed within xx minutes is canceled if it is not completed.
Run asynchronously Select this option to start a script and continue

processing.
To run the pre-command script to completion before

starting the backup, or to run the backup to
completion before starting the post-command script,
uncheck this option.
Starting, stopping, and canceling backup jobs

manually
You can manually manage CPS jobs, including starting, stopping, and canceling
jobs.
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 can
result in an incomplete file on the destination.
To start, stop, or cancel backup jobs manually
1 On the navigation bar, click Job Monitor.
2 In the Current Job Filter box, click All jobs, Backup jobs, or Restore jobs.
3 In the results pane, right-click the job.
98 Backing up data
Starting, 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.
Chapter 6
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 Protection

Server
Continuous Protection Server lets you quickly restore information. Administrators
can view all backups when selecting files to restore.
Note: Restore selections are used for the current session only. If you end a session
without restoring selected files, the files must be selected again. Continuous
Protection Server refreshes the selections at the end of a session to ensure that
each user begins the restore job with a new record.
When an alternate restore destination path is chosen, be careful not to select any
path with data that needs to be saved. Continuous Protection Server overwrites
the data in the selected folder.
See “Protecting CPS with Backup Exec” on page 132.
See “About Backup Exec Retrieve” on page 105.
See “Restoring Continuous Protection Server with Backup Exec” on page 135.
100 Restoring data
Restoring files and folders
Restoring files and folders

You can restore files and folders using CPS Administration Console. Selected files
in a restore job are copied from any backup destination to any computer in the
Backup Group. You can restore data only, the share only, or both. Select data
carefully 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 cannot
be restored, even to another Business Server.
See “Restoring network shares” on page 103.

When an alternate restore destination path is chosen, be careful not to select any
path with data that needs to be saved. Continuous Protection Server overwrites
the 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 data 101
Restoring system information
4 Specify the options that you want.
Restore job name Abbreviated name of this restore job.
For example, WCMKTProposals.
Description Full name or brief description of the restore job.
For example, West Coast Marketing Proposals

Restore Job.
Restore to Location where the selected files and folders will

be copied.
Options Restore to original folder - Restores the selected

files to the folder where they originated.
Redirect the restore to an alternate folder -

Restores the selected files to the folder of your
choice. Type the path to the folder in the text box.
Preserve folder structure Maintains the tree structure of the selected files
and folders during the restore. This check box is
selected for redirected restore jobs. If this option
is not selected, the contents of the restore folder
are added to the alternate restore folder.
When restoring folders containing reparse points,

you must either select the Preserve folder
structure option or restore the folder to an empty
folder.
5 Click OK.
6 Click OK to clear the confirmation message.
Restoring system information

Restoring system information (System State or Shadow Copy Components) involves
copying specific files from a Protection Server back to a Business Server.
Note: You should not restore system information to servers other than the server
from which the information was originally backed up. Redirecting system
information 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
102 Restoring data
Restoring System State to an Active Directory system
State data at or near these same times, the restore may fail because a System State
restore does not interrupt a System State data capture that is in progress. In this
case, the System State restore jobs should be started well before or about 10
minutes after the backup times.
See “About backing up System State and Shadow Copy Components” on page 88.
To restore system information
2 In the selection pane, select the System State or Shadow Copy Components.
Restore job name Abbreviated name of the restore job.
For example, WCSRCSystem.
For example, West Coast Source Server System State.
Restore to System State will always be restored to its original location.
5 Click OK.
When the System Information is restored, the server will automatically
restart.
Restoring System State to an Active Directory system

System State can be restored to a system that is an Active Directory.
Before restoring System State to an Active Directory system, you must have or
create a Directory Services Restore Mode (DSRM) password. For information on
DSRM passwords, see the Microsoft support article “How To Reset the Directory
Services Restore Mode Administrator Account Password in Windows Server 2003”
on the Web.
Symantec does not recommend restoring System State to servers other than the
server from which the System State was originally backed up. Redirecting System
State to other servers will have unpredictable results.
For more information about how to restore System State in Continuous Protection
Server, go to the following URL:
Restoring data 103
Restoring network shares
http://seer.entsupport.symantec.com/docs/278977.htm
To restore System State to an Active Directory system
2 In the selection pane, select System State.
4 Specify the options you want.
For example, WCSRCSystem.
For example, West Coast Source Server System State.
Restore to System State will always be restored to its original location.
5 Click OK.
6 Click OK to clear the confirmation message. The computer will restart in
DSRM mode.
7 Log on using your DSRM password.
8 Double-click the symantec dsrm system state restore.bat file, which is located
on the Desktop. You can monitor the progress in the command window.
When the System State restore has completed, the server will automatically
restart back in normal mode.

Restoring network shares involves restoring the data, the share, or both. If you
protect a server, users of Backup Exec Retrieve can only access files and folders
that were originally written to a share. After restoring shared folders, the screen
must 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 100.
To restore network shares
2 In the task pane, under Views, click Console restore.
104 Restoring data
3 In the results pane, select the restore job.

■ To restore the share only, in the selection tree pane, do not select any
information to restore.
■ To restore the data and the share, in the selection tree pane, select the
files 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 list
pane restores the share. If any attribute in the share changes, the share must
be disabled before restoring. Attributes appear in the Microsoft Windows
Properties dialog box for the shared item and include the share name,
comments, user limits, and permissions.
For example, WCMKTShare.
For example, West Coast Marketing Shared Folders.
Restore to Location where the selected files and folders will

be copied.
Shares can only be restored to their original

location, although the files in a share can be
restored elsewhere.
Options Restore to original folder - Restores the selected

files to the folder from which they originated.
Redirect the restore to an alternate folder -

Restores the selected files to the folder of your
choice. Type the path to the folder in the text box.
Preserve folder structure Maintains the tree structure of the selected files
and folders during the restore. This check box is
enabled for redirected restore jobs.
8 Click OK.
Chapter 7
Using Backup Exec Retrieve
■ About Backup Exec Retrieve
■ How Backup Exec Retrieve works
■ What end users can do with Backup Exec Retrieve
■ Before you install Backup Exec Retrieve
■ Requirements for installing Backup Exec Retrieve on a Web server
■ Requirements for using Backup Exec Retrieve on end users' computers
■ Installing Backup Exec Retrieve
■ About configuring Backup Exec Retrieve
■ Uninstalling Backup Exec Retrieve
■ Troubleshooting Backup Exec Retrieve
About Backup Exec Retrieve

Backup Exec Retrieve provides a Web-based method for end users to search,
browse, preview, and retrieve archived files and email. The files and email must
be in shared folders to which the end users have permission. End users save
retrieved files or emails to a location that they specify. Backup Exec Retrieve is
not designed to restore system databases or other system-level files. Likewise,
end users cannot delete, change, move, or rename files by using Backup Exec
Retrieve.
You can configure Backup Exec Retrieve to let end users retrieve their own data.
Backup Exec Retrieve works with the following data sources:
106 Using Backup Exec Retrieve
How Backup Exec Retrieve works
■ Backup Exec Archiving Option

■ Backup Exec Continuous Protection Server (CPS)
■ Backup Exec Desktop and Laptop Option (DLO)
■ Backup Exec System Recovery Manager
Backup Exec Retrieve uses Windows security and Internet browser download
features and is limited to Windows server platforms.

The following table describes a typical use-case scenario for installing, configuring,
and using Backup Exec Retrieve. It includes information for both the administrator
and the end user .
End users log on with their domain credentials. The system restricts their access
so that they can only retrieve the files to which they originally had access. For
example, if a file server is protected, users likely only have access to the files that
are located inside shared folders. Backup Exec Retrieve also allows Exchange
email retrieval. In such cases, mailbox permissions and mailbox folder permissions
control the access.
Table 7-1 How Backup Exec Retrieve works
Process Role Task or Process

order
1 Administrator Optional - Installs Backup Exec and Backup Exec

Archiving Option on the Backup Exec media server.
2 Administrator Installs Backup Exec Retrieve on a Web server or on the

Backup Exec media server that is on a Web server.
Using Backup Exec Retrieve 107
Table 7-1 How Backup Exec Retrieve works (continued)

order
3 Administrator Configures Backup Exec Retrieve with the locations of

any of the following indexers that can be included in
searches by end users:
■ Media server (for the files and the emails that the
Backup Exec Archiving Option archives).
■ Backup Exec System Recovery Manager server (for
files in recovery points that Backup Exec System
Recovery creates).
■ Continuous Management Service server (for the files
that Continuous Protection Servers back up).
■ Desktop and Laptop Option server (for the files that
the Backup Exec Desktop and Laptop Option backs
up).
4 Administrator Notifies the end users of the following Backup Exec

Retrieve Web address so that they can search their own
files and emails.
https://<Backup Exec Retrieve Web server

name>/BERetrieve
You must also provide the following information to the
end users:
■ If the standard Windows security alert screens are

displayed to the user, inform the user to click Yes or
OK to continue.
■ If a message appears to the user with information
about the security certificate, it is related to SSL
certificates. Have the user click Yes to continue.
What end users can do with Backup Exec Retrieve
Table 7-1 How Backup Exec Retrieve works (continued)

order
5 End user ■ Launches Backup Exec Retrieve using the Web

address that the administrator supplies.
■ The browser may prompt the end user to download
and install Microsoft Silverlight, which is a necessary
component to use Backup Exec Retrieve.
Your organization may not permit end users to
download files from the Web. In such cases, the
administrator must deploy Silverlight to the end
users' computers before end users can use Backup
Exec Retrieve.
See “About deploying the Silverlight run time in your
organization” on page 113.
If Silverlight is already installed on the user's
computer, the browser immediately displays the
Backup Exec Retrieve logon screen.
■ At the logon screen, the end users type their user
name, password, and domain.
The credentials that a user specifies here determines
what data they are authorized to view and retrieve.
6 End user Selects to search, browse, or view recent activity for files
or email.
7 End user Submits a query. Backup Exec Retrieve displays the

results for the end user to page through. The user can
click a related link to drill down into the information.
8 End user Retrieves the selected file or email and saves it locally
on their computer or elsewhere.

Backup Exec Retrieve lets end users search, browse, or retrieve their own files
and emails from a Web-based user interface.
The following table describes the most frequently used tasks in Backup Exec
Retrieve.
Table 7-2 What you can do with Backup Exec Retrieve
Task Description
Basic search Lets end users find the following

information:
■ Files with text in the file name or in the

content. Support is also included for file
system wildcards.
■ Email messages with text in the Subject,
Content, From and To fields.
Advanced search Lets end users find the following:
■ Files based on file name, file content, file

folder, or specified date range.
■ Email messages based on the text in the
following locations:
■ Subject field
■ Subject and email contents
■ From and To fields
■ A date range
Recent activity Lets end users find recently archived,

deleted, or edited files or email messages.
Browse folders Lets end users navigate through shared

folders to which they have permissions. Also
lets them view the files and email that were
backed up or archived.
When a backed up file is located, the end user

can view all stored versions of that file.
Versioning does not apply to archived files
or email messages. Review the date, time,
and file size to determine the version of the
file that you want to retrieve.
Preview Lets end users do the following:
■ Open an abbreviated preview of email

messages or some files in the list of
search results.
■ Preview an entire email message or some
files in the list of search results.
Before you install Backup Exec Retrieve
Table 7-2 What you can do with Backup Exec Retrieve (continued)
Task Description
Show versions Lets end users view all versions of backed up

files. (Does not apply to archived files or
email messages.)
Retrieve files and emails Lets end users retrieve and save a file or an
email message by using the Web browser's
Save As dialog box. Email messages are saved
with a .Msg file extension. Users can then
open the file in Microsoft Outlook.
Before you install Backup Exec Retrieve

Installation procedures might vary, depending on your work environment and
how you want to install Backup Exec Retrieve. You must install the software on
a Web server. If your Backup Exec media server is also a Web server, you can
install Backup Exec Retrieve on that computer as well.
You can have multiple installations of Backup Exec in a network domain.
During the installation, you may be prompted to install the latest version of
Microsoft's .NET Framework and Microsoft's Internet Information Services with
ASP.NET.
You must have Administrator rights, or be able to use an account that has
Administrator privileges, to install Backup Exec Retrieve.
Before you install the product, make sure that the computer meets the specified
requirements.
See “Requirements for installing Backup Exec Retrieve on a Web server”
on page 110.
See “Installing Backup Exec Retrieve” on page 113.
See “Uninstalling Backup Exec Retrieve” on page 118.
Requirements for installing Backup Exec Retrieve on

a Web server
To install Backup Exec Retrieve, the computer on which you install the software
must meet minimum requirements:
See “Before you install Backup Exec Retrieve” on page 110.
Requirements for installing Backup Exec Retrieve on a Web server
Table 7-3 Requirement for installing Backup Exec Retrieve on a Web server
Component Requirement
Processor Intel Pentium 4 CPU 2.0 GHz or faster
Operating system The following operating systems are

supported:
■ Windows Server 2008 R2

■ Windows Server 2008 R2 (x64)
■ Windows Server 2008
■ Windows Server 2008 (x64)
■ Windows Server 2003 R2, SP 2 or later
■ Windows Server 2003 R2, SP 2 or later
(x64)
■ Windows Server 2003, SP1
■ Windows Server 2003, SP 1 (x64 )
RAM 2 GB
Available disk space 45 MB
Software The following is installed on the computer

on which you want to install Backup Exec
Retrieve:
■ Microsoft .NET Framework 3.5 SP1.

At a minimum, Microsoft .NET
Framework 3.5 SP 1 is required to run
Backup Exec Retrieve.
Note: The latest version of the .NET
Framework is automatically installed if
it does not already exist or if an older
version exists. This note applies only
when you install Backup Exec Retrieve
for the first time.
■ Microsoft Internet Information Services
(IIS) 6.0 or later.
■ Microsoft ASP.NET
Requirements for using Backup Exec Retrieve on end users' computers
Requirements for using Backup Exec Retrieve on end

users' computers
For end users to use Backup Exec Retrieve, client computers must meet the
following requirements:
Table 7-4 Requirements for using Backup Exec Retrieve on end users'
computers
Component Requirement
Operating system The following operating systems are supported:
■ Windows XP SP2 or later

■ Windows Vista
Software The following software is required:
■ Microsoft Internet Explorer 7.0 or later.

Other browsers should also be compatible, but certain features
and user interface layouts may vary.
■ Microsoft Silverlight 3.0 or later plug-in
If Silverlight is not detected when a user accesses the Backup
Exec Retrieve Web page, the browser offers to install it.
Your organization may not permit end users to download files
from the Web. In such cases, the administrator must deploy
Silverlight to the end users' computers before end users can
use Backup Exec Retrieve.
See “About deploying the Silverlight run time in your
organization” on page 113.
Internet Internet access is required.
Web address End users must know the following Web server address, and their
own user name and password to access Backup Exec Retrieve.
https://<Backup Exec Retrieve Web server name>/BERetrieve
If the standard Windows security alert screens are displayed to

the user, inform the user to click Yes or OK to continue.
If a message appears to the user with information about the

security certificate, it is related to SSL certificates . Have the user
click Continue to this Web site to continue.
Installing Backup Exec Retrieve
About deploying the Silverlight run time in your organization

If your organization does not permit end users to download files from the Web,
you may need to deploy Silverlight to your organization's users' computers.
Silverlight is a necessary component to use Backup Exec Retrieve.
Functioning as an administrator, you can download the latest version of Silverlight
from the following Web site:
http://www.microsoft.com/silverlight/downloads.aspx
You can deploy Silverlight across your network by using any one of the following
methods:
■ Windows software update services
■ Microsoft System Center Configuration Manager
■ Group policy
For guidance on deploying the Silverlight run time in your own organization, see
the following:
http://www.microsoft.com/silverlight/resources/technical-resources/

You install Backup Exec Retrieve from the Backup Exec installation media browser.
Following the installation, you must configure Backup Exec Retrieve by adding
the data sources that end users can search for their files and email.
See “About configuring Backup Exec Retrieve” on page 115.
To install Backup Exec Retrieve
1 Log on to your Web server (or the Backup Exec media server if it has Web
server capabilities).
You must use either the Administrator account or an account with
administrator privileges.
2 Insert the Backup Exec installation media into the appropriate drive of the
computer.
If the installation starts automatically Continue to the next step.

If the installation does not start Do the following in the order listed:
automatically
■ On the Windows desktop, click Start
> Run.
■ Type: <media drive letter>:\Setup.exe.
For example, e:\setup.exe.
■ Continue with next step.
4 Click Backup Exec Retrieve 2010.

5 In the Welcome panel, click Next.
6 In the License panel, read the license agreement, and then click I accept the
terms of the license agreement.
7 Click Next.
8 In the Environment Check panel, review the results of the Environment
Check . For each requirement, the following results are displayed:
Check mark The requirement and the

recommendations are met.
X The requirement is not met. You cannot

continue with the installation until the
requirement is met.
Click the associated link for additional

information.
9 Click Next.
Backup Exec Retrieve program files are installed in the default path that
appears on the Options page.
10 In the Destination panel, do one of the following:
To change the folder where the Backup Click Change to select a new folder.
Exec Retrieve files are installed
The default path is C:\Program
Files\Symantec\Backup Exec Retrieve\
To accept the default Continue to the next step.

About configuring Backup Exec Retrieve
11 Click Next to begin the installation.

During the installation of Backup Exec Retrieve, you may be prompted to
install Symantec LiveUpdate or Microsoft .NET Framework 3.5. In such cases,
follow the on-screen prompts to complete those specific installations.
12 In the Complete panel, click Finish.

To allow end users to search and retrieve their own files and email, you must first
configure Backup Exec Retrieve. During the configuration, you point to repositories
of user data that are available in the enterprise. These repositories are known as
data sources.These data sources contain backup copies of files or archives of files
and email messages.
For example, you can add a Backup Exec media server on which the Archiving
Option is installed, Continuous Protection Servers, or Backup Exec System
Recovery Manager servers. You add these various data sources to Backup Exec
Retrieve which in turn provide retrieval data to end users.
When you delete a data source, end users can no longer search that repository
for their data using Backup Exec Retrieve.
You must have local administrator rights to add, edit, or delete data sources from
the Backup Exec Retrieve console.
See “Adding a data source” on page 115.
See “Editing a data source” on page 117.
See “Deleting a data source” on page 117.
Adding a data source

You can add the following items to the list of available data sources that hold the
end user 's files and email:
■ Backup Exec media server on which the Archiving Option is installed
■ Continuous Protection Servers
■ Desktop and Laptop Option servers
■ Backup Exec System Recovery Manager servers
Backup Exec Retrieve.
To add a data source

1 Log on to the Backup Exec Retrieve Web server as a local administrator.
2 On the Windows Start menu, click All Programs > Symantec Backup Exec
Retrieve > Backup Exec Retrieve Configuration Console.
3 In the Symantec Backup Exec Retrieve Configuration dialog box, click Add.
4 Set the Add Data Source options.
See “Add or edit data source options” on page 116.
5 Click OK.
Add or edit data source options

When you add or edit a data source, you must specify account credentials to ensure
proper authentication to the server.
See “Adding a data source” on page 115.
See “Editing a data source” on page 117.
Table 7-5 Add or edit data source options
Item Description
Data Type Identifies the data source type that you want
Backup Exec Retrieve to connect to.
Name or IP address Indicates the name or the IP address of the

data source that you want Backup Exec
Retrieve to connect to.
User name Indicates the user name for an account that

has authorized access to this data source.
This option does not apply to the Archiving

Option data type.
Password Indicates the password for this account. The

software encrypts the password but does not
display it.

Option data type.
Confirm password Confirms the password for this account.

Option data type.
Table 7-5 Add or edit data source options (continued)
Item Description
Domain Indicates the domain name for this account

(if applicable to the type of data source you
selected).

Option or the Backup Exec System Recovery
Manager data types.
Editing a data source

You can edit the configuration settings of each data source that you have added
to Backup Exec Retrieve.
To edit a data source
3 In the Symantec Backup Exec Retrieve Configuration dialog box, select the
data source that you want to change.
4 Click Edit.
5 Set the Edit Data Source options.
See “Add or edit data source options” on page 116.
6 Click OK.
Deleting a data source

When you delete a data source, indexing of any new files or email messages
continues to occur. However, Backup Exec Retrieve no longer searches the indexes.
As a result, end users cannot search for those new files or emails.
Uninstalling Backup Exec Retrieve
To delete a data source

3 In the Symantec Backup Exec Retrieve Configuration dialog box, select a
data source name or type in the table.
4 Click Delete.
5 Click Yes to confirm the deletion of the data source.
Uninstalling Backup Exec Retrieve

You can use the Microsoft Windows Add and Remove utility to uninstall Backup
Exec Retrieve.
To uninstall Backup Exec Retrieve
1 From the Windows server on which Backup Exec Retrieve is installed, click
Start, point to the Control Panel, and then click Add or Remove Programs.
2 Click Backup Exec Retrieve, and then click Remove.
3 Click Yes to proceed with the uninstall.
Troubleshooting Backup Exec Retrieve

For help to resolve the problems that you might encounter with Backup Exec
Retrieve, you can check the following information.
Table 7-6 Troubleshooting Backup Exec Retrieve
Problem Description
Users get a secure sockets Backup Exec Retrieve uses a Secure Sockets Layer certificate
layer (SSL) certificate to protect communication between the client and server.
warning in their browser Web browsers may warn users of problems with the site’s
when they go to the Backup security certificate. You can continue to the Web site. For
Exec Retrieve Web site. more information on resolving the warning, click
http://entsupport.symantec.com/umi/V-367-2-1.
Table 7-6 Troubleshooting Backup Exec Retrieve (continued)
Problem Description
Selecting a file causes an When you select a file in Microsoft Internet Explorer, the
error in the application that file is saved to the Internet cache. Then, the program that
launches for viewing the file is required to open it is launched. If the Do not save
encrypted pages to disk option is selected in Internet
Explorer, then the file is not saved to the Internet cache.
However, the associated application is launched but it
cannot open the file. To fix this issue, deselect the option
in Internet Explorer (the option is the default on Windows
2003).
To deselect the option to save encrypted pages to disk
■ In Internet Explorer, click the Tools menu, and then click

Internet Options.
■ Click Advanced, and then scroll down to the Security
section.
■ Uncheck Do not save encrypted pages to disk.
■ Click Apply > OK.
Users cannot log in with a Backup Exec Retrieve usually runs on a separate computer
local account from the original computer that was backed up. The only
authority for local accounts and passwords is the original
computer, which might not be available when you use
Backup Exec Retrieve. You must use a domain account to
log in and retrieve files using Backup Exec Retrieve. Backup
Exec Retrieve makes every effort to capture the domain
users and domain groups that are part of local groups.
Therefore, if your domain account is a member of the Local
Administrators group on your computer, you can retrieve
your files.
Users cannot see all of my Indexing is a resource-intensive process. Performance

data (indexing take too long) expectations vary significantly depending on your hardware,
network configuration, and data change rate. Initial indexing
for a new storage location that contains many base recovery
points is the most intense load, in the range of minutes per
image. A smaller load for subsequent incremental recovery
points is in the range of seconds per incremental. Recovery
points, archives, and files that not indexed do not display
in search results. If you find that indexing takes too long,
you might need to distribute the load across additional
Indexing Servers.
Table 7-6 Troubleshooting Backup Exec Retrieve (continued)
Problem Description
Unable to download a file If an end user cannot download a file from Backup Exec
when you use the computer Retrieve in Internet Explorer, enable automatic downloads
name or IP address of Backup in the browser.
Exec Retrieve in Internet To enable automatic downloads in Internet Explorer
Explorer
■ In Internet Explorer, click Tools > Internet Options.
■ In the Security tab, click Custom Level.
■ In the Security Settings - Internet Zone page, scroll to
Downloads > Automatic prompting for downloads.
■ Click Enable.
■ Click OK, and then click Yes to confirm the change.
■ Click OK to return to Internet Explorer.
Clicking the Backup Exec If Enhanced Security is enabled in Windows, you are
Retrieve in Internet Explorer prompted to add the Backup Exec Retrieve URL to Internet
results in a prompt to add the Explorer's trusted sites list. If you continue without adding
site to the trusted sites list. the URL to the trusted sites list, you are prompted to install
Silverlight, even if it already installed. If you try to install
Silverlight again, the installation fails. Symantec
recommends that you add the Backup Exec RetrieveURL to
Internet Explorer's trusted sites list.
To add the Backup Exec Retrieve URL to Internet Explorer's
trusted sites list:
■ In Internet Explorer, click Tools > Internet Options.

■ In the Security tab, click Trusted sites.
■ Click Sites, and then on the Trusted sites page, add the
Backup Exec Retrieve URL.
■ Click Add, then click Close.
■ Click OK to return to Internet Explorer.
Chapter 8
Monitoring CPS processes
■ About the Job Monitor
■ Monitoring jobs and job pairs
■ Viewing a job report
■ Managing CPS job alerts
About the Job Monitor

You can monitor CPS jobs that are active, scheduled, or completed. The Job Monitor
also allows you to manually start, stop, or cancel jobs. You can narrow the list of
jobs 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 the
following:
■ All jobs
■ Backup jobs only
■ Restore jobs only
Likewise, each column in the Job Monitor view can be sorted and the columns can
be 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
122 Monitoring CPS processes
Monitoring jobs and job pairs

A 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 single
destination server.
In the case of a CPS backup job containing four Business Servers backing up to a
single 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 the
specific 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 be
doing. The job pair states, however, reflect what is actually occurring.
About job states

A job has errors if any error occurs on any job pair; that is, Business Server or
Protection Server. To determine the status of an active CPS job, you must view
the job status and any associated errors or alerts.
Table 8-1 lists the various job states.
Table 8-1 Continuous Protection Server job states
Job state Description
Starting 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 start
or stopped before completing.
Running The starting phase has completed. That is, all job pairs have
attempted 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 user
or schedule cancels the job.
For a scheduled, non-continuous job, the job remains in this state

until the job is completed, or the user or schedule cancels the job.
Monitoring CPS processes 123
Table 8-1 Continuous Protection Server job states (continued)
Job state Description
Stopping The job is attempting to stop. The user or schedule has commanded
that each pair complete synchronization and then stop running.
Errors and alerts indicate failures of one or more pairs to respond

to the stop request or to have reached full synchronization.
Stopped 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.
Canceling The job is attempting to stop abruptly. That is, the user or schedule
has commanded that each pair stop running whether or not they
have achieved synchronization.
Errors and alerts indicate failures of one or more pairs to respond

to the cancel request.
Canceled 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.
Completed If the job is a scheduled, non-continuous job, all pairs have

completed.
If the job is continuous, the job never completes. A continuous job

must be stopped or canceled.
Viewing the status of a job and job pairs

A backup job may consist of several Business Servers being backed up to a
Protection Server. Each Business Server-Protection Server connection for a specific
job constitutes a job pair. The status of each job and job pair can be monitored to
provide job details and logs.
The current jobs appear in the upper results pane, and the pairs that are associated
with 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
Column Description
Current jobs status

Table 8-2 CPS job status (continued)
Column Description
Job name The name that was given for the job.
Description
Type The job type can be one of the following:
■ Backup
■ Restore
■ Exchange Log
Status See “About job states” on page 122.
Transfer Rate The instantaneous rate that the job is running. For example, 21
Kbytes/Second.
Transferred The cumulative rate since the job (or pair) started. For example,
21.3 MB
Errors Indicates whether errors are associated with the job. Possible
values are Yes or No.
Alerts Indicates the number of errors or warnings to which no one

responded.
Schedule Type Indicates the type of schedule that was designated for the job.
Last Start Time Indicates the time that the job was last started.
Table 8-3 identifies status information that is provided for job pair listings
(columns).
Table 8-3 CPS pair status
Column Description
Current jobs status
Source The name of the source computer.
Destination The name and path to the destination computer.
Status See “About job states” on page 122.
Transfer Rate The instantaneous rate that the job is running. For example, 21
Kbytes/Second.
Viewing a job report
Table 8-3 CPS pair status (continued)
Column Description
Transferred The cumulative rate since the job (or pair) started. For example,
21.3 MB
Alerts Indicates the number of errors or warnings to which no one

responded.
Start Time Indicates the time that the job pair was started.
Stop Time Indicates the time when the job pair last stopped.
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, in
the Job History Filter box, select one of the following:
■ Last 24 hours
■ Last 7 days
■ All

You 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 the
heading.
CPS job report details

The information that is contained in the CPS Job Report consists of various topic
boxes that are arranged by the information presented.
Job Report topic box

The first topic box, Job Report, provides a summary statement on the quality of
the CPS jobs. There are two possible states for CPS jobs: all CPS jobs are good and
one or more problems exist with the CPS jobs.
CPS jobs topic boxes

Every CPS job has a topic box that displays in the job report and contains all the
information that is related to that job. The title of the box is the name of the CPS
job. 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
Topic box Description
Backup Job Header Contains a summary of the job at the time the report ran. It shows
the job name, description, type, state, last started time, and last
stopped time.
Backup Job Details Contains the job properties that define how the job was configured.
The Job Details boxes contain most of the job properties that are
found on the CPS Job Properties page.
Backup Job Selections Provides a list of the files and folders that are included and
excluded from the job.
Backup Job Pre/Post Displays any pre- or post-commands that were assigned to the
Commands job. The information that is provided includes the server name,
command, triggering event, whether the command is running
asynchronously, and the timeout period.
Backup Job Log Contains CPS job log entries for the period since the job last ran.
Job entries with warnings are displayed in orange text, and job
entries with associated errors are shown in red text. Jobs with
warnings or errors are also linked to the Symantec Support Web
site for possible solutions.
Backup Pair One Backup Pair box exists for each pair of the associated CPS
job. The title of the box is the name of the actual CPS pair. If there
is an exception associated with the pair, the box title contains the
state of the pair along with a description of the exception
condition.
Managing CPS job alerts
Table 8-4 Subordinate jobs topic boxes (continued)
Pair Header Contains a summary of the pair at the time the job was run. It
shows the source and destination server names, pair state, last
started time, last stopped time, destination consistency, and
destination latency.
Destination latency can only be calculated when both servers in

a pair are running Continuous Protection Server version 10d or
later.
Pair Log Contains CPS pair log entries.
Pair entries with warnings are displayed in orange text, and pair
entries with associated errors are shown in red text. Pairs with
warnings or errors are also linked to the Symantec Support Web
site for possible solutions.
Exception topic box

The Exception topic box provides a summary of warning messages for the various
jobs and pairs. The messages are linked back to the specific incident in the report.
Error topic box

The Error topic box provides a summary of error messages for the various jobs
and pairs. The messages are linked back to the specific incident in the report

Alerts are messages about a job, source server, or destination server in the Backup
Group, 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 the
following:
■ Errors: Red icons
■ Warnings: Yellow icons
■ Informational: Blue icons
Alert history lists the alerts to which an administrator responded. Alerts remain
in history for 30 days by default unless you delete them. You can delete one or
more alerts in history.
When you view active alerts or alert history, you can change the order in which
the information displays. The list can be sorted in ascending or descending order
by any column.
You can also change the order in which the columns display to view the information
in order by the following:
■ Category
■ Job name
■ Message
■ Server name
■ Time alert received
■ Type
Viewing and filtering active alerts

Alerts contain detailed information about the jobs that were run in the Backup
Group and the computers on which they were run. Whether viewing active alerts
or history, you can filter alert messages to show all alerts, only errors, only
warnings, or only informational messages.
To view and filter active alerts
1 On the navigation bar, click Alerts.
2 Click the Active Alerts 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 into
place to change the order in which columns are displayed.
Viewing and filtering alert history

Alert history lists the alerts to which an administrator responded. The alerts
remain in history for up to 30 days or until you delete them. When you view the
alert history, you can filter the list to show errors, warnings, or informational
messages only.
To view and filter alert history
2 Click the Alert History tab.
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 into
place to change the order in which columns are displayed.
Viewing alert properties

Alert properties provide detailed information about each alert. In addition to the
message details, response information appears for alerts in history.
To view alert properties
2 Click the Active Alerts or the Alert History tab.
3 In the selection pane, right-click the alert, and then click Properties.
Category Title of the alert.
Server Name of the Business Server or Protection Server on

which the alert occurred.
Time alert received Date and time the alert occurred. The time is the local
time of the server.
Job name Name of the backup or restore job, if a job is associated

with the alert.
Message Alert text.
4 Click OK.
Responding to active alerts

Responses 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 at
once. Multiple alerts are selected by pressing <Ctrl>.
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, click Respond, and then click a response.
■ To respond to all selected alerts, click Respond OK to All.
If the alerts have an OK response available, they are cleared from the list and
moved to the alert history. If multiple alerts were selected, respond separately
to each alert that is displayed.
Deleting alerts from alert history

The alert history contains the alerts that received a response. Alerts remain in
history for 30 days by default unless you delete them manually. You can delete
one alert at a time, multiple selected alerts, or all alerts at once. Multiple alerts
are selected by pressing <Ctrl>.
See “Changing Settings Utility parameters” on page 85.
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 Delete All.
4 Click Yes.
Chapter 9
Using Continuous
Protection Server with
Backup Exec
■ How Continuous Protection Server works with Backup Exec
■ Protecting your Exchange Servers with Continuous Protection Server and

Backup Exec
■ Protecting CPS with Backup Exec
■ Monitoring CPS jobs in Backup Exec
How Continuous Protection Server works with Backup

Exec
Symantec Backup Exec for Windows Servers enables administrators to perform
backup and restore operations between Continuous Protection Server (CPS) and
Backup 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 storage
of critical business data.
Using SmartLink technology, CPS jobs can be associated with existing Backup
Exec jobs. You can view alerts and log entries for CPS jobs through the Backup
Exec Administration Console.
When you create a job in Backup Exec, each server that is affiliated with CPS is
listed as a Continuous Protection Server node in the backup selection tree. If a
new Protection Server is added to the CPS Backup Group after backup jobs are
132 Using Continuous Protection Server with Backup Exec
Protecting your Exchange Servers with Continuous Protection Server and Backup Exec
created, you can add a new job or modify an existing job to capture CPS data from
the new server.
In the event of a system failure or data loss, Backup Exec enables you to restore
data 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 backup
jobs, and then view any alerts in Backup Exec. Otherwise, CPS jobs can be
monitored independently through the CPS Administration Console.
Protecting your Exchange Servers with Continuous

Protection Server and Backup Exec
Symantec Backup Exec uses Continuous Protection Server to continuously protect
Microsoft Exchange servers. The association between Backup Exec and CPS is
achieved through the Backup Exec Continuous Protection Broker Service that is
installed with each Continuous Protection Agent. For instructions on setting up
CPS Exchange backup jobs, see the Backup Exec Administrator's Guide.
See “Continuous Protection Server services that are installed” on page 36.
The Broker Service is installed only if the option for the Exchange Protection
Agent is installed. After the Exchange Protection Agent is installed, Backup Exec
users can create a backup job to protect the Exchange database and transaction
logs. The protected transaction logs are part of the Backup Exec Exchange full
backup set, as well as Recovery Point backups. Recovery Point jobs protect only
the transaction logs. When the transaction logs are coupled with the Exchange
full backups, more point-in-time restore points are available. In addition, the
transaction log growth on the Exchange server is contained.
Although Exchange protection jobs can only be created from the Backup Exec
Administration Console, CPS users can monitor the status of these jobs in the job
log/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 the
Symantec Backup Exec for Windows Servers Administrator’s Guide.
Protecting CPS with Backup Exec

You 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.
Using Continuous Protection Server with Backup Exec 133
■ Protection Servers and Business Servers.

■ 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 detailed
in 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 to
restore the data to the CPS Protection Server or the Business Server in the Backup
Group from which it was backed up, or to redirect the data to an alternate
destination.
See “Backing up the Continuous Management Service (CMS)” on page 134.
See “Backing up a Protection Server” on page 134.
See “Restoring the Continuous Protection Server ” on page 136.
See “Restoring a CPS Business Server” on page 137.
Configuring CPS for Backup Exec

Continuous 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 only
requirement to integrate CPS and Backup Exec.
If Remote Agent was not installed with the original CPS installation, install it
before creating backup and restore jobs with Backup Exec.
Backing up CPS with Backup Exec

The procedures for backing up CPS data are the same as backing up other data
using Backup Exec. To protect all CPS data, ensure that backup jobs include
selections from all servers in the Backup Group.
The Continuous Protection Server node is the gateway to all CPS data on the local
Backup 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 Continuous
Protection Server tree view.
Table 9-1 Continuous Protection Server tree view elements
Element Description
Continuous Protection The Continuous Protection Server node is the gateway to all CPS
Server data on the local server. The Continuous Protection Server or
Protected Resources root nodes could be selected for backup.
CPS Databases Databases reside on the Continuous Management Service (CMS).

The CMS can be installed on a dedicated server or on a Protection
Server. If the local server is not the CMS, the Databases node does
not display.
See “Backing up CPS databases” on page 134.
Protection Servers Protection Servers are listed in order by name and contain nodes
for the Business Servers on the local server.
See “Backing up a Protection Server” on page 134.
Business Servers Business Servers are listed in order by name under the Backup
Destination node and contain nodes for CPS Backup data on the
local server.
See “Backing up Business Servers” on page 135.
Snapshots Snapshots are listed in order by date and time.
See “Backing up snapshots” on page 135.
Backing up CPS databases

Backing up the CPS databases involves selecting information about the CPS
environment as it pertains to the installation, CMS, Network Helper, and indexing
service. Select the entire CPS Databases node, or a specific database. Backup Exec
displays the Databases node under the Continuous Protection Server node. To
back up databases, access the tree view from the CMS server and select the
Databases node. The Databases node displays on the CMS server and Business
Server with a backup destination.
Backing up the Continuous Management Service (CMS)

Backing up the CMS involves selecting the server that hosts the CMS, the CMS
databases, and Network Helper databases.
Backing up a Protection Server

You 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
from the available Business Servers. To keep critical business data only, selectively
choose information from specific volumes. Regular backups of the Protection
Server can help you restore your CPS environment in the event of a disaster.
Backing up Business Servers

You can back up a full Business Server, or selectively back up data from specific
volumes. File shares and system-level files should be backed up whenever they
change, such as when a new share is added.
Backing up snapshots
Snapshots are created by CPS using Microsoft Volume Shadow Copy Service (VSS).
They contain copies of the Backup Destination at various points in time. Depending
on your configuration, a snapshot of the CPS Backup Destination may contain
data from multiple Business Servers.
It is not necessary to select the root of the Continuous Protection Server node or
to back up snapshots regularly. Most of the data that is captured from snapshot
to snapshot is redundant because the majority of the data on the server does not
change between snapshots. Back up snapshots only as needed. For example, if a
server is running out of disk space, it might be prudent to back up the oldest
snapshot for archival.
Snapshot data should be backed up from the Continuous Protection Server node
on an as needed basis. This is because of the quantity of redundant data that the
snapshots typically contain.
Restoring Continuous Protection Server with Backup Exec

Restoring CPS and Backup Group data involves selecting information from Backup
Exec and then doing the following:
■ Restoring the data to a Protection Server.
■ Restoring the data directly back to the Business Server from which it was
backed 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 Properties
Selections screen.
Restoring the Continuous Management Service

The CMS can be hosted on the Protection Server or another server. If the server
that hosts the CMS fails, Backup Exec can restore the CMS from tape or disk.
Restoring the CMS includes restoring the CMS and Network Helper databases. If
the CMS is also a Protection Server, the CMS, CPA, indexing, and Network Helper
databases are restored.
All CPS configurations, including servers, backup destinations and jobs, that are
modified after the backup was created revert to their previous state when restored.
Restoring the Continuous Protection Server

Using Backup Exec, you can restore data to the Protection Server. Restoring a
Protection Server involves selecting the Protection Server, the CPS components,
and replicas that you want to restore. Backup Exec displays Protection Servers
listed by name under the Continuous Protection Server node.
Backup Exec restores data to the Protection Server from which it originated. For
example, if you are replacing a Protection Server, you should redirect the restore
job to the new server.
Note: Before restoring data from Backup Exec to CPS, stop all continuous jobs on
the CPS Protection Server and its associated Business Servers. In Continuous
Protection 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 Continuous
Protection Server from Backup Exec:
■ SmartLink enables communication between Continuous Protection Server and
Backup Exec for Windows Servers. That is, SmartLink enables backed up files
that 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 Continuous
Protection Server destination through the Backup Exec Administration Console.
Features in Microsoft Windows Server 2003, such as the VSS writer, are used
to back up and restore the files.
■ Restoring files from Backup Exec directly to a CPS source, bypassing the CPS
destination, can be performed under certain circumstances. For example, you
can restore files directly from Backup Exec to a CPS source running Windows
Server 2003.
■ When restoring CPS from Backup Exec, only the whole volume can be restored.
For more information about using Backup Exec Intelligent Disaster Recovery to
recover Continuous Protection Server, go to the following URL:
Monitoring CPS jobs in Backup Exec
Restoring a CPS Business Server

Backup Exec restores the data back to the Business Server from which it was
backed 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 CPS
backup data to an alternate destination. System-level files can be restored to the
server from which they originated; however, they cannot be restored to an alternate
destination.

You can establish a link between CPS and Backup Exec so that you can view alerts
and job logs for CPS jobs in the Backup Exec Administration Console. The
connection between CPS and Backup Exec is established by using the SmartLink
Wizard in CPS. SmartLink technology integrates Backup Exec with other Symantec
products, such as CPS.
The SmartLink Wizard generates a pre-command in Backup Exec, which is a
command 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 time
it ran. This allows Backup Exec administrators to check the status of CPS jobs
before a backup job is run in Backup Exec to protect CPS data.
See “Understanding the credentials for using Backup Exec SmartLink” on page 137.
See “Setting up a SmartLink connection between CPS and Backup Exec” on page 138.
See “Viewing Backup Exec alerts” on page 140.
See “Viewing Backup Exec job logs” on page 143.
Understanding the credentials for using Backup Exec SmartLink

The most important criteria in understanding security credentials is to determine
the security context under which SmartLink operates.
SmartLink runs as a pre-command of Backup Exec’s jobs. Backup Exec uses the
resource-level credential of the Backup Exec media server to run the pre/post
commands. If the computer level credential is not available, the default logon
account of Backup Exec is used to run the pre/post commands. The user can change
the computer level credential through the Backup Exec Administration Console.
If SmartLink cannot be authenticated by the servers containing the CMS or Job
Control Delegate (JCD), the user must create the proper CPS credentials for
SmartLink to access the remote CMS or JCD servers.
At a minimum, backup rights are required, which may be created in one of the
following ways:
■ Logon as the user that SmartLink will run under.

■ Use the SmartLink command line to create the proper CPS credential. Type
the following:
srbeslnkhost.exe /createcredential /server "server-name" /

domain "domain-name" /user "user-name" /password "password"
Setting up a SmartLink connection between CPS and Backup Exec

To view alerts and job logs for CPS jobs in Backup Exec, you must first establish
a SmartLink connection between the two products.
See “Understanding the credentials for using Backup Exec SmartLink” on page 137.
If SmartLink is run with multiple Backup Exec servers with a potential for failover
from one server to another, the batch file must be copied to each server from
which 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 the
Backup Exec job log for the associated job. If errors are detected in the status of
the 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 if
it 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 the
SmartLink command is contained within a batch file with other commands,
sufficient time must be allotted to run all commands. The most significant
constraint on the time that is required to run SmartLink is the amount of logs
that are needed for the backup job. After a backup job is run, the time that is
required for the actual CPS data gathering is shown in the Continuous Protection
section of the Backup Exec job log.
See “Monitoring CPS jobs in Backup Exec” on page 137.
See “Viewing Backup Exec alerts” on page 140.
See “Viewing Backup Exec job logs” on page 143.
Note: When creating a SmartLink association with Backup Exec, the Protection
Server 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 of
a CPS Protection Server.
3 On the CPS navigation bar, click Setup.
4 In the task pane, under General Tasks, click Create SmartLink using wizard.
5 Review the information that displays, and then click Next.
6 When the Enter a Backup Exec Media Server screen opens, SmartLink checks
the local server to determine if it is a Backup Exec media server. If it is, the
local server name is posted in the text box.
If the local server is not a Backup Exec media server (or the appropriate media
server), enter the actual name of the server where the CPS backup job is
located.
If a Backup Exec Central Administration Server (CAS) server is specified,
SmartLink must be installed on all managed media servers that are selected
for the job processing. Additionally, if SmartLink is run from a batch file, the
batch file must exist on each managed media server where it might potentially
be 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 OK
to continue. If the credentials are not valid for the specified server, a warning
appears and the wizard does not proceed.
The credentials that are required to access the media server may not be valid
to 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 same
Backup Group as the Continuous Management Server (CMS).
If the credentials are not valid for the Backup Group registry key, a warning
is presented that SmartLink is unable to determine the validity of the Group.
If the credentials are valid, SmartLink determines the extent of the Backup
Group. If the CMS and media server are in the same Backup Group, SmartLink
proceeds. 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 Backup
Exec 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 and
enter the maximum number of entries per individual CPS job and pair. Click
Next.
SmartLink determines the state of the CPS jobs and pairs, and enters the
states into the Backup Exec Log entries. By default, the CPS Log entries are
not limited between backups. This may result in a very large Backup Exec log
file.
12 Click Finish to transfer the CPS job information to the Backup Exec
pre-command.
You can verify that the pre-command was successfully associated with the
Backup Exec job by viewing the job properties in Backup Exec.
Viewing Backup Exec alerts

You 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 and
all the specified CPS jobs are in a good (consistent) state. CPS alerts themselves
are not posted to the Backup Exec alert system.
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.
Type and category name All CPS-related alerts posted to Backup Exec are
Warnings (yellow icon) and indicate a problem.
Message A message or statement describing the condition

that prompted the alert.
Server name The name of the Backup Exec server being backed
up, which is also CPS’s Protection Server.
Job name The name of the Backup Exec job.
About fatal alerts

Certain errors prevent SmartLink from performing its analysis or some part of
its expected behavior, such as retrieving log entries. Each of these conditions
generates a Warning alert, and more than one alert can be generated during a
single run of SmartLink.
Table 9-2 describes the fatal alert messages and conditions.
Table 9-2 Fatal alert messages
Message Condition Solution
SmartLink is unable to contact the Continuous SmartLink is unable to connect Check network connectivity and
Management Service (CMS). The server may to the CMS. that the CMS is running.
be down or a network issue may be preventing
SmartLink from contacting the CMS. No CPS
Backup data validation is possible.
SmartLink has failed to authenticate to the SmartLink cannot authenticate Verify credentials to CMS.
Continuous Management Service to the CMS.
See “Understanding the
<CMSservername>. No CPS Backup data
credentials for using Backup Exec
validation is possible. Check the user name
SmartLink” on page 137.
and password provided to SmartLink.
SmartLink is unable to contact the Continuous General failure CMS errors. This Attempt to restart the services,
Management Service (CMS) alert is a catch-all for and if not successful, contact
non-network and non-credentials Symantec Technical Support.
based errors.
CPS Backup Job <Cpsjobname> - SmartLink Failure to authenticate to a JCD Verify credentials to JCD server.
has failed to authenticate to the JCD Server indicates that SmartLink is
See “Understanding the
<JCDservername>. The Job and Pair Logs are unable to acquire log entries.
credentials for using Backup Exec
Unavailable. However, an alert is generated
SmartLink” on page 137.
because it is a correctable
configuration error.
CPS Backup Job <Cpsjobname> - SmartLink is JCD is unreachable, which has the Check network connectivity and
unable to contact the JCD Server same effect as the failure to that the JCD server is running
<JCDservername>. The server may be down or authenticate. properly.
a network issue may be preventing SmartLink
from contacting the JCD. The Job and Pair Logs
are Unavailable.
CPS Backup Job <Cpsjobname> - SmartLink is General failure for non-network Attempt to restart the JCD
unable to contact the JCD server < and non-credentials based JCD services, and if not successful,
JCDservername>. The Job and Pair Logs are errors. contact Symantec Technical
Unavailable. Support.
Table 9-2 Fatal alert messages (continued)
Message Condition Solution
CPS Backup Job <invalidjobid> - Invalid CPS A specified CPS Job ID is invalid. Verify that the correct job ID has
Backup Job ID. This condition is a correctable been entered.
SmartLink configuration error
and thus generates a top-level
Alert.
CPS Backup Job <Invalidjobname> - Invalid A specified Job name is invalid. Verify that the correct job name
CPS Backup Job Name This condition is a correctable has been entered.
SmartLink configuration error
and thus generates a top-level
Alert.
CPS Backup Job <Cpsjobname> - The The CPS job is in an unknown Check the connectivity between
Continuous Management Service (CMS) and state. In this case, the CMS does the CMS and JCD, and verify that
the CPS Backup JCD server do not have not have the latest information each is running.
consistent Job State information. The actual regarding a job's run state.
state of Job is unknown.
CPS Backup Job <Cpsjobname> - Unable to get Unable to get Pair information. Check the connectivity between
pair information. the CMS and JCD, and verify that
each is running.
CPS Backup Job <Cpsjobname> - Unable to get Unable to get JCD information. Check the connectivity between
JCD information. the CMS and JCD, and verify that
each is running.
CPS Backup Job <Cpsjobname> - Unable to get Unable to get job log information. Check the connectivity between
job log details Information. the CMS and JCD, and verify that
each is running.
About backup pair alerts

If one or more Jobs were discovered to be in an inconsistent state during
SmartLink’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. This
is because there may be hundreds of pairs that are inconsistent and SmartLink
could easily overwhelm the Backup Exec alerts. Additionally, the Alert message
has limited space (400 characters) to report the error. Consequently, this alert is
a 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
Alert Condition Description
CPS Backup Job One or more pairs in one or Review the information for
<cpsjobname> - Exception in more of the CPS jobs are the Exceptions topic box.
One or More CPS Pairs. inconsistent.
See “Exceptions topic box”
on page 145.
Viewing Backup Exec job logs

SmartLink posts detailed information about the CPS backup job in the Backup
Exec Job Logs.
To view Backup Exec job logs
1 On the Backup Exec navigation bar, click Job Monitor.
2 In the Job History pane, select the Backup Exec jobs that are associated with
the 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 time
that 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 Job
to expand the headings.
About CPS backup job log details

The CPS job logs contained in the Backup Exec Job Logs consists of various topic
boxes.
You can review more details about what displays in the various topic boxes on the
job log.
See “Job Operation - Continuous Protection job topic box” on page 144.
See “Command Line Syntax Error topic box” on page 145.
See “Exceptions topic box” on page 145.
See “Backup Exec SmartLink Options topic box” on page 146.
See “Backup Exec SmartLink Run Log topic box” on page 146.
See “CPS Jobs topic boxes” on page 147.
Job Operation - Continuous Protection job topic box

The first topic box, Job Operation - Continuous Protection, provides a summary
statement 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 might
appear for each state.
Table 9-4 CPS summary log messages
Message Description
All CPS backup jobs are good
CPS Backup Jobs are complete or are This message appears if all CPS jobs have completed or are running without
running without errors. errors.
There are one or more problems
Exception in One or More CPS Backup If there are any problems with the CPS jobs or pairs, this message appears
Jobs. in the CPS Log. Additionally, the Exceptions topic box appears later in the
Job Log, which provides details on the specific problems that are encountered
in the CPS jobs.
See “Exceptions topic box” on page 145.
A fatal error has occurred
The SmartLink Command Line Has This message appears when syntax errors are encountered in the SmartLink
Syntax Errors. command line. Additionally, if this message is posted, the Command Line
Syntax Error topic box appears later in the Job Log, which provides details
on the nature of the error.
See “Command Line Syntax Error topic box” on page 145.
SmartLink is unable to connect to the This error might occur for one of the following reasons:
Backup Exec server. (Server:
■ SmartLink may be invoked using invalid Backup Exec credentials, which
<servername> User: <username>
prevents SmartLink from connecting to Backup Exec. For example, this
Pwd: xxxx ... Error:
message appears if all CPS Jobs are good, but invalid Backup Exec
<errorcode>Errors
credentials were provided.
■ SmartLink was not able to acquire the Backup Exec job information from
Backup Exec.
Table 9-4 CPS summary log messages (continued)
Message Description
SmartLink is unable to contact the The server may be down or a network issue may prevent SmartLink from
Continuous Management Server. The contacting the CMS. No CPS Backup data validation is possible.
server may be down or a network
issue may be preventing SmartLink
from contacting the Continuous
Management Server. No backup data
validation on Protection Server is
possible.
SmartLink is unable to contact the The server may be down or a network issue may prevent SmartLink from
Continuous Management Server. contacting the CMS. No CPS Backup data validation is possible.
Command Line Syntax Error topic box

If a syntax error was identified in the command line, the message was posted in
the Job Operation - Continuous Protection topic box. The Command Line Syntax
Error topic box is provided. This topic box contains details of any syntax errors
that are encountered in the SmartLink command line.
Exceptions topic box

If any errors are associated with the CPS jobs or pairs, the message “SmartLink
Command Line has error . . . .” appears in the Job Operation - Continuous Protection
(Summary) topic box.
Additionally, the Exceptions topic box appears, which contains more detail about
the 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 box
that 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
Exception Description
Goodness Criteria The criteria that are evaluated to determine the consistency of a
job are the following:
■ Each pair must be in a consistent state.

■ Each pair must have been consistent since the last time the
associated Backup Exec job was run.
Job Name or ID Not This exception is given when one or more job names or IDs on the
Found SmartLink command line cannot be found on the CMS.
Invalid CPS Job An invalid job that is specified on the SmartLink command line
that does not exist in the CMS database.
Unknown Job State The JCD of a job and the CMS may be unsynchronized. Thus, there
is no way for SmartLink to get an authoritative measure of the
state of the job or any of the pairs in the job. Thus, the job in
question has an entry in the Exceptions error box but does not
have a “Continuous Protection Job” section.
Backup Exec SmartLink Options topic box

The Backup Exec SmartLink Options topic box provides general information on
the CPS backup job such as the following:
■ 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 box

The Run Log topic box is accessed when the -RunLog parameter is included in the
command line.
This topic box provides detailed information on the CPS and backup jobs. The
information that is displayed in this topic box is generally only required by
Technical 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 boxes

Every CPS job that is specified on the SmartLink command line has a topic box
that is displayed in the job logs. This topic box contains all the information that
is related to that job. The title of the box is the name of the CPS job. This box
always contains a header and a details box. If the job has exceptions, then the box
is orange (warning color). Subordinate topic boxes to the CPS jobs topic box are
as 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
Job Header 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 Details Contains job properties that define how the job was configured when the SmartLink command
line was started. The Job Details boxes contain most of the job properties that are found on the
CPS Job Properties page.
Job Log Contains CPS job log entries for the period starting when the Backup Exec job last 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 sorted
in 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/time
fields 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.
Backup Pair One Backup Pair box exists for each pair of the associated CPS job. The title of the box is the
name of the actual CPS pair. If there is an exception associated with the pair, the box title
contains the state of the pair along with a description of the exception condition.
Table 9-6 Subordinate jobs topic boxes (continued)
Pair Header Contains a summary of the pair at the time SmartLink ran. It shows the source and destination
server names, pair state, last started time, last stopped time, destination consistency, and
destination latency.
Destination latency can only be calculated when both servers in a pair are running Continuous
Protection Server version 10 or later.
Pair Log Contains CPS pair log entries for the time period starting from when the owning Backup Exec
job 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 sorted
in 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/time
fields 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.
Chapter 10
Troubleshooting
Server
■ Troubleshooting Continuous Protection Server
■ Installation and upgrade issues
■ Component issues
■ Configuration issues
■ General issues
■ Backup and restore job issues
■ Database maintenance utilities
Troubleshooting Continuous Protection Server

Use the troubleshooting information to find solutions to problems that might
occur in using the product.
For additional troubleshooting information, see the Readme.txt file on the product
CD or go to the Symantec Website.
Installation and upgrade issues

Table 10-1 describes CPS installation issues.
150 Troubleshooting Continuous Protection Server
Installation and upgrade issues
Table 10-1 CPS installation issues
Issue Description
Workgroups and Symantec does not recommend or support mixing the servers hosting the Continuous
domains Management Service and Continuous Protection Agent between workgroups and domains.
Anti-spyware software Before you install CPS, you should disable any anti-spyware software. If you are prompted
for permission to install CPS, click Yes. This is particularly relevant for computers where
the Continuous Protection Agent was push installed, and their users tend to select the
Block option since they may not know what is being installed and may think it is spyware
from the Internet.
Push installing over If a cross-domain trust exists between the computers that you are installing from and to,
domain trust the account that is running from the installing computer must be present in the local
“administrators” group of the computer being push installed to.
NIC failure after If a NIC card fails after installing CPS, the registry key for the new NIC card must be
installing CPS updated for CPS to work properly.
Pathnames with Asian CPS fails to start if CPS has been installed in a directory whose pathname includes
characters characters from Asian languages, including Japanese, Chinese, and Korean. To avoid this
problem, either install CPS in the default installation directory or choose a directory
whose pathname, netgroup name and master server name only includes English characters
(a-z, A-Z, 0-9).
Network load balancing After installing Continuous Protection Server on a computer running Windows Server
service fails to start 2003, you might receive an error message that the Network Load Balancing Service failed
to start. Microsoft reports the cause as: “Although network Load Balancing (NLB) is not
currently installed, some NLB registry keys might be present in the registry.” Although
Microsoft Knowledge Base Article 268437 describes the problem as applying to Windows
2000 Advanced Server, the fix also works for Windows Server 2003.
For more information about network load balancing on Windows Server 2003, go to the
following URL:
www.microsoft.com/technet/prodtechnol/windows2000serv/support/nlbcontb.mspx
Table 10-2 describes a CPS uninstall issue.
Table 10-2 CPS uninstall issue
Issue Description
Uninstall and reinstall If CPS is uninstalled and reinstalled, information in the job logs
loses job history and pair and pair logs is not saved.
logs
For more information about this issue, go to the following URL:
Troubleshooting Continuous Protection Server 151
Component issues
Component issues
Table 10-3 describes CPS administration console issues.
Table 10-3 Administration Console issues
Issue Description
Administration Console The first time that you select a server to do a CPS restore, a wait
may run slowly when cursor appears and it may take several minutes before anything
first run is displayed. Nothing in the console indicates that anything is
happening and a user might think that nothing can be restored.
This delay is caused by the mounting of the snapshots as
volumes. The amount of time it takes to mount a snapshot is
proportional to the size of the snapshot.
Job name and description Consoles running on computers without the corresponding
are in a different language pack that is installed is not able to properly interpret
language than the the job name or description. For example, when a job name is
Administration Console created with Japanese characters, these characters show as
meaningless square boxes when the job is viewed on an English
Console. Be sure that the language packs are installed for all
languages of job names and descriptions that may be used in
the Console.
Table 10-4 describes a Business Server issue.
Table 10-4 Business Server issues
Issue Description
Recovering restore If a Business Server is deleted from the Backup Group, all restore
selections to a restored selections also disappear. If the deleted Business Server is
or replaced Business brought back into the Backup Group or another server is added
Server with the same name as the deleted server, a new CPS backup
job of at least one file can be created and run to resynchronize
the restore selections. This situation requires reinstalling the
Continuous Protection Agent and restarting the
replaced/restored server.
Configuration issues
Table 10-5 describes snapshot and indexing issues.
General issues
Table 10-5 Snapshot and indexing issues
Issue Description
Snapshots fail to index To troubleshoot indexing of snapshots

properly
1 Click Run > Control Panel > Administrative Tools >
Services.
2 Verify that the Backup Exec Continuous Protection

Indexing Component is running (started).
3 Stop and restart the Indexing Component to start a

reindexing of any snapshots that are not indexed.
4 Check the logs for any erroneous entries.
5 Contact Symantec Technical Support.
Adjusting the free disk The ability to search for files is accomplished by a built-in
space for indexing indexing service. The indexing database requires 1 GB of free
disk space on the destination to search for files to restore or to
display a list of recent activity. The number of files with which
you work can vary widely. Without enough free disk space to
handle the number of files, the search is not performed and the
list of files that are found, or the list of recent activity, appears
empty.
If your destination servers do not have 1 GB of free disk space,

the amount of space CPS looks for can be minimized. You can
adjust the amount of free disk space that CPS looks for by adding
the following line to the [SERVER] section of the
Autonomy\suir.cfg file in the product installation folder.
MinFreeSpaceMB=XX
Where XX is the number of free megabytes that are required on

the server to start the indexing service.
General issues
Table 10-6 describes processing efficiency issues.
Table 10-6 Processing efficiency issues
Issue Description
Bandwidth throttling Bandwidth throttling can be implemented using Quality of

and Quality of Service Service (QOS) with network switches and routers. QOS should
(QOS) be implemented on TCP/IP port 20481.
General issues
Table 10-6 Processing efficiency issues (continued)
Issue Description
System may run out of A chronic “nearly out of memory” condition may exist during
memory during intensive periods of intensive input/output processing.
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 amount

drops to 4000 or less (that is, 4 MB) and tends to stay there.
In this state, the system is unresponsive to user input and should

be corrected.
File system input/output An input/output deadlock can occur for the following reasons:
deadlocks may occur
■ CPS is used to continuously back up large databases.
when continuously
■ The input/output activity on these database files is high.
backing up large
database files ■ The host server has fewer than 4 logical CPUs (that is, 4
physical CPUs without hyperthreading, or 2 CPUs with
hyperthreading).
Table 10-7 describes miscellaneous issues.
Table 10-7 Miscellaneous issues
Issue Description
Utility partitions CPS does not recognize utility partitions.
Disabling CPS SNMP If the Windows SNMP service is installed on the computer when
support CPS was installed, CPS's SNMP support is automatically
installed.
For more information how to turn off SNMP support in CPS, go

to the following URL:
Backup and restore job issues
Table 10-7 Miscellaneous issues (continued)
Issue Description
Multiple pairs are CPS throttles the data transmission for all pairs at the
configured to run least-restrictive rate. For example, if a backup job is configured
between the same two to run between two nodes with the bandwidth limited to 20%
computers of a T1 line and another job is configured to run between the
same two computers with bandwidth limited to 50% of a T1 line,
the throughput of both jobs will be combined and run at a rate
of 50% of the T1 line. That is, each job will not run at the 50%
rate, but rather both jobs combined.
The free space on a CPS If the free space of a CPS database volume is exhausted, the
database volume is Sybase Adaptive Server Anywhere 9 server may assert and
exhausted refuse all new connections until the CPS services on that
computer are restarted.
CPS database backup and Database backup and restore capabilities are based on Volume
restore Shadow Copy Service (VSS) Writer Technology. The following
utilities can be used in lieu of using Backup Exec with VSS
capabilities for configuration database backups, or if the user
wants to perform manual backups and verification.
Use cpsDBBackup to create a validated backup image of the CMS

or CPA database.
Use cpsDBValidate to validate and repair the CMS or CPA

database. Only corrupt indexes can be repaired. Restore is a
manual procedure.
For more information about the CPS database maintenance
utilities, go to the following URL:
Backup and restore job issues

Table 10-8 describes a CPS backup job issue.
Database maintenance utilities
Table 10-8 CPS backup issues
Issue Description
Connection outages If the backup job is configured to use the schedule option
Whenever a file changes, it means the “continue backup after
synchronization” is turned on. In this configuration, the job can
become stalled in the running or expiring state if a connection
outage 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 during
the interval between when a source of the job finishes sending
all synchronization data and a destination of the job finishes
replaying all synchronization data. To resolve this situation,
manually cancel the job.
Table 10-9 describes a CPS restore job issue.
Table 10-9 CPS restore job issues
Issue Description
CPS does not allow files CPS does not allow protected files on a Protection Server to be
on a Protection Servers restored to a different location on the Protection Server. To
to be restored to a move files to different locations on the Protection Server, use
different location on the the copy and paste features of Windows Explorer.
Protection Server

CPS includes several powerful utilities for assessing, backing up, restoring, and
repairing the CPS databases.
These utilities include the following:
■ CPS Database Backup and Restore
■ CPS Database Validation and Repair
Any procedures that are associated with CPS database maintenance utilities may
be superseded by the Backup Exec backup and restore jobs. However, if the
Continuous Management Service (CMS) is operating on a server using Windows
2000 (without the Shadow Copy components), these procedures apply.
See “Protecting CPS with Backup Exec” on page 132.
The Database Maintenance utilities are run from the CPS utilities command line
prompt.
To start the CPS utilities

◆ On the Windows taskbar, click Start > All Programs > Symantec > Backup
Exec CPS > CPS Utilities.
CPS database backup and restore

All CPS job configurations are stored in the CMS database. Any loss or corruption
of this information without a backup will require the user to recreate every lost
job. Thus, it is highly recommended that the CMS database be periodically backed
up for data protection and data redundancy.
Likewise, historical information is logged into a database at every Continuous
Protection Agent (CPA). While backing up these databases is not necessary, some
users 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 database
will 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 the
following URL:
CPS database validation and repair

The cpsDBValidate utility validates and optionally repairs or rebuilds a CMS or
CPA database. However this tool requires exclusive access to the database and
thus will restart the CMS or CPA services.
For more information about the CPS database maintenance utilities, go to the
following URL:
Resetting the standard logon

It is possible to convert the CMS or CPA servers in an existing CPS installation to
use integrated logons.
When running in integrated logon mode the CMS and CPA servers no longer
provide database credentials when connecting to their respective databases. This
is because access has been granted to the account under whose context the services
are running. This provides an added level of security to your installation.
Integrated logons cannot be enabled on systems that were installed in non-secure

mode. The CMS or CPA service's log on or run as account must be set to a domain
account and not the local system or a local system account.
All CMS and CPA servers may have integrated logons enabled by running the
SetIntegratedLogin utility. This must be done for each server, and one server at
a time. If integrated logons is enabled on a combined CMS/CPA server, it is enabled
for both services at the same time. Enabling integrated logons requires restarting
the 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 the
same 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 logons
has 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 account

name 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 backups

Attempts to restore a CMS or CPA database from a backup image that was created
before integrated logon was enabled will cause the service in question to fail to
start. This is because the just restored image was never configured for integrated
logons and the current ODBC Data Source is currently configured for integrated
logons. To overcome this issue, you will need to reconfigure the ODBC Data Source
for standard logon.
To recover after restoring a pre-integrated logon database
1 Run the ODBC Data Source Administrator (odbcad32).
2 Click the System DSN 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 server

The login configurations of a combined CMS/CPA server must be kept in
synchronization. That is, both must be configured for integrated login or neither
must be so configured. This creates a problem with restoring old databases that
are backup images taken before the server was reconfigured to use integrated
login.
See “Database maintenance utilities” on page 155.
To restore a combined CMS/CPA server
1 Restore the CMS database from a pre-integrated login backup image. The
CMS server does not start.
2 Edit the ODBC CMS DSN to use standard logins.
See “Issues with integrated logon and database backups” on page 157.
The CMS service can start.
3 SetIntegratedLogin determines that the CMS and the CPA differ and returns
an error.
Currently the only way to overcome this error is to restore both the CMS and
CPA databases from the same backup image set. That is, both databases must
be backed up at the same time, and the backup images should be kept and
restored together as a set.
4 Restore the CMS and CPA databases from a pre integrated login backup image
set.
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 will
now run in integrated login mode.
Appendix A
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 license
provided 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

162 Third-Party Legal Notices
About Third-Party Legal Notices
About Third-Party Legal Notices

Certain third-party software may be distributed, embedded, or bundled with the
Symantec product or recommended for use in conjunction with the installation
and operation of this Symantec product. Such third-party software is separately
licensed by its copyright holder. Use of the third-party software must be in
accordance with its license terms. This appendix contains the licenses which
govern the use of third-party software and its copyright holder's proprietary
notices. Symantec makes no representation or warranty of any kind regarding
such third-party software. Symantec offers no support for such third-party
software and shall have no liability associated with its use.
ACE and TAO are governed under the same license

provided below.
This para is intentionally added.
ACE (The Adaptive Communication Environment)

Douglas C. Schmidt and his research group at Washington University and
University of California, Irvine and Vanderbuilt Univerity.
ACE(TM) is copyrighted by Douglas C. Schmidt and his research group at
Washington University, University of California, Irvine, and Vanderbilt University
Copyright (c) 1993-2003, all rights reserved.
TAO
Douglas C. Schmidt and his research group at Washington University and
University of California, Irvine and Vanderbuilt Univerity.
TAO(TM) is copyrighted by Douglas C. Schmidt and his research group at
Washington University, University of California, Irvine, and Vanderbilt University
Copyright (c) 1993-2003, all rights reserved.
Copyright and Licensing Information for ACE(TM), TAO(TM), CIAO(TM), and
CoSMIC(TM):
ACE(TM), TAO(TM), CIAO(TM), and CoSMIC(TM) (henceforth referred to as "DOC
software") are copyrighted by Douglas C. Schmidt and his research group at
Washington 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 Notices 163
TAO
irrevocably--the DOC software source code and object code produced from the
source, as well as copy and distribute modified versions of this software.
You must, however, include this copyright statement along with code built using
DOC software. You can use DOC software in proprietary software and are under
no obligation to redistribute any of your source code that is built using DOC
software. 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-source
development model. You needn't inform anyone that you're using DOC software
in your software, though we encourage you to let us know so we can promote your
project in the DOC software success stories.
DOC software is provided as is with no warranties of any kind, including the
warranties 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 obligation
on the part of Washington University, UC Irvine, Vanderbilt University, their
employees, or students to assist in its use, correction, modification, or
enhancement. A number of companies around the world provide commercial
support for DOC software, however. DOC software is Y2K-compliant, as long as
the underlying OS platform is Y2K-compliant.
Washington University, UC Irvine, Vanderbilt University, their employees, and
students shall have no liability with respect to the infringement of copyrights,
trade secrets or any patents by DOC software or any part thereof. Moreover, in
no event will Washington University, UC Irvine, or Vanderbilt University, their
employees, 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 at
the Institute for Software Integrated Systems (ISIS) and the Center for Distributed
Object Computing of Washington University, St. Louis for the development of
open-source software as part of the open-source software community. By
submitting comments, suggestions, code, code snippets, techniques (including
that of usage), and algorithms, submitters acknowledge that they have the right
to do so, that any such submissions are given freely and unreservedly, and that
they waive any claims to copyright or ownership. In addition, submitters
acknowledge that any such submission might become part of the copyright
maintained on the overall body of code, which comprises the DOC software. By
making a submission, submitter agree to these terms. Furthermore, submitters
acknowledge that the incorporation or modification of such submissions is entirely
at the discretion of the moderators of the open-source DOC software projects or
their designees.
Apache Struts, Xerces C++ and Tomcat are governed under the same license provided below
The names ACE(TM), TAO(TM), CIAO(TM), CoSMIC(TM), Washington University,

UC Irvine, and Vanderbilt University, may not be used to endorse or promote
products or services derived from this source without express written permission
from 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 permission
from Washington University, UC Irvine, and Vanderbilt University.
If you have any suggestions, additions, comments, or questions, please let me
know.
Douglas C. Schmidt
Apache Struts, Xerces C++ and Tomcat are governed

under the same license provided below
Apache Struts
Xerces C++
Tomcat
Apache Software Foundation
Portions of this program contain components from the Apache Software
Foundation. 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
Tomcat
Definitions.
“License” shall mean the terms and conditions for use, reproduction, and
distribution as defined by Sections 1 through 9 of this document.
“Licensor” shall mean the copyright owner or entity authorized by the copyright
owner that is granting the License.
“Legal Entity” shall mean the union of the acting entity and all other entities that
control, are controlled by, or are under common control with that entity. For the
purposes of this definition, “control” means (i) the power, direct or indirect, to
cause the direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding
shares, or (iii) beneficial ownership of such entity.
“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions
granted by this License.
“Source” form shall mean the preferred form for making modifications, including
but not limited to software source code, documentation source, and configuration
files.
“Object” form shall mean any form resulting from mechanical transformation or
translation 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 included
in 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, that
is based on (or derived from) the Work and for which the editorial revisions,
annotations, elaborations, or other modifications represent, as a whole, an original
work of authorship. For the purposes of this License, Derivative Works shall not
include works that remain separable from, or merely link (or bind by name) to the
interfaces of, the Work and Derivative Works thereof.
“Contribution” shall mean any work of authorship, including the original version
of the Work and any modifications or additions to that Work or Derivative Works
thereof, that is intentionally submitted to Licensor for inclusion in the Work by
the copyright owner or by an individual or Legal Entity authorized to submit on
behalf of the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent to the
Licensor or its representatives, including but not limited to communication on
electronic mailing lists, source code control systems, and issue tracking systems
that are managed by, or on behalf of, the Licensor for the purpose of discussing
and improving the Work, but excluding communication that is conspicuously
Tomcat
marked or otherwise designated in writing by the copyright owner as "Not a

Contribution."
“Contributor” shall mean Licensor and any individual or Legal Entity on behalf
of whom a Contribution has been received by Licensor and subsequently
incorporated within the Work.
Grant of Copyright License.

Subject to the terms and conditions of this License, each Contributor hereby grants
to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of, publicly display,
publicly perform, sublicense, and distribute the Work and such Derivative Works
in Source or Object form.
Grant of Patent License.

Subject to the terms and conditions of this License, each Contributor hereby grants
to 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 to
sell, sell, import, and otherwise transfer the Work, where such license applies
only to those patent claims licensable by such Contributor that are necessarily
infringed 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 patent
litigation against any entity (including a cross-claim or counterclaim in a lawsuit)
alleging that the Work or a Contribution incorporated within the Work constitutes
direct or contributory patent infringement, then any patent licenses granted to
You under this License for that Work shall terminate as of the date such litigation
is filed.
Redistribution.
You may reproduce and distribute copies of the Work or Derivative Works thereof
in 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 of
this License; and
■ You must cause any modified files to carry prominent notices stating that You
changed the files; and
■ You must retain, in the Source form of any Derivative Works that You
distribute, all copyright, patent, trademark, and attribution notices from the
Tomcat
Source form of the Work, excluding those notices that do not pertain to any
part of the Derivative Works; and
■ If the Work includes a "NOTICE" text file as part of its distribution, then any
Derivative Works that You distribute must include a readable copy of the
attribution notices contained within such NOTICE file, excluding those notices
that do not pertain to any part of the Derivative Works, in at least one of the
following places: within a NOTICE text file distributed as part of the Derivative
Works; within the Source form or documentation, if provided along with the
Derivative Works; or, within a display generated by the Derivative Works, if
and wherever such third-party notices normally appear. The contents of the
NOTICE file are for informational purposes only and do not modify the License.
You may add Your own attribution notices within Derivative Works that You
distribute, alongside or as an addendum to the NOTICE text from the Work,
provided that such additional attribution notices cannot be construed as modifying
the License. You may add Your own copyright statement to Your modifications
and may provide additional or different license terms and conditions for use,
reproduction, or distribution of Your modifications, or for any such Derivative
Works as a whole, provided Your use, reproduction, and distribution of the Work
otherwise complies with the conditions stated in this License.
Submission of Contributions.
Unless You explicitly state otherwise, any Contribution intentionally submitted
for inclusion in the Work by You to the Licensor shall be under the terms and
conditions of this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify the terms
of any separate license agreement you may have executed with Licensor regarding
such Contributions.
Trademarks.
This License does not grant permission to use the trade names, trademarks, service
marks, or product names of the Licensor, except as required for reasonable and
customary use in describing the origin of the Work and reproducing the content
of the NOTICE file.
Disclaimer of Warranty.
Unless required by applicable law or agreed to in writing, Licensor provides the
Work (and each Contributor provides its Contributions) on an “AS IS” BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions of TITLE,
Blowfish Encryption
NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR

PURPOSE. You are solely responsible for determining the appropriateness of
using or redistributing the Work and assume any risks associated with Your
exercise of permissions under this License.
Limitation of Liability
In no event and under no legal theory, whether in tort (including negligence),
contract, or otherwise, unless required by applicable law (such as deliberate and
grossly negligent acts) or agreed to in writing, shall any Contributor be liable to
You for damages, including any direct, indirect, special, incidental, or consequential
damages of any character arising as a result of this License or out of the use or
inability 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 commercial
damages or losses), even if such Contributor has been advised of the possibility
of such damages.
Accepting Warranty or Additional Liability.

While redistributing the Work or Derivative Works thereof, You may choose to
offer, and charge a fee for, acceptance of support, warranty, indemnity, or other
liability obligations and/or rights consistent with this License. However, in
accepting such obligations, You may act only on Your own behalf and on Your
sole responsibility, not on behalf of any other Contributor, and only if You agree
to indemnify, defend, and hold each Contributor harmless for any liability incurred
by, or claims asserted against, such Contributor by reason of your accepting any
such warranty or additional liability.
END OF TERMS AND CONDITIONS
Blowfish Encryption
Bruce Schneier
Copyright 2003 by George Anescu
The code in this project is Copyright 2003 by George Anescu. You have the right
to use and distribute the code in any way you see fit as long as this paragraph is
included with the distribution. No warranties or claims are made as to the validity
of the information and [Blowfish] code contained herein, so use it at your own
risk.
Curl/LibCurl
Curl/LibCurl
Daniel Stenberg
Copyright (c) 1996 - 2004, Daniel Stenberg, <daniel@haxx.se>.
All rights reserved.
Permission to use, copy, modify, and distribute this software for any purpose with
or without fee is hereby granted, provided that the above copyright notice and
this 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 WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES
OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other dealings in this
Software without prior written authorization of the copyright holder.
Digital Encryption Standard (DES) - MIT

MIT and Dennis Ferguson
Copyright (c) 1990 Dennis Ferguson. All rights reserved.
Commercial use is permitted only if products which are derived from or include
this 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 of
Technology. All Rights Reserved.
Export of this software from the United States of America may require a specific
license from the United States Government. It is the responsibility of any person
or organization contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute
this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or publicity
pertaining to distribution of the software without specific, written prior
ICU
permission. M.I.T. makes no representations about the suitability of this software

for any purpose. It is provided “as is” without express or implied warranty.
ICU
International Business Machines Corporation
Copyright (c) 1995-2003 International Business Machines Corporation and others.
ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2003 International Business Machines Corporation and others.
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the “Software”), to deal in the
Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the Software
and that both the above copyright notice(s) and this permission notice appear in
supporting documentation.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR
ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be
used in advertising or otherwise to promote the sale, use or other dealings in this
Software without prior written authorization of the copyright holder.
All trademarks and registered trademarks mentioned herein are the property of
their respective owners.
MD5
RSA Data Security, Inc.
Open SSL
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 as
the “RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material
mentioning or referencing this software or this function.
License is also granted to make and use derivative works provided that such works
are identified as “derived” from the RSA Data Security, Inc.
“MD5 Message-Digest Algorithm” in all material mentioning or referencing the
derived work.
RSA Data Security, Inc. makes no representations concerning either the
merchantability of this software or the suitability of this software for any
particular purpose. It is provided “as is” without express or implied warranty of
any kind.
These notices must be retained in any copies of any part of this documentation
and/or software.
Open SSL
The 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 the
OpenSSL License and the original SSLeay license apply to the toolkit. See below
for the actual license texts. Actually both licenses are BSD-style Open Source
licenses. In case of any license issues related to OpenSSL please contact
openssl-core@openssl.org.
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, this
list 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/or
other materials provided with the distribution.
Open SSL
■ All advertising materials mentioning features or use of this software must

display the following acknowledgment:
■ “This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit. (http://www.openssl.org/)”
■ The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to
endorse or promote products derived from this software without prior written
permission. For written permission, please contact openssl-core@openssl.org.
■ Products derived from this software may not be called “OpenSSL” nor may
“OpenSSL” appear in their names without prior written permission of the
OpenSSL Project.
■ Redistributions of any form whatsoever must retain the following
acknowledgment:
■ “This product includes software developed by the OpenSSL Project for use in
the OpenSSL Toolkit (http://www.openssl.org/)”
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS” AND ANY
EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL
PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) 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
(eay@cryptsoft.com). This product includes software written by Tim Hudson
(tjh@cryptsoft.com).
Original SSLeay License

Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
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 following
conditions are adhered to. The following conditions apply to all code found in this
distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The
Open SSL
SSL documentation included with this distribution is covered by the same copyright
terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code
are not to be removed.
If this package is used in a product, Eric Young should be given attribution as the
author of the parts of the library used. This can be in the form of a textual message
at program startup or in documentation (online or textual) provided with the
package.
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 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/or
other materials provided with the distribution.
■ All advertising materials mentioning features or use of this software must
display the following acknowledgement:
■ "This product includes cryptographic software written by Eric Young
(eay@cryptsoft.com)"
■ The word 'cryptographic' can be left out if the routines from the library being
used are not cryptographic related :-).
■ If you include any Windows specific code (or a derivative thereof) from the
apps directory (application code) you must include an acknowledgement:
■ "This product includes software written by Tim Hudson
(tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA,
OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.
ReportCtrl.h.2.0.1
The licence and distribution terms for any publically available version or derivative
of this code cannot be changed. i.e. this code cannot simply be copied and put
under another distribution licence [including the GNU Public Licence.]
ReportCtrl.h.2.0.1
Maarten Hoeben
Copyright Maarten Hoeben
Author: Maarten Hoeben
E-mail: hamster@xs4all.nl
Implementation of the CReportCtrl and associated classes.
This code may be used in compiled form in any way you desire. This file may be
redistributed unmodified by any means PROVIDING it is not sold for profit without
the authors written consent, and providing that this notice and the authors name
and 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 product
may cause.
STLport
Boris Fomitchev
Copyright 1999,2000 Boris Fomitchev
Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-free
license to use STLport and its documentation without fee.
By downloading, using, or copying STLport or any portion thereof, Licensee agrees
to abide by the intellectual property laws and all other applicable laws of the
United States of America, and to all of the terms and conditions of this Agreement.
Licensee shall maintain the following copyright and permission notices on STLport
sources 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 without
fee, provided the above notices are retained on all copies. Permission to modify
Java 2 Runtime Environment
the code and to distribute modified code is granted, provided the above notices
are retained, and a notice that the code was modified is included with the above
copyright notice.
The Licensee may distribute binaries compiled with STLport (whether original or
modified) 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 conditions
provided 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 its
documentation for any purpose is hereby granted without fee, provided that the
above copyright notice appear in all copies and that both that copyright notice
and this permission notice appear in supporting documentation. Hewlett-Packard
Company makes no representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied warranty.
and this permission notice appear in supporting documentation. Silicon Graphics
makes no representations about the suitability of this software for any purpose.
It is provided "as is" without express or implied warranty.
and this permission notice appear in supporting documentation. Moscow Center
for SPARC Technology makes no representations about the suitability of this
software for any purpose. It is provided "as is" without express or implied warranty.

Sun Microsystems, Inc.
© 2005 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc.
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 SOFTWARE
IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT
ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT
AND SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE
READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS
SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT.
INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT" BUTTON AT THE
BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY
ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE
AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT
CONTINUE.
DEFINITIONS.
"Software" means the identified above in binary form, any other machine readable
materials (including, but not limited to, libraries, source files, header files, and
data files), any updates or error corrections provided by Sun, and any user manuals,
programming guides and other documentation provided to you by Sun under this
Agreement. "Programs" mean Java applets and applications intended to run on
the Java 2 Platform, Standard Edition (J2SETM platform) platform on Java-enabled
general purpose desktop computers and servers.
LICENSE TO USE.
Subject to the terms and conditions of this Agreement, including, but not limited
to the Java Technology Restrictions of the Supplemental License Terms, Sun
grants you a non-exclusive, non-transferable, limited license without license fees
to reproduce and use internally Software complete and unmodified for the sole
purpose of running Programs. Additional licenses for developers and/or publishers
are granted in the Supplemental License Terms.
RESTRICTIONS.
Software is confidential and copyrighted. Title to Software and all associated
intellectual property rights is retained by Sun and/or its licensors. Unless
enforcement is prohibited by applicable law, you may not modify, decompile, or
reverse engineer Software. You acknowledge that Licensed Software is not designed
or intended for use in the design, construction, operation or maintenance of any
nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty
of fitness for such uses. No right, title or interest in or to any trademark, service
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 in
the 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 remedy
and Sun's entire liability under this limited warranty will be at Sun's option to
replace Software media or refund the fee paid for Software. Any implied warranties
on the Software are limited to 90 days. Some states do not allow limitations on
duration of an implied warranty, so the above may not apply to you. This limited
warranty gives you specific legal rights. You may have others, which vary from
state to state.
DISCLAIMER OF WARRANTY.
UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT
THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
LIMITATION OF LIABILITY.
TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING
OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN
IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no
event 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 its
essential purpose. Some states do not allow the exclusion of incidental or
consequential 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 Software
may download, install, and execute applets, applications, software extensions,
and updated versions of the Software from Sun ("Software Updates"), which may
require you to accept updated terms and conditions for installation. If additional
terms and conditions are not presented on installation, the Software Updates will
be considered part of the Software and subject to the terms and conditions of the
Agreement.
SOFTWARE FROM SOURCES OTHER THAN SUN.

You acknowledge that, by your use of optional features of the Software and/or by
requesting services that require use of the optional features of the Software, the
Software may automatically download, install, and execute software applications
from sources other than Sun ("Other Software"). Sun makes no representations
of a relationship of any kind to licensors of Other Software. TO THE EXTENT NOT
PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE
FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED
TO THE USE OF OR INABILITY TO USE OTHER SOFTWARE, EVEN IF SUN HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states do not
allow the exclusion of incidental or consequential damages, so some of the terms
above may not be applicable to you.
TERMINATION.
This Agreement is effective until terminated. You may terminate this Agreement
at any time by destroying all copies of Software. This Agreement will terminate
immediately without notice from Sun if you fail to comply with any provision of
this Agreement. Either party may terminate this Agreement immediately should
any Software become, or in either party's opinion be likely to become, the subject
of 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 US
export control laws and may be subject to export or import regulations in other
countries. You agree to comply strictly with all such laws and regulations and
acknowledge that you have the responsibility to obtain such licenses to export,
re-export, or import as may be required after delivery to you.
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 and
other brand designations ("Sun Marks"), and you agree to comply with the Sun
Trademark and Logo Usage Requirements currently located at
http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks
inures 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's
rights in Software and accompanying documentation will be only as set forth in
this 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 and
controlling 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 Agreement
will remain in effect with the provision omitted, unless omission would frustrate
the 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 subject
matter. It supersedes all prior or contemporaneous oral or written communications,
proposals, representations and warranties and prevails over any conflicting or
additional terms of any quote, order, acknowledgment, or other communication
between the parties relating to its subject matter during the term of this
Agreement. No modification of this Agreement will be binding, unless in writing
and signed by an authorized representative of each party.
SUPPLEMENTAL LICENSE TERMS

These Supplemental License Terms add to or modify the terms of the Binary Code
License Agreement. Capitalized terms not defined in these Supplemental Terms
shall have the same meanings ascribed to them in the Binary Code License
Agreement . These Supplemental Terms shall supersede any inconsistent or
conflicting terms in the Binary Code License Agreement, or in any license contained
within the Software.
■ A. Software Internal Use and Development License Grant. Subject to the terms
and conditions of this Agreement, including, but not limited to the Java
Technology Restrictions of these Supplemental Terms, Sun grants you a
non-exclusive, non-transferable, limited license without fees to reproduce
internally and use internally the Software complete and unmodified (unless
otherwise 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 this
Agreement, including, but not limited to the Java Technology Restrictions of
these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and distribute the Software, provided
that (i) you distribute the Software complete and unmodified (unless otherwise
specified in the applicable README file) and only bundled as part of, and for
the sole purpose of running, your Programs, (ii) the Programs add significant
and primary functionality to the Software, (iii) you do not distribute additional
software intended to replace any component(s) of the Software (unless
otherwise specified in the applicable README file), (iv) you do not remove or
alter any proprietary legends or notices contained in the Software, (v) you only
distribute the Software subject to a license agreement that protects Sun's
interests consistent with the terms contained in this Agreement, and (vi) you
agree to defend and indemnify Sun and its licensors from and against any
damages, costs, liabilities, settlement amounts and/or expenses (including
attorneys' fees) incurred in connection with any claim, lawsuit or action by
any third party that arises or results from the use or distribution of any and
all Programs and/or Software.
■ C. License to Distribute Redistributables. Subject to the terms and conditions
of this Agreement, including but not limited to the Java Technology Restrictions
of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and distribute those files specifically
identified 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 bundled
as part of Programs, (ii) you do not distribute additional software intended to
supersede any component(s) of the Redistributables (unless otherwise specified
in the applicable README file), (iii) you do not remove or alter any proprietary
legends or notices contained in or on the Redistributables, (iv) you only
distribute the Redistributables pursuant to a license agreement that protects
Sun's interests consistent with the terms contained in the Agreement, (v) you
agree to defend and indemnify Sun and its licensors from and against any
damages, costs, liabilities, settlement amounts and/or expenses (including
attorneys' fees) incurred in connection with any claim, lawsuit or action by
any third party that arises or results from the use or distribution of any and
all Programs and/or Software.
■ D. Java Technology Restrictions. You may not modify the Java Platform
Interface ("JPI", identified as classes contained within the "java" package or
any subpackages of the "java" package), by creating additional classes within
the JPI or otherwise causing the addition to or modification of the classes in
the 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 to
third party software developers for the purpose of developing additional
software which invokes such additional API, you must promptly publish broadly
an accurate specification for such API for free use by all developers. You may
not create, or authorize your licensees to create, additional classes, interfaces,
or subpackages that are in any way identified as "java", "javax", "sun" or similar
convention as specified by Sun in any naming convention designation.
■ E. Source Code. Software may contain source code that, unless expressly
licensed for other purposes, is provided solely for reference purposes pursuant
to the terms of this Agreement. Source code may not be redistributed unless
expressly provided for in this Agreement.
■ F. Third Party Code. Additional copyright notices and license terms applicable
to portions of the Software are set forth in the
THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions
of any third party opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and
limitation of liability provisions in paragraphs 5 and 6 of the Binary Code
License Agreement shall apply to all Software in this distribution.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, California 95054, U.S.A. (LFI#135955/Form ID#011801)
Appendix B
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 Server

Symantec products meet federal accessibility requirements for software as defined
in Section 508 of the Rehabilitation Act.
Keyboard shortcuts are available for all graphical user interface (GUI) operations
and menu items. Symantec products are compatible with operating system
accessibility settings as well as a variety of assistive technologies. All manuals
are provided as accessible PDF files, and the online help is HTML displayed in a
help viewer window.
All program functions and menu items are accessible using the keyboard
exclusively. Continuous Protection Server uses standard operating system
navigation keys and keyboard shortcuts. For its unique functions, Continuous
Protection Server uses its own keyboard shortcuts.
Items in the task pane that do not have keyboard shortcuts are accessed by using
the operating system’s “mouse keys”. This enable you to control the mouse through
the numerical keyboard.
184 Maintaining accessibility
About general keyboard navigation in Continuous Protection Server
About general keyboard navigation in Continuous

Protection 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 the
current active tab, radio button, or check box is enclosed within a rectangle that
is formed by dotted lines. These areas are said to have focus and respond to
commands.
All Symantec GUIs use keyboard navigation standards for the following:
■ The TAB key moves the focus to the next active area, field, or control, following
a preset sequence. SHIFT+TAB moves the focus in the reverse direction through
the 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 field
or command button shifts the focus to that field or button.
■ Either ENTER or the SPACEBAR activates your selection. For example, after
pressing the TAB key to select Next in a wizard panel, press the SPACEBAR to
display the next screen.
■ SHIFT+F10 provides access to context menus.
About keyboard navigation in dialog boxes

Dialog boxes contain groups of controls that are necessary to set options or settings
for programs.
The following are some general rules about dialog box navigation:
■ The TAB key moves focus between controls within the dialog box along a preset
sequence.
■ Controls displaying a mnemonic (an underlined letter) can be selected
regardless of focus by typing ALT and the underlined letter.
■ A dark border indicates the default command button. Press Enter at any time
to 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 accessibility 185
Using keyboard shortcuts
■ 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 of
option controls, or groups of page tabs.
■ Items that cannot be changed are not visited by the TAB key sequence. Options
that 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 also
can occur in other contexts. The same navigation standards apply.
List Boxes
List boxes display a column of available choices.
Different kinds of list boxes exist with additional navigation conventions such as
the following:
■ Drop-down list boxes by default show only the selected item. A small button
to the right of the control will show a downward-pointing arrow. Select the
arrow to display more items from the list box. If there are more choices than
can 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. The
TAB 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 down
CTRL+navigation keys to select or clear additional items or blocks of items.
Using keyboard shortcuts

All menu items can be selected by using accelerator or mnemonic keyboard
shortcuts. An accelerator is a key combination that provides shortcut access to a
GUI function. A mnemonic (sometimes referred to as a “hot key”) is a single-key
equivalent (used in combination with the ALT key) for selecting GUI components
such as menu items. The mnemonic “hot key” letter is underlined in the GUI.
Routine functions such as opening, saving, and printing files can be performed
using the standard Microsoft keyboard shortcuts. Other menu items are unique
to Continuous Protection Server.
Table B-1 describes the keyboard shortcuts that are unique to Continuous
Protection Server.
Setting accessibility options
Table B-1 Keyboard shortcuts that are unique to Continuous Protection Server
Continuous Continuous Result

Protection Server Protection Server
accelerator mnemonic
ALT F The File menu expands. On the File menu, you can create new jobs,
devices and media, print selected items, view properties, or exit
Continuous Protection Server.
ALT E The Edit menu expands. On the Edit menu, you can rename, delete,
copy, and select items. In addition, you can work with selection lists
and search catalogs.
ALT V The View menu expands. On the View menu, you can change the
information that displays on the screen. The options on the View menu
change according to which item is selected on the navigation bar.
ALT T The Tools menu expands. The Tools menu provides many important
options for working with Continuous Protection Server, including
starting and stopping services, using device and media operations,
using Wizards, and setting default options.
ALT W The Window menu expands. Use the Window menu to move to a new
window or view.
ALT H The Help menu expands. Use the Help menu to access Continuous
Protection Server documentation and various Symantec Web sites.
Select secondary menu items by opening the main menu and using the UP or
DOWN ARROW key until the item you want to work with is highlighted. Press the
RIGHT ARROW key to open a submenu, and ENTER to select your choice.

Symantec software responds to operating system accessibility settings.
Symantec products are compatible with Microsoft's accessibility utilities. In
Windows 2000, accessibility options involving keyboard responsiveness, display
contrast, alert sounds, and mouse operation can be set through the Control Panel.
Accessibility features are primarily for the English version. Localized versions of
this product include support for keyboard (mouseless) navigation using accelerator
keys and mnemonic keys.
While all graphics in Symantec documentation are readable- by screen readers,
setting your screen reader to ignore graphics improves performance.
Maintaining accessibility 187
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
> Accessibility Wizard.
Glossary
Administration Console The interface that the administrator uses to manage operations in CPS, such as
setting backup destinations, creating backup or restore jobs, and monitoring CPS
processes and alerts.
administrator rights The credentials that enable a person to make systemwide changes to a domain or
computer, install programs, and access all files. The administrator user account
has full access to other user accounts. Administrator rights also enable the person
to 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 user
interaction or acknowledgment.
backup destination The location on a Protection Server where the files that are backed up from a
Business 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 retrieve
files. 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 Management
Service. Files can be backed up only to a Protection Server that is in the same
Backup Group as the Business Server.
backup job An operation that has been scheduled for processing by the Continuous
Management Service. For example, if you make selections and submit a backup
that is based on those selections, you have created a backup job. Jobs contain
source and destination information, settings, and a schedule. Every type of backup
job 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-time
events, periodically run jobs, or continuous processes. Administrators can set or
change 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 in
the event of a loss.
190 Glossary
Business Server A local or remote server where users save files and folders as part of their daily
work. A Business Server is the source of a backup job and must have a Continuous
Protection Agent installed.
CMS (Continuous The primary control of the Continuous Protection Server processes. The CMS
Management Service) maintains a database with all command and control information, and configures
the Protection Agents according to settings that are sent from the Administration
Console.
continuous backup A backup job that runs continuously, thereby allowing any changes to be backed
up as they occur.
CPA (Continuous The Continuous Protection Agent is a software collection that must be installed
Protection Agent) on each computer in a Backup Group. This agent uses a file system component
and file replication technology to enable continuous data protection between
computers in the Backup Group.
CPS Network Helper A CPS component that allows communications within Continuous Protection
Service Server and with Backup Exec. The Network Helper Service was formerly known
as the Enterprise Network Layer (ENL).
destination server The server in the Continuous Protection Server network to which information is
written during the job process. In a backup job, the information is copied from
the Business Servers (sources) to a Protection Server (destination).
EFS (Encrypting File A Microsoft Windows technology that lets you store information on disk in an
System) encrypted 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 specified
otherwise in the retention settings.
Indexing component The Indexing component maintains a directory for the files that are available to
user file retrieval using the Web Restore Server Component and Backup Exec
Retrieve. The Indexing component is an optional feature and should be installed
on any server that will be accessed by users for file retrieval using Backup Exec
Retrieve. The Indexing component supports searches by file, file versions and
recent activity.
infrastructure The underlying foundation or basic framework of the Backup Group. Continuous
Protection 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 backed
up from and to, when the data will be backed up, and other settings. Similar jobs
are defined to restore the data.
job log The results of a job and are created when a job runs. You can review job logs to
find job errors and details.
Glossary 191
periodic backup A backup job that runs on timed intervals, such as Monday through Friday, every
12 hours.
permissions The credentials that enable a particular user to access a particular resource in a
shared network environment. For example, users are granted permissions to
access files, directories, and printers.
Protection Server A Protection Server is the destination of data that is backed up by CPS from
Business 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 A CPS uses the Symantec Backup Exec Remote Agent for Windows Systems
Windows Systems (Remote Agent) to access System State information for backup and restore. Remote
Agent is an optional component and should be installed on any CPS Business
Server that needs to have its System State protected. Remote Agent should also
be installed on the Protection Server and Continuous Management Service if they
will be protected by Symantec Backup Exec.
restore job A job defines what data is to be restored, from what computers the data will be
restored 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. You
can store snapshots up to a limit that is determined by your underlying snapshot
technology. For most installations, this limit is approximately 64 snapshots per
destination. This limit may vary considerably if alternative snapshot providers
are installed.
scheduled backup A backup job that runs on a set schedule. Three kinds of scheduled backup jobs
are used in Continuous Protection Server: regularly scheduled, periodically
scheduled, and continuous. Regularly scheduled backup jobs run on specific days
at a specific time, every week. Periodically scheduled backup jobs run on specific
days at timed intervals, such as every 12 hours. Continuously scheduled backup
jobs 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 as
CPS. SmartLink enables the status of backup jobs that are created in Continuous
Protection 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 files
to be backed up. This computer must have a Continuous Protection Agent installed.
192 Glossary
storage space The disk drive space on the servers in the Continuous Protection Server Backup
Group. Storage space generally refers to available disk space.
strategic backup plan The philosophy of using multiple types of backup jobs to protect your
organization’s information. A strategic backup plan generally uses several layers
of backups to protect different types of information.
strategic naming The philosophy of naming files and backup destinations in a meaningful way.
conventions Rather than naming backup destinations sequentially such as Backup01, Backup02,
and Backup03, destination names are based on physical office locations, functional
business units, or other meaningful criteria. Therefore, when viewing a list of
backup destinations, the destinations are differentiated from each other and are
easier to find information.
system information The Windows operating system includes data that requires special handling to
protect and restore properly. This data, referred to as “system information” in
CPS, contains different information depending on the specific version of Windows
that is installed on the system. For Windows 2000 systems, this includes a set of
data that is called System State and that includes various operating system files
and registry information. For those systems that support Volume Shadow Copy
Services (VSS), the system information consists of key elements of Shadow Copy
Components including System State and Service State.
system resources The parts that make up or operate computer systems or networks such as client
computers, servers, printers, cables, modems, bandwidth, memory, or mother
boards. 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 is
a Certificate Services database, the Certificate Services database is also included.
If the server is a domain controller, the data also includes the Active Directory
services database and SYSVOL directory. The System State data is backed up and
restored only as a collection, never individually.
Web Restore Server The Web Restore Server component is a feature of the CMS that makes available
component versioned copies (snapshots) of files for user retrieval to their workstations.
Index
Symbols alerts (continued)

64-bit support 20 messages 140
properties 140
responding to 129
A SmartLink
accessibility pairs 142
dialog boxes 184 viewing 128
keyboard shortcuts 185 active 128
overview 183 history 128
settings 186 properties 129
Active Directory 102 alerts view 57
Adaptive Server Anywhere 35, 37 AlwaysDoRegionAnalysis parameter 75
adding scripts 96 ASA directory 35
Administration Console assistant view 53
alerts view 57 autonomy directory 35
assistant view 53
backup job properties 57
credentials 52 B
defined 15 backup destinations
general features 52 adding 65
information desk view 54 credentials 65
job monitor view 57 deleting 67
menu bar 52 description 65
minimum requirements 32 managing 65
navigation bar 52 properties 56
preview pane 53 renaming 67
restore view 57 Backup Exec
selection pane 53 alerts 140
server properties 55 job logs
setup view 54 accessing 143
setup view properties 55 job selection for backup 139
starting 52 media server credentials 139
status bar 53 protecting
system summary view 54 Business Servers 135
task pane 52 Continuous Management Service 134
views Continuous Protection Server 132
general 53 CPS databases 134
Administration Service 36 Protection Servers 134
AlertGroomFrequency parameter 75 snapshots 135
alerts 127 restoring
deleting 130 Business Servers 137
fatal 140 Continuous Management Service 135
194 Index
Backup Exec (continued) bandwith

restoring (continued) limiting 96
CPS 135 batch files 138
Protection Servers 136 BroadcastAddress parameter 76
specifying a media server 139 BroadcastHops parameter 76
Backup Exec Retrieve Broker Services, services 36
description 15–16 Business Servers
end users, requirements for using 112 configuring 59
requirements for installing 110 description 14
troubleshooting 118 installing 43
backup group managing 59
defined 14 minimum requirements 30
moving servers between 62 uninstalling 48
backup jobs
adding scripts 96 C
alert history 128
Central Admin Server environments 139
alert properties 129
command-line syntax
alerts posted to Backup Exec 140
errors 145
changing bandwith 96
complete installation 37
changing schedules 94
configuration troubleshooting 151
creating 88
Configuration Writer, services 36
credentials 90
configuring Backup Exec Retrieve 115
filtering alerts 128
ConnectionPooling parameter 76
filters 91
continuous backups
including and excluding information 91
description 22
managing
plans 22
alerts 127
Continuous Management Service
statuses 122
defined 15
manual operation 97
system requirements 31
pairs 122
Continuous Protection Server
properties 57
components 14
schedules 21
credentials 38
states 123
database backup and restore 154
status 122
databases 134
storing snapshots 71
documentation 23
viewing the status 122
drivers 36
backup schedules
firewall support 33
continuous
installation modification 47
description 22
installation upgrade 46
periodic
installing 37
description 22
integrating with Backup Exec 131
scheduled
invalid jobs 146
description 22
job report 125
backup strategies
jobs topic box 126, 147
considerations 21
key tasks 19
periodic backups 22
monitoring jobs 122
regular backups 22
overview 13
bandwidth limiting 96
service account 29, 41
Services 36
Index 195
Continuous Protection Server (continued) Environment Check 27

Services Manager 63 Evaluation version 39
starting 52 exceptions topic box 145
tunable parameters 75 Exchange protection 20
uninstalling 47
use model 16 F
cpssernum.xml file 39
FFXPort parameter 78
credentials
file access
Administration Console 52
secured in Backup Exec Retrieve 106
backup destinations 65
files and directories
Backup Exec media server 139
restoring 100
CPS service account 29
FilteredIDList parameter 78
creating backup jobs 90
filters
installing CPS 38
deleting 94
push installing CPS 44
description 91
SmartLink 137
include and exclude 92
modifying 93
D firewall support 33
data protection 21
data source G
adding 115
Gateway (ENL\System) parameter 78
deleting 117
Gateway (Network.TCPIP) parameter 78
editing 117
Gateway (Network.UDPv6) parameter 78
options 116
database backup and restore 156
database directory 35 H
database maintenance utilities 155 hardware requirements 31
database services 36 Help
database validation and repair 156 online 24
DaysToKeepAlertItems parameter 76 history
DaysToKeepDeletedSnapshots parameter 76 alerts 128
DelayDirChangeNotifications parameter 77
deploying Silverlight in your organization 113 I
destinations Indexing directory 42
installing 37 Indexing Root parameter 79
uninstalling 47 indexing state
Directory Services Restore Mode 102 snapshots 73
DoEventLog parameter 77 information desk view 54
domain security mode 64 install directory 35
domain trust 30 installation
drivers directory 35 about 26
complete 37
E Environment Check 27
EnableDebugConsole parameter 77 Evaluation version 39
EnableLogFile parameter 77 modifying 47
EnableTimestamp parameter 77 prerequisites 25
Encrypting File System push install 43
defined 88 upgrading 46
196 Index
installation logs M
viewing 42 Master (ENL\System) parameter 80
installing Backup Exec Retrieve 113 MaxDirSize parameter 80
MaxLogSize (ENL) parameter 80
J MaxLogSize parameter 80
job details topic box 147 MaxPacketSize (Network.TCPIP) parameter 80
job ID MaxPacketSize (Network.UDPv6) parameter 81
not found 146 MaxRAPerCentChange parameter 81
job logs menu bar 52
job header 147 MinRASizeInKb parameter 81
SmartLink 143 monitoring processes 122
topic box 147 MsBetweenRallyChecks parameter 81
viewing 143
job monitor view 57 N
job name NamedObjectsRoot parameter 81
not found 146 navigation bar 52
job pairs NetBios 34
alerts 142 Network (ENL\System) parameter 81
description 122 Network Helper services 34, 36
exceptions 145 network load balancing service 38, 150
job report 125 network shares
job state restoring 103
unknown 146 NeverDoRegionAnalysis parameter 82
job states 122 NumberOfLogs parameter 82
job status 124
jobs
monitoring 122
O
Journal directory 42 OutboundJournalCleanupSize parameter 82
JournalRoot parameter 79 OutboundJournalNominalSize parameter 82
OutboundSyncJournalLimit parameter 82
L
latency
P
target 127, 148 pair header topic box 148
license keys 39 pair log topic box 148
limiting bandwidth 96 pair status 124
LiveUpdate 20 pairs
local system object cache 45 job 122
log entries parameters
limiting 140 tunable
parameter 147 AlertGroomFrequency 75
LogOpenFileTableOncePerSet parameter 79 AlwaysDoRegionAnalysis 75
LogPath (EFC) parameter 79 BroadcastAddress 76
LogPath parameter 79 BroadcastHops 76
logs changing values 85
viewing installation 42 ConnectionPooling 76
Logs directory 35 DaysToKeepAlertItems 76
LogText parameter 80 DaysToKeepDeletedSnapshots 76
DelayDirChangeNotifications 77
DoEventLog 77
Index 197
parameters (continued) periodic backup

tunable (continued) description 22
EnableDebugConsole 77 permissions
EnableLogFile 77 backup destinations 65
EnableTimestamp 77 media server 139
FFXPort 78 port settings
FilteredIDList 78 Services Manager 34
Gateway (ENL\System) 78 Settings Utility 34
Gateway (Network.TCPIP) 78 pre/post commands
Gateway (Network.UDPv6) 78 adding 96
IndexingRoot 79 runtime settings 138
JournalRoot 79 PreferredAddress (Network.TCPIP) parameter 83
LogOpenFileTableOncePerSet 79 PreferredAddress (Network.UDPv6) parameter 83
LogPath 79 PreferredNIC (Network.TCPIP) parameter 83
LogPath (EFC) 79 PreferredNIC (Network.UDPv6) parameter 83
LogText 80 preview pane 53
Master (ENL\System) 80 properties
MaxDirSize 80 alerts 129
MaxLogSize 80 backup destination 56
MaxLogSize (ENL) 80 backup jobs 57
MaxPacketSize (Network.TCPIP) 80 server 55, 59
MaxPacketSize (Network.UDPv6) 81 Protection Agent
MaxRAPerCentChange 81 defined 15
MinRASizeInKb 81 service 36
MsBetweenRallyChecks 81 Protection Server
NamedObjectsRoot 81 description 14
Network (ENL\System) 81 minimum requirements 31
NeverDoRegionAnalysis 82 push installation 43
NumberOfLogs 82
OutboundJournalCleanupSize 82 R
OutboundJournalNominalSize 82
registry entries 74
OutboundSyncJournalLimit 82
Remote Agent for Windows Systems 15
PreferredAddress (Network.TCPIP) 83
renaming backup folders 65
PreferredAddress (Network.UDPv6) 83
report
PreferredNIC (Network.UDPv6) 83
job 125
PreferredNIC(Network.TCPIP) 83
requirements for end users
registry entries 74
Backup Exec Retrieve 112
ReservedFreeDiskSpace 83
requirements for installing
RxRmsStaticPort 84
Backup Exec Retrieve 110
RxRsaStaticPort 84
ReservedFreeDiskSpaceparameter 83
Schedule 84
responding to alerts 129
SerializeIrpLogging 84
restore view 57
ShareInfoAsSingleComponent 84
retention policies
Socket 84
snapshots 69, 71
UsePrivateFindFileMethod 85
run log topic box 146
using Settings Utility 75
RunLog parameter 146
Verbose (ENL) 85
RxRmsStaticPort parameter 84
VolumeLevel 85
RxRsaStaticPort parameter 84
198 Index
S SmartLink (continued)
Schedule parameter 84 job logs
scheduled backups summary messages 145
description 22 job topic box 143
schedules options topic box 146
changing 94 topic boxes
changing for snapshots 71 command-line syntax errors 145
continuous backups 88 CPS jobs 147
snapshots 70 exceptions 145
schedules for jobs job details 147
troubleshooting 90 job log 147
scripts 96 options 146
secured file access 106 pair header 148
security modes run log 146
domain 64 snapshots
workgroup 64 changing schedules 71
selection pane 53 creating 69
SerializeIrpLogging parameter 84 creating on demand 69
server properties 55 deleting 73
servers indexing state 73
managing properties 59 managing 68
moving between backup groups 62 reasons for deleting 72
service account 29 reindexing 152
Services retention 71
Administration Service 36 retention policies 69
Broker Services 36 scheduling 70
Configuration Writer 36 storing 71
database 36 viewing history 72
Network Helper 36 Socket parameter 84
Protection Agent 36 source properties 59
System State Manager 36 status
services manager 63 job and pair 124
setintegratedlogin utility 156 status bar 53
Settings Utility 20, 74 Symantec
setup view 54 knowledge base 24
setup view properties 55 LiveUpdate 20
Shadow Copy Components 88 Technical Support 23
Shadow Storage System Cache directory 42
changing location 66 System Information 102
ShareInfoAsSingleComponent parameter 84 system requirements
Silverlight hardware 31
deploying in your organization 113 minimum 30
SmartLink System State
alerts backup schedule 102
categories 140 Manager 36
credentials 137 restore to an Active Directory 102
description 137 restoring 101
fatal alerts 140 system summary view 54
job log descriptions 143
Index 199
T V
target latency 127, 148 Verbose (ENL) parameter 85
task pane 52 VolumeLevel parameter 85
tasks available in Backup Exec Retrieve 108
Technical Support 23 W
troubleshooting 149
Windows File Sharing 34
troubleshooting issues
workgroup
Administration Console 151
environment 30
anti-spyware software 150
security mode 64
Backup Exec compatibility 28
browsers supported 150
business servers 151
configuration 151
connection outages 155
CPS backup jobs 155
CPS components 151
CPS configurations 151
CPS restore jobs 155
database backup and restore 154, 156
database maintenance 155
database validationa nd repair 156
disk space for indexing 152
file system filter drivers 29
installation 150
network load balance 150
NIC failure 150
pathnames with Asian characters 150
processing efficiency 153
push installing over domain trust 150
services account 29
setintegratedlogin utility 156
snapshot schedules 90
SNMP support 153
system state backup and restore 155
uninstalling CPS 150
utility partitions 153
workgroups and domains 150
U
uninstallation
Business Server 48
Continuous Protection Server 47
destinations 47
sources 48
uninstalling 118
use case 106
UsePrivateFindFileMethod parameter 85

Backup Exec Continuous Protection Server 2010 Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Backup Exec Continuous Protection Server 2010 Guide

Uploaded by

Copyright:

Available Formats

Symantec Backup Exec

Continuous Protection Server

Documentation version: 2010

Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec

Printed in the United States of America.

Contacting Technical Support

Licensing and registration

Asia-Pacific and Japan customercare_apac@symantec.com

Europe, Middle-East, and Africa semea@symantec.com

North America and Latin America supportsolutions@symantec.com

Additional enterprise services

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

Chapter 2 Installing Continuous Protection Server ........................ 25

Drivers that are installed ......................................................... 36

Chapter 3 Using the Administration Console ................................... 51

Chapter 4 Configuring Continuous Protection Server .................... 59

Defining a retention policy for a snapshot .................................. 71

Chapter 5 Backing up data ................................................................... 87

Chapter 6 Restoring data ...................................................................... 99

Chapter 7 Using Backup Exec Retrieve ............................................ 105

Installing Backup Exec Retrieve .................................................... 113

Chapter 8 Monitoring CPS processes ............................................... 121

Chapter 9 Using Continuous Protection Server with Backup

Chapter 10 Troubleshooting Continuous Protection Server .......... 149

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

DEFINITIONS. ..................................................................... 176

Appendix B Maintaining accessibility ................................................. 183

Glossary ............................................................................................................. 189

■ 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 Protection

Storage Foundation for Windows Provides easy-to-use online disk storage

Components of Continuous Protection Server

Table 1-1 Components of Continuous Protection Server

Backup Group The Backup Group includes the following components:

■ One Continuous Management Service

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

Continuous The Continuous Management Service does the following:

See “Performing an initial installation” on page 37.

Remote Agent is an optional component.

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

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

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

How Continuous Protection Server works

Figure 1-1 Overview of the Continuous Protection Server model

Backup Exec Backup Exec

See “Configuring Business Servers” on page 59.

2 The Continuous Protection Server Backup Destination Wizard designates a

Different servers can be designated as backup destinations based on your needs.

See “Managing backup destinations” on page 65.

See “Creating CPS backup jobs” on page 88.

4 As soon as the data is backed up to the Protection Server, scheduled snapshots

See “Managing snapshots” on page 68.

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

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

What you can do with Continuous Protection Server

Table 1-2 Features and benefits of Continuous Protection Server

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

Symantec LiveUpdate Uses Symantec LiveUpdate to provide periodic product updates.