Hi,
we are using Heartbeat in the configuration physical to virtual.
Now, we have to replace the physical Server. It´s to old and slow.
I didn´t found any helpfull Information in how to replace the one of the Server pairs.
Does anybody know how to do that? Or done it befor?
Thanks
Frank
Hi Jim,
You can use the following KB (VMware KB: Replacing a Windows 2008 Server with vCenter Server Heartbeat installed ), if you plan to replace the physical server with another physical. If you want to use a VM instead, you can just clone it and do the configuration to change its identity to the correct one.
As this KB is older, you will also have to rename the "new" server.
1. with the NICs disconnected, rename it to the name of the replaced server (i.e. primary management name) and add it to a workgroup.
2. after the machine is renamend, connect the NIC and add it back to the domain with the correct management name
Hi,
thanks for sharing. I will see how it could be hepfull for me
Frank
Note: vCenter Server has inter-dependencies with other services. Care must be taken to not break any of these inter-dependencies. As with any major change in your infrastructure, good backups are essential in providing smooth, limited downtime changes.
To move your vCenter Server and SQL database:
Shutdown the VMware Virtual Center Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Take a backup of the SQL database.
If the SQL database is also being moved, create a second instance of your database and use the vendor's tools to migrate the data.
Note: If you are using an Oracle database, create a second instance of your database and migrate the Oracle database schema, vpxadmin. For more information regarding migrating oracle databases, contact your software vendor.
If you are migrating a vCenter Server 4.x/5.x database, you must also migrate the ADAM database. You can migrate this database if the Windows versions in the source and the destination is the same. If not, vCenter might not operate properly and/or the client might fail during connection. For more information, see http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&e...Manually backing up and restoring the vCenter Server 4.x and 5.0 ADAM instance data (1029864).
Create the appropriate System DSN connections on the new vCenter Server host. For more information, see the Viewing and modifying the database server section of vCenter Server installation fails with ODBC and DSN errors (1003928).
Begin the installation of the vCenter Server software on the new server. If you are installing vCenter Server in a virtual machine, see the vCenter Server and the vSphere Client Hardware Requirements section of the ESXi Installable and vCenter Server Setup Guide and Technical Resource Center for guidelines to deploy vCenter Server in a virtual machine, including sizing, installation, functionality, and configuration of VMware High Availability (HA).
When prompted, select Use existing database, and provide the correct credentials to that database.
When prompted, select to not re-initialize the database to preserve all of your inventory data.
Hi Fillips, the procedure that you indicate above does not apply to replacing one of the two vCSHB nodes, but it is intended for the case when you want to migrate vCenter from one server to another, and it is not protected by vCSHB