Connecteddata Center Deployment 82

Connected Backup
Data Center Deployment

Version 8.2
Document information
Connected Backup Data Center Deployment
Connected Backup Version 8.2
Printed: May 7, 2007
Printed in USA
Iron Mountain Support Information

800.675.5971
U.S. +1 508 808 7629
E.U. +49 6102 8828855
corporatesupport@ironmountain.com
Copyright
Copyright 2007 Iron Mountain Incorporated. All rights reserved.
Trademarks
Iron Mountain, the design of the mountain, Iron Mountain, the design of the mountain, Connected, Connected DataProtector,
Connected EmailOptimizer, DataBundler, MyRoam, Delta Block, and SendOnce are trademarks or registered trademarks of Iron
Mountain Incorporated. All other trademarks and registered trademarks are the property of their respective owners. All other
trademarks and registered trademarks are the property of their respective owners.
Confidentiality
CONFIDENTIAL AND PROPRIETARY INFORMATION OF IRON MOUNTAIN. The information set forth herein represents
the confidential and proprietary information of Iron Mountain. Such information shall only be used for the express purpose authorized
by Iron Mountain and shall not be published, communicated, disclosed or divulged to any person, firm, corporation or legal entity,
directly or indirectly, or to any third person without the prior written consent of Iron Mountain.
Disclaimer
While Iron Mountain has made every effort to ensure the accuracy and completeness of this document, it assumes no responsibility
for the consequences to users of any errors that may be contained herein. The information in this document is subject to change without
notice and should not be considered a commitment by Iron Mountain Incorporated. Some software products marketed by Iron
Mountain Incorporated and its distributors contain proprietary software components of other software vendors.
Iron Mountain Incorporated

745 Atlantic Avenue
Boston, MA 02111
1-800-899-IRON
www.ironmountain.com
TABLE
OF
C ONTENTS
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Graphical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Iron Mountain Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Part I: About the Data Center
Chapter 1: Data Center Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
BackupServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
IndexServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
ReplicationServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
PoolServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
HSMServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Compactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
DCAlerter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Chapter 2: Hierarchical Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
About HSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Migration and purge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Tape Groups and Tape Account Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Tape Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Multiple tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Permanent expansion library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Chapter 3: Compactor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Compactor and Data Center configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
How Compactor operates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
File expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Part II: Data Center Installation
Chapter 4: Sizing Your Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Sizing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Sizing estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Network bandwidth requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Table of Contents
Chapter 5: Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Evaluating configuration and license options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Data Center server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Storage solutions requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Security requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Installing and configuring Microsoft software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Support Center and Account Management Website preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Enabling the MyRoam feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Chapter 6: Installing the Data Center Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Installing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Verifying successful installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
Troubleshooting Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Installing Support Center and Account Management Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Chapter 7: Integrating the Data Center with Enterprise Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83
Enterprise directory overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
Integration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Preparing for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Configuring your firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Enabling Support Center access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Map data fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Verifying successful enterprise directory integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Part III: Management
Chapter 8: Managing the Data Center with DCMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
DCMC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
DCMC user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Chapter 9: Installing Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Tools overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Installing the DataBundler Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Installing the Data Center Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Chapter 10: Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Event Log Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Trace Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Part IV: Maintenance
Chapter 11: Introduction to Data Center Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Maintenance task overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Chapter 12: Daily Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
General morning tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Table of Contents
General tasks for the morning and afternoon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Tasks for Data Centers using tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Chapter 13: Weekly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Verify results of the Weekly Automatic Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Backup tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Check for available disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
General tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Tasks for Data Centers using tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Chapter 14: Monthly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Account management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Evaluate current Data Center capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
Verify firmware is current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Check software licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
The Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Clean library and tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Record Keeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Part V: Appendices
Appendix A: Data Center Specification Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Data Center server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160
Appendix B: Data Center Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Installation worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162
Appendix C: Maintenance Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Performing daily maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Performing Weekly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Performing Monthly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
PREFACE
About this manual
The Connected Backup solution is a proven solution that automatically protects and restores user or server data files,
operating systems, and applications using a single central Data Center while reducing Information Technology costs and
email storage demands.
This manual is written for system administrators and Data Center technicians. Readers of this manual should be familiar with
the Windows operating system and the operations of their Data Centers.
This manual is organized into the following sections:
Section
Description
Chapter 1: Data Center Services
Describes the services that run on the Data Center server.
Chapter 2: Hierarchical Storage Manager
Provides details about Hierarchical Storage Manager operations

in the Data Center.
Chapter 3: Compactor
Provides details about Compactor operations in the Data Center.
Chapter 4: Sizing Your Data Center
Provides hardware and software recommendations for your Data

Center.
Chapter 5: Preparing for Installation
Describes the tasks you should complete before installing the

Data Center server software.
Chapter 6: Installing the Data Center Software
Contains procedures that describe how to install and configure the

Data Center server software.
Chapter 7: Integrating the Data Center with Enterprise Describes how to use an Enterprise Directory with the Data
Directory
Center.
Chapter 8: Managing the Data Center with DCMC
Provides an overview of the Data Center Management Console

application.
Chapter 9: Installing Management Tools
Contains procedures that describe how to install the Data Center

management tools.
Chapter 10: Event Logging
Provides an overview of the event logging that the Data Center

uses.
Chapter 11: Introduction to Data Center Maintenance Introduces the daily, weekly, and monthly maintenance tasks for
the Connected Backup application.
Section
Description
Chapter 12: Daily Maintenance
Contains procedures that describe how to perform the daily

maintenance tasks.
Chapter 13: Weekly Maintenance
Contains procedures that describe how to perform the weekly

maintenance tasks.
Chapter 14: Monthly Maintenance
Contains procedures that describe how to perform the monthly

maintenance tasks.
Appendix A: Data Center Specification Worksheet
Contains a worksheet where you can record important

information about your Data Center configuration.
Appendix B: Data Center Installation Worksheets
Contains a worksheet that you can use to record information that

you need when installing the Data Center software.
Appendix C: Maintenance Checklists
Contains worksheets that you can use to track the maintenance

procedures.
Related documentation
Related manuals
The following manuals provide additional information about the Connected Backup product:
Manual
Description
Connected Backup/PC Product Overview
This manual provides an overview of the features in the

Connected Backup product.
Connected Backup Upgrading from Pre-8.0 Versions This manual describes how to upgrade a legacy Data Center and
Agent to version 8.2. The manual also describes new and changed
features in version 8.2.
Connected Backup Agent Deployment
This manual describes how to download, install, and configure

Agents.
Connected Backup/PC Agent Quick Start
This short document provides users with a quick reference for

backup and file retrieval procedures.
Connected Backup/PC Account Management Website

Development
This manual describes how to customize the Account

Management Website.
Other Resources
The following resources provide additional information about the Connected Backup family of products:
Online help All applications provide procedural and conceptual information in an online help system. Click the Help
link, Help button, or ? button to open the online Help.
The Resource Center The Resource Center is a knowledge base of information that all Connected Backup customers
can access. It includes procedures and information not contained in the product manuals or online help systems. The
Resource Center is located at https://resourcecenter.connected.com/
Conventions
Typographical conventions
This manual uses the following typographical conventions:
Convention
Description
Bold text
Indicates one of the following:
Italic text
Monospaced text
Monospaced bold text
A control in an applications user interface
A registry key
Important information
The title of a manual or publication
New terminology
A variable for which you supply a value
file name
folder name
code examples
system messages
Indicates system commands that you enter.
Graphical conventions
This manual uses the following graphical conventions:
Convention
Description
Indicates additional information that may be of interest to the
reader.
Indicates cautions that, if ignored, can result in damage to
software or hardware.
10
Contact Information
Technical support
Use the following to contact technical support:
Email: corporatesupport@ironmountain.com
Telephone: 800.675.5971
U.S. +1 508.808.7629
E.U. +49 6102 8828855
Iron Mountain Website

Access the Iron Mountain Incorporated Website at the following URL:
www.ironmountain.com
11
PART I: ABOUT THE DATA CENTER
Chapter 1: Data Center Services

Chapter 2: Hierarchical Storage Manager
Chapter 3:Compactor
1
DATA CENTER SERVICES
About this chapter
This chapter describes the types of services the Data Center uses in the following topics:
To learn about...
Refer to:
The services that the Data Center uses
Services overview, on page 16
What BackupServer does
BackupServer, on page 17
What IndexServer does
IndexServer, on page 18
What ReplicationServer does
ReplicationServer, on page 19
What PoolServer does
PoolServer, on page 20
What HSMServer does
HSMServer, on page 21
What Compactor does
Compactor, on page 22
What DCAlerter does
DCAlerter, on page 23
15
Chapter 1/Data Center Services
Services overview
Services overview
Types of services
The Data Center uses the following services to perform the necessary tasks of running the Data Center server:
16
BackupServer used for data backup and retrieval.
IndexServer used to index file and archive set information to databases.
ReplicationServer used for replication between servers in a mirrored pair configuration.
PoolServer used to maintain the shared pool that the SendOnce technology uses.
HSMServer used to copy archive sets to archive storage devices and purge migrated sets from disk when needed.
Compactor used to remove old data from the Data Center.
DCAlerter used for Data Center event notification.
BackupServer
BackupServer
How BackupServer works
BackupServer is the Data Center service that processes requests from the Agent for data backup and retrieval. BackupServer
gathers together all of the backed-up data into an archive set. The archive set is a file stored on the Data Center servers disk
in a folder called Customers. It contains file backup data transmitted from a client during a single backup session.
If the backup data from a single backup session is large, the BackupServer service saves information to more than one archive
set, each representing a portion of the backup session. Using multiple archive sets helps to optimize data recovery
performance.
When the Agent requests BackupServer to retrieve a file to a client, BackupServer must find the first backup of the file (called
the baseline) and all of that files changes (called deltas) necessary to recreate the specific version of the file that the user has
requested.
For example, if the user has requested to retrieve the third backed-up version of a file, BackupServer must retrieve the
baseline (version 1), the delta that represents the differences between version 1 and version 2, and the delta that represents
the differences between version 2 and version 3. Since the baseline and the deltas were backed up in different backup
sessions, they are in different archive sets. Therefore, BackupServer typically uses multiple archive sets to retrieve a file.
In addition to processing requests for data backup and retrieval, the BackupServer service manages the list of authorized user
accounts and registers new accounts. There is one user account for each client that is being backed up.
CAUTION
The Data Center servers store backed-up archive sets in a folder called Customers. The Data
Center server saves archive sets as files with the extension .arc.
Under no circumstances should you ever delete an .arc file from the Customers directory.
Doing so would mean deleting end users data and rendering it unrecoverable.
Management
BackupServer starts automatically with Windows Server. Status and statistics for BackupServer are found in the Data Center
Management Console (DCMC). To view the service in the DCMC, expand the Data Center server name and click
BackupServer.
17
IndexServer
IndexServer
IndexServer is the Data Center service that indexes file and archive set information to database tables.
How IndexServer works

As users or servers back up archive sets to the Data Center server, information about each file within the archive set must be
stored in the Directory database. The IndexServer writes this information to the Directory database once the archive set is
fully written to the Data Center server from the Agent. When the indexing process is finished, the archive set is queued for
replication to the mirrored server, if a mirrored configuration is used.
If the Data Center is mirrored or clustered, the IndexServer writes information to the database for all archive sets that have
been replicated from the mirrored server.
Management
IndexServer starts automatically with Windows Server. Status and statistics for IndexServer are found in DCMC. To view
the service in the DCMC, expand the Data Center server name and click IndexServer.
18
ReplicationServer
ReplicationServer
How ReplicationServer works
The ReplicationServer service replicates the following content between the servers in a mirrored pair:
Archive sets
Database table rows
Agent configurations
The ReplicationServer service only runs on mirrored and clustered configurations.

After an archive set is backed up by the Agent to the Data Center server and indexed to the database, it is put into a queue to
be replicated to the mirror. The archive set is replicated as a whole to the mirror rather than bit by bit as it is backed up by
the Agent.
Most, but not all, of the database table rows in the schema are replicated between the servers in a mirrored pair. When a row
is either inserted, deleted, or modified, it is queued for replication between the mirrored servers.
When you use Support Center to create files to be downloaded to Agents, the files created must be replicated between the
mirrored servers. ReplicationServer queues both the Agent configuration files and the corresponding database table rows for
replication to the mirror. In order for file downloads to Agents to be successful, the files and database rows must be on both
servers because Agents can connect to either Data Center server. The server they connect to first is dependent on which server
they are configured to contact first. Therefore, it is necessary for Agent configuration files to be available on all servers in
the Data Center.
Management
ReplicationServer starts automatically with Windows Server. Archive sets and database entries are replicated continuously
when ReplicationServer is running. If it becomes necessary to pause or stop replication, you can pause or stop the service in
the DCMC. You can view the status and progress of the replication service in the DCMC by expanding the Data Center server
name and clicking ReplicationServer.
19
PoolServer
PoolServer
PoolServer is the Data Center service that maintains the shared file pool used to implement SendOnce technology. The
SendOnce technology provides a method for identical files from multiple Agents to be backed up once. This method
reduces the storage needed on the Data Center server since multiple copies of the same file are not stored on the server.
How PoolServer works

Application, operating system, and common organizational files take the greatest advantage of this feature. The PoolServer
service performs a process called Copy On Reference and cleans the pool of uncommon files.
The Copy On Reference process makes copies of files that have been backed up by more than one Agent. When an identical
file is backed up by two Agents, the SendOnce technology places it in a queue for Copy On Reference. Copy On Reference
makes a copy of the file and places it in a special account known as the Pool Account. The Pool Account always uses
999999999 as its account number. Any Agent that backs up the same file references the copy instead of sending another full
copy of the file to the server. Also, if any Agent needs to retrieve the file after backing it up, the Agent retrieves the copy
from the Pool Account.
PoolServer cleans the pool of uncommon files every fourteen days. An uncommon file is a file that no other account has
backed up within fourteen days. These files are removed to keep the Directory database from growing too large and to keep
the performance of the SendOnce operation as efficient as possible. You can use DCMC to change the number of days that
uncommon files remain in the pool.
Management
PoolServer starts automatically with Windows Server. Use the DCMC to view the status and statistics of the PoolServer. In
the DCMC, expand the Data Center server name and click PoolServer.
20
HSMServer
HSMServer
How HSMServer works
HSMServer is the Data Center service that processes the copying of archive sets between the local servers disk and the
archive storage device. The HSMServer contains the following components:
HSMClient
BackupHSM
HSMPurge
HSMClient is invoked by BackupServer to pass archive set copy requests to the BackupHSM service. The HSMClient
monitors the processing of the requests and mediates between BackupServer (the Windows service) and BackupHSM.
BackupHSM handles the operations for archive storage devices. HSMServer supports tape libraries and EMC Centera
archive storage devices.
It is not recommended that you pause the BackupHSM service. When BackupHSM is paused you cannot cancel requests or
view the status in DCMC. You can unmount a tape manually from a tape library while BackupHSM is paused.
The library audits its contents and then BackupHSM audits the library. If it is necessary to stop HSM activities, stopping
BackupHSM alerts the service to complete the current request and then stop.
It is the job of HSMPurge to migrate (copy) archive sets from disk to the archive storage device and, when necessary, purge
(delete) archive sets from disk in order to create free disk space.
When the end user wants to retrieve files, BackupServer sends a request to HSMClient to retrieve the appropriate archive
sets. BackupHSM copies the archive sets from the archive storage device back onto the servers disk where BackupServer
can process them.
Additional information
Refer to Chapter 2: Hierarchical Storage Manager, beginning on page 25, for more information about HSM.
21
Compactor
Compactor
The Compactor service works to clean old data off the Data Center. Compactor checks for synchronization between mirrored
servers, applies expiration rules to backed up data, and deletes data that is deemed expired. The goal of Compactor is to speed
up the Retrieve process and to reduce the amount of data stored long term on the Data Center.
Additional information
Refer to Chapter 3: Compactor, beginning on page 35, for additional details about the Compactor process.
22
DCAlerter
DCAlerter
DCAlerter notifies designated individuals when specific events occur on the Data Center. DCAlerter monitors the Data
Center event logs for specific event IDs configured for notification. When an event ID is logged that has been configured for
notification, DCAlerter sends an email message to the designated individuals.
Refer to Chapter 10: Event Logging, beginning on page 111 for additional information about Data Center event logs.
Configuring email for DCAlerter

You can specify your SMTP mail host and an administrator email address for DCAlerter during Data Center Setup. If the
SMTP mail host information is not entered during Data Center Setup, the feature is not activated. Data Center Setup installs
a default set of events for notifications. You can modify the installed settings using DCMC.
Refer to DCMC Help for a procedure to modify the installed settings.
23
2
HIERARCHICAL STORAGE MANAGER
About this chapter
This chapter contains the following topics:
To learn about...
Refer to:
How migration and purge works
Migration and purge, on page 27
Tape Groups and Tape Account Groups
Tape Groups and Tape Account Groups, on page 28
Tape sets
Tape Sets, on page 29
Multiple tape libraries
Multiple tape libraries, on page 32
Permanent expansion libraries
Permanent expansion library, on page 33
25
Chapter 2/Hierarchical Storage Manager
About HSM
About HSM
Description
Over time, the Agents on many computers perform many backups and the number of archive sets on the Data Center servers
disk grows. When free space on the disk drops below a preconfigured threshold, BackupServer requests Hierarchical Storage
Manager (HSM) to migrate archive sets from disk to the archive storage device, if one is installed. If no archive storage
device is installed, archive sets are kept only on the Data Center servers disks.
The Compactor service, discussed in Chapter 3: Compactor, beginning on page 35, removes old data and recycles disk space
as needed.
Archive storage devices

The Connected Backup application supports the following types of archive storage devices:
Tape libraries (SCSI and DAS).
EMC Centera.
Visit the Resource Center for an updated list of hardware solutions that are currently supported.
26
Migration and purge
Migration and purge

Migration
If your Data Center is configured with HSM, the HSMPurge service migrates archive sets from disk to an archive storage
device when free disk space is reduced to a preset threshold. Upon reaching another free disk space threshold, the migrated
archive sets are purged from disk, freeing disk space for newer backups. If your Data Center is configured to use multiple
disk volumes, the migration and purge processes begin or end when thresholds are reached across all volumes. You can see
the process graphically through the Data Center Management Console (DCMC).
If the Data Center contains unmigrated archive sets and the free space drops below a specified percentage of disk space,
HSMPurge begins migrating the archive sets, while keeping the original archive sets on disk.
Purge
As archive sets are continually backed up to the server and occupy more disk space, free disk space continues to drop. When
free disk space drops to a second specified percentage, HSMPurge starts purging migrated archive sets from disk. The
purging continues until free disk space grows to a third specified percentage. You can specify the disk space percentages for
the migration and purge processes in the DCMC.
Archive sets are not immediately purged from disk after migration to the archive storage device. The reason for this is to keep
as many archive sets as possible available on disk for possible file retrieval requests.
27

Tape Groups provide a method of keeping data from different communities on separate tapes. A community is the basic
organizational unit for accounts on the Data Center server. You might find Tape Groups useful if you have a community
whose data you want to keep on separate tapes in the tape library.
Tape Group 0
Tape Group 0 (zero) is the default Tape Group created by Data Center Setup. The default community is assigned to Tape
Group 0. Unless specified in Support Center, all new communities are also assigned to Tape Group 0.
Tape Account Groups

Tape Account Groups provide a way for HSM to group accounts together for assignment to tape. Tape Account Groups are
groupings of accounts within a Tape Group. The purpose of Tape Account Groups is to fully utilize tape space. Tape Account
Groups have a predetermined maximum number of accounts and quantity of data that are assigned. HSM creates a new Tape
Account Group when the current Tape Account Groups limits are reached.
28
Tape Sets
Tape Sets
Overview
Whether you are running a standalone or a mirrored Data Center configuration, there is a risk of losing backed-up data due
to various failures, such as:
Disk failure on a standalone Data Center or on one of the servers of a mirrored pair.
Loss of tape cartridge.
Total system loss due to fire or similar disaster.
The amount of risk decreases in a mirrored server environment, where all backed-up data is stored redundantly on two
identical Data Centers, so that if one Data Center of a mirrored pair experiences technical problems, data is still available on
its mirror.
Unlike a mirrored pair, a standalone Data Center only stores a single copy of data on disk or archive storage device (if
applicable). In the event of hardware or software malfunction, service outage, a fire, or similar disaster, backed-up data, both
on disk and on the archive storage device, will be completely lost if no extra protective measures have been taken. To take
such protective measures, you can configure your Data Center to use one or more additional tape sets (refer to Chapter 6:
Installing the Data Center Software, beginning on page 73 for installation information). During the migration process, HSM
copies data from disk to tapes that belong to the tape sets. These tape sets are referred to as the Primary and Secondary Tape
Sets.
The Primary and Secondary Tape Sets serve different functions within the Data Center. Therefore, the methods by which you
create them differ as well.
Use DCMC to configure your Data Center to use Tape Sets. Refer to the DCMC Help for configuration procedures
Primary Tape Set

There is only one Primary Tape Set in the tape library. Tapes that belong to the Primary Tape Set remain permanently in the
library to ensure prompt recovery of archive sets at the end users request. The main purpose of the Primary Tape Set is to
optimize the recovery process for end users if they must retrieve some or all of their data. To maximize the speed and
efficiency of file retrieval, data for each individual account is kept together in a Tape Account Group (refer to Tape Groups
and Tape Account Groups, on page 28 for more information).
To enable maximum amounts of data to accumulate on disk before each migration, data is migrated to tape infrequently.
When the Data Center disk space usage parameters have been reached, HSMPurge migrates data to the Primary Tape Set
with the goal of consolidating data for each account. For an account to be assigned to a particular tape, the amount of data
that is already on that tape must be under a specific threshold. Imposing a data threshold provides space for future migrations
for accounts that have already been assigned to the tape. Therefore, when an end user initiates a retrieve, the requested data
is quickly located on the tape to which an account is assigned and copied back to disk. Data is migrated from the Data Center
disk to the Primary Tape Set as needed, based on DCMC settings. If the archive disk is properly sized, migration should occur
once a week.
29
Tape Sets
Secondary Tape Sets

The Data Center software offers a feature that provides redundant protection of backed up data in both a standalone server
and mirrored environment. This includes creating additional copies of archive sets, referred to as Secondary Tape Sets, and
taking them off-site as needed.
The purpose of Secondary Tape Sets is to create and maintain a valid copy of all backed-up data in restorable form so that,
if a major data loss occurs at the Data Center, archive sets are still recoverable using disaster recovery tools and procedures.
Therefore, instead of consolidating data for each account on a particular tape, HSM migrates archive sets to the Secondary
Tape Set tapes as quickly as possible. This feature is available to HSM configurations only.
You can use secondary tape sets without a primary tape set. In this situation, the Data Center functions primarily as a diskonly configuration. A scheduled job runs to request the HSM to create the Secondary Tape Sets. For this type of
configuration, the tape library needs enough slots to hold blank tapes to accommodate one or two days worth of archives
only.
Types of Secondary Tape Sets

There are two kinds of Secondary Tape Sets:
The SendOnce account tape set stores a backup of the SendOnce account (you can create only one copy of a SendOnce
account tape set). This tape set usually remains on-site and is especially helpful in a standalone Data Center
configuration, enabling fast recovery of backed up data, lost due to a bad tape or a disk failure. When the SendOnce
account tape set tape becomes full, you can remove it from the library and store it on the shelf at the same location.
Off-site Secondary Tape Sets contain a complete copy of archive sets (with the exception of the SendOnce account) and
are intended for off-site storage. Depending on your organizations needs, you can configure the system to create one or
more off-site Secondary Tape Sets. For maximum data protection, tapes in these tape sets are filled and removed from
the library as often as possible. After the tapes are removed from the library, they must be stored in a safe location,
preferably in a different building. Therefore, in the event of full-system crash, the most recent users data would still be
available on the off-site Secondary Tape Set tapes.
Deciding to use Secondary Tape Sets

To decide whether or not to use Secondary Tape Sets, you should consider the following:
The amount of risk involved in your Data Center operations.

If you are running a standalone Data Center, the risk of losing some or all of your backed up data is much higher than
in a mirrored environment. If you run a mirrored Data Center, data is still at risk if one of the mirrors is completely
destroyed.
The advantages and disadvantages of this setup and how it can affect your Data Center operations.
The primary advantage of having Secondary Tape Sets is in having an ultimate degree of protection against loss or
damage of backup data. It is particularly valuable in a standalone server environment, where the risk of losing data due
to a disk or tape failure is especially high. In the event of an entire system crash, the off-site tapes from the Secondary
Tape Set remain the only source of end-user data, which would otherwise be lost forever.
30
Tape Sets
Although a mirrored server configuration provides an extra degree of data protection against all possible failures by storing
data redundantly at the two identical Data Centers, Secondary Tape Sets are still very helpful in the following situations:
You must quickly restore archive sets that are lost or damaged due to a tape failure.
One of the servers in a mirrored pair is completely destroyed, and you must quickly move backed-up data to a new
mirror.
The primary disadvantage of using Secondary Tape Sets is the increasing cost of media (you must provide additional tapes
to maintain this setup) and operation maintenance. Your decision is therefore a trade-off of cost against the level of risk you
are ready to accept.
Taking Secondary Tape Set tapes off site

To minimize the vulnerability of data in case of disk failure, fire, or other disaster, two schedules have been defined for the
Secondary Tape Sets: the migration schedule and the extraction schedule.
If you host your own Data Center and would like details about removing Secondary Tape Set tapes from a tape library using
the DCMC, refer to Remove Secondary Tapes, on page 125.
Migration schedule
Frequency of data migration to the Secondary Tape Set is determined by the migration schedule. In a single server
environment, the risk of losing data due to disk failure is much higher than in a mirrored server configuration. To reduce this
risk, data must be migrated to the Secondary Tape Set as frequently as possible. Instead of being demand driven, migration
is scheduled to run daily or several times per day using the daily automatic procedure. The greater the frequency of migration,
the less the data loss if the disk were to fail. Migration to the Secondary Tape Set can also be performed with the DCMC.
To ensure data safety in case of fire or other disaster that might result in loss of the entire Data Center, Secondary Tape Set
tapes must be removed from the library and taken off-site as often as possible. The extraction schedule defines how often the
Secondary Tape Set tapes are removed from the library.
Extraction schedule
The frequency of tape extraction is determined by the following factors:
The amount of data that the Data Center receives daily (if the Data Center has a large user community, tape removal
should be performed more frequently)
The number of blank tapes that the user provides to support the Secondary Tape Set configuration
You can set the extraction interval to less than, equal to, or greater than a day. You should remove Secondary Tape Set tapes
from the library every other day or as soon as the tape gets full (waiting until the tape gets full reduces the cost of media, but
increases the risk of losing backed-up data due to complete disk loss). After the tapes are removed, they should be stored in
a safe location, preferably in a different building. Then, in the event of a full system crash, the most recent data can still be
retrieved from the off-site Secondary Tape Sets.
31

Using multiple tape libraries
The Data Center can run with two tape libraries attached to each server. You might use multiple tape libraries for any of the
following situations:
You have an existing tape library and would like to replace it by transitioning to a new tape library (for example, if you
are replacing an older tape library with one that uses newer technology).
You want to keep your existing tape library, but you must use an additional reliever library temporarily until you can
free up tape space on the original library.
You want to permanently use multiple tape libraries to expand your total available tape capacity.
Each of these situations poses its own unique considerations and procedures. For information on installing two tape libraries
on your Data Center or adding a second tape library, visit the Resource Center.
Transition to a new tape library

If you want to replace your original tape library with a new one, you must make the transition over a period of time during
which you copy the data from the old library to the new library. A likely example of this situation is if you are replacing an
older tape library with one that uses newer technology.
When you replace a library, your goal is to stop using the old tape library, start using the new library, and copy the data from
the tapes in the old library to the tapes in the new library. Visit the Resource Center for a procedure to transition to a new
library.
Temporary reliever library

There might be times when you must use an additional tape library for temporary extended storage until Compactor is able
to free sufficient space in your original library. Your original library would remain your permanent library, and the additional
temporary library would remain in use only for as long as needed.
In this situation, you would simply connect the additional library and let the Compactor service run until it has freed up
enough tape space to warrant removing the additional library.
CAUTION
The previous process requires you to transfer tapes back and forth between tape libraries.
Therefore, the two libraries must be of compatible tape and barcode technologies.
32
Permanent expansion library

Using a permanent expansion library
If you are using multiple tape libraries because you want to permanently expand your available tape capacity, then you must
plan to keep the multiple libraries in use for an indefinite amount of time. Unlike the previous situations, your goal in this
situation is not to work toward using only one library again. Instead your goal is to continually use the multiple libraries as
efficiently as possible. Doing so means balancing tape utilization among all libraries in use.
To balance tape utilization, you should understand the following concepts:
How tape utilization works in HSM
How to balance tape utilization across multiple libraries
How to work with libraries of different technologies
Understanding tape utilization in HSM

When HSM migrates data to tape, it accesses the tapes in the alphabetical and numerical order of their labels. Regardless of
where or when the tapes are inserted, HSM looks for the next tape labeled alphabetically (or numerically) when the previous
tape is full.
For example, assume you have multiple tape libraries with 100 tapes that are labeled ABK001, ABK002,..., ABK100 (you
could have inserted these tapes at any time, in any order, or in any library). When ABK001 is full, HSM then migrates data
to ABK002. When ABK002 is full, HSM migrates data to ABK003, and so forth. It does not matter which library the tapes
are in.
If you have more than one Tape Group, you can split the tapes for the Tape Group between the two libraries. This is not a
concern if the libraries and tapes are of the same technology. The same holds true for Tape Account Groups. It is not a concern
if a Tape Account Group is split across two libraries. For more information on Tape Groups and Tape Account Groups refer
to Tape Groups and Tape Account Groups, on page 28
How HSM determines tape capacity

The driver installed for the tape drive determines a tapes capacity at the time the tape is loaded. HSM requests this
information from the drive shortly after each tape is loaded and then stores this information in an internal database.
Balancing tape utilization

To balance the workload across tape libraries, you should insert the tapes into the tape libraries so that their labels span the
libraries evenly.
For example, assume you have two libraries, each with a 50-tape capacity (a total of 100 tapes). Assume the barcode labels
that you attached to the tapes are ABK001, ABK002,..., ABK100. When you insert the tapes into the two libraries, you should
insert ABK001 into the first library, ABK002 into the second library, ABK003 into the first library, ABK004 into the second
library, and so forth. Then, when one tape is full and HSM accesses the next tape, it alternates between each tape library.
Working with libraries of different technologies

Balancing tape utilization is easy if you use libraries that are of compatible tape and barcode technologies because you can
simply move tapes between the libraries to get the order that yields optimum load balancing. However, this process is not as
easy if you use libraries of different tape and barcode technologies because you cannot simply move tapes between such
libraries.
33
If you use libraries of different tape and barcode technologies, you must prepare in advance of setting up the new tapes. When
you order barcode labels for new tapes, order labels with the same barcode labels as your other libraries. For example, if one
library uses ABK001-ABK200, order labels with ABK001-ABK200 for the additional library. That way you can attach the
barcodes, alternating numbers for each library. For example, use the ABK001 label for the first library, the ABK002 label
for the second library, the ABK003 label for the first library, the ABK004 label for the second library, and so forth. Then
HSM alternates libraries when migrating data to a new tape.
34
3
COMPACTOR
About this chapter
This chapter contains a description on the Compactor service. This chapter contains the following topics:
To learn about...
Refer to:
How different configurations use Compactor
Compactor and Data Center configurations, on page 36
How Compactor operates
How Compactor operates, on page 37
How file expiration affects Compactor
File expiration, on page 40
35
Chapter 3/Compactor
Compactor and Data Center configurations
Compactor and Data Center configurations

The Compactor service
As a Data Center service, Compactor runs automatically and continuously based on Data Center activity. Compactor has
several purposes:
Reduce overall storage requirement for the Data Center.
Improve Agent file retrieval performance.
Limit the number of tapes needed for account recovery.
Free tape and disk space by removing expired data.
Reduce the size of the databases.
Improve data integrity.
Compactor configurations
Compactor runs on all Data Center configurations but runs differently on a mirrored configuration than it does on a
standalone Data Center server. It also works differently with HSM as opposed to a disk-only configuration.
Compactor in mirrored Data Centers

For mirrored Data Centers, the Compactor service runs on both servers but only one of the servers in the pair controls the
workload of the compaction process. This server is referred to as the primary server. If you are running a clustered Data
Center, there is one primary server for every mirrored pair in the cluster. For example, a clustered Data Center with three
mirrored pairs has three primary servers. You can check the status of the primary server(s) in the Compactor view of DCMC.
Administration of Compactor
For assistance in administering Compactor, use DCMC to:
Start, stop, or pause the Compactor service
Specify startup parameters
Monitor Compactor progress for the current session
View recyclable tapes for reuse or removal from the library
Monitor disk space
Monitor Compactor progress for the past 90 days
You can access DCMC Help from DCMC for more information on these topics.
36
Chapter 3/Compactor

Compactor Tasks
The Compactor service removes older, unnecessary data from the Data Center. To accomplish this task, it does the following:
1.
Checks for necessary disk space (HSM configurations only).
2.
Selects accounts or a Tape Account Group.
3.
Performs a system analysis and repair.
4.
Marks files as expired.
5.
Repackages archive sets.
6.
Deletes expired archive sets and database entries.
7.
Migrates new archive sets to tape.
8.
Informs the Agent of changes.
Check disk space (HSM configurations only)

Before Compactor begins processing accounts, it checks for necessary disk space on all servers where HSM is installed. It
compares the DiskCache value in the Windows registry to the sum of free disk space on the archive partitions and the amount
of space taken up by customer archive sets. If there is available space, the compaction process proceeds. If there is not enough
available space, Compactor writes an error message to the Application log and then stops. A certain amount of disk space is
necessary because all archive sets for an account must be on disk for Compactor to process the account. Compactor also
checks for available disk space before each account is processed.
Disk-only Data Centers

On disk-only Data Centers all of the account's archive sets are already on disk; therefore, the disk cache check is not
necessary. If the free disk space on a disk-only Data Center server drops below 10% of the total disk space, Compactor
attempts to compact all accounts on the server to free up disk space.
Select Account or a Tape Account Group

Compactor must determine which accounts to work on per session. For a Data Center using a tape library, Compactor selects
the oldest Tape Account Group that has not been compacted in a set number of days. The default number of days is 15, but
you can adjust this number in DCMC. For more information about Tape Account Groups refer to Tape Groups and Tape
Account Groups, on page 28.
If a Data Center does not use a tape library for the Primary Tape Set (if it is disk-only or uses Centera), Compactor begins
working on accounts that have not been compacted in a set number of days. The default number of days is 15, but you can
adjust this number in DCMC.
Normally, Compactor runs continuously, but you can start the Compactor service by specifying an account, tape, or Tape
Account Group. You can also run compaction on canceled accounts only. Refer to DCMC Help for additional details about
using switches to start Compactor.
37
Chapter 3/Compactor
Perform system analysis and repair

On mirrored and clustered Data Centers, Compactor begins processing an account by first locking the account from all other
processes. Compactor checks for synchronicity of the accounts archive sets and database information on the local server and
then between the two servers of a mirrored pair. If inconsistencies exist, Compactor tries to correct them. If the account still
has inconsistencies, the Compactor service marks any files it cannot retrieve for deletion and requests the Data Center send
a notification to the Agent to resend those files.
Mark files as expired

Compactor uses rules created during Data Center installation to expire files. These rules include how long a canceled
accounts data are kept, how long files deleted from the Agent computer are kept, how long files excluded from the Agent
backup list are kept, and how many versions of a file are kept and for how long. For more specific information on the
expiration rules refer to File expiration, on page 40.
You can view and change the expiration rules within DCMC. Setting any of the values to -1 turns off the rule. Compactor
runs through every version of every file for the selected account and marks files as expired if a rule applies. Because the
expiration process is run on an account approximately every 90 days, there are times when there are more versions of a file
available than the rules would imply.
In configurations using HSM, when the expiration process is complete, archive sets are copied from tape to disk. Archive
sets for accounts that are canceled and ready to be compacted are not copied to disk. These accounts are processed first.
Repackage archive sets

After files have been marked as expired, Compactor can determine which files to delete and which archive sets to repackage
for efficiency.
If a failure to retrieve the archive set from tape or disk occurs, Compactor attempts to retrieve the archive set from the servers
mirror. When working with files in an archive set, Compactor either copies or rebases the file. Rebasing takes the original
base of a file (the first backed-up version) and combines it with its deltas (subsequent changes to backed-up files) to create
a new base. The expired base and deltas are no longer needed and are deleted. Compactor copies files to new archive sets
when a file is not expired but is in an archive set with other files that require rebasing or deletion. After the repackaging
process, Compactor performs additional checks of data integrity on the new archive sets.
Delete archive sets and database entries

After all archive sets have been repackaged, Compactor deletes all of the old archive sets from disk. During this process it
also deletes the appropriate database rows for these files and archive sets.
Compactor does not delete archive sets from tape but does delete information regarding the archive sets location on tape
from the database. This action renders the archive sets irretrievable and the tape space expired. When this step is complete
the account is unlocked, allowing access to all processes.
Migrate new archive sets to tape

In configurations using HSM, Compactor migrates new archive sets to the archive storage device. If using a tape library,
Compactor checks to see if there are four blank tapes in the library before beginning migration. Four tapes are recommended
because Tape Account Groups use four tapes by default. If four blank tapes are not available in the library, Compactor writes
an error message to the DCMaint log and the service is paused.
38
Chapter 3/Compactor
Notify the Agent about changes

When archive sets have been repackaged or deleted, the BackupServer service must notify the Agent of the change. The next
time the Agent connects to the Data Center server, its file list is updated with the new information from the compaction
process. Files that have been deleted by the Compactor service are no longer restorable by the Agent. Therefore, the Agent
must update its list of files available for retrieval.
Once all new archive sets are migrated, the process begins again with the check for available disk cache and selection of the
next account or Tape Account Group to be compacted.
39
Chapter 3/Compactor
File expiration
File expiration
File expiration process
To reuse disk and archive storage space, the Data Center deletes old data using a process during the Compactor process called
expiration.
During setup, you are asked to establish parameters that define when data is old and can be deleted. The file expiration
rules are set to reasonable defaults by Data Center Setup, so you can safely accept the defaults if you are not sure of the
parameters you need. Entering -1 for any of the values turns off the expiration rule.
On a disk-only configuration, file expiration rules are used to keep from running out of disk storage. On a server using HSM,
file expiration rules are only used to minimize growth of data in storage; the disk is kept at an acceptable free space level by
data migration. Consequently, you should monitor a disk-only configuration closely in the weeks after startup, and decrease
the file expiration rules if disk space is being filled too quickly. On both disk-only and HSM configurations, if space is tightly
limited, more aggressive file expiration rules are necessary. File expiration rules are changed using DCMC.
Expiration rules and default settings

The rules and their default settings are detailed as follows:
Canceled specifies the minimum number of days after an account is canceled until its backed-up data is deleted. The
default number of days until deletion is 60.
Deleted specifies the minimum number of days that a file is retained after it has been deleted from the Agent that backed
it up. If a file is backed up and later deleted, it is normally retrievable via the Agent. However, if the file has been expired
and compacted from the Data Center, it cannot be retrieved. The default value is 90 days for disk-only configurations
and 180 days for HSM configurations.
Excluded specifies the number of days that a file is retained after the end-user has excluded it from the backup list on
the Agent. If a file is backed up and then later excluded from the Agent backup list, it is expired and deleted the next
time Compactor runs on the account. The default value is zero days for disk-only and HSM configurations.
RecentVersions and OldVersions are used together to specify the number of versions of a file that are retained. For
example, if RecentVersions = 9 (versions) and OldVersions = 30 (days), then old versions of a file are deleted if they are
more than 30 days old or there are 9 more recent versions. The most recent backed-up version of a file is not expired
using these parameters. The default value for RecentVersions is 10 versions for disk-only configurations and 20 versions
for HSM configurations. The default value for OldVersions is 45 days for disk-only configurations and 90 days for HSM
configurations.
Rule exceptions
It is possible for data to be on the Data Center longer than the expiration rules imply. For example, on January 1st an end user
deletes a file from their computer that has been backed up to the Data Center, and then performs a subsequent backup.
Compactor is set to process accounts no more than every 90 days, the next time Compactor processes this account is on April
15th. In this example, the expiration rule for deleted files is 90 days. As Compactor is processing this account it marks the
file for deletion from the Data Center. The file lived on the Data Center for more than 90 days after its deletion from the
end-user computer. This is because the expiration rule values and the number of days between Compactor runs for an account
or Tape Account Group are minimum values. Data could remain on the Data Center longer than these values indicate.
40
PART II: DATA CENTER INSTALLATION
Chapter 4: Sizing Your Data Center

Chapter 5: Preparing for Installation
Chapter 6: Installing the Data Center Software
Chapter 7: Integrating the Data Center with Enterprise Directory
4
SIZING YOUR DATA CENTER
About this chapter
This chapter provides information that you can use as a guide to determine the hardware requirements for your Data Center.
Precise determination of these requirements is contingent upon a number of variables, most of which are dependant on the
specifics of the end user population, number of servers, and Agent configuration choices. Even if you are licensed for 5,000
users or 500 servers, you still might want to deploy hardware that would serve 10,000 users or 1,000 servers so you can easily
scale the Data Center to handle more users if needed in the future.
To learn about...
Refer to:
How sizing affects your Data Center
Sizing overview, on page 44
Minimum sizing estimates for the Data Center
Sizing estimates, on page 46
Requirements for network bandwidth
Network bandwidth requirements, on page 48
43
Chapter 4/Sizing Your Data Center
Sizing overview
Sizing overview
Planning your deployment
When sizing your Data Center hardware, plan for your total number of users or servers when completely deployed as opposed
to only the number you plan to initially deploy. If your goal is to have more than 10,000 users or 100 servers backing up to
the Data Center, then you should contact Iron Mountain Digital for assistance in sizing your Data Center hardware.
The information in this chapter provides guidelines for different hardware configurations including disk-only, disk with an
attached tape library, and disk with an attached EMC Centera. Disk-only Data Centers represent configurations using
Network Attached Storage (NAS), Storage Area Network (SAN) and directly attached disk storage. If you are configuring a
mirrored Data Center, each server must conform to the same guidelines.
Assumptions for PC accounts

The information in this chapter is based on the following assumptions about PC accounts:
First backup of each account is 1 GB compressed data, on average. This number does not include common files taking
advantage of SendOnce technology.
Size per month of compressed backup data per end user is 125 MB.
Number of files in first backup is 100,000, on average.
Number of delta files backed up monthly is 8,000 per end user.
Average total account size is 2 GB of compressed data.
Number of days archive sets remain on disk is 5 (HSM only).
Tape capacity is 100 GB (HSM only).
Effects of backed-up data from PC accounts

The number of files backed up, along with the size of the files backed up by your end users have a large impact on the sizing
of the Data Center servers. The size of the files backed up influences the amount of storage space needed for archive sets.
The number of files backed up influences the amount of storage space needed for SQL databases, database transaction logs
and, if running a standalone configuration, the database backups.
The sizing charts in this chapter were created with the assumption that end users would be backing up an average of 4,000
files per month with an average total compressed size of 150 MB per month. When sizing your Data Center it is important
to take these parameters into account. If your end users tend to create large files, the size of the Data Center servers must
reflect this activity.
Assumptions for server accounts

The information in this chapter is based on the following assumptions about server account:
44
First backup of each server account is 10 GB compressed, on average. This number does not include common files
taking advantage of SendOnce technology.
Size per month of compressed backup data per end server account is 1GB.
Number of files in first backup is 100,000, on average.
Number of delta files backed up monthly is 10,000 per server account.
Average total account size is .9 gigabytes of compressed data.
Number of days archive sets remain on disk is 5 (HSM only).
Sizing overview
Tape capacity is 15 GB (HSM only).
Effects of backed-up data from server accounts

The number of files backed up, along with the size of the files that server accounts backup have a large impact on the sizing
of the Data Center servers. The size of the files backed up influences the amount of storage space needed for archive sets.
The number of files backed up influences the amount of storage space needed for SQL databases, database transaction logs
and, if running a standalone configuration, the database backups.
The sizing charts in this chapter were created with the assumption that servers would be backing up an average of 4,000 files
per month with an average total compressed size of 150 MB per month. When sizing your Data Center it is important to take
these parameters into account. If the servers store large files, the size of the Data Center servers must reflect this activity.
Additional resources
If your Data Center has variables not accounted for in this chapter, contact Iron Mountain Digital for an individualized sizing
estimation.
Visit the Resource Center for a table that compares each configuration type against each end user range overall.
45
Sizing estimates
Sizing estimates
You can estimate the sizing for a Data Center based on the number of accounts.
Note
If you are configuring a mirrored Data Center, each server must conform to the same minimum
guidelines.
Sizing estimates for accounts

The following table provides sizing estimates for a Data Center based on the data and the number of PC and server accounts.
Volume/folder
PC Account
Server Account
Archive set
2 TB per 1000 PC accounts for disk-only

configurations
2 TB per 200 server accounts for diskonly configurations
200 GB per 1000 PC accounts for Data

Centers with a Centera
200 GB per 200 server accounts for Data

Centers with a Centera
Database
50 GB per 1000 PC accounts
50 GB per 200 server accounts
Centera
2 TB per 1000 PC accounts for disk-only

configurations
2 TB per 200 server accounts for diskonly configurations
Application disk space requirements

The following table provides the minimum application disk space requirements for sizing a Data Center.
Application volume/folder
Requirement
Operating system volume
Windows 2000 Server 8 GB
Windows 2003 Server 10 GB
SQL Server Application volume/folder
SQL Server 2000 SP4 1 GB
Data Center Application volume/folder
900 MB and 130 MB per additional English Agent File Set
2 GB and 1.5 GB per additional International Agent File Set
8 GB
Account Management volume/folder
46
Sizing estimates
Hardware requirements
The following table provides minimum hardware requirements for sizing a Data Center.
Hardware
Requirement
Processors
Server class with dual 2 GHz processors or a single 3

GHz Dual Core processor
Memory
4 GB parity or ECC
Ethernet Adapter
1 GB per second
47
Network bandwidth requirements
Network bandwidth requirements

When considering the network load involved with running your own Data Center, you must focus on the number of Agents
you are deploying. There must be sufficient network bandwidth available for the Agents to communicate with the Data
Center server.
If the Data Center is configured as a mirrored pair, each Agent must have access to both of the servers in case the Agent
cannot access its primary server. Additionally, sufficient network bandwidth must be available for the mirrored servers to
communicate with each other.
Network requirements table

The following table lists the recommended network requirements.
Network element
Network requirements
Network bandwidth between the client and each Data Center 1 megabit/second based on 5 to 6 MB of compressed data per
user per day.
48
IP address
One per Data Center
Network bandwidth between the two Data Centers (if

mirrored configuration)
1 megabit/second based on 5 to 6 MB of compressed data per

user per day.
5
PREPARING FOR INSTALLATION
Configure your servers
Before you can install the Data Center, make sure your servers are prepared and configured correctly for the installation. This
chapter explains how to prepare your server for a Data Center installation.
About this chapter

To learn about...
Refer to:
Tasks you need to complete before installing the Data Center Preinstallation tasks, on page 50
software
Information about configurations and licensing options
Evaluating configuration and license options, on page 51
The requirements for installing the Data Center server

software
Data Center server requirements, on page 52
The requirements for storage solutions
Storage solutions requirements, on page 55
The requirements for network connections
Network requirements, on page 59
The requirements for security
Security requirements, on page 60
How to install the required Microsoft software on the Data

Center server
Installing and configuring Microsoft software, on page 61
How to prepare Support Center and the Account

Management Website with MyRoamTM application for use
Support Center and Account Management Website

preparation, on page 68
49
Chapter 5/Preparing for Installation
Preinstallation tasks
Preinstallation tasks
Preparing for installation
To prepare your Data Center for installation, you should do the following:
Evaluate the appropriate configuration and licensing for your organization.
Review Data Center server requirements.
Review storage solutions requirements.
Review the network requirements.
Review security requirements for your Data Center.
Install and configure Microsoft software.
Prepare the Support Center and Account Management Website server(s) for installation.
Note
The Data Center supports the use of the Account Management Website with MyRoam application for
Connected Backup Agents. If you are using Legacy Agents only, you can ignore all references to the
MyRoam application.
The specific tasks within each of these steps depend on your Data Center configuration. For example, a standalone Data
Center has a different configuration from a mirrored Data Center, and a disk-only Data Center has a different configuration
from a Data Center with Hierarchical Storage Manager (HSM) installed.
Use the Data Center Installation Worksheets in Appendix B to organize your Data Center information. Having this
information available can make the Data Center installation easier.
50
Evaluating configuration and license options
Evaluating configuration and license options

Estimate your needs
Prior to installation, your organization must evaluate deployment options and select the configuration and licensing
agreement most appropriate to your information backup requirements. As part of this process, it is important to determine
the following:
Whether you will have a standalone Data Center or one configured with mirrored pair(s).
Your licensing needs.
The features that you need to deploy.
Standalone Data Center or mirrored pair

The most important decision when preparing to deploy the Data Center is whether you are going to use a standalone Data
Center server or a mirrored pair of servers. There is only one server in a standalone Data Center while a mirrored
configuration has two servers that mirror each other. You can also deploy a clustered Data Center. A clustered Data Center
is similar to a mirrored configuration except that it has more than one mirrored pair. For more information about Data Center
configurations, refer to the Connected Backup/PC Product Overview manual.
The decision to use a standalone Data Center or mirrored pairs depends on the anticipated size of your deployment and the
hardware you have available. Generally speaking, a mirrored configuration requires two of everything that you need for a
standalone Data Center. Of course, the benefit is in having redundant data and server availability during maintenance
downtime or in the event of a disaster.
Whichever configuration you select, you should have an additional server to function as a Web server for Support Center
and, optionally, the MyRoam application.
Licensing
Every Data Center must be licensed. You can purchase licenses for PC accounts only, server accounts only, or both. You
should obtain a permanent license before installing the Data Center software. However, if you do not have a license at the
time of installation, the Setup program creates a temporary license that expires in thirty days.
Your Data Center's license enables optional features your organization has chosen to implement. It also tracks the number of
active users and servers on the Data Center and warns you when the license use is nearing the contracted number.
If at any time you would like to change the features in use at your Data Center or increase the number of end users serviced,
you can contact Support to obtain a new license. For further information about obtaining a new Data Center license, refer to
Chapter 14: Monthly Maintenance.
51
Data Center server requirements

Sizing your Data Center
You should select the hardware for each Data Center server with care. For current information on how to select an appropriate
processor, amount of memory, RAID storage, and other hardware, refer to Chapter 4: Sizing Your Data Center or request an
individualized assessment from your Connected representative.
Production-quality Data Center servers should be dedicated to this application and not shared with other applications.
Configuring these servers as primary or secondary Microsoft Windows domain controllers places an additional
performance burden on them and is not normally recommended, unless the Data Center servers are the only ones using the
domain.
Software requirements
To install the Data Center software, your servers must have the following software installed
Component
Requirement
Operating system
Any of the following Microsoft Windows Server U. S. English operating

systems:
Windows 2003 Standard and Enterprise Editions with Service Pack 2, and
ODBC version 3.0 or later.
Windows 2003 Server Standard and Enterprise Editions R2, and ODBC
version 3.0 or later.
Windows 2000 Server with Service Pack (SP) 4 and all security hotfixes,
and ODBC version 3.0 or later.
Microsoft .NET Framework version 1.1 installed on the Support Center

server.
Important: Windows Small Business Server 2003 is not a supported operating

system for the Data Center server.
Note: On the Web server where Support Center is installed, you must set the
Locale in Regional Options to English (United States). Make sure the default
locale and current locale are set to English (United States) before starting
Support Center.
Database
Network
Microsoft SQL Server 2000, with the following:
Service Pack 4 with available hotfixes.
SQL Server licensing, as necessary.
Enable NetBios over TCP/IP.

The HostID.exe program requires this configuration to properly verify the
Data Center server's MAC address against the Data Center license.
52
Note
For the purposes of this document, references to Windows or Windows Server refer to both Windows
Server 2000 and Windows Server 2003. Information that is pertinent to one specific operating system
is called out as such.
Refer to Installing and configuring Microsoft software, on page 61 for information on installing Microsoft software. Also,
refer to Web server preparation, on page 70 for Support Center and Account Management Website software requirements.
Note
If your Data Center supports more than 10,000 accounts, you should not run Support Center and the
Account Management Website on the same server.
VMware Support
You can install the Data Center on VMware configured to meet the existing system requirements, and open a browser
(Internet Explorer version 6.0 or later) and run the application. Supported versions are VMware ESX 2.5.1, 2.5.2, 2.5.3, and
3.0.1.
Recommended hardware for database backups

Standalone Data Centers use the Weekly Automatic Procedure to automatically backup the SQL databases (refer to
Chapter 13: Weekly Maintenance for details). You can perform these backups to either disk or tape. If you choose to have a
local tape drive and blank tapes for backing up the SQL database (internal/external AIT2 or DLT tape drive or similar), these
items also need to be installed. Alternatively, you can employ other methods of backing up the SQL databases. It is critical
that you routinely back up your database, whichever method you employ.
If you are running a mirrored or clustered Data Center the SQL databases are replicated between the servers. Therefore, the
databases are not backed up using the Weekly Automatic Procedure. The complete mirroring of the databases on a mirrored
Data Center increases the ease and time needed to recover from a database loss.
Note
If you set up a tape device for database backups, and you test it using a Windows Server backup, SQL
Server is not able to use the same media as used for the Windows Server backup.
Recommended naming convention

When choosing names for your Data Center server(s), avoid using the words BACKUP and UPDATE (and other keywords
that Microsoft SQL Server uses) as part of the server name. Using these words in the server name causes problems when the
Data Center software attempts to perform SQL queries. You should also avoid using spaces and special characters such as
the hyphen (-) in the server name.
Running Data Center Setup locally

For the Setup applications help to work correctly, we recommend running the setup application locally. If you run the setup
program remotely, the security settings in Microsoft will not allow access to the Help system.
53
Antivirus software and the Data Center

You should never run antivirus software on the Customers folder of a Data Center server (for example,
D:\Customers). Antivirus software might wrongly confuse the compressed and encrypted archives in the Customers
folder with virus signatures. Most antivirus software would then isolate the archives, essentially corrupting them. The
Data Center would no longer be able to access the archives resulting in data loss. Do not enable antivirus scanning of the
Customer folder.
Archiving files that have already been infected with a virus do not affect Data Center servers. The nature of the encryption
and compression techniques used during backup inoculates the virus from affecting the servers. Connected DataProtector/PC
software, however, does not provide protection to end users who might recover an infected file. If a file is backed up in an
infected state, it will be recovered in such a state. Only client side scans can accurately detect and remedy these issues.
Make the necessary adjustments in your Antivirus software to exclude the Customers folder from antivirus scans before
bringing the Data Center up and online.
54
Storage solutions requirements

Solution types
You can opt to add a secondary storage device to your Data Center to expand available archive storage. The Data Center
supports the following types of secondary storage:
Disk-based
HSM-based
Disk-based solutions
The Connected Backup application supports the following disk-based solutions for secondary storage:
Network Attached Storage (NAS)
Storage Attached Network (SAN)
Disk solutions interface with the Data Center directly rather than through HSM. The following sections include information
to help you prepare your disk solutions for use with the Data Center.
Network Attached Storage

If the Data Center uses NAS devices for extended archive storage, follow the instructions from the NAS vendor for proper
installation and connection to the Data Center servers.
The Data Center uses universal naming convention (UNC) paths and the Microsoft Common Internet File System (CIFS) to
address NAS devices. The Data Center installation asks for the share name of the NAS device on the Data Center server.
Take note of this information in the Data Center Installation Worksheets found in Appendix B.
CAUTION
Do not install the SQL Server database files on a NAS device. Both Microsoft and NAS vendors support
this configuration, but it has not been proven as an efficient or stable configuration for the Connected
Backup application.
The Data Center domain account, CNTD_DCServices, must have full permissions on the NAS volume. Refer to Security
requirements, on page 60 for more information regarding the CNTD_DCServices account.
To improve performance, network interfaces on the Data Center server and on the NAS device, as well as all switches and
bridges, must be set to 100 Full Duplex. You should verify that this setting is correct because it is not always the default
setting.
Storage Attached Network

The Data Center views Storage Attached Network (SAN) as a logical drive. If you are using a SAN with your Data Center
configuration, select the drive letter associated with it for the Customers volume during Data Center Setup.
Unlike NAS devices, you can install the SQL database files on a SAN, although this is not a requirement. A SAN also differs
from a NAS device in that it does not require the CNTD_DCServices account to be given permissions on the SAN. Data
Center Setup automatically configures the CNTD_DCServices account to have access to the Customers folder on the
SAN.
55
HSM-based solutions
If you are installing HSM, you also must have an archive storage device. Visit the Resource Center for a current list of
supported devices. In general, the Connected Backup solution supports tape libraries, EMC Centera, and Distributed AML
Server (DAS). This section contains information about preparing each device for HSM.
EMC Centera
If the Data Center uses EMC Centera as an archive storage device, you should follow the instructions that came with Centera
for proper installation and connection to the Data Center servers. Visit the Resource Center to view a list of supported Centera
software and hardware.
During Data Center Setup, you must enter the following information. For details, see the Data Center Setup online help.
Centera Addresses IP address(es) of the Centera. You can record the IP address(es) on the Data Center Installation
Worksheets in Appendix B.
Handler count Number of threads between Centera and the Data Center. The recommended number is 10 threads
for 100 megabit of network connectivity between Centera and the Data Center. If you use a gigabit connection between
Centera and the Data Center, use 20 threads.
Main Profile BackupHSM uses the Main profile to write data to and read data from the Centera. The default path
and name for the Main profile is: C:\CenteraProfiles\connected_main.pea, but may be edited. You can
record the Main profile path and name on the Data Center Installation Worksheets in Appendix B. For information about
how to set up a profile before running Data Center Setup, refer to the Resource Center procedure Using Centera Access
Profiles with the Data Center (document number 1657).
Purge Profile BackupHSM uses the Purge profile to purge data from the Centera. If Centera does not have purge
capability, BackupHSM deletes the data from Centera. The default path and name for the Purge profile is:
C:\CenteraProfiles\connected_purge.pea, but may be edited. You can record the Purge profile path and
name on the Data Center Installation Worksheets in Appendix B. For information about how to set up a profile before
running Data Center Setup, refer to the Resource Center procedure Using Centera Access Profiles with the Data Center
(document 1657).
Data Center Setup automatically configures HSM to work with Centera with the following settings. If you need to modify
any of these settings, contact Support.
MaxArchiveSize Determines the maximum size of an archive set for optimal performance. The default value is 90
megabytes.
CenteraPurgeInterval Determines how often the Data Center monitors for expired archive sets. The default value
is 1 day.
Tape libraries
If the Data Center will be using a tape library, you will need to have numeric barcode tape labels, and a differential SCSI host
adapter and cable available before installing HSM.
CAUTION
The host adapter to be connected to the library and its tape drives should have SCSI parity enabled.
Otherwise, you could experience problems with unreadable tapes and data loss.
The number of tape drives you have depends on your particular tape library. The tape drives in the tape library are numbered
in the order determined by the physical location of the drive in the library. For example, Drive 0 might be at the top of the
library, followed by Drive 1, Drive 2, Drive 3, and so forth, as you move from the top to the bottom of the library. The specific
numbering sequence varies according to manufacturer. You should refer to the documentation supplied with your tape library
to determine the correct numbering sequence.
56
SCSI ID guidelines for a single SCSI bus

For the tape library and tape drives to function properly, you must connect them to the correct SCSI ports or SCSI busses.
Use the following guidelines for SCSI IDs, using a single SCSI bus:
Set Drive 0 to the lowest available SCSI ID number.
Connect Drive 1 to a SCSI port with an ID number greater than the ID number of the port for tape Drive 0.
The SCSI port ID number for tape Drive 2 must be higher than the ID number for tape Drive 1, etc. The higher the drive
number-the higher the ID number, as shown in the table.
The SCSI IDs do not have to be consecutive.
Tape Drive Number
SCSI
Drive 0
Drive 1
Drive 2
Drive 3
SCSI bus guidelines for multiple SCSI busses

Use the following guidelines for SCSI Busses and IDs, using multiple SCSI busses:
Connect tape drives to busses in consecutive order. For example, connect Drive 0 and Drive 1 to Bus 0; connect Drive
2, Drive 3, and Drive 4 to Bus 1, etc.
Do not connect drives to busses out of sequence. In other words, do not connect Drives 0, 2 and 4 to Bus 0 while
connecting Drives 1, 3, and 5 to Bus 1.
Higher drive numbers must be connected to higher Bus ID numbers, as shown in the table.
The Bus IDs, and the SCSI IDs for each bus, do not have to be consecutive.
Tape Drive Number
SCSI Bus Number
SCSI ID Number
Drive 0
Bus 0
Drive 1
Bus 0
Drive 2
Bus 1
Drive 3
Bus 1
Drive 4
Bus 1
With Microsoft Windows registry editor, you can verify and edit the SCSI mapping in the following registry key:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI
CAUTION
Editing the Windows registry is a procedure that can render your server inoperable. Exercise extreme
caution when editing the registry. For assistance in editing the Windows registry safely, contact Support.
57
Removable Storage Manager

The Removable Storage Manager (RSM) is a Windows Server component that is not compatible with the Data Centers HSM
service. For this reason it is necessary to disable RSM. Follow these steps to disable RSM for specific devices:
1.
Right-click My Computer and select Manage.
2.
In the left pane, expand the Removable Storage node.
3.
Click the Physical Locations folder. A list of tape libraries and drives appears in the right pane.
4.
In the right pane, right-click a listed tape library or drive listed that HSM will use and select Properties.
5.
In the General tab, clear the Enable library check box to deselect it.
6.
Click OK.
7.
Repeat steps 4 through 6 for each tape library and/or drive to be used by HSM.
Distributed AML Server

If the Data Center will be using Distributed AML Server (DAS) as an archive storage device, you should follow the
instructions from the DAS vendor for proper installation and connection to the Data Center server(s).
Refer to SCSI ID guidelines for a single SCSI bus, on page 56 or SCSI bus guidelines for multiple SCSI busses, on page 57
for information on configuring SCSI busses and IDs for the DAS.
To disable RSM for tape drives used by the DAS refer to the section Removable Storage Manager, on page 57.
The Data Center installation asks for the DAS server name and the client name. The client name in a DAS configuration
refers to the server, in this situation the Data Center server, attached to the DAS as it was named during the DAS installation.
Take note of this information in the Data Center Installation Worksheets found in Appendix B.
58
Determining server configuration
The Agent must be able to communicate with the Data Center. Also, if running a mirrored configuration, the Data Center
servers must be able to communicate with each other. For information on network bandwidth requirements, refer to Network
bandwidth requirements, on page 48.
When setting up a mirrored pair, you must assign a unique IP address, or optionally a DNS name, to each server. You must
also establish connectivity between the pair of servers before installing the Data Center software.
Enable NetBios over TCP/IP

On the Data Center computer, enable NetBios over TCP/IP. The HostID.exe program requires this configuration to
properly verify the Data Center server's MAC address against the Data Center license.
Ports
If a firewall or router is restricting communications between mirrored servers, each server must be able to access the
following ports on its mirror:
UDP and TCP - port 135 (Windows).
UDP ports 137 and 138 (Windows).
TCP port 139 (Windows).
TCP port 1433 (SQL Server).
TCP port 16384 (Agent registration, backup, Retrieve, Heal).
TCP port 16385 (data replication).
TCP port 16386 (Agent Service SOAP Server ).
TCP port 16387 (Agent Service Media Mode SOAP Server).
TCP port 16388 (Background Notification Process Listener).
TCP port 16389 (IIS to Account Management Website Tomcat Connector ).
TCP port 16390 (SSWS (Account Management Website Tomcat).
TCP port 16391 (Account Management Website Tomcat Shutdown Listener).
TCP ports 16400 - 16406 (RPC connections for Data Center services).
If a firewall or router is restricting communications between the Agent and the Data Center servers, each server must permit
TCP access on port 16384.
File and Printer Sharing for Microsoft Networks

Enabling File and Printer Sharing for Microsoft Networks is required on the network connections that the Data Center uses.
If you do not enable this property some of the backup and replication components will not work.
59
Security requirements
Security requirements
Setting up security
The Data Center uses Windows authentication and logons to run its services and to connect to SQL Server. The Data Center
installation software creates three domain accounts, each with very limited permission. The Data Center uses these accounts
to run the Data Center services and components.
During installation, Setup creates these accounts using the names and passwords that you specify. If you choose to change
the names of these accounts, make sure you record the new name and password of each account for later use. Choose account
names that accurately reflect the purpose of the account. Alternatively, you can opt to accept the default account names
created during installation.
Domain accounts
The Data Center installation creates the following domain accounts:
Default Account Name
Purpose
CNTD_DCServices
Used to run BackupServer, PoolServer, DCAlerter, ReplicationServer,

IndexServer, Compactor, HSMPurge, and BackupHSM.
CNTD_WebServices
Used by Support Center and the Account Management Website application.
CNTD_DataBundler
Used to run DataBundler.

Refer to Installing the DataBundler Application, on page 107 for additional
details about installing and invoking DataBundler.
You must log on to the server using an account with administrative privileges and the permission to create domain accounts
to run Data Center Setup, otherwise, the accounts created will not have the necessary permissions to start services,
authenticate Support Center and Account Management Website application logon attempts, or run DataBundler.
You can opt to create these accounts manually prior to running Data Center Setup. If you create the accounts prior to Setup,
the accounts must all be in the same domain. This is particularly important in a mirrored configuration where servers must
communicate with each other.
Whether you create these accounts manually or not, during installation, you are prompted to provide a password for each
account.
CAUTION
The domain accounts created by Setup to run the Data Center have limited permissions. Do not use these
accounts to log on to the Data Center server.
Domain account for SQL server

The Microsoft SQL Server requires a domain account with administrative privileges to run properly. Refer to SQL Server
installation guidelines, on page 66 for additional information about installing the SQL server software.
60
Installing and configuring Microsoft software

Before installing
Before you install the operating system or SQL Server, verify the following:
The vendors for all hardware, software, and firmware in your Data Center support Microsoft Windows 2000 Server or
Windows 2003 Server and SQL Server 2000.
All device drivers are at the appropriate revision level according to vendor recommendations.
Ensure that your support contracts are current.

CAUTION
Do not install any software applications that are not discussed in this chapter. Adding unsupported
software to a Data Center server can have uncertain effects on the servers performance.
When installing the required software, be sure to follow the guidelines in the remainder of this section to prepare your server
for a Data Center installation.
For specific Data Center software requirements, refer to Data Center server requirements, on page 52.
Windows server installation guidelines

When you install Windows Server, use the following guidelines to make sure the server is prepared for a Data Center
installation:
Ensure that Windows Server is configured for U.S. date format.
When asked about disk partitions, do the following:
Delete any existing disk partitions, even if you are removing a system partition. However, do not delete any
proprietary computer vendor partitions created for configuration purposes (for example, an EISA partition).
Create an 8 GB, or larger if desired, boot partition (RAID or other redundant storage is best for the boot partition,
but is not essential).
Next, create a page file that is equal to the amount of installed RAM times two.
Install Windows in the new partition. Specify NTFS formatting for the system or boot partition.
When asked about licensing modes, select an option that represents per user licensing (depending on the Windows
version, this might be Per Seat Licensing or Per Device or Per User licensing).
When asked about server type, select standalone server rather than either of the domain controller options, provided
there are existing domain controllers in the network.
When asked about the network configuration for Windows 2000 Server, accept the following default selections:
The computer will participate on a network
Wired to the network
If installing Windows 2003 Server, select:
Typical settings
If installing Windows 2000 Server, be sure to include IIS as part of the installation on the server that will host Support
Center and the MyRoam application (you can use the MyRoam application with Connected Backup Agents only).
Accept all default setup options for IIS except FTP and Gopher, which you should not select. Verify that World Wide
Web Service is selected.
61
If installing Windows 2003 Server, IIS is installed separately after the initial installation. Refer to Install IIS on Windows
2003 server, on page 63 for steps to install IIS after the initial Windows 2003 Server installation.
Refer to Web server preparation, on page 70 for information on setting up IIS on your Web server.
When asked for network protocols, install the TCP/IP protocol. The Data Center software does not use IPX/SPX, though
you can install it if you need it for administrative purposes.
If installing Windows 2000 Server, select the workgroup option (instead of domain) with the default workgroup name
WORKGROUP. Refer to Assign the server to an existing domain on Windows 2000, on page 64 for steps to perform
this task after the initial Windows installation.
If installing Windows 2003 Server, add the server to the appropriate domain during the initial Windows 2003 Server
installation.
Windows server configuration guidelines

After you install Windows Server, you must do the following to configure the server and to prepare it for the Data Center
installation:
Enable IIS installation
Install and configure IIS (Windows 2003 server)
Create data partitions
Assign the server to a domain (Windows 2000 server)
Update the lmhosts configuration
Install a Data Center tape library driver (for HSM configurations)
Synchronize date and time
Verify mirrored servers (for mirrored configurations)
Make emergency repair disks
Enable Internet Information Server (IIS) installation

When you install Windows on the Web server hosting Support Center or the MyRoam application, make sure IIS installation
is enabled so that IIS is installed at the same time. If IIS is not yet installed on the Web server, you should use the Windows
installation program to install it.
The Data Center Setup program installs Support Center and the MyRoam application to your default Web server location
that is specified under the following Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\
Parameters\Virtual Roots
If you want to change the location where Support Center and the MyRoam application are installed, you must change your
Web server location using IIS Manager prior to installing the Data Center software.
The default installation of IIS creates a user called IUSER_servername. This account is used for the Anonymous Access
rights needed for Support Center and the MyRoam application access. By default, this account might not have sufficient
permissions to access all needed files.
To ensure all necessary permissions are granted, do one of the following:
62
Grant the IUSER_servername account Full Control permissions to the following folders: DataCenter,
InetPub\wwwroot\SupportCenter, InetPub\wwwroot\MyRoam, and the Temp folder (depending on your
operating system, either WINNT\Temp. or Windows\Temp).
Change the default account (IUSER_servername) to the Web Services logon account (CNTD_WebServices) created
during Data Center Setup and give this account Full Control permissions to the Temp folder (depedong on your
operating system, either WINNT\Temp or Windows\Temp).
Install IIS on Windows 2003 server

Use the following steps to install IIS on a Windows 2003 server that will host Support Center or the Account Management
Website application:
1.
In the Add or Remove Programs Control Panel window, select Add/Remove Windows Components.
2.
In Windows Components Wizard, select Application Server from the Components section and click Details.
3.
In the Application Server window, select Internet Information Services (IIS) and click Details.
4.
In the Internet Information Services (IIS) window, select Common Files, Internet Information Services Manager,
and World Wide Web Service.
5.
Click OK.
Configure IIS on Windows 2003 server

If Web server is running Windows 2003 Server, use IIS Manager to verify that active server pages are enabled. You must also
follow these steps to ensure proper MyRoam functionality:
1.
Open IIS Manager
2.
Right-click the server name and select Properties.
3.
Click MIME Types.
4.
Click New.
5.
Add the extension .out with MIME type Application/octet-stream.
6.
Click OK.
7.
Use Control Panel Services to stop IIS Admin Service.
8.
Use Control Panel Services to start World Wide Web Publishing Service.
Create data partitions

You must create data partitions for storing SQL databases and archive files. Assuming that you have three RAID volumes,
you would typically use one partition to store the SQL databases, one partition to store the SQL database transaction logs,
and the third partition to store the archive files.
The Data Center creates a share called VolumeX$ where X represents the drive letter for the volume(s) on which the customer
archives are stored. If necessary, modify the volume using the following guidelines:
The CNTD_DCServices account must have change permission, the CNTD_CDMaker account must have read
permission and the account used to log on to the Data Center must have administrator privileges that grant full rights to
these shares.
Any accounts used to access the customer archives, such as those used by CD Maker must be in the same domain.
63
Assign the server to an existing domain on Windows 2000

If using Windows 2000 Server, assign the server to an existing domain using the following steps:
1.
Right-click My Computer and click Properties.
2.
In the System Properties window, click the Network Identification tab and then click Properties.
3.
In the Member of section, type an appropriate domain name in Domain. All servers in the Data Center configuration
must be in the same domain.
4.
In the Domain Username and Password pop-up window, provide a username and password for an account that has
administrator privileges in the domain. Refer to Security requirements, on page 60 for more information.
Note
Using the Data Center servers as domain controllers places an additional performance load on them
and is not typically recommended.
5.
When you restart the server, log on with an account that has administrator privileges in the domain that you specified in
this procedure. You will use this account to set up the Data Centers.
Update the lmhost configuration

For mirrored Data Centers not configured to use DNS, you must add a line at the bottom of the lmhosts file to describe the
mirror of the server you are currently installing. Doing so forces the IP address of the mirrored server to be pre-loaded into
the NETBIOS cache at server startup.
The lmhosts file should be located in the C:\WINNT\System32\drivers\ folder.
If you do not have an lmhosts file, create one following the Microsoft documentation and lmhosts.sam sample file. After
you have an lmhosts file, use a text editor such as Notepad to open it. The line you must enter at the bottom of the file is in
the following format:
<IP> <tab><server name> <tab>#PRE
For example, 111.111.111.111 ABCCorporation_2 #PRE
When you save the lmhosts file, verify that your text editor does not add a .txt file extension.
Install Data Center tape library driver

If you are going to use HSM with either a tape library or DAS, you must install the SCSI adapter board and cable it to the
tape library. After the installation is complete, you must install the device drivers for the tape drives. To install the device
drivers, use the following steps:
64
1.
Turn on the tape library's power.
2.
Open Windows Explorer.
3.
Right-click My Computer and select Manage.
4.
In the left pane, click Device Manager.
5.
In the right pane, expand Tape drives.

Follow the next steps for each tape library drive. Do not follow these steps for the DAT tape drive, if used.
6.
a.
Right-click the first tape drive device and select Properties.
b.
Click the Driver tab.
c.
Click Update Driver.
d.
Click Next on the first window of the Upgrade Device Driver Wizard.
e.
Select Display a list of the known drivers for this device so that I can choose a specific driver, and click Next.
f.
For non-DAS tape libraries: Click Have Disk. From the Connected Backup CD, select the DLT8000.INF file
for a DLT tape drive or the SW2AIT.INF file for an AIT tape drive. Install the tape device driver from the CD.
g.
For DAS libraries: Click Have Disk and install the drivers that came with the drivers installed in the DAS or
download the latest version from the vendors Web site.
Reboot the server so that Windows reassigns tape device numbers to the tape library.
Synchronize date and time

If your Data Center configuration is mirrored, set the date and time for the mirrored server to be the same as the date and
time on the first Data Center server. If your Data Center configuration is clustered, set the date and time for each pair of
servers to be the same as the date and time as the first pair of Data Center servers. The time values should differ by no more
than 30 seconds and should remain synchronized. If the time values differ by more than 30 seconds, errors can occur.
Note
Numerous time-synchronization tools are available that run as a service under Windows to
synchronize the time between the two servers.
Verify mirrored servers

If your Data Center configuration is mirrored, you must verify that each server can write files to its mirror. On each server,
map a network drive from the server to its mirror. Be sure to map the drive to the mirrored server's data partition, as explained
in the section Create data partitions, on page 63. Since you have logged in as a domain administrator, you can type the path:
\\<computer>\<drive letter>$
The <drive letter> variable is the drive used for the data partition. Do not select Reconnect at Login. This network drive
maps the data partition on the mirror to a drive letter on this server. Verify that you can copy files to and from the remote
drive from your local drive.
Disconnect the network drive when you are finished with the test. Be sure to test this process on both mirrors in each pair.
65
Verify access from remote computers

Verify that one of the end-user computers can ping each Data Center server. At a DOS command prompt on an end user's
computer use the command ping <ip> (for example, ping 111.111.111.111) to verify that each Data Center is
reachable (if your firewalls are configured to prohibit ping access from a computer to the Data Center, you can skip this
verification).
Verify that one of the computers to be used for Help Desk functionality can access the Web pages on the Web server(s) for
Support Center and the MyRoam application. Using Internet Explorer, open the default page on each server:
http://<Web_server_name>/default.asp
Make an emergency repair disk on Windows 2000 server

After you have finished installing and configuring your Windows 2000 server(s) and before you install the Data Center
software, you should make an emergency repair disk for each Data Center. Use the following steps:
1.
Select the Windows Backup utility from the Windows Accessories \ System Tools menu in the Start menu.
2.
Insert a formatted floppy disk.
3.
In the Backup utility, click the Tools menu and select Create an Emergency Repair Disk.
4.
Follow the online instructions. When prompted, be sure to select to back up the registry.
5.
When the repair disk is created, remove and label the floppy disk.
Make an emergency repair disk on Windows 2003 server

After you have finished installing and configuring your Windows 2003 server(s) and before you install the Data Center
software, you should make an emergency repair disk for each Data Center. Use the following steps:
1.
Select the Windows Backup utility from the Accessories \ System Tools menu in the Start menu.
2.
Insert a formatted floppy disk.
3.
In the Backup or Restore Wizard window, click Advanced Mode.
4.
In the Backup Utility window, click Automated System Recovery Wizard.
5.
Follow the online instructions. When prompted, be sure to select to back up the registry.
6.
When the repair disk is created, remove and label the floppy disk.
SQL server
Microsoft has implemented a processor-based licensing model to simplify SQL Server licensing. Under this new model, you
acquire a Processor License for each processor running the SQL Server software. If you have made a processor inaccessible
to all operating system copies on which the SQL Server software is set up to run, you do not need a software license for that
processor.
A Processor license includes access for an unlimited number of devices to connect from either inside the corporate LAN or
WAN or outside the firewall. You do not need to purchase additional Server licenses or Client Access Licenses (CALs). The
Processor license is all you need.
If you are installing SQL Server on the Web server or the DataBundler computer, it is only necessary to install the Client
Networking Utility. A full installation of SQL Server is not needed.
Installing SQL Server on a SQL Server farm for use with the Data Center is not a supported configuration. SQL Server must
be installed locally for use with the Data Center.
SQL Server installation guidelines

Use the following guidelines when installing SQL Server:
66
1.
The Data Center server supports the installation of the default instance of the SQL Server only.
2.
When prompted, select Install SQL Server Components, and then Database Server, Standard Edition.
3.
When prompted to specify the disk drive for the SQL Server installation path, specify the SQL database partition you
created in the section Create data partitions, on page 63.
4.
Ensure that SQL Server is set to allow Windows authentication. Create a domain account with local administrator
privileges for SQL Server to run. You should use the same logon account for all SQL Servers in your Data Center.
5.
If running a mirrored or clustered Data Center, enable SQL Server Agent.
6.
When installation is complete, apply the appropriate SQL Server service packs to the server.
SQL Server 2000 SP4
SQL Server configuration tasks

You should also perform the remaining miscellaneous SQL Server configuration tasks:
Visit the Resource Center to obtain any additional software upgrades or hotfixes and install them.
Ensure that SQL Server service is running.
From the Enterprise Manager console's Action menu, click New SQL Server Registration to register the current server.
When prompted, type in the name of the server and select Use Windows Authentication. You must use a domain
account to login into the SQL databases on the Data Center servers.
67
Support Center and Account Management Website preparation
Support Center and Account Management Website

preparation
The Data Center software includes two Web-based applications: Support Center and the Account Manager Website. Use
Support Center to administer and manage your accounts. The Account Manager Website lets users download PC Agent
software, manage their account information, and if the optional MyRoam feature is enabledretrieve files over the
Internet.
If you are using both the Connected Backup and Connected DataProtector/SV products, you can install the Account
Management Website and use the MyRoam application. If you are using the Connected DataProtector/SV product only,
ignore all references to the Account Management Website and the MyRoam application. You cannot use these applications
with the Connected DataProtector/SV Agents.
Refer to the Connected Backup Agent Deployment guide, Chapter 3: Creating Agent Configurations, beginning on page 31 for information about Agent deployment.
System requirements
Because of the added workload associated with Support Center and Account Management Website activities and because of
security considerations with a Web server, you should install Support Center and Account Management Website on a server
that is separate from the Data Center server.
Hardware requirements
Your Web server must meet the following minimum hardware requirements to run Support Center or the Account
Management Website:
Hardware
Support Center
Account Management Website
Processor
500 MHz
1 GHz
RAM
1 GB
1 GB
Operating system disk space
4 GB
4 GB
Secondary disk space
20 GB
10 GB
Computers accessing Support Center or Account Management Websitemust meet the following hardware requirements:
68
Component
Requirement
Processor
300 MHz or higher.
RAM
64 MB or higher.
Software requirements
To install the Support Center and Account Management Website software, your Web server must have the following software
installed:
Component
Requirement
Operating system
Any of the following Microsoft Windows Server operating systems:
Windows 2003 Server
Windows 2000 Server with Service Pack (SP) 4
Database
Microsoft SQL 2000 Client Networking Tools with Service Pack 4
Internet
All of the following:
Windows 2000 server: Microsoft Internet Information Server (IIS) 5.0

or later
Windows 2003 Server: Microsoft Internet Information Server (IIS)

6.0 or later
Secure Socket Layers (SSL) for running Account Management Website
Refer to Windows server installation guidelines, on page 61 for information on installing this software.
Requirements for accessing Support Center and Account Management Website

Computers accessing Support Center and Account Management Website must meet the following software requirements:
Note
You can install Support Center and Account Management Website on VMware configured to meet the
existing system requirements. You can open a browser (Internet Explorer version 6.0 or later) and run
either of those applications. Supported versions are VMware ESX 2.5.1, 2.5.2, 2.5.3, and 3.0.1.
Component
Requirement
Operating system
Windows 98, Windows ME, Windows NT, Windows 2000,

Windows XP, Windows 2003 Server, or Windows Vista with Java
version 1.5.0_11 or later
Java Virtual Machine
Current available version from Sun Microsystems. For a Windows

Vista operating system, Java version 1.5.0_11 or lataer is required.
Web browser
Internet Explorer 6.0 or later
69
Web server preparation

Your Web server must be properly set up before you can install Support Center and Account Management Website. You must
install the following software in the proper order:
Windows 2003 Server or Windows 2000 Server, Service Pack 4. Refer to Windows server installation guidelines, on
page 61 for installation information. Verify that Internet Explorer version 6.0 or higher is included in the installation.
Microsoft SQL 2000 Client Tools, Service Pack 4. Refer to SQL server, on page 66 for installation information.
Microsoft Internet Information Server version 5.0 or higher. Refer to the section below for installation information.
Note
If you are using the Microsoft IIS Lockdown tool to secure IIS, be aware that this tool is known to
cause problems in both applications in some circumstances. The URLScan filter in particular is
known to cause problems and should not be installed on the Web server, if possible. If you must use
the IIS Lockdown tool, back up your IIS state prior to using the tool so as to be able to recover should
IIS Lockdown cause problems with Support Center or Account Management Website.
After all supporting software is installed and configured, you can install Support Center and Account Management Website.
Regional settings
Make sure that both the default locale and the current locale of the Web server is set to English (United States). Use the
following steps to locate and verify this setting:
70
1.
On the Web Server, click the Start button and Settings.
2.
Select Regional Options.
3.
Verify that the current locale is English (United States).
4.
Click Set Default to verify that the default locale is also English (United States).
Enabling the MyRoam feature

What is the MyRoam application?
The MyRoam application lets users retrieve backed-up files to any computer without using the Agent user interface. After
users select the files that they want to retrieve, the Data Center creates a ZIP archive file that contains the selected files. Users
download this file and extract it to a location on their computer.
Users must log on to the Account Management Website to access the MyRoam application.
License and permission requirements

To allow users to access the MyRoam application, you must enable the MyRoam feature. You can enable the MyRoam
feature in your top-level community. You can also enable or disable this feature in individual subcommunities.
You need the following to enable the MyRoam feature in one or more communities:
If you are hosting your own Data Center, you must have a license for the MyRoam feature installed on the Data Center
server. If your current license file does not include the MyRoam feature, contact Support to purchase this license.
To enable the MyRoam feature in a community, you must have the technician permission, Allocate Licenses to SubCommunities enabled.
To enable the MyRoam feature for specific Agent configurations, you must have the technician permission, Modify
Agent Configurations enabled.
MyRoam installation
To install the MyRoam software, run Data Center Setup and select the Install Website with MyRoam option. Refer to
Installing Support Center and Account Management Website, on page 81 for procedures that explain how to install software
on the Data Center server.

To enable the MyRoam feature, you must enable it for each community and each configuration in the community that needs
access to this feature.
Note
In this release, only PC Agents support the use of the MyRoam feature.
Do the following to enable the MyRoam feature:

1.
Log on to Support Center using a technician ID that has the Allocate Licenses to Sub-Communities and Modify Agent
Configurations permissions enabled.
2.
Select the community where you want to enable the MyRoam feature.
3.
On the Community Status page, click Manage Features.
4.
On the Manage Features page, locate the row for the MyRoam feature and select Enabled in the PC Agents column.
5.
Click Save.
6.
Expand the PC Configurations node.
7.
Expand the Website Settings node and select the configuration for which you want to enable the MyRoam feature.
71
8.
Select Options.
9.
In the Account Management Options section, select the option, Allow end users to retrieve files using the
MyRoamfeature.
10. Click Finish.
72
6
INSTALLING THE DATA CENTER SOFTWARE
About this chapter
This chapter explains how to install and configure the Data Center software on servers that do not have a previous Data
Center installation. If your server has Data Center version 6.2, 7.0, or 7.1, or 7.5., or 8.x, visit the Resource Center for
instructions about upgrading your server(s) to version 8.2.
To learn about...
Refer to:
How to install the Data Center server software
Installing the software, on page 74
Verifying that the installation completed successfully
Verifying successful installation, on page 76
Tips for troubleshooting an installation that had errors
Troubleshooting Data Center, on page 79
How to install the software for Support Center and the

Account Management Website application
Installing Support Center and Account Management

Website, on page 81
Addtional Data Center configuration tasks
Configuration tasks, on page 82
73
Chapter 6/Installing the Data Center Software
Installing the software

Review installation preparation
Do not begin this section until you have completed all installation and configurations tasks in Chapter 5: Preparing for
Installation. Taking the time to fill out the Appendix B: Data Center Installation Worksheets before beginning the Data
Center installation is suggested. Having this information available can make the Data Center installation easier.
.
CAUTION
You must write down the Master Encryption Key (MEK) created during Data Center Setup. Store the
written information in a safe place. The MEK is required for reinstalling Data Center software in the
event that reinstallation is necessary.
Note
For the Setup application online Help to work correctly, we recommend running the setup
application locally. If you run the setup program remotely, the security settings in Microsoft will
prevent access to the Help system.
Running Data Center Setup

Do the following to install the Data Center software:
1.
Log on to the server as a user with administrator privileges.
2.
Ensure that the Regional Options setting in Windows Control Panel is set to English, United States. This setting is
necessary on all Data Center servers.
3.
Run the Data Center Setup executable to install a standalone Data Center or a mirrored Data Center (either one pair of
mirrored servers or an entire cluster). You can include or omit HSM, as required. You can also install Support Center
and optionally, the MyRoam application, on the Web server using Data Center Setup.
When you begin the installation process, the program performs an initial check to see whether or not the configuration
prerequisites have been met. If there are problems, you are prompted to correct them.
74
4.
If all prerequisites are met, you can continue to follow the installation step by step. If questions arise as to how to proceed
with any step, click the Help button on the window for specific information on that stage of the process.
5.
After you install the software on each of the servers in your Data Center, refer to Verifying successful installation, on
page 76 for a list of items to check to verify that installation was successful.
Back up certificate files

After installing the Data Center, y ou should back up the certificate files that the software uses. Typically, these files do not
change; therefore, you only need to back up these files once. You should back up the following PEM files:
PrivateKey.pem, located in C:\DataCenter.
Certificate.pem, located in C:\DataCenter.
dh1024.pem, located in C:\DataCenter.
CAfile.pem., located in C:\DataCenter\Configuration
Reinstallation
If, under the guidance of Support, you find it necessary to reinstall the Data Center software, it is important to understand
what it can and cannot accomplish. When reinstalling the Data Center software be aware of the following:
The same version of the software that is currently running on the Data Center must be used.
The SQL databases are not affected.
End user archive sets are not affected.
Agent configuration files are not affected.
Windows registry settings pertaining to Connected software are modified.
Data Center software application files are copied over.
Privileges given for Windows registry keys, file shares, file directories, and databases are only added to, no privileges
are taken away.
You must have the MEK created during the initial Data Center installation to complete a reinstallation of the Data Center
software.
You should not reinstall the Data Center software without the guidance of Support. There are a limited number of reasons to
perform this task, therefore Support needs to be consulted to be sure that reinstalling is the best solution.
75
Verifying successful installation

Verify components installed correctly
To verify that the Data Center installation was successful, you should verify:
The Data Center software installed correctly.
Backup Server is operating correctly.
HSM (if selected) is operating correctly.
Mirror site replication (if using a mirrored or cluster configuration) is operating correctly.
Verify successful installation of Data Center software

You should verify that the Data Center software installed correctly. Use the following steps to verify the correct installation
of the Data Center software:
1.
Log on under the same account in which you installed the Data Center software.
2.
Using the Services Control Panel, verify that the following services are on the list and are started:
Backup Server
DC Alerter (if used). If you did not configure SMTP settings during installation, this service is disabled.
Index Server
Pool Server
Replication Server (if mirrored or clustered)
Backup HSM (if used)
HSM Purge (if used)
Compactor
IIS Admin Service (running on the Support Center and Account Management Website servers)
MSSQL Server
World Wide Web Publishing Service (running on the Support Center and Account Management Website servers)
Apache Tomcat dctomcat (running on the Account Management Website server)
3.
If the services are not started, reboot the server and check again. They should start automatically when you reboot.
4.
From the Data Center Start menu, open Data Center Management Console (DCMC). If necessary, refer to DCMC Help
for instructions on adding a Data Center to DCMC. Verify that the services for your Data Center are running.
5.
In DCMC, expand the Events node and click Application. Look at the events for notification that BackupServer,
DCAlerter, PoolServer, ReplicationServer (if mirrored or clustered), IndexServer, Compactor, HSMPurge, and Backup
HSM (if used) have started.
6.
Verify that there are no warning or error events in the event log. If you have installed a mirrored pair of Data Centers,
you can see warnings from the first Data Center that it could not find its mirror. These are normal as long as they only
occurred before and during the time the mirror was installed.
Verify correct BackupServer operation

To verify correct BackupServer operation, connect to the server(s) and use a test account to perform an actual backup and
file retrieve.
76
The following procedure describes how to install a sample user account onto a client and then backup and retrieve data.
1.
Use Internet Explorer to log on to Support Center.
2.
Using Support Center, create an Agent Setup file. The Agent configuration should include rules that select a small
number of files to back up. Refer to Support Center Help for instructions that explain how to create an Agent
configuration and distribute it to clients.
3.
Use the Agent Setup file on a client computer to install the Agent and register a new account on the Data Center.
CAUTION
Do not install the Agent software on the Data Center or MyRoam servers. Doing so produces problems.
4.
If using a Server Agent, select the Backup Set tab, select a few small files to back up, and click Backup Now. You
should see that the Agent initiates a backup and that the backup completes successfully.
5.
If using a PC Agent, do the following:
6.
a.
Proceed through the installation sequence until prompted to select files for backup. Select Let me select which files
and/or directories to back up.
b.
Continue until you are asked to begin the scan, and then do so. When the scan completes, you are presented with
the Explore to pick files view in the Backup View. Select a few small files to back up, and then click Backup
Now. You should see that the Agent initiates backup and that the backup completes successfully.
After the backup completes, retrieve a file. Do either of the following:

a.
If using a Server Agent, select the Retrieve tab, select a file to retrieve and click Retrieve. When prompted to do
so, select Save all files in folder and enter a folder name in the Retrieve Options window. Then click Retrieve
again. You should see that a file retrieve is initiated and completes successfully.
b.
If using a PC Agent, select Retrieve View, pick one file to retrieve, and click Retrieve Now. Select Retrieve all
files to a different directory, specify a new folder, and click OK. You should see that a file retrieve is initiated and
completes successfully.
7.
If you are testing a standalone Data Center, uninstall the Agent from the test client using the Windows Add/Remove
Programs utility.
8.
If you are testing a mirrored Data Center do not uninstall the Agent. You can use it for other verification tasks.
77
Verify correct HSM operation

If you are using HSM, verify the correct operation of the BackupHSM and HSMPurge services by forcing a migration to be
performed on each server. Do the following:
1.
Start DCMC. Refer to DCMC Help for instructions about adding a Data Center to DCMC.
2.
If using a tape library, be sure that tapes are inserted and labeled.
3.
In DCMC, force a migration. Refer to DCMC Help for a procedure to complete this task.
4.
Use DCMC to view the Application and DCMaint event logs. A blue event indicates that a migration has been
successful. There should be no BackupHSM warning or error events in the event log.
Normally, migrations happen automatically, so it is not necessary for you to perform this manually in a production
environment.
Verify correct mirror site replication

Unless you are running a standalone Data Center, you should test your mirror by verifying replication. To test replication,
you must force a failover situation. Use the following steps to verify replication:
78
1.
Use DCMC to stop the BackupServer service on the first Data Center server. Refer to DCMC Help for specific
instructions.
2.
Using the Agent you created to verify the BackupServer operation, click Retrieve View. Select a file to retrieve, and
then click Retrieve Now (refer to the Agent Help for specific instructions). You should see that a file retrieve is initiated
and completes successfully using the mirror Data Center server.
3.
Using DCMC, restart BackupServer on the first Data Center server.
4.
Use DCMC to shut down BackupServer on the second Data Center server.
5.
Use the Agent to retrieve a file as you did in step 3. When you click Retrieve Now, you should see that a file retrieve is
initiated and completes successfully, using the mirror Data Center server. This operation confirms that the account
registration information and the data that was backed up were properly replicated between the two Data Centers.
6.
Use DCMC to restart BackupServer on the second Data Center server.
7.
Uninstall the Agent using the Windows Add/Remove Programs utility. The program you should remove is Connected
Backup or Connected DataProtector Agent.
8.
Delete the temporary folder and the files you used for the verifications.
Troubleshooting Data Center

Troubleshooting tips
The most likely cause of errors or warnings in the event log is tape library or SQL Server setup problems. You can diagnose
both sets of problems from descriptions in the event log.
If the event log reports tape library problems, make sure the tape library is properly powered on and cabled to a properly
installed differential SCSI adapter. Follow the instructions in the event log. Before calling the tape library vendor for
hardware support, we recommend trying one more time, as some problems are self-correcting.
Troubleshooting problems with BackupServer

If the Agent reports an error 109 or error 102 (with associated text), the Agent could not contact BackupServer or the
communications link between the Agent and the Data Center was not operating properly. In such a situation, use the
following suggestions:
Verify the test computer can ping the Data Center server(s).
Verify all firewalls are properly configured to allow access to port 16384 on the Data Center server(s) from the test
computer to all IP ports.
Use DCMC to verify BackupServer is running on each server.
Verify that you placed the correct IP address(es) into the test Agent configuration. If using a PC Agent, check the Agent
settings. If using a Server Agent, use the Agent Settings node in Support Center to check the Agent settings.
Check the Application and DCMaint event logs for the Data Center to see if there are any messages.
Another possible problem is that the Agent might report an Internal Server Error. Review the Data Center's Application
event log (for mirrored sites, make sure you look at the correct server).
Checking the Data Center server account

Make sure that the NT user account, under which the Data Center server is running, is a domain account with administrator
privileges. Use the following steps to determine the account under which the Data Center server is running:
1.
Open Control Panel Services.
2.
In the details pane, right-click BackupServer and click Properties from the pop-up menu.
3.
In the Log On tab, verify the account name in the This Account box is an account as described in Security requirements,
on page 60.
Troubleshooting HSM problems

When you try to label the first tape, you might encounter problems if the tape drives have not been configured properly.
If the event log reports a problem, follow the instructions in the log. Most likely, the SCSI device assignment (on the back
of the drive) does not match the physical arrangement of the tape drives in the library.
Troubleshooting attached tape library problems

If, during installation, Data Center Setup does not recognize an attached tape library, check the following to verify that the
tape library was installed and configured properly:
Check that the tape library is supported. For a list of tape libraries and tape drives supported by the Data Center software,
visit the Resource Center and refer to Supported Archive Storage Devices.
79
80
Ensure the operating system can detect the tape library, has a medium changer, and has at least one tape drive listed in
the Device Manager.
Ensure that Removable Storage Manager (RSM), a Windows Server component, is disabled for both the tape library and
for all tape drives associated with it. Refer to the Removable Storage Manager, on page 58 for instructions about
disabling RSM for tape libraries and tape drives.
Check that all tape devices start at Logical Unit Number (LUN) 0; the Data Center does not recognize tape devices on
any other LUN.
Installing Support Center and Account Management Website
Installing Support Center and Account Management

Website
Installing Support Center and the Account Management Website
You must install the Data Center first in order to map Support Center to your Data Centers databases. Support Center
connects to the Data Center using Port 80, unless you use Single Socket Layer (SSL) encryption, which requires Port 443.
To install Support Center or the Account Management Website, use the same Data Center Setup program as you did to install
the Data Center software. The setup program installs Support Center and the Account Management Website with the
MyRoam application in your Web servers root location (by default, the/inetpub/wwwroot folder).
To successfully install Support Center and Account Management Website software you must be logged into the server with
administrator privileges.
When you begin the installation process, the program performs an initial check to see whether or not the configuration
prerequisites have been met. If there are problems, you are prompted to correct them.
If all prerequisites have been met you can continue to follow the installation step by step. If questions arise as to how to
proceed with any step click the Help button on the window for specific information on that stage of the process.
Note
If your Data Center supports more than 10,000 accounts, you should not run Support Center and the
Account Management Website on the same server.
Verifying the installation

Verify that Support Center and the Account Management Website application were successfully installed by logging onto the
applications and accessing your Data Centers resources.
For Support Center, use the admin technician ID and password you created during installation to log on to Support Center
using the following URL:
http://<server name>/supportcenter/
For the MyRoam application, log onto the Account Management Website. Use the default registration URL and register an
account.
In the previous URL examples, <server name> represents the server where Support Center and the MyRoamTM
application are installed.
If you are unable to access Support Center or the MyRoam application, verify that access to the server is not blocked by
network or firewall issues. Use Control Panel Services to verify that IIS Admin Service and World Wide Web Publishing
Service are started.
81
Configuration tasks
Configuration tasks
Changing the location of the MyRoam scratch folder
When the MyRoam application receives a request to retrieve files, it sends the request to the Data Center server. The Data
Center server creates a folder for each requested download in a Scratch folder located on the Data Center server, and uses
the Scratch folder to temporarily store the rebased files required to satisfy the retrieve request.
By default, the Scratch folder is located in the Data Center installation folder (typically, C:\Data Center). You may
want to change the location of this folder to a drive that has a significant amount of available disk space, if you expect to
have a large number of MyRoam requests or you expect the requests to be large requests.
Moving the MyRoam Scratch folder

Do the following to change the location of the Scratch folder:
1.
Create a new Scratch folder in the location of your choice. The name of this folder must be Scratch.
2.
Delete or rename the original Scratch folder.
3.
Open the registry editor and change the value of the following registry key to refer to the new location:
HKEY_LOCAL_MACHINE\SOFTWARE\Connected\BackupDataCenter
4.
Restart the BackupServer service.
Configuring DCAlerter
Note
When you configure the DCAlerter service, verify that the anti-virus software on the server is not
blocking the alerts that DCAlerter sends.
DCAlerter uses email to notify designated individuals when specific events occur on the Data Center. Data Center Setup
activates this feature if you specify your SMTP mail host and an administrator email address during installation.
If you did not enter the SMTP mail host information during Data Center Setup, the DCAlerter feature is not activated. Data
Center Setup installs a default set of events for notifications.
To modify the installed settings, use DCMC. Refer to DCMC Help for a procedure to modify the installed settings.
Communities and enterprise directory integration

In addition to the basic Data Center configuration tasks, you need to create communities and technician IDs in Support
Center. You may also want to integrate the Data Center with an enterprise directory.
For information about creating communities and technician IDs, refer to your Connected Backup documentation set.
For information about integrating the Data Center with an enterprise directory, refer to Chapter 7: Integrating the Data Center
with Enterprise Directory, beginning on page 83.
82
7
INTEGRATING THE DATA CENTER WITH
ENTERPRISE DIRECTORY
About this chapter
To learn about
Refer to
How Connected Backup uses enterprise directory.
Enterprise directory overview, on page 84
The steps required to integrate a Data Center with enterprise Integration process, on page 86
directory.
The tasks required before you start the integration.
Preparing for integration, on page 87
Configuring the firewall for enterprise directory integration. Configuring your firewall, on page 89
Enabling Support Center access for enterprise directory
integration.
Enabling Support Center access, on page 90
Map the Support Center data fields to enterprise directory

fields.
Map data fields, on page 92
Confirming that the integration completed successfully.
Verifying successful enterprise directory integration, on

page 94
83
Chapter 7/Integrating the Data Center with Enterprise Directory
Enterprise directory overview

What is enterprise directory?
Enterprise directory uses Lightweight Directory Access Protocol (LDAP), a software protocol enabling you to store personal
information for every individual in your organization. This directory of information enables other applications to read
information from it for authentication and other purposes.
The Connected Backup application supports the following enterprise directory servers:
Novell eDirectory version 8.6.
Netscape iPlanet Directory Server version 4.13.
Sun ONE Directory Server version 5.1.
Microsoft Active Directory.
You can map your entire Data Center to enterprise directory, or you can map only specific communities. If you map a
community to enterprise directory all of its subcommunities will use enterprise directory as well. It is important to map a
community to enterprise directory before allowing PC Agents to register to the community.
Enterprise directory uses

Enterprise directory is used to validate Support Center technicians and optionally, to maintain end users personal data.
Integrating Connected Backup with your enterprise directory provides the following benefits:
Enables Support Center technicians to use their enterprise directory passwords for authentication.
Prevents Support Center technicians from having access to Support Center after reassignment or termination.
Allows PC Agent accounts to be authenticated with the current enterprise directory user account and password. This
means PC Agent users can use their enterprise directory credentials to register PC Agents and retrieve data.
You cannot use enterprise directory to authenticate Server Agent accounts.
Facilitates PC Account Lifecycle Management, since your PC accounts are based on your existing enterprise directory
accounts.
Enables automatic population and updating of PC accounts. This is very useful for account management, reporting, and
troubleshooting.
Existing enterprise directory servers

If you have an existing enterprise directory server, you can map the directory to the Data Center database using Support
Center. Refer to Support Center Help for the procedure to map your Data Center to the enterprise directory Data Center.
Validate Support Center technicians

Through Support Center, you can map the Data Center or specific communities to an enterprise directory. Doing so forces
Support Center technicians to use their enterprise directory user ID and password to log on to Support Center.
84
Maintain end-user personal data for PC accounts

The PC Agent and the Data Center databases use enterprise directory to obtain personal information about the user. This
relieves you of the need to enter information in multiple places. Additionally, you can use enterprise directory for security
by specifying that the users enterprise directory password must be used when retrieving files or performing a Heal with the
Agent. Users of enterprise directory-enabled accounts cannot change their personal information within the Agent. This
information can only be changed on the enterprise directory server.
Server Agents do not support the use of enterprise directory for obtaining personal information about users.
Enterprise directory management

For communities that are enterprise directory-enabled, the Data Center synchronizes user information between the enterprise
directory server and the Data Center databases. This synchronization process is performed by the LDAPSyncher application.
It is run once daily using Windows Scheduled Tasks.
If the enterprise directory server is not available, then Support Center technicians are unable to log on to Support Center, and
new PC Agent registrations are unable to be registered. Retrieve and Heal functions are also disabled for PC Agents during
this period, if your end users use account passwords.
If your organization uses Lotus Domino, please contact Connected Support for more information and assistance.
Support for Lotus Domino requires modifications to the databases that reside in the Data Center.
85
Integration process
Integration process
Integration phases
Before you start the integration, you should understand the following phases that must occur to ensure a successful
integration with enterprise directory:
1.
Preparing your IT infrastructure for integration and gathering the information you need to complete the procedures in
this document.
2.
Configuring your firewall to permit Support Center access to your enterprise directory.
3.
Enabling Support Center access.
4.
Defining the Enterprise Directory Setup Properties in Support Center, which includes mapping Support Center data
fields to corresponding enterprise directory data fields.
Complete each of the requirements and steps in one phase before continuing on to the next phase.
CAUTION
Read this entire procedure before you plan to integrate, and make sure you understand all of the
requirements and steps.
86
Preparing for integration

Preparation steps
The preparation phase involves collecting information you need to configure access to your enterprise directory and verifying
that your infrastructure meets certain requirements to support integration.
Note
An LDAP browser helps you identify and locate all of your enterprise directory accounts and
servers. During the preparation state, is it useful to use the LDAP browser to gather information and
identify the server(s) that you want to permit Support Center to access. Check to see if your
enterprise directory software includes a browser. If it does not, you can obtain a free LDAP browser
from the Internet.
Do the following to prepare for integration with enterprise directory:
1.
Install or upgrade your Data Center to the current version. For more information about installing your Data Center for
the first time refer to Chapter 6: Installing the Data Center Software, beginning on page 73. For more information about
upgrading your Data Center, visit the Resource Center.
2.
Confirm that your organizations enterprise directory is one of following supported directory services:
Novell eDirectory version 8.6
Netscape iPlanet Directory Server version 4.13
Sun One Directory Server version 5.1
Microsoft Windows 2000 Active Directory
Microsoft Windows 2003 Active Directory
3.
Verify that enterprise directory accounts exist for all users to whom you are deploying PC Agents. This also includes
users who are responsible for accessing Support Center to manage your Connected Backup user accounts. (These users
are commonly referred to as Support Center technicians.) If you plan to use enterprise directory to authenticate PC Agent
registration, this is critical. Users without enterprise directory accounts are not able to authenticate, and therefore the
Agent fails to register.
4.
Locate the enterprise directory source server that has access to all the user accounts to which you are planning to deploy
Connected Connected Backup Agents. For best results, this server should be as high up as possible in the enterprise
directory architecture. Make note of the URL for the source server; you will need it later to grant Support Center access
to your enterprise directory.
5.
Install Secure Socket Layer (SSL) certificates on each enterprise directory server that the Data Center servers and the
Support Center server will read. Using SSL is strongly recommended to prevent unauthorized interception of user
credentials.
87
6.
Create a new enterprise directory account that has read permission (and only read permission) on the enterprise directory
server that you identified in step 4. This account requires read access to all enterprise directory accounts and to your
enterprise directory schema. This user account is used by Support Center to read information from your enterprise
directory. It is used during the initial integration, and for every single communication from Support Center. Make note
of it; you will need to enter this user account and password in Support Center.
CAUTION
Use a password that is a minimum of eight characters, preferably a combination of letters and numbers.
Keep in mind that if you change this enterprise directory account password, you must also change it in
Support Center.
88
Configuring your firewall
Configuring your firewall

Configuration procedure
If your Data Center is protected by a firewall, you must configure it to permit the Data Center servers to contact your
enterprise directory servers.
Do the following to configure your firewall:
1.
Permit the Data Center server IP addresses to connect inbound through port 636 to each of the IP addresses associated
with the DNS name of your enterprise directory server.
2.
Permit outbound connections through port 16384. This is the port used by Agents to back up data to the Data Center.
3.
Permit outbound HTTPS/SSL connections through port 443. This enables technicians to connect to Support Center and
Agent users to retrieve files using the MyRoam application.
89
Enabling Support Center access

Providing access information
Enabling Support Center access involves providing Support Center the information required to make a connection to your
enterprise directory and mapping the Support Center data fields to your corresponding enterprise directory data fields.
Since data field labels differ from one enterprise directory to another, it is a good idea to contact the person responsible for
administering your enterprise directory. He or she can help determine which fields to map to the Support Center data fields.
Enter Enterprise directory setup properties

Support Center accesses your enterprise directory server or servers using the enterprise directory account you created. (Refer
to Preparing for integration, on page 87.) Support Center connects through your corporate firewall to the enterprise directory
and reads account information.
You can choose to permit the Data Center to access your enterprise directory to authenticate PC user accounts who attempt
to register DataProtector/PC accounts and retrieve backed up data. The Data Center also authenticates the technicians who
attempt to log on to Support Center to administer your Connected Backup accounts and subcommunities.
Do the following to enter the setup properties:
1.
Log in to Support Center.
2.
Locate the subcommunity that you want to integrate with your enterprise directory. The left hand navigation tree lists
your root and subcommunities. (You might need to expand your root community node to locate the subcommunity that
you want to integrate.)
3.
Click Enterprise Directory in the Community Status page to access the Enterprise Directory Setup page.
4.
In the Enterprise Directory Server URL field, type the URL of the source server. For example, a valid URL for an
Active Directory server would look similar to this:
LDAP://my.edserver.com/dc=edserver,dc=com
5.
Check the Use SSL option. This ensures that inbound Support Center connections are secure.
6.
In the Connection Login DN box, type the enterprise directory user account ID that you created for Support Center to
enable it to connect to your enterprise directory. For example, an Active Directory account would be similar to the
following:
supportcenter@edserver.com
7.
In the Connection Password box, type the account password. Note that this password is encrypted and stored on the
Data Center, and access control is limited to technicians that have the Change the Enterprise Directory user
permission. Refer to Support Center Help for more information about specific technician permissions.
8.
If you want Support Center to use your enterprise directory to authenticate all users who attempt to register a Connected
Backup account, check the Verify existence of users through Enterprise Directory option.
Note
Connected Backup only verifies against deleted PC accounts, it does not verify against disabled
accounts. Disabled accounts are treated the same as active accounts. If you create an account for a
disabled enterprise directory account, you can use Support Center to manually change the account
status to On Hold or Cancelled.
9.
90
Indicate how you want to handle users who do not pass authentication by selecting one of the following options:
Select Change the Account Status to On Hold if you want to temporarily place these accounts on hold until you
can independently verify whether or not they should be allowed to register.
Select Change the Account Status to Cancel if you want to permanently deny the account to register.
10. Continue to the Map data fields procedure to complete the integration.
91
Map data fields
Map data fields

Providing mapping information
Support Center can also read user information such as First Name, Last Name, department or other information from your
enterprise directory. To do this, you must provide Support Center with the name of the corresponding data field in your
enterprise directory. For example, you must map the Support Center Last Name field to the SN (surname) field. By mapping
the data fields, you can control which information the Support Center obtains and reads.
Default values for data fields

The following table shows a list of default values for data fields in Netscape Directory, Novell eDirectory and Microsoft
Active Directory. These are suggested values only and may not represent the values used in your enterprise directory
implementation. Consult your enterprise directory administrator for assistance with mapping data fields, if necessary.
An asterisk (*) next to a field in the following table indicates that the field is required and you must enter the name of your
corresponding enterprise directory data field.
92
Map this Support Center

field:
To this Netscape
Directory field:
To this Novell eDirectory

field:
To this Microsoft Active

Directory field:
User Class *
Inetorgperson
InetOrgPerson
User
LoginID*
Cn
CN
userPrincipalName
UniqueID*
Uid
Uid
objectGUID
First Name
GivenName
Given Name
givenName
Middle Initial
Initials
Initials
initials
Last Name
Sn
Sn
Sn
Address1
Postaladdress
Postal Address
StreetAddress
Address2
Street
Street
Street
City
City
City
State
st
ST
st
Zip
Postalcode
PostalCode
Postalcode
Country
Country
Country
Telephone
TelephoneNumber
TelephoneNumber
TelephoneNumber
Email
Mail
Mail
mail
Company
Company
Company
company
Department
departmentNumber
departmentNumber
Department
Map data fields
Mapping the data fields

Do the following to map the data fields:
1.
In the Enterprise Directory Setup page, type the name of the corresponding enterprise directory data field in each field
provided.
Note
Consult the administrator of your enterprise directory if you are unsure which field names to map to
the Support Center fields.
2.
Double-check the spelling, capitalization, and spacing of each field name that you entered.
3.
When you finish mapping fields, click Save.
93
Verifying successful enterprise directory integration
Verifying successful enterprise directory integration

Verification tasks
After completing all of the integration procedures, you should verify that the integration completed successfully and is
working as expected.
Do the following to verify that the enterprise directory integration was successful:
94
Create a new technician account in Support Center and verify that you can use that account to log into Support Center.
Refer to Connected DataProtector/SV Agent Deployment or your Connected Backup documentation set for
instructions about creating technician accounts.
Create a new test PC Agent configuration within the Support Center community that you integrated with your enterprise
directory. Refer to Support Center Help for more information on how to create a PC Agent configuration.
Deploy and install that PC Agent to an enterprise directory user account. Verify that you can install and register the new
PC Agent using the users enterprise directory user account as credentials. Refer to the Connected Backup
documentation for instructions about PC Agent deployment.
After installing a test PC Agent, confirm that the account information appears in the PC Agent. If the account
information fields in the PC Agent are blank, confirm that the fields are populated within the enterprise directory user
account.
PART III: MANAGEMENT
Chapter 8: Managing the Data Center with DCMC

Chapter 9: Installing Management Tools
Chapter 10: Event Logging
8
MANAGING THE DATA CENTER WITH DCMC
About this chapter
To learn about...
Refer to:
The Data Center Management Console application
DCMC overview, on page 98
Using the DCMC user interface
DCMC user interface, on page 100
97
Chapter 8/Managing the Data Center with DCMC
DCMC overview
DCMC overview
About the DCMC
The Data Center Management Console (DCMC) is a snap-in for the Microsoft Management Console (MMC). The DCMC
enables you to perform a variety of tasks necessary to monitor and control Data Center operations, including managing the
BackupServer, PoolServer, ReplicationServer, IndexServer, BackupHSM, HSMPurge, and Compactor.
DCMC tasks
The DCMC enables you to perform a variety of tasks necessary to monitor and control Data Center operations.
Note
You should be familiar with the Microsoft Management Console (MMC) to be able to work with the
DCMC.
For specific information and procedures on working with the DCMC, refer to the DCMC Help, which you can access through
the DCMC.
With the DCMC, you can:
Start, Pause, and Stop the Data Center services. The icons in the console tree, as well as the information in the details
pane, show whether the Data Center service is started or stopped.
View and modify properties for each Data Center service. The DCMC enables you to view default properties and
properties chosen during Data Center Setup. You can also change these properties as needed (contact Support for
guidance before changing any Data Center service properties).
Monitor multiple Data Center servers simultaneously. The DCMC enables you to monitor all of the servers in a
mirror or cluster at one time.
Manage space used in archive storage devices. You can use the DCMC to view status and monitor usage of all archive
storage devices including tape libraries and EMC Centera.
Monitor current status. Use the DCMC to monitor the status of HSM requests, operations, and tape drive availability.
View event logs and run the Windows Event Viewer. You can view event logs for Data Center operations from within
the DCMC. You can also run the Windows Event Viewer for a selected Data Center. This information is typically used
for problem diagnosis.
Access requirements
To use DCMC, log in to the Data Center server or a remote computer that has the Data Center Toolkit installed using an
account that had administrative privileges. You must also be able to access the following:
98
The HKLM\Software\Connected system Registry key.
The Service Control Manager, which allows you to start, stop, and query services.
The disk volumes attached to each machine. Data Center Setup sets these device shares to only allow access to Domain
Administrators by default. You can change this setting to allow access to other administrators.
The Event Log on each machine.
The SQL Server on the selected server. You must be able to perform read queries on SQL tables as well as inserts,
updates, deletes, and stored procedure calls. The Data Center Setup procedure grants access to the Domain
Administrators group, but you can extend these permissions to other administrators that are not part of the group.
DCMC overview
Starting DCMC
You can run the DCMC on a Data Center server or remotely, if your remote computer has the Data Center Toolkit installed.
Do either of the following to start the DCMC:
If you are working on a Data Center server, do the following:

a.
Click the Start button on the Windows taskbar.
b.
Select Programs and then select Data Center.
c.
Click Data Center Management Console.
If you are working on a remote computer that has the Data Center Toolkit installed, do the following:
a.
Click the Start button on the Windows taskbar.
b.
Select Programs and then select Data Center Toolkit.
c.
Click Data Center Management Console.
If your Data Center does not appear in the DCMC console tree, refer to DCMC Help for instructions to add it.
99
DCMC user interface
DCMC user interface

Interface description
The DCMC supports and enhances all of the standard MMC functions and interface elements. Together with the MMC, it
provides an intuitive user interface that enables you to manage various Data Center components quickly and easily.
The following example shows the DCMC interface:
Menus and toolbars
Console tree
Details pane
The DCMC interface includes:
The console tree, including DCMC-specific icons to make visualizing DCMC components easy.
The details pane, which provides information based on your selection in the console tree.
Menus and toolbars (including shortcut menus), with DCMC-specific commands.
100 Connected Backup Data Center Deployment
DCMC user interface
Console tree
The DCMC console tree (the left pane of the window) contains a view of all of the components of your Data Center, as shown
in the following example:
Console Tree
The console tree uses icons to represent each of the Data Center components. These icons are organized hierarchically to
make it easy for you to locate the components you need:
Servers are listed under the Data Center to which they belong.
Services and components are listed under the server to which they are attached.
Icons for services show whether the service is running, paused, or stopped.
If a service or component contains subcomponents, a plus sign appears to the left of the component's icon. To view the
subcomponents of a given component, expand it by clicking the plus sign (+) or double-clicking the component name.
101
DCMC user interface
Details pane
The DCMC details pane displays specific information on the item you select in the console tree (discussed in the previous
section). For example, if you select a Data Center in the console tree, the details pane shows the statuses and other
information about all of the services running on the servers connected to that Data Center.
The following example shows the DCMC details pane:
You can set the DCMC to automatically refresh the view of the details pane at set intervals. By default, the service statuses
in the DCMC are set to refresh every five minutes. You can also manually refresh the view of the details pane if you do not
want to use the automatic refresh feature.
DCMC user interface
Menus and toolbars

You access the DCMC functions and properties through toolbars and menus. The DCMC menus contain the console
commands as well as other DCMC functions.
Menus
The menus appear in the following forms:
The MMC menu bar includes the Console, Window, and Help menus. These menus are standard to MMC.
The DCMC snap-in menu bar includes the Action and View menus. These menus provide access to DCMC functions
as well as display options for the console tree and details pane.
A shortcut menu appears when you right-click items in the console tree and details pane. This menu enables you to
modify the selected item's properties or to run a command that is relevant to the selected item.
Toolbars
The DCMC contains snap-in toolbars to augment the MMC toolbar. Together, the toolbars provide quick and easy access to
console functionality and DCMC commands, which you could otherwise access through menus. The DCMC also has a
description bar, which displays the name of the current view along with the time the view was last refreshed.
Menus and tool bar example

The following example shows DCMC menus and toolbars:
MMC menu bar

DCMC snap-in menu bar
MMC toolbar
DCMC snap-in toolbar
Context popup menu
103
9
INSTALLING MANAGEMENT TOOLS
About this chapter
The Connected Backup software includes several tools that you can install on a Data Center for management purposes. It
also includes the DataBundler application, which builds account images you can use to retrieve files and restore a system
using Heal when a network connection is not available.
To learn about...
Refer to:
Available tools
Tools overview, on page 106
Installing the DataBundler application
Installing the DataBundler Application, on page 107
Installing Data Center Toolkit
Installing the Data Center Toolkit, on page 109
105
Chapter 9/Installing Management Tools
Tools overview
Tools overview
The DataBundler application
The DataBundler application is not installed on the Data Center server; you must install it separately.
The DataBundler application allows you to create an image of an Agent account that includes all of the backed-up files from
a specific date.
You can burn the account image onto a CD or DVD. For Server Agent accounts, you can also store the image on a Network
Attached Storage (NAS) device. You can configure DataBundler to automatically create account images when it receives
requests or you can build images manually.
When the DataBundler application builds an account image, it also includes a copy of the Agent application. You can use the
Agent user interface to retrieve files or restore a system using Heal from the account image. You can also use the command
line interface for these tasks.
Refer to the Connected Backup/PC Product Overview manual and the DataBundler Help for additional details about this
application.
Data Center Toolkit

Data Center Toolkit is not installed on the Data Center server; you must install it separately. Data Center Toolkit includes
several tools you can use to monitor and manage the Data Center. You can install Data Center Toolkit on as many computers
as you need. The computers on which Data Center Toolkit is installed must have network access to the Data Center server(s).
Installing the DataBundler Application

System requirements
Your computer must meet the following requirements to install DataBundler:
Windows 2003 Server Standard Edition or Windows 2000 Server with Service Pack (SP) 4 and all security hotfixes.
Free hard disk space in one volume approximately equal to twice the size of the largest account (at least 6 GB is
recommended).
Full connectivity to the Data Center server(s).
The DataBundler client should be in the same domain as the Data Center server(s) and must have high-speed LAN
access to the server(s).
SQL Server 2000 Client Networking Utility.
CD-burning hardware and software.
While burning a CD or DVD, do not use the DataBundler client for any other purpose. It is recommended that you dedicate
the client solely to CD or DVD making. If you expect to burn a large number of CDs or DVDs, install DataBundler on more
than one computer. Each DataBundler-enabled computer can only burn one CD or DVD at a time.
Before installing
Before starting the procedure in this section, add the CNTD_DataBundler user account to the Power Users group on the
computer where you plan to install the DataBundler application. Power User privileges are required to successfully burn CDs
and DVDs.
Note
If you are upgrading your Data Center from an earlier version, you can continue to use the
CNTD_CDMaker user account on the computer where you installed the DataBundler application.
Refer to the DataBundler Help for details about using this application.
DataBundler application installation

Use the following steps to install the DataBundler application:
1.
Log on to the intended DataBundler computer as an administrator.
2.
Close any open applications.
3.
Copy the DataBundler software to a convenient location on the computer. You can copy the DataBundler folder from
the folder where you installed the Data Center software or you can visit the Resource Center to download the
DataBundler software.
4.
In the DataBundler folder, double-click setup.exe.
5.
Follow the setup program instructions to complete the installation. When prompted for the folder into which the program
will be installed, specify the location of the large disk volume onto which account images are created. The installation
program creates a share for the folder, so that all members of the domain can access it.
107
DataBundler usage requirements

To use the DataBundler appplication, the following are required:
Ensure that the DataBundler application has write access to its own installation directory.
When starting the DataBundler application, use the user account you specified for the application when you installed
the Data Center (CNTD_DataBundler or CNTD_CDMaker).
The DataBundler user account must belong to the Administrators or Power Users group.
When specifying the location for the media images in the DataBundler application, use a UNC (Universal Naming
Convention) path to a directory the DataBundler application has privileges to access. If the specified path is located on
the local machine, the directory must have write permissions enabled. If the path is located on a remote machine, the
directory must be shared with write privileges enabled.
Requirements for use with 6.x Agents

If you are using a 7.x or later Data Center server and you want to use the DataBundler application to create images for 6.x
Agents , you must do the following:
1.
Install version 6.x of the CD Maker software first.
2.
Install the DataBundler application (do not uninstall the CD Maker software).
Installing the Data Center Toolkit
Installing the Data Center Toolkit

Using Data Center remotely
The Data Center installation program installs a number of utilities for Data Center maintenance on the Data Center server.
However, you can also use some of these utilities from a computer other than the Data Center server. For example, to monitor
the BackupServer status remotely. Data Center Toolkit is provided for this purpose.
Data Center Toolkit requirements

The following installation requirements apply to the Data Center Toolkit:
The Data Center Toolkit is intended for installation on a non-Data Center computer that is in the same domain as the
Data Center server(s).
Install the Data Center Toolkit on computers that have an English Windows operating system installed only.
The computer on which you install Data Center Toolkit must have network access to the Data Center server(s).
Installing the toolkit

You can install the Data Center Toolkit on as many computers as necessary. Do the following to install Data Center Toolkit
on a non-Data Center computer:
1.
Navigate to the folder where you installed the Data Center software.
If you do not have access to the Data Center software, visit the Resource Center to obtain a copy of the Data Center
Toolkit.
2.
In the folder named Toolkit, double-click setup.exe and follow the prompts.
Invoking the Data Center Toolkit

After you intall Data Center Toolkit, you can invoke any of its components by clicking Start (on the Windows taskbar), then
selecting Programs and Data Center Toolkit.
The following tools are available from the Data Center Tookit menu:
Data Center Management Console (DCMC)
HSM Disk Status
HSM Library Status
Tdate
109
10
EVENT LOGGING
About this chapter
This chapter discusses several concepts to help you understand how the Data Center logs information. This chapter contains
the following topics:
To learn about...
Refer to:
Different types of Data Center logging
Event Logging, on page 112
How the Data Center maintains the logs
Event Log Maintenance, on page 113
Trace logging
Trace Logging, on page 114
111
Chapter 10/Event Logging
Event Logging
Event Logging
Overview of event logging
Message logging allows for multiple Data Center components to follow the same standard for reporting event messages,
while providing the additional benefits of multiple levels of logging detail.
The Data Center provides the following levels of logging detail:
The Application event log
The custom DCMaint event log
The Data Center components trace log file
Visit the Resource Center for a list of event messages for each component and for information about using the event logs.
About the Application event log

By placing only the event messages intended for you to see and respond to into the Application event log, the number of
messages that you can view while managing the Data Center is significantly reduced. This feature also allows you to know
exactly when you should take action, and what type of action you should take.
If there are no errors in the Application event log, no further action is required and there is no need to look through the more
detailed DCMaint log. However, certain messages in the DCMaint log may be considered serious in some situations, so it is
a good idea to periodically scan through the DCMaint log for error and warning messages.
About the DCMaint log

If there are errors in the Application log, it might be necessary to obtain more information surrounding the error. You can
find additional information in the DCMaint log. Placing more detailed and specific messages in the DCMaint log gives you
and Support the tools for further diagnosing problems.
About trace logs

The third level of message logging lies in the ability to generate trace log files. These files provide a deeper level of logging,
thus allowing Support to adequately diagnose the potential problem. The trace logs are intended to be used only with the
advice and assistance of a qualified Support representative.
Event message hierarchy

The Data Center generates event messages in the following hierarchy:
The Application event log contains only the event messages specifically designated for the Application event log.
The DCMaint event log contains those event messages specifically designated for the DCMaint event log and repeats
the event messages designated for the Application event log.
If any trace flags are turned on for a Data Center component, the generated trace log file for that component contains
the event messages specifically designated for the trace log and the event messages designated for the DCMaint event
log for that component and the event messages designated for the Application event log for that component.
Event Log Maintenance
Event Log Maintenance

Application log maintenance
If the addition of an entry to the Application event log is found to fill it beyond its limit (for example: 50 MB), a backup of
the Application event log file will automatically be performed. The event log will then be cleared, and an Informational
message will be generated by the system into the Application event log indicating that this event log has been backed up and
cleared due to space limitations. The backup location is specified from the Windows registry setting as a string value
(LogFileDir) under the key: \\LocalMachine\Software\Connected\BackupDataCenter. Each log file name
will be generated as following: NTApp TimeStamp.evt. For example, NTApp 2003-10-01 092345.evt.
Note
In order for the Application log to be automatically saved and cleared, the Data Center must be the
source of the message that will cause the log to exceed capacity. In other words, if a different server
component such as SQL Server fills the log, then the log will not automatically be saved and will have
to be saved and cleared manually.
DCMaint log maintenance

If the DCMaint log becomes full, a backup of the log file is performed. The event log is cleared, and an informational message
is generated by the system into the Application event log indicating that the DCMaint event log has been backed up and
cleared due to space limitations. Saving the log is possible in all situations due to the fact that the DCMaint event log is only
written to by the Data Center software.
Other maintenance of the DCMaint log is performed by the system upon initialization. This includes comparison of the event
log size and age to the Windows registry values MaxSize and LogFileTime. A backup and clear is performed if either
value exceeds the defined limits. The backup location is specified in the Windows registry setting as a string value
(LogFileDir) under the key: \\LocalMachine\Software\Connected\BackupDataCenter.
Each log file name is generated as follows: DCMaint TimeStamp.evt (for example, DCMaint 2003-10-01
092345.evt).
113
Trace Logging
Trace Logging
Using Trace Logging
Trace logging provides for additional event logging when high-level troubleshooting may be required. Trace logging is not
intended to be used in normal circumstances and should typically be used under the advice and assistance of Support.
To generate those event messages that are associated with a trace log, the corresponding trace flag values must be set for the
Data Center component in the Windows registry. Visit the Resource Center for information about turning on trace logging
for specific components.
PART IV: MAINTENANCE
Chapter 11: Introduction to Data Center Maintenance

Chapter 12: Daily Maintenance
Chapter 13: Weekly Maintenance
Chapter 14: Monthly Maintenance
11
INTRODUCTION TO DATA CENTER MAINTENANCE
About this chapter
This chapter describes the types of maintenance tasks you should perform on a regular basis. This chapter contains the
following topics:
To learn about...
Refer to:
The Data Center maintenance tasks described in this manual Maintenance task overview, on page 118
117
Chapter 11/Introduction to Data Center Maintenance
Maintenance task overview
Maintenance task overview

General software and hardware maintenance
This manual describes maintenance procedures specific to the Data Center. It does not provide details about maintaining your
hardware or any software installed on the Data Center that is not part of the Connected Backup product.
For example, one practice that might be important for Data Center operations is for the System Administrator to clean the
tape drives in the tape library. This manual would explain that the task should be completed; however, it would not offer the
details as to how to clean the tape drive. Instead, this manual would refer you to the tape library vendor documentation since
different tape libraries have different cleaning procedures based on their make and model.
Antivirus Software and the Data Center

You should never run antivirus software on the Customers folder of a Data Center server (for example,
D:\Customers). Antivirus software might wrongly confuse the compressed and zipped archives on the Customers volume
with virus signatures. Most antivirus software would then isolate the archives, essentially corrupting them, since the
Data Center would no longer be able to access them. This situation would result in end-user data loss. Do not enable antivirus
scanning of the Customer folder.
Effects of archiving infected files

Archiving files that have already been infected with a virus do not affect Data Center servers. The nature of the encryption
and compression techniques used during backup inoculates the virus from affecting the servers. However, Connected Backup
software does not provide protection to end users who might recover an infected file. If a file is backed up in an infected state,
it will be recovered in such a state. Only scans of the Agent computer with antivirus software can accurately detect and
remedy these issues.
Types of maintenance tasks

This manual provides descriptions of maintenance tasks that you should perform on a daily, weekly, and monthly basis. Refer
to the following chapters for additional details:
Chapter 12: Daily Maintenance, beginning on page 119.
Chapter 13: Weekly Maintenance, beginning on page 127.
Chapter 14: Monthly Maintenance, beginning on page 137
12
DAILY MAINTENANCE
About this chapter
This chapter provides an overview of the daily maintenance tasks required for optimal Data Center performance. Because
there are different tasks that you should perform throughout the day, this chapter distinguishes between morning tasks and
afternoon tasks.
Refer to Daily maintenance checklist, on page 166, for a checklist that you can use to perform routine daily maintenance
checks.
To learn about...
Refer to:
The general maintenance tasks that you should complete

every morning
General morning tasks, on page 120
The general maintenance tasks that you should complete

every morning and afternoon
General tasks for the morning and afternoon, on page 123
The general maintenance tasks that affect tape libraries
Tasks for Data Centers using tape libraries, on page 125
119
Chapter 12/Daily Maintenance
General morning tasks

Performing daily morning tasks
The general tasks that you should perform every morning include:
Verifying the results of the Daily Automatic Procedure.
Verifying personal backups.
Check disk status and unknown disk space.
Verify that the IT alert system works.
Verify the results of the Daily Automatic Procedure

The Data Center comes with a daily maintenance script, dailymaint.sql, which runs automatically at 12:00 noon every
day except Sunday. This script carries out the following tasks:
Backs up the SQL transaction logs for the Directory and Registry databases (standalone Data Centers only).
Migrates archives to the Secondary Tape Set, if a Secondary Tape Set is being used (only on systems with Hierarchical
Storage Manager).
Calculates statistics on database size, account data totals and archive storage device totals. An archive storage device is
any component used to store data, for example, a tape library, Centera, or SAN device.
Note
If you are running a mirrored or clustered Data Center, the SQL databases are replicated between the
servers. Therefore, the databases are not backed up using the Daily Automatic Procedure. The
complete mirroring of the databases on a mirrored Data Center increases the ease and decreases the
time needed to recover from a database loss.
The script writes the results of these tasks to the dailymaint.out and sqldump.log files, which are located in the
Data Center folder. The difference between these files is that the dailymaint.out file stores the results for only the
previous day while the sqldump.log file. stores an ongoing history.
Review results of the Daily Automatic Procedure

Follow these steps to review the results of the Daily Automatic Procedure:
1.
Open either the dailymaint.out or the sqldump.log file. Both files are located in the C:\Data Center\
folder by default.
2.
Review the output file for errors that might have occurred while the maintenance script was running. The output file
should indicate the following:
3.
The Directory and Registry database transaction logs have been successfully backed up at the time specified, if you
are running a standalone Data Center.
The migration to the Secondary Tape Set was successful, if your Data Center uses a Secondary Tape Set.
Open the Application event log using the Data Center Management Console (DCMC) to verify no errors were recorded
in conjunction with the daily SQL transaction logs backup or the migration of data to the Secondary Tape Sets. You can
review the Application log by expanding the Events node and clicking Application.
If problems are reported in either the log files or the Application event log, you should visit the Resource Center for further
information on errors in the Application event log.
Note
If you are running a large standalone Data Center, you can schedule the dailymaint.sql script
to run more than once daily. Increasing the frequency can reduce the risk of data loss and decrease
the time required to recover a failed system.
Verify personal backups

Verify that personal backups work without any problems. You can perform this task using the Agent on any computer that
backs up to your Data Center.
1.
Open the Agent.
2.
Click the History tab and select several of the most recent session logs.
3.
Click View Details to display the log for the selected sessions.
4.
Check to make sure each session started and completed normally.
5.
Look for any errors or indications of connection problems. Keep in mind that these types of problems can occur from
time to time and might not indicate a persistent problem.
Check disk status and unknown disk space

Use the Disk Status tool to check your backup disk status. Do the following to check disk status:
1.
Open the Disk Status tool and enter your Data Center name in the Server box.
2.
Click Update. The Disk Status tool displays information on disk status.
3.
Make sure that all indicators are within normal parameters (within the appropriate colored indicator).
4.
Ensure that the Purge Start level has not been exceeded.
5.
Ensure that the Migrate Start level has not been exceeded.
6.
Check the unknown disk space.

The Disk Status tool displays unknown disk space in red. Files not related to the Data Center use the unknown disk
space.
Click Display to generate a list of files on the customer data volume that are not related to the Data Center. The text file
generated contains a column listing the file name and a column for the file size in bytes. You should move or delete these
files as necessary to allow more room for Data Center files.
121
Verify the IT alert system works

While you can use the DCAlerter service to send email alerts when specific event log warning or error messages are logged,
you can also use a third-party application for this function.
To verify that a third-party IT alert system is working properly, perform an end-to-end test to check the following:
Alert-causing conditions place an appropriate event in the event log.
Alert system traps the event.
Operator is alerted.
Additionally, make sure that the alert system is configured properly to respond to the various conditions that are considered
alert-worthy.
Using evttest.exe to simulate a test event

You can use the Event Test tool to simulate an event to test the alert system. Visit the Resource Center to obtain a copy of
Event Test. Do the following to use the tool to simulate an event:
1.
Copy evttest.exe to the Data Center server.
2.
Configure your alert system to react to a message with a source of DCTest1.
3.
Open a command prompt and type the following command:

evttest 3 sample error text
This command enters an error message into the event log with a source of DCTest1 and message text sample error
text. Change the error text to suit your needs.
4.
Verify that the message is in the Application event log and proper notification is made.
General tasks for the morning and afternoon

Performing morning and afternoon daily tasks
The general tasks you should perform every morning and afternoon include:
Verifying that services are running.
Examining the Windows event log.
Verifying that Support Center and the MyRoam application are running.
Check Copy on Reference and replication.
Verify that services are running

To verify that services are running, do the following:
1.
Open DCMC and expand your Data Center node in the Console tree.
Note
If you do not see your Data Center in the tree, right-click Data Centers in the Console tree pane,
and then click Add a Data Center on the shortcut menu. In the Data Centers window, select the
appropriate configuration for your Data Center and then type the Data Center or server name
(whichever is required based on your configuration selection).
2.
Click the name of the server in the Console tree to view the status of its services in the Details pane. The services include
BackupServer, DCAlerter, ReplicationServer, IndexServer, PoolServer, Compactor, BackupHSM, and HSMPurge,
(HSM services are present only when HSM is installed).
3.
If a service is not running, restart it by expanding the server name, right-clicking the service, and clicking Start Service.
If your request to start the service is unsuccessful, a message is written to the Application event log.
4.
Further verify the status of the Compactor service through the DCMaint log. Expand the Events node and click
DCMaint to view its event messages. Look for messages with a Source of Compactor.
5.
If there are warnings or errors for the Compactor service, check the Compactor log for more information. The
Compactor log is located in the Log Files folder and has the compaction date appended to the file name. If the log
is not being written, refer to Chapter 10: Event Logging for more information regarding logging and trace logs.
Examine the Windows event log

Examine the Application event log for any warnings or errors that might need attention. Do the following:
1.
Open the DCMC.
2.
Expand your Data Center node in the Console tree and then expand the server name.
3.
Expand the Events node and click Application.
4.
Look for any warnings or errors in the log window and review them for any actions you need to take. Visit the Resource
Center for more information regarding actions you need to take for error messages.
123
Verify that Support Center and the MyRoam application are running
To verify that Support Center and the MyRoam application (if your organization uses the MyRoam application for PC
Agents) are running, do the following:
1.
Verify that IIS Admin Service and WWW Publishing Service are both running. Open the Services Control Panel and
verify that the Status for both services is Started.
2.
Verify that Support Center is running. Log on to Support Center from a remote computer and perform a quick lookup
of an account. The default URL for Support Center using the following syntax:
http://servername/supportcenter
In the URL, replace servername with the name of the Web server hosting Support Center.
3.
Verify that the MyRoam application is running. Log on to the MyRoam application from a remote computer. The default
URL syntax for MyRoam is:
http://servername/MyRoam
In the URL, replace servername with the name of the Web server hosting the MyRoam application.
Check Copy on Reference and replication

Checking Copy on Reference and replication (for a mirrored Data Center) involves checking values in DCMC against
previously noted values. You should therefore keep a record of values so that you have historical data to which you can refer.
The values in DCMC are derived from several SQL tables in your database that, under normal circumstances, are usually
empty. Since these tables are empty or nearly empty, the values in DCMC should be relatively small.
Check Copy in Reference

To check Copy on Reference, do the following:
1.
Open the DCMC.
2.
Expand your Data Center node in the Console Tree pane and expand the server name.
3.
Click PoolServer. Review and note the values for SendOnce Queue and SendOnce Status. If the SendOnce Queue is
not zero, refresh the window by pressing F5. The value should decrease after a few minutes.
Check replication
Check replication on each mirrored pair of servers in the Data Center. To check replication (for mirrored and clustered Data
Centers only), do the following:
1.
Open DCMC.
2.
Expand the Data Center in the Console tree and then expand the server name.
3.
Click the ReplicationServer node.
4.
Review and note the values for Database rows to replicate and Archives to replicate. If the values are not zero, refresh
the window by pressing F5. The values should decrease after a few minutes.
Tasks for Data Centers using tape libraries

Daily tape library tasks
You should complete the following tasks on a daily basis if you are using tape libraries:
Check tape drive status and tape requests every morning and afternoon.
Remove tapes that you use for Secondary Tape Sets every morning.
Check tape drive status and tape requests

(Morning and afternoon)
If your Data Center uses a tape library for HSM, you must check that all tape drives are online. Do the following:
1.
Open the DCMC.
2.
Expand your Data Center in the Console tree and then expand the server name.
3.
Expand the BackupHSM node and click Drive Status.
4.
Look at the Status column in the Details pane.
5.
If any drives are offline, visit the Resource Center for troubleshooting information for dealing with offline tape drives.
You must also verify that requests for migration and data retrieval are being processed. Do the following:
1.
In the DCMC, expand your Data Center in the Console tree and the expand the server with which you are working.
2.
Select Current Requests under the Backup HSM node to display the requests status. Be sure to scroll all the way to
the right of the status window to see if anything is listed as suspended under the Suspended column.
3.
Refresh this view by pressing the F5 key on your keyboard, and verify that requests decrease over time.
Special circumstances
In addition to performing this task as part of your morning tasks, you should also perform it under any of the following
circumstances:
Migrations are failing.
Disk is full and not migrating.
DataCopier is running.
Restore or CD creation is taking an excessive amount of time.
Remove Secondary Tapes

(Morning Only)
If your organization makes use of Secondary Tape Sets, check the tapes to determine whether or not to remove them.
Depending on your organizations policy, you can choose to leave the tapes in the library until they are full of data or remove
them on a scheduled basis. Do the following to view the status of Secondary Tape Sets:
1.
Open DCMC.
2.
Expand your Data Center tree and then the server name.
3.
Expand the Tapes node and then Tape Sets. Locate and click Secondary migration set.
4.
In the Details pane, view the utilization information for each tape in the tape set.
125
5.
To remove a tape marked full from the library, click TapeID and click the Eject button on the tool bar.
6.
A tape that is not yet marked full must be marked full before being taken out of the library. To mark the tape full and
eject it follow these steps:
7.
a.
Right-click TapeID.
b.
Select All Tasks and click Mark Tape Full.
Click the Eject button on the toolbar.
If you remove tapes, be sure to save them in a safe location, such as in another building.
13
WEEKLY MAINTENANCE
About this chapter
This chapter provides an overview of the weekly maintenance tasks required for optimal Data Center performance. See
Weekly maintenance checklist, on page 168 for a checklist that you can use to perform routine maintenance checks.
To learn about...
Refer to:
How to verify the results of the Weekly Automatic Procedure Verify results of the Weekly Automatic Procedure, on
page 128
Backups that you should perform on a weekly basis
Backup tasks, on page 130
How to check for available disk space
Check for available disk space, on page 131
General tasks that you should perform on a weekly basis
General tasks, on page 132
Maintenance tasks related to using tape libraries
Tasks for Data Centers using tape libraries, on page 133
127
Chapter 13/Weekly Maintenance
Verify results of the Weekly Automatic Procedure

Weekly maintenance scripts
The Data Center comes with a weekly maintenance script that runs automatically at 12:00 noon every Sunday. This script
carries out the following tasks:
Performs a full backup of the SQL databases on a standalone Data Center.
Clears out the transaction log so that it does not continuously grow.
For HSM configurations with Secondary Tape Sets, migrates data to the Secondary Tape Set.
Note
If you are running a mirrored or clustered Data Center, the SQL databases are replicated between the
servers. Therefore, the databases are not backed up using the Weekly Automatic Procedure. The
complete mirroring of the databases on a mirrored Data Center increases the ease and decreases the
time needed to recover from a database loss.
The name of the script file depends on the media to which you back up your databases:
The weeklymainttape.sql script performs the database backup to tape and is automatically used if there is a local
tape device for backups.
The weeklymaintdisk.sql script performs the database backup to disk and is automatically used if there is no
local tape device for backups.
Both of these files are installed during Data Center installation; however, you should make sure your task scheduler is set to
run the specific file that applies to your configuration.
CAUTION
A weekly, full database backup to disk can consume as much disk space to store the backup files as is
consumed by the actual database. If you perform a backup to disk, then you should use some other utility
to copy the backup files to another medium. Be particularly careful not to allow a new full backup to
overwrite a previous full backup in case the new backup should fail.
You should not backup your SQL databases to the same disk partition as the original SQL databases. If
you were to experience problems with the disk partition, you would risk losing both the databases and
the backups.
Review results
The results of the weekly maintenance script are written to the weeklymaint.out and sqldump.log files, which are
located in the Data Center folder. The difference between these files is that the results for only the previous week are
stored in the weeklymaint.out file, while an ongoing history is stored in the sqldump.log file. Both files are located
in the C:\Data Center folder by default.
Review these output files to verify the following:
The database backup was successful and no errors were reported.
The Master, Model, MSDB, Directory and Registry databases have successfully been backed up at the time specified,
if you are running a standalone Data Center.
The Directory and Registry database transaction logs have successfully been backed up at the time specified, if you are
running a standalone Data Center.
The start and end times written at the start and end of the output file are consistent with the actual start and end times of
the backups.
Review the Application event log

If an output file reports problems with the database backup, you should look at the Application event log for messages
pertaining to the backup and additional information. To view the Application event log:
1.
Open the DCMC.
2.
Expand the Data Center in the Console tree and expand the server name.
3.
Note
If you are running a large standalone Data Center, you can schedule the weeklymaint.sql script
to run more often. Increasing the frequency can reduce the risk of data loss and decrease the time
required to recover a failed system.
129
Backup tasks
Backup tasks
Overview of tasks
During weekly maintenance, you should back up:
Support Center reports
Agent configurations
Windows registry key
PEM files
Rotate tapes for the SQL database backups
Back up Support Center reports

Back up your Support Center reports each week so that you always have a set available if a disaster should occur. This is an
important step whether Support Center is running on the Data Center server or on a separate Web server. The default location
for the reports is c:\Inetpub\wwwroot\SupportCenter. Back up the reports using any method you prefer. For
example, copy to another server or copy to tape.
Back up Agent configurations

Back up your Agent configurations each week so that you do not have to recreate them if some disaster should occur. The
default location for Agent configurations is c:\Data Center\Configuration$\. Back up the Agent configurations
using any method you prefer. For example, copy to another server or copy to tape.
Back up the Connected Windows registry key

Back up the following Windows registry key each week:
HKEY_LOCAL_MACHINE\SOFTWARE\Connected\
Changes you made to values in this registry key will be lost during a disaster or if reinstallation of the Data Center software
becomes necessary.
It is particularly important to back up the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Connected\Keys
To back up this registry key, you must log on to the Data Center server with Administrator privileges and give yourself read
and write permissions for the key. Use the Security menu in RegEdt32 to give yourself the proper permissions.
Rotate database backup tapes

(for SQL Database Backups to Tape)
If you are running a standalone Data Center and perform your SQL database backups to tape, you should remove the backup
tape and place it in a safe place after every backup. Rotate the backup tapes approximately every four weeks so that you
always have the most recent backups from the previous few weeks available on tape.
Check for available disk space
Check for available disk space

Checking for disk space
Each week, check the available disk space for the following volumes to ensure the disk has sufficient capacity:
\Customers folder
SQL database
SQL database backup
Customers folder
The Customers folder is where end-user data is written. If you are running a disk-only configuration, use Windows
Explorer to check the available disk space on all Customers volumes.
If you are running a Data Center with HSM, use the Disk Status tool to check for available disk space on the Customers
volume. Refer to the Connected Backup/PC Product Overview manual for information about the Disk Status tool.
SQL database
The SQL database continues to grow throughout the life of the Data Center. Do the following to check for available disk
space:
1.
Open SQL Server Enterprise Manager.
2.
In the left pane, expand Microsoft SQL Servers down to and including your Data Center server.
3.
Expand the Databases folder and click Directory.
4.
To activate the Taskpad view, right-click Directory and then click View. Select Taskpad from the shortcut menu. The
Taskpad view displays three sections: Database, Maintenance and Space allocated.
5.
In the Space allocated section, note the space used by both the data and the transaction logs. The unused space plus free
space on the disk partition should be at least two times the size of the data and transaction logs.
6.
Calculate how much the used disk space grew since the previous weekly check to assess how much disk space the
databases need over the next ten weeks or so.
CAUTION
You should not back up your SQL databases to the same disk partition as the original SQL databases. If
you were to experience problems with the disk partition for any reason, you would risk losing both the
databases and the backups.
SQL database backups

If you are using a standalone Data Center and backup your SQL databases to disk rather than to tape, you should check the
SQL database backup volume for available disk space on a weekly basis. You should also consider moving the SQL backups
from the disk to a tape or other media. This enables you to have multiple backups to restore from, if it becomes necessary.
131
General tasks
General tasks
Check System Time Synchronization
If you are using a mirrored or clustered configuration, the two servers that comprise a mirrored pair should not differ in time
by more than 30 seconds. Check the time on each server and correct any discrepancies that might exist.
To check the system time:
1.
Open the Microsoft SQL Server Query Analyzer.
2.
Open a connection to both mirrored servers in the same window.
3.
Run select getdate()in each server's window.
Note
You should also perform this time check after adding any new hardware to either server and after
changes in Standard or Daylight Savings Time.
Check for Updates

Occasionally there are times when a software bug is significant enough to warrant a software update. To obtain the latest
software updates, visit the Resource Center.
Service packs are full releases of Connected Backup and therefore require full upgrade of the Data Center and Agent
software. Service packs include all hotfixes released since the last major release or service pack.

Check tapes
As backups are performed to your Data Center, you must ensure that you have adequate unused storage capacity in your tape
library. You must also keep spare tapes on hand should a tape in the library need to be replaced. The number of tapes you
need depends on server usage, growth history, and planned expansion.
Use the following guidelines when managing tapes:
Keep a record of tape consumption (by day or by week).
Based upon your tape consumption measurements, keep at least two weeks worth of tapes available for growth.
Keep at least two spare tapes in addition to the two week reserve in order to replace a bad tape, if necessary.
Keep 1 times as many tape labels as you have tapes.
Checking blank tapes

Initially, your tape library should be adequately stocked to accommodate the number of end-user accounts you planned for
during capacity planning, and all of the tapes in your tape library should be blank. As you add end-user accounts, you can
determine the growth rate of the server by examining how many blank tapes are used each day or each week.
Use the following steps to view information regarding blank tapes:
1.
Open DCMC.
2.
3.
Expand the Tapes node and click Blank Tapes.
4.
Verify that there are an adequate number of labeled blank tapes to handle normal tape usage.
Checking tape use

Use the following steps to view tape usage information:
1.
Open DCMC.
2.
3.
Expand the Tapes node and click Tape Details.
4.
Check Mount Count for any tapes with excessive mounts. You might have to retire these tapes before they start causing
errors.
5.
Check Date of birth, by scrolling to the right, for any relatively old tapes that might need to be retired.
Note
What is a high mount count and how old is old? These are difficult to define. If you notice a specific
tape causing warnings or errors in the Application event log, it is often an indication of a tape going
or gone bad. Pay particular attention to these tapes in the steps above. Also, check with your tape
media vendor for their qualification of high mount count and the life expectancy of a tape.
Checking recyclable tapes

The Data Center automatically checks for and recycles tapes. A tape is deemed ready for recycling when both of the
following conditions exist:
133
All data on the tape is expired.
The tape is marked full.
Before a tape is recycled automatically, a cool-off period of seven days is required. Use DCMC to view recyclable tapes. The
following actions are taken on the tape when recycled:
The tape is relabeled.
The Directory database is cleared of old information regarding the tape.
The starting point for write operations is moved back to the beginning of the tape.
Note
Let tapes cool off after they become recyclable, so that you could use them in case of a
disaster requiring database restoration. If the tapes have been relabeled, the data required to
rebuild the Data Center will be lost. A cooling-off period can last from one week up to a month
prior to recycling.
Managing cleaning tapes

Use the following guidelines for ensuring you have an adequate supply of cleaning tapes:
Review your cleaning schedule and the number of cleaning cycles left on your cleaning tapes.
Keep on hand enough cleaning tapes to last for one month of cleaning cycles.
If you only need one cleaning tape per month, keep a spare cleaning tape on hand just in case you should have a problem
with the first tape.
Check tape library slots

You should check the number of open slots every week. If you use Secondary Tape Sets, be sure to take out full tapes and
store them appropriately. When the percentage of open tape slots declines to 20% or less, you should perform an analysis of
the system to verify how much data is processed in daily and how much data is being processed out by Compactor. This
analysis helps you to determine if more tape slots are necessary for the Data Center in the long run.
Ensure migration events are successful

Check to make sure that successful migrations are occurring on a regular basis. To perform this task:
1.
Open DCMC.
2.
3.
Expand the Events node and then Application.
4.
Perform a Find using Migration as the description. Read the event messages that you receive to determine the
success of the migrations.
5.
If you find unsuccessful migrations, visit the Resource Center for more information about how to respond to the error
events.
Check tape and tape drive health

The relative health of a library tape and tape drive is related to the number of hard errors reported. The errors are reported in
the event log and are also totaled in the Directory database. Hard errors can indicate tape or drive failures before an
irreversible data loss. To view a total of these errors per drive, use the Detect Tape and Tape Drive Errors.sql
script. Visit the Resource Center to obtain a copy of this script, if necessary.
Another indicator of tape drive health is the number of times the cleaning light for a tape drive is turned on. The cleaning
light turns itself on if it is determined that the tape drive needs cleaning. If this is occurring frequently, it can indicate a
problem. The frequency of the cleaning light turning on is also totaled in the Directory database. The Tape Drive
Cleaning Light On.sql script enables you to view a summary of this action. Visit the Resource Center to obtain a
copy of the script, if necessary. Instructions for installing, running, and reading the results of both scripts are included in the
script.
135
14
MONTHLY MAINTENANCE
About this chapter
This chapter provides an overview of the maintenance tasks required for optimal Data Center performance. Refer to Monthly
maintenance checklist, on page 170 for a checklist that you can use to perform routine maintenance tasks.
To learn about...
Refer to:
The maintenance tasks for the databases
Database maintenance, on page 138
Maintenance tasks for account management
Account management, on page 141
Evaluating the current storage capacity on the Data Center
Evaluate current Data Center capacity, on page 144
Verifying that you are using the most current firmware on the Verify firmware is current, on page 146
Data Center server
Check the software licensing for the Data Center
Check software licensing, on page 147
Maintenance tasks for the event log
Saving and clearing the event log, on page 150
Maintenance tasks for tape libraries and drives
Clean library and tape drives, on page 152
Verifying your record keeping
Verify that record keeping is current, on page 153
137
Chapter 14/Monthly Maintenance
Database maintenance
Performing daily and weekly maintenance
As it does with the daily and weekly maintenance scripts, the Data Center comes with a monthly maintenance script to
perform database maintenance. This monthly script runs the DBCC utility that comes with SQL Server (using the dbcc
checkdb query) for each of the Data Center databases. In turn, the DBCC utility checks the databases for the following:
Logical and physical consistency exists in the database.
Indexes and data pages in tables are correctly linked.
Data and index pages are consistent against corresponding extent structures.
Indexes are in proper order, all pointers are consistent, data information on each page is reasonable, and page offsets are
reasonable.
When you run the monthly maintenance script, you must perform specific tasks based on your Data Center configuration.
For this reason, the Data Center Setup program does not add the monthly script to the Windows Scheduler (unlike the daily
and weekly scripts, which are set up to run automatically on a schedule). You therefore must run the script manually.
You can run the script using SQL Query Analyzer. The script's file name is dbmaint.sql, and it is located in the
Data Center folder.
Before you run the script, however, be sure to read the rest of this section for specific guidelines and instructions based
on your Data Center configuration. The rest of the section describes the procedure step-by-step so that you can follow along.
It also provides additional information based on your specific configuration.
Standalone Data Center

On a standalone Data Center a service outage occurs during database maintenance because you must stop the BackupServer
service. You should warn your end users in advance of performing this procedure. When you follow this procedure, notice
references to Server 1. Server 1 represents the name of your Data Center server. Ignore references to Server 2.
Mirrored Data Center

Be sure to keep one server running while you perform database maintenance on the other server. That way you won't create
a service outage. When you finish the procedure for the first server, you can then repeat the procedure for the mirror. When
you follow the procedure, be sure to note which server each step applies to on the mirrored pair: Server 1 refers to the server
that you are bringing down for maintenance. Server 2 refers to the server that remains operational. Server 1 and Server 2
represent the names of your Data Center servers.
Clustered Data Center

For the purposes of this database maintenance procedure, the mirrored server pairs in a clustered Data Center are treated as
separate Data Centers. You therefore perform the maintenance on one Data Center in the cluster (one mirrored pair) and then
perform it again for the next Data Center in the cluster (the next mirrored pair).You can save time by initiating this procedure
on all Data Centers in the cluster sequentially. But it is important to perform this procedure in the correct order. You should
perform the procedure on one side of the cluster (such as the primary side) and then perform the procedure on the mirrored
side.
Procedure
To perform database maintenance, you must do the all of the following tasks in order:
1.
Prepare the mirrored server (for mirrored and clustered Data Centers).
2.
Stop the server for maintenance.
3.
Run maintenance SQL scripts.
4.
Restart the server.
1. Prepare the mirrored server

Use the following steps to prepare the mirrored server (for mirrored pairs):
1.
Open DCMC.
2.
Select Server 2 from the console tree.
3.
Verify that services are running for Server 2. For more information on verifying that services are running, refer to Verify
that services are running, on page 123.
2. Stop the server

Use the following steps to stop the server for maintenance:
1.
In the DCMC, expand your Data Center in the Console tree and then expand the server name.
2.
Right-click BackupServer and click Pause Service.
3.
Right-click DCAlerter and click Stop Service.
4.
Right-click ReplicationServer and click Stop Service.
5.
Right-click PoolServer and click Stop Service.
6.
Right-click IndexServer and click Stop Service.
7.
Right-click BackupHSM and click Stop Service, if you are using HSM.
8.
Right-click HSMPurge and click Stop Service, if you are using HSM.
9.
Right-click Compactor and click Stop Service.
10. Verify that any end-user retrieve requests for Server 1 are complete by right-clicking BackupServer, selecting All
Tasks, and clicking Log Session Statuses. Expand the Events node and click Application. Verify that there are no enduser retrieve requests in progress.
11. When all end-user retrieve requests are complete, right-click BackupServer and click Stop Service.
3. Run maintenance SQL scripts

Use the following steps to run maintenance SQL scripts:
1.
Verify that the Compactor service is not running. If it is still running, end the process or wait until the process finishes.
2.
Open Microsoft SQL Server Query Analyzer and connect to Server 1.
3.
If you are running a standalone Data Center and use a tape system for your database backups, open the SQL script file
weeklymainttape.sql. Otherwise, open the SQL script file weeklymaintdisk.sql. Both files are located in the
Data Center folder, default location c:\Data Center.
4.
Click the execute button to run the SQL script. The system performs a backup of the SQL databases and a migration to
Secondary Tape Sets (for HSM systems with Secondary Tape Sets). For more information refer to Verify results of the
Weekly Automatic Procedure, on page 128.
5.
When the SQL script is finished, run the SQL script file dbmaint.sql, which is also located in the Data Center folder.
Depending on the size of your databases, the SQL script could take minutes or hours.
139
4. Restart the server

Use the following steps to restart the server:
1.
2.
3.
When the SQL script is finished, use the following steps to restart the services for Server 1:
a.
Open DCMC.
b.
Expand Server 1 in the console tree.
c.
Right-click each service and select Continue Service.
Verify that Agents can connect to Server 1:

a.
Right-click BackupServer, select All Tasks. and click Log Session Statuses.
b.
Verify that there are backups or retrieves in progress.

a.
Use the Disk Status tool to check the available free space on the database volume. If the free space on the volume
is 100MB or less, contact Support. Do not continue until you complete this step successfully.
b.
Repeat all steps for Server 2.
Account management
Account management
Accounts to remove
As time goes by the Data Center can become cluttered with abandoned accounts. This clutter can take up precious space in
the databases and in archive storage. These abandoned accounts also use up seats in the Data Center license.
To keep clutter on the Data Center to a minimum, look for the following types of accounts on a monthly basis:
Unowned accounts
Unsupported Agent versions
Duplicate accounts
Inactive accounts
Heavy hitters
Invalid accounts
Unowned accounts
An unowned account is an account where ownership cannot be determined. This type of account is created when a name,
email, telephone or other identifying information is not entered during the Agent setup and registration process.
If you can obtain information for the account, enter it using Support Center. Or you can choose to cancel the account.
In time, Compactor removes it from the Data Center. Visit the Resource Center to obtain a SQL script that you can use to
find unowned accounts on the Data Center.
Unsupported Agent versions

An unsupported Agent version is an account running a version of the Agent software that your organization no longer
chooses to support. Your organization can choose to discontinue support for an Agent version for several reasons:
Reduce support costs and Help Desk calls.
The version is no longer supported.
Their are known issues with the version.
When you identify the accounts, you should upgrade the version by whichever upgrade method your organization employs.
Visit the Resource Center to obtain a SQL script that you can use to find accounts running unsupported Agent versions on
the Data Center.
141
Account management
Duplicate accounts
A duplicate account is an account that is unused because there are two accounts installed on the same Agent computer.
Duplicate accounts are commonly caused by an issue with the account recovery process. Sometimes a user is confused during
the account recovery process and creates a new account rather than recovering the current account. A new account might be
intentionally created because the user was unaware of the account recovery process or there might have been an error during
the process, forcing the user to start a new account. Duplicate accounts cannot be easily identified using an automated
procedure. However the key factors to examine are as follows:
1.
Find multiple accounts registered for an individual email address or name.
2.
Determine if the accounts identified in step 1 have the same computer name.
3.
Verify that the last backup activity for one account ends, and a new account is registered shortly thereafter.
4.
Verify that the new account determined in step 3 has current backup activity and the other account does not.
Visit the Resource Center to obtain a SQL script that you can use to find accounts with the same email address on the
Data Center.
Inactive accounts
An inactive account is an account that has had no activity recorded over an extended period of time. An account can become
inactive through:
Attrition
Duplicate account
Backup schedule no longer active
Agent removed from the computer
For best results, choose an account inactivity threshold time frame. For example, if an account has not performed a backup
in the past 90 days, it is considered inactive. The policy created should be published for end users and Help Desk
representatives and should also accommodate end users on extended absence.
Two SQL scripts are available that you can use to identify inactive accounts. One SQL script identifies accounts with no
activity in the past 90 days and the other SQL script identifies accounts with no activity at all. Your organization can choose
to cancel these accounts or notify them that they have not backed up recently. Visit the Resource Center to obtain copies of
these SQL scripts.
Heavy hitters
The heavy hitters reports are Support Center reports that examine the amount of data that each account is backing up to the
Data Center. The reports have the following names:
Heavy Hitters
Heavy Hitters Cumulative
Both reports are located in the Reports node. Refer to Support Center Help for information about running and viewing the
reports.
If an account is backing up a large amount of data on a regular basis, this often indicates that the account is backing up
unnecessary data. Large backups put undue stress on the Data Center server, HSM (if used), and the SQL databases.
It is up to each individual organization to determine what constitutes heavy usage and how to manage heavy hitters. You
should take steps to reduce or eliminate the load they are putting on the Data Center. You can use the results from the heavy
hitters reports to decide if there are specific types of data you should exclude from backups or to contact accounts about
inordinately large backups.
Account management
Invalid accounts
An invalid account is an account that is unusable. This can occur from a failed registration. The failure could have been from
a network error or some other failure that prevented the system from completing its registration. Occurrences of this type
should be rare. Visit the Resource Center to obtain a SQL script that you can use to find invalid accounts on the Data Center.
143
Evaluate current Data Center capacity

Monitoring capacity
You should also evaluate Data Center capacity on a monthly basis and during specific phases of deployment during your
initial deployment.
As you deploy the Agent to more computers, you might find that you require changes to your original hardware and software
configuration. For example, more backup data from an increase in accounts might require you to add more storage space on
your server(s).
You should check your Data Center capacity more frequently for an aggressive deployment than for a slow deployment.
To determine when to check capacity, you might want to use time intervals based on specific milestones in your deployment.
For example, you could check capacity when you reach 50%, 60%, 75%, and 90% of your installed projected capacity. Visit
the Resource Center to obtain copies of SQL scripts that you can use for capacity planning
You should perform certain system checks on a monthly basis to assess your current hardware and software requirements for
the following:
CPU
RAM
SQL database disk partition
Library slots, tapes, and labels (for HSM)
CPU
For best performance, use a one gigahertz or higher Pentium class processor for your Data Center servers. Refer to
Chapter 4: Sizing Your Data Center, beginning on page 43 manual for more information about Data Center sizing
requirements. If the CPU is over utilized, you can add additional processors or upgrade the existing processors to improve
performance.
CPU utilization is generally easy to detect as a potential bottleneck to Data Center performance, but it is often harder to
address than other potential limitations without a complete hardware upgrade. Certain processes (particularly compaction),
however, can consume a large amount of CPU resources. During these peak periods, you should measure CPU utilization.
You can evaluate your server's CPU utilization using the System Monitor feature of your Windows Performance utility. You
should examine the following items for their averages during peak activity:
Average CPU utilization: Processor\ % Processor Time > 80% indicates heavy CPU utilization.
Generally, a healthy CPU has peaks and valleys of utilization, with many of the peaks reaching 100%. This means that
average processor activity during peak times is actually a better reflection of true performance than the peaks
themselves. The average CPU utilization should be under 85%.
System processor queue length: System\ Processor Queue Length > 2 per CPU indicates that CPUs are overwhelmed
and are queuing up requests.
Generally, there should be no more than the number of processors x 2 as an average queue.
If you find the CPU to be under performing, replace the existing CPU(s) with faster CPU(s) rather than more CPUs. This
recommendation is due to the Windows performance overhead incurred with multiprocessing.
RAM
Your server's RAM, along with disk space, is a likely culprit for being a system bottleneck. Unlike disk or CPU usage, you
measure RAM usage by a more indirect means because Microsoft SQL Server, the primary user of RAM in the Data Center,
consistently utilizes close to 100% of memory resources as it attempts to cache as much of the database in memory as
possible.
The primary tool for determining if RAM is a limiting factor in system performance is the System Monitor feature of the
Windows Performance utility. You should examine the following items for their averages during peak activity:
Number of times Windows is going to disk: Memory\Pages/sec > 0 indicates that Windows is going to disk frequently,
costing disk I/O and CPU resources.
Keeping this value close to zero reduces performance problems incurred by going to disk. You can resolve this issue by
adding more RAM to your system.
Number of times per second that Windows has read from the paging file: Memory\Page Reads/sec > 5 indicates that you
might need to add more RAM to resolve a bottleneck in your system.
SQL database disk partition

Check the database disk partition on a weekly basis. You should also include this check in your regular assessments for
evaluating all factors regarding your Data Center capacity. For more information, refer to Check for available disk space, on
page 131.
Library slots, tapes, and labels

Check library slots, tapes, and labels on a weekly basis. You should also include this check in your regular assessments for
evaluating all factors regarding your Data Center capacity. For more information, refer to Check tapes, on page 133 and
Check tape library slots, on page 134
If you configured your Data Center to use HSM, you should evaluate the capacity of your tape library. If you find you are
storing too much data for your tape library, there are two options to consider to create more space. Reevaluating the file
selection rules and file retention policies can decrease the amount of data backed up and stored. Another option is to add
more tape storage capacity, since the solution does support the use of multiple tape libraries.
145
Verify firmware is current
Verify firmware is current

Check with your manufacturer
Occasionally, hardware manufacturers release firmware fixes, and updates for bugs and other issues. Check with the
manufacturer of each hardware component in your Data Center to see if there are firmware updates for your equipment.
Check software licensing

Updating licensing
You initially purchased a set number of licenses for the Data Center. There are a number of reasons for updating the
Data Center license, including:
You want to deploy the Agent to additional computers.
You want to deploy a new Agent type (PC or server).
The network interface card (NIC) on the Data Center changed.
You installed an additional NIC.
Access to some features is now controlled through licensing.
Every server in a mirrored or clustered Data Center must have the same license. That is, every server must be licensed for
the same features and the same number of end-user accounts.
Deployment to Additional Accounts

If you plan to deploy the Agent to more computers, consider when you want to add more licenses. Follow these steps to see
how many licenses are currently available:
1.
Open the DCMC.
2.
Expand the Data Center in the Console tree and expand the primary Data Center server.
3.
4.
Look or search for the message with a source of License Manager. Event ID 9507 displays the number of seats and
features purchased.
5.
In Support Center, create a report that displays the number of active accounts.
6.
Refer to Requesting a new license, on page 149 to request a new license, if necessary.
New NIC on the Data Center

Each license is created for a specific Data Center server based on the HostID of the network interface card (NIC). A new
license is needed if the Host ID on the server changes (a new NIC is installed). If you have installed a new NIC, follow these
steps to determine the new HostID associated with the new card:
1.
Open a command prompt window.
2.
Change folder to the Data Center folder. By default, this is C:\Data Center.
147
3.
Type hostid.
The following is an example of the system output:
The HostID for the current machine is:
0050dad5a9e6
Note
You must enable NetBios over TCP/IP on the Data Center servers. The HostID.exe program
requires this configuration to properly verify the Data Center server's MAC address against the Data
Center license.
4.
Refer to Requesting a new license, on page 149 for information about requesting your new license.
An additional NIC is installed

The Data Center license is based on the HostID(s) of the network interface card(s) (NICs), up to four. If your Data Center
server uses multiple NICs, the license file needs to be aware of each NIC. If you are adding a NIC, you need to follow these
steps to determine all of the HostIDs:
1.
Open a command prompt window.
2.
Change the folder to the Data Center folder. By default, this is C:\Data Center.
3.
Type hostid.
The following is an example of the system output:
The HostID for the current machine is:
0050dad5a9e6
0026fal7b9r5
0123kel8a6w2
0475der9n3y5
Note
You must enable NetBios over TCP/IP on the Data Center servers. The HostID.exe program
requires this configuration to properly verify the Data Center server's MAC address against the Data
Center license.
4.
Record your Host IDs in the table Licensing, on page 160.
5.
Refer to Requesting a new license, on page 149 for information about requesting your new license.
Features offered to end users changed

If your organization chooses to add or remove features, you must obtain a new license to activate or deactivate features.
Requesting a new license

Use the following steps to request a new license:
1.
In a Web browser, access the following URL and submit the appropriate information:
http://www.ironmountain.com/US/support/licensedsoftware.asp
2.
After the information is processed, you will receive an email with a new license.dat file and instructions for
installation.
149
The Event Log
The Event Log

Saving and clearing the event log
Windows event logs record software, hardware, and system information. They provide valuable diagnostic information in
case of system failure. You should keep a record of your event logs to help diagnose problems if you should experience any
type of system failure.
The Data Center automatically saves and clears the Application log, but only if the Data Center is the application that fills
it. If another application, such as SQL Server, fills the log, then the Data Center does not automatically save and clear it.
Therefore, you should manually save and clear the Application log. The Data Center never saves and clears the System and
Security logs automatically.
Keep a record of at least three months of event logs. Over time, these logs might become full. You should save and clear the
current Application and System logs. When the Data Center detects that DCMaint is full, it automatically saves the log to
the Log Files folder. The Data Center then automatically clears the log.
Do the following to save and clear the event logs:
1.
Open the DCMC.
2.
Expand the Data Center Console tree and expand the server name.
3.
4.
Click the Action menu and click Start Event Viewer. The Windows Event Viewer opens.
5.
In the right pane click Application.
6.
From the Action menu click Save Log File As.
7.
In the Save Application Log As window navigate to the \Log Files folder (by default this folder is located on
the same drive as the \Customers folder).
8.
Name the log file, ensuring that it has a unique name that clearly identifies the log file type and time period of events
contained in the log. For example, you could use the following name to indicate the saved file is the Application event
log for the month of April, 2005:
App9_1_02_to_9_30_02.evt
9.
Repeat the steps in this procedure for the DCMaint and System event logs.
Preventing overwriting of logs

You should configure Windows to not overwrite log files. To do so, follow these steps:
1.
Open the Windows Events Viewer.
2.
Click one of the three logs (Application, DCMaint, or System).
3.
Select Properties on the Actions menu.
4.
In the Log Properties window, select Do not overwrite events.
5.
Click OK.
6.
Repeat these steps for each of the three logs.
The Event Log
Increasing the log file size

Because the Data Center does not automatically save and clear the Application event log if it is filled by another application,
you can increase the maximum log size.
Do the following to increase the log size to 50 MB:
1.
Open the Windows Events Viewer.
2.
Click Application.
3.
Select Properties on the Actions menu.
4.
In the Log Size section, under the General tab, modify the Maximum Log Size to 50 MB by either clicking the up
arrow or typing in 50000. You can set this number higher. The recommended value is 50 MB.
5.
Click OK.
151
Clean library and tape drives
Clean library and tape drives

Clean tape library and drives
If you are using a tape library with your Data Center, you must clean the library and its tape drives. Tape libraries and tape
drives require occasional cleaning in order to remove accumulated dust and contamination on the drive read/write head.
Various types of libraries, drives and media each have their own maintenance schedule.
You should consult your tape library documentation to determine how frequently you should clean the library and the drives,
and how to perform the cleaning function. In addition to your tape library manufacturer's guidelines, use the following
guidelines:
Use DCMC to stop the HSM services. These include: BackupHSM and HSMPurge.
Make sure you have an adequate supply of cleaning tapes for the number of tape drives in your library.
Cleaning tapes can only be used a fixed number of times before they should be discarded. Note each time you use a
cleaning tape, and discard them immediately after their last use.
Record the date of the last cleaning for each drive in a log. A drive that requires more frequent cleaning indicates that it
might need to be serviced.
Clean SQL database backup tape drive

Clean the tape drive used for SQL database backups. Many types of tape drives exist, each with its own maintenance
schedule. You should consult your tape drive documentation to determine how frequently you should clean the drive and how
to perform the cleaning function.
Record Keeping
Record Keeping
Verify that record keeping is current
Every month you should perform the following tasks to make sure that your Data Center record keeping is current:
Examine the daily and weekly scheduled maintenance records to ensure that maintenance is being performed and
recorded.
Compile the records of system usage (such as number of end-user accounts, backups, retrieves, and so forth) and publish
them as appropriate for your organization.
Examine the records of service availability. Compile and publish service availability statistics. You should also compile
and publish these statistics on a rolling twelve-month basis.
Examine the records of hardware maintenance, system software upgrades, and Data Center performed procedures to
verify that records are being kept properly.
Examine the training records of Data Center operators to ensure that your entire staff is properly trained.
Verify that your vendor support contracts are up-to-date.
153
PART V: APPENDICES
Appendix A: Data Center Specification Worksheet

Appendix B: Data Center Installation Worksheets
Appendix C: Maintenance Checklists
A
Data Center Specification Worksheet
About this appendix
Use this appendix to track information regarding your Data Center. Update the information after software, operating system,
SQL Server, and hardware upgrades.
This appendix contains the following information:
To learn about...
Refer to:
Information to track for software versions
Software versions, on page 158
Information to track for the Data Center server
Data Center server information, on page 160
157
Appendix A/Data Center Specification Worksheet
Software versions
Software versions
Data Center
Use the following table to track the version of the Connected Backup software running on your Data Center. Update the table
after installing hotfixes and service packs.
Server
Version
Installation date
Microsoft Windows version

Use the following table to keep track of the Windows version running on the Data Center servers. Update the table after
installing hotfixes and service packs.
Server
Version/update number
Installation date
Microsoft SQL Server version

Use the following table to keep track of the SQL Server version running on the Data Center servers. Update the table after
installing hotfixes and service packs.
Server
158
Version/update number
Installation date
Software versions
Agent
Use the following table to track the version and type of the Agent deployed to each community on the Data Center. Update
the table after installing hotfixes and Service Packs.
Type
(PC or SV)
Community
Version
Deployment date
159
Data Center server information
Data Center server information

Server name and IP address
Use the following table to keep track of Data Center server names, IP addresses, and configuration type.
Server name
IP address
Primary/
secondary
Registration master
Licensing
Use the following table to keep track of the number of licenses, host IDs, and licensed features on each Data Center server.
Server name
160
Host ID
Number of
licenses
Type
Features
(PC or PC with
Server Option)
B
Data Center Installation Worksheets
About this appendix
This appendix contains worksheets that you can use to record information that you need during installation of the Data Center
server software.
To learn about...
Refer to:
Information you need before and during a Data Center

installation
Installation worksheets, on page 162
161
Appendix B/Data Center Installation Worksheets
Installation worksheets
Server names and IP addresses
Server names and IP addresses you have assigned for the Data Center server(s):
Server Name
Server DNS Name
IP Address
CAUTION
When choosing names for your Data Center server(s), avoid using the words BACKUP and
UPDATE (and other keywords used by Microsoft SQL Server) as part of the server name. Using these
words in the server name will cause problems when the Data Center software attempts to perform SQL
queries. You should also avoid using special characters such as a hyphen (-) in the server name.
Logical drive information

Drive letter and purpose for each disk drive on each Data Center server:
Drive
162
Contents
Size (GB)
RAID Level
SQL Server logon

Logon name and password (a domain account with local administrator privileges) for Microsoft SQL Server to run on the
Data Center server(s):
Server Name
User ID
Password
Domain name
Name of the Windows domain to which you will add the Data Center server(s). You must know an account and password
that has administrator privileges in this domain; you will use this account to set up the server(s).
NT Domain:___________________________
Domain account
Domain account with local administrative rights to the Data Center server(s); it should be unprivileged except on the
server(s). Setup creates these accounts automatically during installation or you can create them yourself.
Data Center (CNTD_DCServices, by default):
NT Domain Account:_____________________ Password:___________________
Support Center and MyRoamTM (CNTD_WebServices, by default):
DataBundler (CNTD_DataBundler by default):
Email settings
Email host and address information for the DCAlerter service:
SMTP Mail Host:_____________________________________________________
Administrator Email Address:__________________________________________
Alert Sender Email Address:____________________________________________
Support Center admin password

Password you will assign to the Support Center Admin Technician ID, which is the first Technician ID to be authorized to
use Support Center (not a Windows account name).
Support Center Admin Password: _______________________________________
163
Master Encryption Key (MEK)

Encryption key used to encrypt all other encryption keys on the Data Center. Use the MEK randomly generated by Data
Center Setup or create your own. The MEK must be at least eight characters but no more than 99 characters.
MEK: ________________________________________________________
Archive storage device

Archive storage device information, if used:
EMC Centera
IP address(es): ____________________________________________
Main profile: ______________________________________________
Purge profile: _____________________________________________
Distributed AML Server (DAS)
DAS server name: _________________________________________
Client Name (as configured on the DAS):______________________
The client name in a DAS configuration refers to the server, in this case the Data Center server, attached to the DAS as it
was named during the DAS installation.
NAS storage
Share for the NAS: ________________________________________
Expiration parameters
Expiration parameters, which you will be prompted for during installation. Accept the defaults if you are not sure.
:
Expiration Parameter
Default Value
Canceled
60 days
Deleted
90 days disk only
Chosen Value
180 days HSM

Excluded
0 (zero) days disk only

0 (zero) days HSM
Recent Versions
10 versions disk only

20 versions HSM
Old Versions
45 days disk only

90 days HSM
164
C
Maintenance Checklists
About this appendix
This appendix contains checklists that you can use when performing Data Center maintenance tasks.
To learn about..
Refer to:
Tasks you complete on a daily basis
Daily maintenance checklist, on page 166
Tasks you complete on weekly basis
Weekly maintenance checklist, on page 168
Tasks you complete on a monthly basis
Monthly maintenance checklist, on page 170
165
Appendix C/Maintenance Checklists
Performing daily maintenance

Daily maintenance checklist
This section contains a checklist for the maintenance tasks that you should perform on a daily basis. An M indicates a task
to be completed in the morning and an A indicates a task to be completed in the afternoon; some tasks require both. Each
step in the checklist provides a page reference in case you need detailed information for that step.
The checklist, which begins on the next page, is formatted to make it easy for you to photocopy and use in your regular
Data Center operations.
166
Daily checklist
Morning/ Task
Afternoon
Page
Verify the results of the daily automatic procedure.
120
M, A
Verify that services are running using DCMC.
123
M, A
Examine the event log through DCMC for any warnings or errors that might 123
need attention.
Verify personal backups by reviewing Agent logs for recent backups.
M, A
Verify that Support Center and Account Management Website are running. 124
M, A
Check Copy On Reference and replication using DCMC.
124
Check disk status and unknown disk space using DCMC.
125
Verify that the IT alert system works.
122
M, A
For Data Centers using tape libraries, check the tape drive status and tape 125
requests in DCMC.
For Data Centers using Secondary Tape Sets, determine whether or not to 125
remove Secondary Tape Set tapes.
124
167
Performing Weekly Maintenance

Weekly maintenance checklist
This section contains a checklist for the maintenance tasks that you should perform on a weekly basis. Each step in the
checklist also includes a page reference in case you need detailed information for that step.
168
Weekly checklist
Task
Page
Verify the results of the weekly automatic procedure by reviewing the weeklymaint.out
file with a text editor.
128
Back up Support Center reports.
130
Back up Agent Configurations.
130
Back up the Connected Windows registry key.
130
Check for available disk space.
131
For database backups performed to tape, remove and rotate current backup tape and
store in a safe place.
132
For mirrored or clustered Data Centers: Check time synchronization between mirrored
servers. Time on both servers should be within 30 seconds of each other.
132
Visit the Resource Center to check for software updates.
132
For Data Centers using tape libraries, check blank tapes, tape use, recyclable tapes, and 133
cleaning tapes.
For Data Centers using tape libraries, check library tape slots.
134
For Data Centers using tape libraries, check the event log to verify successful purge and 134
migrations are occurring on a regular basis.
For Data Centers using tape libraries, check tape and tape drive health.
135
169
Performing Monthly Maintenance

Monthly maintenance checklist
This section contains a checklist for the maintenance tasks that you should perform on a monthly basis. Each step in the
checklist also includes a page reference in case you need detailed information for that step.
170
Monthly checklist
Task
Page
Run the database maintenance script, dbmaint.sql, using SQL Query Analyzer. 138
Run Account Management SQL scripts.
141
Evaluate current Data Center capacity by checking CPU, RAM, disk utilization 144
and tape library utilization.
Verify firmware is current with manufacturers specifications.
146
Check your software licensing by checking the License Manager event in the
Application event log and comparing it to the number of accounts reported in
Support Center.
147
Save and clear the event log using the Windows Event Viewer.
150
For Data Centers using tape libraries, clean the library and tape drives.
152
For database backups performed to tape, clean the backup tape drive.
152
Verify that record keeping is up-to-date.
153
171
INDEX
A
access, Data Center Management Console (DCMC) 99
accounts
choosing for tape groups 37
duplicate 142
heavy hitters 142
inactive 142
invalid 143
management 141
reducing unnecessary 141
unowned 141
unsupported Agent versions 141
with excessive backup amounts 142
adding new license
about 149
adding seats to Data Center 147
additional host ID 148
additional NIC 148
changing Agent features 148
Agent
access to Data Center, verifying 66
configurations, backing up 130
licensing, features 148
replication of configuration files, about 19
antivirus software
on the Data Center 54
application event log, automatic backup of 113
Application log
clearing 150
saving 150
archive
balancing tape utilization 33
secondary tape sets, about 30
archive sets
and Compactor 38
deleting, and compaction 38
repackaging, about 38
replication, about 19
archive storage device, Data Center worksheet 164
Attached Storage Network (SAN),using 55
B
back up
Agent configurations 130
databases 128
off-site tapes, about 31
PEM files 75
rotating tape 132
Support Center reports 130
Windows registry key 130
BackupHSM
services 21
backups, managing excessive 142
BackupServer 17
installation, troubleshooting 79
overview 17
verifying operation 77
C
capacity
checking disk space 131
evaluating Data Center 144
tape library 145
Centera
using 56
checking
available tape slots 134
Data Center license 147
disk space status 131
hardware firmware 146
recyclable tapes 134
tape drive health 135
tape health 135
tape usage 133
cleaning
SQL database backup tape drive 152
tape library 152
tapes, managing 134
clearing event logs 150
clustered Data Center
about 51
monthly tasks 138
community,tracking Agent version 159
Compactor
and tape groups 37
archive sets, deleting 38
archive sets, repackaging 38
choosing tape account groups 37
Connected Backup Data Center Deployment 173
Index
database entries, deleting 38

disk space check 37
expiration parameters, Data Center worksheet 164
file expiration 40
migrating archive sets to tape 38
system analysis and repair 38
configurations, backing up Agent 130
configuring
communities 82
DCAlerter 82
enterprise directory integration 82
Copy On Reference 20
CPU utilization, evaluating 144
Customer directory, antivirus programs 54, 118
Customer volume, checking disk space 131
D
Data Center Management Console (DCMC)
accessing 99
interface 101
menus and toolbars 103
Data Center Toolkit
about 109
description 106
installing 109
invoking 109
requirements 109
Data Center worksheet
email settings 163
data migration and HSMPurge 21
database
backup to disk 128
backup to tape 128
cleaning backup tape drive 152
clearing transaction logs 128
compaction and deleting entries from 38
Master, Model, MSDB, backing up 128
monthly maintenance 138
replication of 19
rotating backup tapes 132
DataBundler
before installing 107
installing 107
requirements for use with version 6.x Agents 108
system requirements 107
usage requirements 108
DBCC utility 138
dbmaint.sql 138
DCAlerter
about 23
configuring 82
Data Center worksheet 163
DCMaint log
clearing 150
174
saving 150
default data expiration settings 40
deleting archive sets, and compaction 38
Directory database,backing up 128
disabling Removable Storage Manager (RSM) 58
disk
space, check available 131
space, checking during Compaction process 37
disk-only configuration
expiration rules, about
expiration, about 40
Distributed AML Server (DAS)
using 58
domain account, Data Center worksheet 163
domain controller, using Data Center as 52
domain name, Data Center worksheet 163
domain, Data Center assigning 64
drivers, installing tape library 64
duplicate accounts, managing 142
E
email alerts, configuring DCAlerter 82
email settings, Data Center worksheet 163
EMC Centera
using 56
emergency repair disk
creating on Windows 2000 66
enterprise directory
managing 85
errors, checking tape 135
evaluating
CPU utilization 144
Data Center capacity 144
RAM utilization 145
event log
automatic backup of 113
clearing 150
configuring email alerts 82
DCAlerter service 23
maintenance 113
saving 150
excessive backups, managing accounts 142
expiration
about 40
default settings 40
marking files for 38
of files, and Compactor 40
parameters, Data Center worksheet 164
Index
F
features, licensing for Agent 148
file expiration parameters, Data Center worksheet 164
files
marking as expired, about 38
replication, about 19
shared pool, and SendOnce feature 20
uncommon, and PoolServer 20
firmware, checking 146
formulas
average CPU utilization 144
RAM utilization 145
system processor queue length 144
G
groups
tape account, choosing for compaction 37
tape, about 28
guidelines
SCSI ID for multiple SCSI busses 57
SCSI ID for single SCSI bus 57
H
hardware
firmware, checking 146
requirements for MyRoam 68
requirements for Support Center 68
heavy hitter accounts, managing 142
Hierarchical Storage Manager. See HSM
host ID, new license 147
HSM
about 26
adding permanent expansion library, about 33
archive storage devices 26
balancing tape utilization 33
cleaning tape library 152
cleaning tape library drives 152
determining tape capacity 33
Distributed AML Server (DAS), using 58
EMC Centera, using 56
installation, troubleshooting 79
migrating to Secondary Tape Set 128
migration and purge 27
mirgration 27
mixed libraries 34
multiple SCSI busses, guidelines 57
multiple tape libraries 32
primary tape set, about 29
purge 27
Removable Storage Manager (RSM), disabling 58
requirements 56
secondary tape sets, about 30
single SCSI bus, guidelines 57

taking tapes off-site, about 31
tape and tape account groups, about 28
tape library requirements 56
Tape Sets 29
tape utilization 33
temporary reliever library 32
transitioning to new tape library, about 32
using different tape technologies 34
verifying migration 134
HSMClient, about 21
HSMPurge, about 21
HSMServer
about 21
components 21
how it works 21
HSMServer, components of 21
I
IIS
configuring on Windows 2003 Server 63
installing on Windows 2003 Server 63
using with Support Center and MyRoam 62
inactive accounts, managing 142
IndexServer 18
installation
attached library, troubleshooting 80
BackupServer, troubleshooting 79
Data Center, troubleshooting 79
HSM, troubleshooting 79
Support Center and MyRoam 81
invalid accounts, managing 143
invoking, Data Center Toolkit 109
IP addresses, Data Center worksheet 162
L
libraries
checking available slots 134
different technologies, using 34
expanding 33
multiple, using 32
tape capacity 145
tape usage 133
temporary use of 32
transitioning to new 32
license
adding Agent features 148
adding users 147
additional host ID 148
additional NIC 148
checking Data Center 147
Data Center 51
175
Index
host ID change 147

new NIC 147
removing Agent features 148
requesting new 149
tracking information 160
updating Data Center 147
lmhosts file, configuring 64
logical drive information
logs
Application event 112
automatic backup of 113
DCAlerter service 23
DCMaint 112
Event 112
Trace 114
network, verifying 65
replication, verifying 78
synchronizing system time 132
Model database, backing up 128
monthly maintenance
tasks 138
MSDB database, backing up 128
MyRoam
moving the scratch folder 82
MyRoam server
hardware requirements 68
installing 81
preparation 70
requirements 68
software requirements 69
verifying installation 81
maintenance
daily tasks 119
event log 113
monthly tasks 138
weekly tasks 127
managing
accounts excessive backup amounts 142
accounts on the Data Center 141
accounts unsupported Agent versions 141
duplicate accounts 142
heavy hitter accounts 142
inactive accounts 142
invalid accounts 143
unowned accounts 141
Master database, backing up 128
Master Encryption Key (MEK), Data Center worksheet 164
measuring
CPU utilization 144
Data Center capacity 144
RAM utilization 145
Microsoft
IIS 63
SQL Server 2000, installation guidelines 66
Windows Server, configuration guidelines 62
Windows Server, installation guidelines 61
Microsoft SQL Server, track version 158
Microsoft Windows, track version 158
migration
Secondary Tape Set 128
verifying status 134
mirrored Data Center
about 51
database backup 128
date and time, synchronizing 65
monthly tasks 138
network
assigning Data Center to domain 64
logins, Data Center 60
mirrored Data Center, verifying connection 65
ports 59
remote access to Data Center, verifying connection 66
requirements, Data Center 59
using 55
new license, requesting 149
NIC
license for additional 148
license for new 147
176
O
obtaining new license 149
off-site tape sets 31
overview
BackupHSM 21
BackupServer 17
DCAlerter 23
event log 112
HSMClient 21
HSMPurge 21
IndexServer 18
PoolServer 20
ReplicationServer 19
P
partitions, Data Center server creating 63
PEM files, backing up 75
performance, evaluating Data Center 144
permanent license, Data Center 51
Index
Pool account, about 20

PoolServer 20
about 20
how it works 20
ports for network access 59
ports, Data Center 59
preparing for installation
Data Center 49
Support Center and MyRoam 68
Primary Tape Set 29
purging archive sets 21
Q
querying for
duplicate accounts 142
heavy hitter accounts 142
inactive accounts 142
invalid accounts 143
unowned accounts 141
unsupported Agent versions 141
R
RAM utilization, evaluating 145
record keeping,verifying 153
recyclable tapes, checking 134
Registry database,backing up 128
registry key, backing up 130
reinstallation, Data Center server 75
remote access to Data Center, verifying 66
Removable Storage Manager (RSM), disabling 58
removing Agent features, licensing 148
repair disk
replication
about 19
database 19
verifying 78
reports, backing up Support Center 130
requesting new license 149
requirements
Data Center software 52
HSM 56
MyRoam 68
network, Data Center 59
Support Center 68
Support Center and MyRoam server 68
tape library 56
results
weekly maintenance 128
results,weekly maintenance 128
retrieving files and HSMClient 21
reusing tapes 134

rotate, database backup tapes 132
S
saving event logs 150
scratch folder
moving on the Data Center server 82
SCSI
multiple busses guidelines 57
single bus guidelines 57
Secondary Tape Set
deciding to use 30
description 30
migrating to 128
taking off site 31
security
Data Center 60
SendOnce
Copy On Reference process, about 20
PoolServer service, about 20
server
assigning Data Center to domain 64
Data Center install, verifying 76
Data Center, reinstalling 75
lmhosts file, configuring 64
SQL Server 2000, installing 66
Web server preparation 70
Windows Server, configuring 62
Windows Server, installing 61
service login accounts, Data Center 60
services, Data Center
BackupServer 17
Compactor 37
DCAlerter 23
HSMClient 21
HSMPurge 21
HSMServer 21
IndexServer 18
PoolServer 20
settings,file expiration defaults 40
software requirements
for Data Center 52
for MyRoam 69
for Support Center 69
software version
Microsoft SQL Server worksheet 158
Microsoft Windows worksheet 158
SQL database
backup volume, checking for disk space 131
backups, rotating tapes 132
cleaning backup tape drive 152
volume, checking for disk space 131
177
Index
SQL Server 2000

installing 66
login, Data Center worksheet 163
standalone Data Center
about 51
database backup 128
monthly tasks 138
rotating SQL backup tape 132
Support Center
backing up reports 130
hardware requirements 68
Support Center server
installation, verifying 81
installing 81
preparation 70
requirements 68
synchronicity of account data, and Compactor 38
synchronization, system time 132
synchronizing date/time, mirrored Data Center 65
System log
clearing 150
saving 150
System Monitor
evaluating CPU utilization 144
evaluating RAM utilization 145
system time, synchronization 132
cleaning drives 152

Distributed AML Server (DAS), using 58
driver, installing 64
installation with attached library, troubleshooting 80
multiple SCSI busses guidelines 57
requirements 56
single SCSI bus guidelines 57
Tape Sets
overview 29
primary 29
secondary 30
TCP access, Data Center 59
technicians,validating 84
temporary license, Data Center 51
time, synchronizing system 132
tools
Data Center Toolkit 106
DataBundler 106
trace logging, about 114
transaction logs, clearing 128
troubleshooting
BackupServer installation 79
Data Center installation 79
HSM installation 79
installation with attached tape library 80
U
T
tape
account groups, choosing for compaction 37
checking available slots 134
checking health 135
checking recyclable 134
checking usage 133
compaction of, about 37
errors 135
groups and account groups, about 28
libraries, using different technologies 34
library capacity 145
managing cleaning 134
multiple libraries 32
primary set and HSM 29
primary set, and HSM 29
reusing 134
secondary set and HSM 30
sets, taking off-site 31
transitioning to new library 32
utilization, balancing 33
tape drives
checking health 135
cleaning 152
tape library
cleaning 152
178
UDP access, Data Center 59

unowned accounts, managing 141
unsupported Agent versions, finding accounts with 141
updating, Data Center license 147
usage, tape 133
utilization of tapes, about 33
V
validate Support Center technicians 84
verifying
available tape slots 134
BackupServer 77
Data Center install 76
disk space 131
HSM installation 78
mirrored Data Center replication 78
record keeping 153
Support Center and MyRoam installation 81
tape health 135
weekly maintenance results 128
viewing
replication status 19
viruses in archived files, about 54, 118
volumes
Data Center server creating 63
Index
W
Web server
preparation 70
requirements 68
Support Center and MyRoam, installing 81
verifying installation 81
Windows registry key, backing up 130
Windows Server
authentication, Data Center 60
configuring 62
installing 61
worksheet
license information 160
Microsoft SQL Server version 158
server name and IP address 158
179

Connecteddata Center Deployment 82

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Connecteddata Center Deployment 82

Uploaded by

Copyright:

Available Formats

Connected Backup

Data Center Deployment

Iron Mountain Support Information

Iron Mountain Incorporated

Iron Mountain Incorporated

Connected Backup Data Center Deployment

Chapter 5: Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Connected Backup Data Center Deployment

Iron Mountain Incorporated

General tasks for the morning and afternoon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Iron Mountain Incorporated

Connected Backup Data Center Deployment

Chapter 1: Data Center Services

Describes the services that run on the Data Center server.

Chapter 2: Hierarchical Storage Manager

Provides details about Hierarchical Storage Manager operations

Provides details about Compactor operations in the Data Center.

Chapter 4: Sizing Your Data Center

Provides hardware and software recommendations for your Data

Chapter 5: Preparing for Installation

Describes the tasks you should complete before installing the

Chapter 6: Installing the Data Center Software

Contains procedures that describe how to install and configure the

Provides an overview of the Data Center Management Console

Chapter 9: Installing Management Tools

Contains procedures that describe how to install the Data Center

Chapter 10: Event Logging

Provides an overview of the event logging that the Data Center

Iron Mountain Incorporated

Connected Backup Data Center Deployment

Chapter 12: Daily Maintenance

Contains procedures that describe how to perform the daily

Chapter 13: Weekly Maintenance

Contains procedures that describe how to perform the weekly

Chapter 14: Monthly Maintenance

Contains procedures that describe how to perform the monthly

Appendix A: Data Center Specification Worksheet

Contains a worksheet where you can record important

Appendix B: Data Center Installation Worksheets

Contains a worksheet that you can use to record information that

Appendix C: Maintenance Checklists

Contains worksheets that you can use to track the maintenance

Connected Backup Data Center Deployment

Iron Mountain Incorporated

Connected Backup/PC Product Overview

This manual provides an overview of the features in the

This manual describes how to download, install, and configure

Connected Backup/PC Agent Quick Start

This short document provides users with a quick reference for

Connected Backup/PC Account Management Website

This manual describes how to customize the Account

Iron Mountain Incorporated

Connected Backup Data Center Deployment

Indicates one of the following:

Monospaced bold text

A control in an applications user interface

Indicates one of the following:

The title of a manual or publication

A variable for which you supply a value

Indicates one of the following:

Indicates system commands that you enter.

Connected Backup Data Center Deployment

Iron Mountain Incorporated

Iron Mountain Website