Connected Backup Data Center Deploymentmysupport.download.microfocus.com/SSO/online_help... · 8 Connected® Backup Data Center Deployment Iron Mountain Incorporated Related documentation

Connected® BackupData Center Deployment

Version 8.2 Service Release 2

Document informationConnected Backup Data Center DeploymentConnected Backup Version 8.2 Service Release 2Printed: August 11, 2008Printed in USA

Iron Mountain Support Information800.675.5971 U.S. +1 508 808 7629 E.U. +49 6102 [email protected]

CopyrightCopyright © 2007-2008 Iron Mountain Incorporated. All rights reserved.

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

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

DisclaimerWhile 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 Incorporated745 Atlantic AvenueBoston, MA 021111-800-899-IRONwww.ironmountain.com

mailto:[email protected]

http://www.ironmountain.com

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Graphical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Contacts/Reporting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Iron Mountain Digital Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Part I: About the Data Center

Chapter 1: Data Center Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Services overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16BackupServer Service Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16IndexServer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17ReplicationServer Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17PoolServer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18HSMServer Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Compactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19DCAlerter Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Chapter 2: Hierarchical Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Hierarchical Storage Manager (HSM) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Migration and purge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Tapes Groups and Tape Account Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Tape Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Taking Secondary Tape Set tapes off site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Multiple tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Permanent expansion library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Chapter 3: Compactor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Compactor Service and Data Center configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Compactor Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31File expiration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Part II: Data Center Installation

Chapter 4: Sizing Your Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Sizing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Sizing estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Network bandwidth requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

TABLE OF CONTENTS

Iron Mountain Incorporated Connected® Backup Data Center Deployment 3

Table of Contents

Chapter 5: Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Evaluating configuration and license options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Data Center server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43VMware Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Recommended hardware for database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Storage solutions requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Security requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Installing and configuring Microsoft software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Installing and configuring SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Support Center and Account Management Website preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Enabling MyRoam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Chapter 6: Installing the Data Center Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Installing the Data Center software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Verifying Data Center installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Troubleshooting Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Installing Support Center and Account Management Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Configuration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Chapter 7: Integrating the Data Center with Enterprise Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Enterprise directory overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Enterprise directory integration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Mapping data fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Verifying successful enterprise directory integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Part III: Management

Chapter 8: Managing the Data Center with DCMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

DCMC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86DCMC user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Chapter 9: Installing Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Management Tools Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94Installing DataBundler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94Installing the Data Center Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Chapter 10: Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Event Log Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Part IV: Maintenance

Chapter 11: Introduction to Data Center Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Maintenance tasks overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106Antivirus software and the Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106Types of maintenance tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106

4 Connected® Backup Data Center Deployment Iron Mountain Incorporated

Table of Contents

Chapter 12: Daily Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

Tasks to complete at the start of every day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108Tasks to complete at the start and end of every day . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Tasks to complete daily for Data Centers that use tape libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Chapter 13: Weekly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Verifying the results of the Weekly Automatic Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116Weekly backup tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117Checking for available disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Performing weekly general tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Performing weekly tasks for Data Centers that use tape libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Chapter 14: Monthly Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

Performing database maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124Performing account maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127Evaluating current Data Center capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Verifying current firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Checking software licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131Maintaining the event logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Cleaning library and tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Cleaning the SQL database backup tape drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134Verifying records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135

Part V: Appendices

Appendix A: Worksheets and Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Data Center server information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Appendix B: Data Center Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Data Center Installation Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144

Appendix C: Maintenance Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Daily maintenance checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Weekly maintenance checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Monthly maintenance checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Iron Mountain Incorporated Connected® Backup Data Center Deployment 5

PREFACE

How this document is organized

Iron Mo

This document consists of 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 must complete before you install 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 Directory

Describes how to use an Enterprise Directory with the Data 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.

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.

untain Incorporated Connected® Backup Data Center Deployment 7

8 Con

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

Appendix A: Worksheets and Checklists 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.

Section Description

Related documentation
The following sections list related documents and other documentation resources.
Related documents
The following documents 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 online help. To open the online help, click Help or the ? button.

The Resource Center The Resource Center is a repository of information that all Connected Backup customers can access. It includes procedures and information that are not in the product documents or online help. Visit the Resource Center at https://resourcecenter.ironmountain.com

nected® Backup Data Center Deployment Iron Mountain Incorporated

Conventions

Iron Mo

The following tables list the various conventions used in Iron Mountain® Digital™ documentation. These conventions let you quickly and easily identify particular elements, processes, and names that occur frequently in documents.

Typographical conventions
This document uses the following typographical conventions:
Convention Description

Bold text Indicates one of the following:

• New terminology

• Elements that appear on the user interface

• Registry keys

• Important information

• URLs

Italic text Indicates the title of a document or publication or a variable that requires you to supply a value

Monospaced text Indicates one of the following types of information:

• Code examples

• System messages

Monospaced bold text Indicates system commands that you enter

Graphical conventions

This document uses the following graphical conventions:

Convention Description

Indicates additional information that reader might want to know.

Indicates cautions that, if ignored, can damage software or hardware.


Contacts/Reporting problems

10 Co

For information about how to contact Iron Mountain Incorporated for customer support, see the following sections.

Corporate support
You can contact Product Support Organization Name Here in the following ways:
North American Support Center Southborough MA 08:00 AM to 09:00 PM EST/EDT Monday – Friday

Level 2 and Enterprise telephone numbers +1-800- 675-5971

+1-508- 808-7629

Level 1 telephone numbers +1-800-888-2774, option 5, then 2

+1-508-808-7440

Small Business or Home Office telephone numbers +1-508-808-7440

+1-800-647-3078

Email address [email protected]

Support Web site ironmountain.com/support

Europe, Middle East, and Africa (EMEA) Support Center Frankfurt, Germany 08:00 to 17:00 CET/CEST Monday – Friday

Telephone number +49-6102-882-8855

Email address [email protected]

Support Web site ironmountain.com/support

Iron Mountain Digital Web site

Visit the Iron Mountain Digital Web site at www.ironmountain.com.

nnected® Backup Data Center Deployment Iron Mountain Incorporated

http://www.ironmountain.com/digital

PART I: ABOUT THE DATA CENTER

Chapter 1: Data Center ServicesChapter 2: Hierarchical Storage ManagerChapter 3:Compactor

1

DATA CENTER SERVICES

About this chapter

Iron Mo

This chapter provides an overview of the services that Data Center uses to run the Data Center servers.

This chapter contains the following topics:

To learn about... See:

The services that the Data Center uses Services overview, on page 16

What BackupServer does BackupServer Service Overview, on page 16

What IndexServer does IndexServer Overview, on page 17

What ReplicationServer does ReplicationServer Service Overview, on page 17

What PoolServer does PoolServer Overview, on page 18

What HSMServer does HSMServer Overview, on page 19

What Compactor does Compactor, on page 19

What DCAlerter does DCAlerter Overview, on page 19


Chapter 1: Data Center Services Services overview

Services overview

16 Co

To perform the necessary tasks to run the Data Center server, the Data Center uses the following services:

• BackupServer Service Overview — Facilitates data backups and retrievals

• IndexServer Overview — Indexes file and archive set information to databases

• ReplicationServer Service Overview — Replicates between servers in a mirrored pair configuration

• PoolServer Overview —Maintains the shared pool that the SendOnce® technology uses

• HSMServer Overview —Copies archive sets to archive storage devices and purge migrated sets from disk when needed

• Compactor — Removes old data from the Data Center

• DCAlerter Overview —Alerts technicians about Data Center events

BackupServer Service Overview

The BackupServer service processes requests from the Agent for data backup and retrieval. BackupServer gathers backed-up data into an archive set. The Data Center saves the archive set as a file with an .arc extension and stores it in the Customer folder. Each file contains file backup data transmitted from a client during a single backup session.

If the data from a single backup session is large, BackupServer saves information to more than one archive set. Each represents a portion of the backup session. Using multiple archive sets helps to optimize data recovery performance.

When BackupServer revieves a request from the Agent to retrieve a file, BackupServer must find the first backup of the file (called the base) and all the changes (called deltas) necessary to recreate the specific version of the file that the user requested.

For example, if the user requested to retrieve the third backed-up version of a file, BackupServer must retrieve the base (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. Because the the user backed up the base and the deltas in different backup sessions, they are in different archive sets. Typically, BackupServer uses multiple archive sets to retrieve a file.

In addition to processing requests for data backup and retrieval, BackupServer manages the list of authorized user accounts and registers new accounts. There is one user account for each client.

BackupServer starts automatically with Windows Server. The Data Center Management Console (DCMC) includes a BackupServer node. This node lets you view the following information:

• Service status

• Sessions

• Properties

CAUTION

Do not delete .arc files from the Customers directory. Doing so deletes end users’ data and renders it unrecoverable.


IndexServer Overview Chapter 1: Data Center Services

Iron Mo

To view and edit status information, complete the following steps:

1. Open DCMC.

2. In the Console tree, expand the name of the server on which the service runs, and select BackupServer.

3. To view and edit BackupServer settings, right-click BackupServer, and select Properties.

IndexServer Overview
As Agents back up archive sets to the Data Center server, information about each file in the archive set must be stored in the Directory database. The IndexServer writes this information to the Directory database after 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 you use a mirrored configuration).
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.

IndexServer starts automatically with Windows Server. The Data Center Management Console (DCMC) includes a IndexServer node that lets you access the following information:

• Service status

• Properties


1. Open DCMC.

2. In the Console tree, expand the name of the server on which the service runs, and select IndexServer.

3. To view and edit BackupServer settings, right-click IndexServer, and select Properties.

ReplicationServer Service Overview

The ReplicationServer service replicates the following content between the servers in a mirrored pair:

• Archive sets

• Database table rows

• Agent configurations

After the Agent backs up an archive set to the Data Center server and indexes the database, the archive set goes into a queue to be replicated to the mirror. The ReplicationServer services replicates the archive set to the mirror as a whole rather than in portions as the Agent backs it up.

Most, but not all, of the database table rows in the schema replicate between the servers in a mirrored pair. When a row in the database table is inserted, deleted, or modified, the database is placed in a queue for replication between the mirrored servers. SQL replication handles the replication process.

Important

The ReplicationServer service runs only on mirrored and cluster Data Center configurations.

The Asset database is installed on every Data Center server. This database is populated and replicated only if your Data Center is licensed for Audit.


Chapter 1: Data Center Services PoolServer Overview

18 Co

When you use Support Center to create Agent configuration files to download to Agents, the files that Support Center creates 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. For successful file downloads to Agents, the files and database rows must exist on both servers because Agents can connect to either Data Center server. The server an Agent connects to first depends on which server you configure the Agent to contact first. Therefore, Agent configuration files must be available on all servers in the Data Center.

ReplicationServer starts automatically with Windows Server. Archive sets and database entries are replicated continuously when ReplicationServer runs. If you have to pause or stop replication, you can pause or stop the service in the Data Center Management Console (DCMC).

The DCMC includes a ReplicationServer node that lets you view the following information:

• Service status

• Properties


1. Open DCMC.

2. In the Console tree, expand the name of the server on which the service runs, and select BackupServer.

3. To view and edit BackupServer settings, right-click ReplicationServer, and select Properties.

PoolServer Overview

PoolServer maintains the shared file pool that implements SendOnce® technology. SendOnce technology recongizes duplicate files from multiple Agents and stores them on the Data Center server only once. Doing so reduces the storage space needed on the Data Center.

PoolServer also implements the Copy On Reference service. Copy On Reference cleans the shared file pool of uncommon files. When two Agents back up an identical file (for example, an application file, operating sytem file, or common organization file), the SendOnce technology places the file 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 14 days. An uncommon file is a file that no other account has backed up within 14 days. These files are removed to keep the Directory database from growing too large and to keep the performance of the SendOnce® operation efficient. You can use DCMC to change the number of days that uncommon files remain in the pool.

PoolServer starts automatically with Windows Server.

The Data Center Management Console (DCMC) includes a PoolServer node that lets you access the following information:

• Service status

• Properties


1. Open DCMC.

2. In the Console tree, expand the name of the server on which the service runs, and select PoolServer.

3. To view and edit BackupServer settings, right-click PoolServer, and select Properties.


HSMServer Overview Chapter 1: Data Center Services

HSMServer Overview

Iron Mo

HSMServer is the Data Center service that copies archive sets between the local server’s disk and the archive storage device. The HSMServer contains the following components:

• HSMClient

• BackupHSM

• HSMPurge

BackupServer opens the HSMClient 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.

Do not pause the BackupHSM service. When BackupHSM is paused you cannot cancel requests or view the status in DCMC.

The HSM library audits its contents and then BackupHSM audits the library. If you stop any HSM activities, BackupHSM alerts the service to complete the current request and then stop.

HSMPurge migrates (copy) archive sets from disk to the archive storage device and, purges (deletes) archive sets from disk 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 server’s disk where BackupServer can process them.

For more information about HSM, seeChapter 2: Hierarchical Storage Manager on page 21.

Compactor
The Compactor service cleans old data off of the Data Center. Compactor verifies synchronization between mirrored servers, applies expiration rules to backed up data, and deletes expired data. The goal of Compactor is to speed up the Retrieve process and reduce the amount of data stored long term on the Data Center.
For more information about the Compactor process, seeChapter 3: Compactor on page 29.

DCAlerter Overview

DCAlerter notifies individuals that you designate when events that you specify occur on the Data Center. DCAlerter monitors the Data Center event logs for the event IDs that you specify. When the Data Center logs an event ID that you have specified for notification, DCAlerter sends an email message to the designated individuals.

You can specify your SMTP mail host and an administrator email address for DCAlerter during Data Center Setup. If you do not enter the SMTP mail host information during Data Center Setup, the DCAlerter feature is not active. Data Center Setup installs a default set of events for notifications. You can modify the installed settings using DCMC.

To view status information in the details pane, select DCAlerter from the console tree for the server on which the service runs.

To view and edit DCAlerter settings, complete the following steps:

1. Open DCMC.

2. In the Console tree, right-click DCAlerter, and select Properties.


2

HIERARCHICAL STORAGE MANAGER

About this chapter

Iron Mo

This chapter describes Hierarchical Storage Manger.



What Hierarchical Storage Manager is Hierarchical Storage Manager (HSM) overview on page 22

How migration and purge works Migration and purge, on page 22

Tape Groups and Tape Account Groups Tapes Groups and Tape Account Groups, on page 22

Tape sets Tape Sets, on page 23

Multiple tape libraries Multiple tape libraries, on page 25

Permanent expansion libraries Permanent expansion library, on page 26


Chapter 2: Hierarchical Storage Manager Hierarchical Storage Manager (HSM) overview

Hierarchical Storage Manager (HSM) overview

22 Co

Over time, as Agents on many computers perform many backups, the number of archive sets on the Data Center server disk grows. If you configure your Data Center to use HSM, when free space on the disk drops below a preconfigured threshold, BackupServer sends a request to Hierarchical Storage Manager (HSM) to migrate archive sets from disk to a secondary archive storage device. If there is no secondary storage device, archive sets remain on the Data Center server disks.

Connected Backup supports the following secondary storage devices.

For a list of supported hardware, visit the Resource Center.

Device Description

Tape libraries Devices such as small computer system interface (SCSI) and direct attached storage (DAS) that include a medium changer device to move tapes from storage slots into tape drives and back again.

EMC Centera A disk-based device used by Hierarchical Storage Manager (HSM) for secondary storage.

Migration and purge
Migration and purge are HSM services that move old data into archive sets and remove redundant data.
When free disk space on the Data Center server drops below a preset threshold, HSMPurge migrates archive sets from disk to an archive storage device. After migration to the storage device, the original archive sets remain on the disk. The migrated archive sets remain on disk so there are as many archive sets as possible for file retrieval requests.

When free disk space drops to a second specified threshold, HSMPurge purges the migrated archive sets from disk to free disk space for newer backups. The purging continues until free disk space grows to a specified percentage.

If you configure your Data Center to use multiple disk volumes, the migration and purge processes begin or end when thresholds are reached across all volumes.

To view the migration process and specify disk space percentages for the migration and purge processes, use the Data Center Management Console (DCMC).

Tapes Groups and Tape Account Groups

Tape Groups are a way to keep 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 (zero) is the default Tape Group that Data Center Setup creates. Data Center Setup assigns the default community to Tape Group 0. Unless you specify otherwise in Support Center, Data Center Setup also assigns all new communities to Tape Group 0.

Tape Account Groups are groupings of accounts within a Tape Group. Tape Account Groups provide a way for HSM to group accounts together for assignment to tape. The purpose of Tape Account Groups is to fully use tape space. Tape Account Groups are assigned a predetermined maximum number of accounts and quantity of data. HSM creates a new Tape Account Group when the current Tape Account Group reaches capacity.


Tape Sets Chapter 2: Hierarchical Storage Manager

Tape Sets

Iron Mo

A tape set is a group of tapes that together contain all of the data for a give Data Center.

Whether you run a stand-alone or mirrored Data Center configuration, you risk losing backed up data for the following reasons:

• Disk failure on a stand-alone 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 the Data Center stores backed up data redundantly on two identical Data Centers. For example, if one Data Center of a mirrored pair experiences technical problems, the data is still available on its mirror. However, Stand-alone Data Center configurations store only one copy of data on the primary storage device (or secondary storage device, if applicable).

To protect your data against loss, you can configure your Data Center to use one or more additional tape sets. During the migration process, HSM copies data from disk to tapes that belong to the tape sets. For installation information, seeChapter 3: Compactor Service and Data Center configurations on page 29.

Primary Tape Set
The primary tape set is a set of backup tapes that remain permanently in the tape library. There is only one Primary Tape Set in the tape library. The 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 in the Primary Tape Set. For more information, seeTapes Groups and Tape Account Groups, on page 22.
For tape optimization, do not migrate your data to tape frequently. When the Data Center disk space is full, HSMPurge migrates data to the Primary Tape Set with the goal of consolidating data for each account.

A tape is assigned new accounts only if the amount of data on the tape is under a specific threshold. Imposing a data threshold provides space for future migrations for accounts that have already been assigned to the tape. Based on DCMC settings, Data migrates from the Data Center disk to the Primary Tape Set as needed. If the archive disk is properly sized, migration occurs once a week.

Secondary Tape Sets

A secondary tape set is a set of backup tapes that you can remove from the tape library for off-site storage. 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, you can use disaster recovery tools and procedure to recover archive sets. 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 to provide redundant protection of backed up data in both standalone and mirrored environments.

You can use secondary tape sets without a primary tape set. In this situation, the Data Center functions primarily as a disk-only 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 only one or two day’s worth of archives.


Chapter 2: Hierarchical Storage Manager Tape Sets

24 Co

There are two types of Secondary Tape Sets:

• SendOnce — 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. It is especially helpful in a standalone Data Center configuration because it lets you quickly recover backed up data that is 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 at the same location.

• Off-site — Contain a complete copy of archive sets (with the exception of the SendOnce account) and are intended for off-site storage. Depending on the needs of your configuration, you can configure the system to create one or more off-site Secondary Tape Sets. For maximum data protection, tapes in these sets are filled and removed from the library as often as possible so if there is a full-system crash, the most recent users’ data is available on tape. After you remove tapes from the library, store them in a safe location, preferably in a different building.

Deciding to use Secondary Tape Sets

To decide whether or not to use Secondary Tape Sets, consider the following:

• The amount of risk involved in your Data Center operations.

In 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 using a Secondary Tape set setup and how it can affect your Data Center operations.

The primary advantage of using Secondary Tape Sets is to completely protect against loss or damage of backup data. Secondary Tape Sets can be particularly valuable in a standalone server environment, where the risk of losing data due to a disk or tape failure is especially high. If an entire system becomes unusable, the off-site tapes from the Secondary Tape Set are the only source of end-user data.

Although a mirrored server configuration provides extra protection against all possible failures because it stores data redundantly at the two identical Data Centers, Secondary Tape Sets can be 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 willing to accept.


Taking Secondary Tape Set tapes off site Chapter 2: Hierarchical Storage Manager

Taking Secondary Tape Set tapes off site

Iron Mo

To minimize the vulnerability of data in the event of a disaster, Secondary Tape sets use the following types of schedules:

• Migration schedule

• Extraction schedule

Migration schedule
The migration schedule determines the frequency with which data migrates to the Secondary Tape Set. To reduce this risk of losing data to disk failure in a single-sever environment, data must migrate to the Secondary Tape Set as frequently as possible. The greater the frequency of migration, the less the data loss if the disk were to fail. For that reason, the migration schedule runs migration automatically daily, or several times per day. You can also use the DCMC to migrate data to the Secondary Tape Set.
Extraction schedule
To ensure the safety of data in case of a disaster that in the loss of the entire Data Center, you must remove Secondary Tape Set tapes from the library and take them off-site often. The extraction schedule defines how often the Secondary Tape Set tapes are removed from the library.
To determine how frequently you need to perform tape extraction, consider the following factors:

• The amount of data that the Data Center receives daily. If the Data Center has a large user community, you must perform tape removal more frequently than if the Data Center has a small user community.

• The number of blank tapes that the user provides to support the Secondary Tape Set configuration.

You can set the following extraction intervals:

• Less than a day

• Equal to a day

• Greater than a day

Remove Secondary Tape Set tapes from the library every other day, or as soon as the tape gets full. Do not wait until the tape gets full. Waiting until the tape is full reduces the cost of media, but increases the risk of losing backed-up data due to complete disk loss. After you remove the tapes, store them in a safe location, preferably in a different building.

Multiple tape libraries

The Data Center supports up to two tape libraries attached to each server. You might want to use multiple tape libraries in the following situations:

• You have an existing tape library and would like to replace it with a new tape library (for example, you replace 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.

The following sections explain each of these situations. For more information on how to install two tape libraries on your Data Center or how to add a second tape library, visit the Resource Center.


Chapter 2: Hierarchical Storage Manager Permanent expansion library

Transition to a new tape library

26 Co

The goal of replacing a library 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 those in the new library. Consider the time required to copy the data from the old library to the new library.

For more information about how to transition to a new library, visit the Resource Center.

Temporary reliever library
There might be times when you must use an additional ‘reliever’ tape library for temporary extended storage until Compactor can free sufficient space in your original library. In this situation, keep your original library as the permanent library, and use the additional temporary library for only as long as you need it. Connect the additional library and let the Compactor service run until it frees up enough tape space to warrant removing the additional library.
Permanent expansion library

CAUTION

If you use a temporary reliever library, you must transfer tapes back and forth between tape libraries. Therefore, the two libraries must use compatible tape and barcode technologies.

If you use multiple tape libraries to permanently expand your tape capacity, you must keep the multiple libraries in use for an indefinite amount of time. Your goal is to use the multiple libraries as efficiently as possible. Doing so means balancing tape use among all of your libraries.

To balance tape use, understand the following concepts:

• How tape usage works in HSM

• How to balance tape utilization across multiple libraries

• How to work with libraries of different technologies

The following sections explain these concepts.

Understanding tape usage in HSM

When HSM migrates data to tape, it accesses the tapes in alphabetical and numerical order according to the tape labels. Regardless of where or when you insert the tapes, when the previous tape is full HSM looks for the next sequential tape (labeled alphabetically or numerically).

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 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 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, seeTapes Groups and Tape Account Groups, on page 22.

The driver installed for the tape drive determines the capacity of a tape when you load the tape. HSM requests this information from the drive shortly after each tape is loaded and then stores this information in an internal database.


Permanent expansion library Chapter 2: Hierarchical Storage Manager

Balancing tape use

Iron Mo

To balance the workload across tape libraries, 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, 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

The easiest way to balance tapes is to use libraries with compatible tape and barcode technologies. If the libraries are compatible, you can move tapes between the libraries to get the order that yields optimum load balancing. This process is more difficult if you use libraries with incompatible tape and barcode technologies because you cannot move tapes between the libraries.

If you use libraries with different tape and barcode technologies, you must prepare in advance. 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. HSM alternates libraries when it migrates data to a new tape.


3

COMPACTOR

About this chapter

Iron Mo

This chapter describes the Compactor service.



How different configurations use Compactor Compactor Service and Data Center configurations, on page 30

How Compactor operates Compactor Tasks, on page 31

How file expiration affects Compactor File expiration overview, on page 33


Chapter 3: Compactor Compactor Service and Data Center configurations

Compactor Service and Data Center configurations

30 Co

Compactor is a Data Center service that runs continuously based on Data Center activity. Compactor has the following purposes:

• Reduce the overall storage requirement for the Data Center.

• Improve the performance of Agent file retrieval.

• 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 mirrored configurations than it does on standalone configurations. It also works differently with HSM than it does with a disk-only configuration.
Compactor in mirrored Data Centers
In mirrored Data Centers, the Compactor service runs on both servers. However, only one of the servers in the pair controls the workload of the compaction process. This server is called the primary server. If you run 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

You can use DCMC to administer Compactor in the following ways:

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

For more information on these topics, see DCMC Help.


Compactor Tasks Chapter 3: Compactor

Compactor Tasks

Iron Mo

The Compactor service removes redundant data from the Data Center. It also removes data that is older than set expiration parameters. To remove data, Compactor performs the following tasks:

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 according to rules set during Data Center installation

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 to process accounts, it verifies disk space on all servers that host HSM. Compactor cannot process an account unless all of the archive sets for the account are on disk. Therefore, there must be enough disk space to accommodate all of the archive sets for the account.
When Compactor verifies disk space, 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 space, Compactor writes an error message to the Application log and then stops.

Compactor also checks for available disk space before each account processes.

On disk-only Data Centers, all the archive sets for accounts 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

For each session, Compactor determines which accounts to work on.

If the Data Center uses a tape library for the Primary Tape Set, Compactor selects the Tape Account Group that has not been compacted for the longest period of time. The default time period is 15 days. However, you can use the DCMC to change the default. For more information about Tape Account Groups, see Tapes Groups and Tape Account Groups, on page 22.

If a Data Center does not use a tape library for the Primary Tape Set (if it is a disk-only Data Center, or if it uses Centera), Compactor begins work on accounts that have not been compacted in a set number of days. The default number of days is 15, but you can use the DCMC to adjust the number of days.

Normally, Compactor runs continuously, but you can start the Compactor service manually if you specify an account, tape, or Tape Account Group. You can also run Compactor service on canceled accounts. For more information about how to use switches to start Compactor., see DCMC Help.


Chapter 3: Compactor Compactor Tasks

Perform system analysis and repair

32 Co

To process an account on mirrored and clustered Data Centers, Compactor first locks the account from all other processes.

Compactor then verifies synchronicity between the archive sets in the account and the 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 inconsistencies still exist, Compactor marks the files that it cannot retrieve for deletion, and requests that the Data Center send notification to the Agent to resend those files.

Mark files as expired
To expire files, Compactor uses rules that technicians create during Data Center installation. These rules specify the following parameters:
• How long to keep data for cancelled accounts

• How long to keep files deleted from the Agent computer

• How long to keep files excluded from the Agent backup

• How many versions of a file to keep and how long to keep them

For more information about expiration rules, see File expiration overview, on page 33.

You can use DCMC to view and change the expiration rules. If you set an expiration rule value to -1, you turn off the rule.

Compactor runs through every version of every file for the selected account. If an expiration rule applies to a file, Compactor marks the file as expired. Because the expiration process runs approximately every 90 days, there are times when there are more versions of a file available than the rules might allow.

In configurations that use HSM, when the expiration process completes, Compactor copies archive sets from tape to disk. Compactor does not copy archive sets for accounts that are canceled and ready for compaction. Canceled accounts are processed first.

Repackage archive sets
After Compactor marks files as expired, it determines 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 server’s mirror. When Compactor works with files in an archive set, it 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. Compaction deletes the expired base and deltas. When a file has not expired, but is in an archive set with other files that Compactor must rebase or delete, Compactor copies the files to new archive sets. After the repackaging process, Compactor performs additional data integrity checks on the new archive sets.

Delete archive sets and database entries

After Compactor repackages all archive sets, it deletes the old archive sets from disk. During this process, Compactor also deletes the appropriate database rows for these files and archive sets.

Compactor does not delete archive sets from tape, but deletes information regarding the location of the archive set 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.


File expiration overview Chapter 3: Compactor

Migrate new archive sets to tape

Iron Mo

In configurations that use HSM, Compactor migrates new archive sets to the archive storage device. If you use a tape library, Compactor checks to see if there are four blank tapes in the library before it begins migration. Iron Mountain recommends four tapes because, by default, Tape Account Groups use four tapes. If the library does not have four blank tapes, Compactor writes an error message to the DCMaint log and pauses the service.

Notify the Agent about changes
After Compactor repackages or deletes archive sets, BackupServer notifies the Agent of the change. The next time the Agent connects to the Data Center server, the Data Center updates the file list with the new information from the compaction process. After Compactor deletes files, the Agent cannot restore the files. Therefore, the Agent must update the list of files available for retrieval.
After Compactor migrates all new archive sets, the process begins again. Compactor checks for available disk cache and selects the next account or Tape Account Group for compaction.

File expiration overview
To reuse disk and archive storage space, the Data Center use the expiration process to delete old data.
When technicians setup, the Data Center they specify parameters that define when data is “old” and ready for deletion. The file expiration rules have default settings created by Data Center Setup. You can accept the defaults if you are not sure of the parameters you need. The value -1 for any of the values turns off the expiration rule.

On a disk-only configuration, the file expiration rules keep your Data Center from running out of disk storage. On a server using HSM, file expiration rules minimize growth of data in storage; the disk is kept at an acceptable free space level by data migration. Monitor a disk-only configuration closely in the weeks after startup, and decrease the file expiration rules if disk space fills too quickly. On both disk-only and HSM configurations, if space is tightly limited, you need more aggressive file expiration rules. Use DCMC to change file the expiration rules.

Expiration rules and default settings

Expiration rules have the following default settings:

• Canceled - 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 - The minimum number of days that the Data Center retains a file after it has been deleted from the Agent. If a file is backed up and later deleted, you can usually retrieve the file with the Agent. However, if the Data Center expires and compacts the file, you cannot retrieve it. The default value is 90 days for disk-only configurations and 180 days for HSM configurations.

• Excluded -The number of days that the Data Center retains a file after the end-user excludes it from the backup list on the Agent. If you back up a file and then later exclude it from the Agent backup list, the next time Compactor runs on the account the file is expired and deleted. For disk-only and HSM configurations, the default value is zero days.

• RecentVersions and OldVersions - Used together to specify the number of versions of a retained file. 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.


Chapter 3: Compactor File expiration overview

Rule exceptions

34 Co

Data can remain on the Data Center for longer than the expiration rules imply. For example, on January 1st a user deletes a file from his or her computer. The file has been backed up to the Data Center. The user then performs a subsequent backup.

Compactor processes accounts every 90 days. The next time Compactor processes the user’s account is on April 15th. The expiration rule for deleted files is 90 days. As Compactor processes 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 the user deleted it from the his or her computer. This occurs because the expiration rule values and the number of days between Compactor runs for an account or Tape Account Group are minimum values. Data can remain on the Data Center longer than these values indicate.


PART II: DATA CENTER INSTALLATION

Chapter 4: Sizing Your Data CenterChapter 5: Preparing for InstallationChapter 6: Installing the Data Center SoftwareChapter 7: Integrating the Data Center with Enterprise Directory

4

SIZING YOUR DATA CENTER

About this chapter

Iron Mo

This chapter provides information that you can use as a guide to determine the hardware requirements for your Data Center.



How sizing affects your Data Center Sizing overview, on page 38

Minimum sizing estimates for the Data Center Sizing estimates, on page 39

Requirements for network bandwidth Network bandwidth requirements, on page 40


Chapter 4: Sizing Your Data Center Sizing overview

Sizing overview

38 Co

The hardware requirements for your Data Center depend on your user population, the number of servers you use, your Agent configurations, and your plans for the future For example, although you have licenses for 5,000 users or 500 servers, you might want to deploy hardware that serves 10,000 users or 1,000 servers so you can easily scale the Data Center to handle more users in the future.

You can use the sizing information in this chapter to determine the hardware requirements for your Data Center.

Assumptions for PC accounts
The information in this chapter assumes the following about PC accounts:
• First backup of each account is 1 GB of compressed data, on average. This number does not include common files that use 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 and the size of files your end users back up 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 the Data Center needs for archive sets. The number of files backed up influences the amount of storage space needed for SQL databases, database transaction logs and, if you run a standalone configuration, the database backups.
The sizing charts in this chapter were created with the assumption that end users would back up an average of 4,000 files per month with an average total compressed size of 150 MB per month. When you size 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 assumes the following about your server account:

• 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 on average 100,000.

• Number of delta files backed up monthly is 10,000 per server account.

• Average total account size is .9 GB of compressed data.

• Number of days archive sets remain on disk is 5 (HSM only).

• Tape capacity is 15 GB (HSM only).


Sizing estimates Chapter 4: Sizing Your Data Center

Effects of backed-up data from server accounts

Iron Mo

The number of files and the size of the files that server accounts back up, 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 you run 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.
For a table that compares each configuration type against each end user range overall, visit the Resource Center.

Sizing estimates
You can use the number of Agent accounts to estimate the size of a Data Center.
If your Data Center has variables not accounted for in this chapter, contact Corporate support for an customized sizing estimation.

For a table that compares each configuration type against each end-user range, visit the Resource Center .

Note

If you configure 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

• 200 GB per 1000 PC accounts for Data Centers with a Centera

• 2 TB per 200 server accounts for disk-only configurations

• 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

EMC Centera • 2 TB per 1000 PC accounts for disk-only configurations

• 2 TB per 200 server accounts for disk-only configurations


Chapter 4: Sizing Your Data Center Network bandwidth requirements

Application disk space requirements

40 Co

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

Microsoft® SQL Server® Application volume/folder

• SQL Server 2000 SP4 —1 GB

• SQL Server 2005 SP2 — 2 GB, excluding system and application database files

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

Account Management volume/folder • 8 GB

Data Center 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

Intel® Ethernet Adapter 1 GB per second

Network bandwidth requirements

When you consider the network load that results when you run your Data Center, focus on the number of Agents you deploy. You must have sufficient network bandwidth available for the Agents to communicate with the Data Center server.

If you have a mirrored configuration for your Data Center, each Agent must have access to both of the servers if the Agent cannot connect to its primary server. The mirrored servers must have access to sufficient network bandwidth to communicate with each other.

The following table lists the recommended network requirements.

Network element Network requirements

Network bandwidth between the Agent computer and each Data Center

1 megabit/second based on 5 MB to 6 MB of compressed data per user per day.

IP address One per Data Center

Network bandwidth between the two Data Centers (mirrored configuration)

1 megabit/second based on 5 MB to 6 MB of compressed data per user per day.


5

PREPARING FOR INSTALLATION

About this chapter

Iron Mo

This chapter explains how to prepare your server for a Data Center installation.



Tasks you need to complete before you install the Data Center software

Preinstallation tasks, on page 42

Information about configurations and licensing options

Evaluating configuration and license options, on page 42

Hardware and software requirements for the Data Center server

Data Center server requirements, on page 43

Requirements for storage solutions Storage solutions requirements, on page 45

Requirements for network connections Network requirements, on page 49

Requirements for security Security requirements, on page 51

How to install the required Microsoft software on the Data Center server

Installing and configuring Microsoft software, on page 52

How to prepare Support Center and the Account Management Website with MyRoamTM application for use

Support Center and Account Management Website preparation, on page 59


Chapter 5: Preparing for Installation Preinstallation tasks

Preinstallation tasks

42 Co

To prepare your Data Center for installation, complete the following steps:

• Evaluate the appropriate configuration and licensing for your organization.

• Review Data Center server requirements.

• Review storage solutions requirements.

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

The procedures for these tasks depend on your Data Center configuration. For example, a stand-alone Data Center has a different configuration than a mirrored Data Center, and a disk-only Data Center has a different configuration from a Data Center with Hierarchical Storage Manager (HSM).

To make the Data Center installation easier, and to organize your Data Center information, use the worksheets in Appendix A: Worksheets and Checklists on page 139.

Note

The Data Center supports the Account Management Website with MyRoam for Connected Backup Agents. If you use Legacy Agents only, ignore all references to the MyRoam application.

Evaluating configuration and license options
Before you install the Data Center, evaluate the deployment options and select the configuration and licensing agreement that is most appropriate for your information backup requirements. As part of this process, determine the following:
• Whether to use a stand-alone Data Center or mirrored pair(s)

• Your licensing needs

• The features that you need to deploy

The following sections explain these considerations.

Stand-alone and mirrored Data Centers

As you prepare to deploy the Data Center, decide whether to use a stand-alone Data Center with one server, or a mirrored Data Center. You also can use a clustered Data Center, which is similar to a mirrored configuration except that it has several mirrored servers.

The decision to use a stand-alone Data Center or mirrored pairs depends on the anticipated size of your Data Center and your hardware. Generally, a mirrored configuration requires two of everything that a stand-alone Data Center requires. The benefit of redundant data is server availability during maintenance downtime or in the event of a disaster.

Whichever configuration you select, you need an additional server to function as a Web server for Support Center, and optionally, the Account Management Website with MyRoam.


Data Center server requirements Chapter 5: Preparing for Installation

Licensing

Iron Mo

You must license every Data Center. You can purchase licenses for PC accounts, server accounts, or both. Before you install the Data Center software, you must obtain a permanent license . However, if you do not have a license when you install a Data Center, the Data Center Setup program creates a temporary license that expires in 30 days.

Your Data Center license give you access to optional features that your enterprise has chosen to implement. The license software also tracks the number of active users and servers on the Data Center and warns you when your contracted license agreement nears capacity.

Features
To change the features used at your Data Center or increase the number of end users that your Data Center services, contact Software Fulfillment at Iron Mountain to obtain a new license.
Data Center server requirements
This section describes the hardware and software requirements for Data Center servers.
Hardware requirements

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, request a customized assessment from your Iron Mountain Digital representative.

Important Notes:• Production-quality Data Center servers support only the Data Center software, and not

other applications on the servers.• Do not configure these servers as primary or secondary Microsoft Windows® domain

controllers. If you do, you place an additional performance burden on them, unless only the Data Center servers use the domain.


Chapter 5: Preparing for Installation VMware Support

Software requirements

44 Co

To install the Data Center software, your servers must have the following software.

For information about how to install Microsoft software, see Installing and configuring Microsoft software, on page 52. For Support Center and Account Management Website software requirements, see Web server preparation, on page 61.

Component Requirement

Operating system Any of the following Microsoft Windows Server U. S. English operating systems:

• Windows 2003 Standard and Enterprise Editions with SP 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 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: Connected® Backup does not support Microsoft® Windows® Small Business Server 2003 for the Data Center server.

Database • Microsoft® SQL Server 2000 SP 4 with hotfixes. SQL Server licensing as necessary.

• Microsoft SQL Server 2005 SP 2. SQL Server licensing, as necessary.

Important: Be sure you run Connected Backup Data Center 8.2 Hotfix 8a or later when you install or upgrade to SQL Server 2005.

Network Enable NetBios over TCP/IP.

The HostID.exe program requires this configuration to verify the Data Center server's MAC address against the Data Center license.

Note

If your Data Center supports more than 10,000 accounts, do not run Support Center and the Account Management Website on the same server.

VMware Support

You cannot install the Data Center on VMware. VMWare is supported on Web Servers hosting the Support Center and Account Management websites.


Recommended hardware for database backups Chapter 5: Preparing for Installation

Recommended hardware for database backups

Iron Mo

Stand-alone Data Centers use the Weekly Automatic Procedure to back up the SQL databases. For more information, see Chapter 13: Weekly Maintenance on page 115. You can perform these backups to disk or tape. If you want to usee a local tape drive and blank tapes to back up the SQL database (internal/external AIT2 or DLT tape drive or similar), you must install the tape drive. You also can use other methods to back up the SQL databases. Whichever method you use, back up your SQL databases regularly.

If you run a mirrored or clustered Data Center, the Data Center replicates the SQL databases between the servers. Therefore, the Weekly Automatic Procedure does not back up the databases. The complete mirroring of the databases on a mirrored Data Center increases the ease and minimizes the time needed to recover from data loss.

Note

If you set up a tape device for database backups, and you use a Windows Server backup to test it, SQL Server cannot use the same media that it used for the Windows Server backup.

Recommended naming conventions
When you choose names for your Data Center server(s), do not use the words BACKUP and UPDATE (and other keywords that Microsoft SQL Server uses) as part of the server name. Use of these words in a server name causes problems when the Data Center software attempts to perform SQL queries. Also, do not use spaces and special characters, such as hyphens (-), in the server name.
Running Data Center Setup locally
For the Data Center Setup Help to work, run Data Center Setup on a local drive. If you run the Setup remotely, the security settings in Microsoft do not allow access to the Help system.
Antivirus software and the Data Center
Before you start the Data Center, adjust your antivirus software to exclude the Data Center Customers folder from antivirus scans. Antivirus software might confuse the compressed and encrypted archives in the Customers folder with virus signatures. Most antivirus software would isolate the archives and, as a result, corrupt them. If the archives are corrupted, the Data Center can not gain access to them and the data is lost.
Archived files that have been infected with a virus do not affect Data Center servers. The nature of the encryption and compression techniques you use during backup inoculates the virus so that it does not affect the servers. Connected DataProtector/PC software, however, does not protect end users who might recover an infected file. If the Agent backs up a file that is infected, the Agent recovers the file as infected. The only way to accurately detect and remedy infected files is to use antivirus software to scan the Agent client computer.

Storage solutions requirements

To expand available archive storage, you can add a secondary storage device to your Data Center. The Data Center supports the following types of storage.

• Disk — Primary storage

• HSM — Secondary storage


Chapter 5: Preparing for Installation Storage solutions requirements

Disk storage solutions

46 Co

Disk solutions directly connect with the Data Center rather than through HSM. Connected Backup supports the following disk-based solutions for primary storage:

• Network Attached Storage (NAS)

• Storage Attached Network (SAN)

Network Attached Storage
If the Data Center uses NAS devices for archive storage, follow the instructions from the NAS vendor to install and connect the device 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 prompts you for the share name of the NAS device on the Data Center server. To keep track of this information, see Appendix B: Data Center Installation Worksheets on page 143.

CAUTION

Do not install the SQL Server database files on a NAS device. Microsoft and NAS vendors support this configuration, but it has not been proven as an efficient or a stable configuration for Connected Backup.

The Data Center domain account, CNTD_DCServices, must have full permissions on the NAS volume. For more information, see Security requirements, on page 51.

Storage Attached Network
The Data Center views Storage Attached Network (SAN) as a logical drive. If you use a SAN with your Data Center configuration, during Data Center Setup, select the drive letter associated with the SAN as the Customers volume.
Unlike NAS devices, you can install the SQL database files on a SAN, but it is not required. A SAN does not require that you give permissions to the CNTD_DCServices account because Data Center Setup configures the CNTD_DCServices account to gain access to the Customers folder on the SAN.

HSM storage solutions

If you install HSM, you need an archive storage device. For a current list of supported devices, visit the Resource Center. In general, the Connected Backup solution supports tape libraries, EMC Centera, and Distributed AML Server (DAS). This section contains information about how to prepare each device for HSM.


Storage solutions requirements Chapter 5: Preparing for Installation

EMC Centera

Iron Mo

If the Data Center uses EMC Centera as an archive storage device, see the documentation that came with the device for information about how to install the device and connect it to the Data Center servers. To view a list of supported Centera software and hardware, visit the Resource Center.

During Data Center Setup, enter the following information.

For more information, see the Data Center Setup Help.

To configure HSM to work with Centera, Data Center Setup uses the following settings:

To modify these settings, contact Corporate Support.

Centera Addresses IP address(es) of the Centera. You can record the IP address(es) in Appendix B: Data Center Installation Worksheets on page 143.

Handler count Number of threads between Centera and the Data Center. If you use a 100 megabit network connection between Centera and the Data Center, use 10 threads. If you use a gigabit connection between Centera and the Data Center, use 20 threads.

Main Profile BackupHSM uses the Main profile to write and read data to and from the Centera. The default path and name for the Main profile is: \CenteraProfiles\connected_main.pea, but you can edit it. You can record the Main profile path and name on the Appendix B: Data Center Installation Worksheets on page 143. For information about how to set up a profile before running Data Center Setup, see 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 Centera. If Centera can not purge, BackupHSM uses the Garbage Collection utility to delete the data from Centera. The default path and name for the Purge profile is: \CenteraProfiles\connected_purge.pea, but you can edit it. You can record the Purge profile path and name on the Appendix B: Data Center Installation Worksheets on page 143. For information about how to set up a profile before running Data Center Setup, see the Resource Center procedure Using Centera Access Profiles with the Data Center (document 1657).

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 you set up the Data Center to use a tape library, before you install HSM, you need to have numeric barcode tape labels and a differential SCSI host adapter and cable available.
CAUTION

The host adapter and its tape drives should have SCSI parity enabled. Otherwise, you might experience problems with unreadable tapes and data loss.


Chapter 5: Preparing for Installation Storage solutions requirements

48 Co

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. To determine the correct numbering sequence, see the documentation provieded with your tape library.

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 0

Drive 1 2

Drive 2 3

Drive 3 5

SCSI bus guidelines for multiple SCSI busses

Use the following guidelines for SCSI Busses and IDs, for multiple SCSI busses:

• Connect tape drives to busses in a 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.

With Microsoft Windows registry editor, you can verify and edit the SCSI mapping in the following registry key:

Tape Drive Number SCSI Bus Number SCSI ID Number

Drive 0 Bus 0 0

Drive 1 Bus 0 1

Drive 2 Bus 1 0

Drive 3 Bus 1 2

Drive 4 Bus 1 3


Network requirements Chapter 5: Preparing for Installation

Iron Mo

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI

Removable Storage Manager

CAUTION

Editing the Windows registry is a procedure that can render your server inoperable. Exercise extreme caution when you edit the registry. For assistance, contact Corporate Support.

The Removable Storage Manager (RSM) is a Windows Server component that is not compatible with the Data Center HSM service. For this reason you must disable RSM.

To disable RSM for specific devices, complete the following steps:

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 appear in the right pane.

4. In the right pane, right-click a tape library or drive for HSM use, and then 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 HSM tape drive.

Distributed AML Server
If you configure the Data Center to use a Distributed AML Server (DAS) as an archive storage device, for proper installation and connection to the Data Center server(s), see the documentation from the DAS vendor.
For information on how to configure SCSI busses and IDs for the DAS, see SCSI ID guidelines for a single SCSI bus, on page 48 or SCSI bus guidelines for multiple SCSI busses, on page 48.

To disable RSM for tape drives used by the DAS, see Removable Storage Manager, on page 49.

During your Data Center installation, the installation program prompts you for the DAS server name and the client name. The client name in a DAS configuration refers to the server. For example, the Data Center server, attached to the DAS as it was named during the DAS installation. You can keep track of this information in the Data Center Installation Worksheets found in Appendix B.

Network requirements
The Agent must be able to communicate with the Data Center. Also, if you run a mirrored configuration, the Data Center servers must be able to communicate with each other. For information on network bandwidth requirements, see Network bandwidth requirements, on page 40.
When you set up a mirrored pair, assign a unique IP address, or optionally a DNS name, to each server. Before you install the Data Center software, establish connectivity between the pair of servers.

Enable NetBios over TCP/IP

On the Data Center computer, enable NetBios over TCP/IP. The HostID.exe program requires this configuration to verify the Data Center server's MAC address against the Data Center license.


Chapter 5: Preparing for Installation Network requirements

Ports

50 Co

If a firewall or router restricts communications between mirrored servers, each server must be able to connect to the following Data Center server, Web server, and Agent ports on its mirror:

Data Center server Ports

Windows UDP and TCP — port 135

Windows UDP — ports 137 and 138

Windows TCP — port 139

SQL Server TCP — port 1433

Agent registration, backup, retrieve, Heal TCP — port 16384

Data replication TCP — port 16385

RPC connections for Data Center services TCP — ports 16400 - 16406

Web server Ports

IIS to Account Management Website Apache Tomcat Connector

TCP — port 16389

SSWS (Account Management Website Tomcat) TCP — port 16390

Account Management Website Tomcat Shutdown Listener

TCP — port 16391

Agent Ports

Agent Service SOAP Server TCP — port 16386

Agent Service Media Mode SOAP Server TCP — port 16387

Background Notification Process Listener TCP— port 16388

CompoundFileAnalyzer (CFA) and the Agent service. The Agent uses CFA to analyze and rebuild email files.

TCP— port 16392

Note

If a firewall or router restricts communications between the Agent and the Data Center servers, each server must permit a TCP connection on port 16384.

File and Printer Sharing for Microsoft Networks

You must enable the File and Printer Sharing for Microsoft Networks property on the network connections that the Data Center uses. If you do not enable this property, some backup and replication components do not work.


Security requirements Chapter 5: Preparing for Installation

Security requirements

Iron Mo

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 few permissions, to run the Data Center services and components.

During installation, Data Center Setup creates these accounts, and uses the names and passwords that you specify to create these accounts. To change the names of these accounts, be sure to keep track of the new name and password of each account for future use. Choose account names that accurately reflect the purpose of the account. Alternatively, you can accept the default account names created during installation.

Domain accounts
The Data Center installation creates the following domain accounts:
You can create domain accounts before you run Data Center Setup. However, the accounts must be in the same domain, especially in a mirrored configuration where servers must communicate with each other.

Whether you create the domain accounts manually or automatically, Data Center Setup prompts you to provide a password for each account.

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.

For more information about how to install and invoke DataBundler, see Installing DataBundler, on page 94.

Important

To log on to the server, use an account that has administrative privileges and the permission to create domain accounts that can run Data Center Setup. If you do not, the accounts that you created do not have the necessary permissions to start services, authenticate attempts to log on to Support Center and Account Management Website, or run DataBundler.

Domain account for SQL server

CAUTION

The domain accounts that Data Center Setup creates to run the Data Center have few permissions. Do not use these accounts to log on to the Data Center server.

The Microsoft SQL Server requires a domain account with administrative privileges to run. For more information, see SQL Server installation guidelines, on page 58.


Chapter 5: Preparing for Installation Installing and configuring Microsoft software

Installing and configuring Microsoft software

52 Co

Before you install the operating system or SQL Server, verify the following information:

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

• You use the latest version device drivers revision according to vendor recommendations.

• You have the most current technical support contracts.

CAUTION

Do not install any software that Connected Backup does not support. If you do, the Data Center server might not perform at an optimal level.

When you install the required software, follow the guidelines in the rest of this chapter to prepare your server for a Data Center installation.

For more information about Data Center software requirements, see Data Center server requirements, on page 43.

Windows Server installation guidelines

When you install Windows Server, use the following guidelines to prepare the Windows server for a Data Center installation:

1. Verify that you configured Windows Server with the U.S. date format (MMDDYY).

2. When asked about disk partitions, perform the following tasks:

• Delete any disk partitions, even if you remove a system partition. However, do not delete any proprietary computer vendor partitions you created for configuration purposes (for example, an EISA partition).

• Create an 8 GB or larger boot partition (RAID or other redundant storage works best for the boot partition, but not essential).

• Create a page file that has double the equivalent amount of installed RAM.

3. Install Windows in the new partition. Specify NTFS formatting for the system or boot partition.

4. When Windows Server Setup asks about the 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).

5. When Windows Server Setup asks you about the server type, if domain controllers exist on the network, select stand-alone server. If the domain controllers do not exist on the network, select the domain controller options.

6. When Windows Server Setup asks you about the network configuration for Windows 2000 Server, accept the following default selections:

• The computer will participate on a network

• Wired to the network


Installing and configuring Microsoft software Chapter 5: Preparing for Installation

Iron Mo

7. Select one of the following options when you install a Windows server:

Windows 2000 Server

• Include Internet Information Server (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 only the Connected Backup Agents. Accept all default Setup options for IIS except FTP and Gopher. Verify that you selected World Wide Web Service.

• Select the workgroup option (instead of domain) that has the default workgroup name WORKGROUP. For more information about how to perform this task after the initial Windows installation, see Assign the server to an existing domain on Windows 2000, on page 55.

Windows 2003 Server

a. Select Typical settings.

b. Add the server to the appropriate domain during the initial Windows 2003 Server installation.

c. Install IIS separately after you install the server. For more information, see Install IIS on Windows 2003 server, on page 54.

8. To set up IIS on your Web server, see Web server preparation, on page 61.

9. When Windows Server Setup prompts you for the network protocols, install the TCP/IP protocol. The Data Center software does not use IPX/SPX, though you can install it to use for administrative purposes.

Windows server configuration guidelines
After you install Windows Server, configure and prepare the server for the Data Center installation:
• Enable IIS installation

• Install IIS Windows 2003 server, and the Web server, if applicable

• Configure IIS Windows 2003 server, and the Web server, if applicable

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

• Verify the connection for remote computers

• Make emergency repair disks

Enable Internet Information Server (IIS) installation

When you install Windows on the Web server that hosts Support Center or the MyRoam application, be sure to enable the IIS installation so that you install IIS at the same time. If you have not installed IIS on the Web server, use the Windows installation program to install it.

The Data Center Setup program installs Support Center and the MyRoam application to the default Web server location that you specify under the following Windows registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\ Parameters\Virtual Roots



54 Co

Before you install the Data Center software, you can change the location of where you install Support Center and MyRoam. To do so, change your Web server location using IIS Manager.

To access Support Center and MyRoam with Anonymous Access rights, IIS installation creates a default user account named IUSER_servername. By default, this account might not have sufficient permissions to gain access to all files.

To grant yourself the correct permissions, complete one of the following tasks:

• 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) that you create during Data Center Setup and give this account Full Control permissions to the Temp folder (depending on your operating system, either WINNT\Temp or Windows\Temp).

Install IIS on Windows 2003 server
You must install IIS on a Windows 2003 server to host Support Center or the Account Management Website application.
To install IIS on a Windows 2003 server, complete the following steps:

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

3. In the Application Server window, select Internet Information Services (IIS), and then 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 to install IIS on the Windows 2003 server.

Configure IIS on Windows 2003 server

If Web server runs Windows 2003 Server, use IIS Manager to verify that you enabled active server pages and to ensure that MyRoam functions properly.

To ensure the proper function of MyRoam, complete the following steps:

1. Open IIS Manager.

2. Right-click the server name and click Properties.

The Properties dialog box appears.

3. Click MIME Types.

4. Click New.

5. Add the file type .out with the MIME type Application/octet-stream.

6. To add the new MIME type, click OK.

7. Use Services Management to stop IIS Admin Service.

8. Use Services Management to start World Wide Web Publishing Service.



Create data partitions

Iron Mo

To store your SQL databases and archive files, create data partitions. If you have three RAID volumes, typically you use a partition to store the SQL databases, a partition to store the SQL database transaction logs, and a third partition to store the archive files.

The Data Center creates a shared volume named VolumeX$,

where

X represents the drive letter for the volume(s) on which you store the user’s archives.

If necessary, use the following guidelines to modify the volume:

• The CNTD_DCServices account must have the Change permission. The CNTD_CDMaker account must have the Read permission. The account used to log on to the Data Center must have administrator privileges that grant full permissions to these shares.

• Any accounts with access to the user’s archives, such as those accessed by DataBundler, must be in the same domain.

Assign the server to an existing domain on Windows 2000
To assign the server to an existing domain, complete the following steps:
1. Right-click My Computer, and then click Properties.

The System Properties window opens.

2. Click the Network Identification tab and then click Properties.

The Identification Changes window opens.

3. In the Member of section, enter an appropriate domain name in Domain. Keep all servers in the Data Center configuration in the same domain.

The Domain Username and Password window appears.

4. Enter a user name and password for an account that has administrator privileges in the domain. For more information, see Security requirements, on page 51.

5. When you restart the server, log on to an account with administrator privileges in the domain that you specified in this procedure. Use this account to set up the Data Centers.

Note

Do not use the Data Center servers as domain controllers. It places an additional performance load on them.

Update the lmhost configuration

For mirrored Data Centers that you do not configure to use DNS, add a line at the bottom of the lmhosts file to describe the mirror of the server you install. Doing so, forces the IP address of the mirrored server to pre-load in the NETBIOS cache at server startup.

The lmhosts file is located in the :\WINNT\System32\drivers\ folder.



56 Co

If you do not have an lmhosts file, create that file using the following lmhosts.sam sample file. For more information, see the Microsoft documentation. After you create the lmhosts file, use a text editor such as Notepad to open it. At the bottom of the file, the commands appear in the following format:

<IP><tab><server name><tab>#PRE

For example, 111.111.111.111 ABCCorporation_ #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. When the installation is complete, you must install the device drivers for the tape drives.
To install the device drivers, complete the following tasks:

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.

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 vendor’s Web site.

6. Reboot the server so that Windows reassigns tape device numbers to the tape library.

Synchronize date and time

If you run a mirrored Data Center configuration, 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 you run a clustered Data Center configuration, 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.

You must synchronize the time values, which can be different by a maximum time of 30 seconds. If the time values are different by more than 30 seconds, errors occur.

Note

To synchronize the time between the two servers, use any time-synchronization tools that run as a service under Windows.



Verify mirrored servers

Iron Mo

If you run a mirrored Data Center configuration, verify that each server can write files to its mirror. On each server, map a network drive from the server to its mirror. Map the drive to the mirrored server's data partition, as explained in the section Create data partitions, on page 55. Since you have logged in as a domain administrator, you can type the path:

\\<computer>\<drive letter>$

The <drive letter> variable is the drive 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 finish with the test. Test this process on the mirrors in each pair.

Verify the connection from remote computers
Verify that end-user computers can ping each Data Center server. If you configured your firewalls to prohibit a “ping” connection from a computer to the Data Center, you can skip this verification.
At a DOS command prompt on a user's computer, use the command ping <ip>.For example, ping 111.111.111.111, to verify that you can ping each Data Center.

Verify that a computer you want to use for Help Desk tasks can connect to 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

Create a emergency repair disk on Windows 2000 server

After you install and configure your Windows 2000 server(s), but before you install the Data Center software, create an emergency repair disk for each Data Center.

To create an emergency repair disk for the Data Center, complete the following steps:

1. Click Start > All Programs > Accessories > System Tools > Backup.

The Backup and Restore Wizard dialog box appears.

2. Insert a CD or DVD.

3. In the wizard dialog box, click Tools > Create an Emergency Repair Disk.

4. Follow the instructions in the wizard dialog boxes. When the wizard prompts you, select Back up the registry.

5. After you create the repair disk, remove and label the CD or DVD.


Chapter 5: Preparing for Installation Installing and configuring SQL Server

Create a emergency repair disk on Windows 2003 server

58 Co

After you install and configure your Windows 2003 server(s), but before you install the Data Center software, create an emergency repair disk for each Data Center.

Use the following procedure to create an emergency repair disk:

1. Click Start > All Programs > Accessories > System Tools > Backup.

The Backup and Restore Wizard dialog box appears.

2. Insert a CD or DVD.

3. In the wizard dialog box, click Advanced Mode.

The Backup Utility window opens.

4. Click Automated System Recovery Wizard button.

The Automated System Recovery Preperation Wizard opens.

5. Follow the instructions in the wizard dialog boxes. When the wizard prompts you, select Back up the registry.

6. After you create the repair disk, remove and label the CD or DVD.

Installing and configuring SQL Server
Microsoft has implemented a processor-based licensing model to simplify licensing SQL Server. Under this new model, you acquire a Processor License for each processor that runs SQL Server. If you make a processor inaccessible to all operating system copies on which the SQL Server software runs, you do not need a software license for that processor.
A Processor License includes a connection for an unlimited number of devices from inside the corporate LAN or WAN, or outside the firewall. You need only the Processor license. You do not need to purchase additional Server licenses or Client Access Licenses (CALs).

If you install SQL Server on the Web server or the DataBundler computer, install only the Client Networking Utility. You do not need to install SQL Server fully.

Connected Backup does not support an installation of SQL Server on a SQL Server farm to use with the Data Center. You must install SQL Server locally for use with the Data Center

SQL Server installation guidelines

To install SQL Server, use the following guidelines:

• The Data Center server supports only the Default instance of SQL Server 2005.

• When SQL Server Setup prompts you, select Install SQL Server Components, and then Database Server, Standard Edition or Enterprise Edition.

• When SQL Server Setup prompts you to specify the disk drive for the SQL Server installation path, enter the SQL database partition that you created in the section, Create data partitions, on page 55.

• Verify that SQL Server allows Windows authentication. Create a domain account that has local administrator privileges for SQL Server to run. Use the same logon account for all SQL Servers in your Data Center.

• If you run a mirrored or clustered Data Center, enable SQL Server Agent.

• When the installation finishes, apply SP2 for SQL Server 2005 on the server.


Support Center and Account Management Website preparation Chapter 5: Preparing for Installation

SQL Server configuration tasks

Iron Mo

Perform the following SQL Server configuration tasks:

• To get additional software upgrades or hotfixes and install them, visit the Resource Center.

• Verify that SQL Server service runs.

For SQL Server 2000, register the server:

1. Open the Enterprise Manager console.

2. Click Action > New SQL Server Registration to register the current server.

3. When prompted, type the server name.

4. Select Use Windows Authentication.

5. Log on to the SQL databases on the Data Center servers with a domain account.

For SQL Server 2005, connect to a server:

1. Start SQL Server 2005 Surface Area Configuration.

2. Click Surface Area Configuration for Services and Connections.

3. Expand MSSQLServer > Database Engine in the left pane.

4. Click Remote Connections in the left pane.

5. Select Local and Remote Connections in the right pane.

6. Select Using both TCP/IP and named pipes. Click OK

Support Center and Account Management Website preparation

The Data Center software includes two Web-based applications:

• Support Center — Lets you administer and manage your accounts.

• Account Management Website — Lets you download PC Agent software and manage account information. If you enable the optional MyRoam® application, you can retrieve files over the Internet.

If you use the Connected Backup and Connected DataProtector/PC® products, you can install the Account Management Website and use MyRoam. If you use only the Connected DataProtector/SV™ product, ignore all references to the Account Management Website and MyRoam. You cannot use these applications with the Connected DataProtector/SV Agents.

For more information about how to create Agent configurations, see Support Center Help.

System requirements

Because of the added workload from Support Center and Account Management Website activities, and because of security considerations with a Web server, install Support Center and Account Management Website on a Web server, separate from the Data Center server.


Chapter 5: Preparing for Installation Support Center and Account Management Website preparation

Hardware requirements

60 Co

Your Web server must meet the following minimum hardware requirements to run Support Center or the Account Management Website:

Computers that have access to Support Center or the Account Management Website must meet the following hardware requirements:

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


Processor 300 MHz or greater

RAM 512 MB minimum, 1 GB recommended

Software requirements

Before you install the Support Center and Account Management Website software, your Web server must have the following software installed:

For information about how to install this software, see Windows Server installation guidelines, on page 52.


Operating system The following Microsoft Windows Server operating systems:

• Windows 2003 Server

• Windows 2000 Server with Service Pack (SP) 4

Database The following SQL Server RDBMS operating systems:

• Microsoft SQL 2000 Client Networking Tools with SP 4

• Microsoft SQL 2005 Driver with SP 2

Internet The following software:

• 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


Support Center and Account Management Website preparation Chapter 5: Preparing for Installation

Requirements for accessing Support Center and Account Management Website

Iron Mo

Computers with access to Support Center and the Account Management Website, must meet the following software requirements:

Note

You can install Support Center and the Account Management Website on VMware configured to meet the existing system requirements. Open Internet Explorer (version 6.0 or later) and run either Web application. Supported versions of VMware include VMware ESX 2.5.1, 2.5.2, 2.5.3, and 3.0.1.


Operating system 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, use Java version 1.5.0_11 or later.

Web browser Internet Explorer 6.0 or later

Web server preparation

Before you can install Support Center and Account Management Website, you must configure your Web server properly. You must install the software in the following order:

1. Windows 2003 Server or Windows 2000 Server, SP 4. For more information, see Windows Server installation guidelines, on page 52 . Verify that the Windows Server installation includes Internet Explorer version 6.0 or later.

2. Microsoft SQL 2000 Client Tool SP 4 or SQL Server 2005 SP 2. For more information, see Installing and configuring SQL Server, on page 58.

3. Microsoft Internet Information Server version 5.0 or later.

4. Install Support Center and the Account Management Website on the Web server.

CAUTION

If you use the Microsoft IIS Lockdown tool to secure IIS, the URLScan filter might cause problems in Support Center or Account Management Website. If possible, do not install the filter on the Web server. If you must use the IIS Lockdown tool, back up your IIS state prior to using the tool. That way, you can recover your data if IIS Lockdown causes problems with the Web applications.


Chapter 5: Preparing for Installation Enabling MyRoam

Regional settings

62 Co

Be sure to set the default locale and the current locale of the Web server to English (United States).

To locate and verify the regional settings, complete the following steps:

1. On the Web Server, click Start and then click Settings.

The Settings dialog box appears.

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 English (United States).

Enabling MyRoam
MyRoam 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 their computer.
To use the MyRoam application, users must log on to the Account Management Website .

License and permission requirements
To allow users to use the MyRoam application, enable the MyRoam feature. You can enable the MyRoam feature in your top-level community. You also can enable or disable this feature in individual subcommunities.
To enable the MyRoam feature in one or more communities, you must install or enable the following components:

• If you host your own Data Center, you need a license for the MyRoam feature installed on the Data Center server. If your current license file does not include the MyRoam feature, contact Software Fulfillment to purchase this license.

• To enable the MyRoam feature in a community, you need the technician permission, Allocate Licenses to Sub-Communities enabled.

• To enable the MyRoam feature for Agent configurations, you need 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. For procedures that explain how to install software on the Data Center server, see Support Center and Account Management Website preparation, on page 59.


Enabling MyRoam Chapter 5: Preparing for Installation

Enabling the MyRoam feature

Iron Mo

To enable the MyRoam feature, you must enable it for each community and each configuration in the community that needs access to this feature.

To enable MyRoam, complete the following steps:

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.

8. Select Options.

9. In the Account Management Options section, select the option, Allow end users to retrieve files using the MyRoam®feature.

10. Click Finish.

Note

In this release, only PC Agents support the use of the MyRoam feature.


6

INSTALLING THE DATA CENTER SOFTWARE

About this chapter

Iron Mo

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 how to upgrade your server(s) to version 8.2.



How to install the Data Center server software Installing the Data Center software, on page 66

How to verify that the installation completed successfully

Verifying Data Center installation, on page 67

Tips to help you troubleshoot an installation that had errors

Troubleshooting Data Center, on page 71

How to install the software for Support Center and the Account Management Website application

Installing Support Center and Account Management Website, on page 72

Additional Data Center configuration tasks Configuration tasks, on page 73


Chapter 6: Installing the Data Center Software Installing the Data Center software

Installing the Data Center software

66 Co

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.

Do not install the Data Center software until you have completed all installation and configurations tasks in Chapter 5: Preparing for Installation on page 41. Before you start the Data Center installation, take the time to fill out the worksheets and checklists in Appendix A: Worksheets and Checklists on page 139. By having this information available, you can simplify your Data Center installation..

Running Data Center Setup

CAUTION

Data Center Setup creates a Master Encryption Key (MEK). Store this key in a safe place. You might need the MEK if you reinstall the Data Center software.

To install the Data Center software, complete the following steps:

1. Log on to the server as a user with administrator privileges.

2. In Windows Control Panel, set the Regional Options setting to English, United States on all Data Center servers.

3. Run Data Center Setup to install a stand-alone Data Center or a mirrored Data Center (a pair of mirrored servers or an entire cluster).

You can include or omit Hierarchical Storage Manager (HSM), as required. You also can use Data Center Setup to install Support Center and optionally, the Account Management Website, on the Web server.

When you begin the installation process, Data Setup determines whether your system meets the configuration prerequisite requirements. If your system does not meet the requirements, Data Center Setup prompts you to correct the configuration.

4. If your system meets the installation prerequisites, continue to follow the installation step by step.

If you have questions about any step, click Help in the window for information about that stage of the installation process.

5. After you install the software on each server in your Data Center, see Verifying Data Center installation, on page 67 for a list of items to verify that you installed the software successfully.

Important

For the Data Center Setup Help to work properly, you must run Setup on your local drive. If you run Setup remotely, the security settings in Microsoft prevent you from having access to the Data Center Setup Help system.


Verifying Data Center installation Chapter 6: Installing the Data Center Software

Backing up certificate files

Iron Mo

After you install the Data Center, back up the certificate files that the software uses. Typically, these files do not change. Therefore, back up these files only once. Back up the following .pem certificate files:

• PrivateKey.pem, located in :\DataCenter

• Certificate.pem, located in :\DataCenter

• dh1024.pem, located in :\DataCenter

• CAfile.pem, located in :\DataCenter\Configuration

Data Center reinstallation
If, under the guidance of Support, you must reinstall the Data Center software, you must understand what reinstallation can and cannot accomplish.
Do not reinstall the Data Center software without the guidance of Support. There are only a few reasons to reinstall the Data Center. Therefore, consult Support to confirm that reinstallation is the best solution.

After you reinstall the Data Center software, the installation affects the software and files in the following way:

• Uses the same version of the Data Center software that currently runs on the Data Center.

• Creates the MEK during the initial Data Center installation to reinstall the Data Center software.

• Has no effect on the SQL databases.

• Has no effect on the archive sets.

• Has no effect on the Agent configuration files.

• Modifies Windows registry settings pertaining only to Connected Backup software.

• Replaces the Data Center software application files.

• Provides privileges for Windows registry keys, file shares, file directories, and databases. Reinstallation does not take away any privileges.

Verifying Data Center installation

To ensure that you installed the Data Center, verify the following components:

• You installed the Data Center software properly.

• BackupServer operates properly.

• HSM (if selected) operates properly.

• Mirror site replication (mirrored or clustered configuration) operates properly.


Chapter 6: Installing the Data Center Software Verifying Data Center installation

Verify installation of Data Center software

68 Co

You must verify that you installed the Data Center software properly.

To verify the proper installation of the Data Center software, complete the following steps:

1. Log on to the same account that you used to install the Data Center software.

2. Use Windows Control Panel, Services to verify that the following services are in the list and running:

− Backup Server

− DC Alerter (if used). If you did not configure the SMTP settings during installation, the DC Alerter 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 did not start, restart the server and check the services again in Windows Control Panel, Services.

The services must start when you restart the server.

4. Verify that the services for your Data Center run from the Data Center Management Console (DCMC). Click Start > All Programs > Data Center > Data Center Management Console.

For instructions on how to add a Data Center to DCMC, see DCMC Help.

5. In DCMC, expand the Events node and click Application. Look at the events to see whether BackupServer, DCAlerter, PoolServer, ReplicationServer (if mirrored or clustered), IndexServer, Compactor, HSMPurge, and Backup HSM (if used) have started.

6. Verify that the event log has no warning or error events in it.

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 warnings are typical before and during the time you installed the mirrored pair of Data Centers.


Verifying Data Center installation Chapter 6: Installing the Data Center Software

Verify correct BackupServer operation

Iron Mo

To verify correct BackupServer operation, connect to the server(s) and use a test account to perform an actual backup and file retrieve.

To install a sample user account onto a client and then backup and retrieve data, complete the following steps:

1. Use Internet Explorer to log on to Support Center.

2. Use Support Center to create an Agent Setup file. Include rules that select a small number of files to back up.

For instructions that explain how to create an Agent configuration and distribute it to clients, see Support Center Help.

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

4. If you use a Server Agent, select the Backup Set tab, select a few small files to back up, and click Backup Now.

The Agent initiates a backup and the backup completes successfully.

5. If using a PC Agent, do the following:

a. Proceed through the installation sequence until the installation process prompts you to select files for backup. Select Let me select which files and/or directories to back up.

b. Continue until the installation process and, at the prompt, begin the scan. 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.

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


Chapter 6: Installing the Data Center Software Verifying Data Center installation

Verify HSM operation

70 Co

If you use HSM, verify that BackupHSM and HSMPurge run properly by forcing a migration of data on each server to the secondary tape sets. However, in a production environment, migrations occur automatically. Therefore, you do not have to force a migration manually in a production environment.

To verify the HSM operation, complete the following steps:

1. Start DCMC.

For more information about how to add a Data Center to DCMC, see DCMC Help.

2. If you use a tape library, be sure to insert and label the tapes.

3. In DCMC, force a migration.

For instructions on how to force a migration, see DCMC Help.

4. Use DCMC to view the Application and DCMaint event logs.

A blue event indicates a successful migration. The event log should contain no BackupHSM warning or error events.

Verify mirror site replication

Unless you run a stand-alone Data Center, test your mirrored Data Center by verifying replication. To test replication, force a failover situation.

To verify mirror site replication, complete the following steps:

1. Use DCMC to stop the BackupServer service on the first Data Center server, as explained in DCMC Help.

2. Using the Agent that you installed on the test computer to verify the BackupServer operation, complete the following steps:

a. Click the Retrieve tab in the Agent user interface.

b. Select a file to retrieve.

c. Click Retrieve Now.

The Agent uses the mirror Data Center server to retrieve the file.

For more information on how to retrieve a file, see Agent Help.

3. Use DCMC to 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 2. When you click Retrieve, the Agent uses the mirror Data Center server to retrieve the file.

This operation confirms that ReplicationServer replicated the account registration information and the data on the mirror Data Center server.

6. Use DCMC to restart BackupServer on the second Data Center server.

7. In Windows Control Panel, use Add or Remove Programs to remove the Agent on the test computer.

8. Delete the temporary folder and the files you used for the verifications.


Troubleshooting Data Center Chapter 6: Installing the Data Center Software

Troubleshooting Data Center

Iron Mo

Tape library or SQL Server setup problems cause most errors or warnings in the event log. You can use the descriptions in the event log to diagnose these problems.

If the event log reports tape library problems, ensure that you properly turned on the tape library, connected the the tape library with the correct cable, and properly installed the differential SCSI adapter. Follow the instructions in the event log. Before you call the tape library vendor for hardware support, try to back up your data again, as some problems correct themselves with a subsequent backup.

Troubleshooting problems with BackupServer
If the Agent reports an error 109 or error 102 (with associated text), the Agent cannot contact BackupServer or the communications link between the Agent and the Data Center does not work. In such a situation, use the following suggestions:
• Verify the test computer can ping the Data Center server(s).

• Verify that you properly configured all firewalls to allow a connection to port 16384 on the Data Center server(s) from the test computer to all IP ports.

• Use DCMC to verify that BackupServer runs on each server.

• Verify that you entered the correct IP address(es) in the test Agent configuration. For a PC Agent, check the Agent settings. For a Server Agent, use the Agent Settings node in Support Center to check the Agent settings.

• Check the Data Center Application and DCMaint event logs for messages.

You might encounter another problem, for example, the Agent might report an “Internal Server Error.” Review the Data Center Application event log (for mirrored sites, look at the correct server).

Checking the Data Center server account
Verify that the NT user account, under which the Data Center server runs, is a domain account with administrator privileges.
To determine the account under which the Data Center server runs, complete the following steps:

1. Open Windows Control Panel and open Services.

2. In the details pane, right-click BackupServer and click Properties.

3. On the Log On tab, verify that the account name in the This Account box is an account as described in Security requirements, on page 51.

Troubleshooting HSM problems

When you try to label the first tape, you might encounter problems if you did not configure the tape drives or you configured the tape drives improperly.

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.


Chapter 6: Installing the Data Center Software Installing Support Center and Account Management Website

Troubleshooting attached tape library problems

72 Co

If, during installation, Data Center Setup does not recognize an attached tape library, verify the following items to check whether you installed and configured the tape library properly:

• Verify that Connected Backup supports the tape library that you want to use. For a list of tape libraries and tape drives that the Data Center software supports, visit the Resource Center and see the Supported Archive Storage Devices article.

• Be sure that the operating system can detect the tape library, has a medium changer, and has at least one tape drive in the Device Manager list.

• Disable the Removable Storage Manager (RSM), a Windows Server component for the tape library and all tape drives associated with it. For instructions on how to disable RSM for tape libraries and tape drives, visit the Resource Center and see the HSM Tape Library Storage Solutions article.

• Verify 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

• Install the Data Center first to map Support Center to your Data Center databases. Support Center uses Port 80 to connect to the Data Center 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 server root location (by default, the/inetpub/wwwroot folder).

• To install Support Center and Account Management Website software, log on to the server with administrator privileges.

• When you begin the installation process, Setup determines whether your system meets the prerequisites for the configuration.

− If your system does not meet the prerequisites, Data Center Setup prompts you to correct the configuration.

− If your system meets the prerequisites, continue to follow the installation step by step. If questions arise regarding how to proceed with any step, click Help on the window for information on that stage of the process.

Note

If your Data Center supports more than 10,000 accounts, do not run Support Center and the Account Management Website on the same server.


Configuration tasks Chapter 6: Installing the Data Center Software

Verifying the installation

Iron Mo

• To verify that you installed Support Center and the Account Management Website application successfully, log on to the applications and access your Data Center resources.

• For Support Center, use the admin technician ID and password that you created during installation to log on to Support Center using the following URL where <server name> represents the server where you installed Support Center and Account Management Website.

http://<server name>/supportcenter/

• Log on to the Account Management Website. Use the default registration URL and register an account.

• If you cannot gain access to Support Center or Account Management Website, verify that network or firewall issues do not block access to the server. To verify that IIS Admin Service and World Wide Web Publishing Service started, open Services on the Windows Control Panel.

• To test MyRoam, log on to Account Management Website and use MyRoam to retrieve a file.

Configuration tasks
After you install and verify the Data Center, Support Center, and Account Management Website installations, perform the following configuration tasks:
• Move the MyRoam Scratch folder to a drive that has a significant amount of available disk space.

• Configure DCAlerter.

• Create communities and technician IDs in Support Center.

Integrate the Data Center with enterprise directory.

Moving 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 on the Data Center server. It uses the Scratch folder temporarily to store the rebased files required to satisfy the retrieve request.

By default, the Scratch folder is in the Data Center installation folder (typically, C:\datacenter). You might want to change the location of this folder to a drive that has a significant amount of available disk space, especially if you expect to have many or large MyRoam requests.

To change the location of the Scratch folder, complete the following steps:

1. Create a new folder in the location of your choice. You must name this folder Scratch.

2. Delete or rename the original Scratch folder.

3. Open the Windows registry editor and change the value of the following registry key to see the new location:

HKEY_LOCAL_MACHINE\SOFTWARE\Connected\BackupDataCenter

4. Restart the BackupServer service.


Chapter 6: Installing the Data Center Software Configuration tasks

Configuring DCAlerter

74 Co

DCAlerter uses e-mail 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 e-mail 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. For more information about how to modify the installed settings, see DCMC Help.

Note

When you configure the DCAlerter service, verify that the anti-virus software on the server is not blocking the alerts that DCAlerter sends.

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, see your Connected Backup documentation set.

For information about integrating the Data Center with an enterprise directory, see Chapter 7: Integrating the Data Center with Enterprise Directory on page 65.


7

INTEGRATING THE DATA CENTER WITH ENTERPRISE DIRECTORY

About this chapter

Iron Mo


To learn about See

How Connected Backup uses enterprise directory Enterprise directory overview, on page 76

The steps required to integrate a Data Center with enterprise directory

Enterprise directory integration process, on page 77

The tasks required before you start the integration. Preparing for enterprise directory integration, on page 78

Configuring the firewall for enterprise directory integration

Configuring your firewall, on page 79

How to enable Support Center access for enterprise directory integration

Enabling Support Center access, on page 79

How to map the Support Center data fields to enterprise directory fields

Mapping data fields, on page 80

How to confirm that the integration completed successfully

Verifying successful enterprise directory integration, on page 82


Chapter 7: Integrating the Data Center with Enterprise Directory Enterprise directory overview

Enterprise directory overview

76 Co

Enterprise directory uses Lightweight Directory Access Protocol (LDAP), a software protocol that enables 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 use enterprise directory as well. It is important to map a community to enterprise directory before you allow PC Agents to register to the community.

Enterprise directory uses
You can use Enterprise directory to validate Support Center technicians and optionally, to maintain the personal data of end users. When you integrate Connected Backup with your enterprise directory, you gain the following benefits:
• Support Center technicians can use their enterprise directory passwords for authentication.

• Support Center technicians cannot gain access to Support Center after reassignment or termination.

• PC Agent accounts can authenticate 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.

• You can perform PC Account Lifecycle Management, since your PC accounts are based on your existing enterprise directory accounts.

• PC accounts are automatically populated and updated. This is very useful for account management, reporting, and troubleshooting.

Existing enterprise directory servers
If you have an existing enterprise directory server, use Support Center to map the directory to the Data Center database. For more information about how to map your Data Center to the enterprise directory Data Center, see Support Center Help.
Validate Support Center technicians

Use Support Center to map the Data Center or communities to an enterprise directory. Doing so forces Support Center technicians to use their user ID and password for their enterprise directory to log on to Support Center.


Enterprise directory integration process Chapter 7: Integrating the Data Center with Enterprise Directory

Maintain user personal data for PC accounts (optional)

Iron Mo

The PC Agent and the Data Center databases use the enterprise directory to obtain personal information about the user. Therefore, you do not have to enter information in multiple places.

Additionally, you can use the enterprise directory to require users to provide their enterprise directory password to use the Agent to retrieve files or performing a Heal. Users with accounts that are enabled with enterprise directory cannot change their personal information in the Agent. They can change information only on the enterprise directory server.

Server Agents do not support the use of enterprise directory to obtain personal information about users.

Enterprise directory management
For enterprise directory-enabled communities, the Data Center synchronizes user information between the enterprise directory server and the Data Center databases. The LDAPSyncher application uses Windows Scheduled Tasks to perform this synchronization process and run daily.
If the enterprise directory server is unavailable, Support Center technicians cannot log on to Support Center, and therefore, cannot register new PC Agents. If the users must enter an account password for the Retrieve and Heal features, when the enterprise directory server is unavailable, these features are unavailable.

If your organization uses Lotus Domino, contact Connected Support for more information and assistance. Support for Lotus Domino requires modifications to the databases in the Data Center.Integration process

Enterprise directory integration process

CAUTION

Read this entire procedure before you integrate, and be sure you understand all the requirements and steps.

Complete each requirement and step in one phase before you start the next phase.

Integration includes the following phases:

1. Prepare your IT infrastructure for integration, and gather the information that you need to complete the procedures in this document.

2. Configure your firewall to allow Support Center access to your enterprise directory.

3. Enable Support Center access.

4. Define the Enterprise Directory Setup Properties in Support Center. This requires you to map Support Center data fields to corresponding enterprise directory data fields.

The following sections explain these phases in detail.


Chapter 7: Integrating the Data Center with Enterprise Directory Enterprise directory integration process

Preparing for enterprise directory integration

78 Co

The preparation phase requires you to collect information to configure access to your enterprise directory and verify that your infrastructure meets requirements to support integration.

To prepare for integration with enterprise directory, complete the following steps:

1. Install the Data Center, or upgrade your Data Center to the current version.

For more information about how to install your Data Center for the first time, see Installing the Data Center software, on page 66. For more information about how to upgrade your Data Center, visit the Resource Center.

2. Confirm that your organization’s enterprise directory supports the Microsoft Windows 2000 Active Directory® server.

3. Verify that enterprise directory accounts exist for users to whom you deploy Agents. The users include people use Support Center to manage Connected Backup user accounts, and commonly referred to as Support Center technicians.

If you plan to use enterprise directory to authenticate Agent registration, this step is critical. Users that do not have enterprise directory accounts cannot authenticate. Therefore, the Agent fails to register.

4. Locate the enterprise directory source server that has access to user accounts to which you plan to deploy Connected Backup Agents. Make note of the URL for the source server; you will need it later to grant Support Center access to your enterprise directory.

For best results, place this server as high as possible in the enterprise directory architecture.

5. Install Secure Socket Layer (SSL) certificates on each enterprise directory server that the Data Center servers and the Support Center server will read.

SSL prevents unauthorized interception of user credentials.

6. Create a new enterprise directory account that has only read permission on the enterprise directory server that you identified in step 4. Remember the user account and password; you need to enter it in Support Center.

This account requires read access to all enterprise directory accounts and to your enterprise directory schema. Support Center uses this user account to read information from your enterprise directory during the initial integration, and for every communication from Support Center.

Note

An LDAP browser helps you identify and locate your enterprise directory accounts and servers. As you prepare process, you can use the LDAP browser to gather information and identify the server(s) that you want to permit Support Center to access. Check if your enterprise directory software includes a browser. If it does not, you can obtain a free LDAP browser from the Internet.

CAUTION

Use a password with a minimum of eight characters, and 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.


Enterprise directory integration process Chapter 7: Integrating the Data Center with Enterprise Directory

Configuring your firewall

Iron Mo

If you protected your Data Center with a firewall, you must configure the firewall to permit the Data Center servers to contact your enterprise directory servers.

To configure your firewall, complete the following steps:

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.

Enabling Support Center access
To enable Support Center access, you must provide 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.
Data field labels vary from one enterprise directory to another. To determine which fields to map to the Support Center data fields, contact the person who administers your enterprise directory fields.

Defining enterprise directory setup properties

To gain access to your enterprise directory server or servers, Support Center uses the enterprise directory account you created. For more information, see Preparing for enterprise directory integration, on page 78. Support Center connects through your corporate firewall to the enterprise directory and reads account information.

You can enable the Data Center to connect to your enterprise directory to authenticate users who attempt to register Agent 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.

To enter the setup properties, complete the following steps:

1. Log on to Support Center.

2. Locate the subcommunity that you want to integrate with your enterprise directory.

Your root and subcommunities appear in the navigation tree on the left. You might need to expand your root community node to locate the subcommunity that you want to integrate.

3. To display the Enterprise Directory Setup page, on the Community Status page, click Enterprise Directory.

4. Type the URL of the source server in the Enterprise Directory Server URL field.

The following example shows a valid URL for an Active Directory server.

LDAP://my.edserver.com/dc=edserver,dc=com

5. To ensure that inbound Support Center connections are secure, select Use SSL.

6. In the Connection Login DN box, enter the enterprise directory user account ID that you created for Support Center to enable it to connect to your enterprise directory.

The following example shows an Active Directory account.

[email protected]


Chapter 7: Integrating the Data Center with Enterprise Directory Mapping data fields

80 Co

7. In the Connection Password box, enter the account password.

The Data Center encrypts and stores the password. Only technicians that have the Change the Enterprise Directory user permission have access to the password. For more information, see Support Center Help.

8. Select Verify existence of users through Enterprise Directory to have Support Center use your enterprise directory to authenticate all users who attempt to register a Connected Backup account.

9. To indicate how you want Data Center to respond to users who do not pass authentication, select one of the following options:

• Change the Account Status to On Hold — if you want to place these accounts on hold temporarily until you can verify independently whether they should be allowed to register.

• Change the Account Status to Cancel — if you want to deny the account registration permanently.

10. Continue to the next section, Mapping data fields, to complete the integration.

Note

Connected Backup verifies against only deleted PC accounts. It does not verify against disabled accounts. Connected Backup treats disabled accounts the same as active accounts. If you create an account for a disabled enterprise directory account, you can use Support Center to change the account status to On Hold or Cancelled.

Mapping data fields
Support Center also can read user information, such as First Name, Last Name, department or other information from your enterprise directory. To do so, 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 lists default values for data fields in Netscape Directory, Novell eDirectory and Microsoft Active Directory. These suggested values might not represent the values in your enterprise directory implementation. For assistance with mapping data fields, consult your enterprise directory administrator.


Mapping data fields Chapter 7: Integrating the Data Center with Enterprise Directory

Iron Mo

In the table, an asterisk (*) next to a field indicates a required field, and you must enter the name of your corresponding enterprise directory data field.

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 L City

State st ST st

Zip Postalcode PostalCode Postalcode

Country Country Country c

Telephone TelephoneNumber TelephoneNumber TelephoneNumber

Email Mail Mail mail

Company Company Company company

Department departmentNumber departmentNumber Department

Mapping the data fields

To map the data fields, complete the following steps:

1. In the Enterprise Directory Setup page, enter the name of the corresponding enterprise directory data field in each field.

2. Check the spelling, capitalization, and spacing of each field name that you enter.

3. After you map the fields, click Save.

Note

If you do not know which field names to map to the Support Center fields, consult your enterprise directory administrator.


Chapter 7: Integrating the Data Center with Enterprise Directory Verifying successful enterprise directory integration

Verifying successful enterprise directory integration

82 Co

After you complete the integration procedures, verify that the integration completed successfully and works as expected.

To verify that the enterprise directory integration was successful, complete the following steps:

1. Create a new technician account in Support Center and verify that you can use that account to log on to Support Center.

For instructions on how to create technician accounts, see Connected DataProtector/SV™ Agent Deployment™ or your Connected Backup documentation set.

2. Create a new test PC Agent configuration in the Support Center community that you integrated with your enterprise directory.

For more information about how to create a PC Agent configuration, see Support Center Help.

3. Deploy and install that PC Agent to a user account in the enterprise directory. Verify that you can use the user account in the enterprise directory as credentials to install and register the new PC Agent.

For instructions on how to deploy a PC Agent, see the Connected Backup documentation.

4. After you install a test PC Agent, confirm that the account information appears in the PC Agent. If the account information fields in the PC Agent are empty, confirm that the fields are populated in the enterprise directory user account.


PART III: MANAGEMENT

Chapter 8: Managing the Data Center with DCMCChapter 9: Installing Management ToolsChapter 10: Event Logging

8

MANAGING THE DATA CENTER WITH DCMC

About this chapter

Iron Mo

This chapter describe the Data Center Management Console (DCMC). It also explains how to use the DCMC to monitor and control Data Center operations, and manage Connected Backup services.



The Data Center Management Console application DCMC overview, on page 86

How to use the DCMC user interface DCMC user interface, on page 88


Chapter 8: Managing the Data Center with DCMC DCMC overview

DCMC overview

86 Co

The Data Center Management Console (DCMC) is a snap-in for the Microsoft Management Console (MMC). Together with the MMC, the DCMC provides a user interface that you can use to monitor and control Data Center operations and manage the following services:

• BackupServer

• PoolServer

• ReplicationServer

• IndexServer

• BackupHSM

• HSMPurge

• Compactor

For more information, see the DCMC Help.

The following table describes the tasks that you can perform with the DCMC.

Note

To work with the DCMC, you must be familiar with the Microsoft Management Console (MMC).

Task Description

Start, pause, and stop the Data Center services.

Starts, pauses, and stops Data Center services. Also shows icons in the DCMC console tree and information in the details pane to indicate whether Data Center services are running or stopped. For more information about the DCMC interface, see DCMC user interface, on page 88.

View and modify properties for each Data Center service.

Shows the default properties and properties that you selected during Data Center setup. Also lets you can change these properties. Contact Corporate Support for guidance before you make changes.

Monitor multiple Data Center servers simultaneously.

Shows the status of mirrored or clustered servers simultaneously.

Manage space used in archive storage devices.

Shows the status and space used for archive storage devices, including tape libraries and EMC Centera.

Monitor current status. Shows the status of HSM requests, operations, and the availability of tape drives.

View event logs and run the Windows Event Viewer.

Shows the event logs for Data Center operations so you can diagnose Data Center problems. You also can run the Windows Event Viewer for a Data Center.


DCMC overview Chapter 8: Managing the Data Center with DCMC

DCMC access requirements

Iron Mo

To use DCMC, log on to the Data Center server or a remote computer that has the Data Center Toolkit. Use an account that has administrator privileges. To use DCMC, you must have access to the following components:

• HKLM\Software\Connected system Registry key

• Service Control Manager

The Service Control Manager lets you start, stop, and query services.

• The disk volumes that are attached to each computer

By default, Data Center Setup sets these device shares to allow access only to administrators who have privileges in the domain. You can change this setting to allow access to other administrators.

• Event Log on each computer

• SQL Server on the selected server

You must be able to perform the following tasks on SQL tables:

− Read queries

− Inserts

− Updates

− Deletes

− Stored procedure calls

The Data Center Setup procedure grants access to the Domain Administrators group, but you can extend these permissions to other administrators not part of the group.

Starting DCMC

You can run the DCMC on a Data Center server. Alternatively, if your remote computer hosts the Data Center Toolkit, you can run the DCMC remotely.

To start the DCMC, from a Data Center server, complete the following steps:

1. Click Start > All Programs > Data Center.

2. Click Data Center Management Console.

To start the DCMC from a remote computer that hosts the Data Center Toolkit, complete the following steps:

1. Click Start > All Programs > Data Center Toolkit.

2. Click Data Center Management Console.

If your Data Center does not appear in the DCMC console tree, add it. For more information, see the DCMC Help.


Chapter 8: Managing the Data Center with DCMC DCMC user interface

DCMC user interface

88 Co

The DCMC supports and enhances the standard MMC functions and interface elements. Together with the MMC, the DCMC provides a user interface that lets you manage the Data Center components.

The DCMC interface includes the following elements:

The following figure shows the DCMC interface:

Console tree (left pane) — Displays DCMC icons to make visualizing DCMC components easy

Details pane (right pane) — Provides information based on your selection in the console tree

Menus and toolbars (including shortcut menus) — Displays DCMC commands

Console tree Details pane

Menus and toolbars


DCMC user interface Chapter 8: Managing the Data Center with DCMC

Console tree

Iron Mo

The console tree uses icons to represent each Data Center component. These icons are organized hierarchically in the following manner:

• Servers appear under the Data Center to which they belong.

• Services and components appear under the server with which they are associated.

If a service or component contains subcomponents, a plus sign (+) appears to the left of the component icon. To view subcomponents, complete one of the following tasks:

• Click +

• Double-click the component name

Icons indicate whether the service or component is running or stopped in the following ways:

• Running — right pointing arrow inside of a circle

• Stopped — square inside of a circle

The following figure shows the DCMC console tree.

Console Tree


Chapter 8: Managing the Data Center with DCMC DCMC user interface

Details pane

90 Co

The DCMC details pane displays information about the item that you select in the console tree. For example, if you select a Data Center in the console tree, the details pane displays the status and other information about the services that run on the Data Center servers.

You can set the DCMC to refresh the view of the details pane at set intervals. By default, the DCMC service refreshes the view every five minutes. You also can manually refresh the view of the details pane.

The following figure shows the DCMC details pane.


DCMC user interface Chapter 8: Managing the Data Center with DCMC

Menus and toolbars

Iron Mo

You can gain access to the DCMC functions and properties through toolbars and menus. The DCMC menus contain the console commands and other DCMC functions.

Menus
DCMC has the following menu types:
Menu Description

Microsoft Management Console (MMC) menu bar

Includes the Console, Window, and Help menus. These menus are standard to MMC.

DCMC snap-in menu bar Includes the Action and View menus. These menus provide access to DCMC functions and display options for the console tree and details pane.

Shortcut menu Appears when you right-click items in the console tree and details pane. With a shortcut menu, you can modify the properties for the selected item or run a command relevant to the selected item.

Toolbars

The DCMC contains snap-in toolbars to augment the MMC toolbar. Together, the toolbars provide access to the console functions and DCMC commands. If you do not use the toolbars, you can gain access to the functions and commands through menus. The DCMC also has a description bar, which displays the name of the current view, including the time the view was last refreshed.

The following figure shows the DCMC menus and toolbars:

MMC menu bar

MMC toolbar

DCMC snap-in toolbar

Shortcut menu

DCMC snap-in menu bar


9

INSTALLING MANAGEMENT TOOLS

About this chapter

Iron Mo

This chapter describes the tools that you can install on Data Centers and use to manage Data Centers. It also explains how to install the tools.



The tools that you can install on Data Centers Management Tools Overview, on page 94

How to install the DataBundler™ application Installing DataBundler, on page 94

How to install the Data Center Toolkit Installing the Data Center Toolkit, on page 96


Chapter 9: Installing Management Tools Management Tools Overview

Management Tools Overview

94 Co

The Connected Backup software includes the following management tools:

DataBundler™ — Creates an image of an Agent account that includes backed-up files from a specific date. You can burn the account image onto a CD or DVD. For Server Agent accounts, you also can store the image on a Network Attached Storage (NAS) device. You can configure DataBundler to create account images when it receives requests, or you can build images manually.

When DataBundler builds an account image, it includes a copy of the Agent application. Use the Agent user interface to retrieve files, or use Heal from the account image to restore a system. For more information, see to the DataBundler Help.

Data Center Toolkit — The Data Center Toolkit includes tools that you can use to monitor and manage the Data Center remotely. You can install the Data Center Toolkit on any number of computers. The computers on which you install the Data Center Toolkit must have access to the Data Center server(s).

Installing DataBundler
Data Center Setup does not install DataBundler™ on the Data Center server. You must install it separately.
DataBundler requirements

To run DataBundler, your computer must meet the following requirements:

• Windows 2003 Server Standard Edition or Windows 2000 Server with Service Pack (SP) 4 and all security hotfixes.

• Hard disk space on one volume that is at least twice the size of the largest account (minimum of 6 GB).

• Full connectivity to the Data Center server(s).

• The DataBundler client must 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 you burn a CD or DVD, do not use the DataBundler client for any other purpose. Dedicate the client solely to the creation of CDs or DVDs. If you expect to burn a large number of CDs or DVDs, install DataBundler on more than one computer. Each computer that has DataBundler can burn only one CD or DVD at a time.


Installing DataBundler Chapter 9: Installing Management Tools

Preparing to install DataBundler

Iron Mo

Before you install DataBundler, create the user account CNTD_DataBundler on the computer where you plan to install the DataBundler application and add it to the Power Users group. With Power User privileges, you can successfully burn CDs and DVDs.

NoteIf you upgrade 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.

Installing DataBundler
To install DataBundler, complete the following steps:
1. Do one of the following:

• If you use a 7.x or later Data Center server, and you want to use DataBundler to create images for 6.x Agents, install version 6.x of the CDMaker software first.

Do not remove the CD Maker software.

• If you use a 7.x or later Data Center server, but do not want to use DataBundler to create images for 6.x Agents, continue to the next step.

2. Log on to the computer as an administrator.

3. Close applications that are open.

If you switch user IDs on the same computer, the first user’s open applications do not close automatically.

4. Copy the DataBundler software to a convenient location on the computer.

You can copy the DataBundler folder from where you installed the Data Center software, or you can go to the Resource Center to download the DataBundler software.

5. In the DataBundler folder, double-click setup.exe.

6. Follow the instructions in the setup program to install DataBundler.

7. When DataBundler prompts you for the location of where to install the program, specify the location of the large disk volume on which you want Data Bundler to create the account images.

The setup program creates a share for the folder, so that all members of the domain can have access to it.

Requirements for using DataBundler

Before you use DataBundler application, complete the following tasks:

• Make sure that DataBundler has write access to its installation directory.

• When you start the DataBundler application, use the user account that you specified for the application when you installed the Data Center (CNTD_DataBundler or CNTD_CDMaker).

• Make sure that the DataBundler user account belongs to the Administrators or Power Users group.

• When you specify the location for the media images, use a UNC (Universal Naming Convention) path to a directory to which DataBundler has access. If you specify a path on the local computer, you must provide write permissions for that directory. If you specify a path on a remote computer, use a shared directory and provide the write privileges. For more information about how to use DataBundler, see DataBundler Help.


Chapter 9: Installing Management Tools Installing the Data Center Toolkit

Installing the Data Center Toolkit

96 Co

The Data Center Toolkit lets you use some of the utilities that are included in the Data Center Setup to maintain the Data Center remotely from a computer other than the Data Center server. For example, you can use the Data Center Toolkit to remotely monitor the BackupServer status.

Data Center Setup does not install the Data Center Toolkit. You must install the toolkit on the Data Center server separately.

Data Center Toolkit requirements
The Data Center Toolkit has the following requirements:
• You must install the Data Center Toolkit on a computer that does not host the Data Center software, but is in the same domain as the Data Center server(s).

• You must install the Data Center Toolkit only on computers with Windows operating systems that use the English locale.

• The computer on which you install the Data Center Toolkit must have access to the Data Center server(s).

Installing the toolkit

You can install the Data Center Toolkit on any number of computers.

To install the Data Center Toolkit, complete the following steps:

1. Navigate to the folder where you installed the Data Center software.

If you do not have access to the Data Center software, go to the Resource Center to get a copy of the Data Center Toolkit.

2. In the Toolkit folder, double-click setup.exe,and then follow the installation prompts.

Note

You must install the Data Center Toolkit on a computer that does not host the Data Center software.


Installing the Data Center Toolkit Chapter 9: Installing Management Tools

Running the Data Center Toolkit

Iron Mo

The Data Center Toolkit contains the following tools:

To run a Data Center Toolkit component, complete the following step:

Click Start > All Programs > Data Center Toolkit.

Data Center Management Console— A snap-in for the Microsoft Management Console (MMC) that provides a user interface that you can use to monitor and control Data Center operations and services. For more information, see Chapter 8: Managing the Data Center with DCMC on page 85.

Data Copier — Lets you copy archives from the Hierarchical Storage Manager (HSM) device on a Data Center server to a disk cache on the Data Copier or to the disk cache of another Data Center server.

DCStatus — Lets you remotely check the status of services and databases on each server. For more information, see DCStatus Help.

Disk Status — Verifies the status of the disk space on a Data Center server.

Remote Diagnostic Tool —

Tdate Converter — Translates Tdates into common mm/dd/yy format. A tdate is the date of backup transmission for a file stored at the Data Center. The Data Center software refers to the date as a 10-digit number of seconds since January 1st, 1970.


10

EVENT LOGGING

About this chapter

Iron Mo

This chapter explains how the Data Center logs information.



Different types of Data Center logging Event Logging, on page 100

How the Data Center maintains event logs Event Log Maintenance, on page 101


Chapter 10: Event Logging Event Logging

Event Logging

100 Co

Event logging provides a standard way for multiple Data Center components to report events. It also provides a way to categorizes events according to levels of priority. For more information about how to use the event logs and for a list of event messages for each component, see the Resource Center.

The Data Center generates event messages in the logs in the following hierarchy:

Log Description

DCMaint event log Contains event entries that pertain to the Data Center application specifically designated for the DCMaint event log. You can use this event log to monitor the Data Center services. You can view the DCMaint from DCMC or the Windows Event Viewer on the Data Center server. With more detailed messages in the DCMaint log, you and Corporate Support can diagnose problems further.

Application event log Contains event entries that notify the user of an occurrence detected by the operating system or the applications running on the Data Center server. An event includes the following information:

• Type of event

• Date and time that the event occurred

• The computer on which the event occurred

• Event ID

• Event category

• The source of the event

For a Windows operating system, you can use the application event log for troubleshooting and monitoring the performance and the behavior of the Data Center server and the Data Center application.

Data Center component trace log file Trace log files provide a deeper level of detail that helps Corporate Support diagnose the potential problem. You provide trace logging by way of the registry keys. Corporate Support use trace logs to give the user advice and assistance.

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 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 trace log file for the 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 Chapter 10: Event Logging

Event Log Maintenance

Iron Mo

This section explains how to maintain the following types of event logs:

• Application event logs

• DCMaint logs

Application event log maintenance
If the addition of an event causes the Application event log to exceed its limit (for example, 50 MB), the Agent backs up the Application event log file. The Data Center then clears the event log, and adds an informational message to the log. The message indicates that the event log was backed up and cleared because of space limitations.
The string value LogFileDir under the \\LocalMachine\Software\Connected\BackupDataCenter key in the Windows registry specifies the location to which the Agent backs up the Application event log file. The Data Center names the file according to the following format:

NTApp TimeStamp.evt

For example, NTApp 2003-10-01 092345.evt

Note

To backup and clear the Application log, the Data Center must send the message that causes the log to exceed its limit. For example, if a different server component, such as SQL Server, fills the log, the Data Center does not save the log. You must save and clear the log manually.

DCMaint log maintenance

If the DCMaint log becomes full, the Data Center backs up the log file and clears the log. The system generates an informational message in the Application event log. The message indicates that the DCMaint event log was backed up and cleared because of space limitations. You can save the log because only the Data Center software writes to the DCMaint event log.

The Data Center performs other maintenance of the DCMaint log upon initialization such as a comparison of the event log size and age to the Windows registry values MaxSize and LogFileTime. The Data Center also backs up and clears the log if either value exceeds the defined limits.

The string value LogFileDir under the \\LocalMachine\Software\Connected\BackupDataCenter key in the Windows registry specifies the location to which the Agent backs up the Application event log file. The Data Center names the file according to the following format:

DCMaint TimeStamp.evt

For example, DCMaint 2003-10-01 092345.evt.


PART IV: MAINTENANCE

Chapter 11: Introduction to Data Center MaintenanceChapter 12: Daily MaintenanceChapter 13: Weekly MaintenanceChapter 14: Monthly Maintenance

11

INTRODUCTION TO DATA CENTER MAINTENANCE

About this chapter

Iron Mo

This chapter describes the types of maintenance tasks that you must perform on the Data Center.



The Data Center maintenance tasks described in this manual

Maintenance tasks overview, on page 106


Chapter 11: Introduction to Data Center Maintenance Maintenance tasks overview

Maintenance tasks overview

106 Co

The Data Center documentation provides information that is specific to the Data Center. It does not explain how to maintain third-party hardware or software that is installed on the Data Center. For example, the Data Center documentation explains that technicians must clean the tape drives in the tape library. However, the Data Center documentation does not explain how to clean the tape drives. The steps that you must complete to clean a tape drive depend on the make and model of the tape drive. For information about how to clean the tape drive, see the documentation provided by the tape drive vendor.

Antivirus software and the Data Center
Do not run antivirus software for the Customers folder on Data Center servers. Antivirus software might confuse the compressed and zipped archive sets on the Customers volume with virus signatures. If antivirus software mistakes archive sets for viruses it isolates the archive sets. The archive sets become corrupt because the Data Center no longer has access to them. This situation results in data loss.
If you back up files that contain a virus, the virus does not affect Data Center servers. The encryption and compression techniques used during backup inoculate the virus. However, Connected Backup software does not protect users who might recover an infected file. If a user backs up an infected file, the file remains infected after the user recovers it. The only way to detect and repair recovered files that are infected is to use antivirus software on the Agent computer.

Types of maintenance tasks

This manual provides descriptions of maintenance tasks that you must perform daily, weekly, and monthly. For more information, see the following chapters:

Chapter 12: Daily Maintenance on page 107.

Chapter 13: Weekly Maintenance on page 115

Chapter 14: Monthly Maintenance on page 123


12

DAILY MAINTENANCE

About this chapter

Iron Mo

This chapter describes the maintenance tasks that you must perform each day to ensure that the Data Center runs optimally. Because there are tasks to perform throughout the day, this chapter categorizes tasks by those to perform at the start of the day, and those to perform at the end of the day.

For a checklist that you can use to keep track of daily maintenance tasks, see Appendix C: Maintenance Checklists on page 147.



Tasks to complete at the start of the work day Tasks to complete at the start of every day, on page 108

Tasks to complete every morning and afternoon Tasks to complete at the start and end of every day, on page 110

General maintenance tasks to complete for Data Centers that use tape libraries

Tasks to complete daily for Data Centers that use tape libraries, on page 113


Chapter 12: Daily Maintenance Tasks to complete at the start of every day

Tasks to complete at the start of every day

108 Co

At the start of every day, complete the following tasks:

• Verify the Daily Automatic Procedure results

• Verify personal backups

• Check the disk status and unknown disk space

• Verify that the IT alert system works

Verifying the Daily Automatic Procedure results

The Data Center contains a daily maintenance script, dailymaint.sql, that runs at 12:00 p.m. every day except Sunday. This script executes the following tasks:

• Backs up the SQL transaction logs for the Directory database and Registry database. These backups happen only for stand-alone Data Centers.

• If you use a secondary tape set, migrates archives to the secondary tape set. This migration happens 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 a component that stores data (for example, a tape library, Centera, or SAN device).

The dailymaint.sql script writes the results of the tasks it performs to two log files in the Data Center folder:

To review the results of the Daily Automatic Procedure, complete the following steps:

1. In the default:\Data Center\ folder, open dailymaint.out or sqldump.log.

2. Review the output file for errors that might have occurred while the maintenance script was running.

If the script runs successfully, the output file indicates the following information:

• The Directory database and Registry database transaction logs have been backed up at the time that you specified. These backups happen only for stand-alone Data Centers.

• The migration to the secondary tape set was successful. This migration happens only if your Data Center uses a secondary tape set.

3. To view the Application event log, open the Data Center Management Console (DCMC), expanding the Events node, and click Application.

4. Verify that no errors occurred during the daily SQL transaction logs backup or in the migration of data to the secondary tape sets.

Note

If you run a mirrored or clustered Data Center, the Data Center replicates the SQL databases between the servers. Therefore, the Daily Automatic Procedure does not need to back up the data. In a mirrored environment, if a data loss occurs, you can restore a database from its mirror.

dailymaint.out — Contains the results for only the previous day

sqldump.log — Contains an ongoing history of the Daily Automatic Procedure results


Tasks to complete at the start of every day Chapter 12: Daily Maintenance

Iron Mo

5. If problems appear in the log files or in the Application event log, visit the Resource Center for more information.

Note

If you run a large stand-alone Data Center, you can schedule the dailymaint.sql script to run more than one time per day. If you run the script more than once a day, you reduce the risk of data loss and decrease the time required to recover a failed system.

Verifying personal backups
Verify that user’s personal backups complete successfully. To perform this task, you can use the Agent on any computer that backs up to your Data Center.
To verify personal backups, complete the following tasks:

1. Open the Agent.

2. Click the History tab and select the most recent session logs.

3. To display the log for the selected sessions, click View Details.

4. Verify that each session started and completed successfully.

5. Look for errors and indications of problems with the connection.

Although these types of problems might occur occasionally, they might not indicate a persistent problem.

Checking backup disk status and unknown disk space

Use the Disk Status tool to check the status of the backup disk.

To check disk status, complete the following steps:

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 about the status of the disk.

3. Verify that all indicators are between normal parameters (in 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.

7. To generate a text file that lists files on the customer data volume that are unrelated to the Data Center, click Display.

The text file contains columns that list the file name and the file size in bytes.

8. Move or delete these files to allow more space for the Data Center files.


Chapter 12: Daily Maintenance Tasks to complete at the start and end of every day

Verifying that the IT alert system works

110 Co

You can use the DCAlerter service to send email alerts when the Data Center generates event log warning messages or error messages. You also can use a third-party application to send email alerts.

After you configure the alert system to respond to the conditions for which you want to receive alerts, you can use the Event Test tool to simulate an event so you can test the alert system. To get a copy of Event Test, visit the Resource Center.

To simulate an event with the Event Test tool, complete the following steps:

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 enter the following command:

evttest 3 sample error text

This command enters an error message in the event log with a source of DCTest1 and message text sample error text. You can change the error text to suit your needs.

4. Verify that the error message appears in the Application event log, and that the test event provides the correct notification.

To verify that a third-party IT alert system works correctly, complete the following step:

Verify that the following events happen:

• Alert-causing conditions cause the software to place an event in the event log.

• The Alert system traps the event.

• DCAlerter notifies the operator.

Tasks to complete at the start and end of every day
Perform the following general tasks at every start and end of every day:
• Verify that services are running.

• Examine the Windows event log.

• Verify that Support Center and MyRoam are running.

• Check Copy on Reference and replication.

Verifying that the services on the Data Center server are running

To verify that the services are running, complete the following steps:

1. Open DCMC and expand your Data Center node in the Console tree.


• If you do not see your Data Center in the Console tree, complete the following steps:

a. Right-click Data Centers, and then click Add a Data Center.

b. In the Data Centers window, select the appropriate configuration for your Data Center, and then type the Data Center or server name (whichever required, based on your configuration selection).

• If you see your Data Center in the Console tree, continue to the next step.


Tasks to complete at the start and end of every day Chapter 12: Daily Maintenance

Iron Mo

3. To view the status of the services, in the Console tree, click the name of the Data Center server.

The Console tree displays the following services:

• BackupServer

• DCAlerter

• ReplicationServer

• IndexServer

• PoolServer

• Compactor

• BackupHSM (HSM only)

• HSMPurge (HSM only)

4. To restart a service that has stopped, complete the following steps:

a. In the Console tree, expand the server node.

b. Right-click the service.

A dialog box opens.

c. Click Start Service.

If your request to start the service fails, the Data Center sends a message to the Application event log.

5. To verify the status of the Compactor service, complete the following steps.

a. Expand the Events node.

b. To view event messages, click DCMaint.

c. Look for messages with Compactor under the Source column.

d. Do one of the following:

− If the Data Center writes warning or error messages to the log file, examine the Compactor log in the Log Files folder and the compaction date appended to the file name.

− If the Data Center does not write warning or error messages to the log, for details on logging and trace logs, see Chapter 8: Managing the Data Center with DCMC on page 85.

Examining the Windows event log

To examine the Windows event log for warning messages or error messages that might need attention, complete the following steps:

1. Open the DCMC.

2. In the Console tree, expand your Data Center node, and then expand the server name.

3. Expand the Events node, and click Application.

4. Look for warnings and errors in the log window and review them to determine what actions you must take. For more information about how to respond to error messages, see the Resource Center.


Chapter 12: Daily Maintenance Tasks to complete at the start and end of every day

Verifying that Support Center and MyRoam are running

112 Co

To verify that Support Center and MyRoam are running, complete the following steps:

1. To verify that the IIS Admin Service and the WWW Publishing Service run, open the Services Control Panel and verify that the status is Started.

2. To 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 has the following syntax:

http://servername/supportcenter

where servername is the name of the Web server that hosts Support Center

3. To verify that MyRoam is running, log on to the Account Management Website from a remote computer and retrieve one or more files.

Note

The steps to verify MyRoam apply only if your enterprise uses MyRoam for PC Agents.

Checking Copy on Reference and replication
Copy on Reference is the process that makes copies of files that multiple users have backed up with SendOnce. Replication is the process that, in a mirrored environment, copies files from a Data Center server to it’s mirror. To check Copy on Reference and replication, you must check values in DCMC against previously noted values. Therefore, keep a record of values so that you have a data history to which you can refer.
DCMC obtains the values from SQL tables in your database, which under normal circumstances, are typically empty. Because these tables are empty or nearly empty, the values in DCMC should be relatively small.

Checking Copy on Reference

To check Copy on Reference, complete the following steps:

1. Open the DCMC.

2. Expand your Data Center node in the Console Tree pane, and expand the server name.

3. Click PoolServer.

4. Review and note the values for SendOnce® Queue and SendOnce Status.

5. If the SendOnce Queue does not display zero, press F5 to refresh the window.

If Copy on Reference is working, the value decreases after a few minutes.


Tasks to complete daily for Data Centers that use tape libraries Chapter 12: Daily Maintenance

Checking replication

Iron Mo

You must check replication on each mirrored pair of servers in the Data Center, and on both of the servers that compose a mirrored pair.

To check replication, complete the following steps:

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 notice the values for Database rows to replicate and Archives to replicate.

5. If the values do not equal zero, press F5 to refresh the window.

If replication is working, the values decrease after a few minutes.

Tasks to complete daily for Data Centers that use tape libraries

If you use tape libraries, complete the following daily tasks:

• Check tape drive status and tape requests at the start of every day and the end of each day except Sundays.

• Remove the tapes for Secondary Tape Sets at the start of each day.

Checking tape drive status and tape requests

(Start of day and end of day, and under special circumstances)

If your Data Center uses a tape library for HSM, check the tape drive status and tape requests at the start and end of each day and under the following circumstances:

• Migrations do not respond.

• Full disk and not migrating.

• DataCopier is running.

• Restore or CD creation takes an excessive amount of time.

To verify that tape drives are online, complete the following steps:

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.

If any tape drives appear offline, visit the Resource Center for troubleshooting information.

To verify that the Data Center processes requests for migration and data retrieval, complete the following steps:

1. In the DCMC, expand your Data Center in the Console tree and expand the server.

2. To display the request status, select Current Requests > Backup HSM node.

3. Scroll to the far right of the status window and examine the Suspended column for suspended requests.

4. To refresh the view and verify that requests decrease over time, press F5.


Chapter 12: Daily Maintenance Tasks to complete daily for Data Centers that use tape libraries

Removing Secondary Tapes

114 Co

(Start of day only)

If your enterprise uses Secondary Tape Sets, check the tapes to determine whether you need to remove them. Depending on your the policy of your enterprise, you can leave the tapes in the library until they become full or remove them on a scheduled basis. You, or another technician, must mark a tape as full before you eject it.

To view the status of Secondary Tape Sets and eject full tapes, complete the following steps:

1. Open DCMC.

2. Expand your Data Center tree, and then expand the server name.

3. Expand the Tapes node, and then expand Tape Sets.

4. Click Secondary migration set.

5. In the Details pane, view the use information for each tape in the set to determine which tapes are full.

6. To remove a full tape from the library, click TapeID and click Eject on the tool bar.

To mark the tape full and then eject it, complete the following steps:

1. Right-click TapeID.

2. Select All Tasks and click Mark Tape Full.

3. On the toolbar, click Eject.

If you remove tapes, save them in a safe location (for example, in a different building).


13

WEEKLY MAINTENANCE

About this chapter

Iron Mo

This chapter describes the maintenance tasks that you must perform each week to ensure that the Data Center runs optimally.

For a checklist that you can use to keep track of weekly maintenance tasks, see Weekly maintenance checklist, on page 149.



How to verify the results of the Weekly Automatic Procedure

Verifying the results of the Weekly Automatic Procedure, on page 116

Backups that you should perform on a weekly basis Weekly backup tasks, on page 117

How to check for available disk space Checking for available disk space, on page 119

Tasks that you must perform each week Performing weekly general tasks, on page 120

Tasks that you must perform if you use tape libraries Performing weekly tasks for Data Centers that use tape libraries, on page 120


Chapter 13: Weekly Maintenance Verifying the results of the Weekly Automatic Procedure

Verifying the results of the Weekly Automatic Procedure

116 Co

To verify the results of the Weekly Automatic Procedure, you must perform the following tasks:

• Review the results of the weekly maintenance scripts.

• Review the Application event log.

The following sections explain how to perform these tasks.

Reviewing the weekly maintenance scripts
The Data Center has a weekly maintenance script that runs automatically at 12:00 p.m. every Sunday. This script carries out the following tasks:
• Performs a full backup of the SQL databases on a stand-alone Data Center

• Clears the transaction log so that the log does not grow continuously

• For HSM configurations with Secondary Tape Sets, migrates data to the Secondary Tape Set

The name of the script file depends on the media that you use to backup your databases:

• If there is a local tape device for backups, run the weeklymainttape.sql script to perform the database backup to tape.

• If there is not a local tape device for backups, run the weeklymaintdisk.sql script to perform the database backup to disk.

Data Center Setup installs each script file. However, set your task scheduler to run the script file that applies to your configuration.

Note

If you run a mirrored or clustered Data Center, the SQL databases replicate between the servers. Therefore, the Weekly Automatic Procedure does not back up the databases.

CAUTION

A weekly, full database backup to a disk can use as much disk space as the actual database. If you perform a backup to a disk, use another utility to copy the backup files to a different medium. Do not let a new full backup overwrite a previous full backup in case the new backup fails.

Do not back up your SQL databases to the same disk partition as the original SQL databases. If you experience problems with the disk partition, you might lose the databases and the backups.


Weekly backup tasks Chapter 13: Weekly Maintenance

Iron Mo

The Data Center software records the results of the weekly maintenance script to the weeklymaint.out and sqldump.log files in the Data Center folder. The files have the following differences:

• The weeklymaint.out file contains only the results for the previous week.

• The sqldump.log file contains the results for ongoing history.

These files reside in the default :\Data Center folder.

Review the weeklymaint.out and sqldump.log files to verify the following information:

• Whether the database backup succeeded without errors

• Whether the Master, Model, MSDB, Directory and Registry databases have been backed up at the time specified, if you run a stand-alone Data Center

• If you run a stand-alone Data Center, whether the Directory and Registry database transaction logs were backed up at the time specified

• Whether 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

Reviewing the Application event log
If an output file reports problems with the database backup, review the Application event log for messages that pertain to the backup.
To view the Application event log, complete the following steps:

1. Open the DCMC.

2. Expand the Data Center in the Console tree, and expand the server name.

3. Expand the Events node, and click Application.

The Application windows displays a list of events.

Note

If you run a large stand-alone Data Center, you can schedule the weeklymaint.sql script to run more often. If you increase the frequency, you can reduce the risk of data loss and decrease the time required to recover a failed system.

Weekly backup tasks

Weekly maintenance includes the following backup tasks:

• Back up Support Center reports

• Back up Agent configurations

• Back up the Windows registry key

• Back up PEM files

• Rotate tapes for the SQL database backups


Chapter 13: Weekly Maintenance Weekly backup tasks

Backing up Support Center reports

118 Co

Back up your Support Center report templates and results weekly to ensure that you have a copy of them if a disaster occurs. This step is important whether Support Center runs on the Data Center server or on a separate Web server.

Support Center stores the reports in the default location :\Inetpub\wwwroot\SupportCenter. You can back up the reports templates and report results using any method you prefer. For example, copy the reports to a different server or to tape.

Backing up Agent configurations
Back up your Agent configurations every week to ensure that you have a copy if a disaster occurs. Support Center stores the Agent configurations in the default location :\Data Center\Configuration$\. To back up the Agent configurations, you can use the method that you prefer. For example, copy the Agent configurations to a different server or to tape.
Backing up the Connected Windows registry key
Each week, back up the following Windows registry key:
• HKEY_LOCAL_MACHINE\SOFTWARE\Connected\

It is important to back up the registry key because changes you make to the registry key are lost when you reinstall the Agent and during disasters.

Back up the following registry key:

• HKEY_LOCAL_MACHINE\SOFTWARE\Connected\Keys

To back up this registry key, 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.

Rotating database backup tapes

If you run a stand-alone Data Center and perform your SQL database backups to tape, remove the backup tape and store it after every backup. Rotate the backup tapes every four weeks to ensure that you always have the most recent backups from the previous weeks on tape.


Checking for available disk space Chapter 13: Weekly Maintenance

Checking for available disk space

Iron Mo

Each week, check the available disk space on the following volumes to ensure that the disk has sufficient capacity:

• Customers folder

• SQL database

• SQL database backup

Checking the Customers folder
The Customers folder contains the end-user data. If you run a disk-only configuration, use Windows Explorer to check the available disk space on all Customers volumes.
If you run a Data Center with HSM, use the Disk Status tool to check for available disk space on the Customers volume. For information about the Disk Status tool, see the Connected® Backup/PC Product Overview.

Checking the SQL database
The SQL database grows throughout the life of the Data Center.
To track the size of the SQL database, complete the following steps:

1. Open Microsoft SQL Server Management Studio.

2. In the Object Explorer pane, expand your Data Center server.

A list of folders is displayed under your Data Center server.

3. Expand the Databases folder, right click Directory, and then click Properties.

The Database Properties widow appears.

4. Under the Select a Page pane, select Files.

5. To view the path of your .mdf and .ldf files, scroll to the Path column. Make note of this path.

6. Open Windows Explorer, and then select My Computer.

7. Follow the path that you noted in step five.

8. Record the size of your .mdf files and .ldf files for weekly tracking purposes.

9. Calculate how much the used disk space grew since the previous week to determine how much disk space the databases needs for the next three months.

Checking the SQL database backup

CAUTION

Do not back up your SQL databases to the same disk partition as the original SQL databases. If you experience problems with the disk partition for any reason, you might lose the databases and the backups.

If you run a stand-alone Data Center and back up your SQL databases to a disk rather than to tape, check the SQL database backup volume for available disk space weekly. Also, move the SQL backups from the disk to a tape or other media. Doing so lets you have multiple backups to restore from should a disaster occur.


Chapter 13: Weekly Maintenance Performing weekly general tasks

Performing weekly general tasks

120 Co

Perform the following general tasks weekly:

• Check system time synchronization.

• Check for updates.

Checking System Time Synchronization
If you run a mirrored or clustered configuration, the two servers that comprise a mirrored pair should run within 30 seconds of each other. Check the time on each server and correct discrepancies.
To check the system time, complete the following steps:

1. Open the Microsoft SQL Server Query Analyzer or SQL Server Management Studio.

2. Open a connection to each mirrored server in the same window.

3. For each server, run select getdate( ).

Note

Perform this time check after you add hardware to your server(s) and after changes in standard or daylight savings time.

Checking for Updates
You can upgrade the Data Center, the Agent, or both. A service release includes all hotfixes released since the last major release or service release. To get the latest software updates, visit the Resource Center.
Performing weekly tasks for Data Centers that use tape libraries

Perform the following tape library tasks weekly:

• Check blank tapes, recyclable tapes, and tape use, and manage clean tapes.

• Check tape library slots.

• Ensure that migration completed successfully.

• Check the health of tapes and tape drives.

Checking tapes

Ensure that you have enough unused storage capacity in your tape library to accommodate backups. Also, ensure that you have spare tapes for when you must replace a tape in the library. The number of tapes you need depends on server use, growth history, and planned expansion.

Use the following guidelines to manage tapes:

• Track tape use (by day or by week).

• Based on your tape use, keep at least two weeks worth of tapes plus two additional tapes available to accommodate growth and the replacement of bad tapes.


Performing weekly tasks for Data Centers that use tape libraries Chapter 13: Weekly Maintenance

Iron Mo

• Keep 50% more tape labels as you have tapes.

Checking blank tapes
Initially, your tape library should contain enough blank tapes to accommodate the number of end-user accounts that you estimated during capacity planning. As you add end-user accounts, examine how many blank tapes the Data Center uses each day or each week to determine the growth rate of the server.
To view information about blank tapes, complete the following steps:

1. Open DCMC.

2. Expand your Data Center tree and then the server name.

3. Expand the Tapes node and click Blank Tapes.

4. Verify that you have an adequate number of labeled blank tapes to handle normal tape use.

Checking tape usage
To view tape usage information, complete the following steps:
1. Open DCMC.


3. Expand the Tapes node, and click Tape Details.

4. Check Mount Count for any tapes that have excessive mounts. You might have to retire these tapes before they cause errors.

5. To determine if there are any tapes that you need to retire, scroll to the right to check Date of birth.

Note

If a tape causes warnings or errors in the Application event log, the tape is defective. Monitor defective tapes when you check tape use. 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 checks for and recycles tapes. Recycle a tape when the following conditions exist:

• All data on the tape expired.

• The tape is full.

Before you recycle a tape, the tape requires a cool-off period of seven days. To view recyclable tapes, use DCMC. After the Data Center recycles a tape, perform the following tasks:

• Relabel the tape.

• Clear the Directory database of expired information about the tape.

• Move the start point for write operations back to the beginning of the tape.

Note

Let tapes “cool off” after they become recyclable, so that you can use them in case of a disaster that requires you to restore the database. You must let tapes cool off for at least one week before you can recycle them. If you relabel the tapes, you loose the data that you need to rebuild the Data Center.


Chapter 13: Weekly Maintenance Performing weekly tasks for Data Centers that use tape libraries

Managing cleaning tapes

122 Co

To ensure that you have enough cleaning tapes, adhere to the following guidelines:

• Review your cleaning schedule and the number of cleaning cycles that remain on your cleaning tapes.

• Keep on hand enough cleaning tapes to last for one month of cleaning cycles.

• If you need only one cleaning tape per month, keep a spare cleaning tape on hand in case you have a problem with the first tape.

Checking tape library slots
Check the number of open tape library slots every week. If you use Secondary Tape Sets, remove full tapes and store them appropriately. When the percentage of open tape slots decreases to 20% or less, perform an analysis to verify how much data the system processes daily and how much data Compactor processes. This analysis helps you determine whether you need more tape slots for the Data Center.
Ensuring that migrations complete successfully
To ensure that migrations complete successfully and on a regular basis, complete the following steps:
1. Open DCMC.


3. Expand the Events node and then Application.

4. Perform a Find. Use 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 information about how to respond to the error events.

Checking the health of tapes and tape drives
To check the health of tapes and tape drives, the Data Center uses the following two health indicators:
• Tape and Tape Drive Errors

• Tape Drive Cleaning Light

Tape and Tape Drive Errors
The health of a library tape and tape drive relates to the number of hard errors in the event log and the total number of errors in the Directory database. Hard errors can indicate tape or drive failures before an irreversible data loss. To view the total number of hard errors on each drive, use the Detect Tape and Tape Drive Errors.sql script. To get a copy of this script, visit the Resource Center.
Tape Drive Cleaning Light

The cleaning light turns on if the Data Center determines that the tape drive is dirty. If the cleaning light turns on frequently, there might be a problem with the drive. The frequency at which the cleaning light turns on is displayed as a number in the Directory database. To view a summary of this action, use the script Tape Drive Cleaning Light On.sql. The script explains how to install, run, and read the script results. To get a copy of the script, visit the Resource Center.


14

MONTHLY MAINTENANCE

About this chapter

Iron Mo

This chapter describes maintenance tasks that you must perform each month to ensure that the Data Center runs optimally.

For a checklist that you can use to keep track of monthly maintenance tasks, see Monthly maintenance checklist, on page 150.



How to maintain the Data Center databases Performing database maintenance, on page 124

How to maintain accounts Performing account maintenance, on page 127

How to evaluate the current storage capacity of the Data Center

Evaluating current Data Center capacity, on page 129

How to verify that you are using the most current firmware on the Data Center server

Verifying current firmware, on page 131

How to check the software licensing for the Data Center

Checking software licensing, on page 131

How to maintain the event logs Maintaining the event logs, on page 133

How to maintain tape libraries and drives Cleaning library and tape drives, on page 134

How to verify your record keeping Verifying records, on page 135


Chapter 14: Monthly Maintenance Performing database maintenance

Performing database maintenance

124 Co

The Data Center contains a monthly maintenance script (dbmaint.sql) that runs the DBCC utility (dbcc checkdb query). The DBCC utility comes with SQL Server. The DBCC utility checks each Data Center database for the following conditions:

• Logical and physical consistency in the database

• Correctly linked indexes and data pages in tables

• Data and index pages that are consistent with corresponding extent structures

• Correctly ordered indexes, consistent pointers, reasonable data information on each page, and reasonable page offsets

When you run the monthly maintenance script, you must perform tasks that are specific to your Data Center configuration. For this reason, the Data Center Setup program does not add the monthly script to the Windows Scheduler as it does for the daily and weekly scripts, which run on a schedule. You must run the monthly maintenance script manually.

The monthly maintenance script file (dbmaint.sql), is in the Data Center folder. To run the script, use SQL Query Analyzer or SQL Server Management Studio.

Note

Before you run the script, read the remainder of this section for important guidelines and instructions particular to your Data Center environment.

Considerations for stand-alone Data Centers
To perform maintenance on a stand-alone Data Center, you must stop the BackupServer service. When you stop the BackupServer service, backups that users initiate fail. For this reason, warn users before you perform maintenance on a stand-alone Data Center.
For more information about maintenance procedures, see Performing monthly database maintenance, on page 125. The procedures contain references to Server 1 and Server 2. When you follow the procedures, consider Server 1 as names of your Data Center servers. Ignore references in the procedures to Server 2.

Considerations for mirrored Data Centers

To prevent a service outage, continue to run one server in the mirrored pair while you perform maintenance on the other server. When you finish maintenance on the first server, repeat the maintenance tasks for the mirror server.

For more information about maintenance procedures, see Performing monthly database maintenance, on page 125. The procedures contain references to Server 1 and Server 2. When you follow the procedures, consider Server 1 and Server 2 as the names of your Data Center servers according to the following conventions:

• Server 1 represents the server that you shut down for maintenance.

• Server 2 represents the server that you continue to run.


Performing database maintenance Chapter 14: Monthly Maintenance

Considerations for clustered Data Centers

Iron Mo

For the purpose of database maintenance, consider each mirrored server pair in a clustered Data Center as a separate Data Centers. In other words, perform maintenance on one Data Center in the cluster (one mirrored pair), then perform maintenance again for the next Data Center in the cluster (the next mirrored pair). To save time, perform maintenance on all Data Centers in the cluster sequentially. For example, perform maintenance tasks in sequential order on one “side” of the cluster (such as the primary side), and then on the mirrored side. For more information about maintenance procedures, see Performing monthly database maintenance, on page 125.

Performing monthly database maintenance
Database maintenance comprises the following tasks:
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.

The following sections explain how to perform these tasks.

Note

Perform the tasks in the order in which they appear.

Step 1: Prepare the mirrored server
This procedure applies only to Data Centers that use mirrored environments.
To prepare the mirrored server, complete the following steps:

1. Open DCMC.

2. From the console tree, select Server 2.

3. Verify that services for Server 2 are running.

For more information about how to verify that services are running, seeVerifying that the services on the Data Center server are running, on page 110.

Step 2: Stop the server

To stop the server for maintenance, complete the following steps:

1. In the DCMC Console tree, expand your Data Center, and then expand the server name.

2. Right-click BackupServer, and then click Pause Service.

3. Right-click DCAlerter, and then click Stop Service.

4. Right-click ReplicationServer, and then click Stop Service.

5. Right-click PoolServer, and then click Stop Service.

6. Right-click IndexServer, and then click Stop Service.

7. If you use HSM, right-click BackupHSM, and then click Stop Service.

8. If you use HSM, right-click HSMPurge, and then click Stop Service.

9. Right-click Compactor, and then click Stop Service.


Chapter 14: Monthly Maintenance Performing database maintenance

126 Co

10. To verify that end-user retrieve requests for Server 1 are finished, complete the following steps:

a. Right-click BackupServer.

b. Select All Tasks.

c. Click Log Session Statuses.

d. Expand the Events node, and then click Application. Verify that there are no end-user retrieve requests in progress.

11. After all end-user retrieve requests complete, right-click BackupServer, and then click Stop Service.

Step 3: Run maintenance SQL scripts
To run maintenance SQL scrips, complete the following steps:
1. Verify that the Compactor service is stopped. If it is still running, stop the process or wait until the process finishes.

2. Open Microsoft SQL Server Query Analyzer or SQL Server Management Studio and connect to Server 1.


• If you run a stand-alone Data Center and use a tape system for your database backups, open the SQL script weeklymainttape.sql.

• If you do not run a stand-alone Data Center, open the SQL script weeklymaintdisk.sql.

The script files are in the Data Center folder, default location :\Data Center.

4. To run the SQL script, click Execute.

The system backs up the SQL databases and migrates them to Secondary Tape Sets (for HSM systems with Secondary Tape Sets). For more information, seeVerifying the results of the Weekly Automatic Procedure, on page 116.

5. After the SQL script finishes, run the SQL script dbmaint.sql.

The script is in the Data Center folder, default location :\Data Center. The SQL script can take minutes or hours to complete, depending on the size of your databases.

Step 4: Restart the server

To restart the server, complete the following steps:

1. To restart the services for Server 1, complete the following steps:

a. Open DCMC.

b. Expand Server 1 in the console tree.

c. Right-click each service, and select Continue Service.

2. To verify that Agents can connect to Server 1, complete the following steps:

a. Right-click BackupServer, select All Tasks, and click Log Session Statuses.

b. Expand the Events node, and click Application.

Note

Do not restart the server until after the SQL dbmaint.sql script finishes.


Performing account maintenance Chapter 14: Monthly Maintenance

Iron Mo

3. To verify that backups or retrieves are in progress, complete the following steps:

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.

Performing account maintenance
Abandoned accounts can clutter the Data Center and use space in the databases and archive storage. They also use up seats in the Data Center license.
To minimize clutter on the Data Center, look for the following types of accounts:

• Unowned accounts

• Unsupported Agent versions

• Duplicate accounts

• Inactive accounts

• Heavy hitters

• Invalid accounts

Unowned accounts
An account is unowned when the Data Center cannot determine ownership. You create an unknown account when you fail to enter a name, e-mail address, telephone number, or other information during the Agent Setup and registration process.
If you can get information about the account, use Support Center to enter the information. Otherwise, cancel the account.

In time, Compactor removes unowned accounts from the Data Center. To get a SQL script that finds unowned accounts on the Data Center, visit the Resource Center.

Unsupported Agent versions

An unsupported Agent version is an account that runs a version of the Agent software that your organization no longer supports. Your organization might discontinue support for an Agent version for several reasons:

• To reduce support costs and Help Desk calls

• Because Connected Backup no longer supports the Agent version

• Because the version has known issues

When you identify accounts that use unsupported versions of the Agent, upgrade the version. To do so, use the upgrade method that your organization employs. To get a SQL script that finds accounts that use unsupported versions of the Agent, visit the Resource Center.


Chapter 14: Monthly Maintenance Performing account maintenance

Duplicate accounts

128 Co

A duplicate account is an account that is unused because two accounts exist on the same Agent computer. Users might accidentally create a new account during the account recovery process instead of recovering an existing account. Users might create duplicate accounts if they are unaware of the account recovery process, or if an error occurred during the recovery process that forces the user to create a new account.

You cannot use an automated method to identify duplicate accounts.

To identify duplicate accounts, complete the following steps:

1. Find multiple accounts registered for the same e-mail address or name.

2. Determine whether the accounts that you identified in step 1 have the same computer name.

3. Verify that the last backup activity for one account ends, and that a new account registers shortly thereafter.

4. Verify that the new account you determined in step 3 has current backup activity and that the other account does not.

To get a SQL script that finds accounts with the same e-mail address on the Data Center, visit the Resource Center.

Inactive accounts

An inactive account is one that has had no recorded activity over an extended period of time. An account can become inactive for the following reasons:

• Attrition

• Duplicate account

• Inactive backup schedule

• Agent removed from the computer

For best results, select an account inactivity threshold time frame. For example, if an account has not performed a backup in the past 90 days, the account is inactive. The policy created should be published for end users and Help Desk representatives and should also accommodate end users on extended absence.

To identify inactive accounts, you can use the following SQL scripts:

Your organization can cancel these accounts, or notify the account owners that they have not backed up the accounts recently. To get copies of these SQL scripts, visit the Resource Center.

No Activity for 90 Days — Identifies accounts with no activity in the past 90 days

No Activity Ever — Identifies accounts with no activity at all


Evaluating current Data Center capacity Chapter 14: Monthly Maintenance

Heavy hitters

Iron Mo

The following Support Center reports examine the amount of data that each account backs up to the Data Center:

• Heavy Hitters

• Heavy Hitters Cumulative

The reports appear in the Support Center under the Reports node. For information about how to run and view the reports, see Support Center Help.

Regularly backups of large amounts of data indicate that an account backs up unnecessary data. Large backups put stress on the Data Center server, HSM, and the SQL databases.

Each organization must determine what constitutes heavy use and how to manage heavy hitters. Take steps to reduce or eliminate the load that heavy hitters put on the Data Center. Use the results from the heavy hitters reports to decide whether to exclude data from backups or to contact account owners about inordinately large backups.

Invalid accounts
An invalid account is an unstable account. Unstable accounts can occur from a failed registrations. The failure can be from a network error or another failure that did not let the system register. Invalid accounts are rare. To get a SQL script that finds invalid accounts, visit the Resource Center.
Evaluating current Data Center capacity

Monitor Data Center capacity on a monthly basis and during phases of initial deployment.

As you deploy the Agent to more computers, you might need to change 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).

Check Data Center capacity more frequently for aggressive deployments than for a slow deployments.

To determine when to check capacity, use time intervals based on milestones in your deployment. For example, check capacity when you reach 50%, 60%, 75%, and 90% of your installed projected capacity. To get copies of SQL scripts that you can use for capacity planning, visit the Resource Center

Perform system checks monthly to assess the following hardware and software requirements:

• CPU

• RAM

• SQL database disk partition

• Library slots, tapes, and labels (for HSM)


Chapter 14: Monthly Maintenance Evaluating current Data Center capacity

CPU

130 Co

For best performance, use a one gigahertz or higher Pentium® class processor for your Data Center servers. If the server overuses the CPU, add additional processors or upgrade the existing processors to improve performance. For more information about Data Center sizing requirements, see Chapter 4: Sizing Your Data Center on page 37.

Although CPU usage as a potential bottleneck to Data Center performance is easy to detect, it is difficult to address without a complete hardware upgrade. Certain processes (particularly compaction), however, can use a large amount of CPU resources. During these peak periods, measure CPU use.

To evaluate your server's CPU, use the System Monitor feature of your Windows Performance utility to determine averages during peak activity for the following metrics:

• Average CPU utilization: Processor\ % Processor Time > 80% indicates heavy CPU use.

Generally, a healthy CPU has peaks and valleys of use, with many of the peaks at 100%. Therefore, average processor activity during peak times indicates a better reflection of true performance than the peaks themselves. The average CPU use should be less than 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 a CPU under performs, replace it with a faster CPU instead of more CPUs. The Windows performance overhead incurred with multiprocessing causes less than optimal CPU performance.

RAM
Bottlenecks can occur if your server has limited RAM or disk space. Unlike disk or CPU use, you measure RAM use less directly because Microsoft SQL Server, the primary user of RAM in the Data Center, consistently uses nearly 100% of memory resources as it attempts to cache as much of the database in memory as possible.
To determine whether RAM limits system performance, use the System Monitor feature of your Windows Performance utility to determine averages during peak activity for the following metrics:

• Number of times Windows goes to disk: Memory\Pages/sec > 0 indicates that Windows goes to disk frequently, using disk I/O and CPU resources.

If you keep this value close to zero, you reduce performance problems incurred if you move to disk. To resolve this issue, add 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 weekly. Also, include this check in your regular assessments to evaluate factors that affect Data Center capacity. For more information, see Checking for available disk space, on page 119.


Verifying current firmware Chapter 14: Monthly Maintenance

Library slots, tapes, and labels

Iron Mo

Include your weekly check of library slots, tapes, and labels to evaluate factors that affect your Data Center capacity. For more information, see Tasks to complete daily for Data Centers that use tape libraries, on page 113.

If you configured your Data Center to use HSM, evaluate the capacity of your tape library. If you store too much data for your tape library, consider the following options as ways to create more space:

• Reevaluate the file selection rules and file retention policies to decrease the amount of data backed up and stored.

• Add more tape storage capacity because the solution supports multiple tape libraries.

Verifying current firmware
Occasionally, hardware manufacturers release firmware fixes and updates for issues. Check with the manufacturer of each hardware component in your Data Center for firmware updates that apply to your equipment.
Checking software licensing
You initially purchased a set number of licenses for the Data Center. You can update the Data Center license for the following reasons:
• 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.

• The license now controls access to some features.

Every server in a mirrored or clustered Data Center must have the same license. Therefore, every server must be licensed for the same features and the same number of end-user accounts.

Deploying Agents to additional accounts

If you plan to deploy the Agent to more computers, consider when you want to add more licenses.

To check for the number of available licenses, complete the following steps:

1. Open the DCMC.

2. Expand the Data Center in the Console tree and expand the primary Data Center server.

3. Expand the Events node, and then click Application.

4. Find the message that has a License Manager source. Event ID 9507 displays the number of seats and features that you or your has company purchased.

5. In Support Center, create a report that displays the number of active accounts.

For more information about how to request a new license, see Requesting a new license, on page 133.


Chapter 14: Monthly Maintenance Checking software licensing

Adding new NICs on the Data Center

132 Co

You create each license for a Data Center server based on the HostID of the network interface card (NIC). You need a new license if the Host ID on the server changes (you install a new NIC).

To determine the new HostID associated with the new card, complete the following steps:

1. Open a command prompt window.

2. Change the folder to the Data Center folder. By default, this folder is :\Data Center.

3. Type hostid.

The following example shows a system output:

The HostID for the current machine is:

0050dad5a9e6

For more information about how to request your new license, see to Requesting a new license, on page 133.

Note

Provide NetBios over TCP/IP on the Data Center servers. The HostID.exe program requires this configuration to verify the Data Center server's MAC address correctly against the Data Center license.

Determining HostIDs for additional NICs

Each license applies to a specific Data Center server. The association between the license and the server is based on the HostID of the server’s network interface card (NIC). You can install a maximum of four NICs on your Data Center server. If your Data Center server uses multiple NICs, the license file must be aware of each NIC.

To determine the HostID of a NIC, complete the following steps:

1. Open a command prompt window.

2. Change the directory to the Data Center folder. By default this directory is :\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

4. Record the Host IDs in the table Licensing Information, on page 142.

For more information about how to request a new license, see Requesting a new license, on page 133.

Note

Provide NetBios over TCP/IP on the Data Center servers. The HostID.exe program requires this configuration to correctly verify the MAC address of the Data Center server against the Data Center license.


Maintaining the event logs Chapter 14: Monthly Maintenance

Changing the features offered to end users

Iron Mo

If your organization adds or removes features, get a new license to activate or deactivate features.

Requesting a new license
To request a new license, complete the following steps:
1. In a Web browser, enter the following URL:

http://www.ironmountain.com/US/support/licensedsoftware.asp

2. Enter and submit the license information.

After the information processes, you receive an e-mail with a new license.dat file and installation instructions.

Maintaining the event logs

Windows event logs record software, hardware, and system information. They provide valuable diagnostic information in case of system failure. Track your event logs to help diagnose problems in case of system failure.

The Data Center saves and clears the Application log only if the Data Center is the application that fills the log. If a different application, such as SQL Server, fills the log, the Data Center does not save and clear it. Therefore, save and clear the Application log manually. The Data Center never saves and clears the System and Security logs.

Store at least three months of event logs. Over time, these logs might become full. Save and clear the current Application and System logs. When the Data Center detects a full DCMaint, the Data Center saves the log to the Log Files folder and clears the log.

To save and clear the event logs, complete the following steps:

1. Open the DCMC.

2. Expand the Data Center Console tree and expand the server name.

3. Expand the Events node, and then click Application.

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 dialog box navigate to the \Log Files folder (by default, this folder resides on the same drive as the \Customers folder).

8. Name the log file with a unique name that clearly identifies the log file type and time period of events in the log. For example, you can use the following name to indicate the saved file contains the Application event log for the month of April, 2008:

App4_1_08_to_4_30_08.evt

9. Repeat the steps in this procedure for the DCMaint and System event logs.


Chapter 14: Monthly Maintenance Cleaning library and tape drives

Preventing overwriting of logs

134 Co

To configure Windows so that it does not overwrite log files, complete the following steps:

1. Open the Windows Events Viewer.

2. Click one of the three logs (Application, DCMaint, or System).

3. On the Actions menu, select Properties.

4. In the Log Properties window, select Do not overwrite events.

5. Click OK.

6. Repeat these steps for each log.

Increasing the log file size
Because the Data Center does not save and clear the Application event log if a different applications fills the log, you can increase the maximum log size.
To increase the log size to 50 MB or greater, complete the following steps:

1. Open the Windows Events Viewer.

2. Click Application.

3. On the Actions menu, select Properties.

4. In the Log Size section on the General tab, change Maximum Log Size to 50 MB (recommended) or greater.

5. Click OK.

Cleaning library and tape drives
If you use a tape library with your Data Center, clean the library and its tape drives to remove accumulated dust and contamination on the drive read/write head. The recommended maintenance schedule depends on the type of library, drive, or media. To determine how frequently you clean the library and the drives and how to clean them, see your tape library documentation. In addition the manufacturer's guidelines, use the following guidelines:
• Use DCMC to stop the HSM services including BackupHSM and HSMPurge.

• Have an adequate supply of cleaning tapes for the number of tape drives in your library.

• Use cleaning tapes a fixed number of times before you discard them. Note each time that you use a cleaning tape and discard it immediately after its 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 service.

Cleaning the SQL database backup tape drive

Clean the tape drive that you use for SQL database backups. Many types of tape drives exist, each with its own maintenance schedule. To determine how frequently to clean the drive and how to clean it, see your tape drive documentation.


Verifying records Chapter 14: Monthly Maintenance

Verifying records

Iron Mo

To ensure that Data Center records remain current, complete the following tasks:

• Examine the daily and weekly scheduled maintenance records to ensure that you performed and recorded the maintenance.

• Compile the system use records, such as the number of end-user accounts, backups, and retrievals, and publish them.

• Examine the service availability records, and compile and publish service availability statistics on a rolling twelve-month basis.

• Examine hardware maintenance records, system software upgrade records, and records of procedure that you performed on the Data Center procedures to verify that you or your staff keeps these records up-to-date.

• Examine the training records of Data Center operators to ensure that you properly train your staff.

• Verify that your vendor support contracts are current.

• When the Data Center server certificate expires after two years, replace the certificate with one that has an expiration date of five years into the future. To do so, run the Certificate Renewer utility. For more information, visit the Resource Center.


PART V: APPENDICES

Appendix A: Worksheets and ChecklistsAppendix B: Data Center Installation WorksheetsAppendix C: Maintenance Checklists

A

Worksheets and Checklists

About this appendix

Iron Mo

This appendix provides worksheets and checklists to help you manage your Data Center.


Information to track for software versions Software versions, on page 140

Information to track for the Data Center server Data Center server information, on page 141


Appendix A: Worksheets and Checklists Software versions

Software versions

140 C

Use the worksheets in this section to track information about your Data Center and Agents. Update the information after you upgrade the software, operating system, SQL Server, and hardware.

Data Center
Use the following table to track the version of the Connected Backup software that runs on your Data Center. Update the table after you install hotfixes and service packs.
Server Version Installation date

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

Microsoft SQL Server version

Use the following table to keep track of the version of the SQL Server that runs on the Data Center servers. Update the table after you install hotfixes and service packs.

Server Version/update number Installation date

onnected® Backup Data Center Deployment Iron Mountain Incorporated

Data Center server information Appendix A: Worksheets and Checklists

Agent

Iron Mo

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 you install hotfixes and Service Packs.

Type (PC or SV)

Community Version Deployment date

Data Center server information
Use the worksheets in this section to track information about your Data Center server.
Server name and IP address

Use the following table to track Data Center server names, IP addresses, and configuration types.

Server name IP address Primary/ secondary

Registration master


Appendix A: Worksheets and Checklists Data Center server information

Licensing Information

142 C

Use the following table to track the number of licenses, host IDs, and licensed features on each Data Center server.

Server name Host ID Number of licenses

Type (PC or PC with Server Option)

Features


B

Data Center Installation Worksheets

About this appendix

Iron Mo

This appendix contains worksheets that you can use to record information that you need when you install the Data Center server software.

This appendix contains the following information:


Information you need before and during a Data Center installation

Data Center Installation Worksheets, on page 144


Appendix B: Data Center Installation Worksheets Data Center Installation Worksheets

Data Center Installation Worksheets

144 C

Use the Data Center installation worksheets to record information when you install the Data Center server software.

Server names and IP addresses
Use the following table to track Server names and IP addresses that you assign to the Data Center server(s).
Server Name Server DNS Name IP Address

Logical drive information

CAUTION

When you choose names for your Data Center server(s), do not use the words “backup” and “update” (and other keywords that Microsoft SQL Server uses) as part of the server name. If you use these words in the server name, it causes problems when the Data Center software attempts to perform SQL queries. Also, do not use special characters, such as a hyphen (-), in the server name.

Use the following table to track the drive letter and purpose for each disk drive on each Data Center server:

Drive Contents Size (GB) RAID Level


Data Center Installation Worksheets Appendix B: Data Center Installation Worksheets

SQL Server logon

Iron Mo

Use the following table to track the Logon names and passwords (a domain account with local administrator privileges) necessary to run Microsoft SQL Server on the Data Center server(s):

Server Name User ID Password

Domain name
Name of the Windows domain where you add the Data Center server(s). You must use an account and password that has administrator privileges in this domain. You use this account to set up the server(s).
NT Domain:___________________________

Domain account
Domain account that has local administrative rights to the Data Center server(s). The account should be unprivileged except on the server(s). Setup creates these accounts during installation, or you can create them.
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 administrative password

The password that you assign to the Support Center Admin Technician ID belongs to the first Technician ID that you authorize to use Support Center. It is not a Windows account name.

Support Center Admin Password: _______________________________________


Appendix B: Data Center Installation Worksheets Data Center Installation Worksheets

Master Encryption Key (MEK)

146 C

Encryption key the DataCenter software generates to encrypt all other encryption keys on the Data Center. Use the MEK that DataCenter generates randomly 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:
EMCR 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
Network Attached Storage (NAS)
Share for the NAS: ________________________________________

Expiration parameters

Expiration parameters, which the DataCenter software prompts you for during installation. Accept the defaults if you are not sure of.:

Expiration Parameter Default Value Chosen Value

Canceled 60 days

Deleted 90 days disk only

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


C

Maintenance Checklists

About this appendix

Iron Mo

This appendix contains checklists that you can use when you perform Data Center maintenance tasks.

This appendix contains the following information:

To learn about.. See:

Tasks you complete on a daily basis Daily maintenance checklist, on page 148

Tasks you complete on weekly basis Weekly maintenance checklist, on page 149

Tasks you complete on a monthly basis Monthly maintenance checklist, on page 150


Appendix C: Maintenance Checklists Daily maintenance checklist

Daily maintenance checklist

148 C

This section contains a checklist of tasks to perform each day. An M indicates a task to complete at the start of the day, and an A indicates a task to complete at the end of the day. You must perform some of the tasks at both times of the day. Each step in the checklist provides a page reference in case you need detailed information for that step.

√ Morning/Afternoon

Task Page

M Verify the results of the daily automatic procedure. 108

M, A Verify that services are running using DCMC. 110

M, A Examine the event log through DCMC for any warnings or errors that might need attention.

111

M Verify personal backups by reviewing Agent logs for recent backups. 112

M, A Verify that Support Center and Account Management Website are running.

112

M, A Check Copy On Reference and replication using DCMC. 112

M Check disk status and unknown disk space using DCMC. 113

M Verify that the IT alert system works. 110

M, A For Data Centers using tape libraries, check the tape drive status and tape requests in DCMC.

113

M For Data Centers that use Secondary Tape Sets, determine whether or not to remove Secondary Tape Set tapes.

114


Weekly maintenance checklist Appendix C: Maintenance Checklists

Weekly maintenance checklist

Iron Mo

This section contains a checklist of tasks to perform each week. Each step in the checklist also includes a page reference in case you need detailed information for that step.

√ Task Page

Verify the results of the weekly automatic procedure by reviewing the weeklymaint.out file with a text editor.

116

Back up Support Center reports. 118

Back up Agent Configurations. 118

Back up the Connected Windows registry key. 118

Check for available disk space. 119

For database backups performed to tape, remove and rotate current backup tape and store in a safe place.

120

For mirrored or clustered Data Centers: Check time synchronization between mirrored servers. Time on both servers should be within 30 seconds of each other.

120

Visit the Resource Center to check for software updates. 120

For Data Centers that use tape libraries, check blank tapes, tape use, recyclable tapes, and cleaning tapes.

120

For Data Centers that use tape libraries, check library tape slots. 122

For Data Centers that use tape libraries, check the event log to verify successful purge and migrations are occurring on a regular basis.

122

For Data Centers that use tape libraries, check tape and tape drive health. 122


Appendix C: Maintenance Checklists Monthly maintenance checklist

Monthly maintenance checklist

150 C

This section contains a checklist of tasks to perform each month. Each step in the checklist also includes a page reference in case you need detailed information for that step.

Monthly checklist

√ Task Page

Run the database maintenance script, dbmaint.sql, using SQL Query Analyzer.

124

Run Account Management SQL scripts. 127

Evaluate current Data Center capacity by checking CPU, RAM, disk utilization and tape library utilization.

129

Verify firmware is current with manufacturer’s specifications. 131

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.

131

Use Windows Event Viewer to save and clear the event log. 133

For Data Centers using tape libraries, clean the library and tape drives. 134

For database backups performed to tape, clean the backup tape drive. 134

Verify that record keeping is up-to-date. 135


Symbols, 31

Aaccess, Data Center Management Console (DCMC) 87accounts

choosing for tape groups 31duplicate 128heavy hitters 129inactive 128invalid 129management 127reducing unnecessary 127unowned 127unsupported Agent versions 127with excessive backup amounts 129

adding new licenseabout 133adding seats to Data Center 131additional host ID 132additional NIC 132changing Agent features 133

Agentaccess to Data Center, verifying 57licensing, features 133replication of configuration files, about 18

antivirus softwareon the Data Center 45

application event log, automatic backup of 101archive

balancing tape utilization 27secondary tape sets, about 24

archive setsand Compactor 32deleting, and compaction 32repackaging, about 32replication, about 17

archive storage device, Data Center worksheet 146Attached Storage Network (SAN),using 46

Iron Mountain Incorporated

Bback up

databases 116off-site tapes, about 25PEM files 67rotating tape 120Support Center reports 118

BackupHSMservices 19

backups, managing excessive 129BackupServer 16

installation, troubleshooting 71overview 16verifying operation 69

Ccapacity

checking disk space 119evaluating Data Center 129tape library 131

Centerausing 47verifying operation 70

checkingavailable tape slots 122Data Center license 131disk space status 119hardware firmware 131recyclable tapes 121tape drive health 122tape health 122tape usage 121

cleaningSQL database backup tape drive 134tape library 134tapes, managing 122

clustered Data Centerabout 42monthly tasks 124

community,tracking Agent version 141Compactor

and tape groups 31archive sets, deleting 32archive sets, repackaging 32

INDEX

Connected® Backup Data Center Deployment 151

Index

choosing tape account groups 31database entries, deleting 32disk space check 31expiration parameters, Data Center worksheet 146file expiration 33migrating archive sets to tape 33system analysis and repair 32

configuringcommunities 74DCAlerter 74enterprise directory integration 74

Copy On Reference 18CPU utilization, evaluating 130Customer directory, antivirus programs 45, 106Customer volume, checking disk space 119

DData Center Management Console (DCMC)

accessing 87interface 89menus and toolbars 91

Data Center Toolkitabout 96description 94installing 96requirements 96

Data Center worksheetemail settings 145

data migration and HSMPurge 19database

backup to disk 116backup to tape 116cleaning backup tape drive 134clearing transaction logs 116compaction and deleting entries from 32Master, Model, MSDB, backing up 117monthly maintenance 124replication of 17rotating backup tapes 120

DataBundlerbefore installing 95installing 94system requirements 94usage requirements 95

DBCC utility 124dbmaint.sql 124DCAlerter

about 19configuring 74Data Center worksheet 145

default data expiration settings 33deleting archive sets, and compaction 32details, tape 22Directory database,backing up 116

152 Connected® Backup Data Center Deployment

disabling Removable Storage Manager (RSM) 49disk

space, check available 119space, checking during Compaction process 31

disk-only configurationexpiration rules, about

expiration, about 33Distributed AML Server (DAS)

using 49verifying operation 70

domain account, Data Center worksheet 145domain controller, using Data Center as 43domain name, Data Center worksheet 145domain, Data Center assigning 55drivers, installing tape library 56duplicate accounts, managing 128

Eemail alerts, configuring DCAlerter 74email settings, Data Center worksheet 145EMC Centera

using 47verifying operation 70

emergency repair diskcreating on Windows 2000 57creating on Windows 2003 58

enterprise directorymanaging 77

errors, checking tape 122evaluating

CPU utilization 130Data Center capacity 129RAM utilization 130

event logautomatic backup of 101configuring email alerts 74DCAlerter service 19maintenance 101

excessive backups, managing accounts 129expiration

about 33default settings 33marking files for 32of files, and Compactor 33parameters, Data Center worksheet 146

Ffeatures, licensing for Agent 133file expiration parameters, Data Center worksheet 146files

marking as expired, about 32replication, about 17uncommon, and PoolServer 18


Index

firmware, checking 131formulas

average CPU utilization 130RAM utilization 130system processor queue length 130

Ggroups

tape account, choosing for compaction 31tape, about 22

guidelinesSCSI ID for multiple SCSI busses 48SCSI ID for single SCSI bus 48

Hhardware

firmware, checking 131requirements for MyRoam 60requirements for Support Center 60

hardware requirementsData Center 43

heavy hitter accounts, managing 129Hierarchical Storage Manager. See HSMhost ID, new license 132HSM

balancing tape utilization 27cleaning tape library 134cleaning tape library drives 134determining tape capacity 26Distributed AML Server (DAS), using 49EMC Centera, using 47installation, troubleshooting 71migrating to Secondary Tape Set 116migration and purge 22mirgration 22mixed libraries 27multiple SCSI busses, guidelines 48multiple tape libraries 25primary tape set, about 23Removable Storage Manager (RSM), disabling 49requirements 46secondary tape sets, about 23single SCSI bus, guidelines 48taking tapes off-site, about 25tape (see tape) 22tape and tape account groups, about 22tape library requirements 47Tape Sets 23tape utilization 26temporary reliever library 26transitioning to new tape library, about 26using different tape technologies 27verifying migration 122


verifying operation 70HSMClient, about 19HSMPurge, about 19HSMServer

about 19components 19

HSMServer, components of 19

IIIS

configuring on Windows 2003 Server 54installing on Windows 2003 Server 54using with Support Center and MyRoam 53

inactive accounts, managing 128IndexServer 17installation

attached library, troubleshooting 72BackupServer, troubleshooting 71Data Center, troubleshooting 71HSM, troubleshooting 71Support Center and MyRoam 72

invalid accounts, managing 129IP addresses, Data Center worksheet 144

Llibraries

checking available slots 122different technologies, using 27multiple, using 25tape capacity 131tape usage 121temporary use of 26transitioning to new 26

licenseadding Agent features 133adding users 131additional host ID 132additional NIC 132checking Data Center 131Data Center 43host ID change 132new NIC 132removing Agent features 133requesting new 133tracking information 142updating Data Center 131

lmhosts file, configuring 55logical drive information

Data Center worksheet 144logs

Application event 100automatic backup of 101DCAlerter service 19


Index

DCMaint 100Event 100Trace 100

Mmaintenance

daily tasks 107event log 101monthly tasks 124weekly tasks 115

managingaccounts excessive backup amounts 129accounts on the Data Center 127accounts unsupported Agent versions 127duplicate accounts 128heavy hitter accounts 129inactive accounts 128invalid accounts 129unowned accounts 127

Master database, backing up 117Master Encryption Key (MEK), Data Center worksheet146measuring

CPU utilization 130Data Center capacity 129RAM utilization 130

MicrosoftIIS 54software requirements 44SQL Server 2000, installation guidelines 58Windows Server, configuration guidelines 53Windows Server, installation guidelines 52

Microsoft SQL Server, track version 140Microsoft Windows, track version 140migration

Secondary Tape Set 116verifying status 122

mirrored Data Centerabout 42database backup 116date and time, synchronizing 56monthly tasks 124network, verifying 57replication, verifying 70synchronizing system time 120

Model database, backing up 117monthly maintenance

tasks 124MSDB database, backing up 117MyRoam

moving the scratch folder 73


MyRoam serverhardware requirements 60installing 72preparation 61requirements 59software requirements 60verifying installation 73

Nnetwork

assigning Data Center to domain 55logins, Data Center 51mirrored Data Center, verifying connection 57ports 50remote access to Data Center, verifying connection

57requirements, Data Center 49

Network Attached Storage (NAS)Data Center worksheet 146using 46

new license, requesting 133NIC

license for additional 132license for new 132

Oobtaining new license 133off-site tape sets 25overview

BackupHSM 19BackupServer 16DCAlerter 19event log 100HSMClient 19HSMPurge 19IndexServer 17ReplicationServer 17

Ppartitions, Data Center server creating 55PEM files, backing up 67performance, evaluating Data Center 129permanent license, Data Center 43Pool account, about 18ports for network access 50ports, Data Center 49preparing for installation

Data Center 41Support Center and MyRoam 59

Primary Tape Set 23purging archive sets 19


Index

Qquerying for

duplicate accounts 128heavy hitter accounts 129inactive accounts 128invalid accounts 129unowned accounts 127unsupported Agent versions 127

RRAM utilization, evaluating 130record keeping,verifying 135recyclable tapes, checking 121Registry database,backing up 116reinstallation, Data Center server 67remote access to Data Center, verifying 57Removable Storage Manager (RSM), disabling 49removing Agent features, licensing 133repair disk

creating on Windows 2000 57creating on Windows 2003 58

replicationabout 17database 17verifying 70

ReplicationServer 17reports, backing up Support Center 118requesting new license 133requirements

Data Center software 44hardware 43HSM 46MyRoam 59network, Data Center 49software 44Support Center 59Support Center and MyRoam server 59tape library 47

Resource Center 8results

weekly maintenance 116results,weekly maintenance 116retrieving files and HSMClient 19reusing tapes 121rotate, database backup tapes 120

Sscratch folder

moving on the Data Center server 73SCSI

multiple busses guidelines 48single bus guidelines 48


Secondary Tape Setdeciding to use 24description 23migrating to 116taking off site 25

securityData Center 51

SendOnceCopy On Reference process, about 18

serverassigning Data Center to domain 55Data Center install, verifying 67Data Center worksheet 144Data Center, reinstalling 67lmhosts file, configuring 55SQL Server 2000, installing 58Web server preparation 61Windows Server, configuring 53Windows Server, installing 52

service login accounts, Data Center 51services, Data Center

BackupServer 16Compactor 31DCAlerter 19HSMClient 19HSMPurge 19HSMServer 19IndexServer 17ReplicationServer 17

settings,file expiration defaults 33software requirements

Data Center 44for MyRoam 60for Support Center 60

software versionMicrosoft SQL Server worksheet 140Microsoft Windows worksheet 140

SQL databasebackup volume, checking for disk space 119backups, rotating tapes 120cleaning backup tape drive 134volume, checking for disk space 119

SQL Server 2000installing 58login, Data Center worksheet 145

standalone Data Centerabout 42database backup 116monthly tasks 124rotating SQL backup tape 120

Support Centerbacking up reports 118hardware requirements 60software requirements 60


Index

Support Center serverinstallation, verifying 73installing 72preparation 61requirements 59

synchronicity of account data, and Compactor 32synchronization, system time 120synchronizing date/time, mirrored Data Center 56System Monitor

evaluating CPU utilization 130evaluating RAM utilization 130

system time, synchronization 120

Ttape 22

account groups 22account groups, choosing for compaction 31checking available slots 122checking health 122checking recyclable 121checking usage 121compaction of, about 31errors 122groups 22groups and account groups, about 22libraries, using different technologies 27library capacity 131managing cleaning 122multiple libraries 25primary set and HSM 23primary set, and HSM 23reusing 121secondary set and HSM 23sets, taking off-site 25transitioning to new library 26utilization, balancing 27

tape driveschecking health 122cleaning 134

tape librarycleaning 134cleaning drives 134Distributed AML Server (DAS), using 49driver, installing 56installation with attached library, troubleshooting

72multiple SCSI busses guidelines 48requirements 47single SCSI bus guidelines 48verifying operation 70


Tape Setsprimary 23secondary 23

tape sets 23view 23

TCP access, Data Center 49technicians,validating 76temporary license, Data Center 43time, synchronizing system 120tools

Data Center Toolkit 94DataBundler 94

trace logging, about 100transaction logs, clearing 116troubleshooting

BackupServer installation 71Data Center installation 71HSM installation 71installation with attached tape library 72

UUDP access, Data Center 49unowned accounts, managing 127unsupported Agent versions, finding accounts with 127updating, Data Center license 131usage, tape 121utilization of tapes, about 27

Vvalidate Support Center technicians 76verifying

available tape slots 122BackupServer 69Data Center install 67disk space 119HSM installation 70mirrored Data Center replication 70record keeping 135Support Center and MyRoam installation 73tape health 122weekly maintenance results 116

viruses in archived files, about 45, 106volumes

Data Center server creating 55

WWeb server

preparation 61requirements 59Support Center and MyRoam, installing 72verifying installation 73


Index

Windows Serverauthentication, Data Center 51configuring 53installing 52

worksheetlicense information 142Microsoft SQL Server version 140server name and IP address 140


Connected Backup Data Center Deploymentmysupport.download.microfocus.com/SSO/online_help... · 8 Connected® Backup Data Center Deployment Iron Mountain Incorporated Related documentation

Documents