Veeam Data Platform Reviews

Veeam takes our installation and server backups, then writes them on a disk and the tape backup. After that, it replicates the backups to another recovery site. IT is the only department that uses Veeam directly. It has three to five people.  

I like all of Veeam's features, but the most important ones are the tape backups and replication. Those are the two options available for us, and it's enough for our needs.

I've been using Veeam for more than 10 years

Veeam is stable.

Veeam is scalable. 

I sometimes contact Veeam for some adjustments or updates. They get back to me in a reasonable time. I've also asked them about the availability of particular features or questions about deploying the solution. There are different solutions for freeware and enterprise deployment. Enterprise deployment has various features available to end-users, so I've asked if these solutions are available to us. 

I worked with NetBackup at my previous company, but that was more than eight years ago.

Veeam is easy to install and deploy. 

We pay a yearly license for support and upgrades. I haven't researched the price of any other solutions, so I can't say whether it is expensive or cheap relative to others. It is affordable enough for me.

In the past, Veeam had a host-based license, but now it will be part of Microsoft's core license. I don't like this licensing model. Host-based licensing is better for my system. Maybe so other organizations prefer the core-based.

I rate Veeam Backup and Replication eight out of 10. I recommend Veeam. It is simple and easy to use.

We are using Veeam Backup Replication for daily backups and disaster recovery.

The most valuable features of Veeam Backup Replication are ease of use,  dashboards, and reporting.

The replicating from Veeam Backup Replication to Azure cloud could be improved. Situation:seeding large amounts of data from veeam to azure. I opened up a ticket because there is no clear cut documentation (Steps) on how to do so. they have pieces of the process in different articles with different headings. i opened up a ticket and it was like i was the first customer to ask for this. seeding is when you have slow to medium bandwidth and need to offload the data locally then send it to azure. with some help from support i had to put together my own notes from alot of trial and error from ordering the wrong type of box from azure to completing the process once i actually got the data uploaded to azure. i just feel like they didn't do good job in documenting how to seed data to azure properly

I have been using Veeam Backup Replication for a year and a half.

Veeam Backup Replication is stable.

The scalability was good, it met what was in the marketing of the solution.

The support from Veeam Backup Replication has been very good, it was excellent.

The initial setup was straightforward.

I would advise others the solution is straightforward. We used a third-party demo that was simple for the services. The overall support and services are good. However, the Azure integration difficulties for cloud replication need to be fine-tuned in terms of knowledge-based.

I rate Veeam Backup Replication a nine out of ten.

The use cases vary because we work for several clients and deploy different solutions for each. Some of our customers have upwards of 5,000 users. But generally speaking, we use Veeam for copying databases and storage. 

We use Veeam, Veritas, or Commvault for simple security and second-level storage. We might use Oracle and different kinds of databases for replication and database storage with built-in replication. 

All our customers would like a cheaper license and more flexible deployment

We've been using Veeam for four or five years. 

Veeam is highly scalable. In one scenario, we started with 2,000 users and scaled up to 24,000.

I have a team of consultants who provide support, and we are Veeam-certified too, but we sometimes need help with certain customers and deployments. It's very complex, and we need more time than we expect, but it's working. 

The optimized installation takes two and a half hours, and then the total deployment takes more than a month and a half. 

Customers would rather have a standard license than a subscription because they prefer an OPEX solution over a CAPEX. They prefer to buy the solution with the solution and support for five or 10 years. 

I rate Veeam nine out of 10. Veeam is one of the best solutions. We are using it with customers that have 13 seats and 1,500 servers with varying technologies, including Windows and Linux databases, different interfaces, Citrix solutions, etc. We've been recommending it to our customers for the last two years. 

We primarily use the solution for backups in the virtualization area. They are experts in virtualization. For a lot of use cases, the customer doesn't have a backup in their virtualization for VMware HyperV or Nutanix. We are using Veeam to back up their virtualization. 

They are the second-best backup after Veritas. 

Veeam is easy to set up and they have a simple UI for users to set up and administer the Veeam console.  

Veeam has low pricing. They are great for a smaller market or smaller business all the way through to enterprise-sized companies. It's scalable. In Indonesia, maybe two of our telco companies use Veeam and they have a lot of the market in Indonesia.

The solution's initial setup is easy.

It's a stable solution.

They need to improve their technical side. They don't have a lot of compatibility with Solar HP-UX, IX, or SAP. They still need to have a lot of improvement in that area.

They need to make their Office 365 backup is included in one console with the backup replication. It will be easier that way and place it in line with the Veritas NetBackup offering.

We have found the product to be quite stable. It's not buggy. There aren't glitches. It's reliable. It doesn't crash or freeze. 

The product can scale well. It's great for small businesses to larger enterprises. 

Since Veeam is easy to use and easy to set up, we don't have a lot of problems. Therefore, we don't have a lot of experience with their support. We've never had a reason to contact them. Due to this, I can's speak to how helpful or responsive they are. 

I am familiar with Veritas as well.

The solution is straightforward and simple to set up. It's not a complex or difficult process. A company shouldn't have any issues implementing it. 

The pricing is very good. They are very affordable, even for smaller businesses.

We are a Veeam partner. We're partners with a variety of organizations.

We use various deployment models, including public and private cloud, on-premises, and hybrid setups. 

I would rate the solution at an eight out of ten. We are quite pleased with its capabilities. 

We use Veeam Backup for setting up backups, according to our directives and policies, such as encryption and high contention policies. We then do the backup to Wasabi or any other cloud area. We use these directives to configure the backups. 

This solution is deployed on-premises. 

Veeam Backup has many valuable features and every feature is different. I have created backups for file-level backup, VMware or hypervisor virtual machines, physical machines, and workstations as well. Every time, I learn something new. 

I think Veeam needs to improve the file installation process, as well as more technical things like snapping feature issues. Sometimes during backup, when it's taking the scan snaps on the ESXi, it started and didn't remove the snapshot from there, which consumed storage on the EXSi. It could be improved with more technical depth. 

The response time for Veeam's technical support could also be improved. 

I have been working with Veeam Backup for about four to five years. 

Veeam Backup is stable. There is an issue, where if you lost the VBR machine that was taking the backups, it's a long process to reconfigure the VBR, attach the repositories with the new VBR machine, and restore things. It is a difficult process, but with Datto, they also contain the backup in the cloud—you can manage your cloud to the portal and then you can store the machines on their cloud. 

Maintenance is required from time to time, basically whenever you're upgrading your servers, workstations, or endpoint. According to that, you might need to improve your version of Veeam. I started working with VBR versions 8 and 9, and then upgraded to 10, and then 11. Different restoration features and backup features are available in different versions. 

This solution is easy to scale. You can scale it up—you just need to give it a repository and then assign the backup to those repositories. It is a little difficult moving the old backup change from one repository to another, and is not as simple as with Datto. Datto has a very simple process and when you continue with the Datto machine with a higher amount of space, they always have their pool containing all the previous backups. They also move all those backups to new storage, so their process is very easy, whereas it's a little difficult with Veeam. 

Veeam Backup is mostly suitable for small organizations. For large organizations, I recommend Datto because they're more reliable, in terms of the restoration process. Small organizations may have time to recover things or provide a solution. Basically, it depends on the queue scalability or the RPU and RTO, so you must plan the solution according to that. 

I'm satisfied with Veeam's technical support. Normally, we are able to solve issues ourselves, but if we have any issues that are unresolvable and we can't find a solution on the internet or on forums, then we contact the support team. 

They take a little bit longer to resolve issues because they often have call loads on the support, so you either need to wait one or two hours for someone to call you back or you need to wait on the phone. The other support teams are busy on other calls, so you have to wait for them or leave your number. 

In one scenario, different issues were occurring and we discussed them with the support team. I was working on license utilization of all the VBRs, which were integrated with my Veeam Service Provider Console. We identified that the license utilization was not generating properly through the Veeam Service Provider Console and it also wasn't integrating through to my PSA integration tools. So, he worked with me and they improved the database tables to get the proper report from the VBR. From time to time, these issues are identified and we resolve them. 

If you are installing it for the first time, you might feel that it's a little bit complex. I think that if you are using a backup product, it's easier to configure the backup through Datto, Acronis' business solutions, or Synology NAS. To me, those are the easiest ways to configure the backups. 

The timeframe for deployment depends on the client environment: how many servers, how many backups need to be configured, the size of the backups, etc. When you configure the backup, initially, you need to take the full backups in, which takes time if the backup size is too big and you need to configure it one by one. So, it depends on the infrastructure, bandwidth, and the size of the backup. 

We implemented this solution through an in-house team. 

Veeam products are less expensive than other products. The licensing costs are low and they're pretty affordable. 

I'm using the Veeam Service Provider Console for centralized management of all VBR, and I created the cloud VBR for taking backups off configuration and managing them through the Veeam Service Provider Console.

I also use Datto, which I recommend for large organizations, because they are more reliable, in terms of the restoration process. You can make a machine available for a client on the Datto machine as well as in the cloud. It also takes a shorter amount of time for recovery, whereas on Veeam, you must have additional space and additional hardware available to restore the full machine. They also have a limitation of file level storage. For example, if you are running VBR on a machine and restoring the file, you have two options: you can either restore the files on the original location first, or you can restore the file on the same VR machine. If you lost your original location and you're restoring files, then you must restore the files on one of those two locations because you can't store files on network parts or any external storage. Small organizations may have time to recover things or provide a solution. 

I rate Veeam Backup a seven out of ten. 

I would recommend Veeam Backup, especially for small businesses. Normally, small business owners have a small budget, so they need to configure Veeam, whereas large organizations have large budgets, so they go to Datto. Small businesses can deploy Veeam if they have four or five backups. Otherwise, I would recommend Datto if they can afford it. 

It is for backup and disaster recovery as a service. It is deployed in our data center, and then we sell the service to our customers.

The granular restoration that it provides for a business application is most valuable. For example, for Exchange, we can restore a single mailbox or email. We can also do SQL Server restoration and bare-metal recovery for operating systems. 

Replication features are very useful for customers. They can recover the services and move from one data center to another.

Veeam currently lacks features for backing up to network-attached storage. Veeam Backup & Replication agents do not support S3 storage. Only Veeam Backup & Replication server supports S3 storage. 

We have been using this solution for about five years.

Its stability is good. I would rate it an eight out of 10 in terms of stability.

It scales well. I would rate it an eight out of 10 in terms of scalability.

In our infrastructure, we have hundreds of users. Our customers are from many markets, but its users are from their IT department.

I would rate them an eight out of 10.

It is not complex. It is straightforward. We can deploy it to our customers in about 1 to 2 hours or 1 to 2 days. It depends on a customer's infrastructure.

We deploy it ourselves, and we only use support when we have technical issues with the product. We have three engineers for deployment.

It is very difficult to calculate because it is a backup solution. It is not a business service, which makes it very difficult to calculate the ROI.

We are fine with its pricing policy. 

We provide service for our customers, and the licensing is on a monthly basis. They get licenses, computer resources, and our support. Everything is included in a single price.

I would advise others to test this product before buying it. There are many backup products and services, and they have different features and functionalities. We provide our customers a 30-days trial period to test the product for free, and then they can agree or not agree to use this product.

I would rate it an eight out of 10.

We primarily use Veeam as a backup system, so for backup operations. Every company needs to have backups and restoration, and cannot live without it. We have ransomware, system failure, and a lot of problems facing us, so we need backups for the emailing systems, database, Hypervisor, and VMs. 

One of the most valuable features of Veeam is that the restoration is easy and reliable. 

The ease of use could be improved, but I don't have a very deep amount of experience in Veeam, so it's difficult to say what could be improved. 

I have been using Veeam for a couple of years.

This solution is stable, and the restoration of Veeam is easy and reliable. 

A partner or mine has contacted technical support many times. He was very satisfied and recommended their support team. 

I have also tried Veritas Backup Exec, which is more difficult to use. 

It takes about two hours to install and implement this solution and to start backing up data. The operation of backups depends on the customer's data, so the timeframe will depend based on that data. 

For deployment and maintenance, we have one person for administration and restoration and the IT manager for managing the system. 

In my organization, users use it centralized, and it works for the servers and operates silently. No one can pause or refuse the backup operation. We implemented it like this for all customers, so that it backs up to the server and works without user involvement.

We implemented this solution through an in-house team. 

We pay for a license to use this solution, and we recommend that our customers pay for a license and a renewal license. 

I rate Veeam Backup a nine out of ten, and I would recommend it to others. 

We primarily use the solution as a backup.

From our view, from HPE, the engineering teams of HPE and Veeam are working together, and we are developing some products. There is a tight integration between Veeam's product, Veeam Backup and Recovery, and HPE storage products.

This is, I can say, a win-win approach. Most of the features that we can use with HPE products are directly integrated with the Veeam. This is very important for the customers to have only one pane of glass to manage the backups and also use the HPE products for the backups.

One thing that is always requested by the customers is to have new functionalities integrated very rapidly into the product. There are always new features that we must integrate. The market is pushing very hard to have new functionalities.

Right now, for example, there is a very high demand for protection against ransomware, and we want to integrate the data immutability features in Veeam and integration with HPE products.

For example, in the case of Veeam, they have many other partners. They have Dell. They have Pure Storage. They have NetApp also. For the engineering of Veeam, it's not very easy to integrate the features of all the third-party partners. I can say that the relationship between Veeam and HPE is very strong. We are working on 10 projects. Half of the backup projects that we have with Veeam most of the time.

There are certain solutions, such as Rubrik and Cohesity, that are little by little, taking market share. Veeam needs to be more aggressive to keep their dominance in the space.

I'm in the storage business for more than 20 years. From the beginning, I used to work with VM backups. It's one of the major projects that I handle on the customer side. I used to work with Veeam as it is the leader on the market for VM backups. I used to work with Veeam.

It's a very nice product. The feedback from the customers is that most of the time, it's very good. We install it, and that's all. It works. It's a great product. The only thing is when we have very important environments, I can say it's a little bit complex.

It's so easy to set up that sometimes the breadth of the product is not very well used by the customers, as there are a lot of features inside. Unfortunately, the customers don't have enough time to see all the features that they can use to improve their backups.

In the data center, with HPE, they have some entities in Veeam. We have gateways. We have proxies. As soon as we have some scalability, to size these entities is not very easy. All the time we must work with a Veeam architect to set up the right environment. It's not so easy regarding scalability. It's mostly for large enterprises. For 80-90% of customers, it's very easy. However, for the 20 remaining percent, it's not very easy. It's not so easy, as there are so many features in Veeam that sometimes they are not very well used.

Two or three years ago, we had an important escalation regarding the Veeam environment. It's not very easy to have access to level three. That said, for 90-95% of the cases, it's okay. Sometimes, when we have a real problem, it's not very good, however, that's a general truth in the IT market.

We have a direct relationship with Veeam pre-sales. Most of the time, when we have a very tough escalation, we can make a request to Veeam directly in France, and they can help us in a very efficient way. We have a very strong partnership.

I've worked with a variety of solutions.

Veeam is very, very good when we have a virtualized environment. It's a major part of the virtualized environment. However, in the data center sometimes some other products like Commvault, for example, or NetBackup, have more features than Veeam. When we have very important environments with bare-metal servers, Commvault is a better solution compared to Veeam in some situations.

The difficulty of the initial setup depends. For the smaller environments, it's straightforward. It's very easy to set up an environment with one ESX cluster and one backup appliance to back up 100 VMs, for example, 100 or 200 VMs.

However, when we are in the data center, little by little, what we want is it to be present, to be an enterprise product, and when we are in the data center, when we have a lot of environments, bare-metal environments, virtualized environments, specific applications to back up, I can say that it's not so easy.

You must have the expertise to set up this kind of environment. The consulting phase and the preparation phase and the setup phase are very important. As soon as the environment is set up, changing something is not so easy. Many times we had to change the architecture after the initial setup as all the aspects were not been very well optimized for the environment of the customers.

There is not a very easy answer, as it is not only for Veeam. A backup project is a complex project due to the fact that we have some interaction with all the entities of our customers. We must have some workshops with all these entities to have the right solution to propose and to set up.

The licensing of Veeam sometimes is quite complicated, even if they have improved a lot the way that the licensing is working currently.

I'm a consultant. 

We're an integrator. I'm working for HPE. We are integrating only our products. Sometimes we integrate third-party products too, however, most of the time, we try to use our products. That said, it's impossible for my company to be the leader in all the environments. For example, for the backup,s we have some technology, some preferred partners, and Veeam and Commvault are the main partners right now for the backups.

I'd advise potential new users to analyze exactly what they want to do before implementing the solution as it's always better to know exactly what they want to do.

To set up the environment is very easy, however, you must anticipate future problems and think about scalability. You also need to think about how you are going to add more power to the environment. Everyone needs to prepare for the coming years. 

Right now, there are new demands on the market, and Veeam as a leader in backup software must anticipate these needs. Right now, we have some demands regarding the backups of objects, as, little by little, we have a lot of customers using objects as primary storage. 

In terms of anticipating such kinds of demands, Veeam is one of the leaders of the market.

I'd rate the solution at an eight out of ten. It's a great solution.