It has been pretty straightforward. Initially, when we first got out of the gate with Zerto, we did have a third party to help us set it up, but we rebuilt it about a year later. We did that on our own, and it was surprisingly easy. It pretty much took a quick and free training course on their site. After that, I was up to enough speed to get it set up for us. It took four or five hours of training, and it was very easy. It took a day when I implemented it.

In terms of the implementation strategy, basically, we just wanted to get two sites set up, one on each data center. So, we set up two sites there with the appliances, and then we set up an individual VPG for each VM server. After that, we got them replicating. We set up our retention time and all that, and we were done.

For its deployment, there are two people at most. Usually, there is one. Zerto is easy enough to use, and one person can usually do whatever task is necessary to do in Zerto, whether it is setting up configuration or servers or restoring files. Usually, it is only a one-person job. If it is a more in-depth configuration, then you might need one more person for another pair of eyes to make sure everything looks right.

I was involved in the initial deployment. My job was to get Zerto up from scratch and make sure the configuration, network, storage, et cetera were up and running. It's fairly simple. There's a learning process, however, once you know it, it gets easier. 

I was involved in the initial setup. The initial setup is easy. Veeam had an easier setup, however, once we got Zerto going, it was easier to scale up and test. It's easier to manage in the long run.

The deployment had a bit of complexity. The problem we had was that the VRAs would not install and we had to turn off some security features. The ESXi server was not well documented. 

We set it up in multiple locations in one department.

It took us about three weeks to deploy the solution. 

The maintenance is simple. I handle the maintenance myself. 

I wasn't involved in the initial setup. After the deployment, there is a lot of maintenance. It throws out lots of errors, and we sometimes need to rebuild some of its components. Our backup guy is a little frustrated at times. 

I was not involved in the initial setup. This has been kind of thrown in my lap, and it has not been a nightmare at all.

It is a private cloud deployment. It is all VMware vSphere.

Its initial setup was straightforward. It was not as complicated as any other product. It took two to three weeks.

In terms of the implementation strategy, we wanted to reduce our synchronous synchronization. We wanted a better RTO, so we went to an asynchronous replication on private network infrastructure for faster syncing. There were a few technical aspects, but we took our time to lay out the network infrastructure.

In terms of maintenance, you have to patch it and upgrade it. We have a team of four for backup and storage.

I wasn't involved in the initial deployment, but we operate the solution with one team, our server team. Regarding maintenance, a minimal amount is required to keep up to date with patches etc. We occasionally run into an issue that necessitates upgrading to a newer version; for example, we were trying to move some vast data stores, and Zerto support said we needed to increase the timeout count. We keep fully up to date with security patches, and two staff members are responsible for maintenance. 

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

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

The implementation of the migration was very straightforward. The implementation of disaster recovery into Azure was a little more complex. In part, that was because of the way our company built our Azure subscription and the rules we have in place for installation and dividing things and networks within Azure. 

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

Zerto is user-friendly. When I set this up six or seven years ago, I knew nothing about Zerto. It was relatively straightforward to go from the vCenter SRM to the Zerto environment. It's intuitive, so I can log onto Zerto and figure it out without having to take a class or official training. I can log on and navigate through the screens. If I get stuck, Zerto support is always available.

There were two of us who set it up. I'm in the US, and the other guy is in the Philippines. He initiated it, and I finished it. We completed it in one day, but I don't remember how many hours it took. We did a quick check the following day to ensure everything was in line.

The initial setup is straightforward. The deployment took two months. We identified the core machines that we were previously replicating and gradually migrated applications one set at a time. An application could consist of two servers or even five servers. We can perform these migrations in waves.

For the deployment, we had two engineers, one support person, and one architect.

I wasn't involved in the initial setup.

We have two environments, one in our main office and the other in a data center. We have virtual protection groups that protect VMs in the main office and we are able to move them from failover to the data center as a DR strategy. That will change in the future when we move all assets that currently exist in our practice office into the data center as its native location. For now, it's office and data center, but in the future it will be data center and data center.

Our Zerto environment is VMware vSphere 7, and ESXi 7. It's mostly Windows VMs but there are some Linux VMs in there. It's a mixture of thick and thin-provisioned drives, all on VMFS data stores. Those are VMs that it protects and that it is able to move from one place to another.

As for maintenance, Zerto is really hands-off. It's just the usual software updates and that's about it. 

I believe the next step is that the recovery ZVMs (Zerto Virtual Managers) will turn into appliances, so they will be full Linux appliances. That will be great because we won't have to patch the Windows box underneath. Once that migration happens, it'll be even easier to manage. The only other thing that I have to do every once in a while is when we have another VM to protect. I edit the VPG and keep moving.

Setting up Zerto is straightforward, but I needed to call tech support a few times with some basic questions. I handled the setup by myself because I'm in charge of servers and VMware. It doesn't require much maintenance aside from updates. 

I purchased Zerto to simplify installation and configuration. I set aside a couple of weeks to install it, and I managed to do it in one afternoon. Managing the solution is pretty straightforward for someone with technical skills and experience. I find it simple to use, which is one of the reasons I like it. A lot of the products in the legal sector where I work are incredibly complicated and hard to use. This isn't one of them.

I couldn't believe how easy it was to install. Based on my previous experience with the EMC solution, I expected to be deploying it full-time for two weeks. I set up the prerequisites in advance, which included creating a couple of Windows VMs. We installed, set it up, and started replication within a couple of hours. I have a team of people, but I completed the installation myself.

Zerto is relatively low maintenance, which is another bonus. It just churns away. You need occasional upgrades and bug fixes. I spend an hour or two on maintenance every six months or so. Apart from that, the only other maintenance I do is testing every six months. 

To set up the initial environment, it took about an hour. This included setting up the appliance, making sure it's added to the domain, and things like that. But then, creating all of the VPGs will probably be another couple of hours.

The strategy was that we already had everything ready to go, which included our server list and all of the VPG names. If you have that, you could probably have everything completed in half a day, or a day, from a setup standpoint. Of course, this is depending on how large of an environment it is, but for us, we set up five or six environments and it took us approximately half a day.

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

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

We implemented it recently. There was the ease of implementation. It was easy and straightforward. 

In manufacturing, we have to make sure that everything is on-prem. The data has to be on-prem because all the tools write immediately to the servers. There are two types of manufacturing. For the type of manufacturing where your tools are constantly writing, cloud applications are not good. For example, when we scan wafers, there is a set of data, and when we go through another tool, there is another set of data. This has to be instantaneous. There is nothing called a cache or buffer on those tools. It has to be instantaneous. We cannot say that the cloud is down, and we lost the data. We cannot stop the tool because this is a manufacturing facility with 24-hour operations on 365 days. We cannot have any downtime where the full site has gone down because this site is used for central applications.

Our deployment is on a private cloud. We have compute, storage, and network that we replicate to. The initial deployment of Zerto was straightforward. It took less than 30 days to get it fully operational.

We used it in our test environment first and, once we validated that everything was functional, we included our production environment.

The maintenance involves keeping the versions up to date and there are agents that have to be updated as well.

There is a lot that goes into setting it up. So, the planning has to be done. We were pretty much able to have it up in a few hours, but it also depends on your use case and the complexity of your deployment. Like anything, there are a thousand ways to skin a cat. So, it depends upon how you want to have it set up. It depends on:

• How complex groundwork do you want to put in?
• How isolated do you want your test case to be?
• How isolated do you want different things to be set up?

There could be a little bit more complexity, but in general, it's pretty simple to get going. Obviously, there is a lot that goes into it, but the actual work of setting it up, once you have those decisions made, is pretty straightforward. It's pretty easy.

We definitely did a lot of planning, but we did the actual deployment or the actual configuration of it before we engaged with the professional services aspect of our deployment plan. When we bought the software, we had a project management plan and support from Zerto directly. We pretty much did all the setup ahead of time by ourselves. So, in our case, the setup was very simple and very easy.

It does require some maintenance. There are always service updates that are available, and occasionally, there will be little bumps in the road that require maybe reinstalling or updating something. In terms of general maintenance, as compared to other solutions, its maintenance is probably a little bit less than other solutions. Maintenance is still required, but it doesn't require an extreme amount of maintenance to keep things running smoothly.

The initial setup is pretty simple. We had it set up and replicating in about three hours. It's really quick to set up and works pretty simply.

The initial setup is straightforward. I had no prior knowledge of Zerto when we first deployed the solution, so I had a few conversations with engineers, but other than that, it was relatively easy to learn and I was able to understand the whole process. The deployment took less than two weeks to complete.

It was quite straightforward. You just install the software, point it to your vCenter instance, and then deploy your vRAs, which is done automatically. Updates have been the same, e.g., quite straightforward. The only challenge with updates is if you have multiple Zerto instances that are linked to each other. To be able to replicate to different sites, they can't be out more than a half a version. For instance, I am running version 8.5 on all my sites that are currently running Zerto, but I couldn't be running those if I was running 7.5 anywhere. That would have been too far out of appliance. That is more of a minor challenge than a problem. I don't consider that to be a shortcoming, but it is well-documented, easy to figure out, and also pretty straightforward.

The first site was also kind of a learning experience. That deployment took less than a day from, "Okay, let's start the download," to, "Look, it's doing something," and you need to stand up two sites to go from site A to site B. That took less than a day to get them up and functional in at least some capacity, protecting some machines and workloads.

Ease of use and deployment are fantastic. This is a solution that we started with a proof of concept. We threw it in a lab and said, "Hey, let's just see what it looks like." Next thing you know, we never even had to tear down the proof of concept. Once we started seeing it working we said, "This is definitely something that we want." All we really ended up doing was negotiating licenses, applying the license key, and we were off to the races.

Soup to nuts, it took us five hours to spin the whole solution up and to create our protection groups. It was very fast. That includes downloading the software, spinning the VM up, and protecting and backing up data.

We worked with one of their engineers through the proof of concept. Once we said, "Hey, this is going to work," we tested it on a few servers and then we became a paying customer. They worked with us to help us define what made sense for the 30 licenses that we bought and what machines to deploy it to. But it's really not a complicated tool to deploy. There wasn't a ton of architecting and solution-building around it. There was some, but it was a very simple solution to install.

The setup is straightforward. We deploy an appliance, and it's up very quickly. The initial installation is done in a day, but it takes time to configure things exactly the way you want them, get the VMs protected, write scripts, etc. 

We paid Zerto to help us get it installed, and we paid for the quick start. However, I did not read the contract closely. The person was very helpful, but unfortunately, we did not understand that we had a limited period of time. When we went to ask for support, they said sorry and asked us to buy more hours. That was our fault. It was not explained properly, but I cannot blame Zerto because we just did not read it all. It was a line item on the contract. It was not until they said that I only had six months that I pulled up the documentation, and it was a line item off to the side that said that we had six months total for the start-up, so we did not get the environment fully set up.

When we worked with the quick start engineer, he made some recommendations about setting up a test environment. He made some recommendations here or there, but it failed to launch. When we were working with the engineer, we had some of the same problems that we had after deployment. For example, in some cases, some test machines would never boot up. We then had to redo it and do some other VM. Even at the time when we were working with the engineer, we could not bring it back, and we never resolved the issue because the time expired. Some of that is on us. We get pulled in different directions, and I did not understand the limitation. 

The initial deployment was not very straightforward. We were able to deploy in a matter of hours. The foundational aspects of Zerto are pretty easy, however, managing VRAs and getting the replication going can be a bit more work.

For the initial deployment, we only needed a single administrator. 

The solution definitely requires maintenance, just to keep everything up to date. However, it's very intuitive and everything happens very quickly, based on how many VRAs you have. We have three administrators capable of managing Zerto as needed. 

We have three sites, either on private cloud or on-premises. They are all VMware-based. 

I was indirectly involved with the setup. It didn't take very long, it was like doing an upgrade. 

You just build the servers and the proxy up, install the VRA, and then one by one had them sync.

Seven months ago we had to do a complete resync which took about four to five days. It was straightforward. There is a lot of documentation on Zerto's support site. My advice would be to get the documentation off their site. Open a ticket for support at the same time. 

The initial setup is straightforward. We need a virtual machine, install it, push it through, and configure it to communicate with the host for deployment. I mean, it's a very straightforward process. Two people were involved in the deployment.

Deploying Zerto was straightforward, and I did the job by myself.

The initial setup was straightforward. We had someone from Zerto come down and set up the system in just a few hours. They provided us with knowledge transfer on how to create VPGs and other items and gave us an overview of the architecture of the whole solution so that we were confident in managing it ourselves. We have done all the updates ourselves.

The full deployment including the planning phase took a couple of weeks and required a few people.

The initial setup was pretty easy. You have to have connectivity between the sites that you're replicating, your production, and then your DR site or sites. Getting that connectivity is the biggest thing. Once that connectivity is there, it's fairly simple. You deploy Windows VM, put a small software package on it, and then pair the two. You do the same thing at the recovery site and once those sites are able to talk. In VMware, you install a VM on each ESX host that you need to replicate a VM on. Then you create a policy to do that replication. The replication policies work very well. Re-IP on failover if problematic.

The network connectivity takes the longest. It can take weeks, depending on what you have to do to connect the sites. It could be a couple of hours if you're just setting up a VPN. If you're putting in a circuit, it could take a very long time. That's the X factor with it, but assuming that's already there, within an hour you could be replicating data from one site to another.

ZCCs remain a major stumbling block. If the routing table has issues, the only fix is to delete all protection, redeploy the ZCC and rebuild. Again, avoid Zerto Cloud Manager until the product matures.

At first, the initial deployment was complex, but now it's relatively easy. For someone experienced, it is not a problem.

We have five data centers, and we started with one and deployed it in phases. Because there are lots of firewalls and access, we picked one data center and then built the next one.

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

While the initial deployment presented some challenges and took approximately two weeks to finalize, subsequent deployments have been significantly more streamlined.

I was involved in the initial setup, which was very straightforward. It took about a day to set up. Two people were involved in the deployment.

The only maintenance is the annual upgrade. It's pretty much set and forget.

The product was easy to deploy. At the time, the only thing that we wanted to improve was to have an appliance for the ZVM, instead of a Windows server. I understand an appliance is available now. This will be very beneficial in the future.

The deployment was straightforward. We basically went through the documentation and then had a planning meeting with Zerto. Once we understood all of the requirements we were able to deploy very quickly with really no issues at all. We deployed Zerto in less than a week.

The initial setup is very straightforward. I built a couple of virtual machines to run the manager on, deployed some VRAs, and then attached it to VMware and checked what I wanted to protect. We probably had it up and running in about an hour total. Then we tested protecting some machines, and we had some test boxes that we tested back and forth. It was a very easy setup. People are definitely sold about how easy it is to install and configure.

Initially, our deployment strategy was to protect a small subset of very important machines for an enterprise. And then once we saw how easy it was to implement, how easy it was to put things in there, and how easy it was to protect them, it went from a handful of machines to 350 or so. The initial intent was to protect a very small number. That went from that to a very large number very quickly. Zerto was able to handle it no problem. We actually had to end up buying more storage on the target side because we had not planned on doing that many machines from the initial implementation.

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

The documentation was confusing and, at times, incorrect.

The initial setup was not straightforward.

And maintenance is required for upgrades when there are newer releases, especially when it comes to Azure. There are newer releases that contain fixes and improvements and we do update the version of the Zerto appliance. They are running on Windows Servers, so we also have to patch the operating system. In Azure, there are a lot of SKUs with different pricing. Depending on the utilization of a VM, we sometimes make changes to the family types to save on costs at the VM level.

The initial deployment of Zerto was smooth and simplified by the support and consulting team's expertise and friendliness. We had a team of 4 people involved, including 2 technical architects, myself for project planning and implementation, and a Zerto support person for function control and time management. No maintenance is required on our end after the deployment.

The initial setup was easy.

Since we don't have to maintain all of the hardware and the second data center, one person can manage the entire Azure environment by themselves. As a result,  Zerto has helped us reduce staff. 

There was a learning curve, but the setup was pretty easy. For our deployment model, we have one VPG per server, so it's one-to-one.

For maintenance, there are quarterly patches, and we set up testing of our VPGs every six months.

I designed it all and already knew what I wanted to accomplish and what the product could do. Once we knew what direction we were going in and where the critical applications aligned, it was just a point of picking things up and putting them into placeholders already in the required image I designed for our purposes. It was pretty easy. It might take a little longer without prior experience and an idea of what I want to accomplish. It would still be pretty easy as Zerto provides excellent documentation. This is one of the most straightforward designs out there. End-to-end, with testing and approvals at each step, I think it took two and a half weeks.

The initial deployment was straightforward for the admin that deployed it. It was not complicated. That person left and then another person came in who didn't know anything about this product and he picked it up fairly easily and he's able to manage it with ease.

He's a VMware administrator and he also maintains Zerto.

The deployment was done within a day.  

We don't have plans to increase usage because we are at the point where we're closing out. We're migrating some of our data centers and right now I know it's going to continue utilizing what we have. We haven't even hit the capacity of what we've got right now. Because I think the license we have is around 75 servers. We haven't even hit that. The only thing that's stopping us from right now is just that we need to increase the storage at the remote location to handle additional workloads. We have around 14 servers. 

The initial setup is complex. It may be partly due to our understanding of Azure, which I would not put at an expert level. I would rate our skill at Azure between a neophyte and the mid-range in terms of understanding the connectivity points with it. In addition to that, we had to deal with a cloud service provider.

Essentially, we had to change things around, and I would not say that it was easy. It was difficult and definitely needed a third party to help get the product stood up.

Our deployment was completed within a couple of months of ending the PoC. Our PoC lasted between 30 and 60 days, over which time we were able to validate it. It took another 60 days to get it up and running after we got the green light to purchase it.

We're a multisite location, so the implementation strategy started with getting it baked at our corporate location and validating it. Then, build out an Azure footprint globally and then extend the product into those environments. 

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

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

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

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

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

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

I did not do the implementation, but my team deployed it. Because I have used it before, my guess is that it is not complicated to deploy.

The feedback I received from our team was that the majority of the deployment went smoothly, but there were some technical aspects that were not covered in the deployment documentation, which they had to figure out.

The deployment required two people at times, but the majority of it was completed by one person.

We used one internal engineer to perform the initial setup on two data centers in two days. In general, this involved installing two virtual machines with Zerto Virtual Manager on each data center, creating the corresponding network access rules, and then deploying Zerto replication agents to all virtualization hosts. The last activity was automated, so it took about one hour to deploy Zerto for all virtualization hosts. The replication took one week.

I was not involved in the initial setup or deployment.

From the team, the deployment was very straightforward. The proof of concept that we ran took a little over a week. They were able to stand it up from scratch, deploy, and run several tests of varying complexities. Everything went smoothly. We put a contract and agreement together in record timing for our company.

If you give me two Windows Servers, it will take less than 24 hours to replicate everything and you can already run a DR test. It's really amazing.

Initially with Zerto, every time there was an upgrade, I practically had to do everything from scratch. I had to recreate the groups and everything else. It didn't work well and I told them, "This is a big issue." In version 5, I believe, they resolved this and I could pick up my environment and restore it. When I upgraded my Zerto from version 8 to 9, it worked great and automatically. After half an hour I was running a brand new environment.

The initial setup was fairly straightforward, deploying the VRAs to the VMware infrastructure and stuff like that was point, click, and let it run it. It was fairly quick. The VRAs took a couple of minutes each, so that wasn't bad at all. Setting up the VPGs is quite simple. There is a little bit of confusion where you can set your default for the journaling and stuff like that and then modify individual VMs after the fact. If you want different journal sizes for different VMs in the same VPG, there are a couple of different spots you can tweak. The setup and requirements of the LTR were a little bit confusing.

We purchased six or eight hours of implementation time but that was over multiple calls. We stood up some of the infrastructures, got some VPGs together, and then they left it to me to set up some other VPGs. Then we did a touch base to see what questions I had and things like that. We had six or eight hours purchased but it was spread over multiple engagements.

For the most part, only I worked on the deployment. Our network engineer was involved briefly just to verify connectivity via the VLANs and firewalls. Once we had established a connection, he was pretty much out of it.

I'm the only one who uses it strictly for our district backups. We're a small college. Our IT programs, HR, or business services, don't have their own separate entities. It's all covered under the primary IT department.

Back in 2016, we conducted a 30-day POC with Zerto and that was enough time to fully implement the solution and even utilize it. We were really impressed that we could actually use Zerto from start to test within a 30-day timeframe.

We found the setup and deployment process to be very simple and not complex at all. We installed Zerto on-premises with just regular employees. It was a team of two engineers and a database administrator and that was it. After a little bit of research on the prerequisites we literally ran the installation setup. It was a breeze and there were really no custom tweaks or anything that had to be done post-setup.

The solution is very user intuitive, from the initial setup of the application and installation all the way to actually getting data in there by creating virtual protection groups and populating VMs.

I work on the cloud management side, so it was already deployed. I wasn't involved in deploying the cloud portion. However, I installed all of the virtual management for customers and set up the environment for them. That part of it was easy. It was a click-through thing. Most of the time, we'll guide the customer through the process, so they can see it as well. We show them the step-by-step process of performing the updates. 

The initial setup was straightforward; it wasn't complex at all. It was very simple to install and set up the replication, more so than other solutions. 

The replication functionality is very user-friendly, so that was the easiest part. At the same time, the security aspect of the solution, integrating with our firewalls etc., was the most challenging element of the deployment.

The initial setup was very straightforward. We had some training with some Zerto engineers on how to set up the recovery groups and other things, but once that was set up, we made several changes later on as we played with it. Overall, it was very straightforward to configure and I think that we only had an hour of training.

The deployment took us a couple of weeks to get everything figured out, although it wasn't necessarily Zerto that was the hold-up. We only had a certain number of licenses, perhaps 15 in total. We spent time trying to determine which were our critical workloads, and there was some internal debate about it. From the Zerto perspective, there weren't a lot of issues.

It didn't take a lot of time, just a couple of weeks to get us up and going. We were actually up and technically running within that same day, but to truly boot it and get it where it needed to be, it took a couple of weeks. It was a new technology to us at the time, so it took a while to get up to speed with it.

In terms of our implementation strategy, we just tried to identify the critical workloads, find the ones that really needed to be protected and start to make those recovery groups. Then, we organized them in such a way that things worked properly. For example, the components of our ERP system do have to come up in a certain order. Finding all of that stuff out and fine-tuning the process was part of our strategy. Then, we slowly started moving those workloads across. We broke it down into groups and we did those groups one at a time until the implementation was complete.

Not only was the initial setup simple, but upgrades actually work and backward compatibility during the upgrades work. I've been doing IT for 25 years and it's one of the few solutions that I have come across where backups work, not only doing the actual backup, but they're compatible with what you have in place. Upgrades are very impressive and very seamless.

I started with working with Zerto during the 4.5 version. Right after we deployed that we went to 5.0. The length of time really varies depending upon your engineering platform process. I did the PoC and all the documentation, and then I did the deployment into production. I spent a few days on the PoC because I needed to know what its performance impact was going to be on the host, on the VMs. Then I had to see what the replication impact was going to be as well. 

And documentation took me a couple of weeks. Because I've been in disasters, when I do documentation I do it so that I can hand it to anybody, literally, including—and I've done it—to the janitor. I've handed the documentation to the janitor and I've had them sit down and do a recovery. I'm picky on documentation. 

The actual sit-down at the keyboard to do the deployment, after everything was in place, including getting a service account, getting the VM deployed, etc., was quick. In one day we had it up and running.

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.

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

Four people are required for the deployment.

I carried out the initial setup with support from Zerto, which was very straightforward.

The only requirement for maintenance is monitoring the solution and updating versions.

I was not involved in the initial setup but have heard feedback that those involved loved the simplicity of it.

The setup is very easily done because you tie it into your VMware vCenter. When you put in your credentials, it will recognize everything on your networks. It will recognize storage, whether it be cloud-based or as in our case, at another data center. Once you have those defined, it's just a matter of creating groups that you want to recover, server-wise.

The reason that you would want to do it in groups is that you can set it up in the automation such that it will bring up groups in a certain order. That way, you have a network where the domain controllers come up in the first group, and you can automate stuff from there.

Seven years ago, when I first started to use it, I found it more difficult. I wouldn't say that it was complex but they have certainly made improvements over the years. Where it stands now, if I had to set it up from scratch, I could probably do it in about an hour. Of course, that is because of the way I know the application but in terms of how they have changed the setup, it is certainly more user-friendly than it was compared to where it started.

I remember running into a couple of issues during the deployment, and I contacted their support. They were fantastic and helped me get through it. They made sure that all of my questions were answered, and that it was up and running how we intended it to be used. A lot of it probably had to do with me being a novice at that point, in terms of using the application.

It was a multi-site deployment, with a production site and a DR site, with dedicated storage for each. We have changed the storage that it uses over the years and if I had to do it again, I would use another vendor for storage. A lot of the issues that we ran into were related to the initial storage that we used, as opposed to Zerto issues, even though it was Zerto support that helped me fix them. 

Overall, the deployment was fairly easy. Not because everything went great, but because of the combination of the application being pretty well-written and the support. I would rate the deployment an eight out of ten.

It was quite easy to implement and start the execution. There were no problems. It took us about three months to implement it in production.

I did not do the initial setup of the solution, but the upgrade from version 8.5 to 9.5 was very simple.

Our engineering team members, three systems engineers, are the main users of Zerto. We don't have segregated roles. I'm the point person for Zerto, and the other guys are backups for managing it and doing recoveries. Maintenance only requires one person.

It was actually fairly easy to set up the solution. Installing it, creating the VPGs, and adding the VMs to it was fairly straightforward.

For us, this solution is not difficult to deploy. For a complicated environment then you have to do careful planning but otherwise, it is not hard to deploy.

Typically, if everything is well in place, the deployment will take between one and three hours. In cases where the customer's environment is very complex then I might need a little bit more time. I would estimate that it would take six-plus hours, after careful planning and ensuring that all of the resources are in place.

The installation takes less than 30 minutes; however, the customer environment increases the time because we have to do things like open ports on the firewall. We tell them about these preparations in advance but we always end up doing some of the work ourselves. In situations where the firewall has already been properly configured, I can normally complete the installation and configuration in one hour.

I have two customers that use the cloud-based deployment on Azure but the majority of them use it in a local, on-premises environment.

The initial setup was very straightforward. We had everything running in half an hour. It got deployed with two virtual machines (ZVMs): One got deployed in Massachusetts and another in our Arizona location. From there, we deploy appliances to each one of the hosts that's inside of the clusters that we are managing for our disaster recovery solution.

Within 30 minutes, we had it deployed to our entire production cluster and the hosts in here. After that, we just started creating jobs, which took quite awhile to do because we have a lot of large servers. However, that's not the worry of the Zerto application, but the size of the VMs we have in production. 

For our implementation strategy, we just mimicked what we had in place for our SRM environment. Our 58 machines are spread across different clusters: some in our DMZ, some in our prod and some in our WebSphere clusters. After that, we ran two tests to ensure that we were able to fail over to our Arizona location then fail back without any changes or modifications to the VMs. Once we did that, we started rolling out to each of the clusters, one Virtual Protection Group (VPG) at a time. I think we now have 23 VPGs total.

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

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

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

The deployment of the product is straightforward. We have, for example, more than 100 VMware ESX-site servers and there are two agents in terms of virtual machines that get deployed on all of them.

To deploy the solution, it only takes 30 minutes. You only need one or two resources to manage the implementation. The maintenance is minimal. Once it's set up, it's fine. 

Our experience with the initial setup was easy. It took 15 minutes. 

The on-prem deployment is super easy and works well. Migrating from on-prem to the cloud involves a lot more steps and things you have to configure so that it can communicate into the cloud and build everything that it needs to. That takes more time. It probably requires twice as much time to deploy on the cloud. 

The initial setup was straightforward. I assisted in the deployment, and a total of four people were required. The deployment took one week due to the necessary networking changes that had to be made.

The initial setup is straightforward, especially if those setting it up understand the company's infrastructure. The problems are not directly related to Zerto itself. They're always related to how the infrastructure is set up or how the network itself is segmented and having certain people that have control or access and others that don't.

The initial setup was straightforward, but I had a team, probably from Zerto and not the consultant, that helped us with the installation. So, I had somebody right there holding my hand, and it was very easy to do.

I was not part of the initial installation, but I've heard that some of the initial pieces are straightforward. Where it gets complex is that I don't know if it was set up according to their best practices.

The initial setup was straightforward. You could deploy the VRAs pretty simplistically as long as you set an IP via the UI, so that was pretty easy. We were up and running in a day.

Our implementation strategy was rushed. We were doing a data center move and we just wanted an extra copy of the data. So this was a stop-gap solution that we stuck with.

Zerto itself was straightforward to set up. There was good documentation available and we utilized some of their engineering services to help set up as well. For the size of the products and the complexity that it can do, the actual setup and operations over this are quite easy. It took a couple of days, which included getting everything in Azure set up properly.

The implementation strategy that we did was to create the on-premise environment for a dedicated network, virtual machines, and the installation. Then Azure would become our disaster recovery site in the event that we needed it if we had a disaster on-premise, we could failover all of our services and servers that we needed to in Azure. Then our client computers would connect to them while in the Cloud while be prepared for recovery on-premise.

The deployment of Zerto took a few weeks.

It was deployed before I joined the company.

Our deployment is both on-prem and, for replication, in Azure. The initial setup was straightforward. There was a learning curve in transitioning from our old environment, but it didn't take very long to learn.

It took us about a month to fully deploy.

Outside of updates, it doesn't require any maintenance.

Aside from working with the network team to get all the networking pieces configured, it was pretty straightforward. Installing the agents on the servers and doing the initial replication took the longest time because we have close to a terabyte of data that has to be replicated from one data center to another, but other than that, it was pretty seamless.

I haven't found it to be hard. When you add a new host, you just go to set up and add a new host, then it builds a vRA. It is pretty easy to manage alerts. It will tell you exactly what is wrong, e.g., this doesn't have enough scratch disk, so you need to go update that. Or, this host is offline, e.g., you forgot to evacuate it, so then you need to take it out of Zerto. So, it will alert you to that stuff.

It was pretty straightforward. We had it fully installed and started implementing it within the first couple of hours of the process. We worked with the local rep for about an hour or two, and by then, we had the process down. After that, it was pretty straightforward, and we just replicated that for additional protection groups.

In terms of the implementation strategy, we knew what we needed. We wanted to get out in the cloud. We focused on Azure to start with and then came back and looked at AWS after the fact for a couple of use cases where Azure wasn't the best place for some big data sets.

For its day-to-day maintenance or administration, there is just me. We do have desktop admins that can get into it as well if they need to be, but generally, I take care of it all for them. They just holler out if they have a problem or a question about something, and I can take care of it for them.

The initial setup is very simple.

Our implementation strategy involved setting it up for our two data centers. We have a primary and secondary data center, and Zerto keeps track of all of the VMs at the primary site and replicates them to the other site.

In the future, we plan on looking into the on-premises to cloud replication. On-premises to Azure direct is on our roadmap.

The initial setup of Zerto is quite simple. You build a SQL instance. You build a Windows VM and install the ZVM on it. You integrate it with vCenter and then, from the ZVM, you make sure your firewall ports are open and you push the VRAs down.

Deployment takes a couple of hours, for a relatively big environment. It would typically require 30 minutes of DBA time, an hour or two of Windows engineering time, and another person from VMware for another hour.

It doesn't require any staff for day-to-day maintenance. It's used by our operations team, which is close to 100 people; those are people who have access to it.

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

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

We have Zerto on an HP machine. 

I was not involved in the deployment of the solution. 

Maintenance is necessary, and we have two people handling maintenance tasks. 

I did not initially set up the solution; I inherited it. However, over the past eight years, we have gone through a number of upgrades, which for the most part have gone seamlessly. We did have a few issues in the past that support was able to fix in a timely fashion. 

The initial setup is very straightforward. The wizard that you run through is just very straightforward. If it is a DR-as-a-service customer on my end, then I am just deploying it as sort of a cloud connect, which is very easy.

I wasn't involved in the initial deployment. I have been involved with subsequent deployments, which were straightforward. Originally, I babysat it, then I owned it in tandem with another engineer who was actually the owner of it. I helped with the scripting part since I had more scripting knowledge. 

Subsequent deployments take 15 minutes, which is not long. With ZVM installers, they ask you a question, then you put it in. If you don't have the answers, then you go get them. You have no business deploying Zerto if you don't have those answers to begin with. ZCM is just as easy.

Setting up Zerto is straightforward. The documentation was great, and it is intuitive. Integration with VMware is seamless. It's good at running the scripts needed to run in order to work with VMware. We have a 90 percent virtualized environment. 

I have had to redeploy it a few times with data center changes and such. We went from your typical data center to Cisco UCS Blades to VxRack, a VMware Dell EMC product. With that, I had to deploy it from scratch.

It was pretty straightforward. There is plenty of very easy to follow documentation when it comes to implementing it. There is also a lot of training provided so you can understand it before you implement it. Those two things make it pretty easy.

Just to stand it up and get everything going, that took an hour or two. The overall implementation was over the course of three days, because our core is heavily utilized.

We had a ZVM Virtual Manager on our production side and another on our DR site. Most of our data is replicated from production to DR. We do have some that are in the DR replicating back, but not a lot. Our main concern was between both sites, because we don't have a very large pipe. Even though Zerto's compression is pretty good, we didn't want to send that data all back over. Our main priority, when we set it up again, was that we were able to retain a lot of the data at our DR location and remap it by using preseeded disks, which was huge.

The initial setup was straightforward, although we did have some problems. For example, there were instances where we could not integrate with our internal tools and we were not able to solve the problem. We looked at the FAQ and reached out to customer support to ask what the ideal solution would be.

Overall, it took between six and nine months to deploy.

The initial setup is straightforward. We had it up and running in no time at all, and it wasn't something that took us weeks or months to implement. The install was done in less than a day and we were already starting to create VPGs immediately.

We started off as a trial running a PoC. We had a trial license mainly because, being in the healthcare industry, we have some unique applications. The other options for disaster recovery on those were going to be pretty pricey, and then, that would be a solution just for that one particular application. At that point, we were more interested in having the backups.

We don't like having five different backup utilities and we were hoping to have just one product that would handle all of our DR business continuance needs. That seemed to be Zerto when we looked at it, so we wanted to do a proof of concept on one main application, Meditech. It is our primary healthcare information system that everybody uses. It wasn't officially a supported DR business continuity methodology for it, but we did put it through the wringer a bit during the PoC phase to make sure it worked before we were really committed.

A lot of the other applications are straightforward, so we weren't as concerned with what we were going to do after the fact. But Medtech was one of the big driving ones that needed to be tested out before we committed to purchasing it. We did make calls to other hospitals who were Meditech customers as well, that were also using Zerto, to get a better comfort level based on their experiences.

When I deployed the solution, it took certainly less than a day to get it up and running. The upgrade process has been fairly seamless and painless, in the past, as we have gone from one version to the next. That includes some of the features they've enhanced, where it automatically updates the replication appliances as well as the management pieces.

We have two data centers and they're both Active-Active for one another. Our deployment strategy for Zerto was to stand up a site server at each one, pair them together, and then start identifying the first workloads to add into Zerto protection. We started with our SQL environment. 

I was the only one involved in the deployment. If I had questions I would ask my account team. My sales engineer and the account rep are both very knowledgeable. But I actually didn't need to open a support ticket as part of the deployment. It was very easy and straightforward.

About five of us utilize Zerto. I am the infrastructure engineer, focusing on the compute side of the house. We've got a storage engineer. My manager is an applications delivery manager who uses it. We've got another senior network engineer who focuses more on the runbook side of things, and he uses it. And my backup, who is our Citrix guy, is starting to use it.

Zerto doesn't really require any particular care and feeding. Whenever a new version comes out that has features sets, I'll decide when I'm going to update it and do that myself. It doesn't really even require a support call. It's pretty straightforward. For each management appliance, updates have taken 10 to 15 minutes, in the past. And it's just a couple of minutes for each replication appliance.

It took us about two months to deploy the solution, but that was because we're a very conservative company. We purposely went extremely slowly. If we had wanted to go faster, it could have been done probably in a week or two, to get all 6,000 VMs under protection.

The implementation was really straightforward and easy. We worked with one of their support engineers and we got it up and running really quickly. The deployment took around one hour. 

We didn't really have an implementation strategy. It was about getting the server manager and server up and then walk through the installation steps. We followed their guidelines.

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

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

Zerto is intuitive. We could set everything up in the environment within a day and a half and start migrating on the third day.

The initial deployment was easy. We deployed VRAs to the host from the manager. It works very well. The amount of VRAs you have to deploy and the amount of time it takes is minimal. It took us about an hour. 

The initial setup is straightforward. It is streamlined with simple instructions. Anybody can do it as long as they understand their infrastructure.

The initial setup was very simple, very straightforward. Zerto got online with us when we did the initial configuration and gave us easy guidelines to follow. We were able to have it up and running in less than an hour.

We took what Zerto recommended in their deployment guide. We knew the areas we wanted to cover and what we wanted to improve upon. Based on those things, we were able to come up with a nice, easy plan to follow to get it implemented.

When there's an issue, just one person is involved, but generally speaking, there's not much maintenance on Zerto. Once you get it up and running, it does what it's supposed to do.

I have been involved in some of the Zerto setups and from what I have seen, they go very well. It seems that it is pretty easy to perform the initial setup.

It takes about an hour per site, or per server to upgrade it. 

The initial setup of Zerto was very straight forward. The rest of the configuration will be as complex as your environment's DR needs and application stacks are.

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

I was not involved in its deployment.

The whole process was extremely straightforward. I did a little bit of learning in the Zerto University on how to do a quick deployment. There are not a lot of steps to the quick deployment. After just a few steps we were up and going, almost instantly.

After the installation, it prompts you to log in, and as soon as you log in, it starts telling you what to do. It says, "You need to deploy your virtual replication appliances." And then it says, "Great. Now that you've done that, you're ready to create VPGs." It was almost like the application was literally telling me what to do next.

I was involved on the VMware side, getting things ready for Zerto. My counterpart was the one who actually implemented Zerto. I believe the Zerto implementation was pretty straightforward. The only complexity involved was learning how it worked.

I was amazed at the ease of the installation and how quickly it went. I actually did the install with the support engineer looking over my shoulder, and it was done in 30 minutes.

I did the initial installation, and it was very straightforward. I've never had a solution that is this intensive and yet this easy to deploy. It took a few hours to deploy.

And in terms of working with Zerto on a day-to-day basis, it's just me.

I was involved in the initial setup from the start. It is very complex as far as requirements go and what needs to be set out for Zerto. Once you set it up, it is fine. It works.

Back and forth, our deployment took a couple of weeks. It was deployed on different sites. We needed to set up, provision, have networks open, firewalls, and allocate dedicated storage. We also needed to install it, build it, deploy the agent on the host, and configure it.

The initial setup was straightforward.

The initial setup was pretty straightforward. You set up a ZVM here and there and tell it the direction you want it to replicate in to. You can create an EPG to the journal that goes attached.

Because we were setting it up in the middle of things, it took around one month. 

We did have a strategy of how to put those servers here, build servers there, and IP addresses we were going to assign to it. We did have some sense of where we were going to put things.

The initial setup was not hard at all. We deployed a VM and had our team open the ports and we were all set. 

It only takes about an hour or two if you have the proper people helping you with the networking. 

It was a little rough, but it was not terrible. When we were setting this up, I was working with several machines that were 30 or 40 terabytes in size. Moving that data out to that other location was a long, slow, and ongoing process. There were several times when we had to reach out to their support to try and figure out what was going on. We had to make some adjustments to how they were configured, but that was the biggest challenge we had with that the whole time.

It is slow initially, but once you get it all up there, it is not so bad. It took days to get that data moved. Once it got up or synced, it was down to seven or eight minutes, but it took days to get everything up there to begin with. It took about a week from start to finish to have it fully deployed.

The initial setup was really easy and fast. We had it installed in less than an hour, maybe even half an hour. After that, we created our groups. The time for that would depend on how many DMs you have, but it's easy and intuitive.

The initial deployment is very straightforward. You just install the appliance, make sure that all the ports are working fine, test the connection, and you're done. If you have any problems, technical support is always there to help.

I wasn't involved in the initial setup. We have an individual who is our infrastructure expert. He took it upon himself to try it out. He told us what he found out when he did that trial and we started playing with it a little bit more and saw how easy it was to use.

The setup for Zerto was very simple.

The initial setup is pretty easy to do. I was not with this company when they implemented it, so I don't know how long it took them to deploy. However, in my previous company, we initially installed and set it up in a day. We didn't have much trouble.

At first, we only had a couple of small test instances. We started adding things that we needed, over time.

The initial setup was pretty straightforward. It took a little while to make sure we had everything connected right, and that it was going to the right place, but it's no more difficult than any other setup for something like this. I didn't find it difficult at all.

If you don't include seeding and you only include the setup and deployment, it only took us a day or two of planning and then another day of actually implementing it. The seeding took a while, but that's to be expected.

In terms of our implementation strategy, we were using a different product back then, which wasn't as up to date and live. We were just backing up at night, so we had a nightly snapshot that was being transferred to our DR site. Our strategy with Zerto was to get us to more of a real-time backup solution at the DR site and make sure everything was good. That was the entire purpose of going with Zerto.

I have implemented Zerto from scratch on the infrastructure. In most cases, I am not configuring the network. There are other engineers to do that, but if the network is working and I have all the information I need, then installing Zerto Virtual Manager and Virtual Replication Appliances (VRAs) is very smooth and simple.

If everything is configured as it is supposed to be, it does not take long. It also depends on whether you need to deploy a Windows VM or appliance. If you need to deploy an appliance, it will take a little more time. Deploying a VM and installing Zerto Virtual Manager and VRAs takes a couple of hours.

Zerto is very straightforward to set up. The only drawback is having to have the Window server.

After the Windows server is deployed, it takes less than an hour to deploy the solution.

The initial setup process is simple. You get the executable, you stand up a VM, you install it on a VM and open up firewalls, and connect the ZVM to the ZVRA data sites. It's fairly straightforward.

You can deploy Zerto in under two hours, as long as the firewall is in place. When the firewall is in place, everything runs smoothly. Otherwise, it takes a while.

The initial setup was fairly straightforward. Everything made sense, and after a couple of days, we were up and running.

It didn't seem that difficult to set up. 

It took a couple of days, but that didn't include setting up the SAN and the secondary sites and all of the infrastructure around having it work directly. But just the Zerto solution itself did not take very long at all to set up.

Everything that we needed to do to facilitate the use of the solution was more involved and took a month or so. At the time, we also deployed a Veeam solution to do the long-term storage, and that was wrapped up in the same project, so it's hard to give an exact amount of time for the deployment. 

The initial setup was very straightforward and easy.

The installation was simple. There are lots of guides and information. There are YouTube videos. They had training classes that were free that you can go to and they have a little lab environment. Even without the assistance offered, the way you install it is very straightforward and very simple. Really anybody can run the installer and have an idea of what they're doing right out of the gate without really any training.

Deployment took around a day.

We did have a specific deployment plan and we were able to execute that in about a day. Getting all the sites set up and then the VMs replicated was fast.

We have five people on staff that can handle deployment and maintenance.

The initial setup was straightforward, though it could be more straightforward. Now, you just install the software on a Windows system. It would be nice if they had an appliance that autodeployed in VMware. That would make it simple. But if you can install Office or any kind of application on Windows, you can do this. It is super easy to set up with minimal front-end learning required. 

The deployment takes about an hour for an experienced person. If it is your first time, then it will take a couple hours.

You need to know your use case for an instance where you need something to be backed up. Once that need is identified, you need to know where it is and where you want it to go. Once you already have those questions answered, the implementation is simple. Through the installation progress, you just plug in those values of where is it, what is it, and where do you want it to go, then you're done.

Our IT team handled the deployment, but I don't think it was complicated. 

Zerto is easy to set up. Once you've deployed the appliance and connected it to a  vCenter, your VMs are protected pretty quickly.

I was involved in the initial deployment. 

The process is not too bad. The process was pretty straightforward. 

Currently, we are still on version 9. We have deployed that. Overall, it is very easy once you get the Windows Server. I am excited about the new version 10 coming out that takes away the Windows server requirement.

We had to work on it for about a week to get it running the way we wanted. It took so long because of the fine-tuning. We could have set it up within three hours or something just as a test to see at work, but not necessarily do everything we wanted to do.

The time it took to sync the data up took a little bit longer.

The setup was easy and demo replication was simple too. The initial process started by us building out the VMs of the virtual machines, as per their requirements. We deployed the manager, based on all the log information of the vCenter. You then select the data storage and it installs the VRA out on your environment. Once that is done, you put together the virtual protection groups and you build out your replication site, it is very easy.

The initial setup was very straightforward, very easy. We set up a virtual machine at both locations, which are both Windows, and then installed the Zerto software and gave it credentials to connect into our environments. It did the rest for us. Once it was initially set up, we just had to figure out which virtual machines we wanted to protect and which way: did we want it to copy from our data center over to the co-lo, or back to our data center from the co-lo. They walk you through step-by-step with wizards. It's incredibly easy to set up.

Because there's a lot of data initially to sync over, the deployment took about a week in total. The initial setup only took a couple of hours, but then you have to wait for all that replication to sync.

We didn't have an implementation strategy for Zerto. Because we didn't have a previous solution, we didn't have any migration to do. We just paid for the license, got it installed, and rolled with it.

The initial setup was simple. We were able to deploy one FPE every two weeks. One person was involved in the deployment.

The initial deployment took a few weeks.

The initial setup was straightforward. You open the firewall, install it, connect to vCenter, and then do all the steps to install the software.

The initial setup was pretty straightforward for the site-to-site recovery or for setting up the VPGs. If you just want to do basic replication and you don't have a lot of special situations to account for, you could have it up and running very quickly.

For special situations, there are options within advanced settings. You don't have to dig too far for them, but they're not quite as straightforward.

There is a slight learning curve when setting up, but nothing overwhelming for a good administrator.

This initial setup was pretty straightforward with the exception of needing a VM on every single host.

Setup is really easy and quick. Make sure that you have your desired networking for replication and testing in place.

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

It is easy to maintain.

The initial deployment was pretty simple. The implementation took less than half a day. It has been awhile, but it was very seamless, easy, and did not take very long. We were up and running pretty quickly.

The initial setup was very straightforward. The solution is easy to implement. You implement it and it starts working out-of-the-box. There is not much configuration required. It takes a couple of hours to have it up and running, protecting you.

We had a very experienced consultant set us up.

The initial setup was very straightforward and easy. We were able to start replication within minutes of the initial setup.

The setup was very straightforward. Anyone can do it!

It was straightforward and easy. I was able to install it myself without any help from Zerto.

I was not present for the initial setup, but I deployed Zerto Virtual Manager. It was pretty straightforward. You walk through the wizard, and if you have all your networks on the server and everything is done correctly, you can start to build VPGs right away.

If you have all of the network and firewall rules already in place, you could probably stand up a new one in 45 minutes.

Zerto was already there when I stepped into the picture. I helped initiate some of the disaster recovery processes. Based on what I saw from the outside, it was easy because it was ready for that situation quickly. It was ready in a business day or less, aside from the replication aspect or the data sync from when you first set up the jobs. But the basic setup to get things going was ready within less than a business day.

I was involved in setting up the proof of concept, and I found that the initial setup was okay.

Once the PoC was complete, we went into small volume testing and then started using it after that. The deployment only took us a couple of hours.

It is very easy to set-up this solution.

The Zerto setup was straightforward. It is one of the simplest tools I have ever deployed to protect virtual workloads. It works hand in hand with VMware features such as DRS/HA, so there is no issue when your workload moves around.

The initial setup is straightforward and pretty easy to complete. It takes about an hour to deploy. During the process, you set up the Zerto server to see the whole environment. You then install VRAs on all of the hosts. In general, the management server is pretty user-friendly.

The implementation strategy changes depending on the customer. We did have a few customers that required a more extensive setup because one had an IPsec connection, and a few of them were using point-to-point connections. That's the only strategy. But with Zerto, they need to decide which VMs they want to replicate, and then we create it based on that. First, we will want to replicate the DC, the domain controllers, and then we will want the infrastructure servers, and then the database servers, and the last one is the application.

During setup, one person from our company normally works with one person from our customer's side. Only a single person is required for maintenance.

It was initially set up by a third party. But since then, I've had to re-set it up and it was pretty easy. It wasn't very complicated. It was quick. There were instructions that we followed pretty closely and there were no issues, so it was straightforward. There were a handful of steps, but nothing overly complex. The deployment took around 30 to 45 minutes. 

The initial setup of this solution is very straightforward. The installation and configuration are incredibly easy for someone who is reasonably familiar with IT Management.

The initial setup was straightforward. How the VPGs are configured and adding the VMs is simple and pretty intuitive. It took under an hour to set up. 

The initial setup was very easy. I followed the documentation to set it up myself. The person completing the setup needs to understand the storage layer and the network layer for the backup. Without this understanding, It may be extremely confusing.

When you apply Zerto to your environment, you need to understand your networking settings, storage settings, and your capacity planning. Setting up Zerto took us 15 minutes. 

The initial setup is straightforward. I just followed the documentation online and it was set up in a day.

It's very straightforward to set up. You just install the software and point it at your vCenter. There are not really a lot of overly complex parts to the installation. It installs relatively easily and quickly.

The initial setup of the product was very complex. We were using a SQL Server cluster with a Nimble array, so it was very complicated to get everything set up correctly so it would failover correctly.

Our deployment took about six months. We had an implementation strategy for the solution but it failed three times before they could get it to work. Our deployment plan was set up to failover for our SQL cluster and several web servers to a backup location. In setting up with the Nimble, Zerto recommended that we use an RDM. The RDM did not work. We were using VMware with Nimble and the Zerto team had not used that particular solution before. We jumped through hoops three times before we were able to get the right combination to get the cluster to failover correctly.

There are only three of us working with Zerto. I am the DBA, we have a system administrator, and we have our IT director. We learned very quickly how to use the product very thoroughly since we had to rebuild our solution three times.

The initial setup is pretty straightforward. 

For an off-prem client, I would send them a welcome letter that details what they need to do on their end with the server. I would send the download package, everything like that. If the client is immediately responsive, that could be done within an hour, but then some clients take a little longer. Once they have the infrastructure set up on their end and the VPN is set up, I can have a Zerto off-prem implementation replicating into one of our private clouds within an hour or two hours maximum, even for a large environment.

The initial setup is very straightforward.

They assigned us an engineer and we were set up and replicating within two hours.

The deployment was very straight forward. A small plugin called a VRA is installed on each host. This keeps track of the virtual machines. Then, there is a dedicated virtual machine that runs the Zerto Virtual Manager (ZVM). This is provides the web management interface and monitors the VRA's. This is also where all configuration and updates are performed. The menus do a great job in guiding you through the configuration of the protection groups.

The initial setup was unbelievably easy. We had Zerto up and running in five minutes, whereas setting up the SRM replication took weeks and needed technical support staff.

The initial setup of this solution is straightforward. It's literally an install button and then next, next, next... 

Our deployment was fairly complex, but then we had to deploy a platform capable of multi-tenant support with complex networking and integration with vCloud Director so that customers could access their DR systems via a secure web interface. If you are deploying a site-to-site solution then deployment is very straightforward. Each site requires a Zerto Virtual Manager (ZVM) which is deployed upon Windows, this will then integrate with your vCenter servers at each site. From here it’s a few button clicks to deploy the Virtual Replication Appliance/s (VRAs) which are small Linux systems bound to each host that handle the ‘smart’ features of Zerto Replication, linking the site and your off.

In 2014, when Zerto was launched, the initial setup was pretty simple.

We do setups of Zerto every week or two weeks, because it's not a single platform. We are a multi-cloud environment and service provider. We deploy it according to project requirements. So we don't have a single Zerto platform. We are always deploying VMs and DRs.

Zerto is very easy and straightforward to set up. Whenever we want to use Zerto for a migration from an on-premises customer to our data center, we usually create a WAN to WAN link, or a LAN to LAN, or a VPN link between the customer and us. We just deploy the VPNs from our side to the customer site and request access to their environment. We check for special VM configurations. It's pretty straightforward. We don't like telling the customer to do it, even though it's very easy to deploy and configure, because it's part of our service to do this job for them. We also have our own guidelines and policies that we use to configure Zerto for the best migration setup.

The last deployment I did took me four hours, which included setting up both my side and the customer side, doing the pairing and, later, the VPG's. We migrated over 100 VMs and it took about two days to fully replicate their site to ours. The migration window to do the move was about six hours because they had to change applications. But the move itself took no more than two minutes for every Zerto machine. 

When I talk to the customers, I tell them that it will be faster than the move window we request. Most of the time set aside for the window is for taking applications offline, because they will often need to reconfigure them. When client data comes from an on-premises site to our data centers, there are usually IP address changes, or we have to update VMware tools, or do something at the Zerto machine level by changing Zerto hardware, such as a network card. The moving itself is pretty straightforward.

I was not involved in the implementation, but I do remember that it was a pretty short implementation time. It included setting up the ZVA agents in our on-prem environment and connecting to our provider's cloud storage. The longest part of the implementation was getting the data, the initial seed or the backups, up there. But that's nothing against Zerto. Every environment will be different on that and has to get its initial copy up there. Since then, keeping copies up to date has been good. It meets up with RPOs and RTOs.

The initial implementation and getting everything set up took us about two and a half weeks. After that, to get everything that we are protecting into the cloud took us close to a month. We had to do it in stages, due to our work environment and our connections at the time. We didn't have the biggest connections, but that's more on our side, not Zerto's.

There are three people involved in maintaining Zerto for us. They're systems engineers.

It is not really complicated, if you do a previous good design. Installation is non-invasive, does not require agents in the virtual environment.It is not really complicated, if you do a previous good design. Installation is non-invasive, does not require agents in the virtual environment.

If you follow the documentation you need about 20 Minutes to first run of replication. This is fast and you can choose it if you want with the trail license from Zerto by yourself.

The initial setup of this solution is very straightforward. We were making initial syncs in forty-five minutes. 

The initial setup is very straightforward compared to a lot of others. The user interface is very simple and very intuitive. It goes one step at a time so you can logically follow through the steps to set it up. Whether it's a small site or a big site, it doesn't really matter.

Overall our deployment took about two weeks. We had a detailed project plan, as we always do with any new products or projects that we come up with.

It doesn't require any full-time staff to deploy and maintain the solution. Once you turn on the process, all that somebody needs to do is just monitor the schedule and see whether it's doing things the way it has been programmed.

Initial setup is fairly easy and the environment can be protected in just a few hours.

Very straightforward and I had a tech with me the whole way.

The initial setup is straightforward. It was easy to set up the PoC and the results were good. Setting it up took a few hours and when it came time to move to production, it was in terms of days.

The initial setup is pretty straightforward and seems to be in line with similar products.

Setup was simple and straightforward. We encountered no issues.

The initial setup was very straightforward, but also a lot of information was needed. A fair bit of time was spent setting things up, but it was really just time-consuming. There was nothing that needed to be done by the vendor.

As far as setup and maintenance are concerned, you need to be sure to set it up properly, test it, and occasionally perform updates. For the most part, once it is in place it is pretty hands-off.

Very straightforward and simple setup.

Smooth and Zerto techs assisted.

Once you have your network configured the Zerto configuration is simple. We implemented a proof-of-concept deployment in about 2 hours.

Initial install was straightforward and simple to complete with the minimum amount of time taken up.

Very easy setup. Like all DR solutions, it requires planning. Specifically the network side. Don't skimp.

Very straightforward, the installation and setup are very simple, and we even had assistance from technical support to accomplish it.

The product needs a VPN tunnel from the customer site to ours. VPNs can be tricky depending on the compatibility of the hardware. The programs themselves are a snap, and surprisingly small.

It was straightforward and easy to setup. Once the software was executed, all that was needed was the basic environment details as well as the hypervisor information.

Straightforward, simple deployment

Easy

The Zerto setup is very easy. The difficult task is setting up any processes that need to be run after a failover.

Yes - super simple.

Initial setup is very straight forward. You simply create a group and populate your machines into the group, select a destination and voila ZVR does the rest.

Very simple.

It was pretty straightforward.

The initial setup was very straightforward and can be done in less than one hour. You can then start replicating between two sites.

It is very straightforward. A simple wizard to install.