Veeam Explorer for Microsoft Exchange does not require a separate license. It is installed with Veeam Backup & Replication server or standalone management console; all editions including Veeam Backup Free Edition are supported (for details, see the Licensing and Editions section).
To install and use Veeam Explorer for Microsoft Exchange as a component of Veeam Backup & Replication, make sure that all necessary system requirements for Veeam Backup & Replication are met. System requirements specific for Veeam Explorer for Microsoft Exchange are listed below.
Specification | Requirement |
|---|---|
Microsoft Exchange | Veeam Explorer for Microsoft Exchange supports mailbox database (.EDB) files created by 64-bit versions of the following Microsoft Exchange systems:
Note: Veeam Backup & Replication quiesces the application and creates a snapshot for the Exchange Server VM, and for restore purposes it communicates with Exchange through the Client Access Server. Thus, restore of mailbox items will be supported regardless of membership of an Exchange Server in the DAG and IP address assigned to the DAG (in particular, in case of IP-less DAG in Exchange 2013 SP1 and later). To open mailbox databases, Veeam Explorer for Microsoft Exchange requires a service dynamic link library (ESE.DLL) which is installed together with Microsoft Exchange. |
Software | If you plan to export folders and items as Personal Folder Files (.PST), it is necessary to have a 64-bit version of Microsoft Outlook 2016, Microsoft Outlook 2013 or Microsoft Outlook 2010 installed on the machine where Veeam Explorer runs. |
Ports Used at Backup and Restore
The following table describes network ports that must be opened to ensure proper communication with the runtime coordination process deployed inside the Microsoft Exchange Server guest OS for application-aware processing during the backup.
From | To | Protocol | Port | Notes |
|---|---|---|---|---|
Veeam backup server or Guest interaction proxy (in Enterprise and Enterprise Plus editions) |
Exchange Server VM guest OS | TCP, UDP | 135, 137-139, 445 | Ports required to deploy the runtime coordination process on the VM guest OS. |
TCP | 6005-65535 | Dynamic RPC port range used by the runtime coordination process deployed inside the VM guest OS for application-aware processing (when working over the network).* Note that Exchange 2010 and higher (in particular, Client Access) expands standard Windows dynamic RPD port range - this allows for better scalability. For more information, see https://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx. | ||
Exchange Server VM guest OS | Veeam backup server or Guest interaction proxy (in Enterprise and Enterprise Plus editions) | TCP | 6005-65535 | Dynamic RPC port range used by the runtime coordination process deployed inside the VM guest OS for application-aware processing (when working over the network).* Note that Exchange 2010 and higher (in particular, Client Access) expands standard Windows dynamic RPC port range - this allows for better scalability. For more information, see https://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx. |
* - During setup, Veeam Backup & Replication automatically creates a firewall rule for the runtime process. However, if you use firewall settings other than default ones, or if application-aware processing fails with the “RPC function call failed” error, you need to configure dynamic RPC ports manually.
The following table describes network ports that must be opened to ensure proper communication with Microsoft Exchange Server during application-item restore.
From | To | Protocol | Port | Notes |
|---|---|---|---|---|
Veeam backup server/standalone console | Microsoft Exchange 2003/2007 CAS Server | TCP | 80, 443 | WebDAV connections |
Microsoft Exchange 2010/2013/2016 CAS Server | TCP | 443 | Microsoft Exchange Web Services Connections |
