Veeam Backup & Replication Reviews

We use it internally for our own systems, and we have slightly less need on our clients' side, just because they rarely need that kind of system. We can achieve it with other tools.

Its simplicity and the fact that it just works are most valuable. We kind of set it up and generally forget about it. It does what we need it to do in the background, and it doesn't involve a lot of management.

In terms of functionality, it's pretty good, There is a lot of variety in what it can do and how it can back up. We probably use only 10% of what it is kind of capable of, so we're not really pushing the boundaries of it and having any problem.

It is always nice to get products cheaper.

We have been dealing with this solution for maybe five years.

It is absolutely stable. We tend to set it and forget it. It has been a very reliable solution.

We don't really have much experience with their support. Over the five years, we've maybe put in one or two tickets, and that's about it.

It is very simple. It is pretty self-explanatory as long as you understand the virtual environments that you're working with. Veeam itself is pretty easy.

It is always nice to get products cheaper. 

Technically, it saves you a lot of money. If you wanted to buy the same functionality out of vSphere, you would spend thousands to essentially get the same functionality.

I would highly recommend it, but it also depends on whether or not it all fits in with the clients and the pricing model. It is like any backup solution. You have to consider what you're trying to get out of it before you go ahead and configure it, but for backup and replication across hosts, it works really well.

I would rate it a nine out of 10 for what it does. I don't know anything that does it as well.

I'm actually a consultant, so I deploy it for my customers — quite a few of them.

Our clients are partly interested in backing up their application servers and their environment — that's the first priority. Some of our clients have gone a bit further into remote disaster recovery, off-site disaster recovery. They replicate to another location for those purposes.

Our clients are small to medium-sized companies.

There are a few of them. It's relatively easy to use and the ability to recover in a short period of time has been great — I think that works quite well. I've compared Veeam with other products and to me, it works the best of the lot.

Even though the speed has improved over the years, I think that there are some instances where it still takes a while. In some cases, we have experienced fluctuations in performance. For example, yesterday we performed a synthetic full backup. Normally, this takes less than 90 minutes, but other times, it takes well more than six hours to get 40% of the way.

Other than that, I find that it does what is expected and maybe a bit more. I also don't think that I've really tapped into all of the features of it as yet.

I have been using Veeam Backup & Replication for roughly 10 years.

Veeam Backup & Replication is very stable.

As I mentioned earlier, I have not really investigated all of the features, and one of them is potentially more scalability than anything else. Regarding what little I have done so far, it seems to be pretty scalable. I do have a couple of projects in the works that I'm going to push out a bit more, so I won't be able to give a fair assessment until I have gone through those projects.

I would say it is good. I'm trying to remember when the last time was that I had to call technical support. I think they're very satisfactory overall.

I think that the support resources are adequate. They're pretty good, actually. At the moment, I can't think of anything in terms of technical support and the community support that is lacking.

The initial setup is straightforward. There were no major issues. Well, there was one issue, but that was with an older version of it. For some reason, it would not work on a machine that was part of a domain, but I got that sorted out using a later version of the software.

Regarding deployment, I was able to install the software myself. I had it up and running in a couple of days. We went through a period of more than a week to ensure that the backups were being done properly, were being finished properly. I would say within a couple of weeks it settled down and it's been working fine since then. 

In terms of deployment, it usually takes one person. I installed it with a colleague — we're both Veeam certified, so that helps. From the point of view of the end-users, they seemed to grasp it pretty readily. At every institution, there are one or two people that are needed to maintain it — that's it. As I said, it's stable and relatively simple to use. My customers are satisfied with it.

Some of our clients were using solutions like Arc-Serv, Backup Exec. There are a couple of clients who actually evaluated NAKIVO and Veeam a few years ago. There was one client that was comparing Commvault to Veeam. They eventually went with Commvault, but a lot of that has to do with the support of AS400 symbols. They were able to manage their backup costs and a number of different environments using Commvault.

A number of my clients moved from physical machines to virtual ones. They were using primarily Arc-Serv and Veritas Backup Exec, which proved to be a bit inadequate for new virtual environments. It was never seamless. It was never as straightforward as you would have liked. With NAKIVO, we found that it tended to be easier to deal with. Still, even though one of our customers did go with NAKIVO, after a couple of years, they actually moved onto Veeam.

I would absolutely recommend this solution to others.

I've been using it for a number of years and the bottom line is — it works very well and is simple to use. Within an hour or two, my customers are comfortable enough to be able to create their jobs and monitor job progress, etc. If it works for them, it works for me.

Overall, on a scale from one to ten, I would give this solution a rating of nine.

I use both features Backup and the replication for my 2nd Datacentre - Is my DR Solution.

Easy to use product, If you have a virtual environment and also are worried about putting in a DR solution - This is an easy product to get to grips with, Plugs into Vcentre and has the same feel as Vcentre. the replication feature is great - Seamless on enterprise version that I use for my DR solutions.

Standard version is poor - As you need to power Off/On virtual machines when backing up/Restoring where Enterprise edition you don't - If you have a big estate to manage stay away from Standard.

Over 7 years now - Since ver 6.

No - You can have this up and ready in less than half a day.

Veeam is dependant on Microsoft SQL and VMware or Microsoft Hypervisor so no.

Limitations in VMware is 10000 and Citrix is 6600 VDI's, Veeam is charged at physical CPU so very scalable.

I've not really had to deal with Customer service.

Again not really had to deal with technical support.

Veeam Backup and Replication is in its own world - Nothing out there that is even close to this product that I could recommend.

Very simple to install. If you follow VMware Best practice and install a Vcentre on 1 physical and one Virtual, Same again with Microsoft SQL. Remember if you have a virtual farm failure your need to have it installed in a physical to bring back your virtual platforms - I have seen many of big company's also make this school boy error.

I have implemented many times with an in house team.

I have this installed on a 150k user base - My total spend is 3 Mil Us Dollars.

It's the only solution for an enterprise Virtual environment.

Veeam is our primary backup system used with the DD2500 for the repository. We use Veeam 9.5 Update 3 on a physical Windows 2016 server with Proxy servers deployed one per host in our HA Cluster. We also use the Enterprise Plus licensing for Nimble Snapshot Integration for backups and this allows our backup window to be reduced.

With moving the Veeam server to a physical server and creating a Proxy server on each of the hosts, we are able to leverage SAN based backup which is very fast. Jobs are completed overnight and never run in to the business hours.

Features with the most value are Instant VM Recovery, SQL Explorer and Exchange Explorer. Allowing our Veeam Agents access to the repositories for backups is another big plus.

Physical backup is always where room for improvement could be but Veeam has always stated they are not going in that direction. However, with Veeam Endpoint Backup, physical server backup is possible.

I have been using this solution for more than five years.

Stability has always been the best part of Veeam and never has there been an issue with this.

The scalability of Veeam is endless depending on your needs and there were no issues for us.

Customer Service:

Customer service is always been top notch and I rate it a 10/10.

Technical Support:

Technical support is 10/10. They are always fast with responding to tickets and help you in the best way possible. They even arrange discussions with Architects if you have questions on best practices or environment setup.

Positive

We still use Symantec Backup Exec but only due to having physical Exchange 2010 servers. Once we virtualize this will be decommissioned. Having Veeam Endpoint Backup may be the alternate solution to fast-track this.

The initial setup was very straightforward and there never seems to be issues with Veeam.

We completed the implementation in-house using local resources.

ROI has been about six months.

Be sure as always to evaluate products, get licensing costs, etc. Choose what is right for your business model.

No other options were evaluated as we knew Veeam was one of the better solutions for Virtual Backup.

Veeam is a great product and always works. The product setup is easy and learning of the product for someone technical is straightforward. I look forward to the improvements in this product as it progresses.

It is convenient to create backups of virtual machines, and hard disks. It's also applicable for backing up various other services. When dealing with a heavy workload, the process of backup is designed to be straightforward. It involves transferring data from on-premise to the cloud or vice versa. This encompasses different usage scenarios.

Veeam's Instant Recovery feature allowed my organization to continue operations during file server failure by immediately restoring lost data.

Instant Recovery is an useful feature.

It is efficient but can improve security-wise. 

I have been using Veeam Backup & Replication for the last three years. 

I would rate the stability nine out of ten.

The support is good. 

Positive

It required 2-3 people to deploy. It is deployed in a hybrid manner. It took almost 2-3 hours for the process to complete.

The deployment procedure begins by accessing the Veeam Backup website to download the necessary software. Subsequently, the software is managed on the server where installation is intended. Before proceeding with installation, it's recommended to have a backup, ensuring functionality on the server. The installation process itself is distinct, not combined with the backup sector. Each step is downloadable, contributing to the installation information. The final step involves creating a backup job. Users can choose the backup type they prefer, whether it's full, implemented, or differential. Following this, the backup can be saved on desired media, such as servers.

It is not expensive and I would rate it five out of ten.

We considered other vendors but discovered that the Veeam Backup has establishment as a direct node-to-node connection and synchronization with other systems.

I can recommend that it serves as a good solution. The code constitutes a comprehensive answer. It effectively backs up all workloads. This applies to various scenarios – from email to physical and virtual machines, services, SAP DNS, and Azure DNS – allowing for comprehensive backup solutions. It extends to cloud-based backups as well. Essentially, it covers the entirety of our workload, whether on our infrastructure or network.

I would rate it an eight out of ten.

We are using Veeam Backup & Replication for backing data, such as our databases and VMs.

The most valuable feature of Veeam Backup & Replication is the ease of use.

Veeam Backup & Replication could improve by making it more user-friendly.

I have been using Veeam Backup & Replication for almost one year.

Veeam Backup & Replication is a stable solutions.

I have found Veeam Backup & Replication to be scalable.

We have one person using the solution in our company and they are doing the backup of our data. We plan to increase usage near the end of the year.

The technical support from Veeam is good.

We previously used Veritas NetBackup but it was having some issues and it is almost at its end of life. We moved to Veeam Backup Replication.

The initial setup was easy, and the whole process took two to three days.

We did the implementation of Veeam Backup & Replication ourselves. We only use one person for the maintenance and support of the solution.

We pay for the license of Veeam Backup Replication on an annual basis. The cost of the license is approximately 70,000 rials. The support and maintenance are included in the price.

My advice to others is Veeam Backup Replication is a good solution.

I rate Veeam Backup & Replication a ten out of ten.

It's used to replicate the production environment from the primary side to the backup, or between two data centres.

The most important are the snapshot and the replication features. VMotion for replication of the production is useful, but it's not really important. We don't use these features every day.

I'd like to have this kind of solution, but in the Cloud environment. I think there are other solutions that address the same requirements, like Commvault, which can be used easily in AWS on the S3 environment.

This VMotion feature is not mastered by any expert and we don't use it for replication. If we are migrating and relocating the primary site to another site, we do it in two steps. So at the primary site, we switch it with the backup and then vice versa. We then relocate it to another site. When we wanted to use VMotion to make the switch from the primary site to the backup site, there were some difficulties with it. It's not reliable enough to be 100% sure that there will be no failure in the operation.

I have been using it for eight months.

Once it's in place, the product is stable.

I don't haven't enough knowledge about that yet because I've only been using it for eight months. We haven't had enough transaction volume yet.

With this solution, I have an integrator helping me with all the infrastructure. I rely a lot on these experts because they know the solution very well.

It was quite difficult to put this solution in place and I don't think we use all the features, like VMotion. 

I would rate this solution a five out of ten. 

VM is suited for small and medium enterprises. In big enterprises with a complex IT infrastructure, the solution is not suitable. 

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.