We are using it for disaster recovery.

Zerto provides near-synchronous replication, but more importantly, we can see the status at seven seconds, six seconds, five seconds, and four seconds when we log in to the Zerto console. I found that amazing. There is probably no other disaster recovery solution available in the market that is providing this functionality. It is great and definitely a huge plus point for Zerto.

We do get alerts if suspicious activity is detected on a VPG, but we did not get an actual case where there was ransomware or any other kind of attack and we had to prevent that. I have not come across that with either of my clients, but we do get alerts when Zerto finds something suspicious. We go in and look at it. In some instances, because the application was writing more files, Zerto marked it as suspicious, but we never had to do recovery for security reasons.

We use Zerto with AWS as the target. We do the failover of the on-premises VMware virtual machines to the AWS cloud. I do not deal with the implementation. I only do the administration of the tool, but whatever I did as part of AWS administration in Zerto, it was pretty seamless and straightforward. I did not get any issues there. The documentation is helpful in identifying any issues.

We have about 70 virtual machines that are being protected by using Zerto. Zerto has drastically improved our RPO. It was 15 minutes previously, whereas now, it is in seconds.

Zerto has not had much impact on our RTO. RPO has changed, but RTO has been the same for us.

Zerto has not helped to reduce downtime in any situation. We have only done tests. We have not done any actual production failover because there was no need. Similarly, Zerto has not saved us any recovery time because we never had a requirement to do a recovery since we implemented the tool. It is a pretty new environment for us, so we have not had time.

Zerto has not reduced the number of staff involved in overall backup and DR management. It has remained the same for us.

The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover.

As a power user, I find the customization lacking. I feel it could be customized a little bit more, but Zerto is simple to use. It is easy to use. That is my main reason for using Zerto.

I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved.

The UI does crash a lot, and that is something that can be improved.

It has been about a year. I support multiple clients with multiple backup and disaster recovery products. I was a Storage and Backup engineer, but now, I am covering the solutions for the entire infrastructure. I work on Zerto for multiple clients. We have two clients who are using Zerto as a disaster recovery solution.

The UI does crash, but it does not affect the functionality of the software.

It is scalable. There could be 10 machines or 100 machines. I did not find any issues. It is pretty scalable.

There were some issues for which we had to get responses from them. They were pretty much on the point. There were no issues. The response time was a bit slow, but their support was pretty good. I would rate them an eight out of ten.

We used to use Azure Site Recovery to protect all of the production instances, SAP databases, some file servers, and some basic application servers. We used to first replicate to Azure and then do a test failover and a production failover. It was a bit slow. The RPOs and RTOs were not that great, and the rate of change that Azure Site Recovery supported was not completely meeting the business requirements. The third part was that Azure Site Recovery was not application-agnostic. What we loved about Zerto was that it was application-agnostic. It did not matter to Zerto what was running behind the application. It will replicate everything across any cloud. That was our main point for going for Zerto.

Zerto was also much easier. Azure Site Recovery was a little bit hard to set up and maintain, but Zerto is pretty straightforward and easy.

I did not find much difference between Zerto and other solutions in terms of the speed of recovery. The RPO is great, but when we do a failover, it is basically the same as any other solution.

Zerto has not replaced our legacy backup solutions. Our legacy backup solution is in the same place. We are only using Zerto for DR.

Our environment is hybrid. We are using Zerto to protect our on-prem as well as the cloud environment, but I was not involved in its deployment.

In terms of maintenance, I never had any requirements to maintain it.

Evaluation was done by someone else in the organization.

I would rate Zerto an eight out of ten. Simplicity is an advantage, but customization and reporting can be better.

A lot of our focus area has been around capacity planning that includes virtual machine rightsizing and then construction for failover and resiliency-type models. The other area that is important to us is looking at data in motion, data at rest, and data in transit.

By implementing Zerto, we wanted to be able to go ahead and focus a lot on workload migration and disaster recovery.

I can quickly restore data by reverting anything with more or less a nightly backup. I can pretty much have the data through recovery checkpoints, and each of the checkpoints can only be around five seconds apart.

When I need to work a lot with VPGs, it has a lot of capabilities for that. Monitoring is also very important for us. We do work with Splunk, and I am looking a lot around for logs, metrics, and traces. The capabilities that I get are system throughput, and CPU and RAM input/output.

I have used Zerto for immutable data copies. I have pretty much followed a 3-2-1 strategy. We have three copies of production data and two backup copies. We have two different media and then one off-site copy. It has this offering there.

It's helping very much in terms of the malware. They have a ransomware protection capability.

I have used other solutions jointly with Zerto. What is happening is that they have a focus on isolating and locking with a cyber resiliency vault, and what I have been doing more or less around the vault is working with the Delinea Privileged Access Manager solution. So, some areas have intersections with other tools in our stack. I would love to continue seeing more use cases out of Zerto so that I do not have to defer this anywhere else.

It has enabled us to do disaster recovery (DR) in the cloud, rather than in a physical data center. I think of it as a cloud migration tool. Having DR in the cloud is very important for our organization. I use it with Microsoft Azure.

With Zerto, I have seen five-second near-synchronous replication, so there are thousands of checkpoints in one day, and then afterward, I can have a periodic backup. I can space it out between twelve-hour snapshots. We can have one to three checkpoints per day. I can recover to the state seconds before any sort of attack, and I can utilize Zerto's in-built orchestration and automation. I could easily fail over the entire site without any sort of disruption. Those are the things I see very much in terms of positives. There is a lot of information that it can gather with synchronous replication. The other thing is that I have seen other disaster and backup service offerings, and they very much focus on getting a container image installed or some sort of binary file and then deployment from there afterward.

I find it easy to migrate the data. Once somebody understands how Zerto works, particularly around areas for analytics and automation, with the reference architecture, they will be able to quickly deploy it.

I see a lot of visibility in terms of proactive management with SLA monitoring, run metrics, and other things. We are able to test infrastructure using live and personalized data. It, in turn, becomes very much of a team effort.

Zerto provides complete visibility in terms of storage and consumption data. We get to know the capacity and application volumes. I can also address compliance aspects, such as PCI DSS which is important for us as part of the RPO.

They have an intelligent, predictive infrastructure, so I can just pretty much determine the required compute storage and other server networking resources, whether it is on-premises or in the cloud.

It also saves recovery time. We pretty much monitor that information. In terms of time savings, we are able to ensure that we can set up a backup quickly, figure out the integration details with the use of APIs, and meet our requirements around client security. Afterward, there is the cost consideration. Better documentation on the restoration process would be helpful.

Ransomware is one area where we are using Zerto. If we were utilizing another solution, that might have only been AWS-specific, and we might have not gotten much assistance in proceeding with their public cloud vendor as a result. We might have to figure out what we can do around working with an XDR or another mode of ingesting that data for any vulnerabilities and how to focus on encryption thereafter. If we were to consider another vendor, some of them may not have support for Azure. They might be AWS-focused.

Zerto has helped to reduce our organization's DR testing. We can create failover tests seamlessly, and we can do this routinely. We are able to save time and look at how we can discern between RTO and RPO.

Zerto has not reduced the number of staff involved in overall backup and DR management. Our team size is still roughly the same. We have not seen our headcount change as a result, but we do not need to hire external consultants to support a project.

If I wanted to focus on operational recovery, which may be recovering instances in the database with a 15-second data loss, there are systems administrators designed to take care of that. With Zerto's offering, someone can utilize the Zerto solution as opposed to depending on any sort of manual human intervention.

The continuation to the public cloud has been especially helpful where I can pretty much work with things like hosts and clusters as part of the data center.

Zerto has near-synchronous replication. I like it very much. They had an acquisition and are now a part of HPE. I see it very much as a robust solution.

A slight disadvantage of Zerto is that it requires the Windows Server operating system as the base OS. Over time, I would like to see more offerings in that regard. There should be more deployment options other than just the Windows operating system.

The implementation is very quick and painless, but it would be good to have more information that is not case-sensitive. In the server portal, some fields are case-sensitive. It took some time for me to understand initially.

If a VPG goes down and an application host is not responding, I want to have a little bit more flexibility to automatically point the recovery to other hosts. I would like to see a little bit more flexibility to automatically sustain two applications in their most optimal state. If the VPG is going down and any of the recovery hosts are in maintenance mode, there should be a way for maximum flexibility so that it can automatically utilize Zerto to point that recovery to other hosts.

I want some more information about how to work with bare metal drives. I have been doing some work in capacity planning for using MDM and FormFactor cable and then looking at system throughput, App latency, and a lot of scripts in Linux. I would like to have a little bit more information for anybody needing to work with bare metal drives.

I have been using Zerto for several years.

I have not seen any service disruption that impacted us. If anything like that were to occur, they would communicate it ahead of time.

It is scalable. We have more than 20,000 endpoints.

I do reach out to Zerto, and if there are any questions, we have a ticket in-house, so everyone is working on reviewing it at the same time. I would rate their support a nine out of ten. There are no negatives.

We were not using a similar solution.

By bringing in Zerto, some legacy work has been discontinued. There is operational recovery, application migration, and application cloning. These are the three areas where Zerto has helped us.

We have a cloud version. It is a public cloud.

Its initial deployment was straightforward. I have been trying to focus on capabilities and encryption and how a long-term retention repository works, at least looking at the data capture. Another thing is utilizing some information with APIs and cloud scaling. I have broken down a lot of my use cases, and we have Zerto on the public cloud. Based on that, I was able to figure out how to work with features like compute as well as storage.

Its implementation took about two to three months. In terms of maintenance, it requires maintenance. We focus a lot on metrics such as RTO and RPO monitoring. Somebody can also put it in maintenance mode operation.

We had Zerto representatives, and we also had work done in-house.

I work with a team. Other colleagues are also involved in the effort. We have a team of around ten employees.

We did look at a few other vendors' offerings, but we decided on Zerto. Our organization has a partnership with them, and the other thing was that there were a few industry events, and they were able to effectively make a pitch. Their demonstration was very effective. It was also something in which the client was interested in.

To those looking to implement Zerto in their organization, I would advise creating use cases of their own and then trying to see how Zerto effectively helps them. A few areas where they can work are gathering information with the virtual machine rightsizing and being able to go ahead and create resiliency models. Afterward, they can look at compliance. For us, PCI DSS and locating the public cloud environment being used, which in our case was Microsoft Azure, were important. After they have created use cases on their own, they can come to Zerto and see how they are able to effectively handle it. If they are able to think through what they need, they can come up with specific questions and then get Zerto to effectively deliver.

I would rate Zerto a nine out of ten.

We use Zerto for our application data recovery.

Zerto's near-synchronous replication delivers exceptional results. The data at our recovery site is kept nearly identical to production in real-time, minimizing data loss to near zero.

By utilizing Zerto's immutable data copies and adhering to the three-two-one rule, we have established a highly effective recovery strategy.

While Zerto doesn't inherently block unknown threats or attacks, its detailed history logs enable us to revert to a pre-attack state, essentially restoring a clean system.

Our production machine experienced changes that caused the application to crash. To resolve this quickly, we restored the machine to its previous state using a recovery copy located at the recovery site that was made by Zerto. After powering on the restored machine, we changed its IP address, making it accessible again.

Zerto has a positive effect on our RPOs.

It boasts impressive recovery speed. As a customer, all we need to do is power on the machines at the recovery site - that's how simple and fast it is. Even if the recovered state isn't ideal, we can easily rewind to a specific point in time and power up another instance of the machine at that moment.

Zerto makes it easy to migrate data. The total configuration is user-friendly.

While our current RTO is three hours, Zerto can significantly reduce it to just five minutes.

Zerto helps us significantly reduce downtime during hardware failures, software updates, and natural disasters.

While we haven't experienced a ransomware attack, we have a recovery plan in place. If one were to occur, we could quickly restore production to a previous point in time, minimizing downtime and data loss.

Zerto helps us reduce the amount of disaster recovery testing we need to perform, which also allows us to reduce the number of staff required for the testing down to two.

The Zerto application is licensed per VM. However, the amount of data stored on each VM does not affect the licensing cost. Whether we have terabytes or just a few bytes on each VM, the licensing fee remains the same. This means we only pay for the machines we are replicating, which can lead to significant cost savings.

Real-time replication is a valuable feature, ensuring that changes made to the production site are immediately reflected at the recovery site.

Another feature I appreciate in Zerto is its detailed logging. This functionality allows us to easily access past data and reconstruct the machine's state at any given point in time.

We can recover the replicated machine at the recovery site by simply clicking it back up from the replicated machine. This allows us to keep the original machine running while the recovered machine is active. It's also vendor-agnostic, meaning it works with different hardware vendors like HP or NetApp. In other words, Zerto adapts to the specific hardware we have regardless of the vendor.

Zerto's solution could benefit from additional security features, such as malware scanning tools at the recovery site.

I have been using Zerto for five years.

Zerto is stable.

Zerto is scalable. We just need to add a license and they provide a new key.

The technical support team offers an excellent service. They empower customers by providing comprehensive documentation and guidance, helping them resolve future issues independently.

The initial deployment was straightforward, and I handled it independently. My only reference was the provided documentation; I required no further assistance.

Zerto's pricing doesn't depend on the number of virtual applications. Even if we have a server with 200 terabytes of data, we'll only pay for protecting that single server, not for the total size of the replicated data. This simplifies our cost structure.

The licensing cost is fair.

I evaluated Veeam and SIM before choosing Zerto. Zerto's interface is much easier to use than the other solutions I tested. Integrating into our environment is also seamless.

I would rate Zerto a ten out of ten.

No maintenance is required.

You can save a lot of time researching solutions by choosing Zerto. It's efficient, easy to deploy, and easy to maintain. Additionally, Zerto offers excellent support, including comprehensive documentation, breach and RCM coverage information, and a knowledgeable customer support team.

Implementing failover to a secondary data center is crucial for ensuring business continuity in the event of primary data center loss. This strategy involves automatically redirecting operations and services to the secondary data center when the primary one becomes unavailable. This not only minimizes downtime but also enhances overall system reliability.

The failover process requires robust synchronization mechanisms to ensure data consistency between the primary and secondary data centers. Regular testing and monitoring are essential to validate the effectiveness of the failover mechanism and identify and address any potential issues proactively.

In summary, failover to a secondary data center is a strategic measure to safeguard against disruptions, offering a resilient solution for maintaining seamless operations in dynamic and challenging environments.

Zerto has significantly enhanced our organization's resilience and data protection capabilities. Its real-time replication and failover features have played a pivotal role in minimizing downtime during unexpected events, ensuring business continuity.

The platform's automation and orchestration capabilities have streamlined our disaster recovery processes, reducing manual intervention and accelerating recovery times.

The point-in-time recovery options provided by Zerto have proven invaluable in mitigating the impact of data corruption or accidental deletions. This has bolstered our data integrity and provided a safety net against unforeseen data-related issues.

The live failover tests and point-in-time recovery options have been exceptionally valuable features of Zerto for our organization. Conducting live failover tests allows us to validate the effectiveness of our disaster recovery setup in a controlled environment. This feature ensures that all components are in place and functioning as expected, providing confidence in our ability to respond to real-world disruptions.

Additionally, the ability to choose a specific point in time for recovery down to the seconds is crucial for data integrity. This granular control allows us to roll back to a precise moment, mitigating the impact of data corruption, accidental deletions, or other unforeseen issues. It adds a layer of precision to our recovery process, minimizing potential data loss and enhancing overall resilience.

The product could benefit from improvements in automation, specifically in the area of failovers. Currently, the process is largely manual, and introducing automated failovers after a certain time threshold would enhance efficiency and responsiveness. Automated failovers can reduce the dependency on manual intervention, allowing for quicker and more proactive responses to disruptions. In the next release, the inclusion of scheduled or automated failovers would be a valuable addition. This feature would empower organizations to set predefined parameters and triggers for failovers, ensuring a timely and automated response to potential issues. It not only streamlines operations but also adds an extra layer of reliability to the overall disaster recovery strategy.

I've been using the solution for six months.

We did not have a solution before.

We had great help from the company in terms of setting up our environment.

We implemented through a vendor; I'd rate the experience ten out of ten.

Anything is the worth the cost for virtually no downtime. Time is money.

We did not evaluate other options.

It is a great solution overall, however, it could use some upgrades with automation.

We use the solution for replicating VMs from our on-site VMWare sites to both Google Cloud and Azure clouds. This allows us to feel confident not only in our disaster recovery capabilities but also in testing applications from our on-site data center to isolated cloud instances where there won't be any IP address or domain name system conflicts.

The continuous backup gives us a better point in time recovery. It also reduces the amount of bandwidth to move the Zerto VM data from site to site, and we like that.

Zerto has improved our organization in several ways, particularly in the realm of disaster recovery, data protection, and business continuity.

With Zerto's near-zero recovery time, our critical applications and services can be quickly restored, minimizing the impact on business operations.

The data replication ensures that there is a consistent and up-to-date copy of the information. This helps protect against data loss and ensures data integrity. With Zerto's single pane of glass, it's easier for IT administrators to monitor and manage their disaster recovery and data protection strategies. This has led to more efficient operations and reduced administrative overhead.

Zerto supports multi-cloud environments, allowing our organization to replicate and protect our important data across different cloud providers and sites. This flexibility has benefited our businesses with our diverse cloud strategies and our on-site data centers in different locations.

Zerto helped our organization meet compliance requirements by ensuring data protection and recovery strategies align with our regulatory standards.

Additionally, Zerto has incorporated security features to safeguard the replicated data.

Zerto needs to improve its documentation. It seems like some documents are copied from other older documentation, with misleading screenshots or incorrect steps.

This can be confusing when newly introduced to a product or in a crisis situation such as a disaster recovery test or a true disaster recovery. The documentation needs to be revised, reviewed, and registered to be correct. Perhaps Zerto should consider an outside consultant to review and approve any documentation that is released.

I've used the solution for about a year.

It's very stable, and we have had no issues.

it does scan well and does what it claims to do.

Support needs to be more flexible.

We have only used vRealize.

The documentation was confusing and, at times, incorrect.

We handled the setup in-house.

I don't any ROI information.

I'd advise others to start small.

We also evaluated Veeam.

We utilize the solution for our primary backup and recovery source. We use VMware for all of our servers.

With the ease of integrating with our complete virtual infrastructure, it is nice that we can replicate easily between our HQ and DR sites.

The flexibility in utilizing the test environment to allow production servers to be test restored with no interruption to the actual production server in use is really nice for quick and efficient testing.

I highly recommend it for companies using virtual infrastructure.

The product allows us to restore to any given point within 15-20 second increments, including just files and whole servers.

It allows us to efficiently test restore and restore files that were accidentally deleted within seconds of the deletion, giving the option to have the most up-to-date file restored with little to no data loss.

It also allows reporting on the results of the testing, which can be provided really easily for board reporting, as well as auditing. There are many great features for sure.

The LTR function has by far been the best feature to allow us to retain our backups for at least a year. Also, it allows us to have full monthly and weekly incremental backups for that year, which can be restored or even just files from that period. It has come in handy for those accidentally deleted files.

It also helps us keep our required retention period for specific documents and allows us to recover older documents if we have to compare and recreate those.

We would like the LTR function to be able to retain the past 12 months. Before the update to version 9, we could do this in the GUI. I am hoping that in version 10 (which is on the roadmap to be installed), this feature will return in the GUI to provide an easy way to lengthen our retention. The journaling can also be a problem at times. Also, I'm not sure why, however, retention processes randomly fail and have to be rerun periodically.

We have been utilizing this solution since 2017.

We use Zerto for offsite disaster recovery. We have over 70 VM servers, several of which are our mission-critical servers that are replicated to our VMware hosts at an offsite location.

We also replicate our Citrix environment and Disaster Recovery Zen App servers with Zerto to our offsite location as well. Most of our servers are Windows-based operating systems. However, this doesn't matter because we are replicating the VM servers. Further down the line, we may invoke extended retention for some of our more important servers.

It gives us peace of mind that our data, servers, and environment are protected. We can easily restore VMs quickly and have confidence that the replicated data will be current.

We are able to show proof in tests, reports, and live data to our owners, showing that our most sensitive data and servers are being replicated to an offsite facility, and we can restore it in case of a natural disaster or from our system being compromised by ransomware.

Our IT staff can easily navigate through Zerto and test failover, see if there are issues with replications, and create offline copies of the data.

Being able to test our VPGs and prove that our disaster recovery setup is in place and functional.

Our business owners can be assured that our data is protected, and in case a serious problem occurs, they know that we will be able to recover easily.

Zerto is fast to restore our mission-critical servers when needed. We also use Zerto to make copies of our VM servers for our offsite Citrix Zen App Servers. Zerto has helped simplify the process of disaster recovery setup and made the tasks more efficient for our IT Staff.

Zerto could add text alerts if there are critical problems and alerts if changes affect our replication. We do receive emails, and they will alert us to issues that we are having with VPG SLAs.

I don't have any complaints about Zerto, and I hope they continue to develop new features. If they had classes on using Zerto, that would help with onboarding new IT staff. They may already have them, and I am not aware that they do. Overall, Zerto works out great, and they do a good job.

I've used the solution for five years.

For one client, the use case was to facilitate data center migration, and for another client, it was for failover and failback of the data center for DR. We wanted to have controlled failover and failback of related applications for DR.

We have not used it for disaster recovery in the cloud. Everything has been on-prem so far.

Zerto helps in automating disaster recovery capabilities. It allows automation and orchestration of complex activities.

We have used Zerto to help protect VMs in our environment. Zerto’s overall effect on our RPOs has been pretty good.

It has also been effective for our RTOs.

Zerto has helped to reduce downtime, specifically for failover and failback, but it is hard to qualify the time saved.

Zerto has not saved us time in a data recovery situation due to ransomware or other causes because we have not been impacted by any such issue.

Zerto has helped to reduce the organization's DR testing. There is about 20% reduction.

It has also reduced the number of staff involved in a data recovery situation, but I have not seen any reduction in the number of staff involved in overall backup and DR management.

Its ease of use and scalability are valuable.

I also find the near-synchronous replication to be valuable. It is extremely important for organizations.

There should be more comprehensive cyber recovery capabilities.

I have been using Zerto for two years.

It is stable.

It is scalable. It is deployed across multiple locations. There are roughly about 4,000 VMs.

We might use it to migrate to cloud solutions. It is to be decided.

I have not reached out to them myself.

We were using SRM. We switched to Zerto for automation.

Zerto is highly effective in terms of ease of use as compared to other solutions. Zerto is also pretty effective in terms of its speed of recovery.

We can easily migrate data using the Zerto console.

Zerto has not yet replaced all of our legacy backup solutions but it will.

Our setup is all on-premises. I was involved in its deployment to some degree. It was pretty straightforward to deploy.

It took about three months. It was an enterprise-wide solution.

It was a combination of in-house staff and a third party. The third party was a VAR or value-added reseller.

It required just a handful of staff for deployment. It does not require any maintenance from our side.

We have seen an ROI, but I do not have the metrics.

It is not a bad pricing model.

We evaluated other options on paper, not physically.

Zerto is an effective tool for automation and orchestration of complex activities.

The biggest lesson that I have learned by using Zerto is the need for application involvement and defining protection groups.

Overall, I would rate Zerto a nine out of ten.

We implement Zerto as a part of a Disaster Recovery process for our valuable customers, in various environments. Most of them consist of two sites owned by the same customer, connected with campus or wan link, but both using VMware virtualization platform.

Recently we realized a dedicated infrastructure in our Datacenter, then started to propose to our customers DRaaS using those resources as a recovery site and including dedicated 24x7 support.

Few customers use the public cloud (Azure) as a recovery site: we could only implement and configure the solution or fully manage it because we are also a Microsoft Gold and Tier-1 partner.

Zerto helps reduce downtime in a wide number of situations because it can bring up an entire environment of 40-50 VMs in minutes.

Zerto helps to save time in a data recovery situation too. Some customers experienced VM or database corruption: using the solution's checkpoint feature, the data recovery happened within five minutes or less. A normal restore would probably be two to eight hours depending on if we had to restore from disk/tape and need or not need to apply logs.

Zerto is great at DR testing. We can spin off critical VMs or an entire environment pretty quickly and have users test against this copy with no production environment impact.

Its overall impact on our RTO has been great. It took a few hours in a very complex environment. The customer was very impressed with Zerto when we started with the PoC and then put it in production. It is great.

Zerto has reduced our downtime. Customers have minimal downtime.

We have been enabled to automate tasks with Zerto. Staff can now be dedicated to other tasks.

A great Zerto feature is the non-intrusive failover of the application, similar to an actual disaster recovery test without impacting the services that are currently online. Sometimes customers need to failover to an isolated environment and validate an application without impacting the production environment: we can achieve this goal with Zerto. Again, we can do regular testing in a non-impactful way using isolated testing. For customers of our DRaaS we include once a year, a live test that is more like what would happen if the customer lost the production site.

Eventually, the VPGs (Virtual Protection Groups) allow to grouping of one or more VMs into a single entity, ensuring every point in time inserted into Zerto’s journal (a checkpoint) is from the same point in time for all components within the protection group. This allows easy recovery of an entire application and its dependencies to a consistent point in time.

Zerto is also a very easy product to use.

We started using it a few months ago for immutable data copies for a few customers on multiple repositories like HPE.

Zerto's ability for blocking unknown threats and attacks is key in our disaster recovery process. It's the technical solution where we implement all the data. It is also the recovery plan for our customers.

We have tried experimenting implementing Zerto with the the disaster recovery site on cloud. We use an Azure. It's very useful. Zerto has enables us to do disaster recovery in the cloud, rather than in a physical data center.

We've only used Zerto two or three times to migrate an existing data center to a new one because the hardware under the machine was from a different brand. We used Zerto because the environment is quite complex and the migration using other tools did not fulfill the customers' needs. Zerto is very good at data migration.

One of its best features Zerto is the ability to maintain the data of multiple VMs using Vipro Protection Group. We can aggregate multiple VMs in a workload for specific services. They are protected at the same time.

It's very easy to manage and monitor our DR plans with Zerto. It's very easy to learn and operate. It's easier than VMware.

Zerto could be considered as a backup product but this is not true. So if we could consolidate and use Zerto for disaster recovery as well as everyday backup and restore for situations where we need to recover something, that would be helpful. Anyway, we think that Zerto will win with no competition in the Disaster Recovery process, so we stay focused on this.

Now we are testing version 10 which include real-time ransomware detection, a new Cyber Resilience Vault and enhanced cloud capabilities and security: we expect more from these features for superior hybrid cloud security.

Reports could be useful for customers. I would like to have a report that shows the latency for every single internal VM. it would be useful for troubleshooting.

We started to evaluate Zerto about three years ago, then we implemented it for our valuable customers who need affordable solutions in their disaster recovery processes.

We haven't had any issues with any of the builds or the virtual managers, especially with the new "appliance" mode. It just runs.

Zerto is a very scalable solution. We can create as many protection groups as customers need for their environment even as they growth.

Our customers are mostly medium to small sized enterprises.

We use Zerto Quick Start service for the first installations and we use it in very complex environments: great.

We are very satisfied. We had to use it at the beginning to understand the implementation process and what we needed to do.

They are quick and professional.

We previously used Veeam (B&R + DRO) and VMware (Replication + SRM), but they could not offer all the features of Zerto.

We also sometimes still use VMware Disaster Site Recovery Manager in conjunction with VMware Backup and Recovery.

The implementation is very straightforward. Must be considered security and lay out the network infrastructure to be more efficient.

But from the standpoint of installing and deploying the product, it's very simple.

Pricing is adequate at the standard of the product, but there could be "always" some improvement. We would like to see a consumption model that would charge in a DR scenario, where you're failing over and consuming those resources, instead of a per-protected-node model.

My advice is to look at what you're trying to accomplish: with Zerto you could combine resilience, mobility, and protection into a single software-only solution. It's hardware and hypervisor agnostic as to whether you're using VMware, Microsoft, or Azure.

We have built a disaster recovery landing zone in our Datacenter and we built an isolated environment so we could do non-intrusive failover tests, and still keep customers' production environment up and running.

We have recently introduced the immutable data copies feature, because of the issue of cyberattacks and because even backup systems could become corrupted and then this is still a bad situation. The ability to look at the data that is being replicated in real-time and scan it, in conjunction with immutable data, and putting that into a vault, would be a great benefit.

The 3-2-1 rule isn't so important for us when it comes to disaster recovery. We consider the backup process and then the disaster recovery process. We treat them as two different workloads that we could implement to our customers to solve different issues.

The majority of our customers use it in a hybrid environment, but they prefer to use disaster recovery in their own data center. In some cases, we provide disaster recovery as a service, where the disaster recovery site is in our data center.

Doing a proof of concept is the best way to implement and sell Zerto. The customers don't always trust our advice but when I start with a POC in their environment, they see it's benefits.

We use Zerto to verify the information being transferred from one data center to another.

When a site is down, we can continue to use the other site thanks to Zerto.

The near-synchronous replication is extremely valuable because it ensures we can continue working.

The move action between the app and data center is great and we can see the benefits in minutes.

Our RPOs are performing well thanks to Zerto.

Migrating data using Zerto is easy.

Zerto helps our users collaborate during data migration.

Our RTO using Zerto is good.

The communication between the VM and the secondary data center is the most valuable feature.

I would like Zerto to provide more detailed information when there is an issue.

I have been using Zerto for five years.

Zerto is extremely stable.

Zerto is scalable.

I have used the technical support of Zerto several times and they are good.

Though I wasn't part of the initial deployment, the procedure is relatively simple. Manager rollout is the first step, followed by CPG installation on VMs by the CPG teams and subsequent network configuration verification.

Four people are required for the deployment.

I would rate Zerto a nine out of ten.

Zerto is a good solution for transferring data between centers.