Veeam Data Platform Reviews

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. 

The solution is based on the IAF solutions that are specific for moving the data centers that we have to the cloud. This is the main tension for us right now. We are investing in some past solutions, however, we're not using them yet. There are some tests, some small tests, however, we are moving IAF solutions in order to move our data centers.

We like Veeam as it is the kind of backup that has basic snapshots. It's very useful for us as we have a lot of virtual servers. This is the most impressive thing that we see. 

There are some special features from Veeam. They have the replication and the kind of backup that we can use. We have a very strong solution in the network. Due to the fact that we have several internal DMS's, we needed to make a special design. Veeam adapted to that. That's why we choose it. With all the solutions, it was not possible to use the actual network structure that we had. Veeam made it possible.

The solution is stable and the performance is good.

The product can scale. 

For us, it's important that the products can be adapted to different network scenarios. This is the biggest problem. The issues that we had when we selected the products were due to the specifics on the network from a security point of view. Security for us is the most important feature that we need to work with. THey need to ensure that it's possible to secure the network.

The initial setup is complex. 

We use several proxies, reverse proxies, due to our needs. It's not so common. There's not too much information and it's not so useful. They could develop it more and they could market it better. Not many users have this scenario. The reverse proxy, for us, was an important piece to implement. If a user has a good view of the reverse proxying during the implementation, it's better.

The solution has been implemented in the company for about one year at this point. 

The solution is very stable. We needed to buy the biggest server to accommodate it. The requirements were very high. That's why we started late when they decided to use it. However, after we followed the recommendations and followed the certification of equipment servers and storage that we needed, it's okay. Now we find it's very stable.

The scalability is very good. Everybody uses it. In general, we have about 125,000 people using it.

We likely will increase usage in the future. 

We needed some technical support at the start. It was good. Here in Brazil, they are from Brazil and they have helped us too in the design phase. That said, the product is very good. We don't need exactly support for any issue that we found. We've only needed some help for the implementation, the start of the design.

In terms of the implementation, it's still being rolled out. It's very big and there is a very sparse structure that we have. It's global. It will take about two years for it to be completely implemented, due to the places and locations we need to implement it. We need to make and design for each place as it is not standard. That's why it takes a long time. We prefer to take it in parts to be careful with the implementation, in order to see if it's really what we want. Therefore, for us, the setup is quite complex.

The results have been good so far. People are liking it very much. That said, we still have some designs to do for other places that we have implemented.

Due to the implementation, we are doing, there are about 50 people working on the deployment. This is just an estimation. It's quite a large project.

We pay the licensing fees on a yearly basis. There may be a few additional costs, however, I cannot speak to those exactly. Our technical team might have a better idea of what is involved in terms of licensing arrangements. 

We tried the base license, however, it's my understanding that it wasn't enough and we needed a bit more. 

We are a Veeam partner.

In terms of types of deployments used, at this time it's been working more on-premises, however, we have intentions to use the cloud. We are moving several loads to the cloud. 

I would advise new users that the design is the most important piece. There are several options in the ways that you can implement it. My recommendation is to look at the strategy. Networking becomes very important. Having a good design at the outset makes things easier. 

I'd rate the solution at a nine out of ten.

Our primary use cases for Veeam Backup & Replication are backing up to the cloud, backing up to a couple of deduplication appliances, and backing up to local disk - compressed to disk.

Veeam Backup & Replication is far more dynamic as far as being able to generate backup jobs. We used to use a product called NetWorker, and at the time the version of NetWorker we had would not back up to the cloud. I think it does now, but we're not using it anymore. But at the time, NetWorker was fairly new and it was just a tape backing up the disc. So Veeam is far better dealing with virtual environments and the cloud as targets. The capability with Veeam is just there.

Veeam Backup & Replication works. It integrates very well with VMware, but not so well with Nutanix, but that's common, I understand. I have both VMware and Nutanix virtual environments and I'm backing up through the same Veeam services. I have proxies running on both environments. Like I said, integration with VMware is excellent with very granular recovery while with the Nutanix environment it is not as intuitive, not as readily available.

In terms of what could be improved, when creating a backup job with Veeam, you can create a daily backup, but it doesn't do it within that job. It does not give you the ability to also set the terms for monthly and/or weekly backups. It has to be a separate job. It gets clunky to manage the timeframes where you don't want a daily to run on this day and creating weeklies. And you don't want a daily to run on this day doing monthlies. That is hard to deal with. It would be really nice if you could do it through a single command line or a single interface.

It is called a father son, or grandfather, type backup structure. The retention periods are not consistent or not available for different retention periods within that job. Retention periods being daily, weekly, monthly.

As for what I would like to see in future releases, just the integration to other virtual environments. In our case, the Nutanix environment is incomplete with the enterprise manager recovery tools part of it. That's where it is incomplete on the Nutanix side as well on the ESX. On the VMware side, the ability to set your retention policy within a job over multiple periods would be really nice if that was doable.

I have been using Veeam Backup & Replication for well over a year, probably 18 months, maybe even close to two years.

The product relies fairly greatly on the implementations of the storage vendors. For example, we were using large storage in AWS and it was using Microsoft. It's the format - ReFS, the recovery, the storage, the dis format, the volume formatting. We had a serious failure and lost six 30 terabyte ReFS volumes in AWS and lost nine 15 terabyte ReFS volumes on our local storage. I was able to recover the local storage in a little over two months. To recover the AWS storage of our volumes we calculated would have taken between six months to a year and probably cost us several tens of thousands of dollars.

So our volumes are still sitting in recoverable AWS in the case where if we actually have to recover something it's doable at significant cost. But we don't use ReFS storage anymore.

I'm not big. We have 200 employees and maybe 50 or 60 or 70 VM's, something like that. We have a data domain appliance that we rent space on that is offsite. We have an extra grade appliance and I have a bunch of CADA disks on a net app for just local storage. If that's scalable, I don't know. My understanding is that I can create more, but everything is local. So I don't have to have remote backup servers. But I understand that with my license I can create remote backup servers, as well.

That sounds like it's pretty straightforward. You link it and you can move backups from one site to another and then recover them off that other site. From what I've read, it sounds amazing, but from what I've done, I've never had to go into any great remote control, remote access or remote sites. So I don't know as far as the scalability goes. It sounds like it can scale up the ying yang. The one thing that I'm aware of though, is that when you're doing the backup, when you're scaling, you wind up with tears, because you have one server backing up a set of VM's, or an environment. And you have another server backing up another environment or another set of VM's.

If you lose one backup server it is able to catalog those backups from another server. I know you can catalog those backups to another server to recover. So it's dynamic. I've had to do that. I've had to build a new server and then recover the catalogs and recover data. It is powerful, it is capable. I like it.

In terms of direct users, it is me and three others that have gotten their fingers into it a little bit by the documentation that I've written on how to do something step by step. But there is really only me managing the system.

We are using this product extensively now. 

From the time that we installed it until now, we had to switch from CPU licenses to what they call UL, Universal Licensing. Because CPU licensing was only available on a VMware infrastructure and when we entered do our Nutanix infrastructure, we had to change the licensing model. There was a small cost to doing that because of the way it's licensed. We have not had to increase our license count yet. I will be shortly implementing another version of the Veeam. I think it's a very simple license, it's the five user license. It's in the VLU, but it's not the enterprise version of it, for our computer science department. They will be managing their backups with Veeam and a technician who I will be training.

That ReFS issue was one of the things that I had with technical support. For the most part they have been very responsive. They have been helpful when it's actually a Veeam issue. With the ReFS thing, they couldn't do anything about that and they referred me to Microsoft, which was a fricking waste of time. I'm so ticked with Microsoft.

We used to use NetWorker for 10 or 12 years.

We made the switch because of the virtualization and cloud access as well as disc storage on the version of NetWorker that we were running. NetWorker requires a physical appliance and the upgrades to NetWorker were cumbersome. The next generation of NetWorker, if we had stayed, would have required a rebuild of our hardware, which we've done once and was a pain in the backside. At that point, I don't think we could have run NetWorker because it wants to go to talk directly to devices and manage devices at a hardware level. So you can't virtualize the connections. So our NetWorker product had to reside on a physical machine.

I don't know if that has changed since we haven't used NetWorker for probably three - four years. We haven't done any upgrades in four years. So the move to Veeam or Commvault, which was the two that we were looking at, was primarily because we had local vendor support for both products. The move to Veeam was well priced, Commvault was out to lunch as far as dollars and cents. We are a fairly small shop and the pricing was just outrageous for Commvault 300 virtual machines. 

Veeam natively lives in a virtual environment. NetWorker couldn't. We also used to use a Norton product. I have forgotten the name of it - it starts with an S.

Those were retired when we started using Veeam. It has been four years since any of those were active, but those were for our remote sites. They only backed up the tape. We didn't explore Backup Exec in a virtual situation. Just didn't even look at it. I don't know if that was a mistake. I don't think so. Like I said Veeam, works really well. I am very pleased.

The documentation to set it up was great. I think we were up and running in about 30 minutes. That was to set up the backup server. Then there is building other services - the proxies, the repository manager, the enterprise manager for managing backups and recoveries. But to set up the backup server itself was super easy.

We just did it in house.

My advice to anyone considering Veeam Backup & Replication, is, like anything, to build a test site - do it on a test environment. Don't mess with your live system right off the bat, play with it, get familiar with it. It took me about about four, five or six weeks before I felt reasonably comfortable and built up in our production environment and the various servers. I started backing up and playing with a couple of Veeams that were smaller, and not backed up to the NetWorker, but I was backing them up and looking at how I could do recoveries. Eventually, I could do a full Veeam recovery and I could move it to another site and recover it, and all that sort of thing. I watched over time how retention worked. During that time I was asking questions of the Veeam technical support, too. They were very responsive.

So do it in a test environment if you don't have any training. I read online documents and went through a free Veeam school online, a bunch of documents, and there were a couple of YouTube type tutorials. I did a lot of that sort of thing as well. But it was all done ad hoc from work, I didn't go and do any formal train. So build the test environment and play.

On a scale of one to ten, I would give Veeam Backup & Replication an eight. It's got room for improvement.

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.

I'm the system admin, and I'm taking care of backups and every job in Veeam Backup. We have the AIX machines and we are deploying the AIX machine; we are doing the backup and trying to restrain the AIX on them.

It's very customer-friendly and user-friendly and we use it mostly to backup an issue. 

We have done a multiple-time restore on Veeam Backup and that is an awesome feature. It's a very critical system, we have to restore it and Veeam makes it easy to do so to protect our system.

Initially setting up the product is easy.

The solution has been quite stable. 

Technical support is good.

It supports the technology and it's actually more secure and has enhanced itself. Veeam is always making itself better in terms of functionality and features.

Part of the issue we've had is with the AIX backup. Currently, Veeam has issued version 2.0 for the AIX machine, however, it is not capable of taking the entire machine backup and restoring at the one side. It is only taking the backup of the partitions only. There is a limitation there right now. I'd suggest they improve the functionality in the Veeam Backup agent so that it will take an entire machine backup. That would be more beneficial for the official system for the AIX's.

The stability for AIX machines could be better.

Veeam Backup also needs to be possible in Azure, so that if something goes down Veeam can take care of everything. Our local vendor in India for the Azure environment has found out there is no availability for Azure for Veeam Backup and Replication. If there is an existing Veeam option that supports the Azure environment, they need to relay the message. It's not clear now and it appears there isn't one.

We'd love to see the solution offer more compression in the future to allow us to save more space. 

It's stable for the ESXi and other Linux and workstations they've established. In the case of the AIX machine that we are using, the stability needs to be improved.

The solution is totally scalable. That said, one thing I didn't get from local resources is that Veeam Backup cannot perform in the Azure environment. 

Technical support is good. It's awesome. Still, we can't get the right solution at the right time. If I'm asking about what ports need to be open for the Veeam Backup and Replication and they are just suggesting the link and just showing the port, it's not quite as helpful as we would hope. For example, what can do we to improve from this side? There needs to be more specificity in terms of the level of technical support we get when we have specific concerns. We would be grateful for this.

The setup process was really easy. I've done it so many times, actually and I am quite comfortable with the steps now. However, in the case of AIX, most users don't know about the AIX deployment. They are not seeing exactly what needs to be done. That part needs to be taken care of by Veeam directly.

I can't speak to the exact pricing, however, in our region, in South Asia, pricing is always a concern.

We tried Commvault also, however, it's not user-friendly and it's not as easy compared to Veeam. They have their own benefit, however, they simply are not user-friendly enough for us. Veeam is easier, and it's reassuring. We've saved money with Veeam as we've had to restore a few times now and we've saved so much data using it. That's why it's good. It's proven itself again and again.

We are customers and end-users of Veeam.

I'd rate the solution at a ten out of ten.

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. 

The primary use case is backup and replication. This solution is a backup, so it is used on-premises.

From my experience, Veeam is very good. Its interface is user-friendly. We can restore it whenever. It's not complicated. It's very easy to manage and administration is very easy.

Veeam should go for a different version of a hypervisor. For example, they are concentrating on Microsoft Hyper-V and on VMware. There are some virtualizations there, like AHV Nutanix. In that case, they need to rebuild application-wise. I checked with an AHV for my personal knowledge, and I couldn't find the same as in the VMware and Hyper-V. It's totally different. It opens with a different port.

They need to do some repository and improve the backup chain and logs. For example, sometimes we still need to call support for small things, and they're looking for the log. 

In this case, they need to give some training to the administrators. It should be easy. In this case, there are some knowledge bases. If you go to the Veeam site, you will see the knowledge bases, but there should be a little awareness. Administrator awareness should come up for that, like with the small issues and how you want to replicate. When you have some small issues, you should be able to go through it by yourself and solve the issue instead of opening the ticket and waiting for the engineers to troubleshoot.

It was scalable.

Technical support is amazing.

Veeam is totally different from Veritas when it comes to virtualization and virtual machines. For Veritas, we are just using the standalone, physical servers.

Veritas is good for a small environment. We are taking more backups in Veeam only, and we're only taking some backups in Veritas, which is like a physical server.

The cost is expensive. It will depend on how you are managing your environment, your requirements, and if you can easily manage a license. It's not that difficult, so you can manage it, but the cost is high, so you need to check directly with Veeam as well as the local partner so you can get the discount prices.

I would rate this solution 10 out of 10.

We use Veeam Backup Replication for data backup and replication.

We will upgrade to version 11 soon.

The most valuable features of Veeam Backup Replication are efficient backup and replication. Additionally, Veeam Backup Replication supports all products and vendors.

The solution could improve by having more user-friendly dashboards.

I have been using Veeam Backup Replication for approximately six years.

Veeam Backup Replication is highly stable.

I had a customer that has been in operation for two years without any critical issues.

We do not have plans to increase usage at this time. We use the basic version at this time. 

The scalability of the solution is good.

We have five people in my organization that use this solution and support 10 customers.

I am in Turkey and the support is very important for the customer but it should be improved.

We have used Commvault previously but the customers cannot use Commvault for backups and replication, it is not included on the Commvault backup software. 

Veeam Backup Replication allows both features.

The initial setup of Veeam Backup Replication was straightforward. Step by step, we did not have any problems.

We have five people for maintenance of Veeam Backup Replication.

The price of Veeam Backup Replication has been increasing their price and my customers are asking why. They have CPU-based licenses and a Universal License, the prices should be reduced.

I would advise others that want to implement this solution to check the Veeam website for documentation and follow the information all step by step on how to install it. Everything is available in the documentation about implementation. If someone follows the documentation they will not have a problem with the implementation.
 
I rate Veeam Backup & Replication a nine out of ten.