What is our primary use case?
We manage Veeam for our customers. We are involved as partners and implementers between customers. We are not directly engaged with the vendors, but we provide services to our customers.
Therefore, the use cases vary. For hybrid cloud data, the use case depends on the client's specific requirements. It primarily revolves around Business Continuity and Disaster Recovery (BCDR).
We secure their data using Veeam backups stored offsite in the cloud or on-premises storage, leveraging the safest options available.
We also enable redundancy features like RAID (Redundant Array of Independent Disks) and implement encryption. For encryption, Veeam offers three levels with the option for customer-managed encryption at the host level. This approach gives customers granular control over their data security.
How has it helped my organization?
With native backups, I can perform a restore in under an hour, especially if it's the last backup. I can also directly mount the data on the server. But when it comes to service cases, I would choose Veeam Data Platform over Commvault because restoring from Commvault can be time-consuming due to filtering tasks. Veeam Data Platform, on the other hand, offers a much simpler and faster restore process without the need for a hot channel.
So, the usability of Veeam Data Platform has impacted our clients' IT teams' productivity.
What needs improvement?
With Azure backups, for example, I can only configure three policies and trigger them only three times a day. There's no such adaptive scheduling in Azure. Also, if I have multiple folders, I can't configure different policies for each one in Azure.
Commvault, on the other hand, allows for this kind of flexibility. So, Commvault's adaptive mode seems better suited for cloud-native environments compared to Veeam. Like, Commvault is more adaptive than Veeam Data Platform.
For the first thing, I would like to see the support for third-party data. Like, Oracle database. In Azure, you don't have release support for custom databases, like Oracle or other data. We cannot directly integrate with Azure Backup. There is only hardly any support for SQL and SAP HANA. That's a key area of improvement for Microsoft because we do manage all the databases, libraries, SAP libraries, and Oracle databases. And going with the latest features, So I feel Microsoft needs larger support there.
The other thing is the retention policies. So I can configure the VM backup directly. However, if I wanted to configure the application-level backup, I could only do it on Windows, but not on Linux. But if I see Commvault, I can do it for any of the machines, even if the customer supports Commvault. But Azure has limited support, so even OS compatibility. It supports Windows and some flavors of Linux.
For how long have I used the solution?
It's been more than two years.
Buyer's Guide
Veeam Data Platform
December 2025
Learn what your peers think about Veeam Data Platform. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
879,259 professionals have used our research since 2012.
What do I think about the stability of the solution?
It is a stable product. We didn't find any challenges with stability. I would rate the stability a nine out of ten.
If it went down, it should be the seasonal outage. That was the only problem. If the complete region goes down, that's when the Veeam Data Platform service goes down. And even there, there were options that we could configure on a high level based on the recovery point objective.
What do I think about the scalability of the solution?
It is a truly scalable solution. I would rate the scalability an eight out of ten because there are only a few VMs and flavors of OS supported.
We handle enterprise-level customers like the top ten banking customers in the Middle East. We maintain all of them.
How are customer service and support?
The customer service and support were frequently available for calls, and I could discuss them openly and resolve the issues if I may. So there is no problem with technical support.
They will pitch in for us because we handle enterprise customers. That's another key point to evaluate for us. So the support was really good. So, even if there were any minor bugs in production, they would sort them out in a couple of days or a month. They will come back to us with the proper documentation and solution.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I've been working with Azure for more than four years. We actually prefer the native Microsoft Azure Backup service for file and folder backups. Cloud-native solutions are generally better suited for hybrid environments because we avoid the complexity of managing multiple components.
We start with Azure Arc servers to integrate Azure services on-premises, install and configure Arc to Azure, enable backups, and fully utilize Azure as a service.
For Commvault, we only need a plugin. It's a simple task whether it's an on-premises model or not. Now, we're adopting Commvault as a service, which offers more flexibility compared to cloud-native solutions, especially for hybrid environments.
In our case, even for hybrid environments with Hyper-V, VMware, or physical servers, Commvault works well. You simply install an agent, configure storage, and define backup configurations.
Cloud-native solutions often require more steps, like connecting all servers and services to Azure before using native backup features.
As a Cloud Solution Provider (CSP), we have a footprint in all major clouds, including Azure, AWS, GCP, Oracle Cloud, IBM, and middleware services.
We prefer using Commvault and Veeam Backup for all types of backups, including snapshot and file/folder levels.
We switch between different solutions based on our portfolio or our customers' needs.
How was the initial setup?
Setting up for my case was completely different. There were some product-level bugs that caused a lot of challenges for Veeam Data Platform. So, it took a while, but we are up and running right now.
It was kind of difficult at first. But, once you contact support and get them involved, then there is no hard filing and maintaining it. It's easy to maintain and easy to rely on because it's cloud-native. So, no security questions will be raised.
Once all the communication is in place, it's hardly an hour's job. So, it's all about maintaining the prerequisites that match the current setup, and as per the documentation, I could configure it. It's just a two-step process.
So, there is no hard challenge in configuring it. But it will take time because it has to register to the world and maintain security. You need to log in, integrate with the recovery services vault, and configure the policy.
So it will take some time. It will take at least an hour, but you can bring up the service, and you can rely on it for the next few years.
What about the implementation team?
We implement solutions for customers hosted in cloud platforms.
What's my experience with pricing, setup cost, and licensing?
If you are going with the premium service with all the features, it can be a bit high. So I would go for four. Because when you compare it with third-party tools, like Commvault or Veeam itself, they are a bit cheaper, and we can rely on them for pricing.
Commvault is a perpetual license service, so once you have the license, it's all about the storage that you use.
But Veeam Data Platform, it's pay-as-you-go. So, the more options you choose, the more consumption you have in monthly billing.
So, it's too high for all the services that we get, at least from the backup standpoint.
I would rate the pricing model an eight out of ten, where zero is the cheapest and ten is the most expensive.
Which other solutions did I evaluate?
We evaluated Azure and Commvault for our use cases. We ultimately chose Commvault because it offered more flexibility for data protection and manipulation.
What other advice do I have?
My recommendation would depend on the business scenario. For example, if you are a banking client, I would prefer going for cloud-native because it all depends on the security and the compliance that the customer has to maintain.
Going for third-party tools can be difficult and complex, making things more complicated. But going for cloud-native reduces the security effort, so it's easier to manage compliance.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner