Our primary use cases are for disaster recovery, data center movement, long-term recovery, and backup recovery.
HPE Zerto In-Cloud Software for AWS
Hewlett Packard EnterpriseExternal reviews
External reviews are not included in the AWS star rating for the product.
Took our disaster recovery practice from sixteen hours down to thirty minutes
What is our primary use case?
How has it helped my organization?
Zerto took our disaster recovery practice from sixteen hours down to thirty minutes.
What is most valuable?
The most valuable feature is the fully automated failover. The orchestration made the failover very easy for anyone who wasn't necessarily technically knowledgeable to be able to failover a machine.
I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly.
We've moved some of our workloads to the cloud and back from the cloud using Zerto. The native tools provided by the cloud provider were not as seamless. Having DR in the cloud is very important to us because we trust that the cloud provider will provide a solution, but we also want to make sure that for our business purposes, we have a backup to disaster recoveries so that we're able to recover somewhere else if necessary.
We use Zerto to support DR on the AWS platform. We go between two different clouds. We go from VMware to Azure and also AWS.
Zerto made this quite seamless, especially going between two different clouds. It's just a matter of a couple of clicks. You don't need to understand what's happening on the back end.
We use Zerto to help protect VMs in our environment. It took our RPO from around four hours and now it could be seconds. We can recover the machine in under a minute as far as the boot time. We're between five and ten seconds RPO.
The magnitude of Zerto is much faster. We used to do a disaster recovery failover of our critical systems. It took about sixteen hours and once we had implemented Zerto, it took around thirty minutes to do for the same exact systems.
What needs improvement?
I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial.
For how long have I used the solution?
We have been using Zerto for three years.
What do I think about the stability of the solution?
It's been great. We've had it for three years. The only time we reboot the machines is for normal patches. We don't have to do anything else. It just works. We don't have to think about it. We've never had any issues over the three years we've been running.
What do I think about the scalability of the solution?
We started Zerto with a small footprint. We only did a few VMs as a POC with two nodes on each side. Then we've grown it to 34 nodes on each side, including the cloud. It's always the same amount of resources. We're running 150 protected VMs in there. It runs really well.
How are customer service and support?
The few times we've had to use customer service, it's never been for anything that was really broken. It's more informational or because we didn't understand how the product works. They've been great with communication, they get back to us, and even if they don't get an answer right away in one day, they'll let us know with the ticket updates that they're still working on it.
It's been really good as far as the little interaction we've had. The one nice thing is that we've never had to use it for anything that's been broken or that it's not working.
They have great communication. They don't just send you links to KB articles.
Which solution did I use previously and why did I switch?
We looked at other solutions before we purchased Zerto. We did a bake-off with a couple of other solutions. Zerto blew everything else away. The functionality is the same as everybody else, but the amount of time it takes to implement Zerto is a lot quicker.
Making changes if you want to add another machine or another workload takes virtually seconds, whereas we found other systems took a planning time and could take hours to get implemented correctly.
How was the initial setup?
The setup was great. We had one of our newest engineers run through it because as part of the POC, the salesperson showed us how to install it. It was very straightforward. We took somebody who knew nothing about Zerto, had them install it and they had it installed and running in about fifteen minutes. It is quite easy to use.
I can't say it's the same for SRM. There's a lot of documentation, whereas, with Zerto you point to the button, you push, and it works.
What about the implementation team?
We did the full installation ourselves.
What was our ROI?
We got the recovery time from sixteen hours to thirty minutes. Prior, when it took sixteen hours, there would be about ten or more people who were waiting for systems to come online to be able to test.
With Zerto, within an hour, we get the systems up, and then it's thirty minutes to test. Everybody can go home. There's a lot less time for people to be available. Zerto makes it much easier and quicker to get completed.
What's my experience with pricing, setup cost, and licensing?
The licensing model per VM is great. It's a good way to license it because you want to protect only the devices that you're looking to protect. As far as getting the licensing and working with the sales team, they're very responsive. There's a lot of great communication, it's good all around.
Which other solutions did I evaluate?
We looked at VMware SRM. We also looked at a manual process. We chose Zerto for the simplicity and the cost ratio was phenomenal. It's easy enough that we've had nontechnical people able to failover just by clicking a button.
For Zerto, you add the VM in the VPG or workload, point it to the target, pick where you want it to land, hit go, and it's done. With SRM, in comparison, you'd have to make sure it's being replicated between the two SANs. You have to go to a different UI, configure all of it, make sure that's working, then go into SRM and configure all the orchestration parts. It takes a lot more planning. You really have to make sure that all the different systems work together, whereas Zerto takes care of all that for you.
What other advice do I have?
I would rate Zerto a nine out of ten, there is some room for improvement. The drawback for me is that it's not compatible with every single hypervisor. If we wanted to go with another vendor for a hypervisor locally, then we'd have to look for a different solution, and there's nothing really out there that is comparable to what Zerto can do.
The near-synchronous replication is its shining feature
What is our primary use case?
Our primary use case is for DR failover.
What is most valuable?
The most valuable feature is the rollback feature that captures every couple of minutes. Whenever we have a server that goes down, we can use that to pull it back a couple of minutes before and it's good to go.
The disaster recovery has been a benefit to us. The ability to capture or move something to another data center is also a really handy feature.
The near-synchronous replication is Zerto's shining feature. We leverage the most out of it.
On the technical side, we usually need more of the deeper, not near-synchronous replication. We need it more for the back backups but there's always a fire drill. There's always an emergency that needs something that happened five minutes ago to be restored.
We use Zerto to help protect VMs in your environment.
What needs improvement?
When setting up Zerto, you have to set up VRAs. I would like to see those not be needed as much. They're a little cumbersome and take up a lot of VM counts.
For how long have I used the solution?
I have been using Zerto for around four to five years.
What do I think about the stability of the solution?
The stability is perfect.
What do I think about the scalability of the solution?
It feels like scalability is what it's built for. It's seamless.
How are customer service and support?
I don't usually have to call support. Some of my coworkers are a little more familiar with it, and they have always said that Zerto support is very good.
They're fast, responsive, and willing to look at issues that they're not familiar with.
An interactive chat with knowledgeable staff could be a helpful feature.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We also looked at VMware. Zerto outperformed it and was more affordable.
What's nice about Zerto that I don't think we saw with VMware is the ability to use one console for multiple beta centers. It's really nice not having to go into a specific site to come to or from that site. If a site or a whole data center goes down, you can still access it from the other and pull over it if needed.
How was the initial setup?
We had VRAs that we had to set up. The initial setup was good. The hard part was getting all of the servers into certain groups and then getting the disaster recovery plan for all of those. That was the hard part. Once you have that all setup, initiating those plans is very easy.
What was our ROI?
We have seen ROI. I'm more on the technical side so I can't give exact metrics.
What other advice do I have?
I would rate Zerto a nine out of ten. It gives me everything I want and everything I would need. Failing over is easy. Disaster recovery is easy. If there was ever an event where I had to roll over a whole data center, I don't really worry about it because Zerto has been there. The setup was probably the hardest part but once you get the hard part done, the rest is easy.
Sometimes the console is a little hard to understand. Simplifying some of the commands inside of it would help. It's a very minor aspect. Sometimes the endpoint and destinations can get a little confusing and exactly how you want some of the functions to roll over can be a little bit hard to pick up.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Always works, is good for our business use case, and is easy to set up
What is our primary use case?
We use Zerto for data and disaster recovery replication.
How has it helped my organization?
From time to time, we have to go look at the DR environment. Every time we go there, Zerto application always works. That's a benefit.
Zerto's near-synchronous replication works. The value for our business case is okay.
Zerto's near-synchronous replication is important for healthcare, but not as much because we have time to recover data.
Zerto helped protect VMs in our environment, just for the DR.
Our RPOs are not very aggressive. So, Zerto works just fine for us.
What is most valuable?
It's very easy to set up. Up until now, even with an old version, it always worked fine.
What needs improvement?
There is room for improvement in the upgrades. We are planning an upgrade now, and it seems that it's not straightforward.
In future releases, I look forward to the security feature.
For how long have I used the solution?
We have been using Zerto for more than five years.
What do I think about the stability of the solution?
Stability is very good. We have complaints about stability.
What do I think about the scalability of the solution?
We haven't had issues with scalability. When we add VMs, we just buy additional licenses.
How are customer service and support?
The customer service and support are very good. Every time we have problems, they're ready to help us.
They're always available and very knowledgeable.
They need to be on-site. That would make them a ten on ten.
Which solution did I use previously and why did I switch?
We have only used Zerto.
How was the initial setup?
It was very easy to deploy. There wasn't a lot of configuration needed to get the syncing working.
It is an on-premises deployment.
What about the implementation team?
We used HPE Services. Our experience with them was very good.
What was our ROI?
We have seen ROI. Several times, we needed to recover, and we were able to go to Zerto.
What's my experience with pricing, setup cost, and licensing?
The pricing, setup, cost, and licensing are comparable to other solutions. Zerto is not more cost-effective.
Which other solutions did I evaluate?
We looked at Veeam. They're very similar. We already had the skills for Zerto, so we decided to stay with it.
We decided to stay because we have not had any problems with it, and moving to another solution doesn't make sense for us.
What other advice do I have?
I would rate it an eight out of ten. The version we have doesn't have security yet, so maybe the next version will get a ten.
Has really good near-synchronous replication and protection, which is an advantage for customers
What is our primary use case?
We use the solution for running demos for HPE partners and customers, regarding disaster recovery and backup.
How has it helped my organization?
Although our primary use case is to show demos to partners and customers, we think it's really valuable.
What is most valuable?
The most valuable features are disaster recovery and that the RTO takes less than ten seconds. It's a reallypotent tool.
The near-synchronous replication is really good and an advantage for customers. This feature is really important because we can show it to customers and partners, helping recovering from ransomware, and does provide huge value.
You can protect your VMs in the environment. It depends on the network and environment, but the RTO takes around 7-8 seconds. When you compare Zerto to other solutions in the market, it's very powerful.
Also, the ease of use and speed of recovery are wonderful.
What needs improvement?
I'm happy with the solution, but I would like Zerto to support other hypervisors too
And the price could be cheaper, but it is reasonable.
For how long have I used the solution?
I have been using Zerto for four years.
What do I think about the stability of the solution?
It's very stable.
What do I think about the scalability of the solution?
The scalability is really good.
Which solution did I use previously and why did I switch?
We have used SRM from VMware and RapidDR from Simplivity. In comparison to those products, Zerto is really simple to use and helpful.
We are constantly trying new products. Zerto has the lowest RTO, you can recover a lot more quickly than using other solutions.
How was the initial setup?
The initial setup is very easy.
What about the implementation team?
We did the implementation ourselves.
What's my experience with pricing, setup cost, and licensing?
Our clients think it's quite expensive but I advise them to consider all of Zerto's features.
You need to start with 25 VMs, which sometimes is too much for SMB clients in some countries. It would be better if they had the option to start with a license for less VMs, like 5 or 10.
What other advice do I have?
Overall, I rate the solution a nine out of ten because of the low RTOs, the ease of use, and how helpful it is for clients.
Provides continuous data protection with live test failover and has an easy setup
What is our primary use case?
We use it for continuous data protection on our mission-critical clinical systems. I work for a hospital. We use it to prevent ransomware, malware, or basic recovery for things like our patient data and imaging system. At one point, we used to do recovery once a day. With Zerto, our recovery objective right now is in six seconds.
How has it helped my organization?
We had a database failure one night at around 11 o'clock, and it had probably been about 23 hours since it had a hard backup. With Zerto, we brought it up in my DR site within ten minutes, and it controlled all of the hospital's registration features. Without that system, we can't even ingest patients into our system. So we brought up that database within ten minutes, got it back in line, and continued operations.
What is most valuable?
The live test failover is the most valuable feature because it allows me to validate that my data is protected in the event of a failure.
The near-synchronous replication Zerto provides is awesome. This feature is very important, especially because in today's age of ransomware and everything is so data-centric in a hospital, I need to be able to identify the point in time of infection and recover to the most up-to-date available point in time that I can without having to lose patient data. At one point, we used to do a 24-hour recovery. but in today's day and age, you can't lose a day's worth of data.
We use Zerto to protect our VMs in our environment. It improved our RPOs because before we had 24-hour RPO, and now I'm within ten minutes.
Zerto's speed of recovery is fast compared to other solutions. We use Zerto and Veeam. Zerto already has the disks, which must be signed into and presented. There's a lot of rescanning involved, but Azure builds the VM, attaches the disks, and powers it up. We're leveraging RTO in under ten minutes.
What needs improvement?
The price could be improved. It's pretty expensive per server, but in the long run, it's well worth the level of protection it provides.
For how long have I used the solution?
I have been using Zerto since 2023.
What do I think about the stability of the solution?
Stability is very good.
What do I think about the scalability of the solution?
Scalability is excellent.
How are customer service and support?
Support is very good.
Which solution did I use previously and why did I switch?
We used Veeam, which didn't offer any CDP. We use Zerto primarily for continuous protection.
How was the initial setup?
The initial setup was easy. We had a professional services engagement when we bought our first pack of licenses. They came in and worked with us. We had monthly and weekly meetings for three months to set up everything.
What other advice do I have?
We do not use disaster recovery in the cloud. We have an actual on-prem DR site. We have a multisite Zerto environment that I can bring up in multiple locations, but we do primarily on-prem recovery.
Overall, I rate the solution a nine out of ten for its ease of use, functionality, and multi-tenant support with ransomware detection.
Fast RPO and RTO, ease of use, easy interface, and is always available
What is our primary use case?
I use it for yearly disaster recovery testing.
How has it helped my organization?
The main benefit we see from Zerto is that it helps to meet our disaster recovery objectives.
Zerto's near-synchronous replication is important and impressive.
Zerto helps protect VMs in our environment and has improved all over RPO.
The speed of recovery with Zerto is extremely fast. We're able to perform disaster recovery testing on dozens of VMs within an hour or even half an hour.
What is most valuable?
I like its fast recovery, fast RPO and RTO, ease of use, easy interface, ease of deployment, and that it's always available.
What needs improvement?
I would like for Zerto to improve reporting, provide more data on individual VMs and their performance, and maybe expand into backup with the ability to scan for malware or offline scanning.
For how long have I used the solution?
I have been using Zerto for over seven years.
What do I think about the stability of the solution?
I would rate the stability an eight out of ten.
What do I think about the scalability of the solution?
I would rate the scalability a nine out of ten.
How are customer service and support?
The customer service and support are excellent.
Which solution did I use previously and why did I switch?
We previously used Commvault. It used a lot of scripting and configuration to make disaster recovery happen, and it was slow, with a low RPO.
How was the initial setup?
We haven't tried disaster recovery in the cloud rather than in a physical data center. We only use on-premises recovery.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing was straightforward.
Which other solutions did I evaluate?
We previously used or evaluated other backup and disaster recovery solutions.
We compared Veeam and Commvault against Zerto.
We chose Zerto because of its performance and ease of use.
What other advice do I have?
Overall, I would rate it an eight out of ten because there's always room for improvement.
Used to move servers and VMs between data centers
What is our primary use case?
We're using Zerto to move services between our on-premises data centers and Azure environment.
How has it helped my organization?
Zerto has really helped us streamline migrations to new hardware or other data centers.
What is most valuable?
We use the solution to move servers and VMs between data centers. Thankfully, we don't have to use it a lot for DR.
I love Zerto's near-synchronous replication. It's better than other applications that we tried. This near-synchronous replication is super important to our organization because we don't want to lose any data.
We're now trying to do disaster recovery (DR) in the cloud with Zerto. We haven't had any real use cases, but we're piloting it. It's pretty important to our organization to have DR in the cloud because we're in a very rural area where we don't have a lot of redundancy. So, it's important to have the scalability of Azure where we don't have it.
We use Zerto to help protect VMs in our environment, which is our primary use case. Our RPOs are pretty short. We can roll over a data center in 30 to 60 minutes if we have to. It's pretty quick, and we could turn everything around.
We looked at VMware's SRM but decided not to go with it.
We chose to use Zerto because the RTOs and RPOs were a lot faster with it.
Compared to other solutions, Zerto is really easy to use, and its interface is really nice. It's really easy to set up the replication groups in Zerto.
What needs improvement?
We're struggling a little bit now with the appliance migration with version ten.
Zerto could make some small improvements with some of the newer features. You can back up VMs but can't back up individual objects, like email objects, which could be improved.
For how long have I used the solution?
I have been using Zerto for about seven years.
What do I think about the stability of the solution?
The solution's stability is very good. We haven't had any stability issues with Zerto.
What do I think about the scalability of the solution?
Zerto can go bigger than our environment, so I think it has good enough scalability.
How are customer service and support?
The solution's technical support is pretty good. Since we haven't had a lot of issues with the tool, we don't really use the support much. The cases we've opened have been resolved quickly by the support team. The support team seems knowledgeable and quick.
I rate the solution's technical support an eight or nine out of ten.
What about the implementation team?
We have Zerto deployed in our on-premises data centers and for Azure VMware and Azure native so that we can switch between them. The solution's deployment is really easy. You just deploy the main tool and then tie it into your virtual environments.
What's my experience with pricing, setup cost, and licensing?
Zerto's pricing was not that bad. I think it's gone up since we went live and added the cloud options now that we are an enterprise. The solution is expensive, but it's worth the price.
What other advice do I have?
We use both public and private clouds to deploy the solution.
Overall, I rate the solution an eight or nine out of ten.
Ensures stability and protection against cyber-attacks
What is our primary use case?
We use the solution for a couple of functions. One is cyber recovery, and the other is backing up all our infrastructure with the server.
What is most valuable?
The most valuable feature is the recovery. For example, in our financial operations, we eliminated two other vendors and reduced our costs.
Having DR in the cloud is crucial for us. We use it as a third copy to ensure stability and protection against cyber-attacks, giving us a clean copy in the cloud. This helps protect our VMs, and our RPOs are close to zero.
The recovery speed is much faster and less complicated than it was.
What needs improvement?
The knowledge base could be improved. Sometimes, it's finicky, especially when moving storage around. We've had to redo entire processes, which was time-consuming and resulted in data loss. This has happened multiple times, and despite following support steps and contacting support, we often had to resolve issues on our own.
For how long have I used the solution?
I have been working with the product for a year.
What do I think about the scalability of the solution?
The solution can scale well if you have the needed storage.
How are customer service and support?
We received conflicting answers and resolutions to the same question depending on who we spoke to. Despite this, Zerto is stable. One of the key challenges we faced was during infrastructure moves, such as moving data or personnel. In these cases, we often had to rebuild our VPGs.
Which solution did I use previously and why did I switch?
We used Site Recovery Manager for VM replication and Veeam for backups. Zerto outperformed these products.
How was the initial setup?
Deploying the solution involved a learning curve. The knowledge base had conflicting data compared to other vendors.
What about the implementation team?
HPE helped us with the deployment. Our overall experience with them was good. They answered our questions during virtual sessions. However, we encountered some customer service issues, as the resolution could vary depending on who we spoke to.
What was our ROI?
We have seen ROI by eliminating vendors and thereby saving costs.
What's my experience with pricing, setup cost, and licensing?
Zerto's pricing is comparable. Each product has its ups and downs.
What other advice do I have?
I rate the overall product an eight out of ten.
Has a fast recovery time and good near-synchronous replication
What is our primary use case?
We've used Zerto for file recovery and entire VM recovery.
What is most valuable?
Having a fast recovery time for both of our use cases is invaluable to the business.
The ability to form our backups automatically during the day has saved us, more than a few times.
My impression of Zerto’s near-synchronous replication is very positive. It gets the job done.
Near-synchronous replication is very important for our organization who use a lot of different versions of files across environments and database changes. It's what we do every day and having the functionality of near-instant recovery on entire virtual machines and files is a blessing.
We use Zerto to protect our VMs in our environment. We do daily backups with a different backup management software and having the ability to recover data in under ten seconds has been helpful.
Speed of recovery has been very effective in getting our information back as fast as we're able to get it. The daily backup solution that we use alternatively only allows a single backup versus having continuous backup replication with Zerto, it's a no-brainer.
What needs improvement?
I would like to have more granular notifications for jobs and workloads within the applying case application.
For how long have I used the solution?
We have been using Zerto for around sixteen months.
What do I think about the stability of the solution?
It's pretty stable. The company itself has been around long enough to know they're not going anywhere. The number of clients that use them on a day-to-day basis speaks for itself.
What do I think about the scalability of the solution?
For our environment, scalability does a great job with how it is. It can handle scaling.
How are customer service and support?
Zerto technical support is some of the best around. I know when I reach out to them over the phone or via email, they are there quickly and offer great support.
I would rate them a ten out of ten. Every time I have to call them, they get something ready, very fast, and our issues are resolved quickly.
Which solution did I use previously and why did I switch?
We still use Veeam.
We chose Zerto because when we started our path with GreenLake, we began looking into other backup utilities and Zerto was highly recommended. After we saw a product demo, we were sold. The demo sold itself very well.
Once the VPG is configured, the automation for backups happens on its own. There's nothing else to do. You can monitor but until you need to recover the files, there's nothing else to do. Zerto is very simple. We enjoy using the product.
The main difference between Veeam and Zerto is that with Zerto, we can get our near-instant recovery window to pull entire virtual machines back from the brink of failure. We might be able to implement more recovery windows for Veeam but from a data storage perspective, Zerto does a great job with deduplication.
How was the initial setup?
We had a third party enable our Zerto configurations. They did a great job. The same VPGs are still running today.
What about the implementation team?
We used an integrator for the setup. We had a good setup. They walked us through any issues we had after the setup.
What other advice do I have?
I would rate Zerto a nine out of ten. There is a network issue that my team is still trying to figure out. Once we take care of it, it'll be a perfect ten.
Zerto should be our primary backup solution but until we can get the network issue resolved, it is relegated as a secondary source. It still does its job. We've used it multiple times for specific cases, and it's always passed with flying colors.
Primarily used for DR situations and provides real-time backup and high uptime
What is our primary use case?
We use it primarily for DR situations. Whenever we lose our primary location, we switch to another location. We also backup resources and migrating VMs in and out of different environments, cloud versus on-prem.
What is most valuable?
The most valuable feature is that it provides real-time backup. We're in the financial industry and have to have 100 percent uptime.
It helps us have a lot better uptime than what we would normally have. It's always real-time synced, with instant recovery. We can return to another location if power drops or generators don't work.
It gives us quick uptime. It also helps our customers maintain that trust, so Zerto really does help with trust. We generally use it on-premise.
The near-synchronous replication is really good. It gives us quick uptime. It helps our customers keep that trust in us.
We use Zerto to protect VMs in our environment. Until Zerto, I didn't pay much attention to RPOs. Zerto gives the ability to bring RPOs down to seconds.
For certain use cases, Zerto has a better speed of recovery compared to other solutions but it doesn't tie into our SANs like Veeam does.
What needs improvement?
It is a little expensive.
We could streamline the installation better. The other thing would be ransomware notifications, like IO anomaly notifications. If they integrate with the SAN, that would be valuable to see in terms of snapshots.
For how long have I used the solution?
I have been using Zerto for six to seven years.
What do I think about the stability of the solution?
We came up with the new version, and it's pretty good. If there's no reason for me to say it's unstable. It's been proven so far.
What do I think about the scalability of the solution?
If you buy the licensing, it will scale up to size until you will spend money on it.
How are customer service and support?
Support is helpful.
Which solution did I use previously and why did I switch?
If you want to pull from the snapshot instead of tools, then SRMs are better used for this case. It's fast and the first to market with continuous data protection.
Zerto is easier to use. There is some standup at the beginning, you must install the agents. It's easy to use when it's working right, but sometimes, it takes great effort to get it going if something goes down.
We use another solution, Veeam. We keep them both because they're both beneficial for different use cases.
How was the initial setup?
The initial setup is straightforward, but if you have it the first time, you are stranded in the industry. It could take a little figuring out, but Zerto is pretty helpful.
There have been a couple of situations which they weren't able to fix an issue right away. We move everything off to a different server until we can circle around and extend that one.
What about the implementation team?
We did it in-house.
What was our ROI?
Zerto has paid for itself in man-hours saved.
What other advice do I have?
Zerto gives you the ability to bring RPOs in seconds. We can have instant uptime for everything.
It's more expensive than other solutions but it's worth it for our environment. It has made it very easy to restore files because you can restore them down to the second. It's pretty simple. We have the agent and all the hosts.
Overall, I rate the solution an eight out of ten.