Veeam Backup for Proxmox

VE

Version 1
User Guide
April, 2025
© 2025 Veeam Software.

All rights reserved. All trademarks are the property of their respective owners.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language in any form by any means, without written permission from Veeam Software
(Veeam). The information contained in this document represents the current view of Veeam on the issue
discussed as of the date of publication and is subject to change without notice. Veeam shall not be liable for
technical or editorial errors or omissions contained herein. Veeam makes no warranties, express or implied, in
this document. Veeam may have patents, patent applications, trademark, copyright, or other intellectual
property rights covering the subject matter of this document. All other trademarks mentioned herein are the
property of their respective owners. Except as expressly provided in any written license agreement from Veeam,
the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.

NOTE
Read the End User Software License Agreement before using the accompanying software programs. Using
any part of the software indicates that you accept the terms of the End User Software License Agreement.

2 | V eeam Backup for Proxmox VE | User Guide

Contents
CONTACTING VEEAM SOF TWARE ................................ ................................ ........................... 6
OVERVIEW ................................ ................................ ................................ ...................... 7
Solution Architecture ............................................................................................................................ 8
VM Back up ......................................................................................................................................... 10
Backup Chain ............................................................................................................................. 11
Backup Methods ........................................................................................................................14
Active Full Backup .....................................................................................................................16
Synthetic Full Backup ................................................................................................................. 17
VM Restore .........................................................................................................................................19
Entire VM Restore ..................................................................................................................... 20
File-Level Recovery ................................................................................................................... 21
Retention Policies ............................................................................................................................... 22
PLANNING AND P REPARATION ................................ ................................ ............................. 23
System Requirements ......................................................................................................................... 24
Considerations a nd Limitations ............................................................................................................ 25
Account Permissions ........................................................................................................................... 27
Ports .................................................................................................................................................. 28
LICENSING ................................ ................................ ................................ .................... 30
DEPLOY MENT ................................ ................................ ................................ ................. 31
Installing Proxmox VE Plug-in Manually ............................................................................................... 32
CONFIGURING VEE AM BACKUP FOR PROXMOX VE ................................ ................................ ......34
Configuring Backup Repositories ......................................................................................................... 35
Connecting Proxmox VE Server ........................................................................................................... 36
Adding Proxmox VE Server to Backup Infrastructure ................................................................... 37
Editing Proxmox VE Server Properties ........................................................................................ 44
Rescanning Prox mox VE Server .................................................................................................. 45
Removing Proxmox VE Server .................................................................................................... 46
Managing Workers .............................................................................................................................. 47
Adding Workers ........................................................................................................................ 48
Testing Workers........................................................................................................................ 55
Enabling and Disabling Workers ................................................................................................. 56
Editing Workers ........................................................................................................................ 57
Disabling Automatic Worker Updates ......................................................................................... 58
Removing Workers .................................................................................................................... 59
Configuring General Settings ...............................................................................................................60
Configuring Email Settings .........................................................................................................61
Configuring Notification Settings ............................................................................................... 65

3 | V eeam Backup for Proxmox VE | User Guide

PERFORMING BACKUP ................................ ................................ ................................ .......67
Creating Backup Jobs .......................................................................................................................... 68
Before Y ou Begin ...................................................................................................................... 69
Step 1. La unch New Backup Job Wizard ...................................................................................... 70
Step 2. Specify Job Name and Description ................................................................................... 71
Step 3. Configure Backup Source Settings .................................................................................. 72
Step 4. Specify Backup Job Settings ........................................................................................... 76
Step 5. Define Job Schedule ...................................................................................................... 82
Step 6. Finish W orking with Wizard ............................................................................................ 83
Starting and Stopping Backup Jobs ...................................................................................................... 84
Retrying Jobs ..................................................................................................................................... 85
Editing Backup Job Settings ................................................................................................................ 86
Analyzing Performa nce Bottlenecks..................................................................................................... 87
Cloning Backup Jobs ........................................................................................................................... 89
Enabling and Disabling Backup Jobs ....................................................................................................90
Deleting Backup Jobs...........................................................................................................................91
Creating Active Full Backups ............................................................................................................... 92
Creating VeeamZIP Backups ................................................................................................................ 93
MANAGING BACKUPS ................................ ................................ ................................ ....... 94
Viewing Back up Properties .................................................................................................................. 95
Verifying Backups ............................................................................................................................... 96
Exporting Backups .............................................................................................................................. 97
Copying Backups ................................................................................................................................ 98
Copying Backups to Tapes ................................................................................................................... 99
Deleting Backups .............................................................................................................................. 100
PERFORMING RESTORE ................................ ................................ ................................ .....101
Performing VM Restore ......................................................................................................................102
Step 1. La unch E ntire VM Restore Wizard ..................................................................................103
Step 2. Select Restore P oint .................................................................................................... 104
Step 3. Choose Restore Mode ...................................................................................................105
Step 4. Specify Target Host ..................................................................................................... 106
Step 5. Select Storage ..............................................................................................................107
Step 6. Specify VM Name ........................................................................................................ 108
Step 7. Configure Network Settings ......................................................................................... 109
Step 8. Specify Restore Reason................................................................................................. 110
Step 9. Finish W orking with Wizard ............................................................................................ 111
Performing Instant VM Recovery .........................................................................................................112
Publishing Disks .................................................................................................................................113
Performing File -Level Restore ............................................................................................................ 114
Performing Application Item Restore .................................................................................................. 116

4 | V eeam Backup for Proxmox VE | User Guide

 Exporting Disks ................................................................................................................................. 118
Performing VM Restore to Amazon Web Services ................................................................................ 119
Performing VM Restore to Microsoft Azure .........................................................................................120
Performing VM Restore to Google Cloud ..............................................................................................121
GETTING TECHNICAL SUPPORT................................ ................................ ............................ 122
APPENDIX. CONFIGURING MULTIPLE NETW ORKS ................................ ................................ ..... 124

5 | V eeam Backup for Proxmox VE | User Guide

Contacting Veeam Software
At Veeam Software we value feedback from our customers. It is important not only to help you quickly with your
technical issues, but it is our mission to listen to your input and build products that incorporate your
suggestions.

Customer Support
Should you have a technical concern, suggestion or question, visit the Veeam Customer Support Portal to open a
case, search our knowledge base, reference documentation, manage your license or obtain the latest product
release.

Company Contacts
For the most up-to-date information about company contacts and office locations, visit the Veeam Contacts
Webpage.

Online Support
If you have any questions about Veeam products, you can use the following resources:

• Full documentation set: veeam.com/documentation-guides-datasheets.html

• Veeam R&D Forums: forums.veeam.com

6 | V eeam Backup for Proxmox VE | User Guide

Overview
Veeam Backup for Proxmox VE is a solution developed for protection and disaster recovery tasks for Proxmox
Virtual Environment (Proxmox VE). With Veeam Backup for Proxmox VE, you can perform the following
operations:

• Create backups of Proxmox VE VMs and store them in backup repositories.

• Create VeeamZIP backups of Proxmox VE VMs.

• Create several instances (copies) of the same backup data in different locations.

• Restore VMs from Proxmox VE VM backups to the Proxmox VE environment.

• Restore VMs from VMware ESXi and Microsoft Hyper-V to the Proxmox VE environment.

• Restore VMs from Nutanix AHV and oVirt KVM backups to the Proxmox VE environment.

• Restore VMs from Microsoft Azure, Amazon Web Services (AWS) and Google Cloud backups to the
Proxmox VE environment.

• Restore physical machines from backups created by Veeam Agents to the Proxmox VE environment.

• Restore VMs from Proxmox VE backups to Microsoft Azure, Amazon Web Services (AWS) and Google
Cloud environments.

• Perform Instant Recovery of Proxmox VE VMs to VMware vSphere and Microsoft Hyper-V environments.

• Restore application items (such as Microsoft Active Directory, Microsoft Exchange, Microsoft SharePoint,
Oracle Database and Microsoft SQL Server).

• Restore files and folders of Proxmox VE VM guest OSes.

• Export disks of backed-up Proxmox VE VMs to VMDK, VHD and VHDX formats.

• Mount disks of backed-up Proxmox VE VMs to any server and access data in the read -only mode.

7 | V eeam Backup for Proxmox VE | User Guide

Solution Architecture
The Veeam Backup for Proxmox VE architecture comprises the following set of components:

• Proxmox VE server

• Backup server

• Proxmox VE Plug-in

• Backup repositories

• Workers

Proxmox VE Server
A Proxmox VE server is standalone host or cluster node that runs the Proxmox VE software. Veeam Backup for
Proxmox VE uses the server to access such Proxmox VE resources as storage, networks and VMs while
performing backup and restore operations.

Backup Server
A backup server is a Windows-based physical or virtual machine on which Veeam Backup & Replication is
installed. The backup server is the configuration, administration and management core of the backup
infrastructure. It coordinates backup and restore operations, controls job scheduling and manages resource
allocation.

Proxmox VE Plug-in
Proxmox VE Plug-in is an architecture component that enables integration between the backup server and the
Proxmox VE server. Proxmox VE Plug-in also allows the backup server to deploy and manage workers.

Backup Repositories
A backup repository is a storage location where Veeam Backup for Proxmox VE stores backups of protected
Proxmox VE VMs.

To communicate with backup repositories, Veeam Backup for Proxmox VE uses Veeam Data Mover — the service
that is responsible for data processing and transfer. By default, Veeam Data Mover runs on the repositories
themselves. If a repository cannot host Veeam Data Mover, it starts on a gateway server — a dedicated
component that “bridges” the backup server and workers. For more information, see the
Veeam Backup & Replication User Guide, section Gateway Server.

8 | V eeam Backup for Proxmox VE | User Guide

Workers
A worker is a Linux-based VM that resides on the Proxmox VE host and processes backup workloads when
transferring data to and from backup repositories.

9 | V eeam Backup for Proxmox VE | User Guide

VM Backup
To produce backups of VMs, Veeam Backup for Proxmox VE runs backup jobs. A backup job is a collection of
settings that define the way backup operations are performed: what data to back up, where to store backups,
when to start the backup process, and so on.

Veeam Backup for Proxmox VE does not install agent software inside VMs to back up VM data — it uses native
Proxmox VE capabilities instead. During every backup session, Veeam Backup for Proxmox VE creates a Proxmox
VE copy-on-write snapshot of each VM added to a backup job. The snapshot is further used to create a VM
backup.

How to Protect VMs

1. Check system requirements and account permissions.

2. Add backup repositories.

3. Connect the Proxmox VE server.

4. Configure worker settings.

5. Configure email settings and notifications.

6. Complete the New Backup Job wizard.

How VM Backup Works

Veeam Backup for Proxmox VE performs VM backup in the following way:

1. Launches a worker on the same host where the processed VM resides.

If no worker is deployed on the host, Veeam Backup for Proxmox VE launches a worker that is deployed on
any other Proxmox VE host connected to the backup infrastructure.

2. Connects to the Proxmox VE server and creates a copy-on-write snapshot of the processed VM.

3. Uses the worker to read data from disks that are attached to the processed VM, compares it to the data
written to the snapshot created at the step 2, excludes the changes and transfers the resulting data to the
target repository — and stores it in the native Veeam format.

To reduce the amount of data read from VM disks, Veeam Backup for Proxmox VE uses the changed block
tracking (CBT) mechanism: during incremental backup sessions, Veeam Backup for Proxmox VE compares
the current disk content with the backed-up content and reads only those data blocks that have changed
since the previous backup session. If CBT cannot be used, Veeam Backup for Proxmox VE reads all data
from the VM disks. For more information, see Changed Block Tracking.

Veeam Backup for Proxmox VE compresses and deduplicates data saved to repositories.

4. Removes the created snapshot and suspends the worker when the backup ses sion completes.

10 | V eeam Backup for Proxmox VE | User Guide

Backup Chain
Veeam Backup for Proxmox VE creates a new backup file in a backup repository during every backup session. A
sequence of backup files created during a set of backup sessions makes up a backup chain. Each backup chain
contains data for one VM only. If a backup job includes several VMs, Veeam Backup for Proxmox VE creates one
backup chain for each VM processed by the job.

The backup chain includes backup files of the following types:

• VBK — a full backup file stores a copy of the full VM image.

• VIB — incremental backup files store incremental changes of the VM image.

• VBM — backup metadata files store information about the backup job, VMs processed by the backup job,
number and structure of backup files, restore points, and so on. Metadata files facilitate import of
backups, backup mapping and other operations.

Full and incremental backup files act as restore points for backed -up VMs that let you roll back VM data to the
necessary state. To recover a VM to a specific point in time, the chain of backup files created for the VM must
contain a full backup file and a set of incremental backup files dependent on the full backup file.

If some file in the backup chain is missing, you will not be able to roll back to the necessary state. For t his
reason, you must not delete individual backup files from the backup repository manually. Instead, you must
specify retention policy settings that will let you maintain the necessary number of backup files in the backup
repository. For more information, see Backup Retention.

Changed Block Tracking

The changed block tracking (CBT) mechanism allows Veeam Backup for Proxmox VE to reduce the amount of
data read from processed VMs, and to increase the speed and efficiency of incr emental backups:

• During a full backup session Veeam Backup for Proxmox VE reads only written data blocks, while
unallocated data blocks are filtered out.

• During an incremental backup session, Veeam Backup for Proxmox VE reads only those data blocks that
have changed since the previous backup session.

To detect unallocated and changed data blocks, CBT relies on the QEMU Dirty Bitmaps functionality:

1. During the first (full) backup session, Veeam Backup for Proxmox VE creates a bitmap for each disk that is
attached to a processed VM.

2. During subsequent sessions, Veeam Backup for Proxmox VE uses the created bitmaps to compare the
contents of disks backed up during the previous backup session and the current disk contents. This allows
Veeam Backup for Proxmox VE to detect data blocks that have changed since the previous backup session.
As soon as a new backup is created, Veeam Backup for Proxmox VE updates the bitmaps to include the
latest changes.

Limitations for Changed Block Tracking

Due to Proxmox VE technical limitations, bitmaps created for disks in the RAW and VMDK formats are
automatically removed as soon as VMs that have these disks attached are powered off or restarted. Therefore,
Veeam Backup for Proxmox VE may not be able to use CBT when processing those VMs and trying to detect data
blocks that have changed since the previous backup session. If CBT cannot be used, Veeam Backup for Proxmox
VE reads the whole content of VM disks and compares it with backed-up data that already exists in backup
repositories. In this case, the completion time of incremental backups may occur to grow.

11 | V eeam Backup for Proxmox VE | User Guide

 NOTE

This limitation does not apply to disks in the QCOW2 format.

Backup Retention
Veeam Backup for Proxmox VE retains the number of latest restore points defined in job scheduling settings as
described in section Creating Backup Jobs. For backup chains created by jobs without scheduled active or
synthetic full backups, Veeam Backup for Proxmox VE applies forever forward incremental backup retention
policy. For backup chains created by jobs that regularly produce active or synthetic full backups, Veeam Backup
for Proxmox VE applies forward incremental backup retention policy.

NOTE

For backup chains created by jobs that no longer exist, Veeam Backup for Proxmox VE applies a separate
retention mechanism as described in the Veeam Backup & Replication User Guide, section Background
Retention.

Forever Forward Incremental Backup Retention Policy

To track and remove redundant restore points from a forever forward incremental backup chain, Veeam Backup
for Proxmox VE performs the following actions once a day:

1. Veeam Backup for Proxmox VE checks the configuration database to detect backup chains where the
number of allowed restore points is exceeded.

o If retention policy is specified in days, Veeam Backup for Proxmox VE detects backup chains with
restore points that are older than the specified time limit.

o If retention policy is specified in restore points, Veeam Backup for Proxmox VE detects backup chains
where the number of allowed restore points is exceeded.

2. If a redundant restore point exists in a backup chain, Veeam Backup for Proxmox VE transforms the
backup chain in the following way:

a. Rebuilds the full backup to include there data of the incremental backup that follows the full backup.
To do that, Veeam Backup for Proxmox VE injects into the full backup data blocks from the earliest
incremental backup in the chain. This way, the full backup ‘moves’ forward in the standard backup
chain.

b. Removes the earliest incremental backup from the chain as redundant — this data has already been
injected into the full backup.

12 | V eeam Backup for Proxmox VE | User Guide

 3. Veeam Backup for Proxmox VE repeats step 2 for all other redundant restore points found in the backup
chain until all the restore points are removed. As data from multiple restore points is injected into the
rebuilt full backup, Veeam Backup for Proxmox VE ensures that the backup chain is not broken and that
you will be able to recover your data when needed.

Forward Incremental Backup Retention Policy

To track and remove redundant restore points from a forward incremental backup chain, Veeam Backup for
Proxmox VE performs the following actions once a day:

1. Veeam Backup for Proxmox VE checks the configuration database to detect forward incremental backup
chains where a new full backup has been created (which starts a new backup chain fragment).

2. Veeam Backup for Proxmox VE checks the following:

o If retention policy is specified in days, Veeam Backup for Proxmox VE checks whether the period to
keep restore points in the new chain fragment has reached the allowed time limit.

o If retention policy is specified in restore points, Veeam Backup for Proxmox VE checks whether the
number of restore points in the new chain fragment has reached the number of allowed restore
points.

3. If the new backup chain fragment has reached the limit of allowed restore points, Veeam Backup for
Proxmox VE removes all restore points of the older backup chain fragment.

13 | V eeam Backup for Proxmox VE | User Guide

Backup Methods
Veeam Backup for Proxmox VE provides the following methods for creating backup chains:

• Forever forward incremental

When the forever forward incremental backup method is used, Veeam Backup for Proxmox VE creates a
backup chain that consists of the first full backup file (VBK) and a set of forward incremental backup files
(VIBs) following it. For more information, see Forever Forward Incremental Backup.

This backup method helps you save space on the backup storage because Veeam Backup for Proxmox VE
stores only one full backup file and removes incremental backup files once the retention period is
exceeded.

• Forward incremental

When the forward incremental backup method is used, Veeam Backup for Proxmox VE creates a backup
chain that consists of multiple full backup files (VBKs) and sets of forward incremental backup files (VIBs)
following each full backup file. Full backups created using the synthetic full or active full method split the
backup chain into shorter series. This lowers the chances of losing the backup chain completely and makes
this backup method the most reliable. For more information, see Forward Incremental Backup.

This backup method requires more storage space than other methods because the backup chains contains
multiple full backup files and sometimes Veeam Backup for Proxmox VE stores more restore points than
specified in the retention policy settings due to the specifics of the forward incremental retention policy.

Forever Forward Incremental Backup

To create a backup chain for a VM protected by a backup job that is not configured to produce full backups,
Veeam Backup for Proxmox VE implements the forever forward incremental backup:

1. During the first (full) backup session, Veeam Backup for Proxmox VE copies the full VM image and creates
a full backup file in the backup repository. The full backup file becomes a starting point in the backup
chain.

2. During subsequent backup sessions, Veeam Backup for Proxmox VE copies only those data blocks that
have changed since the previous backup session, and stores these data blocks to incremental backup files
in the backup repository. The content of each incremental backup file depends on the content of the full
backup file and the preceding incremental backup files in the backup chain.

Forward Incremental Backup

To create a backup chain for a VM protected by a backup job that is configured to produce full backups, Veeam
Backup for Proxmox VE implements the forward incremental backup method:

1. During the first (full) backup session, Veeam Backup for Proxmox VE copies the full VM image and creates
a full backup file in the backup repository. The full backup file becomes a starting point in the backup
chain.

14 | V eeam Backup for Proxmox VE | User Guide

 2. During subsequent backup sessions, Veeam Backup for Proxmox VE copies only those data blocks that
have changed since the previous backup session, and stores these data blocks to incremental backup f iles
in the backup repository. The content of each incremental backup file depends on the content of the full
backup file and the preceding incremental backup files in the backup chain.

3. On a day when the synthetic full or active full backup is scheduled, Veeam Backup for Proxmox VE creates
a full backup file and adds it to the backup chain. Incremental restore points produced after this full
backup file use it as a new starting point.

15 | V eeam Backup for Proxmox VE | User Guide

Active Full Backup
In some cases, you need to regularly create a full backup. For example, your corporate backup policy may
require that you create a full backup on weekend and run incremental backup on work days. To let you conform
to these requirements, Veeam Backup for Proxmox VE allows you to create active full backups (either manually
or automatically according to a specific schedule).

When creating an active full backup, Veeam Backup for Proxmox VE starts a new backup chain for the VM. All
further created incremental backups use the latest active full backup file as a new starting point. The old full
backup file from the old backup chain remains on disk until it is automatically deleted according to the retention
policy.

The active full backup session starts at the same time when the backup job is scheduled. For example, if you
schedule the backup job to run at 12:00 AM Sunday through Friday, and schedule active full backup to be
created on Saturday, Veeam Backup for Proxmox VE will start a backup job session that will produce an active
full backup at 12:00 AM on Saturday.

If the backup job is not scheduled to run automatically or is disabled, Veeam Backup for Proxmox VE will not
perform active full backup. If a regular backup session and an active full backup session are scheduled on the
same day, Veeam Backup for Proxmox VE will produce an active full backup — an incremental backup that
should have been created by the regular backup session will not be added to the backup chain. However, if you
run the backup job again on the same day manually, Veeam Backup for Proxmox VE will perform incremental
backup in a regular manner.

16 | V eeam Backup for Proxmox VE | User Guide

Synthetic Full Backup
In some situations, running active full backups periodically may not be an option. Active full backups are
resource-intensive and consume considerable amount of network bandwidth. As an alternative, you can create
synthetic full backups that also produce VBK files and contain data of the whole VM. However, while creating
synthetic full backups, Veeam Backup for Proxmox VE does not retrieve VM data from the cluster but processes
the data that is already stored in the backup repository.

To create a synthetic full backup, Veeam Backup for Proxmox VE performs the following operations:

1. Veeam Backup for Proxmox VE creates a regular incremental backup and adds it to the backup chain.

2. Veeam Backup for Proxmox VE creates a new synthetic full backup using backup files that are already
available in the backup chain, including the newly created incremental backup file.

3. Veeam Backup for Proxmox VE deletes the created incremental backup as its data is already incorporated
in the synthetic full backup.

When creating a synthetic full backup, Veeam Backup for Proxmox VE starts a new backup chain for the VM. All
further created incremental backups use the latest full backup file as a new starting point. The old full backup
file from the old backup chain remains on disk until it is automatically deleted according to the retention policy.

NOTE

The synthetic full backup session starts only on the day when the backup job is scheduled. For example, if
you schedule the backup job to run at 12:00 AM Sunday through Friday, and schedule synthetic full backup
to be created on Saturday, Veeam Backup for Proxmox VE will never start a backup job session that will
produce a synthetic full backup.

17 | V eeam Backup for Proxmox VE | User Guide

If the backup job is not scheduled to run automatically or is disabled, Veeam Backup for Proxmox VE will not
perform synthetic full backup. If a regular backup session and a synthetic full backup session are scheduled on
the same day, Veeam Backup for Proxmox VE will produce a synthetic full backup — an incremental backup that
should have been created by the regular backup session will not be added to the backup chain. However, if you
run the backup job again on the same day manually, Veeam Backup for Proxmox VE will perform incremental
backup in a regular manner.

18 | V eeam Backup for Proxmox VE | User Guide

VM Restore
Veeam Backup for Proxmox VE offers the following restore options:

• Entire VM Restore — restores an entire VM from a backup. You can restore one or more VMs at a time, to
the original location or to a new location.

• File-level recovery — recovers individual VM files and folders from a backup. You can download the
necessary files and folders to a local machine, or restore the files and folders of the source VM to the
original location.

You can restore VM data to the most recent state or to any available restore point.

19 | V eeam Backup for Proxmox VE | User Guide

Entire VM Restore
To restore a VM, Veeam Backup for Proxmox VE performs the following steps:

1. [This step applies only if you perform restore to the original location and if the source VM is still present in
the location] Connects to the Proxmox VE server over REST API to power off and remove the source VM.

2. Launches a worker on same host where the processed VM resides.

If no worker is deployed on the host, Veeam Backup for Proxmox VE launches a worker that is deployed on
any other Proxmox VE host connected to the backup infrastructure.

3. Connects to the Proxmox VE server over REST API, configures a VM and creates empty virtual disks in the
target location.

The number of empty disks equals the number of disks attached to the backed -up VM.

4. Restores backed-up data to the empty disks and restores them to the configured VM.

If multiple disks are attached to the backed-up VM, these disks are restored sequentially, one disk at a
time.

5. Suspends the worker when the restore session completes.

NOTE

If multiple VMs are added to the restore session, these VMs are processed in parallel.

To learn how to restore an entire VM, see Performing VM Restore.

20 | V eeam Backup for Proxmox V E | User Guide

File-Level Recovery
To recover VM files and folders from a backup, Veeam Backup for Proxmox VE performs the following steps:

1. [This step applies only if you perform restore of a VM with an operation system other than Microsoft
Windows] Deploys a helper appliance.

To allow Veeam Backup for Proxmox VE to deploy the helper appliance, you must add a Linux server to
the backup infrastructure as described in the Veeam Backup & Replication User Guide, section Specify
Helper Host.

2. Mounts disks of the backed-up VM to either of the following instances:

o To the backup server or a mount server — if the VM guest OS is Microsoft Windows.

o To the helper appliance — if the VM guest OS is a Linux-based operating system.

3. Launches the Veeam Backup Browser.

The Veeam Backup Browser displays the directory structure of the backed -up VM. In the browser, you
select the necessary files and folders to restore.

4. Restores the selected files and folders to the original location or to a new location.

5. Detaches the disks from the backup server, mount server or helper appliance.

6. [This step applies only if you perform restore of a VM with an operation system other than Microsoft
Windows] Removes the helper appliance.

To learn how to recover individual VM files and folders, see Performing File-Level Restore.

21 | V eeam Backup for Proxmox VE | User Guide

Retention Policies
Backups created by jobs are not kept forever — they are removed according to retention policy settings specified
while creating the jobs as described in section Creating Backup Jobs.

Depending on the data protection scenario, retention policies can be specified:

• In restore p oints

The chain can contain only the allowed number of restore points. If the number of allowed restore points
is exceeded, Veeam Backup for Proxmox VE removes the earliest restore point from the chain.

• In d ays

Restore points in the backup chain can be stored only for the allowed period of time. If a restore point is
older than the specified time limit, Veeam Backup for Proxmox VE removes it from the backup chain.

To learn how Veeam Backup for Proxmox VE applies retention policies to forever forward incremental and
forward incremental backup chains, see Backup Retention.

22 | V eeam Backup for Proxmox VE | User Guide

Planning and Preparation
Before you start deploying Veeam Backup for Proxmox VE, check supported virtualization pl atforms, system
requirements, limitations, permissions and network ports used for data transmission.

23 | V eeam Backup for Proxmox VE | User Guide

System Requirements
Before you start deploying Veeam Backup for Proxmox VE, make sure the virtual environment and the backup
infrastructure components meet the following requirements.

Sp ecification Requirement

Hypervisor Kernel-based Virtual Machine (KVM) must be installed on x86 hardware that supports
virtualization capabilities.

Veeam Backup for Proxmox VE supports Proxmox Virtual Environment version 8.2 (or later)
Virtualization installed using the official ISO image provided by Proxmox .
Platform

Veeam Veeam Backup & Replication version 12.3 or later must be deployed on the backup server.
Software

Workers Workers process backup workload and distribute backup traffic when transferring data to
backup repositories. If you deploy a worker using the default configuration, the following
compute resources will be allocated:
• CPU: 6 vCPU
• Memory : 6 GB RAM
• Disk Space: 100 GB for product installation and logs

With the default configuration, the worker can handle up to 4 concurrent backup and restore
tasks. While deploying a new worker or editing settings of an existing one, you can increase
the maximum number of concurrent tasks. However, you must allocate 1 vCPU and 1 GB
RAM for each additional task. When configuring the maximum number of concurrent tasks,
you must also take into account the network traffic throughput in your virtual infrastructure.

24 | V eeam Backup for Proxmox V E | User Guide

Considerations and Limitations
When you plan to deploy and configure Veeam Backup for Proxmox VE, keep in mind the following limitations
and considerations.

Configuration
When configuring Veeam Backup for Proxmox VE, consider the following:

• Veeam Backup for Proxmox VE supports Proxmox Virtual Environment deployments created using the
official ISO image provided by Proxmox only.

• Veeam Backup for Proxmox VE does not support credentials of the SSH Private Keys type to access the
Proxmox VE server.

• The Proxmox VE server must be able to establish a direct IP connection to the backup server. Connections
through NAT gateways are not supported.

• Before you add a Proxmox VE server to the backup infrastructure, ensure that it has been assigned a
Proxmox VE system UUID and its name does not contain an FQDN.

• If you want to protect VMs that reside in a Proxmox VE cluster, all nodes of these cluster must be added
to the backup infrastructure separately. Adding clusters as standalone entities is not supported.

• After you add nodes of a cluster to the backup infrastructure, you must not change the name of the
cluster in the Proxmox VE administration portal.

• After you make changes to your Proxmox VE environment (for example, you migrate a VM between cluster
nodes), these changes may not appear in Veeam Backup & Replication immediately — the data
synchronization process between the backup server and the Proxmox VE server may take up to 15 minutes
to complete. You can speed up the data synchronization process by rescanning the Proxmox VE server.

Backup Repositories
When managing backup repositories, consider that Veeam Backup for Proxmox VE does not support storing
backups in Veeam Cloud Connect and HPE Cloud Bank Storage repositories. However, you can use them for
storing copies of backups created with Veeam Backup for Proxmox VE.

Workers
When configuring workers, consider the following:

• The default local storage must be enabled on all hosts where worker VMs will be deployed. If you cannot use
the default storage in your environment, contact Veeam Customer Support.

• The storage where system files of workers will be stored must support snapshots.

Backup
When protecting Proxmox VE resources, consider the following:

• Veeam Backup for Proxmox VE does not support backup of LXC containers.

• Veeam Backup for Proxmox VE does not support backup of VM templates.

25 | V eeam Backup for Proxmox VE | User Guide

 • Veeam Backup for Proxmox VE does not support backup of VMs created from templates as linked clones.
Backup of full clones is supported.

• Veeam Backup for Proxmox VE does not support backup of VMs with the same BIOS UUID.

• Veeam Backup for Proxmox VE does not support backup of iSCSI disks. If iSCSI disks are attached to a VM
included into a backup job, these disks will be skipped from processing.

• Veeam Backup for Proxmox VE does not support backup of VM permissions granted to users, user groups
and API tokens.

• Veeam Backup for Proxmox VE does not support backup of VMs that store their disks in the BTRFS and
custom storage. All other Proxmox VE storage types are supported.

• The number of concurrent backup operations performed in each storage is limited to 4 to avoid excessive
load on the production environment. To change the limit, contact Veeam Customer Support.

• Veeam Backup for Proxmox VE does not support VM replication.

Restore
When restoring Proxmox VE resources, consider the following:

• Veeam Backup for Proxmox VE does not support restore of VMs to the BTRFS and custom storage.

• Veeam Backup for Proxmox VE does not support restore of VMs to Ceph/RBD storage if the krbd property
is enabled.

26 | V eeam Backup for Proxmox V E | User Guide

Account Permissions
The accounts used to deploy and administer backup infrastructure components must have the following
permissions.

Backup Server Windows Account Permissions

The Windows account used to install Veeam Backup & Replication on the backup server must have the following
permissions.

Account Required P ermission

Setup Account The account used to install Veeam Backup & Replication and Proxmox VE
Plug-in must have the Local Administrator permissions on the backup server.

Veeam Backup & Replication The account used to run Veeam Backup & Replication services must be a
User Account LocalSystem account or must have the Local Administrator permissions on the
backup server.

Proxmox VE Server Permissions

The administrator account that the backup server uses to access the Proxmox VE server must have the Root
privileges. For more information on system permissions, see Proxmox VE documentation.

27 | V eeam Backup for Proxmox V E | User Guide

Ports
Veeam Backup for Proxmox VE automatically creates firewall rules for the ports required to allow
communication between the Proxmox VE server, workers and the backup server.

Workers
The following table describes network ports that must be open to ensure proper communication of workers with
other backup infrastructure components.

From To P rotocol P ort Notes

Worker Proxmox VE server TCP/HTTPS 8006 Used to communicate with the REST
API service running on the Proxmox
VE server.

Proxmox VE server SSH 22 Used to communicate with Proxmox

VE server.

Backup server TCP 10006 Used to communicate with the backup

server.

Backup server TCP 19001 Used to communicate with the backup

server.

Veeam backup repository TCP 2500- Default range of ports used as

or gateway server 3300 transmission channels for jobs and
restore sessions. For each TCP
connection that a job uses, one port
from this range is assigned.

Rocky Linux repositories TCP/HTTP(S) 80 (443) Used to get OS security updates and
.NET Core package updates.
(mirrors.rockylinux.org,
mirrors.fedoraproject.org, Note: The listed mirror URLs are used
rockylinux.map.fastly.net) to get actual URLs that will be used to
obtain updates.

Veeam Update Repository TCP/HTTPS 443 Used to download worker deployment

(repository.veeam.com) packages.

Amazon CloudFront Note: Veeam Update Repository uses

(cloudfront.net, the Amazon CloudFront service to
amazonaws.com) distribute traffic when downloading
product updates.

28 | V eeam Backup for Proxmox V E | User Guide

 From To P rotocol P ort Notes

Nginx repository TCP/HTTPS 443 Used to download Nginx packages for

worker updates.
(nginx.org/packages/,
nginx.org/packages/keys/)

Backup Server
The following table describes network ports that must be open to ensure proper communication of the backup
server with other backup infrastructure components.

From To P rotocol P ort Notes

Veeam Backup & Replication Backup TCP/HTTPS 8545 Used to communicate with the
console server Platform Service REST API.

Backup server Worker TCP 19000 Used to communicate with workers.

FLR TCP 22 Used to connect to the helper

helper appliance during file-level restore.
appliance

Backup TCP/HTTPS 6172 Used by the Platform Service to

server enable communication with the
Veeam Backup & Replication
database.

Proxmox TCP/HTTPS 8006 Used to communicate with the REST

VE server API service running on the Proxmox
VE server.

Proxmox SSH 22 Used to communicate with the

VE server Proxmox VE server.

NOTE

For the list of ports used by the backup server to communicate with backup repositories, see the
Veeam Backup & Replication User Guide, section Used Ports.

29 | V eeam Backup for Proxmox V E | User Guide

Licensing
Veeam Backup for Proxmox VE is licensed by the number of protected Proxmox VE VMs. Each protected
Proxmox VE VM consumes one Veeam Universal License instance from the license scope. A Proxmox VE VM is
considered protected if it has a restore point created during the past 31 days.

By default, Veeam Backup for Proxmox VE automatically revokes a license instance from a protecte d VM if no
new restore points have been created during the past 31 days. However, you can manually revoke license
instances from protected VMs as described in the Veeam Backup & Replication User Guide, section Revoking
License.

Obtaining New License

You can obtain the following types of licenses for Veeam Backup for Proxmox VE:

• E valuation license is a free license that can be used for product evaluation. The license is valid for 30 days
from the moment of the product download.

To obtain this license, request a trial key on the Veeam downloads page as described in the
Veeam Backup & Replication User Guide, section Obtaining and Renewing License.

• Sub scription license is a paid license with a limited subscription term. The expiration date of the
Subscription license is set to the end of the subscription term. The Subscription license term is normally 1–
5 years from the license issue date.

To obtain this license, choose the required subscription term on the Veeam Backup & Replication Pricing
page and contact the Veeam Sales Team.

• P erpetual license is a paid license without an expiration date. The Perpetual license typically includes one
year period of basic support and maintenance that can be extended.

To obtain this license, contact a reseller in your region.

After you obtain a license, install it on the backup server as described in the Veeam Backup & Replication User
Guide, section Installing License.

Using Existing License

If you already use Veeam Backup & Replication and you have spare Veeam Universal License instances on your
backup server, they can be used to protect Proxmox VE VMs. You can check the number of available license
instances in the Veeam Backup & Replication console as described in the Veeam Backup & Replication User
Guide, section Viewing License Information.

If you have a legacy perpetual per-socket license, you must obtain Veeam Universal License instances and
merge them with the existing perpetual socket license as described in the Veeam Backup & Replication User
Guide, section Merging Licenses.

30 | V eeam Backup for Proxmox V E | User Guide

Deployment
Starting from version 12.2, the Veeam Backup & Replication solution allows you to add Proxmox VE servers to
the backup infrastructure, and to manage data protection and recovery operations for Proxmox VE workloads
from a single console.

To access the Veeam Backup for Proxmox VE functionality, you can either deploy a new backup server as
described in the Veeam Backup & Replication User Guide or use a backup server that already exists in your
backup infrastructure if it meets the Veeam Backup for Proxmox VE system requirements.

31 | V eeam Backup for Proxmox VE | User Guide

Installing Proxmox VE Plug-in Manually
The pre-installed plug-in that comes with the default installation package of Veeam Backup & Replication
allows you to protect Proxmox VE resources. However, you may require to install a new plug -in version on the
backup server manually if some updates and patches become available.

NOTE

If you use a remote Veeam Backup & Replication console, you do not need to install Proxmox VE Plug -in on
the workstation where the remote Veeam Backup & Replication console is deployed.

To install Proxmox VE Plug-in, do the following:

1. Log in to the backup server using an account with the local Administrator permissions.

2. Download a product installation file from your Veeam account page.

3. Open the downloaded archive file and launch the installation file.

Before proceeding with installation, the installer will check whether you have Microsoft .NET Core
Runtime installed on the backup server. In case the required version is missing, the installer will offer to
install it automatically. To do that, click OK.

4. At the License Agreement step of the P roxmox Virtual Environment Plug-in for
Veeam Backup & Replication Setup wizard, read and accept both the Veeam license agreement, licensing
policy, the 3rd party components and required software license agreement. If y ou reject the agreements,
you will not be able to continue installation.

To read the terms of a license agreement, click View.

32 | V eeam Backup for Proxmox VE | User Guide

 5. At the Installation Path step of the wizard, you can change the installation directory if necessary.

6. Click Install to begin installation.

33 | V eeam Backup for Proxmox VE | User Guide

Configuring Veeam Backup for Proxmox
VE
To start working with Veeam Backup for Proxmox VE, perform a number of steps for its configuration:

1. Configure backup repositories where Veeam Backup for Proxmox VE will store backups of Proxmox VE
VMs.

2. Connect to Proxmox VE servers that administer Proxmox VE resources you want to protect.

3. Deploy workers that will transfer backup traffic.

4. [Optional] Configure email settings and notifications.

34 | V eeam Backup for Proxmox VE | User Guide

Configuring Backup Repositories
A backup repository is a storage location where Veeam Backup for Proxmox VE keeps backup files. By default,
the backup server performs the role of a backup repository. To keep your backups in another storage location,
you can configure the following types of repositories:

• Direct attached storage: Microsoft Windows and Linux virtual and physical machines. Hardened
repositories based on Linux servers are supported.

• Network attached storage: CIFS (SMB) shares and NFS shares.

• Ded uplicating storage appliances: ExaGrid, Quantum DXi, Dell Data Domain, HPE StoreOnce, Fujitsu
ETERNUS, Infinidat InfiniGuard.

• Cloud object storage: Amazon S3, S3 compatible, Google Cloud, Wasabi Cloud Storage, Veeam Data Cloud
Vault, IBM Cloud and Microsoft Azure Blob.

To combine repositories of different types in one repository, you can configure a scale-out backup repository
and add any of supported repositories to its performance tier.

For Linux server, Microsoft Windows server, SMB share, ExaGrid, Quantum DXi, Fujitsu ETERNUS and Infinidat
InfiniGuard repositories, you can enable the Fast Clone technology that increases the speed of synthetic backup
creation and transformation, reduces disk space requirements and decreases the load on storage devices. With
this technology, Veeam Backup for Proxmox VE references existing data blocks on volumes instea d of copying
data blocks between files. Data blocks are copied only when files are modified. To learn how to configure a
repository to enable this functionality, see the Veeam Backup & Replication User Guide, section Fast Clone.

IMP ORTANT

Veeam Backup for Proxmox VE does not support storing backups in Veeam Cloud Connect and HPE Cloud
Bank Storage repositories. However, you can use them for storing copies of backups created with Veeam
Backup for Proxmox VE.

35 | V eeam Backup for Proxmox VE | User Guide

Connecting Proxmox VE Server
A Proxmox VE server is a Proxmox VE standalone host or cluster that allows the backup server to access
Proxmox VE resources such as VMs, storage and networks. After you add a Proxmox VE server to the backup
infrastructure, you will be able to deploy workers and to manage data protection tasks for Proxmox VE VMs.

IMP ORTANT

If you want to add a Proxmox VE cluster to the backup infrastructure, consider the following:

• Each node of the cluster must be added to the backup infrastructure separately.
• The name of the cluster must not be changed in the Proxmox VE administration portal after you add
it to the backup infrastructure.

36 | V eeam Backup for Proxmox V E | User Guide

Adding Proxmox VE Server to Backup
Infrastructure
To add a Proxmox VE server to the backup infrastructure, do the following:

1. Launch the New Proxmox VE Server wizard.

2. Specify the Proxmox VE server domain name or IP address.

3. Enter credentials to access the Proxmox VE server.

4. Select storage for snapshots.

5. Apply Proxmox VE server settings.

6. Finish working with the wizard.

37 | V eeam Backup for Proxmox V E | User Guide

Step 1. Launch New Proxmox VE Server Wizard
To launch the New P roxmox VE Server wizard, do the following:

1. In the Veeam Backup & Replication console, open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ma naged Servers.

3. On the ribbon, click Ad d Server.

4. In the Ad d Server window, select Virtualization Platforms.

5. In the Virtualization Platforms window, select P roxmox VE to launch the New P roxmox VE Server wizard.

38 | V eeam Backup for Proxmox V E | User Guide

Step 2. Specify Domain Name or IP Address of Proxmox VE
server
At the Na me step of the wizard, do the following:

1. In the DNS name or IP address field, enter the FQDN or IP address of the Proxmox VE standalone host or
cluster node.

2. In the Description field, provide a description for future reference. The field already contains a default
description with information about the user who added the manager, date and time when the manager
was added.

39 | V eeam Backup for Proxmox V E | User Guide

Step 3. Enter Credentials
NOTE

In versions prior to 1.3, Veeam Backup for Proxmox VE used credentials of the Standard type to connect to
Proxmox VE servers. In version 1.3, those credentials are automatically converted to credentials of the SSH
type. However, keep in mind that credentials of the SSH Private Keys type are not supported.

At the Credentials step of the wizard, specify credentials of an account that will be used to access the Proxmox
VE server — it can be either an account of a root user or an account of a user elevated to root (the latter option
is recommended for security reasons).

For credentials to be displayed in the Credentials list, they must be added to the Credentials Manager as
described in the Veeam Backup & Replication User Guide, section SSH Credentials. If you have not added the
necessary credentials to the Credentials Manager beforehand, you can do this without closing the New P roxmox
VE Server wizard. To do that, click either the Ma nage accounts link or the Ad d button, and specify the user
name, password and description in the Credentials window.

TIP

If you want to use an account of a user elevated to root, you must also select the E levate account
p rivileges automatically check box. Consider that Veeam Backup for Proxmox VE ignores the Ad d account
to the sudoers file and Use "su" if "sudo" fails options for security reasons.

After you click Nex t, the backup server will connect to the Proxmox VE server and check its TLS certificate. If
the certificate is not installed on the backup server, the Certificate Security Alert Window will display a warning
notifying that secure communication cannot be guaranteed. To allow the backup server to connect to the
Proxmox VE server using the certificate, click Continue.

40 | V eeam Backup for Proxmox VE | User Guide

Step 4. Configure Storage Settings
At the Sna pshot Storage step of the wizard, choose whether you want to keep snapshots of processed VMs in
specific storage or in the largest storage available on the connected Proxmox VE server — but only in case the
original VM storage does not support snapshots.

For more information on storage that supports snapshots, see Proxmox VE documentation.

41 | V eeam Backup for Proxmox VE | User Guide

Step 5. Apply Settings
At the Ap p ly step of the wizard, wait until the Proxmox VE server is added to the backup infrastructure and then
click Nex t.

42 | V eeam Backup for Proxmox V E | User Guide

Step 6. Finish Working with Wizard
At the Summary step of the wizard, check that the Proxmox VE server has been successfully added and click
Finish.

43 | V eeam Backup for Proxmox VE | User Guide

Editing Proxmox VE Server Properties
To edit properties of the Proxmox VE server added to the backup infrastructure, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ma naged Servers > Proxmox VE.

3. In the working area, select the Proxmox VE server and click E d it Server on the ribbon, or right-click the
Proxmox VE server and select P roperties.

4. Complete the E d it P roxmox VE Server wizard as described in section Adding Proxmox VE server to Backup
Infrastructure.

44 | V eeam Backup for Proxmox VE | User Guide

Rescanning Proxmox VE Server
Veeam Backup for Proxmox VE retrieves information about the Proxmox VE environment from the Proxmox VE
server. However, the data synchronization process may take some time to complete. If you make any changes to
the Proxmox VE environment and want the Veeam Backup & Replication console to display the changes
immediately, you can rescan the Proxmox VE server manually.

To rescan the Proxmox VE server, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ma naged Servers > Proxmox VE.

3. In the working area, select the Proxmox VE server and click Rescan on the ribbon, or right-click the
Proxmox VE server and select Rescan.

45 | V eeam Backup for Proxmox VE | User Guide

Removing Proxmox VE Server
If you do not want to protect resources managed by the connected Proxmox VE server anymore, you can remove
it from the backup infrastructure.

To remove the Proxmox VE server from the backup infrastructure:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ma naged Servers > Proxmox VE.

3. In the working area, select the Proxmox VE server and click Remove Server on the ribbon, or right-click
the Proxmox VE server and select Remove.

46 | V eeam Backup for Proxmox VE | User Guide

Managing Workers
To perform most data protection and disaster recovery operations, Veeam Backup for Proxmox VE uses workers.
Workers are Linux-based VMs that process backup workload and distribute backup traffic when transferring data
to backup repositories. Each worker is launched on a specific host for the duration of a backup or restore
operation. As soon as a backup or restore session starts, Veeam Backup for Proxmox VE launches a worker, tests
its configuration and installs system updates (if available). When the backup or restore session completes,
Veeam Backup for Proxmox VE shuts down the worker VM so that it can be used for other sessions later.

IMP ORTANT

To modify the worker settings, use the Veeam Backup & Replication console as described in section Editing
Workers. Making any configuration changes to VMs running as workers manually in the Proxmox VE
administration portal may cause technical issues.

Worker Lifecycle
When you add a worker to the backup infrastructure, its configuration is saved to the
Veeam Backup & Replication configuration database, but no VM is actually deployed on the host unless you
choose to test the configuration. In the latter case, a VM (worker VM) is deployed and shut down after the test
operation completes.

As soon as a backup or restore session starts, Veeam Backup for Proxmox VE tries to launch the worker and test
its configuration. If no worker VM has been previously deployed, Veeam Backup for Proxmox VE deploys the VM
using the worker configuration saved to the configuration database. Then, Veeam Backup for Proxmox VE
powers on the worker VM and installs system updates (if available). When the backup or restore session
completes, Veeam Backup for Proxmox VE shuts down the worker VM so that it can be used for other sessions
later.

During the lifecycle, a worker can obtain one of the following statuses:

• Configured — the worker configuration is added to the Veeam Backup & Replication configuration
database.

• Testing — the worker configuration is being updated and tested.

• W orking — the worker is processing a backup or restore operation.

• Shut Down — the worker is powered off.

47 | V eeam Backup for Proxmox VE | User Guide

Adding Workers
To deploy a worker and add it to the backup infrastructure, do the following:

1. Check prerequisites and limitations.

2. Launch the New Proxmox VE Worker wizard.

3. Specify worker VM configuration.

4. Specify worker network settings.

5. Finish working with wizard.

Before You Begin

Before you add a worker to the backup infrastructure, consider the following:

• It is recommended that workers are deployed on each node registered with a Proxmox VE cluster. If no
worker is deployed on the node, performance of backup and restore operations will be affected as Veeam
Backup for Proxmox VE will use a worker deployed on another node.

• Each worker must be provided with sufficient compute resources to handle backup and restore tasks in
parallel. The maximum number of concurrent tasks is configured in worker settings — if this number is
exceeded, the worker will not start a new task until one of the current tasks finishes.

• You can change the maximum number of concurrent tasks (the best practice is to allocate 1 vCPU and 1 GB
RAM for each additional task) while deploying a new worker or editing settings of an existing one.

48 | V eeam Backup for Proxmox VE | User Guide

Step 1. Launch New Proxmox Worker
To launch the New P roxmox Worker wizard, do the following:

1. In the Veeam Backup & Replication console, open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. On the ribbon, select Ad d P roxy.

4. Click P roxmox VE worker.

49 | V eeam Backup for Proxmox VE | User Guide

Step 2. Specify Worker VM Settings
At the Virtual Machine step of the wizard, do the following:

1. Click Choose next to the Host field to specify a host where the worker will be launched.

Make sure that the default local storage is enabled on the selected host. If you cannot use the default
storage in your environment, contact Veeam Customer Support.

2. In the Na me field, specify a name for the worker. The maximum length of the name is 40 characters; the
following characters are only supported: a-z, A-Z, 0-9, -.

3. Click Choose next to the Storage field to select storage where system files of the worker will be stored.
For storage to be displayed in the list of available storage, it must be configured in the virtual
environment as described in Proxmox VE documentation.

Make sure that the selected storage supports snapshots.

4. In the W orker description field, provide a description for future reference. The maximum length of the
description is 1024 characters.

5. In the Ma x concurrent tasks field, specify the number of tasks that the worker will be able to handle in
parallel. If this value is exceeded, the worker will not start processing a new task until one of the currently
running tasks finishes.

The default number of concurrent tasks is set to 4. When you change this value, the wizard automatically
adjusts the amount of resources that will be allocated to the worker. If you want to specify the amount of
resources manually, click Ad vanced.

NOTE
• When performing data protection and disaster recovery operations, Veeam Backup for Proxmox VE
initiates a new task for each VM that is being processed.
• When processing VMs, Veeam Backup for Proxmox VE adjusts the number of concurrent tasks taking
into account a specific limit of backup operations (set to 4 by default) that applies to storage in
order to avoid excessive load on the production environment. For example, you configure a worker
to process maximum 10 VMs simultaneously, while 5 of these VMs store their files on one storage
and the other 5 VMs — on another storage; in this case, the worker will process 8 VMs
simultaneously — 4 VMs for each storage.
The default backup operation limit cannot be changed using the Veeam Backup & Replication
console. To change the limit, contact Veeam Customer Support.

50 | V eeam Backup for Proxmox V E | User Guide

51 | V eeam Backup for Proxmox VE | User Guide
Step 3. Configure Network Settings
At the Networks step of the wizard, do the following:

1. Click Ad d to configure worker network interfaces:

a. From the Network drop-down list, select a network to which the worker network interface will be
connected.

For a network to be displayed in the list of available networks, it must be configured in the virtual
environment as described in Proxmox VE documentation.

b. In the Description filed, provide a network interface description for future reference.

c. If DHCP is enabled in the selected network, the IP address of the worker can be obtained
automatically.

If DHCP is disabled in the selected network, or you want to specify an IP address, select the Use the
following IP address option and enter the worker IP address, subnet mask and default gateway.

To add more network interfaces, repeat the step and specify the network order using the Up and Down
buttons. For more information on multi-network configuration, see section Appendix. Configuring
Multiple Networks.

2. If DHCP is enabled in any network to which the worker will be connected, DNS settings of the worker can
be obtained automatically. To configure DNS settings manually, click Ob tain automatically and do the
following in the DNS Server Settings window:

a. Select the Use the following DNS server address option.

b. Enter the IP addresses of the preferred and alternate DNS servers.

c. Click OK.

NOTE

Since workers are Linux-based VMs, they have the same limitations that apply to machines running the
Rocky Linux operating system. Therefore, DNS settings cannot be configured separately for each net work
added to the worker.

3. To check for available package updates for the worker, Veeam Backup for Proxmox VE automatically
connects to Veeam repositories over the internet. If the worker is not connected to the internet, you can
instruct Veeam Backup for Proxmox VE to use an HTTP p roxy that will provide access to the necessary
repositories. To specify HTTP proxy settings, click Ad vanced and do the following in the Ad vanced
Settings window:

a. Select the Ob tain Updates check box.

b. Select the Use the following internet proxy settings check box.

c. In the Host field, enter the IP address or FQDN of the web proxy.

d. In the P ort field, enter the port used on the web proxy for HTTP or HTTPS connections.

52 | V eeam Backup for Proxmox VE | User Guide

 e. [Applies only if the HTTP proxy requires authentication] Select the Use authentication check box and
select credentials of the account configured on the HTTP proxy to access the internet.

53 | V eeam Backup for Proxmox VE | User Guide

Step 4. Finish Working with Wizard
At the Summary step of the wizard, review summary information and click Finish.

TIP

To test the worker, select the Test the worker configuration when I click Finish check box and then click
Finish.

54 | V eeam Backup for Proxmox VE | User Guide

Testing Workers
Before using a dedicated worker for a backup or restore operation, Veeam Backup for Proxmox VE automatically
tests its configuration — verifies that the worker service can start successfully, checks that the worker can
connect to the backup server and to the host, and installs available updates.

If you want to ensure that the worker configuration is correct before it is used for a backup or restore operation,
you can start a worker configuration test manually:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. In the working area, select the necessary worker and click Test Worker on the ribbon.

Alternatively, right-click the worker and select Test.

TIP

As soon as Veeam Backup for Proxmox VE finishes the worker configuration test, the worker will be
powered off. You can review details of the test session in system logs as described in the
Veeam Backup & Replication User Guide, section Viewing History Statistics.

55 | V eeam Backup for Proxmox V E | User Guide

Enabling and Disabling Workers
By default, workers are launched when jobs or restore sessions start. However, you can temporarily disable a
worker — this may be helpful when you reconfigure a worker and you do not want it to be used for a backup or
restore operation. You will still be able to enable the disabled worker at any time you need.

To enable or disable a worker, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. In the working area, select the necessary worker and click Disable Worker or E na ble Worker on the ribbon.

Alternatively, right-click the worker and select Disable or E na ble.

56 | V eeam Backup for Proxmox V E | User Guide

Editing Workers
For each worker, you can modify settings specified while adding the worker to the backup infrastructure:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. In the working area, select the necessary worker and click E d it Worker on the ribbon.

Alternatively, right-click the worker and select P roperties.

4. Complete the E d it P roxmox VE Worker wizard:

a. To provide a new name and description for the worker or to modify the number of tasks that the
worker is able to handle in parallel, follow the instructions provided in section Adding Workers (step
2).

b. To change the network to which the worker is connected or to specify a new IP address for the
worker, follow the instructions provided in section Adding Workers (step 3).

c. To save changes made to the worker settings, click Finish.

IMP ORTANT

It is not recommended that you decrease the amount of allocated resources or modify the network settings
while the worker is currently transferring data. In this case, Veeam Backup for Proxmox VE will terminate
the related operations, power off the worker and update the settings immediately.

57 | V eeam Backup for Proxmox V E | User Guide

Disabling Automatic Worker Updates
When launching a worker for a backup or restore operation, Veeam Backup for Proxmox VE automatically
downloads updates from Veeam repositories and installs them on the worker. If the worker is not connected to
the internet, you can instruct Veeam Backup for Proxmox VE to use an HTTP proxy that will provide access to
the necessary repositories.

If a worker does not have access to the internet and no HTTP proxy is configured for the worker, you can disable
automatic updates to avoid connection failures and eliminate session warnings:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. In the working area, select the necessary worker and click E d it Worker on the ribbon.

Alternatively, right-click the worker and select P roperties.

4. At the Networks step of the E d it Proxmox VE Worker wizard, click Ad vanced and clear the Ob tain updates
check box. Then, click Finish to save changes made to the worker settings.

58 | V eeam Backup for Proxmox V E | User Guide

Removing Workers
Veeam Backup for Proxmox VE allows you to permanently remove workers if you no longer need them. Note
that you can remove a worker only when it is not processing a back up or restore operation.

To remove a worker, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Ba ckup Proxies.

3. In the working area, select the necessary worker and click Remove Worker on the ribbon.

Alternatively, right-click the worker and select Remove.

4. In the Veeam Backup & Replication window, confirm that you want to permanently delete the worker.

59 | V eeam Backup for Proxmox V E | User Guide

Configuring General Settings
Veeam Backup for Proxmox VE allows you to configure general settings that are applied to all performed
operations and deployed architecture components:

• Configure email settings for automated delivery of reports.

• Configure notification settings.

60 | V eeam Backup for Proxmox VE | User Guide

Configuring Email Settings
You can specify email notification settings for automated delivery of job results. To connect an SMTP server that
will be used for sending email notifications:

1. From the main menu of the Veeam Backup & Replication console, select Op tions.

2. Switch to the E -ma il Settings tab.

3. Select the E na ble e-mail notifications check box.

4. Configure mail server settings.

6. In the From field, enter an email address of the notification sender. This email address will be displayed in
the From field of notifications.

7. In the To field, enter an email address of a recipient. Use a semicolon to separate multiple recipient
addresses.

8. In the Sub ject field, specify a subject for notifications. You can use the following runtime variables:

o %JobName% — a job name.

o %JobResult% — a job result.

o %ObjectCount% — the number of VMs in a job.

9. Choose whether you want to receive email notifications in case jobs complete successfully, complete with
warnings or complete with errors.

10. Select the Sup press notifications until the last job retry check box to receive a notification about the final
job status. If you do not select this check box, the Veeam Backup for Proxmox VE will send one
notification for every job retry.

11. Click Ap p ly.

TIP

Veeam Backup for Proxmox VE allows you to send a test message to check whether you have configured
the settings correctly. To do that, click Test Message . A test message will be sent to the specified email
address.

Configuring Mail Server Settings

To configure mail server settings, choose whether you want to employ SMTP server, Google Gmail or Microsoft
365 authentication for your mail server.

Using SMTP Server Basic Authentication

To employ the SMTP server basic authentication to connect to your mail server, do the following in the Op tions
window:

1. From the Ma il server drop-down list, select SMTP server (basic authentication) .

2. In the SMTP server field, enter a DNS name or an IP address of the SMTP server. All email notifications
(including test messages) will be sent by this SMTP server.

61 | V eeam Backup for Proxmox VE | User Guide

 3. Click Ad vanced next to the Ma il server field and configure SMTP server settings:

a. In the P ort field, specify a communication port for SMTP traffic. The default SMTP port is 587.

b. In the Timeout field, specify a connection timeout for responses from the SMTP server.

c. For an SMTP server with SSL/TLS support, select the Connect using SSL check box to enable SSL data
encryption.

d. If your SMTP server requires authentication, select the This SMTP server requires authentication check
box and specify credentials that will be used to connect to the SMTP server.

Using Google Gmail Modern Authentication

To employ the Google Gmail modern authentication to connect to your mail server, do the following in the
Op tions window:

1. From the Ma il server drop-down list, select Google Gmail (modern authentication) .

2. Click Sig n in with Google. You will be redirected to the authorization page.

3. On the authorization page, specify a Google account to connect to the Veeam Backup & Replication
application. Note that you must also select the Send email on your behalf check box.

62 | V eeam Backup for Proxmox V E | User Guide

 TIP

If you want to use your own web application for email notifications, do the following:

1. Register a new client application in the Google Cloud console for Veeam Backup & Replication to be
able to use OAuth 2.0 to access Google Cloud APIs. When registering the application, it is
recommended to use a dedicated service account with granular SendMail permissions.
2. In the Op tions window, click Ad vanced.
3. In the Ad vanced window, select the Use custom registration settings check box, and provide the
application client ID and client secret created for the application as described in Google Cloud
documentation.
4. Click Sig n in with Google. You will be redirected to the authorization page.
5. On the authorization page, specify a Google account to connect to the registered application. Note
that you must also select the Send email on your behalf check box.

If the authentication process completes successful, Veeam Backup & Replication will display a message notifying
that the token is valid. If the token gets revoked or if the Google account password changes, click Re-authorize
to update the configuration settings.

Using Microsoft 365 Modern Authentication

To employ the Microsoft 365 modern authentication to connect to your mail server, do the following in the
Op tions window:

1. From the Ma il server drop-down list, select Microsoft 365 (modern authentication) .

2. Click Authorize now. You will be redirected to the authorization page.

63 | V eeam Backup for Proxmox V E | User Guide

 3. On the authorization page, specify an Exchange Online account to connect to the
Veeam Backup & Replication application. Note that you must also select the Consent on behalf of your
org anization check box.

To sign in with Exchange Online credentials, you may need to turn off the Internet Explorer Enhanced
Security Configuration option in Server Manager as described in Microsoft documentation.

TIP

If you want to use your own web application for email notifications, do the following:

1. Register a new client application in the Microsoft Azure portal for Veeam Backup & Replication to be
able to use OAuth 2.0 to access Microsoft Azure APIs. When registering the application, it is
recommended to use a dedicated service account with granular SendMail permissions.
2. In the Op tions window, click Ad vanced.
3. In the Ad vanced window, select the Use custom registration settings check box, and provide the
application client ID and tenant ID created for the application as described in Microsoft
documentation.
4. Click Authorize now. You will be redirected to the authorization page.
5. On the authorization page, specify a Exchange Online account to connect to the registered
application. Note that you must also select the Send email on your behalf check box.

If the authentication process completes successful, Veeam Backup & Replication will display a message notifying
that the token is valid. If the token gets revoked or if the Google account password changes, click Re-authorize
to update the configuration settings.

64 | V eeam Backup for Proxmox VE | User Guide

Configuring Notification Settings
You can enable notifications for Veeam Backup for Proxmox VE events that may require your actions:

1. From the main menu of the Veeam Backup & Replication console, select Op tions.

2. Switch to the Notifications tab.

3. In the Ba ckup storage section, choose whether you want to receive notifications when backup repositories
used as target locations for VM backups start running out of free space. While processing VMs included
into backup jobs, Veeam Backup for Proxmox VE analyzes the amount of storage space left in target
repositories and displays warnings in job session details if a specific threshold is breached.

4. In the P roduction datastores section, choose whether you want to receive notifications when Proxmox VE
storage disks used as target locations for VM snapshots start running out of free space. While processing
VMs included into backup jobs, Veeam Backup for Proxmox VE analy zes the amount of space left on target
storage disks and displays warnings in job session details if a specific threshold is breached.

TIP

If Veeam Backup for Proxmox VE detects a target storage disk that is about to run out of free space while
processing a VM, it will either skip the VM from processing or create a snapshot of the VM anyway, which
may result in storage disruptions in the production environment. To avoid the latter, you can instruct
Veeam Backup for Proxmox VE to skip VMs from processing if a specific threshold is breached.

5. In the Sup port expiration section, choose whether you want to receive notifications when the Production
Support and Maintenance agreement included into your Subscription license is about to expire. When
Veeam Backup for Proxmox VE detects that there are less than 14 days left before the support expiration
date, it sends an email notification to the recipient specified in the general email settings.

For more information on how to track the support expiration date, see the Veeam Backup & Replication
User Guide, section Viewing License Information.

65 | V eeam Backup for Proxmox V E | User Guide

 6. In the Up date notification section, choose whether you want to receive notifications on product updates.
When Veeam Backup for Proxmox VE detects an available update, it displays a notification both in the
Windows Action Center and in the Ma naged Servers > Missing Updates node of the Ba ckup Infrastructure
view. If you do not install the update, the notification keeps appearing once a week as a reminder.

It is recommended that you timely install available updates to avoid issues while working with the
product. For example, security updates may help you prevent potential security issues and reduce the risk
of compromising sensitive data. For more information on how to install updates, see the
Veeam Backup & Replication User Guide, section Update Notifications.

66 | V eeam Backup for Proxmox V E | User Guide

Performing Backup
To produce VM backups, Veeam Backup for Proxmox VE runs backup jobs. A backup job is a collection of
settings that define the way backup operations are performed: what data to back up, where to store backups,
when to start the backup process, and so on.

One backup job can be used to process multiple VMs, but you can back up each VM with one backup job at a
time. If a VM is added to more than one backup job, it will be processed only by the backup job that started
earlier.

TIP
Since Veeam Backup for Proxmox VE chooses workers to process backup workload depending on the
source data location and then launches these workers one by one in a random order, it is recommended
that you create separate jobs for VMs that belong to different locations — this may help you reduce the
time required to perform backup operations and optimize the backup performance.

67 | V eeam Backup for Proxmox VE | User Guide

Creating Backup Jobs
To create a backup job, do the following:

1. Check prerequisites and limitations.

2. Launch the New Backup Job wizard.

3. Specify a job name and description.

4. Selects VMs to back up.

5. Specify a backup repository and configure backup settings.

6. Create a schedule for the backup job.

7. Finish working with the wizard.

68 | V eeam Backup for Proxmox V E | User Guide

Before You Begin
Before you create a backup job, consider the following limitations:

• You can back up each VM with one backup job at a time. If a VM is already being processed by a backup
job, another backup job will not start processing this VM until the currently running backup operation
completes.

• You cannot back up a VM being restored. Wait for the restore process to complete, and then start the
backup job.

• You cannot back up VMs created from templates as linked clones. Backup of full clones is supported.

• You cannot back up VMs with the same BIOS UUID.

• You cannot include into a backup job a VM that is being backed up by 3rd party software. Wait for the
backup process to complete or stop the currently running job manually, and then add the VM to the
necessary backup job.

• You cannot include into a backup job a resource pool that does not contain any VMs. Note that after you
update a resource pool in the Proxmox VE administration portal, it may take up to 15 minutes for Veeam
Backup for Proxmox VE to synchronize data between Proxmox VE and Veeam Backup & Replication.

• Veeam Backup for Proxmox VE does not support backup of iSCSI disks. If iSCSI disks are attached to a VM
included into a backup job, these disks will be skipped from processing.

• Veeam Backup for Proxmox VE does not support backup of VM permissions granted to users, user grou ps
and API tokens.

• By default, Veeam Backup for Proxmox VE enables deduplication for backed-up data. Due to technical
limitations, you cannot disable it while configuring backup jobs.

• By default, backup encryption is disabled for backed-up data. However, you can enable encryption at the
repository level as described in the Veeam Backup & Replication User Guide, section Access Permissions.

• VM guest OS file indexing is not supported for backups created with Veeam Backup for Proxmox VE.

• Since Veeam Backup & Replication does not allow you to assign information about locations to the
Proxmox VE server and workers, job statistics do not include information on the Proxmox VE VM data
migration between different geographic regions.

69 | V eeam Backup for Proxmox V E | User Guide

Step 1. Launch New Backup Job Wizard
To launch the New Job wizard, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. On the ribbon, click Ba ckup Job and select Virtual Machine > Proxmox VE.

Alternatively, right-click the working area and select Ba ckup > Virtual machine > Proxmox VE.

70 | V eeam Backup for Proxmox VE | User Guide

Step 2. Specify Job Name and Description
At the Na me step of the wizard, use the Na me and Description fields to specify a name for the new backup job
and to provide a description for future reference. The job name must be unique in Veeam Backup for Proxmox
VE.

The maximum length of the name is 40 characters; the following characters are not supported: ~ " # % & * : < >
! ? / \ { | } . ' ` $. The maximum length of the description is 1024 characters.

71 | V eeam Backup for Proxmox VE | User Guide

Step 3. Configure Backup Source Settings
At the Virtual Machines step of the wizard, specify the following backup source settings:

1. Choose resources to back up.

2. Choose disks to protect.

72 | V eeam Backup for Proxmox V E | User Guide

Step 3a. Choose Resources
First, at the Virtual Machines step of the wizard, specify the backup scope — resources that Veeam Backup for
Proxmox VE will back up:

1. Click Ad d .

2. In the Ad d Objects window, choose whether you want to back up all VMs in the cluster or host, only
specific VMs or groups of VMs included into resource pools:

To view the list of available resource pools, click the Resource pool icon on the toolbar at the top right
corner of the window. If you add a resource pool to the backup scope, Veeam Backup for Proxmox VE will
regularly check for new VMs included into the added pool and automatically update the backup job
settings to include these VMs in the scope. For a resource pool to be displayed in the list, it must be
configured in the Proxmox VE administration portal and must contain at least one VM. For more
information on resource pools, see Proxmox VE documentation.

TIP

As an alternative to specifying resources explicitly, you can exclude a number of resources from the backup
scope. To do that, click E x clusions and specify the VMs that you do not want to back up — the procedure is
the same as described for including resources in the backup scope.

Consider that if a resource appears both in the list of included and excluded resources, Veeam Backup for
Proxmox VE will still not process the resource because the list of excluded resources has a higher priority.

While running the job, Veeam Backup for Proxmox VE processes resources in the order they are added to the
backup scope. However, you can change the order, for example, if you add some mission-critical VMs to the job
and want them to be processed first. To change the processing order, select a resource and use the Up or Down
buttons.

NOTE

Consider the following:

• If you include the same resource into the backup scope multiple times (for example, an individual
VM and a resource pool that contains this VM), Veeam Backup for Proxmox VE will process this
resource only once.
• If you include a resource pool, node or cluster into the backup scope, VMs in this object are
processed at random. To ensure that the VMs are processed in a specific order, you must add them
as standalone VMs — not as part of the resource pool, node or cluster.

73 | V eeam Backup for Proxmox V E | User Guide

By default, jobs process all disks attached to VMs included into the backup scope. However, you can protect
only specific disks of the selected resources. For more information, see Step 3b. Choose Disks and Volume
Groups.

74 | V eeam Backup for Proxmox VE | User Guide

Step 3b. Choose Disks
Second, at the Virtual Machines step of the wizard, you can instruct Veeam Backup for Proxmox VE to back up
only specific virtual disks related to the selected backup scope:

1. Click E x clusions.

2. In the E x clusions window, switch to the Disks tab and click Ad d .

3. In the Ad d Objects window, select a resource that you have added to the backup scope at step 3a, and
click OK.

4. Back to the E x clusions window, select the resource and click E d it.

5. In the Select Disks window, select the Selected Disks option, click Ad d and choose a bus type of the disks
that you want to back up. Then, select the necessary disks.

Disks that you do not select will be excluded from the backup job.

75 | V eeam Backup for Proxmox V E | User Guide

Step 4. Specify Backup Job Settings
At the Ba ckup Destination step of the wizard, do the following:

1. In the Ba ckup repository drop-down list, select a backup repository where you want to store backups.

For a backup repository to be displayed in the list of available repositories, it must be added to the backup
infrastructure.

2. In the Retention policy section, choose a retention policy that Veeam Backup for Proxmox VE will apply to
backups created by the job:

o Select days if you want to keep restore points in a backup chain for the allowed period of time. If a
restore point is older than the specified limit, Veeam Backup for Proxmox VE removes it from the
chain.

o Select restore points if you want a backup chain to contain only the allowed number of restore points.
If the number of allowed restore points is exceeded, Veeam Backup for Proxmox VE removes the
earliest restore point from the chain.

When the restore point limit is exceeded, Veeam Backup for Proxmox VE removes the earliest restore
point from the chain. For more information, see Backup Retention.

If the UUID of a VM changes (for example, if the VM was migrated to another host), Veeam Backup for
Proxmox VE will be unable to continue the backup chain for this VM. After you re-add the VM to the
backup job, Veeam Backup for Proxmox VE will start a new backup chain for it. However, you will still be
able to perform restore operations using backups from the old backup chain.

To help you implement a comprehensive backup strategy, Veeam Backup for Proxmox VE allows you to enable
long-term retention policy for backups and to configure backup job advanced settings (such as backup
maintenance, health check, active and synthetic full backups).

76 | V eeam Backup for Proxmox VE | User Guide

Configuring GFS Policy Schedules
Grandfather-Father-Son (GFS) policy allows you to leverage full backups for long -term retentions instead of
creating a new full backup every time. The mechanism simplifies the backup schedule and optimizes the backup
performance.

Veeam Backup for Proxmox VE re-uses full backups created according to the backup job schedule to achieve the
desired retention for a GFS policy schedule (weekly, monthly and yearly). Each full b ackup is marked with a flag
of a specific GFS policy schedule type: the (W) flag is used to mark full backups for the weekly schedule, (M) —
monthly, and (Y) — yearly. Veeam Backup for Proxmox VE uses these flags to control the retention period for
the created full backups. Once a flag of a GFS policy schedule is assigned to a full backup, this full backup can
no longer be removed — it is kept for the period defined in the retention settings. When the specified retention
period is over, the flag is unassigned from the full backup. If the full backup does not have any other flags
assigned, it is removed according to the short-term retention policy settings. For more information on the GFS
flag assignment and removal, see the Veeam Backup & Replication User Guide, section Long-Term Retention
Policy (GFS).

To configure a GFS policy schedule, select the Keep certain full backups longer for archival purposes check box
and click Configure. Then specify the following options in the Configure GFS window:

• Keep weekly full backups — Veeam Backup for Proxmox VE will keep a full backup created within a week
or on the specific day for a number of weeks.

• Keep monthly full backups — Veeam Backup for Proxmox VE will keep a full backup created during the
specific week for a number of months.

• Keep yearly full backups — Veeam Backup for Proxmox VE will keep a full backup created in the specific
month for a number of years.

After you configure the GFS retention policy settings, schedule active full or synthetic full backups. Otherwise,
no new full backups will be automatically produced, and Veeam Backup for Proxmox VE will be unable to
leverage them for long-term retentions.

77 | V eeam Backup for Proxmox VE | User Guide

 NOTE

If you choose an object storage repository to store backups produced by the backup job, you cannot enable
synthetic full backups. However, if you configure a GFS policy, synthetic backups will be automatically
created according to the specified GFS schedule and marked with an appropriate GFS flag.

Configuring Advanced Settings

To configure backup job advanced settings, do the following:

1. Click Ad vanced to open the Ad vanced settings window.

2. To schedule synthetic full backups, on the Ba ckup tab, select the Create synthetic full backups
p eriodically check box, click Configure and choose whether you want to create synthetic full backups on
specific days every week or on specific days of specific months.

IMP ORTANT
• Synthetic full backups cannot be scheduled if an object storage repository is selected as the target
location for backups.
• Schedule synthetic full backups to run on days when the backup job is scheduled. Otherwise, no
synthetic full backup will be created.

3. To schedule active full backups, on the Ba ckup tab, select the Create a ctive full backups periodically check
box, click Configure and choose whether you want to create active full backups on specific d ays every
week or on specific days of specific months.

Alternatively, you can create active full backups manually when needed. For more information, see
Creating Active Full Backups.

78 | V eeam Backup for Proxmox VE | User Guide

 IMP ORTANT

Do not schedule synthetic and active full backups to run at the same time. Due to technical limitations,
Veeam Backup for Proxmox VE will be unable to create synthetic full backups according to the specified
schedule.

4. To instruct Veeam Backup for Proxmox VE to periodically perform a health check for backups created by
the backup job, on the Ma intenance tab, select the P erform backup files health check (detects and auto -
hea ls corruption) check box, click Configure and specify a schedule for the health check to run.

IMP ORTANT
• It is recommended that the backup and health check schedules configured for the job do not overlap
to avoid data access issues.
• If you have selected an off-premise cloud object storage repository as the target location for
backups at step 4, it is recommended that a helper appliance is configured in the repository settings.
Otherwise, additional data transfer costs may occur.

5. To configure retention settings for backups of VMs that are no longer processed by the backup job, on the
Ma intenance tab, select the Remove deleted items data after check box, and specify the number of days
during which Veeam Backup for Proxmox VE will keep backups of VMs excluded from the job.

6. To decreases the size of the backup, on the Storage tab, from the Compression level drop-down list,
select a compression level for the backup: None, Dedupe-friendly , Optimal, High or Extreme. For more
information on data compression, see Compression and Deduplication.

7. To optimize job performance and storage usage, on the Storage tab, from the Storage optimization drop-
down list, select the block size that will be used to process VMs. For more information on the data block
sizes and how they affect performance, see Storage Optimization.

79 | V eeam Backup for Proxmox VE | User Guide

 8. To configure settings for automated email delivery of job results, on the Notifications tab, select the
E na ble email notifications check box and specify email addresses of recipients. For more information on on
mail server settings required for email notifications, see Configuring Email Settings.

How Health Check Works

When Veeam Backup for Proxmox VE saves a new backup restore point to a backup repository, it calculates CRC
values for metadata in the backup chain and saves these values to the chain metadata, together with the
instance data. When performing a health check, Veeam Backup & Replication verifies the availability of data
blocks and uses the saved values to ensure that the restore points being verified are consistent.

On the day scheduled for a health check to run, Veeam Backup & Replication starts a new health check session.
For each restore point in the standard backup chain, Veeam Backup & Replication calculates CRC values for
backup metadata and compares them to the CRC values that were previously saved to the restore point.
Veeam Backup & Replication also checks whether data blocks that are required to rebuild the restore point are
available.

If Veeam Backup & Replication does not detect data inconsistency, the health check session completes
successfully. Otherwise, the session completes with an error. Depending on the detected data inconsistency,
Veeam Backup & Replication performs the following operations:

• If the health check detects corrupted metadata in a full or incremental restore point,
Veeam Backup & Replication marks the backup chain as corrupted in the configuration database. During
the next backup job session, Veeam Backup for Proxmox VE copies the full instance image, creates a full
restore point in the backup repository and starts a new backup chain in the backup repository.

80 | V eeam Backup for Proxmox VE | User Guide

 • If the health check detects corrupted disk blocks in a full or an incremental restore point, Veeam Backup
for Proxmox VE marks the restore point that includes the corrupted data blocks and all subsequent
incremental restore points as incomplete in the configuration database. During the next backup job
session, Veeam Backup for Proxmox VE copies not only those data blocks that have changed since the
previous backup session but also data blocks that have been corrupted, and saves these data blocks to the
latest restore point that has been created during the current session.

81 | V eeam Backup for Proxmox VE | User Guide

Step 5. Define Job Schedule
At the Schedule step of the wizard, you can instruct Veeam Backup for Proxmox VE to start the backup job
automatically according to a specific backup schedule. The backup schedule defines how often data of the VMs
added to the backup job will be backed up.

Veeam Backup for Proxmox VE allows you to create schedules of the following types:

• Da ily at this time — the backup job will create restore points at a specific time on specific days.

• Monthly at this time — the backup job will create restore points once a month on a specific day.

• P eriodically every — the backup job will create restore points repeatedly with a specific time interval every
day.

TIP

You can instruct Veeam Backup for Proxmox VE to run the backup job again if it fails on the first try. To do
that, select the Retry failed items processing check box, and specify the maximum number of attempts to
run the backup job and the time interval between retries. When retrying backup jobs, Veeam Backup for
Proxmox VE processes only those VMs that failed to be backed up during the previous attempt.

82 | V eeam Backup for Proxmox V E | User Guide

Step 6. Finish Working with Wizard
At the Summary step of the wizard, review summary information and click Finish. As soon as Veeam Backup for
Proxmox VE starts the job, the backup progress will be displayed in the working area when you navigate to Job s
> Ba ckups in the inventory pane of the Home view.

TIP

If you want to start the job immediately, select the Run the job when I click Finish check box and then click
Finish.

83 | V eeam Backup for Proxmox V E | User Guide

Starting and Stopping Backup Jobs
You can start a backup job manually, for example, if you want to create an additional restore point a nd do not
want to modify the configured job schedule. You can also stop a backup job manually if processing of an
Proxmox VE VM is about to take too long, and you do not want the job to have an impact on the production
environment during business hours. When you stop a running job, Veeam Backup for Proxmox VE creates a new
restore point only for those VMs that have already been processed by the time you stop the job.

To start or stop a backup job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Sta rt or Stop on the ribbon.

Alternatively, right-click the job and select Sta rt or Stop.

84 | V eeam Backup for Proxmox VE | User Guide

Retrying Jobs
If a job fails, you can retry the backup operation. When you perform a retry, Veeam Backup for Proxmox VE
restarts the operation only for the failed resources added to the job and does not process VMs that have been
processed successfully. As a result, retrying a job takes less time compared to restarting the job for all
resources.

To retry a job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Retry on the ribbon.

Alternatively, right-click the job and select Retry.

85 | V eeam Backup for Proxmox V E | User Guide

Editing Backup Job Settings
For each backup job, you can modify settings configured while creating the job.

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click E d it on the ribbon.

Alternatively, right-click the job and select E d it.

4. Complete the E d it Job wizard:

a. To provide a new name and description for the job, follow the instructions provided in section
Creating Backup Jobs (step 2).

b. To edit the backup scope, follow the instructions provided in section Creating Backup Jobs (step 3).

c. To change the backup repository where backups are stored, to configure backup job retention
settings, to schedule active and synthetic full backups, to configure health checks and email
notifications, follow the instructions provided in section Creating Backup Jobs (step 4).

d. To modify the job schedule and configure automatic retry settings, follow the instructions provided in
section Creating Backup Jobs (step 5).

e. At the Summary step of the wizard, review configuration information and click Finish.

86 | V eeam Backup for Proxmox V E | User Guide

Analyzing Performance Bottlenecks
As any backup application handles a great amount of data, it is important to make sure the data flow is efficient
and all resources engaged in the backup process are optimally used. For backup jobs, Veeam provides advanced
statistics about the data flow efficiency and lets you identify bottlenecks at the following stages of the data
transmission process:

1. Reading VM data blocks from the source.

2. Processing VM data on a worker.

3. Transporting data over the network.

4. Writing data to the target.

While evaluating the data transmission process, Veeam Backup for Proxmox VE leverages the
Veeam Backup & Replication functionality to analyze performance of all the data flow components:

• Source — the source disk reader component responsible for retrieving data from the source node.

• P roxy — the worker component responsible for processing VM data.

• Network — the network queue writer component responsible for getting processed VM data from the
worker and sending it over the network to the Target (directly or through the Gateway Server).

• Ta rget — the gateway server component responsible for processing VM data, or the target d isk writer
component responsible for storing data in the backup repository.

87 | V eeam Backup for Proxmox VE | User Guide

To see the bottleneck statistics for a job or a specific VM processed by the job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job for which you want to see the bottleneck statistics and click
Sta tistics on the ribbon.

Alternatively, right-click the job and select Sta tistics.

4. In the job session details window, check the Bottleneck field in the SUMMARY column.

TIP

To see the bottleneck statistics for a specific VM, click Show Details, select the VM name in the Na me
column and check the Loa d record in the Action column. To learn how to analyze the statistics, see
Veeam Backup & Replication User Guide, section Performance Bottlenecks.

88 | V eeam Backup for Proxmox VE | User Guide

Cloning Backup Jobs
You can create a new job by cloning an existing one. Job cloning allows you to create an exact copy of any job
with the same job settings.

To clone a job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Clone on the ribbon.

Alternatively, right-click the job and select Clone.

The name of the cloned job is formed by the following rule: <job_name_clone1> , where job_name is the name of
the original job and clone1 is a suffix added to the original job name. If you clone the same job again, the number
in the name will be incremented, for example, job_name_clone2, job_name_clone3 and so on. To change the
name of a cloned job, edit the job as described in section Editing Backup Job Settings.

NOTE

If the original job is scheduled to run automatically, Veea m Backup for Proxmox VE disables the cloned job.
To enable the cloned job, select it in the job list and click E na ble.

89 | V eeam Backup for Proxmox V E | User Guide

Enabling and Disabling Backup Jobs
By default, all created backup jobs run according to the specified schedules. However, you can temporarily
disable a job so that it does not run automatically. You will still be able to enable the disabled job at any time
you need.

To enable or disable a backup job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click E nable or Disable on the ribbon.

Alternatively, right-click the job and select E na ble or Disable.

90 | V eeam Backup for Proxmox VE | User Guide

Deleting Backup Jobs
You can permanently delete a backup job from the Veeam Backup for Proxmox VE configuration database if you
no longer need it. When you delete a job, backups created by this job are displayed under the Ba ckups > Disk
( Orphaned) node in the Home view of the Veeam Backup & Replication console. If you want to delete backup
files as well, follow the instructions provided in section Deleting Backups.

To delete a backup job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Delete on the ribbon.

Alternatively, right-click the job and select Delete.

91 | V eeam Backup for Proxmox VE | User Guide

Creating Active Full Backups
You can manually create an active full backup for all VMs added to a backup job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Active Full on the ribbon.

Alternatively, right-click the job and select Active full.

TIP

To create active full backup automatically according to a specific schedule, configure backup job settings
as described in section Creating Backup Jobs (step 4).

92 | V eeam Backup for Proxmox V E | User Guide

Creating VeeamZIP Backups
You can back up one or multiple VMs without configuring backup jobs. To do that, you can leverage the
VeeamZIP feature — it can be helpful, for example, if you want to create backups for VMs immediately, archive
VMs before decommissioning and so on. VeeamZIP produces a full backup that acts as an independent restore
point. You can store the backup in a repository added to the backup infrastructure, in a local folder on the
backup server or in a network share.

NOTE
• You cannot store VeeamZIP backups in Veeam Cloud Connect and HPE Cloud Bank Storage
repositories.
• Veeam Backup & Replication does not apply network traffic throttling rules to VeeamZIP backup
sessions. For more information, see the Veeam Backup & Replication User Guide, section Configuring
Network Traffic Rules.

To create a VeeamZIP backup, do the following:

1. Open the Inventory view.

2. In the inventory pane, select Virtual Infrastructure > P roxmox VE.

3. In the working area, select the VM that you want to back up and click Veea mZIP on the ribbon.

Alternatively, right-click the VM and select Veea mZIP.

4. Select the destination where the VeeamZIP backup will be stored.

TIP

You cannot specify an SMB share that requires authentication as a local or shared folder. However, you can
add the SMB share to the backup infrastructure and specify it as backup repository.

The created VeeamZIP backup will be displayed under the Ba ckups > Disk (Exported) node in the Home view of
the Veeam Backup & Replication console.

93 | V eeam Backup for Proxmox V E | User Guide

Managing Backups
Veeam Backup for Proxmox VE stores information on all protected Proxmox VE VMs in the configuration
database. Even if a VM is no longer protected by any configured backup job and even if the VM no longer exists
in the Proxmox VE environment, records about created backups will not be deleted from the database until
Veeam Backup for Proxmox VE automatically removes all restore points associated with this VM according to
the retention settings saved in the backup metadata. You can manage Proxmox VE VM backups as long as their
records are present in the configuration database.

94 | V eeam Backup for Proxmox VE | User Guide

Viewing Backup Properties
After a backup job successfully creates a VM backup according to the specified schedule, or after you create an
active full VM backup manually, the backup is displayed under the Ba ckups node in the Home view of the
Veeam Backup & Replication console. Each backup is represented with a set of properties, such as:

• Ob jects — the names and sizes of backed-up VMs.

• Restore Points — the date and time of all restore points created for a VM.

• Files — the size of processed VM data, the size of backed-up VM data, the ratio of data deduplication and
the ratio of data compression.

To view backup properties, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, right-click the necessary backup job and select P roperties.

95 | V eeam Backup for Proxmox V E | User Guide

Verifying Backups
To perform an integrity check of VM backups, Veeam Backup & Replication offers the SureBackup technology
that allows you to ensure that the created restore points are not corrupted. For backups of Windows VMs, you
can also scan the restore points with antivirus software installed on the backup server, and run YARA rules to
detect malware and sensitive data.

To create a SureBackup job, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s > Backup and click SureBackup Job on the ribbon.

3. At the Na me step of the New SureBackup Job wizard, select the Ba ckup verification and content scan only
verification mode, and then complete the wizard as described in the Veeam Backup & Replication User
Guide, section Creating SureBackup Jobs.

If any of the verification checks fail for a restore point, Veeam Backup & Replication will mark both this restore
point and all subsequent points in the backup chain as Infected . To learn how to manage infected restore points,
see Veeam Backup & Replication User Guide, section Managing Malware Status.

TIP

You can scan backups of Windows VMs manually on demand, without creating a SureBackup job. To learn
how to do that, see the Veeam Backup & Replication User Guide, section Scan Backup.

96 | V eeam Backup for Proxmox V E | User Guide

Exporting Backups
Exporting backups allows you to synthesize a complete and independent full backup file using restore points
located in your backup repositories. That is, you can transform any backup chain into a sta ndalone full backup
file and save it to a repository or folder.

To export a backup, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the job that created the backup, right-click a VM for which you want to
synthesize a full backup file, and select E x port Backup.

4. Complete the New E xport wizard as described in the Veeam Backup & Replication User Guide, section
Performing Export.

Once the export operation completes, the exported backup will be displayed under the Ba ckups > Disk
( E xported) node in the Home view of the Veeam Backup & Replication console.

97 | V eeam Backup for Proxmox VE | User Guide

Copying Backups
With backup copy, you can create several instances of a backup and copy them to secondary (target) backup
repositories for long-term storage. Target backup repositories can be located in the same site as the source
backup repository or can be deployed off-site. Since the backup copy has the same format as the original
backup, you can restore VM data directly from the backup copy in case a disaster strikes. For more information
on the backup copy functionality, see the Veeam Backup & Replication User Guide, section Backup Copy.

To copy backups to a secondary backup repository, do the following:

1. Open the Home view.

2. In the inventory pane, select Job s > Backup and click Ba ckup Copy on the ribbon.

3. Create a backup copy job as described in the Veeam Backup & Replication User Guide, section Creating
Backup Copy Jobs.

Note that for backup copies, you can also use Veeam Cloud Connect repositories if a service provider is added to
Veeam Backup & Replication.

TIP

Alternatively, you can create a copy of a backup without configuring a job as described in the
Veeam Backup & Replication User Guide, section Copying Backups.

98 | V eeam Backup for Proxmox V E | User Guide

Copying Backups to Tapes
You can create archives of VM backups and copy them to tapes for long -term storage. Veeam Backup for
Proxmox VE allows you to manage tape archives the same way you manage backups in backup repositories.
However, it usually takes more time to access archived data on tapes than to access backed -up data in
repositories. For more information on tapes, see the Veeam Backup & Replication User Guide, section Tape
Devices Support.

To archive VM backups to tape, do the following:

1. Configure the tape infrastructure:

a. Connect tape devices as described in the Veeam Backup & Replication User Guide, section Tape
Devices Deployment.

b. Perform initial configuration of the tape infrastructure as described in the

Veeam Backup & Replication User Guide, section Getting Started with Tapes (steps 1–3).

2. Create a backup to tape job as described in the Veeam Backup & Replication User Guide, section Creating
Backup to Tape Jobs.

NOTE

You cannot restore Proxmox VE VMs directly from tapes. To restore an Proxmox VE VM, you must first
restore its backups to a repository as described in the Veeam Backup & Replication User Guide, section
Backup Restore from Tape to Repository.

99 | V eeam Backup for Proxmox V E | User Guide

Deleting Backups
By default, Veeam Backup for Proxmox VE maintains backups stored in backup repositories according to
retention policy settings saved in the backup metadata. If Veeam Backup for Proxmox VE detects that the
number of restore points in the backup chain exceeds the allowed number, it automatically removes obsolete
backups. You can also delete backup files from backup repositories manually if you no longer need them.

To delete backup files created for a Proxmox VE VM, do the following:

1. Open the Home view.

2. In the inventory pane of the Home view, select Ba ckups.

3. In the working area, expand the job that created the backup, right-click the VM name and select Delete
from disk.

NOTE

If 4-eyes authorization is enabled in Veeam Backup & Replication, deleting backup files will require
additional approval from another user with the Veeam Backup Administrator role.

100 | V eeam Backup for Proxmox VE | User Guide

Performing Restore
In various disaster recovery scenarios, Veeam Backup for Proxmox VE allows you to perform the following
operations using backed-up data:

• Entire VM restore — recover Proxmox VE VMs to the original location or to a new location.

• Instant VM recovery — instantly start an Proxmox VE VM directly from a backup.

• Disk publishing — mount specific disks of a backed-up Proxmox VE VMs to any server added to the backup
infrastructure.

• File-level restore — recover individual VM guest OS files and folders.

• Application items restore — restore applications, such as Microsoft Active Directory, Microsoft Exchange,
Microsoft SharePoint, and Microsoft SQL Server.

• VM disk export — restore VM disks and convert them to disks of the VMDK, VHD or VHDX format.

• VM restore to Amazon Web Services — restore Proxmox VE VMs to Amazon Web Services as EC2 instances.

• VM restore to Microsoft Azure — restore Proxmox VE VMs to Microsoft Azure as Azure VMs.

• VM restore to Google Cloud — restore Proxmox VE VMs to Google Cloud as VM instances.

You can restore VM data to the most recent state or to any available restore point.

101 | V eeam Backup for Proxmox VE | User Guide

Performing VM Restore
In case of a disaster, you can restore an entire Proxmox VE VM from a backup. Veeam Backup for Proxmox VE
allows you to restore one or more VMs at a time, to the original location or to a new location.

To restore machines to Proxmox VE, you can use the following backups:

• Backups of Proxmox VE VMs created by Veeam Backup for Proxmox VE

• Backups of Nutanix AHV VMs created by Veeam Backup for Nutanix AHV

• Backups of oVirt KVM VMs created by Veeam Backup for Oracle Linux Virtualization Manager and Red Hat
Virtualization

• Backups of Microsoft Hyper-V and VMware vSphere VMs created by Veeam Backup & Replication

• Backups of VMs created by vCloud Director

• Backups of Amazon EC2 instances created by Veeam Backup for AWS

• Backups of Microsoft Azure VMs created by Veeam Backup for Microsoft Azure

• Backups of Google Cloud VM instances created by Veeam Backup for Google Cloud

• Backups of virtual and physical machines created by Veeam Agent for Microsoft Windows and Veeam
Agent for Linux

VM restore is supported only for backups stored in backup repositories, object stora ge repositories and on the
performance, capacity and archive tier of a scale-out backup repository (except for backups stored in the archive
tier that consists of the Amazon S3 Glacier Instant Retrieval extent).

NOTE

You cannot restore VMs from backups stored in external repositories and on tapes. However, you can copy
backups to a supported repository and then use them to restore VMs.

To restore a protected VM, do the following:

1. Launch the Entire VM Restore wizard.

2. Select a restore point.

3. Choose a restore mode.

4. Specify a target cluster.

5. Select a storage where VM virtual disks will be stored .

6. Specify a name for the restored VM.

7. Configure network settings.

8. Specify a restore reason.

9. Verify restore settings.

102 | V eeam Backup for Proxmox V E | User Guide

Step 1. Launch Entire VM Restore Wizard
To launch the E ntire VM Restore wizard, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, select the VM that you want to restore and click
E ntire VM on the ribbon, or right-click the VM and select Restore entire VM to Proxmox.

103 | V eeam Backup for Proxmox V E | User Guide

Step 2. Select Restore Point
At the Virtual Machines step of the wizard, select a restore point that will be used to restore the selected VM.
By default, Veeam Backup for Proxmox VE uses the most recent valid restore point. However, you can restore
the VM data to an earlier state.

To select a restore point, do the following:

1. Select the VM.

2. Click P oint.

3. In the Restore Points window, select the necessary restore point and click OK.

To help you choose a restore point, Veeam Backup for Proxmox VE provides the following information on
each available restore point:

o Job — the name of the backup job that created the restore point and the date when the restore point
was created.

o Ty p e — the type of the restore point.

o Loca tion — the repository where the restore point is stored.

104 | V eeam Backup for Proxmox VE | User Guide

Step 3. Choose Restore Mode
At the Restore Mode step of the wizard, choose whether you want to restore the selected VM to the original or
to a custom location.

105 | V eeam Backup for Proxmox V E | User Guide

Step 4. Specify Target Host
[This step applies only if you have selected the Restore to a new location, or with different settings option at
the Restore Mode step of the wizard]

At the Host step of the wizard, choose a host to which the recovered VM will belong. For a host to be displayed
in the list of available hosts, it must be added to the backup infrastructure as described in Connecting Proxmox
VE server.

TIP

You can also choose whether you want the recovered VM to be included into the same resource pool as the
original VM.

106 | V eeam Backup for Proxmox V E | User Guide

Step 5. Select Storage
[This step applies only if you have selected the Restore to a new location, or with different settings option at
the Restore Mode step of the wizard]

At the Storage step of the wizard, choose storage where virtual disks of the recovered VM will be stored. For
storage to be displayed in the list of available storage, it must be configured in the virtual environment as
described in Proxmox VE documentation.

If you restore the VM to the original host, Veeam Backup for Proxmox VE will automatically select the same
storage where the original VM disks were stored at the moment of backup. If you restore the VM to a new hos t,
you will have to select storage manually. In both cases, the restored disks will by default have the same type as
the original VM disks; however, you can specify another type manually.

NOTE S
• You will not be able to select storage and disk type for each VM disk separately.
• If the selected storage does not support the specified disk type, Veeam Backup for Proxmox VE will
display a warning notifying that some of the provided settings are invalid. You will still be able to
proceed with the wizard without changing the disk type; in this case, Veeam Backup for Proxmox VE
will automatically choose a supported disk type while restoring the VM.

107 | V eeam Backup for Proxmox VE | User Guide

Step 6. Specify VM Name
[This step applies only if you have selected the Restore to a new location, or with different settings option at
the Restore Mode step of the wizard]

At the Na me step of the wizard, you can specify a new name for the recovered VM. The maximum length of the
name is 63 characters; the following characters are only supported: a -z, A-Z, 0-9, -. The hyphen-minus
character (-) is supported, but you cannot use it as the first or the last character of the name.

108 | V eeam Backup for Proxmox V E | User Guide

Step 7. Configure Network Settings
[This step applies only if you have selected the Restore to a new location, or with different settings option at
the Restore Mode step of the wizard]

At the Network step of the wizard, choose a network to which the recovered VM will be connected. If you do not
want to connect the VM to any virtual network, select the VM and click Disconnect.

For a network to be displayed in the list of available networks, it must be configured in the virtual environment
as described in Proxmox VE documentation.

109 | V eeam Backup for Proxmox V E | User Guide

Step 8. Specify Restore Reason
At the Rea son step of the wizard, specify a reason for restoring the VM. This information will be saved to the
session history, and you will be able to reference it later.

110 | V eeam Backup for Proxmox VE | User Guide

Step 9. Finish Working with Wizard
At the Summary step of the wizard, review summary information and click Finish.

TIP

If you want to start the recovered VM as soon as the restore process completes, select the P ower on target
VM a fter restoring check box.

111 | V eeam Backup for Proxmox VE | User Guide

Performing Instant VM Recovery
With Instant VM Recovery, you can immediately restore Proxmox VE VMs as VMware vSphere, Microsoft Hyper -
V or Nutanix AHV VMs to your production environment by running them directly from their backups. Instant VM
Recovery helps you improve recovery time objectives and minimize disruption and downtime of production
workloads. For more information on Instant VM Recovery, see the Veeam Backup & Replication User Guide,
section VM Recovery.

To perform Instant VM Recovery, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM you want to restore and select
Instant Recovery.

o To restore the VM to VMware vSphere, complete the Instant Recovery wizard as described in the
Veeam Backup & Replication User Guide for VMware vSphere, section Performing Instant VM
Recovery of Workloads to VMware vSphere VMs.

o To restore the VM to Microsoft Hyper-V, complete the Instant Recovery wizard as described in the
Veeam Backup & Replication User Guide for Microsoft Hyper-V, section Performing Instant VM
Recovery of Workloads to Hyper-V VMs.

o To restore the VM to Nutanix AHV, complete the Instant Recovery wizard as described in the Veeam
Backup for Nutanix AHV User Guide, section Performing Instant VM Recovery of Workloads to Nutanix
AHV.

112 | V eeam Backup for Proxmox V E | User Guide

Publishing Disks
Veeam Backup & Replication allows you to mount specific disks of backed-up VMs to any server and to instantly
access data in the read-only mode. This can be helpful when you want to copy files and folders as of a point-in-
time state to the target server, and perform an antivirus scan of the backed-up data. For more information, see
the Veeam Backup & Replication User Guide, section Disk Publishing (Data Integration API).

To publish disks of an Proxmox VE VM, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that contains disks you want to
mount and select P ub lish d isks.

4. Complete the P ub lish Disk wizard as described in the Veeam Backup & Replication User Guide, section
Publishing Disks.

113 | V eeam Backup for Proxmox VE | User Guide

Performing File-Level Restore
With guest OS file recovery (file-level restore), you can restore individual guest OS files and folders from VM
backups created with Veeam Backup for Proxmox VE. When restoring files and folders, you do not need to
extract the VM image to a staging location or start the VM prior to restore. For more information on VM guest
OS file restore, see the Veeam Backup & Replication User Guide, section Guest OS File Recovery.

IMP ORTANT

Make sure to install the QEMU Guest Agent on VMs and enable it in the Proxmox VE administration portal
— before the backups are created. You will not be able to install the agent during the recovery operation.

To restore VM guest OS files and folders, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that contains files you want to
restore and do the following:

o If you want to restore files of a Microsoft Windows machine, select Restore g uest files > Microsoft
W ind ows and complete the Guest File Restore wizard as described in the Veeam Backup & Replication
User Guide, section Restoring VM Guest OS Files (FAT, NTFS or ReFS).

o If you want to restore files of a Linux, Solaris, BSD, Unix or Mac machine, select Restore guest files >
Linux and other and complete the Guest File Restore wizard as described in the
Veeam Backup & Replication User Guide, section Restoring VM Guest OS Files (Multi-OS).

NOTE

To restore files of a VM with an operation system other than Microsoft Windows, Veeam Backup for
Proxmox VE requires a helper appliance — a Linux server that will be used to mount VM disks. While
completing the Guest File Restore wizard, you will be able either to choose a server already added to the
backup infrastructure or to specify connection settings of a new server that will used as helper appliance.

114 | V eeam Backup for Proxmox VE | User Guide

115 | V eeam Backup for Proxmox VE | User Guide
Performing Application Item Restore
With application item restore, you can use Proxmox VE backups to restore the following data:

• Microsoft Active Directory objects and containers

• Microsoft Exchange mailboxes, folders and messages

• Microsoft SharePoint sites and lists

• Microsoft SQL Server

• Oracle databases

NOTE

Due to technical limitations, Veeam Backup for Proxmox VE produces only crash-consistent (not
application-consistent) backups that in some cases cannot be used for application item restore.

To restore application items from a VM backup, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, select the VM that contains an application you want
to restore.

4. Click Ap p lication Items on the ribbon and the select the application.

5. In the restore wizard, select a restore point that will be used to restore the application, specify a restore
reason and click Browse.

6. In the Veeam Explorer application, perform the steps described in the Veeam Explorers User Guide.

116 | V eeam Backup for Proxmox VE | User Guide

 TIP

As an alternative to application item restore, you can also perform file-level restore to recover standalone
databases using Veeam Explorers.

117 | V eeam Backup for Proxmox VE | User Guide

Exporting Disks
Veeam Backup for Proxmox VE allows you to export disks, that is, restore disks from VM backups and convert
them to the VMDK, VHD and VHDX formats. You can save the exported disks to any s erver added to the backup
infrastructure or place the disks on a datastore connected to an ESXi host (for the VMDK disk format only). For
more information, see the Veeam Backup & Replication User Guide, section Disk Export.

To export disks of an Proxmox VE VM, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that contains disks you want to
export and select E x port content as virtual disks.

4. Complete the E x p ort Disk wizard as described in the Veeam Backup & Replication User Guide, section
Exporting Disks.

118 | V eeam Backup for Proxmox VE | User Guide

Performing VM Restore to Amazon Web
Services
Veeam Backup for Proxmox VE allows you to restore Proxmox VE VMs to Amazon Web Services (AWS) as EC 2
instances. For more information, see the Veeam Backup & Replication User Guide, section Restore to Amazon
EC2.

To restore a VM to Amazon EC2, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that you want to restore and
select Restore to Amazon E C2.

4. Complete the Restore to Amazon EC2 wizard as described in the Veeam Backup & Replication User Guide,
section Restoring to Amazon EC2.

119 | V eeam Backup for Proxmox VE | User Guide

Performing VM Restore to Microsoft Azure
Veeam Backup for Proxmox VE allows you to restore Proxmox VE VMs to Microsoft Azure as Azure VMs. For
more information, see the Veeam Backup & Replication User Guide, section Restore to Microsoft Azure.

To restore a VM to Microsoft Azure, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that you want to restore and
select Restore to Microsoft Azure.

4. Complete the Restore to Microsoft Azure wizard as described in the Veeam Backup & Replication User
Guide, section Restoring to Microsoft Azure.

120 | V eeam Backup for Proxmox V E | User Guide

Performing VM Restore to Google Cloud
Veeam Backup for Proxmox VE allows you to restore Proxmox VE VMs to Google Cloud as VM instances. For
more information, see the Veeam Backup & Replication User Guide, section Restore to Google Compute Engine.

To restore a VM to Google Cloud, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, expand the necessary backup job, right-click the VM that you want to restore and
select Restore to Google CE.

4. Complete the Restore to Google Compute Engine wizard as described in the Veeam Backup & Replication
User Guide, section Restoring to Google Compute Engine.

121 | V eeam Backup for Proxmox V E | User Guide

Getting Technical Support
If you have any questions or issues with Veeam Backup for Proxmox VE, you can search for a resolution on
Veeam R&D Forums or submit a support case in the Veeam Customer Support Portal.

When you submit a support case, it is recommended that you provide the Veeam Customer Support Team with
the following information:

• Version information for the product and its infrastructure components

• The error message or an accurate description of the problem you are facing

• Log files

Viewing Product Details

To view the product details, do the following:

1. Log in to the backup server using an account with the Local Administrator permissions.

2. Right-click the Sta rt menu and select Control panel.

3. In the Control Panel window, navigate to P rograms > P rograms a nd Features.

4. In the program list, check the version of P roxmox Virtual Environment Plug-in for
Veeam Backup & Replication.

Downloading Logs
To download the product logs, do the following:

1. From the main menu of the Veeam Backup & Replication console, select Help > Support Information.

122 | V eeam Backup for Proxmox VE | User Guide

 2. At the Scop e step of the E x port Logs wizard, select the E x p ort all logs for selected components option.
Then, in the Ma naged servers list, select the backup server.

Complete the wizard as described in the Veeam Backup & Replication User Guide, section Exporting Logs.

123 | V eeam Backup for Proxmox VE | User Guide

Appendix. Configuring Multiple Networks
Veeam Backup for Proxmox VE allows you to connect workers to multiple networks. This may be helpful if your
corporate policies require that inbound and outbound internet traffic is delivered through a secure network
only, or if you want to use a specific network to transfer backed-up data from and to backup repositories.

Since workers deployed by Veeam Backup for Proxmox VE are Linux -based VMs, they have the same limitations
that apply to machines running the Rocky Linux operating system. That is, network routing can only be applied
to the networks connected to the network adapters (vNICs) that has been added first while configuring workers,
which means that these VMs can reach out to endpoints in other networks only through those first vNICs.

That is why you must consider the following while configuring multiple networks for workers:

• If you want workers to obtain updates from online Veeam repositories, you must connect to the first vNIC
a network that allows inbound and outbound internet traffic.

• If a backup repository, the backup server or the Proxmox VE host is not reachable from the network
connected to the first vNIC, you must update the worker settings to add one more vNIC and to connect it
to the network to which that component is connected.

This section describes examples of valid and invalid network configurations.

Example 1. Valid Configuration

In this example, the workers, the backup server, the repository and the Proxmox VE host are connected to
Network B, while the workers are also connected to Network A that allows them to obtain updates from the
internet. This configuration is valid since all backup infrastructure components are connected to the same
network.

124 | V eeam Backup for Proxmox V E | User Guide

Example 2. Valid Configuration
In this example, the workers, the backup server, the repository and the Proxmox VE host are connected to
Network A, while the workers and the backup repository are also connected to Network B that is configured as a
preferred network to deliver traffic to the backup repository. This configuration is valid since all backup
infrastructure components are connected to the same network.

NOTE

The workers will be able to obtain updates from online Veeam repositories only if Network A is configured
to allow inbound and outbound internet traffic.

Example 3. Valid Configuration

In this example, the workers are connected to Network A using their first vNICs and to Network B that is
configured as a preferred network to deliver traffic to the backup repository. Also, you have a router configured
to forward traffic between networks A, C and D. This configuration is valid since the workers can use Network A
to communicate with other backup infrastructure components though the router.

125 | V eeam Backup for Proxmox VE | User Guide

 NOTE

The workers will be able to obtain updates from online Veeam repositories only if Network A is configured
to allow inbound and outbound internet traffic.

Example 4. Invalid Configuration

In this example, the workers are connected both to Network A using their first vNICs and to Network B using
their second vNICs, while the backup server, the backup repository and the Proxmox VE host are connected to
Network C. Also, you have a router configured to forward traffic between networks B and C. This configuration
is invalid since the workers cannot use Network B to communicate with other backup infrastructure components
through the router.

To make the configuration valid, do either of the following:

• Change your network configuration to connect Network A to the router.

126 | V eeam Backup for Proxmox VE | User Guide

 • Add more vNICs to the workers. Then, connect these vNICs to Network C.

127 | V eeam Backup for Proxmox V E | User Guide