comnanax.blogg.se - Veeam versions

#Veeam versions install
#Veeam versions windows 10
#Veeam versions plus
#Veeam versions free

#Veeam versions windows 10

Microsoft Windows 10 (from version 1803 to version 21H1 2, and 21H2 3 )ġ Running Veeam backup server or any of Veeam backup infrastructure components on Insider versions of Microsoft Windows OS (both Client and Server) is not supported.Ģ This version is supported starting from Veeam Backup & Replication 11a (build 11.).Only 64-bit version of the following operating systems are supported 1 : High latency and reasonably unstable WAN links are supported.ġ Here and throughout this document GB is considered as 2^30 bytes, TB as 2^40 bytes.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster for offsite backup and replication.

#Veeam versions free

Additional free disk space for Instant Recovery cache folder (non-persistent data, at least 100 GB recommended). 10 GB per 100 VM for guest file system catalog folder (persistent data).

1.3 GB RAM for catalog jobs for each 1,000,000 filesĭisk Space : 5 GB 1 for product installation and 4.5 GB for Microsoft.

2.6 GB RAM for file restore for each 1,000,000 files.

1.5 GB RAM for file to tape backup for each 1,000,000 files.

Memory consumption varies according to the number of VMs in the job, size of VM metadata, size of production infrastructure, and so on.Īdditionally, for users with tape installations (for file to tape jobs processing more than 1,000,000 files):

#Veeam versions plus

Memory : 4 GB RAM plus 500 MB RAM for each enabled job.

Adding the same repository to different Veeam Backup & Replication installations may lead to corrupted backup and data in the database.ĬPU : x86-64 processor (minimum 4 cores recommended).

Backup components cannot simultaneously interact with Veeam Backup & Replication of different versions.

Veeam installations compete for resources.

We do not recommend to use shared backup infrastructure components across different Veeam installations due to several reasons: Sharing Backup Infrastructure Components Across Veeam Installations For all-in-one installations, the server where all the components are installed must have enough memory resources for all components. Make sure you allocate enough memory resources for your installation. These 2 GB are allotted to the OS itself, assuming each component is installed on the dedicated server.Įach of the following NAS backup components may consume up to 4 GB RAM per task (in case of deduplicating storage appliances, up to 8 GB RAM): backup repository, backup proxy, cache repository.

#Veeam versions install

However, if you plan to restore Microsoft Exchange items from the Veeam Backup Enterprise Manager UI, you must install Veeam Backup Enterprise Manager on the domain member server from the Microsoft Active Directory forest in which Microsoft Exchange mailboxes are located.įor all-in-one installations, you can subtract 2 GB of memory resources from each but one role.

The machine on which you plan to install Veeam Backup & Replication does not necessarily need to be a domain member. Mind that you cannot install Veeam Backup & Replication and Veeam Backup Enterprise Manager on a machine running Microsoft Windows Server Core. You can assign roles of a backup proxy, backup repository, WAN accelerator, Veeam Cloud Connect infrastructure components and tape infrastructure components to machines running Microsoft Windows Server Core. Backup infrastructure component roles can be co-installed. If possible, install Veeam Backup & Replication and its components on dedicated machines. We do not recommend to install Veeam Backup & Replication and its components on mission-critical machines in the production environment such as vCenter Server, Domain Controller, Microsoft Exchange Server, Small Business Server/ Windows Server Essentials and so on. Make sure that servers that you plan to use as backup infrastructure components meet the system requirements listed below.Ĭoexistence with Mission-Critical Production Servers