Veeam Backup & Replication Reviews

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.

In my previous company, this was being used as the backup and replication solution.

The backup and replication capabilities are quite good.

The integration with other solutions should be improved.

I have worked with Veeam Backup & Replication for two years. I stopped using it a few months ago when I changed companies.

For the entire time that I used it, this product was stable.

This a scalable solution.

The technical support for Veeam is good.

We currently use Dell EMC Avamar and we also have experience with IBM Spectrum Protect.

These are all specialty tools and are good, although, for the needs of our organization, we prefer Avamar.

The initial setup is easy.

Overall, this is quite a good product and I recommend it.

I would rate this solution a nine out of ten.

Our primary use case is for a backup solution for our front-end servers. 

It has improved my organization by 90%. Now we can restore a single box with all of its folder contents. We could install one email, one folder or one lead and it could have still one email. This has helped us a lot. Before we used to store the entire database and then we would go to the single mailbox we need to use and we could restore it. Now we could do it instantly whereas it used to take three to four days. 

We migrated our servers from physical to virtual with our B2B platform. We had a big problem when trying to transfer our site server that was about six terabytes to the new environments. We wanted to do it with minimal effort and without changing the permission because if we do a copy, the permissions won't work. We put a Veeam Windows agent on these physical servers, did a backup and then we were able to take this backup as a drive that is connected to the new VM environment. It has helped us transfer the solution in two days instead of working for a minimum of one week to ten days. 

I would like for them to develop the ability to fix the way it does backups. We can't pick a backup for one database. We have to do a backup on the whole Exchange VM. I'd like for them to change it to where we can do individual backups. 

I would like for it to work with Oracle VM. 

The solution is very stable. It has worked well since we deployed it. We haven't had any problems until now. It's currently used daily. We do backups daily, weekly and monthly.  

It's scalable. We are planning to increase usage. We are planning to buy new Oracle hardware and plan to add them to the same solution. It doesn't work with Oracle VM which is an issue.  

We currently have 500 users that include top management, financial people, and engineers. 

The solution's technical support is good. They respond within a 20-hour timeframe. The issue that comes up with them is that our weekends don't overlap. We have off Friday and Saturday and they have off Saturday and Sunday so when we submit a request it can take a long time for them to respond. I would rate their technical support a seven out of ten.  

We had been previously using HP Data Protector. We switched to virtualization. We switched to Veeam because the person who promoted it explained its benefits well. 

The initial setup was very straightforward. The company that we hired came in and installed it without a hitch. Now we can use it efficiently without their help. The deployment took one day. We did have a problem when we started working with it. The difference between the restore points wasn't clear. Up until this point, we're still not sure what effect it has on our backup. I would like this to be made more clear. It's easier for us to directly put it on tapes than to first put it on storage. 

As far as our deployment strategy went, we started with building our jobs. We took our jobs and tried to plan them on the system and we took VMs instead of files. It has worked up until now. After a month or so we did need to make some changes to some of our jobs.  

Our integrator is one who generally deals with IBM and Lenovo hardware in Egypt and we were the first case they had working with a Veeam solution. They listened to what we needed and what we were asking for. We need on the job training so we needed their help for the first month or so after the installation. The engineer was very helpful in guiding us through the deployment. He was very professional. He helped us at the beginning but after a certain point, we had some issues and he would tell us that he'd get back to us but he never did. He was busy and didn't prioritize us because we're not his main customer. We turned for support from Veeam themselves and they were responsive and helped us.

It requires two staff members for maintenance. They're two engineers that act as backup for each other. We really only need one engineer to administer everything but if he's not there, the other one is there as backup.  

The pricing is good and affordable. 

I would advise someone considering this solution to find a good implementor who can help you during and after the implementation. 

I would rate it a nine out of ten. It's a good product that we can rely on, it has many features and works on many platforms. It's a very good product.

We had an issue with power in the data center and one of the IBM storage devices could not startup. We managed to restore all of the VMs from Veeam and disaster recovery was executed as expected within our SLA.

Enables us to restore the VM when the needs arises and for disaster recovery.

• Near-synchronous, better RPO and RTO snapshot-based takes a lot of space and resources.
• They could look at different ways to replicate only new changes or blocks.
• If we have to use Veeam for disaster recovery, we need to make sure that we can at least have up to 10 or 15 minutes of data before a disaster happens. Currently, you can have replication but this uses/eats up a lot of resources, on the network. Is there any other way they could increase RPO with less or limited network resources being used?

We did have stability issues and we had to contact technical support. They were very helpful.

Technical support is very good.

We didn’t have any previous tools for this.

The initial setup was straightforward. We did quite a bit of research and lab testing before the actual implementation. The white papers where very helpful

The pricing and licensing is better than the competitors, but it could be better.

We looked at Zerto and Acronis.

If they are looking for backup and recovery, Veeam is the way to go. If they are looking for a high RPO and RTO, Zerto is the way to go.

I am using Veeam Backup Replication for backups.

The backups we have been receiving from Veeam Backup Replication on-premise have been good.

The cloud backups from Veeam Backup Replication have not been good. Addiotnaally, the backups of Office 365 and the overall performance can always be improved.

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

We have not encountered any problems with the stability of Veeam Backup Replication.

The scalability is good from Veeam Backup Replication.

The technical support from Veeam Backup Replication is good.

Veeam Backup Replication can be quite expensive for Office 365 because its license is per user and not for the space that you use. You need one license for each user. If the user only uses a few files on one hard drive, you need a license to back up these files. It was better to have a license model, such as in the Cohesity solution. Cohesity has a license for a space that you use. It's more useful in this case because the license for backup data is on-premises is for CPU. The license is based on how many CPUs you have but it does not depend on how many users use the CPU. 

I have evaluated Cohesity. I have a demo version that they gave me.

I rate Veeam Backup Replication an eight out of ten.

We use this solution to replicate the SQL server to another site.

We tried to set up the application from SQL to SQL. We did this for the department, but the process took us almost a year. After we had signed off on the solution we noticed that it was affecting the performance of the SQL.

The data backup replication has been the most useful feature. Previously, we copied the data hub to an external hard drive but now we are able to store the backup on one of the depository services.

We struggled to stabilize the application. We had an incident which resulted in a loss of data and have terminated this solution due to lack of support from the Veeam team.

I have been using this solution for three months. 

We have had issues connecting to the server, specifically connecting to the head office to be on the same network. 

We have not tried to scale this solution but it is possible. 

Support for this solution could be improved. We have been frustrated getting help via email. When dealing with the support team, they were not knowledgable on the solution and how it works. 

The initial setup was complex and required assistance from the team at Veeam. After the installation, the solution does not function as we expected. The deployment took two weeks. 

This is an expensive solution and came at a higher cost than expected. We were charged higher prices than shown on the website by partners of Veeam. We were not able to buy a few licences to begin with. We had to buy five licences from the beginning before knowing if the solution worked for us. The initial contract for the solution was not clear on which services were to be paid for and which were free. 

We first completed a POC in a test environment which worked well. However, when moving over to a production environment, we experienced some issues. 

We would have benefitted from more guidance on what options were available based on our internal systems. 

I would rate it a five out of ten. 

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.