Veeam Data Platform Reviews

I have found the backup call feature very good.

I have found that the reporting could improve in its structure.

In an upcoming release, the remote site application, physical workload, and other application integration could improve.

I have been using the solution for approximately four years.

We have experienced some bugs that we reported to the Veeam team and most of the issues have been resolved. For example, we had an issue recovering a file that was 256 characters long which we were testing out. We resolved it by restoring the whole volume.

We are satisfied with the technical support.

We have also worked with Acronis, Commvault, and Veritas.

The initial setup is very simple.

The price of the solution could improve when comparing it to competitors. The market is very competitive and they should have some discounts or special offers.

We have evaluated Commvault and they have a very fantastic rating compared to Veeam Replication. 

I rate Veeam Backup Replication an eight out of ten.

It is used for the virtual environment, which includes virtual Windows servers being on ESX or Hyper-V. It is also used for databases and Exchange in these environments.

We are using version 10. The latest version is 11, but we are not eager to use that because it came out only two weeks ago, and that is not enough for us.

Its ease of use for restore is really good. For Exchange, the Exchange Active Directory is great.

The implementation of the features can be improved. Currently, there is no segregation of duty. Normally, any backup software or client service software is implemented in a way where one person is responsible for the implementation of the server, and one is responsible for the client, but Veeam Backup & Replication is not implemented in that way. Therefore, restores don't work like that. The backup guys have to do the restores, which is not a good thing.

Its pricing should also be improved. It is quite expensive.

I have been using this solution for more than 12 months.

It is quite stable, but you cannot compare it to IBM Spectrum Protect. IBM Spectrum Protect is more stable than Veeam.

It is quite scalable. We are planning to increase its usage. Its scalability is linear. You have more and more virtual systems and fewer physical systems. IBM Spectrum Protect is more for physical systems, and Veeam is for virtual systems.

Their technical support is great. I would rate them a ten out of ten.

It is complex. You certainly need some external guidance for this. The deployment itself is not a big thing. It is the creation of the architecture that is complex. You have to create an architecture that fits your needs.

We can do it ourselves.

Veeam is quite expensive. There are no additional costs to the licensing fees. IBM Spectrum Protect is also expensive. 

They should improve its pricing. They raise the price every time there is an increase in the features of the product. They should think twice about that.

We had a look around, but we decided on Veeam.

I would rate Veeam Backup & Replication an eight out of ten.

Our company is an integrator, and we are offering the Veeam solution for our existing clients and some prospective clients. We currently have 10 to 15 clients. 

It is a straightforward solution. There is no need for a dedicated technical person to do the backup and replication. Veeam is very straightforward when it comes to doing the replication.

It needs to support more applications. In terms of supported applications, Oracle SQL and Office 365 are supported, but I am not sure if it supports Linux-based applications. That's why I'm looking for an alternative. I am currently testing Commvault. The advantage of Commvault is that a lot of applications are supported with it.

I am not sure if CIFS is currently supported. It would be nice to have this feature in case it is not already supported.

I have been using this solution for over a year now.

Veeam offers good support. After you get their product, they provide online support. You just need to raise a ticket, and then someone from global support will contact you. I'm okay with Veeam's support.

It is very straightforward. You just need to spin up the virtual machine and enter proxy, and then you can start the backup. 

The deployment takes a couple of hours. It takes a maximum of two or three hours to deploy it for an enterprise. It is a really straightforward solution. To deploy it for an enterprise, you need at least two to three resources.

This solution could be used as an alternative approach for migration from on-premise to cloud or for disaster recovery. If you have two data centers and you need to replicate the primary virtual machines to another site, this can be an option.

I would recommend this solution to others. I would rate Veeam Backup & Replication a nine out of ten.

We use this solution for virtualization with VMware. I have approximately 50 servers. We also use it for replication of the file server.

There haven't seen any changes to the way the organization has improved.

I would like to see the replication and a recovery plan of the servers in the cloud. It's very important.

I have been using this solution for three months.

We use one of the first versions of this product.

It's a stable product. I would rate it an eight out of ten.

It's a scalable solution.

In our company, we have one administrator and one other operator who use it. One person for each server.

Based on the orders we receive, we will continue to use this product.

Technical support is good. I would rate them an eight out of ten.

Previously, I was using IBM Spectrum.

Three months ago, I made the decision to change to Veeam Backup & Replication because IBM solutions are expensive.

IBM is very good software, but the problem is the cost. I would rate IBM a ten out of ten.

I was also using Acronis, but I wasn't sure of it. I did not have the experience with it.

The initial setup is straightforward. It's easy.

It's not complex to replicate and back up the system.

We used an integrator, reseller, and a public consultant, which was very expensive.

The experience was good but it was a bit of a process with a bit of a struggle.

This is an expensive product, so reducing the cost would be an improvement. The difference between IBM and Veeam Backup & Replication is insignificant.

It is approximately $4,000 to $5,000 for the purchase of the product and I paid an additional $2,000 for the renewal.

For large enterprise companies, I would suggest IBM, but for small companies, I would recommend Veeam Backup & Replication.

I would rate this solution an eight out of ten.

Primary backup and long-term retention to protect our client data across our datacenters. Allows for incremental RPOs for VM and file-level recovery across multiple datacenters to our IT staff of more than 200 technicians. Enable fast restores and long term archival.

As our datacenters continue to grow, we had a challenge of reducing backup windows while being able to scale our total protected VMs. Before Veeam, we had backup infrastructure sprawl. Veeam was able to reduce our overall backup windows while reducing our dedicated backup infrastructure.

Granular permissions through Veeam Enterprise Manager have allowed for us to pass control down to our support staff instead of having it with senior datacenter resources.

Vendor integration for many of the enterprise features have allowed for us to have greater performance from our storage vendors further improving on our commitments to protect our clients' data. 

Multithreading of health check process: This can take too much time to process on large jobs and/or large VMs. Better to have built-in deduplication for long-term retention. Storage efficiency is a weakness.

Additional executive summary reports for the entire infrastructure would be a nice to have.

Three to five years.

No, we have not experienced any stability issues.

One challenge that we have encountered was on the long-term retention of data. Be sure to look into a dedicated deduplication appliance. 

Also, know where the bottleneck is within your environment. If you are repurposing older equipment, it likely won't be up to the task. Storage performance is crucial to your backup times.

Support has been great; no complaints.

We used PHD Virtual and what is now Unitrends UVB. Backup infrastructure was becoming a significant cost and scaling this solution meant more sprawl. Backup windows were increasing outside our comfort levels. At the time, we as acquired a company with additional datacenter services. Consolidating to one solution with a single interface was key. This, in turn, ensured that we had complete visibility of our backup environments across multiple datacenters.

Veeam helped us solve all of these areas of concern.

It was pretty straightforward.

In-house.

We have increased our scalability while being able to free up senior resources from recovery activities. I estimate our overall savings to about $20,000 per year.

Plan your long-term backup strategy for growth and size the solution appropriately. Veeam has a number of setup options to choose from so make sure you understand them to make the right decision.

I would always suggest a multi-year agreement as this will allow for the best possible ROI of licensing.

We looked at vRanger, Unitrends, and Datto.

Since everyone's data is different, I would recommend a proof of concept project to understand how your data will be used within this solution. If you are intending to keep data for long-term retention, look at a dedicated deduplication appliance.

We use the solution for customers who want to back up their VMware environment.

The solution is really easy and straightforward to use. If we want to configure something using Veeam ONE, we don't need much time to study the management interface. Our customers appreciate the solution's ease of use.

Recovery is the most important thing when we create a backup, which works fine on Veeam ONE. We can also use the shared backup and run recovery tests when needed.

The solution is not very good at backing up the physical Linux systems. Backing up SAP HANA with the solution is not very convenient. The solution also does not support the backups of uncommon databases, which prevents it from spreading across the market.

I have been working with the solution for the past five years.

The stability is quite good. I would rate it a nine out of ten.

The scalability is very good. Ten of our customers use the solution. I rate the scalability a ten out of ten.

The support is quite responsive and fast. It depends on what kind of support package you have paid for, but generally, it's fine.

The initial setup is very easy.

It takes us half a day to install and configure the systems. The time taken for deployment depends on how big the environment is.

To deploy the solution, install it first on the virtual machine or the physical systems, then install it on the Windows physical machine. Then, set up the accounts in the physical or virtual servers. Finally, connect the repository for the pickups and configure the backup jobs.

We need one or two administrators and engineers to deploy the solution.

The licensing fee depends on the licensing model we choose. We can pay for on-premise licensing. We can also choose to pay a yearly fee for support, or we can pre-pay for support five years in advance. 

Now, the solution also provides a subscription model. Additional costs depend on the kind of product we purchase.

Veeam has an Essentials edition and an Enterprise edition for larger environments. People who want to use the solution should choose the on-premise licensing instead of the subscription model because it will be much cheaper. Overall, I rate the solution a nine out of ten.

We use it to back up and restore our virtual machine in a live environment without restoring the complete virtual machine. It just mounts its storage to the NFS and makes the machine live in seconds. That is our favourite feature in Veeam ONE.

In the past, we used NAKIVO for our backup replication, and the main problem was that their backups were unverified and, most of the time, were corrupted. But the backup in Veeam ONE is good, and we are satisfied that the backups are also accurate and stable.

When we install an application, we have backups available in another drive and have to import those backups into the machine. Sometimes, rarely, there is a bug that prevents enabling the restore button, which is hectic. We then have to go into the folder and double-click to fix the issue. However, improvements can be made to prevent the bugs and improve restoration and importing of previous backups into the new one.

I don't think any additional features are required as it is already packed with many features.

We have been using this solution for approximately five years and are using the latest version. We always keep our versions updated. It is deployed on-premises.

I rate the stability a nine out of ten. So we like the solution, but I can't rate it a ten because there is room for improvement.

I rate the scalability a ten out of ten because it is scalable even using Google Cloud or Amazon Web Services. It is also scalable on-premises. Only our organization's manager and deputy manager have the right to operate this solution. We have plans to expand use as the data center keeps expanding.

The initial setup was straightforward, and Veeam ONE requests prerequisites and installs them without the internet. That is a big bonus, with those prerequisites packaged in each setup. It is also pretty straightforward for someone unfamiliar with the solution.

Deployment was done in-house. Our data center does not have a big workload, so we use the Veeam ONE backend application and community edition. It is free, and if any issue arises, it can be solved with a Google search. It took three people and around 40 minutes to complete the deployment. One person can complete the rack installation of physical hardware.

It's free of cost for up to ten workloads, which is a big benefit for a small data center.

I rate this solution a nine out of ten. My advice to a new user is to go for the community edition. It is more than sufficient compared to Acronis or NAKIVO. Veeam ONE is the best and the most mature solution for hypervisors and physical machines.

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.