Veeam Backup Replication On Flexible Engine Deployment Guide
Veeam Backup Replication On Flexible Engine Deployment Guide
Objectives
This guide is intended to provide best practices for deployment of a software-defined data protection solution,
Veeam Backup & Replication can be flexibly deployed at any scale in Flexible Engine environment. It is not
meant as a full documentation or detailed explanation of features. Please refer to Veeam documentation for
complete and up to date information.
Veeam Software offers the following types of licenses for Veeam Backup & Replication:
Paid Licenses
Subscription license — license that expires at the end of the subscription term. The Subscription license
term is normally 1-3 years from the date of license issue.
Perpetual license — permanent license. The support and maintenance period included with the license
is specified in months or years. Typically, one year of basic support and maintenance is included with
the Perpetual license.
Rental license — license with the license expiration date set according to the chosen rental program
(normally 1-12 months from the date of license issue). The Rental license can be automatically updated
upon expiration.
Rental licenses are provided to Veeam Cloud & Service Provides (VCSPs) only. For more information, see
the Rental License section in the Veeam Cloud Connect Guide.
You will be requested to enter the Veeam license file during the configuration.
The consumption of Flexible Engine resources including ECS for VBR & storage used as a backup repository is
purchased at standard pricing.
2.1. Pre-requisites
Before deploying a Veeam Backup & Replication Server on Flexible Engine, you must define compute
requirements for VBR Server corresponding to your needs.
Compute Requirements
Recommended Veeam backup server configuration is 1 vCPU and 4 GB RAM per 10 concurrently
running jobs. Concurrent jobs include any running backup or replication jobs as well as any job
with a continuous schedule such as backup copy jobs.
Disk space
Installation folder
Plan for a minimum of 40 GB. If installing in a virtual machine, thin disks may be used. By default
the installer will choose the drive with most available free space for the pre-configured Default
Backup Repository.
Log files
Log file growth will depend on the number and frequency of jobs and the number of instances
being protected. Consider that the logging level may also affect the log size.
Plan for 3 GB log files generated per 100 protected instances, with a 24 hour RPO. For
environments with more than 500 protected instances it is recommended to change the default
location to a different fast access disk. Many concurrently running jobs may produce a lot of write
streams to log files, that can slow down operations for the Veeam Backup Service and Backup
Manager processes.
Plan for 10 GB per 100 ECS for guest file system catalog folder (persistent data).
A backup repository is a storage location where Veeam keeps backup files, Agent based backups, VM copies
and metadata for replicated VMs.
To configure a backup repository, you can use the following storage types however all repository types are
not configurable in Public cloud environment:
2.1.3.1. Infrastructure
For infrastructure components like ECS, EVS Volume, Network etc. the Flexible Engine limitations apply.
2.1.3.3. Backup
Since on Public cloud you don’t have access to hypervisor so to backup workloads like ECS, you need deploy
Veeam agent for Linux & Veeam Agent for Windows.
The sizing for the disk repositories differs based on the stored data & its retention (how long you want to keep
the data). The sizing calculator can you help you size the repository correctly.
To be able to store backups on a backup repository managed by a Veeam backup server, the user must have
access permissions on this backup repository.
Access permissions are granted to security principals such as users and AD groups by the backup administrator
working with Veeam Backup & Replication. Users with granted access permissions can target Veeam Agent
backup jobs at this backup repository and perform restore from backups located on this backup repository.
If the Veeam Backup Jobs are created from Veeam Backup & Replication Server instead of Agent then you do
not need to grant access permissions on the backup repository to users.
After you create a new backup repository, access permissions on this repository are set to Deny to everyone.
To allow users to store backups on the backup repository, you must grant users with access permissions to this
repository.
4. Select any flavor starting with minimum 2vCPU and 4GB RAM
Select required VPC based on tenants to backup & Security Group for inbound/outbound rules :
Provide ECS name as desired and choose key pair to generate secure password for login :
Once you login, you will see an icon for VBR (Veeam Backup & Replication) console on the
desktop to launch Veeam. Just click on connect to use Windows session authentication :
Initially the VBR server will be deployed with a Default Repository as below on C:\Backups, it is always
recommended to use a separate Drive other than system drive to create the backup repository. You can
achieve this by attaching another Disk (EVS) to your ECS :
Click on Create Disk in case of a new EVS volume or click on View Disk to attach an existing EVS volume.
Creating a new local backup repository and using it as an extent for Scale Out Backup Repository with S3 bucket
from Flexible Engine :
Click on BACKUP INFRASTRUCTURE -> Backup Repositories -> right click and Add backup repository…
Click on Direct Attached Storage -> Microsoft Windows as the option since it is the local attached Drive on the
ECS :
Right click on Scale-out Repositories and click on Add scale-out backup repository…
Since direct writing to S3 Object Storage is yet not supported with Veeam hence it needs a tier to be defined,
we will be using local repository as performance tier and stage backups to S3 for larger retention at lower cost.
Select the newly created Repository “Backup Repository 1” :
Now click on Next and Select Data Locality to keep the backup chains together “ Full + Incrementals”
Click on Next and Click on Add to add the extent of S3 Object Storage to Scale Out Backup Repository as next
Tier :
Now you will see the buckets created under the S3 account you are using and create a new folder under which
you want to store backups by clicking on Browse.
You can also limit S3 Object Storage consumption using the checkbox highlighted below.
You can now specify this Scale-out Object Repository in Backup job and let Veeam manage the staging of data
from local disk to S3 bucket using the policy you specified during SoBR creation: