HP Storage Mirroring V5 User Manual

Data Migration

User’s Guide

First Edition (April 2009)

Part Number: T2558-96333

© Copyright 2009 Hewlett-Packard Development Company, L.P.

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors
contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this
material.

This document contains proprietary information, which is protected by copyright. No part of this document may be
photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The
information contained in this document is subject to change without notice.

Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information
is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Hewlett-Packard
Company products are set forth in the express limited warranty statements for such products. Nothing herein should be
construed as constituting an additional warranty.

HP StorageWorks Storage Mirroring Data Migration User’s Guide

First Edition (April 2009)

Part Number: T2558-96333

Double-Take, GeoCluster, Double-Take for Virtual Systems, TimeData, netBoot/i, winBoot/i, Double-Take Cargo, sanFly, Livewire, NSI, Balance,
Double-Take ShadowCaster, and associated logos are registered trademarks or trademarks of Double-Take Software, Inc. and/or its subsidiaries in the United
States and/or other countries. Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United
States and/or other countries. All other trademarks are the property of their respective companies.

© 2009 Double-Take Software, Inc. All rights reserved.

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. You can also migrate just a source's data, in which case the target's system state
(operating system, server configuration, and installed applications) will be used with the
source's data.

Storage Mirroring Data Migration uses patented data replication technology that allows
users to continue accessing and changing data during the migration. As changes are
made on the source, replication keeps the image of the source stored on the target up-to­date. Storage Mirroring Data Migration replicates, in real-time, only the file changes, not
the entire file, allowing you to more efficiently use resources. When you are ready to
cutover to the new server, Storage Mirroring Data Migration applies the source system
state and after a reboot, the source is available and running on what was the target
server hardware.

3 of 49

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.

Source server requirements

● Operating system—Storage Mirroring Data Migration can migrate a physical or

virtual source server running any of the following operating system editions.

● Windows Server 2008 Enterprise, Standard, Web, Small Business Server,

Enterprise x64, or Standard x64

● Windows Server 2003 or 2003 R2 Enterprise, Standard, Web, Small

Business Server, Enterprise x64, or Standard x64. Each of the Windows
2003 operating systems require Service Pack 1 or later.

● System memory—There are different memory requirements depending on the

system architecture you are using. Be sure you have at least the minimum amount
of memory for your environment. You should consider having at least the
recommended amount of system memory.

Architecture Minimum System Memory Recommended System Memory

32-bit 128 MB At least 512 MB

64-bit 512 MB At least 1024 MB

● Disk space for program files—This is the amount of disk space, approximately

130 MB, needed on the source to hold the Storage Mirroring Data Migration
program files.

● File system—Storage Mirroring Data Migration supports the same file system

formats that Microsoft supports: FAT, FAT32, and NTFS.

● Server name—Storage Mirroring Data Migration includes Unicode file system

support, but your server name must be in ASCIIformat.

● Network protocols—Your servers must use TCP/IP with static IPaddressing.

● Junction points—Only domain controller junction points will be replicated. Any

user-created junction points will be replicated as two unlinked copies of the data.

4 of 49

Target server requirements

● Operating system—Your target operating system will depend on the kind of target

you are using.

● 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.

● Windows Server 2008 Enterprise, Standard, Web, Small Business

Server, Enterprise x64, or Standard x64

● Windows Server 2003 or 2003 R2 Enterprise, Standard, Web, Small

Business Server, Enterprise x64, or Standard x64. Each of the
Windows 2003 operating systems require Service Pack 1 or later.

● Provisioned virtual—If your target will be provisioned (automatically created

during the migration process) you must have a physical host machine where
Storage Mirroring Data Migration can create the new virtual server. Your
physical host machine can be either of the following operating systems.

● Windows 2008 Hyper-V

● VMware ESX 3.01 or later with HotRemove patch #692138 with an

existing virtual machine running Windows Server 2003 or 2003 R2
Enterprise or Standard Edition. The existing virtual must have Storage
Mirroring Data Migration installed and licensed on it before you can
start the migration process. The architecture (32-bit or 64-bit) of the
source and existing virtual must be the same. When you are ready for
cutover the existing virtual will create the new virtual server, mount
disks, format disks, and so on.

● System memory—There are different memory requirements depending on the

system architecture you are using. Be sure you have at least the minimum amount
of memory for your environment. You should consider having at least the
recommended amount of system memory.

Architecture Minimum System Memory Recommended System Memory

32-bit 128 MB At least 512 MB

64-bit 512 MB At least 1024 MB

● Disk space for program files—This is the amount of disk space, approximately

130 MB, needed on the target to hold the Storage Mirroring Data Migration
program files.

5 of 49

● Disk space for data files—This is the amount of disk space on the target to hold

all of the source data files. This will be dependent on the applications you are
running and the amount of data files you have.

● Disk space for system state image—This is the amount of disk space on the

target to hold the image of the source system state. You should have at least 5 GB
of space on the target. The more applications you are running on the source, the
larger the system state image will be. Therefore, you may need additional space if
you source has many applications.

● Disk types—Thin-provisioned virtual disks on VMware ESX are not supported

because they cannot be shared by two virtual machines simultaneously.

● Server name—Storage Mirroring Data Migration includes Unicode file system

support, but your server name must be in ASCIIformat.

● Network protocols—Your servers must use TCP/IP with static IPaddressing.

Console requirements

The Storage Mirroring Data Migration console can be run from a source or target to
perform migrations. It can also be run from a source or target to install to other Storage
Mirroring Data Migration servers. However, you cannot run the console on a machine
and install a Storage Mirroring Data Migration server on that same machine.

The Storage Mirroring Data Migration console can be run on any of the source server
operating systems listed above. It can also be run from a Windows XP or Vista machine.

Microsoft .NET Framework version 3.5 Service Pack 1 is required to run the console.

6 of 49

Installation

You will need to install and license the Storage Mirroring Data Migration console first.
From the console, you will be able to install your Storage Mirroring Data Migration
servers. Make sure before installing on your servers, you verify the type of server
licensing you will use.

The following sections are included in this section.

● Installing the Storage Mirroring Data Migration console

● Licensing your console

● Storage Mirroring Data Migration server licensing

● Installing a Storage Mirroring Data Migration server

7 of 49

Installing the Storage Mirroring Data Migration console

Install the Storage Mirroring Data Migration console first. From the console, you will be
able to install your Storage Mirroring Data Migration servers.

You will not be able to install a Storage Mirroring Data Migration server on the

Note:

same machine where you are running the Storage Mirroring Data Migration
console.

1. Close any open applications.

2. Start the installation program using the appropriate instructions, depending on your
media source.

● CD—Load the Storage Mirroring Data Migration CD into the local CD-ROM

drive. If auto-run is enabled, the installation program will start automatically.
To manually start the program, select Start, Run and specify <cd_
drive>:\autorun.exe.

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

3. When the installation program begins, the Storage Mirroring Setup Launcher
appears allowing you to install software and view documentation for various
applications from HP. The listed applications will depend on which products are
included on the CD or in the web download. To install Storage Mirroring Data
Migration, select Storage Mirroring Data Migration from the list of products and
then select Install Storage Mirroring Data Migration.

4. Depending on your version of Windows and the components you have installed,
you may see an initial screen indicating that you should install Microsoft .NET
Framework. If you do not see this screen, your server already has the appropriate
version of Microsoft .NET. The best practice is to install Microsoft .NET before
installing Storage Mirroring Data Migration. Clicking Install will continue the
installation program and give you the opportunity to install or skip the Microsoft
.NET installation. Clicking Cancel will exit the installation program.

The Microsoft .NET installation is via a web download. If your server does

Note:

5. Review and accept the HP license agreement to continue with the installation
program. Click Next to continue.

not have an Internet connection, you must manually install Microsoft .NET
from the Storage Mirroring Data MigrationCD or from a copy from the
Microsoft web site.

8 of 49

6. Select where you want to install Storage Mirroring Data Migration and click Next to
continue.

7. Click Install to begin the installation process.

8. After the files have completed copying, click Finish to exit the installation program.

The Storage Mirroring Data Migration console installation is complete.

9 of 49

Licensing your 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. Licensing the console links the console to a specific machine. Any user on that
machine can use the console, but the console license cannot be used on another
console running on another machine. You will not be able to manage the source server
licenses on one console with another console. The recommended configuration is to
select one machine that will be used to perform all Storage Mirroring Data Migration
server installations and to handle all Storage Mirroring Data Migration source server
licensing.

If you want to perform an installation on a target server or on a source server
that will be using a Storage Mirroring license, you do not need to license the
Storage Mirroring Data Migration console.

Note:

You will not be able to install a Storage Mirroring Data Migration server on the
same machine where you are running the Storage Mirroring Data Migration
console.

1. Open the Storage Mirroring Data Migration console and select Tools, Licensing.

2. Enter your License and click Generate. A valid license will automatically populate
the Server Information.

3. You need to provide the Server Information from this console to anHPpartner
company.

● If you have Internet access from this console, click on the link Get Unlock

Code. You will be taken to a form on the HP partner web site. The Server
Information will be filled in automatically. Enter the remaining information

and submit the form.

● If you do not have Internet access from this console, write down the Server

Information. From a machine with Internet access, go to

https://activate.doubletake.com/hp_data-migration/. (Note there is an

underscore in the URL http://activate.doubletake.com/hp_data-migration/.)
Fill in the information on the form, including the Server Information, and
submit the form.

● If you do not have Internet access, contact your reseller by phone. You will

need the Server Information to give to your reseller.

10 of 49

4. After you or your reseller have submitted the required information and the Server

Information, you will be provided an unlock code via e-mail. Enter that code in the
Unlock Code field and click Unlock.

Once your console has a valid Unlock Code, you can install on the number of sources
assigned to that license. This is listed as the Total migration licenses. The Currently
available licenses field identifies the number of migration licenses you have available
for use. If desired at a later time, you can purchase and enter a new license that will add
to your remaining number of migration licenses.

11 of 49

Storage Mirroring Data Migration server licensing

Storage Mirroring Data Migration has two different licensing strategies.

License

Storage
Mirroring
Data
Migration
migration
license

Purchase

Requirements

for the

Source

You must
purchase a
Storage
Mirroring Data
Migration
migration
license for
each source
you want to
migrate.

Purchase

Requirements

for the

Target

No license is
required for the
target when
using a
Storage
Mirroring Data
Migration
migration
license on the
source.

Server

Installation

You must use
the Storage
Mirroring
Data
Migration
console to
install
Storage
Mirroring
Data
Migration on
each server.

Migration

Timeline

You must
complete the
migration
before the
Storage
Mirroring
Data
Migration
licenses
expires.
Additional
Storage
Mirroring
Data
Migration
migration
licenses can
be
purchased
and added
to the
Storage
Mirroring
Data
Migration
console.

Console

Locking

Requirements

The Storage
Mirroring Data
Migration
console must be
licensed to a
particular
machine in order
to manage the
Storage Mirroring
Data Migration
source server
licenses. License
management on
the console
shows you the
number of
migration
licenses used
and remaining.

1

12 of 49

License

Storage
Mirroring
license

Purchase

Requirements

for the

Source

Purchase

Requirements

for the

Target

You must purchase a Storage
Mirroring license for both the
source and target.

Server

Installation

If Storage
Mirroring is
not already
installed on
each server,
you can use
the Storage
Mirroring
Data
Migration
console to
install
Storage
Mirroring
Data
Migration on
each server.
You will
need a
Storage
Mirroring
activation
code for each
server for the
installation.

Migration

Timeline

There is no
expiration
date with
this license.
After the
migration,
the Storage
Mirroring
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
Migrationconsole
does not have to
be licensed to a
particular
machine when
using it to install
with Storage
Mirroring
licenses.

1

1

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 licenses.

13 of 49

Installing a Storage Mirroring Data Migration server

Before you can perform a migration, you must have Storage Mirroring Data Migration
installed on both the source and target. You must use the Storage Mirroring Data
Migration console to perform Storage Mirroring Data Migration installations on these
servers. You can also use the Storage Mirroring Data Migration console to perform
Storage Mirroring installations.

You cannot install a Storage Mirroring Data Migration server on the same
machine where you are running the Storage Mirroring Data Migration console.

Note:

In order to perform the installation across a NAT or firewall, you must have the
Microsoft WMI and File Share ports open. See Microsoft Windows ports in the

Using firewalls section.

1. If your Storage Mirroring Data Migration servers have Microsoft .NET version 3.5
Service Pack 1 or later, you can skip this step and go to step number 2. If your
Storage Mirroring Data Migration servers do not have Microsoft .NETversion 3.5
Service Pack 1 or later, you must make it available in your Storage Mirroring Data
Migration console installation directory before you start your Storage Mirroring
Data Migration server installations.

a. Locate the file \NetFx\v3.5SP1\dotnetfx35.exe on the Storage Mirroring Data

Migration CD or download .NET version 3.5 Service Pack 1 from the
Microsoft web site.

b. If you downloaded the file, rename the file, if necessary, so that it is

dotnetfx35.exe. In order for the .NET file to be located during the server
installation, the file name must be dotnetfx35.exe.

c. Copy the dotnetfx35.exe file to your Storage Mirroring Data Migration

installation directory. By default, the installation directory is \Program
Files\StorageWorks\Storage Mirroring. With this file in this location, it will be
installed during the Storage Mirroring Data Migration server installation.

2. If your Storage Mirroring Data Migration servers are all the same architecture (32­bit 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. If
your Storage Mirroring Data Migration servers are different architectures and you
downloaded your media from the web, you will need to make additional files

14 of 49

available in your Storage Mirroring Data Migration console installation directory
before you start your Storage Mirroring Data Migration server installations.

a. In your Storage Mirroring Data Migration console installation directory (by

default, \Program Files\StorageWorks\Storage Mirroring), look for the i386
and x64 directories. Only one of them will exist depending on the file you
downloaded and installed. If you originally downloaded a file with i386 in the
file name, you have only files for 32-bit machines. If you originally
downloaded a file with x64 in the file name, you have only files for 64-bit
machines.

b. Create the directory that does not exist. At this point, you should have

\Program Files\StorageWorks\Storage Mirroring\i386 and \Program
Files\StorageWorks\Storage Mirroring\x64.

c. Downloaded the file for the architecture that you need and copy it to your

Storage Mirroring Data Migration console machine.

d. Double-click the file to open it in WinZip.

e. Disable (uncheck) the option When done unzipping open \autorun.exe.

Make sure this option is off because you will not be able to install the files
because you already have the Storage Mirroring Data Migration console
installed.

f. Change the directory Unzip to folder to the \i386 or \x64 directory that you

created earlier. The directory name should correspond to the architecture of
the file you downloaded.

g. Click Unzip. After the files are unzipped, the additional files will be available

for the Storage Mirroring Data Migration console to use.

3. Open the Storage Mirroring Data Migration console and click Prepare from the left
navigation pane.

4. Identify the server where you want to install Storage Mirroring Data Migration.

● Server—Specify the name of the 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. If your source is the only domain controller in
your network, the account must also be a local account in the local
administrators group.

● Password—Specify the password associated with the User name you

entered.

● Domain—If you are working in a domain environment, specify the Domain.

● 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

15 of 49