When estimating the amount of required disk space, you should know the following: Also, consider that VM recovery processes (Instant Recovery, FLR and others) require sufficient resources (as described here). The same amount of resources are needed for SMB gateway servers. It is recommended to configure 4 GB RAM per core. At least 2 cores allow for the Operating System to be more responsive. In mid-sized or enterprise environments, the recommended amount of CPU for a repository is 1 core per concurrent job that processes data on a repository server. See recommendations for backup proxy parameters in the Veeam Backup & Replication Best Practice Guide.RHEL-based backup proxies must have the nfs-utils package installed.
Debian-based backup proxies must have the nfs-common package installed.Linux backup proxies must have NFS client package installed.For Direct NFS access, mind the following:.For Direct SAN access, note that Linux backup proxies must have the Open-iSCSI initiator enabled.Linux backup proxies cannot be used for guest interaction.For integration with storage systems: Linux backup proxies do not support the NFS protocol.Linux backup proxies that use virtual appliance (Hot-Add) transport mode do not support the VM copy scenario.This is because VDDK settings required by VMware cannot be enabled on Linux backup proxies. Linux backup proxies cannot be used with VMware Cloud on AWS.The disk.EnableUUID parameter of the Linux server must be set to the TRUE value in the VMware vSphere client.For more information, see Requirements and Limitations for Veeam Data Movers and Specify Credentials and SSH Settings step of the Adding Linux Servers wizard. Therefore, you cannot assign the role of a backup proxy to a Linux server added with single-use credentials. Linux backup proxies require SSH connection.In addition to the general requirements and limitations, the following ones apply to Linux backup proxies: Requirements and Limitations for Linux Backup Proxy Consider a good connection between proxy and repository. A backup proxy should be as close to the source data as possible with a high bandwidth connection.For more information on CBT, see Changed Block Tracking. If you back up proxies that use the Virtual appliance (Hot-Add) mode to process VM data, the change block tracking mechanism (CBT) will be disabled.You must add the machine to the Veeam Backup & Replication console as a managed server.The account that you specify when adding a server must have permissions described in Required Permissions.For more information, see System Requirements. The machine must meet the system requirements.
#VEEAM BACKUP SERVER REQUIREMENTS WINDOWS#
If neither of the above scenarios is possible, you can assign the role of the backup proxy to a machine whose network is located closer to the source or the target storage to which the proxy will connect.This type of proxy also enables LAN-free data transfer between the host and the backup proxy. The backup proxy can be a VM with HotAdd access to VM disks on the datastore.This way, the backup proxy will retrieve data directly from the datastore bypassing LAN. A machine used as the backup proxy should have direct access to the storage on which VMs reside or the storage where VM data is written.The first connection is the most efficient, the last one is the least efficient. The following list shows possible connections between the machine and storage that keeps backups of this machine. Before you assign the role of a backup proxy, check the following prerequisites and limitations.