Rapid Recovery VMware Virtual Hardware (4040057)

Within Rapid Recovery when you do a Virtual Standby or virtual Export to VMware the Rapid Recovery core will build a VM upon a default template that is designed to be a 'one size fits all' VM. This means that when you look at the virtual hardware within VMware you will notice the VM might have a handful of SCSI controllers, or might have different virtual hardware than what it was assigned to originally. This is expected.

What this means is that you will:

1. Have to reconfigure any static IP addresses for your VMs as a new virtual NIC will provide a new MAC address which within the OS static IPs are assigned to MAC addresses
2. You will have multiple SCSI controllers within the VM - this is to support all customer's virtual restores, whether they have 1 hard disk or 20.
3. The virtual hardware on the restored VM WILL NOT be the same hardware that was present on the protected machine.

In situations where an older operating system is being used within the VM that defaults to IDE connections (XP, 2K3, 2K8) this would cause the VM to not boot into Windows. Which will require you to build a new VM in VMware based upon that older OS family and then attach (open existing) the hard disks that you built with Rapid Recovery to the new VM in order to boot off of IDE controllers and not SCSI.

This  again is expected behavior for Rapid Recovery during an Export or a Virtual Standby where the core will create a VM within VMware.