Using Tivoli Data Protection for Microsoft Exchange Server Strategic planning and implementation considerations for effective backup Backup over the LAN and Storage Area Network Successful recoveries Pat Randall Ivanka Kabranova Jan Sternberg Marcus Thordal ibm.com/redbooks
SG24-6147-00 International Technical Support Organization Using Tivoli Data Protection for Microsoft Exchange Server May 2001
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix H, Special notices on page 151. First Edition (May 2001) This edition applies to Version 2, Release 2 of Tivoli Data Protection for Microsoft Exchange Server, Program Number 5698-PDX for use with Exchange 2000 and Exchange 5.5 running on the Windows 2000 and NT 4.0 Operating Systems. Exchange 2000 requires Windows 2000. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 2001. All rights reserved. Note to U.S Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents Figures................................................... vii Preface....................................................ix The team that wrote this redbook....................................ix Comments welcome.............................................. x Chapter 1. Exchange overview for TSM administrators............. 1 1.1 General overview......................................... 1 1.2 Exchange core components and backup....................... 2 1.2.1 Exchange 5.5 database technology and backup.............. 2 1.2.2 Exchange 2000 database technology and backup............ 3 1.3 Files maintained by Outlook................................. 4 1.3.1 Offline folders........................................ 4 1.3.2 Personal folders...................................... 5 1.3.3 Personal address book................................. 5 1.3.4 Archive folders....................................... 5 1.3.5 Outlook favorites bar file................................ 5 Chapter 2. Planning considerations............................ 7 2.1 Backup strategies......................................... 7 2.1.1 Online versus offline backup............................. 7 2.1.2 Backing up Exchange databases......................... 8 2.1.3 Backup strategies for Exchange 2000 and 5.5.............. 12 2.2 Sizing................................................. 17 2.3 TSM: Preparation for TDP for Exchange...................... 18 2.3.1 Policies and management classes....................... 18 2.3.2 Node registration.................................... 21 2.4 TDP for Exchange v.1 and v.2: differences and coexistence....... 21 2.5 How TDP for Exchange stores objects on the TSM server......... 22 Chapter 3. Installation of TDP for MS Exchange servers........... 25 3.1 TDP for Exchange requirements............................. 25 3.2 How to Install the TDP Agent............................... 26 3.2.1 Installing TDP for Exchange............................ 26 3.2.2 Registering TDP for Exchange with a TSM server........... 29 3.2.3 The TDP for Exchange options file....................... 29 3.3 Installing TDP for Exchange in an MSCS environment............ 30 3.4 Silent installation........................................ 31 3.5 Installing the Backup/Archive client.......................... 33 Copyright IBM Corp. 2001 iii
Chapter 4. Backing up Exchange databases.................... 35 4.1 Exchange 5.5 DIR and IS backup general procedures............ 35 4.1.1 Backing up Exchange 5.5 using the GUI................... 35 4.1.2 Backing up Exchange 5.5 using the Command Line Interface... 40 4.2 General procedures for backing up Exchange 2000.............. 45 4.2.1 Backing up Exchange 2000 using the GUI................. 45 4.2.2 Backing up Exchange 2000 using the CLI.................. 47 4.2.3 Backing up Site Replication Service...................... 50 4.2.4 Backing up Key Management Service..................... 51 4.2.5 Backing up Active Directory............................ 52 4.3 Recommended practices.................................. 52 4.3.1 Include/Exclude statement............................. 52 4.3.2 Different node names................................. 55 4.4 Clustering.............................................. 55 4.5 Automating backups...................................... 57 4.5.1 Scheduling backups on a single node..................... 58 4.5.2 Scheduling backups on a cluster........................ 61 4.6 Performance............................................ 64 4.7 Integration with other products.............................. 65 Chapter 5. SAN usage...................................... 67 5.1 Overview of LAN-free SAN and TDP for Exchange............... 67 5.1.1 The TSM Storage Agent............................... 68 5.2 Setting up LAN-free SAN support............................ 70 5.2.1 Preparing TSM server for LAN-free configuration............ 70 5.2.2 Setting up the client node to support LAN-free.............. 72 Chapter 6. Day-to-day monitoring............................. 83 6.1 DB log management...................................... 83 6.1.1 TSM activity log..................................... 83 6.1.2 TDP for Exchange log................................. 83 6.1.3 TSM API log........................................ 84 6.1.4 Windows event logs.................................. 84 6.1.5 TSM scheduler logs.................................. 84 6.2 Day-to-day verifications................................... 84 6.2.1 TSM server monitoring................................ 84 6.2.2 TDP for Exchange log................................. 88 6.2.3 TSM API log........................................ 89 6.2.4 Windows event log................................... 89 6.2.5 TSM Scheduler logs.................................. 91 6.3 Test restores........................................... 92 6.4 Auto deletion of old backups............................... 92 6.5 Verifying the success of the backup using the GUI............... 94 iv Using Tivoli Data Protection for Microsoft Exchange Server
6.5.1 Query commands.................................... 94 Chapter 7. Restoring Exchange databases..................... 103 7.1 Basic Information Store recovery from online backups........... 103 7.1.1 General restore procedures for Exchange 5.5............. 104 7.1.2 General restore procedures for Exchange 2000............ 104 7.1.3 Using the TDP for Exchange GUI for restoring Exchange..... 107 7.1.4 Using the TDP for Exchange CLI for restoring Exchange..... 109 7.1.5 Restoring Exchange in a cluster environment.............. 115 7.2 Single item and mailbox recovery........................... 117 7.2.1 Deleted Item Retention feature......................... 117 7.2.2 Alternate server restore.............................. 120 7.3 Disaster recovery....................................... 127 7.3.1 Disaster recovery for Exchange 5.5..................... 128 7.3.2 Disaster recovery for Exchange 2000.................... 128 7.4 Restoring Site Replication Service (SRS) database............. 129 7.5 Restoring Key Management Service (KMS) database........... 132 Appendix A. Lab environment................................. 133 Appendix B. Best practices................................... 135 Appendix C. Quick start / checklist............................. 137 C.1 Checklist................................................. 137 C.2 Installation................................................ 137 C.3 Performing backups........................................ 138 C.4 Performing restore......................................... 139 C.5 Solving problems.......................................... 139 Appendix D. Gotchas....................................... 141 D.1 Exchange 5.5 backups invoked from Terminal Service client hangs... 141 D.2 Using NTBackup in Window 2000 to Backup Exchange 5.5......... 141 D.3 Perform a full backup after restoring............................ 142 Appendix E. Troubleshooting.................................. 143 Appendix F. Limitations of the GUI............................. 147 F.1 Backing up the SRS database................................ 147 F.2 Backing up the KMS database................................ 147 F.3 Viewing the TSM object name................................ 147 v
Appendix G. TSM object names................................ 149 Appendix H. Special notices.................................. 151 Appendix I. Related publications............................... 155 I.1 IBM Redbooks............................................. 155 I.2 IBM Redbooks collections.................................... 156 I.3 Tivoli publications........................................... 156 I.4 Other resources............................................ 159 I.5 Referenced Web sites and newsgroups.......................... 159 I.5.1 Web sites............................................. 159 I.5.2 Newsgroups........................................... 160 How to get IBM Redbooks.................................. 161 IBM Redbooks fax order form.................................... 162 Glossary................................................ 163 Index................................................... 169 IBM Redbooks review...................................... 173 vi Using Tivoli Data Protection for Microsoft Exchange Server
Figures 1. TDP for Exchange, TSM APIs, and Exchange APIs: online backup...... 8 2. Circular logging and location of transaction log files................. 10 3. Setting Item Recovery settings for an Exchange 5.5 Information Store.. 15 4. Setting Deletion settings for an Exchange 2000 database............ 16 5. Specifying an installation path.................................. 27 6. TDP for Exchange registration.................................. 28 7. Properties for the shortcut for GUI............................... 31 8. TDP for Microsoft Exchange 5.5 Server GUI....................... 36 9. Backup of Exchange 5.5 Directory and Information Store............. 37 10. Configuring settings general tab.............................. 38 11. Configuration settings performance tab........................ 39 12. Configuration settings logging tab............................. 39 13. Configuration settings regional tab............................ 40 14. TDP for Microsoft Exchange 2000 GUI........................... 45 15. Configuration settings for Exchange 2000......................... 46 16. Example of using Include/Exclude statement...................... 53 17. Result of the backup......................................... 54 18. Backing up Exchange on a cluster............................... 56 19. Defining schedule TSM administrative client Web interface......... 59 20. Associate client nodes with the schedule......................... 60 21. Registry Replication.......................................... 63 22. LAN-free backup............................................ 68 23. SAN devices seen by Windows 2000 after installing Host Bus Adapter.. 73 24. Version of the API-dll......................................... 74 25. AdsmScsi device management................................. 76 26. TSM server monitoring........................................ 85 27. TSM activity log............................................. 86 28. Monitoring Windows event log.................................. 90 29. Verifying success using the GUI................................ 94 30. Restoring the ITSO 6147 Mailbox Store......................... 108 31. Recovering deleted items.................................... 118 32. DS/IS Consistency Adjustment................................ 122 33. Using ADSI Edit to get the legacyexchangedn.................... 124 34. Reconnecting mailboxes..................................... 127 35. Exchange lab environment................................... 133 36. No Exchange organization available for NTBackup................. 141 37. Modifying the GUI shortcut................................... 145 Copyright IBM Corp. 2001 vii
viii Using Tivoli Data Protection for Microsoft Exchange Server
Preface This IBM Redbook is an experience-based description of how to use Tivoli Data Protection (TDP) for Microsoft Exchange v.2.2 to perform backups and restores in your Exchange environment. Tivoli Data Protection for Microsoft Exchange server performs online backups of Microsoft Exchange server databases to Tivoli Storage Manager (TSM) storage. We demonstrate how to back up and recover data on Exchange 5.5 as well as Exchange 2000 on a single server installation and a clustered environment. We decided to use Windows 2000 (Service Pack 1) as the operating system and Exchange 5.5 and Exchange 2000. However, we do not cover backing up the operating system itself. Version 2.2 provides new functionality as well as support for Exchange 2000. Most significantly, the new version of Tivoli Data Protection for Exchange supports one of the important features of Tivoli Storage Management: automatic expiration and version control by policy. We demonstrate how this frees users from having to explicitly delete backup objects in the Tivoli Storage Manager server. TDP for Exchange supports LAN-free data movement. We show how to use TDP for Exchange to perform backups across a traditional LAN as well as utilizing TSM LAN-free to support backups across Storage Area Networks (SANs). Focus is placed on protection of Exchange data, and thorough performance tests are not included. For a description of backing up the Windows 2000 operating system and Active Directory consult Deploying the Tivoli Storage Manager Client for Windows 2000, SG24-6141. This document is written for Exchange administrators as well as TSM administrators with a need to understand the issues and considerations pertinent to utilizing TSM and TDP to back up and restore Microsoft Exchange. The team that wrote this redbook This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization San Jose Center. Pat Randall is a Distributed Storage Software Specialist at the International Technical Support Organization, San Jose, California. He has written 12 Copyright IBM Corp. 2001 ix
Redbooks on ADSM and Tivoli Storage Manager, teaches IBM classes worldwide on all areas of distributed storage, and is a consultant in disaster and business recovery. Before joining the ITSO in July 1996, Patrick worked in IBM UK's Business Recovery Services as a Solutions Architect. Ivanka Kabranova is an IT Expert in Bulgaria. She has 5 years of experience in the IT field, as an administrator of messaging and information systems based on Lotus Notes and MS Exchange server. She holds a degree from Technical University, Sofia. Jan Sternberg is an Advisory IT Specialist at IBM Global Services, Denmark. He has worked at IBM for 7 years. His areas of expertise include Geographical Information Systems, AIX, and Microsoft BackOffice products, in particular, Microsoft Exchange. Jan is a Microsoft Certified Systems Engineer (MCSE) and he holds an MSc. degree in Electronic Engineering from The Technical University of Denmark. Marcus Thordal is an IT Analyst at IBM Global Services, Denmark. He has been with IBM for 3 years. He is MCSE certified, and his areas of expertise include MS cluster, SQL server, and Windows 2000 systems. He holds a BSc. Eng. degree from The Technical University of Denmark. Thanks to the following people for their invaluable contributions to this project: Del Hoobler IBM Global Services, Endicott Jon Tate, SAN Specialist International Technical Support Organization, San Jose Center Yvonne Lyon, editor International Technical Support Organization, San Jose Center Comments welcome Your comments are important to us! We want our Redbooks to be as helpful as possible. Please send us your comments about this or other Redbooks in one of the following ways: Fax the evaluation form found in IBM Redbooks review on page 173 to the fax number shown on the form. Use the online evaluation form found at ibm.com/redbooks Send your comments in an Internet note to redbook@us.ibm.com x Using Tivoli Data Protection for Microsoft Exchange
Chapter 1. Exchange overview for TSM administrators This chapter provides a general overview of Exchange aimed at TSM administrators. 1.1 General overview Exchange server is a contemporary messaging system which enables users to exchange information and messages within an organization and with users on the Internet. It also allows users to view items that are in Public Folders, as well as posting items in these folders so that the other users can see them. Exchange server is a Client/Server Messaging System, meaning that the messaging process is divided between the client and the server. The client composes the messages and sends them to the server, then the server places messages in the appropriate place and communicates with the other servers. If there are new messages for the user, the server dispatches them. Exchange server has a hierarchical organization. In Exchange 5.5, the main container is your organization. The next level is a site or sites. You may have more than one site in your organization. Think of a site as a logical group of servers (for instance, according to geographical location). Servers within a site can replicate directory information and route mail directly to each other, but the administrator must explicitly set replication between sites. Servers are the third level. They contain local user s mailboxes (recipients) and Public Folders for the server. In addition, they may be used for tasks such as connecting to the other Exchange sites or to foreign systems; or for special needs, like replication between sites. In Exchange 2000, servers are organized in administrative groups (instead of sites) for easy administration and in routing groups to control the message flow. Administrative groups do not necessarily coincide with routing groups if you have only Exchange 2000 in your organization and the Exchange server is switched to native mode (the default is mixed). But as long as you have coexistence with Exchange 5.5, you must run Exchange 2000 server in mixed mode, and the content of administrative groups must not deviate from the content of routing groups. Exchange 5.5 keeps its own directory information in the Exchange directory database. Exchange 2000 relies on directory information provided by the Active Directory and the operating system. Because Active Directory Copyright IBM Corp. 2001 1
supports attribute-level security permissions, administrators have more precise control over the Exchange security configuration. 1.2 Exchange core components and backup Awareness of the underlying database technology that Exchange uses can help you to better understand the backup and restore processes. 1.2.1 Exchange 5.5 database technology and backup Exchange 5.5 uses a transaction-based logging system to ensure that users never lose information. All transactions are written first to the transaction log (*.log), then committed to the corresponding database file (*.edb). In the event of a failure, all transactions can be replayed. Exchange also uses check point files which indicate when a transaction is successfully committed to the database file. Using check point files preserves the server from replaying every transaction. Instead, only uncommitted data is replayed. Microsoft Exchange 5.5 has four core components which are implemented as Windows services: Directory service The directory service manages information about addresses, mailbox information, distribution lists, public folder hierarchy, and other servers. The directory information is stored in the dir.edb database file. Information store The Information Store service maintains the server-based private (user mailboxes) and public folder information. The private and public store Information Stores are in two separate databases: priv.edb and pub.edb. The Information Store is responsible for replicating public folders, enforcing storage limits, and delivering messages to users on the same server. Message transfer agent (MTA) The MTA manages submitting, routing, and delivering messages to other servers, other sites, or foreign systems. System attendant The system attendant service is responsible for a number of actions such as server monitoring, checking messaging connectors, checking directory replication, building routing tables, generating e-mail addresses, logging message tracking information, and assisting in generation of the offline address book. All the other services are dependent on the system attendant. 2 Using Tivoli Data Protection for Microsoft Exchange Server
For the Exchange server 5.5 to be backed up, you must perform backup of: The directory service, ExchInstalDir\dsadata\dir.edb The transaction logs for the directory service, ExchInstalDir\dsadata\*.log The private Information Store, ExchInstalDir\mdbdata\priv.edb The public Information Store, ExchInstalDir\mdbdata\pub.edb The transaction logs for the Information Store, ExchInstalDir\mdbdata\*.log The key management server, ExchInstalDir\mdbdata\kmsdata You must keep in mind that Exchange 5.5 uses Windows account information, so you must have access to the account information in order to perform a successful restore. 1.2.2 Exchange 2000 database technology and backup Exchange 2000 database technology is based on the Extensible Storage Engine (ESE) which is part of the Microsoft Web Storage System process. Exchange 2000 uses Microsoft Windows 2000 Active Directory. In earlier versions of Exchange, the directory was an ESE database that was backed up with other Exchange databases. Because the Exchange 2000 directory information is stored in Active Directory, backing up Windows 2000 Active Directory is as important as backing up Exchange 2000 databases. Exchange 2000 provides support for multiple databases and storage groups on the same server. Exchange 2000 allows up to five multiple databases per storage group, with four storage groups possible per server. One database within a storage group is composed of the following files: The *.edb file, which contains folders, tables, and indexes for messaging data, MAPI messages and attachments. The *.stm file, which is a new format in Exchange 2000 for storing native Internet content. The *.edb and *.stm files function as a pair. Also, if you have a Site Replication Service (if you have both Exchange 5.5 and Exchange 2000) and Key Management server, you will have the following files: Site Replication Service files, located in the ExchInstalDir\srsdata directory, which permit compatibility with Exchange 5.5 by emulating an Exchange 5.5 directory service. Key Management server files, which provide security encryption services. Chapter 1. Exchange overview for TSM administrators 3
Exchange 2000 also uses transaction log files. All transactions are written first to the transaction log (*.log), then committed to the correspoding database file (*.edb) and/or streaming database (*.stm). In the event of a failure, all transactions can be replayed using the transaction log. Exchange 2000 also uses check point files which indicates when a transaction is successfully committed to the database file. Using check point files preserves server from replaying every transaction instead of only uncommitted in case of disaster. So, for the Exchange server 2000 to be backed up, you must include the following types of data: Exchange Web Storage Systems databases and supporting files. Message tracking log files - if you are running message tracking. Use for instance Backup/Archive Client to back them up. Active Directory - plan backing up of Active Directory with regular Backup/Archive Client. Key Management Service databases. Site Replication Service (SRS) databases. 1.3 Files maintained by Outlook The Outlook client stores configuration and messaging data in files that are not part of the Microsoft Exchange server. These files may be included in the backup. For this purpose it is a good idea to place them on a file share and use Backup/Archive client for performing backups from central place. Otherwise the client itself must perform backup of these files. 1.3.1 Offline folders Offline folders are files that are replicated copies of the Microsoft Exchange server based mailbox. They are commonly referred to as ost-files because of their default extension. Ost-files are used by mobile users who are not permanently connected to the Microsoft Exchange server. They enable a mobile user to work offline and periodically synchronize local data with the server-based mailbox. The first time you configure and use an offline folder, an ost-file is created on the local file system, and the server-based mailbox is replicated. When working offline, you work in your offline mailbox exactly as you do with your mailbox on the server. When you connect to the Microsoft Exchange server, changes are sent to the server-based mailbox, and any new messages on the server are replicated to the ost-file. 4 Using Tivoli Data Protection for Microsoft Exchange Server
1.3.2 Personal folders Personal folders are files you can create to store messaging data on a file system outside the server-based mailbox. They are commonly referred to as pst-files because of their default extension. You can define as many pst-files as you like. You can copy, delete, rename, and move a pst-file just like any other file. 1.3.3 Personal address book The personal address book is the place where you store the personal address entries in Microsoft Outlook versions which do not support contacts. In later versions of Outlook you should use Contacts instead, because the contacts folder is stored on the server. The personal address book files have the extension pab. 1.3.4 Archive folders Archive folders are files created by the archive process on the Outlook client. They are pst-files. An identical folder structure is created between the archive file and the server-based mailbox. It is important to remember that when you archive items they are moved from the server-based mailbox to the client s file system and are no longer accessible on the server. 1.3.5 Outlook favorites bar file The Outlook favorites bar file contains configuration settings. When you customize the Outlook bar within the Outlook client, the changes are automatically saved to a file called <profile name>.fav. This file is unique for each user and cannot be copied to another user. Chapter 1. Exchange overview for TSM administrators 5
6 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 2. Planning considerations In this chapter we describe some strategies for backing up Exchange 5.5 and Exchange 2000 using TDP for Exchange. 2.1 Backup strategies Our considerations regarding backup are server-centric, and the scope does not include any discussion on backup and restore of the operation system itself. Backup strategies for data controlled by Exchange clients (see 1.3, Files maintained by Outlook on page 4) are not discussed in any greater detail either. For strategies on backing up Windows 2000 and client controlled files, we encourage you to consult the redbook Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141. 2.1.1 Online versus offline backup Offline database backups are defined as file level backups of database files while they are not in use. Thus the Exchange system (or at least parts of it) must be shut down in order to perform an offline backup. Online backups, on the other hand, leave the system running and will allow clients to continue working on the system. Users may experience some performance impact while the backup takes place. Besides the obvious benefit of being able to leave the system running and accessible, online backups do also ensure more reliable backups. When doing online backups, the database is automatically tested for any corruption. This is not the case for offline backups. In some cases a service level agreement will dictate online backups, but even though there may be a choice from the two methods, we strongly recommend online backups. TDP for Exchange supports online backups of Exchange 5.5 and 2000 utilizing the Exchange API and TSM API to communicate with Exchange and the TSM server respectively (see Figure 1). Use the TSM Backup/Archive client for offline backups. This book does not include strategies for offline backups. Note: The term backup (if not specified specifically as being offline) is generally used for online backups in the rest of this book. Copyright IBM Corp. 2001 7
Exchange Server Exchange storage group Transaction logs Tivoli Storage Manager server Exchange API TDP for Exchange v.2 TSM API Exchange databases Figure 1. TDP for Exchange, TSM APIs, and Exchange APIs: online backup 2.1.2 Backing up Exchange databases The concepts and functionalities of the Exchange 5.5 and Exchange 2000 databases are very much alike. Although Exchange 2000 has introduced the new core database file for Internet content data, the stm-file, and added more flexibility with respect to the number and naming of databases, the basic concepts for backing up the databases are very similar to the ones for Exchange 5.5. 2.1.2.1 Transaction logging As described in Chapter 1 Exchange databases are transactional databases. Data is written to the log files before it is committed to the database. Besides some performance benefits, transaction logging may enable you to restore data newer than the oldest backup by replaying the transaction logs. As a consequence of the nature of transaction logging, the placement of transaction log files is important. You should plan to place transaction logs on a physical disk separate from the disk holding the database itself. Thus you will have a possibility of replaying the latest transaction logs in case the disk(s) holding the database files should crash. Recommendation We strongly recommend placing transaction log files on disk separate from the databases themselves. The paths are set on the Server object properties Database Paths tab (Exchange 5.5) and the storage group properties General tab (Exchange 2000). See Figure 2. 8 Using Tivoli Data Protection for Microsoft Exchange Server
Transaction log files are always 5 MB in size, no matter if the file holds any data or not. The files are numbered sequentially, and when one log file is full, Exchange will start using the next one. The number of log files may be limited to a fixed number 1 or simply by the amount of disk space on the system. Microsoft Exchange server operates with the concept of circular logging. When using circular logging, transaction logs are reused in a round-robin fashion. In this way, old transaction logs that contain data which is not yet backed up may be overwritten. If circular logging is disabled, Exchange will simply create new log files on the fly as they are needed. Old log files are then purged from the system at the completion of the next successful full or incremental online backup. On Exchange 5.5 there are two sets of transaction logs: One set for the Directory Store and one set for the Information Store. If the server has got a public Information Store, it will be sharing the transaction logs with the private Information Store. On Exchange 2000 there is one set of transaction logs for every storage group. There may be as many as 4 storage groups per server and up to 5 databases in each storage group. The storage group feature and ability to have more databases in one storage group is new in Exchange 2000, and so is the concept of mounting and unmounting databases. On Exchange 2000, the Information Store service will independently mount and unmount databases within the individual storage groups as the administrator may wish. Since transaction logs are shared among the databases within a particular storage group, it is a very good idea to backup entire storage groups with all databases mounted in one attempt. TDP for Exchange performs backups at a storage group level. If a database is not mounted while the storage group is being backed up, the old transaction log files will not be purged. This may become an issue for the size of incremental backups if the database stays offline for an extended period. The size of the incremental backups will keep on increasing until the transaction log files can be purged. Thus the benefit of using the incremental backup type is slowly being reduced. Exchange 5.5 enables circular logging by default. Exchange 2000 disables it by default. The setting is configured from the server or storage group properties respectively. See Figure 2. 1 Even though Exchange is configured for circular logging the number may be temporarily increased if the server is stressed and new data arrives faster than data is committed to the database. Exchange will initially attempt to maintain a window of four log files when using circular logging. Chapter 2. Planning considerations 9
Figure 2. Circular logging and location of transaction log files You may also use the TDP tool tdpexcc to query the Exchange server for information about circular logging settings: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Microsoft Exchange Server Information ------------------------------------- Server Name: ELBRUS Domain Name: k2.uphi.sky Exchange Server Version: 6.0.4417.0 Storage Groups with Databases and Status ---------------------------------------- First Storage Group Circular Logging - Disabled Mailbox Store (ELBRUS) Public Folder Store (ELBRUS) ITSO SG Circular Logging - Disabled ITSO 6147 Online Online Online 10 Using Tivoli Data Protection for Microsoft Exchange Server
Recommendation We strongly recommend a strategy with regular full backups and disabling circular logging. Note that changing the circular logging settings will require a restart of the Information Store. 2.1.2.2 Exchange 5.5 Directory Store and Information Store On Exchange 5.5 installations, the following storage groups 2 (databases) must be backed up: Directory Store Information Store: - Private Information Store - Public Information Store 2.1.2.3 Exchange 2000 storage groups Exchange 2000 does not have its own Directory Store. Exchange 2000 allows more storage groups and databases per server than does Exchange 5.5. Up to 4 storage groups are supported per server and as many as 5 databases per storage group are supported. All in all, there may be as many as 20 databases to back up on one server. Transaction logs are shared among databases within the same storage group, and backups should be performed at a storage group level, which is the way TDP for Exchange operates. 2.1.2.4 Site Replication Service and Key Management Service Depending on the setup of your Exchange organization, you may need to backup the auxiliary databases for Key Management Services (KMS) and Site Replication Services (SRS). If Key Management Service is part of your Exchange installation the associated KMS databases are subject to backup too. TDP for Exchange supports backup of Exchange 2000 KMS databases through the Command Line Interface. The Site Replication Service (SRS) is responsible for interfacing Exchange 5.5 with Active Directory and assuring replication of configuration in between Exchange servers in a mixed Exchange environment 3. The SRS database is 2 We use the term storage group not only for Exchange 2000 storage groups, but also for the Exchange 5.5 Information Store and directory. 3 Mixed Exchange environment: Exchange organization containing both Exchange 5.5 and Exchange 2000 servers. Chapter 2. Planning considerations 11
a directory database and to Exchange 5.5 servers it looks as any other Exchange 5.5 directory service though it is an Exchange 2000 database. Because SRS is a directory database, you may choose to back it up on a less regular basis if you have more servers in your Exchange organization. In case you need to restore an SRS database that is not completely up-to-date, other servers will simply backfill the database with the missing updates and make it current. TDP for Exchange supports online backup of the Site Replication Service database. 2.1.2.5 Active Directory and IIS metabase Since Exchange 2000 does not have its own directory but relies entirely on Active Directory (AD) for directory information, a backup plan for Exchange 2000 also includes backup of AD. Backing up Active Directory is part of backing up system objects 4 on Windows 2000 domain controllers. It is not discussed any further in this book. Instead, we recommend that you consult Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141, for information about backing up AD in a TSM environment. Exchange 2000 also takes advantage of services provided by Internet Information Server (IIS). Though a lot of information about IIS setup is duplicated in AD, it is still important to back up IIS as well. TDP for Exchange does not back up IIS. 2.1.3 Backup strategies for Exchange 2000 and 5.5 An Exchange backup generally consists of the database file itself (*.edb and for Exchange 2000 *.stm) and a set of transaction log files (*.log). Some products may allow backups of individual databases within a storage group. TDP for Exchange operates on a storage group level and will only allow backups of the type database copy of individual databases. Since transaction logs are used on a storage group level, we would recommend deploying a strategy involving backups at storage group level, anyway. Backing up databases individually would have a great potential for confusing things, due to the fact that transaction logs work on a storage group level. 4 TSM uses the term system objects. The Microsoft equivalent is system state. 12 Using Tivoli Data Protection for Microsoft Exchange Server
TDP for Exchange supports various types of backups: Full Incremental Differential Copy Database copy (Exchange 2000 only) Your backup strategy, however, will include more than one type of backup in many cases. For instance, it does not make much sense to make incremental or differential backups without any full backups. The chosen strategy will depend on such factors as service level agreements, available storage, and ease of use. The following are various backup strategies: Full backups: A full backup will back up the entire database. If circular logging is disabled the old transaction logs will be deleted upon completion of a successful backup (For Exchange 2000 this is only true if all databases within the same storage group are backed up. TDP for Exchange backs Exchange 2000 databases up on a storage group level.). Scheduling daily full backups is the easiest manageable backup strategy to deploy. It greatly reduces the complexity for doing restores, and it is probably the best solution for many smaller organizations. However, when databases grow too large, or backup hardware is only available for a limited time, it may not be feasible to do full backups every day. To restore from a full backup, only one backup set is needed. Incremental and full backups: An incremental backup will back up transaction logs and purge old transaction log files if all databases sharing the log files are backed up. An incremental backup must be used in conjunction with a full database backup in order to be able to restore the database. Using daily incremental backups along with for instance one weekly full backup is a common scenario if the daily backup window is too short to support full backups or the network capacity is too low. Scheduling the full backup to week-ends or other non-peak hours will in most cases make the increased impact on network bandwidth less critical. For a restore the last full backup as well as all incremental backups since the full backup are needed for a complete database restore. This will, of course, increase the complexity of the restore procedure and make it more time consuming and tedious. This is the main drawback of this strategy. Chapter 2. Planning considerations 13
Differential and full backups: A differential backup will back up transaction logs without purging anything. Thus the differential backup can to some degree logically be understood as a cumulative incremental backup. If differential backups are performed without any full backups in between, the last differential backup will also include the transaction logs already backed up the previous differential backups. In this manner differential backups will require more bandwidth and storage compared to incremental backups performed on the same schedule. A differential backup must be used in conjunction with a full database backup in order to be able to restore the database. For a restore, the last full backup as well as the last differential backup (if newer than the full backup) are needed for a complete database restore. Compared to using a full plus incremental backup strategy, this setup will make any restores faster and less tedious. Copy: A copy backup is a full backup without deletion of any transaction logs. It backs up the entire storage group including transaction logs. A copy backup is used to make a full backup of a storage group without interfering with any deployed strategy involving differential or incremental backups. Database copy: The database copy type backup is available for Exchange 2000 only. It works in the same way as the copy backup, but it operates on individual databases within a storage group. It includes the database files along with the associated transaction logs. Transaction logs are not purged using this type of backup. 2.1.3.1 Deleted item and mailbox retention Exchange has some built-in features that will help in recovering data that has been mistakenly deleted by users or administrators. Deleted items retention can be set up on Information Stores and storage groups in order to keep items in the database for a period after the time that a user requested them deleted. Items will then simply be marked for deletion and hidden to users. The items are recoverable from the client as long as a configurable grace period has not expired. Deleted items retention is available for Exchange 5.5 as well as Exchange 2000, but is disabled by default. 14 Using Tivoli Data Protection for Microsoft Exchange Server
See Figure 3 and Figure 4 for configuration retention settings. Retention settings are normally set on a database level, but it is possible to specify individual settings. Individual settings are specified through the limits tab of the mailbox object on Exchange 5.5. Individual Exchange 2000 settings are specified through the Properties -> Exchange Features -> Storage Limits interface of Active Directory Users and Computers MCC. Exchange 2000 also includes a similar feature for retention of deleted mailboxes.the setting is specified as Keep deleted mailboxes. Like the deleted item retention this feature will keep a mailbox in the database for a period after the owner of the mailbox may have been deleted from Active Directory. Administrators will be able to reconnect an AD user object to the mailbox. The default setting for this feature is to keep mailboxes for 30 days. Figure 3. Setting Item Recovery settings for an Exchange 5.5 Information Store Chapter 2. Planning considerations 15
Figure 4. Setting Deletion settings for an Exchange 2000 database It is important to remember that deleted items retention or deleted mailboxes retention are only remedies for recovering data that actually still exist in the database. There is no way that these features will help if the database crashes or for some reason is not startable. Therefore, these features cannot be used for protection against disasters. See 7.2, Single item and mailbox recovery on page 117 for restore procedures utilizing the deleted item retention feature. 2.1.3.2 Files maintained by Outlook 5 Files maintained by Outlook are not backed up by TDP for Exchange. Backups of these files must be accomplished by using file level backups. Use the TSM Backup Archive Client for backing up these files if it is part of your strategy. 5 We generally consider Outlook as the client for Exchange server. Many other clients do exist, and Outlook is now available in many different versions. 16 Using Tivoli Data Protection for Microsoft Exchange Server
We do not discuss backup of Outlook files in any greater detail, but the following considerations may be helpful: Store pst-files (Personal Folders) and pab-files (Personal Address Book) on file shares, for instance users home drives. Backup the file shares. There is generally no particular need to restore ost-files (Offline Folder Storage). They are easily regenerated from the client. For clients supporting Outlook Address Book (Contacts) instead for Personal Address Books, consider using it. Besides being more elaborate, the Contacts folder is server based and is thus backed up by Exchange server backups. Be aware that backups of the Outlook files may fail due to file locking if a client is connected. Connected clients are not an issue in that respect, when performing online Exchange backups. 2.2 Sizing Typical user question: What is the optimal sizing of my Exchange system? Many factors will influence your decisions on how to configure and set up an Exchange environment. However, the effects of backup and restore time will most likely have great influence on the strategies for the sizes of your Exchange databases. Since the size of Exchange 5.5 and 2000 databases theoretically is limited by hardware only, backup and restore times will probably become bottlenecks before anything else when considering database sizes. As databases grow too large, there will simply not be a service window wide enough to support the required backup times. On Exchange 2000, it may be a very good idea to utilize the possibilities for having more storage groups and more databases. Split data between storage groups and back these up separately. Also, there may be different service level agreements applicable to different users. For instance, there may exist requirements for fast restores for a group of VIPs. Here are our recommendations: Create smaller databases for VIPs in order to support quicker restores and leave standard users on larger databases. However, do not overuse the possibility for creating multiple databases. As the number of databases and storage groups grow, so does administration. Exchange and the Extensible Storage Engine are not built for the purpose of single user databases, so avoid setting these up. Chapter 2. Planning considerations 17
When creating multiple storage groups on a cluster, remember that a single cluster node will only support 4 storage groups in total. Thus creating 3 storage groups on both nodes in a two-node cluster will leave 2 storage groups unmounted if one node fails. On Exchange 5.5, it is not possible to create additional storage groups. If a prolonged backup/restore time is forcing a split of the database, it must be done by setting up a new server. Another option for limiting the growth of the database sizes is to enforce quotas on the individual mailboxes. Limits for mailboxes sizes are set on the database properties page (see Figure 3 on page 15 and Figure 4 on page 16). Unless the TSM server is installed on the same server as TDP for Exchange, network bandwidth constraints may become critical factors to backing up and restoring Exchange. A typical 100-Mbs network equals about 42 GB an hour. That is not considering any overhead and collisions. Expect far less available bandwidth for your backups, and schedule backups for quiet hours. If bandwidth is an issue, running backups across a SAN may be the solution. TDP for Exchange supports the TSM LAN-free environment. In Chapter 5, we illustrate how to get your TDP for Exchange installation to transfer data across a SAN. 2.3 TSM: Preparation for TDP for Exchange The TSM administrator must prepare the TSM server for TDP for Exchange nodes. The preparation involves a number steps: Define and configure policy domain Define and configure a policy set Define and configure a management class Define and configure copy groups Assign the default management class to the domain Activate the policy Register TDP for Exchange node(s) 2.3.1 Policies and management classes Tivoli Storage Manager policies are used to specify how objects are backed up and migrated. 18 Using Tivoli Data Protection for Microsoft Exchange Server
The TDP for Exchange version 2.2 conventions for backup objects and file space naming (see Appendix G) differ from version 1. Version 2.2 supports the automatic policy based expiration capabilities provided by the TSM server, and there is no need to request expiration of backup objects from the client anymore. All backup objects are stored in backup storage pools by TDP for Exchange. It is therefore not necessary to setup an archive copy group. An archive copy group can exist, and we did define one, even though was is not being used. We did so just to avoid some warning messages appearing in case the archive copy group did not exist. For instance, an activation of a policy would provoke a warning like this: tsm: BRAZIL>activate policyset TDPEXCH2_DOMAIN standard ANR1554W DEFAULT Management class API_DISK_30DAYS in policy set TDPEXCH2_DOMAIN STANDARD does not have an ARCHIVE copygroup: files will not be archived by default if this set is activated. For our TDP for Exchange installation, we defined the policy domain TDPEXCH2_DOMAIN and the management class API_DISK_30DAYS for the STANDARD policy set. For the API_DISK_30DAYS management class, we defined the copy groups of type backup and archive. As mentioned, only the first one is actually used. We decided using the following parameters for our copy group in our default management class: Versions Data Exists: No limit Versions Data Deleted: No limit Retain Extra Versions: 30 days Retain Only Version: 30 days The rationale was to keep old backups for 30 days before they were expired and removed from TSM storage. Specifying no limit for the Version Data Exists and Version Data Deleted parameters assured that repeated backups in our test environment would not flush relatively new backups just because of exceeding a version limit. Incremental backups are always named uniquely. Therefore, they will only expire due to Retain Only Version limits. When performing a full backup, all objects for the Exchange storage group are inactivated and after that subject to expiration. Whereas a full backup normally will expire due to limitations set by Retain Extra Versions (assuming an unlimited number of versions), the incremental backups will expire from limits set by Retain Only Version. Chapter 2. Planning considerations 19
The value for Retain Only Version for incremental backups must be, at minimum, as long as the value for the associated full backup. On the other hand, it does not make much sense to keep transaction logs if the associated full backup has expired and has been removed from TSM storage. We ended up specifying equal limits for Retain Only Version and Retain Extra Versions: 30 days. The destination for our backups is disk (API_DISK). If using removable media, it is recommended to use collocation if a restore potentially involves more than just a full backup for instance, a differential or multiple incremental backups. The following parameters are not applicable for TDP for Exchange, and default values must be accepted: Copy mode Copy serialization Copy frequency Here is an example of setting up management classes on the TSM server: tsm: BRAZIL>define domain TDPEXCH2_DOMAIN ANR1500I Policy domain TDPEXCH2_DOMAIN defined. tsm: BRAZIL>define policyset TDPEXCH2_DOMAIN standard ANR1510I Policy set STANDARD defined in policy domain TDPEXCH2_DOMAIN. tsm: BRAZIL>define mgmtclass TDPEXCH2_DOMAIN standard API_DISK_30DAYS ANR1520I Management class API_DISK_30DAYS defined in policy domain TDPEXCH2_DOMAIN, set STANDARD. tsm: BRAZIL>define copygroup tdpexch2_domain standard api_disk_30days type=backu p dest=api_disk verexists=nolimit retextra=30 verdeleted=nolimit retonly=30 ANR1530I Backup copy group STANDARD defined in policy domain TDPEXCH2_DOMAIN, set STANDARD, management class API_DISK_30DAYS. tsm: BRAZIL>define copygroup tdpexch2_domain standard api_disk_30days type=archi ve dest=api_disk retver=30 ANR1535I Archive copy group STANDARD defined in policy domain TDPEXCH2_DOMAIN, set STANDARD, management class API_DISK_30DAYS. tsm: BRAZIL>assign defmgmtclass TDPEXCH2_DOMAIN standard API_DISK_30DAYS ANR1538I Default management class set to API_DISK_30DAYS for policy domain TDPEXCH2_DOMAIN, set STANDARD. 20 Using Tivoli Data Protection for Microsoft Exchange Server
2.3.2 Node registration When policy sets and management classes have been configured, it is time to register the node. We decided to use nodenames indicating the particular node as being a TSM Exchange API node. We used the naming template ExchangeServerName_EXCH2. tsm: BRAZIL>register node ELBRUS_EXCH2 uphi domain=tdpexch2_domain backdelete =yes maxnummp=2 ANR2060I Node ELBRUS_EXCH2 registered in policy domain TDPEXCH2_DOMAIN. ANR2099I Administrative userid ELBRUS_EXCH2 defined for OWNER access to node ELBRUS_EXCH2. In this manner we left the server name itself to be used as a nodename for any TSM Backup Archive installation. 2.4 TDP for Exchange v.1 and v.2: differences and coexistence The TDP for Exchange version 2 conventions for backup objects and file space naming are different from version 1 6. This means that the versions are completely incompatible, and it is not possible to query or restore backups made by the earlier version. It is therefore necessary to keep your installation of TDP for Exchange v.1 as long as you are storing backup objects created by this version and you want to be able to restore these. You can still install version 2 and start using it at the same time. The new version will not overwrite the old one. TDP for Exchange version 2 supports Exchange 5.5 and Exchange 2000. If support for Exchange 5.0 is needed, TDP for Exchange version 1 must be used. We did not install version 1, but it is recommended by the installation guide for version 2 that you set up different node names for version 1 and version 2. If using the same nodename, the INCLUDE option in the dsm.opt file must be used to bind TDP for Exchange version 1 objects and TDP for Exchange version 2 objects to different management classes. Otherwise, a malconfigured setup may result in unforeseen removals of backups from TSM or leaving backups forever without any expiration. 6 TDP for Exchange v.1 was initially named ADSMConnect Agent for Microsoft Exchange server Chapter 2. Planning considerations 21
Note Do not use TDP for Exchange v.1 and TDP for Exchange v.2 to back up the same database. Doing so may mess up the transaction log backups. Start using the new version, and leave only the old version, in order to support any possible restores of old backups. 2.5 How TDP for Exchange stores objects on the TSM server As mentioned, TDP for Exchange version 2 stores backup objects on the TSM server differently from the previous version. Objects are stored using the following pattern: Filespace name: ExchangeServerName\StorageGroupName High-level qualifier: \ObjectKeyword[\ObjectIndex][\DatabaseName] where ObjectKeyword is: meta, data, or logs and ObjectIndex is: xxxx (xxxx th file within database data object only. For instance, there will be ObjectIndex 0000 and 0001 for every mailbox store reflecting the existence of the.edb and.stm file) or yyyymmddhhmmss (timestamp) for incremental backups. Metadata is data containing information about a particular backup. The data keyword specifies the database files themselves and the logs keyword specifies backup of transaction log files. Low-level qualifier: \Type where Type is: full, copy, diff, incr, or dbcopy depending on what kind of backup is performed. Knowledge about object names is valuable when querying the TSM server for information about backups. Below we show some examples on viewing objects in TSM database. 22 Using Tivoli Data Protection for Microsoft Exchange Server
Query the backups table using the TSM administrator client: tsm: BRAZIL>select * from backups where node_name='elbrus_exch2' and state='acti VE_VERSION' and filespace_name='elbrus\itso SG' and hl_name like '%ITSO 6148%' ANR2963W This SQL query may produce a very large result table, or may require a significant amount of time to compute. Do you wish to proceed? (Yes (Y)/No (N)) y NODE_NAME: ELBRUS_EXCH2 FILESPACE_NAME: ELBRUS\ITSO SG STATE: ACTIVE_VERSION TYPE: FILE HL_NAME: \data\0000\itso 6148 Mailbox Store\ LL_NAME: full OBJECT_ID: 107084 BACKUP_DATE: 2001-04-06 13:43:26.000000 DEACTIVATE_DATE: OWNER: CLASS_NAME: DEFAULT NODE_NAME: ELBRUS_EXCH2 FILESPACE_NAME: ELBRUS\ITSO SG STATE: ACTIVE_VERSION TYPE: FILE HL_NAME: \data\0001\itso 6148 Mailbox Store\ LL_NAME: full OBJECT_ID: 107085 BACKUP_DATE: 2001-04-06 13:43:26.000000 DEACTIVATE_DATE: OWNER: CLASS_NAME: DEFAULT Notice that there are two data objects for this backup: one object for the.edb file and one for the.stm file. Another option is to use the show versions command through the administrative client. The format is: show versions <node_name> <file_spacename> tsm: BRAZIL>show versions ELBRUS_EXCH2 "ELBRUS\ITSO SG". ELBRUS\ITSO SG : \data\0000\itso 6147 Mailbox Store\ full (MC: DEFAULT) Inactive, Inserted 04/05/01 22:44:59, Deactivated 04/06/01 09:53:18 ObjId: 0.106345 ELBRUS\ITSO SG : \data\0000\itso 6147 Mailbox Store\ full (MC: DEFAULT) Inactive, Inserted 04/06/01 09:53:18, Deactivated 04/06/01 13:43:26 ObjId: 0.106826 Chapter 2. Planning considerations 23
24 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 3. Installation of TDP for MS Exchange servers Tivoli Data Protection for Microsoft Exchange (TDP) performs online backups of Microsoft Exchange server databases to Tivoli Storage Manager (TSM) storage. TDP for Exchange must be installed on the same machine as the Microsoft Exchange server. TDP for Exchange Version 2 supports Microsoft Exchange Server 5.5 and Microsoft Exchange 2000 Server. 3.1 TDP for Exchange requirements Before installing Tivoli Data Protection for Microsoft Exchange server, you must be sure that your system meets the following requirements: Hardware requirements: - 8 MB of free disk space - 48 MB of RAM (96 MB or more is highly recommended) - Intel Pentium or equivalent 166 (or higher) processor - Cluster requirements see Microsoft requirements for installing Exchange in Cluster environment Operating system requirements: Microsoft Windows NT Server (Server or Enterprise Edition) Version 4 with Service Pack 4 (SP4) or Microsoft Windows 2000 Server (Server, Advanced Server, Datacenter Server) with Service Pack 1 (SP1) or later. It is recommended that you install the latest Windows service packs available from Microsoft. In our test environment we installed both Exchange 5.5 (SP4) and Exchange 2000 over Windows 2000 with Service Pack 1. TDP for Exchange supports the following communication protocols: TCP/IP, IPX/SPX, NetBIOS, Named Pipes (only for connection from TDP for Exchange to TSM), LU 6.2(CPIC), Lan free. We set up our environment to run on TCP/IP. If you are planning to use it LAN-free, you must use TCP/IP. Systems supported by TDP for Exchange version 2: - Exchange Server 5.5 (Windows NT 4.0 with SP4 or later and Windows 2000 with SP1 or later). - Exchange 2000 Server (Windows 2000 with SP1 or later). Copyright IBM Corp. 2001 25
- MSCS Active/Passive Configuration Exchange server 5.5 with SP3 (Windows NT 4.0 Enterprise Edition with SP4 or later or Windows 2000 Advanced Server with SP1 or later). - MSCS Active/Active Configuration Exchange 2000 Server (Windows 2000 Advanced Server with SP1 or later). In our test environment we installed Microsoft Exchange 2000 in a MSCS cluster. Also, consider the following issues: The TSM server can reside on a different machine than TDP for Exchange and can be on any platform supported by TSM. In our lab environment we used a TSM server running AIX on RS/6000. If you want to use TSM Scheduling you must install the TSM Backup/Archive Client for Windows. The TSM Backup/Archive Client must reside on the same machine as TDP for Microsoft Exchange server. Microsoft Internet Explorer V4.01 or later for the access to the online information. You can obtain the latest requirements for TDP for Exchange from the following URL: http://www.tivoli.com/products/solutions/storage There are a number of hotfixes to Exchange 2000 that are important. You should check the hotfix list for Exchange 2000. Active/Passive is also supported for Exchange 2000. 3.2 How to Install the TDP Agent This section gives you information how to install TDP for Exchange in a non-clustered environment, how to install TDP Agent in a clustered environment, how to perform silent installation, and how to install the Backup/Archive Client in order to take advantage of the TSM Scheduler. 3.2.1 Installing TDP for Exchange Follow the Microsoft requirements and instructions for installing Microsoft Exchange, and be sure that you use the latest service packs available. In our lab environment, we set up two Exchange servers Exchange 5.5 with SP4 and Exchange 2000, both of them on Windows 2000 with SP1. 26 Using Tivoli Data Protection for Microsoft Exchange Server
Before performing the installation, see the readme1st.txt file which includes useful information about installing and configuring TDP for Exchange. Make sure you are logged to the system with an account having administrator privileges to the local system. Follow these steps to install TDP for Exchange: 1. Insert the TDP for Exchange CD ROM into the CD-ROM drive. If you have the autorun feature enabled, the setup will start as soon as you insert the CD into the drive. If autostart is not enabled: a. Select Run from the Start menu. b. Enter x:\setup where x is your CD-ROM drive letter. c. Click OK to start the installation program. 2. Follow the installation instructions contained in the prompt windows. If no previous version of TDP for Exchange exists on the system, the default installation directory is ProgramFiles\Tivoli\TSM\TDPExchange. You may override it and specify a different installation directory (Figure 5). Figure 5. Specifying an installation path Chapter 3. Installation of TDP for MS Exchange servers 27
However, installing all TSM products into the same base directory is recommended. If the Tivoli Storage Manager product is detected, the path to that product becomes the default installation directory. 3. If you would like to register the TDP for Exchange, check the box provided for registration, and then fill in the form represented in Figure 6. Figure 6. TDP for Exchange registration 4. Click Finish to complete the setup. If TDP for Exchange Version 2 already exists on the system, you can Repair or Remove the previously installed TDP for Exchange Version 2. By choosing Repair you will fix missing or corrupt files, but your configuration will remain intact. By choosing Remove you will have the option to remove the current installation. The other way to remove TDP for Exchange installation is to point to Control Panel -> Add/Remove Programs and then choose Tivoli Data Protection for Microsoft Exchange Server - V2 and click Remove. You should also check the hotfix list for Exchange 2000. 28 Using Tivoli Data Protection for Microsoft Exchange Server
3.2.2 Registering TDP for Exchange with a TSM server Before you can perform backup and restore with TDP for Exchange, your TSM administrator must register TDP for Exchange as a client node with the server. The administrator will provide the node name, the initial password, the communication method to connect to the TSM server, the policy domain to which TDP for Exchange belongs, TSM schedules and whether you are allowed to use compression before sending files to server. (Note that the TSM administrator can override your preferences about compression specified in your options file). See 2.3, TSM: Preparation for TDP for Exchange on page 18 regarding node registration on the TSM server. 3.2.3 The TDP for Exchange options file After registering TDP for Exchange to the TSM server, you must configure several parameters in the options file. The default options file name is dsm.opt and it is stored in the TDP for Exchange directory. You can edit this file using a text editor. You will have to specify the following parameters: NODename xxx The unique name which the TSM administrator has registered. The TSM server name The name of the TSM server. (TCPserveraddress or IPXServeraddress or NETBIOSServername; if you use TCPserveraddress specify IP address or Host name.) Communication Options TDP supports the following communication protocols TCP/IP, IPX/SPX, NetBIOS, Named Pipes. You may specify the following additional options: PASSWORD Access If this option is set to generate the TSM API stores the password (encrypted) in the Windows registry and automatically generates the new password when the current one expires. Be aware that if this option is set to prompt your backup may fail because of an expired password. COMPRESSion You may use this option to compress data before sending it to the TSM server. However, this will lead to higher CPU utilization on the machine where TDP for Exchange is installed. On the other hand, this will cause less network traffic and less storage space on the TSM server. The TSM administrator s settings on the TSM server takes precedence over your settings in the options file and he or she may enforce you to always use compression, never use compression or leave this decision up to you. enablelanfree If yes you may run TDP for Exchange in a LAN free environment. Chapter 3. Installation of TDP for MS Exchange servers 29
3.3 Installing TDP for Exchange in an MSCS environment The procedure for installing TDP for Exchange in a clustered environment is the same as installing it in a non-clustered environment. Install TDP for Exchange on both nodes of the cluster. Make sure that the option files on both nodes of the cluster are identical. You must specify the CLUSTERnode parameter in the options file to be yes for TDP for Exchange to function on the cluster. Also create the new Start menu shortcut so that the GUI is invoked by specifying the /exchserver parameter. To do that, either point to Start -> Settings -> Taskbar and Start Menu Properties, click the Advanced tab and then the Advanced command or browse to \Documents and settings\all users\start Menu\Programs\Tivoli Storage Manager\TDP for MS Exchange. Then choose New Shortcut by right-clicking with the mouse. In the field Type the location of the item specify the location of the tdpexc.exe with the parameter /excserver=your_server or click Browse to find this file and then add the /excserver=your_server parameter. The location of the file is Program files\tivoli\tsm\tdpexchange. If you right-click the created shortcut, you will see the screen shown in Figure 7. 30 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 7. Properties for the shortcut for GUI The option name is "/EXCSERVER". 3.4 Silent installation Silent installation is extremely useful when you want to perform installation of TDP for Exchange on several of identical machines because administrators do not have to provide input to dialog boxes and specify TDP for Exchange parameters. Chapter 3. Installation of TDP for MS Exchange servers 31
If you want to perform the silent installation, you have the following options: Use the command line setup program with s (silent) and v switches: - Use setup /s /v/qn from the command line to install in the default directory. Issue this command from the TDPExchange subdirectory. - Use setup /s /v INSTALDIR=\ X:\Desired Install Path\ /qn to install to the specified directory. Make sure you use quotes if your installation path includes spaces and place a backslash (\) in front of each quote mark that is within an outer set of quotes. Also, there cannot be a space between the command-line option (/v) and the arguments that you are passing. Create a batch file with desired parameters (Create this file with Notepad and save it as setup.bat file). The following example shows the sample script: rem=================================================== rem silent install script rem cd.\tdpexchange.\setup /s /v INSTALDIR=\ X:\Desired Install Path\ /qn rem rem replace the option file copy dsm.opt X:\Desired Install Path rem=================================================== The silent installation package may reside on a file server, or you may choose to burn a special CD and distribute it for this purpose. This package contains the TDP for Exchange code distribution files and usually a batch file for silent installation. If you use a silent install package on a CD and autostart is enabled, the installation will begin after inserting the CD into the drive (do not forget to let the autorun.inf file point to your setup.bat file). If autostart is not enabled, you may run the silent installation by activating the setup.bat file from the root of the CD. If the package is placed on the file server and you want to perform the silent installation from another machine, you must execute the command: net use x:\\machine1\silent_installation where machine1 is the file server and Silent_installation is the shared directory containing the silent installation package. No visual cues exist to inform you about the end of the installation. If the silent installation fails, you can create a detailed log file of installation by typing: setup /v /l*v setup.log. 32 Using Tivoli Data Protection for Microsoft Exchange Server
3.5 Installing the Backup/Archive client If you want to take advantage of TSM Scheduler, you must install the Backup/Archive Client on the same machine on which you have installed TDP for Exchange. Make sure you are logged on using a Windows account with administrative privileges. To install the Backup/Archive Client: 1. Insert the CD-ROM containing the TSM Windows Client into your CD-ROM drive. 2. Start the setup program by selecting Run from the Start menu. 3. Click OK. 4. Follow the instructions displayed on the screen. You can choose between two setup types: - Complete This setup gives you the Backup/Archive Client, the API, and the Web Client. Use the custom option if you want to install the Administrative client. - Custom This setup allows you to select the desired options. You must use this option if you want to install the Administrative client the program which lets administrators monitor and control TSM servers using TSM administrator commands. If you select to install the Backup/Archive client and the administrative client, they must reside in a single directory and will share the same options file. Make sure there is enough disk space for the TSM Client files on the destination drive. 5. Click on Finish once the installation process completes. For current installation and configuration information, refer to the README file that is shipped on the product installation media. For current information concerning TSM, see: http://www.tivoli.com/support/storage_mgr/tivolimain.html Chapter 3. Installation of TDP for MS Exchange servers 33
34 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 4. Backing up Exchange databases TDP for Exchange performs backups of Exchange storage groups on TSM server a storage group being an Exchange 5.5 Directory, an Exchange 5.5 Information store or an Exchange 2000 Storage group. The backup includes databases and associated transactions logs. TDP for Exchange communicates with the TSM server using the TSM application programming interface (API) and with the Exchange server using the Exchange API see Figure 1 on page 8. TDP for Exchange must be able to connect to a TSM server. The TSM server can run on the same machine as TDP for Exchange or on a different machine on any supported operating platform. In our lab environment we set up two Exchange servers Exchange 5.5 and Exchange 2000 both of them running on the Windows 2000 platform. First we installed Exchange 5.5. After that we installed Exchange 2000 joining the Exchange 5.5 site, and we set up a Site Replication Service between them. We set up our environment in this way in order to be close to a common scenario of migrating from Exchange 5.5 to Exchange 2000. We also installed Exchange 2000 in a cluster environment. We used a different machine for the Domain controller. (See Figure 35 on page 133.) 4.1 Exchange 5.5 DIR and IS backup general procedures You can perform backup of the Exchange 5.5 Directory and Information store by using the Graphical User Interface (GUI) or using the Command Line Interface (CLI). 4.1.1 Backing up Exchange 5.5 using the GUI To start the TDP for Exchange GUI point to Start -> Programs, then Tivoli Storage manager -> TDP for MS Exchange Server - v2 and click Exchange Client GUI. You will see the window represented in Figure 8. Copyright IBM Corp. 2001 35
Figure 8. TDP for Microsoft Exchange 5.5 Server GUI The left pane in Figure 8 represents the hierarchical Exchange organization as follows: UPHI is the organization, SJ is the site, Shasta is the Exchange 5.5 server. Notice that the GUI tree view changes with each tab selected. You have the options to perform backup of the Directory Store or Information Store, or both. Check what you want to back up, as shown in Figure 9. 36 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 9. Backup of Exchange 5.5 Directory and Information Store The type of the backup can be full, incremental, differential or copy. You can choose the type of the backup from the right pane of the TDP for Exchange window. The Database Copy backup is inactive here because it is valid only for Exchange 2000. If you choose full backup, the databases and the associated transaction logs will be backed up. After finishing the backup, the log files are deleted. The full backup inactivates all previous backups. By choosing incremental backup, only the transaction logs will be backed up. After finishing the backup, the log files are deleted. If you choose differential backup, only the transaction logs will be backed up. However, after finishing the backup, the log files are not deleted. The differential backup inactivates the previous differential backup. You can choose the copy backup to perform a full backup of the Exchange server without affecting any backup procedures that use incremental or differential backups. For a detailed explanation of different backup strategies, see 2.1.3, Backup strategies for Exchange 2000 and 5.5 on page 12. Chapter 4. Backing up Exchange databases 37
Note If circular logging is enabled, you cannot perform differential or incremental backups, because the log may become wrapped before an incremental or differential backup takes place. So, if you want to perform differential or incremental backups, you can disable circular logging from the Exchange Administrator program. 4.1.1.1 Configuration settings You can adjust several parameters concerning configuration settings by selecting Edit and then Configuration from the TDP for Exchange GUI. Figure 10 shows the screen you will see. Figure 10. Configuring settings general tab These parameters pertain to the operation of the TDP for Exchange GUI. By using command line invocation, you can override the values specified in this file for the current invocation, but the values will not be changed unless you use tdpexcc set command to change them. Wait for Tape Mounts for Backup or Restore This parameter is valid when the TSM server is configured to store the backup data on tape media. If it is checked, TDP for Exchange will wait for the media mount during the backup or restore process. If it is unchecked, the current operation will stop. The default setting for this parameter is checked, as shown in Figure 11. 38 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 11. Configuration settings performance tab TDP Buffers This parameter shows the number of buffers which TDP for Exchange uses when transferring data from Exchange server to TSM server. The default value is 3. The maximum number of the buffers is 8. TDP for Exchange is a multi-threaded application that uses asynchronous execution threads to transfer data between the Exchange servers and TSM servers. To accomplish this, multiple data buffers are used to allow one thread to receive data from one side, while another thread sends data to the other side. TDP Buffers size This parameter specifies the size of TDP buffers. Figure 12 shows the Configuration settings logging tab. Figure 12. Configuration settings logging tab Chapter 4. Backing up Exchange databases 39
Log File Name The name of the log file containing TDP for Exchange information. The default name is tdpexc.log. If you specify the name of a non-existent file, a new one will be created. You may specify the directory where this file is located. If you do not specify a directory, then the directory in which TDP for Exchange is installed is used. Prune Old Entries Check this box to prune old entries. Keep Old Log Entries For Last Days Defines for how many days the log entries will stay in the activity log. We recommend using a default value of 60 days or higher. If Prune Old Entries is unchecked, the entries older than this value will not be pruned. Prune Now Button Click if you want to prune the activity log immediately. Figure 13 shows the Configuration settings regional tab. Figure 13. Configuration settings regional tab Date Format Specifies the date format you want to use. Time Format Specifies the desired time format. Number Format Specifies the number format. 4.1.2 Backing up Exchange 5.5 using the Command Line Interface If you want to use the Command Line Interface point to Start -> Programs, then Tivoli Storage manager -> TDP for MS Exchange Server - v2 and click Exchange Client Cmd.line. The name of the TDP for Exchange Command Line Interface is tdpexcc.exe. and you can find it in the directory where TDP for Exchange is installed. 40 Using Tivoli Data Protection for Microsoft Exchange Server
4.1.2.1 The CLI syntax The format of this command is as follows: TDPEXCC BACKup * DIR IS sgname1,...,sgnamen backuptype where backuptype can be: FULL COPY INCRemental DIFFerential DBCopy dbname [/BUFFers=numbuffers] (default: 3) [/BUFFERSIze=buffersize] (default: 1024) [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/EXCSERVer=servername] (default: local exchange server) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) [/MOUNTWait=Yes No] (default: Yes) [/Quiet] [/TSMNODe=nodename] [/TSMOPTFile=dsm.opt filename] (default: dsm.opt) [/TSMPassword=password] Positional parameters do not include a slash (/). Optional parameters are included in brackets and can appear in any order after the positional ones. The separation characters between parameters are spaces. Parameters which require a value are followed by an equal sign and a value. If a parameter that may have a value is not present, then the value in *.cfg file is used. If it is present without a value, then the original default value is used. If it is present with a value, then that value is used. Upper case is used for showing the minimum abbreviations for keywords. 4.1.2.2 Positional parameters * DIR IS Use these parameters to specify what to back up: * Use this parameter to back up the Directory Store and the Information Store sequentially. DIR Use this parameter to back up only the Directory Store. IS Use this parameter to back up only the Information Store. FULL COPY INCRemental DIFFerential FULL Performs full backup, and after completion, deletes transaction logs. COPY Performs full backup without affecting transaction logs. INCRemental Backs up only logs, and after completion of the backup process, deletes them. DIFFerential Backs up only log files without deleting them. Chapter 4. Backing up Exchange databases 41
For example, tdpexcc backup * full performs a full backup of Exchange server. The output is shown here: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup * full Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning full backup of Directory, 1 of 2. Full: 0 Read: 8405146 Written: 8405146 Rate: 997.47 Kb/Sec Backup of Directory completed successfully. Beginning full backup of Information Store, 2 of 2. Full: 0 Read: 9470205 Written: 9470205 Rate: 1,001.76 Kb/Sec Backup of Information Store completed successfully. Expiring backup [SHASTA\Information Store], [copy] Expiring backup [SHASTA\Information Store], [incr] Expiring backup [SHASTA\Directory], [copy] Expiring backup [SHASTA\Directory], [diff] Total storage groups requested for backup: 2 Total storage groups backed up: 2 Total storage groups expired: 4 Total storage groups excluded: 0 Throughput rate: 996.77 Kb/Sec Total bytes transferred: 17,875,351 Elapsed processing time: 17.51 Secs C:\Program Files\Tivoli\TSM\TDPExchange> You can see that after performing the full backup, the previous backups are automatically expired. The following example shows the incremental backup of an Exchange 5.5 Directory: 42 Using Tivoli Data Protection for Microsoft Exchange Server
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup DIR INCRemental Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning incr backup of Directory, 1 of 1. Full: 0 Read: 10485869 Written: 10485869 Rate: 954.25 Kb/Sec Backup of Directory completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 952.04 Kb/Sec Total bytes transferred: 10,485,869 Elapsed processing time: 10.76 Secs C:\Program Files\Tivoli\TSM\TDPExchange> The next example shows the output of a differential backup of an Exchange 5.5 Information Store: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup IS DIFFerential Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning diff backup of Information Store, 1 of 1. Full: 0 Read: 10485869 Written: 10485869 Rate: 954.97 Kb/Sec Backup of Information Store completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 952.75 Kb/Sec Total bytes transferred: 10,485,869 Elapsed processing time: 10.75 Secs C:\Program Files\Tivoli\TSM\TDPExchange> Chapter 4. Backing up Exchange databases 43
This last example shows the output of a copy backup of the entire Exchange 5.5 server: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup * COPY Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning copy backup of Directory, 1 of 2. Full: 0 Read: 8405146 Written: 8405146 Rate: 995.29 Kb/Sec Backup of Directory completed successfully. Beginning copy backup of Information Store, 2 of 2. Full: 0 Read: 9470205 Written: 9470205 Rate: 1,002.85 Kb/Sec Backup of Information Store completed successfully. Total storage groups requested for backup: 2 Total storage groups backed up: 2 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 996.77 Kb/Sec Total bytes transferred: 17,875,351 Elapsed processing time: 17.51 Secs C:\Program Files\Tivoli\TSM\TDPExchange> 4.1.2.3 Optional parameters The interpretation of the most optional parameters is presented in 4.1.1.1, Configuration settings on page 38. However, there are some additional options: By using the Command Line Interface, you can specify the desired Exchange server to be backed up. By using the GUI, you specify the server from the hierarchal Exchange organization presented in the left pane of the window. You can also specify the /quiet option here to prevent displaying of status information. You can specify the TSM node name for the current command (/TSMNODe=tsmnodename), which will override the value for the node in the TSM options file if PASSWORDACCESS is set to PROMPT. You may specify the tsmoptionfilename (/TSMOPTFile=tsmoptfilename). The file can include a full path name. Important: Make sure that if the full path name includes spaces, you have put it in double quotes. 44 Using Tivoli Data Protection for Microsoft Exchange Server
You can specify the tsmpassword (/TSMPassword=tsmpassword) which TDP for Exchange uses to log on to the TSM server. For more information about this parameter, refer to Chapter 4 of Tivoli Data Protection for Microsoft Exchange Server Installation and User s Guide. 4.2 General procedures for backing up Exchange 2000 This section contains information about procedures for backing up Exchange 2000. The backup of Exchange 2000 utilizes parallel backups by allowing multiple backup sessions of different storage groups at the same time. In order to perform parallel backups, you must run multiple instances of the CLI or GUI. 4.2.1 Backing up Exchange 2000 using the GUI The backup of Exchange 2000 using the GUI is similar to the backup of Exchange 5.5 (see 4.1.1, Backing up Exchange 5.5 using the GUI on page 35). After invoking the GUI, you will be presented with the interface illustrated in Figure 14. Figure 14. TDP for Microsoft Exchange 2000 GUI Chapter 4. Backing up Exchange databases 45
In the left pane of this window you can see that Exchange server ELBRUS is a member of domain uphi.sky and contains two storage groups: First Storage Group and ITSO SG. The First Storage Group contains two databases Mailbox Store (ELBRUS) and Public Store (ELBRUS). The ITSO SG storage group includes only one database ITSO 6147 Mailbox Store. (As with Exchange 5.5, here again the GUI tree view changes with each tab selected). You can perform backup of one of these storage groups, or both. The difference from Exchange 5.5 is that here you can perform a special backup, database copy, which gives you the opportunity to back up only the selected databases and associated transaction logs without affecting any incremental or differential backup processes. For information about configuration settings, refer to 4.1.1.1, Configuration settings on page 38. For Exchange 2000 you have an additional option to specify the temporary path for restoring logs and patch files (Figure 15). If you do not select such a path, the default is used. Before a full copy or database copy restore occurs, TDP for Exchange will delete any residual log files in the temporary directory. Figure 15. Configuration settings for Exchange 2000 Type the Temporary Log Restore Path or click Browse to choose it. Note Do not set this path to be the current Exchange storage group transaction log directory or there could be unpredictable results. 46 Using Tivoli Data Protection for Microsoft Exchange Server
When backing up Exchange 2000, you must keep in mind that if one database from a storage group is dismounted or corrupted, you cannot perform full or copy backup of the storage group which contains this database. However, you can perform differential, incremental, and database copy backup. If you try to perform backup of an entire Information Store, only the storage groups which do not contain dismounted databases will be backed up. That is because all the databases in the storage group share the same transaction log files, and after performing a full backup, the transaction log files are deleted. So, if for any reason one database is not mounted or is corrupted, the full backup will not take place, and the transaction log files will not be deleted. 4.2.2 Backing up Exchange 2000 using the CLI You can perform backup of Exchange 2000 by using the Command Line Interface. Follow the instructions given in 4.1.2, Backing up Exchange 5.5 using the Command Line Interface on page 40 for invoking the Command Line Interface. The difference from Exchange 5.5 is that here you can back up storage groups instead of the Directory or Information Store, and you can perform Database Copy Backups (which are described in the previous section). The format of the command is shown below: TDPEXCC BACKup * sgname1,...,sgnamen backuptype where backuptype can be: FULL COPY INCRemental DIFFerential DBCopy dbname [/BUFFers=numbuffers] (default: 3) [/BUFFERSIze=buffersize] (default: 1024) [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/EXCSERVer=servername] (default: local exchange server) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) [/MOUNTWait=Yes No] (default: Yes) [/Quiet] [/TSMNODe=nodename] [/TSMOPTFile=dsm.opt filename] (default: dsm.opt) [/TSMPassword=password] For additional information concerning parameters, see 4.1.2.2, Positional parameters on page 41 and 4.1.2.3, Optional parameters on page 44. Chapter 4. Backing up Exchange databases 47
If you want to perform a full backup of all Exchange storage groups, type: tdpexcc * full. The output of this command is: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup * full Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning full backup of First Storage Group, 1 of 2. Full: 0 Read: 25216128 Written: 25216128 Rate: 1,035.10 Kb/Sec Backup of First Storage Group completed successfully. Beginning full backup of ITSO SG, 2 of 2. Full: 0 Read: 10510940 Written: 10510940 Rate: 1,003.87 Kb/Sec Backup of ITSO SG completed successfully. Total storage groups requested for backup: 2 Total storage groups backed up: 2 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 1,022.95 Kb/Sec Total bytes transferred: 35,727,068 Elapsed processing time: 34.11 Secs E:\Program Files\Tivoli\TSM\TDPExchange> 48 Using Tivoli Data Protection for Microsoft Exchange Server
If you want to perform a backup of a storage group and the name of the storage group contains spaces, you must put it in double quotes. Be sure that you use the correct case for the name of the Storage Group. Here is an example of the output of a backup of First Storage Group only: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup "First Storage Group" full Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning full backup of First Storage Group, 1 of 1. Full: 5 Read: 5251262 Written: 3145728 Rate: 268.30 Kb/Sec Waiting for TSM server... Full: 0 Read: 19973146 Written: 19973146 Rate: 381.08 Kb/Sec Backup of First Storage Group completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 379.90 Kb/Sec Total bytes transferred: 19,973,146 Elapsed processing time: 51.34 Secs E:\Program Files\Tivoli\TSM\TDPExchange> Chapter 4. Backing up Exchange databases 49
If you want to perform a backup of a database and the name of the database has spaces in it, put the name in double quotes. The next screen shows the output of the DBcopy backup of the database ITSO 6147 Mailbox Store: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup "ITSO SG" DBCopy "ITSO 6147 Mailbox Store" Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning dbcopy backup of storage group <ITSO SG>, database <ITSO 6147 Mailbox Store>, 1 of 1. Full: 0 Read: 12608092 Written: 12608092 Rate: 1,004.04 Kb/Sec Backup of ITSO SG completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 1,003.06 Kb/Sec Total bytes transferred: 12,608,092 Elapsed processing time: 12.28 Secs Keep in mind that you must use the correct case. 4.2.3 Backing up Site Replication Service In our lab environment, we first set up an Exchange 5.5 site, and then we installed Exchange 2000 by joining the existing 5.5 site. Exchange 2000 can coexist with Exchange 5.5 if replication between Active Directory and Exchange 5.5 takes place. Prior to installation of Exchange 2000, we installed an Active Directory Connector and configured one user connection agreement, which connects the Active Directory forest to the Exchange Server 5.5 directory. Site Replication Services (SRS) is installed automatically with the Exchange 2000 installation if you join an existing Exchange 5.5 site. SRS interchanges directory information between the Exchange 5.5 directory service and Active Directory. The SRS database is identical to other Exchange 2000 databases and therefore it shares the same rules for backup and restore. 50 Using Tivoli Data Protection for Microsoft Exchange Server
Be aware that the SRS backup is available only from the command line. The service must be running to perform backups. The syntax of the command is: tdpexcc backup SRS Storage full /EXCAPPlication=srs tdpexcc backup SRS Storage incr /EXCAPPlication=srs tdpexcc backup SRS Storage diff /EXCAPPlication=srs tdpexcc backup SRS Storage copy /EXCAPPlication=srs The output of performing the full backup of SRS is: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup "SRS Storage" full /EXCAPPlication=srs Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting storage group backup... Beginning full backup of SRS Storage, 1 of 1. Full: 0 Read: 7356714 Written: 7356714 Rate: 819.47 Kb/Sec Backup of SRS Storage completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 814.08 Kb/Sec Total bytes transferred: 7,356,714 Elapsed processing time: 8.83 Secs You can use the Command Line Interface or Graphical User Interface to restore SRS. 4.2.4 Backing up Key Management Service You can backup the Key Management Service (KMS) by using the Command Line Interface. The KMS must be running in order to be backed up. Use the following commands: tdpexcc backup Key Management Service full /EXCAPPlication=kms tdpexcc backup Key Management Service copy /EXCAPPlication=kms tdpexcc backup Key Management Service diff /EXCAPPlication=kms tdpexcc backup Key Management Service incr /EXCAPPlication=kms Chapter 4. Backing up Exchange databases 51
You can restore the KMS data by either using Command Line Interface or the Graphical User Interface. If you use the CLI, the command looks like this: tdpexcc restore Key Management Service full /EXCAPPlication=kms If you use the GUI, the process of restoring is similar to restoring any storage group. In our Lab environment we did not set up KMS. For more information on backing up and restoring KMS, refer to the Microsoft documentation. 4.2.5 Backing up Active Directory Because Exchange 2000 is tied with Active Directory, the backup of active Directory is highly recommended. If you lose your Active Directory you will need to rebuild all of the configuration information for your system, which is very labor-intensive work. In this book we do not cover the backup of Active Directory. Refer to Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment, SG24-6141, for instructions on backing up Active Directory. 4.3 Recommended practices The following sections describe some recommended practices concerning using the Include/Exclude statement and different node names. 4.3.1 Include/Exclude statement By using an Include/Exclude list in the dsm.opt file you can: Exclude objects from backup Include any previously excluded objects Bind an object to a specific management class The syntax of the include/exclude statement is: include ObjectNameSpecification [Management Class Name] exclude ObjectNameSpecification Where Object Name Specification is: ExchangeServerName\ExchangeStorageGroupName\dataType\...\backupType In this statement, DataType can be: meta, data, log. For TSM object names, see Appendix G, TSM object names on page 149. 52 Using Tivoli Data Protection for Microsoft Exchange Server
The metadata is information about the data, and it is stored in the TSM ObjInfo field. It keeps a very detailed explanation about each TSM object: version, release, mod, level, TSM API version, Exchange server version, and backup time (used to bind multiple objects together). BackupType can be: full, copy, incr, diff, dbcopy. Be careful to use the correct case for Exchange Storage Groups and lower case for meta, data and logs. If you specify a management class in the Include statement, the applicable objects are backed up by using this management class. If this management class is not valid for the current node, the default management class for the current node is used. There can be more than one Include/Exclude statement for a specific object, as shown in Figure 16. In our lab environment we set up the server ELBRUS as an Exchange 2000 server. It has two storage groups: First Storage Group and ITSO SG. Figure 16. Example of using Include/Exclude statement Chapter 4. Backing up Exchange databases 53
For test purposes, we specified the following statements in the dsm.opt file: EXCLUDE "ELBRUS\...\*" INCLUDE "ELBRUS\First Storage Group\...\*" With the Exclude statement, we excluded the entire server from backup. With the Include statement, we included the first storage group to be backed up. Include/Exclude statements are case sensitive. Include/Exclude statements are processed from bottom to top and are stopped at the first match. So, in our example, when we perform the backup of an entire server (everything is checked in Figure 16) the ITSO SG storage group is not backed up. When the backup process begins, it first checks the Include statement it does not apply to ITSO SG storage group and then it checks the Exclude statement this applies to the ITSO SG storage group and the group is excluded from backup. The same procedure applies to the First Storage Group. When the backup process begins, it first checks the Include statement and this statement includes the backup of the First Storage Group. So, the backup for the First Storage Group is performed and the checking stops. The result of the backup is shown in Figure 17. Figure 17. Result of the backup You can see that only the First Storage Group is being backed up. 54 Using Tivoli Data Protection for Microsoft Exchange Server
4.3.2 Different node names The TSM administrator specifies the Policy Domain in which your node resides. A Policy Domain contains policy sets and management classes, that control how the TSM server manages the objects you back up. If you use the regular Backup/Archive Client for backing up your Windows system and TDP for Exchange to back up Exchange server it is recommended that you use different node names for the clients, because usually they have different requirements for backup and use different Policy Domains. Also, if you have coexistence of v.1 and v.2 of TDP for Exchange, it is recommended to use different node names, despite the fact that you can use an Include/Exclude statement to specofy different management classes. See 2.4, TDP for Exchange v.1 and v.2: differences and coexistence on page 21. 4.4 Clustering In our lab environment we set up Exchange 2000 on computers running Microsoft Cluster service on Microsoft Windows 2000 Advanced Server. After installing the cluster, we installed TDP for Exchange on both nodes. The procedure of installing TDP for Exchange on a cluster is the same as installing TDP for Exchange on a non-clustered environment. TDP for Exchange must be installed on a local disk to each node. Be sure that the options files on both nodes are identical and that you specify the CLUSTERNODE YES in the TDP for Exchange options file. Specify the NODename, the PASSWORDAccess options and the name of the TSM server as is described in 3.2.2, Registering TDP for Exchange with a TSM server on page 29 and 3.2.3, The TDP for Exchange options file on page 29. You can perform backups from either of the nodes. TSM treats backups as coming from a single server. You can perform backup by using the Graphical User Interface or Command Line Interface from either of the nodes. Before using the Graphical User Interface, specify the server as shown in 3.3, Installing TDP for Exchange in an MSCS environment on page 30. After invoking the GUI, you will see the window illustrated in Figure 18. Chapter 4. Backing up Exchange databases 55
Figure 18. Backing up Exchange on a cluster You will see exactly the same interface from both nodes. In our example, the Exchange Virtual server has the name MATTERHORN and it is a member of the domain uphi.sky. There is one storage group residing on this server, and you can perform full, differential, incremental, copy, or database copy backups. For adjustment of configuration settings, refer to 3.2.3, The TDP for Exchange options file on page 29. You can also perform backups using the Command Line Interface. You can see the format of this command and explanation of the options in 4.2.2, Backing up Exchange 2000 using the CLI on page 47. The only difference is that you have to specify the name of the Exchange Virtual server. 56 Using Tivoli Data Protection for Microsoft Exchange Server
The output of performing a full backup of all the storage groups is as follows: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc backup * full /excserver=matterhorn Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully. Starting storage group backup... Beginning full backup of First Storage Group, 1 of 1. Full: 0 Read: 16827110 Written: 16827110 Rate: 941.97 Kb/Sec Backup of First Storage Group completed successfully. Total storage groups requested for backup: 1 Total storage groups backed up: 1 Total storage groups expired: 0 Total storage groups excluded: 0 Throughput rate: 939.82 Kb/Sec Total bytes transferred: 16,827,110 Elapsed processing time: 17.48 Secs In this example, we specify the switch /exchserver=matterhorn which is the name of our Exchange Virtual server. This switch must be used! It is VERY important when setting up scheduling on a cluster that the EXACT steps in the User's Guide are followed. 4.5 Automating backups By using the TSM scheduler, you can automate the backup process. The following sections describe procedures for automation of backups on a single node and in a cluster environment. If you prefer to use another scheduler to control your backups, this is possible too. However, do not forget to set up Registry replication to maintain the password if using the generate option for TDP passwords on a cluster. Chapter 4. Backing up Exchange databases 57
4.5.1 Scheduling backups on a single node Automating concerns both the TSM server and the Exchange server. On the Exchange server, use the following steps: 1. You must install the Backup/Archive Client on the machine where Microsoft Exchange server and TDP for Exchange are installed. A detailed explanation of how to install the Backup/Archive Client is given in 3.5, Installing the Backup/Archive client on page 33. 2. Install the TSM scheduler client as a Windows service. If you already have TSM Scheduler service installed, install another one only for TDP for Exchange. For this purpose, type the following command: dsmcutil inst /name: TDP for Exchange Scheduler /node:your_node_name /password:your_password /autostart:yes /clientdir: Directory_Installation_path_for_BAClient /optfile: Directory_Installation_path_for_TDPExchange\dsm.opt /startnow:no The dsmcutil command is located in the installation directory of Backup/Archive Client. Be careful to fully qualify all file specifications. 3. Create a command file with the commands for performing backups. This file must have the extension cmd. A sample file for performing incremental backups is located in the directory where TDP for Exchange is installed excincr.smp and it performs an incremental backup of all storage groups. 4. Start the created scheduler service either by typing in the console window: net start TDP for Exchange Scheduler or by using the Services MMC window. On the TSM server, you or your TSM administrator must define a schedule to run a command file and associate your TDP for Exchange node name to the defined schedule. You can define a schedule either by using the server console or by using the web interfaced administrative client. To define a schedule by using the Web administrative client, click Server Administration -> Operation View -> Automate client operations and then Define a Client Schedule. You will see the window in Figure 19. 58 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 19. Defining schedule TSM administrative client Web interface Chapter 4. Backing up Exchange databases 59
Fill in the fields Specify your Policy Domain Name, Schedule Name, Description, specify Action as COMMAND; in the Objects field, specify the name of the cmd file; set priority (if two or more schedules for a given client have the same window start time, this value determines the order of execution; the schedule with the highest priority starts first), Start Date, Start Time, Duration, Duration Units, Period, Period Units, Day of Week, and Expiration and then click Finish. If you click Help, you will see a detailed explanation of these parameters. In the example shown in Figure 19 we created a new schedule which performs incremental backups of the Exchange server, every day at 23:55, according to the command file c:\excincr.cmd. After that, you must associate that schedule with the Client node. Select Server administration -> Operation view -> Automate client operations and then Associate client notes with the schedule. You will see the window shown in Figure 20. Figure 20. Associate client nodes with the schedule Specify your Policy Domain Name and then Scheduler name. If you desire, you may specify the node as well. If you put * in the node field, this schedule will concern all your nodes in your policy domain. 60 Using Tivoli Data Protection for Microsoft Exchange Server
If you are using the server console, type the following command to define schedule and replace the values in the example with your preferences: def sched exagents schedule_name desc= Description_of_the_schedule action=command objects= c:\your_command_file.cmd priority=2 starttime=value duration=value duru=minutes period=1 perunits=day dayofweek=any To associate TDP for Exchange to this schedule, issue the following command: define association exagents schedule_name nodename The scheduler is now running. 4.5.2 Scheduling backups on a cluster After installing the Exchange servers in a cluster environment and installing TDP for Exchange on both nodes, as described in 3.3, Installing TDP for Exchange in an MSCS environment on page 30, follow these steps: 1. Install the Backup/Archive Client on both nodes. A detailed explanation of how to install the Backup/Archive Client is given in 3.5, Installing the Backup/Archive client on page 33. 2. Install the TSM scheduler client as a Windows service on both nodes. If you already have one Scheduler Service for the regular TSM client, install another one only for TDP for Exchange. For this purpose, type the following command on the first node and be careful to use fully qualified file specifications: C:\Program Files\Tivoli\TSM\baclient>dsmcutil inst /name:"tdp for Exchange Scheduler" /node:matterhorn_exch2 /password:uphi /autostart:no /clientdir:"c:\program Files\Tivoli\TSM\baclient" /optfile:"c:\program Files\Tivoli\TSM\TDPExchange\dsm.opt" /startnow:no The dsmcutil command is located in the installation directory of Backup/Archive Client. Issue the same command on the second node. Replace the nodename, password, clientdir and optfile with your data. Make sure that you specify the autostart option to no. That is because this service must be started by using the Cluster Administrator program. Chapter 4. Backing up Exchange databases 61
The output of this command looks like this: TSM Windows NT Client Service Configuration Utility Command Line Interface Version 4.00.a Last Updated Feb 17 2001 (Non-Unicode Build) TSM Api Verison 4.1.2 Command: Install TSM Client Service Machine: BONNIE(Local Machine) Installing TSM Client Service: Machine : BONNIE Service Name : TDP for Exchange Scheduler Client Directory : C:\Program Files\Tivoli\TSM\baclient Automatic Start : no Logon Account : LocalSystem The service was successfully installed. Creating Registry Keys... Updated registry value 'ImagePath'. Updated registry value 'EventMessageFile'. Updated registry value 'TypesSupported'. Updated registry value 'OptionsFile'. Updated registry value 'EventLogging'. Updated registry value 'ClientNodeName'. Updated registry value 'ADSMClientKey'. Updated registry value 'TDP for Exchange Scheduler'. Generating registry password... Authenticating TSM password for node MATTERHORN_EXCH2... Connecting to TSM Server via client options file 'C:\Program Files\Tivoli\TSM\TD PExchange\dsm.opt'... Password authentication successful. The registry password for TSM node MATTERHORN_EXCH2 has been updated. 3. Create a command file with the commands for performing backups. A sample file for performing incremental backups is located in the directory where TDP for Exchange is installed excincr.smp and it performs an incremental backup of all storage groups. Modify it or create a new one according to your preferences. Put this file on the Exchange server file share. 4. Start the Cluster Administrator, select the Exchange Cluster Group and create a new resource to represent the TDP for Exchange scheduler. Follow instructions and fill in the fields Name, Description, Resource type: Generic Service, Group: your Exchange cluster group, Dependencies: Microsoft Exchange Directory and Microsoft Exchange Information store, Service Name type the name of the service which you installed with the dsmcutil command. Be careful to set up Registry Replication to none! 62 Using Tivoli Data Protection for Microsoft Exchange Server
5. Issue a command that connects to the TSM server specifying the /tsmpassword=yourpassword option. In this way, you will be sure that a correct password is stored in the registry. For instance, you may type: tdpexcc backup * full /tsmpassword=your_password /excserver=your_server_name or: tdpexcc query tsm /tsmpassword=your_password /excserver=your_server_name 6. Bring the newly-created resource online from the Cluster Administrator. 7. Modify the properties of the resource by double-clicking on it, and then point to Registry Replication. You will see the window in Figure 21. Figure 21. Registry Replication Click Add and enter the following entry: Software\IBM\ADSM\CurrentVersion\BackupClient\NODES\your_node_name 8. Take the resource offline by right clicking on the resource and then click Take Offline. In this way you will save the encrypted password in quorum device, and both nodes will be able to pick up the correct password in case of failover. Chapter 4. Backing up Exchange databases 63
9. Bring the resource online by right-clicking on it and then point to Bring Online. The scheduler is now running. It is important to set up the Registry replication described above when attempting to automate the backup procedure on a cluster. The replication will assure that the password stored in the Registry will be available on both nodes and that it will also be valid on both nodes if the generate option has been used to automatically update the password after an expiration. If you choose to use another scheduler, you should still assure the replication of the password between nodes. If your scheduler is not set up as a Generic Service on the cluster, you can configure the TDP password replication on one of the Exchange services. 4.6 Performance The performance of the backup and restore process depends on many factors. Some of them concern hardware configuration, network type, and so on, and have nothing to do with TDP for Exchange. Nevertheless, you can adjust some parameters to achieve better performance. You can implement buffering, LAN-free backups, and carefully consider your backup strategy. By implementing buffering you can take advantage of asynchronous execution threads which TDP uses when transfering data between Exchange and TSM server. See 4.1.1.1, Configuration settings on page 38 for adjusting the number and size of the buffers by using GUI and 4.1.2.3, Optional parameters on page 44 if you use CLI. By using LAN-free backup you are no longer dependent on network bandwidth. For setting up LAN free backups, see Chapter 5, SAN usage on page 67. Consider using a backup strategy that is most suitable to your network traffic and that provides acceptable backup and restore times. For more information, see 2.1.3, Backup strategies for Exchange 2000 and 5.5 on page 12. The TDP for Exchange progress bar shown in Figure 17 on page 54, which you see during the backup and restore, cannot be used to indicate the remaining time for backup and restore it shows the completed items and its value depends on the size of the items being processed. 64 Using Tivoli Data Protection for Microsoft Exchange Server
4.7 Integration with other products The TSM server has a built-in adapter which can be used to forward all event messages to a receiver. The receiver can, for example, be: Tivoli Enterprise Console, SNMP traps, a file, and so on. You can utilize this feature to automate monitoring of your scheduled backups. Assuming that you already have a TEC server in your environment, you can forward all TDP for Exchange events to the Tivoli Enterprise Console. On the TSM server, specify ENable EVents TIVOLI <eventid> NODEname=<node> where TDP event id prefix is ACO and range is 3000-3999. Note The application client must have enhanced T/EC support enabled in order to route the above messages to the Tivoli Event Console. For more information, consult the TSM Administrators Guide at this URL: http://www.tivoli.com/support/storage_mgr/pubs/v4pubs/v1_html/aix/guide/ anrag192.htm#hdrclam Chapter 4. Backing up Exchange databases 65
66 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 5. SAN usage Storage Area Networks (SANs) have become increasingly popular. There are many reasons for this, which are beyond the scope of this book. Neither will we provide a thorough description on how to set up and run a SAN. In this chapter, we will introduce the concepts of integrating a SAN with the TSM environment utilizing TDP for Exchange. We describe how to move from an existing TDP/TSM installation using the LAN to transfer data to an environment utilizing TSM LAN-free to transfer data on the SAN. We advise you to consult the following books to get a deeper insight in setting up a SAN and TSM in a SAN environment: Using Tivoli Storage Manager in a SAN environment, SG24-6132 TSM Managed System for SAN Storage Agent User s Guide, GC35-0434 Introduction to Storage Area Network, SAN, SG24-5470 5.1 Overview of LAN-free SAN and TDP for Exchange As Exchange databases grow and the amount of data that requires backup is increasing, it may become troublesome to perform TDP backups across the LAN connection to the TSM server. One solution to overcome the problem could be to install a TSM server locally on the Exchange server itself, along with a TSM storage device. This will prevent the backup data from travelling across the LAN and decrease the backup and restore times if the LAN is the bottleneck. However, this solution not only adds additional hardware cost to the TSM environment, but it also makes managing the system more cumbersome and complicated. Also, it is not wise to store backups and backup equipment at the same location as the production system itself. A better solution to problems due to the LAN being a bottleneck for the data transfer is to set up a SAN. SANs, using Fiber Channel Protocol (FCP), are designed for large data transfers, and will outperform even high-speed LANs. TDP for Exchange supports LAN-free backup for TSM. In order to shift the data movement from the LAN to the SAN, TDP is utilizing the TSM Managed System for SAN Storage Agent, which must be installed on the client machine along with TDP for Exchange. Copyright IBM Corp. 2001 67
The implementation is depicted in Figure 22. As seen, the main purpose is to move data from the client across the SAN instead of from the LAN to the TSM storage connected to the SAN. The placement of the data is controlled by the Tivoli Storage Manager server, and only metadata, which is just a fraction of the raw backup data, is communicated across the LAN between the TSM server and the TDP for Exchange client. The Storage Agent functions as an interface to the SAN for TDP for Exchange. TDP for Exchange 2.2 & TDP Storage Agent TCP/IP Meta Data LAN TCP/IP TSM 4.1 Server Data FCP FCP Exchange Data Backup Data SAN SAN Datagateway Figure 22. LAN-free backup 5.1.1 The TSM Storage Agent To support LAN-free data transfer, the Managed System for SAN Storage Agent has been introduced. The Storage Agent is running on the client machine in order to enable data transfers to the SAN. To the TDP for Exchange client, it looks pretty much like any other TSM server. 68 Using Tivoli Data Protection for Microsoft Exchange Server
From a high level standpoint, the Storage agent works in the following way: 1. TDP for Exchange invokes a backup. The client contacts the TSM server and exchanges policy information over the LAN to determine the destination of the backup data. If the client is configured to use LAN-free data movement, the destination will be a storage pool that is set up to use a device on the SAN. The device must also be mapped on the client. 2. Because the backup destination is on the SAN, the client contacts the Storage Agent by opening a named pipe session. The name of the named pipe is hardcoded in TDP code and the only communication protocol supported is named pipes. 3. The Storage Agent opens a server-to-server connection to Tivoli Storage Manager server via the LAN; the only supported communication protocol at this time is TCP/IP. 4. TDP sends a begin-transaction verb to Storage Agent. When the transaction is successfully committed, the Storage Agent opens a SAN data transfer to a tape storage device. Otherwise, if the first transaction fails, the communication will be switched over to the LAN, and the SAN data transfer will not be used. 5. The LAN server-to-server communication between the Storage Agent and Tivoli Storage Manager server is used by the Storage Agent for accessing Tivoli Storage Manager server database. That is because the Storage Agent does not have its own database, nor a recovery log. You can imagine the Storage Agent as a truncated Tivoli Storage Manager server. 6. When the Storage Agent finishes the backup, it sends file attribute data to the TSM server, and the server stores the data in the database. When restoring data, the restore session is always opened through a Storage Agent. If any data was backed up through the SAN, the restore will also go through the SAN. If any data was backed up through a LAN, then the LAN connection will be used during restore. If you have backed up some data using the SAN, you can still access this data through the LAN, if needed. Some limitations and requirements apply to running TDP for Exchange across the SAN: Only TSM server versions 4.1 or higher are supported. Windows NT 4.0 service pack 6, Windows 2000 build 2195 or later TCP/IP is required for the LAN communication. Currently only tape storage pools are valid backup destinations. Chapter 5. SAN usage 69
5.2 Setting up LAN-free SAN support In the following sections we will describe the steps performed to enable TDP for Exchange to successfully move backup data across the SAN. We assume that the SAN itself is already up and running. Our approach is, based on that assumption, to describe how to get a running TDP LAN implementation to work on the SAN. Consult Chapter 3 and Chapter 4 regarding general installation and configuration of TDP for Exchange. Before setting up LAN-free data transfer, you must ensure that you have Tivoli Storage Manager 4.1 server configured and running, since it must be able to communicate with any tape device via the SAN. You can have any server platform running; the only requirement is that it must be TSM Release 4.1 or later. In our environment we used Tivoli Storage Manager Server 4.1.2.0 running on AIX 4.3.3 maintenance level 6. See Appendix A, Lab environment on page 133 for an overview of the lab environment. 5.2.1 Preparing TSM server for LAN-free configuration We assume that the server already has the connectivity to the SAN tape devices configured on the OS. In our test environment we had a Magstar 3570 with two drives connected to the SAN through a 2108 SAN Data Gateway, which was used to bridge SCSI to FCP. Use lsdev -C -c tape to see tape devices available on AIX: # lsdev -C -c tape rmt0 Available 30-58-00-0,0 IBM 3580 Ultrium Tape Drive rmt1 Available 30-58-00-1,0 IBM 3580 Ultrium Tape Drive smc0 Available 30-58-00-6,0 IBM 3583 Library Medium Changer rmt2 Available 20-58-01-2,0 IBM Magstar MP Tape Subsystem (FCP) rmt4 Available 20-58-01-3,0 IBM Magstar MP Tape Subsystem (FCP) To prepare your Tivoli Storage Manager server for LAN-free configuration, we did the following: Defined library and drives. The library must be defined as a SHARED library, otherwise the Storage Agent will not be able to communicate with it. To define the library and drives, we entered the following TSM commands: DEFINE LIBRARY 3570LIB LIBT=SCSI DEVICE=/dev/rmt2.smc SHARED=YES DEFINE DRIVE 3570LIB DRIVE0 DEVICE=/dev/rmt2 DEFINE DRIVE 3570LIB DRIVE1 DEVICE=/dev/rmt4 70 Using Tivoli Data Protection for Microsoft Exchange Server
If you already have a library defined on your server, make sure that the parameter SHARED is set to YES. Note that you cannot use the update library command to update this parameter. You must remove the drives definition, delete the library, and then define it again with the SHARED parameter set to YES. Defined a device class. We defined the device class 3570CLASS for the library: DEFINE DEVCLASS 3570CLASS DEVTYPE=3570 MOUNTRET=2 MOUNTL=2 LIBRARY=3570LIB We specified the MOUNTLIMIT to equal the number of physical drives in the tape library (two drives). Since the library is shared, we set the MOUNTRETENSION as low as 2 minutes. The default is 60 minutes. Defined a storage pool in the device class. DEF STG 3570SAN 3570CLASS We already performed backups across the LAN, and hence our TDP client node was already configured on the server. However, we needed to create copy groups for the new storage group. We decided to simply use the existing policy set and domain and then create a new management class API_SAN_30DAYS: tsm: BRAZIL>define mgmtclass TDPEXCH2_DOMAIN STANDARD API_SAN_30DAYS ANR1520I Management class API_SAN_30DAYS defined in policy domain TDPEXCH2_DOMAIN, set STANDARD. And again, we defined both a backup and an archive copy group: tsm: BRAZIL>define copygroup TDPEXCH2_DOMAIN STANDARD API_SAN_30DAYS type=backup dest=3570san verexists=nolimit retextra=30 verdeleted=nolimit retonly=30 ANR1530I Backup copy group STANDARD defined in policy domain TDPEXCH2_DOMAIN, set STANDARD, management class API_SAN_30DAYS. tsm: BRAZIL>define copygroup TDPEXCH2_DOMAIN STANDARD API_SAN_30DAYS type=archive dest=3570san ANR1535I Archive copy group STANDARD defined in policy domain TDPEXCH2_DOMAIN, set STANDARD, management class API_SAN_30DAYS. Chapter 5. SAN usage 71
Just as TDP nodes must be defined on the TSM server, so must the Storage Agents. Storage Agents are defined as servers. We decided to name our Storage Agents by the template Servername_STA. Hence we defined the TSM server ELBRUS_STA with the password pw. tsm: BRAZIL>define server ELBRUS_STA serverpassword=pw hladdress=193.1.1.144 lladdress=1500 ANR1660I Server ELBRUS_STA defined successfully. In these statements, hladdress and lladdress are the IP-address and port number for the Storage Agent installation. 5.2.2 Setting up the client node to support LAN-free On the TDP client, the following must be accomplished: The Host Bus Adapter (HBA) must be installed to physically connect the client to the SAN. Installation of the Storage Agent software. Configuration of the Storage Agent (dsmsta.opt). Set up server-to-server communication between Storage Agent and TSM server. Obtain device information on the client and define drive mapping on the TSM server. Install and configure the Storage Agent as a service. Reconfigure TDP for Exchange. 5.2.2.1 Installing the Host Bus Adapters (HBA) The first step on the client to enable LAN-free is to get access to the SAN. For the purpose of getting access, a Host Bus Adapter (HBA) has to be installed. In our setup we used a Qlogic 2200 series HBA. Firmware and device driver updates are found at: http://www.storage.ibm.com/hardsoft/products/sangateway/support/cdr/nt/sdg nt.htm http://www.qlogic.com/bbs-html/csg_web/adapter_pages/driver_pages/22xx/22w 2k.html 72 Using Tivoli Data Protection for Microsoft Exchange Server
Installation is straightforward just plug in the card and start up the system. Assuming the SAN administrator has added your system to the correct SAN zone, the tape drives and media changer should appear as new devices on the Windows 2000 server. Figure 23. SAN devices seen by Windows 2000 after installing Host Bus Adapter The changer and drives may appear without any drivers installed, as shown in Figure 23. However, in our experience, the Storage Agent worked just fine anyway. 5.2.2.2 Installation of the Storage Agent software It is recommended to install the latest version of the TDP for Exchange and the TSM API before installing the Storage Agent software. There may be a newer version of the API-DLL available than the one included with TDP. Check the version of the API-DLL by looking at its file properties (see Figure 24). The DLL is found in the Windows 2000 system directory <SystemRoot>\System32, typically C:\WinNT\System32. The name of the DLL is tsmapi.dll. Chapter 5. SAN usage 73
Figure 24. Version of the API-dll Update the Dll-version by installing or reinstalling the latest version of the TSM Backup Archive client. The latest version is downloadable from: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/ client/v4r1/windows/i386/latest/ or http://www.tivoli.com/support/storage_mgr/tivolimain.html If you do not need the Backup/Archive client itself, you can select the custom installation option and select the API for installation only. Though it may seem natural to install the API and possibly Backup/Archive client before installing TDP for Exchange, we did not experience the TDP installation to overwrite an existing version of the API-dll with an older one. By installing the Backup/Archive client (PTF IP22151_12) on our test machines, we upgraded the API-dll from version 4.1.2.0 to 4.1.2.12. The Storage Agent software itself is installed like any other Windows based application through a guided installation wizard. Initiate installation by starting up the setup.exe from the CD-ROM or invoking the downloaded.exe file. 74 Using Tivoli Data Protection for Microsoft Exchange Server
For our test lab we used Storage Agent version 4.1.3.0. Software updates are found at: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/ server/v4r1/nt/latest/ There are only a few options available for the software installation, such as the possibility to install in another directory than the default directory, and whether to include online information or not. A minimum of 12 MB free disk space is needed for the installation, and an additional 20 MB is needed for temporary files if installing from the downloadable package. Note that the installation requires a reboot. 5.2.2.3 Configuration of the Storage Agent (dsmsta.opt) Configure the Storage Agent options file, dsmsta.opt, which is found in the directory where the Storage Agent is installed (default: \Program Files\Tivoli\TSM\storageagent). The Storage Agent must be configured for TCP/IP and named pipes. These are default settings. A device configuration file (see 5.2.2.4, Setting up server-to-server communication on page 76) must also be specified in the Storage Agent options file. If there is a need for other clients to use the same Storage Agent, for instance TDP for Microsoft SQL, the ENABLEALLCLIENTS parameter must be set to YES. Verify that the following is included in the dsmsta.opt file: COMMmethod TCPIP COMMmethod NAMEDPIPE DEVCONFIG devconfig.txt ENABLEALLCLIENTS yes After configuring the Storage Agent, make sure that the AdsmScsi device driver is running. In the Storage Agent directory, issue the command: net start AdsmScsi If experiencing problems getting the service running, there is probably a problem pertaining the installation of the HBA. The device driver is also found in the Window 2000 Computer Management MMC (Start -> Programs -> Administrative Tools -> Computer Management) from where it can be managed too. See Figure 25. Note: You will need to enable viewing hidden devices by right-clicking on Device Manager and selecting Show hidden devices. Chapter 5. SAN usage 75
Figure 25. AdsmScsi device management 5.2.2.4 Setting up server-to-server communication In the Storage Agent directory, issue the following command: E:\Program Files\Tivoli\TSM\storageagent>dsmsta setstorageserver myname=elbrus_sta mypassword=pw servername=brazil serverpassword=brazil hladdress=193.1.1.11 lladdress=1500 The parameters myname and mypassword correspond to the ones specified when configuring the Storage Agent as a server (see Chapter 5.2.1). The parameter servername specifies the TSM server, and serverpassword specifies the corresponding password. The parameters hladdress and lladdress specify the IP-address and port number for the TSM server. The command updates the Storage Agent device configuration file (device.txt) with the following entries: SET STANAME ELBRUS_STA SET STAPASSWORD 18686e DEFINE SERVER BRAZIL HLADDRESS=193.1.1.11 LLADDRESS=1500 SERVERPA=185b801eb97c22 As seen, the passwords are encrypted before they are stored. It is also possible, though not recommended, to manually enter the passwords into the files without encrypting them. The Storage Agent will still work. The command also updates the Storage Agent options file (dsmsta.opt) with the following entry: SERVERNAME=brazil 76 Using Tivoli Data Protection for Microsoft Exchange Server
Running the command more than once will not clean up old entries. 5.2.2.5 Define drive mapping on the TSM server As part of the Storage Agent installation, the TSM device driver is installed on the client machine, but it is not enabled or started. Enable the device driver by issuing the following command in the Storage Agent directory: tsmscsi /enable The output from the command will inform that support is enabled: TSM Windows 2000 / Optical support is enabled on ELBRUS. On NT, the message will be something like this: TSM Optical Support enabled on ELBRUS. Note The message tells you that optical support is enabled. However, that is a misleading message. The Managed System for SAN feature does not support optical devices on the SAN. The TSM server needs to know how the client sees the tape devices on the SAN. The information is used to configure drive mapping on the TSM server. Issue the following command in the Storage Agent directory in order to obtain the information: tsmdlst The following device information was found on our specific installation: Computer Name: TSM Device Driver: ELBRUS Running TSM Device Name ID LUN Bus Port TSM Device Type Device Identifier ------------------------------------------------------------------------------ mt1.2.0.2 1 2 0 2 3570 IBM 03570C125424 lb1.3.0.2 1 3 0 2 LIBRARY IBM 03570C125424 mt1.4.0.2 1 4 0 2 3570 IBM 03570C125424 Chapter 5. SAN usage 77
Use the information obtained in the TSM Device Name column to specify the drive mapping on the TSM server: tsm: BRAZIL>define drivemapping ELBRUS_STA 3570LIB DRIVE1 DEVICE=mt1.2.0.2 ANR8916I Drivemapping for drive DRIVE1 in library 3570LIB on storage agent ELBRUS_STA defined. tsm: BRAZIL>define drivemapping ELBRUS_STA 3570LIB DRIVE2 DEVICE=mt1.4.0.2 ANR8916I Drivemapping for drive DRIVE2 in library 3570LIB on storage agent ELBRUS_STA defined. 5.2.2.6 Install and configure the Storage Agent as a service Install the Storage Agent as a service by using the install.exe found in the Storage Agent directory: E:\Program Files\Tivoli\TSM\storageagent>install "TSM Storage Agent" "E:\Program Files\Tivoli\TSM\storageagent\dstasvc.exe" The service is installed to be started manually. Change the setting to automatic from the Windows 2000 services MMC console and start the service. The command install.exe accepts a user ID and password. Use these options if installing the service to run under a specific account. We simply let the service run under the local system account. The remove.exe utility in the same directory can be used if there for some reason is a need to remove the service. 5.2.2.7 Verification of Storage Agent operation As soon as the Storage Agent service has been started, you can query sessions on the TSM server to verify that the Storage Agent is able to connect appropriately to the server. 78 Using Tivoli Data Protection for Microsoft Exchange Server
tsm: BRAZIL>query session Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- -------------------- 2,244 Tcp/Ip Run 0 S 144.6 K 292 Admin WinNT ADMIN 3,523 Tcp/Ip Run 0 S 382.5 K 99 Admin AIX ADMIN 5,489 Tcp/Ip Run 0 S 663 142 Admin WinNT ADMIN 5,505 Tcp/Ip IdleW 18 S 5.6 K 4.7 K Serv- Windows ELBRUS_STA er NT 5,507 Tcp/Ip IdleW 17 S 29.6 K 17.0 K Serv- Windows ELBRUS_STA er NT 5,508 Tcp/Ip IdleW 17 S 166 575 Serv- Windows ELBRUS_STA er NT Another option is to try to connect to the Storage Agent itself using an administrative client (remember that the Storage Agent acts as a server in the TSM environment). Use the same user ID and password as on the TSM server. Interesting commands are, for instance, QUERY SESSION, QUERY PROCES, and QUERY ACTLOG, but tasks like querying the backups table, of course, do not reveal anything. 5.2.2.8 Reconfiguring TDP for Exchange If TDP for Exchange was already set up to run on the LAN, update the options file (dsm.opt) to enable LAN-free operation: ENABLELANFREE YES This is the only change needed to be configured for TDP if the default management class for your node is using the SAN for storage. In this case, however, we created a new management class API_SAN_30DAYS without making it the default management class. Thus we need to specify whenever we want to use the SAN destination management class. This is done using the INCLUDE/EXCLUDE statements in the dsm.opt file, for instance: INCLUDE "ELBRUS\...\*" API_SAN_30DAYS When sending backups to removable media, it may be a good idea to send the metadata to a storage pool that is using disk. For instance, use the old management class to let metadata go to disk storage: INCLUDE "*\...\meta\*" API_DISK_30DAYS Or, create a completely new management class for metadata in general. Consult Chapter 3 and Chapter 4 if you do not already have a running TDP for Exchange installation. Chapter 5. SAN usage 79
5.2.2.9 Backing up across the SAN To the end user, there is no difference in using TDP for Exchange, whether it is set up for LAN-free or LAN operation. The only difference experienced will be the higher data transfer rate. In order to verify that the backup data actually was sent across the SAN, we used the query session command on both the TSM server and the Storage Agent. The following output is from the TSM server: tsm: BRAZIL>query session Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- -------------------- 6,576 Tcp/Ip Run 0 S 34.1 K 516 Admin WinNT ADMIN 6,596 Tcp/Ip IdleW 31 S 11.7 K 8.0 K Serv- Windows ELBRUS_STA er NT 6,597 Tcp/Ip IdleW 13 S 129.2 K 53.1 K Serv- Windows ELBRUS_STA er NT 6,598 Tcp/Ip IdleW 13 S 166 2.2 K Serv- Windows ELBRUS_STA er NT 6,606 Tcp/Ip IdleW 0 S 135.2 K 54.1 K Serv- Windows ELBRUS_STA er NT 6,640 Tcp/Ip IdleW 0 S 17.4 K 3.1 K Node TDP MSE- ELBRUS_EXCH2 xchgv2 NT The query has been done just as a full backup of the ELBRUS_EXCH2 node finished. There are, as seen, six sessions running due to this particular node, but only a little data has been transferred on the TCP/IP connections. 80 Using Tivoli Data Protection for Microsoft Exchange Server
We did the same query on the Storage Agent itself: tsm: ELBRUS_STA>query session Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- -------------------- 1 Tcp/Ip Start 0 S 8.0 K 11.7 K Serv- ELBRUS_STA er 2 Tcp/Ip Start 0 S 53.1 K 129.2 K Serv- ELBRUS_STA er 3 Tcp/Ip IdleW 0 S 2.5 K 166 Serv- ELBRUS_STA er 7 Tcp/Ip Start 0 S 70.2 K 169.6 K Serv- ELBRUS_STA er 11 Tcp/Ip Run 0 S 1.8 K 189 Admin WinNT ADMIN 13 Named Run 0 S 370 36.1 M Node TDP MSE- ELBRUS_EXCH2 Pipe xchgv2 NT On the Storage Agent, we notice the named pipe (session 13) which has received 36.1 MB at this time. That is the actual backup data sent from TDP for Exchange and forwarded on the SAN. Note that as the backup is ended, the named pipe is closed, and it will no longer be possible to see the pipe when querying the sessions on the Storage Agent. Chapter 5. SAN usage 81
82 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 6. Day-to-day monitoring The process of verifying the success of the backup is as important as the backup process itself. We recommend that you do not assume that the backups are good, and that you always perform daily monitoring. 6.1 DB log management As part of your daily routine, review all of the backup logs and make sure there are no errors and inconsistencies. This section provides information on the different type of logs you can view in order to monitor the health of your system. 6.1.1 TSM activity log The TSM activity log contains all messages normally sent to the server console during a server operation. The only exceptions are responses to commands entered at the console, such as responses to QUERY commands. The following events will be send to the activity log: Starts and ends of the client s sessions Starts and ends of migrations Expiring of backup versions Exporting data to tape Expiration processing Export or import processing Error messages sent to the server console The server automatically deletes the messages from the activity log after they have passed the specified age. Consult your TSM administrator about how long activity log information is kept in the database, or query the server status to see this parameter. Be aware that the activity log information can grow very quickly. If you do not have administrator privileges, ask your TSM administrator to check the log for you. 6.1.2 TDP for Exchange log TDP for Exchange writes log information to the tdpexc.log file in the directory where TDP for Exchange is installed. Copyright IBM Corp. 2001 83
6.1.3 TSM API log The TSM API logs information to the dsierror.log file in the directory where TDP for Exchange is installed. 6.1.4 Windows event logs Using Event Viewer and event logs, you can gather information about hardware, software, and system problems, and you can monitor Windows 2000 security events. Windows 2000 records events in three kinds of logs: Application log Contains events logged by programs. Security log Contains valid and invalid logon attempts and events related to resource use, such as creating, opening, or deleting files or other objects. System log Contains events logged by the Windows system components. 6.1.5 TSM scheduler logs There are two files which contain information regarding scheduling, dsmsched.log and dsmerror.log, which are located in the directory where Backup/Archive Client is installed. 6.2 Day-to-day verifications Regular monitoring of the log files and verifying success of the backup will protect you from data loss when a disaster occurs. 6.2.1 TSM server monitoring You can monitor the TSM server either by using the Administrative client or using the graphical Web interface. If you are using the graphical Web interface (by the means of a browser), point to Server Administration -> Operation view -> Monitor operations. Figure 26 depicts graphical Web interface: 84 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 26. TSM server monitoring You can specify the period for which you want to monitor the log by specifying the Begin Date, Begin Time, End Date, and End Time. Also, if you want to see only particular events, you can specify the Message Number to be displayed (each message in the Activity Log has a number) just type the number you want without prefix or suffix. Next, you specify the Search String (put it in quotation marks if it contains spaces). For the Originator, you specify client, node name specify your node name, client owner the name of the owner for which you want to display logged messages. Chapter 6. Day-to-day monitoring 85
For the Schedule Name, you enter the schedule name for which you want to display logged messages (if you do not enter a schedule name, messages for all schedules are displayed; you can use this field only if you selected Client in the Originator field). For the Policy Domain Name, you select the policy domain name to which a particular named schedule belongs, to display logged messages for that policy domain (this field is required when you use the Schedule Name field; you can use this field only if you selected Client in the Originator field). In our example, we query the TSM activity log to verify success of the backup process. We specify the date, the time period, the originator client, and the node name. The result of this output is in Figure 27. Figure 27. TSM activity log From the log, you can see the time when the backup process begins, the type of the backup, and which storage group is backed up, whether the backup is successful, and statistics about the backup process. You may obtain the same information by using the Command Line Interface. For detailed help, type on the Admin command line: help query actlog. The syntax of the command is as follows: 86 Using Tivoli Data Protection for Microsoft Exchange Server
.-BEGINDate--=--current_date--. >>-Query ACtlog----+-----------------------------+--------------> '-BEGINDate--=--date----------'.-BEGINTime--=--currenttime_minus_1_hour--. >-----+-----------------------------------------+---------------> '-BEGINTime--=--time----------------------'.-ENDDate--=--current_date--. >-----+---------------------------+-----------------------------> '-ENDDate--=--date----------'.-ENDTime--=--current_time--. >-----+---------------------------+-----------------------------> '-ENDTime--=--time----------' >-----+---------------------------+---+--------------------+----> '-MSGno--=--message_number--' '-Search--=--string--'.-ORiginator--=--ALL----------------. >-----+-----------------------------------+---------------------> '-ORiginator--=--+-ALL------------+-' +-SErver---------+ '-CLient-- A --' >---+-------------------------+---+---------------------------+-> '-NODEname--=--node_name--' '-OWNERname--=--owner_name--' >-----+------------------------------+--------------------------> '-SCHedname--=--schedule_name--' >-----+---------------------------+---+--------------------+----> '-MSGno--=--message_number--' '-Search--=--string--'.-ORiginator--=--ALL----------------. >-----+-----------------------------------+-------------------->< '-ORiginator--=--+-ALL------------+-' +-SErver---------+ '-CLient-- A --' This command offers various filtering options that can be used to limit the amount of messages displayed and the time it takes to process this query. If you do not specify any parameters with this command, all messages generated in the last hour are displayed. The output is similar to the output obtained from using the Graphical User Interface. Chapter 6. Day-to-day monitoring 87
6.2.2 TDP for Exchange log TDP for Exchange always writes information to the log the logging cannot be switched off. You can specify the log file name in the Logging tab of Exchange Application Client Settings as shown in Figure 12 on page 39. If the file you specify does not exist, a new one will be created. If you do not specify the path, the default path is used and the log file will be in the directory where the TDP for Exchange is installed. Part of this file is shown in the following screen. 03/19/2001 14:52:37 =================================================================== 03/19/2001 14:52:37 Request : Backup 03/19/2001 14:52:37 SG List : First Storage Group,ITSO SG 03/19/2001 14:52:37 Backup Type : FULL 03/19/2001 14:52:37 Database Name : 03/19/2001 14:52:37 Buffers : 5 03/19/2001 14:52:37 Buffersize : 1024 03/19/2001 14:52:37 Exchange Server : (Local Machine) 03/19/2001 14:52:37 TSM Node Name : 03/19/2001 14:52:37 TSM Options File : E:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt 03/19/2001 14:52:37 Mount Wait: Yes 03/19/2001 14:52:37 Quiet : No 03/19/2001 14:52:37 ------------------------------------------------------------------- 03/19/2001 14:52:58 Total storage groups requested for backup: 2 03/19/2001 14:52:58 Total storage groups backed up: 1 03/19/2001 14:52:58 Total storage groups expired: 4 03/19/2001 14:52:58 Total storage groups excluded: 1 03/19/2001 14:52:58 Throughput rate: 983.31 Kb/Sec 03/19/2001 14:52:58 Total bytes transferred: 19,973,146 03/19/2001 14:52:58 Elapsed processing time: 19.84 Secs 03/19/2001 14:53:30 ==================================================================== You can see the type of request (in our case, Backup); the storage groups which were backed up (in our example, First Storage Group and ITSO SG), the type of backup (FULL), the start time of the backup process, the number and size of the buffers, and the options file which is used. At the end of this screen, there are some statistics about the backup process how many storage groups were requested for backup, how many were really backed up, how many backups were expired, and how many groups were excluded. Notice that, in our example, we requested two storage groups for backup, but one of them was excluded by using the Exclude statement in the TDP for Exchange options file, and that is shown in the log file. We recommend daily monitoring of this file. 88 Using Tivoli Data Protection for Microsoft Exchange Server
6.2.3 TSM API log TDP for Exchange uses the Exchange API to communicate with the Exchange server and the TSM API to communicate with the TSM server see Figure 1 on page 8. The diserror.log does not contain backup statistics. This file contains API error information. For example, if we specify the PASSWORDAccess to be PROMPT in the TDP for Exchange options file and then issue the backup command we would have to enter the password. If the password is incorrect you will see the following lines in this file, which indicate an authentication problem: 03/21/2001 11:15:22 sessopen: Error 137 from signon authentication. 03/21/2001 11:15:22 TcpRead(): recv(): errno = 10053 03/21/2001 11:15:22 Error -50 receiving request 6.2.4 Windows event log The Exchange server writes event information to the Windows event log. So regular monitoring of this log could be very helpful when you try to determine the source of the problem. Diagnostics logging levels determine which Microsoft Exchange server events are written to the Windows NT application event log, and you can adjust this parameter from Diagnostics Logging tab in the Server Properties Window (by using Microsoft Exchange Administrator for Exchange 5.5 or by using Exchange System Manager for Exchange 2000, clicking on the server and then click Properties). You can set logging levels to provide information in varying levels of detail. Events can range from significant events (such as an application failure), to moderately important events (such as the receipt of messages across a gateway), to events relevant only to debugging. We recommend to log only critical events. However, when problems occur, diagnostics logging enables you to change the logging levels to capture more detailed events. Refer to the Microsoft documentation about Exchange server for more information on this topic. Backup and restore procedures by using TDP for Exchange will also create events in the Windows Event Log. Chapter 6. Day-to-day monitoring 89
For example, you will see the event with ID:210 in the log, which indicates the beginning of the full backup (Figure 28): Figure 28. Monitoring Windows event log An event ID:213 indicates the successful completion of the backup process. An event ID:4097 indicates the beginning and successful completion of the schedule. An event ID:4099 indicates the failure of performing a schedule. We recommend regular monitoring of Windows event log it is very helpful and can help you identify possible problems. 90 Using Tivoli Data Protection for Microsoft Exchange Server
6.2.5 TSM Scheduler logs The dsmerror.log is analogous to the TSM API log, which is described in 6.1.3, TSM API log on page 84. The dsmsched.log contains information about the success or failure of scheduled commands. An example of the dsmsched.log is shown here: 03/17/2001 03:03:28 --- SCHEDULEREC QUERY BEGIN 03/17/2001 03:03:28 --- SCHEDULEREC QUERY END 03/17/2001 03:03:28 Next operation scheduled: 03/17/2001 03:03:28 ------------------------------------------------------------ 03/17/2001 03:03:28 Schedule Name: TEST 03/17/2001 03:03:28 Action: Command 03/17/2001 03:03:28 Objects: c:\excincr.cmd 03/17/2001 03:03:28 Options: 03/17/2001 03:03:28 Server Window Start: 13:59:57 on 03/17/2001 03/17/2001 03:03:28 ------------------------------------------------------------ 03/17/2001 03:03:28 Command will be executed in 11 hours and 5 minutes. 03/17/2001 14:08:28 Executing scheduled command now. 03/17/2001 14:08:28 Node Name: ELBRUS_EXCH2 03/17/2001 14:08:28 Session established with server BRAZIL: AIX-RS/6000 03/17/2001 14:08:28 Server Version 4, Release 1, Level 2.0 03/17/2001 14:08:28 Server date/time: 03/17/2001 14:09:16 Last access:03/17/2001 03:04:18 03/17/2001 14:08:28 Executing Operating System command or script: c:\excincr.cmd 03/17/2001 14:08:28 Finished command. Return code is: 0 03/17/2001 14:08:28 Scheduled event 'TEST' completed successfully. 03/17/2001 14:08:28 Sending results for scheduled event 'TEST'. 03/17/2001 14:08:28 Results sent to server for scheduled event 'TEST'. 03/17/2001 14:08:28 Querying server for next scheduled event. 03/17/2001 14:08:28 Node Name: ELBRUS_EXCH2 03/17/2001 14:08:28 Session established with server BRAZIL: AIX-RS/6000 03/17/2001 14:08:28 Server Version 4, Release 1, Level 2.0 03/17/2001 14:08:28 Server date/time: 03/17/2001 14:09:17 Last access:03/17/2001 14:09:16 In this example, the schedule named TEST executed the command file exchincr.cmd at 14:08. However, in this example the entry: Scheduled event 'TEST' completed successfully does not show the success or failure of the command this is only the indication that the TSM server successfully issued the scheduled command associated with the eventname. To verify success of the process, see the return code of the following entry: Finished command. Return code is: 0 To verify failure of the process, see the return code of the following entry: Finished command. Return code is: 1 Chapter 6. Day-to-day monitoring 91
6.3 Test restores We consider performing test restores as part of verifying the backup process. For this purpose, it is good to have some dedicated hardware for recovery. We encourage you to attempt a complete recovery in a test environment similar to your production environment. In this way you will have a real notion about how long this process takes and how successful the restore is. Also, you will be able to identify the problems concerning backup and restore early and reduce the impact of possible future disaster. For more information on restores see Chapter 7, Restoring Exchange databases on page 103. 6.4 Auto deletion of old backups TSM server supports multiple versions of backups to exist, which is extremely useful when you want to restore to some point of time. The most current version of a file is called the active version. All other versions are called inactive versions. TDP for Exchange Version 2 allows using the policy-based expiration capabilities of TSM server, which means that after meeting special conditions the backup versions are deleted. There are four parameters which control the deletion process. The first pair of them controls the number of versions to keep. The second pair controls the number of days to keep backup versions. Version Data Exists The number of versions to keep when the data still exists on the client machine Version Data Deleted The number of the versions to keep when the data no longer exists on the client machine Retain Extra Versions How many days to keep inactive backup versions; the days are counted from the day that the version became inactive Retain Only Versions How many days to keep the last backup version of a object that has been deleted 92 Using Tivoli Data Protection for Microsoft Exchange Server
These parameters interact to determine the backup versions that the server keeps. When the number of the backup versions exceeds the number of the versions allowed (Version Data Exists and Version Data Deleted), the oldest version expires and the server deletes the file the next time the expiration process runs.the Retain Extra Versions also controls how many inactive versions are kept. Inactive versions will expire when the number of days that they have been inactive exceeds the value specified by Retain Extra versions, even if the number of the versions is not exceeded. In our Lab environment, we set up these parameters as described in 2.3.1, Policies and management classes on page 18: Version Data Exists: No limit Version Data Deleted: No limit Retain Extra Versions: 30 days Retain Only Version: 30 days For example, our backup strategy was performing full backups on Sundays and incremental backups on weekdays and Saturdays. Because incremental objects are uniquely named, they are only controlled by the Retain Only Version parameter (which is set to 30 days in our case). The full backup objects are controlled by two parameters: Version Data Exists (which is set to No limit) and Retain Extra Version (which is set to 30 days). Therefore, we can have as many full backup versions as we desire, and they will be kept for 30 days. We began with a full backup on the first day (Sunday), then we performed 6 incremental backups on weekdays and Saturday, then we again performed a full backup on Sunday, and so on. So, following this strategy, on the 30th day we will have 4 inactive versions and one active version of full backups and 25 incremental backup objects. On the 31st day, the oldest version of the full backup will expire. However, we will still have the 6 old incremental objects with no associated full backup objects, which will expire according to the Retain Only Version parameter, one by one, in the next six days. So, keep in mind that if you choose such a strategy, you will always have some old incremental backups without associated full backups. Thus, if you choose the Version Data Exists to be 30 days, then 30 days after the backup operation you will be able to restore to the state of the day indicated by (30 number of incremental backups between full backups ). Chapter 6. Day-to-day monitoring 93
6.5 Verifying the success of the backup using the GUI The Graphical user interface can be used for verifying success of the backup. If you point to the Restore tab you will see a display as in Figure 29: Figure 29. Verifying success using the GUI You have the options to show the Only Active Objects and All Objects. If you specify Only Active Objects, you will see only active backup objects. If you specify All Objects, the list will contain all inactive objects as well. From this list, you can see the type of the backup, the date on which the backup was performed, and the size of the object. 6.5.1 Query commands There are three basic query commands, which allow you to monitor the status of Exchange server, to query a list of the TDP for Exchange configuration information, and to query a list of Exchange backups in TSM storage. 94 Using Tivoli Data Protection for Microsoft Exchange Server
6.5.1.1 tdpexcc query exchange This command can be used for querying the local Exchange server for general information. The format of the command is: TDPEXCC Query EXCHange [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/EXCSERVer=servername] (default: local exchange server) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) The optional parameters are closed in brackets. /CONFIGfile=configfilename Used to specify the name of the TDP for Exchange configuration file that contains the values for the TDP for Exchange configuration options. If you do not include the path where this file is located, the default TDP for Exchange installation directory is used. If the path includes spaces the entire configfile parameter must be placed in double quotes. If you do not specify the /configfile the default tdpexc.cfg is used. And if the /configfile parameter is specified but the configfilename variables not specified the default value is tdpexc.cfg. /EXCSERVer=servername The servername variable specifies the name of the Exchange server to query. If this parameter is not mentioned the default server is used. If you want to query a member of MSCS you must specify the name of the Virtual server. /LOGFile=logfilename This parameter cannot be turned off. If you do not specify the log file, the default log file tdpexc.log is used. You can include the path in the logfilename variable. If the path is not included the default installation directory of TDP for Exchange is used. If the path contains spaces, put the name in double quotes. If the specified file does not exist a new one is opened. If the file exists, the new entries are appended to the file. /LOGPrune=numdays NO Use this parameter to disable log pruning or to explicitly request a prune of the log for one command run. By default, the log prune is enabled and performed once per day. The numdays variable specify the number of days to save log entries. By default, 60 days of log entries are saved in the prune process. You can use the TDP for Exchange GUI or the set command to change the defaults so that log pruning is disabled, or so less or more days of log entries are saved. Note that when the value of the /logprune variable is a number in the range 0 to 9999, a prune is performed, even if one has already been performed for the day. Chapter 6. Day-to-day monitoring 95
The output of the tdpexcc query exchange command for Exchange 5.5 is: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query Exchange Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Microsoft Exchange Server Information ------------------------------------- Organization Name: UPHI Site Name: SJ Server Name: SHASTA Exchange Server Version: 5.5.2653.23 Directory: Information Store: Running (circular logging disabled) Running (circular logging disabled) For this output, you can see the version of the Exchange server, the organization, site and server names, status of the Directory and Information store services and whether the circular logging is enabled. Exchange 5.5 version numbers are as follows: Version Build Number 5.5 SP1 5.5.2232 5.5 SP2 5.5.2448 5.5 SP3 5.5.2650 5.5 SP4 5.5.2653 The current Exchange 2000 version number is 6.0.4417.0. 96 Using Tivoli Data Protection for Microsoft Exchange Server
The output of the tdpexcc query exchange command for Exchange 2000 is: Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Microsoft Exchange Server Information ------------------------------------- Server Name: ELBRUS Domain Name: K2.uphi.sky Exchange Server Version: 6.0.4417.0 Storage Groups with Databases and Status ---------------------------------------- First Storage Group Circular Logging - Disabled Mailbox Store (ELBRUS) Public Folder Store (ELBRUS) ITSO SG Circular Logging - Disabled ITSO 6147 Mailbox Store ITSO 6148 Mailbox Store VIP SG Circular Logging - Disabled Manager Mailbox Store Online Online Offline Online Online From this output, you can see the version of the Exchange server, domain and server names, storage groups, and all database names with status of each of them and whether the circular logging is enabled. 6.5.1.2 tdpexcc query tdp This command gives the current values set in the configuration file for TDP for Exchange. The format of the command is: TDPEXCC Query TDP [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) Chapter 6. Day-to-day monitoring 97
Refer to 6.5.1.1, tdpexcc query exchange on page 95 for the explanation of the optional parameters which can be used. The output of the command is: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query tdp Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. TDP for Microsoft Exchange Preferences -------------------------------------- BUFFers... 3 BUFFERSIze... 1024 DATEformat... 1 LOGFile... tdpexc.log LOGPrune... 60 MOUNTWait... Yes NUMberformat... 1 TEMPLOGRESTOREPath... TIMEformat... 1 You can find a detailed explanation of these parameters in 4.1.1.1, Configuration settings on page 38. 6.5.1.3 tdpexcc query tsm This command provides you with information about the TSM server and TSM API. You can also use this command for displaying a list of active and inactive backups that are stored on the TSM server that match the storage group entered. The format of the command is: TDPEXCC Query TSM [* DIR IS sgname1,...,sgnamen [backuptype]] where backuptype can be: FULL COPY INCRemental DIFFerential DBCopy dbname [/ACtive] [/ALl] [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/FROMEXCSERVer=servername] (default: local exchange server) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) [/TSMNODe=nodename] 98 Using Tivoli Data Protection for Microsoft Exchange Server
If the positional parameters are not specified, you will see only the TSM API and TSM server information. The output of the command, without specifying positional parameters, is: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query tsm Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Tivoli Storage Manager Server Connection Information ---------------------------------------------------- Nodename... SHASTA_EXCH2 NetWork Host Name of Server... 193.1.1.11 TSM API Version... Version 4, Release 1, Level 2 Server Name... BRAZIL Server Type... AIX-RS/6000 Server Version... Version 4, Release 1, Level 2.0 Compression Mode... Client Determined Domain Name... TDPEXCH2_DOMAIN Active Policy Set... STANDARD Default Management Class... API_DISK_30DAYS You can specify the following positional parameters: * DIR IS sg-name * Query all backup objects for all storage groups. DIR Query all Directory backup objects (Exchange Server 5.5 only). IS Query all Information store backup objects (Exchange Server 5.5 only). sg-name Query all backup objects for the specified storage group. Multiple entries are separated by commas. For Exchange Server 5.5, sg-name represents the DIR and IS storage groups. The following positional parameters specify the type of the backup to query: FULL COPY INCRemental DIFFerential DBCopy db-name FULL Query only Full backup types COPY Query only Copy backup types INCRemental Query only Incremental backup types Chapter 6. Day-to-day monitoring 99
DIFFerential Query only Differential backup types DBCopy db-name Query only database copy backups for the database db-name. This is only available on Exchange 2000. If the type of the backup is not specified, all backup types will be displayed. The following optional parameters can be specified: /ACtive Use the /active parameter to display active backup objects only. This is the default. /ALL Use the /all parameter to display both active and inactive backup objects. If the /all parameter is not specified, only active backup objects are displayed. /CONFIGfile=configfilename Use the /configfile parameter to specify the name of the TDP for Exchange configuration file that contains the values for the TDP for Exchange configuration options. The configfilename variable can include a fully qualified path. If the configfilename variable does not include a path, the TDP for Exchange installation directory is used. If the configfilename variable includes spaces, the entire /configfile parameter entry must be placed in double quotes. If the /configfile parameter is not specified, the default value is tdpexc.cfg. If the /configfile parameter is specified but the configfilename variable is not specified, the default value is tdpexc.cfg. /FROMEXCSERVer=server-name Use the /fromexcserver parameter to specify the name of the Exchange server where the original backup was performed.the default is the local Exchange server. However, you must specify the name if the Exchange server is not the default or is a member of an MSCS. /LOGFile=logfilename Use the /logfile parameter to specify the name of the activity log file generated by TDP for Exchange. The logfilename variable identifies the name of the activity log file. If the specified log file does not exist, a new log file is created. If the specified log file exists, new log entries are appended to the file. The logfilename variable can include a fully-qualified path. However, if no path is specified, the log file is written to the TDP for Exchange installation directory. If the logfilename variable includes spaces, the entire /logfile parameter entry must be placed in double quotes. If the /logfile parameter is not specified, log records are written to the default log file, tdpexc.log. The /logfile parameter cannot be turned off. You always get logging. 100 Using Tivoli Data Protection for Microsoft Exchange Server
/LOGPrune=numdays No Use the /logprune parameter to disable log pruning or to explicitly request a prune of the log for one command run. By default, log pruning is enabled and performed once per day. The numdays variable represents the number of days to save log entries. By default, 60 days of log entries are saved in the prune process. You can use the TDP for Exchange GUI or the set command to change the defaults so that log pruning is disabled, or so that more or less days of log entries are saved. The command line user may use the /logprune parameter to override these defaults for one command run. Note that when the value of the /logprune variable numdays is a number in the range 0 to 9999, a prune is performed even if one has already been performed for the day. /TSMNODe=tsmnodename The tsmnodename variable refers to the TSM node name TDP for Exchange uses to log on to the TSM server. You can also store the node name in the TSM options file. The command line parameter overrides the value in the TSM options file if PASSWORDACCESS is set to PROMPT. This parameter is not valid when PASSWORDACCESS is set to GENERATE. /TSMOPTFile=tsmoptfilename The tsmoptfilename variable identifies the TDP for Exchange options file. The file name can include a fully qualified path name. If no path is specified, the directory where TDP for Exchange is installed is searched. If the tsmoptfilename variable includes spaces, the entire /tsmoptfile parameter entry must be placed in double quotes. /TSMPassword=tsmpassword The tsmpassword variable refers to the TSM password TDP for Exchange uses to log on to the TSM server. If you specified PASSWORDACCESS GENERATE in the TDP for Exchange options file, then the password need not be provided here because the one stored in the registry is used. However, in order to store the password in the registry, you must specify the TSM password the first time TDP for Exchange connects to the TSM server. If you do specify a password on the command line when PASSWORDACCESS GENERATE is in effect, then the command line value is ignored unless the password for this node has not yet been stored in the registry. In that case, the specified password is the one that is stored in the registry and used for the current command execution. If PASSWORDACCESS PROMPT is in effect, and a password value is not specified on the command line, then you are prompted for a password.the TSM password TDP for Exchange uses to log on to the TSM server can be up to 63 characters in length. Chapter 6. Day-to-day monitoring 101
You can use tdpexcc query tsm and specify positional and optional parameters for more precise view of the information than using GUI. You can also view the Object Name/Database name which is not possible from the GUI. The following screen presents the output of the tdpexcc query tsm command with specifying the storage group and type of the backup you want: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query TSM "First Storage Group" full Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Backup List ----------- Exchange Server Storage Group : ELBRUS : First Storage Group Backup Date Size A/I B/U Type Object Name/Database Name --------------------- ----------- --- -------- ------------------------- 03/30/2001 12:03:28 19.05MB A full 20010330120328 8,208.37KB Mailbox Store (ELBRUS) 6,160.36KB Public Folder Store (ELBRUS) In this example, only the active objects are displayed. If you want to see all active and inactive objects, you must specify the /all parameter. Only by using this command can you see the Object Name/Database name parameter, which you must use if you perform restore of incremental or any kind of inactivated backup. See Appendix F, Limitations of the GUI on page 147. 102 Using Tivoli Data Protection for Microsoft Exchange Server
Chapter 7. Restoring Exchange databases In this chapter we describe procedures to restore Exchange 5.5 as well as Exchange 2000 data. We go through tasks for restoring single items (messages, mailboxes and the like), and we describe the tasks involved in restoring Exchange databases from complete disasters. Examples in this chapter generally assume that circular logging has been disabled. See Section 2.1.2.1, Transaction logging on page 8 for information about circular logging. 7.1 Basic Information Store recovery from online backups In this section we describe the general procedures for restoring online backups using TDP for Exchange on Exchange 5.5 and Exchange 2000. The general database restore procedures are considered trivial in the respect that all system entities (hardware, operation system, Exchange, and so on) are working without any problems. The database requested for restore may or may not be corrupted, but for some reason, a restore is requested. Note We advise you to do a file level backup of the current transaction log files to disk before commencing a restore. This is just to protect against human errors making a bad situation worse. This is especially true when restoring Exchange 5.5 where there is less control of the recovery procedures. Imagine, for instance, that an operator is performing a restore on Wednesday. The last full backup was done Saturday, and since then, two additional incremental backups have been performed Monday and Tuesday. Accidently, the operator forgets to restore the Tuesday backup. The database engine will see a gap in the log files when running recovery and will not commit any transactions after the Monday backup. At the end of the recovery procedure, the existing log files are deleted, and there will now be no way to restore any data any newer than Tuesday. It may also be a good idea to make a safe copy of existing database files, though that may require a great deal of extra disk space. The copy may be desirable to have in case you realize that the backup, for which a restore is attempted, has been corrupted for some reason. If you can afford the splurge, try to keep disk space usage to less than 50% in order to be able to make database copies to local disk. Copyright IBM Corp. 2001 103
7.1.1 General restore procedures for Exchange 5.5 These are the steps performed at a normal Exchange 5.5 restore: 1. Stop the Information Store service. 2. Next, initiate the restore from the TDP for Exchange Graphical User Interface or Command Line Interface. An Exchange 5.5 restore will copy database files an transaction log files directly to the Exchange data directory. The restore process will create the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Resto re in Progress to signal that a restore is in progress. This key holds various data pertinent to the restoration and replay of transaction log files. 3. Restart the Information Store. 4. The restart of the Information Store service will automatically initiate the recovery process. The beginning of recovery event is logged in the application event log as event ID 106 followed by a series of 109 events and a final event ID 107. After a successful recovery, the Registry key mentioned in step two is deleted. 5. Restart services dependent on the Information Store service. 7.1.2 General restore procedures for Exchange 2000 These are the steps performed at a normal Exchange 2000 restore: 1. The Exchange manager must dismount the database or storage group to be restored before starting the restore process. The action is performed for the Exchange System Manager by right-clicking the appropriate database object(s) and select dismount. As opposed to the Exchange 5.5 procedure, the Information Store service must remain running. 2. Next, initiate the restore from the TDP for Exchange Graphical User Interface or Command Line Interface. TDP will initiate a session with the TSM server and as soon as the restore is beginning, the database engine is informed to enter restore mode. This event will appear in the application event log as event ID 204. 3. TDP for Exchange will start copying the.edb and.stm database files to their target paths. 4. The associated log files are copied to a separate temporary directory. The location of the directory is specified by the restore operator through the Command Line Interface (/templogrestorepath) or the TDP configuration file (default: tdpexc.cfg). If no location is specified, TDP for Exchange will use the TEMP Windows environment variable to define the location. Do not attempt to set the temporary log store path to coincide with the current storage group transaction log directory. 104 Using Tivoli Data Protection for Microsoft Exchange Server
5. When the files have been restored, a instance of ESE is started, specifically with the purpose of doing the restore. Information about the restore is written to a file called Restore.env. This file is used to replay the logs and finalize the restore. Restore.env replaces the Restore in Progress Registry key used for restoring Exchange 5.5. 6. Recovery is initiated and the restored log and patch files are applied to the restored database. The event of the process is written to the Windows application event log as event ID 301. 7. Current log files are replayed if requested. 8. Finally the database is dismounted from the temporary ESE instance and the temporary files are purged. 9. The database is mounted in the target storage group. Note that steps 6 to 9 can be skipped if the restore operator prefers to run recovery (replaying transaction logs) and database mount(s) manually. The replay of the current transaction logs in step 7 may be omitted. Manual recovery If recovery has not yet been run, the restored transaction logs and the Restore.env file are still to be found in the temporary restore directory. The contents of the Restore.env file can by queried by executing: eseutil /cm <path_name> In this command, <path_name> specifies the path to the temporary restore directory. Note that you must concatenate the path name specified from TDP for Exchange with the name for the storage group in order to get the complete path name. An example of the output follows: Chapter 7. Restoring Exchange databases 105
E:\Program Files\Exchsrvr\BIN>eseutil /cm "F:\RestoreTemp\ITSO SG" Microsoft(R) Exchange Server(TM) Database Utilities Version 6.0 Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved. Restore log file: F:\RestoreTemp\ITSO SG Restore Path: F:\RestoreTemp\ITSO SG Annotation: Microsoft Information Store Backup Instance: ITSO SG Target Instance: Restore Instance System Path: Restore Instance Log Path: Databases: 1 database(s) Database Name: ITSO 6147 Mailbox Store GUID: 2B965751-D2D1-4BF5-21BD4BF587DE909B Source Files: E:\Program Files\Exchsrvr\ITSO SG\ITSO 61 47.edb E:\Program Files\Exchsrvr\ITSO SG\ITSO 6147.stm Destination Files: E:\Program Files\Exchsrvr\ITSO SG\ITSO 61 47.edb E:\Program Files\Exchsrvr\ITSO SG\ITSO 6147.stm Log files range: E0100025.log - E0100029.log Last Restore Time: Wed Dec 31 16:00:00 1969 Recover Status: recovernotstarted Recover Error: 0x00000000 Recover Time: Wed Mar 28 16:52:44 2001 You can run a recovery replay of the transaction logs by executing: eseutil /cc <path_name> The utility will replay restored logs as well as the current logs by default. Use the /t switch if you do not want to replay the current logs. You cannot replay the current transaction log files if you installed an old backup creating a gap in the transaction log file sequence. Replaying a sequence with a gap will fail. It is possible to let TDP for Exchange GUI dismount the databases for you. 106 Using Tivoli Data Protection for Microsoft Exchange Server
Note If you attempt to use the same machine for alternate server recoveries (see 7.2.2, Alternate server restore on page 120) for Exchange 5.5 and Exchange 2000 and have had both versions installed on the same machine, you may have multiple versions of eseutil installed. Exchange 5.5 installs eseutil in the Windows system directory (\WINNT\System32) whereas Exchange 2000 will install eseutil in the Exchange binaries directory (\Program Files\exchsrvr\bin). Since the Windows system directory is in your PATH and the Exchange binaries directory is normally not, you will be using the Exchange 5.5 version if it is installed and you are not running the utility from the Exchange bin directory. Check which version you are running by executing: eseutil /? 7.1.3 Using the TDP for Exchange GUI for restoring Exchange The TDP for Exchange Graphical User Interface tdpexc.exe is invoked from Start -> Programs -> Tivoli Storage Manager -> TDP for MS Exchange Server - V 2-> Exchange Client GUI. Three parameters are applicable to the startup of the GUI. Use the /configfile and /tsmoptfile to specify alternative tdpexc.cfg and dsm.opt files for the setup of TDP. The /excserver parameter will overwrite the default Exchange server. This is important on a cluster environment. On a clustered system you can not use the default installed shortcut mentioned above. You must specify the Exchange virtual server name using the /excserver parameter for starting up the GUI properly. We recommend you to create a new shortcut including the startup parameter. The GUI itself is, like most Graphical User Interfaces, quite self-explanatory. Select the appropriate storage group(s) below the server view for your restore, choose your restore options, and click the Restore button. Chapter 7. Restoring Exchange databases 107
Figure 30. Restoring the ITSO 6147 Mailbox Store The Graphical User Interface includes some convenient features that will enable you to select the right files to restore. First of all, the Show Only Active Objects will filter the information about available backup sets on the TSM server so that inactivated backups do not show. Since most restores will be of the most recent backup the option is on by default. Choose Show All Objects if for some reason you wish to install an older backup that is no longer active. If installing inactivated backups, we recommend the usage of the Auto Select feature to assure the selection of all the corresponding backups for restore. The Auto select feature is helpful in finding the appropriate incremental backups logically corresponding to a certain full backup. This is illustrated in Figure 30, where the selection of the full backup of the ITSO 6147 Mailbox Store automatically selected the two incremental backups, that are newer than the full backup, for restoration too. The only restore option available for Exchange 5.5 is the option to Erase Existing Logs. This option will overwrite the existing log files and is used to get back to a known state of the database. The option will not be available if the restore is only partial. That is, for Exchange 5.5, that only the Private Information Store or the Public Information Store has been selected for restoration and not the other. The reason for this restriction is due to the fact 108 Using Tivoli Data Protection for Microsoft Exchange Server
that the public and private Information Stores are sharing the same set of transaction log files. The restore procedure for Exchange 2000 is a little more elaborate. Thus, there are also more restore options to choose from. The restore operator decides whether recovery should automatically be run after the data restore and whether the recovery should include the current log files or not. There is also an option to automatically mount the database after the restore. Though this option will remain selected if it was selected before choosing not to run recovery, TDP for Exchange will not attempt to mount the database if recovery is not being run. The process of manually running recovery is described in Section 7.1.2. 7.1.4 Using the TDP for Exchange CLI for restoring Exchange The Command Line Interface supports the same functionality as the graphical interface with respect to restore operations. The syntax is as follows: TDPEXCC RESTore * DIR IS sgname1,...,sgnamen backuptype where backuptype can be: FULL COPY INCRemental DIFFerential DBCopy dbname [/BUFFers=numbuffers] (default: 3) [/BUFFERSIze=buffersize] (default: 1024) [/CONFIGfile=tdpexc.cfg filename] (default: tdpexc.cfg) [/EXCSERVer=servername] (default: local exchange server) [/FROMEXCSERVer=servername] (default: local exchange server) [/LOGFile=tdpexc.log logfilename] (default: tdpexc.log) [/LOGPrune=60 n No] (default: 60) [/MOUNTWait=Yes No] (default: Yes) [/OBJect=object] (default: current active object) [/Quiet] [/TSMNODe=nodename] [/TSMOPTFile=dsm.opt filename] (default: dsm.opt) [/TSMPassword=password] Exchange Server 5.5 ONLY Options: [/ERASEexistingdata=No Yes] (default: No) [/PARTial=Public Private] (default: NONE) Exchange Server 2000 ONLY Options [/MOUNTDAtabases=No Yes] (default: No) [/PARTial=dbname1,..,dbnameN] (default: NONE) [/RECOVer=APPLYALLlogs APPLYRESToredlogs] (default: APPLYALLlogs) [/TEMPLOGRESTorepath=pathname] (default: TEMP environment var) Many of the options are rather trivial configuration options. See Chapter 4, Backing up Exchange databases for further details on configuration options. Analog to the GUI, some options only apply to Exchange 5.5 and some apply to Exchange 2000. Chapter 7. Restoring Exchange databases 109
Required parameters are the storage group and backup type. The /partial option must be used if not restoring the entire storage group. For Exchange 2000 use the /recover parameter for the last restore in order to initiate recovery. Either specify /recovery=applyalllogs to replay both restored and current transaction log files. Specify /recovery=applyrestoredlogs to only replay restored transaction log entries. If only replaying the restored logs, the next backup must be a full backup. You may choose not to run recovery using TDP and do it manually instead like described in Section Section 7.1.2. If you simply forgot to specify the parameter you can also choose to repeat the last restore with the correct parameters. If recovery is not run, the database will remain unmountable. Specify the /mountdatabase=yes to mount the Exchange 2000 database automatically after the restore. The location for the restored logs can be directed to a specific directory by specifying the /templogrestorepath option. This option is in particular useful when running manual recovery. If the path is not specified, the TEMP environment variable is used. Q290786 An Exchange 2000 bug was discovered during the development of TDP for Exchange. After a restore of an Exchange 2000 database, a full backup must be performed. Not doing so can result in data loss. We expect service pack 1 for Exchange 2000 to enforce this requirement at backup time. The /eraseexistingdata applies to Exchange 5.5. Use /eraseexistingdata=yes to erase existing transaction log files. Use the option to ensure to restore to a known consistent state. The default is not to erase existing transaction logs in which case those will be replayed when restarting the Information Store. The option is not valid for restoring differential or incremental backups. Since the private and public Information Stores share the same set of transaction logs, the option is not valid when restoring only one of the stores, either. If the restore process includes restoring multiple backup sets for instance, one full backup plus one or more incremental or differential backups it is important to restore the backups in the right order. Always restore the full or copy backup first to set the context of the restore and then restore any incremental and/or differential backups. The Graphical User Interface will take care of this automatically, but using the CLI you must ensure the right sequence yourself. If attempting to restore an incremental backup without already having restored a full backup the restore will fail and inform the operator that the restore environment has not been set. 110 Using Tivoli Data Protection for Microsoft Exchange Server
Also make sure to include all applicable incremental and differential backups. The recovery function will fail if an incremental backup is left out and thus resulting in a gap in the transaction log file sequence. Restoring inactive backups Use the /object parameter to specify the exact TSM objects when restoring inactivated backups. Use tdpexcc query TSM * /all to view all available backups, active as well as inactive. What s in a name? On Exchange 2000 it is very easy to change the name of a database. The database name is stored in Active Directory and it can be changed even while the database is in use. The possibility for changing the database name is supported by using the database globally unique identifier (GUID) to identify the database. The GUID will remain intact when changing the database name and since TDP is using the GUID behind the scene to store backup objects on the TSM server, it is still possible to restore a backup performed using the old database name overwriting the renamed database. This also means, that if you query TSM for all existing active and inactive backups for a certain storage group, you will see different names for the same database, if it has been renamed. However, to reduce possible confusion if you should choose to rename the database, we recommend that you do a full backup. When reviewing objects on the TSM server, we did actually experience to see some of the backups with the old name remain indicated as active versions even though the (renamed) database had been backed up again with a full backup. TDP did, however, still manage to find the active versions as expected. Chapter 7. Restoring Exchange databases 111
7.1.4.1 Restore example: Exchange 2000 full & incremental backups In order to perform the same restore as depicted in Figure 30, perform the following steps: 1. Unmount the database to be restored. Unlike the Graphical User Interface, the Command Line Interface does not provide an option for unmounting the database if it is mounted at the time the restore is initiated. In that case the restore will fail with an error message. 2. Restore the last full backup. Since we are not restoring the entire storage group, we must specify which database to restore using the /partial option: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc restore "ITSO SG" full /partial= "ITSO 6147 Mailbox Store" Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting Microsoft Exchange restore... Logging on to the Tivoli Storage Manager server, please wait... Beginning full restore of storage group ITSO SG <03/29/2001 10:43:04>, 1 of 1, to ITSO SG Full: 0 Read: 13664992 Written: 13664992 Rate: 981.95 Kb/Sec Restore of ITSO SG completed successfully. Total backups inspected: 1 Total backups requested for restore: 1 Total backups restored: 1 Throughput rate: 981.23 Kb/Sec Total bytes transferred: 13,664,992 Elapsed processing time: 13.60 Secs 112 Using Tivoli Data Protection for Microsoft Exchange Server
3. Restore the corresponding incremental backups and run recovery using restored as well as current transaction log files: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc restore "ITSO SG" incremental /r ecover=applyalllogs Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting Microsoft Exchange restore... Logging on to the Tivoli Storage Manager server, please wait... Beginning incr restore of storage group ITSO SG <03/29/2001 11:08:01>, 1 of 2, to ITSO SG Full: 0 Read: 10485930 Written: 10485930 Rate: 1,018.01 Kb/Sec Restore of ITSO SG completed successfully. Beginning incr restore of storage group ITSO SG <03/29/2001 11:19:56>, 2 of 2, to ITSO SG Full: 0 Read: 10485930 Written: 10485930 Rate: 970.72 Kb/Sec Recovery being run. Please wait. This may take a while... Restore of ITSO SG completed successfully. Total backups inspected: 2 Total backups requested for restore: 2 Total backups restored: 2 Throughput rate: 993.76 Kb/Sec Total bytes transferred: 20,971,860 Elapsed processing time: 20.61 Secs 4. Mount the restored database. Chapter 7. Restoring Exchange databases 113
7.1.4.2 Restore example: Inactive backup 1. Query TSM using tdpexcc query tsm to find the required backup object. The query command may produce a lot of data, depending on how many backups are still in TSM storage. The following screen dump shows a fraction only. Note the I indicating inactive backups. E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query tsm "ITSO SG" full /all Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Exchange Server Storage Group : ELBRUS : ITSO SG Backup List ----------- Backup Date Size A/I B/U Type Object Name/Database Name --------------------- ----------- --- -------- ------------------------- 04/02/2001 21:17:28 20.05MB I full 20010402211728 8,208.40KB ITSO 6147 Mailbox Store 7,184.51KB ITSO 6148 Mailbox Store 04/02/2001 21:30:00 20.05MB I full 20010402213000 8,208.40KB ITSO 6147 Mailbox Store 7,184.51KB ITSO 6148 Mailbox Store 04/04/2001 10:38:30 20.05MB I full 20010404103830 8,208.40KB ITSO 6147 Mailbox Store 7,184.51KB ITSO 6148 Mailbox Store 114 Using Tivoli Data Protection for Microsoft Exchange Server
2. Find the appropriate object number and initiate the restore after dismounting the databases. Apply only restored logs, use the path F:\RestoreTemp for restored log files, and mount the databases after the restore: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc restore "ITSO SG" full /object= 0010402213000 /recover=applyrestoredlogs /templogrestorepath=f:\restoretemp /mo ntdatabase=yes Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting Microsoft Exchange restore... Logging on to the Tivoli Storage Manager server, please wait... Beginning full restore of storage group ITSO SG <04/02/2001 21:30:00>, 1 of 1, to ITSO SG Full: 0 Read: 21021932 Written: 21021932 Rate: 800.77 Kb/Sec Recovery being run. Please wait. This may take a while... Restore of ITSO SG completed successfully. Total backups inspected: 1 Total backups requested for restore: 1 Total backups restored: 1 Throughput rate: 800.36 Kb/Sec Total bytes transferred: 21,021,932 Elapsed processing time: 25.65 Secs 7.1.5 Restoring Exchange in a cluster environment Just as there are special requirements when using TDP for Exchange to backup Exchange on a cluster, there are also certain aspects to take into account when restoring Exchange databases on a MSCS cluster. Basically, the restore procedures follow the procedures described for non-clustered servers. Only remember to use the /excserver and /fromexcserver to specify the Exchange virtual server when using the Command Line Interface. When using the Graphical User Interface, /excserver will suffice. Chapter 7. Restoring Exchange databases 115
Note Do not stop the Information Store service from the TDP for Exchange GUI if you are running Exchange 5.5 on MSCS. Starting and stopping services should be controlled by the Cluster Manager interface. Otherwise the service stop will trigger a fail-over. Here is an example showing how to restore the storage group First Storage Group on our MSCS virtual server Matterhorn: C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc restore "First Storage Group" full /excserver=matterhorn /fromexcserver=matterhorn /recover=applyalllogs Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting Microsoft Exchange restore... Logging on to the Tivoli Storage Manager server, please wait... Beginning full restore of storage group First Storage Group <04/02/2001 20:43:34 >,1of1, to First Storage Group Full: 0 Read: 17875686 Written: 17875686 Rate: 964.89 Kb/Sec Recovery being run. Please wait. This may take a while... Restore of First Storage Group completed successfully. Total backups inspected: 1 Total backups requested for restore: 1 Total backups restored: 1 Throughput rate: 964.19 Kb/Sec Total bytes transferred: 17,875,686 Elapsed processing time: 18.11 Secs 116 Using Tivoli Data Protection for Microsoft Exchange Server
7.2 Single item and mailbox recovery The database level is the highest degree of granularity for restoring Exchange databases with TDP for Exchange. Thus it is possible to restore either the entire directory, private information or public Information Store on Exchange 5.5. On Exchange 2000 individual databases within a storage group can be restored. These functions are very useful when a complete restore of a database is needed for instance due to a hard disk crash. Data does, however, get lost for many other reasons than simple hardware breakdowns. Human errors are often the primary source for unintended data deletion and in those cases, the data loss is often only a small fraction of the Exchange database. A number of possibilities exist for restoration of single items or mailboxes in Exchange databases: Deleted Item Retention (Exchange 2000: Keep deleted items) Keep deleted mailboxes setting (Exchange 2000 only) Alternate server restore 7.2.1 Deleted Item Retention feature Along with Exchange 5.5, Microsoft introduced the Deleted Item Retention feature for the Exchange Information Stores. In addition to the deleted item retention, Exchange 2000 also added the Keep deleted mailboxes setting. By postponing the actual deletion of data and initially just hiding deleted data, both features enable a possibility to retrieve data that has been accidently deleted by users or administrators. Note that deleted item retention is not enabled by default. See 2.1.3.1, Deleted item and mailbox retention on page 14 for setting up retention. 7.2.1.1 Recovering a deleted item Users can recover any deleted message, which has been deleted within the period specified by the deleted item retention settings. The procedure is simple (Figure 31): 1. In Outlook; go to the Deleted Items folder and select the Recover Deleted Items facility from the Tools menu bar. 2. Select the requested items from the list and click the Recover selected items button to restore. Chapter 7. Restoring Exchange databases 117
Figure 31. Recovering deleted items The deleted item recovery feature is supported by Outlook version 8.03 or later. If you have clients, which do not support the feature, or you for some other reason will allow a group of users (for instance Exchange administrators or a help desk) to be able recover items from any mailbox or public folder, that will be possible too. The user doing the recovery must have access to the mailbox from which the item is recovered. Mailbox access is set up through the Permissions tab on the mailbox object in Exchange 5.5. For Exchange 2000 you must use the Active Directory Users and Computers MMC (remember to set MMC for viewing Advanced features in order to be able to select the Exchange Advanced tab from the user properties sheet). If you are accessing multiple mailboxes through the same MAPI (Outlook) profile, you will normally be allowed to recover messages from your primary mailbox only. There is, however, a little Registry tweak that will allow item recovery from multiple mailboxes. Simply add the following REG_DWORD value on the Outlook client: HKEY_LOCAL_MACHINE_SOFTWARE\Microsoft\Client\Options\DumpsterAlwaysOn Then specify it to hold the value 1. 118 Using Tivoli Data Protection for Microsoft Exchange Server
7.2.1.2 Reconnecting mailboxes Exchange 2000 provides the additional feature of retention on mailbox deletion. If an administrator (intentionally or accidentally) deletes a user from Active Directory, any mailbox belonging to that user will remain in the Exchange database for a specified number of days (default: 30 days). The mailbox is simply marked for deletion which will be indicated by a red cross when viewed through the Exchange System Manager. (The Cleanup Agent may need to run before this is visible.) The same situation is applicable if an administrator deletes the mailbox from the Exchange Tasks wizard in Active Directory Users and Computers. The following procedure describes how to reconnect a mailbox to an Active Directory user: 1. In the Exchange System Manager navigate through the organizational view to the targeted mailbox: Administrative Group -> Servers -> Server -> Storage Group -> Mailboxes -> Mailbox 2. Right click on the mailbox and select Reconnect (See Figure 34 on page 127). 3. Select the appropriate user from the list provided. Note that the reconnect mailbox feature does not allow recovery of mailboxes that have been deleted from the Exchange System Manager. In those cases, the database needs to be restored. 7.2.1.3 Other alternatives The pst-files and ost-files may be used as alternative resorts for data restoration. If data has been copied from the Information Store to a pst-file, the pst-file may be used to restore data back to the Information Store. The procedure is simple. Connect to the server and the pst-file using Outlook, and copy data from one location to the other. Note that pst-files may be password protected. In some cases, ost-files can be used for data recovery too. If using an ost-file to restore data to the Information Store, it is important not to connect to the server before securing the data. Replication will start if the offline client connects to the server, potentially resulting in deleting the data from the ost-file too. Instead, start up the Outlook client in offline mode and copy the desired data to a pst-file. In order to use an ost-file to recover data offline, you must use the MAPI profile for which the ost-file was created. Chapter 7. Restoring Exchange databases 119
7.2.2 Alternate server restore If data, which is only a part of the Private or Public Information Store (for instance a single message or mailbox), needs to be restored without restoring the entire Information Store and the procedures for single item recovery described above are not applicable, then the entire Information Store must be restored in order to retrieve the requested data. It will, of course, not be possible to restore an old version of the Information Store in a production environment without overwriting the existing data. The restore must be performed to an alternate server for data retrieval. The procedures for doing alternate server restores on Exchange 2000 varies from doing it on Exchange 5.5. This is due to the fact that Exchange 2000 is keeping directory information in Active Directory and there can only exist one Exchange organization within the same forest. An alternate server for Exchange 2000 must be kept in a forest separate from the production forest. Exchange 5.5 on the other hand has got its own directory and an alternate server can be set up as a member of the same domain as long as it is not joined to an existing Exchange site. Alternate restore servers You may choose to have standby alternate restore servers ready to use. It is possible to use the same machine for both Exchange 5.5 and Exchange 2000 alternate server restores provided the old software is cleanly removed before switching from one version to another. Attempting to run Exchange 5.5 and 2000 on the same machine is asking for trouble and Exchange 5.5 will not even install if Exchange 2000 is already there. If you want to keep standby alternate servers ready and support Exchange 5.5 as well as Exchange 2000, we encourage you to keep the installations on separate machines. 7.2.2.1 Alternate server restore for Exchange 5.5 In this section we explain alternate server restore for Exchange 5.5. Preparation of the recovery server 1. Install the recovery server as a domain controller or a member server. You can use NT or Windows 2000, but use the same operation system as in the production environment including the same service packs. Since we chose to base our systems on Windows 2000, it fell natural to use Windows 2000 for our recovery server too. Since we are not doing a complete server restore and are not restoring the directory database but 120 Using Tivoli Data Protection for Microsoft Exchange Server
only the Information Store, the server name does not matter. However, the name must be different from any existing server or any server that has previously existed in the Exchange organization. 2. Install Exchange 5.5, including the appropriate service packs (the same as applied to the production server when the backup was performed). Create a new site with the same organization and site name as used on the production server. Note Keep the installation isolated from your production Exchange environment. Do not join an existing site. 3. Install and configure TDP for Exchange. Use the same nodename as the production server. 4. Install Outlook (or another Exchange client) unless you plan to connect to the restored database from another existing installation. Restore the Information Store 5. Initiate the restore from the TDP for Exchange GUI or CLI. Select the appropriate Information Store as described in the previous sections in this chapter. Select Erase Existing Logs (this option is only available if circular logging is disabled). 6. TDP for Exchange will have to shut down the Information Store service if it is running. Accept the shut down and installation will commence. 7. Restart the Information Store service when the restore has successfully finished. Extract mailbox data The Directory Store on the recovery server will initially not hold any data about the mailboxes in the restored Information Store. It is therefore necessary to update the Exchange 5.5 directory before we can gain access to data. 1. Logon to the recovery Exchange server. 2. Run the DS/IS consistency adjuster from the Exchange Administrator program. The utility is found under the advanced tab on the Server properties sheet. Select all the Operation options and All inconsistencies (See Figure 32). The adjustment may take a while, depending on the size of the Information Store. Chapter 7. Restoring Exchange databases 121
Figure 32. DS/IS Consistency Adjustment 3. Select the requested mailbox from the Recipients container when the consistency check has finished. Specify a Primary Windows NT Account on the General tab. Use any account for which you have access to; typically an administrator account. 4. Set up an Outlook profile on a client workstation or the recovery server itself to point to the mailbox on the restored server. Configure the profile to include the Personal Folder service. 5. Logon to the restored mailbox with Outlook. Select the requested items and copy them to the pst-file. If you are restoring an entire mailbox, the export facility (select File -> Import and export -> Export to a file -> Personal Folder File (.pst)) is probably a better option for moving data to a pst-file. If you need to export pst-files of entire mailboxes for many users, a tool like exmerge will help you doing bulk pst exports. 6. Send the pst-file to the requesting user. 122 Using Tivoli Data Protection for Microsoft Exchange Server
7.2.2.2 Alternate server restore for Exchange 2000 Exchange 2000 is flexible regarding database installation and location. There is support for restoring a database on a different server than the one it was backed up on. Setting up an alternate server for Exchange 2000 is also a little more complex and demanding than doing the same for Exchange 5.5. Due to the fact that Exchange 2000 is using Active Directory to store directory information and that there can only be one Exchange organization within the same AD forest, an alternate server installation must take place in a separate AD forest. Before starting the alternate server restore, you will need to gather some information about our production installation. You will need: The name of the organization and administrative group to which the database belongs The legacyexchangedn value for the administrative group to which the database belongs The name of the storage group The name of the database A little effort is needed to obtain the value of the legacyexchangedn 1 for the administrative group. Otherwise, the information is easily gathered from the Exchange System Manager. You can retrieve the value of the attribute using different kinds of Lightweight Directory Access Protocol (LDAP) tools. We used ADSI Edit, which is found among the support tools installable from the \Support\Tools directory of the Windows 2000 installation media. 1 The legacyexchangedn attribute is used to enable coexistence of Exchange 5.5 and Exchange 2000 within the same organization. Consult your Microsoft documentation for further details. Chapter 7. Restoring Exchange databases 123
Figure 33. Using ADSI Edit to get the legacyexchangedn Use ADSI Edit to browse the configuration container to the Services -> Microsoft Exchange -> organization_name -> Administrative Groups -> site_name and select the legacyexchangedn property to reveal its value. Figure 33 shows an example from our test lab. Preparation of the recovery server 1. Install Windows 2000 and service packs on the recovery server and use dcpromo to create a new forest. If you prefer to avoid the cost of having an additional server for recovery purposes, or you are in a hurry, you may choose to use an existing member server. Let dcpromo make it a DC for the new forest, and when the recovery is all over, demote it and move it back to the original domain. Choose a server and forest name not in use on your network. 124 Using Tivoli Data Protection for Microsoft Exchange Server
2. Your new forest will need a DNS server, and you may be prompted to install one during the creation of the forest. Install DNS. If the server is set up as a DCHP client, the installation will warn you that you should use a static IP address for the server. We think this is a good idea for any server, not just DNS servers. Anyhow, if you are installing the server with the single purpose of doing an alternate server restore of your Exchange database, you will probably be fine with a DHCP configured IP address as long as you know what it is. Use ipconfig /all to get your current IP address. Configure the recovery machine to be a DNS client to itself. It may also be a good idea to let the DNS server forward requests to your production DNS server. Otherwise, you will need at least the IP address of the TSM server. 3. Extend the Active Directory schema by running Exchange 2000 setup with the /forestprep switch. 4. Run the Exchange 2000 setup again. This time, install the Microsoft Exchange System Management Tools. DO NOT install Microsoft Exchange Messaging and Collaboration Services at this time. 5. Create a new administrative group by right-clicking the Administrative Groups container. Note: You may need to select the Display administrative groups from the Exchange organization object in order to be able to see and create new administrative groups at all. Apply the same name as on the production system to the new administrative group. The name is the OU part of the legacyexchangedn that was found during the preparation, in our case SJ. 6. Now, run the Exchange 2000 setup for the last time and select Microsoft Exchange Messaging and Collaboration Services for installation. Join the existing site created in the previous step. 7. Create a storage group and database with names matching the database being restored. There is no particular need to ensure the physical file names and locations are the same as on the original production server when restoring an online backup. The logical name on the other hand must be identical to the original. Restoring the database 1. Install TDP for Exchange on the recovery server. Configure the options file dsm.opt with the same nodename as used on the original server. 2. Set the This database can be overwritten by a restore option on the database object in Exchange System Manager. This is necessary because the GUID of the database does not match the GUID of the original database. Chapter 7. Restoring Exchange databases 125
3. Start up TDP for Exchange and connect to the TSM server. If this is the first time you connect to the TSM server from the recovery server, you will need the TSM password to connect to the TSM server. Select the appropriate backup to restore like described in the previous sections. Select your preferred choice for running recovery (automatically or manually), but do not run recovery on current log files. If you are using the Command Line Interface, be sure to specify the original server name for the /fromexcserver parameter. Extract mailbox data to a pst-file Like the Exchange 5.5 alternate server restore, the mailboxes in the restored mailbox store do not have any associated accounts configured. We therefore need to update Active Directory in order to connect to the mailboxes and export data for the production environment. We use the Reconnect feature as described in 7.2.1.2, Reconnecting mailboxes on page 119 for this purpose. See also Figure 34. If the reconnect feature is not available right away, you may choose to run the Cleanup Agent from Exchange System Manager. 1. In Exchange System Manager right-click on the mailbox object and select reconnect. 2. Select an appropriate user from the list for instance the administrative account you used to restore the mailbox store. If you need to go through step 1 and 2 for many mailboxes, it may be worth taking a closer look at the Mbconn utility in the \Support\Utils\I386 directory of the Exchange installation media. 3. Set up an Outlook profile for the user chosen in the previous step on a client workstation or the recovery server itself to point to the mailbox on the restored server. Configure the profile to include the Personal Folder service. 4. Logon to the restored mailbox with Outlook. Select the requested items and copy them to the pst-file. If you are restoring an mailbox, the export facility (select File -> Import and export -> Export to a file -> Personal Folder File (.pst)) is probably a better option for moving data to a pst-file. Again, as for Exchange 5.5, if you need to export pst-files of entire mailboxes for many users, a tool like exmerge may be handy. 5. Send the pst-file to the requesting user. 126 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 34. Reconnecting mailboxes 7.3 Disaster recovery A disaster recovery procedure assumes that your Exchange server is totally gone. All you have are the backups available on the TSM server. This means that before you even think of getting Exchange back in shape, you must get the server itself up and running. We will only cover the procedures required as overviews. The reinstallation and configuration of the operation system itself is out of the scope of this document. We suggest using, for instance, the TSM Backup/Archive client for backup and restore of the system configuration. Installation and configuration of TDP for Exchange is covered in detail in the previous chapters, as is the usage of the product. In order to perform successful complete server restores, you will need configuration information about the original server setup such as server name, IP addresses, and so on. Make it a good habit to keep up-to-date records for your systems and make system backups for all major changes. Microsoft has published many documents and white papers on the subject. We suggest you spend some time checking the links listed in Appendix I.5, Referenced Web sites and newsgroups on page 159. The following procedures assume that Active Directory is still intact and Exchange is not running on a domain controller. Chapter 7. Restoring Exchange databases 127
7.3.1 Disaster recovery for Exchange 5.5 Here is an overview of a complete server restore for Exchange 5.5: 1. Reinstall Windows 2000 as a stand-alone server in its own workgroup using the same machine name as the original server. Use hardware as close the original hardware as possible. Use the same version of Windows 2000 that was previously installed (Server, Advanced Server, or Data Center Server). Install the server as close to the original installation configuration as possible and specify the same drive names. 2. Install any service packs or hotfixes installed on the original server. 3. Install your backup software (for instance, the Backup/Archive client) and restore the system drive and other logical drives. 4. Restore the Windows 2000 System State from backup. This will rejoin the server to the domain using the original machine SID. Restoring the system state backup will require a reboot. 5. Reinstall Exchange using setup /r. This option informs setup to install Exchange without starting the services or initializing the directory. During setup, create a new site using the original organization and site name. Do not join existing site. As a precaution, set the Exchange services to manual startup. 6. Install and configure TDP for Exchange as on the original server. You may need to have the TSM administrator reset the node password in case the password is not available. 7. Start the Microsoft System Attendant service. 8. Select the latest backup from TDP for Exchange and initiate the restore. If, for some reason, you have newer usable log files available, copy those to the specific database directories (default: mdbdata and dsadata). 9. Start the Microsoft Exchange Directory, Information Store, and remaining services. 10.Check the event log for a successful restore and connect to mailboxes from client to verify system operation. 7.3.2 Disaster recovery for Exchange 2000 Here is an overview of a complete server restore for Exchange 2000: 1. Reinstall Windows 2000 as a stand-alone server in its own workgroup using the same machine name as the original server. Use hardware as close the original hardware as possible. Use the same version of Windows 2000 that was previously installed (Server, Advanced Server, or Data 128 Using Tivoli Data Protection for Microsoft Exchange Server
Center Server). Install the server as close to the original installation configuration as possible and specify the same drive names. 2. Install any service packs or hotfixes installed on the original server. 3. Install your backup software (for instance Backup/Archive client) and restore the system drive and other logical drives. 4. Restore the Windows 2000 System State from backup. This will rejoin the server to the domain using the original machine SID. Restoring the system state backup will require a reboot. 5. Reinstall Exchange using setup /DisasterRecovery. Assure that all originally installed components are selected with the Disaster Recovery option. Exchange must be installed to the same drive as originally. 6. The recovery installation of Exchange 2000 will finally prompt for a restore of the databases and a restart. Ignore this message. 7. Install and configure TDP for Exchange as on the original server. You may need to have the TSM administrator reset the node password in case the password is not available. 8. Make sure that the Exchange services are running and dismount the databases for restore. 9. If, for some reason, you have newer usable log files available, copy those to the appropriate directories. Select the latest backup from TDP for Exchange and initiate the restore. Follow the restoration procedures specified in the previous sections. Use your favorite method for running recovery. 10.Check the event log for a successful restore and connect to mailboxes from client to verify system operation. 7.4 Restoring Site Replication Service (SRS) database As described in 2.1.2.4, Site Replication Service and Key Management Service on page 11, the Site Replication Service (SRS) is always present in mixed 2 Exchange sites. The SRS database is responsible for interchanging directory information between Exchange 5.5 and Exchange 2000 and the database is constructed pretty much like the Exchange 5.5 directory database. Due to that, it may not be necessary to back up the SRS database so often. If you need to restore an older version of the SRS database, it will simply start backfilling data from up-to-date databases. 2 Exchange site containing both Exchange 2000 and Exchange 5.5 servers. Chapter 7. Restoring Exchange databases 129
Unlike the Exchange 2000 Information Store that can mount and unmount databases, the Site Replication Service will always attempt to mount the SRS database at startup. This has some implications with respect to restoring the SRS database. When restoring the SRS database, the service is required to be running, but the database is not allowed to be mounted. This will most certainly happen automatically if the database is corrupted at the start of the service. If this is not the case, you can force SRS into this state by removing the database files before starting the service. To restore the Site Replication Service database, follow these steps: 1. Stop the Microsoft Exchange Site Replication Service. 2. Move the content of the \exchsrvr\srsdata directory to another location. The old data can be deleted after a successful restoration. Note Some Microsoft documentation claims that the SRS database is found in \exchsrvr\dsadata. This seems to have changed, and the directory should be \exchsrvr\srsdata. 3. Restart SRS. 4. Check that the service successfully starts. The Windows application event log should now contain an entry specifying that SRS could not find the database and is in a semi-running state awaiting a database restore. The event ID is 1400. 5. Use TDP for Exchange to restore the SRS database. Though only the Command Line Interface supports backup of SRS, both the GUI and the CLI support restoration. Using the CLI, issue the following command: tdpexcc restore "SRS Storage" full /excapplication=srs /recover=applyrestoredlogs General restore options are also applicable to SRS restoration and the restore operation is analog to any other restore operation. Only specify SRS Storage as the storage group and the required /excapplication=srs. The recovery operation, which you may also choose to initiate manually by using eseutil and omitting the /recover option, will automatically restart SRS. If you want to replay the current SRS transaction logs, leave a copy of the transaction log files in the srsdata directory in step 2 and use the /recover=applyalllogs for the restore operation. Do not forget to check the restore being successful by checking the Windows application event log. 130 Using Tivoli Data Protection for Microsoft Exchange Server
Here is how we restored the SRS database in our test lab and ran recovery manually: E:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc restore "SRS Storage" full /excapplication=srs Tivoli Storage Manager Tivoli Data Protection for Microsoft Exchange Server Version 2, Release 2, Level 0.0 (C) Copyright IBM Corporation 1998, 2001. All rights reserved. Starting Microsoft Exchange restore... Logging on to the Tivoli Storage Manager server, please wait... Beginning full restore of storage group SRS Storage <04/03/2001 13:33:21>, 1 of 1, to SRS Storage Full: 0 Read: 7356714 Written: 7356714 Rate: 950.81 Kb/Sec Restore of SRS Storage completed successfully. Total backups inspected: 1 Total backups requested for restore: 1 Total backups restored: 1 Throughput rate: 949.42 Kb/Sec Total bytes transferred: 7,356,714 Elapsed processing time: 7.57 Secs E:\Program Files\Exchsrvr\BIN>eseutil /cc "F:\RestoreTemp\SRS Storage" /t Microsoft(R) Exchange Server(TM) Database Utilities Version 6.0 Copyright (C) Microsoft Corporation 1991-2000. All Rights Reserved. Restore log files: F:\RestoreTemp\SRS Storage Target Instance: Operation completed successfully in 2.113 seconds. If you are completely out of luck and have no backup of the SRS database, you may still be able to recover by deleting and recreating the SRS service. Note that this is only possible if there is another Exchange 2000 server present in the site. Exchange 2000 database (including SRS database) recovery procedures are covered in: http://www.microsoft.com/technet/exchange/dbrecovr.asp Chapter 7. Restoring Exchange databases 131
7.5 Restoring Key Management Service (KMS) database TDP for Exchange supports backup and restore of the Key Management Service (KMS) database. Backup is only supported from the Command Line Interface, whereas restore can be performed from the GUI too. In order to perform a backup, KMS must be up and running. The backup syntax is as follows: tdpexcc backup "Key Management Service" full copy diff incr /EXCAPPlication=kms The KMS database can be restored from the Graphical User Interface like any other database. If restored from the Command Line Interface the /excapplication=kms switch must be specified. For example: tdpexcc restore "Key Management Service" full /EXCAPPlication=kms We restricted the scope of our test lab to exclude KMS due to time constraints. For more information on how to backup and restore KMS, consult the following TechNet article: http://www.microsoft.com/technet/exchange/dbrecovr.asp 132 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix A. Lab environment This appendix shows the lab environment used to produce this redbook, as depicted in Figure 35. The TSM server is running on AIX 4.3. Shasta, Elbrus and K2 are using Windows 2000 Server, and the cluster is running Windows 2000 Advanced server. All Windows 2000 installation have Service Pack 1 installed. Shasta Exchange 5.5 SP4 Matterhorn Exchange 2000 Cluster K2 Domain Controller Active Directory DNS Elbrus Exchange 2000 LAN TCP/IP Brazil TSM server 4.1 SAN FCP SAN Datagateway 3570 Library Figure 35. Exchange lab environment Domain: Exchange Organization: Administrative Group/Site: uphi.sky UPHI SJ Copyright IBM Corp. 2001 133
Rationale for the lab environment We wanted to test TDP for Exchange for Exchange 5.5 as well as Exchange 2000. We set up a mixed Exchange site containing both Exchange 5.5 and Exchange 2000 - an environment we believe is not an uncommon constellation for many organizations on the migration path from Exchange 5.5 to Exchange 2000. Setting up a mixed environment also enabled us to test the facilities for backing up and restoring the SRS database. Including a clustered Exchange installation made it possible to test the particularities and issues with respect to using TDP for Exchange on a cluster. 134 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix B. Best practices In this appendix we provide a short list of practices that we consider essential for proper Exchange data protection: Disable circular logging. Place transaction logs on disks separate from the databases themselves. Perform test restores and fire drills. Back up the entire system when applying changes to the system. Monitor logs (Windows event logs, TDP and TSM logs). Set up dedicated equipment for a recovery lab. Record configuration information. Use a redundant disk configuration. Disable SCSI write cache unless backed up by battery. Deploy UPS. Use the TSM or another scheduler to automate backups. Configure TSM management classes to support your backup strategy and automatic expiration. Back up Exchange using TDP for Exchange installed locally. Copyright IBM Corp. 2001 135
136 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix C. Quick start / checklist This appendix is intended to show you the easiest way to install, configure, and perform backups and restores using TDP for Microsoft Exchange. In this appendix we cover only the Exchange 2000 server. C.1 Checklist Before performing installation of TDP for Exchange, check whether you meet the following requirements: 1. You have appropriate hardware: Intel Pentium Processor at least 166 MHz or equivalent, 8 MB of free disk space, at least 48 MB of RAM (96 MB or more is highly recommended). If you plan on installing TDP in a clustered environment, consult the Microsoft documentation about hardware requirements. 2. You have the Microsoft Windows 2000 Server, Advanced Server or Datacenter Server installed with Service Pack 1 (SP1) or later. 3. The Exchange Server 2000 is installed. If you plan on using Exchange in a clustered environment, follow Microsoft instructions about cluster installation. 4. The TSM server is installed. Your TSM administrator has registered the node for you and supplied you with password and communication method to access the server. C.2 Installation The installation of TDP for Exchange must be performed with an account having administrator privileges to the local system. TDP for Exchange must be installed on the same machine on which Exchange 2000 is installed. Follow these steps: 1. Start the setup program from the Run command from the Start menu. Choose the installation path and follow the installation instructions contained in the prompt windows. If you are setting up TDP in a clustered environment, repeat the same on the second node. Copyright IBM Corp. 2001 137
2. Specify the node name, password method, and the TSM server in your TDP for Exchange options file - dsm.opt file, which is located in the directory in which TDP for Exchange is installed. You can edit this file by using a text editor. For clustering, the options file on both nodes must be identical, and the TDP for Exchange GUI must be invoked by specifying the name of the Virtual Exchange server (/excserver parameter). C.3 Performing backups After installation of TDP for Exchange and connecting to the TSM server, you are ready to perform backups. You can use the graphical user interface or command line interface. If you use the command line interface, you can obtain help about the command syntax and options by typing: tdpexcc help If you use Graphical User Interface, choose the Server and Storage groups you want to back up. There are five different types of backups: Full backup Make sure you perform at least one full backup before performing any differential or incremental backups; for restore you will need only one backup. Incremental backup Performs a backup of the transaction log files and then delete them; however, for restore, you will need the last full backup and all incremental backups. Differential backup Performs a backup of transaction logs and does not delete them; for restore you will need the last full backup and the latest differential backup. Copy backup This is similar to the full backup, without affecting transaction logs. Database copy backup This type of backup is valid only for Exchange 2000 and performs a full backup of a particular Exchange database without interfering with transaction logs. Performing incremental and differential backups requires Exchange circular logging to be disabled. It is better not to mix incremental with differential backups. 138 Using Tivoli Data Protection for Microsoft Exchange Server
C.4 Performing restore The Exchange server must be running, but the Exchange database which is restored must be dismounted. If you perform a restore by using the GUI, you will be prompted to dismount the database or cancel the restore operation. If you are using CLI, you must manually stop any running services. You may obtain help for the Command Line Interface syntax by typing: tdpexcc help When performing database restoration, you may specify whether to reply the restored logs only or reply the restored and current logs (this will give you the most recent state of the database which is restored). C.5 Solving problems There are several sources of information which you can view in case of problems. You can monitor TSM server activity log, or if you do not have rights, the TSM administrator can do it. Also, TDP for Exchange writes log information to the tdpexec.log file, which is by default in the directory where TDP for Exchange is installed. TSM API logs information to the dsierror.log this information concerns API errors, not backup statistics. Exchange server writes information to the Windows Event Log. Appendix C. Quick start / checklist 139
140 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix D. Gotchas In this appendix we list some particularities, unexpected behaviors, and minor issues that we have come across during our work with TDP for Exchange. D.1 Exchange 5.5 backups invoked from Terminal Service client hangs TDP for Exchange does not work if invoked from a Terminal Server session on a Window 2000 installation of Exchange 5.5 SP3. The backup client simply hangs. The same is the case for NTBackup. Solution: Install service pack 4 to solve the problem. Links to the latest Exchange service packs are found at: http://www.microsoft.com/exchange D.2 Using NTBackup in Window 2000 to Backup Exchange 5.5 When using NTBackup to back up Exchange 5.5 on Windows 2000, there seems to be no Exchange organization to select from when specifying the content of the backup (see Figure 36). Figure 36. No Exchange organization available for NTBackup Copyright IBM Corp. 2001 141
Solution: Double-click the text Microsoft Exchange to make the Organization tree appear. D.3 Perform a full backup after restoring During the development of TDP for Exchange, the following bug was identified: After restoring an Exchange 2000 database, a full backup is required. If you do not perform a full backup before performing any incremental or differential backups, loss of information is possible. The problem is due to limitations in the database storage engine. Solution: Exchange 2000 has no restrictions of type of backup you perform, and it is up to administrator to perform recoverable backups. Service Pack 1 for Exchange 2000 is expected to include an enforcement of the requirement for a full backup after restoration. Note Perform a full backup on all restored storage groups as soon as possible. 142 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix E. Troubleshooting When a problem occurs, the most important step in finding a solution to the problem is diagnosing the situation and, in particular, finding out where this problems happens and where it does not happen. In most cases this will help you to solve the problem. The following list presents you with some clues which can be useful in finding the source of the problem: All systems or particular systems Analyze whether the problem concerns all or individual systems. If only some systems are affected, probably the problem is in their configuration. All servers or particular servers Analyze whether the problem concerns all or individual servers. If only some servers are affected, probably the problem is in their configuration All storage groups or just one storage group If only one storage group is affected try to find any differences in configuration for this storage group. Consistent or random Consider when the problem happens. Constant or intermittent Analyze the situation causing the problem. Scheduled or manual If the problem happens when performing scheduled backups, perhaps there is something wrong with the configuration of the scheduling. Try to manually execute the command file which performs the backup. Exchange 5.5 or Exchange 2000 Command Line Interface or Graphical User Interface Consider whether this problem pertains to CLI or GUI execution. Backup / Query / Restore Inspect when the problem happens and whether it concerns the restore, query or backup process. Exchange or TSM Be aware of the correct identification of the problem whether it is problem of Exchange itself or TSM problem. LAN or SAN If the problem happens only when performing the backups and restores by using the SAN, check the EnableLanFree parameter in the options file and SAN configuration. Clustered or non-clustered Examine the problem in both clustered and non-clustered environments and check the ClusterNode parameter in the options file. Failed over or not failed over Copyright IBM Corp. 2001 143
When considering these possibilities, try to see what is the same and what is different, and try to create the pattern of the situation causing the problem. The following is a list of items that may help solve your problem: Windows Event Log Many errors are there. Trace the Event log every time you have a problem. Names See whether the spelling and case are correct and whether you use special characters. Permissions Check if the appropriate permissions are used on the Exchange server, the Windows system and the cluster. Check Exchange, TDP for Exchange, TSM, cluster configurations and Service pack levels. Examine Scheduler scripts. Consider the order of actions you issued and the events you had in response to your actions. There is an undocumented parameter which you can use either by the Command Line Interface or the Graphical User Interface. It gives you detailed trace information on the action you perform. If you use this parameter, trace information will be written to the trace file or sent to the console. If you want this information to be sent to the file, specify: /TraceFile=[path\]FileName Either as a parameter of a command issued on the Command Line Interface or specify it as a parameter of the shortcut invoking GUI; the default path is the directory where TDP for Exchange is installed; the default name is tdpexc.trc. If this file does not exist, a new one will be created. If the file exists, the new events are appended to the file. /TraceFlag=[-]Flag{,[-]Flag} The default is all; all sets most likely set of trace flags; detailed sets all trace flags. For 90% of the cases: /traceflag=all is fine. For example, if you want to trace the backup process by using the Command Line Interface and send trace information to a file, issue the command: tdpexcc backup * full /tracefile=tdpexc.trc /traceflag=all If you want to use the Graphical User Interface, modify the shortcut as is shown on Figure 37. This shortcut is located in x:\documents and Settings\All users\start Menu\Programs\Tivoli Storage Manager\TDP for MS Exchange. 144 Using Tivoli Data Protection for Microsoft Exchange Server
Figure 37. Modifying the GUI shortcut In this way, when you perform backups and restores from the GUI, the trace information will be written to the tdpexc.trc file in the directory where TDP for Exchange is installed. Appendix E. Troubleshooting 145
146 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix F. Limitations of the GUI The functionalities of the Graphical User Interface and the Command Line Interface are pretty much the same. The differences are minor. However, some things are not possible from the GUI. F.1 Backing up the SRS database It is not possible to use the Graphical User Interface to back up the Site Replication Service (SRS) database. SRS must be backed up using the CLI. The syntax is as follows: tdpexcc backup "SRS Storage" full copy incr diff /EXCAPPlication=srs The SRS database can be restored from either the GUI or the CLI. F.2 Backing up the KMS database It is not possible to use the Graphical User Interface to backup the Key Management Service (KMS) database. KMS must be backed up using the CLI. The syntax is as follows: tdpexcc backup "Key Management Service" full copy incr diff /EXCAPPlication=kms The KMS database can be restored from either the GUI or the CLI. F.3 Viewing the TSM object name It is not possible to view the TSM object name for backup objects through the Graphical User Interface. When restoring incremental or any kind of inactivated backups through the CLI, the /object parameter must be used to specify the backup object to be restored. Use tdpexcc query tsm to retrieve object names. Copyright IBM Corp. 2001 147
148 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix G. TSM object names This appendix provides an overview of the object naming structure that TDP for Exchange version 2.2 uses when storing objects on the TSM server. The object names are different from the ones used in the previous version of TDP for Exchange. Filespace name ExchangeServerName\StorageGroupName High-level qualifier \ObjectKeyword[\ObjectIndex][\DatabaseName] ObjectKeyword is: meta, data, or logs ObjectIndex is: xxxx (xxxth file within database data object only) yyyymmddhhmmss for incremental backups Low-level qualifier \Type Type is: full, copy, diff, incr, or dbcopy Some examples of the new TSM object names from the test lab Full backup ELBRUS\ITSO SG\meta\full ELBRUS\ITSO SG\data\0000\ITSO 6147 Mailbox Store \full ELBRUS\ITSO SG\data\0001\ITSO 6147 Mailbox Store \full ELBRUS\ITSO SG\data\0000\ITSO 6148 Mailbox Store \full ELBRUS\ITSO SG\data\0000\ITSO 6148 Mailbox Store \full ELBRUS\ITSO SG\logs\full Incremental backup ELBRUS\ITSO SG\meta\20010406104905\incr ELBRUS\ITSO SG\logs\20010406104905\incr Copyright IBM Corp. 2001 149
Differential backup ELBRUS\ITSO SG\meta\diff ELBRUS\ITSO SG\logs\diff 150 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix H. Special notices This publication is intended to help Exchange administrators to understand how to use TDP for Microsoft Exchange Server and to help TSM administrators to understand how to back up Microsoft Exchange Server. The information in this publication is not intended as the specification of any programming interfaces that are provided by TDP for MS Exchange. See the PUBLICATIONS section of the IBM Programming Announcement for TDP for MS Exchange for more information about what publications are considered to be product documentation. References in this publication to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent program that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program or service. Information in this book was developed in conjunction with use of the equipment specified, and is limited in application to those specific hardware and software products and levels. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Corporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The information contained in this document has not been submitted to any formal IBM test and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee Copyright IBM Corp. 2001 151
that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries: e (logo) IBM Redbooks Redbooks Logo AIX AT Domino Lotus Lotus Notes Magstar Netfinity Notes OS/2 OS/390 RS/6000 S/390 SP, SP1, SP2 The following terms are trademarks of other companies: Tivoli, Manage. Anything. Anywhere.,The Power To Manage., Anything. Anywhere.,TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli, and Tivoli Enterprise are trademarks or registered trademarks of Tivoli Systems Inc., an IBM company, in the United States, other countries, or both. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S. C-bus is a trademark of Corollary, Inc. in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. PC Direct is a trademark of Ziff Communications Company in the United States and/or other countries and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States and/or other countries. 152 Using Tivoli Data Protection for Microsoft Exchange Server
UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, and service names may be trademarks or service marks of others. Appendix H. Special notices 153
154 Using Tivoli Data Protection for Microsoft Exchange Server
Appendix I. Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. I.1 IBM Redbooks For information on ordering these publications see How to get IBM Redbooks on page 161. Book Title Publication Number Tivoli Enterprise Performance Tuning Guide SG24-5392 Tivoli Storage Manager Version 3.7: Technical Guide SG24-5477 A Project Guide for Deploying Tivoli Solutions SG24-5310 ADSM Operation and Management with TME 10 SG24-2214 ADSM Server for Windows NT Configuration and Recovery Examples SG24-4878 ADSM Server-to-Server Implementation and Operation SG24-5244 ADSM/6000 on 9076 SP2 GG24-4499 All About Tivoli Management Agents SG24-5134 An Industry Around the Tivoli Framework: Examples from the 10/Plus Association SG24-2122 An Introduction to Tivoli Enterprise SG24-5494 An Introduction to Tivoli's TME 10 SG24-4948 Backup, Recovery, and Availability with DB2 Parallel Edition on RISC/6000, SG24-4695 ADSM Client Disaster Recovery: Bare Metal Restore SG24-4880 Creating Custom Monitors for Tivoli Distributed Monitoring SG24-5211 Deploying a Tivoli Infrastructure in Large-Scale Environments SG24-5210 Deploying the Tivoli Storage Manager Client in a Windows 2000 Environment SG24-6141 Designing Tivoli Solutions for End-to-End Systems and Service Management SG24-5104 Getting Started with Tivoli Storage Manager: Implementation Guide SG24-5416 High Availability Scenarios for Tivoli Software SG24-2032 Implementing Tivoli Manager for Windows NT SG24-5519 Implementing Tivoli Remote Control in Large Enterprises SG24-5125 Laying the Foundation for Tivoli Modules SG24-5379 Managing Domino/Notes with Tivoli Manager for Domino, Enterprise Edition, Version 1.5 SG24-2104 Managing RDBMS Servers With Tivoli SG24-5240 Managing SAP R/3 with Tivoli SG24-5298 New Features in Tivoli Software Distribution 3.6 SG24-2045 Problem Management Using Tivoli Service Desk and the TEC SG24-5301 TEC Implementation Examples SG24-5216 Tivoli Enterprise Internals and Problem Determination SG24-2034 Tivoli Enterprise Management Across Firewalls SG24-5510 Tivoli Service Desk V6.0 - IT Infrastructure Planning Guide SG24-5312 Tivoli Storage Management Concepts SG24-4877 TME 10 Cookbook for AIX: Systems Management and Networking Applications SG24-4867 TME 10 Deployment Cookbook: Courier and Friends SG24-4976 Copyright IBM Corp. 2001 155
Book Title TME 10 Deployment Cookbook: Inventory and Company TME 10 Framework Version 3.2: An Introduction to the Lightweight Client Framework TME 10 Inventory 3.2: New Features and Database Support Using ADSM to Back Up and Recover Microsoft Exchange Server Using ADSM to Back Up Databases Using Databases with Tivoli Applications and RIM Using Tivoli Software Installation Service for Mass Installation Using Tivoli Storage Manager to Back Up Lotus Notes Using Tivoli to Manage a Large-Scale SAP R/3 Environment Using TSM in a Clustered Windows NT Environment Windows NT Backup and Recovery with ADSM Publication Number SG24-2120 SG24-2025 SG24-2135 SG24-5266 SG24-4335 SG24-5112 SG24-5109 SG24-4534 SG24-5500 SG24-5742 SG24-2231 I.2 IBM Redbooks collections Redbooks are also available on the following CD-ROMs. Click the CD-ROMs button at ibm.com/redbooks for information about all the CD-ROMs offered, updates and formats. CD-ROM Title IBM Networking Redbooks Collection IBM Transaction Processing and Data Management Redbooks Collection IBM Lotus Redbooks Collection Tivoli Redbooks Collection IBM Netfinity Hardware and Software Redbooks Collection IBM RS/6000 Redbooks Collection (PDF Format) IBM Application Development Redbooks Collection IBM Enterprise Storage and Systems Management Solutions Collection Kit Number SK2T-6022 SK2T-8038 SK2T-8039 SK2T-8044 SK2T-8046 SK2T-8043 SK2T-8037 SK3T-3694 I.3 Tivoli publications Book Title These publications are also relevant as further information sources: Tivoli Asset Management Inventory Integration System Administration Tivoli Asset Management Inventory Integration User s Guide Tivoli Asset Management System Administrator s Guide Tivoli Asset Management User s Guide Tivoli Change Management System Administrator s Guide Publication Number GC31-5204 GC32-0288 GC31-5195 GC31-5194 GC31-5188 156 Using Tivoli Data Protection for Microsoft Exchange Server
Book Title Tivoli Change Management User s Guide Tivoli Data Protection for Informix V3R7: Installation and User s Guide Tivoli Data Protection for Lotus Domino for UNIX V1R1: Installation and User s Guide Tivoli Data Protection for Lotus Domino for Windows NT V1R1: Installation and User s Guide Tivoli Data Protection for Microsoft Exchange Server: Installation and User s Guide ADSMConnect Agent for Lotus Notes on AIX Installation and User s Guide ADSMConnect Agent for Lotus Notes on Windows NT Installation and User s Guide ADSMConnect Agent for Microsoft Exchange Server Installation and User s Guide ADSMConnect Agent for Microsoft SQL Server Installation and User s Guide ADSMConnect Agent for Oracle Backup on AIX Installation and User s Guide ADSMConnect Agent for Oracle Backup on HP-UX Installation and User s Guide ADSMConnect Agent for Oracle Backup on Sun Solaris Installation and User s Guide ADSMConnect Agent for Oracle Backup on Windows NT Installation and User s Guide Tivoli Decision Support 2.1 Administrator Guide Tivoli Decision Support 2.1 Installation Guide Tivoli Decision Support 2.1 User s Guide Tivoli Distributed Monitoring 3.6 Collection Reference Tivoli Distributed Monitoring 3.6 Release Notes (supplied with the product) Tivoli Distributed Monitoring 3.6.1 Release Notes (supplied with the product) Tivoli Distributed Monitoring for OS/390 V3.6.1 Tivoli Distributed Monitoring User s Guide 3.6 Tivoli Framework 3.6 User s Guide Tivoli Framework 3.6.1 Release Notes (supplied with the product) Tivoli Inventory 3.6.1 Release Notes (supplied with the product) Tivoli Inventory for OS/390 V3.6.1 Release Notes (supplied with the product) Tivoli Problem Management Distributed Data Manager System Administrator s Guide Tivoli Problem Management System Administrator s Guide Tivoli Problem Management User s Guide Tivoli Service Desk Administration User s Guide Tivoli Service Desk Installation Guide Tivoli Software Distribution 3.6 Release Notes (supplied with the product) Tivoli Software Distribution 3.6.1 Release Notes (supplied with the product) Tivoli Software Installation Service 3.6.1 Release Notes (supplied with the product) Tivoli Software Installation Services 3.6 User s Guide Tivoli Storage Manager for AIX Version 3.7 Administrator s Guide Tivoli Storage Manager for AIX Version 3.7 Administrator s Reference Tivoli Storage Manager for AIX Version 3.7 Quick Start Tivoli Storage Manager for AS/400 Version 3.1.2 Administrator s Guide Publication Number GC31-5190 SH26-4095 SH26-4088 GC26-7320 SH26-4110 SH26-4067 SH26-4065 SH26-4071 SH26-4069 SH26-4061 SH26-4073 SH26-4063 SH26-4086 GC32-0437 GC32-0438 GC32-0436 SC31-5118 GI10-3023 GI10-8021 GI10-8043 GC31-8382 GC31-8433 GI10-8014 GI10-8018 GI10-8048 GC31-5184 GC31-5173 GC31-5175 GC31-5205 GC31-5167 GI10-3014 GI10-8019 GI10-8015 GC31-5121 GC35-0368 GC35-0369 GC35-0367 GC35-0315 Appendix I. Related publications 157
Book Title Tivoli Storage Manager for AS/400 Version 3.1.2 Administrator s Reference Tivoli Storage Manager for AS/400 Version 3.1.2 Quick Start Tivoli Storage Manager for HP-UX Version 3.7 Administrator s Guide Tivoli Storage Manager for HP-UX Version 3.7 Administrator s Reference Tivoli Storage Manager for HP-UX Version 3.7 Quick Start ADSTAR Distributed Storage Manager for MVS Version 3.7 Administrator s Guide ADSTAR Distributed Storage Manager for MVS Version 3.7 Administrator s Reference ADSTAR Distributed Storage Manager for MVS Version 3.7 Quick Start ADSM for OS/2 Version 3.1 Messages Tivoli Storage Manager for Sun Solaris Version 3.7 Administrator s Guide Tivoli Storage Manager for Sun Solaris Version 3.7 Administrator s Reference Tivoli Storage Manager for Sun Solaris Version 3.7 Quick Start Tivoli ADSM for VM Version 3.1 Quick Start Tivoli Storage Manager for Windows NT Version 3.7 Administrator s Guide Tivoli Storage Manager for Windows NT Version 3.7 Administrator s Reference Tivoli Storage Manager for Windows NT Version 3.7 Quick Start Tivoli Storage Manager Version 3.7 AFS/DFS Backup Clients Tivoli Storage Manager Version 3.7 Installing the Clients Tivoli Storage Manager Version 3.7 Messages Tivoli Storage Manager Version 3.7 Reference Cards for the Backup-Archive Clients Tivoli Storage Manager Version 3.7 Trace Facility Guide Tivoli Storage Manager Version 3.7 Using the Application Programming Interface Tivoli Storage Manager Version 3.7 for NetWare Using the Backup-Archive Client Tivoli Storage Manager Version 3.7 for UNIX Using the Backup-Archive Client Tivoli Storage Manager Version 3.7 for Windows Using the Backup-Archive Client TME 10 Enterprise Console 3.6.1 Release Notes (supplied with the product) TME 10 Enterprise Console Adapters Guide Version 3.6 TME 10 Enterprise Console Rule Builder s Guide Version 3.6 TME 10 Enterprise Console User s Guide Version 3.6 TME 10 Framework 3.6 Planning & Installation Guide TME 10 Framework 3.6 Reference Manual TME 10 Framework Release Notes Version 3.6 TME 10 Inventory 3.6 Release Notes (supplied with the product) TME 10 Inventory 3.6 User s Guide TME 10 Software Distribution 3.6 AutoPack Guide TME 10 Software Distribution 3.6 Reference Manual TME 10 Software Distribution 3.6 User s Guide TME 10 Tivoli/Plus ADSM User's Guide Tivoli Framework Version 3.7 User s Guide Publication Number GC35-0316 GC35-0317 GC35-0371 GC35-0372 GC35-0370 GC35-0277 GC35-0278 GC35-0276 SH35-0133 GC35-0374 GC35-0375 GC35-0373 GC35-0351 GC35-0380 GC35-0381 GC35-0379 SH26-4106 SH26-4102 GC35-0382 SX26-6021 SH26-4104 SH26-4107 SH26-4100 SH26-4105 SH26-4101 GI10-8020 SC31-8507 SC31-8508 GC31-8506 SC31-8432 SC31-8434 GI10-3028 GI10-3011 GC31-8381 GC32-0294 SC31-8331 GC31-8330 GC31-8405 GC31-8433 158 Using Tivoli Data Protection for Microsoft Exchange Server
I.4 Other resources Microsoft Knowledge Base Articles: Q266367 - XADM: Extensible Storage Engine 98 Error Codes -1051 to -999999 Q266361 - XADM: Extensible Storage Engine 98 Error Codes 0 to -1048 Q273837 - XGEN: Exchange Server and Exchange 2000 Server Acronyms Q258243 - XADM: How to Back Up and Restore an Exchange 2000 Server Computer Q232938 - XADM: The "Last Backup Set" Check Box and Hard Recovery in Exchange 2000 Q267273 - XADM: How to Install the Key Management Server I.5 Referenced Web sites and newsgroups I.5.1 Web sites These Web sites are relevant information sources regarding backup and restore of Microsoft Exchange: Disaster recovery concepts for Microsoft Exchange 5.5 http://www.microsoft.com/technet/exchange/chapt09.asp Exchange 2000 Server database recovery http://www.microsoft.com/technet/exchange/dbrecovr.asp Backup and restore basics for Microsoft Exchange http://www.microsoft.com/technet/exchange/chapt12.asp Disaster recovery for Microsoft Exchange 2000 Server http://www.microsoft.com/exchange/techinfo/e2krecovery.htm Individual mailbox recovery for Microsoft Exchange 2000 Server http://www.microsoft.com/exchange/techinfo/mailboxrecover.htm Naming Convention Restrictions http://www.microsoft.com/technet/exchange/manuals/planning/apbchar.asp Backup and Restore http://www.microsoft.com/technet/exchange/manuals/planning/c14back.asp Appendix I. Related publications 159
Installing Exchange http://www.microsoft.com/technet/exchange/manuals/planning/c19inst.asp Backing Up and Restoring Data http://msdn.microsoft.com/library/psdk/exchserv/infostor_6gdd.htm Exchange 2000 Server How to guide http://www.microsoft.com/technet/exchange/howtogde.asp I.5.2 Newsgroups Microsoft has a number of newsgroups concerning Microsoft Exchange. Check the news server msnews.microsoft.com and look for the groups starting with microsoft.public.exchange. For information about TSM, check: http://msgs.adsm.org/cgi-bin/get/adsm-current.html 160 Using Tivoli Data Protection for Microsoft Exchange Server
How to get IBM Redbooks This section explains how both customers and IBM employees can find out about IBM Redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided. Redbooks Web Site ibm.com/redbooks Search for, view, download, or order hardcopy/cd-rom Redbooks from the Redbooks Web site. Also read redpieces and download additional materials (code samples or diskette/cd-rom images) from this Redbooks site. Redpieces are Redbooks in progress; not all Redbooks become redpieces and sometimes just a few chapters will be published this way. The intent is to get the information out much quicker than the formal publishing process allows. E-mail Orders Send orders by e-mail including information from the IBM Redbooks fax order form to: In United States or Canada Outside North America Telephone Orders United States (toll free) Canada (toll free) Outside North America Fax Orders United States (toll free) Canada Outside North America e-mail address pubscan@us.ibm.com Contact information is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl 1-800-879-2755 1-800-IBM-4YOU Country coordinator phone number is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl 1-800-445-9269 1-403-267-4455 Fax phone number is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl This information was current at the time of publication, but is continually subject to change. The latest information may be found at the Redbooks Web site. IBM Intranet for Employees IBM employees may register for information on workshops, residencies, and Redbooks by accessing the IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for redbook, residency, and workshop announcements. Copyright IBM Corp. 2001 161
IBM Redbooks fax order form Please send me the following: Title Order Number Quantity First name Last name Company Address City Postal code Country Telephone number Telefax number VAT number Invoice to customer number Credit card number Credit card expiration date Card issued to Signature We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment. 162 Using Tivoli Data Protection for Microsoft Exchange Server
Glossary A Access control. Security mechanism used by Windows 2000 to control access to information. Active directory. The Windows 2000 directory service, which allows users to use a single user account for accessing resources on the network. Active directory alleviates administrators work by providing a single point of administration for all network objects. Active Directory Users and Computers. A Microsoft Management Console used for administering objects in Active Directory. Active policy set. The policy set within a policy domain that contains the most recently activated policy. This policy set is used by all client nodes assigned to the current policy domain. See policy set. Active version. The most recent backup copy of a file stored in TSM storage for a file that currently exists on a file server or workstation. An active version remains active and exempt from deletion until: Replaced by a new backup version. TSM detects, during an incremental backup, that the user has deleted the original file from a file server or workstation. Administrative client. A program that runs on a file server, workstation, or mainframe. This program lets administrators monitor and control TSM servers using TSM administrator commands. Contrast with backup-archive client. Administrative group. Collection of Active Directory objects for the sake of easy permission administration. Application program interface (API). A set of functions that applications running on a client platform can call to store, query, and retrieve objects from TSM storage. Archive. A function permitting users to copy one or more files to a long-term storage device. Archive copies can: Accompany descriptive information Imply data compression software usage Be retrieved by archive date, file name, or description Contrast with retrieve. Archive copy. A file or group of files residing in an archive storage pool in TSM storage. Archive copy group. A policy object containing attributes that control the generation, destination, and expiration of archived files. The archive copy group belongs to a management class. Archive retention grace period. The number of days TSM retains an archived copy when the server is unable to rebind the file to an appropriate management class. Audit. Tracking the user actions recorded in an event log on a server or workstation. Authentication. The process of checking and authorizing a user's password before permitting user access to the server. Authorization rule. A specification permitting another user to either restore or retrieve a user's files from TSM storage. B Backup. A function permitting users to copy one or more files to a storage pool to protect against data loss. Contrast with restore. Backup-archive client. A program that runs on a file server, PC, or workstation and provides a means for TSM users to back up, archive, restore, and retrieve files. Contrast with administrative client. Backup copy group. A policy object containing attributes that control the generation, destination, and expiration of backup files. A backup copy group belongs to a management class. Backup version. A backed up file, directory, or file space that resides in a backup storage Copyright IBM Corp. 2001 163
pool in TSM storage. The active version is the most recent backup version. See active version and inactive version. Bridgehead server. A connection link which other servers use to communicate with each other. In Exchange 2000, the Bridgehead server connects routing group to another routing group, remote system, or other external system C Checkpoint file. A file used to show which transactions have been successfully committed to the database file. Separate checkpoint files are maintained for each storage group. Circular logging. A method of logging transactions in which earlier log files are overwritten. Client. A program running on a file server, PC, workstation, or terminal that requests services of another program called the server. There are two types of TSM clients: administrative and backup-archive. See administrative client and backup-archive client. Client domain. The set of drives, file systems, or volumes selected by a user for processing during a backup or archive operation. Client node. A file server or workstation registered with the server on which the backup-archive client program is installed. Client options file. A file that a client can edit, containing a default set of processing options that identify the server, communication method, backup and archive options, space management options, and scheduling options. Client/server. A communications network architecture in which one or more programs (clients) request computing or data services from another program (the server). Closed registration. A registration process in which an TSM administrator must register workstations as client nodes with the server. Contrast with open registration. Coexistence. Simultaneous existence of Exchange 2000 with the earlier version of Exchange or other messaging systems. Command line interface. A type of user interface where commands are specified on the command line. Contrast with graphical user interface. Commit. To make changes permanent in the databases files. Changes made to the database files are not permanent until they are committed. Communication method. The method by which a client and server exchange information. Communication protocol. A set of defined interfaces that permits computers to communicate with each other. Compression. The process of saving storage space by eliminating empty fields or unnecessary data to shorten the length of the file. In TSM, compression can occur at a workstation before files are backed up or archived to server storage. On some types of tape drives, hardware compression can be used. Configuration connection agreement. An automatically created agreement when the first time an Exchange 2000 joined an Exchange 5.5. Connection agreement. The Active Directory Connector uses it to replicate information between the Exchange 5.5 and Active Directory. Contact. An Active Directory object analogous to Custom recipient in Exchange 5.5 - user without Windows account and mailbox on a server. Copy backup. A copy backup is similar to a full backup except that transaction log files are not cleared after the backup. A backup copy can be used to make a full backup of the Exchange Server database without disrupting any backup procedures that use incremental or differential backups. Copy group. An TSM policy object that determines how TSM backs up or archives files. Copy groups belong to management classes. There are two copy groups: Backup copy group--determines how TSM backs up or archives files. Archive copy group--determines how TSM archives files. 164 Using Tivoli Data Protection for Microsoft Exchange Server
Custom recipient. An Exchange 5.5 user who has not an Exchange mailbox. D Default management class. A management class assigned to a policy set. This class is used to govern backed up or archived files when a user does not explicitly associate a file with a specific management class through the include-exclude list. Differential backup. A differential backup backs up only transaction logs, but does not clear them. If you perform a full backup and then perform only differential backups, the last full backup plus the latest differential backup has all data needed to bring the database back to the most recent state. This type of backup is also called a cumulative incremental backup. Directory replication. The process of updating the directories of all servers within and between sites. Distribution list. A group of recipients used to expedite mass mailing of messages. Domain. See policy domain or client domain for the meaning of this term in regards of TSM server. In Windows 2000 this term means group of computers which are part of a network and which share a common directory database. Domain controller. A computer running Windows 2000 Server that administer user s access to a network. dsm.opt file. See options file. Also called client options file. E Error log. A text file written on disk that contains TSM processing error messages. These errors are detected and saved by the TSM server. Event. The occurrence of a particular action or change of state. Exclude. The process of identifying files in an include-exclude list. This process prevents the files from being backed up or migrated whenever a user or schedule enters an incremental or selective backup operation. Expiration. The process in which files are identified for deletion because their expiration date or retention period has passed. Backed up or archived files are marked for deletion based on the criteria defined in the backup or archive copy group. Extensible Storage Engine. A method defining a very low-level application programming interface (API) to the underlying database structures in Exchange. F Failover. The process of taking resources offline on one node of the cluster and bringing them online on the other node. File server. A dedicated computer and its peripheral storage devices connected to a local area network that stores both programs and files shared by users on the network. File space. A logical space on the TSM server that contains a group of files. In TSM, users can restore, retrieve, or delete file spaces from TSM storage. Full backup. A full backup backs up the specified database as well as its associated transaction logs. After the database and logs are backed up, the log files are deleted. G Generate password. Processing that stores a new password in an encrypted password file when the old password expires. Automatic generation of a password prevents password prompting. Password generation can be set in the options file (passwordaccess option). See options file. Global address list. A server stored list containing all Exchange users, contacts, groups, conferencing resources and public folders in organization. Graphical user interface (GUI). A type of user interface that takes advantage of a high-resolution monitor, includes a combination 165
of graphics, the object-action paradigm, and the use of pointing devices, menu bars, overlapping windows, and icons. Contrast with command line interface. GUI. Graphical user interface. I Inactive version. A copy of a backup file in TSM storage that either is not the most recent version, or the corresponding original file was deleted from the client file system. Inactive backup versions are eligible for expiration according to the management class assigned to the file. Include-exclude file. A file containing statements to determine the files to back up and the associated management classes to use for backup or archive. See include-exclude list. Include-exclude list. A list of include and exclude options that include or exclude selected files for backup. An exclude option identifies files that should not be backed up. An include option identifies files that are exempt from the exclusion rules or assigns a management class to a file or a group of files for backup or archive services. The include-exclude list is defined in one or more include-exclude files or in the client options file. The include-exclude list may contain entries from any or all of the following sources: the client options file, separate include-exclude files, or the TSM server. See options file. Incremental backup. An incremental backup only backs up the transaction logs and then clears them. Restoration of an Exchange Server database from an incremental backup requires a: Restore of the last full backup. Restore of any other incremental backups performed between the full backup and this incremental backup. Restore of this incremental backup. K Key Management server. The Exchange computer on which the Key Management Service is installed. L LAN. Local area network. Local Area Network (LAN). A variable-sized communications network placed in one location. LAN connects servers, PCs, workstations, a network operating system, access methods, and communications software and links. M Mailbox-enabled. An active directory object which has an Exchange mailbox. Management class. A TSM policy object that is a named collection of copy groups. A management class is associated with a file to specify how the server should manage backup versions or archive copies of workstation files. Migration. Moving an existing messaging system to another system. Mixed mode. The mode in which Exchange 2000 runs when coexisting with Exchange 5.5. N Native mode. The mode in which Exchange 2000 runs when there are not earlier Exchange versions in the organization. Node. See client node. Node name. A unique name used to identify a workstation, file server, or PC to the server. O Open registration. A registration process in which users can register their own workstations or PCs as client nodes with the server. Contrast with closed registration. Options file. A file that contains processing options. Identifies TSM servers, specifies communication methods, defines scheduling options, selects backup, archive, restore, and retrieve options. Also called the client options file. P Policy domain. A TSM policy object that lets TSM group client nodes by the policies that govern their files and by the administrator who 166 Using Tivoli Data Protection for Microsoft Exchange Server
manages the policies. The policy domain contains one or more policy sets. Policy set. A TSM policy object that specifies the management classes that are available to groups of users. More than one policy set can exist. However, only one policy set at a time can be active. Progress indicator. A control used to inform a user about the progress of a process. Public folder. A folder which colleagues can use for sharing different type of information. The access to this folder is regulate by permissions. R Recovery log. A log of updates that are about to be written to the databases. The log can be used to recover from system and media failures. Registration. The process of identifying a client node or administrator to the server by specifying a user ID, password, and contact information. For client nodes, a policy domain, compression status, and deletion privileges are also specified. Registry. A central database in Windows that contains information about hardware, applications, and operating system settings for each machine on the network. Provides security and control over system, security, and account settings. Restore. A function that permits users to copy a version of a backup file from the storage pool to a workstation or file server. The backup copy in the storage pool is not affected. Contrast with backup. Retention. The amount of time, in days, that inactive backed up or archived files are retained in the storage pool before they are deleted. The following copy group attributes define retention: retain extra versions, retain only version, retain version. Retrieve. A function permitting users to copy an archived file from the storage pool to the workstation or file server. The archive copy in the storage pool is not affected. Contrast with archive. Routing group. The group of Exchange servers in borders of which messages can go directly from one server to the other. S SAN Storage Area Network Scheduling. A function permitting an administrator to schedule backup and archive operations from a central location. Operations can be scheduled on a periodic basis or on an explicit date. Scheduling mode. The type of scheduling operation for the client-server node. TSM supports two scheduling modes: client-polling and server-prompted. Server. A program running on a mainframe, workstation, or file server that provides shared services such as backup and archive to other various (often remote) programs (called clients). Server cluster. A group of physically and software connected computers which work together and appear to the user as a single system. Server-prompted scheduling. A client-server communication technique where the server contacts the client node when tasks need to be done. Session. A period of time in which a user can communicate with a server to perform backup, archive, restore, or retrieve requests. Site Replication service. A directory Service which Exchange 2000 uses to allow coexistence with Exchange 5.5 sites. Space management. The process of keeping sufficient free storage space available on a local file system for new data and making the most efficient and economical use of distributed storage resources. Storage group. A collection of mailbox and public folders stores which share the same set of transaction log files. Storage pool. A named set of storage volumes used as the destination of backup, archive, or migrated copies. 167
T Tivoli Storage Manager (TSM). A client/server program that provides storage management to customers in a multivendor computer environment. Transaction log file. A file that contain all transactions that take place and which can be used in event of system failure for replying the uncommitted transactions to the database. V Version. Storage management policy may allow back-level copies of backed up objects to be kept at the server whenever an object is newly backed up. The most recent backed up copy is called the "active" version. Earlier copies are "inactive" versions. The following backup copy group attributes define version criteria: versions data exists, and versions data deleted. W Wildcard character. An asterisk (*) or question mark (?) character used to represent multiple (*) or single (?) characters when searching for various combinations of characters in alphanumeric and symbolic names. Workstation. A programmable high-level workstation (usually on a network) with its own processing hardware such as a high-performance personal computer. In a local area network, a personal computer that acts as a single user or client. A workstation can also be used as a server. 168 Using Tivoli Data Protection for Microsoft Exchange Server
Index Numerics 2108 SAN Data Gateway 70 A Active Directory 1, 3, 4, 11, 12 active version 92 administrative client 23 administrative groups 1 Alternate server restore for Exchange 2000 123 Alternate server restore for Exchange 5.5 120 Application log 84 archive copy group 19 Archive folders 5 attribute-level security permissions 2 Auto deletion of old backups 92 Auto select feature 108 autorun 27 B backfilling data 129 Backing up across the SAN 80 Backing up Active Directory 52 backing up Exchange 2000, general procedures 45 Backing up Exchange databases 8 Backing up the SRS database 147 backup and restore time, effect on sizings 17 Backup strategies 7 Backup/Archive Client 26, 33, 58, 61 Backup/Archive client 4 Backup/Archive client, installing 33 backups table 23 base directory 28 batch file parameters 32 Best practices 135 bottlenecks 17 C check point files 2 circular logging 9, 103, 135, 138 Cleanup Agent 119, 126 CLI syntax 41 client node setup for LAN-free 72 cluster 18 cluster environment, restoring Exchange on a 115 Cluster service 55 Command Line Interface 35 Command Line Interface, backing up Exchange 5.5 with 40 command line setup 32 communication method 29 complexity of the restore procedure 13 COMPRESSion 29 compression 29 Configuration settings 39, 40 configuration settings 38, 46 configuring the Storage Agent as a service 78 Contacts 5 Copy backup 138 copy backup 14, 37 copy groups 18 cumulative incremental backup 14 D daily incremental backup 13 database copy 14, 46 Database Copy Backup 47 Database Copy backup 37 Database copy backup 138 database size 17 Date Format 40 Day to day monitoring 83 DB log management 83 DBcopy 50 Deleted items retention 14 deleted mailboxes retention 16 Diagnostics logging 89 Differential backup 138 differential backup 14, 37 differential, incremental and database copy backups 47 DIR and IS backup, general procedures 35 Directory service 2 directory service 3 Disaster recovery 127 Disaster recovery for Exchange 2000 128 Disaster recovery for Exchange 5.5 128 disasters 16 diserror.log 89 dismounted database 47 dismounted databases 47 DNS server 125 Copyright IBM Corp. 2001 169
Domain controller 35 drive mapping on the TSM server 77 dsierror.log 84, 139 dsm.opt 29, 138 dsmerror.log 84, 91 dsmsched.log 84, 91 E enablelanfree 29 erasing existing transaction log files 110 Exchange 2000 database technology 3 Exchange 2000 in a cluster environment 35 Exchange 5.5 1 Exchange 5.5. 8 Exchange API 7 Exchange core components 2 Exchange Server 5.5 25 Exchange storage groups 35 Exchange System Manager 119 Exchange Virtual server 57 Exclude/Include 54 Extensible Storage Engine 17 Extensible Storage Engine (ESE) 3 Extract mailbox data 121 Extracting mailbox data to a pst file 126 F favorites file 5 file server 32 forest 125 Full backup 138 full backup 13, 37 full backup after restoring 142 G Gotchas 141 Graphical User Interface (GUI) 35 H Hardware requirements 25 Host Bus Adapter 72 I IIS metabase 12 inactive versions 92 Include/Exclude 52, 54 INCLUDE/EXCLUDE statement 79 Incremental backup 138 incremental backup 13, 37 incremental backup of Exchange 5.5 42 incremental backup, sizes 9 Incremental backups 19 individual mailbox quotas 18 Information store 2 information store recovery 103 initial password 29 installation directory, default 27 installing and configuring TDP for Exchange 27 installing TDP for Exchange 26 K Key Management server 3 Key Management Service 51, 147 Key Management Service (KMS) database restore 132 Key Management Services 11 L lab environment 35, 133 LAN-free configuration 70 LAN-free SAN support 70 library 70 Log File Name 40 M Mailbox Store (ELBRUS) 46 management class 18, 53, 71 Management Service databases 4 Manual recovery 105 maximum number of TDP buffers 39 Mesage transfer agent 2 messaging data 5 messaging system 1 metadata 53 Microsoft Exchange 2000 25 Microsoft Outlook versions 5 Microsoft Web Storage System process 3 mixed Exchange sites 129 mixed mode 1 monitoring the status of Exchange server 94 monitoring the Windows Event Log 90 mounting and unmounting databases 9 MOUNTLIMIT 71 MOUNTRETENSION 71 170 Using Tivoli Data Protection for Microsoft Exchange Server
MS Exchange 1 MSCS Active/Active Configuration 26 MSCS Active/Passive Configuration 26 MSCS cluster 115 MSCS environment, installing TDP in 30 multiple databases 3 multiple storage groups, cluster 18 N native mode 1 network bandwidth 18 node name 29, 55 Node Registration 21 nodename 21 NTBackup in Window 2000 to Backup Exchange 5.5 141 Number Format 40 O Object Name/Database name 102 object names 22, 149 objects on the TSM server 22 Offline folders 4 Online backups 7 online backups 25 Online versus offline 7 Operating system requirement 25 Optional parameters 44 optional parameters 100 ost-files 4 overview 1 P PASSWORD Access 29 performance benefits 8 performing full, copy or database copy restore 46 Personal Address Book 17 personal address book 5 Personal Folders 17 Personal folders 5 Planning considerations 7 policy domain 18 policy set 18 Positional parameters 41 positional parameters 99 Preparation for TDP for Exchange 18 Private Information Store 11 Prune Now Button 40 Prune Old Entries 40 pst-files 5 public folder 2 Public Folders 1 Public Information Store 11 Public store (ELBRUS) 46 Q Qlogic 2200 series HBA 72 QUERY ACTLOG 79 Query commands 94 QUERY PROCES 79 QUERY SESSION 79 Quick start / Checklist 137 R readme1st.txt 27 Record configuration information 135 restoration of single items or mailboxes 117 Restore example Inactive backup 114 restored logs 106 Restoring inactive backups 111 restoring ost-files 17 Retain Extra Versions 19, 92 Retain Only Version 19 Retain Only Versions 92 retention on mailbox deletion 119 routing groups 1 S SAN Data Gateway 70 SCSI write cache 135 Security log 84 server-to-server communication 76 service level agreement 7 Service Pack 4 (SP4) 25 setup types complete 33 Custom 33 show versions 23 Silent installation 31 silent installation 26 site 1 Site Replication Service 3, 4, 35, 147 Site Replication Service (SRS) restore 129 171
Site Replication Service, backing up 50 Site Replication Services 11, 50 stm-file 8 Storage Agent 68, 69, 78, 80, 81 Storage Agent operation 78 Storage Agent options file 75 Storage Agent software installation 73 Storage Area Networks 67 storage group 17 storage group level 12 storage group, transaction logs for 9 storage pool 71 strategies for Exchange 2000 and 5.5 backup 12 System attendant 2 System log 84 T Tape Mounts, waiting for 38 TCP/IP 25 TDP Buffers 39 TDP for Exchange online backups of Exchange 5.5 and 2000 7 TDP for Exchange CLI, restoring Exchange 109 TDP for Exchange GUI, restoring Exchange 107 TDP for Exchange log 88 TDP for Exchange Version 2 25 TDP for Exchange version 2, systems supported 25 TDP for Exchange, registration 28 tdpexc.cfg 100 tdpexc.log 83 tdpexec.log 139 Temporary Log Restore Path 46 Terminal Server session 141 Terminal Service client hangs 141 test restores 92 Time Format 40 Tivoli Enterprise Console 65 Transaction log 9 transaction log 2, 4, 47 transaction logs 3 transaction logs, placing 8 transaction-based logging 2 Troubleshooting 143 TSM activity log 83 TSM administrator 18 TSM API 7, 73 TSM API log 89 TSM Backup/Archive client 7 TSM device driver 77 TSM LAN-free environment 18 TSM object names 133, 149 TSM Scheduler 33 TSM scheduler 57, 61 TSM Scheduling 26 TSM server monitoring 84 TSM Windows Client 33 tsmoptionfilename 44 type of the backup, full or incremental 37 U using the CLI to backup Exchange 2000 47 using the GUI 45 V verifying the backup process, test restores 92 Version Data Deleted 92 Version Data Exists 92 Versions Data Deleted 19 Versions Data Exists 19 Virtual Exchange server 138 W Web Storage Systems 4 weekly full backup 13 Windows account information 3 Windows Event Log 84, 89 Windows security model 1 172 Using Tivoli Data Protection for Microsoft Exchange Server
IBM Redbooks review Your feedback is valued by the Redbook authors. In particular we are interested in situations where a Redbook "made the difference" in a task or problem you encountered. Using one of the following methods, please review the Redbook, addressing value, subject matter, structure, depth and quality as appropriate. Use the online Contact us review redbook form found at ibm.com/redbooks Fax this form to: USA International Access Code + 1 845 432 8264 Send your comments in an Internet note to redbook@us.ibm.com Document Number Redbook Title SG24-6147-00 Using Tivoli Data Protection for Microsoft Exchange Server Review What other subjects would you like to see IBM Redbooks address? Please rate your overall satisfaction: Please identify yourself as belonging to one of the following groups: Your email address: The data you provide here may be used to provide you with information from IBM or our business partners about our products, services or activities. Questions about IBM s privacy policy? O Very Good O Good O Average O Poor O Customer O Business Partner O Solution Developer O IBM, Lotus or Tivoli Employee O None of the above O Please do not use the information collected here for future marketing or promotional contacts or other communications beyond the scope of this transaction. The following link explains how we protect your personal information. ibm.com/privacy/yourprivacy/ Copyright IBM Corp. 2001 173
Using Tivoli Data Protection for Microsoft Exchange Server (0.2 spine) 0.17 <->0.473 90<->249 pages
Using Tivoli Data Protection for Microsoft Exchange Server Strategic planning and implementation considerations for effective backup Backup over the LAN and Storage Area Network Successful recoveries This IBM Redbook explains how to use Tivoli Data Protection (TDP) for Microsoft Exchange v.2.2 to perform backups and restores in your Exchange environment. Tivoli Data Protection for Microsoft Exchange server performs online backups of Microsoft Exchange server databases to Tivoli Storage Manager (TSM) storage. We demonstrate how to back up and recover data on Exchange 5.5 and Exchange 2000 on a single server installation and a clustered environment. Windows 2000 (Service Pack 1) is used as the operating system and Exchange 5.5 as well as Exchange 2000. However, we do not cover backing up the operating system itself. Version 2.2 provides new functionality as well as support for Exchange 2000. The new version of Tivoli Data Protection for Exchange supports a very important TSM feature: automatic expiration and version control by policy. This frees users from having to explicitly delete backup objects in the Tivoli Storage Manager server. TDP for Exchange supports LAN-free data movement. We use TDP for Exchange to perform backups across a traditional LAN, as well as utilizing TSM LAN-free to support backups across Storage Area Networks (SANs). This document is written for Exchange administrators as well as TSM administrators with a need to understand the issues and considerations pertinent to utilizing TSM and TDP to back up and restore Microsoft Exchange. INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment. For more information: ibm.com/redbooks SG24-6147-00 ISBN 0738421987