Veeam Backup and Replication Hardware Requirements
Make sure that components in the Veeam Amanuensis management infrastructure meet system requirements listed below.
Veeam Backup Server
To learn nearly system requirements for the Veeam backup server and other Veeam Backup & Replication components, see the System Requirements department in the Veeam Backup & Replication User Guide.
Veeam Agent Computer (Microsoft Windows)
A calculator that you want to protect with Veeam Agent for Microsoft Windows must meet the following requirements:
| Specification | Requirement |
|---|---|
| Hardware | CPU: x86-64 processor. Memory: two GB RAM or more. Memory consumption varies depending on number and size of processed disks. Disk Space: 200 MB for production installation. Network: 1 Mbps or faster 1 . System firmware: BIOS or UEFI. Drive encryption: Microsoft BitLocker (optional) 2 . 1 High latency and reasonably unstable WAN links are supported. two BitLocker encrypted volumes must be unlocked at the moment when Veeam Agent for Microsoft Windows starts the backup or restore operation. Simply Microsoft BitLocker is supported for bulldoze encryption. Other bulldoze encryption products are not supported. |
| Os | Both 64-chip and 32-fleck (where applicable) versions of the following operating systems are supported 1 :
Each Veeam Agent estimator that consumes a license installed in Veeam Backup & Replication must accept a unique BIOS UUID. 1 Consider the following:
two Veeam CBT driver is supported only if Microsoft Windows update KB3033929 is installed on the Veeam Agent computer. 3 Microsoft Windows 10 Education is supported starting from build 10586 and subsequently. |
| File System | Microsoft Windows Fat, NTFS, ReFS file systems are supported. The supported file organisation must reside on a volume that is 64 TB or smaller, because Veeam Agent uses the Microsoft Software Shadow Re-create Provider to create a book shadow re-create during the backup. To learn more about the limitation, run into this Microsoft commodity. |
| Microsoft SQL Database | Microsoft SQL Server 2012 SP4 Express LocalDB Edition. Microsoft SQL Server is installed inside the Veeam Agent deployment procedure only if you added the target reckoner to the backup policy. To larn more, meet Backup Policy. |
| Software | The post-obit required 3rd political party software is included in the Veeam Agent for Microsoft Windows Redistributable. During the Veeam Amanuensis deployment process, Veeam Fill-in & Replication checks whether all prerequisite software is available on the target reckoner. If some of the required software components are missing, Veeam Backup & Replication will install missing software automatically.
i The component is installed only together with Microsoft SQL Server. |
Veeam Agent for Microsoft Windows works with simply those hard bulldoze types that are supported by the Microsoft Windows OS. Thus, Veeam Agent supports the 512 bytes and iv KB sector hard drives merely. Other hard drive types are not supported. To learn more, see this Microsoft article.
Veeam Agent Figurer (Linux)
A computer that y'all want to protect with Veeam Agent for Linux must see the following requirements:
| Specification | Requirement |
|---|---|
| Hardware | CPU: x86-64 processor (i386 or later). Memory: i GB RAM or more. Memory consumption varies depending on the backup type and the total corporeality of backed-upwardly data. Disk Infinite: 100 MB gratis disk space for product installation. Network: 10 Mbps or faster network connection to a backup target. System firmware: BIOS or UEFI. Disk layout: MBR or GPT. For virtual machines: But full virtualization type is supported. Containers and paravirtualized instances are not supported. Oracle VM virtual machines are supported with limitations. |
| Bone | Important! Check considerations and limitations that apply to the list of supported OSes. Linux kernel version 2.half dozen.32 or subsequently is supported. Both 64-bit and 32-scrap versions (if applicative) of the following distributions are supported 1 :
1 Starting from Veeam Backup & Replication 11a (build 11.0.1.1261), support of the post-obit OS versions is added: Debian 11, Ubuntu 21.04, RHEL 8.4, CentOS 8.4, Oracle Linux viii.iv (RHCK), Oracle Linux UEK R6 U1, UEK R6 U2 (up to kernel version v.4.17-2102), SLES 15 SP3, SLES for SAP 15 SP3, Fedora 33, 34, openSUSE Bound xv.3. For Veeam Backup & Replication 11 (build 11.0.1.1261) with Cumulative Patch P20211211 ) installed, back up of the following OS versions is added: Ubuntu 21.10, RHEL 8.v, CentOS eight.5, Oracle Linux viii.five (RHCK), Fedora 35. |
| File System | IMPORTANT! Check considerations and limitations that apply to the listing of supported file systems. Veeam Amanuensis for Linux supports consequent snapshot-based data backup for the following file systems one :
The supported file system (except for Btrfs) can reside on a simple book or LVM2 volume; volumes protected with encryption software such as dm-crypt are supported. Btrfs is supported simply if information technology resides directly on a physical device with no additional abstraction layers (such every bit LVM, software RAID, dm-catacomb and and so on) below or in a higher place information technology. Data that resides on other file systems and volumes (including NFS and SMB shares) tin can be backed up using the snapshot-less mode. For details, see the Snapshot-Less File-Level Fill-in section in the Veeam Agent for Linux User Guide. |
| Software | Important! Cheque considerations and limitations that apply to the listing of supported components. Protected computer must have the following components installed:
For file system indexing, the following utilities are required: tar , mlocate and gzip . |
Considerations and Limitations (Linux)
Bone
- Linux kernel version 2.vi.32 or later on is supported as long as you utilize kernels supplied by your distribution. Consider the post-obit limitations:
- Fedora and openSUSE Tumbleweed are supported up to kernel 5.15.vii.
- Linux kernel two.6.32-754.six.3 in RHEL and Oracle Linux (RHCK) is non supported.
- If you piece of work with the Veeam Amanuensis for Linux v.0 build earlier than 5.0.ane.4493 and the protected computer is running Linux kernel version 5.8 or later on, just snapshot-less file-level backup is supported.
- Only GA versions of the supported distributions that have been released earlier the current version of Veeam Agent for Linux are supported.
- The Linux Os must be ready to receive software updates from the default repositories enabled in the OS after installation.
- For cloud-based installations that apply customized kernels (such equally Linux distributions deployed from AWS Marketplace or Azure Marketplace), the veeamsnap kernel module has experimental back up status. For details about experimental support, see this Veeam KB article.
- Automatic Veeam Agent deployment from the Veeam backup console is non supported for the following distributions:
- Fedora 33, 34, 35
- openSUSE Tumbleweed
You demand to install Veeam Amanuensis for Linux directly on a target computer. For details, meet the Installing Veeam Agent for Linux section in the Veeam Agent for Linux User Guide.
- RHEL, CentOS, and Oracle Linux (RHCK) are supported upwards to sure kernel versions. For details, see this Veeam KB article.
- Ubuntu 21.x minimal install is non supported.
File System
- Veeam Agent for Linux does not back up volumes that reside on USB devices and SD cards.
- File-level fill-in has the following limitations:
- Total size of all file systems must non exceed 218 TB.
- Size of a file must not exceed 16 TB.
- Name of a file must not be larger than 254 bytes.
Go along in mind that characters that you lot can utilise in the file name may be encoded in ii bytes or more.
- Veeam Agent supports fill-in of extended attributes with the following limitations:
- Veeam Amanuensis backs upwardly extended attributes only with the post-obit public namespaces: system, security, trusted, and user.
- All extended attribute names and values of a file must not exceed 4096 bytes (size of a default ext4 file system block). Veeam Agent does non back up attributes exceeding the limit.
For the kernel version iv.13 or after, if a value of extended attribute exceeds the limit, Veeam Agent uses the ea_inodes feature. Backups created using the ea_inodes feature cannot be mounted on kernel versions up to 4.12.
- Backup of file and directory attributes (for example, a — append just, c — compressed, and so on) is not supported.
- Each volume included in a backup must have a unique UUID.
- The veeamsnap module provides RAM-based changed cake tracking (CBT) machinery. Every time the module is unloaded or Veeam Agent for Linux computer is rebooted, CBT data is reset. As a result, Veeam Amanuensis reads the entire data added to the backup scope to discover what blocks take inverse since the last task session, and incremental fill-in requires greater time.
- You cannot back up an entire system image or specific volumes of computers used as cluster nodes. Only snapshot-less file-level fill-in of cluster nodes is supported. That includes backup of computers that use shared disks, amassed file systems, or clustered LVM.
- Sure limitations for EMC PowerPath configuration apply. To learn more, encounter this Veeam KB commodity.
- BFQ I/O scheduler is non supported.
- Sparse files are not supported. Veeam Agent backs upwardly and restores thin files as regular files.
Software
| |
| Linux user account used to piece of work with Veeam Agent for Linux installed on the protected computer must have the /bin/bash shell set every bit the default shell. |
- To install Veeam Agent for Linux packages on a target reckoner, Veeam Backup & Replication uses the default parcel manager of the Linux distribution running on this calculator. During the installation process, the parcel manager checks whether all prerequisite software is available on the figurer. If some of the required software components are missing, the packet manager will attempt to install the missing packages from a software repository configured in the Bone.
- The following packages are not required for CentOS, RHEL and SLES distributions if a pre-built binary veeamsnap package is to exist installed.
- dkms
- gcc
- make
- perl
- kernel-headers (for RedHat-based systems)
- kernel-devel (for RedHat-based systems)
For details, see the Installing Veeam Agent for Linux section in the Veeam Amanuensis for Linux User Guide.
- Version of the following packages varies according to the Linux kernel version that you use:
- linux-headers (for Debian-based systems)
- kernel-headers (for RedHat-based systems)
- kernel-devel (for RedHat-based systems)
- For openSUSE and SLES distributions, either of the following packages is required: libncurses5 or libncurses6 .
- The dmidecode package is r equired for Veeam Agent management — a valid BIOS UUID must be obtainable either from dmidecode | grep -i uuid or from /sys/grade/dmi/id/product_uuid . Each Veeam Amanuensis that consumes a license installed in Veeam Fill-in & Replication must have a unique BIOS UUID. If a valid UUID cannot be obtained, Veeam will generate it automatically.
- The libmysqlclient package is required to process MySQL database organization located on the Veeam Agent server. Package version varies according to the MySQL database organization version that you utilize.
- The libpq5 package is required to process PostgreSQL database system located on the Veeam Amanuensis server.
- The python3 packet or another RPM parcel providing a /usr/bin/python3 binary is required for CentOS, RHEL 7.0 and later distributions if a pre-built binary kmod-veeamsnap package is to be installed.
- The btrfs-progs package version iii.xvi or later on is required.
- The lvm2 packet version up to 2.03.12 is required. After versions are non supported.
Veeam Agent Estimator (IBM AIX)
A computer that you desire to protect with Veeam Agent for IBM AIX must meet the following requirements:
| Specification | Requirement |
|---|---|
| Hardware | Retentiveness: 1 GB RAM. For information most RAM requirements for backup of a great number of files, see the RAM Requirements for Large-Scale Environments section in the Veeam Agent for IBM AIX User Guide. Disk space: 1.five GB free disk space for product installation. Network: 10 Mbps or faster network connection to a backup target. |
| OS | All versions of the IBM AIX operating arrangement starting from IBM AIX 6.i are supported. Note:
|
| File Organisation | All file systems supported past the supported operating systems. Notation:
|
| Software | For file arrangement indexing, the following utilities are required: tar , mlocate and gzip .
|
AIX Environment
The LIBPATH AIX surroundings variable on the Veeam Agent reckoner must be set up to blank (default value). If a different value is specified for this variable, you must make adjustments to the AIX environs for proper operation of Veeam Agent. For details, see this Veeam KB article.
Veeam Agent Reckoner (Oracle Solaris)
A estimator that you desire to protect with Veeam Agent for Oracle Solaris must meet the following requirements:
| Specification | Requirement |
|---|---|
| Hardware | CPU: Oracle SPARC or Intel x86 processor. Memory: 1 GB RAM. For information about RAM requirements for backup of a great number of files, see the RAM Requirements for Large-Calibration Environments section in the Veeam Agent for Oracle Solaris User Guide. Disk infinite: 150 MB free disk space for product installation. Network: 10 Mbps or faster network connection to a backup target. |
| OS | Oracle Solaris 10 – eleven.4 operating systems on machines based on the SPARC and Intel x86 architecture are supported. Annotation: Only GA versions of the Oracle Solaris OS that accept been released before the Veeam Agent for Oracle Solaris version 3.0 are supported. |
| File Organisation | All file systems supported by the supported operating systems. Note:
|
| Software | For file system indexing, the following utilities are required: tar , mlocate and gzip .
|
Veeam Agent Reckoner (macOS)
A computer that you desire to protect with Veeam Agent for Mac must meet the following requirements:
| Specification | Requirement |
|---|---|
| Hardware | The protected macOS computer must see the following hardware requirements:
* On a macOS reckoner with the ARM Apple tree-branded hardware, the product is running using the Rosetta Translation Surround. |
| OS | Veeam Agent supports the following macOS versions:
|
| File System | Veeam Agent supports consistent data backup with snapshot for the APFS file system. The following file systems tin be backed upward in the snapshot-less mode:
Consider the following:
Continue in mind that characters that you tin can apply in the file name may be encoded in two bytes or more. |
Backup Target
Backup can be performed to the following types of storage:
For Veeam Agent backup jobs managed past the backup server
- Veeam Fill-in & Replication 11 or later backup repository
- Veeam Deject Connect 11 or subsequently cloud repository
For Veeam Agent backup jobs managed by Veeam Agent
- Local (internal) storage of the protected computer (not recommended)
- Straight attached storage (DAS), such every bit USB, eSATA or Firewire external drives, and raw device mapping (RDM) volumes
| |
| [For Veeam Agent for Microsoft Windows ] We do not recommend targeting a fill-in job at the storage device with the exFAT file organization. If the protected reckoner runs Microsoft Windows 10 or Microsoft Windows Server 2019 and later, this configuration may lead to the backup data corruption caused past the exFAT file organisation issue. |
- Network Attached Storage (NAS) able to represent itself every bit an SMB (CIFS) share
- Network Attached Storage (NAS) able to represent itself equally an NFS share (for backups of Linux and Unix computers merely)
- Veeam Backup & Replication 11 or subsequently fill-in repository
- Veeam Cloud Connect 11 or subsequently cloud repository (excluding backups of Unix computers)
Network
Consider the following:
- Veeam Amanuensis should exist able to constitute a direct IP connectedness to the Veeam Backup & Replication server. Thus, Veeam Agent cannot work with Veeam Fill-in & Replication that is located behind the NAT gateway.
- Domain names of all managed servers added to the Veeam backup infrastructure and computers you desire to back up must exist resolvable into IPv4 addresses.
| |
| For Veeam Amanuensis computers that are included in a protection group for pre-installed Veeam Agents , only Veeam Backup & Replication server must be resolvable into IPv4 address. |
0 Response to "Veeam Backup and Replication Hardware Requirements"
Post a Comment