Within Veeam Reporter, there is an option to select a reporting job to run either automatically or to leave it as on-demand. In most situations, the automatic run of the job would seem to be the best choice. The on-demand job doesn’t run on a schedule, but it still reports the relevant data as configured in the report. The option to configure the job to run automatically is shown in the figure below:
This is primarily a way for administrators to manage the amount of email coming in from Veeam Reporter. Too frequently, everything may be sent over email. That provides a nice audit log, but some things may not need that level of traffic over email. For the concerns about losing the point-in-time visibility, the on-demand option to run a report allows a specified collection to be used for the report. In the example below, a report can be run on-demand from the collection job iterations from the past within Veeam Reporter:
There are a number of reports that could be better suited as an on-demand run configuration. One example is a report on vSphere network interfaces that are in use on each ESX(i) host. This is something that you may not need to run regularly, yet this report would document the exact configuration of each ESX(i) host and vCenter Server as configured. This would be useful to identify a NIC driver in use, which interfaces are not at 1 GB or higher and the associated vmnic number assignment.
It is quick and easy to create this report because it is based off of the base report pack, infrastructure report template and the physical NIC object type. Four basic metrics are provided to document the network configuration on the hosts. These are driver, name, speed (MB), and host system as shown below:
This can be run on-demand within Veeam Reporter or configured to be sent over email. Configuration items such as network details can be done in preparation for an upgrade, auditing connection speeds or other one-time events as part of the ongoing virtualization administration practice.