HP StorageWorks Storage Mirroring application notes Guidelines for using Storage Mirroring with VMware Converter Part number: T2558–96061 First edition: April 2007
Legal and notice information © Copyright 2007 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.
Document overview This document is a Storage Mirroring application note. An application note provides guidelines on the use of Storage Mirroring in a specific environment. This document contains: • Document overview—Explains what an application note contains, how it should be used, what you need to know before trying to use the application note, and where you can go for more information.
• Guidelines for Minimizing Downtime During Failback and Restoration Using Storage Mirroring—This document describes an alternate restoration method that reduces the amount of downtime incurred during failback and restoration.
is complete, DFS is used to import the replica virtual disks, which are then attached to the new virtual machine. This scenario is described in section ”Migrate a Physical Server to a Virtual Machine” on page 5. C:\ HelperBoot.vmdk operating system Double-Take File Server new virtual machine 1 File_C-system.vmdk File_D-data.vmdk C:\File_C-system C:\ Exch_C-system.vmdk C:\Exch_C-system D:\ Exch_D-data.vmdk C:\Exch_D-data C:\ D:\ C:\ SQL_C-system.vmdk D:\ SQL_D-data.
Because no two environments or configurations are exactly the same, you will probably need to implement additional or different steps than what is documented here in order to make the solution work in your environment. Requirements • VMware ESX Server 3.0 with HotRemove patch (#9239363); or ESX Server 3.0.1 with the HotRemove • • • • • • patch (#6921838) DFS 3.0 or later VMware VirtualCenter 2.0 or later VMware Virtual Infrastructure client 2.0 or later Storage Mirroring 4.
In an environment where multiple servers are being migrated, you may need to allocate multiple CPUs, additional memory, or multiple NICs to the helper virtual machine to ensure that it can support the data flow coming from multiple physical servers. NOTE: 9. On the I/O Adapter page, make sure that the default LSI Logic SCSI Adapter is selected. 1. On the Select a Disk page, select the Create a new virtual disk option. 2.
When creating the folder for the mount point, you may want to give it a descriptive name, such as _, where is the name of the physical host that is being migrated, and is the drive on that physical host that you will be replicating to this mount point (for example, ExchangeServer_C. NOTE: 6. 1. Format the disk as NTFS, optionally giving it a Volume label.
Detach the corresponding virtual hard disk from the helper virtual machine Remove the disk from within the helper virtual machine After the replication sets have been disconnected, the virtual disks can be un-mounted from within the helper virtual machine. 1. Open the helper virtual machine console. 2. Select Start, Programs, Administrative Tools, Computer Management, and select Disk Management. 3. Right-click on the first volume to be released, then select Change drive letter and path. 4.
4. 5. 6. 7. 8. Configure additional settings for the new virtual machine that are appropriate for the physical server that you will be migrating. On the Select a Disk page, select the Use an existing virtual disk option. On the Select Existing Disk page, browse to the virtual hard disk file that contains the boot volume of the physical server that you will be migrating. On the Advanced Options page, keep the default settings for the SCSI address and disk type. On the Ready to Complete page, click Finish.
Storage Mirroring does not mirror the pagefile. By default, DFS assigns a 200 MB pagefile. You will need to update the pagefile to a more appropriate value. NOTE: Modif y IP address confi gu ration If your physical server had a static IP address that you plan to re-use on the new virtual machine, you will need to remove the registry entries for your network adapters, then re-configure the static IP address. 1.
2. 3. 4. 5. 6. 7. 8. On the Wizard Type page, select Custom as the type of virtual machine to create. On the Name and Folder page, enter a name for the virtual machine, such as “HelperVM”, then select a location for the virtual machine. On the Datastore page, select the data store that will store the helper virtual machine configuration files. On the Guest Operating System page, select the guest operating system for the helper virtual machine.
4. 5. If the Initialize Disk Wizard does not launch automatically, right-click on every disk that is listed as Not Initialized and initialize it. Right-click on the Unallocated space, select Create Partition, and create a primary partition in that space. When asked to assign a drive letter, select Mount in the following empty NTFS folder. You may create a new folder by clicking the Browse button and creating a new folder within the dialog box.Format the disk as NTFS, optionally giving it a Volume label.
1. 2. 3. Taking the source virtual machine offline of its production responsibilities (that is, stop the application services and disallow client connections). Use the Storage Mirroring Management Console to disconnect the replication set(s) from the source virtual machine to the target (helper virtual machine). Then, delete the replication set. Remove the source virtual machine from the network.
1. 2. 3. 4. 5. 6. 7. 8. Launch the VMware Virtual Infrastructure New Virtual Machine Wizard. On the Wizard Type page, select Custom as the type of virtual machine to create. On the Name and Folder page, enter a name for the new virtual machine, such as “RecoveryVM”, then select a location for the virtual machine. Configure additional settings for the new virtual machine that are appropriate for the source virtual machine that you will be migrating.
3. 16 Set the IP address on the network adapter as it was on the source virtual machine.
