Clumio Reviews

My main use case for Clumio is to back up all of my AWS EC2 instances and my RDS databases along with my other EC2 compute nodes.

The best features that Clumio offers are the ability to know when a backup has completed, to know how to restore both files at the file level and also restore EBS backups, point-in-time restores, as well as snapshots.

Clumio has positively impacted our organization by providing us with the peace of mind of knowing that all of our EC2 instances are securely backed up.

This peace of mind has translated into measurable outcomes as we adhere to NIST 800 compliance, and with that, we need immutable backups and the ability to have backups that do not exist within our existing tenants. Clumio fixes that problem for us.

I cannot think of any features that could make Clumio better.

The only other tweaks I would like to see with Clumio are that it provides more granular reporting and dashboards for showing what is backed up weekly, daily, and monthly backups.

I have been using Clumio, the backup and restore function for AWS, for over a year.

Clumio is stable, and there have been no outages.

Clumio handles growth and increased workloads well, demonstrating good scalability.

Customer support for Clumio has been excellent; we have only had one issue, and they resolved it quickly; otherwise, we have not had to reach out for anything else.

We previously used N2W, and we switched because that solution was backing up instances in our environment, costing us more money.

I was originally with a vendor called N2W because my backups were not immutable and were stored in our tenant. Clumio resolves this issue by backing up our instances in an alternate, secure tenant that is not part of our tenant, which makes the solution better than our previous vendor.

My experience with pricing, setup cost, and licensing was smooth; we received pricing that was cheaper than N2W, and it was a smooth transition from N2W to Clumio.

I have seen a return on investment with Clumio, and the biggest time-saver was not having to log into N2W and guess if my backups were working and guess if I could restore them. I could easily figure out how to restore my backups. The time saved was also creating a Slack channel to quickly see when my backups are taking place and have an easy to use and understand frequency of those backups.

My experience with pricing, setup cost, and licensing was smooth; we received pricing that was cheaper than N2W, and it was a smooth transition from N2W to Clumio.

Before choosing Clumio, I did evaluate other options.

I rate Clumio a 10 overall.

I chose a 10 for Clumio because it is a secure, cloud-based backup solution that we do not have to host; it is hosted externally, and the backups are immutable, in addition to being a secure and cost-effective solution.

I appreciate that Clumio provides turn-key controls and uses AI to understand the environment and ensure that all the backups are done correctly.

Clumio has been very consistent for us, showing us everything that is backed up, what is being backed up over time, and where we can improve.

I purchased Clumio through the AWS Marketplace.

My best advice for others looking into using Clumio is to work with a customer success manager and ensure that you get additional credits to test out the platform for at least 60 days to ensure that everything works properly. My overall rating for Clumio is 10 out of 10.

We use Clumio as our ransomware recovery backstop for critical production workloads across a multi-account AWS environment. The primary use case is air-gapped vaulting of RDS, DynamoDB, S3, and EFS data so that in a worst-case ransomware scenario, we can restore to a clean recovery account that the attacker never had access to. We back up across more than five AWS accounts spanning non-production through production, with per-environment backup frequency policies controlled by a reusable Terraform module.

Before Clumio, our disaster recovery posture for ransomware was largely theoretical. We had AWS Backup snapshots in the same account, which wouldn't survive a compromised IAM scenario. Clumio gave us a genuinely isolated vault that sits outside our AWS Organization's blast radius. This allowed us to go from thinking we could recover to actually running a validated gameday where we restored production-representative data into a fresh account and proved end-to-end recoverability. It also forced us to formalize our per-resource-type Recovery Time Objective expectations, which improved our overall incident response planning.

Secure Vault with cross-account restore is the standout feature. The fact that backed-up data lands in Clumio's infrastructure rather than an S3 bucket in our own organization means a compromised admin role can't touch it. The Terraform provider is also critical for us since we manage everything as code. Being able to define protection groups, policies, and organizational unit connections in HCL made onboarding accounts repeatable. The multi-resource-type coverage (RDS, DynamoDB, S3, EFS, EC2) under one platform is convenient too because we don't need separate tooling per service.

The account onboarding process deploys around 20 IAM roles per account, which is heavy. Consolidating those or offering a slimmer permission set for read-only backup (versus full restore) would help with security review friction. Cross-account restore into a target account still requires manual steps for KMS. If Clumio could handle re-encrypting with the target account's CMK during restore rather than requiring Multi-Region Key pre-staging, that would save significant preparation time. Also, the restore API could surface better progress telemetry since right now, large RDS restores are a bit of a black box until they complete or fail. Finally, DocumentDB and MongoDB Atlas backup support would round out our stack nicely.

We have been using Clumio for about one year.

We were relying on native AWS Backup for snapshots and cross-region copies. The problem is AWS Backup operates within your own account's trust boundary. If an attacker gains admin access, they can delete snapshots, modify vault access policies, or disable backup plans entirely. We needed an air-gapped solution where the backup data is unreachable from any IAM principal in our organization. That is what drove the switch to Clumio.

Price it against the cost of the alternative, not against native AWS Backup. Native backup is cheaper on paper but doesn't give you ransomware isolation. When you factor in the engineering time to build and maintain a custom air-gapped vault solution, Clumio's pricing is reasonable. That said, push for volume discounts if you're backing up a large number of accounts. The per-account onboarding model can add up quickly in a large AWS Organization. Make sure you understand the per-GB vault storage costs for your data growth trajectory.

We looked at Druva (now part of the AWS ecosystem), Cohesity, and considered building a custom solution with AWS Backup Vault Lock plus cross-account copies to a locked-down organization account. Druva's coverage for our specific resource types was less mature at the time. Cohesity felt more geared toward on-premises/hybrid environments than cloud-native AWS. The DIY approach would have required significant engineering investment to get the isolation guarantees that Clumio provides out of the box.

Invest time upfront in your Terraform module design for Clumio policies. Decide early whether backup frequency is controlled per environment or per caller because refactoring that later across many accounts is painful. Also, run a restore gameday before you actually need it since the cross-account KMS, networking (BYOIP, VPC peering, PrivateLink), and IAM dependencies during a real restore are non-trivial, and you don't want to discover them during an incident.

The primary use case for our organization is handling backups.

We achieved cost savings. We did a proof of concept to compare the cost with AWS Backups and Rubrik. Clumio proved to be the most cost-effective option.

We are still in the process of discovering Clumio's valuable features.

We are still exploring the areas where improvements might be needed.

We are new to Clumio, and we are still getting to know the solution.

We previously used AWS Backups, and we switched to Clumio for cost savings.

Clumio provides better prices compared to AWS Backups and Rubrik.

We are still exploring alternate solutions.

I use AWS Backup and Recovery for our AWS infrastructure to ensure efficient backup and recovery processes.

We now have the peace of mind knowing that our entire AWS infrastructure is fully backed up into an air-gapped environment. This includes EC2 Instances, S3 Buckets, and DynamoDB Tables.

The Protect and Restore features are very helpful. I can set up tags to include specific assets in our environment for backup. When I include those tags in my search, the assets are easily found and can be added for backup. I love the restore feature and how easily I can restore files, folders, or an entire image.

I would like to see a Dry Run feature for a full disaster recovery implemented.

I have used the solution for 1 month.

I used N2W prior to this and was unhappy with multiple areas of the product. I found the backup and restore process confusing. I was charged for licensing and for hosting the platform in our ecosystem along with all the snapshots, which proved to be expensive.

The credit system can be confusing, but if you talk to your account manager, they can help alleviate those concerns.

I did not consider alternate solutions.

I recommend starting with a trial and ensuring that the CloudFormation stack properly deploys in your environment. Set up email alerting to make sure you receive notifications about backup successes or failures.

Our use case involves backing up AWS snapshots.

We have been able to safely and securely save our backups off of AWS.

The automation of taking backups and transferring them from AWS to Clumio without manual intervention is valuable.

It would be beneficial to show when backups are available and to receive alerts if there are any issues with the backups.

I have used this solution for one year.

I use the solution for backup and retention.

The solution has helped with cost optimization and provided clarity in our backup policy.

Working with the Clumio/Commvault team has been a very good experience.

More alignment with Clumio and Commvault branding would have helped us understand the product better during the discovery phase.

I have used the solution for one month.

Previously, we used the native AWS solution.

Having clarity on pricing is helpful.

We considered Veam and BackBlaze as alternate solutions.

The solution is easy to understand and set up.

We use Clumio for backup. We were looking for an easy way to back up our data. Previously, we had a traditional backup and another tape backup, but the recovery time was slow, and the backup often failed. Once we switched to Clumio, our cloud backup process became much easier and faster. Most nights, the backup is completed 100%. Clumio offers better reporting services for our team, and their recovery is also more efficient and faster than our previous backup solutions.

We were looking to replace our backup software and started doing a POC. During the POC, we realized the benefits of Clumio, especially given our small team. We always look for solutions that are easily manageable and not cumbersome. Clumio offers an easy interface, is simple to set up, and is easy to maintain. It provides a way to get daily reports directly from the software.

Clumio has a straightforward setup; it involves deploying an OVF agent and connecting it to the cloud. Once connected, it begins backing up to the cloud. You can easily go to the cloud console and specify which servers need backups, and it starts the process. Different policies can be defined and assigned to servers, making the process much easier. Clumio also sends daily report emails, so every morning, we receive a report detailing what was successfully backed up and what failed.

Their support is also good. If a backup fails twice, they proactively open a ticket and contact to resolve the issue.

It is easy to configure and set up, and the recovery is much slimmer, easier, and faster.

They need to improve their SQL backup services and are planning to enhance their SQL recovery options, allowing users to recover from a backup at the table or even the row level.

I have been using Clumio for six to seven years.

It never crashed.

I rate the solution’s stability a ten out of ten.

You have to deploy more agents to scale wherever you want.

The support is good. Sometimes, the backup fails on a couple of servers. They usually open a ticket themselves and notify us.

Positive

Before, we had a Symantec. It was agent-based, requiring the setup of agents on new servers, which made the backup process slow and unable to cover our entire three data centers. In contrast, Clumio operates on the cloud, making it easy to cover all three data centers and allowing management from a single point. Symantec was a tape backup system that required personnel to change the tapes in the data center. With Clumio Cloud, backups are done in the cloud, eliminating the need for manual intervention. Additionally, Clumio is more cost-effective than other solutions.

Zerto has never advertised itself as a backup software, and it's not primarily for backup. It is more designed for disaster recovery purposes. While you can use it for backup, that’s not its primary function. In some cases, Zerto offers an RTO of less than five seconds, making it ideal for recovery and failover scenarios, enabling you to have entire production systems on a different data center, test your disaster recovery sites, and perform similar tasks. Clumio is not designed for all the disaster recovery functionalities like Zerto.

The initial setup is straightforward and takes around a day to complete. You can deploy an OVF on VMware as a virtual appliance. Once you download it, the virtual appliance will automatically connect to the cloud. Then, you go to the cloud and allow the connection. You need to set up a key or something similar. You have to set up a key, and you're done.

We did it by ourselves—we never needed anybody. The POC was easier to set up, and we moved from one to the other quickly.

Clumio doesn't require any maintenance.

Overall, I rate the solution an eight out of ten.

I use the product for air-gapped, off-premises backups.

It has improved our disaster recovery footprint. Previously, backups were only stored on premises. Having an offsite backup improves our reliability and security.

Policies are a valuable feature. I can create standard policies for instances and databases to enforce our company's information security policy. Using tags in AWS, I can add the desired tag for a policy and achieve compliance.

A UI refresh is always nice.

I have been using the solution for four years.

We have been using Clumio for four years. Before that, we used AWS Backup and Snapshots.

The cost model is better now with Pay-as-you-go. I was not a fan of the buy-up-front model due to the scaling of data size.

I did not consider alternate solutions, as I had an internal Clumio representative relationship from a prior company.

I hope CommVault continues to improve the product and keeps the pricing competitive.