You can install it on a physical machine or on a virtual machine. It's used basically the same way a company would use Veeam Agent for Windows - except it has no reporting.
The only use case that I will use it is if you do have Veeam Backup and Replication installed and you have a Linux virtual machine. That is the only place where I will use it since it's the only way for you actually to make successful recoveries.
The only thing I really like about it is that you can deploy it from Backup and Replication onto a virtual Linux machine. Once you start working with the physical Linux machine, it's not compatible, and it doesn't work. Don't even try it.
There's a lot that needs to be changed. I'm not even going to go into the small specifics of it; however, I would say reporting is probably the biggest thing that needs improvement.
It has no cloud backup feature. You can't back up anywhere outside of your local network.
The solution is expensive.
Technical support often has little insight as to what is happening with the product.
It is not really scalable.
I've used the solution for four years.
It's not really very stable. There's no reporting, so you don't even know if the thing is working or not. And, the way I see it, if there's no reporting, there is no backup.
It's not really a scalable product. There is not much you can do with it.
You can't even restore the entire machine. However, if you need it, the other way for you to do that is through Backup and Replication. This solution is very limited.
We were using probably 20 Veeam Linux Agents across a bunch of different districts. We're replacing them.
Unfortunately, when we ask for assistance, often technical support also does not know what is happening.
From my side, I wouldn't even touch the support. I would be more focused on improving my solution. If the solution actually worked and did what it's supposed to do, there wouldn't be necessary for so much need for tech support.
In terms of implementation, there are a whole bunch of additional dependencies that you do need to install. Then, once you have those installed, it's pretty straightforward from there. In order for you to do anything there, you need to physically log onto the machine, physically open the app, and physically configure everything yourself.
Initially, once I got past all the dependencies or included the dependencies, it took about half an hour to an hour to set up the solution.
You have to sort out the actual dependencies of the machine first. You have to download a whole bunch of stuff first so the machine doesn't break. After that, you would need to get the installation file to download, and you would use all CLI commands, all Windows command line commands, basically to download the machine. Once you do the installation, then it's going to tell you, hey, wait, you missed some dependencies. You would have to go and install those first. After that, if you run it again and it goes through, you have to try and figure out how to configure it. It can be quite daunting if you've never worked with it before.
The licensing is quite expensive. It's double the price of anything else.
I wouldn't recommend the solution to others. I'd advise potential users to use something else.
Overall, I'd rate the solution three out of ten.