Replicate

User’s Guide

First Edition (November 2009)

Part Number: T5437-96010
© Copyright 2009 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particul
ar purpose. Hewlett-Packard shall not be liable for errors
contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this
material.
This document contains proprietary information, which is protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The
information contained in this documentis subject to change without notice.
Microsoft®, Windows®, and Windows NT® are U.S. re gistered trademarks of Microsoft Corporation.
Hewlett-Packard Company shall not be liablefor technical or editorial errors or om issions contained herein. The information
is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard
Company products are set forth in the express limited warranty statements for suchproducts. Nothing herein should be
construed as constituting an additional warranty.
HP StorageWorks Storage Mirroring Replicate User’s Guide
First Edition (November 2009)
Part Number: T5437-96010

Double-Take, GeoCluster, Double-Take for Vi rtual Systems, TimeData, netBoot/i, winBoot/i, Double-Take Cargo, sanFly, Livewire, NSI, Balance, Double-
Take ShadowCaster, and associated logos are registered trademarks or trademarks of Double-Take Software, Inc. and/or its subsidiaries in the United States
and/or other countries. Microsoft, Windows, and the Windows logo are trademarks or registered tr ademarks of Microsoft Corporati on in the United States
and/or other countries. All other trademarks are the property of their respective companies.
© 2009 Double-Take Software, Inc. All rights reserved.
Table of Contents
Table of Contents 1
Storage Mirroring Replicate overview 4
TimeData continuous data protection 6
Ontrack PowerControls 7
Cargo archiving 8
Storage Mirroring Replicate requirements 9
Source server requirements 10
Repository server requirements 11
Recovery server requirements 13
TimeData requirements 15
Ontrack PowerControls requirements 16
Cargo requirements 17
Console requirements 19
Replication capabilities 20
Installation 24
Installation and upgrade notes 25
Installing or upgrading Storage Mirroring Replicate 27
Installing Storage Mirroring Replicate automatically 30
Installing TimeData continuous data protection 35
Upgrading to SQL Server 2008 Standard 36
Installing and configuring Ontrack PowerControls 37
Managing server licenses 38
Storage Mirroring Replicate console 40
Importing a job 41
Clearing console security credentials 43
Source protection 44
Protecting your source 45

1 of 195
 Optional protection settings 51
Compressing data for transmission for a protection job 51
Limiting bandwidth for a protection job 51
Routing transmission for a protection job 52
E-mailing repository server event messages 52
Data on the repository server 55
Viewing and retrieving data from snapshots or from a TimeData point in time 56
Viewing and retrieving Exchange data 59
Recovery 60
Installing Storage Mirroring Replicate on the recovery server 61
Recovering an entire server to an existing physical or virtual machine 62
Recovering an entire server to an automatically provisioned virtual machine on
68
VMware ESX
Recovering an entire server to an automatically provisioned virtual machine on
76
Hyper-V
Recovering data to an existing physical or virtual machine 82
Optional recovery settings 87
Compressing data for transmission for a recovery job 87
Limiting bandwidth for a recovery job 87
Routing transmission for a recovery job 88
E-mailing recovery server event messages 88
Job monitoring 91
Monitoring a job through the Storage Mirroring Replicate console 92
Monitoring log files 103
Monitoring event messages 104
Event messages 104
E-mailing source event messages 145
Statistics 148
Viewing the statistics file 149
Statistics 150

2 of 195
 Performance Monitor 158
Monitoring Performance Monitor statistics 158
Performance Monitor statistics 158
SNMP 163
Configuring SNMP on your server 163
SNMP traps 164
SNMP statistics 166
Error codes 170
Cargo archiving 177
Configuring archiving security 178
Running an archive preview report 181
Manually archiving data 183
Archiving files individually 183
Archiving groups of files based on criteria 183
Archiving data on a schedule 185
Choosing a storage location for archived files on the repository server 187
Recalling archived files 189
Recalling files individually 189
Recalling all files 189
Using firewalls 191
Storage Mirroring Replicate ports 192
Microsoft Windows ports 194
Hardware ports 195

3 of 195
Storage Mirroring Replicate overview
Storage Mirroring Replicate is a comprehensive disk-to-disk backup and recovery
solution. It allows you to protect a production server, known as a source, by replicating
data from the source or an image of the entire source to another server, known as a
repository server. The repository server can be located locally or over a WAN. The
image of an entire source contains all of the source server’s data and the source server’s
system state, which is the server’s configured operating system and the installed
applications. The data or entire server image can be recovered to a dissimilar physical
or virtual environment.
As changes are made on the source, Storage Mirroring Replicate mirroring and
replication keeps the image of the source stored on the repository server up-to-date.
Storage Mirroring Replicate replicates, in real-time, only the file changes rather than
copying entire files, allowing you to more efficiently use resources.

In the event the source should fail, you can use the image of the source, stored on the
repository server, to quickly and easily create a new source, which can be a physical or
virtual machine.

4 of 195
Storage Mirroring Replicate also provides features that enhance or extend the benefits of
disk-to-disk protection.
● TimeData continuous data protection enhances the recoverability of data by
providing any-point-in-time recovery of data or entire servers.
● Ontrack PowerControls, an optional feature, adds Exchange data recovery
allowing you to recover messages, folders, attachments, mailboxes, and so on to
an Exchange Server or a .pst file.
● Cargo source disk optimization saves disk space on the source server by archiving
old files to the repository server.
● Atom file-level deduplication reduces storage requirements on the repository
server by storing duplicate files only once. This feature will be available in a future
release.

5 of 195
TimeData continuous data protection
Storage Mirroring Replicate provides the TimeData continuous data protection feature
that records every change made to the source image. With every change recorded on
the repository server, recovery can occur from any point within the continuous data
protection window specified by the user.
TimeData is installed and runs on the repository server. It keeps track of all changes to
the source image. Changes are temporarily stored in the Event cache until they can be
processed and stored in the Event log.

The longer TimeData stores all changes, the more disk space is consumed. To reduce
disk space usage you should keep changes for only as long as needed and rely on
Storage Mirroring Replicate snapshots for older point-in-time-recovery. For example,
retain the last seven days of all changes using TimeData continuous data protection and
rely on Storage Mirroring Replicate snapshots for older points in time.

6 of 195
Ontrack PowerControls
If you purchased a Storage Mirroring Replicate Repository with Ontrack PowerControls
license, you can recover Exchange data including messages, folders, attachments,
mailboxes, and so on to an Exchange Server or a .pst file.

Ontrack PowerControls can recover Exchange data from the repository server from live
data, a Storage Mirroring Replicate snapshot, or from a TimeData continuous data
protection window.

7 of 195
Cargo archiving
Cargo reduces the amount of disk space used on a source server by identifying files on
the source that have not been accessed recently and converting those files to links to the
repository server. The conversion process deletes the contents of the file from the source
server, creates a reparse point to the full contents of the file on the repository server, and
marks the file as sparse. In simpler terms, the source file becomes an empty pointer to
the full contents of the file located on the repository server. When an archived file on the
source is accessed, the full contents are recalled seamlessly from the repository server
with no interruption to the requesting user or application.

Storage Mirroring Replicate can archive files based on the age of files, allowing you to
keep newer files fully on the source. You can exclude files from archiving based on size,
which is useful for excluding small files where the archiving benefit would be minimal.
When a file has been archived, the link file is still accessible on the source. The link file
has an offline file attribute associated with it. When an end-user attempts to access the
link file, the contents of the file are recalled from the repository server back to the source.
The file opens to the end-user as if it had always been fully on the source.
To help you plan archiving and fine-tune your archive settings, you can generate a
preview report. The archiving preview report does not actually archive any data but
reports how much data would be archived based on the settings you select.

8 of 195
Storage Mirroring Replicate
requirements
Each Storage Mirroring Replicate server must meet minimum requirements. Additionally,
the machine where you will be running the Storage Mirroring Replicate console must
also meet some basic requirements.
● Source server—This is the server that contains the data you will be protecting.
Verify your server meets the source server requirements.
● Repository server—This is the server that will be protecting your source server(s).
Verify your server meets the repository server requirements.
● TimeData —The TimeData feature can be run on your repository server and
has additional minimum requirements for the repository server. TimeData
records every change made to the source image(s) on the repository server
allowing you to recover from any point within the TimeData window. Verify
your server meets the repository server and TimeData requirements.
● Ontrack PowerControls—The Ontrack PowerControls feature can be run
on your repository server and has additional minimum requirements for the
repository server. Ontrack PowerControls allows you to recover Microsoft
Exchange messages, folders, attachments, mailboxes, and so on to an
Exchange server or a .pst file. Verify your server meets the repository server
and Ontrack PowerControls requirements.
● Recovery server—This is the server that will become your new source when you
are recovering an entire server. This server can be an existing physical or virtual
machine or Storage Mirroring Replicate can provision (automatically create) a
virtual machine for you during the recovery process. Verify your server meets the
recovery server requirements.
● Cargo —Cargo can be run on your source(s) and repository server. Cargo
archives old files on the source to the repository server, thus reducing the amount
of disk space used on the source. Verify your servers meets the source server,
repository server, and Cargo requirements.
● Console—The Storage Mirroring Replicate console is used to manage your
Storage Mirroring Replicate servers. Verify the machine where you are running the
console meets the console requirements.

In addition to the server and feature requirements, review the Replication capabilities to
understand the type of data that Storage Mirroring Replicate protects.

9 of 195
Source server requirements
This is the server that contains the data you will be protecting.
● Operating system—Storage Mirroring Replicate can protect a physical or virtual
source server running any of the following operating system editions.
● Windows Server 2008 Datacenter, Enterprise, Standard, Essential Business
Server, Web Server, Foundation Server, Small Business Server, or Storage
Server Edition
● Windows Server 2003 or 2003 R2 Datacenter, Enterprise, Standard, Web
Edition, Small Business Server, or Storage Server Edition. Each of the
Windows 2003 operating systems require Service Pack 1 or later.
● Architecture—32-bit and 64-bit architectures are supported
● File system—Storage Mirroring Replicate supports the same file system formats
that Microsoft supports: FAT, FAT32, and NTFS.
● System memory—There are different memory requirements depending on the
system architecture you are using. Be sure you have at least the minimum amount
of memory for your environment. You should consider having at least the
recommended amount of system memory.

Architecture Minimum System Memory Recommended System Memory

32-bit 128 MB At least 512 MB

64-bit 512 MB At least 1024 MB

● Disk space for program files—This is the amount of disk space, approximately
130 MB, needed on the source to hold the Storage Mirroring Replicate program
files.
● Server name—Storage Mirroring Replicate includes Unicode file system support,
but your server name must be in ASCII format.
● Network protocols—Your servers must use TCP/IP with static IP addressing.
● Microsoft .NET Framework—Version 3.5 Service Pack 1 is required on the
source.
● Junction points—Only domain controller junction points will be replicated. Any
user-created junction points will be replicated as two unlinked copies of the data.

10 of 195
Repository server requirements
This is the server that will be protecting your source server(s).
● Operating system—The repository server can be a physical or virtual server
running any of the following operating system editions.

If you are protecting an entire server, your repository server must have a
same or newer operating system than the source (not including service
Note: pack level). For example, you cannot protect a Windows 2008 source to a
Windows 2003 repository server. This is because the repository server
must be able to process the source's registry for system state processing.

● Windows Server 2008 Datacenter, Enterprise, Standard, Essential Business

Server, Web Server, Foundation Server, Small Business Server, or Storage
Server Edition
● Windows Server 2003 or 2003 R2 Datacenter, Enterprise, Standard, Web
Edition, Small Business Server, or Storage Server Edition. Each of the
Windows 2003 operating systems require Service Pack 1 or later.
● Architecture—32-bit and 64-bit architectures are supported
● File system—Storage Mirroring Replicate supports the same file system formats
that Microsoft supports: FAT, FAT32, and NTFS.
● System memory—There are different memory requirements depending on the
system architecture you are using. Be sure you have at least the minimum amount
of memory for your environment. You should consider having at least the
recommended amount of system memory, especially if your repository server is
protecting multiple source servers.

Architecture Minimum System Memory Recommended System Memory

32-bit 128 MB At least 1024 MB

64-bit 512 MB At least 2048 MB

● Disk space for program files—This is the amount of disk space, approximately
130 MB, needed on the repository server to hold the Storage Mirroring Replicate
program files.
● Disk space for data files—This is the amount of disk space on the repository
server to hold all of the source data files. This will be dependent on the number of
sources you are protecting, the applications you are running on each source, and
the amount of data files on each source.

11 of 195
● Disk space for system state image—This is the amount of disk space on the
repository server to hold the image of the source system state. You should have at
least 5 GB of space on the repository server for the system state. The more
applications you are running on the source, the larger the system state image will
be. Therefore, you may need additional space if you source has many
applications. If your repository server is protecting multiple sources, you will need
space for each source's system state.
● Server name—Storage Mirroring Replicate includes Unicode file system support,
but your server name must be in ASCII format.
● Mount point limitations—You cannot store your source data or source image on
the repository server on a volume that is accessed by a mount point.
● Network protocols—Your servers must use TCP/IP with static IP addressing.
● Microsoft .NET Framework—Version 3.5 Service Pack 1 is required on the
repository server.

12 of 195
Recovery server requirements
This is the server that will become your new source when you are recovering an entire
server. This server can be an existing physical or virtual machine or Storage Mirroring
Replicate can provision (automatically create) a virtual machine for you during the
recovery process.
● Operating system—You have several options for your recovery server operating
system.
● Physical or existing virtual—If your recovery server is a physical server or
an existing virtual server, it can have any of the following Windows operating
system editions. A physical or existing virtual recovery server must have the
same operating system as the original source.
● Windows Server 2008 Enterprise, Standard, Web, Small Business
Server, Enterprise x64, or Standard x64
● Windows Server 2003 or 2003 R2 Enterprise, Standard, Web, Small
Business Server, Enterprise x64, or Standard x64. Each of the
Windows 2003 operating systems require Service Pack 1 or later.
● Provisioned virtual—If your recovery server will be provisioned
(automatically created during the recovery process) you must have a physical
host machine where Storage Mirroring Replicate can create the new virtual
server. Your physical host machine can be any of the following operating
systems.
● Windows 2008 Hyper-V
● The Enterprise Edition of VMware ESX version 3.0.x, 3.5, or 4.0. If you
are using version 3.0.1, you must have HotRemove patch #6921838.
VMware ESXi versions 3 or 4 are also supported as long as ESXi is
managed by VCenter or VSphere.
● You must have an existing virtual machine, known as a virtual
recovery appliance, running Windows Server 2008, 2003, or 2003
R2. The virtual recovery appliance must have a same or newer
operating system than the original source (not including service
pack level).
● The existing virtual must have Storage Mirroring Replicate
installed and licensed on it before you can start the recovery
process.
When you are ready for recovery the existing virtual will create the new
virtual server, mount disks, format disks, and so on. Once the new
virtual machine is online, it will have the identity, data, and system state

13 of 195
 of the original source. Since the existing virtual machine maintains its
own identity, it can be reused for additional recoveries.
● System memory—There are different memory requirements depending on the
system architecture you are using. Be sure you have at least the minimum amount
of memory for your environment. You should consider having at least the
recommended amount of system memory.

Architecture Minimum System Memory Recommended System Memory

32-bit 128 MB At least 512 MB

64-bit 512 MB At least 1024 MB

● Disk space for program files—This is the amount of disk space, approximately
130 MB, needed on the recovery server to hold the Storage Mirroring Replicate
program files.
● Disk space for data files—This is the amount of disk space on the recovery
server to hold all of the source data files. This will be dependent on the
applications you are running and the amount of data files you have.
● Disk space for system state image—This is the amount of disk space on the
recovery server to hold the image of the source system state. You should have at
least 5 GB of space on the recovery server for the system state. The more
applications you are running on the source, the larger the system state image will
be. Therefore, you may need additional space if you source has many
applications.
● Disk types—Thin-provisioned virtual disks on VMware ESX are not supported
because they cannot be shared by two virtual machines simultaneously.
● Server name—Storage Mirroring Replicate includes Unicode file system support,
but your server name must be in ASCII format.
● Network protocols—Your servers must use TCP/IP with static IP addressing.
● Microsoft .NET Framework—Version 3.5 Service Pack 1 is required on the
recovery server.

14 of 195
TimeData requirements
In addition to the repository server requirements, the following requirements apply to the
TimeData continuous data protection functionality of Storage Mirroring Replicate.
● Operating system—If your repository server is running a Windows 2003 operating
system, you must have Service Pack 2 installed on the server.
● File system—NTFS is the only supported file system. Do no use FATx file
systems on the repository server.
● System memory—The minimum system memory requirements for the repository
server are higher with TimeData continuous data protection.

Architecture Minimum System Memory Recommended System Memory

32-bit 1 GB 2 GB

64-bit 2 GB 4 GB

● Disk space for program files—This is the amount of disk space, approximately 1.
5 GB, needed on the repository server to hold the TimeData program files.
● Disk space for TimeData historical data—This is the amount of disk space,
approximately two and a half times the amount of data being protected for each
source, needed on the repository server to hold the TimeData continuous data
protection historical data. You may need to adjust the amount of disk space
needed based on the applications and data on your source, the number of days of
historical data you choose to store, and the change rate of your data. There is a
combined limit of 2 TB of TimeData historical data for all sources that you are
protecting to the repository server.
● Microsoft Internet Information Services—Microsoft IIS version 5.0 or later is
required on the repository server.
● Microsoft ASP.NET—The version of Microsoft ASP.NET included with your
Windows operating system is required on the repository server.
● Microsoft SQL Server—TimeData will automatically install Microsoft SQL Server
Express or Standard, depending on your Storage Mirroring Replicate media (CD or
web download).
● Drive configuration—For best results using TimeData continuous data protection,
you should separate the operating system, SQL Server, the TimeData drive, Event
log, and Event cache on different drives.

15 of 195
Ontrack PowerControls requirements
Ontrack PowerControls supports recovery from the following versions of Exchange.
● Exchange Server 5.5
● Exchange Server 2000
● Exchange Server 2003
● Exchange Server 2007
Ontrack PowerControls can recover from an unlimited number of Exchange servers.
In addition to the repository server requirements, the storage files (.edb files) that Ontrack
PowerControls will open must be accessible locally or over the network.

16 of 195
Cargo requirements
In addition to the source and repository server requirements, the following requirements
apply to the Cargo archiving functionality of Storage Mirroring Replicate.
● Operating system—The following operating system and file system requirements
apply to archiving.
● You must use the NTFS file system. FAT and FAT32 are not supported for
archiving.
● Transactional files on Windows 2008 are not supported. Any request for a
recall within a transaction will generate a sharing violation error and the
recall will not occur. The application can open and read a byte outside of a
transaction to cause the recall to occur and then proceed with the transaction.
● Do not modify the system attributes on any file or folder. Incorrect system
attributes could case data to be skipped for archiving, or it could cause
source crashes because the full system files must remain available on the
source.
● Because the archiving feature uses the file access date and time, do not
disable the Windows system setting that updates file access date and time. If
this setting is disabled, the archiving functionality will not behave as
expected.
● Archiving can only be performed on non-system volumes. (The system
volume is where the Windows system files are located.)
● Network configuration—The following network configuration requirements apply
to archiving.
● Workgroup environments are not supported. The source and repository
server should be member servers in a domain environment.
● The source can be a domain controller as long as Active Directory and
system data is not selected for archiving.
● Security—Specific archiving security configuration must be completed before
using the archiving functionality.
● Anti-virus—You must configure your anti-virus software to skip archived files or
the archived files will be recalled during virus scans. Additionally, you must
configure you anti-virus software so that the Storage Mirroring Replicate
application is a low-risk process. Configure the low-risk processes so that they do
not scan when writing to or reading from the disk. If you need assistance
configuring your anti-virus software, see your virus software documentation. Keep
in mind that your anti-virus software may refer to archived files differently, for
example, offline, migrated, or sparse files.

17 of 195
● Cargo functionality—Review the following requirements, limitations, and
informational notes before using the archiving feature.
● Archiving supports a one-to-one or many-to-one source to repository server
configuration. A one-to-many protection job is not supported for archiving
because if there were multiple links, the source would not know which
repository server to recall from.
● Storage Mirroring Replicate will not archive the following file types.
● System files
● Alternate data streams
● Encrypted files
● Reparse points
● Archiving is not a continuous process. It can be initiated manually or a
schedule can be established.
● Only data that is being protected by Storage Mirroring Replicate will be
archived. If you exclude data when configuring your source protection job,
that excluded data will not be eligible for archiving.
● Modifying the attributes of a link file on the source will not recall the contents
of the file from the repository server. The attribute changes will be replicated
to the copy of the file on the repository server, but the source will remain a
link file.
● Storage Mirroring Replicate automatically creates a DTArchiveBin share on
the repository server for archiving activity. Do not modify the name or security
permissions of the share. If Storage Mirroring Replicate does not find the
expected share name and permissions, users will be unable to recall their
data.
● The DTArchiveBin maintains the only copy of your archived files. You may
want to consider regularly backing up the copy of the data on the repository
server and the DTArchiveBin, for example to a tape backup.
● When an archived file is deleted, the link on the source is deleted. The
archived content in the DTArchiveBin will be deleted also if there is an active
protection job present with replication enabled.
● Briefcase files cannot be archived and will cause an error in the Storage
Mirroring Replicate log. These files should be added to the list of files
excluded from the archive process.
● Cargo archiving is not compatible with TimeData continuous data protection.
If you use one, do not use the other.

18 of 195
Console requirements
The Storage Mirroring Replicate console is used to manage your Storage Mirroring
Replicate servers.
● Operating system—The Storage Mirroring Replicate console can be run from a
source or repository server. It can also be run from a Windows XP or Vista
machine.
● Microsoft .NET Framework—Version 3.5 Service Pack 1 is required to run the
console.

19 of 195
Replication capabilities
Storage Mirroring Replicate replicates file and directory data stored on any Windows file
system (FAT, FAT32, NTFS4, and NTFS5). Replicated items also include Macintosh
files, compressed files, NTFS attributes and ACLs (access control list), dynamic
volumes, files with alternate data streams, sparse files, and encrypted files. Files can be
replicated across mount points, even though mount points are not created on the
repository server. Some reparse points are replicated, including CommVault Data
Migrator and BridgeHead Software HT FileStore.
Typically, Storage Mirroring Replicate does not replicate items that are not stored on the
file system, such as physical volume data and registry based data. Nor does it replicate
NTFS extended attributes, registry hive files, Windows or any system or driver pagefile,
system metadata files ($LogFile, $Mft, $BitMap, $Extend\\$UsnJrnl, $Extend\\$Quota,
$Extend\\$ObjId, and $Extend\\$Reparse), hard links, or the Storage Mirroring Replicate
disk-based queue logs. However, if you are protecting a full-server, Storage Mirroring
Replicate will automatically gather and replicate all necessary system state data,
including files for the operating system and applications.
Note the following replication caveats.
1. If you have mixed file systems, keep in the mind the following.
a. If, on your source, you have a FAT volume mounted on a directory which
resides on an NTFS volume, these files will not be mirrored, regardless of the
target file system. Replication will work correctly. To work around this issue,
make sure both volumes are NTFS.
b. If you are mirroring/replicating from an NTFS source to a FAT target, you may
see additional error messages in your Storage Mirroring Replicate log file
because the target file system cannot handle the NTFS attributes or file
permissions. For example, if your protection job contains files with alternate
data streams, you will see messages indicating that there are unfinished
operations because the FAT file system cannot store the alternate data
stream information.
c. If you select a compressed file or folder from an NTFS partition and replicate
it to a FAT target, the attributes are lost, but the data is maintained.
2. If any directory or file contained in your protection job that specifically denies
permission to the system account or the account running the Storage Mirroring
service, the attributes of the file on the target will not be updated because of the
lack of access. This also includes denying permission to the Everyone group
because this group contains the system account.
3. If you select a dynamic volume and you increase the size of the volume, the target
must be able to compensate for an increase in the size of the dynamic volume.
4. If you select files with alternate data streams, keep in mind the following.

20 of 195
 a. Alternate data streams are not included in the protection job size calculation.
Therefore, you may see the mirror process at 100% complete while mirroring
continues.
b. The number of files and directories reported to be mirrored will be incorrect. It
will be off by the number of alternate streams contained in the files and
directories because the alternate streams are not counted. This is a reporting
issue only. The streams will be mirrored correctly.
c. Use the checksum option when performing a difference mirror or verification
to ensure that all alternate data streams are compared correctly.
d. If your alternate streams are read-only, the times may be flagged as different
if you are creating a verification report only. Initiating a remirror with the
verification will correct this issue.
5. If you select encrypted files, keep in mind the following.
a. Only the data, not the attributes or security/ownership, is replicated. However,
the encryption key is included. This means that only the person who created
the encrypted file on the source will have access to it on the target.
b. Only data changes cause replication to occur; changing security/ownership
or attributes does not.
c. Replication will not occur until the Windows Cache Manager has released
the file. This may take awhile, but replication will occur when Storage
Mirroring Replicate can access the file.
d. When remirroring, the entire file is transmitted every time, regardless of the
remirror settings.
e. Empty encrypted files will be mirrored to the target, but if you copy or create
an empty encrypted file within the protection job after mirroring is complete,
the empty file will not be created on the target. As data is added to the empty
file on the source, it will then be replicated to the target.
f. When you are replicating encrypted files, a temporary file is created on both
the source and target servers. The temporary file is automatically created in
the same directory as the Storage Mirroring Replicate disk queues. If there is
not enough room to create the temporary file, an out of disk space message
will be logged. This message may be misleading and indicate that the drive
where the encrypted file is located is out of space, when it actually may be
the location where the temporary file is trying to be created that is out of disk
space.
6. If you are using mount points, keep in mind the following.
a. By default, the mount point data will be stored in a directory on the target.
You can create a mount point on the target to store the data or maintain the
replicated data in a directory. If you use a directory, it must be able to handle

21 of 195
 the amount of data contained in the mount point.
b. Recursive mount points are not supported. If you select data stored on a
recursive mount point, mirroring will never finish.
7. Storage Mirroring Replicate supports transactional NTFS (TxF) write operations,
with the exception of TxF SavePoints (intermediate rollback points).
a. With transactional NTFS and Storage Mirroring Replicate mirroring, data that
is in a pending transaction is in what is called a transacted view. If the
pending transaction is committed, it is written to disk. If the pending
transaction is aborted (rolled back), it is not written to disk.
During a Storage Mirroring Replicate mirror, the transacted view of the data
on the source is used. This means the data on the target will be the same as
the transacted view of the data on the source. If there are pending
transactions, Storage Mirroring Replicate will indicate this state. As the
pending transactions are committed or aborted, Storage Mirroring Replicate
mirrors any necessary changes to the target. Once all pending transactions
are completed, the state will be updated.
If you see the pending transactions state, you can check the Storage
Mirroring Replicate log file for a list of files with pending transactions. As
transactions are committed or aborted, the list is updated until all transactions
are complete.
b. During replication, transactional operations will be processed on the target
identically as they are on the source. If a transaction is committed on the
source, it will be committed on the target. If a transaction is aborted on the
source, it will be aborted on the target.
c. When recovery occurs any pending transactions on the target will be aborted
before the source identity is assigned to the target.
8. Storage Mirroring Replicate supports Windows 2008 symbolic links and junction
points. A symbolic link is a link (pointer) to a file. Junction points are also links, but
to folders and volumes.
a. If the link and the file/folder/volume are both in your source protection job,
both the link and the file/folder/volume are mirrored and replicated to the
target.
b. If the link is in the source protection job, but the file/folder/volume it points to
is not, only the link is mirrored and replicated to the target. The
file/folder/volume that the link points to is not mirrored or replicated to the
target. A message is logged to the Storage Mirroring Replicate log identifying
this situation.
c. If the file/folder/volume is in the source protection job, but the link pointing to
it is not, only the file/folder/volume is mirrored and replicated to the target.

22 of 195
 The link pointing to the file/folder/volume is not mirrored or replicated to the
target.
9. Short file names are not supported on FAT file systems.

23 of 195
Installation
Review the Storage Mirroring Replicate requirements and Installation and upgrade
notes before beginning your installation. You have the following installation options
available.
● Installing or upgrading Storage Mirroring Replicate—Use these instructions to
install or upgrade Storage Mirroring Replicate using the installation wizard.
● Installing Storage Mirroring Replicate automatically—Use these instructions to
install or upgrade Storage Mirroring Replicate using command-line parameters
which allow you to automate the process by running an unattended installation.
● Installing TimeData continuous data protection—If you are installing on a
repository server and will be using TimeData continuous data protection, you will
need to install TimeData after you install Storage Mirroring Replicate. If you
entered a repository server activation code during the Storage Mirroring Replicate
installation, the TimeData installation can be launched directly from the Storage
Mirroring Replicate installation. Otherwise, you will need to start the TimeData
installation manually.
● Upgrading to SQL 2008 Standard—The TimeData installation includes
SQL Server. If you installed from a web download, the SQL Server version is 2008
Express edition. The SQL database is limited to 4 GB in the Express edition. If you
installed from the Storage Mirroring Replicate CD, the SQL Server version is 2008
Standard edition. The SQL database is limited to 524272 TB in the Standard
edition. If you have the Storage Mirroring Replicate CD, you can upgrade a 2008
Express edition to the 2008 Standard edition.
● Installing and configuring Ontrack PowerControls—If you purchased a Storage
Mirroring Replicate Repository with Ontrack PowerControls license, you can install
Ontrack PowerControls on your repository server. If you entered an appropriate
Ontrack PowerControls activation code during the Storage Mirroring Replicate
installation, the Ontrack PowerControls installation can be launched directly from
the Storage Mirroring Replicate installation. Otherwise, you will need to start the
Ontrack PowerControls installation manually.

24 of 195
Installation and upgrade notes
Review the following installation and upgrade notes before beginning your installation or
upgrade.
● Since Storage Mirroring Replicate installs device drivers, it is recommended that
you update your Windows Recovery Disk, before installing or making changes to
your servers. For detailed instructions on creating a recovery disk, see your
Windows reference manuals. Make sure that you select the option to back up the
registry when building the repair disks.
● Because Storage Mirroring Replicate has operating system dependent files, if you
are upgrading your operating system (to a new major version, not a service pack)
and have Storage Mirroring Replicate installed, you must remove Storage
Mirroring Replicate prior to the operating system upgrade. Uninstall Storage
Mirroring Replicate, perform the operating system upgrade, and then reinstall
Storage Mirroring Replicate.
● If you are installing to a drive other than the drive which contains your system
TEMP directory, the Microsoft Windows Installer will still load approximately 100
MB of data to the TEMP directory during the installation. If you do not have enough
disk space on the drive that contains the TEMP directory, you may need to change
where it is located.
● During installation, a file called dtinfo.exe is installed to the Storage Mirroring
Replicate installation directory. This program can be run to collect configuration
data for use when reporting problems to technical support. It gathers Storage
Mirroring Replicate log files; Storage Mirroring Replicate and system registry
settings; network configuration information such as IP, WINS, and DNS addresses;
and other data which may be necessary for customer support to troubleshoot
issues. After running the executable, a zip file is automatically created with the
information gathered.
● Storage Mirroring Replicate 5.2 can interoperate back to version 5.0 but has the
following limitations. The Storage Mirroring Replicate clients can only control the
same or earlier releases. To accommodate rolling upgrades, older sources can
connect to newer targets, but newer sources cannot connect to older targets.
Configurations not listed in the following chart are not supported.

Client Source Target Supported

5.0 5.1 or 5.2 5.1 or 5.2 No

5.1 5.2 5.2 No

5.2 5.0 5.0, 5.1, or 5.2 Yes

25 of 195
 Client Source Target Supported

5.2 5.1 5.0 No

5.2 5.1 5.1 or 5.2 Yes

5.2 5.2 5.0 or 5.1 No

5.2 5.2 5.2 Yes

● When performing a rolling upgrade, update the target server first. After the upgrade
is complete, any sources will automatically reconnect to the target. Upgrade the
source(s) when convenient.

26 of 195
Installing or upgrading Storage Mirroring Replicate
Use these instructions to install Storage Mirroring Replicate or upgrading an existing
Storage Mirroring Replicate installation.
1. Close any open applications.
2. Start the installation program using the appropriate instructions, depending on your
media source.
● CD—Load the Storage Mirroring Replicate CD into the local CD-ROM drive.
If auto-run is enabled, the installation program will start automatically. To
manually start the program, select Start, Run and specify <cd_
drive>:\autorun.exe.
● Web download—Launch the .exe file that you downloaded from the web.
3. When the installation program begins, the Storage Mirroring Setup Launcher
appears allowing you to install software and view documentation for various
applications from HP. The listed applications will depend on which products are
included on the CD or in the web download. To install Storage Mirroring Replicate,
select Storage Mirroring Replicate from the list of products. Under Product
Installs, select Storage Mirroring Replicate.
4. Depending on your version of Windows and the components you have installed,
you may see an initial screen indicating that you should install Microsoft .NET
Framework. If you do not see this screen, your server already has the appropriate
version of Microsoft .NET. You should install Microsoft .NET before installing
Storage Mirroring Replicate. Click Yes to install Microsoft .NET. Click No to
continue without installing .NET.
5. Review and accept the HP license agreement to continue with the installation
program. Click Next to continue.
6. Select the type of installation you would like to perform on this machine.
● Client and Server Components—This options installs both the client and
server components. The server components are required for systems that will
function as a source, repository server, or recovery server. The server
requires an activation code for the service to run. The client does not require
an activation code, but it is required to administer this and other servers
throughout the organization.
● Client Components Only—This option installs only the client components.
The client components do not require an activation code, but are required to
administer servers throughout the organization.
● Server Components Only—This option installs only the server components.
The server components are required for systems that will function as a

27 of 195
 source, repository server, or recovery server. The server requires an
activation code for the service to run.
8. If desired, specify where the Storage Mirroring Replicate files will be installed.
9. Click Next to continue.

If you selected a Client Components Only installation type, continue with

Note:
step 16 below.

10. You will be prompted to enter your activation code information. Your activation
code is a 24-character, alpha-numeric activation code which applies the
appropriate license to your installation. Multiple codes allow you to run multiple HP
products.
● To add a new code to this machine, enter the code and click Add. Repeat
this process if you have additional codes.
● To remove any codes from this machine, highlight the code in the Current
activation codes list and click Remove.
11. When you have added your activation code(s), click Next to continue.
12. Storage Mirroring Replicate uses system memory to store data in queues. Specify
the maximum amount of system memory to be used for the Storage Mirroring
Replicate queues and click Next to continue.

If you set the system memory queue lower, Storage Mirroring Replicate
will use less system memory, but you will queue to disk sooner which may
impact system performance. If you set it higher, Storage Mirroring
Replicate will maximize system performance by not queuing to disk as
Note: soon, but the system may have to swap the memory to disk if the system
memory is not available. In general, the amount of memory Storage
Mirroring Replicate and other applications on the server are configured to
use should be less than the amount of physical memory on the system to
prevent low memory conditions.

13. When the Storage Mirroring Replicate system memory queue is exhausted,
Storage Mirroring Replicate will queue to disk. Specify the size and location of the
disk queue. By default, the disk space is set to Unlimited which will allow the
queue usage to automatically expand whenever the available disk space expands.
14. Click Next to continue.
15. The Storage Mirroring Replicate security information screen appears next. Review
this information and click Next to continue with the installation.
16. If you are satisfied with the selections you have made and are ready to begin
copying the Storage Mirroring Replicate files, click Install.

28 of 195
17. During the installation, you may be prompted to add an exception to the Windows
Firewall for Storage Mirroring Replicate. Click OK to add the port exception. If you
Cancel the port modification, you will have to manually modify your firewall
settings for Storage Mirroring Replicate processing.
18. Depending on the activation code(s) you entered during the installation and if you
selected a Client and Server Components or Server Components Only, you
may see one or two additional installation options after the Storage Mirroring
Replicate files have completed copying. The installation options are for TimeData
continuous data protection and Ontrack PowerControls for Exchange messages,
folders, and mailboxes. If you want to install either of these features, enable the
options and the TimeData and Ontrack PowerControls installations will
automatically start when the Storage Mirroring Replicate installation closes. If both
options are selected, the Ontrack PowerControls installation will run first.
19. Click Finish to exit the installation program.

29 of 195
Installing Storage Mirroring Replicate automatically
The Storage Mirroring Replicate installation program can accept command-line
parameters which allow you to automate the installation or upgrade process by running
an unattended, or silent, installation. The automatic process allows you to pass
parameters through to the installation program instead of entering information manually
during the installation or upgrade.
Since the automated process does not prompt for settings, the settings are manually
defined in a configuration file called DTSetup.ini. By default, DTSetup.ini contains two
sections. The second section can be duplicated as many times as necessary. The first
section, [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 to
specify unique settings for individual servers. You have to modify the heading name
(case-sensitive) to identify the server.
Sample DTSetup.ini

[Config]
DTSETUPTYPE=DTNT
DTACTIVATIONCODE=123456789012345678901234
DOUBLETAKEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
QMEMORYBUFFERMAX=128
DISKQUEUEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
DISKQUEUEMAXSIZE=UNLIMITED
DISKFREESPACEMIN=50
DTSERVICESTARTUP=1
PORT=6320
SET_FWPORT=Y

[Alpha]
DTSETUPTYPE=DTNT
DTACTIVATIONCODE=123456789012345678901234
DOUBLETAKEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
QMEMORYBUFFERMAX=128
DISKQUEUEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
DISKQUEUEMAXSIZE=UNLIMITED
DISKFREESPACEMIN=50
DTSERVICESTARTUP=1
PORT=6320
SET_FWPORT=Y

[Beta]
DTSETUPTYPE=DTNT
DTACTIVATIONCODE=123456789012345678901234

30 of 195
 DOUBLETAKEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
QMEMORYBUFFERMAX=128
DISKQUEUEFOLDER="C:\Program Files\StorageWorks\Storage Mirroring"
DISKQUEUEMAXSIZE=UNLIMITED
DISKFREESPACEMIN=50
DTSERVICESTARTUP=1
PORT=6320
SET_FWPORT=Y

In the sample DTSetup file, the server Alpha would use the parameters defined under
the [Alpha] heading. The server Beta would use the parameters defined under the [Beta]
heading. All other servers would use the configuration under the [Config] section.

Do not leave any parameter blank in the Config or MachineName sections.

Note: Otherwise, a hard-coded default stored in a Storage Mirroring Replicate .dll file
will be used.

Review the following table to understand the different parameters available in

DTSetup.ini.

Parameter Valid Values

● DTNT—Both the Storage Mirroring Replicate server and

client components will be installed. The server
components are required for systems that will function as
a source, repository server, or recovery server. The
server requires an activation code for the service to run.
The client does not require an activation code, but it is
required to administer this and other servers throughout
the organization.
DTSetupType ● DTCO—Only the Storage Mirroring Replicate client
components will be installed. The client components do
not require an activation code, but are required to
administer servers throughout the organization.
● DTSO—Only the Storage Mirroring Replicate server
components will be installed. The server components are
required for systems that will function as a source,
repository server, or recovery server. The server requires
an activation code for the service to run.

A 24 character, alpha-numeric activation code which applies

DTActivationCode
the appropriate license to the server

31 of 195
 Parameter Valid Values

Any valid path specifying the location of the Storage Mirroring

DoubleTakeFolder
Replicate files

Any integer representing the amount of system memory, in MB,

QMemoryBufferMax
to use for memory-based queuing

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

Any integer representing the amount of disk space, in MB, to

use for disk-based queuing or the keyword UNLIMITED which
DiskQueueMaxSize
will allow the queue usage to automatically expand whenever
the available disk space expands

Any integer representing the amount of disk space, in MB, that

DiskFreeSpaceMin
must remain free at all times

● Y or 1—Start the Storage Mirroring service automatically

● N or 0—Do not start the Storage Mirroring service
DTServiceStartup
automatically
This parameter is not applied if your DTSetupType is DTCO.

Any integer between 1024 and 65535 that identifies the

Port
Windows Firewall port used for Storage Mirroring Replicate.

● Y or 1—Set the Windows Firewall port for Storage

Mirroring Replicate
Set_FWPORT
● N or 0—Do not set the Windows Firewall port for Storage
Mirroring Replicate

You must have Microsoft .NET installed on the server before starting the
automatic installation.
If you are using Windows 2008, but you are not using the built-in administrator
account, Windows 2008 User Access Control will prompt you to confirm you
want to install Storage Mirroring Replicate. To work around this issue, use the
Note: built-in administrator account when you are installing to each server. You may
also disable User Access Control if that is acceptable for your environment.
If you are installing to a repository server and will be using TimeData
continuous data protection, the automatic installation will not automatically
launch the TimeData installation. See Installing TimeData continuous data
protection for instructions.

Installing or upgrading automatically to a local machine

32 of 195
 1. Create a temporary directory on the server. For example, create c:\dtinstall.
2. On the CD, locate the files in a subdirectory under \setup\hpsw that is appropriate
for your architecture, either i386, x64, or IA64. Copy the files from that subdirectory
to the temporary directory.
3. From a command prompt, remove the read-only attributes from the files in the
temporary directory by using the command attrib *.* -r.
4. Make a backup copy of the default DTSetup.ini file in the temporary directory.
5. Edit DTSetup.ini as needed using the values described in the previous table.
6. Determine the exact file name of your setup file by using the command dir setup*.*
from the temporary directory command prompt. Depending on how you received
your software (CD or web), your setup file name will be named setup.exe or setup_
xxxx.exe where xxxx is four numbers that specify the build number. For example,
your setup file might be called setup.exe or setup_1352.exe.
7. Run one of the following case-sensitive commands from the temporary directory,
depending on if you have setup.exe or setup_xxxx.exe where xxxx is a four digit
build number.
setup /s /v"DTSETUPINI=\"c:\dtinstall\DTSetup.ini\" /qn"
setup_xxxx /s /v"DTSETUPINI=\"c:\dtinstall\DTSetup.ini\" /qn"

The command must be run from the directory where the temporary files are
located as well as specifying that directory for the .ini file.
Note:
Spacing is critical with this command. A space should precede /s, /v, and /qn
but should not appear anywhere else for the command to work correctly.

Installing or upgrading automatically to a remote machine

1. Create a temporary directory on the primary site server. For example, create
z:\dtinstall.
2. Share the temporary folder.
3. On the CD, locate the files in a subdirectory under \setup\hpsw that is appropriate
for your architecture, either i386, x64, or IA64. Copy the files from that subdirectory
to the temporary directory.
4. From a command prompt, remove the read-only attributes from the files in the
temporary directory by using the command attrib *.* -r.
5. Make a backup copy of the default DTSetup.ini file in the shared folder.
6. Edit DTSetup.ini as needed using the values described in the previous tables.
7. From each server where you want to install Storage Mirroring Replicate, map a
drive to the temporary directory that you created in step 1. For example, you might
map your m: drive to the share.

33 of 195
 8. Determine the exact file name of your setup file by using the command dir setup*.*
from the mapped drive command prompt. Depending on how you received your
software (CD or web), your setup file name will be named setup.exe or setup_
xxxx.exe where xxxx is four numbers that specfy the build number. For example,
your setup file might be called setup.exe or setup_1352.exe.
9. Run one of the following case-sensitive commands from the mapped drive,
depending on if you have setup.exe or setup_xxxx.exe where xxxx is a four digit
build number.
setup /s /v"DTSETUPINI=\"m:\DTSetup.ini\" /qn"
setup_xxxx /s /v"DTSETUPINI=\"m:\DTSetup.ini\" /qn"

The command must be run from the shared folder as well as specifying that
directory for the .ini file.
Note: Substitute your mapped drive for m:\.
Spacing is critical with this command. A space should precede /s, /v, and /qn
but should not appear anywhere else for the command to work correctly.

C:\>net use m: \\server_name\share

The command completed successfully
C:\>M:
M:\>setup_1352 /s /v"DTSETUPINI=\"m:\DTSetup.ini\" /qn"

34 of 195
Installing TimeData continuous data protection
1. Depending on your Storage Mirroring Replicate installation selections, the
TimeData installation may automatically launch immediately following the Storage
Mirroring Replicate installation. If it did not start automatically or if you are installing
it separately from the Storage Mirroring Replicate installation, start the TimeData
installation program using the appropriate instructions, depending on your media
source.
● CD—Load the Storage Mirroring Replicate CD into the local CD-ROM drive.
If auto-run is enabled, the installation program will start automatically. To
manually start the program, select Start, Run and specify <cd_
drive>:\setup\TimeData\TimeData.exe.
● Web download—Unzip the .exe file that you downloaded from the web to a
temporary location and select Start, Run and specify <temporary_unzip_
location>\setup\TimeData\TimeData.exe.
2. At the Welcome screen, click Next.
3. Review and accept the license agreement to continue with the installation
program. Click Next to continue.
4. Specify your User Name and Organization and click Next to continue.
5. Select the directory where you want to install TimeData and click Next to continue.

For best results, you should separate the various TimeData components
Note: that you will be prompted to install (TimeData Event log, TimeData drive
letter, SQL Server, and TimeData Event cache) on different drives.

6. Specify the location to store the TimeData Event log. For best results, do not select
a drive containing Windows system files.
7. Select the drive letter to indicate where the TimeData continuous data protection
historical files will be stored. A TS_Drive network share will be created on the
drive. The drive will be accessible through Windows Explorer and other
applications.
8. Click Next to continue.
9. Select the directory where you want to install the SQL Server databases used with
TimeData and click Next to continue.
10. Specify the location to store the TimeData Event cache, which temporarily stores
data until it can be stored in the TimeData Event log.
11. Specify the maximum size of the TimeData Event cache. By default, the maximum
size is 20 GB. Make sure you have sufficient disk space in the selected location for
the Event cache.

35 of 195
 12. Click Next to continue.
13. At the Ready screen, click Install.
14. During the installation, you may be prompted to add an exception to the Windows
Firewall for TimeData. Click OK to add the port exception. If you Cancel the port
modification, you will have to manually modify your firewall settings for TimeData
processing.
15. Click Finish to exit the installation program. If prompted, reboot your computer for
the installation changes to complete.

Upgrading to SQL Server 2008 Standard

The TimeData installation includes SQL Server. If you installed from a web download,
the SQL Server version is 2008 Express edition. The SQL database is limited to 4 GB in
the Express edition. If you installed from the Storage Mirroring Replicate CD, the SQL
Server version is 2008 Standard edition. The SQL database is limited to 524272 TB in
the Standard edition. If you have the Storage Mirroring Replicate CD, you can upgrade a
2008 Express edition to the 2008 Standard edition.
1. Load the Storage Mirroring Replicate CD into the local CD-ROM drive. If auto-run
is enabled, the Setup Launcher will start automatically. Close the Setup Launcher
when it opens.
2. Locate and run the file \setup\TimeData\SQLServer2008Upgrade.exe on the CD.
3. At the Welcome screen, click Next.
4. Review and accept the license agreement to continue with the installation
program. Click Next to continue.
5. Specify your User Name and Organization and click Next to continue.
6. At the Ready screen, click Install.
7. When the upgrade has completed, click Finish to exit the installation program.

36 of 195
Installing and configuring Ontrack PowerControls
1. Depending on your Storage Mirroring Replicate installation selections, the Ontrack
PowerControls installation may automatically launch immediately following the
TimeData installation. If it did not start automatically or if you are installing it
separately from the Storage Mirroring Replicate installation, start the Ontrack
PowerControls installation program using the appropriate instructions, depending
on your media source.
● CD—Load the Storage Mirroring Replicate CD into the local CD-ROM drive.
If auto-run is enabled, the installation program will start automatically. To
manually start the program, select Start, Run and specify <cd_
drive>:\setup\Ontrack PowerControls\Ontrack PowerControls.exe.
● Web download—Unzip the .exe file that you downloaded from the web to a
temporary location and select Start, Run and specify <temporary_unzip_
location>\setup\Ontrack PowerControls\Ontrack PowerControls.exe.
2. At the Welcome screen, click Next.
3. Review and accept the license agreement by clicking Yes.
4. Specify your User Name and Company Name and click Next to continue.
5. Select the directory where you want to install Ontrack PowerControls and click
Next to begin the installation.
6. Click Finish to exit the installation program.
7. After the installation is complete, you need to configure Ontrack PowerControls to
use your repository server. Select Start, Programs, Kroll Ontrack, Ontrack
PowerControls for Storage Mirroring, Ontrack PowerControls for Exchange.
8. Cancel the Data Wizard when it appears.
9. Select Help, About, and click License Info.
10. Specify the name of your Storage Mirroring Replicate repository server. You can
also click the browse button (the button with ... on it) to select the name from a
network drill-down list.
11. Click Close to save the server information.
12. Click OK to close the About box.

37 of 195
Managing server licenses
From the Replication Console, you can manage your server activation codes. The
activation code is the Storage Mirroring Replicate license which is required on every
Storage Mirroring Replicate server. The activation code is a 24 character, alpha-numeric
code. You can change your activation code without reinstalling, if your license changes.
There are different licenses available.
● Evaluation—An evaluation license has an expiration date built into the activation
code. When the license expires, the software will no longer function. The same
evaluation licenses can be used on multiple machines on a network.
● Single—A single license is available on a per-machine basis. Each server is
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 on a network.
● Site—A site license is available to register every machine with the same license.
This license is designed to be used on multiple servers on a network.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your Storage Mirroring Replicate server in the left pane of the
Replication Console to log on to it.
3. Right-click the server name and select Properties.
4. Select the Licensing tab.

38 of 195
5. Enter an activation code and click Add. Repeat for each activation code.
6. If you need to remove a code from the server, highlight it in the list and click
Remove.
7. Click OK to save the settings.

39 of 195
Storage Mirroring Replicate console
The Storage Mirroring Replicate console is the user interface that manages, monitors,
and controls your backup solutions. To open the console, select Start, Programs,
Storage Mirroring, Storage Mirroring Replicate, Storage Mirroring Replicate
Console.
On the left pane of the console are static navigation buttons which initiate workflows and
display monitoring pages. In essence, these navigation buttons control what is displayed
in the main window.
Each time you open the Storage Mirroring Replicate console, it will automatically open
to the Monitor page. Any existing jobs will be displayed. If there are no existing jobs, the
display will be blank.

The Storage Mirroring Replicate console requires a 1024x768 minimum screen

Note:
resolution.

40 of 195
Importing a job
If you need to manage or monitor a job created on another console or created by another
user, you can import it into your console session using the following instructions.
1. From the Monitor page, select Import jobs on the toolbar.
2. Identify the import server. This is the repository server that contains the source
images that you are protecting.

● Server—To import a protection job (source to repository server), specify the

name of the repository server. To import a recovery job (repository server to
recovery server), specify the name of the recovery server. You can also click
Browse to select the name from Active Directory or from a network drill-down
list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the repository server.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
3. Click Next to continue.
4. Mark those jobs that you want to import into the console with a checkmark.

41 of 195
 5. Click Finish to complete the import.
The Monitor page will automatically appear with the imported job.

42 of 195
Clearing console security credentials
By default, the Storage Mirroring Replicate console caches security credentials. Also by
default, the cache is saved when you close the console, allowing you to reuse the
credentials when you reuse the console. This setting is controlled by the Tools, Save
credentials cache menu option. When the option is selected with a checkmark, the
security credentials cache will be saved. When the option is disabled and no checkmark
is displayed, the security credentials cache will be deleted when the console is closed.
At any time, you can clear the security credentials cache by selecting Tools, Clear
credentials cache.

43 of 195
Source protection
When protecting a source, you can protect the entire server, including the system state,
which is the server's operating system and configured applications, or you can protect
only specific data on the server. Use the instructions Protecting your source for both full-
server and data protection. At the end of the protection workflow, you will have an
opportunity to configure optional protection settings for your protection job.

44 of 195
Protecting your source
Use the following instructions to set up your source protection.
1. Click Protect from the left navigation pane.
2. Identify the source server that you want to protect.

● Server—Specify the name of the source server. You can also click Browse
to select the name from Active Directory or from a network drill-down list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the source.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
3. Click Next to continue.
4. Identify the repository server that will store the source data or the image of the
entire source.

45 of 195
 ● Server—Specify the name of the repository server. You can also click
Browse to select the name from Active Directory or from a network drill-down
list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the repository server.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
5. Click Next to continue.
6. Select what you want to protect on the source.

46 of 195
 ● Protect system state—This option protects the entire source, including the
system state, which is the server's operating system and configured
applications. If you select this option, you will be able to recover the entire
source server.
● Protect selected data only—This option protects only the data you select. If
you select this option, you will only be able to recover the data you select but
not the entire source server.
7. By default, Storage Mirroring Replicate selects all applicable source files based on
your system state or selected data only choice. By default for system state
protection, some files are included and excluded depending on if they can be used
during a recovery. For example, the boot volume cannot be excluded because that

47 of 195
 is where the system state information is stored. If desired, you can exclude other
files that you do not want to protect, but be careful when excluding data. Excluded
volumes, folders, and/or files may compromise the integrity of your applications.
Volumes, folders, and files that are marked with a checkmark are included. If there
is no checkmark, the item is excluded. Expand and collapse the directory tree and
click on an item to add or remove a checkmark.

The Select all and Deselect all buttons allow you to quickly select or
deselect all data on your server based on your system state or selected
Note: data only choice. These buttons will do not change what is selected for
the system state, which is defined by Storage Mirroring Replicate and
cannot be modified.

8. Once you have configured the data to protect, click Next to continue.
9. A point-in-time strategy gives you additional recovery options. In addition to being
able to recover from live data, you can recover to a single point in time using a
snapshot or to any point in time using TimeData continuous data protection.

48 of 195
 ● Enable scheduled snapshots—By default, periodic snapshots are
disabled. If desired, enable snapshots by selecting this option. Because
Storage Mirroring Replicate uses the Microsoft Volume Shadow Copy
service to create snapshots, your source and repository server must be using
the NTFS file system. If you are using a FAT file system, the FAT volumes
will not be included in the snapshot set, and when the snapshots are
reverted, the FAT volume will not be time-consistent with the NTFS volumes.
● Take snapshots on the following interval—By default, Storage Mirroring
Replicate will take a snapshot of the repository server data every hour. If
desired, increase or decrease the interval between snapshots.
● Begin immediately—If you want to start taking snapshots immediately after
the Storage Mirroring Replicate job is established, select this option.
● Begin at—If you want to start taking snapshots at a specific data and time,
select this option and specify the date and time parameters.
● Enable Continuous Data Protection—By default, continuous data
protection is disabled. If desired, enable continuous data protection by
selecting this option. If you did not install TimeData, you will not have this
option available to select. The repository server must be using the NTFS file
system. If you are using a FAT file system, the FAT volumes will not be
included in the continuous data protection and will be unavailable for point-
in-time recovery.
● Keep changes for—By default, Storage Mirroring Replicate will capture and
catalog all changes made to all files and folders for seven days. The
recommended retention is seven days. If desired, increase or decrease the
number of days to protect data continuously. If you increase the number of
days, kkeep in mind space limitations on the repository server. Continuous
data protection is a per repository server setting. Therefore, the length of time
you specify will apply to all jobs that use this repository server.
9. Click Next to continue.
10. Select a location on the repository server to store the location of the source’s data
or image. The location you specify for Path prefix will automatically have the
source server name appended to it, in order to distinguish the data or image from
other data or images.

49 of 195
11. Specify if you want to delete orphan files. An orphan file is a file that exists in the
repository server’s copy of the data or source image, but it does not exist on the
source. An orphan file can be created when a job is stopped and file is deleted on
the source. Because of the stopped job, the delete operation does not get
replicated to the repository server. Orphan files may also exist if files were
manually copied into the repository server's copy of the data or source image.
12. Click Next to continue.
13. At the Protection Summary page, you can review the choices you have made
and you can also set optional data transmission and e-mail notification settings. If
you need to make any changes to the selections you made, click Back to return to
the previous pages. If you want to configure the optional settings, click Configure.
14. Once you have completed your configuration, click Finish to establish your source
protection. The Monitor page will automatically appear with the new job.

50 of 195
Optional protection settings
When you are creating a protection job, you will have an opportunity to configure
optional job settings when you get to the Protection summary workflow page. If you
want to configure optional settings, click Configure next to the options section.
● Compressing data for transmission for a protection job
● Limiting bandwidth for a protection job
● Routing transmission for a protection job
● E-mailing repository server event messages

Compressing data for transmission for a protection job

To help reduce the amount of bandwidth needed to transmit Storage Mirroring Replicate
data, compression allows you to compress data prior to transmitting it across the
network. In a WAN environment this provides optimal use of your network resources. If
compression is enabled, the data is compressed before it is transmitted from the source.
When the repository server receives the compressed data, it decompresses it and then
writes it to disk.

By default, compression is set to None, which means it is disabled. The compression

levels can be set at Minimum, Medium, or Maximum. Each level requires more
overhead than the previous level of compression. If you notice an impact on performance
while compression is enabled in your environment, either adjust to a lower level of
compression or leave compression disabled.

Limiting bandwidth for a protection job

Bandwidth limitations are available to restrict the amount of network bandwidth used for
Storage Mirroring Replicate data transmissions. When a bandwidth limit is specified,
Storage Mirroring Replicate never exceeds that allotted amount. The bandwidth not in
use by Storage Mirroring Replicate is available for all other network traffic.

51 of 195
 ● Do not limit bandwidth—Storage Mirroring Replicate will transmit data using
100% bandwidth availability.
● Place this limit on the bandwidth—Enter a value in kilobytes per second to limit
data transmission. This is the maximum amount of data that will be transmitted per
second.

Routing transmission for a protection job

By default, Storage Mirroring Replicate will select a default route for transmissions. The
default route is the first connection listed in the NIC binding order on the repository
server. If you want to select a different route for Storage Mirroring Replicate
transmissions, you can select a different IP address on the repository server using the
Storage Mirroring Replicate Route option, or you can reorder the bindings on the
repository server (Network Connections, Advanced, Advanced Settings, Adapters
and Bindings).

E-mailing repository server event messages

E-mail notification sends specific Storage Mirroring Replicate events to user-defined e-
mail addresses. If you want to use e-mail notification, you will need to identify who will
receive the messages, what messages they will receive, and your e-mail server
configuration.

The e-mail notification settings are for the repository server. If you want to
Note: configure e-mail notification for your source server, see E-mailing source event
messages.

● Recipients—Specify the e-mail address that each Storage Mirroring Replicate e-

mail message should be sent to and click Add New. The e-mail address will be

52 of 195
 inserted into the list of addresses. Each address is limited to 256 characters, and
you can add up to 256 e-mail addresses. If you want to remove an address from
the list, highlight the address and click Remove. If you want to remove all of the
addresses from the list, click Clear.

● Notifications—Specify which events that you want to be sent via e-mail. You can
select Error, Warning, and/or Information.

● Server Setup—Specify your e-mail server configuration.

● Mail Server—Specify the name of your SMTP mail server.

● Log on to SMTP server—If your SMTP server requires a login, enable this
option and specify a User name and Password.

TimeData events do not support authenticated SMTP notification

Note: methods. Check the TimeData log files for TimeData events if you are
using authenticated SMTP.

53 of 195
 ● User name—Specify a user account with privileges to send e-mail
messages from your SMTP server.
● Password—Specify the password associated with the User Name you
entered.
● From Address—Specify the e-mail address that you want to appear in the
From field of each Storage Mirroring Replicate e-mail message. The address
is limited to 256 characters.
● Subject prefix—Specify default text that will appear on every Storage
Mirroring Replicate e-mail message. This will help distinguish Storage
Mirroring Replicate messages from other messages.
● Add event description to prefix—Specify if you want the description of the
event appended to the Subject prefix. The subject line is limited to 150
characters, so only the first 150 characters of the combined Subject prefix
and event description will be displayed.

Make sure you configure your e-mail client so that the Storage Mirroring
Note: Replicate e-mail notification messages do not get blocked by a spam filter
or sent to a junk mail folder.

54 of 195
Data on the repository server
The images that are stored on the repository server may be in various states. There is
live data, snapshot data, and TimeData historical data. There may be times when you
want to view or retrieve data from the repository server without recovering an entire
server or all of the data you have protected.
● Live data—The live data can be easily be viewed and retrieved at any time on the
repository server using standard file system tools like Windows Explorer. Be
careful not to modify any of the data on the repository server, so that if the data is
needed for a recovery, it will be the same as what is on the source.
● Snapshot and TimeData historical data—Because the snapshot data and
TimeData historical data is not in client accessible format, you need to use Storage
Mirroring Replicate to mount a snapshot or a TimeData point in time so that it can
be accessed. Once mounted, you can retrieve files or folders as needed using
standard file system tools like Windows Explorer.
● Exchange data—If you have installed Ontrack PowerControls, you can open a
Microsoft Exchange storage file (.edb file) for viewing or retrieving individual
messages or mailboxes. Ontrack PowerControls can be used on the live data, a
snapshot, or TimeData historical data.

55 of 195
Viewing and retrieving data from snapshots or from a
TimeData point in time
1. Click View Point In Time from the left navigation pane.
2. Identify the repository server that is storing the source image(s).

● Server—Specify the name of the repository server. You can also click
Browse to select the name from Active Directory or from a network drill-down
list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the repository server.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
3. Click Next to continue.
4. Select the image that you want to view and specify the point-in-time strategy.

56 of 195
 ● Available images—Select the image of the source that contains the data you
want to recover. If the image is not displayed, click Browse to look for the
location of the server image.
● Snapshot—Select this option and choose a snapshot from the list to mount
the data stored in that snapshot. If you did not enable snapshots or there
were no snapshots taken on the repository server, there will be no snapshots
in the list.
● Specific time—Select this option and choose a specific date and time to
mount the data from that point in time. The table below the date and time
fields allows you to confirm that the Storage Mirroring Replicate data is valid
for the point in time you are selecting. If you did not enable continuous data
protection when you configured protection or if the TimeData initialization
has not completed, this option will not be available.
5. Click Finish. If you are completing this task from the repository server, the data
from the image and point-in-time strategy you selected will be mounted
automatically and a Windows Explorer window will open to the mount point. If you
are not completing this task from the repository server, the data from the image and

57 of 195
 point-in-time strategy you selected will still be mounted automatically, but you will
see a pop-up dialog box indicating where you can find the mount point on the
repository server.
6. From Windows Explorer, retrieve files or folders as needed. If the files or folders
you need are not in the snapshot or TimeData point in time, you can repeat the
process multiple times to mount different snapshots or TimeData points in time.

58 of 195
Viewing and retrieving Exchange data
1. Start Ontrack PowerControls by selecting Start, Programs, Kroll Ontrack,
Ontrack PowerControls for Storage Mirroring, Ontrack PowerControls for
Exchange.
2. The Data Wizard will automatically open the first time Ontrack PowerControls is
opened. If it is not opened, select File, Use Wizard.
3. Specify the storage files from your repository server that you want to browse. If you
want to browse a snapshot or TimeData historical data, make sure you mount the
snapshot or TimeData historical data first.
4. Click Next to continue.
5. Specify where you want to copy the Exchange data.
6. Click Next to continue.
7. After Ontrack PowerControls has scanned the files, click Finish.
For more detailed information on using Ontrack PowerControls and its other features,
press F1 from within Ontrack PowerControls to open the online help.

59 of 195
Recovery
In some cases, you can recover data or an entire server back to your original source.
Additionally, you can use the source data or the image of a entire source, stored on the
repository server, to quickly and easily create a new source server. Your new source can
be an existing physical or virtual machine, or Storage Mirroring Replicate can
automatically provision (create) a virtual machine during the recovery process.
When your recovery server is a not your original source, Storage Mirroring Replicate
must be installed on the recovery server (or on the existing virtual machine on an
ESX server) before you start the recovery process. However, you do not need to install
Storage Mirroring Replicate from a CD or web download or have a valid activation code
for the recovery server. Storage Mirroring Replicate has a built-in installation feature that
installs a valid, unactivated copy of Storage Mirroring Replicate on the recovery server.
At any time before the recovery, you can use this built-in installation feature to push a
copy of Storage Mirroring Replicate to your recovery server. If your recovery server
already has a previously installed, properly licensed and activated copy of Storage
Mirroring Replicate, you can skip the recovery installation and go directly to the recovery
process. See Installing on the recovery server for the steps to install Storage Mirroring
Replicate on your recovery server.
Before you begin the recovery process, understand that the flow of data is going to
change. When you were protecting your source, the data was being transmitted from the
source to the repository server. During recovery, the data will be transmitted from the
repository server to the recovery server. This means your repository server is now your
source, and your recovery server is your target.
You have the following recovery options.
● Recovering an entire server to an existing physical or virtual machine
● Recovering an entire server to an automatically provisioned virtual machine on
VMware ESX
● Recovering an entire server to an automatically provisioned virtual machine on
Hyper-V
● Recovering data to an existing physical or virtual machine
● Optional recovery settings

60 of 195
Installing Storage Mirroring Replicate on the recovery
server
1. Select Tools, Prepare Recovery Server.
2. Specify the recovery server information.

● Server—Specify the name of the recovery server.

● User name—Specify a user that has WMI and file share access on the
server.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
3. Click Install and monitor the status of the various installation tasks.

Do not use the copy of Storage Mirroring Replicate that was pushed to
your recovery server outside of the recovery process because it will
Note:
automatically activate the software. Once activated, it will automatically
deactivate after five days.

61 of 195
Recovering an entire server to an existing physical or
virtual machine
1. There are two ways to begin the recovery process.
● Click Recover from the left navigation pane and identify the repository server
that contains your source data that you want to recover. Click Next to
continue.
● Highlight the data protection job on the Monitor page and select Recover
from the toolbar. This automatically identifies the repository server that
contains the source data that you want to recover.
2. Select the image of the source that you want to recover and the point-in-time
strategy.

● Available images—Select the image of the source that contains the data you
want to recover. If the image is not displayed, click Browse to look for the
location of the server image.

62 of 195
 ● Live data—Select this option to recover to the live data that is currently
stored on the repository server.
● Snapshot—Select this option and choose a snapshot from the list to recover
to the data stored in that snapshot. If you did not enable snapshots or there
were no snapshots taken on the repository server, there will be no snapshots
in the list.
● Specific time—Select this option and choose a specific date and time to
recover the data from that point in time. The table below the date and time
fields allows you to confirm that the Storage Mirroring Replicate data is valid
for the point in time you are selecting. If you did not enable continuous data
protection when you configured protection or if the TimeData initialization
has not completed, this option will not be available.
3. Click Next to continue.
4. Select the recovery server. If you used the Storage Mirroring Replicate built-in
installation to push a copy of Storage Mirroring Replicate to the recovery server,
that copy will automatically be activated when you select it as a recovery server.
The copy will automatically deactivate after five days.

● Provision a new virtual machine for this recovery—Do not enable this
option. This setting is only if you are recovering to an automatically
provisioned virtual machine.
● Server—Specify the name of the recovery server. You can also click Browse
to select the name from Active Directory or from a network drill-down list. You
can select your repository server as the recovery server, but keep in mind that
the repository server role and any other source images will be lost.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the recovery server. If your original source was the only

63 of 195
 domain controller in your network, you must specify a local account in the
local administrators group.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
5. Click Next to continue.
6. By default, Storage Mirroring Replicate will Recover the entire server. If you only
want to recover selected data, select Recover selected data only. In either case,
you can, if desired, exclude files that you do not want to recover, but be careful
when excluding data. Excluded volumes, folders, and/or files may compromise the
integrity of your applications.

Volumes, folders, and files that are marked with a checkmark are included. If there
is no checkmark, the item is excluded. Expand and collapse the directory tree and
click on an item to add or remove a checkmark. Once you have configured the data
to recover, click Next to continue.

The Select all and Deselect all buttons allow you to quickly select or
deselect all data on your server based on your system state or selected
Note: data only choice. These buttons will do not change what is selected for
the system state, which is defined by Storage Mirroring Replicate and
cannot be modified.

7. Specify if your recovery server is in a LAN or WAN environment with respect to

your original source.

64 of 195
 ● LAN recovery—If your recovery server is on a LAN with your original
source, the original source name and the IP address(es) will be applied to
the recovery server. Specify which network adapters on the recovery server
that you want to take over for the network adapters on the original source.
● WAN recovery—If your recovery server is located across a WAN from your
original source, the original source name will be applied to the recovery
server, but the IP address(es) of the original source will not be used. Instead,
the IP address(es) of the recovery server will be used. If desired, you can
select to Update DNS servers, which will allow you to specify how to
resolve server names and IP addresses. If you do not select Update DNS
Servers, you must manually modify DNS after the recovery is complete.
8. Click Next to continue.
9. If you selected to update your DNS servers for a WAN recovery type, specify your
DNS update options.
● DNS Domains—Click Add and specify the name of your DNS Domain.
Repeat this for each DNS domain. If you want to remove a domain in the list,
highlight the name and click Remove.
● User name—Highlight a DNS domain and specify a user account that has
privileges to update DNS.

65 of 195
 ● Password—Specify the password associated with the user account you
entered.
● DNS Servers—Click Add and specify the IP address of a DNS server in the
DNS domain. Repeat this for each DNS server in the DNS domain. If you
want to remove a server from the list, highlight the address and click Remove
.
● IP addresses—For each IP address on the source, select an IP address on
the recovery server that will take over for that source IP address.
10. Once you have your DNS updates configured, click Test DNS to determine if your
DNS updates will be successful.
11. Click Next to continue.
12. Specify your recovery shutdown options.

● Wait for user intervention before recovery—Specify if you want to pause

the recovery process after the original source image has been mirrored to the
recovery server, which allows you time to coordinate any other tasks. If you
do not pause the recovery, the original source system state will be processed
on the recovery server immediately after the mirror is complete. (The recovery
server will automatically reboot after the system state processing is
completed.)
● Shut down the source server—Specify if you want to shutdown the source
server before the original source system state is processed on the recovery
server, which avoids identity conflicts on the network. The shutdown will
occur after the original source image is mirrored to the recovery server but
before the original source system state is applied to the recovery server. This
option is not available if the recovery server is the original source.

66 of 195
 ● Original Protection Job—Specify what to do with the original protection job
if the original source is still online. If the original source is not running, these
options will be discarded because they cannot be performed. These options
are not available if the recovery server is the original source or the repository
server.
● Delete the original protection job—The original protection job is
stopped and then deleted.
● Stop the original protection job—The original protection job is
stopped but is not deleted. It can be restarted after the recovery.
● Leave the original protection job running—The original protection
job is not stopped or deleted. Keep in mind with this option that the data
on the recovery server could become inconsistent or corrupted because
the original source protection job could be transmitting data to the
repository server and that data might get transmitted to the recovery
server, depending on the progress of the recovery process .
13. Click Next to continue.
14. At this point, Storage Mirroring Replicate validates that your recovery server is
compatible to become your original source. Errors are designated by a red circle
with a white X. (A question mark icon is an unknown error.) Warnings are
designated by a yellow triangle with a black exclamation point. A successful
validation is designated by a green circle with a white checkmark. You must
correct any errors before you can start the recovery. You must revalidate the
selected server until the validation check passes without errors. Once the
validation is successful, click Next to continue.
15. At the Recovery summary page, you can review the choices you have made and
you can also set optional data transmission and e-mail notification settings. If you
need to make any changes to the selections you made, click Back to return to the
previous pages. If you want to configure optional settings, click Configure. Once
you have completed your configuration, click Finish to start the recovery.
16. Monitor the progress of the recovery mirror on the Monitor page.
17. When the recovery mirror has completed, the recovery server will automatically
reboot to complete the recovery process. If you specified to pause the recovery
before applying the system state, when the mirror is complete, the Activity will
change to Protected. Use this time to complete any necessary tasks. When you
are ready to complete the recovery, click Recover on the Monitor page toolbar to
complete the recovery process. Once the recovery server has been rebooted, it will
become the original source server.

Because the Windows product activation is dependent on hardware, you

Note may need to reactivate your Windows registration after recovery. Follow
the on-screen prompts to complete the reactivation.

67 of 195
Recovering an entire server to an automatically
provisioned virtual machine on VMware ESX
If you want Storage Mirroring Replicate to create a virtual machine on VMware
ESX during the recovery process, you must have a VMware ESX host machine with an
existing virtual machine. See Recovery server requirements for details on the
requirements for the ESX machine and the existing virtual machine. If your environment
does not meet those requirements, you will have to recover to an existing physical or
virtual machine.
The existing virtual machine used during the provisioning process is used to as an
intermediary during the recovery process to create the new virtual server that, once
online, will have the identity, data, and system state of the original source. The existing
virtual must have both Windows and Storage Mirroring Replicate installed and licensed
before you can start the recovery.
Tasks performed by the existing virtual machine during the recovery process
1. Create a new virtual machine
2. Add the disk(s) for that virtual machine to its own machine
3. Mount the disk(s)
4. Apply the incoming mirror data (the original source data and system state
information) from the repository server to the mounted disk(s)
5. Unmount the disk(s)
6. Remove the disk(s) from its own machine
7. Start the new virtual machine
Once the new virtual machine is online, it will have the identity, data, and system state of
the original source. Since the existing virtual machine maintains its own identity, it can
be reused for additional recoveries.
Recovery steps
1. There are two ways to begin the recovery process.
● Click Recover from the left navigation pane and identify the repository server
that contains your source data that you want to recover. Click Next to
continue.
● Highlight the data protection job on the Monitor page and select Recover
from the toolbar. This automatically identifies the repository server that
contains the source data that you want to recover.
2. Select the image of the source that you want to recover and the point-in-time
strategy.

68 of 195
● Available images—Select the image of the source that contains the data you
want to recover. If the image is not displayed, click Browse to look for the
location of the server image.
● Live data—Select this option to recover to the live data that is currently
stored on the repository server.
● Snapshot—Select this option and choose a snapshot from the list to recover
to the data stored in that snapshot. If you did not enable snapshots or there
were no snapshots taken on the repository server, there will be no snapshots
in the list.
● Specific time—Select this option and choose a specific date and time to
recover the data from that point in time. The table below the date and time
fields allows you to confirm that the Storage Mirroring Replicate data is valid
for the point in time you are selecting. If you did not enable continuous data
protection when you configured protection or if the TimeData initialization
has not completed, this option will not be available.

69 of 195
3. Click Next to continue.
4. Select the recovery server. This is the ESX server that will host the virtual machine
that, after the recovery, will become your new source.

● Provision a new virtual machine for this recovery—Enable this option to

recover to an automatically provisioned virtual machine hosted on an ESX
server.
● Server—Specify the name of the ESX server. You can also click Browse to
select the name from Active Directory or from a network drill-down list.
● User name—Specify the root user or another user that has the administrator
role on the VMware ESX server.
● Password—Specify the password associated with the User name you
entered.
● Domain—This option is not necessary for an ESX server.
5. Click Next to continue.
6. Because you are creating a new virtual machine, you must Recover the entire
server so that the system state from the original source can be used to create the
new virtual. You can exclude volumes that you protected but do not want to
recover, but be careful when excluding data. Excluded volumes may compromise
the integrity of your applications. Volumes marked with a checkmark are included.
If there is no checkmark, the item is excluded.

70 of 195
 7. Click Next to continue.
8. Specify the volumes to create on the new virtual machine.

● Selected Data—This displays the amount of data, in gigabytes, currently on

the source volume.
● Source Size—This displays the size, in gigabytes, of the volume on the
source.
● Provisioned Volume—Specify the size, in gigabytes, of the volume to be
created on the new virtual.
9. Click Next to continue.
10. Choose a datastore on the recovery server to store the protected data and system
state information that will be incoming from the repository server. You can only
select a datastore that has enough free space available. The amount of necessary
disk space is noted at the bottom of the page.

71 of 195
 If the size of the datastore is identical to the size of the disk on original source
and there is less than 20 MB of free space on that original source, you may run
Note: out of disk space on the datastore due to differences in how the virtual disk
block size is formatted. In this case, make sure that your datastore has at least
20 MB more disk space than the size of the disk on the original source.

11. Click Next to continue.

12. Choose the Virtual Recovery Appliance, which is your existing virtual machine,
that will be used to create the new virtual machine. The existing virtual machine
must have both Windows and Storage Mirroring Replicate installed and licensed
on it.

● Server—Specify the name of the existing virtual machine on the ESX server.
The drop-down list will only display virtual machines that are running and
have an operating system capable of performing a recovery.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the existing virtual machine. The user must also be a
member of the local administrators group. If your original source was the only
domain controller in your network, the user must be a local account in the
local administrators group.
● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
● VMware Tools—Any servers from the Server list that do not have the latest
VMware tools installed will be listed.

72 of 195
13. Click Next to continue.
14. Configure the new virtual machine that will be created and will become the source
after the recovery.

● VMware Console display name—By default, source name_VM will be used

to create the new virtual machine display name. If desired, you can modify
the name.
● Map replica virtual network IP to target networks—You will need to
identify how you want to handle the network mapping. The Replica VM
Network IP lists the IP addresses contained in the image of the original
source. Map each one to a Target Network, which is a virtual network on the
ESX server.
● Number of processors—Specify how many processors to configure on the
virtual machine. The number of processors from the original source image is
displayed.
● Amount of memory—Specify the amount of memory to configure on the
virtual machine. The amount of memory from the original source image is
displayed.
15. Click Next to continue.
16. Specify your recovery shutdown options.

73 of 195
 ● Wait for user intervention before recovery—Specify if you want to pause
the recovery process after the original source image has been mirrored to the
Virtual Recovery Appliance (the existing virtual machine), which allows you
time to coordinate any other tasks. If you do not pause the recovery, after the
mirror the Virtual Recovery Appliance will immediately unmount the disk(s),
remove them, and start the new virtual machine.
● Shut down the source server—Specify if you want to shutdown the source
server before the new virtual machine is started, which avoids identity
conflicts on the network.
● Original Protection Job—Specify what to do with the original protection job
if the original source is still online. If the original source is not running, these
options will be discarded because they cannot be performed.
● Delete the original protection job—The original protection job is
stopped and then deleted.
● Stop the original protection job—The original protection job is
stopped but is not deleted. It can be restarted after the recovery.
● Leave the original protection job running—The original protection
job is not stopped or deleted. Keep in mind with this option that the data
on the recovery server could become inconsistent or corrupted because
the original source protection job could be transmitting data to the
repository server and that data might get transmitted to the recovery
server, depending on the progress of the recovery process .
17. Click Next to continue.
18. At the Recovery summary page, you can review the choices you have made and
you can also set optional data transmission and e-mail notification settings. If you

74 of 195
 need to make any changes to the selections you made, click Back to return to the
previous pages. If you want to configure optional settings, click Configure. Once
you have completed your configuration, click Finish to start the recovery.
19. Monitor the progress of the recovery mirror on the Monitor page.
20. When the recovery mirror has completed, the new virtual machine on the recovery
server will automatically start to complete the recovery process. If you specified to
pause the recovery, when the mirror is complete, the Activity will change to
Protected. Use this time to complete any necessary tasks. When you are ready to
complete the recovery, click Recover on the Monitor page toolbar to complete the
recovery process. Once the virtual machine has been started, it will become the
original source server.

Because the Windows product activation is dependent on hardware, you

Note may need to reactivate your Windows registration after recovery. Follow
the on-screen prompts to complete the reactivation.

75 of 195
Recovering an entire server to an automatically
provisioned virtual machine on Hyper-V
1. There are two ways to begin the recovery process.
● Click Recover from the left navigation pane and identify the repository server
that contains your source data that you want to recover. Click Next to
continue.
● Highlight the data protection job on the Monitor page and select Recover
from the toolbar. This automatically identifies the repository server that
contains the source data that you want to recover.
2. Select the image of the source that you want to recover and the point-in-time
strategy.

● Available images—Select the image of the source that contains the data you
want to recover. If the image is not displayed, click Browse to look for the
location of the server image.

76 of 195
 ● Live data—Select this option to recover to the live data that is currently
stored on the repository server.
● Snapshot—Select this option and choose a snapshot from the list to recover
to the data stored in that snapshot. If you did not enable snapshots or there
were no snapshots taken on the repository server, there will be no snapshots
in the list.
● Specific time—Select this option and choose a specific date and time to
recover the data from that point in time. The table below the date and time
fields allows you to confirm that the Storage Mirroring Replicate data is valid
for the point in time you are selecting. If you did not enable continuous data
protection when you configured protection or if the TimeData initialization
has not completed, this option will not be available.
3. Click Next to continue.
4. Select the recovery server. This is the Hyper-V server that will host the virtual
machine that, after the recovery, will become your new source.

● Provision a new virtual machine for this recovery—Enable this option to

recover to an automatically provisioned virtual machine hosted on a Hyper-V
server.
● Server—Specify the name of the Hyper-V server. You can also click Browse
to select the name from Active Directory or from a network drill-down list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the recovery server. If your original source was the only
domain controller in your network, you must specify a local account in the
local administrators group.
● Password—Specify the password associated with the User name you

77 of 195
 ● Domain—If you are working in a domain environment, specify the Domain.
5. Click Next to continue.
6. Because you are creating a new virtual machine, you must Recover the entire
server so that the system state from the original source can be used to create the
new virtual. You can exclude volumes that you protected but do not want to
recover, but be careful when excluding data. Excluded volumes may compromise
the integrity of your applications. Volumes marked with a checkmark are included.
If there is no checkmark, the item is excluded.

7. Click Next to continue.

8. Specify the volumes to create on the new virtual machine.

● Selected Data—This displays the amount of data, in gigabytes, currently on

the source volume.
● Source Size—This displays the size, in gigabytes, of the volume on the
source.
● Provisioned Volume—Specify the size, in gigabytes, of the volume to be
created on the new virtual.
● Controller Type—Specify the type of controller, IDE or SCSI, to be used for
each volume. The boot volume must be an IDE controller.

78 of 195
 8. Click Next to continue.
9. Specify the volume and, if desired a folder, on the target server where the new
virtual machine will be created. You can only select a volume that has enough free
space available.

10. Click Next to continue.

11. Configure the new virtual machine that will be created and will become the source
after the recovery.

● Hyper-V Manager display name—By default, source name_VM will be

used to create the new virtual machine display name. If desired, you can
modify the name.
● Map replica virtual network IP to target networks—You will need to
identify how you want to handle the network mapping. The Replica VM
Network IP lists the IP addresses contained in the image of the original
source. Map each one to a Target Network, which is a virtual network on the
Hyper-V server.

79 of 195
 ● Number of processors—Specify how many processors to configure on the
virtual machine. The number of processors from the original source image is
displayed.
● Amount of memory—Specify the amount of memory to configure on the
virtual machine. The amount of memory from the original source image is
displayed.
12. Click Next to continue.
13. Specify your recovery shutdown options.

● Wait for user intervention before recovery—Specify if you want to pause

the recovery process after the original source image has been mirrored to the
new virtual machine on the Hyper-V server, which allows you time to
coordinate any other tasks. If you do not pause the recovery, the new virtual
machine will be started immediately after the mirror is complete.
● Shut down the source server—Specify if you want to shutdown the source
server before the new virtual machine is started, which avoids identity
conflicts on the network.
● Original Protection Job—Specify what to do with the original protection job
if the original source is still online. If the original source is not running, these
options will be discarded because they cannot be performed.
● Delete the original protection job—The original protection job is
stopped and then deleted.
● Stop the original protection job—The original protection job is
stopped but is not deleted. It can be restarted after the recovery.

80 of 195
 ● Leave the original protection job running—The original protection
job is not stopped or deleted. Keep in mind with this option that the data
on the recovery server could become inconsistent or corrupted because
the original source protection job could be transmitting data to the
repository server and that data might get transmitted to the recovery
server, depending on the progress of the recovery process .
14. Click Next to continue.
15. At the Recovery summary page, you can review the choices you have made and
you can also set optional data transmission and e-mail notification settings. If you
need to make any changes to the selections you made, click Back to return to the
previous pages. If you want to configure optional settings, click Configure. Once
you have completed your configuration, click Finish to start the recovery.
16. Monitor the progress of the recovery mirror on the Monitor page.
17. When the recovery mirror has completed, the new virtual machine on the recovery
server will automatically start to complete the recovery process. If you specified to
pause the recovery, when the mirror is complete, the Activity will change to
Protected. Use this time to complete any necessary tasks. When you are ready to
complete the recovery, click Recover on the Monitor page toolbar to complete the
recovery process. Once the virtual machine has been started, it will become the
original source server.

Because the Windows product activation is dependent on hardware, you

Note may need to reactivate your Windows registration after recovery. Follow
the on-screen prompts to complete the reactivation.

81 of 195
Recovering data to an existing physical or virtual
machine
1. There are two ways to begin the recovery process.
● Click Recover from the left navigation pane and identify the repository server
that contains your source data that you want to recover. Click Next to
continue.
● Highlight the data protection job on the Monitor page and select Recover
from the toolbar. This automatically identifies the repository server that
contains the source data that you want to recover.
2. Select the image of the source that you want to recover and the point-in-time
strategy.

● Available images—Select the image of the source that contains the data you
want to recover. If the image is not displayed, click Browse to look for the
location of the server image.

82 of 195
 ● Live data—Select this option to recover to the live data that is currently
stored on the repository server.
● Snapshot—Select this option and choose a snapshot from the list to recover
to the data stored in that snapshot. If you did not enable snapshots or there
were no snapshots taken on the repository server, there will be no snapshots
in the list.
● Specific time—Select this option and choose a specific date and time to
recover the data from that point in time. The table below the date and time
fields allows you to confirm that the Storage Mirroring Replicate data is valid
for the point in time you are selecting. If you did not enable continuous data
protection when you configured protection or if the TimeData initialization
has not completed, this option will not be available.
3. Click Next to continue.
4. You will be prompted that you are restoring data only and not system state
information. Continue the recovery by selecting Yes.
5. Select the recovery server. If you used the Storage Mirroring Replicate built-in
installation to push a copy of Storage Mirroring Replicate to the recovery server,
that copy will automatically be activated when you select it as a recovery server.
The copy will automatically deactivate after five days.

● Provision a new virtual machine for this recovery—This option will not be
available. It is only available for full-server recoveries.
● Server—Specify the name of the recovery server. You can also click Browse
to select the name from Active Directory or from a network drill-down list.
● User name—Specify a user that is a member of the Double-Take Admin
security group on the recovery server.

83 of 195
 ● Password—Specify the password associated with the User name you
entered.
● Domain—If you are working in a domain environment, specify the Domain.
6. Click Next to continue.
7. Because you are working with data only, you will be unable to Recover the entire
server. You can only recover the data you selected to protect. You can exclude
files that you protected but do not want to recover, but be careful when excluding
data. Excluded volumes, folders, and/or files may compromise the integrity of your
applications.

Volumes, folders, and files that are marked with a checkmark are included. If there
is no checkmark, the item is excluded. Expand and collapse the directory tree and
click on an item to add or remove a checkmark. Once you have configured the data
to recover, click Next to continue.

The Select all and Deselect all buttons allow you to quickly select or deselect
all data on your server based on your system state or selected data only choice.
Note:
These buttons will do not change what is selected for the system state, which is
defined by Storage Mirroring Replicate and cannot be modified.

8. Specify the location, including the volume, on the recovery server to store the
source data. For example, you might enter C: or C:\directory.
9. Click Next to continue.
10. Specify your recovery shutdown options.

84 of 195
 ● Wait for user intervention before recovery—This option is not available for
data recovery. It is for full-server recovery jobs only.
● Shut down the source server from the original protection job—Specify if
you want to shutdown the source server after the source data is mirrored to
the recovery server. This option is not available if the recovery server is the
original source.
● Original Protection Job—Specify what to do with the original protection job
if the original source is still online. If the original source is not running, these
options will be discarded because they cannot be performed. This option is
not available if the recovery server is the original source or the repository
server.
● Delete the original protection job—The original protection job is
stopped and then deleted.
● Stop the original protection job—The original protection job is
stopped but is not deleted. It can be restarted after the recovery.
● Leave the original protection job running—The original protection
job is not stopped or deleted. Keep in mind with this option that the data
on the recovery server could become inconsistent or corrupted because
the original source protection job could be transmitting data to the
repository server and that data might get transmitted to the recovery
server, depending on the progress of the recovery process .
11. Click Next to continue.
12. At the Recovery summary page, you can review the choices you have made and
you can also set optional data transmission and e-mail notification settings. If you
need to make any changes to the selections you made, click Back to return to the

85 of 195
 previous pages. If you want to configure optional settings, click Configure. Once
you have completed your configuration, click Finish to start the recovery.
13. Monitor the progress of the recovery mirror on the Monitor page.

86 of 195
Optional recovery settings
When you are creating a recovery job, you will have an opportunity to configure optional
job settings when you get to the Recovery summary workflow page. If you want to
configure optional settings, click Configure next to the options section.
● Compressing data for transmission for a recovery job
● Limiting bandwidth for a recovery job
● Routing transmission for a recovery job
● E-mailing recovery server event messages

Compressing data for transmission for a recovery job

To help reduce the amount of bandwidth needed to transmit Storage Mirroring Replicate
data, compression allows you to compress data prior to transmitting it across the
network. In a WAN environment this provides optimal use of your network resources. If
compression is enabled, the data is compressed before it is transmitted from the source.
When the repository server receives the compressed data, it decompresses it and then
writes it to disk.

By default, compression is set to None, which means it is disabled. The compression

levels can be set at Minimum, Medium, or Maximum. Each level requires more
overhead than the previous level of compression. If you notice an impact on performance
while compression is enabled in your environment, either adjust to a lower level of
compression or leave compression disabled.

Limiting bandwidth for a recovery job

Bandwidth limitations are available to restrict the amount of network bandwidth used for
Storage Mirroring Replicate data transmissions. When a bandwidth limit is specified,
Storage Mirroring Replicate never exceeds that allotted amount. The bandwidth not in
use by Storage Mirroring Replicate is available for all other network traffic.

87 of 195
 ● Do not limit bandwidth—Storage Mirroring Replicate will transmit data using
100% bandwidth availability.
● Place this limit on the bandwidth—Enter a value in kilobytes per second to limit
data transmission. This is the maximum amount of data that will be transmitted per
second.

Routing transmission for a recovery job

By default, Storage Mirroring Replicate will select a default route for transmissions. The
default route is the first connection listed in the NIC binding order on the repository
server. If you want to select a different route for Storage Mirroring Replicate
transmissions, you can select a different IP address on the repository server using the
Storage Mirroring Replicate Route option, or you can reorder the bindings on the
repository server (Network Connections, Advanced, Advanced Settings, Adapters
and Bindings).

E-mailing recovery server event messages

E-mail notification sends specific Storage Mirroring Replicate events to user-defined e-
mail addresses. If you want to use e-mail notification, you will need to identify who will
receive the messages, what messages they will receive, and your e-mail server
configuration.

The e-mail notification settings are for the recovery server. If you want to
Note: configure e-mail notification for your repository server (which is acting in a
source server role), see E-mailing source event messages.

● Recipients—Specify the e-mail address that each Storage Mirroring Replicate e-

mail message should be sent to and click Add New. The e-mail address will be

88 of 195
 inserted into the list of addresses. Each address is limited to 256 characters, and
you can add up to 256 e-mail addresses. If you want to remove an address from
the list, highlight the address and click Remove. If you want to remove all of the
addresses from the list, click Clear.

● Notifications—Specify which events that you want to be sent via e-mail. You can
select Error, Warning, and/or Information.

● Server Setup—Specify your e-mail server configuration.

● Mail Server—Specify the name of your SMTP mail server.

● Log on to SMTP server—If your SMTP server requires a login, enable this
option and specify a User name and Password.

TimeData events do not support authenticated SMTP notification

Note: methods. Check the TimeData log files for TimeData events if you are
using authenticated SMTP.

89 of 195
 ● User name—Specify a user account with privileges to send e-mail
messages from your SMTP server.
● Password—Specify the password associated with the User Name you
entered.
● From Address—Specify the e-mail address that you want to appear in the
From field of each Storage Mirroring Replicate e-mail message. The address
is limited to 256 characters.
● Subject prefix—Specify default text that will appear on every Storage
Mirroring Replicate e-mail message. This will help distinguish Storage
Mirroring Replicate messages from other messages.
● Add event description to prefix—Specify if you want the description of the
event appended to the Subject prefix. The subject line is limited to 150
characters, so only the first 150 characters of the combined Subject prefix
and event description will be displayed.

Make sure you configure your e-mail client so that the Storage Mirroring
Note: Replicate e-mail notification messages do not get blocked by a spam filter
or sent to a junk mail folder.

90 of 195
Job monitoring
Once a job is established you will want to monitor it. You can monitor the job directly
from the Storage Mirroring Replicate console, or you can use several general monitoring
tools that are available.
● Monitoring a job through the Storage Mirroring Replicate console
● Monitoring log files
● Monitoring event messages
● Statistics
● Performance Monitor
● SNMP
● Error codes

91 of 195
Monitoring a job through the Storage Mirroring
Replicate console
Once you have a job established or imported, you can easily monitor the status of the job
from the Monitor page.
When viewing the Monitor page, the main window is divided into two sections. The top
pane displays overview monitoring information, while the bottom pane displays detailed
data. You can hide the details pane by clicking on the Hide details text. You can display
the details pane by clicking on the Show details text.
There is also a toolbar on the Monitor page for specific job and monitoring controls.

Overview status information

Overview information is provided for each job at the top of the Monitor page.

92 of 195
 Column Description

The first unlabeled column is an icon that indicates at-a-glance the status
of the job.

The black, moving circular icon indicates the console is attempting to

process the job to determine the status and statistics.
<no label> The white checkmark inside a green circle indicates the job is in a
good state.

The black exclamation point inside a yellow triangle indicates the job
is in a warning state.

The white X inside a red circle indicates the job is in a bad state.
● Data Protection—This type of job is protecting selected data on the
source.
● Server Protection—This type of job is protecting an entire source,
including the system state.
Job Type
● Data Recovery—This type of job is recovering selected data from
the repository server
● Server Recovery—This type of job is recovering an entire source
from the repository server.

There are many different status messages that keep you informed of the
progress of your jobs. Most of the status messages are informational and
Status do not require any administrator interaction. If you see error messages,
check the job details. You can also view the Storage Mirroring log file on
the server for additional information about processing on that machine.

Source indicates which server is transmitting mirror and replication data.

● Data Protection jobs—When the Job Type is Data Protection,
this is the name of your source. The data from the source is being
transmitted from the source and is being received by the repository
server.
● Server Protection jobs—When the Job Type is Server Protection
Source
, this is the name of your source. The image of the source is being
transmitted from the source and is being received by the repository
server.
● Data Recovery jobs—When the Job Type is Data Recovery, this
is the name of the repository server. The data from the original
source is being transmitted from the repository server and is being

93 of 195
 Column Description

received by the recovery server.

● Sever Recovery jobs—When the Job Type is Server Recovery,
this is the name of the repository server. The image of the original
source is being transmitted from the repository server and is being
received by the recovery server.

Target indicates which server is receiving mirror and replication data.

● Data Protection jobs—When the Job Type is Data Protection,
this is the name of your repository server. The data from the source
is being transmitted from the source and is being received by the
repository server.
● Server Protection jobs—When the Job Type is Server Protection
, this is the name of your repository server. The image of the source
is being transmitted from the source and is being received by the
Target repository server.
● Data Recovery jobs—When the Job Type is Data Recovery, this
is the name of the recovery server. The data from the original source
is being transmitted from the repository server and is being received
by the recovery server.
● Sever Recovery jobs—When the Job Type is Server Recovery,
this is the name of the recovery server. The image of the original
source is being transmitted from the repository server and is being
received by the recovery server.

94 of 195
 Column Description

When mirroring, this is the estimated time remaining to complete the

mirror. For various reasons, this calculation is an estimate. For example,
Time
some file components, like alternate data streams, cannot be included in
Remaining
mirror calculations, or the size of the data set may have changed after the
mirror started.

When mirroring, this is the estimated percentage of the mirror that is

complete. For various reasons, this calculation is an estimate. For
%
example, some file components, like alternate data streams, cannot be
Complete
included in mirror calculations, or the size of the data set may have
changed after the mirror started.

Detailed status information

Detailed information is provided for each job at the bottom of the Monitor page.

Detailed
Section Description
Item

● Data Protection—This type of job is protecting

selected data on the source.
● Server Protection—This type of job is protecting
Job an entire source, including the system state.
Job type
properties ● Data Recovery—This type of job is recovering
selected data from the repository server
● Server Recovery—This type of job is recovering
an entire source from the repository server.

There are many different status messages that keep you

informed of the progress of your jobs. Most of the status
messages are informational and do not require any
administrator interaction. If you see error messages,
check the job details.
Job If the Job Status is Communication Error, the issue
Job Status
properties could be several things such as the source server is
unavailable or the client has invalid credentials for the
source. If it is a problem with the source server, perhaps
the Storage Mirroring service is not running, resolve the
problem on the source. If the source appears to have no
issues, try refreshing the job credentials through the

95 of 195
 Detailed
Section Description
Item

Update credentials toolbar button.

For more details on error messages, review the log file
on the server for additional information about
processing on that machine.

When mirroring, this is the estimated time remaining to

complete the mirror. For various reasons, this
Job Time calculation is an estimate. For example, some file
properties Remaining components, like alternate data streams, cannot be
included in mirror calculations, or the size of the data
set may have changed after the mirror started.

96 of 195
 Detailed
Section Description
Item

Source server indicates which server is transmitting

mirror and replication data.
● Data Protection jobs—When the Job Type is
Data Protection, this is the name of your source.
The data from the source is being transmitted from
the source and is being received by the repository
server.
● Server Protection jobs—When the Job Type is
Server Protection, this is the name of your
source. The image of the source is being
Job Source transmitted from the source and is being received
properties server by the repository server.
● Data Recovery jobs—When the Job Type is
Data Recovery, this is the name of the repository
server. The data from the original source is being
transmitted from the repository server and is being
received by the recovery server.
● Sever Recovery jobs—When the Job Type is
Server Recovery, this is the name of the
repository server. The image of the original source
is being transmitted from the repository server and
is being received by the recovery server.

97 of 195
 Detailed
Section Description
Item

Target server indicates which server is receiving mirror

and replication data.
● Data Protection jobs—When the Job Type is
Data Protection, this is the name of your
repository server. The data from the source is
being transmitted from the source and is being
received by the repository server.
● Server Protection jobs—When the Job Type is
Server Protection, this is the name of your
repository server. The image of the source is
Job Target being transmitted from the source and is being
properties server received by the repository server.
● Data Recovery jobs—When the Job Type is
Data Recovery, this is the name of the recovery
server. The data from the original source is being
transmitted from the repository server and is being
received by the recovery server.
● Sever Recovery jobs—When the Job Type is
Server Recovery, this is the name of the recovery
server. The image of the original source is being
transmitted from the repository server and is being
received by the recovery server.

Job Image This is the location on the Target server where the data
properties Location or image is stored.

This is the total amount of data (mirroring and

Connection Total sent
replication) that has been sent from the Source server
Properties data
to the Target server.

This is the total amount of compressed data (mirroring

Connection Total sent and replication) that has been sent fromthe Source
Properties compressed server to the Target server. If compression is disabled,
this statistic will be the same as Total sent data.

● Transmitting—The job is transmitting data.

Connection Transmit ● Stopped—The job is stopped.
Properties status ● Paused—The job is paused.
● Error—There is a transmission error.

98 of 195
 Detailed
Section Description
Item

● Processing—The Target server is processing

Connection Target data.
Properties status
● Paused—The Target server is paused.

● Yes—The mirror is complete and replication is

continuing. The data or image is valid for
Connection Recovery recovery.
Properties available
● No—The mirror is not yet complete, so the data or
image is not yet valid for recovery.

● Calculating—The amount of mirror data is being

calculated.
● Mirroring—Data is being mirrored.
Mirror Mirror ● Idle—There is no data to mirror.
statistics status ● Paused—The mirror is paused.
● Stopped—The mirror is stopped.
● Unknown—The console is trying or unable to
determine the mirror status.

This is the estimated percentage of the mirror that is

complete. For various reasons, this calculation is an
Mirror
Mirror estimate. For example, some file components, like
percent
statistics alternate data streams, cannot be included in mirror
complete
calculations, or the size of the data set may have
changed after the mirror started.

This is the estimated amount of mirroring data that still

has to be transmitted. For various reasons, this
Mirror Mirror calculation is an estimate. For example, some file
statistics remaining components, like alternate data streams, cannot be
included in mirror calculations, or the size of the data
set may have changed after the mirror started.

This is the amount of mirroring data that has been

Mirror Mirror
skipped (because the data is not different on the
statistics skipped
Source server and Target server).

99 of 195
 Detailed
Section Description
Item

● Replicating—Data is being replicated.

● Pending—Replication is pending.
● Stopped—Replication is stopped.
● Out of memory—Kernel memory has been
Replication Replication exhausted.
statistics status ● Watchdog—The Storage Mirroring service is not
receiving replication operations from the Storage
Mirroring driver.
● Unknown—The console is trying or unable to
determine the replication status.

Replication This is the total amount of replication data that has been
Bytes sent
statistics sent from the Source server to the Target server.

This is the total amount of compressed replication data

Replication Bytes sent that has been sent from the Source server to the
statistics compressed Target server. If compression is disabled, this statistic
will be the same as Bytes sent.

Replication Bytes This is the total amount of replication data that is in

statistics queued queue on the source.

Monitor page toolbar

The Monitor page has its own toolbar buttons for job and monitoring controls.

Toolbar Tooltip
Description
Icon Text

The large shield icon on the far left of the toolbar opens a
New
small menu that lets you select an action to perform. Select
activity
Protect or Recover.

Import The smaller shield icon with the green circle with white plus
jobs sign allows you to launch the import jobs workflow.

The smaller shield icon with the red circle with white line
Stop
removes the job from the console Monitor page. The job
monitoring
remains active, but is no longer visible from the console. To
job
see the job again, import it using the Import jobs button. If

100 of 195
Toolbar Tooltip
Description
Icon Text

you want to permanently delete the job, use the Delete job
button.

Resume The green triangle icon resumes the selected job.

The red square icon stops the selected job. The image of the
source, at the time the job was stopped, is still available for
recovery, but the image is no longer being updated with data
Stop
changes from the source. If you want to use the job again,
you must restart it using the Resume button. When you
restart a job, a remirror will automatically be performed.

The blue icon resembling a photograph takes an immediate

Take a snapshot of the data on the repository server. A pop-up
snapshot dialog box will notify you of the success or failure of the
snapshot.

The life preserver icon starts the recovery process for the
Recover
selected job.

The keys icon allows you to specify credentials for the

Source server and the Target server.
If the Password associated with a specified User name
Update changes after a job has been started, Storage Mirroring
credentials Replicate will attempt to update the credentials it is using. If
the automatic update is not successful, the monitor page will
report Invalid credentials. In this case, you will need to
manually update the credentials that the job is using the
Update credentials button.

The trash can icon permanently deletes the selected job.

The image of the source, at the time the job was deleted, is
still available for recovery, but the image is no longer being
Delete job
updated with data changes from the source. If you want to
use the job again, you must re-create it using the New
activity button.

101 of 195
Toolbar Tooltip
Description
Icon Text

The paper with magnify glass icon toggles between

View
displaying and hiding the details at the bottom of the Monitor
details
page.

The green circle with the white checkmark icon toggles

between displaying and hiding those jobs that are in a good
OK
state. The number of jobs in the good state is also displayed
on the toolbar button.

The yellow triangle with the black exclamation point icon

toggles between displaying and hiding those jobs that are in
Warnings
a warning state. The number of jobs in the warning state is
also displayed on the toolbar button.

The red circle with the white X icon toggles between

displaying and hiding those jobs that are in an error state.
Error
The number of jobs in the error state is also displayed on the
toolbar button.

To the right of all of the toolbar buttons is a summary of the

number of jobs displayed by the good, warning, and error
state toggle buttons. The total number of jobs available for
display in this console is also displayed.

102 of 195
Monitoring log files
Various Storage Mirroring Replicate components, for example the Storage Mirroring
service and the Storage Mirroring Replicate console, generate a log file to gather alerts,
which are notification, warning, and error messages. The log files are written to disk.

Log File Description

This log records basic processing from the Storage Mirroring Replicate
console. It can be found in the Storage Mirroring Replicate installation
livewire.log
directory where the console is being run. This log contains
informational messages only.

This log records detailed processing from the Storage Mirroring

livewire_
Replicate console. It can be found in the Storage Mirroring Replicate
debug.log
installation directory where the console is being run.

This log records detailed processing from the Storage Mirroring

jobmgr.log Replicate servers. It can be found in the Storage Mirroring Replicate
installation directory on the repository or recovery server.

This log records virtual server provisioning processing when

recovering to provisioned virtual machines. The file name is based on
JobName.log the name of the job. It can be found in the \VRA\logs directory under
the Storage Mirroring Replicate installation directory on the repository
or recovery server.

This log contains information from the Storage Mirroring service. The
letter X in the file name represents a series number, for example
dtlogX.dtl dtlog1.dtl, dtlog2.dtl, dtlog3.dtl, and so on. It can be found in the
Storage Mirroring Replicate installation directory on the Storage
Mirroring Replicate servers.

TDAgent-
These three log files record detailed processing for TimeData
Default.log
continuous data protection. They can be found in the \TimeData\logs
TDMsgSvr.log directory under the Storage Mirroring Replicate installation directory
on the repository.
TDRepSvr.log

103 of 195
Monitoring event messages
An event is a significant occurrence in the system or in an application that requires
administrators to be notified. The operating system writes notifications for these events to
a log that can be displayed using the Windows Event Viewer. Three different log files
are generated: application, security, and system.
1. To access the Event Viewer, select Programs, Administrative Tools, Event
Viewer.
2. Select the log to view (System, Security, or Application) from the left pane of the
Event Viewer. The following information is displayed for an event in the right pane
of the Event Viewer.
● Type—A classification of the event, such as Error, Warning, Information,
Success Audit, or Failure Audit.
● Date—The date the event occurred.
● Time—The time the event occurred.
● Source—The software that logged the event, which can be either an
application or a component of the system, such as a driver.
● Category—A classification of the event.
● Event—Shows an ID number to identify the specific event. The Event helps
product-support representatives track events in the system.
● User—Identifies the user that logged the event.
● Computer—The name of the computer where the event occurred.
3. To view a detailed description, double-click an event. The additional information is
displayed in the Event Properties screen.

For additional information on customizing the Event Viewer (such as

Note: sorting the display, filtering the display, and so on), see your Windows
reference guide or the Windows online help.

Event messages
The following table identifies the events.

104 of 195
 ID Category Severity Event Message Required Response

This evaluation period has

expired. Mirroring and
Contact your vendor to
Activation replication have been
1 Error purchase either a single
Key stopped. To obtain a
or site license.
license, please contact
your vendor.

Contact your vendor

before the evaluation
Activation The evaluation period
2 Info. period expires to
Key expires in %1 day(s).
purchase either a single
or site license.

Contact your vendor

The evaluation period has before the evaluation
Activation
3 Info. been activated and expires period expires to
Key
in %1 day(s). purchase either a single
or site license.

If you have an evaluation

license or a site license,
no action is necessary. If
Duplicate activation codes
Activation you have a single
4 Warning detected on machine %1
Key license, you must
from machine %2.
purchase either another
single license or a site
license.

This product edition can

Verify your activation
only be run on Windows
Activation code has been entered
5 Error Server or Advanced Server
Key correctly and contact
running the Server
technical support.
Appliance Kit.

Run the installation and

select Repair. Contact
1000 DTCounters Error An exception occurred: %1
technical support if this
event occurs again.

The Double-Take counter Run the installation and

1001 DTCounters Error DLL could not initialize the select Repair. Contact
statistics handler object to technical support if this

105 of 195
 ID Category Severity Event Message Required Response

gather performance data. event occurs again.

The Double-Take counter Run the installation and

DLL could not map shared select Repair. Contact
1002 DTCounters Error
memory file containing the technical support if this
performance data. event occurs again.

The Double-Take counter

Run the installation and
DLL could not open the
select Repair. Contact
1003 DTCounters Error "Performance" key in the
technical support if this
Double-Take section of the
event occurs again.
registry.

The Double-Take counter

Run the installation and
DLL could not read the
select Repair. Contact
1004 DTCounters Error "First Counter" value under
technical support if this
the Double-
event occurs again.
Take\Performance Key.

The Double-Take counter Run the installation and

DLL read the "First Help" select Repair. Contact
1005 DTCounters Error
value under the Double- technical support if this
Take\Performance Key. event occurs again.

The Double-Take counter Run the installation and

DLL could not create event select Repair. Contact
1006 DTCounters Error
handler for the worker technical support if this
thread. event occurs again.

Logger service was

3000 Service Info. No action required.
successfully started.

Logger service was

3001 Service Info. No action required.
successfully stopped.

Kernel was successfully

4000 Service Info. No action required.
started.

Target service was

4001 Service Info. No action required.
successfully started.

Source service was

4002 Service Info. No action required.
successfully started.

106 of 195
 ID Category Severity Event Message Required Response

Source service was

4003 Service Info. No action required.
successfully stopped.

Target service was

4004 Service Info. No action required.
successfully stopped.

Kernel was successfully

4005 Service Info. No action required.
stopped.

Service has aborted due to

Restart the Storage
4006 Service Error the following unrecoverable
Mirroring service.
error: %1

The connection is auto-

disconnecting because
the disk-based queue on
the source has been
filled, the service has
encountered an
unknown file ID, the
Auto-disconnecting from
target server has
4007 Service Warning %1 (%2) for Replication Set
restarted, or an error has
%3, ID: %4 due to %5
occurred during disk
queuing on the source or
target (for example,
Storage Mirroring
Replicate cannot read
from or write to the
transaction log file).

Auto-disconnect has
4008 Service Info. succeeded for %1 (%2) for No action required.
Replication Set %3, ID: %4

Auto-reconnecting
4009 Service Info. Replication Set %1 to %2 No action required.
(%3)

Auto-reconnect has
succeeded connecting
4010 Service Info. No action required.
Replication Set %1 to %2
(%3)

107 of 195
 ID Category Severity Event Message Required Response

Auto-reconnect has failed Manually reestablish the

4011 Service Error connecting Replication Set replication set to target
%1 to %2 (%3) connection.

This is a placeholder
message for many other
4012 Service Warning %1 messages. See the
specific log message for
additional details.

This is a placeholder
message for many other
4013 Service Info. %1 messages. See the
specific log message for
additional details.

Service has started network

4014 Service Info. No action required.
transmission.

Service has stopped

4015 Service Info. No action required.
network transmission.

Service has established a

4016 Service Info. connection to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has disconnected

4017 Service Info. from %1 (%2) for No action required.
Replication Set %3, ID: %4

%1, however, mirroring and

replication have been
4018 Service Warning disabled as a restore is Perform a restoration.
required due to a previous
failover.

Service has started a mirror

4019 Service Info. to %1 (%2) for Replication No action required.
Set %3, ID: %4

Service has paused a

4020 Service Info. mirror to %1 (%2) for No action required.
Replication Set %3, ID: %4

108 of 195
 ID Category Severity Event Message Required Response

Service has resumed a

4021 Service Info. mirror to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has stopped a

4022 Service Info. mirror to %1 for Replication No action required.
Set %2, ID: %3, %4

Service has completed a

mirror to %1 %2 for
4023 Service Info. No action required.
Replication Set %3, ID: %4,
%5

Service has started

4024 Service Info. Replication to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has stopped

4025 Service Info. Replication to %1 (%2) for No action required.
Replication Set %3, ID: %4

The target has been

4026 Service Info. paused due to user No action required.
intervention.

The target has been

4027 Service Info. resumed due to user No action required.
intervention.

Registration of service
Verify that the Active
class with Active Directory
Directory server is
failed. Verify that the Active
running and that the
4028 Service Warning Directory server is up and
Storage Mirroring service
the service has the proper
has permission to update
permissions to update its
Active Directory.
entries.

Registration of service Verify that the Active

instance with Active Directory server is
Directory failed. Verify that running and that the
4029 Service Warning
the Active Directory server Storage Mirroring service
is up and the service has has permission to update
the proper permissions to Active Directory.

109 of 195
 ID Category Severity Event Message Required Response

update its entries.

Reinstall the software,

using the installation
RSResource.dll has an
Repair option, to install a
unknown error. The product
4030 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
RSResource.dll could not
Repair option, to install a
be opened. The product
4031 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

The RSResource.dll Reinstall the software,

component version does using the installation
not match the component Repair option, to install a
4032 Service Error version expected by the new copy of the
product. The product RSResource.dll. Contact
functionality has been technical support if this
disabled. error persists.

Reinstall the software,

using the installation
RSResource.dll build
Repair option, to install a
version is invalid. The
4033 Service Error new copy of the
product functionality has
RSResource.dll. Contact
been disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
Error verifying the service
Repair option, to install a
name. The product
4034 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

110 of 195
 ID Category Severity Event Message Required Response

Reinstall the software,

using the installation
Error verifying the product
Repair option, to install a
name. The product
4035 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
Error verifying the vendor
Repair option, to install a
name. The product
4036 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
Error verifying the vendor
Repair option, to install a
URL name. The product
4037 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
Error verifying the product
Repair option, to install a
code. The product
4038 Service Error new copy of the
functionality has been
RSResource.dll. Contact
disabled.
technical support if this
error persists.

Reinstall the software,

using the installation
Error while reading
Repair option, to install a
RSResource.dll. The
4039 Service Error new copy of the
product functionality has
RSResource.dll. Contact
been disabled.
technical support if this
error persists.

111 of 195
 ID Category Severity Event Message Required Response

Reinstall the software,

using the installation
The product code is illegal
Repair option, to install a
for this computer hardware.
4040 Service Error new copy of the
The product functionality
RSResource.dll. Contact
has been disabled.
technical support if this
error persists.

Reinstall the software,

The product code is illegal using the installation
for this operating system Repair option, to install a
4041 Service Error version. The product new copy of the
functionality has been RSResource.dll. Contact
disabled. technical support if this
error persists.

Reinstall the software,

The product code requires using the installation
installing the Windows Repair option, to install a
4042 Service Error Server Appliance Kit. The new copy of the
product functionality has RSResource.dll. Contact
been disabled. technical support if this
error persists.

Reinstall the software,

This product can only be
using the installation
run on a limited number of
Repair option, to install a
processors and this server
4043 Service Error new copy of the
exceeds the limit. The
RSResource.dll. Contact
product functionality has
technical support if this
been disabled.
error persists.

An error was encountered

and replication has been Contact technical
4044 Service Error stopped. It is necessary to support if this error
stop and restart the service persists.
to correct this error.

112 of 195
 ID Category Severity Event Message Required Response

Verify that the Storage

Mirroring Replicate port
%1 value must be between value you are trying to
4045 Service Error 1025 and 65535. Using use is within the valid
default of %2. range. If it is not, it will
automatically be reset to
the default value.

Verify that the Storage

This service failed to start Mirroring Replicate ports
4046 Service Error because of a possible port are not conflicting with
conflict. Win32 error: %1 ports used by other
applications.

The compression levels

available depend on
your operating system.
You can reinstall the
Could not load ZLIB DLL
software, using the
%1. Some levels of
4047 Service Error installation Repair
compression will not be
option, to install a new
available.
copy of the DynaZip.dll,
or contact technical
support if this error
persists.

Service has started a

delete orphans task to %1
4048 Service Info. No action required.
(%2) for Replication Set
%3, ID: %4

Service has paused a

delete orphans task to %1
4049 Service Info. No action required.
(%2) for Replication Set
%3, ID: %4

Service has resumed a

delete orphans task to %1
4050 Service Info. No action required.
(%2) for Replication Set
%3, ID: %4

113 of 195
 ID Category Severity Event Message Required Response

Service has stopped a

delete orphans task to %1
4051 Service Info. No action required.
(%2) for Replication Set
%3, ID: %4

Service has completed a

delete orphans task to %1
4052 Service Info. No action required.
(%2) for Replication Set
%3, ID: %4

Service has started a

4053 Service Info. restore task to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has paused a

4054 Service Info. restore task to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has resumed a

4055 Service Info. restore task to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has stopped a

4056 Service Info. restore task to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has completed a

4057 Service Info. restore task to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has started a

verification task to %1 (%2)
4058 Service Info. No action required.
for Replication Set %3, ID:
%4

Service has paused a

verification task to %1 (%2)
4059 Service Info. No action required.
for Replication Set %3, ID:
%4

Service has resumed a

4060 Service Info. verification task to %1 (%2) No action required.
for Replication Set %3, ID:

114 of 195
 ID Category Severity Event Message Required Response

%4

Service has stopped a

verification task to %1 (%2)
4061 Service Info. No action required.
for Replication Set %3, ID:
%4

Service has completed a

verification task to %1 (%2)
4062 Service Info. No action required.
for Replication Set %3, ID:
%4

Bandwidth limit to %1 (%2)

4063 Service Info. No action required.
has changed to %3.

Bandwidth limit to %1 (%2)

4064 Service Info. is now in the "%3" period at No action required.
%4.

Target data state for

connection %1 from %2
4065 Service Warning No action required.
(%3) has changed because
%4.

The activation code you

The product code requires
are using is for the
a virtual server
Virtual SystemsTM
4066 Service Error environment. The product
edition. This code will
functionality has been
not work on non-virtual
disabled.
server environments.

Check other messages

for errors with the
Storage Mirroring
Replicate drivers, and
No replication ops have correct as required. If
been received from the there are no driver
4067 Service Error
driver for an extended messages, verify that
period of time. your drives are
connected to the source.
If this error persists,
contact technical
support.

115 of 195
 ID Category Severity Event Message Required Response

Reboot the source

Failed to write to a server. Contact technical
4068 Service Error
replicating volume. support if this event
occurs again.

Delete the parameter

The registry parameter %2
4096 System Warning and report this issue to
is unknown.
technical support.

Failed to initialize WMI

support. The last Word in
4097 System Warning No action required.
the Data Window is the NT
status code.

The file system filter failed

to load. Replication will not
occur. Reboot your server Reboot your server and
and contact technical contact technical support
4097 System Error
support if this error occurs if this event occurs
again. The last Word in the again.
Data window is the NT
status code.

The registry parameters

failed to load, so the default
configuration values will be
4098 System Warning No action required.
used. The last Word in the
Data window is the NT
status code.

The control device %2 was

not created.
Communication with the
service will be disabled. Reboot your server and
Reboot the server and contact technical support
4098 System Error
contact technical support if if this event occurs
this error occurs again. The again.
last Word in the Data
window is the NT status
code.

116 of 195
 ID Category Severity Event Message Required Response

The driver detected a hard

link for a file on drive %2.
Hard links are not
4099 System Warning Hard links are not
supported.
supported. Changes to this
file will not be replicated.

The driver failed to register

with filter manager. Reboot
Reboot your server and
the server and contact
contact technical support
4099 System Error technical support if this
if this event occurs
error occurs again. The last
again.
Word in the Data window is
the NT status code.

If you are in the process

of installing Storage
Mirroring Replicate,
verify that you are using
Product activation code is a 24 character alpha-
invalid. Please check that it numeric code. If Storage
Activation
4100 Error is typed correctly and is Mirroring Replicate is
Key
valid for the version of the already installed, confirm
operating system in use. that the code entered is
correct. If the code
appears to be correct,
contact technical
support.

The versions of the driver

and the filter driver do not
match. Replication will not
occur. Reboot your server. Reboot your server.
If this error occurs again, Reinstall the software if
reinstall the software. this event occurs again.
4100 System Error Contact technical support if Contact technical
this error occurs after the support if this event
software has been occurs after reinstalling
reinstalled. The last three the software.
Words in the Data window
are the NT status code and
the driver version numbers.

117 of 195
 ID Category Severity Event Message Required Response

The activation code does

not match the type of
This service will not run on server you are
Activation this device. Contact your attempting to run on.
4101 Error
Key sales representative for Contact your vendor for a
upgrade procedures. new activation code or
contact technical
support.

The disk on the target is

Target cannot write %1 due
full. The operation will be
to target disk being full.
4110 Service Warning retried according to the
Operation will be retried
TGExecutionRetryLimit
(%2 times or forever)
setting.

A sharing violation error

is prohibiting Storage
Target can not write %1 Mirroring Replicate from
due to a sharing violation. writing on the target. The
4111 Service Warning
Operation will be retried operation will be retried
(%2 times or forever) according to the
TGExecutionRetryLimit
setting.

An access denied error

is prohibiting Storage
Target can not write %1 Mirroring Replicate from
due to access denied. writing on the target. The
4112 Service Warning
Operation will be retried operation will be retried
(%2 times or forever) according to the
TGExecutionRetryLimit
setting.

An unknown error is
Target can not write %1
prohibiting Storage
due to an unknown reason.
Mirroring Replicate from
Operation will be retried
writing on the target. The
4113 Service Warning (%2 times or forever).
operation will be retried
Please check the log files
according to the
for further information on
TGExecutionRetryLimit
the error.
setting.

118 of 195
 ID Category Severity Event Message Required Response

Target write to %1 was

4120 Service Info. completed successfully No action required.
after %2 retries.

The operation has been

Target write %1 failed after
retried according to the
%2 retries and will be
TGExecutionRetryLimit
discarded. See the event
setting but was not able
log or log files for error
4150 Service Error to be written to the target
conditions. After correcting
and the operation was
the problem, you should re-
discarded. Correct the
mirror or run a verify to
problem and remirror the
resynchronize the changes.
files.

The service was unable to

complete a file system
Correct the file system
operation in the allotted
error and then remirror or
time. See the log files for
perform a verification
4155 Service Warning error conditions. After
with remirror to
correcting the problem,
synchronize the
remirror or perform a
changes.
verification with remirror to
synchronize the changes.

In band task %1 submitted

4200 Service Info. No action required.
from %2 by %3 at %4

A task may be discarded

in the following
scenarios: all
connections to a target
are manually
disconnected, replication
In band task %1 discarded
is stopped for all
4201 Service Warning (submitted from %2 by %3
connections to a target,
at %4)
or an auto-disconnect
occurs. If one of these
scenarios did not cause
the task to be discarded,
contact technical
support.

119 of 195
 ID Category Severity Event Message Required Response

Running %1 in band script:

4202 Service Info. %2 (task %3 submitted from No action required.
%4 by %5 at %6)

Completed run of in band

4203 Service Info. No action required.
script: %1 (exit code %2)

Review the task and its

Error running in band script:
4204 Service Error associated script(s) for
%1
syntax errors.

The timeout specified for

the script to complete
has expired. Normal
Timeout (%1 seconds) processing will continue.
4205 Service Warning
running in band script: %2 You may need to
manually terminate the
script if it will never
complete.

The timeout period was

set to zero (0). Storage
Mirroring Replicate will
Run timeout disabled for in
4206 Service Warning not wait for the script to
band script: %1
complete before
continuing. No action is
required.

In band scripts disabled by

Enable task command
4207 Service Warning server - no attempt will be
processing.
made to run %1

A connection request was You may need to

received on the target disconnect and
4300 Service Error
before the persistent target reconnect your
paths could be loaded. replication set.

Unable to block target If you need to block your

4301 Service Error paths, the driver is target paths, contact
unavailable. technical support.

4302 Service Info. Target Path %1 has been No action required.

120 of 195
 ID Category Severity Event Message Required Response

successfully blocked

If you need to block your

Blocking of target path: %1
4303 Service Warning target paths, contact
failed. Error Code: %2
technical support.

Target Path %1 has been

4304 Service Info. No action required.
successfully unblocked

If you need to unblock

Unblocking of target path:
4305 Service Warning your target paths, contact
%1 failed. Error Code: %2
technical support.

Target paths for source %1

4306 Service Warning (%2) Connection id: %3 are No action required.
already blocked

Target paths for source %1

4307 Service Warning (%2) Connection id: %3 are No action required.
already unblocked

Error loading target paths If you need to block your

4308 Service Error for blocking, registry key target paths, contact
%1 has been corrupted. technical support.

The snapshot could not

created. This may be
due to a lack of disk
Failed to create snapshot space or memory or
set for source %1 (%2) another reason. The
4400 Service Error
Connection ID: %3. Error: error code is the
%4 Microsoft VSS error.
Check your VSS
documentation or contact
technical support.

121 of 195
 ID Category Severity Event Message Required Response

The automatic snapshot

could not deleted. This
may be due to a lack of
memory, the file does not
Failed to delete automatic exist, or another reason.
snapshot set for source %1 The error code is the
4401 Service Error
(%2) Connection ID: %3. Microsoft Volume
Error: %4 Shadow Copy error.
Check your Volume
Shadow Copy
documentation or contact
technical support.

The snapshot could not

deleted. This may be
due to a lack of memory,
the file does not exist, or
Failed to delete snapshot another reason. The
set for source %1 (%2) error code is the
4402 Service Error
Connection ID: %3. Error: Microsoft Volume
%4 Shadow Copy error.
Check your Volume
Shadow Copy
documentation or contact
technical support.

A scheduled snapshot
could not be created for
source %1 (%2) No action required. A
Connection ID: %3. snapshot will
4403 Service Error because the target data automatically be created
was in a bad state. A when the target data
snapshot will automatically reaches a good state.
be created when the target
data reaches a good state.

Set snapshot schedule for

source %1 (%2) connection
4404 Service Info. No action required.
%3 to every %4 minutes.
Next snapshot: %5.

122 of 195
 ID Category Severity Event Message Required Response

Removed snapshot
4405 Service Info. schedule for source %1 No action required.
(%2) connection %3.

Enabled snapshot
4406 Service Info. schedule for source %1 No action required.
(%2) connection %3.

Disabled snapshot
4407 Service Info. schedule for source %1 No action required.
(%2) connection %3.

Orphan files could not be

%1 was unable to move moved. For example, the
some orphans for source location could be out of
4408 Service Warning %2 on connection ID %3. disk space. Check the
Check the %1 logs for Storage Mirroring
further details. Replicate log for more
information.

%3 was unable to delete Orphan files could not be

some orphans for source deleted. Check the
4409 Service Warning %1 on connection ID %2. Storage Mirroring
Check the %3 logs for Replicate log for more
further details. information.

The registry hive dump Contact technical

4410 Service Error
failed with an of error: %1. support.

The firewall port needs

to be unblocked or
restrictions against
The Service has detected
Storage Mirroring
4411 Service Warning that port %1 is being %2 by
Replicate removed so
the Windows Firewall.
that Storage Mirroring
Replicate data can be
transmitted.

Server Monitor service was

5000 Service Info. No action required.
successfully started.

Server Monitor service was

5001 Service Info. No action required.
successfully stopped.

123 of 195
 ID Category Severity Event Message Required Response

Placeholders were
5002 Service Info. No action required.
modified to %1.

5100 Failover Info. Failover completed for %1. No action required.

IP address %1 with subnet

mask %2 was added to
5101 Failover Info. No action required.
target machine's %3
adapter.

User intervention has

%1 has reached a failover been configured. Open
condition. A response from the Failover Control
5102 Failover Warning
the user is required before Center and accept or
failover can take place. decline the failover
prompt.

Started adding drive shares

5103 Failover Info. No action required.
from %1 to %2.

%1 drive shares were taken

5104 Failover Info. No action required.
over by %2.

Attempting to run the %1

5105 Failover Info. No action required.
script.

The %1 script ran

5106 Failover Info. No action required.
successfully.

Verify that the script

Error occurred in running
5107 Failover Error identified exists with the
%1 script.
proper permissions.

This occurs when all

monitored IP addresses
on the source machine
stop responding to pings.
The source machine %1 is Countdown to failover
5108 Failover Error
not responding to a ping. will begin at the first
occurrence and will
continue until the source
machine responds or
until failover occurs.

124 of 195
 ID Category Severity Event Message Required Response

The failover target did

not receive an answer to
its ping of the source
The public NIC on source
machine. Eventually, a
5109 Failover Error machine %1 is not
failover will result.
responding to a ping.
Investigate possible
errors (down server,
network error, etc.).

The %1 script "%2" is still

5110 Failover Info. No action required.
running.

5200 Failback Info.. Failback completed for %1. No action required.

IP address %1 was
5201 Failback Info.. removed from target No action required.
machine's %2 adapter.

Unable to Failback properly

because IP address %1
Contact technical
5202 Failback Error was missing a
support.
corresponding SubNet
Mask.

The following IP address

5300 Monitoring Info. was added to target's No action required.
monitoring list: %1

The following IP address

5301 Monitoring Info. was removed from target's No action required.
monitoring list: %1

Drive share information for

5302 Monitoring Info. %1 has been updated on No action required.
the target machine.

The application monitor

5303 Monitoring Info. script has started No action required.
successfully.

The application monitor

5304 Monitoring Info script has finished No action required.
successfully.

125 of 195
 ID Category Severity Event Message Required Response

Storage Mirroring
The application monitor
Recover Application
5305 Monitoring Warning has found the %1 service
Manager will attempt to
stopped.
restart the service.

The application monitor

5306 Monitoring Warning has restarted the %1 No action required.
service.

Verify the server is

The application monitor
running. Verify available
5307 Monitoring Error cannot contact the server
network communications
%1.
with the server.

Broadcasted new MAC

5400 ARP Info. address %1 for IP address No action required.
%2.

Storage Mirroring
Replicate could not
connect to your SMTP
server or the username
and/or password
supplied is incorrect.
Could not connect to e-mail
Verify that SMTP server
server. Check to make sure
5500 Service Warning is available and that you
the SMTP server %1 is
have identified it
available (error code: %2).
correctly in your e-mail
notification configuration.
Also verify that your
username and password
have been entered
correctly.

126 of 195
 ID Category Severity Event Message Required Response

This alert occurs if there

is an unexpected error
enabling e-mail
notification during
service startup. Check to
see if any other errors
related to e-mail
E-mail notification could not
notification have been
5501 Service Warning be enabled (error code:
logged. Also, check to
%1).
make sure the Windows
Management
Instrumentation (WMI)
service is enabled. If
neither of these apply,
contact technical
support.

E-mail notification
requires Internet
E-mail notification could not
Explorer 5.0 or later.
be initialized. Check to
5502 Service Warning Verify that you have this
make sure Internet Explorer
version or later installed
5.0 or later is installed.
on the Storage Mirroring
Replicate server.

If you are using Storage

Mirroring Replicate
4.4.2.1 or earlier and
E-mail notification could not
Windows NT 4.0, e-mail
be processed. Check to
notification requires
make sure the correct
5503 Service Warning Windows Management
version of SMTPMail.DLL
Instrumentation (WMI) to
is registered on the system
be installed. Verify that
(error code: %1).
you have it installed on
the Storage Mirroring
Replicate server.

127 of 195
 ID Category Severity Event Message Required Response

This alert occurs if there

is an error loading the
resource DLL for the
service. Typically, this is
caused by a missing
LocalRS.dll file.
Could not load LocalRS.dll
5504 Service Warning Reinstall the software,
(for e-mail notification).
using the installation
Repair option, to install a
new copy of the
LocalRS.dll. Contact
technical support if this
error persists.

Verify that the e-mail

E-mail could not be sent. server that you have
5505 Service Warning Check e-mail settings (error identified in your e-mail
code: %1). notification configuration
is correct.

At a minimum, you must

specify the e-mail server,
One or more required e-
the From and To
5506 Service Warning mail settings have not been
addresses, and at least
specified (error code: %1).
one type of event to
include.

If you are using Storage

Mirroring Replicate
4.4.2.1 or earlier and
E-mail notification could not Windows NT 4.0, e-mail
be initialized. Check to notification requires
5507 Service Warning make sure WMI is installed Windows Management
and available (error code: Instrumentation (WMI) to
%1). be installed. Verify that
you have it installed on
the Storage Mirroring
Replicate server.

128 of 195
 ID Category Severity Event Message Required Response

This alert occurs if there

An error occurred
is an error with the
connecting to the WMI
Windows Management
namespace. Check to
Instrumentation (WMI)
make sure the Windows
5508 Service Warning service. Verify that you
Management
have it installed on the
Instrumentation service is
Storage Mirroring
not disabled (error code
Replicate server and that
%1).
it is enabled.

Verify that the include

Part or all of the e-mail
categories and exclude
5600 Service Warning setting %1 is not in a valid
ID list are identified and
format.
formatted correctly.

The driver was unable to

get valid name information
from the Filter Manager for
Contact technical
7106 RepDrv Error the file %2. (Filename may
support.
be truncated.) It cannot be
replicated. Please contact
technical support.

The driver was unable to

get valid name information
from the Filter Manager for Contact technical
7107 RepDrv Error
a file. It cannot be support.
replicated. Please contact
technical support.

The driver encountered an

unrecoverable internal
error. Contact technical Contact technical
8100 RepDac Error
support. The last Word in support.
the Data window is the
internal error code.

129 of 195
 ID Category Severity Event Message Required Response

Driver failed to allocate

Kernel memory.
Replication is stopped and Reboot the server and
server must be rebooted for contact technical support
8192 Resources Error
replication to continue. The if this event occurs
last word in the data again.
window is the tag of the
allocation that failed.

Kernel memory is
Reboot the server and
exhausted. Replication is
contact technical support
8192 RepDrv Error stopped. This may have
if this event occurs
been caused by low system
again.
resources.

The driver failed to create a

thread required for normal
operation. This may have
been caused by low system Reboot the server and
resources. Reboot your contact technical support
8193 System Error
server and contact if this event occurs
technical support if this again.
error occurs again. The last
Word in the Data window is
the NT status code.

The maximum amount of

memory for replication Contact technical
8196 RepDrv Warning queuing has been reached. support if this event
Replication is stopped and occurs again.
memory is being freed.

The driver registry path

could not be saved. The
8198 Resources Warning No action required.
default registry path will be
used.

The driver failed to allocate

a buffer for a file name
8200 Resources Warning Reboot the server and
longer than 260 characters.
The file will be skipped.

130 of 195
 ID Category Severity Event Message Required Response

The last Word in the Data contact technical support

window is the NT status if this event occurs
code. again.

The driver has failed to

process a rename
operation. The driver will
resend the rename
operation. This message is Contact technical
9000 RepKap Warning only a warning. If you support if this event
receive this message occurs again.
repeatedly, contact
technical support. The last
Word in the Data window is
the NT status code.

The driver encountered an

error opening a file from the
service. Check the Event
Check for related service
Viewer Application log for
messages. Contact
9100 RepKap Error additional service
technical support if this
information or contact
event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error reading from the
service input buffer. Check
the Event Viewer Check for related service
Application log for messages. Contact
9101 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

131 of 195
 ID Category Severity Event Message Required Response

The driver encountered an

error writing to the service
output buffer. Check the
Check for related service
Event Viewer Application
messages. Contact
9102 RepKap Error log for additional service
technical support if this
information or contact
event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing to the service
input buffer. Check the
Check for related service
Event Viewer Application
messages. Contact
9103 RepKap Error log for additional service
technical support if this
information or contact
event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for file
security from the service
input buffer. Check the Check for related service
Event Viewer Application messages. Contact
9104 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for file
security from the service
input buffer. Check the Check for related service
Event Viewer Application messages. Contact
9105 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

132 of 195
 ID Category Severity Event Message Required Response

The driver encountered an

error writing file security
data to the service input
buffer. Check the Event Check for related service
Viewer Application log for messages. Contact
9106 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for an
allocated range from the
service input buffer. Check
Check for related service
the Event Viewer
messages. Contact
9107 RepKap Error Application log for
technical support if this
additional service
event occurs again.
information or contact
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for an
allocated range from the
service output buffer.
Check for related service
Check the Event Viewer
messages. Contact
9108 RepKap Error Application log for
technical support if this
additional service
event occurs again.
information or contact
technical support. The last
Word in the Data window is
the exception code.

133 of 195
 ID Category Severity Event Message Required Response

The driver encountered an

error writing an allocated
range to the service input
buffer. Check the Event Check for related service
Viewer Application log for messages. Contact
9109 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for a
directory from the service
input buffer. Check the Check for related service
Event Viewer Application messages. Contact
9110 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for a
directory from the service
output buffer. Check the Check for related service
Event Viewer Application messages. Contact
9111 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing a directory
query to the service input Check for related service
buffer. Check the Event messages. Contact
9112 RepKap Error
Viewer Application log for technical support if this
additional service event occurs again.
information or contact
technical support. The last

134 of 195
 ID Category Severity Event Message Required Response

Word in the Data window is

the exception code.

The driver encountered an

error querying a stream
from the service input
buffer. Check the Event Check for related service
Viewer Application log for messages. Contact
9113 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing a stream query
to the service output buffer.
Check the Event Viewer Check for related service
Application log for messages. Contact
9114 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing a stream query
to the service output buffer.
Check the Event Viewer Check for related service
Application log for messages. Contact
9115 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver has failed to

close a file handle. If you
Contact technical
9116 RepKap Error receive this message
support.
repeatedly, contact
technical support. The last

135 of 195
 ID Category Severity Event Message Required Response

Word in the Data window is

the NT status code.

The driver encountered an

error querying for extended
attributes from the service
input buffer. Check the Check for related service
Event Viewer Application messages. Contact
9117 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing extended
attributes to the service
output buffer. Check the Check for related service
Event Viewer Application messages. Contact
9118 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing extended
attributes status to the
service input buffer. Check
Check for related service
the Event Viewer
messages. Contact
9119 RepKap Error Application log for
technical support if this
additional service
event occurs again.
information or contact
technical support. The last
Word in the Data window is
the exception code.

136 of 195
 ID Category Severity Event Message Required Response

The driver encountered an

error querying for file
information from the service
input buffer. Check the Check for related service
Event Viewer Application messages. Contact
9120 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing file information
to the service output buffer.
Check the Event Viewer Check for related service
Application log for messages. Contact
9121 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing file information
status to the service input
buffer. Check the Event Check for related service
Viewer Application log for messages. Contact
9122 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error querying for fsctl
information from the service Check for related service
input buffer. Check the messages. Contact
9123 RepKap Error
Event Viewer Application technical support if this
log for additional service event occurs again.
information or contact
technical support. The last

137 of 195
 ID Category Severity Event Message Required Response

Word in the Data window is

the exception code.

The driver encountered an

error writing fsctl
information to the service
output buffer. Check the Check for related service
Event Viewer Application messages. Contact
9124 RepKap Error
log for additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

The driver encountered an

error writing fsctl status to
the service input buffer.
Check the Event Viewer Check for related service
Application log for messages. Contact
9125 RepKap Error
additional service technical support if this
information or contact event occurs again.
technical support. The last
Word in the Data window is
the exception code.

This message is only a

placeholder warning. The
10000 RepHsm Warning last Word in the Data No action required.
window is the NT status
code.

Ensure that GeoCluster

is running on all possible
owners and that it can
communicate on the
Connect failed to node %1
network selected for
10000 GeoCluster Error for resource %2. Adding
mirroring and replication
node to reconnect list.
traffic. GeoCluster will try
to reestablish a
connection using the
check unresponsive

138 of 195
 ID Category Severity Event Message Required Response

node interval specified

for the resource.

Reconnect succeeded to
node %1 for resource %2.
10001 GeoCluster Info. Will be added as a possible No action required.
owner when mirror is
complete.

Ensure that GeoCluster

is running on all possible
owners and that it can
Disk check failed on node
communicate on the
%1 for resource %2.
10002 GeoCluster Error public network. Also
Removing as a possible
ensure that the disk
owner.
specified for the resource
is functioning correctly
on all possible owners.

Ensure that the network

used to access the
arbitration path is up and
that the server is
Owner %1 of the quorum
operational. Also ensure
resource %2 couldn't
10003 GeoCluster Error that the arbitration share
access the arbitration path
path does exist and that
%3. Network may be down.
the account running the
cluster service has write
privileges to the share
path.

Failover of the group %1 is

being delayed. Group will
be brought online when the
10004 GeoCluster Warning No action required.
target queue is below the
limit or the timeout has
expired.

Node %1 is taking
ownership of the group %2.
10005 GeoCluster Info. No action required.
The group will be brought
online on this node.

139 of 195
 ID Category Severity Event Message Required Response

The cluster notification

thread failed to start on
node %1 for resource %2. Take the resource offline
10006 GeoCluster Warning
The resource should be and bring it back online.
taken offline and brought
back online.

The user %1 has reverted a No action required. The

10007 GeoCluster Warning snapshot for the %2 snapshot you selected
resource on node %3. will be reverted.

The user %1 has discarded No action required. The

10008 GeoCluster Warning queued data for the %2 queue you selected will
resource on node %3. be discarded.

A snapshot of the current

The user %1 is verifying data has been taken.
10009 GeoCluster Warning data for the %2 resource on After you have verified
node %3. the data, accept or reject
the data.

No action required.
Since the data was
The user %1 has rejected rejected, the data has
10010 GeoCluster Warning the data for the %2 been reverted to the
resource on node %3. snapshot taken when the
data was selected for
verification.

The user %1 has accepted

No action required. The
10011 GeoCluster Warning the data for the %2
current data will be used.
resource on node %3.

The GeoCluster Replicated Replication has been

Disk resource %1 has been stopped because of the
set to validate its data. No validation request.
data replication is occurring Accept or reject the data
10012 GeoCluster Warning
to the remaining nodes in on the node by right-
the cluster. Please Accept clicking on the resource
or Reject the data by right- and selecting the
clicking on the resource appropriate option.

140 of 195
 ID Category Severity Event Message Required Response

and selecting the

appropriate option.

The driver could not recall

a file because it did not
have a token for
Contact technical
impersonation. The security
10100 RepKap Error support if this event
provider service should set
occurs again.
this token. The last Word in
the Data window is the
exception code.

The driver could not access

the file in the archive bin,
due to a failed Contact technical
10101 RepKap Error impersonation attempt. The support if this event
last Word in the Data occurs again.
window is the exception
code.

The driver could not recall

Contact technical
the file. The last Word in
10102 RepKap Error support if this event
the Data window is the
occurs again.
exception code.

Service has started an

11000 Service Info. archive to %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has completed an

archive to %1 (%2) for
11001 Service Info. No action required.
Replication Set %3, ID: %4,
%5

Service has started a recall

11002 Service Info. from %1 (%2) for No action required.
Replication Set %3, ID: %4

Service has completed a

recall from %1 (%2) for
11003 Service Info. No action required.
Replication Set %3, ID: %4,
%5

141 of 195
 ID Category Severity Event Message Required Response

Service has failed Reboot the server or

11004 Service Warning connection to the RepHSM manually restart the
driver. %1 RepHSM.sys driver.

Verify the activation code

on the source and target
Service has aborted the
11005 Service Warning is valid for archiving.
archive operation.
Reboot an unlicensed
server.

Verify the activation code

on the source and target
Service has aborted the
11006 Service Warning is valid for archiving.
archive recall operation.
Reboot an unlicensed
server.

Review the verification

Verification has finished
11007 Service Warning log to correct or accept
with errors. %1
the errors.

The source and target

Archive feature is not
11008 Service Warning must be NTFS for
supported on volume %1.
archiving functionality.

Service has started an

archive preview to %1 (%2)
11009 Service Info. No action required.
for Replication Set %3, ID:
%4

Service has completed an

archive preview to %1 (%2)
11010 Service Info. No action required.
for Replication Set %3, ID:
%4

Verify the activation code

on the source and target
Service has aborted the
11011 Service Warning is valid for archiving.
archive preview operation.
Reboot an unlicensed
server.

This message refers to

12000 DTRecall Info. The service has started. the Storage Mirroring
Recall service. No action

142 of 195
 ID Category Severity Event Message Required Response

required.

Check the user name

and password for the
Storage Mirroring Recall
12001 DTRecall Error The service failed to start. service to ensure
validity. Reinstall the
software if this event
occurs again.

This message indicates

a system shutdown or
the user stopped the
12002 DTRecall Info. The service has stopped.
Storage Mirroring Recall
service. No action is
required.

Restart the Storage

The service failed to create
Mirroring Recall service.
12003 DTRecall Error a stop control event. (Error
Reinstall the software if
%1)
this event occurs again.

Restart the Storage

RegisterServiceCtrlHandler Mirroring Recall service.
12004 DTRecall Error
failed. (Error %1) Reinstall the software if
this event occurs again.

Restart the Storage

Service encountered
Mirroring Recall service.
12005 DTRecall Error SetServiceStatus error
Reinstall the software if
(Error %1)
this event occurs again.

The Storage Mirroring

Recall service could not
connect to the Storage
Service could not get
Mirroring Recall
12006 DTRecall Error handle to driver for security
archiving driver. Reboot
update. (Error %1)
the server and reinstall
the software if this event
occurs again.

143 of 195
 ID Category Severity Event Message Required Response

This message refers to

the Storage Mirroring
Recall service. The
Service failed a periodic operation will be
12007 DTRecall Warning
security update. (Error %1) performed every five
minutes. Reinstall the
software if this event
occurs after five minutes.

The driver encountered an

error accessing a buffer
from the service. Contact Contact technical
12288 RepDrv Error
technical support. The last support.
Word in the Data window is
the exception code.

The driver encountered an

Contact technical
16384 RepDrv Error unrecoverable error.
support
Contact technical support.

The driver encountered an

unexpected internal result.
Contact technical support. Contact technical
16385 RepDrv Error
The last Word in the Data support.
window is the NT status
code.

The driver encountered an

internal error. Contact
Contact technical
16393 RepDrv Error technical support. The last
support.
Word in the Data window is
the internal error code.

The driver detected a

memory error which may
have been caused by a bad
driver or faulty hardware. Contact technical
16395 Resources Error
Contact technical support. support.
The last Word in the Data
window is the internal error
code.

144 of 195
 ID Category Severity Event Message Required Response

The driver failed to create

work queues for normal
operation. This may have
been caused by low system Reboot the server and
resources. Reboot the contact technical support
16396 Resources Error
server and contact if this event occurs
technical support if this again.
error occurs again. The last
Word in the Data window is
the NT status code.

RepDrv has encountered

an unexpected condition,
usually caused by low
kernel memory. Unless
otherwise mentioned, this
event has already been
16400 RepDrv Info. No action required.
handled and your data
remains protected. If you
continue to receive these
events or have further
questions please contact
tech support.

E-mailing source event messages

For those Storage Mirroring Replicate events generated on the source, you can e-mail
event messages to specific addresses. The subject of the e-mail will contain an optional
prefix, the server name where the message was logged, the message ID, and the
severity level (information, warning, or error). The text of the message will be displayed
in the body of the e-mail message.
1. To configure e-mail notification for source event message, you will need to use the
Replication Console. Select Start, Programs, Storage Mirroring, Storage
Mirroring Replication Console.
2. Right-click the Storage Mirroring Replicate source server on the left pane of the
Replication Console.
3. Select Properties.
4. Select the E-mail Notification tab.

145 of 195
4. Select Enable notification.

Any specified notification settings are retained when Enable notification

Note:
is disabled.

5. Specify your e-mail settings.

● Mail Server (SMTP)—Specify the name of your SMTP mail server.
● Log on to SMTP Server—If your SMTP server requires authentication,
enable Log on to SMTP Server and specify the Username and Password
to be used for authentication. Your SMTP server must support the LOGIN
authentication method to use this feature. If your server supports a different
authentication method or does not support authentication, you may need to
add the Storage Mirroring Replicate server as an authorized host for relaying
e-mail messages. This option is not necessary if you are sending exclusively
to e-mail addresses that the SMTP server is responsible for.
● From Address—Specify the e-mail address that you want to appear in the
From field of each Storage Mirroring Replicate e-mail message. The address
is limited to 256 characters.
● Send To—Specify the e-mail address that each Storage Mirroring Replicate
e-mail message should be sent to and click Add. The e-mail address will be
inserted into the list of addresses. Each address is limited to 256 characters.
You can add up to 256 e-mail addresses. If you want to remove an address
from the list, highlight the address and click Remove. You can also select
multiple addresses to remove by Ctrl-clicking.
● Subject Prefix and Add event description to subject—The subject of each
e-mail notification will be in the format Subject Prefix : Server Name :
Message Severity : Message ID : Message Description. The first and last
components (Subject Prefix and Message Description) are optional. The
subject line is limited to 150 characters.
If desired, enter unique text for the Subject Prefix which will be inserted at
the front of the subject line for each Storage Mirroring Replicate e-mail
message. This will help distinguish Storage Mirroring Replicate messages
from other messages. This field is optional.
If desired, enable Add event description to subject to have the description
of the message appended to the end of the subject line. This field is optional.
● Filter Contents—Specify which messages that you want to be sent via e-
mail. Specify Information, Warning, and/or Error. You can also specify
which messages to exclude based on the message ID. Enter the message
IDs as a comma or semicolon separated list. You can indicate ranges within
the list.

146 of 195
 You can test e-mail notification by specifying the options on the E-mail
Notification tab and clicking Test. (By default, the test will be run from the
machine where the Replication Console is running.) If desired, you can
send the test message to a different e-mail address by selecting Send To
and entering a comma or semicolon separated list of addresses. Modify
the message text up to 1024 characters, if necessary. Click Send to test
the e-mail notification. The results will be displayed in a message box.
Click OK to close the message and click Close to return to the E-mail
Notification tab.
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.
Note: This message will not trigger an e-mail. Subsequent e-mail errors will not
generate additional messages. When an e-mail is sent successfully, a
message will then be generated. If another e-mail fails, one message will
again be generated. This is a cyclical process where one message will be
generated for each group of failed e-mail messages, one for each group of
successful e-mail messages, one for the next group of failed messages,
and so on.
If you start and then immediately stop the Storage Mirroring service, you
may not get e-mail notifications for the log entries that occur during startup.
By default, most virus scan software blocks unknown processes from
sending traffic on port 25. You need to modify the blocking rule so that
Storage Mirroring Replicate e-mail messages are not blocked.

6. Click OK to save the settings.

147 of 195
Statistics
Statistics logging is the process of taking snapshots of Storage Mirroring Replicate
statistical data. The data can be written to a file for future use. Changes to the statistics
file configuration are detected and applied immediately without restarting the Storage
Mirroring service.
The statistics log file created is a binary file. To view the log file, you must run the DTStat
utility from the command prompt.
Sample DTStat output

=================================
0/11/09 12:48:05:2040
=================================
SYSTEMALLOCATOR::Total Bytes: 0
IQALLOCATOR::Total Bytes: 0
SECURITY::Logins : 1 FailedLogins : 0
KERNEL::SourceState: 2 TargetState: 1 Start Time: Tue Sep 11 12:45:26 2007
RepOpsGenerated: 436845 RepBytesGenerated: 0
MirOpsGenerated: 3316423 MirBytesGenerated: 108352749214952
FailedMirrorCount: 0 FailedRepCount: 0
ActFailCount: 0 TargetOpenHandles: 0 DriverQueuePercent: 0
TARGET:: 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: 0
SOURCE::autoDisConnects : 0 autoReConnects : 1
lastFileTouched : /log/data_file
CONNECTION:: 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

148 of 195
Viewing the statistics file
The statistics log file created is a binary file. To view the log file, you must run the DTStat
utility from a command prompt. From the directory where Storage Mirroring Replicate is
installed, run the DTStat command.

Command DTSTAT

Description Starts the DTStats statistics logging utility from a command prompt

DTSTAT [-p][-i <interval>][-t <filename>] [-f <filename>] [-s <filename>]

[-st <filename>][-IP <address>] [-START <mm/dd/yyyy hh:mm>][-
Syntax
STOP <mm/dd/yyyy hh:mm>] [-SERVER <ip_address> <port_
number>]

● -p—Do not print the output to the screen

● -i interval—Refresh from shared memory every interval seconds
● -t filename—Save the data from memory to the specified binary file
filename
● -f filename—Reads from a previously saved binary file, filename,
that was generated using the -t option instead of reading from
memory
● -s filename—Saves only the connection data from the data in
memory to an ASCII, comma-delimited file, filename
● -st filename—Saves only the target data from the data in memory
to an ASCII, comma-delimited file, filename
● -f filename1 -s filename2—Saves only the connection data from a
Options previously saved binary file, filename1, to an ASCII, comma-
delimited file, filename2
● -f filename1 -st filename2—Saves only the target data from a
previously saved binary file, filename1, to an ASCII, comma-
delimited file, filename2
● -IP address—Filters out the specified address in the IP address
field and prints only those entries. Specify more than one IP
address by separating them by a comma.
● -START mm/dd/yyyy hh:mm—Filters out any data prior to the
specified date and time
● -STOP mm/dd/yyyy hh:mm—Filters out any data after the
specified date and time
● -SERVER ip_address port_number—Connects DTStat to the

149 of 195
 specified IP address using the specified port number instead of to
the local machine

● DTStat -i 300
● DTStat -p -i 300 -t AlphaStats.sts
Examples
● DTStat -f AlphaStats.sts -s AlphaStats.csv -start 02/02/2007 09:25
● DTStat -server 206.31.4.51 1106

● This command is not case-sensitive.

● If no options are specified, DTStat will print the output to the screen
Notes at an interval of every one second.
● If the statistics are not changing, DTStat will discontinue writing
until statistics begin updating again.

Statistics
The following table identifies the Storage Mirroring Replicate statistics.

The categories you see will depend on the function of your server (source,
target, or both).
If you have multiple IP addresses connected to one target server, you will see
multiple Target sections for each IP address.
If you convert your statistics output to an ASCII, comma-delimited file using the
dtstat -s option, keep in mind the following differences.
● The statistic labels will be slightly different in the ASCII file than in the
Note: following table.
● The statistics will appear in a different order in the ASCII file than in the
following table.
● The statistics in the Target Category in the following table are not included
in the ASCII file.
● The Kernel statistic Target Open Handles is not included in the ASCII file.
● The ASCII file contains a Managed Pagefile Alloc statistic which is no
longer used.

150 of 195
 Category Statistic Description

The date and time that the snapshot was

taken. This is the date and time that each
statistic was logged. By default, these are
Date/Time
generated once a second, as long as there
Stamp
are statistics being generated. If
mirroring/replication is idle, then DTStat will
be idle as well.

The number of bytes currently allocated to

SystemAllocator Total Bytes
the system pagefile

The number of bytes currently allocated to

IQAllocator Total Bytes
the intermediate queue

Security Logins The number of successful login attempts

Security FailedLogins The number of failed login attempts

● 0—Source is not running

● 1—Source is running without the
Kernel SourceState replication driver
● 2—Source is running with the
replication driver

● 0—Target is not running

Kernel TargetState
● 1—Target is running

Date and time stamp indicating when the

Kernel Start Time
Storage Mirroring service was loaded

The number of replication operations

generated by the file system driver. An op is
a file system operation. Storage Mirroring
Replicate replicates data by sending the file
Kernel RepOpsGenerated
system operations across the network to the
target. RepOpsGenerated indicates the
number of file system operations that have
been generated by replication.

151 of 195
 Category Statistic Description

The number of replication bytes generated

by the file system driver. This is the number
of bytes generated during replication. In
other words, this is roughly the amount of
Kernel RepBytesGenerated
traffic being sent across the network that is
generated by replication. It does not take
into account TCP/IP overhead (headers and
such).

The number of mirror operations transmitted

to the target. Mirroring is completed by
transmitting the file system operations
necessary to generate the files on the
target. This statistic indicates the number of
Kernel MirOpsGenerated
file system operations that were transmitted
during the initial mirror. It will continue to
increase until the mirror is complete. Any
subsequent remirrors will reset this field to
zero and increment from there.

The number of mirror bytes transmitted to

the target. This is the number of bytes
generated during mirroring. In other words,
this is roughly the amount of traffic being
Kernel MirBytesGenerated sent across the network that is generated by
the mirror. It does not take into account
TCP/IP overhead (headers and such).
Again, any subsequent remirror will reset
this field to zero and increment from there.

The number of mirror operations that failed

Kernel FailedMirrorCount
due to an error reading the file from the disk

The number of replication operations that

Kernel FailedRepCount failed due to an error reading the file from
the disk

The number of activation code failures

when loading the source or target.
Kernel ActFailCount Activation codes can be bad for reasons
such as: expiration of evaluation codes,
duplicate codes, incorrect codes, etc.

152 of 195
 Category Statistic Description

The number of handles currently open on

Kernel TargetOpenHandles
the target

The amount of throttling calculated as a

Kernel DriverQueuePercent
percentage of the stop replicating limit

Target PeerAddress The IP address of the source machine

Target LocalAddress The IP address of the target machine.

The total number of operations received by

Target Ops Received this machine as a target since the Storage
Mirroring service was loaded

The total number of mirror operations

received by this machine as a target since
Target Mirror Ops Received the Storage Mirroring service was loaded.
This number does not reset to zero for
remirrors.

The number of retries performed before all

Target Retries
operations were completed

The number of operations skipped during a

difference mirror. During a difference mirror,
if Storage Mirroring Replicate detects that
Target OpsDropped
there have been no changes to a file, then it
will indicate the number of operations it did
not send for this file in this field.

The total number of operations that are left

Target Ops Remaining
in the target queue

The number of orphan files removed from

Target Orphan Files Removed
the target machine

Orphan Directories The number of orphan directories removed

Target
Removed from the target machine

The number of orphan bytes removed from

Target Orphan Bytes Removed
the target machine

The number of bytes currently in the system

Target Bytes In Target Queue
memory queue on the target

153 of 195
 Category Statistic Description

Bytes In Target Disk The number of bytes currently in the disk

Target
Queue queue on the target

The number of task commands that have

Target TasksSucceeded
succeeded on the target

The number of task commands that have

Target TasksFailed
failed on the target

The number of task commands that have

Target TasksIgnored
been ignored on the target

The number of automatic disconnects since

starting Storage Mirroring Replicate. Auto-
disconnects occur because the source no
longer sees the target This could be
because the connection between the two
has failed at some point or because the
Source autoDisConnects
target machine data is changing on the
source faster than the source can get the
data to the target. This field tracks the
number of times an auto-disconnect has
occurred since the Storage Mirroring
service was started.

The number of automatic reconnects since

starting Storage Mirroring Replicate. Auto-
reconnect occurs after a target machine is
Source autoReConnects back online. This field tracks the number of
times an auto-reconnect has happened
since the Storage Mirroring service was
started.

The last filename that had a replication

Source lastFileTouched
operation executed

Connection
conPeerAddress The IP address of the target machine

The time that this connection was

Connection connectTime
established

154 of 195
 Category Statistic Description

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
and has no scheduling restrictions
imposed on it at this time. (There may
be restrictions, but it is currently in a
state that allows it to transmit.)
● 2—Paused. This indicates a
connection that has been paused.
Connection conState ● 4—Scheduled. This indicates a
connection that is not currently
transmitting due to scheduling
restrictions (bandwidth limitations,
time frame limitations, and so on).
● 8—Error. This indicates a connection
that is not transmitting because
something has gone wrong (for
example, lost connection).
Only the Scheduled and Error states can
coexist. All other states are mutually
exclusive. Statistics will display a conState
of 12 when the connection is in both a
scheduled and an error state because this
is the sum of the two values (4 + 8).

The number of operations waiting to be

Connection conOpsInCmdQueue
executed on the target

The number of operations waiting in the

acknowledgement queue. Each operation
that is generated receives an
Connection conOpsInAckQueue acknowledgement from the target after that
operation has been received by the target.
This statistic indicates the number of
operations that have yet to receive

155 of 195
 Category Statistic Description

acknowledgement of receipt.

The number of replication operations

Connection conOpsInRepQueue currently waiting to be executed on the
target

The number of mirror operations currently

Connection conOpsInMirQueue
waiting to be executed on the target

The number of replication bytes remaining

Connection conBytesInRepQueue
to be transmitted to the target

The number of operations transmitted to the

target. This is the total number of operations
that Storage Mirroring Replicate has
Connection conOpsTx transmitted as a source. In other words, the
cumulative number of operations
transmitted by this source to all connected
targets.

The number of mirror bytes remaining to be

Connection conBytesInMirQueue
transmitted to the target

The number of bytes transmitted to the

target. This is the total number of bytes that
Storage Mirroring Replicate has transmitted
Connection conBytesTx
as a source. In other words, the cumulative
number of bytes transmitted by this source
to all connected targets.

The number of compressed bytes

Connection conBytesCompressedTx
transmitted to the target.

The number of operations received by the

target. The number of operations that the
Connection conOpsRx target for this connection (as indicated by
the IP address field) has received from this
source.

The number of bytes received by the target.

The number of bytes that the target for this
Connection conBytesRx
connection (as indicated by the IP address
field) has received from this source.

156 of 195
 Category Statistic Description

The number of operations resent because

Connection conResentOpCount
they were not acknowledged

The number of bytes in the source disk

Connection conBytesInDiskQueue
queue

The amount of bandwidth that may be used

Connection conBandwidthLimit
to transfer data

The number of bytes skipped during a

difference mirror. During a difference mirror,
if Storage Mirroring Replicate detects that
Connection conBytesSkipped
there have been no changes to a file, then it
will indicate the number of bytes it did not
send for this file in this field.

The number of mirror bytes remaining to be

Connection conMirrorBytesRemain
transmitted

The percentage of the mirror that has been

Connection conMirrorPercent completed. This field is determined if the
replication set size was calculated.

The number of task commands that have

Connection conTaskCmdsSubmitted
been submitted on the source

The number of task commands that have

Connection conTaskCmdsQueued
been queued on the source

The number of task commands that have

Connection conTasksSucceeded
succeeded on the source

The number of task commands that have

Connection conTasksFailed
failed on the source

The number of task commands that have

Connection conTasksIgnored
been ignored on the source

157 of 195
Performance Monitor
Performance Monitor is the Windows graphical tool for measuring performance. It
provides charting, alerting, and reporting capabilities that reflect both current activity and
ongoing logging. Storage Mirroring Replicate statistics are available through the
Performance Monitor.
● Monitoring Performance Monitor statistics
● Performance Monitor statistics

Monitoring Performance Monitor statistics

1. To access the Performance Monitor, select Start, Programs, Administrative
Tools, Performance.
2. Specify the data to monitor by right-clicking and selecting Add or using the Add
button on the toolbar.
3. Choose one of the following Storage Mirroring Replicate Performance Objects.
● Double-Take Connection
● Double-Take Kernel
● Double-Take Security
● Double-Take Source
● Double-Take Target
4. Select the statistics you want to monitor, and click Add.
For additional information and details on the Performance Monitor, see your Windows
reference guide.

Performance Monitor statistics

The following table identifies the Storage Mirroring Replicate Performance Monitor
statistics.

If you have multiple IP addresses connected to one target server, you will see
Note:
multiple Target statistic sections for each IP address.

Object Statistic Description

The amount of bandwidth that may be used to transfer

Connection Bandwidth Limit
data

Connection Bytes in disk The number of bytes in the source disk queue

158 of 195
 Object Statistic Description

queue

Bytes in
Connection The number of replication bytes in the source queue
replication queue

Bytes in mirror
Connection The number of mirror bytes in the source queue
queue

The number of bytes received by the target since the

Connection Bytes received
last Performance Monitor refresh

Connection Bytes transferred The number of bytes transmitted from the source

Compressed The number of compressed bytes transmitted from the

Connection
bytes transferred source

Operations in
The number of operations waiting in the source
Connection acknowledgement
acknowledgement queue
queue

Operations in The number of operations waiting in the source

Connection
command queue command queue

Operations in
Connection The number of mirror operations in the source queue
mirror queue

Operations in The number of replication operations in the source

Connection
replication queue queue

Operations The number of operations received by the target since

Connection
received the last Performance Monitor refresh

The number of operations re-sent since the last time

Connection Operations resent the Storage Mirroring service was restarted on the
source

Operations
Connection The number of operations transmitted from the source
transmitted

Task commands
Connection The number of task commands queued on the source
queued

Task commands The number of task commands submitted on the

Connection
submitted source

159 of 195
 Object Statistic Description

The number of task commands that have failed to

Connection Tasks failed
execute on the source

The number of task commands that have been

Connection Tasks ignored
ignored on the source

The number of task commands that have succeeded

Connection Tasks succeeded
on the source

The number of activation code failures when loading

Activation code
Kernel the source or target, since the last time the Storage
failures
Mirroring service was restarted on the source

Double-Take
The amount of system memory in use by the Storage
Kernel queue memory
Mirroring Replicate queue
usage

Driver Queue The amount of throttling calculated as a percentage of

Kernel
Percent the stop replicating limit

Failed mirror The number of mirror operations on the source that

Kernel
operations failed due to an error reading the file from the disk

Failed replication The number of replication operations on the source

Kernel
operations that failed due to an error reading the file from the disk

Mirror Kbytes The number of mirror kilobytes transmitted from the

Kernel
generated source

Mirror operations The number of mirror operations transmitted from the

Kernel
generated source

Open Target
Kernel The number of handles currently open on the target.
Handles

Replication The number of replication kilobytes generated on the

Kernel
Kbytes generated source by the file system driver

Replication
The number of replication operations generated on
Kernel operations
the source by the file system driver
generated

Number of failed login attempts since the last time the

Security Failed logins
Storage Mirroring service was restarted

160 of 195
 Object Statistic Description

Number of successful login attempts since the last

Security Successful logins
time the Storage Mirroring service was restarted

The number of automatic disconnects since the last

Source Auto disconnects time the Storage Mirroring service was restarted on
the source

The number of automatic reconnects since the last

Source Auto reconnects time the Storage Mirroring service was restarted on
the source

Bytes in Disk
Target The number of bytes in the target disk queue
Queue

The number of bytes in the system memory and disk

Target Bytes in Queue
queues

Mirror operations The number of mirror operations received on the

Target
received target

Operations
Target The number of operations received on the target
received

The number of operations dropped on the target since

Target Ops Dropped the last time the Storage Mirroring service was
restarted on the target

The number of operations on the targer remaining to

Target Ops Remaining
be applied

Target Orphan Bytes The number of orphan bytes removed from the target

Orphan The number of orphan directories removed from the

Target
Directories target

Target Orphan Files The number of orphan files removed from the target

The number of retries performed on the target since

Target Retries the last time the Storage Mirroringservice was
restarted on the target

The number of task commands that have failed on the

Target Tasks failed
target.

Target Tasks ignored The number of task commands that have been

161 of 195
 Object Statistic Description

ignored on the target

The number of task commands that have succeeded

Target Tasks succeeded
on the target

162 of 195
SNMP
SNMP, Simple Network Management Protocol, is the Internet's standard for remote
monitoring and management of hosts, routers and other nodes and devices on a
network. Storage Mirroring Replicate provides an SNMP sub-agent that can be
managed from an SNMP Management Console.
Storage Mirroring Replicate installs two components to work with SNMP.
● The sub-agent is a program that installs and runs on the same machine as Storage
Mirroring Replicate and gathers statistics, data, and traps. The sub-agent forwards
the information to the SNMP agent, which relays the information to the manager.
The Storage Mirroring Replicate SNMP sub-agent is included in the Storage
Mirroring Replicate installation program.
● A Storage Mirroring Replicate MIB file is placed on the administrator’s machine so
that the Management Console can interpret the data sent from the sub-agent. The
Storage Mirroring Replicate .mib file is dt.mib and meets SNMP standards.

Configuring SNMP on your server

SNMP must be installed on a server before Storage Mirroring Replicate in order for the
Storage Mirroring Replicate SNMP components to be added during the Storage
Mirroring Replicate installation. If SNMP is installed on a server after Storage Mirroring
Replicate is installed, run a repair install to install the SNMP components.
The Storage Mirroring Replicate .mib file will need to be loaded into your SNMP
Management Console. Depending on the type of console you are using, this process
might include compiling the .mib file. Reference your SNMP Management Console
documentation for additional information.

163 of 195
SNMP traps
The following table lists the Storage Mirroring Replicate SNMP traps.

Object
Trap Description
Type

Storage Mirroring Replicate has

Kernel dttrapKernelStarted
started

Storage Mirroring Replicate has

Kernel dttrapKernelStopped
stopped

The source cannot be started due to

License dttrapLicenseViolationStartingSource
a license violation

A Storage Mirroring Replicate serial

License dttrapLicenseViolationOnNetwork number conflict was identified on the
network

Storage Mirroring Replicate source

Source dttrapSourceStarted
component has started

Storage Mirroring Replicate source

Source dttrapSourceStopped
component has stopped

Storage Mirroring Replicate target

Target dttrapTargetStarted
component has started

Storage Mirroring Replicate target

Target dttrapTargetStopped
component has stopped

The source has requested a

Connection dttrapConnectionRequested
connection to the target

The target has received a connection

Connection dttrapConnectionRequestReceived
request from the source

The source to target connection has

Connection dttrapConnectionSucceeded
been established

The source to target connection has

Connection dttrapConnectionPause
paused

The source to target connection has

Connection dttrapConnectionResume
resumed

164 of 195
 Object
Trap Description
Type

The source to target connection was

Connection dttrapConnectionFailed
not successful

The source to target connection has

Connection dttrapConnectionLost
been disconnected

The Storage Mirroring Replicate

Connection dttrapMemoryLimitReached
memory pool limit has been reached

The memory pool usage is below the

Connection dttrapMemoryLimitRemedied
maximum limit specified

Auto-reconnect needs to make a new

Connection dttrapAutoReconnect
connection

A scheduled connection has been

Connection dttrapScheduledConnectStart
established

A scheduled end connection has

Connection dttrapScheduledConnectEnd been reached and the connection
has been disconnected

Auto-disconnect has forced the

Connection dttrapAutoDisconnectWriteQueue
queue to be written to disk

Auto-disconnect requested that the

Connection dttrapAutoDisconnectPauseTransmission source pause any operation (create,
modify, or delete) sending

Auto-disconnect has intentionally

Connection dttrapAutoDisconnectEndConnection
dropped the connection

Auto-disconnect forced Storage

Connection dttrapAutoDisconnectShutdown
Mirroring Replicate to shutdown

Replication dttrapReplicationStart Replication has started

Replication dttrapReplicationStop Replication has stopped

Mirroring dttrapMirrorStart Mirroring has started

Mirroring dttrapMirrorStop Mirroring has stopped

Mirroring dttrapMirrorPause Mirroring has paused

165 of 195
 Object
Trap Description
Type

Mirroring dttrapMirrorResume Mirroring has resumed

Mirroring dttrapMirrorEnd Mirroring has ended

Verification dttrapVerificationStart Verification has started

Verification dttrapVerificationEnd Verification has ended

Verification dttrapVerificationFailure Verification has failed

Restoration dttrapRestoreStarted Restoration has started

Restoration dttrapRestoreComplete Restoration is complete

Replication
dttrapRepSetModified Replication has been modified
Sets

Manual intervention is required

Failover dttrapFailoverConditionMet because failover has detected a
failed source machine

Failover dttrapFailoverInProgress Failover is occurring

Failover dttrapTargetFull The target is full

SNMP statistics
The following table lists the Storage Mirroring Replicate SNMP statistics.

Object
Statistic Description
Type

Time in seconds since Storage Mirroring

General dtUpTime
Replicate was last started

Amount of memory allocated from the Storage

General dtCurrentMemoryUsage
Mirroring Replicate memory pool

The number of mirror operations (create, modify,

General dtMirOpsGenerated or delete) that have been transmitted by the
mirroring process

The number of bytes that have been transmitted

General dtMirBytesGenerated
by the mirroring process

166 of 195
 Object
Statistic Description
Type

The number of operations (create, modify, or

General dtRepOpsGenerated delete) that have been transmitted by the
replication process

The number of bytes that have been transmitted

General dtRepBytesGenerated
by the replication process

The number of operations that failed to mirror

General dtFailedMirrorCount
because they could not be read on the source

The number of operations that failed to be

General dtFailedRepCount replicated because they could not be read on
the source

General dtActFailCount The number of activation code errors

General dtAutoDisCount The number of auto-disconnects

General dtAutoReCount The number of auto-reconnects

The amount of throttling calculated as a

General dtDriverQueuePercent
percentage of the stop replicating limit

● 0—Source is not running

● 1—Source is running without the
Source dtSourceState replication driver
● 2—Source is running with the replication
driver.

● 0—Target is not running

Target dtTargetState
● 1—Target is running

The number of file operations that have been

Target dtRetryCount
retried

The number of file operations that have failed

Target dtOpsDroppedCount
and will not be retried

Security dtLoginCount The number of successful logins

Security dtFailedLoginCount The number of unsuccessful logins

167 of 195
 Object
Statistic Description
Type

The number of active connections between

Connection dtConnectionCount
machines

The IP address of the connected machine. If at

Connection dtconIpAddress the source, then the IP address of the target. If at
the target, then the IP address of the source.

The duration of time since the connection was

Connection dtconConnectTime
first established

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 and
has no scheduling restrictions imposed on
it at this time. (There may be restrictions,
but it is currently in a state that allows it to
transmit.)
● 2—Paused. This indicates a connection
that has been paused.
Connection dtconState ● 4—Scheduled. This indicates a
connection that is not currently
transmitting due to scheduling restrictions
(bandwidth limitations, time frame
limitations, and so on).
● 8—Error. This indicates a connection that
is not transmitting because something has
gone wrong (for example, lost
connection).
Only the Scheduled and Error states can
coexist. All other states are mutually exclusive.
SNMP will display a dtconState of 12 when the
connection is in both a scheduled and an error
state because this is the sum of the two values
(4 + 8).

168 of 195
 Object
Statistic Description
Type

The number of operations (create, modify, or

Connection dtconOpsInCmdQueue
delete) in the retransmit queue on the source

The number of operations (create, modify, or

Connection dtconOpsInAckQueue delete) waiting for verification
acknowledgements from the target

The number of replication operations (create,

Connection dtconOpsInRepQueue
modify, or delete) in the queue

The number of mirror operations (create, modify,

Connection dtconOpsInMirQueue
or delete) in the queue

Connection dtconBytesInRepQueue The number of bytes in the replication queue

Connection dtconBytesInMirQueue The number of bytes in the mirror queue

The total number of operations (create, modify,

Connection dtconOpsTx
or delete) transmitted to the target

The total number of bytes transmitted to the

Connection dtconBytesTx
target

The total number of compressed bytes

Connection dtconBytesCompressedTx
transmitted to the target

The total number of operations (create, modify,

Connection dtconOpsRx
or delete) received from the target

The total number of bytes received from the

Connection dtconBytesRx
target

The number of operations that were resent

Connection dtconResentOpCount
because of acknowledgement errors

169 of 195
Error codes
The following table contains error codes that you may see in the various user interfaces
or in log files.

Error
Description
Code

Unknown error code (generated when a command failed but the failure is not
-1
linked to a pre-defined error code)

-101 Invalid parameter was supplied

-102 Command is not a valid or the syntax is incorrect

-103 Storage Mirroring Replicate source module is not loaded

-104 No Storage Mirroring Replicate source identified

-105 Storage Mirroring Replicate target module is not loaded

-106 Connection already established

-107 Connection does not exist

-108 Mirror currently active

-109 Server does not exist or could not be located

-110 Server is not responding

-111 Storage Mirroring Replicate is running

-112 Unknown connection error

-113 Mirror already active

-114 Date is invalid - valid format is mm/dd/yy

-115 Time is invalid - valid format is hh:mm

-116 Invalid option supplied

-117 Mirror is not paused

-118 Connection is not paused

-119 Connection does not exist

170 of 195
Error
Description
Code

-120 Connection already connected

-121 Mirror is not running

-122 Replication set exists

-123 Replication set does not exist

-124 No replication set has been selected

-125 Connection is replicating

-126 Connection is not replicating

-127 Replication set is enabled

-128 Schedule is not defined

-129 Replication set is changed

-130 Replication set is in use

-131 No Storage Mirroring Replicate target identified

-132 Memory is low

-133 Memory is sufficient

-134 Replication is pending

-135 Invalid option supplied

-136 Replication set rule does not exist

-137 Mirror queue is full

-138 Insufficient security access

-139 Schedule command is invalid

-140 Source path is invalid

-141 Replication set is not changed

-142 Insufficient source security access

-143 Invalid statistics file

171 of 195
Error
Description
Code

-144 Replication set not saved

-145 Connection failed

-146 Cleaner option is not enabled

-147 Target mirror capacity high threshold is met

-148 Target mirror capacity low threshold is met

-149 New option applied

-150 Target is restarted

-151 Replication is out of memory

-152 Write access is blocked on the volume

This error code could be one of two errors. 1) Compression level is not
-153
supported, or server does not support compression 2) Transmission is paused

-154 Transmission is active

-155 Target does not support the command

Command conversion to accommodate a different Storage Mirroring Replicate

-156
version has failed

-157 Incompatible source and target Storage Mirroring Replicate 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

-161 Operation 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

172 of 195
Error
Description
Code

-167 Restore required state is unknown

-168 Not a valid failover source

-169 Failover 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

-176 Memory-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

-188 Schedule is resumed

-189 Target state has changed

-190 Target name has changed

173 of 195
Error
Description
Code

-201 Monitor name exists

-202 Monitor name does not exist

-203 Monitor configuration exists

-204 Monitor configuration does not exist

-205 Monitor configuration is in use

-206 Monitor 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 being monitored

-212 Failback is in progress

-213 IP address placeholders on the target are unavailable

-214 Target NIC was not found

-215 Source module 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

174 of 195
Error
Description
Code

-225 Invalid path

-226 Kernel module is not loaded

-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 and WMI

-2206 E-mail notification requires Internet Explorer version 5.0

-2207 Error sending e-mail

-2208 Error sending test e-mail

-2209 WMI error connecting to e-mail server

-2210 E-mail notification requires WMI

-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

-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

175 of 195
Error
Description
Code

-2303 Bandwidth limit not found

-2304 Bandwidth limit day is invalid

-2305 Bandwidth limit lable is invalid

-2401 Snapshot module is not loaded

-2402 Error reading the snapshot .dll

-2403 Snapshot not found

-2404 No snapshot connections found

-2501 Full-server functionality is disabled

-2502 No full-server interface available

176 of 195
Cargo archiving
Before you begin archiving, you must configure specific archiving security. Once that is
complete, you may want to generate a preview report to help you plan archiving and
fine-tune your archive settings. When you are ready to begin archiving, you can archive
files manually or you can schedule archiving for periodic intervals.
● Running an archive preview report
● Manually archiving data
● Archiving data on a schedule
● Choosing a storage location for archived files on the repository server
● Recalling archived files

The archiving functionality is currently only available in the Replication

Console. In the future, the archiving functionality will be made available in the
Storage Mirroring Replicate console. By default, the Replication Console is
installed with the Storage Mirroring Replicate installation. To open the console,
Note: select Start, Programs, Storage Mirroring, Storage Mirroring Replication
Console.
Archiving is not compatible with TimeData continuous data protection. If you
use one, do not use the other.

177 of 195
Configuring archiving security
Before you can use Storage Mirroring Replicate archiving, you must establish a specific
security configuration. This is a six step process.
1. Confirm Storage Mirroring Replicate is installed on both the source and repository
server.
2. Create a new service account. (A service account is a user account that is created
explicitly to provide security context for a service.) Follow steps a through f to
create a new service account.
a. From Active Directory Users and Computers, create a new user.
b. Enter a descriptive name for the first and last name and modify the full name
as desired.
c. Specify a User logon name.
d. Specify and confirm a Password for the account.
e. Specify your password settings. The settings you select may be dependent
on your company’s security policies. Keep in mind the following caveats for
password settings for a service account.
● User must change password at next logon—The HP
recommendation is to disable this setting. The Storage Mirroring Recall
service will not be able to start if this option is enabled because the
service will be waiting on the required logon change.
● User cannot change password—The HP recommendation is to
enable this setting. If this setting is enabled, you will not have to worry
about updating the credentials in the Storage Mirroring Recall service.
If you cannot select this option because of company security policies
and the password on the account is changed, the Storage Mirroring
Recall service will no longer have valid credentials. File recalls will not
function until the Storage Mirroring Recall service credentials are
updated to the new password.
● Password never expires—The HP recommendation is to enable this
setting. If this setting is enabled, you will not have to worry about
updating the credentials in the Storage Mirroring Recall service. If you
cannot select this option because of company security policies and the
password on the account expires, the Storage Mirroring Recall service
will no longer have valid credentials. File recalls will not function until
the account is reset and the Storage Mirroring Recall service
credentials are updated.
● Account is disabled—The HP recommendation is to disable this
setting. Because the word disable is part of the option name, the

178 of 195
 recommendation can be confusing. You want to enable the account,
which means this option should not have a checkmark. If the option
does have a checkmark, meaning the account would be disabled, file
recalls will not function.
f. Finish the account creation wizard.
3. Add the new service account to the local Administrators group on the source and
repository server.
4. Add the new service account to the local Double-Take Recall group on the source
and repository server.
5. Modify the Storage Mirroring Recall service on the source and repository server to
use the new service account.
a. From the services applet (Administrative Tools, Services) right-click the
Storage Mirroring Recall service and select Properties.
b. On the Log On tab, select This account and specify the new user and the
password.
c. On the General tab, select Startup type, and select Automatic.
d. Click OK to save the changes.
6. Start the Storage Mirroring Recall service on the source and repository server. If
the service is already running, you must stop and restart it so that it uses the user
account and group modifications you just made.

If you have an active Storage Mirroring Replicate job, you can validate
your security configuration using the Replication Console.
1. Open the Replication Console by selecting Start, Programs,
Storage Mirroring, Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication
Console to log on to it.
3. With the source highlighted in the left pane, locate in the right pane
the Storage Mirroring protection job in the Replication Set column.
Note The name will be created from the source and repository server
names and the keyword Protection or Data Protection.
4. Right-click the protection job in the right pane of the Replication
Console and select Connection Manager.
5. Select the Archive Options tab.
6. Click Validate.
The validation checks to see if the correct service is running and if it has
an account in the correct security group. It also confirms if the repository
server has shared the archive bin correctly and if network communications

179 of 195
are functioning properly. Any success or failure messages will be included
in the Storage Mirroring Replicate log file on the source.

180 of 195
Running an archive preview report
To help you plan archiving and fine-tune your archive settings, you can generate a
preview report. The archiving preview report does not actually archive any data but
reports how much data would be archived based on the settings you select.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. With the source highlighted in the left pane, locate in the right pane the Storage
Mirroring protection job in the Replication Set column. The name will be created
from the source and repository server names and the keyword Protection or Data
Protection.
4. Right-click the protection job in the right pane of the Replication Console and
select Archiving, Preview.
5. Select the archiving options that you would like to perform.

● Archive files inactive for—This option specifies the age in days, based on
the last accessed time, of the files that you would want archived. Any file
older than the age specified will be included in the preview report.
● Archive files when size meets or exceeds—This option specifies the size,
in KB, of the files that you want archived. Any file equal to or larger than the
specified size will be archived.
6. If desired, specify if you want to calculate the size of the replication set (the
protection job) prior to starting the archive. If enabled, this will display the archiving

181 of 195
 percentage complete in the Mirror Status column of the Replication Console.
7. Click Preview to generate the report. While the preview report is being generated,
you will see the Mirror Status column change to Archiving. When the preview
report is complete, the Mirror Status column will change back to Idle.
8. After the preview report has been generated, locate and open the file from the
location where Storage Mirroring Replicate is installed. The file name uses the
name of the protection job followed by ArchivePreview.txt. For example, if your
protection job is called alpha to beta data protection, then the preview report would
be called alpha to beta data protection ArchivePreview.txt.

If you want to change the file name used to generate the preview report,
right-click the server from the left pane of the Replication Console and
Note select Properties. On the Logging tab, modify the Archive Preview
Filename. On this tab, you can also modify the maximum size of the
preview report.

9. Review the preview report. At the top of the report, you will find overview
information, including the archive criteria applied to the preview. In the center of the
report will be a list of all of the files that would be archived based on the selected
criteria. At the bottom of the report, you will find summary statistics.
10. If desired, repeat the preview report using different archiving criteria. The preview
report is replaced each time a preview is run, so rename the file to a different file
name if you want to keep the report.

182 of 195
Manually archiving data
Archiving can be performed manually anytime after an initial mirror and when another
mirror is not in progress. You can archive individual files and folders, or you can archive
groups of files based on archive criteria.

Archiving files individually

To archive files or folders individually, use the following steps.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. Expand the tree under the source and locate the Storage Mirroring protection job.
The name will be created from the source and repository server names and the
keyword Protection or Data Protection.
4. Expand the tree under the job name.
5. Highlight the root of the volume under the job name that contains the files or folders
that you want to archive.
6. In the right pane of the Replication Console, drill down through the volume to
locate the files or folders that you want to archive.
7. Right-click on the files or folders and select Archive. The right-click menu will not
be available if the files or folders are not part of your protection job.

Archiving groups of files based on criteria

To archive groups of files based on archive criteria, use the following steps.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. With the source highlighted in the left pane, locate in the right pane the Storage
Mirroring protection job in the Replication Set column. The name will be created
from the source and repository server names and the keyword Protection or Data
Protection.
4. Right-click the protection job in the right pane of the Replication Console and
select Archiving, Preview.
5. Select the archiving options that you would like to perform. Both archiving criteria
must be met for a file to be archived.

183 of 195
 ● Archive files inactive for—This option specifies the age in days, based on
the last accessed time, of the files that you want archived. Any file older than
the age specified will be archived.
● Archive files when size meets or exceeds—This option specifies the size,
in KB, of the files that you want archived. Any file equal to or larger than the
specified size will be archived.
6. If desired, specify if you want to calculate the size of the replication set (the
protection job) prior to starting the archive. If enabled, this will display the archiving
percentage complete in the Mirror Status column in the right pane of the
Replication Console.
7. Click Archive to start the process.
While the archiving is running, you will see the Mirror Status column in the Replication
Console change to Archiving. During this time, you can pause or resume archiving by
right-clicking the protection job and selecting Archiving, Pause or Archiving, Resume.
If you need to stop the archiving process, select Archiving, Stop.

184 of 195
Archiving data on a schedule
Archiving can be scheduled to occur automatically at periodic intervals.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. With the source highlighted in the left pane, locate in the right pane the Storage
Mirroring protection job in the Replication Set column. The name will be created
from the source and repository server names and the keyword Protection or Data
Protection.
4. Right-click the protection job in the right pane of the Replication Console and
select Connection Manager.
5. Select the Archive Schedule tab.

6. To enable scheduled archiving, enable Automatically run archiving tasks on a

schedule.

185 of 195
 7. Specify the criteria that you want to apply to your protection job. All Archiving
Criteria must be met at the time the scheduled archive is initiated for a file to be
archived.
● Archive files when disk usage meets or exceeds—This option is a first
level filter. If disk usage exceeds the specified percentage, Storage Mirroring
Replicate will check the remaining criteria to determine if any files should be
archived. If disk usage is not above the specified percentage, no archiving
will occur.
● Archive files inactive for—This option is a second level filter. It specifies the
age in days, based on the last accessed time, of the files that you want
archived. If disk usage has been exceeded, any file older than the age
specified will be archived.
● Archive files when size meets or exceeds—This option is also a second
level filter. It specifies the size, in KB, of the files that you want archived. Any
file equal to or larger than the specified size will be archived.
6. Specify the archiving schedule that you want to use. Specify the Start time and the
days of the week to run the archiving process.
7. Click OK to save the settings.
When the archive process is initiated by the schedule, the Mirror Status column in the
right pane of the Replication Console will change to Archiving.

If you disable the scheduled archive after it has already archived files, the
archived files will remain as link files on the source until they are recalled. No
Note:
additional files will be archived unless you enable the schedule again or
manually initiate an archive.

186 of 195
Choosing a storage location for archived files on the
repository server
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. With the source highlighted in the left pane, locate in the right pane the Storage
Mirroring protection job in the Replication Set column. The name will be created
from the source and repository server names and the keyword Protection or Data
Protection.
4. Right-click the protection job in the right pane of the Replication Console and
select Connection Manager.
5. Select the Archive Options tab.

6. Select your Archive Bin Location. You have the choice of putting your archived
files on the repository server on the same volume location as they are on the
source, or you can place all of the archived files from all volumes on the source on

187 of 195
 one volume on the repository server. Specify One Per Volume to use the same
volume structure on the source and repository server. Specify Centralized to
Volume and specify a volume to use one volume on the repository server for
archived files from all volumes on the source.
7. Click OK to save the settings.

188 of 195
Recalling archived files
When a file has been archived, the link file is still accessible on the source. The link file
has an offline file attribute associated with it. When an end-user attempts to access the
link file, the contents of the file are recalled from the repository server back to the source.
The file opens to the end-user as if it had always been fully on the source.

If a link file is moved to a different volume on the source, the file will be recalled
Note: and moved. If a link file is moved within the same volume on the source, the file
is not recalled, only moved.

There may be times when you want to recall some or all of the files from the repository
server back to the source. For example, you should recall all of the files before changing
to a new repository server to protect your source or if you want to rearchive your files
using different archive settings.

Recalling files individually

To recall files or folders individually, use the following steps.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. Expand the tree under the source and locate the Storage Mirroring protection job.
The name will be created from the source and repository server names and the
keyword Protection or Data Protection.
4. Expand the tree under the job name.
5. Highlight the root of the volume under the job name that contains the files or folders
that you want to archive.
6. In the right pane of the Replication Console, drill down through the volume to
locate the files or folders that you want to recall.
7. Right-click on the files or folders and select Recall. The right-click menu will not be
available if the files or folders are not part of your protection job.

Recalling all files

To recall all of the files from the repository server, use the following steps.
1. Open the Replication Console by selecting Start, Programs, Storage Mirroring,
Storage Mirroring Replication Console.

189 of 195
2. Double-click your source machine in the left pane of the Replication Console to log
on to it.
3. With the source highlighted in the left pane, locate in the right pane the Storage
Mirroring protection job in the Replication Set column. The name will be created
from the source and repository server names and the keyword Protection or Data
Protection.
4. Right-click the protection job in the right pane of the Replication Console and
select Archiving, Recall All.
5. If desired, specify if you want to calculate the size of the replication set (the
protection job) prior to starting the recall. If enabled, this will display the recall
percentage complete in the Mirror Status column in the right pane of the
Replication Console.
6. Click Recall All Files to begin the recall.

190 of 195
Using firewalls
Storage Mirroring Replicate can be used over a wide area network (WAN) through
firewalls, but it does not support Network Address Translation (NAT) configurations.
If your servers are on opposite sides of a firewall, you will need to configure your
hardware to accommodate Storage Mirroring Replicate communications. You must have
the hardware already in place and know how to configure the hardware ports. If you do
not, see the reference manual for your hardware.

191 of 195
Storage Mirroring Replicate ports
Storage Mirroring Replicate port information is stored in configuration files. By default,
ports 80, 6320, 6330, and 6340 are used. If you are using TimeData continuous data
protection, the default ports are 8080, 17001, 17101, 17201, and 17301. If desired you
can modify some of these ports. However, not all of the ports can be modified.
If you have to modify which ports are used, you will have to modify two configuration
files. Be careful when modifying these configuration files. If you modify them incorrectly,
Storage Mirroring Replicate may no longer work correctly.
1. Open the file JobMgr.dll.config in your Storage Mirroring Replicate installation
directory. By default, this is \Program Files\StorageWorks\Storage Mirroring. You
may need to associate the .config file extension with Notepad or another text
editor.
2. Locate the following lines near the top of the configuration file.
<add key="IdentificationPort" value="6320"/>
<add key="FallbackIdentificationPort" value="1100"/>
<add key="LivewirePort" value ="6340"/>
<add key="VRAPort" value="6330"/>
<add key="TimeDataWebServicePort" value="8080"/>
3. Change the port numbers as necessary. Do not change any other information.
4. Save the configuration file.
5. Repeat steps 1 through 4 with the file BackupConsole.exe.config, using the same
port numbers for each key as you used in the JobMgr.dll.config file.
6. Repeat steps 1 through 5 for each Storage Mirroring Replicate server. The ports
must match between all Storage Mirroring Replicate servers and clients.
7. If you changed the IdentificationPort in the configuration files, you must also
change a port in the Replication Console.
a. Select Start, Programs, Storage Mirroring , Storage Mirroring Replication
Console.
b. Locate your server in the server tree in the left pane of the Replication
Console.

If your server is not listed, select Insert, Server. Type the machine name
Note:
or IP address and click OK.

c. Double-click the server to log on to it.

192 of 195
 d. Right-click the server in the left pane of the Replication Console and select
Properties.
e. On the Network tab, modify the Communications Port to match the
IdentificationPort in the configuration files.
f. Click OK.
g. Repeat steps b through f for all of your Storage Mirroring Replicate servers.
All of your Storage Mirroring Replicate servers and clients must have the same port
configuration.

193 of 195
Microsoft Windows ports
Storage Mirroring Replicate will use WMI (Windows Management Instrumentation)
which uses RPC (Remote Procedure Call). By default, RPC will use ports at random
above 1024, and these ports must be open on your firewall. RPC ports can be
configured to a specific range by specific registry changes and a reboot. See the
Microsoft Knowledge Base article 154596 for instructions.
Storage Mirroring Replicate also relies on other Microsoft Windows ports.
● Microsoft File Share uses ports 135 through 139 for TCP and UDP
communications.
● Microsoft Directory uses port 445 for TCP and UDP communications.
These ports must be open on your firewall. Check your Microsoft documentation if you
need to modify these ports.

194 of 195
Hardware ports
You need to configure your hardware so that all of the above ports for both Storage
Mirroring Replicate and Microsoft Windows are open. Since communication occurs bi-
directionally, make sure you configure both incoming and outgoing traffic.
There are many types of hardware on the market, and each can be configured differently.
See your hardware reference manual for instructions on setting up your particular router.

195 of 195