Veritas NetBackup for Microsoft Exchange Server Administrator s Guide

Transcription

1 Veritas NetBackup for Microsoft Exchange Server Administrator s Guide Windows Release 6.5

2 Veritas NetBackup for Microsoft Exchange Server Administrator s Guide Copyright Symantec Corporation. All rights reserved. NetBackup 6.5 Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright , RSA Data Security, Inc. Created All rights reserved. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software and commercial computer software documentation as defined in FAR Sections and DFARS Section Symantec Corporation Stevens Creek Blvd. Cupertino, CA Printed in the United States of America.

3 Third-party legal notices Licensing and registration Technical support Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder. All third-party copyrights associated with this product are listed in the accompanying release notes. Windows is a registered trademark of Microsoft Corporation. Veritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions. For technical assistance, visit and select phone or support. Use the Knowledge Base search feature to access resources such as TechNotes, product alerts, software downloads, hardware compatibility lists, and our customer notification service.

4 4

5 Contents Chapter 1 Chapter 2 Chapter 3 Introduction to NetBackup for Exchange Server Exchange 2007 support... 9 Features...10 Backup operations...12 Automatic backups...12 Manual backups...13 User-directed backups...13 Exchange Server files that are backed up...13 Restore operations...17 Server-directed restores...17 Redirecting a restore to a different client...17 Redirecting a restore to a different path...17 Restoring Exchange 2003 or Exchange 2007 to a recovery storage group...18 Related resources...18 Installing the NetBackup for Exchange Server agent Verifying the installation prerequisites...19 Operating system and platform compatibility...19 NetBackup software...20 Database agent...20 Cluster software...21 Registering the license key...21 Configuration User interface terminology notes...23 Configuring NetBackup for backups and restores of individual mailboxes and public folders...24 Creating a user account for the NetBackup Client Service...24 Configuring the NetBackup Client Service log on account...26 Configuring NetBackup to use the mailbox that is associated with the NetBackup Client Service account...27 Configuring the account that is used for Exchange Server restores...28 Configuring Single Instance Store backups...29 Configuring a backup policy for a database...30

6 6 Adding a new policy Adding schedules Adding clients Adding backup selections Testing configuration settings Chapter 4 Chapter 5 Using NetBackup for Exchange Server Prerequisites for performing backups and restores Performing user-directed backups Specifying the server (and client) for a backup operation Backup options Performing user-directed backups of Exchange Server 2000 or later Performing user-directed backups of Exchange Server 5.x Performing user-directed backups of mailboxes and public folders Specifying the server, client, and policy type for a restore operation Performing restores of Exchange Server Before performing restores Existing transaction logs Restore options Restoring storage groups or storage group databases Restoring the Key Management Service or Site Replication Service Restoring Exchange 2003 or later to the recovery storage group Restoring Exchange Server 5.x objects Restoring the 5.x public and private databases separately from a Backup Exec backup Performing restores of Exchange mailboxes and public folders Restore options Restoring individual mailboxes, mailbox folders, public folders, or messages Redirecting a restore of mailbox objects or public folders to a different path Redirecting a restore to a different client Using NetBackup for Exchange Server with Snapshot Client NetBackup Snapshot Client for Exchange Server overview Supported platforms Limitations How does Snapshot Client for Exchange Server work? What is backed up? Consistency checks on database and log files... 82

7 7 General configuration...83 Configuration requirements...83 Configuring a pause in consistency checks...84 Backing up transaction log files...85 Configuring a snapshot backup...86 Configuration steps...86 Configuration requirements for Exchange...87 Configuring a Snapshot Client policy...87 Instant recovery configuration...89 Restore Methods...90 Transaction logs and instant recovery...91 Configuration steps...91 Configuration requirements...91 Configuration requirements for Exchange...92 Configuring a Snapshot Client policy with instant recovery...92 Configuring off-host backups...98 Performing user-directed snapshot backups of Exchange Server...98 Restoring snapshot images Restore options Performing a snapshot restore Redirecting a restore to a different client Chapter 6 Index Troubleshooting Debug logging Backup operation debug logging Restore operation debug logging Setting the debug level Verifying Exchange online backups Viewing Event Viewer logs on an off-host server Connecting to the remote server from within Event Viewer Installing the Exchange System Management Tools on the remote server Viewing the status of a NetBackup operation Operational reports Progress reports Transaction logs Setting up an alternate server for restores Disaster recovery of Exchange Server Disaster recovery of Exchange Server 2000/ Disaster recovery of Exchange Server

8 8

9 Chapter 1 Introduction to NetBackup for Exchange Server NetBackup for Microsoft Exchange Server extends the capabilities of NetBackup to include online backups and restores of Exchange databases when Exchange Server has been installed. This capability is provided as an add-on or extension to the NetBackup for Windows client software. Because this product is tightly integrated with the Backup, Archive, and Restore interface for Windows, this document only gives an overview of NetBackup functionality. In general, backup and restore operations for Exchange files are identical to other NetBackup file operations, except where noted in this document. Microsoft Exchange Server is referred to as Exchange Server or Exchange. NetBackup for Microsoft Exchange Server is referred to as NetBackup for Exchange Server. Exchange 2007 support At the time of release of NetBackup 6.5 for Microsoft Exchange, some documented capabilities are not yet available: Instant Recovery for Exchange Server Mailbox Backup for Exchange 2007 Snapshot Backup for Exchange 2007 These capabilities are planned for availability in the next release update, or NetBackup

10 10 Introduction to NetBackup for Exchange Server Features Features Table 1-1 Feature Online backups Features of NetBackup for Exchange Server Description Exchange Server data and transaction logs can be backed up without taking the Exchange Server offline. Exchange services and data remain available during the Exchange Server backup. Minimal backup time Exchange Server Backup methods Tight NetBackup integration Central administration Media management Automated backups Restore operations An administrator has the choice of to perform full or incremental backups (differential incremental backup or cumulative incremental backup). A full backup may take considerable time, so it may be performed infrequently. In the interim, any updates that have occurred since the full backup can be quickly and incrementally backed up through a transaction log backup. In the event of a failure, the full backups and incremental backups would be restored. During recovery, the Exchange Server updates the databases and applies each of the logged transactions to the database. After the Exchange Server recovery has completed, the system is brought back to the state as it existed when the last incremental backup was performed. NetBackup supports all Exchange Server backup methods: full backups, cumulative incremental backups, differential incremental backups, and copy backups. Tight integration with NetBackup means two things: 1 An administrator already familiar with NetBackup procedures and software can easily configure and use NetBackup to perform Exchange Server backup and restore operations. 2 Features and strengths of the NetBackup product suite are available to the Exchange Server backup user. These features include software data compression and encryption, scheduled and user-directed operations, backups of multiple data streams, and in-line tape copy. Many of these features are described, in detail, in the NetBackup Administrator s Guide, Volume I. Administrators can define, back up, and restore Exchange Servers and other NetBackup client machines from a central location. Exchange Server backups can be saved directly to a wide variety of storage devices that the NetBackup master server supports. Administrators can set up schedules for automatic, unattended backups for local or remote clients across the network. These backups can be full or incremental and are managed entirely by the NetBackup server from a central location. The administrator can also manually back up the clients. An administrator using the Backup, Archive, and Restore interface can browse backups and select the ones to be restored.

11 Introduction to NetBackup for Exchange Server Features 11 Table 1-1 Feature Redirected restores Features of NetBackup for Exchange Server Description In a redirected restore, you restore an object (database, mailbox, folder, or message) to a new location. Individual mailbox backup and restore Exchange 2000 or later backup and restore features Backup and restore of the Exchange Public Store Single Instance Storage (SIS) of mailbox message attachments Compression of backups Administrators can perform backup and restore operations on individual mailboxes and folders. The capabilities of this feature are: Scheduled backups of individual mailboxes and folders User-directed backups of individual mailboxes and folders Restores of individual mailboxes, folders, or messages. These restores can be performed using the Backup, Archive, and Restore interface (on the server or on the client). Or you can use the Remote Administration Console for Windows or UNIX. NetBackup can back up and restore storage groups, as well as back up and restore databases within the storage group. The capabilities of this feature are: Scheduled backups of individual storage groups and databases User-directed backups of individual storage groups and databases Restores of individual storage groups and databases.these restores can be performed using the Backup, Archive, and Restore interface (on the server or on the client). Or you can use the Remote Administration Console for Windows or UNIX. (Exchange 2000) NetBackup can perform backups and restores of the Exchange Key Management Server (KMS) (Exchange 2000/2003) Exchange Site Replication Service (SRS) databases. NetBackup can back up and restore the Exchange Public Store. The capabilities of this feature are: Scheduled backups of individual folders User-directed backups of individual folders Restores of individual folders or messages. These restores can be performed using the Backup, Archive, and Restore interface (on the server or on the client). Or you can use the Remote Administration Console for Windows or UNIX. Users can enable Single Instance Storage for message attachments so only one copy of an attachment is written to the backup. Compression increases backup performance over the network and reduces the size of the backup image that is stored on the disk or tape.

12 12 Introduction to NetBackup for Exchange Server Backup operations Table 1-1 Feature Snapshot Client Cluster support Features of NetBackup for Exchange Server Description This separately-priced option allows NetBackup to perform backups and restores of Exchange 2003 or later objects using snapshot methodology. NetBackup can perform backups using the primary (or local) client where the Exchange server resides or using an alternate client. The latter reduces the backup I/O burden on the primary client. If the snapshot was preserved with the instant recovery option, NetBackup tries to restore the database with the fastest means possible. Usually, a rollback of the snapshot volume(s) which contain the Exchange files is the fastest means. However, the ability to perform a rollback depends on several things: the configuration of the Exchange database files, the contents of the volumes, and configuration of the disk array. If a volume rollback cannot be performed, the files that are required for restoration are copied from the snapshot volume to the original volume. The NetBackup for Exchange Server agent supports Microsoft Cluster Server (MSCS) environment and Veritas Cluster Server (VCS). Refer to the Veritas NetBackup Enterprise Server 6.5 Cluster Compatibility list. This list contains information on the versions of Exchange Server that are supported with the cluster environments. Backup operations Automatic backups NetBackup provides three methods to perform backups: automatic, manual, and user-directed. For more information on these backup methods and other administrator-directed activities, refer to the NetBackup Administrator s Guide, Volume I. The NetBackup administrator can schedule the full backups and the incremental backups that occur automatically and unattended. (Incremental backups can be differential incremental backups or cumulative incremental backups.) Automatic backups meet most backup requirements. You cannot perform an automatic copy backup. To perform a copy backup, run a user-directed backup.

13 Introduction to NetBackup for Exchange Server Backup operations 13 Manual backups User-directed backups NetBackup allows the administrator to perform immediate manual backups of the files that are associated with any policy, client, or schedules. The manual backup option can be useful for the following situations: Testing a configuration When workstations miss their regular backups Before installing new software (to preserve the old configuration) Preserving records before a special event such as when companies split or merge Using the Backup, Archive, and Restore interface, the user can perform backups of Exchange Server, mailboxes, and public folders. The user can also perform a user-directed backup to create a copy backup. A user-directed backup of Exchange databases is similar a backup of normal files. Exchange Server files that are backed up The following files can be backed up during a backup operation. Except where noted, the same files are backed up whether frozen image methodology is used to back up the files or not. (Frozen image methodology is available with the Snapshot Client feature.) Database files Different database files are backed up for Exchange Server 2007, Exchange 2000/2003 and for Exchange Server 5.x. Exchange Server 2000 or later For Exchanger Server 2000 and 2003, there can be up to 20 database stores. Each database store consists of 2 database files. For Exchange 2007, there can be up to 50 database stores. Each database store contains only one database file. By default, the database file is named database_name.edb.

14 14 Introduction to NetBackup for Exchange Server Backup operations The following table gives the database names and their default locations for the first Exchange Storage group. Table 1-2 Default locations for Exchange 2000 or later database files Database File Name Default Directory Mailbox Store Priv1.edb...\exchsrvr\mdbdata Priv1.stm...\exchsrvr\mdbdata Note: Subsequent storage groups and databases may have different locations and names (user-defined). Exchange Server 5.x The Exchange Server has three database files, one for the Directory and two for the Information Store. The following table gives the database names and their default locations. Table 1-3 Default locations for Exchange 5.x database files Database File Name Default Directory Directory Dir.edb...\exchsrvr\dsadata Information Store - Public Pub.edb...\exchsrvr\mdbdata Information Store - Private Priv.edb...\exchsrvr\mdbdata Database patch files (Exchange 5.5 or pre-exchange 2000, Service pack 2) Database patch files are used to handle transactions being written to the database during a backup. During the backup operation, data is read from the.edb file. If a transaction causes an update to a part of the.edb file that has already been backed up, then the update is written to the patch file for that database. Patch files only exist during the backup process. These patch files are used during the Exchange Server recovery process. They update the restored

15 Introduction to NetBackup for Exchange Server Backup operations 15 database file with the transactions that were in progress during the backup. The following table gives the names of the patch files and their default locations. Table 1-4 Default locations for patch files Database Patch File File Name Default Directory Directory Dir.pat...\exchsrvr\dsadata Information Store - Public Pub.pat...\exchsrvr\mdbdata Information Store - Private Priv.pat...\exchsrvr\mdbdata Transaction logs For performance and recoverability, the Exchange database uses transaction logs to accept, track, and maintain data. All transactions are first written to transaction logs and memory, and then to their respective databases. Transaction logs can be used to recover Directory or Information Store databases in the event that a failure has corrupted the database. The Information Store can have up to five separate databases but transaction logs are kept in a single set. Transactions are first written to the edb log or e0y log file and then later written to the database. Therefore, the current actual or effective database is a combination of the uncommitted transactions in the transaction log file and the actual edb or e0y database file. When the log file is filled with transaction data, it is renamed and a new edb or e0y log file is created. When the log file is renamed, the other renamed log files are stored in the same subdirectory. The renamed log files are named in a sequential numbering order, using hexadecimal. For full backups and differential incremental backups, the committed transaction logs are truncated (deleted) by Exchange after a successful backup. Note: After every 5MB of transaction log data is written, a new log is created. The log is created even though the transaction data may not be committed to the database. There may be several transaction logs that contain uncommitted data, and therefore they are not purged. Transactions in log files are committed to the respective edb or e0y file when the service is shut down normally. For example, consider when the Information Store service experiences a normal shutdown (service shuts down with no errors). Any transactions that existed in log files and not in the Priv.edb and or Pub.edb files are committed to the edb files. Log files should not be manually purged; instead, purge logs through the backup process.

16 16 Introduction to NetBackup for Exchange Server Backup operations The following process takes place during a full backup: Database files are written to the backup media. (Exchange 5.5 or pre-exchange 2000, Service Pack 2) Patch files are created to accommodate updates to the database during the backup. Transaction logs are written to the backup media. (Exchange 5.5 or pre-exchange 2000, Service Pack 2) Patch files are written to the backup media. Committed transaction logs are truncated (deleted) by Exchange. These logs are no longer required since they have been committed to the database file and they have been written to the backup media. Exchange 2007 The following table gives the names of the transaction logs and their default locations. Table 1-5 Default locations for Exchange 2007 transaction logs Database Transaction Log File Name Default Directory Information Store exxyyyyyyyy.log..\exchsrvr\mdbdata XX is the storage group number (in hex). YYYYYYYY is the log file number (in hex). Note that the log file number now has 8 digits, instead of 5 digits. The size of the transaction logs has changed from 5 MB in Exchange 2000/2003 down to 1MB in Exchange Exchange 2000/2003 The following table gives the names of the transaction logs and their default locations. Table 1-6 Default locations for Exchange 2000/2003 transaction logs Database Transaction Log File Name Default Directory Information Store e0yxxxxx.log..\exchsrvr\mdbdata Where Y is a number from 0-3 representing the storage group, e.g., e00.log, e01.log, e02.log, e03.log. XXXXX is a five-digit hexadecimal number that is incremented each time an e0y log file is renamed.

17 Introduction to NetBackup for Exchange Server Restore operations 17 Exchange 5.5 logs The following table gives the names of the Exchange 5.5 transaction logs and their default locations. Table 1-7 Default locations for Exchange 5.5 transaction logs Database Transaction Log File Name Default Directory Directory edbxxxxx.log..\exchsrvr\dsadata Information Store edbxxxxx.log..\exchsrvr\mdbdata Where XXXXX is a five digit hexadecimal number that is incremented each time an edb log file is renamed. Restore operations With the Backup, Archive, and Restore interface, the administrator can browse for Exchange Server backups and select the ones to restore. Server-directed restores An administrator can browse Exchange Server databases and select the ones to be restored. NetBackup allows you to select the NetBackup server from which files are restored, to view the backup history, and to select items to restore for a specific client or other clients that were backed up by the selected NetBackup server. Redirecting a restore to a different client Databases or directories can be restored to a client other than the one from which they were backed up. The NetBackup administrator must enable this configuration and the database agent must be installed on the alternate client. The administrator can direct restores to any NetBackup client (regardless of which client performed the backup). The administrator can use the NetBackup Administration Console on the master server or the Remote Administration Console to redirect a restore. See the NetBackup Administrator s Guide for the configuration that is needed for this type of redirected restore. Redirecting a restore to a different path A user can restore mailbox objects and Public folder objects to directories that are different from the directories from which the objects were backed up.

18 18 Introduction to NetBackup for Exchange Server Related resources Database objects should not be redirected to different paths. Database objects can be redirected to an Exchange Recovery Storage Group. A user can restore Exchange databases to directories that are different from the directories from which the databases were backed up. Restoring Exchange 2003 or Exchange 2007 to a recovery storage group Related resources NetBackup supports the restore of Exchange 2003 or Exchange 2007 to a recovery storage group. You may also need the following resources from Microsoft Corporation: Exchange Server white papers and FAQs (go to and search for Disaster Recovery ) Microsoft Exchange Administrator's Guide Microsoft Exchange Concepts and Planning Guide Microsoft TechNet Microsoft BackOffice Resource Kit

19 Chapter 2 Installing the NetBackup for Exchange Server agent In order to install the database agent, perform the following tasks: Verify the installation prerequisites. Perform this task before enabling this agent. The database agent software is installed when you install NetBackup, so verify these prerequisites before enabling the agent. Register the license key for the agent. Verifying the installation prerequisites NetBackup for Exchange Server is installed with the NetBackup server and client software, but you must confirm that the installation prerequisites in this section are met before you enable the database agent. These requirements apply for remote and local installations. Operating system and platform compatibility Verify that NetBackup for Exchange Server is supported on your operating system or platform. To verify compatibility 1 Go to the technical support Web page: 2 In the Product Lookup field, type in NetBackup Enterprise Server and click on the > button. 3 From the list on the right, click on Compatibility List.

20 20 Installing the NetBackup for Exchange Server agent Verifying the installation prerequisites 4 In the list of documents, click Veritas NetBackup Enterprise Server (tm) x.x/ NetBackup Server x.x Database Agent Compatibility (Updated date). For x.x, look for the current release. For date, look for the most recent date. For information on supported cluster environments for NetBackup for Exchange Server, see NetBackup (tm) x.x Cluster Compatibility (updated date). 5 Click the link for the PDF document, which is a downloadable file that enables you to view the supported database spreadsheet for this release. 6 Read the document and verify that the software in your environment is compatible with the NetBackup and the database agent. NetBackup software Database agent Verify that the following requirements are met for the NetBackup server and client software: The NetBackup server software is installed and operational on the NetBackup server. The NetBackup server platform can be any that NetBackup supports. For installation information, see the NetBackup Installation Guide. The NetBackup client software is installed on the client that has the databases you want to back up. This step also installs the database agent. (If the database client is also a NetBackup server, the client software is installed along with the server software.) The install_path\netbackup directory must exist on the client. For installation information, see the NetBackup Installation Guide. Make sure that you configure any backup media that the storage unit uses. The amount of backup media that is required depends on the devices that are used, the sizes of the databases that you want to back up, the amount of data that you want to archive, the size of your backups, and the frequency of backups or archives. For information on using Media Manager, see the NetBackup Administrator s Guide, Volume I. Verify that the follow requirements are met for the database software. The Exchange Server software is installed and operational on each client.

21 Installing the NetBackup for Exchange Server agent Registering the license key 21 Cluster software Verify the following requirements if you are enabling the database agent on a NetBackup server configured in a NetBackup cluster: The Exchange vendor software is installed and operational on each node to which NetBackup can failover. The NetBackup server software is installed and configured to work in a NetBackup cluster. Follow the instructions in the NetBackup Installation Guide. The NetBackup server installation procedure installs the database agent software along with the server and client software. After all other prerequisites are met, you only need to register the license key for the agent on each NetBackup server in order to enable the agent. Registering the license key The database agent is installed with the server and client software. To use this agent, register a valid license key for it on the master or media server. In a NetBackup cluster, register the key on each node on which the NetBackup server is installed. To register a license key 1 On the master or media server, open the NetBackup administration console. 2 Choose Help > License Keys. 3 Click the New button. 4 Type in the license key and click Add. For information on adding license keys, see the NetBackup Administrator s Guide, Volume I.

22 22 Installing the NetBackup for Exchange Server agent Registering the license key

23 Chapter 3 Configuration The following topics provide information on how to configure NetBackup to perform backup and restore operations of Exchange Server. Configuring NetBackup for backups and restores of individual mailboxes and public folders Configuring the account that is used for Exchange Server restores Configuring a backup policy for a database Configuring Single Instance Store backups Testing configuration settings User interface terminology notes You can perform many of the configuration steps in this chapter from the NetBackup administration console on the master server. Depending on your master server s platform, the console is available in one or two forms. NetBackup supports a Java interface for both Windows and UNIX master servers. In addition, NetBackup supports a Windows interface for Windows master servers. The Java and Windows interfaces are nearly identical. If interface differences exist in the configuration procedures, this manual uses the following headings to identify the interface being described: From the Windows interface: From the Java interface:

24 24 Configuration Configuring NetBackup for backups and restores of individual mailboxes and public folders Configuring NetBackup for backups and restores of individual mailboxes and public folders The following configuration must be performed so that NetBackup can back up and restore individual mailboxes and mailbox folders, and folders within the public folders. Note: If in a cluster, these steps need to be performed on each Exchange node in the cluster. Creating a user account for the NetBackup Client Service on page 24 Configuring the NetBackup Client Service log on account on page 26 Configuring NetBackup to use the mailbox that is associated with the NetBackup Client Service account on page 27 Creating a user account for the NetBackup Client Service For NetBackup to gain access to the mailboxes and folders to perform backup and restore operations, the NetBackup Client Service must be associated with a valid Exchange mailbox. Symantec recommends that you create a uniquely named mailbox. Creating a user account for the NetBackup Client Service (Exchange 2000/2003) To create a user account for the NetBackup Client Service 1 Use Active Directory Users and Computers to create a user account that has a mailbox with a unique name. A unique name is one that does not already exist within the Exchange Organization. This name cannot be contained as a set of characters in an existing name. For example: EXCH1 is entered as the unique mailbox name, and other mailbox names such as EXCH1BACKUP or BACKUPEXCH1 exist. The backup or restore of individual mailboxes or both fail. 2 After you create the account, double-click the account, click the Members Of tab, and add this account to the Domain Admins group. 3 Open Exchange System Manager. 4 Right-click the Exchange Organization and select Delegate Control. 5 Click Next.

25 Configuration Configuring NetBackup for backups and restores of individual mailboxes and public folders 25 6 On the Users or the Groups screen, click Add. 7 In the Delegate Control dialog box, provide the following information. Group or User Specify the name of the account that was created in step 1. Role Select Exchange Full Administrator. 8 Complete the Delegation wizard. 9 If you have an Active/Active configuration, continue with the next section, Granting the NetBackup Client Service account advanced permission. 10 Continue with the instructions for Configuring the NetBackup Client Service log on account on page 26. Granting the NetBackup Client Service account advanced permission If you have an Active/Active configuration, the account created for the NetBackup Client Service must also be granted Receive As and Send As advanced permission on each virtual Exchange Server in the configuration. To grant the NetBackup Client Service account advanced permission 1 Open Exchange System Manager. 2 Locate the virtual Exchange Server. 3 Right-click the virtual Exchange Server and select Properties. 4 Click the Security tab. 5 Select the account that was created in Creating a user account for the NetBackup Client Service on page Under Permissions, select Receive As and Send As. 7 Click OK. 8 Repeat step 2 through step 7 for each virtual Exchange Server in the cluster. 9 Continue with the instructions for Configuring the NetBackup Client Service log on account on page 26. Creating a user account for the NetBackup Client Service (Exchange 5.x) For Exchange 5.x, if a mailbox is not created for the NetBackup Client Service, you can use any existing mailbox on the Exchange Server to which the NetBackup Client Service account is granted log on rights.

26 26 Configuration Configuring NetBackup for backups and restores of individual mailboxes and public folders Note: Certain minimum rights are required for backing up and for restoring a mailbox. These rights are Modify User Attributes and Modify Administrator Attributes. If you grant permissions individually to each mailbox rather than to all mailboxes at the site or at the recipient container level, you can assign the User role. This role allows backups and restores of mailboxes to which permissions have been given. To back up public folders, add the account that was created for backups (the account for the Netbackup Client Service) to the public folders. Give it Reviewer permissions. To create a user account for the NetBackup Client Service 1 Use Exchange Administrator to create a new mailbox. This mailbox must have a unique name or you must assign a unique alias to the mailbox. A unique name is one that does not already exist within the Exchange Organization. This name cannot be contained as a set of characters in an existing name. For example: EXCH1 is entered as the unique mailbox name, and other mailbox names such as EXCH1BACKUP or BACKUPEXCH1 exist. The backups or restores of individual mailboxes or both fail. 2 Double-click the new mailbox and click the General tab. 3 Click Primary Windows NT Account and add the account that was created step 1. 4 Select either a site container or recipient container that contains the mailboxes you want to back up. 5 Click the Properties button. 6 On the Permissions tab, add the account that was created step 1, select the Admin Role, and click OK. 7 Continue with the instructions for Configuring the NetBackup Client Service log on account on page 26. Configuring the NetBackup Client Service log on account By default, the NetBackup Client Service uses Local System as the account on which to log on. To perform backups or restores of individual mailboxes and folders and items in the public folders, change the service account to the Windows domain account you previously created. (See Creating a user account for the NetBackup Client Service on page 24.) To change this account, you must have administrator group privileges.

27 Configuration Configuring NetBackup for backups and restores of individual mailboxes and public folders 27 To change the log on account for the NetBackup Client Service 1 Open the Windows Services application. 2 Double-click the NetBackup Client Service entry. 3 Click the Log On tab. 4 Provide the name of the account you created for Creating a user account for the NetBackup Client Service on page 24. The account must include the domain name, followed by the user account, domain_name\account. For example, recovery\netbackup. 5 Stop and start the NetBackup Client Service. 6 Continue with the instructions for Configuring NetBackup to use the mailbox that is associated with the NetBackup Client Service account on page 27. Configuring NetBackup to use the mailbox that is associated with the NetBackup Client Service account To configure NetBackup to use the mailbox that are associated with the NetBackup Client Service account 1 Open the NetBackup Administration Console or the Remote Administration Console. 2 In the left pane, expand Host Properties. 3 Click Clients. 4 In the right pane, right-click on the Exchange client you want to configure and choose Properties. 5 Expand Windows client and click Exchange. 6 In the Mailbox for message level backup and restore text box, specify the mailbox. The mailbox may be specified as: An Exchange mailbox name. Use the mailbox that was configured in Creating a user account for the NetBackup Client Service on page 24.

28 28 Configuration Configuring the account that is used for Exchange Server restores A fully-qualified name, if you did create a unique mailbox for NetBackup. For example: /O=<Org_Name>/OU=<Site_Name>/CN=<Server_Name>/CN=<Mailbox_Name> A mailbox alias 7 Click OK. 8 Create a backup policy for Exchange mailboxes. See Configuring a backup policy for a database on page 30. Configuring the account that is used for Exchange Server restores Symantec recommends that the NetBackup Client Service use the same account that runs Exchange Services. If you restore from Exchange 5.x and use an account other than the one for Exchange, add the account to the local computer s Administrators group. You do not need to add the account to the Domain Administrators or Domain Admins groups. Exchange 5.x services must be shut down to restore Exchange Server, and Administrator privileges are necessary to shut down services in Windows.

29 Configuration Configuring Single Instance Store backups 29 Configuring Single Instance Store backups Exchange Server uses single-instance storage (SIS) to store mail messages. This capability in Exchange Server allows the database to keep one copy of a message attachment sent to multiple users on the same server. To perform SIS backups, this feature must be enabled on the client where Exchange Server is installed. Note: Only attachments larger than 100K are backed up as SIS objects. Attachments smaller than 100K are backed up with each individual message. To enable Single Instance Store backups 1 Open the NetBackup Administration Console or the Remote Administration Console. 2 In the left pane, expand Host Properties. 3 Click Clients. 4 In the right pane, right-click on the client you want to configure and choose Properties. 5 Expand Windows client and click Exchange. 6 Select Enable single instance backup for message attachments. 7 Click OK.

30 30 Configuration Configuring a backup policy for a database Configuring a backup policy for a database A backup policy for a database defines the backup criteria for a specific group of one or more clients. These criteria include: Storage unit and media to use Policy attributes Backup schedules Clients to be backed up Items (database objects) to be backed up To back up a database environment, you need to define at least one MS-Exchange-Server policy with the appropriate schedules. A configuration can have a single policy that includes all clients, or there can be many policies, some of which include only one client. Most requirements for database policies are the same as for file system backups. In addition to the policy attributes for this database agent, other attributes are available that you should consider. For configuration instructions and information on all the attributes available, see the NetBackup Administrator s Guide, Volume I. Adding a new policy These instructions describe how to add a new backup policy for a database. To configure a backup policy for databases 1 Log on to the master server as administrator (Windows) or root (UNIX). 2 Start the NetBackup Administration console. 3 If your site has more than one master server, choose the one on which you want to add the policy. 4 From the Windows interface: In the left pane, right-click Policies and choose New Policy. From the Java interface: In the left pane, click Policies. In the All Policies pane, right-click the master server, and click New Policy. 5 In the Add a New Policy dialog box, in the Policy name field, type a unique name for the new policy. 6 Click OK.

31 Configuration Configuring a backup policy for a database 31 7 In the Add a New Policy or Change Policy dialog box, in the Policy type list, select the MS-Exchange-Server policy type. The database agent policy type does not appear in the drop-down list unless your master server has a license key for the database agent. 8 Complete the entries on the Attributes tab. For more information, see Description of attributes on page Add other policy information. To add schedules, see Adding schedules on page 32. To add clients, see Adding clients on page 35. To add Exchange objects to the backup selections list, see Adding backup selections. 10 When you have added all the schedules, clients, and backup selections you need, click OK. Description of attributes With a few exceptions, NetBackup manages a database backup like a file system backup. Table 3-1 shows the policy attributes that are different for Exchange backups. This information is used when you add a new policy. Other policy attributes vary according to your specific backup strategy and system configuration. For more information on policy attributes, see the NetBackup Administrator s Guide, Volume I. Table 3-1 Attribute Policy type Policy attribute descriptions Description Determines the types of clients that can be in the policy. In some cases the policy type determines the types of backups that NetBackup can perform on those clients. To use the database agent, you must define at least one policy of type that is MS-Exchange-Server. Allow multiple data streams Specifies that NetBackup can divide automatic backups for each client into multiple jobs. Each job backs up only a part of the list of backup selections.the jobs are in separate data streams and can occur concurrently. The number of available storage units, multiplex settings, and the maximum jobs parameters determine the total number of streams and how many can run concurrently. Not all directives in the backup selections list allow for multiple database streams.

32 32 Configuration Configuring a backup policy for a database Table 3-1 Attribute Keyword phrase Snapshot Client Policy attribute descriptions (continued) Description A textual description of a backup. Useful for browsing backups and restores. See Using NetBackup for Exchange Server with Snapshot Client on page 79 for information on how to configure policies for snapshot methods. Adding schedules Each policy has its own set of schedules. These schedules control initiation of automatic backups and also specify when user operations can be initiated. To add a schedule 1 In the Policy dialog box, click the Schedules tab. To access the Policy dialog box, double-click the policy name in the Policies list in the NetBackup Administration Console. 2 Click New. 3 Specify a unique name for the schedule. 4 Select the Type of backup. See Types of backups on page Specify the other properties for the schedule. See Schedule properties on page If this is the last schedule, click OK. To add more schedules, click Add and repeat step 2 through step 6.

33 Configuration Configuring a backup policy for a database 33 Types of backups Table 3-2 Type of Backup Full Backup Differentialincremental backup User Backup Description of Types of Backups Description For server backups, this schedule type backs up the Exchange Server database and associated transaction logs. All committed transaction logs are truncated (deleted) after they are successfully backed up. For mailbox backups, this schedule type backs up the entire mailbox, including all the folders and messages in that mailbox. For the Public Store, this schedule type backs up the entire Public Store, including all the folders and messages within the Public Store. A differential incremental backup only backs up changes since the last full or differential incremental backup. Differential incremental backups can be performed of databases, the KMS and the SRS services, mailboxes and of the Public Share. When you use this method to back up a database, only transaction logs are backed up. After the successful backup of the transaction logs, all committed logs are truncated (deleted). The truncation of the transaction logs sets the context for the next backup. To perform a full restore the data that is needed is contained in multiple NetBackup images. One image for the full backup and another image for each differential incremental that was performed. A user backup is not automatically scheduled and is initiated on the target client machine. A user-directed backup of a database is identical to a full backup except that the transaction logs are not truncated. User backups are like a snapshot of the databases at a given point in time, without impacting the content of ongoing full and incremental backups. You may want to consider creating a separate policy for User Backup schedule types. Then you can easily separate user-directed and scheduled backups when you restore files. If you decide to create separate policies for User Backup schedule types, the considerations are similar to those for automatic backups. A Backup Selections list is not needed because users select the files to restore.

34 34 Configuration Configuring a backup policy for a database Table 3-2 Type of Backup Cumulativeincremental backup Description of Types of Backups (continued) Description A cumulative incremental backup backs up all changes since the last full backup or differential incremental backup. (However, most configurations do not mix cumulative and differential incremental backups between full backups.) Cumulative incremental backups can be performed of databases, the KMS and the SRS services, mailboxes and of the Public Share. When you use this method to back up databases, only transaction logs are backed up and they are not truncated upon completion of the backup. When you restore databases, transaction logs remain intact since the last full backup. In an Exchange Server data recovery scenario where the transaction logs are all intact, you only need to restore the database from the last full backup and the last cumulative incremental backup. During recovery, Exchange Server replays all the logs in the log folder. The Exchange Server database is brought back to the current date instead of to the time of the last full or incremental backup. Caution: Differential incremental and cumulative incremental backup types fail if database circular logging is configured for the Exchange Server. See Microsoft s Exchange Server Administration Guide for more information on configuring circular logging. Note: You are allowed to configure incremental schedule types, but incremental backups are not performed for individual databases within storage groups. The backup job still runs according to the configured incremental schedules, but the job logs warnings for attempted incremental backups of these objects.

35 Configuration Configuring a backup policy for a database 35 Schedule properties Some of the schedule properties have a different meaning for database backups than for a regular file system backup. Table 3-3 explains the schedule properties. Table 3-3 Property Type of backup Description of schedule properties Description Specifies the type of backup that this schedule controls. The selection list shows only the backup types that apply to the policy you want to configure. For more information, see Types of backups on page 33. Frequency Calendar Retention This setting is used only for scheduled backups and not for user-directed backups. Frequency specifies the period of time that can elapse until the next backup or archive operation begins on this schedule. For example, assume that the frequency is seven days and a successful backup occurs on Wednesday. The next full backup does not occur until the following Wednesday. Typically, incremental backups have a shorter frequency than full backups. This setting is used only for scheduled backups. It is not used for user-directed backups. The Calendar option allows you to schedule backup operations that are based on specific dates, recurring week days, or recurring days of the month. Specifies a retention period for keeping backup copies of files before deleting them. The retention level also denotes a schedules priority within the policy, with Level 9 schedules having the highest priority and Level 0 the lowest. Set the time period to retain at least two full backups of your database. In this way, if one full backup has been lost, you have another full backup to fall back on. For example, if your database is backed up once every Sunday morning, you should select a retention period of at least 2 weeks. Other schedule properties vary according to your specific backup strategy and system configuration. For more information on schedule properties, consult the NetBackup Administrator s Guide, Volume I. Adding clients The Clients list contains a list of the clients that are backed up during an automatic backup. A NetBackup client must be in at least one policy but can be in more than one.