We provide disaster recovery with Zerto in two scenarios. One is for our customers using on-premises deployments, and the other is for using the multi-tenant cloud. They're buying the cloud as a service, and we're also protecting that with it.

Zerto is primarily well-recognized as a leader in disaster recovery. It makes it easy for us to talk to our clients about the solution we provide them. Since it is Zerto-powered, we don't have to answer many questions about how it works, its reliability, or its capabilities. Thus, having name recognition, a positive company reputation, and technology benefits us.

The platform's ease of deployment and the ability to isolate failovers are key features for our customers who want to perform testing without interrupting their production environments. Those are the two primary use cases.

Our operational teams have discussed the ability to integrate multiple Zerto cloud platforms more seamlessly. For example, we have acquired 22 companies over the last seven years. Some already had it deployed, and integrating those existing deployments into our primary deployment is more challenging than it could be. We have provided our feedback to them.

Thryv has been using Zerto for about twelve years now.

As a product manager, I haven't received any feedback indicating issues with platform stability, which our engineering team would certainly inform me about.

We've had no issues with the product scalability so far, whether it's individual customers or even as an aggregated group.

The size of the environment varies. We have some small customers with only a handful of virtual machines and others with two, three, or four virtual machines.

In our previous company, we used VMware Site Recovery Manager and Veeam. However, over the last 12 to 14 years, we have primarily used Zerto.

We have our private cloud, and that's where we primarily use Zerto. We also manage some Microsoft Azure environments where we have sparingly used the service, mainly because the same functionality is not present as it is when using it in a private cloud.

Disaster recovery as a service is a significant component of our overall cloud services. So, the ROI lies in Thryv's profitability, as we offer a managed service that adds value to our customers and generates a profitable revenue stream.

The product's pricing is the one area where it is less competitive. However, we understand why it costs slightly more comparing the features and capabilities. Customers prioritizing price might choose a solution offering different RPOs and RTOs for a lower cost. We have provided feedback on whether there could be a lighter option or alternative that's more cost-effective for the customers while balancing cost and performance. It would help Zerto and us win more business.

The product is superior compared to the other vendors.

We offer disaster recovery as a service powered by Zerto. We have multiple disaster recovery targets in the US and the UK and are expanding into Canada and Hong Kong.

I am happy that they've reconsidered the decision to stop supporting Hyper-V, especially with all the changes happening in the Broadcom world and customers looking at it as a solution. Zerto's continuous support is key.

The near-synchronous feature is a differentiator. Other platforms compete with Zerto, with Veeam being the primary one, trying to get the same capabilities. It is a key factor for clients who need low RPOs and the ability to protect their data with minimal potential data loss. It cannot eliminate the potential for data loss entirely and has a minimal impact. If the customers have a production-impacting event, their data is as close as possible to a mirror of what they had at the time of the production loss. So, it is a significant factor.

To some extent, we have implemented DR with Microsoft. It is less feature-rich and has a different implementation. We offer the service but don't offer much in the public cloud. Replicating out of the public cloud adds a whole other set of challenges. We can replicate it to a VMware-based cloud. However, no VMware tools are available if we want to replicate it outside of Microsoft Azure. It makes for a different recovery and is a bit more labor-intensive.

It has greatly impacted the RPOs. As long as our customers have enough bandwidth to transmit the changes across the network to our cloud, the RPOs generally take a minute. However, if the customer has bandwidth constraints, it can take up to five minutes.

With Zerto, recovery is much cleaner and faster. It's orchestrated better, and the testing capability within the cloud is a valuable differentiator. Unfortunately, we don't have many customers experiencing disasters, so our experience is generally around the testing component and making simulated or even full recoveries for customers seeking that. It has always performed well.

I would give it a nine for everything around capabilities and the product itself. The only drawback is the pricing. If we could get a better pricing model, especially in larger deals where we need to be more competitive for price-conscious customers, that would be beneficial.

Overall, though, I'm happy with Zerto as a partner. My reaction would have been different if the Hyper-V decision hadn't changed, as that would have caused complications for some customers.

Our primary use case is to continuously replicate our VMs to our DR site. Having the ability to recover them at almost any point in time, mostly back thirty days, is the main purpose of Zerto.

We didn't previously have a continuous replication tool and now we have the ability to recover to any number of points in time. That's really beneficial to us. It cuts down our recovery time.

The most valuable feature is how quickly it powers down the original source VMs and the speed at which it powers up the new VMs. The amount of time it takes to put up the operating system is valuable. The speed is what I like the best.

The near-synchronous replication is awesome. When you get hit by a cyberattack, you never know where the clean VM resides, and at what point in time it actually exists. Having the ability to find the point in time when we are clean is a good thing.

We are going from a physical data center to a physical data center at the moment.

We use Zerto to protect VMs in our environment. It increased our ability to restore at a point in time. We didn't have it before, and now we have it.

Compared to other tools, Zerto is a lot faster. There are tools with your primary block storage backup, but they're just not as fast.

I'm having a problem with CentOS 7 and with VMs with multiple network adapters. Zerto recognizes those multiple network adapters on CentOS 7 vm but it will not give me the option to specify a failover IP, for that particular VM. Something's not working right, but Zerto is going to follow up.

Zerto has been in production for three months.

It seems stable so far.

The scalability seems pretty easy.

Customer service is really good. Technical technical support is lacking. At least from who I've been talking to. Maybe my case has not gotten bumped up to the higher level technicians. Customer support is great, and they're really responsive but their technical knowledge is just not quite there.

Zerto's documentation is outdated. I'm finding it hard to find documents related to my questions. Their documentation is bad.

The initial setup was very easy. We needed a little help with the initial configuration, but it was pretty straightforward.

We worked with Eagle Technologies for the deployment. We loved them.

I wasn't involved in negotiating any pricing. It evidently worked into our budget.

We also looked at Cohesity and Rubrik. I don't know that there's anything like Zerto. We went with Zerto because our third-party vendor recommended it. We also did a proof of concept two years ago. We liked what we saw with Zerto so we went with it.

Everybody taunts their one pane of glass but Zerto is simple to use. I really like the GUI, the interface is not too busy.

I would rate Zerto a nine out of ten. We don't have a test network setup. I know with Zerto, you can simulate a recovery.

Zerto would be a perfect ten if the documentation was easier and if level 1 support would be more knowledgeable.

We use the solution to protect our general workloads, migrating VMs to the cloud and protecting VMs in the cloud. Our primary use case is to protect and provide DR.

Zerto has enabled us to mature our DR stance quite a bit in how we protect functions.

The near-synchronous replication works pretty well. Going from RPOs of an hour to five seconds is pretty interesting.

Zerto enables us to do disaster recovery in the cloud rather than in a physical data center.

Having disaster recovery in the cloud is very important for our organization as we're currently moving our production workloads to the cloud.

We use Zerto to help protect VMs in our environment. Our RPOs are getting lower.

The speed of recovery in Zerto is much faster than with SRM.

The on-prem to Azure, migration, and protection aspects are good. Zerto is one of the few tools that work pretty good and at moving between regions or clouds.

The near-synchronous replication is good.

Automated protection of workloads from one site to another could be improved. For example, with SRM, you can create a VM, and it automatically protects it based on mappings and other factors. Zerto does not do this.

I have been using Zerto for about a year.

It can throw us for a loop at times and it can be challenging to figure out.

We are pretty large-scale. It's been one of the challenges, as it seems pretty simple for smaller scales, but as you get larger, it gets more challenging, which is where the automation piece and lack of that comes in.

Level one and level two are excellent. The development team is a challenge sometimes because they work four days a week. Sometimes, when we have to have a Dev escalation or a severe issue, it takes quite a long time to get a response.

We use SRM and Commvault. Zerto is better than both of them. Commvault is not great at Orchestration DR, and SRM locks you into VMware.

We were early adopters, so the deployment has been challenging, but it's definitely getting more mature and better as we go.

We bought it from a reseller but we used Zerto services to get it going.

It has reasonable pricing comparable to VMware and others.

Overall, I rate Zerto an eight out of ten because it makes testing easy and provides flexibility between on-premises and various clouds.

We store a lot of raw data for reporting and use Zerto to protect that data.

Before implementing Zerto, we lacked a data protection and recovery solution, resulting in a significant data loss incident of approximately 70 percent during a past event.

Zerto is easy to use.

The near-synchronous replication offers a critical advantage for our customers' multi-platform environments by providing continuous data protection with minimal delay.

The main benefit of Zerto is that it doesn't affect the performance of the cloud platform while protecting the data. We realized the benefits of Zerto within the first three months.

Zerto's implementation has significantly improved our recovery time objective, allowing us to get our systems back online much quicker.

Zerto has significantly improved our disaster recovery capabilities, reducing downtime from days to just two hours.

With Zerto in place, our disaster recovery time has been reduced to a maximum of two days, whereas previously we lacked a recovery solution altogether.

Our disaster recovery testing with Zerto exceeded expectations. We aimed to restore all data within five days, but using Zerto's capabilities, we achieved a full recovery in just two days.

Zerto saved our staff three days of work, freeing them for other tasks.

Zerto's continuous data protection, journal-based recovery, automation, multi-cloud and hybrid cloud support, and non-disruptive testing have significantly improved our IT resilience strategy. These features not only enhance data protection and improve our Recovery Time Objective and Recovery Point Objective but also provide the flexibility and scalability needed for a robust IT environment.

It facilitates a cloud-based disaster recovery solution, eliminating the need for a dedicated physical data center to ensure business continuity in the event of an outage.

Zerto was our disaster recovery solution of choice because it offers a cloud-based implementation, which perfectly aligned with our organization's prioritization of cloud-based disaster recovery.

It stands out for its user-friendly approach to data protection and recovery, allowing for quick and efficient backups and restores.

Zerto's pricing structure could be more competitive to better suit the needs of a wider range of businesses.

The setup process could be simpler. A more streamlined installation would improve the user experience.

Zerto's long-term data storage capabilities, specifically how long data can be retained and managed, could benefit from further development.

I have been using Zerto for ten months.

We sometimes face challenges that require multiple hours of downtime but it is rare. I would rate the stability eight out of ten.

Zerto is expensive.

The technical support is quick to respond.

Integrating the initial deployment into our infrastructure proved to be a complex undertaking.

To ensure a smooth implementation, we prioritized planning and engagement, starting with management and then incorporating other stakeholders. We piloted the project with the operations team for a month before a full organizational rollout.

The deployment took around one week and involved six people.

The implementation was completed in-house.

Zerto provides a return on investment through the peace of mind we get knowing that all of our data is protected.

Zerto is expensive.

After considering both Commvault and Carbonite, we ultimately decided Zerto was the best fit for our data protection needs.

Zerto emerged as our choice for data protection because its feature set directly addressed the specific needs of our organization.

I would rate Zerto eight out of ten.

Maintaining Zerto is manageable as we have a dedicated team of three people responsible for its upkeep.

Our organization consists of 40 analysts in one site.

Zerto provides robust data protection and excels in disaster recovery for businesses, but its cost may be steeper compared to other solutions.

We use Zerto to protect our centralized environment on our data center.

We implemented Zerto to ensure our environment keeps running in the event of power failure or hardware issues.

Zerto is extremely easy to use.

The near synchronous replication is powerful and eliminates the need to use other storage solutions. The near synchronous replication is important for the services that we are providing.

It has drastically reduced our downtime. Previously, recovering from an issue took three days, but now with Zerto, we're back up and running in about an hour, minimizing disruption and keeping our business operational.

The continuous data protection has transformed our IT operations. By enabling us to restore our entire environment and resume functionality within hours, it eliminates the multi-day downtime we previously experienced in recovery situations.

Zerto has significantly reduced our operational costs and time commitment by 90 percent. Compared to our previous solution, Zerto requires fewer resources and allows us to complete tasks much faster.

Zerto safeguards our virtual machines, ensuring critical applications recover in minutes while less essential ones are restored within hours. This significant improvement replaces our previous recovery time of two to three days for the entire environment.

It has reduced our downtime by 85 percent.

While we hadn't previously tested our disaster recovery plan, our current backups and improved recovery time give us greater confidence in our ability to respond to an incident.

Zerto strengthens our IT team's disaster recovery plan by boosting their confidence in the system's reliability. With Zerto, the system can now recover quickly from the biannual power outages that used to cause instability, thanks to its improved stability within the failover environment.

The most valuable features of Zerto are the ease of use and recovery speed.

The most valuable feature for enhancing our data protection strategy is the ability to test and validate that the protection is up and running when we need it.

While Zerto's current version supports VMware environments, I'd like the added flexibility of using Hypervisors as well. Although previous Zerto versions offered this functionality, it seems to be missing in the latest iteration.

We are expecting to have VME to VMware or VMware to HPE VME to have fully functional environmen

I have been using Zerto for 3 years

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

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

The technical support team was responsive and effective in resolving the small number of problems we encountered.

We used to rely solely on Veeam for backups, but now we have a layered approach. We still perform Veeam backups for long-term data protection. However, we've added Zerto for disaster recovery, enabling much faster recoveries of our critical systems in case of a major outage. This way, we have both comprehensive backups and the ability to get our key functions back up and running quickly.

Zerto boasts faster recovery speeds than Veeam and offers a significantly easier testing process.

The deployment was straightforward. It was completed by one person in one day.

The time Zerto saves us restoring our services provides a significant return on investment.

I would rate Zerto nine out of ten.

Our Zerto deployment spans multiple locations and is managed by a team of eight administrators who are responsible for protecting 30 virtual machines.

While Zerto itself doesn't require regular maintenance, it's important to conduct periodic tests to verify our disaster recovery functionality and generate reports to monitor its health.

I would recommend Zerto because it provides better and more simplified protection.

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 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.