HP StorageWorks Storage Mirroring Data Migration Users Guide HP Part Number: T5437-96024 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 Data Migration overview 4 Storage Mirroring Data Migration requirements 5 Source server requirements 6 Target server requirements 7 Console requirements 11 Replication capabilities 12 Installation Storage Mirroring Data Migration server licensing 16 17 Storage Mirroring Data Migration migration license 17 Storage Mirroring Recover license 17 Installing Storage Mirroring Data Migration 19 Licensing the Storage Mirroring Data Migration console 21 Insta
E-mailing event messages Job monitoring Monitoring a job through the Storage Mirroring Data Migration console 57 59 60 Overview status information 61 Detailed status information 62 Monitor page toolbar 65 Monitoring log files 67 Monitoring event messages 68 Event messages Statistics 69 96 Viewing the statistics file 97 Statistics 99 Performance Monitor 106 Monitoring Performance Monitor statistics 107 Performance Monitor statistics 108 SNMP 113 Configuring SNMP on your server 114
Storage Mirroring Data Migration overview Storage Mirroring Data Migration is a comprehensive workload migration solution. It allows you to move an entire server, known as a source, by mirroring an image of that source to another server, known as the target. The source and target servers can be physical or virtual. The image of the source contains the server's system state (operating system, server configuration, and installation applications) and all of the source server’s data.
Storage Mirroring Data Migration requirements Each Storage Mirroring Data Migration server must meet minimum requirements. Verify that each server meets the requirements for the function of that machine. Additionally, the machine where you will be running the Storage Mirroring Data Migration console must also meet some basic requirements. 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.
Source server requirements l Operating system—Storage Mirroring Data Migration can migrate a physical or virtual source server running any of the following operating system editions. l l l l l l l l l 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. System memory—There are different memory requirements depending on the system architecture you are using.
Target server requirements l Operating system—You have several options for your target server operating system. l Physical or existing virtual—If your target is a physical server or an existing virtual server, it can have any of the following Windows operating system editions. l l Windows Server 2008 or 2008 R2 Enterprise, Standard, Web, Enterprise x64, or Standard x64 Windows Server 2003 or 2003 R2 Enterprise, Standard, Web, Enterprise x64, or Standard x64.
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.
recovery appliance maintains its own identity, it can be reused for additional migrations.) 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 Data Migration installed and licensed on it.
l Network protocols—Your servers must use TCP/IP with static IP addressing.
Console requirements l l Operating system—The Storage Mirroring Data Migration console can be run from a physical or virtual machine running Windows 7, Windows Vista, or Windows XP, or any of the source server operating systems listed above. Microsoft .NET— Microsoft .NET Framework version 3.5 Service Pack 1 is required on the console. This version is not included in the .NET version 4.0 release. Therefore, even if you have .NET version 4.0 installed, you will also need version 3.5.1.
Replication capabilities Storage Mirroring Data Migration 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 100% complete while mirroring continues. b. The number of files and directories reported to be mirrored will be incorrect.
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.
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 Because of the way Storage Mirroring Data Migration handles migration licenses, the ideal installation scenario is to install Storage Mirroring Data Migration on a single client machine. The client machine is used to manage your server licenses, complete your server installations, and manage your migrations.
Storage Mirroring Data Migration server licensing Storage Mirroring Data Migration has two different licensing strategies. Note: The Storage Mirroring Data Migration console can be used in mixed environments where some servers are being migrated using Storage Mirroring Data Migration licenses and others migrations are using Storage Mirroring Recover licenses.
l l Migration timeline—There is no expiration date with this license. After the migration, the Storage Mirroring Recover licenses can be used on the servers for high availability workload optimization, or the licenses can be reused to migrate other servers. Console locking requirements—The Storage Mirroring Data Migration console does not have to be licensed to a particular machine when using it to install with Storage Mirroring Recover licenses.
Installing Storage Mirroring Data Migration 1. Close any open applications. 2. Start the installation program using the appropriate instructions, depending on your media source. l l CD—Load the HP 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 :\autorun.exe. Web download—Launch the .exe file that you downloaded from the web. 3.
Note: If you selected the Client Components Only installation type, continue with step 16. 9. You will be prompted to enter your activation code information. Enter the code and click Add. If you have other codes for this specific server, add those codes as well. 10. When you have added your activation code(s), click Next to continue. 11. Storage Mirroring Data Migration uses system memory to store data in queues.
Licensing the Storage Mirroring Data Migration console The Storage Mirroring Data Migration console is used to perform Storage Mirroring Data Migration installations on other servers, and it is used as a license manager to manage your Storage Mirroring Data Migration source server licenses. Before you can install Storage Mirroring Data Migration on source servers or before you can manage your source server licenses, you must first license your Storage Mirroring Data Migration console.
Installing Storage Mirroring Data Migration servers from the Storage Mirroring Data Migration console Before you can perform a migration, you must have Storage Mirroring Data Migration installed on both the source and target. You can use the Storage Mirroring Data Migration console to perform Storage Mirroring Data Migration installations on these servers.
2. If your Storage Mirroring Data Migration servers are all the same architecture (32bit or 64-bit), you can skip this step and go to step number 3. If your Storage Mirroring Data Migration servers are different architectures and you installed your Storage Mirroring Data Migration console from CD media, then all necessary files will be available for your server installation and you can go to step number 3.
l l l l License Type—Specify the type of license to be used on the server. Source—The specified machine will be used as a source, meaning it contains the data to be migrated. The installation will automatically push a Storage Mirroring Data Migration license to the source, deducting one license from your available migrations. You must complete the migration before the license expiration date. Typically, the source license is valid for 30 days from when the server is accessed for a job.
Storage Mirroring Data Migration console The Storage Mirroring Data Migration console is the user interface that manages, monitors, and controls your migration solutions. It is also the license manager for all of your Storage Mirroring Data Migration servers. To open the console, select Start, Programs, Storage Mirroring, Move, Storage Mirroring Data Migration Console. On the left pane of the console are static navigation buttons which initiate workflows and display monitoring pages.
Note: The Storage Mirroring Data Migration console requires a 1024x768 minimum screen resolution. Importing a job You can import existing Storage Mirroring Data Migration jobs into the console using the following instructions. 1. From the Monitor jobs page, select Import jobs on the toolbar. 2. Identify the import server. This is the target server that you are migrating to. l l l l Server—Specify the name of the target server or virtual recovery appliance.
Migration When migrating a full server, you can migrate a physical or virtual source to an existing physical or virtual target. You can also migrate to a provisioned virtual target, which means Storage Mirroring Data Migration can create the virtual machine for you during the migration process. When migrating data, you can select data from a physical or virtual source to an existing physical or virtual target.
Migrating an entire source to an existing target Use the following instructions to migrate a source to an existing physical or virtual target. 1. Click Migrate Server from the left navigation pane. 2. Identify the source server that you want to migrate. l l l l 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.
l l l User name—Specify a user that is a member of the Double-Take Admin security group on the target. If your source is the only domain controller in your network, the account must also be a local account in the local administrators group on the target. 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.
7. Specify if your target server is in a LAN or WAN environment with respect to your source. l l LAN migration—If your migration is across a LAN, the source name and the IP address(es) will be applied to the target server. Specify which network adapters on the target that you want to take over for the network adapters on the source. WAN migration—If your migration is across a WAN, the source name will be applied to the target server, but the IP address(es) of the source will not be used.
l l l l User name—Highlight a DNS domain and specify a user account that has privileges to update DNS. 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, highlight the address and click Remove.
server, you will have to go through the job protection workflow again. 14. Once the validation is successful, click Next to continue. 15. At the Migration summary page, you can review the choices you have made and you can also configure optional 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 migration. 16.
If your source was disconnected from the network during the cutover process, the original job that was mirroring the data will still be active on that machine. Do not bring that machine back on the network. If you do, the original job will attempt to begin mirroring data again which could result in data loss. While the machine is still disconnected from the network, stop the Storage Mirroring service, delete the file connect.
Migrating an entire source to a provisioned virtual machine on a VMware ESX target If you want Storage Mirroring Data Migration to create a virtual machine on VMware ESX during the migration process, you must have a VMware ESX host machine with an existing virtual machine. See Target server requirements for details on the requirements for the ESX machine and the existing virtual machine.
Migration steps 1. Click Migrate Server from the left navigation pane. 2. Identify the source server that you want to migrate. l l l l 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.
l l l l l Provision a new virtual machine for this migration—Enable this option to migrate to an automatically provisioned (non-existing) virtual machine hosted on a VMware ESX server. Server—Specify the name of the ESX server. 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 needed for a VMware ESX server. 5. Click Next to continue. 6.
Note: The Select all and Deselect all buttons allow you to quickly select or deselect all user data on your server. These buttons do not change the selection of system state data, which is defined by Storage Mirroring Data Migration and cannot be modified manually. 7. Specify the volumes to create on the new virtual machine. l l l l Selected Data—This displays the amount of data, in gigabytes, currently on the source volume.
disk space is noted at the bottom of the page. Note: If the size of the datastore is identical to the size of the disk on the source and there is less than 20 MB of free space on that source, you may run 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 source. 10. Click Next to continue. 11.
have an operating system capable of performing a migration. l l l l 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 is the only domain controller in your network, the user must be a local account in the local administrators group on virtual recovery appliance. Password—Specify the password associated with the User name you entered.
Network IP lists the IP addresses on the source. Map each one to a Target Network, which is a virtual network on the VMware ESX server. l l Number of processors—Specify how many processors to configure on the virtual machine. The number of processors on the source is displayed. Amount of memory—Specify the amount of memory, in megabytes, to configure on the virtual machine. The amount of memory on the source is displayed. 14. Click Next to continue. 15. Specify your migration shutdown options.
19. When the migration mirror has completed, the target may or may not reboot automatically depending on your selection for Wait for user intervention before cutover. If you disabled user intervention, the target will reboot automatically to complete the migration process. If you enabled user intervention, when the migration mirror is complete, the status will change to Ready for Cutover. Use this time to complete any necessary tasks.
Migrating an entire source to a provisioned virtual machine on a Hyper-V target Use the following instructions to migrate a source to a provisioned virtual machine on a Hyper-V target. 1. Click Migrate Server from the left navigation pane. 2. Identify the source server that you want to migrate. 3. l l l l 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.
l l l l l Provision a new virtual machine for this migration—Enable this option to migrate to an automatically provisioned (non-existing) 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 target.
The Select all and Deselect all buttons allow you to quickly select or deselect all user data on your server. These buttons do not change the selection of system state data, which is defined by Storage Mirroring Data Migration and cannot be modified manually. 8. Specify the volumes to create on the new virtual machine. l l l l l Migration Selected Data—This displays the amount of data, in gigabytes, currently on the source 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. See your Hyper-V documentation for more information.
10. Specify the volume or cluster storage volume and the 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. 11. Click Next to continue. 12. Configure the new virtual machine that will be created and will become the source after the migration. l l Migration Hyper-V Manager display name—By default, the source name_VM will be used to create the new virtual machine display name. If desired, you can modify the name.
Network IP lists the IP addresses on the source. Map each one to a Target Network, which is a virtual network on the Hyper-V server. l l l Number of processors—Specify how many processors to configure on the virtual machine. The number of processors on the source is displayed. Amount of memory—Specify the amount of memory, in megabytes, to configure on the virtual machine. The amount of memory on the source is displayed.
coordinate any other tasks. Replication will continue during this time. If you do not select this option, cutover will be automatic, meaning the source will cutover to the target immediately after the mirror is complete. If your source is running applications, it is important that you enable this option. During the intervention time, you can stop your applications that are running on the source.
begin mirroring data again which could result in data loss. While the machine is still disconnected from the network, stop the Storage Mirroring service, delete the file connect.sts located in the Storage Mirroring Data Migration installation directory, and then restart the Storage Mirroring. This will delete the original job. After the original job is deleted, you can bring the machine on the network if desired.
Migrating data to an existing target Use the following instructions to migrate data from your source to an existing physical or virtual target. 1. Click Migrate Data from the left navigation pane. 2. Identify the source that contains the data that you want to migrate. l l l l 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.
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 Data Migration selects all of the data on your source for migration. It automatically excludes system state information. If desired, you can exclude other files that you do not want to migrate, but be careful when excluding data.
l l Wait for user intervention before cutover—If you select this option, Storage Mirroring Data Migration will pause the migration process after the source data has been mirrored to the target, which allows you time to coordinate any other tasks. Replication will continue during this time. If you do not select this option, cutover will be automatic, meaning the source will cutover to the target immediately after the mirror is complete.
Optional job settings When you are creating a migration job, you will have an opportunity to configure optional job settings when you get to the Migration summary workflow page. If you want to configure optional settings, click Configure next to the options section.
Limiting bandwidth Bandwidth limitations are available to restrict the amount of network bandwidth used for Storage Mirroring Data Migration data transmissions. When a bandwidth limit is specified, Storage Mirroring Data Migration never exceeds that allotted amount. The bandwidth not in use by Storage Mirroring Data Migration is available for all other network traffic. l l l Do not limit bandwidth—Storage Mirroring Data Migration will transmit data using 100% bandwidth availability.
occur Monday through Friday, Weekends to have the limiting occur 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.
Routing transmission By default, Storage Mirroring Data Migration will select a default route for transmissions. The default route is the first connection listed in the NIC binding order on the target.
E-mailing event messages E-mail notification sends specific Storage Mirroring Data Migration events to userdefined 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. 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.
l l l l l l l 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. 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 Data Migration 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 Data Migration console, or you can use several general monitoring tools that are available.
Monitoring a job through the Storage Mirroring Data Migration console Once you have a job established or imported, you can easily monitor the status of the migration 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.
Overview status information Overview information is provided for each job at the top of the Monitor jobs page. No heading 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. 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.
Target The name of your target or virtual recovery appliance is displayed. Time Remaining When mirroring, this is the estimated time remaining to complete the mirror. For various reasons, this calculation is an estimate. For example, some file 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. % Complete When mirroring, this is the estimated percentage of the mirror that is complete.
Job properties, Time remaining When mirroring, this is the estimated time remaining to complete the mirror. For various reasons, this calculation is an estimate. For example, some file 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. Job properties, Source server The name of your source is displayed. Job properties, Target server The name of your target is displayed.
l l Stopped—The mirror is stopped. 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. For example, some file 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.
Monitor page toolbar The Monitor jobs 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 Migrate server or Migrate data. Import jobs The smaller shield icon with the green circle with white plus sign allows you to launch the import jobs workflow.
If the Password associated with a specified User name changes after a job has been started, Storage Mirroring Data Migration 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. Delete job The trash can icon permanently deletes the selected job.
Monitoring log files Various Storage Mirroring Data Migration components, for example the Storage Mirroring service and the Storage Mirroring Data Migration 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 dtmove.log—This log records basic processing from the Storage Mirroring Data Migration console.
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 Data Migration 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 Data Migration 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 Data Migration 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 Data Migration 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 Data Migration 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 Data Migration provides an SNMP sub-agent that can be managed from an SNMP Management Console. Storage Mirroring Data Migration 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 Data Migration and gathers statistics, data, and traps.
Configuring SNMP on your server SNMP must be installed on a server before Storage Mirroring Data Migration in order for the Storage Mirroring Data Migration SNMP components to be added during the Storage Mirroring Data Migration installation. If SNMP is installed on a server after Storage Mirroring Data Migration is installed, run a repair install to install the SNMP components. The Storage Mirroring Data Migration .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 121 of 135
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 .
Using firewalls Storage Mirroring Data Migration 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 Data Migration 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 in to it. d. Right-click the server in the left pane of the Replication Console and select Properties. e.
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.
Index A ACLs (access control list) 12 activate.doubletake.
F file attributes firewall 12 128 H Hyper-V migration requirements 42 5 I import 26 installation installing 19 overview 16 server 22 J job controls 60 import 26 monitoring 60 optional settings 53 junction points 12 L LAN migration licensing log file 28 17, 21-22 67 logging event messages Index 68-69 Page 132 of 135
M Macintosh files 12 migration data overview 50 4, 27 server existing target 28 Hyper-V 42 VMware ESX 34 monitoring tools 59 SNMP mount points 113-114 12 O overview 4 P Performance Monitor ports provision push install 106-108 128 34, 42 22 R reparse points 12 replication capabilities 12 requirements 5 route Index 56 Page 133 of 135
S security credentials shutdown options 26 28, 34, 42, 50 SNMP configuration 114 overview 113 statistics 118 traps 115 source 4 licensing requirements statistics 17, 22 5 60 file 97 output 99 overview 96 Performance Monitor SNMP 107-108 118 status 60 symbolic links 12 system state 4 T target licensing requirements transactional NTFS operations (TxF) 4 17, 22 5 12 transmission bandwidth 54 compression 53 Index Page 134 of 135
route TxF (transactional NTFS operations) 56 12 U unlock key 21 V VMware ESX migration requirements 34 5 W WAN migration 28 Windows reactivation 28 Index Page 135 of 135
