We use it mainly for our disaster recovery, so we replicate our production VMs between our data centers.

The solution meets our high availability and disaster recovery needs.

The disaster recovery reviews itself and it has the ability to fail over within seconds and get new machines up and running on a new data center in a matter of minutes.

It's pretty easy to use. It depends on how detailed you get into the product. If you get real detailed into the product with some of its backup capabilities, it can get a little bit more detailed, for example. However, for the disaster recovery piece itself, it's it's pretty easy to use.

The near synchronous replication is effective. It works really well. The replication and the RTO, RPO times are pretty much the best in the industry.

We saw some benefits right away in that we were understanding that we were now highly available. We also started to see more and more benefits as time went on.

It helps protect virtual machines in our environment.

Our downtime and our ability to replicate happen within seconds. We've seen other products that take about five minutes. Now, we take seconds to get things back up and going. Therefore, the loss of data is virtually nothing. We've been extremely happy with that.

It's helped reduce downtimes in pretty much any situation. We've had instances where a data center or a cluster in a data center was down or we were having problems with it and being able to have that replicated data being able to be spun up within a matter of minutes. It's significantly helped where if we didn't have that ability, we were probably looking at at least three to four hours, if not a day, of downtime. We're talking about the difference between minutes of downtime versus hours to potentially days.

With Zerto we haven't had any any actual instances where ransomware or anything like that actually comes up. We do yearly testing where we'll fail over an entire data center. While we haven't had any malicious incidents, we've had success with conceptual testing.

Zerto hasn't necessarily reduced the overall testing in our organization. We still have to do the testing. That said, it's reduced the time in which it takes to perform that testing. So, we still have our requirements to do yearly testing. However, it's at least reducing the amount of time it takes. Before, the testing would take an entire weekend and multiple departments in order to complete it. Now we're finishing our testing in a matter of hours. We're knocking off quite a bit of time with Zerto - plus hours of time in order to complete testing.

Zerto is now our resiliency strategy. We're able to replicate all of our data and be able to bring up an entire data center within a matter of minutes, which has become our go-to for our resiliency within both of our data centers.

Recently, they started forcing everybody to use a Linux-based appliance for their z/VMs. That appliance has been extremely touchy and, in some cases, problematic. However, there were Windows-based z/VMs prior, and we never really had issues with them. But now we're running into problems where certificates aren't able to be imported for things like LDPAPS and SSL. We've run into actual downtime with the z/VMs recently, which is new to the Linux app appliance. Overall, the appliances had some bugs, and they've not been as reliable as they were in the past.

I've been using Zerto for a little over 4.5 years.

There are the no real lag issues, We've only had a couple of instances where the system has been down, and wasnew since our Linux appliance install. Overall, it's been pretty reliable with the caveat that the new Linux appliance has had some downtime. Prior to that, we hadn't had any.

Scalability's been good. There's a couple of instances where they could allow for some more local replication, however, scalability has been good.

I quite frequently contact technical support. On most things, they have been pretty good. The issues that we've had with that z/VM, those tickets can take quite a while. I have one ticket that's been open for about four and a half months now. They're still trying to figure out some of the bugs within their system, which has caused some tickets to take longer than they really should.

The quality of response has been pretty good. Maybe 7 or 8 out of 10 are quality responses. They're they're pretty good, pretty knowledgeable. Again, there are some instances where they're still learning the system as well, or there's something new, and it's a little bit odd; however, other than that, their answers are typically pretty spot on and pretty well documented.

We used to build products by Nutanix. Their RTO times were much higher. That's about the only solution that I've used at least recently.

I wasn't part of that decision making process. Zerto had been onboarded by the time I came on to to the team here.

The deployments have been pretty easy as long as you have your network topology figured out. If you're just starting up a brand new appliance, and you're running through a setup, signing IPs , et cetera, you have to make sure that the z/VMs can talk to each other. It's a pretty easy process.

Usually, for the setup, we have the SME, which is me, and then a backup to be a second pair of eyes, however, a lot of the work is been done just by myself.

In terms of maintenance, there are updates that need to be applied. The certificate imports need to happen depending on expiration dates. There also is their key cloak integration for authentication, and that requires some upkeep as well depending on how you're signing permissions and what you're signing permissions for.

I've done redeployments myself, for example, when we switched over from Windows to Linux to z/VMs. That was all in-house. At the time when they did their very first deployment, they had used a third party vendor to assist with that. We've not needed them since.

I don't have any visibility on the pricing.

We're a Zerto customer.

I'd rate the solution eight out of ten.

New users need to understand the product prior to deployment and make sure that they're taking the time to whiteboard this out. Your VRAs are going to take up a good amount of space. So users need to understand that when you're replicating data over, you are making a second copy of that data, and understand what your test scenarios are going to be. You need to understand if you need things like a test environment to actually be within Zerto since that will be taking up more space. Overall, people just be aware that the Linux appliances still have to have their bugs worked out. For first-time users, especially, I would keep those deployments as simple as possible to start.

We do many data-related activities for various government ministries in India. We use Zerto to back up and recover data in many training and capacity-building activities.

We implemented Zerto to address challenges with data centralization in our complex platform environment. Previously, pulling data from a central source was impossible due to the need to feed it into an internal location before deployment. This limitation hindered customization and integration efforts. Additionally, integrating our primary data source, previously used with IBM, into the new platform proved difficult due to compatibility issues. Zerto's capabilities were seen as a potential solution to these problems.

The remarkable benefits of Zerto have yet to manifest fully. The software operates efficiently without significant bugs or issues, and Zerto's customer support has been responsive. While real-time reporting is a standout feature compared to other trial products, its impact on our ongoing projects remains to be determined. A full assessment of Zerto's potential will require an additional six months.

Zerto has significantly improved our Recovery Time Objective, particularly regarding project timelines. The expedited turnaround during critical project phases has been instrumental in streamlining our processes. By accelerating these stages, we've reduced the need for additional developer resources and eliminated time-consuming tasks associated with establishing essential parameters and metrics. As a result, projects that previously took six months can now be completed in as little as four. This accelerated timeline has enhanced profitability and optimized resource allocation, allowing us to maximize project revenue.

Zerto has significantly reduced our disaster recovery testing efforts. By consolidating software and streamlining processes, we've dramatically decreased the required manpower. Multiple teams efficiently utilize a single platform, eliminating the need for disparate services and reducing costs. This centralized approach has markedly decreased the time and resources invested in disaster recovery testing and pre-testing activities.

Zerto's greatest strength is its speed. We never encountered lag or interruptions, even when working remotely from home or other locations with potentially limited internet bandwidth. The software's streaming performance was exceptional, without buffering or connectivity issues. This was a primary factor in our decision, as Zerto emphasized its ability to operate effectively on lower bandwidth connections during the initial demo. Deploying the software in any remote location is straightforward and hassle-free.

The primary concern expressed by all server users is the lack of robust integration features. While Zerto offers some integration capabilities, the smooth and efficient data flow between portals remains a significant challenge. The support and technical teams know this issue and actively seek user feedback, but progress has been slow. The current process, involving multiple platforms and a database management system bottleneck, is time-consuming and inefficient. Additionally, while reporting and dashboard features exist, real-time reporting and mobile functionality require improvement. The user interface could be more intuitive and user-friendly. Customization, a critical requirement for government clients, is another concern. Implementing requested changes is often time-consuming and expensive, hindering adaptability. Addressing these integration, reporting, user experience, and customization issues is essential for improving customer satisfaction and retention.

Currently, Zerto only offers an annual subscription, but it would be beneficial to provide quarterly and semi-annual subscriptions to help retain clients.

I have been using Zerto for one year.

I have not encountered any performance issues, such as lagging or crashing. The system operates efficiently and reliably under various conditions, even with significantly lower bandwidth. Zerto has consistently demonstrated stability and high speed, ensuring uninterrupted application performance.

Approximately 50 to 60 individuals within our ecosystem utilize Zerto directly or indirectly. Given its operational efficiency, which I estimate to be between 95 percent, I confidently assert its scalability. While we haven't encountered a scenario within our ecosystem that necessitates testing its scalability limits, its exceptional performance thus far strongly suggests its capacity to handle increased demands.

Zerto uses a ticketing system and offers support through a help desk accessible via chat or phone. A dedicated technical team is assigned to address customer issues, which are typically resolved within 24 hours. We have not experienced any significant delays in issue resolution.

We find the Zerto pricing fits our budget.

I would rate Zerto nine out of ten.

Maintenance is required quarterly. The Zerto technical and business teams collaborate with us on the backend to remove all the repeated queries that make the system sluggish. This service is charged additionally.

I strongly recommend that anyone considering purchasing Zerto begin with the 30-day trial, which can be extended to 60 days. This ample timeframe allows a thorough evaluation of all features and functionalities. Understanding Zerto's customization and integration capabilities to align with specific business needs is crucial. Had I followed this approach and shared my feedback earlier, the outcome might have been different. Therefore, it's essential to fully explore the trial version before committing to an annual subscription. Close collaboration with the Zerto technical team is vital to ensure successful implementation. While sales teams often present an optimistic view, real-world experiences from existing users provide the most valuable insights. I encourage potential customers to connect with other Zerto users through industry networks to gather honest feedback before purchasing.

We utilize Zerto as part of our disaster recovery toolset. We employ a multi-tiered model, catering to a select group of customers, primarily hospital clusters. These customers maintain on-premise networks with cloud-based disaster recovery. In this managed service offering, we leverage Zerto to facilitate their cloud recovery.

The replication is quick. We encountered some challenges replicating the data during the first full copy. Since we weren't using Zerto, I suspect the bandwidth requirements for replication were a bottleneck for us. However, once the initial copy was complete, the process became seamless. The recovery was near zero after the first replication. Zerto worked perfectly.

We implemented Zerto because it supports a multi-tenant model, which was a critical requirement for us. We have five tenants located on-premises across five different data centers. However, we only have a single disaster recovery site in the cloud. Zerto's solution enabled us to consolidate our disaster recovery needs. Previously, managing five separate data protection solutions for each data center and five different cloud recovery subscriptions would have been incredibly expensive. Zerto significantly reduced our costs. Additionally, Zerto provides a single-pane-of-glass dashboard, allowing us to manage our infrastructure efficiently and effectively. This comprehensive view offers full control over our applications and complete visibility into all our tenants. As an infrastructure manager, I believe these features are the most valuable contributions Zerto has made to our organization.

Zerto has helped save around 30 percent of our time.

Zerto has helped achieve significant cost savings.

In the VMS portal, we had a relatively small amount of data overall. We also had multiple tenants, each with a maximum of 20 to 30 virtual machines on-premises. These VMs weren't particularly large. As a result, recovery was quick, typically taking less than a minute. My Recovery Time Objective would be less than a minute for any VM, even for a complete migration of all on-premises VMs to the cloud.

While I wasn't privy to the details of the client's previous DR solution before implementing Zerto, our discussions revealed significant time savings with Zerto's recovery process. Compared to their prior on-premises DR approach, Zerto offers a substantial reduction in recovery time – at least 15 to 20 minutes faster. This improvement stems from eliminating the need to coordinate with personnel and the time required for on-premises recovery procedures at their dedicated DR site. Previously, they relied on manual, on-premises to on-premises recovery, which inherently took longer. However, a direct comparison between their old solution and Zerto wouldn't be entirely accurate. Zerto offers significant efficiency gains, boasting up to 200 percent improvement.

Migrating data through Zerto is straightforward with careful planning. Our first experience involved Zerto's support throughout the process. While initially challenging due to our lack of experience, we were able to navigate the initial setup. One hurdle we faced was optimizing network traffic for the initial data replication from on-premises to the cloud. However, we embraced the learning curve, documenting everything as we gained control of the environment. This ensured a smooth integration for subsequent tenants. While the first migration presented some difficulties, as is to be expected, Zerto's excellent support made the process manageable. Their responsiveness in explaining and resolving issues made it a positive experience overall.

The RPO was very close to zero, meaning there was minimal data loss between replications. However, this could be impacted by the specific database being hosted and other factors. For application servers or virtual machines replicated on-premises to the cloud, I believe there was negligible lag or delay, assuming no network issues. Bandwidth and network traffic did play a role – we observed instances of slower RPO due to traffic spikes or network events. However, with Zerto providing the recommended data bandwidth, we encountered minimal challenges. In most cases, I'd say 90 percent of the data was synchronized almost constantly. The only exception was when network issues arose.

Our data center experienced an issue, necessitating a disaster recovery procedure. Fortunately, data loss seems minimal, and the impact on our clients appears negligible. This is partly due to the managed service we provide for a tenant, who fortunately didn't perceive any significant data loss. The success of the recovery is also attributed to our user-friendly, always-in-sync system. Upon receiving alerts and notifications, we promptly informed the client, who then quickly authorized the recovery process. From our perspective, the recovery went smoothly with minimal challenges. In the actual scenario, we believe data loss was negligible. While some data loss might have occurred technically, it wasn't significant enough to cause any noticeable impact on the client. It's important to note that our monitoring team maintained complete control of the situation, allowing for swift decision-making and a speedy recovery.

In a data recovery scenario, we'll still have our database administrator, Linux administrator, storage administrator, and Zerto operator available. While Zerto can automate disaster recovery and VM restoration, it's important to remember that it's not a foolproof solution. Even though Zerto streamlines the process, a well-prepared organization will always maintain backups and ensure a dedicated team is in place for data recovery. Zerto doesn't reduce the number of personnel involved; rather, it enhances their productivity by freeing them up for other tasks during a recovery event. During a recovery, it's still recommended to have everyone on call. While Zerto handles most recoveries, there may be situations where manual intervention is necessary. By being fully prepared, our organization can effectively address any data recovery situation.

It is easy to manage and monitor the DR plans using the Zerto GUI.

Zerto's most valuable features include its user-friendly interface, multi-tenancy capabilities, and near-zero downtime recovery. Zerto is easy to learn and use, even for those with limited technical experience. Additionally, Zerto's failover testing functionality allows us to run tests in real time without impacting production systems.

We encountered some issues during Active Directory recovery. When we implemented Active Directory, we provided feedback to Zerto regarding the challenges of recovering AD from the on-premises environment to the disaster recovery site. Unlike other virtual machines, AD recovery presents unique difficulties due to its active-active nature. It's unclear whether these challenges stem from Zerto itself or limitations within Microsoft Active Directory. However, in our experience using Zerto for AD recovery compared to other technologies, we faced data discrepancies that necessitated workarounds to bring AD online at the DR site.

Certain applications we migrated from production relied on Active Directory authentication. To ensure successful application functionality at the DR site, a functional AD environment was a prerequisite to application migration. Therefore, our initial step involved copying and guaranteeing a running AD instance on the DR side before application recovery.

However, upon attempting application authentication on the DR side, data inconsistencies prevented successful authentication. To address this, we created an isolated clone of the AD environment and conducted tests. Through trial and error, we were able to develop workarounds to resolve the issue. Notably, these challenges were specific to Active Directory; other VMs didn't exhibit similar problems.

I have been using Zerto for over 3 years.

Zerto has been very stable for us. We do apply patch releases and upgrades whenever necessary to ensure continued stability. Fortunately, we haven't encountered any major bugs or issues that would cause significant downtime, unlike what we've experienced with some other tools. Zerto has been a reliable choice for us.

I would rate the stability of Zerto 9 out of 10.

I would rate the scalability of Zerto nine out of ten.

The technical support is fantastic. They offer same-day assistance, and their documentation is clear and comprehensive.

Before implementing Zerto, the client's disaster recovery relied on an on-premises to on-premises failover strategy. Seeking a cloud-based solution, they chose Zerto to leverage its expertise in this area.

We previously used another tool for DR orchestration. While Zerto can also perform recoveries, it focuses on virtual machines and doesn't extend to the operating system or database level for starting and stopping applications within those VMs. Despite these limitations, Zerto excelled in its support. The Zerto team provided excellent assistance whenever we faced challenges, joined calls to help us troubleshoot, and offered clear timelines for resolving issues. Their documentation was also thorough. In contrast, the previous DR tool lacked comparable support and documentation. This stark difference in support quality is why we favored Zerto and ultimately removed the other tool from our project. Currently, we rely solely on Zerto for our existing tenants, and we plan to continue using it for future ones as well.

We encountered some challenges during the initial setup. Zerto offers several data replication options, I believe 2 or 3. These include copying data to our hard drive or storage box, copying it to the DSR site, and replicating it over the network. However, only network replication worked for us.

The issue might have been related to bandwidth requirements. It's possible that either Zerto itself or our network infrastructure wasn't up to par. We faced some challenges during that initial phase.

However, after the initial setup and the application of delta copying, which happens daily, we rarely experienced any replication issues. Most of the time, network glitches and fluctuations caused brief disconnections, but overall, replication ran smoothly.

We went into the Zerto deployment with a clean slate. Both team members were new to Zerto, so we were all learning as we went. This initial deployment was challenging, but it gave us valuable hands-on experience. Once we had a firm grasp of the environment, onboarding subsequent tenants became seamless. We developed a clear plan and approach, which streamlined the process for future deployments. Technically, the challenges weren't ongoing. The main hurdle was understanding how to integrate Zerto with our existing infrastructure. While that initial learning curve was steep, Zerto's excellent support helped us navigate it successfully.

The deployment time for Zerto varies depending on the complexity of your environment. More complex environments will require a longer replication process. However, on average, we can onboard a new customer within 1 month. This timeframe encompasses the entire process, from the initial planning phase to the deployment of up to 30 VMs within a tenant.

Our project involved 2 separate IT teams at 2 different locations. One team acted as the managed service provider, while the other represented the client side. The client-side team, located on-premises, provided us with essential information about their data centers. This included details on virtual machines, such as their size, quantity, and basic data collection metrics. They also helped us identify their storage requirements. Based on this information, we planned our cloud storage procurement and other necessary actions. The project team comprised approximately 10 to 15 people, including project managers, IT personnel, storage specialists, network engineers, and development experts.

I would rate Zerto 10 out of 10.

Our organization uses Zerto to manage the replication of data centers from 7 on-premises locations to the IBM cloud for our midsize clients.

Our environment consists of VMware, data storage, and a network, with Zerto deployed for disaster recovery. While VCDM and VMware are managed by our cloud provider, we maintain 5 additional technologies with a team of 8 people.

We experienced a brief on-premises outage. Fortunately, we were able to recover quickly using Zerto. The software triggered an alert, notifying our monitoring team. These features proved to be very helpful. Additionally, we were able to promptly contact our clients and explain the situation. They responded quickly and effectively, minimizing the impact on their end. Our clients were pleased with the response.

I recommend Zerto to others.

We use Zerto for the disaster recovery capabilities that it provides us. It is for our Tier 1 applications.

Zerto allows us to protect individual VMs. With the other solutions, we are protecting the storage that the VMs live on, which is costly, so Zerto does save us money.

Zerto has near-synchronous replication. It works very well. Our RPO or recovery point objective time was 20 minutes, and we were doing thousands of VMs. We not only met the RPO; we exceeded it. There were many times when it was just seconds behind.

We have used Zerto to help protect thousands of VMs in our environment. Zerto has had a good effect on our RPO. It has helped to exceed our RPO. Our RPO on some of our critical systems is 20 minutes, and we exceed that. Most of the time, we are under 2 to 3 minutes.

It is very easy to migrate data. We ended up migrating from one data center to another data center, and we moved 20,000 virtual machines with Zerto. It was great.

Zerto lowered our RTOs as well. As a part of the solution analysis that we did for the RPO and RTO, Zerto's interface to do a DR test or a DR recovery was the fastest. We had a 24-hour window to recover 5,000 virtual machines, and we were doing them in three to four hours.

Zerto has helped us to reduce downtime multiple times. We had one incident where we used it to do a recovery. The downtime was roughly about 20 minutes. We do not have a value on that because it is customers' health information. I do not know how it affected the end users or customers outside of our company, but it does affect them.

Zerto has saved us time. When files were deleted, we were able to recover the files quickly. While doing OS patching on the servers, when the servers failed on the reboot, we were able to recover all good things when it came to quick recovery on it. As opposed to pulling it from our backup, it has cut our time probably in three quarters.

Zerto has helped to reduce our organization's DR testing. A DR test or a recovery used to take us days, whereas now, it takes us hours. The system that we were using before took multiple engineers to do the DR test, whereas today, a single engineer can do the DR test, and then we need just a couple of engineers to do checks on it, so it saves us a lot.

Zerto has reduced the number of staff involved in a data recovery situation. Instead of a group of people, we now just need one.

We used Zerto for immutable data copies. It was good, and they were on a course, but they shifted their focus. They were doing DR specifically, and then Zerto started shifting over towards doing backups. We were very excited about their long-term backups, but when HPE bought them, HPE stopped that part of it because they were directly competing against their solution. At the time they were doing it, we were very excited about it.

The DR testing capabilities that it has are valuable.

Its ability to roll back if the VM or the server that you are recovering does not come up right is also valuable. You have the ability to roll back a few seconds or a few minutes. The rollback feature is great.

While going in, we were looking at the backup tool so that we had a DR tool and a backup tool, but they stopped developing their backup solution built into it. That was a bummer for us, so now, we have a DR solution, and we have a backup solution.

For the actual application itself, we have put in our request for certain features, and so far, they seem to be adding those features. In their latest one going to version 10, they did an appliance, which we had asked about 6 years ago. It is great to see that they are doing an appliance. There would be even more savings for us now because we do not have to pay licensing for a Windows VM.

I have been using Zerto for about 7 years. I have used Zerto a few times at different companies.

We have seen very few issues. It is one of the few solutions that actually runs. If you do your leg work and implement it right and go through all the design and other things, you do not have to babysit the solution. Care and feeding is what it amounts to. That is all you have to do, whereas with a lot of the other solutions, you have to babysit them.

Its scalability is very good. It scales very easily.

They could do better in regards to escalating an issue. I would rate them an 8 out of 10. In defense of support, I know it is hard because they are talking to somebody who has got 28 years of IT support. When I get on the call, I am probably dealing with someone who is just starting out. He has to go through his standard process. However, somebody like me is looking for faster support and would like to get to a real smart guy quicker.

For disaster recovery, we were using VMware Site Recovery Manager, and it was not able to provide the recovery, the RTO, or the RPO that the company required. I went out and did a discovery for different DR solutions, and that is where I came across Zerto. Zerto replaced VMware Site Recovery Manager, and it saved us millions.

Our deployment model is hybrid. I was involved in the initial deployment. It was straightforward. It was a lot easier than VMware Site Recovery Manager. It took us a week to deploy it.

In terms of maintenance, other than typical patching and upgrades, it does not require any maintenance. VMware Site Recovery Manager required a lot of ongoing maintenance.

We implemented it in-house. There were just three of us involved in its implementation.

The pricing is based on virtual machines. They need to do better in regards to their tiering pricing rather than one price per VM. A lot of times we have VMs that are lower tier, such as Tier 2 or Tier 3, but we pay the same price as for Tier 1. I know they are developing this out, but it would be nice if they could provide a little better pricing in regards to their tiering protection.

We tested four different solutions, and Zerto was the only one that was able to meet our requirements. We did PoC on Zerto and two other solutions. Zerto was by far the leader when it came to disaster recovery.

To those evaluating this solution, I would recommend doing a PoC on it. Deploy it in your environment and test it. Most of the problems you are going to see are due to the replication, and that is the site-to-site connection. One of the problems that I have experienced with Zerto has been related to replication, not the solution itself.

We have not used Zerto for blocking unknown threats and attacks. Thankfully, we have not had that. We do not have experience of that, thankfully.

We have used Zerto to do DR to both AWS and Azure, but the ability to do disaster recovery (DR) in the cloud is not something critical for us because the health insurance requirements for certification do not allow us to put our Tier 1 data in the cloud. Also, because our applications are multi-tiered where they reach out to the mainframe, Solaris, and other equipment outside of the virtual environment, it did not make sense to go to the cloud with it, but we do have it. We have a development environment there. A lot of times, we will use it to refresh the development environment. So, it is important, but in our case, it is not critical for us.

We have not had any issues utilizing Zerto to support DR on AWS, but AWS is on the slower side. The reason is that for the connection to AWS, even though it is a direct connection, the speed does vary for us.

I would rate Zerto a 10 out of 10.

We are using Zerto for disaster recovery. By implementing Zerto, we wanted fast recovery time.

It helps to meet recovery point objectives. Management is simplified. Its automation capabilities simplify the management of the disaster recovery processes.

It reduces the burden on the IT staff. It is also cost-effective. We could realize its benefits only in eight months.

Disaster recovery through the cloud is very important for our organization. We want to ensure that we are able to retrieve data in a proper manner.

Zerto helps to protect VMs in our environment. It replicates a lot quicker than what we were using previously. There is a reduction in the time taken to replicate. It takes a quarter of the time and protects our VM environment.

Zerto has been very good for our RPOs. It has been within seconds for us. It has also helped us to meet our RTOs.

It is easy to migrate data. We have not had any challenges. Zerto provides the ability to keep our users collaborating with one another during a data migration. It is very useful for a smooth migration process.

Zerto helped to reduce our organization's DR testing. It saved three to four hours.

Zerto has reduced the number of staff involved in overall backup and DR management. Instead of ten people, we now have seven people.

It is cost-effective and stable. It protects virtual machines, and there is a fast recovery time.

It works well. It is simple to set up. It works a lot quicker than what we were using previously. It takes about a quarter of the time. It is important for our organization.

One thing I would like to see in their roadmap is introducing long-term storage in the cloud such as Azure or AWS. They can make it more seamless.

The downtime features can also be improved.

I have been using Zerto for one and a half years.

It is stable.

It is scalable. It can scale based on the growth of the organization.

We have about 25 people using this solution. It is being used in multiple regions.

Their customer support is good. I would rate them a ten out of ten.

We were using the disaster management solution of AWS. We switched to Zerto because of cost management and recovery point objectives. They were offering real-time replication and automation to help our organization achieve its RPOs and RTOs. We wanted better recovery time.

Zerto is also easier to use than other solutions.

Its initial setup is good. Its implementation took one month.

It is easy to maintain.

We had support from Zerto.

We have definitely seen a return on investment.

It is cost-effective.

We did not evaluate other options.

I would recommend Zerto to others. I would rate Zerto a nine out of ten.

Our environment primarily integrates Zerto with VMware. This includes offering Zerto's self-service portal, which integrates seamlessly with Cloud Director. Additionally, we have Zerto integration at the vCenter level in situations where we don't use Zerto Cloud Manager and its self-service portal. This variety reflects the different use cases within our current processes. Since Zerto is our primary offering for disaster recovery solutions, we tailor the implementation based on customer needs.

We implemented Zerto to safeguard our private cloud infrastructure workloads. While disaster recovery is its primary function, we also leverage Zerto for data migration.

Our RPO with Zerto is under five minutes. The RPO time is dependent on the bandwidth.

We have asynchronous replication with Zerto.

Zerto integrates well with Asynchronous Continuous Delivery tools. However, unlike SRM, Zerto offers protection during workflow rollbacks. This rollback functionality, along with its centralized reporting and UI management, makes Zerto an attractive solution.

Zerto offers a cloud-based disaster recovery solution, eliminating the need for physical data centers. In this instance, we leveraged Zerto to protect a private cloud workload running VMware and ensure its seamless recovery in Microsoft Azure. Disaster recovery in the cloud is crucial. As part of the private and hybrid cloud infrastructure team, I'm involved with a service in our catalog that runs workloads in a private cloud but configures disaster recovery primarily for the public cloud, Azure in our case. This is important for both the customer and the organization that provides the service.

Zerto offers significantly faster recovery times compared to SRM. SRM's recovery process involves multiple steps, requiring a detailed checklist to ensure the correct sequence is followed within protection groups and recovery plans. This complexity is a common issue with other data recovery products. Ideally, any product, not just from a design perspective but also from implementation and operation, should be user-friendly. It should be intuitive and easy to operate to achieve its intended purpose. This is a key reason we chose Zerto over other data recovery solutions.

Migrating data with Zerto is incredibly easy. It performs a continuous replication of our data in the background, even while our primary server is running. This live replication ensures all changes are captured before the server is shut down. In other words, it includes everything, resulting in a seamless migration process. Triggering the migration is also straightforward. We simply need to choose whether it's a move operation or a scale-over operation.

It helps reduce downtime during migrations. While there might be a brief interruption when workloads are shut down, there's no data loss. However, downtime for disaster recovery depends on the specific application's RPO. RPO isn't a fixed value; it varies based on how much data loss an application can tolerate.

It helps to reduce our overall DR testing. The solution is designed so that we can trigger the app or a move operation within three steps. Making it easier and quicker for the administrator or customer that is working on it.

Zerto's user-friendly interface simplifies operation and management, allowing us to minimize the number of people involved in overall backup and DR management.

The user interface is very user-friendly. Additionally, the journaling feature allows users to restore their progress to any point in time. This is a valuable feature, especially since similar products, like SRM and SCX, don't offer this functionality. In my opinion, this journaling capability makes Zerto unique.

Zerto integrates with vCloud Director to protect workloads deployed there. However, it would be beneficial if Zerto also offered integration with other cloud management platforms, such as VMware Aria Automation. For example, Site Recovery Manager recently introduced integration with VMware Aria Automation, allowing the protection of workloads deployed through Aria Automation. This functionality, including site recovery management, is currently not available in Zerto. Zerto's strength seems to lie specifically in its VMware capabilities, which could be an area for improvement.

Another point to consider is the potential for Zerto drivers to cause issues in ESXi environments. In some cases, users have reported problems and discovered that the Zerto drivers are not verified by VMware. While HPE is a technical alliance partner for Zerto, improved collaboration between VMware and Zerto regarding driver validation would be valuable. This information seems to be missing at the moment. We are currently in touch with our technical account manager to clarify this.

I have been using Zerto for over five years.

Most Zerto issues we experience are at the ESXi level, likely due to the Zerto drivers. However, these issues are not currently impacting our work.

Zerto is scalable.

The technical support is quick.

I also use SRM but I believe Zerto is better because it's easier to integrate with other systems. While SRM also offers integration for workload protection through VMware Aria Automation and a SIM connection application similar to replication, it may have some limitations. For instance, Zerto might require an agent to communicate with the source system, which could be a disadvantage. This suggests that there might be features offered by other vendors that Zerto could incorporate to improve its functionality.

The initial deployment is straightforward. Zerto has introduced an appliance, making deployment even easier by removing the need for patching and object installation.

One member of our deployment team is needed for the deployment.

As a Zerto partner, we do all the deployments for our customers and provide comprehensive training.

I would rate Zerto nine out of ten.

I recommend that new users take advantage of any training videos and documentation offered by Zerto to familiarize themselves with all the features and how to use them.

We use Zerto for replication.

We implemented Zerto to help with the high bandwidth required for the live application replication.

In my minimal experience with Zerto, the near synchronization replication is good.

Zerto does a good job of blocking unknown threats and attacks.

Its easy-to-use application server has helped our organization improve its bandwidth.

Zerto has made disaster recovery in the cloud much easier for us than in physical data centers.

We've seen significantly faster recovery times compared to other recovery tools we've used, like Carbonite.

Zerto makes it much easier for us to conduct and manage our DR testing.

The replication feature ensures minimal downtime during disaster scenarios.

Zerto's failback capability automatically recovered one of our live applications after it disconnected.

Zerto helps us monitor our disaster recovery.

Zerto's user-friendliness is valuable. It's easy to use.

It would be great if Zerto could automate replication more.

I have been using Zerto for four months. I joined the company when they were already using it.

I would rate the stability of Zerto ten out of ten.

The technical support is good.

I also use Carbonite but Zerto offers faster speeds.

The deployment of Zerto took a few weeks.

I would rate Zerto nine out of ten.

We have over 300 clients using our web applications.

We rely on Zerto for data recovery and cloud migration as our primary disaster recovery solution, especially since we lack a dedicated backup data center. Zerto's ability to block ransomware attacks and facilitate rapid server recovery provides us with significant peace of mind.

This comprehensive solution extends beyond processor recovery and data center capabilities. It also encompasses application testing and on-site data protection, ensuring comprehensive coverage in the event of any incident, including ransomware attacks.

We implemented Zerto to mitigate concerns about cyberattacks and data breaches. Zerto functions as a robust multi-layered defense, safeguarding our data. Even if an attack breaches the initial layers, Zerto allows for rapid recovery, ensuring minimal downtime and continuous synchronization with the production server.

In terms of data protection, Zerto enhances business continuity by promptly reporting any encountered cyberattacks. This allows for timely notifications and, critically, prevents the disruption of running production VMs. This real-time monitoring and reporting prove invaluable in the event of threats, facilitating swift recovery efforts.

Our recovery time now is less than 30 minutes.

Zerto's CDP has had a positive impact on our overall data recovery.

Zerto's near-synchronous replication operates in near real-time, enabling data replication with minimal to no data loss.

Our repeated use of Zerto's immutable data copies has significantly enhanced our trust in our backup and recovery procedures.

Zerto provides real-time notifications and reports, which help us prevent unknown threats.

While cloud platforms offer their own security and backup features, Zerto provides an additional layer of protection for our data in the cloud.

Google Cloud Platform provides primary security for our virtual machines. Additionally, Zerto provides us with granular reports that help us focus on specific areas to ensure further protection.

While I haven't had extensive experience with other DR solutions, Zerto offers impressive recovery speeds.

The migration is not complex.

Zerto has helped reduce downtime by over 50 percent.

Zerto has sped up our recovery time by over 20 percent.

We have been able to reduce the number of employees involved in data recovery situations by five.

I like the ease of recovery and backup the most.

Disaster recovery is the most valuable for ensuring minimal downtime during a disaster scenario.

The technical support response needs improvement. They need to treat us more as a partner.

I have been using Zerto for seven months.

I would rate the stability of Zerto nine out of ten.

I would rate the scalability of Zerto eight out of ten.

We contacted the support team by email and tickets during the data migration but received limited response.

Previously, we relied on backups from GCP, AWS, and Azure. We transitioned to Zerto because it offers granular reporting capabilities, which helps us keep our managers and non-technical personnel informed.

The initial deployment took a few weeks.

The pricing is reasonable.

I would rate Zerto eight out of ten.

We have 500 people in our organization that use Zerto and it is used in multiple regions.

Zerto requires moderate maintenance, handled by a team of five.

We use our custom dashboards to manage and monitor our disaster recovery plans. These dashboards receive emails automatically, allowing us to take necessary actions as needed.

I recommend Zerto for data backup and recovery, as it also helps mitigate the impact of data corruption or deletion.

Zerto is our main application for curbing risks. We use it to protect our workflows on applications from threats that can come from the cloud and on-premises.

Before Zerto, our organization kept experiencing some attacks. Our data was not safe. There were frequent attacks on our data, and that is why we decided to deploy Zerto.

It helps to ensure that our organization's data is safe from any latest threats.

It ensures that our applications are protected. We have high-security firewalls that cannot be attacked or broken by ransomware attacks.

Zerto can block unknown threats and attacks. It has security measures in place to stop any threats that can harm our data.

When it comes to data capacity, Zerto provides an assessment of data replication that can be orchestrated to feed the data protection models.

We used to mostly have on-premises applications, but after the deployment of Zerto, we are able to move to the cloud and ensure that our data is secure from both sides.

When it comes to cloud recovery, Zerto ensures that data transfer from the cloud to our organization is safe. It cannot be easily attacked with malware or by cybercriminals. It is very important to us that our database is safe and the data on our cloud servers cannot be interfered with by external or anonymous users. It ensures that the data for the organization is channeled for the right purpose and through the right infrastructure.

We use Zerto to support DR on the AWS platform. The support has been very good, and I would recommend it. The performance has been good, and our data has always been safe.

I have not had any difficulties with data migration. Since we deployed Zerto, data migration has not been a challenge.

Zerto helps our organization to be in the right direction when it comes to data protection and recovery from both on-premise and cloud servers. When there is anything crucial or any challenge, their customer support team provides a timely solution, which helps with performance.

The recovery management has been efficient. We can use the tools to accommodate any form of data for future retrieval. Our data is safe.

Zerto has been excellent for our RPOs. When it comes to disaster recovery, the company makes sure that we have the right tools at the right time to ensure that we do not have any data recovery challenges across the enterprise.

Zerto has saved a lot of time. We used to take eight hours, but now, it takes us six hours to accomplish most tasks and projects based on the data flow.

Zerto has reduced the number of staff involved in a data recovery situation. We have 20% less staff.

Zerto has also reduced the number of staff involved in overall backup and DR management.

Its user interface is excellent, and when it comes to data duplication, Zerto is very fast.

Their customer support team ensures that we get timely updates and provides status or data on threats to help us ensure that our applications are safe.

The cost of deploying and running this platform is also good as compared to other platforms.

Overall, Zerto is doing a very good job. We have experienced a few downtimes on networking. Most of the time, they come up with a solution immediately to sort out any challenge that may affect data flow or data migration. It does not happen frequently. We might experience it once in two months, but when we face any downtime, it does not impact the data.

I have been using Zerto for the last six months.

It is a stable product. I would rate it a nine out of ten for stability.

It is very scalable. I would rate it a ten out of ten for scalability.

Their support is good. Their technical support team has been doing well. I would rate them a nine out of ten.

We were not using a similar solution previously.

It was not complex. It was simple. The deployment was simple and clear. It took a few hours.

We had four people involved in its deployment. Overall, we have eight people who work with this solution.

We have seen positive returns on investment. We have achieved a lot, and our performance keeps on improving. We have seen an 80% ROI in the past six months.

Its price can be better, but it is not bad. Most small-scale organizations can afford it, but they can come up with more customer-friendly packages.

We did not evaluate other options. For now, we are okay with Zerto.

Overall, its performance has been good, and I would recommend it to other organizations. It is a good solution that can help any organization to achieve projects based on data management.

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

I use Zerto to store and protect my files. Whether I'm working on a project or just need to access old files, Zerto ensures everything is safe. This makes it very convenient, as I can easily access any information I need with just a single click.

Zerto is effective at blocking unknown threats and attacks. We might consider using it on the business website as well, but it's important to understand how it might impact our operations. It helps with blocking threats, which is certainly valuable. So, in terms of its effectiveness, I'd say it's close to 99% guaranteed.

Zerto has helped our organization block threats, is user-friendly, is effective in storage, and inspires users.

Zerto's Cloud disaster recovery is impressive, and recovering most of our data can be relatively straightforward. However, it requires careful planning and understanding. Navigating the recovery site is crucial, so ensure we read and comprehend the instructions thoroughly before clicking anything. This way, we'll know which box to choose and where to click to achieve our desired outcome.

It is easy to migrate data using Zerto.

It helps reduce downtime.

It has helped reduce our disaster recovery time. Before Zerto, we needed ten people for disaster recovery and now with Zerto, we are down to three.

Zerto is truly inspiring. Sometimes, when I provide information and receive it back, it can be remarkably refreshing and motivate me to get the most out of it. There might be instances where I initially think something isn't applicable, but then I try it out and say "wow" as I realize I am getting something positive from it. it becomes quite inspiring and brings out my best creative potential. Witnessing these features makes me naturally want to explore and create more.

The performance was generally good, but occasional lag disrupted the flow, leaving room for improvement.

I have been using Zerto for four months.

While Zerto is stable, it can sometimes be slow to retrieve the data we need.

Zerto is scalable.

We used to complete tasks manually, which consumed a lot of manpower, before adopting Zerto.

Zerto is affordable.

I would rate Zerto a nine out of ten.

No matter what we choose to do, there will always be potential positives and negatives. When aiming for the best outcome, focus on visualizing success and avoid dwelling on negativity. However, even while striving for the positive, acknowledge that occasional setbacks like technology issues or unexpected problems might occur. Don't get discouraged in the present; trust that Zerto will ultimately lead to something beneficial and fulfilling.