Table of Contents. Page 1 of 122. Install the Exchange idataagents Install the Exchange idataagents - Clustered Environment -Virtual Server

Transcription

1 Page 1 of 122 Features - Exchange Database idataagent Table of Contents Overview System Requirements - Microsoft Exchange Database idataagent Installation Install the Exchange idataagents Install the Exchange idataagents - Clustered Environment -Virtual Server Backup Data - Microsoft Exchange Database Restore Data - Exchange Database Exchange Offline Mining Tool Configuration Subclients - Exchange Database Management Backup Job History Restore Job History Use Cases Cluster Continuous Replication (CCR) Backups

2 Page 2 of 122 Overview - Exchange Server idataagents Choose from the following topics: Introduction Supported Data Types Tree Levels in the Exchange Server idataagents License Requirement Installation Deployment Options Exchange Data Secured by the File System idataagent The Exchange Administrative Hierarchy Unicode Support for Exchange Administrator Account Password Exchange Database Backups Using Volume Shadow Service (VSS) Backups Using the Data Classification Enabler SnapProtect Outlook Add-In Disaster Recovery Considerations Related Topics: Cluster Continuous Replication (CCR) Backups (Exchange 2007 Database) Erase Backup/Archived Data (Exchange Mailbox and Public/Web Folder idataagents) Introduction Microsoft Exchange Servers include several databases that are backed up by the Exchange idataagents. Exchange files can also reside locally on the client computers of an Exchange Server. To secure this data, you must back up these files using the appropriate idataagent for the client computer file system. The Exchange entities that can be backed up by the system are described in detail in the following sections. Back to Top Supported Data Types Exchange Database idataagent Data Protection Operations for the following data types are supported by the Exchange Database idataagent: Information stores Public Folder stores Transaction logs and patch files Exchange organizational data Data Protection Operations for all other data types not mentioned in the above list are not supported by the Exchange Database idataagent. Exchange Mailbox idataagent Data Protection Operations for the following data types are supported by the Exchange Mailbox idataagent: Mailboxes

3 Page 3 of 122 Folders within a mailbox Messages within a folder Attachments A message is anything that is contained within a folder (or within a mailbox). For example, messages, contacts, tasks, journal entries and calendar entries that are maintained within an Exchange mailbox are messages and can be restored individually. Data Protection Operations for all other data types not mentioned in the above list are not supported by the Exchange Mailbox idataagent, including: Exchange Server properties Exchange Public Folder idataagent Data Protection Operations for the following data types are supported by the Exchange Public Folder idataagent: Public Folders Messages or items within a Public Folder Attachments An item is anything that is contained within a Public Folder, such as messages, appointments, contacts, tasks, journal entries and notes. Data Protection Operations for all other data types not mentioned in the above list are not supported by the Exchange Public Folder idataagent, including: Exchange Server properties Exchange Web Folder idataagent Data Protection Operations for the following data types are supported by the Exchange Web Folder idataagent: Web Folders Messages or items within a Web Folder Attachments An item is anything that is contained within a Web Folder, such as messages, appointments, contacts, tasks, journal entries, notes, HTML files, image files, Microsoft Office data files and various other file types. Data Protection Operations for all other data types not mentioned in the above list are not supported by the Exchange Web Folder idataagent, including: Exchange Server properties Using the Appropriate idataagent The Mailbox idataagent is a system administration tool. Use the Mailbox idataagent if you want to restore individual mailboxes, mail messages, contacts, calendar entries, etc. This capability enables you to: Perform small restore operations in the course of day-to-day database use (e.g., retrieve data accidentally deleted by a user). Restore part of a server (i.e., a subset of the mailboxes). This can be especially useful when you need to bring part of a storage group or store online as quickly as possible after a crash. The Public Folder idataagent is also a system administration tool, that can be used to restore Public Folders, messages or other types of data included in Public Folders. The Web Folder idataagent is specifically designed to back up and restore items within the Web Storage System (WSS) file structure residing on the Exchange Server, including the default public folder store.

4 Page 4 of 122 However, we recommend using the Public Folder idataagent to back up the default public folder store in cases where Outlook is used to access the data, and use the Web Folder idataagent for all other stores. The Database idataagent is a disaster recovery tool. Use the Database idataagent if you need to secure more than just the mailboxes on the Exchange Server, or if your primary backup goal is full database recovery in the event of a system crash rather than small day-to-day restore operations. If you have all idataagents installed, you can back up Exchange data using all of them. For example, you may want to run daily backups of your private information store using the Mailbox idataagent. This way, you can restore any individual mailbox on the server to within one day of failure. You can use the Public Folder idataagent to restore Public Folders or Exchange data contained in the Public Folders. If your site uses WSS as part of the Exchange Server to make folder items available via the web, then the Web Folder idataagent can restore those items and their associated metadata. At the same time, you may want to schedule monthly backups of your Exchange Server using the Database idataagent, with daily incremental backups in between. This way you can recover efficiently in the event of a server crash. Although your private information store is backed up by both idataagents, the backups are created differently and serve different purposes. You cannot back up data with one Exchange idataagent and restore it with the other. Data Secured by Exchange idataagents An Exchange Server includes information stores, transaction log files, and patch files. The information store maintains databases and is responsible for storing and retrieving data within those databases. The Database idataagent backs up the stores, along with all of the related transaction logs and patch files. The Mailbox idataagent backs up the mailboxes and messages. The Public Folder idataagent backs up the public information store only. The sections that follow describe each of these entities in detail. The terms 'store', 'message store', 'information store' and 'folder' are used interchangeably in both Microsoft's Exchange documentation and user interface. The Information Store (Mailboxes, Folders, and Messages) This database information, located in the Active Directory of the Windows 2000 Server or Windows Server 2003, holds individual users' mailboxes. Mailboxes are the destinations of recipients' incoming mail messages. A mailbox in the private information store can be accessed by the mailbox owner or by other users who have permission. These mailboxes can be backed up either by the Mailbox idataagent or by the Database idataagent. Within a mailbox, folders are used to organize mail messages. Some of these folders (e.g., Inbox, Sent Items) are automatically created within each new mailbox. You can also create your own folders which are stored on the Exchange Server as components of your mailbox. The Deleted Items Retention folder may also be included in the backup. When enabled from the General tab of the Mailbox idataagent's Properties dialog box, the Mailbox idataagent includes the Deleted Items Retention folder in the backup. If it is disabled, the Exchange Mailbox idataagent does not include the Deleted Items Retention folder in the backup. Single Instance Storage is possible when a message is sent to multiple recipients on the same server. There is only one copy (instance) of this message and each recipient is given a pointer to that copy of the message. This message may be modified, however it is only picked up in further backups if the message time stamp is changed beyond a certain value (as determined in the registry). The Public Information Store This database, located on the Exchange Server in a file called pub.edb, holds folders containing information that is publicly accessible to the entire Exchange organization (for example, documents or spreadsheets that are referenced by many users). A wide range of access configurations can be implemented for Public Folders. The public information store is backed up by the Public Folder idataagent and the Database idataagent.

5 Page 5 of 122 Active Directory The Active Directory maintains information about resources and users within the Exchange organization. It stores information about recipients, distribution lists, servers, etc. The Active Directory database is backed up by the Windows File System idataagent only. Transaction Logs A transaction log is a file containing a record of changes to a database. It can be used to bring a database up-to-date during a restore operation. Before a transaction is actually committed to an Exchange database, it is written to the correct eoxxx.log file, which is later applied to the database. When this log file is full, it is renamed in the format eoxxx.log (where xxx represents an incrementing hexadecimal value), and a new eoxxx.log file is created. When the Database idataagent backs up an Exchange database it backs up the related transaction log as well. Circular Logging Microsoft Exchange Servers offer the option of circular logging, which causes the information stores to prune their log files after the transactions in those files are committed. The Database idataagent uses transaction logs to perform incremental and differential backups and restores. Consequently, if this idataagent is used, circular logging must be disabled, which is the default condition in Exchange. Disabling circular logging should not cause the number of transaction logs to grow excessively, since the Database idataagent automatically prunes the transaction logs for every full backup and incremental backup (but not for differential backups). If you allocate a reasonable amount of space on your Exchange Server for transaction logs and back up the server regularly, under normal operating conditions the transaction logs will not exceed the memory allotted to them. The Mailbox idataagent and Public Folder idataagent do not use transaction logs. Consequently, they do not back up or prune the transaction log files. If you plan to use the Mailbox idataagent or Public Folder idataagent exclusively you can enable circular logging. Back to Top Objects stored in the public information store are not backed up by the Mailbox idataagent; they must be backed up by the Public Folder idataagent or Database idataagent. When you install the Database idataagent, the system reminds you to verify that circular logging is disabled. Do not enable circular logging as long as you are using the Database idataagent. Tree Levels in the Exchange Server idataagents When the Exchange Server idataagents are installed, the following levels are automatically created in the CommCell Browser:

6 Page 6 of 122 burton: Client Exchange Database idataagent Exchange Database: default: Subclients Agent Exchange Mailbox idataagent Exchange Mailbox: default: Subclients Agent defaultbackupset: Backup Sets Exchange Public Folder idataagent Exchange Public default: Subclients Folder: Agent defaultbackupset: Backup Sets Exchange Web Folder idataagent Exchange Web Folder: default: Subclients Agent defaultbackupset: Backup Sets License Requirement To perform a data protection operation using this Agent a specific Product License must be available in the CommServe Server. Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information. Back to Top Installation Besides the CommServe, MediaAgent and Windows File System idataagent, the components comprising the Exchange suite of idataagents can be deployed individually or all at once during the installation process. These agents, and the deployment options supported for each application version are discussed briefly below. Exchange Database idataagent (required for backing up/restoring Exchange database and for disaster recovery) Exchange Mailbox idataagent (required for backing up/restoring Exchange Mailbox stores) Exchange Public Folder idataagent (required for backing up/restoring Exchange Public Folder stores) Exchange Web Folder idataagent (required for backing up/restoring Exchange Web Folders)

7 Page 7 of 122 Outlook Add-In (only required if you want end-users to be able to search messages) OWA Proxy Enabler (required for certain configurations; for more information, see OWA Proxy Enabler). Deployment Options Details on deployment options available for the Exchange suite of idataagents are provided below. The Exchange Database idataagent, regardless of Exchange application version, can only be installed on the Exchange Server. Exchange Server 2000 idataagents can only be installed on the Exchange Server. For Exchange Server 2003, the Exchange Mailbox/Public Folder/Web Folder idataagents can either be installed on the Exchange Server or on an off-host proxy client (i.e., a computer other than the Exchange Server). For Exchange Server 2007, the Exchange Mailbox and Public Folder idataagents can either be installed on the Exchange Server (using a 32-bit on 64-bit install) or on an off-host proxy client (i.e., a computer other than the Exchange Server). The Outlook Add-In is typically installed on end-user workstations to support various end-user capabilities such as and searching and restoring messages. For the procedures on installing these components, refer to Deployment - Exchange Server idataagents. To ensure that your Exchange Public/Web Folder trees are fully protected, install the Exchange Public/Web Folder idataagents directly on each Exchange Server in your enterprise that has Public/Web Folders configured. In the case of off-host proxy configurations, install these agents on a proxy computer that is configured to backup/archive data for an Exchange Server that has Public/Web Folders configured. In both cases, the respective Public Folder agent will only back up/archive the local folders on the Exchange Server. Certain guidelines must be followed when installing the Outlook Add-In on a Windows x64 platform. For more information, see Installing 32-bit Components on a Microsoft Windows x64 Platform. OWA Proxy Enabler If you plan to install the agent in an off-host proxy configuration, or in a 32-bit on 64-bit configuration, and you would like to provide functionality support for the Outlook Add-In and/or OWA (if applicable), then you must install the OWA Proxy Enabler on the Exchange Server. For step-by-step instructions, see Install the OWA Proxy Enabler or Install the OWA Proxy Enabler - Clustered Environment - Virtual Server. This component requires a Product License to be available in the CommServe. Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information. Exchange Data Secured by the File System idataagent In addition to the data stored on the Exchange Server, there may be Exchange data stored on Exchange clients or on other computers. Such data is not backed up by the Exchange idataagents. To secure this data you must back it up using the File System idataagent on the Exchange client computer. The following sections describe Exchange files that may be stored on a client's hard drive. Personal Information Store The personal information store (also known as personal folders) is a repository of messages that have been moved from a server-controlled message store to files controlled by a mailbox owner. These files, which are named with the.pst extension, often reside on an Exchange client's local hard drive rather

8 Page 8 of 122 than on the Exchange Server. They can also reside in a shared location on a network. Personal Address Books Exchange users can create personal address books. These are named with the.pab extension and can be stored on a the local hard drive of an Exchange client or of some other computer. Offline Folders.pst files that reside on the Exchange Server are not backed up by the Exchange idataagents. If you want to secure these files, you must back them up using the File System idataagent. Microsoft Exchange Server allows you to create a local copy of a folder that is stored on the Exchange Server. You can access and manipulate the data while offline and synchronize the contents of the your local folder and the server folder when you reconnect with the server. These offline folders are named with the.ost extension and, by definition, are always stored on a local hard drive. The following list identifies those Exchange files that must be backed up and restored by the File System idataagent on the Exchange client computer: Exchange Entity Personal Information Store Personal Address Book Offline Folders Associated Files *.pst *.pab *.ost Supported File System Data Types All Exchange idataagents support the backup and restoration of Exchange data generated on: File allocation table (FAT) file systems New Technology file systems (NTFS) Version 4 and 5 When restoring Exchange data, you can restore the data to a file system type that differs from the type in which it originated. In other words, you can restore NTFS data to a FAT file system and restore FAT data to an NTFS file system. FAT file systems do not support Discretionary Access Control Lists (DACL); therefore, any NTFS data that is restored to a FAT partition loses its original access privileges. Also, when FAT file system data is restored to an NTFS file system, the restored data inherits the DACL of the destination directory. Any Exchange specific properties are maintained. Back to Top The Exchange Administrative Hierarchy The Exchange administrative hierarchy consists of organizations, administrative groups and servers. The organization is the largest administrative unit in Exchange. It includes the entire business or enterprise. Within an organization there are one or more administrative groups and within each administrative group there are one or more servers. A server is a computer on which Windows Server and Microsoft Exchange Server have been installed in order to provide a messaging service to a group of users. Back to Top Unicode Support for Exchange Administrator Account Password The stand-alone CommCell Console application does not support the use of Exchange Administrator Account passwords in Unicode format. However, you can still use the CommCell Console to change the Exchange Administrator Account password to non-unicode format (i.e., plain text). Back to Top

9 Page 9 of 122 Exchange Database Backups Using Volume Shadow Service (VSS) The Windows Server 2003 Operating System includes the Volume Shadow Service (VSS) capability to provide a seamless method of backing up the Exchange 2003/2007 database files. See VSS for Exchange Database idataagents for more information. VSS can also be used in conjunction with the Exchange 2007 Database idataagent to perform shadow copy backups of a replica database and logs in a Cluster Continuous Replication (CCR) configuration. For more information, see Cluster Continuous Replication (CCR) Backups. Back to Top Backups Using the Data Classification Enabler The Exchange Mailbox idataagent can use the Data Classification Enabler to facilitate selecting data for data protection operations. Using the enabler is especially useful if you will be running incremental backups. Back to Top SnapProtect The SnapProtect feature enables you to create a point-in-time snapshot of data to be used for various data protection operations. An effective way to backup live data is to temporarily quiesce it, take a snapshot, and then resume live operations. For more information, see SnapProtect feature. Back to Top Outlook Add-In The Outlook Add-In, when used in conjunction with the Exchange Mailbox idataagent, provides end-users with the capability of browsing, searching and restoring or erasing messages from Outlook on their workstations; or, if Outlook is not available on the client, then the CommCell Console (as a Java applet) can be used for browsing or searching messages. Searches can be performed on message properties such as Subject, From and To. Messages or items that match the search criteria can then be restored or erased. Additionally, if Content Indexing is configured for your site, you can take advantage of advanced search capabilities such as finding a string in the content of messages, as well as searching keywords or exact phrases in the Cc, Bcc fields or in the attachment name. For more information on these advanced search capabilities, see Content Indexing and Search. For step-by-step instructions, see Find and Restore Messages in Outlook. Back to Top Disaster Recovery Considerations Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs. See Disaster Recovery for more information regarding your agent. Back to Top

10 Page 10 of 122 System Requirements - Microsoft Exchange Server idataagents The following requirements are for the Microsoft Exchange Server idataagents: Application The Microsoft Exchange Server idataagents support the following Microsoft Exchange Server versions: Microsoft Exchange bit Server up to the latest service pack Microsoft Exchange bit Server up to the latest service pack Microsoft Exchange bit Server up to the latest service pack Microsoft Exchange bit Server up to the latest service pack* *Special configuration considerations apply. See Considerations for Exchange Server 2010 for more information. Operating System The Microsoft Exchange Server idataagents are supported on the following operating systems as supported by the Microsoft Exchange Server. Microsoft Windows Server bit and x64 Editions with a minimum of Service Pack 1 Microsoft Windows Server 2008 x64 Editions* Microsoft Windows Server 2008 R2 Editions*,** *Core Editions not supported **For Exchange Database idataagent, R2 is supported for Microsoft Exchange 2010 only Cluster Support See Clustering - Support Supported Components Exchange Offline Mining Tool The Exchange Offline Mining Tool is supported on any Windows Server platform. OWA Proxy Enabler The OWA Proxy Enabler is supported on any platform supported by the Microsoft Exchange Server. Outlook Add-In Client The Outlook Add-In Client is supported with any version of Microsoft Outlook supported by the Microsoft Exchange Server. Processor All Windows-compatible processors supported Memory 32 MB RAM minimum required beyond the requirements of the operating system and running applications Hard Disk

11 Page 11 of 122 Exchange Mailbox idataagent 116 MB minimum of hard disk space for software/ 498 MB recommended 50 MB of additional hard disk space for log file growth 82 MB of temp space required for install or upgrade (where the temp folder resides) Exchange Database idataagent 114 MB minimum of hard disk space for software/ 498 MB recommended 50 MB of additional hard disk space for log file growth 81 MB of temp space required for install or upgrade (where the temp folder resides) Exchange Public Folder idataagent 112 MB minimum of hard disk space for software/ 498 MB recommended 50 MB of additional hard disk space for log file growth 80 MB of temp space required for install or upgrade (where the temp folder resides) Exchange Web Folder idataagent 112 MB minimum of hard disk space for software/ 498 MB recommended 50 MB of additional hard disk space for log file growth 80 MB of temp space required for install or upgrade (where the temp folder resides) Peripherals DVD-ROM drive Network Interface Card Miscellaneous TCP/IP Services configured on the computer. The File System idataagent will be automatically installed during installation of this Agent if it is not already installed. For System Requirements and install information specific to the File System idataagent, refer to System Requirements - Microsoft Windows File System idataagent. Microsoft Visual C Redistributable Package is automatically installed. Note that Visual C Redistributable Package can co-exist with other versions of this software..net Framework 2.0 is automatically installed. Note that.net Framework 2.0 can co-exist with other versions of this software. Notes on Data Classification for Exchange Installation Data Classification for Exchange is not supported on an Exchange 2007 CCR cluster. Notes on Microsoft Exchange Server idataagent Installations Microsoft Exchange bit Server Agents are 32-bit MAPI-based Agents installed on a Microsoft Windows x64 platform. See Installing 32-bit Components on a Microsoft Windows x64 Platform for information on installation and configuration requirements for these Agents. The Microsoft Exchange 2003 and 2007 Mailbox and Public Folder-based Agents can be installed in two ways: directly on the Microsoft Exchange Server computer as Proxy Agents on a separate computer running a supported 32-bit operating system

12 Page 12 of 122 Microsoft Windows Server 2008 requires "csvde.exe" feature to be installed on the server to query Active Directory for mailbox information To install "csvde.exe" feature on Windows Server 2008 follow these steps: 1. Open Server Manager 2. Go to Features->Add Feature 3. Remote Server Administration Tools 4. Role Administration Tools 5. Select "Active Directory Lightweight Directory Service Tools" Notes on Exchange Offline Mining Tool Installation The following additional software packages must be installed on the same computer where the Exchange Offline Mining Tool is installed, if they are not already present on the computer:.net Framework 2.0 (will be automatically installed during Offline Mining Tool installation, if needed) Microsoft Outlook 2003 (or later) Notes on Outlook OWA Proxy Enabler Installation Prior to configuring Web Access for Exchange 2007 Mailbox/Public Folder Archiver, WebProxy Agent for Exchange, or OWA Proxy Enabler, ensure that the Client Access Role has been configured on the Exchange Server. Notes on Outlook Add-In Client Installation For Windows clients, JRE 1.6.0_06 is installed automatically with the Outlook Add-In software if it is not already installed. For Macintosh clients, JRE 1.5.x must be installed manually prior to installing the Outlook Add-In software..net Framework is needed to support RPC over HTTP connection mode, as well as support for the Exchange Offline Mining Tool. It is not automatically installed by the MSI package and must be manually installed. Update must be installed on the client in order to use RPC over HTTP. Contact Microsoft Product Support Services and refer to KB to obtain this patch The Microsoft Visual C Redistributable Package is not automatically installed for MSI installs. However, the required subset of files from Microsoft Visual C Redistributable Package are provided as part of the software and therefore, manual installation is not required. DISCLAIMER Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as supported in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system. Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.

13 Page 13 of 122 Install the Exchange Agents on Exchange Server 2003 Click on a link below to go to a specific section of the software installation: Overview Install Requirements Before You Begin Install Procedure Getting Started Select Components for Installation Firewall Configuration Configuration of Other Installation Options Storage Policy Selection Client Group Selection Configure Exchange Database Specific Information Configure Exchange Agents Specific Information Download and Install Latest Packs Verify Summary of Install Options Schedule Automatic Update Setup Complete Post-Install Considerations Overview The following procedure describes the steps involved in installing the Exchange Agents for Exchange Server 2003 on the following: Direct install on a Exchange Server or On an off-host proxy computer. This may be used for the following circumstances: In the configuration where a single non-exchange client is used to backup multiple Exchange Servers. To off-load the backup of Exchange Server, so that the performance of the Exchange Server will not be effected. To install Exchange Agents: On Exchange Server 2003 follow the steps described below. On off-host proxy computer, follow the steps described in the Install the Exchange Agents for Exchange Server 2003 on Off-host Proxy procedure. Install Requirements Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - Microsoft Exchange Server idataagents and System Requirements - Microsoft Windows File System idataagent. The computer on which these agents will be installed is referred to as the Client computer in this install procedure. Review the following Install Requirements before installing the software: General Agents should only be installed after the CommServe and at least one MediaAgent have already been installed in the CommCell. Also, keep in mind that the CommServe and MediaAgent must be installed

14 Page 14 of 122 and running (but not necessarily on the same computer), before you can install the Agent. This version of the software is intended to be installed in a CommCell where the CommServe and MediaAgent(s) version is Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation. Ensure there is an available license on the CommServe for the Agent. Verify that the software installation disc is appropriate to the operating system of the computer on which the software is being installed. Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider. Firewall If the CommServe Server, MediaAgent and/or Clients communicate across two-way firewall(s): Ensure port 8400 is allowed connections through the firewall. In addition a range of bi-directional ports (consecutive or discrete) must also be allowed connections through the firewall. For information on configuring the range of ports, see Port Requirements for Two-way Firewall. If the CommServe Server, MediaAgent and/or Clients communicate across one-way firewall(s): Identify a range of outbound ports (consecutive or discrete) for use by the software. For information on configuring the range of ports, see Port Requirements for One-way Firewall. If the MediaAgent/Client communicates with the CommServe Server across a one-way firewall, you must add the MediaAgent/Client host name (or the IP address) in the CommServe computer before installing the necessary software on the MediaAgent/Client computer. Agent Specific To Set Permissions for the Mail-Enabled User: Method One (Exchange Server 2000/2003): Assigning permissions by using the Exchange Administration Delegation Wizard. 1. Using the Exchange System Manager snap-in, right-click the organization object and delegate control. 2. Using the Wizard, assign the MailboxAdmin user Exchange Full Administrator privileges. Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain. Method Two (Exchange Server 2000/2003): To be used if the MailboxAdmin account is NOT the Administrator, OR a member of the Domain Admins OR Enterprise Admins groups. 1. Using the Active Directory Users and Computers snap-in, right-click on the MailboxAdmin user and select Properties. 2. From the Properties window, select the Member of tab. 3. Click Add, then select Exchange Services or Exchange Domain Servers group. Click Add. 4. Verify that the group selected is added to the list box. 5. Click Apply and OK to close the window. Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain.

15 Page 15 of 122 Before You Begin Log on to the client as local Administrator or as a member of the Administrators group on that computer. Install Procedure Getting Started 1. Place the software installation disc for the Windows platform into the disc drive. After a few seconds, the installation program is launched. If the installation program does not launch automatically: Click the Start button on the Windows task bar, and then click Run. Browse to the installation disc drive, select Setup.exe, click Open, then click OK. 2. In this screen, you choose the language you want to use during installation. Click the down arrow, select the desired language from the pull-down list, and click Next to continue. 3. Select the option to install software on this computer. NOTES The options that appear on this screen depend on the computer in which the software is being installed. 4. Read the Welcome screen. Click Next to continue, if no other applications are running. 5. Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled. 6. Read the license agreement, then select I accept the terms in the license agreement. Click Next to continue. Select Components for Installation 7. Select the component(s) to install. NOTES Your screen may look different from the example shown. Components that either have already been installed, or which cannot be installed, will be dimmed. Hover over the component for additional details.

16 Page 16 of 122 The Special Registry Keys In Use field will be enabled when GalaxyInstallerFlags registry keys have been enabled on this computer. Hover over the field to see which keys have been set, as well as their values. For more information, see Registry Keys. Click Next to continue. To install the Exchange idataagents expand the Client Modules folder, the idataagents folder, and the Exchange idataagents folder then select one or more of the following (as appropriate to your application version): ida for Exchange Database ida for Exchange Mailbox ida for Exchange Public Folder When you select the Exchange Agents for install, the appropriate Windows File System idataagent is automatically selected for install. To install the Exchange Mailbox Archiver Agent and/or Exchange Public Folder Archiver Agents, expand the Client Modules folder, the DataArchiver Agents folder, and then select from the following: DataArchiver Agent for Exchange DataArchiver for Exchange Public Folder Exchange Compliance Archiver 8. Click Yes to set up the required privileges for the local administrators group. NOTES This option will only appear if the Windows user account used to install the software does not have the required administrator rights (e.g., if the operating system was newly installed). If you choose to click Yes, the install program will automatically assign the required rights to your account. You may be prompted to log off and log back on to continue the installation. If you choose to click No, the installation will be aborted. You will be prompted at the end of the installation to decide if you want these privileges to be revoked. The install program checks your Windows user account for the following necessary operating system rights: Right to increase quotas (this is referred to as adjust memory quotas for a process on Windows Server 2003). Right to act as a part of the operating system. Right to replace a process level token.

17 Page 17 of Specify the location where you want to install the software. NOTES Do not install the software to a mapped network drive. Do not use the following characters when specifying the destination path: / : *? " < > It is recommended that you use alphanumeric characters only. If you intend to install other components on this computer, the selected installation directory will be automatically used for that software as well. If a component has already been installed, this screen may not be displayed if the installer can use the same install location as previously used. Click Browse to change directories. Click Next to continue. Firewall Configuration 10. Select from the following: If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select Yes, configure firewall services, and then click Next to continue. Proceed to the next Step. If firewall configuration is not required, click No, do not configure firewall services and then click Next to continue. Proceed to the next section. NOTES Operating systems, such as Windows 2008 and Windows Vista, may have more than one profile present. When you select No to configure firewall services, verify that firewall settings are not enabled in the profile(s). If the system detects firewall settings are present in the profile(s), you must select from the following: Disable firewall for ALL profiles: Employ caution when choosing this option; firewall settings will be disabled in all profiles. This requires a system reboot; installation automatically resumes after reboot. No, Firewall is not enabled: Select this option if your firewall settings allow communication with the CommServe computer. Click Back to configure firewall services.

18 Page 18 of Click the Specify list of machine across the firewall option and then specify the list of hosts separated from this computer by a firewall. Make sure you correctly describe whether the firewall allows two-way communication (but on a limited range of ports), or one-way communication (with either only remote host being able to make connections to this computer, or vice versa). For all one-way firewalls allowing incoming connections and those one-way firewalls allowing outgoing connections without additional port filtering, skip this step. Click Next to continue. NOTES Consider the following: On the CommServe Server, this list should include all the MediaAgents and Clients that are on the other side of the firewall. On the MediaAgents/Clients this should include the CommServe computer, and any other Clients/MediaAgents on the other side of the firewall with which communications will be established. For each machine on the other side of the firewall that you want to configure, choose the type of firewall configuration based on the firewall setup in your environment. Choose from the following options: Click on 2-way firewall if you can open certain ports as bi-directional ports. Click 1-way firewall; host is reachable from this machine on the machine that is on the secure side of the firewall. Click 1-way firewall; host is NOT reachable from this machine on the machine that is on the public / DMZ side of the firewall. If you wish to communicate with computers in a clustered environment, ensure that you add the Host Name/IP Address of all physical nodes in the cluster (even if no CommCell components are installed) and all the virtual nodes in which CommCell components are installed. Type the host name or the IP address and the GxCVD port number of the host name, and click Add to place it in the Host Name/IP Address List. 12. Click the Specify list of restricted open ports option and then specify the port range. Add the starting and ending port range and then click Add to place it in the Open Port List. Repeat as needed.

19 Page 19 of 122 If firewall separating this computer from others allows incoming connections, but these connections can be made only on a limited set of ports, then configure the appropriate port range here. For all other scenarios, skip this step. Note that if you do not specify hostname(s) as well as port number(s), then the firewall services will not be configured. NOTES Typically in a two-way firewall, the open ports must be indicated for all computers. In a oneway firewall, the ports must be specified on computers in the open side, if they are open in a restricted way. Note that the port ranges are not required for computers that are fully closed in the one-way firewall. For example, laptops which are configured as clients in the Workstation Backup Agent. In a clustered environment, make sure the firewall ports specified here are open for communication on all the physical nodes as well as the virtual nodes. Click Next to continue. 13. If desired, modify the Keep Alive interval. Click Next to continue. 14. Optionally, select Advanced Firewall Configuration and specify a local host name interface to use for outgoing tunnel connections through the firewall. Otherwise, the interface and port is automatically selected for you by the OS. Click Next to continue. 15. If desired, modify the Tunnel Initialization interval.

20 Page 20 of 122 Click Next to continue. Configuration of Other Installation Options 16. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com) NOTES Do not use spaces when specifying a new name for the CommServe Host Name. If a component has already been installed, this screen will not be displayed; instead, the installer will use the same Server Name as previously specified. Click Next to continue. 17. Enter the username and password information for an external domain user account or a CommCell user account. This authorizes the installation of an agent on the CommCell. NOTES This window is only displayed when the Require Authentication for Agent Installation option is selected in the CommCell Properties. Users must belong to a User Group with Administrative Management capabilities to enable this feature. For more information, see Authentication for Agent Installs. Click Next to continue. 18. Enter the following: The local (NetBIOS) name of the client computer. The TCP/IP IP host name of the NIC that the client computer must use to communicate with the CommServe Server. NOTES Do not use spaces when specifying a new