In Veeam Backup & Replication, if there are multiple unsuccessful attempts to enter a confirmation code for Multi-Factor Authentication (MFA), the system will lock the user account to prevent unauthorized access.
Based on standard security practices, and while it may vary, a lockout for 24 hours after exceeding the maximum number of failed attempts is a common approach to protect against brute force attacks. Please note that specific lockout policies can vary by system configuration and the policies set by the system administrator. It's always best to consult the actual system settings or documentation for the precise behavior in a given environment.

To change a backup copy job from periodic mode to immediate mode, the most straightforward approach is D:
Create a new backup copy job and delete the original job. Veeam Backup & Replication does not directly allow changing the mode of an existing backup copy job from periodic to immediate within the job settings.
Therefore, the recommended practice is to set up a new backup copy job with the desired settings, in this case, immediate mode, which starts copying backups as soon as they are created by the primary backup job. After the new backup copy job is configured and tested to confirm it meets the requirements, the original periodic mode job can be safely deleted. This ensures a seamless transition to the immediate mode operation without risking data protection consistency or coverage.

Veeam Agents are designed to provide backup solutions for physical and cloud environments. They support various operating systems, including Ubuntu (a Linux-based OS) and Windows Server. These agents ensure that data on servers running these operating systems can be effectively backed up and restored. However, Veeam Agents do not support FreeBSD, IBM iSeries, or iOS as these platforms require different backup solutions or are not typically used in environments where Veeam operates.References:
* Veeam Agents User Guide
* Veeam Help Center: Supported Environments

Reference: https://helpcenter.veeam.com/docs/backup/vsphere/appgroup_vms_vm.html?ver=100

Explanation
https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_restore.html?ver=120