I like the user interface the most about HPE Zerto Software; they did a fantastic job. There are solutions that I had to teach myself that have nothing intuitive about them. The user interface could almost allow someone with IT knowledge elsewhere to get started on day one post-deployment because of how HPE Zerto Software lays everything out. Ease of use, the user experience within the web console, and the resiliency make it such a great product. I have also used it to convert people from a VMware environment to a Hyper-V environment, changing hypervisors and getting off of Broadcom's new subscription model. It converts and deploys a VM from VMware over to a Hyper-V host and makes it a Hyper-V VM, which is very impressive. The biggest thing for anybody using HPE Zerto Software is the planning, as that is the hardest part. It involves saying that these are the VMs you want to protect, here is their current IP addresses and network info, here is the destination, and this is going to be its destination IP address and destination network info. You pick your data stores and choose one for journaling. As long as you plan and know exactly what to do and how to roll back in the case of an event, which is another thing HPE Zerto Software can help out with, it makes it great. HPE Zerto Software works, and it is not hard to implement. It could be a little tedious if you have a lot of VPGs with a lot of unique VMs that are going to all have unique settings, and then you have to configure each VM within that VPG. The virtual protection group can be set up for a bulk of VMs with the same settings, and with one button, you could test it and have it fail over. You then have time to commit before, so you get to check out the VM on the destination side, and before you hit commit, you make sure it looks good, hit commit, and then it is off of production and onto DR. You then do reverse protection. It is really an all-in-one DR solution. In my opinion, customers do not really need to invest more past HPE Zerto Software except at the storage array level, which is outside of HPE Zerto Software. I think the near-synchronous replication feature of HPE Zerto Software is good. Async replication is good when you have a subset of VMs that are not moneymakers or your top tier because async, depending on the interval set on it, will sync, perhaps once a day or two times a day. However, there are some VMs that need synchronous replication, which is live time pretty much. Async has its place and needs to be there because there is less bandwidth going over the wire with async as opposed to having every single VM in your vCenter synchronous live time with every write and every IOPS going over the wire. Async will give your bandwidth a little bit of a break, depending on your scheduling of how often you want it to sync.