HP StorageWorks Storage Mirroring Recover User's Guide (T5437-96008, November 2009)

54 of 739
virtual NICs to a target ESX 3.0.x server which only supports 4 virtual
NICs.
● Windows Firewall—Ports 6331, 443, and 22 must be opened on the source and
target ESX hosts. For more information, see Configuring ports.
Note:
In order to use automatic e-mail notification, you must add VI_Service.exe to the
exception list of most anti-virus and spam filters. In addition, you may need to
open port 25 in your antitrust software to allow SMTP e-mail. For more
information, see Setting e-mail notification options.
● Protocols and Networking—Your servers must have either TCP/IP with static IP
addressing or reserved DHCP addressing.
Note:
VMware does not support using MSDE as the database in a production
environment.
Protecting an entire physical or virtual machine using an ESX virtual machine
● Source servers—Source machines must meet the base Storage Mirroring
Recover requirements.
Note:
● Storage Mirroring Recover Virtual Recovery Assistant for ESX must be
installed on the source server.
● The source cannot be running a version of Windows that is newer than the
version on the recovery appliance.
● Virtual Recovery Assistant does not support Windows XP Professional.
● Virtual Recovery Assistant supports Windows 2008 as long as the virtual
recovery appliance is running Windows 2008.
● The source and target cannot both be domain controllers. Only one or the
other can be a domain controller. Ideally, the target should not be a
domain controller or host any functionality (file server, application server,
and so on) because the functionality will be removed when failover
occurs.
If your source is a domain controller, it will start in a non-authoritative
restore mode after failover. This means that if the source was
communicating with other domain controllers before failover, it will require
one of those domain controllers to be reachable after failover so it can
request updates. If this communication is not available, the domain
controller will not function after failover. If the source is the only domain
controller, this is not an issue.