continuous protection server

September 2006

10759381

Symantec Backup Exec™ Continuous Protection Server version 11d

Administrator’s Guide

CPS11.book Page i Wednesday, October 18, 2006 4:33 PM

ii Backup Exec Continuous Protection Server Administrator’s Guide

Disclaimer

The information contained in this publication is subject to change without notice. Symantec Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Symantec Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

Symantec Legal Notice

Copyright © 2006 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Backup Exec 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.

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.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

http://www.symantec.com/

Third-Party Copyrights

Certain third-party software may be distributed, embedded, or bundled with this 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. Please see copyrights.pdf for licenses that govern the use of the third-party software and for proprietary notices of the copyright holders.

CPS11.book Page ii Wednesday, October 18, 2006 4:33 PM

iii

Contents

Chapter 1. Introducing Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

About Backup Exec Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

What are the features and benefits of CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

What are the key components of CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

How Continuous Protection Server works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

About backup strategies and planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Data protection considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About backup job schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

How system information is protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

System State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Shadow Copy Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Exchange Server protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

For additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Accessing the CPS documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing the Symantec Technical Support Web site . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing the Symantec Backup Exec Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Installing Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Before you install the CPS software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

The general installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Checking your environment before installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Minimum system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

System Requirements for Business Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

System Requirements for Continuous Management Service and Protection Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

System Requirements for Administration Console . . . . . . . . . . . . . . . . . . . . . . . 21

System Requirements for Web Restore Server Component . . . . . . . . . . . . . . . . 21

CPS11.book Page iii Wednesday, October 18, 2006 4:33 PM

iv Backup Exec Continuous Protection Server Administrator’s Guide

System Requirements for Indexing Component . . . . . . . . . . . . . . . . . . . . . . . . . 22

System Requirements for Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . 22

Encrypted files and reparse points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Firewall support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

What gets installed and where . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Files and folders that are installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Drivers that are installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

CPS Services that are installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Registry entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Performing an initial installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Push-installing CPS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Upgrading to CPS 11d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Modifying CPS installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Uninstalling the Continuous Management Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Uninstalling a Continuous Protection Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 3. Using the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About the CPS Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Starting CPS and accessing the Administration Console . . . . . . . . . . . . . . . . . . . . . . . . 39

About the general Administration Console features . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

About the Administration Console views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setup view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Setup View Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Restore view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Job Monitor view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Alerts view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4. Configuring Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring Business Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Moving servers between Backup Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

CPS11.book Page iv Wednesday, October 18, 2006 4:33 PM

Contents v

Managing the CPS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Managing backup destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Additional notes on backup destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Adding a backup destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Configuring the backup destination for Shadow Storage . . . . . . . . . . . . . . . . . . . . . 55

Renaming backup destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Deleting backup destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Managing snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Creating snapshots on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Creating snapshots on schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Changing snapshot schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Defining Retention Policies for snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Viewing snapshot history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Snapshot indexing states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Deleting snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring registry entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Accessing and viewing the Settings Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

About the Settings Utility tunable parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Changing CPS tuning parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 5. Backing Up Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

About CPS data backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Backing up System Information in CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Creating CPS backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Modifying backup job configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Moving a backup job to a different backup destination . . . . . . . . . . . . . . . . . . . . . . 83

Including and excluding information to back up . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Changing backup schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Limiting bandwidth that is dedicated to a backup job . . . . . . . . . . . . . . . . . . . . . . . . 88

Adding scripts that run before or after backup jobs . . . . . . . . . . . . . . . . . . . . . . . . . 89

CPS11.book Page v Wednesday, October 18, 2006 4:33 PM

vi Backup Exec Continuous Protection Server Administrator’s Guide

Starting, stopping, and canceling jobs manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 6. Restoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Restoring files and directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Restoring System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Restoring System State to an Active Directory system . . . . . . . . . . . . . . . . . . . . . . 94

Restoring network shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 7. Using Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

About Backup Exec Retrieve features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Security and credentials for Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Internet Explorer security on Windows Server 2003 . . . . . . . . . . . . . . . . . . . . . . . . 98

Retrieving files using Backup Exec Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Using CPS with Backup Exec Desktop and Laptop Option . . . . . . . . . . . . . . . . . . . . . . 101

Securing files that are not retrievable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 8. Monitoring CPS Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Viewing the job status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

About job states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Viewing the status of a job or the job pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

CPS job and pair status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Viewing a job report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

CPS job report details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Job Report Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

CPS Jobs Topic Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Exception Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Error Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Managing CPS job alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Viewing and filtering active alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Viewing and filtering alert history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Viewing alert properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

CPS11.book Page vi Wednesday, October 18, 2006 4:33 PM

Contents vii

Responding to active alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Deleting alerts from alert history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 9. Using CPS with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Protecting CPS with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring CPS for Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Backing up CPS with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Backing up CPS databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Backing up the Continuous Management Service (CMS) . . . . . . . . . . . . . . . . . 118

Backing up a Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Backing up Business Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Backing up snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Restoring CPS with Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Restoring the Continuous Management Service . . . . . . . . . . . . . . . . . . . . . . . . 121

Restoring the CPS Protection Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Restoring a CPS Business Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Monitoring CPS Jobs in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Setting up a SmartLink connection between CPS and Backup Exec . . . . . . . . . . 122

Viewing alerts posted to Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

About fatal alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

About pair alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Viewing job logs posted in Backup Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

About CPS backup job log details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Job Operation - Continuous Protection Job Topic Box . . . . . . . . . . . . . . . . . . . . 130

Command Line Syntax Error Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Exceptions Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Backup Exec SmartLink Options Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Backup Exec SmartLink Run Log Topic Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

CPS Jobs Topic Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Chapter 10. Troubleshooting Continuous Protection Server . . . . . . . . . . . . . . . . . . . . . 135

CPS11.book Page vii Wednesday, October 18, 2006 4:33 PM

viii Backup Exec Continuous Protection Server Administrator’s Guide

CPS compatibility issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

CPS installation and upgrade issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

CPS credentials and security issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

CPS components issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

CPS configuration issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

CPS general issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

CPS backup and restore job issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

CPS System State backup and restore issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

CPS job monitor issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Backup Exec Retrieve issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

CPS Tools and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

CPS Database Maintenance utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

CPS Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

CPS Database Validation and Repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Services Manager utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

SetIntegratedLogin utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Issues with integrated login and database backups . . . . . . . . . . . . . . . . . . . . . 157

Restoring a combined CMS/CPA server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Appendix A. Maintaining Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159

About accessibility in CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

About general keyboard navigation in CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

About keyboard navigation in dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

List Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Using keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Establishing accessibility settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

CPS11.book Page viii Wednesday, October 18, 2006 4:33 PM

1

Chapter

Introducing Continuous Protection Server

1

This section includes the following topics:

■ “About Backup Exec Continuous Protection Server” on page 1

■ “How Continuous Protection Server works” on page 6

■ “About backup strategies and planning” on page 9

■ “For additional information” on page 13

About Backup Exec Continuous Protection ServerSymantec Backup ExecTM Continuous Protection Server (CPS) software ensures 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 backups and restores. As a disk-based solution, data is protected in a continuous mode that provides granular restore from points in time throughout the day. It also enables simultaneous backups of multiple servers. CPS integrates with Symantec Backup Exec 11d for Windows Servers for traditional tape-based data protection, and delivers integrated management by Backup Exec SmartLink technology.

CPS reduces overall administration costs by providing efficient and immediate user restores with a Web-based data retrieval tool. Through a Web interface, users can safely retrieve their own files without requiring IT assistance. Because it is Web based, no software or client is required on the users’ desktops or laptops. Thus, no client software has to be updated or maintained.

CPS11.book Page 1 Wednesday, October 18, 2006 4:33 PM

About Backup Exec Continuous Protection Server

2 Backup Exec Continuous Protection Server Administrator’s Guide

What are the features and benefits of CPS

Features and Benefits of CPS

Feature Description

Continuous data protection

CPS backs up files on a network (LAN or WAN) and writes them immediately to a Protection Server, with no wait time. There is no need for incremental or differential backups on servers 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.

Web-based user file retrieval

Backup Exec Retrieve enables end users to retrieve their own files without contacting IT, which reduces administrator requests and improves service levels. Retrieving files is as simple as using a web-based search engine to search for and download a file from the Internet. Since you only need a standard Web browser to retrieve files, there is no client software or agent to install on desktops and laptops, making deployment and administration easy.

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.

Powerful Administration Console

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

Point-in-time snapshots CPS leverages Volume Shadow Copy Service (VSS) snapshots to provide versioning of files and 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 Symantec Backup Exec

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


Chapter 1, Introducing Continuous Protection Server


3

Flexible backup options Back up only the specific data you need. Save on system resources by backing up only the information that needs to be recovered in case of file corruption or a system failure, or for compliance purposes.

Customized backup schedules

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

Bandwidth throttling Administrators can set the maximum amount of bandwidth to be used for continuous data protection jobs.

Open file protection CPS protects open files during continuous protection.

Customized retention properties

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

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 being 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 CPS will capture system state information, reducing the time and effort associated with recovery of 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 version 6 (IPv6).

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

Features and Benefits of CPS (continued)

Feature Description




What are the key components of CPS

Continuous Protection Server consists of the following key components. Refer to “How Continuous Protection Server works” on page 6 for roles and configurations of these components.

DLO file recovery Backup Exec Retrieve now allows users of Backup Exec Desktop and Laptop Option (DLO) to restore DLO protected files directly back to their workstations using a Web interface.

Continuous protection of Exchange

Supports continuous protection of Exchange servers using the Backup Exec Administration Console.

Features and Benefits of CPS (continued)

Feature Description

CPS Key Components

Component Description

Backup Group The Backup Group consists of only one Continuous Management Service, at least one Business Server, at least one Protection Server, the CPS Administration Console, and optionally, the Web Restore Server Component.

Business Servers Business Servers store the data that is routinely saved by users during the course of their daily operations. Once data is saved to the Business Server, the data may be backed up to a Protection Server. Business Servers must therefore reside in the same Backup Group as the Protection Server. Each Business Server requires that a Continuous Protection Agent be installed.

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, as well as the Web Restore Server Component that allows users to retrieve data by Backup Exec Retrieve. More than one Protection Server can be installed in the Backup Group.




5

Continuous Management Service

The Continuous Management Service (CMS) provides primary control of the CPS processes, retains configuration settings from the Administration Console, and manages the CPS system. Only one CMS may be installed in a Backup Group, and it must be installed before any other CPS components. The CMS should be installed on a server that is appropriate for its use and has a fixed IP address.

Continuous Protection Agent

A Continuous Protection Agent must be installed on all Business Servers and Protection Servers within the Backup Group. The Continuous Protection Agents are responsible for managing the collection of data during CPS backup and restore jobs.

Administration Console The Administration Console controls all aspects of CPS, including defining data sources and 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.

Web Restore Server Component

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

Backup Exec Retrieve Backup Exec Retrieve is 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.

Users can search by full or partial file name, browse to the location where their files are stored, view all versions of a file that were backed up, and select a copy of the file they need. When files are selected, a copy can be downloaded without assistance from system administrators.

Indexing Component The Indexing component maintains a directory of 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 that is installed on any Protection Server that users access for file retrieval using Backup Exec Retrieve. The Indexing component allows searches by file name, file versions, and recent activity.

CPS Key Components (continued)



How Continuous Protection Server works


How Continuous Protection Server worksFollowing is an idealized use model for running CPS. Each step is characterized in the “CPS Use Model Figure” on page 8.

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.

2. The CPS Backup Destination Wizard designates a specific directory on a specific Protection Server where the data is backed up. The backup destination definition includes scheduling of the data snapshots for file versioning and setting 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.

Backup Exec SmartLink This component simplifies management by enabling users to view the combined status of CPS and Backup Exec jobs in the Backup Exec Administration Console.

Remote Agent for Windows Systems (Remote Agent)

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

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 any Protection Server and the server hosting the CMS that will be protected by Symantec Backup Exec. Remote Agent is not required when CPS is installed on the Backup Exec Media Server because the Media Server already contains Remote Agent functionality. However, the Remote Agents used by CPS and the Backup Exec Media Server must be the same version (11d).

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.

CPS Key Components (continued)





7

3. CPS backup jobs are created to back up data from one or more Business Servers to a Protection Server using the Backup Job Wizard. When jobs are created, you select the data to be backed up and the schedule for the backup job. CPS backup jobs can be scheduled to run at specific times (periodically), as files incur any changes (continuously) or as needed (on demand).

4. As soon as the data has been backed up to the Protection Server, scheduled snapshots of the data can be made. The data is then indexed and made available to the Web Restore Server Component.

5. Users retrieve specific files and folders from the Web Restore Server Component directly back to their workstations using Backup Exec Retrieve and their Internet browsers. Since the data was backed up with specified snapshots, users can select specific versions of their data to be restored.

6. In the event of a system failure at one or more Business Servers, the backed up data can be quickly restored from the Protection Server back to the Business Server.

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

8. In the event of a system failure or data loss at a Protection Server, Backup Exec is able to quickly restore the data back to the Protection Server or directly back to a Business Server from the Backup Exec media server.

9. A CPS component, Backup Exec SmartLink, allows the status of CPS backup jobs to be viewed in the Backup Exec Job Logs and Alerts. This option allows administrators to determine the quality and completion of the CPS jobs before or during the Backup Exec backup job.




CPS Use Model Figure



About backup strategies and planning

9

Related Topics:

“Performing an initial installation” on page 27

“Push-installing CPS Components” on page 32

“Configuring Business Servers” on page 49

“Managing backup destinations” on page 54

“Managing snapshots” on page 58

“Creating CPS backup jobs” on page 80

“Restoring Data” on page 91

“Using Backup Exec Retrieve” on page 97

“Backing up CPS with Backup Exec” on page 117

“Restoring CPS with Backup Exec” on page 120

“Monitoring CPS Jobs in Backup Exec” on page 122

About backup strategies and planningOne of the most important assets to any business is the information stored on its computers. Whether reporting regulatory information, placing and tracking orders, communicating with customers, storing email addresses and phone numbers, or managing financial results, every business contains a large amount of information pertinent to its operations.

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. System administrators have a limited amount of time to spend creating complex backup schemes. Most of their time is spent managing network resources, researching technology trends, and ensuring data availability and access. 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 quickly restore lost files.

Data protection considerations

Some decisions should be made about your backup requirements before installing and using CPS. Some of the specific questions you should consider include:

■ 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 will store it?

■ How long should the data be retained and available for restore?

■ Has the System Information for the server been modified such that it warrants backup protection?

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

■ What information should 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 CPS 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 the quality of the backup, the resources that are required to process and store the information, and the process of locating information you need to restore.

There are multiple levels of backup schedules that work well together and each organization will probably 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 used for compliance purposes or related to your core products or services, should be backed up continually.

On demand scheduled backups

The CPS backup job runs when manually started by the user.




11

Regularly scheduled backups

Regularly scheduled backups consist of files being copied on a regular 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.

Periodically scheduled backups

Periodically scheduled backups consist of files being copied on certain days of the week, and run periodically on timed intervals. For example, you can back up your sales proposals data every hour, your development data every three hours, your quality assurance data every four hours, and so on.

Continuously scheduled backups

Critical business information, such as your customer data, should be 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.

Related Topics:

“Changing backup schedules” on page 87

How system information is protected

The Windows operating system includes data that requires special handling so that it may be protected and restored properly. This data, referred to as “System Information” in CPS, contains different information depending on the version of Windows that is installed on the system.

System State

Windows 2000 Server and Windows Server 2003 systems include a set of data called System State. Depending on the installation options, System State data may consist of the registry, COM+ Class Registration database, system boot files, and the Certificate Services database (if the server is a certificate server). If the server is a domain controller, Active Directory and the SYSVOL directory are also contained in the System State data. If you are running the domain name service (DNS) on a domain controller, then the Active Directory portion of the System State data also contains all of the DNS zone information. Finally, if the server is running the Cluster service, then the System State data will also include any resource registry checkpoints and the quorum resource recovery log, which contains the most recent cluster database information.




Shadow Copy Components

In addition to the System State data, Windows Server 2003 systems include the Shadow Copy Components. Windows 2000 Server systems do not include the Shadow Copy Components. Depending on the installation options, the Shadow Copy Components may consist of the event logs, removable storage manager database, and the Windows Management Installation database. Additionally, if the Windows Server 2003 also acts as a SharePoint server, the Shadow Copy Components will include the SharePoint databases.

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 will be backed up or restored.

If the server’s System Information has been modified, such as to comply with a corporate standard configuration, you may want to back up the System Information for protection.

Related Topics:

“Backing up System Information in CPS” on page 80

“Restoring System Information” on page 93

“Backing up CPS with Backup Exec” on page 117

Exchange Server protection

Symantec Backup Exec uses Continuous Protection Server 11d to continuously protect Microsoft Exchange servers. The association between Backup Exec and CPS 11d is achieved through the Backup Exec Continuous Protection Broker Service that is installed with each CPA (see “CPS Services that are installed” on page 26).

Once the Broker Service is installed, Backup Exec users can create an Exchange Log Protection job to protect the Exchange transaction logs. The protected transaction logs are part of the Backup Exec Exchange full backup set.

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.

Related Topics:

Symantec Backup Exec for Windows Servers Administrator’s Guide

“Viewing the status of a job or the job pairs” on page 105



For additional information

13

For additional informationThe product documentation provides assistance for using Backup Exec Continuous Protection Server to your advantage. You can access the information that you need from the product CD and Symantec Web site.

Accessing the CPS documentation

The Backup Exec Continuous Protection Server documentation is available on the product CD and installed with each Administration Console. The following manuals and help files comprise the Continuous Protection Server documentation set.

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

▼ To access the CPS documents from the CD:

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

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

3. Double-click the file to open it.

Document Title Description

Continuous Protection Server Administrator’s Guide(CPSadmin_XX.pdf)

Continuous Protection Server documentation that is written for system administrators and delivered in Adobe Acrobat (PDF) format.

Continuous Protection Server Quick Installation Guide(CPSquick_xx.pdf)

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

Continuous Protection Server Help files(CPSconsole_XX.chm)

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

Continuous Protection Server Readme files(Readme_XX.html)

An HTML file containing any product changes and installation issues that should be reviewed before installing the CPS product.


For additional information


Using online Help

Online Help is installed with the CPS software.

▼ To access the online Help:

1. Install the CPS software.

2. Click Help or press [F1].

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:

1. On the Internet, go to http://www.symantec.com/techsupp

2. Follow the links to the information you want.

Accessing the Symantec Backup Exec Web site

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

▼ To access the Symantec Backup Exec Web site:

1. On the Internet, go to http://backupexec.com

2. Follow the links to the information you want.


15

Chapter

Installing Continuous Protection Server

2


■ “Before you install the CPS software” on page 15

■ “What gets installed and where” on page 24

■ “Performing an initial installation” on page 27

■ “Push-installing CPS Components” on page 32

■ “Upgrading to CPS 11d” on page 34

■ “Modifying CPS installations” on page 35

■ “Uninstalling the Continuous Management Service” on page 35

■ “Uninstalling a Continuous Protection Agent” on page 36

Before you install the CPS softwareYou should review the following pre-installation topics before you install the CPS software,

❏ “The general installation procedure” on page 16

❏ “Understanding the CPS service account” on page 140

❏ “Checking your environment before installing” on page 16

❏ “Minimum system requirements” on page 18

❏ “Encrypted files and reparse points” on page 23

❏ “Firewall support” on page 23

❏ “CPS compatibility issues” on page 136


Before you install the CPS software


The general installation procedure

Continuous Protection Server was designed to provide diverse and yet straight-forward configurations for unique customer requirements. To maximize the benefit of these configurations, Symantec recommends that you install CPS according to the following general procedure.

■ Install the Continuous Management Service (CMS) and an Administration Console, preferably on a dedicated server, before installing other CPS components. (See “Performing an initial installation” on page 27.)

■ From the initially installed Administration Console, push-install additional Administration Consoles, Continuous Protection Agents (CPAs), or both, to other Business Servers or Protection Servers. (See “Push-installing CPS Components” on page 32.)

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

Note If you are upgrading over or plan to operate Continuous Protection Server with Veritas Storage Replicator or Veritas Replication Exec, refer to the CPS white paper, “Upgrade, Migration and Concurrent Operation” available at the following location: http://support.veritas.com/docs/277838.

Checking your environment before installing

The Symantec Backup Exec Environment Check allows you to assess your existing hardware and software resources for compatibility with the Continuous Protection Server software installation. Environment Check assesses and reports on a number of pre-installation configurations, including the following.

■ If the computer meets the minimum requirements for installation, such as the operating system, disk and memory space, and sufficient logon account privileges.

For more information, see “Minimum system requirements” on page 18.

■ If third-party software that use CPS ports is configured correctly.

■ If required components are installed, and if they are versions that are compatible with CPS.

■ If previous versions of CPS are installed.

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


Chapter 2, Installing Continuous Protection Server


17

The results that are reported for each item are flagged as:

Although the Environment Check runs automatically during installation, you may want to run it manually before installing CPS or before backing up data with CPS.

To check your environment before installing:

1. From the CD browser, click Start the Backup Exec Continuous Protection Server Environment Check.

2. Click Next.

3. Do any of the following:

4. Click Next.

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

Passed There are no incompatibilities that will prevent the CPS installation. For hardware, this result indicates that the hardware configuration is recognized by CPS.

Warning An incompatibility with CPS exists, but can be resolved, or a condition of which you should be aware.

Failed An incompatibility with CPS exists, and it will cause the installation to fail. Some action is required before you can successfully install CPS.

To check the configuration of the local computer

Check Local Environment Check.

To check the configuration of a remote computer

Check Remote Environment Check.

To select the name of a computer from a list

◆ Click Add Server From List.

◆ Select the computer from the list, and then click Next.




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.

Minimum system requirements

The minimum system requirements vary for each CPS component. For minimum requirements for each component, see the following:

■ “System Requirements for Business Servers” on page 19

■ “System Requirements for Continuous Management Service and Protection Servers” on page 20

■ “System Requirements for Administration Console” on page 21

■ “System Requirements for Web Restore Server Component” on page 21

■ “System Requirements for Indexing Component” on page 22

■ “System Requirements for Backup Exec Retrieve” on page 22

Note 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.

To add the name of a computer manually

◆ Click Add Server Manually.

◆ In the Domain field, type the name of the domain.

◆ In the Computer Name field, type the name of the computer.

◆ Click OK.

◆ Type the user name and password for this computer.

◆ 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.

◆ Click Remove.




19

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.

Business Server requirements

Item Description

Supported Operating Systems ◆ Microsoft Windows 2000 Server with Service Pack 4

◆ Microsoft Windows 2000 Advanced Server with Service Pack 4

◆ Microsoft Windows Server 2003 x64 Editions

◆ Microsoft Windows Server 2003 (including R2, but not Data Center) with Service Pack 1

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

◆ Microsoft Windows Storage Server 2003 with Service Pack 1

RAM 512 MB, 1 GB recommended

Disk Space: CPS Software 25 MB

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.

CMS and Protection Server requirements

Item Description

Supported 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


Disk Space: CPS Software 58 MB

Disk Space: Logs and Alerts 100 MB

Disk Space: Indexing Component

1 GB or more as required

Volumes The Protection Server should have at least four separate volumes for ideal performance:

◆ System volume

◆ Journals volume

◆ Backup destination volume

◆ Snapshot storage volume for backup destination

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





21

System Requirements for Administration Console

Any number of Administration Consoles may be installed in the Backup Group.

System Requirements for Web Restore Server Component

Web Restore Server component is installed on the computer hosting the Continuous Management Service.

Administration Console requirements

Item Description

Supported Operating Systems ◆ Microsoft Windows 2000 Professional with Service Pack 4

◆ Microsoft Windows 2000 Server with Service Pack 4



◆ Microsoft Windows XP Professional

◆ Microsoft Windows XP Professional x64 Edition

RAM 128 MB, 512 MB recommended

Disk Space 35 MB for Console alone, plus add:

◆ 250 MB for 32-bit push-install files

◆ 275 MB for 64-bit push-install files

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

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

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


.Net Framework 2.0 will be installed for Settings Utility, if needed

Web Restore Server Component requirements

Item Description


Disk Space: Installed Software 25 MB




System Requirements for Indexing Component

The Indexing Component is installed with each Continuous Protection Agent.

System Requirements for Backup Exec Retrieve

Backup Exec Retrieve is the gateway by which users access the Web Restore Server Component to retrieve files.


Indexing Component requirements

Item Description


Disk Space: Installed Software 40 MB

Disk Space: Index As required


Backup Exec Retrieve requirements

Item Description

Supported Operating Systems ◆ Microsoft Windows 2000 Professional with Service Pack 4

◆ Microsoft Windows 2000 Server with Service Pack 4



◆ Microsoft Windows XP Professional Service Pack 1 or later

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

Web Restore Server Component requirements (continued)

Item Description




23

Encrypted files and reparse points

CPS detects files on sources in the CPS Backup Group that were given reparse points as place holders from an application such as Single Instance Storage (SIS) or Hierarchical Storage Management (HSM). CPS copies the raw information inside the reparse point to the Protection Server. This information is generally not useful until it is restored to the same server from which it originated.

Note Files with reparse points are not displayed or available in Backup Exec Retrieve.

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.

Firewall support

Firewalls must be configured to allow the following ports through to support CPS. To change the ports, see “About the Settings Utility tunable parameters” on page 66.

Note If any of the default port settings are changed on one computer, they must be changed on all computers in the CPS Backup Group.

Continuous Protection Server default port settings

Service Name Default Port Number

Port Type Editable Registry Key

Network Helper Service (ENL)

1804 UDP HKLM\Software\Symantec\ENL\Network.TCPIP

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

Web Restore Server Component (http)

8181 TCP To change the Web Restore Server Component port numbers, see the following TechNote http://support.veritas.com/docs/278249.


What gets installed and where


Additionally, the CPS Services Manager, push-install, and Settings Utility utilize Windows file sharing (NetBIOS or SMB) ports. In order for these services to function, the following ports must be configured.

Caution Symantec recommends that you do not open these ports to the Internet.

Note CPS also uses the following ports on the local server: 2638, 9000–9003, 10000, 13730, 14300 and 20487. Because these ports are only used on the local server, it is not necessary (or recommended) that they be opened through your firewall.

Related Topics:

“Configuring registry entries” on page 65

What gets installed and whereAfter the CPS installation completes, depending on the CPS components that are installed, a number of files, services, drivers, and registry entries are made to the system. This section discusses these CPS installation footprints.

Web Restore Server Component (https)

8443 TCP To change the Web Restore Server Component port numbers, see the following TechNote http://support.veritas.com/docs/278249



Windows(NetBIOS over TCP/IP)

445 TCP No

Windows (NetBIOS

137

138

139

UDP

UDP

TCP

No

Continuous Protection Server default port settings (continued)






25

Files and folders that are installed

By default, CPS installs files and folders in the following directory:

C\Program Files\Symantec\Continuous Protection Server\

Drivers that are installed

CPS installs the (CpsFsJnl.sys) filter driver. This driver is responsible for detecting changes in protected files and recording those changes to the protection server.

Folder Name Description

ASA (Adaptive Server Anywhere)

The ASA folder contains two folders: Win32 and Charsets. The Win32 folder contains the 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 CPS 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 CMS (rms.db) and CPA (rsa.db) databases, their backup copies, and the related database files.

Drivers The Drivers folder contains the CPS filter driver.

Install The Install folder contains CPS, Remote Agent, and Symantec LiveUpdate installation files for push installs.

Services The Services folder contains CPS service executable files and associated support files.

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




CPS Services that are installed

CPS installs the following services depending on the CPS components that are installed:

Service Name Short Name Description

Backup Exec Continuous Protection Administration Service

RxRMS This service is the CMS service and is present only on the server hosting the CMS. It manages the configuration for all Backup Exec Continuous Protection Agents in the Backup Group.

Backup Exec Continuous Protection Agent

RxRSA This service is the CPA service and is present on all servers on which the CPA is installed. It enables CPS to back up data from the server or move the backed-up data on the server.

Backup Exec Continuous Protection Broker Service

RepBrokerSvc This service allows communication between CPS and Backup Exec to facilitate continuous protection of Microsoft Exchange transaction logs.

Backup Exec Continuous Protection Configuration Writer

rxWriterSvc This service communicates with Volume Shadow Services to save and store the Continuous Protection Server’s configuration information.

Backup Exec Continuous Protection Database

RxASA This service controls the configuration database for all CPS information.

Backup Exec Continuous Protection System State Manager

RxNoService This service captures system information and file share information.

Backup Exec Continuous Protection Network Helper (ENL)

ENL This service enables the CMS to group and discover CPA’s and communicate with them.

Backup Exec Continuous Protection Indexing Service

SUIR This service indexes files backed up using CPS and presents these files after a search operation from the Web Retrieval Interface or the Administration Console.

Backup Exec Continuous Protection Web Restore Backend

RxWRG This service controls the CPS Web Restore backend interface.



Performing an initial installation

27

Registry entries

CPS adds a number of keys to the registry. Some of the CPS registry locations are as follows:

■ HKLM\SOFTWARE\Symantec\Backup Exec CPS

This location stores information about the journal directories, CPS installation path, CMS database installation directory, CPS parameters, and CPS build details.

■ HKLM\SYSTEM\CurrentControlSet\Services\

This location stores information about the CPS 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 and viewing the Settings Utility” on page 65).

Performing an initial installationA typical and fully functional CPS Backup Group includes the following components.

■ A server that has the Continuous Management Service (CMS), the Continuous Protection Agent (CPA), the Administration Console, the Web Restore Server Component, and Indexing Component 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.

Backup Exec Continuous Protection Web Restore Frontend

RxWebApp This service controls the CPS Web Restore frontend interface.

VERITAS Web Server VRTSweb This service is the Web Server service.

Service Name Short Name Description




Note The CMS components can be installed on a Backup Exec Media Server or on a stand-alone server. If CPS is installed on a Media Server, then that Backup Exec installation must be upgraded to Backup Exec version 11d. If CPS is installed on a stand-alone server, then the 11d version of Remote Agent is also installed. A Remote Agent is not installed on a Media Server.

The first step in creating a fully functional environment is configuring the server that hosts the CMS. Establishing the CMS is usually accomplished by performing an initial installation from the CD.

CPS application files that should be installed during the initial installation include the Continuous Management Service (CMS) and an Administration Console. If the server hosting the CMS will also be a Business or Protection Server, a Continuous Protection Agent (CPA) must also be installed. The Web Restore Server Component, Indexing Component, and the SmartLink application are also installed. The Remote Agent is installed optionally during the initial installation with a CPA. Symantec LiveUpdate is installed automatically with an Administration Console.

Firewalls need to be manually reconfigured for CD installation and push installation. Alternatively, firewalls can be turned off during the installation process. For additional information on configuring firewalls for CPS installation, see “Firewall support” on page 23 and “About the Settings Utility tunable parameters” on page 66.

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 20.

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 additional information, go to the Microsoft Web site (http://www.microsoft.com), and search for the article “Network Load Balancing, Windows 2000 Advanced Server”.

▼ To perform an initial installation:

1. Close all other programs that may be running.

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




29

3. Select the language, and then click OK.

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

5. The Backup Exec Continuous Protection Server Environment Check will start. Do one of the following:

■ If the Environment Check does not reveal any issues that may prevent a successful installation of CPS, click Next.

■ If the Environment Check reveals issues that may prevent a successful installation of CPS, click Cancel to exit the wizard. Correct the issues before attempting to install again.

Click Next.

6. Select Start theBackup Exec Continuous Protection Server Installation to install CPS. CPS will determine whether the computer is a 32-bit or 64-bit server and install the appropriate version of the software. Click Next to continue.

7. Review the CPS Installation Wizard welcome screen, and then click Next.

8. Read and accept the license agreement on the License Agreement screen, and then click Next.

9. Select one of the following methods to enter license keys:

10. Click Next.

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

To enter license keys manually

◆ Type a license key into the license key field.

◆ Click Add.

◆ Repeat for each license key for each option or agent you want to add.

To import license keys from a file

◆ Click Import.

◆ Select the cpssernum.xml file.

To install an evaluation version

◆ Leave the license key field blank.

◆ Proceed to step 12.




11. On the Local Features screen, select the CPS components to be installed as follows:

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 CPS 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. The options are:

◆ 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 CMS, which must be installed to create and manage the Backup Group.

Note Only one CMS may be installed in each Backup Group, and it must be installed before other CPS components.

Web Restore Server Components

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

Continuous Protection Agent

Check this option to install a CPA on the computer.

Note A CPA 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 Windows Systems

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

Exchange Protection Agent

Check this option to allow for continuous protection of Microsoft Exchange Servers.

Note An Exchange Protection Agent must be installed with the CMS, and a CPA must be installed on the Backup Exec Managed Media Server.

Note An Exchange Protection Agent must be installed with the Remote Agent as well as a CPA on the Microsoft Exchange system.




31

12. Click Next.

13. On the Backup Group screen, enter a name of the Backup Group and the name of the Continuous Management Service. Click Next to continue.

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 CPS Service Account, including user name, password and domain. For additional information, see “Understanding the CPS service account” on page 140.

15. If a CMS was selected for this installation and the CMS 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. Click Next to continue.

16. On the Support Folder screen, accept the default directories or change the directories for the following:.

Symantec recommends that these directories be on separate volumes.

17. Click Next.

18. On the Ready to Install the Program screen, review the selections, and then click Install.

System Cache Directory

Select or browse to the directory where CPS 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 2 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.


Push-installing CPS Components


19. Following the CPS installation, you are prompted to restart the computer. Click Yes to complete the installation.

Note If a CPA 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.

Push-installing CPS ComponentsAfter you perform the initial installation, additional CPS components can be installed remotely using the previously installed CPS Administration Console. Components that may be push-installed consist of additional Administration Consoles, Continuous Protection Agents (CPA), or both. Any number of Consoles may be installed in the Backup Group, and a CPA must be installed on each Business Server and Protection Server.

Firewalls need to be manually reconfigured for CD installation and push-installation. Alternatively, firewalls can be turned off during the installation process. For additional information on configuring firewalls for CPS installation, see the following TechNote: http://support.veritas.com/docs/278180.

▼ To push install a CPS component:

1. Start the CPS Administration Console using the shortcut in the Start menu:

Start > Programs > Symantec > Backup Exec CPS > Backup Exec CPS Console.

2. On the navigation bar, click Setup.

3. From the Server Tasks pane, select 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 to continue.

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. Click Next to continue.

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.



Push-installing CPS Components

33

6. On the Select Components screen, use the check boxes to designate the components you want to install. The options are to install a Continuous Protection Agent (with or without a Remote Agent or Indexing Component) or Administration Console (with or without Symantec LiveUpdate or the Settings Utility), or both. By default, all options are pre-selected for installation. Click Next to continue.

For optimal performance, some CPS 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.

7. Enter the Credentials for the Backup Exec CPS Service Account, including user name, password and domain. For additional information, see “Understanding the CPS service account” on page 140.

8. Enter the license keys provided, and click Next to continue.

9. On the Local System Object Cache Path screen, select or browse to the directory where CPS 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. Click Next.

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

10. 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. Click Next.

11. 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. Click Next.

12. 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. Click Next to continue.

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.

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


Upgrading to CPS 11d


14. On the Completing the Push Install CPS Components Wizard screen, click Finish to begin the installation. A screen appears showing the installation progress.

15. Verify that the Protection Agent was properly installed by noting that the Business Server shows in the server list on the Servers tab. Please note that this step may take some time due to the configuration and system restart.

The server you add to the CPS Backup Group must be restarted. If you use Microsoft’s Shutdown Event Tracker, you must restart the server manually after installation.

Upgrading to CPS 11dCPS 11d is not compatible with any earlier versions of the Continuous Protection Server or Veritas Replication Exec (VRE) software. The CMS, CPAs and Consoles must all be updated to CPS 11d.

The CPS 11d installer upgrades previous versions of CMS or VRE on Windows 2003 Server systems. Existing job configurations are also migrated during the installation.

If you are upgrading from VRE on a Windows 2000 Server you must completely uninstall it and install CPS 11d on a Windows 2003 Server.

Note If you want to upgrade only portions of the CPS products or run CPS 11d concurrently with CPS 10d, see the following TechNote: http://support.veritas.com/docs/283642.

▼ To upgrade to CPS 11d:

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

2. Insert the CPS 11d CD into the CD-ROM drive. If AutoPlay is not enabled, navigate the installation CD and double-click browser.exe. This will open the welcome screen of the Continuous Protection Server installation wizard.

If earlier versions of CPS or Replication Exec are detected, a prompt will appear noting that the earlier versions must be manually uninstalled before CPS 11d can be installed.

3. Click Update to continue.

4. If upgrading a CPA, when prompted, enter the license keys for the CPS 11d product, and click Next to continue.

The installation wizard will detect which earlier components are already installed on that server, and update them to CPS 11d.



Modifying CPS installations

35

As soon as CPS 11d is installed on one server, the Console running on that server can be used to install or update CPA's and Consoles to other remote servers.

Note When upgrading a CPS or Replication Exec database, all job schedules are disabled to allow CPAs to be upgraded before the CMS attempts to start the scheduled jobs. As soon as the CPA’s are upgraded, the job schedules must be re-enabled from the Console.

Modifying CPS installationsTo reinstall CPS components, use the Push-installation option for CPS Administration Consoles or Continuous Protection Agents. To detect and repair CPS component problems, rerun browser.exe, or use the Change option of the Add and Remove Programs control panel.

Uninstalling the Continuous Management ServiceUninstalling CPS 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.

▼ To uninstall the Continuous Management Service:

1. From the Windows Start menu, click Control Panel.

2. Select 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 CMS or CPA databases, data stored within backup destinations, web restore indexing database, and the local data cache.

Select Yes to all removal of all data, or select No to remove the data manually after uninstall has completed.

7. Restart the server to complete the software removal process.


Uninstalling a Continuous Protection Agent


Note A system restart is not required unless you are also uninstalling a CPA. If you are uninstalling all components and Symantec LiveUpdate is not required for any other installed applications, it will be uninstalled automatically. The Remote Agent and .net framework 2.0 will not be uninstalled. If they are not required for any other Symantec products they may be uninstalled manually.

Uninstalling 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 63.

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

▼ To uninstall Continuous Protection Agent:


2. On the Control Panel, select 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.

7. From an Administration Console, perform the following to delete the unavailable Business Server:

■ On the navigation bar, click Setup.

■ In the selection pane, click Servers.

■ In the results pane, right-click the unavailable source, and then click Delete Unavailable Server.




37

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.


39

Chapter

Using the Administration Console

3


■ “About the CPS Administration Console” on page 39

■ “Starting CPS and accessing the Administration Console” on page 39

■ “About the general Administration Console features” on page 40

■ “About the Administration Console views” on page 42

About the CPS Administration ConsoleMost functions of Continuous Protection Server are run from the Administration Console. The Administration Console is used to:

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

Starting CPS and accessing the Administration ConsoleThe Administration Console is the centralized point of management for all Continuous Protection Server activities. Administrator rights are required to start the Administration Console.


About the general Administration Console features


▼ To start the CPS Administration Console:

1. From the Windows Start menu, select Programs (or All Programs), and then Symantec, Backup Exec CPS.

2. Click Backup Exec CPS Console.

Note You can add the option to the Start menu and access it from there. To do so, right-click Backup Exec CPS Console, and then click Pin to Start menu.

About the general Administration Console featuresThe Administration Console is comprised of the following general features. Refer also to the “Administration Console Features” on page 42.

General CPS Administration Console features

Feature Description

Menu bar You can access Continuous Protection Server features 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 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 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 will change based on the view 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.

Selection pane You can select the item 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.


Chapter 3, Using the Administration Console

About the general Administration Console features

41

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 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 being performed. It appears across the bottom of the Administration Console window. You can show or hide the status bar at any time using the View menu.

General CPS Administration Console features (continued)

Feature Description


About the Administration Console views


Administration Console Features

About the Administration Console viewsContinuous Protection Server groups similar tasks together using a variety of built-in Console views. When you select a view using the navigation bar, related tasks appear in the task pane. Changing views enables you to selectively access the various CPS features.

Main menu bar Navigation bar Results pane

Task pane Selection pane Preview pane Status bar




43

Overview view

You can access the Getting Started, CPS Assistant, or System Summary views from the Overview view.

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 the Backup Exec Retrieve feature, alerts and notifications, and product updates and patches.

CPS Assistant view

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

The information desk provides links to information about:

■ Documentation, getting started, configuration and CPS wizards.

■ CPS Technical Support Web sites and Knowledge Base.

■ Symantec learning tools and sites.

System Summary View

This view displays information about backup jobs, CPS alerts, and backup servers. This view also enables you to get a comprehensive summary of your Backup Group and backup jobs.

Setup view

This view enables you to 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.

Common tasks that are shown in the task pane for the Setup view are as follows.

Task pane options of the Setup View

Task Description

Push install CPS components using wizard

Allows you to push-install additional Continuous Protection Agents, CPS Administration Consoles, or both.




Setup View Properties

You can also 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 CPS configurations. To view properties, select one of the options in the Settings pane, right-click the server, destination, or job, and then click Properties. To reveal specific properties or options, select the property from the properties pane. The resulting screens and options are described below.

Server Properties

New backup destination Allows you to configure servers within the Backup Group to be the Protection Servers of backup jobs.

New backup destination using wizard

Allows you to use the Backup Destination Wizard to designate servers within the Backup Group as Protection Servers for backup 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.

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 wizard Allows you to create a new backup job using the New Backup Job Wizard.

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.

Task pane options of the Setup View

Task Description




45

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.

Feature Description




Backup Destination Properties

Backup Jobs Properties

Feature Description

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.

Feature Description

Settings

General Provides specific information on the backup job, including backup job name, description, and Protection Server details.

Backup Selections Allows you to select the specific backup server, 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.




47

Restore view

This view enables you to 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

This view enables you to 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 CPS job by selecting Monitor job pairs from the Task pane. See Chapter 8, “Monitoring CPS Processes” on page 103.

Alerts view

This view enables you to respond to notification about the status of the CPS 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.

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.

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.

Feature Description


49

Chapter

Configuring Continuous Protection Server

4


■ “Configuring Business Servers” on page 49

■ “Moving servers between Backup Groups” on page 51

■ “Managing the CPS Services” on page 53

■ “Managing backup destinations” on page 54

■ “Managing snapshots” on page 58

■ “Configuring registry entries” on page 65

Configuring Business ServersYou can 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:


2. In the selection pane, click Servers.

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


Configuring Business Servers


4. Under Settings, click General, and then review the following:

5. Under Settings, click Volumes, and then review the following:

6. Under Settings, click Advanced.

7. To define the number of days to save the backup records, check Remove log records after (days). Then enter the number of days to keep the records.

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 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 CPS 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.

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

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.


Chapter 4, Configuring Continuous Protection Server

Moving servers between Backup Groups

51

8. Under Settings, click license keys, and then define the appropriate options as follows:

9. Under History, click Server Log, and then define the appropriate options as follows:

10. Click OK.

Moving servers between Backup GroupsIn some cases, one or more Business or Protection Servers may need to be moved to a different Backup Group. This condition might occur if an existing Backup Group has grown 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.

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.

Show entries Narrows the list of server log entries. Your options are:

◆ 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.


Moving servers between Backup Groups


Note When a new Backup Group is created, it must have a unique name and unique CMS. Each Backup Group can only have one CMS.

As soon as a new Backup Group has been created, the Business Servers and Protection Servers can be migrated to the new group.

▼ To move a server to a different Backup Group:

1. From an Administration Console installed in the original Backup Group, select the Server view.

2. Right-click a server, and then select Change Management Server.

3. 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, check the check box if you want to delete the job pairs and rules associated with the old CMS.

4. A warning is issued asking you to verify that you want to change the CMS and noting that the operation cannot be undone. Click Yes to proceed or 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 is displayed noting the failure.

Note As soon as a server has been moved to a different Backup group, all jobs involving that server must be recreated.



Managing the CPS Services

53

Managing the CPS Services The Service Manager is a CPS utility that allows you to start and stop the CPS services and change the Service Account credentials on the protected server.

▼ To stop or start CPS services:

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

2. Select the appropriate options as follows:

▼ To change the services credentials:

1. Click Services credentials to display the Service Account Information screen.

2. In the Security Mode list box, select one of the following:

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 select the file containing the server list.

Start all services Click this option to start all CPS services for the selected server.

Stop all services Click this option to stop all CPS services for the selected server.

Restart all services Click this option to stop all CPS services and then restart the services for the selected server.

Services credentials Click this option to change Service Account information or to change the startup options.

Refresh Click this option to refresh this dialog box.

Remove Servers Click this option to remove a selected server or servers from the server list.

Domain The user account that is entered 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.


Managing backup destinations


Note Every node in the Backup Group must be running in the same Mode.

Related Topics:

■ “CPS credentials and security issues” on page 140

■ “SetIntegratedLogin utility” on page 156

Managing backup destinationsContinuous Protection Server enables you to 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 are stored.

Tip 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 cities, create a destination for each city by adding a prefix to the department name. For example, a destination for the San Luis Obispo Marketing department could be SLOMarketing.

Additional notes on backup destinations

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

■ 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 a server that runs Windows 2003 Server operating system and has 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.

Workgroup 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.




55

Adding a backup destination

You need at least one backup destination before you can start backing up information from your sources.

▼ To add a backup destination:


2. In the task pane, under Backup Destination Tasks, click New backup destination.

3. Define the appropriate options as follows:

4. Click OK.

Configuring the 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.

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.

Note The server cannot be changed after the backup destination is saved.

Path Location on the Protection Server where the backup files will be stored. Type or browse to the location of the backup destination in the Backup Group.

Note The path cannot be changed after the backup destination is saved.




▼ 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 select Properties.

3. Select 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, also modify the Maximum size of the storage area to accommodate its intended use.

8. Click Okay, and then click Okay again.

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 as follows:

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.




57

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.

Note 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.

4. The Delete Backup Destination screen is displayed with the following options.

5. Click OK to delete the backup destination.

Delete all snapshots associated with this Backup Destination

Check this option to delete all snapshots automatically when the backup destination is deleted.

Open backup destination folder in explorer view

Check this option to open Windows Explorer so that data may be deleted manually.

Note In order to manually delete the data, you must have adequate permissions. Refer to Microsoft Windows security help.


Managing snapshots


Related Topics:

“Working with backup destinations” on page 141

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

Note Since snapshots are volume-based, any changes on the volume are captured in the snapshot, including the CPS data. Thus, 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 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. End 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. However, when snapshots are deleted, the disk space may not be immediately freed. A history of the snapshots can be viewed and unnecessary snapshots can be manually deleted from within the CPS Administration Console.

Additional notes on snapshots

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



Managing snapshots

59

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

Related Topics:

“Web Restore Server Component” on page 5

“How Continuous Protection Server works” on page 6

“Indexing Component” on page 5

“Snapshot indexing states” on page 63

“Retrieving files using Backup Exec Retrieve” on page 99

Creating snapshots on demand

Snapshots can be created on demand or by a schedule. Snapshot schedules are defined when the backup destination is created, and can be modified as needed.

▼ To create a snapshot on demand:



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 snapshots on schedules

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.

Note Snapshots cannot be captured more frequent than hourly.


Managing snapshots


▼ To schedule snapshots:




4. Under Snapshots, click Schedule.

5. Select one of the following snapshot schedule options.

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.

Changing snapshot schedules

Snapshot schedules can be modified to meet your backup and restore needs. You can change snapshot schedules to include any day of the week, and either run the snapshot on a schedule or run the snapshot periodically on timed intervals.

▼ To change the snapshot schedule for a backup destination:


2. In the selection pane, click Backup destinations.


4. Under Snapshot, click Schedule.

Run on these days Select the check box next to each day you want the snapshot to be taken.

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

Run Select and define the intervals at which the snapshot is taken.



Managing snapshots

61

5. Select the appropriate options as follows.

Snapshot schedules are always shown in the local time of the user creating the snapshot schedule. If snapshot schedules are created for servers that are located in other time zones, the specific time must be converted to your local time.

6. Click OK.

Defining Retention Policies for snapshots

Backup snapshots are saved on the Protection Server for 24 hours unless specified otherwise. You have the option to set the frequency with which backup 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:




4. Under Snapshot, click Retention Policy.

5. Select the appropriate check boxes and options as follows.

Run on these days Days of the week on which snapshots are started. Select the check box next to each day you want snapshots to occur. Clear the check box next to the days you do not want snapshots to occur.For example: To take a snapshot daily, select all the days of the week.

Frequency To take a snapshot at a specific time, select Run only at, and then indicate the time. For example: 1:00:00 A.M.

To run the snapshot periodically, select Run, and then indicate the frequency, start time, and end time.For example: Run every 1 Hour from 8:00:00 A.M. to 5:00:00 P.M.

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.


Managing snapshots


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.

▼ To view snapshot history:




4. Under History, click Snapshots.

If Show deleted snapshots is checked, two additional columns are added to the snapshot listings: the date deleted and the reason the snapshot was deleted. The possible reasons that a snapshot was deleted are as follows.

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.

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

63

Snapshot indexing states

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.

The values you might see in the “Indexing State” column are as follows.

See also “Snapshot and indexing issues” on page 145.

Deleting snapshots

Snapshots can be kept for a certain number of hours, days, weeks, or months before being automatically removed. Define the retention period to indicate the length of time snapshots are retained. If you need to free 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.

▼ To manually delete snapshots:




4. Under History, click Snapshots.

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).


Managing 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.

Note 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 57.



Configuring registry entries

65

Configuring registry entriesCPS 11d includes a Settings Utility that allows users to change a number of CPS tunable parameters. These parameters could previously only be changed by manually modifying entries in the system registry. Using the Settings Utility, you can now change various parameters related to the following.

■ CPS trace and indexing logs

■ Journal root directory

■ Named Objects (System Cache) directory

■ Job Retry Intervals

■ Selected Network Interface

■ TCP and UDP ports

Note The parameters that are included in the Settings Utility are often updated. For the most current list and description of configurable parameters, see the following TechNote: http://support.veritas.com/docs/283641.

Accessing and viewing the Settings Utility

▼ To access the Settings Utility:

■ Do one of the following:

■ Navigate to the CPS Services directory C:\Program Files\Symantec\Continuous Protection Server\Services, and double-click SettingsUtility.exe.

■ From the Administration Console, select the Tools menu and then select Settings Utility.

Once accessed, the Symantec Continuous Protection Server 11d - Settings Utility screen displays the following.

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.




About the Settings Utility tunable parameters

The tunable parameters currently identified in the Settings Utility are as follows.

Caution Modifying multiple parameters may have unpredictable and adverse consequences. Symantec recommends that these parameters be changed only by knowledged users or at the guidance of Symantec Technical Support.

Parameters pane ◆ Location is the registry path for each parameter.

◆ Value Name is the specific name of the registry value. See “About the Settings Utility tunable parameters” on page 66.

◆ Current Value is the current value of the registry entry.

Refresh Click Refresh button to update the values in the Parameter pane after making changes.

Help Click Help button to learn more about the Settings Utility.

Reset Defaults Click Reset Defaults to restore all parameters to their original default values.

Settings Utility Tunable Parameters

Parameter Value 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).

Note 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. The default value is 0.

Caution Changing this value requires that the Continuous Protection Agent Service be restarted on the server.




67

BroadcastAddress Specifies the IPv6 Multicast address to which 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.

Caution 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.

Caution 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.


Note 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.


Settings Utility Tunable Parameters (continued)





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.

Note 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.

Caution 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.








69

FFXPort Continuous Protection Agent data port.


Caution 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(ENL\Network.TCPIP)

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

The default value is usually the CMS name.


Gateway(ENL\Network.UDPv6)

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

The default value is usually the CMS name.


Gateway (ENL\System)

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

The default value is Yes for a CMS computer and No for all non-CMS computers (except in special situations where a non-CMS may be used to route ENL 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.

Caution 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.

Caution 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 (located in EFC)

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

The default value is set at install time.







71

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 (located in ENL\System)

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

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(ENL\System)

The maximum size of the ENL log in bytes.

Default is 1048576 bytes (1 MB).

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






MaxPacketSize (ENL\Network.TCPIP)

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



MaxPacketSize (ENL\Network.UDPv6)

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



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).







73

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


Caution 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.

Note 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.

Note 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 (ENL\Network.TCPIP)

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



PreferredAddress (ENL\Network.UDPv6)

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



PreferredNIC (ENL\Network.TCPIP)

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 by the MAC address of the NIC.








75

PreferredNIC (ENL\Network.UDPv6)

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 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.


Caution Changing 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, and the Continuous Management Service must be restarted on the CMS server.

RxRsaStaticPort Continuous Protection Agent RPC port.


Caution Changing 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.

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.

Caution Changing this value will require that the system be restarted.






Changing CPS tuning parameters

Caution Changing CPS tunable parameters may require restarting CPS services or systems on one or more servers in the Backup Group. Before changing any CPS tuning parameter, please review the cautions associated with changing that parameter in the CPS tunable parameters list. This information will also be displayed during the parameter changing procedure.

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.


Caution 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(ENL\System)

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.

Caution 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.








77

▼ To change the tuning parameters:

1. Open the Settings Utility (see “Accessing and viewing the Settings Utility” on page 65).

2. In the Server pane, select the server for which you want to review or change a parameter value.

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. Click OK to continue.

4. Review the warning information, and then click OK to change the parameter value.

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


79

Chapter

Backing Up Data

5


■ “About CPS data backups” on page 79

■ “Creating CPS backup jobs” on page 80

■ “Modifying backup job configurations” on page 82

■ “Starting, stopping, and canceling jobs manually” on page 90

About CPS data backupsContinuous Protection Server enables you to 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.

Once a CPS backup job has been created, it can be modified to enable additional job definition and functionality.

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

■ Filter drivers 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.

■ Scripts can be run 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.

■ Limiting bandwidth allows jobs to consume fewer resources. Advanced options are available for setting bandwidth restrictions.


Creating CPS backup jobs


Backing up System Information in CPS

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 data sets. Likewise, 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.

Related Topics:

■ “How system information is protected” on page 11

■ “Restoring System Information” on page 93

Creating CPS backup jobsJobs can be created from any Administration Console within the Backup Group. 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 steps for creating a backup job manually or using the wizard are essentially the same.

When you create a backup job, the following information is required:

■ Name and user description for the backup job.

■ The backup destination.

■ Location of the data to be backed up.

■ Schedule for the backup to occur.

Before a backup job can be created, a backup destination must have already been defined (see “Managing backup destinations” on page 54).


Chapter 5, Backing Up Data

Creating CPS backup jobs

81

▼ To create a CPS backup job using the wizard:

1. From the navigation bar, click Setup.

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, enter 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. (See “Adding a backup destination” on page 55.)

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

Caution 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 by the following icons.

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.


Modifying backup job configurations


7. On the Select When to Backup screen, designate when the backup should occur. The options are:

The Completing the Backup Job Wizard screen indicates the completion of the backup job configuration. It also provides an option to create another backup job if wanted.

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

Modifying backup job configurationsThe backup job configurations that are defined when the backup job was created can be modified. The settings that can be modified include the backup job name and backup job description.

Note Backup jobs restart if the job is modified while it is running.

▼ To access and modify the 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.

Whenever a file changes This option 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 This option enables you to 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.

Note 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

This option enables you to back up the contents of the folder or file on demand. This job will not start automatically.




83

4. Under Settings, click General.

5. Modify 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.

▼ To move a backup job to a different backup destination:




4. In the Backup destination drop-down list, select the new backup destination for the job.

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

Moving a job between backup destinations does not delete the data from the original backup destination. Instead, once the backup destination has been changed and the job run, a dialog is displayed informing the user of the change and allowing them to launch Windows Explorer to display the root folder of the original backup destination. From 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.

Including and excluding information to back up

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.

Caution 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 to 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 used to decide whether or not to back up a file.

Note 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.




85


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.

▼ To modify include and exclude filters:



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


Type Kind of filter. Your options are:

◆ Include

◆ 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 the check box if the include or exclude filters apply to subdirectories of the backup selection.




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


7. Select the 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.


▼ To delete included and excluded filters:





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


7. Select the include or exclude filter, and then click Delete.

8. Confirm that you want to delete the selected include or exclude filter.

9. Click OK.





87

Changing backup schedules

As your data protection needs change, you may need to change the backup schedule. Backups can be scheduled to run continuously (whenever changes are made to a file), periodically (according to a schedule), or when needed (manually).

Note 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.

▼ To change the schedule for a backup job:




4. Under Settings, click Schedule.

5. Under Back up the selected files and folders, select the appropriate option as follows. For a description of the various backup job schedules, see “About backup job schedules” on page 10.

6. Click OK.

7. Under Back up the selected files and folders, select According to a schedule, and then click Edit Schedule.


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

Starts the backup job when manually stared from the CPS Console.

Run on these days Select the days of the week you want to run the backup. Clear the check box next to the days you do not want the backup to run.For example: To back up daily, select all the days of the week.




9. Click OK, and then when the Backup Job Properties dialog box appears, click OK.

Limiting bandwidth that is dedicated to a backup job

CPS enables you to specify bandwidth properties to better manage your resources during backup jobs.

Note The 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 bandwidth that is dedicated to 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 appropriate options as follows:

8. Click OK.

Frequency To run a scheduled backup at a specific time, select Run only at, and then indicate the time.

To run the backup periodically, select Run, and then indicate the frequency, start time, and end time.For example: Run every 1 Hour from 8:00:00 A.M to 5:00:00 P.M.

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.




89


Adding scripts that run 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.

See also “Understanding the CPS service account” on page 140 for user rights and credentials that are required to run scripts.

▼ To add a script that runs before or after backup jobs:



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. To add a script that runs before or after the backup job, click Add, and then complete the appropriate options as follows:

Server Select the server on which to run the script.

Event Select when the script will run. Your choices are:

◆ Pre-backup

◆ 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 completed within xx minutes

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


Starting, stopping, and canceling jobs manually


Starting, stopping, and canceling jobs manuallyYou can manually manage CPS jobs, including starting, stopping, and canceling jobs.

▼ To start, stop, or cancel a job manually:

1. On the navigation bar, click Job Monitor.

2. In the Current Job Filter box, click one of the following:

■ All jobs

■ Backup jobs

■ Restore jobs

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

4. Do one of the following:

Run asynchronously Check Run asynchronously 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, clear the check box.

To start the job Click Start Job.

To stop the job Click Stop Job.

To cancel the job Click Cancel Job.


91

Chapter

Restoring Data

6


■ “Restoring files and directories” on page 92.

■ “Restoring System Information” on page 93.

■ “Restoring network shares” on page 95.

Continuous Protection Server enables you to 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.

If Business Servers in the Backup Group are running Microsoft Windows Server 2003, data can be restored back to the Business Servers directly from Backup Exec. If Business Servers are running under other operating systems, files from Backup Exec must be restored to a Protection Server, and then using CPS, the files may be restored to the Business Servers. For additional information on the interaction between CPS and Backup Exec, see “Using CPS with Backup Exec” on page 115.

Related Topics:

“Retrieving files using Backup Exec Retrieve” on page 99

“Restoring CPS with Backup Exec” on page 120


Restoring files and directories


Restoring files and directoriesFiles and directories can be restored through the 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.

Caution 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.

▼ To restore files and directories:

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.


Restore job name Abbreviated name of this restore job.For example: SLOMKTProposals.

Description Full name or brief description of the restore job.For example: San Luis Obispo Marketing Proposals Restore Job.

Restore to Location where the selected files and folders will be copied.

Options Your choices are:

◆ 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. If this option is not selected, the contents of the restore directory are added to the alternate restore folder.

Note When restoring directories containing reparse points, you must either select the Preserve folder structure option or restore the directory to an empty directory.


Chapter 6, Restoring Data

Restoring System Information

93

5. Click OK.

6. Click OK to clear the confirmation message.

Related Topics:

“Restoring network shares” on page 95

Restoring System InformationRestoring System Information (System State or Shadow Copy Components) involves copying specific files from a Protection Server back to a Business Server.

Caution Symantec does not recommend restoring 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.

Note 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 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.

▼ 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: SLOSRCSystem.

Description Full name or brief description of the restore job.For example: San Luis Obispo Source Server System State.

Restore to System State will always be restored to its original location.


Restoring System Information


5. Click OK.

6. Click OK to clear the confirmation message. As soon as the System Information is restored, the server will automatically restart.

Related Topics:

“How system information is protected” on page 11

“Backing up System Information in CPS” on page 80

Restoring System State to an Active Directory system

System State can be restored to a system that is an Active Directory.

Note 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 following Microsoft publication: “How To Reset the Directory Services Restore Mode Administrator Account Password in Windows Server 2003” at the following Web site, http://support.microsoft.com/default.aspx?scid=kb;en-us;322672.

▼ To restore System State to an Active Directory system:


2. In the selection pane, select System State.



5. Click OK.

6. Click OK to clear the confirmation message. The computer will restart in DSRM mode.

Restore job name Abbreviated name of the restore job.For example: SLOSRCSystem.

Description Full name or brief description of the restore job.For example: San Luis Obispo Source Server System State.

Restore to System State will always be restored to its original location.


Chapter 6, Restoring Data

Restoring network shares

95

7. Log on using your DSRM password.

8. Double-click the symantec dsrm system state restore.bat file located on the Desktop. You can monitor the progress in the command window. As soon as the System State restore has completed, the server will automatically restart back in normal mode.

Restoring network sharesRestoring 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 originally written to a share. After restoring shared folders, the screen must be refreshed before the shared folder icon appears.

Note Network shares cannot be restored if they are in use at the time of the restore.

▼ To restore network shares:


2. In the task pane, under Views, click Console restore.

3. In the results pane, select the restore job.

4. Do one of the following:

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



Restoring network shares



8. Click OK.

9. Click OK to clear the confirmation message.

Related Topics:

“Restoring files and directories” on page 92

“Restoring System Information” on page 93

Restore job name Abbreviated name of the restore job.For example: SLOMKTShare.

Description Full name or brief description of the restore job.For example: San Luis Obispo Marketing Shared Folders.

Restore to Location where the selected files and folders will be copied.

Note Shares can only be restored to their original location, although the files in a share can be restored elsewhere.

Options Your choices are:

◆ 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.


97

Chapter

Using Backup Exec Retrieve

7


■ “About Backup Exec Retrieve features” on page 97

■ “Security and credentials for Backup Exec Retrieve” on page 98

■ “Retrieving files using Backup Exec Retrieve” on page 99

■ “Using CPS with Backup Exec Desktop and Laptop Option” on page 101

Continuous Protection Server allows users to restore files directly back to their workstation through Backup Exec Retrieve and a Web browser. Users can view and retrieve the contents of shared folders to which they have permission.

Backup Exec Retrieve is optimized for Microsoft Internet Explorer (6.0 or later). Backup Exec Retrieve also works with other Internet browsers, although screen layouts may vary. Likewise, Backup Exec Retrieve uses Windows security and Internet Explorer download features. Thus, Backup Exec Retrieve is limited to Windows-based platforms.

Note Backup Exec Retrieve is designed to enable users to restore their everyday office documents, PST files and the like. It is not designed to restore system databases or other system-level files. Likewise, users cannot delete files using Backup Exec Retrieve.

About Backup Exec Retrieve featuresBackup Exec Retrieve enables desktop and laptop users to recover their own files on demand. You can search for files by name, browse through files in shared folders, or view recently changed or deleted files. Downloading selected files restores the selected copy to the user’s computer.


Security and credentials for Backup Exec Retrieve


Features of Backup Exec Retrieve include the following.

Security and credentials for Backup Exec RetrieveBackup Exec Retrieve is protected by Windows-level security. You will be prompted for your Windows domain logon information. This information is used to restrict the files that you can view and retrieve.

If you protect a server, users of Backup Exec Retrieve can only access files and folders originally written to a share. That is, unless a folder is shared from a file server, you cannot see or retrieve the files.

Internet Explorer security on Windows Server 2003

This topic only applies to user workstations operating on Windows Server 2003. When restoring files as a desktop user, Continuous Protection Server is optimized to display Backup Exec Retrieve through the Microsoft Internet Explorer (IE) browser. To ensure the retrieval process runs smoothly, you must define the destination as a trusted site in IE. Alternatively, you can lower the security settings from High to Medium. However, the

Backup Exec Retrieve features

Feature Description

Search Find files by name. Use standard Windows-like search capabilities to find a file when the file name is unknown or only partially known.

Browse Navigate through shared folders to which you have permissions, and view any of the files that were backed up. When a file is located, you can view all stored versions of that file. Review the date, time, and file size to determine the version of the file you want to retrieve.

Recent Activity View a list of files that were recently modified or deleted. Recent activity includes files from the earliest through the latest snapshot on record. The file list is sorted in order by files from today, yesterday, last week, two weeks ago, and older.

Note The Recent Activity list does not show any files that have been modified or deleted after the last snapshot was taken.

Download List Restore files in a manner similar to buying items in an online store. Select files for download while searching, browsing, or viewing recent activity. Review the list of files, and then download all of the files at once. Unless specified otherwise, the files are saved to My Documents\My Restored Files.


Chapter 7, Using Backup Exec Retrieve

Retrieving files using Backup Exec Retrieve

99

security settings should be lowered at your own risk. By setting the Protection Server in IE as a trusted site, the higher level of security is maintained and the Backup Exec Retrieve appears correctly.

Refer to the Microsoft Internet Explorer documentation for information about adding a trusted site to IE or changing the level of security. The site that should be added is: https://<CMSServerName>:8443.

Retrieving files using Backup Exec RetrieveDesktop users can restore files using Backup Exec Retrieve, which is accessed through your Web browser and a designated URL.

Note Files that are downloaded with Backup Exec Retrieve are saved with the default permissions of the folder they are placed into. This is like other files that are downloaded from the Internet.

▼ To retrieve files using Backup Exec Retrieve:

1. In the Web browser address bar, type the URL of your Continuous Management Service.

The default URL is https://<CMSServerName>:8443/BERetrieve.Where <CMSServerName> is the name of the server hosting the Continuous Management Service, and 8443 is the port number. The term BERetrieve at the end of the path is case sensitive. Contact your system administrator if you do not know the name of the CMS server.

2. If the standard Windows Security Alert screens are displayed, click Yes or OK to continue.

3. If a message appears with information about the security certificate, it is related to SSL Certificates. Click Yes to continue.

4. In the Backup Exec 11d Retrieve screen, enter the user name, password, and domain (or computer name if in a workgroup). Click Log on to continue.

5. In the Backup Exec Retrieve screen, select one of the following options to locate and specify the data to be retrieved:

■ The Search tab allows you to search for the data by file name.

■ The Browse tab allows you to browse the backup data for the data.


Retrieving files using Backup Exec Retrieve


■ The Recent Activity tab allows you to select data from the files that were recently modified or deleted.

6. Click Browse.

7. Click the computer name to display the folders that have been backed up. Subsequent clicks on the folder name allow you to navigate deeper into subdirectories. At any level, you can use the check box to select that folder and subordinate folders and files.

8. To view recently modified or deleted files, on the Recent Activity tab, do one of the following:

■ Click Recently Modified to view modified files.

■ Click Recently Deleted to view deleted files.

9. Click Add to Download List to add the file to your list of data to be retrieved. Add more files to the download list using the Browse tab again.

10. As soon as all files are selected for retrieval, select the Download List tab to display a list of all files selected.

11. Click Download Selected Items. A download screen notes that the download will begin automatically.

12. Internet Explorer's standard File Download screen displays. Click Open (or Run) to download a small executable file (DownloadManager.exe) that restores the selected files.

13. The File Restore screen prompts for a directory where the files are restored. Select the default <user>\My Documents\Restored Files, or browse to a location. Click Next to begin the file retrieval.

14. Verify the files you selected were restored to the specified location.

The Versions field is added to the data listing whenever files are displayed. Click the versions icon to show all the versions of a particular file.


Chapter 7, Using Backup Exec Retrieve

Using CPS with Backup Exec Desktop and Laptop Option

101

Using CPS with Backup Exec Desktop and Laptop OptionWith CPS 11d, Backup Exec Web Retrieve may be associated with Backup Exec Desktop and Laptop Option (DLO) so that end users can restore their data that was copied to a network share by DLO.

To enable DLO integration with CPS, the Continuous Management Service (CMS) must be installed on the same computer as the Backup Exec Media Server. Additionally, the administrator needs to install a Continuous Protection Agent (CPA) on each DLO file server. The CPA installation can be performed by manually running setup on each computer, or using the push-install mechanism in the CPS Administration Console. The Console helps the administrator with this task by indicating DLO file servers in the CPS push-install computer selection list (see “Push-installing CPS Components” on page 32).

The initial indexing of the DLO file server may take significant time, during which the search results may be incomplete. The CPS Console will display an alert when the initial indexing is completed. Additionally, the user sees a warning to this effect while the initial indexing is running.

When searching for files, you can find DLO files based on their filenames, and all versions of the DLO file that match the criteria (excluding local revisions). Recent Activity searches includes DLO files as well as files written directly to shares. Additionally, DLO results in both search and recent activity display a unique icon to distinguish them as DLO results.

Files are indexed nearly immediately after being copied to the DLO file server. Snapshots are not required or recommended on the DLO file server to begin the indexing. If there are snapshots of the DLO file server, they are ignored for DLO/CPS integration purposes.

To restore DLO data, follow the procedures in “Retrieving files using Backup Exec Retrieve” on page 99.

Securing files that are not retrievable

Backup Exec Retrieve does not restore Windows Encrypted File System (EFS) files. Likewise, compressed or sparse files are restored in their entirety (not compressed and not sparse). Reparse points are also not restorable using Backup Exec Retrieve.

Also, permissions and other information are lost as a side-effect of Web downloads. DLO unencrypts EFS files, and then re-encrypts them (optionally) with their own key. Thus, users can restore EFS files that are protected by DLO using Backup Exec Retrieve, but the restored file is no longer encrypted on the user’s computer.

PST and Lotus Notes files can also be restored, but only the entire file.

Note Files on DLO file servers that are located on FAT32 partitions are browsable, but not searchable.


Using CPS with Backup Exec Desktop and Laptop Option



103

Chapter

Monitoring CPS Processes

8


■ “Viewing the job status” on page 103

■ “Viewing a job report” on page 107

■ “Managing CPS job alerts” on page 109

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:

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

Viewing the job statusA 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, four separate job pairs exist, as follows.

Business Server #1 to Protection Server #1 (i.e. 1:1)



Viewing the job status




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. The possible job states are as follows.

CPS 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.

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.

Note 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.


Chapter 8, Monitoring CPS Processes


105

Viewing the status of a job or the 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.

▼ To view the status of a job and job pairs:


2. 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

CPS job and pair status

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.

Information that is provided for the job and job pair listings (columns) are as follows.

Canceled The job has canceled and all pairs have stopped running.

Note 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.

Note If the job is continuous, the job never completes. A continuous job must be stopped or cancelled.

CPS job states (continued)

Job State Description





Column Description

Current Jobs Status

◆ Job name The name that was given for the job.

◆ Type The job type can be one of the following:

◆ a backup job

◆ a restore job

◆ an Exchange Log job

◆ Status For a description of the possible job statuses, see “About job states” on page 104.

◆ 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.

Pairs in Job <JobName> status (indicated for the job that was selected in the upper results pane)

◆ Source The name of the source computer.

◆ Destination The name and path to the destination computer.

◆ Status For a description of the possible job statuses, see “About job states” on page 104.

◆ Transfer Rate The instantaneous rate that the job is running. For example, 21 Kbytes/Second.



Viewing a job report

107

Viewing a job reportDetailed information for the CPS jobs is provided in the Job Report.

▼ To access and view the job report:


2. In the results pane, 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. The two possible states for CPS jobs are:

■ All CPS jobs are good

■ One or more problems exist with the CPS jobs

◆ 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.


Column Description


Viewing a job report


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).

The CPS Jobs topic box has several subordinate topic boxes that may be expanded, as discussed below.

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 Topic Box

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 Topic Box

Provides a list of the files and folders that are included and excluded from the job.

Backup Job Pre/Post Commands Topic Box

Displays any pre- or post-commands that were assigned to the 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 Topic Box

Contains CPS job log entries for the period since the job last ran.

Note 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 Topic Box 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.

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.

Note Destination latency can only be calculated when both servers in a pair are running Continuous Protection Server version 10d (or later).



Managing CPS job alerts

109

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

Managing CPS job alertsAlerts 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. Alert categories include:

■ 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 deleted manually. You can delete one alert, multiple alerts, or all alerts in history at once.

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:

■ Category

■ Job name

■ Message

Pair Log Topic Box Contains CPS pair log entries.

Note 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.

Subordinate jobs topic boxes (continued)





■ 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 Active Alerts.

3. To view details of a specific alert, in the selection pane, select the alert. The details appear in the preview pane.

4. In the Active Alerts Filter box, click one of the following:

■ All alerts

■ Error alerts

■ Warning alerts

■ Information alerts

5. To sort the list in ascending or descending order by any column, click the column heading.

6. To change the order in which columns display, click and drag a column to a new position in the list, and then drop it into place.

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 deleted manually. When you view the alert history, you can filter the list to show only errors, only warnings, or only informational messages.




111

▼ To view and filter alert history:


2. Click Alert History.

3. In the Alert History Filter box, click one of the following:

■ All alerts

■ Error alerts

■ Warning alerts

■ Information alerts

4. To view details of a specific alert, in the selection pane, select the alert. The details appear in the preview pane.

Alerts older than 30 days are removed by the system.

5. To sort the list in ascending or descending order of any column, click the column heading.

6. To change the order of the columns, click and drag a column to a new position in the list, and then drop it into place.

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 one of the following:

■ Active Alerts tab

■ Alert History tab

3. In the selection pane, right-click the alert, and then click Properties.

The Alert Properties dialog box provides the following options:

Category Title of the alert.




4. View the alert properties, and then 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 holding the CTRL key.

▼ To respond to an active alert:


2. Click the Active Alerts tab.

3. In the selection pane, select the alerts that you wish to respond to.

4. Right-click the alerts, and then click Respond.

5. Click a response for the alert.

To respond OK to all alerts selected, click Respond OK to All. If the alerts have an OK response available, they are cleared from the list and moved to alert history. If multiple alerts were selected, respond separately to each alert that displays.

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 deleted manually. You can delete one alert at a time, multiple selected alerts, or all alerts at once. Multiple alerts are selected by holding the CTRL key. To change the time that alerts remain in history, see “Changing CPS tuning parameters” on page 76.

Server 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.




113

▼ To delete alerts from history:


2. Click the Alert History tab.

3. In the selection pane, select the alerts you want to delete.

4. Right-click the alerts, and then click Delete. To delete all alerts from history, click Delete All.

5. Click Yes to confirm that you want to delete the selected alerts from the history.


115

Chapter

Using CPS with Backup Exec

9


■ “Protecting CPS with Backup Exec” on page 116

■ “Monitoring CPS Jobs in Backup Exec” on page 122

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. Symantec provides full integration between Backup Exec and CPS, ensuring valid, reliable backup and recovery of the data, as well as a consistent user experience through both products.

Using SmartLink technology, CPS jobs can be associated with existing Backup Exec jobs. Doing so enables you to view alerts and log entries for CPS jobs through the Backup Exec Administration Console.

When jobs are created or modified, CPS data selections are made through a tree view in the Backup Exec Administration Console. Each server that is affiliated with CPS displays a Continuous Protection Server node from which CPS data can be selected. If a new Protection Server is added to the CPS Backup Group after backup jobs are 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 CPS with Backup Exec


Protecting CPS with Backup ExecYou can back up several types of CPS data with Backup Exec. CPS data you can select for Backup Exec backup jobs includes:

■ CPS databases that contain information, such as CPS configuration settings, the CMS, and the indexing database.

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

Note 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.

Related Topics:

“Backing up CPS with Backup Exec” on page 117.

“Backing up the Continuous Management Service (CMS)” on page 118.

“Backing up a Protection Server” on page 118.

“Restoring the CPS Protection Server” on page 121.

“Restoring a CPS Business Server” on page 121.

Configuring CPS for Backup Exec

Continuous Protection Server is compatible with Backup Exec media server version 11d, or Remote Agent for Windows Systems (Remote Agent) version 11d. Installing version 11d of the media server or Remote Agent is the only requirement to integrate CPS and Backup Exec.

Note If Remote Agent was not installed with the original CPS installation, install it before creating backup and restore jobs with Backup Exec. See Chapter 2, “Installing Continuous Protection Server”.


Chapter 9, Using CPS with Backup Exec


117

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 media 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.

The expanded Continuous Protection Server tree view includes the following elements:

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.

Continuous Protection Server tree view elements

CPS Node Description

Continuous Protection Server

The Continuous Protection Server node is the gateway to all CPS 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 117.

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 118.

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 119.

Snapshots Snapshots are listed in order by date and time. See “Backing up snapshots” on page 119.




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.

Backup Job Properties selections screen

CPS Databases

Backup Destination

Business Server

Snapshots




119

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.

If you select to back up a snapshot and the snapshot is deleted before the job runs, the job fails with the message, “Unable to attach”. Edit the backup job to include a snapshot other than the one that was deleted, or remove the snapshot selection from the backup job.




Restoring CPS with Backup Exec

Restoring CPS and Backup Group data involves selecting information from the Backup Exec media server and then:

■ Restoring the data to a Protection Server.

■ Restoring the data directly back to the Business Server from which it was backed up.

Note 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. The expanded Continuous Protection Server tree view includes the following elements.

Restore Job Properties selections screen

Backup Destination

Business Server

Snapshots




121

Restoring the Continuous Management Service

The CMS can be hosted on the Protection Server or another server. In the event the server hosting 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.

Note 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 CPS 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 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 would want to redirect the restore job to the new server.

Caution Before restoring data from Backup Exec to CPS, stop all continuous jobs on the CPS Protection Server and its associated Business Servers. In CPS, change the scheduled jobs to manual, and then in Backup Exec, restore the selected data.

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.


Monitoring CPS Jobs in Backup Exec


Monitoring CPS Jobs in Backup ExecYou 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 using the SmartLink Wizard in CPS. SmartLink technology integrates Backup Exec with other Symantec products, such as CPS, Storage Exec, and Replication Exec.

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.

Related Topics:

“Setting up a SmartLink connection between CPS and Backup Exec” on page 122

“Viewing alerts posted to Backup Exec” on page 124

“Viewing job logs posted in Backup Exec” on page 128

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.

▼ 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. See “Backing up CPS with Backup Exec” on page 117.

3. On the CPS navigation bar, click Setup.

4. On the task pane, 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 name of the server where the CPS backup job is located.




123

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. For proper credentials, see “CPS credentials and security issues” on page 140.

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.

If SmartLink is run with multiple media servers with a potential for fail over 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.




Upon 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.

To manually edit the command, see “Using the SmartLink Command Line Syntax” located at the following: http://support.veritas.com/docs/277859.

Note 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.

Related Topics:

“Monitoring CPS Jobs in Backup Exec” on page 122

“Viewing alerts posted to Backup Exec” on page 124

“Viewing job logs posted in Backup Exec” on page 128

Viewing alerts posted to Backup Exec

▼ To access and view Backup Exec Alerts:

1. On the Backup Exec navigation bar, click Alerts.

2. Select the alert from either the Active Alerts or Alert History pane.

3. Under General Tasks in the task pane, click Properties.

4. View the following 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.




125

The CPS-related alerts are organized into two categories: fatal events, and CPS job or pair problems.

Note 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.

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. Fatal conditions include the following.

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.

Fatal alert messages

Message Description

SmartLink is unable to contact the Continuous Management Service (CMS). The server may be down or a network issue may be preventing SmartLink from contacting the CMS. No CPS Backup data validation is possible.

Situation:

SmartLink is unable to connect to the CMS.

Solution:

Check network connectivity and that the CMS is running.

SmartLink has failed to authenticate to the Continuous Management Service <CMSservername>. No CPS Backup data validation is possible. Check the user name and password provided to SmartLink.

Situation:

SmartLink cannot authenticate to the CMS.

Solution:

Verify credentials to CMS, per “CPS credentials and security issues” on page 140.




SmartLink is unable to contact the Continuous Management Service (CMS)

Situation:

General failure CMS errors. This alert is a catch-all for non-network and non-credentials based errors.

Solution:

Attempt to restart the services, and if not successful, contact Symantec Technical Support.

CPS Backup Job <Cpsjobname> - SmartLink has failed to authenticate to the JCD Server <JCDservername>. The Job and Pair Logs are Unavailable.

Situation:

Failure to authenticate to a JCD indicates that SmartLink is unable to acquire log entries. However, an alert is generated because it is a correctable configuration error.

Solution:

Verify credentials to JCD server, per “CPS credentials and security issues” on page 140.

CPS Backup Job <Cpsjobname> - SmartLink is unable to contact the JCD Server <JCDservername>. The server may be down or a network issue may be preventing SmartLink from contacting the JCD. The Job and Pair Logs are Unavailable.

Situation:

JCD is unreachable, which has the same effect as the failure to authenticate.

Solution:

Check network connectivity and that the JCD server is running properly.

Cpsjobname JCDservername Situation:

General failure for non-network and non-credentials based JCD errors.

Solution:

Attempt to restart the JCD services, and if not successful, contact Symantec Technical Support.

CPS Backup Job <invalidjobid> - Invalid CPS Backup Job ID.

Situation:

A specified CPS Job ID is invalid. This condition is a correctable SmartLink configuration error and thus generates a top-level Alert.

Solution:

Verify that the correct job ID has been entered.

Fatal alert messages (continued)

Message Description




127

About 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.

CPS Backup Job <Invalidjobname> - Invalid CPS Backup Job Name

Situation:

A specified Job name is invalid. This condition is a correctable SmartLink configuration error and thus generates a top-level Alert.

Solution:

Verify that the correct job name has been entered.

CPS Backup Job <Cpsjobname> - The Continuous Management Service (CMS) and the CPS Backup JCD server do not have consistent Job State information. The actual state of Job is unknown.

Situation:

The CPS job is in an unknown state. In this case, the CMS does not have the latest information regarding a job's run state.

Solution:

Check the connectivity between the CMS and JCD, and verify that each is running.

CPS Backup Job <Cpsjobname> - Unable to get pair information.

Situation:

Unable to get Pair information.

Solution:


CPS Backup Job <Cpsjobname> - Unable to get JCD information.

Situation:

Unable to get JCD information.

Solution:


CPS Backup Job <Cpsjobname> - Unable to get job log details Information.

Situation:

Unable to get job log information.

Solution:


Fatal alert messages (continued)

Message Description




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.

Viewing job logs posted in Backup Exec

SmartLink posts detailed information about the CPS backup job in the Backup Exec Job Logs.

▼ To access and view Backup Exec job logs:

1. On the Backup Exec navigation bar, click Job Monitor.

2. From 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. Expand the Job Operation - Continuous Protection Job headings by clicking the plus sign [+] to the left of the heading.

CPS Backup Pair Alerts

Alert Field Description

CPS Backup Job <cpsjobname> - Exception in One or More CPS Pairs.

Situation:

One or more pairs in one or more of the CPS jobs are inconsistent.

Solution:

Review the “Exceptions Topic Box” on page 131.




129

About CPS backup job log details

The CPS job logs contained in the Backup Exec Job Logs consists of various topic boxes.

For details about what displays in the various topic boxes on the job log, see the following:

■ “Job Operation - Continuous Protection Job Topic Box” on page 130

■ “Command Line Syntax Error Topic Box” on page 131

■ “Exceptions Topic Box” on page 131

■ “Backup Exec SmartLink Options Topic Box” on page 132

■ “Backup Exec SmartLink Run Log Topic Box” on page 132

■ “CPS Jobs Topic Boxes” on page 133




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. Three possible states exist for CPS jobs:

■ All CPS jobs are good

■ One or more problems exist with the CPS jobs

■ Fatal errors occurred that prevent SmartLink from running

Based on these quality states, one of the following messages appears in this topic box:

CPS Summary Log Messages

Message Description

All CPS Backup Jobs are Good:

CPS Backup This message appears if all CPS jobs have completed or are running without errors.

There are One or More Problems:

CPS Backup If there are any problems with the CPS jobs or pairs, this message appears 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 131).

A Fatal Error has Occurred:

This message appears when syntax errors are encountered in the SmartLink 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 131).

Backup Exec Errors ◆ SmartLink may be invoked using invalid Backup Exec credentials, which prevents SmartLink from connecting to the Backup Exec server. For example, this message appears if all CPS Jobs are good, but invalid Backup Exec credentials were provided.

◆ SmartLink was not able to acquire the Backup Exec job information from the Backup Exec server.




131

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 following message appears in the Job Operation - Continuous Protection (Summary) topic box.

SmartLink Command Line has error . . . .

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.

SmartLink is unable to contact the Management Server. The server may be down or a network issue may be preventing SmartLink from contacting the Management Server. No backup data validation on Protection Server is possible.

The server may be down or a network issue may prevent SmartLink from contacting the CMS. No CPS Backup data validation is possible.

SmartLink is unable to contact the Management Server.

The server may be down or a network issue may prevent SmartLink from contacting the CMS. No CPS Backup data validation is possible.

CPS Summary Log Messages (continued)

Message Description




■ Failure to connect to the Job Control Delegate (JCD) to retrieve log details.

Backup Exec SmartLink Options Topic Box

This topic box provides general information on the CPS backup job, including 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.

Exceptions

Exception Description

Goodness Criteria The criteria that are evaluated to determine the consistency of a job are:

◆ Each pair must be in a consistent state, and

◆ Each pair must have been consistent since the last time the associated Backup Exec job was run.

Job Name or ID Not Found This exception is given when one or more job names or IDs on the 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.




133

This topic box provides detailed information on the CPS and backup jobs. This information is generally only required by Technical Support to aid in troubleshooting the job. The information that is displayed in this topic box includes 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.

Note Jobs that have exceptions are listed before any successful jobs.

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 Topic Box 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 Topic Box 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 vs. 24-hour clock, UTC vs. local time, international time format, etc.)

The number of entries is optionally configured with the –logLimit command line parameter.

Backup Pair Topic Box 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.

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.

Note Destination latency can only be calculated when both servers in a pair are running Continuous Protection Server version 10 (or later).

Pair Log Topic Box 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 vs. 24 hour clock, UTC vs. local time, international time format, etc.)

◆ The number of entries is optionally configured with the –logLimit command line parameter.

Subordinate Jobs Topic Boxes (continued)



135

Chapter

Troubleshooting Continuous Protection Server

10

This section provides information about CPS components, configuration, backup jobs, restore jobs, the job monitor, alerts, Backup Exec Retrieve and various CPS tools.

See also the Symantec Web site for an updated list of Frequently Asked Questions (FAQs), release notes, and a technical knowledge base for this product. See “Accessing the Symantec Technical Support Web site” on page 14.

The common known CPS issues are grouped by subject and include the following.

■ “CPS compatibility issues” on page 136

■ “CPS installation and upgrade issues” on page 138

■ “CPS credentials and security issues” on page 140

■ “CPS components issues” on page 143

■ “CPS configuration issues” on page 145

■ “CPS general issues” on page 147

■ “CPS backup and restore job issues” on page 149

■ “CPS System State backup and restore issues” on page 151

■ “CPS job monitor issues” on page 151

■ “Backup Exec Retrieve issues” on page 152

■ “CPS Tools and Utilities” on page 155


CPS compatibility issues


CPS compatibility issues.


Issue Description

CPS product compatibility The Symantec family of products is designed to protect all of your business information. Each product provides a different level of protection, and works together to ensure your data is available when you need it.

Continuous Protection Server is compatible with the following Symantec products:

◆ Backup Exec (10d or later) for Windows Servers backs up your application servers such as Exchange, SQL, and the Continuous Management Service. It also provides long-term storage to various media.

◆ Backup Exec (10d or later) Desktop and Laptop Option protects information that is created on remote and mobile personal computers.

◆ Storage Exec prevents unwanted files from being stored on the Business Server or Protection Server.

◆ Storage Foundation for Windows provides easy-to-use online disk storage management for mission-critical, enterprise Windows environments.


Chapter 10, Troubleshooting Continuous Protection Server


137

CPS and Backup Exec compatibility

CPS uses Backup Exec to access the System State and perform backups and restores of the CPS files. This functionality is contained in the Backup Exec Remote Agent for Windows Systems (Remote Agent) as well as the Backup Exec Media Server. A minimum Backup Exec version of 11d is required on any server running the Continuous Protection Agent.

Caution 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 to version 11d. However, this upgrade breaks existing backup functionality if the Backup Exec Media Sever is a 10.x or earlier version. The installer will always alert you before upgrading the Remote Agent.

The same consideration should be given when upgrading the Media Server if that is where the Continuous Management Service will run. If a version 10.x Media Server is upgraded to 11d, then it is no longer able to back up any of its existing (10x) clients.

File system filter driver compatibility

Software that use 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.

If an incompatible product is installed on the system that is to run CPS, it is necessary to disable or remove the incompatible product before installing CPS. If CPS is already installed on the system, do not enable or start the other product while CPS is running.

See the Readme file accompanying this release for the most current list of products with incompatible filter drivers.

CPS compatibility issues (continued)

Issue Description


CPS installation and upgrade issues



CPS installation issues

.

CPS installation issues

Issue Description

Workgroups and domains Symantec does not recommend or support mixing the servers hosting the Continuous Management Service and Continuous Protection Agent between workgroups and domains.

Anti-spyware software Any program that blocks executables, services, etc., should be disabled or if prompted for permission to install CPS, answer “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.

Apache Tomcat Web Server If the Web Restore Server Component is installed during the installation of the CMS, a modified version of Apache Tomcat Web Server 5.5.7 is also installed. All Web servers are common targets for malicious attacks. Thus, in the event that any future issues arise with this product, contact Symantec Technical Support for corrective information.

Push installing over domain trust 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.

NIC failure after installing CPS If a NIC card fails after installing CPS, the registry key for the new NIC card must be updated for CPS to work properly. See the following TechNote: http://support. veritas.com/docs/277852.

Microsoft Internet Explorer version 6.0 or later required

Some features of CPS require Internet Explorer 6.0 or later, such as Backup Exec Retrieve and Job Reports. Thus, earlier versions should be upgraded for proper functionality.




139

CPS uninstall issues

Pathnames with Asian characters CPS fails to start if CPS has been installed in a directory whose pathname includes 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 service fails to start

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. See the following: http://www.microsoft.com/technet/prodtechnol/windows2000serv/support/nlbcontb.mspx

Viewing installation logs For installation troubleshooting purposes, you my view the installation logs in the following directory:

%allusersprofile%\application data\symantec\Backup Exec CPS\logs

CPS uninstall issues

Issue Description

Uninstall and reinstall loses job history and pair logs

If CPS is uninstalled and reinstalled, information in the job logs and pair logs are not saved. For additional information, see the following TechNote: http://support.veritas.com/docs/278649.

CPS installation issues (continued)

Issue Description


CPS credentials and security issues




Issue Description

Understanding the CPS 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.

Note 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 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. See the Windows documentation.

The account that 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.




141

Installing CPS from the CD-ROM Administrator rights are required on the computer where the software is being installed when performing a CD installation.

Push installing CPS components 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.

Using the Administration Console

Administrator rights are required on the system running the CPS Administration Console when using the Console.

Creating CPS backup jobs Backup rights are required to all referenced servers of a CPS backup job, including the server hosting the Continuous Management Service (CMS).

Working with backup destinations

Permissions of 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 directory tree when deleting backup destinations. In this case, “local ownership” must be assigned to the Domain Admin on the files and all related subdirectories if they originate from another “local system”.

CPS credentials and security issues (continued)

Issue Description




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 media server to run the pre/post commands. If the computer level credential is not available, the default logon account of the media server 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"

CPS credentials and security issues (continued)

Issue Description



CPS components issues

143


CPS Administration Console

Continuous Management Service (CMS)

Administration Console issues

Issue Description

Administration Console may run slowly when first run

The first time that you select a server to do a CPS restore, a wait cursor appears and it may take several minutes before anything 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. After the first hit to the backup destination, all subsequent access is much faster. The amount of time it takes to mount a snapshot is proportional to the size of the snapshot.

Job name and description are in a different language than the Administration Console

Consoles running on computers without the corresponding language pack that is installed is not able to properly interpret the job name or description. For example, when a job name is 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.

Continuous Management Service issues

Issue Description

The CMS must be installed before other CPS components

The CMS should be installed before other CPS components are installed.

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).




Business Servers

Protection Servers

Business server issues

Issue Description

Recovering restore selections to a restored or replaced Business Server

If a Business Server is deleted from the Backup Group, all restore selections also disappear. If the deleted Business Server is brought back into the Backup Group or another server is added 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.

Protection server issues

Issue Description

Protection Server for SmartLink must have actual server name

When creating a SmartLink association with Backup Exec, the Protection Server must be specified by an actual server name and not an IP address.

Protection Server volumes The Protection Server should have at least four separate volumes for ideal performance:

◆ System volume

◆ Journals volume

◆ Backup destination volume

◆ Snapshot storage volume for backup destination



CPS configuration issues

145


Snapshot and indexing issues

Snapshot and indexing issues

Issue Description

Snapshots fail to index properly If snapshots fail to index properly, do the following:

1. Navigate to the Indexing Services as follows:Run > Control Panel > Administrative Tools> Services

2. Verify that the Backup Exec Continuous Protection Indexing Component is running. If it is not running, start it.

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 space for indexing

The ability to search for files is accomplished by a built-in 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. 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 directory:

MinFreeSpaceMB=XX

Where XX is the number of free megabytes that are required on the server to start the indexing service.




Snapshot schedules 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 CPS are included in the scheduled snapshots.

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

Snapshot and indexing issues (continued)

Issue Description



CPS general issues

147

CPS general issues

Processing efficiency

Processing efficiency issues

Issue Description

Bandwidth throttling and Quality of Service (QOS)

Bandwidth throttling can be implemented using Quality of Service (QOS) with network switches and routers. QOS should be implemented on TCP/IP port 20481.

System may run out of memory during intensive input/output processing

A chronic “nearly out of memory” condition may exist during periods of intensive i/o processing. This state can be determined in the following way:

1. Start the Windows Task Manager.

2. Select the Performance tab.

3. Look at the “Physical Memory (K)“control group.

4. Verify how much memory is currently “Available”, and if the amount drops to “4000” or less (i.e., 4MBytes) and tends to stay there.

In this state, the system is largely unresponsive to user input and the following corrections should be made. To resolve this condition, see the following TechNote: http://support.veritas.com/docs/277876.

File system input/output deadlocks may occur when continuously backing up large database files

An input/output deadlock can occur when:

◆ CPS is used to continuously back up large databases, and

◆ the i/o activity on these database files is high, and

◆ the host server has fewer than 4 logical CPUs (i.e., 4 physical CPUs without hyperthreading, or 2 CPUs with hyperthreading).

To resolve this condition, see the following TechNote: http://support.veritas.com/docs/277871.


CPS general issues


Miscellaneous issues

Miscellaneous issues

Issue Description

Utility partitions CPS does not recognize utility partitions.

Disabling CPS SNMP support If the Windows SNMP service is installed on the computer when CPS was installed, CPS's SNMP support is automatically installed. To disable CPS's SNMP support, see the following TechNote: http://support.veritas.com/docs/277856.

Multiple pairs are configured to run between the same two computers

CPS throttles the data transmission for all pairs at the least-restrictive rate. For example, if a backup job is configured to run between two nodes with the bandwidth limited to 20% 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 database volume is exhausted

If the free space of a CPS database volume is exhausted, the Sybase Adaptive Server Anywhere 9 server may assert and refuse all new connections until the CPS services on that computer are restarted.

CPS database backup and restore Database backup and restore capabilities are based on Volume 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 additional information on the database backup and restore utilities, see the following TechNote: http://support.veritas.com/docs/277860.



CPS backup and restore job issues

149


CPS backup job issues

CPS backup issues

Issue Description

Stopping versus canceling a job 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.

Exclude list For a given job, you can define items to include or exclude from the backup selections tree. See “Including and excluding information to back up” on page 83.

Connection outages If the backup job is configured in the console 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 “stuck” 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) will be “stuck” 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.

Performing Backup Exec recovery of Continuous Protection Server

Detailed instructions for using Backup Exec Intelligent Disaster Recovery (IDR) to recover CPS that contains Backup Destinations can be found in the following TechNote: http://support.veritas.com/docs/278977.




CPS restore jobs

CPS restore job issues

Issue Description

CPS does not allow Protection Servers to be restored to a different location on the Protection Server

CPS does not allow protected files on a Protection Server to be restored to a different location on the Protection Server. To move files to different locations on the Protection Server, use the copy and paste features of Windows Explorer.

Restoring Continuous Protection Server from Backup Exec for Windows Servers

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.

To restore to a CPS source running Windows Server 2000, you must first restore the files from Backup Exec to the Continuous Protection Server destination. The files can then be restored from the destination to the source. The ability to restore from Backup Exec to a Continuous Protection Server source requires the features that are not available in Windows Server 2000.

Alternate restore destination paths

When an alternate restore destination path is chosen, be very careful not to select any path with data that needs to be saved. CPS overwrites the data in the selected directory.



CPS System State backup and restore issues

151

CPS System State backup and restore issues

CPS job monitor issues

System State backup and restore issues

Issue Description

System State backup and restore When System State is restored on Windows Server 2003 computers, the state of the restore job is reverted to “Never Run”. Additionally, all history that is associated with the restore job is lost.

Restoring System State in CPS 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 additional information on restoring System State in CPS, see the following TechNote: http://support.veritas.com/docs/278977.

CPS job monitor issues

Issue Description

Filtering the list of jobs so that all jobs are not displayed

Jobs can be filtered in a variety of ways. See “Monitoring CPS Processes” on page 103.


Backup Exec Retrieve issues




Issue Description

Backup Exec Desktop and Laptop Option

CPS does not need to store the credentials to connect to the Backup Exec Media Server. However, the CPA on the DLO file servers and the CMS must all run as an account that is a member of the Administrators group on the Backup Exec Media Server. No additional software is needed on the Backup Exec Media Server.

Trusted domains Backup Exec Retrieve does not work if the Business Servers, Protection Servers, and CMS are not located in the same (or trusted) domain(s). However, the client (Web browser) computers do not need to be in the same (or any) domain.

Non-domain environments Set up accounts with the same user name and password on the source, destination, and the Web Restore Server Component. Log on to the Web retrieval site, and select the local computer as the domain.

Files on the source that use customized permissions are not accessible through Backup Exec Retrieve. Users can view and download files accessible to everyone.

Same-date searches When searching for files to restore, if the window of the search (“From” date to “To” date) are the same, no files are listed. The “from” and “to” dates in the search window should be different by at least one day.

Multi-byte filenames If you restore a file using Backup Exec Retrieve that has multi-byte characters, you may find that the filename of the downloaded file does not match the original file name. This occurs if the Web browser computer is not running in the same language as the file you are trying to download (i.e. downloading a file with Japanese characters to an English computer). This behavior is exhibited for both the single-file download using Internet Explorer and the multi-file download using the Download Manager.




153

Folders without contents When browsing folders in Backup Exec Retrieve, you may encounter folders that have no contents. Folders may appear empty for the following reasons.

◆ The user does not have access to this folder.

◆ The backup destination that protects this folder is offline.

◆ The folder is actually empty.

No files are listed for a shown source computer

The source does not have any accessible shares. Start sharing the folder on the source, and then refresh Backup Exec Retrieve.

Protecting confidential files from being viewed or downloaded by other users

Permissions should be configured on the share, and then each destination should be backed up. CPS applies the most recent permissions to shared folders. If confidential information is accidentally shared, correct the permissions on the share, and then back up the files again.

Search results pane is blank The results pane displays shared folders to which users have Read permissions or higher, and which were backed up from the selected source. Administrator shares do not display in Backup Exec Retrieve, which is intended for user access.

The files that appear in Backup Exec Retrieve results pane originate from snapshots of the backup destination. For example, if a file is saved three times in an hour, and snapshots are scheduled to take place every two hours, the saved files appear after the snapshot of the backup destination is taken.

Backup Exec Retrieve issues (continued)

Issue Description




File Not Found Errors On some computers, opening a file directly from Backup Exec Retrieve results in a “File Not Found” error from the application that was launched to view the file. This condition results when the “do not save encrypted pages to disk” option is enabled in Internet Explorer. If this option is enabled, the file is never saved to the disk, so the application is unable to open it.

To disable this option:

1. From the Internet Explorer Tools menu, select Internet Options.

2. Select the Advanced tab.

3. Under Security, verify that the Do not save encrypted pages to disk check box is not selected. Alternatively, when prompted by the browser to open or save the file, select Save, then open the file from the saved location.

Modifying the Backup Exec Retrieve URL

The default Backup Exec Retrieve URL (https://server:8443/BERetrieve) can be modified to a simpler form, such as http://server.

To modify the default Backup Exec Retrieve address:

1. Make sure you are not running another Web server on port 80, such as IIS, Apache, etc. If you are, then you will need to disable that Web server.

2. Open a command prompt, and browse to the following directoryC:\Program Files\Symantec\Continuous Protection Server\VRTSweb\bin.

3. Execute the following command: webgui addport 80 HTTP

4. Browse to the ROOT5 folder:C:\Program Files\Symantec\Continuous Protection Server\VRTSweb\admin\root5\ROOT5.

5. Open up index.html in a text editor such as Microsoft Notepad.

6. Change URL=Home.do to URL=/BERetrieve.

7. Save the file

Now when open up your browser to http://server, you will automatically be redirected to the BE Retrieve login page.

Backup Exec Retrieve issues (continued)

Issue Description



CPS Tools and Utilities

155

CPS Tools and UtilitiesCPS includes a number of tools and utilities to extend its functionality.

CPS Database Maintenance utilities

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

The procedures associated with the CPS database maintenance utilities may be superseded by the Backup Exec backup and restore jobs (see “Protecting CPS with Backup Exec” on page 116). However, if the Continuous Management Service (CMS) is operating on a server using Windows 2000 (without the Shadow Copy components), these procedures apply.

The Database Maintenance utilities are run from the CPS Utilities command line prompt:

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 current procedures related to database backup and restore, see the following TechNote: http://support.veritas.com/docs/277860.

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 current procedures related to database validation and repair, see the following TechNote: http://support.veritas.com/docs/277860.

Services Manager utility

See “Managing the CPS Services” on page 53.

SetIntegratedLogin utility

It is possible to convert the CMS or CPA servers in an existing CPS installation to use integrated logins. Following is a description of the advantages of integrated logins, their restrictions, and how to enable this mode of operation.

When running in integrated login mode the CMS and CPA servers no longer provide database credentials when connecting to their respective databases since 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 logins 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 logins enabled by running the SetIntegratedLogin utility. This must be done for each server, and one server at a time. If integrated logins is enabled on a combined CMS/CPA server, it is enabled for both services at the same time. Enabling integrated logins requires restarting the affected CPS services.

Once integrated logins have been enabled, it is possible to reset standard logins, 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 logins has been enabled.

The SetIntegratedLogin utility is run from the CPS Utilities command line prompt:

Start > All Programs > Symantec > Backup Exec CPS > CPS Utilities

▼ To reset the standard login:

1. Run SetIntegratedLogin to reset the standard logins,

2. Change the services in question to the run-as account name.

3. Run SetIntegratedLogin to re-enable integrated logins.




157

Note It is necessary to run SetIntegratedLogin only if the services “run as” account name is changed, not the “run as” password.

Issues with integrated login and database backups

Attempts to restore a CMS or CPA database from a backup image created before integrated login was enabled will cause the service in question to fail to start. This is because the just restored image was never configured for integrated logins and the current ODBC Data Source is currently configured for integrated logins.

Thus, after restoring a pre-integrated login database backup image, do the following.

▼ To recover after restoring a pre-integrated login database:

1. Reconfigure the ODBC Data Sources for standard login

a. Run the ODBC Administrator (odbcad32), click on the System DSN tab, select the CPA DSN and then click on the Configure... button. On the ODBC Configuration for Adaptive Server Anywhere... screen, click on the Login tab. Select Supply user ID and password, and then click on OK.

b. Repeat step 1a, but this time for the CMS DSN, if there is one.

c. Close the ODBC Data Source Administrator. The CMS and/or CPS services can now run.

2. Reconfigure the services for integrated login.

3. Run the SetIntegratedLogin utility to re-enable integrated logins. For example, "SetIntegratedLogin Watchword."

The service(s) will now run in integrated login mode.

Restoring a combined CMS/CPA server

Note 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.




▼ To restore a CMS/CPA server:

1. Restore the CMS database from a pre-integrated login backup image. The CMS server does not start.

2. Modify the ODBC CMS DSN to use standard logins, see step 1 of “To recover after restoring a pre-integrated login database:” on page 157. Now the CMS service can start.

3. SetIntegratedLogin (step 2 of “To recover after restoring a pre-integrated login database:” on page 157) determines that the CMS and the CPA differ and returns an error!

Currently the only way to overcome this issue 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, see step 1 of “To recover after restoring a pre-integrated login database:” on page 157. Now the services can start.

6. SetIntegratedLogin (step 2) succeeds and the CMS and the CPA services will now run in integrated login mode.

Related Topics:

“CPS Database Maintenance utilities” on page 155

“Services Manager utility” on page 156


159

Appendix

Maintaining Accessibility

11

Symantec products meet federal accessibility requirements for software as defined in Section 508 of the Rehabilitation Act:

http://www.access-board.gov/508.htm

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.

The following topics detail accessibility features and compliance in CPS:

■ “About general keyboard navigation in CPS” on page 160

■ “About keyboard navigation in dialog boxes” on page 160

■ “Using keyboard shortcuts” on page 161

■ “Establishing accessibility settings” on page 162

About accessibility in CPS

All program functions and menu items are accessible using the keyboard exclusively. CPS uses standard operating system navigation keys and keyboard shortcuts. For its unique functions, CPS 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.

To see a table of the standard Microsoft navigation keys and keyboard shortcuts, select your version of Microsoft Windows from the table at:


160 Administrator’s Guide

http://www.microsoft.com/enable/products/keyboard.aspx

About general keyboard navigation in CPS

You can navigate and use CPS 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 the following keyboard navigation standards:

■ 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 necessary to set options or settings for programs. Here 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.

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


Appendix 11, Maintaining Accessibility 161

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

■ 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 itemis 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 CPS. The following table lists the keyboard shortcuts unique to CPS:

Keyboard Shortcuts Unique to CPS

CPS Accelerator CPS Mnemonic Result

ALT F The File menu expands. From the File menu, you can create new jobs, devices and media, print selected items, view properties, or exit CPS.



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.

Establishing accessibility settings

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.

Note 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.

▼ To set accessibility options:


2. Select Accessibility Options.

ALT E The Edit menu expands. From 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. From 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 CPS, 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 CPS documentation and various Symantec Web sites.

Keyboard Shortcuts Unique to CPS (continued)

CPS Accelerator CPS Mnemonic Result


Appendix 11, Maintaining Accessibility 163

Note You can also set accessibility options through the Accessibility Wizard. From the Windows Start menu point to All Programs, point to Accessories, point to Accessibility, and click Accessibility Wizard.

Note Though all graphics in Symantec documentation are readable- by screen readers, setting your screen reader to ignore graphics improves performance.


165

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. See also “Using the Administration Console” on page 39.

administrator rights

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. See also “CPS credentials and security issues” on page 140.

alerts

Events, such as a completed backup job, that usually require some form of user interaction or acknowledgment. See also “Managing CPS job alerts” on page 109.

Backup Exec Retrieve

Backup Exec Retrieve is 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 newer, and others). CPS software is not required on the user workstations. See also “Using Backup Exec Retrieve” on page 97.

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. See also “Managing backup destinations” on page 54.

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 jobs

Operations that have 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. See also “Backing Up Data” on page 79.

backup schedules

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. See also “About backup job schedules” on page 10.

backup schedule types

Continuous Protection Server uses the following backup schedule types:

On Demand (Manual)The backup job runs only when manually started.

Regularly scheduledThe backup job runs on schedule at a specific time, on specific days.

Periodically scheduledThe backup job runs on certain days at timed, hourly intervals.

ContinuousThe backup job is always running. Files on the source are backed up to the destination whenever the file changes.

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. See also “About backup strategies and planning” on page 9.

Business Server

A local or remote server where end 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.

continuous backups

Backup jobs that run continuously, thereby allowing any changes to be backed up as they occur.


Glossary 167

Continuous Management Service (CMS)

Provides primary control of the Continuous Protection Server processes. The CMS 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 Protection Agent (CPA)

The Continuous Protection Agent is a software collection that must be installed 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 Service

CPS component that allows communications within Continuous Protection 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).

Encrypting File System (EFS)

Microsoft Windows technology that enables users to store information on disk in an encrypted format. The encryption is enabled through the advanced file attributes. CPS skips over files that are encrypted with EFS.

Enterprise Network Layer (ENL)

See “CPS Network Helper Service.”

history file

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.

jobs

Jobs define 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. See also “Backing Up Data” on page 79 and “Restoring Data” on page 91.

job logs

Contain the results of a job and are created when a job runs. You can review job logs to find job errors and details. See also “CPS job report details” on page 107.

periodic backups

Backup jobs that run on timed intervals, such as Monday through Friday, every 12 hours.

permissions

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. See also “CPS credentials and security issues” on page 140.

Protection Server

Protection Servers are the destinations of data that is backed up by CPS from Business Servers.

regular backups

Backup jobs that are run on a regular schedule, such as every Friday at 6:00 P.M.

Remote Agent for Windows Systems (Remote Agent)

CPS uses the Symantec Backup Exec Remote Agent for 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

Jobs define what data is to be restored, from what computers the data will be restore from and back to, when the data will be restored, and other settings. See also “Restoring Data” on page 91.


Glossary 169

retention properties

Length of time you want to save snapshots on the backup destination. You can store snapshots up to a limitthat 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. See also “Defining Retention Policies for snapshots” on page 61.

scheduled backups

Backup jobs that run 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 that are run on specific days at a specific time, every week. Periodically scheduled backup jobs that are 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. See also “CPS credentials and security issues” on page 140.

Shadow

Point-in-time, fixed respresentations, or copies of a specified volume. See also “snapshots.”

Shadow Copy Components

Windows Server 2003 systems include the Shadow Copy Components. Windows 2000 Server systems do not include the Shadow Copy Components. Depending on your OS installation options, the Shadow Copy Components may consist of the event logs, removable storage manager database, and the Windows Management Installation database. Additionally, if the Windows Server 2003 also acts as a SharePoint server, the Shadow Copy Components will include the SharePoint databases. See also “How system information is protected” on page 11.

Shadow Storage

A volume that is specified where snapshots are stored.

SmartLink

Technology that integrates Backup Exec with other Symantec products, such as Continuous Protection Server, Storage Exec, and Replication Exec. SmartLink enables the status of backup jobs that are created in Continuous Protection Server to display in the Backup Exec Administration Console. See also “Monitoring CPS Jobs in Backup Exec” on page 122.



snapshots

Point-in-time, fixed respresentations, or copies of a specified volume. See also “Shadow.” and “Managing snapshots” on page 58.

source computer

Any 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.

storage space

Disk drive space on the servers in the Continuous Protection Server Backup Group. Storage space generally refers to available disk space.

strategic backup plan

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 conventions

Philosophy of naming files and backup destinations in a meaningful way. Rather than naming backup destinations sequentially such as Backup01, Backup02, and Backup03, destination names are based on physical office locations, 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. See also “How system information is protected” on page 11 and “Backing up CPS with Backup Exec” on page 117.

system resources

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.


Glossary 171

System State

Computer system information that varies between Windows 2000 and Windows 2003 operating systems. System State generally contains COM+ database, registry, and system files. See also “system Information.”

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 Component

The Web Restore Server Component is a feature of the CMS that makes available versioned copies (snapshots) of files for user retrieval to their workstations.


173

Index

Numerics64-bit support, 3

Aaccessibility

dialog boxes, 160keyboard shortcuts, 161overview, 159settings, 162

Active Directory, 94Adaptive Server Anywhere, 25, 27adding scripts, 89Administration Console

alerts view, 47assistant view, 43backup job properties, 46credentials, 141defined, 5, 165general features, 40information desk view, 43job monitor view, 47menu bar, 40minimum requirements, 21navigation bar, 40overview view, 43preview pane, 41restore view, 47selection pane, 40server properties, 44setup view, 43setup view properties, 44starting, 39status bar, 41system summary view, 43task pane, 40views, general, 42

Administration Service, 26administrator rights, defined, 165AlertGroomFrequency parameter, 66alerts, 109

defined, 165deleting, 112deleting from history, 112fatal, 125messages, 124properties, 124

responding to, 112SmartLink, pairs, 127viewing and filtering active, 110viewing and filtering history, 110viewing properties, 111

alerts view, 47AlwaysDoRegionAnalysis parameter, 66ASA directory, 25assistant view, 43autonomy directory, 25

Bbacking up

changing schedules, 87continuously, 80overview, 49, 79storing snapshots, 61

backup destinationsadding, 54, 55credentials, 141defined, 165deleting, 57description, 54managing, 54permissions, 54properties, 46

Backup Execalerts, 124Desktop and Laptop option, 4job logs, accessing, 128job selection for backup, 123media server credentials, 123protecting a Protection Server, 118protecting Business Servers, 119protecting Continuous Management

Service, 118protecting CPS, 116protecting CPS databases, 117protecting snapshots, 119restoring a Business Server, 121restoring a Protection Server, 121restoring Continuous Management

Service, 121restoring CPS, 120Retrieve

security and credentials, 98



specifying a media server, 122Backup Exec Environment Check, 16Backup Exec Retrieve

browse, 98description, 5, 6, 97download list, 98features, 97minimum requirements, 22recent activity, 98retrieving files, 99search, 98URL, 99

backup groupdefined, 4, 165moving servers between, 51

backup jobsadding scripts, 89alert history, 110alert properties, 111alerts posted to Backup Exec, 124changing schedules, 87creating, 79creating continuous, 80credentials, 141defined, 165, 166filtering alerts, 110filters, 83including and excluding

information, 83managing alerts, 109managing statuses, 103manual operation, 90pairs, 103properties, 46schedules, 10states, 104storing snapshots, 61viewing the status, 103

backup processencrypted files, 23reparse points, 23

backup schedulescontinuous, description, 11defined, 166periodic, description, 11scheduled, description, 11

backup strategiesconsiderations, 9defined, 166

periodic backups, 11regular backups, 11

bandwidth limiting, 88batch files, 124besernum.xml file, importing license keys

with, 29BroadcastAddress parameter, 67BroadcastHops parameter, 67Broker Services, services, 26Business Servers

configuring, 49defined, 170description, 4, 166installing, 32managing, 49minimum requirements, 19uninstalling, 36

CCentral Admin Server environments, 123command line syntax, errors, 131complete installation, 27configuration troubleshooting, 145Configuration Writer, services, 26configuring

Business Servers, 49Continuous Protection Server, 115registry entries, 65snapshots, 58

ConnectionPooling parameter, 67continuous backups

defined, 166description, 11plans, 11

Continuous Management Servicedefined, 5, 167system requirements, 20uninstalling, 35

Continuous Protection Serverconfiguring, 49credentials, 140, 141database backup and restore, 148databases, 117documentation, 13drivers, 25features and benefits, 2firewall support, 23installation modification, 35installation upgrade, 34


Index 175

installing, 15integrating with Backup Exec, 115introduction, 1invalid jobs, 132job report, 107jobs topic box, 108, 133key components, 4monitoring jobs, 103service account, 31, 140Services, 26Services Manager, 53starting, 39tools and utilities, 155tunable parameters, 66use model, 6

creatingcontinuous backup jobs, 80snapshots, 59

credentials, 140Administration Console, 141backup destinations, 141Backup Exec DLO, 152Backup Exec media server, 123CPS service account, 140creating backup jobs, 141installing CPS, 141Internet Explorer security, 98push installing CPS, 141SmartLink, 142

Ddata protection, 9database backup and restore, 155database directory, 25database maintenance utilities, 155database services, 26database validation and repair, 155DaysToKeepAlertItems parameter, 67DaysToKeepDeletedSnapshots

parameter, 67DelayDirChangeNotifications

parameter, 68deleting

alerts from history, 112backup destinations, 57snapshots, 63

Desktop and Laptop option, 4, 101destinations

defined, 167

installing, 27uninstalling, 35

Directory Services Restore Mode, 94disk space, requirements, 151DoEventLog parameter, 68domain security mode, 53domain trust, 140drivers directory, 25

EEnableDebugConsole parameter, 68EnableLogFile parameter, 68EnableTimestamp parameter, 68encrypted files, 23Encrypting File System, defined, 23, 167Enterprise Network Layer (ENL), 167Environment Check, running for Backup

Exec, 16errors, command line syntax, 131Evaluation version, installing CPS, 29exceptions topic box, 131Exchange protection, 4excluding information, 83

Ffeatures and benefits, 2FFXPort parameter, 69files and directories, restoring, 92FilteredIDList parameter, 69filters

deleting, 86description, 83include and exclude, 84modifying, 85

firewall support, 23free disk space, 151

GGateway (ENLSystem) parameter, 69Gateway (Network.TCPIP) parameter, 69Gateway (Network.UDPv6) parameter, 69getting started, 39

Hhardware requirements, 20Help, online, 14Hierarchical Storage Management, 23history file, defined, 167history, alerts, 110



Iincluding information, 83indexing component

description, 5minimum requirements, 22

Indexing directory, 31Indexing Root parameter, 70indexing services, 26indexing state, snapshots, 63information desk view, 43infrastructure, defined, 168install directory, 25installation

complete, 27general procedure, 16modifying, 35prepare to, 15push install, 32upgrading, 34

installingbesernum.xml file, import license

keys, 29Environment Check, running

pre-install, 16Evaluation version, 29import license keys, 29

installing CPS, 27Internet Explorer, security, 98

Jjob details topic box, 133job ID, not found, 132job logs

defined, 168job header, 133SmartLink, 129topic box, 134viewing, 128

job monitor view, 47job name, not found, 132job pairs

alerts, 127description, 103exceptions, 131

job report, 107job state, unknown, 132job states, 104job status, 106jobs

defined, 168monitoring, 103troubleshooting, 151

Journal directory, 31JournalRoot parameter, 70

Kkey components

Backup Exec Retrieve, 6CPS overview, 4

Llatency, target, 108, 134license keys

Backup Exec, adding and removing, 29See also names of individual agents and

optionslimiting bandwidth, 88LiveUpdate, 3local system object cache, 33log entries

limiting, 123parameter, 134

LogOpenFileTableOncePerSet parameter, 70

LogPath (EFC) parameter, 70LogPath parameter, 70Logs directory, 25LogText parameter, 71

Mmanaging

backup destinations, 54backup job status, 103Business Servers, 49snapshots, 58source properties, 49

Master (ENLSystem) parameter, 71MaxDirSize parameter, 71MaxLogSize (ENL) parameter, 71MaxLogSize parameter, 71MaxPacketSize (Network.TCPIP)

parameter, 72MaxPacketSize (Network.UDPv6)

parameter, 72MaxRAPerCentChange parameter, 72menu bar, 40MinRASizeInKb parameter, 72modifying filters, 85monitoring jobs, 103


Index 177

monitoring processes, 103MsBetweenRallyChecks parameter, 72

NNamedObjectsRoot parameter, 73navigation bar, 40NetBios, 24Network (ENLSystem) parameter, 73Network Helper services, 23, 24, 26network load balancing service, 28, 139network shares, restoring, 95NeverDoRegionAnalysis parameter, 73NumberOfLogs parameter, 73

OOutboundJournalCleanupSize

parameter, 73OutboundJournalNominalSize

parameter, 74OutboundSyncJournalLimit parameter, 74overview view, 43

Ppair header topic box, 134pair log topic box, 134pair status, 106pairs, job, 103parameters, tunable, 65, 66

AlertGroomFrequency, 66AlwaysDoRegionAnalysis, 66BroadcastAddress, 67BroadcastHops, 67changing values, 76ConnectionPooling, 67DaysToKeepAlertItems, 67DaysToKeepDeletedSnapshots, 67DelayDirChangeNotifications, 68DoEventLog, 68EnableDebugConsole, 68EnableLogFile, 68EnableTimestamp, 68FFXPort, 69FilteredIDList, 69Gateway (ENLSystem), 69Gateway (Network.TCPIP), 69Gateway (Network.UDPv6), 69IndexingRoot, 70JournalRoot, 70LogOpenFileTableOncePerSet, 70LogPath, 70

LogPath (EFC), 70LogText, 71Master (ENLSystem), 71MaxDirSize, 71MaxLogSize, 71MaxLogSize (ENL), 71MaxPacketSize (Network.TCPIP), 72MaxPacketSize (Network.UDPv6), 72MaxRAPerCentChange, 72MinRASizeInKb, 72MsBetweenRallyChecks, 72NamedObjectsRoot, 73Network (ENLSystem), 73NeverDoRegionAnalysis, 73NumberOfLogs, 73OutboundJournalCleanupSize, 73OutboundJournalNominalSize, 74OutboundSyncJournalLimit, 74PreferredAddress (Network.TCPIP), 74PreferredAddress (Network.UDPv6), 74PreferredNIC (Network.UDPv6), 75PreferredNIC(Network.TCPIP), 74ReservedFreeDiskSpace, 75RxRmsStaticPort, 75RxRsaStaticPort, 75Schedule, 75SerializeIrpLogging, 75ShareInfoAsSingleComponent, 76Socket, 76UsePrivateFindFileMethod, 76Verbose (ENL), 76VolumeLevel, 76

periodic backupdefined, 168description, 11

permissionsbackup destinations, 54defined, 168media server, 123

planning, backup, 9port settings

Services Manager, 24Settings Utility, 24

pre/post commandsadding, 89runtime settings, 124

PreferredAddress (Network.TCPIP) parameter, 74

PreferredAddress (Network.UDPv6)



parameter, 74PreferredNIC (Network.TCPIP)

parameter, 74PreferredNIC (Network.UDPv6)

parameter, 75preview pane, 41properties

alerts, 111backup destination, 46backup jobs, 46server, 44, 49

Protection Agentdefined, 5, 167service, 26

Protection Serverdescription, 4, 168minimum requirements, 20uninstalling, 35

push installation, 32

Rregistry entries, 65regular backups, defined, 168Remote Agent for Windows Systems, 6renaming backup folders, 54reparse points, 23report, job, 107requirements

disk space, 151hardware, 20

ReservedFreeDiskSpaceparameter, 75responding to alerts, 112restore jobs, defined, 168restore view, 47restoring

as the administrator, 92from the desktop, 99network shares, 95overview, 91, 97

retention policies, snapshots, 58, 61retention properties, defined, 169run log topic box, 132RunLog parameter, 132RxRmsStaticPort parameter, 75RxRsaStaticPort parameter, 75

SSchedule parameter, 75scheduled backups

defined, 169

description, 11schedules

changing, 87changing for snapshots, 60continuous backups, 80snapshots, 59

scripts, 89security, 140security modes

domain, 53workgroup, 54

security, Internet Explorer, 98selection pane, 40SerializeIrpLogging parameter, 75server properties, 44servers, managing properties, 49servers, moving between backup groups, 51service account, 140Services

Administration Service, 26Broker Services, 26Configuration Writer, 26database, 26indexing, 26Network Helper, 26Protection Agent, 26System State Manager, 26Web restore backend, 26Web restore frontend, 27Web server, 27

services manager, 53Services Manager utility, 156setintegratedlogin utility, 156Settings Utility, 3, 65setup view, 43setup view properties, 44Shadow Copy Components, 12, 169Shadow Storage, changing location, 55ShareInfoAsSingleComponent

parameter, 76Single Instance Storage, 23SmartLink

alerts, categories, 125credentials, 142defined, 169description, 122fatal alerts, 125job log descriptions, 129job logs, summary messages, 130


Index 179

job topic box, 129options topic box, 132topic boxes

command line syntax errors, 131CPS jobs, 133exceptions, 131job details, 133job log, 134options, 132pair header, 134run log, 132

snapshotschanging schedules, 60creating on demand, 59deleting, 63indexing state, 63managing, 58reasons for deleting, 62reindexing, 145retention, 61retention policies, 58scheduling, 59storing, 61viewing history, 62

Socket parameter, 76status bar, 41status, job and pair, 106storage space, 170strategic backup plan, 170strategic naming conventions, defined, 170strategies, backup, 9Symantec

knowledge base, 14LiveUpdate, 3Technical Support, 13

System Cache directory, 31System Information, 11, 93system requirements

disk space, 151hardware, 20minimum, 18

system resources, 170System State, 11

backup schedule, 93backup, defined, 171Manager, 26restore to an Active Directory, 94restoring, 93

system summary view, 43

Ttarget latency, 108, 134task pane, 40Technical Support, 13troubleshooting, 135troubleshooting issues

Administration Console, 143anti-spyware software, 138Apache Tomcat Web Server, 138Backup Exec Retrieve, 152browsers supported, 138business servers, 144configuration, 145connection outages, 149Continuous Management Service, 143CPS and Backup Exec, 137CPS backup jobs, 149CPS compatibility, 136CPS components, 143CPS configurations, 145CPS restore jobs, 150CPS tools and utilities, 155credentials and security, 140database backup and restore, 148, 155database maintenance, 155database validationa nd repair, 155disk space for indexing, 145file system filter drivers, 137installation, 138job monitoring, 151network load balance, 139NIC failure, 138pathnames with Asian characters, 139processing efficiency, 147protection servers, 144push installing over domain trust, 138services account, 140Services Manager utility, 156setintegratedlogin utility, 156snapshot schedules, 146SNMP support, 148system state backup and restore, 150,

151uninstalling CPS, 139utility partitions, 148workgroups and domains, 138

Uuninstalling



Business Server, 36Continuous Management Service, 35destinations, 35Protection Server, 35sources, 36

use model, 6UsePrivateFindFileMethod parameter, 76user rights, 140

VVerbose (ENL) parameter, 76Veritas

Replication Exec, 16Storage Replicator, 16

viewing

and filtering active alerts, 110job statuses, 103snapshot history, 62

VolumeLevel parameter, 76

WWeb restore

backend services, 26frontend services, 27server component, 5, 21

Web server service, 27Windows File Sharing, 24workgroup

environment, 140security mode, 53


continuous protection server

Documents

uninterruptible

battery backup

network load

continuous

continuous

alternative

fully qualified

enterprise