Near-synchronous replication has some trade-offs. With near-synchronous replication, we get almost all the information up to date at the destination site, but the trade-off is that sometimes that could take a lot of CPU cycles, network bandwidth, and troubleshooting. A few versions back with Zerto, there were some bugs in the software that were causing constant replication back and forth that was driving a lot of network bandwidth utilization over the network, and we did not know why until we found out it was a bug. It depends on what your business or application really requires. If it requires near-synchronous, you have to enable that. However, if Zerto can make it easier or have a smaller footprint by sending larger payloads or having network compression, it will be a little bit easier. On wide area networks and local area networks, that would definitely be preferred. We have had some issues running Linux virtual machines on the new version. There were some issues with virtual replication adapters on Cisco UCS hosts running VMware vCenter 8. There were several things we had to do with installation and getting the replication adapters to work. Integration with Keycloak for Active Directory authentication using new Linux VMs was challenging, but it is now functioning well.
