![]() If you are replicating to a second vCenter Server you will need to deploy a vSphere Replication appliance in that environment as well. Depending on where you are replicating to there might be some additional steps required. Now the vSphere Replication appliance is ready to be powered on. Click “Next” on the vService bindings, when the binding status is “ok”.Provide an administrative “password” and enter the “Networking properties” and click “Next”.Select the “Network” it needs to be connected to and click “Next”.Select the “Datastore” it needs to be provisioned to and click “Next”.Select the “Name and folder” this virtual machine will needs to be placed in and click “Next”.If you agree “Accept” the EULA and click “Next”.As a source I select the ova file I downloaded, now click “Next”.Right click the cluster object and click “All vCenter Actions” -> “Deploy OVF Template”.Go to your cluster under “vCenter” -> “Hosts and Clusters”.I downloaded the vSphere Replication virtual appliance and imported and configured it in just a couple of steps using the vSphere 5.1 Web Client: I am going to assume you have “vSphere Replication” traffic enabled on a VMkernel NIC, if you do not know how to create a VMkernel NIC check this article This makes installing and configuring it a matter of minutes. ![]() For instance the database is now included in the appliance and it isn’t as DNS sensitive as it was with 5.0. ![]() I have used vSphere Replication in 5.0 and it was nice, but with 5.1 the installation and configuration process has been improved. (Make sure to read the what’s new paper) The reason for it being is that it now brings “advanced” technology to everyone (Essentials Plus and upwards). One of the coolest features that has been included with vSphere 5.1 in my opinion is vSphere Replication. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |