*************************************************************************
****** Updated information - Mar 31, 2021 ******
****** Check new Maximum for VR 68.4 ****** *************************************************************************
As one of my blog's tradition here’s the updated information about vSphere Replication 6.0
Before we
dive into the product’s operational limits, let’s see what new cool features have
been introduced with VR 6.0
- Linux
quiescing: used to quiesce your Windows boxes to prevent file-level crashing,
now the feature is also available for the Linux ones;
- Full
replication traffic isolation: with new vmkernel portgroups you can isolate
replication traffic from end to end. (I’ll cover that in more details on a future post).
Besides the
new features, we also had some enhancements on the scalability.
The maximum
number of VRS still 10 (9 VRS + 1 VRMS, yes VRMS is also a replication server)
But the
maximum VMs a single VRS can replicate has been increase from 100 to 200.
That means,
using the solution at it’s maximum, you can reach a total of 2000 replicated
VMs.
The old VR
5.1 and 5.5 Operational Limits KB has not bee updated to reflect the 6.0
enhancements, a new KB2102453 has been created instead.
If you are
planning to replicate more than 500 VMs, here’s a few thing to be aware of:
- Adjust
event maximum age at
/opt/vmware/hms/conf/hms-configuration.xml
- On VRMS
upgraded from previsous version the disk size cannot accommodate the internal
database size so you need to increase the disk size too (assuming you are not using
an external DB)
Check KB2102463
for the procedure.
Good
replication ; )
