Configuring upgraded vSphere Replication Appliances to support up to 4000 Replications

Products

• VMware Live Recovery

Issue/Introduction

This article applies to upgraded vSphere Replication appliances that use an embedded database. Use the table below to determine whether your vSphere Replication deployment requires additional configuration to enable the support of up to 4000 replications per vSphere Replication appliance.

Please note that versions prior to vSphere Replication 8.4 only support a maximum of 2000 replications

Note: In addition to configuring the upgraded appliance, the maximum number of replications that a vSphere Replication Management Server can support depends on a number of factors in your environment, like bandwidth, change rate, compressibility, RPO, and others. See Requirements to the Environment for the Support of Up To 4000 Replications (KB 2107869).

Deployment Scenario	2000 Replications Support
vSphere Replication 8.1 new deployment with embedded database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.1 new deployment with external database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.2 new deployment with embedded database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.2 new deployment with external database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.3 new deployment with embedded database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.3 new deployment with external database	Yes, but the value for event maximum age must be changed. See the Solution section.

 

Deployment Scenario	3000 Replications Support
vSphere Replication 8.4 new deployment with embedded database	Yes, but the value for event maximum age must be changed. See the Solution section.
vSphere Replication 8.5 new deployment with embedded database	Yes. No need to change the value for event maximum age.

 

Deployment Scenario	4000 Replications Support
vSphere Replication 8.6 new deployment with embedded database	Yes, No need to change the value for event maximum age.
vSphere Replication 8.7 new deployment with embedded database	Yes, No need to change the value for event maximum age.

The purpose of this article is to explain how to modify the event maximum age in the vSphere Replication appliance.

Environment

VMware vSphere Replication 8.x

Resolution

1. Change the value for event maximum age to 3 hours.
   If you plan to replicate more than 500 virtual machines, you must change the default value for event maximum age at the vSphere Replication appliance.
   1. In the remote console session to the vSphere Replication appliance, open the /opt/vmware/hms/conf/hms-configuration.xml file for editing.
       
   2. Change the value for event maximum age to the following:
      <hms-eventlog-maxage>10800</hms-eventlog-maxage>
       
   3. Restart the HMS service by running the following command:
      # service hms restart
       
   4. Stop VCTA service.

      For vSphere Replication 8.1 and earlier versions, run this command:

# service vmware-vcd stop

For vSphere Replication 8.2 and newer, run this command:

# service vcta stop

Note: Stopping this service interrupts the replications to and from the cloud.
 

Note: If a connectivity issue occurs in your environment or the vSphere Replication appliance encounters a problem, the offline or downtime period should not exceed the period set in the hms-eventlog-maxage tag. After the problem is resolved, there must be enough time for the events to be delivered within the maximum age period.