Questions for Configuring vCenter Heartbeat in differrent sites

[vvermani]

Hello,

We are planing to deploy VMware Heartbeat v6.3 in our Virtual Environment v4.1U1 soon and the configuration would be as follows :

1. Two DataCenters in differrent locations with 10 ESX host each site.

2. One Virtual Center (with SQL DB on differrent server in Site A)

3. The DC(integrated DNS) and VC are all running Windows Server 2008 R2

4. Network Communication between sites direct link 4GB Fibre Channel (with firewall in between) and VC would have differrent IP configuration, Example :

Site A : Primary Virtual vCenter (with DB configuraed on a different Server in the same site)

IP : 10.5.0.__

Subnet : 255.255.255.192

SITE B : DR Virtual vCenter

IP : 10.10.0.__

Subnet : 255.255.255.192

Both the Primary and Secondary vCenter Servers are going to be Virtual.

I am setting up VMware Heartbeat the very first time and have gone through Hearbeat Install Guide in breif(not completely) but I have few questions as follows :

=============

1. I am not a network specialist but first of all is it possible to setup Virtual Channel with the the above IP configuration ?

2. If yes, then what would be the best option to move ahead with :

(A)Identical or Non-Identical configuration ?

(B)Pre-Cloned and Install Clone ?

3. The vCenter Database is on a differrent SQL server however the same server also holds differrent other application Databases as well, will the Heartbeat Protect the Virtual Center Database or the Complete SQL Database (which we don't want).

Licensing :

========

We could have gone with 2 vCenter Server in each site and configure them with Link Mode however we had 2 Licenses for Heartbeat therefore we thought we would make use of them rather than buying another vCenter License.

1. Having said that does the Primary and the Secondary both require 2 differrent licenses or the Secondary server pulls the license from the backup configuration files created by the Primary Server ?

2. Would we need a differrent License to Protect our Virtual Center SQL Database which is on a differrent Server or the same License earlier for protecting vCenter can be used ?

Thanks in Advance

[godra]

HI,

Maybe it would be best if you would read Hearbeat Install Guide. From what i know there you will find you're best answers. And be carefull when reading it at the Notes that are displayed in the pages.

Regards.

[vvermani]

After a month research/testing different configurations, getting firewall ports opened, finally got VMware Heartbeat working

For people who are looking for info on the questions I had:

=============================================

• Yes, it is possible to configure Heartbeat in different sites that have different subnets over firewalls
  
• Heartbeat v6.4 is the only Multi-identity released over WAN for the above requirement
  

Licenses required:
==============
1 vCenter
1 Heartbeat

Following Configuration worked flawlessly:
===============================

Configuration: DR – WAN, Virtual to Virtual

Cloning Technology: vCenter Cloning before Installation

Domain Controller\DNS: Windows Server 2008 R2
Protection : vCenter only

Also, would suggest going through the following Kb as it was a pain to change IP addresses and getting the firewall ports open again :
=============================
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200492...

Lastly, Heartbeat does not update DNS Host A records dynamically if you are running Windows Server 2008 R2 - which I got resolved by “Disabling RPC for DNS”, command as follows :
==============================
dnscmd /config /RpcAuthLevel 0

MCP | MCITP | VCP 3,4,5

Please award points if you find the above helpful