Considerations and Limitations

Before you install Veeam Software Appliance, review known issues and limitations described in release notes. Also, consider the following:

  • Veeam Software Appliance must be installed on a dedicated empty machine that meets the system requirements. For more information, see System Requirements.
  • Enterprise Manager on Linux is supported only with the Enterprise Plus edition license.
  • You cannot install other backup infrastructure components on the machine where Enterprise Manager is installed. This includes the backup server, backup repository, proxy server and other components.
  • Backup infrastructure components communicate over specific network ports. These ports must be open. For more information, see Ports.
  • Veeam Software Appliance installation and initial configuration support only the English US keyboard layout.
  • When you install Veeam Software Appliance, the Rocky Linux operating system, Veeam Backup Enterprise Manager and other Veeam Software Appliance components are installed with predefined settings, including volume partitioning and user account creation. After installation is complete, you need to proceed with the initial configuration of Veeam Software Appliance, which includes setting up host users, and configuring server time and network settings.
  • [VMware only] Veeam Software Appliance only supports the Network transport mode.
  • Veeam Software Appliance uses DISA and FIPS-compliant Linux policies. These policies cannot be changed.
  • Veeam Software Appliance is compliant with most SCAP Security Guide DISA STIG for RHEL 9 requirements except for the following ones:
  • V-258230 — RHEL 9 must enable FIPS mode.

Important

If you have infrastructure that does not support the TLS Extended Master Secret, Veeam Software Appliance will not be fully FIPS-compliant

  • V-258241 — RHEL 9 must implement a FIPS 140-3-compliant systemwide cryptographic policy.
  • V-270180 — The RHEL 9 fapolicy module must be configured to employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs.
  • V-257937 — The RHEL 9 firewall must employ a deny-all, allow-by-exception policy for allowing connections to other systems.
  • V-258122 — RHEL 9 must enable certificate based smart card authentication.

Page updated 11/20/2025

Page content applies to build 13.0.1.180