Features - Exchange Public Folder Archiver Agent

Transcription

1 Page 1 of 77 Features - Exchange Public Folder Archiver Agent Table of Contents Overview System Requirements - Exchange Public Folder Archiver Agent Installation Install the Exchange Mailbox/Public Folder Archiver Agent Install the Exchange Mailbox/Public Folder Archiver Agent - Clustered Environment - Virtual Server Migration Archiving - Exchange Public Folder Archiver Agents Recover Data - Exchange Public Folder Archiver Agents Configuration Agents Archive Sets Subclients Management Archive History Recovery History Additional Components Outlook Add-In - Administrators Outlook Add- In - End-Users

2 Page 2 of 77 Overview - Exchange Public Folder Archiver Agent Choose from the following topics: Introduction Supported Data Types Tree Levels in the Exchange Public Folder Archiver Agent License Requirement Installation Configuration Archive and Recovery DataArchiver Outlook Add-In DataArchiver WebProxy Agent for Exchange Outlook Web Access (OWA) Disaster Recovery Considerations Related Topics: Erase Backup/Archived Data Introduction The size of Exchange Server Information Store will grow over time. To keep its size under control, administrators and users have to either delete or archive unwanted Public Folder items periodically to release disk space. So it is necessary to have centralized migration management to keep the size of Public Folders within a healthy range, as well as to provide easy access to the archived items. The Exchange Public Folder Archiver Agent is designed for the above purpose on Exchange Servers. It will automatically archive Public Folder items satisfying certain criteria, and replace them with stubs containing information for recovery. Users can double-click the item stub in Outlook or Outlook Web Access (OWA) to recover the original item. Alternatively, users can also ask the administrator to browse the CommCell Console to recover the item. The latter method is especially useful if the stub is deleted. Terminology A reduction in the Public Folder size shown in the Exchange System Manager will be seen immediately after a migration operation. However, in order for the database size to show the space savings, an offline defragmentation will need to be run. References to the product family name, Exchange Migration Archiver Agents, in this documentation include the Exchange Mailbox Archiver Agent and the Exchange Public Folder Archiver Agent in cases where common material is shared. References to the product name, Exchange Mailbox Archiver Agent, in this documentation are used in topic discussions relevant only to this particular agent, which is displayed as "Exchange Mailbox Archiver" in the CommCell Console References to the product name, Exchange Public Folder Archiver Agent, in this documentation are used in topic discussions relevant only to this particular agent, which is displayed as "Exchange PF Archiver" in the CommCell Console. Supported Data Types Data Protection Operations for the following data types are supported by the Exchange Public Folder

3 Page 3 of 77 Archiver Agent: 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, and journal entries. Data Protection Operations for all other data types not mentioned in the above list are not supported by the Exchange Public Folder Archiver Agent, including: Exchange Server properties Tree Levels in the Exchange Public Folder Archiver Agent When the Exchange Public Folder Archiver Agent is installed, the following levels are automatically created in the CommCell Browser. exch1: Client default: Subclient Exchange PF Archiver: Agent defaultarchiveset: Archive Set 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. Installation Besides the CommServe and MediaAgent, there are three components to be installed for the Exchange Public Folder Archiver Agent: Exchange Public Folder Archiver Agent (includes Outlook Web Access option) DataArchiver Outlook Add-In OWA Proxy Enabler In addition, there is a one-time setup task required to publish forms to the Organizational Form Library (OFL). Each of these components is briefly described below. For the procedures on installing these components, refer to Deployment - Exchange Public Folder Archiver Agent.

4 Page 4 of 77 Exchange Public Folder Archiver Agent For Exchange Server 2003/2007, this component can either be installed on an Exchange Server or on an off-host proxy computer, and is similar to the Exchange Public Folder idataagent installation. For Exchange 2000, this component is installed on the Exchange Server. To fully protect the data on the Exchange Server, it is recommended that the Exchange Database idataagent and Exchange Public Folder idataagent also be installed. 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. DataArchiver Outlook Add-In The DataArchiver Outlook Add-In software can be installed on clients with Outlook to facilitate stub recalls. For more information, see DataArchiver Outlook Add-In. 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. In order to support stub recalls from OWA for Exchange 2003 agents in an off-host proxy configuration, run the RegisterWSSForm tool located on the Resource Pack, after installing the OWA Proxy Enabler. For Exchange 2007 on a cluster virtual server, in either an off-host proxy configuration or a 32-bit on 64- bit configuration, because of a Microsoft issue with Exchange 2007 Server, components must be deployed in the following manner: The cluster virtual server must have the Exchange Mailbox role only, not the client access role. The Exchange Client Access role must be on another, non-clustered server. For OWA recalls, OWA Proxy Enabler must be installed on both servers. Functionality support for the Outlook Add-In requires that the OWA Proxy Enabler be installed on the cluster virtual server which has the Exchange Mailbox role. For Exchange 2007 in a non-clustered environment, when deployed with the Exchange Mailbox role on one server and the Exchange Client Access role on another server, components must be deployed in the following manner: For OWA recalls, OWA Proxy Enabler must be installed on both servers. Functionality support for the Outlook Add-In requires that the OWA Proxy Enabler be installed on the server which has the Exchange Mailbox role. For step-by-step installation 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. Publish Outlook Forms to OFL This task only needs to be performed once per Exchange Organization.

5 Page 5 of 77 Initially, the Exchange administrator needs to create the Organizational Form Library if is does not already exist. After the OFL is available, the administrator can log on as the owner of the OFL from a computer with Outlook installed and run the PublishForm tool (located on the Resource Pack) to publish the forms. If there are multiple Exchange Servers, the OFL should be replicated to make the forms available to other servers. In addition, you need to ensure that only one OFL per language exists in the Exchange Organization, taking replication into account. For details about how to create and manage the OFL, please refer to Exchange Server documentation and related Microsoft Knowledge Base articles. For the procedure on publishing forms for the Exchange Migration Archiver Agents, refer to OFL Configuration. Configuration The migration archiving operation is based on subclients, so the following configuration is per subclient basis. Most of the following options are located in the subclient properties dialog box. Archiving Rules The configuration of the archiving rules is central to customizing migration archiving operations to meet the needs of your organization. The Archiving Rules are discussed in detail in Archiving Rules - Exchange Mailbox/Public Folder Archiver Agents. Indexing Option To keep the index within a manageable size, a new index will be created every certain number of migration archiving operations. This value can be entered in the Create new index every n Archive Operations field on the subclient properties Archiving Rules tab. This setting will apply only when the messages are recovered using browse and recovery from the CommCell Console (stand-alone application). The CommCell Console also allows you to specify a point-in-time to find a message/item archived before the last creation of a new index. Note that the new index creation interval setting established in the subclient properties can be overridden during the running of a migration archiving operation by selecting the Create New Index option from the Advanced Archive Options (Data) tab. Note that this setting does not affect recovering messages/items from Outlook or OWA. Storage Policy Archiving Rules are initially disabled by default. After creating a subclient, you must clear the Disable All Rules option and configure archiving rules before Archive Operations are possible. Otherwise, the system will ignore all archiving rules (except for the Do Not Create Stub rule) for the subclient. The retention criteria for preserving archived data through Storage Policies associated with DataArchiver Agents is based only on time, not cycles. For more information on Storage Policies, see Storage Policies. Stub Retention By default, stub retention length is decided by the retention of the archived messages/items associated with the stub. After the messages/items on the media (all the copies) have expired, the stub will be pruned in next migration archiving operation. Users can also specify a value in days for stub retention time, from the subclient properties Archiving Rules tab. Keep in mind that the stub could be pruned before this value, if the storage policy retention time is smaller than this value. Archive and Recovery After configuration is completed, the recovery administrator can schedule migration archiving jobs, similar to scheduling backup jobs for idataagents. To ensure that only successfully archived messages will be changed into stubs, the migration archiving operation is divided into two phases: archiving and

6 Page 6 of 77 stubbing. The stubbing phase starts after the archiving phase succeeds. However, stubs will only be created if the subclient properties were configured to create them during migration archiving operations. In the archiving phase, DataArchiver will archive the messages/items meeting the pre-set archiving criteria and, if applicable, put them into a list for the stubbing phase and prune expired stubs. During this phase of the migration archiving operation for the Exchange Mailbox Archiver Agent, messages and folders that were added to the Archive List in Outlook will also be included in the migration archiving operation. Information about each archived message/item is placed into a stub that can then be used as a link to recover the message/item. If the Select Items with attachment(s) only option is selected in the subclient properties Archiving Rules tab, it will only archive attachment(s) of the message/item. Archiving of data in the Notes folder is not supported by the Exchange Public Folder Archiver Agent. Refer to Migration Archiving more information. Recovery There are four ways to recover an archived message: from the CommCell Console (stand-alone application), CommCell Console (as a Java applet), Outlook, or Outlook Web Access (OWA). From the CommCell Console, the browse of Exchange Migration Archiver data is forced to be a non-image browse to view all the archived messages/items in this migration archiving cycle (i.e., since last creation of new index). The recovery administrator can browse and find the message/item to recover. To find messages/items archived earlier than the last creation of new index, the administrator can provide a point-in-time in the Browse Options dialog box. Refer to Recover Archived Data for more information. DataArchiver Outlook Add-In For the Exchange Public Folder Archiver Agent, the Outlook Add-In enables Outlook users to recover archived data from stubs. In Outlook, the stubs will appear as messages/items with the icon. The stubs include information on sender, recipient, subject and body text if Archive message attachments only option is enabled. To find a stub, users can look for the icon in the folder view. Once a stub is located, users can open the stub by clicking on it in Outlook. The Outlook Add-In will intercept the Outlook user s open item event and then ask for the user s confirmation. Once the user decides to recover the original message or item, the Outlook Add-In will get the recovery information from the stub and submit the recovery request to the system. A recovery job will be started and the message/item will be recovered back to Exchange Server. After the recovery is completed, Outlook users will see the recovered message/item. During recovery, the Outlook Add-In allows the user to cancel the recovery job. At the end of recovery, the Outlook Add-In will display the result and related information to the user. Because a recovered message/item will have the most recent modification time, it will not be archived again until it meets the minimal message age or is added to the Archive List by the Outlook user (applicable for Exchange Mailbox Archiver), unless the user decides to delete the stub or the recovered message/item after use. DataArchiver WebProxy Agent for Exchange If the DataArchiver WebProxy Agent for Exchange is installed on an IIS server in your network, during the install of the DataArchiver Outlook Add-in, you can select the option to route stub recovery through the IIS server over HTTPS. Normally, two direct channels of communication are opened from the Outlook Add-in client, one to the Exchange Server and one to the CommServe, over ports 8401 and When using the WebProxy Agent, a single channel of communication is opened through the IIS server. Stub recovery is performed through a single, encrypted and authenticated SSL (Secure Sockets Layer) port.

7 Page 7 of 77 This solution takes advantage of the RPC over HTTP facilities of Windows Server 2003; therefore, this solution only applies to Exchange 2003 accounts on an Exchange 2003 Server, running on Windows Server See System Requirements - Exchange Mailbox Archiver Agent or System Requirements - Exchange Public Folder Archiver Agent for detailed IIS server and Outlook Add-in client requirements. See Deployment - Exchange Mailbox Archiver Agent or Deployment - Exchange Public Folder Archiver Agent for instructions on installing and configuring these components. To change the method of communication for stub recovery (HTTPS, or Direct) after installation, uninstall and then reinstall the Outlook add-in, selecting the desired method of communication. To avoid possible intermittent message recall failures when using the Outlook Add-In in RPC over HTTP mode, worker process recycling and Web Garden options under IIS 6.0 should be disabled for the DMProxy Service. See Configure an Application Pool for the DataArchiver WebProxy Agent for Exchange for step-by-step instructions. Outlook Web Access (OWA) When an Exchange Migration Archiver Agent is installed, you have the option to enable support for recovering archived message/item stubs from Outlook Web Access. If this option is enabled, the stubs will appear as messages with the icon in OWA, which can double-clicked for recovery. Since no stub icons are available for OWA 2003, the following enhancements have been made to allow you to easily distinguish them from normal messages in that version of OWA and any supported version of Outlook: For Public Folder Archiver and 7.0 pre-service Pack 3 data archived by Exchange 2003/2007 Mailbox Archiver, message stubs are distinguished in Outlook and OWA 2003/2007 by displaying the word "ARCHIVED:" in the Subject line. For data archived after installing 7.0 Service Pack 3, Exchange 2003/2007 Mailbox Archiver allows Subject line text to be customized using the StubIdentifier registry key, otherwise no stub identification text will display in the Subject line. For more information on using this feature, refer to Recover a Message from Outlook or OWA. Back to Top Disaster Recovery Considerations The Exchange Public Folder Archiver product does not provide the ability to restore the entire system in the event of a disaster. Systems using an Archiver Agent should also be protected using the corresponding backup and recovery agent. Exchange Public Folder Archiver relies upon the Exchange Database idataagent to perform a full system restore of Exchange data, and the Windows File System idataagent to restore the operating system. For more information, see Recover Data - Exchange Server - Full System Restore. Back to Top

8 Page 8 of 77 System Requirements - Exchange Public Folder Archiver Agent The following requirements are for the Exchange Public Folder Archiver Agent: Application The Exchange Public Folder Archiver Agent supports 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 Operating System The Exchange Public Folder Archiver Agent is 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 Cluster Support See Clustering - Support Supported Components OWA Proxy Enabler The OWA Proxy Enabler is supported on any platform supported by the Microsoft Exchange Server. Web Proxy Agent The Web Proxy Agent 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. The Outlook Add-In Client does not support Microsoft Outlook Processor All Windows-compatible processors supported Memory 32 MB RAM minimum required beyond the requirements of the operating system and running applications Hard Disk

9 Page 9 of 77 OWA Proxy Enabler 121 MB minimum of hard disk space for software/ 148 MB recommended 79 MB of temp space required for install (where the temp folder resides) Web Proxy Agent 50 MB of additional hard disk space for log file growth 10 MB of temp space required for install (where the temp folder resides) Outlook Add-In Client 35 MB minimum of hard disk space for software/ 50 MB recommended 21 MB of temp space required for install (where the temp folder resides) Peripherals DVD-ROM drive Network Interface Card Miscellaneous TCP/IP Services configured on the computer. 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 Microsoft Exchange Server idataagent Installation 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 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 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.

10 Page 10 of 77 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.

11 Page 11 of 77 Install the Exchange Mailbox/Public Folder Archiver Agents Click on a link below to go to a specific section of the software installation: Install Requirements Install Checklist 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 Specific Information Outlook Web Access Option Download and Install Latest Packs Verify Summary of Install Options Schedule Automatic Update Setup Complete Post-Install Considerations Install Requirements The Exchange Mailbox Archiver and Exchange Public Folder Archiver Agents are installed on the computer in which the Exchange Server resides; for Exchange Server 2003/2007, you can also install this agent on a separate computer other than the Exchange Server. (In either case, the computer on which these agents will be installed is referred to as the Client computer in this install procedure.) 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. Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - Exchange Mailbox Archiver Agent and in System Requirements - Exchange Public Folder Archiver Agent. The following procedure describes the steps involved in installing the Exchange Mailbox Archiver Agent and the Exchange Public Folder Archiver Agent. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary. The Exchange Mailbox Archiver and Exchange Public Folder Archiver Agents also have a separate component, the Outlook Add-In, that can be installed on end-user workstations to allow users to perform stub recoveries and submit migration archiving requests from Outlook. See Deployment - Exchange Mailbox Archiver Agent or Deployment - Exchange Public Folder Archiver Agent for procedures on installing the DataArchiver Outlook Add-In component. Review the following Install Requirements before installing the software:

12 Page 12 of 77 General Prior to installing multiple instances of a software component on the same computer, review the guidelines contained in Multi Instancing. 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 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. Multi Instancing By utilizing the Multi Instancing feature, the same Agent and MediaAgent software can be installed on a computer multiple times, but not all components support Multi Instancing. This limitation can apply to the component you are installing, or to one already installed on the computer. Prior to installing multiple instances of a software component on the same computer, carefully review the information contained in Multi Instancing, and follow the instructions in the How to Use Multi Instancing section for the additional screens that will appear during the installation process. Agent Specific Exchange Server 2007 You must create a new Public Folder database, if one is not already set up at your Exchange site, prior to installing this agent in order for the MailboxAdmin account for this agent to be created by install. This can be accomplished from Microsoft's Exchange Management Console, and help is available from that tool for the procedure on How To Create a New Public Folder Database. If you will be installing a 32-bit MAPI-based agent (such as Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver) on a Windows x64 platform, review the general and agent-specific requirements contained in Installing 32-bit Components on a Microsoft Windows x64 Platform prior to installation. If you will be installing a 32-bit MAPI-based agent (such as Exchange Mailbox idataagent,

13 Page 13 of 77 Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver) on a 32-bit off-host proxy client (i.e., a computer other than the Exchange Server), perform the following pre-requisite tasks before installing these agents: 1. Ensure that the proxy computer has been added to the same Domain in which the Exchange Server 2007 resides. 2. We recommend installing Outlook 2007 on the off-host proxy client in order to supply the software drivers necessary for Exchange-based agents to function in an off-host proxy configuration. Alternatively, you can install the exchangemapicdo.exe software on the proxy computer (available for download from Microsoft Corporation), or use the Exchange Management Tools 2007 to accomplish this task. 3. If you intend to install multiple instances of these agents on the same off-host proxy computer for the purpose of fanning out to different Exchange Servers, then you will need to create the ballowmultiinstances registry key on the proxy computer prior to installing the second instance. Other off-host proxy fanning requirements are noted in relevant steps of the installation procedures. For proxy fanning configurations, make sure that the Exchange Server specified during the installation of the second instance exists within the same domain as the Exchange Server specified during installation of the first instance. 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. Exchange Server 2003 If you will be installing the Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver Agent on an off-host proxy client (i.e., a computer other than the Exchange Server), perform the following pre-requisite tasks before installing these agents: 1. Ensure that the proxy computer has been added to the same Domain in which the Exchange Server 2003 resides. 2. We recommend installing Outlook 2003 on the off-host proxy client in order to supply the software drivers necessary for Exchange-based agents to function in an off-host proxy configuration. Alternatively, you can install the exchangemapicdo.exe software on the proxy computer (available for download from Microsoft Corporation), or use the Exchange Management Tools 2003 to accomplish this task. All Exchange Server Versions Prior to installing the Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver you must create a mail-enabled user that has the proper permissions. Some points to keep in mind when setting up this mail-enabled user are listed below. Use MailboxAdmin, or something similar, as the mailbox name. In order for the MailboxAdmin user to perform basic operations, certain permissions are required. The MailboxAdmin user must be a member of the Local Administrator Group and have rights to all mailboxes on the server. There are a number of different ways to grant permissions for the MailboxAdmin user to have the proper rights. Listed below are three of the most common. These procedures may need to be changed depending on your privacy and security policies. For the Exchange Public Folder idataagent, the MailboxAdmin user must be the "Owner" of all public folders. To Set Permissions for the Mail-Enabled User: Method One (Exchange Server 2000/2003): Assigning permissions by using the Exchange Administration Delegation Wizard.

14 Page 14 of 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. Method Three (Exchange Server 2007): 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 Organization Administrators 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. For more information refer to the following publications: Microsoft TechNet ( XADM: How to Get Service Account Access to All Mailboxes in Exchange 2000 ( Exchange 2007 Permissions: Frequently Asked Questions ( Install Checklist Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder. 1. Install folder location: See Select Components for Installation for more information. 2. If the CommServe Server and the client computer communicate across a firewall: Firewall ports:

15 Page 15 of 77 Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall: Keep Alive Interval minutes: Hostname for outgoing tunnel connections: Tunnel Initialization Interval seconds: See Firewall Configuration for more information. 3. CommServe Host Name or the CommServe IP address: See Configuration of Other Installation Options for more information. 4. Client computer's Host name (NetBIOS name) or IP address See Configuration of Other Installation Options for more information. 5. Job result folder location: If necessary, Name and Password for the specified folder: See Configuration of Other Installation Options for more information. 6. Storage Policy used by the default subclient: See Storage Policy Selection for more information. 7. Client Group to which this Client will be associated: See Client Group Selection for more information. 8. Exchange Administrator Account Name: Exchange Administrator Account Password: Exchange Administrator Mailbox Name: Exchange Administrator Profile Name: Exchange Server Name: Exchange Server Domain: See Configure Exchange Specific Information for more information. 9. Outlook Web Access Alias: See Outlook Web Access Option for more information.

16 Page 16 of Time and frequency for Install of Automatic Updates: See Schedule Automatic Update for more information. 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. If you are installing on a x64 version of Windows 2008 Server Core R2, go to the AMD64 folder and run Setup.exe. 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. This screen will only appear when the ballow32bitinstallon64bit registry key has been created and enabled on this computer. 4. Select the option to install software on this computer. The options that appear on this screen depend on the computer in which the software is being installed. 5. Read the Welcome screen. Click Next to continue, if no other applications are running. 6. Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled.

17 Page 17 of Read the license agreement, then select I accept the terms in the license agreement. Click Next to continue. Select Components for Installation 8. Select the component(s) to install. 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. 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 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 9. Click Yes to set up the required privileges for the local administrators group. 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.

18 Page 18 of 77 Right to replace a process level token. 10. Specify the location where you want to install the software. 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. If you intend to use the SnapProtect feature for Windows File System idataagent, the agent should be installed on a non-system drive and not a filer volume. Click Browse to change directories. Click Next to continue. Firewall Configuration 11. 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. 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

19 Page 19 of 77 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. 12. 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. 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

20 Page 20 of 77 Address List. 13. 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. 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. 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. 14. If desired, modify the Keep Alive interval. Click Next to continue. 15. 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.

21 Page 21 of If desired, modify the Tunnel Initialization interval. Click Next to continue. Configuration of Other Installation Options 17. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com) 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. 18. 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. 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

22 Page 22 of 77 capabilities to enable this feature. For more information, see Authentication for Agent Installs. Click Next to continue. 19. 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. Do not use spaces when specifying a new name for the Client. The default network interface name of the client computer is displayed if the computer has only one network interface. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server. If a component has already been installed, this screen will not be displayed; instead, the install program will use the same name as previously specified. Click Next to continue. 20. Specify the following and click Next to continue: Type the location of the client's job results directory, or click Browse. The Agent uses the job results directory to store the client's backup and restore job results. Storage Policy Selection 21. Select the storage policy through which you want to back up/archive the indicated component

23 Page 23 of 77 (subclient, instance, etc.) A storage policy directs backup data to a media library. Each library has a default storage policy. When you install an Agent, the install program creates a default subclient for most Agents. If desired, you can change your storage policy selection at any time after you have installed the client software. If applicable, enable Global Filters for the default subclient. If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents. Click Next to continue. Client Group Selection 22. Select a Client Group from the list. Click Next to continue. This screen will be displayed only if Client Groups are configured in the CommCell Console. For more information, see Client Computer Groups. Configure Exchange Specific Information 23. Enter the following Exchange Administrator information then click Next to continue: Account Name - Domain user account created with the proper permissions. Do not include the domain name here. Account Password - The password assigned to the domain user. Mailbox Name for this Account - Mailbox associated with the user above. Profile Name - Created during agent install. This profile is associated with the domain user's mailbox. Exchange Server Name - Name of the Exchange Server that the agent will communicate with for data protection and recovery operations.

24 Page 24 of 77 Domain - The Windows domain that the Exchange Server resides in. The installation detects and enters a domain name. If necessary, this field can be modified. The Exchange Administrator Account Information dialog will appear only once during the installation of multiple Exchange MAPIbased agents, and the account settings established initially will apply to all of them. To specify different Exchange Administrator Account settings for each Exchange MAPIbased agent, either install the agents separately or manually modify the account information in the Agent properties. If you are installing the agent on a 32-bit offhost proxy computer, or are performing a multi-instance proxy fanning install, ensure that you enter the name of the appropriate Exchange Server in the Exchange Server Name field. In some cases, a pre-populated default value for this field will appear and may need to be changed depending on your configuration. See the Exchange Agents section in User Accounts and Passwords for more information. Outlook Web Access Option 24. A dialog will ask you to enter an alias that you will use to connect to the system via your web browser, for the purpose of recovering archived messages from stubs using Outlook Web Access (OWA). Type in the desired alias, then click Next to continue. For multi-instance installs, the alias must be different for each instance you are installing. Download and Install Latest Packs 25. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider. Internet connectivity is required to download updates. This step is applicable when installing on the first instance. Updates are downloaded to the following

25 Page 25 of 77 directory: <software installation>/base/temp/downloadedpacks. They are launched silently and installed automatically for the first instance. Click Next to continue. Verify Summary of Install Options 26. Verify the summary of selected options. The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. Click Next to continue or Back to change any of the options. The install program now starts copying the software to the computer. This step may take several minutes to complete. 27. The System Reboot message may be displayed. If so, select one of the following: Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time. Reboot Now If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot. Exit Setup If you want to exit the install program, click Exit Setup. Schedule Automatic Update

26 Page 26 of If necessary, select this option to schedule an automatic installation of software updates. Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console. To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates. You may be prompted to reboot the computer before restarting services. If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously specified. Click Next to continue. Setup Complete 29. Click Next to continue. Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling. 30. Click Yes to remove the privileges that were assigned earlier by the install program. If you do not wish to remove them, click No. This option will only be displayed if you were prompted to assign the privileges earlier in the installation. 31. Setup displays the successfully installed components. The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the

27 Page 27 of 77 example shown. If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents. If Reboot Now button is displayed make sure to reboot the computer before performing any other operations from the computer. Click Finish to close the install program. The installation is now complete. Post-Install Considerations General Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component. After installing the Agent, you may want to configure the Agent before running a data protection operation. The following list includes some of the most common features that can be configured: Configure your subclients - see Subclients for more information. Schedule your data protection operations - see Scheduling for more information. Configure Alerts - See Alerts and Monitoring for more information. Schedule Reports - See Reports for more information. The software provides many more features that you will find useful. See the Index for a complete list of supported features. Agent Specific The following configuration tasks are required before performing an Archive Operation using this DataArchiver Agent: Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations. If you installed 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 Client Access role server or Exchange Server. For step-by-step instructions, see Install the OWA Proxy Enabler or Install the OWA Proxy Enabler - Clustered Environment - Virtual Server. Afterwards, you must also configure the Proxy for Exchange field in the Client Properties (Advanced) tab on the client hosting the Exchange Server to point to the client hosting the 32-bit agents. For more information, see Configuring the Proxy for Exchange. 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.

28 Page 28 of 77 Install the Exchange Mailbox/Public Folder Archiver Agents - Clustered Environment - Virtual Server Click on a link below to go to a specific section of the software installation: Install Requirements Install Checklist Before You Begin Install Procedure Getting Started Cluster Selection Select Components for Installation Firewall Configuration Configuration of Other Installation Options Storage Policy Selection Client Group Selection Configure Exchange Specific Information Outlook Web Access Option Download and Install Latest Packs Verify Summary of Install Options Schedule Automatic Update Install Remaining Cluster Nodes Setup Complete Post-Install Considerations Install Requirements The Exchange Mailbox Archiver Agent and Exchange Public Folder Archiver Agent can be installed from the active node to the virtual server using the following procedure. The software can also be automatically installed on all available passive nodes when the software is installed onto the virtual server, or you can choose to install any passive node(s) separately. 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. For an overview of deploying the software components in a clustered environment, see Clustering Support. Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - Exchange Mailbox Archiver Agent and in System Requirements - Exchange Public Folder Archiver Agent. The following procedure describes the steps involved in installing the Exchange Mailbox Archiver Agent and Exchange Public Folder Archiver Agent. If you choose to install additional components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary. The Exchange Mailbox Archiver and Exchange Public Folder Archiver Agents also have a separate

29 Page 29 of 77 component, the Outlook Add-In, that can be installed on end-user workstations to allow users to perform stub recoveries and submit migration archiving requests from Outlook. See Deployment - Exchange Mailbox Archiver Agent or Deployment - Exchange Public Folder Archiver Agent for procedures on installing the DataArchiver Outlook Add-In component. Review the following Install Requirements before installing the software: General Prior to installing multiple instances of a software component on the same computer, review the guidelines contained in Multi Instancing. 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 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. If a MediaAgent or Client on a Microsoft Windows MSCS virtual server needs to communicate with other CommCell components across a firewall, you must: Install File System idataagent or MediaAgent on all the physical nodes of the cluster. During the installation, use the firewall related prompts to establish the firewall settings required by the software to communicate across the firewall. Then install the software components on the virtual nodes. (It is not necessary to configure the firewall settings again in the virtual nodes.) If the cluster communicates with the CommServe across a one-way firewall, you must add both the physical and virtual nodes' host names (or the IP addresses) in the CommServe computer before installing the software. Cluster Check the following on the cluster computer in which you wish to install the software: Cluster software is installed and running. Active and passive nodes are available.

30 Page 30 of 77 Disk array devices configured with access to the shared array. Public Network Interface Card is bound first, before the private Network Interface Card. (Does not apply to NetWare Cluster.) Multi Instancing By utilizing the Multi Instancing feature, the same Agent and MediaAgent software can be installed on a computer multiple times, but not all components support Multi Instancing. This limitation can apply to the component you are installing, or to one already installed on the computer. Prior to installing multiple instances of a software component on the same computer, carefully review the information contained in Multi Instancing, and follow the instructions in the How to Use Multi Instancing section for the additional screens that will appear during the installation process. Agent Specific Exchange Server 2007 You must create a new Public Folder database, if one is not already set up at your Exchange site, prior to installing this agent in order for the MailboxAdmin account for this agent to be created by install. This can be accomplished from Microsoft's Exchange Management Console, and help is available from that tool for the procedure on How To Create a New Public Folder Database. If you will be installing a 32-bit MAPI-based agent (such as Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver) on a Windows x64 platform, review the general and agent-specific requirements contained in Installing 32-bit Components on a Microsoft Windows x64 Platform prior to installation. If you will be installing a 32-bit MAPI-based agent (such as Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver) on a 32-bit off-host proxy client (i.e., a computer other than the Exchange Server), perform the following pre-requisite tasks before installing these agents: 1. Ensure that the proxy computer has been added to the same Domain in which the Exchange Server 2007 resides. 2. We recommend installing Outlook 2007 on the off-host proxy client in order to supply the software drivers necessary for Exchange-based agents to function in an off-host proxy configuration. Alternatively, you can install the exchangemapicdo.exe software on the proxy computer (available for download from Microsoft Corporation), or use the Exchange Management Tools 2007 to accomplish this task. 3. If you intend to install multiple instances of these agents on the same off-host proxy computer for the purpose of fanning out to different Exchange Servers, then you will need to create the ballowmultiinstances registry key on the proxy computer prior to installing the second instance. Other off-host proxy fanning requirements are noted in relevant steps of the installation procedures. For proxy fanning configurations, make sure that the Exchange Server specified during the installation of the second instance exists within the same domain as the Exchange Server specified during installation of the first instance. 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. Exchange Server 2003 If you will be installing the Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver Agent on an off-host proxy client (i.e., a computer other than the Exchange Server), perform the following pre-requisite tasks before installing these agents: 1. Ensure that the proxy computer has been added to the same Domain in which the Exchange Server 2003 resides.

31 Page 31 of We recommend installing Outlook 2003 on the off-host proxy client in order to supply the software drivers necessary for Exchange-based agents to function in an off-host proxy configuration. Alternatively, you can install the exchangemapicdo.exe software on the proxy computer (available for download from Microsoft Corporation), or use the Exchange Management Tools 2003 to accomplish this task. All Exchange Server Versions Prior to installing the Exchange Mailbox idataagent, Exchange Public Folder idataagent, Exchange Compliance Archiver, Exchange Mailbox Archiver and/or Exchange Public Folder Archiver you must create a mail-enabled user that has the proper permissions. Some points to keep in mind when setting up this mail-enabled user are listed below. Use MailboxAdmin, or something similar, as the mailbox name. In order for the MailboxAdmin user to perform basic operations, certain permissions are required. The MailboxAdmin user must be a member of the Local Administrator Group and have rights to all mailboxes on the server. There are a number of different ways to grant permissions for the MailboxAdmin user to have the proper rights. Listed below are three of the most common. These procedures may need to be changed depending on your privacy and security policies. For the Exchange Public Folder idataagent, the MailboxAdmin user must be the "Owner" of all public folders. 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. Method Three (Exchange Server 2007): 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 Organization Administrators group. Click Add. 4. Verify that the group selected is added to the list box. 5. Click Apply and OK to close the window.

32 Page 32 of 77 Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain. For more information refer to the following publications: Microsoft TechNet ( XADM: How to Get Service Account Access to All Mailboxes in Exchange 2000 ( Exchange 2007 Permissions: Frequently Asked Questions ( Install Checklist Collect the following information before installing the software. Use the space provided to record the information, and retain this information in your Disaster Recovery binder. 1. Name of the disk group in which the virtual server resides See Cluster Selection for more information. 2. Install folder location: See Select Components for Installation for more information. 3. If the CommServe Server and the client computer communicate across a firewall: Firewall ports: Hostnames and/or IP Addresses and corresponding GxCVD port numbers of computers on the other side of the firewall: Keep Alive Interval minutes: Hostname for outgoing tunnel connections: Tunnel Initialization Interval seconds: See Firewall Configuration for more information. 4. Client computer's Host name (NetBIOS name) or IP address See Configuration of Other Installation Options for more information. 5. CommServe Host Name or the CommServe IP address: See Configuration of Other Installation Options for more information. 6. Job result folder location: If necessary, Name and Password for the specified folder: See Configuration of Other Installation Options for more information. 7. Storage Policy used by the default subclient:

33 Page 33 of 77 See Storage Policy Selection for more information. 8. Client Group to which this Client will be associated: See Client Group Selection for more information. 9. Exchange Administrator Account Name: Exchange Administrator Account Password: Exchange Administrator Mailbox Name: Exchange Administrator Profile Name: Exchange Server Name: Exchange Server Domain: See Configure Exchange Specific Information for more information. 10. Outlook Web Access Alias: See Outlook Web Access Option for more information. 11. Time and frequency for Install of Automatic Updates: See Schedule Automatic Update for more information. Before You Begin Log on to the active node as the Domain User with administrative privileges to all nodes on the cluster. 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. If remotely installing to other physical nodes of the

34 Page 34 of 77 cluster, ensure you mount the software installation disc on a UNC path or a shared location (e.g., \\machine_name\shared_directory_name). 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. This screen will only appear when the ballow32bitinstallon64bit registry key has been created and enabled on this computer. 4. Select the option to install software on this computer. The options that appear on this screen depend on the computer in which the software is being installed. 5. Read the Welcome screen. Click Next to continue, if no other applications are running. 6. Read the virus scanning software warning. Click OK to continue, if virus scanning software is disabled. 7. Read the license agreement, then select I accept the terms in the license agreement. Click Next to continue. Cluster Selection 8. Select Configure a Virtual Server. Click Next to continue. 9. Select the disk group in which the virtual server resides. Click Next to continue.

35 Page 35 of 77 Select Components for Installation 10. Select the component(s) to install. 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. 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 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 11. Click Yes to set up the required privileges for the local administrators group. 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.

36 Page 36 of 77 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. 12. Specify the location where you want to install the software. 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. If you intend to use the SnapProtect feature for Windows File System idataagent, the agent should be installed on a non-system drive and not a filer volume. Click Browse to change directories. Click Next to continue. Proprietary disk resources will not appear in the browse window. To install to a proprietary disk resource, manually enter the path. After installing to a proprietary disk resource, the error message CVD failed to set dependency may be generated. To set the dependency, open the Cluster Administrator and select the CVD that has just been installed. Click on the Properties Dependencies tab, and click Modify. Select the proprietary disk resource and click OK. Do not select the same destination drive in which the MSCS resides. Firewall Configuration 13. Select from the following: If this Client communicates with the CommServe Server and/or MediaAgent across a firewall, select Yes, configure firewall

37 Page 37 of 77 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. 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. 14. 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. 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:

38 Page 38 of 77 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. 15. 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. 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. 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. 16. If desired, modify the Keep Alive interval. Click Next to continue.

39 Page 39 of 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. 18. If desired, modify the Tunnel Initialization interval. Click Next to continue. Configuration of Other Installation Options 19. Enter the fully qualified domain name of the CommServe computer. (TCP/IP network name. e.g., computer.company.com) 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

40 Page 40 of 77 previously specified. Click Next to continue. 20. 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. 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. 21. 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. Do not use spaces when specifying a new name for the Client. The default network interface name of the client computer is displayed if the computer has only one network interface. If the computer has multiple network interfaces, enter the interface name that is preferred for communication with the CommServe Server. If a component has already been installed, this screen will not be displayed; instead, the install program will use the same name as previously specified. Click Next to continue. 22. Specify the following and click Next to continue: Type the location of the client's job results directory, or click Browse.

41 Page 41 of 77 The Agent uses the job results directory to store the client's backup and restore job results. Storage Policy Selection 23. Select the storage policy through which you want to back up/archive the indicated component (subclient, instance, etc.) A storage policy directs backup data to a media library. Each library has a default storage policy. When you install an Agent, the install program creates a default subclient for most Agents. If desired, you can change your storage policy selection at any time after you have installed the client software. If applicable, enable Global Filters for the default subclient. If this screen appears more than once, it is because you have selected multiple agents for installation and are configuring storage policy association for each of the installed agents. Click Next to continue. Client Group Selection 24. Select a Client Group from the list. Click Next to continue. This screen will be displayed only if Client Groups are configured in the CommCell Console. For more information, see Client Computer Groups.

42 Page 42 of 77 Configure Exchange Specific Information 25. Enter the following Exchange Administrator information then click Next to continue: Account Name - Domain user account created with the proper permissions. Do not include the domain name here. Account Password - The password assigned to the domain user. Mailbox Name for this Account - Mailbox associated with the user above. Profile Name - Created during agent install. This profile is associated with the domain user's mailbox. Exchange Server Name - Name of the Exchange Server that the agent will communicate with for data protection and recovery operations. Domain - The Windows domain that the Exchange Server resides in. The installation detects and enters a domain name. If necessary, this field can be modified. The Exchange Administrator Account Information dialog will appear only once during the installation of multiple Exchange MAPIbased agents, and the account settings established initially will apply to all of them. To specify different Exchange Administrator Account settings for each Exchange MAPIbased agent, either install the agents separately or manually modify the account information in the Agent properties. If you are installing the agent on a 32-bit offhost proxy computer, or are performing a multi-instance proxy fanning install, ensure that you enter the name of the appropriate Exchange Server in the Exchange Server Name field. In some cases, a pre-populated default value for this field will appear and may need to be changed depending on your configuration. See the Exchange Agents section in User Accounts and Passwords for more information. Outlook Web Access Option 26. A dialog will ask you to enter an alias that you will use to connect to the system via your web browser, for the purpose of recovering archived messages from stubs using Outlook Web Access (OWA). Type in the desired alias, then click Next to continue.

43 Page 43 of 77 For multi-instance installs, the alias must be different for each instance you are installing. Download and Install Latest Packs 27. Select Download Pack(s) and Install to download and install the latest service packs and post packs from the software provider. Internet connectivity is required to download updates. This step is applicable when installing on the first instance. Updates are downloaded to the following directory: <software installation>/base/temp/downloadedpacks. They are launched silently and installed automatically for the first instance. Click Next to continue. Verify Summary of Install Options 28. Verify the summary of selected options. The Summary on your screen should reflect the components you selected for install, and may look different from the example shown. Click Next to continue or Back to change any of the options. The install program now starts copying the software to the computer. This step may take several minutes to complete. 29. The System Reboot message may be displayed. If so, select one of the following: Skip Reboot This option will be displayed if the install program finds any files belonging to other applications, that need to be replaced. As

44 Page 44 of 77 these files are not critical for this installation, you may skip the reboot and continue the installation and reboot the computer at a later time. Reboot Now If this option is displayed without the Skip Reboot option, the install program has found files required by the software that are in use and need to be replaced. If Reboot Now is displayed without the Skip Reboot option, reboot the computer at this point. The install program will automatically continue after the reboot. Exit Setup If you want to exit the install program, click Exit Setup. Schedule Automatic Update 30. If necessary, select this option to schedule an automatic installation of software updates. Install Updates Schedule allows automatic installation of the necessary software updates on the computer on a single or weekly basis. If you do not select this option, you can schedule these updates later from the CommCell Console. To avoid conflict, do not schedule the automatic installation of software updates to occur at the same time as the automatic FTP downloading of software updates. You may be prompted to reboot the computer before restarting services. If a component has already been installed, this screen will not be displayed; instead, the installer will use the same option as previously specified. Click Next to continue. Install Remaining Cluster Nodes 31. To install/upgrade the software on the remaining nodes of the cluster, click Yes. To complete the install for this node only, click No. 32. Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list. The list of Preferred Nodes displays all the

45 Page 45 of 77 nodes found in the cluster; from this list you should only select cluster nodes configured to host this virtual server. Do not select nodes that already have multiple instances installed. For more information, see Multi Instancing. When you have completed your selections, click Next to continue. 33. Type the User Name and Password for the Domain Administrator account, so that the installer can perform the remote install/upgrade of the cluster nodes you selected in the previous step. Click Next to continue. 34. The progress of the remote install for the cluster nodes is displayed; the install can be interrupted if necessary. Click Stop to prevent installation to any nodes after the current ones complete. Click Advanced Settings to specify any of the following: Maximum number of nodes on which Setup can run simultaneously. Time allocated for Setup to begin executing on each node, after which the install attempt will fail. Time allocated for Setup to complete on each node, after which the install attempt will fail. If, during the remote install of a cluster node, setup fails to complete or is interrupted, you must perform a local install on that node. When you do, the install begins from where it left off, or from the beginning if necessary. For procedures, see Manually Installing the Software on a Passive Node. 35. Read the summary for remote installation to verify that all selected nodes were installed

46 Page 46 of 77 successfully. If any node installation fails, you must manually install the software on that node once the current installation is complete. (See Manually Installing the Software on a Passive Node for step-by-step instructions.) The message displayed on your screen will reflect the status of the selected nodes, and may look different from the example. Click Next to continue. Setup Complete 36. Click Next to continue. Schedules help ensure that the data protection operations for the Agent are automatically performed on a regular basis without user intervention. For more information, see Scheduling. 37. Click Yes to remove the privileges that were assigned earlier by the install program. If you do not wish to remove them, click No. This option will only be displayed if you were prompted to assign the privileges earlier in the installation. 38. Setup displays the successfully installed components. The Setup Complete message displayed on your screen will reflect the components you installed, and may look different from the example shown. If you install an Agent with the CommCell Console open, you need to refresh the CommCell Console (F5) to see the new Agents. If Reboot Now button is displayed make sure to reboot the computer before performing any other operations from the computer. Click Finish to close the install program.