HPE Zerto Software Reviews

We use it for backup and replication.

The total time for replication has been reduced drastically for us and that really adds value in the long run because time equals money and resources.

It has also helped to reduce our DR testing. Previously, when we were doing it across our own locations, we had to make sure it was working by doing a lot of testing back and forth.

Also, the solution is already up to the mark on audits and certification.

For us, the most valuable features are the quick upload time and how the sync works. The sync is pretty good and that's really helpful. The quick upload is important to us because other solutions were lagging behind. We have VMware SRM and Veeam, and they have been pretty slow and sluggish. We have had some challenges with them.

We have been using Zerto for seven years.

We're just replicating and I assume it runs on some kind of cloud as an overlay, so the stability is pretty good.

The scalability is insane. Really good.

An area for improvement is the support because it gets really expensive. They need to make it a little cheaper. Support also takes time.

Neutral

We still have some other solutions in-house. We are not fully dependent on Zerto. We are still trying to get rid of the others, but we have not entirely moved on.

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

We used an integrator. Our experience with them, at our engineering level, was that it was pretty smooth and streamlined, the first time we used Zerto. We had a few issues in the initial deployment, but later on, when we moved to scripting, the process became streamlined.

I would like to see different service levels. They're good, but it still takes a lot of our budget in ops.

We evaluated Veeam and SRM. Zerto is an HPE product, and we have been using a lot of HPE servers. That trust in HPE won our business.

When comparing Zerto with Veeam and SRM, the latter are newer in the market. They try to provide a multi-cloud strategy with tie-ups across six different clouds, which is different from Zerto. That's where I would use them if I had to.

All the solutions were almost equal but Zerto is still better because they have a lot of releases and new versions.

We are just using it for backup and replication. We have not yet had an event where we have had to restore.

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

The analytic tools are great. 

The external API is something we're using quite a lot. It was upgraded, however, we still haven't upgraded to nine. We were starting to work at six, then seven, then eight, and now we are at eight of five updates. We've been working with this product quite a lot, and they have constantly added a few features. The long-term journal is one feature that is useful in that it allows us to use the product as both CDP and backup. You don't need the backup and disaster recovery tool. That's lowered the overall maintenance and operational costs. The OPEX gets reduced, once you use these two products. 

They have reasonable support. The Zerto university for training staff is very useful. It's very easy to get people on board and to get technicians to work and be familiar with the product. The virtual labs are very useful. You have a sandbox and you can easily play and try the product.

Unlike other products that split the VPG into protection plans and activation plans, they're doing everything within the same location. 

Technical support is good.

It's a very stable solution.

They could improve their online documentation.

From a reliability perspective, the product is around seven. It's less reliable than, others for example. They have one limitation when they have a virtual protection group that does everything.

From the ease of deployment perspective, it requires expertise and time. It's not very easy to do auto-tagging or to run multiple VPG genes at the same time. So, from multi-tenant or multi-complex scenarios such as using Zerto external products, such as firewalls, while their own product is good, it's part of a larger ecosystem, that still has a long way to go.

The triggering of external products could be better. Combining a master runbook and not just a single VPG or splitting the protection group from the activation plan could be better. There will be a protection policy and activation policy as being done in other products. 

Better tagging and better multi-term support are needed. Currently, there is no tenant admin support, only global admin support. They should work at the tenant level instead of the global admin level.

Right now it's an HPE product; they're no longer a startup. We are hoping that being bought by a major company will do good for them and they'll fix what needs to be fixed. There were very good products, to begin with, and HPE should work to make it even better.

We've been using the solution for the last three years at this point. 

The stability of the product is good. There are no bugs or glitches. It doesn't crash or freeze. it's reliable and the performance is good.

Technical support has been great. We are happy with the level of support.

We use both on-premises and cloud deployments. In terms of the cloud we are using, we are using Azure. We are using our own Cloud provider; we are using VMware Cloud Director.

I would rate the solution at an eight out of ten. We are happy with its capabilities. They are a very good product, however, they are not perfect just yet.

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

Zerto has taken us from being able to do a failover in four to six hours down to one to two hours.

The most valuable features are

• the continuous streaming
• that it takes very little CPU usage — it doesn't affect production 
• the recovery time is very short.

With the VPG (virtual protected group) it would be nice if you could pick individuals in the grouping instead of having to failover the whole group. 

Other than that, it's a pretty good product.

I have been using Zerto for about a year.

It's very stable.

I don't see a problem with scaling it at all. They could improve setting up for SQL clustering or for SQL Always On. It really is set up for a one-to-one and not for a multiple solution. They could work on that.

We will probably increase our usage in the future. Right now we have a license for 15 VMs through Zerto and we are only using 10.

We haven't worked with Zerto's technical support other than during deployment. Everything seems to be running really well now. During deployment, their support was very responsive. It's just that they did not have a good solution that worked with VMware and Nimble.

Positive

We were using Veeam. We switched to Zerto because it has continuous streaming that would keep us up to date a lot faster. Veeam kept promising they were going to have that, but they never came through on their promise, after waiting for a year. We were able to convince management to switch to Zerto.

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.

We were working with Zerto directly. They didn't have a good solution and we had to test out a lot of things with the hardware and software that we were using. They could have improved that. They kept giving us solutions that would not work, so we had to keep trying different solutions.

It's hard to say if we have seen ROI since it's only been running for about four months. I think that we will see cost savings over the next year.

As far as licensing goes, start out with what you need to get started and you can always scale up. Zerto worked very well with us. They have a tool called zPlanner which was able to document how much we needed to get started. That was a very handy tool.

We looked at some other options, but nothing really compared to what Zerto offered.

The main differences were the ease of use, not having to have a dedicated person assigned to watching it, and the automation. A lot of this stuff is taken care of through Zerto without us having to script or put a lot of effort in on the back-end. Everything is automated.

Make sure that they can demo what you want done before you move forward. We had a problem with the SQL clustering. Make sure that the equipment that you're using is certified by all the vendors that are involved, like VMware.

Now that we have the solution working, we're very happy. We've had it working for the last four to five months. We were able to test it with a test platform and it worked amazingly.

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

Zerto has helped to reduce the number of people involved during a data recovery situation in our company. All we have to do is click a few times. We have even configured a DR solution for our customers so that they can do it themselves. We give them access to the Zerto platform, as well as have a small manual of instructions, and they can go do it. It's very simple to use and to deploy and to support. It does not have a very large learning curve.

For our clients who do DR in the cloud, Zerto has definitely saved them money. We only have a few DR client accounts, but for the ones we do have, there haven't been any failures of Zerto, whenever we do failover tests. It performs well.

It's a great platform because it's very well built, technically. 

It's also very much faster than any other migration or disaster recovery platform we have. I work with virtualization, mostly on VMware, and I must admit that Zerto is even better than VMware Site Recovery Manager. Zerto compresses the data and it works much faster. We use it whenever we can, and especially whenever we are on a tight time schedule for closing a project, or we need to bring information or VMs from a client or from another data center. Zerto is very valuable because of its speed.

And in terms of ease of use, when I started with my current company I didn't even know about Zerto. My first project was a migration from a big customer and I thought, "Wow, this will be a lot of work." It was a little scary because of the pressure to get it done. But Zerto was so easy to use. I like it a lot.

I've been using Zerto for about 12 months, but the company I work for has been using it for four or five years.

It's very solid, like a rock. It's very stable.

Even with the most recent customer that we migrated to our data center, it was really impressive that Zerto kept the levels of performance very consistent. This customer's site was at another data center provider, not one of ours. It was on a very old VMware version, and we were deploying them to the latest, vCenter Server 7. At first I thought, "We will be struggling to bring this customer over," because they were two major versions behind. I didn't think Zerto would be compatible for making this migration happen. But it worked like a charm, and we had no problems regarding Zerto itself. While we had some problems with this migration, they were not related to the technology.

It's very scalable. Most of our core usage here is for migrations from our customers' on-premises or data center instances. And about two years ago, we had a very big migration of over 3,000 virtual machines, and Zerto performed really well. That's why we have kept Zerto in our portfolio.

Their support is amazing. We have had to open some support cases and they have a very good technical team. They're always referring us to their technical teams if we need to discuss something. Or if we fail to understand some of the concepts, we can reach out to them too. It's more than a commercial relationship. They support us whenever we need help.

Positive

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.

Because I'm a support engineer, I don't really work directly on the commercial side of things. Whenever I need to request a license for Zerto, someone on our dedicated licensing support team takes care of it. So I don't know if that process is easy or not.

Zerto works very well as a backup and recovery solution, with frequent recovery points. It's very good. But it's too pricey for us to use it as a backup solution for all of our clients. Not every customer needs recovery points every five seconds.

It's a great platform, if you use it as a recovery system and as a migration tool. It's really amazing. It's a very well-developed product and one of the best solutions. In the same way that what makes Microsoft big today is Active Directory, which is an amazing product and one that no other enterprise could do any better, Zerto is the same type of leader in its category and is at the very top, without a doubt.

We have Zerto as an emergency backup if we were to lose electricity or compute.

I purchased Zerto because I wanted to get a return to operations and to minimize the downtime.

The return to operations is the most valuable feature because it decreases the amount of time it takes us to recover. 

Zerto is the best of breed when it comes to providing continuous data protection.

It has a number of features rolled together. So when we need to failover, it does it successfully without a lot of stuff that we have to tune underneath the scenes. We use Zerto for the short-term retention of the data.

I would rate its ease of use as an eight out of ten. It has made it a lot easier for us to failover. Usually, in the past, we had to manually go and bring things up and this automates it.

The solution decreases the time it takes and the people we need when we need to fail back or move workloads. It saves around eight hours and one person. We had started off with two to three people.

It could save us time in a data recovery situation due to ransomware or other causes but we haven't used it for that.

We haven't had something where we had to recover data using this product, but I assume it would reduce the number of staff involved in data recovery situations.

It has helped to reduce downtime in testing but we haven't had a serious issue where we had to switch over and use it.

The documentation needs improvement in terms of the setup, getting enough detail, and getting that up to speed.

I have been using Zerto for about a year. 

We found Zerto to be pretty stable.

We haven't had problems with scalability.

We don't really have users. We just have data that we move over which is basically the size of the campus.

We need at least one full-time employee to run it.

It's used for all of our failovers so it's in 100% usage.

I have had a little bit of experience with their technical support. I don't have any issues with them.

The ease of use, compared to other products, is much better. Zerto is all-encompassing. 

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.

We'll probably see ROI in around three years. 

The pricing is more expensive, but the functionality is what we wanted.

There are no additional costs to standard licensing.

We also looked at Druva. We liked the flexibility that we get with Zerto. 

You'll be happy with Zerto.

The biggest lesson I have learned from Zerto is to be patient. 

I would rate Zerto a nine out of ten. 

We primarily use Zerto for replication and disaster recovery.

Zerto is good in terms of providing continuous data protection. We have databases that require point in time recovery capability and Zerto is very flexible in this regard, compared with some other solutions we use, such as Sybase Replication and Oracle Replication.

We do not yet use Zerto's long-term retention feature but we are planning to do so. Currently, we are exploring AWS Glacier for long-term retention, and we will see how Zerto can help with the process.

Using Zerto has helped to simplify our process. The DBS steps are very deeply involved in the case of Sybase replication. This means that it takes a lot of technical skill, time, and effort to manage Sybase replication. Compared with that, Zerto is very user-friendly.

When we need to failback or move workloads, Zerto decreases both the number of highly skilled people involved and the time it takes to complete. For example, to do a command-line restore and recovery of Sybase involves pages of steps and it requires a talented DBA. However, with Zerto, we can take care of that with an intern. Only one person is involved in the process for either case, but with Zerto, fewer skills and experience in recovery are needed.

Fortunately, we have not yet been the victim of a ransomware attack. However, I am confident that Zerto can help, should that situation occur. Similarly, since implementing Zerto, we have not had any downtime. That said, we have simulated different scenarios and our results were good.

The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so.

Zerto is pretty user-friendly. Normally, data recovery involves a lot of DBS skills but with Zerto, it is point-and-click.

It is very important to us that Zerto provides both backup and disaster recovery in a single platform. Because of problems that people are facing, we needed to have recovery time objectives (RTO) and recovery point objectives (RPO) for the major cloud providers. This is the primary reason that we were looking for an up-to-date and current solution.

I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files. I have not tested it yet, so I can't say for sure whether it will choke or not.

The two large clouds that we use are AWS and Azure, and compatibility with these is always important for us.

We have been using Zerto for approximately five years. We are using one version back from the current one.

In terms of stability, so far it looks okay but I am not sure how Zerto will react to volume loads. We haven't had a chance to test that because we don't have such a large environment.

Scalability has been good but I have yet to see how large a file it can handle.

We have two DBAs using the product, and then we have some interns to help out.

Currently, it is running in a small network where it is backing up a couple of replicated environments. We may increase our usage in the future, as we are now just beginning to back up everything to AWS.

Zerto's technical support team is pretty knowledgeable.

Prior to Zerto, we were using Sybase replication. When Sybase was acquired by SAP, we began having trouble when we needed technical support. The reason that we started looking for a replacement product is that we used to contact technical support in California when we needed help. However, we now have to call Germany first, only to have them redirect the call to California. SAP is a mess.

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.

A couple of people from our organization handled the deployment, and we had some Zerto technical reps available to answer questions. The Zerto staff are pretty knowledgeable and they answered the questions well.

Compared to the licensing fees with Oracle and SAP, we see a return on investment.

Price-wise, Zerto is fairly reasonable and I can't complain about it when we compare it against Oracle and SAP licensing.

We have not tried using any features that are outside of the standard licensing fees.

We looked into Oracle GoldenGate but it is pretty expensive and cumbersome. Sybase is better than Oracle in terms of pricing, but Zerto is cheaper.

We have not yet enabled data recovery in the cloud, but we are planning to use it. As of now, we haven't tested it. We always back things up but in terms of restoring and testing, we are behind.

My advice for anybody who is considering this product is that it is pretty user-friendly compared to Oracle and SAP. This is a good solution to start with. Once it has been implemented, I suggest moving to volume testing to see how well it handles large volumes of data.

We have never had a real situation where we were under the gun for the purpose of RTO and RPO recovery times. As such, I can't say for sure how it will behave in a real situation but we are satisfied with our tests.

I would rate this solution an eight out of ten.

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

Zerto provides us with continuous data protection and it is working well for us so far. It has matched our requirements, especially in terms of compliance and security considerations. The solutions in our environment are working together to make everything achievable in terms of different certifications.

We have only been using Zerto for less than a year, and have not had much time to consider long-term data retention. However, it is our intention to use this capability in the future.

Using this product has enabled our leaders to guide the business through our transition to the cloud. It has allowed us to implement a cloud-based disaster recovery solution.

Having a cloud-based disaster recovery solution, rather than a physical one, saves us in terms of resources. I don't have exact numbers in terms of money, but I can say that in the short time that we have been using Zerto, it has saved us between 10% and 20% resource-wise, including time.

We do not have any real use cases so far, but our model shows that we will need fewer people involved when we failback or move workloads. I expect that we will require 10% to 20% fewer resources in these situations.

So far, we have not had a use case where we had less downtime because of Zerto.

The most valuable feature for us is accelerating cloud adoption, as it helps provide greater speed for disaster recovery. Ultimately, this saves us time, as well as resources.

This product is easy to use. Initially, we had some issues and hiccups but we worked with the solution engineers and were able to rectify the problems and move forward.

When we initially set up the product, we didn't know about the exact features. Some of them were discussed in different wording. It took some time to get to know the solution in general, and exactly what functions each of the features is used for. They seemed more like hidden features to us.

I have been using Zerto for close to one year.

The availability of Zerto has been good for us, so far. We have not experienced any issues with it.

Being a cloud-based solution, it can be scaled as per our requirements. I don't see any issues with it. We have three people who work with it, although not on a daily basis. They are technical analysts and product engineers.

They were more hands-on during the PoC and deploying it, and they will be involved if we have any issues.

Technical support from Zerto is good and they help us all the time.

The turnaround time is good, as well as the help that they give us in understanding and resolving problems.

We are still using our previous solution for backups. We are switching away from it because we will be able to take advantage of automation and use fewer resources.

In terms of cost, using Zerto saves us approximately 15% over our previous solution.

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.

My team was responsible for deployment.

We have seen a return on our investment in terms of time and resources.

We evaluated several other solutions prior to selecting Zerto.

We chose Zero because it is more user-friendly, and better overall.

My advice for anybody who is considering Zerto is that it's user-friendly, easy to use, and easy to deploy. So far, Zerto has been working fine for us and my team has not had any complaints.

I would rate this solution an eight out of ten.

I am a cloud provider and I use Zerto to provide disaster recovery solutions for my clients.

Recently, we had an issue where one of our customers using Oracle Server experienced corruption in a database. The customer doesn't know when the issue started, so we used Zerto. We started to do a real-live failover for the machine, and we were able to determine the timestamp for the start of the issue. Prior to this, Oracle engineers tried for four hours to fix the database but did not have any luck in doing so. Ultimately, we were able to save the customer's data by using Zerto.

A few of my customers are using file-level restore but the majority of them are using the replication features for disaster recovery.

Zerto offers features for long-term data retention; however, we don't use them. The longest time that we back up data for is 30 days. At this time, I don't have any request for this from my customs, although in the future, if we have a customer that asks for it then we can provide it.

Zerto provides our customers with the ability to continue work, even if something happens to their office or data center.

We have a customer with an on-premises data center that replicates the environment to our cloud. One day, this customer had a water pipe burst in his data center. The entire data center was flooded and everything stopped working. We did a live failover and from that point, he could continue working but it was running from the data center in our cloud, instead. Zerto definitely saved us time in this data recovery situation.

It took the customer between four and five days to return everything back to normal onsite. During that time, he spoke with us at 9:00 AM on the first day, and after an hour, his company resumed work with our help. This reduced his downtime to one hour from approximately five days.

Performing a failback using Zerto is pretty much the same in terms of how long it takes, and how many people we require. The customer decides when to do the fallback; for example, it can be done during the night. We replicate the data at their chosen time and it avoids issues for them because they don't operate during those hours.

In a situation like a burst water pipe or a database becoming corrupt, Zerto doesn't help to reduce the number of staff involved. The reason is that when something affects the company, management, including the CEO, has to be involved. They do not deal specifically with operating Zerto but rather, they wait for things to develop. The good part is that they know that with Zerto, they have a solution, and they don't need to figure out what to do.

In terms of the number of people it takes to recover data in cases like this, there is typically one person from our company involved, and one person from our customer's company.

My customers save money using Zerto and our facilities, rather than a physical data center because they do not have to do any maintenance on the backup equipment. It is also much easier to pay one company that will do everything for them.

Using Zerto makes it easier for my clients, giving them time to work on other things. The main reason is that they don't have to maintain or upgrade their environment. Not having to implement new recovery solutions as their needs change, saves them time.

The most valuable feature is the ability to do disaster recovery.

Zerto is very user-friendly and engineer-friendly, as well. When we need to create a new Virtual Protection Group (VPG) for replication, then it is done with just a few clicks of the mouse. We can see all of the environments and we don't need to install agents on the customer's VMs.

The live failover feature is very helpful.

With regards to providing continuous data protection, it's great. Most of the time, it's about five seconds for replication.

The monitoring and alerting functionality need to be improved. Ideally, the monitoring would include the option for more filters. For example, it would be helpful if we could filter by company name, as well as other attributes.

I have been using Zerto for almost three years.

Zerto is a pretty stable product. We have had issues from time to time over two years, but usually, it is stable. When we have trouble then we contact their excellent technical staff.

I have quite a lot of customers that are using Zerto for disaster recovery and it is simple to scale. Our intention is to increase our usage by bringing on more customers that will replicate from their on-premises environment to the cloud.

In my company, there are five or six people who work doing the backup and recovery operations. On the client's side, they normally have one or two people that are in charge of maintaining the data center.

The size of your environment will depend on how many VMs you need to replicate. For example, if you are replicating 100 VMS then you can use a small environment. However, if you are replicating 1,000 or more VMS then you will need a stronger and larger environment, with more storage and more memory.

The technical staff is excellent and we contact them whenever we need something.

We had a customer that replicated his VM and for some reason, when we tried to do a failover test, the VM came back with an error saying that the network card was disconnected. We spoke with the Zerto technical staff and they actually implemented an ad-hoc fix for our environment. In the next Zerto version update, they released it for all their customers.

The technical support is definitely responsive and they explain everything.

I began using Zerto version 6.5 and am now using version 8. We did not use a different solution for disaster recovery beforehand.

We use Veeam for backup tasks. We looked at Veeam CDP to compare with Zerto, and Zerto is definitely better. It is more user-friendly, agentless, and the technical support is better.

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.

My impression is that Zerto is more expensive than other solutions, although I don't have exact numbers.

We evaluated CloudEndure and we also had Double-Take, but neither of these solutions worked well. These solutions were based on agents, which affected the customers' server performance.

In terms of usage, Zerto is a different level of experience when compared to other products. It is easier to set up and use.

With other solutions, we need to install software on the customer's server and then reboot, whereas, with Zerto, we don't need to do these things. In fact, there is no downtime on the customer's side. Depending on the customer's environment, post-installation downtime may have been as little as one minute, or more than an hour.

In situations where downtime is expected, and there is an important application like a database running, these periods need to be scheduled. Normally, downtime will be scheduled at night, after business hours. Although there may not be a disruption in work, it is an extra effort that needs to be put into the other products.

Looking ahead, I have seen that the next version of Zerto will support Salesforce replication. This could be something that is useful for my customers.

The biggest lesson that I have learned from user Zerto is that every organization should have a disaster recovery plan. My advice for anybody who is considering this product is to calculate how much it will cost in the event of downtime or a disaster, and then compare it to the cost of Zerto. Once this is done, people will opt for a disaster recovery solution.

I would rate this solution a ten out of ten.