What is your primary use case for Zerto?

Our primary use case is for seamless migration to our client's cloud environment, ensuring a non-destructive migration with minimal downtime. We focus on cloud adoption and migration, and Zerto assists with the smooth migration of client workloads to the cloud environment. Additionally, Zerto provides disaster recovery solutions, data protection, and ensures minimal disruption during migration.

I use Zerto to monitor replication, configure protection, and manage disaster recovery and performance. We implemented Zerto to manage disaster recovery and also for faster performance on backups and failovers.

We primarily use the solution for DR purposes.

We use the solution for disaster recovery purposes.

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.

We use Zerto for disaster recovery and cloud migration. We are an MSP, so we have Zerto deployed on multiple public clouds, private clouds, and on-premises. We implemented Zerto because its continuous data protection significantly reduces data loss and downtime costs. In the event of a production issue, we can quickly recover using the user-friendly Check Point feature. Zerto also offers flexible support for storage models, primary and disaster recovery, and hypervisors.

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.

We use Zerto for disaster recovery and backup of our application server.

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.

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

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

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.

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

We use Zerto for our application data recovery.

Implementing failover to a secondary data center is crucial for ensuring business continuity in the event of primary data center loss. This strategy involves automatically redirecting operations and services to the secondary data center when the primary one becomes unavailable. This not only minimizes downtime but also enhances overall system reliability. The failover process requires robust synchronization mechanisms to ensure data consistency between the primary and secondary data centers. Regular testing and monitoring are essential to validate the effectiveness of the failover mechanism and identify and address any potential issues proactively. In summary, failover to a secondary data center is a strategic measure to safeguard against disruptions, offering a resilient solution for maintaining seamless operations in dynamic and challenging environments.

For one client, the use case was to facilitate data center migration, and for another client, it was for failover and failback of the data center for DR. We wanted to have controlled failover and failback of related applications for DR. We have not used it for disaster recovery in the cloud. Everything has been on-prem so far.

It was a pilot. We did a bake-off between Zerto and RP for VM, which was an EMC product. It was to fail over 130 Oracle databases. We wanted to handle disaster recovery for our data center. Zerto was mainly a failover product. We did not use any security layering.

We primarily use Zerto for disaster recovery.

The solution was primarily used for disaster recovery for clients. If there was a major issue in the data center, it allowed the client to move to the second data center. It was also used for migration to virtual machines.

We use Zerto to replicate all of our production solutions. We replicate to cloud storage.

The primary use case is disaster recovery.

In my previous company, we used it for recovery. We'd use it for annual DR testing. At that point in time, I was doing recovery for a few customers in government, financial, and other institutions.

I use Zerto for disaster recovery.

We primarily use Zerto for DR as a service but also for high availability purposes. It's mostly deployed at our on-prem colocation data center. We also do a little on the cloud, as well.

I am a system engineer and IT architect. We use Zerto to protect our production -environment and critical applications. Everything is on-prem. We don't do any DR to the cloud. We're protecting around 300 VMs right now.

We've been using Zerto for data center migration, but we will begin using it for disaster recovery. Because of some data center issues, we're still using version 9.5. One of our data centers is at 6.5 and the other one is at 7, so we can't move any or upgrade to 10.

Our primary use case is for disaster recovery. We replicate up to Azure, and that's essentially disaster recovery as a service. Overall, the effects of RPO have been great. They are never more than a minute or two, even throughout the production day.

Our primary use cases include replication and disaster recovery.

We had a specific use case for one of our clients that had a regulatory requirement for backups to be further than what we were already able to give with our current backup structure. We are actually a global company and our global headquarters are in Northern Ireland. We're located in Pennsylvania. We're the North American headquarters. We implemented Zerto, and we replicate on our Northern Ireland site. That got us more business with our clients.

Our primary use cases are for disaster recovery replication side to side. We were running VMware Site Recovery Manager and it ran well. It was a great solution compared to what we had before. We didn't have disaster recovery issues. We were just doing our test. It ran superbly. Zerto improved the amount of time it took to failover and address any issues. We went from failing over in about three or four hours during the test to it taking one hour. It was very fast. It's in a single department in a single company. Luckily, we don't really have to support much of our field force. We have approximately 4,000 agents who are in eleven states, but we don't have to go out into the states. We're on in one building and it's one business unit. We manage the failovers but it's just one group management. Approximately four users use the solution.

We currently utilize Zerto as our disaster recovery solution. With Zerto, we replicate production virtual machines to our DR site. This approach enables us to recover and bring everything back online in a disaster swiftly. Our recovery point objective can be as low as five seconds, depending on the replication point. Additionally, we employ Zerto for scaling purposes and for conducting upgrade testing. This entails spinning up VMs in an isolated environment, allowing us to perform various tests. For example, a few years ago, we tested the upgrade of our active directory domain controllers. By validating processes within this environment, we can ensure their smooth execution in production. These are the two primary use cases for Zerto in our organization.

We utilize Zerto for our disaster recovery solution, which involves replicating our virtual machines to a remote hot site to ensure failover capabilities.

I am the global lead for infrastructure for the VMware and Windows Server environments. We are mainly using Zerto for disaster recovery. We have a prime site in Missouri, and we have plants in Taiwan, Malaysia, Japan, Italy, and Korea. We have 400 to 500 users in the environment. We have installed Zerto software on the DR site and the production site. We will be using Zerto for the production site for all the centrally used applications, such as SAP, file servers, and Exchange. Because this is a central site, a lot of other sites come to this site for various things. We also have Zerto on the DR site. In manufacturing, there are 60 or 70 tools, and each tool costs around $500,000. When the site goes down, you cannot transfer these tools very easily. It takes time. These are big tools, and it takes time for them to go somewhere else. You have to do a test again and go through the qualifications procedure, which takes time. As the IT department, we are interested in getting the applications that are used by all the sites centrally located, and if anything happens to the primary site, we want all the applications to be already there on the disaster recovery site. We just bring them up, and we are good to go. Zerto will help to protect VMs in our environment. We have tried that in the test environment. That would be another reason for using Zerto.

In my previous company, I used it for disaster recovery. We protected our critical workloads in another data center where we would replicate our primary workloads. In my current company, we're in the middle of a data center consolidation project and we're using Zerto in two ways. First, we're migrating the workloads we had in one data center to another, about 250 servers. It took us about three months to complete the migration. We had to schedule all of our moves and work with the business to validate that the services were fine and accessible, once they were moved to the other data center. We've completed the migration and a data center has been shut down, and we're working on building disaster recovery for our primary workloads in Azure.

We use it for disaster recovery. We were looking for faster recovery time objectives. Our primary use case is protecting virtual machines in our environment.

We use Zerto as our disaster recovery solution for our servers in the multiple data centers we have. It allows us to replicate our servers from one data center to another and perform disaster recovery testing to ensure compliance with our organization's DR requirements. Our organization wanted a solution for replication, whether for VMs or Azure sites, and the ability to migrate servers or VPGs in case of a disaster or for testing purposes. And we wanted something reliable.

We primarily use Zerto for disaster recovery and business continuity. We have also used it significantly for transferring workloads between different environments.

We mostly use Zerto to replicate applications and database servers between our primary data center and our disaster recovery site. We have a number of business applications, Oracle servers, and three sites that we replicate to our DR site, and Zerto works well. We deployed Zerto on private cloud and on-prem.

Our biggest use case is real-time replication to a secondary site in case of the need for a disaster failover. We also use it for file-level protection and restore, but the main purpose is to help add another layer of protection in the event of a disaster.

Zerto is primarily used for disaster recovery. In rare cases, it is also used for backup, but only for long-term storage. We deployed our on-premises infrastructure in two data centers in Russia located in two cities, and multiple regions with combined infrastructure. We also had two data centers in Europe.

Zerto is used as our go-to disaster recovery failover software for the replication of key systems from our main office to our main data center. We primarily use it to protect VMs.

We use Zerto for backups and DR; we back up to a StoreOnce unit and then offsite. We have over 11 servers, including three Oracle servers, one Oracle database, and an Active Directory.

We have critical servers at remote sites that failover or are replicated to our main data center in case of an emergency. If a remote site has a failure, we can spin up that virtual machine from our data center. We operate a hub and spoke design with a centralized data center hosting our main instance, reaching out to roughly 78 remote locations. We handle the VPGs through the centralized management console at our data center. We also use the Zerto to replicate from a primary host to a secondary host in case the primary goes down; we have a kind of cold box to which the solution replicates. Our final use case is if we are updating a plant's entire server rack, and we use Zerto to replicate the old servers onto the new ones, which results in less downtime.

After a car hit a power pole and knocked out the Data Center in our building, management realized the value of Zerto and being able to failover in about an hour to the DR site and be back up and running on our mission-critical applications. 

This was very helpful as power took over a day to get restored.

We offer Zerto as a DRaaS service to our customers. We have it installed at almost all of our data centers within Canada, the US, the UK, and Australia.

Our primary use case currently is for replicating virtual machines on a production site and for backups. We also use it for onsite cloning, and we have a license that enables us to do that. We don't use Zerto in the cloud at the moment.

Our use case has evolved over the years. Initially, we strictly used Zerto for its original purpose: continuous replication of our virtual machines. We had a ransomware attack and needed to instantly restore virtual machines on or off-site without too much aggravation. That has been successful. The product expanded since then, and we're using many other features now. We haven't replaced our other backup solutions yet, but we're considering it. I need to do some more testing of my databases and mail servers. It depends on how we utilize the cloud in the business. We're currently using an on-prem data center with a reserve disaster recovery site, but we're contemplating a transition to Azure. For example, if we are using Exchange Online, I'll need to find an appropriate backup solution. It may be something in the Azure stack, but I don't know yet. We plan to use Zerto for cloud disaster recovery eventually. I'm in an upgrade cycle because I need to upgrade various backend elements to put me on 9.5, which I think is the latest release. That will give me immutable storage and benefits like single sign-on and multifactor authentication, which insurance companies increasingly request for all our applications. I plan to start shifting workloads into the cloud, and Zerto is one of the tools that will help me with that. Zerto is deployed across my organization's entire computing infrastructure. We've got several different departments in the firm, so it handles many workloads. That sits on a Windows environment, and it replicates a data center where we just buy some shelving space. Including equity partners, consultants, and other visiting members of staff, we have around 250 users over seven sites.

We use Zerto as a DR tool. Instead of having to have a duplicate DR server, we can add a system to BPG and point it to whatever our DR site will be and replicate it for customers. We also use it for migration planning. If we need to move VMs from on-premise to Azure or back, or it was built in the wrong place, we can easily move it over.

We use it primarily for DR.

We offer Zerto to our application owners and system owners as a DR solution for them. It's part of our service offering from the VMware side because we do the infrastructure for them. We help orchestrate and set it up for them at the back end. We also use Zerto to remove RDMs from the environment and help manage our storage. If we need to relocate the storage, we use Zerto, especially when going from multiple vCenters or multiple clusters. It's very convenient.

It is mainly for disaster recovery of our public-facing website. I oversee the infrastructure team. I'm the lead for the infrastructure. It is not one of the technologies that I've primarily managed. As an infrastructure lead, I have my hands on every project, and it is hard for me to just focus on one. Especially because it is more of a disaster-recovery type solution for us, as long as replication is going fine and there are no issues, we don't really go in and play with it much.

Its primary use case is for disaster recovery of 10 servers that we have in-house.

We use Zerto to replicate to a cloud center.

My primary use case is doing demos and testing to make sure that Zerto is going to work for our customers. I test it mainly for disaster recovery and backup. We've tested with VMware, Zadara, and AWS.

Our primary use case for Zerto is disaster recovery.

We primarily use it for disaster recovery.

We use this solution for replication from our primary data center to the secondary data center.

Our main use case for this solution is the data center migration. We are in the process of moving from our legacy data center and all the VMs into our new data center. In the future, we would like to look more into disaster recovery using Zerto but that's a much longer process and we are still looking into it.

We use Zerto to help our customers migrate and consolidate data centers, especially crossing different geo spaces or long distances. I haven't used it for downtime, but our customers have it configured for all of their disaster recovery needs.

We use it mostly for VMs that are hosting client-facing applications and mostly client databases. We replicate 100 servers; we have 100 protected VMs.

We primarily use it for DR, that is, for VM replication between two data centers, using it not only for replication but also for orchestration.

Our use case is disaster recovery or failover. It makes it a lot easier for us to actually test DR because of some of the coordination and orchestration that are a part of Zerto. However, our use case is strictly DR, making sure that we have the right RPOs, and Zerto does a good job of handling that.

We have previously used Zerto for data center migration projects. We have another data center migration coming up within the next year where we will be using Zerto as well.

We have customers who come in for DR as a service, but we also do inter-cloud DR.

We are replicating all of our production VMs to a DR site. We also have another offsite vCenter that we are replicating to a DR site for protection and eventual testing.

We mostly use it for disaster recovery purposes. We do a lot of migrations as well, e.g., VM from one site to another. We use Zerto for that, as we have hundreds of VMs that we protect as our main DR position using Zerto. In general, our DR position is entirely based around Zerto. We use it for everything. We just have a couple things that we don't put on it. There are a couple of Oracle things that we replicate with different methods, but we pretty much do everything related to DR with Zerto. We are not using it for backup. We are using it for continuous DR and replication between two on-prem sites. We have two data center sites with bidirectional replications. Each site protects the other site and we have our VPGs that go back and forth.

We have three locations. We replicate circularly around all those locations for all our VMs. This is for DR.

Our use cases are disaster recovery and long-term retention against ransomware.

We use it for DR and general backup. We have snapshots or shadow copies with Microsoft and we do Zerto backups to our other locations so we can always get the data back.

We use it for disaster recovery, by replicating to our DR data center.

Our primary use case is disaster recovery, as well as data center migration when we went to a new VMware infrastructure platform.

Our main use case for this solution is disaster recovery, migration and app testing.

We work in a public safety environment and we use Zerto for disaster recovery.

We started off using this solution for disaster recovery and DR testing but then it morphed into more of a file recovery tool. We can usually get closer to a point in time recovery using Zerto versus the nightly backups that we do.

We purchased Zerto for our business continuity and DR approach to make sure that workloads are available. We have 1,000 servers but are only protecting 250 of them because they are our core servers. The ones we don't currently protect are Tier three applications.

We have approximately 1500 to 2000 Hyper-V machines. Those Hyper-V machines are being used and converted to VMware. We use Zerto for our conversion from Hyper-V to VMware. We are also considering using it for DR purposes. Our prod environment runs on-premises and we have a DR copy of everything that we run in production. Our development runs on machines and hardware. In the event of a DR event, we would shut down dev and bring up our secondary copy of production. We hope that Zerto is going to be the tool to help us do that.

We use it for our conversion from Hyper-V to VMware. The DR purposes are being looked into as well. We've got about 1500 to 2000 Hyper-V machines. These Hyper-V machines are used and converted to VMware, and these are the two environments that we work with now, both on-premises and in a hosted environment.

In the past, we were predominantly using Citrix Hypervisor in the Hyper-V shop. Now that we've moved to VMware, we utilize Zerto to move those VMs from Hyper-V and Citrix Hypervisor over to VMware. We're also looking at utilizing it for our DR site to be able to push up those VMs to the remote site in the case of a DR situation.

We are using it to decommission a data center, then moving the data over to other data centers that will still persist within our environment. Also, we now have a more robust disaster recovery for a lot of our non-vital, non-critical applications.

We use it mainly to move the server alarm between vCenter and the physical center.

I've used it for a temporary migration. We had to shut down a data center and we moved some database servers over to a disaster recovery site. We then did the maintenance at the data center and brought them back. We're using it only for on-prem and we use it to replicate from our onsite data center to a co-location, but there is a fiber connection between the two, so it isn't an internet-based replication.

We are mainly using it for DR and, in a few use cases, we leverage it for migration as well. It really fits our use cases.

Zerto is primarily used for site-to-site replication and recovery, low RTO and RPO, and migration from onsite to the cloud. Currently, we have ZVMs installed on Windows Servers in our environment, vRAs and VRAHs installed on our vCenter environment, and ZCAs installed in our Azure environment. I am not the primary user of Zerto. I am sort of the implementation or API specialist on it.

I primarily use it for disaster recovery backup. Also, whenever we need to move things between our different environments, e.g., moving it to different vCenters and Azure, that is primarily done through Zerto

Our primary use cases were designed around backing up and being able to restore our management plan. This isn't something used for our department users. It is specifically for our infrastructure, things like vCenter, vRealize Operations—all those things that we still have to maintain. We wanted something a little more granular than just a standard backup. We needed to be able to say, "Rollback half an hour or an hour," as opposed to following the backup schedule that the larger backup system provided.

We use it to protect VMs. Disaster recovery is our use case. Our compliance requires that we need to simulate a DR exercise every six months if we are protecting a VM. One of the features of Zerto is simulating a disaster recovery exercise in case of failure. We fail back the VM to the DR site, and when the event is over, we fail it back to the production site. We are using one of the newer releases, but we are still six months behind.

We use it for backup and replication.

We've been using it to consolidate data centers. We have 13 hospitals and two main data centers and a cloud presence. We're trying to collapse everything. We've been using Zerto to move the workloads over to our primaries.

We primarily use Zerto for disaster recovery and backups.

We use Zerto for offsite replication.

The primary use case is to migrate VMs. It's easier to use than HCX and SRM.

We have a production environment that we are replicating to a warm data center, and Zerto keeps our virtual machine-protected groups in continuous sync. It has been working really well for us.

We are failing over approximately 250 systems. In many ways, this could impact 3,800 insurance agents across 11 states. There are two sites: the source site and the production site. Those are failing over to another data center about 150 miles north of my location.

We use Zerto primarily for disaster recovery replication between two sites. We started to use this solution to help with disaster recovery planning and fast recoverability. The solution is deployed on-premises. We have two different SANS by EMC, VMware as our DOS network operating system, and we have a mixture of Windows, Linux, Red Hat, and Cisco switches. We haven't done DR in the cloud because we don't do anything in the cloud. We haven't used Zerto for immutable data copies because everything is on-premises. We just use it in a VM environment for the VMDK replication.

We use Zerto for our disaster recovery procedure and testing to ensure our servers and virtual machines can failover from a production environment if there's a catastrophe. We have a disaster recovery test twice a year and use Zerto to recover the environment. We have two environments for Zerto. One is for the US, and the other is for Europe. We updated one last week to version 9.0, and the other still uses version 8.5 but I will update that today or tomorrow.

We use Zerto as our primary disaster recovery tool for our most important servers.

Zerto is deployed on a VM, and we use it to replicate the database for our POS system in our data center.

We use Zerto for disaster recovery (DR) purposes. We needed a tool to provide a quick resolution during a failure or problem and help us achieve our goals related to our service level agreement (SLA). We needed a tool that would help us in providing the availability of lost services within a specific time frame. We wanted to make sure that in case there is a problem and we have to execute the DR procedure, it is quick, easy, and safe. So, the main purpose for going for Zerto is related to meeting the required parameters for RPO and RTO. We don't use Zerto for backup purposes. It is used only for virtual machines. We also have physical servers, but we have different tools for backup. Currently, we are using it for on-premise data centers, but we also do proof of concept tests with public clouds or hybrid clouds.

We're currently doing a two-tiered on-site and off-site replication, with one long-term retention being displaced into a cloud and one long-term retention being displaced to a third data center. We were looking to make our recovery solution more streamlined and efficient, that's why we implemented this product. We're not as huge as everybody else. We just have large devices. We have four SQL servers running, each of which is about six terabytes, so our continuous replication is a lot larger than others. We also have multiple secured file storages in the two-terabyte range, so we replicate around 140 terabytes continuously, utilizing about 60 VM servers. Our primary and secondary production is VMware, and our third-tier backup area is a hypervisor.

We're solving the issues of disaster recovery with it. So, our main use case is disaster recovery. We use it to do real-time replication of our data so that if we needed to failover for whatever reason or we had a disaster at our primary data center, we would be able to spin up in our colo disaster recovery location with minimum downtime. Our delay is about five seconds. So, if something negative were to happen to our data center, our DR copy would be within five seconds of the original copy, which is pretty good. We are also using it for testing. Our setup is on-prem. It enables you to do DR in the cloud rather than in a physical data center, but we didn't go that route. We went the route of creating our own colo location. So, instead of leveraging Azure or AWS, we decided to maintain our own facility. Our primary data center is on-prem, and our disaster recovery location is a colo location that we control. The current version that we're using is 9.5, which is the latest. When we installed it, it was probably version 8.

We've got two data centers, and for any of our applications that are not in some kind of a load-balanced or high-availability cluster, we use Zerto to replicate them, to make them as highly available as possible, without building that into the solution. We replicate between 100 and 150 different VMs from our North Carolina data center to our Chicago data center.

We use Zerto as a DR replicator for VMWare VC, VCD, and public cloud. 

We have developed a Multi-replicator tool to support complex scenarios with multiple Replicators, networking and security (FW) protection plans, recovery plans, orchestration capabilities which use Zerto API to collect current status and manage VPG, testing & failovers 

Our primary use case for Zerto is DR replication for a subset of business critical applications that require a very low RPO\RTO to a co-location datacenter.

Replication for very high RPO servers.

We primarily use the solution for continuous data protection and cloud onboarding.

Zerto is our primary means of failing over our critical production loads that have a relatively low RPO/RTO. This is our use case for this solution.

We use Zerto as a migration platform from a customer's data center or from their on-premises environment to our data centers. We also use it for disaster recovery.

Right now, we use it just for disaster recovery.

We use it for a hot DR site for our primary production environment, allowing us to fail over all of our production servers in case of an emergency.

We use it primarily for backup and recovery of individual servers and databases. We also use it for long-term retention.

We didn't have any kind of disaster recovery solution in our environment, whatsoever. We're using it for disaster recovery.

Zerto is part of our disaster recovery plan. We have it set up in our main office and in a remote location in another state. We replicate all of our ERP data over to the replication site utilizing Zerto. In case there's a failure or a ransomware attack, or anything that we need to restore back to a point in time, in real time, Zerto covers those scenarios.

We're replicating mainly some of our critical applications. One is our backup solution and then also some critical applications that we don't want to have to recover from tapes. That's been working very well for us. We actually just recently went through a DR rehearsal, where we ran a quick test and that ran for about a week and then completed that test. Then we were able to report that we were able to successfully recover our critical ERP system inside of the remote location successfully.

It's deployed on private cloud. I have two data centers, one in New Jersey, one in Ohio, which is my job site. I'm using a Zerto instance for my servers and another for my VDI machines. I can replicate everything.

We use Zerto to enable our hot site configuration. We have two data centers. One of them is in one of our corporate buildings, which is our primary, and then we have a co-location center rack that we rent for our hot site backup or app. We use Zerto to replicate our servers and our VMs between those two sites. So, primarily, it is there in case of a disaster or malware attack, etc. We also use it to restore files on the fly for users if they accidentally delete the wrong file or something like that. From a restoration standpoint, it is closer to the frontline of our security posture. We would first look to restore items. For removing the threat and everything like that, it obviously wouldn't be involved, but from a restoration standpoint, it would be frontline. We have not yet used the cloud with Zerto. We just use on-prem physical servers.

Zerto runs on a Windows Virtual Server and we have it installed at two sites. There is the production site, as well as the failover DR site. We use this product almost exclusively for disaster recovery. It is responsible for the automated recovery of what we deem to be our mission-critical servers.

Our primary use case is for our Tier 1 application environment, we're an SQL environment. We have around 25 VMs that are replicated to a hot site or warm site. And we're a VMware shop and we use Pure Storage as our SAN, but that doesn't matter because Zerto's agnostic. We're a small shop. I am the only Zerto user and my official title is Senior Systems Engineer. I handle anything data center-related as far as information stack, the blades, networking, VMware Hypervisor, and Pure Storage. We also have a Citrix environment as well we have to support. I do all of the data center work.

We have typical use cases for it: resilience and disaster recovery. They have some other functionalities that their software can help account for, but we are using its disaster recovery and resilience, which are kind of its core functions.

It is for real-time data protection and, if needed, for the ability to recover within seconds at a point in time. It is deployed on-premise and multi-cloud on Azure and AWS.

Database replication is our primary use case. We don't use Zerto for backups. We use Zerto as DR at our sites. It is deployed on-premises at several sites.

We use Zerto for real-time replication of our systems, company-wide. The main reason is disaster recovery failover.

We use Zerto to replicate data between our on-premises data centers, as well as for replicating data to the cloud. It is used primarily for disaster recovery, and we're not using it very much for backups.

We have two primary use cases. One would be to use it in reaction to a cyber-terror event, particularly ransomware, because Zerto has point-in-time backup. If we find an area that needs to be restored, as long as we figure it out within 24 hours, which is approximately the amount of time we have replicated, we can go back to a point in time. Let's say the files got encrypted at 9:30 AM. We can say restore our 9:29 AM copy of what the data looked like at that point. We have not needed to use that, thankfully, because we've been educating our users very well. The other case that we would use it for is because we're in a hurricane area. Our particular office is actually in an evacuation area, typically, meaning that we're close enough to the coast that should a hurricane event come through, they generally force us out of the area. What we would do if we needed it, and thankfully we haven't yet, would be to shut down our primary on-prem services to make them a little bit more resistant to water damage. Obviously, if they're not running, they're a little bit less likely to get zapped if there is some water damage. Then we can bring up the copies that we have at our data center and run remotely from that if. It doesn't have a full copy of our entire environment, but it does have a copy of our ERP system, as far as sales are concerned. We wouldn't be able to ship anything, but we could look at orders and help our customers. We could even take orders if we needed to, although we wouldn't be able to process them. Zerto is a replication solution. It copies our setup which is on-prem to our data center, which is also somewhat local, about 15 miles away. It doesn't really do anything in the cloud other than move data across it. We're not replicating to any cloud-based services like Amazon or Azure. Essentially, we're using it at two on-premises locations: Our primary location, which is what is being replicated, and the replicated copy is being stored at another on-premises location, nearby.

We mostly use it just for disaster recovery. We also utilize it for our quarterly and annual DR test. It is on-prem. We have a primary location and a DR location.

Originally, I was looking for a solution that allowed us to replicate our critical workloads to a cloud target and then pay a monthly fee to have it stored there. Then, if some kind of disaster happened, we would have the ability to instantiate or spin up those workloads in a cloud environment and provide access to our applications. That was the ask of the platform. We are a manufacturing company, so our environment wouldn't be drastically affected by a webpage outage. However, depending on the applications that are affected, being a $15 billion dollar company, there could be a significant impact.

Our primary use case is disaster recovery. We have Zerto deployed on-premises at both our primary and DR locations.

We're using it for site plate replication and fail-over or disaster recovery. We're primarily using it to replicate between the data centers that we own and operate.

We are an electric utility and we have some pretty critical workloads. We have identified the most critical workloads in our environment and have implemented Zerto as a protective measure for them. We try to keep our critical workloads protected, which are a subset of our systems. For example, we're not going to protect a print server with Zerto.

We have Zerto as an emergency backup if we were to lose electricity or compute. I purchased Zerto because I wanted to get a return to operations and to minimize the downtime.

We primarily use Zerto for replication and disaster recovery.

I am a solution provider and Zerto is one of the products that I implement for my clients. Most of my customers use this product for disaster recovery purposes. Some of them use it in a local, on-premises environment, whereas other customers use it in the cloud. We have assisted some of our clients with on-premises to cloud migration. These were customers that had an established local environment but wanted to explore the cloud. For these clients, it is a cloud-based DR implementation. There are four or five customers that did not want a cloud deployment, so we have implemented the DR site on-premises for them. If the client is given the choice, typically they prefer a cloud-based deployment. CDP technology is becoming the new norm, even for the backup industry. However, there are some instances where it is not an option. For example, in some situations, they cannot use cloud-based storage due to legal and compliance requirements. Some of our customers that are making a digital transformation cannot afford to lose hours or even minutes of data. As such, I think that cloud-based disaster recovery is the future and the customers understand why it is much more important for them. Together with our reputation, I see this as a game-changing situation.

We are using Zerto to facilitate cloud adoption in the organization. Our product teams are migrating their VMware workloads to the cloud, and Zerto is helping with that task.

We primarily use Zerto for backing up our databases. We are heavily invested in database technology. We use SQL databases such as PostgreSQL and MS SQL, and we are also functional with NoSQL databases. Our use cases are majorly relying on databases for financial vendors and most of the time, we have to perform day-to-day operations with respect to finance and accounting. We have been using the data retention functionality for a long time and whenever there is a failure and the system goes down, we recover the data from that particular snapshot in time. We also require security, as it is one of the major concerns. Ultimately, we align these two things together. We are deployed in AWS, although we are also deploying in GCP and plan to do so with Azure as well.

Our primary use case is for disaster recovery and migrations. We have two primary sites that we replicate to. If there are on-prem clients we replicate back and forth between those two and then we replicate our off-prems to them as well. We use on and off-prem as well as Azure.

Right now, everything is on-prem including LTR. We are looking at adding the Azure features but we're not quite there yet. We purchased Zerto to replace our Legacy backup system that still had disks, Archiver Appliance, and everything like that. We had wanted to do something that was diskless but still gave us multiple copies. So we were utilizing both the instantaneous backup and recovery, as well as the LTR, Long Term Retention, function. We do our short-term backup with normal journaling and then our longer-term retention with the LTR appliance, which is going to dedicated hardware in one of our data centers. We use Zerto for both backup and disaster recovery. It was fairly important that Zerto offers both of these features because Unitrends did provide the traditional backup piece. They also had another product called ReliableDR, which they later rolled into a different product. Unitrends actually bought the company. That piece provided the same functionality as what Zerto is doing now, but with Unitrends that was separate licensing and a different management interface. It wasn't nice to have to bounce between the two systems. The ability to do it all from a single pane of glass that is web-based is nice. It's definitely not going to save us money. It'll be a peace of mind thing, that we have another copy of our data somewhere. Our DR site is approximately 22 miles away. The likelihood of a tornado or something devastating two communities where our facilities are based is pretty slim. It's peace of mind and it does not require additional storage space on-prem. We know that the charges for data at rest are not free in Azure. We get good pricing discounts being in education but it definitely won't save money.

We are using Zerto as our disaster recovery solution for on-premises to Azure, and also from Azure to Azure between different regions. At this time, we are only using it for DR. However, we will also be using it for data center migration.

Our primary use case for Zerto is for disaster recovery. In the last few versions, they've offered backup, but we don't use it because it's not nearly as robust as what most of our customers are looking for. We also use it for migrations too, to migrate customers into our cloud, and things like that. But that's around 20% of our use case.

I am a cloud provider and I use Zerto to provide disaster recovery solutions for my clients. Recently, we had an issue where one of our customers using Oracle Server experienced corruption in a database. The customer doesn't know when the issue started, so we used Zerto. We started to do a real-live failover for the machine, and we were able to determine the timestamp for the start of the issue. Prior to this, Oracle engineers tried for four hours to fix the database but did not have any luck in doing so. Ultimately, we were able to save the customer's data by using Zerto. A few of my customers are using file-level restore but the majority of them are using the replication features for disaster recovery.

We are protecting 91 terabytes worth of data that consist of 200 virtual machines over the span of 96 tracking groups. We currently have 300 licenses and Zerto provides protection for our critical production systems with a 24-hour journal. We do utilize another platform to backup our entire enterprise as well as handling retention for a longer period of time. We limit Zerto access to our platform engineers so either our Linux administrators or our Windows administrators use the solution. When a virtual machine is tagged as the article, in other words something that should be replicated to a target data center, they have the authority to create a VM and make sure it is protected via Zerto. We have an annual DR test requirement. Initially, we used Zerto for testing a subset of our production systems and generated reports that would validate that the tests were successful. We leveraged Zerto to test failover for over 200 VMs by running it in the test scenario. We ran it for a couple of days and tested connectivity to verify that all the virtual machines were up and running and that disk integrity was fine. Over the years, we have moved from an offline test scenario to an actual real-life failover for subsets of applications. For a couple of years now, we have failed over applications into another data center and have run production from there on a small subset. Our vision going forward is to avoid these offline once a year tests and to periodically move applications from one data center to another in a real-time testing scenario. We currently have a production data center and then we have a co-location, which we are leasing. So we actually have two locations where we can failover. We do have a small cloud presence in Azure, and we have started a small cloud presence in AWS as well, but we are not running any IaaS virtual machines in those clouds. There's really been no cost-savings at all in the cloud so we've brought those work machines back on-premises.

We utilize Zerto to backup our on-prem environment to our cloud provider. We've also used it for migrations from on-prem to our cloud provider. Our deployment model is a hybrid. We're using on-prem and also replicating to Azure. It is used in our production environment and also our lower environment, on-prem. It's like a DR, as we're backing it all up to our cloud provider. There are a handful of servers involved, replicating and backing up.

We use this solution for disaster recovery and business continuance. We are protecting: SQL, our file servers, and some other applications that are specific to the healthcare domain.

We are using it to protect all our on-premise virtual workloads, which includes mission-critical applications, line of business applications, and several unstructured data type repositories for disaster recovery. It is our sole disaster recovery solution for what it does. It is protecting all the workloads at SmartBank. Both of our data centers are on-premise and in colocations. Our plan over the next year or two is that we will very likely be shifting to DR in the cloud.

We use the solution for two different data center sites. Inside the data centers we use VMware virtualization, NSX stretched VLANs and Dell servers. There are many servers, storage, virtualization, and a myriad of operating systems such as Red Hat and Windows Servers. We use Zerto to replicate our VMs from one site to the other, where we don't want to have to pay for two licenses of the same thing. We also do this to have high availability or to have the disaster recovery version of a piece of software. It is a benefit to be able to use Zerto to replicate that VM at the second site, and not have to power it on or anything. We know that it's always replicated on the other site. We currently use the solution for disaster recovery only but we are looking at longterm backup retention in the future.

We are using it for disaster recovery for our day-one applications that need to be up first, upon failover.

We use it for disaster recovery. We use it for some testing. And we use it for hot backups on databases.

It's on-prem only, and we're replicating part of production data centers to the DR location. We use it 100 percent for DR. Zerto, as a product, has a lot of capabilities, but we're only using it to replicate servers for disaster recovery, on-prem.

Our use case is 100 percent disaster recovery between two different geographies. We have a very large private cloud offering. We've got about 1,200 customers and almost 10,000 VMs that are under Zerto protection. Every one of those virtual machines needs to be replicated from Waltham to Chicago, from the East Coast of the U.S. to the central U.S. Likewise, we have a European business with the exact same flow, although it's much smaller as far as number of VMs; it might be a couple of hundred. That implementation is going from Berlin to Amsterdam. We've got one-way protection in two different geographies and all of those machines are under Zerto protection.

We needed Zerto in order to provide a disaster recovery solution for the entire organization. We use it to replicate some resources on-prem and for quick recovery. We also use Azure to replicate for disaster. If we ever have a catastrophic failure or attack at our main headquarters, we could failover and run our resources in Azure. We don't use Zerto for backup, we use Veeam. Once the new long-term retention features are added to Zerto, then we will investigate using it for that and possibly dropping Veeam.

We use it for DR as well as migration. We have four data centers and migrate workloads between them. We don't use it for backup.

We use Zerto for data migrations. We use it to move our virtual machines from one location or data center to another and eventually, we then switch that over to DR from our facility in one state to another. It's for the migration of existing VMs.

We have servers in Houston and we have servers at a DR site, we need to be able to make sure that they're replicated in some form or fashion. That's what we use Zerto for, to replicate between our primary site and our DR site.

We use Zerto for DR purposes, we replicate what's critical to continue business. We replicate it from our headquarters to another state, a DR site. If something happens to the headquarters where we are located we could run the continued business from the DR site with Zerto.

We use Zerto for disaster recovery data replication from our headquarters to an offsite data center at another location. It has replaced all of my legacy backup solutions.

We use it for disaster recovery and to migrate machines from one location to another.

We do a semiannual disaster recovery test, usually one in January and another in September, where we fail our entire company over to our Arizona DR facility. We run the business out of Arizona location for the day. In order to be able to do that, the Zerto application allows us to migrate 58 machines over to that location and allows us to run our business from that location for the course of the day.

We're backing up VMs with it. Our company has about 200 VMs and we're using Zerto on 30 of them in the main line of business applications. We're using it to replicate all that data over to our DR site so we can do our testing and reporting against that. Within those 30 servers we've broken out into three different SLAs on which ones get spun up first. We have it all scripted with monthly plans to fail over, spin it up, actually use it over there, spin it down, bring it back into production, etc.

It is controlling our mission-critical production system as a backup and a failover.

We protect about 15 virtual machines. We use Zerto to replicate them from our home office in Pennsylvania to our co-lo facility in Arizona. Our main data center is in our Pennsylvania office, but if that office were to go down, we would use this as a DR solution so we could run our company out of Arizona.

For all the most important applications, we are using Zerto as a hot site in case something were to go on with our on-prem data center-based applications. We can immediately resort to Zerto as a failover. It's deployed for replication from our data center into the public cloud.

We use Zerto for replication to a DR site of Windows and Unix machines. We like having a testable solution which does not interfere with the performance on our production machines. It has an included feature allowing assignment of a specific LAN or IP address to segregate the machine while testing. We are replicating 56 machines, totaling more than 30 TB, but compressing at 70 percent for space savings. We use the email alerts as a way to monitor replication status. This helps in off hours alerting for potential problems.

We use Zerto as a robust failover and replication solution. Currently we replicate about 50-55 VMs to our DR site. We have run multiple test failovers, and have even done a full-scale, full company REAL failover. Zerto worked flawlessly. We use Zerto to make sure that our primary Server farm is replicated and protected in case of a failover.

We use the solution for DR failover/testing on our DR site. We're a Windows/VMware environment and replicate 25 virtual machines from our primary data center to our disaster recovery site. The solution allows us to perform live failovers without shutting down our production systems.

We use Zerto to keep a replica copy of the core servers we have running at our backup site. In the case of an outage, we are able to flip over to our backup location. Zerto keeps these servers up to date within seconds and in the case of an outage at our core data center, we can flip over services with little to no data loss.

We use Zerto for disaster recovery of our tier 1 applications from our primary data center to our secondary data center. We have also used Zerto to successfully perform server migrations from one site to another for data center moves and company acquisitions. Our administrators love the product and it has been proven to be easier to use than VMware SRM which we were using before going with Zerto.

We use Zerto at our remote locations as a backup solution in environments where we don't have the infrastructure for redundancy. It allows us to use two HPE DL380 servers as stand-alone VMware hosts and replicate the VMs without needing shared storage.

We primarily use Zerto for our critical applications and infrastructure to allow immediate failover at our DR site. We licensed our critical applications and database servers and standard backup the rest. In order to increase uptime, we replicate our entire Active Directory infrastructure as well.

We use Zerto to protect our staff information against ransomware and is outlined in our disaster recovery plan. We have a DR site that we failover to if anything happens at our primary data center. We have only our core services, that we could not live without, being protected.

We primarily use this solution for disaster recovery. The initial sync was from Pure to Compellent, and DR with disparate storage was great. Once we identified our critical servers, vetted the Live and Test Failover, and got the necessary configuration at our DR site, we are now able to perform tests in a safe bubble.

Our primary use for this solution is DR Replication to a separate data centre. We use VMware at both sites. We're currently replicating around eighty VMs from our primary data centre in London to our secondary data centre in Beccles. Most of these are SQL servers with the VSS agent installed.

We primarily use this solution for Replication and Disaster Recovery.

We use this solution for disaster recovery.

Real-time replication for our Disaster Recovery site, which is currently hosted in another on-premise site but will shortly be moving to a Data Center in the Cloud. I have also used this solution to do point-in-time restores of Exchange mailbox items and to check updates from Microsoft.

Our primary use case for Zerto was to enable replication at our DR site for virtual appliances and automation of the failover - failback process. This also gets utilized for recovery at our DR site at different timestamps using the journal history. This solution is very light, with zero-touch deployment and very enhanced dashboards.

Cloud-based disaster recovery. However, do your homework on your provider. There are several options besides Azure and AWS that don't have their surprise charges. Be sure to check them out.

We were able to replace most of VMware SRM with this solution. It allows us to failover individual machines or application clusters with ease. The one thing that it does not do nicely is a full site failover. We have never needed that aspect though (only for testing).

Virtual server replication, as well as a level of backup, to our disaster recovery site.

Disaster Recovery and quick file recovery. We have used Zerto to recover from Ransomware three times. Between the attacks we have recovered over 2 million files. We have never paid a ransome. Our users were only affected just under two hours with the attacks, majority of the time is actually figuring out in the office which pc actually had the crypto locker program running.