Double-Take Availability 6.0 User Guide

Version 6.0User's Guide

Double-Take® AVAILABILITY™

Published: June 20, 2012 version 6.0 Copyrights, Trademarks, and Notices

ContentsChapter 1 Double-Take Availability overview 7

Core operations 8Double-Take Availability workloads 11Supported configurations 16Mirroring and replication capabilities 23

Chapter 2 Core Double-Take requirements 28

Chapter 3 Installation and activation 38Installation 39Installation notes 40Installing Double-Take Availability on aWindows server using the installationwizard 43Installing Double-Take Availability on aWindows server using the command lineutility 47Installing Double-Take Availability on a Linux server using the .rpm file 51Installing the Double-Take Virtual Recovery Appliance 53Installing Double-Take Availability on aWindows or Linux server using theDouble-Take Console 55Installing theWindows iSCSI Initiator 60

Licensemanagement and activation 61Managing the Double-Take license inventory 62Activating a single Double-Take server 65Activatingmultiple Double-Take servers 67Deactivating Double-Take licenses 69

Chapter 4 Double-Take Console 70Double-Take Console requirements 72Console options 73

Chapter 5 Managing servers 76Adding servers 80Providing server credentials 83Viewing server details 84Editing server properties 86General server properties 87Server licensing 88Server setup properties 91Double-Take queue 94Source server properties 98Target server properties 100E-mail notification configuration 102Script credentials 105

2

Log file properties 106Verification log 107

Server and job settings 110Viewing server events 166Viewing server logs 167Managing VMware servers 169Managing snapshots 170Snapshot states 170

Chapter 6 Selecting a protection type 174

Chapter 7 Files and folders protection 183Files and folders requirements 184Creating a files and folders job 186Managing and controlling files and folders jobs 213Viewing files and folders job details 224Validating a files and folders job 228Editing a files and folders job 229Viewing a files and folders job log 231

Failing over files and folders jobs 233Failback and restoration for files and folders jobs 234Restoring then failing back files and folders jobs 235Failing back then restoring files and folders jobs 237

Chapter 8 Full server protection 239Full server requirements 240Creating a full server job 244Managing and controlling full server jobs 269Viewing full server job details 280Validating a full server job 284Editing a full server job 285Viewing a full server job log 287

Failing over full server jobs 289Reversing full server jobs 292Reversing full server jobsmanually 294

Chapter 9 Exchange protection 298Exchange requirements 299Creating an Exchange job 303Managing and controlling Exchange jobs 330Viewing Exchange job details 341Validating an Exchange job 345Editing an Exchange job 346Viewing an Exchange job log 348

Failing over Exchange jobs 350Restoring then failing back Exchange jobs 353

Chapter 10 SQL protection 355SQL requirements 356Creating a SQL job 359Managing and controlling SQL jobs 384Viewing SQL job details 395

3

Validating a SQL job 399Editing a SQL job 400Viewing a SQL job log 402

Failing over SQL jobs 404Restoring then failing back SQL jobs 406

Chapter 11 Full server to Hyper-V protection 408Full server to Hyper-V requirements 409Creating a full server to Hyper-V job 411Managing and controlling full server to Hyper-V jobs 432Viewing full server to Hyper-V job details 443Validating a full server to Hyper-V job 447Editing a full server to Hyper-V job 448Viewing a full server to Hyper-V job log 449

Failing over full server to Hyper-V jobs 451

Chapter 12 Full server to ESX protection 454Full server to ESX requirements 455Creating a full server to ESX job 458Managing and controlling full server to ESX jobs 482Viewing full server to ESX job details 493Validating a full server to ESX job 497Editing a full server to ESX job 498Viewing a full server to ESX job log 499

Failing over full server to ESX jobs 501

Chapter 13 Full server to ESX appliance protection 504Full server to ESX appliance requirements 505Creating a full server to ESX appliance job 511Managing and controlling full server to ESX appliance jobs 520Viewing full server to ESX appliance job details 528

Failing over full server to ESX appliance jobs 532

Chapter 14 V to ESX protection 533V to ESX requirements 534Creating a V to ESX job 537Managing and controlling V to ESX jobs 546Viewing V to ESX job details 557Validating a V to ESX job 561Editing a V to ESX job 562Viewing a V to ESX job log 576

Failing over V to ESX jobs 578Reversing V to ESX jobs 579

Chapter 15 V to Hyper-V protection 580V to Hyper-V requirements 581Creating a V to Hyper-V job 583Managing and controlling V to Hyper-V jobs 598Viewing V to Hyper-V job details 609Validating a V to Hyper-V job 613Editing a V to Hyper-V job 614Viewing a V to Hyper-V job log 628

4

Failing over V to Hyper-V jobs 630Reversing V to Hyper-V jobs 632

Chapter 16 Host-level Hyper-V protection 633Host-level Hyper-V requirements 634Creating a host-level Hyper-V job 637Configuring Hyper-V Pro tip integration for failover notification 656Managing and controlling host-level Hyper-V jobs 658Viewing host-level Hyper-V job details 669Validating a host-level Hyper-V job 673Editing a host-level Hyper-V job 674Viewing a host-level Hyper-V job log 675

Failing over host-level Hyper-V jobs 677Reversing host-level Hyper-V jobs 679

Chapter 17 GeoCluster protection 680GeoCluster requirements 681Configuring your cluster for GeoCluster installation 682Establishing GeoCluster protection 685GeoCluster Replicated Disk resource properties 692

Monitoring and controlling GeoCluster jobs 698

Chapter 18 Simulating protection 702

Chapter 19 Monitoring tools 703Log files 704Viewing the log files through the Double-Take Console 705Viewing the log files through a text editor 709Filtering the log file with LogViewer 713

Statistics 715Viewing the statistics file 716Statistics 718

Error codes 725WindowsEvent messages 731Event messages 732

PerformanceMonitor 817Monitoring PerformanceMonitor statistics 817PerformanceMonitor statistics 818

Microsoft SystemsCenter OperationsManager 2007 826SNMP 829Configuring SNMP on your server 829SNMP traps 830SNMP statistics 833

Chapter 20 Special network configurations 837Firewalls 838Domain controllers 839NetBIOS 840WINS 841DNS 844Non-Microsoft DNS 851Macintosh shares 853

5

NFS Shares 854

Chapter 21 Recommended optimizations 855Planning 856Installation optimizations 857General optimizations 858Full server optimizations 862Application optimizations 863

Chapter 22 Security 865Adding users to the security groups 866

Changing the account used to run the Double-Take service onWindows servers 867

6

Chapter 1 Double-Take Availability overviewDouble-Take Availability ensures the availability of critical workloads. Using real-timereplication and failover, you can protect data, entire servers, individual applications,virtual servers, or clusters.

You identify what you want to protect on your production server, known as the source,and replicate that to a backup server, known as the target. The target server, on a localnetwork or at a remote site, stores a replica copy of the data from the source. Double-Takemonitors any changes to the source and sends the changes to the replica copystored on the target server. By replicating only the file changes rather than copying anentire file, Double-Take allows you tomore efficiently use resources.

7

Core operationsDouble-Take performs three basic types of operations.

l SeeMirroring on page 8—The initial copy or subsequent resynchronization ofselected data

l SeeReplication on page 9—The on-going capture of byte-level file changesl See Failover on page 10—The ability to stand-in for a server, in the event of afailure

MirroringMirroring is the process of transmitting user-specified data from the source to the targetso that an identical copy of data exists on the target. When Double-Take initially performsmirroring, it copies all of the selected data, including file attributes and permissions.Mirroring creates a foundation upon which Double-Take can efficiently update the targetserver by replicating only file changes.

If subsequent mirroring operations are necessary, Double-Take canmirror specific filesor blocks of changed data within files. Bymirroring only files that have changed, networkadministrators can expedite themirroring of data on the source and target servers.Mirroring has a defined end point when all of the selected files from the source have beentransmitted to the target. When amirror is complete, the target contains a copy of thesource files at that point in time.

1. Identical files are not mirrored.2. New files aremirrored.3. Different files can bemirrored.4. Checksums can calculate blocks of data to bemirrored.

8

ReplicationReplication is the real-time transmission of file changes. Unlike other relatedtechnologies, which are based on a disk driver or a specific application, the Double-Takereplication process operates at the file system level and is able to track file changesindependently from the file’s related application. In terms of network resources and time,replicating changes is amore efficient method of maintaining a real-time copy of datathan copying an entire file that has changed.

After a source and target have been connected through Double-Take, file systemchanges from the user-defined data set are tracked. Double-Take immediately transmitsthese file changes to the target server. This real-time replication keeps the data on thetarget up-to-date with the source and provides high availability and disaster recoverywith minimal data loss. Unlikemirroring which is complete when all of the files have beentransmitted to the target, replication continuously captures the changes as they arewritten to the source. Replication keeps the target up-to-date and synchronized with thesource.

1. A user or application updates part of a file.2. Only the changed portion of the file is replicated to the target.3. An up-to-date copy of the file ismaintained on the target.

9

FailoverFailover is the process in which a target stands in for a failed source. As a result, userand application requests that are directed to the failed source are routed to the target.

Double-Takemonitors the source status by tracking requests and responses exchangedbetween the source and target. When amonitored source does not respond to thetarget's requests, Double-Take assumes that the server has failed. Double-Take thenprompts the network administrator to initiate failover, or, if configured, it occursautomatically. The failover target assumes the identity of the failed source, and user andapplication requests destined for the source server or its IP address(es) are routed to thetarget.

When partnered with the Double-Take data replication capabilities, failover routes userand application requests with minimal disruption and little or no data loss.

1. User and application requests are sent to the source name or IP address.2. Data on the source ismirrored and replicated to the target.3. The target monitors the source for failure.4. In the event the source fails, the target stands in for the source. User and

application requests are still sent to the source name or IP address, which are nowrunning on the target.

10

Double-Take Availability workloadsIn addition to selecting your own files and folders that you want to protect, Double-Takecan protect specific types of workloads tomeet your protection and business goals.

Full server protectionFull server protection provides high availability for an entire server, including the systemstate, which is the server's configured operating system and applications. You identifyyour source, which is the server you want to protect, and your target, which is the serverthat will stand-in for the source in the event the source fails. Double-Takemonitors thesource for a failure, and if it fails, the target will stand-in for the source by rebooting andapplying the source system state on the target. After the reboot, the target becomes thesource.

1. The source data and system data, together a total image of the source, aremirrored and replicated to the target.

2. The target monitors the source for failure.3. In the even the source fails, the source's system state is applied when the target is

rebooted. After the reboot, the target is now the source, in both identity and withthe source data.

11

Application protectionApplication protection provides high availability for Microsoft Exchange or Microsoft SQLServer. You identify your source, which is the server running the application, and yourtarget, which is the server that will stand-in for the source in the event the source fails.Double-Take will gather information from your environment (application configuration,Active Directory, DNS, and so on) about the application being protected andautomatically protect the application. Double-Takemonitors the source server or theapplication services for a failure. If it fails, the target will stand-in for the source. End-users continue to access the application, now running on the target.

1. The configuration is sent to the target and then application data ismirrored andreplicated to the target.

2. The target canmonitor the application for failure.3. The target canmonitor the source for failure.

12

Virtual protectionVirtual protection provides high availability to Hyper-V or ESX virtual servers. Youidentify your source, which is the server you want to protect. Your source can be aphysical server, a virtual machine where you want to protect the data within the guestoperating system, or a virtual machine where you want to protect the host-level virtualdisk files (.vhd files). Your target is a Hyper-V or ESX server that will host a virtualmachine that is a replica of the source. Double-Takemonitors the source for a failure. Inthe event of a source failure, the replica virtual machine on the target can stand-inallowing end-users to continue accessing data and/or applications.

You can protect virtual workloads inmany different configurations. SeeSelecting aprotection type on page 174 for a decision tree to help you determine the best virtualprotection for your environment.

13

GeoCluster protectionIn a standard cluster configuration, a single copy of data resides on a SCSI disk that isshared between cluster nodes. Data is available without users knowing which nodeowns a cluster resource. MSCS handles failover between nodes of the cluster.

1. The source cluster nodes share data from a single SCSI disk.

In a GeoCluster configuration, data is stored on volumes local to each node andreplicated to each node in the cluster using Double-Take. This eliminates the single pointof failure of a standard cluster (shared disk) configuration.With GeoCluster, resourcesand groups are handled in the samemanner as a standard cluster. Instead of assigningone group by SCSI drive, you assign one group per logical volume. If a server, disk,group, or network interface should fail, MSCS relocates the failed group to another node,which contains the replicated copy of the data, thusmaintaining availability.

1. Users access data from the owning node.2. Data ismirrored and replicated between nodes of the cluster.

14

3. In the event the owning node changes, users access data from the new owningnode.

15

Supported configurationsDouble-Take is an exceptionally flexible product that can be used in a wide variety ofnetwork configurations. To implement Double-Take effectively, it is important tounderstand the possible configuration options and their relative benefits. Double-Takeconfigurations can be used independently or in varying combinations.

Not all types of jobs support all of these configurations. See the requirements ofeach job type to determine which configurations are supported.

l SeeOne-to-one, active/standby on page 17l SeeOne-to-one, active/active on page 18l SeeMany-to-one on page 19l SeeOne-to-many on page 20l SeeChained on page 21l SeeSingle server on page 22

16

One-to-one, active/standby

Description

One target server, having no production activity, is dedicated to supportone source server. The source is the only server actively replicatingdata.

Applications

l This configuration is appropriate for offsite disaster recovery,failover, and critical data backup. This is especially appropriate forcritical application servers such as Exchange, SQL Server, and webservers.

l This is the easiest configuration to implement, support, andmaintain.

Considerations

l This configuration requires the highest hardware cost because atarget server is required for every source server.

l Youmust pause the target when backing up database files on thetarget.

17

One-to-one, active/active

Description

Each server acts as both a source and target actively replicating data toeach other

Applications

This configuration is appropriate for failover and critical data backup.This configuration ismore cost-effective than the Active/Standbyconfiguration because there is no need to buy a dedicated target serverfor each source. In this case, both servers can do full-time productionwork.

Considerations

l Coordination of the configuration of Double-Take and otherapplications can bemore complex than the one-to-oneactive/standby configuration.

l During replication, each server must continue to process its normalworkload.

l Administratorsmust avoid selecting a target destination path that isincluded in the source’s protected data set. Any overlap will cause aninfinite loop.

l To support the production activities of both servers during failoverwithout reducing performance, each server should have sufficientdisk space and processing resources.

l Failover and failback scriptsmust be implemented to avoid conflictwith the existing production applications.


18

Many-to-one

Description

Many source servers are protected by one target server.

Applications

This configuration is appropriate for offsite disaster recovery. This isalso an excellent choice for providing centralized tape backup becauseit spreads the cost of one target server amongmany source servers.

Considerations

l The target server must be carefullymanaged. It must have enoughdisk space and RAM to support replication from all of the sourcesystems. The target must be able to accommodate traffic from all ofthe servers simultaneously.

l If using failover, scriptsmust be coordinated to ensure that, in theevent that the target server stands in for a failed server, applicationswill not conflict.


19

One-to-many

Description

One source server sends data tomultiple target servers. The targetserversmay or may not be accessible by one another.

Applications

This configuration provides offsite disaster recovery, redundantbackups, and data distribution. For example, this configuration canreplicate all data to a local target server and separately replicate asubset of themission-critical data to an offsite disaster recovery server.

Considerations

l Updates are transmittedmultiple times across the network. If one ofthe target servers is on aWAN, the source server is burdened withWAN communications.


l If you failover to one of the targets, the other targets stop receivingupdates.

20

Chained

Description

The source servers sends replicated data to a target server, which actsas a source server and sends data to a final target server, which is oftenoffsite.

Applications

This is a convenient approach for integrating local high availability withoffsite disaster recovery. This configurationmoves the processingburden ofWAN communications from the source server to thetarget/source server. After failover in a one-to-one, many-to-one, orone-to-many configuration, the data on the target is no longerprotected. This configuration allows failover from the first source to themiddlemachine, with the third machine still protecting the data.

Considerations

l The target/source server could become a single point of failure foroffsite data protection.


21

Single server

Description

Source and target components are loaded on the same server allowingdata to be replicated from one location to another on the same volumeor to a separate volume on the same server. These could be locallyattached SCSI drives or Fibre Channel based SAN devices.

Applications

This configuration is useful upgrading storage hardware while leavingan application online. Once the data ismirrored, you can swap the drivein the diskmanager. If the source and target copies of the data arelocated on different drives, this configuration supports high availability ofthe data in the event that the source hard drive fails.

Considerations

l This configuration does not provide high availability for the entireserver.

l This configurationmust be configured carefully so that an infiniteloop is not created.

22

Mirroring and replication capabilitiesFor Windows source servers, Double-Takemirrors and replicates file and directory datastored on anyNTFSWindows file system.(FAT and FAT32 are no longer supported.)Mirrored and replicated items also includeMacintosh files, compressed files, NTFSattributes and ACLs (access control list), dynamic volumes, files with alternate datastreams, sparse files, encrypted files, and reparse points. Files can bemirrored andreplicated acrossmount points, althoughmount points are not created on the target.

Double-Take does not mirror or replicate items that are not stored on the file system,such as physical volume data and registry based data. Additionally, Double-Take doesnot mirror or replicate NTFS extended attributes, registry hive files, Windows or anysystem or driver pagefile, systemmetadata files ($LogFile, $Mft, $BitMap,$Extend\\$UsnJrnl, $Extend\\$Quota, and $Extend\\$ObjId), hard links, or the Double-Take disk-based queue logs. The only exception to these exclusions is for the full serverjob types. If you are protecting your system state and data using full server protection,Double-Take will automatically gather and replicate all necessary system state data,including files for the operating system and applications.

Note the following replication caveats.

1. You cannot replicate from or to amapped drive.2. If any directory or file contained in your job specifically denies permission to the

system account or the account running the Double-Take service, the attributes ofthe file on the target will not be updated because of the lack of access. This alsoincludes denying permission to the Everyone group because this group containsthe system account.

3. If you select a dynamic volume and you increase the size of the volume, the targetmust be able to compensate for an increase in the size of the dynamic volume.

4. If you select files with alternate data streams, keep inmind the following.a. Alternate data streams are not included in the job size calculation.

Therefore, youmay see themirror process at 99-100% complete whilemirroring continues.

b. The number of files and directories reported to bemirrored will be incorrect.It will be off by the number of alternate streams contained in the files anddirectories because the alternate streams are not counted. This is areporting issue only. The streamswill bemirrored correctly.

c. Use the checksum option when performing a differencemirror orverification to ensure that all alternate data streams are compared correctly.

d. If your alternate streams are read-only, the timesmay be flagged asdifferent if you are creating a verification report only. Initiating a remirror withthe verification will correct this issue.

5. If you select encrypted files, keep inmind the following.a. Only the data, not the attributes or security/ownership, is replicated.

However, the encryption key is included. Thismeans that only the personwho created the encrypted file on the source will have access to it on thetarget.

23

b. Only data changes cause replication to occur; changing security/ownershipor attributes does not.

c. Replication will not occur until theWindowsCacheManager has releasedthe file. Thismay take awhile, but replication will occur when Double-Takecan access the file.

d. When remirroring, the entire file is transmitted every time, regardless of theremirror settings.

e. Verification cannot check encrypted files because of the encryption. Ifremirror is selected, the entire encrypted file will be remirrored to the target.Independent of the remirror option, all encrypted files will be identified in theverification log.

f. Empty encrypted files will bemirrored to the target, but if you copy or createan empty encrypted file within the job after mirroring is complete, the emptyfile will not be created on the target. As data is added to the empty file on thesource, it will then be replicated to the target.

g. When you are replicating encrypted files, a temporary file is created on boththe source and target servers. The temporary file is automatically created inthe same directory as the Double-Take disk queues. If there is not enoughroom to create the temporary file, an out of disk spacemessage will belogged. Thismessagemay bemisleading and indicate that the drive wherethe encrypted file is located is out of space, when it actuallymay be thelocation where the temporary file is trying to be created that is out of diskspace.

6. If you are usingmount points, keep inmind the following.a. By default, themount point data will be stored in a directory on the target.

You can create amount point on the target to store the data or maintain thereplicated data in a directory. If you use a directory, it must be able to handlethe amount of data contained in themount point.

b. Recursivemount points are not supported. If you select data stored on arecursivemount point, mirroring will never finish.

7. Double-Take supports transactional NTFS (TxF) write operations, with theexception of TxF SavePoints (intermediate rollback points).

a. With transactional NTFS and Double-Takemirroring, data that is in apending transaction is in what is called a transacted view. If the pendingtransaction is committed, it is written to disk. If the pending transaction isaborted (rolled back), it is not written to disk.

During a Double-Takemirror, the transacted view of the data on the sourceis used. Thismeans the data on the target will be the same as thetransacted view of the data on the source. If there are pending transactions,the Double-TakeTarget Data Statewill indicate Transactions Pending.As the pending transactions are committed or aborted, Double-Takemirrors any necessary changes to the target. Once all pending transactionsare completed, the Target Data Statewill update toOK.

If you see the pending transactions state, you can check the Double-Takelog file for a list of files with pending transactions. As transactions are

24

committed or aborted, the list is updated until all transactions are complete,and the Target Data State isOK.

b. During replication, transactional operationswill be processed on the targetidentically as they are on the source. If a transaction is committed on thesource, it will be committed on the target. If a transaction is aborted on thesource, it will be aborted on the target.

c. When failover occurs any pending transactions on the target will be aborted.d. Double-Take restore functions as amirror, except the roles of the source

and target are reversed. The transacted view of the data on the target isrestored to the source. As pending transactions are committed or abortedon the target, Double-Take restores any necessary changes to the source.Once all pending transactions are completed, the restoration is completeand replication will continue from the target to the source.

e. If you have restored your data before starting the failback process, makesure the restoration process does not have pending transactions and iscomplete before starting failback. If you are restoring your data after thefailback the process has completed, users will not be accessing the dataonce failback occurs, so there are no opportunities for pending transactions.

8. Double-Take supportsWindows 2008 symbolic links and junction points. Asymbolic link is a link (pointer) to a file. Junction points are also links, but to foldersand volumes.

a. If the link and the file/folder/volume are both in your job, both the link and thefile/folder/volume aremirrored and replicated to the target.

b. If the link is in the job, but the file/folder/volume it points to is not, only the linkismirrored and replicated to the target. The file/folder/volume that the linkpoints to is not mirrored or replicated to the target. A message is logged tothe Double-Take log identifying this situation.

c. If the file/folder/volume is in the job, but the link pointing to it is not, only thefile/folder/volume ismirrored and replicated to the target. The link pointing tothe file/folder/volume is not mirrored or replicated to the target.

d. Junction points will not be processed for orphan files.9. If you have theWindowsNtfsDisable8dot3NameCreation setting enabled (set to

1) on the source but disabled (set to 0) on the target, there is a potential that youcould overwrite and lose data on the target because of the difference in how longfile nameswill be associated with short files names on the two servers. This is onlyan issue if there are like named files in the same directory (for example,longfilename.doc and longfi~1.doc in the same directory). To avoid the potentialfor any data loss, the NtfsDisable8dot3NameCreation setting should be the sameon both the source and target.

10. Double-Take can replicate paths up to 32,760 characters, although eachindividual component (file or directory name) is limited to 259 characters. Pathslonger than 32760 characters will be skipped and logged.

11. If you rename the root folder of a job, Double-Take interprets this operation as amove from inside the job to outside the job. Therefore, since all of the files underthat directory have beenmoved outside the job and are no longer a part of the job,those files will be deleted from the target replica copy. This, in essence, will delete

25

all of your replicated data on the target. If you have to rename the root directory ofyour job, make sure that the job is not connected.

12. Keep inmind the following caveats when including and excluding date forreplication.

a. Do not excludeMicrosoft Office temporary files from your job. When a useropens aMicrosoft Office file, a temporary copy of the file is opened.Whenthe user closes the file, the temporary file is renamed to the original file andthe original file is deleted. Double-Take needs to replicate both the renameand the delete. If you have excluded the temporary files from your job, therename operation will not be replicated, but the delete operation will bereplicated. Therefore, you will havemissing files on your target.

b. WhenMicrosoft SQL Server databases are being replicated, you shouldalways include the tempdb files, unless you can determine that they are notbeing used by any application. Some applications, such as PeopleSoft andBizTalk, write data to the tempdb file. You can, most likely, excludetemporary databases for other database applications, but you shouldconsult the product documentation or other support resources before doingso.

c. Some applications create temporary files that are used to store informationthat may not be necessary to replicate. If user profiles and home directoriesare stored on a server and replicated, this could result in a significantamount of unnecessary data replication on large file servers. Additionally,the \Local Settings\Temporary Internet Files directory can easily reach afew thousand files and dozens of megabytes. When this ismultiplied by ahundred users it can quickly add up to several gigabytes of data that do notneed to be replicated.

d. Creating jobs that only contain one file may cause unexpected results. If youneed to replicate just one file, add a second file to the job to ensure the datais replicated to the correct location. (The second file can be a zero byte file ifdesired.)

13. Double-Take does not replicate the last access time if it is the only thing that haschanged. Therefore, if you are performing incremental or differential backups onyour target machine, you need tomake sure that your backup software is using anappropriate flag to identify what files have been updated since the last backup.Youmaywant to use the last modified date on the file rather than the date of thelast backup.

14. Keep inmind the following caveats when using anti-virus protection.a. Virus protection software on the target should not scan replicated data. If

the data is protected on the source, operations that clean, delete, orquarantine infected files will be replicated to the target byDouble-Take. Ifthe replicated data on the target must be scanned for viruses, configure thevirus protection software on both the source and target to delete orquarantine infected files to a different directory that is not in the job. If thevirus software denies access to the file because it is infected, Double-Takewill continually attempt to commit operations to that file until it is successful,and will not commit any other data until it can write to that file.

26

b. Youmaywant to set anti-virus exclusions on your source to improvereplication performance. There are risks associated with making exclusions,so implement them carefully. For more information, see theMicrosoft article822158 Virus scanning recommendations for Enterprise computers that arerunning currently supported versions ofWindows.

c. If you are using avast! anti-virus software, it must be installed in its defaultinstallation location if you want to protect your sever with a full serverprotection job. If it is not in its default installation directory, failover will fail.

15. SQL Server 2005 or later may not initialize empty space when the database sizeincreases due to the auto grow feature. Therefore, there is nothing for Double-Take to replicate when this empty space is created.When the empty space ispopulated with data, the data is replicated to the target. A verification report willreport unsynchronized bytes between the source and target due to the emptyspace. Since the space is empty, the data on the source and target is identical. Inthe event of a failure, the SQL database will start without errors on the target.

16. If you are running Symantec version 10 or later, youmay receive Event message16395 indicating that Double-Take has detected a hard link. Symantec uses ahard link to recover from a virus or spyware attack. Double-Take does not supporthard links, therefore, the Event message is generated, but can be disregarded.

17. If you have reparse points in your data set, Double-Take will replicate the tag,unless it is a known driver. If it is a known driver, for exampleMicrosoft SIS,Double-Take will open the file allowing the reparse driver to execute the file. In thiscase, the entire file will be replicated to the target (meaning the file is no longersparse on the target and has all the data).

18. Keep inmind if you have reparse points in your data set, youmust have thereparse driver available on the target in order to access this data after failover.

19. If you are using an archiving solution, do not archive any files after failover.Archiving files after failover could cause corruption.

20. If you are usingWindows 2008 and theMicrosoft WindowsUpdate feature,schedule your updates outside the timeswhen amirroring operation (initial mirroror remirror) is running.Windows updates that occur during amirror may causedata integrity issues on the target.

27

http://support.microsoft.com/kb/822158















Chapter 2 Core Double-Take requirementsEach Double-TakeWindows server must meet theminimum core requirements below.Your serversmay need tomeet additional requirements depending on the job type willbe selecting. See the requirements section for each of the job types for those specificrequirements.

l Operating system—There are different Double-Take editions depending on theoperating system you are using. Review the various editions from FoundationEdition below toVirtual Host PremiumEdition on page 33 to be sure you have thecorrect Double-Take edition for your operating system. The remaining corerequirements continue on page 33.

Microsoft Server Core 2008 R2 is supported for files and folders jobs, butmay have specific requirements or limitations for other job types. ServerCore 2008 is not supported for any job type.

Each of theWindows 2003 operating systems require Service Pack 1 orlater.

Foundation EditionWindows 2003 and 2003 R2 operating systems

l Storage Server Editionl Small Business Server

Windows 2008 and 2008 R2 operating systems

l Storage Server Edition i386 and x64l Small Business Server Standard and Premium x64l Foundation Server with SAKl Essential Business Server x64

Virtual server protection

There is no virtual server (guest-level or host-level) protectionwith the Foundation Edition.

Notes

You can install the Foundation Edition on a server running otherserver Windows operating systems, so you do not have to payextra for an upgraded Double-Take license.When theFoundation Edition is installed on a server running these otherserver Windows operating systems, the following limitationswillapply. 1) The server will function in a target role only. 2) Thetarget-only server can only protect a source that is running the

28

Double-Take Foundation Edition and one of the operatingsystem editions listed for the Foundation Edition. 3) Full serverprotection is the only supportedmethod of failover.

Standard EditionWindows 2003 and 2003 R2 operating systems

l Storage Server Editionl Small Business Serverl WebEdition i386 and x64l Standard Edition i386 or x64


l Storage Server Edition i386 and x64l Small Business Server Standard and Premium x64l Foundation Serverl Essential Business Server x64l WebServer i386 and x64l Standard Edition i386 and x64

Virtual server guest-level protection

The Standard Edition can run inside one virtual server to provideprotection for data and/or applications running on the guestoperating system.

Virtual server host-level protection

There is no virtual server host-level protection with the StandardEdition.

Advanced EditionWindows 2003 and 2003 R2 operating systems

l Storage Server Editionl Small Business Serverl WebEdition i386 and x64l Standard Edition i386 or x64l Enterprise Edition i386 and x64


l Storage Server Edition i386 and x64l Small Business Server Standard and Premium x64l Foundation Serverl Essential Business Server x64

29

l WebServer i386 and x64l Standard Edition i386 and x64l Enterprise Edition i386 and x64


The Advanced Edition can run inside one virtual server to provideprotection for data and/or applications running on the guestoperating system.


There is no virtual server host-level protection with the AdvancedEdition.

Notes

If you are using Hyper-V R2with Cluster Shared Volumes(CSV), you can use Double-Take within the guest. However, youwill be unable to protect the virtual machines at the host levelusing Double-Take.

Premium EditionWindows 2003 and 2003 R2 operating systems

l Storage Server Editionl Small Business Serverl WebEdition i386 and x64l Standard Edition i386 or x64l Enterprise Edition i386 and x64l Datacenter i386 and x64


l Storage Server Edition i386 and x64l Small Business Server Standard and Premium x64l Foundation Serverl Essential Business Server x64l WebServer i386 and x64l Standard Edition i386 and x64l Enterprise Edition i386 and x64l Datacenter Edition i386 and x64


The PremiumEdition can run inside a virtual server to provideprotection for data and/or applications running on the guestoperating system.

30


There is no virtual server host-level protection with the PremiumEdition.

Notes


Virtual Guest EditionWindows 2003 and 2003 R2 operating systems

l Storage Server Editionl Small Business Serverl WebEdition i386 and x64l Standard Edition i386 or x64l Enterprise Edition i386 and x64l Datacenter i386 and x64


l Storage Server Edition i386 and x64l Small Business Server Standard and Premium x64l Foundation Serverl Essential Business Server x64l WebServer i386 and x64l Standard Edition i386 and x64l Enterprise Edition i386 and x64l Datacenter Edition i386 and x64


The Virtual Guest Edition can run inside virtual servers to provideprotection for data and/or applications running on the guestoperating system.


There is no virtual server host-level protection with the VirtualGuest Edition.

Notes


31

Virtual Host Standard EditionWindows 2008 and 2008 R2 operating systems

l Standard EditionVirtual server guest-level protection

There is no virtual server guest-level protection with the VirtualHost Standard Edition.


The Virtual Host Standard Edition runs outside the virtual serverto protect the virtual disk (.vhd) and its associated files stored onthe host operating system. This edition can protect an unlimitednumber of virtual servers on a singleWindowsStandard EditionHyper-V host.

Notes

If you are using Hyper-V R2with Cluster Shared Volumes(CSV), you will be unable to protect the virtual machines at thehost level using Double-Take. However, you can use Double-Take within the guest using one of the non-host Double-Takelicenses.

Virtual Host Advanced EditionWindows 2008 and 2008 R2 operating systems

l Standard Editionl Enterprise Edition


There is no virtual server guest-level protection with the VirtualHost Advanced Edition.


The Virtual Host Advanced Edition runs outside the virtual serverto protect the virtual disk (.vhd) and its associated files stored onthe host operating system. This edition can protect an unlimitednumber of virtual servers on a singleWindowsStandard orEnterprise Edition Hyper-V host.

Notes

If you are using Hyper-V R2with Cluster Shared Volumes(CSV), you will be unable to protect the virtual machines at thehost level using Double-Take. However, you can use Double-

32

Take within the guest using one of the non-host Double-Takelicenses.

Virtual Host Premium EditionWindows 2008 and 2008 R2 operating systems

l Standard Editionl Enterprise Editionl Datacenter Edition


There is no virtual server guest-level protection with the VirtualHost PremiumEdition.


The Virtual Host PremiumEdition runs outside the virtual serverto protect the virtual disk (.vhd) and its associated files stored onthe host operating system. This edition can protect an unlimitednumber of virtual servers on a singleWindowsStandard,Enterprise, or Datacenter Hyper-V host.

Notes

If you are using Hyper-V R2with Cluster Shared Volumes(CSV), you will be unable to protect the virtual machines at thehost level using Double-Take. However, you can use Double-Take within the guest using one of the non-host Double-Takelicenses.

l File system—Double-Take supports the NTFS file system. FAT and FAT32 areno longer supported.

l System memory—Theminimum systemmemory on each server should be 1GB. The recommended amount for each server is 2 GB.

l Disk space for program files—This is the amount of disk space needed for theDouble-Take program files. For Windows 2003, this is approximately 300MB. ForWindows 2008, this is approximately 375MB.

The program files can be installed to any volumewhile theMicrosoftWindows Installer files are automatically installed to the operating systemboot volume.

Make sure you have additional disk space for Double-Take queuing,logging, and so on.

l Server name—Double-Take includesUnicode file system support, but your

33

server namemust still be in ASCII format. If you have the need to use a server'sfully-qualified domain name, your server cannot start with a numeric characterbecause that will be interpreted as an IP address.

l Protocols and networking—Your serversmust meet the following protocol andnetworking requirements.

l Your serversmust have TCP/IP with static IP addressing. (Some job typesallow you to add DHCP addresses for failover monitoring, although onlyafter a job has already been created. Keep inmind that depending on yourfailover configuration, a source reboot may or may not cause a failover buthaving a new address assigned byDHCPmay also cause a failover.)

l By default, Double-Take is configured for IPv6 and IPv4 environments, butthe Double-Take service will automatically check the server at servicestartup andmodify the appropriate setting if the server is only configured forIPv4. If you later add IPv6, you will need tomanuallymodify theDefaultProtocol server setting. SeeServer and job settings on page 110 fordetails.

l IPv6 is only supported for Windows 2008 servers.l If you are using IPv6 on your servers, your clientsmust be run from an IPv6capablemachine.

l In order to properly resolve IPv6 addresses to a hostname, a reverse lookupentry should bemade in DNS.

l Windows firewall—If you haveWindows firewall enabled on your servers, thereare two requirements for theWindows firewall configuration.

l TheDouble-Take installation programwill automatically attempt toconfigure ports 6320, 6325, and 6326 for Double-Take. If you cancel thisstep, you will have to configure the portsmanually.

l If you are using the Double-Take Console to push installations out to yourservers you will have to open firewall ports for WMI (WindowsManagementInstrumentation), which usesRPC (Remote Procedure Call). By default,RPC will use ports at random above 1024, and these portsmust be open onyour firewall. RPC ports can be configured to a specific range by specificregistry changes and a reboot. See theMicrosoft Knowledge Base article154596 for instructions. Additionally, you will need to open firewall ports forSMB (server message block) communicationswhich uses ports 135-139and port 445. As an alternative, you can disable theWindows firewalltemporarily until the push installations are complete.

See Firewalls on page 838 for instructions on handling firewalls in yourenvironment.

l NAT support—Double-Take does not support NAT configurations because youmust select an actual IP address on your source and target servers for monitoringand routing data. You cannot use external addresses.

l Windows Management Instrumentation (WMI)—Double-Take is dependenton theWMI service. If you do not use this service in your environment, contacttechnical support.

l Snapshots—Double-Take uses theMicrosoft Volume Shadow Copy service

34






(VSS) for snapshot capabilities. To use this functionality, your serversmust meetthe following requirements.

l Snapshot operating system—Your serversmust be running, at aminimum,Windows 2003 Service Pack 1. You should upgrade to ServicePack 2 or later so that several Microsoft patches that addressmemory leaksin the Volume Shadow Copy service are applied. If you do not have ServicePack 2 installed, you will need to review the patches available on theMicrosoft web site and install those that correct the Volume Shadow Copyservicememory leaks.

l Snapshot data—Snapshots are taken at the volume level. For example, ifyour job is protecting D:\data and E:\files, the snapshot will contain all of thedata on both the D: and E: volumes. If your job is only protecting D:\data(E:\files exists but is not included in the job), the snapshot will only containthe D: volume.

l Double-Take installation location—In order to enable Double-Takesnapshots, Double-Takemust be installed on the system drive. If Double-Take is not installed on the system drive, snapshots will be disabled whenenabling protection.

l Snapshot configuration—If you have related data on different drives onyour source (for example, an Exchange database on one drive and relatedlog files on another), snapshots of each drivemust be taken simultaneouslyso that the snapshots for each drive represent the same point in time.However, based on theMicrosoft Volume Shadow Copy snapshottechnology, different snapshots cannot be taken at the same time. To workaround this limitation and guarantee data integrity on the target, you need tocreate amount point, thus ensuring that one point-in-time consistentsnapshot will be taken of both volumes at once. To create amount point,create an empty folder on one of the drives. Using theDisk Managementtool in theWindows Computer Management applet, remove the driveletter from the other drive. Then create amount point by selectingMount inthe following empty NTFS folder and specifying the folder you justcreated. If you havemultiple drives, create an empty folder on the drive foreach of the other drives and createmount points to each of the folders.When the snapshot is taken of the drive, eachmount point will be included inthe snapshot. You will need tomodify your applications to specify the newlocation for the files that are now on themount point. For additional detailson creating and usingmount points, see your Windows referencemanual.For details onmodifying your applications, see your application referencemanual.

l Snapshot limitations—Sometimes taking a snapshot may not bepossible. For example, theremay not be enough disk space to create andstore the snapshot, or maybe the target is too low onmemory. If a snapshotfails, an Event message and a Double-Take logmessage are both createdand logged.

There are also limitations imposed byMicrosoft Volume Shadow Copy thatimpact Double-Take snapshots. For example, different Double-Take jobtypes create different snapshot types, either client-accessible or non-client-

35

http://msdn.microsoft.com/en-us/library/bb968832(VS.85).aspx



accessible. VSS onlymaintains 64 client-accessible snapshots, while itmaintains 512 non-client-accessible snapshots. If themaximumnumber ofsnapshots exists and another one is taken, the oldest snapshot is deleted tomake room for the new one.

Another example is that Double-Take snapshotsmust be created withinoneminute because Volume Shadow Copy snapshotsmust be createdwithin oneminute. If it takes longer than oneminute to create the snapshot,the snapshot will be considered a failure.

Additionally, Volume Shadow Copywill not revert snapshots of a volumewith operating system files, therefore Double-Take is also unable to revert avolumewith operating system files.

Youmust also keep inmind that if you are using extended functionalityprovided by Volume Shadow Copy, you need to be aware of the impactsthat functionalitymay have on Double-Take. For example, if you change thelocation where the shadow copies are stored and an error occurs, it mayappear to be a Double-Take error when it is in fact a Volume Shadow Copyerror. Be sure and review any events created by the VolSnap driver andcheck your Volume Shadow Copy documentation for details.

l Other snapshot functionality—You can use Volume Shadow Copy forother uses outside Double-Take, for exampleMicrosoft Backup uses it.Keep inmind though that the driver for Volume Shadow Copy is startedbefore the driver for Double-Take. Therefore, if you use snapshots on yoursource and you revert any files on the source that are protected by your job,Double-Take will not be aware of the revert and the file change will not bereplicated to the target. The file change will bemirrored to the target duringthe next mirroring process.

l Clusters—If your job type supports clustering, make sure your cluster meets thefollowing general requirements in addition to any job specific cluster requirements.

l Best practices—You should carefully review Microsoft documentation andresources for properly configuring your cluster before implementingDouble-Take on a cluster. TheMicrosoft TechNet articles Failover Clustersand Installing and Upgrading Cluster Nodes are two resources you canstart with. There aremany other resources available on theMicrosoftTechNet web site.

l Networking—The following networking requirements apply to your cluster.l Youmust have TCP/IP connections between nodes.l Multiple networks are recommended to isolate public and privatetraffic.

l The private network should be a unique subnet so that Double-Takewill not attempt to use an unreachable private network.

l Your network can contain direct LAN connections or VLANtechnology.

l For Windows 2003, the cluster nodesmust be on the same logical IPsubnet.

36

http://technet.microsoft.com/en-us/library/cc732488(WS.10).aspx







http://technet.microsoft.com/en-us/default.aspx




l For Windows 2003, themaximum round trip latency between nodesshould be nomore than½ second.

l Domain—The cluster nodesmust bemembers of the same domain.l DNS—Forward and reverse lookupsmust be implemented on the primaryDNS server for the cluster name and individual nodes.

l Cluster service account—ForWindows 2003 clusters, use the samecluster service account on source and target clusters.

l Double-Take disk queue—Ensure that the disk queue is not on a PhysicalDisk resource.

l Volumes—The source and target should have identical drivemappings.l Licensing—Each node in the cluster must have a valid Double-TakeAvailability activation code.

l Resource registration—In some cases, the Double-Take clusterresourcesmay not be registered automatically when Double-Take isinstalled. You canmanually register the resources by runningDTResUtility.exe, which is installed in the \Windows\Cluster directory.

37

Chapter 3 Installation and activationThe installation and activation for Double-Take servers is a two-part process. First, youwill have to install the software on your servers. Second, you will have to activate yourlicenses. Choose how you want to install and activate your servers using either of thefollowingmethods.

l Single server installation and activation—You can install and activate yourservers one at a time. In this scenario, you will install Double-Take on one serverand then you will activate the license on that server. You can repeat this processfor other servers.

l Multiple server installation and activation—You can install and activatemultiple servers at one time. In this scenario, you will need install Double-Take onall of your servers and then you will activate the licenses for all of the servers atonce.

The term installation is being used generically to represent a new Double-Takeinstallation or a Double-Take upgrade.

If you have received an evaluation activation code in order to test Double-Takebefore purchasing a license, you will not need to perform the activation steps.Your evaluation activation code will automatically disable all Double-Takefunctionality when the evaluation period expires. You will then need to update toa valid license and go through the activation process.

If you are going to be creating a V to Hyper-V or V to ESX job (seeSelecting aprotection type on page 174 for details on which job to create), the job creationprocess can automatically push the Double-Take installation out to the servers, ifyou have the Double-Take Availability Virtual Guest Edition license. After the jobis created, you will have 14 days to activate the licenses using either the singleserver method or themultiple server method. If you do not have a Double-TakeAvailability Virtual Guest Edition license, you will need to perform the installationoutside of the job creation process using the single server or multiple serversmethod.

If you protecting aGeoCluster configuration, where data is stored on volumeslocal to each node and replicated to each node in the cluster, you should confirmor configure your cluster configuration before beginning the installation. SeeConfiguring your cluster for GeoCluster installation on page 682.

See Installation on page 39 and Licensemanagement and activation on page 61 fordetails on the various installation and license and activationmethods.

38

InstallationReview the Installation notes on page 40 before beginning your installation. Then choosefrom one of the following installationmethods.

l Installing Double-Take Availability on aWindows server using the installationwizard on page 43—Use these instructions to install on a singleWindows serverusing the installation wizard. The wizard will guide you step by step through theinstallation process.

l Installing Double-Take Availability on aWindows server using the command lineutility on page 47—Use these instructions to install on a single or multipleWindows server using the command line utility. This utility automates theinstallation process by running an unattended, or silent, installation. It allows you topass parameters through to the installation program instead of enteringinformationmanually through the wizard.

l Installing Double-Take Availability on a Linux server using the .rpm file on page51—Use these instructions to install on a single Linux server using the .rpm file.The .rpm file can be launched from a Linux console or from a command prompt.

l Installing the Double-Take Virtual Recovery Appliance on page 53—If you will becreating a full server to ESX appliance job (seeSelecting a protection type onpage 174 for details on which job to create), use these instructions to install theDouble-Take Virtual Recovery Appliance on your ESX server. Youmust installthis appliance before you can push the Double-Take installation out to your Linuxsource servers using the Double-Take Console. Depending on your networkconfiguration, the appliancemay or may not have to be installed before you pushthe Double-Take installation out to your Windows source servers using theDouble-Take Console. In either case, youmust install the appliance before youcan create your full server to ESX appliance job.

l Installing Double-Take Availability on aWindows or Linux server using theDouble-Take Console on page 55—Once you have the Double-Take Consoleinstalled on aWindowsmachine, you can use it to push the installation out to yourother servers. The push installation is a full, client and server installation onWindows servers and a full server installation on Linux servers.

l Installing theWindows iSCSI Initiator on page 60—To support the full server toESX appliance job type, theWindows iSCSI Initiator is placed into a folder onWindows 2003 servers during any of the aboveWindows installations. You willhave to install it manually before creating a full server to ESX appliance job. Usethese instructions tomanually install theWindows iSCSI Initiator. If you are usingWindows 2008, the iSCSI Initiator is already installed, but you will have to enable itthrough Administrative Tools, if it is not already enabled. (By default, it is notenabled.)

39

Installation notesReview the installation notes below before beginning an installation or upgrade.

l Because Double-Take has operating system dependent files, if you are upgradingyour operating system (to a new major version, not a service pack) and haveDouble-Take installed, youmust remove Double-Take prior to the operatingsystem upgrade. Uninstall Double-Take, perform the operating system upgrade,and then reinstall Double-Take.

l During the installation, DTInfo is installed. This is a utility that can be run to collectconfiguration data for use when reporting problems to technical support. It gathersDouble-Take log files; Double-Take and system settings; network configurationinformation such as IP,WINS, and DNS addresses; and other data whichmay benecessary for technical support to troubleshoot issues.

l OnWindows server, the DTInfo utility is DTInfo.exe, and it is installed to theDouble-Take installation directory. After running the executable, a zip file isautomatically created with the information gathered.

l On Linux source servers, the DTInfo utility is DTInfo.sh, and it can be runfromDTSetup. After running the script, a .tar.gz is automatically createdwith the information gathered. Youmust have root (or uid 0 equivalent) toexecute the diagnostics or to copy or read the resulting file.

l On the Double-Take Linux appliance, DTInfo has to be runmanually. It islocated in /opt/dbtk and should be executed asDTInfo.sh -f. After runningthe script, a .tar.gz is automatically created with the information gathered.

l The following notes are specific toWindows servers.l Since Double-Take installs device drivers, it is recommended that youupdate your WindowsRecovery Disk, before installing or making changesto your servers. For detailed instructions on creating a recovery disk, seeyour Windows referencemanuals. Make sure that you select the option toback up the registry when building the repair disks.

l If you are installing to a drive other than the drive which contains yoursystemTEMP directory, theMicrosoft Windows Installer will still loadapproximately 100MB of data to the TEMP directory during the installation.If you do not have enough disk space on the drive that contains the TEMPdirectory, youmay need to change where it is located.

l If during the installation you receive themessage that the wizard wasinterrupted before the installation could be completed, you will need todelete the registry value DefaultAccessPermissions under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole key in order to installDouble-Take. This registry setting denies permissions for retrieving andsetting property values. Deleting this registry setting will not have a negativeimpact on your server.

l Double-Take 6.0 is interoperable back to version 5.2 (for Windows servers) but isrestricted to the following limitations. The Double-Take clients can only control thesame or older releases. To accommodate rolling upgrades, older sources canconnect to newer targets, but newer sources cannot connect to older targets.(Check the requirements for each individual job type, to see if Double-Take can be

40

upgraded with an existing job in place or if the existing job needs to be deletedbefore the upgrade.)

l 5.2 client—Supports 5.2 source and target, but does not support 5.3 or 6.0source or target

l 5.3 client—Supports 5.2 or 5.3 source and target as long as the target isthe same or newer than the source, but does not support 6.0 source ortarget

l 6.0 client—Supports 5.2, 5.3, or 6.0 source and target as long as the targetis the same or newer than the source

l When performing a rolling upgrade, update the target servers first. After theupgrade is complete, the sourceswill automatically reconnect to the targets.Upgrade the sourceswhen convenient.

l If you are using a chained configuration, update the last target first, then updatethemiddle server acting as both a source and target, and update the productionsource last.

l If you are using a configuration where the source is an older version than thetarget, you will not be able to restore from the newer version target back to theolder version source. Youmust upgrade the source to the same version as thetarget before restoring.

l Use the following procedure to upgrade Double-Take on aWindowsmulti-nodecluster. If both your source and target are clusters, use the following procedure onthe target cluster first, then on the source. If you are protecting Hyper-V virtualmachines at the host-level using a cluster configuration, you cannot upgrade. Youmust delete the existing job, upgrade all of your nodes, and then re-create the job.

1. Move all cluster resources to one node.2. Upgrade to the new version of Double-Take on all of the other nodes.3. Move the cluster resources to one of the upgraded nodes.4. Upgrade to the new version of Double-Take on the last node.5. If needed, move the cluster resources to the desired nodes.

l Use the following procedure to upgrade Double-Take on aWindows single-nodecluster. If both your source and target are clusters, use the following procedure onthe target cluster first, then on the source.

1. Take your cluster resources offline.2. Upgrade to the new version of Double-Take.3. After the upgrade is complete, bring the resources back online.

l If you are upgrading and are currently using theGeoCluster Replicated Disk asthe quorum resource, you will need to select another quorum resource beforeupgrading. SeeConfiguring your cluster for GeoCluster installation on page 682for more information.

l During an installation or upgrade, if the GeoCluster Replicated Disk resource filesfail to register with the cluster, use the DTResUtility, located in the\windows\cluster directory, to manually register the resources.

41

l The following files require administrator credentials. If you are not logged in withadministrator credentials, you will be prompted to supply them.

l dfo.exel DTInfo.exel setup.exe

42

Installing Double-Take Availability on a Windows server usingthe installation wizard

Make sure you have reviewed the Installation notes on page 40, and then use theseinstructions to install Double-Take Availability or upgrade an existing Double-TakeAvailability installation.

1. Close any open applications.2. Start the installation program using the appropriate instructions, depending on

your media source.

l Physical media—If auto-run is enabled, the installation programwill startautomatically. Tomanually start the program, selectStart,Run and specify<drive>:\autorun.exe.

l Web download—Launch the .exe file that you downloaded from the web.

If you are installing on Server Core, copy the physical media files or webdownload file to the Server Coremachine using a UNC share, and thenlaunch the installation program from the Server Coremachine. Theinstallation UI will display on the Server Coremachine.

3. When the installation program begins, the Autorun appears allowing you to installsoftware and view documentation and online resources. To install Double-TakeAvailability, select the Install Double-Take Availability link.

4. Depending on your version ofWindows and the components you have installed,youmay see an initial screen indicating that you need to install or enableMicrosoft.NET Framework. If you do not see this screen, your server already has theappropriate version of Microsoft .NET. Youmust install or enableMicrosoft .NETbefore installing Double-Take. SelectYes to install or enableMicrosoft .NET andclickContinue.

5. If you are upgrading from a previous version of Double-Take RecoverNow, andyou have anyDouble-Take archived or deduplicated files, you will be prompted torecall and restore those filesmanually. Double-Take RecoverNow willautomatically be uninstalled, however youmust recall and restore those files first.

6. You will be given the opportunity to check for amore recent version of thesoftware.

l If you do not want to check for a later version, selectNo and clickNext.l If you want to check for a later version, selectYes and clickNext. Theinstallation programwill establish an Internet connection from your server tothe Vision Solutionsweb site.

l If later versions are found, theywill be listed. Highlight the version youwant and either download that version and install it automatically ordownload that version and exit the installation. (If you exit theinstallation, you can run the updated installation later directly from thelocation where you saved it.)

l If no later versions are found, continue with the current installation.

43

l If an Internet connection cannot be established, continue with thecurrent installation or install a previously downloaded version.

7. If you are upgrading, review the upgrade note.l Any jobs that were created in legacyDouble-Take consoles, includingReplication Console, Full Server Failover Manager, ApplicationManager,Double-TakeMove Console, or DTCL, will no longer function once theupgrade is complete.

l Jobs that were created in the version 5.2 Double-Take Consolemust firstbe upgraded to version 5.3, and then they can be upgraded to version 6.0.You can also delete any jobs created in the version 5.2 Double-TakeConsole, upgrade directly to version 6.0, and then re-create the jobs.

l Any jobs created in the version 5.3 Double-Take Console will be upgradedand will continue to function normally.

l If you are protecting Hyper-V virtual machines at the host-level using acluster configuration, you cannot upgrade. Youmust delete the existing job,upgrade all of your nodes, and then re-create the job.

8. ClickNext to continue.9. If you are upgrading fromDouble-Take RecoverNow with TimeData, select if you

want to uninstall the TimeData components. You can also removeOntrackPowerControls if you have that installed. The uninstall may be time consumingwhile it removes the associated SQL instance and deletes the continuous dataprotection storage bins. Additionally, the TimeData uninstall may require a reboot.If you choose not to uninstall TimeData or Ontrack PowerControls, Double-TakeRecoverNow will still be uninstalled, and these programswill no longer functionafter the upgrade. If you do not remove the products, you will have tomanuallyremove them.

10. Review and accept the Vision Solutions license agreement to continue with theinstallation program. ClickNext to continue.

11. Review the activation notice. Most Double-Take version 6.0 and later licensesrequire activation after installation for full product functionality. Failure to activatelicenses that require it will cause your Double-Take jobs to fail. See Licensemanagement and activation on page 61 for more details.

12. ClickOK to continue.13. Select the type of installation you would like to perform on thismachine.

l Client and Server Components—This option installs both the client andserver components. The server components are required for systems thatwill function as a source or target. The server requires an activation code forthe service to run. The client does not require an activation code, but it isrequired to administer this and other Double-Take servers throughout theorganization.

l Client Components Only—This option installs only the clientcomponents. The client components do not require an activation code, butare required to administer Double-Take servers throughout theorganization.

l Server Components Only—This option installs only the servercomponents. The server components are required for systems that will

44

function as a source or target. The server requires an activation code for theservice to run.

If you are installing on Server Core, you will only be able to select theServer Components Only installation. You will not be able to run theclient components from the Server Coremachine. The client will have tobe run from another machine.

14. If desired, specify where the Double-Take files will be installed by clickingChange, specifying a location, and then clickingOK.

15. ClickNext to continue.

If you selected a client only installation, continue with step 15.

16. You will be prompted to enter your activation code information. YourActivationCode is a 24-character, alpha-numeric activation code which applies theappropriate license to your installation. Enter your code and clickAdd.

If you are installing Double-Take for the first time, you will not be requiredto add an activation code, however the product will not work without one. Ifyou are upgrading an existing version, youmust have an activation code tocontinue the installation.

17. ClickNext to continue.18. Double-Take uses systemmemory for Double-Take processing. Themaximum

amount is dependent on the server hardware and operating system. Specify themaximumamount of systemmemory that Double-Take can use and clickNext tocontinue.

19. When the allocated Double-Take systemmemory is exhausted, Double-Take willqueue to disk. If you want to disable disk queuing, deselectEnable disk queue.Ideally, you should use disk queuing. Specify theQueue folder, which is thelocation of the disk queue. By default, the size of the disk queue is set toUnlimiteddisk queue, which will allow the queue usage to automatically expand wheneverthe available disk space expands. If desired, you can select Limit disk space forqueue and specify a fixed disk space amount. You can also specify theMinimumfree disk space, which is theminimumamount of disk space in the specifiedQueue folder that must be available at all times. This amount should be less thanthe amount of physical disk spaceminus the disk size specified for Limit diskspace for queue. (SeeDouble-Take queue on page 94 for additional guidelineson selecting appropriate queue settings.) ClickNext to continue.

20. The Double-Take security information screen appears next. Review thisinformation and clickNext to continue with the installation.

45

21. If you are satisfied with the selections you havemade and are ready to begincopying the Double-Take files, click Install.

22. During the installation, youmay be prompted to add an exception to theWindowsFirewall for Double-Take. ClickOK to add the port exceptions. If youCancel theport modification, you will have tomanuallymodify your firewall settings forDouble-Take processing. SeeCore Double-Take requirements on page 28.

23. After the files have completed copying, clickFinish to exit the installation program.

46

Installing Double-Take Availability on a Windows server usingthe command line utility

TheDouble-Take installation program can accept command-line parameters whichallow you to automate the installation or upgrade process by running an unattended, orsilent, installation. The automatic process allows you to pass parameters through to theinstallation program instead of entering informationmanually during the installation orupgrade.

If you are upgrading fromDouble-Take RecoverNow, you shouldmanuallyremove it and any TimeData andOnTrack PowerControls components beforeupgrading. The uninstall may be time consuming while it removes the associatedSQL instance and deletes the continuous data protection storage bins.Additionally, the TimeData uninstall may require a reboot. Make sure that yourecall and restore anyDouble-Take archived or deduplicated files before youuninstall Double-Take RecoverNow. See the support site for completeinstructions on themanual removal process.

Since the automated process does not prompt for settings, the settings aremanuallydefined in a configuration file called DTSetup.ini. By default, DTSetup.ini contains twosections. The second section can be duplicated asmany times as necessary. The firstsection, [Config], applies to any server not defined in the second (or duplicate of second)sections. The second (or duplicate of second) section, [MachineName], allows you tospecify unique settings for individual servers. You have tomodify the heading name(case-sensitive) to identify the server.

Review the following table to understand the different parameters available inDTSetup.ini.

DTSetupType

l DTNT—Both the Double-Take server and client components will beinstalled.

l DTCO—Only the Double-Take client components will be installed.l DTSO—Only the Double-Take server components will be installed.

If you are installing on Server Core 2008 R2 or WindowsHyper-VServer (standalone), the setup type will be server components onlyregardless of your setting.

DTActivationCode

A 24 character, alpha-numeric activation code which applies theappropriate license to the server. Multiple activation codes can beseparated by a semi-colon.

47

http://support.doubletake.com/


DoubleTakeFolder

Any valid path specifying the location of the Double-Take files

QMemoryBufferMax

Any integer representing the amount of systemmemory, in MB, thatDouble-Take can use

DiskQueueFolder

Any valid path to the location of the disk-based queue

DiskQueueMaxSize

Any integer representing the amount of disk space, in MB, to use fordisk-based queuing or the keywordUNLIMITED which will allow thequeue usage to automatically expand whenever the available diskspace expands

DiskFreeSpaceMin

Any integer representing the amount of disk space, in MB, that mustremain free at all times

DTServiceStartup

l Y or 1—Start the Double-Take service automaticallyl N or 0—Do not start the Double-Take service automatically

This parameter is not applied if yourDTSetupType is DTCO.

Port

Any integer between 1024 and 65535 that identifies the primary portused for Double-Take communications

Set_FWPort

l Y or 1—Set the Double-TakeWindows firewall port exclusionsl N or 0—Do not set the Double-TakeWindows firewall portexclusions

Youmust haveMicrosoft .NET installed on the server before starting theautomatic installation.

If you are usingWindows 2008, but you are not using the built-in administratoraccount, Windows 2008 User AccessControl will prompt you to confirm youwant to install Double-Take. To work around this issue, use the built-inadministrator account when you are installing to each server. Youmay alsodisable User AccessControl if that is acceptable for your environment.

48

Installing or upgrading automatically to a local machine1. Create a temporary installation directory on the server. For example, create

c:\temp_install.2. Use the following steps if you downloaded your software from the web.

a. Unzip the .exe file that you downloaded to another temporary directory.b. Locate the subdirectory under \setup\dt that is appropriate for your

architecture, either i386 or x64.c. Copy the files from the \setup\dt\i386 or \setup\dt\x64 directory to your

temporary installation directory.3. Use the following steps if you have a CD.

a. Locate the subdirectory under \setup\dt that is appropriate for yourarchitecture, either i386 or x64.

b. Copy the files from the \setup\dt\i386 or \setup\dt\x64 directory to yourtemporary installation directory.

4. Remove the read-only attributes from the files in the temporary installationdirectory.

5. Make a backup copy of the default DTSetup.ini file in the temporary installationdirectory.

6. Edit DTSetup.ini as needed using the values described in the previous table.7. Run the following case-sensitive command from the temporary installation

directory.

setup /s /v"DTSETUPINI=\"c:\temp_install\DTSetup.ini\" /qn"

The commandmust be run from the temporary installation directory aswell as specifying the temporary installation directory for the .ini file.

Spacing is critical with this command. A space should precede /s, /v, and/qn but should not appear anywhere else for the command to workcorrectly.

49

Installing or upgrading automatically to a remote machine1. Create a temporary installation directory on the primary site server. For example,

create z:\temp_install.2. Share the temporary installation directory.3. Use the following steps if you downloaded your software from the web.

a. Unzip the .exe file that you downloaded to another temporary directory.b. Locate the subdirectory under \setup\dt that is appropriate for your

architecture, either i386 or x64.c. Copy the files from the \setup\dt\i386 or \setup\dt\x64 directory to your

shared temporary installation directory.4. Use the following steps if you have a CD.

a. Locate the subdirectory under \setup\dt that is appropriate for yourarchitecture, either i386 or x64.

b. Copy the files from the \setup\dt\i386 or \setup\dt\x64 directory to yourshared temporary installation directory.

5. Remove the read-only attributes from the files in the shared temporary installationdirectory.

6. Make a backup copy of the default DTSetup.ini file in the shared temporaryinstallation directory.

7. Edit DTSetup.ini as needed using the values described in the previous table.8. From each server where you want to install Double-Take, map a drive to the

shared temporary installation directory. For example, youmight map your m: driveto the share.

9. Run the following case-sensitive command from themapped drive.

setup /s /v"DTSETUPINI=\"m:\DTSetup.ini\" /qn"

The commandmust be run from the shared drive aswell as specifying thatshared drive for the .ini file.

Spacing is critical with this command. A space should precede /s, /v, and/qn but should not appear anywhere else for the command to workcorrectly.

C:\>net use m: \\server_name\shareThe command completed successfullyC:\>M:M:\>setup /s /v"DTSETUPINI=\"m:\DTSetup.ini\" /qn"

50

Installing Double-Take Availability on a Linux server using the.rpm file

Use these instructions if you are installing or upgrading Double-Take Availability on aLinux server.

You will need lsb, /usr/sbin/dmidecode, and /user/bin/ on your Linux serverbefore you can install Double-Take Availability.

1. Determine the installation package that is appropriate for your operating system.There are separate .rpm installation packages for 32-bit and 64-bit architectures.Make sure you are installing the correct .rpm file. If you are uncertain about thearchitecture of your machine, you can use the uname -m command to determine it.Additionally, the version_numbers in the installation file namewill vary and willcorrespond to the version of Double-Take Availability you are installing.

l 32-bit architecture—DoubleTake-version_numbers.i386.rpml 64-bit architecture—DoubleTake-version_numbers.x86_64.rpm

For example, if you are installing version 6.0.0.0.2200, the installation files wouldbe DoubleTake-6.0.0.0-2200.i386.rpm or DoubleTake-6.0.0.0-2200.x86_64.rpm.

2. If you are upgrading an existing Double-Take Availability server, you shouldcomplete the following steps before upgrading.

l Shutdown the protected application(s)l Stop the Double-Take daemonl Detach DTLOOP, if it is being used

3. Once you have determined the appropriate installation package to use, you caninstall the software from the user interface or from the command line.

l UI installation—Double-click the .rpm file from the UI and confirm theinstallation or upgrade.

l Command line installation—Use the following steps to install from acommand line.

a. Make sure you are a root/uid 0 user.b. Go to a shell prompt by launching a terminal application from your UI

or logging in via the Linux virtual console.c. If you are installing from aCD, mount the file ISO9660 or UDF file

system.d. To run the installation use rpm -i with the installation file name to

install the software or rpm -U with the installation file name toupgrade the software. For example, if you were installing on a 32-bitoperating system, you would use the command rpm -i DoubleTake-6.0.0.0-2200.i386.rpm.

A successful installation returns you to the shell prompt.

51

4. After the installation on the Linux server is complete, you will need to license yourserver using the following instructions.

a. Run the DTSetup command from the shell prompt to start DTSetup. Thecommand is case-sensitive.

Do not run DTSetup using the sudo command. Use a real root shellto launch DTSetup instead, either by logging in as root on theconsole or by using the login session of a non-privileged user to runsu - to start a root shell.

b. If prompted, review the Vision Solutions license agreement and accept theterms of agreement by typing yes.

c. When the DTSetupmenu appears, enter the number of themenu optionyou want to access. In this case, selectSetup tasks, which will allow you toactivate your server.

d. SelectSet Activation Code Menu.e. SelectSet Activation Code in /etc/DT/DT.conf.f. Enter your activation code and press Enter. The activation code will

automatically be inserted into the configuration file.g. Press Enter to return to themenu.h. PressQasmany times as needed to return back to themainmenu and then

exit DTSetup.

52

Installing the Double-Take Virtual Recovery ApplianceIf you will be creating full server to ESX appliance jobs, you will need to install theDouble-Take Virtual Recovery Appliance, which is anOVF (Open Virtualization Format)virtual machine. Youmust install this appliance before you can push the Double-Takeinstallation out to your Linux source servers and before you can create your full server toESX appliance job.

Use the following instructions to install the Double-Take Virtual Recovery Appliance.

1. Access the Double-Take Autorun program using the appropriate instructions,depending on your media source.

l Physical media—If auto-run is enabled, the installation programwill startautomatically. Tomanually start the program, selectStart,Run and specify<drive>:\autorun.exe.

l Web download—Launch the .exe file that you downloaded from the web.2. The Autorun allows you to install software and view documentation and online

resources. Select theGet the Linux Virtual Recovery Appliance link, and anExplorer window will be opened to the Double-Take .ova file. For example, forversion 6.0, your file namemight be dtvra_6.0.0.1195.0.ova. If necessary, copythis file to a location that is accessible from your vSphere client.

3. From your vSphere client, select the root of your tree, select File,DeployOVF Template, and specify the dtvra_<version_number>.ova file. ClickNext tocontinue.

4. Review theOVF template details and clickNext to continue.5. Review the Vision Solutions license agreement. Youmust accept the license

agreement by clickingAccept. ClickNext to continue.6. Specify the name and location where you want to install the appliance. This should

be the same datacenter where your target ESX host is located. ClickNext tocontinue.

7. Select the ESX host where you want to install the appliance. This is your targetESX host. ClickNext to continue.

8. If desired, select the resource pool where you want to install the appliance. Youmay not have any resource pools in your environment. ClickNext to continue.

9. Select the disk where you want to store the appliance files. Make sure the disk hasat least 2 GB of disk space available. ClickNext to continue.

10. Select the type of disk to create, and clickNext to continue.l Flat Disk—This disk type allocates the full amount of the disk spaceimmediately, but does not initialize the disk space to zero until it is needed.This option is only available for ESX version 5.

l Thick Provision—This disk type allocates the full amount of the disk spaceimmediately, initializing all of the allocated disk space to zero.

l Thin Provision—This disk type does not allocate the disk space until it isneeded.

11. If your selected ESX host hasmultiple networks, map the network on theappliance to a network on your ESX host, and clickNext to continue.

53

12. Assign the networking properties, including the IP address and subnet mask,gateway, and DNS server. ClickNext to continue.

13. Review theDeployment settings. If you want to make any changes, clickBack.If not, enable thePower on after deployment option. This option is onlyavailable for ESX version 5, and clickFinish.

14. After the appliance deployment is complete, clickClose.15. After the appliance has powered on, open the console, enter a new password,

and confirm the password by entering it again.16. You will need to add your Double-Take license to your appliance next.

a. Install the Double-Take Console on aWindowsmachine, if you haven'talready. See Installing Double-Take Availability on aWindows server usingthe installation wizard on page 43 , making sure you select the client-onlyinstallation.

b. After the installation is complete, open the console by selectingStart,Programs,Double-Take,Double-Take Console.

c. ClickManage Servers in the toolbar.d. ClickAdd Servers in the toolbar, and specify the following fields on the

Manual Entry tab of theAdd Servers page.l Server—Specify the IP address of your appliance.l User name—Specify the root user.l Password—Specify the password associated with the root user.

e. ClickAdd to add the appliance to the server list and then clickOK.f. Highlight your appliance on theManage Servers page and clickView

Server Details from the toolbar. Under Tasks, selectEdit serverproperties.

g. In the box underAdd activation codes and activation keys, enter youractivation code, clickAdd. Some activation codeswill have a 14-day graceperiod to activate the license. If your license requires activation as noted ontheEdit Server Properties page, see Licensemanagement and activationon page 61 for details on license activation.

h. ClickOK to return to theManage Servers page.

Once your appliance is licensed, you are ready to create a full server to ESX appliancejob.

Once the appliance has been installed and configured, you should not need toaccess or use it. However, if you need to change any network settings, you canmodify them using theConfigure Networkmenu on the appliance or by usingthe web interface by going to https:\\ip_address:5480, where ip_address is thecurrent IP address of the appliance. After the network settings have beenupdated, youmust reboot the appliance for the changes to take effect.

The virtual recovery appliancemenu runs as root, somake sure you takeadvantage of VMware security to restrict access to the appliance. See yourVMware documentation for details on limiting access to the appliance's console.

54

Installing Double-Take Availability on a Windows or Linuxserver using the Double-Take Console

You can use the Double-Take Console to install or upgrade Double-Take Availability onyour other servers. The installation is a full, client and server installation onWindowsservers. The installation is a full server installation on Linux servers.

If you are upgrading fromDouble-Take RecoverNow, you shouldmanuallyremove it and any TimeData andOnTrack PowerControls components beforeupgrading. The uninstall may be time consuming while it removes the associatedSQL instance and deletes the continuous data protection storage bins.Additionally, the TimeData uninstall may require a reboot. Make sure that yourecall and restore anyDouble-Take archived or deduplicated files before youuninstall Double-Take RecoverNow. If you choose not to uninstall TimeData orOntrack PowerControls, Double-Take RecoverNow will still be uninstalled, andthese programswill no longer function after the upgrade. If you do not removethe products, you will have tomanually remove them.

The push installation processwill not work on cluster nodes.

If you are going to be creating a V to Hyper-V or V to ESX job (seeSelecting aprotection type on page 174 for details on which job to create), the job creationprocess can automatically push the Double-Take installation out to the servers, ifyou have the Double-Take Availability Virtual Guest Edition license. After the jobis created, you will have 14 days to activate the licenses. (SeeActivating a singleDouble-Take server on page 65 or Activatingmultiple Double-Take servers onpage 67. ) If you do not have a Double-Take Availability Virtual Guest Editionlicense, you will need to perform the installation outside of the job creationprocess.

For Linux servers, the push installation process uses a combination of SSH(secure shell) and SCP (secure copy) to copy the installation binary files andexecute them. SCP is not installed by default on certain configurations of version6.x of Red Hat Enterprise Linux, Oracle Enterprise Linux, and CentOS. You willneed to install it manually to use the push installation process. See your Linuxdocumentation for installation details.

1. Add the servers where you want to install Double-Take to your console session.SeeAdding servers on page 80.

2. From theManage Servers page, highlight all of the servers where you want toinstall Double-Take, and select Install from the toolbar.

3. Each server needs an activation code for the installation. If you are upgrading andyour server already has an activation code that is valid for the current version, youcan either skip this step to use the existing activation code or you can complete thisstep to replace the existing activation code.

a. If you have a single activation code that can be used onmultiple servers,such as a site license or an evaluation code, highlight all of the servers

55

where you want to apply the same activation code and clickSet Activationcodes. If you have unique activation codes for each of your servers,highlight just one server and clickSet Activation codes.

b. Type in your activation code or clickChoose from inventory to open theActivation Codes dialog boxwhere you can select the activation code youwant to apply. For more information on the license inventory, seeManagingthe Double-Take license inventory on page 62.

c. ClickOK to configure the installation or upgrade for the selected activationcode.

d. Repeat steps a-c for any additional servers that are using unique activationcodes.

If you are pushing out a new activation code and it is a code thatrequires activation, you will have 14 days to activate the code. SeeLicensemanagement and activation on page 61 for more details onlicense activation.

4. TheDefault Installation Options section contains the default settings from theconsole'sOptions page. These settingswill be applied to all of the servers you areinstalling to or upgrading. If desired, modify any of the installation options. SeeConsole options on page 73.

Options youmodify when using the push installation will be replaced bythe default values from theOptions page each time you use the pushinstallation.

TheDefault Installation Options settingswill vary depending on howyou entered your source in your console session. If you are using aproxied source server, you will have fewer available options, and some ofthe optionsmay be disregarded for Linux servers. SeeAdding servers onpage 80 for more details on proxied source servers.

56

l Location of 32-bit installation package—Specify the location of thesetup file (on the local machine) that will be used to install on 32-bit servers.By default, this is in the \i386 subdirectory where you installed Double-Take.

l Location of 64-bit installation package—Specify the location of thesetup file (on the local machine) that will be used to install on 64-bit servers.By default, this is in the \x64 subdirectory where you installed Double-Take.

l Location of .NET 3.5 SP1 installation package—If your servers arerunningWindows 2008 or earlier and do not haveMicrosoft .NET version3.5.1, specify the location of the setup file (on the local machine) that will beused to install it. The setup file is available on the Double-Take CD in the\NetFx\v3.5SP1\Full directory or from theMicrosoft web site.

l Temporary folder for installation package—Specify a temporarylocation (on the server where you are installing Double-Take) where theinstallation files will be copied and run. You need approximately 130MB ofspace in the specified location.

l Installation folder—Specify the location where you want to install Double-Take on each server.

l Queue folder—Specify the location where you want to store the Double-Take disk queue on each server.

l Amount of system memory to use—Specify themaximumamount ofmemory, in MB, that can be used for Double-Take processing. Forcomplete details onmemory usage, seeDouble-Take queue on page 94.

57

http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe



l Minimum free disk space—This is theminimumamount of disk space inthe specifiedQueue folder that must be available at all times. This amountshould be less than the amount of physical disk spaceminus the disk sizespecified for Limit disk space for queue.

l Do not use disk queue—This option will disable disk queuing.Whensystemmemory has been exhausted, Double-Take will automatically beginthe auto-disconnect process.

l Unlimited disk queue—Double-Take will use an unlimited amount of diskspace in the specifiedQueue folder for disk queuing, which will allow thequeue usage to automatically expand whenever the available disk spaceexpands.When the available disk space has been used, Double-Take willautomatically begin the auto-disconnect process.

l Limit disk space for queue—This option will allow you to specify a fixedamount of disk space, in MB, in the specifiedQueue folder that can beused for Double-Take disk queuing.When the disk space limit is reached,Double-Take will automatically begin the auto-disconnect process.

5. Specify when you want to perform the installations under theSchedule section.

The Installation Schedule section will not be available if you are using aproxied source server. SeeAdding servers on page 80 for more details onproxied source servers.

l Install now—Select this option to complete the installation immediately.l Install later—Select this option and specify a date and time to complete theinstallation then.

l Reboot automatically if needed—If selected, the server willautomatically reboot after the installation, if a reboot is required.

58

6. After you have configured your installation options, click Install.

During an upgrade, any existing jobs on theManage Jobs pagemay disappearand then reappear. This is expected while certain Double-Take files areupdated.

If there are errors with the push installation before the installation is executed onthe server, check the console log on themachine where you are pushing theinstallation from. Once the installation execution has started, then check theinstallation log on the server where you are installing.

Proxied servers will install Double-Take using the installation packages from thevirtual recovery appliance rather than the installation packages from the Double-Take Console.

59

Installing the Windows iSCSI InitiatorTo support the full server to ESX appliance job type, theWindows iSCSI Initiator isplaced into a folder onWindows 2003 servers during Double-TakeWindowsinstallations. You will have to install it manually before creating a full server to ESXappliance job. If you are usingWindows 2008, the iSCSI Initiator is already installed, butyou will have to enable it through Administrative Tools, if it is not already enabled. (Bydefault, it is not enabled.)

1. Locate the iSCSI Initiator directory in your Double-Take installation location. Bydefault, this is \ProgramFiles\Vision Solutions\Double-Take.

2. Select either the x64 or x86 sub-directory depending on your server architecture.3. Launch the executable in your selected sub-directory.4. When theMicrosoft iSCSI Initiator installation begins, clickNext.5. Keep the default installation options for Initiator Service andSoftware Initiator,

and clickNext to continue.6. Accept the license agreement by clicking I Agree, and clickNext to continue.7. When the installation is complete, clickFinish.

60

License management and activationYou canmanage your Double-Take licenses through the license inventory feature in theDouble-Take Console. Ideally, you should select onemachine in your organizationwhere you want to maintain the license inventory because the license inventory does notcommunicate betweenmachines.

From the license inventory, you can add and remove Double-Take licensesmanually.You can import and export a Double-Take license file to handle groups of licenses. Youcan also activate and deactivate the licenses in your inventory. SeeManaging theDouble-Take license inventory on page 62 for details on using the license inventory.

For those Double-Take licenses that require activation, you have 14 days to activate thelicense. You can use the license inventory to activatemultiple licenses at one time, or youcan activate your licenses one at a time on a per server basis.

l Activating a single Double-Take server on page 65—Youwill need to haveDouble-Take installed on a single server, then you can activate the license on thatserver using the Double-Take Console. You can repeat this process for otherservers individually.

l Activatingmultiple Double-Take servers on page 67—Youwill need to haveDouble-Take installed onmultiple servers, then you can activate the licenses onthose servers all at once.

Additionally, you can deactivate a Double-Take license if you uninstall Double-Takeusing the Double-Take Console. The license that was in use will be deactivated, and thatlicense can be used on a new server. If you do not deactivate your license, you will haveto complete a host transfer which will allow you to activate the license for use on anotherserver.You can only complete two host transfers, and then the license becomes invalid.You can complete an unlimited number of deactivations. SeeDeactivating Double-Takelicenses on page 69.

61

Managing the Double-Take license inventoryYou canmanage your Double-Take licenses through the license inventory feature in theDouble-Take Console. Ideally, you should select onemachine in your organizationwhere you want to maintain the license inventory because the license inventory does notcommunicate betweenmachines.

By default, the license inventory feature is enabled. You can, and should, disable it onmachines that are not maintaining your license inventory. To disable the licenseinventory, selectOptions from the console toolbar, deselectEnable license inventory,and clickSave.

Tomanage your license inventory, selectGo,Manage License Inventory.

The license inventory featuremay not appear in your console if your serviceprovider has restricted access to it.

You will see the following fields on theManage License Inventory page.

Warning or error icon

Warnings indicate the license has not been activated, or it is temporaryand will expire. Errors indicate the license has expired.

Serial Number

The serial number associated with the license

Product

TheDouble-Take product associated with the license

License Type

A short description of the type of license, including any expiration date

Version

The product version number associated with the license

Server

The name of the server the license has been applied to, if any. If thesame activation code is used onmultiple servers, for example withevaluation licenses, you will seemultiple entries in the license inventoryfor each server that is using that activation code.

62

Use the following toolbar controls to manage your licenses.

Import Licenses

Imports all of the activation codes from a license inventory file into thelicense inventory. This is a file youmay have received fromVisionSolutions, or it may be from another Double-Take Console. Dependingon the information contained in the file, youmay be prompted to activatesome of the servers in your license inventory.

Export Licenses

Exports all of the activation codes in the license inventory to a licenseinventory file. This is a file that youmaywant to send to Vision Solutionswhen upgrading codes for a newer release or when activating ordeactivating licenses. In this case go to https://activate.doubletake.com.Youmay also need to upload a file tohttps://activate.doubletake.com/hosttransferfile.aspx to complete host-transfers. Youmay also want this file so you can store and back up youractivation codes.

Add Licenses

Allows you tomanually enter your activation codes. Enter the activationcodes in the Add Licenses dialog box in the space provided, separatingmultiple codes by a comma or by putting each code on a separate line.Once your activation codes are in your license inventory, you can applythem to a server in several ways. SeeActivating a single Double-Takeserver on page 65 or SeeActivatingmultiple Double-Take servers onpage 67.

Remove License

Removes the selected activation code from the license inventory. Youcan only remove activation codes that are not being used by any serverin the console.

Reclaim License

Reclaims the selected activation code back into the license inventory.Youmaywant to reclaim a license if you have removed it from a serveror if the server it is assigned to is no longer managed by the console.You can also reclaim a license on any server that is still managed butthe Double-Take Console cannot communicate with. If communicationbecomes successful later on, it will be reassigned to the server.

63

https://activate.doubletake.com/

https://activate.doubletake.com/hosttransferfile.aspx

Activate

Activates and deactivates the activation codes in the license inventory.For complete details on this process, seeActivatingmultiple Double-Take servers on page 67 andDeactivating Double-Take licenses onpage 69.

64

Activating a single Double-Take serverYouwill need to have Double-Take installed on a single server, then you can activate thelicense on that server using the Double-Take Console. You can repeat this process forother servers individually.

1. Open the Double-Take Console by selectingStart, Programs,Double-Take,Double-Take Console.

2. ClickManage Servers in the toolbar.3. ClickAdd Servers in theManage Servers page toolbar.4. Specify the name of your server and the credentials of the account used to install

Double-Take, and clickAdd.5. ClickOK.6. After you server has been added to theManage Servers page, clickView Server

Details in the toolbar.7. On theView Server Details page, clickEdit server properties under Tasks.8. Expand the Licensing section.

9. If your activation code needs to be activated, you will see an additionalActivation

65

section at the bottom of the Licensing section. To activate your code, use one ofthe following procedures.

l Activate online—If you have Internet access, you can activate your licenseand apply the activated license to the server in one step. SelectActivateOnline. You will not be able to activate a license that has already beenactivated but has not been deactivated. In that case, you will be prompted tocomplete a host transfer. Ideally, you should deactivate the license insteadof doing a host transfer. SeeDeactivating Double-Take licenses on page 69for more details. If youmust do a host transfer, you will have to export yourlicense inventory to a file, upload that file tohttps://activate.doubletake.com/hosttransferfile.aspx, and then import thefile you get back. SeeManaging the Double-Take license inventory on page62 for details on exporting and importing a license inventory file.

l Obtain activation key online, then activate—If you have Internetaccess, click the hyperlink in theActivation section to take you to the webso that you can submit your activation information. Complete and submit theactivation form, and you will receive an email with the activation key.Activate your server by entering the activation key in theAdd activationcodes and activations keys field and clickingAdd.

l Obtain activation key offline, then activate—If you do not have Internetaccess, go to https://activate.doubletake.com from another machine thathas Internet access. Complete and submit the activation form, and you willreceive an email with the activation key. Activate your server by entering theactivation key in theAdd activation codes and activations keys fieldand clickingAdd.

The permanent code is specific to this server. It cannot be used on any otherserver. If the activation code and server do not match, Double-Take will not run.

If your activation codes needs to be activated, you will have 14 days to do so.

66



Activating multiple Double-Take serversYouwill need to have Double-Take installed onmultiple servers, then you can activatethe licenses on those servers all at once.

1. On theManage Servers page, verify that all of the Double-Take servers that youwant to activate have been added to your Double-Take Console. SeeAddingservers on page 80.

2. SelectGo,Manage License Inventory.3. ClickActivate in the toolbar.

l Activate online—Select this option on an Internet connectedmachine tocontact the Vision Solutions activation web site to automatically activate allof the licenses in your license inventory. This processwill also deactivateany licenses that have been uninstalled through the Double-Take Console.You will not be able to activate a license that has already been activated buthas not been deactivated. In that case, you will be prompted to complete ahost transfer. Ideally, you should deactivate the license instead of doing ahost transfer. SeeDeactivating Double-Take licenses on page 69 for moredetails. If youmust do a host transfer, you will have to export your licenseinventory to a file, upload that file tohttps://activate.doubletake.com/hosttransferfile.aspx, and then import thefile you get back. SeeManaging the Double-Take license inventory on page62 for details on exporting and importing a license inventory file.

l Enter activation keys—Select this option on a non-Internet connectedmachine tomanually enter activation keys. You can obtain these keys fromhttps://activate.doubletake.com by entering the server information for each

67



server manually or by uploading an export file of your license inventory. SeeActivating a single Double-Take server on page 65 for details on gatheringthe server information orManaging the Double-Take license inventory onpage 62 for details on creating an export file.

l Activate using only my current local inventory—Select this option toactivate all of the licenses in your inventory based on the inventory's currentlocal settings. This processwill also deactivate any licenses that have beenuninstalled through the Double-Take Console. For example, if a server wasoffline when you performed activate online, you can perform the activationprocess again when the server is available. Youmay also need to performthis option if you selected not to activate the servers when you imported alicense inventory file.

4. ClickOK to begin the activation process.

After your servers have been activated, you will have permanent codes that are specificto each server. They cannot be used on any other server. If the activated code andserver do not match, Double-Take will not run.

If your activation codes needs to be activated, you will have 14 days to do so.

68

Deactivating Double-Take licensesOnce you have activated a license, it is a permanent code specific to the assigned server.It cannot be used on any other server. If the activation code and server do not match,Double-Take will not run. You can deactivate a Double-Take license if you uninstallDouble-Take using the Double-Take Console. The license that was in use will bedeactivated, and that license can be used on a new server. If you do not deactivate yourlicense, you will have to complete a host transfer which will allow you to activate thelicense for use on another server.You can only complete two host transfers, and then thelicense becomes invalid. You can complete an unlimited number of deactivations.

The key to the deactivation process is performing the uninstall through the Double-TakeConsole. If you perform the uninstall through theWindows add remove programs applet,the license will not be deactivated.

If you failed over a full server job but did not enable reverse protection when youconfigured the job, you will lose the activated target license. To workaround thissituation, uninstall Double-Take on the failed over source (currently on the targethardware) using the Double-Take Console, and the uninstall processwilldeactivate both the source and target licenses. You can then reinstall Double-Take on the failed over source (currently on the target hardware) and reactivatethe source's original license.

1. From theManage Jobs page, confirm that there are no jobs currently using theserver that you want to uninstall from. If there are, stop and delete those jobs.

2. From theManage Servers page, highlight the server you want to uninstall fromand clickUninstall from the toolbar.

3. When the uninstallation is complete, selectGo,Manage License Inventory.4. ClickActivate in the toolbar.5. SelectActivate online. This option will contact the Vision Solutions activation

web site to automatically deactivate the licenses that have been uninstalledthrough the Double-Take Console.

6. ClickOK to begin the process.

After your licenses have been deactivated, you can reuse them on another Double-Takeserver.

If your server is not connected to the Internet, you will have to export your licenseinventory to a file and then upload that file to https://activate.doubletake.com tocomplete the deactivation process. SeeManaging the Double-Take licenseinventory on page 62 for details on export the license inventory.

69


Chapter 4 Double-Take ConsoleAfter you have installed the console, you can launch it by selectingStart, Programs,Double-Take,Double-Take Console.

The Double-Take Console is used to protect andmonitor your servers and jobs. Eachtime you open the Double-Take Console, you start at theHome page. This pageprovides a high-level overview of the status of your jobs.

The appearance of theHome page is the same for all users. However, other consolepagesmay have variances in the appearance depending on the Double-Take productsthat you have installed, the Double-Take activation codes on your servers, and the typeof job you are working with.

l Headlines—The top section gives a quick overview of any jobs that requireattention aswell as providing quick access buttons.

l These jobs require attention—Any jobs that require attention (those inan error state) are listed. You will see the source and target server nameslisted, as well as a short description of the issue that requires your attention.If the list is blank, there are no jobs that require immediate attention.

l View—If you highlight a job in the list and clickView, you will go to theViewJob Details page where you can seemore detailed information about thejob.

70

l Tools—Select this drop-down list to launch other Vision Solutionsconsoles.

l Servers Summary—Themiddle section summarizes the servers in your console.l Total number of servers—This field displays the number of servers thatyou have been added to the console.

l View all servers—Select this link to go to theManage Servers pagewhere you can view, edit, add, remove, or manage the servers in yourconsole. SeeManaging servers on page 76.

l Jobs Summary—The bottom section summarizes the jobs in your console.l Total number of jobs—This field displays the number of jobs running onthe servers in your console.

l View jobs with errors—Select this link to go to theManage Jobs page,where the Filter: Jobs with errorswill automatically be applied.

l View jobs with warnings—Select this link to go to theManage Jobspage, where the Filter: Jobs with warningswill automatically be applied.

l View all jobs—Select this link to go to theManage Jobs page and view alljobs.

At the bottom of the Double-Take Console, you will see a status bar. At the right side,you will find links for Jobs with warnings and Jobs with errors. This lets you seequickly, nomatter which page of the console you are on, if you have any jobs that needyour attention. Select this link to go to theManage Jobs page, where the appropriateFilter: Jobs with warnings or Filter: Jobs with errorswill automatically be applied.

71

Double-Take Console requirementsYoumust meet the following requirements for the Double-Take Console.

l Operating system—TheDouble-Take Console can be run from aWindowssource or target. It can also be run from a 32-bit or 64-bit physical or virtualmachine runningWindows 7,WindowsVista, or WindowsXP Service Pack 2 orlater.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5 ServicePack 1 is required. This version is not included in the .NET version 4.0 release.Therefore, even if you have .NET version 4.0 installed, you will also need version3.5.1. You can install this version from the Double-Take CD, via a web connectionduring the Double-Take installation, or from a copy you have obtainedmanuallyfrom theMicrosoft web site.

If you are installing on Server Core 2008 R2, .NET 3.5.1 functionality isincluded with the operating system but is disabled by default. You willneed to enable it prior to installing Double-Take. See your Server Coredocumentation for the specific commands to enable the.NET functionality.

l Screen resolution—For best results, use a 1024x768 or higher screenresolution.

72




Console optionsThere are several options that you can set that are specific to the Double-Take Console.To access these console options, selectOptions from the toolbar.

l Monitoring interval—Specifies how often, in seconds, the console refreshes themonitoring data. The servers will be polled at the specified interval for informationto refresh the console.

l Default port for XML web services protocol—Specifies the port that theconsole will use when sending and receiving data to Double-Take servers. Bydefault, the port is 6325. Changes to the console port will not take effect until theconsole is restarted.

l Default port for legacy protocol—If you are using an older Double-Takeversion, you will need to use the legacy protocol port. This applies to Double-Takeversions 5.1 or earlier.

l Export Diagnostic Data—This button creates a raw data file that can be usedfor debugging errors in the Double-Take Console. Use this button as directed bytechnical support.

l View Log File—This button opens the Double-Take Console log file. Use thisbutton as directed by technical support.

l View Data File—This button opens the Double-Take Console data file. Use thisbutton as directed by technical support.

l Automatically check for updates—Bydefault, each time the console is started,it will automatically check the Vision Solutionsweb site to see if there is updatedconsole software available. If there is updated console software available, anAutomatic Updates section will appear on theHome page. ClickGet the latestupdate to download and install the updated console software.

If you want to disable the automatic check for updates, clickChange automaticupdates or selectOptions from the toolbar. On theOptions page, deselectAutomatically check for updates to disable the automatic check.

You can alsomanually check for updates by selectingHelp,Check for Updates.

l Update available—If there is an update available, clickGet Update. Thedialog boxwill close and your web browser will open to the Vision Solutionsweb site where you can download and install the update.

l No update available—If you are using themost recent console software,that will be indicated. ClickClose.

l No connection available—If the console cannot contact the updateserver of if there is an error, the console will report that information. Theconsole log contains amore detailed explanation of the error. ClickCheckusing Browser if you want to open your browser to check for consolesoftware updates. You will need to use your browser if your Internet accessis through a proxy server.

l Enable license inventory—This option allows you to use this console tomanagethe Double-Take licenses assigned to your organization.When this option is

73

enabled, theManage License Inventory page is also enabled. SeeManagingthe Double-Take license inventory on page 62.

The license inventory featuremay not appear in your console if yourservice provider has restricted access to it.

l Default Installation Options—All of the fields under theDefault InstallationOptions section are used by the push installation on the Install page. SeeInstalling Double-Take Availability on aWindows or Linux server using theDouble-Take Console on page 55. The values specified here will be the defaultoptions used for the push installation. Options youmodify when using the pushinstallation will be replaced by these default values each time you use the pushinstallation.

l Location of 32-bit installation package—Specify the location of thesetup file (on the local machine) that will be used to install on 32-bit servers.By default, this is in the \i386 subdirectory where you installed Double-Take.

l Location of 64-bit installation package—Specify the location of thesetup file (on the local machine) that will be used to install on 64-bit servers.By default, this is in the \x64 subdirectory where you installed Double-Take.

l Location of .NET 3.5 SP1 installation package—If your servers arerunningWindows 2008 or earlier and do not haveMicrosoft .NET version3.5.1, specify the location of the setup file (on the local machine) that will beused to install it. The setup file is available on the Double-Take CD in the\NetFx\v3.5SP1\Full directory or from theMicrosoft web site.

l Temporary folder for installation package—Specify a temporarylocation (on the server where you are installing Double-Take) where theinstallation files will be copied and run. You need approximately 130MB ofspace in the specified location.

l Installation folder—Specify the location where you want to install Double-Take on each server.

l Queue folder—Specify the location where you want to store the Double-Take disk queue on each server.

l Amount of system memory to use—Specify themaximumamount ofmemory, in MB, that can be used for Double-Take processing. Forcomplete details onmemory usage, seeDouble-Take queue on page 94.

l Minimum free disk space—This is theminimumamount of disk space inthe specifiedQueue folder that must be available at all times. This amountshould be less than the amount of physical disk spaceminus the disk sizespecified for Limit disk space for queue.

l Do not use disk queue—This option will disable disk queuing.Whensystemmemory has been exhausted, Double-Take will automatically beginthe auto-disconnect process.

l Unlimited disk queue—Double-Take will use an unlimited amount of diskspace in the specifiedQueue folder for disk queuing, which will allow thequeue usage to automatically expand whenever the available disk space

74




expands.When the available disk space has been used, Double-Take willautomatically begin the auto-disconnect process.

l Limit disk space for queue—This option will allow you to specify a fixedamount of disk space, in MB, in the specifiedQueue folder that can beused for Double-Take disk queuing.When the disk space limit is reached,Double-Take will automatically begin the auto-disconnect process.

75

Chapter 5Managing serversTomanage the servers in your console, selectManage Servers from the toolbar. TheManage Servers page allows you to view, edit, add, remove, or manage the servers inyour console.

You can also organize the servers that are in your console into groups, allowing you tofilter the servers you are viewing based on your organization. The servers displayed inthe right pane depend on the server group folder selected in the left pane. Every server inyour console session is displayed when theAll Servers group is selected. If you havecreated and populated server groups underMy Servers, then only the servers in theselected group will displayed in the right pane.

Right pane displayThe following table identifies the columns displayed in the right pane of theManageServers page.

Column 1 (Blank)

The first blank column indicates the status of communications betweenthe console and the server or cluster.

The console is attempting to communicate with the server or cluster.

The server or cluster is online and the console is communicatingwith it.

The server or cluster is offline, so the console cannotcommunicate with it.

The console has lost communication with the server or cluster. Ifyou have uninstalled and reinstalled Double-Take on a server, youmaysee the server twice on theManage Servers page because thereinstall assigns a new unique identifier to the server. One of theservers (the original version) will show with the red X icon. You cansafely remove that server from the console.

This icon indicates a VMware server that has been inserted into theconsole.

Column 2 (Blank)

The second blank column indicates the security level

Administrator access—This level grants full control.

Monitor only access—This level grantsmonitoring privileges only.

76

No security access—This level does not allow monitoring or control.

Server

The name or IP address of the server. If you have specified areserved IP address, it will be displayed in parenthesis.

Activity

There aremany differentActivitymessages that keep you informed ofthe server activity. Most of the activitymessages are informational anddo not require any administrator interaction. If you see error messages,check the server details. SeeViewing server details on page 84.

Version

The product version information

Product

The products licensed for the server

Activation Code

The activation codes associated with the products licensed for theserver

Main toolbarThe following options are available on themain toolbar of theManage Servers page.These toolbar options control the servers selected in the right pane. These options arealso available in a right-clickmenu. Additionally, in the right-clickmenu is aRefreshoption.

Add Servers

Adds a new server. This button leaves theManage Servers page andopens theAdd Servers page. SeeAdding servers on page 80.

View Server Details

Views detailed information about a server. This button leaves theManage Servers page and opens theView Server Details page. SeeViewing server details on page 84.

Remove Server

Removes the server from the console.

77

Provide Credentials

Changes the login credentials for a server. This button opens theProvide Credentials dialog boxwhere you can specify the newaccount information. SeeProviding server credentials on page 83. Youwill remain on theManage Servers page after updating the servercredentials.

Manage Group Assignments

Allows you to assign, move, and remove the selected server fromspecific server groups. This buttons opens theManageGroupAssignments dialog boxwhere you can assign and unassign the serverto specific server groups. The server will appear in server groupsmarked with a checkmark, and will not appear in groupswithout acheckmark. Servers assigned to a server group will automaticallyappear in parent server groups.

Install

Installs or upgradesDouble-Take on the selected server. This buttonopens the Install page where you can specify installation options. SeeInstalling Double-Take Availability on aWindows or Linux server usingthe Double-Take Console on page 55.

Uninstall

Uninstalls Double-Take on the selected server.

View Server Events

Views event messages for a server. This button leaves theManageServers page and opens theView Server Events page. SeeViewingserver events on page 166.

View Server Logs

Views the Double-Take logsmessages for a server. This button opensthe Logswindow. This separate window allows you to continueworking in the Double-Take Console while monitoring logmessages.When the Double-Take Console is closed, the Logswindow willautomatically close. SeeViewing the log files through the Double-TakeConsole on page 705.

78

Overflow Chevron

Displays any toolbar buttons that are hidden from view when thewindow size is reduced.

Left pane toolbarBetween themain toolbar and the left pane is a smaller toolbar. These toolbar optionscontrol the server groups in the left pane.

Create New Server Group

Creates a new server group below the selected group

Rename Server Group

Allows you to rename the selected server group

Delete Server Group

Deletes the selected server group. This will not delete the servers in thegroup, only the group itself.

Overflow Chevron


79

Adding serversThe first time you start the console, it is empty. In order to protect andmonitor yourservers, youmust insert your servers in the console. You can insert servers during jobcreation, or you have other threemethods for inserting servers into the console.

If you will be creating a full server to ESX appliance job (seeSelecting aprotection type on page 174 for details on selecting a job type), you should insertyour virtual recovery appliance into your console session before inserting yoursource servers.

Inserting servers manually1. SelectGet Started from the toolbar.2. SelectAdd servers and clickNext.3. On theManual Entry tab, specify the server information.

l Server—This is the name or IP address of the server to be added to theconsole.

l User name—Specify a user that is amember of theDouble-Take AdminorDouble-Take Monitors security group on the server.

l Password—Specify the password associated with theUser name youentered.

4. You can expand theMore Options section to configure the following settings.l Domain—If you are working in a domain environment, specify theDomain.l Double-Take proxy server—If you will be creating a full server to ESXappliance job, and your source is a Linux server, specify the name orIP address of your virtual recovery appliance. Your Linux source is nowconsidered a proxied server.

Youmay also want to insert your Windows source servers as proxiedservers, depending on your network configuration. If your environment isconfigured so that your Windows source servers can only communicatewith your virtual recovery appliance, but not directly with your Double-TakeConsole, then you need to insert your Windows source servers as proxiedservers. If your Double-Take Console can communicate with your Windowssource servers, you can insert the servers as proxied servers or as non-proxied servers.

l Protocol—Specify the protocol type that the console will use tocommunicate with the server.

l Automatically detect protocol—Double-Take will check theserver to determine the protocol type to use.

80

l XML web services protocol—Select this option to use XMLwebservices as your protocol. Select this option if your server is runningDouble-Take version 5.2 or later.

l Legacy protocol—Select this option to use the legacy proprietaryDouble-Take protocol. Select this option if your server is runningDouble-Take version 5.1 or earlier.

5. After you have specified the server information, clickAdd.6. Repeat steps 3 through 5 for any other servers you want to add.7. If you need to remove servers from the list of Servers to be added, highlight a

server and clickRemove. You can also remove all of themwith theRemove Allbutton.

8. When your list of Servers to be added is complete, clickOK.

Inserting servers through Active Directory discovery1. SelectGet Started from the toolbar.2. SelectAdd servers and clickNext.3. Select theAutomatic Discovery tab.4. ClickDiscover to search Active Directory for servers running Double-Take.5. If you need to remove servers from the list of Servers to be added, highlight a

server and clickRemove. You can also remove all of themwith theRemove Allbutton.

6. When your list of Servers to be added is complete, clickOK.7. Because the Active Directory discovery uses pass-through authentication, you will

need to update the credentials for each server from theManage Servers page,so that explicit credentials can be used when you go to create a job. ClickProvideCredentials and provide credentials for a user that has privileges to that serverand is amember of the Double-Take Admin security group.

Importing and exporting servers from a server and groupconfiguration fileYou can share the console server and group configuration betweenmachines that havethe Double-Take Console installed. The console server configuration includes the servergroup configuration, server name, server communications ports, and other internalprocessing information.

To export a server and group configuration file, select File, Export Servers. Specify afile name and clickSave. After the configuration file is exported, you can import it toanother console.

When you are importing a console server and group configuration file from anotherconsole, you will not lose or overwrite any servers that already exist in the console. Forexample, if you have server alpha in your console and you insert a server configurationfile that contains servers alpha and beta, only the server beta will be inserted. Existinggroup nameswill not bemerged, so youmay see duplicate server groups that you willhave tomanually update as desired.

81

To import a server and group configuration file, select File, Import Servers. Locate theconsole configuration file saved from the other machine and clickOpen.

82

Providing server credentialsTo update the security credentials used for a specific server, selectProvideCredentials from the toolbar on theManage Servers page.When prompted, specifytheUser name, Password, andDomain of the account you want to use for this server.ClickOK to save the changes.

83

Viewing server detailsHighlight a server on theManage Servers page and clickView Server Details from thetoolbar. TheView Server Details page allows you to view details about that particularserver.

Server name

The name or IP address of the server. If you have specified areserved IP address, it will be displayed in parenthesis.

Status

There aremany differentStatusmessages that keep you informed ofthe server activity. Most of the statusmessages are informational anddo not require any administrator interaction. If you see error messages,check the rest of the server details.

Activity

There aremany differentActivitymessages that keep you informed ofthe server activity. Most of the activitymessages are informational anddo not require any administrator interaction. If you see error messages,check the rest of the server details.

Connected via

The IP address and port the server is using for communcations. You willalso see the Double-Take protocol being used to communicate withserver. The protocol will be XMLweb services protocol (for serversrunning Double-Take version 5.2 or later) or Legacy protocol (forservers running version 5.1 or earlier).

Version

The product version information

Access

The security level granted to the specified user

User name

The user account used to access the server

Licensing

Licensing information for the server

l Warning or error icon—Warnings indicate the license istemporary and will expire. Errors indicate the license has expired.

l Product—The product associated with the licensel Serial Number—The serial number associated with the license

84

l Expiration Date—The date the license expires, if there is onel Activation Code—The activation code

Source jobs

A list of any jobs from this server. Double-clicking on a job in this list willautomatically open theView Job Details page.

Target jobs

A list of any jobs to this server. Double-clicking on a job in this list willautomatically open theView Job Details page.

85

Editing server propertiesHighlight a server on theManage Servers page and clickView Server Details from thetoolbar. Under Tasks, selectEdit server properties. TheEdit Server Propertiespage allows you to view and edit properties for that server. Click on a heading on theEdit Server Properties page to expand or collapse a section of properties.

l SeeGeneral server properties on page 87—These properties identify the server.l SeeServer licensing on page 88—View, add, and remove your activation codes inthis section.

l SeeServer setup properties on page 91—These properties indicate how theserver will act on startup and shutdown.

l SeeDouble-Take queue on page 94—Learn about and configure the Double-Take queues.

l SeeSource server properties on page 98—These properties are specific to thesource server role.

l See Target server properties on page 100—These properties are specific to thetarget server role.

l SeeE-mail notification configuration on page 102—Set e-mail notification If youwant to receivemessages regarding a server.

l SeeScript credentials on page 105—These credentials will be used whenexecuting custom scripts duringmirroring or failover.

l See Log file properties on page 106—These settings allow you to specify your logfile configuration.

If you are running earlier versions of Double-Take on your server (earlier thanversion 5.3), youmay not be able to edit the properties for your server. In thiscase, see the Double-Take documentation distributed with your earlier versionfor instructions for editing the server properties.

Server properties cannot be edited on a cluster.

If you are editing server properties for a proxied source server or a Double-TakeVirtual Recovery Appliance, you will only see the licensing properties section.SeeAdding servers on page 80 for more details on proxied source servers.

If you are using a full server to ESX appliance job, the server properties that youapply to the source will automatically apply to the target because of the way theDouble-Take replication engine works for this particular job type. Think of it assingle server replication when you are configuring your server properties.

86

General server propertiesThe general server properties identify the server.

l Default address—On a server with multiple NICs, you can specify which addressDouble-Take traffic will use. It can also be used on servers with multiple IPaddresses on a single NIC.

l Port—The server uses this port to send and receive commands and operationsbetween Double-Take servers.

l Operating system—The server's operating system version is displayed.l Product—TheDouble-Take version number is displayed.

87

Server licensingServer licensing identifies your Double-Take activation codes.

The fields and buttons in the Licensing section will vary depending on yourDouble-Take Console configuration and the type of activation codes you areusing.

l Add activation codes and activation keys—The activation code and activationkey are the Double-Take license which is required on every Double-Take server.They are a 24 character, alpha-numeric code. You can change your activationcode without reinstalling, if your license changes.

There are different licenses available.

l Evaluation—An evaluation license has an expiration date built into theactivation code.When the license expires, the software will no longerfunction. The same evaluation licenses can be used onmultiple machines

88

on a network. An evaluation license does not have to be activated.l Single—A single license is available on a per-machine basis. Each serveris required to have a unique license whether it is functioning as a source,target, or both. A single license can only be used on one server. It may havea 14 day activation period built-in or a 60 expiration date, depending on theDouble-Take product you are using and the type of license you havepurchased.

l Quantity—A quantity license is available to license a specific number ofservers. Generally, these licenses have a built-in expiration date.

l Site—A site license is available to register everymachine with the samelicense. This license is designed to be used onmultiple servers on anetwork. This licensemay or may not have to be activated, depending onthe code.

To add an activation code and activation key, type in the code and clickAdd. Ifyour console has been enabled tomanage your license inventory, clickChoosefrom inventory to open the Activation Codes dialog boxwhere you can select theactivation codes you want to apply. SeeConsole options on page 73 for details onenabling the license inventory.

The license inventory feature cannot be enabled if your service providerhas restricted access to it.

l Current activation codes—The server's current activation codes are displayed.

l Warning or error icon—Warnings indicate the license is temporary andwill expire. Errors indicate the license has expired.

l Product—The product associated with the licensel Serial Number—The serial number associated with the licensel Expiration Date—The date the license expires, if there is onel Activation Code—The activation code

To remove a code, highlight it and clickRemove. To copy a code, highlight it andclickCopy.

l Activation—If your activation code needs to be activated, you will see anadditionalActivation section at the bottom of the Licensing section. To activateyour code, use one of the following procedures.

l Activate online—If you have Internet access, you can activate your licenseand apply the activated license to the server in one step. SelectActivateOnline. You will not be able to activate a license that has already beenactivated but has not been deactivated. In that case, you will be prompted tocomplete a host transfer. Ideally, you should deactivate the license insteadof doing a host transfer. SeeDeactivating Double-Take licenses on page 69for more details. If youmust do a host transfer, you will have to export yourlicense inventory to a file, upload that file tohttps://activate.doubletake.com/hosttransferfile.aspx, and then import the

89


file you get back. SeeManaging the Double-Take license inventory on page62 for details on exporting and importing a license inventory file.

l Obtain activation key online, then activate—If you have Internetaccess, click the hyperlink in theActivation section to take you to the webso that you can submit your activation information. Complete and submit theactivation form, and you will receive an email with the activation key.Activate your server by entering the activation key in theAdd activationcodes and activations keys field and clickingAdd.

l Obtain activation key offline, then activate—If you do not have Internetaccess, go to https://activate.doubletake.com from another machine thathas Internet access. Complete and submit the activation form, and you willreceive an email with the activation key. Activate your server by entering theactivation key in theAdd activation codes and activations keys fieldand clickingAdd.

The permanent code is specific to this server. It cannot be used on any otherserver. If the activation code and server do not match, Double-Take will not run.

90


Server setup propertiesServer setup properties indicate how the server will act on startup and shutdown.

l Log statistics automatically—If enabled, Double-Take statistics logging willstart automatically when Double-Take is started.

l Enable task command processing—Task command processing is a Double-Take feature that allows you to insert and run tasks at various points during thereplication of data. Because the tasks are user-defined, you can achieve a widevariety of goals with this feature. For example, youmight insert a task to create asnapshot or run a backup on the target after a certain segment of data from thesource has been applied on the target. This allows you to coordinate a point-in-time backup with real-time replication. Enable this option to enable task commandprocessing, however to insert your tasks, youmust use the Double-Take scriptinglanguage. See theScripting Guide for more information. If you disable this optionon a source server, you can still submit tasks to be processed on a target, althoughtask command processingmust be enabled on the target.

l Advertise service with Active Directory—If enabled, the Double-Take serviceregisters withWindowsActive Directory when the service is started.

l Mirror only changed files when source reboots—If enabled, Double-Takewill use theWindowsNTFS change journal to track file changes. If the source isrebooted, only the files identified in the change journal will be remirrored to thetarget. This setting helps improvemirror times.

l Automatically reconnect during source initialization—Disk queues are userconfigurable and can be extensive, but they are limited. If the amount of disk spacespecified for disk queuing ismet, additional data would not be added to the queueand data would be lost. To avoid any data loss, Double-Take will automaticallydisconnect jobswhen necessary. If this option is enabled, Double-Take willautomatically reconnect any jobs that it automatically disconnected. Theseprocesses are called auto-disconnect and auto-reconnect and can happen in thefollowing scenarios.

l Source server restart—If your source server is restarted, Double-Takewill automatically reconnect any jobs that were previously connected. Then,if configured, Double-Take will automatically remirror the data. This processis called auto-remirror. The remirror re-establishes the target baseline toensure data integrity, so disabling auto-remirror is not advised.

91

l Exhausted queues on the source—If disk queuing is exhausted on thesource, Double-Take will automatically start disconnecting jobs. This iscalled auto-disconnect. The transaction logs and systemmemory areflushed allowing Double-Take to begin processing anew. The auto-reconnect process ensures that any jobs that were auto-disconnected areautomatically reconnected. Then, if configured, Double-Take willautomatically remirror the data. This process is called auto-remirror. Theremirror re-establishes the target baseline to ensure data integrity, sodisabling auto-remirror is not advised.

l Exhausted queues on the target—If disk queuing is exhausted on thetarget, the target instructs the source to pause. The source willautomatically stop transmitting data to the target and will queue the datachanges.When the target recovers, it will automatically tell the source toresume sending data. If the target does not recover by the time the sourcequeues are exhausted, the source will auto-disconnect as described above.The transaction logs and systemmemory from the source will be flushedthen Double-Take will auto-reconnect. If configured, Double-Take will auto-remirror. The remirror re-establishes the target baseline to ensure dataintegrity, so disabling auto-remirror is not advised.

l Queuing errors—If there are errors during disk queuing on either thesource or target, for example, Double-Take cannot read from or write to thetransaction log file, the data integrity cannot be guaranteed. To prevent anyloss of data, the source will auto-disconnect and auto-reconnect. Ifconfigured, Double-Take will auto-remirror. The remirror re-establishes thetarget baseline to ensure data integrity, so disabling auto-remirror is notadvised.

l Target server interruption—If a target machine experiences aninterruption (such as a cable or NIC failure), the source/target networkconnection is physically broken but both the source and target maintain theconnection information. The Double-Take source, not being able tocommunicate with the Double-Take target, stops transmitting data to thetarget and queues the data changes, similar to the exhausted target queuesdescribed above.When the interruption is resolved and the physicalsource/target connection is reestablished, the source begins sending thequeued data to the target. If the source/target connection is notreestablished by the time the source queues are exhausted, the source willauto-disconnect as described above.

l Target service shutdown—If the target service is stopped and restarted,there could have been data in the target queue when the service wasstopped. To prevent any loss of data, the Double-Take service will attemptto persist to disk important target connection information (such as thesource and target IP addresses for the connection, various target queueinformation, the last acknowledged operation, data in memorymoved todisk, and so on) before the service is stopped. If Double-Take is able tosuccessfully persist this information, when the Double-Take service on thetarget is restarted, Double-Take will pick up where it left off, withoutrequiring an auto-disconnect, auto-reconnect, or auto-remirror. If Double-Take cannot successfully persist this information prior to the restart (for

92

example, a server crash or power failure where the target service cannotshutdown gracefully), the source will auto-reconnect when the target isavailable, and if configured, Double-Take will auto-remirror. The remirrorre-establishes the target baseline to ensure data integrity, so disabling auto-remirror is not advised.

If you are experiencing frequent auto-disconnects, youmaywant toincrease the amount of disk space on the volumewhere the Double-Takequeue is located or move the disk queue to a larger volume.

If you havemanually changed data on the target, for example if you weretesting data on the target, Double-Take is unaware of the target datachanges. Youmust manually remirror your data from the source to thetarget, overwriting the target data changes that you caused, to ensuredata integrity between your source and target.

l Behavior when automatically remirroring—Specify how Double-Take willperform themirror when it is automatically remirroring.

l Do not mirror—Do not automatically remirror any files. If you select thisoption, you will have to start a mirror manually to guarantee data integrity.

l Mirror different files using block checksum—Any file that is differenton the source and target based on date, time, and/or size is flagged asdifferent. Themirror then performs a checksum comparison on the flaggedfiles and only sends those blocks that are different.

l Mirror all files—All files are sent to the target. l Mirror different files—Any file that is different on the source and targetbased on date, time, and/or size is sent to the target.

l Mirror only newer files—Only those files that are newer on the source aresent to the target.

Database applicationsmay update files without changing the date, time,or file size. Therefore, if you are using database applications, you shoulduse the file differenceswith checksum or mirror all option.

l Time allowed to complete shutdown operations—This setting indicates theamount of time, in seconds, for the Double-Take service to wait prior to completinga shutdown so that Double-Take can persist data on the target in an attempt toavoid a remirror when the target comes back online. A timeout of zero (0) indicateswaiting indefinitely and any other number indicates the number of seconds. Thetimeout setting only controls the service shutdown caused byDouble-Take. It doesnot control the service shutdown through a reboot or from the Service ControlManager.

93

Double-Take queueDuring the Double-Take installation, you identified the amount of disk space that can beused for Double-Take queuing. Queuing to disk allowsDouble-Take to accommodatehigh volume processing that might otherwise exhaust systemmemory. For example, onthe source, thismay occur if the data is changing faster than it can be transmitted to thetarget, or on the target, a locked file might cause processing to back up.

Double-Take Queuing DiagramThe following diagramwill help you understand how queuing works. Each numberedstep is described after the diagram.

1. If data cannot immediately be transmitted to the target, it is stored in systemmemory. You can configure how much systemmemory you want Double-Take touse for all of its processing.

2. When the allocated amount of systemmemory is full, new changed data bypassesthe full systemmemory and is queued directly to disk. Data queued to disk iswritten to a transaction log. Each transaction log can store 5MB worth of data.Once the log file limit has been reached, a new transaction log is created. The logscan be distinguished by the file namewhich includes the target IP address, theDouble-Take port, the connection ID, and an incrementing sequence number.

Youmay notice transaction log files that are not the defined size limit. Thisis because data operations are not split. For example, if a transaction loghas 10 KB left until the limit and the next operation to be applied to that fileis greater than 10 KB, a new transaction log file will be created to storethat next operation. Also, if one operation is larger than the defined sizelimit, the entire operation will be written to one transaction log.

94

3. When systemmemory is full, themost recent changed data is added to the diskqueue, as described in step 2. Thismeans that systemmemory contains the oldestdata. Therefore, when data is transmitted to the target, Double-Take pulls the datafrom systemmemory and sends it. This ensures that the data is transmitted to thetarget in the same order it was changed on the source. Double-Take automaticallyreads operations from the oldest transaction log file into systemmemory. As atransaction log is depleted, it is deleted.When all of the transaction log files aredeleted, data is again written directly to systemmemory (step 1).

4. To ensure the integrity of the data on the target, the informationmust be applied inthe same order as it was on the source. If there are any delays in processing, forexample because of a locked file, a similar queuing process occurs on the target.Data that cannot immediately be applied is stored in systemmemory.

5. When the allocated amount of systemmemory on the target is full, new incomingdata bypasses the full systemmemory and is queued directly to disk. Data queuedto disk is written to a transaction log. On the target, the transaction logs areidentified with the source IP address, the Double-Take port, the connection ID,and an incrementing sequence number.

Like the source, systemmemory on the target contains the oldest data so whendata is applied to the target, Double-Take pulls the data from systemmemory.Double-Take automaticallymoves operations from the oldest transaction log file tosystemmemory. As a transaction log is depleted, it is deleted.When all of thetransaction log files are deleted, data is again written directly to systemmemory(step 4).

The followingmemory and queue options are available for each Double-Take server.

l Queue folder—This is the location where the disk queue will be stored. Anychangesmade to the queue location will not take effect until the Double-Takeservice has been restarted on the server.

When selecting the queue location, keep inmind the following caveats.

l Select a location on a non-clustered volume that will haveminimal impact onthe operating system and applications.

l Select a location that is on a different volume as the location of theWindowspagefile.

95

l Select a dedicated, non-boot volume.l Do not select the root of a volume.l Do not select the same physical or logical volume as the data beingreplicated.

Although the read/write ratio on queue files will be 1:1, optimizing the disk for writeactivity will benefit performance because the writes will typically be occurring whenthe server is under a high load, andmore readswill be occurring after the load isreduced. Accordingly, use a standalone disk, mirrored (RAID 1) or non-paritystriped (RAID 0) RAID set, and allocatemore I/O adapter cachememory to writesfor best performance. A RAID 5 arraywill not perform aswell as amirrored ornon-parity striped set because writing to a RAID 5 array incurs the overhead ofgenerating and writing parity data. RAID 5 write performance can be up to 50%less than the write performance of a single disk, depending on the adapter anddisk.

Scanning the Double-Take queue files for viruses can cause unexpectedresults. If anti-virus software detects a virus in a queue file and deletes ormoves it, data integrity on the target cannot be guaranteed. As long as youhave your anti-virus software configured to protect the actual productiondata, the anti-virus software can clean, delete, or move an infected file andthe clean, delete, or move will be replicated to the target. This will keep thetarget from becoming infected and will not impact the Double-Takequeues.

l Amount of system memory to use—This is themaximumamount of Windowssystemmemory, in MB, that Double-Take will use.When this limit is reached,queuing to disk will be triggered. Theminimumamount of systemmemory is 512MB. Themaximumamount is dependent on the server hardware and operatingsystem. If you set this value lower, Double-Take will use less systemmemory, butyou will queue to disk sooner whichmay impact system performance. If you set ithigher, Double-Take will maximize system performance by not queuing to disk assoon, but the systemmay have to swap thememory to disk if the systemmemoryis not available.

Since the source is typically running a production application, it is important thatthe amount of memoryDouble-Take and the other applications use does notexceed the amount of RAM in the system. If the applications are configured to usemorememory than there is RAM, the systemwill begin to swap pages of memoryto disk and the system performance will degrade. For example, by default anapplicationmay be configured to use all of the available systemmemorywhenneeded, and thismay happen during high-load operations. These high-loadoperations cause Double-Take to needmemory to queue the data being changedby the application. In this case, you would need to configure the applications sothat they collectively do not exceed the amount of RAMon the server. Perhaps ona server with 4 GB of RAM running the application and Double-Take, youmightconfigure the application to use 1GB andDouble-Take to use 1GB, leaving 2GBfor the operating system and other applications on the system. Many server

96

applications default to using all available systemmemory, so it is important tocheck and configure applications appropriately, particularly on high-capacityservers.

Any changes to thememory usage will not take effect until the Double-Takeservice has been restarted on the server.

l Do not use disk queue—This option will disable disk queuing.When systemmemory has been exhausted, Double-Take will automatically begin the auto-disconnect process.

l Unlimited disk queue—Double-Take will use an unlimited amount of disk spacein the specifiedQueue folder for disk queuing, which will allow the queue usageto automatically expand whenever the available disk space expands.When theavailable disk space has been used, Double-Take will automatically begin theauto-disconnect process.

l Limit disk space for queue—This option will allow you to specify a fixed amountof disk space, in MB, in the specifiedQueue folder that can be used for Double-Take disk queuing.When the disk space limit is reached, Double-Take willautomatically begin the auto-disconnect process.

l Minimum free disk space—This is theminimumamount of disk space in thespecifiedQueue folder that must be available at all times. This amount should beless than the amount of physical disk spaceminus the disk size specified for Limitdisk space for queue.

The Limit disk space for queue andMinimum free disk spacesettingswork in conjunction with each other. For example, assume yourqueue is stored on a 10GB disk with the Limit disk space for queue setto 10GB and theMinimum free disk space set to 500MB. If anotherprogram uses 5GB, Double-Take will only be able to use 4.5 GB so that500MB remains free.

l Alert at this queue usage—This is the percentage of the disk queue that mustbe in use to trigger an alert message. By default, the alert will be generated whenthe queue reaches 50%.

97

Source server propertiesThese properties are specific to the source server role.

l Number of replication packets per one mirror packet—You can specify theratio of replication packets tomirror packets that are placed in the source queue.The default value (5) allowsDouble-Take to dynamically change the ratio asneeded based on the amount of replication data in queue. If you set a specificvalue other than the default (other than 5), the specified value will be used.Changes to this setting will take effect for future jobs. Existing jobswill have to bestopped and restarted to pick up the new ratio.

l Replicate NTFS security attributes by name—Double-Take allows you toreplicateWindows permission attributes by local name aswell as security ID(SID). By replicatingWindows security by name, you can transmit the ownernamewith the file. If that user exists on the target, then the SID associated with theuser will be applied to the target file ownership. If that user does not exist on thetarget, then the ownership will be unknown. By default, this option is disabled.

l Domain security model—If you are using aWindows domain securitymodel by assigning users at the domain level, each user is assigned asecurity ID (SID) at the domain level. When Double-Take replicates a file tothe target, the SID is also replicated. Since a user will have the same SID onthe source and target, the user will be able to access the file from the target.Therefore, this option is not necessary.

l Local security model—If you are using aWindows local securitymodel byassigning users at the local level (users that appear onmultiple machine willeach have different SIDs), you will need to enable this feature so that userscan access the data on the target. If you do not enable this feature with alocal securitymodel, after a Double-Take file and SID is replicated, a localuser will not be able to access the file because the user’s SID on the targetmachine is different from the SID that was replicated from the sourcemachine.

If you enable this option, make sure that the same groups and users exist on thetarget as they do on the source. Additionally, youmust enable this option on yourtarget server before starting a restoration, because the target is acting like asource during a restoration.

98

Enabling this optionmay have an impact on the rate at which Double-Take cancommit data on the target. File security attributes are sent to the target duringmirroring and replication. The target must obtain the security ID (SID) for the usersand groups that are assigned permissions, which takes some time. If the usersand groups are not on the target server, the delay can be substantial. Theperformance impact of enabling this option will vary depending on the type of fileactivity and other variables. For instance, it will not affect the overall performanceof large database filesmuch (since there is a lot of data, but only a few filepermissions), but may affect the performance of user files significantly (since thereare often thousands of files, each with permissions). In general, the performanceimpact will only be noticed duringmirrors since that is when the target workload isgreatest.

Regardless of the securitymodel you are using, if you create new user accountson the source, you should start a remirror so the new user account informationassociated with any files in your job can be transmitted to the target.

l Maximum pending mirror operations—This option is themaximumnumber ofmirror operations that are queued on the source. The default setting is 1000. If,duringmirroring, themirror queued statistic regularly shows low numbers, forexample, less than 50, this value can be increased to allow Double-Take to queuemore data for transfer.

l Size of mirror packets—This option determines the size of themirror packets, inbytes, that Double-Take transmits. The default setting is 65536 bytes. Youmaywant to consider increasing this value in a high latency environment (greater than100ms response times), or if your data set containsmainly larger files, likedatabases.

l Use block checksum during difference mirrors—This option allows afile differencemirror to check each block of data, regardless of the file attributes. Ifthis option is disabled, Double-Take will assume files are synchronized if theirattributesmatch.

Database applicationsmay update files without changing the date, time,or file size. Therefore, if you are using database applications, you shouldenableUse block checksum during difference mirrors to ensureproper file comparisons.

If you are not using database applications, disabling this option will shortenmirror times.

99

Target server propertiesThese properties are specific to the target server role.

l Pause mirroring at this level—You can specify themaximumpercentageof Windows systemmemory that can contain mirror data before the target signalsthe source to pause the sending of mirror operations. The default setting is 20.

l Resume mirroring at this level—You can specify theminimumpercentage ofWindows systemmemory that can contain mirror data before the target signalsthe source to resume the sending of mirror operations. The default setting is 15.

l Retry delay for incomplete operations—This option specifies the amount oftime, in seconds, before retrying a failed operation on the target. The defaultsetting is 3.

l Block target paths on connection—You can blockwriting to the replica sourcedata located on the target. This keeps the data from being changed outside ofDouble-Take processing. After failover, any target paths that are blocked will beunblocked automatically during the failover process so that users canmodify dataon the target after failover. During restoration, the paths are automatically blockedagain. If you failover and failbackwithout performing a restoration, the target pathswill remain unblocked.

Do not block your target paths if you are protecting an entire serverbecause system state data will not be able to be written to the target. Also,do not block target paths if you will be using Double-Take snapshots orbacking up from the target (most backup software uses snapshots).

l Move deleted files to this folder—This option allows you to save files that havebeen deleted, bymoving them to a different location on the target. When a filedeletion is replicated to the target, instead of the file being deleted from the target,the file ismoved to the specified location. This allows for easy recovery of thosefiles, if needed. If you enable this option, specify where you want to store thedeleted files.

100

If you aremoving deleted files on the target and you have orphan filesconfigured for removal (which is the default setting for most job types), donot move the deleted files to a location inside the replica data on the target.The deleted files that aremoved will then be deleted by the orphan filefunctionality.

l Remove deleted files after this number of days—If you aremoving deletedfiles, you can specify a length of time, in days, to maintain themoved files. Amoved file that is older than the specified number of dayswill be deleted. Double-Take checks for moved files that should be deleted once daily at 8 PM. Only thedate, not the time, of the file is considered whenmoved files are deleted. Forexample, if you specify to deletemoved files after 30 days, any file that is 31 daysold will be deleted. Because the criteria is based on days and not time, a file thatwill be deleted could have beenmoved anytime between 12:01 AMand 11:59 PM31 days ago.

If deleted files aremoved for long enough, the potential exists for thetarget to run out of space. In that case, you canmanually delete files fromthe target move location to free space.

Do not include the Recycler directory in your job if you aremoving deletedfiles. If the Recycler directory is included, Double-Take will see anincoming file deletion as amove operation to the Recycle Bin and the filewill not bemoved as indicated in themove deleted files setting.

Alternate data streams that are deleted on the source will not bemoved onthe target.

Encrypted files that are deleted on the source will only bemoved on thetarget if themove location is on the same volume as the copy of the sourcedata on the target.

Compressed and sparse files that are deleted on the source will bemovedon the target, although the compression and sparse flagswill only beretained on the target if themove location is on the same volume as thecopy of the source data on the target.

101

E-mail notification configurationYou can e-mail Double-Take event messages to specific addresses, using an SMTPmail server. (SSL or TLS are not supported.) The subject of the e-mail will contain anoptional prefix, the server namewhere themessage was logged, themessage ID, andthe severity level (information, warning, or error). The text of themessage will bedisplayed in the body of the e-mail message.

l Enable e-mail notification—This option enables the e-mail notification feature.Any specified notification settingswill be retained if this option is disabled.

l E-mail server—Specify the name of your SMTPmail server.l Log on to e-mail server—If your SMTP server requires authentication, enablethis option and specify theUser name andPassword to be used forauthentication. Your SMTP server must support the LOGIN authenticationmethod to use this feature. If your server supports a different authenticationmethod or does not support authentication, youmay need to add the Double-Takeserver as an authorized host for relaying e-mail messages. This option is not

102

necessary if you are sending exclusively to e-mail addresses that the SMTP serveris responsible for.

l From address—Specify the e-mail address that you want to appear in the Fromfield of each Double-Take e-mail message. The address is limited to 256characters.

l Send to—Specify the e-mail addresses that each Double-Take e-mail messageshould be sent to. Enter the addresses as a comma or semicolon separated list.Each address is limited to 256 characters. You can add up to 256 e-mailaddresses.

l Subject prefix andAdd event description to subject—The subject of each e-mail notification will be in the format Subject Prefix : Server Name : MessageSeverity : Message ID : Message Description. The first and last components(Subject Prefix andMessage Description) are optional. The subject line is limitedto 255 characters.

If desired, enter unique text for theSubject prefixwhich will be inserted at thefront of the subject line for each Double-Take e-mail message. This will helpdistinguish Double-Takemessages from other messages. This field is optional.

If desired, enableAdd event description to subject to have the description ofthemessage appended to the end of the subject line. This field is optional.

l Includes these events—Specify whichmessages that you want to be sent via e-mail. Specify Information,Warning, and/or Error. You can also specify whichmessages to exclude based on themessage ID. Enter themessage IDs as acomma or semicolon separated list. You can indicate rangeswithin the list.

When youmodify your e-mail notification settings, you will receive a test e-mail summarizing your new settings. You can also test e-mail notificationby clicking Test. By default, the test will be run from themachine wherethe console is running. If desired, you can send the test message to adifferent e-mail address by selectingSend To and entering a comma orsemicolon separated list of addresses. Modify theMessage Text up to1024 characters, if necessary. ClickSend to test the e-mail notification.The results will be displayed in amessage box.

E-mail notification will not function properly if the Event logs are full.

If an error occurs while sending an e-mail, a message will be generated.Thismessage will not trigger another e-mail. Subsequent e-mail errors willnot generate additional messages.When an e-mail is sent successfully, amessage will then be generated. If another e-mail fails, onemessage willagain be generated. This is a cyclical processwhere onemessage will begenerated for each group of failed e-mail messages, one for each group ofsuccessful e-mail messages, one for the next group of failedmessages,and so on.

If you start and then immediately stop the Double-Take service, youmaynot get e-mail notifications for the log entries that occur during startup.

103

By default, most anti-virus software blocks unknown processes fromsending traffic on port 25. You need tomodify the blocking rule so thatDouble-Take e-mail messages are not blocked.

104

Script credentialsThese credentials will be used when executing custom scripts for mirroring and failover.

Specify aUser name, Password, andDomain to use when running the scripts. If youdo not specify any security credentials, the account running the Double-Take service willbe used. After you have specified credentials, you can clickTest to confirm thecredentials can be used for a successful login. It the credentials cannot be authenticated,you will receive an error. You will need tomanually test that credentials you supply haveappropriate rights to execute any scripts youmay be running.

105

Log file propertiesThese settings allow you to specify your log file configuration.

l Logging folder—Specify the directory where each of the log files in this sectionare stored. The default location is the directory where the Double-Take programfiles are installed.

l Messages & Alerts—These settings apply to the service log file.l Maximum size—Specify themaximum size, in bytes, of the log file. Thedefault size is 5242880 bytes (5MB). Once themaximumhas beenreached, a new log file will be created.

l Maximum number of files—Specify themaximumnumber of log files thataremaintained. The default is 5, and themaximum is 999. Once themaximumhas been reached, the oldest file will be overwritten.

l Verification—The verification log is created during the verification process anddetails which files were verified aswell as the files that are synchronized. SeeVerification log on page 107.

l File name—This field contains the base log file name for the verificationprocess. The job type and a unique identifier will be prefixed to the base logfile name. For example, since the default is DTVerify.log, the verification logfor a files and folders job will be Files and Folders_123456abcdefDTVerify.log.

l Maximum size—Specify themaximum size, in bytes, of the verification logfile. The default is 1048576 bytes (1MB).

106

l Append—Enable theAppend check box if you want to append eachverification process to the same log file. If this check box is disabled, eachverification process that is logged will overwrite the previous log file. Bydefault, this option is enabled.

l Language—At this time, English is the only language available.l Statistics—The statistics logmaintains connection statistics such asmirror bytesin queue or replication bytes sent. This file is a binary file that is read by the DTStatutility. SeeStatistics on page 715.

l File name—This is the name of the statistics log file. The default file nameis statistic.sts.

l Maximum size—Specify themaximum size, in bytes, of the statistics logfile. The default is 10485760 bytes (10MB). Once thismaximumhas beenreached, the oldest data will be overwritten.

l Write interval—Specify how often, in minutes, Double-Take writes to thestatistics log file. The default is every 5minutes.

Verification logIn the log file, each verification process is delineated by beginning and endmarkers. A listof files that are different on the source and target is provided aswell cumulative totals forthe verification process. The information provided for each file is the state of itssynchronization between the source and the target at the time the file is verified. If theremirror option is selected so that files that are different are remirrored, the data in theverify log reflects the state of the file before it is remirrored, and does not report the stateof the file after it is remirrored. If a file is reported as different, review the output for the fileto determine what is different.

107

Sample verification log

--- VERIFICATION OF CONNECTION 2, CHECKSUM ENABLED (Sales data for alpha --> 206.31.65.40: 1100) ---Start Time: 1/24/2012 12:15:20 PM for connection 2 (Sales data for alpha -->206.31.65.40 : 1100)File: beta\users\bob\budget.xls DIFFERENT ON TARGET Source Attributes: Timestamp = 1/17/2012 8:21:36 PM Size = 1272 Mask = [0x20] Target Attributes: Timestamp = 1/17/2012 8:21:36 PM Size = 1272 Mask = [0x20]Security descriptors are different. 0 BYTES OUT OF SYNCFile: beta\users\bill\timesheet.xls DIFFERENT ON TARGET Source Attributes: Timestamp = 1/17/2012 8:21:37 PM Size = 1272 Mask = [0x20] Target Attributes: Timestamp = 1/17/2012 8:21:37 PM Size = 1272 Mask = [0x23] 0 BYTES OUT OF SYNCFile: beta\users\vincent\training.doc DIFFERENT ON TARGET Source Attributes: Timestamp = 1/12/2012 3:28:20 PM Size = 17 Mask = [0x20] Target Attributes: Timestamp = 1/20/2012 5:05:26 PM Size = 2 Mask = [0x20] 17 BYTES OUT OF SYNCCompletion Time: 1/24/2012 12:37:44 PM for connection 2 (Sales data for alpha -->206.31.65.40 : 1100)Elapsed Time (seconds): 1320.256470Total Directories Compared: 657Total Directories Missing: 0Total Directories Remirrored: 0Total Files Compared: 120978Total Files Missing: 0Total Files Different: 3Total Files Encrypted: 0Total Files Remirrored: 1Total Bytes Skipped: 0Total Bytes Compared: 18527203678Total Bytes Missing: 0Total Bytes Different: 17Total Bytes Remirrored: 17Related links and directory attributes have been adjusted.----- END OF VERIFICATION -----

l Timestamp—The last modified date and time of the filel Size—The size, in bytes, of the filel Mask—The attributes associated with the file. See further details below.l Security descriptors—TheNTFS file permissions of the file. If the filepermissions are different, themessage "Security descriptors are different" will belogged. If the file permissions are the same, nothing will be logged.

l Bytes out of sync—The number of bytes that are not synchronized between thefile on the source and the file on the target. If the data in the file is identical, themessage "0 BYTES OUTOF SYNC" will be logged. If the file is different, themessage will indicate how many byteswere different. Thismessage does notindicate that the file was remirrored during the verify.

Themaskmust be converted in order to determine what attributes are assigned to a file.Themask is a hexadecimal number corresponding to a binary number that indicateswhat the attributes are. Using the following steps, you can determine how themaskcorresponds to the attributes of a file.

1. Eachmask beginswith 0x. Identify the hexadecimal number after the constant 0x.For example, if themask is 0x23, then the hexadecimal number you are interestedin is 23. The hexadecimal number may be up to four digits.

2. Convert the hexadecimal number to its 16-digit binary equivalent. You can use theWindows calculator for this conversion.

108

a. SelectStart, Programs,Accessories,Calculator.b. Switch to scientific view, if it is not already in that view, by selectingView,

Scientific.c. SelectHex.d. Enter the hexadecimal number, for example 23, as specified in your

verification log.e. SelectBin and the hexadecimal number will change to the binary

equivalent.f. Pad the beginning of the binary equivalent with zeroes (0) so that the

number is 16 digits long. For example, hexadecimal number 23 converts to100011, so the 16-digit binary equivalent would be 0000000000100011.

3. Determine what number (0 or 1) appears in each position of the binary number.Because binary numbers count from right to left, start with position 1 on the right.

l 1—Read onlyl 2—Hiddenl 3—Nonel 4—Systeml 5—Directoryl 6—Archivel 7—Encryptedl 8—Normall 9—Temporaryl 10—Sparse filel 11—Reparse pointl 12—Compressedl 13—Offlinel 14—Not content indexedl 15—Nonel 16—None

4. Using the list above, identify those attributes that are enabled by those positionsequal to one (1). The positions equal to zero (0) are disabled and that attributedoes not apply. So hexadecimal number 23, which converted to0000000000100011, indicates read only, hidden, and archive. Another examplemight bemask 0x827 which converted to binary is 0000100000100111. Positions1-3, 6, and 12 are all enabled which indicates the file is read only, hidden, archive,and compressed.

Files that were replicated with theReplicate NTFS security attributesby name feature enabled, will be identified as different in the log filebecause of the local name attribute. The files will be the same.

109

Server and job settingsThe easiest way to view and change select server and job settings is through the Double-Take Console. However, not all of the settings are available there. To view and updatethe remaining settings, in addition to the settings available in the console, you will need togo to HKEY_LOCAL_MACHINE\SOFTWARE\NSI Software\Double-Take\CurrentVersion in the registry. For a Linux server, you can use DTSetup tomodifythe configuration settings.

The following table lists all of the settings, in decimal value.

Double-Take Availability and Double-TakeMove share the same set of serverand job settings. Some settings apply to one product, some to the other, andsome to both. For settings that apply to both, the Double-Take Availabilityterminology is used. For example, PreFailoverScript is used for the script to berun before failover or cutover.

If you are using a Linux source server, you will have only a subset of the settingslisted below.

AcquireDataRetryLimit

Description—The length of time, in milliseconds, spent retrying a fileread if there is a read error

Values—Any positive, integer value

Default—2000

Console Setting—None

Service restart required—No

ActivationCode

Description—24-character Double-Take activation code

Values—Unique value for each customer

Default—N/A

Console Setting—Edit Server Properties page, Licensing section,Current activation codes


AdapterFlags

Description—Specifies the adapter to use when establishing aconnection. This option should not be changed.

Values—2Encryption, 4 Network Data Representation

Default—4

110


Service restart required—Yes

AddOnCodes

Description—This setting is no longer used.

Advertisement

Description—Indicates if the server uses Active Directory to advertiseitself so that the Double-Take Console can be populated throughautomatic discovery

Values—0Do not use Active Directory advertisement, 8 Use ActiveDirectory advertisement

Default—8

Console Setting—Edit Server Properties page, Setup section,Advertise service with Active Directory


Notes—If Active Directory advertisement is enabled, there is a 200byte impact on the Active Directory service for each server thatregisters. The Double-Take service registers with Active Directory atstartup and unregisters at shutdown.

AllFailover

Description—Specifies which IP addresses to failover

Values—0Failover onlymonitored IP addresses, 1 Failover all IPaddresses

Default—1

Console Setting—Set Options page, Failover Options section,Failover IP addresses


AllMustFail

Description—Specifies whether or not all IP addressesmust fail forfailover to take place

Values—0any IP address can fail, 1 All IP addressesmust fail

Default—1



111

ArchiveExclusionDirectories



ArchiveExclusionFiles



ArchiveLoopAttempts



ArchiveLoopDelay



ArchivePreviewFileName


ArchivePreviewMaxFileSize


ArchiveRemoveBinFileOnRecall



ArchiveRequireMirrorCompleteTime



ArchiveUseAlternateDate



ArchiveUseDNSName



112

AutoCalcEulaAccepted

Description—Used internally byDouble-Take. Do not modify thisentry.

AutoReconnect

Description—Specifies whether to reinstate the target connection(s)when the sourcemachine is brought online after a sourcemachinefailure

Values—0Do not reconnect, 1 Reconnect

Default—1

Console Setting—Edit Server Properties page, Setup section,Automatically reconnect during source initialization


AutoRemirror

Description—Specifies whether to remirror when a source is broughtonline after an auto-disconnect

Values—0Do not remirror, 1 Perform a file differences checksummirror, 2 Perform a full mirror, 3 Perform a file differencesmirror, 4Perform a date comparisonmirror and send data only if the source datais newer than the target data.

Default—1

Console Setting—Edit Server Properties page, Setup section,Behavior when automatically reconnecting


AutoRemirrorRetry

Description—Specifies how often, in seconds, the source shouldcheck for connections that have been reconnected but still need to beremirrored

Values—any integer

Default—30



AutoRetransmit

Description—Determineswhether or not a source that has lost itsconnection with a target will attempt to reconnect to the target

Values—0Do not attempt to reconnect, 1 Attempt to reconnect

113

Default—1



BackupDir

Description—Location on the target of the backup of the protecteddata sets

Values—any valid path

Default—the location where the Double-Take files were installed



CalculateByVolume

Description—Calculates the approximate size of a protected data setby using the size of the volume and subtracting the free space

Values—0Disabled, 1 Enabled

Default—0



Notes—If your protected data set contains a large number of files, forexample, 250,000 or more, youmaywant to disable the calculation ofthe protected data set size so that data will start beingmirrored sooner.If calculation is enabled, the source calculates the file size before itstartsmirroring. This can take a significant amount of time dependingon the number of files and system performance. Disabling calculationwill result in themirror status not showing the percentage complete orthe number of bytes remaining to bemirrored. CalculateByVolume canbe enabled as a workaround. This setting will get the amount of diskspace in use for the entire volume from the operating system, so thecalculation occurs instantaneously. However, if the entire volume is notbeing replicated, themirror percentage complete and bytes remainingwill be incorrect accordingly.

Do not use enable this option if you are using a full server job because itwill bypass needed hard link processing.

CalculateOnConnect

Description—Specifies whether or not the amount of data to bemirrored should be calculated on connection

Values—0Do not calculate on connection, 1 Calculate on connection

Default—1

114



CaseSensitiveRepSetQueries

Description—This entry is no longer used.

ChangeJournalState

Description—An internal setting for change journal tracking. Do notmodify this setting.

ChecksumAll

Description—Setting to allow for the difference checksum option onmirror, verify, or restore to ignore the date, time, and size of the file andperform a checksum calculation on all files

Values—0Checksum using date, time, size comparison, 1 Checksumall files regardless of the date, time, or file size

Default—1

Console Setting—Edit Server Properties page, Source section, Useblock checksum during differencemirrors


ClusterDir

Description—Location of aMicrosoft Cluster Service installation, if itexists


Default—determined by theMicrosoft Cluster Service installation



ConnectionFile

Description—Name of the database file containing connectioninformation

Values—any valid file name

Default—connect.sts



115

CreateDumpOnAckErrors

Description—Enables additional logging for out of orderacknowledgement errors

Values—0Do not create a logging file, 1 Create a logging file

Default—0



DataPath

Description—The location of the Double-Take file attribute, protecteddata set, connection, and schedule database files





DefaultAddress

Description—The default primary IP address in amulti-homed server

Values—any valid IP address that will act as your primary IP addressfor connecting the source to the target

Default—<null>

Console Setting—Edit Server Properties page, General section,Default address


DefaultProtocol

Description—The default protocol

Values—2 IPv4 protocol only, 23 IPv4 and IPv6 protocols, 3 TDU(Throughput Diagnostics Utility)

Default—2 for Windows 2003, 23 for Windows 2008



DefaultReaderType

Description—Internal setting used byDouble-Take RecoverNow forrecoveries. Do not modify this setting.

116

DelayGCArbitration

Description—Number of seconds to delay the arbitration process.This option allows time for the network to become stable before trying toexecute arbitration logic, for example, when a cluster failover hasoccurred, but the network has a lag before it returns to a stable state.Arbitration should not start until the network is back in that stable state.

Values—any positive number

Default—0



DelayGCConnection

Description—Delays theGeoCluster Replicated Disk resourceconnection to allow the cluster service enough time to reset

Values—1-15

Default—3



DiffMirrorHardLinkCleanup

Description—Specifies if files with more than one hard link are deletedon the target during a differencemirror and then relinked after theremirror is complete. This setting only applies toWindows 2008 serverswith a full server job or full server migration job. If mirror performance isnegatively impacted by this setting, youmaywant to disable it.

Values—0Hard link files are not deleted and relinked during adifferencemirror, 1 Hard link files are deleted and relinked during adifferencemirror

Default—1



DirUNetPort

Description—Port used by pre-5.2 versions for directed UDPcommunications

Values—1025 - 65535

Default—1105


117


DisableAttributeReplication

Description—Specifies whether or not attributes (read-only, hidden,and so on) are replicated to the target

Values—0Enable attribute replication, 1 Disable attribute replication

Default—0



DropOpOnAccessDeniedError

Description—Specifies whether or not operations are dropped orretried after an access denied error

Values—0The operation will be retried, 1 The operation will bedropped

Default—1



DropOpOnHandleError

Description—Determines if an additional attempt ismade to access afile by aMicrosoft API call if the Double-Take call fails.

Values—0When opening a file using the Double-Take driver fails,attempt to open the file usingtheMicrosoft Win32 API, 1When openinga file using the Double-Take driver fails, skip the file and document it inthe Double-Take log

Default—1



Notes—If the value is set to 0 and theWin32 call also fails, Double-Take will skip the file and document it in the Double-Take log

DTSetupType

Description—Used by the Double-Take installation program tomaintain the installation settings for an upgrade. Do not modify thissetting.

118

DumpDiskQuotaIntervalMinutes

Description—Specifies how often, in minutes, a snapshot of the diskquota is taken as a backup in case the live registry is not usable atfailover or cutover


Default—240



DumpHiveIntervalMinutes

Description—Specifies how often, in minutes, a snapshot of theregistry is taken as a backup in case the live registry is not usable atfailover or cutover


Default—240



EmailEnabled

Description—Specifies if e-mail notification is enabled

Values—0E-mail notification is disabled, 1 E-mail notification isenabled

Default—0

Console Setting—Edit Server Properties page, E-mail Notificationsection, Enable e-mail notifications

Service restart required—Yes from the registry, No from the console

Notes—This is a read-only setting. If you change this setting using theregistry editor, e-mail notification will not automatically start. Youmustuse the console or a PowerShell script to start e-mail notification.

EmailExcludeIds

Description—Identifies theWindowsEvent Viewer messages that areexcluded from e-mail notification.

Values—Comma or semicolon separated list of Event Viewer IDs. Youcan indicate rangeswithin the list.

Default—None

119

Console Setting—Edit Server Properties page, E-mail Notificationsection, Exclude these event IDs


EmailFromAddress

Description—Specifies the e-mail address that will appear in the Fromfield of Double-Take generated e-mail messages.

Values—Any valid e-mail address, up to 256 characters

Default—None

Console Setting—Edit Server Properties page, E-mail Notificationsection, From address


EmailIncludeCategories

Description—Specifies which Event Viewer messages are sent via e-mail

Values—1Error messageswill be sent via e-mail, 2Warningmessageswill be sent via e-mail, 3 Informationmessageswill be sentvia e-mail

Default—1,2

Console Setting—Edit Server Properties page, E-mail Notificationsection, Include these events


EmailNotificationList

Description—Specifies the e-mail address(es) that will receiveDouble-Take generated e-mail messages.

Values—A comma separated list of valid e-mail addresses, up to 256addresses. Each address is limited to 256 characters.

Default—None

Console Setting—Edit Server Properties page, E-mail Notificationsection, Send to


EmailPassword

Description—The password required for SMTP server authentication

Values—Any valid password text

Default—None

120

Console Setting—Edit Server Properties page, E-mail Notificationsection, Password


Notes—Since the password is encrypted for security, this entry cannotbe displayed or changed through the registry.

EmailServer

Description—The name of the SMTP server for e-mail notification

Values—Any valid server name text

Default—None

Console Setting—Edit Server Properties page, E-mail Notificationsection, E-mail server (SMTP)


EmailServerPort

Description—Specifies the port that the SMTP e-mail server is using

Values—any valid port number

Default—25



EmailSmtpLogin

Description—Specifies if SMTP server authentication for e-mailnotification is enabled or disabled

Values—0SMTP authentation is disabled, 1 SMTP authenticaion isenabled

Default—0

Console Setting—Edit Server Properties page, E-mail Notificationsection, Log on to e-mail server


Notes—Your SMTP server must support the LOGIN authenticationmethod to use this feature. If your server supports a differentauthenticationmethod or does not support authentication, youmayneed to add the Double-Take server as an authorized host for relayinge-mail messages. This option is not necessary if you are sendingexclusively to e-mail addresses that the SMTP server is responsible for.

121

EmailSubjectDesc

Description—Specifies if the Event Viewer message will be appendedto the end of the subject line for e-mail notification

Values—0Event Viewer message is not included in the subject line, 1Event Viewer message is included in the subject line

Default—1

Console Setting—Edit Server Properties page, E-mail Notificationsection, Add event description to subject


EmailSubjectPrefix

Description—Specifies unique text which will be inserted at the frontof the subject line for each Double-Take generated e-mail message.This will help distinguish the Double-Takemessages from othermessages.

Values—Any valid text

Default—Double-Take Notification

Console Setting—Edit Server Properties page, E-mail Notificationsection, Subject prefix


EmailUsername

Description—The user ID required for SMTP server authentication

Values—Any valid user ID text

Default—None

Console Setting—Edit Server Properties page, E-mail Notificationsection, User name


Notes—Since the username is encrypted for security, this entry cannotbe displayed or changed through the registry.

EnableCRCCheck

Description—Indicates if Double-Take will perform a cyclicredundancy check between the source and target to identify corruptedpackets


Default—0


122


Notes—This option only needs to be set on the source server.However, if you will be restoring or reversing, where the roles of theservers are reversed, then you will need to set this option on the targetaswell.

EnableDHCP

Description—Indicates if Double-Take DHCP support is enabled


Default—1



EnableEFSVerify

Description—Indicates if Double-Take will verifyMicrosoft encryptionon the source before transmitting the encrypted file to the target


Default—0



EnableFileOpenTracing

Description—Specifies if debug-level messages are enabled to traceall mirroring and replicated files that are opened

Values—0Do not trace files that are opened, 1 Trace files that areopened

Default—0



Notes—This option should only be enabled (1) for temporary, debugsessions as instructed by technical support.

EnablePerformanceTracking

Description—This entry will be used in the future.

EnableRootEncryption

Description—Specifies if the top-level folders of a protected data setare encrypted on the source, theywill be encrypted on the target aswell


123

Default—1



Notes—If the top-level folders in a protected data set are notencrypted, disabling this optionmay obtain a small performanceimprovement.

EnableShortFileNameProcessing

Description—Indicates if Double-Take will correct any short filenames created by the operating system on the target during amirror orfor create and rename operations during replication

Values—0Do not correct any short file names on the target, 1 Correctshort file names on the target

Default—0



EnableSnapshots

Description—Specifies whether Double-Take snapshot functionalityis enabled

Values—0Double-Take snapshot functionality is disabled, 1 Double-Take snapshot functionality is enabled

Default—1



Notes—This setting only impacts Double-Take snapshot functionality.If this setting is disabled, other snapshot software such asMicrosoftVolume Shadow Copywill be not be impacted.


EnableTargetOpOrdering

Description—Identifies if the target will retain operations that arereceived out of order so they do not need to be re-requested from thesource, allowing Double-Take to workmore efficiently and reduceretransmission of operations that are dropped, perhaps due to anunreliable network

Values—0 the target will not retain operations that are out of order, 1the target will retain operations that are out of order

Default—1

124


Service restart required—No, however youmust disconnect andreconnect any existing connections for the change to take effect

Notes—EnableTargetOpOrderingmust be enabled on both sourceand target to be used.

EnableTaskCmdProcessing

Description—Queues tasks inline with replication data

Values—0Disable task command processing, 1 Enable task commandprocessing

Default—0

Console Setting—Edit Server Properties page, Setup section,Enable task command processing


ExtensionNumber

Description—Used by the Double-Take log files.

FailbackHostname

Description—Returns the host SPN (Service Principle Name) to itsoriginal setting on failback


Default—0



Notes—If you are using Active Directory, this option should be enabledor youmay experience problemswith failback.

FailoverHostname

Description—Automatically removes the host SPN (Service PrincipleName) fromActive Directory on the source


Default—0



Notes—If you are using Active Directory, this option should be enabledor youmay experience problemswith failover.

125

FailoverOnRouteFailure

Description—Determines if failover will occur when receiving a routermessage back from an IP address on the network

Values—0Failover will not occur when receiving a destination hostunreachablemessage, 1 Failover will occur when receiving adestination host unreachablemessage

Default—1



FCCHelpPath


FileAccessRetry

Description—The number of times a failed driver call will be retried bythe service.

Values—1 - 65535

Default—10



FileQueueSize

Description—When amirror is started, one thread reads from the diskand builds the file queue. Another set of threads reads files off of thequeue and sends them to the target. This setting is themaximum size ofthe queue in entries. If you had 100 files to bemirrored and this was setto 16 (the default value), the first thread would fill the queue to amaximumof 16 entries.

Values—1 - 65535

Default—16



Notes—This valuemust be set prior to starting themirror process. Thehigher the number, themorememory that is used.

ForceReplaceOnFailover

Description—Specifies additional failover options

126

Values—0Use standard failover add / replace settingswith noadditional settings, 1 Replace the target server namewith that of thesource and add the source IP address, 2 Add the source server nameto the target and replace the target IP address, 3 Replace the targetserver namewith that of the source and replace the target IP address

Default—0



ForceVerifyOnMirror

Description—Specifies if verification will be performedwith everydifferencemirror

Values—0Verification is not performedwith every differencemirror, 1Verification is performedwith every differencemirror

Default—0



GenerateDumpOnShutdownCrashes

Description—Specifies if a log file will be created during a shutdowncrash

Values—0No log file is created and the default exception handler isused, 1 Log file is created

Default—0



HardLinkInterval

Description—Specifies the length of time, in seconds, to generate ahard link report

Values—any valid integer

Default—3600



HardLinkLogPath

Description—Specifies the location where hard links will be logged. Ifno path is specified, the location defined in LogDir will be used.

127


Default—None



HBLoopback


HBTrace

Description—Specifies whether heartbeat debugging information isgenerated

Values—0not generated, 1 Generated

Default—0



HBTTL

Description—Number of secondswithout receiving a heartbeatbefore a remotemachine is considered unavailable

Values—0 - 65535

Default—10



HeartbeatIgnoreIPs


HPQueueRatio

Description—Ratio of replication packets to onemirror packet

Values—0 - 65535

Default—5

Console Setting—Edit Server Properties page, Source section,Number of replication packets per onemirror packet

Service restart required—No for future connections, Yes for thecurrent connection

Notes—AnHPQueueRatio of 5 allowsDouble-Take to dynamicallychange the ratio as needed based on the amount of replication data in

128

queue. If you set a specific value other than the default (other than 5),the specified value will be used.

IgnoreAlternateStreamFiles

Description—Specifies alternate streams to skip duringmirroring andreplication

Values—a semi-colon separate list of stream names. The streamnames are not case-sensitive

Default—none



IgnoreArchiveBit

Description—Specifies if the archive bit is compared duringverification

Values—0Archive bit is compared during a verification, 1 Archive bit isnot compared during a verification

Default—1



IgnoreDeleteOps

Description—Specifies if file and directory delete operationswill bereplicated to the target

Values—0Delete operations are replicated to the target, 1 Deleteoperations are not replicated to the target

Default—0



IgnorePPPAddresses

Description—Identifies if Double-Take will use PPP (Point-to-PointProtocol) or SLIP (Serial Line Internet Protocol) adapters

Values—0Double-Take will send out heartbeats across the PPP/SLIPadapter, 1 Double-Take will not send out heartbeats across thePPP/SLIP adapter

Default—1


129


IgnoreSourceErrors

Description—Ignores source errors that will cause an update to thetarget data state

Values—0Do not ignore source errors, 1 Ignore source errors

Default—0



IgnoreThumbnailStreams

Description—Specifies if thumbnails will be replicated to the target.

Values—0Double-Take will mirror and replicate all data streams, 1Double-Take will not mirror or replicate any data about the alternatedata streams for thumbnail images.When comparing data for averification or differencemirror,alternate data streams for thumbnailswill not be reported as different.

Default—1


Service restart required—If you change this value to 0, youmustrestart the Double-Take service in order for the Double-Take driver tobegin sending all data stream information to the service. If you changethis value to 1, you do not need to restart the service.

IgnoreWriteFailureOnTarget

Description—Specifies whether failures to write a file on the target arelogged

Values—0Log all write failures on the target, 1 or any larger integerindicates that number of write failures which will be ignored beforestarting to log the write failures

Default—0



IncludeSysVolInfo

Description—Specifies whether the system volume information folderismirrored and replicated

Values—0Do not include the system volume information folder, 1Include the system volume information folder

Default—0

130



InstallPath

Description—Path specified during the Double-Take installation. Donot modify this entry.

InstallVersionInfo

Description—Installation number specified during the Double-Takeinstallation. Do not modify this entry.

IntermediateQueueLimit

Description—Amount of memory, in KB, that may be allocated to theintermediate queue by the systemmemorymanager whenMemoryAllocatorMode is set to mixedmode (2).

Values—512-4194304

Default—65536



IPFailover

Description—Specifies whether or not to failover the IP addressesduring failover

Values—0Do not failover IP addresses 1 Failover IP addresses

Default—1

Console Setting—Set Options page, Failover Options section,Failover IP addresses


KFAIOpenRetry

Description—Specifies the number of times an operation is retried ifthe driver return an error


Default—10



131

LanguagesAvailable

Description—Specifies the Double-Take language support that hasbeen installed. Do not modify this setting. If you need to add or removelanguage support, use the Double-Take installation program.

LanguageSelected

Description—Specifies the language of the verification log

Values—Depends on LanguagesSupported

Default—Language used during the installation

Console Setting—Edit Server Properties page, Logging section,Language


LanguagesSupported

Description—Specifies the available languages for the verification log.Currently English is the only language available. Do not modify thissetting.

LastModifiedReadDelay

Description—Specifies the length of time, in seconds, to wait beforereading the last modified file time attribute


Default—15



Notes—This option is only used if SendLastModifiedTimeOnClose isdisabled

LoadSourceTarget

Description—Specifies the functionality of the Double-Take service

Values—0Neither the source nor target modules are loaded, 1 Onlythe sourcemodule is loaded, 2 Only the target module is loaded, 3 Boththe source and target modules are loaded

Default—3



LogAllOrphans


132

LogDir

Description—The location of the Double-Takemessages/alerts,verification, and statistics log files



Console Setting—Edit Server Properties page, Logging section,Logging folder


LogFile

Description—The name of the Double-Takemessages/alerts log file


Default—DTLog



LogHardlinks

Description—Indicateswhether hard links are logged to replication_set_name.log when the protected data set size is calculated

Values—0Hard links are not logged, 1 Hard links are logged

Default—0



LogMessageLevel

Description—Specifies the types of messages logged to the.dtl files

Values—0Nomessageswill be logged, 1 Only alert messageswill belogged, 2 Alert and releasemessageswill be logged, 3 Alert, release,and debugmessageswill be logged

Default—2



LoopbackID


133

MaxChecksumBlocks

Description—Specifies the number of checksum values retrieved fromthe target


Default—32



MaxConnections

Description—Number of network requests that can be processedsimultaneously. Windows is limited to 5 simultaneous requests.

Values—0 - 65535

Default—5



Notes—Vision Solutions recommends that you not change this value.

MaxLogFileSize

Description—Maximum size, in bytes, of any .dtl log file

Values—limited by available disk space

Default—5242880

Console Setting—Edit Server Properties page, Logging section,Maximum size (under Messages & Alerts)


MaxLogPathname

Description—Themaximum length of a file name (the entirevolume\directory\filename including slashes, spaces, periods,extensions, and so on) that will be displayed in the Double-Take log fileand theWindowsEvent Viewer. File names longer than theMaxDisplayablePath will be truncated and will be followed by an ellipsis(...).

Values—1-32760

Default—32760



134

MaxNumberofLogFiles

Description—Maximumnumber of .dtl log files that can exist at onetime.WhenDouble-Take creates a new .dtl file, if this number isexceeded, the oldest .dtl file is deleted.

Values—1 - 999

Default—5

Console Setting—Edit Server Properties page, Logging section,Maximumnumber of files


MaxOpBufferSize

Description—An internal setting for memory buffering. Do not modifythis setting.

MaxRemoveOrphansOpSize

Description—Determineswhether or not Double-Take will send overmultiple orphan operations. Double-Take will send over the operationsif a directory hasmore files than this number.

Values—0 - 131072

Default—1000



MaxRetry

Description—A generic, application wide setting specifying thenumber of retry attempts for processes such as creating sockets,starting the service, and so on


Default—5



MaxWriteChunkSize

Description—Maximummerged op size (in bytes) used duringreplication

Values—1 - 131072

Default—65536


135


MCHelpPath


MemoryAllocatorCallbackMode

Description—Determineswhat action is taken when theMemoryQueueToDiskThreshold ismet

Values—0Auto-disconnect processing is initiated whentheMemoryQueueToDiskThreshold has beenmet. Connectionswill bereestablished when auto-reconnect occurs, 1 The Double-Take servicestops pulling operations from the driver whentheMemoryQueueToDiskThreshold has beenmet. The target willpause the source.The service will resume pulling operationswhen thetarget tells the source to resume, 2 The source and target beginqueuing operations to disk.

Default—2



MemoryQueueToDiskThreshold

Description—A percentage of QmemoryBufferMax that will triggerqueuing to disk.

Values—any valid percentage

Default—75



MinCompressionFileSize

Description—Theminimum file size, in bytes, that will be compressed.Files smaller than this size will not be compressed.

Values—any file size

Default—1024



MirrorChunkSize

Description—Block size, in bytes, used in themirroring process

Values—1 - 1048576

136

Default—65536

Console Setting—Edit Server Properties page, Source section, Sizeof mirror packets


Notes—A higher block size value gives you better throughput, but onlyto a certain point, then it starts usingmorememory (this has to do withthe waymemory is allocated and deallocated). A lower block size valueproduces slower throughput, but usesmemory efficiently.

MirrorEncryptedFiles

Description—Specifies if Windows 200x encrypted files aremirrored

Values—0Encrypted files are not mirrored, 1 Encrypted files aremirrored

Default—1



MirrorOverwrite

Description—Determines if themirror process overwrites existing files

Values—0never overwrite, 1 always overwrite, 2 overwrite if older

Default—1



MirrorPrompting


MirrorQueueLimit

Description—Maximumnumber of mirror operations that can bequeued on the sourcemachine

Values—1 - 65535

Default—1000

Console Setting—Edit Server Properties page, Source section,Maximumpendingmirror operations


137

MirrorRootAttributes

Description—Specifies whether or not root permissions from thesource aremirrored to the target

Values—0Root permissions are not mirrored to the target, 1 Rootpermissions aremirrored to the target

Default—1



MirrorZeroKFiles

Description—Specifies whether or not empty files, zero byte files, areincluded in amirror

Values—0Zero byte files are skipped and not mirrored to the target, 1All files aremirrored to the target

Default—1



Notes—If MirrorZeroKFiles is enabled (0), zero byte files are skippedduring a full mirror, file differencesmirror, and a verification withsynchronization. Zero byte files that contain alternate data streams thatare not empty, will still be skipped if MirrorZeroKFiles is enabled.

MissedHeartbeats

Description—Specifies the number of heartbeats that can gounanswered by the source before failover occurs, when using Double-Take service responses tomonitor for failover

Values—1 - 65535

Default—20



Notes—This value is used in conjunction with the PingFrequency valueto determine the value of Consider the source server failed (on the SetOptions page, Failover Monitor section).

MissedPackets

Description—Specifies the number of requests sent by the target thatgo unanswered by the source before failover occurs, when usingnetwork responses tomonitor for failover

Values—1 - 65535

138

Default—5



Notes—This value is used in conjunction with the PingFrequency valueto determine the value of Consider the source server failed (on the SetOptions page, Failover Monitor section).

MoveOrphanedFiles


MoveOrphansDir


NameFailover

Description—Specifies whether or not to failover machine names

Values—0Do not failover machine names, 1 Failover machine names

Default—1

Console Setting—Set Options page, Failover Options section,Failover server name


NetPort

Description—Port used by pre-5.2 versions for TCP communications

Values—1025 - 65535

Default—1100



NetworkRetry

Description—Specifies the interval, in seconds, at which Double-Takewill attempt to reconnect to the target

Values—any positive number

Default—10



139

NetworkStatusInterval

Description—An internal setting for network communications. Do notmodify this setting.

NetworkTimeout

Description—Themaximum length of time, in seconds, to wait on anetwork connection. If data is not received over a network connectionwithin the specified time limit, the connection is closed. During idleperiods, Double-Take sends small amounts of keep-alive data at aninterval 1/6 of the NetworkTimeout value to keep the socket from beinginadvertently closed.


Default—120



Notes—If you are archiving files and it takes longer than theNetworkTimeout specified (for example, thismay happen if theDTArchiveBin is located on an alternate volume), the archive operationwill complete on the target, but the full file will not be changed to a linkon the source because the source detected the network timeout.

NodeLockedLicenseKey

Description—An internal setting for licensing. Do not modify thissetting.

NodeLockedServerInfo

Description—An internal setting for licensing. Do not modify thissetting.

OpBufferMax

Description—Specifies the number of operations that can be stored inthememory queue prior to queuing to disk

Values—0There is no limit to the number of operations that can bestored in thememory queue, 1 or any larger integer

Default—200000



OpBuffersCount

Description—An internal setting for memory buffering. Do not modifythis setting.

140

OpLogging

Description—Specifies whether operations from the Double-Takedriver are logged

Values—0Do not log operations, 1 Log operations

Default—0



OutOfOrderDiff

Description—Themaximumnumber of operations that can be out oforder before the connection is paused


Default—10



Notes—The larger the value, themorememory the Double-Takeservice on the targe service will use.

PingFrequency

Description—Specifies, in seconds, how often a ping is sent to thesource from amonitoring target

Values—1 - 65535

Default—5



Notes—This value is used in conjunction with theMissedHeartbeats orMissedPackets value to determine the value of Consider the sourceserver failed (on the Set Options page, Failover Monitor section).

Port

Description—Port connection for core Double-Take communications

Values—1025 - 65535

Default—6320

Console Setting—Edit Server Properties page, General section, Port


141

PostFailbackScript

Description—Location on the target where the target post-failbackscript is located

Values—Any valid path

Default—<null>

Console Setting—Set Options page, Failover Options section, Scriptfile (under Post-failback script)


PostFailbackScriptArgs

Description—Arguments to be used with the target post-failback script

Values—Any valid argument

Default—<null>

Console Setting—Set Options page, Failover Options section,Arguments (under Post-failback script)


PostFailoverScript

Description—Location on the target where the target post-failoverscript is located


Default—<null>

Console Setting—Set Options page, Failover Options section, Scriptfile (under Post-failover script)


PostFailoverScriptArgs

Description—Arguments to be used with the target post-failover script


Default—<null>

Console Setting—Set Options page, Failover Options section,Arguments (under Post-failback script)


PreFailbackScript

Description—Location on the target where the target pre-failbackscript is located

142


Default—<null>

Console Setting—Set Options page, Failover Options section, Scriptfile (under Pre-failback script)


PreFailbackScriptArgs

Description—Arguments to be used with the target pre-failback script


Default—<null>

Console Setting—Set Options page, Failover Options section,Arguments (under Pre-failback script)


PreFailbackWait

Description—Specifies whether or not to wait for the target pre-failback script to complete before finishing a failback

Values—0Do not wait, 1Wait

Default—0

Console Setting—Set Options page, Failover Options section, Delayuntil script completes (under Pre-failback script)


PreFailoverScript

Description—Location on the target where the target pre-failoverscript is located


Default—<null>

Console Setting—Set Options page, Failover Options section, Scriptfile (under Pre-failover script)


PreFailoverScriptArgs

Description—Arguments to be used with the target pre-failover script


Default—<null>

143

Console Setting—Set Options page, Failover Options section,Arguments (under Pre-failover script)


PreFailoverWait

Description—Specifies whether or not to wait for the target pre-failover script to complete before finishing a failover

Values—0Do not wait, 1Wait

Default—0

Console Setting—Set Options page, Failover Options section, Delayuntil script completes (under Pre-failover script)


ProductCode

Description—Used by the Double-Take installation program tomaintain the installation settings for an upgrade. Do not modify thisentry.

ProductName


QJournalDir

Description—The location where the queue is stored.


Default—the location specified during the installation

Console Setting—Edit Server Properties page, Queue section,Queue folder


Notes—For best results and reliability, you should select a dedicated,non-boot volume. The queue should be stored on a fixed, local NTFSvolume. This location also stores the Double-Take driver pagefile.

QJournalFileSize

Description—The size, in MB, of each queuing transaction log file.

Values—any valid file size, up to 4095MB

Default—5


144


QJournalFreeSpaceMin

Description—Theminimumamount of disk space, in MB, in thespecified QJournalDir that must be available at all times.

Values—dependent on the amount of physical disk space available

Default—250

Console Setting—Edit Server Properties page, Queue section,Minimum free disk space


Notes—TheQJournalFreeSpaceMin should be less than the amountof physical disk spaceminusQJournalSpaceMax.

QJournalPreload

Description—The number of operations being pulled from the diskqueue at one time. Do not modify this setting.

QJournalSpaceMax

Description—Themaximumamount of disk space, in MB, in thespecified QJournalDir that can be used for Double-Take queuing.When this limit is reached, Double-Take will automatically begin theauto-disconnect process.

Values—dependent on the amount of physical disk space available

Default—Unlimited

Console Setting—Edit Server Properties page, Queue section, Limitdisk space for queue


Notes—The unlimited setting allows the disk queue usage toautomatically expand whenever the available disk space expands.Setting this option to zero (0) disables disk queuing. Even if you areusing the unlimited option, Double-Take will only store 16,384 log files.If you are using the default 5MB file size, this is approximately 80GB ofdata. If you anticipate needing to be able to queuemore data than this,you should increase the size of the log files.

QLogWriteThrough

Description—Specifies if the disk queues are write-throughmode

Values—0Disk queues are not write-throughmode, 1 Disk queues arewrite-throughmode

Default—0

145



Notes—While write-throughmodemay decrease the frequency ofauto-disconnects, it may also decrease the performance of the sourceserver.

QMemoryBufferMax

Description—The amount of Windows systemmemory, in MB, that,when exceeded, will trigger queuing to disk.

Values—minimum512, maximum is dependent on the serverhardware and operating system

Default—1024

Console Setting—Edit Server Properties page, Queue section,Amount of systemmemory to use


QueryOnQuorumFile

Description—Identifies if the Double-Take service will reopen closedfiles on the quorum drive

Values—0TheDouble-Take service will not attempt to reopen aclosed file on the quroum drive to get security descriptors or lastmodified times, 1 The Double-Take service will attempt to reopen aclosed file on the quroum drive to get security descriptors or lastmodified times.

Default—1



QueueSizeAlertThreshold

Description—The percentage of the queue that must be in use totrigger an alert message in theWindowsEvent Viewer.

Values—any valid percentage

Default—50

Console Setting—Edit Server Properties page, Queue section, Alertat this queue usage


Registered


146

RemoveAllOrphans


RemoveOrphansTime


RemoveSharesOnDisconnect

Description—Specifies if shares are removed on the target machinewhen a Double-Take protected data set is disconnected from a targetor a sourcemachine ismanually shutdown by the administrator.(Shares are not removed if either the source or target machines fail.)

Values—0Remove shares from the target, 1 Do not remove sharesfrom the target

Default—1



ReplaceTarget

Description—Specifies whether or not to replace the target identitywith the source identity during a failover

Values—0Do not replace, 1 Replace

Default—0



ReplicateNtSecurityByName

Description—Determineswhether or not Double-Take replicatespermissions and attributes assigned to local (non-domain) users andgroups

Values—0Do not replicate by name, 1 Replicate by name

Default—0

Console Setting—Edit Server Properties page, Source section,Replicate NTFS security attributes by name


ReplicationDiskCheckScript

Description—Specifies the script to run if validation of the replicationdrive fails

Values—Any valid path and script file

147

Default—<null>



ReplicationDiskCheckTimeOut

Description—Specifies the interval, in seconds, between validationcheckswhen ReplicationDiskCheckSript is populated


Default—300

GUI Setting—None


RepSetDBName

Description—Name of the database that contains protected data setinformation


Default—DblTake.db



RestoreOverwrite

Description—Determines if the restoration process overwritesexisting files

Values—0never overwrite, 1 always overwrite, 2 overwrite if older

Default—2



RestorePrompting


RetentionFlag

Description—This entry will be used in the future.

RunDTInfoOnCutover

Description—Specifies if DTInfo is launched before a failover orcutover when protecting an entire server

Values—0Do not launch DTInfo, 1 Launch DTInfo

148

Default—1



RunScriptatSnaptime

Description—If a script is specified, the script is launched on the targetbefore Double-Take executes any snapshots. The snapshot will not beexecuted until the script has completed. If the script returns an error, thesnapshot will still execute.

Values—any valid path and script name

Default—<null>



RunScriptInsteadofSnap

Description—Specifies if a script specified in RunScriptAtSnaptime isexecuted

Values—0Execute script specified in RunScriptAtSnaptime, 1 Do notexecute script specified in RunScriptAtSnaptime

Default—1



SaveStatFile

Description—Determines if the statistic.sts (statistics logging) file issaved or ovewritten

Values—0overwrite, 1 saved as statistic-old.sts

Default—1



ScheduleFile

Description—Name of the database file that contains transmissionscheduling information


Default—Schedule.sts


149


ScheduleInterval

Description—The number of seconds to wait before checking thetransmission schedules to see if transmission should be started orstopped

Values—1 - 3600

Default—1



SendDirLastModifiedTime

Description—Specifies if the last modified time for directories will betransmitted to the target during a differencemirror

Values—0 last modified time on directories will not be sent to thetarget, 1 last modified time on directories will be sent to the target

Default—1



SendFileTimesOnCreate

Description—Specifies whether a file is accessed twice so that thefile’s creation time can bemodified tomatch the source

Values—0TheDouble-Take service will not access newly created filesthat have not beenmodified. These files on the target will have the dateand time of when the file was created on the target, 1 The Double-Takeservice will access newly created files. These files on the target willhave the same date and time as the source.

Default—0



Notes—New files created on the source that have not beenmodifiedwill have the date and time of when the file is created on the target. Thedate and time will be corrected tomatch the source’s true file attributeswhen a remirror or verificationmodifies them tomatch the source or thefile ismodified by a user or application on the source. For example, if thesourcemachine's clock is set to 2:00 PMand the target machine is setto 4:00 PM, a newly created file that has not beenmodified will have atime stamp of 4:00 PMwhen it is applied to the target. If this option isenabled (1), Double-Take will access the file twice, to correctly set the

150

time to 2:00 PM to reflect the file’s true attributes. If this option isdisabled (0), Double-Take will not access the file twice, and the file willhave the target time of 4:00 PMuntil it is modified (remirror, verification,or user or application update).

SendLastModifiedTimeOnClose

Description—Specifies that the last modified time attribute is sentwhen a file is closed

Values—0Last modified time is sent when Double-Take has notreceived any additional operations for the file in the time periodspecified by LastModifiedReadDelay, 1 Last modified time is sent whena file is closed, whichmay not be immediately depending on systemprocessing

Default—1



Notes—If system processing delays (such as the system cachemanager not flushing quickly enough) are causing delays in processingthe last modified time, youmaywant to consider disabling this option(0).

ServerUUID

Description—Used internally by the Double-Take service to identifyDouble-Take connections and IP addresses used between servers

Values—Unique identifier generated byDouble-Take

Default—Generated byDouble-Take



Notes—If you are certain that the server is not being used by any jobs,you can delete the ServerUUID. For example, youmaywant to deletethe ServerUUID so that you can create an image of a server afterinstalling Double-Take. A deleted ServerUUID will be re-created thenext time the Double-Take service is started. Keep inmind, if you deletethe ServerUUID and the server is being used by any jobs, you will haveproblemswith all aspects of Double-Take includingmirroring,replication, and failover.

ServicePriority

Description—The priority level at which the Double-Take service runs.

Values—2normal priority, 3 high priority

Default—2

151



Notes—TheDouble-Take service runs at normal priority by default.This option should not bemodified, however, if the priority is raised tohigh (3), it can be done throughWindows TaskManager.

ServicesToKeepRunning

Description—Services that will not be stopped on the target

Values—Comma separated list of service names

Default—<null>



ServiceStopState

Description—Used internally by the Double-Take service. Do notmodify this entry.

ShareFailover

Description—Specifies whether or not to failover shares

Values—0Do not failover shares, 1 Failover shares

Default—1

Console Setting—Set Options page, Failover Options section,Failover shares


ShareUpdateInterval

Description—Specifies how often, in minutes, the share file will besent to the target

Values—1 - 65535

Default—60



ShortFileNameScanIntervalMinutes

Description—Specifies how often, in minutes, the registry is scannedfor short file names


Default—240

152



ShutdownRebootTimeoutMinutes

Description—Specifies the amount of time, in minutes, to wait for thesource to shutdown during failover or cutover


Default—5



ShutdownTimeout

Description—The amount of time, in seconds, for the service to waitprior to completing the shutdown so that Double-Take can persist dataon the target in an attempt to avoid a remirror when the target comesback online

Values—any valid number of secondswhere 0 (zero) indicateswaitingindefinitely and any other number indicates the number of seconds

Default—0

Console Setting—Edit Server Properties page, Setup section, Timeallowed to complete shutdown operations


Notes—This setting only controls the service shutdown from theDouble-Take clients. It does not control the service shutdown through areboot or from the Service Control Manager.

SkipCompressionFileExt

Description—A period delimited list of file types that are notcompressed, even if compression is enabled.

Values—any period delimited list of file types

Default—mp3.exe.wmv.wma.qt.mpg.mpeg.zip.jpg.jpeg.tiff.tar.rar.cab



SnapshotType

Description—Specifies the type of snapshot that Double-Take takes

153

Values—0Create a client-accessible or non-client-accessiblesnapshot based on the job type , 1 Always create a client-accessiblesnapshot, 2 Always create a non-client-accessible snapshot

Default—0



SourceNewerMaxFileCount

Description—The number of files to compare during a source newerdifferencemirror

Values—1-1000

Default—16



SourcePendingAcks

Description—The number of operations received by the target queuein which the source is waiting for a response

Values—100 - 20,000

Default—2000



SourcePostFailbackScript

Description—Path on the source where the source post-failback scriptis located


Default—<null>



SourcePostFailbackScriptArgs

Description—Arguments to be used with the source post-failbackscript


Default—<null>


154


SSMKeepTargetActivationCode

Description—Specifies if the activation code on the target is replacedor maintained after a full-serer failover or cutover. Do not modify thisentry.

SSMShutdownServices

Description—Used by full server jobs to determine services toshutdown during failover or cutover. Do not modify this entry.

SSMShutdownSource

Description—Specifies if the source is shutdownwhen performingfailover or cutover

Values—0The source will not be shutdown, 1 The source will beshutdown

Default—1

Console Setting—Set Options page, Failover Options section,Shutdown the source server


Notes—This settingmust be applied on the target server.

SSMStagingBase

Description—Specifies the folder to use for staging system state filesfor full server failover or cutover. Do not modify this entry.

SSMUseDiskSignature

Description—Used by full server jobs to determine how target disksignatures are used. Do not modify this entry.

StartupScript

Description—Used by full server jobs to control the post-failover scriptafter reboot after failover. Do not modify this entry.

StatsDriverLogFlags

Description—Indicateswhich driver statistics are logged to theDouble-Take log

Values—0No driver statistics are logged, 1 State, 2 Operations, 4Paging, 8 Timing

Default—0



155

Notes—Use the sum of various values to logmultiple driver statistics.For example, a setting of 5 would log paging and state statistics. Asetting of 7 would log paging, operations, and state statistics. A settingof 15 would log all driver statistics.

StatsFileName

Description—Default file for logging statistics


Default—statistic.sts

Console Setting—Edit Server Properties page, Logging section,Filename (under Statistics)


StatsLoggingOn

Description—Specifies if Double-Take logs statistics at startup

Values—0Stats logging does not start when Double-Take starts, 1Stats logging starts when Double-Take starts

Default—0

Console Setting—Edit Server Properties page, Setup section, SetupOptions, Log statistics automatically


StatsMaxFileSize

Description—Maximum size, in MB, for the statistic.sts file

Values—limited by available disk space

Default—10485760

Console Setting—Edit Server Properties page, Logging section,Maximum size (under Statistics)


StatsMaxObjects


StatsPort

Description—Port used by pre-5.2 versions for DTStat to gatherstatistics

Values—1025 - 65535

Default—1106


156


StatsShmSize


StatsWriteInterval

Description—Interval, in minutes, in which statistics are written to thestatistic.sts file

Values—0 - 65535

Default—5

Console Setting—Edit Server Properties page, Logging section,Write interval


SystemMemoryLimit

Description—Set by the Double-Take service, each time it is started,to record the amount of availablememory.

TargetPaused

Description—Internal setting that indicates if the target machine ispaused. Do not modify this setting.

TargetPausedVirtual

Description—Internal setting that indicateswhich target machines arepaused. Do not modify this setting.

TCPBufferSize

Description—Size of the TCP/IP buffer in bytes.

Values—4096-7500000

Default—375000



Notes—The default setting creates a TCP window that willaccommodatemost environments. In most environments, this value willnot need to be adjusted. However, if your Double-Take network has along end-to-end route and the throughput is not where you wouldexpect it to be, then adjusting this parameter may have beneficialresults. This value is the bandwidth delay product, which is calculatedusing the bandwidth of the network (in bits/second) times the round triptime (in seconds) between the two ends. Use the followingrecommended settings to improve Double-Take throughputperformance.

157

l 100Mbit LAN—The setting should be around 37500.l 1Gbit LAN—The setting should be around 375000.l WAN—The setting should be around 130000.

While the calculations are fairly straight forward, the values that havebeen suggested are not exact because they depend on round trip time.Some improvements could be gained by adjusting these values eitherhigher or lower. The value suited for your environment can best bedetermined through trial and error testing.

TempDir

Description—Temporary directory used when replicatingWindows200x encrypted files.


Default—\ProgramFiles\Vision Solutions\Double-Take\Temp



TGBlockOnConnect

Description—Blocks the target path for all connections, regardless ofthe source, so that the data cannot bemodified

Values—0Target paths are not blocked, 1 Target paths are blocked

Default—0


Description—Do not modify this setting without assistance fromtechnical support.


TGCloseDelay

Description—The length of time, in milliseconds, a file is held open onthe target

Values—0 - 2000

Default—1000



Notes—If disk caching on the target is disabled either manually or bydefault (for example, by default on disks that host Active Directorydatabase files), the target systemmay be slow during amirror. If so,

158

descreasing this setting to 100, 10, and 0 will result in incrementalimprovements, with 0 returning the system performance to normal.

TGDaysToKeepMovedFiles

Description—Specifies the length of time, in days, to keepmoved filesif TGMoveFilesOnDelete is enabled


Default—0

Console Setting—Edit Server Properties page, Target section,Remove deleted files after this number of days


TGDisableAttributeReplication

Description—Specifies whether or not the attributes compression,ACL, and file mask are written to the target duringmirroring andreplication

Values—0Enable attribute replication 1 Disable attribute replication

Default—0



TGExecutionRetryLimit

Description—The number of times an unfinished operation will beretried on the target before it is discarded. If this value is set to zero (0),an operation will never be discarded and will be retried on the targetuntil it is applied.

Values—0 - 65536

Default—0



TGFileAlloc

Description—Indicates that Double-Take allocates an entire file on thefirst write of amirror operation

Values—0Disabled 1 Enabled

Default—1



159

Notes—To help eliminate file fragmentation on the target server,Double-Take should allocate the entire file first. With extremely largefiles, the file allocationmay take a long time. Therefore, youmaywant todisable the file allocation. If you disable file allocation, you will havemore fragmentation on the target disk.

TGMirrorCapacityHigh

Description—Maximumpercentage of systemmemory that cancontain mirror data before the target signals the source to pause thesending of mirror operations.

Values—2-75

Default—20

Console Setting—Edit Server Properties page, Target section,Pausemirroring at this level


TGMirrorCapacityLow

Description—Minimumpercentage of systemmemory that cancontain mirror data before the target signals the source to resume thesending of mirror operations.

Values—1-75

Default—15

Console Setting—Edit Server Properties page, Target section,Resumemirroring at this level


Notes—Themaximum value forTGMirrorCapacityLow is either 75 orTGMirrorCapacityHigh, which ever is lower.

TGMoveFilesOnDelete

Description—Specifies whether files deleted on the source areactuallymoved to a different location on the target rather than beingdeleted on the target

Values—0Files deleted on the source will be deleted on the target, 1Files deleted on the source will bemoved to a different location on thetarget

Default—0

Console Setting—Edit Server Properties page, Target section,Moved deleted files to this folder


160

Notes—If this option is enabled, the deleted files will bemoved to thelocation specified in TGMoveFilesPath.

TGMoveFilesPath

Description—Specifies where deleted files on the source are beingmoved to on the target


Default—<null>

Console Setting—Edit Server Properties page, Target section,Moved deleted files to this folder


TGMoveFilesSingleDirectory

Description—Specifies if deleted files that will bemoved on the target(see TGMoveFilesOnDelete) will bemoved to a single directorystructure

Values—0Use the same directory structure on the target as the sourceto store deleted files, 1 Use a single directory structure on the target tostore deleted files

Default—0



TGRetryLocked

Description—Minimumnumber of seconds to wait before retrying afailed operation on a target

Values—0-65536

Default—3

Console Setting—Edit Server Properties page, Target section, Retrydelay for incomplete operations


TGThreadCount

Description—This setting is no longer used

TGUnfinishedOpEvent

Description—Specifies whether or not unfinished operations on thetarget are logged to the Event Viewer

161

Values—0Unfinished operationmessages are not logged, 1Unfinished operationmessages are logged

Default—1



TGWriteCache

Description—Specifies whether or not Double-Take uses theintermediate cache

Values—0Bypass the intermediate cache and write directly to disk, 1Do not bypass the intermediate cache

Default—1



TGWriteFailureBeforeNotification

Description—Specifies the number of times an operation will beretried on the target before a notification is sent to update the targetstatus

Values—0-1024

Default—10



Notes—If you change the setting to 0, the notification will be disabled.Changing this option will only affect how the target status is displayed.To solve the underlying issue of why the operations are failing willrequire investigation into the Double-Take log files.

UpdateInterval


UpgradeCode


UseChangeJournal

Description—Specifies if theWindowsNTFS change journal is usedto track file changes. If the source is rebooted, only the files identified in

162

the change journal will be remirrored to the target. This setting helpsimprovemirror times.

Values—0Do not track file changes, 1 Track file changes and remirroronly changed files on source reboot, 2 Track file changes and remirroronly changed files on source reboot and auto-reconnect

Default—1

Console Setting—Edit Server Properties page, Setup section, Mirroronly changed files when source reboots


Notes—The corresponding Console Setting only allows off (0) and on(1) settings. Therefore, if you set UseChangeJournal to 2, thecorresponding Console Setting will be disabled. The Console Settingwill be reenabled when UseChangeJournal is set to 0 or 1.

UseEventLog

Description—Specifies whether or not messages are logged to theWindowsEvent Viewer

Values—0Do not logmessages to the Event Viewer, 1 Logmessagesto the Event Viewer

Default—1



UseLegacyDrivers


UserIntervention

Description—Specifies whether or not user intervention is required toinitiate a failover or cutover

Values—0User intervention is not required, 1 User intervention isrequired

Default—1

Console Setting—Set Options page, Failover Options section, Waitfor user to initiate failover


UseScheduledPause

Description—Used byDouble-Take for internal schedule processing.Do not modify this setting.

163

UseShareFile

Description—Specifies whether to create and use a share file or touse the shares that are currently stored in the target memory

Values—0Use the shares that are currently stored in the targetmemory, 1 Create and use a file containing the share information

Default—1



VerifyLogAppend

Description—Specifies whether the DTVerify.log file will be appendedto or overwritten

Values—0Overwrite, 1 Append

Default—1

Console Setting—Edit Server Properties page, Logging section,Append


VerifyLogLimit

Description—Maximum size of the DTVerify.log file in bytes

Values—limited by available hard drive space, up to 4GB

Default—1048576

Console Setting—Edit Server Properties page, Logging section,Maximum size (under Verification)


VerifyLogName

Description—Name of the verification log file


Default—DTVerify.log

Console Setting—Edit Server Properties page, Logging section, Filename (under Verification)


VerifyRetryInterval

Description—The time, in minutes, between when one verificationfails and a retry is scheduled to begin.

164

Values—any valid number

Default—3



VerifyRetryLimit

Description—The number of time a verification will be retried.

Values—any valid number

Default—5



VersionInfo

Description—The version of Double-Take that was installed. Do notmodify this entry.

WarningPings


WatchDogFailureProcessDump

Description—Creates a troubleshooting dump file if the Double-Takedriver stops running

Values—0Do not create a dump file, 1 Create a dump file

Default—0



WatchDogFailureScript

Description—Specifies the script to run if the Double-Take driverstops running

Values—Any valid path and script file

Default—<null>



165

Viewing server eventsHighlight a server on theManage Servers page and clickView Server Events from thetoolbar. TheView Server Events page displays the samemessages that are logged totheWindowsEvent Viewer. The list of events are displayed in the top pane of the page,although the description is limited.When you highlight an event, the event details,including the full description, are displayed in the bottom pane of the page.

l Severity—An icon and/or text that classifies the event, such as Error, Warning,Information, Success Audit, or Failure Audit.

l Time—The date and time the event occurred.l ID—An identification number to help identify and track event messages.l Source—The component that logged the event.l Description—The event details.

You can filter the events displayed by using the Filter drop-down list or theViewWarning Events andView Error Events toolbar buttons. To clear a filter, selectAllevents in the Filter drop-down list. SeeEvent messages on page 732 for a complete listof the service and driver event messages.

166

Viewing server logsYou can view the Double-Take and Double-TakeManagement Service log files throughthe Double-Take Console using either of these twomethods.

l On theManage Servers page, highlight a server in the list and clickView ServerLogs from the toolbar.

l On theManage Jobs page, right-click a job and selectView Logs. Select eitherthe source server log or the target server log.

Separate logging windows allow you to continue working in the Double-Take Consolewhile monitoring logmessages. You can openmultiple logging windows for multipleservers. When the Double-Take Console is closed, all logging windowswill automaticallyclose.

167

The following table identifies the controls and the table columns in theServer logswindow.

Start

This button starts the addition and scrolling of new messages in thewindow.

Pause

This button pauses the addition and scrolling of new messages in thewindow. This is only for theServer logswindow. Themessages arestill logged to their respective files on the server.

Copy

This button copies themessages selected in theServer logswindowto theWindows clipboard.

Clear

This button clears theServer logswindow. Themessages are notcleared from the respective files on the server. If you want to view all ofthemessages again, close and reopen theServer logswindow.

Filter

From the drop-down list, you can select to view all logmessages or onlythosemessages from the Double-Take log or the Double-TakeManagement Service log.

Time

This column in the table indicates the date and time when themessagewas logged.

Description

This column in the table displays the actual message that was logged.

Service

This column in the table indicates if themessage is from the Double-Take log or the Double-TakeManagement Service log.

See Log files on page 704 for more information on the log files.

168

Managing VMware serversTomanage your VMware servers, selectGo,Manage VMware Servers. TheManageVMware Server page allows you to view, add, remove, or edit credentials for yourVMware servers available in the console.

VMware Server

The name of the VMware server

Full Name

The full name of the VMware server

User Name

The user account being used to access the VMware server

Add VMware Server

Add a newWMare server. When prompted, specify the VMware serverand a user account.

Remove Server

Remove the VMware server from the console.

Provide Credentials

Edit credentials for the selected VMware server. When prompted,specify a user account to access the VMware server.

169

Managing snapshotsA snapshot is an image of the source replica data on the target taken at a single point intime. Snapshots allow you to view files and folders as they existed at points of time in thepast, so you can, for example, recover from caseswhere corrupted source data wasreplicated to the target. For someDouble-Take job types, when failover is triggered, youcan use the live target data at the time of failover or you can failover to a snapshot of thetarget data.

1. From theManage Jobs page, highlight the job and clickManage Snapshots inthe toolbar.

2. You will see the list of snapshots, if any, associated with the job.l Scheduled—This snapshot was taken as part of a periodic snapshot. l Deferred—This snapshot was taken as part of a periodic snapshot,although it did not occur at the specified interval because the job betweenthe source and target was not in a good state.

l User Request—This snapshot was takenmanually by a user.3. ClickTake Snapshot to create a new snapshot for the job.4. If there is a snapshot that you no longer need, highlight it in the list and click

Delete.5. When you have completed your snapshot management, clickClose.

Snapshot statesWhenDouble-Take transitions from a good state to a bad state, it will automaticallyattempt to take a snapshot of the data before it leaves the good state and enters the badstate. For example, if your data is in a good state and you start a mirror, before themirroris started, Double-Take will automatically take a snapshot of the target. In the event themirror fails to complete, you will have a snapshot of the data on the target when it was inits last good state. Only one automatic snapshot per job ismaintained on the target.When an automatic snapshot is taken, it replaces any previous automatic snapshots.

A snapshot may not necessarily be useful if the data on the target is in a bad state. Youonly want snapshots of data that is in a good state. Therefore, you need to understandwhen the data is in a good or bad state.

l Mirror startedl State—Badl Description—Mirroring has started, but is not complete. The data on thesource and target will not be synchronized until themirror is complete.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will be delayed until themirror iscomplete before taking a snapshot.

l User interaction required for manual snapshots—Wait until themirroris complete and the data is in a good state, then take amanual snapshot.

170

l Mirror stoppedl State—Badl Description—Mirroring has stopped without completing. The data on thesource and target will not be synchronized until themirror is complete.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will be delayed until themirror hasbeen restarted and is complete before taking a snapshot.

l User interaction required for manual snapshots—Restart themirror,wait until it is complete and the data is in a good state, and then take amanual snapshot.

l Mirror completel State—Goodl Description—Because themirror is complete, the data on the source andtarget is synchronized. Double-Take will take a snapshot while the data is ina good state.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will occur normally.

l User interaction required for manual snapshots—Manual snapshotscan be taken normally.

l Write operation retriedl State—Goodl Description—An operation cannot be written to the hard drive on thetarget. For example, the file could be in use by another application on thetarget.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will occur normally, although theoperation that is being retried will not be included in the snapshot.

l User interaction required for manual snapshots—Manual snapshotscan be taken normally, although the operation that is being retried will not beincluded in the snapshot.

l Write operation droppedl State—Badl Description—An operation could not be written to the hard drive on thetarget, even after multiple retries. For example, the file could be in use byanother application on the target.

l Automatic action taken for scheduled and automatic snapshots—An automatic snapshot will be taken just prior to the operation beingdropped. Scheduled snapshots will be delayed until the target data is backin a good state.

l User interaction required for manual snapshots—Start a mirror, waituntil it is complete and the data is in a good state, and then take amanualsnapshot.

171

l Write operation succeededl State—Goodl Description—An operation that was retrying on the target has beensuccessfully written to the hard drive.



l Target restarted with job persistencel State—Goodl Description—The target service was able to persist job information prior torestarting.



l Target restarted without job persistencel State—Badl Description—The target service has been restarted and was unable topersist job information, therefore, operations that were in the queue havebeen lost.

l Automatic action taken for scheduled and automatic snapshots—An automatic snapshot will be taken after the target restarts, if the targetdata was in a good state prior to the target restart and the job is configuredto auto-remirror on auto-reconnect. Scheduled snapshots will be delayeduntil the target data is back in a good state.

l User interaction required for manual snapshots—Start a mirror, waituntil it is complete and the data is in a good state, and then take amanualsnapshot.

l Restore requiredl State—Good or badl Description—The data on the target no longer matches the data on thesource because of a failover. This does not necessarilymean that the dataon the target is bad.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will be delayed until a restore iscompleted or the restore required state is overruled by amirror. Once therestoration or mirror is complete, automatic and scheduled snapshots willoccur normally.

l User interaction required for manual snapshots—Restore the targetdata back to the source or override the restore required state by performingamirror. Once the restoration or mirror is complete, manual snapshots canbe taken normally.

172

l Snapshot revertedl State—Good or badl Description—The data on the target no longer matches the data on thesource because a snapshot has been applied on the target. This does notnecessarilymean that the data on the target is bad.

l Automatic action taken for scheduled and automatic snapshots—Scheduled and automatic snapshots will be delayed until a restore iscompleted or the snapshot reverted state is overruled by amirror. Once therestoration or mirror is complete, automatic and scheduled snapshots willoccur normally.

l User interaction required for manual snapshots—Restore the targetdata back to the source or override the snapshot reverted state byperforming amirror. Once the restoration or mirror is complete, manualsnapshots can be taken normally.

l Restore completel State—Goodl Description—Because the restoration is complete, the data on the sourceand target is synchronized.



To be completely assured that your data on the target is good, automatic and scheduledsnapshots only occur when the data is in a good Double-Take state. However, manualsnapshots can be taken during any state. There are instanceswhen youmaywant totake amanual snapshot, even if the target data is in a bad state. For example, if you dropan operation, that does not necessarilymean your data on the target is corrupt or thetarget would be unable to stand in for the source in the event of a failure. A snapshot of abad statemay be useful and usable, depending on your environment. If your source is afile server and an operation has been dropped, it is just one user file that is out-of-date.All of the remaining target files are intact and can be accessed in the event of a failure.However, if your source is an application server and an operation has been dropped, thatone file could cause the application not to start on the target in the event of a failure. Inthese cases, manual snapshots of a bad state depend on the context of yourenvironment.

173

Chapter 6 Selecting a protection typeDouble-Take is an exceptionally flexible product that can be used in a wide variety ofnetwork configurations. However, this flexibility canmake it difficult to determine whichDouble-Take job is right for your environment. Knowing what you want to protect on yoursource is the key to determine which Double-Take job to use. Review the followingdecision trees to find which job type is best for your needs and environment.

l Data protection—If you want to protect specific data on your source, your jobtype will be a files and folders job. Review the following data decision tree to seethe various configurations available for a files and folder job.

If your source is a domain controller, you should use one of the full serverprotectionmethods to protect the entire server because of complexitieswith SPNs.

174

l Application protection—If you want to protect Microsoft Exchange or MicrosoftSQL, your job type will be an Exchange Server or SQL Server job. Review thefollowing application decision tree to see the various configurations available forthese job types.

If your source is a domain controller, you should use one of the full serverprotectionmethods to protect the entire server because of complexitieswith authentication and as a best practice.

175

l Full server protection—Protecting an entire server is themost flexible, but confusing, scenario. Unlike the data andapplication decision trees, the full server decision trees leads you tomany different possible Double-Take job types.Because the full server decision tree is so large and complex, it is broken down into smaller sections on the followingpages. Study the full server decision tree, or the following smaller sections, to determine the best job type for yourenvironment and protection needs.

176

Physical source server branches of the full server decision tree

177

Windows at the virtual guest level of an ESX host branches ofthe full server decision tree

178

Windows at the virtual guest level of a Hyper-V host branches ofthe full server decision tree

179

Windows at the virtual guest level of non-ESX or non-Hyper-Vhost branches of the full server decision tree

180

Linux at the virtual guest level branch of the full server decisiontree

181

Host level branches of the full server decision tree

182

Chapter 7 Files and folders protectionThis section is specific to files and folders protection and includes the following topics.

l See Files and folders requirements on page 184—Files and folders protectionincludes specific requirements for this type of protection.

l SeeCreating a files and folders job on page 186—This section includes step-by-step instructions for creating a files and folders job.

l SeeManaging and controlling files and folders jobs on page 213—You can viewstatus information about your files and folders jobs and learn how to control thesejobs.

l See Failing over files and folders jobs on page 233—Use this section when afailover condition has beenmet or if you want to failover manually.

l See Failback and restoration for files and folders jobs on page 234—Use thissection to determine if you want to failback and then restore or if you want torestore then failback.

If your source is a domain controller, you should use one of the full serverprotectionmethods to protect the entire server because of complexities withSPNs. SeeSelecting a protection type on page 174.

183

Files and folders requirementsThe files and folders job does not have any additional requirements beyond theCoreDouble-Take requirements on page 28. However, you should review the following tableto understand the supported configurations for a files and folders job.

Configuration Supported NotSupported

Source totargetconfiguration1

One-to-one, active/standby X

One-to-one, active/active X

Many-to-one X

One-to-many X

Chained X

Single server X

Serverconfiguration

Standalone-to-standalone X

Standalone-to-cluster X

Cluster-to-standalone X

Cluster-to-cluster X

Cluster Shared Volumes (CSV) guest level X

Cluster Shared Volumes (CSV) host level X

Upgradeconfiguration2

Upgrade 5.2 Replication Console connectionto 6.0 Double-Take Console files and foldersjob

X

Upgrade 5.2 Double-Take Source Connectionresource connection to 6.0 Double-TakeConsole files and folders cluster job

X

Upgrade 5.3 Replication Console connectionto 6.0 Double-Take Console files and foldersjob

X

Upgrade 5.3 Double-Take Source Connectionresource connection to 6.0 Double-TakeConsole files and folders cluster job

X

Upgrade 5.3 Double-Take Console files andfolders job to 6.0 Double-Take Console filesand folders job

X

184

1. SeeSupported configurations on page 16 for details on each of the source totarget configurations.

2. When using a supported upgrade configuration, you can perform a rolling upgradewhere you update the target server first. After the upgrade is complete, the sourcewill automatically reconnect to the target. Upgrade the source when convenient.For an upgrade configuration that is not supported, you will have to delete theexisting connection before the upgrade and create a new job after the upgrade.

185

Creating a files and folders jobUse these instructions to create a files and folders job.

Note the following information concerning cluster scenarios.

l For cluster to standalone jobs, the source cluster name and the standalonetarget must be added to theManage Servers page. Double-Take will querythe source cluster name and get a list of cluster groups that contain a file shareresource and then present those groups for protection. Double-Take willfailover the name, IP addresses, SPNs, and shares for the clustered fileserver to the standalone target.

l For cluster to cluster jobs, the source and target cluster namesmust be addedto theManage Servers page. Double-Take will query the source clustername and get a list of cluster groups that contain a file share resource andthen present those groups for protection. Double-Take will not failover thename, IP addresses, SPNs, or shares. Failover will be DNS failover. Groupswill be brought online on the target, therefore they need to be pre-stagedusing step 1 or 2 below, depending on your operating system.

1. If your target is a cluster and you are usingWindows 2003, follow theseinstructions to configure the cluster before you create your Double-Take files andfolders job.

a. Take the source file server Network Name offline.b. Create the sameNetwork Name on the target cluster in the file server

group.c. Create identical file shares in the target file server group andmake them

dependent on the Network Name that was just created.d. Take the target Network Name resource offline.e. Bring the source Network Name resource online.f. If it is not already, DNS registrationmust be enabled for a source cluster

name for DNS failover to function properly. You should not allow the sourcecluster name to come online if your source fails over.

2. If your target is a cluster and you are usingWindows 2008, follow theseinstructions to configure the cluster before you create your Double-Take files andfolders job.

a. Youmaywant to lower the TTL (time to live) value of your DNS records toavoid caching during this configuration.

b. Give the target cluster account full control over the source file serveraccount in Active Directory and over the source file server DNS record.

186

If control of the DNS record is not added, the Client Access Pointwill fail name resolution and you will not be able to create the targetshares unless the record ismanually updated.

c. Take the source file server Client Access Point offline, including IP address,and then flush DNS on the target.

d. Create the Client Access Point with the same name on the target andprovide a unique IP address.

e. While the target Client Access Point is online, create identical shares to thesource file server.

f. Take the target Client Access Point and IP address offline. Take the targetfile share resources offline.

g. Bring the source Client Access Point online. DNS registration will changethe IP address back to the source IP address.

h. If desired, reset your TTL value back to its original value.i. If it is not already, DNS registrationmust be enabled for a source clustername for DNS failover to function properly. You should not allow the sourcecluster name to come online if your source fails over.

3. ClickGet Started from the toolbar.

4. SelectDouble-Take Availability and clickNext.

5. SelectProtect files and folders, an application, or an entire Windowsserver and clickNext.

6. Choose your source server. This is the server that contains the files and foldersthat you want to protect. If your source is a cluster, select the cluster name, not thefile server name.

187

l Current Servers—This list contains the servers currently available in yourconsole session. Servers that are not licensed for the workflow you haveselected will be filtered out of the list. Select your source server from the list.

l Find a New Server—If the server you need is not in theCurrent Serverslist, click the Find a New Server heading. From here, you can specify aserver along with credentials for logging in to the server. If necessary, youcan clickBrowse to select a server from a network drill-down list.

If you enter the source server's fully-qualified domain name, the Double-Take Console will resolve the entry to the server short name. If that shortname resides in two different domains, this could result in name resolutionissues. In this case, enter the IP address of the server.

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. Ideally, you should use a local account rather than adomain account because the domain account will fail to authenticate to thesource while failed over if the NETBIOS name and/or SPNs are failedover to the target. Additionally, if the source is a domain controller,Double-Take will add the security groups to the usersOU, thereforepermissionsmust be located there. If you want Double-Take to updateDNS during failover, the account must be amember of the DomainAdmins group. If your security policies do not allow use of this group, seeDNS on page 844 and use the instructions under the Double-Take DFOutility to use a non-Domain Admins account.

188

To best prepare for a potential failover, restore, and failback scenario, youmaywant to use a source server that has been inserted into the consoleby a private IP address. In this scenario, your sourcemust have at leasttwo IP addresses, one for public communication and one for private. If youinsert your source in the console using the private IP address, then thatprivate IP address canmore easily be used after a failure to restore thedata that changed during failover from the target back to the source. Ifyour source server has already been inserted into the console by name,you can remove it and reinsert it by private IP address on theManageServers page.


8. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, select Files and Folders. In theWorkload itemspane, you will see the volumes and shares (if any) for your source, or if you areprotecting a cluster, you will see your cluster groups. Select the volumes, shares,or cluster groups that you want to protect.

If the workload you are looking for is not displayed, enableShow all workloadtypes. The workload types in gray text are not available for the source server youhave selected. Hover your mouse over an unavailable workload type to see areason why this workload type is unavailable for the selected source.

9. To select your files and folders in more detail, click theReplication Rulesheading and expand the volumes under Folders.

Volumes and folders with a green highlight are included in their entirety in theprotection. Volumes and folders highlighted in light yellow have individual filesincluded in the protection. If there is no highlight, no part of the volume or folder isincluded in the protection. Tomodify the items selected, highlight a volume, folder,

189

or file and clickAdd Rule. You can also enter a rule, including a wildcardspecification, manually. Specify if you want to Include or Exclude the item. Also,specify if you want the rule to be recursive, which indicates the rule shouldautomatically be applied to the subdirectories of the specified path. If you do notselectRecursive, the rule will not be applied to subdirectories.

If you need to remove a rule, highlight it in the list at the bottom and clickRemoveRule. Be careful when removing rules. Double-Takemay createmultiple ruleswhen you are adding directories. For example, if you add E:\Data to be included inprotection, then E:\ will be excluded. If you remove the E:\ exclusion rule, then theE:\Data rule will be removed also.


11. Choose your target server. This is the server that will store the replica data fromthe source.

l Current Servers—This list contains the servers currently available in yourconsole session. Servers that are not licensed for the workflow you haveselected and those not applicable to the workload type you have selectedwill be filtered out of the list. Select your target server from the list.


If you enter the target server's fully-qualified domain name, the Double-Take Console will resolve the entry to the server short name. If that shortname resides in two different domains, this could result in name resolutionissues. In this case, enter the IP address of the server.

190

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. Ideally, you should use a local account rather than adomain account because the domain account will fail to authenticate to thesource while failed over if the NETBIOS name and/or SPNs are failedover to the target. Additionally, if the source is a domain controller,Double-Take will add the security groups to the usersOU, thereforepermissionsmust be located there. If you want Double-Take to updateDNS during failover, the account must be amember of the DomainAdmins group. If your security policies do not allow use of this group, seeDNS on page 844 and use the instructions under the Double-Take DFOutility to use a non-Domain Admins account.


13. You havemany options available for your files and folders job. However, not all ofthe optionswill be applicable to clustered environments. Configure those optionsthat are applicable to your environment.

Go to each page identified below to see the options available for that section of theSet Options page. After you have configured your options, continue with the nextstep on page 212.

l General on page 192l Failover Monitor on page 193l Failover Options on page 195l Failover Identity on page 198l Mirror, Verify & Orphaned Files on page 201l Network Route on page 204l PathMapping on page 205l Failover Services on page 206l Snapshots on page 207l Compression on page 208l Bandwidth on page 209l Scripts on page 211

191

General

For the Job name, specify a unique name for your job.

192

Failover Monitor

l Total time to failure—Specify, in hours:minutes:seconds, how long thetarget will keep trying to contact the source before the source is consideredfailed. This time is precise. If the total time has expired without a successfulresponse from the source, this will be considered a failure.

Consider a shorter amount of time for servers, such as a web server ororder processing database, whichmust remain available and responsive atall times. Shorter times should be used where redundant interfaces andhigh-speed, reliable network links are available to prevent the falsedetection of failure. If the hardware does not support reliablecommunications, shorter times can lead to premature failover. Consider alonger amount of time for machines on slower networks or on a server thatis not transaction critical. For example, failover would not be necessary inthe case of a server restart.

l Consecutive failures—Specify how many attempts the target will make tocontact the source before the source is considered failed. For example, ifyou have this option set to 20, and your source fails to respond to the target20 times in a row , this will be considered a failure.

l Monitor on this interval—Specify, in hours:minutes:seconds, how long towait between attempts to contact the source to confirm it is online. Thismeans that after a response (success or failure) is received from the source,Double-Take will wait the specified interval time before contacting thesource again. If you set the interval to 00:00:00, then a new checkwill beinitiated immediately after the response is received.

If you choose Total time to failure, do not specify a longer interval thanfailure time or your server will be considered failed during the intervalperiod.

193

If you chooseConsecutive failures, your failure time is calculated by thelength of time it takes your source to respond plus the interval time betweeneach response, times the number of consecutive failures that can beallowed. That would be (response time + interval) * failure number. Keep inmind that timeouts from a failed check are included in the reponse time, soyour failure time will not be precise.

l Network monitoring—With this option, the target will monitor the sourceusing a network ping.

l Monitor these addresses—Select eachSource IP Address thatyou want the target to monitor.

If you are protecting a cluster, you are limited to the IPaddresses in the cluster group that you are protecting.

l Monitoring method—This option determines the type of networkping used for failover monitoring.

l Network service—Source availability will be tested by anICMP ping to confirm the route is active.

l Replication service—Source availability will be tested by aUDP ping to confirm the Double-Take service is active.

l Network and replication services—Source availability willbe tested by both an ICMP ping to confirm the route is activeand a UDP ping to confirm the Double-Take service is active.Both pingsmust fail in order to trigger a failover.

l Failover trigger—If you aremonitoringmultiple IP addresses,specify when you want a failover condition to be triggered.

l One monitored IP address fails—A failover condition will betriggered when any one of themonitored IP addresses fails. Ifeach IP address is on a different subnet, youmaywant totrigger failover after one fails.

l All monitored IP addresses fail—A failover condition will betriggered when all monitored IP addresses fail. If there aremultiple, redundant paths to a server, losing one probablymeans an isolated network problem and you should wait for allIP addresses to fail.

194

Failover Options

l Wait for user to initiate failover—Bydefault, the failover processwillwait for you to initiate it, allowing you to control when failover occurs. Whena failure occurs, the job will wait in Failover Condition Met for you tomanually initiate the failover process. Disable this option only if you wantfailover to occur immediately when a failure occurs.

l Failover shares—Bydefault, shareswill be failed over to the target. If youdo not want to failover shares, disable this option.

Automatic share failover only occurs for standardWindows filesystem shares. Other sharesmust be configured for failoverthrough the failover scripts or createdmanually on the target. SeeMacintosh shares on page 853 orNFS Shares on page 854 formore information.

If you are failing over Windows shares but your source and targetdo not have the same drive letters, youmust use theAll to Oneselection under Path Mappingwhen establishing your job.Otherwise, the shareswill not be created on the target duringfailover.

If your target is a standalone server, Windows share information isautomatically updated on the target once an hour. If your target is acluster, you will need tomanually update shares on the target. ForWindows 2003, you can create the file share resourceswhile the

195

source is running but keep the resource offline. For Windows 2008,you will need to repeat the initial cluster configuration steps,although you can skip giving the target cluster account full controland creating the target Client Access Point, because those stepswere already completed during the initial cluster configuration.

Shares are not applicable to environments where the target is acluster.

l Failover host name—If desired, you can failover the source server's hostname. This will automatically remove the host SPN (Service PrincipleName) fromActive Directory on the source and add it to Active Directory onthe target. If you are using Active Directory, enable this option or youmayexperience problemswith failover.

l Failback host name—This option returns the host SPN on the source andtarget back to their original settings on failback. If you are using ActiveDirectory, enable this option or youmay experience problemswith failback.

l Active Directory Credentials—If you are failing over and/or failing backthe host name, you need to specify a user that has update privilegeswithinActive Directory. ClickActive Directory Credentials and identify a userand the associated password that has privileges to create and delete SPNs.The usernamemust be in the format fully_qualified_domain\user,, and theaccount password cannot be blank.

l Scripts—You can customize failover and failback by running scripts on thesource and target. Scriptsmay contain any validWindows command,executable, or batch file. The scripts are processed using the same accountrunning the Double-Take service, unless you have identified a specificaccount through the server's properties. SeeScript credentials on page105. Examples of functions specified in scripts include stopping services onthe target before failover because theymay not be necessary while thetarget is standing in for the source, stopping services on the target that needto be restarted with the source’smachine name and/or IP address, startingservices or loading applications that are in an idle, standbymodewaiting forfailover to occur, notifying the administrator before and after failover orfailback occurs, stopping services on the target after failback because theyare no longer needed, stopping services on the target that need to berestarted with the target machine’s original name and/or IP address, and soon. There are four types of failover and failback scripts.

l Pre-failover script—This script runs on the target at the beginningof the failover process. Specify the full path and name of the script file.

l Post-failover script—This script runs on the target at the end of thefailover process. Specify the full path and name of the script file.

l Pre-failback script—This script runs on the target at the beginningof the failback process. Specify the full path and name of the scriptfile.

196

l Post-failback script—This script runs on the target at the end of thefailback process. Specify the full path and name of the script file.

l Arguments—Specify a comma-separated list of valid argumentsrequired to execute the script.

l Delay until script completes—Enable this option if you want todelay the failover or failback process until the associated script hascompleted. If you select this option, make sure your script handleserrors, otherwise the failover or failback processmay never completeif the process is waiting on a script that cannot complete.

Scripts will run but will not be displayed on the screen if the Double-Takeservice is not set to interact with the desktop. Enable this option through theWindowsServices applet.

197

Failover Identity

l Apply source network configuration to the target—If you select thisoption, you can configure the source IP addresses to failover to the target. Ifyour target is on the same subnet as the source (typical of a LANenvironment), you should select this option.

If you are applying the source network configuration to the target inaWAN environement, do not failover your IP addresses unless youhave a VPN infrastructure so that the source and target can be onthe same subnet, in which case IP address failover will work thesame as a LAN configuration. If you do not have a VPN, you canautomatically reconfigure the routers via a failover script (bymovingthe source's subnet from the source's physical network to thetarget's physical network). There are a number of issues to considerwhen designing a solution that requires router configuration toachieve IP address failover. Since the route to the source's subnetwill be changed at failover, the source server must be the onlysystem on that subnet, which in turn requires all server

198

communications to pass through a router. Additionally, it may takeseveral minutes or even hours for routing tables on other routersthroughout the network to converge.

l Failover server name—Select this option to failover the servername to the target. Double-Take checks the hosts file and uses thefirst name there. If there is no hosts file, Double-Take will use the firstname in DNS. (Keep inmind, the first name in DNSmay not alwaysbe the same each time the DNS server is rebooted.) Lastly, if there isno DNS server, Double-Take will use the failover monitor namecreated by the Double-Take Console. You will need to failover theserver name for file shares to function properly after failover. If you donot want to failover the server name, disable this option.

l Add these addresses to the selected target adapter afterfailover—Select which IP addresses you want to failover and selectthe Target Network Adapter that will assume the IP address duringfailover.

If you have inserted your source server into the console usinga private IP address, do not select the private IP address forfailover.

If you configured failover to be triggered when all monitoredIP addresses fail and are failing over more IP addresses thanyou aremonitoring, youmay have IP address conflicts afterfailover. For example, if youmonitor two out of threeaddresses, and those two addresses fail but the third onedoes not, and you failover all three IP addresses, the thirdaddress that did not fail may exist on both the source and thetarget, depending on the cause of the failure. Therefore,when a source is failing over more IP addresses than arebeingmonitored, there is a risk of an IP address conflict.


l Retain target network configuration—If you select this option, the targetwill retain all of its original IP addresses. If your target is on a differentsubnet (typical of aWAN environment), you should select this option.

If you choose to retain the target network configuration, but havealso selected to failover shares under the Failover Options sections,the source NetBIOS namewill automatically be failed over so thatthe shares can be accessed after failover.

199

l Update DNS server—Specify if you want Double-Take to updateyour DNS server on failover. If DNS updates aremade, theDNS recordswill be locked during failover.

Expand theDNS Options section to configure how the updateswillbemade. The source's domain, the current DNS credentials, and theDNS servers from the source's domain controller will be discoveredand displayed.

l Change—If necessary, click this button and specify a user thathas privileges to access andmodify DNS records. The accountmust be amember of the DnsAdmins group for the domain,andmust have full control permissions on the source's A (host)and PTR (reverse lookup) records. These permissions are notincluded by default in the DnsAdmins group. You can enter auser name for a different domain by entering a fully qualifieduser name. The fully qualified user namemust be in the formatdomain\username or username@domain. If you enter a non-qualified name, the selected domain will be used.

l Remove—If there are anyDNS servers in the list that you donot want to update, highlight them and clickRemove.

l Update these source DNS entries with thecorresponding target IP address—For each IP address onthe source, specify what address you want DNS to use afterfailover. For clusters, be sure and select the clusteredIP address.

l Update TTL—Specify the length of time, in seconds, for thetime to live value for all modified DNS A records. Ideally, youshould specify 300 seconds (5minutes) or less.

If you selectRetain your target network configuration but donot enableUpdate DNS server, you will need to specify failoverscripts that update your DNS server during failover, or you canupdate the DNS server manually after failover. This would alsoapply to non--Microsoft Active Directory Integrated DNS servers.You will want to keep your target network configuration but do notupdate DNS. In this case, you will need to specify failover scriptsthat update your DNS server during failover, or you can update theDNS server manually after failover.

200

Mirror, Verify & Orphaned Files

l Mirror all files—All protected files will bemirrored from the source to thetarget.

l Mirror different files—Only those protected files that are different basedon date and time, size, or attributeswill bemirrored from the source to thetarget.

l Mirror only if the file on the source is newer than the copy onthe target—Only those protected files that are newer on the sourcearemirrored to the target.

If you are using a database application or are protecting adomain controller, do not use this option unless you know forcertain that you need it. With database applications andbecause domain controllers store their data in a database, itis critical that all files, not just some of the files that might benewer, get mirrored.

l Use block checksum for comparisons—For those files flaggedas different, themirroring process can perform a block checksumcomparison and send only those blocks that are different.

l Enable scheduled verification—Verification is the process of confirmingthat the source replica data on the target is identical to the original data onthe source. Verification creates a log file detailing what was verified aswellas which files are not synchronized. If the data is not the same, canautomatically initiate a remirror, if configured. The remirror ensures dataintegrity between the source and target. When this option is enabled,Double-Take will verify the source replica data on the target and generate averification log.

201

Because of the way theWindowsCacheManager handlesmemory, machines that are doingminimal or light processingmayhave file operations that remain in the cache until additionaloperations flush them out. Thismaymake Double-Take files on thetarget appear as if they are not synchronized.When theWindowsCacheManager releases the operations in the cache on the sourceand target, the files will be updated on the target.

l Verify on this interval—Specify the interval between verificationprocesses.

l Begin immediately—Select this option if you want to start theverification schedule immediately after the job is established.

l Begin at this time—Select this option if you want to start theverification at the specified date and time.

l Mirror files to the target server when verifying—When thisoption is enabled, in addition to verifying the data and generating alog, Double-Take will alsomirror to the target any protected files thatare different on the source.

l Mirror only if the file on the source is newer than thecopy on the target—Only those protected files that arenewer on the source aremirrored to the target.

If you are using a database application or areprotecting a domain controller, do not use this optionunless you know for certain that you need it. Withdatabase applications and because domain controllersstore their data in a database, it is critical that all files,not just some of the files that might be newer, getmirrored.

l Use block checksum for comparisons—For those filesflagged as different, themirroring process can perform a blockchecksum comparison and send only those blocks that aredifferent.

l Calculate size of protected data before mirroring—Specify if you wantDouble-Take to determine themirroring percentage calculation based onthe amount of data being protected. If the calculation is enabled, it iscompleted before the job startsmirroring, which can take a significantamount of time depending on the number of files and system performance.If your job contains a large number of files, for example, 250,000 or more,youmaywant to disable the calculation so that data will start beingmirroredsooner. Disabling calculation will result in themirror status not showing thepercentage complete or the number of bytes remaining to bemirrored.

202

The calculated amount of protected datamay be slightly off if yourdata set contains compressed or sparse files.

l Delete orphaned files—An orphaned file is a file that exists in the replicadata on the target, but does not exist in the protected data on the source.This option specifies if orphaned files should be deleted on the target duringamirror, verification, or restoration.

Orphaned file configuration is a per target configuration. All jobs tothe same target will have the same orphaned file configuration.

The orphaned file feature does not delete alternate data streams.To do this, use a full mirror, which will delete the additionalstream(s) when the file is re-created.

If delete orphaned files is enabled, carefully review any replicationrules that use wildcard definitions. If you have specified wildcards tobe excluded from protection, filesmatching those wildcardswill alsobe excluded from orphaned file processing and will not be deletedfrom the target. However, if you have specified wildcards to beincluded in your protection, those files that fall outside the wildcardinclusion rule will be considered orphaned files and will be deletedfrom the target.

If you want to move orphaned files rather than delete them, you canconfigure this option along with themove deleted files feature tomove your orphaned files to the specified deleted files directory.See Target server properties on page 100 for more information.

During a full mirror, orphaned file processing successmessageswillbe logged to a separate orphaned file log. This keeps the Double-Take log from being overrun with orphaned file success processingmessages. Orphaned files processing statistics and any errors inorphaned file processing will still be logged to the Double-Take log,and during differencemirrors, verifications, and restorations, allorphaned file processingmessages are logged to the Double-Takelog. The orphaned file log is located in the Logging folder specifiedfor the source. See Log file properties on page 106 for details on thelocation of that folder. The orphaned log file is overwritten duringeach orphaned file processing during a full mirror, and the log filewill be amaximumof 50MB.

203

Network Route

This section is not applicable if your target is a cluster.

l Send data to the target server using this route—Bydefault, Double-Take will select a target route for transmissions. If desired, specify analternate route on the target that the data will be transmitted through. Thisallows you to select a different route for Double-Take traffic. For example,you can separate regular network traffic and Double-Take traffic on amachine with multiple IP addresses.

The IP address used on the source will be determined through theWindows route table.

l Block target paths upon connection—You can blockwriting to thereplica source data located on the target. This keeps the data from beingchanged outside of Double-Take processing. Any target paths that areblocked will be unblocked automatically during the failover process so thatusers canmodify data after failover. During restoration, the paths areautomatically blocked again. If you failover and failbackwithout performinga restoration, the target pathswill remain unblocked.

204

Path Mapping

For theMappings, specify the location on the target where the replica of thesource data will be stored. By default, the replica source data will be stored in thesame directory structure on the target, in a one-to-one configuration. Make sureyou update this location if you are protectingmultiple sources or jobs to the sametarget. Double-Take offers two pre-defined locations aswell as a custom optionthat allows you to set your path.

l All To One—Click this button to set themapping so that the replica sourcedata will be stored on a single volume on the target. The pre-defined path is\source_name\volume_name. If you are protectingmultiple volumes on thesource, each volumewould be stored on the same volume on the target.For example, C:\data and D:\files for the source Alpha would be stored inD:\alpha\C and D:\alpha\D, respectively.

l One To One—Click this button to set themapping so that the replicasource data will be stored in the same directory structure on the target. Forexample, C:\data and D:\files on the source will be stored in C:\data andD:\files, respectively, on the target.

l Custom Location—If the pre-defined options do not store the data in alocation that is appropriate for your network operations, you can specifyyour own custom location where the replica source data will be stored. Clickthe Target Path and edit it, selecting the appropriate location.

If you are protecting dynamic volumes or mount points, your location onthe target must be able to accommodate the amount of data that may bestored on the source.

If you are protectingmultiple mount points, your directorymappingmustnot create a cycle or loop. For example, if you have the C: volumemounted at D:\C and the D: volumemounted at C:\D, this is a circularconfiguration. If you establish a job for either C:\D or D:\C, there will be acircular configuration and Double-Takemirroring will never complete.

If you are protecting sparse files and your location on the target is a non-NTFS 5 volume, the amount of disk space availablemust be equal to orgreater than the entire size of the sparse file. If the target location is anNTFS 5 volume, the amount of disk space availablemust be equal to orgreater than the on-disk size of the sparse file.

205

Failover Services

This section is not applicable to clustered environments.

Services to start on source and stop on target during failover and stopon source and start on target during failback—If necessary, you can startand stop services during failover and failback. ClickAdd to insert a service into thelist orRemove to remove a service from the list. The serviceswill be started in theorder they appear and stopped in the reverse order. Highlight a service and clickMove Up orMove Down to arrange the services in the desired order.

206

Snapshots


A snapshot is an image of the source replica data on the target taken at a singlepoint in time. You can view the snapshots in VSS and recover any files or foldersdesired. However, you cannot failover to a snapshot.

Turn onEnable scheduled snapshots if you want Double-Take to takesnapshots automatically at set intervals.

l Take snapshots on this interval—Specify the interval (in days, hours, orminutes) for taking snapshots.

l Begin immediately—Select this option if you want to start takingsnapshots immediately after the protection job is established.

l Begin at this time—Select this option if you want to start taking snapshotsstarting at a later date and time. Specify the date and time parameters toindicate when you want to start.

SeeManaging snapshots on page 170 for details on takingmanualsnapshots and deleting snapshots.

You should set the size limit on how much space snapshots can use. Seeyour VSS documentation for more details.

207

Compression

To help reduce the amount of bandwidth needed to transmit Double-Take data,compression allows you to compress data prior to transmitting it across thenetwork. In aWAN environment this provides optimal use of your networkresources. If compression is enabled, the data is compressed before it istransmitted from the source.When the target receives the compressed data, itdecompresses it and then writes it to disk. You can set the level fromMinimum toMaximum to suit your needs.

Keep inmind that the process of compressing data impacts processor usage onthe source. If you notice an impact on performance while compression is enabledin your environment, either adjust to a lower level of compression, or leavecompression disabled. Use the following guidelines to determine whether youshould enable compression.

l If data is being queued on the source at any time, consider enablingcompression.

l If the server CPU utilization is averaging over 85%, be cautious aboutenabling compression.

l The higher the level of compression, the higher the CPU utilization will be.l Do not enable compression if most of the data is inherently compressed.Many image (.jpg, .gif) andmedia (.wmv, .mp3, .mpg) files, for example, arealready compressed. Some images files, such as .bmp and .tif, areuncompressed, so enabling compression would be beneficial for thosetypes.

l Compressionmay improve performance even in high-bandwidthenvironments.

l Do not enable compression in conjunction with aWAN Accelerator. Useone or the other to compressDouble-Take data.

All jobs from a single source connected to the same IP address on a targetwill share the same compression configuration.

208

Bandwidth

Bandwidth limitations are available to restrict the amount of network bandwidthused for Double-Take data transmissions.When a bandwidth limit is specified,Double-Take never exceeds that allotted amount. The bandwidth not in use byDouble-Take is available for all other network traffic.

All jobs from a single source connected to the same IP address on a targetwill share the same bandwidth configuration.

l Do not limit bandwidth—Double-Take will transmit data using 100%bandwidth availability.

l Use a fixed limit—Double-Take will transmit data using a limited, fixedbandwidth. Select aPreset bandwidth limit rate from the commonbandwidth limit values. TheBandwidth field will automatically update to thebytes per second value for your selected bandwidth. This is themaximumamount of data that will be transmitted per second. If desired, modify thebandwidth using a bytes per second value. Theminimum limit should be3500 bytes per second.

l Use scheduled limits—Double-Take will transmit data using a dynamicbandwidth based on the schedule you configure. Bandwidth will not belimited during unscheduled times.

l New—ClickNew to create a new scheduled bandwidth limit. Specifythe following information.

l Daytime entry—Select this option if the start and end times ofthe bandwidth window occur in the same day (between 12:01AMandmidnight). The start timemust occur before the endtime.

l Overnight entry—Select this option if the bandwidth windowbegins on one day and continues past midnight into the nextday. The start timemust be later than the end time, for example6 PM to 6 AM.

209

l Day—Enter the day on which the bandwidth limiting shouldoccur. You can pick a specific day of the week,Weekdays tohave the limiting occur Monday through Friday,Weekends tohave the limiting occur Saturday and Sunday, or Every day tohave the limiting repeat on all days of the week.

l Start time—Enter the time to begin bandwidth limiting.l End time—Enter the time to end bandwidth limiting.l Preset bandwidth—Select a bandwidth limit rate from thecommon bandwidth limit values. TheBandwidth field willautomatically update to the bytes per second value for yourselect bandwidth.

l Bandwidth—If desired, modify the bandwidth using a bytesper second value. Theminimum limit should be 3500 bytes persecond.

l Edit—ClickEdit to modify an existing scheduled bandwidth limit.l Delete—ClickDelete to remove a scheduled bandwidth limit.

If you change your job option fromUse scheduled limits toDonot limit bandwidth orUse a fixed limit, any schedule that youcreated will be preserved. That schedule will be reused if youchange your job option back toUse scheduled limits.

You canmanually override a schedule after a job is established byselectingOther Job Options, Set Bandwidth. If you selectNobandwidth limit or Fixed bandwidth limit, that manual overridewill be used until you go back to your schedule by selectingOtherJob Options, Set Bandwidth, Scheduled bandwidth limit. Forexample, if your job is configured to use a daytime limit, you wouldbe limited during the day, but not at night. But if you override that,your override setting will continue both day and night, until you goback to your schedule. See theManaging and controlling jobssection for your job type for more information on theOther JobOptions.

210

Scripts

You can customizemirroring by running scripts on the target at pre-defined pointsin themirroring process. Scriptsmay contain any validWindows command,executable, or batch file. The scripts are processed using the same accountrunning the Double-Take service, unless you have identified a specific accountthrough the server's properties. SeeScript credentials on page 105. There arethree types of mirroring scripts.

l Mirror Start—This script starts when the target receives the first mirroroperation. In the case of a differencemirror, thismay be a long time after themirror is started because the script does not start until the first different datais received on the target. If the data is synchronized and a differencemirrorfinds nothing tomirror, the script will not be executed. Specify the full pathand name of theScript file.

l Mirror Complete—This script starts when amirror is completed. Becausethemirror statisticsmay indicate amirror is at 99-100%when it is actuallystill processing (for example, if files were added after the job size wascalculated, if there are alternate data streams, and so on), the script will notstart until all of themirror data has been completely processed on the target.Specify the full path and name of theScript file.

l Mirror Stop—This script starts when amirror is stopped, whichmay becaused by an auto-disconnect occurring while amirror is running, theservice is shutdownwhile amirror is running, or if you stop amirrormanually. Specify the full path and name of theScript file.

l Arguments—Specify a comma-separated list of valid arguments requiredto execute the script.

l Allow script to interact with desktop—Enable this option if you want thescript processing to be displayed on the screen. Otherwise, the script willexecute silently in the background.

211

l Delay until script completes—Enable this option if you want to delay themirroring process until the associated script has completed. If you select thisoption, make sure your script handles errors, otherwise themirroringprocessmay never complete if the process is waiting on a script that cannotcomplete.

l Test—You can test your script manually by clicking Test. Your script will beexecuted if you test it. If necessary, manually undo any changes that you donot want on your target after testing the script.

Mirror scripts are dependent on the target and the Target PathMappings specified under theNetwork Route & Folder Selectionsection. If you establishmirroring scripts for one job and then establishadditional jobs to the same target using the same target pathmapping, themirroring scripts will automatically be applied to those subsequent jobs. Ifyou select a different target pathmapping, themirroring scripts will have tobe reconfigured for the new job(s).


15. Double-Take validates that your source and target are compatible. TheSummarypage displays your options and validation items.

Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enableprotection. Depending on the error, youmay be able to clickFix or Fix All and letDouble-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correctthe error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.

Before a job is created, the results of the validation checks are logged to theDouble-TakeManagement Service log on the target.

16. Once your servers have passed validation and you are ready to establishprotection, clickFinish, and you will automatically be taken to theManage Jobspage.

212

Managing and controlling files and folders jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.

The jobs displayed in the right pane depend on the server group folder selected in the leftpane. Every job for each server in your console session is displayed when the Jobs onAll Servers group is selected. If you have created and populated server groups (seeManaging servers on page 76), then only the jobs associated with the server or targetservers in that server group will be displayed in the right pane.

l SeeOverview job information displayed in the top pane on page 213l SeeDetailed job information displayed in the bottom pane on page 216l See Job controls on page 218

Overview job information displayed in the top paneThe top pane displays high-level overview information about your jobs.

Column 1 (Blank)

The first blank column indicates the state of the job.

The job is in a healthy state.

The job is in a warning state. This icon is also displayed on anyserver groups that you have created that contain a job in a warningstate.

The job is in an error state. This icon is also displayed on any servergroups that you have created that contain a job in an error state.

The job is in an unknown state.

Job

The name of the job

Source Server

The name of the source. This could be a name or IP address of astandalone server, a cluster, or a node. Cluster jobswill be associatedwith the cluster name and standalone jobswill be associated with astandalone server or a cluster node.

213

Target Server

The name of the target. This could be a name or IP address of astandalone server, a cluster, or a node. Cluster jobswill be associatedwith the cluster name and standalone jobswill be associated with astandalone server or a cluster node.

Job Type

Each job type has a unique job type name. This job is a Files andFolders job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Activity

There aremany differentActivitymessages that keep you informed ofthe job activity. Most of the activitymessages are informational and donot require any administrator interaction. If you see error messages,check the job details. Keep inmind that Idle indicates console to serveractivity is idle, not that your servers are idle.

Mirror Status

l Calculating—The amount of data to bemirrored is beingcalculated.

l In Progress—Data is currently beingmirrored.l Waiting—Mirroring is complete, but data is still being written to thetarget.

l Idle—Data is not beingmirrored.l Paused—Mirroring has been paused.l Stopped—Mirroring has been stopped.l Removing Orphans—Orphan files on the target are beingremoved or deleted depending on the configuration.

l Verifying—Data is being verified between the source and target.l Restoring—Data is being restored from the target to the source.l Unknown—The console cannot determine the status.

Replication Status

l Replicating—Data is being replicated to the target.l Ready—There is no data to replicate.l Pending—Replication is pending.l Stopped—Replication has been stopped.l Out of Memory—Replicationmemory has been exhausted.l Failed—TheDouble-Take service is not receiving replicationoperations from the Double-Take driver. Check the Event Viewer fordriver related issues.

l Unknown—The console cannot determine the status.

214

Transmit Mode

l Active—Data is being transmitted to the target.l Paused—Data transmission has been paused.l Scheduled—Data transmission is waiting on schedule criteria.l Stopped—Data is not being transmitted to the target.l Error—There is a transmission error.l Unknown—The console cannot determine the status.

215

Detailed job information displayed in the bottom paneThe details displayed in the bottom pane of theManage Jobs page provide additionalinformation for the job highlighted in the top pane. If you select multiple jobs, the detailsfor the first selected job will be displayed.

Name

The name of the job

Target data state

l OK—The data on the target is in a good state.l Mirroring—The target is in themiddle of amirror process. The datawill not be in a good state until themirror is complete.

l Mirror Required—The data on the target is not in a good statebecause a remirror is required. Thismay be caused by anincomplete or stoppedmirror or an operationmay have beendropped on the target.

l Restore Required—The data on the source and target do notmatch because of a failover condition. Restore the data from thetarget back to the source. If you want to discard the changes on thetarget, you can remirror to resynchronize the source and target.

l Snapshot Reverted—The data on the source and target do notmatch because a snapshot has been applied on the target. Restorethe data from the target back to the source. If you want to discard thechanges on the target, you can remirror to resynchronize the sourceand target.

l Busy—The source is low onmemory causing a delay in getting thestate of the data on the target.

l Not Loaded—Double-Take target functionality is not loaded on thetarget server. Thismay be caused by an activation code error.


Mirror remaining

The total number of mirror bytes that are remaining to be sent from thesource to the target

Replication queue

The total number of replication bytes in the source queue

Disk queue

The amount of disk space being used to queue data on the source

216

Bytes sent

The total number of mirror and replication bytes that have beentransmitted to the target

Bytes sent (compressed)

The total number of compressedmirror and replication bytes that havebeen transmitted to the target. If compression is disabled, this statisticwill be the same asBytes sent.

Connected since

The date and time indicating when the current job wasmade. This fieldis blank, indicating that a TCP/IP socket is not present, when the job iswaiting on transmit options or if the transmission has been stopped.This field will maintain the date and time, indicating that a TCP/IPsocket is present, when transmission has been paused.

Recent activity

Displays themost recent activity for the selected job, along with an iconindicating the success or failure of the last initiated activity. Click the linkto see a list of recent activities for the selected job. You can highlight anactivity in the list to display additional details about the activity.

Additional information

Depending on the current state of your job, youmay see additionalinformation displayed to keep you informed about the progress andstatus of your job. If there is no additional information, you will see(None) displayed.

217

Job controlsYou can control your job through the toolbar buttons available on theManage jobspage. If you select multiple jobs, some of the controls will apply only to the first selectedjob, while others will apply to all of the selected jobs. For example,View Job Detailswillonly show details for the first selected job, whileStopwill stop protection for all of theselected jobs.

If you want to control just one job, you can also right click on that job and access thecontrols from the pop-upmenu.

Create a New Job

This button leaves theManage Jobs page and opens theGet Startedpage.

View Job Details

This button leaves theManage Jobs page and opens theView JobDetails page.

Delete

Stops (if running) and deletes the selected jobs.

Provide Credentials

Changes the login credentials for one or both servers in the selectedjob. This button opens the Provide Credentials dialog boxwhere youcan specify the new account information and which servers you want toupdate. SeeProviding server credentials on page 83. You will remainon theManage Jobs page after updating the server credentials.

View Recent Activity

Displays the recent activity list for the selected job. Highlight an activityin the list to display additional details about the activity.

Start

Starts or resumes the selected jobs.

If you have previously stopped protection, the job will restart mirroringand replication.

If you have previously paused protection, the job will continuemirroringand replication fromwhere it left off, as long as the Double-Take queue

218

was not exhausted during the time the job was paused. If the Double-Take queue was exhausted during the time the job was paused, the jobwill restart mirroring and replication.

Pause

Pauses the selected jobs. Data will be queued on the source while thejob is paused. Failover monitoring will continue while the job is paused.

Stop

Stops the selected jobs. The jobs remain available in the console, butthere will be nomirroring or replication data transmitted from the sourceto the target. Mirroring and replication data will not be queued on thesource while the job is stopped, requiring a remirror when the job isrestarted. The type of remirror will depend on your job settings. Failovermonitoring will continue while the job is stopped.

Take Snapshot

Even if you have scheduled the snapshot process, you can run itmanually any time. If an automatic or scheduled snapshot is currently inprogress, Double-Take will wait until that one is finished before takingthemanual snapshot.

Snapshots are not applicable to clustered environments.

Manage Snapshots

Allows you tomanage your snapshots by taking and deleting snapshotsfor the selected job. SeeManaging snapshots on page 170 for moreinformation.


Failover or Cutover

Starts the failover process. See Failing over files and folders jobs onpage 233 for the process and details of failing over a files and foldersjob.

Failback

Starts the failback process. See Failback and restoration for files andfolders jobs on page 234 for the process and details of failing back afiles and folders job.

219

Restore

Starts the restoration process. See Failback and restoration for filesand folders jobs on page 234 for the process and details of restoring afiles and folders job.

Reverse

Reverses protection. Reverse protection does not apply to files andfolders jobs.

Undo Failover

Cancels a test failover by undoing it. Undo failover does not apply tofiles and folders jobs.

View Job Log

Opens the job log. On the right-clickmenu, this option is calledViewLogs, and you have the option of opening the job log, source server log,or target server log. SeeViewing the log files through the Double-TakeConsole on page 705 for details on all three of these logs.

Other Job Actionsl Mirroring—You can start, stop, pause and resumemirroring for anyjob that is running.

When pausing amirror, Double-Take stops queuingmirror data onthe source but maintains a pointer to determine what information stillneeds to bemirrored to the target. Therefore, when resuming apausedmirror, the process continueswhere it left off.

When stopping amirror, Double-Take stops queuingmirror data onthe source and does not maintain a pointer to determine whatinformation still needs to bemirrored to the target. Therefore, whenstarting amirror that has been stopped, you will need to decide whattype of mirror to perform.

l Mirror all files—All protected files will bemirrored from thesource to the target.

l Mirror different files—Only those protected files that aredifferent based on date and time, size, or attributeswill bemirrored from the source to the target.

l Mirror only if the file on the source is newer thanthe copy on the target—Only those protected filesthat are newer on the source aremirrored to the target.

220

If you are using a database application or areprotecting a domain controller, do not use thisoption unless you know for certain that youneed it. With database applications andbecause domain controllers store their data in adatabase, it is critical that all files, not just someof the files that might be newer, get mirrored.

l Use block checksum for comparisons—For thosefiles flagged as different, themirroring process canperform a block checksum comparison and send onlythose blocks that are different.

l Calculate size of protected data before mirroring—Specify if you want Double-Take to determine themirroringpercentage calculation based on the amount of data beingprotected. If the calculation is enabled, it is completed beforethe job startsmirroring, which can take a significant amount oftime depending on the number of files and systemperformance. If your job contains a large number of files, forexample, 250,000 or more, youmaywant to disable thecalculation so that data will start beingmirrored sooner.Disabling calculation will result in themirror status not showingthe percentage complete or the number of bytes remaining tobemirrored.

The calculated amount of protected datamay beslightly off if your data set contains compressed orsparse files.

l Verify—Even if you have scheduled the verification process, youcan run it manually any time amirror is not in progress.

l Create verification report only—This option verifies thedata and generates a verification log, but it does not remirrorany files that are different on the source and target. SeeVerification log on page 107 for details on the log file.

l Mirror files to the target server automatically—When thisoption is enabled, in addition to verifying the data andgenerating a log, Double-Take will alsomirror to the target anyprotected files that are different on the source.


221



l Set Bandwidth—You canmanually override bandwidth limitingsettings configured for your job at any time.

l No bandwidth limit—Double-Take will transmit data using100% bandwidth availability.

l Fixed bandwidth limit—Double-Take will transmit datausing a limited, fixed bandwidth. Select aPreset bandwidthlimit rate from the common bandwidth limit values. TheBandwidth field will automatically update to the bytes persecond value for your selected bandwidth. This is themaximumamount of data that will be transmitted per second.If desired, modify the bandwidth using a bytes per secondvalue. Theminimum limit should be 3500 bytes per second.

l Scheduled bandwidth limit—If your job has a configuredscheduled bandwidth limit, you can enable that schedule withthis option.

l Delete Orphans—Even if you have enabled orphan file removalduring your mirror and verification processes, you canmanuallyremove them at any time.

l Target—You can pause the target, which queues any incomingDouble-Take data from the source on the target. All active jobs tothat target will complete the operations already in progress. Any newoperationswill be queued on the target until the target is resumed.The data will not be committed until the target is resumed. Pausingthe target only pausesDouble-Take processing, not the entireserver.

While the target is paused, the Double-Take target cannot queuedata indefinitely. If the target queue is filled, data will start to queueon the source. If the source queue is filled, Double-Take willautomatically disconnect the connections and attempt to reconnectthem.

If you havemultiple jobs to the same target, all jobs from the samesource will be paused and resumed.

222

l Update Shares—Windows share information is automaticallyupdated on the target once an hour. This option allows you tomanually update share information immediately when the option isselected. Shares are not applicable to environments where thetarget is a cluster.

Filter

Select a filter option from the drop-down list to only display certain jobs.You can displayHealthy jobs, Jobs with warnings, or Jobs witherrors. To clear the filter, selectAll jobs. If you have created andpopulated server groups, then the filter will only apply to the jobsassociated with the server or target servers in that server group. SeeManaging servers on page 76.

Type a server name

Displays only jobs that contain the text you entered. If you have createdand populated server groups, then only jobs that contain the text youentered associated with the server or target servers in that server groupwill be displayed. SeeManaging servers on page 76.

Overflow Chevron


223

Viewing files and folders job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.

Review the following table to understand the detailed information about your jobdisplayed on theView Job Details page.

Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Files andFolders job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Health


The job is in a warning state.

The job is in an error state.


Activity

There aremany differentActivitymessages that keep you informed ofthe job activity. Most of the activitymessages are informational and donot require any administrator interaction. If you see error messages,check the rest of the job details.

Connection ID

The incremental counter used to number jobs. The number isincremented when a job is created. It is also incremented by internalactions, such as an auto-disconnect and auto-reconnect. The lowestavailable number (as jobs are created, stopped, deleted, and so on) willalways be used. The counter is reset to one each time the Double-Takeservice is restarted.

Transmit Mode

l Active—Data is being transmitted to the target.l Paused—Data transmission has been paused.l Scheduled—Data transmission is waiting on schedule criteria.l Stopped—Data is not being transmitted to the target.

224

l Error—There is a transmission error.l Unknown—The console cannot determine the status.

Target data state








Target route

The IP address on the target used for Double-Take transmissions.

Compression

l On / Level—Data is compressed at the level specified.l Off—Data is not compressed.

Bandwidth limit

If bandwidth limiting has been set, this statistic identifies the limit. ThekeywordUnlimitedmeans there is no bandwidth limit set for the job.

Connected since


225



Mirror Status





Mirror percent complete

The percentage of themirror that has been completed

Mirror remaining


Mirror skipped

The total number of bytes that have been skipped when performing adifference or checksummirror. These bytes are skipped because thedata is not different on the source and target.

Replication Status



226

Replication queue


Disk queue


Bytes sent


Bytes sent compressed


227

Validating a files and folders jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.

1. From theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.

2. In the Tasks area on the right on theView Job Details page, clickValidate jobproperties.



Validation checks for an existing job are logged to the job log on the target server.See Log files on page 704 for details on the various log files.

4. Once your servers have passed validation, clickClose.

228

Editing a files and folders jobUse these instructions to edit a files and folders job.


2. In the Tasks area on the right on theView Job Details page, clickEdit jobproperties. (You will not be able to edit a job if you have removed the source ofthat job from your Double-Take Console session or if you only have Double-Takemonitor security access.)

3. You have the same options available for your files and folders job aswhen youcreated the job. SeeCreating a files and folders job on page 186 for details oneach job option.

Changing some optionsmay require Double-Take to automaticallydisconnect, reconnect, and remirror the job.

4. If you want to modify the workload items or replication rules for the job, clickEditworkload or replication rules. Modify theWorkload item you are protecting, ifdesired. Additionally, you canmodify the specificReplication Rules for your job.

Volumes and folders with a green highlight are included in their entirety in theprotection. Volumes and folders highlighted in light yellow have individual filesincluded in the protection. If there is no highlight, no part of the volume or folder isincluded in the protection. Tomodify the items selected, highlight a volume, folder,or file and clickAdd Rule. You can also enter a rule, including a wildcardspecification, manually. Specify if you want to Include or Exclude the item. Also,specify if you want the rule to be recursive, which indicates the rule shouldautomatically be applied to the subdirectories of the specified path. If you do notselectRecursive, the rule will not be applied to subdirectories.


ClickOK to return to theEdit Job Properties page.



Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enable

229

protection. Depending on the error, youmay be able to clickFix or Fix All and letDouble-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correctthe error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.


7. Once your servers have passed validation and you are ready to update your job,clickFinish.

230

Viewing a files and folders job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.

The following table identifies the controls and the table columns in the Job logswindow.

Start


Pause

This button pauses the addition and scrolling of new messages in thewindow. This is only for the Job logswindow. Themessages are stilllogged to their respective files on the server.

Copy

This button copies themessages selected in the Job logswindow totheWindows clipboard.

231

Clear

This button clears the Job logswindow. Themessages are not clearedfrom the respective files on the server. If you want to view all of themessages again, close and reopen the Job logswindow.

Time


Description


232

Failing over files and folders jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.

1. On theManage Jobs page, highlight the job that you want to failover and clickFailover or Cutover in the toolbar.

2. Select the type of failover to perform.l Failover to live data—Select this option to initiate a full, live failover usingthe current data on the target. The target will stand in for the source byassuming the network identity of the failed source. User and applicationrequests destined for the source server or its IP addresses are routed to thetarget.

l Perform test failover—This option is not available for files and foldersjobs.

l Failover to a snapshot—This option is not applicable to files and foldersjobs.

3. Select how you want to handle the data in the target queue. Youmaywant tocheck the amount of data in queue on the target by reviewing theStatistics onpage 715 or PerformanceMonitor on page 817.

l Apply data in target queues before failover or cutover—All of thedata in the target queue will be applied before failover begins. Theadvantage to this option is that all of the data that the target has received willbe applied before failover begins. The disadvantage to this option isdepending on the amount of data in queue, the amount of time to apply all ofthe data could be lengthy.

l Discard data in the target queues and failover or cutoverimmediately—All of the data in the target queue will be discarded andfailover will begin immediately. The advantage to this option is that failoverwill occur immediately. The disadvantage is that any data in the targetqueue will be lost.

4. When you are ready to begin failover, clickFailover.

IPv6 addresses on the source will be set to DHCP on the target afterfailover. Update them to static addressesmanually, if needed.

If your NICswere configured for network load balancing (NLB), you willhave to reconfigure that after failover.

233

Failback and restoration for files and folders jobsFailover occurred because the target wasmonitoring the source for a failure, and when afailure occurred, the target stood in for the source. User and application requests thatwere directed to the failed source are routed to the target.

While the users are accessing their data on the target, you can repair the issue(s) on thesource. Before users can access the source again, you will need to restore the data fromthe target back to the source and perform failback. Failback is the processwhere thetarget releases the source identity it assumed during failover. Once failback is complete,user and application requests are no longer routed to the target, but back to the source.

Ideally, you want to restore your data from the target back to the source before youfailback. This allows users who are currently accessing their data on the target becauseof failover to continue accessing their data. Restoration before failback reduces userdowntime. Another method, whichmay be easier in some environments that have strictIP addressing policies, allows you to failback first and then restore the data from thetarget to the source. A possible disadvantage to this process is that usersmayexperience longer downtime, depending on the amount of data to be restored, becausetheywill be unable to access their data during both the restoration and the failback.

l SeeRestoring then failing back files and folders jobs on page 235l See Failing back then restoring files and folders jobs on page 237

If you want to failback only, without performing a restoration, follow theinstructions for failing back then restoring and you will be able to skip therestoration process. Keep inmind that if you skip the restoration process, anydata changes that weremade on the target during failover will be lost.

234

Restoring then failing back files and folders jobsRestoring before failing back allows your users to continue accessing their data on thefailed over target, which is standing in for the source, while you perform the restorationprocess. The key to this process is to keep the users off of the source, but allow thesource and target to communicate to perform the restoration.

1. Remove the source from the network and fix the issue that caused your sourceserver to fail. Make sure in resolving the problems that you do not bring the sourceon the network at this time because the target currently has the source's identitybecause of failover.

2. Disable all of the IP addresses on the source that you failed over to the target.3. If you failed over all of your source IP addresses, change an existing IP address on

the source to a new, unique IP address that the target can access. If you insertedyour source server into the console using a private IP addresswhen you createdthe job, and you did not failover that private IP address, you can skip this step.

4. Bring the source onto the network using the IP address that the target can access.This will either be the new, unique IP address you just created or the private IPaddress you originally used when inserting the server into the console. You candisregard any identity conflict errors.

5. Stop any applications that may be running on the source. Filesmust be closed onthe source so that updated files from the target will overwrite the files on thesource.

6. If you had to create a new, unique IP address on the source, you will have toremove the original source in the console and add it back in using the new, uniqueIP address. Use a local account, not a domain account, that is amember of theDouble-Take Admin and Administrators groups. Complete this step on theManage Servers page. If you inserted your source server into the console using aprivate IP addresswhen you created the job, you can skip this step.

7. On theManage Jobs page, highlight the job and clickRestore.8. ConfirmRestore data is selected, then highlight your source server in the server

list. Look for the new, unique IP address or the private IP address in parenthesisafter the server name.

235

9. ClickContinue to start the restoration.

During the restoration, only the data is restored back to the source.Shares are not created on the source during the restoration. Shares thatwere created on the target during failover will need to be createdmanuallyon the source, if they do not already exist.

10. During the restoration process, theActivity andMirror Statuswill both indicateRestoring. When the restoration is complete, theMirror Statuswill change toIdle, however, theActivitywill remainRestoring because replication is still on-going. At this time, schedule a time for failback. User downtimewill begin oncefailback is started, so select a time that will haveminimal disruption on your users.

11. On theManage Jobs page, highlight the job and clickFailback.12. In the dialog box, highlight the job that you want to failback and clickFailback.13. After failback is complete, stop the restoration by clickingStop in the toolbar.14. After the restoration is stopped, enable the IP addresses on the source that you

disabled earlier. If desired, you can change the new, unique IP address back to itsoriginal address.

15. If you want to enable protection again, clickStart.

Depending on where you are running the console from, youmay need toadd the target back to the console after failback in order to see your job.

236

Failing back then restoring files and folders jobsFailback before restoration can be a simpler process, but it may require additionaldowntime. The amount of downtimewill depend on the amount of data to be restored.Usersmust be kept off of the source and target during this entire process.

1. Remove the source from the network and fix the issue that caused your sourceserver to fail. Make sure in resolving the problems that you do not bring the sourceon the network at this time because the target currently has the source's identitybecause of failover.

2. Schedule a time for the failback and restoration process. Select a time that willhaveminimal disruption on your users.

3. When you are ready to begin the failback process, prohibit user access to both thesource and target.

4. On theManage Jobs page, highlight the job and clickFailback.5. Highlight the job that you want to failback and clickFailback.6. Once failback is complete, theActivitywill indicateRestore Required. At this

time, bring the source onto the network. Make sure that end users continue to beprohibited from accessing both the source and target because the updated datafrom the target needs to be restored back to the source.

Depending on where you are running the console from, youmay need toadd the target back to the console after failback in order to see your job.

7. Stop any applications that may be running on the source. Filesmust be closed onthe source so that updated files from the target will overwrite the files on thesource.

8. On theManage Jobs page, highlight the job and clickRestore.

237

9. If you want to skip the restoration, selectDo not restore data, and clickContinue. Keep inmind that if you skip the restoration process, any data changesthat weremade on the target during failover will be lost. If you want to restore thechanged data from the target back to the source, selectRestore data, highlightyour source server in the server list, and clickContinue to start the restoration.

During the restoration, only the data is restored back to the source.Shares are not created on the source during the restoration. Shares thatwere created on the target during failover will need to be createdmanuallyon the source, if they do not already exist.

10. When the restoration is complete, theActivitywill indicateRestored. If youskipped the restoration, theActivitywill indicateMirror Required. At this point,stop the job by clickingStop.

11. After the job is stopped, you can allow users to access the source again.12. If you want to enable protection again, clickStart.

238

Chapter 8 Full server protectionThis section is specific to full server protection and includes the following topics.

l See Full server requirements on page 240—Full server protection includesspecific requirements for this type of protection.

l SeeCreating a full server job on page 244—This section includes step-by-stepinstructions for creating a full server job.

l SeeManaging and controlling full server jobs on page 269—You can view statusinformation about your full server jobs and learn how to control these jobs.

l See Failing over full server jobs on page 289—Use this section when a failovercondition has beenmet or if you want to failover manually.

l SeeReversing full server jobs on page 292—Use this section to reverseprotection. The source (what was your original target hardware) is now sendingdata to the target (what was your original source hardware).

239

Full server requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor full server protection.

l Operating system—The source and target servers can be any operating systemlisted in theCore Double-Take requirements on page 28. However, keep inmindthat a target server maymeet these requirements but may not be suitable tostand-in for a source in the event of a source failure. See Target compatibility onpage 242 for additional information regarding an appropriate target server for yourparticular source.

l Operating system language—Your serversmust be running the sameWindows localized version. For example, if your source is running an Englishlanguage version ofWindows, your target must also be running an Englishlanguage version ofWindows. If your source is running a Japanese languageversion ofWindows, your target must also be running a Japanese languageversion ofWindows. This applies to all localized languages.

l Source and target preparation—Uninstall any applications or operating systemfeatures that are not needed from both your source and target. For example,unused language packswill slow down failover since there are thousands of extrafiles that need to be examined.

l Storage Server Edition—If you are usingWindowsStorage Server Edition, youwill need to checkwith your NAS vendor to verify if there are technical or licenserestrictions on failing over an image of a server to different hardware.

l Microsoft Server Core 2008 R2—This operating system is only supported in aServer Core to Server Core configuration.

l Hyper-V servers—Full server protection of a Hyper-V server is not supported.l Network adapters—NIC teaming is not supported for full server protection.l Double-Take licensing—If you are protecting a full server in a physical source tovirtual target configuration, you will be unable to reverse if your virtual target has aDouble-Take Availability Virtual Guest Edition license. If you want to reverse, youwill need to have one of the other (non-virtual) Double-Take Availability licenses.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5 ServicePack 1 is required on the source and target. This version is not included in the.NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed,you will also need version 3.5.1. You can install this version from the Double-TakeCD, via a web connection during the Double-Take installation, or from a copy youhave obtainedmanually from theMicrosoft web site.


240




l Supported configurations—The following table identifies the supportedconfigurations for a full server job.





Many-to-one X

One-to-many X

Chained X

Single server X

Serverconfiguration2





Cluster Shared Volumes (CSV) guestlevel X

Cluster Shared Volumes (CSV) hostlevel X


Upgrade 5.2 Full Server FailoverManager connection to 6.0 Double-Take Console full server job

X

Upgrade 5.3 Double-Take Consolefull server failover job to 6.0 Double-Take Console full server job

X

1. If you are using a one-to-many configuration, you will only be able toconfigure reverse protection for the first job. Subsequent jobs from thatsource will have reverse protection disabled.

2. Full server protection of a cluster is not a default supported configuration,but it is possible with assistance fromProfessional Services. If you want touse a full server job in a cluster environment, contact Sales or ProfessionalServices. Because this is an advanced configuration, you will be referred toProfessional Services for further assistance.

3. When using a supported upgrade configuration, you can perform a rollingupgrade where you update the target server first. After the upgrade iscomplete, the source will automatically reconnect to the target. Upgrade thesource when convenient. However, after failover you will not be able to

241

reverse until the original source has been upgraded. For an upgradeconfiguration that is not supported, you will have to delete the existingconnection before the upgrade and create a new job after the upgrade.

Target compatibilityl Operating system version—The source and target must have the sameoperating system. For example, you cannot haveWindows 2003 on the sourceandWindows 2008 on the target. The two servers do not have to have the samelevel of service pack or hotfix. Windows 2003 and 2003 R2 are considered thesame operating system, however theWindows 2008 and 2008 R2 releases areconsidered different operating systems. Therefore, you can haveWindows 2003on the source andWindows 2003 R2 on the target, but you cannot haveWindows2008 on the source andWindows 2008 R2 on the target. TheWindows edition(Standard, Enterprise, and so on) does not have to be the same.

l Server role—The target cannot be a domain controller. Ideally, the target shouldnot host any functionality (file server, application server, and so on) because thefunctionality will be removed when failover occurs.

If your source is a domain controller, it will start in a non-authoritative restoremodeafter failover. Thismeans that if the source was communicating with other domaincontrollers before failover, it will require one of those domain controllers to bereachable after failover so it can request updates. If this communication is notavailable, the domain controller will not function after failover. If the source is theonly domain controller, this is not an issue.

Additionally, if your source is a domain controller, you will not be able to reverseprotection.

l Architecture—The source and the target must have the same architecture. Forexample, you cannot failover a 32-bit server to a 64-bit server.

l Processors—There are no limits on the number or speed of the processors, butthe source and the target should have at least the same number of processors. Ifthe target has fewer processors or slower speeds than the source, there will beperformance impacts for the users after failover.

l Memory—The target memory should be within 25% (plus or minus) of the source.If the target hasmuch lessmemory than the source, there will be performanceimpacts for the users after failover.

l Network adapters—Youmust map at least one NIC from the source to one NICon the target. If you have NICs on the source that are not being used, it is best todisable them. If the source hasmore NICs than the target, some of the sourceNICswill not bemapped to the target. Therefore, the IP addresses associatedwith those NICswill not be available after failover. If there aremore NICs on thetarget than the source, the additional NICswill still be available after failoverandwill retain their pre-failovernetwork settings.

l File system format—The source and the target must have the sameNTFS filesystem format on each server. FAT and FAT32 are no longer supported.

l Logical volumes—There are no limits to the number of logical volumes, althoughyou are bound by operating system limits. For each volume you are protecting on

242

the source, the target must have amatching volume. For example, if you areprotecting drivesC: and D: on the source, the target cannot have drivesD: and E:.In this case, the target must also have drivesC: and D:. Additional target volumesare preserved and available after failover, with all data still accessible.

l System path—The source and the target must have the same system path. Thesystem path includes the location of theWindows files, ProgramFiles, andDocuments and Settings.

l Disk space—The target must have enough space to store the data from thesource. This amount of disk space will depend on the applications and data filesyou are protecting. Themore data you are protecting, themore disk space you willneed.

The target must also have enough space to store, process, and apply the source'ssystem state data. If you will be enabling reverse protection, the sourcemust haveenough space to store, process, and apply the target's system state data. In eithercase, the size of the system state will depend on the operating system andarchitecture. Windows 2003 operating systems need at aminimum2-3GB of freespace for the system state. Windows 2008 operating systems need at aminimum7-9GB of free space for the system state. Windows 2008 R2 operating systemsneed 10GB of free space for the system state. Theseminimums are for a cleanoperating system installation. Operating system customizations, installedapplications, and user data will increase the disk space requirement.

243

Creating a full server jobUse these instructions to create a full server job.

1. Review these best practices before you create your job.l NIC configuration—If you are planning to failover the IP address of thesource to the target, use a separate NIC and separate network for aDouble-Take reserved IP address that will not be failed over. If you areunable to do that and just one NIC is used for both production and reservedIP addresses, disable DNS registration on the NIC.

l Windows 2003 servers—If your servers are runningWindows 2003 andyou have a separate, reserved NIC configuration, make sure that thereserved NIC address does not have a default gateway set. If your serversare runningWindows 2003 and you have a single NIC configuration, makethe Double-Take reserved IP address the primary IP address in the NICproperties on the source, otherwise, the failed over IP addressmay need tobe removed on the original source after failover to allow the reserved IPaddress to come online.

l Third machine setup—Ideally, you should use a third machine (not thesource or target) for configure protection, to failover, and to reverse. Thethird machinemust be able to communicate with the source and targetusing their reserved IP addresses.

l Double-Take Console—Insert your source and target servers into theconsole using the reserved IP addresses and a local computer account thatis amember of the Double-Take Admin and Administrators groups.




5. Choose your source server. This is the physical or virtual server that you want toprotect.

244




When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. If your source is the only domain controller in yournetwork, the account must also be a local account in the localadministrators group on the target. If you want Double-Take to updateDNS during failover, the account must be amember of the DomainAdmins group. If your security policies do not allow use of this group, seeDNS on page 844 and use the instructions under the Double-Take DFOutility to use a non-Domain Admins account.


7. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, select Full Server. In theWorkload items pane,

245

select the volumes on the source that you want to protect.


8. By default, Double-Take selects your entire source for protection. If desired, clicktheReplication Rules heading and expand the volumes under Folders. You willsee that Double-Take automatically excludes particular files that cannot be usedduring the protection. If desired, you can exclude other files that you do not want toprotect, but be careful when excluding data. Excluded volumes, folders, and/orfilesmay compromise the integrity of your installed applications. There are somevolumes, folders, and files (identified in italics text) that you will be unable toexclude, because they are required for protected. For example, the boot filescannot be excluded because that is where the system state information is stored.


If you need to remove a rule, highlight it in the list at the bottom and clickRemoveRule. Be careful when removing rules. Double-Takemay createmultiple rules

246

when you are adding directories. For example, if you add E:\Data to be included inprotection, then E:\ will be excluded. If you remove the E:\ exclusion rule, then theE:\Data rule will be removed also.

If IIS is being used as a hardware platformmanager by your hardwarevendor on both the source and target, you need to remove the INetPubdirectory from replication under theReplication Rules heading. If IIS isbeing used as a software application on your source but as a hardwareplatformmanager by your hardware vendor on your target, you need toadd the INetPub directory to theStaged Folders Options list on theSetOptions page later in this workflow.


10. Choose your target server. This is the server that will store the replica data fromthe source.



If you enter the target server's fully-qualified domain name, the Double-Take Console will resolve the entry to the server short name. If that short

247

name resides in two different domains, this could result in name resolutionissues. In this case, enter the IP address of the server.

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. If your source is the only domain controller in yournetwork, the account must also be a local account in the localadministrators group on the target. If you want Double-Take to updateDNS during failover, the account must be amember of the DomainAdmins group. If your security policies do not allow use of this group, seeDNS on page 844 and use the instructions under the Double-Take DFOutility to use a non-Domain Admins account.


12. You havemany options available for your full server job. Configure those optionsthat are applicable to your environment.


l General on page 249l Failover Monitor on page 250l Failover Options on page 252l Failover Identity on page 253l Creating a full server job on page 244l Network Adapter Options on page 257l Mirror, Verify & Orphaned Files on page 258l Staging Folder Options on page 261l Target Services on page 262l Snapshots on page 263l Compression on page 264l Bandwidth on page 265l Scripts on page 267

248

General


249

Failover Monitor






250











251

Failover Options


l Scripts—You can customize failover by running scripts on the target.Scriptsmay contain any validWindows command, executable, or batch file.The scripts are processed using the same account running the Double-Take service, unless you have identified a specific account through theserver's properties. SeeScript credentials on page 105. Examples offunctions specified in scripts include stopping services on the target beforefailover because theymay not be necessary while the target is standing infor the source, stopping services on the target that need to be restarted withthe source’smachine name and/or IP address, starting services or loadingapplications that are in an idle, standbymodewaiting for failover to occur,notifying the administrator before and after failover occurs, and so on. Thereare two types of failover scripts.




l Delay until script completes—Enable this option if you want todelay the failover process until the associated script has completed. Ifyou select this option, make sure your script handles errors,otherwise the failover processmay never complete if the process iswaiting on a script that cannot complete.


252

Failover Identity

l Apply source network configuration to the target—If you select thisoption, you can configure the source IP addresses to failover to the target. Ifyour target is on the same subnet as the source (typical of a LANenvironment), you should select this option.

If you are applying the source network configuration to the target inaWAN environement, do not failover your IP addresses unless youhave a VPN infrastructure so that the source and target can be onthe same subnet, in which case IP address failover will work thesame as a LAN configuration. If you do not have a VPN, you canautomatically reconfigure the routers via a failover script (bymovingthe source's subnet from the source's physical network to thetarget's physical network). There are a number of issues to considerwhen designing a solution that requires router configuration toachieve IP address failover. Since the route to the source's subnetwill be changed at failover, the source server must be the onlysystem on that subnet, which in turn requires all servercommunications to pass through a router. Additionally, it may takeseveral minutes or even hours for routing tables on other routersthroughout the network to converge.

l Retain target network configuration—If you select this option, the targetwill retain all of its original IP addresses. If your target is on a differentsubnet (typical of aWAN environment), you should select this option.

253





l Update these source DNS entries with thecorresponding target IP address—For each IP address onthe source, specify what address you want DNS to use afterfailover.



254

Reverse Protection

l Enable reverse protection—After failover, your target server is lost.Reverse protection allows you to store a copy of the target's system state onthe source server, so that the target server will not be lost. The reverseprocesswill bring the target identity back on the source hardware andestablish protection. After the reverse, the source (running on the originaltarget hardware) will be protected to the target (running on the originalsource hardware).

In a LAN environment, youmust have at least two IP addresses on eachserver in order to failover the production IP address and also reverse yourprotection. One (or more) will bemonitored and failed over and should bethe production IP address(es) that your users access. One IP address,called a reserved IP address, will be used for the reverse process and willnot failover or reverse, remaining with the server hardware. Ideally, thisreserved IP address should not be used for production communications.The reserved IP address can be on the same or a different subnet from yourproduction IP addresses, however if the subnet is different, it should be on adifferent network adapter.

The reserved IP addresseswill also be used to route Double-Take data.

l Select a reserved IP address on the source—Specify a reservedIP address on the source which will be used to permanently identifythe source server. The IP address you specify will not be failed overto the target in the event of a failure. This allows you to reverseprotection back to the source after a failover.

l Select a reserved IP address on the target—Specify a reservedIP address on the target which will be used to permanently identifythe target server. The IP address you specify will not be lost duringfailover. This allows you to reverse protection back to the source aftera failover.

When reverse protection is enabled, an image of the target'ssystem state ismirrored to the source server. Thismirror may causea performance impact on your source server. This impact is onlytemporary, and system performance will return to normal when the

255

reverse protectionmirror is complete. Tomaintain systemperformance on the source, the target's system state is notcontinuously replicated to the source. You canmanually update theimage of the target's system state by viewing the job details andclickingUpdate under Target Server Image. SeeViewing fullserver job details on page 280.

l Disable reverse protection—If you do not use reverse protection, after afailover, your target server will be lost. In order to continue protecting yourdata, you will have tomanually rebuild your original source and restartprotection, which can be a long and complicated process. Also, if youdisable reverse, you will lose the activated target license after failover. SeeDeactivating Double-Take licenses on page 69 for how you can save anddeactivate the target license.

l Send data to the target server using this route—Specify an IPaddress on the target to route Double-Take data. This allows you toselect a different route for Double-Take traffic. For example, you canseparate regular network traffic and Double-Take traffic on amachine with multiple IP addresses.

256

Network Adapter Options

ForMap source network adapters to target network adapters, specify howyou want the IP addresses associated with each NIC on the source to bemappedto a NIC on the target. Do not mix public and private networks. Also, if you haveenabled reverse protection, make sure that your NICswith your reserved IPaddresses aremapped to each other.

257




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for full server jobs.

l Use block checksum for comparisons—For those files flaggedas different, themirroring process can perform a block checksumcomparison and send only those blocks that are different. Make sureyou always enable this option for full server jobs.



258





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for full serverjobs.




Do not disable this option for full server jobs. The calculation time iswhen the system state protection processes hard links. If youdisable the calculation, the hard link processing will not occur andyoumay have problems after failover, especially if your source isWindows 2008.



259





260

Staging Folder Options

l Select additional folders from the source that need to be staged—Applications running on the target that cannot be stopped will cause retryoperations because Double-Take will be unable to write to open applicationfiles. In this case, you will want to mirror those application files to a staginglocation instead of their actual location. Generally, this will only apply toapplications that are not installed in theWindowsProgramFiles directory. Inthis case, clickAdd and specify the folder that you want staged. Any stagedfolders will be applied to their actual installation location during failover.

l Show system state and profile folders—This option displays the list ofessential system state and profile folders that will be staged automatically.These essential items are displayed in a lighter color than folders you havemanually added, and they cannot be removed from the list.

If IIS is being used as a software application on your source but as ahardware platformmanager by your hardware vendor on your target, youneed to add the INetPub directory to theStaged Folders Options list. IfIIS is being used as a hardware platformmanager by your hardwarevendor on both the source and target, you need to go to theChoose Datapage and remove the INetPub directory from replication under theReplication Rules heading.

261

Target Services

l Services to leave running on the target server during protection—Double-Take controls which services are running and stopped on the targetduring protection. You can specify which services you want to keep runningby clickingAdd and selecting a service from the list. If you want to remove aservice from the list, highlight it and clickRemove.

Services are stopped on the target to protect against retryoperations. Do not leave services running unless absolutelynecessary.

l Show essential services—This option displays the list of essentialservices that will remain running on the target. The essential services aredisplayed in a lighter color than services you havemanually added. Theessential services cannot be removed from the list.

262

Snapshots

A snapshot is an image of the source replica data on the target taken at a singlepoint in time. You can failover to a snapshot. However, you cannot access thesnapshot to recover specific files or folders.







263

Compression









264

Bandwidth









265







266

Scripts







267









268

Managing and controlling full server jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server

The name of the source. This could be the name or IP address of yoursource. In parenthesis will be the reserved IP address that youassigned to this server.

Target Server

The name of the target. This could be the name or IP address of yourtarget. In parenthesis will be the reserved IP address that you assigned

269

to this server.

Job Type

Each job type has a unique job type name. This job is a Full ServerFailover job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode

l Active—Data is being transmitted to the target.l Paused—Data transmission has been paused.l Scheduled—Data transmission is waiting on schedule criteria.

270

l Stopped—Data is not being transmitted to the target.l Error—There is a transmission error.l Unknown—The console cannot determine the status.

271


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


272

Bytes sent




Connected since


Recent activity




273



Create a New Job


View Job Details


Delete


Provide Credentials




Start




274


Pause


Stop


Take Snapshot


Manage Snapshots



Failover or Cutover

Starts the failover process. See Failing over full server jobs on page 289for the process and details of failing over a full server job.

Failback

Starts the failback process. Failback does not apply to full server jobs.

Restore

Starts the restoration process. Restore does not apply to full serverjobs.

275

Reverse

Reverses protection. The original source hardware will be reversed tothe target identity and the job will start mirroring in the reverse directionwith the job name and log file names changing accordingly. After themirror is complete, the job will continue running in the oppositedirection. SeeReversing full server jobs on page 292 for the processand details of reversing a full server job.

Undo Failover

Cancels a test failover by undoing it. Undo failover does not apply to fullserver jobs.

View Job Log







l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forfull server jobs, but ideally it should not be used.

l Use block checksum for comparisons—For thosefiles flagged as different, themirroring process canperform a block checksum comparison and send only

276

those blocks that are different. Make sure you alwaysenable this option for full server jobs.



Do not disable this option for full server jobs. Thecalculation time is when the system state protectionprocesses hard links. If you disable the calculation, thehard link processing will not occur and youmay haveproblems after failover, especially if your source isWindows 2008.




l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forfull server jobs, but ideally it should not be used.



277







If you have paused your target, failover will not start ifconfigured for automatic failover, and it cannot be initiated ifconfigured for manual intervention. Youmust resume thetarget before failover will automatically start or before youcanmanually start it.


l Update Shares—Shares are not applicable because they areautomatically included with the system state that is being protectedwith the entire server.

Filter

Select a filter option from the drop-down list to only display certain jobs.You can displayHealthy jobs, Jobs with warnings, or Jobs witherrors. To clear the filter, selectAll jobs. If you have created andpopulated server groups, then the filter will only apply to the jobs

278

associated with the server or target servers in that server group. SeeManaging servers on page 76.

Type a server name


Overflow Chevron


279

Viewing full server job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Full ServerFailover job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


280


Target data state








Target route


Compression


Bandwidth limit


Connected since


281



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



282

Replication queue


Disk queue


Bytes sent




Target Server Image

When a full server job is created with reverse protection enabled, animage of the target's system state is stored on the source server. Thisimage allows you to reverse your source and target after a failover. Toimprove performance, the target's system state is not continuouslyreplicated to the source. You canmanually update the image of thetarget's system state by clickingUpdate. This reverse protectionmirrormay cause a performance impact on your source server. This impact isonly temporary, and system performance will return to normal when thereverse protectionmirror is complete.

283

Validating a full server jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







284

Editing a full server jobUse these instructions to edit a full server job.



3. You will see the same options for your full server job aswhen you created the job,but you will not be able to edit all of them. If desired, edit those options that areconfigurable for an existing job. SeeCreating a full server job on page 244 fordetails on each job option.








Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of the

285

validation items to see details. Youmust correct any errors before you can enableprotection. Depending on the error, youmay be able to clickFix or Fix All and letDouble-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correctthe error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.



286

Viewing a full server job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


287

Clear


Time


Description


288

Failing over full server jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.

If you have paused your target, failover will not start if configured for automaticfailover, and it cannot be initiated if configured for manual intervention. Youmustresume the target before failover will automatically start or before you canmanually start it.


2. Select the type of failover to perform.l Failover to live data—Select this option to initiate a full, live failover usingthe current data on the target. The source is automatically shut down if it isstill running. Then the target will stand in for the source by rebooting andapplying the source identity, including its system state, on the target. Afterthe reboot, the target becomes the source, and the target no longer exists.

l Perform test failover—This option should only be used if your target is avirtual server. It is like live failover, except the source is not shutdown.Therefore you should isolate the virtual server from the network during thereboot process, otherwise, you will get conflict error messages after thereboot. (If you do not isolate the virtual server, you can ignore the conflictmessages.) Before selecting this option, you should take a snapshot of thevirtual server. After your test is complete, you will have to revert back to thesnapshot. If your target is a physical server, contact technical support if youwant to test failover, because you will have to rebuild your target systemvolume after the test.

l Failover to a snapshot—Select this option to initiate a full, live failoverwithout using the current data on the target. Instead, select a snapshot andthe data on the target will be reverted to that snapshot. This option will notbe available if there are no snapshots on the target or if the target does notsupport snapshots. This option is also not applicable to clusteredenvironments. To help you understand what snapshots are available, theType indicates the kind of snapshot.

l Scheduled—This snapshot was taken as part of a periodicsnapshot.

l Deferred—This snapshot was taken as part of a periodic snapshot,although it did not occur at the specified interval because the jobbetween the source and target was not in a good state

l Manual—This snapshot was takenmanually by a user.

289




l Revert to last good snapshot if target data state is bad—If the targetdata is in a bad state, Double-Take will automatically revert to the last goodDouble-Take snapshot before failover begins. If the target data is in a goodstate, Double-Take will not revert the target data. Instead, Double-Take willapply the data in the target queue and then failover. The advantage to thisoption is that good data on the target is guaranteed to be used. Thedisadvantage is that if the target data state is bad, you will lose any databetween the last good snapshot and the failure.



Youmay experience issues following a failover if an application or serveruses hard-linked files. For example, Windows 2008 Server Roles addedafter the job has been established will not function after failover becausethe hard links related to the server role were not replicated. After updatingserver roles, a remirror should be performed.

Some applications and hardware devices create and use softwaredeviceswithin the operating system, but they have the characteristics of ahardware device. For example, NIC teaming solutions are typicallyimplemented in the operating system, however they are still designed toemulate a single piece of storage hardware. In these cases, the device willnot be failed over because it appears to be a hardware device.

If your NICswere configured for network load balancing (NLB), you willhave to reconfigure that after failover.

Because theWindows product activation is dependent on hardware, youmay need to reactivate your Windows registration after failover. In mostcaseswhen you are usingWindows 2003, you can follow the on-screenprompts to complete the reactivation. However, when you are usingWindows 2008, the reactivation depends on several factors includingservice pack level, Windows edition, and your licensing type. If aWindows

290

2008 target comes online after failover with an activation failure, use thefollowing steps appropriate for your license type.

l Retail licensing—Retail licensing allows the activation of a singleoperating system installation.

1. Open theSystem applet inWindowsControl Panel.2. UnderWindows activation at the bottom of the page, click

Change product key.3. Enter your retail license key. Youmay need access to the

Internet or to call Microsoft to complete the activation.l MAK volume licensing—Multiple Activation Key (MAK) licensingallows the activation of multiple operating system installations using thesame activation key.

1. View or download theMicrosoft Volume Activation DeploymentGuide from theMicrosoft web site.

2. Using an administrative user account, open a command promptand follow the instructions from the deployment guide to activateMAK clients. Multiple rebootsmay be necessary before you canaccess a command prompt. Youmay need access to the Internetor to call Microsoft to complete the activation.

l KMS volume licensing—KeyManagement Service (KMS) licensingallows IT professionals to complete activations on their local networkwithout contactingMicrosoft.


2. Using an administrative user account, open a command promptand follow the instructions from the deployment guide to converta MAK activation client to a KMS client. Multiple rebootsmay benecessary before you can access a command prompt.

5. If you performed a test failover, revert your snapshot on the target, and thenrestart your job by clickingStart.

291

Reversing full server jobsAfter a full server failover, the source is running on your original target hardware andyour target no longer exists. That means the source and target hardware now share thesame identity, which is the source identity.

If you did not enable reverse protection, your source is a domain controller, or ifyou have to rebuild your source, you will have to reverse your protectionmanually. SeeReversing full server jobsmanually on page 294.

1. Fix the issue that caused your original source server to fail.2. Connect the original source server to the network. You can disregard any conflict

messages that you receive.3. On theManage Jobs page, highlight the job that you want to reverse. If the job is

not listed, youmay need to add your servers to your console again. Use thereserved IP addresses and local credentials.

4. Highlight the job you want to reverse and clickReverse in the toolbar. During thereverse process, you will see various states for the job. During theRestoringprocess, the target identity is being established on the original source hardware.During theSynchronizing process , protection is being established from thesource (on the original target hardware) to the target (on the original sourcehardware). The reverse protection is also established in the opposite direction.When the reverse process is complete, the target (on the original sourcehardware) will reboot. At this point, your source is still running on your originaltarget hardware with the source name, but the original source hardware now hasthe target identity.

5. To go back to your original hardware, highlight the job and clickFailover. Thesource identity will now be applied to the target (on the original source hardware),and the target identify will again be gone. Both servers will have the sourceidentity.

6. To bring back the target identify, highlight the job and clickReverse. The sameprocess as above will be repeated, but on the opposite servers. When the reverseis complete, you will be back to your original identities on the original hardware.

IPv6 addresses on the source will be set to DHCP on the target after failover.Update them to static addressesmanually, if needed.

Youmay experience issues following a failover if an application or server useshard-linked files. For example, Windows 2008 Server Roles added after the jobhas been established will not function after failover because the hard linksrelated to the server role were not replicated. After updating server roles, aremirror should be performed.

Some applications and hardware devices create and use software deviceswithin the operating system, but they have the characteristics of a hardware

292

device. For example, NIC teaming solutions are typically implemented in theoperating system, however they are still designed to emulate a single piece ofstorage hardware. In these cases, the device will not be failed over because itappears to be a hardware device.

If your NICswere configured for network load balancing (NLB), you will have toreconfigure that after failover.

Because theWindows product activation is dependent on hardware, youmayneed to reactivate your Windows registration after failover. In most caseswhenyou are usingWindows 2003, you can follow the on-screen prompts to completethe reactivation. However, when you are usingWindows 2008, the reactivationdepends on several factors including service pack level, Windows edition, andyour licensing type. If aWindows 2008 target comes online after failover with anactivation failure, use the following steps appropriate for your license type.

l Retail licensing—Retail licensing allows the activation of a single operatingsystem installation.

1. Open theSystem applet inWindowsControl Panel.2. UnderWindows activation at the bottom of the page, clickChange

product key.3. Enter your retail license key. Youmay need access to the Internet or to

call Microsoft to complete the activation.l MAK volume licensing—Multiple Activation Key (MAK) licensing allows theactivation of multiple operating system installations using the same activationkey.

1. View or download theMicrosoft Volume Activation Deployment Guidefrom theMicrosoft web site.

2. Using an administrative user account, open a command prompt andfollow the instructions from the deployment guide to activateMAKclients. Multiple rebootsmay be necessary before you can access acommand prompt. Youmay need access to the Internet or to callMicrosoft to complete the activation.

l KMS volume licensing—KeyManagement Service (KMS) licensing allowsIT professionals to complete activations on their local network withoutcontactingMicrosoft.

1. View or download theMicrosoft Volume Activation Deployment Guidefrom theMicrosoft web site.

2. Using an administrative user account, open a command prompt andfollow the instructions from the deployment guide to convert a MAKactivation client to a KMS client. Multiple rebootsmay be necessarybefore you can access a command prompt.

293

Reversing full server jobs manuallyIf you did not enable reverse protection, your source is a domain controller, or if you haveto rebuild your source, you have two options after a failover. You can continue runningfrom the failed over server indefinitely. This server is your source (running on the originaltarget hardware) and you can protect it to a new target. Your other option is to go back tothe original hardware.Without reverse protection, you have to complete this processmanually, which can be difficult.

Preparation of your original source hardware or a new server is key to thismanualprocess. The type of preparation required will depend on the role of the original sourceserver, the applications that were used on the original server, whether the original sourcewas a physical or virtual server, and the failure or event that occurred.

l Server role—If your original source was a domain controller, a Cluster Serviceserver, or a Certificate Service server, you will have to reinstall Windows. Theutility required to reuse a server cannot be used on these types of servers. Startwith 1A. Preparing a new server by reinstallingWindows on page 295 and thencontinue with the remaining instructions.

l Applications—If your original source was running a name-specific application,like Exchange, you should reinstall Windows. Start with 1A. Preparing a newserver by reinstallingWindows on page 295 and then continue with the remaininginstructions.

l Physical servers—If your original source was a physical server, your preparationmethod will depend on if you experienced a catastrophic or non-catastrophicfailure.

l Catastrophic failure—If your original hardware is unusable or the failurewill require you to reinstall Windows, start with 1A. Preparing a new serverby reinstallingWindows on page 295 and then continue with the remaininginstructions.

l Non-catastrophic failure—If the failure did not damage the server or theoperating system and you want to reuse the server, start with 1B. Reusingyour original source hardware on page 295 and then continue with theremaining instructions.

l Virtual servers—If your original source was a virtual server, you preparationmethod will depend on if you want to create a new virtual guest or reuse theexisting one.

l New virtual guest—If your original guest is unusable, start with 1A.Preparing a new server by reinstallingWindows on page 295 and thencontinue with the remaining instructions.

If possible, you can attach any virtual hard disks that survived thefailure event to a new virtual guest. Reusing any undamaged diskswill decrease the time required to restore data because you can usea differencemirror.

294

As an alternative tomanually creating a new virtual guest, you canlet Double-Take automatically provision (create) the new virtualguest for you. If you choose this option, you will need to use theinstructionsCreating a full server to ESX job on page 458 orCreating a full server to Hyper-V job on page 411 instead of theinstructions in this section.

l Reusing virtual guest—If the failure did not damage the virtual guest andyou want to reuse it, start with 1B. Reusing your original source hardwareon page 295 and then continue with the remaining instructions.

1A. Preparing a new server by reinstalling Windows1. Install or reinstall Windows on your physical or virtual server using unique,

temporary server information. See your Windows documentation for details oninstalling the operating system.

2. After the operating system installation is complete, install Double-Take using theactivation code from your original target. See Installing Double-Take Availabilityon aWindows server using the installation wizard on page 43.

3. After Double-Take is installed and activated, continue with 2. Mirroring andreplicating from the source to the original source hardware or new server andfailing over on page 296.

1B. Reusing your original source hardware1. Disconnect the original source hardware from the network. For a physical server,

youmaywant to disconnect the network cable. For a virtual server, remove it fromthe network using your virtual console. Youmust make sure the original source iscompletely disconnected before proceeding.

2. After the original source hardware is disconnected from the network, remove thetarget server identity fromActive Directory. You should remove the target'soriginal identity, not the identity of the source which the original target hardwarenow holds.

3. Keeping the original source hardware disconnected from the network, reboot itand login as the local administrator.

4. Stop all application services on the original source hardware and set them tomanual.

5. If you failed over the source IP address, create a new unique IP addresses. Seeyour Windows documentation for details onmodifying IP addresses.

6. Modify the original source hardware identity by placing the server into aworkgroup. Make sure you reboot when prompted, continuing to keep the serverdisconnected from the network. See your Windows documentation for details onplacing a server into a workgroup.

7. After the reboot, login as the local administrator.

295

8. Using the Double-Take Console, remove and reinsert the original source serverinto the server list on theManage Servers page.

9. Double-click on the server in the server list to view the server details page, andthen click on theEdit server properties link.

10. Under the Licensing section, enter the activation code from the original targetserver and clickAdd. If the original source server activation code is listed, removeit from theCurrent activation codes list. ClickOK to return to theManageServers page.

11. Run theMicrosoft Sysprep utility to modify SIDs (security identifiers) and theserver name. If desired, you can use the original target server namewhen theutility prompts for a server name. See theMicrosoft web site for details on theSysprep utility.

If the Sysprep utility does not force you to choose a new computer name,you will need to complete the following additional steps.

1. Finish the Sysprep process.

2. Reboot the server and login as the local administrator.

3. Rename the computer manually and reboot when prompted.

The server must be given a new name either via Sysprep or manually afterSysprep has completed before you can proceed.

12. Connect the server to the network and continue with 2. Mirroring and replicatingfrom the source to the original source hardware or new server and failing over onpage 296.

2. Mirroring and replicating from the source to the originalsource hardware or new server and failing over

1. Using the Double-Take Console, delete the original job from theManage Jobspage.

2. Establish full server protection from your source to the original source hardware ornew server. SeeCreating a full server job on page 244. In the console, specifyyour source (running on the original target hardware) on theChoose SourceServer page, and specify your original source hardware or new server that youbuilt or modified in step 1A or 1B above on theSelect Target Server page. Selectthe same data for protection and use the options that you used when protectingthe source initially, although you can select different settings for snapshots,compression, and so on.

3. Once you have established full server protection, data will bemirrored from thesource (on the original target hardware) to the target (on the original sourcehardware or your new server). Replication will keep the target up-to-date with the

296

changes end-users are continuing tomake on the source. Monitor the progress ofthe job. SeeManaging and controlling full server jobs on page 269.

4. Once themirror is complete, determine when you want to perform failover. Thiswill require downtime, typically between 15 and 30minutes depending on LAN orWAN configurations and server processing capabilities.

5. Using the Double-Take Console, perform failover using live data or a snapshot, asdesired. See Failing over full server jobs on page 289.

6. Monitor the progress. After the target reboots, the target will no longer exist, sinceit will become the source.

After the reboot, users and other servers can resume normal operations afterDNS/IP updates have been propagated to them.

If desired, you can re-establish protection again for this source so that you are preparedfor the next emergency.

If you want to reuse the same target hardware, you will have to remove thesource identity components from that server. You can use either method 1A.Preparing a new server by reinstallingWindows on page 295 or 1B. Reusingyour original source hardware on page 295 to prepare a new target.

297

Chapter 9 Exchange protectionThis section is specific to Exchange protection and includes the following topics.

l SeeExchange requirements on page 299—Exchange protection includes specificrequirements for this type of protection.

l SeeCreating an Exchange job on page 303—This section includes step-by-stepinstructions for creating a Exchange job.

l SeeManaging and controlling Exchange jobs on page 330—You can view statusinformation about your Exchange jobs and learn how to control these jobs.

l See Failing over Exchange jobs on page 350—Use this section when a failovercondition has beenmet or if you want to failover manually.

l Restoring then failing back Exchange jobs on page 353—Use this section whenyou are ready to restore and failback.

If your source is a domain controller, you should use one of the full serverprotectionmethods to protect the entire server because of complexities withauthentication. SeeSelecting a protection type on page 174.

298

Exchange requirementsIn addition to theCore Double-Take requirements on page 28, youmust alsomeet thefollowing requirements to protect Exchange.

l Exchange versions—Double-Take can protect Microsoft Exchange 2007 orExchange 2010. Exchange 2010must have Service Pack 1 or later.

l Exchange and network configuration—The following requirements andlimitations apply to your Exchange server and network configuration.

l All Microsoft best practices should be used for all versions of Exchange.l The version of Exchange on the source and target must be identical.l Exchange 2010must be running on a 64-bit server runningWindows 2008SP2 or later or Windows 2008 R2.

l Double-Take does not check the edition of Exchange 2007 (Enterprise orStandard). However, it is able to differentiate between service pack levels. Ifyou have Exchange 2007 Enterprise on the source and Exchange 2007Standard on the target, you will be limited to only failing over the number ofdatabases or storage groups supported by Exchange 2007 Standard. Seethe Exchange Server 2007 Editions and Client Access Licenses informationon theMicrosoft website.

l In a consolidated role environment only themailbox role is protected. TheHub Transport and Client Access roles are not protected or failed overbecause they are already installed on the target.

l For Exchange 2007 and 2010, replication and failover between a distributedrole source configuration to a consolidated role target configuration ispermitted as long as the sourceMailbox Server role is installed on astandalone server or cluster with the other roles residing on differentservers, and the target configuration is a standalone server with theMailbox, Hub Transport, and Client Access roles installed. In theseconfigurations, Double-Take will not replicate any data associated with theHub Transport/Client Access data, however, the target HubTransport/Client Access roles function properly when failing over the sourceMailbox role, allowing necessary operations to resume. For Exchange 2010with DAG (Database Availability Group), replication and failover from adistributed role source configurationmust be to a non-DAGdistributed roletarget configuration.

l For Exchange 2010 with DAG, the following requirements and limitationsalso apply.

l A DAG to standalone configuration is the only supportedconfiguration. Multi-site DAGs (DAG to DAGconfigurations) are notsupported.

l All mailbox storesmust be replicated to all other members of theDAG.

l During failover, Double-Take will update SPNs, move usermailboxes, and performActive Directory updates. DNS updates arenot made during failover, but can be scriptedmanually if needed.

299

http://www.microsoft.com/exchange/2007/evaluation/editions.mspx








l The Exchange program filesmust be installed in the same location on thesource and target.

l The drive letter(s) where Exchange stores its data on the sourcemust bethe same on the target.

l Single-label DNS domain names (those without a suffix such as .com,.corp, .net) are not supported.

l In environments where the FIPS security policy is enabled, youmust useimpersonation, which requires the following.

l The user running the Double-Take Consolemust have allappropriate rights to update the domain (that is, only impersonation issupported).

l Youmust manually verify DNS rights by running the DFOutility withthe /test parameter.

l If you are protecting Exchange 2007 and will only be protecting a subset ofthe storage groups, the storage groups you are protecting cannot have ahyphen followed by a space in the storage group name. You will either needto change the name of the storage group to remove the hyphen followed bythe space, or select all of your storage groups for protection.

l Microsoft Server Core is not supported.l The source and target serversmust be in the same root forest domain.l In a parent/child domain, at least one domain controller in the child domainmust be designated as a global catalog server.

l The target server cannot be a domain controller.l Exchange and a domain controller cannot be on the same node of a cluster.l The source and target serversmust be part of the same ExchangeAdministrative Group.

l The Exchange configurations on the source and target serversmust beidentical for the following components: storage groups, location of storagegroups (log and data files), log file prefixes, database locations (log and datafiles), Message Transfter Agent (MTA) location, and queue paths.

l If you are protecting Exchange in a 2008 R2 domain where the domainfunctional level is set to R2, youmust grant two levels of access to the localsystem account on the target. First, grant theAdminister informationstore control to the target in theConfiguration Naming Context in orderto move users during failover. Second, grant Full control to the target intheDomain Naming Context in order to move Service Principal Names,which will allow users to access their e-mail after a failover.

l Before you attempt to protect your Exchange application, youmaywant tocomplete the following tasks to verify that the environment is properly setup.

l With both Exchange servers online, useActive Directory Usersand Computers to move an existing user from the source to thetarget and then back to the original source.

l Verify that you can create a new user on the target.

300

l To verify connectivity, create anOutlook profile for the new user on aclient machine and connect to the target.

l If /domainprep has not been run in an Exchange 2007 environment,users will not be failed over and SPNswill not be updated duringfailover due to access denied errors. To fix this issue, run setup withthe /domainprep parameter in the environment.

l Supported configurations—The following table identifies the supportedconfigurations for an Exchange job.


Source totargetconfiguration



Many-to-one X

One-to-many X

Chained X

Single server X






Cluster Shared Volumes (CSV)guest level X

Cluster Shared Volumes (CSV)host level X


Upgrade 5.2 Double-TakeApplicationManager job to 6.0Double-Take ConsoleExchange job

X


X

1. When using a supported cluster configuration, the followinglimitations also apply.

301

l If you are using Exchange 2007, only themailbox role isprotected.

l Exchange and the domain controller cannot be on the samenode in the cluster.

l Exchangemust be installed in a unique group, not in the clustergroup.

2. For an upgrade configuration that is not supported, you will have todelete the existing job before the upgrade and create a new job afterthe upgrade.

302

Creating an Exchange jobUse these instructions to create an Exchange job.




4. Choose your source server. This is the physical or virtual server runningExchange. If your source is a cluster, select the cluster name, not the Exchangevirtual server name or virtual IP address. If you are protecting Exchange 2010 withDAG, select the DAGas your source server.




303

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. If desired, the user must alsomeet the followingcredentials requirements, however, you can specify a separate user laterin the job creation process to handle the Exchange specific tasks.

l The account must be an Exchange Full Administrator at theorganizational level, as delegated via the Exchange SystemManager atthe user level.

l The account must have rights to manage Exchange in order to queryandmodify the Exchange Active Directory objects.

l The account must be amember of the Domain Admins group. If yoursecurity policies do not allow use of this group, seeDNS on page 844and use the instructions under the Double-Take DFOutility to use anon-Domain Admins account.

l If Exchange is on a cluster, the account must be amember of theCluster Administrators security group on each node. Additionally, forWindows 2003 the same cluster service account should be used forboth the source and target.


6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, selectExchange Server. In theWorkload itemspane, Double-Take will automatically select the entire Exchange program anddata files.


304

7. If you want to select other files and folders to include in your protection, click theReplication Rules heading and expand the volumes under Folders. Forexample, if you need to protect data that is stored on a non-mailbox server role, forexample SMTP queue data, you will need to configure protection for that dataseparately.




9. Choose your target server. This is the server that will store the replicaExchange Server from the source.


305



When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. If desired, the user must alsomeet the followingcredentials requirements, however, you can specify a separate user laterin the job creation process to handle the Exchange specific tasks.

l The account must be an Exchange Full Administrator at theorganizational level, as delegated via the Exchange SystemManager atthe user level.

l The account must have rights to manage Exchange in order to queryandmodify the Exchange Active Directory objects.


l If Exchange is on a cluster, the account must be amember of theCluster Administrators security group on each node. Additionally, forWindows 2003 the same cluster service account should be used forboth the source and target.


306

11. You havemany options available for your Exchange job. Configure those optionsthat are applicable to your environment.


l General on page 308l Failover Monitor on page 309l Failover Options on page 313l Failover Identity on page 315l Mirror, Verify & Orphaned Files on page 317l Network Route on page 320l Failover Services on page 321l Snapshots on page 322l Compression on page 323l Bandwidth on page 324l Scripts on page 326l Test Failover Scripts on page 328l ExchangeOptions on page 329

307

General


308

Failover Monitor


Consider a shorter amount of time for servers, such as a web server ororder processing database, whichmust remain available and responsive atall times. Shorter times should be used where redundant interfaces andhigh-speed, reliable network links are available to prevent the falsedetection of failure. If the hardware does not support reliable

309

communications, shorter times can lead to premature failover. Consider alonger amount of time for machines on slower networks or on a server thatis not transaction critical. For example, failover would not be necessary inthe case of a server restart.













310



l Service monitoring—This option is only available in standaloneenvironments. It is not available in cluster environments.With this option, thetarget will monitor specific services on the source by confirming that they arerunning. Multiple services in the list will be checked in parallel. A failovercondition ismet when one of themonitored services fails the check. ClickAdd and select the service that you want to monitor. Repeat this step foradditional services that you want to monitor. If you want to remove a servicefrom theServices to monitor list, highlight it and clickRemove.

l Attempt to restart this service after each failure—When thisoption is enabled, if a service fails themonitor check, Double-Takewill attempt to restart it. During this restart period, Double-Take willnot check the other services, to avoid any false failures while the oneservice is attempting to be restarted. If the service cannot berestarted, Double-Take will consider this a failure.

l Custom script monitoring—This option is only available in standaloneenvironments. It is not available in cluster environments. With this option,you can use your own custom script to monitor the source for a failure. Youcan use any standard script such as PowerShell, VB, batch files, and so on.Your script must return a code of 0 upon success. Any other code willindicate a failure condition has beenmet. Your script will not be interactive,so ensure that it does not require any user interaction to executesuccessfully.

l Script file—Specify the full path and file name of your custom scriptfile.

l User name—Specify a user with privileges to execute your customscript and all commandswithin the script.

l Password—Specify the password associated with the user youhave entered.

l Domain—Specify the domain, if needed.

The networkmonitoring test is performed independently, while theservice and custommonitoring tests are performed in parallel.Therefore, if you are using networkmonitoring with service and/orcustommonitoring, and the networkmonitor fails, the service andcustommonitoring will be skipped. If the networkmonitor issuccessful, service or custommonitoring will be performed. Anyfailure between these two tests will be considered a failure,

311

therefore, both testsmust complete and pass for the test to beconsidered successful.

312

Failover Options


l Failover hostname—This option is not used for Exchange jobs. The jobwill automatically handle this functionality.

l Failback hostname—This option is not used for Exchange jobs. The jobwill automatically handle this functionality.

l Active Directory Credentials—This option is not used for Exchange jobs.The job will automatically handle this functionality.

l Scripts—You can customize failover and failback by running scripts on thesource and target. Scriptsmay contain any validWindows command,executable, or batch file. The scripts are processed using the same accountrunning the Double-Take service, unless you have identified a specificaccount through the server's properties. SeeScript credentials on page105. Examples of functions specified in scripts include stopping services onthe target before failover because theymay not be necessary while thetarget is standing in for the source, stopping services on the target that needto be restarted with the source’smachine name and/or IP address, startingservices or loading applications that are in an idle, standbymodewaiting forfailover to occur, notifying the administrator before and after failover orfailback occurs, stopping services on the target after failback because they

313

are no longer needed, stopping services on the target that need to berestarted with the target machine’s original name and/or IP address, and soon. There are four types of failover and failback scripts.








314

Failover Identity

This section is not applicable to DAG to standalone configurations.

l Retain target network configuration—The target will retain all of itsoriginal IP addresses.




315


l Update these source DNS entries with thecorresponding target IP address—For each IP address onthe source, specify what address you want DNS to use afterfailover. For clusters, be sure and select the clusteredIP address.



316








317










318


l Delete orphaned files—An orphaned file is a file that exists in the replicadata on the target, but does not exist in the protected data on the source.This option specifies if orphaned files should be deleted on the target duringamirror, verification, or restoration. In an Exchange environment, it isimportant that you delete orphaned files because if you have orphanedExchange log files on the target, it is possible that one or more Exchangedatabase will not mount after failover.






319

Network Route





320

Failover Services


Services to start on source and stop on target during failover and stopon source and start on target during failback—Double-Take automaticallydetermines the appropriate Exchange services to start and stop based on yourExchange version, Exchange configuration, and your operating system. Ifnecessary, you can start and stop other services during failover and failback. ClickAdd to insert a service into the list orRemove to remove a service from the list.The serviceswill be started in the order they appear and stopped in the reverseorder. Highlight a service and clickMove Up orMove Down to arrange theservices in the desired order.

321

Snapshots


A snapshot is an image of the source replica data on the target taken at a singlepoint in time. You can view the snapshots in VSS and recover any files or foldersdesired. You can also failover to a snapshot.







322

Compression









323

Bandwidth









324







325

Scripts







326




327

Test Failover Scripts


These scripts are like the live failover scripts, except they are only used during atest failover.

l Post-Failover Script—This script runs on the target at the end of thefailover process. Specify the full path and name of the script file.

l Pre-Failback Script—This script runs on the target at the beginning of thefailback process. Specify the full path and name of the script file.

Scripts will run but will not be displayed on the screen if the Double-Take service isnot set to interact with the desktop. Enable this option through theWindowsServices applet.

328

Exchange Options

ClickChange and specify a user that meets the following requirements.

l The login account must be an Exchange Full Administrator at theorganizational level, as delegated via the Exchange SystemManager atthe user level.

l The login account must have rights to manage Exchange in order toquery andmodify the Exchange Active Directory objects.

l If Exchange is on a cluster, the login account must be amember of theCluster Administrators security group on each node. Additionally, forWindows 2003 the same cluster service account should be used forboth the source and target.






329

Managing and controlling Exchange jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


330

Target Server


Job Type

Each job type has a unique job type name. This job is an ExchangeServer job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Activity


Mirror Status





Replication Status



331

Transmit Mode


332


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


333

Bytes sent




Connected since


Recent activity




334



Create a New Job


View Job Details


Delete


Provide Credentials




Start




335


Pause


Stop


Take Snapshot



Manage Snapshots



Failover or Cutover

Starts the failover process. See Failing over Exchange jobs on page350 for the process and details of failing over an Exchange job.

Failback

Starts the failback process. SeeRestoring then failing back Exchangejobs on page 353 for the process and details of failing back anExchange job.

336

Restore

Starts the restoration process. SeeRestoring then failing backExchange jobs on page 353 for the process and details of restoring anExchange job.

Reverse

Reverses protection. Reverse protection does not apply toExchange jobs.

Undo Failover

Cancels a test failover by undoing it. Undo failover does not apply toclustered jobs. See Failing over Exchange jobs on page 350 for detailson undoing a test failover.

View Job Log








337









338











l Update Shares—Shares are not applicable.

339

Filter


Type a server name


Overflow Chevron


340

Viewing Exchange job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is an ExchangeServer job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


341


Target data state








Target route


Compression


Bandwidth limit


Connected since


342



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



343

Replication queue


Disk queue


Bytes sent




344

Validating an Exchange jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







345

Editing an Exchange jobUse these instructions to edit an Exchange job.



3. You have the same options available for your Exchange job aswhen you createdthe job. SeeCreating an Exchange job on page 303 for details on each job option.








Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enableprotection. Depending on the error, youmay be able to clickFix or Fix All and let

346

Double-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correctthe error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.



347

Viewing an Exchange job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


348

Clear


Time


Description


349

Failing over Exchange jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.


2. Select the type of failover to perform.l Failover to live data—Select this option to initiate a full, live failover usingthe current data on the target. The application serviceswill be stopped onthe source (if it is online), and theywill be started on the target. DNS recordswill be updated, if applicable. Application requests destined for the sourceserver or its IP addresses are routed to the target.

l Perform test failover—Select this option to perform a test failover usingthe current data on the target for standalone environments. This option isnot applicable to clustered environments.This option will allow you toconfirm Exchange on the target is viable for failover. This processwill pausethe target (the entire target is not paused, just Double-Take replication),take a snapshot of the target (so that you can revert back to the pre-teststate after the test is complete), and then start the application services onthe target. Success and failuremessageswill be available in the job log.(Note the application services are still running on the source during the test,and not users aremoved during the test.) Once the application services arerunning on the target, you can perform any testing desired on the targetserver.

The following caveats apply to performing a test failover forExchange.

l Make sure you have enough space on your target tocontain the snapshot.

l If you have scheduled Double-Take snapshots, theywillcontinue to be created during the test, however, youshould not use any of these snapshots from this timeperiod because the target datamay not be in a goodstate.

l If you are usingWindows 2008 R2 and Double-Takesnapshots, any snapshots that you take before testingfailover will be unusable for an actual failover. To workaround this issue, take another snapshot immediatelyafter the test. Once the additional, post-testing snapshotis taken, all of the previous snapshots will be usable forfuture failovers. This issue is fixed in theWindows 2008R2 Service Pack 1 release. If you install that release, you

350

will not have to worry about the extra snapshot after thetest.

l If you have takenmultiple Double-Take snapshots on thetarget and then tested failover, in some instances theSMTPSVC servicemay not start after failing over to asnapshot. If possible, failover to a snapshot taken afterthe target data was tested. If that is not possible, you willhave to start the SMTPSVC servicemanually on thetarget after failover.




l Manual—This snapshot was takenmanually by a user.3. Select how you want to handle the data in the target queue. Youmaywant to

check the amount of data in queue on the target by reviewing theStatistics onpage 715 or PerformanceMonitor on page 817.




351

4. When you are ready to begin failover, clickFailover.5. If you performed a test failover, you can undo it by selectingUndo Failover in the

toolbar. The application serviceswill be stopped on the target, the pre-testsnapshot that was taken will be reverted, and the target will be resumed.

352

Restoring then failing back Exchange jobsRestoring before failing back allows your users to continue accessing their data on thefailed over target, which is standing in for the source, while you perform the restorationprocess. The key to this process is to keep the users off of the source, but allow thesource and target to communicate to perform the restoration.

1. Fix the issue that caused your source server to fail.2. Bring the source server online, if needed.

In a consolidated Exchange environment, youmay not be able to login tothe source while it is failed over using domain credentials.

3. On theManage Jobs page, highlight the job and clickRestore.

4. ConfirmRestore data is selected, then highlight your source server in the serverlist.

If you do not want to restore your data, you can selectDo not restoredata. Keep inmind, that any data changes that took place on the targetafter failover will be lost.

5. ClickContinue to start the restoration.

353

6. During the restoration process, theActivity andMirror Statuswill both indicateRestoring. When the restoration is complete, theMirror Statuswill change toIdle, and theActivitywill beRestored. At this time, schedule a time for failback.User downtimewill begin once failback is started, so select a time that will haveminimal disruption on your users.

7. On theManage Jobs page, highlight the job and clickFailback.8. In the dialog box, highlight the job that you want to failback and clickFailback.9. Check that your source is fully functional, and then, if desired, you can enable

protection again by clickingStart.

354

Chapter 10 SQL protectionThis section is specific to SQL protection and includes the following topics.

l SeeSQL requirements on page 356—SQL protection includes specificrequirements for this type of protection.

l SeeCreating a SQL job on page 359—This section includes step-by-stepinstructions for creating a SQL job.

l SeeManaging and controlling SQL jobs on page 384—You can view statusinformation about your SQL jobs and learn how to control these jobs.

l See Failing over SQL jobs on page 404—Use this section when a failovercondition has beenmet or if you want to failover manually.

l Restoring then failing back SQL jobs on page 406—Use this section when you areready to restore and failback.

If your source is a domain controller, you should use one of the full serverprotectionmethods to protect the entire server as a best practice. SeeSelectinga protection type on page 174.

355

SQL requirementsIn addition to theCore Double-Take requirements on page 28, youmust alsomeet thefollowing requirements to protect SQL.

l SQL versions—Double-Take can protect Microsoft SQL Server or Express2005, 2008, 2008 R2, or 2012.

l SQL and network configuration—The following requirements and limitationsapply to your SQL server and network configuration.

l All Microsoft best practices should be used for all versions of SQL.l You should use the same version, service pack, and architecture (32-bit or64-bit) of SQL Server on both the source and target servers.

l If you are using SQL 2008 R2, cluster to cluster configurations aresupported, however, the AlwaysOn cluster feature is not supported.

l If you are using SQL Express 2008, you will need to enable and start theSQL Browser Service. By default, this service is set to disabled.Additionally, you will need to enable TCP/IP to accept remote connections.To do this, launch the SQL Server ConfigurationManager. ExpandSQLServer Network Configuration, and under Protocols enable TCP/IP.

l If you are using SQL Express 2005, you will need to enable named pipesand TCP/IP to accept remote connections. To do this, launch the SQLServer ConfigurationManager. ExpandSQL Server 2005 NetworkConfiguration, and under ProtocolsenableNamed Pipes and TCP/IP.

l The SQL program filesmust be installed in the same location on the sourceand target.

l The drive letter(s) where SQL stores its data on the sourcemust be thesame on the target.

l The source and target serversmust have named instanceswith the samename installed prior to configuring protection.

l Single-label DNS domain names (those without a suffix such as .com,.corp, .net) are not supported.

l In environments where the FIPS security policy is enabled, youmust useimpersonation, which requires the following.

l The user running the Double-Take Consolemust have allappropriate rights to update the domain (that is, only impersonation issupported).

l Youmust manually verify DNS rights by running the DFOutility withthe /test parameter.

l Microsoft Server Core is not supported.l If your source and target are in a domain, they should be in the samedomain. If they are not, the SQL Server service on both the source andtarget serversmust be configured to start with the same domain useraccount.

l If your source and target are in a workgroup, make sure the source server'sNIC does not register the IP addresseswith DNS.

356

l If you are using SQL 2005 or later and are using a domain service accountthat is not in the domain or local Administrators security group, thereplicated databaseswill not mount on the target after failover or on thesource after restore because of security restrictions at the file system level.You need to place the SQL 2005 service account in the local Administratorsgroup on the source and target because of the way these versions of uselocal groups for NTFS permissions.

l Youmaywant to exclude the tempdb database to reducemirroring andreplication traffic.

l Transparent Data Encryption (TDE) is supported for SQL 2008, howeverthe SQL servicemust be running with the same service account on thesource and target.

l You should use a domain user account as theWindowsService Account forSQL. See Setting UpWindowsService Accounts on theMicrosoft web sitefor more information. You should include this account in the localAdministrators group on your source and target to ensure that theappropriate permissions for the replicated databases and log files will beavailable after failover and failback.

l Double-Take does not support a SQL default instance that is using non-default ports.

l Supported configurations—The following table identifies the supportedconfigurations for a SQL job.


Source totargetconfiguration



Many-to-one X

One-to-many X

Chained X

Single server X

357

http://msdn.microsoft.com/en-us/library/ms143504.aspx






Serverconfiguration









X


X

1. For an upgrade configuration that is not supported, you will have todelete the existing job before the upgrade and create a new job afterthe upgrade.

358

Creating a SQL jobUse these instructions to create a SQL job.




4. Choose your source server. This is the physical or virtual server runningSQL Server. If your source is a cluster, select the cluster name, not the SQL virtualserver name or virtual IP address.




359

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. Additionally, the user must meet the followingcredentials requirements.

l The account must be assigned the sysadmin role on the SQL server inorder to query and administer SQL, and the SQL service startupaccount should be a domain account.



6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, selectSQL Server. In theWorkload items pane,Double-Take will automatically select the entire SQL program and data files. Ifdesired, you can exclude user databases from protection, but the systemdatabases (except for tempdb) are required and cannot be excluded.


7. If you want to select other files and folders to include in your protection, click theReplication Rules heading and expand the volumes under Folders.

Volumes and folders with a green highlight are included in their entirety in theprotection. Volumes and folders highlighted in light yellow have individual files

360

included in the protection. If there is no highlight, no part of the volume or folder isincluded in the protection. Tomodify the items selected, highlight a volume, folder,or file and clickAdd Rule. You can also enter a rule, including a wildcardspecification, manually. Specify if you want to Include or Exclude the item. Also,specify if you want the rule to be recursive, which indicates the rule shouldautomatically be applied to the subdirectories of the specified path. If you do notselectRecursive, the rule will not be applied to subdirectories.



9. Choose your target server. This is the server that will store the replica SQL Serverfrom the source.



If you enter the target server's fully-qualified domain name, the Double-Take Console will resolve the entry to the server short name. If that short

361

name resides in two different domains, this could result in name resolutionissues. In this case, enter the IP address of the server.

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. Additionally, the user must meet the followingcredentials requirements.

l The account must be assigned the sysadmin role on the SQL server inorder to query and administer SQL, and the SQL service startupaccount should be a domain account.



11. You havemany options available for your SQL job. Configure those options thatare applicable to your environment.


l General on page 363l Failover Monitor on page 364l Failover Options on page 368l Failover Identity on page 370l Mirror, Verify & Orphaned Files on page 372l Network Route on page 375l Failover Services on page 376l Snapshots on page 377l Compression on page 378l Bandwidth on page 379l Scripts on page 381l Test Failover Scripts on page 383

362

General


363

Failover Monitor


Consider a shorter amount of time for servers, such as a web server ororder processing database, whichmust remain available and responsive atall times. Shorter times should be used where redundant interfaces andhigh-speed, reliable network links are available to prevent the false

364

detection of failure. If the hardware does not support reliablecommunications, shorter times can lead to premature failover. Consider alonger amount of time for machines on slower networks or on a server thatis not transaction critical. For example, failover would not be necessary inthe case of a server restart.













365



l Service monitoring—This option is only available in standaloneenvironments. It is not available for clustered source servers. With thisoption, the target will monitor specific services on the source by confirmingthat they are running. Multiple services in the list will be checked in parallel.A failover condition ismet when one of themonitored services fails thecheck. ClickAdd and select the service that you want to monitor. Repeatthis step for additional services that you want to monitor. If you want toremove a service from theServices to monitor list, highlight it and clickRemove.

l Attempt to restart this service after each failure—When thisoption is enabled, if a service fails themonitor check, Double-Takewill attempt to restart it. During this restart period, Double-Take willnot check the other services, to avoid any false failures while the oneservice is attempting to be restarted. If the service cannot berestarted, Double-Take will consider this a failure.

l Custom script monitoring—This option is only available in standaloneenvironments. It is not available for clustered source servers. With thisoption, you can use your own custom script to monitor the source for afailure. You can use any standard script such as PowerShell, VB, batchfiles, and so on. Your script must return a code of 0 upon success. Any othercode will indicate a failure condition has beenmet. Your script will not beinteractive, so ensure that it does not require any user interaction to executesuccessfully.

l Script file—Specify the full path and file name of your custom scriptfile.

l User name—Specify a user with privileges to execute your customscript and all commandswithin the script.

l Password—Specify the password associated with the user youhave entered.

l Domain—Specify the domain, if needed.

The networkmonitoring test is performed independently, while theservice and custommonitoring tests are performed in parallel.Therefore, if you are using networkmonitoring with service and/orcustommonitoring, and the networkmonitor fails, the service andcustommonitoring will be skipped. If the networkmonitor issuccessful, service or custommonitoring will be performed. Any

366

failure between these two tests will be considered a failure,therefore, both testsmust complete and pass for the test to beconsidered successful.

367

Failover Options


l Failover hostname—This option is not used for SQL jobs. The job willautomatically handle this functionality.

l Failback hostname—This option is not used for SQL jobs. The job willautomatically handle this functionality.

l Active Directory Credentials—This option is not used for SQL jobs. Thejob will automatically handle this functionality.

l Scripts—You can customize failover and failback by running scripts on thesource and target. Scriptsmay contain any validWindows command,executable, or batch file. The scripts are processed using the same accountrunning the Double-Take service, unless you have identified a specificaccount through the server's properties. SeeScript credentials on page105. Examples of functions specified in scripts include stopping services onthe target before failover because theymay not be necessary while thetarget is standing in for the source, stopping services on the target that needto be restarted with the source’smachine name and/or IP address, startingservices or loading applications that are in an idle, standbymodewaiting forfailover to occur, notifying the administrator before and after failover orfailback occurs, stopping services on the target after failback because they

368

are no longer needed, stopping services on the target that need to berestarted with the target machine’s original name and/or IP address, and soon. There are four types of failover and failback scripts.








369

Failover Identity

l Retain target network configuration—The target will retain all of itsoriginal IP addresses.





l Update these source DNS entries with thecorresponding target IP address—For each IP address on

370

the source, specify what address you want DNS to use afterfailover. For clusters, be sure and select the clusteredIP address.



371








372










373








374

Network Route





375

Failover Services


Services to start on source and stop on target during failover and stopon source and start on target during failback—Double-Take automaticallydetermines the appropriate SQL services to start and stop based on your SQLversion, SQL configuration, and your operating system. If necessary, you can startand stop other services during failover and failback. ClickAdd to insert a serviceinto the list orRemove to remove a service from the list. The serviceswill bestarted in the order they appear and stopped in the reverse order. Highlight aservice and clickMove Up orMove Down to arrange the services in the desiredorder.

376

Snapshots


A snapshot is an image of the source replica data on the target taken at a singlepoint in time. You can view the snapshots in VSS and recover any files or foldersdesired. You can also failover to a snapshot.







377

Compression









378

Bandwidth









379







380

Scripts







381




382

Test Failover Scripts


These scripts are like the live failover scripts, except they are only used during atest failover.

l Post-Failover Script—This script runs on the target at the end of thefailover process. Specify the full path and name of the script file.

l Pre-Failback Script—This script runs on the target at the beginning of thefailback process. Specify the full path and name of the script file.

Scripts will run but will not be displayed on the screen if the Double-Take service isnot set to interact with the desktop. Enable this option through theWindowsServices applet.






383

Managing and controlling SQL jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


384

Target Server


Job Type

Each job type has a unique job type name. This job is a SQL Server job.For a complete list of all job type names, press F1 to view the Double-Take Console online help.

Activity


Mirror Status





Replication Status



385

Transmit Mode


386


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


387

Bytes sent




Connected since


Recent activity




388



Create a New Job


View Job Details


Delete


Provide Credentials




Start




389


Pause


Stop


Take Snapshot



Manage Snapshots



Failover or Cutover

Starts the failover process. See Failing over SQL jobs on page 404 forthe process and details of failing over a SQL job.

Failback

Starts the failback process. SeeRestoring then failing back SQL jobson page 406 for the process and details of failing back a SQL job.

Restore

Starts the restoration process. SeeRestoring then failing back SQLjobs on page 406 for the process and details of restoring a SQL job.

390

Reverse

Reverses protection. Reverse protection does not apply to SQL jobs.

Undo Failover

Cancels a test failover by undoing it. Undo failover does not apply toclustered jobs. See Failing over SQL jobs on page 404 for details onundoing a test failover.

View Job Log








If you are using a database application or areprotecting a domain controller, do not use thisoption unless you know for certain that youneed it. With database applications andbecause domain controllers store their data in a

391

database, it is critical that all files, not just someof the files that might be newer, get mirrored.








If you are using a database application or areprotecting a domain controller, do not use thisoption unless you know for certain that youneed it. With database applications andbecause domain controllers store their data in a

392

database, it is critical that all files, not just someof the files that might be newer, get mirrored.










l Update Shares—Shares are not applicable.

Filter

Select a filter option from the drop-down list to only display certain jobs.You can displayHealthy jobs, Jobs with warnings, or Jobs with

393

errors. To clear the filter, selectAll jobs. If you have created andpopulated server groups, then the filter will only apply to the jobsassociated with the server or target servers in that server group. SeeManaging servers on page 76.

Type a server name


Overflow Chevron


394

Viewing SQL job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a SQL Server job.For a complete list of all job type names, press F1 to view the Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


395


Target data state








Target route


Compression


Bandwidth limit


Connected since


396



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



397

Replication queue


Disk queue


Bytes sent




398

Validating a SQL jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







399

Editing a SQL jobUse these instructions to edit a SQL job.



3. You have the same options available for your SQL job aswhen you created thejob. SeeCreating a SQL job on page 359 for details on each job option.








Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enableprotection. Depending on the error, youmay be able to clickFix or Fix All and let

400

Double-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correctthe error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.



401

Viewing a SQL job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


402

Clear


Time


Description


403

Failing over SQL jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.


2. Select the type of failover to perform.l Failover to live data—Select this option to initiate a full, live failover usingthe current data on the target. The application serviceswill be stopped onthe source (if it is online), and theywill be started on the target. DNS recordswill be updated, if applicable. Application requests destined for the sourceserver or its IP addresses are routed to the target.

l Perform test failover—Select this option to perform a test failover usingthe current data on the target for standalone environments. This option isnot applicable to clustered environments.This option will allow you toconfirm SQL on the target is viable for failover. This processwill pause thetarget (the entire target is not paused, just Double-Take replication), take asnapshot of the target (so that you can revert back to the pre-test state afterthe test is complete), and then start the application services on the target.Success and failuremessageswill be available in the job log. (Note theapplication services are still running on the source during the test.) Once theapplication services are running on the target, you can perform any testingdesired on the target server.

The following caveats apply to performing a test failover for SQL.l Make sure you have enough space on your target tocontain the snapshot.

l If you have scheduled Double-Take snapshots, theywillcontinue to be created during the test, however, youshould not use any of these snapshots from this timeperiod because the target datamay not be in a goodstate.

l If you are usingWindows 2008 R2 and Double-Takesnapshots, any snapshots that you take before testingfailover will be unusable for an actual failover. To workaround this issue, take another snapshot immediatelyafter the test. Once the additional, post-testing snapshotis taken, all of the previous snapshots will be usable forfuture failovers. This issue is fixed in theWindows 2008R2 Service Pack 1 release. If you install that release, youwill not have to worry about the extra snapshot after thetest.

404









4. When you are ready to begin failover, clickFailover.5. If you performed a test failover, you can undo it by selectingUndo Failover in the

toolbar. The application serviceswill be stopped on the target, the pre-testsnapshot that was taken will be reverted, and the target will be resumed.

405

Restoring then failing back SQL jobsRestoring before failing back allows your users to continue accessing their data on thefailed over target, which is standing in for the source, while you perform the restorationprocess. The key to this process is to keep the users off of the source, but allow thesource and target to communicate to perform the restoration.

1. Fix the issue that caused your source server to fail.2. Bring the source server online, if needed.3. On theManage Jobs page, highlight the job and clickRestore.

4. ConfirmRestore data is selected, then highlight your source server in the serverlist.

If you do not want to restore your data, you can selectDo not restoredata. Keep inmind, that any data changes that took place on the targetafter failover will be lost.

5. ClickContinue to start the restoration.6. During the restoration process, theActivity andMirror Statuswill both indicate

Restoring. When the restoration is complete, theMirror Statuswill change toIdle, and theActivitywill beRestored. At this time, schedule a time for failback.User downtimewill begin once failback is started, so select a time that will haveminimal disruption on your users.

406

7. On theManage Jobs page, highlight the job and clickFailback.8. In the dialog box, highlight the job that you want to failback and clickFailback.9. Check that your source is fully functional, and then, if desired, you can enable

protection again by clickingStart.

407

Chapter 11 Full server to Hyper-V protectionThis section is specific to full server to Hyper-V protection and includes the followingtopics.

l See Full server to Hyper-V requirements on page 409—Full server to Hyper-Vprotection includes specific requirements for this type of protection.

l SeeCreating a full server to Hyper-V job on page 411—This section includesstep-by-step instructions for creating a full server to Hyper-V job.

l SeeManaging and controlling full server to Hyper-V jobs on page 432—You canview status information about your full server to Hyper-V jobs and learn how tocontrol these jobs.

l See Failing over full server to Hyper-V jobs on page 451—Use this section when afailover condition has beenmet or if you want to failover manually.

408

Full server to Hyper-V requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor full server to Hyper-V protection.

l Source server—The source server can be any physical or virtual server runningany of the operating systems listed in theCore Double-Take requirements onpage 28. However, if you are using aWindows 2003 operating system, youmusthave Service Pack 2 which is required for Hyper-V Integration Services.

l Target server—The target server can be anyWindows 2008 or 2008 R2operating system from theCore Double-Take requirements on page 28 that hasthe Hyper-V role enabled. In addition, you can use Hyper-V Server 2008 R2 orServer Core 2008 R2with the Hyper-V role enabled. (Hyper-V Server 2008 andServer Core 2008 are not supported.)

l Disk types—Virtual machines cannot use raw, pass-through, or differencingdisks.



l Supported configurations—The following table identifies the supportedconfigurations for a full server to Hyper-V job.





Many-to-one X

One-to-many X

Chained X

Single server X

409











Cluster Shared Volumes (CSV) hostlevel X


Upgrade 5.2 physical or virtual serverto Hyper-V connection to 6.0 fullserver to Hyper-V job

X

Upgrade 5.3 P/V to Hyper-V job to6.0 full server to Hyper-V job X

1. SeeSupported configurations on page 16 for details on each of the sourceto target configurations.

2. Supported cluster configurations can be used to protect a node, sharedstorage, or a virtual machine, however, there is no cluster resource orcluster-awarenesswith this configuration.

3. When upgrading from version 5.2, you can keep your existing job, but youwill need to upgrade to version 5.3 first, then upgrade to version 6.0. If youwant to upgrade directly to version 6.0, you will have to delete your job andre-create it. When upgrading from version 5.3, you can perform a rollingupgrade where you update the target server first. After the upgrade iscomplete, the source will automatically reconnect to the target. At this point,the job will be an unmanaged job that you can delete or failover. No otherjob controls will be available. Once you upgrade you source, the job will befully controllable.

410

Creating a full server to Hyper-V jobUse these instructions to create a full server to Hyper-V job.








When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator security

411

groups on the source. The user must also have administrative rights forMicrosoft Hyper-V.

Your source can have nomore than four NICs enabled.


6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, select Full Server to Hyper-V or ESX. In theWorkload items pane, select the volumes on the source that you want to protect.


7. By default, Double-Take selects the system volume for protection. You will beunable to deselect the system volume. Select any other volumes on the sourcethat you want to protect. If desired, click theReplication Rules heading andexpand the volumes under Folders. You will see that Double-Take automaticallyexcludes particular files that cannot be used during the protection. If desired, youcan exclude other files that you do not want to protect, but be careful whenexcluding data. Excluded volumes, folders, and/or filesmay compromise theintegrity of your installed applications. There are some volumes, folders, and files(identified in italics text) that you will be unable to exclude, because they arerequired for protected. For example, the boot files cannot be excluded becausethat is where the system state information is stored.

412




9. Choose your target server. This is the Hyper-V server that will store the replica ofthe virtual machine from the source.



413


When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source. The user must also have administrative rights forMicrosoft Hyper-V.


11. You havemany options available for your full server to Hyper-V job. Configurethose options that are applicable to your environment.


l General on page 415l Failover Monitor on page 416l Failover Options on page 418l Replica Virtual Machine Location on page 419l Replica Virtual Machine Configuration on page 420l Replica Virtual Machine Volumes on page 421l Replica Virtual Machine Network Settings on page 422l Mirror, Verify & Orphaned Files on page 423l Network Route on page 426l Snapshots on page 427l Compression on page 428l Bandwidth on page 429

414

General


415

Failover Monitor






416











417

Failover Options


418

Replica Virtual Machine Location

l Select the volume and folder on the target server that will hold thereplica virtual machine—Select one of the volumes from the list toindicate the volume on the target where you want to store the new virtualserver when it is created. The target volumemust have enough FreeSpace to store the source data.

l Full path where the replica virtual machine will be stored—Specify alocation on the selectedVolume to store the replica of the source. Byspecifying an existing folder, you can reuse an existing virtual machine onyour Hyper-V target created by a previous protection job. This can be usefulfor pre-staging data on a virtual machine over a LAN connection and thenrelocating it to a remote site after the initial mirror is complete. You save timeby skipping the virtual disk creation steps and performing a differencemirrorinstead of a full mirror. In order to use a pre-existing virtual disk, it must be avalid virtual disk and it cannot be attached to any registered virtual machine.In aWAN environment, youmaywant to take advantage of re-using anexisting virtual disk by using a process similar to the following.

a. Create a protection job in a LAN environment, letting Double-Takecreate the virtual disk for you.

b. Complete themirror process locally.c. Delete the protection job and when prompted, select to keep the

replica.

d. From the Hyper-V Manager, delete the replica virtual machine, whichwill delete the virtual machine configuration but will keep theassociated .vhd files.

e. Shut down andmove the Hyper-V target server to your remote site.f. After the Hyper-V target server is back online at the remote site,

create a new protection job for the same source server. Double-Takewill reuse the existing .vhd files and perform a differencemirror overtheWAN to bring the virtual machine up-to-date.

419

Replica Virtual Machine Configuration

l Replica virtual machine display name—Specify the name of the replicavirtual machine. This will be the display name of the virtual machine on thehost system.

l Number of processors—Specify how many processors to create on thenew virtual machine. The number of processors on the source is displayedto guide you inmaking an appropriate selection. If you select fewerprocessors than the source, your clientsmay be impacted by slowerresponses. Themaximumnumber of processors on a host is four.

l Amount of memory—Specify the amount of memory, in MB, to create onthe new virtual machine. Thememory on the source is displayed to guideyou inmaking an appropriate selection. If you select lessmemory than thesource, your clientsmay be impacted by slower responses.

l Map source virtual switches to target virtual switches—Identify howyou want to handle the networkmapping after failover. TheSourceNetwork Adapter column lists the NICs from the source. Map each one toa Target Network Adapter, which is a virtual network on the target.

420

Replica Virtual Machine Volumes

l Replica Disk Size—For each volume you are protecting, specify the sizeof the replica disk on the target. Be sure and include the value inMB or GBfor the disk. The valuemust be at least the size of the specifiedUsed Spaceon that volume.

In some cases, the replica virtual machinemay usemore virtual diskspace than the size of the source volume due to differences in howthe virtual disk's block size is formatted and how hard links arehandled. To avoid this issue, specify the size of your replica to be atleast 20MB larger.

l Replica Disk Format—For each volume you are protecting, specify theformat of the disk,Dynamic or Fixed, that will be created on the replicavirtual machine. Any disk format specification will be discarded if you arereusing a disk from the Full path where the replica virtual machine willbe stored from theReplica Virtual Machine Location section.

l Storage Controller—For each volume you are protecting, specify the typeof Storage Controller that you want to use for each volume on the target.

The system volumemust be an IDE controller. In addition, up to twomore volumes can be attached to an IDE controller. If you areprotectingmore than three volumes on the source, you will need toinstall the Hyper-V Integration Components to acquire a SCSIdevice. See your Hyper-V documentation for more information.

If your source isWindows 2003 or Windows 2008 with no servicepacks and you have selected a SCSI controller, you will need tomanually install the Hyper-V Integration Components after failoverto attach these volumes to the replica virtual machine.

421

Replica Virtual Machine Network Settings

l Use advanced settings for replica virtual machine networkconfiguration—This option allows you to configure advanced networksettings, which are primarily for WAN support.

l Source network adapter—Select a network adapter on the source andspecify the Target IP addresses,Default Gateways, andDNS Serveraddresses to be used after failover. If you addmultiple gateways or DNSservers, you can sort them by using theMove Up andMove Down buttons.Repeat this step for each network adapter on the source.

Updatesmade during failover will be based on the network adapternamewhen protection is established. If you change that name, youwill need to delete the job and re-create it so the new namewill beused during failover.

If you update one of the advanced settings (IP address, gateway, orDNS server), then youmust update all of them. Otherwise, theremaining itemswill be left blank. If you do not specify any of theadvanced settings, the replica virtual machine will be assigned thesame network configuration as the source.

422




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for full server to Hyper-Vjobs.




423





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for full serverto Hyper-V jobs.




Do not disable this option for full server to Hyper-V jobs. Thecalculation time is when the system state protection processes hardlinks. If you disable the calculation, the hard link processing will notoccur and youmay have problems after failover, especially if yoursource isWindows 2008.



424





425

Network Route

For Send data to the target server using this route, Double-Take will select,by default, a target route for transmissions. If desired, specify an alternate route onthe target that the data will be transmitted through. This allows you to select adifferent route for Double-Take traffic. For example, you can separate regularnetwork traffic and Double-Take traffic on amachine with multiple IP addresses.


426

Snapshots








427

Compression









428

Bandwidth









429









Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enableprotection. Depending on the error, youmay be able to clickFix or Fix All and letDouble-Take correct the problem for you. For those errors that Double-Takecannot correct automatically, you will need tomodify the source or target to correct

430

the error, or you can select a different target. Youmust revalidate the selectedservers, by clickingRecheck, until the validation check passeswithout errors.



431

Managing and controlling full server to Hyper-V jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server

The name of the source. This could be the name or IP address of yoursource.

Target Server

The name of the target. This could be the name or IP address of yourtarget.

432

Job Type

Each job type has a unique job type name. This job is a Full Server toHyper-V job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode


433


434


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


435

Bytes sent




Connected since


Recent activity




436



Create a New Job


View Job Details


Delete


If you no longer want to protect the source and no longer need thereplica of the source on the target, select to delete the associatedreplica virtual machine. Selecting this option will remove the job andcompletely delete the replica virtual machine on the target.

If you no longer want to mirror and replicate data from the source to thetarget but still want to keep the replica of the source on the target, selectto keep the associated replica virtual machine. Youmaywant to use thisoption to relocate the virtual hard disks and create a new job betweenthe original source and the new location. Selecting this option, willpreserve the source replica on the target.

Provide Credentials


437



Start



If you have previously paused protection, the job will continuemirroringand replication fromwhere it left off, as long as the Double-Take queuewas not exhausted during the time the job was paused. If the Double-Take queue was exhausted during the time the job was paused, the jobwill restart mirroring and replication.

Pause


Stop


Take Snapshot


Manage Snapshots


Failover or Cutover

Starts the failover process. See Failing over full server to Hyper-V jobson page 451 for the process and details of failing over a full server to

438

Hyper-V job.

Failback

Starts the failback process. Failback does not apply to full server toHyper-V jobs.

Restore

Starts the restoration process. Restore does not apply to full server toHyper-V jobs.

Reverse

Reverses protection. Reverse protection does not apply to full server toHyper-V jobs.

Undo Failover

Cancels a test failover by undoing it. This resets the servers and the jobback to their original state. See Failing over full server to Hyper-V jobson page 451 for the process and details of undoing a failed over fullserver to Hyper-V job.

View Job Log






439


l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forfull server to Hyper-V jobs, but ideally it should not beused.




Do not disable this option for full server to Hyper-Vjobs. The calculation time is when the system stateprotection processes hard links. If you disable thecalculation, the hard link processing will not occur andyoumay have problems after failover, especially ifyour source isWindows 2008.




440

l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forfull server to Hyper-V jobs, but ideally it should not beused.











441

Filter


Type a server name


Overflow Chevron


442

Viewing full server to Hyper-V job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Full Server toHyper-V job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


443


Target data state








Target route


Compression


Bandwidth limit


Connected since


444



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



445

Replication queue


Disk queue


Bytes sent




446

Validating a full server to Hyper-V jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







447

Editing a full server to Hyper-V jobUse these instructions to edit a full server to Hyper-V job.



3. You will see the same options available for your full server to Hyper-V job aswhenyou created the job, but you will not be able to edit all of them. If desired, edit thoseoptions that are configurable for an existing job. SeeCreating a full server toHyper-V job on page 411 for details on each job option.







448

Viewing a full server to Hyper-V job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


449

Clear


Time


Description


450

Failing over full server to Hyper-V jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.


2. Select the type of failover to perform.l Failover to live data—Select this option to initiate a full, live failover usingthe current data on the target. This option will shutdown the sourcemachine(if it is online), stop the protection job, and start the replica virtual machineon the target with full network connectivity.

l Perform test failover—Select this option to perform a test failover usingthe current data on the target. This option will leave the sourcemachineonline, suspend the protection job, and start the replica virtual machine onthe target without network connectivity.








451



Because theWindows product activation is dependent on hardware, youmay need to reactivate your Windows registration after failover. In mostcaseswhen you are usingWindows 2003, you can follow the on-screenprompts to complete the reactivation. However, when you are usingWindows 2008, the reactivation depends on several factors includingservice pack level, Windows edition, and your licensing type. If aWindows2008 target comes online after failover with an activation failure, use thefollowing steps appropriate for your license type.










Once failover has occurred, if you add CPUs to the replica of the sourceon the target, youmay have to reboot the replica before the operatingsystemwill recognize the additional CPUs.

452

5. If you performed a test failover, you can undo it by selectingUndo Failover in thetoolbar. The replica virtual machine on the target will be shut down and theprotection job will be restarted performing a file differencesmirror.

6. There is no reverse or failback once you have failed over. If you need to go back toyour original hardware, delete the job and re-create a new one if your originalsource was a virtual server. If your original source was a physical server, you willneed to use a full server job.

453

Chapter 12 Full server to ESX protectionThis section is specific to full server to ESX protection and includes the following topics.

l See Full server to ESX requirements on page 455—Full server to ESX protectionincludes specific requirements for this type of protection.

l SeeCreating a full server to ESX job on page 458—This section includes step-by-step instructions for creating a full server to ESX job.

l SeeManaging and controlling full server to ESX jobs on page 482—You can viewstatus information about your full server to ESX jobs and learn how to controlthese jobs.

l See Failing over full server to ESX jobs on page 501—Use this section when afailover condition has beenmet or if you want to failover manually.

454

Full server to ESX requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor full server to ESX protection.

l Source server—The source server can be any physical server running any of theoperating systems listed in theCore Double-Take requirements on page 28. Thesource server must have Double-Take installed and licensed on it.

l ESX server—The ESX server that will host your target can be any of thefollowing operating systems. Note that ESX is commonly referred to as the Classicedition and ESXi as the Embedded and Installable edition.

l ESX 4.0.x or 4.1 Standard, Advanced, Enterprise, or Enterprise Plusl ESXi 4.0.x or 4.1 Standard, Advanced, Enterprise, or Enterprise Plusl ESXi 5.0 Standard, Advanced, Enterprise, or Enterprise Plus

If you are using the Standard edition of ESX 4.0 or ESXi 4.0, youmust have update 1 or later.

If your source is aWindows 2008 R2 server, your ESX server musthave ESX 4.0 update 1 or later.

l vCenter—Although vCenter is not required, if you are using it, then youmust useversion 4.1 or later.

VMotion is only supported if you are using vCenter.

l Virtual recovery appliance—The ESX server must have an existing virtualmachine, known as a virtual recovery appliance, that meets the followingrequirements. (When you establish protection, the virtual recovery appliance willcreate a new virtual server, mount disks, format disks, and so on. If failover occurs,the new virtual machine is detached from the virtual recovery appliance andpowered on. Once the new virtual machine is online, it will have the identity, data,and system state of the source. Since the virtual recovery appliancemaintains itsown identity, it can be reused for additional failovers.)

l Operating system—The virtual recovery appliance can be any of theoperating systems listed in theCore Double-Take requirements on page28.

l Operating system version—The virtual recovery appliancemust havethe same or newer operating system than the source (not including servicepack level).

l Operating system installation location—Because VMware boots fromthe first bootable volume that is discovered, the operating systemmust beinstalled to SCSI device 0, Slot 0 on the virtual recovery appliance.

455

l Double-Take—The virtual recovery appliancemust have Double-Takeinstalled and licensed on it.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5Service Pack 1 is required on the virtual recovery appliance. This version isnot included in the .NET version 4.0 release. Therefore, even if you have.NET version 4.0 installed, you will also need version 3.5.1. You can installthis version from the Double-Take CD, via a web connection during theDouble-Take installation, or from a copy you have obtainedmanually fromtheMicrosoft web site.

l Snapshots—Do not take snapshots of the virtual recovery appliance,because theywill interfere with proper failover.

l Disk controller—VMware Paravirtual SCSI Controllers are not supported.

l Domain controllers—If your source is a domain controller, it will start in a non-authoritative restoremode after failover. Thismeans that if the source wascommunicating with other domain controllers before failover, it will require one ofthose domain controllers to be reachable after failover so it can request updates. Ifthis communication is not available, the domain controller will not function afterfailover. If the source is the only domain controller, this is not an issue.

l Supported configurations—The following table identifies the supportedconfigurations for a full server to ESX job.





Many-to-one X

One-to-many X

Chained X

Single server X

456













Upgrade 5.2 physical or virtualserver to ESX connection to 6.0 fullserver to ESX job

X

Upgrade 5.3 P/V to ESX job to 6.0full server to ESX job X



3. When upgrading from version 5.2, you can keep your existing job, but youwill need to upgrade to version 5.3 first, then upgrade to version 6.0. If youwant to upgrade directly to version 6.0, you will have to delete your job andre-create it. When upgrading from version 5.3, you can perform a rollingupgrade where you update the target server first. After the upgrade iscomplete, the source will automatically reconnect to the target. At this point,the job will be an unmanaged job that you can delete or failover. No otherjob controls will be available. Once you upgrade you source, the job will befully controllable.

457

Creating a full server to ESX jobUse these instructions to create a full server to ESX job.








458

When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source.

Your source can have nomore than ten NICs enabled.


6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, select Full Server to Hyper-V or ESX. In theWorkload items pane, select the volumes on the source that you want to protect.


7. By default, Double-Take selects the system volume for protection. You will beunable to deselect the system volume. Select any other volumes on the sourcethat you want to protect. If desired, click theReplication Rules heading andexpand the volumes under Folders. You will see that Double-Take automaticallyexcludes particular files that cannot be used during the protection. If desired, youcan exclude other files that you do not want to protect, but be careful whenexcluding data. Excluded volumes, folders, and/or filesmay compromise theintegrity of your installed applications. There are some volumes, folders, and files(identified in italics text) that you will be unable to exclude, because they arerequired for protected. For example, the boot files cannot be excluded becausethat is where the system state information is stored.

459




9. Choose your target server. This is the virtual recovery appliance on your ESXserver. See Full server to ESX requirements on page 455 for details on the virtualrecovery appliance.



460


When specifying credentials for a new server, specify a user that is amember of the local Double-Take Admin and local administrator securitygroups on the source.


11. Choose the ESX server where your target virtual recovery appliance is located.This is also the server where your replica virtual machine will be located.

l Current Servers—This list contains the vCenter and ESX serverscurrently available in your console session. Select your ESX server from thelist.

l Find a New Server—If the server you need is not in theCurrent Serverslist, click the Find a New Server heading.

l VirtualCenter Server—Select your vCenter server from the list. Ifyour vCenter server is not in the list, clickAdd VirtualCenterServer, specify the server and valid credentials, and clickAdd. If youare not using vCenter, selectNone.

l ESX Server—Specify the name or IP address of the ESX server.l User name—This field will only be available if you are not usingvCenter. In this case, specify the root user or another user that hasthe administrator role on the specified ESX server.

461

l Password—Specify the password associated with theUser nameyou entered.


13. You havemany options available for your full server to ESX job. Configure thoseoptions that are applicable to your environment.


l General on page 463l Failover Monitor on page 464l Failover Options on page 466l Replica Virtual Machine Location on page 467l Replica Virtual Machine Configuration on page 468l Replica Virtual Machine Volumes on page 469l Replica Virtual Machine Network Settings on page 472l Mirror, Verify & Orphaned Files on page 473l Network Route on page 476l Snapshots on page 477l Compression on page 478l Bandwidth on page 479

462

General


463

Failover Monitor






464











465

Failover Options


466


Select one of the volumes from the list to indicate the volume on the target whereyou want to store the configuration files for the new virtual server when it iscreated. The target volumemust have enough Free Space. You can select thelocation of the .vmdk files underReplica Virtual Machine Volumes.

467






468


l Replica Disk Size—For each volume you are protecting, specify the sizeof the replica disk on the target. Be sure and include the value inMB or GBfor the disk. The valuemust be at least the size of the specifiedUsed Spaceon that volume. Any disk size specification will be discarded if you selectUse pre-existing virtual disks, because the pre-existing configuration willbe used.


l Replica Disk Format—For each volume you are protecting, specify theformat of the disk that will be created. Any disk format specification will bediscarded if you selectUse pre-existing virtual disks, because the pre-existing configuration will be used.

l Flat—This disk format allocates the full amount of the disk spaceimmediately, but does not initialize the disk space to zero until it isneeded. This disk format is only available on ESX 5.

l Thick—This disk format allocates the full amount of the disk spaceimmediately, initializing all of the allocated disk space to zero.

l Thin—This disk format does not allocate the disk space until it isneeded.

l Target Volume—For each volume you are protecting, specify the volumeon the target where you want to store the .vmdk files for the new replicavirtual machine. If you selectUse pre-existing virtual disks, all of the pre-

469

existing disksmust be on the same volume. You can specify the location ofthe virtual machine configuration files underReplica Virtual MachineLocation.

l Use pre-existing virtual disks—You can reuse an existing virtual disk onyour target, rather than having Double-Take create a virtual disk for you.This can be useful for pre-staging data on a virtual machine over a LANconnection and then relocating it to a remote site after the initial mirror iscomplete. You save time by skipping the virtual disk creation steps andperforming a differencemirror instead of a full mirror. In order to use a pre-existing virtual disk, it must be a valid virtual disk. It cannot be attached toany other virtual machine, and the virtual disk size and format cannot bechanged.

Each pre-existing diskmust be placed in a temporary location on theappropriate datastore, and each temporary locationmust be the samename. For example, a valid configuration would be datastore1/prestage,datastore2/prestage, and datastore3/prestage, but an invalid configurationwould be datastore1/prestage1, datastore2/prestage2, anddatastore3/prestage3. Double-Take will skip the virtual disk creation stepswhen using a pre-existing disk, and will insteadmove your existing virtualdisks to the appropriate VMware location on that datastore for the virtualmachine. Therefore, it is important that you place your pre-existing virtualdisks in the temporary locations so thismove processwill be handledcorrectly. Specify this temporary location for Enter the path on the targetdatastore which has pre-existing virtual disks.

In order for Double-Take to find the pre-existing disk, the virtual disk filenamesmust be formatted using the convention SourceServer_DriveLetter.For example, if your source server is Alpha and you are protecting drivesCand D, Double-Take will look for the file namesAlpha_C.vmdk and Alpha_D.vmdk. If you are using IP addresses, substitute the IP address for theserver name. For example, if the IP address for server Alpha is172.31.10.25 then Double-Take will look for the file names 172.31.10.25_C.vmdk and 172.31.10.25_D.vmdk.

If you originally created a virtual disk and specified the source server by itsIP address, the pre-existing virtual disk file name cannot use the servername. However, you can rename that file and its associated -flat.vmdk fileto use the IP address. The reverse is also true. If you originally specified thesource server by its name, the pre-existing virtual disk file name cannot usethe server’s IP address. However, you can rename the file and itsassociated -flat.vmdk to use the source name. For example, if you originallycreated a virtual disk and specified the source by its IP address, you need torename the file source_name_drive.vmdk to source_IPaddress_drive.vmdk. You also need to rename the file source_name_drive-flat.vmdkto source_IPaddress_drive-flat.vmdk. The reverse (change source_IPaddress to source_name for both files) is also true. Additionally, you willneed to edit the .vmdk file manually because it contains the name of the -

470

flat.vmdk file. Modify the reference to the -flat.vmdk file to the new name youhave specified using any standard text editor.

In aWAN environment, youmaywant to take advantage of theUse pre-existing virtual disks feature by using a process similar to the following.



replica.d. Remove the virtual machine from the ESX inventory, which will

delete the virtual machine configuration but will keep theassociated.vmdk files.

e. Shut down andmove the ESX target server to your remote site.f. After the ESX target server is back online at the remote site, move

the .vmdk files to a temporary location.g. Create a new protection job for the same source server and select to

Use pre-existing virtual disks, specifying the temporary location ofyour .vmdk files. Double-Take will reuse the existing .vmdk files(automaticallymoving the files to the correct location) and perform adifferencemirror over theWAN to bring the virtual machine up-to-date.

471






472




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for full server to ESX jobs.




473





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for full serverto ESX jobs.




Do not disable this option for full server to ESX jobs. The calculationtime is when the system state protection processes hard links. If youdisable the calculation, the hard link processing will not occur andyoumay have problems after failover, especially if your source isWindows 2008.



474





475

Network Route



476

Snapshots








477

Compression









478

Bandwidth









479










480




481

Managing and controlling full server to ESX jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


Target Server


482

Job Type

Each job type has a unique job type name. This job is a Full server toESX job. For a complete list of all job type names, press F1 to view theDouble-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode


483


484


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


485

Bytes sent




Connected since


Recent activity




486



Create a New Job


View Job Details


Delete




Provide Credentials


487



Start




Pause


Stop


Take Snapshot


Manage Snapshots


Failover or Cutover

Starts the failover process. See Failing over full server to ESX jobs onpage 501 for the process and details of failing over a full server to ESX

488

job.

Failback

Starts the failback process. Failback does not apply to full server to ESXjobs.

Restore

Starts the restoration process. Restore does not apply to full server toESX jobs.

Reverse

Reverses protection. Reverse protection does not apply to full server toESX jobs.

Undo Failover

Cancels a test failover by undoing it. This resets the servers and the jobback to their original state. See Failing over full server to ESX jobs onpage 501 for the process and details of undoing a failed over full serverto ESX job.

View Job Log






489


l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forfull server to ESX jobs, but ideally it should not be used.




Do not disable this option for full server to ESX jobs.The calculation time is when the system stateprotection processes hard links. If you disable thecalculation, the hard link processing will not occur andyoumay have problems after failover, especially ifyour source isWindows 2008.




l Mirror only if the file on the source is newer thanthe copy on the target—This option is available for

490

full server to ESX jobs, but ideally it should not be used.l Use block checksum for comparisons—For thosefiles flagged as different, themirroring process canperform a block checksum comparison and send onlythose blocks that are different.










Filter

Select a filter option from the drop-down list to only display certain jobs.You can displayHealthy jobs, Jobs with warnings, or Jobs witherrors. To clear the filter, selectAll jobs. If you have created andpopulated server groups, then the filter will only apply to the jobs

491

associated with the server or target servers in that server group. SeeManaging servers on page 76.

Type a server name


Overflow Chevron


492

Viewing full server to ESX job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Full server toESX job. For a complete list of all job type names, press F1 to view theDouble-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


493


Target data state








Target route


Compression


Bandwidth limit


Connected since


494



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



495

Replication queue


Disk queue


Bytes sent




496

Validating a full server to ESX jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







497

Editing a full server to ESX jobUse these instructions to edit a full server to ESX job.



3. You will see the same options for your full server to ESX job aswhen you createdthe job, but you will not be able to edit all of them. If desired, edit those options thatare configurable for an existing job. SeeCreating a full server to ESX job on page458 for details on each job option.







498

Viewing a full server to ESX job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


499

Clear


Time


Description


500

Failing over full server to ESX jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.











501



Because theWindows product activation is dependent on hardware, youmay need to reactivate your Windows registration after failover. In mostcaseswhen you are usingWindows 2003, you can follow the on-screenprompts to complete the reactivation. However, when you are usingWindows 2008, the reactivation depends on several factors includingservice pack level, Windows edition, and your licensing type. If aWindows2008 target comes online after failover with an activation failure, use thefollowing steps appropriate for your license type.











502


6. There is no reverse or failback once you have failed over. If you need to go back toyour original hardware, delete the job and re-create a new one if your originalsource was a virtual server. If your original source was a physical server, you willneed to use a full server job.

503

Chapter 13 Full server to ESX applianceprotection

This section is specific to full server to ESX appliance protection and includes thefollowing topics.

l See Full server to ESX appliance requirements on page 505—Full server to ESXappliance protection includes specific requirements for this type of protection.

l SeeCreating a full server to ESX appliance job on page 511—This sectionincludes step-by-step instructions for creating a full server to ESX appliance job.

l SeeManaging and controlling full server to ESX appliance jobs on page 520—You can view status information about your full server to ESX appliance jobs andlearn how to control these jobs.

l See Failing over full server to ESX appliance jobs on page 532—Use this sectionwhen a failover condition has beenmet or if you want to failover manually.

504

Full server to ESX appliance requirementsUse these requirements for full server to ESX appliance protection.

l Source server—The source server can be a physical or virtual server runningany of the following operating systems.

l Windows—You can use any of the followingWindows operating systemsfor a physical server or a virtual guest.

l Windows 2003 SP1 or later and 2003 R2l Storage Server Editionl Small Business Serverl WebEdition (i386 and x64)l Standard Edition (i386 and x64)l Enterprise Edition (i386 and x64)l Datacenter (i386 and x64)

l Windows 2008 and 2008 R2l Storage Server Edition (i386 and x64)l Small Business Server (Standard and Premium x64)l Foundation Serverl Essential Business Server (x64)l WebServer (i386 and x64)l Standard Edition (i386 and x64)l Enterprise Edition (i386 and x64)l Datacenter (i386 and x64)l Server Core (2008 R2 only)

To support the full server to ESX appliance job type onWindows2003 servers, theWindows iSCSI Initiator is placed into a folder onWindows 2003 servers during Double-TakeWindows installations.You will have to install it manually before creating a full server toESX appliance job. See Installing theWindows iSCSI Initiator onpage 60. If you are usingWindows 2008, the iSCSI Initiator isalready installed, but you will have to enable it throughAdministrative Tools, if it is not already enabled. (By default, it is notenabled.)

505

l Linux—You can use any of the following Linux operating systems for aphysical server or a virtual guest.

l RedHat Enterprise Linux, Oracle Enterprise Linux, and CentOSl Operating system version—5.7 through 5.8l Kernel version—2.6.18.x.xl Kernel type for x86 (32-bit) architectures—Default (SMP),Xen, PAE

l Kernel type for x86-64 (64-bit) architectures—Default (SMP),Xen

l File system—Ext3, Ext4l RedHat Enterprise Linux, Oracle Enterprise Linux, and CentOS

l Operating system version—6.1 through 6.2l Kernel version—2.6.32.x.xl Kernel type for x86 (32-bit) architectures—Defaultl Kernel type for x86-64 (64-bit) architectures—Defaultl File system—Ext3, Ext4

Oracle Enterprise Linux support is for themainline kernel only, notthe Unbreakable kernel.

Youmust have lsb, parted, /usr/sbin/dmidecode, and /usr/bin/whichon your Linux server before you can install and use Double-TakeAvailability. Your Linux source server must also have a Linux iSCSIinitiator (iscsi-initiator-utils package) that is version 2.0-870 or later.See your operating system documentation for details on thesepackages and utilities.

l Target host server—The target host server must be an ESX server. It can beany of the following ESX operating systems. Note that ESX is commonly referredto as the Classic edition and ESXi as the Embedded and Installable edition.


If you are using the Standard edition of ESX 4.0 or ESXi 4.0, youmusthave update 1 or later.

If your virtual guest isWindows 2008 R2, your ESX host must have ESX4.0 update 1 or later.

506

l Virtual recovery appliance—The target ESX host must have an existing virtualmachine, known as a virtual recovery appliance. This will be anOVF (OpenVirtualization Format) virtual machine included with Double-Take. Youmust installthis virtual machine before you can establish protection. When you establishprotection, the virtual recovery appliance will create a new virtual server, createand attach disks and an iSCSI target, and so on. If failover occurs, the iSCSItarget is released andmounted and the new virtual machine is prepped andbooted. Once the new virtual machine is online, it will have the identity, data, andsystem state of the source. Since the virtual recovery appliancemaintains its ownidentity, it can be reused for additional failovers. Keep inmind the followingcaveats for the virtual recovery appliance.

l The virtual recovery appliancemust a standalone virtual machine.l It should not reside in anymultiple virtual machine vApp.l The appliance is pre-configured for optimal performance. You do not needtomodify thememory, CPU, or other configurations.

l You should not install or run anything else on this appliance.l The firewall is disabled and should remain disabled.l A single virtual recovery appliance can protect amaximumof 59 volumesfrom any number of sources.

l vCenter—vCenter is not required, but can be used in your envionment. VMotionis only supported if you are using vCenter.

l System memory—Theminimum systemmemory on each server should be 1GB. The recommended amount for each server is 2 GB.

l Disk space for program files—This is the amount of disk space needed for theDouble-Take program files. For Windows 2003, this is approximately 300MB. ForWindows 2008, this is approximately 375MB. For Linux, this is approximately 285MB.

For Windows operating systems, the program files can be installed to anyvolumewhile theMicrosoft Windows Installer files are automaticallyinstalled to the operating system boot volume.

For Linux operating systems, about 45MB will be on your /root partition,about 40MB will be on your /usr partition, and about 200MB will be in /opt.

Make sure you have additional disk space for Double-Take queuing,logging, and so on.

l Server name—Double-Take includesUnicode file system support, but yourserver namemust still be in ASCII format. If you have the need to use a server'sfully-qualified domain name, your server cannot start with a numeric characterbecause that will be interpreted as an IP address.

507

l Protocols and networking—Your serversmust meet the following protocol andnetworking requirements.

l Your serversmust have TCP/IP with static IP addressing. (Some job typesallow you to add DHCP addresses for failover monitoring, although onlyafter a job has already been created. Keep inmind that depending on yourfailover configuration, a source reboot may or may not cause a failover buthaving a new address assigned byDHCPmay also cause a failover.)

l By default, Double-Take is configured for IPv6 and IPv4 environments, butthe Double-Take service will automatically check the server at servicestartup andmodify the appropriate setting if the server is only configured forIPv4. If you later add IPv6, you will need tomanuallymodify theDefaultProtocol server setting. SeeServer and job settings on page 110 fordetails.

l IPv6 is only supported for Windows 2008 servers.l If you are using IPv6 on your servers, your clientsmust be run from an IPv6capablemachine.

l In order to properly resolve IPv6 addresses to a hostname, a reverse lookupentry should bemade in DNS.

l Ports—In addition to the core server ports identified inCore Double-Takerequirements on page 28, youmust also allow iSCSI communication betweenyour source and the virtual recovery appliance, communication on ports 6325 and6326 between your source and the virtual recovery appliance, and the serversmust also be able to communicate using ports 6525 and 6526.

l Windows specific requirements—The following requirements apply only if yoursource is aWindows operating system.

l Windows firewall—If you haveWindows firewall enabled on your servers,there are two requirements for theWindows firewall configuration.

l TheDouble-Take installation programwill automatically attempt toconfigure ports 6320, 6325, and 6326 for Double-Take. If you cancelthis step, you will have to configure the portsmanually.

l If you are using the Double-Take Console to push installations out toyour servers you will have to open firewall ports for WMI (WindowsManagement Instrumentation), which usesRPC (Remote ProcedureCall). By default, RPC will use ports at random above 1024, andthese portsmust be open on your firewall. RPC ports can beconfigured to a specific range by specific registry changes and areboot. See theMicrosoft Knowledge Base article 154596 forinstructions. Additionally, you will need to open firewall ports forSMB (server message block) communicationswhich uses ports 135-139 and port 445. As an alternative, you can disable theWindowsfirewall temporarily until the push installations are complete.

See Firewalls on page 838 for instructions on handling firewalls in yourenvironment.

l Windows Management Instrumentation (WMI)—Double-Take isdependent on theWMI service. If you do not use this service in your

508






environment, contact technical support.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5Service Pack 1 is required. This version is not included in the .NET version4.0 release. Therefore, even if you have .NET version 4.0 installed, you willalso need version 3.5.1. You can install this version from the Double-TakeCD, via a web connection during the Double-Take installation, or from acopy you have obtainedmanually from theMicrosoft web site.

l File system—Double-Take supports the NTFS file system. FAT andFAT32 are no longer supported.

l Linux specific requirements—The following requirements apply to a Linuxsource and to the virtual recovery appliance.

l Name resolution—Your serversmust have name resolution or DNS. TheDouble-Take Consolemust be able to resolve the virtual recoveryappliance, and the virtual recovery appliancemust be able to resolve allsource servers. For details on name resolution options, see your Linuxdocumentation or online Linux resources.

l Security—Double-Take security is granted throughmembership in usergroups. The groups can be local or LDAP (Lightweight Directory AccessProtocol). A user must provide a valid local account that is amember of theDouble-Take security groups

l SELinux policy—SELinux should be disabled on the source.l Supported configurations—The following table identifies the supportedconfigurations for a full server to ESX appliance job.





Many-to-one X

One-to-many X

Chained X

Single server X

509





Serverconfiguration





WindowsCluster Shared Volumes(CSV) guest level X

WindowsCluster Shared Volumes(CSV) host level X


Upgrade 4.6 Double-Take for Linuxconnection to 6.0 full server to ESXappliance job

X

Upgrade 4.7 Double-Take for Linuxconnection to 6.0 full server to ESXappliance job

X


2. Since the upgrade configuration is not supported, you will have to delete theexisting connection before the upgrade and create a new job after theupgrade.

510

Creating a full server to ESX appliance jobUse these instructions to create a full server to ESX appliance job.



3. SelectProtect any server with a Linux Virtual Recovery Appliance and clickNext.

4. Choose your Double-Take Virtual Recovery Appliance and the ESX server that ishosting the appliance.

l Virtual Recovery Appliance—Specify the IP address of the Double-TakeVirtual Recovery Appliance.

l User name—Specify the root user.l Password—Specify the password that you assigned when first youpowered on the virtual recovery appliance.

l Use vCenter—Select this option if you want to specify your vCenter server.l Use ESX host directly—Select this option if you want to specify your ESXhost.

l Server—Specify the name or IP address of your vCenter server or ESXserver.

l User name—Specify the root user or another user that has theadministrator role on your ESX server.

l Password—Specify the password associated with theUser name youentered.

511


6. Choose your source server. This is theWindows or Linux server that you want toprotect.




When specifying credentials for a new server, specify a user that is amember of the dtadmin security group on the source.


512

8. For the server that you are protecting, choose the volumes that you want toprotect.

l Target datastore—Select a datastore on your ESX host where you wantto store the replica virtual machine configuration files. You can specify thelocation of the .vmdk files later in the workflow.

l Select the volumes you want to protect—Bydefault, the systemvolumewill be selected for protection. If you are protecting a Linux source,the boot volumewill also be selected for protection. You will be unable todeselect these volumes. Select any other volumes on the source that youwant to protect.

On Linux source servers, the swap partition is excluded by defaultand you cannot select it, however, it will be created on the replica.

l Exclude these paths—If there are specific paths on a volume that you donot want to protect, specify those locations. Keep inmind that excluded datamay impact the integrity of your applications. Specify any paths to excludefrom protection and clickAdd. You can also specify a semi-colon delimitedlist of paths and clickAdd, and separate exclude rules will bemade for eachpath in your list. If you need to remove a path from being excluded, selectthe path and clickRemove.


513

10. You havemany options available for your full server to ESX appliance job.Configure those options that are applicable to your environment.


l General on page 514l Replica Virtual Machine Configuration on page 515l Replica Virtual Machine Volumes on page 516l Replica Virtual Machine Network Settings on page 517l Mirror, Verify & Orphaned Files on page 518

General


514






515


l Replica Disk Size—For each volume you are protecting, specify the sizeof the replica disk on the target. Be sure and include the value inMB or GBfor the disk. The valuemust be at least the size of the specifiedUsed Spaceon that volume.


l Replica Disk Type—For each volume you are protecting, specify theformat of the disk that will be created.

l Flat—This disk format allocates the full amount of the disk spaceimmediately, but does not initialize the disk space to zero until it isneeded. This disk format is only available on ESX 5.

l Thick—This disk format allocates the full amount of the disk spaceimmediately, initializing all of the allocated disk space to zero.

l Thin—This disk format does not allocate the disk space until it isneeded.

l Storage Controller—For each volume you are protecting, specify the typeof Storage Controller that you want to use for each volume on the target.

l Target Volume—For each volume you are protecting, specify the volumewhere you want to store the .vmdk files for the new replica virtual server.You can specify the location of the virtual machine configuration files on thepreviousChoose Volumes to Protect page.

If your source is Linux, and it is using LVM (Logical VolumeManager), foreach source partition individual fixed disks will be created on the replica.

516






517










If delete orphaned files is enabled, carefully review any replicationrules that use wildcard definitions. If you have specified wildcards tobe excluded from protection, filesmatching those wildcardswill alsobe excluded from orphaned file processing and will not be deletedfrom the target. However, if you have specified wildcards to beincluded in your protection, those files that fall outside the wildcard

518

inclusion rule will be considered orphaned files and will be deletedfrom the target.








519

Managing and controlling full server to ESX appliancejobs

ClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


Target Server


520

Job Type

Each job type has a unique job type name. This job is a Full Server toESX Appliance job. For a complete list of all job type names, press F1 toview the Double-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode


521


522


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


523

Bytes sent




Connected since


Recent activity




524



Create a New Job


View Job Details


Delete



If you no longer want to mirror and replicate data from the source to thetarget but still want to keep the replica of the source on the target, selectto keep the associated replica virtual machine.

Provide Credentials




525

Start




Pause

Pauses the selected jobs. Data will be queued on the source while thejob is paused.

Stop

Stops the selected jobs. The jobs remain available in the console, butthere will be nomirroring or replication data transmitted from the sourceto the target. Mirroring and replication data will not be queued on thesource while the job is stopped, requiring a remirror when the job isrestarted. The type of remirror will depend on your job settings.

Take Snapshot

Snapshots are not applicable to full server to ESX appliance jobs.

Manage Snapshots

Snapshots are not applicable to full server to ESX appliance jobs.

Failover or Cutover

Starts the failover process. See Failing over full server to ESXappliance jobs on page 532 for the process and details of failing over afull server to ESX appliance job.

Failback

Starts the failback process. Failback does not apply to full server to ESXappliance jobs.

Restore

Starts the restoration process. Restore does not apply to full server toESX appliance jobs.

526

Reverse

Reverses protection. Reverse protection does not apply to full server toESX appliance jobs.

Undo Failover

Cancels a test failover by undoing it. Undo failover does not apply to fullserver to ESX appliance jobs.

View Job Log

Opens the job log. The job log is not available for full server to ESXappliance jobs.

Other Job Actions

Opens a small menu of other job actions. These job actions are notavailable for full server to ESX appliance jobs.

Filter


Type a server name


Overflow Chevron


527

Viewing full server to ESX appliance job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Full Server toESX Appliance job. For a complete list of all job type names, press F1 toview the Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


528


Target data state








Target route


Compression


Bandwidth limit


Connected since


529



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



530

Replication queue


Disk queue


Bytes sent




531

Failing over full server to ESX appliance jobsYouwill be notified in the console when a failover condition has beenmet. At this time,you should trigger failover. You can also trigger failover at any other time you desire, thusallowing you to better control the failover process.



l Failover to a snapshot—This option is not available for full server to ESXappliance jobs.



4. When you are ready to begin failover, clickFailover.5. There is no reverse or failback once you have failed over. If your original source

was aWindows server, you can create a full server job to go back to your originalsource hardware.

If you need to update DNS after failover, there is a sample DNS update scriptlocated in /etc/DT/sysprep.d. Youmay need tomodify the script for yourenvironment. If you need basic assistance with script modifications, contactTechnical Support. Assistance with advanced scripting will be referred toProfessional Services.

532

Chapter 14 V to ESX protectionThis section is specific to V to ESX protection and includes the following topics.

l SeeV to ESX requirements on page 534—V to ESX protection includes specificrequirements for this type of protection.

l SeeCreating a V to ESX job on page 537—The section includes step-by-stepinstructions for creating a V to ESX job.

l SeeManaging and controlling V to ESX jobs on page 546—You can view statusinformation about your V to ESX jobs and learn how to control these jobs.

l See Failing over V to ESX jobs on page 578—Use this section when a failovercondition has beenmet or if you want to failover manually.

l SeeReversing V to ESX jobs on page 579—Use this section to reverseprotection. The source replica on the target is now sending data back to theoriginal source.

533

V to ESX requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor V to ESX protection.

l Source virtual server—The source virtual server can be any of the operatingsystems listed in theCore Double-Take requirements on page 28. The sourceserver does not need Double-Take installed on it. If it is not, the installation will becompleted during the protection process, however the virtual must meet theWindows firewall requirements as described in theCore Double-Takerequirements on page 28.

In order for the installation to be completed during the protection process,the Double-Take Console should have enough valid licenses in the licenseinventory for each of the virtual machines you are protecting. If you do nothave enough valid licenses available, you will have to install Double-Takeon each virtual machine individually and then restart each protection job.SeeManaging the Double-Take license inventory on page 62.

l Source and target ESX server—The ESX server that will host your source andtarget must be the same version of ESX. The version of ESX can be any of thefollowing. Note that ESX is commonly referred to as the Classic edition and ESXias the Embedded and Installable edition.


If you are using the Standard edition of ESX 4.0 or ESXi 4.0, youmust have update 1 or later.

If your source is aWindows 2008 R2 server, your ESX server musthave ESX 4.0 update 1 or later.

l vCenter—Although vCenter is not required, if you are using it, then youmust useversion 4.1 or later.

VMotion is only supported if you are using vCenter.

l Virtual recovery appliance—The target ESX server must have an existingvirtual machine, known as a virtual recovery appliance, that meets the followingrequirements. (When you establish protection, the virtual recovery appliance willcreate new virtual servers, mount disks, format disks, and so on. If failover occurs,the new virtual machines are detached from the virtual recovery appliance and

534

powered on. Once the new virtual machines are online, theywill have the identity,data, and system state of their source. Since the virtual recovery appliancemaintains its own identity, it can be reused for additional failovers.) You canoptionally have an existing virtual recovery appliance on the source ESX server toreverse your protection if desired.

l Operating system—The virtual recovery appliance can be any of theoperating systems listed in theCore Double-Take requirements on page28.

l Operating system version—The virtual recovery appliancemust havethe same or newer operating system than the source (not including servicepack level).

l Operating system installation location—Because VMware boots fromthe first bootable volume that is discovered, the operating systemmust beinstalled to SCSI device 0, Slot 0 on the virtual recovery appliance.

l Double-Take—The virtual recovery appliancemust have Double-Takeinstalled and licensed on it.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5Service Pack 1 is required on the virtual recovery appliance. This version isnot included in the .NET version 4.0 release. Therefore, even if you have.NET version 4.0 installed, you will also need version 3.5.1. You can installthis version from the Double-Take CD, via a web connection during theDouble-Take installation, or from a copy you have obtainedmanually fromtheMicrosoft web site.

l Snapshots—Do not take snapshots of the virtual recovery appliance,because theywill interfere with proper failover.

l Disk controller—VMware Paravirtual SCSI Controllers are not supported.

l Domain controllers—If you are protecting a domain controller, it will start in anon-authoritative restoremode after failover. Thismeans that if it wascommunicating with other domain controllers before failover, it will require one ofthose domain controllers to be reachable after failover so it can request updates. Ifthis communication is not available, the domain controller will not function afterfailover. If this is the only domain controller, this is not an issue.

l Supported configurations—The following table identifies the supportedconfigurations for a V to ESX job.

535





Source to targetconfiguration1



Many-to-one X

One-to-many X

Chained X

Single server X









Upgrade 5.3WindowsESX toESX job to 6.0 V to ESX job X



3. When upgrading, you can perform a rolling upgrade where you update thetarget server first. After the upgrade is complete, the source willautomatically reconnect to the target. At this point, the job will be anunmanaged job that you can delete or failover. No other job controls will beavailable. Once you upgrade you source, the job will be fully controllable.

536

Creating a V to ESX jobUse these instructions to create a V to ESX job.



3. SelectProtect multiple Windows virtual servers on ESX with a WindowsVirtual Recovery Appliance and clickNext.

4. Choose your source server. This is the ESX host that contains the virtual serversthat you want to protect.







537

6. Select the virtual servers on your source that you want to protect. Virtual machinesthat are suspended or powered off, or those that do not have a valid operatingsystem according to ESX will not be available for selection. A separate job will becreated for each source that you select for protection.

Each source can have nomore than ten NICs enabled.


8. Choose the ESX server where your target virtual recovery appliance is located.This is also the server where your replica virtual machine will be located.

538







10. Choose your virtual recovery appliance on your target ESX server. Only validvirtual recovery applianceswill be displayed in the list. If necessary, clickProvideCredentials and specify a valid user on the virtual recovery appliance you haveselected. The user must be amember of the local Double-Take Admin and localadministrators security groups. SeeV to ESX requirements on page 534 fordetails on the virtual recovery appliance.

539


12. If desired, select a virtual recovery appliance on your source ESX server. Thisappliance will be used during the reverse process, allowing you to protect thesource replica virtual server on the target back to the original source ESX host. Ifnecessary, clickProvide Credentials and specify a valid user on the virtualrecovery appliance you have selected. The user must be amember of the Double-Take Admin security group. You can skip this step and select a reverse applianceafter the job has been created, however, youmust have a reverse applianceselected before failover. SeeV to ESX requirements on page 534 for details onthe virtual recovery appliance.

540


14. Select your protection options.

541

l Datastore—For each virtual server you are protecting, select a datastoreon the target ESX host where the replica source virtual server will becreated. If necessary, clickProvide Credentials and specify a valid useron each virtual server. If you want to view disk information for the datastoreson your target ESX host, clickShow additional target datastoresinformation. To hide the information, clickHide additional targetdatastores information.

l Disk Format—For each virtual server you are protecting, specify the typeof disk, Flat (for ESX 5 only), Thick or Thin, that will be created on thereplica virtual server.

l Target Network—For each virtual network on the source ESX host, selecta network on the target ESX host to handle networking for the virtualservers after failover.

l Enable compression—To help reduce the amount of bandwidth needed

542

to transmit Double-Take data, compression allows you to compress dataprior to transmitting it across the network. In aWAN environment thisprovides optimal use of your network resources. If compression is enabled,the data is compressed before it is transmitted from the source.When thetarget receives the compressed data, it decompresses it and then writes it todisk. On a default Double-Take installation, compression is disabled. Toenable it, select this option and set the level fromMinimum toMaximum tosuit your needs.

Keep inmind that the process of compressing data impacts processorusage on the source. If you notice an impact on performance whilecompression is enabled in your environment, either adjust to a lower level ofcompression, or leave compression disabled. Use the following guidelinesto determine whether you should enable compression.



l The higher the level of compression, the higher the CPU utilizationwill be.

l Do not enable compression if most of the data is inherentlycompressed. Many image (.jpg, .gif) andmedia (.wmv, .mp3, .mpg)files, for example, are already compressed. Some images files, suchas .bmp and .tif, are uncompressed, so enabling compression wouldbe beneficial for those types.


l Do not enable compression in conjunction with aWAN Accelerator.Use one or the other to compressDouble-Take data.

All jobs from a single source connected to the same IP address on atarget will share the same compression configuration.

l Target network route—Bydefault, Double-Take will select a defaulttarget route for transmissions. If desired, select a different target route.

l Reverse network route—If you selected a reverse appliance, Double-Take will select a default source route for transmissions. If desired, select adifferent source route.

l Select bandwidth limit—Bandwidth limitations are available to restrict theamount of network bandwidth used for Double-Take data transmissions.When a bandwidth limit is specified, Double-Take never exceeds thatallotted amount. The bandwidth not in use byDouble-Take is available forall other network traffic.

543

All jobs from a single source connected to the same IP address on atarget will share the same bandwidth configuration.

l Do not limit bandwidth—Double-Take will transmit data using100% bandwidth availability.

l Use a fixed limit—Enter a value, in bytes per second, to limit datatransmission. This is themaximumamount of data that will betransmitted per second.

l Use scheduled limits—Use a schedule to limit bandwidth fordifferent times. Schedules that you create will bemaintained if youchange to a fixed limit or to no limit.

l New—ClickNew to create a new scheduled bandwidth limit.Specify the following information.

l Daytime entry—Select this option if the start and endtimes of the bandwidth window occur in the same day(between 12:01 AMandmidnight). The start timemustoccur before the end time.

l Overnight entry—Select this option if the bandwidthwindow begins on one day and continues past midnightinto the next day. The start timemust be later than theend time, for example 6 PM to 6 AM.

l Day—Enter the day on which the bandwidth limitingshould occur. You can pick a specific day of the week,Weekdays to have the limiting occur Monday throughFriday,Weekends to have the limiting occur Saturdayand Sunday, or Every day to have the limiting repeat onall days of the week.

l Start time—Enter the time to begin bandwidth limiting.l End time—Enter the time to end bandwidth limiting.l Preset bandwidth—Select a bandwidth limit rate fromthe common bandwidth limit values. TheBandwidthfield will automatically update to the bytes per secondvalue for your select bandwidth.

l Bandwidth—If desired, modify the bandwidth using abytes per second value. Theminimum limit should be28000 bytes per second.

l Edit—ClickEdit to modify an existing scheduled bandwidthlimit.

l Delete—ClickDelete to remove a scheduled bandwidth limit.15. ClickNext to continue.


544

Errors are designated by a white X inside a red circle. Warnings are designated bya black exclamation point (!) inside a yellow triangle. A successful validation isdesignated by a white checkmark inside a green circle. You can sort the list by theicon to see errors, warnings, or successful validations together. Click on any of thevalidation items to see details. Youmust correct any errors before you can enableprotection.



Because this job type allowed you to createmore than one job at a time, optionsthat are job specific were not presented during the job creation process. Oncethe jobs are created, you can edit each one individually to see and edit all of thevarious job options. SeeEditing a V to ESX job on page 562.

545

Managing and controlling V to ESX jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


Target Server


546

Job Type

Each job type has a unique job type name. This job is a V to ESX job.For a complete list of all job type names, press F1 to view the Double-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode


547


548


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


549

Bytes sent




Connected since


Recent activity




550



Create a New Job


View Job Details


Delete




Provide Credentials


551



Start




Pause


Stop


Take Snapshot

Snapshots are not applicable to V to ESX jobs.

Manage Snapshots

Snapshots are not applicable to V to ESX jobs.

Failover or Cutover

Starts the failover process. See Failing over V to ESX jobs on page 578for the process and details of failing over a V to ESX job.

Failback

Starts the failback process. Failback does not apply to V to ESX jobs.

552

Restore

Starts the restoration process. Restore does not apply to V to ESX jobs.

Reverse

Reverses protection. The job will start mirroring in the reverse directionwith the job name and log file names changing accordingly. After themirror is complete, the job will continue running in the oppositedirection. SeeReversing V to ESX jobs on page 579 for the processand details of reversing a V to ESX job.

Undo Failover

Cancels a test failover by undoing it. This resets the servers and the jobback to their original state.. See Failing over V to ESX jobs on page 578for the process and details of undoing a failed over V to ESX job.

View Job Log







l Mirror only if the file on the source is newer thanthe copy on the target—This option is available for Vto ESX jobs, but ideally it should not be used.

553




Do not disable this option for V to ESX jobs. Thecalculation time is when the system state protectionprocesses hard links. If you disable the calculation, thehard link processing will not occur and youmay haveproblems after failover, especially if your source isWindows 2008.




l Mirror only if the file on the source is newer thanthe copy on the target—This option is available for Vto ESX jobs, but ideally it should not be used.



554









Filter


Type a server name


555

Overflow Chevron


556

Viewing V to ESX job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a V to ESX job.For a complete list of all job type names, press F1 to view the Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


557


Target data state








Target route


Compression


Bandwidth limit


Connected since


558



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



559

Replication queue


Disk queue


Bytes sent




560

Validating a V to ESX jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







561

Editing a V to ESX jobUse these instructions to edit a V to ESX job.



3. Because you configuredmultiple jobs at once when you first established yourprotection, not all of the individual job optionswere available during job creation.Therefore, you will have additional job optionswhen you edit an existing job.


There will be additional sections on theEdit Job Properties page thatyou will be able to view only. You cannot edit those sections.

Go to each page identified below to see the options that you can edit on theEditJob Properties page. After you have configured your options, continue with thenext step on page 574.

l General on page 563l Failover Monitor on page 564l Failover Options on page 566l Reverse Appliance on page 567l Mirror, Verify & Orphaned Files on page 568l Network Route on page 571l Compression on page 572l Bandwidth on page 573

562

General


563

Failover Monitor






564











565

Failover Options

Wait for user to initiate failover—Bydefault, the failover processwill wait foryou to initiate it, allowing you to control when failover occurs. When a failureoccurs, the job will wait in Failover Condition Met for you tomanually initiate thefailover process. Disable this option only if you want failover to occur immediatelywhen a failure occurs.

566

Reverse Appliance

l Select the virtual recovery appliance on the source ESX server thatwill be used when reversing the protection—If desired, select a virtualrecovery appliance on your source ESX server. This appliance will be usedduring the reverse process, allowing you to protect the source replica virtualserver on the target back to the original source ESX host. If necessary, clickProvide Credentials and specify a valid user on the virtual recoveryappliance you have selected. The user must be amember of the Double-Take Admin security group. You can skip this step, however, youmust havea reverse appliance selected before failover.

l Send data to the source route when reversing the protection—Specify an IP address on the source to route Double-Take data. This allowsyou to select a different route for Double-Take traffic. For example, you canseparate regular network traffic and Double-Take traffic on amachine withmultiple IP addresses.

567




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for V to ESX jobs.




568





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for V toESX jobs.




Do not disable this option for V to ESX jobs. The calculation time iswhen the system state protection processes hard links. If youdisable the calculation, the hard link processing will not occur andyoumay have problems after failover, especially if your source isWindows 2008.



569





570

Network Route



571

Compression









572

Bandwidth









573











574


575

Viewing a V to ESX job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


576

Clear


Time


Description


577

Failing over V to ESX jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.




l Failover to a snapshot—This option is not available for V to ESX jobs.3. Select how you want to handle the data in the target queue. Youmaywant to








578

Reversing V to ESX jobsReversing protection allows you to protect your source replica virtual server running onthe target back to the original source host. Your original source host must have alicensed virtual recovery appliance like your original target host. SeeV to ESXrequirements on page 534.

1. Make sure you original source virtual machine is not running.2. On theManage Jobs page, highlight the job that you want to reverse and click

Reverse in the toolbar. The flow of mirroring and replication data will change.Data will be transmitted from the replica virtual machine on the target back to theoriginal source host.

After the reverse is complete, your source replica virtual machine on the target is beingprotected to your original source host. In the event you want to go back to your originalserver roles and hardware configuration, you can failover again.

The original disk structure on the original source virtual machine will be deletedand re-created the first time you perform a reverse. This reverse will perform afull mirror. Subsequent reverseswill always perform a file differencesmirror.

579

Chapter 15 V to Hyper-V protectionThis section is specific to V to Hyper-V protection and includes the following topics.

l SeeV to Hyper-V requirements on page 581—V to Hyper-V protection includesspecific requirements for this type of protection.

l SeeCreating a V to Hyper-V job on page 583—The section includes step-by-stepinstructions for creating a V to Hyper-V job.

l SeeManaging and controlling V to Hyper-V jobs on page 598—You can viewstatus information about your V to Hyper-V jobs and learn how to control thesejobs.

l See Failing over V to Hyper-V jobs on page 630—Use this section when a failovercondition has beenmet or if you want to failover manually.

l SeeReversing V to Hyper-V jobs on page 632—Use this section to reverseprotection. The source replica on the target is now sending data back to theoriginal source.

580

V to Hyper-V requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor V to Hyper-V protection.

l Source server—The source server can be any virtual server running any of theoperating systems listed in theCore Double-Take requirements on page 28.However, if you are using aWindows 2003 operating system, youmust haveService Pack 2 which is required for Hyper-V Integration Services. Additionally, ifyour source is a virtual server and you want Double-Take tomonitor it for failover,then youmust have Integration Components installed on the guest operatingsystem and the virtual machinemust be powered on.

l Target server—The target server can be anyWindows 2008 or 2008 R2operating system from theCore Double-Take requirements on page 28 that hasthe Hyper-V role enabled. In addition, you can use Hyper-V Server 2008 R2 orServer Core 2008 R2with the Hyper-V role enabled. (Hyper-V Server 2008 andServer Core 2008 are not supported.)

l Disk types—Virtual machines cannot use raw, pass-through, or differencingdisks.



l Supported configurations—The following table identifies the supportedconfigurations for a V to Hyper-V job.

581





Source to targetconfiguration1



Many-to-one X

One-to-many X

Chained X

Single server X

Server configuration





Cluster Shared Volumes(CSV) guest level X

Cluster Shared Volumes(CSV) host level X


582

Creating a V to Hyper-V jobUse these instructions to create a V to Hyper-V job.




4. Choose your source server. This is the Hyper-V server or cluster that is hostingthe virtual machines that you want to protect.





583



6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, selectGuest-Level Hyper-V. In theWorkloaditems pane, select the virtual machines on the Hyper-V source that you want toprotect. The list of virtual machineswill vary depending on whether your source isa Hyper-V server, cluster, or node.



8. Choose your target server. This is the Hyper-V server that will store the replicas ofthe virtual machines from the source.

584






585

10. You havemany options available for your V to Hyper-V jobs. Configure thoseoptions that are applicable to your environment.


l Replica Virtual Machines on page 587l Replica Virtual Machine Configuration on page 588l Mirror, Verify & Orphaned Files on page 589l Network Route on page 592l Reverse Network Route on page 593l Compression on page 594l Bandwidth on page 595

586

Replica Virtual Machines

l Target Volume—For each virtual machine you are protecting, specify thevolumewhere you want to store the replica virtual machine on the target.

l Target Path—For each virtual machine you are protecting, specify a pathon the selected Target Volumewhere you want to store the replica virtualmachine on the target.

l Replica Disk Format—For each virtual machine you are protecting,specify the type of disk,Dynamic or Fixed, that will be created on thereplica virtual machine.

l Provide Credentials—If necessary, clickProvide Credentials andspecify a valid user on the virtual recovery appliance you have selected. Theuser must be amember of the Double-Take Admin security group andmusthave administrative rights for Hyper-V.

l Show additional target volumes information—Click this link to seestorage information for the volumes on your target. This will help you selectthe appropriate volumes for your replica virtual machines.

If your target is a cluster, you will only see the clustered volumes that havebeen added to the cluster prior to creating the job. If the target is a clusternode, you will only see non-clustered volumes.

587


Map source virtual switches to target virtual switches—Identify how youwant to handle the networkmapping after failover. TheSource NetworkAdapter column lists the NICs from the source. Map each one to a TargetNetwork Adapter, which is a virtual network on the target.

588




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for V to Hyper-V jobs.




589





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for V toHyper-V jobs.




Do not disable this option for V to Hyper-V jobs. The calculationtime is when the system state protection processes hard links. If youdisable the calculation, the hard link processing will not occur andyoumay have problems after failover, especially if your source isWindows 2008.



590





591

Network Route




592

Reverse Network Route

This section is not applicable if your source is a cluster.

Send data to the source server when reversing the protection using thisroute—Bydefault, Double-Take will select a default source route fortransmissions. If desired, specify an alternate route on the source that the data willbe transmitted through. This allows you to select a different route for Double-Taketraffic. For example, you can separate regular network traffic and Double-Taketraffic on amachine with multiple IP addresses.

The IP address used on the target during a reverse will be determinedthrough theWindows route table.

593

Compression









594

Bandwidth









595










596




Because this job type allowed you to createmore than one job at a time, optionsthat are job specific were not presented during the job creation process. Oncethe jobs are created, you can edit each one individually to see and edit all of thevarious job options. SeeEditing a V to Hyper-V job on page 614.

597

Managing and controlling V to Hyper-V jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server

The name of the source.

Target Server

The name of the target.

598

Job Type

Each job type has a unique job type name. This job is a V to Hyper-Vjob. For a complete list of all job type names, press F1 to view theDouble-Take Console online help.

Activity


Mirror Status





Replication Status



Transmit Mode


599


600


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


601

Bytes sent




Connected since


Recent activity




602



Create a New Job


View Job Details


Delete




Provide Credentials


603



Start




Pause


Stop


Take Snapshot

Snapshots are not applicable to V to Hyper-V jobs.

Manage Snapshots

Snapshots are not applicable to V to Hyper-V jobs.

Failover or Cutover

Starts the failover process. See Failing over V to Hyper-V jobs on page630 for the process and details of failing over a V to Hyper-V job.

Failback

Starts the failback process. Failback does not apply to V to Hyper-Vjobs.

604

Restore

Starts the restoration process. Restore does not apply to V to Hyper-Vjobs.

Reverse

Reverses protection. The job will start mirroring in the reverse directionwith the job name and log file names changing accordingly. After themirror is complete, the job will continue running in the oppositedirection. SeeReversing V to Hyper-V jobs on page 632 for the processand details of reversing a V to Hyper-V job.

Undo Failover

Cancels a test failover by undoing it. This resets the servers and the jobback to their original state.. See Failing over V to Hyper-V jobs on page630 for the process and details of undoing a failed over V to Hyper-Vjob.

View Job Log







605

l Mirror only if the file on the source is newer thanthe copy on the target—This option is available for Vto Hyper-V jobs, but ideally it should not be used.




Do not disable this option for V to Hyper-V jobs. Thecalculation time is when the system state protectionprocesses hard links. If you disable the calculation, thehard link processing will not occur and youmay haveproblems after failover, especially if your source isWindows 2008.




l Mirror only if the file on the source is newer thanthe copy on the target—This option is available for Vto Hyper-V jobs, but ideally it should not be used.

l Use block checksum for comparisons—For thosefiles flagged as different, themirroring process can

606

perform a block checksum comparison and send onlythose blocks that are different.










Filter


607

Type a server name


Overflow Chevron


608

Viewing V to Hyper-V job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a V to Hyper-Vjob. For a complete list of all job type names, press F1 to view theDouble-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


609


Target data state








Target route


Compression


Bandwidth limit


Connected since


610



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



611

Replication queue


Disk queue


Bytes sent




612

Validating a V to Hyper-V jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







613

Editing a V to Hyper-V jobUse these instructions to edit a V to Hyper-V job.



3. Because you configuredmultiple jobs at once when you first established yourprotection, not all of the individual job optionswere available during job creation.Therefore, you will have additional job optionswhen you edit an existing job.


There will be additional sections on theEdit Job Properties page thatyou will be able to view only. You cannot edit those sections.

Go to each page identified below to see the options that you can edit on theEditJob Properties page. After you have configured your options, continue with thenext step on page 626.

l General on page 615l Failover Monitor on page 616l Failover Options on page 618l Mirror, Verify & Orphaned Files on page 619l Network Route on page 622l Reverse Network Route on page 623l Compression on page 624l Bandwidth on page 625

614

General


615

Failover Monitor






616











617

Failover Options

Wait for user to initiate failover—Bydefault, the failover processwill wait foryou to initiate it, allowing you to control when failover occurs. When a failureoccurs, the job will wait in Failover Condition Met for you tomanually initiate thefailover process. Disable this option only if you want failover to occur immediatelywhen a failure occurs.

618




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for V to Hyper-V jobs.




619





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for V toHyper-V jobs.




Do not disable this option for V to Hyper-V jobs. The calculationtime is when the system state protection processes hard links. If youdisable the calculation, the hard link processing will not occur andyoumay have problems after failover, especially if your source isWindows 2008.



620





621

Network Route




622

Reverse Network Route

This section is not applicable if your source is a cluster.

Send data to the source server when reversing the protection using thisroute—Bydefault, Double-Take will select a default source route fortransmissions. If desired, specify an alternate route on the source that the data willbe transmitted through. This allows you to select a different route for Double-Taketraffic. For example, you can separate regular network traffic and Double-Taketraffic on amachine with multiple IP addresses.

The IP address used on the target during a reverse will be determinedthrough theWindows route table.

623

Compression









624

Bandwidth









625










626




627

Viewing a V to Hyper-V job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


628

Clear


Time


Description


629

Failing over V to Hyper-V jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.




l Failover to a snapshot—This option is not available for V to Hyper-V jobs.3. Select how you want to handle the data in the target queue. Youmaywant to







In a cluster configuration, if youmove the shared storage ownership onthe original source cluster or change the drive letter after failover, you will

630

be unable to reverse your protection. Keep the source clusterconfiguration the same in order to allow proper reversing of protection.

631

Reversing V to Hyper-V jobsReversing protection allows you to protect your source replica virtual server running onthe target back to the original source host.





632

Chapter 16 Host-level Hyper-V protectionThis section is specific to host-level Hyper-V protection and includes the following topics.

l SeeHost-level Hyper-V requirements on page 634—There are specificrequirements for host-level Hyper-V protection.

l SeeCreating a host-level Hyper-V job on page 637—This section includes step-by-step instructions for creating a host-level Hyper-V job.

l SeeConfiguring Hyper-V Pro tip integration for failover notification on page 656—This section explains how you can extendMicrosoft SystemCenter VirtualMachineManager (SCVMM) Performance and ResourceOptimization (PRO)capabilities by providing specific PRO tips for failover of host-level Hyper-V jobs.

l SeeManaging and controlling host-level Hyper-V jobs on page 658—You canview status information about your host-level Hyper-V jobs and learn how tocontrol these jobs.

l See Failing over host-level Hyper-V jobs on page 677—Use this section when afailover condition has beenmet or if you want to failover manually.

l SeeReversing host-level Hyper-V jobs on page 679—Use this section to reverseprotection. The source replica on the target is now sending data back to theoriginal source.

633

Host-level Hyper-V requirementsIn addition to theCore Double-Take requirements on page 28, use these requirementsfor host-level Hyper-V protection.

l Source and target host operating system—Your source and target hostservers can be anyWindows 2008 or 2008 R2 operating system from theCoreDouble-Take requirements on page 28 that has the Hyper-V role enabled. Inaddition, you can use Hyper-V Server 2008 R2 or Server Core 2008 R2with theHyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are notsupported.) In each case, the source and target must be running identicaloperating system versions. For example, your source cannot beWindows 2008and your targetWindows 2008 R2.

l Guest operating systems—The guest operating system can be any operatingsystem. However, if you want Double-Take tomonitor the virtual machine forfailover, then youmust have Integration Components installed on the guestoperating system and the virtual machinemust be powered on.

l Virtual machine configurations—The following limitations apply to the virtualmachines on the source and target Hyper-V servers.

l The virtual machinesmust be in their own home folder that is not shared byany other virtual machines.

l The virtual machines cannot be created in or replicated to the Hyper-Vsystem default folder.

l The virtual machines' snapshot folder must be unique to each virtualmachine, they cannot be in the Hyper-V system default folder, and theycannot be changed once protection has been established.

l The virtual machines cannot use raw, pass-through, or differencing disks.l WAN support—If your source and target are across aWAN and you wantDouble-Take to automatically update networking on the guest operating systemduring failover, the following limitations apply. If you choose not to have Double-Take automatically update networking on the guest operating system duringfailover, you will have to update the networkmanually, but the following limitationswill not apply.

l Guest operating system—The guest operating systemmust beWindows2003 or Windows 2008.

l Windows Management Instrumentation (WMI)—The host and guestoperating systemsmust have theWMI service enabled.

l User Access Control (UAC)—UACmust be disabled on the guestoperating system.

l Name resolution—Youmust establish name resolution for the guestoperating system.

l Microsoft .NET Framework—Microsoft .NET Framework version 3.5 ServicePack 1 is required on the source and target. This version is not included in the.NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed,you will also need version 3.5.1. You can install this version from the Double-Take

634

CD, via a web connection during the Double-Take installation, or from a copy youhave obtainedmanually from theMicrosoft web site.


l Supported configurations—The following table identifies the supportedconfigurations for a host-level Hyper-V job.





Many-to-one X

One-to-many X

Chained X

Single server X







Cluster Shared Volumes (CSV)host level X 3


Upgrade 5.2 Hyper-V server toHyper-V server connection to 6.0host-level Hyper-V job

X

Upgrade 5.3 Hyper-V to Hyper-Vjob to 6.0 host-level Hyper-V job X


635




2. Windows 2008 R2 is the only supported version of clustered Hyper-Vservers. Windows 2008 R1 is not supported for clustering.

3. Although CSV is not supported for host-level protection, you can use host-level protection for non-CSV virtual machines on a CSV configured cluster.To do this, you will need to execute the altitude script located in the\tools\scripts\csv directory on the product CD or in the extracted webdownload files. If you copy the altitude.bat file to another location, be sureand copy the two .reg files aswell. To protect non-CSV virtual machines ona CSV configured cluster, run the following command on each node of thecluster.

altitude default

The default script will cause your cluster to go into redirected (maintenance)mode the next time the CSV is brought online, taken offline, or changesowning nodes.

If you change back to CSV virtual machines on your CSV configuredcluster, you will need to run the following command to change Double-Takeback to the correct configuration for CSV functionality.

altitude target

The target script will keep your cluster from going into redirected(maintenance) mode.

4. When upgrading from version 5.2, you can keep your existing job, but youwill need to upgrade to version 5.3 first, then upgrade to version 6.0. If youwant to upgrade directly to version 6.0, you will have to delete your job andre-create it. When upgrading from version 5.3, you can perform a rollingupgrade where you update the target server first. After the upgrade iscomplete, the source will automatically reconnect to the target. At this point,the job will be an unmanaged job that you can delete or failover. No otherjob controls will be available. Once you upgrade you source, the job will befully controllable. If you are using a cluster configuration, you cannotupgrade. Youmust delete the existing job, upgrade all of your nodes, andthen re-create the job.

636

Creating a host-level Hyper-V jobUse these instructions to create a host-level Hyper-V job.




4. Choose your source server. This is the Hyper-V server or cluster that is hostingthe virtual machine that you want to protect.





637



6. Choose the type of workload that you want to protect. Under Server Workloads,in theWorkload types pane, selectHost-Level Hyper-V. In theWorkloaditems pane, select the virtual machine on the Hyper-V source that you want toprotect. The list of virtual machineswill vary depending on whether your source isa Hyper-V server, cluster, or node.



8. Choose your target server. This is the Hyper-V server or cluster that will store thereplica of the virtual machine from the source.

638






639

10. You havemany options available for your host-level Hyper-V job. Configure thoseoptions that are applicable to your environment.


l General on page 641l Failover Monitor on page 642l Replica Virtual Machine Location on page 644l Replica Virtual Machine Configuration on page 646l Replica Virtual Machine Network Settings on page 647l Mirror, Verify & Orphaned Files on page 648l Network Route on page 651l Compression on page 652l Bandwidth on page 653

640

General


641

Failover Monitor

l Monitor for failover—Select this option if you want the target to activelymonitor the source for a failure. If you disable this option and do not monitorfor failover, the target will not activelymonitor the source for a failure. In thiscase, you will have tomonitor the sourcemanually on your own and initiatefailover manually if there is a source failure.






If you chooseConsecutive failures, your failure time is calculated in one oftwo ways.

l ICMP enabled—If ICMP is enabled on your host when the job iscreated, your failure time is calculated by the length of time it takesyour host to respond to an ICMP host ping plus the length of time it

642

takes your virtual machine to respond plus the interval time betweenthese two checks, times the number of consecutive failures that canbe allowed. That would be (ICMP host response time + virtualmachine response time + interval) * failure number. If theICMP check fails, the virtual machine check is skipped and the ICMPcheckwill reoccur after the interval time.

l ICMP disabled—If ICMP is disabled on your host when the job iscreated, your failure time is calculated by the length of time it takesyour virtual machine to respond plus the interval time between eachresponse, times the number of consecutive failures that can beallowed. That would be (virtual machine response time + interval) *failure number.

Keep inmind that timeouts from a failed check are included in the responsetimes, so your failure time will not be precise.

l Wait for user to initiate failover—If you aremonitoring for failover, whena failure occurs you can have Double-Take automatically initiate the failoverprocess or wait for you to initiate it. When this option is enabled and a failureoccurs, the job will wait in Failover Condition Met for you tomanuallyinitiate the failover process.When this option is disabled, failover will occurimmediately when a failure occurs.

643


l Select the volume and folder on the target server that will hold thereplica virtual machine—Select one of the volumes from the list toindicate the volume on the target where you want to store the new virtualserver when it is created. The target volumemust have enough FreeSpace to store the source data. If your target is a cluster, you will only seethe cluster aware volumes that have been added to the cluster prior tocreating the job.

l Full path where the replica virtual machine will be stored—Specify alocation on the selectedVolume to store the replica of the source. Byspecifying an existing folder, you can reuse an existing virtual machine onyour Hyper-V target created by a previous protection job. This can be usefulfor pre-staging data on a virtual machine over a LAN connection and thenrelocating it to a remote site after the initial mirror is complete. You save timeby performing a differencemirror instead of a full mirror. In order to use apre-existing virtual disk, it must be a valid virtual disk and it cannot beattached to any registered virtual machine. In aWAN environment, youmaywant to take advantage of re-using an existing virtual disk by using aprocess similar to the following.



replica.

Even though you are keeping the replica virtual machine, it isnot registered with the Hyper-V Manager. If you want to usethe replicamachine, you will have to register it. However, youdo not need to register it to reuse the disks in Double-Take.Double-Take will automatically register the virtual machine atfailover time.

d. Shut down andmove the Hyper-V target server to your remote site.e. After the Hyper-V target server is back online at the remote site,

create a new protection job for the same source server. Double-Take

644

will reuse the existing .vhd files and perform a differencemirror overtheWAN to bring the virtual machine up-to-date.

645




l Map source VLAN ID to target VLAN ID—If your environment is avirtual local area network, identify how you want to handle the VLAN IDsafter failover. Map eachSource VLAN ID to a Target VLAN ID.

646


If your virtual machine is powered on and has Integration Services available, thisoption will allow you to configure advanced settings, which are used primarily forWAN support. Before you can set these options, youmust provide credentials forthe virtual machine you are protecting. Click the linkProvide source virtualmachine credentials to use advanced network configuration and specifytheGuest DNS name,User name, Password,Domain, and clickOK





647




l Mirror only if the file on the source is newer than the copy onthe target—This option is not available for host-level Hyper-V jobs.




648





l Mirror only if the file on the source is newer than thecopy on the target—This option is not available for host-levelHyper-V jobs.







If delete orphaned files is enabled, carefully review any replicationrules that use wildcard definitions. If you have specified wildcards tobe excluded from protection, filesmatching those wildcardswill also

649

be excluded from orphaned file processing and will not be deletedfrom the target. However, if you have specified wildcards to beincluded in your protection, those files that fall outside the wildcardinclusion rule will be considered orphaned files and will be deletedfrom the target.



650

Network Route




651

Compression









652

Bandwidth









653










654




Once protection is established, Double-Takemonitors the virtual disks of theprotected virtual machine for changes to the disk layout. If a new virtual hard diskis added to the virtual machine, the protection job will automatically be updated toinclude the new virtual hard disk, and a file differencemirror will automaticallystart. However, if a virtual hard disk is removed from the protected virtualmachine, the virtual hard disk will not be removed from the projection job until it isdeleted from the source or the protection job is deleted and re-created.

If your source is a cluster and the Double-Take service on the source is stoppedand restarted but failover is not initiated, you will need tomanually bring thesupporting cluster resource back online through the cluster manager in order foryour host-level Hyper-V job to reconnect and transition to a good state. Theresource is located on the source cluster and is called DTTargetRes_VM_GUID,where VM is the name of your virtual machine andGUID is a global unique IDassigned to the job. The resource will be located in the Other Resources group.

If your source is a cluster and your cluster resourcemoves to a node thatDouble-Take considers a bad node (for example, the Double-Take service is notrunning or the node has an invalid activation code), your job will enter an errorstate. Youmust fix the issue on the cluster node and then you can restart the job.However, if this situation occurs on a target cluster, the job will no longer appearin the console. In this case, you will need to fix the issue on the cluster node andthen bring the supporting cluster resource back online through the clustermanager. The resource is located on the source cluster and is calledDTTargetRes_VM_GUID, where VM is the name of your virtual machine andGUID is a global unique ID assigned to the job. The resource will be located inthe Other Resources group.

655

Configuring Hyper-V Pro tip integration for failovernotification

Microsoft SystemCenter Virtual MachineManager (SCVMM) provides centralizedadministration for your Hyper-V virtual machines.Within SCVMM, Performance andResourceOptimization (PRO) provides a basic set of monitors that can alert you tosituationswhere youmaywant or need tomodify a virtual machine configuration in orderto optimize the host or virtual machine. These alerts, called PRO tips, recommendactions for you to take to return a host, virtual machine, or any other component of avirtual environment to a healthy state. Double-Take extends the PROcapabilities byproviding specific PRO tips for host-level Hyper-V jobs.

In order to receive PRO tips for host-level Hyper-V jobs, your SCVMMmachinemust beamember of the domain where your Hyper-V host is located, and youmust have amachine (same or different than your SCVMMmachine) runningMicrosoft SystemCenter OperationsManager (SCOM) 2007 R2.

1. Locate the Double-Take Hyper-V Management Pack for SystemCenterOperationsManager using one of the followingmethods.

l Start the Double-Take installation, and when the Autorun appears, selecttheGet the SCVMM Management Pack link. Copy the .xml file to yourSCOMmachine.

l On the Double-Take installation CD, browse to the SCMgmt\SCVMMdirectory and copy the .xml file to your SCOMmachine.

l Download the Hyper-V Management Pack from the VisionSolutionssupport web site to your SCOMmachine.

2. From the SCOMconsole, clickAdministration or selectGo,Administration.3. Right-click on theManagement Packs line item in the left pane and select Import

Management Pack.4. ClickAdd and selectAdd from disk. You can disregard anymessages indicating

themanagement packmay have dependencies that cannot be located.5. Navigate to the location of the Double-Take Hyper-V Management Pack file that

you copied or downloaded, and follow the steps in theManagement Pack ImportWizard. See the SCOMdocumentation for complete details.

6. SeeCreating a host-level Hyper-V job on page 637 to configure failovermonitoring andmanual intervention.

7. In the event your Hyper-V source fails, you will receive a PRO tip alert.

656




8. You can Implement the Pro tip to start failover or you canDismiss it if you do notwant to failover.

657

Managing and controlling host-level Hyper-V jobsClickManage Jobs from themain Double-Take Console toolbar. TheManage Jobspage allows you to view status information about your jobs. You can also control yourjobs from this page.




Column 1 (Blank)






Job

The name of the job

Source Server


658

Target Server


Job Type

Each job type has a unique job type name. This job is a Host-levelHyper-V job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Activity


If your source is a cluster and the Double-Take service on the source isstopped and restarted but failover is not initiated, you will need tomanually bring the supporting cluster resource back online through thecluster manager in order for your host-level Hyper-V job to reconnectand transition to a good state. The resource is located on the sourcecluster and is called DTTargetRes_VM_GUID, where VM is the nameof your virtual machine andGUID is a global unique ID assigned to thejob. The resource will be located in the Other Resources group.

If your source is a cluster and your cluster resourcemoves to a nodethat Double-Take considers a bad node (for example, the Double-Takeservice is not running or the node has an invalid activation code), yourjob will enter an error state. Youmust fix the issue on the cluster nodeand then you can restart the job. However, if this situation occurs on atarget cluster, the job will no longer appear in the console. In this case,you will need to fix the issue on the cluster node and then bring thesupporting cluster resource back online through the cluster manager.The resource is located on the source cluster and is calledDTTargetRes_VM_GUID, where VM is the name of your virtualmachine andGUID is a global unique ID assigned to the job. Theresource will be located in the Other Resources group.

Mirror Status



l Idle—Data is not beingmirrored.l Paused—Mirroring has been paused.

659

l Stopped—Mirroring has been stopped.l Removing Orphans—Orphan files on the target are beingremoved or deleted depending on the configuration.


Replication Status



Transmit Mode


660


Name

The name of the job

Target data state








Mirror remaining


Replication queue


Disk queue


661

Bytes sent




Connected since


Recent activity




662



Create a New Job


View Job Details


Delete




Provide Credentials


663



Start




Pause


Stop


Take Snapshot

Snapshots are not applicable to host-level Hyper-V jobs.

Manage Snapshots

Snapshots are not applicable to host-level Hyper-V jobs.

Failover or Cutover

Starts the failover process. See Failing over host-level Hyper-V jobs onpage 677 for the process and details of failing over a host-level Hyper-Vjob.

664

Failback

Starts the failback process. Failback does not apply to host-level Hyper-V jobs.

Restore

Starts the restoration process. Restore does not apply to host-levelHyper-V jobs.

Reverse

Reverses protection. The job will start mirroring in the reverse directionwith the job name and log file names changing accordingly. After themirror is complete, the job will continue running in the oppositedirection. SeeReversing host-level Hyper-V jobs on page 679 for theprocess and details of reversing a host-level Hyper-V job.

Undo Failover

Cancels failover by undoing it. This resets the servers and the job backto their original state. If you had performed a live failover, any changesmade on the target will be lost when you undo. See Failing over host-level Hyper-V jobs on page 677 for the process and details of failingundoing a failed over host-level Hyper-V job.

View Job Log





665



l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forhost-level Hyper-V jobs, but ideally it should not beused.







l Mirror only if the file on the source is newer thanthe copy on the target—This option is available forhost-level Hyper-V jobs, but ideally it should not beused.

l Use block checksum for comparisons—For thosefiles flagged as different, themirroring process can

666

perform a block checksum comparison and send onlythose blocks that are different.










Filter


667

Type a server name


Overflow Chevron


668

Viewing host-level Hyper-V job detailsFrom theManage Jobs page, highlight the job and clickView Job Details in thetoolbar.


Job name

The name of the job

Job Type

Each job type has a unique job type name. This job is a Host-levelHyper-V job. For a complete list of all job type names, press F1 to viewthe Double-Take Console online help.

Health





Activity


Connection ID


Transmit Mode


669


Target data state








Target route


Compression


Bandwidth limit


Connected since


670



Mirror Status







Mirror remaining


Mirror skipped


Replication Status



671

Replication queue


Disk queue


Bytes sent




672

Validating a host-level Hyper-V jobOver time, youmaywant to confirm that any changes in your network or environmenthave not impacted your Double-Take job. Use these instructions to validate an existingjob.







673

Editing a host-level Hyper-V jobUse these instructions to edit a host-level Hyper-V job.



3. You will see the same options available for your host-level Hyper-V job aswhenyou created the job, but you will not be able to edit all of them. If desired, edit thoseoptions that are configurable for an existing job. SeeCreating a host-level Hyper-V job on page 637 for details on each job option.







674

Viewing a host-level Hyper-V job logYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


675

Clear


Time


Description


676

Failing over host-level Hyper-V jobsWhen a failover condition has beenmet, failover will be triggered automatically if youdisabled the wait for user option during your failover configuration. If the wait for userbefore failover option is enabled, you will be notified in the console when a failovercondition has beenmet. At that time, you will need to trigger it manually from the consolewhen you are ready.




l Failover to a snapshot—This option is not available for host-level Hyper-V jobs.






In a cluster configuration, if youmove the shared storage ownership onthe original source cluster or change the drive letter after failover, you willbe unable to reverse your protection. Keep the source clusterconfiguration the same in order to allow proper reversing of protection.

677

5. If desired, you can undo your live or test failover by selectingUndo Failover in thetoolbar. In either case, the replica virtual machine on the target will be shut downand the protection job will be restarted performing a file differencesmirror. Theone difference when undoing a live failover is the virtual machine on the source willbe started. This step is not needed when undoing a test failover, because thevirtual machine on the source is not shut down during a test failover. In both cases,all changesmade on the replica virtual machine on the target will be lost. If you donot want to lose data changesmade on the replica virtual machine on the target,seeReversing host-level Hyper-V jobs on page 679

678

Reversing host-level Hyper-V jobsReversing protection allows you to protect your source replica virtual server running onthe target back to the original source host.





679

Chapter 17GeoCluster protectionThis section is specific to GeoCluster protection and includes the following topics.

l SeeGeoCluster requirements on page 681—GeoCluster protection includesspecific requirements for this type of protection.

l SeeConfiguring your cluster for GeoCluster installation on page 682—GeoCluster protection requires you to have an appropriately configured clusterenvironment, which is detailed in this section.

l SeeEstablishing GeoCluster protection on page 685—This section includes step-by-step instructions for establishing GeoCluster protection.

l SeeMonitoring and controlling GeoCluster jobs on page 698—This sectionincludes information on an online pending resource and theGeoClusterReplicated Disk Status resource.

680

GeoCluster requirementsMake sure your cluster meets theCore Double-Take requirements on page 28, aswellas the following requirements specific to GeoCluster protection.

l Operating system—The operating systems are limited to theWindowsEnterprise and Datacenter editions listed in theCore Double-Take requirementson page 28.

l Hardware—Microsoft support for MSCS andMSCS-basedMicrosoftapplications requires that the cluster configuration appear on theMicrosoftHardware Compatibility List under category Cluster.

l Cluster Network Name—Double-Take does not handle dynamic changes to thecluster network names, the names assigned to the routes for network traffic. If anetwork name is changed for a network that is used byDouble-Take, theGeoCluster Replicated Disk resourcemust be taken offline, the resource'snetwork propertymust be changed, and then the resourcemust be brought backonline.

l Disk queuing—TheDouble-Take disk queue, configured during installation,should use a local volume for each node in the cluster.

l Anti-virus software—You should configure your anti-virus software to delete orquarantine viruses because cleaning them can cause an access denied retryingoperation error. Additionally, configuring virus software to scan outgoing traffic willlessen performance impacts.

l Supported upgrade configurations—Before upgrading be sure and read theInstallation on page 39 and review the proper procedure for upgrading Double-Take on a cluster.

Upgrade Configuration Supported NotSupported

Upgrade 5.2 GeoCluster Replicated Disk Resourceto 6.0 GeoCluster Replicated Disk Resource X

Upgrade 5.3 GeoCluster Replicated Disk Resourceto 6.0 GeoCluster Replicated Disk Resource X

681

Configuring your cluster for GeoCluster installationComplete the Geocluster installation and configuration appropriate for the operatingsystem you are using.

l Configuring aWindows 2003 cluster on page 682l Configuring aWindows 2008 cluster on page 683

Configuring a Windows 2003 clusterIn a typicalWindows 2003MSCS shared disk cluster configuration, the quorumresource, by default, is the Local Quorum and is located on the first shared disk in thecluster. Because in a GeoCluster configuration there is no shared physical disk, the LocalQuorumwill not work as the quorum resource. You will need to choose one of the otherWindows quorums. The recommended quorum resource for GeoCluster is theMajorityNode Set or Majority Node Set with File ShareWitness.

If you are upgrading from a previousGeoCluster version and were usingGeoCluster as a quorum, youmust select another quorum type. GeoCluster canno longer be used as a quorum resource.

l Local Quorum—This quorum is for single node clusters and shared disk clusters.It cannot be used in a GeoCluster configuration.

l Majority Node Set—This quorum is for clusters with three or more nodes.l Majority Node Set with File Share Witness—This quorum is for clusters withonly two nodes. If you are usingWindows 2003 Service Pack 1, see theMicrosoftsupport article 921181 for an update for the File ShareWitness. If you are usingService Pack 2 or later, the update is not needed.

Use the following instructions as a guideline for configuring your Windows 2003 cluster.See your Windows cluster documentation as a complete reference.

1. Login with an account that has administrative rights on the domain and the localmachine.

2. Create the cluster on the first node, if it is not already created. See your Windowsdocumentation for instructions on how to create a cluster.

3. Add your additional nodes to the cluster. See your Windows documentation forinstructions on how to add nodes to the cluster.

4. Install Double-Take Availability on each node of the cluster. See Installing Double-Take Availability on aWindows server using the installation wizard on page 43.

5. Configure your quorum. See your Windows documentation for instructions onconfiguring the quorum appropriate for your environment.

6. If desired, you can install Double-Take Availability on non-clustered clientmachines if you want to use Cluster Administrator to control the GeoCluster

682





resources. Install Double-Take Availability, selecting theClient ComponentsOnly installation option.

Configuring a Windows 2008 clusterThe default quorum resource in aWindows 2008 environment will vary depending onyour configuration (number of nodes, shared disks, and so on). The recommendedquorum resource for GeoCluster is the Node and File ShareMajority. There are otherquorum types available. Review the following list to determine which quorum isappropriate for your environment.

l Node Majority—This quorum is recommended for clusters with an odd numberof nodes. The cluster can handle failures of half of the nodes (rounding up) minusone and still stay online.

l Node and Disk Majority—This quorum is recommended for clusters with aneven number of nodes. The cluster can handle failures of half of the nodes(rounding up), as long as the witness disk remains online, and still stay online. Ifthe witness disk fails, the cluster can handle failures of only half of the nodes(rounding up) minus one and still stay online.

l Node and File Share Majority—This quorum is recommended for clusters withspecial configurations, such asGeoCluster. The cluster can handle failures of halfof the nodes (rounding up), as long as the witness share remains online, and stillstay online. If the witness share fails, the cluster can handle failures of only half ofthe nodes (rounding up) minus one and still stay online.

l No Majority: Disk Only—This quorum is not usually recommended. The clustercan handle failures of all nodes except one and still stay online.

Use the following instructions as a guideline for configuring your Windows 2008 cluster.See your Windows cluster documentation as a complete reference.

1. Login with an account that has administrative rights on the domain and the localmachine.

2. Create the cluster, if it is not already created. See your Windows documentationfor instructions on how to create a cluster.

3. Configure a Node and File ShareMajority quorum. See your Windowsdocumentation for instructions on how to configure the quorum.

4. If you are going to be using Hyper-V, install the Hyper-V server role on all nodes inthe cluster. Make sure that you have the requiredMicrosoft hotfixes applied,including KB958065 which is a failover clustering hotfix and KB950050.

5. Install Double-Take Availability on each node of the cluster. See Installing Double-Take Availability on aWindows server using the installation wizard on page 43.

6. If desired, you can install Double-Take Availability on non-clustered clientmachines if you want to use Cluster Administrator to control the GeoClusterresources. Install Double-Take Availability, selecting theClient ComponentsOnly installation option.

7. If you are going to be using Hyper-V, create your virtual machine fromwithinHyper-V. Be sure to leave the virtual machine off.

683



8. FromFailover Cluster Management, create your application or service group.

If you are creating a file server using clustered file shares, the path for thefile share in the Failover Cluster Management wizard is case-sensitive. Ifthe drive letter is uppercase, the path in the clustered file share wizardmust also be uppercase. If the case does not match, the wizard will failstating the path does not exist.

If your application requires a disk before installation can begin, create anEmpty Service or Application. After your GeoCluster Replicated Diskresource is created, you can delete the Empty Service or Application andDouble-Take will automaticallymove theGeoCluster Replicated Diskresource to available storage for your application installation.

9. If you are using Hyper-V, add your virtual machine resource to the group. Anywarnings about storagemay be disregarded because theGeoCluster ReplicatedDisk will alleviate storage requirements.

684

Establishing GeoCluster protectionTheGeoCluster Replicated Disk resource allows for the real-time copy of data to beavailable on other nodes in the cluster. In the event of a failure and another node takesownership, the GeoCluster Replicated Disk resource is alsomoved to the other nodeand it continues to replicate data, in real-time, to the remaining nodes in the cluster.

The instructions for creating this resource are different depending on your operatingsystem.

l SeeCreating the GeoCluster Replicated Disk Resource onWindows 2003 onpage 685

l SeeCreating the GeoCluster Replicated Disk Resource onWindows 2008 onpage 687

l SeeCreating the GeoCluster Replicated Disk Resource onWindows 2008Hyper-V on page 689

l SeeBringing the resource online on page 691l Taking the resource offline on page 691

Creating the GeoCluster Replicated Disk Resource on Windows2003

1. SelectStart, Programs,Administrative Tools,Cluster Administrator.2. Right-click the group that you want to add a replicated disk to and selectNew,

Resource.3. Specify the following fields on the New Resource dialog box.

l Name—Specify a name that identifies which application, file set, disk, andso on that you are protecting. This namemust be unique within the cluster.

l Description—You can optionally add amore detailed description for thisresource.

l Resource type—Specify GeoCluster Replicated Disk.l Group—The group that you originated the new resource fromwill beselected. Verify that this is the correct group. If it is not, select the correctgroup name.

4. ClickNext to continue.5. TheGeoCluster Replicated Disk resource ensures that an up-to-the-minute copy

of the data resides on all nodes identified in thePossible owners list. All nodesare included in the default, which should not be changed. ClickNext to continue.

6. TheGeoCluster Replicated Disk resource is not dependent on any otherresources. ClickNext to continue.

7. Specify the GeoCluster Replicated Disk parameters using the settings below.l Disk to replicate—Select a disk to replicate from the available volumes.The only volumes that will be displayed are those that meet the followingcriteria.

685

l NTFS volumesl Volumeswhich are not already being replicated by anotherGeoCluster Replicated Disk resource

l Volumes that are not physical disk resourcesl Volumes that do not contain system files (The volume that you bootedWindows fromwill not be displayed.)

l Volumes that exist on all nodes of the clusterl Network—Select the network that you want to use for Double-Takemirroring and replication traffic. If you do not havemultiple networksestablished, you will only be able to select the one network that does exist. Ifyou do not select a network, Double-Take will use DNS to determine anetwork route to use. Ideally, the networks used for various traffic should beseparated. This is dependent on the number of networks that youestablished when you created the cluster and the priority assigned to eachnetwork. For example, if you have two network routes, separate Double-Take and your public traffic. If you have three routes, separate the publictraffic and then separate Double-Take from the cluster heartbeat.

l Interval to check unresponsive nodes—Specify how much time, inseconds, between checks of nodes to see if a Double-Take connection canbemade.

l Delay connection until resources dependent on this one areonline—This option allows you to delay a Double-Take connection until anyresources that have theGeoCluster Replicated Disk resource as adependency are online. By ensuring that all resources that are dependenton theGeoCluster Replicated disk resource are online before starting theconnection, the chance of a conflict occurring because applicationresources are attempting to open files exclusively while Double-Take ismirroring those files is removed.

8. ClickNext to continue.9. An orphan is a file that exists in the target location but is not in the source location.

You can select to delete orphans during amirror.10. ClickNext to continue.11. If you want to configure compression, verify that Enable Compression is

selected. Depending on the compression algorithms available for your operatingsystem, youmay see a slider bar indicating different compression levels. Set thelevel fromminimum tomaximum compression to suit your needs.

12. ClickNext to continue.13. Specify your Double-Takemirroring settings.

l Full Mirror—All files will be sent from the source to the target.l File differences—Only those files that are different based size or date andtime will be sent from the source to the target.

l Send data only if Source is newer than Target—Only those filesthat are newer on the source are sent to the target.

686

If you are using a database application, do not use the neweroption unless you know for certain you need it. With databaseapplications, it is critical that all files, not just some of themthat might be newer, get mirrored.

l Use block checksum—For those files flagged as different, themirror performs a checksum comparison and only sends those blocksthat are different.

l Calculate Replication Set size prior to mirror—Determines the size ofthe protected data set prior to starting themirror. Themirroring status willupdate the percentage complete if the data set size is calculated.

14. ClickFinish to complete the creation of the GeoCluster Replicated Disk resource.15. To control the resource, you can bring it online and take it offline. Neither of these

actions trigger failover. They just control the activity of the resource.

Creating the GeoCluster Replicated Disk Resource on Windows2008

1. SelectStart, Programs,Administrative Tools, Failover Cluster Manager.2. Right-click the application group where you want to add a replicated disk to and

selectAdd a resource,More resources,Add GeoCluster Replicated Disk.3. Right-click on the resource and selectProperties.4. On theConnection Parameters tab, specify the GeoCluster Replicated Disk

connection parameters using the settings below.l Disk to replicate—Select a disk to replicate from the available volumes.The only volumes that will be displayed are those that meet the followingcriteria.

l NTFS volumesl Volumeswhich are not already being replicated by anotherGeoCluster Replicated Disk resource

l Volumes that are not physical disk resourcesl Volumes that do not contain system files (The volume that you bootedWindows fromwill not be displayed.)

l Volumes that exist on all nodes of the clusterl Network to route Double-Take mirroring and replication trafficover—Select the network that you want to use for Double-Takemirroringand replication traffic. If you do not havemultiple networks established, youwill only be able to select the one network that does exist. If you do notselect a network, Double-Take will use DNS to determine a network routeto use. Ideally, the networks used for various traffic should be separated.This is dependent on the number of networks that you established whenyou created the cluster and the priority assigned to each network. Forexample, if you have two network routes, separate Double-Take and your

687

public traffic. If you have three routes, separate the public traffic and thenseparate Double-Take from the cluster heartbeat.



5. On theOrphans tab, you will see the option to delete orphan files. An orphan is afile that exists in the target location but is not in the source location. You can selectto delete orphans during amirror.

6. On theCompression tab, you will see your compression configuration. If youwant to configure compression, verify that Enable Compression is selected.Depending on the compression algorithms available for your operating system,youmay see a slider bar indicating different compression levels. Set the level fromminimum tomaximum compression to suit your needs.

7. On theMirror Properties tab, specify your Double-Takemirroring settings.l Full Mirror—All files will be sent from the source to the target.l File differences—Only those files that are different based size or date andtime will be sent from the source to the target.





8. No other settings are required for the GeoCluster Replicated Disk resource,although there are optional settings available. SeeGeoCluster Replicated Diskresource properties on page 692 for details. ClickOK to save theGeoClusterReplicated Disk configuration changes that youmade.

9. To control the resource, you can bring it online and take it offline. Neither of theseactions trigger failover. They just control the activity of the resource.

688

Creating the GeoCluster Replicated Disk Resource on Windows2008 Hyper-V

1. Create a virtual machine using the Hyper-V Manager. For details, see your Hyper-V documentation.

2. SelectStart, Programs,Administrative Tools, Failover ClusterManagement.

3. Cluster the virtual machine using the High AvailabilityWizard. (Right-click theServices and Applications group and selectConfigure a service orapplication.)

4. Take the virtual machine cluster group offline by right-clicking on it and selectingTake this resource offline.

5. Right-click on the virtual machine cluster group and selectAdd a resource,Moreresources,Add GeoCluster Replicated Disk.

6. Right-click on the resource and selectProperties.7. On theConnection Parameters tab, specify the GeoCluster Replicated Disk

connection parameters using the settings below.l Disk to replicate—Select the volumewhere the virtual machine .vhd file isstored.

l Network to route Double-Take mirroring and replication trafficover—Select the network that you want to use for Double-Takemirroringand replication traffic. If you do not havemultiple networks established, youwill only be able to select the one network that does exist. If you do notselect a network, Double-Take will use DNS to determine a network routeto use. Ideally, the networks used for various traffic should be separated.This is dependent on the number of networks that you established whenyou created the cluster and the priority assigned to each network. Forexample, if you have two network routes, separate Double-Take and yourpublic traffic. If you have three routes, separate the public traffic and thenseparate Double-Take from the cluster heartbeat.



8. On theOrphans tab, you will see the option to delete orphan files. An orphan is afile that exists in the target location but is not in the source location. You can selectto delete orphans during amirror.

9. On theCompression tab, you will see your compression configuration. If youwant to configure compression, verify that Enable Compression is selected.

689

Depending on the compression algorithms available for your operating system,youmay see a slider bar indicating different compression levels. Set the level fromminimum tomaximum compression to suit your needs.

10. On theMirror Properties tab, specify your Double-Takemirroring settings.l Full Mirror—All files will be sent from the source to the target.l File differences—Only those files that are different based size or date andtime will be sent from the source to the target.





11. No other settings are required for the GeoCluster Replicated Disk resource,although there are optional settings available. SeeGeoCluster Replicated Diskresource properties on page 692 for details. ClickOK to save theGeoClusterReplicated Disk configuration changes that youmade.

12. Modify the virtual machine and virtual machine configuration resources and addtheGeoCluster Replicated Disk resource (not the GeoCluster Replicated DiskStatus resource) as a dependency.

690

Bringing the resource onlineTheGeoCluster Replicated Disk resource will appear offline after it is created.When youbring it online, the following actions occur.

1. A Double-Take job is created.2. The job is connected to all of the possible owners specified in the resource (except

the active node which is the source).3. A mirror is initiated to create the baseline copy of data from the active node to all of

the possible owners.4. The drive where themirrored data is located on each of the possible owners is

made read-only to all other applications except Double-Take.5. Real-time replication from the active node to all of the possible owners begins.

If you are usingWindows 2003, right-click the resource and selectBring online.

If you are usingWindows 2008, right-click the resource and selectBring this resourceonline.

Taking the resource offlineWhen you take theGeoCluster Replicated Disk resource offline, the following actionsoccur.

1. Real-time replication from the active node to the possible owners stops.2. The read-only limitation is removed from the corresponding drive letters on the

possible owners.3. The job is disconnected from all of the possible owners.4. The job is deleted.

If you are usingWindows 2003, right-click the resource and select Take offline.

If you are usingWindows 2008, right-click the resource and select Take this resourceoffline.

If the GeoCluster Replicated Disk Resource is offline, it will impact anyapplication depending on it. Data integrity cannot be guaranteed on the othernodes in the cluster.

691

GeoCluster Replicated Disk resource propertiesResource properties are displayed differently inWindows 2003 andWindows 2008. Forexample, the possible owners of a resource is listed on theGeneral tab of the resourceproperties inWindows 2003, while inWindows 2008 they are listed on theAdvancedPolicies tab.

For both operating systems, right-click the resource and selectProperties, when youwant to view or modify the resource properties.

l SeeGeoCluster Replicated Disk properties onWindows 2003 on page 692l SeeGeoCluster Replicated Disk properties onWindows 2008 on page 695

GeoCluster Replicated Disk properties on Windows 2003There are seven properties tabs for the GeoCluster Replicated Disk resource onWindows 2003.

1. General—This tab identifies theName andDescription of the resource and thePossible Owners. If you change the name of the resource, the replication setnamewill not change until the next time the resource is brought online. TheGeoCluster Replicated Disk resourcemust have at least two possible owners tofunction properly. Modifying thePossible Owners list will cause one of thefollowing actions to occur.

l If you add additionalPossible Owners, the GeoCluster Replicated Diskresource will connect the resource’s replication set to the new owners andbegin amirror to each.

l If you removePossible Owners, the GeoCluster Replicated Disk resourcewill disconnect the resource’s replication set from each owner removed.

2. Dependencies—Bydefault, the GeoCluster Replicated Disk resource is notdependent on any other resources.

3. Advanced settings—This tab controls how and whenMSCS handles a failure ofthe resource.

l Do not restart—Select this option if you do not want cluster service torestart the resource if it fails.

l Restart—Select this option if you want cluster service to restart theresource if it fails.

l EnableAffect the group if you want a failure of this resource tomove the group to another node. If you disable this option, clusterservice still attempts to restart the resource using the Threshold andPeriod values, but the failure of the resource will not cause the grouptomove to another node.

l The Threshold andPeriod values determine the number of timescluster service will attempt to restart the failed resource within aspecified period of time beforemoving the group to another node.

l "Looks Alive" poll interval—This setting specifies how often theresource is polled to determine whether it is still running on the active node.

692

You can choose a value from the resource type, or you can specify yourown value.

l "Is Alive" poll interval—This setting designates how often the possibleowners are polled to determine whether the specified disk on each nodecan be written to and read from. You can choose a value from the resourcetype, or you can specify your own value.

l Pending timeout—This value determines how long the resource isallowed to remain in a pending state before it fails. If the resource takeslonger than the time specified to be brought online or taken offline, theresource fails.

For more information on theAdvanced Settings options, see yourWindows documentation.

4. Connection parameters—This tab controls disk replication, network routing,and orphan files for GeoCluster.

l Disk to replicate—The volume to replicatel Network to route Double-Take mirroring and replication trafficover—The network to use for Double-Takemirroring and replication traffic.If you do not havemultiple networks established, you will only be able toselect the one network that does exist. If you do not select a network,GeoCluster will use DNS to determine a network route to use.

Ideally, the networks used for various traffic should be separated. This isdependent on the number of networks that you established when youcreated the cluster and the priority assigned to each network. For example,if you have two network routes, separate GeoCluster and your public traffic.If you have three routes, separate the public traffic and then separateGeoCluster from the cluster heartbeat.

Modifications to either of the first two settingswill not take effect until thenext time the resource is brought online.

l Interval to check unresponsive nodes—The frequency to determinehow often an unresponsive node is checked to see if a Double-Takeconnection can bemade

l Delay connection until resources dependent on this one areonline—This option allows you to delay a Double-Take connection until anyresources that have theGeoCluster Replicated Disk resource as adependency are online. By ensuring that all resources that are dependenton theGeoCluster Replicated disk resource are online before starting theconnection, the chance of a conflict occurring because applicationresources are attempting to open files exclusively while GeoCluster ismirroring those files is removed.

5. Orphans—An orphan is a file that exists in the target location but is not in thesource location. You can select to delete orphans during amirror.

6. Compression—If you want to configure Double-Take compression, verify thatEnable Compression is selected. Depending on the compression algorithmsavailable for your operating system, youmay see a slider bar indicating different

693

compression levels. Set the level fromminimum tomaximum compression to suityour needs.

7. Mirror Properties—This tab controls the Double-Takemirroring process.l Full Mirror—All files in the replication set will be sent from the source to thetarget.

l File differences—Only those files that are different based size or date andtime will be sent from the source to the target.




l Calculate Replication Set size prior to mirror—Determines the size ofthe replication set prior to starting themirror. Themirroring status willupdate the percentage complete if the replication set size is calculated.

694

GeoCluster Replicated Disk properties on Windows 2008There are nine properties tabs for the GeoCluster Replicated Disk resource onWindows2008.

1. General—This tab identifies theName andResource type of the resource. Italso displays the current state of the resource and an additional detailed statusmessage.

2. Dependencies—Bydefault, the GeoCluster Replicated Disk resource is notdependent on any other resources.

3. Policies—This tab controls how and whenMSCS handles a failure of theresource. For more information onPolicies options, see your Windowsdocumentation.

l If resource fails, do no restart—Select this option if you do not wantcluster service to restart the resource if it fails.

l If resource fails, attempt restart on current node—Select this option ifyou want cluster service to restart the resource if it fails. Specify the lengthof time to attempt restarts and the number of restarts to attempt during thatperiod of time.

l If restart is unsuccessful, fail over all resources in this service orapplication—If this option is enabled, the failure of the group will cause theresource tomove to another node. If this option is disabled, the failure of theresource will not cause the resource tomove to another node.

l If all the restart attempts fail, begin restarting again after thespecified period—If this option is enabled, the cluster will delay the lengthof time specified before trying to restart the resource again.

l Pending timeout—This value determines how long the resource isallowed to remain in a pending state before it fails. If the resource takeslonger than the time specified to be brought online or taken offline, theresource fails.

4. Advanced Policies—This tab controls resource specific settings. For moreinformation onAdvanced Policies options, see your Windows documentation.

l Possible owners—All nodes of the cluster are listed. Select or deselectthe nodes that you want to be possible owners.

l If you add additional owners, the GeoCluster Replicated Diskresource will connect the resource’s replication set to the new ownersand begin amirror to each.

l If you remove owners, the GeoCluster Replicated Disk resource willdisconnect the resource’s replication set from each owner removed.

TheGeoCluster Replicated Disk resourcemust have at least twopossible owners to function properly.

l Basic resource health check interval—This setting is formerly known asthe Looks Alive poll interval. It specifies how often the resource is polled todetermine whether it is still running on the active node. You can choose thestandard time period of 5 seconds, or you can specify your own value.

695

l Thorough resource health check interval—This setting is formerlyknown as the Is Alive poll interval. It designates how often the possibleowners are polled to determine whether the specified disk on each nodecan be written to and read from. You can choose the standard time period of1minute, or you can specify your own value.

l Run this resource in a separate Resource Monitor—You shouldenable this option so that eachGeoCluster Replicated Disk resource runs inits ownmonitor.

5. Connection parameters—This tab controls disk replication, network routing,and orphan files for Double-Take.

l Disk to replicate—The volume to replicatel Network to route Double-Take mirroring and replication trafficover—The network to use for Double-Takemirroring and replication traffic.If you do not havemultiple networks established, you will only be able toselect the one network that does exist. If you do not select a network,GeoCluster will use DNS to determine a network route to use.

Ideally, the networks used for various traffic should be separated. This isdependent on the number of networks that you established when youcreated the cluster and the priority assigned to each network. For example,if you have two network routes, separate GeoCluster and your public traffic.If you have three routes, separate the public traffic and then separateGeoCluster from the cluster heartbeat.

Modifications to either of the first two settingswill not take effect until thenext time the resource is brought online.

l Interval to check unresponsive nodes—The frequency to determinehow often an unresponsive node is checked to see if a Double-Takeconnection can bemade

l Delay connection until resources dependent on this one areonline—This option allows you to delay a Double-Take connection until anyresources that have theGeoCluster Replicated Disk resource as adependency are online. By ensuring that all resources that are dependenton theGeoCluster Replicated disk resource are online before starting theconnection, the chance of a conflict occurring because applicationresources are attempting to open files exclusively while GeoCluster ismirroring those files is removed.

6. Orphans—An orphan is a file that exists in the target location but is not in thesource location. You can select to delete orphans during amirror.

7. Compression—If you want to configure Double-Take compression, verify thatEnable Compression is selected. Depending on the compression algorithmsavailable for your operating system, youmay see a slider bar indicating differentcompression levels. Set the level fromminimum tomaximum compression to suityour needs.

8. Online Pending—Because context-sensitive, right-clickmenus are not availablein theWindows 2008 Failover Cluster Administrator, GeoCluster processingcontrols have been added to a properties tab. For details on this tab, seeMonitoring and controlling GeoCluster jobs on page 698.

696

9. Mirror Properties—This tab controls the Double-Takemirroring process.l Full Mirror—All files in the replication set will be sent from the source to thetarget.

l File differences—Only those files that are different based size or date andtime will be sent from the source to the target.




l Calculate Replication Set size prior to mirror—Determines the size ofthe replication set prior to starting themirror. Themirroring status willupdate the percentage complete if the replication set size is calculated.

697

Monitoring and controlling GeoCluster jobsTheDouble-Take job created by theGeoCluster will be displayed as an Legacy Job ontheManage Jobs page of the Double-Take Console. You will have limited control overthe job, including taking andmanaging snapshots, viewing the job log, initiatingmirrorsand verifications, setting bandwidth limitations, deleting orphan files, and pausing andresuming the target.

If you delete the job, the GeoCluster Replicated Disk resource will not be deleted. Youwill have to remove and readd the passive nodes to the resource to re-create the jobwithout impacting production. If you are not worried about impacting production, you cantake the resource offline and then bring it back online to re-create the job.

Ideally, you should use the standardWindows cluster tools to monitor the status of theresource. See your cluster documentation for details onmonitoring a cluster resource.

You can also use the following information to help youmonitor the GeoClusterReplicated Disk resource.

l Do not use the Initiate Failure feature of Cluster Administrator to test failover ofGeoCluster resources. Use other test methods, such asmanuallymoving thegroup or unplugging the owning nodes network cable.

l Do not use theAutomatic Failback feature of Cluster Administrator. If you needto return ownership to the original node, wait until GeoCluster has completedmirroring from the new owning node back to the original owning node and thenmanuallymove the group.

l If you change an IP address on any node of the cluster, youmust stop and restartthe cluster service on all of the nodes in the cluster in order for GeoCluster todetect the new IP address.

l If youmust reboot the owning node, you shouldmove all of your cluster groups toanother node before the reboot. This will ensure data integrity and allow you tomake sure the applications come online before the node is rebooted.

698

Resolving an online pending GeoCluster Replicated DiskresourceWhen theGeoCluster Replicated Disk resource is in an online pending state, you areprotected from possible data corruption. If you are usingWindows 2003, review thedescription of the GeoCluster Replicated Disk Status resource to see why theGeoCluster Replicated Disk resource is in the online pending state. If you are usingWindows 2008, you can see the online pending status directly in the description of theGeoCluster Replicated Disk resource. If the pending state were bypassed, the nodewhere you are trying to bring the resource online would have incomplete data, whichwould then be replicated to the other nodes in the cluster. This state safeguards you fromcorrupting your data.

There are different options for resolving an online pending state, depending on whetheryour operating system supports snapshots. Therefore, some of the following optionsmay not be displayed or may be disabled if they are not valid for your configuration.

If you are usingWindows 2003, right-click on the online pending resource and select thedesired control. The controls are described in the following tables.

If you are usingWindows 2008, right-click the online pending resource, selectProperties, select theOnline Pending tab, and click the desired control. The controlsare described in the following tables.

l Revertl Windows 2003 menu—Revert to snapshotl Windows 2008 menu—Revert Snapshotl Description—If you have a snapshot of the target data available, you canrevert to that data. If you revert to a snapshot, any data changesmade afterthe snapshot’s specified date and time will be lost. A Double-Takeconnection will be established to replicate the node’s data (at the snapshotpoint-in-time) to the other nodes.

l Discard queuel Windows 2003 menu—Discard target queuel Windows 2008 menu—Discard Queuel Description—If you have data in the target queue, you can discard thatdata. If you discard the queued data, you will lose the changes associatedwith that datamade on the previously owning node. A Double-Takeconnection will be established to replicate the node’s data (without the datathat was in queue) to the other nodes.

l Offline or faill Windows 2003 menu—Force ResourceOfflinel Windows 2008 menu—Fail Resourcel Description—If you are usingWindows 2003, you can force the resourceoffline. If you are usingWindows 2008, you can fail the resource. In eithercase, no Double-Take connection will be established.

699

l Verify groupl Windows 2003 menu—Verify Groupl Windows 2008 menu—Verify Groupl Description—With this option and snapshot capability, you can test thedata on the node before deciding whether to use it. If you select this option,a snapshot of the node’s current Double-Take data will be taken, the diskwill come online, but the GeoCluster Replicated Disk resource will not comeonline, allowing you to check the data. (Thismeans there is no Double-Take connection established at this time.) Once the snapshot is taken, youcan test the data on the node to see if it is viable. Make sure you preventuser accesswhile you are verifying the data. Once you have tested the data,you need to right-click on the online pending resource again and accept orreject the data.

l Accept datal Windows 2003 menu—Accept Datal Windows 2008 menu—Acceptl Description—If you accept the data, the current data on the node will beused, and a Double-Take connection will be established to replicate thecurrent node’s data to the other nodes. If any other nodes in the clustercontain more recent data, this node will overwrite that data and it will be lost.

l Reject datal Windows 2003 menu—Reject Datal Windows 2008 menu—Rejectl Description—If you reject the data, the node will be reverted to thesnapshot that was taken when you selected theVerify Group option. Anychangesmade on the node after that snapshot was created will be lost. Thisoption essentially takes you back to where you were, allowing you theopportunity to check other nodes for more recent data.

If you havemultiple GeoCluster Replicated Disks in the same group andhave selected to reject the data after verifying the group, the rejectionprocessingmay take several minutes.

700

GeoCluster Replicated Disk Status ResourceThe function of the GeoCluster Replicated Disk Status resource (also displayed asGRDStatus) varies betweenWindows 2003 andWindows 2008. In both operating systems, itis automatically created when the first GeoCluster Replicated Disk resource is created ina group. Once the status resource is created, it will exist as long as there is a GeoClusterReplicated Disk resource in the group.When the last GeoCluster Replicated Diskresource in a group is deleted, the status resource will be deleted. Only one statusresource is created per group.If the resource is deleted, it will automatically be re-created.

If you are usingWindows 2003, the description of the status resource corresponds tovarious states of your Double-Take data. By reviewing the status descriptions, you cantell at-a-glance the state of your Double-Take data. If you are usingWindows 2008,these status descriptions are seen directly in the GeoCluster Replicated Disk resourcedescription, rather than the status resource.

For example, youmay see the status "The status of all targets is OK." This indicates thedata on each target node is in a good state. Another messagemay be "Target target_name is queuing. Data in queue on target." This indicates the data on the specified targetis not up-to-date. Because there is data in queue on the target, that has not been writtento disk yet, the target data is out-of-date. Or youmay see either of the following statusdescriptions.

l Target target_name is pending. Data integrity not guaranteed.l Target target_name is suspect. Data integrity not guaranteed.

Thesemessages indicate the data on the specified target node is not in a good state.This could be because amirror is in progress, an operation has been dropped on thetarget, or another Double-Take processing issue.As long as the status is pending, dataintegrity cannot be guaranteed on the specified target node. Check the Double-Takelogs for more information. See Log files on page 704 for more details.

The text of the descriptionsmay vary betweenWindows 2003 andWindows 2008.

Another function of the status resource, for bothWindows 2003 andWindows 2008, is tokeep you frommoving theGeoCluster Replicated Disk resource to another node at thewrong time and potentially corrupting your data. If the GeoCluster Replicated Diskresource wasmoved while the status resource is in a pending or queuing state, the newnode would have incomplete data, which would then be replicated to the other nodes inthe cluster. This resource safeguards you from corrupting your data. This happens byremoving passive nodes as possible owners and discarding anymanual changesmadeto the possible owners list.

701

Chapter 18 Simulating protectionDouble-Take offers a simple way for you to simulate protection in order to generatestatistics that can be used to approximate the time and amount of bandwidth that aparticular source and job type will use when actively established. This simulation usesthe TDU (Throughput Diagnostics Utility), which is a built-in null (non-existent) target thatsimulates a real job. No data is actually transmitted across the network. Since there is notrue job, this diagnostics utility helps you plan your implementation strategy.

Before and after simulating a job, you should gather network and system informationspecific to Double-Take operations. Use the DTInfo utility to automatically collect thisdata. It gathers Double-Take log files; Double-Take and system settings; networkconfiguration information such as IP,WINS and DNS addresses; and other data whichmay be necessary in evaluating Double-Take performance. The DTInfo utility can befound on the product CD, in the Double-Take installation directory, or on the VisionSolutions support web site.

1. From the source where you will be running the TDU, run DTInfo.exe. It may takeseveral minutes for DTInfo to finish processing. After DTInfo processing iscomplete, a \support subdirectory will automatically be created in the Double-Takeinstallation directory. (The default installation directory is \ProgramFiles\VisionSolutions\Double-Take.) A .zip file will contain the information gathered fromDTInfo. The file name is based on themachine name. To distinguish this file fromthe next time you run DTInfo, append a unique identifier, perhaps the date andtime, to the end of the file name.

2. Establish a protection job, noting the following caveats.l The TDU is not available for the following job types.

l Full server to ESX appliancel V to ESXl V to Hyper-V

l When you get to theChoose Target Server page in the workflow, selecttheDiagnostics target.

l When you get to theSet Options page in the workflow, some options foryour selected job type will not be displayed because they are not applicable.For example, if you have selected a job type for an ESX server, you will notneed to specify options for the target replica virtual machine because thereis no actual target with the TDU.

3. Once you have established your job, you should ideally let it run for several days togather accurate data for your network and source server usage. The simulationdata will be logged to the Double-Take statistics file. SeeStatistics on page 715.

4. After your simulation is complete, repeat step 1 to run DTInfo again, appendingthe new unique identifier to the end of the new .zip file.

702

Chapter 19Monitoring toolsOutside of the Double-Take consoles, you have other general monitoring tools availablefor all job types.

l Log files on page 704l Statistics on page 715l Error codes on page 725l WindowsEvent messages on page 731l PerformanceMonitor on page 817l Microsoft SystemsCenter OperationsManager 2007 on page 826l SNMP on page 829

703

Log filesDouble-Take generates log files to gather alerts, which are notification, warning, anderror messages.

l Double-Take log—This log records data from the Double-Take service, alsoreferred to as the Double-Take engine. The Double-Take service controls the datamovement functions like Double-Takemirroring and replication. This log file canbe viewed fromwithin the Double-Take Console (seeViewing the log files throughthe Double-Take Console on page 705) or through any standard text editor (seeViewing the log files through a text editor on page 709). You can also filter the datain the log file using the Double-Take LogViewer utility. (see Filtering the log filewith LogViewer on page 713).

l Double-Take Management Service log—This log records data from theDouble-TakeManagement Service. It controls all non-datamovement aspects ofeach job. This log file can be viewed fromwithin the Double-Take Console (seeViewing the log files through the Double-Take Console on page 705) or throughany standard text editor (seeViewing the log files through a text editor on page709).

l Double-Take job log—This log records job specificmessage. There is a uniquejob log for each job you create. This log file can be viewed fromwithin the Double-Take Console (seeViewing the log files through the Double-Take Console onpage 705) or through any standard text editor (seeViewing the log files through atext editor on page 709).

l Double-Take Console log—This log records data and user interaction from theDouble-Take Console. This log file can be viewed through any standard text editor(seeViewing the log files through a text editor on page 709).

For cluster environments, be sure and review the log files on all nodes of thecluster.

704

Viewing the log files through the Double-Take ConsoleYou can view the Double-Take, Double-TakeManagement Service, job, and Double-Take Console log files through the Double-Take Console.

Viewing the Double-Take and Double-Take Management ServicelogsYou can view the Double-Take and Double-TakeManagement Service log files throughthe Double-Take Console using either of these twomethods.

l On theManage Servers page, highlight a server in the list and clickView ServerLogs from the toolbar.

l On theManage Jobs page, right-click a job and selectView Logs. Select eitherthe source server log or the target server log.

Separate logging windows allow you to continue working in the Double-Take Consolewhile monitoring logmessages. You can openmultiple logging windows for multipleservers. When the Double-Take Console is closed, all logging windowswill automaticallyclose.

705

The following table identifies the controls and the table columns in theServer logswindow.

Start


Pause

This button pauses the addition and scrolling of new messages in thewindow. This is only for theServer logswindow. Themessages arestill logged to their respective files on the server.

Copy

This button copies themessages selected in theServer logswindowto theWindows clipboard.

Clear

This button clears theServer logswindow. Themessages are notcleared from the respective files on the server. If you want to view all ofthemessages again, close and reopen theServer logswindow.

Filter

From the drop-down list, you can select to view all logmessages or onlythosemessages from the Double-Take log or the Double-TakeManagement Service log.

Time


Description


Service

This column in the table indicates if themessage is from the Double-Take log or the Double-TakeManagement Service log.

706

Viewing the job log fileYou can view a job log file through the Double-Take Console by right-clickingView JobLog from the toolbar on theManage Jobs page. Separate logging windows allow you tocontinue working in the Double-Take Console while monitoring logmessages. You canopenmultiple logging windows for multiple jobs. When the Double-Take Console isclosed, all logging windowswill automatically close.


Start


Pause


Copy


707

Clear


Time


Description


Viewing the Double-Take Console log fileYou can view the Double-Take Console log file by using the following instructions.

1. Select Tools,Options.2. Expand theDiagnostics section, if necessary.3. ClickView Log File.4. ClickCancel to return back to the console page you were on previously. (Unless

you were in themiddle of a job creation workflow, in which case you will bereturned to the beginning of the workflow.)

The log file is opened in the default text editor. The file will remain open until you close.

708

Viewing the log files through a text editorYou can view the Double-Take, Double-TakeManagement Service, job, and Double-Take Console log files through any text editor.

Viewing the Double-Take logThis log file is located in the same directory where you installed Double-Take. By default,this is \ProgramFiles\Vision Solutions\Double-Take.

The Double-Take log file consists of a base name, a series number, and an extension.The base name is dtlog and the extension is .dtl. The series number ranges from 1 to999. For example, Double-Take begins loggingmessages to dtlog1.dtl. When this filereaches itsmaximum size, which by default is 5MB, the next log file will be written todtlog2.dtl. As long as logmessages continue to be written, files dtlog3.dtl, dtlog4.dtl, anddtlog5.dtl will be opened and filled. When themaximumnumber of files is reached, whichby default is 5, the oldest file is deleted. For example, when dtlog6.dtl is created,dtlog1.dtl is deleted, and when dtlog7.dtl is created, dtlog2.dtl is deleted.When filedtlog999.dtl is created and filled, dtlog1.dtl will be re-created and Double-Take willcontinue writing logmessages to that file. The Double-Take log file settings can bemodified for each server. See Log file properties on page 106 for details.

The following list describes the information found in each column of the log file.

1. Date themessage was generated2. Time themessage was generated3. Process ID4. Thread ID5. Sequence number is an incremental counter that assigns a unique number to

eachmessage6. The type or level of message displayed - 1 for warning or error message and 2 for

informational message7. Message ID, if any8. Message text

02/14/2012 05:26:32.954 1360 3668 1 2 0 Using default heap02/14/2012 05:26:33.048 1360 3668 3 2 0 Winsock v2.2Enabled02/14/2012 05:26:35.689 1360 3668 5 2 0 Virtual operating system detected.02/14/2012 05:26:35.689 1360 3668 6 2 69 Kernel Starting on BETA ip://112.42.74.30:6320 V02/14/2012 05:26:35.689 1360 3668 7 2 0 WARNING: Unable to determine Firewall status, ass02/14/2012 05:26:35.751 1360 3668 8 2 69 Kernel Started on BETA ip://112.42.74.30:6320 Ve02/14/2012 05:26:35.954 1360 3668 9 2 503008 LoadNL set state to IDLE02/14/2012 05:26:35.954 1360 3944 10 2 503008 Op Retrieval: entering standard retrieval m02/14/2012 05:26:35.954 1360 3020 11 2 503008 Op Parsing: entering standard parsing mode02/14/2012 05:26:36.017 1360 3668 12 2 0 The local security process has been added to the02/14/2012 05:26:38.751 1360 3668 14 2 0 SourceRelationships::UpdateSourceMap:GUID(A0779C02/14/2012 05:26:38.751 1360 3668 15 2 0 Source IP '10.10.10.29:6320' for ServerID 'GUID(02/14/2012 05:26:38.814 1360 3668 16 2 52000 New Target Internals created for 10.10.10.2902/14/2012 05:26:38.876 1360 3668 17 2 302004 Queuing to disk has started02/14/2012 05:26:38.876 1360 3668 18 2 302005 Disk Queue is empty - Queuing to disk has s02/14/2012 05:26:38.939 1360 3668 19 2 52501 Target module loaded successfully02/14/2012 05:26:39.064 1360 3816 20 2 71 Originator Attempting ip://10.10.10.29:632002/14/2012 05:26:39.157 1360 2260 21 2 72 Connection request from IP address 112.42.74.30

709

Viewing the Double-Take Management Service logThis file is located in the \Service\Logs subdirectory where you installed Double-Take.

The Double-TakeManagement Service log file consists of a base name, an optionaldate, an optional series number, and an extension. The base name isManagementService and the extension is .log. When this file reaches itsmaximum size,10MB, the file will be renamedwith the current date in year, month, day format. Forexample, it might beManagementService.20120207.log. The latest logmessages arethen stored inManagementService.log. If themain file fills again on the same day, then aseries number will be used. In this case, theManagementService.log file will be renamedtoManagementService.20120207.1.log. If themain file is filled on a different day, thatdate will be specified. In each case, the latest logmessageswill be stored inManagementService.log.When themaximumnumber of files is reached, which is 5, theoldest file is deleted. TheManagement Service log file settings cannot bemodified.

[2012-02-14 05:27:19] Verbose: Successfully opened service host JobManager (PID:2512, TID[2012-02-14 05:27:19] Verbose: Successfully opened service host WorkloadManager (PID:2512[2012-02-14 05:27:19] Verbose: Successfully opened service host ManagementService (PID:25[2012-02-14 05:27:19] Verbose: Successfully opened service host CoreEngine (PID:2512, TID[2012-02-14 05:27:19] Verbose: Successfully opened service host CoreSystemState (PID:2512[2012-02-14 05:27:19] Verbose: Successfully opened service host DiskManager (PID:2512, TI[2012-02-14 05:27:20] Verbose: Completed: 10.10.10.30 (PID:2512, TID:9, AID:fce50580-0307[2012-02-14 05:27:20] Information: The Double-Take engine is initialized. (PID:2512, TID:[2012-02-14 05:27:20] Verbose: The Double-Take engine source module is initialized. (PID:[2012-02-14 05:27:20] Verbose: The Double-Take engine target module is initialized. (PID:[2012-02-14 05:27:20] Verbose: Removing Connection: Id = f34dcb1e-ac6b-4267-a891-5e45629b[2012-02-14 05:27:20] Verbose: The Double-Take engine failover module is initialized. (PI[2012-02-14 05:27:21] Verbose: Removing Monitor: Id = 5fa3b4eb-ea21-4e47-976e-25fd62c10c5[2012-02-14 06:48:44] Verbose: Entered TopState (PID:2512, TID:13, AID:7c5f8158-16f0-4330[2012-02-14 06:48:44] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:7c5f8158[2012-02-14 06:48:44] Verbose: Changing to StoppedState from UninitializedState in respon[2012-02-14 06:48:44] Verbose: Exited UninitializedState (PID:2512, TID:13, AID:7c5f8158-[2012-02-14 06:48:44] Verbose: Entered InitializedState (PID:2512, TID:13, AID:7c5f8158-1

710

Viewing the job logThis file is located on the target server in the \Service\Logs subdirectory where youinstalled Double-Take.

The job log file consists of a global unique identifier (GUID) for the job and the job name.When this file reaches itsmaximum size, 10MB, the file will be renamedwith the currentdate in year, month, day format. For example, it might be a6cbf990-ba67-403d-855f-5bb44c18e1d6 (alpha to beta).20120207.log. The latest logmessages are then stored inthe baseGUID_name.log file. If themain file fills again on the same day, then a seriesnumber will be used. In this case, the example file would be renamed to a6cbf990-ba67-403d-855f-5bb44c18e1d6 (alpha to beta).20120207.1.log. If themain file is filled on adifferent day, that date will be specified. In each case, the latest logmessageswill bestored in themain GUID_name.log file. When themaximumnumber of files is reached,which is 5, the oldest file is deleted. The job log file settings cannot bemodified.

[2012-02-14 06:48:46] Verbose: Entered TopState (PID:2512, TID:13, AID:e6246673-57a9-4a25[2012-02-14 06:48:46] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:e6246673[2012-02-14 06:48:46] Information: Target beta is a NOT a cluster. Setting JobFilePath de[2012-02-14 06:48:47] Verbose: Entered TopState (PID:2512, TID:13, AID:e6246673-57a9-4a25[2012-02-14 06:48:47] Verbose: Entered UninitializedState (PID:2512, TID:13, AID:e6246673[2012-02-14 06:48:47] Verbose: Attaching to engine monitor 00000000-0000-0000-0000-000000[2012-02-14 06:48:47] Verbose: Changing to StoppedState from UninitializedState in respon[2012-02-14 06:48:47] Verbose: Exited UninitializedState (PID:2512, TID:5, AID:e6246673-5[2012-02-14 06:48:47] Verbose: Entered InitializedState (PID:2512, TID:5, AID:e6246673-57[2012-02-14 06:48:47] Verbose: Entered StoppedState (PID:2512, TID:5, AID:e6246673-57a9-4[2012-02-14 06:48:47] Verbose: Stopping monitor ab2268f7-85c6-4b68-819c-3d2912f5380a: nam[2012-02-14 06:48:47] Information: Successfully created monitor 618b51de-70f0-418b-9869-1[2012-02-14 06:48:47] Verbose: Changing to StoppedState from UninitializedState in respon[2012-02-14 06:48:47] Verbose: Exited UninitializedState (PID:2512, TID:13, AID:e6246673-[2012-02-14 06:48:47] Verbose: Entered InitializedState (PID:2512, TID:13, AID:e6246673-5[2012-02-14 06:48:47] Verbose: Entered StoppedState (PID:2512, TID:13, AID:e6246673-57a9-[2012-02-14 06:48:47] Verbose: Changing to StartingState from StoppedState in response to[2012-02-14 06:48:47] Verbose: Exited StoppedState (PID:2512, TID:13, AID:5decb7a7-ff7a-4[2012-02-14 06:48:47] Verbose: Entered StartingState (PID:2512, TID:13, AID:5decb7a7-ff7a[2012-02-14 06:48:48] Information: Event log entry written: '6008'. (PID:2512, TID:13, AI[2012-02-14 06:48:48] Verbose: Target beta is not clustered (PID:2512, TID:13, AID:5decb7[2012-02-14 06:48:48] Verbose: Changing to RunningState from StoppedState in response to[2012-02-14 06:48:48] Verbose: Exited StoppedState (PID:2512, TID:14, AID:e6246673-57a9-4[2012-02-14 06:48:48] Verbose: Entered RunningState (PID:2512, TID:14, AID:e6246673-57a9-[2012-02-14 06:48:48] Verbose: Starting monitor ab2268f7-85c6-4b68-819c-3d2912f5380a: nam

711

Viewing the Double-Take Console logThis file is called Double-Take Console.log and its location depends on your operatingsystem. If you are usingWindows 2008, the file will be located in \Users\<your username>\AppData\Local\Vision Solutions\Double-Take Console\Logs. If you are usingWindows 2003, the log file will be located in \Documents and Settings\<your username>\Local Settings\Application Data\Vision Solutions\Double-Take Console\Logs.Note that these are hidden locations, so you will have to search directly for the file nameor display hidden files to browse for it. Also note that the log file is dependent on the userwho is logged in, so there will bemultiple Double-Take Console log files if you havemultiple Double-Take users.

[2012-02-14 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.VRAConsol[2012-02-14 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.VRABindin[2012-02-14 05:28:01] Verbose: Activating DoubleTake.Virtualization.VRA.Console.Model.VRA[2012-02-14 05:28:02] Verbose: Rendering Tier = 0 (PID:620, TID:1, AID:00000000-0000-0000[2012-02-14 05:28:02] Verbose: Component Versions: Microsoft .NET Framework: 2.0.50727.3053 Double-Take Console Framework: 6.0.0.1023 Double-Take Applications Console Library: 6.0.0.1023 Double-Take Dashboard Console Library: 6.0.0.1023 Double-Take Diagnostics Console Library: 6.0.0.1023 Double-Take Full Server Console Library: 6.0.0.1023 Double-Take Move Console Library: 6.0.0.1023 Double-Take for Hyper-V Console Library: 6.0.0.1023 Double-Take Virtualization UVRA Console Library: 6.0.0.1023 Double-Take Virtualization VRA Console Library: 6.0.0.1023 (PID:620, TID:1, AID:2e1d2989-7b38-4c9a-93b9-063a3c12b6f3 - Extensibility)[2012-02-14 05:29:33] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0[2012-02-14 05:40:52] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0[2012-02-14 06:06:38] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0[2012-02-14 06:25:02] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0[2012-02-14 06:47:48] Information: Qualify truealpha (PID:620, TID:1, AID:00000000-0000-0[2012-02-14 06:48:46] Verbose: Creating job with options: <JobOptions xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas <ApplicationOptions i:nil="true" /> <BandwidthOptions xmlns:d2p1="http://schemas.datacontract.org/2004/07/DoubleTake.Jo <d2p1:Entries i:nil="true" /> <d2p1:Limit>0</d2p1:Limit> <d2p1:Mode>NotLimited</d2p1:Mode> <d2p1:Specifications xmlns:d3p1="http://schemas.datacontract.org/2004/07/DoubleTa </BandwidthOptions> <ClusterOptions>

712

Filtering the log file with LogViewerYou can filter the Double-Take log file through the Double-Take LogViewer utility. Froma command prompt, use the LogViewer command from the directory where Double-Take is installed. PressCtrl-C to exit back to the command prompt.

Command

LOGVIEWER

Description

TheDouble-Take logging utility that filtersDouble-Take log files

Syntax

LOGVIEWER [-PATH <path>] [-TYPE <number>] [-INCLUDE<list>] [-EXCLUDE <list>] [-NODATE] [-NOTIME] [-NOPID] [-NOTID] [-NOSEQ] [-NOTYPE] [-NOID] [-HELP]

Options

l PATH path—Specify the full path to the log filel TYPE number—Allows you to filter themessages that aredisplayed. Specify 1 to display warning and error messages orspecify 2 to display warnings, errors, and informationmessages.

l INCLUDE—Only includes specified IDs. All other IDswill not bedisplayed in the output

l EXCLUDE—Excludes specified IDs. Ignore the specified IDs anddisplay all others

l list—A comma-separated list of IDs or ID ranges that follows theINCLUDE and EXCLUDE switches. A space should separate theswitch from the list but within the list, there should be no spaces.Ranges are specified with a begin and end number and separatedwith a dash (-).

l NODATE—Does not display the date in the outputl NOTIME—Does not display the time in the outputl NOPID—Does not display the process ID in the outputl NOTID—Does not display the thread ID in the outputl NOSEQ—Does not display the sequence number in the outputl NOTYPE—Does not display themessage type number in the output

l NOID—Does not display the LogViewer ID in the outputl HELP—Displays the command options

713

Examples

l LogViewer -type 2l LogViewer -include 200,400-500,10000-15000

Notes

The default setting is -type 2 which displays both type 1 and 2messages.

714

StatisticsStatistics logging is the process of taking snapshots of Double-Take statistical data. Thedata can be written to a file for future use. Changes to the statistics file configuration aredetected and applied immediately without restarting the Double-Take service.

The statistics log file created is a binary file. To view the log file, youmust run the DTStatutility from the command prompt.

Sample DTStat output

=================================0/11/10 12:48:05:2040=================================SYSTEMALLOCATOR::Total Bytes: 0IQALLOCATOR::Total Bytes: 0SECURITY::Logins : 1 FailedLogins : 0KERNEL::SourceState: 2 TargetState: 1 Start Time: Tue Sep 11 12:45:26 2007RepOpsGenerated: 436845 RepBytesGenerated: 0MirOpsGenerated: 3316423 MirBytesGenerated: 108352749214952 FailedMirrorCount: 0 FailedRepCount: 0 ActFailCount: 0 TargetOpenHandles: 0 DriverQueuePercent: 0TARGET:: PeerAddress: 10.10.1.104 LocalAddress: 10.10.1.104 Ops Received: 25 Mirror Ops Received: 23 Retries: 0 OpsDropped: 0 Ops Remaining: 0 Orphan Files Removed: 0 Orphan Directories Removed: 0 Orphan Bytes Removed: 0 Bytes In Target Queue: 0 Bytes In Target Disk Queue: 0 TasksSucceeded: 0 TasksFailed: 0 TasksIgnored: 0SOURCE::autoDisConnects : 0 autoReConnects : 1 lastFileTouched : /log/data_fileCONNECTION:: conPeerAddress: 10.10.1.104 connectTime: Tue Sep 11 12:45:34 2007 conState: 1 conOpsInCmdQueue: 0 conOpsInAckQueue: 0 conOpsInRepQueue: 0 conOpsInMirQueue: 0 conBytesInRepQueue: 0 conOpsTx: 27 conBytesInMirQueue: 0 conBytesTx: 14952687269 conBytesCompressedTx: 14952 conOpsRx: 201127 conBytesRx: 647062280 conResentOpCount: 0 conBytesInDiskQueue: 0 conBandwidthLimit: 429496295 conBytesSkipped: 22867624 conMirrorBytesRemain: 0 conMirrorPercent: 100.0% conTaskCmdsSubmitted: 0 conTaskCmdsQueued: 0 conTasksSucceeded: 0 conTasksFailed: 0 conTasksIgnored: 0

715

Viewing the statistics fileThe statistics log file created is a binary file. To view the log file, youmust run the DTStatutility from a command prompt. From the directory where Double-Take is installed, runthe DTStat command.

Command

DTSTAT

Description

Starts the DTStats statistics logging utility from a command prompt

Syntax

DTSTAT [-p][-i <interval>][-t <filename>] [-f <filename>] [-s<filename>] [-st <filename>][-IP <address>] [-START<mm/dd/yyyyhh:mm>][-STOP <mm/dd/yyyyhh:mm>] [-SERVER<ip_address> <port_number>]

Options

l -p—Do not print the output to the screen. This option will increasethe speed of the output to files.

l -i interval—Refresh from sharedmemory every interval secondsl -t filename—Save the data frommemory to the specified binary filefilename

l -f filename—Reads from a previously saved binary file, filename,that was generated using the -t option instead of reading frommemory

l -s filename—Saves only the connection data from the data inmemory to an ASCII, comma-delimited file, filename

l -st filename—Saves only the target data from the data in memory toan ASCII, comma-delimited file, filename

l -f filename1 -s filename2—Saves only the connection data from apreviously saved binary file, filename1, to an ASCII, comma-delimited file, filename2

l -f filename1 -st filename2—Saves only the target data from apreviously saved binary file, filename1, to an ASCII, comma-delimited file, filename2

l -IP address—Filters out the specified address in the IP addressfield and prints only those entries. Specifymore than one IP addressby separating them by a comma.

l -STARTmm/dd/yyyyhh:mm—Filters out any data prior to thespecified date and time

l -STOPmm/dd/yyyyhh:mm—Filters out any data after the specifieddate and time

716

l -SERVER ip_address port_number—Connects DTStat to thespecified IP address using the specified port number instead of to thelocal machine

Examples

l DTStat -p -f statistic.sts -s statistic.csvl DTStat -p -f statistic.sts -st statistic.csv

Notes

l This command is not case-sensitive.l If no options are specified, DTStat will print the output to the screenat an interval of every one second.

l If the statistics are not changing, DTStat will discontinue writing untilstatistics begin updating again.

717

StatisticsThe following table identifies the Double-Take statistics.

The categories you see will depend on the function of your server (source,target, or both).

If you havemultiple IP addresses connected to one target server, you will seemultiple Target sections for each IP address.

Statistic values are cumulative. For example if Kernel, RepBytesGenerated is10000 at 1:00pm and 25000 at 2:00pm, the difference is 15000 and that is theamount of change that occurred within that one hour.

If you convert your statistics output to an ASCII, comma-delimited file using thedtstat -s option, keep inmind the following differences.

l The statistic labels will be slightly different in the ASCII file than in the followingtable.

l The statistics will appear in a different order in the ASCII file than in thefollowing table.

l The statistics in the Target Category in the following table are not included inthe ASCII file.

l The Kernel statistic Target Open Handles is not included in the ASCII file.l The ASCII file contains aManaged Pagefile Alloc statistic which is no longerused.

Date/Time Stamp

The date and time that the snapshot was taken. This is the date andtime that each statistic was logged. By default, these are generatedonce a second, as long as there are statistics being generated. Ifmirroring/replication is idle, then DTStat will be idle aswell.

System Allocator, Total Bytes

The number of bytes currently allocated to the system pagefile

IQAllocator, Total Bytes

The number of bytes currently allocated to the intermediate queue

Security, Logins

The number of successful login attempts

Security, Failed Logins

The number of failed login attempts

718

Kernel, SourceState

l 0—Source is not runningl 1—Source is running without the replication driverl 2—Source is running with the replication driver

Kernel, TargetState

l 0—Target is not runningl 1—Target is running

Kernel, Start Time

Date and time stamp indicating when the Double-Take service wasloaded

Kernel, RepOpsGenerated

The number of replication operations generated by the file systemdriver. An op is a file system operation. Double-Take replicates data bysending the file system operations across the network to the target.RepOpsGenerated indicates the number of file system operations thathave been generated by replication.

Kernel, RepBytesGenerated

The number of replication bytes generated by the file system driver.This is the number of bytes generated during replication. In otherwords, this is roughly the amount of traffic being sent across thenetwork that is generated by replication. It does not take into accountTCP/IP overhead (headers and such).

Kernel, MirOpsGenerated

The number of mirror operations transmitted to the target. Mirroring iscompleted by transmitting the file system operations necessary togenerate the files on the target. This statistic indicates the number of filesystem operations that were transmitted during the initial mirror. It willcontinue to increase until themirror is complete. Any subsequentremirrors will reset this field to zero and increment from there.

Kernel, MirBytesGenerated

The number of mirror bytes transmitted to the target. This is the numberof bytes generated duringmirroring. In other words, this is roughly theamount of traffic being sent across the network that is generated by themirror. It does not take into account TCP/IP overhead (headers andsuch). Again, any subsequent remirror will reset this field to zero andincrement from there.

Kernel, FailedMirrorCount

The number of mirror operations that failed due to an error reading thefile from the disk

719

Kernel, FailedRepCount

The number of replication operations that failed due to an error readingthe file from the disk

Kernel, ActFailCount

The number of activation code failures when loading the source ortarget. Activation codes can be bad for reasons such as: expiration ofevaluation codes, duplicate codes, incorrect codes, etc.

Kernel, TargetOpenHandles

The number of handles currently open on the target

Kernel, DriverQueuePercent

The amount of throttling calculated as a percentage of the stopreplicating limit

Target, PeerAddress

The IP address of the sourcemachine

Target, LocalAddress

The IP address of the target machine.

Target, Ops Received

The total number of operations received by thismachine as a targetsince the Double-Take service was loaded

Target, Mirror Ops Received

The total number of mirror operations received by thismachine as atarget since the Double-Take service was loaded. This number doesnot reset to zero for remirrors.

Target, Retries

The number of retries performed before all operationswere completed

Target, OpsDropped

The number of operations skipped during a differencemirror. During adifferencemirror, if Double-Take detects that there have been nochanges to a file, then it will indicate the number of operations it did notsend for this file in this field.

Target, Ops Remaining

The total number of operations that are left in the target queue

Target, Orphan Files Removed

The number of orphan files removed from the target machine

720

Target, Orphan Directories Removed

The number of orphan directories removed from the target machine

Target, Orphan Bytes Removed

The number of orphan bytes removed from the target machine

Target, Bytes In Target Queue

The number of bytes currently in the systemmemory queue on thetarget

Target. Bytes In Target Disk Queue

The number of bytes currently in the disk queue on the target

Target, TasksSucceeded

The number of task commands that have succeeded on the target

Target, TasksFailed

The number of task commands that have failed on the target

Target, TasksIgnored

The number of task commands that have been ignored on the target

Source, autoDisConnects

The number of automatic disconnects since starting Double-Take.Auto-disconnects occur because the source no longer sees the targetThis could be because the connection between the two has failed atsome point or because the target machine data is changing on thesource faster than the source can get the data to the target. This fieldtracks the number of times an auto-disconnect has occurred since theDouble-Take service was started.

Source, autoReConnects

The number of automatic reconnects since starting Double-Take. Auto-reconnect occurs after a target machine is back online. This field tracksthe number of times an auto-reconnect has happened since theDouble-Take service was started.

Source, lastFileTouched

The last filename that had a replication operation executed

Connection, conPeerAddress

The IP address of the target machine

Connection, connectTime

The time that this connection was established

721

Connection, conState

The state of the active connection

l 0—None. This indicates a connection has not been established.Statistics are still available for the source and target machines.

l 1—Active. This indicates that the connection is functioning normallyand has no scheduling restrictions imposed on it at this time. (Theremay be restrictions, but it is currently in a state that allows it totransmit.)

l 2—Paused. This indicates a connection that has been paused.l 4—Scheduled. This indicates a connection that is not currentlytransmitting due to scheduling restrictions (bandwidth limitations,time frame limitations, and so on).

l 8—Error. This indicates a connection that is not transmittingbecause something has gone wrong (for example, lost connection).

Only the Scheduled and Error states can coexist. All other states aremutually exclusive. Statistics will display a conState of 12 when theconnection is in both a scheduled and an error state because this is thesum of the two values (4 + 8).

Connection, conOpsInCmdQueue

The number of operationswaiting to be executed on the target

Connection, conOpsInAckQueue

The number of operationswaiting in the acknowledgement queue.Each operation that is generated receives an acknowledgement fromthe target after that operation has been received by the target. Thisstatistic indicates the number of operations that have yet to receiveacknowledgement of receipt.

Connection, conOpsInRepQueue

The number of replication operations currently waiting to be executedon the target

Connection, conOpsInMirQueue

The number of mirror operations currently waiting to be executed on thetarget

Connection, conBytesInRepQueue

The number of replication bytes remaining to be transmitted to thetarget

Connection, conOpsTx

The number of operations transmitted to the target. This is the totalnumber of operations that Double-Take has transmitted as a source. In

722

other words, the cumulative number of operations transmitted by thissource to all connected targets.

Connection, conBytesInMirQueue

The number of mirror bytes remaining to be transmitted to the target

Connection, conBytesTx

The number of bytes transmitted to the target. This is the total numberof bytes that Double-Take has transmitted as a source. In other words,the cumulative number of bytes transmitted by this source to allconnected targets.

Connection, conBytesCompressedTx

The number of compressed bytes transmitted to the target.

Connection, conOpsRx

The number of operations received by the target. The number ofoperations that the target for this connection (as indicated by the IPaddress field) has received from this source.

Connection, conBytesRx

The number of bytes received by the target. The number of bytes thatthe target for this connection (as indicated by the IP address field) hasreceived from this source.

Connection, conResentOpCount

The number of operations resent because theywere not acknowledged

Connection, conBytesInDiskQueue

The number of bytes in the source disk queue

Connection, conBandwidthLimit

The amount of bandwidth that may be used to transfer data

Connection, conBytesSkipped

The number of bytes skipped during a differencemirror. During adifferencemirror, if Double-Take detects that there have been nochanges to a file, then it will indicate the number of bytes it did not sendfor this file in this field.

Connection, conMirrorBytesRemaining

The number of mirror bytes remaining to be transmitted

Connection, conMirrorPercent

The percentage of themirror that has been completed. This field isdetermined if the Job size was calculated.

723

Connection, conTaskCmdsSubmitted

The number of task commands that have been submitted on the source

Connection, conTaskCmdsQueued

The number of task commands that have been queued on the source

Connection, conTasksSucceeded

The number of task commands that have succeeded on the source

Connection, conTasksFailed

The number of task commands that have failed on the source

Connection, conTasksIgnored

The number of task commands that have been ignored on the source

724

Error codesThe following table contains error codes that youmay see in the various user interfacesor in log files.

-1 Unknown error code (generated when a command failed but the failure is not linked toa pre-defined error code)

-101 Invalid parameter was supplied

-102 Command is not a valid or the syntax is incorrect

-103 Double-Take sourcemodule is not loaded

-104 NoDouble-Take source identified

-105 Double-Take target module is not loaded

-106 Connection already established

-107 Connection does not exist

-108Mirror currently active

-109 Server does not exist or could not be located

-110 Server is not responding

-111 Double-Take is running

-112 Unknown connection error

-113Mirror already active

-114 Date is invalid - valid format ismm/dd/yy

-115 Time is invalid - valid format is hh:mm

-116 Invalid option supplied

-117Mirror is not paused

-118 Connection is not paused

-119 Connection does not exist

-120 Connection already connected

-121Mirror is not running

-122 Job exists

-123 Job does not exist

-124 No job has been selected

-125 Connection is replicating

725

-126 Connection is not replicating

-127 Job is enabled

-128 Schedule is not defined

-129 Job is changed

-130 Job is in use

-131 NoDouble-Take target identified

-132Memory is low

-133Memory is sufficient

-134 Replication is pending

-135 Invalid option supplied

-136 Job replication rule does not exist

-137Mirror queue is full

-138 Insufficient security access

-139 Schedule command is invalid

-140 Source path is invalid

-141 Job is not changed

-142 Insufficient source security access

-143 Invalid statistics file

-144 Job not saved

-145 Connection failed

-146 Cleaner option is not enabled

-147 Target mirror capacity high threshold ismet

-148 Target mirror capacity low threshold ismet

-149 New option applied

-150 Target is restarted

-151 Replication is out of memory

-152Write access is blocked on the volume

-153 Transmission is paused

-154 Transmission is active

-155 Target does not support the command

-156 Command conversion to accommodate a different Double-Take version has failed

726

-157 Incompatible source and target Double-Take versions

-158 Incompatible source and target operating system versions

-159 NAS server to non-NAS server is not a supported configuration

-160 Target module is not loaded

-161Operation or command is not supported

-162 Target is paused

-163 Target is pending

-164 Target is active

-165 Target is retrying operations

-166 Target is no longer retrying operations

-167 Restore required state is unknown

-168 Not a valid failover or cutover source

-169 Failover or cutover login failed

-170 Feature is not supported

-171 Command is not supported

-172 Target queue log file error

-173 Target disk is full

-174 Target disk has sufficient disk space

-175 Error reading from or writing to the queue log file

-176Memory-based queue is in use

-177 Disk-based queue is in use

-178 Restore is required

-179 ID the driver supplied to the service is invalid

-180 Child path is blocked

-181 Parent path is blocked

-182 Target path blocking is disabled

-183 Connection ID specified is invalid

-184 No command objects are in the queue

-185 Target is discarding operations from the target queue

-186 Target is not discarding operations from the target queue

-187 Schedule is paused

727

-188 Schedule is resumed

-189 Target state has changed

-190 Target name has changed

-191 Acknowledgement queue has been updated

-201Monitor name exists

-202Monitor name does not exist

-203Monitor configuration exists

-204Monitor configuration does not exist

-205Monitor configuration is in use

-206Monitor configuration is not in use

-207 Source is online

-208 Source is offline

-209 Server is not failed over

-210 Server is failed over

-211 Server is not beingmonitored

-212 Failback is in progress

-213 IP address placeholders on the target are unavailable

-214 Target NIC was not found

-215 Sourcemodule is not loaded

-216 Failed to set the source state

-217 Unable to ping source

-218 Invalid argument

-219 Recovery is busy

-220 Invalid command

-221 Recovery is started

-222 Script failed to start

-223 Script timeout met

-224 No replication timeout met - connection is bad

-225 Invalid path

-226 Kernel module is not loaded

-227 System dump has failed

728

-228 Response is null

-229Object stream is not OK

-230 Transactional NTFS (TxF) SavePoints (intermediate rollback points) are notsupported

-231 Data overload

-2001 Transform initialization failed

-2002General transform failure

-2003 Transform volume count

-2004 Transformmissing source

-2005 Transformmissing target

-2101 Network controller initialization failed

-2102General network controller failure

-2103 Network controller already started

-2104 No socket on the network controller

-2105 Listen failure on the network controller

-2201 Error communicating with e-mail server

-2202 Error connecting to e-mail server

-2203 E-mail notification is disabled

-2204 E-mail notification is enabled

-2205 E-mail notification requires Internet Explorer version 5.0 andWMI (E-mailnotification no longer requires Internet 5.0 or later.)

-2206 E-mail notification requires Internet Explorer version 5.0 (E-mail notification nolonger requires Internet Explorer 5.0 or later.)

-2207 Error sending e-mail

-2208 Error sending test e-mail

-2209WMI error connecting to e-mail server

-2210 E-mail notification requiresWMI

-2211 Event Viewer settings for e-mail notification are invalid

-2212 E-mail notification setting is invalid

-2213 E-mail notification address exists

-2214 E-mail notification alert ID is invalid

-2215 E-mail notification format is invalid

729

-2216 E-mail notification address does not exist

-2217 E-mail notification address notification list is empty

-2218 E-mail warning is not set

-2219 E-mail test warning is not set

-2200 E-mail notification is functioning properly

-2301 Bandwidth limiting time exists

-2302 Bandwidth limiting name exists

-2303 Bandwidth limit not found

-2304 Bandwidth limit day is invalid

-2305 Bandwidth limit label is invalid

-2401 Snapshot module is not loaded

-2402 Error reading the snapshot .dll

-2403 Snapshot not found

-2404 No snapshot connections found

-2405 Snapshot revert completed

-2406 Snapshot revert is in progress

-2501 Full server functionality is disabled

-2502 No full server interface available

-3001 Refused target mode - Small Business Server

-3002 Refused target mode - Double-TakeMove

-3003 Refused target mode - Duplicate code

-3004 Refused target mode - Double-Take Cloud

730

Windows Event messagesAn event is a significant occurrence in the system or in an application that requiresadministrators to be notified. The operating systemwrites notifications for these eventsto a log that can be displayed using theWindowsEvent Viewer. Three different log filesare generated: application, security, and system.

1. To access the Event Viewer, selectPrograms,Administrative Tools, EventViewer.

2. Select the log to view (System, Security, orApplication) from the left pane ofthe Event Viewer. The following information is displayed for an event in the rightpane of the Event Viewer.

l Type—A classification of the event, such as Error, Warning, Information,Success Audit, or Failure Audit.

l Date—The date the event occurred.l Time—The time the event occurred.l Source—The software that logged the event, which can be either anapplication or a component of the system, such as a driver.

l Category—A classification of the event.l Event—Shows an ID number to identify the specific event. TheEventhelps product-support representatives track events in the system.

l User—Identifies the user that logged the event.l Computer—The name of the computer where the event occurred.

3. To view a detailed description, double-click an event. The additional information isdisplayed in the Event Properties screen.

For additional information on customizing the Event Viewer (such assorting the display, filtering the display, and so on), see your Windowsreference guide or theWindows online help.

For a complete list of Double-Take events, seeEvent messages on page 732.

731

Event messagesThe following table identifies the Double-Take events. The event ID is followed by theevent message. Below the ID andmessage you will find the following information.

l Event log—This identifies if themessage will be found in the Application orSystem event log.

l Source—This identifies the Source in the event log.l Category—This identifies the Category in the event log. OnWindows 2008, this iscalled the TaskCategory.

l Type or Level—This identifies the Type (Windows 2003) or Level (Windows2008) in the event log.

l Required response—This identifies the required action, if any, you should take ifyou get thismessage.

l SCOM alert—This identifies if a SCOMalert rule for themessage is enabled, bydefault, in the Double-TakeManagement Pack. If there is no pre-defined rule forthismessage, that will be indicated. SeeMicrosoft SystemsCenter OperationsManager 2007 on page 826 for details on theManagement Pack.

Double-Take Availability and Double-TakeMove share the same set of eventmessages. Somemessages apply to one product, some to the other, and someto both. For messages that apply to both, the Double-Take Availabilityterminology is used. For example, message 5100 indicates failover completed.This samemessage will also be seen when cutover is completed.

Variables that are dynamically updated in a generatedmessage are designatedby a percent symbol followed by a number. For example, themessage "Theevaluation period expires in%1 day(s)" will have a number automaticallyinserted for %1, so themessage you seemight be "The evaluation periodexpires in 12 day(s)." Variables are used for things like server names, errorcodes, numbers, and so on.

1: This evaluation period has expired. Mirroring and replication have beenstopped. To obtain a license, please contact your vendor.

Event log—Application

Source—Double-Take

Category—ActivationKey

Type or Level—Error

Required response—Contact your vendor to purchase either a singleor site license.

SCOM alert—Enabled

732

2: The evaluation period expires in %1 day(s).




Type or Level—Information

User action required—Contact your vendor before the evaluationperiod expires to purchase either a single or site license.


3: The evaluation period has been activated and expires in %1 day(s).





User action required—Contact your vendor before the evaluationperiod expires to purchase either a single or site license.

SCOM alert—Disabled

4: Duplicate activation codes detected on machine %1 from machine %2.




Type or Level—Warning

User action required—If you have an evaluation license or a sitelicense, no action is necessary. If you have a single license, youmustpurchase either another single license or a site license.


5: This product edition can only be run on Windows Server or AdvancedServer running the Server Appliance Kit.





733

User action required—Verify your activation code has been enteredcorrectly and contact technical support.


200: ExchFailover failover from %1 to %2 was started in commit mode. Seelog file %3 for details.


Source—ExchFailover

Category—None


User action required—See the specific logmessage for additionaldetails.


201: ExchFailover failover from %1 to %2 was started in test mode. See log file%3 for details.



Category—None




202: ExchFailover failback to %1 from %2 was started in commit mode. Seelog file %3 for details.



Category—None




203: ExchFailover failback to %1 from %2 was started in test mode. See logfile %3 for details.



734

Category—None




204: ExchFailover setup started for server %1. See log file %2 for details.



Category—None




205: ExchFailover was unable to open the default log file. A new log file hasbeen created. All messages will be log in %1.



Category—None




210: ExchFailover completed. Moved %1 users in %2 mail stores in %3seconds. Check log file %4 for details.



Category—None

Type or Level—Success



735

211: ExchFailover completed with warnings. Moved %1 users in %2 mailstores in %3 seconds. Check log file %4 for details.



Category—None




212: ExchFailover completed. Tested %1 users in %2 mail stores in %3seconds. Check log file %4 for details.



Category—None




213: ExchFailover completed with warnings. Moved %1 users in %2 mailstores in %3 seconds. Check log file %4 for details.



Category—None




214: ExchFailover setup completed. Updated %1 mail stores in %2 seconds.Check log file %3 for details.



Category—None


736



220: ExchFailover start failed. Could not open log file: %1.



Category—None


User action required—Restart failover. Contact technical support ifthis event occurs again.


221: ExchFailover start failed. Invalid command line arguments. See log file%1 for details.



Category—None




222: ExchFailover start failed. Double-Take is not licensed on this machine.



Category—None


User action required—Verify your activation code has been enteredcorrectly and contact technical support.


223: ExchFailover start failed due to an Active Directory error.



Category—None


737

User action required—Restart failover. Contact technical support ifthis event occurs again.


224: ExchFailover failed to find one (or both) of the Exchange servers. Checkthe server names. This can also occur if the process does not have sufficientprivileges to access Active Directory.



Category—None


User action required—Verify the Exchange server names and theaccount has sufficient privileges to update Active Directory.


1000: An exception occurred: %1


Source—DTCounters

Category—None


User action required—Run the installation and select Repair.Contact technical support if this event occurs again.


1001: The Double-Take counter DLL could not initialize the statistics handlerobject to gather performance data.


Source—DTCounters

Category—None




1002: The Double-Take counter DLL could not map shared memory filecontaining the performance data.


Source—DTCounters

738

Category—None




1003: The Double-Take counter DLL could not open the "Performance" key inthe Double-Take section of the registry.


Source—DTCounters

Category—None




1004: The Double-Take counter DLL could not read the "First Counter" valueunder the Double-Take\Performance Key.


Source—DTCounters

Category—None




1005: The Double-Take counter DLL read the "First Help" value under theDouble-Take\Performance Key.


Source—DTCounters

Category—None




739

1006: The Double-Take counter DLL could not create event handler for theworker thread.


Source—DTCounters

Category—None




3000: Logger service was successfully started.



Category—Service


User action required—No action required.


3001: Logger service was successfully stopped.



Category—Service




4000: Kernel was successfully started.



Category—Service




740

4001: Target service was successfully started.



Category—Service




4002: Source service was successfully started.



Category—Service




4003: Source service was successfully stopped.



Category—Service




4004: Target service was successfully stopped.



Category—Service




4005: Kernel was successfully stopped.



741

Category—Service




4006: Service has aborted due to the following unrecoverable error: %1



Category—Service


User action required—Restart the Double-Take service.


4007: Auto-disconnecting from %1 (%2) for Replication Set %3, ID: %4 due to%5



Category—Service


User action required—The connection is auto-disconnectingbecause the disk-based queue on the source has been filled, theservice has encountered an unknown file ID, the target server hasrestarted, or an error has occurred during disk queuing on the source ortarget (for example, Double-Take cannot read from or write to thetransaction log file).


4008: Auto-disconnect has succeeded for %1 (%2) for Replication Set %3, ID:%4



Category—Service




742

4009: Auto-reconnecting Replication Set %1 to %2 (%3)



Category—Service




4010: Auto-reconnect has succeeded connecting Replication Set %1 to %2(%3)



Category—Service




4011: Auto-reconnect has failed connecting Replication Set %1 to %2 (%3)



Category—Service


User action required—Manually reestablish the job to targetconnection.


4012: %1



Category—Service


User action required—This is a placeholder message for many othermessages. See the specific logmessage for additional details.


743

4013: %1



Category—Service




4014: Service has started network transmission.



Category—Service




4015: Service has stopped network transmission.



Category—Service




4016: Service has established a connection to %1 (%2) for Replication Set %3,ID: %4



Category—Service




744

4017: Service has disconnected from %1 (%2) for Replication Set %3, ID: %4



Category—Service




4018: %1, however, mirroring and replication have been disabled as a restoreis required due to a previous failover.



Category—Service


User action required—Perform a restoration.


4019: Service has started a mirror to %1 (%2) for Replication Set %3, ID: %4



Category—Service




4020: Service has paused a mirror to %1 (%2) for Replication Set %3, ID: %4



Category—Service




4021: Service has resumed a mirror to %1 (%2) for Replication Set %3, ID: %4


745


Category—Service




4022: Service has stopped a mirror to %1 for Replication Set %2, ID: %3, %4



Category—Service




4023: Service has completed a mirror to %1 %2 for Replication Set %3, ID: %4,%5



Category—Service




4024: Service has started Replication to %1 (%2) for Replication Set %3, ID:%4



Category—Service




4025: Service has stopped Replication to %1 (%2) for Replication Set %3, ID:%4



746

Category—Service




4026: The target has been paused due to user intervention.



Category—Service




4027: The target has been resumed due to user intervention.



Category—Service




4028: Registration of service class with Active Directory failed. Verify that theActive Directory server is up and the service has the proper permissions toupdate its entries.



Category—Service


User action required—Verify that the Active Directory server isrunning and that the Double-Take service has permission to updateActive Directory.


4029: Registration of service instance with Active Directory failed. Verify thatthe Active Directory server is up and the service has the proper permissions toupdate its entries.


747


Category—Service


User action required—Verify that the Active Directory server isrunning and that the Double-Take service has permission to updateActive Directory.


4030: RSResource.dll has an unknown error. The product functionality hasbeen disabled.



Category—Service


User action required—Reinstall the software, using the installationRepair option, to install a new copy of the RSResource.dll. Contacttechnical support if this error persists.


4031: RSResource.dll could not be opened. The product functionality hasbeen disabled.



Category—Service




4032: The RSResource.dll component version does not match the componentversion expected by the product. The product functionality has been disabled.



Category—Service


748



4033: RSResource.dll build version is invalid. The product functionality hasbeen disabled.



Category—Service




4034: Error verifying the service name. The product functionality has beendisabled.



Category—Service




4035: Error verifying the product name. The product functionality has beendisabled.



Category—Service




749

4036: Error verifying the vendor name. The product functionality has beendisabled.



Category—Service




4037: Error verifying the vendor URL name. The product functionality hasbeen disabled.



Category—Service




4038: Error verifying the product code. The product functionality has beendisabled.



Category—Service




4039: Error while reading RSResource.dll. The product functionality has beendisabled.



750

Category—Service




4040: The product code is illegal for this computer hardware. The productfunctionality has been disabled.



Category—Service




4041: The product code is illegal for this operating system version. Theproduct functionality has been disabled.



Category—Service




4042: The product code requires installing the Windows Server Appliance Kit.The product functionality has been disabled.



Category—Service


751



4043: This product can only be run on a limited number of processors andthis server exceeds the limit. The product functionality has been disabled.



Category—Service




4044: An error was encountered and replication has been stopped. It isnecessary to stop and restart the service to correct this error.



Category—Service


User action required—Contact technical support if this error persists.


4045: %1 value must be between 1025 and 65535. Using default of %2.



Category—Service


User action required—Verify that the Double-Take port value you aretrying to use is within the valid range. If it is not, it will automatically bereset to the default value.


4046: This service failed to start because of a possible port conflict. Win32error: %1


752


Category—Service


User action required—Verify that the Double-Take ports are notconflicting with ports used by other applications.


4047: Could not load ZLIB DLL %1. Some levels of compression will not beavailable.



Category—Service


User action required—The compression levels available depend onyour operating system. You can reinstall the software, using theinstallation Repair option, to install a new copy of the DynaZip.dll, orcontact technical support if this error persists.


4048: Service has started a delete orphans task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




4049: Service has paused a delete orphans task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




753

4050: Service has resumed a delete orphans task to %1 (%2) for ReplicationSet %3, ID: %4



Category—Service




4051: Service has stopped a delete orphans task to %1 (%2) for ReplicationSet %3, ID: %4



Category—Service




4052: Service has completed a delete orphans task to %1 (%2) for ReplicationSet %3, ID: %4



Category—Service




4053: Service has started a restore task to %1 (%2) for Replication Set %3, ID:%4



Category—Service




754

4054: Service has paused a restore task to %1 (%2) for Replication Set %3, ID:%4



Category—Service




4055: Service has resumed a restore task to %1 (%2) for Replication Set %3,ID: %4



Category—Service




4056: Service has stopped a restore task to %1 (%2) for Replication Set %3,ID: %4



Category—Service




4057: Service has completed a restore task to %1 (%2) for Replication Set %3,ID: %4



Category—Service




755

4058: Service has started a verification task to %1 (%2) for Replication Set %3,ID: %4



Category—Service




4059: Service has paused a verification task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




4060: Service has resumed a verification task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




4061: Service has stopped a verification task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




756

4062: Service has completed a verification task to %1 (%2) for Replication Set%3, ID: %4



Category—Service




4063: Bandwidth limit to %1 (%2) has changed to %3.



Category—Service




4064: Bandwidth limit to %1 (%2) is now in the "%3" period at %4.



Category—Service




4065: Target data state for connection %1 from %2 (%3) has changed because%4.



Category—Service




757

4066: The product code requires a virtual server environment. The productfunctionality has been disabled.



Category—Service


User action required—The activation code you are using is for theVirtual SystemsTMedition. This code will not work on non-virtual serverenvironments.


4067: No replication ops have been received from the driver for an extendedperiod of time.



Category—Service


User action required—Check other messages for errors with theDouble-Take drivers, and correct as required. If there are no drivermessages, verify that your drives are connected to the source. If thiserror persists, contact technical support.


4068: Failed to write to a replicating volume.



Category—Service


User action required—Reboot the source server. Contact technicalsupport if this event occurs again.


4069: The option MoveOrphansDir has been updated because it was missingor empty.



Category—Service

758




4070: An error occurred while reading data for connection %1. All data needsto be remirrored. See the log for details.



Category—Service


User action required—Initiate a remirror to guarantee data integrity.Contact technical support if this event occurs repeatedly.


4071: Received network message with invalid checksum.



Category—Service


User action required—Initiate a remirror to guarantee data integrity.Contact technical support if this event occurs repeatedly.


4096: The registry parameter %2 is unknown.

Event log—System

Source—RepDrv

Category—None


User action required—Delete the parameter and report this issue totechnical support.


4097: Failed to initialize WMI support. The last Word in the Data Window is theNT status code.

Event log—System

Source—RepDrv, RepKap, RepHsm, or RepSis

Category—None

759




4097: The file system filter failed to load. Replication will not occur. Rebootyour server and contact technical support if this error occurs again. The lastWord in the Data window is the NT status code.

Event log—System

Source—RepDrv

Category—None


User action required—Reboot your server and contact technicalsupport if this event occurs again.


4098: The registry parameters failed to load, so the default configurationvalues will be used. The last Word in the Data window is the NT status code.

Event log—System

Source—RepKap

Category—None




4098: The control device %2 was not created. Communication with the servicewill be disabled. Reboot the server and contact technical support if this erroroccurs again. The last Word in the Data window is the NT status code.

Event log—System

Source—RepDrv, RepDac, RepKap, or RepHsm

Category—None




4099: The driver detected a hard link for a file on drive %2. Hard links are notsupported. Changes to this file will not be replicated.

Event log—System

760

Source—RepDrv

Category—None


User action required—Hard links are not supported.


4099: The driver failed to register with filter manager. Reboot the server andcontact technical support if this error occurs again. The last Word in the Datawindow is the NT status code.

Event log—System

Source—RepKap

Category—None




4100: Product activation code is invalid. Please check that it is typed correctlyand is valid for the version of the operating system in use.





User action required—If you are in the process of installing Double-Take, verify that you are using a 24 character alpha-numeric code. IfDouble-Take is already installed, confirm that the code entered iscorrect. If the code appears to be correct, contact technical support.


4100: The versions of the driver and the filter driver do not match. Replicationwill not occur. Reboot your server. If this error occurs again, reinstall thesoftware. Contact technical support if this error occurs after the software hasbeen reinstalled. The last three Words in the Data window are the NT statuscode and the driver version numbers.

Event log—System

Source—RepDrv

Category—None


761

User action required—Reboot your server. Reinstall the software ifthis event occurs again. Contact technical support if this event occursafter reinstalling the software.


4101: This service will not run on this device. Contact your salesrepresentative for upgrade procedures.





User action required—The activation code does not match the typeof server you are attempting to run on. Contact your vendor for a newactivation code or contact technical support.


4110: Target cannot write %1 due to target disk being full. Operation will beretried (%2 times or forever)



Category—Service


User action required—The disk on the target is full. The operation willbe retried according to the TGExecutionRetryLimit setting.


4111: Target can not write %1 due to a sharing violation. Operation will beretried (%2 times or forever)



Category—Service


User action required—A sharing violation error is prohibiting Double-Take fromwriting on the target. The operation will be retried accordingto the TGExecutionRetryLimit setting.


762

4112: Target can not write %1 due to access denied. Operation will be retried(%2 times or forever)



Category—Service


User action required—An access denied error is prohibiting Double-Take fromwriting on the target. The operation will be retried accordingto the TGExecutionRetryLimit setting..


4113: Target can not write %1 due to an unknown reason. Operation will beretried (%2 times or forever). Please check the log files for further informationon the error.



Category—Service


User action required—An unknown error is prohibiting Double-Takefromwriting on the target. The operation will be retried according to theTGExecutionRetryLimit setting.


4120: Target write to %1 was completed successfully after %2 retries.



Category—Service




4150: Target write %1 failed after %2 retries and will be discarded. See theevent log or log files for error conditions. After correcting the problem, youshould re-mirror or run a verify to resynchronize the changes.



Category—Service

763


User action required—The operation has been retried according tothe TGExecutionRetryLimit setting but was not able to be written to thetarget and the operation was discarded. Correct the problem andremirror the files.


4155: The service was unable to complete a file system operation in theallotted time. See the log files for error conditions. After correcting theproblem, remirror or perform a verification with remirror to synchronize thechanges.



Category—Service


User action required—Correct the file system error and then remirroror perform a verification with remirror to synchronize the changes.


4200: In band task %1 submitted from %2 by %3 at %4



Category—Service




4201: In band task %1 discarded (submitted from %2 by %3 at %4)



Category—Service


User action required—A taskmay be discarded in the followingscenarios: all connections to a target aremanually disconnected,replication is stopped for all connections to a target, or an auto-disconnect occurs. If one of these scenarios did not cause the task to bediscarded, contact technical support.


764

4202: Running %1 in band script: %2 (task %3 submitted from %4 by %5 at%6)



Category—Service




4203: Completed run of in band script: %1 (exit code %2)



Category—Service




4204: Error running in band script: %1



Category—Service


User action required—Review the task and its associated script(s)for syntax errors.


4205: Timeout (%1 seconds) running in band script: %2



Category—Service


User action required—The timeout specified for the script tocomplete has expired. Normal processing will continue. Youmay needtomanually terminate the script if it will never complete


765

4206: Run timeout disabled for in band script: %1



Category—Service


User action required—The timeout period was set to zero (0).Double-Take will not wait for the script to complete before continuing.No action is required.


4207: In band scripts disabled by server - no attempt will be made to run %1



Category—Service


User action required—Enable task command processing.


4300: A connection request was received on the target before the persistenttarget paths could be loaded.



Category—Service


User action required—Youmay need to stop and restart your job.


4301: Unable to block target paths, the driver is unavailable.



Category—Service


User action required—If you need to block your target paths, contacttechnical support.


766

4302: Target Path %1 has been successfully blocked



Category—Service




4303: Blocking of target path: %1 failed. Error Code: %2



Category—Service




4304: Target Path %1 has been successfully unblocked



Category—Service




4305: Unblocking of target path: %1 failed. Error Code: %2



Category—Service


User action required—If you need to unblock your target paths,contact technical support.


767

4306: Target paths for source %1 (%2) Connection id: %3 are already blocked



Category—Service




4307: Target paths for source %1 (%2) Connection id: %3 are alreadyunblocked



Category—Service




4308: Error loading target paths for blocking, registry key %1 has beencorrupted.



Category—Service




4400: Failed to create snapshot set for source %1 (%2) Connection ID: %3.Error: %4



Category—Service


User action required—The snapshot could not be created. Thismaybe due to a lack of disk space or memory or another reason. The error

768

code is theMicrosoft VSS error. Check your VSS documentation orcontact technical support.


4401: Failed to delete automatic snapshot set for source %1 (%2) ConnectionID: %3. Error: %4



Category—Service


User action required—The automatic snapshot could not be deleted.Thismay be due to a lack of memory, the file does not exist, or anotherreason. The error code is theMicrosoft Volume Shadow Copy error.Check your Volume Shadow Copy documentation or contact technicalsupport.


4402: Failed to delete snapshot set for source %1 (%2) Connection ID: %3.Error: %4



Category—Service


User action required—The snapshot could not be deleted. Thismaybe due to a lack of memory, the file does not exist, or another reason.The error code is theMicrosoft Volume Shadow Copy error. Checkyour Volume Shadow Copy documentation or contact technicalsupport.


4403: A scheduled snapshot could not be created for source %1 (%2)Connection ID: %3. because the target data was in a bad state. A snapshot willautomatically be created when the target data reaches a good state.



Category—Service


User action required—No action required. A snapshot willautomatically be created when the target data reaches a good state.

769


4404: Set snapshot schedule for source %1 (%2) connection %3 to every %4minutes. Next snapshot: %5.



Category—Service




4405: Removed snapshot schedule for source %1 (%2) connection %3.



Category—Service




4406: Enabled snapshot schedule for source %1 (%2) connection %3.



Category—Service




4407: Disabled snapshot schedule for source %1 (%2) connection %3.



Category—Service




770

4408: %1 was unable to move some orphans for source %2 on connection ID%3. Check the %1 logs for further details.



Category—Service


User action required—Orphan files could not bemoved. Forexample, the location could be out of disk space. Check the Double-Take log for more information.


4409: %3 was unable to delete some orphans for source %1 on connection ID%2. Check the %3 logs for further details.



Category—Service


User action required—Orphan files could not be deleted. Check theDouble-Take log for more information.


4410: The registry hive dump failed with an of error: %1.



Category—Service


User action required—Contact technical support.


4411: The Service has detected that port %1 is being %2 by the WindowsFirewall.



Category—Service


771

User action required—The firewall port needs to be unblocked orrestrictions against Double-Take removed so that Double-Take datacan be transmitted.


5000: Server Monitor service was successfully started.



Category—Service




5001: Server Monitor service was successfully stopped.



Category—Service




5002: Placeholders were modified to %1.



Category—Service




5100: Failover completed for %1.



Category—Failover



772


5101: IP address %1 with subnet mask %2 was added to target machine's %3adapter.



Category—Failover




5102: %1 has reached a failover condition. A response from the user isrequired before failover can take place.



Category—Failover


User action required—Check your sourcemachine, and initiatefailover, if user intervention for failover is configured. If you bring yoursourcemachine back online, without initiating failover, the failoverconditionmet state will be canceled.


5103: Started adding drive shares from %1 to %2.



Category—Failover




5104: %1 drive shares were taken over by %2.



Category—Failover



773


5105: Attempting to run the %1 script.



Category—Failover




5106: The %1 script ran successfully.



Category—Failover




5107: Error occurred in running %1 script.



Category—Failover


User action required—Verify that the script identified exists with theproper permissions.


5108: The source machine %1 is not responding to a ping.



Category—Failover


User action required—This occurs when all monitored IP addresseson the sourcemachine stop responding to pings. Countdown to failoverwill begin at the first occurrence and will continue until the sourcemachine responds or until failover occurs.

774


5109: The public NIC on source machine %1 is not responding to a ping.



Category—Failover


User action required—The failover target did not receive an answerto its ping of the sourcemachine. Eventually, a failover will result.Investigate possible errors (down server, network error, and so on).


5110: The %1 script "%2" is still running.



Category—Failover




5200: Failback completed for %1.



Category—Failback




5201: IP address %1 was removed from target machine's %2 adapter.



Category—Failback




775

5202: Unable to Failback properly because IP address %1 was missing acorresponding SubNet Mask.



Category—Failback




5300: The following IP address was added to target's monitoring list: %1



Category—Monitoring




5301: The following IP address was removed from target's monitoring list: %1







5302: Drive share information for %1 has been updated on the target machine.







5303: The application monitor script has started successfully.


776






5304: The application monitor script has finished successfully.







5305: The application monitor has found the %1 service stopped.





User action required—ApplicationManager will attempt to restart theservice.


5306: The application monitor has restarted the %1 service.







5307: The application monitor cannot contact the server %1.




777


User action required—Verify the server is running. Verify availablenetwork communicationswith the server.


5400: Broadcasted new MAC address %1 for IP address %2.



Category—ARP




5500: Could not connect to e-mail server. Check to make sure the SMTPserver %1 is available (error code: %2).



Category—Service


User action required—Double-Take could not connect to your SMTPserver or the username and/or password supplied is incorrect. Verifythat SMTP server is available and that you have identified it correctly inyour e-mail notification configuration. Also verify that your usernameand password have been entered correctly.


5501: E-mail notification could not be enabled (error code: %1).



Category—Service


User action required—This alert occurs if there is an unexpectederror enabling e-mail notification during service startup. Check to see ifany other errors related to e-mail notification have been logged. Also,check tomake sure theWindowsManagement Instrumentation (WMI)service is enabled. If neither of these apply, contact technical support.


778

5502: E-mail notification could not be initialized. Check to make sure InternetExplorer 5.0 or later is installed.



Category—Service


User action required—E-mail notification no longer requires InternetExplorer 5.0 or later. If you receive this error, contact technical support.


5503: E-mail notification could not be processed. Check to make sure thecorrect version of SMTPMail.DLL is registered on the system (error code: %1).



Category—Service


User action required—If you are using Double-Take 4.4.2.1 or earlierandWindowsNT 4.0, e-mail notification requiresWindowsManagement Instrumentation (WMI) to be installed. Verify that youhave it installed on the Double-Take server.


5504: Could not load LocalRS.dll (for e-mail notification).



Category—Service


User action required—This alert occurs if there is an error loading theresource DLL for the service. Typically, this is caused by amissingLocalRS.dll file. Reinstall the software, using the installation Repairoption, to install a new copy of the LocalRS.dll. Contact technicalsupport if this error persists.


5505: E-mail could not be sent. Check e-mail settings (error code: %1).



779

Category—Service


User action required—Verify that the e-mail server that you haveidentified in your e-mail notification configuration is correct.


5506: One or more required e-mail settings have not been specified (errorcode: %1).



Category—Service


User action required—At aminimum, youmust specify the e-mailserver, the From and To addresses, and at least one type of event toinclude.


5507: E-mail notification could not be initialized. Check to make sure WMI isinstalled and available (error code: %1).



Category—Service


User action required—If you are using Double-Take 4.4.2.1 or earlierandWindowsNT 4.0, e-mail notification requiresWindowsManagement Instrumentation (WMI) to be installed. Verify that youhave it installed on the Double-Take server.


5508: An error occurred connecting to the WMI namespace. Check to makesure the Windows Management Instrumentation service is not disabled (errorcode %1).



Category—Service


780

User action required—This alert occurs if there is an error with theWindowsManagement Instrumentation (WMI) service. Verify that youhave it installed on the Double-Take server and that it is enabled.


5600: Part or all of the e-mail setting %1 is not in a valid format.



Category—Service


User action required—Verify that the include categories and excludeID list are identified and formatted correctly.


6000: %1


Source—Double-TakeManagement Service

Category—None




6001: %1



Category—None




6002: %1



Category—None


781



6003: A %1 job has been created. The name is "%2" and the ID is %3.



Category—None




6004: The %1 job "%2" (ID %3) has been started.



Category—None




6005: The %1 job "%2" (ID %3) has been stopped.



Category—None


User action required—No action required. If desired, you can restartyour job.


6006: The %1 job "%2" (ID %3) has been deleted.



Category—None


782

User action required—No action required. If desired, you can re-create your job.


6007: The %1 operation has failed for the %2 job "%3" (ID %4).



Category—None


User action required—No action required. If desired, you can re-create your job.


6008: The %1 operation has completed successfully for the %2 job "%3" (ID%4).



Category—None




6009: Could not log the following message:%n%1%n---%nError:%n%2.



Category—None


User action required—There is a problemwith logging. Contacttechnical support if this event occurs again.


6010: A failover condition has been met for the %1 job "%2" (ID %3).



Category—None


783



6100: The job "%1" (ID %2) has started provisioning a replica for %3.



Category—Service




6101: The job "%1" (ID %2) has successfully completed provisioning a replicafor %3.



Category—Service




6102: The job "%1" (ID %2) has failed to provision a replica for %3.%n%n



Category—Service


User action required—Review the additional error information toidentify the problem. Correct the problem and retry the operation.Contact technical support if this event occurs again.


6110: The job "%1" (ID %2) has started a %3 failover of the replica of %4.



Category—Service

784




6111: The job "%1" (ID %2) has successfully completed a %3 failover of thereplica of %4.



Category—Service




6112: The job "%1" (ID %2) has encountered an error while performing a %3failover of the replica of %4.%n%n



Category—Service




6120: The job "%1" (ID %2) has started undoing the failover for the replica of%3.



Category—Service




6121: The job "%1" (ID %2) has successfully reattached the replica andresumed protecting %3.



785

Category—Service




6122: The job "%1" (ID %2) has encountered an error undoing the failing overfor the replica of %3.%n%n



Category—Service




6130: The job "%1" (ID %2) has started reversing the direction of theprotection of %3.



Category—Service




6131: The job "%1" (ID %2) has successfully reversed the direction of theprotection of %3.



Category—Service




6132: The job "%1" (ID %2) has encountered an error reversing the directionof the protection of %3.%n%n


786


Category—Service




6140: The job "%1" (ID %2) is being deleted.



Category—Service




6141: The job "%1" (ID %2) has successfully been deleted.



Category—Service




6142: The job "%1" (ID %2) has encountered an error while beingdeleted.%n%n



Category—Service




6150: The job "%1" (ID %2) protecting %3 has completed its mirror.


787


Category—Service




6210: The job "%1" (ID %2) has started a %3 failover of the replica of %4.



Category—Service




6211: The job "%1" (ID %2) has successfully completed a %3 failover of thereplica of %4.



Category—Service




6212: The job "%1" (ID %2) has encountered an error while performing a %3failover of the replica of %4.%n%n



Category—Service




6213: A failover condition has been met for the host level job "%1" (ID %2).


788


Category—None




6214: Failover monitors removed for the host level job "%1" (ID %2).



Category—None


User action required—No action required. The failover pending statehas been canceled because the job has been stopped, deleted, or failedover.


6215: The job "%1" (ID %2) is protecting.



Category—None




6220: The job "%1" (ID %2) has started undoing the failover for the replica of%3.



Category—Service




789

6221: The job "%1" (ID %2) has successfully reattached the replica andresumed protecting %3.



Category—Service




6222: The job "%1" (ID %2) has encountered an error undoing the failing overfor the replica of %3.%n%n



Category—Service




6230: The job "%1" (ID %2) has started reversing the direction of theprotection of %3.



Category—Service




6231: The job "%1" (ID %2) has successfully reversed the direction of theprotection of %3.



Category—Service



790


6232: The job "%1" (ID %2) has encountered an error reversing the directionof the protection of %3.%n%n



Category—Service




6240: The job "%1" (ID %2) is being deleted.



Category—Service




6241: The job "%1" (ID %2) has successfully been deleted.



Category—Service




6242: The job "%1" (ID %2) has encountered an error while beingdeleted.%n%n



Category—Service


791



6250: The job "%1" (ID %2) protecting %3 has completed its mirror.



Category—Service




6300: A failover condition has been met for the full server job "%1" (ID %2).



Category—Service




6500: A cutover condition has been met for the full server migration job "%1"(ID %2).



Category—Service


User action required—Initiate cutover.


6700: A cutover condition has been met for the data migration job "%1" (ID%2).



792

Category—Service


User action required—Initiate cutover.


7106: The driver was unable to get valid name information from the FilterManager for the file %2. (Filename may be truncated.) It cannot be replicated.Please contact technical support.

Event log—System

Source—RepDrv

Category—None




7107: The driver was unable to get valid name information from the FilterManager for a file. It cannot be replicated. Please contact technical support.

Event log—System

Source—RepDrv

Category—None




8100: The driver encountered an unrecoverable internal error. Contacttechnical support. The last Word in the Data window is the internal error code.

Event log—System

Source—RepDac

Category—None




8192: Driver failed to allocate Kernel memory. Replication is stopped andserver must be rebooted for replication to continue. The last word in the datawindow is the tag of the allocation that failed.

Event log—System

793

Source—RepDrv, RepKap, or RepHsm

Category—None


User action required—Reboot the server and contact technicalsupport if this event occurs again.


8192: Kernel memory is exhausted. Replication is stopped. This may havebeen caused by low system resources.

Event log—System

Source—RepDrv or RepHsm

Category—None




8193: The driver failed to create a thread required for normal operation. Thismay have been caused by low system resources. Reboot your server andcontact technical support if this error occurs again. The last Word in the Datawindow is the NT status code.

Event log—System

Source—RepDrv

Category—None




8196: The maximum amount of memory for replication queuing has beenreached. Replication is stopped and memory is being freed.

Event log—System

Source—RepDrv

Category—None


User action required—This error is expected when the amount ofreplication exceedswhat can be queued and transmitted on the source

794

server. You do not have to take any action because Double-Take willautomatically disconnect, reconnect and remirror (by default) whenmemory resources are available. However, youmaywant to considerchanges to the source that will reduce the load on the server. SeeKnowledge Base Article 32410 on the support site for details on the8196 event and possible steps you can take on your server to helpalleviate this condition. (The old article number is 2022.)


8198: The driver registry path could not be saved. The default registry path willbe used.

Event log—System

Source—RepDrv, RepKap, or RepHsm

Category—None




8200: The driver failed to allocate a buffer for a file name longer than 260characters. The file will be skipped. The last Word in the Data window is the NTstatus code.

Event log—System

Source—RepDrv

Category—None




9000: The driver has failed to process a rename operation. The driver willresend the rename operation. This message is only a warning. If you receivethis message repeatedly, contact technical support. The last Word in the Datawindow is the NT status code.

Event log—System

Source—RepKap

Category—None


User action required—Contact technical support if this event occursagain.

795


9100: The driver encountered an error opening a file from the service. Checkthe Event Viewer Application log for additional service information or contacttechnical support. The last Word in the Data window is the exception code.

Event log—System

Source—RepKap

Category—None


User action required—Check for related servicemessages. Contacttechnical support if this event occurs again.


9101: The driver encountered an error reading from the service input buffer.Check the Event Viewer Application log for additional service information orcontact technical support. The last Word in the Data window is the exceptioncode.

Event log—System

Source—RepKap

Category—None




9102: The driver encountered an error writing to the service output buffer.Check the Event Viewer Application log for additional service information orcontact technical support. The last Word in the Data window is the exceptioncode.

Event log—System

Source—RepKap

Category—None




9103: The driver encountered an error writing to the service input buffer.Check the Event Viewer Application log for additional service information or

796

contact technical support. The last Word in the Data window is the exceptioncode.

Event log—System

Source—RepKap

Category—None




9104: The driver encountered an error querying for file security from theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9105: The driver encountered an error querying for file security from theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9106: The driver encountered an error writing file security data to the serviceinput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

797

Source—RepKap

Category—None




9107: The driver encountered an error querying for an allocated range fromthe service input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9108: The driver encountered an error querying for an allocated range fromthe service output buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9109: The driver encountered an error writing an allocated range to theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None

798




9110: The driver encountered an error querying for a directory from theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9111: The driver encountered an error querying for a directory from theservice output buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9112: The driver encountered an error writing a directory query to the serviceinput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None


799



9113: The driver encountered an error querying a stream from the serviceinput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None




9114: The driver encountered an error writing a stream query to the serviceoutput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None




9115: The driver encountered an error writing a stream query to the serviceoutput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None




800

9116: The driver has failed to close a file handle. If you receive this messagerepeatedly, contact technical support. The last Word in the Data window is theNT status code.

Event log—System

Source—RepKap

Category—None




9117: The driver encountered an error querying for extended attributes fromthe service input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9118: The driver encountered an error writing extended attributes to theservice output buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9119: The driver encountered an error writing extended attributes status tothe service input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

801

Source—RepKap

Category—None




9120: The driver encountered an error querying for file information from theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9121: The driver encountered an error writing file information to the serviceoutput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None




9122: The driver encountered an error writing file information status to theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None

802




9123: The driver encountered an error querying for fsctl information from theservice input buffer. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




9124: The driver encountered an error writing fsctl information to the serviceoutput buffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None




9125: The driver encountered an error writing fsctl status to the service inputbuffer. Check the Event Viewer Application log for additional serviceinformation or contact technical support. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None


803



9126: The driver encountered an error reading from the service input buffer,KFAI_OPEN_BY_FILE_ID. Check the Event Viewer Application log foradditional service information or contact technical support. The last Word inthe Data window is the exception code

Event log—System

Source—RepKap

Category—None




9127: The driver encountered an error writing to the service output buffer,KFAI_OPEN_BY_FILE_ID. Check the Event Viewer Application log foradditional service information or contact technical support. The last Word inthe Data window is the exception code.

Event log—System

Source—RepKap

Category—None




9128: The driver encountered an error reading from the service input buffer,KFAI_QUERY_INFO. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




804

9129: The driver encountered an error writing to the service output buffer,KFAI_QUERY_INFO. Check the Event Viewer Application log for additionalservice information or contact technical support. The last Word in the Datawindow is the exception code.

Event log—System

Source—RepKap

Category—None




10000: This message is only a placeholder warning. The last Word in the Datawindow is the NT status code.

Event log—System


Category—RepHsm




10000: Connect failed to node %1 for resource %2. Adding node to reconnectlist.



Category—GeoCluster


User action required—Ensure that GeoCluster is running on allpossible owners and that it can communicate on the network selectedfor mirroring and replication traffic. GeoCluster will try to reestablish aconnection using the check unresponsive node interval specified for theresource.


10001: Reconnect succeeded to node %1 for resource %2. Will be added as apossible owner when mirror is complete.



805





10002: Disk check failed on node %1 for resource %2. Removing as a possibleowner.





User action required—Ensure that GeoCluster is running on allpossible owners and that it can communicate on the public network.Also ensure that the disk specified for the resource is functioningcorrectly on all possible owners.


10003: Owner %1 of the quorum resource %2 couldn't access the arbitrationpath %3. Network may be down.





User action required—Ensure that the network used to access thearbitration path is up and that the server is operational. Also ensure thatthe arbitration share path does exist and that the account running thecluster service haswrite privileges to the share path.


10004: Failover of the group %1 is being delayed. Group will be brought onlinewhen the target queue is below the limit or the timeout has expired.







806

10005: Node %1 is taking ownership of the group %2. The group will bebrought online on this node.







10006: The cluster notification thread failed to start on node %1 for resource%2. The resource should be taken offline and brought back online.





User action required—Take the resource offline and bring it backonline.


10007: The user %1 has reverted a snapshot for the %2 resource on node %3.





User action required—No action required. The snapshot youselected will be reverted.


10008: The user %1 has discarded queued data for the %2 resource on node%3.





807

User action required—No action required. The queue you selectedwill be discarded.


10009: The user %1 is verifying data for the %2 resource on node %3.





User action required—A snapshot of the current data has beentaken. After you have verified the data, accept or reject the data.


10010: The user %1 has rejected the data for the %2 resource on node %3.





User action required—No action required. Since the data wasrejected, the data has been reverted to the snapshot taken when thedata was selected for verification.


10011: The user %1 has accepted the data for the %2 resource on node %3.





User action required—No action required. The current data will beused.


10012: The GeoCluster Replicated Disk resource %1 has been set to validateits data. No data replication is occurring to the remaining nodes in the cluster.Please Accept or Reject the data by right-clicking on the resource andselecting the appropriate option.



808



User action required—Replication has been stopped because of thevalidation request. Accept or reject the data on the node by right-clicking on the resource and selecting the appropriate option.


10100: The driver could not recall a file because it did not have a token forimpersonation. The security provider service should set this token. The lastWord in the Data window is the exception code.

Event log—System

Source—RepKap

Category—None




10101: The driver could not access the file in the archive bin, due to a failedimpersonation attempt. The last Word in the Data window is the exceptioncode.

Event log—System

Source—RepKap

Category—None




10102: The driver could not recall the file. The last Word in the Data window isthe exception code.

Event log—System

Source—RepKap

Category—None



809


11000: Service has started an archive to %1 (%2) for Replication Set %3, ID:%4



Category—Service




11001: Service has completed an archive to %1 (%2) for Replication Set %3,ID: %4, %5



Category—Service




11002: Service has started a recall from %1 (%2) for Replication Set %3, ID:%4



Category—Service




11003: Service has completed a recall from %1 (%2) for Replication Set %3,ID: %4, %5



Category—Service



810


11004: Service has failed connection to the RepHSM driver. %1



Category—Service


User action required—Reboot the server or manually restart theRepHSM.sys driver.


11005: Service has aborted the archive operation.



Category—Service


User action required—Verify the activation code on the source andtarget is valid for archiving. Reboot an unlicensed server.


11006: Service has aborted the archive recall operation.



Category—Service




11007: Verification has finished with errors. %1



Category—Service


User action required—Review the verification log to correct or acceptthe errors.

811


11008: Archive feature is not supported on volume %1



Category—Service


User action required—The source and target must be NTFS forarchiving functionality.


11009: Service has started an archive preview to %1 (%2) for Replication Set%3, ID: %4



Category—Service




11010: Service has completed an archive preview to %1 (%2) for ReplicationSet %3, ID: %4



Category—Service




11011: Service has aborted the archive preview operation.



Category—Service



812


12000: The service has started.



Category—DTRecall


User action required—Thismessage refers to the Double-TakeRecall service. No action required.


12001: The service failed to start.



Category—DTRecall


User action required—Check the user name and password for theDouble-Take Recall service to ensure validity. Reinstall the software ifthis event occurs again.


12002: The service has stopped.



Category—DTRecall


User action required—Thismessage indicates a system shutdown orthe user stopped the Double-Take Recall service. No action is required.


12003: The service failed to create a stop control event. (Error %1)



Category—DTRecall


813

User action required—Restart the Double-Take Recall service.Reinstall the software if this event occurs again.


12004: RegisterServiceCtrlHandler failed. (Error %1)



Category—DTRecall




12005: Service encountered SetServiceStatus error (Error %1)



Category—DTRecall




12006: Service could not get handle to driver for security update. (Error %1)



Category—DTRecall


User action required—TheDouble-Take Recall service could notconnect to the Double-Take Recall archiving driver. Reboot the serverand reinstall the software if this event occurs again.


12007: Service failed a periodic security update. (Error %1)



Category—DTRecall


814

User action required—Thismessage refers to the Double-TakeRecall service. The operation will be performed every fiveminutes.Reinstall the software if this event occurs after fiveminutes.


12288: The driver encountered an error accessing a buffer from the service.Contact technical support. The last Word in the Data window is the exceptioncode.

Event log—System

Source—RepDrv

Category—None




16384: The driver encountered an unrecoverable error. Contact technicalsupport.

Event log—System

Source—RepDrv

Category—None




16385: The driver encountered an unexpected internal result. Contacttechnical support. The last Word in the Data window is the NT status code.

Event log—System

Source—RepDrv

Category—None




16393: The driver encountered an internal error. Contact technical support.The last Word in the Data window is the internal error code.

Event log—System

Source—RepDrv

815

Category—None




16395: The driver detected a memory error which may have been caused by abad driver or faulty hardware. Contact technical support. The last Word in theData window is the internal error code.

Event log—System

Source—RepDrv or RepHsm

Category—None




16396: The driver failed to create work queues for normal operation. This mayhave been caused by low system resources. Reboot the server and contacttechnical support if this error occurs again. The last Word in the Data windowis the NT status code.

Event log—System

Source—RepDrv

Category—None




16400: RepDrv has encountered an unexpected condition, usually caused bylow kernel memory. Unless otherwise mentioned, this event has already beenhandled and your data remains protected. If you continue to receive theseevents or have further questions please contact tech support.

Event log—System

Source—RepDrv

Category—None




816

Performance MonitorPerformanceMonitor is theWindows graphical tool for measuring performance. Itprovides charting, alerting, and reporting capabilities that reflect both current activity andongoing logging. Double-Takestatistics are available through the PerformanceMonitor.

l Monitoring PerformanceMonitor statistics on page 817l PerformanceMonitor statistics on page 818

Monitoring Performance Monitor statistics1. To access the PerformanceMonitor, selectStart, Programs,Administrative

Tools, Performance.2. Specify the data tomonitor by right-clicking and selectingAdd or using theAdd

button on the toolbar.3. Choose one of the following Double-Take PerformanceObjects.

l Double-Take Connectionl Double-Take Kernell Double-Take Securityl Double-Take Sourcel Double-Take Target

4. Select the statistics you want to monitor, and clickAdd.

For additional information and details on the PerformanceMonitor, see your Windowsreference guide.

PerformanceMonitor should not be used remotely on systems running differentoperating systems (Windows 2003 toWindows 2008 or vice versa).PerformanceMonitor can be used remotely when using like systems (Windows2003 toWindows 2003 or Windows 2008 toWindows 2008).

817

Performance Monitor statisticsThe following tables identify the Double-Take PerformanceMonitor statistics for eachDouble-Take counter. For each statistic, you will find the following information.

l Description—This description identifies what the statistic ismeasuring.l SCOM alert—This identifies if a SCOMalert rule for themessage is enabled, bydefault, in the Double-TakeManagement Pack. If there is no pre-defined rule forthismessage, that will be indicated. SeeMicrosoft SystemsCenter OperationsManager 2007 on page 826 for details on theManagement Pack.

If you havemultiple IP addresses connected to one target server, you will seemultipleDouble-Take Target statistic sections for each IP address.

Double-Take Connection

Bandwidth Limit

Description—The amount of bandwidth that may be used to transferdata


Bytes in disk queue

Description—The number of bytes in the source disk queue


Bytes in replication queue

Description—The number of replication bytes in the source queue


Bytes in the mirror queue

Description—The number of mirror bytes in the source queue


Bytes received

Description—The number of bytes received by the target since thelast PerformanceMonitor refresh


Bytes transferred

Description—The number of bytes transmitted from the source

818


Compressed bytes transferred

Description—The number of compressed bytes transmitted from thesource


Operations in acknowledgement queue

Description—The number of operationswaiting in the sourceacknowledgement queue


Operations in command queue

Description—The number of operationswaiting in the sourcecommand queue


Operations in mirror queue

Description—The number of mirror operations in the source queue


Operations in replication queue

Description—The number of replication operations in the sourcequeue


Operations received

Description—The number of operations received by the target sincethe last PerformanceMonitor refresh


Operations resent

Description—The number of operations re-sent since the last time theDouble-Take service was restarted on the source


Operations transmitted

Description—The number of operations transmitted from the source


Task commands queued

Counter—Double-Take Connection

819

Description—The number of task commands queued on the source


Task commands submitted

Description—The number of task commands submitted on the source


Tasks failed

Description—The number of task commands that have failed toexecute on the source


Tasks ignored

Description—The number of task commands that have been ignoredon the source


Tasks succeeded

Description—The number of task commands that have succeeded onthe source


820

Double-Take Kernel

Activation code failures

Description—The number of activation code failures when loading thesource or target, since the last time the Double-Take service wasrestarted on the source


CRC Read Time

Description—The length of time, in microseconds, spent reading CRC(cyclic redundancy check) data on the target. If this value is longer thanthe standard access time of the target's storage device, it indicatesthere is possibly an issue reading the data on the target. For example, ifthe target storage is a SAN, theremay be an issue with the way theSAN is configured.

SCOM alert—No rule defined

CRC Thread Count

Description—The number of commands being executedsimultaneously on the target. In a properly functioning environment, thisnumber should never be greater than the number of differencemirrorscurrently being executed on the sources connected to this target. If thevalue grows larger than the number of currently executing differencemirrors, that indicates there is an error condition.


Double-Take queue memory usage

Description—The amount of systemmemory in use by the Double-Take queue


Driver Queue Percent

Description—The amount of throttling calculated as a percentage ofthe stop replicating limit


Failed mirror operations

Description—The number of mirror operations on the source thatfailed due to an error reading the file from the disk


821

Failed replication operations

Description—The number of replication operations on the source thatfailed due to an error reading the file from the disk


Memory Pool Bytes Available

Description—The amount of memory, in bytes, in the Double-Takememory pool that can be used for Double-Take operations.WhenDouble-Take is at or near idle, the pool bytes available and pool totalbytes will at or near equal. If Double-Take is queuing, the pool bytesavailable will be at or near zero and the pool total bytes will be larger(near 256MB based on default settings).


Memory Pool Total Bytes

Description—The amount of memory, in bytes, that Double-Take hasallocated for memory pooling. WhenDouble-Take is at or near idle, thepool bytes available and pool total bytes will at or near equal. If Double-Take is queuing, the pool bytes available will be at or near zero and thepool total bytes will be larger (near 256MB based on default settings).


Mirror Kbytes generated

Description—The number of mirror kilobytes transmitted from thesource


Mirror operations generated

Description—The number of mirror operations transmitted from thesource


Open Target Handles

Description—The number of handles currently open on the target.


Replication Kbytes generated

Description—The number of replication kilobytes generated on thesource by the file system driver


822

Replication operations generated

Description—The number of replication operations generated on thesource by the file system driver


Double-Take Security

Failed logins

Description—Number of failed login attempts since the last time theDouble-Take service was restarted


Successful logins

Description—Number of successful login attempts since the last timethe Double-Take service was restarted


Double-Take Source

Auto disconnects

Description—The number of automatic disconnects since the last timethe Double-Take service was restarted on the source


Auto reconnects

Description—The number of automatic reconnects since the last timethe Double-Take service was restarted on the source


823

Double-Take Target

Bytes in Disk Queue

Description—The number of bytes in the target disk queue


Bytes in Queue

Description—The number of bytes in the systemmemory and diskqueues


Mirror operations received

Description—The number of mirror operations received on the target


Operations received

Description—The number of operations received on the target


Ops Dropped

Description—The number of operations dropped on the target sincethe last time the Double-Take service was restarted on the target


Ops Remaining

Description—The number of operations on the target remaining to beapplied


Orphan Bytes

Description—The number of orphan bytes removed from the target


Orphan Directories

Description—The number of orphan directories removed from thetarget


824

Orphan Files

Description—The number of orphan files removed from the target


Retries

Description—The number of retries performed on the target since thelast time the Double-Take service was restarted on the target


Tasks failed

Description—The number of task commands that have failed on thetarget.


Tasks ignored

Description—The number of task commands that have been ignoredon the target


Tasks succeeded

Description—The number of task commands that have succeeded onthe target


825

Microsoft Systems Center Operations Manager 2007Microsoft SystemsCenter OperationsManager 2007 (SCOM) is an enterprise classoperationsmanagement system that provides event management, proactivemonitoringand alerting, reporting and trend analysis, system and application specific knowledge,and configurable task responses to proactively respond to negative trends and alerts.Management Packs are pre-configured collections of these capabilities focused onmanaging a specific application or hardware type, which can be easily exported andimported into other SCOMenvironments.

The Double-TakeManagement Packwas created to help youmonitor Double-Takeoperations and provides the following features.

l Event rules to monitor all Double-Take generated events—All Double-Takegenerated events that appear in the Event Viewer can trigger a SCOMalert. Bydefault, only a subset of events are pre-selected to generate alerts, but additionalalerts can easily be generated by enabling additional event rules. SeeEventmessages on page 732 for a list of the events.

l Performance rules for threshold violations—All Double-Take performancecounters that appear in the PerformanceMonitor can generate a SCOMalertwhen the configured threshold is violated. Because every environment is unique,only a few performance thresholds are enabled by default. SeeCustomizing theManagement Pack on page 827 for instructions on configuring the performancethresholds, and seePerformanceMonitor statistics on page 818 for a list of thestatistics.

l Performance rules for performance monitoring—A subset of Double-Takeperformance counters can be graphicallymonitored in the Double-Takeperformance views, accessible from the SCOMconsole. These statistics illustratekeymetrics, such as how muchmemory or disk space Double-Take is consumingand how much data is being transmitted.

l Vendor produced knowledge for alerts—Understanding why problems existand how to fix them is an important part of operationsmanagement. The Double-TakeManagement Pack contains product knowledge for each alert, gatheredfromVision Solutions technical support. Each alert will also provide informationand links to external support.

l Double-Take specific views—VariousDouble-Take specific views are providedin the SCOMconsole.

l Alerts View—View only Double-Take alerts for computers with Double-Take installed.

l State View—View the server state for all Double-Take servers. You canalso view the various properties of all Double-Take servers, including theoverall server state.

l Events View—View Double-Take events for Double-Take servers.l Performance Data View—View graphs of various performance countersfor one or multiple computers, as defined in the performance rules.

826

Installing the Double-Take Management PackMicrosoft Management Pack for Microsoft SystemsCenter OperationsManager 2007R2 is required for the Double-TakeManagement Pack. To improve the operation of theDouble-TakeManagement Pack, you should have theOpsMgr 2007MOM2005Backward CompatibilityMP Update installed. ThisManagement Pack can be found ontheMicrosoft download site athttp://www.microsoft.com/downloads/details.aspx?FamilyID=655cdd06-861e-4342-99b2-8a81e09f6546&DisplayLang=en.

TheManagement Pack is distributed as an .xml file that is imported via the SCOMconsole.

1. Locate the Double-TakeManagement Pack using one of the followingmethods.l Start the Double-Take installation, and when the Autorun appears, selecttheGet the SCOM Management Pack link. Copy the .xml file to yourSCOMmachine.

l On the Double-Take installation CD, browse to the SCMgmt\SCOMdirectory and copy the .xml file to your SCOMmachine.

l Download theManagement Pack from the Vision Solutionssupport web siteto your SCOMmachine.

2. From the SCOMconsole, clickAdministration or selectGo,Administration.3. Right-click on theManagement Packs line item in the left pane and select Import

Management Pack.4. Navigate to the location of the Doubletake.xml file, and follow the steps in the

Management Pack Import Wizard.

See theMicrosoft SCOMdocumentation for complete installation details.

Customizing the Management PackAfter the installation, you will have the following Double-TakeManagement Pack assets.

l Double-Take Product Version Attribute—This attribute checks the Double-Take product version and is used by the Double-Take Servers computer group.

l Double-Take Servers Group and Installation Type—This asset uses aformula and regular expressionmatch on the Double-Take Product Versionattribute to determine which servers have Double-Take installed.

l Double-Take Rules—Rules can be found under theManagement PackObjectssection, and contains all of the rules that comprise theManagement Pack.Performance Rules, Alert Rules and Event Rules are grouped together under theRules category. (To see only Double-Take rules, change the scope of the Rulesgroup and filter by Double-Take Servers Installation.)

l Double-Take views—Various views are available as previously described inDouble-TakeSpecific Views.

827

http://www.microsoft.com/downloads/details.aspx?FamilyID=655cdd06-861e-4342-99b2-8a81e09f6546&DisplayLang=en








Except for vendor produced product knowledge, all aspects of theManagement Packcan bemodified by the SCOMadministrator. Use the following notes as suggestions forcustomization, and see your SCOMdocumentation for complete instructions.

l Threshold configuration—Because each server environment is different, thethresholds at which alerts should be generated will be different. To enable one ofthe pre-existing (but disabled) performance rules, right-click a performance ruleand selectProperties. On theGeneral tab, enablePerformance Rule. If youwant to customize the threshold trigger, modify the threshold value on theOverrides tab.

l Multi-tier alerting—Although only one performance rule is provided for eachperformance counter, by copying that rule and changing the alert severity andthreshold values, multi-tiered alerting is possible. For example, it is possible togenerate a warning alert when 1024MBmemory is used for queuing andgenerate an error when 512MB is consumed. Threshold values can bemodifiedon theOverrides tab. Alert severities can bemodified on theConfiguration tab,by highlighting theGenerateAlert entry and editing the XML data behind the rule.For more details, see your SCOMdocumentation.

l Enable additional event rules—Bydefault, only a pre-selected group of eventswill generate alerts. If additional alerts are desired, enable additional Event Rulesand verify the alert severity.

l Notifications—For each Double-Take Alert Rule, a notification response is pre-selected and will send the applicablemessage to the defined Recipients andnotification Subscriptions. Notification and Subscription options in SCOMdo notallow for pre-defined Double-Take notification groups. Therefore, it is requiredthat the SCOMadministrator create custom notification Recipients andSubscriptions. (Notification Groups previously used inMOM2005 can be re-created in SCOMusing the Subscriptions feature. For more information onRecipients and Subscriptions, refer to OperationsManager Help using thekeyword Notifications.)

828

SNMPSNMP, Simple NetworkManagement Protocol, is the Internet's standard for remotemonitoring andmanagement of hosts, routers and other nodes and devices on anetwork. Double-Take provides an SNMP sub-agent that can bemanaged from anSNMPManagement Console.

Double-Take installs two components to work with SNMP.

1. The sub-agent is a program that installs and runs on the samemachine asDouble-Take and gathers statistics, data, and traps. The sub-agent forwards theinformation to the SNMP agent, which relays the information to themanager. TheDouble-Take SNMP sub-agent is included in the Double-Take installationprogram.

2. A Double-TakeMIB file is placed on the administrator’smachine so that theManagement Console can interpret the data sent from the sub-agent. TheDouble-Take .mib file is dt.mib andmeets SNMP standards.

l Configuring SNMP on your server on page 829l SNMP traps on page 830l SNMP statistics on page 833

Configuring SNMP on your serverTheDouble-Take SNMP components are automatically included with the Double-Takeinstallation. However, the Double-Take .mib file will need to be loaded into your SNMPManagement Console. Depending on the type of console you are using, this processmight include compiling the .mib file. Reference your SNMPManagement Consoledocumentation for additional information.

829

SNMP trapsThe following table lists the Double-Take SNMP traps.

dttrapAutoDisconnectEndConnection

Auto-disconnect has intentionally dropped the connection

dttrapAutoDisconnectPauseTransmission

Auto-disconnect requested that the source pause sending anyoperations (create, modify, or delete)

dttrapAutoDisconnectShutdown

Auto-disconnect forced Double-Take to shut down

dttrapAutoDisconnectWriteQueue

Auto-disconnect has forced the queue to be written to disk

dttrapAutoReconnect

Auto-reconnect needs tomake a new connection

dttrapConnectionFailed

The source to target connection was not successful

dttrapConnectionLost

The source to target connection has been disconnected

dttrapConnectionPause

The source to target transmission has paused

dttrapConnectionRequested

The source has requested a connection to the target

dttrapConnectionRequestReceived

The target has received a connection request from the source

dttrapConnectionResume

The source to target transmission has resumed

dttrapConnectionSucceeded

The source to target connection has been established

830

dttrapFailoverConditionMet

Manual intervention is required because failover has detected a failedsourcemachine

dttrapFailoverInProgress

Failover or cutover is occurring

dttrapKernelStarted

Double-Take has started

dttrapKernelStopped

Double-Take has stopped

dttrapLicenseViolationOnNetwork

A Double-Take serial number conflict was identified on the network

dttrapLicenseViolationStartingSource

The source or target cannot be started due to a license violation

dttrapMemoryLimitReached

TheDouble-Takememory pool limit has been reached

dttrapMemoryLimitRemedied

Thememory pool usage is below themaximum limit specified

dttrapMirrorEnd

Mirroring has ended

dttrapMirrorPause

Mirroring has paused

dttrapMirrorResume

Mirroring has resumed

dttrapMirrorStart

Mirroring has started

dttrapMirrorStop

Mirroring has stopped

dttrapReplicationStart

Replication has started

dttrapReplicationStop

Replication has stopped

831

dttrapRepSetModified

The replication set has beenmodified

dttrapRestoreComplete

Restoration has ended

dttrapRestoreStarted

Restoration has started

dttrapScheduledConnectEnd

A scheduled end connection has been reached and the connection hasbeen disconnected

dttrapScheduledConnectStart

A scheduled connection has been started

dttrapSourceStarted

TheDouble-Take source component has started

dttrapSourceStopped

TheDouble-Take source component has stopped

dttrapTargetFull

The target is full

dttrapTargetStarted

TheDouble-Take target component has started

dttrapTargetStopped

TheDouble-Take target component has stopped

dttrapVerificationEnd

Verification has ended

dttrapVerificationFailure

Verification has the source and target are not synchronized

dttrapVerificationStart

Verification has started

832

SNMP statisticsThe following table lists the Double-Take SNMP statistics.

dtActFailCount

The number of activation code errors

dtAutoDisCount

The number of auto-disconnects

dtAutoReCount

The number of auto-reconnects

dtconBytesCompressedTx

The total number of compressed bytes transmitted to the target

dtconBytesInMirQueue

The number of mirror bytes in the queue

dtconBytesInRepQueue

The number of replication bytes in the queue

dtconBytesRx

The total number of bytes received by the target

dtconBytesTx

The total number of bytes transmitted to the target

dtconConnectTime

The length of time, in seconds, that the connection has been active

dtconIpAddress

The IP address of the connectedmachine. If you are on the source,then this will be the IP address of the target. If you are on the target,then this will be the IP address of the source.

dtConnectionCount

The number of active connections between servers

dtconOpsInAckQueue

The number of operations (create, modify, or delete) waiting forverification acknowledgements from the target

833

dtconOpsInCmdQueue

The number of operations (create, modify, or delete) in the queue onthe source

dtconOpsInMirQueue

The number of mirror operations (create, modify, or delete) in thequeue on the source

dtconOpsInRepQueue

The number of replication operations (create, modify, or delete) in thequeue on the source

dtconOpsRx

The total number of operations (create, modify, or delete) received bythe target

dtconOpsTx

The total number of operations (create, modify, or delete) transmitted tothe target

dtconResentOpCount

The number of operations that were resent because ofacknowledgement errors

dtconState

The state of the active connection

0—None. This indicates a connection has not been established.Statistics are still available for the source and target machines.

1—Active. This indicates that the connection is functioning normally andhas no scheduling restrictions imposed on it at this time. (Theremay berestrictions, but it is currently in a state that allows it to transmit.)

2—Paused. This indicates a connection that has been paused.

4—Scheduled. This indicates a connection that is not currentlytransmitting due to scheduling restrictions (bandwidth limitations, timeframe limitations, and so on).

8—Error. This indicates a connection that is not transmitting becausesomething has gone wrong (for example, lost connection).

Only the Scheduled and Error states can coexist. All other states aremutually exclusive. SNMP will display a dtconState of 12 when theconnection is in both a scheduled and an error state because this is thesum of the two values (4 + 8).

834

dtCurrentMemoryUsage

The amount of memory, in bytes, allocated from the Double-Takememory pool

dtCurrentMemoryUsageMB

The amount of memory, in MB, allocated from the Double-Takememory pool

dtDriverQueuePercent

The percentage of the driver queue that is currently in use. (This is theamount of throttling calculated as a percentage of the stop replicatinglimit.)

dtFailedLoginCount

The number of unsuccessful logins

dtFailedMirrorCount

The number of operations that failed tomirror because they could notbe read on the source

dtFailedRepCount

The number of operations that failed to be replicated because theycould not be read on the source

dtLoginCount

The number of successful logins and logouts

dtMirBytesGenerated

The number of bytes generated by themirroring driver

dtMirOpsGenerated

The number of mirror operations (create, modify, or delete) that havebeen generated by themirroring driver

dtOpsDroppedCount

The number of file operations that have failed and will not be retried

dtRepBytesGenerated

The number of bytes generated by the replication driver

dtRepOpsGenerated

The number of operations (create, modify, or delete) that have beengenerated by the replication driver

dtRetryCount

The number of file operations that have been retried

835

dtSourceState

0—Source is not running

1—Source is running without the replication driver

2—Source is running with the replication driver

dtTargetState

0—Target is not running

1—Target is running

dtUpTime

The time in seconds since Double-Take was last started

836

Chapter 20 Special network configurationsDouble-Take can be implemented with very little configuration necessary in small orsimple networks, but additional configurationmay be required in large or complexenvironments. Because an infinite number of network configurations and environmentsexist, it is difficult to identify all of the possible configurations. Review the followingsections for configuration information for that particular type of network environment.

l See Firewalls on page 838l SeeDomain controllers on page 839l SeeNetBIOS on page 840l SeeWINS on page 841l SeeDNS on page 844l SeeNon-Microsoft DNS on page 851l SeeMacintosh shares on page 853l SeeNFS Shares on page 854

837

FirewallsIf your source and target are on opposite sides of a firewall, you will need to configureyour hardware to accommodate communications. Youmust have the hardware alreadyin place and know how to configure the hardware ports. If you do not, see the referencemanual for your hardware.

l Double-Take ports—Ports 6320, 6325, and 6326 are used for Double-Takecommunications andmust be open on your firewall. Also, Double-Take usesICMP pings, by default, to monitor the source for failover. You should configureyour hardware to allow ICMP pings between the source and target. If you cannot,you will have to configure Double-Take tomonitor for a failure using the Double-Take service. See the failover instructions for your specific job type.

l Microsoft WMI and RPC ports—Some features of Double-Take (pushinstallations, DNS failover, and host-level Hyper-VWAN failover) useWMI(WindowsManagement Instrumentation) which usesRPC (Remote ProcedureCall). By default, RPC will use ports at random above 1024, and these portsmustbe open on your firewall. RPC ports can be configured to a specific range byspecific registry changes and a reboot. See theMicrosoft Knowledge Base article154596 for instructions.

l Microsoft File Share and Directory ports—Double-Take push installationswillalso rely on File Share and Directory ports, whichmust be open on your firewall.Check your Microsoft documentation if you need tomodify these ports.

l Microsoft File Share uses ports 135 through 139 for TCP and UDPcommunications.

l Microsoft Directory uses port 445 for TCP and UDP communications.l ESX ports—If you are using VirtualCenter or an ESX host, port 443 is alsorequired andmust be opened.

You need to configure your hardware so that the Double-Take ports, Microsoft Windowsports, and ESX ports. applicable to your environment are open. Since communicationoccurs bidirectionally, make sure you configure both incoming and outgoing traffic.

There aremany types of hardware on themarket, and each can be configureddifferently. See your hardware referencemanual for instructions on setting up yourparticular router.

838






Domain controllersFailover of domain controllers is dependent on the Double-Take functionality you areusing.

l Domain controller role—If you want to failover a domain controller, includingthe roles of the domain controller, you should create full server or virtualprotection.

l Non-domain controller role—If you are only protecting data, you can failover adomain controller, but the roles of the domain controller are not included. Theserver will be amember server after failover. In this case, you need to keep inmindthat the unavailability of some of the FSMO (Flexible SingleMaster Operation)roles can cause immediate issues such as the inability to extend the ActiveDirectory schema or to add a domain to a forest.

l Global catalog server—If your source is a global catalog server, you shouldhave other global catalog servers throughout the network to ensure that the failureof the source will not impact users.

839

NetBIOSBecause NetBIOS is not available onWindows 2008, if you are usingWindows 2008 in aworkgroup environment and do not have DNS host records, theremay be a delay of upto fiveminutes before the failed over source server name is available for client access.SeeAbout the NetBIOS Interface in theMSDN library.

840



WINSWhenDouble-Take failover occurs, Windows initiatesWINS registration with thetarget’s primaryWINS server to associate the source server’s namewith the target’sprimary IP address. In an environment with just oneWINS server, no additionalprocessing is required. In an environment with more than oneWINS server, WINSreplication will distribute the updatedWINS registration to other WINS servers on thenetwork. The length of time required for all WINS servers to obtain the new registrationdepends on the number ofWINS servers, theWINS replication architecture, and theWINS replication interval. Clients will be unable to access the target until their WINSserver has received the updatedWINS information. You can reduce the time required fortheWINS updates, thereby decreasing the wait time for the end users, by scripting theWINS updates in the Double-Takefailover scripts. You have two options for scripting theWINS updates.

l WINS registration on page 841—This option registers a user-specified server withWINS. It requires less network overhead but administrator groupmembership onallWINS servers.

l WINS replication on page 842—This option forcesWINS replication. It does notrequire any special privileges, but requires system and network resources tocompleteWINS replication. The impact on the network will depend on the size andcomplexity of theWINS architecture.

WINS registrationWINS registration can be added to your failover and failback scripts by using theWindowsNETSH commandwith theWINS add name context. Add the followingcommand to your failover and failback scripts for each additionalWINS server in yourenvironment (excluding the target’s primaryWINS server).

netsh wins serverwins_server_IP_address add nameName=source_server_nameRecType=1 IP={IP_address}

Use the following variable substitutions.

l wins_server_IP_address—The IP address of theWINS serverl source_server_name—The name of the source serverl IP_address—The IP address of the target that has taken over for the failedsource (for the failover script) or the IP address of the source that is reassuming itsoriginal identity (for the failback script)

For example, suppose you had the following environment.

l Source name and IP address—Alpha 192.168.1.108l Target name and IP address—Beta 116.123.2.47l Target’s Primary WINS server—116.123.2.50

841

l First secondary WINS server on the network—192.168.1.110l Second secondary WINS server on the network—150.172.114.74

You would add the following to your failover script to register the source’s namewith thetarget’s IP address on the two secondaryWINS servers.

netsh wins server 192.168.1.110 add name Name=Alpha RecType=1 IP={116.123.2.47}netsh wins server 150.172.114.74 add name Name=Alpha RecType=1 IP={116.123.2.47}

Youwould add the following to your failback script to register the source’s name backwith the source’s original IP address on the two secondaryWINS servers.

netsh wins server 192.168.1.110 add name Name=Alpha RecType=1 IP={192.168.1.108}netsh wins server 150.172.114.74 add name Name=Alpha RecType=1 IP={192.168.1.108}

See your Windows documentation or theMicrosoft web site for more details on theNETSH command.

WINS replicationWINS replication can be added to your failover and failback scripts by using theWindowsNETSH commandwith theWINS set replicate context. Add the following command toyour failover and failback scripts.

netsh wins server target’s_primary_wins_server_IP_address set replicateflag 1

Use the following variable substitution.

l target's_primary_wins_server_IP_address—The IP address of the target'sprimaryWINS server


l Source name and IP address—Alpha 192.168.1.108l Target name and IP address—Beta 116.123.2.47l Target’s Primary WINS server—116.123.2.50l First secondary WINS server on the network—192.168.1.110l Second secondary WINS server on the network—150.172.114.74

You would add the following to your failover script to force the target’s primaryWINSserver to replicate its updated information to the other secondaryWINS servers on thenetwork.

netsh wins server 116.123.2.50 set replicateflag 1

Youwould add the same line to your failback script to force the target’s primaryWINSserver to replicate its updated information again. This would replicate information for thesource’s name and the source’s original IP address to the other secondaryWINSservers on the network.

842

netsh wins server 116.123.2.50 set replicateflag 1

See your Windows documentation or theMicrosoft web site for more details on theNETSH command.

843

DNSIf you are using aMicrosoft DNS server, when Double-Take failover occurs, DNSmay ormay not be automatically updated depending on your job type and job options. If the end-users use DNS to resolve server names and the source IP addresswas not failed over tothe target, additional DNS updateswill be required because the host records for thesource will remain intact after failover. You can automate this process by scripting theDNS updates in the failover and failback scripts. You have two options for scripting theDNS updates.

l WindowsDNSCMD command on page 844—TheWindowsSupport Toolscontain a DNS Server Troubleshooting Tool utility. This utility includes theDNSCMD commandwhich can be scripted to delete and add host and reverselookup entries in DNS.

l Double-Take DFOutility on page 846—Double-Take also has a utility, called DFO(DNS Failover). The DFOutility can be used to script the deletion and addition ofthe host and reverse lookup entries in DNS. This utility can be found on theproduct CD or from the Vision Solutionssupport web site.

Windows DNSCMD commandDNS updates can be added to your failover and failback scripts by using theWindowsDNSCMD command as long as dynamic updates are enabled on the DNS zone and theaccount running the Double-Take service is amember of the DNSAdmins securitygroup. (See your Microsoft documentation to verify if dynamic updates are enabled.) Youmaywant to disable the DNS registration feature of each IP address that is beingchanged in DNS to prevent the source from changing the record backwhen it comesonline after a failover.

Add the following commands to your failover and failback scripts to delete the host andreverse lookup entries and add new entries associating the source to the target.

l dnscmdDNS_server’s_FQDN /RecordDeleteDNS_zone source_server_nameA source_server_IP_address /f

l dnscmdDNS_server’s_FQDN /RecordDeletewww.xxx.in-addr.arpa zzz.yyyPTR source_server’s_FQDN /f

l dnscmdDNS_server’s_FQDN /RecordAddDNS_zone source_server_nameA target_server_IP_address

l dnscmdDNS_server’s_FQDN /RecordAdd aaa.bbb.in-addr.arpa ddd.cccPTRsource_server’s_FQDN

Use the following variable substitutions.

l DNS_server’s_FQDN—The fully qualified domain name of the DNS serverl DNS_zone—The name of the DNS zonel source_server_name—The name of the source serverl source_server_IP_address—The IP address on the source

844




l www.xxx—The first two octets of the source’s IP address. For example, if thesource’s IP address is 192.168.1.108, this variable would be 192.168.

l zzz.yyy—The last two octets, in reverse order, of the source’s IP address. Forexample, if the source’s IP address is 192.168.1.108, this variable would be 108.1.

l source_server’s_FQDN—The fully qualified domain name of the source serverl target_server_IP_address—The IP address on the targetl aaa.bbb—The first two octets of the target’s IP address. For example, if thetarget’s IP address is 116.123.2.47, this variable would be 116.123.

l ddd.ccc—The last two octets, in reverse order, of the target’s IP address. Forexample, if the target’s IP address is 116.123.2.47, this variable would be 47.2.


l Full qualified domain name of the source—Alpha.domain.coml Source IP address—192.168.1.108l Fully qualified domain name of the target—Beta.domain.coml Target IP address—116.123.2.47l Fully qualified domain name of the DNS server—DNSServer.domain.coml DNS zone—domain.com

Youwould add the following to your failover script to delete the host and reverse lookupentries and add new entries associating the source to the target.

dnscmd DNSServer.domain.com /RecordDelete domain.com alpha A 192.168.1.108 /fdnscmd DNSServer.domain.com /RecordDelete 192.168.in-addr.arpa 108.1 PTR alpha.domain.com/fdnscmd DNSServer.domain.com /RecordAdd domain.com alpha A 116.123.2.47dnscmd DNSServer.domain.com /RecordAdd 116.123.in-addr.arpa 47.2 PTR alpha.domain.com

Youwould add the following to your failback script to delete the host and reverse lookupentries and add new entries associating the source with its original identity.

dnscmd DNSServer.domain.com /RecordDelete domain.com alpha A 116.123.2.47 /fdnscmd DNSServer.domain.com /RecordDelete 116.123.in-addr.arpa 47.2 PTR alpha.domain.com/fdnscmd DNSServer.domain.com /RecordAdd domain.com alpha A 192.168.1.108dnscmd DNSServer.domain.com /RecordAdd 192.168.in-addr.arpa 108.1 PTR alpha.domain.com

See your Windows documentation or theMicrosoft web site for more details on theDNSCMD command.

845

Double-Take DFO utilityDNS updates can be added to your failover and failback scripts by using the Double-Take DFOutility as long as the utility has been registered and the proper privileges areconfigured.

1. Extract the DFOutility to the location where the Double-Take program files areinstalled on the target.

2. From a command prompt, change to the Double-Take program files directory andregister the DFOutility by entering the command regsvr32 capicom.dll

3. Create a user account that has full control on theWMI DNS namespace on thesource’s primary DNS server.

a. If you are usingWindows 2003 SP1, use the following steps.1. SelectStart,Run, and enter the commandmmc.2. After theMicrosoft Management Console starts, select File,

Add/Remove Snap-in.3. ClickAdd, selectWMI Control, clickAdd again, confirm the local

computer is selected, and then clickFinish.4. Close the snap-in dialog box and then clickOK to return to the

console.b. If you are usingWindows 2003 SP2 or later, selectStart,Run, and enter

the commandwmimgmt.msc.c. Right-clickWMI Control and selectProperties.d. On theSecurity tab, expand the tree underRoot.e. SelectMicrosoftDNS and clickSecurity.f. ClickAdd and identify the user account that you want the DFOutility to use.g. If you are usingWindows 2003 SP1, grant the user account permissions for

ExecuteMethods, Full Write, PartialWrite, Provider Write, Enable Account,Remote Enable, and Read Security.

h. If you are usingWindows 2003 SP2 or later, use the following steps.1. Grant the user account permissions for ExecuteMethods, Enable

Account, Remote Enable, and Read Security.2. ClickAdvanced and in thePermissions list, select the user account

and clickEdit. Select This namespace and subnamespaces.i. ClickOK to close all open dialog boxes and then close the console.j. Restart theWindowsManagement Instrumentation service for the changesto take effect. .

4. If you are usingWindows 2003 SP2 or later, complete the following additionalsteps.

a. SelectStart,Run, and enter the command dcomcnfg.b. ExpandComponent Services, expandComputers, then right-clickMy

Computer and selectProperties.c. On theCOM Security tab, underAccess Permissions, clickEdit Limits.d. ClickAdd, identify the user account, and clickOK.

846

e. In thePermissions for User list, allow permissions for Local Access andRemote Access and clickOK.

f. Under Launch and Activation Permissions, clickEdit Limits.g. ClickAdd, identify the user account, and clickOK.h. In thePermissions for User list, allow permissions for Local Launch,

Remote Launch, Local Activation, and Remove Activation.i. ClickOK.j. ClickOK again.k. ExpandMy Computer, expandDCOM Config, then right-clickWindows

Management and Instrumentation and selectProperties.l. On theSecurity tab, underAccess Permissions, clickEdit.

m. ClickAdd, identify the user account, and clickOK.n. In thePermissions for User list, allow permissions for Local Access and

Remote Access and clickOK.o. ClickOK to close all open dialog boxes.p. Restart the DNS/Domain Controller.

5. Add the same user account that has full control on theWMI DNS namespace tothe domain’s DnsAdmins group where the source's primary DNS server islocated.

a. SelectStart, Programs,Administrative Tools (Common), andActiveDirectory Users and Computers.

b. Right-click theDnsAdmins group and selectProperties.c. Select theMembers tab, clickAdd, and identify the user account that you

granted full control on theWMI DNS namespace.d. ClickOK to close all open dialog boxes and then close Active Directory

Users and Computers.6. Add a user to the Server Operator group.

a. SelectStart, Programs,Administrative Tools (Common), andActiveDirectory Users and Computers.

b. SelectBuiltin, then right-click theServer Operators group and selectProperties.

c. Select theMembers tab, clickAdd, and identify the user account that yougranted full control on theWMI DNS namespace.

d. ClickOK to close all open dialog boxes and then close Active DirectoryUsers and Computers.

7. Grant the user full control over the source and target DNS records.a. SelectStart, Programs,Administrative Tools (Common), andDNS.b. Locate both the source and target records in the forward and reverse

lookup zones.c. For each record, right-click and selectProperties.d. On theSecurity tab, clickAdd and identify the user account that you

granted full control on theWMI DNS namespace, and clickOK.

847

e. In thePermissions for User list, allow permissions for Full control andclickOK.

f. ClickOK to close all open dialog boxes and repeat for each record.g. Close DNS Manager.

8. Add the appropriate DFOcommand to your failover script using the followingsyntax.

Command

DFO

Description

Used in scripts to failover DNS server name

Syntax

DFO [/DNSSRVNAME <dns_server_name>] /SRCNAME<source_fqd_name> /SRCIP <source_ip> /TARIP <target_ip> /TARNAME <target_fqd_name> [/RECORDTYPE <rec_type>] [/USERNAME <user_name> /PASSWORD<password>] [/DNSZONE <zone_name>] [/DNSDOMAIN<domain_name>] [/LOGFILE <file_name>] /FAILBACK [fb_switch] [/SETPASSWORD <user_name><password>[machine][file]] [/GETPASSWORD] [/LOCK][/UNLOCK] /TRUSTEE <trustee_name> [/VERBOSE][/FLUSHDNS /MACHINE <machine_fqd_name>] [/TTL<seconds>] [/ADDOMAIN <active_directory_domain_name> [/SOURCEDN <source_domain_name> [/TEST][/DEBUG] [/HELP]

Options

l DNSSRVNAME dns_server_name—The name of thesource domain/zone's primary DNS server. If not specified,the local machine will be used.

l SRCNAME source_fqd_name—The sourcemachine's fullyqualified domain name

l SRCIP source_ip—The sourcemachine's IP addressl TARIP target_ip—The target machine's IP addressl TARNAME target_fqd_name—The target machine's fullyqualified domain name (required only for failback)

l RECORDTYPE rec_type—The type of DNS resourcerecords tomodify or list. Values record types are ALL,MSEXCHANGE, A, CNAME, MX, PTR, STD, orSTANDARD. STD and STANDARD are used to specify anon-Exchange record (minus theMX records). By default, allrecord types are included.

848

l USERNAME user_name—The domain name of the useraccount. If not specified, the account running the utility will beused.

l PASSWORD password—The password associated with theuser account

l DNSZONE zone_name—The name of the DNS zone orDNS container, used to refine queries

l DNSDOMAIN domain_name—The name of the DNSdomain, used to refine queries

l LOGFILE file_name—The name of the log filel FAILBACK fb_switch—Denotes a failback procedure,performed after a failed source is recovered or restored(required for failback). By default, the DFOwill only failbackrecords in the dfo_failback_config.dat file. This option allowsyou to enter search criteria to identify the records to changeback, even if they are not in the configuration file. This option isalso used if the dfo_failback_config.dat file ismissing.

l SETPASSWORD user_name password machine file—Stores user credentials on the specifiedmachine in thespecified file for later use. The file will be encrypted. Thisoptionmust be run separately from amodify or list activity.

l GETPASSWORD—Retrieves previously stored usercredentials. This option can only be used if the credentialswere previously stored with the setpassword option.

l LOCK—AllowsActive Directory locking for the A record typeof the source specified without modifying the record

l UNLOCK—AllowsActive Directory unlocking for the A recordtype of the source specified without modifying the record

l TRUSTEE trustee_name—The domain account for thesourcemachine (domain\machine$). DFOattempts to denywrite permissions to the DNS A record on failover for theaccount identified as the trustee. “Denywrite permissions” isthen removed from the DNS A record on failback. This keepsthe source server from reclaiming its DNS A record if it comesback online prior to failback.

l VERBOSE—Logging and display level set to maximumdetaill FLUSHDNSMACHINEmachine_fqd_name—Runs theipconfig /flushdns command to flush the DNS cache on thespecifiedmachine. Use the fully-qualified domain name of themachine.

l TTL seconds—Specifies the number of seconds for the timeto live value of all modified records

l ADDOMAIN active_directory_domain_name—The nameof the Active Directory domain

849

l SOURCEDN source_domain_name—The name of thesource's domain

l TEST—Runs in test mode so that modifications are not made,only listed

l DEBUG—ForcesDFO to write the DNS resource record as-is to the dfolog.log file prior to anyDFOmodify or list activity.

l HELP—Displays the syntax of the DNS Failover utilityExamples

l dfo /dnssrvname gamma.domain.com /srcnamealpha.domain.com /srcip 206.31.4.10 /verbose (Lists allresource records on the specified DNS server that match thesource criteria)

l dfo /dnssrvname gamma.domain.com /srcnamealpha.domain.com /srcip 206.31.4.10 /tarip 210.11.12.13/verbose (Modifies all resource records on the specified DNSserver that match the source criteria, using the credentials ofthe account running the utility to connect to the DNS server)

l dfo /dnssrvname gamma.domain.com /srcnamealpha.domain.com /srcip 206.31.4.10 /tarip 210.11.12.13/username domain.com\admin /password /verbose (Modifiesall resource records on the specified DNS server that matchthe source criteria, using the username and password toconnect to the DNS server)

l dfo /dnssrvname gamma.domain.com /srcnamealpha.domain.com /srcip 210.11.12.13 /tarnamebeta.domain.com /tarip 206.31.4.10 /failback /verbose (Failsback all resource records on the specified DNS server thatwere changed on failover)

l dfo /setpassword domain.com\admin password (Stores theuser name and password in an encrypted file)

l dfo /dnssrvname gamma.domain.com /srcnamealpha.domain.com /srcip 206.31.4.10 /tarip 210.11.12.13/username domain.com\admin /getpassword /verbose(Modifies all resource records on the specified DNS serverthat match the source criteria, using the specified usernameand retrieving the password from the encrypted file)

850

Non-Microsoft DNSIf you are using a non-Microsoft DNS server (such asUnix) or if you are in a non-domainconfiguration (such as a workgroup), when Double-Take failover occurs, DNSmay ormay not be automatically updated depending on your job type and your job options. If theend-users use DNS to resolve server names and the source IP addresswas not failedover to the target, additional DNS updateswill be required because the host records forthe source will remain intact after failover. You can automate this process by scripting theDNS updates in the failover and failback scripts.

One option is to use a BIND DNS client for DNS scripting. The following steps provide anexample of how you can use a BIND DNS client for DNS failover and failback scripting.Youmay need tomodify this example to fit your environment.

1. Go to www.isc.org and download the appropriate BIND DNS client.2. Install the BIND client on the target server.3. Set a PATH statement for the BIND directory to ensure that it runs every time the

executable is called.4. Create a failover script file in the Double-Take directory.5. Add the following line to the failover script file, substituting your Double-Take

directory for install_location.

nsupdate.exe "c:\install_location\dnsover.txt"

6. Save the failover script file.7. Create a text file, called dnsover.txt in the Double-Take directory.8. Add the following lines to the dnsover.txt file, substituting your source name, fully-

qualified domain name, target name, and target IP address as appropriate.

update delete source_server_name.fully_qualified_domain_name.com Aupdate add target_server_name.fully_qualified_domain_name.com 86400 A target_server_IP_addresssend

9. Save the dnsover.txt file.10. Create a failback script file in the Double-Take directory.11. Add the following line to the failback script file, substituting your Double-Take

directory for install_location.

nsupdate.exe "c:\install_location\dnsback.txt"

12. Save the failback script file.13. Create a text file, called dnsback.txt in the Double-Take directory.14. Add the following lines to the dnsback.txt file, substituting your target name, fully-

qualified domain name, source name, and source IP address as appropriate.

update delete target_server_name.fully_qualified_domain_name.com Aupdate add source_server_name.fully_qualified_domain_name.com 86400 A source_

851

http://www.isc.org/

server_IP_addresssend

15. Save the dnsback.txt file.16. Change the Double-Take service on the target server to a domain account that

has rights to modify BIND DNS. Stop and start the service to have it take effect.

852

Macintosh sharesA share is any volume, drive, or directory resource that is shared across a network.During failover, the target can assume or add any source shares so that they remainaccessible to the end users. Automatic share failover only occurs for standardWindowsfile system shares. Other shares, includingMacintosh volumes, must be configured forfailover through the failover scripts or createdmanually on the target.

1. On your target, set the File Server for Macintosh service tomanual startup. Thisallows the post-failover script on the target to control when the service starts onthe target.

2. Create each volume on the target machine exactly as it exists on the source. Usethe Shared Folder wizard to configure each volume as aMacintosh-accessiblevolume. Follow these steps to start the wizard.

a. Open the Control Panel and clickAdministrative Tools.b. SelectConfigure Your Server.c. In the Configure Your Server window, click the File Server link.d. ClickStart the Shared Folder wizard to start the wizard, and then follow

the directions provided by the wizard. On the Create Shared Foldersscreen, youmust enableApple Macintosh.

You can automate the creation of the volumes during the failoverprocess by using themacfile volume command in the post-failoverbatch file. For detailed information on how to use this command,see your Windows reference guide.

3. On the target machine, copy the chngname utility, chngname.exe, from the\tools\Win2K directory of the Double-Take CD or from the Vision Solutionssupportweb site to the directory where Double-Take is installed.

4. Add the following to your failover script.

rem Commands for Macintosh-accessible volume failoverrem The chngname utility (chngname.exe) must be located in the samerem directory where Double-Take is installed.rem The following command temporarily changes the name of the server. Yourem will need to replace <drive>:\<directory>\ with the location ofrem your Double-Take chngname utility and replacerem source_name with the name of the source machine.<drive>\<directory>\chngname /s source_namerem The following command starts the File Server for Macintosh servicenet start "File server for Macintosh"rem The following command changes the name of the server back to itsrem original name. You will need to replace <drive>:\<directory>\ withrem the location of your Double-Take chngname utility.<drive>\<directory>\chngname /t

In the event of a failure, theMacintosh clientsmust remap the volume in order to accessit. From theMacintosh client, use the Chooser to select the volume that needs to beremapped.

853




NFS SharesA share is any volume, drive, or directory resource that is shared across a network.During failover, the target can assume or add any source shares so that they remainaccessible to the end users. Automatic share failover only occurs for standardWindowsfile system shares. Other shares, including NFS shares, must be configured for failoverthrough the failover scripts or createdmanually on the target.

1. On your target, set the NFS service tomanual startup. This allows the post-failover script on the target to control when the service starts on the target.

2. Create each shared drive or directory on the target exactly as it exists on thesource. Configure each drive or directory as an NFS share by following thesesteps.

a. Right-click the drive or directory that you want to share, selectSharing, andclick theNFS Sharing tab on the ProgramFiles Properties dialog box.

b. EnableShare this folder, provide the name of the share, and clickOK.3. On the target machine, copy the chngname utility, chngname.exe, from the

\tools\Win2K directory of the Double-Take CD or from the support web site to thedirectory where Double-Take is installed.

4. Add the following to your failover script.

rem Commands for NFS share failoverrem The chngname utility (chngname.exe) must be located in the samerem directory where Double-Take is installed.rem The following command temporarily changes the name of the server. Yourem will need to replace <drive>:\<directory>\ with the location ofrem your Double-Take chngname utility and replacerem source_name with the name of the source machine.<drive>\<directory>\chngname /s source_namerem The following command starts the NFS servicenet start "Server for NFS"

In the event of a failure, the clientsmust remount the shares in order to access them.

854




Chapter 21 Recommended optimizationsDouble-Take is an exceptionally flexible product that can be used in a wide variety ofnetwork configurations. However, this flexibility canmake implementing Double-Takeeffectively difficult. There is a often a balance that must be found between variousconfiguration options and their relative benefits.

Through years of testing and implementing in diverse environments, Vision Solutionshas compiled the following list of recommended optimizations. Keep inmind, what worksfor one environment or configurationmay not work in another. A best practice in oneorganizationmay be ineffective in another. You should work with Vision Solutionstechnical support or Professional Serviceswhenmaking optimization changes.

l SeePlanning on page 856l See Installation optimizations on page 857l SeeGeneral optimizations on page 858l See Full server optimizations on page 862l SeeApplication optimizations on page 863

855

PlanningBefore you begin your Double-Take installation, you should plan your implementationstrategy. Ask yourself the following questions.

l What is the role of each server?Will this server be a source?Will this server be atarget?

l Is the source server a Domain Controller? Or does it have another very specificrole or configuration? Youmaywant consider protecting the entire server in thesecases.

l Is the source runningMicrosoft Exchange or Microsoft SQL?l How much data will you be protecting? Can your target handle that amount ofdata?

l How much bandwidth is available between your source and target? Can yournetwork handle themirroring and replication traffic between the two servers? If theamount of change is greater than the bandwidth available, youmaywant toconsider getting additional bandwidth or planning for disk queuing.

If there are concerns about resource utilization or how Double-Take replication willimpact the environment, you can profile the source server, the network links between thesource and target, and the target server before installing Double-Take to ensure thateach component has adequate resources to handle the added load of replicating thedata. Most environments do not require this type of analysis, but it may be needed if thereare applications producing high-volume file writes or limited CPU, memory, disk, ornetwork resources.

The best way to understand the impact of replication in an environment is to set up testequipment that simulates the production environment. However, if the resources to testin thismanner are not available, resource utilization can be analyzed usingWindowsPerformanceMonitor and a utility to monitor network utilization. Performance datashould be logged for a period that encompasses normal usage aswell as anymaintenance, backup, scheduled jobs, or batch processing that occurs. If utilization ofany component is extremely high for a significant period of time, then it may be necessarytomodify particular Double-Take options. Keep inmind that some factors that aretypically not in a test environment, such as backups and other applications usingbandwidth, can affect resource utilization in the production environment.

Onemethod to avoid for planning purposes is estimating the amount of data that will bereplicated in a given period using the amount of data backed up in a differential backup.Although thismay be valid in some cases, it is usually not a good indicator because it isbased on the differences in data at the time of backup. For example, if a 1MBMicrosoftWord document is saved ten times throughout the day, this will result in 10MB ofreplication traffic becauseWord rewrites the entire file each time it is saved. However,this will only result in 1MB being backed up for a differential backup.

856

Installation optimizationsMake sure you review all of theCore Double-Take requirements on page 28 and anyrequirements that are specific to your job type.When you perform the installation, youwill have several decisions tomake.

l Login—Always log on to the server with an account that is in the localAdministrators group before starting the installation.

l Components—Decide what components to install and where to install them.Keep inmind that server components are required for systems that will function asa source or target, and they require an activation code for the service to run. Clientcomponents do not require an activation code, but are required to administerDouble-Take servers throughout your environment.

l Activation code—The activation code that is required for each server is a 24-character, alpha-numeric code which applies the appropriate license to yourinstallation.

l Queues—The installation will prompt you to select disk queue settings. Double-Take uses systemmemory to store data. When the Double-Take systemmemorylimit is reached, Double-Take will queue to disk.

l If you set the systemmemory limit lower, Double-Take will use less systemmemory, but you will queue to disk sooner whichmay impact systemperformance. If you set it higher, Double-Take will maximize systemperformance by not queuing to disk as soon, but the systemmay have toswap thememory to disk if the systemmemory is not available. In general,the amount of memoryDouble-Take and other applications on the serverare configured to use should be less than the amount of physical memory onthe system to prevent low memory conditions.

l Select your disk queue location for optimal performance. For example, donot put it on the same physical device as the data being replicated. Ifpossible, put it on a dedicated array optimized for writing. If you expect largeamounts of disk queuing, youmaywant to increase the size of the queuefiles from the default of 5 MB to 50MB for more efficient queuing. SeeQJournalFileSize on page 144.

SeeDouble-Take queue on page 94 for more details on the disk queue usage.

l Upgrades—Keep the following caveats in mind when upgrading.l If Double-Take does not function correctly after the upgrade, run theDouble-Take Setup, select theRepair option, and reboot the server. IfDouble-Take does not function correctly after the repair, uninstall Double-Take, reboot, and install the new version.

l If your current Double-Take version ismore than twominor versions old,youmaywant to consider uninstalling the old version and installing the newversion instead of upgrading.

l Always upgrade the target server first when upgrading a source and targetconfiguration.

857

General optimizationsThe following are general optimizations that can be used for anyDouble-Take job type.

l Performance optimizations on page 858l General manageability on page 860l Anti-virus protection on page 861l Hardware configurations on page 861

Performance optimizationsl Initial mirror across slow network—A large amount of data that is beingmirrored across a slow networkmay take days to complete the initial mirror,depending on the amount of data and the available bandwidth. Youmaywant toconsider the following options to reduce the amount of time for the initial mirror.

l Move the target server to the source's site for the initial mirror. When themirror is complete, move the target server to its permanent location andcreate a new job using a differencemirror.

l Archive the data tomedia that can be transported to the target site andrestored to the target server. When the data is restored to the target, createthe job using a differencemirror.

l Create a compressed archive of the source data, copy the archive to thetarget, uncompress the data, and then create the job using a differencemirror.

l Compression—Double-Take compression should be used when networkbandwidth between the source and target is limited. In some cases, performancemay also be improved by enabling compression in high-bandwidth environments.The best level of compression for a given solution will depend on a number offactors, including the type of data being replicated, CPU load, and availablebandwidth. Since compression settings can be changed dynamically, the easiestway to find the best level of compression is to enable themid-level andmonitor theresults. If data is still being queued on the source , increase the compression level.If CPU load becomes an issue on the server, decrease the compression level.

l Low bandwidth and queuing—In low bandwidth environments, youmay needto revisit the queuing configuration you established when you were installingDouble-Take. See the Installation optimizations on page 857 andDouble-Takequeue on page 94 for more details on the disk queue usage.

l High latency and mirror packet size—In a high latency environment (greaterthan 100ms response times), youmaywant to consider increasing the size of thepackets of mirror data. The default value is 65536 bytes. Youmaywant to doublethat to 131072 bytes. However, if the average size of the files on the source issmaller than the value you set, changing the value will not help. This option isavailable through theSource server properties on page 98.

l High latency and MaxChecksumBlocks—In a high latency environment(greater than 100ms response times), youmaywant to consider increasing the

858

number of checksum values retrieved from the target. The default is 32. Youmaywant to double that to 64.SeeMaxChecksumBlocks on page 134.

l Target write speed—In high-bandwidth environments, Double-Take throughputismost often limited by the write speed of the target disks. Accordingly, optimizingthe target disks for write performance will often increase Double-Takeperformance, particularly for full mirrors and high loads of replication. Using RAID0 and/or RAID 1 instead of RAID 5 on the target disks will improve the target writeperformance, aswell as allocating some (or all) of the I/O controller's cachememory to write operations.

l TCPBufferSize—Network throughput is directly related to the TCP buffer sizeand the network latency of the LAN or WAN connection. By default, Double-Takeis configured for a 1Gbit LAN network. If you are replicating across a different LANnetwork or aWAN network, adjust the TCP buffer size accordingly. For example,for a 100Mbit LAN, the value should be around 37500, and for aWAN, the valueshould be around 130000. See TCPBufferSize on page 157 or the technicalsupport article 31855. (The old article number is 1483.)

l Windows MTU—TheMaximumTransmission Unit (MTU) is the largest amountof data, a packet, that can be transferred in one physical frame on a network. If theMTU is too high, youmay get fragmented packets which can slow downDouble-Takemirroring and replication and can possibly cause lost Double-Takeconnections. Use the ping commandwith the -f -l 1500 options. If you receive aresponse that packets need to be fragmented, you should lower your MTU value.See theMicrosoft article 314825 for details on specifying theMTU value.

l Disable root encryption—If the top-level folders in your jobs are not encrypted,you can gain a performance improvement by disabling root encryption. SeeEnableRootEncryption on page 123.

859




General manageabilityl Temporary files—Some applications create temporary files that are used tostore information that may not be necessary to replicate. If user profiles and homedirectories are stored on a server and replicated, some unexpected datamay bereplicated if applications use the \Local Settings\Temp directory to store data. Thiscould result in significant amount of unnecessary data replication on large fileservers. Additionally, the \Local Settings\Temporary Internet Files or\AppData\Local\Microsoft\Windows\Temporary Internet Files directories caneasily reach a few thousand files and dozens of megabytes. When this ismultipliedby a hundred users it can quickly add up to several gigabytes of data that do notneed to be replicated. Youmaywant to consider excluding temporary data likethis, however it is important to know how applicationsmay use these temporaryfiles. For example, Microsoft Word creates a temporary file when a document isopened.When the user closes the file, the temporary file is renamed to the originalfile and the original file is deleted. In this case, youmust replicate that temporaryfile so that Double-Take can process the rename and delete operationsappropriately on the target.

l E-mail notification—Enable e-mail notification through theE-mail notificationconfiguration on page 102 so that you are notified when a Double-Takemessageis written to the Event log for that server.

l Target path blocking—Target path blocking prevents themodification of thecopy of the source data on the target until failover has occurred or protection isdisabled. This can be can be configured for some job types or for all jobs to a targetthrough the Target server properties on page 100.

l File difference mirrors—When performing a file differencemirror, youmay notwant to use theMirror only if the file on the source is newer than the copyon the target option, unless you know for certain that it is acceptable. This isparticularly true for database applications and domain controllers since it is criticalthat all files, not just some of them that might be newer, aremirrored.

l Disable attribute replication—On servers where the file permissions need to bedifferent on the source and target, you can disable the replication of file attributes.When attribute replication is disabled, files on the target can inherit permissionsfrom the parent directory on the target. See TGDisableAttributeReplication onpage 159.

860

Anti-virus protectionl Double-Take queue—Exclude the Double-Take queue directory on the sourceand target from any real-time scanning or scheduled system scans. If a queue fileis deleted by a process other than Double-Take, unexpected resultsmay occur,including an auto-disconnect due to the loss of queued data. The files in the sourcequeue directory have already been scanned (cleaned, deleted, or quarantined) intheir original storage location. The files in the target queue have already beenscanned (cleaned, deleted, or quarantined) on the source.

l Target data—Exclude the copy of the source data stored on the target from anyreal-time scanning or scheduled system scans. The files have already beenscanned (cleaned, deleted, or quarantined) on the source. If the replicated data onthe target must be scanned for viruses, configure the virus protection software onboth the source and target to delete or quarantine infected files to a differentdirectory that is not being protected. If the virus software denies access to the filebecause it is infected, Double-Take will continually attempt to commit operationsto that file until it is successful, and will not commit any other data until it can writeto that file. Additionally, if the virus protection software cleans the file, an operationto clean the file will likely also be replicated from the source, whichmay result in filecorruption.

Hardware configurationsl NIC teaming—If you are using NIC teaming, set it up for fault tolerance, not loadbalancing.

l Device drivers—Keep your hardware device drivers, especially NIC drivers, up-to-date.

l Port speed and duplex—Set static values for port speed and duplex on NICsand switches, if possible.

861

Full server optimizationsReview the following optimizationswhen you are using a full server protection job.

l Third machine to run Double-Take Console—Ideally, you should use a thirdmachine to run the Double-Take Console and set up protection and to performfailover and reverse. If you do not use a third machine, youmay need to removeand reinsert your servers (using reserved IP addresses) into the console. If youuse a third machine, it must be able to communicate with the reserved IPaddresses.

l Single gateway—If you are usingmultiple IP addresses onWindows 2003, donot usemultiple gateways.

l Reserved IP address—You should put your reserved IP address on separate aNIC and disable DNS registration on that NIC. This is especially important if theseparate NIC is on the same network as the production NIC.

l Single NIC—If you have to use only one NIC, disable DNS registration andensure the reserved IP address is first in the list of IP addresses. For Windows2003, if the failover IP address is listed first and it cannot come online due to IPaddress conflicts, subsequent IP addressesmay not come online. Also, theoriginal source IP addressmay need to be removedmanually after bringing theoriginal source back online.

l Disabling DNS registration—Disabling DNS registration for thereserved IP address ensures that an end-user is not communicating to the originalsource when it is failed over because two different DNS recordswill point to twodifferent servers.

l Unnecessary target components—Do not install applications, features orlanguage packs on the target that are not essential to that machine. These canslow the failover process and/or causemirroring issues.

l Vendor applications—Disable or remove any vendor applications that you arenot using. These applicationsmay cause issues after failover, like applicationcrashes or even server crashes. These applicationsmay not be in standardapplication directories, like C:\Dell or C:\cqpsystem, and those directories shouldbe added to the list of staged folders. Also, theymay use resources (likeC:\INetPub), whichmay be need after failover. Those directories would also haveto be staged.

l Hardware maintenance—If you replace a NIC after you have established fullserver protection, you should delete and re-create your job.

862

Application optimizationsReview the following optimizationswhen you are using an Exchange Server or SQLServer job or if you are protecting any other application on your source.

l SeeGeneral applications on page 863l SeeExchange on page 864l SeeSQL on page 864

General applicationsl Application services on the target—Ensure that all application services on thetarget are stopped and set to manual.

l Connection mappings—When protecting an application server, select theOneTo Onemapping when creating a files and folders job.

l File difference mirrors—When performing a file differencemirror, youmay notwant to use theMirror only if the file on the source is newer than the copyon the target option, unless you know for certain that it is acceptable. This isparticularly true for database applications and domain controllers since it is criticalthat all files, not just some of them that might be newer, aremirrored.

l Mirror using write-through mode—You can set a Double-Take driver optionwhich allowsmirroring to open files in write-throughmodewhich is the samewaymany applications, such as Exchange and SQL, open files. Thismay improveperformance on application servers. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RepKap\Parameters, add aDWORD value called DisableKfaiCaching, and set it to 1.

l Database backups—Pause the target while you perform a backup of databasefiles stored on the target because the database and log filesmust be backed upwhen they are at the exact same point in time. For example, say the back up of thefile mydatabase.mdf begins on the target. While the backup program has accessto the file, Double-Take cannot write to the file. When the backup completes,Double-Take writes to the file. Double-Take also writes to the correspondingmydatabase.ldf file. When the backup gets to themydatabase.ldf file, it no longermatches the .mdf file. The databasemay require special startup procedures,whichmay result in incomplete transactions being left in the database or data loss.To workaround this scenario, pause the target before starting the backup and thenresume the target when the backup is complete.

863

Exchangel Orphan log files—Exchange database and log files should be synchronizedbetween the source and target, including the removal of any orphan log files on thetarget. Exchangemay not recover the databases correctly if orphan log files arepresent on the target. (Orphan files are files that exist in the copy of the sourcedata on the target, but are not on the source. This usually occurs when a file isdeleted on the source when there is no Double-Take connection.) Make sure youconfigure your Exchange protection to remove orphan files.

SQLl Memory—Typically, SQL uses all availablememory. Youmaywant to considerlimiting SQLmemory usage to allow the Double-Take service to function withoutrunning out of memory.

l Temp database—Checkwith your application vendor to determine if the tempdatabase is used and needed. If it is not needed, you can exclude it fromreplication. For example, SQL Server re-creates the tempdb database file eachtime it starts, so any tempdb data that gets replicated to the target will never getused.Writes to the tempdb databasemay account for a significant percentage ofwrites to all SQL Server files, so excluding the tempdb filesmay result in much lessreplication traffic. If the database application you are using uses the tempdatabase file (for example in Prophecy, PeopleSoft, and BizTalk) or if you areuncertain, do not exclude it from replication.

l SQL service account—Configure the source and target to use the same domainaccount to start the SQL services, if possible. This eliminates the need tomoveSQLService Principal Names (SPNs) during failover and failback. If you have touse different accounts, Kerberos authentication will require the Service PrincipalNames to be failed over. See the technical support article 33398 for details onfailing over the Service Principal Names. (The old article number is 3084.)

864



Chapter 22 SecurityTo ensure protection of your data, Double-Take offer multi-level security using nativeoperating system security features. Privileges are granted throughmembership in usergroups defined on eachmachine. To gain access to a source or target, the user mustprovide a valid operating system user name and password and the specified user namemust be amember of one of the Double-Take security groups. Once a valid user nameand password have been provided and the source or target has verifiedmembership inone of the security groups, the user is granted appropriate access to the source or targetand the corresponding features are enabled in the client. Access is granted on one of thefollowing three levels.

l Administrator Access—All features are available for that machine.l Monitor Access—Servers and statistics can be viewed, but functionality is notavailable.

l No Access—Servers appear in the clients, but no access to view the serverdetails is available.

Although passwords are encrypted when they are stored, Vision Solutions securitydesign does assume that anymachine running the client application is protected fromunauthorized access. If you are running the client and step away from your machine, youmust protect your machine from unauthorized access.

l Adding users to the security groups on page 866l Changing the account used to run the Double-Take service onWindows serverson page 867

865

Adding users to the security groupsThe security groups are automatically created during the installation process.

l Windows servers—TheDouble-Take Admin and Double-TakeMonitors groupsare automatically created and the local administrator and domain administratorare automatically added to the Double-Take Admin group during installation.

l Linux servers—The groups can be local or LDAP (Lightweight Directory AccessProtocol). The groups are called dtadmin (default group ID 501) and dtmon(default group ID 502). During the installation, the user root is automatically addedto the dtadmin group.

If Double-Take is installed on aWindowsmember server, it will use the localgroups. If an Active Directory user is granted access to the Active DirectoryDouble-Take Admin or Double-TakeMonitors groups, the user or domain groupmust also be granted access to the local Double-Take groups. If Double-Take isinstalled on aWindows domain controller, the Active Directory group will providesufficient access. The groups are created in the UsersOU and need to stay here.If the groups are not there, users will be unable to log into Double-Take on thedomain controller.

Users that need administrator access to Double-Takemust be added to the Double-Take Admin or dtadmin group, depending on the operating system. Users that needmonitor only accessmust be added to the Double-TakeMonitors or dtmon group,depending on the operating system. In both cases, local users, domain users, or globalgroupsmay be added to the local groups.

See your Windows documentation for instructions on adding, deleting, or modifyingusers in a security group.

For Linux servers, use the following steps.

1. Run the DTSetup command from the shell prompt. The command is case-sensitive. Do not run DTSetup using the sudo command. Use a real root shell tolaunch DTSetup instead, either by logging in as root on the console or by using thelogin session of a non-privileged user to run su - to start a root shell.

2. SelectSetup tasks.3. SelectAdd/Remove users to Double-Take groups.4. Select the necessarymenu options to add or remove groups to the administrator

or monitors group as needed, and specify the user namewhen prompted.5. When you have completed your security groupmodifications, pressQasmany

times as needed to return back to themainmenu or to exit DTSetup.

866

Changing the account used to run the Double-Takeservice on Windows servers

By default, the Double-Take service onWindows servers is configured to log on as thesystem account. If you want to select a specific account to run the service, use theseinstructions.

If you are protecting an entire server, you cannot modify the account used to runthe Double-Take service. Otherwise, the full server protection will not functioncorrectly.

1. Modify the user account that the Double-Take service is using.a. Open the Double-Take service settings by selectingStart, Programs,

Administrative Tools, Services and double-clicking the Double-Takeservice.

b. Select the Log On tab, select This Account, and enter a valid domainaccount.

c. Enter the password for this account.d. ClickOK to save these settings.

2. Grant an additional user right to the account you are using to run the Double-Takeservice.

If domain-level policy settings are defined (throughDomain SecurityPolicy, Security Settings, Local Policies,User Rights Assignment),theywill override local policy settings.

a. SelectStart, Programs,Administrative Tools, Local Security Policy.b. Expand the Local Policies folder and highlight theUser Rights

Assignment folder.c. Double-click the optionAct as part of operating system on the right

pane of the screen.d. Add the user that you selected to run the Double-Take service and clickOK.e. Exit the Local Security Settings dialog box. This user is now configured to

run the Double-Take service.3. Add the domain account to the local administrator group.

a. SelectStart, Programs,Administrative Tools,ComputerManagement.

b. Expand the Local Users and Groups folder and highlight theGroupsfolder.

c. Right-click on theAdministrators group on the right pane of the screenand selectAdd to Group.

867

d. ClickAdd.e. Locate the domain account that you are using for the Double-Take service.

Select that account and clickOK.f. ClickOK to close the Administrators Properties dialog box.g. The domain account is now added to the local administrator group. Close

the Computer Management window.

868

Notices

Double-Take, Balance, Double-Take Availability, Double-Take Backup, Double-Take Cargo,Double-Take Flex, Double-Take for Hyper-V, Double-Take for Linux, Double-TakeMove, Double-Take ShadowCaster, Double-Take for Virtual Systems, GeoCluster, Livewire, netBoot/i, NSI,sanFly, TimeData, TimeSpring, winBoot/i and associated logos are registered trademarks ortrademarks of Vision Solutions, Inc. and/or its affiliates and subsidiaries in the United States and/orother countries. Microsoft, Hyper-V,Windows, and theWindows logo are trademarks or registeredtrademarks of Microsoft Corporation in the United States and/or other countries. All othertrademarks are the property of their respective companies.

© 1996-2012 Vision Solutions, Inc. All rights reserved.

Corporate HeadquartersVision Solutions, Inc.Irvine, California USATel: +1 (949) 253-6500

A

activation 38, 61, 65, 67, 69activation codes 45, 88adding servers 80anti-virus 23, 96, 104, 858auto-reconnect 91

C

chained configuration 21change journal 91cluster 14, 36configurations 16console 55, 62, 70, 72credentials 83options 73servers 76, 80, 84, 86

core operations 8create jobExchange 303files and folders 186full server 244full server to ESX 458full server to ESX appliance 511full server to Hyper-V 411host-level Hyper-V 637SQL 359V to ESX 537V to Hyper-V 583

credentials 83

D

deactivation 69Diagnostics target 702disk queue 45, 97DNS 844, 851domain controller 839Double-Take Admin 866Double-TakeMonitors 866DTInfo 40, 702DTResUtility.exe 37DTStat 716

E

error codes 725

870

Index

ESX 13full server to ESX 454full server to ESX appliance 504V to ESX 533

event messages 166, 731-732Exchange 12create job 303edit job 346failback 353failover 350job details 341job log 348job validation 345managing 330protection 298replication rules 305requirements 299restoration 353source 303target 305workload 304

F

failbackExchange 353files and folders 234-235, 237SQL 406

failover 10Exchange 350files and folders 233full server 289full server to ESX 501full server to ESX appliance 532full server to Hyper-V 451host-level Hyper-V 656, 677SQL 404V to ESX 578V to Hyper-V 630

file system 23files and folderscreate job 186edit job 229failback 234-235, 237failover 233job details 224job log 231job validation 228managing 213

871

protection 183replication rules 189requirements 184restoration 234-235, 237source 187target 190workload 189

firewall 34, 508, 838full server 11create job 244edit job 285failover 289job details 280job log 287job validation 284managing 269protection 239replication rules 246requirements 240reverse 292, 294source 244target 247workload 245

full server to ESXcreate job 458edit job 498failover 501job details 493job log 499job validation 497managing 482protection 454replication rules 459requirements 455source 458target 460-461workload 459

full server to ESX appliancecreate job 511failover 532job details 528managing 520protection 504requirements 505source 512

full server to Hyper-Vcreate job 411edit job 448failover 451

872

job details 443job log 449job validation 447managing 432protection 408replication rules 412requirements 409source 411target 413workload 412

G

GeoCluster 14installation 682managing 698properties 692protection 680, 685requirements 681

H

host-level Hyper-Vcreate job 637edit job 674failover 656, 677job details 669job log 675job validation 673managing 658protection 633requirements 634reverse 679source 637target 638workload 638

Hyper-V 13full server to Hyper-V 408host-level Hyper-V 633V to Hyper-V 580

I

installation 38-39, 682, 857console 55iSCSI Initiator 60Linux 51, 55notes 40Virtual Recovery Appliance 53

873

Windows 43, 47, 55, 60

J

jobExchange 303, 330, 341, 345-346, 350, 353files and folders 186, 213, 224, 228-229, 233-235, 237full server 244, 269, 280, 284-285, 289, 292, 294full server to ESX 458, 482, 493, 497-498, 501full server to ESX appliance 511, 520, 528, 532full server to Hyper-V 411, 432, 443, 447-448, 451GeoCluster 698host-level Hyper-V 637, 656, 658, 669, 673-674, 677, 679SQL 359, 384, 395, 399-400, 404, 406V to ESX 537, 546, 557, 561-562, 578-579V to Hyper-V 583, 598, 609, 613-614, 630, 632

job log 231, 287, 348, 402, 449, 499, 576, 628, 675job options 110

L

legal 869license 45, 62, 89Linux requirements 505logging 167, 704-705, 709, 713LogViewer 713

M

Macintosh 23, 853managing jobsExchange 330files and folders 213full server 269full server to ESX 482full server to ESX appliance 520full server to Hyper-V 432GeoCluster 698host-level Hyper-V 658SQL 384V to ESX 546V to Hyper-V 598

managing servers 76, 169many-to-one configuration 19memory 45, 96Microsoft Volume Shadow Copy 34mirroring 8, 23monitoring 703

874

N

NetBIOS 840networking 837NFS 854

O

one-to-many configuration 20one-to-one configuration 17optimizations 855applications 863full server 862general 858installation 857planning 856

overview 7-8, 11, 16, 70

P

PerformanceMonitor 817-818ports 34, 508, 838pre-requisites See requirementsPRO tips 656protectionExchange 298, 303files and folders 183, 186full server 239, 244full server to ESX 454, 458full server to ESX appliance 504, 511full server to Hyper-V 408, 411GeoCluster 680, 685host-level Hyper-V 633, 637overview 7, 174simulating 702SQL 355, 359V to ESX 533, 537V to Hyper-V 580, 583

Q

queue 91, 94quorum 682

R

replication 9, 23

875

replication rulesExchange 305files and folders 189full server 246full server to ESX 459full server to Hyper-V 412SQL 360

requirementsconsole 72core 28Exchange 299files and folders 184full server 240full server to ESX 455full server to ESX appliance 505full server to Hyper-V 409GeoCluster 681host-level Hyper-V 634Linux 505SQL 356V to ESX 534V to Hyper-V 581

restoreExchange 353files and folders 234-235, 237SQL 406

reversefull server 292, 294host-level Hyper-V 679V to ESX 579V to Hyper-V 632

S

security 865-867server details 84server events 166server properties 86-88, 91, 94, 98, 100, 102, 105-106, 110silent installWindows 47

simulating protection 702single server configuration 22snapshots 34, 170SNMP 829-830, 833source 7Exchange 303files and folders 187full server 244full server to ESX 458

876

full server to ESX appliance 512full server to Hyper-V 411host-level Hyper-V 637SQL 359V to ESX 537V to Hyper-V 583

SQL 12create job 359edit job 400failback 406failover 404job details 395job log 402job validation 399managing 384protection 355replication rules 360requirements 356restoration 406source 359target 361workload 360

statistics 715-716, 718, 817-818, 833synchronization 8SystemCenter Virtual MachineManager (SCVMM) 656SystemsCenter OperationsManager (SCOM) 826

T

target 7Diagnostics 702Exchange 305files and folders 190full server 247full server to ESX 460-461full server to Hyper-V 413host-level Hyper-V 638SQL 361V to ESX 538V to Hyper-V 584

Throughput Diagnostics Utility (TDU) 702traps 830

U

upgrade 38-39console 55Linux 51, 55notes 40

877

Virtual Recovery Appliance 53Windows 43, 47, 55

V

V to ESXcreate job 537edit job 562failover 578job details 557job log 576job validation 561managing 546protection 533requirements 534reverse 579source 537target 538

V to Hyper-Vcreate job 583edit job 614failover 630job details 609job log 628job validation 613managing 598protection 580requirements 581reverse 632source 583target 584workload 584

verification 107virtual 13full server to ESX 454full server to ESX appliance 504full server to Hyper-V 408host-level Hyper-V 633V to ESX 533V to Hyper-V 580

VSS 34

W

WINS 841workload 11Exchange 304files and folders 189full server 245

878

full server to ESX 459full server to Hyper-V 412host-level Hyper-V 638SQL 360V to Hyper-V 584

879