Backup and Restore for Internet Data Centers Version 1.0

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred. © 2002 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, BizTalk, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Contents Chapter 1

Backup and Restore Design

1

Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 The Importance of Backing Up the Internet Data Center Environment . . . . . . . . . . . . 1 Assessing Your Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Backup Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Disaster Avoidance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Disaster Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Best Practices for Developing a Backup Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Backup Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Avoiding Unnecessary Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Choosing an Appropriate Time for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Choosing the Appropriate Type of Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Choosing the Appropriate Storage Media to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Galaxy Software Modules and Core Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 CommCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Galaxy Architecture and Deployment Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Distributed MediaAgent Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 CommCell Deployment Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Deciding What to Back Up and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Front-End Web Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Infrastructure VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Data VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Management VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Summary of Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Galaxy Solution Design and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Hardware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Best Practices for Configuring Galaxy Components . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 2

Backup and Restore Deployment Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Back-End Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Middle-Tier and Web-Tier Components . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Galaxy Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployment Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Firewall Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31 31 31 31 32 32 32 33 33

iv

Contents

CommServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing the CommServe Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing the CommServe on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Installing a MediaAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Installing a MediaAgent on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Drive and Library Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 After You Install a MediaAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 iDataAgent for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Installing iDataAgent for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Installing iDataAgent for Windows 2000 on a Cluster . . . . . . . . . . . . . . . . . . . . . . . 60 Backing Up iDataAgent for Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Database iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Installing the Database iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . 66 Installing the Database iDataAgent for Exchange 2000 on a Cluster . . . . . . . . . . . . 69 Backing Up the Database iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . 73 Mailbox iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Installing the Mailbox iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . . . 74 Installing the Mailbox iDataAgent for Exchange 2000 on a Cluster . . . . . . . . . . . . . 77 Installing the Mailbox iDataAgent for Exchange 2000 on a Cluster . . . . . . . . . . . . . 78 Backing Up the Mailbox iDataAgent for Exchange 2000 . . . . . . . . . . . . . . . . . . . . . 82 iDataAgent for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Installing iDataAgent for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Installing iDataAgent for SQL Server on a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Backing Up iDataAgent for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Getting Started with iDataAgent Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Overview of the CommCell Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Starting the CommCell Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Installing for CommCell Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Administration Using the CommCell Snap-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 3

Basic Backup and Restore Operations Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Daily Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Events for the Last 24 Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Backup History for the last 24 Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review the Media Management Housekeeping Report . . . . . . . . . . . . . . . . . . . . . Review the Scratch Pool Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107 107 107 108 108 108 109 109 110

Contents

v

Managing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incremental Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Differential Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synthetic Full Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scheduled Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Subclients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing On-Demand Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating Backup Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Data to Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Data to Exchange 2000 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Data to SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Media into a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Media from a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112 112 112 112 114 114 114 120 122 123 124 124 128 130 131 131 132 134

Chapter 4

Advanced Backup and Restore Operations Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Area Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAN Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAN Addressing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCSI-LUN Mapping Guidelines for SAN Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . Avoiding Common SAN Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAN Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . License Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Destination of CommServe ExpressRecovery Backups . . . . . . . . . . . . . . . . . . . . . Galaxy Service Control Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Galaxy Service Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CommCell Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alert Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auxiliary Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Pruning Overview and Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rules for Archive Pruning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Galaxy Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering a CommServe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

135 135 135 135 135 137 138 142 144 145 145 149 150 151 157 158 162 166 167 180 182 189 200 202 202 204

vi

Contents

MediaAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing the Index Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Drive Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSM-Controlled Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering a MediaAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Libraries and Drive Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Master Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Groups and Scratch Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stand-alone Drive Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating a Magnetic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client Job Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Pipeline Pairs to Configure for Multiple Network Interfaces . . . . . . . . . . . . . iDataAgents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Subclients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using On-Demand Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iDataAgent for Windows 2000: Browse and Restore Operations . . . . . . . . . . . . . . Database iDataAgent for Exchange 2000 Server . . . . . . . . . . . . . . . . . . . . . . . . . Mailbox iDataAgent for Exchange 2000 Server: Restore Operations . . . . . . . . . . . Limitations of the Default Settings of Browse and Restore Operations . . . . . . . . . iDataAgent for SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Managing Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total Disaster Recovery Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total Disaster Recovery Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering a Computer Running Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . Restoring Exchange 2000 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restoring SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Additional Resources

206 206 212 213 215 216 218 218 218 219 219 220 221 222 223 226 228 229 229 231 231 233 235 244 247 249 253 260 261 261 262 281 284

289

1 Backup and Restore Design Abstract This chapter describes the Microsoft® Internet Data Center backup and restore solution. Data center backup principles and strategies are described, together with methods of assessing what to backup in an Internet Data Center environment. The recommended backup and restore solution uses CommVault Galaxy software in each of the Internet Data Center virtual local-area networks (VLANs). The functionality of Galaxy software is explained and the design of the solution is described, including details of the planning and configuration steps required to successfully implement this backup and restore solution.

Introduction The Internet Data Center architecture is designed to provide resilience with no single point of failure. It is still essential, however, to make adequate backups so that data and systems configuration can be restored in the event of a catastrophic failure. Although you may take every conceivable precaution, it is impossible to plan for every disaster or outage that could affect a data center, which is why planning a strategy for disaster recovery is so important.

The Importance of Backing Up the Internet Data Center Environment The quantity of data that is stored in Internet Data Center environments varies but can grow as large as multiple terabytes, while the number of supported users will increase as well. In this type of constantly changing environment, mission-critical applications must be available, downtimes must be kept to a minimum, and increased dependence on the multiple tiers must be managed effectively.

2

Backup and Restore for Internet Data Center

It is important to back up Internet Data Center environments to protect critical data and allow it to be restored quickly in the event of any data loss, whether small or large. Data loss can result from the following: ● Hard disk subsystem failure ● Power failure (resulting in corrupted data) ● Systems software failure ● Accidental or malicious deletion or modification of data ● Viruses ● Natural disasters (that is, fire, flood, earthquake, and so on) ● Theft or sabotage An organization must be able to recover quickly from any outage or disaster, whether the situation involves a simple component failure or the complete destruction of a site. Therefore, when designing a backup and recovery architecture, you should consider all types of failure. The architecture you select should be based on well-defined system availability requirements and should take into account the contents and configuration of each server.

Assessing Your Situation For each operating system and application introduced into an Internet Data Center environment, consider the following questions: ● What are possible failure scenarios? ● What is the critical data and where is it located? ● How often are backups required? ● When should full backups be done, as compared to incremental or differential backups? ● What backup media will be used (magnetic disk, magneto-optical disk, or tape)? ● Will backups be performed online or offline? ● Will backups be started manually, or automatically according to a schedule? ● What will be used to test for valid backups? ● Where will backups be stored (on-site, off-site, or both)? A good backup and recovery architecture should include a disaster avoidance plan, procedures, and tools that assist in recovering from a disaster or outage, and detailed procedures and standards for performing the recovery. For each subject area, the architecture should clearly define the people, process, and technologies required for success.

Chapter 1: Backup and Restore Design

3

Backup Design You should consider a number of factors when developing a backup solution for the Internet Data Center architecture. For example, you’ll need to determine how to anticipate and avoid disasters, decide which parts of the environment should be backed up and how often, and learn how to plan a backup and recovery strategy for the environment. Your completed solution should include well-documented disaster avoidance and disaster recovery plans.

Disaster Avoidance Plan A disaster avoidance plan must anticipate events that can affect system operation and provide for such occurrences. Events that can disrupt Internet services range from an Internet connection problem to minor failures in components that cannot readily be replaced, to more complex software problems. Elements of a successful disaster avoidance plan include geographical redundancy and remote storage of backup tapes. Use of redundant, geographically distant data centers is good way to ensure that a regional catastrophe does not eliminate the ability to provide service. Removing backup tapes from each data center is a good way to avoid losing both the data center and the data center’s backup mechanism. Depending on the importance of the data, several off-site storage facilities can be used. Off-site storage need not add a great deal to the cost of the backup and recovery architecture; many companies provide off-site storage services and will pick up and deliver backups tapes when the tapes need to be rotated. A disaster avoidance plan must be based on the performance and availability requirements defined for the particular application being hosted. If the application serves a specific region, for example, it may not make sense to include a second, geographically distant data center in planning.

Disaster Recovery Plan A disaster recovery plan prepares an organization for recovering from disasters and outages that cannot be avoided. When developing the plan, consider the following: ● Can business operations continue during a disaster or outage? A disaster recovery plan should include procedures for maintaining business operations during a disaster or outage (including network outages). For example, the telephones in the sales department will continue to ring even when the server is not operational, so staff may need to take orders manually until the server is operational again. Each department should work out strategies for such situations. ● How is the disaster recovery plan to be created and maintained? To ensure its success, the disaster recovery plan must be managed properly. It is recommended that one or more members of the organization be responsible for supervising the organization’s disaster preparation efforts. Someone must install and

4

Backup and Restore for Internet Data Center

maintain hardware protection devices, ensure that all departments have a plan if the server fails temporarily, ensure that backups are made and rotated off-site regularly, and create extensive documentation to support the disaster recovery plan.

Best Practices for Developing a Backup Solution When developing a backup solution, follow these recommendations: ● Involve the correct personnel and use the appropriate resources when developing and testing backup and restore strategies. ● Create a data protection organization chart that includes responsibilities and contact information for each person. ● Perform an initial full backup of every volume that needs protection. ● Back up system state for every server and ensure that Microsoft Active Directory® directory service is included for each domain controller. ● Print and review backup reports for CommVault Galaxy systems to ensure that all files are being backed up correctly. ● Perform trial restorations of data periodically to verify that the files are being backed up correctly. ● Ensure that backup media, systems, and servers are secured in a manner that prevents a rogue administrator from restoring stolen data onto your server. ● Develop and implement a disaster recovery test plan to ensure the integrity of your backup data.

Backup Strategies You should consider a number of factors when planning for your backup solution, such as backing up only what is necessary, scheduling backups carefully, and choosing the appropriate type of backup to perform.

Avoiding Unnecessary Backups When designing a backup strategy, you may be tempted to perform a full backup of every server in the environment. Keep in mind, however, that your objective is to successfully restore the environment after an outage or disaster. Therefore, your backup strategy should focus on the following goals: ● The data to be restored should be easy to find. ● The restoration should be as quick as possible.

Chapter 1: Backup and Restore Design

5

If you back up every server indiscriminately, you will have a large volume of data to recover. Although current tape storage and backup products allow for fast restoration of data, it may increase downtime if everything must be restored from tape. For example, most backup products require the following steps: 1. Reinstall the operating system. 2. Reinstall the backup software. 3. Restore the backup from tape. The more files you are backing up, the longer the backup takes to perform and, more important, the longer it takes to restore the files. When disaster strikes, time is critical, so the shorter the restoration process, the better. Furthermore, large backups that are performed on a regular basis affect network performance negatively unless you establish a dedicated backup network. After you have determined the optimal backup strategy for your environment, it is vital that you perform a trial restoration across the entire test network. This trial identifies any problem areas and provides useful experience in restoring systems in the Internet Data Center environment, without the pressure of having to bring a production system back online. (The CommVault Galaxy interface, which is described more fully later in this chapter, simplifies data identification so that you can select the appropriate data to back up and then restore critical data first.)

Choosing an Appropriate Time for Backup Backing up an e-commerce environment is not the same as backing up a corporate local area network (LAN) infrastructure. On a corporate LAN, network usage usually drops outside of core business hours. In an e-commerce environment, usage generally increases in the early evening and may continue at this level until the early hours of the morning, especially if the customer base spans multiple time zones. For this reason, it may not be possible to identify an ideal time to back up your environment. To reduce impact to Web customers, follow these guidelines: ● Schedule backups to avoid times of peak Web usage. ● Do not back up unnecessary data. ● Perform regular trial restore operations on a test network to verify that the correct backups are being made.

Choosing the Appropriate Type of Backup The three main types of backup are: ● Normal ● Incremental ● Differential

6

Backup and Restore for Internet Data Center

In addition, CommVault Galaxy software provides two backup types that assist in the backup process and save time within the critical backup window: ● Auxiliary Copy ● Synthetic Full

Normal Backup A normal (or full) backup copies all selected files and marks each file as having been backed up (in other words, the archive attribute is cleared). With normal backups, only the most recent copy of the backup file or tape is needed to restore all of the files. A normal backup is usually performed the first time a backup set is created.

Incremental Backup An incremental backup backs up only those files that have been created or changed since the last normal or incremental backup. It marks files as having been backed up (in other words, the archive attribute is cleared). If a combination of normal and incremental backups is used, the last normal backup set and all incremental backup sets are needed to restore all data.

Differential Backup A differential backup copies only those files that have been created or changed since the last normal or incremental backup. It does not mark files as having been backed up (in other words, the archive attribute is not cleared). If a combination of normal and differential backups is used, the files or tapes from both the last normal backup and the last differential backup are needed to restore all data.

Auxiliary Copy An auxiliary (or secondary) copy is a copy of backup data. The data copied is a true image of the primary backup copy and can be used as a hot standby backup copy in the event that primary backup servers, devices, and media are lost or destroyed. The primary and secondary copies use different media and often use different backup libraries.

Synthetic Full Backup A synthetic full backup combines the most recent full backup of the selected data with all subsequent incremental and/or differential backups, and stores the result in a single archive file. Synthetic full backups are used primarily to enhance the performance of restore operations, because a single backup will then be all that is needed for a successful restore.

Chapter 1: Backup and Restore Design

7

Advantages and Disadvantages of Each Type of Backup When deciding which type of backup to perform, you must consider the backup’s impact on network bandwidth and the time required to restore the data. Table 1.1 describes the advantages and disadvantages of each type of backup. Table 1.1: Comparison of backup types Backup Type

Advantages

Disadvantages

Normal (full)

Files are easier to find because they are on the current backup medium. Requires only one medium or set of media for file recovery.

Is time consuming. If files change infrequently, backups are nearly identical.

Incremental

Requires the least amount of data storage. Provides the fastest backups.

Complete system restoration may take longer than using normal or differential backup.

Differential

Recovery requires media from last normal and last differential backups only. Provides faster backup than normal.

Complete system restoration may take longer than using normal backup. If large amounts of data changes occur, backups may take longer than incremental type.

Auxiliary Copy

Makes exact copies of backup tapes for redundancy. Copies are quicker to generate than actual backups. Copies can be kept onsite for disaster recovery.

Synthetic Full

Consolidates normal and incremental backups into a new normal backup within a library that is stored off of the network and/or critical servers. Reduces backup and restoration time.

Choosing the Appropriate Storage Media to Use In addition to determining what type of backup to perform and when to perform it, you should evaluate the types of storage media available, and select appropriately. When choosing a storage medium, consider the following factors: ● The amount of data to be backed up ● The type of data to be backed up ● The backup window ● The environment ● The distance between the systems being backed up and the storage device ● Your organization’s budget ● The Service Level Agreements for data restorations

8

Backup and Restore for Internet Data Center

Table 1.2 summarizes the advantages and disadvantages of the common backup media types. Table 1.2: Comparison of backup media types Backup Media Type

Advantages

Disadvantages

Tape

Provides fast backup and long retention. Has high storage capacity. Is less expensive than magnetic and magnetooptical disks.

Wears out faster and is more susceptible to errors than magnetic disks and magneto-optical disks. Is difficult to configure and maintain, especially in SAN configuration. Requires periodic cleaning of drives.

Magnetic disk

Is easy to configure and maintain. Can be used for staging data.

Is the most expensive medium for initial storage.

Magneto-optical disk

Offers longest life span without degradation of the medium.

Is slowest for backup and restore. Limits choice of hardware.

Galaxy Software Modules and Core Functionality The Microsoft Internet Datacenter architecture uses CommVault Galaxy for Windows 2000 as its backup solution. The CommVault Galaxy framework of software modules includes the following components: ● One or more Intelligent DataAgents (iDataAgents), which back up and restore particular data ● One or more MediaAgents, which oversee the transfer of data between iDataAgents and backup media ● One CommServe StorageManager, which controls the iDataAgents and MediaAgents All of these software modules can exist on the same computer system, each can reside on a separate system, or they can be combined on various systems. Together, the iDataAgents, MediaAgents, and CommServe StorageManager make up a single CommCell, which is the primary building block of the Galaxy framework.

CommCell Galaxy software supports the creation of multiple, discrete CommCells. Each CommCell contains the appropriate number of iDataAgents and MediaAgents to meet the requirements of the system it is backing up (these requirements include the backup window, performance throughput, and amount of data within the

Chapter 1: Backup and Restore Design

9

CommCell). From a single logon screen, the user can select and manage any individual CommCell from any Web-based console in the enterprise. For more information on the CommCell and its deployment options, refer to “Galaxy Architecture and Deployment Strategy,” later in this chapter.

CommServe StorageManager A single CommServe StorageManager software module (a CommServe) directs combinations of MediaAgents and iDataAgents. The CommServe is the command and control center of the CommCell. The CommServe software handles all requests for activity between MediaAgents and iDataAgents, and monitors and administers all backups and restores. Only control information passes through the CommServe software module; not the backup or restore data itself. The CommServe includes the centralized event and job managers and the logical and physical management tree, and it also houses the meta database catalog. This database includes metadata about the nature and location of the data that is backed up. The centralized event manager logs all events, providing unified notification of important events. The job manager controls all the major activity of the software and provides Galaxy with its restart capabilities. Because the CommCell console is displayed through the use of a Web browser interface or Microsoft Management Console (MMC) snap-in, you can remotely manage the entire Galaxy system either internally from any VLAN in the Internet Data Center environment, or externally by using Web-based access through a virtual private network (VPN). The CommServe StorageManager may reside on its own dedicated system, or on a system that also contains a MediaAgent and/or iDataAgent.

MediaAgent The MediaAgent software module manages the movement of data between the physical backup storage devices and the corresponding iDataAgents. MediaAgents manage the backup storage devices, which are typically attached through a local bus adapter, such as a small computer system interface (SCSI). The MediaAgent software is designed to be storage-media independent; thus, it is capable of supporting a wide variety of storage models. This approach allows an organization to adapt rapidly to changes in storage technology. For example, MediaAgents communicate with the following types of storage devices: ● Tape libraries. The MediaAgent manages the multiple tape media and multiple tape drives in the library, and the movement of the robotic arm within it. The use of tape libraries saves time, limits the possibility of human errors, provides lights-out data protection, and allows for the consolidation of data through synthetic full backups.

10

Backup and Restore for Internet Data Center ●

●

●

Stand-alone tape drives. The MediaAgent manages the tape drive. You must load and unload media manually, so you should avoid using stand-alone tape drives if possible. Magnetic disk. Magnetic storage can consist of multiple disks or a redundant array of independent disks (RAID). This option has become more popular with increasing disk sizes, falling prices, and faster transfer rates. Storage costs for magnetic disk remain more expensive than for tape or magneto-optical disk, but in many Internet Data Center environments, the need for fast backups requires the use of magnetic disk for intermediate stage storage prior to backup to tape. Magneto-optical disk. Magneto-optical disks offer data throughput of 6 megabytes (MB) per second and decades of shelf life. Bar-coded magneto-optical libraries are gaining favor as a medium for hierarchical storage management, in which you create policies to move less-frequently used files off magnetic disks, which are more expensive.

iDataAgent The iDataAgent (Intelligent DataAgent) is the software module that manages the data transfer to the backup media through the MediaAgent, and is specific to the data type it manages. In the Internet Data Center environment, there are specific iDataAgents for the file systems for the Microsoft Windows 2000 Server operating system (for example, Web and application servers), the servers running Microsoft Exchange Server 2000, and Microsoft SQL Server™ 2000 databases. An iDataAgent is required for each managed data type per client system, whether the system is physical or virtual, such as on clustered systems or in SAN configurations where there are many virtual file systems or clients. Each iDataAgent can manage multiple instances per client of the appropriate data type, so a single Galaxy iDataAgent for Windows 2000 configured to manage the Windows NTFS file system can manage multiple file system instances on the same client computer.

Indexing The Galaxy software uses a two-part synchronized indexing scheme. This scheme consists of a centralized meta database catalog residing within the CommServe StorageManager software and an index that is located on the same computer as the MediaAgent software. To enhance browsing and recovery performance, each MediaAgent maintains an index of the backup data written to the backup media. A permanent copy of the index is stored on the backup media and an active copy of the index is maintained on the media storage disk where the MediaAgent is installed. This local index cache disk is finite. As new data is written to the backup media, new indexes are created. Configurable parameters allow administrators to set the size of the cache and lifespan of the local index. If the index exceeds the preconfigured capacity, older indexes are overwritten by using a least recently used (LRU) algorithm.

Chapter 1: Backup and Restore Design

11

DataPipe Galaxy DataPipe technology is designed to move data as fast as the source client can provide it and as fast as the backup media device can write it. The Galaxy software uses the same process for writing backups to direct-attached SCSI devices, SAN-attached devices, and remote network Transmission Control Protocol/Internet Protocol (TCP/IP) connections. The Galaxy DataPipe provides high-performance data movement with low overhead. Over TCP/IP networks, you can achieve data transfer rates close to the theoretical limit of the network, minus protocol overhead. The data transfer method works as well with disparate media types as it does with identical media types.

Dynamic Drive Sharing Galaxy can share tape devices (libraries and drives) in a switched SAN fabric configuration, with more than one MediaAgent sharing all or some drives of a tape library. The implementation of dynamic drive sharing (DDS) in Galaxy software allows for policy-based sharing to tape library drive resources among multiple backup systems. Galaxy software uses a software layer to manage the sharing of devices. This approach provides significantly greater reliability than does a simple SCSI reserve and release strategy, and makes data easier to manage. The advantages of DDS and library sharing include the following: ● Better backup performance ● Better return on hardware investment ● Reduced hardware spending ● Improved data protection ● Faster data access

Security CommVault Galaxy uses authentication mechanisms to ensure that communication between the Galaxy clients (iDataAgents) and Galaxy components (CommServe and MediaAgents) is performed only between recognized modules. The graphical user interface (GUI), an application of the CommServe, processes requests from userinitiated GUI sessions; it is also responsible for the challenge/response authentication of users and for processing the requests of those users. Therefore, because the CommServe is using authenticated connections, computers outside the Galaxy realm are prevented from connecting with Galaxy processes. The CommCell uses a network password as an internal security measure to ensure that Galaxy communications occur only between CommCell computers. By default, Galaxy assigns each computer in the CommCell a different password (which is not a user-level password). At any time, you can define a new CommCell network password for any computer in the CommCell.

12

Backup and Restore for Internet Data Center

Access to the resources and features of a CommCell is granted or denied based on a combination of the CommCell resources, capabilities, user groups, and accounts. The Galaxy administrator assigns user names and passwords. These Galaxy user accounts exist only in the context of Galaxy and are not Windows accounts. During installation, Galaxy creates a permanent user named cvadmin, which is the default CommCell administrator. This user name cannot be changed after the installation and has all available rights within a CommCell, including rights for creating user accounts.

Galaxy Architecture and Deployment Strategy The Internet Data Center environment is built on a multi-tiered architecture of physical VLANs and distributed Microsoft .NET–based application servers. The recommended Galaxy data storage management strategy includes procedures for backup and restore operations from the systems level through to applications and application configurations. This strategy protects data residing in each system, each virtual local area network (VLAN), and across the complete Internet Data Center environment. Galaxy uses all of the available technologies used in Internet Data Center, such as clustering, Storage Area Network (SAN) for speed, and security techniques such as IP Security (IPSec) for making the Internet Data Center environment highly available. In addition, Galaxy uses clustering to protect against failover of its components (such as CommServe and MediaAgents). The Galaxy solution is designed to protect against component, server, or application failure, and also to protect against an entire data center loss, as in a fire. Because all of the tiers in the Internet Data Center architecture communicate through the firewalls and the VLAN switched environment, a distributed backup and restore architecture is recommended. This recommendation is not based on a Galaxy software requirement or limitation; rather, it is to enhance the availability of the Internet Data Center environment.

Distributed MediaAgent Strategy Placing a MediaAgent in each VLAN accomplishes the following: ● Enables effective control of backup data transfer. ● Reduces the volume of data being transferred between VLANs. ● Improves security for servers and simplifies the firewall configuration. For example, the Infrastructure VLAN in the Internet Data Center architecture includes at least five servers running .NET-based applications, each of which contain several distributed components. Therefore, backing up each application

Chapter 1: Backup and Restore Design

13

server requires that you open ports at each server and at the firewall to provide the connection to the Data/Management VLAN for backup traffic. If a MediaAgent is placed in the Infrastructure VLAN, the MediaAgent can then back up the application servers locally and, at a time when there is less network traffic, use the Auxiliary Copy feature of the Galaxy software to copy the data to the tape media on the Data/Management VLAN. To use this method, the MediaAgent must have adequate disk space to store the backup data before transferring it to the tape media. Figure 1.1 illustrates the distributed Galaxy architecture for the Internet Data Center environment. ISP1

Internet routers

ISP2

Infrastructure VLAN Galaxy iDataAgents Web server farm Galaxy iDataAgents Perimeter firewalls

DMZ - VLANs 21, 22, 23 IS C OSS C T YE MS

ISC C OS YS TE MS

Cata y sl t IE S 0 Po eS w rp uly 85 0 SE 0R

Po wreS pp u yl 0

ow P rS e up ly 1

ow P eS rp uy 1 l

D S

D S

aCtal y st E IES 85 0S 0R

Infrastructure - VLAN 13

Swict h Proc es o r Switc h Proe cs o r

VLAN 15

Switches

Domain controllers Application servers

DMZ - VLAN 11 Web server farm Internal firewalls

Optional Infrastructure VLAN MediaAgent (magnetic)

Optional Web farm MediaAgent (magnetic)

Data / Management - VLAN 12 SQL Server cluster

Galaxy iDataAgents and MediaAgents for SQL Server 2000

Backup server Database servers Management servers VPN servers

Management VLAN Galaxy iDataAgents SQL data SAN layer

Figure 1.1 Distributed Galaxy Architecture

Tape library Clustered backup server BCK01 CommServe / MediaAgent

14

Backup and Restore for Internet Data Center

CommCell Deployment Strategy As stated previously, the combination of iDataAgents, MediaAgents, and the CommServe StorageManager together form a CommCell, which is the primary building block of the Galaxy framework. The control and data paths shown in Figure 1.2 assume a traditional LAN-based computing environment. When Galaxy software is deployed in a storage-networking environment (for example, when backing up Microsoft SQL Server 2000 on the Data VLAN), the control and data flows may be different.

CommServe StorageManager

Library Media Agent iDataAgent

iDataAgent Library

Backup and restore data

Main dataflow Monitoring/Control GalaxyCommCell

Figure 1.2 Galaxy CommCell

For extremely large systems, the Galaxy architecture allows you to place the iDataAgent and MediaAgent modules on the same computer to deliver highperformance direct-attached throughput (Figure 1.3).

Chapter 1: Backup and Restore Design

15

CommServe Storage media MediaAgent iDataAgent(s) Main dataflow Monitoring/Control

Figure 1.3 iDataAgent and MediaAgent on a large system

In environments where centralized management and centralized storage are essential, (for example, in environments that use centralized storage for a single department or in raised-floor data center environments that centralize all operations), the Galaxy solution easily conforms to the data protection strategy. Various iDataAgents across the network can pass monitoring and control information and data to a centrally managed MediaAgent and attached storage (Figure 1.4).

CommServe StorageManager Media Agent

Storage media

Main dataflow iDataAgent(s)

Monitoring/Control iDataAgent(s)

iDataAgent(s)

Figure 1.4 Centralized control in the Galaxy solution

You can also deploy Galaxy software with centralized control of distributed storage. Doing so eliminates the requirement that you move backup data across the LAN, and therefore significantly reduces backup and recovery time. Figure 1.5 illustrates centralized management control of both local and remote storage in a system running Galaxy software. Because only control information is passed between the MediaAgent and the CommServe StorageManager software, slow communication links can be used.

16

Backup and Restore for Internet Data Center Remote site iDataAgent(s)

CommServe MediaAgent

Storage media

MediaAgent MediaAgent iDataAgent(s)

iDataAgent(s)

Storage media Main dataflow Storage media

iDataAgent(s) Monitoring/Control

Figure 1.5 Management control over local and remote storage

Galaxy software supports storage area network (SAN) architectures (Figure 1.6). In the Internet Data Center environment, the cluster running SQL Server 2000 on the Data VLAN uses a SAN for data storage. The Galaxy tape library is also attached to the SAN. This means the MediaAgents can take advantage of SAN speed to transfer data to the tape library. In SAN environments, Galaxy software supports LAN-free backup as well as server-free and serverless backup and recovery of application data.

MediaAgent iDataAgent

CommServeStorage Manager

SAN fabric Main dataflow Monitoring/Control

Storage media Figure 1.6 Galaxy software in SAN environments

Storage media

Chapter 1: Backup and Restore Design

17

Recommendation: To use DDS to share all drives in the library, configure all drives in both the MediaAgents on the cluster running SQL Server and the MediaAgent on the CommServe. The MediaManager of the CommServe manages the resource allocation. Detailed information on configuring MediaAgents is provided in the CommVault Galaxy CommCell Media Management Administration Guide.

Deciding What to Back Up and Restore Virtually any system component can be backed up, and backup media is relatively inexpensive. It is therefore tempting to back up every component of the Internet Data Center architecture. However, a solution of this type requires a significant amount of time and bandwidth to perform the backup and to restore the system. It is important to look at all the parts of the implementation of the Internet Data Center architecture and determine what data must be restored if the disaster recovery plan is invoked. Doing so helps you to decide on an effective backup and restore strategy and to identify potential weaknesses in the application design. If the application architecture changes significantly, you should re-evaluate your backup strategy. Figure 1.7 on the next page can be used to decide which servers in the Internet Data Center architecture must be backed up. The discussion that follows provides backup recommendations for typical Internet Data Center environments.

18

Backup and Restore for Internet Data Center Determine type of backup for servers running Active Directory, servers running SQL Server, and management repositories

Do CLB servers contain persistent data?

No

Do IIS serers contain persistnet data?

No

Back up domain controllers, servers running SQL Server, and management repositories only

Yes Yes

Do IIS servers contain persistent data?

No

Yes

Back up domain controllers, servers running SQL Server, management repositories, IIS servers, and CLB servers

Back up domain controllers, servers running SQL Server, management repositories, and IIS servers

Back up domain controllers, servers running SQL Server, management repositories, and CLB servers

Figure 1.7 Backup design flowchart

Front-End Web Recovery In the Internet Data Center architecture, it is recommended that a recovery process for the front-end Web farm involve rebuilding the servers by using automated builds. One of the principle aims of the design for the front-end Web in the Internet Data Center architecture is that no persistent data should be stored on any of the Web servers. All of the Web-tier servers are clones that receive their content and settings from Microsoft Application Center 2000, which resides on the Infrastructure

Chapter 1: Backup and Restore Design

19

VLAN. As a result, the Web servers for most Web applications do not need to be backed up. This dramatically reduces the volume of data that needs to be backed up and simplifies the firewall configuration. In some cases, you may need to back up individual Web servers (for example, if you are not using Microsoft Application Center 2000, or if you are running an application such as a business-to-business (B2B) application where persistent data must be stored on the Web servers). You should avoid having to do so if possible. If required, however, you can use the CommVault Galaxy backup and restore solution through a firewall to back up and restore the Web servers in this tier. Recommendation: If Internet Data Center Web servers are to be backed up, you must install Galaxy iDataAgent for Windows 2000 on the servers. In addition, you may want to use a dedicated server on this VLAN to host a MediaAgent that writes to magnetic disk rather than to tape. This approach offers the following advantages: ●

Backup and restore traffic is localized in the VLAN.

●

The media is readily available (for example, tapes do not have to be loaded), and the backup and restoration of data to or from magnetic disk is fast.

●

Secondary copies can be (selectively) copied to the back-end tapes during periods of low network usage.

Infrastructure VLAN The Infrastructure VLAN contains the domain controllers for Windows 2000 and, if the application architecture requires it, the load-balancing servers running Component Services, the business-to-consumer (B2C) components running Microsoft Commerce Server, and the B2B components running Microsoft BizTalk™ Server (including Product Catalog System, Profiling System, and Business Process Pipelines). It also contains the controller and staging servers for Application Center 2000. If the application architecture relies on Active Directory to store customer account data, including user authentication and computer accounts, in the Active Directory database, the successful backup and restoration of Active Directory should be as high a priority as the restoration of the data from computers running SQL Server 2000 in the Data VLAN. Even if the Web application does not rely on Active Directory for data storage or user authentication, it is still vital that the Active Directory domain controllers be backed up on a regular basis. Active Directory can store security credentials, such as certificates, replication components, and system resources. Furthermore, other servers in the environment will have permissions and service accounts based on instances of accounts stored in Active Directory. If it is not possible to recover a current instance of Active Directory, considerable effort will be required to resynchronize computer accounts and reapply permissions.

20

Backup and Restore for Internet Data Center

If the Web application is using an array of load-balancing servers running Component Services that are managed by Application Center, consider backing up only the staging server. Because the Internet Data Center architecture provides automated installations of all servers, the servers running Component Services can be rebuilt as quickly as they can be restored from a backup, and rebuilding may be less problematic than restoring from backups. However, because the staging server contains the current master copy of the Component Services–based application and the configuration for Application Center, it should be backed up to reduce the time needed to restore the entire array. Recommendation: An iDataAgent needs to be installed on the servers. As with the front-end Web, you can use an optional dedicated server to host a MediaAgent that writes to magnetic disk rather than tape. The advantages of this approach are as follows: ●

Backup and restore traffic is localized in the VLAN.

●

The media is readily available (for example, tapes do not have to be loaded), and the backup and restoration of data to/from magnetic disk is fast.

●

Secondary copies can be (selectively) copied to the back-end tapes during periods of low network usage.

Data VLAN The database servers running SQL Server 2000 on the Data VLAN are most likely to need a strong backup solution. The database servers are likely to contain customer information, financial information, and crucial data for the functionality of the Internet Data Center Web application. If a strong backup and restore solution is not used, major organizational disruption could result. Therefore, all database servers containing live data must be backed up as frequently as possible. A clustered iDataAgent for SQL Server 2000 must be configured on servers running SQL Server 2000. Recommendation: Placing a MediaAgent and iDataAgents on the same physical hardware in the Data VLAN reduces backup time and enhances backup and restore performance. Because the SQL Server 2000 data layer is configured in a SAN environment, installing a MediaAgent on the same server as the iDataAgent takes advantage of the speed and robustness of the available SAN environment without incurring additional hardware costs.

Stand-By Disaster Recovery Option for the Data VLAN Because the Data VLAN is the most important layer of the Internet Data Center architecture from a data perspective, you should back up the databases frequently and restore them to exact replicated servers running SQL Server 2000 at a different location. To do so, you can use the SQL Server 2000 log-shipping utility in combination with the Galaxy solution. This strategy provides higher availability of the data

Chapter 1: Backup and Restore Design

21

layer. It also prevents problems such as data corruption and virus attack if the data is not protected by clustering and replication. This option is inexpensive and provides a strategy for availability in environments where there is some tolerance for downtime.

Management VLAN Monitoring and management repositories should also be backed up because they contain historical data about the system. For example, security events may be archived to the these repositories, and some organizations, such as financial service providers, may be legally required to retain this data for a set period of time.

Summary of Recommendations Table 1.2 summarizes the state of each VLAN in an Internet Data Center environment and the relevant backup and restore recommendations. Table 1.2: Backup and restore recommendations VLAN

State

Recommendation

Front-end Web VLAN in standard environments. Frontend interface layer (top tier).

Web server clones managed by Application Server 2000. No stored persistent data.

IIS Web Server farm: Rebuild servers by using automated builds (no backups required). Priority: Low – Backup/restore strategy is optional.

Front-end Web VLAN in particular B2B environments. Front-end interface layer (top tier).

Web server clones managed by Application Server 2000. B2B applications that require persistent data to be stored on Web servers.

You must back up persistent data. Priority: High – Use a strong backup and restore strategy.

Infrastructure VLAN. Business logic layer (middle tier).

Contains business logic. Can also contain user authentication and computer accounts stored in Active Directory. Components include the controller for Application 2000; staging servers; Active Directory/ Domain Name System (DNS) servers; Commerce Server 2000 (for B2C Web applications), BizTalk Server 2000 (for B2B Web applications); Exchange Server 2000 (for the mail component of BizTalk Server).

Application Center 2000: You must back up the controller configuration for Application Center 2000, content on staging servers, and COM+ data. Active Directory, DNS, and Exchange Server 2000: You must back up the B2C application and system state. BizTalk Server 2000 components: You must back up system state, all components, and the B2B application. Priority: High – Use a strong backup and restore strategy. (continued)

22

Backup and Restore for Internet Data Center

VLAN

State

Recommendation

Data VLAN Database layer (bottom tier).

Contains crucial data used by Commerce Server 2000, BizTalk Server 2000, and Web applications. Data is managed and stored by clustered SQL Server 2000 in a SAN environment.

SQL Server 2000: You must back up system state and all databases. Priority: High/Very High – Use a strong backup and restore strategy.

Management VLAN. Administration and systems management.

Monitoring and management servers and VPN servers.

Monitoring and Management repositories: You must back up historical system data. Priority: Medium – Use a medium backup and restore strategy.

Galaxy Solution Design and Configuration This section provides procedures for designing and configuring a Galaxy system for optimum performance. To design and implement a Galaxy system, you must determine the following: ● Storage required ● Storage devices required ● MediaAgents required Your first-pass design of a Galaxy system should provide you with preliminary hardware and storage requirements. You can then perform the same process again to refine the design for specific storage needs. “Galaxy Configuration” (later in this chapter) provides recommendations for enhancing this design. An example is included to illustrate the Galaxy System design process.

Hardware Considerations You can find details about the hardware solution used for the Internet Data Center architecture on the following site: http://www.microsoft.com/solutions/IDC/default.asp It is important that you determine what additional systems hardware you will need for on-site backup, equipment redundancy, and off-site storage. For many environments, it is good practice to maintain a test facility that has the same equipment as the production environment, but is in a different location. Note: For information about hardware requirements for Galaxy systems, see the Galaxy documentation or visit: http://www.commvault.com

Chapter 1: Backup and Restore Design

23

Storage Requirements Storage requirements are the total amount of storage space and storage media required to maintain the backup for a specified period of time. To calculate storage requirements for your system, you must determine the following: ● Number of clients ● Data retention period ● Storage required ● Storage media required You must first determine these requirements to estimate the amount of physical storage space your solution requires.

Determining Number of Clients Determine the number of client computers in the Galaxy system.

Determining the Data Retention Scheme The data retention period is the period of time for which a particular set of backup data is to remain available to restore. After the data retention period has elapsed and you have run the pruning utility, the media will be available for reuse. To determine your data retention scheme, use the following criteria: ● Number of full backup cycles maintained in storage (Cycles). A full backup cycle includes the full backups and all other backups until the next full backup. ● Number of incremental/differential backups in a full cycle (Incrementals).

Determining the Storage Required The storage required is the total amount of data that will be maintained on the storage media for the data retention period. Index is the space required on the MediaAgent to store the index data that defines the user objects saved in a given backup. This index is archived to storage media at the end of the backup. To determine your total storage needs, use the following criteria: Storage Required = Full Backups + Incremental Backups + Index Where: Full Backups = (Cycles * Total Used) Incremental Backups = (Cycles * Daily Change * Incrementals) Index = 4% (Full Backups + Incremental Backups) Total Used is the total amount of disk space used for all clients.

24

Backup and Restore for Internet Data Center

Cycles is the number of full backup cycles. Daily Change is the estimated daily rate of change of data. Incrementals is the number of incremental and/or differential backups in each full backup cycle. For example, assume that the backup cycle for your system is four weeks, and that you run six incremental backups each week. Also assume that the total amount of disk space used on all clients (Total Used) is 1 (terabyte) TB. and that the daily estimated change (Daily Change) is 10%, or 100 gigabytes (GB). The size of all the full backups is: (4 Cycles * 1 TB) = 4 TB

The size of all incremental backups is: (4 Cycles * 6 Incrementals* 100 GB Daily Change) = 2.4 TB

The size of the index is: 4% of 6.4 TB = 256 GB

The storage required is: 4 TB + 2.4 TB + 256 GB = 6.656 TB

Determining the Storage Media Requirement The storage media requirement is the amount of physical media (tape, magnetic disk, or magneto-optical disk) needed to hold your total storage requirements for the data retention period. To determine your storage media needs, use the following criteria: Storage Media = Storage Required / (Media * Compression Rate) Where: Storage Media is the amount of storage media needed. Storage Required is the total calculated in the previous example. Media is the uncompressed capacity of the media type used. Compression Rate is the compression ratio of the hardware. Continuing with the previous example, assuming that the tape you are using has a capacity of 60 GB uncompressed, and that hardware compression allows a 2:1 compression ratio, the number of tapes required is: 6.656 TB / (60 GB * 2) = 56 Tapes

Chapter 1: Backup and Restore Design

25

Determining the Storage Device Requirement The storage device requirement is the number of tape drives needed to perform a full backup on all clients simultaneously such that the backups are completed within a specific time period or backup window. To determine your storage device needs, use the following criteria: Drives Minimum = (Full / Backup Rate) / Backup Window Drives Maximum = (Clients * Streams * Backup Duration) / Backup Window Where: Drives is the number of tape drives needed. Full is the size of a single full backup for all clients. Backup Rate is the estimated backup rate in GB per hour. Backup Window is the backup window (available time for backups to be completed) in hours. Continuing with the previous example, assume that the full backup size for all clients is 1 TB, and that your drive has a backup rate of about 35 GB per hour, that the backup window is eight hours, that each client has 2 backup streams, and that the backup duration per client is two hours. The minimum number of tape drives needed is: (1 TB/35 GB per hour) / 8 Hours = 4 Drives

The maximum number of tape drives needed is: (30 Clients * 2 Streams * 2 Hours) / 8 Hours = 15 Drives

Determining the Number of MediaAgents A Galaxy MediaAgent manages the library and the transmission of data between clients and backup media. To determine MediaAgent needs for your system, use the following criteria: MediaAgents = Drives / Drives per Library Where: MediaAgents is the number of MediaAgents needed. Drives is the number of tape drives needed. Drives per Library is the number of drives in the library. Continuing with the previous example, assuming that a library contains 10 backup drives, the number of MediaAgents needed is: 15 Drives / 10 = Two MediaAgents

26

Backup and Restore for Internet Data Center

Best Practices for Configuring Galaxy Components Configuring Galaxy components and following best practices for optimal performance can enhance the Galaxy system you design. You can configure specific components or applications, or adjust your storage requirements according to the requirements of your particular Internet Data Center environment. The following configuration is provided to enhance and support the availability and performance of the Internet Data Center environment.

Configuring CommServe This section provides best practices and recommendations for implementing Galaxy CommServe in the Internet Data Center environment. CommServe Redundancy

The CommServe should be implemented in a Windows 2000 clustered environment. CommServe Sizing

A single CommServe can manage up to 35 clients. The number of clients in the environment can vary, depending on the design and hardware you use. For environments with more than 35 clients, you should deploy another CommServe. Hardware and Software for CommServe

To optimize the performance of a clustered CommServe, use a quad processor computer running the Windows 2000 Advanced Server operating system. The computer should meet the following minimum requirements: ● Pentium-compatible 700 megahertz (MHz) or higher Xeon processor ● 2 GB of RAM ● At least 8 GB of hard disk space, plus index cache storage

Configuring MediaAgents This section provides the best practices and recommendations for implementing Galaxy MediaAgents in the Internet Data Center environment. MediaAgent Sizing

To increase performance and reduce network traffic, place a MediaAgent on the same computer as any iDataAgent that will have large storage requirements. MediaAgent Redundancy

A MediaAgent can be implemented in a Windows 2000 clustered environment where fail-over capability is needed.

Chapter 1: Backup and Restore Design

27

Data Retention

Use a one-month, four-backup cycle for your data retention scheme. Perform a full backup once a week, and perform incremental backups daily. When scheduling full backups, use Start new media in Advanced Backup Options. Storage Policy

Use a separate storage policy for each iDataAgent. Include the client name and iDataAgent type in each storage policy name (for example, Server1_SQL) Increase the number of streams so that it equals the maximum number of drives configured. Compression Modes

Use hardware compression for each storage policy by setting the Hardware Compression attribute. Hardware and Software for MediaAgent

To optimize the performance of the server hosting the MediaAgent, use a quad processor computer that is running the Windows 2000 Server operating system. The computer should meet the following minimum requirements: ● Pentium-compatible 700 MHz or higher Xeon processor ● 2 GB of RAM ● At least 8 GB of hard disk space, plus index cache storage

Configuring Storage Media When using storage media in the Internet Data Center environment, follow these recommendations. ● Use magnetic media only when your total storage requirement on a client is less than 20 GB. ● When the primary copy of a backup is on magnetic media, you must create an auxiliary copy from which to make secondary copies to tape. ● Set short data retention periods for magnetic media (for example, two days for one full backup).

Configuring Off-site Storage When configuring off-site storage, follow these recommendations: 1. Assign each iDataAgent to one storage policy. If an iDataAgent has multiple subclients, assign them all to the same storage policy.

28

Backup and Restore for Internet Data Center

2. Name the storage policy using a simple naming scheme such as host

name_application type. For example, if a server running Exchange Server named avocado hosts two Galaxy iDataAgents named file system and Exchange database, the storage policies that the server points to would be named avocado_fs and avocado_exdb. 3. When scheduling full backups, use Start new media in Advanced Backup Options. Doing so marks as Full the previous active tape for the storage policy. By following these steps, you can take tapes off-site weekly. To identify which tapes you can take off-site, run the Backups on Media report for the appropriate storage policies in the CommCell, and specify that the report display only those tapes marked for the library as Full and In. If the data retention period has not elapsed for the data stored on the off-site tapes, you can bring the tapes back on-site and restore the data. If the data retention period has elapsed but the tapes have not been recycled, you can use the Galaxy Disaster Recovery tool to restore the data. Note: The Disaster Recovery tool currently supports the restoration of data from file system backups. Later this year, CommVault will add support for Exchange 2000 and other application types.

To keep selected backup media (such as full backups for the end of the month, quarter, and year), use the View media option in the Galaxy Backup History to identify those tapes so that you can be sure not to reuse them. To restore the backups from the tapes, use the Disaster Recovery tool. To prevent the off-site data from aging off, use the auxiliary copy feature of the Galaxy software. This requires a separate set of tapes that are used specifically for off-site storage. The auxiliary copy feature copies Galaxy archive files from the primary copy of a given storage policy to an auxiliary (secondary, tertiary, and so on) copy. This copying can occur between similar (for example, tape to tape) or dissimilar (for example, magnetic to tape) media. After running the auxiliary copy, you can take the tape belonging to the auxiliary copy off-site. Aging rules (retention times) for the auxiliary copy data can be greater than the retention times on the primary copy.

Configuring iDataAgents for SQL Server 2000 When stripping is supported, use multiple-stream storage policies.

Chapter 1: Backup and Restore Design

29

The Effect of Backup on a Client To run, backups require hardware resources (particularly CPU and RAM) on the client computer. The degree to which a backup operation affects a client depends on what hardware resource is available and whether other operations are running on the client computer concurrently. ● Make sure that the client computer meets at least the minimum requirements described in Chapter 2, “Backup and Restore Deployment.” ● Perform all nonessential tasks or other operations (for example, virus scans) outside the backup window. ● Run backups on a client during the evening, or at times when activity on the client is minimal. ● Run subclient backups sequentially. ● Set the operational window to prevent backups from occurring during the day, or during other active periods.

2 Backup and Restore Deployment Abstract This chapter describes how to deploy Backup and Restore Solution for Windows 2000-Based Data Centers, which uses CommVault Galaxy software. An overview of the deployment process is provided, together with detailed instructions for configuring the CommServe, MediaAgents and the various iDataAgents used in the Internet Data Center environment. Use of the CommCell Console is also described for basic iDataAgent administration.

Introduction This chapter describes the steps required to deploy the CommVault Galaxy backup and restore solution in an Internet data center environment. The three key types of components that you will install are the CommServe StorageManager (CommServe), one or more MediaAgents, and one or more platform-specific iDataAgents. For detailed information about the Galaxy architecture, see Chapter 1, “Backup and Restore Design.”

Installing Back-End Components You must install the following components on the data and management virtual local area networks (VLANs): ● Galaxy CommServe ● Galaxy MediaAgent ● Galaxy iDataAgent for Exchange 2000 Server (database and mailbox) ● Galaxy iDataAgent for SQL Server (you must also install this iDataAgent on the cluster)

32

Backup and Restore for Internet Data Center

Installing Middle-Tier and Web-Tier Components You must install Galaxy iDataAgent for the Microsoft Windows® 2000 operating system on the Infrastructure VLANs and the Web server farm. The number of instances of iDataAgent for Windows 2000 that you must install and configure depends on which servers are to be backed up. Some Internet data center configurations may also require you to install MediaAgents on the Infrastructure VLAN and the Web server farm. For the recommended backup strategy for the Infrastructure VLANs and the Web server farm, see Chapter 1, “Backup and Restore Design.”

Overview of Galaxy Software The Galaxy product suite provides a powerful set of storage management tools that help you manage critical enterprise and departmental information. These tools enable you to store and retrieve the data of one or more computer systems. The Galaxy system is composed of one or more CommCells. Each CommCell consists of the following installed and configured components: ● One CommServe StorageManager. The CommServe communicates with all client computers in the CommCell to initiate system backup and restore operations. Similarly, it communicates with MediaAgents when the media subsystem requires management. The CommServe is the heart of the Galaxy CommCell, connecting all components into one area network. ● One or more MediaAgents. The MediaAgent component of the Galaxy CommCell conducts data between the client computer and the backup media. Each MediaAgent communicates locally to one or more storage units by using a local bus adapter (for example, SCSI). The Galaxy system provides for a wide variety of storage units to which data can be backed up. ● One or more Intelligent DataAgents (iDataAgents). The iDataAgents are software modules responsible for backing up and restoring data on host computer systems (clients). A CommCell can support many clients. The Galaxy system provides a variety of iDataAgents, with each designed to handle a different kind of data (data for Windows 2000, Microsoft Exchange 2000 Server, and so on). If a given computer has two or more types of data, it requires two or more iDataAgents, one for each data type, to secure all the client data.

System Requirements The following are the system requirements, described in greater detail in the CommVault Galaxy Pre-Installation Checklist, for deploying the CommVault Galaxy software: ● Hardware requirements for CommServe, MediaAgent, and Galaxy client computers

Chapter 2: Backup and Restore Deployment ●

● ● ●

33

Operating system, networking, and other software requirements for CommServe, MediaAgent, and Galaxy client computers Hardware and software requirements for a remote administration console Network requirements Library and drive configuration instructions for direct-attached devices, Storage Area Network (SAN) devices, and Network Data Management Protocol (NDMP) network-attached storage (NAS) devices

For information about supported libraries and drives, check with your CommVault representative.

Deployment Sequence You must install the Galaxy components in the following sequence: 1. CommServe 2. MediaAgent 3. iDataAgents An iDataAgent for Exchange 2000 or Microsoft SQL Server™ 2000 can be installed only on a computer that already has iDataAgent for Windows 2000 installed. During the installation of the iDataAgents for Exchange2000 and SQL Server 2000, Galaxy checks the client computer for iDataAgent for Windows 2000. If it is not found, Galaxy installs it before continuing the installation of the iDataAgent for Exchange 2000 or SQL Server 2000. Note: Each installation of a file system iDataAgent requires a valid license.

Firewall Requirements Firewall support between CommServes, MediaAgents, and clients enhances security by restricting incoming and outgoing Transmission Control Protocol (TCP) ports to a predetermined range. A firewall offers many advantages, including added security, Internet Protocol (IP) translation, logging, and monitoring. Currently, all computers interacting with one another across a firewall must use the same range of ports. The range of ports is 100 for the first CommServe firewall— client backup, 50 ports for a separate MediaAgent, and 25 more for each additional simultaneous client backup outside of the firewall. Note: Each component (CommServe, MediaAgent, and client) must have the same number and range of ports allocated. The CommServe, MediaAgent, and clients within the firewall do not use firewall resources.

34

Backup and Restore for Internet Data Center

Use the following procedure to configure Galaxy communications on computers across a firewall.


To set-up firewall access 1. Verify that Galaxy version 3.1.0 (GSP1) or later is installed on the CommServe, MediaAgent, and firewall clients. 2. Ensure that ports 8400 through 8403 are enabled for the CommServe, MediaAgent, and appropriate clients. For added security, it is recommended that you configure the firewall in such a way as to accept connections only from Galaxy computers on the opposite side of the firewall. Note: Galaxy uses a secure proprietary protocol for those processes communicating on enabled ports.

3. Determine the range of TCP/IP ports to use through the firewall. The ranges of

ports are as follows: ● 100 for the first CommServe/firewall client backup ● 25 more for each additional simultaneous client backup outside the firewall ● 50 ports for each MediaAgent Note: Reserved ports must be numbered between 5000 and 65536.

4. Before creating the configuration files, stop all Galaxy services on your computer.

Then, proceed with the configuration. 5. Using Microsoft Notepad or a similar text editor, create a file named Firewall.svc

in the Galaxy home directory (where the Galaxy software has been installed) and type the range of ports you want to use. The following example shows what you would type for a port range of 8600–8699: 8600 START_PORT (this must be the first line of the file) 8699 END_PORT

Do not list ports 8400, 8401, 8402, or 8403. These ports are used for the CommServe, MediaAgent, and appropriate clients. 6. To reserve a port (other than for a firewall) in the range that you have specified (for example, port 8650), edit Firewall.svc and specify the port number, followed by :-1:-1:-1. For example: 8600 START_PORT 8699 END_PORT 8650:-1:-1:-1

Chapter 2: Backup and Restore Deployment

35

While backups are running, do not examine the Firewall.svc file; instead, look at the backup copy named Firewall_bak.txt. 7. Create a text file named Firewall_loc.txt in the same directory as the Firewall.svc file. Firewall_loc.txt should include the domain names of the computers that are on the other side of the firewall (use one line per computer name and make sure that there are no trailing spaces). For example, suppose that the CommServe (bck01.nwtraders.com) and MediaAgent (sql01.nwtraders.com) are on one side of the firewall, and that clients named iis01.nwtraders.com, iis02.nwtraders.com, and ad01.nwtraders.com are on the other side of the wall. On the CommServe host, the Firewall_loc.txt file looks like the following: iis01.nwtraders.com iis02.nwtraders.com ad01.nwtraders.com

On each of the firewall clients, the Firewall_loc.txt file looks like the following: bck01.nwtraders.com sql01.nwtraders.com

8. Restart all Galaxy services after creating the configuration changes. 9. At startup, the host names in the Firewall_loc.txt file are read and are converted

to IP addresses by gethostbyname, and the addresses are written to the Firewall_exp.txt file. These addresses are compared to the host addresses at the far end of the socket you are using. If an address matches one of the addresses in the Firewall_exp.txt file, a firewall port is used. Otherwise, a random port is generated. 10. If several messages in the log file indicate that Galaxy communications are in a sleep/wait mode (that is, waiting for ports to become available), there are not enough ports allocated for use with the firewall. If the log file contains a message indicating that no firewall ports are available, you must designate more ports.

CommServe The CommServe communicates with all client computers in the CommCell to initiate system backup and restore operations. It also communicates with MediaAgents when the media subsystem requires management. The CommServe is the heart of the Galaxy CommCell, connecting all components into one area network. When installing a CommCell, always install the CommServe software first.

36

Backup and Restore for Internet Data Center

Before You Begin To avoid common installation problems, do the following: ● Review the product release notes to learn about changes and enhancements to the product. ● Obtain the Galaxy software CD-ROM for Windows 2000. ● Obtain a valid license. Provided on a valid Galaxy license disk. Note: You cannot install Galaxy software without a valid license.. ●

●

●

●

●

Ensure that the CommServe meets the following minimum system requirements, which are described in greater detail in the Galaxy Pre-Installation Checklist: Install the software on a noncompressed drive. You must not install the CommServe on a compressed drive. To avoid compatibility and performance issues, do not install the CommServe software on the following: ● A computer running Microsoft Exchange Server ● A computer that has a pre-existing installation of SQL Server version 6.5 or 7.0 that is serving other applications. Dedicate SQL Server to Galaxy. The SQL Server–based application that is installed on the CommServe must be dedicated to support the Galaxy software and cannot be shared by any other applications. Test all network interfaces. If your CommServe computer has multiple network interface cards (NICs) and IP addresses, ensure that all network communication paths are working.

If your CommServe computer has at least two physical disk drives, you can enhance CommServe performance by installing the CommServe database on a different physical drive from the Microsoft SQL Server 7.0 application and SQL Server 7.0 database.

Installing the CommServe Software The following procedure describes how to install the CommServe software.


To install the CommServe software 1. On the computer that will serve as the CommServe, log on as Administrator or as a member of the Administrators group on that computer. The Galaxy software can be installed only by a user who is a member of the local Administrators group. 2. Place the Galaxy software CD-ROM into the CommServe CD-ROM drive. After a few seconds, the installation menu displays.

Chapter 2: Backup and Restore Deployment

37

Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. Note that the installation will become corrupted unless the drive is actually mapped.

If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, click SetupGalaxy.exe, and then click OK. 3. On the installation menu, select CommServe, and then click Install. 4. The Setup program determines whether you are in a clustering environment. If

you are, see Installing a CommServe and MediaAgent in a Clustered Environment. If you are not, Setup continues automatically. 5. Setup checks your Windows user account for the necessary user rights. These rights include the ability to log on as a service, to act as part of an operating system, and to replace a process level token. If your account already has the necessary rights, you will not receive this prompt, and you can proceed to the next step. 6. The installation program changes the rights of the group administrator. Press CTRL+ALT+DEL to log off and then log on again. Provide the administrator user name and password again. 7. Setup checks to see if Microsoft SQL Server 7.0 is installed on your computer. If it is, Setup informs you that the existing SQL Server installation may not be compatible with Galaxy. You can use the existing SQL Server installation (not recommended), or you can exit Setup, remove SQL Server, and then restart the CommServe installation. If you use the existing installation, SQL Server must be configured to run using the local system account. If Microsoft SQL Server 7.0 is not installed, Setup informs you that it needs to be installed on the CommServe computer. Galaxy Setup has an embedded SQL Server 7.0 installation. Note: Microsoft SQL Server 7.0 is needed for the operation of the CommServe software.

8. Click Yes to install Microsoft SQL Server 7.0. 9. Select one of the following Microsoft SQL Server 7.0 installation directories: ●

●

Installation path. This is the location where you want to install Microsoft SQL Server 7.0. Database path. This is the location where you want to set up the Microsoft SQL Server 7.0 database. (This database is used for SQL Server 7.0 bookkeeping; it’s not used for Galaxy.)

If different directories are required, browse and change directories as appropriate. Then click OK.

38

Backup and Restore for Internet Data Center

10. When prompted, insert the Galaxy SQL Server Database CD-ROM, and then

11. 12.

13. 14. 15.

click OK. Setup copies Microsoft SQL Server to the computer. This step may take several minutes to complete. A password policy settings error is displayed. Click OK to continue. When prompted, insert the Galaxy software CD-ROM, and then click OK. At the next prompt, click OK to restart your computer. After the computer restarts, the CommServe installation procedure automatically continues. On the Welcome screen, click Next to proceed. Read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. Choose the location of the Galaxy Destination Folder. If you install other Galaxy software (a MediaAgent, for example) on this computer, this installation directory will also be used for that software. Either accept the default by clicking Next, or click Browse to name a different location on a local disk drive. (Do not install the software to a mapped network drive.) Record the folder here: Galaxy Destination Folder: _________________

16. Choose the type of SQL metadata database installation you want to perform.

(The CommServe database holds the metadata created by Galaxy. It is used for internal record keeping.) Click Typical or Custom. Custom options are displayed at the end of the install procedure. 17. Choose the location to which the CommServe database will be installed. Either accept the default by clicking Next, or click Browse to name a different location on a local disk drive. (Do not specify a mapped network drive.) The disk on which the database will be stored should have at least 1 gigabyte (GB) of free space. Record the destination here: Galaxy Database Destination: _______________ 18. Click Next to continue. 19. If this is a new software installation or an upgrade to a major release, you are

prompted for the location of the Galaxy installation license file. Insert the disk that contains the license file into the computer’s floppy disk drive and click Browse to locate the license file, filename.txt; license file names are a randomly generated number that usually includes a descriptive name, for example CVL_000004DB_Microsoft_IDCLab2.txt Do not remove the disk until the installation is complete. Click OK.

Chapter 2: Backup and Restore Deployment

39

Note: If this is a pilot or trial license, it expires in a predetermined time interval, which is usually 30 days. If you plan to use Galaxy on a permanent basis, please obtain a permanent license, which you apply at a later time. For more information, see the license instruction sheet that accompanies the Galaxy software.

20. Select the CommServe host name. This is the TCP/IP network name of the

CommServe computer. If your CommServe has more than one NIC, choose the NIC (the host name) that can communicate with all computers in the CommCell. If necessary, you can obtain the host name(s) by clicking Network and Dial-Up Connections in Control Panel. Record the name here: CommServe Host Name: ___________________ (case sensitive) Click Next. 21. ExpressRecovery backups secure the CommServe’s internal database. In the Galaxy CommServe ExpressRecovery (ER) Path window, specify the appropriate information in the following fields: ● CommServe ER destination path. Type the destination path to which the CommServe ExpressRecover backups are sent. This path must be a valid network path specified by a Universal Naming Convention (UNC) prefix. ● Network share user name. Type the domain/user name of the user who has administrative rights to the ER destination path. ● Network share password. Type the password of the network share user name. ● Re-enter password. Re-type the password for verification purposes. Note: To better secure your Galaxy metadata, CommServe ExpressRecovery backups should be directed to a drive on a remote Galaxy client, not a drive that is local to the CommServe. After the CommServe is installed, be sure to schedule daily ExpressRecovery backups.

22. Assign an account name and password for the SQL Server CommServe Data-

base Administrative account. Galaxy uses this SQL Server account internally to access the CommServe database. Account Name: ___________________________ Password: _______________________________

Do not confuse this account with the account used to log in to the Galaxy console. The two administrative accounts, SQL Server and Galaxy accounts, are separate even if both accounts are named cvadmin by default. The installation creates a Galaxy login account with the user name and password of cvadmin without prompting the user. The password to the Galaxy login account, cvadmin, can be changed later through the account properties of the user in the CommCell Users of the Galaxy console.

40

Backup and Restore for Internet Data Center

23. Click Next and confirm your password. Then click OK again. 24. Click Next following a summary of the installation options that you have chosen. 25. Setup checks the Microsoft Internet Explorer installation. (This software is a

requirement of the CommServe software.) If a version of Internet Explorer that meets the minimum requirements is not installed, Setup informs you of this. If you are planning on using the Microsoft Management Console (MMC) Snap-in version of the CommCell Console, Internet Explorer 5, or later, must be installed. 26. Setup checks the Java Runtime Environment (JRE) installation. If it is not installed, Galaxy displays the following: Setup cannot find Java Runtime Environment version 1.3 installed. The Galaxy CommCell Console requires this version to operate properly. Click Yes to have Setup install the JRE now, otherwise click No to skip the installation of this component and continue with the installation. Setup now starts copying the CommServe software to the computer. This step may take several minutes to complete.

Click Yes to install the JRE Environment or No to continue the installation. A dialog box prompting you for the destination location is displayed. Specify the destination location, and then click Next. 27. Setup prompts you to assign a password to the SQL Server system administrator login. This is the administrator’s account created by SQL Server during the installation. Assign and confirm the password. (If you used an existing installation of SQL Server 7.0 for the Galaxy installation, you are prompted to provide the password for the existing system administrator account.) Then click OK. 28. If you selected the Typical option in Step 16, the installation process skips to Step 31. If you selected the Custom option in Step 16, the installation continues with the following steps. The Custom option allows you to configure Galaxy script and log file locations, as well as the location, size, and growth rate of Galaxy database files. If you selected to install custom database options: ● Setup displays the CommServe Database Configuration window. Select custom locations for the data files and log file, and then click OK. ● Click Yes to confirm that the CommServe database options are defined. ● In the CommServe Database File Groups Configuration window, enter initial maximum file sizes and the file growth values you want. Then click Next. ● Click Yes to confirm that the CommServe database file group configurations are defined. 29. Ensure that selected CommServe database options are disabled to optimize

database performance. To do this: a. To select the CommServe database, select Database, and then select CommServe. b. Right-click the CommServe name, and then click Properties.

Chapter 2: Backup and Restore Deployment

41

c. Select the Option pane. d. Ensure that only the Select Into Bulk Copy and Truncate Log on Checkpoint check boxes are selected. 30. Set the database memory to 128 MB, or larger, if you have more memory avail-

able to your CommServe. To set the maximum memory for the SQL Server, complete the following steps within the SQL Server Enterprise Manager: a. In the left pane display, select Microsoft SQL Servers, select SQL Server Group, and then select Instance_Name (where Instance_Name is the name of the instance). b. Right-click the instance, and then click Properties. c. Click the Memory tab. d. Select Dynamically Configure SQL Memory, and set the maximum memory to half of the database memory available to the CommServe. Set the minimum memory to 0. 31. If Microsoft Internet Information Services (IIS) is installed, Setup prompts you to

indicate if you want to configure Galaxy for Web-based administration. Doing so allows you to access the CommCell Console (the Galaxy graphical user interface, for example) and view CommCell reports by using a Web browser. (If IIS is not installed, you do not receive this prompt, and you can proceed to the next step by clicking OK.) Click Yes. a. When prompted for an alias, type the name of the Web alias that you want to use for accessing the CommCell Console remotely (or use the default alias name Galaxy). Click OK. b. If prompted, click Yes to overwrite the alias. c. The program reports the Uniform Resource Locator (URL) that you can use to access the CommCell Console by using a Web browser. For future use, record this URL here: Galaxy Web URL: _________________________

Click OK to continue. 32. If you chose not to install the JRE, you will receive the following message: Could not locate the JRE home directory on this machine. The Galaxy CommCell Console for Java will not be installed. Click OK to continue the installation.

Click OK to continue. Galaxy attempts to add your computer to CommCell Plus. If this operation fails, and your computer is a member server in a Microsoft Windows 2000 Active Directory directory service domain, you can run the following command: regEvMgrsWithAD-c CommServe_fully_qualified_name

42

Backup and Restore for Internet Data Center

CommServe_fully_qualified_name is the fully qualified domain name (FQDN) of your CommServe. Click OK to continue. 33. Remove the license disk, and then when prompted, click OK to restart the CommServe computer. 34. Set up an ExpressRecovery account so that the CommServe database can be backed up. For instructions, see the topic “Setting up an Express Recovery Account” in the “Getting Started with iDataAgent Administration” section later in this chapter.

Installing the CommServe on a Cluster This section describes how to install a CommServe in a clustered environment. Note that, during active node installation, Setup automatically installs the CommServe on a passive node. It is suggested that you install a clustered CommServe to its own disk group, or at least to a disk group that does not contain applications that require backing up by iDataAgents. This is suggested for two reasons: ● Maintaining all data and backups in one disk group may affect the data protection strategy. ● If iDataAgents are installed to the same disk group as the CommServe, timing issues may arise in regard to stopping and starting the Galaxy clustered resources during iDataAgent installation.

Before You Begin To help avoid common installation problems you need to: ● Verify node availability. Both active and passive nodes must be available. ● Pre-install SQL Server. SQL Server 7.0 service pack 1 must be installed and clustered prior to installing the CommServe. ● Cluster service should bind the public network adapter before the private network adapter. ● Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. ● Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running.


To install a CommServe on a cluster 1. Log on to the computer that will serve as the CommServe as the Domain User with privileges to all nodes in the cluster.

Chapter 2: Backup and Restore Deployment

43

2. Place the Galaxy software CD-ROM for Windows 2000 into the CommServe

CD-ROM drive. After a few seconds, the installation menu displays. 3. If the installation menu does not display: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. Note: You can also install the product by using a mapped CD-ROM on another computer on the network. However, the installation will become corrupted unless the drive is actually mapped.

4. On the installation menu, select CommServe, and then click Install.

The Setup program determines that you are in a clustering environment. 5. A list of disk groups that are configured on the cluster that contain virtual

6. 7. 8.

9.

10. 11.

servers is displayed. Select the disk group that contains the virtual server in which you want to install the CommServe software and the clustered installation of SQL Server 7.0. Whenever an install within a clustering environment requires a reboot, ensure that the disk group has failed over to its original owning node (that is, the disk group is owned by its preferred node) and that all resources are online before continuing. In case of a failover in a clustering environment, the CommServe resumes all running jobs except for online backups, such as those for the SQL Server database and the Exchange database. Online databases report a failed state. A dialog box may display with a message indicating an incompatibility regarding the SQL Server. Ignore this message, and go to the next step. Perform Steps 6 through 32 of the previous procedure, “Installing the CommServe Software.” In the Start Copying Files dialog box, a list of all nodes to which the virtual server can fail over is available. Each of these nodes is to be updated with the active node settings. Click Next to continue. After Galaxy updates the passive nodes on the cluster so that the virtual server can fail over, reboot all of the updated passive nodes. A program to create the CommServe Data Source Name (DSN) is launched automatically on each passive node after the reboot. Click OK. If you are informed at the end of the active node installation that the passive node was not available, select one of the following choices, otherwise, continue on to the next step:

44

Backup and Restore for Internet Data Center ●

●

Click Yes to continue with the active installation and update any remaining passive nodes. Click No to continue with the active installation and skip updating any remaining passive nodes. Click Yes to update any remaining nodes, and then, when prompted, click OK to restart the CommServe computer when prompted.

12. Set up an ExpressRecovery account so that the CommServe database can be

backed up. For instructions, see “Setting up an Express Recovery Account in the Getting Started with iDataAgent Administration” section later in this chapter.

Performing a Manual Passive Node Installation This procedure must be used if a passive node failed to update during the installation of the active node. Note: In a clustering environment, the CommServe automatically installs a graphical user interface (GUI) for the active node or passive node, as appropriate. The GUI installation for the active node points to the Galaxy/GUI Galaxy installation directory on the shared drive. This GUI is accessible only when the node is the owner of the shared drive.


To perform a manual passive node installation 1. Repeat Steps 1 through 5 of the previous installation procedure. 2. A message displays that Setup has determined that this is a passive node and will update the environment on that node. Click OK. 3. Provide the following values (if you do not know this information, check the active node’s registry where Galaxy was already installed). You can verify the information that must be provided by using the Base or CommServe registry keys of the active node under HKEY_LOCAL_MACHINE\Software\CommVault Systems\CommVault\Galaxy\Virtual_Server_Name): a. Galaxy install folder on shared disk. The Galaxy installation path you used during active installation for the virtual computer. Base key: dGALAXYHOME

b. CommServe database account name. The name of the SQL Server CommServe database administrative account. (Cvadmin, for example.) c. CommServe database account password. The password needed to access the SQL Server CommServe database administrative account. (Cvadmin, for example.) d. CommServe Computer Name. The local (NetBIOS) CommServe short name for the CommServe. CommServe key: sCSCLIENTNAME

Chapter 2: Backup and Restore Deployment

45

e. CommServe Host Name. The TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the CommServe). CommServe key: sCSHOSTNAME 4. The registry and files are updated on the passive node. When the update is

completed, the system displays the Setup Complete window. To close this window, click Finish. 5. Click OK to restart the CommServe computer when prompted. 6. Set up an ExpressRecovery account so that the CommServe database can be backed up. For instructions, see the topic “Setting up an Express Recovery Account” in the “Getting Started with iDataAgent Administration” section later in this document.

Installing a MediaAgent The primary task of the MediaAgent is to oversee the transfer of data between client programs and backup media. Each MediaAgent communicates locally to one or more storage units by using a local bus adaptor (SCSI, for example). The MediaAgent installation consists of two key phases, described later in this section: ● Installing the MediaAgent software ● Configuring libraries and drives

Before You Begin To help avoid common installation problems you need to: ● Review product changes and enhancements. These are provided in the product release notes. ● Obtain the appropriate software. For example, the Galaxy software CD-ROM that is appropriate to the destination computer’s operating system. ● Obtain valid MediaAgent licenses. The CommServe that will communicate with this MediaAgent must have a license available for a MediaAgent of this operating system type. ● Obtain a valid library license. You must have a library control license for your library (if you are using one). ● Meet the minimum requirements. The MediaAgent computer must satisfy the minimum requirements provided in the Galaxy Pre-Installation Checklist. ● Install to a noncompressed drive. Make sure that the MediaAgent is not installed on a compressed drive.

46

Backup and Restore for Internet Data Center ●

●

●

●

●

●

Check media connectivity. The MediaAgent computer must be correctly connected to a removable-media or magnetic library, if direct media connections are being used. Check media. Any removable-media library being used must contain at least one media cartridge labeled with a bar code, preferably more. Check for drivers. The storage device and SCSI adapter drivers must be installed and loaded on the MediaAgent computer. Verify CommServe is running. The CommServe computer and library must be turned on, and the CommServe software running. Test all network interfaces. For a MediaAgent with multiple NICs and IP addresses, ensure that all intended network communication paths are working. Ensure all media are supported. Your library and drive must be on the CommVault list of supported media.

Note: If you are sharing a library between two or more MediaAgents, it is recommended that you install the MediaAgent software on the MediaAgent that controls the medium changer before installing on the MediaAgents that are attached only to drives. In the procedures that follow, it is assumed that you have followed this convention.

For more information, see the Galaxy Quick Start and CommCell Media Management Guides.


To install a MediaAgent 1. Log on to the MediaAgent computer as Administrator or as a member of the Administrators group on that computer. The Galaxy software can be installed only by a user who is a member of the local Administrators group. 2. Place the Galaxy software CD-ROM into the MediaAgent’s CD-ROM drive. After a few seconds, the installation menu displays. If the installation menu does not display: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. Note: You can also install the product by using a mapped CD-ROM on another computer on the network. However, the installation will become corrupted unless the drive is actually mapped.

3. On the installation menu, select MediaAgent, and then click Install. 4. The Setup program determines whether you are in a clustering environment.

If you are, see the next section, “Installing a MediaAgent on a Cluster.”

Chapter 2: Backup and Restore Deployment

47

5. Setup checks your Windows user account for the necessary user rights. Log on,

and then log off again to reset administrative rights. 6. Close any running applications. If necessary, exit Setup and close your running applications. 7. Read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. If Galaxy software is already installed on this computer, you will not receive this prompt. Continue to the next step. 8. Choose the location of the Galaxy installation directory. Either accept the default or click Browse to name a different location on a local disk drive. (Do not install the software to a mapped network drive.) Click Next to continue. If the Galaxy software is already installed on this computer, you do not receive this prompt. Note: If you intend to install other Galaxy software (iDataAgents, for example) on this computer, the selected installation directory is automatically used for that software as well.

9. Enter the following: ●

●

CommServe computer name (short name). This is the local (NetBIOS) name of the CommServe computer. CommServe host name (FQDN). The TCP/IP network name of the CommServe computer (computer.company.com, for example).

Note: You recorded the CommServe host name during CommServe installation.

Click Next to continue. 10. You are prompted to configure the MediaAgent’s communications paths. Select or enter: a. The MediaAgent name of the MediaAgent computer. b. The interface name that the CommServe uses to contact the MediaAgent. c. The default interface name that backups/restores use to communicate with the MediaAgent. Note: The GUI displays a list of available host names for selection. If the host name is not complete or correct, check the network connection’s working status. If necessary, enter the correct host name.

Click Next to continue. 11. Select the location of the MediaAgent index cache. Accept the default or choose another location. In either case, the location must be local and large enough to hold a reasonable amount of cache data. Click Next to continue.

48

Backup and Restore for Internet Data Center

Note: It is recommended that the index cache be configured to be written on a partitioned drive used exclusively for holding an index cache. The area of it should be large enough to hold about 4 percent of the size of the data that you plan to back up and maintain through this MediaAgent. Additional information on MediaAgent configuration and the index cache can be found in the Advanced Operations Guide or the CommVault Galaxy CommCell Media Management Administration Guide.

12. After the next window displays a summary of the installation settings that you

have chosen, click Next to continue. 13. Setup now starts copying the MediaAgent software to the computer. This may take several minutes to complete. 14. When prompted, restart the MediaAgent computer.

Installing a MediaAgent on a Cluster This section describes how to install a MediaAgent in a clustered environment. MediaAgent clustering is supported only in a SAN environment; multiple MediaAgents on a single cluster server is not supported. Note: Make sure that the host bus adapter (HBA) cards of a MediaAgent cluster are installed on the same port number in all of the nodes (this allows the SCSI address for the library within the SAN environment to remain the same for all nodes). It is recommended that these HBA cards be identical in all corresponding nodes.

Before You Begin To help avoid common installation problems you need to: ● Ensure that all nodes are running. Make sure that both the active and passive nodes are on. ● Use a Storage Area Network. A clustered MediaAgent is supported only in a SAN environment. ● Cluster service should bind the public network adapter before the private network adapter. ● Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. ● Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running.


To install a MediaAgent on a cluster 1. Log on to the MediaAgent computer as Domain User with privileges to all nodes in the cluster.

Chapter 2: Backup and Restore Deployment

49

2. Place the Galaxy software CD-ROM that is appropriate to the MediaAgent

computer’s operating system into the MediaAgent’s CD-ROM drive. After a few seconds, the installation menu displays. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. Note that the installation becomes corrupted unless the drive is actually mapped.

3. On the installation menu, select MediaAgent, and then click Install.

The Setup program determines that you are in a clustering environment. 4. Setup checks your Windows user account for the necessary user rights. 5. A list of disk groups that are configured on the cluster that contain virtual

servers is displayed. Select the disk group that contains the virtual server in which you want to install the MediaAgent software and the clustered installation of SQL Server 7.0. The next window prompts you to choose a location of the Galaxy Installation Directory. Select the drive:\path on which to install the clustered MediaAgent program files and data (H:\Galaxy, for example). Type the full path, including drive letter, for the Galaxy installation in the folder window. Note: It is not recommended to select the same drive for the clustered MediaAgent as where the Microsoft Cluster service resides.

6. Select the location for the MediaAgent index cache. You can accept the default or 7. 8.

9. 10.

11. 12.

click Browse to select another path. Verify the current settings and click Next. Setup begins to copy the program files and creates Galaxy cluster resources. A list of all nodes to which the virtual server can fail over is available in the Start Copying Files window. Each of these nodes is to be updated with the active node settings. Click Next to continue. After Galaxy updates the passive nodes on the cluster so that the virtual server can fail over, reboot all updated passive nodes, and then click OK. If you are informed at the end of the active node installation that the passive node was not available, proceed to the next procedure to perform a manual passive node installation. If you do not receive this message, go to the next step. Click Yes to update all remaining nodes. Reboot your computer.

50

Backup and Restore for Internet Data Center

Performing a Manual Passive Node Installation The following procedure must be used if a passive node failed to update during the installation of the active node. Note: In a clustering environment, the CommServe automatically installs a GUI for the active node or passive node, as appropriate. The GUI installation for the active node points to the Galaxy/GUI Galaxy installation directory on the shared drive. This GUI is accessible only when the node is the owner of the shared drive.


To perform a manual passive node installation 1. Repeat Steps 1 through 5 of the previous installation procedure. 2. Select the disk group that you selected when you installed the MediaAgent on the active node. 3. Setup determines that you are installing on a passive node. Click Yes to update the Galaxy environment on that node. 4. Provide the following passive node information. If you do not know this information, check the active node registry. The path in the registry editor is HKEY_LOCAL_MACHINE/SOFTWARE/CommVault Systems/Galaxy/Platform Information/virtual_computer, where virtual_computer is the name of your virtual computer. ● MediaAgent name. The local (NetBIOS) MediaAgent name (short name of the MediaAgent). ● Interface name. The TCP/IP host name of the NIC that the virtual MediaAgent name uses to communicate with the CommServe. (The FQDN on the virtual server.) ● Default interface name. The TCP/IP host name of the NIC that the virtual MediaAgent name uses as the default interface for transferring all backups and restores on the client computer. 5. Restart your computer. 6. Setup informs you to run the Media Library and drive configuration tool. Make

sure that the virtual server is owned by this node before running the tool. 7. Confirm that the disk groups and Galaxy resources are online and can fail over

successfully to the passive node. Then, fail back the disk group to the original owning node. To confirm failover capability, move the disk group to the passive node, and then move the disk group back to the original active node. Note: Please refer to the CommCell MediaAgent Administration Guide before configuring a MediaAgent on a cluster.

Chapter 2: Backup and Restore Deployment

51

Drive and Library Configuration You can run the Galaxy Library and Drive Configuration utility on the CommServe, or on any Windows MediaAgent within the CommCell. It is used for the following operations on tape libraries, stand-alone tape libraries or optical libraries, and media drives: ● Detect devices. This feature is used to display all devices that are controlled by MediaAgents. ● Configure libraries, master drive pools, drive pools, and drives. Library configuration enables MediaAgents to send data to and receive data from the library. Master drive pool and drive pool configuration creates the necessary entries for these entities in the Galaxy database. Drive configuration enables a MediaAgent to read and write data through the media drive. ● Share libraries among MediaAgents. To share a library among MediaAgents, either directly or by using a SAN, you must properly configure and map the resident drives. The Library and Drive Configuration utility is also used if you want to modify the configuration of a shared library. ● Discover media. To use the media within a library, the Galaxy system must collect information about the media through the discovery process. ● Change the SCSI mapping of storage devices. If the SCSI configuration of devices within the CommCell does not match the recommended configuration, Galaxy may not associate devices with their correct SCSI addresses. You can modify the SCSI-to-device mapping through the Library and Drive Configuration utility. ● Validate the SCSI mapping of devices within the CommCell. The Validate feature verifies that Galaxy has access to each physical device through the device’s mapped SCSI address. For more detailed information on configuration, see the Galaxy CommCell Media Management Administration Guide.

Disabling Removable Storage Control If you do not want your libraries and drives to be under the control of the Removable Storage service, you must disable Removable Storage control.


To disable Removable Storage on a computer running Windows 2000 and MediaAgent 1. On the Windows taskbar, click the Start button, point to Programs, point to Administrative Tools, and then click Computer Management. 2. In the left pane of the Computer Management window, select System Tools, and then click Device Manager. 3. In the right pane, expand the Medium Changers node, and then double-click the entry of a Galaxy library.

52

Backup and Restore for Internet Data Center

4. From the active list of the library medium changer, select disable. (Repeat Steps

3 and 4 for each Galaxy library.) 5. You can disable the Removable Storage service in the Services panel if no libraries are attached to the computer needed to run the Removable Storage service. 6. Otherwise, if Removable Storage is running, in the left pane of the Computer Management window, expand Storage, expand Removable Storage, and then expand Physical Locations. Verify that all non-Removable Storage controlled libraries and drives are not present or disabled on the list.

Configuring Libraries and Drives Without Removable Storage After you install your MediaAgent, you must configure the libraries and drives controlled by your MediaAgent. If other applications are using your library, it is necessary to use the Removable Storage service. For more information on configuring the Removable Storage service, refer to the CommCell Media Management Administration Guide. Otherwise, disable the Removable Storage service before you configure. Library configuration may take a minute or more to complete. If you do not regain your prompt within that time period, Galaxy may be having difficulty in starting the DMS or LMS services, which are described as follows: ● Library management service (LMS). The Galaxy service that manages a medium changer. ● Drive management service (DMS). The Galaxy service that manages a media drive. If you suspect this problem, use the Windows Services tool (accessed by clicking Administrative Tools in Control Panel) to check the status. If you see a DMS/LMS service for each drive but it is not started, perform a restart. There must be one DMS for each drive configured for the MediaAgent. Configure the library or drive from either the CommServe computer or the MediaAgent computer.

Direct-Attached Libraries and Drives The following procedure describes how to configure direct-attached libraries and drives.


To configure direct-attached libraries and drives 1. Restart the MediaAgent computer, and then log on again as the same user who installed the MediaAgent. This may take a few moments. 2. In the Galaxy Library and Drive Configuration window, you can detect devices. To do this, click Detect Devices.

Chapter 2: Backup and Restore Deployment

53

3. Select the MediaAgent, and then click Add All or Add to add the selected 4.

5.

6. 7. 8. 9.

MediaAgent(s) to the list. Click OK. If manual detection fails to detect the library or the correct number of drives, confirm that your devices are working properly. If you cannot resolve problems for a specific library at this time, refer to the CommCell Media Management Administration Guide. The library and/or drive alias names are available for easier identification in the future. To change the alias of a library or drive in the Library and Drive Configuration window, right-click the library or drive, click Properties, and then type or change the alias in the alias field. In the Library and Drive Configuration window, right-click the library, and then click Configure. Setup prompts you to confirm the configuration. Click Yes. Click Yes to configure all the drives for the library. Right-click the same library in the window, and then click Discover Media to discover the library. Note: If a library inventory is being taken, Setup will not allow you to discover media. Reattempt the media discovery when the inventory has been completed.

10. In the Library and Drive Configuration window, right-click the library, and then

click Validate to validate the library. Validating the library ensures that Galaxy has access to all of the configured drives. It forces the media changer to physically mount a tape in each drive, confirming that the drive’s physical connection and target SCSI identification match. If the validation failed, unload the stacked medium manually and reset the library for recovery.

Stand-Alone Libraries and Drives The following procedure describes how to configure stand-alone libraries and drives.


To configure stand-alone libraries and drives 1. Repeat Steps 1 and 2 of the procedure described in the preceding section, “Direct-Attached Libraries and Drives.” 2. You may want to rename the stand-alone library and/or drive for easier identification in the future. To change the name of a library or drive, in the Library and

54

Backup and Restore for Internet Data Center

Drive Configuration window, right-click the library or drive, click Properties, and then change the name. 3. In the Library and Drive Configuration window, right-click the library, and then click Configure. 4. Click Yes to confirm the configuration. Note: It is strongly recommended that you physically label each stand-alone drive containing the library name shown in the configuration window. This will help you identify the proper drive when the Galaxy system prompts you to manually insert a cartridge into a stand-alone drive. It is also recommended that you label each media used in a stand-alone drive.

Magnetic Disk Libraries The following procedure describes how to configure magnetic disk libraries.


To configure magnetic disk libraries 1. Repeat Steps 1 and 2 of the procedure described in the preceding section, “Direct-Attached Libraries and Drives.” 2. In the Library and Drive Configuration window, click Add Magnetic Library. Select the name of the MediaAgent that will control the library and type the library’s alias name and low watermark. 3. Click OK. The magnetic library is displayed in the window as mount path, and the Add Mount Path dialog box is displayed. 4. Type/select the magnetic library alias name and ID. Click Use Network Share if the storage area resides on a network share. 5. If the Use Network Share button is selected, type the user name that has access to the share, the user name password, and the mount path of the appropriate magnetic storage area. 6. Click OK. The specified mount path is created and the new mount path is displayed in the Galaxy Library and Drive Configuration window. The magnetic library is now configured. 7. To create additional mount paths for the same magnetic library, right-click the appropriate magnetic library, and then select Add Mount Path. Repeat Steps 4 and 5 for each required mount path.

Configuring Other Libraries For information about the following libraries, please refer to the Galaxy CommServe Quick Start and the CommCell Media Management Administration Guides: ● Removable Storage libraries ● Direct-attached shared libraries

Chapter 2: Backup and Restore Deployment ● ●

55

SAN-attached libraries (Digital Data Storage [DDS] and non-DDS environments) NAS-attached libraries

After You Install a MediaAgent If you plan to install any additional MediaAgents in the immediate future, you should install them all now. Each MediaAgent installation creates a default storage policy for each configured library. Therefore, installing all MediaAgents now provides you with the greatest possible selection of storage policies. However, this is only one approach to installing a CommCell. If you want, you can install additional MediaAgents later and re-associate the client(s) and the storage policies at any time.

Create storage policies for each client you plan to install. Although storage policies can be created at any time, it is a good practice to create a storage policy for each of the clients you plan to install. In addition to making the storage policy available during the installation of the client, creating separate storage policies allows ease of use in offsite tape management. For more information about creating a storage policy, refer to “Storage Policies” in the Daily Operations Guide .

Create a CommServe ExpressRecovery subclient to secure the magnetic CommServeER data to tape For instructions, see the “Setting up CommServeER Subclient” topic in the “Getting Started with iDataAgent Administration” section later in this document.

iDataAgent for Windows 2000 The iDataAgent for Windows 2000 is the backup and restore vehicle for file system data (files, folders, system state, and so on) that resides on computers running the Windows 2000 operating system. The iDataAgent for Windows 2000 is the foundation for all Galaxy products, and needs to be installed before other iDataAgents .

Installing iDataAgent for Windows 2000 This section describes the procedure for installing iDataAgent for Windows 2000.

Before You Begin To help avoid common installation problems you need to: ● Review product changes and enhancements. These are provided in the product release notes.

56

Backup and Restore for Internet Data Center ●

●

●

●

●

●

●

●

●

●

Obtain the appropriate software. Galaxy software CD-ROMs and the iDataAgent for Windows 2000 software. Obtain valid licenses. Ensure you have enough licenses to install the iDataAgent on each required computer within the CommCell. Meet the minimum requirements. The client computer must satisfy the minimum requirements provided in the “System Requirements” section of the Introduction to this chapter. Install to a noncompressed drive. Make sure that iDataAgent for Windows 2000 is not installed on a compressed drive. Verify CommServe is running. The CommServe computer is turned on and the CommServe software is running. Have IP connectivity to the CommServe. If your network does not have DNS lookup or some other name resolution facility, you may be asked to enter the IP address of the CommServe computer. Verify the binding order on clients that are multihomed. The binding order is significant for the Galaxy software to communicate with the CommServe and MediaAgent. Refer to the Galaxy Windows 2000 Server Family iDataAgents Release Notes document for specific instructions on configuring your network adapter binding order. Regarding the firewall: ● Have an appropriate firewall configuration. If your client computer is on the opposite side of a firewall from a CommServe and/or MediaAgent, and the CommServe and MediaAgent have not been configured for firewall support, refer to the Galaxy Pre-Installation Checklist for specific instructions on configuring your firewall. - or ● Configure the client for firewall support. If your client computer is on the opposite side of a firewall from a CommServe and MediaAgent that have already been configured for firewall support, it is only necessary to add the Firewall.svc and Firewall_loc.txt files (as described in the Galaxy Pre-Installation Checklist) to your client. After these files are added to your client, you must also add the client name to the Firewall_loc.txt file of your CommServe. Create storage policies. Storage policies must be created for the client, as suggested in “After You Install a MediaAgent” in the previous section of this chapter. Install patches. All applicable Galaxy patches have been applied.

Chapter 2: Backup and Restore Deployment

57

Note: For domain controllers, Galaxy 3.1 GSP1 requires that patches 4, 11 and 23 be applied. You may receive an error during patch installation that the client was unable to communicate with the CommServe. This error may occur if the path to the Galaxy installation directory has not been applied to the environment. You can correct the error by applying the path to the environment (MyComputer\Properties\Advanced\Environment variables\System Path) and restarting the Galaxy services. Or you can ignore the error and continue with the patch installation. The patch will still apply to the client computer. This is a Galaxy 3.1 GSP1–specific issue and has been corrected. ●




Create subclient filters. Subclient filters must be created on clusters and any applicable clients.

To install iDataAgent for Windows 2000 1. Log on to the client computer as Administrator or as a member of the Administrators group on that computer. The Galaxy software can only be installed by a user who is a member of the local Administrators group. 2. Place the Galaxy software CD-ROM that is appropriate to the client computer’s operating system into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. The installation will become corrupted unless the drive is actually mapped.

3. From the Select Platform window, select iDA for Windows File System from the

installation menu, and then click Install. Setup checks your Windows user account for the necessary user rights. If your account already has the necessary rights, you will not receive this prompt. Continue to the next step. If your account does not have the necessary rights, it automatically assigns the required rights to your account, and then prompts you to log off and log back on. 4. The Galaxy Base Client Installation window prompts you to close any running applications. If necessary, exit Setup and close your running applications, or click Next to continue. 5. The Software License Agreement window prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement.

58

Backup and Restore for Internet Data Center

6. If Galaxy software is already installed on this computer, you will not receive this

prompt. Continue to the next step. The Choose Destination Location window prompts you to choose the location of the Galaxy installation directory. Either accept the default by clicking Next, or click Browse to name a different location on a local disk drive. (Do not install the software to a mapped network drive.) Note: If you intend to install other Galaxy software on this computer, the selected installation directory will be automatically used for that software as well.

7. The Galaxy CommServe Computer and Host Name window prompts you to

enter the following: ● CommServe computer name (short name). This is the local (NetBIOS) name of the CommServe computer. ● CommServe host name (FQDN). This is the TCP/IP network name of the CommServe computer (computer.company.com, for example). If Galaxy software is already installed on this computer, one or more of the fields on this screen may already be filled in and therefore unavailable. 8. The Galaxy Computer Name window prompts you to configure the client’s communications paths. (If you are performing a virtual server installation, you should use the virtual server information for the client computer.) Enter or select: ● The local (NetBIOS) name of the client computer. ● The TCP/IP host name of the NIC that the client computer is to use to communicate with the CommServe. ● The TCP/IP host name of the NIC that the client computer is to use as the default interface for transferring all backup/restore data on that client computer. (You can specify the same NIC for both NIC entries.) 9. The Job Results Destination Location window prompts you to specify the loca-

tion of the client’s job results directory. Galaxy uses the job results directory to store the client’s backup and restore job results. Choose a location that is on a local disk drive. 10. The Start Copying Files window displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. 11. After you click Next, Setup starts copying the Base Client software to the computer. This step may take a few minutes to complete. With the Base Client software installed, Setup automatically starts the installation of iDataAgent for Windows 2000.

Chapter 2: Backup and Restore Deployment

59

12. The Galaxy Windows 2000 iDataAgent Installation window prompts you to close

any running applications. If necessary, exit Setup and close your running applications. You may be prompted to restart the system. 13. The Software License Agreement window prompts you to read the Galaxy license agreement. To continue, you must accept the terms of the agreement. 14. Next, select a storage policy from the Storage Policy Selection window. A storage policy directs backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient. Note: You can change your selection at any time after you have installed the client software.

15. Next, the Start Copying Files window displays a summary of the installation

options that you have chosen. Click Next to continue or Back to change any option. 16. After you click Next, Setup starts copying the iDataAgent software to the computer. This step may take a few minutes to complete. 17. The system displays the Setup Complete window. To close this window, click Finish. Note the following: ● If you installed file system clients while the CommCell Console was open, you need to refresh the CommCell Console (press F5) to see the new clients. ● If you installed in a clustered environment, access iDataAgent for Windows 2000 from the CommCell console. From this iDataAgent, filter the subclients: ● Filter all shared drives from the physical clients (node 1 and node 2). ● Filter all local drives and shared drives owned by other virtual disk groups for each virtual client. ●

●

The default subclient automatically backs up the quorum database. If you are using file system backups to back up the quorum database, filter all applications accordingly. If you installed the file system client software on the CommServe computer, record the required information on the CommServe ExpressRecovery Data Sheet in the CommCell Quick Start Guide. Doing so will help you avoid problems should you need to recover the CommServe database at some future time.

This procedure is now complete. You can now do any of the following: ● Install the file system client software on another computer.

60

Backup and Restore for Internet Data Center ●

●

Back up the file system data on the client computer that you just installed. For more information, see “Backing Up iDataAgent for Windows 2000” later in this section. Exit the installation menu.

Installing iDataAgent for Windows 2000 on a Cluster Galaxy software supports the advanced reliability and availability features of a clustering environment for certain applications that can run in a clustered environment (such as iDataAgents for Windows 2000). Installation instructions for installing iDataAgent for Windows 2000 in a clustering environment follow. For more information on Galaxy clustering, see the CommServe Administration Guide.

Before You Begin To help avoid common installation problems, in addition to the list in the previous section, you need to: ● Ensure all nodes are running. Prior to installing the client software, make sure that both the active and passive nodes are available. ● Correctly install iDataAgent for Windows 2000. This iDataAgent must be installed onto the active (physical) node, then install it onto all passive (physical) nodes. This iDataAgent must be installed on all physical nodes in the cluster prior to attempting any virtual server installations. ● Cluster service should bind the public network interface card before the private network interface card. ● Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. ● Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running.


To install iDataAgent for Windows 2000 on a cluster 1. Log on to the client computer as Domain User with privileges to all nodes in the cluster. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK.

Chapter 2: Backup and Restore Deployment

61

Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. Note the installation will become corrupted unless the drive is actually mapped.

3. On the installation menu, select iDA for Windows File System, and then click

Install. Note: Physical nodes must have iDataAgent for Windows 2000 installed prior to installing the client software on the virtual node.

4. A dialog box states that the physical node is running as a cluster node and

5. 6.

7.

8. 9.

10.

prompts you to specify a physical node installation or a virtual server installation. Select Virtual Server, and then click Next. A list of virtual servers configured for the node displays. Select a virtual server (which is the disk group where your virtual server resides). A dialog box displays a list of virtual servers configured for the node. Select a virtual server (which is the disk group where your virtual server resides), and then click Next. Setup checks your Windows user account for the necessary user rights. If your account already has the necessary rights, you will not receive this prompt. Continue to the next step. If your account does not have the necessary rights, it automatically assigns the required rights to your account, and then prompts you to log off and log back on. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications. A dialog box prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. If Galaxy software is already installed on this computer, you will not receive this prompt. Continue to the next step. A dialog box prompts you to choose the location of the Galaxy installation directory. Either accept the default by clicking Next, or click Browse to name a different location on a local disk drive. (Do not install the software to a mapped network drive.) In the folder window, type the full path, including drive letter, for the Galaxy installation Note: If you intend to install other Galaxy software on this computer, the selected installation directory will be automatically used for that software as well.

11. A dialog box prompts you to enter the following: ●

CommServe computer name (short name). This is the local (NetBIOS) name of the CommServe computer.

62

Backup and Restore for Internet Data Center ●

CommServe host name (FQDN). This is the TCP/IP network name of the CommServe computer (computer.company.com, for example).

If Galaxy software is already installed on this computer, one or more of the fields on this screen may already be filled in and therefore unavailable. 12. A dialog box prompts you to configure the client’s communications paths. (If you are performing a virtual server installation, the virtual server information should be used for the client computer.) Enter or select: ● The local (NetBIOS) name of the client computer. ● The TCP/IP host name of the NIC that the client computer is to use to communicate with the CommServe. You can specify the same NIC for both NIC entries. ● The TCP/IP host name of the NIC that the client computer is to use as the default interface for transferring all backup/restore data on that client computer. 13. A dialog box prompts you to specify the location of the client’s job results direc-

14.

15.

16. 17.

tory. Galaxy uses the job results directory to store the client’s backup and restore job results. Choose a location that is on a local disk drive. A dialog box displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. After you click Next, Setup starts copying the Base Client software to the computer. This step may take a few minutes to complete. With the Base Client software installed, Setup automatically starts the installation of iDataAgent for Windows 2000. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications. You may be prompted to restart the system. A dialog box prompts you to read the Galaxy license agreement. To continue, you must accept the terms of the agreement. In the next window, you will select a storage policy. A storage policy directs backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient. Note: You can change your selection at any time after you have installed the client software.

18. A dialog box displays a summary of the installation options that you have

chosen. Click Next to continue or Back to change any option. After you click Next, Setup starts copying the iDataAgent software to the computer. This step may take a few minutes to complete.

Chapter 2: Backup and Restore Deployment

63

19. The system displays the Setup Complete window. To close this window, click

Finish. Note the following: ● If you installed File System clients while the CommCell Console was open, you need to refresh the CommCell Console (press F5) to see the new clients. ● If you installed in a clustered environment, access iDataAgent for Windows 2000 from the CommCell Console. From this iDataAgent, filter the subclients: ● Filter all shared drives from the physical clients (node 1 and node 2). ● Filter all local drives and shared drives owned by other virtual disk groups for each virtual client. ●

●

The default subclient automatically backs up the quorum database. If you are using file system backups to back up the quorum database, filter all applications accordingly. If you installed the file system client software on the CommServe computer, record the required information on the CommServe ExpressRecovery Data Sheet in the Galaxy CommServe Quick Start Guide. Doing so will help you avoid problems should you need to recover the CommServe database at some future time.

This procedure is complete. You can now do any of the following: ● Install the file system client software on another computer. ● Back up the file system data on the client computer that you just installed. For more information, see “Backing Up iDataAgent for Windows 2000” later in this section. ● Exit the installation menu.

Performing a Manual Passive Node Installation This procedure must be used if a passive node failed to update during the installation of the active node. 1. Repeat Steps 1 through 6 of the previous installation procedure. Then proceed to the next step. 2. If you do not know this information, check the active node registry. (If you are performing a virtual server installation, the virtual server information should be used for the client computer.) A dialog box prompts you for the following information: ● Galaxy install folder on shared disk. This is the installation path you used during the active installation. ● CommServe computer name. This is the short name of the computer on which the CommServe is installed.

64

Backup and Restore for Internet Data Center ●

●

●

CommServe host name. The FQDN of the computer on which the CommServe is installed (computer.company.com, for example). Client name. This is the local (NetBIOS) name of the virtual server (the short name for the client). Communication interface. This is the TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the client).

Note: If you have already installed the iDataAgent for Windows 2000, this prompt displayed during that installation, and is not re-displayed at this time.

3. The registry and environmental files are updated on the passive node. When the

update is complete, the system displays the Setup Complete dialog box. To close this window, click Finish.

Backing Up iDataAgent for Windows 2000 In this section, you will back up the file system of the client computer.

Before You Begin To help avoid common installation problems you need to: ● Ensure that all systems are running. Make sure that the CommServe is running, the MediaAgent computer and media library are turned on, and the client computer is turned on. ● Ensure that all software is installed. The file system client software must be installed on the client computer. ● Check services are started. All Galaxy services must have been started. ● Perform Discover Media. Discover Media must be performed to ensure you have media to back up. ● Check Pre/Post commands. Application Center Services require Pre/Post commands on the Pre/Post Process tab of the default subclient Properties dialog box. This is because Application Center Server has a personal edition of Microsoft SQL Server, and backup and restore of this edition is performed by iDataAgent for Windows 2000, rather than iDataAgent for SQL Server. To successfully backup the databases, the following commands must be entered. The PreBackup process field should point to a batch file that contains the following command: net stop SQLAgent$MSAC net stop MSSQL$MSAC

Chapter 2: Backup and Restore Deployment

65

The PostBackup process field should point to a batch file that contains the following command: net start MSSQL$MSAC net start SQLAgent$MSAC

Perform an Immediate Full Backup of the Default Subclient The following procedure describes how to back up the default subclient.


To back up the default subclient 1. Log on to the CommServe computer. 2. On the Windows taskbar, click the Start button, point to Programs, point to Galaxy, and then click Galaxy CommCell Console for Java GUI. 3. In the CommCell Logon window, log on by entering your Galaxy user name and password. Galaxy displays the CommCell Console window. 4. In the CommCell Browser, open the Client Computers node, and then the appropriate client. Right-click the File System icon, and then click Backup Default Backup Set. 5. Galaxy informs you that this kind of backup starts a backup of all subclients within the backup set. In this case, because you haven’t defined any other subclients, only the default subclient exists. Galaxy prompts you to indicate whether you want to continue. Click Yes. 6. In the Backup Options window, click Full for a full backup, and then click OK. (Regardless of the type of backup you select, Galaxy performs a full backup the first time any file system is backed up.) 7. Galaxy starts a full backup of the file system and indicates its status in the Job Controller window. The job status should change from Waiting to Running in a few moments. (You can track the status by right-clicking the job and then clicking Details.) Note: Depending on the size of the file system and the type of backup media selected, the backup may take a while.

8. When the backup is complete, Galaxy displays a completion message. Click OK

to close the window. This completes the backup.

66

Backup and Restore for Internet Data Center

Where to Go From Here Now that you have installed Galaxy and run your first backup, you probably want to set up backup schedules, monitor the success of your backups, and configure Galaxy to notify you when significant system events occur. See the “Getting Started with iDataAgent Administration” section later in this document, and the Daily Operations Guide for basic administrative tasks.

Database iDataAgent for Exchange 2000 The database iDataAgent for Exchange 2000 Server is the backup and restore vehicle for Exchange 2000 Server data, including: ● Information stores. ● Public folder stores. ● Transaction logs and patch files. ● Exchange 2000 organizational data.

Installing the Database iDataAgent for Exchange 2000 This section describes how to install the database iDataAgent for Exchange 2000 .

Before You Begin To help avoid common installation problems you need to: ● Review product changes and enhancements. These are provided in the product release notes. ● Obtain the appropriate software. Galaxy software CD-ROMs and the iDataAgent for Exchange 2000 software. ● Obtain valid licenses. Ensure you have enough licenses to install the iDataAgent on each required computer within the CommCell. ● Meet the minimum requirements. The client computer must satisfy the minimum requirements provided in the “Satisfy System Requirements” section of the client Quick Start Guide. ● Install to a noncompressed drive. Make sure that iDataAgent for Exchange 2000 is not installed on a compressed drive. ● Check for iDataAgent for Windows 2000. This iDataAgent software must be installed on the client computer. ● Verify that CommServe is running. The CommServe computer is turned on and the CommServe software is running.

Chapter 2: Backup and Restore Deployment ●

●

●

● ●




67

Have IP connectivity to the CommServe. If your network does not have Domain Name System (DNS) lookup or some other name resolution facility, you may be asked to enter the IP address of the CommServe computer. Regarding the firewall: ● Have an appropriate firewall configuration. If your client computer is on the opposite side of a firewall from a CommServe and/or MediaAgent, and the CommServe and MediaAgent have not been configured for firewall support, refer to the Galaxy Pre-Installation Checklist for specific instructions on configuring your firewall. - or ● Configure the client for firewall support. If your client computer is on the opposite side of a firewall from a CommServe and MediaAgent that have already been configured for firewall support, it is only necessary to add the Firewall.svc and Firewall_loc.txt files (as described in the Galaxy Pre-Installation Checklist) to your client. After these files are added to your client, you must also add the client name to the Firewall_loc.txt file of your CommServe. Create storage policies. Storage policies must be created for the client, as suggested in the topic “After You Install a MediaAgent” in the previous section of this chapter. Install patches. All applicable Galaxy patches must have been applied. Create subclient filters. Subclient filters must be created on clusters and any applicable clients.

To install the database iDataAgent for Exchange 2000 1. Log on to the client computer as Administrator or as a member of the Administrators group on that computer. The Galaxy software must be installed by a user who is a member of the local Administrators group. 2. Place the Galaxy software CD-ROM for the appropriate Windows platform into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. 3. Setup prompts you to select a Galaxy software module. Select iDA for Exchange

Database, and then click Install. Optionally, you can install both the database and mailbox iDataAgents by selecting Exchange iDataAgents. Setup verifies that the file system client software is installed on the computer.

68

Backup and Restore for Internet Data Center

If the file system client software is already installed on this computer, you will not receive this prompt. Continue with the next step. If it is not installed, you will be prompted to install it now. For instructions on installing the file system client software, see the Client Quick Start Guide (Windows 2000 Server Family). 4. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications, or click Next to continue. 5. A dialog box prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. 6. In the next dialog box type in the following information then click Next: ● Exchange Site Service Account Name ● Exchange Site Service Domain Name ● Exchange Site Service Account Password 7. A dialog box prompts you to select the backup type for Exchange 2000 database

backups. A backup type is the selected partial backup that you run between full backups. Select the backup type that you want for this client computer from either of the following options, and then click Next: ● Differential. Backs up all new and changed data since the last full backup. ● Incremental. Backs up all new and changed data since the last backup. Note: This setting can be changed later from the CommCell Console.

8. A dialog box prompts you to select a storage policy. A storage policy directs

backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. 9. A dialog box displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. When you install the iDataAgent, Galaxy creates a default subclient. This subclient can backup the entire Exchange 2000 database. 10. Setup checks to see if circular logging is enabled. Circular logging must be off for Exchange 2000 database backups to operate properly. If circular logging is disabled, you will not receive this prompt. Continue to the next step. If circular logging is on, Setup displays a message asking if it can disable circular logging. Click Yes to disable circular logging. (You can click No and complete the installation, but you must still disable circular logging before you perform a backup.)

Chapter 2: Backup and Restore Deployment

69

Setup starts copying the iDataAgent software to the computer. This step may take a few minutes to complete. 11. The system displays the Setup Complete dialog box. To close this dialog box, click Finish. You can now do any of the following: ● Install the Exchange 2000 database client software on another client computer. ● Backup Exchange 2000 database data on the client computer that you just installed; for instructions see “Backing Up the Database iDataAgent for Exchange 2000” later in this section. ● Exit the installation program.

Installing the Database iDataAgent for Exchange 2000 on a Cluster Galaxy software supports the advanced reliability and availability features of a clustering environment for certain applications that can run in a clustered environment (such as iDataAgents for Exchange 2000). Installation instructions for installing these iDataAgents in a clustering environment are provided below. For more information about Galaxy clustering, see the CommServe Administration Guide.

Before You Begin To help avoid common installation problems, in addition to the list in the previous section, you need to: ● Ensure all nodes are running. Prior to installing the client software, make sure that both the active and passive nodes are available. ● Correctly install iDataAgent for Windows 2000. This iDataAgent must be installed onto the active (physical) node, and then installed onto all passive (physical) nodes. The iDataAgent for Windows 2000 must be installed on all physical nodes in the cluster prior to attempting any virtual server installations. ● Install iDataAgent for Exchange 2000. Install iDataAgent for Exchange 2000 (database or mailbox) for the virtual server on the active node. ● Cluster service should bind the public network interface card before the private network interface card. ● Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. ● Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running.

70

Backup and Restore for Internet Data Center




To install the database iDataAgent for Exchange 2000 on a cluster 1. Log on to the client computer as Domain User with privileges to all nodes in the cluster. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. 3. Setup prompts you to select a Galaxy software module. Select iDA for Exchange

Database, and then click Install. Optionally, you can install both the database iDataAgent for Exchange 2000 and the mailbox iDataAgent for Exchange 2000 software by selecting Exchange iDataAgents. 4. A dialog box displays a message stating that the physical node is running as a cluster node; it prompts you to specify a physical node installation or a virtual server installation. Select Virtual Server then click Next. Note: Physical nodes must have iDataAgent for Windows 2000 installed prior to installing the database iDataAgent for Exchange 2000 software on the virtual node.

5. A dialog box prompts you to indicate whether you have installed iDataAgent for

6.

7. 8. 9.

Windows 2000 on all physical nodes. If necessary, exit Setup and do this before proceeding, otherwise click Yes to continue. A dialog box displays a list of virtual servers configured for the node. Select a virtual server (which is the disk group where your virtual server resides), and then click Next. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications or click Next to continue. A dialog box prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. In the next dialog box, you will select a storage policy. A storage policy directs backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. A dialog box displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. After you click Next, Setup starts copying the client software to the computer. This step may take a few minutes to complete.

Chapter 2: Backup and Restore Deployment

71

A list of all nodes to which the virtual server can fail over is available in the Start Copying Files dialog box. Each of these nodes is to be updated with the active node settings. Click Next to continue. 10. Click OK. If you are informed at the end of the active node installation that the passive node was not available, select one of the following choices; otherwise continue on to the next step. ● Click No, and then follow the procedure for Performing a Manual Passive Node Installation on the next page. - or ● Click Yes to update any remaining nodes. 11. The registry and environmental files are updated on the passive node. When the

update is complete, the system displays the Setup Complete dialog box. To close this dialog box, click Finish. 12. From the CommCell Console, access iDataAgent for Windows 2000. From this iDataAgent, filter the subclients: ● Filter all shared drives from the physical clients (node 1 and node 2). ● Filter all local drives and shared drives owned by other virtual disk groups for each virtual client. The default subclient automatically backs up the quorum database. If you are using file system backups to back up the quorum database, filter all applications accordingly. This procedure is complete. You can now do any of the following: ● Install the database iDataAgent for Exchange 2000 client software on another client computer in the cluster. ● Back up Exchange 2000 data on the client computer that you just installed; for instructions, see the topic “Backing Up the Database iDataAgent for Exchange 2000” later in this section. ● Install the Exchange 2000 mailbox client software on this or another client computer in the cluster; for instructions, see “Installing the Mailbox iDataAgent for Exchange 2000 on a Cluster” in the next section of this document. ● Exit the installation menu.

Performing a Manual Passive Node Installation This procedure must be used if a passive node failed to update during the installation of the active node.

72

Backup and Restore for Internet Data Center




To manually install a passive node 1. Repeat Steps 1 through 6 of the installation procedure. Then proceed to the next step. 2. A dialog box prompts you for the following information. If you have already installed iDataAgent for Windows 2000, this dialog box will have been displayed during that installation and will not be re-displayed at this time. If you do not know this information, check the active node’s registry. Its path in the registry is HKEY_LOCAL_MACHINE/SOFTWARE/CommVault Systems/ Galaxy/ Platform Information/virtual_computer, where virtual_computer is the name of your client computer: ● Galaxy install folder on shared disk. The install folder of the disk onto which you are installing the passive node. Base key: dGALAXYHOME ●

CommServe computer name. The local (NetBIOS) CommServe name (short name of the CommServe). CommServe key: sCSCLIENTNAME

●

CommServe host name. The TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the CommServe). CommServe key: sCSHOSTNAME

●

Client name. The local (NetBIOS) name of the virtual server (the short name for the client). Session key: sCLIENTNAME

●

Communication interface. The TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the client). Session key: sHOSTNAME

3. The registry and environmental files are updated on the passive node. When the

update is complete, the system displays the Setup Complete dialog box. To close this window, click Finish.

Chapter 2: Backup and Restore Deployment

73

Backing Up the Database iDataAgent for Exchange 2000 This section describes how to back up the database iDataAgent for Exchange 2000.

Before You Begin To help avoid common installation problems you need to: ● Review product changes and enhancements. These are provided in the product release notes. ● Ensure that all software is installed. The database iDataAgent for Exchange 2000 software must be installed on the client computer. ● Ensure that all systems are running. The client computer is turned on. ● Ensure that you have enough licenses. You must have enough licenses to install the iDataAgent on each required computer within the CommCell.

Execute an Immediate Full Backup of the Default Subclient After you have reviewed the preceding section, you are ready to back up the file system on the client computer. Note: It is advisable to back up the database Exchange 2000 at the same relative time as the system state data, using iDataAgent for Windows 2000. The reason is that the stores are backed up in this procedure. The user and mailbox information is backed up as part of Active Directory. The two should be in sync to provide valid backup data. This is necessary for the Exchange 2000 disaster recovery procedure.

1. On the Windows taskbar, click the Start button, point to Programs, point to 2.

3.

4.

5.

Galaxy, and then click Galaxy CommCell Console for Java GUI. In the CommCell Logon window, log on by entering your Galaxy user name and password. Galaxy displays the CommCell Console window. In the CommCell browser, open Client Computers, and then open the appropriate client. Right-click the iDA Exchange 2000 Database icon, and then click Backup All Subclients. Galaxy prompts you to confirm that you want to backup all subclients. In this case, because you haven’t defined any other subclients, only the default subclient exists. Click Yes to confirm. In the Backup Options window, click Full Backup, and then click OK. (Regardless of the backup type you select, Galaxy performs a full backup the first time any computer is backed up.) Galaxy starts a full backup of the Exchange 2000 database and indicates its status in the Job Controller window. The job status should change from Waiting to Running in a few moments.

74

Backup and Restore for Internet Data Center

6. When the backup completes, Galaxy displays a completion message. Click OK to

close the window. You’ve just completed your first Exchange 2000 database backup using Galaxy. Remember to back up Active Directory in the system state as well.

Where to Go From Here Now that you’ve installed Galaxy and run your first backup, you probably want to set up backup schedules, monitor the success of your backups, and configure Galaxy to notify you when significant system events occur. For more information about these basic administrative tasks, see the topic “Getting Started with iDataAgent Administration” later in this chapter and the Daily Operations Guide.

Mailbox iDataAgent for Exchange 2000 The mailbox iDataAgent for Exchange 2000 is the backup and restore vehicle for some or all of the mailbox entities. Specifically, you can use the mailbox iDataAgent for Exchange 2000 to restore the following: ● One or more mailboxes ● One or more mailboxes from an Exchange version 5.5 Server to an Exchange 2000 Server ● One or more folders within a mailbox ● One or more messages within a mailbox

Installing the Mailbox iDataAgent for Exchange 2000 This section describes how to install the mailbox iDataAgent for Exchange 2000.

Before You Begin To help avoid common installation problems you need to: ● Review product changes and enhancements. These are provided in the product release notes. ● Obtain valid licenses. Ensure that you have enough licenses to install the iDataAgent on each required computer within the CommCell. ● Install to a noncompressed drive. Make sure mailbox iDataAgent for Exchange 2000 is not installed on a compressed drive. ● Create a valid mailbox. Prior to installing this iDataAgent, you must create a mailbox that has the proper permissions. Some points to keep in mind when setting up this mailbox follow:

Chapter 2: Backup and Restore Deployment ●

●

●

●

●

● ●

●




75

Use GalaxyAdmin, or something similar, as the mailbox name for the first installation only. When more than one mailbox iDataAgent for Exchange 2000 is installed within one Exchange 2000 Server site, the GalaxyAdmin mailbox name for each installation must be unique. On subsequent installations, it is recommended that you use GalaxyAdmin1, GalaxyAdmin2, and so on, for each mailbox name. This provides the necessary unique mailbox/alias for each installed mailbox iDataAgent for Exchange 2000.

The GalaxyAdmin user must be a member of the following groups: ● Account operators ● Domain administrators ● Domain users ● Exchange administrators ● Server operators You must allow enough time for Active Directory replication to complete before proceeding with the installation process. Create storage policies. Storage policies must be created for the client, as suggested in the topic “After You Install a MediaAgent” earlier in this chapter. Install patches. All applicable Galaxy patches must have been applied. Configure firewall support. Galaxy firewall support, if applicable, must be properly implemented. Create subclient filters. Subclient filters must be created on clusters and any applicable clients.

To install the mailbox iDataAgent for Exchange 2000 1. Log on to the client computer (Exchange 2000 Server, for example) as Administrator or as a member of the Administrators group on that computer. The Galaxy software must be installed by a user who is a member of the local Administrators group. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. 3. Setup prompts you to select a Galaxy software module. Select iDA for Exchange

Mailbox, and then click Install.

76

Backup and Restore for Internet Data Center

4.

5. 6. 7.

Optionally, you can install both the database iDataAgent for Exchange 2000 and the mailbox iDataAgent for Exchange 2000 software by selecting the Exchange iDataAgents option. Setup verifies that the file system client software is installed on the computer. If the file system client software is already installed on this computer, you will not receive this prompt. Continue with the next step. If it is not installed, you will be prompted to install it now. For instructions on installing the file system client software, see the Client Quick Start Guide (Windows 2000 Server Family). A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications or click Next to continue. A dialog box prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. In the next dialog box enter the following information, and then click Next: ● Account name for the GalaxyAdmin account ● Account password for this account ● Mailbox name for this account ● Profile name that you want to use for the GalaxyAdmin mailbox ● Exchange server name ● Domain name

8. A dialog box prompts you to select a storage policy. A storage policy directs

backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. 9. A dialog box displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. When you install the iDataAgent, Galaxy creates a default subclient. This subclient can back up all the mailboxes on the server running Exchange. 10. After you click Next, Setup starts copying the client software to the computer. This step may take a few minutes to complete. 11. The system displays the Setup Complete dialog box. To close this dialog box, click Finish. You can now do any of the following: ● Install the mailbox iDataAgent for Exchange 2000 software on another client computer. ● Back up mailbox data for Exchange 2000 on the computer that you just installed. For instructions, see the topic “Backing Up the Mailbox iDataAgent for Exchange 2000” later in this section.

Chapter 2: Backup and Restore Deployment ●

●

77

Install the database Exchange 2000 software on this or another client computer. For instructions, see the topic “Installing the Database iDataAgent for Exchange 2000” in the previous section. Exit the installation program.

Installing the Mailbox iDataAgent for Exchange 2000 on a Cluster Galaxy software supports the advanced reliability and availability features of a clustering environment for certain applications that can run in a clustered environment (such as iDataAgents for Exchange 2000). Installation instructions for installing these iDataAgents in a clustering environment follow. For more information on Galaxy clustering, see the CommServe Administration Guide.

Before You Begin To help avoid common installation problems, in addition to the previous list, you need to: ● Obtain the appropriate software. Galaxy software CD-ROMs and the iDataAgent for Exchange 2000 software. ● Meet the minimum requirements. The client computer must satisfy the minimum requirements provided in Satisfy System Requirements of the client Quick Start Guide. ● Ensure that the CommServe is available. The CommServe computer is turned on and the CommServe software is running. ● Have IP connectivity to the CommServe. If your network does not have DNS lookup or some other name resolution facility, you may be asked to enter the IP address of the CommServe computer. ● Regarding the firewall: ● Have an appropriate firewall configuration. If your client computer is on the opposite side of a firewall from a CommServe and/or MediaAgent, and the CommServe and MediaAgent have not been configured for firewall support, refer to the Galaxy Pre-Installation Checklist for specific instructions on configuring your firewall. - or ● Configure the client for firewall support. If your client computer is on the opposite side of a firewall from a CommServe and MediaAgent that have already been configured for firewall support, it is only necessary to add the Firewall.svc and Firewall_loc.txt files (as described in the Galaxy PreInstallation Checklist) to your client. After these files are added to your client, you must also add the client name to the Firewall_loc.txt file of your CommServe.

78

Backup and Restore for Internet Data Center ●

●

●

●

●

●

●

● ●

●

Ensure that all of the nodes are running. Prior to installing the client software, make sure that both the active and passive nodes are available. Cluster service should bind the public network interface card before the private network interface card. Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running. Correctly install iDataAgent for Windows 2000. The file system software must be installed on the client computer; and it must be installed first onto the active (physical) node, then installed onto all passive (physical) nodes. iDataAgent for Windows 2000 must be installed on all physical nodes in the cluster prior to attempting any virtual server installations. Install iDataAgent for Exchange 2000. Install this iDataAgent (database or mailbox) for the virtual server on the active node. Create storage policies. Storage policies must be created for the client, as suggested in the “After You Install a MediaAgent” section earlier in this chapter. Install patches. All applicable Galaxy patches must have been applied. Create subclient filters. Subclient filters must be created on clusters and any applicable clients. Create a valid mailbox. Prior to installing the mailbox iDataAgent for the Exchange 2000, you must create a mail-enabled user that has the proper permissions. When setting up this mail-enabled user: ● Use GalaxyAdmin, or something similar, as the mailbox name for the first installation only. ● The GalaxyAdmin user must be a member of the following groups: ● ● ● ●

Account operators Domain administrators Domain users Server operators

You must allow enough time for Active Directory to replicate the previous information before proceeding with the installation process.

Installing the Mailbox iDataAgent for Exchange 2000 on a Cluster This section describes how to install the mailbox iDataAgent for Exchange 2000 on a cluster.

Chapter 2: Backup and Restore Deployment




79

To install the mailbox iDataAgent for Exchange 2000 on a cluster 1. Log on to the client computer (Exchange 2000 Server, for example) as Domain User with privileges to all nodes in the cluster. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. 3. Setup prompts you to select a Galaxy software module. Select iDA for Exchange

Mailbox, and then click Install. Optionally, you can install both the database iDataAgent for Exchange 2000 and the mailbox iDataAgent for Exchange 2000 software by selecting Exchange iDataAgents. 4. A dialog box displays a message stating that the physical node is running as a cluster node and prompts you to specify a physical node installation or a virtual server installation. Select Virtual Server, and then click Next. Note: Physical nodes must have iDataAgent for Windows 2000 installed prior to installing the mailbox iDataAgent for Exchange 2000 software on the virtual node.

5. A dialog box prompts you to indicate that you have installed iDataAgent for

6.

7. 8. 9.

Windows 2000 on all physical nodes. If necessary, exit Setup and do this before proceeding, otherwise click Yes to continue. A dialog box displays a list of virtual servers configured for the node. Select a virtual server (which is the disk group where your virtual server resides), and then click Next. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications, or click Next to continue. A dialog box prompts you to read the Galaxy license agreement. To continue, you must click Yes and accept the terms of the agreement. In the next dialog box enter the following information (if you do not know this information, check the active node registry): ● Account name for the GalaxyAdmin account ● Account password for this account ● Mailbox name for this account ● Profile name you want to use for the GalaxyAdmin mailbox ● Exchange server name ● Domain name

80

Backup and Restore for Internet Data Center

10. A dialog box prompts you to select a storage policy. A storage policy directs

11.

12.

13. 14.

backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. A dialog box displays a summary of the installation options that you have chosen. Click Next to continue or Back to change any option. After you click Next, Setup starts copying the client software to the computer. This step may take a few minutes to complete. A list of all nodes to which the virtual server can fail over is available in the Start Copying Files dialog box. Each of these nodes is to be updated with the active node settings. Click Next to continue. Click OK. If you are informed at the end of the active node installation that the passive node was not available, select one of the following; otherwise continue on to the next step: ● Click Yes to continue with the active installation and update any remaining passive nodes. - or ● Click No to continue with the active installation and skip updating any remaining passive nodes.

If this message appears for the node listed in the message, follow the steps for “Performing a Manual Passive Node Installation” in the following topic. 15. The registry and environmental files are updated on the passive node. When the update is complete, the system displays the Setup Complete dialog box. To close this dialog box, click Finish. 16. From the CommCell console, access iDataAgent for Windows 2000. From this iDataAgent, do the following: ● Filter all shared drives from the physical clients (node 1 and node 2). ● Filter all local drives and shared drives owned by other virtual disk groups for each virtual client. 17. The default subclient automatically backs up the quorum database. If you are

using file system backups to back up the quorum database, filter all applications accordingly. This procedure is complete. You can now do any of the following: ● Install the mailbox iDataAgent for Exchange 2000 on another client computer in the cluster.

Chapter 2: Backup and Restore Deployment ●

●

81

Back up Exchange 2000 mailbox data on the computer that you just installed; for instructions see the topic “Backing Up the Mailbox iDataAgent for Exchange 2000” later in this section. Exit the installation program.

Performing a Manual Passive Node Installation This procedure must be used if a passive node failed to update during the installation of the active node. 1. Repeat Steps 1 through 6 of the installation procedure, and then proceed to the next step. 2. A dialog box prompts you for information listed in the next step. If you have already installed iDataAgent for Windows 2000, this dialog box will have been displayed during that installation and will not be displayed at this time. 3. If you do not know this information, check the active node’s registry. Its registry path is the following: HKEY_LOCAL_MACHINE/SOFTWARE/CommVault Systems/Galaxy/Platform Information/ passive_computer

(where passive_computer is the name of the computer you are making passive). The following information is for the virtual server, not the physical node (the host name is the network name of the virtual server, not the host name of the owning node): ● Galaxy install folder on shared disk. The install folder of the disk onto which you are installing the passive node. Base key: dGALAXYHOME ● CommServe computer name. The local (NetBIOS) CommServe name (short name of the CommServe). CommServe key: sCSCLIENTNAME ● CommServe host name. The TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the CommServe). CommServe key: sCSHOSTNAME ● Client name. The local (NetBIOS) name of the virtual server (the short name for the client). Session key: sCLIENTNAME ● Communication interface. The TCP/IP host name of the NIC that the virtual server uses to communicate with the CommServe (FQDN of the client). Session key: sHOSTNAME

82

Backup and Restore for Internet Data Center

4. The registry and environmental files are updated on the passive node. When the

update is complete, the system displays the Setup Complete dialog box. To close this window, click Finish.

Backing Up the Mailbox iDataAgent for Exchange 2000 This section describes how to back up the mailbox iDataAgent for Exchange 2000.

Before You Begin To help avoid common installation problems, do the following: ● Check the installation of the mailbox iDataAgent for Exchange 2000. You must have installed the mailbox iDataAgent for Exchange 2000 on the client computer. ● Check that systems are running. Make sure that the client computer is turned on and the CommServe software is running.


To perform an immediate full backup of the default subclient 1. On the Windows taskbar, click the Start button, point to Programs, point to Galaxy, and then click Galaxy CommCell Console for Java GUI. 2. In the CommCell Logon window, log on by entering your Galaxy user name and password. 3. Galaxy displays the CommCell Console window. 4. From the CommCell browser, open Client Computers, and then the appropriate client. Right-click the Exchange 2000 Mailbox icon, and then click Backup Default Backup Set. 5. Galaxy prompts you to confirm that you want to back up all the subclients within the backup set. In this case, because you haven’t defined any other subclients, only the default subclient exists. Click Yes to confirm. 6. In the Backup Options window, click Full, for a full backup, and then click OK. (Regardless of the backup type you select, Galaxy performs a full backup the first time any backup is started.) 7. Galaxy starts a full backup of the Exchange mailboxes and indicates its status in the Job Controller window. The job status should change from Waiting to Running in a few moments. 8. When the backup has completed, Galaxy displays a completion message. Click OK to close the window.

Where to Go From Here Now that you’ve installed Galaxy and run your first backup, you probably want to set up backup schedules, monitor the success of your backups, and configure Galaxy to notify you when significant system events occur. For more information

Chapter 2: Backup and Restore Deployment

83

about these basic administrative tasks, see the topic “Getting Started with iDataAgent Administration” later in this chapter and the Daily Operations Guide.

iDataAgent for SQL Server iDataAgent for SQL Server is the backup and restore vehicle for SQL Server databases. Note: This product only secures the SQL Server databases (system and user databases, for example). To secure SQL Server application files that reside on a local hard drive or file system data that resides on a SQL Server computer, you must use the file system iDataAgent.

Installing iDataAgent for SQL Server This section describes how to install iDataAgent for SQL Server.

Before You Begin To help avoid common installation problems, do the following: ● Review product changes and enhancements. These are provided in the current release notes for iDataAgent for SQL Server. ● Install to a noncompressed drive. Make sure iDataAgent for SQL Server is not installed on a compressed drive. ● Obtain a valid SQL Server logon. You must have the logon name and password of a SQL Server account with system administrator privileges for all of the SQL Server instances that are to be configured; this account is used by iDataAgent for SQL Server. ● Check the SQL Server service account. If the SQL Server service is running using any account other than the local system account, you will need the user name and password of that account. ● Obtain the software. Make sure that you have the Galaxy software CD-ROMs. ● Obtain valid licenses. Ensure that you have enough licenses to install the iDataAgent on each required computer within the CommCell. ● Meet the minimum requirements. The client computer must satisfy the minimum requirements provided in the “Satisfy System Requirements” section of the client Quick Start Guide. ● Check for iDataAgent for Windows 2000. The file system software must be installed on the client computer. ● Verify that CommServe is running. The CommServe computer is turned on and the CommServe software is running.

84

Backup and Restore for Internet Data Center ●

●

●

● ●

Have IP connectivity to the CommServe. If your network does not have DNS lookup or some other name resolution facility, you may be asked to enter the IP address of the CommServe computer. Regarding the firewall: ● Have an appropriate firewall configuration. If your client computer is on the opposite side of a firewall from a CommServe and/or MediaAgent, and the CommServe and MediaAgent have not been configured for firewall support, refer to the Galaxy Pre-Installation Checklist for specific instructions on configuring your firewall. - or ● Configure the client for firewall support. If your client computer is on the opposite side of a firewall from a CommServe and MediaAgent that have already been configured for firewall support, it is only necessary to add the Firewall.svc and Firewall_loc.txt files (as described in the Galaxy PreInstallation Checklist) to your client. After these files are added to your client, you must also add the client name to the Firewall_loc.txt file of your CommServe. Create storage policies. Storage policies must be created for the client, as suggested in the “After You Install a MediaAgent” section of this chapter. Install patches. Ensure that all applicable Galaxy patches have been applied. Create subclient filters. Subclient filters must be created on clusters and any applicable clients.

Note: If the name of the client computer running SQL Server has changed since the SQL Server was installed, run the following stored procedures before installing iDataAgent for SQL Server:

sp_dropserver ‘ oldservername ‘ sp_addserver ‘ newservername ‘, ‘LOCAL’


To install iDataAgent for SQL Server 1. Log on to the client computer as Administrator or as a member of the Administrators group on that computer. The Galaxy software must be installed by a user or by a user who is a member of the Administrators group. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK.

Chapter 2: Backup and Restore Deployment

85

Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. However, the installation will become corrupted unless the drive is actually mapped.

3. On the installation menu, select iDA for SQL Server, and then click Install. 4. Setup checks your Windows user account for the necessary user rights.

5.

6. 7. 8. 9.

If your account does not have the necessary rights, it automatically assigns the required rights to your account and then prompts you to log off and log back on. If your account already has the necessary rights, you will not receive this prompt, and you can proceed to the next step. Setup verifies that the file system client software is installed on the computer. If it is not installed, you will be prompted to install it at this time. For instructions on installing the file system client software, see the CommCell Quick Start Guide. If the iDataAgent for Windows 2000 software is already installed on this computer, you will not receive this prompt.. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications, or click Next to continue. The Galaxy license agreement displays. To continue, you must click Yes and accept the terms of the agreement. In the next dialog box, select the SQL Servers to be configured in the top pane, and then click Configure. A dialog box prompts you to select a storage policy. A storage policy directs backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. Note: You can change the storage policy selection at any time after you install the client software.

10. Enter the SQL Server System administrator account user name (this has an initial

default of sa) and password. This account is a SQL Server account, not a Windows account, and must have the SQL Server system administrator role. Galaxy uses this account to access the SQL Server. 11. Next, enter the user name and password of the Windows SQL Server Account that the SQL Server service is using to run the SQL Server instance being configured. When configuring multiple instances, each instance is treated separately. One instance may use the local system account, while another instance uses a different account.

86

Backup and Restore for Internet Data Center

If the local system is the account being used for this SQL Server instance, this step is skipped. 12. Select a default undo directory path for storing undo files created during restore operations of databases in standby mode. To accept the default location, click Next. To select a different location, click Browse and then select a different location. Note: This folder is used as the default location for undo files, but can be changed during any restore.

13. A dialog box displays a list of databases from the SQL Server instance currently

being configured. Select the databases you want configured by moving the database name to the Selected Databases pane, and then click Next. All databases selected in this step are configured to use the storage policy previously selected. If you want to use different storage policies for any of the available databases, don’t configure them in this step, and then add them by using the CommCell Browser after the installation is complete. For information about adding databases to be secured by Galaxy, see the Client Administration Guide (Microsoft SQL Server). Note: You can change the storage policy associated with any database at any time after the installation is complete.

14. A summary displays the installation options you have chosen. Click Next to

continue or Back to change any option. 15. In the MSSQL Servers dialog box, the SQL Server instance(s) just configured are now listed in the Successfully Configured SQL Servers pane. Click Finish. If you need to configure multiple instances of SQL Server, and there are still other instances left to configure, repeat the previous steps for each selected instance. 16. The system displays the Setup Complete window. To close this window, click Finish. The procedure is now complete. You can now do any of the following: ● Install iDataAgent for SQL Server on another client computer. ● Back up SQL Server databases on the client computer that you just installed; for instructions, see the topic “Backing Up iDataAgent for SQL Server” later in this section. ● Exit the installation menu.

Chapter 2: Backup and Restore Deployment

87

Installing iDataAgent for SQL Server on a Cluster Galaxy software supports the advanced reliability and availability features of a clustering environment for certain applications that can run in a clustered environment (such as iDataAgent for SQL Server). For more information on Galaxy clustering, see the CommServe Administration Guide.

Before You Begin To help avoid common installation problems, you need to: ● Install patch 28. iDataAgent for Windows 2000 must be installed using the Galaxy 3.1.0 GSP1 (build 59) compact disc prior to installing iDataAgent for SQL Server from the patch 28 package. In a clustered environment, install iDataAgent for Windows 2000 to all physical nodes first, and then install to all chosen virtual servers, before using the patch 28 package to install iDataAgent for SQL Server. ● Patch 28 supports SQL Server 7.0 Service Pack 1. Microsoft SQL Server 7.0 with a minimum of Service Pack 1 up to Service Pack 3 or Microsoft SQL Server 2000 with a minimum of Service Pack 0 up to Service Pack 1 must be installed and clustered prior to installing the Galaxy iDataAgent. ● Review product changes and enhancements. These are provided in the current release notes for iDataAgent for SQL Server. ● Install to a noncompressed drive. Make sure iDataAgent for SQL Server is not installed on a compressed drive. ● Obtain a valid SQL Server logon. You must have the logon name and password of a SQL Server account with system administrator privileges (this account is used by iDataAgent for SQL Server) for all SQL Server instances to be configured. ● Check the SQL Server service account. If the SQL Server service is running using any account other than the local system account, you will need the user name and password of that account. ● Obtain the software. Make sure that you have the Galaxy software CD-ROMs. ● Obtain valid licenses. Ensure that you have enough licenses to install the iDataAgent on each required computer within the CommCell. ● Meet the minimum requirements. The client computer must satisfy the minimum requirements provided in the “Satisfy System Requirements” section of the client Quick Start Guide. ● Check for iDataAgent for Windows 2000. The file system software must be installed on the client computer. ● Verify that CommServe is running. The CommServe computer is turned on and the CommServe software is running.

88

Backup and Restore for Internet Data Center ●

●

●

●

●

●

●

●

●

Have IP connectivity to the CommServe. If your network does not have DNS lookup or some other name resolution facility, you may be asked to enter the IP address of the CommServe computer. Regarding the firewall: ● Have an appropriate firewall configuration. If your client computer is on the opposite side of a firewall from a CommServe and/or MediaAgent, and the CommServe and MediaAgent have not been configured for firewall support, refer to the Galaxy Pre-Installation Checklist for specific instructions on configuring your firewall. - or ● Configure the client for firewall support. If your client computer is on the opposite side of a firewall from a CommServe and MediaAgent that have already been configured for firewall support, it is only necessary to add the Firewall.svc and Firewall_loc.txt files (as described in the Galaxy PreInstallation Checklist) to your client. After these files are added to your client, you must also add the client name to the Firewall_loc.txt file of your CommServe. Ensure that all of the nodes are running. Prior to installing the client software, make sure that both the active and passive nodes are available. Cluster service should bind the public network interface card before the private network interface card. Cluster service should have the Microsoft (pre-Service Pack 3) 19425 gethostbyaddress patch applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. Cluster service should have all disk array devices configured with access to the shared array and cluster software installed and running. Create storage policies. Storage policies must be created for the client, as suggested in the “After You Install a MediaAgent” topic earlier in this chapter. Create subclient filters. Subclient filters must be created on clusters and any applicable clients. Install clients in the correct order. The client software installations must be performed in the following order: 1. Install iDataAgent for Windows 2000 onto the active (physical) node. Then install it onto all passive (physical) nodes. (This iDataAgent must be installed on all physical nodes in the cluster prior to attempting any virtual server installations.) Then install iDataAgent for Windows 2000 on any virtual servers. 2. Install iDataAgent for SQL Server for the virtual server on the active node.

Chapter 2: Backup and Restore Deployment




89

To install iDataAgent for SQL Server on a cluster 1. Log on to the client computer (Exchange 2000 server, for example) as Domain User with privileges to all nodes in the cluster. 2. Place the Galaxy software CD-ROM into the client computer’s CD-ROM drive. After a few seconds, the installation menu appears. If the installation menu does not appear: a. On the Windows taskbar, click the Start button, and then click Run. b. Browse to the CD-ROM drive, select SetupGalaxy.exe, and then click OK. Note: You can also install the product by using a mapped CD-ROM drive on another computer on the network. However, the installation will become corrupted unless the drive is actually mapped.

3. Setup prompts you to select a Galaxy software module. Select iDA for SQL

Server, and then click Install. 4. A message states that the physical node is running as a cluster node and prompts you to specify a physical node installation or a virtual server installation. Select Virtual Server, and then click Next. Note: Physical nodes and virtual servers must first have iDataAgent for Windows 2000 installed from the 3.1.0 GSP1 compact disc, before installing the iDataAgent for SQL Server software on to the virtual node from the patch 28 compact disk.

5. A list of virtual servers configured for the node is presented. Select a virtual

server (which is the disk group where your virtual server resides), and then click Next. 6. A dialog box prompts you to indicate whether you have installed iDataAgent for Windows 2000 on all physical nodes. If necessary, exit Setup and do this before proceeding, otherwise click Yes to continue. 7. Setup checks your Windows user account for the necessary user rights. If your account already has the necessary rights, you will not receive this prompt, and you can proceed to the next step. If your account does not have the necessary rights, Setup automatically assigns the required rights to your account and then prompts you to log off and log back on. 8. Setup verifies that the file system client software is installed on the computer. If the iDataAgent for Windows 2000 software is already installed on this computer, you will not receive this prompt.

90

Backup and Restore for Internet Data Center

9. 10. 11. 12.

13.

14.

If it is not installed, you will be prompted to install it at this point. For instructions on installing the file system client software, see the Galaxy CommServe Quick Start Guide. A dialog box prompts you to close any running applications. If necessary, exit Setup and close your running applications, or click Next to continue. The Galaxy license agreement displays. To continue, you must click Yes and accept the terms of the agreement. In the next dialog box, select the SQL Servers to be configured in the top pane, and then click Configure. A dialog box prompts you to select a storage policy. A storage policy directs backup data to a media library. Each library has a default storage policy. Select the storage policy through which you want to back up the default subclient, and then click Next. Enter a user name and password for a Windows account with SQL Administrator rights. This account is not a SQL Server account. It is a Windows account, and it must be a member of the local computer’s Administration group. Galaxy uses this account to access the SQL Server. Click Next to continue. If the local system is the account being used for this SQL Server instance, this step is skipped. If prompted, enter the user account name and password of the Windows SQL Server Account that the SQL Server service is using to run the SQL Server instance being configured. Note: If the local system is the account being used for this SQL Server instance, this step is skipped.

Multiple Instances: In physical nodes, when configuring multiple instances, each instance is treated separately; one instance may use the local system account, while another instance uses a different account. When using virtual servers, you are constrained to only one account. 15. Select a default Undo directory path for storing undo files created during restore operations of databases in standby mode. To accept the default location, click Next. To select a different location, click Browse, and then select another location. This folder is used as the default location for undo files, but it can be changed during any restore. 16. A dialog box displays a list of databases from the SQL Server instance currently being configured. Select the databases you want to configure by moving the database name to the Selected Databases pane. Complete your selections by clicking Next.

Chapter 2: Backup and Restore Deployment

91

All databases selected in this step are configured to use the storage policy you selected previously (in Step 12). If you want to use different storage policies for any of the available databases, do not configure them in this step and add them using the CommCell Browser after the installation is complete. For information on adding databases to be secured by Galaxy, see the Client Administration Guide (Microsoft SQL Server). Note: You can change the storage policy selection at any time after you have installed the client software.

17. A summary displays the installation options you have chosen. Click Next to

continue or Back to change any option. 18. The SQL Servers dialog box displays. The configured SQL Server instance(s) are

now listed in the Successfully Configured SQL Servers pane. Click Finish. If you need to configure multiple physical nodes of SQL Server, and there are still other instances left to configure, repeat Steps 12 through 17 for each selected instance. 19. The system displays the Setup Complete window. To close this window, click Finish. 20. If you are informed at the end of the active node installation that the passive node was not available, select one of the following choices; otherwise continue on to the next step: ● Click Yes to continue with the active installation and update any remaining passive nodes. ● Click No to continue with the active installation and skip updating any remaining passive nodes. You will then need to follow the steps for “Performing a Manual Passive Node” for the node listed in the message. 21. The registry and environmental files are updates on the passive node. When the update is complete, the system displays the Setup Complete window. To close this window, click Finish. 22. The Galaxy installation has a configuration file on the shared drive. To complete the configuration setup, after installing iDataAgent for SQL Server, you must fail over the disk group containing this iDataAgent to the passive nodes at least once, so that the configurations to the passive nodes occur. Note: Do not go on to the other installations before you fail over and create the nodes.

23. Fail back the nodes and then continue with the installation as usual. 24. From the CommCell Console access iDataAgent for Windows 2000. From this

iDataAgent, filter the shared drives from the physical clients (node 1 & node 2), and the local drives from the virtual clients.

92

Backup and Restore for Internet Data Center

The default subclient of the physical iDataAgent automatically backs up the quorum database. If you are using file system backups to back up the quorum database, filter all applications accordingly. This concludes the iDataAgent for SQL Server software installation procedure in a clustered environment. You can now do any of the following: ● Install iDataAgent for SQL Server on another client computer. ● Back up SQL Server databases on the client computer that you just installed; for instructions, see the topic “Backing Up iDataAgent for SQL Server” later in this section. ● Exit the installation program.

Performing a Manual Passive Node Installation This procedure must be used if a passive node failed to update during the installation of the active node. Before You Begin

Please review the items in the checklist “Before You Begin” topic of the “Installing iDataAgent for SQL Server on a Cluster” section in this chapter. In particular you must: ● Install patch 28. iDataAgent for Windows 2000 must be installed using the Galaxy 3.1.0 GSP1 (build 59) compact disc prior to installing iDataAgent for SQL Server from the patch 28 package. In a clustered environment, install iDataAgent for Windows 2000 to all physical nodes first, and then install to all chosen virtual servers, before using the patch 28 package to install iDataAgent for SQL Server.


To perform a manual passive node installation 1. In the registry, create a new string under HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Platform\Virtual_Server_Name\Install (where virtual_server_name is the name of the virtual server). ● For Windows 2000, the string name is Windows2000. ● For the Microsoft Windows NT® operating system, the string name is FSBackup. ● For both platforms, the value is Installed. 2. Repeat Steps 1 through 6 of the previous installation procedure. Then proceed

to the next step. 3. A dialog box acknowledges this to be a passive node, and prompts you to indicate whether you want Setup to update the CommVault environment on the node. Click Yes.

Chapter 2: Backup and Restore Deployment

93

4. Enter the SQL Server system administrator account user name (initial default of

sa) and password. Galaxy uses this account to create the Open Database Connectivity (ODBC) driver entry. 5. The registry and environmental files are updates on the passive node. When the update is complete, the system displays the Setup Complete window. To close this window, click Finish. This concludes the manual passive installation procedure for iDataAgent for SQL Server.

Backing Up iDataAgent for SQL Server In the following procedure, you will perform a backup of an instance, using the SQL Server sample database.

Before You Begin To help avoid common installation problems, do the following: ● Ensure that all software is installed. The iDataAgent for SQL Server software must be installed on the client computer. ● Ensure that all systems are running. The client computer is turned on. ● Install the sample SQL Server database. You must have installed the sample database Pubs included with your Microsoft SQL Server software.


To perform a backup of the Pubs database on the client computer 1. On any computer where the CommCell Console is installed, click the Start button on the Windows taskbar, point to Programs, point to Galaxy, and then click Galaxy CommCell Console for Java GUI. 2. In the CommCell Logon window, log on by entering your Galaxy user name and password. 3. Galaxy displays the CommCell Console window. 4. From the CommCell browser, open Client Computers, open the appropriate client, and then open the SQL Server nodes. Next, open the Instance node where you just installed the iDataAgent. Right-click Pubs, and then click Backup Database. 5. In the SQL Backup Options window, click OK. Regardless of the backup type you select, Galaxy automatically performs a full backup the first time any database is backed up. 6. Galaxy starts a full backup of the Pubs database and indicates its status in the Job Controller window. The job status should change from Waiting to Running in a few moments. 7. When the backup completes, Galaxy displays a completion message. Click OK to close the window.

94

Backup and Restore for Internet Data Center

Where to Go From Here Now that you’ve installed Galaxy and run your first backup, you probably want to set up backup schedules, monitor the success of your backups, and configure Galaxy to notify you when significant system events occur. For more information about these basic administrative tasks, see the section “Getting Started with iDataAgent Administration” later in this chapter and the Daily Operations Guide.

Getting Started with iDataAgent Administration Now that the Galaxy clients are installed and backed up, you are ready to begin basic back up administration. This section introduces you to the user interface and scheduling. Daily administrative tasks are reviewed in the Operations Guide.

Overview of the CommCell Console Please refer to the Galaxy CommServe Administration Guide for more information about the CommCell Console. The CommCell Console is the graphical user interface that allows you to control and manage a Galaxy CommCell. You can use the CommCell Console to initiate a variety of tasks, for example: ● Establish and change configurations of CommCell entities (storage policies, for example) ● Start or schedule backups, restores, or administrative jobs ● Monitor ongoing jobs ● Evaluate success of completed jobs ● Monitor Galaxy system events Multiple remote CommCell Console sessions can be active at one time, so multiple users can access the CommServe simultaneously. The CommCell Console software can be run in the following ways: ● As a stand-alone Java application ● As a Web-based Java applet ● As an MMC Snap-in module All versions of the CommCell Console enable you to access all Galaxy features. There are, however, some distinctions between the MMC Snap-in version and the other two Java versions.

Chapter 2: Backup and Restore Deployment

95

Stand-alone Java Console The stand-alone Java version of the CommCell Console is automatically installed and therefore always available on the CommServe computer. For remote administration, you can also install the CommCell Console application directly on other computers, whether or not they are part of a Galaxy CommCell. Installation instructions are provided in the CommVault Galaxy Quick Start Guide. You can access the CommCell Console application by clicking the Start button on the Windows taskbar, and then pointing to Programs.

MMC Snap-in Console The CommCell Console is available as an MMC Snap-in module and thus provides you with the convenience of managing and controlling the Galaxy CommCell from within the context of MMC. The MMC Snap-in module of the CommCell Console is automatically installed and therefore always available on the CommServe computer. For remote administration, you can also install it directly on other computers, whether or not they are part of a Galaxy CommCell. Installation instructions are provided in the CommVault Galaxy Quick Start Guide. You can access the CommCell Console application by clicking the Start button on the Windows taskbar, and then pointing to Programs.

Web-based Java Applet Console The CommCell Console is also available as a Web-based Java applet. Using a Javaenabled Web browser, you can display the CommCell Console from a remote computer, in a manner similar to that of the application version. In fact, the Webbased version of the CommCell Console has the same basic appearance as the stand-alone version. The Web-based version offers additional flexibility in that you need not install any Galaxy software on the display computer. You need only a Java-enabled Web browser. Note: Remote access may not be available for computers on the other side of an Internet firewall because they cannot access the URL of the CommServe. For more information on this topic, see the Galaxy CommServe and MediaAgent Release Notes.

You can access the CommCell Console as a Web applet by entering the URL of the Galaxy CommServe in your Web browser. The CommServe computer must have IIS installed for this capability. Note: For Web-based access to work, the CommServe must be properly configured. For additional details, see the Galaxy Pre-Installation Checklist and the Galaxy CommServe Quick Start Guide. Also, you can enable Web browse support manually for the Windows NT or Windows 2000 CommServe, as described in the CommServe Administration Guide.

96

Backup and Restore for Internet Data Center

Starting the CommCell Console This section describes starting the CommCell Console.

MMC Snap-in Version The Galaxy CommCell Snap-in is available to be used as a part of any MMC-based tool. Provided with your Galaxy installation is a sample tool created with Galaxy’s CommCell Snap-in. This tool has examples of task pads and other capabilities provided by MMC. The Single Sign-on option allows you to start the MMC Snap-in without entering your user name and password. You can do this after your Windows logon account is authenticated (that is, after you are logged on to your Windows system) and as long as your user account is also configured in the CommServe Users Database. If your account is not configured as such, you must start the MMC Snap-in by entering your user name and password.


To start the Java version of the CommCell Console 1. On the Windows taskbar, click the Start button, point to Programs, point to Galaxy, and then click Galaxy CommCell Console for JAVA GUI. The CommCell Logon Information window appears. At the bottom of the window, a brief “Retrieving list of CommCells...” message displays. If CommCell Plus is installed, a list containing the names of the available CommServes and a brief “List of CommCells retrieved...” message display. 2. In the CommCell Logon Information window, type your CommCell user name and password. Then, if CommCell Plus is installed, select the CommCell that you want from the drop-down list. 3. Click OK. In a few moments, the CommCell Console appears, and is now ready for use. Note: If the CommCell Console does not start, check that the Galaxy services on the CommServe computer are running. For more information about Galaxy services, see Chapter 5, “Galaxy Service Control Manager,” in the CommServe Administration Guide.

Web-Based Applet The following procedure describes how to run the CommCell Console (Java version) as a Web-based applet. Before You Begin

To help avoid common problems you need to: ● Obtain a valid Galaxy account. To log on to the Galaxy CommCell, you must have a Galaxy user account. If you need an account, contact your Galaxy administrator.

Chapter 2: Backup and Restore Deployment ●

●

●




97

Obtain the CommServe URL. You need the URL of the Galaxy home page on the CommServe computer, by default, http://CommServe_name/Galaxy. For URL information, contact your Galaxy administrator. Use a Java-enabled browser. Your Web browser must be capable of running Java applets and be Java-enabled. Also, Java version 1.3 or later is required. Correctly configure the CommServe. To support Web access, your CommServe must be properly configured. This configuration is performed during CommServe installation. For details, see the Galaxy Quick Start Guide.

To run the CommCell Console as a Java Web Applet 1. From any computer on the network, open a Java-enabled Web browser. 2. Type the URL of the CommServe in the browser. By default, the URL is http:// CommServe_name/Galaxy. Note: If this is your first time accessing the CommServe from this computer, you may need to install the Java plug-in software. For specific instructions on downloading and installing the plug-in, see the “To install the Java Plug-in” section of the CommServe Administration Guide. After you have installed the plug-in, continue with the next step.

Tools Menu

The Tools menu has the following commands: • CommCell Browser. This command presents all objects in the CommCell in a tree structure. The objects are displayed under the following categories: Client Computers, MediaAgents, CommCell Users, CommCell User Groups, and Storage Policies. The browser is divided into two panes: the left pane displays the Galaxy CommCell tree and the right pane displays detailed information about the CommCell object that is selected in the left pane. • Backup Controller. This command provides a simplified view of the CommCell browser, showing only the client computers and related objects. This view is optimized for performing backup-related operations only. • Restore & Browse. This command allows you to browse and restore the CommCell’s backed up data. • Job Controller. This command displays information about running Galaxy operations (backups, restores, and so on). You can end, suspend, or resume a job by using this controller. For more information about the Job Controller, see Chapter 6, “Job Management,” of the CommServe Administration Guide. • Scheduler. This command allows you to view scheduled jobs (backups, restores, and auxiliary copies, for example) and change their schedule. • Event Viewer. This command displays events from the Galaxy Event Log. Each event contains information about a Galaxy process, which can be filtered, as an

98

Backup and Restore for Internet Data Center

• •

•

option. For more information about the Event Viewer, see Chapter 7, “Galaxy Event Viewer,” in the CommServe Administration Guide. Reports. This command allows you to generate a report. Library & Drive Configuration. This command allows you to configure all storage devices within the CommCell and display all configured devices in the CommCell. NAS Client Configuration. This command allows you to configure a NAS client.

The MMC Snap-in version of the CommCell Console provides the same capabilities as the Java-based Galaxy CommCell Console. These include CommCell Plus, which is discussed in the “Starting the CommCell Console (Java version)” section of the CommServe Administration Guide. There are some variations in appearance, but the functionality is the same. The most notable differences in appearance are the locations of the Job Controller and Event Viewer, as well as all functionality being accessed by using the right-click, context-sensitive menus. CommCell Plus on the MMC Console works only if the computer on which the Console is installed is a member of a Windows 2000 Active Directory domain.

Installing for CommCell Plus If you are planning on using the CommCell Plus feature that allows you to log on to any CommServe computer on your network, note the following: ● The Java version of the CommCell Console fully supports the CommCell Plus feature. ● The MMC Snap-in version of the CommCell Console supports the CommCell Plus feature only if the Console is installed on a computer that is a member of an Active Directory enabled domain. The CommCell Plus feature is not available if you are accessing a CommCell Console by using the Galaxy console Java applet. ● To support CommCell Plus, your computer must be a part of a Windows 2000 Active Directory enabled domain. ● Even if the computer is running Windows 2000 and is a member of an Active Directory enabled domain, you may still receive a message stating that this CommServe has not been made a part of CommCell Plus. If you receive this message, click OK to continue the installation. ● When the installation is complete, click the Start button on the Windows taskbar, click Run, and then enter the following: RegEvMgrsWithAD –c

Chapter 2: Backup and Restore Deployment

99

Administration Using the CommCell Snap-in This section describes the methods in which the CommCell Snap-in can be used to administer your CommCell.

Before you Begin To log on to the Galaxy CommCell, you must have a Galaxy user account. If you do not have a Galaxy user account, contact your Galaxy administrator. Note: Before you start the CommCell Console, make sure that Galaxy services are running on the CommServe. Otherwise, the CommCell Console will not run. For details, see Chapter 5, “Galaxy Service Control Manager,” in the CommServe Administration Guide.


To start the sample MMC tool 1. On the computer where Galaxy’s MMC Snap-in has been installed, click the Start button on the Windows taskbar, point to Programs, point to Galaxy, and then click Galaxy CommCell Snap-in for MMC. (For information about installing the Galaxy CommCell Snap-in for MMC, see the Galaxy Quick Start Guide.) 2. In the Connect to CommCell window, continue by using the instructions in the appropriate bullet item that follows: ● If the Use Windows User Name field is selected, the User Name and Password fields are unavailable; this indicates that you may have the single sign-on option described earlier. If multiple consoles are available from the CommCell drop-down box (indicating CommCell Plus capability), select the appropriate CommCell. Otherwise, type the appropriate CommCell name (if necessary). Then click OK. If this does not start the MMC Snap-in, you receive an error message; if this happens, try the procedure in the next bullet item. Otherwise, go to the next step. ● Select the Use CommCell authentication field. Then, if multiple consoles are available from the CommCell drop-down box (indicating CommCell Plus capability), select the appropriate CommCell. Otherwise, enter the appropriate CommCell name (if necessary). Finally, type your user name and password and click OK. For example: User: cvadmin Password: cvadmin. 3. In a few moments, the MMC appears, and the Galaxy CommCell Snap-in will be

ready for use.

Setting Up the ExpressRecovery Account CommServe ExpressRecovery is a Galaxy feature that secures the Galaxy metadata on the CommServe computer. After installing the CommServe software, you need to identify the Windows user account under which CommServe ExpressRecovery backups are to be conducted. In order for ExpressRecovery backups to work successfully, the specified Windows account must be a domain administrative account

100 Backup and Restore for Internet Data Center

for the domain containing the ExpressRecovery backup destination directory. Also, Galaxy’s SQL Server account needs to be a system account dedicated to the Galaxy application.


To specify the ExpressRecovery account 1. On the Windows taskbar, click the Start button, point to Programs, point to Galaxy, and then click Galaxy CommCell Console for Java GUI or Galaxy CommCell Console for MMC GUI. 2. In the CommCell Logon window, log on as Cvadmin, with a password of Cvadmin, and then click OK. 3. In the CommCell browser, right-click the CommCell node (the top-most object in the CommCell browser, for example), and then click Properties. 4. On the ER Backup tab of the CommCell Properties window, click Change. 5. In the Change User Account dialog box, type the user name and password of the Windows user account under which you want the ExpressRecovery backups conducted. Type the password a second time to confirm it, and then click OK. 6. After specifying the Windows user account, you should start an ExpressRecovery backup. In the CommCell Browser, right-click the CommCell node, and then click ExpressRecovery Backup. 7. Check the status of the operation by using the Galaxy Event Viewer.

Setting Up the ExpressRecovery Subclient Backup These steps are performed after a MediaAgent with a tape library is installed. In the case of disaster where your magnetic CommServeER is lost, you need to retrieve the data from tape quickly to rebuild the CommServe and recover the enterprise. Creating a subclient that contains only the data of the CommServeER backup is the first step in a successful disaster recovery plan. After the subclient is created, the second step is to schedule the subclient to back up one hour after the magnetic CommServeER backup is performed. The final step is to note the barcode of the media that contains this critical data. In the case of disaster, you will be prepared to use Galaxy’s DRRestoreGUI.exe to easily index and recover the CommServeER data. DRRestoreGUI.exe information is provided in the Advanced Operations Guide.


To create an ExpressRecovery subclient 1. From the CommCell browser, right-click the client that contains the CommServeER backup. This is the client on which you designated CommServeER backup data to reside (see the “Installing the CommServe Software” section above).

Chapter 2: Backup and Restore Deployment 101

Note: If you do not have the information, review your settings provided in CommCell node (that is, the top-most object in the CommCell browser), and then click Properties. The client name is listed in the UNC path. From the ER Backup tab of the CommCell Properties dialog box, view the UNC path for CommServeER.

2. Expand the tree, and then right-click Default Backup Set. 3. From the short-cut menu, click New Subclient. 4. In the Subclient Properties dialog box, click the General tab. In the Name box,

5.

6. 7. 8.

type Subclient CommServeER or CSER (something you will recognize in the backup history as the subclient containing CommServeER data). Click the Contents tab, and in the Enter New Content field, type the path to the CommServeER data (for example C:\CommServeER). Optionally, you can use the Browse button to locate the content. In the Subclient Properties dialog box, click the Storage Device tab, and then click CSER Storage Policy on the Storage Policy pull-down menu. Click OK to create the subclient. Perform and confirm the immediate backup: a. From the CommCell browser, right-click the CSER, and then click Backup. b. From the window, select Full for the backup type, and then click OK. You can track the progress of the backup operation from the Job Controller window. c. When the backup is complete, browse the backup data to confirm it contains the data you expected.

You can also choose to restore the data for further confirmation. This should be part of your disaster recovery plan.


To restore the data 1. From the CommCell browser, right-click the CSER, and then click RestoreFiles/ Folders. 2. Click OK to allow the defaults of browsing the most recent date. 3. Expand the tree to view the data structure of the backup. Restoration of data is included in the “Disaster Recovery” section of Chapter 4, “Advanced Backup and Restore Operations.” You are now ready to note the tape that your backup is stored on. For additional security, you should export this media for offsite storage on a schedule basis. For information about exporting tapes, see the “Exporting Media” section of Chapter 4, “Advanced Backup and Restore Operations.”

102 Backup and Restore for Internet Data Center


To view the barcode of the tape on which the CommServeER subclient is stored 1. From the CommCell browser, right-click the CSER subclient or backup set, and then click View Backup History. 2. Right-click the most recent backup of the CSER subclient, and then click View Media. 3. Note the barcode for the CSER backup. If this tape is needed in the case of disaster recovery, knowing the barcode will save hours of cataloging tapes. The CommServeER data has been backed up to tape and the barcode of the tape has been noted. You are now ready to schedule the subclient to back up.




To schedule the CSER subclient backup 1. From the CommCell browser, right-click the CSER subclient, and then click Backup. 2. From the window, select the backup type Full. 3. Select Schedule. 4. Schedule the backup to perform daily, selecting the time of 6:00 P.M. (one hour after the default time that CommServeER backup to magnetic is performed). You have completed the CommServe installation. Continue to the next section to install the MediaAgent software.

Scheduling Backups Backup strategies are determined in the planning phase prior to installation. Now that the enterprise clients have been installed, all clients can now be scheduled for backup from a single point, the CommCell console. When to Schedule Backups

A backup, like any other process, consumes system resources. The extent to which any given backup affects other applications depends on several factors: ● Amount of data to be backed up ● Processing power of the client computer ● Compression mode of the backup ● Number of other backups occurring for the same client computer It is suggested that you schedule regularly occurring backups for times of low system utilization. For example, you may want to avoid backing up during office hours. If backup data must travel across a network to reach the destination library, scheduling backups during off-peak hours can be even more important because launching many backups simultaneously could diminish network responsiveness. The extent, if any, to which network responsiveness is degraded depends on a number of issues, including the quantity of data being backed up concurrently, the capacity of the network, network configuration, and so on.

Chapter 2: Backup and Restore Deployment 103

It is often prudent to distribute the scheduled backups in a CommCell over some period of time in order to avoid media drive and media group contention. The length of time for any particular CommCell depends on the amount of data to be backed up and the specific configuration of the CommCell with respect to libraries and storage policies. If the number of media drives is small compared with the number of subclients in the CommCell, drive contention can occur. If the number of storage policies is small compared with the number of subclients or if a specific storage policy is the target of many subclients, media group contention can occur. If either condition occurs, backups will queue until the needed resource becomes available. Consequently, backups may extend beyond the backup window that was intended for the CommCell. How to Schedule Backups

Scheduling the jobs within your CommCell helps ensure that the data that you want to safeguard is secured automatically on a regular basis. Designing Backup Schedules

Backups can be scheduled from either the Schedule Wizard or the CommCell browser. Within the CommCell browser, you can schedule backups at various levels in the browser tree by right-clicking the entity that you want to back up and then selecting the appropriate menu options. If your iDataAgent supports backup sets, you can schedule a backup for either a subclient or an entire backup set. Scheduling at the backup set level provides the convenience of scheduling all subclients in one step. When establishing a backup schedule for an entire backup set, keep in mind that each subclient initiates a backup at the scheduled time. If two or more subclients are associated with the same storage policy, their backups may run serially. That is, it is possible that one subclient will back up at the specified time, but that the other(s) will queue until the storage policy is free. Depending on the iDataAgent, Galaxy allows you to schedule some or all of the following: ● Full backups ● Incremental backups ● Differential backups ● Synthetic full backups ● Preselected backups (the exact type of a preselected backup depends on your selection during iDataAgent installation)

104 Backup and Restore for Internet Data Center Before You Begin

To help avoid common problems you need to: ● Use an effective backup cycle. When you create a backup schedule, you will most likely establish a full backup cycle. Try to ensure that the backups that comprise a full backup cycle are complementary. For example, if a schedule calls for daily incremental backups with full backups to occur every week, make sure that the incremental backup skips the day that the full backup is scheduled to run, avoiding unnecessary backups and collisions. ● Consider storage retention periods. If you are scheduling backups to establish a full backup cycle, keep in mind that the full backup cycle should be reflective of the associated retention period. For those iDataAgents that support backup sets, if you are scheduling for an entire backup set, you should consider the storage policy retention periods for all constituent subclients. ● Minimize media and network usage. If your CommCell has several client computers, try to coordinate your backups to minimize media, media drive, and possible network contention. ● Use appropriate backup schedules. To secure all data for a given iDataAgent on a client computer, be sure to define backup schedules either for all subclients within the iDataAgent or for a backup set (if backup sets are supported). ● Check the backup timeframe. Check if an operational window has been established for the type of backup operation that you want to schedule. If an operational window exists, be sure to schedule the backup within the valid time frame. ● Enable backup. Ensure backup activity is enabled.

Adding, Modifying, and Deleting Scheduled Jobs Jobs can be scheduled from either the Schedule Wizard or the CommCell browser. Within the CommCell browser, you create a scheduled job by right-clicking the entity (subclient or backup set, for example) for which you want to schedule a job, and then selecting the appropriate backup or browse/restore options. The following procedure tells you how to access the Schedule Wizard, which you can use to schedule backup, restore, or administrative jobs.


To add a scheduled job ● In the CommCell browser, click the Tasks menu, and then click View Schedules. ● To add: In the dialog box that appears, click Add. A Schedule wizard appears to guide you through the process of scheduling a backup, restore, or administrative job. ● To modify: Select the job you want to reschedule, and then click Edit. ● To delete: Select the job you want to remove from the schedule, and then click Delete. To confirm the deletion, click Yes in the message that appears.

Chapter 2: Backup and Restore Deployment 105

Scheduling Reports Reports are detailed in Chapter 4, “Advanced Backup and Restore Operations,” in this documentation series. Now that client backups have succeeded and are scheduled, reports should be scheduled for ease in daily administration. Selecting Users and Scheduling Reports Note: Scheduling reports use the same mail server as Alerts.

Each of the report types discussed in the previous sections allows you to do the following: ● Select the users who will receive the reports. ● Schedule reports for specific times (for example, daily, weekly, monthly, and so on). To select users for and schedule any report type, do the following: 1. Click the Reports icon. 2. In the dialog box for the appropriate report, click Schedule. The Select the Users dialog box appears. 3. Include the users who will receive the reports in the Users to be Notified field. To move a user name from the Available Users field to the Users to be Notified field, select the name in the former field and then click button. e. Click OK to confirm the users to be notified. f. Click OK. Your configuration is set. 3. Configure the No Spare Media Alert:

In the CommCell tree, right-click the CommCell icon and click Properties. Scroll down the Alert column to the Tape section. In the Event column find No Spare Media. Click Edit and select the user to be added to the Users to be Notified list by clicking the < button. To remove a user from the Users to be Notified list, click the > button. e. Click OK to confirm the users to be notified. f. Click OK. Your configuration is set.

a. b. c. d.

4. Configure the Spare Media Low Alert:

a. In the CommCell tree, right-click the CommCell icon and click Properties. b. Scroll down the Alert column to the Library section. c. In the Event column, find Spare Media Low.

112 Backup and Restore for Internet Data Center

d. Click Edit and select the user to be added to the Users to be Notified list by clicking the < button. To remove a user from the Users to be Notified list, click the > button. e. Click OK to confirm the users to be notified. f. Click OK. Your configuration is set. Note: Spare Media Low Alerts are only available when a media library has been configured.

Managing Backups The Galaxy system supports Full, Incremental, or Differential backups. These backups can either be scheduled or manually initiated.

Full Backups Backups for any client start with a full backup. The full backup becomes a baseline to which subsequent incremental and differential backups are applied. A full backup is a backup of all of the database elements allocated to a subclient. It is essentially a snapshot of the subclient. If the database elements are divided between two subclients, each subclient requires a full backup to back up the entire database on that client.

Incremental Backups An incremental backup is a backup of only those portions of the database that have changed since the last backup. It is essentially a backup of the database transaction logs. On average, incremental backups consume far less media and place less of a burden on resources than full backups.

Differential Backups A differential backup contains only those changes that have occurred since the most recent full backup. Like incremental backups, differential backups generally consume less media and place less of a burden on resources than full backups.

Comparing Full, Incremental, and Differential Backups The backup scheme for an iDataAgent can include more than one type of backup. You may choose either full and incremental backups or full and differential backups, depending on your data security needs and preferences, but you cannot mix types. Full backups always back up all of the data that is assigned to a given subclient.

Chapter 3: Basic Backup and Restore Operations 113

While full backups are sometimes necessary (to establish a backup baseline), they are the least efficient form of backup because they back up all data and therefore take the longest time to complete (but they are the quickest to restore). Incremental backups generally back up the least amount of data and are the most efficient form of backup. Differential backups, on average, are somewhere between the two. They tend to back up more data than incremental backups, but less than full backups. Incremental backups are more efficient than differentials from a backup perspective. However, differential backups can increase restore efficiency. Each time a backup occurs, the data is written to an archive file on the backup media. Since each incremental backup produces an archive file, the backup data for a given subclient instance tends to be distributed among different archive files. In differential backups, however, all the changed data resides in one (that is, the latest) archive file. From a restore perspective, this storage protocol can be important, particularly if you want to restore a large amount of data. Conclusions on Incremental and Differential Backups

Incremental and differential backups each have their own advantages. Incremental backups: ● Back up less data than differential backups. ● Consume less media than differential backups. ● Take less time to complete than differential backups. ● Result in lengthier restores than differential backups do, particularly when large amounts of data are involved. Differential backups: ● Back up more data than incremental backups. ● Consume more media than incremental backups. ● Take more time to complete than incremental backups. ● Result in faster restores than incremental backups, particularly of large amounts of data. Differential backups are cumulative and get larger in succession as additional databases change over time. This can introduce problems in the backup strategy of subclient instances where the proportion of data that changes is high. Under these conditions, the size of the differential backup can rapidly approach the size of a full backup. In such cases, you may want to revisit your backup strategy and run full backups more frequently.

114 Backup and Restore for Internet Data Center

Synthetic Full Backups Synthetic Full backups enable you to do a full backup to new media without involving the client. It is a restore-to-backup function that consolidates your previous backups onto a new tape. Be aware that a Synthetic Full backup does not collect any data from the client and, as such, is not a substitute for your normally scheduled backup. If you schedule a Synthetic Full backup followed immediately by a normal full backup to new media you can isolate a full backup on a single set of tape(s) for export and offsite storage. Restoring requires you to specify a point-in-time between the last backup before the synthetic full and the time of the synthetic full backup.

Scheduled Backups Scheduled backups provide a convenient means of backing up data without user intervention. You can establish backup schedules for each subclient using the CommCell Console. When scheduling backups, you need to establish a backup schedule for each subclient or backup set level. A backup schedule may contain a full backup and one or more incremental or differential backups.

Storage Policies Storage Policies act as the primary conduits through which data is backed up and restored. A Storage Policy forms the primary logical entity through which a subclient instance is backed up. Its chief function is to map backup data to a physical backup medium. The Galaxy system provides a default Storage Policy for each media library or stand-alone drive. When file system subclient instances are created, Galaxy automatically associates each to one of the default storage policies. You can, however, define any number of additional storage policies to: ● Tailor the backup attributes to your needs ● Send the backup data to another library ● Provide for parallel backups A Storage Policy has user-configurable parameters that you can use to tailor the Storage Policy’s operation to meet your specific needs. These parameters include security, data streams, copy names, retention criteria, scratch pools, and drive pools. Retention parameters are dynamically applied, which means that if a retention time was previously set to infinite, you can change it to a lesser value and all existing backup sets adjust to the new value. Doing so allows you to alter retention parameters to dynamically prune backup data.

Chapter 3: Basic Backup and Restore Operations 115

Media Contention Within Removable Media Groups When you direct the backups from different subclients to the same Storage Policy, you increase the likelihood of resource contention for those Storage Policy copies that are associated with removable media libraries. A media group can support one operation at a time. As a result, backups or restores that access the same Storage Policy at the same time may actually be performed serially. This is particularly true if the corresponding Storage Policy is configured to provide only one data stream. Removable media contention tends to lessen as the number of configured streams increases. Even so, because a given backup can use any stream, it is possible that the backup data for different clients could, over time, be written to the same stream, and thus to the same tapes. Consequently, removable media contention can arise when backing up or restoring data to different clients that share the same Storage Policy. The Galaxy system does not compel you to consolidate the data of different subclients or client computers within the same Storage Policy. To avoid the effects of media contention, you may want to create additional storage policies.

Galaxy Storage Policy Configuration Terminology The following terms are used in the configuration of Galaxy Storage Policy. Copy Names

Storage Policies provide a named entity (up to 32 characters), and defining attributes, to which backup data is deposited and managed. A Storage Policy can have one or more Copy Names (up to 32 characters) associated with it. Galaxy automatically creates the first (primary) copy name when you create the Storage Policy. All backup data from the subclient is deposited to the primary copy. Using New Copy Name, you can create any number of additional media backup copies called secondary copies. These secondary copies can be synchronized with the primary copy through the Auxiliary Copy operation. When Auxiliary Copy is executed for a Storage Policy, each secondary copy is updated (synchronized) in a precedence order with backup data from the primary copy. This update is a backupmedia–to-backup-media data movement that does not involve the client. Any synchronized secondary copy can be promoted to a primary copy, as long as a backup/restore operation is not in progress. When executing restores, you are given a choice of which of these media copies to retrieve data from. This allows you to easily avoid a bad media copy when you need to restore data quickly. Each Storage Policy Copy Name has its own set of attributes. Storage Policy attributes define the how, where, and when of managing backup data. In using Storage Policy copy names, you can back up the same data to different MediaAgents. This feature allows Galaxy to easily support backup-data redundancy by providing you with the ability to back up identical copies of data to

116 Backup and Restore for Internet Data Center

different media libraries. The following storage-policy attributes should be defined for each copy name: ● Library. This term is used by Galaxy to refer to all storage devices within the CommCell. Examples of storage devices include tape libraries and magnetic disk media, both of which may be displayed as libraries by Galaxy. ● Drive Pool (removable media library only). A drive pool is defined as a logical arrangement of drives. Drive pools allow the drives in a single library to be shared by multiple MediaAgents. ● Number of Streams. You need to specify the maximum number of concurrent streams you want the Storage Policy-Copy Name to support. Each data stream uses one media drive. Understand that multi-streamed storage policies can only be assigned to a subclient whose iDataAgent supports multiple streams. ● Retention Time. This specifies the minimum number of days that you want to retain the data. Backup Sets can be pruned, and media recycled to the scratch pool, when this criterion and the Retention Cycles criteria have been met. This attribute can be dynamically changed at any time to facilitate media management. Archive Pruning operations have to be scheduled or manually initiated. Data Retention Time is not automatically determined, and must be set before Archive Pruning will run. ● Retention Cycles. This specifies the minimum number of cycles that you want to retain. Each backup cycle starts at a Full backup or equivalent as defined by the iDataAgent, and may contain any number of incremental or differential backups. This attribute can be dynamically changed at any time to facilitate media management. As noted earlier in this chapter, Archive Pruning operations must be scheduled or initiated manually, but in this case, data Retention Cycles are then automatically set. Scratch Pool (Removable Media Library Only)

A scratch pool is a repository of new or recycled media that is available for use. In Storage Policy configuration, the scratch pool field specifies the name of the scratch pool from which the Storage Policy-Copy Name will obtain and return media. This attribute can be dynamically changed at any time to facilitate media management. Hardware Compression

If enabled, hardware compression is used for the Storage Policy-Copy Name. Enabling hardware compression overrides the subclient software compression setting. Hardware compression can give you faster performance and fewer CPU demands on the client/MediaAgent, but it also means more traffic across the data path in both directions. It also uses a device-specific compression algorithm, which could cause problems when an attempt is made to restore data using a different manufacturer’s drive.

Chapter 3: Basic Backup and Restore Operations 117

Software Compression

If hardware compression is not enabled, software compression may be used. Software compression on the client reduces network traffic in both directions and uses a device-independent compression algorithm. However, it does put more loading on both the client CPU and the MediaAgent CPU. This last issue may negate almost all the benefits gained from reduced network traffic. MediaAgent software compression does not reduce network traffic during backups but does reduce it during restores. There is less client-side CPU loading during restores than during backups; therefore, MediaAgent software compression may be a good choice if you have a powerful MediaAgent. Technical Notes on Compression

Galaxy has hardware-compression and software-compression features. Hardware compression is performed on supported tape drives and is configured in Galaxy (CommCell Console) at the Storage Policy. Software compression is configured and performed for either Compress on Client or Compress on MediaAgent. Selection. Where software compression takes place is part of the subclient configuration, found under Properties and Advanced Features, and is allowable only if hardware compression is set to Off. Default settings for both hardware and software compression is initially set to Off. Software compression creates a performance hit on the CPU that is running it (Client or MediaAgent). Software compression at the client will increase CPU cycles on the client system during backup operations but has the benefit of decreasing the overall network traffic between the client system and MediaAgent. Software compression at the MediaAgent increases CPU cycles on the MediaAgent system during backup operations also. The benefit of decreased network traffic is not realized with this option. However, if several client workstations have software compression configured for the same MediaAgent and simultaneous backups are started, the MediaAgent will show signs of performance degradation. Therefore, it is advisable to configure software compression on the MediaAgent only for client systems that are mission critical and cannot afford the performance degradation. An alternative to using software compression on the MediaAgent may be to use hardware compression, which disables software compression completely. Hardware decompression occurs at the tape drive and is automatic for data that was compressed using hardware during backup. All software decompression is performed at the client system, regardless of where it may have been compressed. If client data is software-compressed on the MediaAgent during backup, it is still uncompressed at the client during a restore operation. Software decompression has less impact on the client during restore operations than compression would have during backups.

118 Backup and Restore for Internet Data Center

To see where compression is taking place during a backup, look in the Cvd.log on the client and search for CompressType or CompressWhere. Refer to Table 3.2 to decode the results; for example, CompressType=0, and CompressWhere=1 means software compression is talking place at the MediaAgent. Note that Hardware Compression and No Compression display the same type (that is, 2), meaning that software compression is off. Table 3.2: Compression Log Values CompressType

CompressWhere

Software Compression at the Client

0

0

Software Compression at the MediaAgent

0

1

Hardware Compression

2

2

No Compression

2

2

Which compression you use depends on the processing power of the client and MediaAgent, and the available bandwidth between the two. If you are the user, select Hardware Compression to start with and then test the alternatives once your backup implementation is up and running.

Creating a Storage Policy Before performing the following steps, it is recommended that you read “Media Contention Within Removable Media Groups” and Galaxy Storage Policy Configuration Terminology” earlier in this chapter.


To create a Storage Policy 1. In the CommCell Browser, right-click the Storage Policies icon and select New Storage Policy. 2. You should now see the Storage Policy Wizard welcome window. Click Next to continue. 3. In the Storage Policy Name field, enter Storage Policy name and click Next. 4. In the Primary Copy name field, enter primary copy name and click Next. 5. Select the library to which you would like to associate the primary Storage Policy copy and click Next. 6. If you are not working with a removable media library, skip to step 8. Otherwise, select the drive pool that you would like to associate with the Storage Policy and click Next. 7. Choose a scratch pool for the primary Storage Policy copy and click Next to continue.

Chapter 3: Basic Backup and Restore Operations 119

8. In the dialog box set the Number of Streams to 1, and configure the Retention

Time to 7 days and 1 cycle. The retention time is set to infinity by default. Once you have configured these settings, click Next to continue. 9. If you are not configuring the Storage Policy to removable media, skip to step 10. Otherwise, you will now be prompted to select whether or not you want to enable hardware compression on the storage device. Leave the box cleared and click Next to continue. 10. You will now be prompted to confirm the settings that you have chosen for your Storage Policy. Verify that the settings are correct and click Finish. Your new Storage Policy should now be listed in the CommCell Browser.

View Scheduled Jobs for a Specific Storage Policy Galaxy allows you to view scheduled jobs that are assigned to each Storage Policy. Having this feature allows you to see the demands that are being placed on each Storage Policy’s resources.


To view the jobs assigned to a Storage Policy 1. In the CommCell Browser, expand the CommCell root until the desired Storage Policy is shown. Right-click the Storage Policy and select View Schedules. You would then see the Scheduled Jobs window. 2. The Schedule Jobs window provides details about each scheduled job assigned to the Storage Policy. New jobs can be scheduled at this time by clicking Add to launch the Schedule Wizard.

Deleting Storage Policies A Storage Policy cannot be deleted if it is associated with a subclient. Before attempting to delete a Storage Policy, you must either delete each subclient assigned to the Storage Policy, or associate the subclients attached to the Storage Policy with another Storage Policy. Once a Storage Policy is deleted, any data that had been associated with the Storage Policy will no longer be available for restore. All media that the Storage Policy was assigned to will immediately be available for pruning. Reasons for deleting a Storage Policy may include the following: ● Data that was backed up through the Storage Policy is no longer needed ● No backup data is currently assigned to the Storage Policy and there are no plans for future backups involving the Storage Policy


To delete a Storage Policy 1. In the CommCell Browser, expand the CommCell root until the desired Storage Policy is listed. Right-click the desired Storage Policy and select Delete. 2. You are warned in the confirmation box that once you delete the Storage Policy, any data backed up using the Storage Policy will not be available for restore.

120 Backup and Restore for Internet Data Center

Creating Subclients Subclients are used to back up different portions of the file system on a client computer. Initially, the Galaxy system defines a default subclient for each backup set. At that time, the default subclient contains the entire file system and the system state. If you define other subclients within the same backup set, then the default subclient contains the entire file system except for those portions that have been assigned to the other subclients. When you define a subclient, you need to: ● Provide a subclient name. ● Define the content of the subclient. ● Associate a Storage Policy to the subclient. You enter this information using the Subclient Properties dialog box. Although this information alone is sufficient to declare a subclient, you can choose to establish other subclient properties as well. For example, you can: ● Create a backup filter ● Select the subclient’s data compression scheme ● Declare backup-triggered processes

Creating a New Subclient Within a Backup Set It is important to note that you should not create a subclient while the parent backup set or any sibling subclient is backing up.


To create a new subclient within a backup set 1. In the CommCell Browser, right-click the backup set for which you want to create the subclient, and then click New Subclient from the shortcut menu. 2. Click the General tab of the Subclient Properties dialog box and type the name (up to 32 characters) of the subclient that you want to create. The system state backup is only triggered on the default subclient. 3. Click the Content tab, and in the Enter New Content field type the Subclient’s content. Optionally, you can click Browse to enter the content. 4. When specifying a UNC data path, click As User and enter the user account information for the domain user with permissions for that path. 5. Click the Storage Device tab of the Subclient Properties dialog box, then select a Storage Policy you want to associate with this subclient from the Storage Policy pull-down menu.

Chapter 3: Basic Backup and Restore Operations 121

Renaming a Subclient You can rename any user-defined subclient at any time. However, Galaxy does not allow you to rename a default subclient. You should not rename a subclient that is being backed up. 1. In the CommCell Browser, right-click the subclient that you want to rename, and then on the shortcut menu click Properties. 2. On the General tab of the Subclient Properties dialog box, in the Subclient name field type the new name, and then click OK. The CommCell Browser updates the subclient with its new name.

Changing the Content of a Subclient The portion of a file system that is assigned to the subclient is called the subclient content. You can view and change the content of any subclient from the tab of the Subclient Properties dialog box. You should not change the content of the default subclient from its initial setting (that is, \). This setting ensures that the default subclient contains all portions of the file system that are not contained by other subclients. If you change the setting to a different path, then the default subclient will only back up the data pertaining to that path, and the file system will no longer be backed up in its entirety by the subclients within the backup set. It also important not to change the content of a subclient that is being backed up.


To change the content of a subclient 1. In the CommCell Browser, right-click the subclient whose content you want to change, and then on the shortcut menu click Properties. 2. Click the General tab of the Subclient Properties dialog box. 3. To include a file or folder in the content of the subclient, do one of the following: a. In the Enter New Content field manually enter the path (including the drive letter) of the file or folder that you want to add and click Add. Repeat this step if you want to add more files and/or folders to the content. b. Clicking Browse to browse and select the path. In the Browse window, expand the file system of the client computer, click the file or folder that you want to include, and then click Add. Repeat this step for each additional entry. c. To specify a UNC data path, click As User, and enter the user account information for the domain user with permissions for that path. 4. To save your content changes, click OK on the Content tab of the Subclient

Properties box.

122 Backup and Restore for Internet Data Center

Performing On-Demand Backups Backups are one of the primary functions of the Galaxy system. It is through the backup process that you secure the data on the client computers within the CommCell. On-demand backups allow you to secure data and/or the system state immediately without having to wait for the scheduled backup time. This capability can be useful if: ● You have some particularly valuable data that you need to secure immediately. ● Your data is not routinely secured through a backup schedule and you want to back up your data. Using on-demand backups, you can initiate full, incremental, and differential backups. You can initiate an on-demand backup on the following levels: ● A selected subclient ● A selected backup set ● The default backup set Note: Selecting a backup set backs up the entire file system on the client computer. Selecting a subclient backs up only that portion of the file system that is mapped to that subclient. Starting a backup on a backup set causes Galaxy to start individual backups for each subclient contained therein. If the subclients are associated with the same Storage Policy, then their backups will run serially unless that Storage Policy is configured to accommodate multiple data streams.

The Microsoft Windows 2000 system state backup is initiated from the default subclient in the backup set. The system state is always backed up using a full backup, even if that subclient runs a different kind of backup on the file system portion of the data.


To start an on-demand backup of a selected subclient 1. In the CommCell Browser, right-click the subclient that you want to back up, and then on the shortcut menu, click Backup. 2. In the window, select the type of backup that you want to initiate. 3. After selecting the backup type and any advanced options, click OK. You can track the progress of the backup operation in the Job Controller window.




To start an on-demand backup of a selected backup set 1. In the CommCell Browser, right-click the backup set that you want to back up, and then on the shortcut menu click Backup All Subclients. The system prompts you to confirm that you want to back up all the subclients contained within the selected backup set. Click OK to proceed. 2. In the window, select the type of backup that you want to initiate.

Chapter 3: Basic Backup and Restore Operations 123

Note: Do not select Synthetic Full. This is a special type of backup.

3. After selecting the backup type and any advanced options, click OK. You can

track the progress of the backup operation from the Job Controller window.


To start an on-demand backup of the default backup set 1. In the CommCell Browser, right-click the File System iDataAgent icon corresponding to the client computer that you want to back up, and then from the shortcut menu click Backup Default Backup Set. 2. The system prompts you to confirm that you want to back up all the subclients contained within the backup set. Click Yes to proceed. 3. After selecting the backup type and any advanced options, click OK. Galaxy starts the backup operation. You can track the progress of the backup operation in the Job Controller window. When the backup completes, Galaxy displays a confirmation message.

Creating Backup Sets A backup set is a logical grouping of subclients. During client installation, Galaxy creates one default backup set on the client computer. This backup set contains a default subclient, ensuring that the entire client file system and system state elements can be backed up. If desired, you can create additional backup sets for the same client computer. A backup set always contains a default subclient. You can also create additional subclients within each backup set. Backup sets are a powerful feature. Through them, you can establish the following: ● One or more series of backups for a given client computer. ● One or more subclient groups for a given client computer. ● One or more series of backups for related subclients (that is, members of a subclient group).


To create additional backup sets for the client computer 1. In the CommCell Browser, right-click the File System icon of the client computer for which you want the backup set created, and then from the shortcut menu, click New Backup Set. In the next dialog box, enter the following: ● New Backup Set Name. Type the name (up to 32 characters) of the backup set that you want to create. ● Make this the Default backup set. If you want to designate this backup set as the default, select this checkbox; otherwise, leave this checkbox cleared.

124 Backup and Restore for Internet Data Center 2. Verify that the Storage Policy that Galaxy has associated with the default

3. 4.

5. 6.

7. 8.

subclient is the Storage Policy that you want. If you want to select a different Storage Policy, click the Storage Policy entry and select the one you want from the list. Click Add to create additional subclients within this backup set. On the General tab of the Subclient Properties dialog box, enter the name (up to 32 characters) of the subclient, and the content of the subclient. Subclients have optional properties that you can establish at this time from the other tabs within this dialog box. Click OK and repeat this step for each additional subclient that you want to define within this backup set. If you want to change the properties of any subclient that is listed in the New Backup Set dialog box, select the subclient and click Edit. Doing so displays the Subclient Properties dialog box, from which you can change the properties of the subclient. If you want to delete any subclient that you may have defined in the New Backup Set dialog box, select the subclient and then click Delete. In the New Backup Set dialog box, click OK.

Managing Restores Procedures often vary, depending on the type of data you are restoring.

Restoring Data to Windows 2000 In this section, you will learn how to restore some of the data that you backed up. To avoid overwriting existing data, restore the data to an alternate location. Before you begin, review the items in the following checklist. Doing so will help you to avoid common problems. Please ensure the following: ● The CommServe computer is powered on and the CommServe is running. ● The MediaAgent computer and media library are powered on. ● The client computer is powered on. ● All Galaxy services have been started. ● You have successfully performed a backup of this client computer.

Chapter 3: Basic Backup and Restore Operations 125

Restoring File System Data Galaxy allows you to restore data in several different ways. In this section, the most common method, a Browse/Restore, will be used. Browsing allows you to view the data that you have backed up and then select some or all of that data for restoration.





To browse the backup data and restore some of it to another directory 1. Log on to the CommServe computer. 2. On the Windows Start menu, point to Programs, then Galaxy then click Galaxy CommCell Console for Java GUI. 3. On the CommCell Logon window, log on by entering your Galaxy user name and password. 4. Galaxy displays the CommCell Console window. 5. In the CommCell Browser, right-click the File System icon, and then click Browse Default Backup Set. 6. In the Browse Options dialog box, click OK (assuming the default settings are being used). 7. Galaxy displays the Browse window, which shows the files and directories that you backed up from the client computer. 8. In the Browse window, open the file system structure and select the data you want to restore. 9. Click Restore All Selected. 10. In the Restore Options dialog box, clear the Restore to Same Paths option, and then type the name of the directory to which you want the data restored (for example, C:\Newdir) in the Destination folder field. By default, Galaxy will create this directory if it does not already exist. 11. Click OK (If the other settings are to remain unchanged). 12. Galaxy starts a restore and indicates the status in the Job Controller window. Once the data is fully restored, Galaxy displays a confirmation message. Click OK to acknowledge the message. 13. To confirm that the data was indeed restored, navigate to the restore destination directory. There you will find the data that you restored. To restore file system data to the client computer 1. In the CommCell Browser, right-click the backup set whose data you want to browse and then from the shortcut menu click Browse Backup Data. 2. In the dialog box, select the browse options that you want to use. 3. In this procedure, the Client Computer field is unavailable because it was already determined when the backup set was selected in step 1. 4. Select any additional browse options from the dialog box.

126 Backup and Restore for Internet Data Center 5. In the Browse window, use the file system tree to open the structure of the file 6. 7. 8. 9.

system. In the Browse window, select the files and/or directories that you want to restore and then click Restore All Selected. In the dialog box, select the restore options that you want to use. If you want to select any additional restore options, click Advanced and in the dialog box, select the options that you want. Once you have selected the restore options, the system displays the Progress bar and starts to restore the data. Observe the Progress bar to monitor the restore process. If you want to browse the same backup set again, perhaps using different browse-time thresholds, on the Browse menu click New Browse.

Restoring System Databases The system state is always backed up in its entirety as Full backups. Included with the system state backup data are several other databases. Since these other databases are separate elements, they can be selectively restored, without performing a full system state restore. These database elements include the following: ● Event logs ● RSM database ● Terminal Server database ● Quota information ● Content indexing catalogs You have the choice of restoring these items when you perform a restore operation of the System Databases. These databases are available for restoration if they have been installed and have been backed up.


To restore the system databases 1. In the CommCell Browser, right-click the backup set that contains the System Databases to restore, and then click Restore System Databases. 2. In the Restore System Databases Options dialog box, accept the defaults or change the option selections. 3. Click OK. Galaxy initiates the system state restore job. Some services may be interrupted during the time that the databases are restored. After the restore, ensure that the services are returned to the online state.

Restoring Data to a Mapped Network Drive Galaxy allows you to restore data to a client computer’s mapped network drives. The restored data assumes the access characteristics of the destination share.

Chapter 3: Basic Backup and Restore Operations 127

Before you begin, note that mapped network drives exist as Windows share directories (that is, shares) on some other computer on the network. For data security reasons, these shares possess access privileges that determine who can access the share and the rights under which access is permitted. If your Windows account does not have privileges to write data to the share, you must be prepared to provide the login and password of a Windows account that does have these privileges. Ensure that the Windows share to which you intend to restore the data is accessible as a mapped network drive from the destination computer.


To restore data to a mapped network drive 1. In the CommCell Browser, right-click the backup set whose data you want to browse, and then click Browse Backup Data from the short-cut menu. 2. In the dialog box, select the browse options that you want to use. 3. Select any additional browse options from the dialog box. 4. In the Browse window, use the file system tree to open the structure of the file system. 5. In the Browse window, select the files and/or directories that you want to restore, and then click Restore All Selected. 6. In the dialog box, select the restore options that you want to use. 7. Ensure that the destination computer is the computer that has the mapped drive, not the computer that has the share. Also, if the data did not originate from the mapped drive, type the destination path starting with the mapped drive letter in the Restore to Same Paths field (for example, H:\Sales\Monthly Reports). 8. If you want to select any additional restore options, click Advanced and select the options you want from the dialog box. 9. If you do not have Change permissions for the share to which you intend to restore the data, then you must select Impersonate NT User in the Advanced Restore Option dialog box and provide the login and password of a Windows account that does have these permissions; otherwise, the data cannot be restored to the selected share. If you can copy or create a file in the share, you should be able to restore data to that share without having to select this option. If the user account is established as a domain user account, you must enter a fully qualified user name (for example, domain_name\user_name) and password. 10. Once you have selected the restore options the system displays the Progress bar and begins to restore the data. Observe the Progress bar to monitor the restore process.

128 Backup and Restore for Internet Data Center

Restoring Data to Exchange 2000 Server To avoid common problems, make sure the client computer is powered on and that you have successfully performed a database backup of Exchange 2000 Server before you begin.

Restoring Database Data The Galaxy iDataAgent for Exchange 2000 Server software enables you to restore your Exchange 2000 Server databases. The following procedure provides the steps necessary to restore an Exchange 2000 Server database: Warning: This procedure describes how to restore the Exchange 2000 Server database. It is provided for informational purposes only. Do not perform this procedure unless you intend to overwrite your existing Exchange 2000 Server database with the backed up version.

1. Dismount all information stores that you will be selecting during the restore

2.

3.

4. 5. 6. 7. 8. 9. 10. 11. 12.

operation. If you are restoring the entire server running Exchange 2000 Server, dismount all stores. If you are restoring the Key Management Service (KMS) database, verify that the KMS data directory is empty (typically \Program Files\Exchsrvr\Kmsdata ), and make sure that the Microsoft Exchange Key Management Service is started. If you are restoring the Site Replication Service (SRS) database, verify that there are no *.ebd, *.log or *.chk files in the Exchsrvr/Srsdata folder, and make sure that the Microsoft Exchange Site Replication Service is started. On the Start menu, point to Programs, then Galaxy, and then click Galaxy CommCell Console for Java GUI. In the CommCell Logon window, log on by entering your Galaxy user name and password. Galaxy displays the CommCell Console window. From the CommCell Browser tree, right-click the Exchange Database icon, and then click Browse Backup Data. In the Browse Options dialog box, click OK (assuming the default settings are being used). Galaxy displays the Browse window, which shows the Exchange 2000 Server databases that have been backed up. In the Browse window, select the database(s) you would like to restore. Click Restore All Selected. In the Restore Summary dialog box, use the default settings and restore the data to the same Exchange 2000 Server database.

Chapter 3: Basic Backup and Restore Operations 129

13. To automatically mount the stores after the restoration, select the Mount data-

base after restore option. Note that this option is disabled if only KMS or SRS databases have been selected for restore. Do not perform this step unless you intend to overwrite your existing Exchange 2000 Server database stores with the backed up versions. Click OK. 14. Galaxy starts a full restore of the items selected and indicates its status in the Job Controller window. Once the data is fully restored, Galaxy displays a confirmation message. Click OK to acknowledge the message. 15. If you restored the KMS database, make sure that you stop and then re-start the Microsoft Exchange Key Management Service after the restore has successfully completed. 16. If you restored the SRS database, make sure that you stop and then re-start the Microsoft Exchange Site Replication Service after the restore has successfully completed.

Restoring Data to an Exchange 2000 Mailbox The Galaxy software for Exchange 2000 Mailbox allows you to select and restore not only specific mailboxes, but also individual mailbox messages. The following procedure uses the browse and restore feature to browse the mailbox data and restore some individual messages.


To browse the Mailbox data and restore individual settings 1. On the Start menu, point to Programs, then Galaxy, and then click Galaxy CommCell Console for Java GUI. 2. In the CommCell Logon window, log on by entering your Galaxy user name and password. 3. Galaxy displays the CommCell Console window. 4. In the CommCell Browser tree, right-click the Exchange Mailbox icon, and then click Browse Default Backup Set. 5. In the Browse Options dialog box, click OK (assuming the default settings are being used). 6. Galaxy displays the Browse window, which shows the mailboxes that you backed up. 7. In the Browse window, expand the mailbox structure by opening an Exchange 2000 mailbox. Then select some mailbox data that you want to restore. 8. Click Restore All Selected. 9. In the Restore Summary dialog box, click OK to use the default settings and restore the messages to the same mailbox folder. Keep in mind that Galaxy will append these messages to the mailbox folder. It will not overwrite the original messages.

130 Backup and Restore for Internet Data Center 10. Galaxy starts a full restore of the items selected and indicates its status in the Job

Controller window. Once the messages are restored, Galaxy displays a confirmation message. Click OK to acknowledge the message. 11. To confirm that the messages were actually restored, check the mailbox folder for the restored messages.

Restoring Data to SQL Server 2000 This section describes how to perform an out-of-place restore of a SQL Server database on the client computer. To avoid common problems, make sure that the client computer is powered on and that you have successfully performed an SQL Server 2000 database backup before you begin. The Galaxy SQL Server client software allows you to select and restore specific databases. Using Galaxy’s browse and restore feature, you can browse the database data and restore an individual database. The following instructions demonstrate the procedure using a backup of the sample Pubs database. For information about how this database was backed up, refer to Chapter 2, “Backup and Restore Deployment.”


To restore data from a pubs database 1. On any computer where the CommCell Console is installed, on the Start menu, point to Programs, then Galaxy, and then click Galaxy CommCell Console for Java GUI. 2. In the CommCell Logon window, log on by entering your Galaxy user name and password. 3. Galaxy displays the CommCell Console window. 4. In the CommCell Browser tree, right-click SQL Server and then click Browse SQL Server. 5. In the Browse Option dialog box, click OK to accept the default settings. 6. In the Browse window, click the SQL Server instance. Then select the Pubs database that was backed up previously. 7. Click Restore All Selected. 8. In the SQL Database Restore Options dialog box, select a Restore type_of_database_Restore and a Recovery type_of_Recovery. Then click Advanced. 9. In the Advanced SQL Restore Options dialog box, select the Pubs database and enter a new name. This replaces all instances of the name Pubs in the Database field with the new name. 10. Change the Database File Path for all Pubs files to an alternate location. The path to the alternate location must exist before the restore is performed. 11. Click OK to go back to the SQL Database Restore Options screen. Click OK again.

Chapter 3: Basic Backup and Restore Operations 131

12. Galaxy starts a full restore of the Pubs database to the new database name and

location, and indicates its status in the Job Controller window. 13. When the restore has completed, Galaxy displays a completion message. Click OK to close the window. 14. To confirm that the Pubs database was actually restored, open Enterprise Manager and refresh the Databases list. The new copy of the Pubs database should be listed under the new name.

Managing Media Managing media consists of importing into and exporting from a library.

Importing Media into a Library Importing is the process by which you move media that are outside a library into storage slots within the library. There are two ways of importing media: ● You can import media through the library’s mail slot (if one is available). ● You can open the library door and insert media into storage slots by hand. Importing media through a mail slot offers several advantages: The inventory update that is triggered by a mail slot import is much less time-consuming than the full inventory operation that is triggered when you open and then close the library door. In addition, if you import new media through a mail slot using the Galaxy import operation, Galaxy automatically discovers the media. Note that inserting media in, and closing, the mail slots of some libraries may trigger a full inventory operation (rather than an inventory update). If you open the door and insert media, you must initiate a discovery operation. You must also initiate a discovery operation if you import through a mail slot, without using the Galaxy import operation. However, under certain circumstances, you may want to open the library door even though a mail slot is available. For example, if you want to add many media to a library at once, it may be faster to open the door than to use the mail slot. If you are not using a mail slot, be careful not to open the library door while media are mounted in drives within the library. In some library models (for example, ATL 200 and ATL 500), opening the door causes the library to unmount all media, even those that are in active use. This can cause database inconsistency and failure of the running job(s).


To import media into a library 1. From the CommCell Browser, right-click the library (or the scratch pool of the library) into which you want to import media, and then click Import Media from the short-cut menu.

132 Backup and Restore for Internet Data Center 2. An Import Media prompt appears, advising you to do one of the following: ●

●

Importing through a mail slot. Insert one or more media into the mail slot and wait for them to be moved to storage slots. Do not click OK until all of the imported media have been moved to storage slots. After all media are transferred to storage slots, click OK in the Import Media prompt. If you click OK in the Insert Media prompt before the media are moved to storage slots, Galaxy will not discover the media. Inserting media directly. Open the library door, insert media into storage slots, and then close the door. Click OK in the Import Media prompt.

3. Galaxy displays a warning message to move cleaning media to the cleaning

media pool. Click OK. 4. If the imported media were previously discovered, their barcodes are displayed in the library inventory in the right pane of the CommCell Browser. Otherwise, the media must be discovered: ● Automatic Discovery. If you imported undiscovered media through the mail slot (and you did not click OK in the Insert Media prompt until the media were moved to storage slots), Galaxy automatically discovers the media. ● In the dialog box that appears, select the hardware type of the new media from the Media Type to be Imported list. ● Select the scratch pool to which you want the media assigned from the Destination Scratch Pool list. ● The total number of undiscovered media available in the library is displayed in the No. of media in Free Media Pool field. ● Specify the number of media you would like to discover in the No. of media to be discovered field. ● Click OK. ●

Manual Discovery. If you opened the library door and inserted media directly, or if you imported through a mail slot and clicked OK before the media were moved to storage slots, you must manually discover media. For details on Discovering Media within a Library refer to the online help, under the topic Library Operations.

Exporting Media from a Library Exporting is the process by which you physically remove one or more media from a library. When you export a medium, the data that it contains is no longer at the immediate disposal of the Galaxy system. If an operation (for example, restore or auxiliary copy) requires data from an exported medium, you will have to reimport the medium to complete the operation. Galaxy retains information about exported media; they do not have to be rediscovered if they are reimported.

Chapter 3: Basic Backup and Restore Operations 133

There are two ways to export media: ● You can export media through the library’s mail slot (if one is available). ● You can open the library door and remove media from the storage slots by hand. Exporting media through a mail slot offers an advantage. The inventory update that is triggered by a mail slot export is much less time-consuming than the full inventory operation that is triggered when you close the library door. Under certain circumstances, however, you may want to open the library door even though a mail slot is available. For example, if you want to remove many media from a library at once, it may be faster to open the door than to use the mail slot. Media that are being written to or read from cannot be exported. It is recommended that you enter a description of the storage location and appropriate reference information when you export a medium. Note: Removing media from and closing the mail slots of some libraries may trigger a full inventory operation (rather than an inventory update).


To export media from a library If you are not using a mail slot, be careful not to open the library door while media are mounted in drives within the library. In some library models (for example, ATL 200 and ATL 500), opening the door causes the library to unmount all media, even those that are in active use. This can cause database inconsistency and failure of the running job(s). 1. In the CommCell Browser, right-click the library from which you want to export media, and then from the shortcut menu click Export Media. 2. In the next dialog box, on the Media List, select the barcodes of one or more media that you want to remove from the library. You can enter an optional comment about the location to which you are moving the media (for example, Shelf 26 in Storage Room) in the Location field. Click OK. The location field is for display purposes only, to help you keep track of exported media. Galaxy cannot ensure that media are stored in the locations entered. 3. An Export Media prompt appears, advising you to do one of the following: ● Exporting through a mail slot. Click OK, wait for the media to be moved to the mail slot, and then remove them from the library. If you are exporting multiple media, they will be delivered to the mail slot one by one until all have been exported. ● Removing media directly. Open the library door, remove the media that you want to export, and then close the door.

134 Backup and Restore for Internet Data Center 4. (Optional) In the case of a bulk export (multiple media), some libraries require

that you open the mail slot and remove each medium individually, as it is delivered. This is true even if the mail slot can hold multiple media. If your library has this requirement and you fail to remove a medium within the Galaxy export media timeout period, the operation times out; that is, Galaxy terminates the operation and sends a message to the Event Log reporting the failure.

Summary Information in this chapter covers the daily recommended or routine operations of the Galaxy Backup and Restore solution for the Microsoft Systems Architecture environment. These tasks include the verification of periodic backups and the procedures for maintaining or restoring client data for the Windows 2000 File System, Exchange 2000 and SQL Server 2000. Additional system configuration is provided, to enable these tasks to be successfully carried out. For further information on the default Galaxy configuration, refer to Chapter 2, “Backup and Restore Deployment.” For further information on the advanced configuration of Galaxy in a Microsoft Systems Architecture environment, refer to Chapter 4, “Advanced Backup and Restore Operations.”

4 Advanced Backup and Restore Operations Abstract This chapter describes the advanced operations of the Galaxy system used in the Backup and Restore Solution for Windows 2000-Based Data Centers. These operations include Storage Area Network configuration, configuring the CommServe, MediaAgents, libraries and drives, and iDataAgents. Detailed instructions and guidelines for managing disaster recovery are also provided.

Introduction This chapter describes in detail the advanced operations of a Galaxy system, and includes procedures for configuring Galaxy components and the network, and for managing disaster recovery.

Storage Area Network Configuration When you configure a storage area network (SAN), you must consider a number of configuration, addressing, and mapping issues, as well as errors that may occur during the processes that are involved.

SAN Configuration Overview Here you can read about particular configuration issues that arise when Galaxy is used in a SAN environment. For general information on configuring Galaxy in a SAN environment, see the Galaxy Media Management Administration Guide.

136 Backup and Restore for Internet Data Center

The Basic SAN Setup A SAN is a Fibre Channel (FC) network that is dedicated to carrying backup data. A SAN improves backup and restore performance and eases congestion on an enterprise’s local area network (LAN), freeing it for normal business activities and communication. You can configure your SAN environment to use the dynamic drive sharing (DDS) feature to share drives among multiple MediaAgents in a CommCell within a SAN environment. Basic SAN components include the following: ● Host Bus Adapter (HBA). Each computer that is attached to a fiber network needs a special adapter called an HBA, which can send and receive signals across FC cables. ● Bridge, Router or Gateway. These pieces of equipment translate fiber signals to signals that can be understood by SCSI devices (fiber-to-SCSI communications) and vice versa. A gateway can also communicate between an FC network and native fiber devices (fiber-to-fiber communications). Bridges, routers, and gateways are used to connect servers and storage devices to the SAN. ● Hub. In a Fibre Channel arbitrated loop (FC-AL), the hub is the fault-tolerant center of the network to which servers and storage devices are connected. ● Switch. In the more complex network environment of switched fiber (see the following), the switch is the center of the fabric, or infrastructure, of the network. Servers and storage devices are connected to the switch, which is more intelligent and has more bandwidth than a hub.

Fibre Channel Configurations There are two basic SAN configurations. Fibre Channel arbitrated loop (FC-AL) is a logical ring of fiber to which all of the devices are connected. It is created by connecting devices to a hub so that bandwidth and storage resources on the network are pooled and shared by all devices, as shown in Figure 4.1.

Chapter 4: Advanced Backup and Restore Operations 137

HBA Media Agent FC to SCSI SAN Bridge/Route

FC-AL Hub

SCSI Media Library

SCSI to FC FC Cable SCSI Cable

HBA Media Agent

Figure 4.1 Fibre Channel Arbitrated Loop

In a switched fiber (FC-SW) configuration, as shown in Figure 4.2, virtual loops are established between hosts and backup devices. Each host can have exclusive use of its virtually attached storage devices. SCSI Media Library

HBA Media Agent FC to SCSI

FC Switch

SAN Bridge/Route SCSI to FC

SCSI Media Library

HBA Media Agent

FC Cable SCSI Cable

Figure 4.2 Fibre Channel Switched Fiber

SAN Addressing Overview For backup devices to be available to Galaxy, the system must know which physical device is mapped to a given SCSI address. When a MediaAgent is directly attached to a storage device, the SCSI address is determined by the physical SCSI connection, and the SAN adds an FC network between the MediaAgent and the SCSI backup device. However, the MediaAgent and the backup device still use the SCSI protocol

138 Backup and Restore for Internet Data Center

to communicate across the FC network. Consequently, the MediaAgent still needs to be able to associate each physical device with a SCSI address. A SCSI address includes three identifiers. Table 4.1 lists the components of a SCSI address and its counterparts in the FC-SW and FC-AL addressing schemes. Table 4.1: SCSI address components SCSI address component

FC-AL*

FC-SW

Bus

Loop

Fabric

Target

Arbitrated Loop Physical Address (AL_PA)

Port_ID

Logical Unit Number (LUN)

LUN

LUN

* Conceptually, both a loop and a fabric represent collections of addressable devices. In practice, this part of the address is generally the same as the port number of the HBA that connects the host to the FC network.

SCSI-LUN Mapping Guidelines for SAN Libraries Note: See your hardware manufacturer’s documentation for instructions on setting SCSI targets for storage devices and SCSI-to-FC address mapping for SAN routers.

The SCSI target guidelines that follow are recommendations that can make system administration easier—they are not requirements. However, the LUN guidelines must be followed in order for the system to function properly.

SCSI Target Guidelines You should observe the following guidelines when assigning SCSI targets to storage devices that are attached to a SAN: ● Assign each medium changer to a SCSI target that is lower than those of the targets of its drives. ● When setting the SCSI targets, you should assign SCSI target numbers in ascending order, in accordance with the physical drive location. That is, the drive that has the physical address with the lowest number (for example, Drive 0) gets the lowest SCSI target, while the drive that has the physical address with the highest number (for example, Drive 4) gets the highest SCSI target, with remaining drives assigned in sequence. A good convention to use, when possible, is to set the library medium changer to 0, the first drive to target 1, the second drive to target 2, and so on.

Chapter 4: Advanced Backup and Restore Operations 139

Note: Physical drive locations are numbered differently depending on the library. The first drive in one library may be 0, whereas in another library it may be 1. See the manufacturer’s documentation for details on your library. ●

●

If multiple SCSI ports are to be attached to a single library, you should attach the SCSI ports in order of the physical device sequence. For example, connect the first SCSI port to the medium changer and drives 1 and 2; the next SCSI port to drives 3 and 4, and so on. Try to assign a unique SCSI target to each device, even for devices on different SCSI ports. Doing so can make it easier to identify the drives later, should that become necessary.

Fibre Channel LUN Guidelines The following guidelines must be observed when assigning Fibre Channel LUNs to storage devices that are attached to a SAN: ● Assign each medium changer to a LUN that has a lower number than that of the LUNs of its drives. Otherwise, drives may be associated with the wrong library or incorrectly detected as stand-alone drives. ● For each router, start with zero when assigning LUNs and continue in ascending sequence. Do not skip any numbers in the sequence. If possible, match the LUN to the SCSI target of the device. The following figures show several scenarios that demonstrate the SCSI target and LUN guidelines. LUN SCSI Bus 0 HBA MediaAgent

SAN Switch

0 1

Gateway/ Router

2

SCSI Bus 1

Library 1

SCSI Target

Medium Changer

0

Drive 1*

1

Drive 2*

2

Library 2 Fibre Channel (FC) SCSI

3

Medium Changer

3

4

Drive 1*

4

5

Drive 2*

5

* = Physical drive

Figure 4.3 Single-router, multiple-library configuration

140 Backup and Restore for Internet Data Center

Figure 4.3 shows the configuration for a single router that is connected to multiple libraries. Pictured from left to right, the figure shows the following: A MediaAgent contains an HBA that connects it to a SAN router through a Fibre Channel switch. Within the fiber network, SAN devices are addressed by Fibre Channel LUNs, which are set through the LUN mapping interface provided by the manufacturer of the router. The router is connected through SCSI buses and cables to two libraries. Within the libraries, each device has a SCSI target, which is set through the interface provided by the manufacturer of the library. Note the following guidelines in operation: ● SCSI Target. When you assign SCSI targets, assign target 0 first, and assign the rest in ascending order. The lowest target within each library is assigned to the library’s medium changer. ● LUN. When you assign Fibre Channel LUNs, assign 0 first, followed by contiguous LUNs assigned in ascending order. Figure 4.4 depicts only those aspects of the SCSI and FC addresses that are commonly configured by the user. 3 shows the complete address translations that are performed by the router between SCSI addresses (Bus, Target, LUN) and Fibre Channel addresses (Loop, AL_PA, LUN), and the reverse translations that are performed by the MediaAgent’s HBA. The left-most SCSI addresses are the ones by which the SAN devices are identified in the Galaxy Library and Drive Configuration utility. For additional information on this utility, see the Galaxy CommCell Media Management Guide. Note that values of zero have been assigned to Loop, AL_PA, and the SCSI bus and target in the address on the left, as shown in Figure 4.4. The actual values depend on the SAN configuration.

SCSI B0T0L0 B0T0L1 B0T0L2 B0T0L3 B0T0L4 B0T0L5

HBA HBA Loop0 " " " " "

FC AL_PA0L0 " L1 " L2 " L3 " L4 " L5

Router FC Router Loop0 AL_PA0L0 " " L1 " " L2 " " L3 " " L4 " " L5

SCSI B0T0L0 B0T1L0 B0T2L0 B1T3L0 B1T4L0 B1T5L0

Figure 4.4 Single router, multiple library address translations

The configuration for multiple routers and a single library, shown in Figure 4.5, can maximize performance for a library containing many drives.

Chapter 4: Advanced Backup and Restore Operations 141

fibre Channel (FC) SCSI

LUN

SCSI Bus 0

SAN Switch

0

1

Drive 1*

1

2

Drive 2*

2

3

Drive 3*

3

Drive 4*

4

Router

SCSI Bus 0

4 Fibre Channel (FC) SCSI

SCSI Target

Medium Changer

0

SCSI Bus 1 HBA MediaAgent

Library 1

0 1

Router

Drive 5*

5

Drive 6*

6

* = Physical drive no.

Figure 4.5 Multiple router, single library configuration

Pictured from left to right, the figure shows the following: a MediaAgent contains an HBA that connects it to a SAN switch by using a Fibre Channel network. The switch is connected to two SAN routers. Within the fiber network, SAN devices are addressed by Fibre Channel logical unit numbers (LUNs), which are set through the LUN mapping interface provided by the manufacturer of the router. The router is connected by using SCSI buses and cables to a single library containing six drives. Within the library, each device has a SCSI target, which is set by using the interface provided by the manufacturer of the library. Note the following guidelines in operation: ● SCSI Target. When assigning SCSI targets, assign target 0 first, and assign the rest in ascending order. The lowest target within the library is assigned to the library’s medium changer. If the library had additional drives, target 7 would be skipped, because the SCSI controller uses SCSI ID 7 by default, and the assignments continue with target 8. ● LUN. When assigning Fibre Channel LUNs, assign 0 first, and assign the remaining contiguous LUNs in ascending order. Restart LUN numbering with the second router. Figure 4.5 depicts only those aspects of the SCSI and FC addresses that are commonly configured by the user. Figure 4.6 shows the complete address translations that are performed by the router between SCSI addresses (Bus, Target, LUN) and FC addresses (Loop, AL_PA, LUN), and the reverse translations that are performed by the MediaAgent’s HBA. The SCSI addresses on the left are the ones by which the SAN devices are identified in the Galaxy Library and Drive Configuration utility. (For information on using this utility, see the Galaxy CommCell Media Management Guide.) Each router is represented in the addresses on the left as a separate SCSI target.

142 Backup and Restore for Internet Data Center

SCSI B0T0L0 B0T0L1 B0T0L2 B0T0L3 B0T0L4 B0T1L0 B0T0L1

HBA HBA Loop0 " " " " Loop0 Loop0

FC AL_PA0L0 " L1 " L2 " L3 " L4 AL_PA1L0 "L1

Router FC Router Loop0 AL_PA0L0 " " L1 " " L2 " " L3 " " L4 Loop0 AL_PA1L0 Loop0 "L1

SCSI B0T0L0 B0T1L0 B0T2L0 B1T3L0 B1T4L0 B0T5L0 B0T6L0

Figure 4.6 Multiple router, single library - address translations

Note that in Figure 4.6, values have been assigned to Loop, AL_PA, and the SCSI bus and target in the address on the left. The actual values depend on the system configuration.

Avoiding Common SAN Errors In setting up a SAN for use by Galaxy, the essential goal is to ensure that each physical device is represented in the CommCell by one, and only one, SCSI address (bus, target, and LUN), and that this SCSI address remains consistent through all layers of the SAN, at all times. If a single device is represented by multiple SCSI addresses, or if multiple instances of a single address for a device exist within the network, resource contention can result when different MediaAgents attempt to use the same drive simultaneously.

Uniform Addressing Across Devices Within the FC network, the routers, bridges, or gateways that are physically connected to storage devices translate the SCSI addresses of those devices to the LUNs that are used by the FC network. Each MediaAgent that is attached to the SAN contains an HBA. Among other functions, the HBA translates the FC addresses generated by the router back to SCSI addresses and makes these addresses available to the MediaAgent. Different HBAs use different algorithms to map FCs to SCSI addresses. This can result in a single drive appearing under two different identifiers in the Galaxy Library and Drive Configuration utility, and can cause resource-contention problems. In addition, different routers, gateways, and bridges may use different SCSI-to-FC mapping algorithms.

Chapter 4: Advanced Backup and Restore Operations 143

Note: To ensure that the SCSI addressing convention is the same for all devices in the SAN, all MediaAgents attached to a SAN must use the same brand and model HBA, and the same driver and firmware revisions. Furthermore, all routers must be of the same brand and model. The drivers and firmware should be the newest available.

Avoiding Dynamic Address Changes An FC address can change at either the AL_PA/Port_ID level or at the LUN level. In either case, the HBA-translated SCSI address of affected devices changes as well. If the SCSI address of a configured device changes, Galaxy is unable to access the device. The sections that follow show how to maintain address stability within your SAN. AL_PAs and Port_IDs

AL_PAs and Port_IDs can be set in one of two ways: ● Hard addressing. This addressing scheme requires that you manually set switches on a device to assign it a permanent AL_PA. (A Port_ID includes the AL_PA plus information about the fabric port to which the device is attached.) ● Soft addressing. If you use this scheme, AL_PAs are automatically assigned to fiber devices (for example, routers, gateways, HBAs, and so on) when they are attached to the network. However, if devices are added or removed, the addresses of other devices in the network may be reassigned, rendering these devices inaccessible to Galaxy. If the AL_PA of a router changes, all attached libraries become inaccessible to Galaxy. Soft addresses can be assigned even when you use hard addressing. If the switches on two devices are set for the same AL_PA, the first device detected by the network is assigned that address, while the second device is assigned a soft address. Note: To ensure that AL_PAs won’t change, use hard addressing and make sure that each device is assigned a unique AL_PA. To ensure that Port_IDs won’t change, follow the AL_PA guidelines. In addition, do not change the fabric ports of configured devices.

Some gateways do not work well with FC switches unless you enable soft addressing. Also some of the SAN gateways do not allow you to disable soft addressing. Enable soft addressing in both these circumstances.

144 Backup and Restore for Internet Data Center LUNs

Fibre Channel LUNs are set by bridges, routers, and gateways, which translate the SCSI addresses (SCSI port, target, and LUN) of attached devices to FC addresses. Routers have two addressing modes: ● Manual. This addressing scheme requires that you manually set the LUN for each device that is attached to the router. ● Automatic. In this addressing scheme, the router automatically assigns LUNs to attached devices. However, if devices are added or removed, the addresses of other attached devices may be reassigned. Consequently, Galaxy is unable to access the device. LUNs must start from zero. They must also be sequential and contiguous (that is, they must not skip numbers). Note: To ensure that the LUNs of devices that are attached to a router will not change, use manual addressing. Make sure that each device is assigned a unique LUN, and that LUNs start from zero and are sequential and contiguous. When you first configure your SAN, you may want to use automatic addressing to ensure that LUNs meet these criteria. You can then switch to manual mode to set the same addresses that were automatically assigned by the router.

SAN Configuration Summary The following are the essential SAN configuration principles that have an impact on the ability of Galaxy to successfully detect and use SAN storage devices: ● All MediaAgents attached to a SAN must use the same brand and model HBA, as well as the same driver and firmware revisions; all routers must also be of the same brand and model. This ensures that the same Fibre Channel-to-SCSI address translation is used for all devices in the SAN. ● The latest firmware and device driver versions must be used. ● Hard addresses must be used rather than soft addresses to ensure that AL_PAs and Port_IDs will not change. ● Each device is assigned a unique AL_PA. ● The fabric port of configured devices that are attached to a switched network must not be changed. ● The sequential, contiguous LUN order, starting at 0 (assumed by operating systems), must be preserved when you set AL_PAs in manual mode. ● Manual addressing mode must be used to prevent SAN routers from changing LUNs when the SCSI configuration changes. ● For easier system administration, SCSI configuration guidelines should be followed when setting SCSI targets for storage devices.

Chapter 4: Advanced Backup and Restore Operations 145

CommServe Many aspects of the CommServe either require configuration or can be configured according to your specific backup and restore solution.

License Administration Each component of Galaxy (MediaAgents, libraries, and clients) requires a license for use. When you purchase Galaxy, an installation license is provided with the Galaxy software. This initial installation license applies to the entire CommCell, specifying a license type and count for each CommCell component within the CommCell configuration. The CommServe component does not contain a separate license type and count; it is automatically included in the CommCell configuration. The Galaxy License Administration feature performs the following functions: ● Displays and updates all licensing information. ● Keeps track of installed components. License information for the entire CommCell, including the type and number of the components installed, is displayed in the License Administration window. When a component is installed or uninstalled, the count of that license type is updated to reflect the new configuration.

Updating the CommServe IP Address If the CommServe IP address is updated, the CommServe license must also be updated. An updated license must be obtained from CommVault Support before the address is changed. CommVault Support will assist in the process of changing the IP address and updating the license through license administration.

License Types Galaxy uses the following types of licenses in various situations: Table 4.2: Galaxy license types License type

Description

Evaluation license

An evaluation license can be used to install a Galaxy CommCell initially. You can continue to use Galaxy for evaluation for the duration of the license.

Permanent license

There are two types of permanent licenses: Installation is used for new CommCell installations Release upgrade is used to upgrade your Galaxy installation from one major release to another.

Update license

Update licenses are permanent and are used to do the following: Convert an evaluation license to a permanent license. Add components to an existing Galaxy software installation. Support change of the CommServe IP address. Maintain the license database. Update licenses are permanent in nature.

146 Backup and Restore for Internet Data Center

Note: Contact your Galaxy software provider for instructions on obtaining and using a license. After you have obtained the license, follow the instructions to update your existing license.

Keep the installation license file in a safe place; you may need the file if you ever need to perform ExpressRecovery.

License Administration The Galaxy License Administration feature allows you to examine and update an existing license. The License Administration window displays the following information: ● If and when the license will expire. ● The types of licenses installed on the CommCell. ● The total number of each license type. ● The number of used licenses for each type. The following procedures explain how to view and update licenses.


To open the License Administration window 1. In the CommCell Browser, right-click the CommServe and then click License Administration. 2. The License Administration window indicates the status of existing licenses for the CommCell and its Galaxy software components: This window may include the following items: Table 4.3: Items displayed in the License Administration window Item

Type of data displayed

CommCell ID

A unique serial number for this CommCell

CommServe ID

The IP address of the CommServe computer.

Activation Key

An automatically-generated key for the most current version of the license file.

OEM ID

A unique identifier number of the original equipment manufacturer (OEM) manufacturer. This applies only when the existing CommCell license is an Evaluation license.

OEM License Type

A type of license issued for this OEM. This applies only when the existing CommCell license is an Evaluation license.

Expiration Date

Expiration date of the CommCell license. This applies only when the existing CommCell license is an Evaluation license. After the license expires, Galaxy operations will fail.

Chapter 4: Advanced Backup and Restore Operations 147

Item

Type of data displayed

License Type

Indicates the Galaxy software component for the specific application (iDataAgent for the Microsoft® Windows® 2000 operating system, MediaAgent for Windows 2000, library control module, and so on).

Total

The total number of licenses for this license type.

Used

The number of licenses in use for this license type.

Expiration Date (for CommCell components)

The expiration date, if applicable, for the listed license type; permanent licenses never expire.

Note: Columns in the License Administration window can be sorted by clicking on the column header.

Updating a License You can use the License Administration feature to update a Galaxy license in the following situations: ● To extend the evaluation copy. ● To update the evaluation license to a permanent license. This enables Galaxy operations to continue uninterrupted beyond the expiration date of the Evaluation license. ● To add software components (for example, a MediaAgent) to, or increase the license copy numbers of, an existing CommCell. ● To update the IP address of the CommServe computer. There are two ways to update a CommCell license: by using the Galaxy Console or by using the command line in a command prompt when the Galaxy Console is unavailable.


To update the CommCell license by using the Galaxy Console 1. Insert the disk containing the updated license file into the CommServe computer’s disk drive. 2. In the License Administration window, click Update License. 3. In the Open dialog box, specify the location of the license file and then click Open. When finished processing, the system indicates success or failure of the license update as follows: ● Success: The License Administration window refreshes automatically with new data. ● Failure: A pop-up window appears, stating that the update failed.

148 Backup and Restore for Internet Data Center

Note: If the License Administration window does not automatically refresh, close it and reopen it.

4. If successful, click OK. (If not, contact your Galaxy software provider.)

License Validity and the CommServe IP Address If you change the CommServe IP address after you have installed the Galaxy software, the CommCell license becomes invalid. This may render the Galaxy software inoperable until you update the license with the new IP address. To update the license, you must obtain an IP Address Change license from your Galaxy provider and follow the instructions in “Updating a License” earlier in this chapter.

Anticipating License Expiration If you have not converted the CommCell installation license to a permanent license, and you want to know when the installation license will expire, you can check the expiration date from the CommCell Console. Use the Galaxy Event Viewer, which displays license expiration information at a set time before the license actually expires. The event viewer logs a major event if the CommServe license is going to expire within 10 days. The event message is triggered by any type of backup, including synthetic full.

Responding to License Expiration If the installation license expires, one or more symptoms may result. You can determine the cause of these symptoms by checking the Event Viewer or various log files in the \Galaxy\Log Files folder, as indicated in the following tables. If the installation license has expired for any reason, contact your Galaxy software supplier for instructions. The following list identifies these symptoms: ● Backups will not run. If this is the only symptom, check for iDataAgent license expiration as follows: ● Check the Event Viewer for: failure to initialize backup request, invalid or no license for application type app_type. Application name is app_name. ● Check the JobManager.log file for an expired application license evaluation date. ●

The MediaAgent will not restart. In this scenario, check for MediaAgent license expiration as follows: ● Check the Event Viewer for an expired application license evaluation date. ● Check the cvd.log file for an expired application license evaluation date.

Chapter 4: Advanced Backup and Restore Operations 149 ●

●

Only the Event Manager service (Evmgrs) and the Galaxy Console are activated. In this scenario, update the license from the Galaxy Console. The license has expired. Obtain either a purchase license or an extended license from CommVault Systems. Then update your license from the Galaxy Console.

Destination of CommServe ExpressRecovery Backups The ExpressRecovery backup destination must be a directory specified by a Universal Naming Convention (UNC) network path, preferably within the Windows domain of the CommServe computer. If you specify a drive outside the CommServe’s Windows domain, you will need to configure the share to allow ExpressRecovery backups to be written. Note: We strongly recommend that you write down the destination of your ExpressRecovery backups and keep this information in a secure location.

The destination path cannot be local to the CommServe computer because, while it is possible to direct ExpressRecovery backups to the CommServe’s local hard drive, you may be unable to rebuild the CommServe if the computer’s hardware fails. Also, the path cannot be a mapped network drive. You should also reserve enough space on your backup drive for ExpressRecovery backups. The recommended amount of space is 1 gigabyte (GB), although this will vary from system to system. Initially, you probably will not need this much space. However, because an ExpressRecovery backup contains a dump of the Microsoft SQL Server database, backups can eventually grow to take up as much space as the database. ExpressRecovery backups will run only when the SQL Server is run as a System Account. If ExpressRecovery backups have failed from the start, check the services panel to determine whether the SQL Server is set up to log in with a System Account. If the setting is specified differently and the SQL Server brings the Galaxy services down, change the SQL Server service to run from the System Account, restart the SQL Server service, and then restart Galaxy services. Generally, one ExpressRecovery backup per day per system is sufficient. However, this depends on the retention periods and pruning schedules that you implement for your backups. As a rule of thumb, for each additional ExpressRecovery backup that you want, you should allocate an additional GB of space. If your ExpressRecovery backups start to fail, the appropriate message will be displayed; in such a case, check the amount of available space on your backup drive. You initially set the backup destination during CommServe installation; however, you can change the destination at any time from the ER Backup tab of the CommCell Properties dialog box.

150 Backup and Restore for Internet Data Center

The backup destination path you enter determines the destination of the next full ExpressRecovery backup. Differential backups are always sent to the same directory as the last full backup. If you change the backup destination without running a full ExpressRecovery backup, the first backup will by default be converted to a full backup. If you enter a non-local destination directory for ExpressRecovery backups during the CommServe installation, then you must enter the user name and password of the account that Galaxy will use to access the backup directory, after the installation/upgrade is completed. This account must be a domain account that has access privileges for the backup destination directory. (You can enter the user name and password on the ER Backup tab of the CommCell Properties dialog box.) You cannot change the ExpressRecovery destination that was entered during installation until an ExpressRecovery user account is entered by using the General tab of the CommCell Properties dialog box. This is true whether the original destination is local or remote, and whether the new backup destination is local or remote. If you change the ExpressRecovery destination to a new non-local destination, make sure that you change the account to a domain account with access to the new destination. Note: You should check the Galaxy Event Viewer regularly so that you will be aware of any problems associated with ExpressRecovery backups.


To set or change the ExpressRecovery backup destination To perform this procedure you must have Administrative Management permissions on the Galaxy system:

1. In the CommCell Browser, right-click the CommServe, and then click Properties. 2. In the CommCell Properties dialog box, on the ER Backup tab, in the Back Up

Metadata to box, enter a backup path either by clicking Browse or by typing the path. The directory must be a valid UNC network path in the UNC format: \\server\share\path

Galaxy Service Control Manager While the procedures in this chapter describe how to start and stop Galaxy services, we recommend that the services remain running at all times. You should avoid stopping Galaxy services whenever possible, and make sure to review and thoroughly understand all procedures in this chapter before you attempt to implement them. By default, all Galaxy services start automatically when you start a system that has the Galaxy software installed.

Chapter 4: Advanced Backup and Restore Operations 151

Note: Galaxy services must be running in order for backups, restores, and all Galaxy jobs to run properly. Generally, you should leave all Galaxy services running.

When you stop Galaxy services on a given system, the functions that depend on that system’s services will no longer be available to the rest of the CommCell. As documented throughout this chapter, it is strongly recommended that you suspend or kill all jobs prior to stopping any Galaxy services. Any interrupted auxiliary copy jobs will need to be restarted after stopping and restarting Galaxy services. Stopping either the CommServe services or the base services will stop all Galaxy operations that depend on that CommServe. Because all Galaxy services depend on the base services, stopping the base services stops all Galaxy services.

Galaxy Service Configurations As Table 4.4 shows, all Galaxy computer configurations must include at least the base services. Then, depending on which Galaxy components (for example, CommServe and MediaAgents) are installed, their corresponding Galaxy services apply as well. If several Galaxy components are installed on a given computer, then that computer hosts all associated services. Table 4.4: Galaxy components and services For these Galaxy components

These Galaxy services apply

... which include the following services

Client only (any Galaxy system)

Galaxy base services

Galaxy Client Event Manager Galaxy Communications Service

CommServe only

Galaxy base services

Galaxy Client Event Manager Galaxy Communications Service

Galaxy CommServe Services

Galaxy Galaxy Galaxy Galaxy

Galaxy Base Services

Galaxy Client Event Manager Galaxy Communications Service

Galaxy MediaAgent Services

Galaxy Media Mount Manager Drive Management Service (DMS) Library Management Service (LMS) Note: LMS and DMS apply only to nonRemovable Storage Manager (RSM) tape and optical libraries.

MediaAgent only

Application Manager Job Manager Media & Library Manager Server Event Manager

152 Backup and Restore for Internet Data Center

Galaxy Service Dependencies When a Galaxy system has more than one Galaxy component, the Galaxy service dependencies are as shown in Table 4.5. Table 4.5: Galaxy service dependencies Using the Galaxy Service Control Manager to do the following:

Has the following effect:

Stop all Galaxy services

Stops all Galaxy services on that system.

Start all Galaxy services

Starts all Galaxy services on that system.

Stop the base services

Stops all Galaxy services on that system because all Galaxy services depend on the base services.

Start the base services

Starts only the base services. Restarting the other Galaxy services can be done individually or by restarting all services simultaneously.

Stop the CommServe services

Stops only the CommServe services. Operations for all Galaxy resources that depend on that CommServe are stopped.

Start the CommServe services

Starts the base and CommServe services.

Stop the MediaAgent services

Stops only the MediaAgent Service.

Start the MediaAgent services

Starts the base and the MediaAgent Services.

Controlling the Galaxy Services Because a system’s Galaxy component configuration (CommServe, MediaAgent, client computer) determines which Galaxy services will be running on that system, you will need to choose the procedure(s) most appropriate for each system on which you intend to stop the Galaxy services: ● Starting and stopping all Galaxy services (strongly recommended) ● Starting and stopping the base services ● Starting and stopping the CommServe services ● Starting and stopping the MediaAgent services Note: You can use either the Galaxy Service Control Manager or the Windows Services dialog box to view the status of the Galaxy services. To stop and start Galaxy services, however, use only the Galaxy Service Control Manager, and follow the appropriate procedure.

Chapter 4: Advanced Backup and Restore Operations 153

Starting and Stopping All Galaxy Services The following procedures describe how to stop and restart all Galaxy services on a local system. The option to stop all Galaxy services stops all the Galaxy services on the local computer, no matter which components are installed (for example, CommServe or client). This option is particularly useful if several components are installed and you want to stop the Galaxy services for all of them. Before you begin, use the Job Controller to suspend or kill all jobs. Alternately, you can wait for a job to complete.


To stop all Galaxy services 1. Click Start, point to Programs, click Galaxy and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy Base Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you prefer to start all Galaxy services manually, clear this option to disable the auto-start feature. 4. Click Stop to stop all Galaxy services. When the services are stopped successfully, the Galaxy Service Control Manager dialog box updates the All Galaxy Services status from Running to Stopped. 5. Optionally, you can verify which services you have stopped by clicking Services in Control Panel.




To start all Galaxy services 1. Click Start, point to Programs, click Galaxy and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy Base Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you prefer to start all Galaxy services manually, clear this option to disable the auto-start feature. 4. Click Start to restart all Galaxy services. When the services are restarted successfully, the Galaxy Service Control Manager dialog box updates the All Galaxy Services status from Stopped to Running. 5. Optionally, you can verify which services you have restarted by clicking Services in Control Panel. 6. Resume any jobs you suspended prior to stopping all Galaxy services.

154 Backup and Restore for Internet Data Center

Starting and Stopping the Base Services The following procedures describe how to stop and restart the base services. Note: Stopping the base services stops all Galaxy services (for the local system) automatically; however, restarting the base services does not automatically restart all Galaxy services. After stopping the base services, therefore, you can restart all Galaxy services or restart each service separately (base, CommServe, and MediaAgent).

Before you begin, use the Job Controller to suspend or kill all jobs. Alternately, you can wait for a job to complete.


To stop the base services 1. Click Start, point to Programs, click Galaxy and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy Base Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you prefer to start all Galaxy services manually, clear this option to disable the auto-start feature. 4. Click Stop to stop the base services. 5. When prompted to continue, click Yes only if it is acceptable to stop the other services. When the base services are stopped successfully, the Galaxy Service Control Manager dialog box updates the Galaxy Base Services status from Running to Stopped. 6. Optionally, you can verify which services you have stopped by clicking Services in Control Panel.




To start the base services 1. Click Start, point to Programs, click Galaxy, and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy Base Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you prefer to start all Galaxy services manually, clear this option to disable the auto-start feature. 4. Click Start to restart the Base services. When the base services are restarted successfully, the Galaxy Service Control Manager dialog box updates the Galaxy Base Services status from Stopped to Running. 5. Optionally, you can verify which services you have stopped by clicking Services in Control Panel.

Chapter 4: Advanced Backup and Restore Operations 155

6. Resume any jobs you suspended prior to stopping the base services.

Stopping and Starting the CommServe Services The following procedures describe how to stop and restart the CommServe services. Note: Stopping the CommServe services also stops all Galaxy operations within the CommCell.

Before you begin, use the Job Controller to suspend or kill all jobs. Alternately, you can wait for a job to complete.


To stop the CommServe services 1. Click Start, point to Programs, click Galaxy, and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy CommServe Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you want to start all Galaxy services manually instead, clear this option to disable the auto-start feature. 4. Click Stop to stop the CommServe services. When the CommServe services are stopped successfully, the Galaxy Service Control Manager dialog box updates the Galaxy CommServe Services status from Running to Stopped. 5. Optionally, you can verify which services you have stopped by clicking Services in Control Panel.




To start the CommServe services 1. Click Start, point to Programs, click Galaxy, and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy CommServe Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you want to start all Galaxy services manually instead, clear this option (to disable the auto-start feature). 4. Click Start to restart the CommServe services. When the CommServe services are restarted successfully, the Galaxy Service Control Manager dialog box updates the Galaxy CommServe Services status from Stopped to Running. 5. Optionally, you can verify which services you have started by clicking Services in Control Panel. 6. Resume any jobs you suspended prior to stopping the CommServe services.

156 Backup and Restore for Internet Data Center

Stopping and Starting the MediaAgent Services The following procedures describe how to stop and restart the Galaxy services that apply to the MediaAgent. Note: Stopping or starting the MediaAgent services stops or starts only the Galaxy Media Mount Manager service, DMS, and LMS; that is, operations for all Galaxy resources that depend on that MediaAgent are stopped or started.

Before you begin, use the Job Controller to suspend or kill all jobs. Alternately, you can wait for a job to complete.


To stop the MediaAgent services 1. Click Start, point to Programs, click Galaxy, and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy MediaAgent Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you want to start all Galaxy services manually instead, clear this option to disable the auto-start feature. 4. Click Stop to stop the MediaAgent services. When the MediaAgent services are stopped successfully, the Galaxy Service Control Manager dialog box updates the Galaxy MediaAgent Services status from Running to Stopped. 5. Optionally, you can verify which services you have stopped by clicking Services in Control Panel.




To start the MediaAgent services 1. Click Start, point to Programs, click Galaxy, and then click Galaxy Service Control Manager. 2. In the Galaxy Service Control Manager dialog box, in the Services field, click Galaxy CommServe Services. 3. By default, the Auto-Start Services when OS Starts option is selected, meaning that all Galaxy services applicable to the local system will start automatically when the system is restarted. If you want to start all Galaxy services manually instead, clear this option to disable the auto-start feature. 4. Click Start to restart the MediaAgent services. When the MediaAgent services are restarted successfully, the Galaxy Service Control Manager dialog box updates the Galaxy MediaAgent Services status from Stopped to Running. 5. Optionally, you can verify which services you have started by clicking Services in Control Panel. 6. Resume any jobs you suspended prior to stopping the MediaAgent services.

Chapter 4: Advanced Backup and Restore Operations 157

Operation Window An operation window is a daily time period when a specific type of operation is allowed to occur. The main purpose of this feature is to help you prevent an unexpected, time-consuming operation from disrupting normal operations. Operation windows can be established either for the entire CommCell or for a specific iDataAgent. By default, all operations can be conducted at any time. If a job is submitted outside of its window of operation, Galaxy puts the job into a pending status until the window of operation becomes valid. (This is reflected in the job’s pending status in the Job Controller window.) For example, if you restrict backups to a 6:00 P.M. to 7:00 A.M. operation window, a backup that is scheduled for 1:00 P.M. remains pending until 6:00 P.M. If a job is started within its window of operation, but does not complete before the operation window expires, Galaxy manages the job in one of the following ways: ● Restartable jobs (it can be stopped and restarted at the point of suspension), are put into a pending status when the window expires, then restarted when the window of operation becomes valid again. In the preceding example, if a backup is still running when the 7:00 A.M. operation window expires, Galaxy suspends it until the next backup operation window begins at 6:00 P.M. ● Non-restartable, are allowed to run to completion.

CommCell Operation Windows You can establish operation windows for the entire CommCell from the Operation Window tab of the CommCell Properties dialog box. Table 4.6 lists the options that can be included in this tab. Table 4.6: Operations Window options All Backups

Defines the daily time period during which any backup (other than full) can occur.

Full Backups

Defines the daily time period during which a full backup can occur. To be effective, this operation window must be within the All Backups operation window at the CommCell level.

Synthetic Full Backups

Defines the time period in which Synthetic Full backup operations can occur. To be effective, this operation window must be within the All Backups operation window at the CommCell level. For information on Synthetic Full backups, see the online Help for the iDataAgents that support this backup type.

ExpressRecovery Backups

Defines the time period during which ExpressRecovery backups can occur.

Restores

Defines the daily time period during which standard restore operations can occur.

Auxiliary Copies

Defines the time period in which auxiliary copy operations can occur.

158 Backup and Restore for Internet Data Center

Also included under this tab is the time zone for the CommServe (for example, Eastern Standard Time).


To set an operation window at the CommCell level To carry out this procedure, you must have Administrative Management permissions on the Galaxy system. 1. In the CommCell Browser, right-click CommServe, and then click Properties. 2. On the Operation Window tab, set the desired starting and ending times of the operation windows.

iDataAgent Operation Windows Operation windows can be established at the iDataAgent level for backup and restore operations. When specified at the iDataAgent level, the operation windows apply only to those operations that originate from the specified iDataAgent. The operation windows that are established at the CommCell level apply across the entire CommCell. If you establish operation windows at both levels for any given operation, the effective operation window becomes the times in common to both levels; for example, if restores are permitted between 1:00 P.M. and 5:00 P.M. at the CommCell level and between 2:00 P.M. and 6:00 P.M. for a given iDataAgent, the effective operation window for restores is between 2:00 P.M. and 5:00 P.M. for that iDataAgent. Restores that originate from some other iDataAgent are still valid between 1:00 P.M. and 5:00 P.M. (that is, the CommCell operation window), provided a restore operation window for that iDataAgent does not exist. For additional details on the operation windows established at the iDataAgent level, see online Help for iDataAgent-specific information.

Job Priorities Galaxy job priorities are used to determine which of several competing jobs can access limited resources (such as media drives and backup media); the job with the highest priority gets the resources. When multiple jobs have the same priority, resources are allocated on a first-come, first-served basis. When a job completes, the system allocates the newly freed resources to the next job. If a job fails, the system attempts to restart it one hour later and as many as 72 times (default settings). The way that Galaxy manages jobs is also influenced by the job category: restartable or non-restartable. If a running job is using resources needed by another job with a higher priority, Galaxy will manage the jobs in one of two ways: ● If the running job is restartable, Galaxy interrupts the running job and then allocates the resources to the higher-priority job. (The interrupted job enters a waiting state and then resumes when the resources it needs become available.)

Chapter 4: Advanced Backup and Restore Operations 159 ●

If the running job is not restartable, it runs to completion, regardless of priority of the new job.

Note: Archive pruning jobs cannot start when restores, backup index restores, or auxiliary copy operations are in progress.

Job Priority Overview When any job is started, the Galaxy Job Manager assigns the job a priority number: the lower the number, the higher the priority. The priority of a given job is based on the following: ● Priority of the operation type ● Priority of the client computer that is performing the operation ● Priority of the type of iDataAgent from which the operation originated ● Priority precedence (the weighting of the priority of the client computer relative to the priority of the iDataAgent)

Job Priority Number Each job priority number is based on a three-digit integer; leading zeroes are suppressed. Each digit within this number represents a different priority field as shown in Figure 4.7. Client Precedence

Job Priority Operation Priority Backup, Synthetic Full=3; Client Priority (0-9; UseriDataAgent Priority (0-9; User-

XYZ

iDataAgent

Job Priority Operation Priority Backup, Synthetic Full=3; iDataAgent Priority (0-9; UserClient Priority (0-9; User-

XZY

Figure 4.7 Job Priority Numbers

The first digit represents the priority of the job operation. The second and third digits, by default, represent the priorities of the client computer and iDataAgent respectively. You can also change their order of precedence so that they represent the priorities of the iDataAgent and client computer respectively. The following sections discuss each of these topics is greater detail.

160 Backup and Restore for Internet Data Center Operational Priority

Galaxy assigns priorities for all operation types. These priorities, which represent the first and most significant digit of the three-digit priority number, are fixed and cannot be changed. The priority assignments are shown in Table 4.7; note that restore operations have the highest priority, and Synthetic Full backups have the lowest. Table 4.7: Operational priorities Job operation

Assigned priority

Restores

0

Backups

1

Synthetic Full

3

Client Computer Priority

By default, Galaxy assigns the same priority (9 – the lowest) to all client computers. As a result, the Job Manager evaluates all client computers as having the same priority. If desired, you can change the priority of any client computer so that its operations are given a higher priority than another. For example, you may want operations originating from a specific file server to take precedence over operations originating from users’ computers. In such a case, you would assign a higher client priority to the file server than to the other computers within the CommCell. Client priority is configured at the client-computer level. iDataAgent Priority

By default, Galaxy assigns the same priority (9 – the lowest) to all iDataAgents within a CommCell. As a result, the Job Manager evaluates all iDataAgents as having the same priority. You can change the priority of any iDataAgent so that its operations are given a higher priority than those of another iDataAgent. For example, you may want database backup and restore operations for Microsoft Exchange to take precedence over Windows 2000 file system operations. In such a case, you would assign a higher priority to the database iDataAgent for Exchange 2000 Server than to the iDataAgent for Windows 2000. The iDataAgent priority is configured at the CommCell level. Therefore, the priority that you assign to any iDataAgent is effective for operations that originate from that iDataAgent for all client computers within the CommCell.

Chapter 4: Advanced Backup and Restore Operations 161

Default Job Priorities

The default job priority numbers for various operation types are shown in Table 4.8. Table 4.8: Default job priorities Job operation

Default job priority

Archive Pruning

0

ExpressRecovery backups

1

Restore

99

Backup

199

Auxiliary copy

299

Synthetic full backup

399

Because Archive Pruning and ExpressRecovery backup operations are not associated with any client or iDataAgent, they have no second or third digits. Therefore, they are the highest priority Galaxy jobs. The Auxiliary Copy operation also has no associated client or iDataAgent; therefore, Galaxy keeps the priority at 299 and it has a lower priority than backup and restore operations.

Customizing Job Priorities The priorities for administrative operations (for example, Archive Pruning, Auxiliary Copy, and ExpressRecovery backups) are assigned by Galaxy and cannot be customized. However, you can customize the priorities of client-oriented operations (for example, backups, restores, and Synthetic Full backups) by changing any of the following: ● Priority precedence ● Client computer priority ● iDataAgent priority Priority Precedence

By default, the client computer, which is represented by the second digit, has precedence over the iDataAgent, which is represented by the third digit. You can reverse the order of these digits, and thus the precedence, so that the iDataAgent has precedence over the client computer. An example of this is the effect that priority precedence can have when you customize client computer and iDataAgent priorities. Assume there are two client computers; opal and coal. Client opal is a file server that uses the iDataAgent for Windows 2000. Client coal is an server running Exchange that uses the database iDataAgent for Exchange 2000 Server.

162 Backup and Restore for Internet Data Center

The job priorities for backup operations from each client computer are shown in Table 4.9; note that different backup operations have a higher priority (lower number) depending on the setting of the priority precedence. When the priority precedence is set for Client, the File System backup from opal has the higher priority. When the priority precedence is set for iDataAgent, the Exchange Database backup from coal has the higher priority. The corresponding Restore and Synthetic Full backup operations would yield similar results. Table 4.9: Priority precedence settings Priority precedence setting Operation

Client

iDataAgent

Backup, File System for Windows 2000, Client opal

186

168

Backup, Exchange Database, Client coal

194

149

Viewing Job Priorities By default, the Job Controller window does not display the priorities of running jobs. To view the job priorities for all jobs, you need to enable the Priority column as described in the procedures in online Help.

Job Control The Job Controller allows you to manage jobs and view detailed information about them. Information about a job is continually updated and available in the Job Controller window as long as the job exists. When a job is completed, the information about that job is removed from the Job Controller window. If the job was a backup or restore operation, you can still obtain job information by using the backup or restore history feature. For information on viewing backup or restore history, see online Help for iDataAgent-specific details.

Job Controller Windows You should be familiar with the following before attempting to manage jobs: ● Job Details dialog boxes ● Job Controller window The Job Controller window displays all the current jobs in the CommCell. Table 4.10 shows the information displayed by default by the Job Controller.

Chapter 4: Advanced Backup and Restore Operations 163

Table 4.10: Information shown in the Job Controller display




Job ID

A numeric identifier, unique within the CommCell, identifying the backup, restore, or administrative job.

iDataAgent

The Galaxy software module from which the job originated (for example, iDataAgent for Windows 2000).

User

The Galaxy user who initiated the job.

Operation

Description of the job being performed (backup, restore, and so on).

Status

Current job status.

Client Computer

For backup operations: The computer from which the operation is being performed. For restore operations the computer from which the restored data was originally backed up

Progress

A status bar indicating the job’s progress. The progress bar is not visible for certain operations (for example, archive pruning) or for the initial phases of some backup operations.

Priority (not displayed by default)

Job priority number.

Start (not displayed by default)

The time (and date) the job started.

Elapsed (not displayed by default)

The time lapsed since the job started, updated periodically.

To open the Job Controller and rearrange columns Generally the Job Controller is in view when you first open the CommCell Console. If however, you closed the Job Controller window, you can reopen it as follows. ● On the CommCell Console, click the Job Controller icon. ● Drag and drop the headings of the columns that you want to rearrange. The columns will return to their original order if you close and reopen the Job Controller window.




To hide or display columns in the Job Controller 1. Click the Job Controller window to make it active. 2. In the CommCell Console, on the View menu, click Table. A list of Job Controller columns appears with a check mark next to each displayed column. 3. Click the name of a checked column to hide it. Click the name of a cleared column to display it. Note: You cannot display fewer than three columns.

164 Backup and Restore for Internet Data Center

Controlling Galaxy Jobs The Job Controller allows you to manually control jobs by using the operations shown in Table 4.11. Table 4.11: Job Controller operations Suspend

Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time. Only restartable jobs can be suspended.

Resume

Resumes a stopped job and returns the status to Waiting, Pending, or Running depending on the availability of resources, or the state of the operation window and activity control settings.

Kill

Terminates a job.

View Events

Allows you to view the events for the job.

Detail

Displays information about the selected job.

The ability to suspend specific jobs depends on their job category; either restartable or non-restartable.

Job Status Levels A job may have one of eight status levels, as shown in Table 4.12. Table 4.12: Job status levels Running

The job is active and has access to the resources it needs.

Waiting

The job is active, waiting for resources (for example, media drives) to become available or for internal processes to start.

Interrupt Pending

Galaxy has suspended the job and is waiting for the completion of associated processes before stopping the job.

Pending

Galaxy has suspended the job and will restart it without user intervention. A pending job may be waiting for a valid operation window, or it may have failed and is waiting for Galaxy to restart it.

Stop Pending

You have suspended the job, and Galaxy is waiting for the completion of associated processes before stopping the job.

Stopped

By using the Suspend option, you have manually stopped the job. It will not complete until you restart it by using the Resume option.

Kill Pending

The job has been terminated, and Galaxy is waiting for the completion of associated processes before killing the job.

Killed

The job is terminated and removed from the Job Controller window.

The status of a job determines the Job Controller actions (kill, suspend, or resume) that you can perform and the resulting status, as shown in Table 4.13.

Chapter 4: Advanced Backup and Restore Operations 165

Table 4.13: Job status actions available Original status

Actions available

New status

Running

Suspend

Stopped

Kill

N/A

Suspend

Stopped

Kill

N/A

Interrupt Pending

N/A

N/A

Pending

Suspend

Stopped

Kill

N/A

Stop Pending

N/A

N/A

Stopped

Resume

Returns to original state, resources and other conditions permitting

Kill

N/A

N/A

N/A

Waiting

Kill Pending




To suspend a job To carry out this procedure you must have Job Management capability on the Galaxy system. 1. Right-click the job and then click Suspend. 2. The job state changes to Stop. (The job status may first change to Stop Pending for a few moments while an operation completes.)




To resume a suspended job 1. Right-click the job and then click Resume. 2. The Job Manager attempts to restart the job; the job status changes to Waiting, Pending, or Running.




To kill a job 1. Right-click the job and then click Kill. 2. If you are sure you want to kill the job, click Yes when the confirmation prompt appears. Note: The job status may change to Kill Pending for a few moments while the operation completes. After the operation completes, the job status will change to Killed and be removed from the Job Controller window.

3. In the Job Status dialog box, click Detail to see the Job Details dialog box for the

terminated job, or click OK to close the dialog box.

166 Backup and Restore for Internet Data Center


To view events on a particular job 1. Right-click the job and then click View Events. 2. The All Found Events window appears. Use this window to view all of the events associated with a particular job. See online Help for details.




To view details on a particular job 1. Right-click the job and then click Details. 2. The appropriate details window appears (for example, the Backup Job Details for Job ID window.). See online Help for details.

Job Status and Job Details Dialog Boxes When each job completes, fails, or is killed, Galaxy displays the Job Status dialog box, provided the Job Controller window is open. If this window is not open, the dialog box is not displayed. Click Detail in the Job Status dialog box to view the Job Details dialog box for the completed operation. You can use the Job Controller window to view details for the following types of jobs: ● Backups ● Restores ● Synthetic Full backups ● Auxiliary copies ● ExpressRecovery backups The Job Details dialog boxes contain a wealth of information about a selected job. This information can be useful in determining job status and progress.

Activity Control The Activity Control feature allows you to enable or disable backup and/or restore operations at three levels in the Galaxy hierarchy (Table 4.14). Table 4.14: Activity Control options CommCell

Allows you to enable/disable all backup and/or restore operations for all client computers within the CommCell.

Client computer

Allows you to enable/disable all backup and/or restore operations on a specific client computer.

Client computer/ iDataAgent

Allows you to enable/disable the backup and/or restore operations of a specific iDataAgent on a specific client computer.

Chapter 4: Advanced Backup and Restore Operations 167

Order of Precedence When operations are disabled, the CommCell level has the highest priority while the client computer/iDataAgent has the lowest priority. For example, if you disable backups at the CommCell level, all backups throughout the CommCell are disabled regardless of the corresponding settings of the individual client computers and client/iDataAgents. However, if backups are enabled at the CommCell level, you can still disable backup operations at the client computer or client/iDataAgent levels. By default, all operations are enabled at all levels of the Galaxy hierarchy.

Accessing the Activity Control Feature You access the Activity Control feature from the Activity Control tab of the associated Properties dialog box. For example, to access the Activity Control feature at the CommCell level, you would open the Activity Control tab of the CommCell Properties dialog box. For information on applying activity control to a specific client computer/iDataAgent, see the appropriate online Help.


To enable or disable backup or restore operations To perform this procedure you must have CommCell-level Administrative Management capabilities on the Galaxy system. 1. In the CommCell Browser, right-click the CommServe, client computer, or client iDataAgent, and then click Properties. 2. On the Activity Control tab, select or clear one or both of the following options: ● Enable Backup. When selected, enables backups to occur. When cleared, backups are disabled. Backups cannot be started. Running and Waiting backups, if any, run to completion. Backups in the Stopped state cannot be resumed until backups are enabled. (The Job Controller indicates the Job states.) Pending backups do not run until backups are enabled. ● Enable Restore. When selected, enables restores to occur. When cleared, restores are disabled and Restores cannot be started. Running restores run to completion. Pending restores do not run until restores are enabled.

CommCell Users and Groups User Administration is an important aspect of CommCell administration. It is through proper user management that users gain access to the Galaxy CommCell in a secure manner. This section provides an overview of the Galaxy user management system and describes the methodology for creating user accounts and user groups, and assigning resources to users and groups.

168 Backup and Restore for Internet Data Center

CommCell Resources CommCell resources are manageable entities within a CommCell that perform some operation, possess configurable attributes, or both. Each CommCell has the following resources: ● The CommServe ● Each client computer ● Each Client-iDataAgent ● Each MediaAgent ● Each library ● Each storage policy The Client-iDataAgent is the combination of the client computer and an individual iDataAgent. This combination allows you to target individual iDataAgents on a client computer for different user groups, as needed.

User Access Access to a Galaxy CommCell’s resources and features is granted or denied based on a combination of the following determining factors: ● CommCell resources ● Capabilities ● User groups ● User accounts Using this approach, a CommCell administrator can provide each Galaxy user with the exact capabilities required. These requirements can vary, depending on the tasks each user needs to perform. Figure 4.8 shows an example of how resources can be distributed within a CommCell.

Chapter 4: Advanced Backup and Restore Operations 169 Capability Capability Capability Capability Capability

master Group cvadmin UserA,UserB... User Group 1 UserC,UserD...

Capability

Resource1 Resource Resource Resource Resource Resource

User Groupn UserB,UserC... Capabilityn

Resource

Capability Capability Capability Capability Capability

Resource1 master Group cvadmin UserA,UserB... User Group 1 UserC,UserD...

Capability

Resource Resource Resource Resource Resource

User Groupn UserB,UserC... Capabilityn

Resource

Resource1

Capability Capability Capability

master Group cvadmin UserA,UserB...

Capability

Resource Resource

Capability Capability

Resource

User Group 1 UserC,UserD...

Resource Resource

User Groupn UserB,UserC... Capabilityn

Resource

Figure 4.8 Distributing CommCell resources

Capabilities (Privileges) Capabilities are privileges that allow users to perform a variety of functions within a CommCell. These functions include routine operations, such as backing up or restoring data, as well as the more administrative operations such as license administration, archive pruning, or administering user accounts. Table 4.15 identifies Galaxy capabilities and their associated resources, and describes their associated operations.

170 Backup and Restore for Internet Data Center

Associating Resources and Capabilities Each capability, and its associated operation, affects only one type of resource. For example, the backup capability, which allows all users in a particular user group to perform on-demand backups, operates only on the Client-iDataAgent resources. It does not, for example, operate on a library resource, because libraries do not initiate backups themselves. When you create a user group, choose the capabilities appropriate for the resources that you will associate with that group. Table 4.15 lists the available Galaxy capabilities: Table 4.15: Galaxy capabilities Capabilities (Privileges)

Resources

Associated Operations

Licensing capabilities:

License Management

CommCell

Update license keys

CommCell Management Capabilities:

Job Management

CommCell

Suspend, resume, and kill jobs

Administrative Management

CommCell

Job pruning Server configuration Initiate auxiliary copies ExpressRecovery Enable/disable backups and restore (CommCell) Define the operation window on CommCell level Scheduling functions for administrative jobs Change network password Other administrative jobs Specify mail server for alert messages Library and drive configuration NAS client configuration

Report Management

CommCell

Run reports Scheduling functions for reports

Storage Policy Management

CommCell

Create/delete storage policies Add/delete copies Mark active media full Migrate media

User Management

CommCell

Add/delete user/ user group Enable/disable user Enable/disable user groups Associate a group with an object

Alert Management

All

Add/delete alerts for users

Chapter 4: Advanced Backup and Restore Operations 171

Capabilities (Privileges)

Resources

Associated Operations

Library and MediaAgent Management Capabilities:

Library

Move media between scratch pools Create/delete new scratch pools Discover media Import/export media Mark a drive clean Replace a drive Reset filer Reset library Set drives online/offline Migrate magnetic library

CommCell

Edit Storage Resources properties

MediaAgent Management

MediaAgent

Modify MediaAgent properties

CommCell

Forced De-configure MediaAgent

iDataAgent Management

Client iDataAgent

Enable/disable backups and restore (client or iDataAgent level) Create/modify/remove backup sets and subclients Define the operation window on the iDataAgent level Forced De-configure iDataAgent

CommCell

Forced De-configure client

Backup

Client-iDataAgent

On-demand backup operations

Browse/Restore

Client-iDataAgent

On-demand browse and restore operations

iDataAgent Scheduling

Client-iDataAgent

Backup and restore operation scheduling (This operation also requires the Backup and Browse/ Restore capabilities, respectively)

iDataAgent Capabilities:

Backup and Restore Capabilities:

Library Management

Note: Users can add themselves to an alert without Alert Management rights. However, they cannot add others to an alert.

User Groups User groups are named logical entities—containers to which capabilities, system resources, and users are assigned. This arrangement provides an extremely flexible system that allows you to specify not only the privileges for the member users, but also the resources they can access. Users who are assigned to a group are granted the group’s privileges and access to the group’s resources.

172 Backup and Restore for Internet Data Center

The master user group, which is predefined by the Galaxy system, is assigned all available rights and system resources. This group is permanent; it cannot be removed, nor can its privileges or access to system resources be curtailed. All other user groups are created and maintained as needed by members of groups that have the user management right.

User cvadmin Within the master user group is a permanent user called cvadmin. Galaxy creates the cvadmin user automatically; it is the default CommCell administrator, and this user name cannot be changed. As a member of the master user group, cvadmin has all available rights within a CommCell. Using these privileges, cvadmin can create users, groups, and user accounts at any time. Note that cvadmin can also assign additional users to the master group, thereby giving full access to other users as well.

CommCell User Accounts All CommCell users have a CommCell user account that contains basic Galaxyrelated information about the user. Users who are part of groups that have the User Management capability can create CommCell user accounts. The CommCell user accounts are specifically created to control CommCell access. A user can be a member of more than one group (and have all of the capabilities of each of those groups). If a user is not a member of any group, that user does not have any capabilities and can use the CommCell Console on a view-only basis. CommCell user accounts are completely separate entities from Windows user accounts; their purposes are different and should not be regarded as interchangeable. CommCell users need not have a Windows user account.

Managing User Groups User groups provide a convenient means of assigning a common set of capabilities and resources to a set of users. You can create any number of user groups, each having any combination of assigned capabilities. Proper user-group administration requires a certain amount of planning. Successful planning helps you minimize the number of groups, which is always desirable from an administrative standpoint. When you plan your user group strategy, take time to consider the following questions: ● Who needs access to the Galaxy system? ● What tasks will each Galaxy user need to perform? ● As an administrator, what are your security needs?

Chapter 4: Advanced Backup and Restore Operations 173

Managing Galaxy user groups requires the following administrative tasks: ● Creating user groups ● Changing user groups ● Deleting user groups Creating User Groups

User groups are created for users who require access to the Galaxy system. Each user group represents a distinct set of users, capabilities, and CommCell resources. The procedures in this section describe the following aspects of creating user groups: ● Immediate assignment. When you create a user group, you can immediately assign the users, capabilities, and CommCell resources. ● Unspecified assignment. Alternately, you can leave these assignments unspecified, which would limit the user to browsing through the CommCell.


To create a user group To carry out this procedure, you must have the User Management capability on the Galaxy system. 1. On the CommCell Browser, right-click CommCell User Groups, and then click New User Group. 2. In the New User Group Properties dialog box, on the General tab, type the following: ● Name. The name you want to assign to the user group (up to 32 characters; do not include trailing spaces). ● Description. Some descriptive information that characterizes the user group. Perhaps the users of the group belong to some department or organization. Maybe the group is more closely associated with a specific computer or a CommCell function (for example, backups). Note: If you want to leave the user group dormant (without users, capabilities, or associations), in the New User Group Properties dialog box, click OK.

3. Select Enabled if you want to activate the group (selected by default). If you

want the group to be dormant until some later time, clear the Enabled option. 4. If you want the user group to possess all Galaxy capabilities, select All Capabilities. Otherwise, leave this option cleared. 5. If you want the user group to be associated with all CommCell resources, select All Associations. Otherwise, leave this option cleared.

174 Backup and Restore for Internet Data Center

Note: The All Capabilities and All Associations options are very powerful. If they are assigned improperly, you risk exposing all the features and resources of the CommCell to users who may not have adequate training or knowledge. For this reason, these options are cleared by default.

6. At this point, you have entered all the information required to create the user

group; however, you have not yet populated the group with users nor have you associated it with Galaxy capabilities or CommCell resources. If you did not select All Capabilities, the user group has no assigned capabilities. Similarly, if you did not select All Associations, the user group has no associated CommCell resources.


To assign Galaxy capabilities to a user group 1. In the New User Group Properties dialog box, click the Capabilities tab. 2. Assign the capabilities to the user group as follows: ● To assign a capability to a user group, click the capability in the Available Capabilities pane, and then click the < button. ● To remove a capability from a user group, click the capability in the Assigned Capabilities pane, and then click the > button. ● Repeat this step for each additional capability you want to add to or remove. 3. When finished, click OK.




To assign users to a user group You can assign existing users to a user group in the New User Group Properties dialog box. This procedure is most useful when you want to establish group membership on a group-by-group basis. As an alternative, you can establish user group membership on a user-by-user basis. 1. Click the Users tab in the New User Group Properties dialog box. 2. Assign the users to the user group as follows: ● To assign a user to a user group, click the user name in the Available Users pane, and then click the < button. ● To remove a user from a user group, click the user name in the Member Users pane, and then click the > button. ● Repeat this step for each additional user that you want to add or remove. 3. When finished, click OK.

Associating CommCell Resources to a User Group CommCell resource associations enable members of a group to perform Galaxy operations on associated resources. The nature of those operations depends on the Galaxy capabilities assigned to the group. If a resource, such as a client computer, is

Chapter 4: Advanced Backup and Restore Operations 175

not associated with a given user group, the users of that group cannot perform any Galaxy operations involving that client computer. If, however, the user group was created with the All Associations option set, the group is already associated with all the resources in the CommCell, and the users have all CommCell resources at their disposal. You can associate the following resources to a user group: The CommServe ● Each client computer ● Each Client-iDataAgent ● Each MediaAgent ● Each library ● Each storage policy ●

Each of these resources supports specific functions within the Galaxy CommCell.


To associate or dissociate a CommCell resource to/from a user group In this procedure, you will associate a CommCell resource to a user group that is already established. Before starting this procedure, you should know which resources you want to associate to a given user group. 1. On the CommCell Browser, right-click the CommCell resource that you want to associate to a user group, and then click Properties. 2. In the Properties dialog box, click the Security tab. The Associated Groups pane displays the names of the user groups to which the resource is associated. The master group is always listed, because all resources are always associated to it. 3. To associate the selected resource to a user group, click the group you want in the Available Groups pane and then click the > button. Repeat this step for each user group that you want dissociated from this resource. 5. When finished, click OK.

Changing User Group Properties Galaxy allows you to change the following user-group properties: ● Description ● Assigned capabilities ● Associated CommCell resources ● Assigned users ● Enabled/disabled

176 Backup and Restore for Internet Data Center

Note: Although you cannot change a user group name, you can delete the group and then create a new group with matching attributes and a new name.

All changes are effective immediately, regardless of whether a user from the user group is logged on.


To change the properties of a user group 1. In the CommCell Browser, click CommCell User Groups. 2. In the right-hand pane of the CommCell Browser, right-click the user group whose properties you want to change, and then click Properties. 3. In the User Group Properties dialog box, change the properties as needed. 4. When finished, click OK.

Deleting User Groups On occasion, you may want to delete a user group. This could be when your CommCell has grown to a size where you need to reassess and reorganize user responsibilities, or when the functions or membership of a particular user group have become obsolete. Under these circumstances, you may want to delete a user group and create a new one instead of changing the existing user group. The following procedure guides you through this process. Note: You cannot delete the master user group. The master user group is the primary CommCell administrator (cvadmin) user group and remains available at all times. For the master user group, the Description field is the only property you can change.

To carry out this procedure you must have the User Management capability on the Galaxy system.


To delete a user group 1. From the CommCell Browser, click the CommCell User Groups icon. 2. In the right-hand pane of the CommCell Browser, right-click the user group you want to delete, and then click Delete. 3. When the system prompts you to confirm the deletion, click Yes to delete the user group or click No to cancel the deletion and leave the user group intact.

Managing User Accounts Managing Galaxy user accounts includes the following tasks: ● Creating user accounts ● Changing user accounts ● Deleting user accounts

Chapter 4: Advanced Backup and Restore Operations 177

Creating User Accounts User accounts are created for users who need to access the Galaxy system. Each user must have a separate account. When you create a user account, you can immediately assign the account to the available user groups or leave the account unassigned. The following procedures describe both activities. To carry out this procedure you must have User Management capability on the Galaxy system.


To create a user account 1. In the CommCell Browser, right-click CommCell Users, and then click New User. 2. In the New User Properties dialog box, on the General tab, type the following required information: ● User Name. The name that you want the user to type when they log on to the Galaxy system (up to 32 characters; do not include trailing spaces). ● Password. The password that you initially assign to the user (up to 32 characters; do not include trailing spaces). (Users can change their own passwords.) ● Confirm Password. A confirmation of the Password. 3. Optionally, you can enter the following additional user information: ●

●

●

Full Name. The real name of the person to whom the account is assigned (up to 32 characters; do not include trailing spaces). Description. Some descriptive information about the user, such as a job title, department, or organization name. E-Mail. The user’s e-mail address.

4. If you want to enable the user account immediately, select Enabled (selected by

default). If you want to create the account, but leave it inactive until some later time, then clear the Enabled option. 5. If you want the user’s password to expire on a periodic basis, select Age Password and then select the number of days for which the password is to remain valid. If you do not want the user password to expire, leave this option cleared (it is cleared by default). A password age of one day means that the password expires at midnight of the present day. Note: Unless you assign the user account to a user group, the user will not have any Galaxy capabilities after logging on.

6. Decide whether to assign the new user to a user group: ● ●

To leave the user unassigned, in the New User Properties dialog box, click OK. To assign the user to a user group, click the User Groups tab and follow the next procedure.

178 Backup and Restore for Internet Data Center

The following procedure demonstrates how to assign a user to one or more user groups by using the User Properties dialog box. This procedure is most useful for establishing group membership on a user-by-user basis. As an alternative, you can establish user group membership on a group-by-group basis.


To assign a user to a user group 1. Click the User Groups tab of the New User Properties dialog box. 2. Assign the user to the user groups as follows: ● To assign the user to a user group, in the Available Groups pane, click the group and then click the < button. ● To remove the user from a user group, in the Member Groups pane, click the group and then click the > button. 3. When finished, click OK.

Changing the Properties of a User Account The Galaxy system allows you to change the following user-account properties: ● Password (and password aging) ● Full name ● Description ● E-mail address ● Enabled/disabled ● User-group memberships Note: You cannot change the User Name property; however, you can delete an account and then create a new account with another user name. The only properties you can change for the cvadmin user account are the password and the e-mail address.

All changes are effective immediately, regardless of whether the user is logged on, except in the following instance: If a user is logged on and you disable his or her account, he or she will still be able to use the CommCell console; however, he or she will be denied access after he or she has logged off. To perform this procedure you must have User Management capability on the Galaxy system.


To change the properties of a user account 1. From the CommCell Browser, click the CommCell Users icon. 2. In the right pane of the CommCell Browser, right-click the user whose account properties you want to change, and then click Properties. 3. In the User Properties dialog box, change the properties as needed. 4. When finished, click OK.

Chapter 4: Advanced Backup and Restore Operations 179

Deleting a User Account One of the usual duties associated with user management is the deletion of user accounts. Deletions are effective immediately, unless the user being deleted is logged on to the Galaxy system. In this case, the deleted user will still be able to use the CommCell console; however, he or she will be denied access after he or she has logged off. Note: You cannot delete the cvadmin user account. User cvadmin is the primary CommCell administrator and remains enabled at all times.

To perform this procedure, you must have User Management capability on the Galaxy system.


To delete a user account 1. In the CommCell Browser, click the CommCell Users icon. 2. In the right pane of the CommCell Browser, right-click the user you want to delete, and then click Delete. 3. When the system prompts you to confirm the deletion, click Yes to delete the user or click No to cancel the deletion and leave the user account intact.

CommCell Network Password The CommCell network password is an internal security measure used to ensure that Galaxy communications occur only between CommCell computers. By default, Galaxy assigns each computer in the CommCell a different password. You can, at any time, define a new CommCell network password for any computer in the CommCell. Although you do not need to know the existing password to define a new one, you do need to have the Administrative Management capability. Note: The CommCell network password is not a user-level password; no user will ever need to enter this password. It is used only on an internal basis.

To carry out this procedure, you must have Administrative Management capability on the Galaxy system. 1. In the CommCell Browser, right-click the CommCell icon, and then click Change Network Password. 2. In the Change Network Password dialog box, select the computer whose network password you want to change. 3. In the New Password field, type new network password and in the Confirm Password field re-type it. 4. When finished, click OK. Galaxy changes the password of the selected computer.

180 Backup and Restore for Internet Data Center

Job Scheduling Scheduling the jobs within your CommCell helps ensure that the data that you want to safeguard is secured automatically on a regular basis.

Designing Backup Schedules Use either the Schedule Wizard or the CommCell Browser to schedule backups. Within the CommCell Browser, you can schedule backups at various levels in the Browser tree by right-clicking the entity that you want to back up and selecting the appropriate menu options. If your iDataAgent supports backup sets, you can schedule a backup for either a subclient or an entire backup set. Scheduling at the backup set level provides the convenience of scheduling all subclients in one step. Note: When establishing a backup schedule for an entire backup set, keep in mind that each subclient will initiate a backup at the scheduled time. If two or more subclients are associated with the same storage policy, their backups may run serially. That is, it is possible that one subclient will back up at the specified time, but the other(s) will queue until the storage policy is free.

Depending on the iDataAgent, Galaxy allows you to schedule some or all of the following: ● Full backups ● Incremental backups ● Differential backups ● Synthetic Full backups ● Preselected backups (the exact type of the preselected backups depends on what you select during iDataAgent installation) Before You Begin: When you create a backup schedule, you should establish a full backup cycle. Try to ensure that the backups that comprise a full backup cycle are complementary. For example, if a schedule calls for daily incremental backups with full backups to occur every week, make sure that the incremental backup skips the day that the full backup is scheduled to run, avoiding unnecessary backups and collisions. ● If you are scheduling backups to establish a full backup cycle, keep in mind that the full backup cycle should be reflective of the associated retention period. For those iDataAgents that support backup sets, if you are scheduling for an entire backup set, then you should consider the storage policy retention periods for all constituent subclients. ●

Chapter 4: Advanced Backup and Restore Operations 181 ●

●

●

If your CommCell has several client computers, try to coordinate your backups to minimize media, media drive, and possible network contention. To secure all data for a given iDataAgent on a client computer, be sure to define backup schedules either for all subclients within the iDataAgent or for a backup set (if backup sets are supported). Check to see whether an operational window has been established for the type of backup operation that you want to schedule. If an operational window exists, be sure to schedule the backup within the valid time frame.

Designing Restore Schedules A scheduled restore operation relieves you of having to manually initiate the restore. Before you begin, if your CommCell has several client computers, try to coordinate your restore operation to minimize media, media drive, and possible network contention. Check to see whether an operational window has been established for restore operations. If an operational window exists, be sure to schedule the restore within the valid time frame. The following procedures are available in online Help under the topic job scheduling: ● Adding a scheduled job ● Modifying a scheduled job ● Deleting a scheduled job

Establishing Holidays on Which No Scheduled Tasks Run Galaxy allows you to establish holidays on which no scheduled tasks will run. This feature affects only scheduled tasks, and it affects all such tasks. (Immediate tasks are allowed to run.) Holidays are defined at the CommCell level and are evaluated in the CommServe Time Zone. You can establish a holiday for a specific date within a given year or for a specific month/day on a yearly basis (annually). Only one holiday per date is allowed. If you set a holiday to occur on an annual basis, this supersedes any holiday that is set for the same month/day and specific year. You can also add or delete holidays. Unless it is an annual holiday, a holiday is automatically deleted after it has expired. Annual holidays never expire. Events and alerts are sent for scheduled items that are skipped due to holidays.


To add or delete a holiday 1. In the CommCell Browser, right-click the CommCell icon, and then click Set Holidays. The Holidays window appears with the current holidays displayed. 2. Add or delete holidays.

182 Backup and Restore for Internet Data Center

Alert Notifications An alert is an e-mail message sent by Galaxy, by using the mail server designated on the General tab of the CommCell properties box, to inform the message recipient that a particular Galaxy event has occurred or user action has been taken. For example, if you configure an alert for changes to CommCell properties, an alert message is dispatched to the designated user when a property at the CommCell level is changed. Or, if you configure an alert for successful backups at the Client Computer level, the selected users will receive an alert message for each successful backup for all iDataAgent installed on that client. You can configure alerts by selecting one or more events and then selecting which users are to receive alerts for the selected events. Events that are available for alert configuration are listed on the Alert tab of the object’s Properties dialog box. You can configure alerts at the CommCell, Client, iDataAgent, Instance, MediaAgent, Library, and Storage Policy levels. Alerts configured at a higher level in the Galaxy hierarchy affect all lower levels. For example, if you configure an alert for successful backups at the Client Computer level, all successful backups for all iDataAgents on that client will initiate an alert message.

Galaxy Capabilities and Alerts Galaxy capabilities allow system administrators to assign specific user groups permission to perform particular Galaxy operations. Then, by adding users to those user groups, the system administrator can manage which users can perform which operations in Galaxy. The Alert Management capability allows a system administrator to control which user accounts have permission to configure alerts. Users can configure their own alerts, regardless of group membership. However, to configure alerts for other users you must belong to one of the following user groups: ● The master group ● A user group that has the Alert Management capability that is associated with the object for which you want to configure the alert. For example, if you want to configure an alert for the file system iDataAgent or MediaAgent for another user, the user group with the Alert Management Capability must be associated with the file system iDataAgent or MediaAgent objects. The master user group is assigned all Galaxy capabilities by default and is associated with all objects in the Galaxy hierarchy. Configuring alert notification requires the Administrative Management or Alert Management capabilities on the Galaxy system.

Chapter 4: Advanced Backup and Restore Operations 183




To configure alert notifications 1. In the CommCell tree, right-click the CommCell icon and click Properties. 2. On the General tab, designate an e-mail server for alert message management and then select the events you want to configure from the Alert tab as follows: ● Alert. The category of alerts. Alerts are displayed only at their appropriate level. ● Event. The individual events or conditions that produce alert messages. ● Users. List of users who receive an alert e-mail when the event occurs. ● Edit. Displays the User Alert window where you assign users to events for notification. The User Alert window contains the following fields: ● Users to be Notified. Listed users receive alert messages for the selected events. ● Available Users. These users are candidates to receive alert messages for the selected events. 3. Click Edit and select the user that you want to add to the Users to be Notified

list by clicking the < button. To remove a user from the Users to be Notified list, click the > button. 4. Click OK to confirm the users to be notified, and then click OK again.

Table 4.16 identifies the alerts that can be displayed at each level of the CommCell. Table 4.16: CommCell alerts Alert

CommCell

Scheduler Added

X

Deleted

X

Failed to Schedule Job

X

Holidays Modified

X

Modified

X

Scheduled Job Ran Late

X

Skipped Due to Holiday

X

Skipped Scheduled Jobs

X

Archive Pruning Completed With Warning(s)

X

Failed

X

Failed to Start

X

Job Aborted

X

Killed by User

X

Succeeded

X

Client

iDataAgent

Instance

MediaAgent

Library (Tape)

Library (Magnetic)

Storage Policy

184 Backup and Restore for Internet Data Center

Available Alerts

Alert

CommCell

Client

iDataAgent

Instance

MediaAgent

Library (Tape)

Library (Magnetic)

Storage Policy

Auxiliary Copy Completed With Warning(s)

X

Failed

X

Failed to Start

X

Job Aborted

X

Killed by User

X

Succeeded

X

Synthetic Full X

Failed

X

Failed to Start

X

Job Aborted

X

Job Interrupted

X

Job Restarted

X

Killed by User

X

Resumed by User

X

Succeeded

X

Suspended by User

X (continued)

Chapter 4: Advanced Backup and Restore Operations 185

Completed With Warning(s)

CommCell

Express Recovery Backup set(s) Pruned

X

Completed With Warning(s)

X

Failed

X

Failed to Start

X

Job Aborted

X

Killed by User

X

Succeeded

X

CommCell Alert Modified

X

CommCell Database Disk Space Low

X

Forced De-configure

X

Properties Modified

X

Unauthorized Attempt to Alter Properties

X

Unauthorized Attempt to Modify Alerted Users

X

Client

iDataAgent

Instance

MediaAgent

Library (Tape)

Library (Magnetic)

Storage Policy

186 Backup and Restore for Internet Data Center

Alert

Alert

CommCell

Client

iDataAgent

Instance

Failed

X

X

X

X

Failed to Start

X

X

X

X

Job Aborted

X

X

X

X

Job Interrupted

X

X

X

X

Job Restarted

X

X

X

X

Killed by User

X

X

X

X

Resumed by User

X

X

X

X

Succeeded

X

X

X

X

Suspended by User

X

X

X

X

Failed

X

X

X

X

Failed to Start

X

X

X

X

Job Aborted

X

X

X

X

Killed by User

X

X

X

X

Succeeded

X

X

X

X

New Content Added

X

X

X

X

Properties Modified

X

X

X

X

Unauthorized Attempt to Alter Properties

X

X

X

X

MediaAgent

Library (Tape)

Library (Magnetic)

Storage Policy

Backup

Client Properties

(continued)

Chapter 4: Advanced Backup and Restore Operations 187

Restore

CommCell

Client

iDataAgent

Instance

MediaAgent

Library (Tape)

Library (Magnetic)

X

Storage Policy

MediaAgent Properties Modified

X

X

Switched On/Off-line

X

X

Unauthorized Attempt to Alter Properties

X

X

Below Low Media Threshold

X

X

X

Duplicate Barcode/Label

X

X

X

Enabled/Disabled

X

X

X

Magnetic Library Out of Space

X

X

Properties Modified

X

X

X

X

Switched On/Off-line

X

X

X

X

Thresholds Exceeded

X

X

X

Unauthorized Attempt to alter properties

X

X

X

Media is Not in Library

X

X

X

Mount Error

X

X

X

No Spare Media

X

X

X

Unmount Error

X

X

X

Library

X

X

Tape

Storage Policy Properties Modified

X

X

Unauthorized Attempt to alter properties

X

X

188 Backup and Restore for Internet Data Center

Alert

Chapter 4: Advanced Backup and Restore Operations 189

Auxiliary Copy For a full understanding of this feature, you should have some basic knowledge of storage policy configuration.

Auxiliary Copy Overview Galaxy performs backups through the primary copy only. However, you can use the auxiliary copy operation to copy the backup data that was created on a primary copy from the primary copy to all secondary copies within a storage policy. This copies the data as a true image of the primary copy, archive file for archive file. After the data has been copied, it is available for the length of time specified by the copy’s data retention period. The auxiliary copy feature can be useful for creating hot standby backup copies. The primary and secondary copies use different media and often use different libraries, depending on the configuration. If the primary copy path becomes inoperative, perhaps due to a storage media failure, or a library or network malfunction, you can promote a secondary copy to become the primary copy. This allows you to continue operations as before and make repairs without interrupting backup and restore operations. When you start an auxiliary copy operation, you select the storage policy for which you want the copy (or copies) created. The primary copy of the specified storage policy serves as source of the data. If the storage policy does not have a secondary copy, you must define a new one on that storage policy. Auxiliary copies cannot copy data to another storage policy. When an auxiliary copy is started, Galaxy copies all unpruned data (that is, all data if pruning has not yet occurred, or the data remaining after a pruning operation) from the primary copy to all active secondary copies within the storage policy as shown in the Figure 4.9. (Secondary copies that are not in the active state do not participate in the auxiliary copy operation.) Note: Pruning is the process of deleting all data that have exceeded their defined retention period.

Auxiliary Copies vs. Standard Backups

An auxiliary copy should not be confused with a standard backup operation. The two operations are unrelated, except of course that a backup must precede an auxiliary copy. In all other ways the two operations are distinct and must be initiated or scheduled individually. A backup operation is specific to a particular subclient, copying the subclient content from the client computer to the primary storage policy copy. An auxiliary copy however, does not involve subclients; instead, it copies backed up data from the primary copy to one or more secondary copies. If you want the auxiliary copy to capture the backup data of only one subclient, you must ensure that the subclient has a dedicated storage policy.

190 Backup and Restore for Internet Data Center Retention Periods, Subclients, and Copies

Retention periods are defined on a copy basis. This is important for auxiliary copy operations, because it allows you to specify different retention periods for the primary backups and the auxiliary copies. When you create secondary copies, you should set the corresponding retention period to be equal to or greater than the retention period of the primary copy. This arrangement helps to ensure that secondary copy data is not pruned before the corresponding primary data. Note: To promote consistent data availability of the entire File System, it is recommend that all subclients within a backup set be associated either with the same storage policy or with storage policies whose primary copies have the same retention period.

Figure 4.9 demonstrates the relationships between retention periods and copies. Copy 1

Storage Policy A

To Backup Media

Subclient: onyx, File System, BK1, default onyx, File System, BK1, sales ruby, MSExchMB, BK1, default

Copy 2

To Backup Media

Subclient: onyx, File System, BK1, default onyx, File System, BK1, sales ruby, MSExchMB, BK1, default

Storage Policy B

Copy 1

Retention Period: 2 weeks, 2 fulls

Retention Period: Unlimited

To Backup Media

Subclient: ruby, FILESYSTEMT, BK1, default

Retention Period: 4 weeks, 2 fulls

primary copy path secondary copy path Subclient = Computer, iDataAgent, Backup Set, Subclient

Figure 4.9 Retention periods and copies

Using the example in Figure 4.9, we can make the conclusions displayed in the following table.

Chapter 4: Advanced Backup and Restore Operations 191

Table 4.17: Retention periods and copies conclusions Storage Policy

Copy

Description

A

1

This is the primary copy for storage policy A. It has a retention period of two weeks and two full backup cycles. Being the primary copy, the backups from all subclients that are associated with this storage policy automatically use this copy. Furthermore, all backup data for this copy is retained according to the same criteria.

2

This is a secondary copy and is used to create auxiliary copies for storage policy A. For this copy, all subclients have an unlimited retention period. These retention periods are appropriate if you intend to store the media for some indefinite length of time.

1

This is a primary copy for storage policy B. In this example, it is used for the backup data of the default File System subclient on client computer ruby.

B

Promoting a Secondary Copy to be the Primary Copy

Should the primary copy become inoperative, perhaps due to a library or network malfunction, all backup operations originating from the parent storage policy are non-functional. Additionally, restore operations may not complete successfully. Galaxy enables you to secure and retrieve data using secondary copies, allowing you to make repairs without interrupting Galaxy operations. If the primary copy becomes inoperative, you may be able to promote a secondary copy to become the primary copy. Note: To promote a secondary copy to be the primary copy, both copies must be synchronized— that is, the secondary copy must contain all unpruned data residing on the primary copy. If they are not synchronized, the promotion fails and Galaxy displays an explanatory message. To maintain synchronization between the primary copy and the secondary copies, it is strongly recommended that you perform an Auxiliary Copy operation after a backup job has completed.

Keep in mind that the data-retention period (and all defined attributes for that particular secondary copy) is retained when promoted. It is recommend that secondary copies have a retention period that is greater than or equal to that of the primary copy. Consequently, you may need to adjust the retention periods of your new primary and secondary copies after the promotion. In the case of an inoperative primary copy, you can use secondary copies for restore operations or auxiliary copy operations.

192 Backup and Restore for Internet Data Center Using Secondary Copies for Restore Operations

If your primary and secondary copies are not synchronized, you cannot promote the secondary copy to be the primary copy. You can, however, specify a secondary copy from which you want the data restored, by using the copy precedence feature. Using Secondary Copies for Auxiliary Copy Operations

Secondary copies are components of storage policies that are used in Auxiliary Copy operations. This allows remote or multiple copies to be made of backup media for archival or disaster-recovery purposes. To keep it simple, consider an Auxiliary Copy to be an exact copy of the data stored on a storage policy. Any number of Auxiliary Copies can be created and in turn promoted to be the primary copy as required if they are in sync (current). Auxiliary Copies are updated in sequence and can be scheduled. Copy precedence determines which Auxiliary Copy is updated first. Auxiliary Copy allows you to create multiple redundant copies of backup data without making an impact on the client. During Galaxy restore operations, Galaxy initially searches the primary copy for the requested data. If the data is unavailable through the primary copy (due to data pruning, for example), Galaxy attempts to retrieve the data from a secondary copy. Note: Although a secondary copy can use the same library as the primary copy, it is recommended that you configure a secondary copy to use a different library. This will lessen the consequences of a single library failure.

Auxiliary Copy Summary ●

●

●

●

●

●

●

Secondary copies are components of storage policies that are used in Auxiliary Copy operations. Selecting the Active check box in the Copy Name Properties dialog box enables storage policies. In the Copy Name Properties dialog box, select the Hardware Compression check box to enable hardware compression for all data backed up through the storage policy copy. Software compression, which can be enabled on either the client or MediaAgent computer, is only available when hardware compression is not enabled. Any secondary copy of a storage policy can be promoted to become the primary copy by selecting the Primary Copy check box in the Copy Name Properties dialog box. Secondary copies can only be promoted if they are synchronized with the primary copy (that is, they contain the same backup data). During an Auxiliary Copy operation, secondary copies are synchronized with the primary copy in their assigned order of precedence.

Chapter 4: Advanced Backup and Restore Operations 193 ●

● ●

●

Auxiliary Copy operations can be executed on-demand or can be scheduled to occur on a regular basis. Galaxy will not allow you to delete primary storage policy copies. After any secondary storage policy copy is deleted, the data contained in the copy will no longer be available for restore. All media assigned to a deleted storage policy copy immediately becomes available for archive pruning.

Copy Precedence

When a copy is configured, Galaxy automatically assigns it a copy precedence number, which you can change at any time. When requesting a restore operation, you can specify a copy precedence number from which you want the data restored. This can be useful in several scenarios, including the following: ● The primary copy is no longer available for restore operations due to a hardware failure. ● The secondary copy restores from a magnetic disk, which is more efficient than the tape library from which the primary copy restores. If you attempt to restore from a specific copy and the data is unavailable through the given copy, Galaxy does not search the remaining copies, and the restore operation fails. For example, assume a storage policy includes three copies. Two of the copies direct data to Library A, and the third directs data to Library B. Restoring from copy precedence 3 forces Galaxy to restore the data from Copy 3 without initially searching the primary copy. If File A is unavailable through Copy 3 (due to data pruning, for example) the restore operation fails. When you restore from copy precedence, keep in mind that the restore data may have been secured through more than one storage policy, each one associated with more than one copy. If you specify a copy precedence for a restore operation, the data is restored from the specified copy precedence for all of the associated storage policies. If the data is unavailable through the specified copy for any of the storage policies, the restore operation will not complete successfully.

Auxiliary Copy Examples To gain a better understanding of the nature of auxiliary copies, the following section looks closer at how auxiliary copies behave under several conditions. For practical reasons, this section focuses on simpler scenarios first and then builds on that knowledge to understand the more complex scenarios.

194 Backup and Restore for Internet Data Center Single-Stream/Single Subclient Auxiliary Copy

The example in Figure 4.10 explains how auxiliary copies are performed when the storage policy serves only one subclient, and that subclient uses only a single data stream. In this example, a File System subclient backs up its data to a dedicated storage policy. Under such conditions, the primary copy writes the data to a single media group. Additional assumptions: ● The subclient backs up three times a week, with one full backup performed each week. (The full backups are marked F1 and F2.) ● The subclient is new (therefore, it has no backup history). ● The storage policy associated with this subclient has just one secondary copy: Copy 2 and it is active. ● The retention periods relevant to this storage policy are: ● Two weeks and three full backup cycles for the primary copies ● Infinite for the secondary copy

Week Copy 1

Stream 1

F1

F2

1

2

F1

I11 I12 F2

A1

I21 I22

Primary Backup Media

Archive files

A1 Copy 2

Stream 1

F1

I11 I12 F2

I21 I22

Auxiliary Copy Media

Archive files

Figure 4.10 Single-stream/single subclient auxiliary copy - starting point

For example, backups have occurred regularly over a two-week period. Prior to the scheduled time of the third full backup, we initiate an auxiliary copy (A1). This auxiliary copy copies all data from the primary backup media to secondary copy 2. Figure 4.11 shows what happens to the data as time progresses. Two more weeks pass, during which two more sets of backups and auxiliary copies have occurred. At the end of the third week, a second auxiliary copy (A2) is initiated.

Chapter 4: Advanced Backup and Restore Operations 195 F1

Week Copy 1

1

Stream 1

F1

F3 A1

F2

3

2 I11 I12 F2

F4 A2

I21 I22 F3

A3

4 I31 I32 F4

I41 I42

Primary Backup Media

Archive files

A1 Copy 2

Stream 1

F1

A2

I11 I12 F2

I21 I22 F3

I31 I32

I11 I12 F2

I21 I22 F3

I31 I32 F4

A3

Archive files Copy 2

Stream 1

F1

I41 I42

Auxiliary Copy Media (Week 3) Auxiliary Copy Media (Week 4)

Archive files

Figure 4.11 Single-stream/single subclient auxiliary copy - after three weeks

This time, the operation copies only the backups done since the previous auxiliary copy (the full backup F3 and the two subsequent incremental copies). At the end of the fourth week, a third auxiliary copy (A3) is initiated. As before, the operation copies only the backups done since the previous auxiliary copy. On the primary backup media, the first set of backups has expired and has been pruned. This data, however, remains available on the auxiliary copy media, subject to the terms of the retention period. The next set of examples examines some of the ramifications of expiring data with regard to auxiliary copies. Multi-Stream/Single Subclient Auxiliary Copy

Figure 4.12 shows how auxiliary copies are performed when the storage policy serves one subclient that uses two data streams. The ability of a subclient to support multiple streams depends on the iDataAgent to which the subclient belongs. Many iDataAgents, particularly those that secure File System data, do not support multiple stream backups. For details on any particular iDataAgent, see the applicable Galaxy Client Administration Guide. In this example, a subclient backs up its data to a dedicated storage policy. Some additional assumptions are as follows: ● The subclient backs up three times a week, with one full backup performed each week. (The full backups are marked F1 and F2.) ● The subclient is new (no backup history). ● The subclient is configured to perform backups, using two data streams. ● The storage policy associated with this subclient has only one secondary copy: copy 2.

196 Backup and Restore for Internet Data Center ●

The retention periods relevant to this storage policy are as follows: ● Two weeks and three full backups for the primary copies. ● Infinite for the secondary copy. F1

F2 A1

Week Stream 1

1 F1a

2 I11a I12a F2a

I21a I22a Primary Backup Media

Copy 1

Stream 2

F1b

I11b I12b F2b

I21b I22b

Archive files

Stream 1

A1

F1a

I11a I12a F2a

I21a I22a

F1b

I11b I12b F2b

I21b I22b

Secondary Copy Media Copy 2

Stream 2

Archive files

Figure 4.12 Multi-stream/single subclient auxiliary copy

For example, backups occurred regularly over a two-week period. Prior to the scheduled third full backup, we initiate an auxiliary copy (A1). This auxiliary copy copies the data of both data streams from the primary backup media to secondary copy 2.

Starting an Auxiliary Copy To avoid possible media contention, which can affect performance, it is recommended that you do not start an auxiliary copy operation if the selected storage policy is already participating in a backup or restore operation. In such a case, the auxiliary copy would fail to copy any files from primary storage to secondary storage. To identify the participating storage policy for any job, use the Detail option from the Job Controller window. Note: You cannot conduct an auxiliary copy from a library attached to a MediaAgent for Windows to a library attached to a UNIX MediaAgent. Similarly, you cannot conduct an auxiliary copy from a library attached to a UNIX MediaAgent to a library attached to a MediaAgent for Windows.

To perform the following procedure you must have Administrative Management capability on the Galaxy system.

Chapter 4: Advanced Backup and Restore Operations 197




To start an auxiliary copy immediately 1. In the CommCell Browser, right-click the storage policy for which you want to start an auxiliary copy and then click Auxiliary Copy. 2. In the Auxiliary Copy window, if you want to copy the data to a different backup tape, select Start New Media; otherwise, leave this option blank. Then click OK. 3. When the auxiliary copy is completed, a message window appears, indicating that the job is complete. Click OK. Auxiliary copies can also be scheduled. To perform the following procedure, you must have Administrative Management capability on the Galaxy system.




To schedule one or more auxiliary copies 1. In the CommCell Browser, right-click the storage policy for which you want to schedule an auxiliary copy and then click Auxiliary Copy. 2. In the Auxiliary Copy window, if you want to copy the data to a different backup tape, select Start New Media; otherwise, leave this option blank. Then click Schedule. 3. When the Schedule Details dialog box appears, select the scheduling options you want, and then click OK when finished. The auxiliary copy is scheduled. 4. When the auxiliary copy runs, a message window will appear when the job is complete. Click OK.

Creating a Secondary Copy Secondary copies allow you to establish unique configurations for multiple copies of backup data. This configuration may include unique retention parameters or media assignment for a specific copy of backup data. Galaxy refers to all storage policy copies that are created beyond the primary copy as secondary copies, regardless of the number of copies created. Note: It is recommended that the retention parameters of all secondary copies be greater than or equal to the retention parameters of the primary copy.


To create a secondary copy 1. In the CommCell Browser, double-click the CommCell root until the storage policy is shown. Right-click the storage policy and select New Copy Name. 2. In the Copy Name Properties dialog box, enter the following information: ● In the Name field, enter a name for your secondary copy. ● In the Library field, select the library that you would like the storage policy copy assigned to. If you chose magnetic storage for the primary copy, select a tape storage device for this secondary copy. If the selected library is a tape library, select the library drive pool and scratch pool.

198 Backup and Restore for Internet Data Center ●

●

●

●

When the Primary Copy Name check box is selected, the storage policy copy is identified as the primary copy. When any subclient backups are performed that are assigned to the storage policy, the backup data is written to the primary copy. When the Primary Copy Name check box is cleared, the copy is identified as a secondary copy. Data is written to secondary copies during the Auxiliary Copy operation. When the Hardware Compression check box is selected, hardware data compression is enabled for all data that is backed up through the storagepolicy copy. When the Hardware Compression check box is cleared, hardware compression is not enabled, allowing you to select either MediaAgent or client-level software compression for the storage-policy copy. Software compression is configured at the iDataAgent level. Additional information on software compression can be found in any iDataAgent training module. When the Active check box is selected, the storage policy copy is enabled, allowing the storage policy copy to transfer data to and from its assigned media. When the Active check box is cleared, the storage policy copy is disabled, not allowing the storage policy copy to transfer data to and from its assigned media. Ensure that the Active box is selected, set the retention parameters to 180 days and 6 cycles, and click OK to complete the creation of your secondary copy.

Promoting a Storage Policy Copy Galaxy enables you to promote a secondary copy of a storage policy to be the primary copy. This feature can be useful if a hardware failure has occurred in the primary copy path (for example, MediaAgent, library, and so on) and you need to continue operations with the storage policy while you make repairs. After you have promoted the copy, all backup operations for the storage policy are conducted through the new primary copy. Galaxy automatically redesignates the former primary copy as a secondary copy. Any current secondary copy of a storage policy can be promoted to become the primary copy. When a secondary copy is promoted to the primary copy, the previous primary copy is automatically demoted to secondary copy status. When a secondary copy is promoted, its configuration settings do not change. This includes the copy’s retention parameters. Before promoting a secondary copy, note the following: ● In order to promote a secondary copy to be the primary copy, both copies must be synchronized (that is, they must contain the same data). If they are not synchronized, the promotion fails and Galaxy displays an explanatory message. If you need to synchronize the copies, you should perform an auxiliary copy operation as described in the Galaxy CommServe Administration Guide.

Chapter 4: Advanced Backup and Restore Operations 199 ●

●




It is recommended that you not change copy configuration while the parent storage policy is conducting a backup, restore, or auxiliary copy operation. It is also recommended that secondary copies have a retention period that is greater than or equal to that of the primary copy. Consequently, you may need to adjust the retention periods of your new primary and secondary copies after the promotion.

To promote a secondary copy to be the primary copy 1. In the CommCell Browser, right-click the copy that you want to promote and then click Properties. 2. In the Copy Name Properties dialog box, on the General tab, select the Primary Copy Name checkbox. 3. Galaxy prompts you to confirm your selection. Click OK to proceed. 4. Galaxy promotes the selected copy to be the primary for the storage policy. You can confirm the copy promotion by examining the Primary Copy check box settings for the copies listed in the right pane of the CommCell Browser.

Setting the Copy Precedence of Storage Policy Copies When an auxiliary copy operation is initiated, the backups contained in the primary copy that have not been copied since the last auxiliary copy operation are copied to the storage policy’s secondary copies in order of precedence. Setting precedence allows you to establish the order in which secondary copies are synchronized with the primary copy.


To establish the copy precedence 1. In the CommCell Browser, double-click the CommCell root until the storage policy you want is shown. Right-click the storage policy and then click Properties. 2. In the Storage Policy Properties dialog box, click the Precedence tab. 3. Click the copy whose precedence you want to change and then click either the Up or Down button to increase or decrease the copy precedence. After you have set the new copy-precedence order, click OK to register the changes.

Deleting a Secondary Storage Policy Copy Galaxy does not allow you to delete primary storage policy copies. The only way to delete a primary copy is to delete the storage policy itself. After a storage policy copy has been deleted, the data contained in the copy will no longer be available to be restored. All media assigned to a deleted storage policy copy immediately becomes available for archive pruning.

200 Backup and Restore for Internet Data Center

Note: Deleting a secondary copy also deletes any unpruned data on that copy.


To delete a secondary copy 1. In the CommCell Browser, right-click the secondary copy that you want to delete and then click Delete. 2. Galaxy prompts you to confirm the deletion. Click OK to proceed. Galaxy deletes the selected copy and removes it from the CommCell Browser.

Archive Pruning Overview and Procedures Data secured by Galaxy (that is, backups, auxiliary copies, and Synthetic Full backups) remains available for restoration for a period of time known as the retention period. You can set the length of the retention period by modifying certain parameters, generally a number of days and the number of full backup cycles that must be available. The Archive Pruning operation, which you either schedule or initiate manually, deletes data that has exceeded its retention period. Data that has not been deleted is fully accessible to the system and can be restored. If you never prune your data, it all remains available, regardless of retention settings. Archive Pruning operations cannot run concurrently with restore, auxiliary copy, or Synthetic Full operations. If archive pruning is in progress and you attempt to start an incompatible operation, or vice versa, a message appears in the Event Viewer informing you that the second operation could not start because the first was running. If data stored on tape exceeds its retention period and the archive pruning utility is run, the data is logically deleted; meaning, it is removed from the Galaxy database. If all of the data on a medium is pruned, the medium is recycled; that is, it is returned to the scratch pool that is currently associated with the storage policy copy that writes to the medium. The following procedures are described in this section: ● Viewing backups that are candidates for pruning and media that are candidates for recycling ● Scheduling a pruning job ● Starting a pruning job


To view backups that are candidates for pruning and media that are candidates for recycling 1. In the CommCell Browser, right-click the CommServe, and then click Archive Pruning.

Chapter 4: Advanced Backup and Restore Operations 201

2. In the Archive Pruning Option dialog box, select the Forecast dialog box. 3. In the Archive Pruning dialog box, the Prunable Backups tab displays a list of

those backups that have exceeded their retention periods. For each backup, the following are displayed: the computer from which the backup originated, iDataAgent, software instance (where applicable), backup set, subclient, and backup time. 4. In the Archive Pruning dialog box, the Media Recycled tab displays a list of media that will be recycled the next time backup data is pruned. The following information is displayed: the storage policy and copy through which the data was backed up and to which the media are assigned, the scratch pool to which the media will be reassigned, and the number of media on this storage policy and copy that are to be recycled. 5. To initiate an immediate pruning operation, click Prune Now. 6. A message that the archive pruning is complete is displayed, click OK. Note: After data is pruned, it cannot be restored.


To schedule a pruning job 1. In the CommCell Browser, right-click the CommServe, and then click Archive Pruning. In the Archive Pruning Option dialog box, select the Schedule option, and then click OK. In the Schedule Details window, the Schedule Details tab appears. 2. Set the schedule details. 3. If you want to view the job summary for the pruning job that you have scheduled, on the Schedule Details window click the Job Summary tab. Otherwise, click OK. Note: After data is pruned, it cannot be restored.




To starting a pruning job 1. In the CommCell Browser, right-click the CommServe, and then click Archive Pruning. 2. In the Archive Pruning Option dialog box, select the Prune Now option, and then click OK. 3. If you are sure that you want to prune, in the Warning prompt that appears click Yes. (If you want to see which backups will be deleted, click No, and then select Forecast and continue).

202 Backup and Restore for Internet Data Center

Rules for Archive Pruning Each iDataAgent within Galaxy follows a set of Archive Pruning rules. Moreover, some iDataAgents share the same set of rules; in other words, one set of Archive Pruning rules may apply to several iDataAgents. The following iDataAgents share the same set of Archive Pruning rules: ● File System ● The Windows NT® operating system ● Windows 2000 ● Exchange 5.5 ● Exchange 2000 ● Netware The following iDataAgents have their own unique set of Archive Pruning rules: Microsoft SQL Server 7.0 ● Microsoft SQL Server 2000 ● Celera (NAS) ● Oracle ● Network Appliance (NAS) ●

For details on specific Archive Pruning rules, see the appropriate Galaxy Client Administration Guide.

Galaxy Reports The Galaxy system allows you to generate a variety of reports, each tailored to a particular aspect of data management, such as scheduling, event management, media management, and archive pruning. For a list of the Galaxy reports, see the Galaxy CommCell Administration Guide. Note: The appearance of some Galaxy reports may be affected by the browser package or version. Also, some Galaxy reports may be truncated when they are printed.

Report Filters On the CommCell Console, on the standard toolbar, click the Reports icon to display the Report Filter window. Galaxy reports can be customized by filtering various sort criteria, depending on the report type selected. For example, some reports can include all job IDs (by default) or be customized to report information on only one job ID.

Chapter 4: Advanced Backup and Restore Operations 203

Select the report that you want to generate from the Report Filter. Specify its filter criteria, and then generate the report. The Report Filter window varies, depending on the report type selected.

Web Browser Requirement Reports are displayed in the default Web browser. If you are running the CommCell Console from a Web browser, the report will be displayed using the same browser. Note: To view reports remotely, either through a Web browser or from a remotely based CommCell Console, you must install and configure Microsoft Internet Information Services (IIS) on the CommServe computer. For all CommServe installation details, see the Galaxy Quick Start Guide.

Report File Pruning Each generated report creates an HTML file that is saved for at least two days after the report is generated. After the two-day period has lapsed, the HTML files are deleted automatically whenever another report (of any type) is generated.

Report Types Galaxy provides the following range of report types: ● Archive Pruning Report. Reports on aged backups (that can be pruned) and media that can be recycled. ● Auxiliary Copy Report. Lists the status of all archive files copied in the last auxiliary copy operation, indicating whether they were successfully copied. ● Backup History Report. Provides a history of backup operations for the CommCell. ● Backups On Media Report. Provides information on backups and their associated media and libraries. ● Event Report. Lists Galaxy system events. ● Job Schedule Report. Lists jobs scheduled to begin within a specified time frame. ● Library and Drive Report. Provides information on media drives and storage libraries. ● Media in Library Report. Provides details on individual media contained in an entire library. ● Media in Storage Policy Copies Report. Provides details on individual media associated with selected storage policies and copies. ● Media Management Housekeeping Report. Provides information on tapes and drives in need of maintenance.

204 Backup and Restore for Internet Data Center ●

●

● ●

NAS NDMP Backup Archives Report. Provides information on backup archives and their associated storage policies. Restore History Report. Provides a history of restore operations for the CommCell. Scratch Pool Report. Indicates the status of the CommCell’s scratch pools. Storage Policy Report. Lists properties and media associated with the CommCell storage policies.

Creating Galaxy Reports See the appropriate procedure in the Galaxy CommCell Administration Guide to generate the report you want to create.

Recovering a CommServe For detailed information on disaster-recovery operations on a CommServe, follow the procedures outlined in “CommServe Recovery Procedures,” found in Appendix A of the Galaxy CommServe Administration Guide. See the topic applicable to your configuration, in this case “Recovering a CommServe/MediaAgent.” This topic outlines the process, and provides information on the Disaster Recovery tool used as part of the recovery operation. You must ensure that all storage devices (tape devices) are configured before performing the CommserveER restore. Note: Galaxy 3.1 GSP1 requires an additional step after performing CommserveER. Before running the Galaxy Drive and Library Configuration, as instructed in the Administration Guide, change the properties on the task bar from ‘backup01’ to BACKUP01.


To recover a CommServe 1. Click Start, point to Programs, click Galaxy, right-click Drive and Library Configuration, and then click Properties. 2. Change the hostname in the startup command from ‘backup01’ to BACKUP01, and then click Apply. 3. To confirm that this fix has been successfully installed, click Start, point to Programs, click Galaxy, click Drive and Library Configuration and then make sure that all of the text in the window in bold rather than being shaded. The method used to recover the CommServe will depend on the status of the CommServeER backup data: ● If the magnetic copy of the CommServeER backup data is lost, or has been damaged, you must retrieve the data from the tape prior to running CommServeER. Locate the CommServeER subclient tape, as described in the Deployment Guide, and restore the data by following the procedures outlined in

Chapter 4: Advanced Backup and Restore Operations 205

●

“DRRestoreGUI”. You must first install the CommServe (and MediaAgent) as outlined in CommServe Recovery Procedures found in Appendix A of the Galaxy CommServe Administration Guide. Then run the DRRestoreGUI to retrieve the CommServeER data, and continue with CommServe Recovery Procedures. If the magnetic copy of CommServER backup data is available, skip DRRestoreGUI procedures and follow the procedures outlined in the Galaxy CommServe Administration Guide.

Note: Each original storage device must be properly installed and configured before carrying out the CommserveER restore.

DRRestoreGUI The Disaster Recovery tool (DRRestoreGUI.exe) allows you to retrieve previously backed up Galaxy data in the case of a disaster. It can retrieve File System and ExpressRecovery backup data from tape, optical, or magnetic media. The DRRestoreGUI allows you to restore data from media to a user-defined destination.


To restore media using the DRRestoreGUI 1. Make sure that there are no tapes loaded on any of the tape drives. 2. In the Galaxy\Base\SystemTools directory on the newly installed CommServe, double click DRRestoreGUI.exe. The Galaxy Disaster Recovery window is displayed. 3. Using a non-RSM tape or optical library, click Tape Detect. When detection is complete, the Tape Mount Path will list the available drives. 4. Click Library Detect. An inventory of the library will begin. When detection is complete, the tape and barcode should appear in the windows. 5. Select the barcode that contains the CommServeER data. (It is recommended that you note the barcode of the ‘CSER’ tape during deployment of the CommServe.) 6. Click Catalog Tape. The catalog operation reads the archive file information from the media. A dialog box appears with the message, “Operation Finished. Check DRRecovery.log for details,” and then click OK. 7. An archive file was created during the previous step. This file is saved in the directory Galaxy\Base\SystemTools. The Archive file number is represented by x in this file name, Archive File ID x Catalog.txt; for example if the file name is Archive File ID 1 Catalog.txt, the Archive File ID is ‘1’. Note the Archive File ID from the file name. 8. Close the DRRestoreGUI. This will dismount the tape. 9. Open the DRRestoreGUI. Click Tape Detect. Click Library Detect. Select the barcode. Do not select Catalog Tape.

206 Backup and Restore for Internet Data Center 10. Select the Archive File To Restore check box and type the ID of the archive file.

The ID can be found in the name of the archive file created in Step 5. 11. If the directory path in the archive file is C:\CSER, this data will be restored to C:\CSER on this CommServe. Select Optional Restore Path and enter a new directory location if desired. 12. Click Start Restore. This will mount the tape and restore the files to the location listed in the archive file. A dialog appears with the message, “Operation Finished. Check DRRecovery.log for details,” click OK. 13. Check the location where the restored files were stored and verify your data. You are now ready to complete the CommServe Recovery Procedures, as found in Appendix A of the Galaxy CommServe Administration Guide.

MediaAgent Many aspects of the MediaAgent either require configuration or can be configured according to your specific backup and restore solution.

Managing Media The best way to manage Media is by creating a closed media management cycle. Regular Archive Pruning is essential to a closed media management cycle. Media rotation is essential for good media management because: ● It allows demarcation points between media sets, which facilitates media re-use. ● It minimizes the impact on data recovery caused by the failure of one or more media (tapes, for example). ● It optimizes costs and administrative overheads, while still providing data protection.

Understanding the Closed Media Management Cycle A media management cycle describes the various states of a medium as it is used. There are four basic states: ● Spare. Available for storing data; member of a scratch pool. ● Active. The media is available for writing. In other words, when data is sent to the storage policy copy associated with the media group containing this media, the data is written to this media. ● Used. Holds needed data, but is no longer being written to. ● Expired. No longer holds needed data, and is eligible for re-use. A closed media management cycle provides for the automatic re-use of media by ensuring media moves automatically through all states. Without a closed media

Chapter 4: Advanced Backup and Restore Operations 207

management cycle, the administrator must constantly provide an external source for spare media and intervene manually to move the medium between various states. Often administrators will plan backups and retention without regard to the number or source of media required to support the stored data. This usually manifests itself in unplanned budget expenditures, extra media administration, or failed data protection.

How Archive Pruning Fits In The primary purpose of Archive Pruning is to re-use the medium. It is the key function that enables an administrator to create a closed media management cycle. Without it you would never recycle media. With a tape medium, Archive Pruning removes the metadata information pointing to the backed up data. When all pointers to a specific tape have been pruned, the tape is moved to the appropriate scratch pool and marked for re-use. No backup data on the tape needs to be erased because it is automatically written over when the tape is re-used. However, after Archive Pruning, the existing data on it still cannot be retrieved by Galaxy without the metadata pointers. Magnetic disk libraries work differently in that, in addition to the metadata pointers being removed, the backup data is actually erased when you perform Archive Pruning. This is because magnetic disk does not support writing over existing data without erasing it first. This process provides for the automatic recovery of disk space for re-use by Galaxy. The pointers to backup data that are eligible for pruning are those that exceed retention criteria. Which metadata pointers are pruned depends on the retention parameters of the associated storage policy’s copy name. It is important to note that Galaxy can still retrieve it until you prune the pointers to the backup data. Also note that pruning is done for the entire CommCell and cannot be selectively applied to a specific storage policy. There are several additional things that should be observed when determining pruning eligibility. First, if you have more than one active copy name in a storage policy, Galaxy rightly assumes you intend to do an Auxiliary Copy within that Storage Policy. Until you perform that auxiliary copy, no data for that storage policy can be pruned. Optionally, you could inactivate the other copy names and then prune. When you do that, however, you lose the synchronization of backup data between copy names and may jeopardize your ability to correctly restore data from those copies. Second, Galaxy has certain requirements that ensure the continuity of data recoverability for a cycle set. A cycle set is defined as a full (or Synthetic Full) backup and all of its associated incremental or differential backups. Galaxy will not orphan data

208 Backup and Restore for Internet Data Center

within a cycle set. This means that incremental or differential backups must have an associated full backup. Galaxy requires that all backup data within each cycle exceed retention parameters before any data within that cycle can be pruned. Third, Archive Pruning should not be scheduled while backups are in progress. Archive Pruning will consider the backup in progress in its determination of eligibility without knowing whether that backup will eventually succeed or fail. This can yield undesirable results. How often should you perform Archive Pruning? That depends on your remaining backup storage capacity, retention parameters, and backup schedule. Administrators should schedule Archive Pruning at least on a weekly basis because the more common cycle sets last one week.. Archive Pruning will not prune data sets if there are none eligible to prune, so it does no harm to run Archive Pruning more often, even daily. While this may be more pro-active in freeing up spare media, it does not give the administrator any room for error should a reason occur to delay Archive Pruning.

Media Rotation Media rotation is a planned methodology of using separate media (or medium sets) and backup types over a period of time to store data. Media rotation is used to minimize the impact to data recoverability from the loss of one or more backup storage mediums. Risks to storage media are many. A removable tape or magnetic-optical medium can become lost, damaged, worn, or deteriorated to the point of being unrecoverable. Magnetic media can experience various hardware failures, which can be compensated for by use of redundant array of independent disks (RAID) configurations. Using a single medium for storing data increases the risk of these failures happening to your backup data by introducing the medium as a single point of failure. With Media rotation, each medium or medium set is self-recoverable; it does not require any of the other media used in order to restore data. This is accomplished by making each backup set independent of the other. These sets are then used alternately over a period of time. Multiple backup sets with varying usage times and rates can be combined to provide the degree of protection desired. Although rotating media reduces risk, it results in added costs for media and administrative overhead. As a result, various methods of media rotation have been developed that optimize the ratio of overhead to risk reduction. There are different rotation schemes to suit different systems, different environments, and different organizational needs.

Chapter 4: Advanced Backup and Restore Operations 209

Media Rotation Systems

At a minimum, you should have two media sets that you rotate on alternate backups. This protects you against relying on a single backup media set, and eliminates the chance that a hard disk crash during backup would leave you with nothing at all. It is not the ideal level of protection, because there is no provision for off-site media storage. If you use two media sets, you need to decide how often to do the backup. The longer you go between backups, the longer the changes that you made since the last backup are at risk. For many users who use their systems little enough that this minimum scheme makes sense, doing backups weekly is more than sufficient. For others, daily backups make more sense, which means that a more comprehensive rotation scheme is required. Good media rotation schemes provide multiple media sets and a depth of file versions that a file to be restored to a particular point in time, such as prior to a virus attack. Grandfather-father-son (GFS) and Tower of Hanoi are two well-established rotation schedules that provide a long and varied history of file versions and comprehensive recovery capabilities. Implementing Media Rotation Schemes

Galaxy’s support of media rotation schemes depends on iDataAgents. Table 4.18 lists the media rotation support for each iDataAgent. Table 4.18 Supported media rotation systems iDataAgent

Media rotation support

Comments

File System (Windows NT and Windows 2000, Netware, and UNIX)

Multiple backup sets and Synthetic Full backups

Each set has identical subclients and different storage policies

Transaction log-based (Microsoft Exchange, Microsoft SQL Server, IBM Lotus Notes, Oracle Server)

Auxiliary copy

Continuity of transaction logs is critical

NAS (NetApps and EMC Celera)

None

Auxiliary copy, or multiple backup sets, are not supported

Multiple Backup Sets

Galaxy’s file system iDataAgents support the use of multiple backup sets, which allows you to configure duplicate subclients assigned to different storage policies and, therefore, different media sets. You should create a backup set for each set in a media rotation schedule and schedule the associated subclients in accordance with the media-rotation timetable. Restoring requires you to select which backup set or media you want to use.

210 Backup and Restore for Internet Data Center Synthetic Full Backups

Synthetic Full backups enable you to do a full backup to new media without involving the client. This restore-to-backup function consolidates your previous backups onto a new tape. Be aware that a Synthetic Full backup does not collect any data from the client and, therefore, is not a substitute for your regularly scheduled backup. If you schedule a Synthetic Full backup followed immediately by a normal full backup to new media, you can isolate a full backup on a single set of tapes for export and offsite storage. Restoring requires you to specify a point in time between the last backup before the Synthetic Full backup and the time of the Synthetic Full backup. Auxiliary Copy

Auxiliary copy synchronizes backup data between multiple copy names and media. With applications that depend on transaction logs for recovery, making an auxiliary copy is the only way to support the use of multiple media sets to minimize risk of data loss from a single media failure. Inactivating and taking a copy name offsite is an option for disaster recovery. Migrate Media Between Storage Policy Copies

Media migration provides you with a great deal flexibility in media management. For example, if a library is destroyed, you can simply change the metadata pointers at the CommServe to point a storage policy’s media to a different library. The following restrictions apply to media migration: ● Media must be compatible between libraries. ● Media cannot be migrated from a MediaAgent for Windows to a UNIX MediaAgent, nor vice-versa. ● You can migrate from a library to a stand-alone drive, but cannot migrate media from a stand-alone drive to a library.


To migrate media 1. Manually remove the media from the source library and insert it into the destination library. 2. In the CommCell Browser, right-click the storage policy copy whose media you want to migrate, and select Migrate Media. 3. Galaxy lists the media owned by the storage-policy copy and again prompts you to remove the media from its original library. Click OK to continue. 4. Select the destination MediaAgent, Library, Master Drive Pool, Drive Pool, and Scratch Pool. Click OK when finished. 5. A dialog box prompts you to indicate whether the destination library and drives are compatible. Click OK.

Chapter 4: Advanced Backup and Restore Operations 211

6. When you receive the message that the media has been successfully migrated,

click Close to complete the operation. Media Expiration

It is necessary to replace media before they begin to degrade. Galaxy helps you do this by keeping track of various types of media events (for example, software error, mount operation). For each medium, the system tracks the number of times each event occurs. When the number of events exceeds a preset threshold, the system lists the medium in the Media Management Housekeeping report, notifying you that it is time to replace the medium. You can set event thresholds for each media type. In other words, you can decide how many events of each event type can occur before a medium of a particular media type exceeds its capacity for reliable operation. When an event exceeds its threshold value, Galaxy sends a message to the event log and generates the Threshold Exceeded alert, if configured. Note: See the manufacturer’s documentation for the recommended maintenance criteria for each media type.

Galaxy allows you to set various media expiration thresholds. As shown in Table 4.19. Table 4.19: Media expiration thresholds Threshold

Description

Number of mounts

The number of times the medium can be mounted in a drive before it must be replaced.

Number of soft errors (since cleanup)

The number of software errors that can be encountered while writing to or reading from the medium before the medium must be replaced.

Number of years

The length of time the medium can remain in use.

Number of writes

The number of times data can be written on the medium before it is marked as expired.

Number of reads

The number of times data can be read from the medium before it is marked as expired.

Number of reuses

The number of times the medium can be recycled before it is marked as expired.

Number of hard errors

The number of hardware errors that can be encountered while writing to or reading from the medium before it is marked as expired.

For information on the procedure for modifying media maintenance thresholds see online Help, under the topic “Media Expiration Parameters.”

212 Backup and Restore for Internet Data Center

Managing the Index Cache Each MediaAgent maintains an index cache, which is a designated portion of the Media Agents’ hard drive in which Galaxy index data resides. Index data is a valuable resource because it provides Galaxy with an efficient mechanism for locating user files for browse and restore operations. Although this index data is stored on the backup media for safekeeping, Galaxy writes an additional copy to the index cache of the MediaAgent that manages the backup. Data maintained in the index cache can be accessed more quickly than data stored on backup media if the corresponding user data is needed for browsing or restoration. Galaxy manages the cache on a least-recently-used (LRU) basis. As the capacity of the cache is reached, Galaxy overwrites those index data files that have been least recently accessed with the new index data. If a restore operation requires index data that is no longer in the cache (that is, a cache miss), Galaxy recovers the index data from the backup media. The index-cache directory is the directory in which index data resides. The amount of index data that can be cached is the amount of storage space available to the directory. This is determined by the size of the partition that contains the index-cache directory and by the amount of storage space occupied by other data (if any) within the same partition. (A partition is a logically designated portion of the hard disk.) To ensure that other files do not use up disk space that is needed for index data, you can create a new partition specifically for the index cache directory. The partition should be large enough to accommodate four percent of the amount of data managed by the MediaAgent. Specifically, this means four percent of the maximum amount of backed-up data that can be available for restoration by using this MediaAgent. Note: Do not specify or relocate a MediaAgent’s index cache to a directory residing on a compressed drive.

Calculating the Storage Space Required for the Index-Cache Directory To calculate the amount of disk space needed, you must consider: ● Which clients use the MediaAgent in question for backup and restore operations. ● The approximate amount of storage space required for a full backup of each client. ● The approximate amount of storage space required for incremental or differential backups of each client. ● The maximum number of full and partial backups that are retained for each client.

Chapter 4: Advanced Backup and Restore Operations 213

For example, assume that you have a MediaAgent that serves the backups of five file system clients. Each client has a 2-GB hard drive containing file system data. You run one full and two incremental backups for each client every week, and the retention period for these clients is 21 days and three full backup cycles. (For more information on retention periods, see the Overview chapters of the Galaxy Client Administration Guides for individual iDataAgents). You would calculate the storage space needed for the index cache as follows: ● The maximum storage space required for a full backup of all clients is 5 * 2 GB = 10 GB. ● If you estimate each incremental backup at 100 MB, the storage space required for an incremental backup of all clients is 5 * 100 MB = 500 MB, which is equivalent to 0.5 GB. ● Each backup cycle includes one full and two incremental backups. Consequently, a single full backup cycle for all the clients that are using the MediaAgent requires an estimated 11 GB of storage space (10 GB for the full backup, and 0.5 GB * 2 = 1 GB for the incremental backups). ● The retention period requires that three full backup cycles be available for restoration at all times, so the total storage space required for File System backups is 3 * 11 GB, or 33 GB. This is your estimate of the maximum amount of data that can be available for restoration by using the MediaAgent. ● Four percent of the total is 0.04 * 33 GB = 1.32 GB. Consequently, you should ensure that approximately 1.32 GB of storage space is available for the index cache directory. This example describes a very simple configuration, with just one iDataAgent and uniform requirements across client computers. In reality, client computers can have more than one iDataAgent, and the storage space required by each type of data must be added into the total. Different computers can have widely varying storage requirements. For example, an Exchange server might require much more storage space than a desktop computer. If different clients have different retention periods, this must also be considered in the calculation.

Library Sharing To help you get the most out of your tape and/or optical libraries, Galaxy allows you to allocate the medium changer and drives within a library to different MediaAgents within the CommCell. The system creates a Master Drive Pool for all of the drives within a given library that are controlled by a specific MediaAgent. (Although the library’s medium changer is attached to one MediaAgent, all MediaAgents that are attached to the library have access to the medium changer through centralized software). The following are some applications of library sharing:

214 Backup and Restore for Internet Data Center ●

●

●

Libraries can be shared directly using different SCSI cards, or using a SAN. Drives within a shared library can also be shared by using Dynamic Drive Sharing within the SAN. For more information on the interaction between Galaxy and SANs, see the Galaxy Pre-Installation Checklist. More MediaAgent processing power is available for a shared library. If you run multiple jobs simultaneously, you can improve job performance by distributing the load among MediaAgents. In certain cases, you may want to eliminate network traffic by sending large backups from a client computer directly to a library. For example, if you have a very large database on a client computer, you can install the MediaAgent software on the client, attach the client or MediaAgent to a library, and send backups directly without using the network. Library sharing allows you to use some drives within a library in this fashion while keeping other drives available for normal network operations.

The Master Drive Pool contains all the physical drives in the library, which can be shared among all the MediaAgents that are connected to this library. The logical group of drives within a single tape library that are actually controlled by a specific MediaAgent is referred to as a drive pool. Figure 4.13 shows a directly-attached shared library, shared by three MediaAgents. Note that any of these MediaAgents can also be attached to additional libraries.

medium Media Agent 1

Drive 1 Drive 2

Media Agent 2 SQL Server Client

Drive 3 Drive 4

Master Driver Pool Drive Pool 1

Master Driver Pool Drive Pool 2

Drive 5 Media Agent 3

Drive 6

Master Driver Pool Drive Pool 3

Drive 7

Figure 4.13 Directly-attached shared library

The functions of the MediaAgents shown in Figure 4.13 are: ● MediaAgent 1. Controls the library’s medium changer and Drive 1 and Drive 2, which are assigned to Master Drive Pool 1.

Chapter 4: Advanced Backup and Restore Operations 215 ●

●

MediaAgent 2. Controls Drive 3 and Drive 4, which are assigned to Master Drive Pool 2. This MediaAgent is also the host of a large SQL Server database, and a SQL Server Galaxy client. MediaAgent 3. Controls Drive 5, Drive 6, and Drive 7, which are assigned to Master Drive Pool 3.

Dynamic Drive Sharing Figure 4.14 shows a library shared by using a SAN with Dynamic Drive Sharing. Three MediaAgents share a tape library with four drives. Note that any of these MediaAgents can also be attached to additional libraries. medium Media Agent 1

Drive 1 Drive 2

Drive Pool 1

Drive 3 Drive 4 Drive 1 Media Agent 2 SQL Server Client

Drive 2 Drive Pool 2

Master Drive Pool

Drive 3 Drive 4

Drive 1 Drive 2 Drive Pool 3

Media Agent 3 Drive 3 Drive 4

Figure 4.14 Dynamic Drive Sharing

Note the following in Figure 4.14: ● All the MediaAgents share the same four drives (Dynamic Drive Sharing). ● MediaAgent 1 controls the library’s medium changer. ● Each MediaAgent has a drive pool that is grouped under one master drive pool for the library.

216 Backup and Restore for Internet Data Center

If you divide control of a library’s drives among multiple MediaAgents, you must take the following into account to avoid resource contention: ● When a library’s resources are divided among MediaAgents, and if resource availability is limited, resource contention is more likely than if the library were not shared. ● When you configure storage policies, the number of drives in the smallest drive pool associated with any copy of the storage policy determines the maximum number of streams that can be created simultaneously by any copy of the storage policy. For additional information on storage policies, copies, and resource contention, see the Galaxy Client Administration Guide of your iDataAgent.

RSM-Controlled Libraries Galaxy can use the Windows 2000 Removable Storage Manager (RSM) service to support operations in your library. RSM enables multiple applications to share a library. Before you configure Galaxy to use RSM, verify the following: 1. All Galaxy libraries in your MediaAgent computer use RSM. RSM libraries should not be mixed with non-RSM libraries. 2. Your libraries and drives are correct. To verify your libraries and drives: ● From Device Manager, make sure the attached medium changer, tape, or optical drives for the library are listed. ● If drives are not listed, detect the device and install the appropriate driver. For more information on this task, see the user manual provided by the manufacturer of your library and drive. 3. The RSM service is on. To do this: ●

●

In the Computer Management window click the Services icon and make certain that the Status field shows Removable Storage as Started. If it does not show as Started, right-click Removable Storage and click on Properties. Under Startup type select Automatic. Click Apply then right-click Removable Storage and then select Start.

4. The medium changers are not disabled and all target libraries are working

(media and drives are shown in the Removable Storage/Physical Locations folder when using the Removable Storage Microsoft Management Console (MMC) Snap-in. Note: For Windows 2000 RSM, auto configuration requires that all drives in the library have to be on one SCSI bus. Otherwise, manual configuration procedures are needed.

5. Unrecognizable and/or import media have been moved into the free media pool.

To do this using the Removable Storage MMC Snap-in, right-click the media available in the /Removable Storage/Media Pools/Import or /Unrecognized folder, then click Prepare.

Chapter 4: Advanced Backup and Restore Operations 217

6. Click Yes to confirm in the Media Preparation window and click Yes again to

confirm each individual media label. 7. After the selected media are in the free pool they have an Available status and are ready for allocation by Galaxy.


To configure a library that uses the RSM service for Galaxy Before you begin, ensure that the libraries used by Galaxy work under the RSM service. (If the libraries function under the RSM service, Galaxy automatically recognizes the RSM-enabled devices when you detect the RSM devices using the Galaxy Library and Drive Configuration window.) Also, verify that the required manual preparation for free media is done. Note: You can use libraries with or without barcode scanners.

1. Display the Galaxy Library and Drive Configuration window. 2. Detect the devices that are controlled by the MediaAgents that will access the

library. Galaxy detects the devices and displays them in the Galaxy Library and Drive Configuration window, with their detection status displayed as one of the following: not configured, RSM enabled, or RSM detect success. 3. If you want to modify the library properties, right-click the library and then select Properties. 4. In the Galaxy Library Properties dialog box, you can change the following properties: ● Alias. The user-defined name for the library. Galaxy displays this name in the CommCell Browser for the library. It is recommended that you give each library a descriptive name as its Alias, for easier system administration. ● Door Check Seconds. This interval, expressed in seconds, determines how frequently the system checks to see whether the library door is open. If the door is open during a check, the system conducts a full inventory of the library after the door is closed. This brings the inventory up to date way, if media were manually inserted or removed from the library while the door was open, the inventory is brought up to date. If you open and close the door in the interval between checks, the system does not detect the opening and closing, and does not update the library’s inventory. 5. When you are satisfied with your changes, click OK. 6. In the Galaxy Library and Drive Configuration dialog box, right-click the

library that you want to configure, and then click Configure. 7. A prompt appears, asking if you are sure that you want to configure the library. Click Yes to continue with the configuration. 8. A prompt appears, asking if you want to configure all of the drives within the library.

218 Backup and Restore for Internet Data Center ● ●

If you want to configure the drives individually, click No. If you want to configure all of the drives within the library (for example, if you are doing a typical library installation), click Yes.

The status of the library changes to RSM configured. If you chose to configure all associated drives, the status of the drives (and of the drive pool that contains them) also changes.


To protect the RSM database from corruption 1. On the MediaAgent computer containing the RSM database, create a new backup set exclusively for the RSM database. 2. If necessary, reset the default subclient content to avoid backing up the entire computer. This is because the default content entry of the default subclient is “\”, which means back up everything on the computer that is not defined or filtered by other subclients. To avoid backing up the entire computer, reset the default subclient content to be a small folder or a file on the computer. 3. Use a storage policy associated with a library that is not controlled by this RSM. 4. Schedule frequent backup schedules for the backup set that contains the RSM database; alternately, you can manually back up this backup set at frequent and regular intervals.




To restore the RSM database 1. On the MediaAgent computer that contains the RSM database, right-click the backup set and choose Restore System Databases. In the Restore System Databases Options window, select only the RSM database option and click OK. 2. After a successful restore operation, restart the RSM service or restart the computer, if necessary.

Recovering a MediaAgent For information on disaster-recovery operations on a MediaAgent, see the Galaxy CommServe Administration Guide.

Libraries and Drive Operations You can manage libraries, drive pools, and stand-alone drives within your backup and restore solution.

Master Drive Pool The Master Drive Pool contains the total number of drives in the library, which can be shared among all the MediaAgents that are connected to this library.

Chapter 4: Advanced Backup and Restore Operations 219

The following procedures on the Master Drive Pool are available in the Galaxy MediaAgent Administration Guide: ● Configuring a Master Drive Pool ● Validating the SCSI mapping of drives within a Master Drive Pool or Drive Pool ● Viewing Master Drive Pool Properties ● Deconfiguring a Master Drive Pool

Drive Pool A Drive Pool is a group of drives within a single tape library that are controlled by a specific MediaAgent. The following procedures on Drive Pools are available in the Galaxy MediaAgent Administration Guide: ● Configuring a Drive Pool ● Viewing Drive Pool properties ● Deconfiguring a Drive Pool

Library Inventory Galaxy maintains an inventory of all media associated with each library. It assesses the contents of the inventory using the inventory operation, which identifies the slot location and barcode or On Media Label (OML) of every medium detected within the library. A medium that is mounted in a drive is not included in the inventory. After the medium is removed from the drive and returned to a storage slot, Galaxy updates the inventory with the medium’s barcode (or user name), and location. Note: The inventory operation finds out which media are contained within a library. However, in order to use new media, Galaxy requires additional information, which is collected by the discovery operation.

The inventory operation, which may take a few minutes depending on the settings in the individual library, usually takes place when any of the following occurs: ● The door of the library is opened and then closed. ● The library’s power is turned on. ● A Reset Library operation is requested, although not all libraries invoke the full inventory command on a reset library command.

220 Backup and Restore for Internet Data Center

In addition, many library models conduct a full inventory operation when any of the following occurs: ● You install and configure the library for the first time. ● The CommServe’s Library and Media Manager service is restarted (this happens when you restart the CommServe). ● The library’s Library Management Service (LMS) is stopped and then restarted (this happens when you restart the MediaAgent). In addition, the inventory is updated when media are imported or exported through a library’s mail slot. Note: Inserting media in and closing the mail slots of some libraries may trigger a full inventory operation (rather than an inventory update).

When an inventory operation or update is performed for a library, Galaxy takes the library offline until the procedure completes successfully. This means that new backup or restore operations that access the library cannot start until the inventory completes. Because the inventory does not affect media that are already mounted in drives, a backup or restore that is in progress when the inventory begins can continue as long as it does not need to access unmounted media. For details on viewing the inventory of a library, see “Library Inventory” in online Help.

Importing Media Note: Ensure that the barcode used in the media is compatible with the library’s barcode reader (see the library manufacturer’s documentation for a list of compatible label formats). Importing media with an incompatible barcode may cause all operations in the library to fail.

Importing is the process by which you move media that are outside a library into storage slots within the library. There are two ways of importing media: ● You can import media through the library’s mail slot (if one is available). ● You can open the library door and insert media into storage slots by hand. Importing media through a mail slot offers the following advantages: The inventory update that is triggered by a mail slot import is much less time-consuming than the full inventory operation that is triggered when you open and then close the library door. In addition, if you import new media through a mail slot by using the Galaxy import operation, Galaxy automatically discovers the media. If you open the door and insert media, you must initiate a discovery operation. You must also initiate a discovery operation if you import through a mail slot, without using the Galaxy import operation. However, under certain circumstances you may

Chapter 4: Advanced Backup and Restore Operations 221

want to open the library door even though a mail slot is available. For example, if you want to add many media to a library at once, it may be faster to open the door than to use the mail slot. For libraries using the RSM services, media should be imported using the RSM MMC Snap-in window. Note: If you are not using a mail slot, be careful not to open the library door while media are mounted in drives within the library. In some library models (for example ATL 200 and ATL 500) opening the door causes the library to unmount all media, even those that are in active use. This can cause database inconsistency and failure of the running job(s).

For details on importing media into a tape or optical library, see “Library Operations” in online Help.

Discovering Media Before Galaxy can use a new, unrecognized medium, it must collect certain information about it through a process known as discovery. When a medium has been discovered and its information is entered into the Galaxy database, the medium is catalogued. Galaxy retains media information permanently; a medium does not have to be rediscovered if it is exported from the library and reimported. Note: Because Galaxy retains media information, a given barcode can only be used on a single medium within a CommCell. Do not reuse a barcode even if the medium to which it was attached is removed from the CommCell permanently.

If new media are imported through a library’s mail slot, the import operation automatically discovers them. If you import new media by opening the library door and inserting them, you must initiate a discover operation. Note: Although only uncataloged media must be discovered, it is recommended that you initiate a discovery operation every time you open the library door and insert media.

When a medium is imported, the system assigns it in one of the following ways: ● The medium is already catalogued. The medium belongs to the scratch pool, or to a storage policy copy to which it was assigned before it was exported. ● The medium is not already catalogued, and is successfully discovered. The system assigns the medium to the scratch pool that you select. ● The medium is not catalogued, and is not successfully discovered. The system assigns the medium to the unidentified media group. For details on discovering media within a library, see “Library Operations” in online Help.

222 Backup and Restore for Internet Data Center

Exporting Media Exporting is the process by which you physically remove one or more media from a library. When you export a medium, the data that it contains is no longer at the immediate disposal of the Galaxy system. If an operation (for example, restore or auxiliary copy) requires data from an exported medium, you will have to re-import the medium in order to complete the operation. Galaxy retains information about exported media; they do not have to be rediscovered if they are re-imported. There are two ways to export media: ● You can export media through the library’s mail slot (if one is available). ● You can open the library door and remove media from the storage slots by hand. Exporting media through a mail slot offers an advantage. The inventory update that is triggered by a mail slot export is much less time-consuming than the full inventory operation that is triggered when you close the library door. However, under certain circumstances you may want to open the library door even though a mail slot is available. For example, if you want to remove many media from a library at once, it may be faster to open the door than to use the mail slot. Media that are being written to or read from cannot be exported. It is recommended that you enter a description of the storage location and appropriate reference information when you export a medium. Note: Removing media from and closing the mail slots of some libraries may trigger a full inventory operation (rather than an inventory update).

For details on exporting media from a tape/optical library, see the “Library Operations” topic in online Help.

Resetting a Library and Drive Resetting a library unmounts all tapes from the drives in the library, and resets all the drives and the library so that they are ready for use. Resetting a drive unmounts the tape from the drive, and resets the drive so that it is ready for use. You can also perform this operation on a stand-alone drive. For details on resetting a library, see “Library Operations” in online Help.

Cleaning Drives Ensure that you have imported or moved a cleaning medium into the Cleaning Media Pool before you perform the drive cleaning operation. If a job is in progress in the drive you want to clean, the drive cleaning operation will fail. Ensure that the drive is free before you start the operation.

Chapter 4: Advanced Backup and Restore Operations 223

The drive cleaning operation is not available for stand-alone drives, Optical libraries, or RSM-controlled libraries. For Galaxy to perform the Clean Drive function, the library’s auto-cleaning feature must be disabled from the library’s front panel menu. For example, in the Exabyte X80 library you can use the following steps to disable the autoclean function: 1. Switch to LCD mode: On the main menu, select RobotControl, select LCD, then click Save. 2. Change the Autoclean Mode: On the main menu, select ConfigMenu, then select AutoclnSetup, then click DisableAutocln 3. Switch to SCSI mode: On the main menu, select RobotControl, then select SCSI, then click Save. Additional information on drive cleaning is available in the CommVault Galaxy CommCell Media Management Administration Guide.

Media Groups and Scratch Pools A scratch pool is a repository of media that are available for use. When a backup, synthetic full, or auxiliary copy operation requires a new medium, the system takes one from a scratch pool. Media arrive a scratch pool when they are: Assigned to a scratch pool. Media are assigned to a scratch pool when they are physically imported from outside the library. ● Logically reassigned between scratch pools. Media can be reassigned from one scratch pool to another scratch pool. ● Returned to a scratch pool. When data is pruned or deleted the system returns media to a scratch pool. ●

Every library has a default scratch pool, which Galaxy creates when the library is configured. When the system creates a storage policy for the library (for example, when the library or one of its drive pools is configured), the primary storage policy copy is associated with the default scratch pool. In addition, when you import new media into the library, this is the scratch pool to which they are assigned (unless you specify otherwise). You can create any number of additional scratch pools, and assign these to different storage-policy copies that access the library. You can also designate a user-defined scratch pool as the default for the library. (For information on storage policies, storage-policy copies, and changing the scratch pool associated with a storage policy copy, see the Galaxy Client Administration Guide for individual iDataAgents.) The ability to create scratch pools and assign them to specific storage policy copies enables you to ensure that critical operations always have the media that they need.

224 Backup and Restore for Internet Data Center

For example, assume that you regularly back up both a file server containing mission-critical data and a number of user computers. You may want to prevent situations in which less important computer backups use up all available media, causing vital file server backups to fail. You can do this by creating a scratch pool specifically for the storage-policy copies that conduct file-server backups. Galaxy also allows you to move media between scratch pools. In the preceding example, if you noticed that the supply of media in the scratch pool dedicated to the file server was getting low, you could logically reassign media from another scratch pool to the file-server pool. The following procedures are available under the “Scratch Pools” topic in online Help: ● Creating a Scratch Pool ● Viewing or Changing Properties of a Scratch Pool ● Viewing the Inventory of a Scratch Pool ● Importing Media into a Scratch Pool ● Moving a Specific Medium from One Scratch Pool to Another ● Moving a Number of Unspecified Media from One Scratch Pool to Another ● Deleting a Specific Medium from a Scratch Pool ● Exporting a Specific Medium from a Scratch Pool ● Deleting a Scratch Pool Galaxy allows you to establish a low watermark for every scratch pool. This parameter represents the minimum number of media that should be available from the scratch pool at all times. If the number of available media falls below the low watermark, Galaxy logs a message to the event log and adds an entry to the Scratch Pool Report. When you establish a low watermark, consider the media requirements of all operations (for example, backups, auxiliary copies, and Synthetic Full backups) that draw from the scratch pool. The low watermark should be high enough to ensure that you will be notified of the need for more media while there are still enough media available to allow running operations to complete. For example, if the operations that access a particular scratch pool regularly fill two media every week, you might set the low watermark at three. This way, Galaxy advises you every week to add more media to the scratch pool while it still contains sufficient media to handle its normal operational load. For information on media groups, storage policy copies, and other Galaxy entities that determine the load placed on a particular scratch pool, see the Galaxy Client Administration Guide.

Chapter 4: Advanced Backup and Restore Operations 225

Assigned Media Group The assigned media group is a repository of media that are used by Galaxy. When a backup, Synthetic Full, or auxiliary copy operation requires a new medium, the system takes one from a scratch pool and adds it to the assigned media group. As soon as the media is in use, its status is displayed as Active. If the medium is full or marked as full, the status is displayed as Full. Galaxy no longer writes to the media; media marked as full can only be used for restoring data.

Cleaning Media Pool The cleaning media pool is the logical repository for the cleaning media. When you configure a library for the first time, the system creates a cleaning media pool for each library. Galaxy will use the catalogued cleaning media during the drive-cleaning operation, if auto drive cleaning is not available for a library. If you do not identify the media as a cleaning media, Galaxy considers it to be regular media and attempts either to validate the drive or write on the media when you run a backup. Such an attempt would fail. The ability to identify cleaning media ensures that the validate and backup operations will not use them. Note: If your library manufacturer provides you with a special barcode labels for cleaning media, use these labels on your cleaning media. For example, cleaning media labels for some libraries start with the letters CLN. Because RSM supports the auto drive-cleaning function, Galaxy does not need the drive-related operations for RSM-controlled libraries. Clean Drive Option is not available for stand-alone drives.

The following procedures are available under the topic “Cleaning Media Pool” in online Help. ● Importing Cleaning Media to the Cleaning Media Pool ● Discovering Cleaning Media within a Library ● Moving a Cleaning Medium from Scratch Pool to Cleaning Media Pool ● Exporting Cleaning Media from the Cleaning Media Pool ● Deleting Cleaning Media

Exported Media Group Whenever media are exported from the library, which includes the spare media, used media, or cleaning media, the media are listed in the exported media group. All the media used in stand-alone drives are listed in the exported media group.

226 Backup and Restore for Internet Data Center

Unidentified Media Group The unidentified media group is a logical repository for media within a library that cannot be used by the Galaxy system. When you configure a library for the first time, the system creates one unidentified media group for the library. A medium may be placed in the unidentified media group for the following reasons: ● The medium contains data and had been used by other applications. ● The system encountered an error when it tried to discover the medium. ● The system encountered an error while initializing the medium (for example, the medium was damaged or write-protected). The following procedures are available under the topic “Unidentified Media Group” in online Help. ● Viewing the Properties of an Unidentified Media Group ● Moving Media from an Unidentified Media Group to a Scratch Pool ● Moving Several Media from an Unidentified Media Group to a Scratch Pool ● Exporting all Media from an Unidentified Media Group

Stand-alone Drive Operations A stand-alone library is a one-drive storage unit with no media storage capability, no medium changer, and no barcode reader. Note: Because stand-alone drives do not have the facility to store used media, it is your responsibility to label and store all used media in a secure and accessible location. It is strongly recommended that you physically label each stand-alone drive using the library name shown in the configuration window. This will help you identify the proper drive when Galaxy prompts you to insert a medium into a drive.

The following procedures are available in the online Help, under the topic “StandAlone Drive Operations”: ● Viewing or Modifying Properties of a Stand-alone Library ● Viewing or Modifying Properties of a Drive Pool ● Viewing or Modifying Properties of a Stand-Alone Drive ● Viewing or Modifying Properties of a Medium ● Making a Stand-Alone library Online or Offline ● Overwriting Tapes in Stand-Alone Drives

Chapter 4: Advanced Backup and Restore Operations 227

Media Operations in Stand-alone Drives Stand-alone libraries do not have an initial list of spare media. The system prompts you to insert a new medium whenever it is required. Galaxy creates an On Media Label (OML), which is a unique internal identifier (unique ID) for each medium, the first time you insert the media in the stand-alone library. Subsequently, you can provide your own unique ID for the medium. Whenever you insert a new medium, Galaxy prompts you to enter the unique ID and the storage location for the medium. This prompt is in the form of a pop-up message. You can run a backup or restore operation on a stand-alone drive by doing one of the following: ● Insert the correct medium in the stand-alone drive before starting an operation. Galaxy identifies the medium by using the OML and proceeds with the operation. Galaxy does not display any messages or prompts when it finds the correct medium in the stand-alone drive. ● Leave the stand-alone drive empty and wait for Galaxy to prompt you to insert the appropriate medium. After the medium is inserted, Galaxy uses the OML to identify the medium and proceeds with the operation when it finds the correct medium. ● Insert or have an incorrect medium in the stand-alone drive. After the medium is inserted, Galaxy uses the OML to identify the medium and proceeds with the operation when it finds the correct medium. Note: If an operator is not available to insert the required media in a stand-alone drive, it is recommended that you avoid scheduling jobs that use different storage policies. If you want to schedule jobs for a stand-alone drive, make sure that all of the jobs use the same storage policy. If a scheduled job uses a different storage policy from the one to which the medium in the drive belongs, the job cannot start until someone removes that medium and inserts another. This may defeat the purpose of scheduling the job.

All media available in a stand-alone drive are displayed in the CommCell Browser under the Exported Media pool except the currently used medium, which is displayed under the stand-alone drive.

Pop-up Messages Galaxy displays a pop-up message for every operation in the stand-alone drive. You do not have to respond to the pop-up messages generated by Galaxy for standalone drives. These messages are displayed for four minutes and automatically disappear after that time.

228 Backup and Restore for Internet Data Center

When you insert a new medium Galaxy displays a pop-up message prompting you to enter a unique ID and the storage location for the medium. You can either: ● Enter the information and click OK. ● Click OK without entering the information. ● Do nothing. The message is displayed for four minutes, and after four minutes it automatically disappears. You can however, add the information in the CommCell Browser, by using the Media Properties dialog box. If you do not subsequently add the information, the pop-up message will be displayed whenever you re-insert the medium, until you provide a unique ID for the medium. When you perform a backup or restore operation, Galaxy displays a pop-up message if it finds the stand-alone drive empty, or if does not find the correct media. Galaxy displays these messages on the MediaAgent computer to which the standalone drive is attached, and on all computers that have the CommCell Console (both MMC and/or Java GUI) open. For example, on the MediaAgent computer, if both the Java GUI and MMC are open, you will see three pop-up messages with the same message. You can click OK in any one of these messages. However, only a response on the MediaAgent computer will take effect. If you do not respond to the message, the message displays for four minutes and after four minutes it automatically disappears. The message displays again when Job Manager re-tries the job and does not find the required medium.

Migrating a Magnetic Library You can use the CommCell Browser to view the properties of magnetic libraries and mount paths, to take these entities online and offline, and to configure magnetic library alerts (e-mail notification). For a detailed explanation of Galaxy alerts, see the Galaxy CommServe Administration Guide. The user has the option of migrating a magnetic library to another MediaAgent. This may be helpful if the user wants to release the MediaAgent so that it can be used for a non-backup purpose. The migration is a logical rather than a physical operation. To use this feature, the MediaAgent that is being migrated to must have access to the same mount path as the MediaAgent that is being migrated from. Therefore, it is recommended that the MediaAgents within the user’s backup system have mirroring. Mirroring allows one MediaAgent (purple, for example) to be set up identically as another MediaAgent (green, for example). Using this example, purple, as a mirrored version of green, would be able to perform all of the MediaAgent functions that green performs. Magnetic Library Migration to another MediaAgent is supported for UNC paths and local paths for the Windows and UNIX File Systems. If mirroring is not an

Chapter 4: Advanced Backup and Restore Operations 229

option, the user must have mount paths containing UNC paths for Windows or the Network File System (NFS) mounted File System for UNIX. Also, before performing any operation, you should ensure that all mount paths are online or accessible. Cross-platform migrations are not allowed (that is, you cannot migrate a magnetic library from a MediaAgent for Windows to a UNIX MediaAgent, or vice versa). The following procedures are available in the online Help, under the topic Magnetic Disk Library Administration Procedures: ● Viewing or Changing Magnetic Disk Library Properties ● Viewing or Changing Mount Path Properties ● Migrating a Magnetic Library

Client Job Results Job results are viewed by using the Backup History and Restore History features. You can specify the job results directory to which the client computer’s backup and restore job results are written. Galaxy provides the following options to administer the job results directory from the subclient’s Properties dialog box. ● Change the job results location. If you change the job results location path, Galaxy copies all existing job results to the new path as well. ● Set a job results save period. You can establish a time period (days) for which backup and restore job results are maintained. ● Specify a disk capacity threshold to initiate pruning of job results. You can specify a disk capacity threshold that, if exceeded, causes Galaxy to prune job results. The disk is that disk on which the job results of the client computer are stored (probably a local disk). Note that capacity utilization refers to the combined disk usage of all data (including applications) stored on the disk; not just that portion used for job results. Note: Do not specify or relocate the job results directory to a directory that resides on a compressed drive.

Using Pipeline Pairs to Configure for Multiple Network Interfaces Many companies do not want backups to saturate their production network. The solution is to install a second, high-speed network on the servers for backup and restore data only. In some cases, multiple networks may be assigned for backup use. You can use Pipeline Pairs to configure Galaxy subclients to take advantage of these additional networks. Pipeline Pairs are configured at the subclient level.

230 Backup and Restore for Internet Data Center


To configure pipeline pairs 1. Open the subclient’s Properties dialog box and click the Storage Device tab. 2. Click Advanced and add or delete pipeline pairs in the bottom half of the window. When you click Add, each network connection available between the MediaAgent and the Client appears in a set of dropdown boxes. 3. Select a combination to create a Pipeline Pair.

Moving Data Within Pipeline Pairs If there are no Pipeline Pairs added, backup/restore data is moved across the default network connection. When you add Pipeline Pairs, the default network connection will relegate itself to handle only coordination data exchange between the CommServer, MediaAgent, and Client. All backup/restore data movement between the client and the MediaAgent will be on the added Pipeline Pairs. If more than two network connections are available between the MediaAgent and the client, additional Pipeline Pairs can be added. For example: If the ClientMediaAgent combination has three network connections available in total, you can have the default connection plus two Pipeline Pairs. Each backup/restore stream initiated between the Client-MediaAgent will use the Pipeline Pairs alternately in a round-robin fashion. Stream 1 will use the first pair, Stream 2 the second, Stream 3 the first, and so on. Note that you cannot split a data stream over two different Pipeline Pairs. To use Pipeline Pairs, both the MediaAgent and the Client must have multiple adapters installed and properly configured. The connections should not share the same data path (routers, for example) in order to take full advantage of the additional bandwidth. You must also have correct IP Address/Name resolution before you can add Pipeline Pairs.

Configuring Multiple Adapters A multi-homed computer is one that has two or more network interface cards (NICs). To ensure proper name/IP address resolution within Galaxy, it is necessary to uniquely name each NIC in the domain name system (DNS). An example of this is a computer named amber, with fully qualified host names of amber1.nwtraders.com and amber2.nwtraders.com, and the computer has two NICs with the following IP addresses: ● First NIC: 150.128.4.78 ● Second NIC: 150.128.6.32 To ensure that both interfaces can be resolved, you would need to define unique names within DNS, such as: ● amber1.nwtraders.com 150.128.4.78 ● amber2.nwtraders.com 150.128 6.32

Chapter 4: Advanced Backup and Restore Operations 231

With Windows 2000, the DNS tab allows you to assign only a unique domain name. This is because identifying each network connection uniquely should be accomplished by providing unique domain names appended to the computer name. On the DNS tab, you can use the DNS suffix for this connection value to define a unique domain name. If you follow this convention, do not select the Register this connection’s addresses in DNS check box. Because of a feature in the Windows 2000 DNS, you will get two identical name entries in your DNS database under the same primary Forward lookup zone regardless of which domain the second adapter was assigned to. If this happens, all Pipeline Pairs will appear identical to Galaxy. To overcome this, you must manually enter the host and pointer records into the appropriate Forward and Reverse lookup zones on the DNS server. The Windows 2000 client DNS Resolver service caches both negative and positive responses received from a DNS server. This means that if you make a change to DNS server database or hosts file to remedy a negative response, you might not see the positive change because the DNS client continues to draw its response from the cache. When working with DNS changes and a Windows 2000 system, you should always run ipconfig /flushdns on the client to clean out the local DNS cache. It is also important to note that with Windows NT and Windows 2000 the local hosts file is always pre-loaded into the DNS cache and is, therefore, checked first during name resolution.

iDataAgents The Galaxy system includes iDataAgents for Windows 2000, Exchange 2000, and SQL Server 2000, as well as subclients for each backup set.

Managing Subclients Subclients are used to back up different portions of the file system on a client computer. Initially, the Galaxy system defines a default subclient for each backup set. At that time, the default subclient contains the entire file system and the system state. If you define other subclients within the same backup set, the default subclient contains the entire file system, except for those portions that have been assigned to the other subclients. When you define a subclient, you need to: ● Provide a subclient name. ● Define the content of the subclient. ● Associate a storage policy to the subclient

232 Backup and Restore for Internet Data Center

You can use the Subclient Properties dialog box to enter this information. Although this information alone is sufficient to declare a subclient, you can establish other subclient properties as well. For example, you can: ● Create a backup filter. ● Select the subclient’s data-compression scheme. ● Declare backup-triggered processes.


To create a new subclient within a backup set Before you begin, it is important not to create a subclient while the parent backup set or any sibling subclient is backing up. 1. In the CommCell Browser, right-click the backup set for which you want to create the subclient, and then on the shortcut menu, click New Subclient. 2. In the Subclient Properties dialog box, on the General tab, type the name (up to 32 characters) of the subclient that you want to create. The system state backup is only triggered on the default subclient. (The default subclient always backs up the system state. It is not optional.) 3. On the Contents tab, type the subclient’s content in the Enter New Content field. Optionally, you can use the Browse button to enter the content. 4. When specifying a UNC data path, click As User, and enter the user account information for the domain user with permissions for that path. 5. On the Subclient Properties dialog box, on the Storage Device tab, select a storage policy that you want to associate with this subclient from the storage policy menu. 6. Click Add. Optionally, you can establish other subclient properties, such as creating a backup filter, declaring backup-triggered processes, or selecting the subclient’s data-compression scheme and pipeline configuration. 7. Click OK.

Renaming a Subclient You can rename any user-defined subclient at any time. However, Galaxy does not allow you to rename a default subclient. Do not attempt to rename a subclient that is being backed up.


To rename a subclient 1. In the CommCell Browser, right-click the subclient that you want to rename, and then on the shortcut menu click Properties. 2. On the Subclient Properties dialog box, on the Storage Device tab, type the new name in the Subclient name field, and then click OK. The CommCell Browser updates the subclient with its new name.

Chapter 4: Advanced Backup and Restore Operations 233

Changing the Content of a Subclient The portion of a File System that is assigned to the subclient is called the subclient content. You can view and change the content of any subclient from the Subclient Properties dialog box. Do not change the content of the default subclient from its initial setting (that is, \). This setting ensures that the subclient content contains all portions of the File System not contained by other subclients. If you change the setting to some path, the default subclient will back up only the data pertaining to that path. The Subclients within the backup set will no longer back up the File System in its entirety. Do not change the content of a subclient that is being backed up.


To change the content of a subclient 1. In the CommCell Browser, right-click the subclient whose content you want to change, and then on the shortcut menu click Properties. 2. Click the Contents tab of the Subclient Properties dialog box. 3. To include a file or folder in the content of the subclient, do one of the following: ● In the Enter New Content field, manually enter the path (including the drive letter) of the file or folder that you want to add and then click Add. Repeat this step if you want to add more files or folders to the content. or ● Clicking Browse to browse and select the path. In the Browse dialog box, double-click the file system of the client computer, click the file or folder that you want to include, and then click Add. Repeat this step for each additional entry. ● When specifying a UNC data path, click As User, and enter the user account information for the domain user with permissions for that path. 4. To save your content changes, on the Content tab of the Subclient Properties

box, and then click OK.

Using On-Demand Backups On-demand backups allow you to secure data and the system state immediately without having to wait for the scheduled backup time. This capability can be useful if the following applies: ● You have some particularly valuable data that you need to secure immediately. ● Your data is not routinely secured through a backup schedule and you want to back up your data.

234 Backup and Restore for Internet Data Center

Using on-demand backups, you can initiate full, incremental, and differential backups. You can initiate an on-demand backup on the following levels: ● A selected subclient ● A selected backup set ● The default backup set Selecting a backup set backs up the entire File System on the client computer. Selecting a subclient backs up only that portion of the File System that is mapped to that subclient. Starting a backup on a backup set causes Galaxy to start individual backups for each subclient contained therein. If the subclients are associated with the same storage policy, their backups will run serially, unless that storage policy is configured to accommodate multiple data streams. The Windows 2000 system state backup is initiated from the default subclient in the backup set. The system state is always backed up using a full backup, even if that subclient runs a different kind of backup on the file system portion of the data.


To start an on-demand backup of a selected subclient 1. In the CommCell Browser, right-click the subclient that you want to back up and then on the shortcut menu, click Backup. 2. In the window, select the type of backup that you want to initiate. 3. After selecting the backup type and any advanced options, click OK. You can track the progress of the backup operation from the Job Controller window.




To start an on-demand backup of a selected backup set 1. In the CommCell Browser, right-click the backup set that you want to back up, and then on the shortcut menu, click Back up All Subclients. The system prompts you to confirm that you want to back up all the subclients contained within the selected backup set. Click OK to proceed. 2. In the window, select the type of backup that you want to initiate. Do not select Synthetic Full; it is a special type of backup. 3. After selecting the backup type and any advanced options, click OK. You can track the progress of the backup operation from the Job Controller window.




To start an on-demand backup of the default backup set 1. In the CommCell Browser, right-click the File System icon corresponding to the client computer that you want to back up, and then on the shortcut menu, click Back up Default Backup set. 2. The system prompts you to confirm that you want to back up all the subclients contained within the backup set. Click OK to proceed.

Chapter 4: Advanced Backup and Restore Operations 235

3. After selecting the backup type and any advanced options, click OK. Galaxy

starts the backup operation. You can track the progress of the backup operation from the Job Controller window. When the backup completes, Galaxy displays a confirmation message.

iDataAgent for Windows 2000: Browse and Restore Operations Browse operations allow you to view the data that has been backed up for a client computer without actually restoring the data. Restore operations retrieve the data from the backup media and restore it to a specified location. Although you can restore data without first browsing, in practice the two operations often go hand-in-hand. Browse and restore options allow you to do the following: ● Restore one or all versions of a file. ● Restore data to a mapped network drive. ● Restore data without browsing.


To browse and restore file system data to the client computer 1. In the CommCell Browser, right-click the backup set whose data you want to browse, and then on the short-cut menu, click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, use the File System tree to open the structure of the file system. 5. In the Browse dialog box, select the files and/or directories that you want to restore and then click Restore All Selected. 6. In the Restore Options dialog box, select the restore options that you want to use. 7. If you want to select any additional restore options, click Advanced and select the options that you want. 8. After you have selected the restore options, the system displays the progress bar and starts to restore the data. Observe the progress bar to monitor the restore process. If you want to browse the same backup set again, perhaps using different browse-time thresholds, in the Browse dialog box click New Browse.

236 Backup and Restore for Internet Data Center

Restoring System Databases The system state is always backed up in its entirety as a full backup, regardless of the type of file backup being performed. For example, an incremental backup of the default subclient will perform an incremental backup of the file system and a full backup of the system state. Included with the system state backup data are several other databases. Because these other databases are separate elements, they can be selectively restored, without performing a full system-state restore. These database elements include the following: ● Event logs ● RSM database ● Terminal Server database ● Quota information ● Content indexing catalogs You have the choice of restoring these items when you perform a restore operation of the system databases. These databases are only available for restoration if they have been installed and backed up.


To restore the system databases 1. In the CommCell Browser, right-click the backup set that contains the System Databases to restore, and then click Restore System Databases. 2. In the Restore System Databases Options dialog box, accept the defaults or change the option selections. 3. Click OK. Galaxy initiates the system state restore job. Some services may be interrupted during the time that the databases are restored. After the restore operation is complete, ensure that the services are returned to the online state.

Browsing and Restoring File Versions The Browse/Restore dialog box allows you to browse different backed up versions of the same file and then restore either any one version of the file or all versions of the file. When you restore all file versions simultaneously, Galaxy appends a different number to the file name so that each version remains unique. Before you begin browsing and restoring file versions, note the following: ● If you plan to restore more than one version of the same file by restoring each version individually, be sure to restore them to different locations to prevent overwriting your files. ● If full backup transparency is enabled, browsing will return all versions of the selected files. However, by default, browse returns only those files that exist back to the most recent full backup (full backup transparency is disabled). If you need to obtain earlier versions, set the Browse To date of the browse operation to a date prior to the most recent full backup.

Chapter 4: Advanced Backup and Restore Operations 237 ●




Windows 2000 includes a directory called Tombstone Lifetime, which uses Active Directory® directory service and has a default setting of 60 days. If you attempt to restore Active Directory data after this date has passed, the system will reject the data. Do not attempt to restore data that has exceeded its lifetime.

To restore one version of a file 1. In the CommCell Browser, right-click the backup set that contains the file(s) you want to browse, and then on the shortcut menu, click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, use the File System tree to open the structure of the file system. 5. Right-click the file whose versions you want to browse, and then click View All Versions. 6. In the window, click the file version that you want to restore and then click Restore. 7. In the Restore Options dialog box, select the restore options that you want to use. 8. If you want to select any additional restore options, click Advanced and select the options you want. 9. After you have selected the restore options, the system displays the progress bar and starts to restore the data. Observe the progress bar to monitor the restore process. If you want to restore another version of the same file, repeat this procedure starting with Step 6. If you want to browse the versions of other files, repeat the entire procedure.




To restore all versions of a file 1. In the CommCell Browser, right-click the backup set that contains the file(s) that you want to browse, and then on the shortcut menu, click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use and click OK. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, use the File System tree to open the structure of the file system. 5. Right-click the file whose versions you want to restore, and then click Restore All Versions.

238 Backup and Restore for Internet Data Center 6. In the Restore Options dialog box, select the restore options that you want to

use. 7. If you want to select any additional restore options, click Advanced and select the options you want. 8. After you have selected the restore options, the system displays the progress bar and starts to restore the data. Observe the progress bar to monitor the restore process.

Restoring Data to a Mapped Network Drive Galaxy allows you to restore data to a client computer’s mapped network drives. The restored data assumes the access characteristics of the destination share. Before you begin, remember that mapped network drives exist as Windows share directories (that is, shares) on some other computer on the network. For data security reasons, these shares possess access privileges that determine who can access the share and the rights under which access is permitted. If your Windows account does not have privileges to write data to the share, you must be able to provide the user name and password of a Windows account that does have these privileges. Also ensure that the Windows share to which you intend to restore the data is accessible as a mapped network drive from the destination computer.


To restore data to a mapped network drive 1. In the CommCell Browser, right-click the backup set whose data you want to browse, and then from the shortcut menu, click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, use the File System tree to open the structure of the file system. 5. In the Browse dialog box, select the files and/or directories that you want to restore, and then click Restore All Selected. 6. In the Restore Options dialog box, select the restore options that you want to use. 7. Ensure that the destination computer is the computer that has the mapped drive, not the computer that has the share. Also, if the data did not originate from the mapped drive, type the destination path starting with the mapped drive letter in the Restore to Same Paths field (for example, H:\Sales\Monthly Reports). 8. If you want to select any additional restore options, click Advanced and select the options you want.

Chapter 4: Advanced Backup and Restore Operations 239

9. If you do not have Change permissions for the share that you intend to restore

the data to, you must go to the Advanced Restore Option dialog box, select Impersonate NT User and then provide the logon and password of a Windows account that does have these permissions; otherwise, the data cannot be restored to the selected share. If you can copy or create a file in the share, you should be able to restore data to that share without having to select this option. Note: If the user account is established as a domain user account, you must enter a fully qualified user name (for example, domain_name\user_name where domain_name is the name of the domain and user_name is the user name) and password.

10. After you have selected the restore options the system displays the progress bar

and starts to restore the data. Observe the progress bar to monitor the restore process.

Restoring Data Without Browsing If you know the path of the data that you want to restore, you can restore it without browsing. This procedure is most appropriate when you want to restore data from a single path. If you want to restore data from multiple paths, you should select the data from the Browse window.


To restore data without browsing 1. In the CommCell Browser, right-click the backup set that contains the data you want to restore and then click Restore. 2. In the Restore dialog box, type the path of the data that you want to restore. Note that Galaxy does not back up multiple copies of mounted data. If a backup includes more than one mount point to the same drive, Galaxy backs up the data only one time. To restore data in mounted volumes, you must type the path of the first point that is mounted to the drive. 3. In the Restore Options dialog box, select the restore options that you want to use. 4. If you want to select any additional restore options, click Advanced and select the options you want from the dialog box. 5. After you have selected the restore options, the system displays the progress bar and starts to restore the data.

Finding a File or Directory The Find operation allows you to search the backup archives for any file or directory name or name pattern. It is a type of browse operation. The Find operation lets you use the system to locate files or directories with specific names or naming patterns.

240 Backup and Restore for Internet Data Center

The Find operation supports a number of wild card characters (for example, * and ?) to broaden or narrow the scope of your searches. The supported wild card characters are provided and discussed in “Restoring Data Using Wildcard Expressions” later in this chapter.


To find a file or directory 1. In the Commcell Browser, right-click the backup set that contains the data you want to find, and then click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, right-click the backup set, and then click Find. 5. In the Find dialog box, type the name or wildcard pattern of the file or directory that you want to find. By default, the Look In field is set to the backup set that was selected in Step 1. If you want to search the backups of a different backup set on the same client computer, you can choose another backup set in this field. 6. For optional features, select the Time Range tab. From this tab you can select the following options: ● Search from the latest backup data. When selected, Galaxy searches all backups, up to the most recent backup, for the specified data. (This option is selected by default.) When cleared, Galaxy searches all backups for the specified data up to the specified time. ● Image Browsing. If selected, Galaxy searches for the specified data based on the image of the data as it existed as of the specified browse times. If cleared (No Image Browse), Galaxy searches for the specified data based on all the data that was ever backed up as of the specified browse times. ● Advanced. Provides access to the Advanced Browse Options dialog box, which allows you to narrow the scope of the Find operation. 7. After you have selected your Find options, click Find Now. 8. After the files or directories that match the specified name or pattern are dis-

played, right-click the file or directory name that you want and perform one of the following operations: ● Restore the file or directory. ● View all Versions of the selected file (Not available for directories.) ● Restore all Versions of the selected file (Not available for directories.)

Chapter 4: Advanced Backup and Restore Operations 241

Filtering Data from Restore Operations In the Advanced Restore Operations dialog box, you can specify the files, directories, and file name patterns that you want to filter from the restore data.


To filter data from a restore operation 1. You can access the Restore Option dialog box by performing either a browse operation or a restore operation on a backup set. 2. In the Restore Option dialog box, click Advanced. 3. From the window, type the files, directories, and file name patterns that you want to filter in the Filter Paths pane. Click Add to specify your filter entries. Each entry must be specified as a complete path and must be a child of the Source Paths pane. Wildcard entries must be expressed as complete paths (for example, C:\Test\*.dll). 4. The restore filter supports the following wildcard characters. To broaden the scope of your filtering, you can use the character *, which stands for any number of characters, or the character ?, which stands for any one character. You can also use a combination of wildcards in a single expression (for example, access?.h*).

Using Wildcard Expressions to Restore Data Galaxy allows you to restore data using wildcard expressions. You can restore the data directly or browse it first and then restore it. This functionality gives you the ability to restore files and/or directories that have a common naming convention (for example, Msde2.doc and Msj4j.doc). The supported wildcard characters are listed in Table 4.20. Table 4.20: Supported Wildcard Characters Wild card

Signifies ...

*

Any number of any characters. For example:*.doc Any file name with the extension “.doc” (for example, status.doc, mission.doc) Any file name that begins with the letter a, and has the extension .dll (for example, alsvc.dll, advdcc.dll)

?

Any one character. For example: access? Any file name that begins with the word access, followed by any one character (for example, access1, access5)

[]

Any range of characters. For example: [ei]nsure.doc Any file name that ends with the term nsure.doc, and begins either the letters e or i. (for example, ensure.doc, insure.doc) [a-m].doc Any file name that ends with the extension .doc and begins with the letters a through m, inclusive. (continued)

242 Backup and Restore for Internet Data Center Wild card

Signifies ...

[! ]

The negation of a range of characters. For example: [!ei]nsure.doc Any file name that ends with the term nsure.doc, but does not begin with the letter e or the letter i. (for example, unsure.doc)

**

Any directory level. For example: C:\**\Move.cpp The file named Move.cpp located at any directory level under the c: drive. (for example, C:\info\com\Move.cpp)

If you specify the expression by itself without a path (for example, *.doc), Galaxy searches for and returns all data within the backup set that satisfies the expression. By preceding the expression with a path, you can narrow the scope of the restored data. For example, specifying C:\My documents\*.doc would restore only those files and directories within the C:\My Documents directory with the extension .doc. When restoring directories, if you specify a wildcard pattern that matches the name of a directory, Galaxy restores the directory, but none of the directory’s contents. For example, if your wildcard restore string is tem?, Galaxy restores any and all data named with a four-character string starting with the letters t, e, and m. If there is a directory whose name satisfies that criterion (for example, C:\Temp) only the directory would be restored; however, none of the files or any subdirectories contained therein would be restored. Galaxy allows you to select specific data to be restored in addition to specifying the data through the wildcard expressions. This is known as mixed mode restore. The general result of a mixed mode restore is that Galaxy restores the selected data as well as the data that satisfies the wildcard expression(s), with one important exception: all directories that are to be restored, whether they were specifically named or selected, or merely satisfy the wildcard expression(s), are restored without their content (that is, any directory to be restored is handled in the same way as if the directory were being restored as a result of a wildcard expression).

Using Wildcards to Restore Data Directly This method of restoring data is the fastest because you need not browse the backup data first. However, you may need to have a better working knowledge of the organization of the data that you want to restore.


To directly restore data using wildcards 1. In the CommCell Browser, right-click the backup set that contains the data that you want to restore, and then click Restore.

Chapter 4: Advanced Backup and Restore Operations 243

2. In the Restore dialog box, type the wildcard expression that corresponds to the

data that you want to restore. For the broadest restore, omit the path. To narrow the scope of the restore operation, you should precede the expression with a path. 3. In the Restore Options dialog box, select the restore options that you want to use. 4. Optionally, click Advanced if you want to access the dialog box to enable additional capabilities (for example, specify another restore wildcard expression or some specific path). If you enter both specific data paths and wildcard expressions (that is, a mixed mode restore), Galaxy informs you that any directories that are to be restored in the operation will be restored empty. 5. After you have selected the restore options, the system displays the progress bar and starts to restore the data.

Using Wildcards to Browse and Restore Data This method for restoring data uses the browse data feature. This feature can be helpful when you are uncertain of the organization of the data that you want to restore.


To browse and restore data using wildcards 1. In the CommCell Browser, right-click the backup set that contains the data that you want to restore, and then click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. In this procedure, the Client Computer field is unavailable because it was already determined when the backup set was selected in Step 1. 3. In the Advanced Browse Options dialog box, select any additional browse options. 4. In the Browse dialog box, use the File System tree to open the structure of the file system. 5. In the Browse dialog box, select the data that you want to restore, and then click Restore All Selected. You must select data from the Browse dialog box, even if you want to restore data by using only a wildcard expression. If you do not select any data (even one file), Galaxy cannot provide you access to the Advanced Restore Option dialog box, which you need in order to enter the wildcard expression. If desired, you can always clear the data as described later in this procedure. 6. In the Restore Options dialog box, select the restore options that you want to use and then click Advanced. In the Advanced Restore Option dialog box, the Source Paths pane shows the path of the data that you selected in Step 5.

244 Backup and Restore for Internet Data Center 7. In the Advanced Restore Option dialog box, do one or both of the following: ●

●

To clear the data that you selected in the Browse dialog box, select the entry in the Source Paths pane and click Delete. To specify a restore wildcard expression or some specific path, in the Source Paths pane, click Add, enter the expression or path in the Enter Path dialog box, and click OK.

Repeat these steps to enter additional wildcard expressions. 8. In the Advanced Restore Option dialog box, select any other advanced restore features as desired and click OK. If you enter both specific data paths and wildcard expressions (that is, a mixed-mode restore), Galaxy informs you that any directories that are to be restored in the operation will be restored empty. 9. In the dialog box, click OK. 10. After you have selected the restore options, the system displays the progress bar and starts to restore the data. Observe the progress bar to monitor the restore process.

Database iDataAgent for Exchange 2000 Server You can use iDataAgent for Exchange 2000 Server to backup and restore your data in a variety of ways.

Using Subclients to Establish Parallel Backups You can back up an entire instance more quickly by scheduling multiple subclients for simultaneous backup, so that the backups proceed in parallel and take less time than if the instance client were not divided into separate subclients. However, in order for the subclient backups to run in parallel, they must either be configured to use different storage policies, or to use a storage policy configured to have at least as many data streams as the total required for all the subclients that you want to back up in parallel. If any of the subclients are configured to use the same storage policy, and that storage policy is not configured for enough data streams, then there will be contention for media group resources, and the competing subclients will back up serially.

Restore Operations Restores are one of the primary functions of the Galaxy system. Galaxy provides two general operations that help you retrieve backed up data: browse and restore. A browse operation allows you to view the database elements that have been backed up for a client computer running Exchange 2000 before you restore the data. This enables you to easily identify the elements that you want to restore. The restore operation then retrieves the database elements from the backup media and restores them.

Chapter 4: Advanced Backup and Restore Operations 245

Browsing Data

A browse operation provides a snapshot of the databases that been backed up by iDataAgent for Exchange 2000 Server. It does this by retrieving the index file(s) of the related subclient(s). The results are returned to the CommCell Console, which graphically displays those databases that are within the selected subclient that has been backed up. From the CommCell Console display, you can select some or all of the data and restore it using a restore operation. Restoring Data

The restore operation retrieves the data that you select in the CommCell Console. The Galaxy system provides a powerful set of restore options that enable you to specify and restore only the data that you need. To properly specify the data, you should have a basic understanding of how the Galaxy system restores databases. The restoration process can take place under a variety of circumstances, as described in the following paragraphs. Browse and Restore Scenarios

The database iDataAgent for Exchange 2000 Server allows you to browse and restore the content and organization of data that is secured through standard backup operations. A browse operation displays all of the database backups for the iDataAgent as of a specified time; a restore operation restores some or all of the selected databases. Database Retrieval

When you browse or restore data, by default the system returns the requested data based on the latest backups available. This is usually the information that users are interested in. The system uses the current date and time as the effective date.

Limitations of the Default Settings of Browse and Restore Operations The default settings of the restore operation (that is, restoring data from the current full backup cycle) may not meet your needs in all circumstances. It can restore only the latest version of a database. Further, if the requested data was deleted before the most recent full backup, it cannot be restored by the default mode of operation. The Galaxy system provides various restore options that extend its restore capabilities and allow you to control the search and retrieval process. These options are discussed in the following sections.

246 Backup and Restore for Internet Data Center Controlling the Browse Time Interval

The browse operation provides you with the To option, which allows you to control the starting point of the browse retrieval process. Browse searches extend backwards in time starting with the To option. This feature can be useful if you need to restore any of the following: ● A previous version of a database ● The contents of a database from an earlier date ● Data that was deleted prior to the most recent backup The Time-of-Day Element

The specification for the To option includes not only the date, but the time-of-day (that is, hours and minutes) as well. You should specify the time when isolating a backup on a date on which two or more backups occurred. (Note that this condition can occur even if backups are scheduled only once a day. For example, someone may have launched an on-demand backup in addition to a scheduled backup. Also, depending on the size of a backup and the time it is scheduled to begin, a backup can start before midnight on one date and finish on the next date. In determining whether to include a backup in a search, the Galaxy system uses the time that a backup completes. The To option causes the Galaxy system to start its browse search using the most recent backup that completed before the specified date and time. Scheduled Restore Operations

When you want to restore data, you usually need it immediately. However, there may be times when you do not need the data right away. Using the scheduling feature, you can schedule a restore operation. As with scheduled backups, a scheduled restore operation relieves you of having to manually initiate the operation. This feature can be particularly useful if you want to restore a large amount of data, but would prefer to do so at a time when either the client computer (that is, the Exchange 2000 Server) is not in use or network utilization is low (assuming the data must traverse a network).

Restoring Data to Exchange 2000 Server Before you start restore operations, ensure that you have met the following requirements and performed the following operational procedures. Restoring System State First

If you delete or change the properties of any Exchange 2000 object that is related to Active Directory, you must first restore the system state before you can restore data to the Exchange 2000 database and complete the retrieval of the container. Perform a non-authoritative restore. This will prevent the restore from overwriting the current system state data. (The system state restore restores Exchange components and information to Active Directory).

Chapter 4: Advanced Backup and Restore Operations 247

Backing Up after a Restore

After you perform a restore operation on the Exchange 2000 database, a full backup is required before a scheduled pre-selected backup (incremental or differential) can successfully occur.


To browse and restore data to Exchange 2000 1. In the CommCell Browser, right-click the Exchange 2000 database subclient whose data you want to browse, then click Browse Backup Data. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. If specifying a browse time, click Advanced for the dialog box. 4. In the Browse/Restore dialog box, double-click Microsoft Information Store and select the storage group(s) or specific information store(s) that you want to restore. 5. When you are finished selecting items to restore, click Restore All Selected. (Click New Browse to edit the Browse selection.) 6. In the Restore Options dialog box, select the restore options that you want. 7. Click Advanced if you want to restore using a selected copy precedence. This brings up the Advanced Restore Options dialog box. 8. When the data is restored, the system displays a confirmation message. In the confirmation window, click OK. You can click Detail to review information on the restore operation. 9. Perform a full backup of the database. This is required before a scheduled preselected backup (incremental or differential) can occur.

Mailbox iDataAgent for Exchange 2000 Server: Restore Operations Galaxy provides two general operations that help you retrieve backed-up data: browse and restore. These operations are performed at the backup-set level, which allows you to browse and restore Exchange 2000 data for an entire server. The mailbox iDataAgent for Exchange 2000 Server allows you to browse and restore both complete mailboxes and individual messages.

Browsing Data A browse operation provides a view of the data that has been backed up for a client. It does this by retrieving the index file(s) of the related subclient(s). The results are returned to the CommCell Console, which displays those mailboxes that have been backed up and are within the selected backup set. From this structure, you can select a mailbox folder and browse individual backed-up messages. From the CommCell Console display, you can select some or all of the data and restore it using a restore operation.

248 Backup and Restore for Internet Data Center

Restoring Data The restore operation retrieves the data that you select in the CommCell Console. The mailbox iDataAgent for Exchange 2000 Server does not require that you browse the data first when you are restoring a complete mailbox. If you know the path of the mailbox that you want to restore, you can type it in the Restore dialog box and perform the restore operation directly. The Galaxy system provides a powerful set of restore options that enable you to specify and restore only the data you need. To properly specify the data, you need a basic understanding of how the Galaxy system restores mailboxes and messages. The following sections describe the restoration process under a variety of circumstances.

Browse and Restore Scenarios The Image Mode is the default for browse and restore operations. An Image refers to the content and organization of Exchange 2000 mailbox data that is secured through standard backup operations. An ”image browse” operation displays the Exchange 2000 mailbox structure, as it existed at a specified time. An image restore operation restores Exchange 2000 mailbox data or a specified portion thereof. You can browse the mailboxes within a backup set, the folders within a mailbox, or the messages within a folder: For full mailbox restores a browse operation displays the mailbox backups that existed for the backup set as of a specified time and the restore operation restores some or all of the backup set’s mailboxes. For folder restores, a browse operation displays the folder backups that existed within the mailbox as of a specified time, and the restore operation restores some or all of the mailbox folders. For message restores, a browse operation displays the message backups that existed within the folder as of a specified time, and the restore operation restores some or all of the folder’s messages. When you browse or restore data, by default the system returns the requested data based on the latest backups available. The system uses the current date and time as the effective date. The following examples show how single mailboxes, folders, and messages are restored.

Single Mailbox Retrieval Assume that on a given day you request the most recent version (that is, the default) of a mailbox. In response, Galaxy retrieves the most recent index file. It searches the index for the most recent version of the mailbox, retrieves the mailbox from the backup media and restores it to the client computer.

Chapter 4: Advanced Backup and Restore Operations 249

Folder Retrieval Assume that on a given day you request the restoration of an entire mailbox, as it existed in its most recent state (that is, the default). Using the latest index file, Galaxy retrieves the most recent copy of each folder until all the folders have been restored.

Message Retrieval Assume that on a given day you request the most recent version of a specific message. In response, Galaxy retrieves the most recent index file, searches the index for the most recent version of the message, retrieves the message from the backup media, and restores it to the client computer.

Limitations of the Default Settings of Browse and Restore Operations The default settings of the restore operation (that is, restoring data from the current full backup cycle) may not meet your needs in all circumstances. It can restore only the latest version of a mailbox, folder or message. Furthermore, if the requested data was deleted before the most recent full backup, it cannot be restored by the default mode of operation. The Galaxy system provides various restore options that extend its restore capabilities and allow you to control the search and retrieval process. These options are discussed in the following sections.

Controlling the Browse Time Interval The browse operation includes the To option button, which allows you to control the starting point of the browse retrieval process (remember, browse searches extend backwards in time starting with the time that is specified using To option button). This feature can be useful if you need to restore any of the following: ● A previous version of a database ● The contents of a database as of an earlier date ● Data that was deleted prior to the most recent backup

The Time-of-Day Element The specification for the To option button includes the date and the time of day (that is, hours and minutes). Specifying the time is necessary when isolating a backup on a date in which two or more backups occurred. (Note that this condition can occur even if backups are scheduled only once a day. For example, someone may have launched an on-demand backup in addition to a scheduled backup. Also, depending on the size of a backup and the time it is scheduled to begin, a backup can start before midnight on one date and finish on the next date.) In determining

250 Backup and Restore for Internet Data Center

whether to include a backup in a search, the Galaxy system uses the time that a backup completes. The To option button causes the Galaxy system to start its browse search using the most recent backup that completed before the specified date and time.

Browsing Data from Before the Most Recent Full Backup In the browse operations described previously, the most recent full backup bounds the searches. There may be times, however, when you want to browse data that is older than the most recent full backup. The way to access that data is to specify a To date that pre-dates the full backup. Remember, the To date establishes the starting point of the search. Consequently, using a To date that pre-dates the most recent full backup starts the search in the previous full backup cycle. This is only valid if the data in that full backup cycle has not expired.

Cross-client Restore Operations By default, Galaxy restores data to the client computer (the Exchange 2000 Server) from which it originated. If you want, you can also restore the data to a different client computer, as long as the mailbox iDataAgent for Exchange 2000 Server is installed on the target system. This is called a cross-client restore. ● The restore destination must be on another server running Exchange 2000 on which the mailbox iDataAgent for Exchange 2000 is installed and operational. ● The destination server must reside in the same CommCell as the server that is being backed up. ● The mailbox must exist or be created on the destination server running Exchange 2000 before the restore operation is started. ● You must have user-management capabilities for Galaxy restores on both the source and destination computer to perform a cross-computer restore. When you perform a cross-client restore, the restored data assumes Exchange 2000 permissions that it had originally and the Windows NT security attributes (permissions) of the parent directory.

Scheduled Restore Operations When you want to restore data, you usually need it immediately. However, there may be times when you do not need the data right away. You can use the scheduling feature to schedule a restore operation. As with scheduled backups, a scheduled restore operation relieves you of having to manually initiate the operation. This feature can be particularly useful if you want to restore a large amount of data, but would prefer to do so at a time when either the client computer (that is, the Exchange 2000 Server) is not in use or at a time when network utilization is low (assuming the data must traverse a network).

Chapter 4: Advanced Backup and Restore Operations 251

Restoring Mailbox Data to Exchange 2000 Restores are one of the primary functions of the Galaxy system. Browse operations allow you to view the backup data (backed up at the backup-set and subclient levels), giving you access to the Exchange 2000 mailboxes. This enables you to easily identify the mailboxes, folders and messages that you want to restore. The Browse/Restore window is the central window from which you browse and restore data. Restore operations retrieve the data from the backup media and restore it to the desired location. The Find Message feature is a powerful search tool that searches the backup archives for any messages that match the pattern used in the search. The Find operation lets you locate messages with specific naming patterns. Before starting restore operations, ensure that you have met the following requirements and performed the following operational procedures: ● Restore Failure Housekeeping. If a restore job fails in progress, and there are entries in the restore list, there may be leftover items in the GalaxyAdmin mailbox (which is associated with the required GalaxyAdmin profile on the Exchange 2000 Server). If so, open the GalaxyAdmin mailbox and remove any mailboxes, folders, or messages left over. Be sure that there are no restores in progress or scheduled during this procedure. ● Disabling Storage Limits. Before performing a mailbox, mailbox folder, or mailbox message restore, ensure that the storage limits are disabled. Otherwise the storage limit may prevent the entire list of items from being restored, even though the restore job may report success. The following procedure describes how to remove or disable any storage limit before performing a restore operation.


To disable storage limits 1. In the Exchange 2000 Server software hierarchy view, under the server running Exchange, right-click a mailbox store or public store and then click Properties. 2. On the Limits tab, remove or disable any storage limits. Note: Storage limits can be set from an individual mailbox, or use the value taken from the Store Properties dialog box. If any individual mailboxes have set storage limits, disable them as well.

To perform this procedure you must have User-Management permissions on the Galaxy system. User Management permissions for Galaxy restore operations are required on both the source and destination computer to perform a cross-computer restore.

252 Backup and Restore for Internet Data Center


To browse and restore mailbox data If you are trying to restore a large amount of data (so that backing up the subclient takes longer than the time allotted for the specified backup window), you should either break up the restore into many smaller restores, or perform an Exchange Server database restore. 1. In the CommCell Browser, right-click the backup set whose data you want to browse, and then click Browse Backup Data. 2. In the dialog box, select the browse options that you want to use. 3. If specifying a browse time, click Advanced to open the Advanced Options window. 4. In the Browse dialog box, use the mailbox/folder tree to open the Exchange 2000 structure. Select the mailboxes, folders, and/or messages that you want to restore. Display further pages of specific folder objects by clicking the Next and Previous (the number of objects specified for Page Size in the Browse dialog box). 5. When you are finished selecting items to restore, click Restore All Selected. 6. Click New Browse to initiate a fresh Browse dialog box. Use new browse option settings, if you want. To search for a particular item(s), see “Finding and Restoring an Exchange 2000 Object” later in this chapter for instructions. 7. The system displays the window. Select the options that you want, and then click OK to continue. 8. When the data is fully restored, the system displays a confirmation message. Click OK to close the message window or click Detail to review information on the restore operation.

Finding and Restoring an Object in Exchange 2000 The Find feature can be used to locate mail messages or other Exchange 2000 objects (for example, contacts). 1. Browse (as described in “Restoring Mailboxes” earlier in this chapter), selecting any browse options desired. 2. From the Browse dialog box, right-click the backup set, and then click Find. You can also start the Find operation from any mailbox or folder. 3. From the Find dialog box, type in your search criteria in the Subject, From, and To fields (and check the box next to that field). 4. For optional features, select the Time Range tab. 5. After you have selected your Find options, click the Find Now button. As the Find operation proceeds, Galaxy displays a searching message at the bottom of the window. Then, any items that match the specified name or pattern are displayed in the lower pane of the Find window. 6. From the Find Results list, right-click the object that you want, then click Restore.

Chapter 4: Advanced Backup and Restore Operations 253

iDataAgent for SQL Server iDataAgent for SQL Server 2000 operates in the same manner as the other iDataAgents, with a few exceptions.

Databases and Subclients Databases and Subclients are similar for iDataAgent for SQL Server in that there is one subclient for each database. Each database contains a default subclient. Because each database contains one subclient, these two levels of the tree are similar. The main differences are in the functionality that is available at the different levels and the configuration options that affect any lower levels. The configuration options can be accessed in the Properties dialog box for each particular level. Installation Defaults

During installation, Galaxy automatically configures the three system databases: master, msdb, and model. During installation, you can also select user-defined databases to be configured. A database icon is created in the CommCell Browser to represent each configured database. Each database contains one subclient named Default. A subclient is also created during installation for each database. The subclient backs up all data associated with each particular SQL Server database that is secured by Galaxy, which is represented by the database icon. This means that, with a minimum of configuration, you can run backups that include all of the data that you want to secure. Through the subclient, the database knows which storage policy to use. There is one database per subclient. You can back up a database to a different library by changing the associated storage policy. This is useful for making backups for off-site storage. The subclient is also where you specify the number of streams to use for backup operations. Tree Levels for iDataAgent for SQL Server

In the CommCell browser tree, there is a node for each client computer and each iDataAgent on each client computer. Under this iDataAgent level is the Instance level. The configuration settings at each level affect all lower levels. This means that configuration settings at the iDataAgent level affect the Instance level, and configuration settings at the Instance level affect all databases below the Instance level. Support for Multiple Instances of SQL Server 2000

SQL Server 2000 supports multiple instances of SQL Server on one client computer. iDataAgent for SQL Server supports configurations with both SQL Server 7.0 and SQL Server 2000 on the same client computer. Multiple instances of SQL Server 2000 on the same client computer (with or without SQL Server 7.0) are also supported.

254 Backup and Restore for Internet Data Center

A SQL Server 7.0 instance is identified by a SQL Server instance icon beneath an iDataAgent icon in the CommCell Browser. Each SQL Server 2000 instance is identified by an instance icon beneath the iDataAgent icon in the CommCell Browser. Figure 4.15 illustrates these icons.

Figure 4.15 Instance icons for iDataAgent for SQL Server

Using Subclients to Establish Parallel Backups

You can back up an entire instance more quickly by scheduling multiple subclients for simultaneous backup so that the backups proceed in parallel and take less time than if the instance client were not divided into separate subclients. However, for the subclient backups to run in parallel, they must be configured to use different storage policies, or the storage policy must be configured to have at least as many data streams as the total required for all subclients to be backed up in parallel. If any of the subclients are configured to use the same storage policy, and that storage policy is not configured for enough data streams, contention for media group resources will result, and the competing subclients will back up one after the other in a serial manner. Archive Pruning Rules for iDataAgent for SQL Server

Galaxy software provides for a data retention period. When data is backed up through a storage-policy copy, it remains valid for some period of time in accordance with the criteria of the associated retention period. After the retention thresholds are exceeded, the data becomes a candidate for pruning by the archive pruning utility. The archive pruning utility is a Galaxy utility that enforces the data retention period for all backed up data in the CommCell. Under your direction (either scheduled or manually initiated), the archive pruning utility compares all data with the related

Chapter 4: Advanced Backup and Restore Operations 255

retention periods. If you do not run the archive pruning utility, retention periods are not enforced and backup data remains valid indefinitely. (Administration of archive-pruning utility is discussed at length in the Galaxy CommCell Media Management Administration Guide.) The pruning of data enables the Galaxy software to automatically recycle the backup media. When all the data on a given backup medium has been pruned, the archive pruning utility, in accordance with its schedule, re-assigns the medium to a scratch pool for later reuse. For SQL Server subclients, the retention period is defined by two parameters: ● The length of time the data is to be retained. ● The number of full backup cycles. (A full backup cycle begins with a full backup and includes all other backups up to, but not including, the next full backup.) Data becomes a candidate for pruning only when both of these thresholds are exceeded for all backups within a full backup cycle. This means that data is pruned only on full backup cycle boundaries and not on an individual backup basis. In the scenarios that follow, F means a full backup, D means a differential backup, L means a transaction-log backup, and P indicates when the archive pruning utility executes. A dashed diagonal line across a backup means that the backup data is removed during archive pruning. F1

L1

F2

L2

P

3/10 3/10 3/11 3/11 3/12

Figure 4.16 Scenario 1

This scenario shows data backed up over two days and two cycles. The archive pruning utility prunes F1 and L1. The F2 and L2 cycle are kept. F1

L1

F2

L2

RL1

P

3/10 3/10 3/11 3/11 3/12 3/13

Figure 4.17 Scenario 2

256 Backup and Restore for Internet Data Center

Suppose you perform a full backup and a transaction-log backup as the first backup cycle, then another full backup and another transaction-log backup as the second backup cycle. Next, you restore to the transaction-log backup that is part of the first backup cycle. At this point, the archive pruning utility still prunes F1 and L1, even though you have restored L1. F1

L1

F2

L2

RL1 L1'/D1

P

3/10 3/10 3/11 3/11 3/12 3/13 3/14

Figure 4.18 Scenario 3

Continuing from Scenario 2, to make the first backup cycle F1 active again so that the archive pruning utility will not prune that data, you need to perform a transaction log or differential backup after the restore operation. In other words, if you want to keep F1 data, perform a transaction log or differential backup before archive pruning. F1

L1

F2

L2

F3

L3

F4

L4

RL2 L2'

P

3/10 3/10 3/11 3/11 3/12 3/13 3/14 3/14 3/15 3/15 3/15

Figure 4.19 Scenario 4

In this scenario, there are four backup cycles. When you restore to L2 and then perform a transaction-log backup, the F2 cycle becomes the current cycle. The archive pruning utility prunes the F1, F3, and F4 cycles only. If you want to keep the F4 cycle you need to define the retention period for a minimum of two cycles.

Chapter 4: Advanced Backup and Restore Operations 257

F1

L1

F2

L2

RL1

F3

3/10 3/10 3/11 3/11 3/12 3/13

Figure 4.20 Scenario 5

If a full backup is performed after restoring to a previous backup cycle, the new full backup becomes the current backup cycle and earlier backup cycles are pruned. An additional scenario 6 would be if a database is deleted from Galaxy. The next time the archive pruning utility executes, existing backup sets are pruned regardless of their retention periods.

Browse and Restore Operations The Galaxy system provides two operations to retrieve backed up databases: browse and restore. Browse can be performed at the client computer, iDataAgent, and instance levels. Restores can be performed from the instance or database levels. Browsing and restoring from the instance level, and browsing from the application level, allow you to browse and restore all databases within a single SQL Server instance which have been backed up at the same time. Browsing Data

A browse operation provides a list of databases that have been backed up at a specified browse time. You can use this display to select some or all of the databases and restore them using a restore operation. When restoring databases you control two main parameters: ● Browse time interval ● Restore type Controlling the Browse Time Interval

The browse operation provides you with the ability to browse the latest backup data or specify a particular time to include in the browse. The Browse the Latest Backup Data option is selected by default. This option returns a list of databases that have been backed up prior to the time that the browse command was issued. You can specify the browse time span by selecting a time in the Browse To dialog box. The list of databases returned in the Browse dialog box includes all databases that were backed up prior to the selected Browse To time. The Browse From option is also available. However, in this context it does not offer any functionality.

258 Backup and Restore for Internet Data Center Restoring Data

The restore operation retrieves the data that you select in the Browse dialog box. Galaxy offers a variety of restore options, and does not require that you first browse the data. You can right-click the database or SQL Server instance that you want to restore, choose Restore and perform the restore operation directly. Restoring the Master and msdb Databases

When restoring the master database, the SQL Server service must be stopped and restarted in single-user mode. Galaxy informs you of this and gives you the option to continue (that is, stop and restart the SQL Server service at this point) or to cancel the restore operation. If you continue the restore operation, Galaxy stops and restarts the SQL Server service in single-user mode as part of the restore operation. When restoring the msdb database on an SQL Server, Galaxy displays a message stating that the SQLAgent service cannot be running during the restore. To shut down the SQLAgent and continue, click Yes. To abort the operation, click Cancel. To continue the operation without shutting down the SQLAgent service, click No. If you click No and the SQLAgent service is running, the job fails; if it is not running, the job continues normally. In a clustered environment, the SQLAgent service should be stopped from the Cluster Administrator dialog box. Cross-Client Restore Operations

By default, Galaxy restores data to the client computer from which it originated. You can also restore databases to another SQL Server computer that has the SQL Server iDataAgent installed. This is called a cross-client restore. Changing the SQL Server listed in the SQL Database Restore Options dialog box initiates a cross-client restore. Hot Server Restore

Galaxy allows you to perform hot server restores on any secured database in the SQL Server. This functionality enables you to easily maintain a hot server spare of one or more databases in the event of a server failure of the main SQL Server computer. You can also schedule hot server restores so that they automatically occur at a specified interval. Matching a hot server restore schedule with a backup schedule on the source database keeps your hot-server databases up-to-date automatically. See online Help for a full description of Hot Server Restore. Scheduled Restore Operations

When you want to restore data, you usually need it immediately. However, there may be times when you need the data by some specific time, but not necessarily right away. Using the scheduling feature, you can schedule a restore operation. As with scheduled backups, a scheduled restore operation relieves you of having to manually initiate the operation. This feature can be particularly useful if you want

Chapter 4: Advanced Backup and Restore Operations 259

to restore a large amount of data, but would prefer to do so at a time when either the client computer is not in use or at a time when network utilization is low (assuming the data must traverse a network). Understanding Restore Options

While browse and restore operations often go hand in hand, a restore can be performed on demand. The previous section discussed the Browse dialog box and the available browse options. This section discusses the available restore options. A restore operation recovers the data that you want and restores it to the desired location. The Galaxy system offers a variety of restore options that allow you to control how the data is restored. Note: Do not attempt to perform backup or restore operations on the master or CommServe databases on the Galaxy CommServe computer. Galaxy Services depend on SQL Server services and will not function if SQL Server is shut down.

The options available on the SQL Database Restore Option dialog box differ slightly depending on whether the restore operation is for a single database or multiple databases. Multiple database restore options also apply when restoring the entire instance. SQL Server does not allow restores on databases that are in use. Before you attempt a restore operation, make sure that all the databases that you want to restore are not in use. When you restore the msdb database, the SQLAgent service must be stopped. Galaxy displays a confirmation message when you attempt to restore one or both of these databases. Click OK to stop the service and continue the restore or Cancel to abort the operation.


To browse and restore data 1. In the CommCell Browser, right-click the SQL Server instance whose data you want to browse, and click Browse SQL Server. 2. In the Browse Options dialog box, select the browse options that you want to use. 3. If specifying a browse time, click Advanced. 4. From the Browse/Restore dialog box, select the databases that you want to restore, and click Restore All Selected. Note: If the master database or all available databases in the browse window are selected, then when you click Restore All Selected, Galaxy displays a message stating that the master database has been selected for restore and that the SQL Server will be shut down and restarted in single-user mode. Click Yes if you want to continue with the restore, or No to cancel without shutting down the server.

260 Backup and Restore for Internet Data Center 5. In the Restore Options dialog box, select the restore options that you want. If

you want to restore the database to another SQL Server, select the server in the SQL Server drop-down menu. 6. Click Advanced if you want to copy or move a database. 7. When the data is restored, click OK on the confirmation window. You can click Detail to review information on the restore operation. It is highly recommended that you perform a full backup after a point-in-time or discreet restore, or after restoring from an auxiliary copy.


To restore a database without browsing You can restore a database or instance without browsing first. This procedure is most appropriate when you want to restore to the latest backup version. 1. In the CommCell Browser, right-click the database that contains the database that you want to restore, and then click Restore Database. 2. In the Restore Options dialog box, select the restore options that you want to use. 3. On the Restore Time menu, select the backup that you want to restore. Galaxy automatically restores all necessary backups based on your choice of Restore Time. 4. If you want to select any additional restore options, click Advanced and select the options you want from the dialog box. 5. After you have selected the restore options, click OK. The system displays the progress bar and starts to restore the data.




To restore a SQL Server instance without browsing 1. In the CommCell Browser, right-click the instance, and then click Restore SQL Server. 2. In the Restore Options dialog box, select the restore options that you want to use. 3. If you want to select any additional restore options, click Advanced and select the options you want from the dialog box. 4. After you have selected the restore options, click OK. The system displays the progress bar and starts to restore the data.

Managing Disaster Recovery Here you can read about various options for restoring the full system, including: ● Recovering a Windows 2000-based computer ● Recovering a server running Exchange Server ● Recovering a server running SQL Server

Chapter 4: Advanced Backup and Restore Operations 261

In the case that you have to recover from a total enterprise disaster, please read the following information. For steps in recovering a server running Windows 2000, begin with “Full System Restore Procedures.”

Total Disaster Recovery Overview In the case of a total enterprise disaster, the order in which you complete the restore is important. In general, the proper order is as follows: 1. Deploy the CommServe and MediaAgent server(s). 2. Recover the CommServe and MediaAgent by following procedures for recovering a CommServe/MediaAgent in the CommServe Administration Guide. Because the domain controllers will not be functioning before the restore, the enterprise computers that are not domain controllers will fail to join the domain, and will instead automatically default to a workgroup member. For this reason, the domain controllers must be deployed and restored before the remaining enterprise computers are deployed, as follows: 1. Deploy the domain controllers. The domain controller(s) are built using the Galaxy Disaster Recovery Phase. This builds the domain controller computers as Workgroup members, in preparation to be restored and recovered as fully functional domain controller(s) from the backup. 2. Restore the domain controllers. 3. Deploy the remaining enterprise computers (which can now join the domain). 4. Restore the enterprise.

Total Disaster Recovery Steps First recover the CommServe, using the procedures outlined in “Recovering a CommServe” in this chapter and in “CommServe Recovery Procedures,” found in Appendix A of the Galaxy CommServe Administration Guide. The procedures include those for recovering the MediaAgent. After the CommServe and MediaAgent are restored, you are ready to deploy and restore all Galaxy clients in the enterprise in the following order: 1. The domain controllers (Active Directory and DNS) need to be recovered first, to establish proper connectivity throughout the enterprise: ● Because there is no naming resolution until the domain controller is restored, the domain controllers name must be added to the CommServe and MediaAgent host files. The names of the CommServe and MediaAgent must also be added to this domain controller’s host file. The entry should match what will be restored in DNS: IP address, fully qualified domain name (FQDN, short name. These entries will be overwritten after a full system restore is performed on each computer.

262 Backup and Restore for Internet Data Center ●

●

In the Windows Full iDataAgent Restore Options dialog box, select Primary to recover the first domain controller. All other full restores of iDataAgent for Windows in the enterprise can be recovered by accepting the default selections. Domain controllers are installed as Workgroup members to avoid security ID (SID) conflicts. Galaxy will restore this FQDN to the domain controller, but will have its own naming resolution conflict if the name changes from Short to FQDN during the restore. Therefore, the FQDN must be added to the computer properties before the restore is implemented.

2. The SQL Cluster and SQL Servers need to be recovered next, so that their depen-

dent servers will start: ● Deploy the cluster nodes and follow Internet Data Center guidance to configure the EMC storage and install clustering. ● Review the steps in “Restoring a Cluster Server Node.” 3. Deploy and restore the remaining computers in the enterprise. If there are other

servers that have other servers dependent on them, such as Microsoft Commerce Server 2000 or Microsoft SQL Analysis servers, they should be restored next. For example, if a retail site is to be restored, the SQL Server cluster databases have to be available before the Commerce Server can start, and Commerce Server usually has Microsoft SQL Analysis server running on it as well; both these services need to be restored and running before for Web servers can be restored. The number of clients to be restored after the foundation has been recovered depends on the number of drives available in the tape library. Because restores are cannot be interrupted, you can invoke the remaining full iDataAgent restores for the enterprise at that time. The jobs will be queued until a drive is available.

Recovering a Computer Running Windows 2000 Here you can read about the various procedures used to restore a computer running Windows 2000, including the steps required for particular server roles, such as domain controller and Web server.

Recovering iDataAgent for Windows 2000 A full iDataAgent restore operation includes a full restoration of a Galaxy client’s file system and system state. Full iDataAgent restores can be helpful or even necessary, depending on circumstances. The following are some examples: ● Creating a computer that duplicates the data and configuration from another computer ● Re-establishing a computer’s data and configuration after a catastrophic system failure

Chapter 4: Advanced Backup and Restore Operations 263

The difference between a full iDataAgent restore and a typical restore is in the type of data that is to be restored. A full iDataAgent restore recovers not only regular data files and directories to their original paths, but also the system state (if required). The file system and system state can be restored at the same time without an intervening restart. By default during full iDataAgent restores of file system data, the Galaxy system restores all data by unconditionally overwriting the corresponding files to the system being established. Galaxy also provides several options for replicating the restored data across the domain. The system-state restore allows the hardware on the target to take precedence over the hardware settings that were backed up, so it is important that hardware devices are properly configured on the target prior to restoring. What Should Be Restored

As part of the full iDataAgent restore, you can restore any or all of the following: ● File system ● System state ● System databases File System Restores

Files and directories are restored in-place; however, if any files are locked at the time of restore, the Galaxy system automatically writes each locked file to another file name within the same directory and records the instance in the Windows 2000 registry. When a full iDataAgent restore is performed, the system will restart once to restore the registry and overwrite the locked files. System State Restores

The system state consists of components that are backed up as a unit and can be restored individually or as a unit. The system state is automatically backed up with the default subclient, which should be backed up frequently. The procedures for restoring system state differ, depending on whether you are restoring to a domain controller or to a non-domain controller. If you are restoring on a domain controller, the domain controller must be started in the directory services restore mode, in order to restore certain database objects, such as Active Directory. During a system-state restore on a non-domain controller, no databases need to be offline. Therefore, there is no need to start in a special mode when performing a system state restore on a non-domain controller.

264 Backup and Restore for Internet Data Center System Database Restores

The system databases are backed up with the system-state backup on the default subclient. These databases can be restored as part of the full iDataAgent restore. It is possible to restore a specific system database; however, the services associated with the restored database must be installed and functional. Domain Controller Restore Types

Domain controllers communicate with each other across the network and replicate data and network information. This replication takes place automatically, according to the schedule you established during Windows installation. When restoring the system state to a domain controller, Galaxy allows you to decide how you want the restored data to be replicated across the domain. The restore types are non-authoritative, authoritative, and primary. When Active Directory or System Volume (SYSVOL) is restored to a domain controller, by default it is restored in a non-authoritative mode. Newer data on the network is then propagated to the restored computer, updating it with any newer information. When the restored data is meant to override the data on other domain controllers, it should be restored using the authoritative mode. After this data is restored to the domain controller, it is propagated to the other domain controllers and overwrites any newer data on those computers. The authoritative mode is used if critical SYSVOL or Active Directory data has been deleted and the deletion has been propagated throughout the domain. Note: Authoritative restores must be performed with caution, as the system state will be rolled back to the point of the backup, possibly resulting in a loss of data that cannot be restored after it is overwritten.

A primary restore marks the restored data as the primary data for all of the replicas within the domain. This creates a new File Replication service (FRS) database, and pushes the replicated SYSVOL data to any domain controllers that are added to the replication system. Note: A primary restore should be used only when all other domain controllers are nonfunctional and you want to rebuild the domain from the last backup. Do not perform a primary restore if any other working domain controller from this domain is available.

Restore Options for System State Data System state restore operations restore several objects, including SYSVOL and Active Directory. Here you can read about the options available for restoring these system state objects.

Chapter 4: Advanced Backup and Restore Operations 265

SYSVOL Restores

The SYSVOL restore type may be chosen directly in the Full iDataAgent Restore Options dialog box. The following restore types are supported for SYSVOL: ● Authoritative ● Non-authoritative ● Primary The chosen restore type for SYSVOL applies only to the SYSVOL restore operation, and will not effect the restore operations of other domain controller components. For example, if you choose authoritative restore for SYSVOL, Active Directory is restored non-authoritatively by default. Active Directory Restores

Galaxy performs a non-authoritative restore of Active Directory by default. To force an authoritative restore, run the NTDS utility (ntdsutil) after running a Galaxy full iDataAgent restore. Cluster Database Restores

The cluster services and quorum databases are restored with the system state restore of the physical node owning the quorum databases. Program files are restored with the file system. Restoring both the system state and the file system will restore the files on the physical node, and the cluster databases to a temporary directory. In order to complete the restore of the cluster databases, enter the following: authorutil –cluster. For more information about cluster database restores, see “Restoring the Cluster Server” later in this chapter. Specific Boot Modes

When you restore the SYSVOL, Active Directory, and system databases on a domain controller, you must restart the computer in the directory services restore mode. Restart the computer and press F8 upon system startup, then select Directory Services Restore Mode. You may also restore file system data on a domain controller that is in the Directory Services Restore mode. The restore process will restore the system state data and the file system data in one restore operation. When complete, the computer must be restarted into the normal operation mode. If the computer is not a domain controller, it is not necessary to restart it in the Directory Services Restore mode, because there is no Active Directory present. You can fully restore all components with one operation.

266 Backup and Restore for Internet Data Center

Performing Full iDataAgent Restore Operations Table 4.21 provides a broad overview of the components and information required to fully restore your Windows 2000-based computer. During the system rebuild, you will be prompted for system information, depending upon the system setup. Because the computer will be down during the operating system rebuild, you may not be able to access necessary information about the system. It is important to record such information before a disaster occurs. Table 4.21: Installation components for system rebuilding Component

Description

Software

Windows 2000 installation discs, compact disc, and required service packs iDataAgent for Windows 2000.

Drives

Use the Disk Management utility to record the volumes and sizes of the hard drives in the system. This information is needed to recreate the disk configuration in case of hard drive failure. Hard drives must be configured before system state or file system data is restored.

Computer name

Use the same computer name and avoid changing other configuration settings.

TCP/IP

Record the fully qualified network name and IP address if the computer uses a static IP address. Subnet mask for your network IP address of the network router used by the client computer TCP/IP domain name for the network (for example, ad01.nwtraders.com) IP address of the DNS server

Video settings

Record the video settings if the resolution and color depth are important.

Domain information

Record the domain this computer resides in, and set up a new computer account when ready.

Local administrator password

Record this information or you will not be able to log on to the computer after it is restored.

Galaxy Install Directory

Record the directory in which Galaxy was installed.

The restore process is performed at the backup set level. If the client computer has two or more backup sets, be prepared to identify the backup set whose data you want restored during the restore process. (In general, all backup sets of a given client computer encompass the entire file system; however, backup filters, which can be unique, can introduce differences.)

Chapter 4: Advanced Backup and Restore Operations 267

Full System Restore Procedures

If the operating system of your Windows 2000-based client has been corrupted, follow this procedure manually or use deployment scripts to restore the full system.


Rebuilding the operating system 1. If required, rebuild the system hardware. 2. Install the Windows 2000 operating system. Windows 2000 must be installed in the same directory as that of the original computer. Be sure to enter the correct time and select the proper time zone. You should leave the server in a workgroup and not include it in the domain. 3. Install required Service Packs. For Service Pack requirements, see the iDataAgent for Windows 2000 release notes. 4. Configure hardware devices, such as disk arrays, and confirm connectivity to all drives. 5. Confirm connectivity to and from the CommServe, MediaAgent, and Galaxy client to be restored (using forward and reverse DNS lookup or ping). All computers should have successful TCP/IP connections to the CommServe. 6. If DNS is not available, add all computer names to the CommServe’s host file; address FQDN shortname or alias, for example, 192.168.123.123 ad01.nwtraders.com ad01. Web Tier servers should bind the back-end network interface card first. 7. Web tier servers, CommServe, and MediaAgents should be enabled for Galaxy to allow traffic through the firewall; that is, the Galaxy firewall configuration files must be properly set up. 8. Cluster servers should bind the public network interface card before the private network interface card. 9. Cluster servers should have the Microsoft Hotfix (pre-Service Pack 3) 19425 gethostbyaddress applied to all nodes. Please contact Microsoft Product Support Services to obtain this patch. 10. Cluster Servers should have all disk-array devices configured with access to the shared array, and cluster software should be installed and running. 11. iDataAgent for Windows 2000 should be installed to all Galaxy clients in the enterprise. The client name and interface names should be installed using the same information provided during the initial installation to the CommServe. It is only necessary to install iDataAgent for Windows 2000 to the computer. After the file system is restored, additional iDataAgents, such as iDataAgent for SQL Server, will be restored to the target from the backup data and accessible by the CommServe. For details on installing the iDataAgent for Windows 2000, see Chapter 2, “Backup and Restore Deployment.”

268 Backup and Restore for Internet Data Center 12. Apply Galaxy patches. Domain controllers need Galaxy 3.1 GSP1 patches 4, 11,

and 23. To install iDataAgent for SQL Server, use Galaxy 3.1 GSP1 patch 28. 13. Shut down and restart the Windows 2000-based computer so that the changes take effect. 14. After the installation is complete, open the CommCell Console. 15. Ensure that backup jobs are disabled for the client computer that you intend to restore. This prevents any backups that may have been previously scheduled for the client computer from starting while the restore is in progress. Restoring a Domain Controller

Before you begin: ● Make sure that you have completed all the steps listed in “Rebuilding the operating system” before continuing. ● Make sure the correct FQDN has been configured for the computer that will be restored as a domain controller. ● If you are rebuilding a DNS server, add the CommServe, MediaAgent and CommClient names and IP addresses to the host file of the client and CommServe for name resolution until the DNS server is restored. ● Enable and configure TCP/IP support. Configure the network interface card(s) for connectivity to the CommServe. ● Implement Compaq teaming, if the computer was backed up in a teamed configuration. ● Apply Galaxy 3.1 GSP1 patches 4, 11, and 23 (required for domain controllers). Note: For domain controllers, Galaxy 3.1 GSP1 requires that patches 4, 11, and 23 be applied. You may receive an error message during patch installation that states that the client was unable to communicate with the CommServe. This error may occur if the path to the Galaxy installation directory has not been applied to the environment. You can correct the error by applying the path to the environment (MyComputer\Properties\Advanced\Environment variables\System Path) and restarting the Galaxy Services. Or you can ignore the error and continue with the patch installation. The patch will still apply to the client computer. This is a Galaxy 3.1 GSP1-specific issue and has been corrected.


To restore a domain controller 1. To restore the system state data, the domain controller must be in the Directory Services Restore mode. file system data and System databases can also be selected during this operation. To do this, follow these steps: a. Restart the computer. b. As it restarts, the following message appears: “For troubleshooting and advanced startup options for Windows 2000, press F8.”

Chapter 4: Advanced Backup and Restore Operations 269

c. Press F8. Then select Directory Services Restore Mode.

2. 3. 4. 5.

6. 7. 8.

The system will start in the Directory Services Restore mode and display “Safe Mode” on all four corners of the screen. From the backup server, start the CommCell Browser. Expand Client Computers. You will see a list of client computers. Select the client that will be restored and expand it. A list of installed iDataAgents on the client computer will be listed. Expand the File System iDataAgent tree. A list of backup sets will be displayed if the client was configured with more than one backup set. There will be at least one—the default backup set called defaultbackupset. Select and right-click the backup set that contains the data that you want to be restored. From the menu, click Full iDataAgent Restore. The system prompts you to confirm the selection. Click OK to continue. In the Full iDataAgent Restore Options dialog box, make selections based on whether you are restoring a stand-alone domain controller or a non-stand-alone domain controller. ● Click Exclude Files/Folders and add the SYSVOL path. The system state will restore the SYSVOL. Filter this directory from the restore. Filtering will prevent the file system from additionally restoring the SYSVOL. (Computers deployed using MSA scripting default to C:\Ad\Sysvol. The standard default location is C:\WINNT\Sysvol). ● In the dialog box, select primary for a stand-alone domain controller or the first domain controller being restored to the enterprise. ● For a networked domain controller or if this is not the first domain controller being restored to the enterprise, select the SYSVOL restore option that you want to apply. ● To render the domain controller operational again without replicating any changes to the other domain controllers on the network, in the SYSVOL field set the Restore option to Non-Authoritative. ● To render the domain controller operational again and replicate the restored data to the other domain controllers on the network, set the Restore option for SYSVOL field to Authoritative and complete the restore by running the NTDS restore utility (ntdsutil) from the command prompt after the restore completes.

9. Click OK to start the restore process. As the restore proceeds, the system displays

a restore progress bar. It may take several minutes before you see the progress bar. 10. You will be notified that the restore has been completed successfully. Click OK.

270 Backup and Restore for Internet Data Center 11. You will be prompted to restart the computer.

a. If you are performing a primary or a non-authoritative restore, click OK and restart in normal mode. b. If you are performing an authoritative restore of the SYSVOL and Active Directory, click OK, but restart the computer in Directory Services Restore Mode to continue with the Authoritative Restore procedures. Restore the Active Directory using an Authoritative Restore: a. Click Start, point to Programs, click Accessories, and then click Command Prompt. b. At the command prompt, type ntdsutil. c. At the ntdsutil prompt, type Authoritative Restore. d. At the Authoritative Restore prompt, type Restore Database. e. Click Yes to restore the database. f. When done, exit the Authoritative Restore prompt by typing quit and then end the ntdsutil session by typing quit again. Exit the command prompt by typing exit. g. Restart the computer and allow time for replication to complete. h. To restore the SYSVOL Authoritatively, manually copy the data from the \WINNT\Temp directory to the existing SYSVOL directory (shown in the following example as \WINNT\SYSVOL). (This will move the restored SYSVOL information from the \WINNT\Temp directory to the existing SYSVOL directory). Copy \WINNT\Temp\Sysvol\Domain Scripts to \WINNT\SYSVOL\Sysvol\Domain\Scripts and \WINNT\Temp\Sysvol\Domain\Policies to \WINNT\SYSVOL\Sysvol\Domain\Policies 12. If Microsoft Certificate Services is installed, ensure that Certificate Services is

back online after the previous restart step. Certificate Services will not accept any certificate requests until it completes its restore functions. Restoring a Non-Domain Controller or Member Server

If you are restoring a non-domain controller, follow this procedure. Make sure that you have completed all of the steps in “Rebuilding the operating system” prior to continuing. If restoring more than one computer, review “Total Disaster Recovery Steps,” earlier in this chapter, and evaluate any dependencies that might affect the order of the computer restore operations. If you are restoring a cluster server or cluster node, review the cluster information later in this chapter.

Chapter 4: Advanced Backup and Restore Operations 271




To restore a non-domain controller or member server 1. Start the CommCell Browser. 2. Expand Client Computers. You will see a list of client computers. 3. Select the client that will be restored and expand it. A list of installed iDataAgents on the client computer will be listed. 4. Expand the File System iDataAgent. A list of backup sets will be displayed if the client was configured with more than one backup set. There will be at least one— the default backup set called defaultbackupset. 5. Select and right-click the backup set that contains the data that you want to be restored. On the menu, click Full iDataAgent Restore. 6. The system prompts you to confirm the selection. Click OK to continue. 7. In the Full iDataAgent Restore Options dialog box, select the restore options that you wish to apply. 8. Clear the System State option. 9. Click OK to start the restore process. As the restore proceeds, the system displays a restore progress bar. 10. You will be notified that the restore has been completed successfully. Click OK. 11. You will be prompted to restart the computer. Click Cancel. Do not restart the computer. 12. Repeat Steps 5-9, this time selecting the System State option. Clear all other defaults. 13. Click OK to start the restore process. As the restore proceeds, the system displays a restore progress bar. 14. You will be notified that the “Windows 2000 file system restore for client name completed partially”. This indicates success for this stage of the restore. Click OK. 15. The following message appears: “To perform an authoritative restore of Active Directory, please run ntdsutil. To complete the authoritative restore of sysvol, please copy over the contents of sysvol from the temporary restore directory.” Click OK. This message is informational and only relevant when you are performing an authoritative restore of a domain controller. If the computer being restored is part of a cluster, the message above will include, “To complete the restored cluster database, please run clustrest.”. Ignore this message and review the cluster information later in this chapter. 16. You will be prompted to restart the computer. Click OK to do so. After a full iDataAgent restore, the SID for Windows 2000 for the rebuilt system may not match the corresponding SID on the primary domain controller. To resolve this conflict, remove the system from the Windows 2000 domain by logging in locally, and joining a workgroup. Then add the rebuilt system back into the Windows 2000 domain by joining the domain.

272 Backup and Restore for Internet Data Center

A full iDataAgent restore operation restores only certificates issued before the last backup. You can leave the remaining certificates orphaned, or you can revoke and reissue them. Restoring Commerce Server

Preliminary information is available in “Restoring a Non-Domain Controller or Member Server.” Servers with SQL Server will also need a SQL Server database restore as described in “Recovering SQL Server,” later in this chapter. You should stop the Commerce Server 2000 services when you restore the server running SQL Server and Commerce Server 2000. Restoring Application Center

Preliminary information is available in “Restoring a Non-Domain Controller or Member Server” earlier in this chapter. Before you restore a member server, evict the node from the cluster. Re-join the cluster after the restore has been completed. Restoring Internet Information Services

Preliminary information is available in “Restoring a Non-Domain Controller or Member Server” earlier in this chapter. Restoring the Cluster Server

Before you begin, make sure that you have completed all the steps in “Rebuilding the operating system.” In the case of a total loss of the cluster, the following process is most efficient. It includes a SQL Server restore as described in “Recovering SQL Server.” later in this chapter. The cluster service and SQL Server service must be running before you restore SQL Server.


To restore the cluster server 1. Install the Windows 2000 operating system software on both physical nodes. 2. Install the Microsoft (pre-Service Pack 3) WINSE19425 patch. 3. Shut down node2. 4. On node1, configure the EMC drives, and change drive letters and Emulex settings (For more information, see the Internet Data Center documentation on TechNet). When prompted to re-start your computer, click Yes. 5. After the computer restarts, new hardware will be discovered, and you will be prompted to restart the computer again. Click No. Join the domain, restart the computer, and then log on to the domain.

Chapter 4: Advanced Backup and Restore Operations 273

6. Install cluster software on node1 as the first node in the cluster, but do not restart 7. 8.

9.

10. 11. 12. 13.

14.

15.

16.

17. 18.

the computer. After the cluster software is installed, shut down node1. Power on node2. On node2, configure the EMC drives, and change drive letters and Emulex settings (For more information, see the Internet Data Center documentation on TechNet). When prompted to re-start your computer, click Yes. After the computer restarts, new hardware will be discovered, and you will be prompted to restart the computer again. Click No. Join the domain but do not restart the computer. Shut down node2. Turn on node1 and log on to the domain. Turn on node2 and log on to the domain. Install cluster software on node2 as a secondary node to the cluster. Using Cluster Administrator, configure the disk groups. (For more information, see the Internet Data Center documentation on TechNet.) The Cluster Group should own the quorum disk. Set the disk group properties to allow failback. Install SQL Server 2000 and Service Pack 1 to both SQL Server 2000 instances. The server and instance name should be the same as they were when there were installed previously. If this is not recorded anywhere, use the CommCell Browser and browse the computer you need to restore. The SQL instance name is listed under the SQL iDataAgent in the CommCell console. You can see the location of the data and log file directories by browsing iDataAgent for Windows 2000. Install Galaxy to the same location where it was previously installed. Install iDataAgent for Windows 2000 on both SQL Server physical nodes. Then, install iDataAgent for Windows 2000 on the virtual servers. During the installation on a virtual server, type the full path, including drive letter, for the Galaxy installation in the folder window. If this is not recorded anywhere, use the CommCell Browser and browse the virtual server that you need to restore. You can see the location of the previous Galaxy installation directory by browsing the iDataAgent for Windows 2000. Install iDataAgent for SQL Server using Patch 28 to the virtual servers. The iDataAgent’s for each virtual server must be installed from node that currently owns the virtual server resources. Restore the server running SQL Server to both virtual servers by following instructions in “Restoring SQL Server,” later in this chapter. Restore any desired non-database files to the virtual servers.

This completes the recovery of the SQL Server cluster.

274 Backup and Restore for Internet Data Center Restoring a Cluster Server Node

If the cluster server is functioning in a fail-over mode, and one cluster node is functioning and the other is not, you can recover the failed node by following instructions described in “Restoring a Non-Domain Controller or Member Server.” The cluster service must be running on the node that you are recovering prior to the restore operation. 1. When you restore a single cluster node, you must evict the node from cluster administrator before rebuilding the node. From the cluster administrator, highlight the node that has failed, right-click it, and select evict node. 2. Rebuild the operating system. Make sure that you have completed all the steps in “Rebuilding the operating system” prior to continuing. 3. Configure TCP/IP for private and public network interface cards. 4. Confirm that the public network interface card binds before the private network interface card. 5. Join the computer to the domain, but do not restart yet. 6. From Device Manager, configure the EMC drives, change drive letters and Emulex settings. For more information, see the Internet Data Center documentation on TechNet. 7. Restart the computer in safe mode by pressing F8 during restart. Apply the Microsoft (pre-Service Pack 3) WINSW 19425 patch and then restart the computer in normal mode. 8. Install Microsoft cluster software and configure as secondary node. 9. Install iDataAgent for Windows 2000 on the physical node. 10. Perform a Full System iDataAgent restore of a non-domain controller. For details, see “Restoring a Non-Domain Controller or Member Server,” earlier in this chapter. 11. Confirm that each Microsoft resource in cluster administrator has both nodes listed as available nodes on the general properties tab. When a cluster node is evicted, the evicted node gets removed from each Microsoft cluster resource as an available node. In the cluster administrator, double-click each Microsoft cluster resource to view the general properties tab. If all nodes are not listed as possible owners, click Modify and move the node from the left pane (“available”) to the right pane (“possible”) and then click OK. In order for a group to fail over to a desired node, every resource within the group must list that node as a possible owner. 12. Confirm failover and failback capability.

Chapter 4: Advanced Backup and Restore Operations 275

Restoring the Cluster Databases

Cluster databases should be restored only if the existing databases are corrupt or missing cluster resource information that can be retrieved from the backup data. The cluster services and quorum databases are restored with the system state. The program files are restored with the file system. Restoring both the system state and the file system will restore the cluster information. However, the quorum databases are always restored in authoritative mode and require a manual, non-authoritative restore process. A system state restore will place the quorum (drive) databases in a temporary location, \WINNT\Temp. If the quorum disk was lost or corrupted, the data can be restored using the authoritative restore utility (authorutil). The cluster services must be online during the authoritative restore. If the existing quorum data is corrupt, the cluster services will not start. You will need to uninstall and re-install the cluster service before running authorutil – cluster (or install the cluster service prior to the restore operation).


To restore the cluster databases 1. From the command prompt of the node that owns the quorum database, type: authorutil –cluster 2. Stop the cluster service on all nodes, except the one that is performing the restore. You should perform the restore on the node that owns the cluster group/ quorum database during backup operations. (If you do not follow this process, and another node with a more current database takes ownership of the quorum before you update the database from the restored node, the restore will not work.) 3. A successful restoration will prompt you to restart the services on the paused nodes. 4. After you complete the process and the Cluster service has started successfully on the newly restored node, restart the other nodes. If clusdb was not restored, perform the procedure described in the following Microsoft Knowledge Base article: Q224999, “How to Use the Cluster TMP File to Replace a Damaged Clusdb File.” You can use cluster service commands to troubleshoot or debug the cluster service from the command prompt. The cluster service command line can only be run locally from the cluster directory: systemroot\cluster The clussvc command should not be used under typical conditions; rather, it should be used only as a temporary diagnostic tool if the cluster service fails to start (for example, after a system-related error).

276 Backup and Restore for Internet Data Center

The following rules apply when entering commands from the command prompt: ● When entering commands from the command prompt, you can specify multiple options for one command line. Clussvc.exe processes options from left to right. If an option fails, the command stops running at the failed option. ● To use the cluster service commands, you must be logged on with administrative rights. ● To stop the cluster service, press CTRL+C at the command prompt. The command line for starting the cluster service has the following syntax: clussvc -debug [command] where command is: fixquorum

This allows the cluster service to start up, even if there are problems with the quorum device. resetquorumlog

Creates a new quorum log file if the quorum log file is not found or is corrupted; it is based on information in the local node’s cluster database file. If the quorum log file is found and is not corrupted, this command has no effect. The cluster service runs in the command prompt window and displays all output recorded in the cluster log in the window. Other Restore Scenarios

The full iDataAgent restore function can also be used in the following disaster recovery situations. When restoring to a rebuilt or new system: ● Make sure the target computer is as similar to the original as possible. ● Make sure the target computer has the same fully qualified network name as the original. ● Try to match the general hardware configuration (that is, IDE, SCSI) of the original computer. ● Match the local disk drive configuration as closely as possible to that of the client being restored. ● Make sure the computer’s disk(s) can accommodate the quantity of data being restored. ● If possible, use the same network interface card (NIC) as that of the client being restored.

Chapter 4: Advanced Backup and Restore Operations 277

If you are performing a full iDataAgent restore to a computer with a different hardware configuration (for example, network interface card, video card) from the backed up client, perform the following procedure.


To perform a full iDataAgent restore to a computer with a different hardware configuration from the backed up client 1. Perform the full iDataAgent restore as described in this chapter with the unconditional overwrite option cleared. 2. Check the TCP/IP and video configuration. If they are incorrect, perform the following steps. a. Re-install the appropriate network interface card drivers. b. Uninstall the Network Adapters and Display Adapters (using the Hardware Uninstall Wizard or Windows Device Manager). c. Restart the computer when prompted. d. Your hardware should be re-discovered by Windows and the appropriate drivers restored. 3. Reconfigure your TCP/IP and Display Adapter settings.

Windows 2000 supports basic and dynamic hard drives. When you perform a full iDataAgent restore, the target hard drive should be configured as a dynamic hard drive if the backed up drive was a dynamic hard drive. Note: If the drive type does not match during a restore, the rebuilt drive will be marked as foreign and the restored data will be inaccessible. If this happens, the drive must be converted from foreign, to basic and then to dynamic, using Windows 2000 disk management tools. The restore should then be run again.

For a full iDataAgent rebuild of a domain controller, the Galaxy installation directory must be on the same drive on the target computer as it is on the backup data. In addition, it is strongly recommended that the directory be in the same location on the target as on the backup. Whenever you restore NTDS and SYSVOL, the data is moved into a temporary directory. The temporary path uses the Galaxy install directory path from the backup data and tries to put the data in the same place on the target. If you are going to restore a domain controller, and if the location of the Galaxy install directory on the target is different from its location on the backup, rename the following data path before you restart: D:\GalaxyNew\iDataAgent\FileSystemAgent\2\2\RESTORE\GALAXY\iDataAgent \FileSystemAgent\2

278 Backup and Restore for Internet Data Center

The first part of the path starting with GalaxyNew is the current Galaxy installation on the target; the second part of the path starting with GALAXY is the Galaxy installation on the backup. Before you restart, change the second path to match the first path. This will allow the necessary restored data in the temporary directory to get moved to the new Galaxy installation directory on the target. Full iDataAgent Restore Options Window

As part of the full system restore, you must select which options you want to be in the options window for the full-system restore. The following tables describe the options available from this window. Table 4.22: Restore Time options Option

Description

Restore from the Latest Backup

Restores the client computer using the most recent backup data.

Restore from a Backup That Occurred Before This Date

Allows you to restore the client computer using a backup from a specified date and time. This option allows a file system restore with the corresponding options described in the next table.

Chapter 4: Advanced Backup and Restore Operations 279

Table 4.23: File System Restore options Option

Description

File System

This option includes file system data in this restore with the corresponding options described in this table. Note: If you are restoring to a domain controller and have started in the Directory Services Restore Mode, you may also restore the file system data at this point.

Restore Deleted Files/ Folders (no-image)

If this option is cleared: Galaxy restores the computer by using the image of the data as it existed as of the specified backup time. If this option is selected: Galaxy restores the client computer with all the data that was ever backed up as of the specified backup time. This is called a no-image browse.

Unconditional Overwrite

If this option is selected: All data being restored is unconditionally written to the specified location. If this option is cleared: Files/directories whose names are the same as those in the restore path and for which the backed up data is as old or older than those in the restore path are not restored. Files/directories whose names are the same as those in the restore path and for which the backed up data is newer than those in the restore path are restored. Files/directories whose names are different from those in the restore path are restored.

Restore ACLs

If this option is selected: All data being restored retains its original access control lists (ACLs) and therefore its original security attributes. If this option is cleared: The data is restored without the ACLs. Consequently, the restored data assumes the ACLs of the parent directory.

Recreate Mount Points

If this option is selected: Any mount points that have been deleted or that have had a change in the configuration are recreated during the restore operation. If this option is cleared: Any mount points that have been deleted or whose configuration has changed will not be restored.

Exclude Files/Folders Button

Allows you to specify files and/or folders that you want to filter from the restore. To add a file or folder to the filter, use the Add button. To delete a file or folder from the filter, highlight the path in the window and click the Delete button.

280 Backup and Restore for Internet Data Center Table 4.24: System State Restore options Option

Description

system state

This option includes system state in this restore with the corresponding options described later. There are several objects included in a system state restore. Galaxy provides a choice of restore type only for SYSVOL. For Active Directory, Galaxy performs a non-authoritative restore without offering restore type options. To force an authoritative Active Directory restore, you must use the ntdsutil utility.

Primary

A primary restore marks the restored data as the primary data for all of the replicas within the domain. This creates a new FRS database, and pushes the replicated system state data to any domain controllers added to the replication system. Note: A primary restore should be used only when all other domain controllers are non-functional and you want to rebuild the domain from the last backup. Do not perform a primary restore if any other working domain controller from this domain is available.

Authoritative

When the restored data is meant to override the data on other domain controllers, it should be restored using the authoritative mode. After this data is restored to the domain controller, it is propagated to the other domain controllers and will overwrite any newer data on those computers. The authoritative mode is useful if critical system state data has been deleted and the deletion has been propagated to other servers. Note: Authoritative restores must be performed with caution, as the system state will be rolled back to the point of the backup, possibly resulting in a loss of data that cannot be restored after it is overwritten.

Non-Authoritative (default)

When system state data is restored to a domain controller, by default it is restored in a non-authoritative mode. After the system state is restored in a non-authoritative mode, newer data on the network is propagated to the restored computer, updating it with any newer information.

Chapter 4: Advanced Backup and Restore Operations 281

Table 4.25: System Database options Option

Description

System Databases

This option includes system databases in this restore with the corresponding options described in this table.

Event Logs

Restores the system event logs when selected.

RSM Database

Restores the RSM database when selected.

Terminal Server Database

Restores the Terminal Services database when selected.

Quota Information

Restores quota information when selected.

Content Indexing Catalogs

Restores the content indexing catalogs when selected.

Advanced Option

Displays the Choose Copy Precedence window, which allows you to select the precedence of the copies from which you want to restore data. By default, Galaxy restores the data from the copy that has the highest precedence and has the data. Usually this will be the primary copy (precedence of 1). If, however, the data is distributed to multiple copies (using the auxiliary copy feature) whose retention periods are greater than that of the primary copy, then the data (if it comes from an older backup) will restore from a secondary copy.

Keep in mind that restore operations are conducted at the backup-set level and therefore transcend subclient boundaries. If the data being restored was backed up from different subclients, each associated with a different storage policy, then the restore data will be restored from those copies whose precedence matches the one that is specified. If the specified copy is not available for a given subclient, the restore operation will not be completed successfully.

Restoring Exchange 2000 Server In some cases, an Exchange 2000 database may become corrupted. In that event, the Exchange 2000 Server software must be reinstalled before the database is restored. The procedures in this section describe this type of rebuild.

Considerations When Restoring the Entire Computer The system state or file system must be restored on the system where the Exchange 2000 Server resides. See the procedures in the Galaxy Client Administration Guide (Windows 2000 Server Family). After the computer is operational, continue to “Restoring Exchange Databases” later in this chapter. The computer may need a full system rebuild, including the system state and file system, before the Exchange 2000 Server is recovered.

282 Backup and Restore for Internet Data Center

Active Directory is corrupted and resides on the Exchange 2000 Server. See the Galaxy Client Administration Guide (Windows 2000 Server Family), (Full System Restore Procedures). If the Exchange 2000 Server is the only object that is missing or corrupt in Active Directory, follow the procedures for restoring Exchange later in this chapter. Active Directory is corrupted and does not reside on the Exchange 2000 Server. See the Galaxy Client Administration Guide (Windows 2000 Server Family), (Full System Restore Procedures) to rebuild the domain controller on which Active Directory resides. If Exchange 2000 Server is the only object that is missing or corrupt in Active Directory, you can restore the Exchange 2000 Server objects by using a nonauthoritative system state restore. Exchange 2000 Server requires an SRS database recovery. The Site Replication Service (SRS) must be functional before the database is restored. SRS is backed up as part of the system state. See the Galaxy Client Administration Guide (Windows 2000 Server Family) for information on this topic. Exchange 2000 Server requires a key management system database recovery. See the Galaxy Client Administration Guide (Windows 2000 Server Family), Full System Restore Procedures to restore the file system and system state. If the Exchange 2000 Server was the certificate authority, this will be included with the key management system (KMS) when the system state is restored. If the KMS application data is missing or corrupt, restoring the file system data will include this. The default location of the program data is \Program Files\Exchsrvr\KMS\Data. Exchange 2000 Server resides on a Cluster Server and the Cluster Server is corrupt. See Galaxy Client Administration Guide (Windows 2000 Server Family), (Full System Restore Procedures). The Cluster Server is operational and only the Exchange 2000 Server needs recovery. In that case, follow these procedures.


To perform Exchange 2000 Server Recovery 1. Review “Considerations” earlier in this chapter to determine if a full restore of the Windows 2000 system state and file system is required. For procedures and supporting information, see the Galaxy Client Administration Guide (Windows 2000 Server Family). 2. If Active Directory contains the Exchange 2000 Server Objects, run Exchange setup in disaster recovery mode (setup/disasterrecovery). If the Exchange 2000 Server objects are not present in Active Directory, see “Restoring System State First.” You can choose to reinstall Exchange 2000 Server, but you must use the identical information structure and hierarchy as were used in the original Exchange 2000 Server. In either instance, you must install Exchange 2000 Server to the same location where it was originally installed. If you choose to set up in disaster recovery mode, do not restart the computer when the setup is complete. Continue to the next step.

Chapter 4: Advanced Backup and Restore Operations 283

3. Verify that Circular Logging for all storage groups is disabled. 4. If there is software currently running on the server that may attempt to access 5. 6. 7. 8.


the Exchange 2000 database, such as Virus Scan, disable it at this time. Perform a full restore of the Exchange 2000 database, selecting all Exchange 2000 Databases requiring a restore. You can now enable any software that was disabled in a previous step. Verify that the server is operational. Perform a full backup of the Exchange 2000 database to ensure the existence of a current archive.

To restoring single or multiple Exchange databases This procedure describes how to restore the Exchange 2000 Server database(s). Do not perform this procedure unless you intend to overwrite your existing Exchange 2000 Server database with the backed up version. 1. Dismount any databases that will be restored. If you are restoring the entire Exchange 2000 Server, dismount all stores. 2. If you are restoring the KMS database, verify that the key management server data directory is empty (typically \Program Files\Exchsrvr\Kmsdata), and make sure that the Microsoft Exchange KMS is started. 3. If you are restoring the site replication service (SRS) database, verify that there are no *.ebd , *.log or *.chk files in the Exchsrvr/Srsdata folder, and verify that the Microsoft Exchange Site Replication Service is started. 4. On the Windows taskbar, click Start, point to Programs, click Galaxy, and then click Galaxy CommCell Console. 5. In the CommCell logon window, log on by entering your Galaxy user name and password. Galaxy displays the CommCell console window. 6. In the CommCell browser tree, select and double-click the client. 7. In the CommCell browser tree, right-click the Exchange Database iDataAgent icon and then click Browse Backup Data. 8. In the Browse Options dialog box, click OK (assuming the default settings are being used). 9. Galaxy displays the Browse dialog box, which shows the Exchange 2000 Server databases. 10. In the Browse dialog box, select the database(s) to be restored. 11. Click the Restore All Selected button. 12. Verify the contents of the Restore Summary dialog box. 13. To automatically mount the stores after the restoration, check the Mount database after restore option. Note that this option will be disabled if only KMS or SRS databases have been selected for restore.

284 Backup and Restore for Internet Data Center 14. Click OK. 15. Galaxy starts a full restore of the items selected. After the data is fully restored,

Galaxy displays a confirmation message. Click OK to acknowledge the message. 16. If you restored the KMS database, make sure that you stop and then restart the KMS after the restore has successfully completed. 17. If you restored the SRS database, make sure that you stop and then restart the SRS after the restore has been successfully completed.

Restoring SQL Server 2000 Here you can find information on and procedures for fully restoring SQL Server and its databases that are secured by Galaxy.

Performing a Full System Restore A full system restore operation restores all files (including the operating system) and SQL Server databases on a client computer after a catastrophic event. Before beginning a SQL database restore operation, determine if a full restore of the Windows 2000 system state and file system is required. For procedures and supporting information, see the Galaxy Client Administration Guide (Windows 2000 Server Family). The full system restore is a two-step process: 1. The computer must be fully functional with the Microsoft SQL Server application installed. A Full iDataAgent Restore will accomplish this. If a full system restore has been performed, uninstall and reinstall Microsoft SQL Server on the computer after performing a full system rebuild. Uninstall and re-install Microsoft SQL Server 2000 and Service Pack 1. The server and instance name should be the same as in the previous installation. If this is not recorded anywhere, use the CommCell Browser and browse the computer you need to restore. The SQL Server instance name is listed under the SQL iDataAgent in the Commcell console. You can see the location of the data and log file directories by browsing the file system iDataAgent. 2. The SQL Server databases must be restored. Follow the procedures given in “Performing Full SQL Server Instance Restores.” When you restore the SQL Server with Commerce Server 2000 installed, you should stop Commerce Server 2000 services before you start the restore operation.

Chapter 4: Advanced Backup and Restore Operations 285

Performing a Full SQL Server Restore A full SQL Server instance restore is the process of fully restoring all databases of a SQL Server instance, either to the same computer or to a different one. Full SQL server instance restores can be helpful or even necessary, depending on circumstances. Some examples are as follows: ● Creating a server running SQL Server that duplicates the data and configuration from another server running SQL Server. ● Re-establishing a SQL Server’s databases after a catastrophic server failure.

Restoring the Entire Computer If a system state or file system restoration is necessary on the system where the SQL Server resides, see the procedures in “Restoring a Non-Domain Controller or Member Server.” After the computer is operational, continue to “Performing Full SQL Server Instance Restores.” The computer may need a full system rebuild before the SQL Server is recovered. The particular steps required for the restore depend on the state of the SQL Server computer: The computer has been rebuilt and restored using full file system iDataAgent Restore. Uninstall and re-install SQL Server on the computer after performing a full system rebuild. The server and instance name should be the same as those that were used when SQL Server was installed previously. If this is not recorded anywhere, use the CommCell browser and browse the computer you need to restore. The SQL instance name is listed under SQL iDataAgent in the CommCell console. After you complete the steps for the restore operation, you will also need to perform a SQL Server restore operation on servers that are running SQL Server, as described in “Recovering SQL Server.” The SQL Server resides in a cluster. Restoring SQL Server to a cluster requires that the Microsoft cluster services and SQL Server be functional prior to the restore. If necessary, install Microsoft cluster software and Microsoft SQL Server 2000 and Service Pack 1. Data or registry information on the physical node is missing. Perform a full system iDataAgent restore on the physical node; then uninstall and re-install Microsoft SQL Server to the virtual server. Cluster database information, such as SQL cluster resources, is missing. Run authorutil –cluster after performing a full system iDataAgent restore on the physical node that owns the cluster group/quorum drive. Program files are missing from the virtual drive. Perform a file system restore for the virtual server that owns the program drive.

286 Backup and Restore for Internet Data Center

Performing Full SQL Server Instance Restores When performing a full SQL Server instance restore, you must select Unconditionally overwrite existing databases or files in the SQL Server Restore Options dialog box. There are two methods you can use to perform a SQL Server instance restore. The first method is the recommended method. ● Method 1 allows you to restore the system databases (master, model, and msdb) as one restore operation, and then restore user-defined databases one by one. By using Method 1, you can get your instance up and running before you attempt to restore your user databases. This method also allows you to determine the order in which databases are restored. You can even restore user databases in parallel as long as the databases are properly configured. ● Method 2 allows you to restore the whole instance, both system and user defined databases, as one job.


Method 1: To restore full SQL Server instances 1. The SQL Server service must be started. If the SQL Server is started, begin with step 2. If the SQL Server will not start, see “Rebuilding the Master Database (Rebuild Master Utility).” 2. Perform either a single or multiple database restore of the system databases (master, model, msdb). 3. If you are restoring to a different SQL Server, the data directory where the SQL Server system databases (master, msdb, model) reside must be identical on both SQL Server computers. 4. Restore the user databases in the order you want. 5. If the master database has been restored to a different SQL Server, execute the following stored procedures on the new host SQL Server: sp_dropserver ‘ oldservername ‘ sp_addserver ‘ newservername ‘, ‘LOCAL’




Method 2: To restore full SQL Server instances 1. The SQL Server service must be started. If the SQL Server is started, begin with step 2. If the SQL Server will not start, see “Rebuilding the Master Database (Rebuild Master Utility).” 2. In the CommCell browser, right-click on the SQL Server instance that you want to restore, and select Restore SQL Server. 3. In the SQL Server Restore Options dialog box, select Overwrite existing databases and files, and any other restore options that you want.

Chapter 4: Advanced Backup and Restore Operations 287

4. If you are restoring to a different SQL Server, the data directory where the SQL

Server system databases (master, msdb, model) reside must be identical on both SQL Server computers. 5. Click OK. 6. If the master database has been restored to a different SQL Server, execute the following stored procedures on the new host SQL Server: sp_dropserver ‘ oldservername ‘ sp_addserver ‘ newservername ‘, ‘LOCAL’

Rebuilding the Master Database (Rebuild Master Utility) If the SQL Server will not start, run the SQL Server utility Rebuildm.exe (at a command prompt) to rebuild the master database. This utility re-creates the system databases (master, msdb, model) and default databases (pubs and northwind) in the SQL Server data directory so that the SQL Server service can be started.


To rebuild the master database 1. Shut down Microsoft SQL Server 2000, and then run Rebuildm.exe. This is located in the Program Files\Microsoft SQL Server\80\Tools\Binn directory. If you use the SQL Server installation compact disc, copy all the files from the compact disc to a local hard drive. Remove the read-only attribute from the files after you copy them to the hard drive. For more information, see the following article in the Microsoft Knowledge Base: “Q273572 BUG: Rebuildm.exe Utility Stops Responding When Source Directory is on a CD.” You will then need to execute Rebuildm.exe and point it either to the original shared installation files or to the files that you copied from the compact disc to the local hard drive. 2. In the Rebuild Master dialog box, click Browse. 3. In the Browse for Folder dialog box, select the \Data folder on the SQL Server 2000 compact disc or in the shared network directory from which SQL Server 2000 was installed, and then click OK. 4. Click Settings. In the Collation Settings dialog box, verify or change settings used for the master database and all other databases. 5. Initially, the default collation settings are shown, but these may not match the collation selected during setup. You can select the same settings used during setup or select new collation settings. When done, click OK. 6. In the Rebuild Master dialog box, click Rebuild to start the process. The Rebuild Master utility reinstalls the master database. To carry out this procedure, you may need to stop a server that is running on this computer.

288 Backup and Restore for Internet Data Center

Rebuilding the Master Database on a Virtual (Clustered) SQL Server 2000 Server To rebuild the master SQL Server 2000 database, perform the following steps: 1. Make sure that the node in which you execute Rebuildm.exe is controlling the SQL Server resources. 2. Use the SQL Server service manager Bring the SQL Server virtual server offline by using. 3. Make sure that the original shared installation files or the SQL Server installation compact disc is available. If you use the SQL Server installation compact disc, copy all the files from the compact disc to a local hard drive. Remove the readonly attribute from the files after you copy them to the hard drive. For more information, see the following article in the Microsoft Knowledge Base: “Q273572 BUG: Rebuildm.exe Utility Stops Responding When Source Directory is on a CD.” Run Rebuildm.exe and point it to the original shared installation files or the files that you copied from the compact disc to the local hard drive. 4. Select Windows Collation or SQL Collation. 5. After the Rebuildm.exe program completes, verify that you can bring the resources online and that they successfully fail over. 6. Execute the sp_helpsort stored procedure to verify the collation. Note: The preceding procedure does not include the steps that are necessary to rebuild user databases. If you have a recent backup of the master database, you may restore it at this point. If not, you must restore or attach the user databases.

p a t t er ns & p ra c t i c es Proven practices for predictable results

Reduce project cost ●

Exploit Microsoft’s engineering efforts to save time and money on projects

●

Follow Microsoft’s recommendations to lower project risks and achieve predictable outcomes

Increase confidence in solutions ●

Build solutions on Microsoft’s proven recommendations for total confidence and predictable results

●

Provide guidance that is thoroughly tested and supported by PSS, not just samples, but production quality recommendations and code

Deliver strategic IT advantage ●

Gain practical advice for solving business and IT problems today, while preparing companies to take full advantage of future Microsoft technologies.

To learn more about patterns & practices visit: msdn.microsoft.com/practices To purchase patterns & practices guides visit: shop.microsoft.com/practices

Proven practices for predictable results

Patterns & practices are based on real-world experiences that go far beyond white papers to help enterprise IT pros and developers quickly deliver sound solutions. This technical guidance is reviewed and approved by Microsoft engineering teams, consultants, Product Support Services, and by partners and customers. Organizations around the world have used patterns & practices to:

p a t t er ns & p ra c t i c es

Patterns & practices are Microsoft’s recommendations for architects, software developers, and IT professionals responsible for delivering and managing enterprise systems on the Microsoft platform. Patterns & practices are available for both IT infrastructure and software development topics.

p a t t er ns & p ra c t i c es Proven practices for predictable results Patterns & practices are available for both IT infrastructure and software development topics. There are four types of patterns & practices available:

Proven practices for predictable results

p a t t er ns & p ra c t i c es

Reference Architectures Reference Architectures are IT system-level architectures that address the business requirements, operational requirements, and technical constraints for commonly occurring scenarios. Reference Architectures focus on planning the architecture of IT systems and are most useful for architects.

Reference Building Blocks References Building Blocks are re-usable sub-systems designs that address common technical challenges across a wide range of scenarios. Many include tested reference implementations to accelerate development. Reference Building Blocks focus on the design and implementation of sub-systems and are most useful for designers and implementors.

Operational Practices Operational Practices provide guidance for deploying and managing solutions in a production environment and are based on the Microsoft Operations Framework. Operational Practices focus on critical tasks and procedures and are most useful for production support personnel.

Patterns Patterns are documented proven practices that enable re-use of experience gained from solving similar problems in the past. Patterns are useful to anyone responsible for determining the approach to architecture, design, implementation, or operations problems.

To learn more about patterns & practices visit: msdn.microsoft.com/practices To purchase patterns & practices guides visit: shop.microsoft.com/practices

p a t t er ns & p ra c t i c es c u r r e n t t i t l e s December 2002

Reference Building Blocks Data Access Application Block for .NET 279 pages .NET Data Access Architecture Guide 60 pages Designing Data Tier Components and Passing Data Through Tiers 70 pages Exception Management Application Block for .NET 307 pages Exception Management in .NET 35 pages Monitoring in .NET Distributed Application Design 40 pages Microsoft .NET/COM Migration and Interoperability 35 pages Production Debugging for .NET-Connected Applications 176 pages Authentication in ASP.NET: .NET Security Guidance 58 pages Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication 608 pages

Operational Practices Security Operations Guide for Exchange 2000 Server 136 pages Security Operations for Microsoft Windows 2000 Server 188 pages Microsoft Exchange 2000 Server Operations Guide 113 pages Microsoft SQL Server 2000 Operations Guide 170 pages Deploying .NET Applications: Lifecycle Guide 142 pages Team Development with Visual Studio .NET and Visual SourceSafe 74 pages Backup and Restore for Internet Data Center 294 pages

For current list of titles visit: msdn.microsoft.com/practices To purchase patterns & practices guides visit: shop.microsoft.com/practices

Proven practices for predictable results

Microsoft Systems Architecture—Enterprise Data Center 2007 pages Microsoft Systems Architecture—Internet Data Center 397 pages Application Architecture for .NET: Designing Applications and Services 127 pages Microsoft SQL Server 2000 High Availability Series: Volume 1: Planning 92 pages Microsoft SQL Server 2000 High Availability Series: Volume 2: Deployment 128 pages Enterprise Notification Reference Architecture for Exchange 2000 Server 224 pages Microsoft Content Integration Pack for Content Management Server 2001 and SharePoint Portal Server 2001 124 pages UNIX Application Migration Guide 694 pages Microsoft Active Directory Branch Office Guide: Volume 1: Planning 88 pages Microsoft Active Directory Branch Office Series Volume 2: Deployment and Operations 195 pages Microsoft Exchange 2000 Server Hosting Series Volume 1: Planning 227 pages Microsoft Exchange 2000 Server Hosting Series Volume 2: Deployment 135 pages Microsoft Exchange 2000 Server Upgrade Series Volume 1: Planning 306 pages Microsoft Exchange 2000 Server Upgrade Series Volume 2: Deployment 166 pages

p a t t er ns & p ra c t i c es

Reference Architectures