Veeam Data Platform Reviews

The solution is primarily used for disaster recovery, replication, and stacking up all the endpoints using the product's endpoint component.

Setting up the replication is very simple.

The solution just works consistently. I never have issues with it.

The product is stable.

The scalability is excellent.

I have issues with the licensing. 

The solution isn't ideal for small companies or systems. It's much more geared towards larger entities. 

I've been dealing with the solution for eight years. 

The stability is excellent. The solution just runs. There are no bugs or glitches. It doesn't crash or freeze It's extremely reliable. 

The scalability has been great. I can pretty much do whatever I need to. The problem is the licensing. Scalability equals licensing and that costs quite a bit.

The solution is best for businesses that are larger - those that have got multiple systems, and by that I mean about 20-plus systems, that need to be protected. 

I have no issues with technical support. They have been helpful and responsive and I am satisfied with the level of service I get.

The initial setup of it has a learning curve that is a little bit steep, however, you quickly get a hang of it.

The solution is quite expensive, and that becomes an issue if you need to scale. Costs add up quite quickly. At the end of the day, it doesn't matter how good your product is, if it's not affordable, you're not going to get people behind it.

I'm an end-user.

My company uses both private cloud and on-premise deployment models. 

The solution is a very good product for what it does. 

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

If this is a good solution or not for a company depends on the company size and what it wants to achieve. If your company is about 15 to 20 people and you just need to have backup and recovery and not have to worry about 24/7 uptime, then I wouldn't recommend Veeam for you. However, if you need something that is up 24/7 and you can quickly recover, then I would say go with Veeam. For big systems, I'd say you'd go with Veeam, and that it works best as an onsite system. When you start moving to the cloud, and when you need to back up the data for the company, you've got other systems that also can handle it.

It is for backup and replication.

We use it for failover and disaster recovery. There have been times when our primary systems have failed, and we've been able to run virtually until our primary systems are available again. From a business continuity experience, it has worked fairly well.

Replication is most valuable.

The cloud part of it can be improved. There should be an option for Veeam in your own cloud, as compared to the Veeam cloud offering that's currently there. The rest of it is easy. 

I have been using this solution for eight years.

It is stable.

I am not trying to scale it up.

I didn't have any issues with technical support.

We use Zerto for the main part, and Veeam for a little part. We use them for different things. I prefer Zerto because I get a better RTU and RPO. It may be not as easy to set up, but once it is working, the RPO is in a region of 10 seconds. As compared to Veeam, its replication is currently two or three times.

It is of medium complexity.

It is relatively cheap.

I would advise others to use it. It is a good system.

I would rate it an eight out of 10.

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.

It is installed and configured in 15 minutes. It is reliable and you can really count on its restore jobs. It also provides very good deduplication alongside fast backup/restore on tape and instant VM recovery and allowing you to restore a VM onto an NFS mount point anywhere you want on a Windows 2012 Server. Veeam's 3-2-1 backup rule is also good where it has three copies of data, two different medias, with one off-site copy. Lastly, we're able to sandbox VMs without impacting the production environment.

In a fully virtualized environment, the ability to perform instant or quick restore full VM is invaluable, and because this product is reliable, I often forget the backup appliance for weeks or months.
Veeam Backup makes me more confident and agile in managing and maintaining my IT infrastructure.

Since this is a pure 95 % virtualized solution for Hyper-V or vSphere, this product could do more to backup individual files, databases, and or complete guest OS. For now, I have to backup NAS, and doing this for individual files is a pain in the neck and I have to play with two different backup solutions. Also, Veeam will not backup a physical server.

I've been using it since v6.0 in 2013. It was used in parallel with VMware VDR, and then VDP but it was quickly abandoned for a full Veeam solution.

We have had no issues with the deployment.

There have been no performance issues.

I have ordered more socket CPU licenses but I do not know if this will be easy or painful. There is nothing to do when adding clusters/hosts except checking the number of CPUs allowed.

I have, 99 % of time, found an answer to my questions or issues through customer services or via forums.

On-line help is also complete and often come with interactive videos showing how and where to click, and this is amazing.

Prior to Veeam, I used VMware VDR, and then VDP (> vSphere 5.x).

It's complete in 15 minutes. It's so easy that even a child could schedule bakcups. It was the same when upgrading from v8.0 to 9.0. It was simply a click and wait job and completed within 10 minutes.

I’m responsible for choosing and implementing this product. I discovered Veeam through my previous jobs. In this one, it was already implemented by local IT engineers.

Licensing costs are OK, they are a good average when compared to their competitors. The only issue I have is having three NetApp filers and not being able to backup/restore from snapshots, SnapMirror, or SnapVault. So if I had more money, I’d head directly to the Enterprise “Plus” Edition. The Standard Edition is not supposed to manage tapes or deduplication and is limited to small infrastructure environments.

I’m not a specialist of EMC Avamar, but I think that Avamar is more universal (backup of NAS for example), but it is way more expensive and complex than Veeam. I didn’t evaluate any other commercial solution.

There's no need to buy direct attached disks, as you can just build from scratch a “Veeam appliance” with a a big 2U 8 core Xeon server with 16 GB RAM and lot of SAS disks (at least 2 RAID). You then add Windows Server OS and the Veeam software. With this setup, you won’t need extra space, separate SANs, or network switches, except maybe for your LTO drives.

Otherwise, use some VMs for Veeams and separate the proxy so you can make your big physical server a repository. Do not allow your physical server to backup your ESXi hosts with VMFS datastores, as you might not find your VMs in the VMDK virtual disks.

Most important though is to always test your real recovery abilities and try to simulate total failures of a SAN direct attached volume for example, or even from your backup system.

We use the solution for monitoring purposes.

The price could be cheaper.

Veeam ONE should make the work easier without installing additional dashboards to start configuration.

I have been using Veeam ONE for nine years.

Support is best.

Positive

Deployment is not difficult and takes three to four hours to complete.

The product is expensive.

One person can manage all parameters.

Overall, I rate the solution a ten out of ten.

For data recovery, we do some tests. We haven't had any problems yet. The tests we've done work fine.

For me, it's perfect. We don't have any problems with backups and applications.

Immutability is the most important aspect of data protection in terms of Veeam Data Platform. That could be one critical factor for us.

Data protection is the most valuable aspect.

We had one problem once with the multinet in the network, but it wasn't a big problem. It was a problem with the network itself. That is the only problem we have had.

I have been using it for two years. We use the current application tool, the new one, that's the tool server that I use.

I personally haven't requested any support, but my coworker has and says it's good.

Positive

I have also been using Veeam ONE for about two years to monitor traffic and jobs. So, mainly as a monitoring tool.

We use it to monitor everything. We don't have any other tool like it. We used to use vRealize Operations Manager, but we don't have that anymore. That's why we use Veeam ONE. It's easy to view all the infrastructure.

The infrastructure we have is simple.

So, the initial setup is very easy as our environment isn't complicated.

We finished the deployment in about three weeks. We didn't deploy the solution solely for the strategy part. It took us three weeks because it wasn't a priority for us when we deployed the solution. So, the deployment time could have been less.

We didn't have any problems with integration into our existing ecosystem.

In my opinion, maintenance is very simple. We don't have any problems with updates.

It is not expensive. 

I would give it a ten out of ten because I haven't had any problems with maintenance. It's very simple and our environment is also very simple.

So for simple use, it's a very good tool and fulfills all our needs.

I highly recommend it.

We use Veeam ONE mostly for data backup and recovery for virtualized environments.

One valuable feature of Veeam ONE for backup management is its dashboard, which offers a comprehensive view of backups and other essential data.

In terms of improvement, I have found Veeam ONE to be lacking in some areas. The reports are basic and not customizable, making it challenging to get detailed insights. Additionally, there are limitations with the reports if your backup schedule runs overnight. I hope they release a better version soon.

I have been using Veeam ONE for two and a half years.

I would rate the overall stability of Veeam as a seven. While it is reliable for general backups and snapshots, it faces challenges with scale-out and Oracle backups. The Azure scale-out feature also presents stability issues, with most of our tickets revolving around that area.

I would rate the scalability of Veeam ONE as a five out of ten. While it can scale, it is heavily dependent on factors like bandwidth and data volume. Our organization, being data-heavy, faces challenges with scale-outs due to bandwidth limitations. Smaller organizations might find it easier to scale without such constraints.

We have around ten users currently using Veeam ONE in our organization, overseeing the protection of approximately 3,000 workloads.

I would rate Veeam's support as a nine overall. Tier one support can be weak, but tier two is excellent. We often need to escalate to tier two for resolution. Occasionally, issues require R&D involvement, but overall, support is reliable.

Positive

We chose Veeam over Commvault because it is simpler to use and more cost-effective. Commvault's complexity and lack of readiness for cloud backups made it less appealing. Veeam offered comprehensive backup solutions for on-premises, Azure, and Office 365, with fewer hardware requirements compared to Commvault.

Deploying Veeam ONE in our organization took around one to one and a half hours. It was straightforward, it was just a matter of connecting to the server and following a few steps.

We handle maintenance and troubleshooting for Veeam ONE in-house with a team of two to three people. If we can't resolve issues internally, we escalate to Veeam support. We used to have weekly catch-ups during critical issues but now have shifted to monthly since there are no critical issues currently. Overall, it is a straightforward product that doesn't require frequent maintenance once set up.

Overall, we find Veeam ONE to be reasonably priced, especially with our long-term deals. Its capability to manage various aspects of our infrastructure, including on-premises and Azure, adds significant value. While we initially tried Azure native backup, we found Veeam to be more comprehensive and user-friendly. Although we currently use two backup solutions, we are considering consolidating everything under Veeam in the future.

We don't use Veeam ONE for monitoring our virtual environment due to compatibility issues with other software like Pulse SolarWinds. We primarily use it for backup activities. I have tested it and found it promising, but haven't run it extensively due to operational concerns.

I use Veeam ONE for proactive issue resolution by relying on its reports. If something isn't healthy, the report alerts me. Then I investigated further, like when it flagged issues with our proxy server's pricing. I don't check it daily; I schedule reports and review them, giving me a basic idea of what is happening. If I see unexpected issues in the report, I know where to focus my attention. While I don't use it for daily monitoring, it is handy for reporting.

Veeam ONE's reporting capabilities provide a decent overview, but I need more granularity for our data protection strategies. While the reports are okay, they sometimes lack the detail my team and boss require. I'm currently exploring ways to meet our need for more detailed reporting, such as tracking data scaled out to Azure.

Veeam ONE's analytics have helped us with IT decision-making by identifying issues like poor storage and repository node problems. Its focused view on backup infrastructure narrowed our troubleshooting scope. For instance, it highlighted discrepancies in backup deletion, leading us to uncover a bug in our current version. 

I would recommend Veeam ONE for small organizations, but for larger ones needing granular reporting, it might fall short. Veeam is continually improving its features and aiming to compete at an enterprise level, but it is still evolving. Overall, I would rate Veeam ONE as an eight out of ten.