Captured data
Each Veeam server becomes an asset of the type Veeam. The detail page groups the data as follows:
How the detail page of the type is structured is described in
Storage, Backup, Permissions.
Setting up the job
The wizard follows the standard path Basics › Targets › Schedule › Summary—see Creating a Scan Job. The Targets step is what sets this module apart. Each row carries the columns IP/Hostname and Credentials. IP/Hostname takes one Veeam server per row, as an address or hostname; the column does not accept an address range. The Credentials column must be filled, with an entry of the type User Account. An entry in Credentials for all targets applies to every row without an assignment of its own. The module setting Collect Backup History (Days) determines how many days of backup history the scan captures; it is prefilled with 42 days. Where the module settings are is described in Creating a Scan Job.Prerequisites
The scan connects to the Veeam server over WMI and queries the Veeam data through PowerShell.Ports and protocols
Permissions
- The account is a local administrator on the Veeam server—for the WMI connection.
- The account is a member of the Veeam Backup Administrators group—for the Veeam data.
- Multifactor authentication is not active for the account.
- The account has signed in to the Veeam server at least once, opened the Veeam Backup & Replication console and confirmed the certificate message.
- If the Veeam server is not a member of the domain, use a local administrator
account, such as
.\Administrator.
Network requirements
- The firewall allows the ports above. In a domain, enable the predefined rules
through Group Policy:
- File and Printer Sharing (Echo Request - ICMPv4-In)
- File and Printer Sharing (Echo Request - ICMPv6-In)
- Windows Management Instrumentation (WMI-In)
- Windows Management Instrumentation (DCOM-In)
- PowerShell 7 is installed on the Veeam server.
Discovery-VeeamBR.exe scan script
(Veeam Backup & Replication 13) or Discovery-VeeamBR-Legacy.exe (version
12)—see Scanning by Script.
Common issues
The registry value, set on the Veeam server: