Settings and activity
3 results found
-
44 votes
An error occurred while saving the comment 
Scott
supported this idea
·
-
17 votes
An error occurred while saving the comment Scott
commented
Completely agree with this. We have Veeam Backup Enterprise Manager for the sole purpose of being able to run PRTG's Veeam sensors against it at the moment.
Additionally, in Veeam 13, if you move to the Veeam Software Appliance (VSA), Veeam Backup Enterprise Manager requires its *own VM*, meaning that if you're coming from an environment with a single backup server that also ran Veeam Backup Enterprise Manager, you now require *two* virtual machines; one for Backup and Replication, another for Backup Enterprise Manager.
Further, in Veeam 13.1, if you're running the new Veeam Software Appliance, you can now do roll based access for web restores, which further eliminates the need for Backup Enterprise Manager for many customers.
Native PRTG sensors that connected directly to the native Backup and Replication REST API would help greatly and eliminate the need for Backup Enterprise Manager and an entire second virtual machine to run it when using the Veeam Software Appliance. This would greatly reduce attack surface, management, and resources.
Scott
supported this idea
·
-
2 votesScott
shared this idea
·
This would definitely be handy for organizations that either require a publicly signed certificate or don't have an internal PKI set up. Additionally, for the majority of these servers that won't be exposed to the internet, the integrated ACME client should support DNS challenge with popular providers like Cloudflare and Amazon AWS Route 53.