Virtualization for Disaster Recovery: Metrics

Archive for the ‘Virtualization’ Category

Virtualization for Disaster Recovery: Metrics

Posted by

Some quick thoughts on using server virtualization for disaster recovery. The key metrics in using VMs for DR is RTO and RPO. These are defined during the BIA process. One question that I wrestled with was how to get a near time RTO (within minutes before the disaster) and a rapid RPO (within 1hours after the disaster).

Traditional P2V techniques rely on a live system or a nightly backup, so RTO is up to 24 hours. Traditional P2V also relies upon writing the data back out into virtual disks, so the RPO for our average server was up to 7 hours. We addressed these challenges by keeping the storage on a backend SAN and pointing the disk into the VM in the event of a disaster. The RTO is then near time and the RPO is an hour or less.

The DR strategy requires native NTFS disk access and SAN support. Both VMware ESX and Hyper-V support this type of DR. Linux based hypervisors such as Xen do not.

XenServer hangs on Himem.sys when booting DOS

Posted by

I am testing out XenServer for server virtualization, and Acronis for physical-to-virtual conversions. When booting on the Acronis restore CD, the vm displays:

cirrus-compatible VGA is detected
Processor 1: Xen(R) Virtual CPU
XS Virtual IDE Controller  Hard Drive (16384MB)
Unknown device
Unknown device
XS Virtual ATAPI-4  CD-Rom/DVD-Rom

Boot device: CD-Rom – success.
Starting Caldera DR-DOS…
HIMEM.SYS: Cannot control address line A20.

Caldera DR-DOS 7.03
Copyright (c) 1976, 1998 Caldera, Inc. All rights reserved.

It then hangs with the processor consuming 100% of the resources. I notice the same behavior when booting from a DOS 6.22 disk with Himem.sys loading, even if I specify /a20control:off.  I found an article from Microsoft that describes the problem. Submitted it to Acronis to get a fix. They wrote back “We have confirmed this behavior with the Xen Virtualization platform with the DR process. Right now it has been logged as a defect in our bugtracker. Right now I do not have an ETA on this being resolved.”

 The “Unable to control A20 Line” error message
http://support.microsoft.com/kb/73713

There are two workarounds for this problem:

Add the /M:x switch to the HIMEM.SYS line in the CONFIG.SYS file, where x is number from the valid range of 1-14 and 16, and then restart your computer. For example: DEVICE=C:\DOS\HIMEM.SYS /M:1

Upgrade your computer’s BIOS or contact your computer vendor for help with the modification of your CMOS settings. You may need to disable a FastGate (or similar) option.

The A20 line is the start of the first 64K of extended memory, known as the high memory area (HMA). The HIMEM.SYS device driver must control the A20 line to manage extended memory. The HIMEM.SYS driver reports the error if it incorrectly identifies the extended memory handling mechanism of the computer or if the handling method of the computer’s BIOS is unknown.

Move an OS, set the IP, and see the IP address you have entered is already assigned

Posted by

You did something. Maybe you replaced a network adapter on a physical server. Maybe the server is a virtual machine, and you moved the vm to a new host. Maybe you restored an OS onto new hardware, or moved an OS on the SAN from one piece of server hardware to another. The result is that your network adapter is now set to DHCP.

You go into your Windows Server 2003 control panel, network connections, and pull up properties of the network adapter. Open properties of Internet Protocol (TCP/IP) and set the IP address. When you click Ok, you get:

 

The IP address a.b.c.d you have entered for this network adapter is already assigned to another adapter ‘Some Ethernet Adapter’ on this computer. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to fix the problem by entering a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

 

You check the control panel and do not see any other network adapters. The reason is that the adapter is hidden from network connections control panel once it is removed. However, it still contains its IP address.

The resolution is to turn nonpresent devices on and remove the network adapter from device manager:

 

set devmgr_show_nonpresent_devices=1
start devmgmt.msc

 

When Device Manager opens, select View > Show hidden devices. Then browse to network adapters and remove all adapters. Right-click the top-node and scan for new hardware. Your new network adapter will then reinstall itself. Now you will be able to set the IP address without getting the error message.

If this happens frequently, such as if you have a dynamic environment were Windows Server 2003 instances are getting shuffled around regularly, you can set nonpresent devices to be always shown. Add devmgr_show_nonpresent_devices=1 to the System Variables (My Computer, Properties, Advanced, Environment Variables, System Variables).