Zerto

Zerto is one of our primary tools for Disaster Recovery. We tier all of our virtual servers via priority, all of which are prioritized accordingly in Zerto for our backup frequency needs in the event we need to invoke our DR site. The fast connections and replication allow for a large amount of replicated data.

High-value virtual servers are replicated from our primary production data center to our secondary fail-over data center. In effect, this represents the core of our disaster recovery and business continuity plans. Other, legacy backup and restore solutions were too slow to restore, and [the] speed of restore is among the most important features for our environment.

We mainly use Zerto as migration from our customer's on-premises data center (which could be their own or a competitor's data center), but in fewer cases as a DRaaS solution for our customers.

Its real-time replication and worry-free DR solution is the reason we decided to use and retain this product. This makes our annual/quarterly DR tests a breeze and gives peace of mind for any true DR event. I recommend Zerto to any friends/colleagues that could utilize it at their companies.

We use Zerto for disaster recovery and site replication between our primary and DR datacenters. We are able to recover our virtual servers in near real-time from a failure or disaster event. Zerto helps us meet audit and regulatory needs in the banking industry for backup/recovery of our datacenters.

We are using Zerto for disaster recovery across the entire organization. With it, we are able to minimize downtime by making sure that we are able to bring up downed systems in a timely manner. It helps us to manage the virtual machines in a way that maximizes uptime and limits downtime.

We use Zerto for real-time replication of our production Hyper V virtual environment. It is a crucial part of our disaster recovery protection.

We use Zerto to failover our VMware environment from one data center to another. It's being used for the VMs that need to be part of our disaster recovery plan. One of the problems [in my opinion] is the size of the journaling.

Zerto is being used to provide failover protection for our critical production servers. There have been some instances where we had to use it in the event of power outages at our main office. The affected servers were only unavailable for a short number of minutes, and most of that was waiting for them to update their DNS registrations. Zerto actually had the servers back up in seconds. We've also used it to migrate servers. At first, we were replicating the servers to a co-location, which was a secured data center where we had rented rack space. A few years ago, we decided to move our production servers to the colo and have the replicated instances at our main office (we only have the two locations) as the colo was a more stable environment. Zerto has built-in functionality for such migrations that makes the replicated instance the primary instance and then flips the protection. This made it quick and easy to do these migrations with very little downtime, even a server that was around 6TB in size (these locations were connected by only a 100 Mb private line at the time).

Our company has been using Zerto successfully for a little over 6 years. Zerto is used to backup VMs hosting our own developed secure customer application that is kept in a secure colocation and also to replicate the application programs and data to another DR site located at a diverse location for redundancy.

We use Zerto to replicate our On-prem VMware datacenter to Azure for DR purposes. We have also used it plenty to consolidate our data centers as well as migrate VMs from disjoined organizations during acquisitions.

Shortly after starting at my company the CTO called a meeting with all of IT and told us that the company had not passed DR testing in 3 years and that if we didn't pass this year, a finding would be posted with the SEC and stay there for years. IT had little understanding of a couple of our applications at the time, and this had caused recovery testing failures. After looking at the market we decided to try Zerto. This almost magically allowed us to pass ALL of our Critical systems that year, and we have not had a single failure in 6 years now. The CTO later told me that he didn't believe Zerto would do what was promised and that had it not, it would have been a resume-generating event for me. I can't say enough how amazing and easy to implement Zerto is compared to the other DR solutions I've attempted to use [throughout] my 22 years in IT. You will be shocked and appalled when you see how easy this makes your DR testing and system migrations!

Zerto has provided us with an RPO that no other product could provide. We use it for backup and DR for our most critical systems that require next to zero data loss. Zerto provides great built-in tools to test recovery without disrupting protection and every year we use it to test DR recovery.

Zerto is currently performing our DR processes across the corporation. Over 100 VM servers are being protected including multiple user file servers. The average RPO is less than 10 seconds across all machines running between California and datacenters located in the Midwest. The platform is so easy to use that the number of staff with the knowledge to run the DR process greatly increased.

My organization is currently using Zerto for our offsite DR location. We previously used CloudEndure which was purchased by AWS and lost its support expertise. Zerto is used for replicating critical servers to our cloud location for quick recovery.

We use Zerto for Disaster Recovery and it has been a wonderful solution. This includes on-prem from a data center on the West Coast to another on the East Coast, it also includes on-prem to Azure, and Azure to Azure replication. We use it across the organization to DR any x86 virtual systems.

We use Zerto primarily as a DR/Replication engine, to frequently snapshot and replicate VMWare VM's between sites. Zerto is also very useful in that it allows easy 'rollback', e.g. if something happens unexpectedly and we don't have an easy/current/fresh snapshot to roll back to, and/or on occasion, if we're not certain where/when a bust occurred, we can spin up several instances/iterations of past machine states for analysis.

Zerto is deployed across multiple data centers and allows for VM replication, migration, and recovery. Zerto is managed by our Systems Engineering team within the IT department. Zerto addresses our business continuity need for a low RPO and fast RTO, while being storage agnostic. Zerto has an easy-to-use interface that allows new team members to quickly learn the system and perform recovery options. We successfully perform disaster recovery testing and Zerto plays a large role in that success.

We utilize Zerto in our organization to replicate our VM workloads to an off-site location. Our typical RPO is usually less than 10 seconds.

We are using Zerto for our Disaster Recovery solution. It is being used across our entire international company. It ensures we'll be ready in case of a disaster.

Zerto allows us to replicate our VM's to a secondary data center also gave us a tool to replicate VMs that had previously been using NFS storage and were migrated to Fiber Channel storage.

Zerto is being used in my department as a disaster recovery tool. It allows us to easily recover data center assets in public cloud providers for our year disaster recovery test. It addresses business continuity for our business.

Zerto is used by our institution in order to synchronize servers across our sites for Disaster Recovery in near real-time. Primarily used by the Information Technology department the solution benefits the organization as a whole. This enables us to quickly failover and recover at an alternate site in the event we lose a primary data center.

Zerto is hands down one of the best solutions for DR in our organization. We use Zerto to easily replicate between multiple sites including a cloud data center. This allows us multiple redundant paths with our data while achieving great RPO/RTO in our organization.

We use Zerto for [the] replication of our VMs across the whole organization. Replication is made to a DR site 3 hours away with an RTO of 4 to 8 seconds. There is currently 48Tb being replicated. We hold normal copies for 3 days. We use Zerto's long-term retention and hold daily copies for 7 days, weekly copies for 1 month, monthly copies for 12 months, and yearly for 7 years. It fulfills our company [backup] policy for a financial institution.