- Network traffic compression: replicated data is now optionally compressed prior to being sent over the network, resulting in reduced replication times and less network bandwidth consumed.
- Linux guest OS quiescing: introducing Linux guest OS quiescing service to provide file-system level crash consistency to replicated Linux-based VMs.
- Network isolation: management and replication traffic can be split over separate networks.
- Increase in product scalability: each vSphere Replication Management Server can now configure for replication and manage a maximum of 2000 simultaneous replications, up from the limit of 500 replications today.
- Performance improvements: numerous enhancements were made to the host-based replication engine to enhance performance and minimize the amount of data that is transferred over the network, resulting in faster initial synchronizations.
- Interoperability with VMware vSphere Storage DRS at the target site: vSphere Storage DRS can now detect replica discs of replicated virtual machines at the target site. When vSphere Storage DRS needs to initiate a move of replica disks between datastores, vSphere Replication will seamlessly and automatically handle the move to the new datastore, thereby eliminating the need for any manual intervention by administrators.
- The vSphere Replication 6.0 release removes the functionality that switches the TCP port for replication traffic from port 31031 to 44046 after the end of the initial synchronization. Replication traffic now uses port 31031 at all times. For the purposes of traffic shaping, customers can use the Network isolation feature.
- Existing replications are not affected during upgrade of vSphere Replication, and you do not have to reconfigure them due to this change. Existing replications will continue to use port TCP 44046 until they are reconfigured for some other reason.
Source VMware Release Note
No comments:
Post a Comment