1. Add clients following these steps:

  • Exchange 2007 requires creating two clients on the CFA: one 64-bit client to backup the Exchange database files, and one 32-bit client to backup the email at the mailbox and message level. The two clients must communicate with the Exchange server over different ports. Follow these instructions:
    1. Add one client with a name like Ex07Data. Create the client selecting MS Windows/x64 as the Client OS. Edit this client to use TCP port 9202.
      If you are running 3.5 RevOS version, make sure the "Enable/Override" option is selected in the client file set. If this is not enabled, the database will not be backed up.
    2. Add another client with a name like Ex07Mailboxes. Create this client selecting MS Windows as the client OS.

2. Install the client software.

  • The client software can be downloaded from the Clients > Software tab.
  • Be sure to install the 64-bit agent for the Ex07Data client AND the 32-bit agent for the Ex07Mailboxclient.

3. Install the MAPI client libraries.

  • MAPI client libraries are not included in the base installation of Exchange 2007. To enable the message level backups you will be required to download and install the Microsoft file ExchangeMapiCdo.exe.</span>

4. Configure the 32-bit agent. This is the agent that will run the mailbox level backup.

  • Confirm that VSS is disabled (do not use) for this client. Edit the client file set (Clients > Edit > Pencil Button next to FileSet) and make sure the VSS option is not marked. To do this select the radio button for: Do Not Use Service.
  • If you are running 3.5 or higher RevOS version, make sure the "Enable/Override" option is selected for Exchange Mailbox in the client file set. If this is not enabled, the mailboxes will not be backed up.
  • Because of Exchange overhead, the mailbox level backup will be considerably slower than the database or flat file backup.
    • Any flat file or system writer backups should be configured on the x64 database client to maximize backup speeds. Remove the reference to C:/ from Starting Directories and Files on the x32 bit agent.
  • Confirm that Deduplication is disabled for this client- mailbox level backups cannot be deduplicated.
    • NOTE If you are running RevOS 4 or higher mailbox backups will now deduplicate. Please upgrade your OS.
  • A simplified set of permissions for the account running the backup service on Exchange 2007 are as follows (with DOMAIN=your domain, below):

    Note: this user will need to have a mailbox, the mailbox cannot be hidden, and you need to be able to send and receive mail from this mailbox to allow mailbox level backups to succeed.

    1) Create a domain user (such as "RvxBackup") with a User Mailbox (easiest using Exchange Management Console).
    *) This user's mailbox cannot have the "Hide from Exchange address lists" property checked.
    2) Add the user to the group on the Exchange server: BUILTIN\Administrators
    *) My Computer > Manage > Local Users and Groups > Groups > Administrators > Add to Group... > DOMAIN\RvxBackup
    3) Add the user to the domain group: DOMAIN\Exchange Organization Administrators
    4a) On the Exchange server > Backup Agent (the 32-bit client with unqualified name, not 64-bit) > Configure Backup > Run as Administrator > Service Control > Stop
    4b) Run Service As: > (x) Other Account: "DOMAIN\RvxBackup" > Password: *** > Confirm Password: *** > Start

5. In addition to considerations for setting up Exchange 2007 for backup, when running on Server 2008, IPv6 must be disabled using the following procedure.

  • This only applies if the Exchange server host is not also a domain controller.
  • The goal will be to enable access to Exchange's MAPI interface when running Exchange 2007 server on Server 2008. Exchange's MAPI interface is used by programs such as Exchange Mailbox Backup to access and restore mailbox data.

    The problem is due to some Exchange services not registering to listen on ports in the IPv6 stack, but only on IPv4. We found a [related issue]( http://msexchangeteam.com/archive/2008/06/20/449053.aspx){:target=\_blank} involving Outlook Anywhere
    . Using those instructions relevant to our backup scenario, we found a pretty simple fix:
  • 1) Notepad > Run as Administrator
    2) File > Open > "C:\Windows\System32\drivers\etc\" > [All Files] > "hosts" > Open

    Comment out the line "::1 localhost"
    Add the following two lines:


    An example might look like: localhost
    #::1 localhost exchange-server exchange-server.your-domain.com


    3) Run a backup and let us know - if everything else is setup correctly, it should work.

    If the backup has subsequent problems, please send us the Message Logs of the backup after doing the above, or we can look for ourselves is a tunnel is established.

    </li> </ul>

    Other Notes and Recommendations.

    • Please make sure that you do not have any other backup program running when the CFA starts a backup. They could conflict over VSS access causing one or both backups to fail.
    • Also, do not use another program to backup exchange databases. The VSS writer will not distinguish between the backup programs, so the incremental or differential backup from one program could depend on incrementals, differentails and fulls run by the other. Becuase of this, neither system will have everything needed to restore anything other than full backups.
    • Do not install Outlook on the Exchange Server. Installing Outlook with break the MAPI we depend on for mailbox backups
    • The client may be started from either the RVXConfig tool or the Services window.
    • Verify that your Exchange client has a green check mark in the Client > Summary tab. You may test the new client by running a manual backup.
      • After a possible system state backup, the MBXBackup is performed at the beginning, you may see this working by viewing the properties of a running job.
    • We strongly encourage the use of a Weekly schedule for an Exchange client. Please do not run a schedule that mixes differential and incremental backups.
    • Though allowed, we do not recommend truncating the logs after incremental or differential backups. By default we truncate the logs only after a full database level (ESE) backup.
    • To verify that Exchange has been backed up, either browse the job(s) in the Job History or browse the client from the Client Summary. You may see the default C:/ directory and also a new EXCHANGE:/ directory. Both directories can be browsed.
      • The EXCHANGE/ directory contains an ESEBackup and/or an MBXBackup directory. The ESEBackup directory contains the Exchange or mailbox databases. The MBXBackup directory contains the individual mailboxes with their data and e-mail messages.

    Note: If you make any changes to the client configuration via the RVXConfig window while the client is running, you must restart the client before changes take effect.

    *[AES]: Advanced Encryption Standard *[AESs]: Advanced Encryption Standards *[API]: application programming interface *[APIs]: application programming interfaces *[AWS]: Amazon Web Services *[AWSs]: Amazon Web Servicess *[BMR]: BareMetal Restore *[BMRs]: BareMetal Restores *[CAB]: Cloud Application Backup *[CABs]: Cloud Application Backups *[CB]: Cloud Backup *[CBs]: Cloud Backups *[CBT]: Changed Block Tracking *[CBTs]: Changed Block Trackings *[CFA]: cloud failover appliance *[CFAs]: cloud failover appliances *[CIFS]: Common Internet File System *[CIFSs]: Common Internet File Systems *[DC]: data center *[DCs]: data centers *[DDFS]: deduplication file system *[DDFSs]: deduplication file systems *[DDFS-AR]: DDFS-assisted replication *[DDFS-ARs]: DDFS-assisted replications *[DPS]: Data Protection Server *[DPSs]: Data Protection Servers *[DR]: disaster recovery *[DRs]: disaster recoverys *[DRaaS]: Disaster Recovery as a Service *[DRaaSs]: Disaster Recovery as a Services *[GCP]: Google Cloud Platform *[GCPs]: Google Cloud Platforms *[ICAB]: Infrascale Cloud Application Backup *[ICABs]: Infrascale Cloud Application Backups *[ICB]: Infrascale Cloud Backup *[ICBs]: Infrascale Cloud Backups *[ICMP]: Internet Control Message Protocol *[ICMPs]: Internet Control Message Protocols *[IDR]: Infrascale Disaster Recovery *[IDRs]: Infrascale Disaster Recoverys *[IPMI]: Intelligent Platform Management Interface *[IPMIs]: Intelligent Platform Management Interfaces *[JVM]: Java virtual machine *[JVMs]: Java virtual machines *[LVM]: logical volume management *[LVMs]: logical volume managements *[MFA]: multi-factor authentication *[MFAs]: multi-factor authentications *[MSP]: managed services provider *[MSPs]: managed services providers *[N/A]: Not applicable *[N/As]: Not applicables *[NAS]: network-attached storage *[NASs]: network-attached storages *[NAT]: network address translation *[NATs]: network address translations *[NFS]: Network File System *[NFSs]: Network File Systems *[NIC]: network interface controller *[NICs]: network interface controllers *[NTP]: Network Time Protocol *[NTPs]: Network Time Protocols *[NTPD]: Network Time Protocol Daemon *[NTPDs]: Network Time Protocol Daemons *[OBRM]: Online Backup and Recovery Manager *[OBRMs]: Online Backup and Recovery Managers *[PBKDF2]: Password-Based Key Derivation Function 2 *[PBKDF2s]: Password-Based Key Derivation Function 2s *[POSIX]: Portable Operating System Interface for Unix *[POSIXs]: Portable Operating System Interface for Unixs *[RAID]: Redundant Array of Independent Disks *[RAIDs]: Redundant Array of Independent Diskss *[RCT]: resilient change tracking *[RCTs]: resilient change trackings *[ROM]: read-only memory *[ROMs]: read-only memorys *[SDK]: software development kit *[SDKs]: software development kits *[SMB]: Server Message Block *[SMBs]: Server Message Blocks *[SMTP]: Simple Mail Transfer Protocol *[SMTPs]: Simple Mail Transfer Protocols *[SNMP]: Simple Network Management Protocol *[SNMPs]: Simple Network Management Protocols *[UCAR]: unique content addressable repository *[UCARs]: unique content addressable repositorys *[UDP]: User Datagram Protocol *[UDPs]: User Datagram Protocols *[UEFI]: Unified Extensible Firmware Interface *[UEFIs]: Unified Extensible Firmware Interfaces *[UNC]: Universal Naming Convention *[UNCs]: Universal Naming Conventions *[vCFA]: virtual cloud failover appliance *[vCFAs]: virtual cloud failover appliances *[VM]: virtual machine *[VMs]: virtual machines *[VNC]: Virtual Network Computing *[VNCs]: Virtual Network Computings *[vNIC]: virtual network interface controller *[vNICs]: virtual network interface controllers *[VPN]: virtual private network *[VPNs]: virtual private networks *[VSS]: Volume Shadow Copy Service *[VSSs]: Volume Shadow Copy Services