What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Veeam Backup for about four to five years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
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.
What about the implementation team?
We implemented this solution through an in-house team.
What's my experience with pricing, setup cost, and licensing?
Veeam products are less expensive than other products. The licensing costs are low and they're pretty affordable.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
After sale support should be the most important decision criteria for buying any solution. When it comes to disaster recovery usually people are mentally stressed and challenged in terms of RTOs, that causes a bit of a panic and may affect proper judgement of taking the right decisions at the time, having a simple solution comes handy in such situations. All I can say that according to my 2 year in depth experience of dealing with multiple Veeam products and before that having dealt with other backup vendor's I cannot stop but say the truth that Veeam has an amazing after sales support experience hence their NPS scores and their products are the easiest to use in their field so far. It really just works!