Installation and User's Guide - Services and Support

Storage Manager for Mail5.5Data Protection for Microsoft ExchangeServerInstallation and User’s GuideIBM ConfidentialSC32-9058-04

Storage Manager for Mail5.5Data Protection for Microsoft ExchangeServerInstallation and User’s GuideIBM ConfidentialSC32-9058-04

IBM ConfidentialNoteBefore using this information and the product it supports, read the information in “Notices” on page 199.Edition noticeThis edition applies to version 5, release 5 of IBM Tivoli Storage Manager for Mail Data Protection for MicrosoftExchange Server and to all subsequent releases and modifications until otherwise indicated in new editions.1998, 2007 Tivoli

IBM ConfidentialContents||Tables . . . . . . . . . . . . . . . ixPreface . . . . . . . . . . . . . . . xiWho should read this guide . . . . . . . . .xiPublications . . . . . . . . . . . . . .xiIBM Tivoli Storage Manager library . . . . .xiRelated publications . . . . . . . . . . xiiAccessing terminology online . . . . . . . xivAccessing publications online . . . . . . . xivOrdering publications . . . . . . . . . . xivSupport information . . . . . . . . . . .xvWhat to do when you encounter a problem . .xvTivoli Technical Training . . . . . . . . . xviIBM Tivoli Storage Manager Web site . . . . xviIBM Tivoli Storage Manager for Mail Web site xviiIBM System Storage Web site . . . . . . . xviiSearching knowledge bases . . . . . . . xviiObtaining fixes . . . . . . . . . . . . xviiReceiving weekly support updates . . . . . xviiiContacting IBM Software Support . . . . . xixConventions used in this book . . . . . . . . xxiTypeface conventions . . . . . . . . . . xxiAccessibility . . . . . . . . . . . . . . xxiMagnifying what is displayed on the screen xxiiNavigating the interface using the keyboard xxiiTechnical changes for Version 5.5.0 -December 2007 . . . . . . . . . . xxiiiChapter 1. Data Protection for ExchangeOverview . . . . . . . . . . . . . . 1New product features for 5.5.0 . . . . . . . .1Data Protection for Exchange product features . . .2Backup Processing: Overview . . . . . . . . .4VSS Backup processing: Overview . . . . . .4Backup types . . . . . . . . . . . . .5Backup methods . . . . . . . . . . . .6Restore Processing: Overview . . . . . . . .10Restore methods . . . . . . . . . . . .12Backup strategies . . . . . . . . . . . .14Full backups only . . . . . . . . . . .15Full backup plus incremental backups . . . .15Full backup plus differentials . . . . . . .15Using VSS and Legacy Backups together . . .15Using VSS operations in a cluster . . . . . .16How Tivoli Storage Manager server policy affectsData Protection for Exchange . . . . . . . .18Security . . . . . . . . . . . . . . .20Performance . . . . . . . . . . . . . .20Buffering (Legacy only) . . . . . . . . .20LAN Free . . . . . . . . . . . . . .21Microsoft Cluster Server (MSCS) Support . . . .21Veritas Cluster Server (VCS) Support . . . . . .22Documentation . . . . . . . . . . . . .22Globalization . . . . . . . . . . . . . .23Chapter 2. Installing Data Protection forExchange . . . . . . . . . . . . . 25Software and operating system requirements . . .25Hardware requirements . . . . . . . . . .27Installation procedure . . . . . . . . . . .29Language Packs . . . . . . . . . . . .30Chapter 3. Configuring Data Protectionfor Exchange . . . . . . . . . . . . 31Part I: Configuration overview . . . . . . . .32Back up to Tivoli Storage Manager storage versusback up to local shadow volumes . . . . . .32Recommended Tivoli Storage Manager policysettings . . . . . . . . . . . . . . .35Data Protection for Exchange node name:Recommended settings . . . . . . . . .36Proxy node definitions (VSS Backups) . . . .37Specifying Data Protection for Exchange options 39Specifying Data Protection for Exchangepreferences . . . . . . . . . . . . .43Part II: Configuration procedure . . . . . . .441. On the Tivoli Storage Manager server: . . .452. On the machine running the Exchange Server: 453. On the machine running the Off-loadedbackups (VSS only): . . . . . . . . . .46Part III: Verify your configuration . . . . . . .47Chapter 4. Using the Graphical UserInterface (GUI) . . . . . . . . . . . 49Menu bar . . . . . . . . . . . . . . .49Edit Menu . . . . . . . . . . . . . .49View Menu . . . . . . . . . . . . .52Utilities Menu . . . . . . . . . . . .53Help Menu . . . . . . . . . . . . .53Toolbar . . . . . . . . . . . . . . . .54GUI Invocation . . . . . . . . . . . . .54Backup and Restore Window . . . . . . . .55GUI Tasks . . . . . . . . . . . . . . .56How to perform a Legacy Backup . . . . . .56How to perform a VSS Backup . . . . . . .56How to perform a VSS Off-loaded Backup . . .57Restoring Exchange storage groups . . . . .58Restoring the Site Replication Service (SRS). . .60Restore options . . . . . . . . . . . .60Data Protection for Exchange in a MSCS or VCSenvironment . . . . . . . . . . . . . .61Chapter 5. Using the Command LineInterface . . . . . . . . . . . . . . 63Command overview . . . . . . . . . . .63Query Exchange command . . . . . . . . .64Query Exchange syntax . . . . . . . . .64iii

IBM ConfidentialQuery Exchange optional parameters . . . . .64Query Exchange Example 1 . . . . . . . .66Query Exchange Example 2 . . . . . . . .66Query Exchange Example 3 . . . . . . . .67Query TDP command . . . . . . . . . . .68Query TDP syntax . . . . . . . . . . .68Query TDP optional parameters . . . . . .68Query TDP Example . . . . . . . . . .69Query TSM command . . . . . . . . . . .70Query TSM syntax . . . . . . . . . . .70Query TSM positional parameters . . . . . .71Query TSM optional parameters . . . . . .71Query TSM Example 1 . . . . . . . . .74Query TSM Example 2 . . . . . . . . .74Backup Command . . . . . . . . . . . .75Backup syntax . . . . . . . . . . . .76Backup positional parameters . . . . . . .77Backup optional parameters . . . . . . . .78Backup Example 1 . . . . . . . . . . .82Backup Example 2 . . . . . . . . . . .82Backup Example 3 . . . . . . . . . . .83Backup Example 4 . . . . . . . . . . .83Backup Example 5 . . . . . . . . . . .84Restore command . . . . . . . . . . . .84VSS restore considerations . . . . . . . .86Restore syntax . . . . . . . . . . . .86Restore positional parameters . . . . . . .87Restore optional parameters . . . . . . . .88Restore Example 1 . . . . . . . . . . .94Restore Example 2 . . . . . . . . . . .94Restore Example 3 . . . . . . . . . . .95Restore Example 4 . . . . . . . . . . .95Restorefiles command . . . . . . . . . . .96Restorefiles syntax . . . . . . . . . . .97Restorefiles positional parameters . . . . . .97Restorefiles optional parameters . . . . . .98Restorefiles Example 1 . . . . . . . . . 101Restorefiles Example 2 . . . . . . . . . 102Restorefiles Example 3 . . . . . . . . . 102Changetsmpassword command . . . . . . . 103Changetsmpassword syntax . . . . . . . 103Changetsmpassword positional parameters . . 103Changetsmpassword optional parameters . . . 104Changetsmpassword Example . . . . . . . 105Set command . . . . . . . . . . . . . 106Set syntax . . . . . . . . . . . . . 106Set positional parameters . . . . . . . . 106Set optional parameters . . . . . . . . . 109Set Example . . . . . . . . . . . . .110Help command . . . . . . . . . . . . .110Help syntax . . . . . . . . . . . . .110Help optional parameters . . . . . . . .110Help Example 1 . . . . . . . . . . . 111Help Example 2 . . . . . . . . . . .113Chapter 6. Using the Tivoli StorageManager scheduler . . . . . . . . . 115Example Procedure . . . . . . . . . . .115On the Tivoli Storage Manager server . . . .116On the Exchange Server . . . . . . . . .117Scheduler considerations . . . . . . . . . 120Appendix A. Quick configuration(Legacy) . . . . . . . . . . . . . 123Appendix B. Frequently askedquestions . . . . . . . . . . . . . 125Appendix C. Silent installation . . . . 131Installing with the Setup Program (setup.exe) . . 133Creating batch files . . . . . . . . . . 134Installing with MSI (msiexec.exe) . . . . . . . 134Installation problems: capturing a log of theinstallation . . . . . . . . . . . . . . 135Creating the package on a cd or a file server . . . 135Creating a silent install package . . . . . . 135Playing back the silent installation . . . . . . 135Setup error messages . . . . . . . . . . . 136Appendix D. Advanced restoreprocedures . . . . . . . . . . . . 137Complete Restore or Replacement . . . . . . 137Individual Mailbox Restore . . . . . . . . . 137Exchange 2003 Recovery Storage Group . . . . 138Requirements . . . . . . . . . . . . 138Procedure . . . . . . . . . . . . . 138Appendix E. Data Protection forExchange Messages . . . . . . . . 139ACN0003S: An internal processing error hasoccurred. . . . . . . . . . . . . . . . 139ACN0004E: An unknown error has been detected. 139ACN0005E: Out of memory. Stop other processesand try the operation again. . . . . . . . . 139ACN0053E: License file (licensefile) could not beopened. . . . . . . . . . . . . . . . 139ACN0054E: Read failure on license file (licensefile). 140ACN0055E: Write failure on license file (licensefile). 140ACN0056E: Data in the license file (licensefile) is notin a valid format. . . . . . . . . . . . . 140ACN0057E: The checksum in the license file(licensefile) does not match the license string text. . 141ACN0058E: The ’Try and Buy’ license has expired. 141ACN0100E: Incomplete command: . . . . . . 141ACN0101E: Invalid argument: . . . . . . . 141ACN0102E: Invalid command: . . . . . . . 142ACN0103E: Invalid option for the specifiedcommand: . . . . . . . . . . . . . . 142ACN0104E: Invalid option: . . . . . . . . 142ACN0105E: Missing argument: . . . . . . . 142ACN0132W: Tracing could not be started.Processing will continue. . . . . . . . . . 143ACN0133W: Could not locate installation directory.Attempting to continue... . . . . . . . . . 143ACN0134W: Could not locate log directory.Processing will continue... . . . . . . . . . 143ACN0150I: Operation canceled by user. . . . . 144ACN0151E: Errors occurred while processing therequest. . . . . . . . . . . . . . . . 144ACN0152I: Performance stats: seconds secondsspent in apicall API calls . . . . . . . . . . 144iv Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN0153I: Performance stats: seconds secondsspent in function . . . . . . . . . . . . 145ACN0154E: The Data Protection for MicrosoftExchange Server application client cannot workwith the version of the Tivoli Storage Manager APIyou have installed. Please install versionversion.release.level or greater. . . . . . . . . 145ACN0155E: The Data Protection for MicrosoftExchange Server application client cannot workwith the release of Tivoli Storage Manager API youhave installed. Please install release version.release.level or greater. . . . . . . . . . . . . . 145ACN0156E: Could not load the Tivoli StorageManager API. . . . . . . . . . . . . . 146ACN0160E: An authentication error occurred withyour stored Tivoli Storage Manager password. . . 146ACN0161E: Authentication error. The passwordentered is not valid. You are not logged on to theTivoli Storage Manager server. . . . . . . . . 146ACN0162E: The passwords entered do not match.Please enter them again. . . . . . . . . . . 147ACN0163E: The directory path needs to befully-qualified. . . . . . . . . . . . . . 147ACN0167E: The fully-qualified file name is toolong. . . . . . . . . . . . . . . . . 147ACN0200E: File (filename) could not be opened forreading. . . . . . . . . . . . . . . . 147ACN0201E: File (filename) could not be opened forwriting. . . . . . . . . . . . . . . . 148ACN0202E: Read failure on file (filename). . . . . 148ACN0203E: Write failure on file (filename). . . . . 148ACN0204E: File (filename) could not be closed. . . 148ACN0205E: File (filename) statistics could not beobtained. . . . . . . . . . . . . . . . 149ACN0206E: Directory (directory) could not becreated. . . . . . . . . . . . . . . . 149ACN0207E: Directory path (directorypath) is toolong. . . . . . . . . . . . . . . . . 149ACN0208E: There is not enough disk space for theoperation attempted. . . . . . . . . . . . 150ACN0209E: The rename of file (filename1) to(filename2) failed. . . . . . . . . . . . . 150ACN0210E: The Tivoli Storage Manager high levelqualifier is too long. . . . . . . . . . . . 150ACN0211E: The Tivoli Storage Manager low levelqualifier is too long. . . . . . . . . . . . 150ACN0212E: The Tivoli Storage Manager filespacename is too long. . . . . . . . . . . . . 151ACN0213E: The maximum number of objectsallowed per Tivoli Storage Manager transaction is too small. . . . . . . . . . . . . . . . 151ACN0214E: The backup object’s management classbackup copy group does not exist. . . . . . . 151ACN0215E: All backup objects do not have thesame management class backup copy destination. . 152ACN0216E: Unable to obtain space information forvolume (volumename).. . . . . . . . . . . 152ACN0217E: The Tivoli Storage Manager filespacename is invalid. . . . . . . . . . . . . 152ACN0218E: The Tivoli Storage Manager high levelqualifier is invalid. . . . . . . . . . . . 152ACN0219E: The Tivoli Storage Manager low levelqualifier is invalid. . . . . . . . . . . . 153ACN0256E: The password in your Tivoli StorageManager options file has expired. Please changeyour password on the Tivoli Storage Managerserver using the ’change password’ command andthen either change or remove the password valuein your options file. . . . . . . . . . . . 153ACN0257E: Your password has expired. . . . . 153ACN0258E: You did not enter a valid password.Processing ends. . . . . . . . . . . . . 154ACN0259E: The password you entered forverification does not match the password youentered for your new password. Your passwordwill not be changed. . . . . . . . . . . . 154ACN0260I: Password successfully changed. . . . 154ACN0261I: There are no backups for the servernamed servername. . . . . . . . . . . . . 155ACN0263E: Failed to start Web browser with areturn code of returncode. . . . . . . . . . 155ACN0264I: Could not find the default browserdefined. An attempt will be made to use MicrosoftInternet Explorer. . . . . . . . . . . . . 155ACN0265E: Could not find Internet Explorer. . . . 156ACN0266E: Could not find the Tivoli StorageManager HTML books. . . . . . . . . . . 156ACN0267E: The verify password entered does notmatch the new password entered. . . . . . . 156ACN0300E: Invalid restore type. . . . . . . . 156ACN0301E: Invalid backup type. . . . . . . . 157ACN351E: Invalid trace keyword - ’keyword’ . . . 157ACN357E: Unable to open trace output filefile-name. . . . . . . . . . . . . . . . 157ACN366E: Unable to close trace output filefile-name. . . . . . . . . . . . . . . . 157ACN367E: Unable to write to trace file tracefile.Tracing disabled. . . . . . . . . . . . . 158ACN368E: Invalid trace file name (name too long). 158ACN383E: Specifying the trace file ’link’ as asymbolic link is not allowed. . . . . . . . . 158ACN384E: Symbolic link ’linkname’ to ’target’ wassuccessfully deleted. . . . . . . . . . . . 159ACN385E: Unable to delete symbolic link ’link’. 159ACN476E: program-name: cannot open file file-spec:error. . . . . . . . . . . . . . . . . 159ACN487E: Specifying the error log ’link’ as asymbolic link is not allowed. . . . . . . . . 159ACN488E: Initialization functions cannot open theerror log: log-name. errno = errno-value, . . . . . 160ACN495E: Failure writing to a Tivoli StorageManager log or log-related file: file-name, errno =errno-value, reason . . . . . . . . . . . . 160ACN496I: TDP is converting the log-file fromcontinuous (pruning) mode to wrapping mode.This process may take several minutes. . . . . . 161ACN497I: TDP is converting the log-file fromwrapping mode to continuous (pruning) mode.This process may take several minutes. . . . . . 161ACN498I: count log records processed. . . . . . 161Contentsv

IBM ConfidentialACN501E: Invalid Proxy Configuration Detected:Target Node ’targetnode’ is not listed as a validnode to proxy to for Node Name ’nodename’. . . . 162ACN501T: Invalid Proxy Configuration Detected:Target Node ’targetnode’ is not listed as a validnode to proxy to for Node Name ’nodename’. . . . 162ACN515E: Invalid DSMAGENT Nodeconfiguration found for node ’dsmagentnode’. . . . 162ACN516I: The Windows console event handlerreceived a ’event’ console event. . . . . . . . 163ACN517I: An unexpected error was encountered.TDP function name : function-name TDP function :function-desc TDP return code : TSM-rc TDP file :file-name (line-number) . . . . . . . . . . 163ACN518E: Backups selected for restore must havethe same backup location (TSM or LOCAL). . . . 163ACN519E: The VSS operation failed with rc =returncode. . . . . . . . . . . . . . . 164ACN520E: Failed to connect to Local DSMAGENTNode ’localdsmagentnode’ at address:port’address:portnumber’. Verify that the TSM ClientAcceptor Daemon (CAD) is installed, configured,and running properly. . . . . . . . . . . 164ACN521E: Pruning functions cannot open one ofthe Tivoli Storage Manager prune files: log-name.errno = errno-value, . . . . . . . . . . . 164ACN3500I: Data Protection for Exchange: Startingbackup type backup of object name from server servername. . . . . . . . . . . . . . . . . 165ACN3501I: Data Protection for Exchange: backuptype backup of object name from server server namecompleted successfully. bytes bytes sent in secondsseconds. . . . . . . . . . . . . . . . 165ACN3502E: Data Protection for Exchange: backuptype backup of object name from server server namefailed, rc = return code. . . . . . . . . . . 165ACN3503I: Data Protection for Exchange: backuptype backup of storage group name from server servername was cancelled by the user. . . . . . . . 166ACN3504I: Data Protection for Exchange: Startingrestore for server servername. . . . . . . . . 166ACN3505I: Data Protection for Exchange: Restorefrom server servername to servername is complete.Total backups restored: Total bytes transferred:Elapsed processing time: Secs Throughput rate:Kb/Sec . . . . . . . . . . . . . . . 166ACN3506I: Data Protection for Exchange: Startingbackup type restore of storage group storage groupname to server server name. . . . . . . . . . 167ACN3507E: Data Protection for Exchange: backuptype restore of storage group storage group name toserver server name completed successfully. . . . . 167ACN3508E: Data Protection for Exchange: backuptype restore of storage group storage group name toserver server name failed, rc = return code. . . . . 167ACN3509I: Data Protection for Exchange: backuptype restore of storage group storage group name toserver server name was cancelled by the user. . . . 168ACN3510I: Data Protection for Exchange:Attempting to inactivate the object: filespace -[filespace name], hl - [high level], ll - [low level] . . . 168ACN3511I: Data Protection for Exchange:Inactivation of the previous objects succeeded. . . 168ACN3512E: Data Protection for Exchange:Inactivation of the previous objects failed. . . . . 169ACN3513E: Data Protection for Exchange:Inactivation of the previous objects was canceled. . 169ACN3514I: Data Protection for Exchange: Startingbackup for server servername. . . . . . . . . 169ACN3516I: Data Protection for Exchange: Backupof server servername is complete. Total storagegroups backed up: Total bytes transferred: Elapsedprocessing time: Secs Throughput rate: Kb/Sec . . 170ACN3517E: Data Protection for Exchange: Backupof server servername failed, rc = returncode. . . . . 170ACN3518I: Data Protection for Exchange: Backupof server servername failed. The request wascanceled by the user. . . . . . . . . . . . 170ACN5050I: A new configuration file has beencreated. . . . . . . . . . . . . . . . 171ACN5051W: The configuration file cannot befound, using default settings. . . . . . . . . 171ACN5052E: An error occurred trying to set thepreference preference. . . . . . . . . . . . 171ACN5053E: The value for the preference preferenceis not valid. See the TDPEXCC HELP SET outputor the User’s Guide for valid SET commandparameters. . . . . . . . . . . . . . . 171ACN5054I: The preference has been setsuccessfully. . . . . . . . . . . . . . . 172ACN5055E: The Microsoft Exchange API could notbe loaded. . . . . . . . . . . . . . . 172ACN5056I: The logfile log file could not be pruned.Processing will continue. . . . . . . . . . 172ACN5057I: The logfile log file has been prunedsuccessfully. . . . . . . . . . . . . . 173ACN5058W: The length of the logf ile name isgreater than the maximum allowed. Processing willcontinue using a log file name of logfile in thecurrent directory. . . . . . . . . . . . . 173ACN5059W: The logfile log file cannot be openedfor writing. There will be no logging of events. . . 173ACN5060E: A Tivoli Storage Manager API errorhas occurred. . . . . . . . . . . . . . 174ACN5061E: A Microsoft Exchange api error hasoccurred. . . . . . . . . . . . . . . . 174ACN5062E: The version of Microsoft Exchange thatis running is not a supported version for IBMTivoli Storage Manager for Mail. . . . . . . . 174ACN5063E: An error occurred trying to get theMicrosoft Exchange version information. It couldbe a problem with the registry. Or, a MicrosoftExchange Server is not installed on this machine. . 175ACN5064W: The service cannot be started whendoing a restore. . . . . . . . . . . . . . 175ACN5065E: All of the services associated with thisrestore are running. . . . . . . . . . . . 175ACN5066W: The storage group doesnot exist. . . . . . . . . . . . . . . . 175vi Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5067E: None of the storage groups ordatabases entered exist. Or, if they do exist, andyou are using Exchange 2000 or Exchange 2003, thedatabases have not been dismounted. . . . . . 176ACN5068W: The database does notexist in the storage group . . . . . 176ACN5069W: The database in the storagegroup is not dismounted. . . . . 176ACN5070W: The Directory Service is not running.The Directory will not be backed up. . . . . . 177ACN5071W: The Information Store is not running.The Information Store will not be backed up. . . . 177ACN5072W: Databases in storage group are dismounted -- skipping. . . . . . . 177ACN5073E: None of the storage groups entered arein a state to be backed up. . . . . . . . . . 178ACN5074E: None of the databases or storagegroups entered exist. . . . . . . . . . . . 178ACN5076W: Unable to inactivate all previousbackup objects. . . . . . . . . . . . . . 178ACN5083I: All of the storage groups entered havebeen excluded. . . . . . . . . . . . . . 178ACN5084W: IS was not input as one of the parts torestore. The partial option will be ignored. . . . 179ACN5086W: None of the storage groups enteredexist. Or, if doing a DBCOPY backup, the databaseentered does not exist. . . . . . . . . . . 179ACN5087E: PASSWORDACCESS is Generate.Either the stored password is incorrect or there isno stored password. If you do not have a storedpassword, use of the -TSMPassword=xxx optionwill set and store your password. . . . . . . 179ACN5140I: Storage Group does notexist - skipping. . . . . . . . . . . . . 180ACN5141I: Database , Storage Group does not exist - skipping. . . . . 180ACN5142E: No storage group was found thatmatches the request. . . . . . . . . . . . 180ACN5209I: There are no backups matching theserver name servername and the followingfilespecs:filespecs. . . . . . . . . . . . . 181ACN5228I: Data Protection for Exchange is notconfigured for VSS operations. . . . . . . . 181ACN5229E: Error obtaining VSS information fromLocal DSMAgent Node: ’localdsmagentnode’. . . . 181ACN5237E: Unable to communicate with theMicrosoft Exchange Server. . . . . . . . . . 182ACN5238E: Unable to retrieve the domaininformation for the Microsoft Exchange Server. . . 182ACN5239E: Unable to retrieve the storage groupinformation. . . . . . . . . . . . . . . 182ACN5240E: Unable to retrieve the databaseinformation. . . . . . . . . . . . . . . 183ACN5241E: The Microsoft Exchange InformationStore is currently not running. . . . . . . . . 183ACN5301E: Unable to get the value for theOrganization from the registry. . . . . . . . 183ACN5302E: Unable to get the value for the Sitefrom the registry. . . . . . . . . . . . . 184ACN5303E: Unable to get the value for CircularLogging from the registry. . . . . . . . . . 184ACN5304E: Unable to open service to determine ifrunning or not. . . . . . . . . . . . . . 184ACN5305E: Unable to query service information. 184ACN5350E: An unknown Exchange API error hasoccurred. . . . . . . . . . . . . . . . 185ACN5351E: The Exchange server application is notregistered for backup. . . . . . . . . . . 185ACN5352E: The Exchange server application is notregistered for offline restore. . . . . . . . . 185ACN5353E: The Exchange server application is notregistered for online restore. . . . . . . . . 186ACN5354E: The storage group was not found. . . 186ACN5355E: The database was not found. . . . . 186ACN5356E: The database file name is undefined. 187ACN5357W: The truncation of the transaction logfailed. . . . . . . . . . . . . . . . . 187ACN5358E: A Microsoft Exchange API protocolerror has occurred. . . . . . . . . . . . 187ACN5359E: An attempt was made to get the TEMPenvironment variable. This attempt failed. . . . . 187ACN5360E: The /ERASEexistingdata option is notallowed during a partial restore. . . . . . . . 188ACN5361E: It is invalid to have an ’*’ within astorage group name. . . . . . . . . . . . 188ACN5362W: The filespace in an invalidfilespace name. . . . . . . . . . . . . . 188ACN5500E: The MultiByteToWideChar() functionfailed. . . . . . . . . . . . . . . . . 189ACN5501E: The WideCharToMultiByte() functionfailed. . . . . . . . . . . . . . . . . 189ACN5705W: An error was encountered with TivoliStorage Manager API initialization, rc = returncode.Examine the dsierror.log for more information ordetermine if the TSM API is installed properly. . . 189ACN5706I: The logfile_name log file did not needpruning. . . . . . . . . . . . . . . . 189ACN5707W: The logfile_name log file could not beopened for writing. The log was not pruned andthere will be no logging of events. . . . . . . 190ACN5724I: No databases have been selected forbackup. . . . . . . . . . . . . . . . 190ACN5725I: No Storage Groups have been selectedfor backup. . . . . . . . . . . . . . . 190ACN5741I: No Backups have been selected forrestore. . . . . . . . . . . . . . . . 191ACN5758W: At least one of the database’s servicesthat is selected for restore is running. Do you wantto stop the service(s)? . . . . . . . . . . 191ACN5759W: At least one of the databases that isselected for restore is mounted. Do you want todismount the database(s)? . . . . . . . . . 191ACN5766E: Unable to dismount database databasein storage group storage group. Do you want tocontinue the restore process? . . . . . . . . 192ACN5798E: MS Exchange API api name failed withHRESULT: api retcode - . . . . . . . . . . 192ACN5800E: Backup is corrupt. See log file foradditional information. . . . . . . . . . . 192Contentsvii

IBM ConfidentialACN5802T: When a Recovery Storage Group exists,mailbox and public folder databases cannot berestored in the same operation. ACTION: Pleaseselect either a mailbox OR public folder databasefor restore. . . . . . . . . . . . . . . 193ACN5803T: When performing a mailbox databaserestore to a Recovery Storage Group, the ReplayRestored Logs ONLY option must be specified orthe restore may fail. ACTION: The Replay RestoredLogs ONLY option will AUTOMATICALLY beused on the restore. Do you wish to continue withthe restore? . . . . . . . . . . . . . . 193ACN5805E: Restore failed. File already exists. . . 193ACN5810E: Restoring Legacy backups and VSSbackups in the same restore operation is notsupported. Retry the restores in separateoperations. . . . . . . . . . . . . . . 193ACN5811E: Invalid command. Data Protection forExchange only supports VSS backup types ofFULL and COPY. . . . . . . . . . . . . 194ACN5812E: Invalid command. Data Protection forExchange does not support OFFLOAD with theLegacy backup method. . . . . . . . . . . 194ACN5813E: Invalid command. Data Protection forExchange only supports Legacy backups with abackup destination of TSM. . . . . . . . . 194ACN5814E: Invalid command. Data Protection forExchange does not support OFFLOAD with thespecified backup destination. . . . . . . . . 195ACN5815E: The VSS operation failed with rc =returncode. . . . . . . . . . . . . . . 195ACN5816E: Data Protection for Exchange is notable to run VSS operations. You must be runningExchange Server 2003 (or later) and have the MSExchange VSS license file (acsexc.lic) installed. . . 195ACN5817E: Missing, blank, or invalid LocalDSMAGENT Node Name is not allowed. . . . . 196ACN5818E: Invalid command. Data Protection forExchange only supports restoring VSS backuptypes of FULL and COPY. . . . . . . . . . 196ACN5819E: Multiple backup objects were foundfor the specified storage group(s) and backupdestination. Use the OBJECT= andBACKUPDESTINATION= options to identifywhich specific backup object to restore. . . . . . 196ACN5820E: There were no Exchange backupsfound on the Tivoli Storage Manager servermatching the specified criteria. . . . . . . . 197ACN5824I: Storage Group does nothave replica - skipping. . . . . . . . . . . 197ACN5825E: Invalid command. Data Protection forExchange does not support FROMREPLICA withthe Legacy backup method. . . . . . . . . 197ACN5829E: Invalid command. Data Protection forExchange does not support INTOSG with theLegacy restore method. . . . . . . . . . . 198Notices . . . . . . . . . . . . . . 199Trademarks . . . . . . . . . . . . 201Glossary . . . . . . . . . . . . . 203Index . . . . . . . . . . . . . . . 209viii Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialTables1. Data Protection for Exchange key features 22. Backup strategy characteristics . . . . . .163. Minimum software and operating systemrequirements for Legacy Backup and Restoreoperations . . . . . . . . . . . . .254. Minimum software and operating systemrequirements for basic VSS operations . . . .255. Minimum software and operating systemrequirements for VSS Off-loaded Backup . . .266. Minimum software and operating systemrequirements . . . . . . . . . . . .267. Minimum software and operating systemrequirements for VSS Restore into theRecovery Storage Group . . . . . . . .268. Minimum software and operating systemrequirements for VSS Backup of CCR and LCRcopies . . . . . . . . . . . . . .279. Minimum hardware requirements for Legacyor VSS Backup and Restore operations . . .2710. Minimum hardware requirements for VSSoff-loaded backup operations . . . . . .2811. Minimum hardware requirements for VSSInstant Restore operations . . . . . . . .2812. List of applications to configure . . . . . .3113. Required node names for basic VSS operations 3714. Required node names for VSS off-loadedbackups . . . . . . . . . . . . . .3815. Silent installation options . . . . . . . 13116. Silent installation features (base client only) 13217. Silent installation features (LanguagePackages only) . . . . . . . . . . . 13218. Silent installation features (IBM Tivoli StorageManager for Copy Services MicrosoftExchange VSS Integration Module only) . . 13219. Silent installation features (IBM Tivoli StorageManager for Copy Services Hardware DevicesSnapshot Integration Module only) . . . . 13220. Silent installation transforms . . . . . . 133ix

x Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialPrefaceThe subject of this publication is Data Protection for Exchange, a component of theIBM Tivoli Storage Manager for Mail product.Data Protection for Exchange performs online backups of Microsoft ® ExchangeServer databases to Tivoli Storage Manager storage. This integration with theMicrosoft Exchange Server application program interface (API) maximizes theprotection of data, thus providing a comprehensive storage management solution.Tivoli Storage Manager is a client-server licensed product that provides storagemanagement services in a multi-platform computer environment.Throughout this document, the term Windows ® (unless otherwise specified) refersto the following operating systems:v Windows Server 2003Throughout this document, the term Exchange Server (unless otherwise specified)refers to the following products:v Exchange Server 2003v Exchange Server 2007Who should read this guideThe target audience for this publication are system installers, system users, TivoliStorage Manager administrators, and system administratorsIn this book, it is assumed that you have an understanding of the followingapplications:v Microsoft Exchange Serverv Tivoli Storage Manager serverv Tivoli Storage Manager backup-archive clientv Tivoli Storage Manager Application Program Interfacev Microsoft Volume Shadow Copy Service (VSS) technology (knowledge of thisapplication is only assumed if you plan to perform VSS operations)It is also assumed that you have an understanding of one of the followingoperating system:v Windows Server 2003PublicationsThis section lists related IBM Tivoli Storage Manager publications. It also describeshow to access Tivoli ® publications online and how to order Tivoli publications.IBM Tivoli Storage Manager libraryThe following documents are available in the IBM Tivoli Storage Manager library:v IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installationand User’s Guidexi

IBM ConfidentialRelatedProvides information for an end-user to install, configure, and use the TivoliStorage Manager client on UNIX and Linux operating systems.v IBM Tivoli Storage Manager for AIX Administrator’s GuideProvides concepts and procedures for configuring and customizing the TivoliStorage Manager server on AIX operating systems.v IBM Tivoli Storage Manager for AIX Administrator’s ReferenceProvides details about administrative commands, server options, and serverutilities for Tivoli Storage Manager server on AIX operating systems.v IBM Tivoli Storage Manager MessagesProvides explanations and suggested actions for messages issued by the TivoliStorage Manager server program for storage management services, theadministrative client graphical user interface, administrative command lineclient, data protection clients, and backup-archive client.v IBM Tivoli Storage Manager: Problem Determination GuideThis guide describes how to diagnose problems with Tivoli Storage Manager.v IBM Tivoli Storage Manager Using the Application Program InterfaceProvides information to help you add Tivoli Storage Manager applicationprogram interface calls to an existing application and to write programs withgeneral-use program interfaces that obtain the services of Tivoli StorageManager.v IBM Tivoli Storage Manager for SAN for AIX Storage Agent User’s GuideProvides an overview of LAN-free data transfer and detailed explanations aboutconfiguring and using the Tivoli Storage Manager client, storage agent, andserver.publicationsThe following IBM publications provide additional information.v IBM System Storage DS6000 Introduction and Planning GuideThis publication provides an overview of the IBM System Storage DS6000, andprovides the feature codes for ordering standard and optional features. It alsoprovides planning guidelines for DS6000 installation and configuration.v IBM System Storage DS6000 Host Systems Attachment GuideThis guide provides information about:– Attaching the IBM DS6000 to an open-systems host with Small ComputerSystem Interface (SCSI) adapters.– Attaching the DS6000 to an open-systems host with fibre-channel adapters.– Connecting IBM Enterprise Systems Connection ESCON cables to an IBMS/390 and IBM (zSeries) host systems.– Connecting IBM Enterprise Systems Fibre Connection (FICON) cables to anS/390 and zSeries host systems.v IBM System Storage DS6000 Command-Line Interface User’s GuideThis guide introduces the IBM System Storage DS command-line interfaces(CLI). It also provides command syntax and reference information for commandsthat can be used through the IBM System Storage DS6000 Command LineInterfaces.v IBM System Storage DS8000 Introduction and Planning GuideThis publication provides an overview of the IBM System Storage DS8000, andprovides the feature codes for ordering standard and optional features. It alsoprovides planning guidelines for DS8000 installation and configuration.xii Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialv IBM System Storage DS8000 User’s GuideThis publication provides the procedures for using the IBM System StorageDS8000. It includes an overview of the DS8000 and guidelines for:– Operating the DS8000.– Operating the Hardware Management Console.– Using optional software for the DS8000.– Migrating data to the DS8000.– Analyzing problems.– Disaster Recovery.v IBM System Storage DS8000 Host Systems Attachment GuideThis guide provides information about:– Attaching the IBM DS8000 to an open-systems host with Small ComputerSystem Interface (SCSI) adapters.– Attaching the DS8000 to an open-systems host with fibre-channel adapters.– Connecting IBM Enterprise Systems Connection ESCON cables to an IBMS/390 and IBM (zSeries) host systems.– Connecting IBM Enterprise Systems Fibre Connection (FICON) cables to anS/390 and zSeries host systems.v IBM System Storage SAN Volume Controller Configuration GuideProvides information about how to configure the SAN Volume Controller.v IBM System Storage SAN Volume Controller Configuration Guide Supplement (VSS)Provides information about how to install and use Microsoft Volume ShadowCopy service with the SAN Volume Controller.v IBM System Storage SAN Volume Controller Planning GuideThis publication introduces the IBM System Storage SAN Volume Controller, itscomponents and its features. It also provides planning guidelines for installingand configuring the SAN Volume Controller.v CIM Agent and Console for IBM System Storage SAN Volume ControllerProvides license information for IBM System Storage Common InformationModel Agent.v IBM System Storage SAN Volume Controller CIM Agent Developer’s ReferenceThis Guide helps developers retrieve and abstract CIM Agent object classes andproperties. This will help developers to use object classes and models to createcopy services and LUN masking.v Installation and Setup Instructions for the IBM System Storage N3700 and EXP600Expansion UnitThis manual provides basic information required to install and set up an IBMSystem Storage N3700 and disk expansion unit EXP600. It also providesinformation required to connect an N3700 to a network, additional shelves, apower source, third party devices, and/or to an ASCII terminal.v IBM System Storage N3700 Hardware and Service GuideThis manual provides basic information required to install and set up an IBMSystem Storage N3700, models A10 and A20. It also provides informationrequired to connect an N3700 to a network, additional shelves, a power source,third party devices, and/or to an ASCII terminal. This manual also providesinformation required to configure, monitor, troubleshoot and replace the N3700.Finally, it provides regulatory information.v IBM Tivoli Storage Manager in a Clustered EnvironmentPrefacexiii

IBM ConfidentialThis IBM Redbook describes how to implement IBM Tivoli Storage ManagerVersion 5.3 products in highly available clustered environments. It is intendedfor those who want to plan, install, test, and manage these products in variousenvironments by providing best practices and showing how to develop scriptsfor clustered environments.v Using IBM Tivoli Storage Manager for Copy Services to Back Up Microsoft Exchangewith VSSThis IBM Redbook describes how to plan, configure and run IBM Tivoli StorageManager for Copy Services in a Microsoft Exchange environment.Accessing terminology onlineThe Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. The Tivoli Software Glossary is available at the followingTivoli software library Web site:http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htmThe IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:http://www.ibm.com/software/globalization/terminologyAccessing publications onlineOrderingIBM ® posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli software information centerWeb site. Access the Tivoli software information center by first going to the Tivolisoftware library at the following Web address:http://www.ibm.com/software/tivoli/library/Scroll down and click the Product manuals link. In the Tivoli Technical ProductDocuments Alphabetical Listing window, click the linkto access the product library at the Tivoli software information center.Note: If you print PDF documents on other than letter-sized paper, set the optionin the File → Print window that allows Adobe Reader to print letter-sized pages onyour local paper.publicationsYou can order many Tivoli publications online at the following Web site:http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgiYou can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968In other countries, contact your software account representative to order Tivolipublications.xiv Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSupport informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:v Searching knowledge bases: You can search across a large collection of knownproblems and workarounds, Technotes, and other information.v Obtaining fixes: You can locate the latest fixes that are already available for yourproduct.v Contacting IBM Software Support: If you still cannot solve your problem, andyou need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.For more information about these three ways of resolving problems, see“Contacting IBM Software Support” on page xix.What to do when you encounter a problemIf you encounter a problem during Data Protection for Exchange processing, followthese steps as your first attempt to resolve the problem:1. Retry the operation that failed.2. If the problem occurred during an incremental, differential, or database copybackup, run a full backup. If the full backup completes successfully, retry theoperation that failed.3. If the problem still exists, close other applications, especially those applicationsthat interact with Exchange (anti-virus applications, for example). Retry theoperation that failed.4. If the problem still exists:a. Shut down the Exchange server.b. Start the Exchange server again.c. Run the operation that failed.5. If the problem still exists:a. Shut down the entire machine.b. Start the machine again.c. Run the operation that failed.6. If the problem still exists, determine if it is occurring on other Exchangeservers.Determining if the problem resides on Tivoli Storage Manager orExchangeThis section provides information to help determine if the problem is a DataProtection for Exchange issue or an Exchange issue.For Legacy operations:v Try recreating the problem with the Microsoft NTBACKUP utility. This utilityuses a call sequence similar to Data Protection for Exchange to run an onlinebackup. If the problem is recreatable with NTBACKUP then the problem mostlikely exists within the Exchange server.v Try recreating the problem with the Microsoft BACKREST application. Thisapplication can run backups using the Microsoft Exchange APIs. If the problemis recreatable with BACKREST then the problem most likely exists within theExchange server. Microsoft ships BACKREST with the Exchange SoftwarePrefacexv

IBM ConfidentialDeveloper’s Kit (SDK). IBM Service can provide a copy of BACKREST if youencounter problems obtaining or building this application.v If the error message ″ACN5350E An unknown Exchange API error has occurred″ isdisplayed, the Exchange server encountered an unexpected situation. Microsoftassistance may be needed if the problem continues.v Data Protection for Exchange error messages occasionally contain an HRESULTcode. Use this code to search Microsoft documentation and the MicrosoftKnowledge Base for resolution information. The Exchange SDK file ESEBKMSG.Hcontain these messages.For VSS operations: Try recreating the problem with the Microsoft VSHADOWapplication. This application can run backups using the Microsoft Exchange VSSAPIs. If the problem is recreatable with VSHADOW then the problem most likelyexists within the VSS provider or the Exchange server. Microsoft ships VSHADOWwith the Volume Shadow Copy Services (VSS) Software Developer’s Kit (SDK).IBM Service can provide a copy of VSHADOW if you encounter problemsobtaining or building this application.Installation Problems: Creating an Installation Log FileIn the event a silent installation fails, gather the following information to assistCustomer Support when evaluating your situation:v operating system levelv service packv hardware descriptionv installation package (CD-ROM or electronic download) and levelv any Windows event log relevant to the failed installationv Windows services active during the failed installation (for example, anti-virussoftware)v whether you are logged on to the local machine console (not via terminal server)v whether you are logged on as a local administrator, not a domain administrator(Tivoli does not support cross-domain installs)You can create a detailed log file (setup.log) of the failed installation. Run the setupprogram (setup.exe) in the following manner:setup /v"l*v setup.log"Tivoli Technical TrainingFor Tivoli technical training information, refer to the following IBM TivoliEducation Web site:http://www.ibm.com/software/tivoli/educationIBM Tivoli Storage Manager Web siteTechnical support information and publications are available at the followingaddress: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.htmlBy accessing the Tivoli Storage Manager home page, you can access subjects thatinterest you. You can also keep up-to-date with the newest Tivoli Storage Managerproduct information.xvi Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialIBM Tivoli Storage Manager for Mail Web siteThe IBM Tivoli Storage Manager for Mail Web site contains a knowledge base ofarticles and information related to backup and restore issues. Access thisinformation at: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforMail.html If you plan to perform VSS operations, theIBM Tivoli Storage Manager for Copy Services Web site contains a knowledge baseof VSS-related articles and information:http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforCopyServices.htmlIBM System Storage Web siteTechnical support information and publications are available at the followingaddress: http://www.ibm.com/servers/storageBy accessing the IBM System Storage home page, you can access detailedinformation regarding product compatibility requirements. You can also keepup-to-date with the newest IBM System Storage product information.Searching knowledge basesYou can search the available knowledge bases to determine whether your problemwas already encountered and is already documented.Searching the information centerIBM provides extensive documentation that can be installed on your localcomputer or on an intranet server. You can use the search function of thisinformation center to query conceptual information, instructions for completingtasks, and reference information.Searching the InternetIf you cannot find an answer to your question in the information center, search theInternet for the latest, most complete information that might help you resolve yourproblem.To search multiple Internet resources for your product, go to this product supportweb site: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html and look for the section to search the supportknowledge base. From this section, you can search a variety of resources including:v IBM technotesv IBM downloadsv IBM Redbooks v Forums and newsgroupsYou can also search the IBM Tivoli Storage Manager: Problem Determination Guide forhelpful diagnostic information at this Web site: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmm.doc/update/main.htmlObtainingfixesA product fix might be available to resolve your problem. To determine what fixesare available for your IBM software product, follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.2. Click Downloads and drivers in the Support topics section.Prefacexvii

IBM Confidential3. Select the Software category.4. Select a product in the Sub-category list.5. In the Find downloads and drivers by product section, select one softwarecategory from the Category list.6. Select one product from the Sub-category list.7. Type more search terms in the Search within results if you want to refine yoursearch.8. Click Search.9. From the list of downloads returned by your search, click the name of a fix toread the description of the fix and to optionally download the fix.For more information about the types of fixes that are available, see the IBMSoftware Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.Receiving weekly support updatesTo receive weekly e-mail notifications about fixes and other software support news,follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/support.2. Click My support in the upper right corner of the page.3. If you have already registered for My support, sign in and skip to the nextstep. If you have not registered, click register now. Complete the registrationform using your e-mail address as your IBM ID and click Submit.4. Click Edit profile.5. In the Products list, select Software. A second list is displayed.6. In the second list, select the product segment, Storage Management. A thirdlist is displayed.7. In the third list, select the product sub-segment, Data Protection. A list ofapplicable products is displayed.8. Select the products for which you want to receive updates, for example, IBMTivoli Storage Manager for Mail.9. Click Add products.10. After selecting all products that are of interest to you, click Subscribe to emailon the Edit profile tab.11. Select Please send these documents by weekly email.12. Update your e-mail address as needed.13. In the Documents list, select Software.14. Select the types of documents that you want to receive information about.15. Click Update.If you experience problems with the My support feature, you can obtain help inone of the following ways:OnlineSend an e-mail message to erchelp@ca.ibm.com, describing your problem.By phoneCall 1-800-IBM-4You (1-800-426-4968).xviii Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialContacting IBM Software SupportIBM Software Support provides assistance with product defects.Before contacting IBM Software Support, your company must have an active IBMsoftware maintenance contract, and you must be authorized to submit problems toIBM. The type of software maintenance contract that you need depends on thetype of product you have:v For IBM distributed software products (including, but not limited to, Tivoli,Lotus ® , and Rational ® products, as well as DB2 ® and WebSphere ® products thatrun on Windows or UNIX ® operating systems), enroll in Passport Advantage ® inone of the following ways:OnlineGo to the Passport Advantage Web site at http://www.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm and clickHow to Enroll.By phoneFor the phone number to call in your country, go to the IBM SoftwareSupport Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.v For customers with Subscription and Support (S & S) contracts, go to theSoftware Service Request Web site at https://techsupport.services.ibm.com/ssr/login.v For IBM eServer software products (including, but not limited to, DB2 andWebSphere products that run in zSeries ® , pSeries ® , and iSeries environments),you can purchase a software maintenance agreement by working directly withan IBM sales representative or an IBM Business Partner. For more informationabout support for eServer software products, go to the IBM Technical SupportAdvantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.If you are not sure what type of software maintenance contract you need, call1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go tothe contacts page of the IBM Software Support Handbook on the Web athttp://techsupport.services.ibm.com/guides/contacts.html and click the nameof your geographic region for phone numbers of people who provide support foryour location.To contact IBM Software support, follow these steps:1. “Determining the business impact”2. “Describing problems and gathering information” on page xx3. “Submitting problems” on page xxDetermining the business impactWhen you report a problem to IBM, you are asked to supply a severity level.Therefore, you need to understand and assess the business impact of the problemthat you are reporting. Use the following criteria:Severity 1The problem has a critical business impact. You are unable to use theprogram, resulting in a critical impact on operations. This conditionrequires an immediate solution.Prefacexix

IBM ConfidentialSeverity 2The problem has a significant business impact. The program is usable, butit is severely limited.Severity 3The problem has some business impact. The program is usable, but lesssignificant features (not critical to operations) are unavailable.Severity 4The problem has minimal business impact. The problem causes little impacton operations, or a reasonable circumvention to the problem wasimplemented.Describing problems and gathering informationWhen describing a problem to IBM, be as specific as possible. Include all relevantbackground information so that IBM Software Support specialists can help yousolve the problem efficiently. To save time, know the answers to these questions:v What is the version and release level of your Tivoli Storage Manager serverproduct? Enter the query status command to determine this information. Forexample:query statusv What software versions were you running when the problem occurred?v Do you have logs, traces, and messages that are related to the problemsymptoms? IBM Software Support is likely to ask for this information.v Can you create the problem again? If so, what steps were performed to createthe problem?v Did you make any changes to the system? For example, did you make changesto the hardware, operating system, networking software, and so on.v Are you currently using a workaround for the problem? If so, be prepared toexplain the workaround when you report the problem.Submitting problemsYou can submit your problem to IBM Software Support in one of two ways:OnlineByClick Submit and track problems on the IBM Software Support site athttp://www.ibm.com/software/support/probsub.html. Type yourinformation into the appropriate problem submission form.phoneFor the phone number to call in your country, go to the contacts page ofthe IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the nameof your geographic region.If the problem you submit is for a software defect or for missing or inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. Whenever possible,IBM Software Support provides a workaround for you to implement until theAPAR is resolved and a fix is delivered. IBM publishes resolved APARs on theIBM product support Web pages daily, so that other users who experience thesame problem can benefit from the same resolutions.For more information about problem resolution, see Searching knowledge basesand Obtaining fixes.xx Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialConventions used in this bookThis guide uses several conventions for special terms and actions, operatingsystem-dependent commands and paths.This guide uses the following typeface conventions:Bolditalicsboldv Commands, keywords, authorization roles, or other information that youmust use.v Example: Log on to the server as root user.v Values or variables that you must provide.v Emphasized words and phrases.v Example: The node name of the production node and backup node must notbe the same.italicsv Options and parameters.monospacev Example: Specify the value for the compression option.v Directories, parameters, URLs, and output examples.v Example: The product is installed in the C:\programfiles\tivoli\tsm\client\ba directory.UPPER CASEv Environment variables associated with Tivoli Storage Manager, operatingsystems, or Exchange Server.v Example: Make sure the DSM_DIR environment variable is set correctly.TypefaceconventionsAccessibilityAccessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in this product enable users to do the following:v Use assistive technologies, such as screen-reader software and digital speechsynthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.In addition, the product documentation was modified to include features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats togive the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that userswith vision impairments can understand the contents of the images.Prefacexxi

IBM ConfidentialMagnifying what is displayed on the screenYou can enlarge information on the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. Refer to the documentation provided by youroperating system for more information.Navigating the interface using the keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. Refer to the documentation provided byyour operating system for more information.xxii Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential||||||||||Technical changes for Version 5.5.0 - December 2007IBM Confidential BETA Draft (8/6/07) OnlyThe following changes have been made to this publication:v Microsoft Exchange Server 2007 supportv Volume Shadow Copy Service back ups of Exchange Server 2007 LocalContinuous Replication (LCR) and Cluster Continuous Replication copiesv Veritas Cluster Server supportSee “New product features for 5.5.0” on page 1 for detailed information aboutthese changes.xxiii

xxiv Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialChapter 1. Data Protection for Exchange OverviewThis section provides introductory information about Data Protection for Exchange.Data Protection for Exchange performs online backups and restores of MicrosoftExchange Server storage groups to Tivoli Storage Manager storage and localshadow volumes. You can perform backups and restores using a command-line orgraphical user interface (GUI) on a Windows 2003 system. Refer to your ExchangeServer documentation for complete, detailed information regarding the backup andrestore of Microsoft Exchange Servers.Data Protection for Exchange operations use the Tivoli Storage Managerapplication program interface (API) to communicate with the Tivoli StorageManager server and use the Exchange API to communicate with the ExchangeServer. In addition to using these APIs, Data Protection for Exchange VSSoperations also use the Tivoli Storage Manager backup-archive client and MicrosoftVolume Shadow Copy Service technology to produce an online snapshot(point-in-time consistent copy) of Exchange data that can be stored on localshadow volumes or on Tivoli Storage Manager server storage.You must install Data Protection for Exchange on the same machine as theExchange Server. Data Protection for Exchange must be able to connect to a TivoliStorage Manager server running on any supported operating system. See “Softwareand operating system requirements” on page 25 for the required level of TivoliStorage Manager server. Optionally, the Tivoli Storage Manager server can be onthe same machine as the Exchange Server. Data Protection for Exchange alsosupports operations in a Microsoft Cluster Server (MSCS) or Veritas Cluster Server(VCS) environment.New product features for 5.5.0Data Protection for Exchange 5.5.0 provides new features.Microsoft Exchange Server 2007 supportLegacy and VSS backup, restore, and query operations are now supported onMicrosoft Exchange Server 2007 Servers.In addition, Data Protection for Exchange supports these specific VSS operationsfor Microsoft Exchange Server 2007 data:Local Continuous Replication (LCR) backupsTechnology that allows a copy of a storage group to be created andmaintained on a second set of disks that are connected to the same serveras the production storage group.Cluster Continuous Replication (CCR) backupsTechnology that extends the high availability capabilities of Exchange 2007Mailbox servers using Exchange 2007 failover and management featuresprovided by the Microsoft Windows Cluster service.1

IBM ConfidentialVSS Restore into the Recovery Storage GroupVSS Restore capabilities for the Recovery Storage Group allows data to berestored from a backup (or database copy) without disturbing user accessto the current data.VSS Restore into an alternate storage groupVSS Restore capabilities allow data to be restored to a storage groupdifferent from the storage group that was originally backed up. Thealternate storage group can also be the Recovery Storage Group.Veritas Cluster Server supportVeritas Cluster Server (VCS) provides high availability cluster management ofExchange data. Data Protection for Exchange supports backup and restoreoperations in a VCS environment. “Veritas Cluster Server (VCS) Support” on page22 provides details regarding this new feature.Data Protection for Exchange product featuresData Protection for Exchange provides the following key features 1 :Table 1. Data Protection for Exchange key featuresFeature Referred to as:Back up Exchange Server 2003 databases(running on Windows Server 2003) usingMicrosoft Volume Shadow Copy Service (VSS)technology.Perform a VSS Backup to the Tivoli StorageManager server using an alternate machineinstead of a production machine.Restore VSS Backups that reside on TivoliStorage Manager server storage to theiroriginal location.Restore VSS Backups that reside on localshadow volumes 2 using file-level copymechanisms.Restore VSS Backups that reside on localshadow volumes using hardware-assistedvolume-level copy mechanisms.For more informationsee:VSS Backup “VSS Backup” on page 7Off-loadedBackup“Off-loaded Backup” onpage 10VSS Restore “VSS Restore” on page12VSS Fast Restore “VSS Fast Restore” onpage 12VSS InstantRestoreRestore a VSS Backup to an alternate machine. Alternate serverrestoreTivoli Storage Manager policy-basedmanagement of VSS snapshot backups.Restore the .edb, .stm, and .log files from alegacy backup that resides on Tivoli StorageManager server storage to an alternate path foruse with third-party products (such asIndividual Mailbox Restore utilities).“VSS Instant Restore” onpage 12Appendix D, “Advancedrestore procedures,” onpage 137Server policy “How Tivoli StorageManager server policyaffects Data Protectionfor Exchange” on page18restorefilescommand“Restorefiles command”on page 962 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialTable 1. Data Protection for Exchange key features (continued)Feature Referred to as:A single graphical user interface for performinglegacy and VSS backup, restore, and queryoperations.A single command line interface for performinglegacy and VSS backup, restore, and queryoperations.For more informationsee:GUI Chapter 4, “Using theGraphical User Interface(GUI),” on page 49CLI Chapter 5, “Using theCommand LineInterface,” on page 631Note that in order to use VSS features, you must also install the following:v IBM Tivoli Storage Manager for Copy Services Microsoft Exchange VSS IntegrationModule (required for basic VSS operations)v IBM Tivoli Storage Manager for Copy Services Hardware Devices Snapshot IntegrationModule (required for VSS Instant Restore operations)2The term local shadow volumes is used throughout this document to describe datathat is stored on shadow volumes localized to a disk storage subsystem.Data Protection for Exchange helps protect and manage Exchange Server data bymaking it easy to perform the following actions:v Back up Exchange Server storage groups and transaction logsv Maintain multiple versions of Exchange Server storage group and transaction logbackupsv Restore storage group and transaction log backups and replay the transactionlog filesv Automatically inactivate previous backups when performing a full backupv Automate scheduled backups (see Chapter 6, “Using the Tivoli Storage Managerscheduler,” on page 115)v Set automatic expiration of backup objects that are based on version limit andretention period (see “How Tivoli Storage Manager server policy affects DataProtection for Exchange” on page 18)v Monitor results through the Data Protection for Exchange activity log andautomatically prune the activity logv Query a local Exchange Server or a Tivoli Storage Manager server forconfiguration informationv Legacy restore of mailbox databases into the Exchange Server 2003 RecoveryStorage Group (RSG)v Legacy back up and restore of Exchange Site Replication Service (SRS) databasesv Participate in Microsoft Cluster Server (MSCS) or Veritas Cluster Server (VCS)fail-over environments (see “Microsoft Cluster Server (MSCS) Support” on page21 or “Veritas Cluster Server (VCS) Support” on page 22)v Obtain online task and concept help (see “Documentation” on page 22)v View online documentation for Data Protection for Exchangev Globalization SupportChapter 1. Data Protection for Exchange Overview 3

IBM ConfidentialBackup Processing: OverviewA backup performed by Data Protection for Exchange creates a copy of anExchange Server storage group on Tivoli Storage Manager server storage. Thebackup includes any associated transaction logs.When a Legacy backup operation is initiated, Data Protection for Exchangeperforms the following actions:1. Begins a session with a Tivoli Storage Manager server.2. Informs the Exchange Server that a backup is ready to begin.3. Forwards data from the Exchange Server to the Tivoli Storage Manager server.4. Informs the Exchange Server that the backup is complete.5. Ends the Tivoli Storage Manager server session.Data Protection for Exchange provides backup and restore functions for theExchange storage groups and associated transaction logs. Data Protection forExchange does not provide a complete disaster recovery solution for an ExchangeServer. In a disaster recovery situation, Data Protection for Exchange only restoresstorage groups. Other files need to be restored in a disaster recovery situation.Refer to your Microsoft Exchange Server documentation for a comprehensivediscussion of disaster recovery considerations.Personal folders and personal address books that are stored on Outlook clients arenot protected by Data Protection for Exchange. The Tivoli Storage ManagerBackup-Archive client can be used on the Outlook client platform to back up andrestore these files. Since the Outlook client normally keeps these files locked whenrunning, you should stop the Outlook client before backing up or restoring thesefiles. Note that since Tivoli Storage Manager Backup-Archive client provides openfile support, you may be able to back up and restore these files while the Outlookclient is running.VSS Backup processing: OverviewIt is important to understand that Data Protection for Exchange VSS Backupoperations are implemented through the Tivoli Storage Manager backup-archiveclient. The client serves as the VSS Requestor that communicates with VSS toaccess the Exchange data in order to create shadow copies of Exchange storagegroups. Thus, Data Protection for Exchange serves as a front end for VSS Backupoperations and performs the following actions when a VSS Backup operation isinitiated:1. Validates the state of Exchange server objects.2. Begins a session with a Tivoli Storage Manager server.3. Verifies that the VSS service is running and that the Exchange writer isavailable.4. The Tivoli Storage Manager VSS Requestor lists the backup componentsthrough the VSS Writer.5. The Tivoli Storage Manager VSS Requestor performs the VSS snapshot backuppreparation stage.6. The Tivoli Storage Manager VSS Requestor performs the actual VSS Backup.7. The Tivoli Storage Manager VSS Requestor performs an integrity check on theVSS Backup.8. The Tivoli Storage Manager VSS Requestor backs up the data (and metadata)to a Tivoli Storage Manager server. Optionally, the movement of data to a4 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialBackupFull Backup (Legacy and VSS)A full backup backs up the specified storage group as well as associatedtransaction logs. Data Protection for Exchange deletes these log files afterthe storage group and logs are successfully backed up. The log files are notdeleted if storage groups are not mounted.Incremental Backup (Legacy only)An incremental backup only backs up transaction logs, and then deletesthem. These log files are not deleted if the backup fails. Restoration of anExchange Server storage group from an incremental backup requires thefollowing:v Restore of the last full backupv Restore of any other incremental backups performed between the fullbackup and this incremental backupv Restore of this incremental backupThe log files are not deleted if storage groups are not mounted.Differential Backup (Legacy only)A differential backup only backs up transaction logs, but does not deletethem. If you perform a full backup and then perform only differentialbackups, the last full backup plus the latest differential backup has all dataneeded to bring the storage group back to the most recent state. This typeof backup is also called a cumulative incremental backup.Restoring an Exchange Server storage group from a differential backuprequires the following:v Restore of the last full backupv Restore of this differential backup, but no other differential backupsCopy Backup (Legacy and VSS)A copy backup is similar to a full backup except that transaction log filesare not deleted after the backup. A copy backup is used to make a fullbackup of the Exchange Server storage group without disrupting anybackup procedures that use incremental or differential backups.Database Copy Backup (Legacy only)A database copy backup is a special type that backs up only the specifieddatabase as well as its associated transaction logs. The transaction log filesare not deleted after the backup. A database copy backup is used to makea special full backup of the database without disrupting any backupprocedures that use incremental or differential backups.Note: When circular logging is enabled, you cannot use differential or incrementalbackups. This is because data loss could occur if the log wrapped before anincremental or differential backup is done. If you choose a backup strategy thatinvolves incremental or differential backups, you must disable circular logging forthe Exchange storage group from the Exchange Administrator program.For more information on circular logging, see your Microsoft Exchange Serverdocumentation.methodsData Protection for Exchange provides two main methods for backing up yourdata.6 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialLegacy BackupA legacy backup is a specialized API backup that functions with the Exchangeserver storage engine. It is occasionally referred to as the Exchange serverstreaming backup and restore API. This is the type of backup provided byprevious releases of Data Protection for Exchange.The following characteristics are true of Legacy backups:v Full, copy, incremental, differential, and database copy backup types aresupported.v Backup granularity is at the database and storage group level.v Backups are stored on Tivoli Storage Manager server storage.v Backups are managed through Tivoli Storage Manager server policy.v Backups can be performed in a Microsoft Cluster Server (MSCS) or VeritasCluster Server (VCS) environment.v Backups provide Exchange Server database zeroing functionality.v Backups provide Exchange Server database integrity check functionality.v Backup and restore of SRS databases is supported.VSS BackupA VSS Backup uses Microsoft Volume Shadow Copy Service technology to producean online snapshot (point-in-time consistent copy) of Exchange data that can bestored on local shadow volumes or on Tivoli Storage Manager server storage. Bothof these storage destinations require that sufficient space be available for thesnapshot. A VSS Backup means the Exchange server is not in ″backup mode″ foran extended period of time because the length of time to perform the snapshot isusually measured in seconds and not hours. In addition, a VSS Backup allows asnapshot of large amounts of data at one time since the snapshot works at thevolume level.Optionally, VSS Backups can be stored locally on VSS shadow volumes that aredirectly accessible by the Exchange system, as long as sufficient space is availablefor the snapshot. These types of backups are fast because data is not placed intoTivoli Storage Manager server storage. Restoring these backups is also fast becausethe Exchange data is not transferred from Tivoli Storage Manager server storageover the network. VSS Backups are only available on Exchange Server 2003 andWindows Server 2003.When performing VSS Backups and moving data to Tivoli Storage Manager serverstorage, sufficient space on local snapshot volumes is still required to hold thesnapshot. For Exchange data backed up to Tivoli Storage Manager server storage,the Exchange data on the snapshot volume is sent to the Tivoli Storage Managerserver. Once the data transfer to the server is complete, the snapshot volume ismade available for reuse. If you are storing VSS Backups locally and the maximumnumber of local backup versions to be maintained (as specified by the TivoliStorage Manager policy) is reached, the oldest backup version is expired in orderto create the snapshot for the backup to Tivoli Storage Manager server storage. See“How Tivoli Storage Manager server policy affects Data Protection for Exchange”on page 18 for details regarding how Tivoli Storage Manager proceeds in thissituation.For Exchange data backed up to local shadow volumes, the snapshot backupresides on the shadow copy volume.Chapter 1. Data Protection for Exchange Overview 7

IBM ConfidentialFor Exchange data backed up to both destinations, a local snapshot backup isperformed and the Exchange data on the local snapshot volume is sent to theTivoli Storage Manager server. The local snapshot volume is retained as a localbackup.VSS Backup characteristicsThe following characteristics are true of VSS Backup:v Full and copy backup types are supported. Incremental, differential, anddatabase copy backup types are not supported.v Backup granularity is at the storage group level only.v Backups are managed through Tivoli Storage Manager server policy.v Backups can be stored on local shadow volumes, Tivoli Storage Manager serverstorage, or both locations.v Different policy settings can be defined for each storage location and backupmethod.v Backups to Tivoli Storage Manager server storage can be off-loaded to analternate machine as resource relief for production servers.v Backups can be performed in a Microsoft Cluster Server (MSCS) or VeritasCluster Server (VCS) environment.v Backups do not provide Exchange Server database zeroing functionality.v Backups provide Exchange Server database integrity check functionality.v Backup and restore of SRS is not supported.v Backup and restore into a Recovery Storage Group are not supported.v There is no automatic retry for Data Protection for Exchange VSS operations likethere is for legacy operations.VSS Backup planning requirementsConsider the following requirements when planning for VSS Backups:v Continue to schedule and perform Legacy backups in your strategy.v Make sure you have a well-defined and tested recovery plan that meets yourservice level objectives.v Use single hardware LUNs for each storage group.v Use basic disks.v If you plan to keep some VSS snapshot backups on local shadow volumes only,make sure to consider the VSS provider-specific implementation andconfiguration options when setting up your strategy. For example, if your VSShardware provider supports a full-copy snapshot versus a copy-on-write (COW)snapshot mechanism, be aware that full-copy type implementations have greaterdisk storage requirements but are less risky because they do not rely on theoriginal volume to restore the data. COW implementations require much lessdisk storage but rely completely on the original volume to perform a restore.Since these implementations are entirely controlled by the VSS provider and notData Protection for Exchange, make sure to consult your VSS providerdocumentation for a complete understanding of your VSS implementation.v You cannot perform parallel VSS Backups as this feature is not supported byVSS.v Do not enable circular logging since it has severe limitations and possiblenegative impacts.8 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialv Do not place multiple volumes on the same LUN. Microsoft recommends thatyou configure a single volume/single partition/single LUN as 1 to 1 to 1.System Provider: Be aware that if you are using the Windows VSS SystemProvider, no configuration is required.Software or Hardware Provider: If you use a software or hardware provider,consider the following requirements when planning for VSS Backups:v If a hardware provider is used, the disks that contain Exchange data must beconfigured as basic.v Place databases files for each storage group on their own dedicated logicalvolume.v Place logs for each storage group on their own logical volume.v Do not place non-Exchange data on storage volumes that are dedicated toExchange.v When using hardware snapshot providers, do not share storage group LUNswith other storage groups or applications.v Make sure to read and follow specific installation and configuration instructionsin the documentation provided by your VSS provider vendor.SAN Volume Controller: If you use SAN Volume Controller, consider thefollowing requirements when planning for VSS Backups:v Place databases files for each storage group on their own dedicated logicalvolume.v Place logs for each storage group on their own logical volume.v Do not place non-Exchange data on storage volumes that are dedicated toExchange.v When using hardware snapshot providers, do not share storage group LUNswith other storage groups or applications.v Only one backup is allowed to occur while the background copy process ispending. A new backup is not performed until the background copy process forthe previous backup completes. As a result, local backups for SAN VolumeController storage subsystems should be initiated at a frequency greater than thetime required for the background copy process to complete.VSS Backups of replica copies: Data Protection for Exchange provides VSSBackups of replica copies in Local Continuous Replication (LCR) or ClusterContinuous Replication (CCR) environments. For CCR copies, you must back upthe replica copy from the secondary node of the cluster that currently contains thereplica copy.VSS limitations: Data Protection for Exchange VSS offloaded backups will notfunction correctly if the Exchange storage group, database and/or log locationinformation is specified with UNC-based drive letters. This is not a commonconfiguration. For example, in the Exchange System Manager, you should notspecify the path of an Exchange storage group as:\\host_srv1\c$\Program Files\Exchsrvr\First Storage Groupbut rather as:C:\Program Files\Exchsrvr\First Storage GroupIf you are using a volume mount point, or using a cluster drive, or using acombination of both, you can still use drive-based naming, for example:Chapter 1. Data Protection for Exchange Overview 9

IBM ConfidentialX:\Exch_Mount_Point\Program Files\Exchsrvr\First Storage GroupYou cannot use the UNC-based specification, for example:\\host_srv1\x$\Exch_Mount_Point\Program Files\Exchsrvr\First Storage GroupThe same storage group name appears twice in different lists when issuing a DataProtection for Exchange command-line interface QUERY TSM command. Inaddition, the VSS backups under one of those storage groups are older and theydo not get expired when new VSS backups of the same storage group are taken.This issue can be created when you perform VSS backups of a storage group,followed by a deletion of the storage group, followed by a recreation of the storagegroup with the identical name. Since the new storage group has a globally uniqueID (GUID), the Exchange Server VSS Writer considers this an entirely differentstorage group. There is nothing harmful in this situation. The older backups willremain and follow their assigned policy and the last backups will remain active.This is a known issue that is currently being investigated. To work around thisissue, if you wish to delete the older VSS backups, you can do so by contactingyour Tivoli Storage Manager Server administrator and having the FILESPACEdeleted that corresponds to the old storage group. You must be careful when doingthis so that you delete the filespace with the matching GUID of the older storagegroup. If you are unsure how to identify this, please call IBM Service.When performing a Data Protection for Exchange VSS restore operation, if you arerestoring a VSS backup of a storage group that contains databases that do notcurrently exist in the live storage group, the files for the old databases will still berestored but you will not see any message indicating that there is a problem. Thisis a harmless situation. To work around this issue, if you do not want theadditional data to be restored, you can perform the VSS restore operation and onlyselect the desired databases that you would like to be restored.Off-loaded BackupAn off-loaded backup uses an alternate machine to move the data to the TivoliStorage Manager server. This type of backup shifts the backup load from theproduction machine to another machine. This frees the production system to servethe Exchange server. This requires that a VSS hardware provider that supportstransportable shadow copy volumes is installed on the production and secondarymachines.Restore Processing: OverviewA restore obtains backup copies of Exchange storage groups and transaction logsand returns them to the Exchange Server.v The Exchange Information Store service must be running but the databasesbeing restored within the storage group must be dismounted.When a Legacy restore operation is initiated, Data Protection for Exchangeperforms the following actions:1. Data Protection for Exchange prompts the user to dismount the databases orcancel the restore operation entirely. This prompt occurs in the GUI only.Command line interface users must dismount necessary databases.2. Starts a session with a Tivoli Storage Manager server.3. Informs the Exchange Server that a restore is about to begin.4. Restores the specified storage group(s) and logs from the Tivoli StorageManager server. The logs are restored to a temporary location as specified bythe user.10 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialWhen performing a restore of a mailbox database with Exchange Server 2003, ifa Recovery Storage Group exists, the mailbox database will be restored to theRecovery Storage Group instead of to the original storage group. Also, whenrestoring a mailbox database to a Recovery Storage Group, you must specifythe option to replay restored logs only or the restore operation may fail. SelectReplay Restored Logs ONLY in the GUI Restore Window or specify/recover=applyrestoredlogs on the command line. This note ONLY applies toLegacy restores. VSS Restores to the Recovery Storage Group are NOTsupported by Microsoft.5. Informs the Exchange Server that the restore has completed. At this point youhave the option of:v starting recoveryv mounting the databases (when recovery completes)6. Ends the Tivoli Storage Manager server session.Depending on the backup strategy you choose, restoring an Exchange storagegroup can involve restoring multiple backup objects from the Tivoli StorageManager server. See “Backup strategies” on page 14.To restore an individual item such as a message, mailbox, or folder, use DataProtection for Exchange to restore the entire database containing the desiredmailbox or public folder to an alternate Exchange Server. From the alternateExchange Server, use the Exchange Administrator program to access and copy theitem you want. See Appendix D, “Advanced restore procedures,” on page 137 fordetails on performing this procedure.You can also use Data Protection for Exchange to restore mailbox databases to aRecovery Storage Group with Exchange Server 2003. See “Exchange 2003 RecoveryStorage Group” on page 138 for details on performing this procedure. WithMicrosoft Exchange Server, you can also use the item Recovery feature of theExchange Client to recover messages and folders which are accidentally deleted.Exchange Server 2003 and Exchange Server 2007 also provide a ″deleted mailbox″feature to recover deleted mailboxes. For more information, see your MicrosoftExchange Server documentation.The restorefiles command restores the .edb, .stm, and .log files from a specifiedData Protection for Exchange backup (that resides on Tivoli Storage Managerserver storage) into a specified directory. It also enables third-party IndividualMailbox Restore products. See “Restorefiles command” on page 96 for moreinformation about this command. The brickback.doc file (located in the default DataProtection for Exchange installation directory) also provides information on how toperform brick-level backup and restore operations.When a VSS restore operation is initiated, Data Protection for Exchange performsthe following actions:1. Validates the state of Exchange server objects.2. When using the Data Protection for Exchange GUI, you are prompted whetherto dismount the databases within the selected storage group.3. Begins a session with a Tivoli Storage Manager server.4. Verifies that the VSS service is running and that the Exchange writer isavailable.5. The Tivoli Storage Manager VSS Requestor performs the VSS snapshot restorepreparation stage.Chapter 1. Data Protection for Exchange Overview 11

IBM ConfidentialRestore6. The Tivoli Storage Manager VSS Requestor restores the backup data.7. The Tivoli Storage Manager VSS Requestor marks the restore as complete inVSS.8. Optionally, mounts databases to run recovery.methodsData Protection for Exchange provides two main methods for restoring your data.Legacy RestoreA legacy restore is the type of restore provided by previous releases of DataProtection for Exchange. It restores legacy backups (Exchange database files andlog files) from Tivoli Storage Manager server storage to their original location. Likea legacy backup, it uses a specialized API restore that functions with the Exchangeserver storage engine. It is occasionally referred to as the Exchange serverstreaming backup and restore API.VSS RestoreThis restores VSS Backups (Exchange database files and log files) that reside onTivoli Storage Manager server storage to their original location. The followingcharacteristics are true of VSS Restores:v Full and copy backup types can be restored. Incremental, differential, anddatabase copy backup types are not supported by VSS and therefore, cannot berestored.v Restore granularity is at the database level.v Supports restoring one (or more) storage groups from a VSS snapshot backuplocated on Tivoli Storage Manager server storage.v VSS requires that data must always be restored to the same drive letters andpaths as existed during the original backup.v Restores can be performed in a Microsoft Cluster Server (MSCS) or VeritasCluster Server (VCS) environment.v Due to a Microsoft limitation, Recovery Storage Group (RSG) restores andrestores of SRS backups are not supported.v Supports restoring a VSS Backup (directly from Tivoli Storage Manager serverstorage) to an alternate machine.VSS Fast RestoreA VSS Fast Restore restores VSS Backups that reside on local shadow volumes. Ingeneral, restore processing can conclude within minutes instead of hours in thissituation. The following characteristics are true of VSS Fast Restore restores:v Full and copy backup types can be restored. Incremental, differential, anddatabase copy backup types are not supported by VSS and therefore, cannot berestored.v Restore granularity is at the database level.v The key component of producing a VSS Fast Restore is the speed with which theapplication can become operational with the data that resides on local shadowvolumes. Be aware that even though the data is restored relatively quickly, thetransaction logs must still be replayed after the restore and therefore, the time ofrecovery for the application can increase.VSS Instant RestoreA VSS Instant Restore is when a set of target volumes (that contain a validsnapshot) are copied back to the original source volumes using hardware-assisted12 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialvolume-level copy mechanisms. The application can return to normal operations assoon as the hardware-assisted volume-level copy has been started and the logreplay is complete.The key component of producing a VSS Instant Restore is the speed with whichthe application can become operational with the data that resides on local shadowvolumes. Be aware that even though the data is restored relatively quickly, thetransaction logs must still be replayed after the restore and therefore, the time ofrecovery for the application can increase.Be aware that a VSS Instant Restore is only possible when all of the data (from thestorage group or database specified for restore) resides on storage subsystemssupported by the VSS Instant Restore. If part of the data being restored (includingthe log files) resides on a local disk, a VSS Instant Restore of this data is notsupported. In this situation, a VSS Fast Restore is performed.When performing a VSS Instant Restore, you must restore ALL databases withinthe specified storage group. You cannot perform a partial restore (/partial) whileusing VSS Instant Restore. Although Data Protection for Exchange allows thisoperation to begin, it will either fail or complete with undesirable consequences. Ifyou need to restore just one database from a VSS Backup that resides on local VSSshadow volumes on DS or SAN Volume Controller disks, make sure to select theDisable VSS Instant Restore option in the Data Protection for Exchange GUIRestore Window or specify /instantrestore=no on the command line interface. IfVSS Instant Restore capability is needed for single databases, make sure to placethese databases in their own storage group.Although VSS Instant Restore is the default restore method when all Exchangedata specified for restore resides on storage subsystems supported by the VSSInstant Restore, a failover to VSS Fast Restore can occur when an error is detectedearly enough in the VSS Instant Restore process to trigger the failover. In thissituation, an error is logged in the dsmerror.log file used by the DSMAGENT.However, a failover to VSS Fast Restore may not always be possible. For example,if an error occurs later in the restore process (such as a pending background copyon the storage subsystem, a failure to start the FlashCopy operation on thesnapshot provider system, or other hardware error), VSS Instant Restore processingfails without a failover to VSS Fast Restore.VSS Instant Restore does not support SSL for Common Information Model ObjectManager (CIMOM) communication. As a result, perform the following tasks beforeattempting a VSS Instant Restore:1. Configure the CIMOM server to accept communication without SSL byspecifying these values for the following options in the CIMOMcimom.properties file:Port=5988ServerCommunication=HTTPDigestAuthentication=falseSslEnabled=false (SVC only)Restart the CIMOM service after making these changes.2. If you are using SAN Volume Controller, you must also change theseWebSphere files so that they use the new CIMOM settings (the CIMOM islocated by default in the svcconsole directory):Chapter 1. Data Protection for Exchange Overview 13

IBM ConfidentialC:\Program Files\IBM\svcconsole\console\embeddedWAS\installedApps\DefaultNode\ICAConsole.ear\ICAConsole.war\WEB-INFC:\Program Files\IBM\svcconsole\console\embeddedWAS\installedApps\DefaultNode\SVCConsole.ear\SVCConsole.war\WEB-INFC:\Program Files\IBM\svcconsole\console\embeddedWAS\config\cells\DefaultNode\applications\ICAConsole.ear\deployments\ICAConsole\ICAConsole.war\WEB-INFC:\Program Files\IBM\svcconsole\console\embeddedWAS\config\cells\DefaultNode\applications\SVCConsole.ear\deployments\SVCConsole\SVCConsole.war\WEB-INFRestart the WebSphere service after making these changes.Be aware of the following considerations when planning for VSS Instant Restore:v Requires IBM System Storage Support for Microsoft Volume Shadow CopyService software.v Backups must reside on the same DS6000, DS8000, or SAN Volume Controllerstorage subsystem to which they are restored.Backward compatibility: On DS storage:v Backups created with IBM Tivoli Storage Manager for Copy Services Version5.3.3 on local shadow volumes that reside on DS storage cannot be restored viaVSS Instant Restore using IBM Tivoli Storage Manager for Copy Services Version5.4. You must create backups on local shadow volumes (residing on DS storage)using IBM Tivoli Storage Manager for Copy Services Version 5.4 in order torestore them via VSS Instant Restore.v Backups created with IBM Tivoli Storage Manager for Copy Services Version5.3.3 on local shadow volumes (residing on DS storage) can be restored via VSSFast Restore using IBM Tivoli Storage Manager for Copy Services Version 5.4.On SAN Volume Controller storage: Backups created with IBM Tivoli StorageManager for Copy Services Version 5.3.3 on local shadow volumes that reside onSAN Volume Controller storage can be restored via VSS Instant Restore (and VSSFast Restore) using IBM Tivoli Storage Manager for Copy Services Version 5.4.BackupstrategiesDepending on your specific requirements regarding network traffic, backupwindow, and acceptable restore times, you might choose to follow different backupstrategies. It is important to completely understand all aspects of Exchange Serverdisaster recovery as well as backup considerations recommended by Microsoft.Refer to your Exchange Server documentation for this information. Somecommonly used strategies are described below.v If you choose a strategy that involves incremental or differential backups,circular logging must be disabled on the storage groups of the Exchange Server.v You should not mix incremental and differential backups. Differential backupswill only back up changes made since the last incremental backup. Incrementalbackups performed after differential backups contain all changes since the lastincremental or full backup. Restores are more complicated when using a mixedstrategy. You need to determine on an individual basis which transaction logbackups (differential or incremental) to restore along with the full backup.v If you plan to use VSS Backups, you should continue to use Legacy Backups aswell.v When scheduling Legacy and VSS Backups, make sure they do not overlap.v Incremental and differential legacy backups cannot be restored with full or copyVSS Backups.14 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialFull backups onlyThis approach is best for Exchange Servers that are relatively small because eachbackup contains enough data to restore the entire storage group. Each backuptakes longer to perform, but the restore process is the most efficient because onlythe most recent (or other appropriate) full backup needs to be restored.Full backup plus incremental backupsThis strategy is commonly used when the normal backup window or networkcapacity cannot support a full backup each time. In such cases, a periodic fullbackup followed by a series of incremental backups allows the backup windowand network traffic to be minimized during peak usage times. For example, youcan perform full backups on the weekend and incremental backups during theweek. The full backups can be done during low usage times when a larger backupwindow and increased network traffic can be tolerated. The restore processbecomes more complex, however, because a full backup, as well as subsequentincremental backups, must be restored. In addition, transactions within the logsmust be applied which increases process time. As a result, the more transactionsapplied, the longer the recovery process.If you use this backup strategy, you must decide whether the Tivoli StorageManager storage management policies are modified, to ensure all incrementalbackups are stored together on the Tivoli Storage Manager server (collocated). Thishelps improve restore performance by reducing the number of media mountsnecessary for restoring a series of incremental backups. See “How Tivoli StorageManager server policy affects Data Protection for Exchange” on page 18 for moreinformation.Full backup plus differentialsThis process provides an easier restore than the full plus incremental backup. Thisapproach might be useful if your backup window and network capacity canhandle the backup of all transaction logs that accumulate between full backups.This is because it requires the transfer of only one differential plus the last fullbackup to accomplish a restore. However, the same amount of data must betransferred in the differential image, as in the series of incremental backups.Therefore, a full backup plus differential backup policy increases network trafficand Tivoli Storage Manager storage usage. This assumes that the differentialbackups are performed with the same frequency as the incremental backups.You should carefully consider whether there is sufficient advantage to justify theadditional resource necessary to resend all prior transaction logs with eachsubsequent differential backup.Using VSS and Legacy Backups togetherMicrosoft supports and recommends using both methods of backup in yourcomplete backup strategy. However, Microsoft also states that you cannot mix thetwo types of backups. For example, a Legacy incremental or differential backupcannot be applied to a VSS full or copy backup. This is noted in the MicrosoftExchange Server 2003 SDK documentation. The Exchange store will prevent youfrom mixing backup types.Also, be aware of the following best practice:v Legacy and VSS Backups to Tivoli Storage Manager server storage are usuallydictated by time, not versions.Chapter 1. Data Protection for Exchange Overview 15

IBM Confidentialv Backups to local shadow volumes are usually dictated by versions because ofspace limitations and provisioning of VSS storage.Table 2. Backup strategy characteristicsStrategycharacteristics Legacy backup only Legacy backup plus VSS backupAvailable backuptypes:COPY 1+ per monthFULL 1+ per weekLegacy COPY 1+ per monthLegacy FULL 1+ per weekAvailable restoretypes:INCR 1+ per dayRestore to production ExchangeServerRestore attributes: FULL, COPY, INCR, DIFF,DBCOPYServer and storage group levelrestore granularityPoint-in-time recoveryRoll-forward recoveryRestore to alternate machineRecovery Storage Group(Exchange Server 2003)VSS FULL 1+ per dayVSS:v VSS Restore 1v VSS Fast Restore 2v VSS Instant Restore 3Legacy:v Restore to the productionExchange ServerFULL, COPYServer and storage group levelrestore granularityPoint-in-time recoveryRoll-forward recoveryRestore to alternate machineRecovery Storage Group (ExchangeServer 2003 and Legacy only)1 Files are copied from the Tivoli Storage Manager server directly to theproduction source volumes.2 Files are copied from local shadow volumes directly to the productionsource volumes.3 Snapshot volumes are copied to the production source volumes. SANVolume Controller, DS6000, or DS8000 is required to perform this type ofrestore.Using VSS operations in a clusterData Protection for Exchange supports VSS operations in a clustered ExchangeServer environment.Cluster requirements for VSSThe following requirements must be met for VSS operations to performsuccessfully in a cluster environment:v The vssaltstagingdir option must be specified when the following circumstancesare true of your cluster environment:– Tivoli Storage Manager performs the VSS operations.– VSS Backups are stored on local shadow volumes.16 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialThis option must be specified in the dsm.opt file for all potentiallocaldsmagentnode nodes that could be running the Tivoli Storage ManagerRemote Client Agent Service (DSMAGENT):vssaltstagingdir d:\dird: represents a shared drive that is accessible by all nodes in the cluster. It canalso be a disk that follows the Virtual Exchange Server. \dir represents adirectory located on the shared drive. This option must be specified on all nodesthat are used in the cluster. For example:vssaltstagingdir Q:\TSMVSSv When registering nodes to the Tivoli Storage Manager server specifically for VSSoperations, do not specify the Tivoli Storage Manager USerid=NONE parameter.VSS operations will fail when this parameter is specified.v Make sure to specify the following options in each of the dsm.opt files that areused for the LOCALDSMAGENT, REMOTEDSMAGENT, and OFFLOADmachines:CLUSTERNODE NOCLUSTERDISKSONLY NOCluster limitations for VSSBe aware of these limitations when performing VSS operations in a clusterenvironment:v All servers within the cluster must use the same levels of Tivoli StorageManager, Windows, and other applicable software.v Microsoft KB921181 is required to perform VSS Instant Restore in a clusterenvironment.v Dynamic disks are not supported.v VSS Backups that reside on local VSS shadow volumes can only be restored tothe physical node that created the VSS Backup. For example, if NODE_A of acluster created a VSS Backup and stored it on local shadow volumes, NODE_Bof the cluster cannot restore that particular VSS Backup. NODE_B can onlyrestore VSS Backups stored on the Tivoli Storage Manager server or VSSBackups stored on local shadow volumes that were created by NODE_B. This isdue to a limitation related to VSS cluster support and not to Tivoli StorageManager.v VSS Backups that reside on local VSS shadow volumes may be deleted in theevent of a cluster failover. This means that if NODE_A of a cluster created alocal VSS Backup and afterward, the Exchange Server fails over to NODE_B, if aData Protection for Exchange VSS operation is performed on NODE_B of thecluster, the local VSS Backup created by NODE_A will be deleted. This is causedby the fact that the Microsoft VSS architecture is not cluster aware.v The Tivoli Storage Manager Client Acceptor Daemon (CAD) must be installed oneach cluster node so that it can continue operations in the event of a failover.Make sure the CAD service name is the same on all cluster nodes so that it canbe started by a generic cluster service.v It is recommended that the Local DSMAgent client node be a separate nodefrom your normal backup-archive client, as this CAD service will need to bemade a non cluster option.v The Remote DSMAgent client node does not require you to register a separatenode for each server within the cluster as this server only acts as a secondaryserver.v Use the Microsoft vssadmin and vshadow commands to verify the environment.Chapter 1. Data Protection for Exchange Overview 17

IBM Confidentialv A Data Protection for Exchange configuration file should be configured for eachnode in the cluster. These files are almost identical, except that thelocaldsmagentnode parameter points to the corresponding local DSMAgent oneach node.If you plan to perform scheduled VSS operations in a cluster environment, beaware of these considerations:v Install the Tivoli Storage Manager scheduler as a Windows service on bothcluster nodes.v If the command file resides on a local drive, you must make sure that it remainsconsistent on all cluster nodes. Optionally, you can create the command file on ashared drive. Make sure the objects parameter (specified with the defineschedule command on the Tivoli Storage Manager server) points to thiscommand file.Additional useful cluster information is available in the IBM Redbook, Using IBMTivoli Storage Manager for Copy Services to Back Up Microsoft Exchange with VSS.How Tivoli Storage Manager server policy affects Data Protection forExchangeTivoli Storage Manager policy determines how Data Protection for Exchangebackups are managed on Tivoli Storage Manager storage. The Tivoli StorageManager server recognizes Data Protection for Exchange as a node. Data that isbacked up to Tivoli Storage Manager storage from this Data Protection forExchange node is stored and managed according to settings specified for TivoliStorage Manager server policy items.Tivoli Storage Manager policy can manage the VSS Backups that are placed onlocal shadow volumes as well as in Tivoli Storage Manager server storage pools.The Tivoli Storage Manager server is responsible for managing VSS Backups,whether the backup is stored on local shadow volumes or on the Tivoli StorageManager server. Be aware that while a VSS snapshot (created for back up to TivoliStorage Manager server storage) is deleted after the backup completes, a VSSsnapshot (created for back up to local shadow volumes) remains active until thebackup version is expired according to the policy settings for VSS Backups on localshadow volumes.The number of local backup versions maintained by the Tivoli Storage Managerserver is determined by the value specified by the Tivoli Storage Manager serververexists parameter (defined in the copy group of the management class to whichthe local backup belongs). The number of Target Volume sets allocated for localbackups should be equal to the verexists parameter. For example, if verexists=3,then at least three sets of Target Volumes must be allocated for the backup tocomplete successfully. If only two sets of Target Volumes are allocated, the thirdand subsequent backup attempt will fail. If more sets of Target Volumes exist thanthe number specified by the verexists parameter, these sets are ignored by theTivoli Storage Manager server.The policy management of local backups is responsible for reconciling the localbackup repository with the information stored on the Tivoli Storage Managerserver. For example, if Target Volume LUNs that were used for a local backup areremoved from the storage subsystem, the information representing the backup onthe Tivoli Storage Manager server must be reconciled. Likewise if the TivoliStorage Manager server policy has determined that a local backup copy is no18 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentiallonger needed, the local backup manager must free the Target Volume LUNs to thestorage subsystem so that these LUNs can be used for future backup operations.Tivoli Storage Manager automatically detects these situations and performs thereconciliation.ImportantTivoli Storage Manager requires that sufficient storage space be available to createshadow volumes required for VSS Backup processing. Even when the VSS Backupdestination is the Tivoli Storage Manager server, storage space to create a shadowvolume is still required (though on a temporary basis). Since the value of theverexists parameter (specified for your local backup policy) determines the numberof backup versions to retain on local shadow volumes, a verexists=1 setting willcause the deletion of an existing backup on local shadow volumes (during a VSSBackup to Tivoli Storage Manager server storage) in order to create enoughtemporary space for the new snapshot. Therefore, if you want to keep N backupson local shadow volumes and also perform VSS Backups to Tivoli Storage Managerserver storage, make sure you provision enough storage space on local shadowvolumes and specify verexists=N+1.Make sure to specify a verexists value that accommodates your VSS Backup goals.If you have limited storage space for VSS operations and are restricted to averexists=1 setting, you can take advantage of the Backup Destination BOTHoption. This stores the backup on local shadow volumes as well as sends a copy toTivoli Storage Manager server storage.It is possible for VSS Backups (that Data Protection for Exchange creates and storeson local shadow volumes) to be modified and deleted from outside of TivoliStorage Manager control. For example, the Microsoft VSSADMIN DELETESHADOWS command can remove a VSS Backup managed by Tivoli StorageManager without Tivoli Storage Manager being able to prevent such a removal. Insuch a situation, Tivoli Storage Manager recognizes the backup removal andreconciles its index of available backups with what resides on local shadowvolumes. It is important to be aware of this potential for removal and establish astrategy that protects VSS Backup data stored on local shadow volumes from beingcompromised.Be aware that the following issues impact your Tivoli Storage Manager policy formanaging VSS Backups:v Overall backup strategy.v Length of time that VSS Backups will reside on Tivoli Storage Manager serverstorage.v Number of VSS Backup versions to reside on Tivoli Storage Manager serverstorage.v Types of VSS Backups to reside on Tivoli Storage Manager server storage.v Number of VSS Backup versions to reside on local shadow volumes.v Types of VSS Backups to reside on local shadow volumes.v The amount of available target volume storage provisioned for VSS operations.Chapter 1. Data Protection for Exchange Overview 19

IBM ConfidentialSecurity||||||||||||Data Protection for Exchange must be registered to the Tivoli Storage Managerserver and use the appropriate node name and password when connecting to theTivoli Storage Manager server. Standard Tivoli Storage Manager securityrequirements apply to Data Protection for Exchange.In order to perform backup and restore tasks, Data Protection for Exchange mustbe operating in an account that meets these two conditions:1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator rolev Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group for themachine on which the Exchange server is running.PerformanceMany factors can affect the backup and restore performance of your ExchangeServer. Some of these, such as hardware configuration, network type, and capacity,are beyond the control of Data Protection for Exchange. These factors are notwithin the scope of this document. However, some options that are related to DataProtection for Exchange can be tuned for optimum performance. See “SpecifyingData Protection for Exchange options” on page 39 for details regarding theseoptions.In addition, be aware of how the following issues affect performance:v Backups to local shadow volumes eliminates the transfer of data to the TivoliStorage Manager server.v During VSS Backup processing, integrated Exchange integrity checking readsevery page in the files to be backed up. As a result, backup processing time canbe significant. You can specify the /skipintegritycheck parameter to bypassintegrity checking. However, this parameter is only valid for copy-type VSSBackups as Microsoft requires integrity checking be performed for full-type VSSBackups.v The time required to perform a snapshot ranges from seconds to minutes,depending on the type of VSS provider used.v Backup-archive client settings can affect performance when backing up data tothe Tivoli Storage Manager server.Buffering (Legacy only)Data Protection for Exchange is a multithread application that uses asynchronousexecution threads to transfer data between the Exchange servers and Tivoli StorageManager servers. To accomplish this, multiple data buffers are used to allow onethread to receive data from one side, while another thread sends data to the otherside. For example, one thread reads data from an Exchange Server while anotherthread sends data to the Tivoli Storage Manager server. As a result, the ExchangeServer continues sending data to available buffers regardless of the ability of theTivoli Storage Manager server to receive the data. The number and size of buffersthat are allocated for this can be configured through the Settings dialog in theData Protection for Exchange GUI. The number and size of buffers can also be20 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialspecified in the buffers and buffersize parameters on the command line interface.For more information, see Chapter 5, “Using the Command Line Interface,” onpage 63.LANFreeRunning Data Protection for Exchange in a LAN free environment allows data tobe sent directly to storage devices. As a result, data bypasses potential networkcongestion. However, you must be properly equipped to operate in a LAN freeenvironment. The Tivoli Storage Manager Managed System for SAN Storage AgentUser’s Guide provides detailed information about setting up a LAN Freeenvironment.In addition to specific LAN free requirements, you must specify the enablelanfreeoption for Data Protection for Exchange to activate this LAN free feature.v For Legacy backups, specify enablelanfree yes in the Data Protection forExchange options file.v For VSS Backups, specify enablelanfree yes in the backup-archive client optionsfile.Microsoft Cluster Server (MSCS) SupportData Protection for Exchange supports Exchange Servers running in MSCSconfigurations. The list below provides information you should consider whenrunning Data Protection for Exchange in an MSCS environment.Note: References to the Exchange Server in this section pertain to the virtualExchange Server name in an MSCS environment.v Data Protection for Exchange must be installed on both nodes of the cluster. Inaddition, when installing Data Protection for Exchange, it must be installed on adisk local to each node (not a shared cluster disk).v Use identical configurations in the Tivoli Storage Manager options file whenconfiguring Data Protection for Exchange on each node of the cluster. You mustspecify clusternode yes in the Data Protection for Exchange options file.v When using the Tivoli Storage Manager scheduler for automating backups, youmust install the scheduler service on both nodes of the cluster to enable failoversupport. See Chapter 6, “Using the Tivoli Storage Manager scheduler,” on page115 for more information.v The Tivoli Storage Manager server treats backups as coming from a single server(the virtual Exchange server) regardless of the cluster node on which the backupwas performed.v When running in an MSCS environment, Data Protection for Exchange must beinvoked from the command line with the /excserver parameter. For example, ifthe Exchange virtual server name on the Microsoft Cluster is excvs1, the GUIinvocation istdpexc /excserver=exc1and an example command line interface invocation istdpexcc backup "First Storage Group" full /excserver=excvs1Chapter 1. Data Protection for Exchange Overview 21

IBM ConfidentialVeritas Cluster Server (VCS) SupportDocumentationData Protection for Exchange supports Exchange Servers running in Veritas ClusterServer (VCS) configurations. The list below provides information you shouldconsider when running Data Protection for Exchange in a VCS environment.Note: References to the Exchange Server in this section pertain to the virtualExchange Server name in a VCS environment.v Data Protection for Exchange must be installed on both nodes of the cluster. Inaddition, when installing Data Protection for Exchange, it must be installed on adisk local to each node (not a shared cluster disk).v Use identical configurations in the Tivoli Storage Manager options file whenconfiguring Data Protection for Exchange on each node of the cluster. You mustspecify clusternode yes in the Data Protection for Exchange options file.v When using the Tivoli Storage Manager scheduler for automating backups, youmust install the scheduler service on both nodes of the cluster to enable failoversupport. See Chapter 6, “Using the Tivoli Storage Manager scheduler,” on page115 for more information.v The Tivoli Storage Manager server treats backups as coming from a single server(the virtual Exchange server) regardless of the cluster node on which the backupwas performed.v When running in a VCS environment, Data Protection for Exchange must beinvoked from the command line with the /excserver parameter. For example, ifthe Exchange virtual server name on the VCS is excvcs1, the GUI invocation istdpexc /excserver=excvcs1and an example command line interface invocation istdpexcc backup "First Storage Group" full /excserver=excvcs1Data Protection for Exchange provides product documentation in these formats.Installation and User’s GuideThe IBM Tivoli Storage Manager for Mail Data Protection for Microsoft Exchange ServerInstallation and User’s Guide 5.5 provides the most detailed information regardinghow to install, configure, and use Data Protection for Exchange 5.5 in a Windows2003 environment. This publication is provided in the following locations in PDFand XHTML format:v IBM Tivoli Storage Manager for Mail 5.5 Quick Start CDThe IBM Tivoli Storage Manager for Mail 5.5 Quick Start CD is available withthe Data Protection for Exchange product or can be downloaded from the IBMPassport Advantage Web site: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp. The Quick Start CD also contains the IBM TivoliStorage Manager for Mail 5.5 Quick Start Guide which provides a high-leveloverview of how to install Data Protection for Exchange.v IBM Tivoli Storage Manager for Copy Services 5.5 Quick Start CDThe IBM Tivoli Storage Manager for Copy Services 5.5 Quick Start CD isavailable with the Data Protection for Exchange product or can be downloadedfrom the IBM Passport Advantage Web site: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp. The Quick Start CD also contains the IBM22 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialTivoli Storage Manager for Copy Services 5.5 Quick Start Guide which provides ahigh-level overview of how to install Data Protection for Exchange for VSSoperations.v Online at the Tivoli Information Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jspGUI Online HelpGUI online help is provided for specific information related to tasks that areperformed in the Data Protection for Exchange GUI. After launching the GUI, go toHelp->Data Protection for Microsoft Exchange Server. The online help displays.See Chapter 4, “Using the Graphical User Interface (GUI),” on page 49 foradditional informationCommand Line HelpCommand line help is also provided for specific information related to tasks thatare performed on the Data Protection for Exchange command line. Enter tdpexcchelp on the Data Protection for Exchange command line interface for a list ofavailable help topics. See “Help command” on page 110 for additional information.GlobalizationData Protection for Exchange supports the following languages:v American Englishv Brazilian PortuguesevvvvvFrenchGermanItalianJapaneseKoreanv Simplified ChinesevSpanishv Traditional ChineseIf you want to use a language other than English, you must install the LanguagePack for the desired language. See the description of “Language Packs” on page 30for detailed information.Chapter 1. Data Protection for Exchange Overview 23

24 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialChapter 2. Installing Data Protection for ExchangeThis section provides information on the client environment that must exist beforeyou install Data Protection for Exchange. Detailed instructions are also provided oninstalling Data Protection for Exchange on a Windows 2003 workstation.See the readmedpexc_enu.htm file that is shipped on the product installationmedia for current informationSoftware and operating system requirementsData Protection for Exchange requires the following levels of Tivoli StorageManager software:v Tivoli Storage Manager backup-archive client Version 5.5.0 (or later).v Tivoli Storage Manager API Version 5.5.0 (or later).v Tivoli Storage Manager server Version 5.4.0 (or later)Legacy Backup and Restore software and operating systemrequirementsTable 3. Minimum software and operating system requirements for Legacy Backup andRestore operationsOperating SystemMicrosoftWindows 2003(32-bit) 1MicrosoftWindows 2003(x64) 3ExchangeServerExchangeServer 2003 2ExchangeServer 2007 4VSS Provider Tivoli Storage Manager forCopy ServicesNoneNoneNoneNoneBasic VSS software and operating system requirementsTable 4. Minimum software and operating system requirements for basic VSS operationsOperating SystemMicrosoftWindows 2003(32-bit) 1MicrosoftWindows 2003(x64) 3ExchangeServerExchangeServer 2003 2ExchangeServer 2007 4VSS Provider Tivoli Storage Manager forCopy ServicesAny VSS provider that issupported by Microsoftrules for VSS providers.Any VSS provider that issupported by Microsoftrules for VSS providers.Microsoft Exchange VSSIntegration Module Version5.5.0 5Microsoft Exchange VSSIntegration Module Version5.5.0 525

VSS Off-loaded Backup software and operating systemrequirements5.5.0 5 (x64) 3rules for VSS providers.IBM ConfidentialTable 5. Minimum software and operating system requirements for VSS Off-loaded BackupExchange VSS Provider Tivoli Storage Manager forOperating System ServerCopy ServicesMicrosoftWindows 2003(32-bit) 1ExchangeServer 2003 2Any VSS provider thatsupports transportableshadow copies. 6Microsoft Exchange VSSIntegration Module Version5.5.0 (or later) 5MicrosoftWindows 2003(x64) 3ExchangeServer 2007 4Any VSS provider thatsupports transportableshadow copies. 6Microsoft Exchange VSSIntegration Module Version5.5.0 (or later) 5Table 6. Minimum software and operating system requirementsExchange VSS Provider Tivoli Storage Manager forOperating System ServerCopy ServicesMicrosoftExchange On DS storageOn DS storage subsystems:Windows 2003 Server 2003 2 subsystems:v Microsoft Exchange VSS(32-bit) 1v IBM System Storage Integration ModuleVSS Hardware Provider Version 5.5.0 (or later) 52.4.2 (or later)v Hardware DevicesOn SAN VolumeSnapshot IntegrationController storageModule Version 5.5.0 (orsubsystems:later) 8v IBM System Storage On SAN Volume ControllerMicrosoftExchangeSAN Volume Controller storage subsystems:Windows 2003 Server 2007 4Version 2.1.x (or later)(x64) 3v Microsoft Exchange VSSor Version 3.1.x 7Integration Modulev IBM System Storage Version 5.5.0 (or later) 5VSS Hardware Provider v Hardware Devices2.4.3 (or later)Snapshot IntegrationModule Version 5.5.0 (orlater) 8Table 7. Minimum software and operating system requirements for VSS Restore into theRecovery Storage GroupExchange VSS Provider Tivoli Storage Manager forOperating System ServerCopy ServicesMicrosoftExchange Any VSS provider that is Microsoft Exchange VSSWindows 2003 Server 2007 4 supported by Microsoft Integration Module VersionVSS Instant Restore software and operating systemrequirementsVSS Restore into the Recovery Storage Group software andoperating system requirements26 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialVSS Backup of CCR and LCR copies software and operatingsystem requirementsTable 8. Minimum software and operating system requirements for VSS Backup of CCR andLCR copiesOperating SystemMicrosoftWindows 2003(x64) 3ExchangeServerExchangeServer 2007 4VSS Provider Tivoli Storage Manager forCopy ServicesAny VSS provider that issupported by Microsoftrules for VSS providers.Microsoft Exchange VSSIntegration Module Version5.5.0 51 Windows Server 2003 (32-bit): Standard, Enterprise, or DataCenter Edition.All versions must be at Service Pack 1 (or later). Windows Server 2003 R2:Standard, Enterprise, or DataCenter Edition. Microsoft Virtual Server 2005R2 is also supported.2 Exchange Server 2003 Standard or Enterprise Edition. All versions must beat Service Pack 2 (or later). MSCS or VCS support is available.3 Windows Server 2003: Standard, Enterprise, or DataCenter x64 Edition.Windows Server 2003 R2: Standard, Enterprise, or DataCenter x64 Edition.Microsoft Virtual Server 2005 R2 is also supported.4 Exchange Server 2007 Standard or Enterprise Edition.5 The Microsoft Exchange VSS Integration Module is dependent upon thebase Data Protection for Exchange product and must be installed toperform any VSS operations.6 The VSS hardware provider must be installed on both machines that areinvolved in an Off-loaded backup.7 IBM Subsystem Device Driver (SDD) 1.6.0.2 with Host Attachment Scripts1.1.0.3. or (later) is required.8 The Hardware Devices Snapshot Integration Module is dependent uponthe base Tivoli Storage Manager backup-archive client product and mustbe installed to perform VSS Instant Restore operations.HardwarerequirementsLegacy or VSS Backup and Restore hardware requirements 1Table 9. Minimum hardware requirements for Legacy or VSS Backup and RestoreoperationsArchitecture Hardware DiskSpace32-bit One Intel Pentium or equivalent 166 (or later)processor.x64 One of the following:v A processor that supports Intel ExtendedMemory 64 Technologyv A processor that supports AMD64technologyRAM20 MB 48 MB (96 MBor greaterrecommended)20 MB 48 MB (96 MBor greaterrecommended)Chapter 2. Installing Data Protection for Exchange 27

IBM ConfidentialVSS off-loaded backup hardware requirements 1Table 10. Minimum hardware requirements for VSS off-loaded backup operationsArchitecture Hardware Disk Space RAM32-bit or x64 A storage subsystem with a VSS hardwareprovider. 2See Provider Seedocumentation ProviderdocumentationVSS Instant Restore hardware requirements 1Table 11. Minimum hardware requirements for VSS Instant Restore operationsArchitecture Hardware Disk Space RAM32-bit or x64 One of the following:v IBM System Storage DS6000 disk storagesubsystem 3v IBM System Storage DS8000 disk storagesubsystem 3v IBM System Storage SAN VolumeController Version 2.1.x (or later) 3See disk See diskstorage storagesubsystem subsystemdocumentation documentation1 Data Protection for Exchange VSS operations are available on anyhardware that supports Microsoft VSS requirements. Refer to your VSSprovider documentation for required levels. The following list identifiessome hardware storage subsystems that were tested with Data Protectionfor Exchange VSS operations:v IBM System Storage DS6000 and a machine with a processor supportedby DS6000 with IBM Common Interface Model (CIM) Agent for DSOpen API.v IBM System Storage DS8000 and a machine with a processor supportedby DS8000 with IBM Common Interface Model (CIM) Agent for DSOpen API.v IBM System Storage N3700 with Network Appliance (NetApp)SnapDrive Version 3.2 (or later). Make sure to see important NetApprequirement and configuration information in “VSS limitations forNetApp FAS series or IBM N-series” on page 34.v NetApp fabric-attached storage (FAS) system with NetApp SnapDriveVersion 3.2 (or later).v IBM System Storage SAN Volume Controller Version 2.1.x (or later) orVersion 3.1.x.Contact your hardware storage subsystem vendor for exact details of theirsupport of VSS operations.2 You must have a hardware storage subsystem that supports transportableshadow copies and delivers a VSS hardware provider for the hardwarestorage subsystem that adheres to Microsoft VSS Provider API standards.3 On 32-bit architecture, IBM System Storage DS6000, DS8000, and SANVolume Controller storage subsystems require that IBM System StorageVSS Hardware Provider Version 2.5.0.1027 (or later) also be running on thesame machine as Data Protection for Exchange. On x64 architecture,Version 3.1 (or later) must be running.28 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialFor detailed information regarding current hardware product compatibilityrequirements, see the IBM System Storage Web site: http://www.ibm.com/servers/storageInstallationprocedureAttention: See the README file on the Tivoli Information Center for the latestinformation regarding Data Protection for Exchange:http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jspThese instructions step you through the installation of Data Protection forExchange. Make sure to read the Installation Considerations section for importantinstallation information.Data Protection for Exchange is available in the following packages:Paid in FullThis package contains a license component and is a complete stand-alonerelease of the product.Program Temporary Fix (PTF)This package does not contain a license component. It is created to installover a previously installed version of Data Protection for Exchange.Installation considerations:v The default installation directory is Program Files\Tivoli\TSM\TDPExchange. If aTivoli Storage Manager product exists, the path to that product becomes theData Protection for Exchange default installation directory. You can override thedefault installation directory and specify a different installation directory.However, installing all Tivoli Storage Manager products and components intothe same base directory is highly recommended. The base directory is ProgramFiles\Tivoli\TSM. Note that you cannot override subdirectory names.v If you are storing backup objects created by Data Protection for ExchangeVersion 1, you must retain Data Protection for Exchange Version 1 for as long asyou retain those backup objects.v To uninstall Data Protection for Exchange (Version 1, Version 2, Version 5.1.5, orVersion 5.2.1), open the Control Panel on your Windows workstation and selectthe Add/Remove Programs item.Follow these steps to install Data Protection for Exchange:1. Insert the Data Protection for Exchange CD into the CD drive.Note:v Data Protection for Exchange must be installed from an account that is amember of the local Administrators group for the machine on which theExchange server is running.If autostart is not enabled, perform the following steps:a. Select Run from the Start menu.b. Enter X:\TDPExchange\win32\client\setup where X is your CD driveletter.c. Click OK to start the installation program.2. Select a language for the installation (see “Language Packs” on page 30 formore information).Chapter 2. Installing Data Protection for Exchange 29

IBM Confidential3. Follow the installation instructions contained in the prompt windows.4. Click Finish to complete the installation of the Data Protection for Exchangebase product.5. (VSS only): If you plan to perform basic VSS operations, you must also installthe Tivoli Storage Manager for Copy Services Microsoft Exchange VSSIntegration Module. This module is located in the X:\TDPExchange\win32\plugin\setup directory on the Tivoli Storage Manager for Copy Services CDwhere X is your CD drive letter. Double-click the ″setup″ file to launch theinstallation. This module installs in the Program Files\Tivoli\TSM\TDPExchangedirectory.6. (VSS only): If you plan to perform VSS Instant Restores, you must also installthe Tivoli Storage Manager for Copy Services Hardware Devices SnapshotIntegration Module (in addition to the Tivoli Storage Manager for CopyServices Microsoft Exchange VSS Integration Module). This module is locatedin the X:\tsmcli\win32\plugin directory on the Tivoli Storage Manager forCopy Services CD where X is your CD drive letter. Double-click the ″setup″ fileto launch the installation. This module installs in the ProgramFiles\Tivoli\TSM\baclient\plugins directory.If you are installing Data Protection for Exchange in a Microsoft Cluster Serverenvironment, repeat the installation procedure on the secondary node of yourcluster.After successfully installing Data Protection for Exchange, see Chapter 3,“Configuring Data Protection for Exchange,” on page 31 for importantconfiguration information.LanguagePacksTo view the Data Protection for Exchange GUI, command line output, andmessages in a language other than English, install the desired Language Packprovided on the product CD. The Language Pack executable files are located in theTDPExchange\x32\languages\xxx directory on the product CD. The xxx directoryrepresents the three-letter country code associated with that language. Double-clickthe ″setup″ file to launch the installation. After installing the Language Pack,activate the language by updating the Data Protection for Exchange configurationfile (tdpexc.cfg by default) using either of these methods:v Use the set command with the language parameter to specify the desiredlanguage. For example:tdpexcc set lang=fraSee the description of the language parameter on page 107 for a list of availablelanguages and their three-letter country codes.v Use the Configuration Editor in the Data Protection for Exchange GUI byselecting Edit–>Configuration–>Regional–>Language. The GUI ConfigurationEditor will show the installed languages in their long form. For example:English (United States)30 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialChapter 3. Configuring Data Protection for ExchangeThis chapter is divided into two major sections:v “Part I: Configuration overview” on page 32This section provides detailed information about setting Data Protection forExchange and Tivoli Storage Manager options, policies, and preferences. For bestresults, it is recommended that you read this information carefully beforeperforming any configuration tasks.v “Part II: Configuration procedure” on page 44This section provides detailed step-by-step instructions on how to configureData Protection for Exchange for both Legacy and VSS Backups.v “Part III: Verify your configuration” on page 47This section provides instructions on how to verify that Data Protection forExchange is installed and configured properly, including those componentsrequired for VSS Backups. Data Protection for Exchange should be ready forbackup and restore processing upon successful completion of this verificationprocedure.What applications must I configure? This table identifies the software applicationsthat must be configured to perform certain features.Table 12. List of applications to configureTo use these features: You must configure these applications:v Legacy backupv Legacy restorev VSS Backupv VSS Restorev VSS Backupv VSS Restorev Off-loaded backupv Data Protection for Exchangev Tivoli Storage Manager serverv Tivoli Storage Manager backup-archiveclient schedulerv Data Protection for Exchangev Tivoli Storage Manager serverv Tivoli Storage Manager backup-archiveclient schedulerv Tivoli Storage Manager backup-archiveclient local Client Acceptor Daemon (CAD)(Local DSMAGENT Node)v VSS software provider and/or VSShardware providerv Data Protection for Exchangev Tivoli Storage Manager serverv Tivoli Storage Manager backup-archiveclient schedulerv Tivoli Storage Manager backup-archiveclient local CAD (Local DSMAGENT Node)v Tivoli Storage Manager backup-archiveclient remote CAD (Remote DSMAGENTNode)v VSS software provider and/or VSShardware provider31

IBM ConfidentialTable 12. List of applications to configure (continued)To use these features: You must configure these applications:v VSS Backupv VSS Restorev VSS Instant Restorev Off-loaded backupv Data Protection for Exchangev Tivoli Storage Manager serverv Tivoli Storage Manager backup-archiveclient schedulerv Tivoli Storage Manager backup-archiveclient local CAD (Local DSMAGENT Node)v Tivoli Storage Manager backup-archiveclient remote CAD (Remote DSMAGENTNode)v VSS software provider and/or VSShardware providerPart I: Configuration overviewThis section provides guidelines about available options, recommended settings,and other useful information needed to configure Data Protection for Exchange. Itis recommended that you review this information before performing theconfiguration tasks described in “Part II: Configuration procedure” on page 44. Foran overview of the various VSS components, see “VSS Service” on page 5.Back up to Tivoli Storage Manager storage versus back up tolocal shadow volumesWhen creating policy for your backups, consider these differences between backingup data to Tivoli Storage Manager storage versus VSS disks.Tivoli Storage Manager storageBackups to Tivoli Storage Manager server storage are usually dictated by time, notversions.A Tivoli Storage Manager backup operation stores the backed up data on TivoliStorage Manager server storage. Although this type of backup typically takeslonger to process than a backup to local shadow volumes, a Tivoli StorageManager backup is necessary when long term storage is needed such as savingExchange data on tape for archival purposes. Tivoli Storage Manager backups arealso necessary for disaster recovery situations when the disks that are used forlocal backups are unavailable. By maintaining multiple backup copies on TivoliStorage Manager server storage, a point in time copy is available should backupson the local shadow volumes become corrupt or deleted.Local shadow volumesBackups to local shadow volumes are usually dictated by versions because of spacelimitations and provisioning of VSS storage.Sufficient local storage space must be available on local shadow volumes for a VSSbackup strategy to be successful. Make sure there is enough available storage spaceassigned to the volumes to accommodate your Data Protection for Exchangebackup operations. Environment and storage resources also impact how manybackup versions are maintained on local shadow volumes (for VSS Fast Restoreand VSS Instant Restore) and how many backup versions are maintained on Tivoli32 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialStorage Manager server (VSS Restore and longer term storage). It is recommendedthat different sets of policies be created for backups to both local shadow volumesand to Tivoli Storage Manager server storage. If you are using a VSS providerother than the Windows VSS System Provider, make sure to review thedocumentation for that specific VSS provider.VSS operations in DS and SAN Volume Controller environmentsIn order to determine how much storage space is required for each local backup,be aware that the backup LUNs require the same amount of storage space as theoriginal LUNs. For example, if you have a 100GB database residing on a 200GBLUN, you will need a 200GB LUN for each backup version.VSS limitations for SAN Volume Controller: When performing a Data Protectionfor Exchange VSS backup (non-offloaded) with backup destination as TivoliStorage Manager Server, and the Exchange Server data resides on SAN VolumeController (SVC) disks, and the IBM TotalStorage VSS Hardware Provider is beingused, in some isolated cases the SVC LUNs remain mapped to the Windows hosteven though the VSS backup is complete. To work around this issue, you can use abackup destination other than TSM (BOTH or LOCAL). You can also manuallyunmap the volumes attached to the Windows host to work around this issue.When performing two Data Protection for Exchange VSS backups, back to back,and the Exchange Server data resides on SAN Volume Controller (SVC) disks, ifthe volumes are large and/or the SVC background copy rate is set a low number,it may appear that the second VSS backup is hanging. In fact, it is waiting for theSVC background copy of the first backup to complete before proceeding with thesecond backup. SVC will not allow two background copies of the same volume tooccur at the same time. There is no indication that the second backup is waitingfor the first SVC background copy to complete. You may also see timeouts errors ifthe previous SVC background copy takes too long. To work around this issue,schedule your VSS backups far enough apart to accommodate this situation. Youcan also try increasing the copyrate of the SVC background copy.VSS operations in IBM N-series and NetApp environmentsBe aware that in environments that contain IBM N-series and NetApp systems,snapshots created using the IBM N-series and NetApp snapshot provider arestored on the same volume where the LUN resides. Disk space consumed by alocal backup consists only of the blocks that have changed since the last localbackup was created. The following formula can be used to help determine howmuch space is required for each local backup:Amount of data changed per hour * number of hours before a local backup expiresIn addition, Write Anywhere File Layout (WAFL) reserves blocks equal to twotimes the specified size of the LUN to be used. This space reservation ensureswrites for virtual disks. The following example demonstrates how to calculate thesize of these volumes:Database size of an Exchange storage group: 100GBNumber of local backups to be kept: 3Snapshot for TSM backup: 1duration for TSM backup: 2hrBackup frequency: 3hrsThe duration before a local backup is expired: 9 hrsAmount of data changed/added/deleted per hr: 50MBSpace required for each local backup: 50*9= 450 MBSpace required for 3 local backups + 1 TSM backup: 450*3 + 50*2 = 1450 MBThe volume size required for the storage group: 100*2 (space reservation) + 1.5 = 201.5 GBChapter 3. Configuring Data Protection for Exchange 33

IBM ConfidentialVSS limitations for NetApp FAS series or IBM N-series: Due to the limitationsin SnapDrive 4.0 and any supported prior versions, the VSS Provider for NetAppFAS series and IBM N-series, VSS based operations using Data Protection forExchangeData Protection for Exchange with backup destination set to LOCAL,must be performed in specific ways. Failure to comply with the followingconfiguration and operational recommendations can lead to serious conditionssuch as premature deletion of snapshots representing VSS backups to LOCAL,backup failure, and out of space conditions on the production volumes. When thelimitations in the SnapDrive are addressed by NetApp, Data Protection forMicrosoft Exchange VSS operations can be fully utilized.Exchange Server storage configuration for NetApp FAS series or IBM N-seriesVSS operationsIf you plan to perform VSS backups with backup destination set to LOCAL, pleasecheck your setup to ensure that following requirements are met.v The NAS filers LUNs used by a storage group must be fully dedicated to thestorage group. The Microsoft Exchange Server storage groups can not shareLUNs.v A NAS filer LUN used by the Exchange storage groups must be the only LUNon the filer volume. For example, if Exchange uses four LUNs, there must befour corresponding filer volumes, each volume containing one LUN.Guidelines for VSS Backup operations for NetApp FAS series or IBM N-seriesIf you plan to perform VSS backups with backup destination set to LOCAL, thesebackups must adhere to the following guidelines.v VSS backups with backup destination set to Local must be bound to amanagement class that has verExists=1.v VSS backups with backup destination set to Local can either be of type full orcopy. You can not mix local backups of type full and copy.v VSS backups with backup destination set to TSM can be full or copy. There areno restrictions on Tivoli Storage Manager backups.v When performing VSS backups, you must ensure that previous backup hasfinished completely before starting a new backup. Any overlap of backups canresult in undesirable side-effects on the Microsoft Exchange Server, the VSSservice, and, the NAS filer.Sample VSS Backup procedure for NetApp FAS series or IBM N-seriesTaking above considerations into account, the following section describes a samplebackup procedure that could be used to perform VSS backups utilizing both TivoliStorage Manager and LOCAL backup destinations in an optimal manner. Note thatthe following assumptions apply to this sample backup procedure:v The configuration requirements stated above are met.v The VSS backup to Tivoli Storage Manager takes one hour to complete.v The VSS backup to LOCAL takes five minutes to complete.Your backup procedure could consist of the following backups:v Daily VSS full backups to LOCAL every four hours - 12am, 4am, 8am, 12pm,4pm, 8pmv Daily VSS full backups to Tivoli Storage Manager storage by one of thefollowing two methods:34 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential– Specify backupdestination set to BOTH at 12am. Note that this will create a12am backup to local. Therefore, no separate 12am backup to local isrequired.– Full offloaded-backup at 1am. Note that no VSS local backup will be availableto restore from between 1am and 4am when next VSS backup to local willtake place.v Perform weekly VSS-copy backups to Tivoli Storage Manager (offloaded backup)5amv Perform weekly legacy full backups (or as needed).Recommended Tivoli Storage Manager policy settingsMake sure the following policy items are defined with the recommended settings.Consult your Tivoli Storage Manager administrator or see the IBM Tivoli StorageManager for Windows Administrator’s Guide and the IBM Tivoli Storage Manager forWindows Administrator’s Reference for complete information on defining or updatingthese Tivoli Storage Manager policy items.DomainCreate a policy domain on the Tivoli Storage Manager server to be usedexclusively for Data Protection for Exchange backups.Policy SetPolicy sets contain management classes (which contain copy groups) thatdetermine the rules by which Data Protection for Exchange backups are performedand managed. Define the policy set to the policy domain to which Data Protectionfor Exchange backups belong. Note that the policy set must be activated and onlyone policy set can be active in the policy domain.Management ClassDefine a management class for backups residing on local shadow volumes and amanagement class for backups residing on Tivoli Storage Manager server storage.Different management classes provide the opportunity for specialized policies foreach storage destination. For example, you can maintain six versions of local VSSBackups of a given storage group (VERExists=6) while maintaining only twoversions of the same storage group on Tivoli Storage Manager server storage(VERExists=2). In addition, you can create a separate management class for copybackup types for use in long term storage. Such policies can maximize storageresources and provide more control over your storage strategy.Be aware that since Legacy backups on Tivoli Storage Manager server storage, VSSBackups on Tivoli Storage Manager server storage (COPY and FULL), and VSSBackups on local shadow volumes (COPY and FULL) all have different TivoliStorage Manager server naming and therefore, can each have their ownmanagement class, it is possible to have five active backups of the same storagegroup. Make sure your backup strategy is planned and well-defined beforedefining management classes.Copy GroupDefine the copy group as a backup copy group and not an archive copy group.Since Data Protection for Exchange stores all objects as backup objects on TivoliStorage Manager in backup storage pools, an archive copy group is not required,although an archive copy group can exist. The following backup copy groupparameters significantly influence your backup policy:Chapter 3. Configuring Data Protection for Exchange 35

IBM ConfidentialVERExistsDetermines the maximum number of Exchange Server database backupversions to retain for databases that exist on the Data Protection forExchange client system.VERDeletedDetermines the maximum number of Exchange Server database backupversions to retain for databases that have been deleted from the DataProtection for Exchange client system after being backed up by TivoliStorage Manager.RETExtraDetermines the number of days to retain an Exchange Server databasebackup version after that version becomes inactive.RETOnlyDetermines the number of days to retain the last Exchange Server databasebackup version of a database that has been deleted from the DataProtection for Exchange client system. Be aware that incremental backupsdo not participate in expirations (due to version limit) because there isnever more than one version of an incremental backup object. This isbecause incremental backups are always uniquely named. However, allLegacy backup objects for an Exchange Server storage group areinactivated when a new full backup of that Exchange Server storage groupis performed (VSS backup objects remain active). Therefore, the retentionperiod set in the RETOnly parameter controls the expiration of incrementalbackup objects.When setting the value of the RETOnly parameter for incrementalbackups, the value must be (at a minimum) as long as the value set for thefull backup objects to which the incremental backups are associated. Youcan use the same management class for incremental backups and the fullbackup objects (that are retained the longest) to be sure an adequate valueis used. However, all Legacy backup objects for an Exchange Serverstorage group are inactivated when a new Legacy full backup of thatExchange Server storage group is performed (VSS backup objects remainactive).MODE, SERialization, FREQuencyYou can accept default values for these backup copy group parameters asthey are not applicable to Data Protection for Exchange.It is recommended that you discuss these parameters with your Tivoli StorageManager server administrator in order to accomplish your backup strategy.Storage PoolA single restore can require a full backup, a differential backup, and multipleincremental backups. It is recommended to use collocation if these backups arestored on removable media. Use collocation by file space (define stgpoolCOLlocate=FILespace) if you plan to restore multiple storage groups in parallel.This is recommended because all data for any one storage group is stored withinone Tivoli Storage Manager server file space.Data Protection for Exchange node name: RecommendedsettingsThe machine where Data Protection for Exchange is installed must be registered tothe Tivoli Storage Manager server with a node name. This node name owns andmanages all Data Protection for Exchange data that is backed up to the Tivoli36 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialStorage Manager server. Specify this node name with the nodename option in thedsm.opt options file located (by default) in the Data Protection for Exchangeinstallation directory. Note that in order to perform VSS operations, you may needto register node names for additional machines. See “Proxy node definitions (VSSBackups)” for details about this task.Be aware of the following Tivoli Storage Manager parameter conditions whenregistering your Data Protection for Exchange node name (machine) to the TivoliStorage Manager server:v MAXNUMMP This parameter determines the maximum number of mountpoints a client node is allowed to use on the Tivoli Storage Manager serverduring a backup operation.v TXNGroupmax This parameter determines the number of files transferred as agroup between the client and server between transaction commit points. Thisparameter MUST have a value of 12 or greater.v COMPression This parameter determines whether the Data Protection forExchange node compresses data before sending it to the Tivoli Storage Managerserver during a backup operation. Specify COMPression=Client to allow theData Protection for Exchange node to make the decision whether to compressdata via the value of the client COMPRESSIon option specified in the optionsfile (dsm.opt) located in the Data Protection for Exchange directory.Note: If you are running Data Protection for Exchange on a Microsoft ClusterServer, it is recommended that the node name match the Exchange virtual servername.See the IBM Tivoli Storage Manager for Windows Administrator’s Reference forcomplete information regarding these parameters.Proxy node definitions (VSS Backups)Since Data Protection for Exchange VSS Backup operations are implementedthrough the Tivoli Storage Manager backup-archive client, you must use nodenames specifically for VSS operations in addition to using a node name for whereData Protection for Exchange is installed. As part of the configuration procedure, aproxy relationship is defined for these various node names. This proxy relationshipallows node names to perform operations on behalf of another node name. Whenregistering these nodes to the Tivoli Storage Manager server for VSS operations, donot specify the Tivoli Storage Manager USerid=NONE parameter. VSS operationswill fail when this parameter is specified.There are two types of node names defined in proxy node relationships:v Target node: A node name that controls backup and restore operations and thatalso owns the data on the Tivoli Storage Manager server.v Agent node: A node name that performs operations on behalf of a target node.Required node names for basic VSS operationsTo perform basic VSS operations, you must have one target node and one agentnode:Table 13. Required node names for basic VSS operationsProxy node type Nodename Where to specifyTarget node Data Protection for Exchangenode nameUse the nodename option in theData Protection for Exchangeoptions file (dsm.opt)Chapter 3. Configuring Data Protection for Exchange 37

IBM ConfidentialTable 13. Required node names for basic VSS operations (continued)Proxy node type Nodename Where to specifyAgent node Local DSMAGENT Node Use the localdsmagentnodeparameter in the Data Protection forExchange configuration file(tdpexc.cfg)TargetAgentnodeThis is the node name where Data Protection for Exchange is installed.This node name (specified with the nodename option in the dsm.opt file) isreferred to as the Data Protection for Exchange node name.nodeThis is the node name where the backup-archive client and VSS providerare installed. This node is responsible for performing the VSS operations asData Protection for Exchange itself does not perform any direct VSSoperations. This node name is referred to as the Local DSMAGENT Nodeand is specified with the localdsmagentnode parameter in the DataProtection for Exchange configuration file (tdpexc.cfg by default). You canuse the Configuration task in the Edit Menu of the GUI or the tdpexcc setcommand to specify this parameter.Note: The agent node and target node will be on the same machine for basic VSSoperations.Required node names for VSS off-loaded backupsTo perform VSS off-loaded backups, you must have one target node and two agentnodes:Table 14. Required node names for VSS off-loaded backupsProxy node type Nodename Where to specifyTarget node Data Protection for Exchangenode nameUse the nodename option in theData Protection for Exchangeoptions file (dsm.opt)Agent node Local DSMAGENT Node Use the localdsmagentnodeparameter in the Data Protection forExchange configuration file(tdpexc.cfg)Agent node Remote DSMAGENT Node Use the remotedsmagentnodeparameter in the Data Protection forExchange configuration file(tdpexc.cfg)TargetAgentnodeThis is the node name where Data Protection for Exchange is installed.This node name (specified with the nodename option in the dsm.opt file) isreferred to as the Data Protection for Exchange node name.nodeThis is the node name where the backup-archive client and VSS providerare installed. This node is responsible for performing the VSS operations asData Protection for Exchange itself does not perform any direct VSSoperations. This node name is referred to as the Local DSMAGENT Nodeand is specified with the localdsmagentnode parameter in the Data38 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialAgentProtection for Exchange configuration file (tdpexc.cfg by default). You canuse the Configuration task in the Edit Menu of the GUI or the tdpexcc setcommand to specify this parameter.nodeThe node name of a separate machine that must also have thebackup-archive client, VSS provider, and the Exchange SystemManagement Tools installed (make sure you install the same level of theExchange System Management Tools that is installed on your Exchangeproduction server). This machine is responsible for performing themovement of VSS snapshot data from local shadow volumes to the TivoliStorage Manager server. It is also responsible for performing the ExchangeIntegrity Check. This node name is referred to as the Remote DSMAGENTNode and is specified with the remotedsmagentnode parameter in the DataProtection for Exchange configuration file (tdpexc.cfg by default). You canuse the Configuration task in the Edit Menu of the GUI or the tdpexcc setcommand to specify this parameter. The choice of available machinesdepends on whether the machines have access to the local shadowvolumes that contain the VSS snapshot backups. This node name is onlyvalid for VSS environments that support transportable shadow copies. It isnot supported if you are using the default VSS system provider. Refer toyour VSS provider documentation for details.Make sure that the localdsmagentnode and remotedsmagentnode are registered tothe same Tivoli Storage Manager server that is specified in the Data Protection forExchange options file (dsm.opt) and the backup-archive client options file (alsodsm.opt).Specifying Data Protection for Exchange optionsOnce Data Protection for Exchange is registered to Tivoli Storage Manager, severalData Protection for Exchange parameters need to be configured. The Tivoli StorageManager administrator should have provided you with the node name, password,and the communications method with the appropriate parameters to connect to theTivoli Storage Manager server. These values, together with other parameters, arestored in an options file located (by default) in the Data Protection for Exchangeinstallation directory. The default options file name is dsm.opt. To modify theinitial dsm.opt file, open dsm.opt using a text editor.Attention: Make sure that the Data Protection for Exchange options file (dsm.opt)and the backup-archive client options file (also dsm.opt) specify the same TivoliStorage Manager server.The options file includes the following parameters, which are required for initialconfiguration:NODenameThe Tivoli Storage Manager node name is the unique name by which TivoliStorage Manager recognizes the machine running Data Protection forExchange.COMMMethodThis option specifies the communication protocol to use between the DataProtection for Exchange node with the Tivoli Storage Manager server. DataProtection for Exchange supports the same set of communication protocolssupported by other Tivoli Storage Manager clients on Win 32 platforms.Chapter 3. Configuring Data Protection for Exchange 39

IBM ConfidentialDepending on the chosen commmethod, the connectivity parameters forthat commmethod need to be specified as well.The following additional options are not required for initial configuration. Bydefault they are not specified, but you can modify the default settings:PASSWORDAccessThis option instructs the Tivoli Storage Manager API to store the currentpassword (encrypted) in the Windows registry and automatically generatesa new one when the current one expires. This method of passwordmanagement is recommended when running scheduled, unattendedbackups since it ensures that the backup never fails because of an expiredpassword. The default is prompt.A utility program named dsmcutil.exe allows you to manage (update ordisplay) the password as stored in the registry. This utility program isdistributed with the Tivoli Storage Manager backup-archive client package.For more information on using the dsmcutil program, see the dsmcutil.hlpfile or the dsmcutil.txt file which are distributed with the Tivoli StorageManager backup-archive client package.CLUSTERnodeThis option directs the Tivoli Storage Manager API and Data Protection forExchange to be cluster-aware when running in a MSCS or VCSenvironment. This option must be specified for Data Protection forExchange to function properly on a MSCS or VCS.ENABLELANFreeThis option allows Data Protection for Exchange to run in a LAN-freeenvironment (if you are equipped to do so). To perform a LAN-free backupwith Data Protection for Exchange, a Tivoli Storage Manager Storage Agentmust be installed on the same machine and enablelanfree yes must bespecified in the options file. See Managed System for SAN Storage AgentUser’s Guide for detailed information about LAN-free environments.ENABLECLIENTENCRYPTKEYThis option encrypts Exchange databases during backup and restoreprocessing. One random encryption key is generated per session and isstored on the Tivoli Storage Manager server with the object in the serverdatabase. Although Tivoli Storage Manager manages the key, a validdatabase must be available in order to restore an encrypted object. Specifyenableclientencryptkey yes in the options file. In addition, assign the typeof encryption to use by specifying the encryptiontype option in this sameoptions file. You can specify DES56 (56-bit) or AES128 (128bit). The defaultis AES128. In this same file, you must also specify the databases you wantencrypted by adding an include statement with the include.encrypt option.Transparent encryption is only available on Tivoli Storage Manager serverand API Version 5.3.0 (or later). Note that files that are backed up usingencryption CANNOT be restored by an older API.v For Legacy backups, specify these encryption options in the DataProtection for Exchange options file.v For VSS Backups, specify these encryption options in the backup-archiveclient options file. It is recommended that you refer to the encryptioninformation available in the client documentation before attempting toencrypt your storage groups.Perform the following tasks to encrypt your Exchange database Legacybackups:40 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential1. Verify that you are running version 5.3.0 (or later) of the Tivoli StorageManager server and Tivoli Storage Manager API.2. Edit the options file for Data Protection for Exchange and add thefollowing three options:a. Add the enableclientencryptkey yes option.b. Add the encryptiontype option with the type of encryption to use.c. Add your include statements with the include.encrypt option. Forexample, to encrypt all Exchange data, specify the following:include.encrypt *\...\*To encrypt all the data in Storage Group 1, specify the following:include.encrypt "SERVER_NAME\Storage Group 1\...\*"COMPRESSIonThis option instructs the Tivoli Storage Manager API to compress databefore sending it to the Tivoli Storage Manager server; this reduces trafficand storage requirements. If you enable compression, it affectsperformance in two ways:v CPU utilization is higher on the machine on which Data Protection forExchange is running.v Network bandwidth utilization is lower because fewer bytes are sent.v Storage usage on the Tivoli Storage Manager server is reduced.You may want to specify compression yes if any of the following conditionsexist:v The network adapter has a data overload.v Communications between the Data Protection for Exchange and TivoliStorage Manager server are over a low bandwidth connection.v There is heavy network traffic.v You can also use the compressalways yes option (with the compressionyes setting) to specify that file compression continues even if the filegrows as a result of compression.It may be better to specify compression no in the following cases:v The computer running Data Protection for Exchange has a CPUoverload; the added CPU usage can impact other applications includingthe Exchange Server. You can monitor CPU and network resourceutilization using the Performance Monitor program shipped withWindows.v You are not constrained by network bandwidth; in this case, you canachieve the best performance by leaving compression NO and enablinghardware compaction on the tape drive, which also reduces storagerequirements.The Tivoli Storage Manager administrator can override the compressionoption setting for the Data Protection for Exchange node when registeringor updating the node by specifying, on the Tivoli Storage Manager serverside, that a particular node:v Always uses compression.v Never uses compression.v Leaves the decision up to the client (default value).Considerations:Chapter 3. Configuring Data Protection for Exchange 41

IBM Confidentialv For Legacy backups, specify the compression option in the DataProtection for Exchange options file.v For VSS Backups, specify the compression option in the backup-archiveclient options file. It is recommended that you refer to compressioninformation available in the client documentation before attempting tocompress your data.INCLUDE and EXCLUDENote: Only use include and exclude statements to set policy for Legacybackups. Use the VSSPOLICY statement in the Data Protection forExchange configuration file to set policy for VSS backups. See “SpecifyingData Protection for Exchange preferences” on page 43 for moreinformation.A Data Protection for Exchange Legacy backup object name is composed ofa series of qualifiers, each either an Exchange name or a Data Protectionfor Exchange constant, where the qualifiers are separated by a backslash(\). The general include and exclude syntax is:include "objectNameSpecification" [ManagementClassName]exclude "objectNameSpecification"where objectNameSpecification is:ExchangeServerName\ExchangeStorageGroupName\...\backupTypewhere backupType is one of the following:full, copy, incr, diff, dbcopyNote: Important! The Tivoli Storage Manager API does not allow sendingany of the three data types (meta, data, logs) that comprise an Exchangedatabase backup to different storage destinations on the Tivoli StorageManager server.This example excludes Storage Group 1 from a backup:EXCLUDE "SERVER1\Storage Group 1\...\*"This example binds all objects for storage group SG2 to management classCLASS1:INCLUDE "SERVER1\SG2\...\*" CLASS1This example binds all Directory backups to management class CLASS2:INCLUDE "SERVER2\Directory\...\*" CLASS2This example binds all incremental objects to management class CLASS3:INCLUDE "SERVER3\...\incr" CLASS3Consider the following behavior when setting include and excludestatements:v The wildcard character (*) matches zero or more characters.v The wildcard character (?) matches any one character.v The wildcard character (*) within a qualifier replaces zero or morecharacters only within that qualifier. The qualifier itself must exist in thematching object name. To match zero or more qualifiers, use ellipses(\...\).42 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialNote the following characteristics of Data Protection for Exchange configurationparameters:v The value of a configuration parameter specified on a command line invocationoverrides (but does not change) the value of the configuration parameterspecified in the Data Protection for Exchange configuration file.v During a command line invocation that does not specify an overriding value fora configuration file parameter, the values in the default Data Protection forExchange configuration file (tdpexc.cfg) are used.See “Set command” on page 106 for descriptions of available configurationparameters.Set policy for VSS backups by specifying the VSSPOLICY statement in your DataProtection for Exchange configuration file. Note that you must specify thisstatement manually. You cannot specify it using the tdpexcc set command or theConfiguration task in the Edit Menu of the Data Protection for Exchange GUI.VSSPOLICY statements are processed from the bottom up and processing stops atthe first match. To ensure that more specific specifications are processed at all, themore general specification should be listed before the more specific ones, so as tobe processed after the more specific specifications. Otherwise, the more generalspecification will match the target before the more specific specifications are seen.Specify the following information in the VSSPOLICY statement:VSSPOLICY "" The statement contains the following values:v Name of the Exchange Server or wildcard character: *v "" Name of storage group or wildcard character: *v Backup type: FULL or COPY or wildcard character: *v Backup destination: TSM or LOCAL or wildcard character: *v Management Class name. This sets the management class for thespecified class of backup.Here are examples of the VSSPOLICY statement:VSSPOLICY * * FULL TSM MC1VSSPOLICY * * FULL LOCAL MC2VSSPOLICY * * COPY TSM MC3VSSPOLICY * * COPY LOCAL MC4VSSPOLICY * "Payroll" * TSM MC5VSSPOLICY * "First Storage Group" * LOCAL MC6VSSPOLICY SERVER1 * * TSM MC7VSSPOLICY SERVER1 * * LOCAL MC8Part II: Configuration procedureThis section provides step-by-step instructions on how to configure the requiredapplications to perform Data Protection for Exchange backup and restoreoperations. Configuration tasks are presented in sequential order based on thelocation of where the tasks must be performed:1. On the Tivoli Storage Manager server2. On the machine running the Exchange Server3. On the machine running the off-loaded backups (VSS only)44 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialAttention:If you plan to perform VSS operations in a MSCS or VCS environment, make sureto specify the following options in each of the dsm.opt files that are used for theLOCALDSMAGENT, REMOTEDSMAGENT, and OFFLOAD machines:CLUSTERNODE NOCLUSTERDISKSONLY NO1. On the Tivoli Storage Manager server:Perform these steps on the Tivoli Storage Manager server:1. Define the policy domains, policy sets, management classes, copy groups, andstorage pools needed to meet your Data Protection for Exchange backup andrestore requirements. For VSS operations, Tivoli Storage Manager serverauthentication must be on.2. Register your Data Protection for Exchange node name and password with theTivoli Storage Manager register node command. For example: For VSSoperations, this node is the Target Node. Note that when registering nodes tothe Tivoli Storage Manager server specifically for VSS operations, do notspecify the Tivoli Storage Manager USerid=NONE parameter. VSS operationswill fail when this parameter is specified.3. If not already defined, register your Tivoli Storage Manager backup-archiveclient node name and password for the machine where the Exchange Serverinstalled. For example:For VSS operations, this agent node is the LocalDSMAGENT Node.4. (VSS only) If you plan to perform off-loaded backups, register the TivoliStorage Manager backup-archive client node name and password for themachine that will perform the VSS off-loaded backups. For example:This agentnode is the Remote DSMAGENT Node. Note that BAOFF is used in thisexample (and in Step 5) to differentiate between this Remote DSMAGENTNode and the Local DSMAGENT Node (Step 3). You can replace BAOFF withthe node name of your backup-archive client. If you do not plan to performoff-loaded backups, you can skip this step.5. (VSS only) Define the proxy node relationship (for the Target Node and agentnodes) with the Tivoli Storage Manager grant proxynode command. Forexample:grant proxynode target=DP agent=BAnodename,BAOFF2. On the machine running the Exchange Server:Perform these steps on the machine where the Exchange Server is installed andrunning:1. Specify your Data Protection for Exchange node name and communicationmethod in the dsm.opt file located (by default) in the Data Protection forExchange installation directory. Additional options are also available.2. Specify your Data Protection for Exchange preferences (such as language, dateformat, log file, etc.) in the tdpexc.cfg file located (by default) in the DataProtection for Exchange installation directory. Use the set command or theConfiguration task in the Edit Menu of the Data Protection for ExchangeGUI.3. (VSS Only): Specify your VSSPOLICY statement in your Data Protection forExchange configuration file.Chapter 3. Configuring Data Protection for Exchange 45

IBM Confidential4. (VSS Only): Configure the Tivoli Storage Manager backup-archive client (if itis not already configured). If the backup-archive client is already configured,you can use existing client services. The backup-archive client Setup Wizardcan guide you through the configuration process (if needed). In thebackup-archive client GUI menu, select Utilities->Setup Wizard->Help meconfigure the TSM Backup Archive Client. Note that the node name for thismachine is referred to as the Local DSMAGENT Node and is specified withthe localdsmagentnode parameter in the Data Protection for Exchangeconfiguration file (tdpexc.cfg by default).5. (VSS Only): Install and configure the Tivoli Storage Manager Client AcceptorDaemon (CAD) Service (if not already installed and configured). You can usean existing client CAD Service if one is already installed and configured. Thebackup-archive client Setup Wizard can guide you through the CADinstallation process (if needed). In the backup-archive client GUI menu, selectUtilities->Setup Wizard->Help me configure the TSM Web Client. Makesure this CAD service is running before proceeding to Step 6.6. (VSS Only): Install and configure the Tivoli Storage Manager Remote ClientAgent Service (DSMAGENT) if it is not already installed and configured. Thebackup-archive client Setup Wizard can guide you through the configurationprocess. In the backup-archive client GUI menu, select Utilities->SetupWizard->Help me configure the TSM Web Client. You can use the existingDSMAGENT if one is already installed and configured.7. (VSS Only): Install the Tivoli Storage Manager Copy Services Exchange VSSIntegration Module from the product (if it is not already installed).8. (VSS Only): If you plan to perform VSS Instant Restores, install the TivoliStorage Manager Copy Services Hardware Devices Snapshot IntegrationModule from the product (if it is not already installed). Note that a SANVolume Controller, DS6000, or DS8000 storage subsystem is also required toperform VSS Instant Restores.9. (VSS Only): Add the Microsoft Exchange Server binary path to the PATHstatement in the system environment variables. For example:"C:\Program files\Exchsrvr\bin"Verify that the ″ESEUTIL.EXE″ executable exists in this directory.10. (VSS Only): Install and configure a VSS provider. Consult the VSS providerdocumentation for information regarding configuration of that software. Notethat there is no installation or configuration required if you are using thedefault Windows VSS System Provider.11. (VSS Only): Define storage space to hold VSS Backups that will reside onlocal shadow volumes. Make sure you define enough space to hold all copiesof the VSS Backups as designated by your policies.See “Back up to Tivoli Storage Manager storage versus back up to localshadow volumes” on page 32 for recommendations regarding sufficient diskstorage space.3. On the machine running the Off-loaded backups (VSS only):Perform these steps on the machine running the off-loaded backups:1. Configure the Tivoli Storage Manager backup-archive client (if it is not alreadyconfigured). If the backup-archive client is already configured, you can useexisting client services. The backup-archive client Setup Wizard can guide youthrough the configuration process (if needed). In the backup-archive client GUImenu, select Utilities->Setup Wizard->Help me configure the TSM Backup46 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialArchive Client. Note that the node name for this machine is referred to as theRemote DSMAGENT Node and is specified with the remotedsmagentnodeparameter in the Data Protection for Exchange configuration file (tdpexc.cfg bydefault).2. Install and configure the Tivoli Storage Manager Client Acceptor Daemon(CAD) Service (if not already installed and configured). You can use an existingclient CAD Service if one is already installed and configured. Thebackup-archive client Setup Wizard can guide you through the CADinstallation process (if needed). In the backup-archive client GUI menu, selectUtilities->Setup Wizard->Help me configure the TSM Web Client.3. Install and configure the Tivoli Storage Manager Remote Client Agent Service(DSMAGENT). The backup-archive client Setup Wizard can guide you throughthe configuration process. In the backup-archive client GUI menu, selectUtilities->Setup Wizard->Help me configure the TSM Web Client.4. Install the Microsoft Exchange Server management tools from the MicrosoftExchange Server installation media. Take note of the Microsoft Exchange ServerManagement tools binary directory (for example: C:\Programfiles\Exchsrvr\bin). Verify that the ″ESEUTIL.EXE″ executable exists in thisdirectory. Data Protection for Exchange uses this tool to run automatic integritychecking of the VSS backup.Note:a. The Exchange Server does not need to be installed or running on thismachine. Only the Microsoft Exchange Server management tools arerequired to be installed on this machine.b. See your Microsoft Exchange Server documentation for necessary licenserequirements.5. Add the Microsoft Exchange Server binary path to the PATH statement in thesystem environment variables. For example:"C:\Program files\Exchsrvr\bin"6. Install and configure a VSS provider (if you are not using the default systemVSS provider). Consult the VSS provider documentation for informationregarding configuration of that software.Part III: Verify your configurationBefore attempting to perform a backup or restore operation, verify that DataProtection for Exchange is installed and configured correctly by running the queryexchange command on the machine where the Exchange Server is installed andrunning. For example:tdpexcc query exchangeThis command returns information and status about the Exchange Server, storagegroups, circular logging, and VSS components (when configured for VSSoperations). The following output example shows that the configuration is correctand ready for Legacy backups, VSS Backups (Local DSMAgent Node), and VSS Offloaded backups (Remote DSMAgent Node):IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 3, Level 3.0(C) Copyright IBM Corporation 1998, 2006. All rights reserved.ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully.Chapter 3. Configuring Data Protection for Exchange 47

IBM ConfidentialMicrosoft Exchange Server Information-------------------------------------Server Name: ONYDomain Name: optimus.zor.localExchange Server Version: 6.5.7638.1Storage Groups with Databases and Status----------------------------------------First Storage GroupCircular Logging - Disabledforfun store OnlineMailbox Store (ONY) OnlinePublic Folder Store (ONY) Onlinestg3Circular Logging - Disabledmail1mail2mail3stg_bigCircular Logging - Disabledmail1mail2mail3mail4testCircular Logging - Disabledtest1OnlineOnlineOnlineOnlineOnlineOnlineOnlineOnlineVolume Shadow Copy Service (VSS) Information--------------------------------------------Writer Name : Microsoft Exchange WriterLocal DSMAgent Node : svc_baRemote DSMAgent Node : svc_offloadWriter Status : OnlineSelectable Components : 4Note that the following two errors are commonly returned when performing a VSSoperation. Information is provided to help locate the cause of the error.ANS1017E (RC-50) Session rejected: TCP/IP connection failureThis is displayed when the Tivoli Storage Manager backup-archive clientCAD is either not running or is not configured properly.ANS1532E (RC5722) Proxy Rejected: Proxy authority has not been granted to thisnode. This is displayed when the Tivoli Storage Manager server has not beenconfigured for the proxy nodes correctly.48 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialChapter 4. Using the Graphical User Interface (GUI)This section provides information on how to use the Data Protection for ExchangeGUI to perform the following:v Perform a Legacy backup of Exchange storage groups and transaction logs,including Exchange Site Replication Service (SRS) databases.v Perform a VSS Backup of Exchange storage groups and transaction logs.v Perform a VSS Off-loaded backup of Exchange storage groups and transactionlogs.v Restore Exchange storage groups and transaction logs.v Restore the SRS database.v Modify the Data Protection for Exchange configuration.v Select short cuts from the Data Protection for Exchange Toolbar.Note: The term Tree View refers to the directory tree view in the left frame of abackup or restore window. The term List View refers to the scrollable list of objectsin the right frame of a backup or restore window.MenubarThe Data Protection for Exchange GUI Menu Bar consists of the following itemsand menu list functions:File Exit the program.Edit Configure Data Protection for Exchange. The default configuration settingsare contained in the tdpexc.cfg file.View Refresh the Tree View.UtilitiesChange the Tivoli Storage Manager password or display Tivoli StorageManager server information.Help Obtain Data Protection for Exchange help, view online books, TivoliStorage Manager Web access, and information about Data Protection forExchange.EditMenuConfigurationThis allows you to modify the Data Protection for Exchange configurationfile. If a configuration file is not specified, the tdpexc.cfg file is used. If noconfiguration file is found, a default file is created which contains all thedefault settings for the parameters. A different configuration file can bespecified by invoking the GUI from the command line with the /configfileparameter.Clicking this menu item displays the Data Protection for Exchange Settingsdialog with the following five tabs and their settings:v General TabTemporary Log Restore PathEnter the default temporary path to use when restoring logs and49

IBM Confidentialpatch files. For best performance, the path specified should beon a different physical device than the current active logger. Ifyou choose to not enter a path, the default is the value of theTEMP environment variable. When performing full, copy, ordatabase copy restores, all log files residing in the specified pathare erased.|||Note: Do not specify double-byte characters (DBCS) within thetemporary log path. This is not supported by Data Protection forExchange or Microsoft.Retries for Legacy Backups (default value: 4)Specify the number of times (0 to 32) that Data Protection forExchange will retry a failed Legacy backup.Wait for Tape Mounts for Backup or RestoreCheck this box when you want Data Protection for Exchange towait for tape media to be mounted for backup and restoreoperations. This setting is applicable when the Tivoli StorageManager server is configured to store the backup data on tapemedia. With backup data on removable media it is likely thatduring backup and restore operations a wait period will occurduring storage volume mounts. If a wait occurs this settingspecifies whether Data Protection for Exchange should wait forthe media mount or stop the current operation. Wait for tapemounts is the default.Use VSS Backup as the default Backup methodCheck this box to set VSS Backups as the default backupmethod. Be aware of the following considerations when usingthis parameter:– Make sure the Local DSMAGENT Node name parameter isspecified.– VSS Backups can only be restored using VSS.– You cannot mix a VSS Backup with a Legacy backup.– This parameter is unavailable if the Microsoft Exchange VSSIntegration Module is not installed.The default value is to use the Legacy backup method.v Performance Tab (Applies to legacy backups only)TDP Buffers (default value: 3)Select a number (2 to 8) that specifies the number ofcommunication data buffers Data Protection for Exchange useswhen transferring data between Data Protection for Exchangeand the Tivoli Storage Manager server. Each buffer is the sizespecified in the TDP Buffer Size parameter. Note that thisparameter applies to Legacy backups only.TDP Buffer Size (default value: 1024)Select a number (64 to 8192) that specifies the size of the buffersused by Data Protection for Exchange to transfer data to theTivoli Storage Manager server. Note that this parameter appliesto Legacy backups only.v Logging Tab50 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialLog File Name (default value: tdpexc.log)Enter the name of the file into which you want Data Protectionfor Exchange to write activity log information.Prune Old Entries (default value: selected)Check this box to enable pruning of the activity log. Specify thenumber of days (0 to 9999) to keep old entries. Data Protectionfor Exchange prunes entries greater than this number when youinitialize this application. The default value is to keep the entriesfor 60 days. Click on the Prune Now button to prune the activitylog immediately.v Regional TabLanguage (default value: American English)Specify the language to use for displaying the GUI and DataProtection for Exchange messages. The following languages areavailable during installation:– English (United States) (This is the default).– Brazilian Portuguese– Chinese (Simplified)– Chinese (Traditional)– French– German– Italian– Japanese– Korean– SpanishThe language you specify does not become effective until youexit and restart the GUI.Date Format (default value: mm/dd/yyyy)Specify the date format of your choice.– dd Day of the Month– mm Month of the Year– yyyy YearTime Format (default value: hh:mm:ss)Specify the format for displaying time.– hh Hours (24-hour day)– mm Minutes in an hour– ss Seconds in a minuteNumber Format (default value: xxx,xxx.dd)Specify the format for displaying numbers. The choices on thedisplay represent several ways to place the decimal, comma, andspaces.v VSS Backup TabDefault Backup Destination (default value: TSM Server)Select the default storage location for your backups. You canselect from the following storage locations:Chapter 4. Using the Graphical User Interface (GUI) 51

IBM ConfidentialTSM ServerThe data is stored on Tivoli Storage Manager serverstorage only. This is the default.Local The backup is stored on local shadow volumes only.Both The backup is stored on both Tivoli Storage Managerserver storage and local shadow volumes. Note that ifthis parameter is selected, the Tivoli Storage Managerserver backup cannot be off-loaded.Note that this parameter is only valid when using the VSSbackup method.Local DSMAGENT Node nameSpecify the Tivoli Storage Manager node name (agent node) ofthe local client machine that performs VSS operations and movesthe VSS data from local shadow volumes to Tivoli StorageManager server storage during Tivoli Storage Manager serverbackups. This parameter must be specified for VSS operations tobe performed.Remote DSMAGENT Node nameSpecify the Tivoli Storage Manager node name (agent node) ofthe remote client machine that moves the VSS data from localshadow volumes to Tivoli Storage Manager server storageduring off-loaded backups.For specific considerations related to these configuration settings, see “Setcommand” on page 106.ViewMenuRefresh tree viewWhen the tree is refreshed, the GUI will:v clear all selectionsv clear all List View information for all Storage Groupsv rebuild the directory treev completely expand the directory treeIf you simply move back and forth between the Backup and Restore tabswithout refreshing, you do not lose the current selections or Tree View. Ifyou switch from the Restore tab to the Backup tab, perform a new backup,then switch back to the Restore tab, you must refresh the Restore directorytree to see the new backup.Show only Active objectsSelect this option to display only active backup objects in the List View.This is the default value.Show all objectsSelect this option to display both active and inactive objects in the ListView.Auto SelectSelect this option to quickly select the backup objects to restore. WhenAuto Select is off, you must click on all objects to be restored. When AutoSelect is on (the default value), additional selections are automaticallymade as you click.52 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUtilitiesMenuThe following is characteristic of Auto Select:v Operates when you click on a full, differential, or incremental backup inthe List View. Auto Select also operates when you click on a storagegroup or server name in the Tree View.v Ignores copy and database copy backups.v If you click on a full backup, the latest associated differential or allassociated incremental backups are selected.v If you click on a differential backup, the associated full backup is alsoselected.v If you click on an incremental backup, the associated full backup and allassociated earlier incremental backups are also selected.v Operates when you deselect a full, differential, incremental, storagegroup, or server name.Auto Select will not make additional selections in the following twosituations:v If a combination of differential and incremental backups exist for a fullbackup. for example, if you clicked on a full backup that had associatedincremental and differential backups, only the full backup is selected.v If a differential or incremental backup is selected and no associated fullbackup can be found.To override the characteristics of Auto Select, deselect the Auto Selectoption and manually select what you need.Change TSM PasswordThis dialog prompts you to enter the old password, then enter the newpassword twice, in order to verify the new password. See“Changetsmpassword command” on page 103 for additional information.TSM Server InformationThis window displays the following Tivoli Storage Manager serverconnection information:vNodenamev Server Network Host Namev Tivoli Storage Manager API Versionv Server Namev Server Typev Server Versionv Compression Modev Domain Namev Active Policy Setv Default Management ClassHelpMenuData Protection for Microsoft Exchange ServerLaunches Data Protection for Exchange online help.BooksOnlineLaunches the March 2006 edition of the Data Protection for ExchangeInstallation and User’s Guide.Chapter 4. Using the Graphical User Interface (GUI) 53

IBM ConfidentialTSM Web AccessLaunches an online help panel that contains links to IBM, Tivoli StorageManager, and Exchange Server Web site links.About Data Protection for Microsoft Exchange ServerLaunches a splash screen that contains product release information.ToolbarThe Toolbar provides short cuts to frequently used tasks such as:v Refresh the Tree Viewv Edit Data Protection for Exchange configurationv Display IBM, Tivoli Storage Manager, and Exchange Server Web site linksv Display the the March 2006 edition of the Data Protection for Exchange Installationand User’s GuideGUIInvocationThe following parameters can be entered when the GUI is launched from thecommand line interface:/configfileSpecify this parameter to override the default Data Protection for Exchangeconfiguration file (tdpexc.cfg).For example, to specify the configuration file, file.cfg, located in the\temp\test directory during the GUI invocation, you would enter thefollowing command in the Data Protection for Exchange command lineinterface:tdpexc /CONFIGfile=c:\temp\test\file.cfg/excserverSpecify this parameter to override the default Exchange server. The defaultExchange server is the local Exchange server. IMPORTANT! If you arerunning Data Protection for Exchange in a MSCS or VCS, you MUSTinvoke the GUI with the /excserver parameter from the Data Protection forExchange command line.For example, to specify the Exchange server exc1 during the GUIinvocation, you would enter the following command in the Data Protectionfor Exchange command line interface:tdpexc /EXCSERVer=exc1/tsmoptfileSpecify this parameter to override the default Tivoli Storage Manageroption file (dsm.opt).For example, to specify the file.opt option file located in the \temp\testdirectory during the GUI invocation, you would enter the followingcommand in the Data Protection for Exchange command line interface:tdpexc /TSMOPTFile=c:\temp\test\file.opt54 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialBackup and Restore WindowData Protection for Exchange provides separate windows for backup and restoreoperations. Each window contains its own directory tree, list, and tab controls.Considerationsv Both Legacy and VSS operations are performed from the same tab.v The backup window is the initial window visible upon startup of the GUI.v You cannot close, minimize, or move the backup or restore windowindependently of the main GUI window.v Note that a VSS related feature is greyed out when the Exchange VSSIntegration Module is not installed.Highlighting and Selectingv When an item is highlighted in the Tree, information about all the items onelevel under the highlighted item is displayed in the List View. For example, if aStorage Group is highlighted in the Restore Tree, all Tivoli Storage Managerbackups for that Storage Group are displayed in the List View.v The following list contains exception– If the Site, Organization, or Domain name is highlighted in the Backup Tree,information about the Site, Organization, or Domain, Exchange server, andversion level are displayed in the List View.– If the Information Store item is highlighted in the Backup Tree, the List Viewdisplays status for all Storage Groups.– If the server name is highlighted in the Restore Tree, the List View displays allStorage Groups and their backups (indented under the Storage Group).v Highlighting the List View has no effect.v To select an item for backup or restore, click on the square selection box to theleft of the item name. Clicking on a selection box in the Tree will also highlightthat item, displaying associated information in the List View.v Double-clicking on a selection box in the Tree will select that item and collapseor expand the Tree at that point. An item can be selected from both the Tree andthe List View.v If a selection box contains an ″X″, the selection is disabled for that item. Youmay still be able to backup or restore the item. For example, if a Storage Groupitem has a disabled selection box in the Tree and all the List View items alsohave disabled selection boxes, then those items cannot be selected for backup orrestore. This can happen only if you have an empty Tivoli Storage Managerserver file space. See the restore option Auto Select for additional information onselecting items in the Tree and List View.Note that some selectable items, such as inactive Tivoli Storage Manager Backups,can only be selected in the List View.MessagesPlease be aware of the following IMPORTANT messages when performing backupor restore operations:v Selecting multiple Copy, Full, or Database Copy backups, or any combination ofthese backups, for restore, a warning message will ask you if you want tocontinue. If you continue, all backups will be restored but only the latest backupwill take affect. All the time spent restoring the earlier backups will be wasted.Chapter 4. Using the Graphical User Interface (GUI) 55

IBM Confidentialv When you request a backup to be restored, Data Protection for Exchange willfirst check to make sure any databases have been dismounted. If they have not,you will be prompted to stop them or cancel the restore. After a restore, you cancheck the Mount Databases After Restore option, or mount them from outsideData Protection for Exchange.GUITasksHow to perform a Legacy Backup||||||||||||In order to perform backup tasks, Data Protection for Exchange must be operatingin an account that meets these two conditions:1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator rolev Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group for themachine on which the Exchange server is running.This procedure assumes that Data Protection for Exchange and the Tivoli StorageManager server are properly configured in your environment. See Chapter 3,“Configuring Data Protection for Exchange,” on page 31 for detailed instructionson how to configure these applications.Follow these steps to perform a Legacy backup of your data:1. Start the Data Protection for Exchange GUI. If you are running Data Protectionfor Exchange in a MSCS or VCS:Note:a. If you are backing up the Site Replication Service (SRS), you must initializethe SRS database through the cluster administrator. The SRS must berunning in order to be backed up.b. You MUST invoke the GUI with the /excserver parameter from the DataProtection for Exchange command line.2. From the Tree View, select one or more storage groups to back up. You can alsoselect one or more storage groups to back up in the List View. Note that youcannot back up more than one application (SRS, IS) in a single operation.3. In the Backup Options section of the Backup window, select the Legacy Backupmethod.||||Note: You can specify that Data Protection for Exchange retry a failed backupby setting the Retries for Legacy Backup parameter in the Data Protection forExchange Settings window. From the File Menu, click on Edit -> Configuration-> General Tab.4. Specify the type of backup to perform with the Backup Type drop-down menu.Note that you cannot perform a database copy of an SRS database.5. Click on the Backup button to begin the backup operation.How to perform a VSS Backup||In order to perform backup tasks, Data Protection for Exchange must be operatingin an account that meets these two conditions:56 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential||||||1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator rolev Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group for themachine on which the Exchange server is running.This procedure assumes that Data Protection for Exchange, the Tivoli StorageManager backup-archive client, the Tivoli Storage Manager server, the MicrosoftExchange VSS Integration Module, and a VSS or VDS provider are properlyconfigured in your environment. See Chapter 3, “Configuring Data Protection forExchange,” on page 31 for detailed instructions on how to configure theseapplications.|||||||||||Follow these steps to perform a VSS Backup of your data:1. Start the Data Protection for Exchange GUI. If you are running Data Protectionfor Exchange in a MSCS or VCS, you MUST invoke the GUI with the /excserverparameter from the Data Protection for Exchange command line.2. Make sure a Local DSMAGENT Node name is specified. You can specify thisnode name using the Data Protection for Exchange Settings window. From theFile Menu, click on Edit -> Configuration -> VSS Backup Tab.3. From the Tree View, select one or more storage groups to back up. You can alsoselect one or more storage groups to back up in the List View.4. In the Backup Options section of the Backup window, select the VSS Backupmethod. Note that this method will automatically be selected when the UseVSS as the default Backup method parameter is selected in the Data Protectionfor Exchange Settings window. If the Microsoft Exchange VSS IntegrationModule is not installed, the VSS Backup method is not available for selection.5. Specify the storage destination of your backup with the Backup Destinationdrop-down menu.You can also use an alternate machine to offload the movement of theExchange data to Tivoli Storage Manager server storage. This type of backuprequires that a Remote DSMAGENT Node be specified and that a VSShardware subsystem (that supports transportable shadow copies) be available.See “How to perform a VSS Off-loaded Backup” for detailed information.6. Specify the type of backup to perform with the Backup Type drop-down menu.Note that you can only perform a full, copy, or copy without integrity checkbackup with the VSS Backup method.7. If you are running in an Exchange Server Local Continuous Replication (LCR)or Cluster Continuous Replication (CCR) environment and you want to backup from the replica copy, select the Backup using replica (if present) option inthe Backup window. Note that for CCR copies, you must run the backup whilelogged in to the secondary node of the cluster that currently contains thereplica copy.8. Click on the Backup button to begin the backup operation.How to perform a VSS Off-loaded Backup||||In order to perform backup tasks, Data Protection for Exchange must be operatingin an account that meets these two conditions:1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator roleChapter 4. Using the Graphical User Interface (GUI) 57

IBM Confidential||||v Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group for themachine on which the Exchange server is running.This procedure assumes that Data Protection for Exchange, the Tivoli StorageManager backup-archive client, the Tivoli Storage Manager server, the MicrosoftExchange VSS Integration Module, and a VSS or VDS provider are properlyconfigured in your environment. See Chapter 3, “Configuring Data Protection forExchange,” on page 31 for detailed instructions on how to configure theseapplications.An off-loaded backup uses an alternate machine (specified with the RemoteDSMAGENT Node parameter) to move Exchange data to Tivoli Storage Managerserver storage. This may help reduce network, I/O, and CPU resources associatedwith the production machine from being impacted during backup processing. Italso uses the alternate machine to perform the Exchange Integrity Check.||||||Follow these steps to perform a VSS off-loaded backup of your data:1. Start the Data Protection for Exchange GUI. If you are running Data Protectionfor Exchange in a MSCS or VCS, you MUST invoke the GUI with the /excserverparameter from the Data Protection for Exchange command line.2. Make sure a Local DSMAGENT Node name is specified. You can specify thisnode name using the Data Protection for Exchange Settings window. From theFile Menu, click on Edit -> Configuration -> VSS Backup Tab.3. Make sure a Remote DSMAGENT Node name is specified. You can specify thisnode name using the Data Protection for Exchange Settings window. From theFile Menu, click on Edit -> Configuration -> VSS Backup Tab.4. From the Tree View, select one or more storage groups to back up. You can alsoselect one or more storage groups to back up in the List View.5. In the Backup Options section of the Backup window, select theVSS Backupmethod. Note that this method will automatically be selected when the UseVSS as the default Backup method option is selected in the Data Protection forExchange Settings window. If the Microsoft Exchange VSS Integration Moduleis not installed, the VSS Backup method is not available.6. In the Backup Destination drop-down menu, select TSM Server (Offloaded).7. Specify the type of backup to perform with the Backup Type drop-down menu.Note that you can only perform a full, copy, or copy without integrity checkbackup with the VSS off-loaded backup method.8. If you are running in an Exchange Server Local Continuous Replication (LCR)or Cluster Continuous Replication (CCR) environment and you want to backup from the replica copy, select the Backup using replica (if present) option inthe Backup window. Note that for CCR copies, you must run the backup whilelogged in to the secondary node of the cluster that currently contains thereplica copy.9. Click on the Backup button to begin the backup operation.Restoring Exchange storage groups||||In order to perform restore tasks, Data Protection for Exchange must be operatingin an account that meets these two conditions:1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator role58 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential|||||||||||||v Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group for themachine on which the Exchange server is running.Review the “VSS restore considerations” before attempting any type of VSS restore.(Legacy restores only) When performing a Legacy restore of mailbox databases, ifa Recovery Storage Group exists, mailbox databases will be restored to theRecovery Storage Group instead of to the original storage group. Also, whenrestoring a mailbox database to a Recovery Storage Group, you must specify theReplay Restored Logs Only option or the restore operation may fail. This noteONLY applies to Legacy restores. VSS restores to the Recovery Storage Group areNOT supported by Microsoft with Exchange Server 2003 and Exchange Server2007.When you restore a storage group, be aware that data which exists in the storagegroup is overwritten and is no longer available after the restore is complete.|||||Perform the following steps to restore an Exchange server storage group:1. Start the Data Protection for Exchange GUI.2. Click on the Restore tab.3. From the Tree View, select the Exchange server storage group to restore. Torestore a particular database, first highlight the storage group in the Tree View.Then select the database to be restored in the List View. To restore all availablestorage groups, select the Exchange server in the Tree View.The List View displays the following information about your backups:v Backup Method (Legacy or VSS)v Type (Full, Incremental, Differential, Copy, Database Copy)v Backup Location (TSM Server or VSS Device)v Management Class (The Tivoli Storage Manager server management class towhich the backup belongs.)4. If you want to restore the Exchange Server 2007 storage group into theRecovery Storage Group or into an alternate storage group, right-mouse clickon the selected storage group and click on the Restore into option. Select thesame storage group name (as the one being restored) from the list of availablestorage groups.5. Select the appropriate restore options in the Restore Options section. See“Restore options” on page 60 for details.6. Click on the Restore button to begin the restore operation.VSS restore considerationsBe aware of the following considerations when performing VSS restores. Unlessotherwise specified, ″VSS restores″ refers to all restore types that use VSS (VSSRestore, VSS Fast Restore, VSS Instant Restore):v VSS restores ignore the Recovery Storage Group and are placed directly into theproduction database.v The VSS Backups to be restored must be from the same snapshot (i.e. contain thesame timestamp). VSS Backups that contain different timestamps must berestored one at a time and cannot be restored together in a single operation.v A VSS Instant Restore overwrites the entire contents of the source volumes.However, you can avoid overwriting the source volumes by selecting theChapter 4. Using the Graphical User Interface (GUI) 59

IBM ConfidentialDisable VSS Instant Restore option. This option bypasses volume-level copyand uses file-level copy instead to restore the files from a VSS Backup thatresides on local shadow volumes.v Unlike Legacy restores (which only dismount the database being restored), VSSrestores dismount all databases in the storage group that is being restored. Thisis a Microsoft requirement.v If a hardware provider is used, the disks that contain Exchange data must beconfigured as basic.v Be aware that when a VSS restore from local shadow volumes is performed, thebytes transferred will display ″0″. That is because no data (″0″) is restored fromthe Tivoli Storage Manager server.v When performing a VSS Instant Restore, you must restore ALL databases withinthe specified storage group. You cannot perform a partial restore (/partial) whileusing VSS Instant Restore. Although Data Protection for Exchange allows thisoperation to begin, it will either fail or complete with undesirable consequences.If you need to restore just one database from a VSS Backup that resides on localVSS shadow volumes on DS or SAN Volume Controller disks, make sure toselect the Disable VSS Instant Restore option in the Data Protection forExchange GUI Restore Window. If VSS Instant Restore capability is needed forsingle databases, make sure to place these databases in their own storage group.Restoring the Site Replication Service (SRS)When you restore an SRS database, be aware that data which exists in the SRSdatabase is overwritten and is no longer available after the restore is complete.Perform the following steps to restore an SRS database:1. Stop the SRS service.2. Rename the SRSDATA folder (located in the Exchange folder path) to a name ofyour choice.3. Start the SRS service.4. Start the Data Protection for Exchange GUI.5. Click on the Restore tab.6. From the Tree View, select the SRS database for restore. You cannot restoremore than one application (SRS, IS) in a single operation.7. Select the appropriate restore options.8. Click on the Restore button to begin the restore operation.RestoreoptionsRunRecoverySelect this option to specify whether to replay just the restored logs or toreplay both the restored and current logs. When recovery is not run, thedatabases are not online. As a result, recovery must be run for Legacyrestores by either another restore operation (with Run Recovery specified)or manually using the ESEUTIL utility.v Select Replay Restored AND Current Logs to replay any transaction logentries appearing in the current active transaction log. This includes bothcurrent and restored logs. This is the default value. Note that this optionis not supported for VSS Instant Restore.60 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialv Select Replay Restored Logs ONLY to replay any transactions appearingin the restored transaction logs. IMPORTANT: After performing this typeof restore, it is highly recommended that you perform a new fullbackup.|||||||Note: (Legacy restores only) When performing a Legacy restore ofmailbox databases, if a Recovery Storage Group exists, mailbox databaseswill be restored to the Recovery Storage Group instead of to the originalstorage group. Also, when restoring a mailbox database to a RecoveryStorage Group, you must specify the Replay Restored Logs Only option orthe restore operation may fail. This note ONLY applies to Legacy restores.VSS restores to the Recovery Storage Group are NOT supported byMicrosoft with Exchange Server 2003 and Exchange Server 2007.Mount Databases After RestoreSelect this option to automatically mount databases within the storagegroup after the recovery completes. With Exchange Server 2003, if theLegacy restore operation is a mailbox restore to the Recovery StorageGroup, the database mounted is the database in the Recovery StorageGroup, not the database in the original storage group.Disable VSS Instant RestoreSelect this option to bypass volume-level copy and instead use file-levelcopy to restore the files from a VSS Backup that resides on local shadowvolumes. Bypassing volume-level copy means that Exchange database files,log files, and the checkpoint file are the only data overwritten on thesource volumes. This can result in a longer restore processing time. If thisoption is not selected, volume level snapshot restore is used for these VSSBackup if the backup exists on volumes that support it. The default valueis to use volume level snapshot restore if supported.Restore IntoSelect the name of the Exchange Server 2007 storage group into which theVSS Backup will be restored. In order to restore into the Recovery StorageGroup (RSG), the RSG must already exist (with the databases to berestored already added to it) before attempting the restore operation. Notethat VSS restores to the Recovery Storage Group are NOT supported byMicrosoft with Exchange Server 2003.Data Protection for Exchange in a MSCS or VCS environmentConsider the following information when running Data Protection for Exchange ina MSCS or VCS environment:v The GUI MUST be invoked from the command line with the /excserverparameter. For example, if the Exchange virtual server name on the cluster isexc1, the command line entry (GUI invocation) istdpexc /excserver=exc1v The Start menu shortcut for the Data Protection for Exchange GUI applicationMUST be modified. Modify the Start menu shortcut for the Data Protection forExchange GUI application by performing the following steps:1. Right-mouse click on the Data Protection for Exchange GUI icon.2. Select Properties.3. Select Shortcut.4. Enter the following text in the Target window:"C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.exe /excserver=exc1"Chapter 4. Using the Graphical User Interface (GUI) 61

IBM Confidentialwhere Data Protection for Exchange is installed in the default installationdirectory and the Exchange virtual server name is exc1.62 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialChapter 5. Using the Command Line InterfaceThis chapter describes how to use the Data Protection for Exchange command lineinterface. Each command includes a syntax diagram and a description. See formore information.The next section is an overview of the command line interface. The commands aredescribed in the following categories:vvvvvvQueryBackupRestoreChangetsmpasswordSetHelpThe Data Protection for Exchange command line interface can also be used whenscheduling automatic backups of Exchange databases. See Chapter 6, “Using theTivoli Storage Manager scheduler,” on page 115 for a discussion of using the TivoliStorage Manager scheduler with Data Protection for Exchange.CommandoverviewThe name of the Data Protection for Exchange command line interface istdpexcc.exe. This program is located in the directory where Data Protection forExchange is installed.The command line parameters have the following characteristics:v positional parameters do not include a leading slash (/) or dash (-)v optional parameters can appear in any order after the required parametersv optional parameters begin with a forward slash (/) or a dash (-)v minimum abbreviations for keywords are indicated in upper case textv some keyword parameters require a valuev for those keyword parameters that require a value, the value is separated fromthe keyword with an equal sign (=)v if a parameter requires more than one value after the equal sign, the values areseparated with commasv each parameter is separated from the others by using spacesv if a parameter’s value includes spaces, the value must be enclosed in doublequotesv a positional parameter can appear only once per command invocationIssue the tdpexcc ? or tdpexcc help command to display help for the commandline interface.63

IBM ConfidentialQuery Exchange commandUse this command to query the local Exchange Server for general information.The query exchange command returns the following information:v Version and level of the Exchange Serverv Domain and Server Namesv Storage groups and all database names with status of eachv Exchange Server 2003 Recovery Storage Group statusv Whether the storage group has circular logging enabledv VSS Information (only applicable when configured for VSS operations)Query Exchange syntaxUse the query exchange command syntax diagrams as a reference to viewavailable options and truncation requirements.►► TDPEXCC Query EXCHange/CONFIGfile=tdpexc.cfgconfigfilename►►/EXCSERVer=local Exchange serverserver-name►►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►◄Query Exchange optional parametersOptional parameters follow the query exchange command./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg.64 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential/EXCSERVer=server-nameUse the /excserver parameter to specify the name of the Exchange Serverto query.The server-name variable specifies the name of the Exchange Server toquery.Considerationsv If the Exchange Server to query is a member of a Microsoft ClusterServer, this parameter must be specified and should be set to the nameof the Exchange virtual server.v The default value is the local Exchange Server./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. Thelogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:Chapter 5. Using the Command Line Interface 65

IBM Confidentialv Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting.Query Exchange Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the query exchange command.The tdpexcc query exchange command queries the Exchange server. An exampleof the output when this command is performed on Exchange Server 2003 isdisplayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.loglog file has been pruned successfully.Microsoft Exchange Server Information-------------------------------------Server Name: TESEXCHDomain Name: emmaeus.test.localExchange Server Version: 6.0.4417.0Storage Groups with Databases and Status----------------------------------------First Storage GroupCircular Logging - DisabledMailbox Store (TESEXCH) OnlinePublic Folder Store (TESEXCH) OnlineSecond Storage GroupCircular Logging - DisabledMailbox Store SSG 1 Onlinestg3Circular Logging - Disabledmail3OnlineQuery Exchange Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the query exchange command.This tdpexcc query exchange command queries an Exchange Server 2003. Theoutput example displays that a Recovery Storage Group exists and that all mailboxdatabase will be restored to it.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Microsoft Exchange Server Information-------------------------------------Server Name: GUEST5Domain Name: guest5.quest00.localExchange Server Version: 6.5.6944.0Storage Groups with Databases and Status66 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential----------------------------------------First Storage GroupCircular Logging - DisabledMailbox Store (GUEST5) OnlinePublic Folder Store (GUEST5) OnlineMySecond Storage GroupCircular Logging - DisabledsecondmailboxMyThird Storage GroupCircular Logging - DisabledthirdstorageboxOnlineOfflineRecovery Storage Group exists - All mailbox databases will be restored here.Query Exchange Example 3This output example provides a sample of the text, messages, and process statusthat displays when using the query exchange command.In this example, the tdpexcc query exchange command queried an ExchangeServer that is configured for VSS operations. The following output is displayed:IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log file has been pruned successfully.Microsoft Exchange Server Information-------------------------------------Server Name: ONYDomain Name: optimus.zor.localExchange Server Version: 6.5.7638.1Storage Groups with Databases and Status----------------------------------------First Storage GroupCircular Logging - Disabledforfun store OnlineMailbox Store (ONY) OnlinePublic Folder Store (ONY) Onlinestg3Circular Logging - Disabledmail1mail2mail3stg_bigCircular Logging - Disabledmail1mail2mail3mail4testCircular Logging - Disabledtest1OnlineOnlineOnlineOnlineOnlineOnlineOnlineOnlineVolume Shadow Copy Service (VSS) InformationChapter 5. Using the Command Line Interface 67

IBM ConfidentialQuery TDP command--------------------------------------------Writer Name : Microsoft Exchange WriterLocal DSMAgent Node : svc_baRemote DSMAgent Node : svc_offloadWriter Status : OnlineSelectable Components : 4Use this command to query a list of the current values set in the configuration filefor Data Protection for Exchange.Query TDP syntaxUse the query TDP command syntax diagrams as a reference to view availableoptions and truncation requirements.►► TDPEXCC Query TDP/CONFIGfile=tdpexc.cfgconfigfilename►►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►◄Query TDP optional parametersOptional parameters follow the query TDP command./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. The68 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentiallogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting.Query TDP ExampleThis output example provides a sample of the text, messages, and process statusthat displays when using the query TDP command.The tdpexcc query tdp command queries the values set in the Data Protection forExchange configuration file. An example of the output in a Legacy configuration isdisplayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Data Protection for Exchange Preferences----------------------------------------BACKUPDESTination...................BACKUPMETHod........................TSMLEGACYChapter 5. Using the Command Line Interface 69

IBM ConfidentialQuery TSM commandBUFFers ............................ 3BUFFERSIze ......................... 1024DATEformat ......................... 1LANGuage ........................... ENULOCALDSMAgentnode...................LOGFile ............................ tdpexc.logLOGPrune ........................... 60MOUNTWait .......................... YesNUMberformat ....................... 1REMOTEDSMAgentnode..................TEMPLOGRESTOREPath..................E:\TEMPTIMEformat ......................... 1An example of the output in a VSS configuration is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 3, Level 3.0(C) Copyright IBM Corporation 1998, 2006. All rights reserved.Data Protection for Exchange Preferences----------------------------------------BACKUPDESTination................... TSMBACKUPMETHod........................ VSSBUFFers ............................ 3BUFFERSIze ......................... 1024DATEformat ......................... 1LANGuage ........................... ENULOCALDSMAgentnode................... svc_baLOGFile ............................ tdpexc.logLOGPrune ........................... 60MOUNTWait .......................... YesNUMberformat ....................... 1REMOTEDSMAgentnode.................. machine1_baTEMPLOGRESTOREPath.................. c:\tdp\tdptemplogTIMEformat ......................... 1Use this command to query Tivoli Storage Manager for information about theTivoli Storage Manager API and the Tivoli Storage Manager server. This commandcan also display a list of backups that are stored on the Tivoli Storage Managerserver that match the storage groups entered. Active and inactive objects can bedisplayed.By default, only the active backup objects are displayed. To include inactivebackup versions in the list, use the /all optional parameter.Query TSM syntaxUse the query TSM command syntax diagrams as a reference to view availableoptions and truncation requirements.►► TDPEXCC Query TSM * FULLsg-name,sg-nameNCOPYINCRementalDIFFerentialDBCopy db-name/ACtive►70 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential►/ALl/CONFIGfile=tdpexc.cfgconfigfilename►►/FROMEXCSERVer=local Exchange serverserver-name►►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►►/SKIPINTEGRITYCHECK /TSMNODe= tsmnodename►►/TSMOPTFile=dsm.opttsmoptfilename/TSMPassword=tsmpassword►◄Query TSM positional parametersPositional parameters immediately follow the query TSM command and precedethe optional parameters.The following positional parameters specify the object to query. If none of thesepositional parameters are specified, only the Tivoli Storage Manager API and TivoliStorage Manager server information is displayed:* | DIR | IS | sg-name* Query all backup objects for all storage groupssg-nameQuery all backup objects for the specified storage group. Multipleentries are separated by commas.The following positional parameters specify the type of backup to query. If thisparameter is not specified, all backup types will be displayed:FULL | COPY | INCRemental | DIFFerential | DBCopy db-nameFULL Query only Full backup typesCOPY Query only Copy backup typesINCRementalQuery only Incremental backup typesDIFFerentialQuery only Differential backup typesDBCopy db-nameQuery only database copy backups for database db-name.Query TSM optional parametersOptional parameters follow the query TSM command and positional parameters.Chapter 5. Using the Command Line Interface 71

IBM Confidential/ACtiveUse the /active parameter to display active backup objects only. This is thedefault./ALl Use the /all parameter to display both active and inactive backup objects. Ifthe /all parameter is not specified, only active backup objects aredisplayed./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg./FROMEXCSERVer=server-nameUse the /fromexcserver parameter to specify the name of the ExchangeServer where the original backup was performed.The default is the local Exchange Server. However, you must specify thename if the Exchange Server is not the default or is a member of a MSCSor VCS./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. Thelogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for each72 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting./TSMNODe=tsmnodenameThe tsmnodename variable refers to the Tivoli Storage Manager node nameData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. You can also store the node name in the Tivoli Storage Manageroptions file. The command line parameter overrides the value in the TivoliStorage Manager options file if PASSWORDACCESS is set to PROMPT.This parameter is not valid when PASSWORDACCESS is set toGENERATE./TSMOPTFile=tsmoptfilenameThe tsmoptfilename variable identifies the Data Protection for Exchangeoptions file.The file name can include a fully qualified path name. If no path isspecified, the directory where Data Protection for Exchange is installed issearched.If the tsmoptfilename variable includes spaces, the entire /tsmoptfileparameter entry must be placed in double quotes. For example:/TSMOPTFile="c:\Program Files\file.opt"The default is dsm.opt./TSMPassword=tsmpasswordThe tsmpassword variable refers to the Tivoli Storage Manager passwordData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. If you specified PASSWORDACCESS GENERATE in the DataProtection for Exchange options file, then the password need not beprovided here because the one stored in the registry is used. However, inorder to store the password in the registry, you must specify the TivoliStorage Manager password the first time Data Protection for Exchangeconnects to the Tivoli Storage Manager server.Chapter 5. Using the Command Line Interface 73

IBM ConfidentialIf you do specify a password on the command line whenPASSWORDACCESS GENERATE is in effect, then the command line valueis ignored unless the password for this node has not yet been stored in theregistry. In that case, the specified password is the one that is stored in theregistry and used for the current command execution.If PASSWORDACCESS PROMPT is in effect, and a password value is notspecified on the command line, then you are prompted for a password.The Tivoli Storage Manager password Data Protection for Exchange uses tolog on to the Tivoli Storage Manager server can be up to 63 characters inlength.Query TSM Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the query TSM command.The tdpexcc query tsm command displays information about the Tivoli StorageManager API and Tivoli Storage Manager server. An example of the output isdisplayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.ACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.loglog file has been pruned successfully.Tivoli Storage Manager Server Connection Information----------------------------------------------------Nodename ............................... TURKEYNetWork Host Name of Server ............ FIREFLY.DOMAINXYZ.COMTSM API Version ........................ Version 5, Release 3, Level 3Server Name ............................ FIREFLYServer Type ............................ WindowsServer Version ......................... Version 5, Release 3, Level 2.0Compression Mode ....................... Client DeterminedDomain Name ............................ TSSVT1Active Policy Set ...................... TSSVT1Default Management Class ............... TSSVT1Query TSM Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the query TSM command.The tdpexcc query tsm * /all command displays information about the list ofbackups on the Tivoli Storage Manager server. An example of the output when thiscommand is performed on Exchange Server 2003 in a VSS configuration isdisplayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Querying Tivoli Storage Manager server for a list of database backups, please wait...Backup List-----------74 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialExchange Server : ONYXStorage Group : stg2Backup Date Size S Fmt Type Loc Object Name/Database Name------------------- ----------- - ---- ---- --- -------------------------01/17/2006 09:47:06 114.04MB I VSS full Srv 2006011709470642.02MBmailbox165.01MBLogs7,184.00KBmailbox201/17/2006 10:09:00 64.04MB A VSS full Srv 2006011710090042.02MBmailbox115.01MBLogs7,184.00KBmailbox201/17/2006 13:16:23 79.04MB A VSS full Loc 2006011713162342.02MBmailbox130.01MBLogs7,184.00KBmailbox2BackupCommandThe backup command performs Exchange Server storage group backups from theExchange Server to Tivoli Storage Manager server storage. You must have localregistry rights (for all versions of Exchange Server) to perform a Data Protectionfor Exchange backup. This command also backs up Site Replication Service (SRS)databases. Use the /excapplication option when backing up this databases.When a full Legacy backup is performed, all active Legacy backups previous tothis full backup are automatically inactivated for the particular storage group thatis being backed up.Note: Microsoft Exchange Server considers the wildcard character (*) to be aninvalid character when used in database and storage group names. As a result,database and storage groups that contain the wildcard character (*) in their namewill not be backed up.When a full VSS snapshot backup (created for back up to local shadow volumes) isperformed, the backup remains active until the backup version is expired on theTivoli Storage Manager server according to the defined server policy. As a result,five different active backups can exist at the same time:v Legacyv VSS local (full)v VSS local (copy)v VSS Tivoli Storage Manager server (full)v VSS Tivoli Storage Manager server (copy)For SAN Volume Controller storage subsystems, only one backup is allowed tooccur while the background copy process is pending. A new backup is notperformed until the background copy process for the previous backup completes.As a result, local backups for SAN Volume Controller storage subsystems shouldbe initiated at a frequency greater than the time required for the background copyprocess to complete.See “Backup strategies” on page 14 for additional information related to thebackup command.Data Protection for Exchange supports the following types of backup:Chapter 5. Using the Command Line Interface 75

IBM ConfidentialBackupFull (Legacy and VSS)Back up the entire storage group and transaction logs, and if a successfulbackup is obtained, deletes the transaction logsIncremental (Legacy only)Back up the transaction logs, and if a successful backup is obtained, deletesthe transaction logsDifferential (Legacy only)Back up the transaction logs but do NOT delete themCopy (Legacy and VSS)Back up the entire storage group and transaction logs, do NOT delete thetransaction logsDatabase Copy (Legacy only)Back up only the specified database and transaction logs, do NOT deletethe transaction logsNote: If there are databases within a storage group that are not mounted at thetime of the backup, the transaction logs will NOT be deleted.syntaxUse the backup command syntax diagrams as a reference to view available optionsand truncation requirements.►► TDPEXCC BACKup * FULLsg-name,sg-nameN COPY″SRS Storage″ INCRementalDIFFerentialDBCopy db-name►►/BACKUPDESTination=TSMLOCALBOTH/BACKUPMETHod=LEGACYVSS►►/BUFFers=3numbuffers/BUFFERSIze=1024buffersize►►/CONFIGfile=tdpexc.cfgconfigfilename/EXCAPPlication=ISSRS►►/EXCSERVer=local Exchange serverserver-name►|►/FROMREPLicaproductiondatabase►76 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►►/MOUNTWait=YesNo/OFFLOAD /Quiet /SKIPINTEGRITYCHECK►►/TSMNODe= tsmnodename dsm.opt/TSMOPTFile=tsmoptfilename►►/TSMPassword=tsmpassword►◄Backup positional parametersPositional parameters immediately follow the backup command and precede theoptional parameters.The following positional parameters specify the object to back up:* | DIR | IS | sg-name* Back up all storage groups sequentially.sg-nameBack up the specified storage group. Multiple entries are separatedby commas. If any storage group contains commas or blanks,enclose the storage group name in quotes.The following positional parameters specify the type of backup to perform:FULL | COPY | INCRemental | DIFFerential | DBCopy db-nameFULL (Legacy and VSS)Back up the entire storage group and transaction logs, and if asuccessful backup is obtained, truncate the transaction logs.COPY (Legacy and VSS)Back up the entire storage group and transaction logs, do NOTtruncate the transaction logs.INCRemental (Legacy only)Back up the transaction logs, and if a successful backup isobtained, truncate the transaction logs.DIFFerential (Legacy only)Back up the transaction logs but do NOT truncate them.DBCopy db-name (Legacy only)Back up only the specified database and transaction logs, do NOTtruncate the transaction logs. Note that this type of backup is notavailable with a VSS snapshot backup.If there are databases within a storage group that are not mounted at the time ofthe backup, the transaction logs will NOT be truncated.Chapter 5. Using the Command Line Interface 77

Backup optional parametersOptional parameters follow the backup command and positional parameters./BACKUPDESTination=TSM|LOCAL|BOTHUse the /backupdestination parameter to specify the location where thebackup is stored.You can specify:TSM The backup is stored on Tivoli Storage Manager server storageonly. This is the default.LOCALThe backup is stored on local shadow volumes only. This is onlyvalid when the /backupmethod parameter specifies VSS.BOTH The backup is stored on Tivoli Storage Manager server storage andlocal shadow volumes. This is only valid when the /backupmethodparameter specifies VSS./BACKUPMETHod=LEGACY|VSSUse the /backupmethod parameter to specify the manner in which thebackup is performed.You can specify:IBM ConfidentialLEGACYThe backup is performed with the legacy API. This is the Exchangestreaming backup and restore API as used in previous versions ofData Protection for Exchange. This is the default.VSS The backup is performed with VSS./BUFFers=numbuffersUse the /buffers parameter to specify the number of data buffers used formoving data between the Exchange Server and the Tivoli Storage ManagerAPI during Legacy backup and restore operations. Separate, asynchronousexecution threads are used by Data Protection for Exchange forcommunicating with the Exchange Server and Tivoli Storage ManagerAPIs. Increasing the number of data buffers improves throughput byreducing the possibility of one thread having to wait for another thread.The numbuffers variable refers to the number of data buffers to use. Thenumber of data buffers can be from 2 to 8. The default number of databuffers is 3./BUFFERSIze=buffersizeUse the /buffersize parameter to specify the size of data buffers used tomove data between the Exchange Server and the Tivoli Storage ManagerAPI during Legacy backup and restore operations.The buffersize variable refers to the size of the data buffers in kilobytes. Thesize of the data buffers can be from 64 to 8192 kilobytes. The default sizeof the data buffers is 1024 kilobytes./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.78 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialThe configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg./EXCAPPlication=SRSUse the /excapplication parameter to specify the name of the SRS databaseto be backed up during a Legacy backup operation. You must also specify"SRS Storage" for the storage group name in the command line syntax.The SRS database must be online and running to be backed up. SpecifySRS for the Site Replication Service database to be backed up. If no valueis specified, Data Protection for Exchange backs up the Information Storedatabase./EXCSERVer=server-nameUse the /excserver parameter to specify the name of the Exchange Serverto be backed up.The server-name variable specifies the name of the Exchange Server to bebacked up.Considerationsv If the Exchange Server to be backed up is a member of a MicrosoftCluster Server, this parameter must be specified and must be set to theExchange virtual server name.v The default value is the local Exchange Server.|||||||||||||/FROMREPLicaUse the /fromreplica parameter if you are running in an Exchange ServerLocal Continuous Replication (LCR) or Cluster Continuous Replication(CCR) environment and want to back up the Exchange data from thereplica copy. This parameter is available for VSS Backups only.Considerationsv For CCR copies, you must back up the replica copy from the secondarynode of the cluster that currently contains the replica copy.v For LCR copies, you must back up the replica copy from the samemachine as the live production storage group.v If the environment is not a CCR environment and replica does not exist,the production database is backed up.v The default value is to not back up the replica./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. TheChapter 5. Using the Command Line Interface 79

IBM Confidentiallogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting./MOUNTWait=Yes|NoIf the Tivoli Storage Manager server is configured to store the backup dataon removable media (such as tapes), then it is possible that the TivoliStorage Manager server might indicate to Data Protection for Exchangethat it is waiting for a required storage volume to be mounted. If thatoccurs, this parameter allows you to specify whether Data Protection forExchange should wait for the media mount or stop the current operation.You can specify:Yes Wait for tape mounts. This is the default.No Do not wait for tape mounts./OFFLOADSpecify this parameter to perform the integrity check and backup of files toTivoli Storage Manager on the machine specified by theremotedsmagentnode instead of the local machine. This parameter is80 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialONLY valid when /backupmethod=VSS and /backupdestination=TSM.Note that this parameter requires a VSS provider that supportstransportable shadow copies. It is not supported with the default WindowsVSS System Provider./Quiet This parameter prevents status information from being displayed. Thisdoes not affect the level of information written to the activity log./SKIPINTEGRITYCHECKSpecify this parameter to bypass the Exchange integrity check typicallyperformed during a backup. This parameter is ONLY valid when/backupmethod=VSS and the backup type is COPY.Attention:When using this parameter, it is possible that the stored backup is notvalid because it is not being verified with the Exchange integrity checkutility. Make sure that you have a valid backup stored on Tivoli StorageManager server storage./TSMNODe=tsmnodenameThe tsmnodename variable refers to the Tivoli Storage Manager node nameData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. You can also store the node name in the Tivoli Storage Manageroptions file. The command line parameter overrides the value in the TivoliStorage Manager options file if PASSWORDACCESS is set to PROMPT.This parameter is not valid when PASSWORDACCESS is set toGENERATE./TSMOPTFile=tsmoptfilenameThe tsmoptfilename variable identifies the Data Protection for Exchangeoptions file.The file name can include a fully qualified path name. If no path isspecified, the directory where Data Protection for Exchange is installed issearched.If the tsmoptfilename variable includes spaces, the entire /tsmoptfileparameter entry must be placed in double quotes. For example:/TSMOPTFile="c:\Program Files\file.opt"The default is dsm.opt./TSMPassword=tsmpasswordThe tsmpassword variable refers to the Tivoli Storage Manager passwordData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. If you specified PASSWORDACCESS GENERATE in the DataProtection for Exchange options file, then the password need not beprovided here because the one stored in the registry is used. However, inorder to store the password in the registry, you must specify the TivoliStorage Manager password the first time Data Protection for Exchangeconnects to the Tivoli Storage Manager server.If you do specify a password on the command line whenPASSWORDACCESS GENERATE is in effect, then the command line valueis ignored unless the password for this node has not yet been stored in theregistry. In that case, the specified password is the one that is stored in theregistry and used for the current command execution.Chapter 5. Using the Command Line Interface 81

IBM ConfidentialIf PASSWORDACCESS PROMPT is in effect, and a password value is notspecified on the command line, then you are prompted for a password.The Tivoli Storage Manager password Data Protection for Exchange uses tolog on to the Tivoli Storage Manager server can be up to 63 characters inlength.Backup Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the backup command.The tdpexcc backup ″First Storage Group″,″Second Storage Group″ incrementalcommand performs an incremental backup of Exchange Server storage groupsidentified as First Storage Group and Second Storage Group. An example of theoutput is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Starting storage group backup...Beginning incr backup of First Storage Group, 1 of 2.Full: 0 Read: 278 Written: 0 Rate: 0.00 Kb/SecFull: 2 Read: 9437462 Written: 5243158 Rate: 2 284.82 Kb/SecFull: 2 Read: 15728934 Written: 12583198 Rate: 3 797.37 Kb/SecFull: 0 Read: 20971822 Written: 20971822 Rate: 4 834.82 Kb/SecFull: 0 Read: 20971822 Written: 20971822 Rate: 4 834.82 Kb/SecBackup of First Storage Group completed successfully.Beginning incr backup of Second Storage Group, 2 of 2.Full: 0 Read: 198 Written: 0 Rate: 0.00 Kb/SecFull: 1 Read: 7340238 Written: 5243078 Rate: 2 305.35 Kb/SecFull: 0 Read: 10485966 Written: 10485966 Rate: 3 179.20 Kb/SecFull: 0 Read: 10485966 Written: 10485966 Rate: 3 179.20 Kb/SecBackup of Second Storage Group completed successfully.Total storage groups requested for backup: 2Total storage groups backed up: 2Total storage groups expired: 0Total storage groups excluded: 0Throughput rate: 4 046.43 Kb/SecTotal bytes transferred: 31 457 788Elapsed processing time: 7.59 SecsBackup Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the backup command.The tdpexcc backup ″Second Storage Group″ dbc ″Mailbox Store SSG 1″command performs a database copy backup of Exchange Server database MailboxStore SSG 1, located in storage group Second Storage Group. An example of theoutput is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.82 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5057I The C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log log filehas been pruned successfully.Starting storage group backup...Beginning dbcopy backup of storage group ,database , 1 of 1.Full: 2 Read: 7348466 Written: 3154162 Rate: 2 502.22 Kb/SecFull: 0 Read: 7356900 Written: 7356900 Rate: 3 221.74 Kb/SecFull: 2 Read: 11551204 Written: 7356900 Rate: 2 223.61 Kb/SecFull: 2 Read: 12608200 Written: 11551204 Rate: 2 666.15 Kb/SecFull: 0 Read: 12608200 Written: 12608200 Rate: 2 353.79 Kb/SecFull: 0 Read: 12608200 Written: 12608200 Rate: 2 353.79 Kb/SecBackup of Second Storage Group completed successfully.Total storage groups requested for backup: 1Total storage groups backed up: 1Total storage groups expired: 0Total storage groups excluded: 0Throughput rate: 2 350.20 Kb/SecTotal bytes transferred: 12 608 200Elapsed processing time: 5.24 SecsBackup Example 3This output example provides a sample of the text, messages, and process statusthat displays when using the backup command.The tdpexcc backup stg2 full /backupdestination=tsm /backupmethod=vsscommand performs a full VSS Backup of Exchange 2003 Server storage group stg2to Tivoli Storage Manager server storage. An example of the output is displayedbelow.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Connecting to TSM Server as node ’SVC_TDP’...Connecting to Local DSM Agent ’svc_ba’...Beginning VSS backup of ’stg2’...Preparing to backup using snapshot.Executing system command: Exchange integrity check for storage group ’stg2’Files Examined/Completed/Failed: [ 17 / 17 / 0 ] Total Bytes: 67192452VSS Backup operation completed with rc = 0Files Examined : 17Files Completed : 17Files Failed : 0Total Bytes : 67192452Backup Example 4This output example provides a sample of the text, messages, and process statusthat displays when using the backup command.The tdpexcc backup stg2 full /backupdestination=local /backupmethod=vsscommand performs a full VSS Backup of Exchange 2003 Server storage group stg2to local shadow volumes. An example of the output is displayed below.Chapter 5. Using the Command Line Interface 83

IBM ConfidentialIBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Connecting to TSM Server as node ’SVC_TDP’...Connecting to Local DSM Agent ’svc_ba’...Beginning VSS backup of ’stg2’...Preparing to backup using snapshot.Executing system command: Exchange integrity check for storage group ’stg2’Files Examined/Completed/Failed: [ 10 / 10 / 0 ] Total Bytes: 33547VSS Backup operation completed with rc = 0Files Examined : 10Files Completed : 10Files Failed : 0Total Bytes : 33547Backup Example 5This output example provides a sample of the text, messages, and process statusthat displays when using the backup command.The tdpexcc backup * full /backupdestination=both /backupmethod=vsscommand performs a full VSS Backup of Exchange 2003 Server storage groupsstg2, stg3, stg4, and First Storage Group to local shadow volumes and to TivoliStorage Manager server storage. An example of the output is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Connecting to TSM Server as node ’TDP_REAL’...Connecting to Local DSM Agent ’ba_real’...Starting storage group backup...Beginning VSS backup of ’stg2’, ’First Storage Group’, ’stg4’, ’stg3’...Preparing to backup using snapshot.Executing system command: Exchange integrity check for storage group ’stg4’Executing system command: Exchange integ chk strg grp ’First Storage Group’Executing system command: Exchange integrity check for storage group ’stg2’Executing system command: Exchange integrity check for storage group ’stg3’Files Examined/Completed/Failed: [ 187 / 187 / 0 ] Total Bytes: 6706246239VSS Backup operation completed with rc = 0Files Examined : 187Files Completed : 187Files Failed : 0Total Bytes : 6706246239RestorecommandUse this command to restore a storage group backup from Tivoli Storage Managerstorage to an Exchange Server. You must have local registry rights (for all versionsof Exchange Server) to perform a Data Protection for Exchange restore. Thiscommand also restores the Site Replication Service (SRS) database. Use the/excapplication option when restoring these databases.84 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialWhen using the restore command, keep the following points in mind:v When restoring inactive backups or active incremental backups, use the /objectparameter to specify the name of the backup object to restore. This object nameuniquely identifies the backup instance in Tivoli Storage Manager storage. Youcan issue a tdpexcc query tsm command to obtain a list of the object names.Note: If the tdpexcc restore sgname incr command is entered (without the/object parameter) to restore multiple active incremental backups, all multipleactive incremental backups are restored sequentially. The /object parameter isused to restore only one incremental backup at a time.v IMPORTANT: To initiate recovery, you MUST use the /recover parameter whenrestoring the last backup object of a storage group. In addition, the value of/templogrestorepath should not be the same value as the current location for thestorage group. If the value is the same, corruption can occur.– Specify /recover=applyalllogs to replay the restored transaction log entriesAND the current active transaction log entries.– Specify /recover=applyrestoredlogs to replay ONLY the restored transactionlog entries. The current active transaction log entries will NOT be replayed.Note: When choosing this option for a restore, your next backup MUST be afull or copy backup.Failure to use the /recover parameter when restoring the last backup set of astorage group leaves the databases unmountable. If this occurs, for Legacybackups you can either restore the last backup again and specify the/recover=value option or you can use the Microsoft ESEUTIL /cc command torun recovery manually.v Specify /mountdatabases=yes if you are restoring the last backup set and youwant the databases within the storage group automatically mounted after therecovery completes. Note that when restoring mailbox databases to a RecoveryStorage Group with Exchange Server 2003, the mailbox databases will berestored to the Recovery Storage Group (when a Group exists) and that theoriginal databases will not be dismounted. Only transaction logs that arecontained in the backup will be applied to the mailbox database whenperforming a Recovery Storage Group restore. You must specify/recover=applyrestoredlogs when restoring a mailbox database to a RecoveryStorage Group or the restore operation may fail.The GUI provides an easy-to-use, flexible interface to help you perform a restoreoperation. The interface presents information in a way that allows multipleselection and, in some cases, automatic operation.Note: Microsoft Exchange Server considers the wildcard character (*) to be aninvalid character when used in database and storage group names. As a result,database and storage groups that contain the wildcard character (*) in their namewill not be backed up.Data Protection for Exchange supports the following types of restore:Full (Legacy and VSS)Restore a Full type backupCopy (Legacy and VSS)Restore a Copy type backupIncremental (Legacy only)Restore an Incremental type backupChapter 5. Using the Command Line Interface 85

IBM ConfidentialDifferential (Legacy only)Restore a Differential type backupDatabase copy (Legacy only)Restore a Database Copy type backup.VSS restore considerationsBe aware of the following considerations when performing VSS restores. Unlessotherwise specified, ″VSS restores″ refers to all restore types that use VSS (VSSRestore, VSS Fast Restore, VSS Instant Restore):Restorev VSS restores ignore the Recovery Storage Group and are placed directly into theproduction database.v The VSS Backups to be restored must be from the same snapshot (i.e. contain thesame timestamp). VSS Backups that contain different timestamps must berestored one at a time and cannot be restored together in a single operation.v A VSS Instant Restore overwrites the entire contents of the source volumes.However, you can avoid overwriting the source volumes by specifying/INSTANTRESTORE=NO. This parameter bypasses volume-level copy and usesfile-level copy instead to restore the files from a VSS Backup that resides on localshadow volumes.v Unlike Legacy restores (which only dismount the database being restored), VSSrestores dismount all databases in the storage group that is being restored.v If a hardware provider is used, the disks that contain Exchange data must beconfigured as basic.v Be aware that when a VSS restore from local shadow volumes is performed, thebytes transferred will display ″0″. That is because no data (″0″) is restored fromthe Tivoli Storage Manager server.syntaxUse the restore command syntax diagrams as a reference to view available optionsand truncation requirements.►► TDPEXCC RESTore * FULLsg-name,sg-nameNCOPYINCRementalDIFFerentialDBCopy db-name►►/BACKUPDESTination=backupdestination or tdpexc.cfgTSMLOCAL►►/BACKUPMETHod=backupmethod or tdpexc.cfgLEGACYVSS►86 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential►/BUFFers=3numbuffers/BUFFERSIze=1024buffersize►►/CONFIGfile=tdpexc.cfgconfigfilename/EXCAPPlication=SRS►►/EXCSERVer=local Exchange serverserver-name►►/FROMEXCSERVer=local Exchange serverserver-name►|►/INSTANTRESTORE=YesNo/INTOSG=into-sg-name►►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►►/MOUNTDAtabases=NoYes/MOUNTWait=YesNo/OFFLOAD►►/OBJect=current backup objectobject-name/PARTial= dbname1, dbnameN►►/Quiet/RECOVer=APPLYALLlogsAPPLYRESToredlogs►►►/TEMPLOGRESTorepath= path-name /SKIPINTEGRITYCHECK/TSMNODe= tsmnodename dsm.opt/TSMOPTFile=tsmoptfilename►►►/TSMPassword=tsmpassword►◄Restore positional parametersPositional parameters immediately follow the restore command and precede theoptional parameters.The following positional parameters specify the object to restore:Chapter 5. Using the Command Line Interface 87

IBM Confidential* | sg-name* Restore all storage groups sequentially.sg-nameRestore the specified storage group. Multiple entries are separatedby commas. If any storage group contains commas or blanks,enclose the storage group name in quotes.The following positional parameters specify the type of restore to perform:FULL | COPY | INCRemental | DIFFerential | DBCopy db-nameFULL (Legacy and VSS)Restore a Full type backupCOPY (Legacy and VSS)Restore a Copy type backupINCRemental (Legacy only)Restore an Incremental type backupDIFFerential (Legacy only)Restore a Differential type backupDBCopy db-name (Legacy only)Restore the db-name database copy backup.Restore optional parametersOptional parameters follow the restore command and positional parameters./BACKUPDESTination=TSM|LOCALUse the /backupdestination parameter to specify the location from wherethe backup is to be restored. The default is the value (if present) specifiedin the Data Protection for Exchange preferences file (tdpexc.cfg). If novalue is present, the backup is restored from Tivoli Storage Manager serverstorage.You can specify:TSM The backup is restored from Tivoli Storage Manager server storage.This is the default if no value is specified in the Data Protection forExchange preferences file (tdpexc.cfg).LOCALThe backup is restored from the local shadow volumes./BACKUPMETHod=LEGACY|VSSUse the /backupmethod parameter to specify the manner in which therestore is performed. The default is the value (if present) specified in theData Protection for Exchange preferences file (tdpexc.cfg). If no value ispresent, the backup is restored with the legacy API.You can specify:LEGACYThe restore is performed with the legacy API. This is the default ifno value is specified in the Data Protection for Exchangepreferences file (tdpexc.cfg).VSS The restore is performed with VSS./BUFFers=numbuffersUse the /buffers parameter to specify the number of data buffers used for88 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialmoving data between the Exchange Server and the Tivoli Storage ManagerAPI during Legacy restore operations. Separate, asynchronous executionthreads are used by Data Protection for Exchange for communicating withthe Exchange Server and Tivoli Storage Manager APIs. Increasing thenumber of data buffers improves throughput by reducing the possibility ofone thread having to wait for another thread.The numbuffers variable refers to the number of data buffers to use. Thenumber of data buffers can be from 2 to 8. The default number of databuffers is 3./BUFFERSIze=buffersizeUse the /buffersize parameter to specify the size of data buffers used tomove data between the Exchange Server and the Tivoli Storage ManagerAPI during Legacy backup and restore operations.The buffersize variable refers to the size of the data buffers in kilobytes. Thesize of the data buffers can be from 64 to 8192 kilobytes. The default sizeof the data buffers is 1024 kilobytes./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg./EXCAPPlication=SRSUse the /excapplication parameter to specify the name of the SRS databaseto be restored. Specify SRS for the Site Replication Service database to berestored. If no value is specified, Data Protection for Exchange restores theInformation Store database./EXCSERVer=server-nameUse the /excserver parameter to specify the name of the Exchange Serverto restore to.The server-name variable specifies the name of the Exchange Server to berestored to.Considerationsv If the Exchange Server to be restored is a member of a Microsoft ClusterServer, this parameter must be specified and must be set to the name ofthe Exchange virtual server.v The default value is the local Exchange Server.Chapter 5. Using the Command Line Interface 89

IBM Confidential|||||||||||||||||/FROMEXCSERVer=server-nameUse the /fromexcserver parameter to specify the name of the ExchangeServer where the original backup was performed.The default is the local Exchange Server. However, you must specify thename if the Exchange Server is not the default or is a member of a MSCSor VCS./INSTANTRESTORE=Yes|NoUse the /instantrestore parameter to specify whether to use volume levelsnapshot or file level copy to restore a VSS Backup that resides on localshadow volumes. Note that a SAN Volume Controller, DS6000, or DS8000storage subsystem is required to perform VSS Instant Restores.You can specify:Yes Use volume level snapshot restore for a VSS Backup that resideson local shadow volumes if the backup exists on volumes thatsupport it. This is the default.No Use file level copy to restore the files from a VSS Backup thatresides on local shadow volumes. Note that bypassingvolume-level copy means that Exchange database files, log files,and the checkpoint file are the only data overwritten on the sourcevolumes./INTOSG=into-sg-nameUse the /intosg parameter to specify the name of the Exchange Server 2007storage group into which the VSS Backup will be restored. The storagegroup name must be specified with the into-sg-name variable. Thisparameter requires that the name of the storage group into which the VSSBackup will be restored must also be specified with the tdpexcc restorepositional parameter, sg-name. For example, if STG1 is the name of thestorage group into which the VSS Backup will be restored, the commandline entry would be as follows:TDPEXCC RESTore STG1 FULL /INTOSG=STG1 /BACKUPMETHod=vss /BACKUPDESTination=localConsiderationsv There is no default value.v In order to restore into the Recovery Storage Group (RSG), the RSGmust already exist (with the databases to be restored already added to it)before attempting the restore operation.v Note that VSS restores to the Recovery Storage Group are NOTsupported by Microsoft with Exchange Server 2003./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. Thelogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"90 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialIf the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting./MOUNTDAtabases=No|YesUse the /mountdatabases parameter to specify whether to mount thedatabases after the restore operation completes. You MUST specify one ofthe following values:Yes Mount the databases after the restore operation completes.No Do not mount the databases after the restore operation completes.This is the default./MOUNTWait=Yes|NoIf the Tivoli Storage Manager server is configured to store the backup dataon removable media (such as tapes), then it is possible that the TivoliStorage Manager server might indicate to Data Protection for Exchangethat it is waiting for a required storage volume to be mounted. If thatoccurs, this parameter allows you to specify whether Data Protection forExchange should wait for the media mount or stop the current operation.You can specify:Yes Wait for tape mounts. This is the default.No Do not wait for tape mounts./OBJect=object-nameUse the /object parameter to specify the name of the backup object youChapter 5. Using the Command Line Interface 91

IBM Confidentialwant to restore. The object name uniquely identifies each backup objectand is created by Data Protection for Exchange.Use the Data Protection for Exchange query tsm command to view thenames of the backup objects.If the tdpexcc restore sgname incr command is entered (without the/object parameter) to restore multiple active incremental backups, allmultiple active incremental backups are restored sequentially. The /objectparameter is used to restore only one incremental backup at a time./PARTial=dbname1,dbnameNUse the /partial parameter to specify that only the named databases(dbname1,dbnameN) within the full or copy backup should be restored.Considerationsv If you specify this option, you must include at least one valid databasename.v If you do not specify this option, all databases within the backup arerestored.v You cannot specify this parameter while using VSS Instant Restore. Youmust restore ALL databases within the specified storage group whenperforming a VSS Instant Restore. Although Data Protection forExchange allows this operation to begin, it will either fail or completewith undesirable consequences. If you need to restore just one databasefrom a VSS Backup that resides on local VSS shadow volumes on DS orSAN Volume Controller disks, make sure to specify /instantrestore=noon the command line interface. If VSS Instant Restore capability isneeded for single databases, make sure to place these databases in theirown storage group./Quiet This parameter prevents status information from being displayed. Thisdoes not affect the level of information written to the activity log./RECOVER=APPLYRESToredlogs|APPLYALLlogsUse this parameter to specify whether or not you want to run recoveryafter you restore an object. It is recommended this parameter be specifiedon the last backup object restored for any particular storage group. Toinitiate recovery, you MUST use the /recover parameter when restoring thelast backup object of a storage group. In addition, the value of/templogrestorepath should not be the same value as the current locationfor the storage group. If the value is the same, corruption can occur.Failure to use the /recover parameter when restoring the last backup set ofa storage group leaves the databases unmountable. If this occurs, you caneither restore the last backup again and specify the /recover=value optionor you can use the Microsoft ESEUTIL /cc command to run recoverymanually.You MUST specify one of the following values when using this parameter:APPLYALLlogsSpecify /recover=applyalllogs to replay the restored transactionlog entries AND the current active transaction log entries. Anytransaction logs entries that appear in the current active transactionlog are replayed. This is the default.APPLYRESToredlogsSpecify /recover=applyrestoredlogs to replay ONLY the restoredtransaction log entries. The current active transaction log entrieswill NOT be replayed. When restoring a mailbox database to a92 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialRecovery Storage Group on Exchange Server 2003, you mustspecify /recover=applyrestoredlogs or the restore operation may fail.Note: When choosing this option for a restore, your next backupMUST be a full or copy backup.Considerationsv When restoring multiple backup objects, the /recover option should beused on the restore of the last object.Note: If you specify /recover=applyrestoredlogs when performing arestore, the next backup of the storage group MUST be a full backup./TEMPLOGRESTorepath=path-nameUse the /templogrestorepath parameter to specify the default temporarypath to use when restoring logs and patch files. For best performance, thisshould be on a different physical device than the current active logger.If the /templogrestorepath parameter is not specified, the default value isthe value specified by the TEMPLOGRESTOREPATH option in the DataProtection for Exchange configuration file. The default Data Protection forExchange configuration file is tdpexc.cfg.If the /templogrestorepath parameter is not specified and the value doesnot exist in the Data Protection for Exchange configuration file, the TEMPenvironment variable value is used.Note: When performing a full, copy, or dbcopy restore, all log filesresiding in the path specified by the /templogrestorepath parameter areerased.In addition, the value of /templogrestorepath should not be the same valueas the current location for the storage group. If the value is the same,corruption can occurNote: Do not specify double-byte characters (DBCS) within the temporarylog path. This is not supported by Data Protection for Exchange orMicrosoft./TSMNODe=tsmnodenameThe tsmnodename variable refers to the Tivoli Storage Manager node nameData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. You can also store the node name in the Tivoli Storage Manageroptions file. The command line parameter overrides the value in the TivoliStorage Manager options file if PASSWORDACCESS is set to PROMPT.This parameter is not valid when PASSWORDACCESS is set toGENERATE./TSMOPTFile=tsmoptfilenameThe tsmoptfilename variable identifies the Data Protection for Exchangeoptions file.The file name can include a fully qualified path name. If no path isspecified, the directory where Data Protection for Exchange is installed issearched.If the tsmoptfilename variable includes spaces, the entire /tsmoptfileparameter entry must be placed in double quotes. For example:/TSMOPTFile="c:\Program Files\file.opt"Chapter 5. Using the Command Line Interface 93

IBM ConfidentialThe default is dsm.opt./TSMPassword=tsmpasswordThe tsmpassword variable refers to the Tivoli Storage Manager passwordData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. If you specified PASSWORDACCESS GENERATE in the DataProtection for Exchange options file, then the password need not beprovided here because the one stored in the registry is used. However, inorder to store the password in the registry, you must specify the TivoliStorage Manager password the first time Data Protection for Exchangeconnects to the Tivoli Storage Manager server.If you do specify a password on the command line whenPASSWORDACCESS GENERATE is in effect, then the command line valueis ignored unless the password for this node has not yet been stored in theregistry. In that case, the specified password is the one that is stored in theregistry and used for the current command execution.If PASSWORDACCESS PROMPT is in effect, and a password value is notspecified on the command line, then you are prompted for a password.The Tivoli Storage Manager password Data Protection for Exchange uses tolog on to the Tivoli Storage Manager server can be up to 63 characters inlength.Restore Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the restore command.The tdpexcc restore sg3.sg3 full /recover=applyalllogs command restores a fulltype backup of the Exchange Server storage group identified as sg3.sg3, andreplays the restored transaction log entries AND the current active transaction logentries. An example of the output is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Starting Microsoft Exchange restore...Logging on to the Tivoli Storage Manager server, please wait...Beginning full restore of storage group sg3.sg3 ,1 of 1, to sg3.sg3Full: 1 Read: 26314796 Written: 26314796 Rate: 3,589.11 Kb/SecRestore of sg3.sg3 completed successfully.Total backups inspected: 1Total backups requested for restore: 1Total backups restored: 1Throughput rate: 1,054.11 Kb/SecTotal bytes transferred: 26,314,796Elapsed processing time: 24.38 SecsRestore Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the restore command.94 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialThe tdpexcc restore sg3.sg3 dbcopy ″A Public Store″/recover=applyalllogscommand restores a database copy backup of ExchangeServer database A Public Store, located in storage group sg3.sg3, and replays therestored transaction log entries AND the current active transaction log entries. Anexample of the output is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Starting Microsoft Exchange restore...Logging on to the Tivoli Storage Manager server, please wait...Beginning dbcopy restore of storage group sg3.sg3 ,1 of 1, to sg3.sg3Full: 1 Read: 10511010 Written: 10511010 Rate: 4,015.91 Kb/SecRestore of sg3.sg3 completed successfully.Total backups inspected: 1Total backups requested for restore: 1Total backups restored: 1Throughput rate: 1,024.52 Kb/SecTotal bytes transferred: 10,511,010Elapsed processing time: 10.02 SecsRestore Example 3This output example provides a sample of the text, messages, and process statusthat displays when using the restore command.The tdpexcc restore stg2 full /backupdestination=tsm /backupmethod=vsscommand restores a full VSS Backup of Exchange Server 2003 storage group stg2from Tivoli Storage Manager server storage to local shadow volumes. An exampleof the output is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Connecting to TSM Server as node ’SVC_TDP’...Connecting to Local DSM Agent ’svc_ba’...Beginning VSS restore of ’stg2’...Files Examined/Completed/Failed: [ 14 / 14 / 0 ] Total Bytes: 88135694VSS Restore operation completed with rc = 0Files Examined : 14Files Completed : 14Files Failed : 0Total Bytes : 88135694Restore Example 4This output example provides a sample of the text, messages, and process statusthat displays when using the restore command.The tdpexcc restore stg4 full /backupdestination=local /backupmethod=vsscommand restores a full VSS Backup of Exchange Server 2003 storage group stg4from local shadow volumes. An example of the output is displayed below.Chapter 5. Using the Command Line Interface 95

IBM ConfidentialIBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Connecting to TSM Server as node ’TDP_REAL’...Connecting to Local DSM Agent ’ba_real’...Starting Microsoft Exchange restore...Beginning VSS restore of ’stg4’...VSS Restore operation completed with rc = 0Files Examined : 7Files Completed : 7Files Failed : 0Total Bytes : 0RestorefilescommandUse this command to restore the .edb, .stm, and .log files from a specified DataProtection for Exchange backup (that resides on Tivoli Storage Manager serverstorage) into a specified directory. Note the following information about thiscommand:v This command applies to Legacy backups only. It does not apply to VSSBackups.v The restore operation will fail if previous restore files exist.v This command does not restore the data to the Exchange Server.v This command does not require an Exchange Server to be installed on oraccessible from the machine where the restorefiles command is issued. As aresult, files can be restored to an alternative machine or to an alternativedirectory on the same machine as the Exchange Server.v This command also restores the Site Replication Service (SRS) files. Use the/excapplication parameter when restoring these files.v When restoring files from an inactive backup or an active incremental backup,use the /object parameter to specify the name of the backup object. The objectname uniquely identifies the backup instance in Tivoli Storage Manager serverstorage. A list of backup object names is obtained by issuing the query tsmcommand.v This command is only available on the command line interface. It is notavailable in the Data Protection for Exchange GUI.Data Protection for Exchange supports the following types of restores using therestorefiles command:Full Restore the files from a Full type backup.Copy Restore the files from a Copy type backup.IncrementalRestore the files from an Incremental type backup.DifferentialRestore the files from a Differential type backup.Database copyRestore the files from a Database Copy type backup.96 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialRestorefilessyntaxUse the restorefiles command syntax diagrams as a reference to view availableoptions and truncation requirements.►► TDPEXCC RESTOREFIles * FULLsg-name,sg-nameNCOPYINCRementalDIFFerentialDBCopy db-name►►/BUFFers=3numbuffers/BUFFERSIze=1024buffersize►►/CONFIGfile=tdpexc.cfgconfigfilename/EXCAPPlication=SRS►►/FROMEXCSERVer=local machine nameserver-name/INTO=currentpathpath►►/LOGFile=tdpexc.loglogfilename/LOGPrune=60numdaysNo►►/MOUNTWait=YesNo/OFFLOAD►►/OBJect=current backup objectobject-name/PARTial= dbname1, dbnameN►►/Quiet /SKIPINTEGRITYCHECK /TSMNODe= tsmnodename►►/TSMOPTFile=dsm.opttsmoptfilename/TSMPassword=tsmpassword►◄Restorefiles positional parametersPositional parameters immediately follow the restorefiles command and precedethe optional parameters.The following positional parameters specify the object to restore:* | sg-name* Restore all storage group files sequentially.Chapter 5. Using the Command Line Interface 97

IBM Confidentialsg-nameRestore the specified storage group files. Multiple entries areseparated by commas. If any storage group contains commas orblanks, enclose the storage group name in quotes.The following positional parameters specify the type of backup from which thefiles are restored:FULL | COPY | INCRemental | DIFFerential | DBCopy db-nameFULL Restore the files from a Full type backup.COPY Restore the files from a Copy type backup.INCRementalRestore the files from an Incremental type backup.DIFFerentialRestore the files from a Differential type backup.DBCopy db-nameRestore the files from the db-name database copy backup.Restorefiles optional parametersOptional parameters follow the restorefiles command and positional parameters./BUFFers=numbuffersUse the /buffers parameter to specify the number of data buffers used forretrieving data from the Tivoli Storage Manager API.The numbuffers variable refers to the number of data buffers to use. Thenumber of data buffers can be from 2 to 8. The default number of databuffers is 3./BUFFERSIze=buffersizeUse the /buffersize parameter to specify the size of data buffers used toretrieve data from the Tivoli Storage Manager API.The buffersize variable refers to the size of the data buffers in kilobytes. Thesize of the data buffers can be from 64 to 8192 kilobytes. The default sizeof the data buffers is 1024 kilobytes./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg.98 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential/EXCAPPlication=SRSUse the /excapplication parameter to specify the name of the SRS databasefrom which files will be restored. Specify SRS for the Site ReplicationService database files to be restored. If no value is specified, DataProtection for Exchange restores the Information Store database files./FROMEXCSERVer=server-nameUse the /fromexcserver parameter to specify the name of the ExchangeServer where the original backup was performed. The default is the localmachine name./INTO=pathnameUse the /into parameter to specify the root directory where files are to berestored. The restorefiles operation creates a subdirectory under the rootdirectory that contains the name of the storage group. Restored files areplaced in that subdirectory. If the /into parameter is not specified, the fileswill be restored into directory from which the restorefiles command isissued. For example, if Data Protection for Exchange is installed in thec:\Program Files\Tivoli\TSM\TDPExchange directory and the followingcommand is issued from the E:\Somedir location: e:\Somedir>c:\″Program Files″\Tivoli\TSM\TDPExchange\tdpexcc restorefilesThirdSG full, then the files are restored to the subdirectories in thee:\Somdir location:e:\Somedir\ThirdSG\DB3_1.edbe:\Somedir\ThirdSG\DB3_1.stme:\Somedir\ThirdSG\E0200001.log/LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. Thelogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.When using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents theChapter 5. Using the Command Line Interface 99

IBM Confidentialnumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting./MOUNTWait=Yes|NoIf the Tivoli Storage Manager server is configured to store the backup dataon removable media (such as tapes), then it is possible that the TivoliStorage Manager server might indicate to Data Protection for Exchangethat it is waiting for a required storage volume to be mounted. If thatoccurs, this parameter allows you to specify whether Data Protection forExchange should wait for the media mount or stop the current operation.You can specify:Yes Wait for tape mounts. This is the default.No Do not wait for tape mounts./OBJect=object-nameUse the /object parameter to specify the name of the backup object filesyou want to restore. The object name uniquely identifies each backupobject and is created by Data Protection for Exchange.Use the Data Protection for Exchange query tsm command to view thenames of the backup objects.If the tdpexcc restore sgname incr command is entered (without the /objectparameter), all multiple active incremental backup files are restoredsequentially. The /object parameter is used to restore files from only oneincremental backup at a time./PARTial=dbname1,dbnameNUse the /partial parameter to specify that only files from the nameddatabases (dbname1,dbnameN) within the full or copy backup should berestored into the alternative directory.Considerationsv If you specify the /partial parameter, you must include at least one validdatabase name.v If you do not specify the /partial parameter, all files within the backupare restored./Quiet This parameter prevents status information from being displayed. Thisdoes not affect the level of information written to the activity log./TSMNODe=tsmnodenameThe tsmnodename variable refers to the Tivoli Storage Manager node nameData Protection for Exchange uses to log on to the Tivoli Storage Manager100 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialserver. You can also store the node name in the Tivoli Storage Manageroptions file. The command line parameter overrides the value in the TivoliStorage Manager options file if PASSWORDACCESS is set to PROMPT.This parameter is not valid when PASSWORDACCESS is set toGENERATE./TSMOPTFile=tsmoptfilenameThe tsmoptfilename variable identifies the Data Protection for Exchangeoptions file.The file name can include a fully qualified path name. If no path isspecified, the directory where Data Protection for Exchange is installed issearched.If the tsmoptfilename variable includes spaces, the entire /tsmoptfileparameter entry must be placed in double quotes. For example:/TSMOPTFile="c:\Program Files\file.opt"The default is dsm.opt./TSMPassword=tsmpasswordThe tsmpassword variable refers to the Tivoli Storage Manager passwordData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. If you specified PASSWORDACCESS GENERATE in the DataProtection for Exchange options file, then the password need not beprovided here because the one stored in the registry is used. However, inorder to store the password in the registry, you must specify the TivoliStorage Manager password the first time Data Protection for Exchangeconnects to the Tivoli Storage Manager server.If you do specify a password on the command line whenPASSWORDACCESS GENERATE is in effect, then the command line valueis ignored unless the password for this node has not yet been stored in theregistry. In that case, the specified password is the one that is stored in theregistry and used for the current command execution.If PASSWORDACCESS PROMPT is in effect, and a password value is notspecified on the command line, then you are prompted for a password.The Tivoli Storage Manager password Data Protection for Exchange uses tolog on to the Tivoli Storage Manager server can be up to 63 characters inlength.Restorefiles Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the restorefiles command.This command, tdpexcc restorefiles Finance COPY /INTO=e:\test/FROMEXCSERVER=excsrv12 /TSMNODE=excsrv12/TSMPASSWORD=password, restores backup files from a COPY type backup ofthe Finance storage group (from the Exchange Server 2003 named excsrv12) into thee:\test directory. The restored files are:e:\test\Finance\E0000011.loge:\test\Finance\E0000012.loge:\test\Finance\MB1.edbe:\test\Finance\MB1.stme:\test\Finance\MB2.edbe:\test\Finance\MB2.stme:\test\Finance\MB3.edbe:\test\Finance\MB3.stmChapter 5. Using the Command Line Interface 101

Restorefiles Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the restorefiles command.This command, tdpexcc restorefiles FSG FULL /PARTIAL=Mailbox2/INTO=e:\test /FROMEXCSERVER=excsrv05 /TSMNODE=excsrv05/TSMPASSWORD=password, restores Mailbox2 backup files from a FULL typebackup of the FSG storage group (from the Exchange Server named excsrv05) intothe e:\test directory. The restored files are:e:\test\FSG\E0000029.loge:\test\FSG\E000002A.loge:\test\FSG\Mailbox2.edbe:\test\FSG\Mailbox2.stmRestorefiles Example 3This output example provides a sample of the text, messages, and process statusthat displays when using the restorefiles command.First, this command, tdpexcc q tsm * /all /FROMEXCSERVER=EXCH1, queries theTivoli Storage Manager server for all active and inactive backups that wereoriginally backed up from the Exchange Server named EXCH1. The commanddisplays the following backup objects:IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Querying Tivoli Storage Manager server for a list of databasebackups, please wait...Backup List-----------Exchange Server : EXCH1Storage Group : Second Storage GroupBackup Date Size S Fmt Type Loc Object Name/Database Name------------------- ----------- - ---- ---- --- -------------------------02/14/2006 14:01:19 2,940.06MB A Lgcy full Srv 200602141401192,003.02MBmailbox_jie924.02MB Second Mail Store8,212.39KB Second Public Store5,120.09KBLogs02/14/2006 14:24:59 2,950.05MB A VSS full Loc 2006021414245915.01MBLogs8,208.00KB Second Public Store924.02MB Second Mail Store2,003.02MBmailbox_jieSecond, this command, tdpexcc restorefiles ″Second Storage Group″ FULL/OBJECT=20060214140119 /INTO=c:\test /FROMEXCSERVER=EXCH1/TSMNODE=tdp_geo /TSMPASSWORD=password, restores backup files of02/14/2006 14:01:19 FULL type backup of the storage group named Second StorageGroup (from the Exchange Server 2003 named EXCH1) into the e:\test directory.The command displays the following output:IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Starting Microsoft Exchange restore...102 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialLogging on to the Tivoli Storage Manager server, please wait...Beginning full restore of storage group Second Storage Group ,1 of 1, to Second Storage GroupFull: 2 Read: 2327880532 Written: 2325783380 Rate: 2,475.62 Kb/SecWaiting for TSM server...Full: 0 Read: 3082876092 Written: 3082876092 Rate: 2,475.36 Kb/SecRestore of Second Storage Group completed successfully.Total backups inspected: 1Total backups requested for restore: 1Total backups restored: 1Throughput rate: 2,475.36 Kb/SecTotal bytes transferred: 3,082,876,092Elapsed processing time: 1,216.24 SecsChangetsmpasswordcommandUse this command to change the Tivoli Storage Manager password used by DataProtection for Exchange to log on to the Tivoli Storage Manager server. If you donot enter the old and new passwords, Data Protection for Exchange prompts youfor the old and new passwords. Data Protection for Exchange does not display thepassword on the screen.The Tivoli Storage Manager password Data Protection for Exchange uses to log onto the Tivoli Storage Manager server can be up to 63 characters in length.ChangetsmpasswordsyntaxUse the changetsmpassword command syntax diagrams as a reference to viewavailable options and truncation requirements.►► TDPEXCC ►► CHANGETSMPasswordoldpasswordnewpasswordverifypassword►►/CONFIGfile=tdpexc.cfgconfigfilename/LOGFile=tdpexc.loglogfilename►►/LOGPrune=60numdaysNo/SKIPINTEGRITYCHECK►►/TSMNODe= tsmnodename dsm.opt/TSMOPTFile=tsmoptfilename►◄Changetsmpassword positional parametersPositional parameters immediately follow the changetsmpassword command andprecede the optional parameters.The following positional parameters specify required password information:Chapter 5. Using the Command Line Interface 103

IBM Confidentialoldpassword newpassword verifypasswordoldpasswordSpecifies the current password used by Data Protection forExchange.newpasswordSpecifies the new password used by Data Protection for Exchange.verifypasswordSpecifies the new password again for verification.If any of these values are not entered during a command invocation, you areprompted for them.Changetsmpassword optional parametersOptional parameters follow the changetsmpassword command and positionalparameters./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file that contains the values for the DataProtection for Exchange configuration options. See “Set command” on page106 for details about the contents of the file.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.Considerationsv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes. For example:/CONFIGfile="c:\Program Files\file.cfg"v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg./LOGFile=logfilenameUse the /logfile parameter to specify the name of the activity log filegenerated by Data Protection 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 thespecified log file exists, new log entries are appended to the file. Thelogfilename variable can include a fully-qualified path. However, if no pathis specified, the log file is written to the Data Protection for Exchangeinstallation directory.If the logfilename variable includes spaces, the entire /logfile parameterentry must be placed in double quotes. For example:/LOGFile="c:\Program Files\mytdpexchange.log"If the /logfile parameter is not specified, log records are written to thedefault log file, tdpexc.log.The /logfile parameter cannot be turned off. You always get logging.104 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialWhen using multiple simultaneous instances of Data Protection forExchange to perform operations, use the /logfile parameter to specify adifferent log file for each instance used. This directs logging for eachinstance to a different log file and prevents interspersed log file records.Failure to specify a different log file for each instance can result inunreadable log files./LOGPrune=numdays|NoUse the /logprune parameter to disable log pruning or to explicitly requesta prune of the log for one command run. By default, log pruning isenabled and performed once per day. The numdays variable represents thenumber of days to save log entries. By default, 60 days of log entries aresaved in the prune process. You can use the Data Protection for ExchangeGUI or the set command to change the defaults so that log pruning isdisabled, or so that more or less days of log entries are saved. Thecommand line user may use the /logprune parameter to override thesedefaults for one command run. Note that when the value of the /logprunevariable numdays is a number in the range 0 to 9999, a prune is performedeven if one has already been performed for the day.Changes to the value of the timeformat or dateformat parameter can resultin an undesired pruning of the Data Protection for Exchange log file. If youare running a command that may prune the log file and the value of thetimeformat or dateformat parameter has changed, perform one of thefollowing to prevent undesired pruning of the log file:v Make a copy of the existing log file.v Specify a new log file with the /logfile parameter or logfile setting./TSMNODe=tsmnodenameThe tsmnodename variable refers to the Tivoli Storage Manager node nameData Protection for Exchange uses to log on to the Tivoli Storage Managerserver. You can also store the node name in the Tivoli Storage Manageroptions file. The command line parameter overrides the value in the TivoliStorage Manager options file if PASSWORDACCESS is set to PROMPT.This parameter is not valid when PASSWORDACCESS is set toGENERATE./TSMOPTFile=tsmoptfilenameThe tsmoptfilename variable identifies the Data Protection for Exchangeoptions file.The file name can include a fully qualified path name. If no path isspecified, the directory where Data Protection for Exchange is installed issearched.If the tsmoptfilename variable includes spaces, the entire /tsmoptfileparameter entry must be placed in double quotes. For example:/TSMOPTFile="c:\Program Files\file.opt"The default is dsm.opt.ChangetsmpasswordExampleThese output example provides a sample of the text, messages, and process statusthat displays when using the changetsmpassword command.The tdpexcc changetsmpassword oldpw newpw newpw command changes theTivoli Storage Manager password used by Data Protection for Exchange. Anexample of the output is displayed below.Chapter 5. Using the Command Line Interface 105

IBM ConfidentialIBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.ACN0260I Password successfully changed.SetcommandUse this command to set the Data Protection for Exchange configurationparameters defined in the Data Protection for Exchange configuration file,tdpexc.cfg by default.The value of a configuration parameter specified on a command line invocationoverrides (but does not change) the value of the configuration parameter specifiedin the Data Protection for Exchange configuration file.During a command line invocation that does not specify an overriding value for aconfiguration file parameter, the values in the default Data Protection for Exchangeconfiguration file (tdpexc.cfg) are used.SetsyntaxUse the set command syntax diagrams as a reference to view available options andtruncation requirements.|►►TSMTDPEXCC SET BACKUPDESTINATION=LOCALBOTHLEGACYBACKUPMETHOD= VSSBUFFers= numbuffersBUFFERSIze= buffersizeDATEformat= dateformatnumLANGuage= languageLOCALDSMAGENTNODE= nodenameLOGFile= logfilenamenumdaysLOGPrune= NOYesMOUNTWait= NoNUMBERformat= numformatnumREMOTEDSMAGENTNODE= nodename4RETRies=numTEMPLOGRestorepath= pathTIMEformat= timeformatnum/CONFIGfile=tdpexc.cfgconfigfilename►◄Set positional parametersPositional parameters immediately follow the set command and precede theoptional parameters.The following positional parameters specify the values in the Data Protection forExchange configuration file. You can set only one value for each tdpexcc setcommand run:BACKUPDESTination=TSM|LOCAL|BOTHUse the BACKUPDESTINATION positional parameter to specify thestorage location for your backup. You can specify:106 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialTSM The backup is stored on Tivoli Storage Manager server storageonly. This is the default.LOCALThe backup is stored on local shadow volumes only.BOTH The backup is stored on both Tivoli Storage Manager serverstorage and local shadow volumes.BACKUPMETHod=Legacy|VSSUse the BACKUPMETHOD positional parameter to specify the method foryour backup. You can specify:LEGACYData Protection for Exchange uses the legacy API to perform thebackup. This is the default.VSS Data Protection for Exchange uses VSS to perform the backup.BUFFers=numbuffersUse the BUFFers positional parameter to specify the number of databuffers used for moving data between the Exchange Server and the TivoliStorage Manager API. Increasing the number of data buffers can improvethroughput. You can specify a value of 2 through 8 in the numbuffers value.BUFFERSIze=buffersizeUse the BUFFERSIze positional parameter to specify the size of databuffers used to move data between the Exchange Server and the TivoliStorage Manager API.The buffersize variable refers to the size of the data buffers in kilobytes. Thesize of the data buffers can be from 64 to 8192 kilobytes. The default sizeof the data buffers is 1024 kilobytes.DATEformat=dateformatnumUse the DATEformat positional parameter to select the format you want touse to display dates.The dateformatnum variable displays the date in one of the followingformats. Select the format number that corresponds to the format you wantto use.1 MM/DD/YYYY. This is the default.2 DD-MM-YYYY.3 YYYY-MM-DD.4 DD.MM.YYYY.5 YYYY.MM.DD.Changes to the value of the dateformat parameter can result in anundesired pruning of the Data Protection for Exchange log file (tdpexc.logby default). You can avoid losing existing log file data by performing oneof the following:v After changing the value of the dateformat parameter, make a copy ofthe existing log file before running Data Protection for Exchange.v Specify a new log file with the /logfile parameter.LANGuage=languageSpecify the three-character code of the language you want to use to displaymessages:Chapter 5. Using the Command Line Interface 107

IBM ConfidentialCHS Simplified ChineseCHT Traditional ChineseDEU Standard GermanENU American English (This is the default.)ESP Standard SpanishFRA Standard FrenchITA Standard ItalianJPN JapaneseKOR KoreanPTB Brazilian PortugueseLOCALDSMAgentnode=nodenameSpecify the node name of the local machine that performs the VSSbackups. This positional parameter must be specified for VSS operations tobe performed.LOGFile=logfilenameUse the LOGFile positional parameter to specify the name of the activitylog file generated by Data Protection for Exchange. The Data Protection forExchange activity log records significant events, such as completedcommands and error messages.The logfilename variable identifies the name of the activity log file. If thespecified log file does not exist, a new log file is created. If the specifiedlog file exists, new log entries are appended to the file. The logfilenamevariable can include a fully-qualified path. However, if no path is specified,the log file is assigned to the Data Protection for Exchange installationdirectory.LOGPrune=numdays|NoUse the LOGPrune positional parameter to disable log pruning or to setlog pruning parameters. By default, log pruning is enabled and performedonce per day. The numdays variable represents the number of days to savelog entries. You can specify a value of No or 0 through 9999. By default, 60days of log entries are saved in the prune process.MOUNTWait=Yes|NoUse the MOUNTWait positional parameter to specify whether DataProtection for Exchange should wait for removable media to mount (suchas tapes or CD-ROMs) or to stop the current operation. This situationoccurs when the Tivoli Storage Manager server is configured to storebackup data on removable media and waits for a required storage volumeto be mounted.Specify Yes for Data Protection for Exchange to wait until all initialvolumes of any required removable media are made available to the TivoliStorage Manager server before completing the command.Specify No for Data Protection for Exchange to terminate the command (ifremovable media are required). An error message will display.NUMberformat=fmtnumUse the NUMberformat positional parameter to specify the format youwant to use to display numbers.108 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialThe fmtnum variable displays numbers using one of the following formats.Select the format number that corresponds to the format you want to use.1 n,nnn.dd. This is the default.2 n,nnn,dd.3 n nnn,dd4 n nnn.dd5 n.nnn,dd6 n’nnn,ddREMOTEDSMAgentnode=nodenameSpecify the node name of the machine that moves the VSS data to TivoliStorage Manager server storage during off-loaded backups.||||RETRies=numUse the RETRies positional parameter to specify the number of times thatData Protection for Exchange will retry a failed Legacy Backup. You canspecify a value of 0 through 32 in the num value. The default value is 4.TEMPLOGRESTorepath=path-nameUse the TEMPLOGRESTorepath positional parameter to specify the defaulttemporary path to use when restoring logs and patch files. For bestperformance, the path specified in the path-name should be on a differentphysical device than the current active logger. If the path-name variableincludes spaces, the entire TEMPLOGRESTorepath positional parameterentry must be placed in double quotes. For example:TEMPLOGRESTorepath="c:\Program Files\file.log"Note: Do not specify double-byte characters (DBCS) within the temporarylog path. This is not supported by Data Protection for Exchange orMicrosoft.TIMEformat=formatnumberUse the TIMEformat positional parameter to specify the format in whichyou want system time displayed.The formatnumber variable displays time in one of the following formats.Select the format number that corresponds to the format you want to use.1 HH:MM:SS This is the default.2 HH,MM,SS3 HH.MM.SS4 HH:MM:SSA/PSet optional parametersOptional parameters follow the set command and positional parameters./CONFIGfile=configfilenameUse the /configfile parameter to specify the name of the Data Protectionfor Exchange configuration file in which these values will be set.The configfilename variable can include a fully qualified path. If theconfigfilename variable does not include a path, the Data Protection forExchange installation directory is used.ConsiderationsChapter 5. Using the Command Line Interface 109

IBM Confidentialv If the configfilename variable includes spaces, the entire /configfileparameter entry must be placed in double quotes.v If the /configfile parameter is not specified, the default value istdpexc.cfg.v If the /configfile parameter is specified but the configfilename variable isnot specified, the default value is tdpexc.cfg.SetExampleThis output example provides a sample of the text, messages, and process statusthat displays when using the set command.The tdpexcc set logfile=d:\tsm\tdpexchange\exchange.log command specifiesexchange.log, in the d:\tsm\tdpexchange directory, as the Data Protection forExchange log file instead of the default Data Protection for Exchange log file,tdpexc.log, located in the directory where Data Protection for Exchange is installed.An example of the output is displayed below.IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.ACN5054I The preference has been set successfully.HelpcommandUse this command to display help for Data Protection for Exchange commands.This command lists one or more commands and their parameters.HelpsyntaxUse the help command syntax diagrams as a reference to view available optionsand truncation requirements.►►TDPEXCC?HELP*command*subcommand►◄Help optional parametersOptional parameters follow the help command.The following optional parameters specify the help to be displayed:*|commandIdentifies the specific Data Protection for Exchange command that is to bedisplayed. If the wildcard character (*) is used, help for all Data Protectionfor Exchange commands is displayed.The valid command names are shown below:BACKupCHANGETSMPasswordHELPQueryRESToreRESTOREFIlesSET110 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential*|subcommandHelp can be displayed for commands that have several subcommands, forexample, the query command. If you do not specify a subcommand or thewildcard character (*), help for all Data Protection for Exchange querycommands is displayed.The valid subcommand names for the query command are shown below:EXCHangeTDPTSMHelp Example 1This output example provides a sample of the text, messages, and process statusthat displays when using the help command.The tdpexcc help command displays available help for Data Protection forExchange. The following output is displayed:IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.Choose from the following commands:TDPEXCC BACKup *|sgname1,...,sgnameN backuptypewhere backuptype can be:FULL|COPY|INCRemental|DIFFerential|DBCopy dbname[/BACKUPDESTination=TSM|LOCAL|BOTH] (default: TSM)[/BACKUPMETHod=LEGACY|VSS] (default: LEGACY)[/BUFFers=numbuffers] (default: 3)[/BUFFERSIze=buffersize] (default: 1024)[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/EXCAPPlication=SRS] (default: Information Store)[/EXCSERVer=servername] (default: local exchange server)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)[/MOUNTWait=Yes|No] (default: Yes)[/OFFLOAD}[/Quiet][/SKIPINTEGRITYCHECK][/TSMNODe=nodename][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)[/TSMPassword=password]TDPEXCC CHANGETSMPassword [oldpw [newpw [verifypw]]][/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)[/TSMNODe=nodename][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)TDPEXCC [ HELP|? [*|command [*|subcommand]] ]Valid command names: Valid subcommands:BACKupEXCHangeCHANGETSMPasswordTDPHELPTSMQueryRESToreRESTOREFIlesSETTDPEXCC Query EXCHange[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/EXCSERVer=servername] (default: local exchange server)Chapter 5. Using the Command Line Interface 111

IBM Confidential[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)TDPEXCC Query TDP[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)TDPEXCC Query TSM [*|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][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)[/TSMPassword=password]TDPEXCC RESTore *|sgname1,...,sgnameN backuptypewhere backuptype can be:FULL|COPY|INCRemental|DIFFerential|DBCopy dbname[/BACKUPDESTination=TSM|LOCAL] (default: TSM)[/BACKUPMETHod=LEGACY|VSS] (default: LEGACY)[/BUFFers=numbuffers] (default: 3)[/BUFFERSIze=buffersize] (default: 1024)[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/EXCAPPlication=SRS] (default: Information Store)[/EXCSERVer=servername] (default: local exchange server)[/FROMEXCSERVer=servername] (default: local exchange server)[/INSTANTRESTORE=Yes|No] (default: Yes)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)[/MOUNTDAtabases=No|Yes] (default: No)[/MOUNTWait=Yes|No] (default: Yes)[/OBJect=object] (default: current active object)[/PARTial=dbname1,..,dbnameN] (default: NONE)[/Quiet][/RECOVer=APPLYALLlogs|APPLYRESToredlogs] (default: APPLYALLlogs)[/TEMPLOGRESTorepath=pathname] (default: TEMP environment var)[/TSMNODe=nodename][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)[/TSMPassword=password]TDPEXCC RESTOREFIles *|sgname1,...,sgnameN backuptypewhere backuptype can be:FULL|COPY|INCRemental|DIFFerential|DBCopy dbname[/BUFFers=numbuffers] (default: 3)[/BUFFERSIze=buffersize] (default: 1024)[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/EXCAPPlication=SRS] (default: Information Store)[/FROMEXCSERVer=servername] (default: local exchange server)[/INTO=path] (default: current path)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)[/MOUNTWait=Yes|No] (default: Yes)[/OBJect=object] (default: current active object)[/PARTial=dbname1,..,dbnameN] (default: NONE)[/Quiet][/TSMNODe=nodename][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)[/TSMPassword=password]TDPEXCC SET PARMname=value[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)112 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialwhere PARMname and default values are:BACKUPDESTination=TSM|LOCAL|BOTHBACKUPMETHod=LEGACY|VSSBUFFers=3 (2..8)BUFFERSIze=1024 (64..8192)DATEformat=1 MM/DD/YYYY2 DD-MM-YYYY3 YYYY-MM-DD4 DD.MM.YYYY5 YYYY.MM.DDLANGuage=3-letter country codeENU American EnglishPTB Brazilian PortugueseCHS Chinese, SimplifiedCHT Chinese, TraditionalFRA Standard FrenchDEU Standard GermanITA Standard ItalianJPN JapaneseKOR KoreanESP Standard SpanishLOCALDSMAGENTNODE=nodenameLOGFile=tdpexc.log (filename)LOGPrune=60 (0..9999) | NoMOUNTWait=Yes (Yes|No)NUMberformat=1 n,nnn.dd2 n,nnn,dd3 n nnn,dd4 n nnn.dd5 n.nnn,dd6 n’nnn,ddREMOTEDSMAGENTNODE=nodenameTEMPLOGRestorepath=path (pathname)TIMEformat=1 HH:MM:SS2 HH,MM,SS3 HH.MM.SS4 HH:MM:SSA/PEXAMPLES:TDPEXCC Backup "Storage Group 1" fullTDPEXCC Query TSMHelp Example 2This output example provides a sample of the text, messages, and process statusthat displays when using the help command.The tdpexcc help query command displays available help for Data Protection forExchange query commands. The following output is displayed:IBM Tivoli Storage Manager for Mail:Data Protection for Microsoft Exchange ServerVersion 5, Release 5, Level 5.0(C) Copyright IBM Corporation 1998, 2007. All rights reserved.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)Chapter 5. Using the Command Line Interface 113

IBM ConfidentialTDPEXCC Query TDP[/CONFIGfile=tdpexc.cfg|filename] (default: tdpexc.cfg)[/LOGFile=tdpexc.log|logfilename] (default: tdpexc.log)[/LOGPrune=60|n|No] (default: 60)TDPEXCC Query TSM [*|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][/TSMOPTFile=dsm.opt|filename] (default: dsm.opt)[/TSMPassword=password]114 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialChapter 6. Using the Tivoli Storage Manager schedulerThis section demonstrates how to use the Tivoli Storage Manager scheduler withData Protection for Exchange to automate a full Legacy back up of ExchangeServer storage groups. You can automate a full backup of Exchange Server storagegroups as well. We recommend that you have the most current Tivoli StorageManager backup-archive client installed.For VSS operations, it is recommended that you set up different schedules to meetthe policy needs that are defined for your Legacy and VSS backups.Once Data Protection for Exchange has been registered to a Tivoli Storage Managerserver and installed on the Exchange Server, the procedure involves the followingsteps:1. On the Tivoli Storage Manager server:a. Define a schedule to run a Windows command file in the policy domain towhich Data Protection for Exchange is registered.b. Associate the Data Protection for Exchange node to the defined schedule.2. On the machine where Data Protection for Exchange and the Exchange Serverare installed:a. Install the Tivoli Storage Manager scheduler client as a Windows service forData Protection for Exchange. If a scheduler already exists for the regularTivoli Storage Manager backup-client, install another one for DataProtection for Exchange.b. Define a command file that contains Data Protection for Exchangecommands to perform the desired backup.c. If you are running in a cluster server environment, install the Tivoli StorageManager scheduler as a Windows service on both cluster nodes.d. If you are running in a cluster server environment, create a new clusterresource that represents the Tivoli Storage Manager scheduler. Verify thatthe cluster resource is started.e. Start the scheduler installed in step 2a (this is step 2.1 in some HTMLbrowsers).ExampleProcedureThis example assumes the following environment:v Data Protection for Exchange is registered to a Tivoli Storage Manager server:– The node name is mynode.– The password is mypassword.– The policy domain is mydomain.v The event to be scheduled:– A daily full Legacy backup of all storage groups.– The backups begin between 9:00 and 9:15 pm.v Exchange Server 2003 is installed on a Windows 2003 system.115

IBM ConfidentialOn the Tivoli Storage Manager serverYou must set up a scheduler service on the machine where the backup-archiveclient is installed before performing this procedure.1. Create a command file called c:\excfull.cmd. A sample command file(excfull.smp) is provided in the directory where Data Protection for Exchange isinstalled. This sample file contains commands necessary to perform ascheduled full Legacy backup of all Exchange Server storage groups to TivoliStorage Manager storage. You must specify COMPLETE PATHNAMES in thecommand file for all file names and non-system commands.Note: Perform the following if you are setting up the scheduler for anExchange Server running in a cluster environment:v Your command file must reside on the Exchange Server File Share. Theschedule you define on the Tivoli Storage Manager server needs to matchthis command file. In Step 1 and Step 2, the command file c:\excfull.cmdcould be x:\excfull.cmd where x is the Exchange Server File Share.v The tsmoptfile and logfile options specified in your command file mustreflect the location of the options file and log file on the Exchange Server FileShare.v The Exchange virtual server must be specified in the c:\excfull.cmd file. Usethe excserver option to specify the Exchange virtual server in the commandtext located at the end of the c:\excfull.cmd file:tdpexcc backup * full /tsmoptfile=dsm.opt /logfile=excsch.log/excserver=virtualservername>> excfull.logNote that this command text is divided on two lines to accommodate pageformatting.2. Enter the following command to define the schedule. You can enter thiscommand on the server console or from an administrative client. Theadministrative client does not have to be running on the same system as theTivoli Storage Manager server.def sched mydomain my_schedule desc="Exchange Daily Full LegacyBackup" action=command objects="c:\excfull.cmd" priority=2 starttime=21:00 duration=15 duru=minutes period=1 perunits=day dayofweek=anyNote that if there is a space in the directory specified for the object parameter,then the directory must be enclosed in two sets of quotes. For example:objects=””c:\Program Files\Tivoli\TSM\TDPEXchange\excfull.cmd"”Tivoli Storage Manager displays this message:ANR2500I Schedule MY_SCHEDULE defined in policy domain MYDOMAIN.3. Issue the following command to associate Data Protection for Exchange to thisschedule:define association mydomain my_schedule mynodeTivoli Storage Manager displays this message:ANR2510I Node MYNODE associated with schedule MY_SCHEDULE inpolicy domain MYDOMAIN.A schedule is now defined on the Tivoli Storage Manager server with thefollowing attributes:v It runs a command file called c:\excfull.cmd.v It begins at 9:00 pm.v It is performed daily and can start on any day of the week.116 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialYou can use the Tivoli Storage Manager administrative commands queryschedule and query association to confirm that the schedule and associationare set correctly.On the Exchange ServerThis section of the procedure assumes the following environment:v The Tivoli Storage Manager Backup-Archive client is installed on the ExchangeServer in the d:\Program Files\Tivoli\TSM\baclient directory.v Data Protection for Exchange is installed on the Exchange Server in thed:\Program Files\Tivoli\TSM\TDPExchange directory.v The communication options in the dsm.opt option files located in thesedirectories point to the Tivoli Storage Manager server to which the Exchangestorage groups are to be backed up.The options file that is defined for Data Protection for Exchange is used by thescheduler when validating the node and password. The options file is also usedwhen contacting the Tivoli Storage Manager server for schedule information.If this message displays:A communications error occurred connecting tothe Tivoli Storage Manager ServerThen:1. make sure the communication options in the dsm.opt file points to thecorrect Tivoli Storage Manager server.2. make sure the Tivoli Storage Manager server is running.Perform the following steps on the Exchange Server:1. Login using a Windows account that has administrative privileges.2. Open a Windows command prompt window.3. In the window, issue the following command:cd /d d:\"Program Files"\Tivoli\TSM\baclientYou must place quotation marks around the section of a directory pathnamethat contains a space (for example: d:\"Program Files"\Tivoli\TSM\baclient.You can also use the short form of a pathname by placing a tilde (~) andunique identifier after the first six characters in the pathname. An example ofthe short form of the pathname is shown below:d:\Progra~1\Tivoli\TSM\baclientNote: If a Tivoli Storage Manager scheduler is already installed on yourmachine (for the regular backups of the Windows system), you need to installanother scheduler (with a unique name) to run the schedules defined for DataProtection for Exchange. The Tivoli Storage Manager scheduler must have adifferent node name from the regular Tivoli Storage Manager backup-archiveclient.4. In the window, issue the following command:dsmcutil inst /name:"Data Protection for Exchange Scheduler"/node:mynode /password:mypassword /autostart:yes/clientdir:"d:\Program Files\Tivoli\TSM\baclient"/optfile:"d:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt"/startnow:noChapter 6. Using the Tivoli Storage Manager scheduler 117

IBM ConfidentialThe Windows ID that is used to start the scheduler service may require thatyou specify the client dsmcutil options ntdomain, ntaccount, and ntpasswordin this command.Note: If you are setting up the scheduler for an Exchange Server running in acluster environment:a. Change the /autostart option to no and add the /clusternode and/clustername options. For example:/autostart:no /clusternode:yes /clustername:your cluster nameb. Move the Exchange virtual server to the secondary node of the cluster tocreate the scheduler service. Make sure the secondary node of the clusterhas ownership of the Exchange virtual server.c. The primary node of the cluster must contain the command file on the fileshare used to create the scheduler service.d. Copy the options file (dsm.opt in the Step 4 example) to a shared driveassociated with the virtual server. For example:/optfile:"x:\dsm.opt"Tivoli Storage Manager displays this output:TSM Windows Client Service Configuration UtilityCommand Line Interface - Version 5, Release 3, Level 3.0(C) Copyright IBM Corporation, 1990, 2006, All Rights Reserved.Last Updated May 29 2005TSM Api Verison 5.3.3Command: Install TSM Client ServiceMachine: TDPEX1(Local Machine)Installing TSM Client Service:Machine : MYNODEService Name : Data Protection for Exchange SchedulerClient Directory : D:\Program Files\Tivoli\TSM\baclientAutomatic Start : yesLogon Account : LocalSystemThe service was successfully installed.Creating Registry Keys ...Updated registry value ’ImagePath’ .Updated registry value ’EventMessageFile’ .Updated registry value ’TypesSupported’ .Updated registry value ’Data Protection for Exchange Scheduler’ .Updated registry value ’ADSMClientKey’ .Updated registry value ’OptionsFile’ .Updated registry value ’EventLogging’ .Updated registry value ’ClientNodeName’.Generating registry password ...Authenticating password with Tivoli Storage Manager for node MYNODE ....Connecting to Tivoli Storage Manager via client options file’d:\Program Files\Tivoli\TSM\TDPExchange\dsm.opt’ ...Password authentication successful.The Registry password for node MYNODE has been updated .118 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialNote: If you need to make corrections after installing a service:a. Issue the following command to remove the service:dsmcutil remove /name:"Data Protection for Exchange Scheduler"b. Issue the command in Step 4 again to install a new service.Note: If you are setting up the scheduler service for an Exchange Serverrunning in a cluster environment, repeat Step 1 through Step 4 on thesecondary node of the cluster. IMPORTANT! The name of the schedulerservice created by the dsmc util command in Step 4 and the cluster servicemust have the same logon authority.5. The Tivoli Storage Manager scheduler is now installed but has not started. Tostart the scheduler IN A NON-CLUSTER ENVIRONMENT, issue the followingcommand in the Windows command prompt window:net start "Data Protection for Exchange Scheduler"This output is displayed:The Data Protection for Exchange Scheduler service is starting.The Data Protection for Exchange Scheduler service was startedsuccessfully.Note that because /autostart:yes is specified, the Tivoli Storage Managerscheduler automatically starts each time the Windows system is rebooted.Note:IMPORTANT!v If you are creating the scheduler service in a non-cluster environment,proceed directly to Step 13.v If you are creating the scheduler service in a cluster environment, performStep 6 through Step 13.The newly created scheduler service is tied to a cluster group. This allows theTivoli Storage Manager scheduler to correctly fail over between the nodes andalso manage automatic password changes.6. Start the Cluster Administrator.7. Select the Exchange Server Cluster Group and create a new Resource torepresent the Data Protection for Exchange scheduler (File–>New–>Resource).Make sure the following parameters are specified:Resource TypeSpecify Generic Service.Group Specify the Exchange Virtual Server.Possible OwnersMake sure both node machines are listed. Add them if they are notlisted.Resource DependenciesMake sure the Exchange Virtual server and the shared drives wherethe options file is located are listed.Generic Service–>Service NameSpecify the exact name of the scheduler service.For example:Name: Data Protection for Exchange SchedulerDescription: Data Protection for Exchange SchedulerResource Type: Generic ServiceGroup: MARSEXC1Chapter 6. Using the Tivoli Storage Manager scheduler 119

IBM ConfidentialDependencies: Microsoft Exchange Information Store InstanceService Name: Data Protection for Exchange Scheduler(this MUST match the name of the servicethat you installed earlier)Registry Replication: None8. Select the new resource and modify its properties. Under the RegistryReplication–>Root Registry Key parameter, add the exact key where the DataProtection for Exchange node name is listed. For example:SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\NODES\\TSMServerNameReplace with your Data Protection for Exchange node name. Forexample:SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\NODES\MYNODE\TSMServerName9. In the Windows command prompt window, change to the Data Protection forExchange installation directory.cd /d d:\"Program Files"\Tivoli\TSM\TDPExchange10. Verify that the clusternode option in the dsm.opt file is set to yes. After this isverified, enter a command that connects with the Tivoli Storage Managerserver. Specify the /tsmpassword=yourpassword parameter to ensure the correctpassword is stored in the registry. This allows the scheduler to properlyconnect automatically to the Tivoli Storage Manager server.tdpexcc query tsm /tsmpassword=mypassword11. From the Cluster Administrator, select the new resource and bring it online(File–> Bring Online).12. After the new resource is online, move the Group from the secondary node tothe primary node of the cluster. Verify that the Data Protection for Exchangescheduler service on the primary node has started.13. Your system is now ready to run the scheduled full Legacy backups of theExchange storage groups.SchedulerconsiderationsConsider the following characteristics when defining a Tivoli Storage Managerschedule:v If you are using both Legacy and VSS Backups, make sure your backupschedules do not overlap as the second backup may fail. This failure is due toExchange not allowing Legacy and VSS Backups to process at the same time.v If you want to use the Tivoli Storage Manager server-prompted schedulingmode, you must ensure that the Data Protection for Exchange option file has thetcpclientaddress and tcpclientport options specified. If you want to run morethan one scheduler service, use the same tcpclientaddress. However, you mustuse different values for tcpclientport (in addition to the different node names).An example of running more than one scheduler service is when you arescheduling Data Protection for Exchange as well as the regular Windows backupclient.Server-prompted scheduling is supported only when TCP/IP communication isbeing used. By default, Data Protection for Exchange uses the client pollingschedule mode.v If any changes that affect the scheduler are made to the Data Protection forExchange options file, the scheduler has to be restarted in order to pick up the120 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialchanges. An example of this is the Tivoli Storage Manager server address, theschedule mode, or the client TCP address or port. This can be done by issuingthe following commands:net stop "Data Protection for Exchange Scheduler"net start "Data Protection for Exchange Scheduler"Note: IMPORTANT! If you are running the scheduler service in a clusterenvironment, use the Cluster Administrator to stop and restart your schedulerservice. Do NOT use the net stop and net start commands.v The default Tivoli Storage Manager scheduler log file (dsmsched.log) containsstatus information for the Tivoli Storage Manager scheduler. In this example, thefile is located in this path:d:\Program Files\Tivoli\TSM\TDPExchange\dsmsched.logYou can override this file name by specifying the schedlogname option in theData Protection for Exchange options file.v Data Protection for Exchange creates its own log file with statistics about thebacked up storage group objects when the /logfile parameter is specified duringthe tdpexcc command. In the sample file (excfull.smp), the log file isexcsched.log. This file is different from the Tivoli Storage Manager scheduler logfile and must also be different from the file to which the tdpexcc commandoutput is redirected. In the example above, this file is excfull.log.Note: Output from scheduled commands are sent to the scheduler log file(dsmsched.log). After scheduled work is performed, check the log to ensure thework completed successfully.When a scheduled command is processed, the scheduler log might contain thefollowing entry:Scheduled event eventname completed successfullyThis is merely an indication that Tivoli Storage Manager successfully issued thescheduled command associated with the eventname. No attempt is made todetermine the success or failure of the command. You should assess the successor failure of the command by evaluating the return code from the scheduledcommand in the scheduler log. The scheduler log entry for the command’sreturn code is prefaced with the following text:Finished command. Return code is:v If passwordaccess generate is not specified in the dsm.opt file, then the TivoliStorage Manager password needs to be specified on the tdpexcc command. Tospecify the password, use the /tsmpassword parameter in the command filebeing run by the scheduler (excfull.cmd). You can also specify the password onthe Data Protection for Exchange command line. For example:tdpexcc query tsm /tsmnode=mars1 /tsmpassword=newpasswordIf you plan to perform scheduled VSS operations in a cluster environment, beaware of these considerations:v Install the Tivoli Storage Manager scheduler as a Windows service on bothcluster nodes.v If the command file resides on a local drive, you must make sure that it remainsconsistent on all cluster nodes. Optionally, you can create the command file on ashared drive. Make sure the objects parameter (specified with the defineschedule command on the Tivoli Storage Manager server) points to thiscommand file.Chapter 6. Using the Tivoli Storage Manager scheduler 121

122 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialAppendix A. Quick configuration (Legacy)Note: This Quick configuration applies to Legacy backups only. If you plan toperform VSS operations, you must follow configuration instructions provided inChapter 3, “Configuring Data Protection for Exchange,” on page 31.This section provides instructions on how to perform a quick install, configuration,and Legacy back up of a storage group using the Data Protection for ExchangeGUI on a Windows 2003 workstation running Exchange Server 2003. It minimizesset up time and allows you to proceed quickly to a state where you can beginbacking up your Exchange storage group(s). See Chapter 3, “Configuring DataProtection for Exchange,” on page 31 for detailed instructions on how to customizeData Protection for Exchange for your environment and processing needs.1. Install Data Protection for Exchange from an account that is a member of thelocal Administrators group for the machine on which the Exchange server isrunning.v Detailed installation instructions are available in “Installation procedure” onpage 29.2. In the Program Files\Tivoli\TSM\TDPExchange directory, edit this dsm.opt filewith the following options:v nodename: Specify the nodename of the machine where Data Protection forExchange is installed. This is the unique name by which the Tivoli StorageManager server recognizes your machine.v tcpserveraddress: Specify the TCP/IP address of the Tivoli Storage Managerserver to which you will back up your Exchange databases. You can specifythe address as a domain name (server.xyz.company.com) or a dot address(10.100.23.5).3. Launch the Data Protection for Exchange GUI by selectingStart–>Programs–>Tivoli Storage Manager–>Data Protection forExchange–>Exchange Client GUI. By default, the Backup window displays andLegacy Backup is selected as the backup method.4. Select the Exchange storage group(s) you want to back up in the ExchangeServer tree by clicking on the box next to the desired storage group(s).5. Select Full in the Backup Type drop-down menu of the Backup window.6. Click the Backup button to start the backup process. Enter the Tivoli StorageManager password provided by your Tivoli Storage Manager administratorwhen prompted. A Backup Progress panel displays that shows the progress ofyour backup.7. When the backup is complete, click the OK button to return to the Backupwindow.8. Exit the GUI by selecting File–>Exit in the Menu bar.At this point, Data Protection for Exchange is installed, configured, and hasperformed the initial full backup of the selected storage group(s). Review the restof this publication to become familiar with Data Protection for Exchange features,policies, procedures, and backup strategies, including VSS operations.123

124 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialAppendix B. Frequently asked questionsThis section contains information on frequently asked questions regarding DataProtection for Exchange.Can I use IBM Tivoli Storage Manager for Copy Services Version 5.4 to performa VSS Instant Restore of backups created with IBM Tivoli Storage Manager forCopy Services Version 5.3.3?On DS storage: Backups created with IBM Tivoli Storage Manager forCopy Services Version 5.3.3 on local shadow volumes that reside on DSstorage cannot be restored via VSS Instant Restore using IBM Tivoli StorageManager for Copy Services Version 5.4. You must create backups on localshadow volumes (residing on DS storage) using IBM Tivoli StorageManager for Copy Services Version 5.4 in order to restore them via VSSInstant Restore. Backups created with IBM Tivoli Storage Manager forCopy Services Version 5.3.3 on local shadow volumes (residing on DSstorage) can be restored via VSS Fast Restore using IBM Tivoli StorageManager for Copy Services Version 5.4.On SAN Volume Controller storage: Backups created with IBM TivoliStorage Manager for Copy Services Version 5.3.3 on local shadow volumesthat reside on SAN Volume Controller storage can be restored via VSSInstant Restore (and VSS Fast Restore) using IBM Tivoli Storage Managerfor Copy Services Version 5.4.See “VSS Instant Restore” on page 12 formore information.Can I perform VSS operations in a clustered Exchange Server environment?Yes, Data Protection for Exchange supports VSS operations in a clusteredExchange Server environment. See “Using VSS operations in a cluster” onpage 16 for detailed information.Why can I not perform VSS operations?The IBM Tivoli Storage Manager for Copy Services Microsoft ExchangeVSS Integration Module must be installed. See “Software and operatingsystem requirements” on page 25 detailed information.Why can I not perform VSS Instant Restore even though I have SAN VolumeController or a DS storage subsystem installed?The IBM Tivoli Storage Manager for Copy Services Hardware DevicesSnapshot Integration Module must be installed. See “Software andoperating system requirements” on page 25 for detailed information.Why is myVSS Instant Restore failing over to a VSS Fast Restore?A failover can occur if the Exchange data resides on storage subsystemsthat are not supported for VSS Instant Restore. See “VSS Instant Restore”on page 12 for information about failovers.Can I use VSS Instant Restore to restore a single database (partial restore)?You cannot perform a partial restore (/partial) while using VSS InstantRestore. You must restore ALL databases within the specified storagegroup when performing a VSS Instant Restore. Although Data Protectionfor Exchange allows this operation to begin, it will either fail or completewith undesirable consequences. If you need to restore just one databasefrom a VSS Backup that resides on local VSS shadow volumes on DS orSAN Volume Controller disks, make sure to select the Disable VSS InstantRestore option in the Data Protection for Exchange GUI Restore Window125

IBM Confidentialor specify /instantrestore=no on the command line interface. If VSS InstantRestore capability is needed for single databases, make sure to place thesedatabases in their own storage group.How can I use VSS and Legacy backups together in a common backup strategy?See “Using VSS and Legacy Backups together” on page 15 and “Back up toTivoli Storage Manager storage versus back up to local shadow volumes”on page 32 for detailed information.Can I restore Legacy backups and VSS Backups together?No, Legacy backups and VSS Backups cannot be mixed due to a Microsoftlimitation. See “Using VSS and Legacy Backups together” on page 15 formore information.Are VSS Restores restored into the Recovery Storage Group?No, VSS Restores ignore the Recovery Storage Group and are placeddirectly into the production database. This is a Microsoft limitation. See“VSS restore considerations” on page 59 for more information.Why are all my databases dismounted when I perform a VSS Restore?All databases are dismounted during VSS Restore processing due to aMicrosoft requirement.How does VSS Instant Restore work?VSS Instant Restore is a volume-level hardware-assisted copy where targetvolumes (that contain the snapshot) are copied back to the original sourcevolumes. A SAN Volume Controller, DS6000, or DS8000 storage subsystemis required to perform VSS Instant Restores. See “VSS Instant Restore” onpage 12 for more information.Now that I am performing VSS operations, why are there so many activebackups?Tivoli Storage Manager policy manages VSS Backups residing on localshadow volumes and on Tivoli Storage Manager server storage. Thisallows for different policies which can lead to an increase in the number ofactive backups. See “How Tivoli Storage Manager server policy affectsData Protection for Exchange” on page 18 and “Back up to Tivoli StorageManager storage versus back up to local shadow volumes” on page 32 formore information.Can I use dynamic disks with VSS operations?No, dynamic disks are not allowed with VSS operations. Disks that containExchange data must be configured as basic if a hardware provider is used.Can I use UNC drive letters with VSS off-loaded backups?No, Data Protection for Exchange VSS off-loaded backups will not processcorrectly if the Exchange storage group, database, or log location arespecified with UNC-based drive letters. For example, the following pathuses UNC drive letters and is not supported in a VSS off-loaded backup:\\host_srv1\c$\Program Files\Exchsrvr\First Storage GroupThe following path is specified correctly:C:\Program Files\Exchsrvr\First Storage GroupDrive-based names are supported when using a volume mount point,cluster drive, or both. For example:X:\Exch_Mount_Point\Program Files\Exchsrvr\First Storage Group126 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialHowever, UNC-based naming (as shown in the following example) is notsupported when using a volume mount point, cluster drive, or both:\\host_srv1\x$\Exch_Mount_Point\Program Files\Exchsrvr\First Storage GroupWhy do I receive a TCP/IP timeout failure when I have Windows internal VSStracing turned on?Data Protection for Exchange VSS operations may timeout with a TCP/IPfailure when Windows internal VSS tracing is turned on because of theadditional time required to write entries to the trace file. You can avoidthis issue by increasing the values for the Tivoli Storage Manager servercommtimeout and idletimeout options or by decreasing the amount ofWindows internal VSS tracing.How do I perform mailbox level backup and restore for Exchange?See BRICKBACK.DOC in the Data Protection for Exchange installationdirectory. BRICKBACK.DOC explains how to use the Microsoft ExMergeutility and the Tivoli Storage Manager Backup-Archive Client to performan item level backup and restore. Data Protection for Exchange is notinvolved with that solution.See Appendix D, “Advanced restore procedures,” on page 137 forinformation.See “Exchange 2003 Recovery Storage Group” on page 138 for information.How should I set up my policy settings for Data Protection for Exchange?See the following sections for information about Data Protection forExchange policy settings:v “How Tivoli Storage Manager server policy affects Data Protection forExchange” on page 18v “Specifying Data Protection for Exchange options” on page 39How do I perform an alternate server restore?See Appendix D, “Advanced restore procedures,” on page 137 forinformation about performing this procedure.What should my Data Protection for Exchange performance settings be?The default value of the buffers parameter (3) and the buffersize parameter(1024) have demonstrated the best performance in testing. However,environment factors such as network speed, physical database layout,machine resources, and Exchange Server resources all affect DataProtection for Exchange performance and should be considered whendetermining your settings. Note that the buffers and buffersize parametersapply to Legacy backups only.See the following sections for more information:v “Performance” on page 20v “Specifying Data Protection for Exchange options” on page 39v ″/buffers and /buffersize parameters″ (with the backup command) on“Backup optional parameters” on page 78.v ″/buffers and /buffersize parameters″ (with the restore command) on“Restore optional parameters” on page 88.v ″/buffers and /buffersize parameter″ (with the set command) on “Setpositional parameters” on page 106.Appendix B. Frequently asked questions 127

IBM ConfidentialCan I restore my Data Protection for Exchange Version 1 backups with laterversions of Data Protection for Exchange?No, you cannot restore Data Protection for Exchange Version 1 backupswith later versions of Data Protection for Exchange (versions 2.2.0, 2.2.1,5.1.5, 5.2.1, or 5.3.3). You must retain Data Protection for Exchange Version1 for as long as you maintain Version 1 backups.How do I set deleted item or deleted mailbox retention to avoid a mailbox levelbackup and restore?See Appendix D, “Advanced restore procedures,” on page 137 forinformation related to mailbox level backup and restore.How do I schedule Data Protection for Exchange backups?You can schedule Data Protection for Exchange backups by using the TivoliStorage Manager Backup-Archive client scheduler.See the following sections for more information:v Chapter 6, “Using the Tivoli Storage Manager scheduler,” on page 115v “Backup types” on page 5v “Backup strategies” on page 14What should I do if I get an "unknown Exchange API error" when running DataProtection for Exchange?See for more information about error messages.How do I set up Data Protection for Exchange to run in a cluster?The following sections contain information about using Data Protection forExchange in a cluster environment:v “Microsoft Cluster Server (MSCS) Support” on page 21v “Veritas Cluster Server (VCS) Support” on page 22v ″CLUSTERnode option″ in “Specifying Data Protection for Exchangeoptions” on page 39v “Data Protection for Exchange in a MSCS or VCS environment” on page61Make sure the user can access the universal naming convention (UNC)share name of the directory specified by the templogrestorepath option. Ifthat is not possible, specify a directory that has a valid share driveavailable and that is accessible to the user.How do I know if my backup ran successfully?A message displays that states the backup completed successfully. Inaddition, processing information is available in the following files:v Data Protection for Exchange log file (default: tdpexc.log)This file indicates the date and time of a backup, data backed up, andany error messages or completion codes.v Tivoli Storage Manager server activity logData Protection for Exchange logs information on backup and restorecommands to the Tivoli Storage Manager server activity log. A TivoliStorage Manager administrator can view this log for you if you do nothave a Tivoli Storage Manager administrator user ID and password.v Tivoli Storage Manager API error log file (default: dsierror.log)To prevent unsuccessful backups, consider the following information:128 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidential|||||||||||v Storage group databases in the Exchange Server Information Store mustbe mounted for a backup to complete successfully.v An incremental back up of an Exchange Server database can fail if aprevious full backup attempt of the same database terminatedprematurely. If you receive Data Protection for Exchange errorsACN3025E or ACN4226E, perform a full backup of the database.v A backup can fail if necessary transaction logs have been deleted ortruncated. An error message will display stating that log files or patchfiles are missing. Perform the following steps to recover from this typeof backup failure:1. Verify that only one product is performing backups on your system.2. Perform a full backup.3. If an error is still encountered, shut down and restart the ExchangeServer, then perform a full backup.4. If an error is still encountered, reboot the machine, then perform afull backup.How do the Exchange Server transaction logs get deleted?Be aware that the Exchange Server deletes transaction logs, not DataProtection for Exchange. As a result, the Exchange Server only deletes logscontaining transactions that have been committed to the Exchangedatabase. During high processing times, the Exchange Server may notdelete all the transaction logs. Thus, it is possible that log files remain afterthe Data Protection for Exchange backup completes.What do I do when this Tivoli Storage Manager server error displays: "ANR9999Dsnmode.c(xxxx): Error validating inserts etc."?You do not have to do anything as this message can be ignored. Installinga later version of Tivoli Storage Manager server will prevent this messagefrom being displayed.What authority do I need to perform a Data Protection for Exchange backup andrestore?In order to perform backup and restore tasks, Data Protection for Exchangemust be operating in an account that meets these two conditions:1. The account must be delegated with the appropriate privilege:v Exchange Server 2003: Exchange Administrator rolev Exchange Server 2007: membership in the Exchange OrganizationAdministrators group2. The account must be a member of the local Administrators group forthe machine on which the Exchange server is running.Data Protection for ExchangeShould I use the same nodename as used by my Backup-Archive client?Legacy backups: It is recommended that you use different node names tosimplify scheduling, data separation, and policy management tasks.VSS Backups: You MUST use different node names.See “Specifying Data Protection for Exchange options” on page 39 for moreinformation.How do I set up LANFree to back up Data Protection for Exchange over mySAN?Appendix B. Frequently asked questions 129

IBM ConfidentialSee “LAN Free” on page 21 for more information.Can I run Data Protection for Exchange with multiple sessions backing up?You can run separate instances of Data Protection for Exchange to back updifferent storage groups.See “Backup strategies” on page 14 for more information.Can I delete a single Data Protection for Exchange backup from the TivoliStorage Manager server based on the date that the backup was performed?No. It is not possible to delete a single Data Protection for Exchangebackup from the Tivoli Storage Manager server.130 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialAppendix C. Silent installationAdministrators can install Data Protection for Exchange using silent installation. Asilent installation runs on its own without any intervention so that administratorsare freed from the task of monitoring the installation and providing input to dialogboxes. This method is especially useful when Data Protection for Exchange mustbe installed on a number of different computers with identical hardware. Forexample, a company may have 25 Exchange Servers spread out across 25 differentsites. To ensure a consistent configuration and to avoid having 25 different peopleenter Data Protection for Exchange parameters, an administrator may choose toproduce an unattended install and make it available to the 25 sites by cutting andsending out 25 CDs or by placing the unattended install package on a file server.You can perform a silent installation using one of the following methods:SetupProgramUse the setup command with the command-line invocation and specialsilent installation options.Microsoft Installer (MSI)Use msiexec.exe to install the MSI package.The following options can be used with both silent installation methods:Table 15. Silent installation optionsOptionDescription/i Specifies the program is to install the product./l*v Specifies verbose logging./qn Runs the installation without running the external userinterface sequence./s Specifies silent mode./v Specifies the Setup Program to pass the parameterstring to the call it makes to the MSI executable(msiexec.exe). Note the following syntax requirementswhen invoking the /v option:v A backslash (\) must be placed in front of anyquotation marks (" ") that reside within existingquotation marks.v Do not include a space between the /v commandline option and its arguments.v Multiple parameters entered with the /v commandline option must be separated with a space.v You can create a log file by specifying the directoryand filename at the end of the command. Thedirectory must already exist at the time a silentinstallation is performed./x Specifies the program is to uninstall the product.addlocal Specifies features to install.allusers Specifies which users can use the installation package.installdir Specifies the directory where Data Protection forExchange is to be installed.131

IBM ConfidentialTable 15. Silent installation options (continued)OptionDescriptionreboot Specifies whether or not to prompt the user to rebootthe system after silent installation.v Force Always prompts user to reboot after silentinstallation.v Suppress Suppress prompt to reboot after silentinstallation.v ReallySuppress Suppress all reboots and prompts toreboot after silent installation.rebootyesno Specifies whether or not to reboot the system aftersilent installation. Specify Yes to reboot the systemafter silent installation. Specify No not to reboot thesystem after silent installation.transforms Specifies language to install.The following features are used in this procedure and are case sensitive:Table 16. Silent installation features (base client only)FeatureDescriptionClient Data Protection for Exchange codeDocs Data Protection for Exchange Readme and User’sGuide (HTML and PDF format)License_Paid License file (Used when PAID versions of DataProtection for Exchange are installed)License_TryBuy License file (Used when TryBuy versions of DataProtection for Exchange are installed)Table 17. Silent installation features (Language Packages only)FeatureDescriptionLanguageFiles Language specific filesTable 18. Silent installation features (IBM Tivoli Storage Manager for Copy Services MicrosoftExchange VSS Integration Module only)FeatureDescriptionPlugin IBM Tivoli Storage Manager for Copy ServicesMicrosoft Exchange VSS Integration Module (enablesbasic VSS operations)Table 19. Silent installation features (IBM Tivoli Storage Manager for Copy ServicesHardware Devices Snapshot Integration Module only)FeatureDescriptionPlugin IBM Tivoli Storage Manager for Copy ServicesHardware Devices Snapshot Integration Module(enables VSS Instant Restore operations)132 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialThe following transforms are used in this procedure:Table 20. Silent installation transformsTransformLanguage1028.mst CHT Chinese (Traditional)1029.mst CSY Czech 11031.mst DEU German1033.mst ENG English1034.mst ESP Spanish1036.mst FRA French1038.mst HUN Hungarian 11040.mst ITA Italian1041.mst JPN Japanese1042.mst KOR Korean1045.mst PLK Polish 11046.mst PTB Portuguese1049.mst RUS Russian 12052.mst CHS Chinese (Simplified)1Language support is for the following components only:v IBM Tivoli Storage Manager for Copy Services Microsoft Exchange VSSIntegration Modulev IBM Tivoli Storage Manager for Copy Services Hardware Devices SnapshotIntegration ModuleThis language support does not apply to Data Protection for Exchange.Installing with the Setup Program (setup.exe)|||Data Protection for Exchange must be installed from an account that is a memberof the local Administrators group for the machine on which the Exchange server isrunning.Note: This section shows an example of the Data Protection for Exchange silentinstallation. You must substitute the appropriate feature when installing a languageother than English. See Table 17 on page 132.Run the following command to silently install Data Protection for Exchange to thedefault installation directory:setup /s /v/qnThis example silently installs Data Protection for Exchange to a directory otherthan the default installation directory and includes custom features:setup /s /v"INSTALLDIR=\"c:\program files\tivoli\tsm\"ADDLOCAL=\"Client,License_Paid,Docs\"TRANSFORMS=1033.mst /qn /l*v \"e:\log.txt\""Note:1. You must place a backslash (\) before each quotation mark that is within anouter set of quotation marks (″).Appendix C. Silent installation 133

IBM Confidential2. You must place quotation marks (″) around the following:v A directory path that contains spaces.v An argument that specifies multiple features. Although quotation marks areneeded around the complete argument, you must still place a backslashbefore each internal quotation mark.3. All features listed in a custom installation must be listed after the addlocaloption.Creating batch filesA batch file can be created to begin silent install with desired parameters.v c:\setup.bat — sample script to demonstrate unattended installation.@echo offrem ===================================rem sample silent install scriptremsetup /s /v"INSTALLDIR=\"X:\Desired Install Path\" /qn"rem ====================================rem code could be added after therem installation completes torem customize the dsm.opt filesrem if desiredrem ====================================|||Installing with MSI (msiexec.exe)Data Protection for Exchange must be installed from an account that is a memberof the local Administrators group for the machine on which the Exchange server isrunning.Note: This section shows an example of the Data Protection for Exchange silentinstallation. You must substitute the appropriate .msi package filename andLanguage Package feature when installing a language other than English. SeeTable 17 on page 132.This example silently installs Data Protection for Exchange to a directory otherthan the default installation directory and includes custom features:msiexec /i"IBM Tivoli Storage Manager for Mail - MS Exchange.msi"RebootYesNo="No" Reboot="Suppress" ALLUSERS=1INSTALLDIR=\"c:\program files\tivoli\tsm"ADDLOCAL=\"Client,License_Paid,Docs"TRANSFORMS=1033.mst /qn /l*v "e:\log.txt"Note:1. You must place a backslash (\) before each quotation mark that is within anouter set of quotation marks (″).2. You must place quotation marks (″) around the following:v A directory path that contains spaces.v An argument that specifies multiple features. Although quotation marks areneeded around the complete argument, you must still place a backslashbefore each internal quotation mark.3. All features listed in a custom installation must be specified after the addlocaloption.134 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialInstallation problems: capturing a log of the installationIn the event of an installation failure, please record symptoms and environmentinformation for the failing install and contact customer support with thatinformation. The following environmental information may be helpful:v Operating system levelv Service packv Hardware descriptionv Install package (CD-ROM or electronic download) and levelv Any Windows event log that is relevant to the failed installv Other Windows services active at the time of the install (e.g. anti-virus software)Before contacting support, you can check for the following:v You are logged on to the local machine console (not via terminal server).v You are logged on as a local administrator, not a domain administrator.Cross-domain installs are not supported by Tivoli.Assuming that all looks correct, gather a detailed log of the failing install into a filecalled setup.log. To do this, run the setup program as follows:setup /v"/l*v setup.log"Creating the package on a cd or a file serverThe administrator has a choice of making the package available in different waysincluding burning a CD or placing the package in a shared directory on a fileserver. Typically, the package contains the Data Protection for Exchange codedistribution files and a batch file for silent install.Creating a silent install packageFirst you will need to choose a location for the package. If you are burning a CD itis convenient to use a staging directory. If you are placing the package on a fileserver you can use a staging directory or you can build the package directly on thefile server. The following example uses c:\tdpdpkg as a staging directory. It isrecommended you have a minimum of 14 MB of free space in the stagingdirectory. The following commands can be executed to create the package.CommandDescriptionmkdir c:\tdpdpkg – Create a staging directory for the silent installpackagecd /d c:\tdpdpkg – Go to the staging directoryxcopy g:\*.* . /s – Copy the Data Protection for Exchange CDdistribution files to the staging directorycopy c:\setup.bat – Replace the existing setup.bat with the one createdin the previous stepAt this point the silent install should be tested. When testing is complete thepackage can be placed on CD or it can be made available from a shared directory.Playing back the silent installationOnce the package is available on CD or from a shared directory it can be playedback (run) on another machine. Allow enough time for the unattended setup tocomplete. No visual cues exist to inform you when the installation has finished,although this could be added in the batch file.Appendix C. Silent installation 135

IBM Confidentialv From a silent install package on CD:If autostart is enabled, the silent install begins as soon as the CD is inserted intothe drive. If autostart is not enabled, the silent install can be run by executingthe setup.bat file from the root of the CD.cd /d g:\setup.batv From a distribution directory:If the package was placed in a shared directory called tdpdpkg located at\\machine1\d$, another computer could execute the command: net use x\\machine1\d$ to share the drive as drive x. The following command could thenbe issued:cd /d x:\tdpdpkgsetup.batSetup error messagesIn either case the silent install begins.The setup.exe program may produce error messages if it cannot start properly. Inmost cases you will encounter these messages when a severe error occurs. Rarelywill your end users see these messages. When you get an error message, it appearsin a message box. Every error message has a number. These are system errormessages and there is no way to suppress them in your script.If you encounter an error you can go to the InstallShield support Web site at URL:http://support.installshield.com/default.asp, and use the Search facility toobtain information on the error.136 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialAppendix D. Advanced restore proceduresData Protection for Exchange can be used to:v restore a single mailboxSee BRICKBACK.DOC in the Data Protection for Exchange installation directory.BRICKBACK.DOC explains how to use the Microsoft ExMerge utility and theTivoli Storage Manager Backup-Archive Client to perform an item level backupand restore. Data Protection for Exchange is not involved with that solution.v completely restore a server that has been destroyedv move Exchange data from an old server to a newer replacement serverNote: Please refer to your Microsoft documentation for a more completediscussion of advanced restore procedures for Exchange servers.The following procedure explains how to restore your Exchange data once the restof the machine is recovered or installed.Note: This explanation does not go into details on how to restore the entiremachine or even your Exchange Server. To back up your Windows server andconfiguration files, including the Exchange Server program and configuration files,you must rely on some other backup facility. An example of a backup facility islocated in the IBM Tivoli Storage Manager for Windows Backup-Archive ClientInstallation and User’s Guide publication.Complete Restore or ReplacementFor information on how to recover an Exchange Server 2003, see the ″ExchangeServer 2003 Disaster Recovery Operations Guide″ at the following URL:http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/disrecopgde.mspx||||For information on how to recover an Exchange Server 2007, see the MicrosoftTechNet magazine article, ″Data Protection and Disaster Recovery for ExchangeServer 2007″ at the following URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;326052Individual Mailbox RestoreFor information on how to recover an Exchange Server 2003 mailbox, see the″Exchange Server 2003 Disaster Recovery Operations Guide″ at the following URL:http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/disrecopgde.mspx||||For information on how to recover an Exchange Server 2007 mailbox, see theMicrosoft TechNet article, ″Disaster Recovery (Exchange Server 2007) at thefollowing URL: http://support.microsoft.com/default.aspx?scid=kb;enus;326278137

IBM ConfidentialExchange 2003 Recovery Storage GroupThis section describes how to restore mailbox databases using the Exchange 2003Recovery Storage Group feature. This procedure ONLY applies to Legacy restores.VSS Restores to the Recovery Storage Group are NOT supported by Microsoft.RequirementsThe following requirements must be met for this procedure to be successful:Procedurev The mailbox database to be restored can reside on any server running ExchangeServer 2003 within the same Admin group.v If you are restoring multiple mailbox stores at the same time, they all must befrom a single storage group.v You must run the restore from an account that has Receive As and Send Aspermissions on all mailboxes to be restored.v You cannot use multiple instances of Data Protection for Exchange to restoredatabases into the Recovery Storage Group simultaneously.Information regarding Recovery Storage Group processing is written to the DataProtection for Exchange activity log file (tdpexc.cfg by default).Note: When restoring to a Recovery Storage Group, you must specify the option toreplay restored logs only or the restore operation may fail. Select Replay RestoredLogs ONLY in the GUI Restore Window or specify /recover=applyrestoredlogs on thecommand line.This procedure assumes that you have already backed up your storage group.1. Use the Exchange System Manager to create the Recovery Storage Group (ifone does not already exist).2. Use the Exchange System Manager to add the mailbox database you want torestore to the Recovery Storage Group.3. Use Data Protection for Exchange to restore the mailbox database. Make surethat no public folders within the storage group are selected. By default, thedatabase is restored directly to the Recovery Storage Group. The DataProtection for Exchange GUI will display a text message to remind you that allmailbox database restores will go to the Recovery Storage Group if a RecoveryStorage Group exists.v If a Recovery Storage Group does not exist, the database is restored directlyto the original storage group.Note: Please note that only transaction logs that are contained in the backupwill be applied to the mailbox database when performing a Recovery StorageGroup restore.4. Use the Microsoft ExMerge utility to perform one of the following:v import the mailboxes to the desired storage group; orv export the desired mailboxes to external .PST files.138 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialAppendix E. Data Protection for Exchange MessagesACN0003S: An internal processing error has occurred.ExplanationAn internal processing error has occurred.System actionProcessing ends.User responseRetry the operation. If this error persists, contact your service representative.ACN0004E: An unknown error has been detected.ExplanationAn internal processing error has occurred that prevents the generation of amessage for a return code.System actionProcessing continues.User responseRetry the operation. If this error persists, contact your service representative.ACN0005E: Out of memory. Stop other processes and try the operationagain.ExplanationThe machine has run out of memory.System actionProcessing continues.User responseClose unnecessary processes and try the operation again.ACN0053E: License file (licensefile) could not be opened.ExplanationAn attempt to read from the license file failed.139

IBM ConfidentialSystem actionProcessing ends.User responseInstall the product again. This ensures that the correct license file is installed.ACN0054E: Read failure on license file (licensefile).ExplanationAn attempt was made to read from the license file. This attempt failed.System actionProcessing ends.User responseReinstall the product. This will ensure that the correct license file is installed.ACN0055E: Write failure on license file (licensefile).ExplanationAn attempt to write to the license file failed.System actionProcessing ends.User responseMake sure enough space exists on the workstation to write to the license file. Ifenough space exists, run the command again.ACN0056E: Data in the license file (licensefile) is not in a valid format.ExplanationAn attempt to read information from the license file failed.System actionProcessing ends.User responseInstall the product again.140 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN0057E: The checksum in the license file (licensefile) does notmatch the license string text.ExplanationAn attempt was made to read information from the license file. The checksum wasnot valid so it appears that the license file is not at the correct level.System actionProcessing ends.User responseReinstall the product.ACN0058E: The ’Try and Buy’ license has expired.ExplanationThis ’Try and Buy’ license that was detected has expired.System actionProcessing ends.User responseThis product is no longer valid for use. A valid license must be obtained beforerunning the product.ACN0100E: Incomplete command:ExplanationThis message displays the incomplete command that was entered.System actionProcessing ends.User responseRe-enter the complete command.ACN0101E: Invalid argument:ExplanationThis message displays the command that was entered, up to and including theinvalid command or option argument that was detected.System actionProcessing ends.Appendix E. Data Protection for Exchange Messages 141

IBM ConfidentialUser responseACN0102E: Invalid command:Re-enter the command specifying a valid argument for the command or option.ExplanationThis message displays the invalid command that was entered.System actionProcessing ends.User responseRe-enter a valid command.ACN0103E: Invalid option for the specified command:ExplanationThis message displays the command that was entered, up to and including theoption that was detected as invalid for the command.System actionProcessing ends.User responseACN0104E: Invalid option:Re-enter the command specifying valid command options.ExplanationThis message displays the command that was entered, up to and including theinvalid option that was detected.System actionProcessing ends.User responseRe-enter the command specifying valid command options.ACN0105E: Missing argument:ExplanationThis message displays the command that was entered, up to and including thecommand or option whose required argument is missing.142 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionProcessing ends.User responseRe-enter the command specifying a valid argument for the command or option.ACN0132W: Tracing could not be started. Processing will continue.ExplanationA problem prevented tracing from beginning.System actionProcessing will continue with the command entered.User responseRefer to the other messages that display with this message to determine theproblem.ACN0133W: Could not locate installation directory. Attempting tocontinue...ExplanationAn attempt was made to read the registry to determine where the Tivoli DataProtection application client was installed. This attempt failed.System actionProcessing will continue with the command entered.User responseThere should be other messages along with this one. Refer to the other messages todetermine the problem. If the problem can not be determined, it may be necessaryto reinstall the application client code. This will ensure that the registry entries areset up correctly.ACN0134W: Could not locate log directory. Processing will continue...ExplanationAn attempt was made to read the registry to determine where the Tivoli DataProtection application client log is located. This attempt failed.System actionProcessing will continue with the command entered.Appendix E. Data Protection for Exchange Messages 143

IBM ConfidentialUser responseThere should be other messages along with this one. Refer to the other messages todetermine the problem. If the problem can not be determined, it may be necessaryto reinstall the application client code. This will ensure that the registry entries areset up correctly.ACN0150I: Operation canceled by user.ExplanationThe user has requested that the Data Protection for Microsoft Exchange Serverapplication client end by entering ctrl-C.System actionProcessing ends.User responseNoneACN0151E: Errors occurred while processing the request.ExplanationAttempting to process the request entered, an error occurred.System actionProcessing ends.User responseAttempt to determine the source of the errors from viewing the log file. Correct theproblems and try running the command again.ACN0152I: Performance stats: seconds seconds spent in apicall APIcallsExplanationThe indicated number of seconds were spent making API calls for the indicatedsystem.System actionProcessing continues.User responseNone144 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN0153I: Performance stats: seconds seconds spent in functionExplanationThe indicated number of seconds were spent the named function.System actionProcessing continues.User responseNoneACN0154E: The Data Protection for Microsoft Exchange Serverapplication client cannot work with the version of the Tivoli StorageManager API you have installed. Please install versionversion.release.level or greater.ExplanationThe version of the Tivoli Storage Manager API currently installed on the system isolder than the version used to build the Data Protection for Microsoft ExchangeServer application client.System actionProcessing ends.User responseInstall a version of the Tivoli Storage Manager API at or later than the indicatedlevel. A copy is distributed with the Data Protection for Microsoft Exchange Serverapplication client.ACN0155E: The Data Protection for Microsoft Exchange Serverapplication client cannot work with the release of Tivoli StorageManager API you have installed. Please install release version.release.level or greater.ExplanationThe release of the Tivoli Storage Manager API currently installed on the system isolder than the release used to build the Data Protection for Microsoft ExchangeServer application client.System actionProcessing ends.Appendix E. Data Protection for Exchange Messages 145

IBM ConfidentialUser responseInstall a release of the Tivoli Storage Manager API at or later than the indicatedlevel. A copy is distributed with the Data Protection for Microsoft Exchange Serverapplication client.ACN0156E: Could not load the Tivoli Storage Manager API.ExplanationThe Tivoli Storage Manager API could not be loaded.System actionProcessing ends.User responseEnsure the Tivoli Storage Manager API is correctly installed. Run the DataProtection for Microsoft Exchange Server application client with the/TRACEFLAGS=API /TRACEFILE=filename options and view the tracefile todetermine why it could not be loaded. Another possible cause is that theTSMAPI.DLL does not exist in the system directory. Re-install the Tivoli StorageManager API, if this is the case.ACN0160E: An authentication error occurred with your stored TivoliStorage Manager password.ExplanationYou were unable to log on to the Tivoli Storage Manager server due anauthentication error.System actionProcessing stops.User responseThe stored Tivoli Storage Manager password may have become corrupted. Contactyour Tivoli Storage Manager server administrator.ACN0161E: Authentication error. The password entered is not valid.You are not logged on to the Tivoli Storage Manager server.ExplanationAn incorrect password was entered.System actionProcessing stops.146 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseEnter the correct Tivoli Storage Manager password and try again.ACN0162E: The passwords entered do not match. Please enter themagain.ExplanationAn incorrect password was entered.System actionProcessing stops.User responseEnter the passwords again.ACN0163E: The directory path needs to be fully-qualified.ExplanationThe /intopath option was specified without a fully-qualified path.System actionProcessing stops.User responseEnter the command again and specify a fully-qualified path in the /intopathoption.ACN0167E: The fully-qualified file name is too long.ExplanationAn attempt was made to use a fully-qualified file name that was too long. Thisattempt failed.System actionProcessing ends.User responseNoneACN0200E: File (filename) could not be opened for reading.ExplanationAn attempt was made to open a file for reading. This attempt failed.Appendix E. Data Protection for Exchange Messages 147

IBM ConfidentialSystem actionProcessing ends.User responseNoneACN0201E: File (filename) could not be opened for writing.ExplanationAn attempt was made to open a file for writing. This attempt failed.System actionProcessing ends.User responseNoneACN0202E: Read failure on file (filename).ExplanationAn attempt was made to read from a file. This attempt failed.System actionProcessing ends.User responseNoneACN0203E: Write failure on file (filename).ExplanationAn attempt was made to write to a file. This attempt failed.System actionProcessing ends.User responseNoneACN0204E: File (filename) could not be closed.ExplanationAn attempt was made to close a file. This attempt failed.148 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionProcessing ends.User responseNoneACN0205E: File (filename) statistics could not be obtained.ExplanationAn attempt was made to obtain file statistics. This attempt failed.System actionProcessing ends.User responseNoneACN0206E: Directory (directory) could not be created.ExplanationAn attempt was made to create a directory. This attempt failed.System actionProcessing ends.User responseNoneACN0207E: Directory path (directorypath) is too long.ExplanationAn attempt was made to use a directory path that was too long. This attemptfailed.System actionProcessing ends.User responseNoneAppendix E. Data Protection for Exchange Messages 149

IBM ConfidentialACN0208E: There is not enough disk space for the operationattempted.ExplanationAn attempted operation required more disk space than was available. The attemptfailed.System actionProcessing ends.User responseNoneACN0209E: The rename of file (filename1) to (filename2) failed.ExplanationAn attempt was made to rename a file. This attempt failed.System actionProcessing ends.User responseNoneACN0210E: The Tivoli Storage Manager high level qualifier is too long.ExplanationAn attempt was made to use a Tivoli Storage Manager high level qualifier that wastoo long. This attempt failed.System actionProcessing ends.User responseNoneACN0211E: The Tivoli Storage Manager low level qualifier is too long.ExplanationAn attempt was made to use a Tivoli Storage Manager low level qualifier that wastoo long. This attempt failed.System actionProcessing ends.150 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseNoneACN0212E: The Tivoli Storage Manager filespace name is too long.ExplanationAn attempt was made to use a Tivoli Storage Manager filespace name that was toolong. This attempt failed.System actionProcessing ends.User responseNoneACN0213E: The maximum number of objects allowed per TivoliStorage Manager transaction is t oo small.ExplanationIn order to maintain backup data integrity, multiple backup objects are sent to theTivoli Storage Manager server in a single transaction. The Tivoli Storage Managerserver has indicated that the maximum number of objects allowed per transactionis less than the minimum required by the Data Protection for Microsoft ExchangeServer application client.System actionProcessing ends.User responseIncrease the maximum number of objects allowed per transaction on the TivoliStorage Manager server and retry the operation.ACN0214E: The backup object’s management class backup copygroup does not exist.ExplanationThe Tivoli Storage Manager server has indicated that the backup object’smanagement class backup copy group does not exist.System actionProcessing ends.User responseContact your Tivoli Storage Manager server administrator.Appendix E. Data Protection for Exchange Messages 151

IBM ConfidentialACN0215E: All backup objects do not have the same managementclass backup copy destination.ExplanationIn order to maintain backup data integrity, multiple backup objects are sent to theTivoli Storage Manager server within a single transaction. All backup objectswithin a single transaction are required to have the same management classbackup copy destinations.System actionProcessing ends.User responseContact your Tivoli Storage Manager server administrator.ACN0216E: Unable to obtain space information for volume(volumename).ExplanationAn attempt was made to obtain space information for a volume. This attemptfailed.System actionProcessing ends.User responseNoneACN0217E: The Tivoli Storage Manager filespace name is invalid.ExplanationThe filespace name or directory delimeter is invalid.System actionProcessing ends.User responseCheck that the filespace name length, characters, and directory delimeters arevalid.ACN0218E: The Tivoli Storage Manager high level qualifier is invalid.ExplanationThe high level qualifier name or directory delimeter is invalid.152 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionProcessing ends.User responseCheck that the high level qualifier name length, characters, and directorydelimeters are valid.ACN0219E: The Tivoli Storage Manager low level qualifier is invalid.ExplanationThe low level qualifier name or directory delimeter is invalid.System actionProcessing ends.User responseCheck that the low level qualifier name length, characters, and directory delimetersare valid.ACN0256E: The password in your Tivoli Storage Manager options filehas expired. Please change your password on the Tivoli StorageManager server using the ’change password’ command and theneither change or remove the password value in your options file.ExplanationYour Tivoli Storage Manager password has expired. You need to change yourpassword.System actionProcessing ends.User responseObtain a new password for your Tivoli Storage Manager server; node using thechange password command or by asking your Tivoli Storage ManagerAdministrator to change your password.ACN0257E: Your password has expired.ExplanationYour Tivoli Storage Manager password has expired. A new password needs to beobtained.System actionProcessing ends.Appendix E. Data Protection for Exchange Messages 153

IBM ConfidentialUser responseObtain a new password for your Tivoli Storage Manager node using the changepassword command or by asking your Tivoli Storage Manager Administrator tochange your password.ACN0258E: You did not enter a valid password. Processing ends.ExplanationThe password that was entered was not a valid password.System actionProcessing ends.User responseRe-enter the command specifying a valid password.ACN0259E: The password you entered for verification does not matchthe password you entered for your new password. Your password willnot be changed.ExplanationThe password you entered for verification of your new password does not matchthe new password that was entered.System actionProcessing ends.User responseTry again to change your password being sure to enter the same password for thenew password and for the verification password.ACN0260I: Password successfully changed.ExplanationThe change password command completed successfullySystem actionProcessing ends.User responseNone154 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN0261I: There are no backups for the server named servername.ExplanationThere are no backups on the Tivoli Storage Manager server for the specified servername.System actionProcessing ends.User responseNoneACN0263E: Failed to start Web browser with a return code ofreturncode.ExplanationAn attempt was made to start the web browser to view the TSM HTML b ook.This attempt failed.System actionProcessing ends.User responseStart your web browser manually and point it to bookfrm.htm in the agent htmdirectory.ACN0264I: Could not find the default browser defined. An attempt willbe made to use Microsoft Internet Explorer.ExplanationAn attempt was made to read the registry to determine the default browser.However, a default browser is not defined. A determination will be made whereMicrosoft Internet Explorer is installed.System actionProcessing continues.User responseIt is possible that a default browser is not defined for the system. This is okay. Anattempt will be made to use Microsoft Internet Explorer.Appendix E. Data Protection for Exchange Messages 155

IBM ConfidentialACN0265E: Could not find Internet Explorer.ExplanationAn attempt was made to read the registry to determine where Microsoft’s InternetExplorer was installed. This attempt failed.System actionProcessing ends.User responseMake sure that the registry is set up correctly for Internet Explorer.ACN0266E: Could not find the Tivoli Storage Manager HTML books.ExplanationAn attempt was made to read the registry to determine where the Tivoli StorageManager books were installed. This attempt failed.System actionProcessing ends.User responseIt may be necessary to reinstall the application client code. This will ensure that theregistry entries are set up correctly.ACN0267E: The verify password entered does not match the newpassword entered.ExplanationThe verify password does not match the new password.System actionProcessing ends.User responseRetry the command with a matching verify password.ACN0300E: Invalid restore type.ExplanationThe type of restore requested is invalid.System actionProcessing ends.156 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseRe-enter the command specifying a valid restore type.ACN0301E: Invalid backup type.ExplanationThe type of backup requested is invalid.System actionProcessing ends.User responseRe-enter the command specifying a valid backup type.ACN351E: Invalid trace keyword - ’keyword’ExplanationA TRACEFLAG option in the user configuration file or on the command line isincorrect.System actionClient program did not initialize or tracing was not enabled in the applet.User responseCorrect the value.ACN357E: Unable to open trace output file file-name.ExplanationA TRACEFILE option in the user configuration file or on the command line used adirectory path and file-name combination to which you do not have write access.System actionClient program did not initialize.User responseChange the TRACEFILE value so that it is a location to which you have writeaccess.ACN366E: Unable to close trace output file file-name.ExplanationAn error occurred during the closing of a trace output file-name (for example, notenough disk space).Appendix E. Data Protection for Exchange Messages 157

IBM ConfidentialSystem actionProcessing continues.User responseCheck the options.doc file for a description of possible causes of the error, or seeyour system administrator.ACN367E: Unable to write to trace file tracefile. Tracing disabled.ExplanationAn error occurred when writing to the specified tracefile.System actionTracing is disabled. Processing continues.User responseEnsure the device that the tracefile access is available and has sufficient space forthe tracefile. Retry the command.ACN368E: Invalid trace file name (name too long).ExplanationA TRACEFILE option in the preferences files used a file name that is too long.System actionClient program did not initialize.User responseChange the file name used as the TRACEFILE so that it is equal to or less than 255characters in length.ACN383E: Specifying the trace file ’link’ as a symbolic link is notallowed.ExplanationTrace file ’linkname’ cannot be a symbolic link.System actionThe symbolic link ’linkname’ is deleted, the trace file is recreated, and processingstops.User responseSpecify the trace file location with the ’tracefile’ option.158 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN384E: Symbolic link ’linkname’ to ’target’ was successfully deleted.ExplanationLog ’linkname’ cannot be a symbolic link.System actionThe symbolic link ’linkname’ is deleted, the log is recreated, and processing stops.User responseCheck the location of the new file. To specify the location of log files, refer to theuser’s manual for the ’errorlogname’ option, the ’schedlogname’ option, and the’DSM_LOG’ environmental variable.ACN385E: Unable to delete symbolic link ’link’.ExplanationLog ’linkname’ cannot be a symbolic link.System actionProcessing stops.User responseDelete the symbolic link ’linkname’.ACN476E: program-name: cannot open file file-spec: error.ExplanationTDP cannot open the file.System actionTDP cannot complete the requested operation.User responseRetry the operation. If the problem continues, check with your systemadministrator.ACN487E: Specifying the error log ’link’ as a symbolic link is notallowed.ExplanationError log ’linkname’ cannot be a symbolic link.Appendix E. Data Protection for Exchange Messages 159

IBM ConfidentialSystem actionThe symbolic link ’linkname’ is deleted, the error log is recreated, and processingstops.User responseCheck the location of the new error log. To specify the location of the error logs,refer to the user’s manual for the ’errorlogname’ option and ’DSM_LOG’environmental variable.ACN488E: Initialization functions cannot open the error log: log-name.errno = errno-value,ExplanationThe file log-name could not be opened during initialization. The system set theerror code errno-value. If the reason given is ″access denied,″ the current user doesnot have permission to write to the log in the directory specified. It is also possiblethat no space is available at the given log location.System actionProcessing terminates.User responseSet the DSM_LOG (or DSMI_LOG) environment variable to a directory into whichthe current user can write. You may also use the ERRORLOGNAME option tospecify a file to which the current has write permission.ACN495E: Failure writing to a Tivoli Storage Manager log or log-relatedfile: file-name, errno = errno-value, reasonExplanationA failure was encountered when writing to one of the log files or a related filenamed file-name. The system set the error code errno-value. reason is the systemexplanation of that error code. Among other things, it is possible that no space isavailable at the given log location.System actionProcessing terminates.User responseSet the DSM_LOG (or DSMI_LOG) environment variable to a directory withadequate space to write the log data.160 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN496I: TDP is converting the log-file from continuous (pruning)mode to wrapping mode. This process may take several minutes.ExplanationThe log-file was previously in continouos mode where the only size control wasthrough the use of ERRORLOGRETENTION or SCHEDLOGRETENTION option.This is the first occasion where ERRORLOGMAX or SCHEDLOGMAX is specifiedfor this log, so its format must be changed and old data saved.System actionTransition processing continues.User responseNone.ACN497I: TDP is converting the log-file from wrapping mode tocontinuous (pruning) mode. This process may take several minutes.ExplanationThe log-file was previously in wrapping mode where the size control was throughthe use of the ERRORLOGMAX or SCHEDLOGMAX option. This is the firstoccasion where ERRORLOGMAX or SCHEDLOGMAX is not specified for this log,so its format must be changed and old data saved.System actionTransition processing continues.User responseNone.ACN498I: count log records processed.ExplanationThis is just a progress report to let you know the process is still ongoing.System actionTransition processing continues.User responseNone.Appendix E. Data Protection for Exchange Messages 161

IBM ConfidentialACN501E: Invalid Proxy Configuration Detected: Target Node’targetnode’ is not listed as a valid node to proxy to for Node Name’nodename’.ExplanationThe proxy node configuration on the TSM Server is not correct to support this VSSoperation.System actionThe VSS operation stops.User responseContact the TSM Server administrator to have the correct TSM Server GRANTPROXY commands issued to enable proxy authority for the nodes. If the errorpersists, contact your service representative.ACN501T: Invalid Proxy Configuration Detected: Target Node’targetnode’ is not listed as a valid node to proxy to for Node Name’nodename’.ExplanationThe proxy node configuration on the TSM Server is not correct to support this VSSoperation.System actionThe VSS operation stops.User responseContact the TSM Server administrator to have the correct TSM Server GRANTPROXY commands issued to enable proxy authority for the nodes. If the errorpersists, contact your service representative.ACN515E: Invalid DSMAGENT Node configuration found for node’dsmagentnode’.ExplanationThe DSMAGENT Node specified is not configured properly.System actionThe VSS operation stops.User responseVerify that the DSMAGENT Node specified is correct and that the Client AcceptorDaemon (CAD) is running for the DSMAGENT Node. If the error persists, contactyour service representative.162 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN516I: The Windows console event handler received a ’event’console event.ExplanationA console event was received by one of the Data Protection for Microsoft ExchangeServer processes or programs. The following events can be recevied:v Ctrl-C - This indicates either the user entered the ctrl-c sequence or that one ofthe Windows services was stopped.System actionNone.User responseNone.ACN517I: An unexpected error was encountered. TDP function name :function-name TDP function : function-desc TDP return code : TSM-rcTDP file : file-name (line-number)ExplanationNone.System actionProcessing stops.User responseContact the TDP administrator with the information provided in this message.ACN518E: Backups selected for restore must have the same backuplocation (TSM or LOCAL).ExplanationA VSS restore operation was submitted that specified multiple backup objects. Thebackup objects chosen had different backup locations. This is not allowed. Allbackup objects submitted in the same VSS restore operation must have the samebackup location, either TSM or LOCAL, but not both.System actionThe VSS restore operation stops.User responseRetry the VSS restore operation specifying one backup object at a time.Appendix E. Data Protection for Exchange Messages 163

IBM ConfidentialACN519E: The VSS operation failed with rc = returncode.ExplanationThere was a failure when TSM performed the VSS operation.System actionThe VSS operation stops.User responseVerify that the TSM Client Acceptor Daemon (CAD) is installed, configured, andrunning properly on the machine. Retry the operation. If the error persists, contactyour service representative.ACN520E: Failed to connect to Local DSMAGENT Node’localdsmagentnode’ at address:port ’address:portnumber’. Verify that theTSM Client Acceptor Daemon (CAD) is installed, configured, andrunning properly.ExplanationAn attempt was made to connect to the TSM Client Acceptor Daemon (CAD)running on the local machine. A communication error occurred when thisconnection was attempted.System actionThe operation stops.User responseIn order to perform VSS operations, you must have a TSM Client AcceptorDaemon (CAD) and a TSM Remote Client Agent Service (DSMAGENT) installedand configured properly. In addition, the TSM Client Acceptor Daemon (CAD)must be running. Verify that the TSM Client Acceptor Daemon (CAD) is installed,configured, and running properly on the local machine. If the error persists,contact your service representative.ACN521E: Pruning functions cannot open one of the Tivoli StorageManager prune files: log-name. errno = errno-value,ExplanationThe file ″log-name″ could not be opened during pruning. The system set the errorcode errno-value. If the reason given is ″access denied,″ the current user does nothave permission to write to the file in the directory specified. It is also possiblethat no space is available at the given file location or another Tivoli StoragerManager process started by different user id is performing pruning at the sametime.164 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionPruning stops, processing continues.User responseSet the DSM_LOG (or DSMI_LOG) environment variable to a directory into whichthe current user can write.ACN3500I: Data Protection for Exchange: Starting backup type backupof object name from server server name.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a backup is started.System actionNoneUser responseNone Centrally loggedACN3501I: Data Protection for Exchange: backup type backup of objectname from server server name completed successfully. bytes bytes sentin seconds seconds.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a backup completes successfully.System actionNoneUser responseNone Centrally loggedACN3502E: Data Protection for Exchange: backup type backup of objectname from server server name failed, rc = return code.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a backup fails.System actionNoneAppendix E. Data Protection for Exchange Messages 165

IBM ConfidentialUser responseNone Centrally loggedACN3503I: Data Protection for Exchange: backup type backup ofstorage group name from server server name was cancelled by the user.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a storage group backup was cancelled by the user.System actionNoneUser responseNone Centrally loggedACN3504I: Data Protection for Exchange: Starting restore for serverservername.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the start of a restore.System actionNoneUser responseNone Centrally loggedACN3505I: Data Protection for Exchange: Restore from serverservername to servername is complete. Total backups restored: Totalbytes transferred: Elapsed processing time: Secs Throughput rate:Kb/SecExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the end of a restore.System actionNoneUser responseNone Centrally logged166 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN3506I: Data Protection for Exchange: Starting backup type restoreof storage group storage group name to server server name.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the start of a storage group restore.System actionNoneUser responseNone Centrally loggedACN3507E: Data Protection for Exchange: backup type restore ofstorage group storage group name to server server name completedsuccessfully.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a storage group restore completes successfully.System actionNoneUser responseNone Centrally loggedACN3508E: Data Protection for Exchange: backup type restore ofstorage group storage group name to server server name failed, rc =return code.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a storage group restore fails.System actionNoneUser responseNone Centrally loggedAppendix E. Data Protection for Exchange Messages 167

IBM ConfidentialACN3509I: Data Protection for Exchange: backup type restore ofstorage group storage group name to server server name was cancelledby the user.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log when a storage group restore was cancelled by the user.System actionNoneUser responseNone Centrally loggedACN3510I: Data Protection for Exchange: Attempting to inactivate theobject: filespace - [filespace name], hl - [high level], ll - [low level]ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the attempt to inactivate an object.System actionNoneUser responseNone Centrally loggedACN3511I: Data Protection for Exchange: Inactivation of the previousobjects succeeded.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the success of the inactivation of objects.System actionNoneUser responseNone Centrally logged168 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN3512E: Data Protection for Exchange: Inactivation of the previousobjects failed.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the failure of the inactivation of objects.System actionNoneUser responseNone Centrally loggedACN3513E: Data Protection for Exchange: Inactivation of the previousobjects was canceled.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the failure of the inactivation of objects because thetask was canceled by the user.System actionNoneUser responseNone Centrally loggedACN3514I: Data Protection for Exchange: Starting backup for serverservername.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the start of a backup.System actionNoneUser responseNone Centrally loggedAppendix E. Data Protection for Exchange Messages 169

IBM ConfidentialACN3516I: Data Protection for Exchange: Backup of server servernameis complete. Total storage groups backed up: Total bytes transferred:Elapsed processing time: Secs Throughput rate: Kb/SecExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the end of a backup request.System actionNoneUser responseNone Centrally loggedACN3517E: Data Protection for Exchange: Backup of serverservername failed, rc = returncode.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the failure of a backup request.System actionNoneUser responseNone Centrally loggedACN3518I: Data Protection for Exchange: Backup of server servernamefailed. The request was canceled by the user.ExplanationThis is an informational message that is written to the Tivoli Storage ManagerServer activity log indicating the failure of a backup request. The user canceled thebackup.System actionNoneUser responseNone Centrally logged170 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5050I: A new configuration file has been created.ExplanationThe /configfile value specified a file name that does not exist. A new file has beencreated.System actionProcessing continues.User responseNone.ACN5051W: The configuration file cannot be found, using defaultsettings.ExplanationThe /configfile value specified a file that cannot be found. Default settings will beused.System actionProcessing continues using default settings.User responseEnsure that the configuration file exists, and enter the command again.ACN5052E: An error occurred trying to set the preference preference.ExplanationAn error occurred while writing to the preferences file.System actionProcessing ends.User responseView any other messages that were displayed. Fix any of the problems indicatedand enter the command again.ACN5053E: The value for the preference preference is not valid. Seethe TDPEXCC HELP SET output or the User’s Guide for valid SETcommand parameters.ExplanationThe preference being set is not valid.Appendix E. Data Protection for Exchange Messages 171

IBM ConfidentialSystem actionProcessing ends.User responseRun the ″tdpexcc help set″ command or see the User’s Guide for valid SETcommand parameters.ACN5054I: The preference has been set successfully.ExplanationThe preference was set successfully.System actionProcessing ends.User responseNoneACN5055E: The Microsoft Exchange API could not be loaded.ExplanationIf running on Microsoft Exchange 5.5, the dll that is attempting to load isedbbcli.dll. If running on a later version of Microsoft Exchange, the dll that isattempting to load is esebcli2.dll.System actionProcessing ends.User responseEnsure that the Microsoft Exchange Server has been correctly installed.ACN5056I: The logfile log file could not be pruned. Processing willcontinue.ExplanationAn attempt to prune the log was unsuccessful.System actionProcessing continues.User responseEnsure that the log file name is valid and that the log file exists. If a valid log filename was specified, view the log for indications of what the problem may be.172 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5057I: The logfile log file has been pruned successfully.ExplanationThe specified log file was pruned successfully.System actionProcessing continues.User responseNone.ACN5058W: The length of the logf ile name is greater than themaximum allowed. Processing will continue using a log file name oflogfile in the current directory.ExplanationThe log file name entered was not fully qualified. When the fully qualified log filename was created, it was longer than the maximum allowed length for a log filename.System actionProcessing continues creating and using a log file in the current directory.User responseUpdate the log file name using a fully qualified path.ACN5059W: The logfile log file cannot be opened for writing. There willbe no logging of events.ExplanationThe specified log file could not be opened for append and logging of events willnot occur. The log file may be read-only or the log file name is not valid.System actionProcessing continues without logging.User responseDetermine why the log could not be opened. You may need to ensure that the logfile is not read-only, or ensure that a valid drive or partition is specified in the logfile name.Appendix E. Data Protection for Exchange Messages 173

IBM ConfidentialACN5060E: A Tivoli Storage Manager API error has occurred.ExplanationA Tivoli Storage Manager API api error has occurred.System actionProcessing ends.User responseTry the operation again. If the error persists, contact your service representative.ACN5061E: A Microsoft Exchange api error has occurred.ExplanationA Microsoft Exchange api error has occurred.System actionProcessing ends.User responseTry the operation again. If the error persists, contact your service representative.ACN5062E: The version of Microsoft Exchange that is running is not asupported version for IBM Tivoli Storage Manager for Mail.ExplanationIBM Tivoli Storage Manager for Mail has detected a version of Microsoft ExchangeServer that is not supported.System actionProcessing ends.User responseRefer to the software requirements section of the product documentation to view alist of the supported versions of Microsoft Exchange Server. If the version ofMicrosoft Exchange Server running is a supported version, try the operation again.If the error persists, contact your service representative.174 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5063E: An error occurred trying to get the Microsoft Exchangeversion information. It could be a problem with the registry. Or, aMicrosoft Exchange Server is not installed on this machine.ExplanationAn attempt was made to read the registry to determine the level of MicrosoftExchange that is currently running. This attempt failed.System actionProcessing ends.User responseDetermine if the registry has been corrupted. Also, ensure that the MicrosoftExchange Server is installed on this machine.ACN5064W: The service cannot be started when doing a restore.ExplanationA request was made to restore the listed database. However, the service associatedwith this database has already started. The service needs to be stopped in order todo this restore.System actionProcessing ends.User responseStop the associated service and enter the restore command again.ACN5065E: All of the services associated with this restore are running.ExplanationA request was made to restore several databases. However, all of the servicesassociated with these databases are running. The services need to be stopped inorder to do this restore.System actionProcessing ends.User responseStop the associated services and enter the restore command again.ACN5066W: The storage group does not exist.ExplanationThe storage group that was entered that does not exist on the server specified.Appendix E. Data Protection for Exchange Messages 175

IBM ConfidentialSystem actionProcessing ends.User responseEnter the command specifying a storage group that exists.ACN5067E: None of the storage groups or databases entered exist. Or,if they do exist, and you are using Exchange 2000 or Exchange 2003,the databases have not been dismounted.ExplanationThe storage groups that were entered either do not exist on the Microsoft ExchangeServer or the databases within the storage groups have not been dismounted.System actionProcessing ends.User responseVerify that the storage groups or databases exist and that the databases have beendismounted before starting the restore.ACN5068W: The database does not exist in thestorage group .ExplanationThe database that was entered does not exist in the storage group that wasentered.System actionProcessing ends.User responseEnter the command again specifying a valid database name that exists in a validstorage group.ACN5069W: The database in the storage group is not dismounted.ExplanationWhile examining the list of databases to restore, it was determined that not all ofthe databases within the specified storage groups were dismounted.System actionProcessing continues skipping over the listed databases and storage groups.176 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseEnsure that the databases are dismounted and enter the command again.ACN5070W: The Directory Service is not running. The Directory willnot be backed up.ExplanationA request was made to backup the Directory service. However, the Directoryservice needs to be running in order to do the backup.System actionProcessing ends.User responseStart the Directory service and enter the backup command again.ACN5071W: The Information Store is not running. The InformationStore will not be backed up.ExplanationA request was made to backup the Information Store. However, the InformationStore needs to be running in order to do the backup.System actionProcessing ends.User responseStart the Information Store and enter the backup command again.ACN5072W: Databases in storage group aredismounted -- skipping.ExplanationA request was made to backup a set of storage groups. However, some databasesin this storage group are not mounted. All of the databases need to be mounted inorder to backup this storage group.System actionProcessing continues, but dismounted databases are skipped.User responseEnsure that all of the databases are mounted in the storage group and start thebackup for the storage group again.Appendix E. Data Protection for Exchange Messages 177

IBM ConfidentialACN5073E: None of the storage groups entered are in a state to bebacked up.ExplanationA request was made to backup a set of storage groups. However, each of thestorage groups entered has at least one database that is dismounted.System actionProcessing ends.User responseEnsure that all of the databases are mounted in the storage groups and start thebackup for the storage groups again.ACN5074E: None of the databases or storage groups entered exist.ExplanationA request was made to backup a set of storage groups or databases that do not.The storage group and database names might not have been entered using thecorrect casing.System actionProcessing ends.User responseEnsure that the correct casing is used when entering the list of databases or storagegroups to be backed up. Enter the backup command again.ACN5076W: Unable to inactivate all previous backup objects.ExplanationA request to inactivate some previous backup objects failed.System actionProcessing ends.User responseWhen the next full backup of the database is run, another attempt will be made toinactivate the failed objects.ACN5083I: All of the storage groups entered have been excluded.ExplanationAn attempt was made to do a backup. However, the storage groups or databasesentered have been excluded by an exclude statement in the options file.178 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionProcessing ends.User responseIf you want these storage groups or databases backed up, modify the excludestatements in your options file.ACN5084W: IS was not input as one of the parts to restore. The partialoption will be ignored.ExplanationA request was made to restore either the private or public part of the InformationStore. However, the IS was not input as one of the parts to restore.System actionProcessing continues ignoring the partial option.User responseTo restore either the public or private part of the Information Store, enter IS as aninput.ACN5086W: None of the storage groups entered exist. Or, if doing aDBCOPY backup, the database entered does not exist.ExplanationA storage group was entered that does not exist on the server specified. Or, if aDBCOPY backup was entered, the dbname specified does not exist on theMicrosoft Exchange Server.System actionProcessing ends.User responseEnter the command specifying a storage group or dbname that exists.ACN5087E: PASSWORDACCESS is Generate. Either the storedpassword is incorrect or there is no stored password. If you do nothave a stored password, use of the -TSMPassword=xxx option will setand store your password.ExplanationThe client options file has the PASSWORDACCESS option set to generate.Currently, there is no password that has been stored. An initial password needs tobe stored.Appendix E. Data Protection for Exchange Messages 179

IBM ConfidentialSystem actionProcessing ends.User responseInvoke the command again using the -TSMPassword option. Any subsequentcommands should then complete without specifying a password.ACN5140I: Storage Group does not exist - skipping.ExplanationThe storage group that was specified by the user is not found on this Exchangeserver.System actionThis storage group is skipped.User responseEnsure that the storage group name is spelled correctly and enter the commandagain.ACN5141I: Database , Storage Group doesnot exist - skipping.ExplanationThis combination of storage group and database name that was specified is notfound on this Microsoft Exchange server.System actionThe storage group and database are skipped.User responseEnsure that the the storage group name and databse name are spelled correctlyand enter the command again.ACN5142E: No storage group was found that matches the request.ExplanationThe storage groups or databases could not be found on this Microsoft Exchangeserver.System actionProcessing ends.180 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseEnsure that the storage group or database names are spelled correctly and enterthe command again.ACN5209I: There are no backups matching the server nameservername and the following filespecs:filespecs.ExplanationThere are no database backups on the Tivoli Storage Manager server for thespecified server name.System actionProcessing ends.User responseNoneACN5228I: Data Protection for Exchange is not configured for VSSoperations.ExplanationData Protection for Exchange has not been configured to perform VSS operations.System actionNone.User responseIn order to perform VSS operations, there must be a valid Tivoli Storage ManagerAdvanced Copy Services license installed and the Data Protection for ExchangeLOCALDSMAGENTNODE preference must be set correctly. Refer to the DataProtection for Exchange User’s Guide for details on configuring the client for VSSoperations.ACN5229E: Error obtaining VSS information from Local DSMAgentNode: ’localdsmagentnode’.ExplanationData Protection for Exchange attempted to obtain VSS information through thespecified LOCALDSMAGENTNODE but failed. The error message encountered isalso displayed.System actionVSS information is not displayed.Appendix E. Data Protection for Exchange Messages 181

IBM ConfidentialUser responseRefer to the error message displayed along with this message.ACN5237E: Unable to communicate with the Microsoft ExchangeServer.ExplanationAn attempt was made to communicate the with the Microsoft Exchange Server thatwas entered. This attempt failed.System actionProcessing ends.User responseEnsure that the name of the Microsoft Exchange server that was entered is valid.Also, ensure that the Microsoft Exchange server is running.ACN5238E: Unable to retrieve the domain information for the MicrosoftExchange Server.ExplanationAn attempt was made to retrieve the domain information for the MicrosoftExchange Server. This attempt failed.System actionProcessing ends.User responseEnsure that the Microsoft Exchange server is running.ACN5239E: Unable to retrieve the storage group information.ExplanationAn attempt was made to retrieve the storage group information for the MicrosoftExchange Server. This attempt failed.System actionProcessing ends.User responseEnsure that the Microsoft Exchange Server is running properly.182 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5240E: Unable to retrieve the database information.ExplanationAn attempt was made to retrieve the database information for the storage group ofthe Microsoft Exchange Server. This attempt failed.System actionProcessing ends.User responseEnsure that the Microsoft Exchange Server is running properly.ACN5241E: The Microsoft Exchange Information Store is currently notrunning.ExplanationAn attempt was made to retrieve the Microsoft Exchange Server information. Thisattempt failed.System actionProcessing ends.User responseIn order to retrieve the Microsoft Exchange Server information, the MicrosoftExchange Information Store needs to be running. Start this service to get therequested information.ACN5301E: Unable to get the value for the Organization from theregistry.ExplanationAn attempt was made to read the registry to determine the organization for theMicrosoft Exchange Server. This attempt failed.System actionProcessing ends.User responseDetermine if there is a problem with the registry or ensure that the MicrosoftExchange Server is installed properly.Appendix E. Data Protection for Exchange Messages 183

IBM ConfidentialACN5302E: Unable to get the value for the Site from the registry.ExplanationAn attempt was made to read the registry to determine the site for the MicrosoftExchange Server. This attempt failed.System actionProcessing ends.User responseDetermine if there is a problem with the registry or ensure that the MicrosoftExchange Server is installed properly.ACN5303E: Unable to get the value for Circular Logging from theregistry.ExplanationAn attempt was made to read the registry to determine the Circular Loggingsetting for either the IS or the DIR of the Microsoft Exchange Server. This attemptfailed.System actionProcessing ends.User responseDetermine if there is a problem with the registry or ensure that the MicrosoftExchange Server is installed properly.ACN5304E: Unable to open service to determine if running or not.ExplanationAn attempt to open a service failed.System actionProcessing ends.User responseDetermine if there is a problem with the Microsoft Exchange server.ACN5305E: Unable to query service information.ExplanationAn attempt to query specific service information failed.184 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialSystem actionProcessing ends.User responseDetermine if there is a problem with the Microsoft Exchange server.ACN5350E: An unknown Exchange API error has occurred.ExplanationAn Exchange API error has occurred but the associated error message could not befound. The Windows NT event log may contain more information.System actionProcessing ends.User responseIf the Windows NT event log does not help resolve the problem, verify theExchange Server installation and retry the operation. If the error persists, contactyour service representative.ACN5351E: The Exchange server application is not registered forbackup.ExplanationThe Exchange server application must be registered for backup with the WindowsServer. The Windows NT event log may contain more information.System actionProcessing ends.User responseIf the Windows NT event log does not help resolve the problem, verify theExchange Server installation and retry the operation. If the error persists, contactyour service representative.ACN5352E: The Exchange server application is not registered foroffline restore.ExplanationThe Exchange server application must be registered for offline restore with theWindows Server. The Windows NT event log may contain more information.System actionProcessing ends.Appendix E. Data Protection for Exchange Messages 185

IBM ConfidentialUser responseIf the Windows NT event log does not help resolve the problem, verify theExchange Server installation and retry the operation. If the error persists, contactyour service representative.ACN5353E: The Exchange server application is not registered foronline restore.ExplanationThe Exchange server application must be registered for online restore with theWindows Server. The Windows NT event log may contain more information.System actionProcessing ends.User responseIf the Windows NT event log does not help resolve the problem, verify theExchange Server installation and retry the operation. If the error persists, contactyour service representative.ACN5354E: The storage group was not found.ExplanationThe specified storage group name was not found.System actionProcessing ends.User responseVerify the command input and retry the operation. If the error persists, contactyour service representative.ACN5355E: The database was not found.ExplanationThe specified database name was not found.System actionProcessing ends.User responseVerify the command input and retry the operation. If the error persists, contactyour service representative.186 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5356E: The database file name is undefined.ExplanationEvery Microsoft Exchange database must specify a database file name.System actionProcessing ends.User responseVerify the database properties and retry the operation. If the error persists, contactyour service representative.ACN5357W: The truncation of the transaction log failed.ExplanationThe truncation of the transaction log failed.System actionProcessing continues.User responseRefer to other messages that are displayed to determine the problem.ACN5358E: A Microsoft Exchange API protocol error has occurred.ExplanationAn unrecoverable Microsoft Exchange API protocol error has occurred.System actionProcessing ends.User responseContact your service representative.ACN5359E: An attempt was made to get the TEMP environmentvariable. This attempt failed.ExplanationThe TEMPLOGRESTOREPATH option was not set for the restore. Therefore, anattempt was made to get the TEMP environment variable for the machine. Thisattempt failed.System actionProcessing ends.Appendix E. Data Protection for Exchange Messages 187

IBM ConfidentialUser responseEnsure that the TEMP environment variable is set for this machine. You can alsouse the TEMPLOGRESTOREPATH option with the restore.ACN5360E: The /ERASEexistingdata option is not allowed during apartial restore.ExplanationA partial storage group restore was requested with the /ERASEexistingdata option.The /ERASEexistingdata option is not allowed during a partial restore.System actionProcessing ends.User responseEnter the command to restore the entire storage group or enter the commandwithout the /ERASEexistingdata option.ACN5361E: It is invalid to have an ’*’ within a storage group name.ExplanationAn attempt was made to backup a storage group that contains an ’*’. It is invalidto have an ’*’ in a storage group name.System actionProcessing continues, but this storage group will not be backed up.User responseRename the storage group, otherwise this storage group cannot be backed up.ACN5362W: The filespace in an invalid filespace name.ExplanationThe filespace displayed in the message exists, but is an invalid filespace.System actionProcessing continues, but this filespace will not be used.User responseEnsure that the storage group name does not contain invalid characters. Refer tothe Microsoft Exchange documentation for the list of invalid characters.188 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5500E: The MultiByteToWideChar() function failed.ExplanationAn internal error occurred.System actionProcessing ends.User responseRetry the operation. If this error persists, contact your service representative.ACN5501E: The WideCharToMultiByte() function failed.ExplanationAn internal error occurred.System actionProcessing ends.User responseRetry the operation. If this error persists, contact your service representative.ACN5705W: An error was encountered with Tivoli Storage Manager APIinitialization, rc = returncode. Examine the dsierror.log for moreinformation or determine if the TSM API is installed properly.ExplanationAn attempt was made to run setup for the Tivoli Storage Manager API. However,errors were encountered.System actionProcessing continues.User responseExamine the dsierror.log file to determine the problem. If this file does not exist, itis possible that the TSM API is not installed properly. If this is the case, reinstallthe TSM API and try running the command again.ACN5706I: The logfile_name log file did not need pruning.ExplanationThe log file specified did not need to be pruned.Appendix E. Data Protection for Exchange Messages 189

IBM ConfidentialSystem actionProcessing continues.User responseThe log file will automatically be pruned at a later date. If the log file is too largenow, lower the number of days the log entries are retained.ACN5707W: The logfile_name log file could not be opened for writing.The log was not pruned and there will be no logging of events.ExplanationThe log could not be opened for append. Therefore, there will be no logging doneand the request to prune was not done.System actionProcessing continues without logging and without pruning.User responseDetermine why the log could not be opened. You may need to ensure that the fileis not read-only, or ensure that a valid drive or partition is specified with the logfile name.ACN5724I: No databases have been selected for backup.ExplanationThe Backup button was pressed but no databases have been selected in the list inthe graphical user interface.System actionProcessing stops.User responseSelect a database and press the Backup button.ACN5725I: No Storage Groups have been selected for backup.ExplanationThe Backup button was pressed but no Storage Groups have been selected in thetree or list in the graphical user interface.System actionProcessing stops.190 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseSelect a Storage Group and press the Backup button.ACN5741I: No Backups have been selected for restore.ExplanationThe Restore button was pressed but nothing was selected in the tree or list view.System actionProcessing stops.User responseMake a selection in the tree or list view and press the Restore button again.ACN5758W: At least one of the database’s services that is selected forrestore is running. Do you want to stop the service(s)?ExplanationA service that you are trying to restore is running. The service cannot be runningin order to perform the restore.System actionNoneUser responseChoose the desired response and continue.ACN5759W: At least one of the databases that is selected for restore ismounted. Do you want to dismount the database(s)?ExplanationA database you are trying to restore is mounted.System actionNoneUser responseClick ’OK’ to dismount and continue, or cancel to stop.Appendix E. Data Protection for Exchange Messages 191

IBM ConfidentialACN5766E: Unable to dismount database database in storage groupstorage group. Do you want to continue the restore process?ExplanationAn error occurred while trying to dismount a database.System actionNone.User responsePress OK to continue the restore or press cancel to stop.ACN5798E: MS Exchange API api name failed with HRESULT: apiretcode -ExplanationA Microsoft Exchange API error occurred during an operation. The specific APIfunction that failed along with the HRESULT code of the failure and possiblemessage associated with that error is displayed.System actionProcessing ends.User responseIf the Windows Event Log does not help resolve the problem, stop and restart theExchange server and retry the operation. If the error persists, contact your servicerepresentative.ACN5800E: Backup is corrupt. See log file for additional information.ExplanationWhen attempting to process an Exchange backup on the Tivoli Storage ManagerServer, not all required objects were present. The operation cannot proceed. Thespecific backup affected is logged.System actionProcessing ends.User responseRetry the operation. If the error persists, contact your service representative.192 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5802T: When a Recovery Storage Group exists, mailbox andpublic folder databases cannot be restored in the same operation.ACTION: Please select either a mailbox OR public folder database forrestore.ACN5803T: When performing a mailbox database restore to a RecoveryStorage Group, the Replay Restored Logs ONLY option must bespecified or the restore may fail. ACTION: The Replay Restored LogsONLY option will AUTOMATICALLY be used on the restore. Do youwish to continue with the restore?ACN5805E: Restore failed. File already exists.ExplanationThe specified file already exists in the restore (/INTO) path. The RESTOREFILEScommand is designed not to overwrite existing files.System actionThe restore operation fails and processing ends.User responseIf you want to restore the specified file, you must first delete the file that exists inthe restore (/INTO) path and retry the operation or specify a different restore(/INTO) path and retry the operation.ACN5810E: Restoring Legacy backups and VSS backups in the samerestore operation is not supported. Retry the restores in separateoperations.ExplanationAt least one VSS backup object and one Legacy backup object were selected for arestore in the same operation. This is not supported.System actionThe restore operation is canceled.User responseRetry the restores specifying the Legacy backups and VSS backups in separateoperations.Appendix E. Data Protection for Exchange Messages 193

IBM ConfidentialACN5811E: Invalid command. Data Protection for Exchange onlysupports VSS backup types of FULL and COPY.ExplanationAn invalid backup type was specified on the VSS backup request. Data Protectionfor Exchange supports backup types of FULL and COPY when using the VSSbackup method.System actionThe backup operation is canceled.User responseRetry the backup operation specifying a supported VSS backup type.ACN5812E: Invalid command. Data Protection for Exchange does notsupport OFFLOAD with the Legacy backup method.ExplanationThe OFFLOAD option was specified when using the Legacy backup method. DataProtection for Exchange does not support offload with the Legacy backup method.Data Protection for Exchange supports offload with the VSS backup method only.System actionThe backup operation is canceled.User responseRetry the backup operation without specifying the offload option or by specifyingthe VSS backup method.ACN5813E: Invalid command. Data Protection for Exchange onlysupports Legacy backups with a backup destination of TSM.ExplanationAn invalid backup destination was specified with the Legacy backup method. DataProtection for Exchange only supports a backup destination of TSM when usingthe Legacy backup method.System actionThe backup operation is canceled.User responseRetry the backup operation specifying a backup destination of TSM.194 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialACN5814E: Invalid command. Data Protection for Exchange does notsupport OFFLOAD with the specified backup destination.ExplanationThe OFFLOAD option was specified with an unsupported backup destination.Data Protection for Exchange only supports offload with a backup destination ofTSM.System actionThe backup operation is canceled.User responseRetry the VSS offloaded backup operation specifying a backup destination of TSM.ACN5815E: The VSS operation failed with rc = returncode.ExplanationThere was a failure when Data Protection for Exchange performed the VSSoperation.System actionThe VSS operation stops.User responseVerify that the Client Acceptor Daemon (CAD) is installed, configured, andrunning properly on the machine. Retry the operation. If the error persists, contactyour service representative.ACN5816E: Data Protection for Exchange is not able to run VSSoperations. You must be running Exchange Server 2003 (or later) andhave the MS Exchange VSS license file (acsexc.lic) installed.ExplanationIn order to perform VSS operations, Data Protection for Exchange verifies that theExchange Server level is at least Exchange Server 2003 and that the Tivoli StorageManager for Advanced Copy Services - MS Exchange VSS Integration Module isinstalled. If the Tivoli Storage Manager for Advanced Copy Services - MSExchange VSS Integration Module is installed, there will be a license file, acsexc.lic,in the Data Protection for Exchange installation directory.System actionThe operation stops.Appendix E. Data Protection for Exchange Messages 195

IBM ConfidentialUser responseVerify that the prerequisites identified above are met and retry the operation. If theerror persists, contact your service representative.ACN5817E: Missing, blank, or invalid Local DSMAGENT Node Name isnot allowed.ExplanationIn order to run VSS operations, Data Protection for Exchange verifies that the LocalDSMAGENT Node Name is specified and valid. This error indicates that the LocalDSMAGENT Node Name is missing, blank, or invalid.System actionThe operation stops.User responseSet the Local DSMAGENT Node Name to a valid value and retry the operation.ACN5818E: Invalid command. Data Protection for Exchange onlysupports restoring VSS backup types of FULL and COPY.ExplanationAn invalid backup type was specified on the VSS restore request. Data Protectionfor Exchange supports restoring backups of type FULL and COPY.System actionThe restore operation is canceled.User responseRetry the restore operation specifying a supported VSS backup type.ACN5819E: Multiple backup objects were found for the specifiedstorage group(s) and backup destination. Use the OBJECT= andBACKUPDESTINATION= options to identify which specific backupobject to restore.ExplanationThe backup object specified for the VSS restore operation was not specific enoughto be unique. More information is required in order to restore the correct backupobject.System actionThe restore operation is canceled.196 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialUser responseRetry the restore operation specifying the /OBJECT= and/BACKUPDESTINATION parameters.ACN5820E: There were no Exchange backups found on the TivoliStorage Manager server matching the specified criteria.ExplanationA query was issued to the Tivoli Storage Manager server to find the DataProtection for Exchange backups that match the specified search criteria. Therewere no backups found.System actionNone.User responseNone.ACN5824I: Storage Group does not have replica -skipping.ExplanationReplica for the storage group specified by the user is not found on this Exchangeserver.System actionThis storage group is skipped.User responseEnsure that the storage group name is spelled correctly and has a replica and enterthe command again.ACN5825E: Invalid command. Data Protection for Exchange does notsupport FROMREPLICA with the Legacy backup method.ExplanationThe FROMREPLICA option was specified when using the Legacy backup method.Data Protection for Exchange does not support fromreplica with the Legacy backupmethod. Data Protection for Exchange supports fromreplica with the VSS backupmethod only.System actionThe backup operation is canceled.Appendix E. Data Protection for Exchange Messages 197

IBM ConfidentialUser responseRetry the backup operation without specifying the fromreplica option or byspecifying the VSS backup method.ACN5829E: Invalid command. Data Protection for Exchange does notsupport INTOSG with the Legacy restore method.ExplanationThe INTOSG option was specified when using the Legacy restore method. DataProtection for Exchange does not support INTOSG with the Legacy restoremethod. Data Protection for Exchange supports INTOSG with the VSS restoremethod only.System actionThe restore operation is canceled.User responseRetry the restore operation without specifying the INTOSG option or by specifyingthe VSS restore method.198 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialNoticesThis information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:199

IBM ConfidentialIBM CorporationInformation Enabling RequestsDept. M135600 Cottle RoadSan Jose CA 95193-0001U.S.A.Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.This information is for planning purposes only. The information herein is subject tochange before the products described become available.If you are viewing this information softcopy, the photographs and colorillustrations may not appear.200 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialTrademarksIBM, the IBM logo and the following terms are trademarks of the InternationalBusiness Machines Corporation in the United States, other countries, or both:AIXAS/400DB2DFSDFSMS/MVSDFSMShsmDFSMSrmmDPIEnterprise Storage ServerESCONeServerFICONFlashCopyHACMPInformixiSeriesLotusLotus 1-2-3Lotus ApproachLotus DominoLotus NotesMagstarMVSNetViewOpenEditionOS/2OS/390OS/400Passport AdvantagepSeriesRACFRationalRedbooksRS/6000S/390SANergySecureWayStorageSmartSystemViewTivoliTivoli Enterprise ConsoleTivoli Management EnterpriseTotalStorageTMEVTAMWebSpherez/OSzSeriesIntel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporationin the United States, other countries, or both.Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and othercountries.Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries,or both.Other company, product or service names may be trademarks or service marks ofothers.201

202 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

IBM ConfidentialGlossaryThe terms in this glossary are defined as theypertain to the Tivoli Storage Manager library. Ifyou do not find a term you are looking for, youcan refer to the IBM Dictionary of Computing atURL:www.ibm.com/networking/nsg/nsgmain.htmThis glossary may include terms and definitionsfrom:v The American National Standard Dictionary forInformation Systems , ANSI X3.172-1990,copyright (ANSI). Copies can be purchasedfrom the American National StandardsInstitute, 11 West 42nd Street, New York, NewYork 10036.v The Information Technology Vocabulary,developed by Subcommittee 1, Joint TechnicalCommittee 1, of the International Organizationfor Standardization and the InternationalElectrotechnical Commission (ISO/IECJTC2/SC1).active policy setThe policy set within a policy domainthat contains the most recently activatedpolicy. This policy set is used by all clientnodes assigned to the current policydomain. See policy set.active versionThe most recent backup copy of a filestored in Tivoli Storage Manager storagefor a file that currently exists on a fileserver or workstation. An active versionremains active and exempt from deletionuntil:v Replaced by a new backup version.v Tivoli Storage Manager detects, duringan incremental backup, that the userhas deleted the original file from a fileserver or workstation.administrative clientA program that runs on a file server,workstation, or mainframe. This programlets administrators monitor and controlTivoli Storage Manager servers usingTivoli Storage Manager administratorcommands. Contrast with backup-archiveclient.administratorA user who is registered to the server asan administrator. Administrators maypossess one or more privilege classes.Administrators can use the administrativeclient to enter Tivoli Storage Managerserver commands and queries accordingto their privileges.application program interface (API)A set of functions that applicationsrunning on a client platform can call tostore, query, and retrieve objects fromTivoli Storage Manager storage.archivearchiveA function permitting users to copy oneor more files to a long-term storagedevice. Archive copies can:v Accompany descriptive informationv Imply data compression software usagev Be retrieved by archive date, file name,or descriptionContrast with retrieve.copyA file or group of files residing in anarchive storage pool in Tivoli StorageManager storage.archive copy groupA policy object containing attributes thatcontrol the generation, destination, andexpiration of archived files. The archivecopy group belongs to a managementclass.archive retention grace periodThe number of days Tivoli StorageManager retains an archived copy whenthe server is unable to rebind the file toan appropriate management class.authenticationThe process of checking and authorizing auser’s password before permitting useraccess to the Tivoli Storage Managerserver. An administrator with systemprivilege can enable or disableauthentication.authorization ruleA specification permitting another user to203

IBM Confidentialeither restore or retrieve a user’s filesfrom Tivoli Storage Manager storage.backupA function permitting users to copy oneor more files to a storage pool to protectagainst data loss. Contrast with restore.backup-archive clientA program that runs on a file server, PC,or workstation and provides a means forTivoli Storage Manager users to back up,archive, restore, and retrieve files.Contrast with administrative client.backup copy groupA policy object containing attributes thatcontrol the generation, destination, andexpiration of backup files. A backup copygroup belongs to a management class.backup versionA backed up file, directory, or file spacethat resides in a backup storage pool inTivoli Storage Manager storage. The activeversion is the most recent backup version.See active version and inactive version.client A program running on a file server, PC,workstation, or terminal that requestsservices of another program called theserver. There are two types of TivoliStorage Manager clients: administrativeand backup-archive. See administrativeclient and backup-archive client.clientclientdomainThe set of drives, file systems, or volumesselected by a user for processing during abackup or archive operation.nodeA file server or workstation registeredwith the server on which thebackup-archive client program is installed.client options fileA file that a client can edit, containing adefault set of processing options thatidentify the server, communicationmethod, backup and archive options,space management options, andscheduling options.client/serverA communications network architecturein which one or more programs (clients)|||||||closedrequest computing or data services fromanother program (the server).registrationA registration process in which an TivoliStorage Manager administrator mustregister workstations as client nodes withthe server. Contrast with open registration.Cluster Continuous Replication (CCR)Technology that extends the highavailability capabilities of Exchange 2007Mailbox servers using Exchange 2007failover and management featuresprovided by the Microsoft WindowsCluster service.command line interfaceA type of user interface where commandsare specified on the command line.Contrast with graphical user interface.commitTo make changes permanent in thedatabases files. Changes made to thedatabase files are not permanent untilthey are committed.communication methodThe method by which a client and serverexchange information.communication protocolA set of defined interfaces that permitscomputers to communicate with eachother.compressionThe process of saving storage space byeliminating empty fields or unnecessarydata to shorten the length of the file. InTivoli Storage Manager, compression canoccur at a workstation before files arebacked up or archived to server storage.On some types of tape drives, hardwarecompression can be used.copycopybackupA copy backup is similar to a full backupexcept that transaction log files are notcleared after the backup. A backup copycan be used to make a full backup of theExchange Server database withoutdisrupting any backup procedures thatuse incremental or differential backups.groupAn Tivoli Storage Manager policy objectthat determines how Tivoli StorageManager backs up or archives files. Copy204 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialgroups belong to management classes.There are two copy groups:v Backup copy group—determines howTivoli Storage Manager backs up orarchives files.v Archive copy group—determines howTivoli Storage Manager archives files.default management classA management class assigned to a policyset. This class is used to govern backedup or archived files when a user does notexplicitly associate a file with a specificmanagement class through theinclude-exclude list.differential backupA differential backup backs up onlytransaction logs, but does not clear them.If you perform a full backup and thenperform only differential backups, the lastfull backup plus the latest differentialbackup has all data needed to bring thedatabase back to the most recent state.This type of backup is also called acumulative incremental backup.domainSee policy domain or client domain.dsm.opt fileSee options file. Also called client optionsfile.errorlogA text file written on disk that containsTivoli Storage Manager processing errormessages. These errors are detected andsaved by the Tivoli Storage Managerserver.excludeThe process of identifying files in aninclude-exclude list. This process preventsthe files from being backed up ormigrated whenever a user or scheduleenters an incremental or selective backupoperation.expirationThe process in which files are identifiedfor deletion because their expiration dateor retention period has passed. Backed upor archived files are marked for deletionbased on the criteria defined in thebackup or archive copy group.filefilefullserverA dedicated computer and its peripheralstorage devices connected to a local areanetwork that stores both programs andfiles shared by users on the network.spaceA logical space on the Tivoli StorageManager server that contains a group offiles. In Tivoli Storage Manager, users canrestore, retrieve, or delete file spaces fromTivoli Storage Manager storage.backupA full backup backs up the specifieddatabase as well as its associatedtransaction logs. After the database andlogs are backed up, the log files aredeleted.generate passwordProcessing that stores a new password inan encrypted password file when the oldpassword expires. Automatic generationof a password prevents passwordprompting. Password generation can beset in the options file (passwordaccessoption). See options file.graphical user interface (GUI)A type of user interface that takesadvantage of a high-resolution monitor,includes a combination of graphics, theobject-action paradigm, and the use ofpointing devices, menu bars, overlappingwindows, and icons. Contrast withcommand line interface.GUI Graphical user interface.inactive versionA copy of a backup file in Tivoli StorageManager storage that either is not themost recent version, or the correspondingoriginal file was deleted from the clientfile system. Inactive backup versions areeligible for expiration according to themanagement class assigned to the file.include-exclude fileA file containing statements to determinethe files to back up and the associatedmanagement classes to use for backup orarchive. See include-exclude list.Glossary 205

IBM Confidentialinclude-exclude listA list of include and exclude options thatinclude or exclude selected files forbackup. An exclude option identifies filesthat should not be backed up. An includeoption identifies files that are exemptfrom the exclusion rules or assigns amanagement class to a file or a group offiles for backup or archive services. Theinclude-exclude list is defined in one ormore include-exclude files or in the clientoptions file. The include-exclude list maycontain entries from any or all of thefollowing sources: the client options file,separate include-exclude files, or theTivoli Storage Manager server. See optionsfile.incremental backupAn incremental backup only backs up thetransaction logs and then clears them.Restoration of an Exchange Serverdatabase from an incremental backuprequires a:v Restore of the last full backup.v Restore of any other incrementalbackups performed between the fullbackup and this incremental backup.v Restore of this incremental backup.LAN Local area network.legacylegacybackupA specialized API backup that functionswith the Exchange server storage engine.restoreA specialized API restore that functionswith the Exchange server storage engineto restore legacy backups (Exchangedatabase files and log files) from TivoliStorage Manager server storage to theiroriginal location.local In a Data Protection for Exchange VSSenvironment, local refers to data that isstored on shadow volumes localized to adisk storage subsystem.Local Area Network (LAN)A variable-sized communications networkplaced in one location. LAN connectsservers, PCs, workstations, a networkoperating system, access methods, andcommunications software and links.||||||Local Continuous Replication (LCR)Technology that allows a copy of astorage group to be created andmaintained on a second set of disks thatare connected to the same server as theproduction storage group.management classA Tivoli Storage Manager policy objectthat is a named collection of copy groups.A management class is associated with afile to specify how the server shouldmanage backup versions or archive copiesof workstation files.node See client node.nodeopennameA unique name used to identify aworkstation, file server, or PC to theserver.registrationA registration process in which users canregister their own workstations or PCs asclient nodes with the server. Contrastwith closed registration.options fileA file that contains processing options.Identifies Tivoli Storage Manager servers,specifies communication methods, definesscheduling options, selects backup,archive, restore, and retrieve options. Alsocalled the client options file.policypolicydomainA Tivoli Storage Manager policy objectthat lets Tivoli Storage Manager groupclient nodes by the policies that governtheir files and by the administrator whomanages the policies. The policy domaincontains one or more policy sets.setA Tivoli Storage Manager policy objectthat specifies the management classes thatare available to groups of users. Morethan one policy set can exist. However,only one policy set at a time can beactive.206 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialprogress indicatorA control used to inform a user about theprogress of a process.recovery logA log of updates that are about to bewritten to the databases. The log can beused to recover from system and mediafailures.registrationThe process of identifying a client node oradministrator to the server by specifyinga user ID, password, and contactinformation. For client nodes, a policydomain, compression status, and deletionprivileges are also specified.registryA central database in Windows thatcontains information about hardware,applications, and operating systemsettings for each machine on the network.Provides security and control oversystem, security, and account settings.restoreA function that permits users to copy aversion of a backup file from the storagepool to a workstation or file server. Thebackup copy in the storage pool is notaffected. Contrast with backup.retentionThe amount of time, in days, that inactivebacked up or archived files are retained inthe storage pool before they are deleted.The following copy group attributesdefine retention: retain extra versions,retain only version, retain version.retrieveA function permitting users to copy anarchived file from the storage pool to theworkstation or file server. The archivecopy in the storage pool is not affected.Contrast with archive.schedulingA function permitting an administrator toschedule backup and archive operationsfrom a central location. Operations can bescheduled on a periodic basis or on anexplicit date.scheduling modeThe type of scheduling operation for theclient-server node. Tivoli Storage Managersupports two scheduling modes:client-polling and server-prompted.scroll Move through a list of items in a windowby operating the scrollbars with themouse cursor.select Choose an item from a list or group ofitems.selective backupA function permitting users to back upfiles from a client domain. These files arenot excluded in the include-exclude listand meet the requirement for serializationin the backup copy group of themanagement class assigned to each file.Contrast with incremental backup.server A program running on a mainframe,workstation, or file server that providesshared services such as backup andarchive to other various (often remote)programs (called clients).server-prompted schedulingA client-server communication techniquewhere the server contacts the client nodewhen tasks need to be done.sessionspaceA period of time in which a user cancommunicate with a server to performbackup, archive, restore, or retrieverequests.managementThe process of keeping sufficient freestorage space available on a local filesystem for new data and making the mostefficient and economical use of distributedstorage resources.Tivoli Storage ManagerA client/server program that providesstorage management to customers in amultivendor computer environment.storageTCP/IPpoolA named set of storage volumes used asthe destination of backup, archive, ormigrated copies.Transmission Control Protocol/InternetProtocol.timeoutA time event involving:Glossary 207

IBM Confidential|||v An event that happens at the end of apredetermined period of time thatbegan at the happening of anotherspecified event.v A time interval allotted for certainoperations to happen. For example,response to polling or addressingbefore system operation is interruptedand must be restarted.v A terminal feature that logs off a user ifan entry is not made within a specifiedperiod of time.Transmission Control Protocol/Internet Protocol(TCP/IP)A set of communication protocols thatsupport peer-to-peer connectivityfunctions for both local and wide areanetworks.Veritas Cluster Server (VCS)An application that provides highavailability cluster management.versionStorage management policy may allowback-level copies of backed up objects tobe kept at the server whenever an objectis newly backed up. The most recentbacked up copy is called the ″active″version. Earlier copies are ″inactive″versions. The following backup copygroup attributes define version criteria:versions data exists, and versions datadeleted.VSSBackupA backup that uses Microsoft VolumeShadow Copy Service technology toproduce an online snapshot (point-in-timeconsistent copy) of Exchange data thatcan be stored on local shadow volumes oron Tivoli Storage Manager server storage.VSS Fast RestoreA function that uses a VSS softwareprovider to restore VSS Backups(Exchange database files and log files)that reside on local shadow volumes.VSS Instant RestoreA volume-level hardware-assisted copywhere target volumes (that contain thesnapshot) are copied back to the originalsource volumes.VSS Off-loaded backupA backup that uses a VSS hardwareprovider (installed on an alternatemachine) to move Exchange data to theTivoli Storage Manager server. This typeof backup shifts the backup load from theproduction machine to another machine.VSSRestoreA function that uses a VSS softwareprovider to restore VSS Backups(Exchange database files and log files)that reside on Tivoli Storage Managerserver storage to their original location.wildcard characterAn asterisk (*) or question mark (?)character used to represent multiple (*) orsingle (?) characters when searching forvarious combinations of characters inalphanumeric and symbolic names.workstationA programmable high-level workstation(usually on a network) with its ownprocessing hardware such as ahigh-performance personal computer. In alocal area network, a personal computerthat acts as a single user or client. Aworkstation can also be used as a server.208 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM ConfidentialIndexAactive parameterand query tsm command 72all parameterand query tsm command 72Bbackup 79automating 115copydescription 6database copydescription 6differentialdescription 6fulldescription 6strategy 15full plus differentialsstrategy 15full plus incrementalstrategy 15incrementaldescription 6legacyGUI 56SRScommand line 79storage group 4command line 77Tivoli Storage Managerscheduler 115transaction log 4types 4VSSGUI 56, 57Backup and Restore Window (GUI) 55backup commandand /backupdestinationparameter 78and /backupmethod parameter 78and /buffers parameter 78and /buffersize parameter 78and /configfile parameter 78and /excapplication parameter 79and /excserver parameter 79and /fromreplica parameter 79and /logfile parameter 79and /logprune parameter 80and /mountwait parameter 80and /offload parameter 80and /quiet parameter 81and /skipintegritycheckparameter 81and /tsmnode parameter 81and /tsmoptfile parameter 81and /tsmpassword parameter 81example 82, 83, 84overview 75backup command (continued)syntax diagram 76backup strategy 14full backup 15full plus differentials 15full plus incremental 15Tivoli Storage Manager versus localshadow volumes 32VSS and Legacy together 15VSS cluster 9, 16, 33, 34backupdestination parameterand backup command 78and restore command 88and set command 106backupmethod parameterand backup command 78and GUI 50and restore command 88and set command 107bookssee publications xivbufferingdescription 20buffers parameterand backup command 78and GUI 50and restore command 88and restorefiles command 98and set command 107buffersize parameterand backup command 78and GUI 50and restore command 89and restorefiles command 98and set command 107Cchangetsmpassword commandand /configfile parameter 104and /logfile parameter 104and /logprune parameter 105and /tsmnode parameter 105and /tsmoptfile parameter 105example 105overview 103syntax diagram 103changetsmpassword parameterand GUI 53circular logging 6clustercommand line invocation 21, 22Data Protection for Exchangesupport 21, 22GUI 61installing Data Protection forExchange 30VSS 9, 16, 33, 34clusternode option 40command line interfacecluster 21, 22command line interface (continued)help 110overview 63command line parameters/activeand query tsm 72/alland query tsm 72/backupdestinationand backup 78and restore 88and set 106/backupmethodand backup 78and restore 88and set 107/buffersand backup 78and restore 88and restorefiles 98and set 107/buffersizeand backup 78and restore 89and restorefiles 98and set 107/configfileand backup 78and changetsmpassword 104and GUI invocation 54and query exchange 64and query tdp 68and query tsm 72and restore 89and restorefiles 98and set 109/dateformatand set 107/excapplicationand backup 79and restore 89and restorefiles 99/excserverand backup 79and cluster 54and GUI invocation 54and query exchange 65and restore 89/fromexcserverand query tsm 72and restore 90and restorefiles 99/fromreplicaand backup 79/instantrestoreand restore 90/intoand restorefiles 99/intosgand restore 90209

IBM Confidentialcommand line parameters (continued)/languageand set 107/localdsmagentnodeand set 108/logfileand backup 79and changetsmpassword 104and query exchange 65and query tdp 68and query tsm 72and restore 90and restorefiles 99and set 108/logpruneand backup 80and changetsmpassword 105and query exchange 65and query tdp 69and query tsm 73and restore 91and restorefiles 99and set 108/mountdatabasesand restore 91/mountwaitand backup 80and restore 91and restorefiles 100and set 108/numberformatand set 108/objectand restore 91and restorefiles 100/offloadand backup 80/partialand restore 92and restorefiles 100/quietand backup 81and restore 92and restorefiles 100/recoverand restore 92/remotedsmagentnodeand set 109/retriesand set 109/skipintegritycheckand backup 81/templogrestorepathand restore 93and set 109/timeformatand set 109/tsmnodeand backup 81and changetsmpassword 105and query tsm 73and restore 93and restorefiles 100/tsmoptfileand backup 81and changetsmpassword 105and GUI invocation 54command line parameters (continued)/tsmoptfile (continued)and query tsm 73and restore 93and restorefiles 101/tsmpasswordand backup 81and query tsm command 73and restore 94and restorefiles 101commandschangetsmpassword 103and GUI 53help 110query exchange 64query tdp 68query tsm 70set 106communication protocol option 39compressalways option 41compression option 41configfile parameterand backup command 78and changetsmpasswordcommand 104and GUI invocation 54and query exchange command 64and query tdp command 68and query tsm command 72and restore command 89and restorefiles command 98and set command 109configurationlist of applications 31options 39overview 32procedure 44Exchange Server 45Off-loaded backups 46Tivoli Storage Manager server 45verify 47considerations (installation) 29conventionstypeface xxicopy backupdescription 6copy group 35customer support xixDData Protection for Exchangeadvanced restore procedures 137backup strategy 14backup types 4bufferingdescription 20cluster support 21, 22installation 30command line help 110commands 63configuration parameters 43, 44configuring options 39exclude processing 42features 2GUI 49include processing 42Data Protection for Exchange (continued)include/exclude processing 42installationconsiderations 29hardware requirements 27overview 25packages 29procedure 29LAN Freedescription 21online help 22operating environment 1overview 1performance 20policy settings 18previous versions 29, 128quick configuration 123registering 36restore types 10security 20silent installation 131supported languages 23database copy backupdescription 6dateformat parameterand GUI 51and set command 107Default Backup Destination parameterand GUI 51differential backupdescription 6domain 9, 35dsm.opt fileconfiguring 39clusternode 40communication protocol 39compressalways 41compression 41enableclientencryptkey 40enablelanfree 40encryptiontype 40include.encrypt 40nodename 39passwordaccess 40Tivoli Storage Managerscheduler 117dsmcutil.exe file 40dsmcutil.hlp file 40dsmcutil.txt file 40Eedit menudescription 49educationsee Tivoli technical training xvienableclientencryptkey option 40enablelanfree option 40encryption 40encryptiontype option 40examplebackup command 82, 83, 84changetsmpassword command 105excfull.cmd 116help command 111, 113include/exclude processing 42query exchange command 66, 67210 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialexample (continued)query tdp command 69query tsm command 74restore command 94, 95restorefiles command 101, 102set command 110Tivoli Storage Managerscheduler 115excapplication parameterand backup command 79and restore command 89and restorefiles command 99excfull.cmd 116example 116excfull.log 121Exchange 2000 Server 79, 89, 99authorityoperating 20backing up SRScommand line 79database copydescription 6legacy backup of KMSGUI 56legacy backup of SRSGUI 56restoring SRScommand line 89, 99GUI 60Exchange Server 2003authorityinstalling 29operating 20, 129legacy backup of KMSGUI 56legacy backup of SRSGUI 56restore 10restoring SRScommand line 89, 99GUI 60Exchange Server 2007authorityoperating 129restore 10exclude processing 42excsched.log 121excserver parameterand backup command 79and cluster 54and GUI invocation 54and query exchange command 65and restore command 89cluster 61FFAQ 125features 2filesData Protection for Exchangeoptions 73, 81, 94, 101dsm.opt 39, 117dsmcutil.exe 40dsmcutil.hlp 40dsmcutil.txt 40excfull.cmd 116files (continued)excfull.log 121excsched.log 121readmedpexc_enu.htm 25READMEDPEXC_enu.htm 29tdpexc.cfgand backup command 78and changetsmpasswordcommand 104and GUI invocation 54and query exchange command 64and query tdp command 68and query tsm command 72and restore command 89, 93and restorefiles command 98and set command 109setting 43vsspolicy option 44tdpexc.log 128and backup command 79and changetsmpasswordcommand 104and GUI 51and query exchange command 65and query tdp command 68and query tsm command 72and restore command 90and restorefiles command 99and set command 108tdpexcc.exe 63Tivoli Storage Manager optionsfile 73, 81, 93, 100, 105fixes, obtaining xviifromexcserver parameterand query tsm command 72and restore command 90and restorefiles command 99fromreplica parameterand backup command 79full backupdescription 6strategy 15full plus differential backupstrategy 15full plus incremental backupstrategy 15Gglossary 203GUIand changetsmpasswordcommand 53and configuring Data Protection forExchange 49and tdpexc.cfg file 49Backup and Restore Window 55cluster 61edit menu 49functions 49help menu 53legacy backup 56legacy backup of KMS 56legacy backup of SRS 56list view 49menu bar 49messages 55GUI (continued)restore 58, 60restore options 60selecting items 55toolbar 54tree view 49utilities menu 53view menu 52VSS backup 56VSS off-loaded backup 57GUI parametersbackupmethod 50buffers 50buffersize 50dateformat 51Default Backup Destination 51language 51localdsmagentnode 52logfile 51logprune 51mountwait 50numberformat 51remotedsmagentnode 52retries 50templogrestorepath 50timeformat 51Hhardware provider 9hardware requirements 27helponline 22help commandexample 111, 113overview 110syntax diagram 110help menudescription 53Iinclude processing 42include/exclude examples 42include.encrypt option 40incremental backupdescription 6information centers, searching forproblem resolution xviiinstallationconfiguring options 39considerations 29hardware requirements 27overview 25procedure 29quick configuration 123registering Data Protection forExchange 36installing Data Protection for Exchangeon multiple servers (silent) 131unattended (silent) 131instantrestore parameterand restore command 90Internetsearching for problem resolution xviiIndex 211

IBM Confidentialinto parameterand restorefiles command 99intosg parameterand restore command 90KKMSlegacy backupGUI 56knowledge bases, searching for problemresolution xviiLLAN Free 40description 21language parameterand GUI 51and set command 107languagessupported by Data Protection forExchange 23legacy backupKMSGUI 56SRSGUI 56Legacy backupand VSS 15hardware requirements 27method 7overview 4quick configuration 123Legacy restorehardware requirements 27method 12list viewdescription 49local shadow volumesstorage space 19localdsmagentnode parameterand GUI 52and set command 108logfile parameterand backup command 79and changetsmpasswordcommand 104and GUI 51and query exchange command 65and query tdp command 68and query tsm command 72and restore command 90and restorefiles command 99and set command 108loggingcircular 6logprune parameterand backup command 80and changetsmpasswordcommand 105and GUI 51and query exchange command 65and query tdp command 69and query tsm command 73and restore command 91logprune parameter (continued)and restorefiles command 99and set command 108Mmanagement class 35manualssee publications xivmenu bardescription 49messagesGUI 55verification 48migrationprevious versions 29, 128mountdatabases parameterand restore command 91mountwait parameterand backup command 80and GUI 50and restore command 91and restorefiles command 100and set command 108msiexec.exeused for silent installation 134Nnode nameData Protection for Exchangerecommendations 36Off-loaded backup 38proxy nodes 37VSS 37nodename option 39numberformat parameterand GUI 51and set command 108Oobject parameterand restore command 91and restorefiles command 100Off-loaded backupconfiguration procedure 46description 10hardware requirements 27node names 38offload parameterand backup command 80, 81online help 22online publicationsaccessing xivoperating environment 1optionsGUI restoreauto select 52disable VSS instant restore 61mountdatabases 61restore into 61run recovery 60Show all objects 52Show only Active objects 52ordering publications xivoverview 1Pparameters/activeand query tsm command 72/alland query tsm command 72/backupdestinationand backup command 78and restore command 88and set command 106/backupmethodand backup command 78and restore command 88and set command 107/buffersand backup command 78and restore command 88and restorefiles command 98and set command 107/buffersizeand backup command 78and restore command 89and restorefiles command 98and set command 107/configfileand backup command 78and changetsmpasswordcommand 104and GUI invocation 54and query exchange command 64and query tdp command 68and query tsm command 72and restore command 89and restorefiles command 98and set command 109/dateformatand set command 107/excapplicationand backup command 79and restore command 89and restorefiles command 99/excserverand backup command 79and cluster 54and GUI invocation 54and query exchange command 65and restore command 89/fromexcserverand query tsm command 72and restore command 90and restorefiles command 99/fromreplicaand backup command 79/instantrestoreand restore command 90/intoand restorefiles command 99/intosgand restore command 90/languageand set command 107/localdsmagentnodeand set command 108212 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialparameters (continued)/logfileand backup command 79and changetsmpasswordcommand 104and query exchange command 65and query tdp command 68and query tsm command 72and restore command 90and restorefiles command 99and set command 108/logpruneand backup command 80and changetsmpasswordcommand 105and query exchange command 65and query tdp command 69and query tsm command 73and restore command 91and restorefiles command 99and set command 108/mountdatabasesand restore command 91/mountwaitand backup command 80and restore command 91and restorefiles command 100and set command 108/numberformatand set command 108/objectand restore command 91and restorefiles command 100/offloadand backup command 80/partialand restore command 92and restorefiles command 100/quietand backup command 81and restore command 92and restorefiles command 100/recoverand restore command 92/remotedsmagentnodeand set command 109/retriesand set command 109/skipintegritycheckand backup command 81/templogrestorepathand restore parameter 93and set command 109/timeformatand set command 109/tsmnodeand backup command 81and changetsmpasswordcommand 105and query tsm command 73and restore command 93and restorefiles command 100/tsmoptfileand backup command 81and changetsmpasswordcommand 105and GUI invocation 54parameters (continued)/tsmoptfile (continued)and query tsm command 73and restore command 93and restorefiles command 101/tsmpasswordand backup command 81and query tsm command 73and restore command 94and restorefiles command 101backupmethodand GUI 50buffersand GUI 50buffersizeand GUI 50dateformatand GUI 51Default Backup Destinationand GUI 51languageand GUI 51localdsmagentnodeand GUI 52logfileand GUI 51logpruneand GUI 51mountwaitand GUI 50numberformatand GUI 51remotedsmagentnodeand GUI 52retriesand GUI 50templogrestorepathand GUI 50timeformatand GUI 51partial parameterand restore command 92and restorefiles command 100passwordaccess option 40performance 20policy set 35policy settingscopy group 35Data Protection for Exchange andTivoli Storage Manager 18domain 9, 35management class 35policy set 35recommended 35storage pool 36problem determinationdescribing problems xxdetermining business impact xixsubmitting problems xxproxy nodes 37publicationsaccessing online xivordering xivQquery exchange commandand /configfile parameter 64and /excserver parameter 65and /logfile parameter 65and /logprune parameter 65and Recovery Storage Group 64example 66, 67overview 64syntax diagram 64query tdp commandand /configfile parameter 68and /logfile parameter 68and /logprune parameter 69example 69overview 68syntax diagram 68query tsm commandand /active parameter 72and /all parameter 72and /configfile parameter 72and /fromexcserver parameter 72and /logfile parameter 72and /logprune parameter 73and /tsmnode parameter 73and /tsmoptfile parameter 73and /tsmpassword parameter 73example 74overview 70syntax diagram 70quick configuration (Legacy) 123quiet parameterand backup command 81and restore command 92and restorefiles command 100Rreadmedpexc_enu.htm 25READMEDPEXC_enu.htm 29recover parameterand restore command 92Recovery Storage Groupand backup strategy 11and mounting databases 85and query exchange command 64and restore 11, 59, 61and restore command 85output example 66procedure 138requirements 138registration 36remotedsmagentnode parameterand GUI 52and set command 109restore 89considerations 137database 10SRScommand line 89GUI 60storage group 10command line 87GUI 58transaction log 10types 10Index 213

IBM Confidentialrestore commandand /backupdestinationparameter 88and /backupmethod parameter 88and /buffers parameter 88and /buffersize parameter 89and /configfile parameter 89and /excapplication parameter 89and /excserver parameter 89and /fromexcserver parameter 90and /instantrestore parameter 90and /intosg parameter 90and /logfile parameter 90and /logprune parameter 91and /mountdatabases parameter 91and /mountwait parameter 91and /object parameter 91and /partial parameter 92and /quiet parameter 92and /recover parameter 92and /templogrestorepathparameter 93and /tsmnode parameter 93and /tsmoptfile parameter 93and /tsmpassword parameter 94example 94, 95overview 84syntax diagram 86restore optionsGUIauto select 52disable VSS instant restore 61mountdatabases 61restore into 61run recovery 60Show all objects 52Show only Active objects 52restorefiles commandand /buffers parameter 98and /buffersize parameter 98and /configfile parameter 98and /excapplication parameter 99and /fromexcserver parameter 99and /into parameter 99and /logfile parameter 99and /logprune parameter 99and /mountwait parameter 100and /object parameter 100and /partial parameter 100and /quiet parameter 100and /tsmnode parameter 100and /tsmoptfile parameter 101and /tsmpassword parameter 101example 101, 102overview 96syntax diagram 97retries parameterand GUI 50and set command 109SSAN Volume Controller 9considerations 9security 20set commandand /backupdestinationparameter 106and /backupmethod parameter 107and /buffers parameter 107and /buffersize parameter 107and /configfile parameter 109and /dateformat parameter 107and /language parameter 107and /localdsmagentnodeparameter 108and /logfile parameter 108and /logprune parameter 108and /mountwait parameter 108and /numberformat parameter 108and /remotedsmagentnodeeparameter 109and /retries parameter 109and /templogrestorepathparameter 109and /timeformat parameter 109example 110overview 106syntax diagram 106setup.exeused for silent installation 133silent installation of Data Protection forExchange 131software provider 9Software Supportcontacting xixdescribing problems xxdetermining business impact xixreceiving weekly updates xviiisubmitting problems xxSRSbackupcommand line 79legacy backupGUI 56restore 60command line 89restorefilescommand line 99storage groupbackupcommand line 77legacy backupGUI 56restore 58command line 87restorefilescommand line 97VSS backupGUI 56VSS off-loaded backupGUI 57storage pool 36syntax diagramsbackup command 76changetsmpassword command 103help command 110query exchange command 64query tdp command 68query tsm command 70restore command 86restorefiles command 97syntax diagrams (continued)set command 106system provider 9Ttdpexc.cfg fileand backup command 78and changetsmpasswordcommand 104and GUI 49and GUI invocation 54and query tdp command 68and query tsm command 72and restore command 89, 93and restorefiles command 98and set command 109parameterssetting 43query exchange 64tdpexc.log fileand backup command 79and changetsmpasswordcommand 104and GUI 51and query exchange command 65and query tdp command 68and query tsm command 72and restore command 90and restorefiles command 99and set command 108tdpexcc.exeoverview 63templogrestorepath parameterand GUI 50and restore command 93and set command 109timeformat parameterand GUI 51and set command 109Tivoli software information center xivTivoli Storage Managerpolicy settings 18Tivoli Storage Manager options file 73,81, 93, 100, 105Tivoli Storage Manager schedulerautomate backups 115example 115Tivoli technical training xvitoolbardescription 54training, Tivoli technical xvitransaction logbackup 4restore 10, 84tree viewdescription 49tsmnode parameterand backup command 81and changetsmpasswordcommand 105and query tsm command 73and restore command 93and restorefiles command 100tsmoptfile parameterand backup command 81214 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s Guide

IBM Confidentialtsmoptfile parameter (continued)and changetsmpasswordcommand 105and GUI invocation 54and query tsm command 73and restore command 93and restorefiles command 101tsmpassword parameterand backup command 81and query tsm command 73and restore command 94and restorefiles command 101typeface conventions xxiUutilitiesdsmcutil 40utilities menudescription 53VVersion 1backup strategy 29, 128view menudescription 52VSSand Legacy backups 15cluster 9, 16, 33, 34DS and SAN Volume Controllerstorage 33hardware provider 9N-series and NetAppstorage 33node names 37Off-loaded backup 10proxy nodes 37software provider 9system provider 9VSS Backupconsiderations 8method 7overview 4VSS Fast Restoremethod 12VSS Instant Restorehardware requirements 27method 12VSS operationsoutput example 67VSS Provider 5VSS Requestor 5VSS Restoremethod 12VSS Serviceoverview 5VSS Writer 5vsspolicy option 44Index 215

216 Storage Manager for Mail 5.5: Data Protection for Microsoft Exchange Server Installation and User’s GuideIBM Confidential

Program Number: 5608-APE, 5608-CSSIBM ConfidentialPrinted in USASC32-9058-04