What is our primary use case?
We've been providing Veeam solutions to clients. We basically distribute MSP licenses to clients.
Veeam Agent for Windows is basically the mini compared to Backup and Replication, which is like the Mercedes of the two. It's for anything that doesn't require a backup of an application or license. For example, for physical server backups or physical workstation backups. You won't really use it for virtual machines. You'll rather install a backup of the application and use it for that. That's about it.
What is most valuable?
To do recoveries is not that hard. To do the actual backup configuration is also not too bad. It also works off an agent. It does snapshots.
Technical support is helpful.
What needs improvement?
It basically does caching on the actual customer's machine. For example, if you're doing a trial backup, which enables you to basically do a similar thing to Acronis, where you can carry on from where you left off. The only issue is that caching is running on your local machine. So, if you have a little bit of space left on your machine and now it has a big cache, then your hard drive runs out of space, and it crashes. You don't want the tool to be responsible for breaking your machine.
I've worked with a lot of tools, and the only difference between this and the normal CMB tool, which just does a snapshot and copies files, is the way it's being stored. It puts it in a different kind of file format. In terms of, let's just say, Acronis Cloud, it's got something like active protection, which actually protects your backup archive from ransomware. Veeam does not have anything like that. There's no security feature whatsoever.
They tried to bring in something like immutable backups, so now you can't change your backup. Yet it can still be encrypted. It's absolutely pointless. We try to move away from the, let's say, old legacy kind of products like Veeam, even though it's still marked as one of the best backup products there is.
We need some sort of security for backups and archives. I've had too many instances of targeted attacks where people will access the backup repository and encrypt the backup file, then launch attacks on the machine. When that happens, the machine is not recoverable, and you have to pay a ransom to get your information back.
For how long have I used the solution?
I've used the solution from the time it was released.
What do I think about the stability of the solution?
It's quite stable. It is an on-premise installation. It can be set up to send you email notifications via SMTP, and that in itself can become tricky to basically set up.
With the actual recovery, let's say you work at a company, and you don't want to install Backup and Replication, and you want to deploy only Veeam Agent for Windows. That's fine. You can deploy everything and set everything up. For every single instance or agent that you install, in order for you to do a recovery of that machine, you would need an individual copy of your recovery media. So that means you're going to have a hundred recovery media over the size of about 500 megabytes or even bigger, in some cases. At the end of the day, that is useless storage. What happens is if you lose one of those recovery media or you don't make it, you cannot restore that machine.
What do I think about the scalability of the solution?
It's not really that scalable.
We used have over 2000 Veeam Agents installed across various customers.
How are customer service and support?
Their tech support is quite good. It's a legacy product in my eyes and it forms part of the basic principles of backup. For instance, if this doesn't work, do that. If the service is down, just start it. There's no real big complexity with it sometimes. However, tech support is quite good. Sometimes there are errors that you just can't avoid and nobody can help you with them. And that just means that you have to start from scratch with the backups.
Which solution did I use previously and why did I switch?
I've worked with Veeam Backup and Replication and Veeam Agent for Linux. For Linux, there's no reporting. The only way for you to figure out what's happening is to physically log into the machine and figure out if the backup ran or not. It's not really that good. For Windows itself, it looks fine.
How was the initial setup?
With regards to the setup, the big issue there is you do need the latest version of .NET. If you want to install it on an older kind of machine. It doesn't really support all of that. It means you need to do system updates, all of those kinds of things, just before you can even install .NET, and it can become quite a headache to get it up and running initially.
To deploy it on a network can be quite tricky, and that's why most people would rather use Backup and Replication and deploy it through there instead of deploying it one by one. That's basically what you need to do with this. You need to go to a machine, install it, go to the next machine, and install it. Unless you try and push the installation through your active directly, which sometimes works and sometimes doesn't. There are also issues with that as well.
What's my experience with pricing, setup cost, and licensing?
One upside of Veeam Agent for Windows is that it's free - unless you want to back up to the cloud. You would need to get a Cloud Connect License in that case, which is really inexpensive. Then it just has to be set up at the back end of your MSP, and then you pay for the cloud storage program.
The licensing costs are actually very good.
What other advice do I have?
We're using the latest version of the solution.
I would advise people to use the solution in certain use cases. For example, if a customer has a machine that doesn't really have internet, or they don't want a cloud-based solution, and the customer is very small and has one or two machines, then yes, by all means, use it.
I'd rate the solution six out of ten. It's tricky to manage, and you literally have to go to each machine to go and figure out what's wrong with it. There is no real information that you can pull up online when there's a problem.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner