Double Take Tech.-Info

Exchange Failover Toolkit 3.0

Note: To install the exchfailover.exe utility and application notes, the installation must be run on a server with a valid Double-Take activation code.

• Simplified setup of failover with new eXchange Protection Wizard (XPW)
• A workflow guided interface to allow the user to easily protect Exchange servers
• Discovers Exchange servers in the specified domain


• Automates setup and protection of Exchange data in addition to creation of monitoring and failover components.


• Ability to validate the configuration in addition to resolving "best practice" conflicts that are found between the source and target Exchange servers
• DNS Failover: New functionality and methodology to automatically update DNS resource records in order to seamlessly redirect network clients.


• Added the switch "-movehostspn" to exchfailover.exe for use in environments with Windows® 2003 Server Service Pack 1 and the Exchange server is a Outlook Web Access server

Downloaded, Installed and running within one hour with MCSE Qualifications.

Realtime replication and automatic failover in seconds of:

• Active Directory


• Citrix Profile Server


• Exchange


• Oracle


• Print Servers


• File Servers


• SQL. Exchange 2000 (Manual failover.)


• One to one for efficient realtime replication


• One to many replication for enhanced security


• Many to one for centralised Backup


• Failover and replication for Custom applications

Clustering solutions let you boost the availability, reliability, and scalability of Windows-based servers. A typical clustering configuration that addresses availability consists of two or more like nodes, typically connected to a shared storage subsystem. When these nodes function in an active-active configuration, the workload is distributed between the cluster nodes; however, the typical purpose of a cluster is to permit failover in the event of an application or hardware failure?

Clustering solutions let you boost the availability, reliability, and scalability of Windows-based servers. A typical clustering configuration that addresses availability consists of two or more like nodes, typically connected to a shared storage subsystem. When these nodes function in an active-active configuration, the workload is distributed between the cluster nodes; however, the typical purpose of a cluster is to permit failover in the event of an application or hardware failure?

Reducing Network Bandwidth when Replicating Microsoft SQL Server

If you're running a Microsoft SQL Server database and are concerned that your bandwidth usage may be higher than it should be, try excluding the temporary database (TEMPDB.MDF) from the replication set.

As you probably know, Double-Take only transmits data across the network when information is written to the disk. When a user reads information out of the database, one might think that this would not create a write, and therefore would not generate traffic across the network. However, Microsoft SQL Server responds to a query by first writing the results to a table in the temporary database. Over the course of many small queries (or a few large ones), a significant amount of unnecessary replication traffic may be generated.

To avoid this, simply exclude the temporary database from the replication set. This is completely safe because in a failover or other recovery situation, Microsoft SQL Server does not use any data contained in TEMPDB. This is a simple and safe way to reduce the amount of replication traffic without losing any ability to recover data on the targets. By the way, most other relational database systems work the same way, so this solution applies to them, too!

Feel free to visit our Tech Site, with more technical information. www.amtsoft.com/doubletake