All but Neverfail can protect multiple Exchange servers with one backup server, Neverfail requiring one backup server for each Exchange server protected.
The iSCSI booting is handled via emBoot, with the initial boot stage run via PXE, the same as all other servers. As with Neverfail, users connecting via MAPI or Outlook Web Access may need to restart the client to connect to the backup server.
You will need to create service accounts, as with the other solutions, but the documentation steps you through the process.
You will need to create service accounts, as with the other solutions, but the documentation steps you through the process.
Archiving can be driven by fine-grain policies, but policy is applied on a per-store basis. Backups can be scheduled, but restores are performed manually.
A low-bandwidth module is available that enables compression and encryption over a WAN link, as well as asynchronous replication. All of the servers should be in the same Windows domain.
A low-bandwidth module is available that enables compression and encryption over a WAN link, as well as asynchronous replication.
After the key has been received from Neverfail, the system clones the Exchange server to the backup system. Support for Xen is under consideration.
Other screens are equally uncluttered, but less intuitive: They require practice to locate important items. You can track every change to some accounts, while keeping only the latest copy of other mailboxes, but only by spreading the accounts across separate stores.
Linux personas are generally built and run as netboot systems, with their file system residing on an NFS server central to the solution.
Unfortunately, the manuals have no explanations of error messages nor is there an accessible knowledge base on the Web site, so when a problem occurs you have no option but to call tech support.
Pricing is per pair of servers, based on the server in the pair with the greater number of CPUs. Other screens are equally uncluttered, but less intuitive: They require practice to locate important items. Only one gateway is needed at each end, and one Recovery server can support multiple Source servers. These procedures are well-documented in the manuals.
After a reservation has been made, the administrator can run the configuration or release it to a team member for deployment. The UI updated with the status of the VMware server persona showing as down, and the Web servers showing a status of retargeting, but nothing happened. All transactions are recorded as they occur, ensuring no loss of e-mails that have arrived since the last backup.
If you have a lot of users with fat inboxes, you might want to start replication over a weekend. For instance, an Apache Web server could be built on any physical server, configured, have an application installed, and then be condensed into a persona. This ensures that the proper interface exists on the proper network with the proper IP information. This is more the fault of Windows itself, which is less forgiving than other OSes when the underlying hardware changes.
Any changes to the mailboxes that occur during the fail-over are incrementally updated on the primary server. Users must restart Outlook to reconnect to the backup mailboxes.
Maybe even on an enterprise scale.
For maximum protection, administrators might choose to implement a fail-over system plus the CDP that DigiVault provides.
A low-bandwidth module is available that enables compression and encryption over a WAN link, as well as asynchronous replication.
You can track every change to some accounts, while keeping only the latest copy of other mailboxes, but only by spreading the accounts across separate stores. Picking up on the familiar theme, these reports mostly focus on resource allocation and availability.
Users connecting via MAPI or the Outlook Web Access client may need to restart the client to connect to the backup server.
Although some admins may take issue with the absence of automated fail-over, the product is easy to set up and administer and offers a reasonable value.