A Guide to Veeam Setup Best Practices

More and more companies realize that server virtualization is the way to modern data security. In 2020, VMware is still the market leader, and many Veeam customers are using VMware vSphere as their preferred virtualization platform. But backing up virtual machines in vSphere is only part of the service availability. Backup is the backbone of recovery. So it’s important that backups are always available at the right speed.

This guide presents Veeam Backup & Replication best practices. It is not complete documentation or a detailed explanation of the features. The Best Practices Guide is for professionals looking for answers and suggestions on various topics. It may be a design idea, the best way to use a function, possible pitfalls, etc. D. As a rule, this information has been developed, collected, and updated by the Veeam Solutions Architects team working on site with Veeam users. They do not explain theory, but practice.

Note that the best practices are not the only available answer. In most cases it will work, but it may be completely wrong in other circumstances. Make sure you understand the recommended best practices, or ask someone to do so.

K.I.S.S. design

It becomes more difficult for the IT department to manage and ignore too complex projects, and it is easier for an intruder to use them and stay in the background. Projects that are easier and easier to ignore are usually safer. Use the K.I.S.S. (Keep it simple stupid) Principle for your creations. KISS is an acronym for “Keep it simple, stupid” as a design principle established by the US Navy in 1960. The principle of KISS states that most systems work best when they are simple and uncomplicated. Therefore, simplicity should be a key design objective and unnecessary complexity should be avoided. Simple design is easier to control and is generally safe.

Adding security to an existing infrastructure is much harder and more expensive than thinking about designing a new infrastructure or upgrading an existing one. In a virtual infrastructure, it makes sense to create a master image that has been enhanced from the beginning. Remove all known attack vectors and access only when Veeam components are added and certain (port) openings or additional software are required for correct operation. Thus, all versions are consistent and up-to-date, which makes them safe in the database.

Make sure that the repository servers are physically protected.

Place the repository servers in a restricted area, because these servers contain a 100% copy of your production environment! The repository servers must be physically secure and have appropriate access control systems. This will restrict access. All those who have access are logged and controlled at certain defined levels.

Use a standalone Windows server

If you are protecting the entire environment, you do not want the Veeam repository to be associated with the same Microsoft Active Directory domain that you are protecting through a backup. Otherwise, you may have a chicken and egg problem with accounts trying to authenticate to a domain that is no longer available if everything is lost.

If the domain administrator account is compromised, we do not want that account to be able to override the password for the backup store account so that the hacker can access the backup files as well as the entire environment.

Protect physical or external cloud servers with Veeam Agent’s backup.

  1. You may have servers that Veeam cannot back up or replicate.
  2. Maybe physical servers or a virtual machine that is in a public cloud that you do not have access to a hypervisor (e.g. AWS),
    Azure-blue). For these servers, you can back up the iland cloud repository using Veeam Agent.
  3. Backups. This agent is installed in the guest operating system of the production server and does not require access at hypervisor level. Veeam Agent can be installed on Windows and Linux systems.

Note the bandwidth availability.

  1. The performance of Veeam Cloud Connect is highly dependent on the available bandwidth. For example,
  2. If you are trying to back up or replicate terabytes of data, but only 20 Mbps is available, you can
  3. Backing up should take a few days. The initial backup or replica may be important time, because all data has to be transmitted for the first time.
  4. When you can’t finish Timely progressive work can have a significant impact on your safety and confidentiality.
  5. It is also better to schedule external tasks outside working hours if possible. This allows you to allocate Veeam bandwidth instead of sharing it with your network end users.

Check your backups and replicas regularly.

The worst time to find out if your backups or replicas are damaged is when you need them. Check yours.
Backups and copies for replication to ensure that they are complete and acceptable when and how you do it
you need them. You can use Veeam Console to restore all VMs, VM files or guest OS files to your computer.
Surroundings. This process gives you confidence that your data will be available immediately if
There is a disaster.

  1. You can test the failover at any time and access your replicas in the iland cloud.
  2. This is useful not only to test the integrity of your replica data, but also to provide access to and
  3. The function works as it should. It may be necessary to update the existing network rules.
    or that new critical servers have been added to production but not yet replicated.

Physical deployment


In small to medium sized environments (up to 500 virtual machines), Veeam Backup and Replication Server, Backup Repository and Backup Proxy components are typically running on the same physical server. This is also known as deployment of a “model device”.

In large environments (over 2500 virtual machines), Veeam’s backup and replication services work best on separate physical or virtual servers. When multiple jobs are running at the same time and consume large amounts of CPU and RAM, it may not be possible to scale up a virtual backup and replication server to meet system requirements.

One of the advantages of running Veeam Backup and Replication Server on a physical server is that it runs independently of the virtual platform. This may be an ideal situation where the virtualized platform is recovering from a disaster.

In an enterprise environment, you can install additional VBR to speed up the disaster recovery process. You can reuse existing availability components, such as a repository or proxy server, for Veeam Backup and Replication.

Backup Proxy

The Backup Proxy is a compact architectural component of Veeam that sits between the data source and the backup destination, processing backup jobs and providing backup traffic. Backup proxy server tasks include retrieving VM data from the production storage and compressing, deduplicating and sending this data to the backup repository. With more than one virtualized (or physical) backup proxy, you can easily scale your backup infrastructure to fit your system size.

  • In a simple deployment scenario for small environments, Veeam Backup Proxy is automatically installed on the VBR as part of the Veeam Backup and Replication installation.
  • In advanced deployments, the Proxy role is manually assigned to one or more Windows servers. This offloads the Veeam backup server, reducing backup time and improving performance.

How to Setup and Configure Veeam Backup & Replication

Veeam Backup & Replication is the only solution that easily, reliably and flexibly protects all your cloud, virtual and physical workloads. Get rid of privacy, extortion protection, and compliance issues. Veeam saves time and money, simplifies administration, and minimizes costly downtime with key features that allow you to fully manage your entire backup data lifecycle. Now you can confidently focus on your business goals.

What is Veeam Configuration Backup?

By default, Veeam Backup & Replication is configured to create a daily configuration backup. You can change the schedule or run the backup manually.

Run the setup wizard.

To run the setup wizard:

  1. Download the latest Veeam Backup & Replication installation image from the Veeam product download page.
  2. Deploy the install image on the computer where you want to install Veeam Backup & Replication, or burn the image file to a flash drive or other removable media. If you want to install Veeam Backup & Replication on a virtual machine, use the built-in virtualization management software tools to mount the installation image on a virtual machine.
  3. To extract ISO content, you can also use the latest versions of utilities that can properly extract data from large ISO files and process it properly with long file paths.
  4. After you install the image or install your hard drive, Autorun opens a welcome screen with installation options. If Autorun is unavailable or disabled, start the Setup.exe file from the image or from your hard drive.
  5. In the Veeam Backup & Replication Welcome section, click Install.

Install Veeam Backup & Replication

Install Veeam Backup & Replication on a Microsoft Windows physical or virtual machine.

To install Veeam Backup & Replication, follow these steps:

Download the latest Veeam Backup & Replication installation image from the Veeam product download page.
You need to be logged in to your Veeam account. If you don’t have an account, register using your work email address.

  1. Deploy the installation image on the computer where you want to install Veeam Backup & Replication, or write the image file to a flash drive or other removable media.
  2. If you want to install Veeam Backup & Replication on a virtual machine, use the built-in virtualization management software tools to mount the installation image on the virtual machine.
  3. Run Setup.exe in the image or on your hard drive to open the welcome screen.
  4. In the Veeam Backup & Replication Welcome section, click Install.
  5. Leave the default settings at the “Software Features” step of the wizard.
  6. Install all missing software components on the “Check System Configuration” step of the wizard.
  7. In the default configuration step of the wizard, click “Install” to start the installation.

Select the license file and program functions

The step “Grant a license” is not obligatory. You can simply continue to install Veeam Backup & Replication and it will run in Free Edition mode. The Wizard will let you know if you already have a license on your computer.

Click Browse to provide the license file, whether it’s a trial or a purchased version. Find the * .lic file in Explorer and click Next.
Then you can select the components you want to install in the “Program Features” screen.

Veeam Backup & Replication
Veeam Backup Catalogue
Veeam Backup & Replication console

If necessary, you can click the “Browse” button to change the installation folder. Leave all three options selected and click Next to go to the system configuration check screen.

Check for Missing Software

At this stage, the wizard will check the system to make sure that all the necessary software is installed. The wizard will continue when all the necessary components are available on your computer. Otherwise, the screen of missing components will be displayed.

Select Install to install the missing components. Once the Wizard has finished installing, you will see a status screen where you can click Next to proceed to the next step. If you do not want the Wizard to install the missing components for you, exit the installation, install these components, and then run the Wizard again.

How to install and configure Veeam Backup

Step 1: Enter the PhoenixNAP Veeam Availability Console (VAC).
Step 2 – Install Veeam Management Agent.
Step 3 – Configure the management agent connection.
Step 4 – Install the Veeam Backup Agent.
Step 5 – Configure the Veeam Backup Agent and start the backup job.

The steps described in this article helped you install and configure Veaam Management Agent and Veeam Backup Agent using Veeam Availability Console.

How to install Veeam Agent

To start installing the Veeam Backup agent:

  • Log in to the Veeam service provider console.
  • Veeam Service Provider Console section.
  • From the left menu, click Managed Computers.
  • Click the Found Computers tab.
  • Select the check boxes next to the computers you need.
  • Click Install a Backup Agent.
  • The “Install Backup Agent” window opens.
  • In the “Backup policy to use” list, select the backup policy to be applied during the installation process.
  • The selected backup policy is used to configure the backup task settings after Veeam Backup agents are installed. You can select “No policy” if you do not want to configure the backup task settings during the installation process.
  • To configure a new backup policy, click “Create” and configure a new backup policy.
  • By default, the read-only access mode is enabled for all Veeam backup agents. To disable read-only access for Veeam’s backup agents, set the Enable read-only access to the user interface for the Backup Agent to Disable.
  • Backup agents. In the Enable read-only access mode section.
    To pass global settings of Veeam Backup agents, click Configure and specify the default global settings of Veeam Backup agents.
  • Click Apply.
  • Wait until the installation process is complete.
  • The installation process may take a few minutes.

How to Change Veeam Cache Location

Veeam Agent for Microsoft Windows, managed by Veeam Backup & Replication, supports the creation of recovery points in the backup cache, a temporary local storage where Veeam Agent creates backup files if the remote backup storage is unavailable. This can be useful if you are creating Veeam Agent’s backups using a backup policy: if some computers in the backup policy cannot access the remote storage during a scheduled backup, Veeam Agent creates backup files in the backup cache on those computers. When the target storage becomes available, Veeam Agent uploads the backup files from the backup cache to the remote storage so that the backup chain contains a sequence of recovery points that exactly match the backup schedule.

In Veeam Agent’s management scenario, the backup cache works the same way as Veeam Agent, which works offline. For more information, see Veeam Agent. See the “Backup Cache” section in the Veeam Agent User Guide for Microsoft Windows.

In addition to the Backup Cache features and limitations listed in the Veeam Agent for Microsoft Windows User Guide, the following applies to Veeam Agent running in managed mode:

  • You can specify backup cache settings in the Backup Policy properties that target the following types of backup stores:
  • Veeam Backup Repository
  • Cloud Repository
    • To simplify setting up the backup cache on multiple Veeam Agent computers added to your backup policy, you can instruct
    • Veeam Agent to automatically select the location of the backup cache on each computer.

Select the location of the performance cache

During the wizard performance data caching phase, select the directory where the performance cache should be located.

The performance cache is the space on the hard drive where Veeam ONE stores performance data in real time when collecting this data. Performance cached data is used for Veeam ONE Monitor dashboards and views. A performance cache on the disk can significantly reduce the amount of RAM used on the computer where the Veeam ONE Server component is running.

By default, the performance cache is stored in folder C: \ PerfCache. To store the cache in another folder, click “Browse” next to the “Performance Cache” field and specify the path to the new folder.

Consider the following recommendations when choosing a location for your performance cache:

  • Make sure that the drive where the performance cache is located can quickly process read and write requests. Do not place the remote cache on networks with high latency values.
  • In large monitoring environments, place the performance cache on the local SSD on the computer running the Veeam ONE Server component. Usually one hard drive is enough for small and medium size video surveillance systems.
  • The length of the path to the performance cache folder cannot exceed the maximum Windows path limit.
  • Make sure you have enough space for the performance cache. The cache is cleared hourly when new data is collected. However, large amounts of disk space can be used in large surveillance environments. For example, in Advanced Scalability Mode, the cache can take up to 6 GB of storage per 1000 virtual machines during peak workloads.

Specify backup cache settings

The Cache Backup Wizard step is available if you have backup files stored in a remote location: a network shared folder, Veeam’s backup repository, Veeam Cloud Connect or Microsoft OneDrive.

Specifies the settings for the backup cache:

  • Select the Include backup cache checkbox.
  • In the Location field, enter the path to the folder on your computer where you want the backup files to be saved.
  • In the Maximum size field, enter the size of the backup cache.
  • When setting the backup cache size, assume the following:
    • Each full backup file may take up about 50% of the size of the backup data.
    • Each incremental backup file may take up about 10% of the size of the backup data.

You can use a dedicated removable storage device for the backup cache, for example. B. USB stick or SD card. In this case, the backup cache does not take up space on the local disk of the computer with Veeam Agent.

Determine the location and size of the cache

During the wizard caching phase, define the settings for the folder where the service files and global cache data are stored.

  • In the “Folder” field, enter the path to the folder where the service files (for source and target WAN Accelerators) and global cache data (for target WAN Accelerators) should be stored. When selecting a folder on the target WAN
  • Accelerator, make sure there is enough room to store global cache data.
  • In the Cache size field, specify the size of the global cache. The total cache size is specified for each original WAN Accelerator.
  • If you want to use a target WAN gas pedal with multiple original WAN gas pedals, each original WAN gas pedal will be allocated the specified space and the total cache size will increase proportionally.

Select the location of the local backup cache

The Cache Backup Wizard step is available if you have backup files stored in a remote location: a network share, Veeam Backup & Replication repository or cloud storage.

Specifies the settings for the backup cache:

  1. Select the Include backup cache check box.
  2. In the Location field, enter the path to the folder on the protected computer where you want the backup cache files to be stored.
  3. In the Maximum size field, enter the size of the backup cache.
    When setting the backup cache size, remember the following:

    1. Each full backup file can take up about 50% of the size of the backup data.
    2. Each incremental backup file may take about 10% of the size of the backup data.

vPower NFS Write Cache Location

Veeam vPower NFS is used when performing instant recovery from a Veeam backup file and allows Veeam to present a compressed backup file to your ESXi host as a regular VMDK.

VPower technology allows you to perform the following functions:

  • Recovery Overview
  • Instant recovery VM
  • Immediate recovery of a virtual machine disk
  • Prepared reconstruction
  • Universal Recovery of Application Elements (U-AIR)
  • Restore at file level with multiple operating systems

The key element of vPower technology is the vPower NFS service. The vPower NFS service is a Microsoft Windows service that runs on a Microsoft Windows computer and allows that computer to act as an NFS server.

Veeam Backup & Replication creates a special directory on the vPower NFS server, the vPower NFS data warehouse. When you run a VMDK or disk of a virtual machine from backup, Veeam Backup & Replication “publishes” the VMDK files of the virtual machine from backup to the vPower NFS data warehouse. Technically, Veeam Backup & Replication simulates the presence of VMDK files in a vPower NFS data warehouse. The VMDK files themselves are still in the backup file in the backup repository.

The vPower NFS data repository is then mounted on the ESXi host. As a result, the ESXi host can “see” virtual machine images backed up by the vPower NFS data repository and work with them in the same way as with regular VMDK files. Emulated VMDK files act as pointers to real VMDK files in a backup in the backup repository.

Location of the vPower NFS Server

If you store backups in a Microsoft Windows backup repository, it is highly recommended to enable vPower NFS server in this backup repository. In this case Veeam Backup & Replication can establish a direct connection between the backup repository and ESXi where the vPower NFS data warehouse is mounted.

Veeam vPower NFS can also run on any Microsoft Windows server in the backup infrastructure, including the backup server itself. In this case, however, the performance of the recovery check may degrade. The connection between ESXi host and backup repository is divided into two parts:

From ESXi host to vPower NFS server.
From vPower NFS server to backup repository

Specify Data Locations

The Data Location wizard step is available if you have manually configured the installation options.

You can specify where to store the record cache and index data.

[For VMware environments] In the Write cache for immediate recovery section, specify the path to the IR cache folder. The IR Cache folder stores the record cache for computers that run during recovery verification or backup operations. Make sure that you have at least 10 GB of free space to store the cache record.
By default, the Installation Wizard creates an IR cache folder on a volume with maximum free space, for example. B. C: \ ProgramData \ Veeam \ Backup \ IRCache.

You do not need to configure this data location for Microsoft Hyper-V environments.

In the “Guest file system directory” section, specify the path to the folder where the index files will be stored.
By default, the installation wizard creates a VBRCatalog folder on a volume with maximum free space, for example. For example: C: \ VBRCatalog.

How to Change the vPower NFS Path

  • Immediate recovery is already performed on the server listed below, so C: already has enough disk space, and D:, E: and G: has a lot of free space. Therefore we will move the vPower NFS E : path.
  • Open Veeam Backup and select “Backup infrastructure” from the menu on the left. Then select the default backup repositories, right-click on the default backup repositories and select “Properties”.
  • The “Modify Backup Repository” dialog box will open.
  • On the left, select the vPower NFS option.
  • In the “Folder” field enter vPower NFS or go to the new path.
  • This dialog box will appear when Veeam detects an existing vPower NFS installation.
  • When you are done, click the “Finish” button.

Does Veeam Use SQL Server?

As database servers and other Tier 1 applications are virtualized, organizations need to be able to recover data at any given time, minimize the impact on end users and ensure business continuity. Consequently, backup and recovery strategies are more important for applications with high transaction rates.

Veeam Backup & Replication provides flexible backup options and a variety of recovery approaches for virtualized SQL Server and databases, including the popular full SQL Server virtual machine recovery, file-level recovery and basic recovery.

To properly configure a backup job that backs up with consistent transactions and enables you to restore SQL Server databases in the future, you must understand how the backup processes implemented by Veeam work.

Veeam Backup & Replication backs up all SQL Server, including all SQL Server instances and databases. This can be a full incremental, incremental or reverse backup (depending on the selected backup method). Own SQL means running backups for each database, as well as creating full and differential backups. Please note that these custom SQL backup types do not in any way match Veeam’s backup methods. In this regard, please note that Veeam Backup & Replication performs the following steps when creating backups at the image level of applications:

Create a backup at the image level of your SQL Server virtual machine, including all hosted instances and databases and their associated settings, and save them to the backup repository in the proprietary Veeam format: .VBK (full backup virtual machine), .VIB (incremental) or. VRB (inverted in steps).
When the transaction log management option is selected, Veeam Backup & Replication retrieves the transaction log (.BAK) backup files created initially and saves them with Veeam Log Shipping Server to the address where the virtual machine backup is stored. . These log backups are saved in Veeam’s own format (.VLB).

Does Veeam Require SQL?

If necessary, you can change the installation folder.

Veeam Backup & Replication requires Microsoft .NET Framework 4 and Microsoft SQL Server (.NET Framework 4 and Microsoft SQL Server 2008 R2 Express are included in the configuration). If you want to install these components together with the configuration, you must have at least 2 GB of free space on your system hard drive.

Can Veeam Perform SQL Server Backups?

Veeam supports two types of SQL Server backups:

Snapshot backup. As explained above, this is a snapshot of the entire machine since the snapshot was created. SQL Server databases are in a consistent state thanks to the snapshot created with the SQL Server VSS Writer service.

Transaction log backups. You can add transaction log backups to your instant backups. As we will see, Veeam creates log backups into files using the normal BACKUP LOG command and then copies the log backup files to the Veeam backup repository. Transaction log backups are performed only for databases that are in the full or mass recovery model. So make sure that you have the desired recovery model for your database.

Which Database Does Veeam Use?

Veeam Agent for Microsoft Windows can be used in managed mode to create transaction-compliant backups of servers running applications that support Microsoft VSS. The system requirements for VSS-compatible processing are listed in the following table.

Domain Controller for Microsoft Active Directory

The following versions of Microsoft Active Directory domain service servers (domain controllers) are supported:

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008 R2 with Service Pack 1 (SP1)
  • The minimum supported functional level for domain and forest is Windows 2003.

Microsoft Exchange

The following versions of Microsoft Exchange are supported:

  • Microsoft Exchange 2019
  • Microsoft Exchange 2016
  • Microsoft Exchange 2013 with Service Pack 1 (SP1)
  • Microsoft Exchange 2013
  • Microsoft Exchange 2010 SP1, SP2 or SP3

Microsoft Sharepoint

The following versions of Microsoft SharePoint are supported:

  • Microsoft SharePoint 2019
  • Microsoft SharePoint 2016
  • Microsoft SharePoint 2013
  • Microsoft SharePoint 2010

All editions (Foundation, Standard, Enterprise) are supported.

Microsoft SQL Server

The following versions of Microsoft SQL Server are supported:

  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2008 R2
  • Microsoft SQL Server 2008
  • Microsoft SQL Server 2005 with Service Pack 4 (SP4)

All Microsoft SQL Server editions are supported, except LocalDB.


Oracle Database 11g – 19c versions are supported for the following operating systems (32-bit and 64-bit architecture):

  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008 R2 with Service Pack 1 (SP1)

How can I back up and restore a SQL Server database?

To make a backup of your database, follow these steps:

  • Start SQL Server Management Studio (SSMS) and connect to your SQL Server instance.
  • Expand the Databases node in the object browser.
  • Right-click the database, point the mouse pointer at the tasks and select Save…
  • In the Destination section, make sure that the path to the backup copy is correct. If you need to change this, select “Delete” to delete an existing path, then select “Add” to enter a new path. You can use an ellipsis to navigate to a specific file.
  • Click OK to create a backup of your database.

Veeam Installation and Deployment Step by Step Guide

Veeam Backup & Replication is a software product developed by Veeam Software for backup, recovery and replication of data in virtual machines (VM). It was first released in 2008 and is part of the Veeam Availability Suite.

Veeam was one of the first to develop virtual machine backup software. Prior to Veeam, backup applications could not differentiate between physical and virtual machine protection.

Veeam Backup & Replication software is compatible with a wide range of backup destinations and can be used with VMware vSphere and Microsoft Hyper-V. The product operates at the virtualization level and has no agents. According to the vendor, the software has a target recovery time of less than 15 minutes for all applications and uses built-in WAN acceleration to replicate data off-site up to 50 times faster than raw data transfers.

To work with Veeam Backup & Replication, you need to configure a backup server. Install Veeam Backup & Replication on a computer that meets the system requirements. This can be done using the installation wizard or by installing the product in unattended mode.

When installing Veeam Backup & Replication, the Veeam Backup & Replication console is automatically installed on the backup server. If you want to remotely access Veeam Backup & Replication, you can install Veeam Backup & Replication Console on a dedicated computer.

How to Deploy Veeam

Check the prerequisites before installing Veeam Backup & Replication.

  • The computer on which you plan to install Veeam Backup & Replication must meet the system requirements.
  • The user account you want to use for installation must have sufficient permissions. F.
  • The backup infrastructure components communicate with each other through specific ports. These ports must be open.
  • Veeam Backup & Replication requires Microsoft SQL Server to be deployed locally on a backup server or remotely. If Microsoft SQL Server is not installed, the Veeam Backup & Replication installer installs it locally on the backup server.
  • If Microsoft SQL Server is installed with a previous version of the product, Veeam Backup & Replication connects to the existing configuration database, updates it (if necessary) and uses it to work.
  • You must remove Veeam Backup & Replication components from versions that are not supported by the target machine upgrade process. You may also need to uninstall previous versions of other Veeam products and components.

Can I Install Veeam on a Virtual Machine?

You can install Veeam on a virtual machine or physical system – the best solution depends only on your virtual environment.

If you have a large VMware Hyper-V virtual environment with heavy production servers, we usually recommend installing Veeam on a physical machine.

How to Configure Veeam Replication

To create a replication task:

  1. On the Home tab, click Replication Job and select Virtual Machine> VMware vSphere or Virtual Machine> Microsoft Hyper-V.
  2. In the Name step of the wizard, provide a name and description for the replication job.
    If you want to use advanced settings to work:

    1. Check the Replica Seeding checkbox to activate the seeding step in the wizard.
    2. Select the Network Reassignment check box to activate the Network step in the wizard. Veeam Backup & Replication does not currently support automatic connection of a Linux VM replica to the network on a cloud host. To manually select the source and target networks for these replicas, you must use the Networking step of the wizard.
    3. Veeam Backup & Replication does not support IP reassignment rules for VM replicas on a cloud host. Do not select the Re-IP Replica check box for a replication job targeting a cloud host. If you select the Re-IP Replica option, this option will be disabled when you select a cloud host in the Assign step of the wizard.
    4. In the Virtual Machines step of the wizard, click Add and select the virtual machines and virtual machine containers that you want to replicate. Use the search box at the bottom of the Add Items window to quickly find the item you want.
    5. To specify the source from which the virtual machine data should be read, click Source and select one of the following options:
    6. From the production warehouse. In this case, Veeam Backup & Replication fetches the virtual machine data from the production storage connected to the original virtualization host.
    7. From backup files. In this case, Veeam Backup & Replication reads the VM data from a backup chain that already exists in a regular backup repository or cloud backup repository.
    8. If you want to exclude virtual machines from the virtual machine container or replicate only specific virtual machine disks, click Exclusions and specify the objects to exclude.
    9. If you want to set the order in which the replication task should process virtual machines, select the virtual machine or virtual machine container added to the task and use the Up and Down buttons to move the virtual machine or machine container. virtual to the top or bottom list.
    10. In the Assign step of the wizard, under Host or Cluster, click Select and select Cloud Host. Then select the cloud host assigned to you by your service provider:
    11. If you selected an SP assigned to replication resources on a VMware vSphere or Microsoft Hyper-V host, select the cloud host provided to you through the hardware plan.
    12. If the SP has assigned you replication resources in VMware vCloud Director, select a cloud host that will serve you through the organization’s vDC.
  3. In the wizard assignment step, select the storage resources assigned to you by your service provider:
  4. To set up VMware replication. If you want to specify a datastore for storing virtual machine replicas, in the Datastore section, click Select and select the datastore you want.
  5. [To set up Hyper-V replication] If you want to specify the path to the storage where you want to store the replica of the virtual machines, click Select in the Path section and select the storage you need.
  6. [To specify replication for vCloud Director] To specify a vApp or retention policy for replica virtual machines, follow these steps:
  7. In the vApp section, click Select and select the required vApp.
    In the Retention Policy section, click Select and select the desired retention policy.
  8. In the Networking step of the wizard, in the Network Mapping section, click Add and select the production network to which the virtual machines are connected in the task and the network on the cloud host to which the replica virtual machines should be connected. Repeat this step for each network to which the replica Linux virtual machines should be connected. Automatic network mapping for non-Windows VMs is currently not supported in Veeam Cloud Connect Replication.
  9. In the “Job Parameters” step of the wizard, in the Replication Metadata Repository list, select the standard backup repository configured in your backup infrastructure. Veeam Backup & Replication stores the checksums of the read data blocks in the metadata of the selected backup repository for virtual machine replicas, which are necessary to optimize the incremental execution of the replication job.
  10. In the Replica name suffix box, enter the suffix for the virtual machine replica name. To register a replica VM on the target host of the SP site, Veeam Backup & Replication adds the specified suffix to the name of the source VM.
    In the Recovery points to save field, specify the number of recovery points that the replication task should manage. If this number is exceeded, the oldest recovery point is deleted.
  11. In the data transfer wizard step, select the backup infrastructure components that will be used in the replication process and select the path for transferring the virtual machine data:
  12. Next to the Source Proxy Server box, click Select to select the source backup proxy for the job. In the Backup Proxy section, you can choose to automatically select a backup proxy or explicitly designate a source backup proxy.
    You cannot specify a target backup proxy for a replication job that targets a cloud host. When performing a replication job, Veeam Backup & Replication automatically selects the target backup proxy configured by the service provider in the Veeam Backup & Replication SP infrastructure.
  13. To transfer data from the virtual machine directly to the cloud host through one or more backup proxy servers, select “Direct”.
  14. To transfer VM data through WAN Accelerators, select “Via built-in WAN Accelerators”. In the Source WAN Accelerator field, select the WAN gas pedal that you have configured on your side.
  15. During the initial boot of the wizard, configure the replication fill and match for the replication job.
    In the Startup section, select the “Get Startup from next Backup Repository” checkbox. From the list of backup repositories, select a normal backup repository or a cloud repository containing the initial (full backup) copy. When you run a replication task, Veeam Backup & Replication tries to restore all VMs added to the task with the initial value you set.
  16. If no virtual machine is found in the seed, the replication skips the virtual machine.
  17. In the “Match replicas” section, check the “Match replicas to existing virtual machines” box, select a production virtual machine from the list, click “Edit” and select an existing replica of the virtual machine. Matching replicas reduces the amount of virtual machine data transferred over the network during the first session of the replication task.
  18. At the wizard’s guest processing stage, check the Enable processing checkbox that supports applications for creating replicas of virtual machines with consistent transactions. When application support is enabled, Veeam Backup & Replication can most effectively detect the network settings of replicated virtual machines and use the discovered settings to configure network expansion devices.
  19. Next to the list of credentials, click “Add” and specify the credentials for a user account with local administrator rights in the guest virtual machine. By default, Veeam Backup & Replication uses the same credentials for all virtual machines added to the job. If a virtual machine requires a different user account, click Credentials and enter the user credentials for the desired virtual machine.
  20. Click “Applications”, select the desired virtual machine and click “Edit”. On the General tab, under Applications, specify a
  21. VSS behavior scenario:
    Select Require Processing for successful execution if you want Veeam Backup & Replication to stop the backup process when
  22. VSS errors occur.
    Select “Try processing the application”, but ignore the errors if you want to continue the backup process even if VSS errors occur. This option is recommended to ensure completion. The backup image you have created does not match the transactions, but it matches the failures.
    Select Disable application processing if you do not want to enable the VSS standby mode at all.
  23. [For Microsoft SQL and Oracle virtual machines] Under “Transaction logs”, specify how Veeam Backup & Replication will process transaction logs.
  24. Select Process transaction logs with this task if you want Veeam Backup & Replication to process transaction logs. When this option is enabled, Veeam Backup & Replication provides you with a choice of transaction log processing options on the SQL and Oracle tabs.
  25. Select Copy only if you use your own enforcement tools or a third-party tool to process the transaction logs. Veeam Backup & Replication backs up only for the selected VM. Backup for backup only supports a chain of full / differential backup files and transaction logs.
  26. On the Schedule step of the wizard, select the “Run job automatically” checkbox and specify the necessary schedule options for the job. If you do not check this box, you will need to manually launch the replication task to create recovery points for virtual machine replicas in the cloud.
  27. At the Summary step of the wizard, select the “Run this task when I click” Done checkbox ” if you want to run the created task right after finishing the wizard.
  28. Click Finish.

Which of the following are the most important components of Veeam Backup & Replication?

You can use Veeam Backup & Replication in virtual environments of any size and complexity. The solution architecture supports data protection both within and outside the enterprise, as well as work in remote and geographically dispersed sites. Veeam Backup & Replication offers flexible scalability and easily adapts to the needs of your virtual environment.

Veeam Backup & Replication supports multiple deployment scenarios, each of which contains the core infrastructure components: a backup server, a backup proxy, and a backup repository. Depending on the size of your virtual environment, you can use one of the following scenarios:

Simple deployment
For small virtual environments. In this scenario, the roles of all components required for data protection tasks are assigned to the computer.

Advanced deployment
For medium to large virtual environments. In this scenario, the roles of the components required for data protection tasks are assigned to dedicated computers.

Veeam Backup & Replication also supports a distributed deployment scenario for large geographically dispersed environments with multiple backup servers. We do not provide a detailed description of this scenario as this guide provides a quick overview of the main functions.