HP StorageWorks Storage Mirroring Replicate Users Guide HP Part Number: T5437-96023 Published: November 2010
© Copyright 1996-2010 Hewlett-Packard Development Company, L.P. and Double-Take Software, Inc. All rights reserved. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Storage Mirroring Replicate overview 6 TimeData continuous data protection 8 Ontrack PowerControls 9 Cargo archiving 10 Atom file-level deduplication 11 Storage Mirroring Replicate requirements 12 Source server requirements 14 Repository server requirements 15 Recovery server requirements 17 TimeData requirements 21 Ontrack PowerControls requirements 22 Cargo requirements 23 Atom requirements 25 Console requirements 25 Replication capabilities 26 Installation
Clearing console security credentials Source protection 49 50 Protecting your source 50 Optional protection settings 57 Compressing data for transmission for a protection job 58 Limiting bandwidth for a protection job 59 Routing transmission for a protection job 61 E-mailing server event messages 62 Enabling file-level deduplication 64 Data on the repository server 66 Viewing and retrieving data from snapshots or from a TimeData point in time 67 Viewing and retrieving Exchange data 70
Monitoring a job through the Storage Mirroring Replicate console 110 Overview status information 110 Detailed status information 112 Monitor page toolbar 116 Monitoring log files 119 Monitoring event messages 120 Event messages Statistics 121 148 Viewing the statistics file 149 Statistics 151 Performance Monitor 158 Monitoring Performance Monitor statistics 159 Performance Monitor statistics 160 SNMP 165 Configuring SNMP on your server 166 SNMP traps 167 SNMP statistics 170 E
Repository server management 194 Monitoring a repository server 195 Managing a repository server 196 Setting deduplication options 197 Performing deduplication management tasks 199 Using the AtomAdmin utility 201 Scanning the storage bin to remove unused content 203 Restoring a storage bin to a new drive 203 Validating the Atom database or recovering from an inconsistent Atom database 204 Recovering from a corrupted Atom database 204 Using firewalls 205 Storage Mirroring Replicate port
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.
Storage Mirroring Replicate also provides features that enhance or extend the benefits of disk-to-disk protection. l l l l 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.
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.
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.
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.
Atom file-level deduplication The Atom deduplication feature of Storage Mirroring Replicate provides the ability to deduplicate protected data on the repository server. Deduplication is the process of finding duplicate files within a data set and storing those files only once to reduce storage consumption.
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. l l l l l l l l 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).
l Workgroups or multiple forests—If you want to use Storage Mirroring Replicate in a workgroup or multiple forest, you will need to create an account with the same name and credentials on all servers. Use that account like you would an Active Directory account. In addition to the server and feature requirements, review the Replication capabilities to understand the type of data that Storage Mirroring Replicate protects.
Source server requirements This is the server that contains the data you will be protecting. l Operating system—Storage Mirroring Replicate can protect a physical or virtual source server running any of the following operating system editions. l l l l l 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.
Repository server requirements This is the server that will be protecting your source server(s). l Operating system—The repository server can be a physical or virtual server running any of the following operating system editions.
l l l l 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—Microsoft .NET Framework version 3.5 Service Pack 1 is required on the repository server. This version is not included in the .
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. l Operating system—You have several options for your recovery server operating system.
Hyper-V Server 2008 R2 or Server Core 2008 R2 with the Hyper-V role enabled. (Hyper-V Server 2008 and Server Core 2008 are not supported.) l l l If you are using Hyper-V Integration Services and your source is running Windows 2003, the source must have Service Pack 2 or later. The virtual machines cannot use raw, pass-through, or differencing disks.
original source. Since the virtual recovery appliance maintains its own identity, it can be reused for additional recoveries.) l l l l l l l l l The virtual recovery appliance must have the same or newer operating system than the source (not including service pack level). The virtual recovery appliance must have Storage Mirroring Replicate installed and licensed on it.
via a web connection during the Storage Mirroring Replicate installation, or from a copy you have obtained manually from the Microsoft web site. l Network protocols—Your servers must use TCP/IP with static IP addressing.
TimeData requirements In addition to the repository server requirements, the following requirements apply to the TimeData continuous data protection feature. l l l 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.
Ontrack PowerControls requirements In addition to the repository server requirements, the following requirements apply to the Ontrack PowerControls feature. l l l l Exchange versions—Ontrack PowerControls supports recovery from the following versions of Exchange. l Exchange Server 5.5 l Exchange Server 2000 l Exchange Server 2003 l Exchange Server 2007 Exchange servers—Ontrack PowerControls can recover from an unlimited number of Exchange servers.
Cargo requirements In addition to the source and repository server requirements, the following requirements apply to the Cargo archiving feature. l Operating system and file system—The following operating system and file system requirements apply to archiving. l l l l l l l l 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.
in mind that your anti-virus software may refer to archived files differently, for example, offline, migrated, or sparse files. l Cargo functionality—Review the following requirements, limitations, and informational notes before using the archiving feature. l l l l l l l l l Archiving supports a one-to-one or many-to-one source to repository server configuration.
Atom requirements In addition to the repository server requirements, the only other requirement that applies to the Atom feature is the file system. NTFS is the only supported file system. Do no use FATx file systems on the repository server. Console requirements The Storage Mirroring Replicate console is used to manage your Storage Mirroring Replicate servers. l l Operating system—The Storage Mirroring Replicate console can be run from a source or repository server.
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 target.
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. a. Alternate data streams are not included in the replication set size calculation. Therefore, you may see the mirror process at 99-100% complete while mirroring continues. b. The number of files and directories reported to be mirrored will be incorrect.
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.
restoration is complete and replication will continue from the target to the source. e. If you have restored your data before starting the failback process, make sure the restoration process does not have pending transactions and is complete before starting failback. If you are restoring your data after the failback the process has completed, users will not be accessing the data once failback occurs, so there are no opportunities for pending transactions. 8.
Installation Review the Storage Mirroring Replicate requirements and Installation and upgrade notes before beginning your installation. You have the following installation options available. l l l l l l Installing or upgrading Storage Mirroring Replicate—Use these instructions to install or upgrade Storage Mirroring Replicate using the installation wizard.
Installation and upgrade notes Review the following installation and upgrade notes before beginning your installation or upgrade. l l l l l 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.
l 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.
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. l l CD—Load the Storage Mirroring Replicate CD into the local CD-ROM drive. If auto-run is enabled, the installation program will start automatically.
source, repository server, or recovery server. The server requires an activation code for the service to run. 7. If desired, specify where the Storage Mirroring Replicate files will be installed. 8. Click Next to continue. 9. 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. Enter your code and click Add. 10.
configured to use should be less than the amount of physical memory on the system to prevent low memory conditions. 14. 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. Click Next to continue. 15.
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.
DTACTIVATIONCODE=123456789012345678901234 DOUBLETAKEFOLDER="C:\Program Files\Storage Works\Storage Mirroring" QMEMORYBUFFERMAX=128 DISKQUEUEFOLDER="C:\Program Files\Storage Works\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.
QMemoryBufferMax Any integer representing the amount of system memory, in MB, to use for memory-based queuing DiskQueueFolder Any valid path to the location of the disk-based queue.
Installing or upgrading automatically to a local machine 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.
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.
Installing or upgrading 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.
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.
Installing and configuring Ontrack PowerControls 1. Depending on your Storage Mirroring Replicate installation selections, the Ontrack PowerControls 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 Ontrack PowerControls installation program using the appropriate instructions, depending on your media source.
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. l l l Evaluation—An evaluation license has an expiration date built into the activation code.
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.
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, 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.
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 jobs 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. l l l l Server—To import a protection job (source to repository server), specify the name of the repository server.
5. Click Finish to complete the import. The Monitor jobs page will automatically appear with the imported job.
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.
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 fullserver and data protection. At the end of the protection workflow, you will have an opportunity to configure optional protection settings for your protection job.
l l l l 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.
l l 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 or selected data. 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.
l Snapshots—A snapshot is an image of data taken at a single point in time. Snapshots allow you to view files and folders as they existed at points of time in the past, so you can, for example, recover from cases where corrupted source data was replicated to the target. For more information about snapshots, see the Snapshots section in the Storage Mirroring Recover User's Guide. l l Enable scheduled snapshots—By default, periodic snapshots are disabled.
l l l 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 date and time, select this option and specify the date and time parameters. Continuous Data Protection—Continuous data protection provides access to data from any point in time. TimeData records every change made to the source image.
l l Event log file path—Enter the path where you want to store the event log file or click Browse to select the folder from a directory drill-down list. Keep in mind that you need to select a location with sufficient space. Keep CDP data for—By default, TimeData will maintain changes for seven days, which is the recommended retention period. If desired, modify the number of days to store data changes. If you increase the number of days, keep in mind space limitations on the repository server.
the selections you made, click Back to return to the previous pages. If you want to configure the optional settings, click Configure. 15. Once you have completed your configuration, click Finish to establish your source protection. The Monitor jobs page will automatically appear with the new job.
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 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.
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. l l l Do not limit bandwidth—Storage Mirroring Replicate will transmit data using 100% bandwidth availability.
Saturday and Sunday, or Everyday to have the limiting repeat on all days of the week. l Start time—Enter the time to begin bandwidth limiting. l End time—Enter the time to end bandwidth limiting. l Preset Bandwidth—Select a bandwidth limit rate from the common bandwidth limit values. If you want to specify your own bandwidth limit, select Custom (user entered), then enter the bandwidth in the Limit field. The minimum limit should be 28 Kbps. Click OK to save the new schedule.
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.
E-mailing server event messages E-mail notification sends specific Storage Mirroring Replicate events to user-defined email 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. l l l l Server—Select the server that you want to configure e-mail notifications for. E-mail notification settings apply to all jobs for a server.
Note: TimeData events do not support authenticated SMTP notification methods. Check the TimeData log files for TimeData events if you are using authenticated SMTP. l l l l l 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.
Enabling file-level deduplication File-level deduplication allows you detect and reduce storage of redundant files on the repository server. l Deduplicate—Select the checkbox in the Deduplicate column for those volumes that you want to deduplicate redundant files. The system volume, with the boot partition, will be unavailable for deduplication. Note: Some files (for example, .log, .temp, .
NTFS change journal already exists, the existing change journal will be used with the size and growth values originally specified. l Storage bin location—Specify the location where the single copy of the redundant files will be stored. Do not select the system volume. Note: If you set the storage bin location during another protection setup, the option to set a storage bin location will not be available. Instead, you will need to move the storage bin, if desired.
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. l l l Live data—The live data can easily be viewed and retrieved at any time on the repository server using standard file system tools like Windows Explorer.
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). l l l l 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.
l l l 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.
are not completing this task from the repository server, the data from the image and 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.
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.
Deleting point-in-time snapshots Use the following instructions to delete the point-in-time snapshots from the repository server. Keep in mind, if you delete a snapshot, you will be unable to use it for future recoveries. 1. From a command prompt, run the vssadmin list shadows command to identify the snapshot you want to delete. The snapshot will have a GUID (globally unique identifier) and a creation date and time. Make a note of the GUID.
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 an 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.
Installing Storage Mirroring Replicate on the recovery server 1. Select Tools, Prepare Recovery Server. 2. Specify the recovery server information. l l l l Server—Specify the name of the recovery server. User name—Specify a user that has local administrator, WMI, and administrative file share (for example, C$) 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.
Recovering an entire server to an existing physical or virtual machine 1. There are two ways to begin the recovery process. l l Click Recover data 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.
l l l 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.
domain controller in your network, you must specify a local account in the local administrators group on the recovery server. l l 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.
l l 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.
l l l 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.
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. l 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.
server. Note: Because the Windows product activation is dependent on hardware, you may need to reactivate your Windows registration after recovery. Follow the on-screen prompts to complete the reactivation.
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.
Recovery steps 1. There are two ways to begin the recovery process. l l Click Recover data 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.
l l l 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.
l l l l l Local administrator on the original source and the virtual recovery appliance (the existing virtual machine that will be used to create the new virtual machine) Member of the Double-Take Admin security group on the original source and the virtual recovery appliance (the existing virtual machine that will be used to create the new virtual machine) Full permissions and file sharing access for Windows Management Instrumentation (WMI) Password—Specify the password associated with the User name y
l l l l 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. Virtual Disk Type—For each volume you are protecting, specify the type of disk, Dynamic or Fixed, that will be created on the virtual machine. 9. Click Next to continue. 10.
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. l l l l l Server—Specify the name of the existing virtual machine on the ESX server.
l l l l 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.
l l l 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.
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 Activity will change to Recovery Paused (unless you disabled the wait for user intervention option, in which case the recovery server will reboot immediately).
Recovering an entire server to an automatically provisioned virtual machine on Hyper-V 1. There are two ways to begin the recovery process. l l 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.
l l l 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.
l l 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. 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.
l l Virtual Disk Type—For each volume you are protecting, specify the type of disk, Dynamic or Fixed, that will be created on the virtual machine. Controller Type—Specify the type of controller, IDE or SCSI, to be used for each volume. Note: The system volume must be an IDE controller. In addition, up to two more volumes can be attached to an IDE controller. If you are protecting more than three volumes on the source, you will need to install the Hyper-V Integration Components to acquire a SCSI device.
l l l l l 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.
l Limit the processor features that this virtual machine can use— Select this option to allow Hyper-V live migrations between cluster nodes with different processor versions. The target must be running Windows 2008 R2, have at least one cluster shared volume, and be configured to be a node in the cluster. Note: If the source is running Windows 2008 or later, the SAN policy must be set to Online. See your Microsoft documentation for more information on this policy. 13. Click Next to continue. 14.
l l l 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.
Recovering data to an existing physical or virtual machine 1. There are two ways to begin the recovery process. l l 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.
l l l 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.
domain controller in your network, you must specify a local account in the local administrators group on the recovery server. l l 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.
l l l 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.
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.
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 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.
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. l l l Do not limit bandwidth—Storage Mirroring Replicate will transmit data using 100% bandwidth availability.
Saturday and Sunday, or Everyday to have the limiting repeat on all days of the week. l Start time—Enter the time to begin bandwidth limiting. l End time—Enter the time to end bandwidth limiting. l Preset Bandwidth—Select a bandwidth limit rate from the common bandwidth limit values. If you want to specify your own bandwidth limit, select Custom (user entered), then enter the bandwidth in the Limit field. The minimum limit should be 28 Kbps. Click OK to save the new schedule.
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.
E-mailing server event messages E-mail notification sends specific Storage Mirroring Replicate events to user-defined email 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. l l l l Server—Select the server that you want to configure e-mail notifications for. E-mail notification settings apply to all jobs for a server.
Note: TimeData events do not support authenticated SMTP notification methods. Check the TimeData log files for TimeData events if you are using authenticated SMTP. l l l l l 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.
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 Once you have a job established or imported, you can easily monitor the status of the job from the Monitor jobs page. When viewing the Monitor jobs 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.
Status 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. You can also view the Storage Mirroring log file on the server for additional information about processing on that machine. Source Source indicates which server is transmitting mirror and replication data.
l 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. Time Remaining When mirroring, this is the estimated time remaining to complete the mirror. For various reasons, this calculation is an estimate.
If the Job Status is Communication Error, the issue 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 Update credentials toolbar button.
server. l l l 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 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.
l Idle—There is no data to mirror. l Paused—The mirror is paused. l Stopped—The mirror is stopped. l Unknown—The console is trying or unable to determine the mirror status. Mirror statistics, Mirror percent complete This is the estimated percentage of the mirror that is complete. For various reasons, this calculation is an estimate.
this statistic will be the same as Bytes sent. Replication statistics, Bytes queued This is the total amount of replication data that is in queue on the source. Monitor page toolbar The Monitor page has its own toolbar buttons for job and monitoring controls. New activity The large shield icon on the far left of the toolbar opens a small menu that lets you select an action to perform. Select Protect data or Recover data.
success or failure of the snapshot. Recover The life preserver icon starts and resumes the recovery process. Updated credentials 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 changes after a job has been started, Storage Mirroring Replicate will attempt to update the credentials it is using. If the automatic update is not successful, the monitor page will report Invalid credentials.
Displayed Total 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.
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. l l l l l l livewire.log—This log records basic processing from the Storage Mirroring Replicate console. It can be found in the Storage Mirroring Replicate installation directory where the console is being run.
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.
Event messages The following table identifies the Storage Mirroring events. 1 This evaluation period has expired. Mirroring and replication have been stopped. To obtain a license, please contact your vendor. Error—Contact your vendor to purchase either a single or site license. 2 The evaluation period expires in %1 day(s). Information—Contact your vendor before the evaluation period expires to purchase either a single or site license. 3 The evaluation period has been activated and expires in %1 day(s).
1003 The Double-Take counter DLL could not open the "Performance" key in the Double-Take section of the registry. Error—Run the installation and select Repair. Contact technical support if this event occurs again. 1004 The Double-Take counter DLL could not read the "First Counter" value under the Double-Take\Performance Key. Error—Run the installation and select Repair. Contact technical support if this event occurs again.
4006 Service has aborted due to the following unrecoverable error: %1 Error—Restart the Storage Mirroring service.
4018 %1, however, mirroring and replication have been disabled as a restore is required due to a previous failover. Warning—Perform a restoration. 4019 Service has started a mirror to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 4020 Service has paused a mirror to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 4021 Service has resumed a mirror to %1 (%2) for Replication Set %3, ID: %4 Information—No action required.
4030 RSResource.dll has an unknown error. The product functionality has been disabled. Error—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists. 4031 RSResource.dll could not be opened. The product functionality has been disabled. Error—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists.
4037 Error verifying the vendor URL name. The product functionality has been disabled. Error—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists. 4038 Error verifying the product code. The product functionality has been disabled. Error—Reinstall the software, using the installation Repair option, to install a new copy of the RSResource.dll. Contact technical support if this error persists.
4044 An error was encountered and replication has been stopped. It is necessary to stop and restart the service to correct this error. Error—Contact technical support if this error persists. 4045 %1 value must be between 1025 and 65535. Using default of %2. Error—Verify that the Storage Mirroring port value you are trying to use is within the valid range. If it is not, it will automatically be reset to the default value. 4046 This service failed to start because of a possible port conflict.
4054 Service has paused a restore task to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 4055 Service has resumed a restore task to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 4056 Service has stopped a restore task to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 4057 Service has completed a restore task to %1 (%2) for Replication Set %3, ID: %4 Information—No action required.
4066 The product code requires a virtual server environment. The product functionality has been disabled. Error—The activation code you are using is for the Virtual SystemsTM edition. This code will not work on non-virtual server environments. 4067 No replication ops have been received from the driver for an extended period of time. Error—Check other messages for errors with the Storage Mirroring drivers, and correct as required.
4098 The control device %2 was not created. Communication with the service will be disabled. Reboot the server and contact technical support if this error occurs again. The last Word in the Data window is the NT status code. Error—Reboot your server and contact technical support if this event occurs again. 4099 The driver detected a hard link for a file on drive %2. Hard links are not supported. Changes to this file will not be replicated. Warning—Hard links are not supported.
4111 Target can not write %1 due to a sharing violation. Operation will be retried (%2 times or forever) Warning—A sharing violation error is prohibiting Storage Mirroring from writing on the target. The operation will be retried according to the TGExecutionRetryLimit setting. 4112 Target can not write %1 due to access denied. Operation will be retried (%2 times or forever) Warning—An access denied error is prohibiting Storage Mirroring from writing on the target.
scenarios did not cause the task to be discarded, contact technical support. 4202 Running %1 in band script: %2 (task %3 submitted from %4 by %5 at %6) Information—No action required. 4203 Completed run of in band script: %1 (exit code %2) Information—No action required. 4204 Error running in band script: %1 Error—Review the task and its associated script(s) for syntax errors. 4205 Timeout (%1 seconds) running in band script: %2 Warning—The timeout specified for the script to complete has expired.
4306 Target paths for source %1 (%2) Connection id: %3 are already blocked Warning—No action required. 4307 Target paths for source %1 (%2) Connection id: %3 are already unblocked Warning—No action required. 4308 Error loading target paths for blocking, registry key %1 has been corrupted. Error—If you need to block your target paths, contact technical support. 4400 Failed to create snapshot set for source %1 (%2) Connection ID: %3. Error: %4 Error—The snapshot could not be created.
4407 Disabled snapshot schedule for source %1 (%2) connection %3. Information—No action required. 4408 %1 was unable to move some orphans for source %2 on connection ID %3. Check the %1 logs for further details. Warning—Orphan files could not be moved. For example, the location could be out of disk space. Check the Storage Mirroring log for more information. 4409 %3 was unable to delete some orphans for source %1 on connection ID %2. Check the %3 logs for further details.
5103 Started adding drive shares from %1 to %2. Information—No action required. 5104 %1 drive shares were taken over by %2. Information—No action required. 5105 Attempting to run the %1 script. Information—No action required. 5106 The %1 script ran successfully. Information—No action required. 5107 Error occurred in running %1 script. Error—Verify that the script identified exists with the proper permissions. 5108 The source machine %1 is not responding to a ping.
5302 Drive share information for %1 has been updated on the target machine. Information—No action required. 5303 The application monitor script has started successfully. Information—No action required. 5304 The application monitor script has finished successfully. Information—No action required. 5305 The application monitor has found the %1 service stopped. Warning—Application Manager will attempt to restart the service. 5306 The application monitor has restarted the %1 service. Warning—No action required.
5503 E-mail notification could not be processed. Check to make sure the correct version of SMTPMail.DLL is registered on the system (error code: %1). Warning—If you are using Storage Mirroring 4.4.2.1 or earlier and Windows NT 4.0, e-mail notification requires Windows Management Instrumentation (WMI) to be installed. Verify that you have it installed on the Storage Mirroring server. 5504 Could not load LocalRS.dll (for e-mail notification).
7107 The driver was unable to get valid name information from the Filter Manager for a file. It cannot be replicated. Please contact technical support. Error—Contact technical support. 8100 The driver encountered an unrecoverable internal error. Contact technical support. The last Word in the Data window is the internal error code. Error—Contact technical support. 8192 Driver failed to allocate Kernel memory. Replication is stopped and server must be rebooted for replication to continue.
repeatedly, contact technical support. The last Word in the Data window is the NT status code. Warning—Contact technical support if this event occurs again. 9100 The driver encountered an error opening a file from the service. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages. Contact technical support if this event occurs again.
9106 The driver encountered an error writing file security data to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages. Contact technical support if this event occurs again. 9107 The driver encountered an error querying for an allocated range from the service input buffer.
9112 The driver encountered an error writing a directory query to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages. Contact technical support if this event occurs again. 9113 The driver encountered an error querying a stream from the service input buffer.
information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages. Contact technical support if this event occurs again. 9119 The driver encountered an error writing extended attributes status to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages.
or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages. Contact technical support if this event occurs again. 9125 The driver encountered an error writing fsctl status to the service input buffer. Check the Event Viewer Application log for additional service information or contact technical support. The last Word in the Data window is the exception code. Error—Check for related service messages.
10005 Node %1 is taking ownership of the group %2. The group will be brought online on this node. Information—No action required. 10006 The cluster notification thread failed to start on node %1 for resource %2. The resource should be taken offline and brought back online. Warning—Take the resource offline and bring it back online. 10007 The user %1 has reverted a snapshot for the %2 resource on node %3. Warning—No action required. The snapshot you selected will be reverted.
10102 The driver could not recall the file. The last Word in the Data window is the exception code. Error—Contact technical support if this event occurs again. 11000 Service has started an archive to %1 (%2) for Replication Set %3, ID: %4 Information—No action required. 11001 Service has completed an archive to %1 (%2) for Replication Set %3, ID: %4, %5 Information—No action required. 11002 Service has started a recall from %1 (%2) for Replication Set %3, ID: %4 Information—No action required.
11011 Service has aborted the archive preview operation. Warning—Verify the activation code on the source and target is valid for archiving. Reboot an unlicensed server. 12000 The service has started. Information—This message refers to the Storage Mirroring Recall service. No action required. 12001 The service failed to start. Error—Check the user name and password for the Storage Mirroring Recall service to ensure validity. Reinstall the software if this event occurs again. 12002 The service has stopped.
16384 The driver encountered an unrecoverable error. Contact technical support. Error—Contact technical support 16385 The driver encountered an unexpected internal result. Contact technical support. The last Word in the Data window is the NT status code. Error—Contact technical support. 16393 The driver encountered an internal error. Contact technical support. The last Word in the Data window is the internal error code. Error—Contact technical support.
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.
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.
l l l -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 specified IP address using the specified port number instead of to the local machine Examples l DTStat -i 300 l DTStat -p -i 300 -t AlphaStats.sts l DTStat -f AlphaStats.sts -s AlphaStats.csv -start 02/02/2007 09:25 l DTStat -server 206.31.4.
Statistics The following table identifies the Storage Mirroring statistics. Note: 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.
Kernel, SourceState l 0—Source is not running l 1—Source is running without the replication driver l 2—Source is running with the replication driver Kernel, TargetState l 0—Target is not running l 1—Target is running Kernel, Start Time Date and time stamp indicating when the Storage Mirroring service was loaded Kernel, RepOpsGenerated The number of replication operations generated by the file system driver. An op is a file system operation.
Kernel, FailedMirrorCount The number of mirror operations that failed due to an error reading the file from the disk Kernel, FailedRepCount The number of replication operations that failed due to an error reading the file from the disk Kernel, ActFailCount The number of activation code failures when loading the source or target. Activation codes can be bad for reasons such as: expiration of evaluation codes, duplicate codes, incorrect codes, etc.
Target, Ops Remaining The total number of operations that are left in the target queue Target, Orphan Files Removed The number of orphan files removed from the target machine Target, Orphan Directories Removed The number of orphan directories removed from the target machine Target, Orphan Bytes Removed The number of orphan bytes removed from the target machine Target, Bytes In Target Queue The number of bytes currently in the system memory queue on the target Target.
Connection, conPeerAddress The IP address of the target machine Connection, connectTime The time that this connection was established Connection, conState The state of the active connection l l l l l 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.
Connection, conBytesInRepQueue The number of replication bytes remaining to be transmitted to the target Connection, conOpsTx The number of operations transmitted to the target. This is the total number of operations that Storage Mirroring has transmitted as a source. In other words, the cumulative number of operations transmitted by this source to all connected targets.
changes to a file, then it will indicate the number of bytes it did not send for this file in this field. Connection, conMirrorBytesRemaining The number of mirror bytes remaining to be transmitted Connection, conMirrorPercent The percentage of the mirror that has been completed. This field is determined if the replication set size was calculated.
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 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. l Double-Take Connection l Double-Take Kernel l Double-Take Security l Double-Take Source l Double-Take Target 4. Select the statistics you want to monitor, and click Add.
Performance Monitor statistics The following table identifies the Storage Mirroring Replicate Performance Monitor statistics. Note: If you have multiple IP addresses connected to one target server, you will see multiple Target statistic sections for each IP address.
Connection, Operations in replication queue The number of replication operations in the source queue Connection, Operations received The number of operations received by the target since the last Performance Monitor refresh Connection, Operations resent The number of operations re-sent since the last time the Storage Mirroring service was restarted on the source Connection, Operations transmitted The number of operations transmitted from the source Connection, Task commands queued The number of task command
Kernel, CRC Thread Count The number of commands being executed simultaneously on the target. In a properly functioning environment, this number should never be greater than the number of difference mirrors currently being executed on the sources connected to this target. If the value grows larger than the number of currently executing differences mirrors, that indicates there is an error condition.
Kernel, Open Target Handles The number of handles currently open on the target.
Target, Ops Remaining The number of operations on the target remaining to be applied Target, Orphan Bytes The number of orphan bytes removed from the target Target, Orphan Directories The number of orphan directories removed from the target Target, Orphan Files The number of orphan files removed from the target Target, Retries The number of retries performed on the target since the last time the Storage Mirroring service was restarted on the target Target, Tasks failed The number of task commands that have
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. l l The sub-agent is a program that installs and runs on the same machine as Storage Mirroring Replicate and gathers statistics, data, and traps.
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.
SNMP traps The following table lists the Storage Mirroring SNMP traps.
Connection, dttrapConnectionFailed The source to target connection was not successful Connection, dttrapConnectionLost The source to target connection has been disconnected Connection, dttrapMemoryLimitReached The Storage Mirroring memory pool limit has been reached Connection, dttrapMemoryLimitRemedied The memory pool usage is below the maximum limit specified Connection, dttrapAutoReconnect Auto-reconnect needs to make a new connection Connection, dttrapScheduledConnectStart A scheduled connection has bee
Mirroring, dttrapMirrorStop Mirroring has stopped Mirroring, dttrapMirrorPause Mirroring has paused 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 Replicatio
SNMP statistics The following table lists the Storage Mirroring SNMP statistics.
General, dtDriverQueuePercent The amount of throttling calculated as a percentage of the stop replicating limit Source, dtSourceState 0—Source is not running 1—Source is running without the replication driver 2—Source is running with the replication driver.
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. 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.
Connection, dtconBytesCompressedTx The total number of compressed bytes transmitted to the target Connection, dtconOpsRx The total number of operations (create, modify, or delete) received from the target Connection, dtconBytesRx The total number of bytes received from the target Connection, dtconResentOpCount The number of operations that were resent because of acknowledgement errors Job monitoring Page 173 of 214
Error codes The following table contains error codes that you may see in the various user interfaces or in log files.
-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 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 Replicati
-154 Transmission is active -155 Target does not support the command -156 Command conversion to accommodate a different Storage Mirroring version has failed -157 Incompatible source and target Storage Mirroring 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 retry
-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 -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
-223 Script timeout met -224 No replication timeout met - connection is bad -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 (E-mail notification no longer requires Internet Explorer 5.0 or later.
-2401 Snapshot module is not loaded -2402 Error reading the snapshot .
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.
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.
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.
has shared the archive bin correctly and if network communications are functioning properly. Any success or failure messages will be included in the Storage Mirroring Replicate dtlogX.dtl file on the source.
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.
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 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.
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.
l l 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.
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.
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. l l l 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.
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.
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.
Recalling archived files using the Replication Console 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.
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. 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.
Repository server management You can add, manage, and monitor your repository servers from the Manage repository servers page. Click Manage repositories from the left navigation pane to access this page. When viewing the Manage repository servers page, the window is divided into two sections. The top pane displays the list of repository servers discovered from the protection and recovery jobs being monitored, as well as repository servers that have been added manually.
l Performing deduplication management tasks l Using the AtomAdmin utility Monitoring a repository server When a repository server is highlighted in the top pane of the Manage repository servers page, the bottom pane displays detailed data about the server. 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. The detailed information is automatically refreshed every 15 seconds.
l Size—The total size of the volume l Free—The amount of free space on the volume l Detail—Additional status or known information for the volume Managing a repository server The Manage repository servers page has its own toolbar buttons for repository server controls. Add server The server icon allows you to add a new repository server to monitor and manage.
Setting deduplication options File-level deduplication allows you detect and reduce storage of redundant files on the repository server. l Deduplicate—Select the checkbox in the Deduplicate column for those volumes that you want to deduplicate redundant files. The system volume, with the boot partition, will be unavailable for deduplication. Note: Some files (for example, .log, .temp, .tmp, and so on) and some files with particular attributes (like encrypted, reparse, and so on) will not be deduplicated.
NTFS change journal already exists, the existing change journal will be used with the size and growth values originally specified. l Storage bin location—Specify the location where the single copy of the redundant files will be stored. Do not select the system volume. Note: If you set the storage bin location during another protection setup, the option to set a storage bin location will not be available. Instead, you will need to move the storage bin, if desired.
Performing deduplication management tasks If needed, you can move the location of your deduplication storage bin, or you can restore deduplicated files. 1. Click Manage repositories in the Storage Mirroring Replicate Console left navigation pane to take you to the Manage repository servers page, if you are not already there. 2. Click Perform deduplication tasks from the Manage repository servers page toolbar. 3. If you want to move the location of the deduplication storage bin, click Move location.
Note: After a deduplication task has started, if the Atom File-Level Deduplication Service is stopped for any reason (including a server shutdown or crash) before the task has completed, that task will not be restarted automatically. You will need to restart the task manually.
Using the AtomAdmin utility The deduplication feature is designed to run with minimal up-front configuration. However, because the storage bin and the embedded SQL database for duplicate identification can grow over time, you may eventually need to perform tasks to maintain or restore efficient deduplication operation. Complete the following tasks using the AtomAdmin.exe command-line utility, which is located in the \Atom subdirectory where you installed Storage Mirroring Replicate.
l l l l l l l volume_list—A semi-colon separated list of volumes that specifies the drive(s) that will be validated. The volumes can be designated as a drive letter (e), a drive designation (e:), a drive path (e:\), or the eightdigit volume serial number. None of these designations are casesensitive. If this option is not specified, all system drives will be validated. F or FIX—These options will automatically delete orphan files from the storage bin when using the bin or all validation options.
The following are some sample tasks where you might want to use the AtomAdmin utility. Scanning the storage bin to remove unused content Use the following instructions to scan the storage bin and remove unused content. 1. Validate the links and storage bin files by using the following command, substituting the volumes to be evaluated for volume_list. atomadmin -v all volume_list 2.
Validating the Atom database or recovering from an inconsistent Atom database The Atom embedded database is self-cleaning. Normal operation will add or remove database rows as files are added or removed from monitored volumes. For volumes that are no longer being monitored, use the following instructions to validate the database.
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.
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. Note: If your server is not listed, select Insert, Server. Type the machine name or IP address and click OK. c. Double-click the server to log on to it. d. Right-click the server in the left pane of the Replication Console and select Properties. e.
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.
Index A ACLs (access control list) 26 activation code 44 alternate data streams 26 archiving Atom requirements See Cargo 6 25 B bandwidth 59, 104 C Cargo files overview 186 6, 10, 180 preview report 184 recalling 192 requirements 12, 23 schedule 188 security 181 storage location 190 compression files 58, 103 26 console overview requirements security Index 46 12, 25 49 Page 208 of 214
continuous data protection See TimeData D deduplication requirements dynamic volumes 25 26 E e-mail recovery server 107 repository server 62 encrypted files error codes event messages Exchange 26 174 120-121 See Ontrack PowerControls F file attributes firewall 26 205 I import 47 installation automatic process 36 continuous data protection 41 installing Double-Take Backup 33 notes 31 Ontrack PowerControls 43 overview 30 recovery server 73 TimeData 41 Index Page 209 of 214
J job controls import 110 47 monitoring 110 monitoring tools 109 optional protection settings 57 optional recovery settings 102 junction points 26 L licensing log file 44 119 logging event messages 120-121 M Macintosh files 26 monitoring tools console 110 log files 119 overview 109 SNMP mount points 165-166 26 O Ontrack PowerControls installing 43 overview 6, 9 Index Page 210 of 214
requirements 12, 22 viewing data 66, 70 overview archiving 6, 10 Cargo 6, 10 continuous data protection Double-Take Backup 6, 8 6 Ontrack PowerControls 6, 9 TimeData 6, 8 P Performance Monitor 158-160 ports 205 preview report 184 protection establishing 50 optional settings 57 overview 50 R recalling 192 recovery data 97 full server to existing 74 full server to Hyper-V 90 full server to VMware ESX 81 installing to recovery server 73 optional settings overview Index 1
recovery server defined installation 6 73 requirements 12, 17 reparse points 26 replication capabilities 26 repository server defined finding data requirements 6 66 12, 15 requirements archiving 23 Atom 25 Cargo 23 console 25 continuous data protection 21 deduplication 25 Ontrack PowerControls 22 overview 12 recovery server 17 repository server 15 source server 14 TimeData 21 route 61, 106 S security credentials shutdown options silent install Index 49 74, 81, 90 36 Pa
snapshot protection 50 recover data 97 recover full server to existing 74 recover full server to Hyper-V 90 recover full server to VMware ESX 81 viewing 66-67 SNMP configuration 166 overview 165 statistics 170 traps 167 source defined requirements 6 12, 14 SQL Server upgrade 30, 42 statistics file 149 output 151 overview 148 Performance Monitor SNMP symbolic links system state 159-160 170 26 6 T TimeData installing 41 overview 6, 8 Index Page 213 of 214
protection 50 recover data 97 recover full server to existing 74 recover full server to Hyper-V 90 recover full server to VMware ESX 81 requirements 12, 21 viewing data 66-67 transactional NTFS operations (TxF) 26 transmission bandwidth 59, 104 compression 58, 103 route 61, 106 TxF (transactional NTFS operations) 26 U upgrade notes 31 SQL Server 42 upgrading Double-Take Backup 33 Index Page 214 of 214
