Scribd
Upload
43 views

Veeam Backup 12 User Guide Hyperv

This document is the user guide for Veeam Backup & Replication version 12 for Microsoft Hyper-V. It provides information on planning and preparing for deployment including supported platforms, deployment scenarios, system requirements, permissions, ports and naming conventions. It also covers security guidelines such as securing the backup infrastructure, malware detection, data encryption, multi-factor authentication and licensing. Finally, it discusses deploying Veeam Backup & Replication including installing, repairing, obtaining and installing licenses.

Uploaded by

virtualheadz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
43 views

Veeam Backup 12 User Guide Hyperv

This document is the user guide for Veeam Backup & Replication version 12 for Microsoft Hyper-V. It provides information on planning and preparing for deployment including supported platforms, deployment scenarios, system requirements, permissions, ports and naming conventions. It also covers security guidelines such as securing the backup infrastructure, malware detection, data encryption, multi-factor authentication and licensing. Finally, it discusses deploying Veeam Backup & Replication including installing, repairing, obtaining and installing licenses.

Uploaded by

virtualheadz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2244

Veeam Backup & Replication

Version 12
User Guide for Microsoft Hyper-V
December, 2023
© 2023 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 intelle ctual
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 & Replication | User Guide for Microsoft Hyper-V


Contents
CONTACTING VEEAM SOF TWARE ................................ ................................ .......................... 15
ABOUT THIS DOCUMENT ................................ ................................ ................................ .... 16
ABOUT VEEAM BACKUP & REPLICATION ................................ ................................ .................. 17
PLANNING AND P REPARATION ................................ ................................ ............................ 20
Platform Support................................................................................................................................ 24
Deployment Scenarios ........................................................................................................................ 30
Simple Deployment.................................................................................................................... 31
Advanced Deployment .............................................................................................................. 33
Distributed Deployment ............................................................................................................ 35
System Requirements ......................................................................................................................... 36
Permissions ........................................................................................................................................ 65
Ports ...................................................................................................................................................91
Naming Conventions .......................................................................................................................... 152
SECURITY GUIDELINES ................................ ................................ ................................ ......153
General Security Considerations ......................................................................................................... 154
Securing Backup Infrastructure ........................................................................................................... 156
Security & Compliance Analyzer ......................................................................................................... 159
Malware Detection ............................................................................................................................ 177
How Malware Detection Works ................................................................................................. 178
Malware Detection Methods .................................................................................................... 180
Configuring Malware Detection ............................................................................................... 204
Managing Malware Status ....................................................................................................... 207
Trusted Root Certificates ...................................................................................................................210
Data Encryption..................................................................................................................................211
Encryption Sta ndards ............................................................................................................... 213
Encryption Algorithms ............................................................................................................. 215
Encryption Keys ....................................................................................................................... 216
Encrypted Objects.................................................................................................................... 221
How Data Encryption Works .................................................................................................... 229
How Data Decryption Works ..................................................................................................... 231
How Decryption Without Password W orks .................................................................................233
Encryption Best Practices .........................................................................................................235
Restoring Data from Encrypted Backups....................................................................................237
Restoring Encrypted Data from Tapes ...................................................................................... 245
Multi-Factor Authentication ...............................................................................................................253
Kerberos Authentication ....................................................................................................................257
Using Group Ma naged Service Accounts .............................................................................................. 261

3 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


LICENSING ................................ ................................ ................................ ................... 264
Types of Licenses.............................................................................................................................. 267
Instance Consumption for Object Storage Backup, File Backup a nd File to Tape Jobs ........................... 268
Obtaining and Renewing License ........................................................................................................ 271
Installing License ...............................................................................................................................273
Merging Licenses .............................................................................................................................. 276
Viewing License Information ............................................................................................................. 278
Revoking License .............................................................................................................................. 282
Removing License ............................................................................................................................. 283
Exceeding License Limit .................................................................................................................... 286
License Expiration............................................................................................................................. 288
Updating License .............................................................................................................................. 290
Updating License Ma nually ....................................................................................................... 291
Updating License Automatically............................................................................................... 293
Automatic License Usage Reporting ................................................................................................... 296
DEPLOY MENT ................................ ................................ ................................ ............... 297
Installation ....................................................................................................................................... 298
Installing Veeam Back up & Replication..................................................................................... 299
Installing Veeam Back up & Replication Console ......................................................................... 318
Repairing Veeam Backup & Replication .................................................................................... 326
Repairing Veeam Backup & Replication Console .........................................................................332
Uninstalling Veeam Backup & Replication..................................................................................337
Upgrade and Update ......................................................................................................................... 338
Upgrading to Veeam Backup & Replication 12.1 ........................................................................ 339
Updating Veeam Backup & Replication ..................................................................................... 356
Veeam Backup & Replication Update Notifications .....................................................................357
Upgrading Veeam Backup & Replication Console ...................................................................... 360
Upgrading Infrastructure Comp onents ..................................................................................... 367
Silent Deployment ............................................................................................................................ 369
Installing Veeam Back up & Replication in Silent Mode .............................................................. 370
Installing Veeam Back up & Replication Console in Silent Mode .................................................. 378
Installing Veeam Back up & Replication in Unattended Mode ..................................................... 383
Upgrading Veeam Backup & Replication in Silent Mode ............................................................. 423
Upgrading Veeam Backup & Replication Console in Silent Mode ................................................ 428
Updating Veeam Backup & Replication in Silent Mode ............................................................... 432
Uninstalling Veeam Backup & Replication in Silent Mode .......................................................... 435
Uninstalling Veeam Backup & Replication Console in Silent Mode .............................................. 438
GETTING STARTED WITH VEEAM BACKUP & REPLICATION................................ ........................... 441
Logging in to Veeam Backup & Replication......................................................................................... 442
Veeam Backup & Replication UI ......................................................................................................... 443

4 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Main Menu ............................................................................................................................. 444
Navigation Pane ...................................................................................................................... 445
Ribbon a nd Tabs ..................................................................................................................... 446
Views ..................................................................................................................................... 447
Working Area .......................................................................................................................... 449
Job Filter ................................................................................................................................ 450
Footer .................................................................................................................................... 453
Changing Color Theme ............................................................................................................ 454
Restore P oints Icons ................................................................................................................ 455
Hypervisor Infrastructure Icons ................................................................................................ 457
Veeam Backup & Replication Services ................................................................................................ 458
Veeam Installer Service ........................................................................................................... 459
Veeam AI Online Assistant..................................................................................................................461
Resource Scheduling ......................................................................................................................... 463
Limitation of Concurrent Tasks ................................................................................................ 464
Limitation of Read and Write Data Rates for Back up Repositories .............................................. 467
Performance Bottlenecks ........................................................................................................ 468
Job Priorities .................................................................................................................................... 470
CONFIGURING VEE AM BACKUP & REPLICATION ................................ ................................ ....... 472
Configuring General Settings ............................................................................................................. 473
Specifying I/O Settings ............................................................................................................ 474
Configuring Security Settings .................................................................................................. 476
Specifying Email Notification Settings .......................................................................................491
Specifying SNMP Settings.........................................................................................................501
Specifying Syslog Servers ........................................................................................................ 504
Specifying Other Notification Settings...................................................................................... 507
Specifying Session History Settings ...........................................................................................510
Managing Users and Roles ...................................................................................................................511
Configuring Users .................................................................................................................... 512
Four -Eyes Authorization........................................................................................................... 515
Managing Credentials ........................................................................................................................ 518
Credentials Manager ................................................................................................................ 519
Cloud Credentials Manager .......................................................................................................527
Password Manager .................................................................................................................. 558
Key Management System Keys ................................................................................................. 561
Managing Locations .......................................................................................................................... 566
Creating and Assigning Locations to Infrastructure Objects ....................................................... 569
Editing Locations ..................................................................................................................... 571
Deleting Locations ...................................................................................................................572
Exporting and Importing Locations List .....................................................................................573

5 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Managing Network Traffic ................................................................................................................. 574
Configuring Network Traffic Rules ............................................................................................575
Managing Upload Streams ....................................................................................................... 582
Specifying Preferred Networks ................................................................................................ 583
IPv6 Support .......................................................................................................................... 585
Managing Logs ................................................................................................................................. 586
Exporting Logs ....................................................................................................................... 587
Configuring Global VM Exclusions ..................................................................................................... 592
BACKUP INFRASTRUCTURE COMPONENTS ................................ ................................ ............. 594
Backup Server .................................................................................................................................. 595
Backup & Replication Console ........................................................................................................... 596
Veeam Backup & Replication Config uration Database ......................................................................... 599
Managing Configuration Database .......................................................................................... 600
Veeam Backup PowerShell Module .................................................................................................... 649
Virtualization Servers and Hosts ........................................................................................................ 650
Adding Microsoft Hyper-V Servers ........................................................................................... 652
Adding Microsoft SMB3 Servers ............................................................................................... 666
Adding Microsoft Windows Servers .......................................................................................... 677
Adding Linux Servers............................................................................................................... 685
Rescanning Servers ................................................................................................................. 694
Editing Server Settings ............................................................................................................ 695
Removing Servers ................................................................................................................... 696
General-Purpose Backup Proxies ....................................................................................................... 697
Adding General-Purpose Backup Proxies .................................................................................. 698
Off-Host Backup Proxies ................................................................................................................... 705
Adding Off-Host Backup Proxies .............................................................................................. 707
Editing Backup Proxy Settings .................................................................................................. 713
Disabling and Removing Backup Proxies .................................................................................... 714
Configuring Advanced Options for Off -Host Backup Proxies ....................................................... 716
Cache Repositories............................................................................................................................ 720
Backup Repositories ........................................................................................................................... 721
Microsoft Windows Server ........................................................................................................722
Linux Server ............................................................................................................................733
Hardened Repository .............................................................................................................. 745
SMB (CIFS) Share .................................................................................................................... 792
NFS Share ............................................................................................................................... 803
Deduplicating Storage Appliances ............................................................................................. 815
Backup Repositories with Rotated Drives ................................................................................. 854
Object Storage Repositories ....................................................................................................860
Managing Backup Repositories ................................................................................................ 989

6 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


External Repositories ...................................................................................................................... 1002
How External Repository W orks ............................................................................................. 1003
Adding External Rep ositories ................................................................................................. 1006
Managing External Rep ositories ..............................................................................................1029
Scale-Out Back up Repositories .........................................................................................................1034
Limitations for Scale-Out Backup Repositories .........................................................................1036
Immutability for Scale-Out Backup Rep ositories ......................................................................1038
Performance Tier ...................................................................................................................1039
Capacity Tier ......................................................................................................................... 1049
Archive Tier ...........................................................................................................................1076
Adding Scale -Out Back up Repositories ................................................................................... 1089
Managing Scale -Out Back up Repositories ................................................................................ 1103
Guest Interaction Proxies .................................................................................................................. 1127
Gateway Servers .............................................................................................................................. 1130
Mount Servers .................................................................................................................................. 1135
Veeam Data Mover Service ................................................................................................................ 1137
WAN Accelerators .............................................................................................................................1139
WAN Global Cache .................................................................................................................. 1141
WAN Accelerator Sizing ...........................................................................................................1147
Adding WAN Accelerators........................................................................................................ 1152
Removing WAN Accelerators .................................................................................................. 1160
WAN Acceleration ................................................................................................................... 1161
Log Shipping Servers ........................................................................................................................1165
Tape Servers.................................................................................................................................... 1166
NDMP Servers ..................................................................................................................................1167
Veeam Backup Enterprise Ma nager ................................................................................................... 1168
BACKUP ................................ ................................ ................................ ..................... 1169
About Backup .................................................................................................................................. 1170
How Backup W orks ................................................................................................................. 1171
Backup Infrastructure for Back up ............................................................................................. 1173
Backup of VMs on Local Storage and CSV ................................................................................. 1177
Backup of VMs on Microsoft SMB3 .......................................................................................... 1189
Backup Chain ......................................................................................................................... 1194
Changed Block Tracking ......................................................................................................... 1230
Data Compression and Deduplication ...................................................................................... 1233
Data Exclusion ....................................................................................................................... 1237
Microsoft Hyper-V Guest Quiescence ...................................................................................... 1245
Guest Processing ................................................................................................................... 1247
Microsoft SQL Server Log Backup ........................................................................................... 1263
Oracle Log Backup ................................................................................................................. 1274

7 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


PostgreSQL W AL Files Back up ................................................................................................ 1283
Backup Job Sched uling ............................................................................................................1291
Immutability for Backup Files ................................................................................................. 1299
Health Check for Back up Files ................................................................................................ 1300
Compact of Full Backup File ...................................................................................................1306
Backup Move .........................................................................................................................1308
Resume on Disconnect ............................................................................................................ 1313
Creating Backup Jobs ........................................................................................................................1314
Before Y ou Begin .................................................................................................................... 1315
Step 1. La unch New Backup Job Wizard ....................................................................................1316
Step 2. Specify Job Name and Description ................................................................................ 1317
Step 3. Select VMs to Back Up .................................................................................................1318
Step 4. Exclude Objects from Backup Job .................................................................................1319
Step 5. Define VM Backup Order .............................................................................................. 1321
Step 6. Specify Backup Storage Settings ................................................................................. 1322
Step 7. Configure Long-Term Retention .................................................................................. 1324
Step 8. Specify Advanced Backup Settings .............................................................................. 1326
Step 9. Specify Secondary Target ............................................................................................ 1336
Step 10. Specify Guest Processing Settings.............................................................................. 1337
Step 11. Define Job Schedule .................................................................................................. 1350
Step 12. Finish Working with Wizard ........................................................................................ 1352
Performing Active Full Backup.......................................................................................................... 1353
Quick Backup ................................................................................................................................... 1355
Retention Policy for Quick Backups ......................................................................................... 1356
Performing Quick Back up ....................................................................................................... 1357
Importing Backups Manually ............................................................................................................ 1358
Importing E ncrypted Backups .................................................................................................1360
Importing Transaction Logs .....................................................................................................1361
Importing Backup Files from Scale -Out Back up Repositories .................................................... 1362
Managing Backups ........................................................................................................................... 1363
Viewing Back up Properties ..................................................................................................... 1364
Upgrading Backup Chain Formats ........................................................................................... 1365
Moving Backups ..................................................................................................................... 1367
Copying Backups .................................................................................................................... 1370
Exporting Backups ................................................................................................................. 1373
Detaching Backups from Jobs ..................................................................................................1381
Removing Back ups from Configuration.................................................................................... 1382
Deleting Backups from Disk .................................................................................................... 1383
Deleting Backups from Object Storage Repositories ................................................................. 1385
Deleting Backups from Scale -Out Back up Repositories ............................................................. 1386

8 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Removing Missing Restore Points ........................................................................................... 1387
Launching Background Retention ...........................................................................................1390
Disabling Background Retention ..............................................................................................1391
Managing Backup Jobs ..................................................................................................................... 1392
Editing Job Settings ............................................................................................................... 1393
Cloning Jobs .......................................................................................................................... 1394
Disabling and Deleting Jobs ................................................................................................... 1396
Starting and Stopping Jobs ..................................................................................................... 1397
Starting and Stopping Transaction Log Backup Jobs ................................................................ 1399
Retrying Jobs......................................................................................................................... 1401
Reconfiguring Jobs with Microsoft SQL Server VMs .................................................................1403
Targeting Jobs to Another Repository .................................................................................... 1404
Reporting ........................................................................................................................................1405
Viewing Real-Time Statistics .................................................................................................. 1406
Viewing Job Session Results .................................................................................................. 1409
Viewing Job and Job Session Reports ...................................................................................... 1410
REPLICATION ................................ ................................ ................................ ............... 1412
Considerations a nd Limitations ..........................................................................................................1413
Backup Infrastructure for Replication................................................................................................ 1414
Replication Scenarios ............................................................................................................. 1416
How Replication Works .................................................................................................................... 1419
Replication Chain ....................................................................................................................1421
VM Replica Types ................................................................................................................... 1422
Replica Seeding a nd Mapping ................................................................................................. 1425
Replica from Backup .............................................................................................................. 1428
Creating Replication Jobs ..................................................................................................................1431
Before Y ou Begin ................................................................................................................... 1432
Step 1. La unch New Replication Job W izard ............................................................................. 1433
Step 2. Specify Job Name and Description ............................................................................... 1434
Step 3. Select VMs to Replicate .............................................................................................. 1436
Step 4. Specify Data Source .................................................................................................... 1437
Step 5. Exclude Objects from Replication Job .......................................................................... 1438
Step 6. Specify VM Replication Order ..................................................................................... 1440
Step 7. Specify Replica Destination ......................................................................................... 1441
Step 8. Create Network Map Table.......................................................................................... 1443
Step 9. Config ure Re -IP Rules ................................................................................................. 1445
Step 10. Specify Replication Job Settings ................................................................................ 1447
Step 11. Specify Advanced Replica Settings ..............................................................................1448
Step 12. Specify Data Transfer Settings ................................................................................... 1454
Step 13. Define Seeding and Mapping Settings ........................................................................ 1456

9 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Step 14. Specify Guest Processing Settings .............................................................................. 1458
Step 15. Define Job Schedule ..................................................................................................1469
Step 16. Finish Working with Wizard ........................................................................................1471
Creating Replica Seeds ..................................................................................................................... 1472
Managing Replicas ........................................................................................................................... 1473
Viewing Replica Properties ..................................................................................................... 1474
Rescanning Replicas ............................................................................................................... 1475
Removing Replicas from Configuration.................................................................................... 1476
Deleting Replicas from Disk .................................................................................................... 1477
Managing Replication Jobs ............................................................................................................... 1478
Retrying Replication Jobs ....................................................................................................... 1479
Editing Replication Jobs ........................................................................................................ 1480
Cloning Replication Jobs ........................................................................................................ 1481
Disabling and Deleting Replication Jobs .................................................................................. 1482
Failover and Failback for Replication.................................................................................................1484
Failover Plans ........................................................................................................................ 1487
Failover ................................................................................................................................. 1497
Permanent Failover ................................................................................................................1504
Planned Failover ....................................................................................................................1506
Failover Undo ......................................................................................................................... 1512
Failback..................................................................................................................................1514
Failback Commit .................................................................................................................... 1529
Failback Undo ......................................................................................................................... 1531
UNSTRUCTURED DATA BACKUP ................................ ................................ ......................... 1533
Backup Infrastructure for Unstructured Data Backup ......................................................................... 1534
Adding Unstructured Data Source ........................................................................................... 1539
How Unstructured Data Back up Works ...............................................................................................1591
Data Structure in Backup, Archive and Secondary Repositories ................................................. 1592
Unstructured Data Backup Retention Scenarios ....................................................................... 1597
Unstructured Data Backups in Object Storage Rep ositories ..................................................... 1604
Unstructured Data Backups in Immutable Rep ositories ............................................................1607
Unstructured Data Backups in Scale -Out Repositories ............................................................... 1611
Scale-Out Repository with Extents in Metadata and Data Roles .................................................1612
File Backup Integration with Storage Systems ......................................................................... 1614
Creating Backup Jobs for Protecting Unstructured Data ..................................................................... 1616
Creating File Backup Jobs ........................................................................................................1617
Creating Object Storage Backup Jobs ...................................................................................... 1641
Managing Unstructured Data Backups............................................................................................... 1662
Viewing Unstructured Data Backup Properties ......................................................................... 1663
Copying Unstructured Data Backups .......................................................................................1664

10 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Starting New Back up Chain..................................................................................................... 1665
Performing Health Check and Repair for Unstructured Data Backups ........................................1666
Converting Back ups from SMB or NFS Shares to NAS Filer Shares .............................................1668
Converting Back ups from Non-Root to Root Shared Folders .....................................................1670
Updating Source File Share Path for Backup Jobs with Secondary Target ...................................1671
Unstructured Data Recovery............................................................................................................. 1673
File Share Data Recovery ........................................................................................................ 1674
Object Storage Data Recovery ................................................................................................1709
VEE AMZIP................................ ................................ ................................ ................... 1735
Creating VeeamZIP Backups ............................................................................................................. 1736
Managing VeeamZIP Back ups ........................................................................................................... 1739
BACKUP COPY ................................ ................................ ................................ ............. 1740
About Backup Copy...........................................................................................................................1741
How Backup Copy Works ........................................................................................................ 1743
Backup Copy Architecture ...................................................................................................... 1745
Backup Copy Modes ............................................................................................................... 1747
Backup Copy Intervals ............................................................................................................ 1749
Restore P oint Selection .......................................................................................................... 1752
Transformation Processes....................................................................................................... 1753
Backup Copy Window ............................................................................................................. 1754
Retention Policy for Backup Copy Jobs.................................................................................... 1755
Health Check for Back up Files ................................................................................................. 1768
Compact of Full Backup File ................................................................................................... 1770
Backup Copy Job Mapping ....................................................................................................... 1771
Active Full Backup Copies ....................................................................................................... 1773
Automatic Job Retries ............................................................................................................ 1774
Creating Backup Copy Jobs for VMs and P hysical Machines ................................................................ 1776
Before Y ou Begin ................................................................................................................... 1777
Step 1. La unch New Backup Copy Job Wizard........................................................................... 1778
Step 2. Specify Job Name and Copy Mode ............................................................................... 1779
Step 3. Select W orkloads to Process ........................................................................................1780
Step 4. Exclude Objects from Backup Copy Job ....................................................................... 1782
Step 5. Define Processing Order .............................................................................................. 1783
Step 6. Specify Target Repository and Retention Settings ........................................................ 1784
Step 7. Map Backup File ......................................................................................................... 1786
Step 8. Specify Advanced Settings .......................................................................................... 1788
Step 9. Specify Data Path Settings .......................................................................................... 1795
Step 10. Define Backup Copy Wind ow ..................................................................................... 1796
Step 11. Finish W orking with Wizard ........................................................................................ 1798
Creating Backup Copy Jobs for HPE StoreOnce Rep ositories .............................................................. 1799

11 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Before Y ou Begin .................................................................................................................. 1800
Step 1. La unch New Backup Copy Job Wizard........................................................................... 1801
Step 2. Specify Job Name and Description ...............................................................................1802
Step 3. Select Source and Target Repositories .........................................................................1803
Step 4. Specify Advanced Settings ..........................................................................................1805
Step 5. Define Backup Copy W indow ...................................................................................... 1809
Step 6. Finish W orking with Wizard ......................................................................................... 1810
Creating Backup Copy Jobs for Veeam Plug -ins .................................................................................. 1811
Linking Backup Jobs to Back up Copy Jobs ..........................................................................................1812
Managing Backups ............................................................................................................................1813
Viewing Back up Properties ..................................................................................................... 1814
Upgrading Backup Chain Formats ........................................................................................... 1816
Moving Backups ..................................................................................................................... 1819
Copying Backups .................................................................................................................... 1822
Removing Back ups ................................................................................................................. 1825
Removing Missing Restore Points ........................................................................................... 1828
Managing Backup Copy Jobs .............................................................................................................1831
Editing Backup Copy Job Settings ........................................................................................... 1832
Starting and Stopping Backup Copy Jobs ................................................................................. 1834
Creating Active Full Backups .................................................................................................. 1837
Disabling and Deleting Backup Copy Jobs ............................................................................... 1838
Reporting ....................................................................................................................................... 1840
FILE COPY ................................ ................................ ................................ ................... 1841
Creating File Copy Jobs .................................................................................................................... 1842
Before Y ou Begin ................................................................................................................... 1843
Step 1. La unch New File Copy Job Wizard ................................................................................1844
Step 2. Specify Job Name and Description ............................................................................... 1845
Step 3. Select Files and Folders to Be Copied ...........................................................................1846
Step 4. Select Destination for Copying .................................................................................... 1847
Step 5. Define Job Schedule ...................................................................................................1848
Step 6. Finish W orking with Wizard .........................................................................................1850
Copying Files and Folders Manually ...................................................................................................1851
Managing Folders ............................................................................................................................ 1852
Editing and Deleting Files ................................................................................................................ 1853
RECOVERY VERIFICATION ................................ ................................ ................................ 1854
SureBackup ..................................................................................................................................... 1855
How SureBack up Works .......................................................................................................... 1856
Backup Recovery Verification Tests ......................................................................................... 1858
Application Group .................................................................................................................. 1863
Virtual Lab............................................................................................................................. 1873

12 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


SureBackup Job ..................................................................................................................... 1893
XML Files with Machine Roles Description ...............................................................................1920
Manual Recovery Verification ................................................................................................. 1923
ON-DEMAND SANDBOX ................................ ................................ ................................ ..1924
Configuring On-Dema nd Sandbox ..................................................................................................... 1925
DATA RECOVERY................................ ................................ ................................ ........... 1927
VM Recovery ................................................................................................................................... 1928
Instant Recovery to VMware vSphere ...................................................................................... 1929
Instant Recovery to Microsoft Hyper-V ................................................................................... 1962
Instant Recovery to Nutanix AHV ............................................................................................ 1983
Entire VM Restore ..................................................................................................................1984
Staged Restore ..................................................................................................................... 2002
Restore to Microsoft Azure ....................................................................................................2004
Restore to Amazon EC2 ......................................................................................................... 2052
Restore to Google Compute Engine ........................................................................................ 2071
Disk Recovery .................................................................................................................................2090
Disk Export ............................................................................................................................2091
Disk Publishing (Data Integration API) ..................................................................................... 2102
Item Recovery ..................................................................................................................................2116
VM Files Restore ..................................................................................................................... 2117
Guest OS File Restore............................................................................................................. 2124
Application Item Restore ........................................................................................................ 2167
TAPE DE VICES SUPPORT................................ ................................ ................................ .. 2179
STORAGE SYSTEM SNAPSHOT INTEGRATION................................ ................................ ......... 2180
INTEGRATION WITH VEEAM BACKUP FOR AWS ................................ ................................ ....... 2181
INTEGRATION WITH VEEAM BACKUP FOR MICROS OFT AZURE ................................ ..................... 2182
INTEGRATION WITH VEEAM BACKUP FOR GOOGLE CLOUD ................................ ......................... 2183
INTEGRATION WITH VEEAM BACKUP FOR NUTANIX AHV ................................ ........................... 2184
INTEGRATION WITH VEEAM BACKUP FOR RED HAT VIRTUALIZATION ................................ ............ 2185
VEE AM AGENT MANAGEMENT ................................ ................................ .......................... 2186
VEE AM CLOUD CONNECT................................ ................................ ................................ . 2187
VEE AM BACKUP & REPLICATION UTILITIES ................................ ................................ ............2188
Extract Utility .................................................................................................................................. 2189
Using Extract Utility in GUI .....................................................................................................2190
Using Extract Utility in Interactive Mode ..................................................................................2191
Using Extract Utility from Command Line ................................................................................ 2192
Veeam Configuration Database Connection Utility ............................................................................. 2196
Using Veeam.Backup.DBConfig.exe Utility .............................................................................. 2197
Veeam Backup Validator ................................................................................................................. 2205
Using Veeam Backup Validator .............................................................................................. 2206

13 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Veeam Backup Configuration Tool .................................................................................................... 2214
Using Veeam Backup Configuration Tool ................................................................................. 2215
VEE AM BACKUP & REPLICATION EVE NTS ................................ ................................ .............. 2218
General ........................................................................................................................................... 2219
License............................................................................................................................................ 2221
Security ........................................................................................................................................... 2223
Servers and Hosts ............................................................................................................................2226
Repositories .................................................................................................................................... 2227
Proxy Server ....................................................................................................................................2229
WAN Accelerator ............................................................................................................................ 2230
Jobs ................................................................................................................................................ 2231
NAS Backup ..................................................................................................................................... 2235
Restore ...........................................................................................................................................2236
SureBackup ..................................................................................................................................... 2237
Tape ...............................................................................................................................................2239
Agents ............................................................................................................................................2243

14 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


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 tha t 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

15 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


About This Document
This user guide provides information about main features, installation and use of Veeam Backup & Replication in
Microsoft Hyper-V environments. The document applies to version 12 and all subsequent versions until it is
replaced with a new edition.

Intended Audience
The user guide is intended for anyone who wants to use Veeam Backup & Replication. It is primarily aimed at
Microsoft Hyper-V administrators, consultants, analysts and any other IT professionals using the product.

16 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


About Veeam Backup & Replication
Veeam Backup & Replication is a comprehensive data protection and disaster recovery solution. With
Veeam Backup & Replication, you can create image-level backups of virtual, physical and cloud machines and
restore from them. Technology used in the product optimizes data transfer and resource consumption, which
helps to minimize storage costs and the recovery time in case of a disaster.

Veeam Backup & Replication provides a centralized console for administering backup, restore and replication
operations in all supported platforms (virtual, physical, cloud). Also, the console allows you to automate and
schedule routine data protection operations and integrate with solutions for alerting and generating compliance
reports.

This section contains an overview of Veeam Backup & Replication and solutions integrated with it.

Main Features
Main functionality of Veeam Backup & Replication includes:

• Backup: creating image-level backups of virtual, physical, cloud machines and backups of file shares and
object storage repositories.

• Restore: performing restore from backup files to the original or a new location.
Veeam Backup & Replication offers a number of recovery options for various disaster recovery scenarios,
including Instant Recovery, image-level restore, file-level restore, restore of application items and so on.

• Replication: creating an exact copy of a VM and maintaining the copy in sync with the original VM.

• Backup Copy: copying backup files to a secondary repository.

• Storage Systems Support: backing up and restoring VMs using capabilities of native snapshots created on
storage systems. For more information, see the Storage System Snapshot Integration Guide.

• Tape Devices Support: storing copies of backups in tape devices. For more information, see the Tape
Devices Support section in the Veeam Backup & Replication User Guide.

• Recovery Verification: testing VM backups and replicas before recovery.

Protected Objects
With Veeam Backup & Replication, you can back up and restore the following objects:

• Virtual machines:

o VMware vSphere VMs

o Microsoft Hyper-V VMs

o Nutanix AHV VMs (requires an additional plug-in)

• Cloud VMs:

o AWS EC2 instances

o Microsoft Azure VMs

o Google Cloud VMs

17 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• Unstructured data:

o File shares

o Object storage repositories

• P hy sical machines. To back up machines running Windows, Linux or macOS operating systems,
Veeam Backup & Replication uses backup agents installed on each computer. Veeam Backup & Replication
operates as a centralized control center for deploying and managing Veeam Agent for Microsoft Windows,
Veeam Agent for Linux and Veeam Agent for Mac. For details, see the Veeam Agent Management Guide.

Also, you can use standalone backup agents and integrate them with Veeam Backup & Replication: Veeam
Agent for Oracle Solaris and Veeam Agent for IBM AIX.

Protected Applications
Native functionality of Veeam Backup & Replication allows you to create application-consistent backups for:

• Microsoft SQL Server

• PostgreSQL

• Oracle Database

• Active Directory

• Microsoft Exchange

• Microsoft OneDrive

• Microsoft SharePoint

Also, you can install the following additional tools:

• Veeam Backup for Microsoft 365: for full protection of Microsoft applications.

• Veeam Plug-ins for Enterprise Applications: for integration of Veeam Backup & Replication with Oracle
RMAN, SAP HANA Backint, and BR*Tools.

Management and Reporting


Veeam Backup & Replication integrates with a set of solutions that provide reporting and management
capabilities for enterprise environments:

• Veeam ONE: a solution that enables real-time monitoring, business documentation and management
reporting for Veeam Backup & Replication, VMware vSphere and Microsoft Hyper-V.

• Veeam Backup Enterprise Manager: a management and reporting component that allows you to manage
multiple Veeam Backup & Replication installations from a single web console.

• Management Pack for Veeam Backup & Replication: a component that integrates
Veeam Backup & Replication infrastructure, services and jobs into Microsoft System Center Operations
Manager.

• Veeam Disaster Recovery Orchestrator: a solution that orchestrates disaster recovery processes in
VMware vSphere environments, supports one-click recovery for critical applications and sites, and
provides features for documentation and testing.

18 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Service Providers
If you are a service provider, you can use Veeam Service Provider Console to deliver Veeam-powered Backup-as-
a-Service (BaaS) and Disaster Recovery-as-a-Service (DRaaS) services to your customers.

You can also use Veeam Backup & Replication to offer cloud repository as a service and disaster recovery as a
service. For details, see Veeam Cloud Connect.

19 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Planning and Preparation
Infrastructure of Veeam Backup & Replication depends on the business needs and resources of your company.
Before you install Veeam Backup & Replication, make sure that your backup infrastructure meet product
hardware recommendations and system requirements. For more information, see these sections:

• Platform Support

• Deployment Scenarios

• System Requirements

• Permissions

• Ports

• Naming Conventions

Before you deploy Veeam Backup & Replication, consider the following tips and recommendations that may help
you design your backup infrastructure:

1. Define protection scope.

2. Define RTO and RPO goals.

3. Select Veeam Backup & Replication features that you will need.

4. Plan how many copies of your data you need to store (3-2-1 rule).

5. Design Veeam Backup & Replication infrastructure.

Step 1. Define Protection Scope


Define how many machines you need to protect and the amount of disk space the machines use.

After defining the protection scope, calculate how much of the total amount of data is actually changing on a
daily basis. This information is required because of the mechanism of how Veeam Backup & Replication creates a
backup chain. At the first run, Veeam Backup & Replication creates a full backup file; at the second and further
runs, Veeam Backup & Replication creates an incremental backup file that contains only the blocks that has been
changed since the last backup. As a result, the daily change rate has a significant impact on the backup window
and the storage capacity needed to store the backups. As Veeam Backup & Replication creates image-level or
block level backups, you need to know the daily change rate on the block level. For VMware vSphere or
Microsoft Hyper-V, you can use Veeam ONE to measure and generate a report on the daily change rate of VMs.

As a result of this step, you can make a list of machines to be protected, including the data on which of the
machines contain databases, which of the machines host business critical applications, and how much of the
total amount of data is changing on these machines on a daily basis. This information will help you in further
steps of deployment planning.

20 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Step 2. Define RPO and RTO
When you make a business continuity and disaster recovery plan, you must define two important parameters:
Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

• RP O defines a period during which you may accept to lose data. Basically, it is the age of the latest backup
that will be used for recovery in case of a failure. It means that your company accepts that in case of a
failure you may lose the data that has been accumulated since the latest restore point. RPO set by the
policy of your company defines how often you need to create a recovery point. This will help you estimate
how much storage you will need to store backups, how many copies of your data you need, and which
Veeam Backup & Replication features are the most suitable for business needs of your company.

• RTO is related to downtime. RTO represents the amount of time from the beginning of an incident until all
services are back online and available to users.

Define a list of your workloads grouped and organized by how fast they must be recoverable. Divide the list into
categories. The higher the recovery priority, the lower the RTO will be required relative to the rest of your
workloads.

Step 3. Select Veeam Backup & Replication Features


Based on the analysis of your RTO and RPO, you can define your protection plan and se lect which features are
the most suitable for your business needs. It is a common practice to divide servers and applications into
categories and use different protection functionality for each category based on SLA (service level agreement).
You can take the following table as a reference.

RP O: Seconds RP O: Minutes RP O: RP O: Hours


Hours ( 24-48)
( < 24h)

RTO: Seconds Continuous Data Protection Replication


(for VMware vSphere)

RTO: Minutes Snapshot Orchestration Backup Backup


(for VMware vSphere) Copy

RTO: Hours Tape


Devices
Support

21 | V eeam Backup & Replication | User Guide for Microsoft Hyper -V


Apart from backup and replication options, the RTO also depends on the method of recovery and recovery
verification. Veeam Backup & Replication offers a number of recovery options for various disaster recovery
scenarios, including Instant Recovery, image-level restore, file-level restore, restore of application items and so
on. For details, see the following sections:

• Restore: performing restore from backup files to the original or a new location.

• Recovery Verification: testing VM backups and replicas before recovery.

Step 4. Plan How Many Copies of Data You Need (3-2-1 rule)
To build a successful data protection and disaster recovery plan, we recommend that you follow the 3 -2-1 rule:

• 3: You must have at least three copies of your data: the original production data and two backups. The
first copy of your data is the original production data. The second copy of your data is a backup created by
a backup job. To create the third copy of data you can use Backup Copy or Backup to Tape jobs. Also, if
you use cloud repositories (S3, Azure Blob, Google Cloud, IBM Cloud), you can copy backups to a capacity
tier.

• 2: You must use at least two different types of media to store the copies of your data.

• 1: You must keep at least one backup off-site. For example, in the cloud or in a remote site. One of the
repositories must be offline, air-gaped or immutable.

Veeam Backup & Replication provides integration with various types of repositories. Select where you want to
store your backup files. For the full list of supported backup repositories, see Backup Repository, Tape Devices
Support, Storage System Snapshot Integration Guide.

To plan the required space on repositories, you may also need to analyze for how long will you store the
backups. Veeam Backup & Replication provides short-term and long-term (GFS) retention policies to effectively
store the backup files.

Step 5. Design Veeam Backup & Replication Infrastructure


Veeam Backup & Replication can be used in virtual environments of any size and complexity. The architecture of
the solution supports on-site and off-site data protection, operations across remote sites and geographically
dispersed locations. Veeam Backup & Replication provides flexible scalability and easily adapts to the needs of
your virtual environment.

NOTE

Consider general security recommendations and recommendations for hardening specific backup
infrastructure components when designing Veeam Backup & Replication infrastructure.

Before you install Veeam Backup & Replication, familiarize yourself with common deployment scenarios and
plan your backup infrastructure layout. For details, see Deployment Scenarios.

The easiest way to start is to deploy a Veeam Backup & Replication server, one dedicated server for a off-host
proxy and one repository. While you keep adding backup jobs, add more proxies and repositories. Each backup
infrastructure component has its own specifics and requirements that are described in the following sections of
this guide:

• Veeam Backup & Replication Server

• Off-Host Backup Proxy

• Backup Repository

22 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Also, note that in most cases, it is recommended to deploy Veeam Backup & Replication, Veeam Backup
Enterprise Manager and Veeam ONE on separate servers.

23 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Platform Support
This section includes information about platforms that Veeam Backup & Replication supports.

NOTE

The information on this page is valid as of the date of the last page update.

Veeam Backup & Replication provides support for the following versions of the Microsoft Hyper -V platform.

Virtual Infrastructure

Sp ecification Requirement

• Microsoft Windows Server 2022


P la tform
• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Azure Stack HCI OS
For the supported versions, see this Veeam KB article.
• Windows 111
• Windows 101

• Windows Server Hyper-V 2022


Hy p ervisor
• Windows Server Hyper-V 2019
• Windows Server Hyper-V 2016
• Windows Server Hyper-V 2012 R2
• Windows Server Hyper-V 2012
• Azure Stack HCI
• Microsoft Hyper-V Server (free hypervisor) is supported

Server Core installations are fully supported.

Microsoft Nano Server with Hyper-V role installed cannot be added to the backup
infrastructure as a managed server and no role can be assigned to it. However, you can
back up and replicate such servers, but application-aware processing is not supported
for them.

Note that you must keep your servers up-to-date.

24 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

• Microsoft PowerShell Engine 2.0 or later (optional, enables networkless guest


Ma nagement
Server (optional) processing)
• Microsoft System Center Virtual Machine Manager 2022
• Microsoft System Center Virtual Machine Manager 2019
• Microsoft System Center Virtual Machine Manager 1807
• Microsoft System Center Virtual Machine Manager 1801
• Microsoft System Center Virtual Machine Manager 2016
• Microsoft System Center Virtual Machine Manager 2012 R2
• Microsoft System Center Virtual Machine Manager 2012 SP1

1
Windows 10/11 is supported only as a target for Instant Recovery and as a host on which a virtual lab for SureBackup jobs
can be created.

VMs

Sp ecification Requirement

• Supported virtual hardware versions are 5.0 to 10.0 (valid for Hyper -V 2016 to
Ha rdware
2022).
• Both Generation 1 and 2 virtual machines are supported, including 64 TB VHDX
disks.
• Pass-through virtual disks and guest disks connected through in-guest FC or
iSCSI initiators are not supported for host-based backup. VMs with pass-through
disks cannot be snapshotted, which prevents snapshot-based backup. In-guest
connected disks are skipped from processing automatically. If backup of these
VMs/disks is required, use agent-based backup.
• [For Hyper-V Server 1803 or later] Backup of VMs with VMPmemController is
not supported.
• [For Hyper-V 2016 and later] Veeam Backup & Replication does not support
processing of VMs with shared VHDX disks. You must change the disk format to
VHD Set (VHDS).
• [For Hyper-V 2016 and later] VMs with pass-through virtual disks cannot be
processed due to Hyper-V 2016 checkpoints limitation.
• [For Hyper-V 2012 R2] Veeam Backup & Replication backs up shared VHDX disks
in a crash-consistent state.
• [For Hyper-V 2012 R2 and earlier] Backup and replication of VMs whose data
resides on a Hyper-V host volume of 64 TB and larger is not supported.

25 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS All operating systems supported by Hyper-V.

Note: You can back up VMs of Hyper-V clusters in rolling upgrade. However,
Veeam Backup & Replication does not use the Resilient Changed Tracking mechanism
in such scenario. To perform backup with RCT enabled, make sure your Microsoft
Hyper-V environment meets these requirements. It is recommended to complete the
rolling upgrade within four weeks. For more information, see Microsoft Docs.

Software Hyper-V integration components (optional, required for application-aware processing).

Consider the following:

• [For Microsoft Windows 2003 and Nano Server] Application-aware processing is not supported due to the
absence of VSS framework.

• [For Hyper-V 2016 and later] Application-aware processing for Microsoft Windows VMs with volumes
larger than 64 TB is not supported, because Veeam Backup & Replication uses the Microsoft Software
Shadow Copy Provider to create a volume shadow copy during the backup or replication. For more
information, see this Microsoft KB article.

• [For Hyper-V 2016 and later] Veeam Backup & Replication cannot interact with the guest OS of a shielded
VM and get information about its OS, IP address and so on. For this reason, the following operations are
not supported for shielded VMs:

o Application-aware image processing

o Restore of VM guest OS files to the original location

o Restore of application items to the original location

• [For Hyper-V 2016 and later] Shielded VMs can run only on trusted hosts guarded with the Host Guardian
Service. Consider that when selecting a target host for VM replication or VM restore. If the target host is
not guarded with the same Host Guardian Service as the source host, you will not be able to power on the
replicated or restored VM.

• The two previous limitations also apply to Generation 1 of Microsoft Hyper-V VMs that use Key Storage
Drive. For more information about Key Storage Drive, see Microsoft Docs.

• Guest processing (which includes application-aware processing and indexing) is supported for 64-bit
versions of the following Linux operating systems:

o CentOS 7.x

o Debian 10.0 to 11.0

o Oracle Linux 7 (UEK3) to 9 (UEK R7)

o Oracle Linux 7 to 9 (RHCK)

o RHEL 7.0 to 9.1

o SLES 12 SP4 or later, 15 SP1 or later

o Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

26 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Guest OS File Restore

OS Sup ported File Systems

• FAT, FAT32
Microsoft Windows
• NTFS
• ReFS (ReFS is supported only if Veeam Backup & Replication is installed on
Microsoft Windows Server 2012 or later.)

Windows file-level restore to original location is supported for Microsoft


Windows 2008/Windows Vista or later except Nano Server.

• ext2, ext3, ext4


Linux
• ReiserFS
• JFS
• XFS
• Btrfs

DRBD (Distributed Replicated Block Devices) are not supported.

BSD UFS, UFS2

Ma c HFS, HFS+ (volumes up to 2 TB)

• UFS
Solaris
• ZFS (except any pool versions of Oracle Solaris)

The helper appliance uses module ZFSonLinux version 0.7.0. For this reason,
Veeam Backup & Replication supports only those versions of pools and features
that are available in ZFSonLinux version 0.7.0.

For other requirements and limitations of guest OS file restore, see Requirements and Limitations.

File Servers
Veeam Backup & Replication supports backup of files and folders from the file servers managed by the following
operating systems:

• 64-bit versions of the Microsoft Windows operating systems:

o Microsoft Windows Server 2022

o Microsoft Windows Server 2019

o Microsoft Windows Server 2016

o Microsoft Windows Server 2012 R2

o Microsoft Windows Server 2012

o Microsoft Windows 11 (versions 21H2, 22H2)

27 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


o Microsoft Windows 10 (from version 1909 to version 22H2)

o Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

• 64-bit versions of the Linux operating systems:

o CentOS 7.x

o Debian 10.0 to 12.21

o Oracle Linux 7 (UEK3) to 9 (UEK R7)

o Oracle Linux 7 to 9 (RHCK)

o RHEL 7.0 to 9.31

o SLES 12 SP4 or later, 15 SP1 or later

o Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS


1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

Unstructured Data Backup Support


Veeam Backup & Replication supports backup of data from the following sources:

• Object storage repositories 1 :

o S3 compatible object storage repositories

o Amazon S3 object storage

o Microsoft Azure Blob storage

• Managed Microsoft Windows or Linux server

• Enterprise NAS systems: NetApp Data ONTAP, Lenovo ThinkSystem DM Series, Dell PowerScale (formerly
Isilon), Nutanix Files Storage

• NFS file shares

• SMB file shares


1
The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

Requirements and Limitations for File Shares


Consider the following requirements and limitations for file shares:

• Only 64-bit versions of operating systems are supported for managed Microsoft Windows or Linux server
file share.

• Backup of file shares on Linux hosts added with single use credentials is not supported.

• NFS file share must run NFS protocol version 3 or 4.1.

• Network shares and files on them targeted to 3rd party storage devices may have difficulties being
restored, or may not be restored at all. Such shares/files often rely upon specific software/OS filters to be
recalled from the alternate storage location, which is not available when performing a file share data
recovery. See your software vendor documentation to learn how to back up such files.

28 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• Anonymous or AD/Kerberos authentication is not supported for access to file shares through NFS.

In NFS settings of the source file share, you must explicitly specify what servers will have access to the file
share.

• SMB file share must run on SMB version 1.x, 2.x or 3.x.

• To support the VSS for SMB File Shares feature, make sure that requirements listed in this Veeam KB
article are met.

• To correctly back up SACL (Ownership) files and folders from the SMB file share and restore them:

a. When you are specifying access settings for the SMB file share, select the This share requires access
credentials check box.

b. Make sure that the account you use to Unstructured Data Backup access the file share is either added
to the Ba ckup Operators group or has the SeBackupPrivilege and SeRestorePrivilege privileges in
Windows Server on the file share.

Requirements and Limitations for Object Storage


Consider the following limitations for object storage added as a source of unstructured data:

• Veeam Backup & Replication does not support backup from and restore to the following types of Azure
Blob Storage: Azure Data Box Storage, Azure Stack Edge.

• Veeam Backup & Replication does not support backup from and restore to AWS Snowball Edge Storage.

For more information on unstructured data backup, see the Unstructured Data Backup section.

Network
Consider the following requirements and limitations:

• Names of port groups/segments/networks must be unique.

29 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Deployment Scenarios
Veeam Backup & Replication can be used in virtual environments of any size and complexity. The architecture of
the solution supports on-site and off-site data protection, operations across remote sites and geographically
dispersed locations. Veeam Backup & Replication provides flexible scalability and easily adapts to the needs of
your virtual environment.

Before you install Veeam Backup & Replication, familiarize yourself with common deployment scenarios and
carefully plan your backup infrastructure layout.

30 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Simple Deployment
The simple deployment scenario is good for small virtual environments or the purpose of the
Veeam Backup & Replication evaluation. In this scenario, Veeam Backup & Replication is installed on a single
Windows-based machine.

IMP ORTANT

You must not install Veeam Backup & Replication directly on a Hyper-V host. Such installation may lead to
unpredictable system behavior. Instead, install Veeam Backup & Replication and its components on
dedicated machines. Backup infrastructure component roles can be co-installed..

The machine where Veeam Backup & Replication is installed performs the following roles:

• Backup server that coordinates all jobs, controls their scheduling and performs other administrative
activities.

• Default backup repository where backup files are stored. During installation, Veeam Backup & Replication
checks volumes of the machine on which you install the product a nd identifies a volume with the greatest
amount of free disk space. On this volume, Veeam Backup & Replication creates the Backup folder that is
used as the default backup repository.

• Mount server that is needed for restoring of VM guest OS files.

• Guest interaction proxy that is needed for application-aware processing, guest file system indexing and
transaction log processing.

The role of the default backup proxy is assigned to the source Hyper -V server. It handles job processing and
transfers backup traffic directly to the target server. All services necessary for the backup proxy are installed
directly on the source Hyper-V server.

Veeam Backup & Replication is ready for use right after the installation. The only thing you must do is add
Microsoft Hyper-V servers that you plan to use as source and target for backup, replication and other activities.
For details, see Adding Microsoft Hyper-V Servers.

In Hyper-V environments that require a large number of backup or replication activities to be performed, the
simple deployment scheme is not appropriate due to the following reasons:

• The backup server may not have enough disk capacity to store the required amount of backup data.

• A significant load is placed on production servers that combine the roles of backup proxies and source
hosts.

31 | V eeam Backup & Replication | User Guide for Microsoft Hyper -V


To take the overhead off the backup server and source Hyper-V servers, you can use the advanced deployment
scenario. For details, see Advanced Deployment.

32 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Advanced Deployment
For mid-size and large-scale Hyper-V environments with a great number of backup and replication jobs, the
advanced deployment scenario can be a good choice.

The advanced deployment includes the following components:

• Virtual infrastructure servers — Hyper-V hosts used as source and target for backup and replication.

• Backup server — a configuration and control center of the backup infrastructure.

• Off-host backup proxy — a “data mover” component used to retrieve VM data from the source da tastore,
process it and deliver to the target.

• Backup repository — a location used to store backup files and auxiliary replica files.

• Dedicated mount servers — component required for VM guest OS files and application items restore to the
original location.

• Dedicated guest interaction proxies — components used to deploy the non-persistent runtime components
or persistent agent components in Microsoft Windows VMs.

In the advanced deployment scenario, data processing is shifted from the Hyper -V server to an off-host backup
proxy — a dedicated machine that is deployed on the source side, closer to the source Hyper -V host. The off-
host backup proxy functions as a “data mover”, processing VM data and mediating the backup traffic from
source to target. Therefore, the job processing overhead and data transport is offloaded from the source Hyper -
V host.

In the advanced deployment scenario, backup data is no longer stored to the backup repository on the backup
server. Instead, data is transported to dedicated backup repositories. The backup server becomes a “manager”
for off-host backup proxies and backup repositories.

With the advanced deployment scenario, you can expand your backup infrastructure horizontally in a matter of
minutes to meet your data protection requirements. Instead of growing the number of backup servers or
constantly tuning job scheduling, you can install multiple backup infrastructure components and distribute the
backup workload among them. The installation process is fully automated, which simplifies deployment and
maintenance of the backup infrastructure in your virtual environment.

33 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


In virtual environments with several proxies, Veeam Backup & Replication dynamically distributes the backup
traffic among these proxies. A job can be explicitly mapped to a specific proxy. Alternatively, you can let
Veeam Backup & Replication choose an off-host backup proxy. In this case, Veeam Backup & Replication will
check settings of available backup proxies and select the most appropriate one for the job. The backup proxy
should have access to the source and target hosts, and to backup repositories to which files will be written.

To regulate the backup load, you can specify the maximum number of concurrent tasks per backup proxy and
set up throttling rules to limit the proxy bandwidth. For a backup repository, you can set the maximum number
of concurrent tasks and define a combined data rate.

34 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Distributed Deployment
The distributed deployment scenario is recommended for large geographically dispersed virtual environments
with multiple Veeam Backup & Replication servers installed across different sites. These backup servers are
federated under Veeam Backup Enterprise Manager — an optional component that provides centralized
management and reporting for these servers through a web interface.

Veeam Backup Enterprise Manager collects data from backup servers and enables you to run backup and
replication jobs across the entire backup infrastructure through a single web console, edit them and clone jobs
using a single job as a template. It also provides reporting data for various areas (for example, all jobs
performed within the last 24 hours or 7 days, all VMs engaged in these jobs and so on). Using indexing data
consolidated on one server, Veeam Backup Enterprise Manager provides advanced capabilities to search for VM
guest OS files in VM backups created on all backup servers (even if they are stored in backup repositories on
different sites), and recover them in a single click. Search for VM guest OS files is ena bled through Veeam
Backup Enterprise Manager itself.

With flexible delegation options and security roles, IT administrators can delegate the necessary file restore or
VM restore rights to authorized personnel in the organization – for example, allow database administrators to
restore Oracle or Microsoft SQL Server VMs.

If you use Veeam Backup Enterprise Manager in your backup infrastructure, you do not need to install licenses
on every backup server you deploy. Instead, you can install one license on the Ve eam Backup Enterprise
Manager server and it will be applied to all servers across your backup infrastructure. This approach simplifies
tracking license usage and license updates across multiple backup servers.

35 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


System Requirements
Make sure that servers that you plan to use as backup infrastructure components meet the listed system
requirements.

NOTE

The information on this page is valid as of the date of the last page update.

Limitations and Recommendations


Coexistence with Mission-Critical Production Servers
We do not recommend you to install Veeam Backup & Replication and its components on mission-critical
machines in the production environment such as Microsoft Hyper-V Server, Domain Controller, Microsoft
Exchange Server, Small Business Server/ Windows Server Essentials and so on. If possible, install
Veeam Backup & Replication and its components on dedicated machines. Backup infrastructure component roles
can be co-installed.

Native Hyper-V Replication


Do not use native Hyper-V replication especially if replication is targeted at the same scope (host, cluster,
SCVMM) where the source VM resides. This can cause VM ID collision. Instead, we recommend you use Veeam
replication. For more information, see Replication.

Microsoft Windows Server Core


You can assign roles of a backup proxy, backup repository, WAN accelerator, Veeam Cloud Connect
infrastructure components and tape infrastructure components to machines running Microsoft Windows Server
Core.
Note that you cannot install Veeam Backup & Replication and Veeam Backup Enterprise Manager on a machine
running Microsoft Windows Server Core.

Windows Server IoT/Windows Storage Server Support


For information about support of Windows Server IoT/Windows Storage Server, see this Veeam KB article.

Domain Member
The machine on which you plan to install Veeam Backup & Replication does not necessarily need to be a domain
member. However, if you plan to restore Microsoft Exchange items from the Veeam Backup Enterprise Manager
UI, you must install Veeam Backup Enterprise Manager on the domain member server from the Microsoft Active
Directory forest in which Microsoft Exchange mailboxes are located.

Encrypted Communication
Veeam backup infrastructure components support the following TLS versions:

• TLS 1.3. Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), TLS 1.3 is partially supported
by backup infrastructure components installed on Microsoft Windows Server 2022. PowerShell
components and components using OpenSSL do not support TLS 1.3.

• TLS 1.2.

36 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


NOTE

For security reasons, disable outdated protocols TLS 1.0 and 1.1 if they are not needed. For more
information, see this Microsoft article.

To avoid negotiation problems between Veeam Backup & Replication and a Microsoft Windows server, ensure
that both sides of communication support the same ciphers.

To avoid negotiation problems between Veeam Backup & Replication and a Linux server, the latter should use
ciphers, Key Exchange (KEX) algorithms, and MAC algorithms compatible with SSH libraries supported by
Veeam Backup & Replication:

Alg orithms Sup ported values

Ciphers Recommended: aes128-ctr, aes192-ctr, aes256-ctr, [email protected],


[email protected], [email protected]

Supported for backward compatibility: 3des-cbc, 3des-ctr, aes128-cbc, aes192-cbc,


aes256-cbc, arcfour, arcfour128, arcfour256, blowfish-cbc, blowfish-ctr, cast128-
cbc, twofish-cbc, twofish128-cbc, twofish128-ctr, twofish192-cbc, twofish192-ctr,
twofish256-cbc, twofish256-ctr

KEX algorithms Recommended: diffie-hellman-group-exchange-sha256, diffie-hellman-group14-


sha256, diffie-hellman-group15-sha512, diffie-hellman-group16-sha512, ecdh-sha2-
nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, curve25519-sha256,
[email protected]

Supported for backward compatibility: diffie-hellman-group1-sha1, diffie-hellman-


group14-sha1, diffie-hellman-group-exchange-sha1

MAC algorithms Recommended: hmac-sha2-256, hmac-sha2-512

Supported for backward compatibility: hmac-md5, hmac-md5-96, hmac-sha-256-


96, hmac-sha1-96, hmac-sha2-512-96, hmac-ripemd160, hmac-
[email protected], hmac-sha1

Ensure that your SSH configuration on the Linux server allows you to use at least one cipher, KEX algorithm, and
MAC algorithm from the table above. You can run the following command to verify the list of allowed
algorithms:

sudo sshd -T | grep "\(ciphers\|macs\|kexalgorithms\)"

All-in-One Installations
For all-in-one installations, you can subtract 2 GB of memory resources from each but one role. These 2 GB are
allotted to the OS itself, assuming each component is installed on the dedicated server.

37 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Unstructured Data Backup
Each of the following components for unstructured data backup may consume up to 4 GB RAM per task (in case
of deduplicating storage appliances, up to 8 GB RAM): backup repository, backup proxy, cache repository. Make
sure you allocate enough memory resources for your installation. For all-in-one installations, the server where
all the components are installed must have enough memory resources for all components.

Sharing Backup Infrastructure Components Across Veeam Installations


Using Linux-based shared backup infrastructure components across different Veeam installations is not
supported.

As for non-Linux backup infrastructure components, we do not recommend using them shared across different
Veeam installations due to several reasons:

• Veeam installations compete for resources.

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

• Adding the same repository to different Veeam Backup & Replication installations may lead to corrupted
backup and data in the database.

Backup Server

Sp ecification Requirement

Ha rdware CPU: x86-64 processor (minimum 4 cores recommended).

Memory: 4 GB RAM plus 500 MB RAM for each concurrent job. Memory
consumption varies according to the number of VMs in the job, size of VM metadata,
size of production infrastructure, and so on.

Additionally, for users with tape installations (for file to tape jobs processing more
than 1,000,000 files):
• 1.5 GB RAM for file to tape backup for each 1,000,000 files
• 2.6 GB RAM for file restore for each 1,000,000 files
• 1.3 GB RAM for catalog jobs for each 1,000,000 files

Disk Space: 5 GB1 for product installation and 4.5 GB for Microsoft .NET Framework
4.7.2 installation. 10 GB per 100 VM for guest file system catalog folder (persistent
data). At least 10 GB for storing logs, although the disk space required for logging
depends on the set of features used and may significantly increase. For details on
logs locations, see Logging.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster
for off-site backup and replication. High latency and reasonably unstable WAN links
are supported.
1
Here and throughout this document GB is considered as 2^30 bytes, TB as 2^40 bytes.

38 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported 1 :

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R22, 3
• Microsoft Windows Server 20122, 3
• Microsoft Windows 11 (versions 21H2, 22H2, 23H2 4 )
• Microsoft Windows 10 (from version 1909 to version 22H2)
• Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
1
Running Veeam backup server or any of Veeam backup infrastructure components on Insider
versions of Microsoft Windows OS (both Client and Server) is not supported.
2
VMware Cloud Director servers cannot be added or used in this version of Microsoft
Windows OS.
3
There may be issues when using Veeam Backup for Nutanix AHV with backup server running
on this version of Microsoft Windows OS. For more information, see this Veeam KB article.
4
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

39 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

Configuration Local or remote installation of the following versions of PostgreSQL 1 :


Da tabase
• PostgreSQL 14.x
• PostgreSQL 15.x (PostgreSQL 15.5 is included in the
Veeam Backup & Replication 12.1 setup, PostgreSQL 15.1 is included in the
Veeam Backup & Replication 12 setup, but we strongly recommend to
download and install the latest PostgreSQL 15.x version)

Local or remote installation of the following versions of Microsoft SQL Server:

• Microsoft SQL Server 2022


• Microsoft SQL Server 2019
• Microsoft SQL Server 2017
• Microsoft SQL Server 2016
• Microsoft SQL Server 2014
• Microsoft SQL Server 2012

All editions of Microsoft SQL Server are supported. The usage of Microsoft SQL
Server Express Edition is limited by the database size up to 10 GB. If you plan to
have larger databases, use other editions of Microsoft SQL Server.

If you plan to use a database engine other than PostgreSQL 15.1, included in the
Veeam Backup & Replication setup, you must install it yourself. If you want to use
an already installed PostgreSQL instance for the configuration da tabase, make sure
the instance contains the default postgres database. If you allow the setup to
install a new PostgreSQL instance, the postgres database will be created on the
instance automatically. Since Veeam Backup & Replication connects to the
postgres database to access the configuration database, do not rename the
postgres database upon the installation.

Veeam Backup & Replication does not support Microsoft SQL Server database with
case-sensitive collations.

Veeam Backup & Replication and Veeam Backup Enterprise Manager configuration
databases can be deployed in Microsoft SQL Always On Availability Groups. For
more information, see this Veeam KB article.
1
Veeam Backup & Replication does not support PostgreSQL installations on cloud database
services (for example, Amazon Relational Database Service (RDS).

40 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

Software During setup, the system configuration check is performed to determine if all
prerequisite software is available on the machine where you plan to install
Veeam Backup & Replication. If some of the required software components are
missing, the setup wizard will offer you to install missing software automatically.
This refers to:
• Microsoft .NET Framework 4.7.2
• Microsoft ASP.NET Core Shared Framework 6.0.24
• Microsoft Edge WebView2 Runtime 119.0.2151.72 (not installed for Microsoft
Windows Server 2012 and 2012 R2 due to the version incompatibility)
• Microsoft PowerShell 5.1
• Microsoft Report Viewer Redistributable 2015
• Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL
installations)
• Microsoft Universal C Runtime
• Microsoft Windows Desktop Runtime 6.0.24

The backup server installation also requires the automatic installation of the
prerequisite software for Veeam Cloud Plug-Ins.

The following software must be installed manually:

• Firefox, Google Chrome, or Microsoft Edge (optional, to use Veeam Backup


Enterprise Manager web UI).
• Windows Installer 4.5

• RDP client version 7.0 or later installed on the backup server (required to
open the VM console during SureBackup recovery verification of Microsoft
Hyper-V VMs). The RDP client is pre-installed on Microsoft Windows
10/Windows Server 2012 OS or later.

[Optional] You can add to Veeam Backup & Replication infrastructure SCVMM
servers from version 2012 SP1 to 2022. To be able to use them, you must also install
SCVMM Admin UI on the backup server. The Admin UI version must match the
SCVMM server version.

If you plan to install Veeam Backup & Replication in the unattended mode using the
command line interface, manually install all prerequisite software before that. For
more information, see Installing Veeam Backup & Replication in Unattended Mode.

Consider the following:

• If you plan to back up VMs running Microsoft Windows Server 2012 R2 or later, and Data Deduplication is
enabled for some VM volumes, it is recommended that you deploy the Veeam Backup & Replication
console and mount server on a machine running same or later version of Microsoft Windows Server with
Data Deduplication feature enabled. Otherwise, some types of restore operations for these VMs (such as
Microsoft Windows File-Level Recovery) may fail.

• Due to its limitations, Microsoft SQL Server Express Edition can only be used for evaluation purposes or in
case of a small-scale production environment. For environments with a lot of VMs, it is necessary to install
a fully functional commercial version of Microsoft SQL Server.

41 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


For more information, see Backup Server.

Veeam Backup & Replication Console

Sp ecification Requirement

Ha rdware CPU: x86-64 processor.

Memory: 2 GB RAM

Disk Space: 500 MB for product installation and 4.5 GB for Microsoft .NET
Framework 4.7.2 installation.

Network : 1 Mbps connection to the backup server. High latency and low bandwidth
impact user interface responsiveness.

OS 64-bit versions of the following Microsoft Windows operating systems are


supported:

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows 11 (versions 21H2, 22H2, 23H2 1 )
• Microsoft Windows 10 (from version 1909 to version 22H2)
• Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

42 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

Software During setup, the system configuration check is performed to determine if all
prerequisite software is available on the machine where you plan to install the
Veeam Backup & Replication Console. If some of the required software components
are missing, the setup wizard will offer you to install missing software
automatically. This refers to:
• Microsoft .NET Framework 4.7.2
• Microsoft Edge WebView2 Runtime 119.0.2151.72 (not installed for Microsoft
Windows Server 2012 and 2012 R2 due to the version incompatibility)
• Microsoft PowerShell 5.1
• Microsoft Report Viewer Redistributable 2015
• Microsoft SQL Server System CLR Types (both for SQL Server and PostgreSQL
installations)
• Microsoft Universal C Runtime
• Microsoft Windows Desktop Runtime 6.0.24

The following software must be installed manually:


• Firefox, Google Chrome, or Microsoft Edge (optional, to use Veeam Backup
Enterprise Manager web UI)
• Windows Installer 4.5
• RDP client version 7.0 or later (required to open the VM console during
SureBackup recovery verification of Microsoft Hyper-V VMs). The RDP client
is pre-installed on Microsoft Windows 10/Windows Server 2012 OS or later.

For more information, see Backup & Replication Console.

Hyper-V Off-Host Backup Proxy/Hyper-V Host as Backup


Proxy

Sp ecification Requirement

Ha rdware CPU: modern x86-64 processor with 2 cores (vCPUs) minimum. It is recommended
to add 1 core (vCPU) for each 2 additional concurrent tasks. Using faster processors
improves data processing performance. For more information, see Limitation of
Concurrent Tasks.

Memory: 2 GB RAM plus 500 MB for each concurrent task. The actual size of
memory required may be larger and depends on the amount of data to back up,
machine configuration, and job settings. Using faster memory (DDR3/DDR4)
improves data processing performance.

Disk Space: 300 MB.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster
for off-site backup and replication. High latency and reasonably unstable WAN links
are supported.

43 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported, including Core edition:

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012

The Hyper-V role must be enabled on a machine performing the role of an off-host
backup proxy.

Note: Versions of a Microsoft Hyper-V host and off-host backup proxy must
coincide. For example, if you use a Microsoft Windows Server 2012 machine with the
Hyper-V role enabled as a Microsoft Hyper-V host, you must deploy the off-host
backup proxy on a Microsoft Windows Server 2012 machine with the Hyper -V role
enabled.

Software For off-host backup from CSV (SAN): VSS hardware provider that supports
transportable shadow copies. The VSS hardware provider is typically distributed as a
part of client components supplied by the storage vendor.

Not required for off-host backup from SMB shared storage.

For more information, see Off-Host Backup Proxy.

If you use the on-host backup mode, note that the source Hyper-V host performing the role of the backup proxy
will require additional computing resources similar to those specified as the off -host backup proxy
requirements. For more information, see On-Host Backup.

General-Purpose Backup Proxy


The following table shows the minimum system requirements for a general-purpose backup proxy used for
agent-based backup of object storage repositories, NAS, filers, file shares and off-host backup of physical
servers.

Sp ecification Requirement

Ha rdware CPU: x86-64 processor with 2 cores (vCPUs) minimum. Using multi-core processors
improves data processing performance and allows for more tasks to be processed
concurrently.

Memory: 4 GB RAM for each concurrent task. Using faster memory (DDR3/DDR4)
improves data processing performance.

Disk Space: 300 MB.

Network : High latency and reasonably unstable WAN links are supported.

44 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported:

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows 11 (versions 21H2, 22H2, 23H21 )
• Microsoft Windows 10 (from version 1909 to version 22H2)
• Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

Backup proxies running Microsoft Windows Server 2012 R2 or later support the VSS
for SMB File Shares feature. To use it, make sure that all requirements listed in this
Veeam KB article are met.

For object storage backup, also 64-bit versions of the following Linux distributions
are supported:
• CentOS 7.x
• Debian 10.0 to 12.21
• Oracle Linux 7 (UEK3) to 9 (UEK R7)
• Oracle Linux 7 to 9 (RHCK)
• RHEL 7.0 to 9.31
• SLES 12 SP4 or later, 15 SP1 or later
• Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

For more information on the backup proxy, see General-Purpose Backup Proxy.

45 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Backup Repository
These requirements also apply to mount servers (if separate from the repository server), gateway servers for file
share and deduplicating appliance-based repositories, and cache repository servers.

Sp ecification Requirement

Ha rdware CPU: x86-64 processor. The number of cores depends on the concurrent task
settings. For more information, see Limitation of Concurrent Tasks.

Memory: 4 GB RAM, plus not less than 1 GB RAM for each concurrently processed
machine disk and not less than 4 GB RAM for each concurrently processed
unstructured data source (file share or object storage repository). For more
information, see Limitation of Concurrent Tasks. For RAM allocation
recommendations for unstructured data backup, see Limitations and
recommendations for unstructured data backup.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster
for off-site backup and replication. High latency and reasonably unstable WAN links
are supported.

46 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported, including Core edition:

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows 11 (versions 21H2, 22H2, 23H2 1 )
• Microsoft Windows 10 (from version 1909 to version 22H2)
• Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

64-bit versions of the following Linux distributions are supported:

• CentOS 7.x
• Debian 10.0 to 12.21
• Oracle Linux 7 (UEK3) to 9 (UEK R7)
• Oracle Linux 7 to 9 (RHCK)
• RHEL 7.0 to 9.31
• SLES 12 SP4 or later, 15 SP1 or later
• Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS

Bash shell and SSH are required to deploy the management agent (SSH connection
is not required for updating Veeam components and can be disabled afterwards).
Perl is required only for non-persistent Veeam Data Movers. Check the full list of
required Perl modules in this Veeam KB article.

For advanced XFS integration (fast clone), only the following 64-bit Linux
distributions are supported:

• Debian 10.0 to 12.21


• RHEL 8.2 to 9.31
• SLES 15 SP2, SP3, SP4, SP5 1
• Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS

For other distributions, XFS integration support is experimental, with kernel version
5.4 or later recommended. For more information, see this Veeam KB article.
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

For more information, see the Backup Repositories section.

NOTE

Consider the following:

• If you plan to use a Microsoft Windows backup repository with Data Deduplication, make sure that
you set up the Microsoft Windows server correctly. For more information, see this Veeam KB article.
• In rare cases, Veeam backups may become corrupted when stored on the exFAT file system. We
strongly discourage using the exFAT filesystem for backup storage when attached to Windows 10 or
Windows Server 2019 and later. For more information, see this Veeam KB article.

47 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Cache Repository
The following storage types can be used as a cache repository for unstructured data backup:

• Direct attached storage. You can add virtual and physical servers as cache repositories:

o Microsoft Windows server (only 64-bit versions are supported).

o Linux server (only 64-bit versions are supported).

• Network attached storage. You can add SMB (CIFS) Share or NFS Share as a cache repository.

For system requirements of backup repositories that can be used as a cache repository, see Backup Repository.

For more information on the cache repository, see Ca che Repository in the Backup Infrastructure for
Unstructured Data Backup section.

Cache Repository for Object Storage Repository


If the cache repository works with an unstructured data source being backed up to an object storage repository,
it also processes active metadata that is heavily used during backup and restore operations. So you will require
more disk space for the cache repository. The volume of this disk space depends on the number of the file
versions on the data source and the number of unstructured data backup jobs that protect this data source. We
recommend allocating not less than 1 GB of disk space for active metadata of each 1,000,000 file versions
protected with 1 file backup job or object storage backup job. If you protect the same data source, for example,
with 2 different backup jobs, the volume of metadata will double. For more information, see the Unstructured
Data Backups in Object Storage Repositories section.

TIP

We strongly recommend utilizing a fast storage disk, for example, an SSD in the role of the cache
repository used for working with an object storage repository.

Tape Server

Sp ecification Requirement

Ha rdware CPU: x86-64 processor with 2 cores (vCPUs) minimum. Using multi-core processors
improves data processing performance and allows for more tasks to be processed
concurrently.

Memory : 2 GB RAM plus 500MB for each concurrent task. Depending on the source
of tape jobs, different entities are considered tasks: for machine backup to tape, a
task covers a source job or a source chain if tape paralleling is enabled; for file
backup to tape, a task covers an entire server or a file share. Restoring VMs directly
from tape requires 400MB of RAM per 1TB of the restored virtual disk size. Tape
cloning requires 1GB RAM for each concurrent task.

Disk Space: 300 MB, plus 10 GB for temporary data storage for backup and restore
operations.

Network : 1 Gbps or faster.

For system requirements for large number of files in the file backup to tape job, see
Before You Begin file backup to tape.

48 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported, including Core edition:
o Microsoft Windows Server 2022
o Microsoft Windows Server 2019
o Microsoft Windows Server 2016
o Microsoft Windows Server 2012 R2
o Microsoft Windows Server 2012
o Microsoft Windows 11 (versions 21H2, 22H2, 23H2 1 )
o Microsoft Windows 10 (from version 1909 to version 22H2)
o Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

64-bit versions of the following Linux distributions are supported 2:


o CentOS 7.x
o Debian 10.0 to 12.21
o Oracle Linux 7 (UEK3) to 9 (UEK R7)
o Oracle Linux 7 to 9 (RHCK)
o RHEL 7.0 to 9.31
o SLES 12 SP4 or later, 15 SP1 or later
o Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).
2
Note that the tape server requires root access rights. For this reason, hardened repository
cannot be used as the tape server.

WAN Accelerator

Sp ecification Requirement

Ha rdware CPU: x86-64 processor. Using multi-core processors improves data processing
performance, and is highly recommended on WAN links faster than 10 Mbps.

Memory : 8 GB RAM. Using faster memory (DDR3/DDR4) improves data processing


performance.

Disk Space: Disk space requirements depend on the WAN Accelerator role. Source
WAN Accelerator requires 20 GB per 1 TB of source data to store digests of data
blocks of source VM disks. Disk space consumption is dynamic and changes as
unique VMs are added to (or removed from) jobs with WAN Acceleration enabled.
Target WAN Accelerator requires global cache size as defined by user (fixed
amount). Disk space is reserved immediately upon selecting the WAN Accelerator as
a target one in any job. For more information, see WAN Accelerator Sizing.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster
for off-site backup and replication. High latency and reasonably unstable WAN links
are supported.

49 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Sp ecification Requirement

OS 64-bit versions of the following Microsoft Windows operating systems are


supported, including Core edition:
o Microsoft Windows Server 2022
o Microsoft Windows Server 2019
o Microsoft Windows Server 2016
o Microsoft Windows Server 2012 R2
o Microsoft Windows Server 2012
o Microsoft Windows 11 (versions 21H2, 22H2, 23H2 1 )
o Microsoft Windows 10 (from version 1909 to version 22H2)
o Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

For more information, see WAN Accelerators.

NOTE

Global cache is not leveraged by source WAN accelerators, or by WAN accelerators operating in the Hig h
b a ndwidth mode, so it does not need to be allocated and populated in such cases.

Backup Target
Backed up data can be stored in the following disk-based systems:

• Local (internal) storage of the backup repository

• Direct Attached Storage (DAS)


The DAS must be connected to the backup repository, including external USB/eSATA drives, USB pass
through and raw device mapping (RDM) volumes.

• Storage Area Network (SAN)

The backup repository must be connected into the SAN fabric through hardware or virtual HBA, or
software iSCSI initiator.

• Network Attached Storage (NAS)


The NAS must be able to present its capacity as NFS share (protocol versions 3.0 and 4.1 only) or SMB
(CIFS) share (any protocol versions). Using consumer-grade NAS storage without an enterprise-grade
RAID controller with battery-backed write cache (BBWC) is not recommended for reliability
considerations.

• Amazon S3

• Google Cloud Storage

• IBM Cloud Object Storage

• Microsoft Azure Blob Storage

• Wasabi Hot Cloud Storage 1

50 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• Any S3-compatible object storage (on-premise appliance, or cloud storage provider)

• Dell Data Domain (DD OS version 6.2 2 to 7.12) with DDBoost license

Both Ethernet and Fibre Channel (FC) connectivity is supported.

• ExaGrid 3 (firmware version 5.0.0 or later)

• Fujitsu ETERNUS CS800 3 software version 3.4.0 or later

• HPE StoreOnce (firmware version 3.18.18 or later for Gen3 and 4.2.3 or later for Gen4) with Catalyst
license

Both Ethernet and Fibre Channel (FC) connectivity are supported. Note that HPE StoreOnce Federated
Catalyst is not supported.

• Infinidat InfiniGuard 3 version 3.6 and later

• Quantum3 (DXi software 3.4.0 or later)

Supported Quantum DXi systems include DXi4700 (NAS configuration), DXi4700 (multi-protocol
configuration), DXi 4800, DXi 6900, DXi 6900-S, DXi 9000, DXi 9100, and DXi V5000. FIPS-
compliant operations mode requires DXi software 4.0 or later.
1
From Veeam Backup & Replication 12.1 (build 12.1.0.2131).
2
The minimum supported version for Veeam Backup & Replication 12.1 (build 12.1.0.2131) is 7.3.
3
These storage systems use the Veeam Transport Service. Make sure that they also meet system requirements for the
backup repository.

Once backups are created, they can be copied (for redundancy) or offloaded (for long -term retention) to one of
the following hot object storage types using the scale-out backup repository Capacity Tier:

• Amazon S3 (including AWS Snowball Edge)

• Google Cloud Storage

• IBM Cloud Object Storage

• Microsoft Azure Blob storage (including Microsoft Azure Data Box)

• Wasabi Hot Cloud Storage

• Any S3-compatible object storage (on-premises appliance, or cloud storage provider)

Once backups are created on Amazon S3, Microsoft Azure Blob Storage, or S3-compatible object storage
systems with the archiving extension of Smart Object Storage API, they can be further archived to one of the
following respective cold object storage classes using the scale-out backup repository Archive Tier:

• Amazon S3 Glacier Instant Retrieval

• Amazon S3 Glacier Flexible Retrieval

• Amazon S3 Glacier Deep Archive

• Microsoft Azure Archive Tier

• Microsoft Azure Cold Tier

For the full list of partner-tested solutions including primary backup storage solutions, S3-compatible object
storage solutions and offline storage solutions, see this Veeam page.

51 | V eeam Backup & Replication | User Guide for Microsoft Hyper -V


For information on unstructured data backup target, see Storage Repositories in the Backup Infrastructure for
Unstructured Data Backup section.Tape

Sp ecification Requirement

Ha rdware The following types of tape libraries (including VTL) and standalone drives are
supported:
o LTO3-LTO9
o IBM 3592 (TS1160 and TS1170) 1

Tape device must be directly attached to the backup server, to a tape server
through SAS, FC or iSCSI interface.
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

o Tape devices without device-specific, vendor-supplied OEM drivers for


Software
Windows will appear in Windows Device Manager as Unknown or Generic and
require enabling native SCSI commands mode.
o If multiple driver installation modes are available for your tape device, use
the one that allows for multiple open handles from a host to a drive to exist
at the same time. Usually, such drivers are referred to as “non-exclusive”.
o No other backup server must be interacting with the tape device.

Storage Systems
Veeam Backup & Replication provides the following types of snapshot integrations: NAS integration, VMware
integration and Veeam Agent integration. Each type of integration supports different storage systems.

NAS Integration
NAS integration is possible with the following built-in storage systems.

Dell PowerScale (formerly Isilon)

• Filer integration for NAS backup functionality

• NFS or SMB (CIFS) connectivity

• OneFS 8.1.2 to 9.5

Fujitsu ETERNUS HX/AX

• NFS or SMB (CIFS) connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• Synchronous SnapMirror is not supported

52 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Lenovo DM Series

• NFS or SMB (CIFS) connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• Synchronous SnapMirror is not supported

NetApp FAS/AFF/ASA, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA

• NFS or SMB (CIFS) connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• NetApp Synchronous SnapMirror is not supported

Nutanix Files

• Filer integration for NAS backup functionality

• NFS or SMB (CIFS) connectivity

• Nutanix File Server 3.8.1.3 to 4.2.0

Veeam Agent Integration with Built-in Storage Systems


VMware and Veeam Agent integrations are possible with the following built-in storage systems.

Dell VNX, VNX2, VNXe and Unity XT/Unity

• NFS, Fibre Channel (FC) or iSCSI connectivity

• Dell VNX/VNX2 all OE versions are supported

• Dell VNXe OE versions 3.x

• Dell Unity XT/Unity OE versions 5.0 to 5.2

Fujitsu ETERNUS HX/AX

• NFS, Fibre Channel or iSCSI connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

53 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• Synchronous SnapMirror is not supported

HPE 3PAR StoreServ

• Fibre Channel (FC) or iSCSI connectivity

• 3PAR OS versions 3.2.2 up to 3.3.2

• WSAPI 1.5 and later

• iSCSI VLAN tags are supported

• Virtual Domains are supported

HPE Primera

• Fibre Channel (FC) or iSCSI (starting from OS versions 4.3 or later) connectivity

• OS versions 4.x

• Virtual Domains are supported

HPE Alletra 9000

• Fibre Channel (FC) or iSCSI connectivity

• OS version 9.3 or later

• Virtual Domains are supported

HPE Alletra MP

• Fibre Channel (FC) connectivity

• OS version 10.2 or later

• Virtual Domains are supported

HPE Nimble Storage AF-Series, HF-Series and CS-Series

• Fibre Channel (FC) or iSCSI connectivity

• Nimble OS 5.0 and later

HPE Alletra 5000/6000

• Fibre Channel (FC) or iSCSI connectivity

• OS version 6.0

HPE StoreVirtual (formerly LeftHand/P4000 Series) and StoreVirtual VSA

• iSCSI connectivity only

• LeftHand OS versions 9.5 up to 12.8

54 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• HPE SV3200 (LeftHand OS version 13) is not supported

IBM FlashSystem (formerly Spectrum Virtualize, includes IBM StorWize and IBM SVC)

• Fibre Channel (FC) or iSCSI connectivity

• IBM Spectrum Virtualize OS version 8.2 or later

• Policy-based replication is not supported

IBM N Series

• NFS, Fibre Channel or iSCSI connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• Synchronous SnapMirror is not supported

Lenovo DM Series

• NFS, Fibre Channel or iSCSI connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

• Synchronous SnapMirror is not supported

Lenovo Storage V Series

• Fibre Channel (FC) or iSCSI connectivity

• Spectrum Virtualize 8.2 or later

• Policy-based replication is not supported

NetApp FAS/AFF/ASA, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA

• NFS, Fibre Channel or iSCSI connectivity

• ONTAP 7-mode versions 8.2 up to 8.2.5

• ONTAP cluster-mode versions 9.1 to 9.13.1 (Version 9.13.1 has some issues. For more details, see this
Veeam KB article.)

• MetroCluster is supported

• ONTAP features application-aware data management and SVM-DR are not supported

55 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• NetApp Synchronous SnapMirror is not supported

Veeam Agent Integration with Universal Storage API Integrated Systems


To start working with Universal Storage API integrated systems, you must install storage system plug-ins.
VMware and Veeam Agent integrations are possible with the following storage systems.

DataCore SANsymphony

• Fibre Channel (FC) or iSCSI connectivity

• DataCore SANsymphony 10.0 PSP12 or later

Dell PowerMax

• Fibre Channel (FC) or iSCSI connectivity

• Dell PowerMax/VMAX All Flash (PowerMax OS microcode family 5978 or later)

• Unisphere for PowerMax 9.2.1.6 or later

Dell PowerStore

• Fibre Channel (FC) or iSCSI connectivity

• Dell PowerStore T and PowerStore X series (PowerStore OS 3.x or later)

Dell SC Series (formerly Compellent)

• Fibre Channel (FC) or iSCSI connectivity

• Storage Center OS 7.4.2 or later

• FluidFS volumes and Live Volumes are not supported

Fujitsu ETERNUS AF and DX Series

• Fibre Channel (FC) or iSCSI connectivity

• ETERNUS AF series: AF250 S2, AF650 S2, AF150 S3, AF250 S3, AF650 S3

• ETERNUS DX series: DX60 S4, DX100 S4, DX200 S4, DX500 S4, DX600 S4, DX8900 S4, DX60 S5,
DX100 S5, DX200 S5, DX500 S5, DX600 S5, DX900 S5

• Storage firmware version:

o ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later

o ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later

Hitachi VSP

• Fibre Channel (FC) or iSCSI connectivity

• VSP E series (93-03-01-60/00 or later)

• VSP F series (88-07-01-x0/00 or later)

• VSP G series (88-07-01-x0/00 or later)

56 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• VSP 5100 and VSP 5500 (90-05-01-00/00 or later)

• VSP 5200 and VSP 5600 (90-08-01-00/00 or later)

HPE XP

• Fibre Channel (FC) or iSCSI connectivity

• HPE XP8 (90-05-01-00/00 or later)

INFINIDAT Infinibox F-Series

• NFS, Fibre Channel (FC) or iSCSI connectivity

• InfiniBox 5.0 or later

NOTE

You must add to the backup infrastructure only one of the two InfiniBox storage arrays for which
Active/Active Replication is configured, or exclude the replicating volumes on one of these arrays from
rescan. For details on how to exclude volumes from rescan, see the Rescanning Storage Systems section in
the Veeam Backup & Replication User Guide.

NEC Storage M Series

• Fibre Channel (FC) or iSCSI connectivity

• M120, M320, M320F, M520, M720, M720F (Storage Control Software revision 1234 or later)

NEC Storage V Series

• Fibre Channel (FC) or iSCSI connectivity

• V100, V300 (93-04-21-XX or later), V10e (88-08-09-XX or later)

NetApp SolidFire/HCI

• iSCSI connectivity

• Element OS version 10.0 or later

Pure Storage FlashArray

• Fibre Channel (FC) or iSCSI connectivity

• Purity 4.10 or later

Tintri IntelliFlash (formerly Western Digital IntelliFlash, Tegile)

• NFS, Fibre Channel (FC) or iSCSI connectivity

• Tintri IntelliFlash 3.11 or later

57 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Gateway Server

Sp ecification Requirement

Ha rdware CPU: x86-64 processor, 2 or more cores.

Memory: 4 GB RAM, plus up to 4 GB RAM for each concurrently processed machine,


file share or object storage. For more information, see Limitation of Concurrent
Tasks. For RAM allocation recommendations for unstructured data backup, see
Limitations and recommendations for unstructured data backup .

Disk space: 2 GB per TB of data processed during a SOBR offload job for a machine
that acts as a gateway server for an Object Storage Repository. For more
information, see this Veeam KB article.

Note: If a unstructured data backup stored in an object storage does not have
metadata in the cache repository, during the restore or health check operation this
metadata will be downloaded to the gateway server. That can consume up to 80%
of the gateway server disk space.

Network : 1 Gbps or faster for on-site backup and replication, and 1 Mbps or faster
for off-site backup and replication. High latency and reasonably unstable WAN links
are supported.

OS 64-bit versions of the following Microsoft Windows operating systems are


supported:

• Microsoft Windows Server 2022


• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows 11 (versions 21H2, 22H2, 23H2 1 )
• Microsoft Windows 10 (from version 1909 to version 22H2)
• Microsoft Windows 10 LTS (versions LTSB 1607, LTSC 1809, LTSC 2021)

For the communication with object storage repositories, external repositories and
NFS backup repositories, you can use machines running 64-bit versions of the
following Linux distributions:
• CentOS 7.x
• Debian 10.0 to 12.21
• Oracle Linux 7 (UEK3) to 9 (UEK R7)
• Oracle Linux 7 to 9 (RHCK)
• RHEL 7.0 to 9.31
• SLES 12 SP4 or later, 15 SP1 or later
• Ubuntu: 18.04 LTS, 20.04 LTS, and 22.04 LTS
1
This version requires Veeam Backup & Replication 12.1 (build 12.1.0.2131).

For more information, see Gateway Server.

58 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Mount Server
The mount server role must be assigned to a 64-bit Microsoft Windows machine added to the backup
infrastructure. For the list of supported OSes, see Veeam Backup & Replication Console.

On the mount server machine, Veeam Backup & Replication installs the Veeam Mount Service. The Veeam
Mount Service requires Microsoft .NET Framework 4.7.2. If Microsoft .NET Framework 4.7.2 is not installed on
the machine, Veeam Backup & Replication will install it automatically.

If you plan to restore VM guest OS files from VMs running Microsoft Windows ReFS or from VMs with data
deduplication enabled for some volumes, you must assign the mount server role to machines running specific OS
versions. For more information, see ReFS and Data Deduplication subsections in Restoring VM Guest OS Files
(FAT, NTFS or ReFS).

[For Microsoft Windows 2008R2/7] Make sure that you have SHA-2 code signing support installed. Normally,
this component is included in Microsoft Windows updates. For more information, see Microsoft Docs.

The following jobs consume 1 GB RAM per guest VM disk on mount server + 100 MB RAM per VM:

• SureBackup

• Instant Recovery

• Instant Disk Recovery

For more information on the mount server, see Mount Server.

Veeam Backup Enterprise Manager Server


The machine where you plan to install Veeam Backup Enterprise Manager must meet the requirements listed in
the System Requirements section of the Enterprise Manager User Guide.

Veeam Plug-Ins
The machine where you plan to install Veeam plug-ins must meet the following requirements:

Veeam Plug-In Requirement

AW S P lug-in for Veeam Microsoft .NET Core Runtime 6.0 or later


Ba ckup & Replication
version 12.0.5.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for AWS
Integration with Veeam Backup & Replication Guide.

Microsoft Azure Plug-in for Microsoft .NET Core Runtime 6.0 or later
Veeam Backup & Replication
version 12.0.4.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for
Microsoft Azure Integration with Veeam Backup & Replication Guide.

59 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Veeam Plug-In Requirement

Goog le Cloud Plug-in for Microsoft .NET Core Runtime 6.0 or later
Veeam Backup & Replication
version 12.0.3.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for
Google Cloud Integration with Veeam Backup & Replication Guide.

Nuta nix AHV P lug-in for Microsoft .NET Core Runtime 6.0 or later
Veeam Backup & Replication
version 12.0.4.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for
Nutanix AHV User Guide.

RHV P lug-in for Microsoft .NET Core Runtime 6.0 or later


Veeam Backup & Replication
version 12.0.3.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for RHV
User Guide.

Ka sten K10 Plug-in for Microsoft .NET Core Runtime 6.0 or later
Veeam Backup & Replication
version 12.0.0.xxx and later Microsoft ASP.NET Core Shared Framework 6.0 or later

For other system requirements of the plug-in, see the Veeam Backup for
Kasten K10 User Guide.

Supported Applications
You can create transactionally-consistent backups or replicas of VMs that run the following applications.

Ap p lication Requirement

Microsoft Active Veeam Backup & Replication supports backup of domain controllers for the
Directory following operating systems:
• Microsoft Windows Server 2022
• Microsoft Windows Server 2019
• Microsoft Windows Server 2016
• Microsoft Windows Server 2012 R2
• Microsoft Windows Server 2012
• Microsoft Windows Server 2008 R2
• Microsoft Windows Server 2008

Minimum supported domain and forest functional level is Windows 2008.

60 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Ap p lication Requirement

Microsoft Exchange Veeam Backup & Replication supports backup of the following Microsoft Exchange
versions:

• Microsoft Exchange 2019


• Microsoft Exchange 2016
• Microsoft Exchange 2013

Microsoft SharePoint Veeam Backup & Replication supports backup of the following versions of Microsoft
SharePoint Server (virtualized either on VMware or Hyper-V platform):
• Microsoft SharePoint Server Subscription Edition
• Microsoft SharePoint 2019
• Microsoft SharePoint 2016
• Microsoft SharePoint 2013

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

Restore of Microsoft SharePoint data may require an available staging Microsoft SQL
Server. To learn how to configure this server, see the Configuring Staging SQL
Server section of the Veeam Explorers User Guide.

Microsoft SQL Server Veeam Backup & Replication supports backup of the following Microsoft SQL Server
versions:

• Microsoft SQL Server 2022 (only for Windows)


• Microsoft SQL Server 2019 (only for Windows)
• Microsoft SQL Server 2017 (only for Windows)
• Microsoft SQL Server 2016 SP2
• Microsoft SQL Server 2014 SP3
• Microsoft SQL Server 2012 SP4
• Microsoft SQL Server 2008 R2 SP3
• Microsoft SQL Server 2008 SP4

All editions of Microsoft SQL Server except LocalDB are supported.

The database whose logs you want to back up must use the Full or Bulk-logged
recovery model. In this case, all changes of the Microsoft SQL Server state will be
written to transaction logs, and you will be able to replay transaction logs to restore
the Microsoft SQL Server. You can use the Microsoft SQL Server Management Studio
to switch to one of these models. For more information, see Microsoft Docs.

Restore of Microsoft SQL Server data may require an available staging Microsoft SQL
Server. To learn how to configure this server, see the Configuring Staging SQL
Server section of the Veeam Explorers User Guide.

61 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Ap p lication Requirement

Ora cle on Windows Veeam Backup & Replication supports backup of the following Oracle Database
OS versions on Microsoft Windows machines:

• Ora cle Database 21c


For supported operating systems, see Oracle documentation.
• Ora cle Database 19c
For supported operating systems, see Oracle documentation.
• Ora cle Database 18c
For supported operating systems, see Oracle documentation.
• Ora cle Database 12c Release 2
For supported operating systems, see Oracle documentation.
• Ora cle Database 12c Release 1
For supported operating systems, see Oracle documentation.
• Ora cle Database 11g Release 2
For supported operating systems, see Oracle documentation.

Ora cle on Linux OS Veeam Backup & Replication supports backup of the following Oracle Database
versions on Linux machines:

• Ora cle Database 21c


For supported operating systems, see Oracle documentation.
• Ora cle Database 19c
For supported operating systems, see Oracle documentation.
• Ora cle Database 18c
For supported operating systems, see Oracle documentation.
• Ora cle Database 12c Release 2
For supported operating systems, see Oracle documentation.
• Ora cle Database 12c Release 1
For supported operating systems, see Oracle documentation.
• Ora cle Database 11g Release 2
For supported operating systems, see Oracle documentation.

Starting from version 12.1 (build 12.1.0.2131), Veeam Backup & Replication supports
the backup of Linux-based VMs with several Oracle homes of different versions.

62 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Ap p lication Requirement

Ora cle Database Consider the following:


configuration
• Automatic Storage Management (ASM) is supported for Oracle 11g and later;
requires ASMlib present.
• Oracle Real Application Clusters (RAC) are not supported within the image-
level backup functionality. Use Veeam Plug-in for Oracle RMAN. For details,
see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-ins for
Enterprise Applications User Guide.
• Oracle Database Express Edition (XE) is supported for Windows-based
machines only.
• Configurations with different versions of Oracle Database deployed on the
same server are not supported. Use Veeam Plug-in for Oracle RMAN. For
details, see the Veeam Plug-in for Oracle RMAN section of the Veeam Plug-
ins for Enterprise Applications User Guide.
• To create Oracle database backups, all Oracle servers that use Data Guard
must be added to the backup job.
• You can use Veeam Plug-in for Oracle RMAN to integrate RMAN with
Veeam Backup & Replication repositories. For details, see the Veeam Plug-in
for Oracle RMAN section of the Veeam Plug-ins for Enterprise Applications
User Guide.

P ostgreSQL Veeam Backup & Replication supports backup of the following PostgreSQL versions
on Linux machines:
• PostgreSQL 16
• PostgreSQL 15
• PostgreSQL 14
• PostgreSQL 13
• PostgreSQL 12

NOTE

Consider that 32-bit Oracle running on 64-bit operating systems and Oracle Express Edition (XE) on Linux
are not supported.

Veeam Explorers
• Veeam Explorer for Microsoft Active Directory

• Veeam Explorer for Microsoft Exchange

• Veeam Explorer for Microsoft SharePoint

• Veeam Explorer for Microsoft SQL

• Veeam Explorer for Microsoft Teams

• Veeam Explorer for Oracle

63 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• Veeam Explorer for PostgreSQL

64 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Permissions
Make sure the user accounts that you plan to use have permissions described in the following sections.

Installing and Using Veeam Backup & Replication


The accounts used for installing and using Veeam Backup & Replication must have the following permissions.

Account Required P ermission

Setup Account The account used for product installation must have
the local Administrator permissions on the target
machine.

Veeam Backup & Replication Console Permissions When you open the Veeam Backup & Replication
console for the first time or after a cumulative patch
is installed on the backup server, you must run the
console under an account with the local
Administrator permissions on the machine where the
console is installed. In other cases, you can run it
under an account that is a member of the Users
group on the machine where the console is installed.
However, you may require additional permissions to
recover guest OS files of Microsoft Windows VMs.

[For recovery of Microsoft Windows VM guest OS


files] If you plan to save files to a new location, the
user who launched the Veeam Backup & Replication
console does not have permissions to read and write
data to the new location, and the mount point is
located on the same machine as the
Veeam Backup & Replication console, check that the
user has the SeBackupPrivilege and
SeRestorePrivilege . For more information on where
mount points are created, see Mount Points and
Restore Scenarios.

Accounts that are members of the Protected Users


Active Directory group cannot be used to access the
backup server remotely over the
Veeam Backup & Replication console. For more
information, see Microsoft Docs.

Veeam Backup Service Account The account used to run the Veeam Backup Service
must be a LocalSystem account or must have the
local Administrator permissions on the backup
server.

65 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Account Required P ermission

Microsoft SQL Server You require different sets of Microsoft SQL


( where the configuration database is stored) permissions in the following cases:

• Installation (remote or local): current account


needs CREATE ANY DATABASE permission on
the SQL server level. After database creation
this account automatically gets a db_owner
role and can perform all operations with the
database. If the current account does not have
this permission, a Database Administrator may
create an empty database in advance and
grant the db_owner role to the account that
will be used for installing
Veeam Backup & Replication.
• Upgrade: current account should have
sufficient permissions for that database. To
grant these permissions through role
assignment, it is recommended that you use
the account with db_owner role.
• Operation: the account used to run Veeam
Backup Service requires db_datareader and
db_datawriter roles as well as permissions to
execute stored procedures for the
configuration database on the Microsoft SQL
Server. Alternatively, you can assign db_owner
role for this database to the service account.

For more information, see Microsoft Docs.

P ostgreSQL The account used for installation, upgrade and


operation requires superuser role.

Using Virtualization Servers and Hosts


The following permissions are required to work with virtualization servers and hosts during data protection
tasks.

Role Required P ermission

Source / Target Administrator permissions.


Hy p er-V host or
cluster

66 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Role Required P ermission

SCVMM Any SCVMM user.

W ind ows Server Administrator permissions


a d ded to the
b a ckup
infrastructure

Linux Server Permissions for the account that you specify when adding a Linux server differ
a d ded to the depending on the role that you plan to assign to this server:
b a ckup
• Roles for which Veeam Data Movers must be persistent (hardened/immutable
infrastructure
repository) require root or equivalent permissions. For the full list of roles, see
Veeam Data Movers.
• Gateway server that communicates with NFS share requires root or equivalent
permissions.
• Backup repository requires read and write permissions on the folder where
backups will be stored. You will configure this folder at the Configure Backup
Repository Settings step of the backup repository wizard.
• Other roles require read and write permissions on files and folders with which
the server will work.

SMB Backup Read and write permission on the target folder and share.
Rep ository

Performing Guest Processing


To use guest OS processing (application-aware processing, pre-freeze and post-thaw scripts, transaction log
processing, guest file indexing and file exclusions), make sure to configure your accounts according to the
requirements listed in this section. For more information on guest processing, see Guest Processing.

All user accounts used for guest processing of Windows VMs must have the following permissions:

• Logon as a batch job granted

• Deny logon as a batch job not set

67 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Other permissions depend on applications that you back up. You can find permissions for backup operations in
the following table. For restore operation permissions, see P ermissions sections in the Veeam Explorers User
Guide.

Ap p lication Required P ermission

Microsoft SQL To back up Microsoft SQL Server data, the user whose account you plan to use must
Server be:
• Local Administrator on the target VM.
• System administrator (has the Sysadmin role) on the target Microsoft SQL
Server.

If you need to provide minimal permissions, the account must be assigned the
following roles and permissions:
• SQL Server instance-level role: public and dbcreator.
• Database-level roles and roles for the model system database:
db_backupoperator , db_denydatareader , public;
for the master system database — db_backupoperator , db_datareader , public;
for the msdb system database — db_backupoperator , db_datareader , public,
db_datawriter.
• Securables: view any definition, view server state, connect SQL .

Microsoft Active To back up Microsoft Active Directory data, the account must be a member of the
Directory built-in Administrators group.

Microsoft To back up Microsoft Exchange data, the account must have the local Administrator
E x change permissions on the machine where Microsoft Exchange is installed.

Ora cle The account specified at the Guest Processing step must be configured in the following
way:
• For a Windows-based VM, the account must be a member of both the Local
Administrator group and the ORA_DBA group (if OS authentication is used). In
addition, if ASM is used, then such an account must be a member of the
ORA_ASMADMIN group (for Oracle 12 and higher).
• For a Linux-based VM, the account must be a Linux user elevated to root. The
account must have the home directory created.

To back up Oracle databases, make sure the account specified on the Ora cle tab has
been granted SYSDBA privileges. You can use either the same account that was
specified at the Guest Processing step if such an account is a member of the ORA_DBA
group for a Windows-based VM and OSASM, OSDBA and OINSTALL groups for a Linux-
based VM, or you can use, for example, the SYS Oracle account or any other Oracle
account that has been granted SYSDBA privileges.

To perform guest processing for Oracle databases on Linux servers, make sure that the
/tmp directory is mounted with the exec option. Otherwise, you will get an error with
the permission denial.

68 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Ap p lication Required P ermission

Microsoft To back up Microsoft SharePoint server, the account must have the Farm Administrator
Sha rePoint role.

To back up Microsoft SQL databases of the Microsoft SharePoint Server, the account
must have the same privileges as that of Veeam Explorer for Microsoft SQL Server.

P ostgreSQL The account specified at the Guest Processing step must be a Linux user elevated to
root. The account must have the home directory created.

Note: If you back up data using vSphere API, the account specified at the Guest
P rocessing step must be a root Linux user.

To back up PostgreSQL instances, the account must have the superuser privileges for
the PostgreSQL instance. For more information, see PostgreSQL documentation.

Consider the following general requirements when choosing a user account:

• [For guest OS file indexing] For Windows-based workloads, choose an account that has administrator
privileges. For Linux-based workloads, choose an account of a root user or user elevated to root.

• To use networkless guest processing over PowerShell Direct, you must specify one of the following
accounts at the Guest P rocessing step of the backup wizard. Check that the account also has permissions
listed in the table.

o If Windows User Account Control (UAC) is enabled, specify Local Administrator


(MACHINE\Administrator) or Domain Administrator (DOMAIN\Administrator) account.

o If UAC is disabled, specify an account that is a member of the built-in Administrators group.

• [If you plan to use guest processing over network for workloads without listed applications] For Windows -
based workloads, choose an account that has administrator p rivileges. For Linux-based workloads, choose
an account of a root user or user elevated to root.

• When using Active Directory accounts, make sure to provide an account in the DOMAIN\Username format.

• When using local user accounts, make sure to provide a n account in the Username or HOST\Username
format.

• To process a Domain Controller server, make sure that you are using an account that is a member of the
DOMAIN\Administrators group.

• To back up a Read-Only Domain controller, a delegated RODC administrator account is sufficient. For more
information, see Microsoft Docs.

Adding Microsoft Azure Compute Accounts


Microsoft Azure Compute account is required to restore workloads to Microsoft Azure, add Azure archive
storage and so on. For more information, see Microsoft Azure Compute Accounts.

69 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


The following permissions are required for adding a Microsoft Azure Compute account:

• If you use a new Microsoft Entra ID (formerly Azure Active Directory) application (select the Create a new
a ccount option at the Subscription step of the wizard) when adding a Microsoft Azure Compute account,
the Microsoft Entra ID user account where the Microsoft Entra ID application will be created must have
the following privileges:

a. To register applications. For this, you can assign the Global Administrator privileges to the user or
enable the Users can register applications option for the user in Azure portal. For details, see
Microsoft Azure Docs.

b. To assign a role on the subscription level for the registered application. For this, you can use the
Owner role or if the Owner role cannot be used, you can create a custom role with minimal
permissions. To learn how to create a custom role, see Creating Custom Role for Azure and Azure
Stack Hub Accounts.

• If you use an existing Microsoft Entra ID (formerly Azure Active Directory) application (select the Use the
ex isting account option at the Subscription step of the wizard) when adding a Microsoft Azure Compute
account, the application must have the Contributor, Key Vault Crypto User and Storage Queue Data
Contributor role privileges for the selected subscription. If you cannot use these roles, you can create a
custom role with minimal permissions. To learn how to create a custom role, see Creating Custom Role for
Azure and Azure Stack Hub Accounts.

Adding Microsoft Azure Stack Hub Compute Accounts


A Microsoft Azure Stack Hub Compute account is required to restore workloads to Microsoft Azure Stack Hub.
For more information, see Microsoft Azure Stack Hub Compute Accounts.

The following permissions are required to add a Microsoft Azure Stack Hub Compute account:

• If you use a new Microsoft Entra ID (formerly Azure Active Directory) application (select the Create a new
a ccount option at the Subscription step of the wizard) when adding a Microsoft Azure Stack Hub Compute
account, the Microsoft Entra ID user account where the Microsoft Entra ID application will be created must
have the following privileges:

a. To register applications. For this, you can assign the Global Administrator privileges to the user or
enable the Users can register applications option for the user in Azure portal. For details, see
Microsoft Azure Docs.

b. To assign a role on the subscription level for the registered application. For this, you can use the
Owner role or if the Owner role cannot be used, you can create a custom role with minimal
permissions. To learn how to create a custom role, see Creating Custom Role for Azure and Azure
Stack Hub Accounts.

• If you use an existing Microsoft Entra ID (formerly Azure Active Directory) application (select the Use the
ex isting account option at the Subscription step of the wizard) when adding a Microsoft Azure Stack Hub
Compute account, the application must have the Contributor role privilege for the selected subscription. If
you restore workloads to Microsoft Azure Stack Hub and cannot use the Contributor role, you can create a
custom role with minimal permissions. To learn how to create a custom role, see Creating Custom Role for
Azure and Azure Stack Hub Accounts.

Adding Microsoft Azure Storage Accounts (Entra ID)


NOTE

This feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

70 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Microsoft Azure storage account with Microsoft Entra ID authorization is required to add Azure Blob storage,
Azure archive storage, and so on. For more information, see Microsoft Azure Storage Accounts (Entra ID).

The following permissions are required to existing Microsoft Azure storage account with Microsoft Entra ID
authorization:

• If you use a new Microsoft Entra ID (formerly Azure Active Directory) application (select the Create a new
a ccount option at the Subscription step of the wizard) when adding a Microsoft Azure Stack Hub Compute
account, the Microsoft Entra ID user account where the Microsoft Entra ID application will be created must
have the following privileges:

a. To register applications. For this, you can assign the Global Administrator privileges to the user or
enable the Users can register applications option for the user in Azure portal. For details, see
Microsoft Azure Docs.

b. To assign a role on the subscription level for the registered application. For this, you can use the
Owner role or if the Owner role cannot be used, you can create a custom role with minimal
permissions. To learn how to create a custom role, see Creating Custom Role for Azure and Azure
Stack Hub Accounts.

• If you use an existing Microsoft Entra ID (formerly Azure Active Directory) application (select the Use the
ex isting account option at the Account Type step of the wizard), the application must have the following
role privileges for the selected storage account:

o Storage Account Contributor

o Storage Blob Data Contributor

o Storage Blob Data Owner

For more information, see Microsoft Docs.

Using Object Storage Repositories


Amazon S3 Object Storage Permissions
Consider the following:

• Make sure the account you are using has access to Amazon buckets and folders.

• The ListAllMyBuckets permission is not required if you specify the bucket name explicitly at the
Buck et step of the New Object Repository wizard.

Permissions for Amazon S3 Object Storage depend on whether you use immutability and helper appliance
settings.

NOTE

S3 compatible object storage repositories use the same permissions as Amazon S3 Object Storage with the
following exclusion: since you cannot setup helper appliance in the cloud, so you don't need permissions
for it. Therefore, S3 compatible object storage repositories requires permissions which start with s3, for
example, "s3:ListBucket". Permissions that start with ec2 can be skipped, for example,
"ec2:DescribeInstances".

71 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


1. Immutability Disabled and Helper Appliance not Used

The following permissions are required to use Amazon S3 object storage with immutability disabled. A helper
appliance is not used for health check operations.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration"
],
"Resource": "*"
}
]
}

72 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


2. Immutability Disabled and New Helper Appliance Configured

The following permissions are required to use Amazon S3 object storage with immutability disabled. For health
check operations a new helper appliance is configured and the Amazon VPC, subnet and security group settings
are set to (Create new) for the helper appliance settings.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs",
"ec2:CreateVpc",
"ec2:CreateSubnet",
"ec2:DescribeAvailabilityZones",
"ec2:CreateRoute",
"ec2:CreateInternetGateway",
"ec2:AttachInternetGateway",
"ec2:ModifyVpcAttribute",
"ec2:CreateSecurityGroup",
"ec2:DeleteSecurityGroup",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:DescribeRouteTables",
"ec2:DescribeInstanceTypes"
],
"Resource": "*"
}
]
}

73 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


3. Immutability Disabled and Helper Appliance Configured Beforehand

The following permissions are required to use Amazon S3 object storage with immutability disabled. Amazon
VPC, subnet and security group settings for a helper appliance are configured beforehand.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs"
],
"Resource": "*"
}
]
}

74 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


4. Immutability Enabled and Helper Appliance not Used

The following permissions are required to use Amazon S3 object storage with immutability enabled. A helper
appliance is not used for health check operations.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration",
"s3:ListBucketVersions",
"s3:GetObjectVersion",
"s3:GetObjectRetention",
"s3:GetObjectLegalHold",
"s3:PutObjectRetention",
"s3:PutObjectLegalHold",
"s3:DeleteObjectVersion"
],
"Resource": "*"
}
]
}

75 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


5. Immutability Enabled and New Helper Appliance Configured

The following permissions are required to use Amazon S3 object storage with immutability enabled. For health
check operations a new helper appliance is configured and the Amazon VPC, subnet and security group settings
are set to (Create new) for the helper appliance settings.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration",
"s3:ListBucketVersions",
"s3:GetObjectVersion",
"s3:GetObjectRetention",
"s3:GetObjectLegalHold",
"s3:PutObjectRetention",
"s3:PutObjectLegalHold",
"s3:DeleteObjectVersion",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs",
"ec2:CreateVpc",
"ec2:CreateSubnet",
"ec2:DescribeAvailabilityZones",
"ec2:CreateRoute",
"ec2:CreateInternetGateway",
"ec2:AttachInternetGateway",
"ec2:ModifyVpcAttribute",
"ec2:CreateSecurityGroup",
"ec2:DeleteSecurityGroup",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:DescribeRouteTables",
"ec2:DescribeInstanceTypes"
],
"Resource": "*"
}
]
}

76 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


6. Immutability Enabled and Helper Appliance Configured Beforehand

The following permissions are required to use Amazon S3 object storage with immutability enabled. Amazon
VPC, subnet and security group settings for a helper appliance are configured beforehand.

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListAllMyBuckets",
"s3:GetBucketVersioning",
"s3:GetBucketObjectLockConfiguration",
"s3:ListBucketVersions",
"s3:GetObjectVersion",
"s3:GetObjectRetention",
"s3:GetObjectLegalHold",
"s3:PutObjectRetention",
"s3:PutObjectLegalHold",
"s3:DeleteObjectVersion",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs"
],
"Resource": "*"
}
]
}

For more information on permissions, see AWS Documentation.

Amazon S3 Glacier Storage Permissions


Permissions for Amazon S3 Glacier depend on whether you use immutability and the archiver appliance settings:

77 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


1. Immutability Disabled and Archiver Appliance not Configured

The following permissions are required for Amazon S3 Glacier storage with immutability disabled. VPC, subnet
and security group settings set to are set to (Create new) for the archiver appliance settings.

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:DeleteObject",
"s3:PutObject",
"s3:GetObject",
"s3:RestoreObject",
"s3:ListBucket",
"s3:AbortMultipartUpload",
"s3:GetBucketVersioning",
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:GetBucketObjectLockConfiguration",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs",
"ec2:CreateVpc",
"ec2:CreateSubnet",
"ec2:DescribeAvailabilityZones",
"ec2:CreateRoute",
"ec2:CreateInternetGateway",
"ec2:AttachInternetGateway",
"ec2:ModifyVpcAttribute",
"ec2:CreateSecurityGroup",
"ec2:DeleteSecurityGroup",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:DescribeRouteTables",
"ec2:DescribeInstanceTypes"
],
"Resource": "*"
}
]
}

78 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


2. Immutability Disabled and Archiver Appliance Configured Beforehand

These permissions apply for Amazon S3 Glacier storage with immutability disabled. Amazon VPC, subnet and
security group settings for an archiver appliance are configured beforehand.

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:DeleteObject",
"s3:PutObject",
"s3:GetObject",
"s3:RestoreObject",
"s3:ListBucket",
"s3:AbortMultipartUpload",
"s3:GetBucketVersioning",
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:GetBucketObjectLockConfiguration",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs"
],
"Resource": "*"
}
]
}

79 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


3. Immutability Enabled and Archiver Appliance not Configured

The following permissions are required for Amazon S3 Glacier storage with immutability enabled. VPC, subnet
and security group settings set to are set to (Create new) for the archiver appliance settings.

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:DeleteObject",
"s3:PutObject",
"s3:GetObject",
"s3:RestoreObject",
"s3:ListBucket",
"s3:AbortMultipartUpload",
"s3:GetBucketVersioning",
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:GetBucketObjectLockConfiguration",
"s3:PutObjectRetention",
"s3:GetObjectVersion",
"s3:PutObjectLegalHold",
"s3:GetObjectRetention",
"s3:DeleteObjectVersion",
"s3:ListBucketVersions",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs",
"ec2:CreateVpc",
"ec2:CreateSubnet",
"ec2:DescribeAvailabilityZones",
"ec2:CreateRoute",
"ec2:CreateInternetGateway",
"ec2:AttachInternetGateway",
"ec2:ModifyVpcAttribute",
"ec2:CreateSecurityGroup",
"ec2:DeleteSecurityGroup",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:DescribeRouteTables",
"ec2:DescribeInstanceTypes"
],
"Resource": "*"
}
]
}

80 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


4. Immutability Enabled and Archiver Appliance Configured Beforehand

These permissions apply for Amazon S3 Glacier storage with immutability enabled. Amazon VPC, subnet and
security group settings for an archiver appliance are configured beforehand.

{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"s3:DeleteObject",
"s3:PutObject",
"s3:GetObject",
"s3:RestoreObject",
"s3:ListBucket",
"s3:AbortMultipartUpload",
"s3:GetBucketVersioning",
"s3:ListAllMyBuckets",
"s3:GetBucketLocation",
"s3:GetBucketObjectLockConfiguration",
"s3:PutObjectRetention",
"s3:GetObjectVersion",
"s3:PutObjectLegalHold",
"s3:GetObjectRetention",
"s3:DeleteObjectVersion",
"s3:ListBucketVersions",
"ec2:DescribeInstances",
"ec2:CreateKeyPair",
"ec2:DescribeKeyPairs",
"ec2:RunInstances",
"ec2:DeleteKeyPair",
"ec2:DescribeVpcAttribute",
"ec2:CreateTags",
"ec2:DescribeSubnets",
"ec2:TerminateInstances",
"ec2:DescribeSecurityGroups",
"ec2:DescribeImages",
"ec2:DescribeVpcs"
],
"Resource": "*"
}
]
}

Azure Archive Object Storage Permissions


The following permissions are required to use Azure Archive object storage.

81 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


{
"properties": {
"roleName": "CUSTOM_ROLE_MINIMAL_PERMISSIONS",
"description": "CUSTOM_ROLE_MINIMAL_PERMISSIONS",
"assignableScopes": [
"/subscriptions/111111-1111-1111-0000-00000000000"
],
"permissions": [
{
"actions": [
"Microsoft.Authorization/*/read",
"Microsoft.Compute/locations/*",
"Microsoft.Compute/virtualMachines/*",
"Microsoft.Network/locations/*",
"Microsoft.Network/networkInterfaces/*",
"Microsoft.Network/networkSecurityGroups/join/action",
"Microsoft.Network/networkSecurityGroups/read",
"Microsoft.Network/networkSecurityGroups/write",
"Microsoft.Network/networkSecurityGroups/delete",
"Microsoft.Network/publicIPAddresses/join/action",
"Microsoft.Network/publicIPAddresses/read",
"Microsoft.Network/publicIPAddresses/write",
"Microsoft.Network/publicIPAddresses/delete",
"Microsoft.Network/virtualNetworks/read",
"Microsoft.Network/virtualNetworks/write",
"Microsoft.Network/virtualNetworks/subnets/join/action",
"Microsoft.Storage/storageAccounts/listKeys/action",
"Microsoft.Storage/storageAccounts/read",
"Microsoft.Resources/deployments/*",
"Microsoft.Resources/subscriptions/resourceGroups/read",
"Microsoft.Resources/checkResourceName/action",
"Microsoft.Resources/subscriptions/resourceGroups/write",
"Microsoft.Resources/subscriptions/locations/read"
],
"notActions": [],
"dataActions": [],
"notDataActions": []
}
]
}
}

Google Cloud Object Storage Permissions


Consider the following:

• The storage.buckets.list permission is not required if you specify the bucket name explicitly at the
Buck et step of the New Object Repository wizard.

• The Owner IAM role does not necessarily grant the permissions required for working with Google Cloud
Storage.

The following permissions are required to use Google Cloud object storage.

{
"storage.buckets.get",
"storage.buckets.list",

82 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


"storage.objects.create",
"storage.objects.delete",
"storage.objects.get",
"storage.objects.list"
}

NetApp Data ONTAP/Lenovo Thinksystem DM Permissions


The account used to connect to a NetApp Data ONTAP/Lenovo Thinksystem DM storage system must have the
following permissions:

7-Mode

• login-http-admin

• api-system-*

• api-license-* (api-license-list-info)

• api-volume-*

• api-net-*

• api-options-*

• api-vfiler-*

• api-qtree-*

• api-nfs-*

• api-snapshot-*

• api-lun-*

• api-iscsi-*

• api-feature-*

• api-registry-*

• api-fcp-*

• api-file-*

• api-igroup-*

• api-clone-*

• api-snapvault-*

• api-snapmirror-*

• api-cf-*

• cli-options

• security-api-vfiler

83 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


CDOT (VMware Integration)

Command/Directory Access/Query Level

DEFAULT readonly

cluster readonly

metrocluster readonly

fcp readonly

file readonly

igroup all

iscsi all

network readonly

node readonly

security readonly

security login readonly

set readonly

snapmirror all

system readonly

version readonly

qtree readonly

lun all

nfs all

84 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Command/Directory Access/Query Level

snapshot all

volume all

vserver all

Only as SVM (VMware Integration)

Command/Directory Access/Query Level

DEFAULT none

lun all

lun igroup all

network readonly

security readonly

security login readonly

snapmirror all

system readonly

version readonly

volume all

volume file readonly

volume qtree all

volume snapshot all

85 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Command/Directory Access/Query Level

vserver all

vserver fcp all

vserver iscsi all

vserver nfs all

CDOT (NAS Backup Integration)

Command/Directory Access/Query Level

DEFAULT readonly

security readonly

security login readonly

volume snapshot all

vserver all

vserver nfs all

Only as SVM (NAS Backup Integration)

Command/Directory Access/Query Level

DEFAULT none

lun readonly

network readonly

security readonly

86 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Command/Directory Access/Query Level

security login readonly

snapmirror readonly

version readonly

volume readonly

volume snapshot all

vserver all

CDOT (Veeam Agent Integration)

Command/Directory Access/Query Level

cluster readonly

lun all

metrocluster readonly

network readonly

system license readonly

system node readonly

version readonly

volume all

volume snapshot all

vserver all

87 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Only as SVM (Veeam Agent Integration)

Command/Directory Access/Query Level

lun all

network readonly

version readonly

volume all

volume snapshot all

vserver all

Universal Storage API Integrated Systems Permissions


The account used to connect to a Universal Storage API integrated system must be assigned a necessary role in
the storage system console and have a set of necessary permissions.

• For Dell PowerMax, the account must be assigned the Storage Administrator role.

• For Fujitsu ETERNUS, the account must be assigned the Software role.

• For NetApp SolidFire/HCI, the account must have the following permissions:

o Volumes

o Cluster Admins

• For Western Digital IntelliFlash, the account must be assigned the Veeam Admin Role.

• For DataCore, the account must have the following permissions:

o General

o Port

o Host

o Virtual disk

o Snapshot

o Physical disk

• For Hitachi VSP, the account must be assigned the following roles:

o Storage Administrator (View Only)

o Storage Administrator (Provisioning)

88 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


o Storage Administrator (Local Copy)

• For HPE XP, the account must be assigned the following roles:

o Storage Administrator (View Only)

o Storage Administrator (Provisioning)

o Storage Administrator (Local Copy)

• For Dell PowerStore, the account must be assigned one of the following roles:

o Administrator

o Storage Administrator

o Storage Operator

• For NEC Storage M Series, the account must be assigned the Administrator role.

• For NEC Storage V Series, the account must be assigned the following roles:

o Storage Administrator (View Only)

o Storage Administrator (Provisioning)

o Storage Administrator (Local Copy)

For privileges required to integrate the unstructured data backup feature with Dell PowerScale (formerly Isilon),
see Integration with Dell PowerScale in the Unstructured Data Backup section.

For storage systems not mentioned above, the account must have Administrator role.

Adding Object Storage Repositories as Unstructured Data


Source
Amazon S3 and S3 Compatible Object Storage
The account that you use to add Amazon S3 and S3 Compatible object storage as unstructured sources and back
up data from them must be able to perform the following actions:

GetBucketAccelerateConfiguration
GetBucketAcl
ListBucketAnalyticsConfigurations
GetBucketAnalyticsConfiguration
GetBucketCors
GetBucketEncryption
GetBucketIntelligentTieringConfiguration
ListBucketIntelligentTieringConfigurations
GetBucketInventoryConfiguration
ListBucketInventoryConfigurations
GetBucketLifecycleConfiguration
GetBucketLogging
GetBucketMetricsConfiguration
ListBucketMetricsConfigurations
GetBucketNotificationConfiguration
GetBucketOwnershipControls
GetBucketPolicy

89 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


GetPublicAccessBlock
GetBucketReplication
GetBucketRequestPayment
GetBucketTagging
GetBucketVersioning
GetBucketWebsite
GetObjectLockConfiguration

90 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


Ports
On backup infrastructure components, Veeam Backup & Replication automatically creates firewall rules for the
required ports. These rules allow components to communicate with each other.

IMP ORTANT

Some Linux distributions require firewall and security rules to be created manually. For details, see this
Veeam KB article.

You can find the full list of the ports below.

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

From To P rotocol P ort Notes

Communication with Virtualization Servers

Backup SCVMM TCP 8100 Default port used to communicate


server with the VMM server through WCF.

Microsoft Hyper-V server TCP 445 Required for deploying


135 Veeam Backup & Replication
components.

TCP 6160 Default port used by Veeam Installer


Service.

TCP 6162 Default port used by Veeam Data


Mover Service.

TCP 6163 Default port used to communicate


with Veeam Hyper-V Integration
Service.

91 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

TCP 2500 to Default range of ports used as


3300 transmission channels for jobs. For
every TCP connection that a job uses,
one port from this range is assigned.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication starting
from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB
article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule
for the runtime process. If you use
firewall settings other than default
ones or application-aware processing
fails with the "RPC function call
failed" error, you need to configure
dynamic RPC ports. For more
information on how to configure RPC
dynamic port allocation to work with
firewalls, see this Microsoft KB article.

SCVMM Backup server TCP 8732 Port used by Veeam PowerShell


Manager to establish communication
between Veeam Backup & Replication
components and the VMM server.

Other Communications

Backup PostgreSQL server hosting TCP 5432 Port used for communication with
server the PostgreSQL server on which the
Veeam Backup & Replication Veeam Backup & Replication
configuration database configuration database is deployed.

92 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

Microsoft SQL Server TCP 1433 Port used for communication with
hosting the Microsoft SQL Server on which the
Veeam Backup & Replication Veeam Backup & Replication
configuration database configuration database is deployed (if
you use a Microsoft SQL Server
default instance).

Additional ports may need to be open


depending on your configuration. For
more information, see Microsoft Docs.

DNS server with UDP 53 Port used for communication with the
forward/reverse name DNS Server.
resolution of all backup
servers

Veeam Update Notification TCP 443 Default port used to download


Server (dev.veeam.com) information about available updates
from the Veeam Update Notification
Server over the Internet.

Veeam License Update TCP 443 Default port used for license auto-
Server update.
(vbr.butler.veeam.com,
autolk.veeam.com)

KMS server TCP 5696 Default port used for communication


with Key Management System server.

Microsoft SMB3 server TCP 6160 Default port used by Veeam Installer
Service.

TCP 6162 Default port used by Veeam Data


Mover Service.

TCP 6163 Default port used by the Hyper-V


Integration Service.

Backup server TCP 9501 Port used locally on the backup server
for communication between Veeam
Broker Service and Veeam services
and components.

Backup server TCP 6172 Port used to provide REST access to


the Veeam Backup & Replication
database.

93 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

Management Backup server TCP 3389 Default port used by the Remote
client PC Desktop Services. If you use third-
(remote party solutions to connect to the
access) backup server, other ports may need
to be open.

REST client Backup server TCP 9419 Default port for communication with
REST API service.

Backup & Replication Console


The following table describes network ports that must be opened to ensure proper communication with the
Veeam Backup & Replication console.

From To P rotocol P ort Notes

Veeam Backup & Replication Backup TCP 9392 Ports used by the
console server 9420 Veeam Backup & Replication console
to communicate with the backup
server.

Port 9420 is required starting from


Veeam Backup & Replication 12.1
(build 12.1.0.2131).

TCP 9396 [Remote console only] Port used by


the Veeam.Backup.UIService process
for managing database connections.

TCP 10003 [Remote console only] Port used by


the Veeam Backup & Replication
console to connect to the backup
server only when managing the
Veeam Cloud Connect infrastructure.

94 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

Mount TCP 2500 to [Remote console only] Default range


server 3300 of ports used as data transmission
channels. For every TCP connection
that a job uses, one port from this
range is assigned.

This port is used if the mount server is


not located on the console.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication starting
from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup Proxy
The following table describes network ports that must be opened to ensure proper communication of backup
proxies with other backup components. For more information about ports that must be opened between the
backup proxy and specific backup repository, see Backup Repositories.

From To P rotocol P ort Notes

Communication with Backup Server

Backup server Hyper-V TCP 445 Required for deploying


server/Off-host 135 Veeam Backup & Replication
backup proxy components.

TCP 6160 Default port used by Veeam


Installer Service.

TCP 6162 Default port used by Veeam


Data Mover Service.

TCP 6163 Default port used by the


Hyper-V Integration Service.

95 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

TCP 49152 to 65535 Dynamic RPC port range for


Microsoft Windows 2008
and later. For more
information, see this
Microsoft KB article.

Note: If you use default


Microsoft Windows firewall
settings, you do not need to
configure dynamic RPC
ports. During setup,
Veeam Backup & Replication
automatically creates a
firewall rule for the runtime
process. If you use firewall
settings other than default
ones or application-aware
processing fails with the
"RPC function call failed"
error, you need to configure
dynamic RPC ports. For
more information on how to
configure RPC dynamic port
allocation to work with
firewalls, see this Microsoft
KB article.

Off-host file TCP 6210 Default port used by the


proxy Veeam Backup VSS
Integration Service for
taking a VSS snapshot
during the SMB file share
backup.

Other Communications

96 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

Hyper-V Gateway server TCP 2500 to 3300 Default range of ports used
server/Off-host as transmission channels.
backup proxy For every TCP connection
that a job uses, one port
from this range is assigned.

Note: This range of ports


applies to newly installed
Veeam Backup & Replication
starting from version 10.0,
without upgrade from
previous versions. If you
have upgraded from an
earlier version of the
product, the range of ports
from 2500 to 5000 applies
to the already added
components.

Hyper-V server TCP 2500 to 3300 Default range of ports used


as transmission channels for
replication jobs. For every
TCP connection that a job
uses, one port from this
range is assigned.

Note: This range of ports


applies to newly installed
Veeam Backup & Replication
starting from version 10.0,
without upgrade from
previous versions. If you
have upgraded from an
earlier version of the
product, the range of ports
from 2500 to 5000 applies
to the already added
components.

97 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

Microsoft SMB3 Hyper-V TCP 2500 to 3300 Ports used to retrieve CBT
server server/Off-host information from a
backup proxy Microsoft SMB3 server
managing shares that host
VM disks.

Note: This range of ports


applies to newly installed
Veeam Backup & Replication
starting from version 10.0,
without upgrade from
previous versions. If you
have upgraded from an
earlier version of the
product, the range of ports
from 2500 to 5000 applies
to the already added
components.

Gateway Server
The following table describes network ports that must be opened to ensure proper communication with
gateway servers. For more information about ports that must be opened between the gateway server and
specific backup repository, see Backup Repositories.

From To P rotocol P ort Notes

Backup server Gateway TCP 445 Required for deploying


server 135 Veeam Backup & Replication components.
(Microsoft
Windows)
TCP 6160 Default port used by Veeam Installer
Service.

TCP 6162 Default port used by Veeam Data Mover


Service.

Gateway TCP 22 Default SSH port used as a control


server (Linux) channel.

TCP 6160 Default port used by Veeam Installer


Service for Linux.

98 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


From To P rotocol P ort Notes

TCP 6162 Default port used by Veeam Data Mover


Service.

You can specify a different port while


adding the Linux server to the
Veeam Backup & Replication
infrastructure. Note that you can specify a
different port only if there is no
previously installed Veeam Data Mover on
this Linux server. For more information,
see Specify Credentials and SSH Settings.

Gateway TCP 2500 to Default range of ports used as


server 3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Hyper-V Gateway TCP 2500 to Default range of ports used as


server/ Off- server 3300 transmission channels. For every TCP
host backup connection that a job uses, one port from
proxy this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup Repositories
• Microsoft Windows/Linux-based Backup Repository

• NFS Backup Repository

• SMB Backup Repository

• Dell Data Domain System

• ExaGrid

99 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V


• HPE StoreOnce

• Quantum DXi

• Fujitsu ETERNUS CS800

• Infinidat InfiniGuard

• Object Storage Repository

• External Repository

• Archive Object Storage Repository

Microsoft Windows/Linux-based Backup Repository


The following table describes network ports that must be opened to ensure proper communication with
Microsoft Windows/Linux-based backup repositories.

From To P rotocol P ort Notes

Backup server Backup TCP 445 Required for deploying


repository 135 Veeam Backup & Replication components.
(Microsoft
Windows)
TCP 6160 Default port used by Veeam Installer
Service.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

TCP 22 Default SSH port used as a control


channel.

100 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Backup TCP 6160 Default port used by Veeam Installer


repository Service for Linux.
(Linux)
Also used by Veeam Data Mover Service
for communication between the backup
server and the hardened repository.

TCP 6162 Default port used by Veeam Data Mover


Service except for communication
between the backup server and the
hardened repository.

You can specify a different port while


adding the Linux server to the
Veeam Backup & Replication
infrastructure. Note that you can specify a
different port only if there is no
previously installed Veeam Data Mover on
this Linux server. For more information,
see Specify Credentials and SSH Settings.

TCP 2500 to Default range of ports used as


3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

101 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Backup Backup server TCP 2500 to Default range of ports used as


repository 3300 transmission channels for copy backup
(Linux) operations if the backup server is used as
the target backup repository. These ports
are also required for file copy operations
between the Linux backup repository and
the backup server.

For every TCP connection that a job uses,


one port from this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Hyper-V Backup TCP 2500 to Default range of ports used as


server/ Off- repository 3300 transmission channels for replication jobs.
host backup For every TCP connection that a job uses,
proxy one port from this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Source Target TCP 2500 to Default range of ports used as


backup backup 3300 transmission channels for backup copy
repository repository jobs and copy backup operations. For
every TCP connection that a job uses, one
port from this range is assigned.

If the backup copy job utilizes WAN


accelerators, make sure that ports specific
for WAN accelerators are opened.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

102 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NFS Backup Repository
The following table describes network ports that must be opened to ensure proper communication with NFS
shares added as backup repositories.

From To P rotocol P ort Notes

Gateway NFS backup TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
server or repository the port mapper service.
backup proxy
Also used as a transmission channel from
the gateway server to the target NFS
backup repository if a gateway server is
specified explicitly in NFS backup
repository settings.

Gateway NFS backup TCP, UDP mountd_port Dynamic port used for mountd service.
server or repository Can be assigned statically.
backup proxy (NFS v3)

TCP, UDP statd_port Dynamic port used for statd service. Can
be assigned statically.

TCP, UDP lockd_port Dynamic port used for lockd service. Can
be assigned statically.

SMB Backup Repository


The following table describes network ports that must be opened to ensure proper communication with SMB
(CIFS) shares added as backup repositories.

From To P rotocol P ort Notes

Gateway SMB (CIFS) TCP 445 Used as a transmission channel from the
server or backup gateway server to the target SMB (CIFS)
backup proxy repository backup repository if a gateway server is
(Microsoft specified explicitly in SMB (CIFS) backup
Windows) repository settings.

Dell Data Domain System


For more information, see Dell Documents.

From To P rotocol P ort Notes

Backup server Dell Data TCP 111 Port used to assign a random port for the
or gateway Domain mountd service used by NFS and
server DDBOOST. Mountd service port can be
statically assigned.

103 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 2049 Main port used by NFS. Can be modified


using the ‘nfs set server-port’ command.
Command requires SE mode.

TCP 2052 Main port used by NFS MOUNTD. Can be


modified using the 'nfs set mountd-port'
command in SE mode.

ExaGrid

From To P rotocol P ort Notes

Backup server ExaGrid TCP 22 Default command port used for


communication with ExaGrid.

Backup proxy ExaGrid TCP 2500 to 3300 Default range of ports used for
communication with the backup
proxy.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If
you have upgraded from an earlier
version of the product, the range
of ports from 2500 to 5000
applies to the already added
components.

HPE StoreOnce

From To P rotocol P ort Notes

Backup server HPE TCP 9387 Default command port used for
or StoreOnce communication with HPE StoreOnce.
gateway
server
9388 Default data port used for communication
with HPE StoreOnce.

104 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Quantum DXi

From To P rotocol P ort Notes

Backup server Quantum DXi TCP 22 Default command port used for
communication with Quantum DXi.

Backup proxy Quantum DXi TCP 2500 to 3300 Default range of ports used for
communication with the backup
proxy.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If
you have upgraded from an earlier
version of the product, the range
of ports from 2500 to 5000
applies to the already added
components.

Fujitsu ETERNUS CS800

From To P rotocol P ort Notes

Backup server Fujitsu TCP 22 Default command port used for


ETERNUS communication with Fujitsu
CS800 ETERNUS CS800.

Backup proxy Fujitsu TCP 2500 to 3300 Default range of ports used for
ETERNUS communication with the backup
CS800 proxy.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If
you have upgraded from an earlier
version of the product, the range
of ports from 2500 to 5000
applies to the already added
components.

105 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Infinidat InfiniGuard

From To P rotocol P ort Notes

Backup server Infinidat TCP 22 Default command port used for


InfiniGuard communication with Infinidat
InfiniGuard.

Backup proxy Infinidat TCP 2500 to 3300 Default range of ports used for
InfiniGuard communication with the backup
proxy.

Note: This range of ports applies to


newly installed
Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If
you have upgraded from an earlier
version of the product, the range
of ports from 2500 to 5000
applies to the already added
components.

Object Storage Repository


The following table describes network ports and endpoints that must be opened to ensure proper
communication with object storage repositories. For more information, see Object Storage Repository.

From To P rotoc P ort Notes


ol

Source object Backup proxy TCP 2500 to Default range of ports used as
storage repository (direct 3300 transmission channels. For every TCP
connection)/Gate connection that a job uses, one port from
way server or this range is assigned.
backup server
Note: This range of ports applies to newly
installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from 2500
to 5000 applies to the already added
components.

106 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotoc P ort Notes
ol

Backup proxy Amazon S3 object TCP 443 Used to communicate with the Amazon S3
(direct storage object storage through the following
connection)/Gate endpoints:
way server or
• *.amazonaws.com (for both
backup server
Global and Government regions)
• *.amazonaws.com.cn (for China
region)

All AWS service endpoints are specified in


the AWS documentation.

80 Used to verify the certificate status


through the following endpoints:
• *.amazontrust.com

Consider that certificate verification


endpoints (CRL URLs and OCSP servers)
are subject to change. The actual list of
addresses can be found in the certificate
itself.

Microsoft Azure TCP 443 Used to communicate with the Microsoft


object storage Azure object storage through the
following endpoints:
• xxx.blob.core.windows.net
(for Global region)
•
xxx.blob.core.chinacloudap
i.cn (for China region)
•
xxx.blob.core.usgovcloudap
i.net (for Government region)

Consider that the <xxx> part of the


address must be replaced with your actual
storage account URL that can be found in
the Azure management portal.

107 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotoc P ort Notes
ol

80 Used to verify the certificate status


through the following endpoints:
• ocsp.digicert.com

• ocsp.msocsp.com

Consider that certificate verification


endpoints (CRL URLs and OCSP servers)
are subject to change. The actual list of
addresses can be found in the certificate
itself. For more details, see also this
Microsoft article.

Google Cloud TCP 443 Used to communicate with Google Cloud


storage storage through the following endpoints:
• storage.googleapis.com

All cloud endpoints are specified in this


Google article.

80 Used to verify the certificate status


through the following endpoints:
• ocsp.pki.goog
• pki.goog

• crl.pki.goog

Consider that certificate verification


endpoints (CRL URLs and OCSP servers)
are subject to change. The actual list of
addresses can be found in the certificate
itself.

IBM Cloud object TCP Depends Used to communicate with IBM Cloud
storage on device object storage.
configurati
on

S3 compatible TCP Depends Used to communicate with S3 compatible


object storage on device object storage.
configurati
on

108 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
External Repository
The following table describes network ports and endpoints that must be opened to ensure proper
communication with external repositories. For more information, see External Repository.

From To P rotocol P ort Notes

Source Gateway TCP 2500 to Default range of ports used as transmission


object server or 3300 channels. For every TCP connection that a job
storage backup uses, one port from this range is assigned.
repository server
Note: This range of ports applies to newly
installed Veeam Backup & Replication starting
from version 10.0, without upgrade from previous
versions. If you have upgraded from an earlier
version of the product, the range of ports from
2500 to 5000 applies to the already added
components.

Gateway Amazon S3 TCP 443 Used to communicate with the Amazon S3 object
server or object storage through the following endpoints:
backup storage
• *.amazonaws.com (for both Global and
server
Government regions)
• *.amazonaws.com.cn (for China region)

All AWS service endpoints are specified in the


AWS documentation.

80 Used to verify the certificate status through the


following endpoints:
• *.amazontrust.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself.

109 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Microsoft TCP 443 Used to communicate with the Microsoft Azure


Azure object storage through the following endpoints:
object
• xxx.blob.core.windows.net (for
storage
Global region)
• xxx.blob.core.chinacloudapi.cn
(for China region)
• xxx.blob.core.usgovcloudapi.net
(for Government region)

Consider that the <xxx> part of the address must


be replaced with your actual storage account URL
that can be found in the Azure management
portal.

80 Used to verify the certificate status through the


following endpoints:
• ocsp.digicert.com

• ocsp.msocsp.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself. For more details, see also
this Microsoft article.

Google TCP 443 Used to communicate with Google Cloud storage


Cloud through the following endpoints:
storage
• storage.googleapis.com

All cloud endpoints are specified in this Google


article.

80 Used to verify the certificate status through the


following endpoints:
• ocsp.pki.goog
• pki.goog
• crl.pki.goog

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself.

110 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Archive Object Storage Repository
The following table describes network ports and endpoints that must be opened to ensure proper
communication with object storage repositories used as a part of Archive Tier. For more information, see Archive
Tier.

From To P rotocol P ort Notes

Gateway Amazon TCP 443 Used by default to communicate with the Amazon
server or EC2 helper EC2 helper appliance through public/private IPv4
backup appliance addresses of EC2 appliances.
server
If you use Amazon S3 Glacier object storage, the
gateway server should have direct connection to
AWS service endpoints. HTTP/HTTPS proxy
servers are not supported.

If there is no gateway server selected, the backup


server will be used as a gateway server.

TCP 22 Default SSH port used as a control channel.

Microsoft TCP 443 Used by default to communicate with the


Azure proxy Microsoft Azure helper appliance through
appliance public/private IPv4 addresses of Azure appliances.

If there is no gateway server selected, the backup


server will be used as a gateway server.

TCP 22 Default SSH port used as a control channel.

Amazon Amazon S3 TCP 443 Used to communicate with the Amazon S3 object
EC2 helper object storage through the following endpoints:
appliance storage
• *.amazonaws.com (for both Global and
Government regions)
• *.amazonaws.com.cn (for China region)

All AWS service endpoints are specified in the


AWS documentation

TCP 80 Used to verify the certificate status through the


following endpoints:
• *.amazontrust.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself.

111 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Microsoft Microsoft TCP 443 Used to communicate with the Microsoft Azure
Azure proxy Azure object storage through the following endpoints:
appliance object
• xxx.blob.core.windows.net (for
storage
Global region)
• xxx.blob.core.chinacloudapi.cn
(for China region)
• xxx.blob.core.usgovcloudapi.net
(for Government region)

Consider that the <xxx> part of the address must


be replaced with your actual storage account URL
that can be found in the Azure management
portal.

TCP 80 Used to verify the certificate status through the


following endpoints:
• ocsp.digicert.com

• ocsp.msocsp.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself. For more details, see also
this Microsoft article.

Storage Systems
• Dell VNX(e) Storage

• Dell Unity XT/Unity Storage

• Dell PowerScale (Formerly Isilon) Storage

• HPE 3PAR StoreServ Storage

• HPE Alletra MP/Alletra 9000/Primera Storage

• HPE StoreVirtual/LeftHand/P4000 Series Storage

• HPE Alletra 5000/Alletra 6000/Nimble Storage

• IBM Spectrum Virtualize Storage

• Lenovo ThinkSystem DM Series Storage

• NetApp Data ONTAP Storage

• Nutanix Files Storage

• Universal Storage API Integrated System

112 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Dell VNX(e) Storage

From To P rotocol P ort Notes

Backup server VNX File TCP 22 Default command port used for
communication with Dell VNX File over
SSH.

VNX Block TCP 443 Default port used for communication with
Dell VNX Block/Dell VNXe over HTTPS
VNXe and sending REST API calls.

Backup proxy VNX Block TCP 3260 Default iSCSI target port.

VNXe

VNX File TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
the port mapper service.
VNXe

Dell Unity XT/Unity Storage

From To P rotocol P ort Notes

Backup server Dell Unity TCP 443 Default port used for communication with
XT/Unity Dell Unity XT/Unity over HTTPS and
storage sending REST API calls.
system

Backup proxy Dell Unity TCP 3260 Default iSCSI target port.
XT/Unity
storage
system TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
the port mapper service.

Dell PowerScale (Formerly Isilon) Storage

From To P rotocol P ort Notes

Backup server Dell TCP 8080 Default port used for communication with
PowerScale Dell PowerScale over HTTPS and sending
storage REST API calls.
system

113 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Backup proxy Dell TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
PowerScale the port mapper service.
storage
system
TCP 445 Standard SMB port.

HPE 3PAR StoreServ Storage

From To P rotocol P ort Notes

Backup server HPE 3PAR TCP 8008 Default port used for communication with
StoreServ HPE 3PAR StoreServ over HTTP.
storage
system
TCP 8080 Default port used for communication with
HPE 3PAR StoreServ over HTTPS.

TCP 22 Default command port used for


communication with HPE 3PAR StoreServ
over SSH.

Backup proxy HPE 3PAR TCP 3260 Default iSCSI target port.
StoreServ
storage
system

HPE Alletra MP/Alletra 9000/Primera Storage

From To P rotocol P ort Notes

Backup server HPE Alletra TCP 443 Default port used for communication with
MP/Alletra HPE Alletra MP/Alletra 9000/Primera
9000/Primera over HTTPS.
storage
system
TCP 22 Default command port used for
communication with HPE Alletra
MP/Alletra 9000/Primera over SSH.

Backup proxy HPE Alletra TCP 3260 Default iSCSI target port.
MP/Alletra
9000/Primera
storage
system

114 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
HPE StoreVirtual/LeftHand/P4000 Series Storage

From To P rotocol P ort Notes

Backup HPE TCP 16022 Default command port used for


server StoreVirtual/LeftHand/P4000 communication with HPE
series storage system StoreVirtual/LeftHand/P4000 series.

Backup HPE TCP 3260 Default iSCSI target port.


proxy StoreVirtual/LeftHand/P4000
series storage system

HPE Alletra 5000/Alletra 6000/Nimble Storage

From To P rotocol P ort Notes

Backup server HPE Alletra TCP 5392 Default command port used for
5000/Alletra communication with HPE Alletra
6000/Nimble 5000/Alletra 6000/Nimble.
storage
system

Backup proxy HPE Alletra TCP 3260 Default iSCSI target port.
5000/Alletra
6000/Nimble
storage
system

IBM Spectrum Virtualize Storage

From To P rotocol P ort Notes

Backup server IBM Spectrum TCP 22 Default command port used for
Virtualize communication with IBM Spectrum
storage Virtualize over SSH.
system

Backup proxy IBM Spectrum TCP 3260 Default iSCSI target port.
Virtualize
storage
system

115 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Lenovo ThinkSystem DM Series Storage

From To P rotocol P ort Notes

Backup server Lenovo Think TCP 80 Default command port used for
System DM communication with Lenovo Think System
Series storage DM Series over HTTP.
system

TCP 443 Default command port used for


communication with Lenovo Think System
DM Series over HTTPS.

Backup proxy Lenovo Think TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
System DM the port mapper service.
Series storage
system
TCP 445 Standard SMB port.

TCP 3260 Default iSCSI target port.

NetApp Data ONTAP Storage

From To P rotocol P ort Notes

Backup server NetApp Data TCP 80 Default command port used for
ONTAP communication with NetApp Data ONTAP
storage over HTTP.
system

TCP 443 Default command port used for


communication with NetApp Data ONTAP
over HTTPS.

Backup proxy NetApp Data TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
ONTAP the port mapper service.
storage
system
TCP 445 Standard SMB port.

TCP 3260 Default iSCSI target port.

116 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Nutanix Files Storage

From To P rotocol P ort Notes

Backup server Nutanix Files TCP 9440 Default port used for communication with
storage Nutanix Files and sending REST API calls.
system

Backup proxy Nutanix Files TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
storage the port mapper service.
system

TCP 445 Standard SMB port.

Universal Storage API Integrated System


The following tables describe network ports that must be opened to ensure proper communication with
Universal Storage API integrated systems:

• DataCore SANsymphony

• Dell SC Series

• Dell PowerMax

• Dell PowerStore

• Fujitsu ETERNUS DX/AF

• INFINIDAT InfiniBox

• NetApp SolidFire/HCI

• Pure Storage FlashArray

• Tintri IntelliFlash/Western Digital/Tegile

DataCore SANsymphony

From To P rotocol P ort Notes

Backup server DataCore TCP 443 Default command port used for
SANsymphony communication with DataCore
storage SANsymphony over HTTPS.
system

Backup proxy DataCore TCP 3260 Default iSCSI target port.


SANsymphony
storage
system

117 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Dell SC Series

From To P rotocol P ort Notes

Backup server Dell SC Series TCP 3033 Default command port used for
storage communication with Dell SC Series over
system HTTPS.

Backup proxy Dell SC Series TCP 3260 Default iSCSI target port.
storage
system

Dell PowerMax

From To P rotocol P ort Notes

Backup server Dell TCP 8443 Default command port used for
PowerMax communication with Dell PowerMax over
storage HTTPS.
system

Backup proxy Dell TCP 3260 Default iSCSI target port.


PowerMax
storage
system

Dell PowerStore

From To P rotocol P ort Notes

Backup server Dell TCP 443 Default command port used for
PowerStore communication with Dell PowerStore over
storage HTTPS.
system

Backup proxy Dell TCP 3260 Default iSCSI target port.


PowerStore
storage
system

118 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Fujitsu ETERNUS DX/AF

From To P rotocol P ort Notes

Backup server Fujitsu TCP 22 Default command port used for


ETERNUS communication with Fujitsu ETERNUS
DX/AF DX/AF over SSH.
storage
system

Backup proxy Fujitsu TCP 3260 Default iSCSI target port.


ETERNUS
DX/AF
storage
system

INFINIDAT InfiniBox

From To P rotocol P ort Notes

Backup server INFINIDAT TCP 443 Default command port used for
InfiniBox communication with INFINIDAT InfiniBox
storage over HTTPS.
system

Backup proxy INFINIDAT TCP 3260 Default iSCSI target port.


InfiniBox
storage
system

NetApp SolidFire/HCI

From To P rotocol P ort Notes

Backup server NetApp TCP 443 Default command port used for
SolidFire/HCI communication with NetApp
storage SolidFire/HCI over HTTPS.
system

Backup proxy NetApp TCP 3260 Default iSCSI target port.


SolidFire/HCI
storage
system

119 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Pure Storage FlashArray

From To P rotocol P ort Notes

Backup server Pure Storage TCP 443 Default command port used for
FlashArray communication with Pure Storage
system FlashArray over HTTPS.

Backup proxy Pure Storage TCP 3260 Default iSCSI target port.
FlashArray
system

Tintri IntelliFlash/Western Digital/Tegile

From To P rotocol P ort Notes

Backup server Tintri TCP 443 Default command port used for
IntelliFlash communication with Tintri IntelliFlash
system over HTTPS.

Backup proxy Tintri TCP 3260 Default iSCSI target port.


IntelliFlash
system

Tintri TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
IntelliFlash the port mapper service.
system

Unstructured Data Backup Components


The following tables describe network ports that must be opened to ensure proper communication between
unstructured data backup components.

• File Share Connections

• Cache Repository Connections

• Archive Repository Connections

120 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
File Share Connections

From To P rotocol P ort Notes

Backup File server TCP 2500 to Default range of ports used as transmission
proxy 3300 channels. For every TCP connection that a job
uses, one port from this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication starting
from version 10.0, without upgrade from previous
versions. If you have upgraded from an earlier
version of the product, the range of ports from
2500 to 5000 applies to the already added
components.

NAS filer TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by the port
(NetApp mapper service.
Data ONTAP
or Lenovo
ThinkSystem TCP 445 Standard SMB port.
DM Series
storage
TCP 3260 Default iSCSI target port.
system)

NAS filer TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by the port
(Dell mapper service.
PowerScale
(formerly
Isilon) or TCP 445 Standard SMB port.
Nutanix
Files storage
system)

Backup NFS share TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by the port
proxy or mapper service.
tape
server
SMB share TCP 445 Standard SMB port.

Amazon S3 TCP 443 Used to communicate with the Amazon S3 object


object storage through the following endpoints:
storage
• *.amazonaws.com (for both Global and
Government regions)
• *.amazonaws.com.cn (for China region)

All AWS service endpoints are specified in the


AWS documentation.

121 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 80 Used to verify the certificate status through the


following endpoints:
• *.amazontrust.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself.

Microsoft TCP 443 Used to communicate with the Microsoft Azure


Azure object object storage through the following endpoints:
storage
• xxx.blob.core.windows.net (for
Global region)
• xxx.blob.core.chinacloudapi.cn
(for China region)
• xxx.blob.core.usgovcloudapi.net
(for Government region)

Consider that the <xxx> part of the address must


be replaced with your actual storage account URL
that can be found in the Azure management
portal.

TCP 80 Used to verify the certificate status through the


following endpoints:
• ocsp.digicert.com

• ocsp.msocsp.com

Consider that certificate verification endpoints


(CRL URLs and OCSP servers) are subject to
change. The actual list of addresses can be found
in the certificate itself. For more details, see also
this Microsoft article.

S3 TCP Depends on Used to communicate with S3 compatible object


compatible device storage.
object configuration
storage

122 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cache Repository Connections

From To P rotocol P ort Notes

Backup proxy Cache TCP 2500 to Default range of ports used as


repository 3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Cache Backup proxy TCP 2500 to Default range of ports used as


repository 3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Primary or TCP 2500 to Default range of ports used as


secondary 3300 transmission channels for file share
backup backup restore jobs. For every TCP
repository connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

123 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Archive Repository Connections

From To P rotocol P ort Notes

Primary Archive TCP 2500 to Default range of ports used as


backup repository 3300 transmission channels. For every TCP
repository connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Tape Server
The following table describes network ports that must be opened to ensure proper communication with tape
servers.

From To P rotocol P ort Notes

Backup server Tape server TCP 445 Required for deploying


135 Veeam Backup & Replication components.

TCP 2500 to Default range of ports used as data


3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

TCP 6160 Default port used by Veeam Installer


Service.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 6166 Controlling port for RPC calls.

124 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

Tape server Backup server TCP 2500 to Default range of ports used as data
3300 transmission channels. For every TCP
connection that a job uses, one port from
this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup TCP 2500 to Default range of ports used as data


repository or 3300 transmission channels. For every TCP
gateway connection that a job uses, one port from
server this range is assigned.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

NFS share TCP, UDP 111, 2049 Standard NFS ports. Port 111 is used by
the port mapper service.

125 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

SMB share TCP 445 Standard SMB port.

WAN Accelerator
The following table describes network ports that must be opened to ensure proper communication between
WAN accelerators used in backup copy jobs and replication jobs.

From To P rotocol P ort Notes

Backup server WAN TCP 445 Required for deploying


accelerator 135 Veeam Backup & Replication components.
(source and
target)
TCP 6160 Default port used by Veeam Installer
Service.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 6164 Controlling port for RPC calls.

TCP 6220 Port used for traffic control (throttling)


for tenants that use WAN accelerators.

This port is required only in the Veeam


Cloud Connect infrastructure.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

126 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

WAN Backup TCP 2500 to Default range of ports used as data


accelerator repository 3300 transmission channels. For every TCP
(source and (source and connection that a job uses, one port from
target) target) this range is selected dynamically.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

WAN WAN TCP 6164 Controlling port for RPC calls.


accelerator accelerator

TCP 6165 Default port used for data transfer


between WAN accelerators. Ensure this
port is open in firewall between sites
where WAN accelerators are deployed.

Guest Processing Components


Connections with Non-Persistent Runtime Components
The following tables describe network ports that must be opened to ensure proper communication of the
backup server and backup infrastructure components with the non-persistent runtime components deployed
inside the VM guest OS for application-aware processing and indexing.

From To P rotocol P ort Notes

Backup server VM guest TCP 22 Default SSH port used as a control channel.
OS (Linux)

Guest TCP 6190 Used for communication with the guest


interaction interaction proxy.
proxy

TCP 6290 Used as a control channel for


communication with the guest interaction
proxy.

TCP 445 Port used as a transmission channel.

127 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Network ports described in the table below are NOT required when working in networkless mode over
PowerShell Direct.

From To P rotocol P ort Notes

Guest VM guest TCP 445 Required to deploy the runtime


interaction OS 135 coordination process on the VM guest OS.
proxy (Microsoft
Windows)
TCP 2500 to Default range of ports used as transmission
3300 channels for log shipping.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Used by the runtime process deployed


inside the VM for guest OS interaction.

Note: If you use default Microsoft Windows


firewall settings, you do not need to
configure dynamic RPC ports. During setup,
Veeam Backup & Replication automatically
creates a firewall rule for the runtime
process. If you use firewall settings other
than default ones or application-aware
processing fails with the "RPC function call
failed" error, you need to configure dynamic
RPC ports. For more information on how to
configure RPC dynamic port allocation to
work with firewalls, see this Microsoft KB
article.

TCP 22 Default SSH port used as a control channel.

128 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

VM guest TCP 2500 to Default range of ports used as transmission


OS (Linux) 3300 channels for log shipping.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

VM guest OS Guest TCP 2500 to Default range of ports used as transmission


interaction 3300 channels for log shipping.
proxy
Note: This range of ports applies to newly
installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

Connections with Persistent Agent Components


The following table describes network ports that must be opened to ensure proper communication of the
backup server with the persistent agent components deployed inside the VM guest OS for application-aware
processing and indexing.

From To P rotocol P ort Notes

Backup server VM guest TCP 6160 Default port used by Veeam Installer
OS (Linux) Service for Linux.

TCP 6162 Default Management Agent port. Required


if it is used as a control channel instead of
SSH.

Guest VM guest TCP 6160 Default port and failover port used by
interaction OS 11731 Veeam Installer Service.
proxy

TCP 6173 Used by the Veeam Guest Helper for guest


2500 OS processing and file-level restore.

129 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Log Shipping Components
The following tables describe network ports that must be opened to ensure proper communication between log
shipping components.

• Log Shipping Server Connections

• MS SQL Guest OS Connections

• Oracle Guest OS Connections

• PostgreSQL Guest OS Connections

Log Shipping Server Connections

From To P rotocol P ort Notes

Backup server Log TCP 445 Required for deploying


shipping 135 Veeam Backup & Replication components.
server

TCP 6160 Default port used by Veeam Installer


Service.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft Windows


firewall settings, you do not need to
configure dynamic RPC ports. During setup,
Veeam Backup & Replication automatically
creates a firewall rule for the runtime
process. If you use firewall settings other
than default ones or application-aware
processing fails with the "RPC function call
failed" error, you need to configure dynamic
RPC ports. For more information on how to
configure RPC dynamic port allocation to
work with firewalls, see this Microsoft KB
article.

130 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Log shipping Backup TCP 2500 to Default range of ports used for
server repository 3300 communication with a backup repository
and transfer log backups.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

MS SQL Guest OS Connections

From To P rotocol P ort Notes

Guest MS SQL VM TCP 445 [Non-persistent runtime components only]


interaction guest OS 135 Required for deploying
proxy Veeam Backup & Replication components
including Veeam Log Shipper runtime
component.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

TCP 2500 to Default range of ports used for


3300 communication with a guest OS.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

131 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 49152 to [Non-persistent runtime components only]


65535 Dynamic RPC port range for Microsoft
Windows 2008 and later. For more
information, see this Microsoft KB article.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: If you use default Microsoft Windows


firewall settings, you do not need to
configure dynamic RPC ports. During setup,
Veeam Backup & Replication automatically
creates a firewall rule for the runtime
process. If you use firewall settings other
than default ones or application-aware
processing fails with the "RPC function call
failed" error, you need to configure dynamic
RPC ports. For more information on how to
configure RPC dynamic port allocation to
work with firewalls, see this Microsoft KB
article.

TCP 6160 [Persistent agent components only] Default


11731 port and failover port used by Veeam
Installer Service.

TCP 6167 Used by the Veeam Log Shipping Service for


preparing the database and taking logs.

MS SQL VM Guest TCP 2500 to Default range of ports used for


guest OS interaction 3300 communication with a guest interaction
proxy proxy.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

132 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

MS SQL VM Backup TCP 2500 to Default range of ports used for


guest OS repository 3300 communication with a backup repository
and transfer log backups. Should be opened
if log shipping servers are not used in the
infrastructure and the MS SQL server has a
direct connection to the backup repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

MS SQL VM Log TCP 2500 to Default range of ports used for


guest OS shipping 3300 communication with a log shipping server
server and transfer log backups.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

Oracle Guest OS Connections

From To P rotocol P ort Notes

Guest Oracle VM TCP 445 [Non-persistent runtime components only]


interaction guest OS 135 Required for deploying
proxy (Microsoft Veeam Backup & Replication components
Windows) including Veeam Log Shipper runtime
component.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

133 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 2500 to Default range of ports used for


3300 communication with a guest OS.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

TCP 49152 to [Non-persistent runtime components only]


65535 Dynamic RPC port range for Microsoft
Windows 2008 and later. For more
information, see this Microsoft KB article.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: If you use default Microsoft Windows


firewall settings, you do not need to
configure dynamic RPC ports. During setup,
Veeam Backup & Replication automatically
creates a firewall rule for the runtime
process. If you use firewall settings other
than default ones or application-aware
processing fails with the "RPC function call
failed" error, you need to configure dynamic
RPC ports. For more information on how to
configure RPC dynamic port allocation to
work with firewalls, see this Microsoft KB
article.

TCP 6160 [Persistent agent components only] Default


11731 port and failover port used by Veeam
Installer Service.

TCP 6167 Used by the Veeam Log Shipping Service for


preparing the database and taking logs.

Oracle VM TCP 22 [Non-persistent runtime components only]


guest OS Default SSH port used as a control channel.
(Linux)
This port is NOT required when working in
networkless mode over PowerShell Direct.

134 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 6162 [Persistent agent components only] Default


Management Agent port. Required if it is
used as a control channel instead of SSH.

TCP 2500 to Default range of ports used for


3300 communication with a guest OS.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

Oracle VM Guest TCP 2500 to Default range of ports used for


guest OS interaction 3300 communication with a guest interaction
proxy proxy.

These ports are NOT required when working


in networkless mode over PowerShell
Direct.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

Oracle VM Backup TCP 2500 to Default range of ports used for


guest OS repository 3300 communication with a backup repository
and transfer log backups. Should be opened
if log shipping servers are not used in the
infrastructure and the Oracle server has a
direct connection to the backup repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

135 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Oracle VM Log TCP 2500 to Default range of ports used for


guest OS shipping 3300 communication with a log shipping server
server and transfer log backups.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

PostgreSQL Guest OS Connections

From To P rotocol P ort Notes

Guest PostgreSQL TCP 22 [Non-persistent runtime components only]


interaction VM guest Default SSH port used as a control channel.
proxy OS
.

TCP 6162 [Persistent agent components only] Default


Management Agent port. Required if it is
used as a control channel instead of SSH.

TCP 2500 to Default range of ports used for


3300 communication with a guest OS.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

136 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

PostgreSQL Guest TCP 2500 to Default range of ports used for


VM guest OS interaction 3300 communication with a guest interaction
proxy proxy.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

PostgreSQL Backup TCP 2500 to Default range of ports used for


VM guest OS repository 3300 communication with a backup repository
and transfer log backups. Should be opened
if log shipping servers are not used in the
infrastructure and the PostgreSQL server
has a direct connection to the backup
repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

PostgreSQL Log TCP 2500 to Default range of ports used for


VM guest OS shipping 3300 communication with a log shipping server
server and transfer log backups.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without upgrade
from previous versions. If you have
upgraded from an earlier version of the
product, the range of ports from 2500 to
5000 applies to the already added
components.

Recovery Components
• Guest OS File Recovery

• Veeam vPower NFS Service

• Veeam U-AIR

137 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Microsoft Active Directory Domain Controller Connections During Application Item Restore

• Microsoft Exchange Server Connections During Application Item Restore

• Microsoft SQL Server Connections During Application Item Restore

• Restore to Amazon EC2

• Restore to Google Cloud

• Restore to Microsoft Azure

Guest OS File Recovery


The following table describes network ports that must be opened to ensure proper communication between
components for guest OS file recovery.

• Mount Server Connections

• Helper Appliance Connections

• Helper Host Connections

• Guest OS Connections

Mount Server Connections

From To P rotocol P ort Notes

Mount server Backup server TCP 9401 Used for communication with the Veeam
Backup Service.

Backup TCP 2500 to Default range of ports used for


repository 3300 communication with a backup repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup server Mount server TCP 445 Required for deploying


Veeam Backup & Replication components.

138 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 2500 to Default range of ports used for


3300 communication with a mount server.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

TCP 6160 Default port used by Veeam Installer


Service including checking the
compatibility between components
before starting the recovery process.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 6170 Used for communication with a local or


remote Mount Service.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

139 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Helper Appliance Connections

From To P rotocol P ort Notes

Helper Backup TCP 2500 to Default range of ports used for


appliance repository 3300 communication with a backup repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup server Helper TCP 22 Default SSH port used as a control


appliance channel.

TCP 2500 to Default range of ports used for


3300 communication with a helper appliance.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Mount server Helper TCP 22 Default SSH port used as a control


appliance channel.

TCP 2500 to Default range of ports used for


3300 communication with a helper appliance.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

140 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Helper Host Connections

From To P rotocol P ort Notes

Helper host Backup TCP 2500 to Default range of ports used for
repository 3300 communication with a backup repository.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup server Helper host TCP 22 Default SSH port used as a control
channel.

TCP 2500 to Default range of ports used for


3300 communication with a helper host.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

TCP 6162 Default port used by Veeam Data Mover


Service.

TCP 32768 to Dynamic port range for Linux


60999 distributions. Used for communication
with a helper host. For more information,
see the Linux kernel documentation.

Mount server Helper host TCP 22 Default SSH port used as a control
channel.

141 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

TCP 2500 to Default range of ports used for


3300 communication with a helper host.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

TCP 32768 to Dynamic port range for Linux


60999 distributions. Used for communication
with a helper host. For more information,
see the Linux kernel documentation.

Guest OS Connections

From To P rotocol P ort Notes

VM guest OS Helper TCP 21 Default port used for protocol control


(Linux/Unix) appliance messages if FTP server is enabled.

Helper VM guest OS TCP 20 Default port used for data transfer if FTP
appliance (Linux/Unix) server is enabled.

TCP 2500 to Default range of ports used for


3300 communication with a VM guest OS.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

142 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Helper host VM guest OS TCP 2500 to Default range of ports used for
(Linux/Unix) 3300 communication with a VM guest OS.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Backup server VM guest OS TCP 22 Default SSH port used as a control


(Linux/Unix) channel.

Mount server VM guest OS TCP 445 Required to deploy the runtime


(Microsoft 135 coordination process on the VM guest OS.
Windows)

TCP 6160 Default port and failover port used by


11731 Veeam Installer Service.

TCP 6173 Used by the Veeam Guest Helper for


2500 guest OS processing and file-level restore
if persistent agent components are
deployed inside the VM guest OS.

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later. For more
information, see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

143 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Backup server VM guest OS TCP 2500 to Default range of ports used for
3300 communication with a VM guest OS.

Note: This range of ports applies to newly


installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Veeam vPower NFS Service

From To P rotocol P ort Notes

Backup server Microsoft TCP 6160 Default port used by Veeam Installer
Windows Service.
server with
the mount
server role TCP 6161 Default port used by the Veeam vPower
running NFS Service.
vPower NFS
Service

ESXi host Microsoft TCP 111 Standard port used by the port mapper
Windows UDP service.
server with
the mount
server role TCP 1058+ or Default mount port. The number of port
running UDP 1063+ depends on where the vPower NFS
vPower NFS Service is located:
Service • 1058+: If the vPower NFS Service is
located on the backup server.
• 1063+: If the vPower NFS Service is
located on a separate Microsoft
Windows machine.

If port 1058/1063 is occupied, the


succeeding port numbers will be used.

TCP 2049+ Standard NFS port. If port 2049 is


UDP occupied, the succeeding port numbers
will be used.

144 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Backup Microsoft TCP 2500 to Default range of ports used as


repository or Windows 3300 transmission channels during Instant
gateway server with Recovery to VMware vSphere.
server the mount
working with server role For every TCP connection that a job uses,
backup running one port from this range is assigned.
repository vPower NFS
Note: This range of ports applies to newly
Service
installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Microsoft Backup TCP 2500 to Default range of ports used as


Windows repository or 3300 transmission channels during Instant
server with gateway Recovery to VMware vSphere.
the mount server
server role working with For every TCP connection that a job uses,
running backup one port from this range is assigned.
vPower NFS repository
Note: This range of ports applies to newly
Service
installed Veeam Backup & Replication
starting from version 10.0, without
upgrade from previous versions. If you
have upgraded from an earlier version of
the product, the range of ports from
2500 to 5000 applies to the already
added components.

Veeam U-AIR
The following table describes network ports that must be opened to ensure proper communication of U -AIR
wizards with other components.

From To P rotocol P ort Notes

U-AIR wizards Veeam TCP 9394 Used by default for communication with
Backup Veeam Backup Enterprise Manager. Can
Enterprise be customized during Veeam Backup
Manager Enterprise Manager installation.

145 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Active Directory Domain Controller Connections During Application Item
Restore
The following table describes network ports that must be opened to ensure proper communication of the
backup server with the Microsoft Active Directory VM during application-item restore.

From To P rotocol P ort Notes

Backup server Microsoft TCP 135 Used for communication between the
Active domain controller and backup server.
Directory VM
guest OS
TCP, 389 LDAP connections.
UDP

TCP 636, 3268, LDAP connections.


3269

TCP 49152 to Dynamic RPC port range for Microsoft


65535 Windows 2008 and later used by the
runtime coordination process deployed
inside the VM guest OS for application-
aware processing For more information,
see this Microsoft KB article.

Note: If you use default Microsoft


Windows firewall settings, you do not
need to configure dynamic RPC ports.
During setup,
Veeam Backup & Replication
automatically creates a firewall rule for
the runtime process. If you use firewall
settings other than default ones or
application-aware processing fails with
the "RPC function call failed" error, you
need to configure dynamic RPC ports. For
more information on how to configure
RPC dynamic port allocation to work with
firewalls, see this Microsoft KB article.

Microsoft Exchange Server Connections During Application Item Restore


The following table describes network ports that must be opened to ensure proper communication of the
Veeam backup server with the Microsoft Exchange Server system during application-item restore.

From To P rotocol P ort Notes

Backup Microsoft Exchange TCP 80, 443 WebDAV connections.


server 2003/2007 CAS
Server

146 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Microsoft Exchange TCP 443 Microsoft Exchange Web Services


2010/2013/2016/2019 Connections.
CAS Server

Microsoft SQL Server Connections During Application Item Restore


The following table describes network ports that must be opened to ensure proper communication of the
backup server with the VM guest OS system during application-item restore.

From To P rotocol P ort Notes

Backup server Microsoft TCP 1433, Used for communication with the
SQL VM guest 1434 and Microsoft SQL Server installed inside the
OS other VM.

Port numbers depends on configuration


of your Microsoft SQL server. For more
information, see this Microsoft article.

UDP 1434 Used by the Microsoft SQL Server


Browser service.

For more information, see this Microsoft


article.

Restore to Amazon EC2

From To P rotocol P ort Notes

Backup server Helper TCP 22 Used as a communication channel to the


or backup appliance helper appliance.
repository

TCP 443 Default redirector port. You can change


the port in helper appliance settings. For
details, see the Sp ecify Helper Appliance
section in Restore to Amazon EC2.

147 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore to Google Cloud

From To P rotocol P ort Notes

Backup server Helper TCP 22 Used as a communication channel to the


or backup appliance helper appliance.
repository

TCP 443 Default redirector port. You can change


the port in helper appliance settings. For
details, see the Sp ecify Helper Appliance
section in Restore to Google Cloud.

Restore to Microsoft Azure

From To P rotocol P ort Notes

Backup Helper TCP 22 Used by default as a communication channel to


server appliance the helper appliance when restoring Linux
workloads. Can be changed during helper
appliance deployment. For details, see
Configuring Helper Appliances.

Microsoft TCP 443 Default management and data transport port


Azure required for communication with Microsoft
Azure.

Azure TCP 443 Used by Veeam Backup & Replication to install


Windows the Azure Windows VM agent on the restored
VM agent VM through the following URLs:
distribution
• go.microsoft.com
server
• aka.ms (additional components
required for the Azure Windows VM
agent installation)
• github.com (additional components
required for the Azure Windows VM
agent installation)
• objects.githubusercontent.com
(additional components required for the
Azure Windows VM agent installation)

Consider that these URLs are subject to


change. For more information, see this
Microsoft article.

148 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
From To P rotocol P ort Notes

Azure Stack TCP 443, 30024 Default management and data transport port
Hub required for communication with Azure Stack
Hub.

Backup Azure TCP 443 Default management and data transport port
server or restore required for communication with the Azure
backup proxy restore proxy appliance. The port must be
repository appliance opened on the backup server and backup
(former repository storing VM backups.
Azure proxy)
Can be changed in the settings of the Azure
restore proxy appliance. For details, see Specify
Credentials and Transport Port.

Veeam Backup Enterprise Manager


Veeam Backup Enterprise Manager Connections

Veeam Explorers
• Veeam Explorer for Microsoft Active Directory Connections

• Veeam Explorer for Microsoft Exchange Connections

• Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft OneDrive for Business
Connections

• Veeam Explorer for Microsoft SQL Server Connections

• Veeam Explorer for Microsoft Teams Connections

• Veeam Explorer for Oracle Connections

• Veeam Explorer for PostgreSQL Connections

Veeam Cloud Connect


Veeam Cloud Connect Connections

Veeam Agents
Veeam Agent for Microsoft Windows
• Connections for Veeam Agent for Microsoft Windows Operating in Managed Mode

• Connections for Veeam Agent for Microsoft Windows Operating in Standalone Mode

149 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Agent for Linux

• Connections for Veeam Agent for Linux Operating in Managed Mode

• Connections for Veeam Agent for Linux Operating in Standalone Mode

Veeam Agent for Mac

• Connections for Veeam Agent for Mac Operating in Managed Mode

• Connections for Veeam Agent for Mac Operating in Standalone Mode

Veeam Plug-ins for Enterprise Applications


• Veeam Plug-in for SAP HANA Connections

• Veeam Plug-in for Oracle RMAN Connections

• Veeam Plug-in for SAP on Oracle Connections

• Veeam Plug-in for Microsoft SQL Server Connections

Veeam Plug-ins for Cloud Solutions


• AWS Plug-in for Veeam Backup & Replication

• Microsoft Azure Plug-in for Veeam Backup & Replication

• Google Cloud Platform Plug-in for Veeam Backup & Replication

Kasten K10
Veeam Plug-ins for Kasten K10

Other Connections
NDMP Servers
The following table describes network ports that must be opened to ensure proper communication with NDMP
servers.

From To P rotocol P ort Notes

Gateway NDMP server NDMP 10000 Port used for data transfer between the
server components.

150 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Mail Servers
The following table describes network ports that must be opened to ensure proper communication of the
backup server with mail servers.

From To P rotocol P ort Notes

Backup SMTP server TCP 25 Used by the SMTP server.


server

TCP 587 Used by the SMTP server if SSL is


enabled.

Gmail REST API TCP 443 Used to communicate with Google


(gmail.googleapis.com) Mail services.

Microsoft Graph REST API TCP 443 Used to communicate with Microsoft
(graph.microsoft.com, Exchange Online organizations.
login.microsoftonline.com)

Event Forwarding Components


The following table describes network ports that must be opened to ensure proper communication with event
forwarding components.

From To P rotocol P ort Notes

Backup server Syslog server TCP 514 Default port used to communicate with
UDP the syslog server.

TLS 6514 Default port used to communicate with


the syslog server over TLS.

Internet Connections
If you use an HTTP/HTTPS proxy server to access the Internet, make sure that WinHTTP settings are properly
configured on Microsoft Windows machines with Veeam backup infrastructure components. For information on
how to configure WinHTTP settings, see Microsoft Docs.

NOTE

Tenants cannot access Veeam Cloud Connect infrastructure components through HTTP/HTTPS proxy
servers. For information on supported protocols for Veeam Cloud Connect, see the Ports section in the
Veeam Cloud Connect Guide.

151 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Naming Conventions
Do not use Microsoft Windows reserved names for names of the backup server, managed servers, backup
repositories, jobs, tenants and other objects created in Veeam Backup & Replication: CON, PRN, AUX, NUL,
COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7,
LPT8 and LPT9.

If you plan to store backups on a repository operating in the per-machine mode, do not use Microsoft Windows
reserved names for names of the virtual machines to back up.

If you use a reserved name, Veeam Backup & Replication may not work as expected. For more information on
naming conventions in Microsoft Windows, see Microsoft Docs.

152 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Security Guidelines
When you set up the backup infrastructure, one thing that you must not overlook is security. The backup
infrastructure can be potentially used as a backdoor to gain access to your systems and data. This section
includes a number of security features and recommendations that will help you prevent potential security issues
and reduce the risk of compromising sensitive data.

153 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
General Security Considerations
General security considerations include best practices which help you to harden backup infrastructure, build a
more secure environment, and mitigate risks of being compromised. Ensure that your backup infrastructure
meet the common recommendations described in this section. For more information about hardening specific
backup infrastructure components, see Securing Backup Infrastructure.

Network
To secure the communication channel for backup traffic, consider the following recommendations:

• Use network segmentation. Create network segmentation policies to define network boundaries, control
traffic between subnets and limit access to security-sensitive backup infrastructure components. Also,
ensure that only ports used by backup infrastructure components are opened.

• Isolate backup traffic. Use an isolated network to transport data between backup infrastructure
components — backup server, backup proxies, repositories and so on.

• Disable outdated network protocols. Check that the following protocols are disabled:

o SSL 2.0 and 3.0 as they have well-known security vulnerabilities and are not NIST-approved. For more
information, see NIST guidelines.

o TLS 1.0 and 1.1 if they are not needed. For more information, see NIST guidelines.

o LLMNR and NetBIOS broadcast protocols to prevent spoofing and man-in-the-middle (MITM) attacks.

o SMB 1.0 protocol as it has a number of serious security vulnerabilities including remote code
execution. For more information, see this Microsoft article.

User Roles and Permissions


Administrator privileges on a backup server or a backup proxy allow the user to access other backup
infrastructure components. If an attacker gains such permissions, they can destroy most of the production data,
backups, and replicas, as well as compromise other systems in your environment. To mitigate risks, use the
principle of the least privilege. Provide the minimal required permissions needed for the accounts to run. For
more information, see Permissions.

Security Audit
Perform regular security audits to estimate your backup infrastructure by security criteria and understand if it is
compliant with best practices, industry standards, or federal regulations.

The most possible causes of a credential theft are missing operating system updates and use of outdated
authentication protocols. To mitigate risks, ensure that all software and hardware running backup infrastructure
components are updated regularly. If the latest security updates and patches are installed on backup
infrastructure servers, this will reduce the risk of exploiting vulnerabilities by attackers. Note that you should
work out an update management strategy without a negative impact on production environment.

NOTE

You can subscribe to Veeam security advisories published in the Veeam Knowledge Base to stay up to date
with the latest security updates.

154 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Windows Server
To secure Microsoft Windows-based backup infrastructure components, consider the following
recommendations:

• Use operating system versions with Long Term Servicing Channel (LTSC). For these versions Microsoft
provides extended support including regular security upd ates. For more information, see this Microsoft
article.

• Turn on Microsoft Defender Firewall with Advanced Security . Set up rules for inbound and outbound
connections according to your infrastructure and Microsoft best practices. For more information, see this
Microsoft article.

• Disable remote services if they are not needed:

o Remote Desktop Service

o Remote Registry service

o Remote PowerShell

o Windows Remote Management service

NOTE

A backup server also requires additional configuration described in section Securing Backup Infrastructure.

Linux Server
To secure Linux-based backup infrastructure components, consider the following recommendations:

• Use operating system versions with long-term support (LTS). LTS versions of popular community-based
and commercial Linux distributions have extended support including regular security updates.

• Choose strong encryption algorithms for SSH . To communicate with Linux servers deployed as a part of
the backup infrastructure, Veeam Backup & Replication uses SSH. Make sure that for the SSH tunnel you
use a strong and proven encryption algorithm, with sufficient key length. For more information, see this
section. Also, ensure that private keys are kept in a highly secure place and cannot be uncovered by a
third-party.

NOTE

For the Linux hardened repository, instead of SSH Veeam Backup & Replication uses SHA256RSA
self-signed certificates with 2048-bit RSA key.

• Avoid using password authentication to connect to remote servers over SSH . Using key-based SSH
authentication is generally considered more secure than using password authentication and helps averting
man-in-the-middle (MITM) attacks. The private key is not passed to the server and cannot be captured
even if a user connects to a fake server and accepts a bad fingerprint.

NOTE

A Linux hardened repository requires a specific security configuration described section Hardened
Repository.

155 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Securing Backup Infrastructure
This section includes recommendations for hardening specific backup infrastructure components in addition to
general security considerations.

Infrastructure Planning
For large environments, adding the backup server and other backup infrastructure components to a
management domain in a separate Active Directory forest is the best practice for building the most secure
infrastructure.

For medium-sized and small environments, backup infrastructure components can be placed to a separate
workgroup. If you want to use specific Veeam Backup Enterprise Manager features, for example, SAML
authentication or restore of Microsoft Exchange items, you can add this component to the domain.

In both cases, backup infrastructure components should be placed to a separate network where applicable. Also,
it is recommended to use the hardened backup repository.

Backup Server
To secure the backup server, consider the following recommendations:

• Restrict outbound connections. To enable product update check, automatic license update, and license
usage reporting, the backup server must be connected to the internet and be able to send requests to
servers on the internet. Allow only HTTPS connections to the Veeam Update Notification Server
(dev.veeam.com), Veeam License Update Servers (vbr.butler.veeam.com, autolk.veeam.com),
and Microsoft WSUS servers or Microsoft Update sites.

• Restrict inbound connections. Inbound connectivity to backup servers from the internet must not be
allowed. If you want to manage backup servers remotely over the Internet, you can deploy the
Veeam Backup & Replication console on a jump server. Service providers who want to manage backup
servers remotely can use the Veeam Backup Remote Access functionality. For more information, see the
Using Remote Access Console section in the Veeam Cloud Connect Guide.

NOTE

The account used for RDP access must not have local Administrator privileges on the jump server,
and you must never use the saved credentials functionality for RDP access or any other remote
console connections. To restrict users from saving RDP credentials, you can use Group Policies. For
more information, see this article.

• E ncrypt backup traffic. By default, Veeam Backup & Replication encrypts network traffic transferred
between public networks. To ensure secure communication of sensitive data within the boundaries of the
same network, encrypt backup traffic also in private networks. For more information, see Enabling Traffic
Encryption.

• Use multi-factor authentication. Enable multi-factor authentication (MFA) in the


Veeam Backup & Replication console to protect user accounts with additional user verification. For more
information, see Multi-Factor Authentication.

• Use self-signed TLS certificates generated by Veeam Backup & Replication. This type of certificates is
recommended for establishing a secure connection from backup infrastructure components to the backup
server. For more information, see Generating Self-Signed Certificates.

156 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Red uce the number of user sessions opened for a long time. Set the idle timeout to automatically log off
users. To do this, go to Users a nd Roles, select the E na ble auto log off after <number> min of inactivity
check box, and set the number of minutes.

• Restrict untrusted Linux VMs and Linux servers to connect to the backup server . Enable a manual SSH
fingerprint verification for machines that do not meet specific conditions. For more information, see Linux
Host Authentication.

• Use the recommended Access Control List (ACL) for the custom installation folder . If you specify a custom
installation folder for Veeam Backup & Replication, use the recommended ACL configuration to prevent
privilege escalation and arbitrary code execution (ACE) attacks. Remove all inherited permissions from this
folder. Then, add the following permissions:

o Administrators: Full control, applies to this folder, subfolders and files

o SYSTEM: Full control, applies to this folder, subfolders and files

o CREATOR OWNER: Full control, applies to subfolders and files only

o Users: Read & Execute, applies to this folder, subfolders and files

Veeam Backup & Replication Database


The Veeam Backup & Replication configuration database stores credentials of user accounts required to connect
to virtual servers and other systems in the backup infrastructure. All passwords stored in the database are
encrypted. However, a user with administrator privileges on the backup server can decrypt passwords which is a
potential threat.

To secure the Veeam Backup & Replication configuration database, consider the following recommendations:

• Restrict user access to the database. Check that only authorized users can access the backup server and
the server that hosts the Veeam Backup & Replication configuration database (if the database runs on a
remote server).

• E ncrypt data in configuration backups. Enable data encryption for configuration backup to secure
sensitive data stored in the configuration database. For details, see Creating Encrypted Configuration
Backups. Also, ensure that the repository for configuration backups is not located in the same network
with the backup server.

Backup Repositories
To secure data stored in backups and replicas, consider the following recommendations:

• Follow the 3-2-1 rule. To build a successful data protection, use the 3-2-1 rule when designing your
backup infrastructure. For more information, see Plan How Many Copies of Data You Need (3-2-1 rule).

• E nsure physical security of all data storage components. All devices including backup repositories,
proxies, and gateway servers must be physically located in an access-controlled area.

• Restrict user access to backups and replicas. Check that only authorized users have permissions to
access backups and replicas on target servers.

• E ncrypt data in backups. Use Veeam Backup & Replication built-in encryption to protect data in
backups. For more information, see Encryption Best Practices.

• E ncrypt SMB traffic. If you use SMB shares in your backup infrastructure, enable SMB signing to prevent
NTLMv2 relay attacks. Also, enable SMB encryption.

157 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• E na ble immutability for backups. To protect backup files from being modified or deleted, you can make
them immutable. The feature is supported for any tier of scale-out backup repository.

• Use offline media to keep backup files in addition to virtual storage. For more information, see Backup
Repositories with Rotated Drives and the Tape Devices Support Guide.

• E nsure security of mount servers. Machines performing roles of mount servers have access to the
backup repositories and ESXi hosts which make them a potential source of vulnerability. Check that all
required security recommendations are applied to these backup infrastructure components.

Veeam Backup Enterprise Manager


To secure Veeam Backup Enterprise Manager server, consider the following recommendations:

• Install Veeam Backup & Replication server and Veeam Backup Enterprise Manager on different
ma chines. Deploy Veeam Backup Enterprise Manager on a server different from the
Veeam Backup & Replication server to prevent a key change attack. Even if passwords are lost due to
unauthorized access, you can restore lost data with the help of Enterprise Manager. For more
information, see Decrypting Data Without Password.

• E na ble encryption password loss protection . To improve data loss protection, provide an alternative
way to decrypt the data if a password for encrypted backup or tape is lost. For more information, see
Managing Encryption Keys.

• Use the recommended Access Control List (ACL) for the custom installation folder . If you specify a
custom installation folder for Veeam Backup Enterprise Manager, use the recommended ACL
configuration to prevent privilege escalation and arbitrary code execution (ACE) attacks. Remove all
inherited permissions from this folder. Then, add the following permissions:

o Administrators: Full control, applies to this folder, subfolders and files

o SYSTEM: Full control, applies to this folder, subfolders and files

o CREATOR OWNER: Full control, applies to subfolders and files only

o Users: Read & Execute, applies to this folder, subfolders and files

Veeam Cloud Connect


Veeam Cloud Connect secures communication between the provider side and tenant side with TLS. If an attacker
obtains a provider’s private key, backup traffic can be eavesdropped and decrypted. The attacker can also use
the certificate to impersonate the provider (man-in-the-middle attack). To mitigate risks, Veeam Cloud Connect
providers must ensure that the TLS certificate is kept in a highly secure place and cannot be uncovered by a
third-party.

158 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Security & Compliance Analyzer
Veeam Backup & Replication provides a built-in tool to ensure that your backup server configuration follows
security best practices for Veeam backup infrastructure components based on Microsoft Windows Server and
Linux operating systems.

To perform a security check, open the Home tab and click Security & Compliance (Best P ractices Analyzer -
before Veeam Backup & Replication 12.1 (build 12.1.0.2131)) on the ribbon. After that, the Security & Compliance
Ana lyzer window opens and the security check starts automatically.

Configuration parameters set up as recommended will have the Passed status. Parameters that have the Not
implemented status should be revised in terms of your backup infrastructure. You can set them up as
recommended or exclude specific parameters from the checklist.

To see the last scan results, click La st run.

TIP

Run the Security & Compliance Analyzer regularly, especially after you made significant changes in the
backup infrastructure. To set up scan scheduling, see this section.

Configuration Parameters
The Security & Compliance Analyzer checks the following configuration parameters:

P a rameter Check Condition Notes

Ba ckup Infrastructure Security

159 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Remote The Remote Desktop Services service is not running. The Sta rtup type Remote services
Desktop parameter is set to Disabled . should be
Services disabled if they
(TermService) are not needed.
should be Note that for the
disabled Veeam Cloud
Connect
infrastructure,
this parameter
must be enabled
if the SP uses
Remote Desktop
Protocol (RDP) to
connect to the
tenant backup
server. For more
information, see
Remote Desktop
Connection to
Tenant.

Remote The Remote Registry service is not running. The Sta rtup type Remote services
Registry parameter is set to Disabled . should be
service disabled if they
(RemoteRegist are not needed.
ry) should be
disabled

Windows The Windows Remote Management (WS-Management)service is not Remote services


Remote running. The Sta rtup type parameter is set to Disabled . should be
Management disabled if they
(WinRM) are not needed.
service should
be disabled

160 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Windows The following PowerShell command returns True for Domain, Public, Microsoft
Firewall and Private firewall profiles: Defender Firewall
should be with Advanced
enabled Get-NetFirewallProfile | Format-Table Name, Enabled Security should
be turned on.
Also, rules for
inbound and
outbound
connections
should be set up
according to your
infrastructure
and Microsoft
best practices.
For more
information, see
this Microsoft
article.

WDigest The value of the WDigest


credentials HKLM\System\CurrentControlSet\Control\SecurityProvide credentials
caching should rs\WDigest\UseLogonCredential registry key is set to 0. caching stores
be disabled cleartext
credentials in
Windows RAM.
To reduce the risk
of credential
dumping attacks,
the setting
should be
disabled with a
registry value.
For more
information, see
this Microsoft
article.

161 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Web Proxy The WinHTTP Web Proxy Auto-Discovery service is not running. The The Web Proxy
Auto- Sta rtup type parameter is set to Disabled . Auto-Discovery
Discovery (WPAD) protocol
service The value of the provides
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Intern
(WinHttpAuto automatic
ProxySvc) et Settings\WinHttp\DisableWpad registry key is set to 1. discovery of web
should be proxy
disabled configuration. If
this feature is not
used in the
backup
infrastructure,
the WinHTTP
Web Proxy Auto-
Discovery Service
should be
disabled to
prevent man-in-
the-middle
(MITM) attacks.

162 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deprecated Values of the following registry keys are set to 1: Outdated
versions of SSL network
•
and TLS protocols SSL 2.0
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
should be and 3.0 should
disabled roviders\SCHANNEL\Protocols\SSL be disabled as
2.0\Client\DisabledByDefault they have well-
known security
•
vulnerabilities
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
and are not NIST-
roviders\SCHANNEL\Protocols\SSL approved. Also,
2.0\Server\DisabledByDefault TLS 1.0 and 1.1
• should be
disabled if they
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
are not needed.
roviders\SCHANNEL\Protocols\SSL For more
3.0\Client\DisabledByDefault information, see
• NIST guidelines.
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP Note that this
roviders\SCHANNEL\Protocols\SSL parameter will
3.0\Server\DisabledByDefault have the Passed
or Not
•
implemented
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
status only if
roviders\SCHANNEL\Protocols\TLS specific registry
1.0\Client\DisabledByDefault keys with specific
values exist. For
•
more
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
information, see
roviders\SCHANNEL\Protocols\TLS this Microsoft
1.0\Server\DisabledByDefault article. If the
• registry key does
not exist, the
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
parameter will
roviders\SCHANNEL\Protocols\TLS have the Unable
1.1\Client\DisabledByDefault to detect status.
•
If the registry key
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP existence cannot
roviders\SCHANNEL\Protocols\TLS be checked for
1.1\Server\DisabledByDefault some reason, the
parameter will
Values of the following registry keys are set to 0: also have the Not
implemented
•
status.
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\SSL
2.0\Client\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\SSl
2.0\Server\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP

163 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

roviders\SCHANNEL\Protocols\SSL
3.0\Client\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\SSl
3.0\Server\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\TLS
1.0\Client\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\TLS
1.0\Server\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\TLS
1.1\Client\Enabled
•
HKLM\SYSTEM\CurrentControlSet\Control\SecurityP
roviders\SCHANNEL\Protocols\TLS
1.1\Server\Enabled

164 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Windows The value of the HKLM\SOFTWARE\Microsoft\Windows Script Windows Script


Script Host Host\Settings registry key is set to 0. Host should be
should be disabled to
disabled prevent script-
based malware
attacks.

Before disabling
Windows Script
Host, make sure
that this service
is not used by
backup
infrastructure
components you
plan to install on
the backup
server. If there
are any (for
example,
PostgreSQL
database), it is
recommended to
disable the
service after you
install these
components.

SMBv1 The following PowerShell command returns False: Outdated


protocol network protocol
Get-SmbServerConfiguration | Select
should be SMB 1.0 should
EnableSMB1Protocol
disabled be disabled as it
has a number of
serious security
vulnerabilities
including remote
code execution.
For more
information, see
this Microsoft
article.

165 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Link-Local The HKLM\SOFTWARE\Policies\Microsoft\Windows Outdated


Multicast NT\DNSClient\EnableMultiCast registry key exists. The value of broadcast
Name the key is set to 0. protocol Link-
Resolution Local Multicast
(LLMNR) Name Resolution
should be (LLMNR) should
disabled be disabled to
prevent spoofing
and man-in-the-
middle (MITM)
attacks.

Note that this


parameter will
have the Passed
or Not
implemented
status only if
specific registry
keys with specific
values exist. If
the registry key
does not exist,
the parameter
will have the
Unable to detect
status.

If the registry key


existence cannot
be checked for
some reason, the
parameter will
also have the Not
implemented
status.

166 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

SMBv3 signing The following PowerShell command returns True for all specified If SMB shares are
and encryption parameters: used in the
should be backup
enabled Get-SmbServerConfiguration | select infrastructure,
RequireSecuritySignature, EncryptData,
SMB signing and
EnableSecuritySignature
encryption
should be
enabled to
prevent NTLMv2
relay attacks. For
more
information, see
these Microsoft
articles:
Configure SMB
Signing with
Confidence, SMB
security
enhancements.

P roduct Configuration

MFA for the In the Users and Roles > Security window, the E nable multi-factor Multi-factor
backup a uthentication (MFA) check box is selected. authentication
console should (MFA) should be
be enabled enabled for the
Veeam Backup &
Replication
console to
protect user
accounts with
additional user
verification. For
more
information, see
Multi-Factor
Authentication.

167 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Immutable or At least one of the following components is added to the Immutable


offline (air Veeam Backup & Replication console and actively used: repositories
gapped) media should be used to
• Backup repository with enabled immutability
should be protect backup
used • Backup repository with rotated drives files from being
• Tape device modified or
deleted. For
more
information, see
Immutability.

Offline media
should be used to
keep backup files
in addition to
virtual storage
devices. For more
information, see
Backup
Repositories with
Rotated Drives
and Tape Devices
Support.

Password loss In Veeam Backup Enterprise Manager settings, the E na ble encryption Password loss
protection p a ssword loss protection check box is selected. protection should
should be be enabled on
enabled Veeam Backup
Enterprise
Manager to
provide an
alternative way
to decrypt the
data if a
password for
encrypted backup
or tape is lost.
For more
information, see
Managing
Encryption Keys.

168 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Backup server The backup server is in a workgroup. Adding the


should not be backup server
a part of the and other backup
production infrastructure
domain components to a
management
domain in a
separate Active
Directory forest is
the best practice
for building the
most secure
infrastructure.
For medium-
sized and small
environments,
backup
infrastructure
components can
be placed to a
separate
workgroup.

Note that this


parameter will
have the Passed
status only if the
backup server is
not joined to any
domain. In other
cases, it will have
the Unable to
detect status
because there is
no way to
identify the
production
domain
automatically.

Email In the Op tions > E-Mail Settings window, the E na ble e-mail Email
notifications notifications check box is selected. notifications
should be should be
enabled enabled to
monitor job
statuses. For
more
information, see
Specifying Email
Notification
Settings.

169 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

All backups At least one of the following jobs or components exists in the To be compliant
should have at Veeam Backup & Replication console: with the 3-2-1
least one copy rule, at least one
• Backup copy job
(the 3-2-1 backup copy job
backup rule) • Scale-out backup repository with the copy mode should be
• Archive Tier created, or a
scale-out backup
repository with
the copy mode or
archive tier
should be added.
For more
information, see
Plan How Many
Copies of Data
You Need (3-2-1
rule).

Reverse In the backup job settings, the incremental backup method is selected. The reverse
incremental incremental
backup mode backup method
is deprecated should not be
and should be used as it
avoided produces the
heaviest I/O
impact on the
backup storage
compared to
other backup
methods. For
more
information, see
Backup Methods.

Unknown In the Op tions > Security window, the Ad d unknown hosts to the list Untrusted Linux
Linux servers ma nually option is selected in the Linux hosts authentication section. VMs and Linux
should not be servers must be
trusted allowed to
automatically connect to the
backup server
only using
manual SSH
fingerprint
verification. For
more
information, see
Linux Host
Authentication.

170 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

The In the configuration backup settings, the default backup repository or The configuration
configuration any other folder on the backup server are not selected as target backup must not
backup must backup repository. be stored on the
not be stored backup server or
on the backup on the default
server backup
repository to be
able to recover
its configuration
in case of failure.
For more
information, see
Configuration
Backup.

Host to proxy For VMware backup proxy that is used the Network transport mode, If a VMware
traffic the E na ble host to proxy traffic encryption in Network mode (NBDSSL) backup proxy
encryption check box is selected. uses the Network
should be transport mode,
enabled for it is
the Network recommended to
transport transfer VM data
mode over an
encrypted TLS
connection. For
more information
about this
configuration and
its limitations,
see Choose
Server.

Hardened The hardened repository added to the Veeam Backup & Replication To reduce the
repositories console is not hosted on a virtual machine. attack surface,
should not be the hardened
hosted in repository should
virtual be hosted on a
machines physical machine
with local
storage. For more
information
about hardened
repository
requirements, see
Requirements
and Limitations.

171 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Network In the Global Network Traffic Rules window, all added network traffic Network traffic
traffic rules have the E ncrypt network traffic check box selected. encryption
encryption should be
should be enabled in the
enabled in the backup network
backup to ensure secure
network communication
of sensitive data
not only between
public networks
but also between
private ones. For
more
information, see
Enabling Traffic
Encryption.

Linux servers Linux servers added to the Veeam Backup & Replication console do not Key-based SSH
should have use standard accounts. authentication is
password- generally
based considered more
authentication secure than
disabled password-based
authentication.
The private key is
not passed to the
server and cannot
be captured even
if a user connects
to a fake server
and accepts a bad
fingerprint. This
helps averting
man-in-the-
middle (MITM)
attacks.

Backup The Veeam Backup Service runs under a LocalSystem account. The account used
services to run Veeam
should be services should
running under be a LocalSystem
the account.
LocalSystem
account

172 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Configuration In the configuration backup settings, the following check boxes are Configuration
backup should selected: backup should be
be enabled enabled to
• The E nable configuration backup to the following repository
and use reduce the risk of
encryption check box. data loss and
• The E nable configuration backup file encryption check box. manage the
Veeam Backup &
Replication
configuration
database easier.
For more
information, see
Configuration
Backup and
Restore.

Data encryption
for configuration
backup should be
enabled to secure
sensitive data
stored in the
configuration
database. For
more
information, see
Creating
Encrypted
Configuration
Backups.

Credentials Passwords of the user accounts added to the Credentials Manager, For all user
and encryption Cloud Credentials Manager, and Password Manager were changed less accounts added
passwords than 365 days ago. to the Credentials
should be Manager, Cloud
rotated at Credentials
least annually Manager and
Password
Manager,
passwords should
be changed at
least once a year.

173 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Hardened Hardened repositories added to the Veeam Backup & Replication SSH connection is
repositories console are not available through SSH connection. necessary only
should have for the
the SSH Server deployment of
disabled Veeam Data
Mover. For
security
purposes, after
adding the
hardened
repository to the
backup
infrastructure,
the SSH
connection
should be
disabled for the
user account
used to connect
to the Linux
server or for the
server itself.

S3 Object Lock Immutable object storage repositories added to the The Compliance
in the Veeam Backup & Replication console use the Compliance retention retention mode
Governance mode. should be used
mode does not for object storage
provide true repositories with
immutability immutability
enabled. This is a
more secure
option compared
to the
Governance
retention mode.
For more
information
about
immutability for
object storage
repositories, see
this section. For
more information
about retentions
modes, see this
Amazon article.

174 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Check Condition Notes

Backup jobs to In the backup job settings, if the cloud repository is selected as a To reduce the
cloud backup repository, the E na ble backup file encryption check box is also cloud attack
repositories selected. surface, job-level
should use encryption
encryption should be
enabled. For
more
information, see
Storage Settings.

Latest product In the Op tions > Notifications window, the Check for product and Veeam Backup &
updates hy p ervisor updates periodically check box check box is selected. Replication
should be should be
installed updated
regularly. Major
releases and
cumulative
patches usually
contain bug fixes,
performance
enhancements,
and new
features.

If you set up parameters as recommended, click Ana lyze to perform a security check again and ensure that the
status changed to Passed .

TIP

To implement Security & Compliance recommendations, you can use the automatic configuration script
provided by Veeam. For more information, see this KB article.

Excluding Parameters from Checklist


You can skip security check for specific parameters. For example, if you use Remote Desktop Service to connect
to Veeam Backup & Replication and do not need to disable it, exclude this parameter from the checklist. To do
this, perform the following steps:

1. Select a parameter and click Sup press.

2. [Optional] Leave a comment in the Note field.

3. Click OK.

175 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Excluded parameters are displayed in the Sup pressed section. To restore default settings for the selected
parameter and return it to the checklist, click Reset. If you want to return all excluded parameters to the
checklist, click Reset All.

Scan Scheduling
To set up daily scan scheduling, do the following:

1. Click Schedule.

2. Select the Sca n the backup infrastructure daily at check box and set up the time.

3. If you want to receive scan results by email, select the Send scan results to the following recipients check
box and specify one or several email addresses separated with a semicolon. You can use global notification
settings or specify custom notification settings as required.

4. Click OK.

176 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Malware Detection
Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), you can use built-in or third-party malware
detection methods to scan backup data and get information about suspicious activity or infected objects. The
functionality includes:

• Detecting malware activity in guest indexing data and data stream

• Scan backup

• Performing YARA scan during secure restore

• Integration with third-party malware protection solutions through Veeam Incident API

• Viewing malware detection events

• Receiving daily and immediate reports about malware detection events

• Managing malware status of the machines marked as Suspicious or Infected

• Marking specific restore points as Infected or Clean

Requirements and Limitations


Malware detection has the following requirements and limitations:

• Full malware detection support is included only in the Veeam Data Platform Advanced or Premium
License. Managing the malware status of specific restore points is available for all licenses. For more
details about licensing all malware detection features, see Veeam Data Platform Feature Comparison.

• Only users with the Veeam Backup Administrator role have full access to the functionality. Users with
other roles can view malware detection events and machines marked as Suspicious or Infected .

177 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Malware Detection Works
Malware detection is managed by the Veeam Data Analyzer Service. The service re starts once a day at 12:00 AM
and starts a new malware detection session. During the session, the Veeam Data Analyzer Service performs the
following operations:

• Checks updates for the list of malware signatures. For more information, see Updating Database of
Malware Signatures.

• Sends email notification about all malware detection events that were created within the last 24 hours.
For more information, see Notifications.

• Initiates a scan session using a specific malware detection method if there are new backup data that need
to be scanned. If there are no any, the service waits for a new data to appear.

If a malware activity detected, the Veeam Data Analyzer Service does the following:

1. Creates a malware detection event.

2. Marks the machine and the restore point where the malware activity was detected for the first time as
Suspicious or Infected .

NOTE

All next restore points created by the original backup job and any additional jobs (backup copy job, backup
to tape job, and so on) that include the scanned machine will also be marked as Suspicious or Infected until
the machine is marked as clean. For more information, see Managing Malware Status.

The malware status of machines and restore points is displayed only in the Veeam Backup & Replication
console. If you perform restore operations using standalone applications, for example, Veeam Agent for
Microsoft Windows, information about the malware status will not be available.

Information about malware detection sessions is displayed in the History view under the Ma lware Detection
node. The Ma lware Detection > Malware Events subnode displays events created as a result of the following
operations:

• Performing a backup job with the guest indexing data scan

• Performing a backup job with the inline scan

• Performing a Scan Backup job

• Performing a restore session with the Secure Restore option

• Sending Veeam Incident API requests

NOTE

The Activity date column displays the creation date and time of the restore point where the malware
activity was detected for the first time.

178 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
179 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Malware Detection Methods
Veeam Backup & Replication supports the following malware detection methods:

Ma lware detection Sca n objects Notes


method

Signature-based Guest indexing data During the backup job, detects the following malware
detection activity:
• Malware signatures
• Renamed files
• Deleted files

Marks objects as Suspicious.

For more information, see Guest Indexing Data Scan.

File entropy Blocks in a data stream During the backup job, detects the following malware
analysis activity:
• Encrypted files
• Onion links
• Ransom notes

Marks objects as Suspicious.

For more information, see Inline Scan.

Rule-based Restore points During the Scan Backup job, does one of the following:
detection (YARA)
• Finds the last clean restore point
• Analyzes the content for specific information

During the restore session with the Secure Restore


option, detects malware activity as specified in the YARA
rule.

Marks objects as Infected .

For more information, see Scan Backup and Secure


Restore.

Antivirus scan Restore points During the Scan Backup job, finds the last clean restore
point.

During the restore session with the Secure Restore


option, detects malware activity as specified in the
antivirus configuration file.

Marks objects as Infected .

For more information, see Scan Backup and Secure


Restore.

180 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ma lware detection Sca n objects Notes
method

Third-party Depends on the Uses Veeam Incident API to send a request about
malware configuration of the detected malware activity to
protection malware protection Veeam Backup & Replication.
solution solution
Marks objects as Infected .

For more information, see Veeam Backup & Replication


REST API Reference.

Guest Indexing Data Scan


To scan guest indexing data, Veeam Backup & Replication uses a signature-based approach. During the backup
job, the following malware activity can be detected:

• Malware signatures specified in the SuspiciousFiles.xml file. The file is located on the backup server
in the Veeam Backup & Replication product folder. The path by default: C:\Program
Files\Veeam\Backup and Replication\Backup\SuspiciousFiles.xml.

NOTE

Do not edit the SuspiciousFiles.xml directly. If you want to customize the list of malware
signatures, you can do it in the malware detection settings. For more information, se e Customizing
Malware Signatures.

• Multiple files renamed by malware. A malware detection event will be created if the following conditions
are met:

o There must be at least 200 renamed files with the same or different extensions.

o These extensions are not specified in the SuspiciousFiles.xml file.

• Multiple files deleted by malware. A malware detection event will be created if at least 25 files with
specific extensions or 50% of files with specific extensions are deleted.

NOTE

Detection of "sleeping" malware is not supported by this method.

Supported Scenarios
You can scan guest indexing data when backing up the following machines:

• VMware VMs including VMware Cloud Director VMs

• Hyper-V VMs

• Machines with Veeam Agent for Microsoft Windows operating in the managed mode (image -level and
volume-level backup)

• Machines with Veeam Agent for Microsoft Windows operating in the standalone mode

181 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How It Works
For guest indexing data, malware detection works in the following way:

o When the backup job with enabled guest file system indexing is complete and indexing data is saved in
the VBRCatalog folder on the backup server, the Veeam Guest Catalog Service notifies the Veeam
Data Analyzer Service about new data that need to be scanned.

o The Veeam Data Analyzer Service checks last scan results in the GuestIndexAnalyzeState.xml file
located in the VBRCatalog folder and initiates a new scan session.

o The Veeam Data Analyzer Service compares scan session results with the list of malware signatures and
updates the GuestIndexAnalyzeState.xml file. If malware activity is detected, the service will
create a malware detection event and mark objects as Suspicious.

Locations of suspicious files are stored in malware detection logs. The path by default:
C:\ProgramData\Veeam\Backup\Malware_Detection_Logs.

NOTE

The scan session is also initiated in the following situations:

o If the Veeam Data Analyzer Service gets new indexing data after the service starts.
o If you disable guest indexing data scan for some period of time and enable it again. Indexing data
created during this time will be scanned.
o If you import backups with the enabled Import guest file system index data to the catalog check
box.

If you upgrade to Veeam Backup & Replication 12.1 (build 12.1.0.2131), old indexing data will not be
scanned.

Configuring Guest Indexing Data Scan


To enable the guest indexing data scan, do the following:

o From the main menu, select Ma lware Detection > General.

o In the Suspicious activity detection field, select the E na ble file system activity analysis check box.

NOTE

This functionality is enabled by default when you install or upgrade to Veeam Backup & Replication
12.1 (build 12.1.0.2131).

182 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Make sure that you enable guest file system indexing for the necessary backup job. For more
information, see Specify Guest Processing Settings.

Updating Database of Malware Signatures


To keep the database of malware signatures up-to-date, select the Up date malware definitions automatically
check box. If the option is enabled, Veeam Backup & Replication will communicate with the Veeam Update
Server (vbr.butler.veeam.com) daily and download the latest version of the database file in the XML
format. The Veeam Data Analyzer service checks for the database updates once a day at 12:00 AM.

NOTE

If your backup server has limited internet access, you can update the database of malware signatures
manually. For more information, see this Veeam KB article.

Customizing Malware Signatures


To customize the list of malware signatures, perform the following steps:

1. From the main menu, select Ma lware Detection > General and click File masks to monitor.

2. To add a malware signature that should be marked as suspicious, do the following:

a. In the Suspicious files window, click Ad d .

b. Specify a file extension or a file name with or without extension. You can also use * and ? wildcard
characters. For example:

bot.txt
bot
b?t
*.avi

NOTE

Malware detection scan is case-insensitive. You do not need to add extensions or file names with
different cases, for example, bot and Bot.

c. Click OK.

183 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. To add a malware signature that should be skipped during the scan session, do the following:

a. In the Trusted files window, click Ad d .

b. Specify a malware signature as it is listed in the SuspiciousFiles.xml file (the FileMask tag).
For example:

*.cryptoboss

c. Click OK.

You can also export and import the list of additional or trusted signatures to/from a file in the XML format.

Inline Scan
To scan blocks in a data stream, Veeam Backup & Replication uses file entropy analysis. During the backup job,
the following malware activity can be detected:

• Files encrypted by malware. A malware detection event will be created if the amount of encrypted data
exceeds scan sensitivity limits.

• Text artifacts created by malware:

o V3 onion addresses that consist of 56 symbols in the [a-z2-7]{56}.onion format. For example,
vykenniek4sagugiayj3z32rpyrinoadduprjtdy4wharue6cz7zudid.onion. A malware detection event
will be created if at least one onion address is found.

o Ransomware notes created by Medusa and Clop. A malware detection event will be created if at
least one ransomware note is found.

NOTE

This functionality is disabled by default when you install or upgrade to Veeam Backup & Replication 12.1
(build 12.1.0.2131). If you want to use it, consider that the inline scan may consume a large amount of
system resources.

184 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Supported Scenarios
You can scan blocks in a data stream when backing up the following machines:

• VMware VMs including VMware Cloud Director VMs

• Hyper-V VMs

• Machines with Veeam Agent for Microsoft Windows operating in the managed mode (volume -level
backup only)

How It Works
For inline scan, malware detection works in the following way:

o During the backup job, Veeam Backup & Replication analyzes data blocks metadata and saves
ransomware data in the temporary folder on the backup proxy. A file in the RIDX format is created for
each disk and contains the following information:

o Disk metadata (disk name, creation time, disk size, used size, sector size, partition table)

o Ransomware data for each data block (the amount of encrypted files and files with different types,
the amount of onion addresses and ransomware notes)

NOTE

If LZMA headers are found, they will be excluded from encrypted data calculation to decrease
the number of false positive events.

o When the backup job is complete, ransomware data is saved in the VBRCatalog folder on the backup
server. The Veeam Guest Catalog Service notifies the Veeam Data Analyzer Service about new data that
need to be scanned.

o The Veeam Data Analyzer Service checks last scan results in the
RansomwareIndexAnalyzeState.xml file located in the VBRCatalog folder and initiates a new
scan session.

The scan session is also initiated if the Veeam Data Analyzer Service gets new indexing data after the
service starts.

4. The Veeam Data Analyzer Service compares the last and previous RIDX files and updates the
RansomwareIndexAnalyzeState.xml file. If malware activity is detected, the service will create a
malware detection event and mark objects as Suspicious.

If the previous RIDX file is not found, the Veeam Data Analyzer Service will perform a ful l disk read
operation to create a RIDX file. In this case, the job session will last longer than usual but the size of the
incremental backup file will not be affected.

A full disk read operation will also be performed if you add a new disk to the VM.

NOTE

The first RIDX file is used as a source for the first scan session and will not be analyzed after creation.

185 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
The inline scan has the following requirements and limitations:

• Scanning is supported only for simple volumes and for the following file systems: NTFS, ext4, ext3,
ext2.

• Scanning dynamic disks and disks encrypted by BitLocker is not supported.

• Text artifacts will be detected only if the following conditions are met:

o The block size of the file system is 4 KB.

o The size of the text file is not less than 4 KB.

o Text file has the UTF-8 encoding.

o Text file is not stored in the Master File Table (MFT).

• Detection of "sleeping" malware is not supported.

• Some file types may be unintentionally marked as suspicious during inline scan, for example, Linux
packages with LZMA compression, files encrypted with Windows EFS, specific ISO files, and so on. If you
have such files, you can mark related malware detection events as false-positive. For more information,
see Managing Malware Status.

Configuring Inline Scan


To enable inline scan, do the following:

• From the main menu, select Ma lware Detection > General.

• In the E ncryption detection field, select the E na ble inline entropy analysis check box.

• Specify the scan sensitivity depending on your backup data and backup infrastructure capabilities. The
default value is Normal.

Scan Backup
To scan restore points, Veeam Backup & Replication uses a rule-based detection approach or antivirus software.
You can run the Scan Backup job to perform the following operations:

• Find the last clean restore point after a recent malware attack.

186 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Find the last clean restore point if the date of the malware attack is unknown.

• Find some specific information, for example, sensitive data.

How Scan Backup Works


For Scan Backup job, malware detection works in the following way:

1. Veeam Backup & Replication mounts disks of the machine that you plan to scan to the mount server.

2. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify antivirus or YARA configuration, or both, depending on your Scan Backup settings.

b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

3. If you search for the last clean restore point using antivirus software or YARA rule, consider the following:

a. If a clean restore point is found, the Scan Backup job will be finished with the Success status. The
malware detection event will not be created.

b. If a clean restore point is not found, the Scan Backup job will be finished with the Failed status. The
malware detection event will be created for each restore point. Objects will be marked as Infected .

4. If you check the restore point for sensitive data using YARA rule, consider the following:

a. If sensitive data is found, the Scan Backup job session will b e finished with the Failed status.

b. If sensitive data is not found, the Scan Backup job session will be finished with the Success status.

In both cases, the malware detection event will not be created.

By default, the mount server role is assigned to the backup server or a backup repository. However, you can
assign the mount server role to any 64-bit Microsoft Windows machine in your backup infrastructure. For
example, you may want to run the malware detection scan on a different server for security reasons. For more
information about mount server deployment and requirements, see Mount Server.

Configuring Scan Backup Job


To run the Scan Backup job, do the following:

1. Open the Sca n Backup window by doing one of the following:

o Open the Inventory view and select the Ma lware Detection node. Select the required machine and
click Sca n Backup on the ribbon. Alternatively, right-click the machine and select Sca n backup.

o Open the Home view and select the Ba ck ups node. Select the job and required machine, and click Scan
Ba ckup on the ribbon. Alternatively, right-click the machine and select Sca n backup.

2. Specify the scan mode you want to use:

o Find the last clean restore point.

o Find the last clean restore point in range.

o Scan content of all restore points in range.

187 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Specify the scan engine you want to use:

o To use antivirus software as a scan engine, select the Sca n restore points with an antivirus engine
check box. For more information, see Antivirus Scan for Scan Backup.

o To use a YARA rule as a scan engine, select the Sca n restore points with the following YARA rule
check box and specify the YARA file located in the Veeam Backup & Replication product folder. For
more information, see YARA Scan for Scan Backup.

o To use scan engines simultaneously, select both check boxes.

4. Configure the scan range. You can specify the following options:

o Scan all restore points, from most recent restore point to the oldest one.

o Scan restore points created during a specific time period.

If you want to continue the Scan Backup job after the first malware or the first piece of specific
information is found, select the Continue scanning all remaining files after the first occu rence check box.

5. Click OK.

Antivirus Scan for Scan Backup


For Scan Backup job, you can run the antivirus scan session to find the last clean restore point.

To perform antivirus scan during the Scan Backup job, select the Sca n restored points with an antivirus engine
check box in the Sca n Backup window.

Consider the following:

• The antivirus software must be installed on the mount server and support the command line interface
(CLI).

• The antivirus configuration file must be located on the mount server and properly configured. For details,
see Antivirus XML Configuration File.

• If you use ESET NOD32 Antivirus version 9 and earlier, the Continue scanning all remaining files after the
first occurence option will not affect the antivirus scan session. Even if this option is not selected, the
antivirus scan session will continue after the malware activity is detected

188 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Antivirus Scan Works

During the Scan Backup job, antivirus scan works in the following way:

1. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify if the antivirus is installed on the mount server and the AntivirusInfos.xml configuration
file is located in the %ProgramFiles%\Common Files\Veeam\Backup and
Replication\Mount Service folder. For more details, see Antivirus XML Configuration File.

If the antivirus is not installed or the configuration file is improperly configured,


Veeam Backup & Replication will not start the restore process. In the restore wizard, you will not be
able to pass the step with secure restore settings.

b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

2. If the antivirus does not find a clean restore point, the Scan Backup job will be finished with the Failed
status. The malware detection event will be created for each restore point. Objects will be marked as
Infected .
You can further access the restored machine or its disks in the isolated environment and clean the
infection.

3. If the antivirus finds a clean restore point, the Scan Backup job will be finished with the Success status.
The malware detection event will not be created.

Viewing Antivirus Scan Results


Results of the antivirus scan are available in the Scan Backup job statistics.

To view antivirus scan results, do one of the following:

• Open the Home view, in the inventory pane select La st 24 hours. In the working area, double-click the
necessary Scan Backup job. Alternatively, you can select the job and click Sta tistics on the ribbon or right-
click the job and select Sta tistics.

189 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the History view, in the inventory pane select Job s. In the working area, double-click the necessary
Scan Backup job. Alternatively, you can select the job and click Sta tistics on the ribbon or right-click the
job and select Sta tistics.

To view the detailed logging of the antivirus scan, click the Sca n Log button at the bottom of the window with
the Scan Backup job statistics. Veeam Backup & Replication will display the most recent logs in a file of 1 MB in
size.

Full logs of the scan are stored on the mount server in the following folder:
C:\ProgramData\Veeam\Backup\FLRSessions\Windows\FLR__<machinename>_\Antivirus.

YARA Scan for Scan Backup


For Scan Backup job, you can run the YARA scan session to perform the following operations:

• Find the last clean restore point.

• Analyze the content for specific information, for example, sensitive data.

To perform YARA scan during the Scan Backup job, do the following:

1. In the Sca n Backup window, enable the Sca n restore points with the following YARA rule option.

2. Specify the YARA file located in the Veeam Backup & Replication product folder. The path by default:
C:\Program Files\Veeam\Backup and Replication\Backup\YaraRules. The YARA file must
have the .yara or .yar extension.

For more information on how to create a YARA rule, see YARA documentation.

How YARA Scan Works

During the Scan Backup job, YARA scan works in the following way:

1. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify if the YARA file is located in the C:\Program Files\Veeam\Backup and


Replication\Backup\YaraRules folder.

190 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

2. If you search for the last clean restore point, consider the following:

a. If a clean restore point is found, the Scan Backup job will be finished with the Success status. The
malware detection event will not be created.

b. If a clean restore point is not found, the Scan Backup job will be finished with the Failed status. The
malware detection event will be created for each restore point. Objects will be marked as Infected .

If you do not want to create a malware detection event for a YARA rule, you can add a
SuppressMalwareDetectionNotification tag to the name of the rule. For example:

rule SearchFileHash : SuppressMalwareDetectionNotification

In this case, the malware detection event will not be created but the Scan Backup job will be finished
with the Warning status.

3. If you check the restore point for sensitive data, consider the following:

a. If sensitive data is found, the Scan Backup job session will be finished with the Failed status.

b. If sensitive data is not found, the Scan Backup job session will be finished with the Success status.

In both cases, the malware detection event will not be created.

Viewing YARA Scan Results


Results of the YARA scan are available in the Scan Backup job statistics.

To view YARA scan results, do one of the following:

• Open the Home view, in the inventory pane select La st 24 hours. In the working area, double-click the
necessary Scan Backup job. Alternatively, you can select the job and click Sta tistics on the ribbon or right-
click the job and select Sta tistics.

191 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the History view, in the inventory pane select Job s. In the working area, double-click the necessary
Scan Backup job. Alternatively, you can select the job and click Sta tistics on the ribbon or right-click the
job and select Sta tistics.

To view the detailed logging of the YARA scan, click the Sca n Log button at the bottom of the window with the
Scan Backup job statistics. Veeam Backup & Replication will display the most recent logs in a file of 1 MB in size.

Full logs of the scan are stored on the mount server in the following folder:
C:\ProgramData\Veeam\Backup\FLRSessions\Windows\FLR__<machinename>_\Antivirus.

Secure Restore
Secure restore allows you to scan restore points with antivirus software before restoring the machine to the
production environment. Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), you can also scan
restore points with YARA rules.

Secure restore is available for the following operations:

• Instant Recovery

• Instant Disk Recovery

• Entire VM Restore

• Restore to Microsoft Azure

• Restore to Amazon EC2

• Restore to Google Compute Engine

• Disk Export

• SureBackup

192 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Secure Restore Works
For secure restore, malware detection works in the following way:

1. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify antivirus or YARA configuration, or both, depending on your secure restore settings.

b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

2. If malware activity is not detected, Veeam Backup & Replication will restore the machine to the target
location. The malware detection event will not be created.

3. If malware activity is detected, Veeam Backup & Replication will perform the following steps:

a. Abort the restore process or restore the machine with restrictions depending on secure restore
settings.

b. Create the malware detection event and mark objects as Infected .

By default, the mount server role is assigned to the backup server or a backup repository. However, you can
assign the mount server role to any 64-bit Microsoft Windows machine in your backup infrastructure. For
example, you may want to run the malware detection scan on a different server for security reasons. For more
information about mount server deployment and requirements, see Mount Server.

TIP

You can also scan machines for malware regularly within a SureBackup job. For information on how to
enable the malware scan for a SureBackup job, see the Settings step of the SureBackup job wizard.

Requirements and Limitations


Secure restore has the following requirements and limitations:

• You can perform secure restore only for Microsoft Windows machines.

• Veeam Backup & Replication does not perform malware scan for disks or volumes that cannot be mounted
to the mount server. For example, Storage Spaces disks or ReFS volumes (if ReFS is not supported by the
mount server OS) are skipped from the scan and restored in a regular way.

Antivirus Scan for Secure Restore


To perform antivirus scan during restore session, enable the Sca n the restored point with an a ntivirus engine
option at the Secure Restore step of the restore wizard.

Antivirus scan has the following requirements and limitations:

• The antivirus software must be installed on the mount server and support the command line interface
(CLI).

• The antivirus configuration file must be located on the mount server and properly configured. For details,
see Antivirus XML Configuration File.

193 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you use ESET NOD32 Antivirus version 9 and earlier, the Continue scanning all remaining files after the
first occurence option will not affect the antivirus scan session. Even if this option is not selected, the
antivirus scan session will continue after the malware activity is detected.

How Antivirus Scan Works


During the restore session, antivirus scan works in the following way:

1. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify if the antivirus is installed on the mount server and the AntivirusInfos.xml configuration
file is located in the %ProgramFiles%\Common Files\Veeam\Backup and
Replication\Mount Service folder. For more details, see Antivirus XML Configuration File.

If the antivirus is not installed or the configuration file is improperly configured,


Veeam Backup & Replication will not start the restore process. In the restore wizard, you will not be
able to pass the step with secure restore settings.

b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

2. If the antivirus does not detect malware activity, Veeam Backup & Replication will restore the machine to
the target location. The malware detection event will not be created.

3. If the antivirus detects malware activity, Veeam Backup & Replication will perform the following steps:

a. Abort the restore process or restore the machine with restrictions depending on the following secure
restore settings:

▪ Disable the network adapter (NIC) on the restored machine.

▪ Connect the restored machine to a different Microsoft Azure virtual network.

▪ Change the AWS security group for the restored machine.

b. Create the malware detection event and mark objects as Infected .

You can further access the restored machine or its disks in the isolated environment and clean the infection.

194 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Antivirus XML Configuration File

The antivirus software that you plan to use for scanning backups is described in the AntivirusInfos.xml file.
Veeam Backup & Replication creates this configuration file on every machine with the mount server role and
stores the file in the %ProgramFiles%\Common Files\Veeam\Backup and Replication\Mount
Service folder.

During restore session, Veeam Backup & Replication reads settings from the configuration file and triggers the
antivirus to scan backup files. The settings in the file are already predefined for the following antivirus software:

• Symantec Protection Engine

• ESET

• Windows Defender

• Kaspersky Security 10 and 11

• Bitdefender Endpoint Security Tools

• [Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131)] SentinelOne

• [Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131)] Trellix

If you want to scan machine data with other antivirus software, you must add configuration for this software to
the AntivirusInfos.xml file. The configuration must contain the same elements and attributes as the
antiviruses supported out-of-the-box. Consider that the antivirus software must support the command line
interface (CLI).

NOTE

If you made changes to the antivirus configuration file, you do not need to restart Veeam services on the
backup server — Veeam Backup & Replication will perform the next malware scan with new settings.

XML File Structure


The XML file describing antivirus settings has the following structure:

195 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
<Antiviruses>
<!-- Symantec -->
<AntivirusInfo Name='Symantec' IsPortableSoftware='false' ExecutableFilePath=
'Veeam.Backup.Antivirus.Scan.exe' CommandLineParameters='/p:%Path%' RegPath='HK
EY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\symcscan' ServiceName='symcs
can' ThreatExistsRegEx='Threat\s+found' IsParallelScanAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No threats detected'>0</ExitCode>
<ExitCode Type='Error' Description='Invalid command line argument'>1</E
xitCode>
<ExitCode Type='Error' Description='Antivirus scan was completed with e
rrors'>2</ExitCode>
<ExitCode Type='Error' Description='Antivirus scan was canceled'>4</Exi
tCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>3</Ex
itCode>
</ExitCodes>
</AntivirusInfo>
<!-- Eset -->
<AntivirusInfo Name='Eset File Security' IsPortableSoftware='true' Executable
FilePath='%ProgramFiles%\ESET\ESET File Security\ecls.exe' CommandLineParameter
s='%Path% /clean-mode=None /no-symlink' RegPath='' ServiceName='' ThreatExistsR
egEx='threat\s*=\s*["&apos;](?!is OK["&apos;])[^"&apos;]+["&apos;]' IsParallelS
canAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No threats detected'>0</ExitCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>1</Ex
itCode>
<ExitCode Type='Warning' Description='Some files were not scanned'>10</
ExitCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>50</E
xitCode>
<ExitCode Type='Error' Description='Antivirus scan was completed with e
rrors'>100</ExitCode>
</ExitCodes>
</AntivirusInfo>
<AntivirusInfo Name='ESET Antivirus' IsPortableSoftware='true' ExecutableFile
Path='%ProgramFiles%\ESET\ESET Security\ecls.exe' CommandLineParameters='%Path%
/clean-mode=None /no-symlink' RegPath='' ServiceName='' ThreatExistsRegEx='thre
at\s*=\s*["&apos;](?!is OK["&apos;])[^"&apos;]+["&apos;]' IsParallelScanAvailab
le='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No threats detected'>0</ExitCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>1</Ex
itCode>
<ExitCode Type='Warning' Description='Some files were not scanned'>10</
ExitCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>50</E
xitCode>
<ExitCode Type='Error' Description='Antivirus scan was completed with e
rrors'>100</ExitCode>
</ExitCodes>
</AntivirusInfo>
<!-- Windows Defender -->
<AntivirusInfo Name='Windows Defender' IsPortableSoftware='false' ExecutableF
ilePath='%ProgramFiles%\Windows Defender\mpcmdrun.exe' CommandLineParameters='-
Scan -ScanType 3 -File %Path% -DisableRemediation -BootSectorScan' RegPath='HKE
Y_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend' ServiceName='WinDe
fend' ThreatExistsRegEx='Threat\s+information' IsParallelScanAvailable='false'>
<ExitCodes>

196 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
<ExitCode Type='Success' Description='No threats detected'>0</ExitCode>
<ExitCode Type='Error' Description='Antivirus scan was completed with e
rrors'>2</ExitCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>2</Ex
itCode>
</ExitCodes>
</AntivirusInfo>
<!-- Kaspersky Security -->
<AntivirusInfo Name='Kaspersky Security' IsPortableSoftware='false' Executabl
eFilePath='kavshell.exe' CommandLineParameters='scan %Path%' RegPath='HKEY_LOCA
L_MACHINE\SYSTEM\CurrentControlSet\services\KAVFS' ServiceName='kavfs' ThreatEx
istsRegEx='' IsParallelScanAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No threats detected'>0</ExitCode>
<ExitCode Type='Warning' Description='There were processing errors for
some files'>-82</ExitCode>
<ExitCode Type='Warning' Description='Some files were not scanned'>-83<
/ExitCode>
<ExitCode Type='Warning' Description='Some files were corrupted'>-84</E
xitCode>
<ExitCode Type='Error' Description='Operation timed out'>2</ExitCode>
<ExitCode Type='Error' Description='Antivirus scan was canceled'>1</Exi
tCode>
<ExitCode Type='Error' Description='Service process is not running'>-2<
/ExitCode>
<ExitCode Type='Error' Description='Access denied'>-3</ExitCode>
<ExitCode Type='Error' Description='Object not found'>-4</ExitCode>
<ExitCode Type='Error' Description='Invalid syntax'>-5</ExitCode>
<ExitCode Type='Error' Description='Invalid operation'>-6</ExitCode>
<ExitCode Type='Error' Description='Service does not exist'>-7</ExitCod
e>
<ExitCode Type='Error' Description='Service disabled'>-8</ExitCode>
<ExitCode Type='Error' Description='Service logon failure'>-9</ExitCode
>
<ExitCode Type='Error' Description='Unable to create file'>-10</ExitCod
e>
<ExitCode Type='Error' Description='Invalid command line argument'>-11<
/ExitCode>
<ExitCode Type='Error' Description='Invalid password'>-12</ExitCode>
<ExitCode Type='Error' Description='Cannot create report file'>-85</Exi
tCode>
<ExitCode Type='Error' Description='License is invalid'>-301</ExitCode>
<ExitCode Type='Error' Description='Antivirus bases are corrupted'>-236
</ExitCode>
<ExitCode Type='Infected' Description='Infected object was detected'>-8
0</ExitCode>
<ExitCode Type='Infected' Description='Possibly infected object was det
ected'>-81</ExitCode>
</ExitCodes>
</AntivirusInfo>
<!-- Bitdefender Endpoint Security Tools -->
<AntivirusInfo Name='Bitdefender Endpoint Security Tools' IsPortableSoftware=
'true' ExecutableFilePath='%ProgramFiles%\Bitdefender\Endpoint Security\product
.console.exe' CommandLineParameters= ' /c FileScan.OnDemand.RunScanTask custom
path=%Path%' RegPath='' ServiceName='' ThreatExistsRegEx='Remaining issues:\s[1
-9]\d*|Resolved issues:\s[1-9]\d*' IsParallelScanAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='Command executed successfully'>0<
/ExitCode>
<ExitCode Type='Error' Description='Invalid Parameter'>87</ExitCode>

197 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
<ExitCode Type='Error' Description='Bad Arguments'>160</ExitCode>
<ExitCode Type='Error' Description='Function Failed – an error occurred
while executing the command'>1627</ExitCode>
<ExitCode Type='Infected' Description='A threat was detected on the sys
tem'>-526</ExitCode>
</ExitCodes>
</AntivirusInfo>
<!-- SentinelOne -->
<AntivirusInfo Name='SentinelOne' IsPortableSoftware='false' ExecutableFilePa
th='%ProgramFiles%\SentinelOne\Sentinel Agent 22.1.4.10010\SentinelCtl.exe' Com
mandLineParameters='%Path% /clean-mode=None /no-symlink' RegPath='HKEY_LOCAL_MA
CHINE\SYSTEM\CurrentControlSet\Services\SentinelAgent' ServiceName='SentinelAge
nt' ThreatExistsRegEx='Threat\s+found' IsParallelScanAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No threats detected'>1639</ExitCo
de>
<ExitCode Type='Error' Description='Invalid command line argument'>1</E
xitCode>
<ExitCode Type='Error' Description='Antivirus scan was completed with e
rrors'>2</ExitCode>
<ExitCode Type='Error' Description='Antivirus scan was canceled'>4</Exi
tCode>
<ExitCode Type='Infected' Description='Virus threat was detected'>3</Ex
itCode>
</ExitCodes>
</AntivirusInfo>
<!-- Trellix -->
<AntivirusInfo Name='Trellix Command Line Scanner' IsPortableSoftware='true'
ExecutableFilePath='<local-path>\scan.exe' CommandLineParameters='%Path% /NOMEM
/ALL /SUB /PROGRAM /RECURSIVE /UNZIP /ANALYZE /MANALYZE /PANALYZE' RegPath='' S
erviceName='' ThreatExistsRegEx='Found' IsParallelScanAvailable='false'>
<ExitCodes>
<ExitCode Type='Success' Description='No viruses found'>0</ExitCode>
<ExitCode Type='Infected' Description='Virus found'>13</ExitCode>
<ExitCode Type='Infected' Description='Virus found in memory'>10</ExitC
ode>
<ExitCode Type='Error' Description='Self-integrity check failed'>15</Ex
itCode>
<ExitCode Type='Error' Description='DAT file not found'>8</ExitCode>
<ExitCode Type='Error' Description='There has been a problem with scan'
>6</ExitCode>
<ExitCode Type='Error' Description='DAT file integrity check failed'>2<
/ExitCode>
</ExitCodes>
</AntivirusInfo>
</Antiviruses>

The XML file contains the following elements:

• Antiviruses. The element encapsulates the file with antivirus settings.

• AntivirusInfo. The element describes the antivirus software.

• ExitCodes. The element encapsulates messages that Veeam Backup & Replication displays on scan results.

• ExitCode. The element describes the subject and the body of the message that
Veeam Backup & Replication displays on scan results.

198 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
AntivirusInfo
The element has the following attributes:

Attribute Description

Na me Specifies the antivirus name. Veeam Backup & Replication will display this name
in restore session logs.

IsP ortableSoftware Indicates if antivirus software is portable:

• If you set this attribute to True, Veeam Backup & Replication will treat
the antivirus software as portable. Before performing secure restore,
Veeam Backup & Replication will verify if the antivirus executable file
exists. The path to the file is specified by the ExecutableFilePath
attribute.
• If you set this attribute to False, Veeam Backup & Replication will treat
the antivirus software as non-portable. Before performing secure restore,
Veeam Backup & Replication will verify if the antivirus registry value exists
and if the antivirus service is running.
The key is specified by the RegPath attribute. The service name is
specified by the ServiceName attribute.

E x ecutableFilePath Specifies the path to the antivirus executable file.

CommandLineParameters Specifies antivirus commands that you want to execute during the scan. Make
sure that the antivirus supports the specified commands. For example, the list of
commands for ESET is available in this ESET KB article.

Note: The %Path% variable is required for this attribute. During secure restore,
Veeam Backup & Replication substitutes this variable for the path to the folder
with mounted disks (C:\VeeamFLR\<machinename>).

ServiceName Specifies the name of the antivirus service. The service must be responsible for
data scanning. The attribute value can be an empty string if IsP ortableSoftware =
True and E x ecutableFilePath is specified.

Reg Path Specifies the registry value of the anitivirus service. The attribute value can be an
empty string if IsP ortableSoftware = True and E x ecutableFilePath is specified.

ThreatExistsRegEx Specifies regular expressions. A regular expression is a sequence of characters


that form a search pattern. Veeam Backup & Replication will search the antivirus
output messages for the specified regular expression. If any of the output
messages match the expression, Veeam Backup & Replication will notify you on
detected threat.

Note: You must have a good understanding of the regular expression language
to specify this attribute properly. For more information on the regular expression
language, see Microsoft Docs.

199 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Attribute Description

IsParallelScanAvailable Indicates if the antivirus will run multiple jobs to scan files on mounted disks
simultaneously.

If you set this attribute to True, Veeam Backup & Replication will lock the
antivirus to perform the scan for the current restore session. The antivirus will
not be available for other sessions with enabled secure restore until the scan
completes.

The default value for antivirus lock time-out is 24 hours. If the scan does not
complete after this period, Veeam Backup & Replication will finish other restore
sessions as specified in the restore wizard: abort restore sessions or restore
machines with restrictions.

Note: You can change the lock time-out using registry values. For more
information, contact Veeam Support.

If the antivirus CLI does not support multiple scan jobs, set this attribute to
False.

ExitCode
The element has the following attributes:

Attribute Description

Ty p e Specifies the subject of the message that Veeam Backup & Replication will
display on scan results:
• Success

• Infected
• Warning

• Error

Description Specifies the body of the message that Veeam Backup & Replication will display
on scan results.

TIP

You can distribute the XML configuration file among other mount servers in your backup infrastructure
using Veeam PowerShell. For more information, see the Copy-VBRAntivirusConfigurationFile section in the
Veeam PowerShell Reference.

Viewing Antivirus Scan Results

Results of the antivirus scan are available in restore session statistics.

200 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To view restore session statistics, do one of the following :

• Open the Home view, in the inventory pane select La st 24 hours. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

• Open the History view, in the inventory pane select Restore. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

To view the detailed logging of the malware scan, click the Sca n Log button at the bottom of the window with
restore session statistics. Veeam Backup & Replication will display the most recent logs in a file of 1 MB in size.

Full logs of the scan are stored on the mount server in the following folder:
C:\ProgramData\Veeam\Backup\FLRSessions\Windows\FLR__<machinename>_\Antivirus.

YARA Scan for Secure Restore


To perform YARA scan during restore session, do the following at the Secure Restore step of the restore wizard:

1. Enable the Sca n restore points with the following YARA rule option.

2. Specify the YARA file located in the Veeam Backup & Replication product folder. The path by default:
C:\Program Files\Veeam\Backup and Replication\Backup\YaraRules. The YARA file must
have the .yara or .yar extension.

For more information on how to create a YARA rule, see YARA documentation.

How YARA Scan Works


During the secure restore, YARA scan works in the following way:

1. On the mount server, Veeam Backup & Replication runs the Veeam Mount Service to perform the
following steps:

a. Verify if the YARA file is located in the C:\Program Files\Veeam\Backup and


Replication\Backup\YaraRules folder.

b. Mount machine disks from backups to the mount server under the C:\VeeamFLR\<machinename>
folder.

c. Initiate a new scan session.

201 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. If malware activity is not detected, Veeam Backup & Replication will restore the machine to the target
location. The malware detection event will not be created.

3. If malware activity is detected, Veeam Backup & Replication will perform the following steps:

a. Abort the restore process or restore the machine with restrictions depending on the following secure
restore settings:

▪ Disable the network adapter (NIC) on the restored machine.

▪ Connect the restored machine to a different Microsoft Azure virtual network.

▪ Change the AWS security group for the restored machine.

b. Create the malware detection event and mark objects as Infected .

If you do not want to create a malware detection event for a YARA rule, you can add a
SuppressMalwareDetectionNotification tag to the name of the rule. For example:

rule SearchFileHash : SuppressMalwareDetectionNotification

In this case, the malware detection event will not be created but the restore job will be finished with
the Warning status.

You can further access the restored machine or its disks in the isolated environment and clean the infection.

Viewing YARA Scan Results

Results of the YARA scan are available in restore session statistics.

To view restore session statistics, do one of the following:

• Open the Home view, in the inventory pane select La st 24 hours. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

• Open the History view, in the inventory pane select Restore. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

To view the detailed logging of the YARA scan, click the Sca n Log button at the bottom of the window with
restore session statistics. Veeam Backup & Replication will display the most recent logs in a file of 1 MB in size.

202 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Full logs of the scan are stored on the mount server in the following folder:
C:\ProgramData\Veeam\Backup\FLRSessions\Windows\FLR__<machinename>_\Antivirus.

203 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Malware Detection
This section describes malware detection settings.

General Settings
In the General tab, you can configure malware detection settings for guest indexing data and inline scan. For
more information, see the following sections:

• Configuring Guest Indexing Data Scan

• Configuring Inline Scan

Veeam Incident API


You can run quick backup when Veeam Backup & Replication gets a Veeam Incident API response that triggers a
malware detection event. To do this, perform the following steps:

1. From the main menu, select Ma lware Detection > Incident API.

2. Select the P erform a Quick Backup upon receiving an external event check box.

NOTE

If there are several machines with malware detection events triggered by Veeam Incident API, quick backup
will process these machines one by one.

For more information about quick backup, see Quick Backup. For more information about Incident API methods,
see Veeam Backup & Replication REST API Reference.

Notifications
You can receive SNMP traps or email notifications about created malware detection events. To do this, perform
the following steps:

1. From the main menu, select Ma lware Detection > Notifications.

2. If you want to receive SNMP traps, select the Send SNMP notifications for d etected malware check box.
For more information, see Configuring Global SNMP Settings.

204 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. If you want to receive email notifications, select the Send email notifications to the following recipients
check box and specify one or several email addresses separated with a semicolon. You can use global
notification settings or specify custom notification settings as required. For more information, see
Configuring Global Email Notification Settings.

Veeam Backup & Replication sends the following email notifications:

o Daily report is sent when the Veeam Data Analyzer Service restarts the malware detection session
(once a day at 12:00 AM) or when you restart the service manually. The report contains consolidated
data about all malware detection events that were created within the last 24 hours.

o Immediate report is sent each time a malware detection event is created. If several events were
created in 10 seconds, one report with consolidated data will be sent.

Malware Exclusions
To exclude specific machines from the malware detection scan, perform the following steps:

1. Open the Ma lware Detection Exclusions window by doing one of the following:

a. From the main menu, select Global Exclusion > Malware Exclusions.

b. Open the Inventory view, select the Ma lware Detection node, and click E x clusions on the ribbon.

2. Click Ad d and select Hy p er-V VMs or P hy sical and cloud machines.

3. Select the object from the list and click Ad d .

4. Click Note to provide a description for future reference.

5. Click OK.

You can also add the machine to the exclusions list when you mark it as clea n. For more information, see
Managing Infected Machines.

NOTE

Malware exclusions are applied only to guest indexing data scan and inline scan and do not affect antivirus
scan or YARA scan.

205 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
206 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Malware Status
Veeam Backup & Replication allows you to manage the malware status of machines and specific restore points.

Marking Machines as Clean


All machines marked by malware detection as suspicious or infected can be found in the Inventory view under
the Ma lware Detection node.

If you cleaned the machine from malware or the malware detection event was false positive, you can mark the
machine as clean. To do this, perform the following steps:

1. Right-click one or more machines and select Ma rk as clean. Alternatively, click Ma rk as Clean on the
ribbon.

2. If machines was cleaned from malware, specify the reason and click Y es . The malware status of the
machine will be automatically updated. Previous restore points will be left with the Suspicious or Infected
status. All next restore points will not be marked as suspicious or infected.

3. If the malware detection event was false positive, specify the reason, select the Ma rk restore points
a ffected by corresponding detection events as clean check box, and click Y es . The malware status of the
machine will be automatically updated. Previous restore points will be marked as clean. Next restore
points will not be marked as suspicious or infected.

If you want to disable next malware detection scans for machines that you mark as clean, select the E x clude the
work load from malware detection check box. The machines will be added to the exclusions list. For more
information, see Malware Exclusions.

Managing Malware Status of Specific Restore Points


If you know that a specific machine is infected but the malware detection scan did not detect any suspicious
activity, you can manually change the malware status of the specific restore point. To do this, perform the
following steps:

1. Open the Home view and navigate to the Ba ckups node.

2. Right-click the job name and select P roperties.

3. [Optional] If all backup data is backed up to a single storage and you want to change the malware status
of the specific restore point for a specific machine, select the machine in the Ob jects window.

207 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Files window, right-click the restore point and select Ma lware > Mark as infected.

If you know that a specific restore point is not infected, you can manually change the malware status of the
specific restore point. To do this, perform the following steps:

1. Open the Home view and navigate to the Ba ckups node.

2. Right-click the job name and select P roperties.

3. [Optional] If all backup data is backed up to a single storage and you want to change the malware status
of the specific restore point for a specific machine, select the machine in the Ob jects window.

4. In the Files window, right-click the restore point and select Ma lware > Mark as clean.

208 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you set the malware status of the restore point manually, it will have a higher priority. The result of the
malware detection scan will not affect the malware status of this restore point even if the malware
detection event is created.

209 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Trusted Root Certificates
There are several root certificates necessary for the Veeam Backup & Replication to operate correctly.

In most cases, these certificates are already installed on Microsoft Windows machines. Some Micros oft Windows
installations do not contain needed root certificates authority as trusted root certificates, or have non-current
certificates. This may happen on servers with locked down security settings, or servers with no internet access
or if the latest updates are not installed.

Removal of these certificates from the backup server may limit the functionality of Veeam Backup & Replication
or may cause it to fail.

Make sure the following root certificates are installed on the backup server:

• https://www.digicert.com/CACerts/DigiCertAssuredIDRootCA.crt (DigiCert Assured ID Root CA)

• http://secure.globalsign.com/cacert/gscodesigng3ocsp.crt (GlobalSign CodeSigning CA - G3)

• https://www.digicert.com/CACerts/DigiCertHighAssuranceEVRootCA.crt (DigiCert High Assurance EV Root


CA)

• https://www.digicert.com/CACerts/DigiCertEVCodeSigningCA -SHA2.crt (DigiCert EV Code Signing CA -


SHA2)

• https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates (install R1
and R3 certificates)

If your backup server does not have internet access, download certificate files from another computer.

210 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Encryption
Data security is an important part of the backup strategy. You must protect your information from unauthorized
access, especially if you back up sensitive VM data to off-site locations or archive it to tape. To keep your data
safe, you can use data encryption.

Data encryption transforms data to an unreadable, scrambled format with the help of a cryptographic algorithm
and a secret key. If encrypted data is intercepted, it cannot be unlocked and read by the eavesdropper. Only
intended recipients who know the secret key can reverse encrypted information back to a readable format.

In Veeam Backup & Replication, encryption works at the following levels:

• Backup job

• Transaction log backup job

• Backup copy job

• VeeamZIP

• Tapes in media pools

Veeam Backup & Replication uses the block cipher encryption algorithm. Encryption works at the source side.
Veeam Backup & Replication reads VM or file data, encodes data blocks, transfers them to the target side in the
encrypted format and stores the data to a file in the backup repository or archives the data to tape. Data
decryption is also performed on the source side: Veeam Backup & Replication transfers encrypted data back to
the source side and decrypts it there.

NOTE

Veeam Backup & Replication will pass encryption keys to the target backup repository or cloud repository
in the following cases:

• If you run a backup copy job over WAN accelerators


• If you perform health check for the encrypted backup files

Data Encryption and Deduplication


Data encryption has a negative effect on the deduplication ratio if you use a deduplicating storage appliance as a
target. Veeam Backup & Replication uses different encryption keys for every job session. For this reason,
encrypted data blocks sent to the deduplicating storage appliances appear as different though they may contain
duplicate data. If you want to achieve a higher deduplication ratio, you can disable data encryption. If you still
want to use encryption, you can enable the encryption feature on the deduplicating storage appliance itself.

211 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Encryption and Compression
If data compression and data encryption are enabled for a job, Veeam Backup & Replication compresses VM data
first and after that encrypts the compressed data blocks. Both operations are performed at the source side.

Note, however, that if the Decompress backup data blocks before storing check box is selected in the backup
repository settings, Veeam Backup & Replication does not compress VM data before encryption. Therefore, in
the job statistics, you may observe a higher amount of transferred data (the Tra nsferred counter) as compared
to a job for which encryption is disabled. For details on job statistics, see Viewing Real-Time Statistics.

212 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encryption Standards
Veeam Backup & Replication uses the following industry-standard data encryption algorithms:

Data Encryption
For data encryption consider the following:

• To encrypt data blocks in backup files, Veeam Backup & Replication uses the 256-bit AES with a 256-bit
key length in the CBC-mode. For more information, see Advanced Encryption Standard (AES). This type of
encryption is also supported for backup files stored in the following locations:

o Backup files archived to tape devices. For more information, see the Tape Devices Support Guide.

o Backup files stored in archive tier. For more information, see Archive Tier.

o Backup files stored in capacity tier. For more information, see Capacity Tier.

• To generate a key based on a password, Veeam Backup & Replication uses the Password-Based Key
Derivation Function, PKCS #5 version 2.0. Veeam Backup & Replication uses 10,000 HMAC-SHA1
iterations and a 512-bit salt. For more information, see Recommendation for Password-Based Key
Derivation.

Enterprise Manager Keys


For Veeam Backup Enterprise Manager consider the following:

• To generate Enterprise Manager keys required for data restore without a password,
Veeam Backup & Replication uses the RSA algorithm with a 4096-bit key length.

• To generate a request for data restore from a backup server, Veeam Backup & Replication uses the RSA
algorithm with a 2048-bit key length.

For more information, see RSA Cryptography Specifications.

Hashing Algorithms
Veeam Backup & Replication uses the following hashing algorithms:

• For digital signature generation: SHA-256

• For SSH fingerprint verification: SHA-256

• For backward compatibility and certificate thumbprint generation: SHA-1

• For HMAC generation: SHA-1

• For random number generation: OpenSSL, cryptographic libraries provided by the operating system

Encryption Libraries
For Linux-based components and services, Veeam Backup & Replication uses Veeam Cryptographic Module.

For Veeam Data Movers installed on Microsoft Windows-based machines, Veeam Backup & Replication also uses
Veeam Cryptographic Module. For other Microsoft Windows-based components and services,
Veeam Backup & Replication uses Microsoft Crypto API.

213 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication uses the following cryptographic service providers:

• Microsoft Base Cryptographic Provider. For more information, see Microsoft Docs.

• Microsoft Enhanced RSA and AES Cryptographic Provider. For more information, see Microsoft Docs.

• Microsoft Enhanced Cryptographic Provider. For more information, see Microsoft Docs.

If you need Veeam Cryptographic Module and Microsoft Crypto API to be compliant with the Federal
Information Processing Standards (FIPS 140), enable FIPS compliance as described in section FIPS Compliance.

Veeam Backup & Replication encrypts stored credentials using the Data Protection API (DPAPI) mechanisms. For
more information, see Microsoft Docs.

214 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encryption Algorithms
To encrypt data in backups and files, Veeam Backup & Replication employs a symmetric key encryption
algorithm.

The symmetric, or single-key encryption algorithm, uses a single, common secret key to encrypt and decrypt
data. Before data is sent to target side, it is encoded with a secret key. To restore encrypted data, you must have
the same secret key. Users who do not have the secret key cannot decrypt data and get access to it.

Veeam Backup & Replication relies on a hierarchical encryption scheme. Each layer in the hierarchy encrypts the
layer below with a key of specific type.

215 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encryption Keys
An encryption key is a string of random characters that is used to bring data to a scrambled format and back to
unscrambled. Encryption keys encode and decode initial data blocks or underlying keys in the key hierarchy.

Veeam Backup & Replication uses the following types of keys:

• Service keys generated by Veeam Backup & Replication:

o Session key

o Metakey

o Storage key

• User key — a key generated using a user password.

• Enterprise Manager keys — a pair of keys used for data recovery without a password.

• Backup server keys — a pair of keys used for identity verification of the backup server.

Session Keys and Metakeys


The session key is the lowest layer in the encryption key hierarchy. When Veeam Backup & Replication encrypts
data, it first encodes every data block in a file with a session key. For session keys, Veeam Backup & Replication
uses the AES algorithm with a 256-bit key length in the CBC-mode.

Veeam Backup & Replication generates a new session key for every job session. For example, if you have created
an encrypted backup job and run 3 job sessions, Veeam Backup & Replication will produce 3 backup files that
will be encrypted with 3 different session keys:

• Full backup file encrypted with session key 1

• Incremental backup file encrypted with session key 2

• Incremental backup file encrypted with session key 3

The session key is used to encrypt only data blocks in backup files or files archived to tape. To encrypt backup
metadata, Veeam Backup & Replication applies a separate key — metakey. Use of a metakey for metadata raises
the security level of encrypted backups.

For every job session, Veeam Backup & Replication generates a new metakey. For example, if you have run 3 job
sessions, Veeam Backup & Replication will encrypt metadata with 3 metakeys.

216 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
In the encryption process, session keys and metakeys are encrypted with keys of a higher layer — storage keys.
Cryptograms of session keys and metakeys are stored to the resulting file next to encrypted data blocks.
Metakeys are additionally kept in the configuration da tabase.

Storage Keys
Backup files in the backup chain often need to be transformed, for example, in case you create a reverse
incremental backup chain. When Veeam Backup & Replication transforms a full backup file, it writes data blocks
from several restore points to the full backup file. As a result, the full backup file contains data blocks that are
encrypted in different job sessions with different session keys.

To restore data from such “composed” backup file, Veeam Backup & Replication requires a bunch of session
keys. For example, if the backup chain contains restore points for 2 months, Veeam Backup & Replication will
have to keep session keys for a 2-month period.

In such situation, storing and handling session keys will be resource consuming and complicated. To facilitate
the encryption process, Veeam Backup & Replication introduces another type of service key — a storage key.

For storage keys, Veeam Backup & Replication uses the AES algorithm. A storage key is directly associated with
one restore point in the backup chain. The storage key is used to encrypt the following keys in the encryption
hierarchy:

• All session keys for all data blocks in one restore point

• Metakey encrypting backup metadata

During the restore process, Veeam Backup & Replication uses one storage key to decrypt all session keys for one
restore point, no matter how many session keys were used to encrypt data blocks in this restore point. As a
result, Veeam Backup & Replication does not need to keep the session keys history in the configuration
database. Instead, it requires only one storage key to restore data from one file.

In the encryption process, storage keys are encrypted with keys of a higher layer — user keys and optionally a
public Enterprise Manager key. Cryptograms of storage keys are stored to the resulting file next to encrypted
data blocks, and cryptograms of session keys and metakeys.

Storage keys are also kept in the configuration database. To maintain a set of valid storage keys in the datab ase,
Veeam Backup & Replication uses retention policy settings specified for the job. When some restore point is
removed from the backup chain by retention, this restore point's storage key is also removed from the
configuration database.

217 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
User Keys
When you enable encryption for a job, you must define a password to protect data processed by this job, and
define a hint for the password. The password and the hint are saved in the job settings. Based on this password,
Veeam Backup & Replication generates a user key.

The user key protects data at the job level. In the encryption hierarchy, the user key encrypts storage keys for all
restore points in the backup chain.

During the encryption process, Veeam Backup & Replication saves a hint for the password to the encrypted file.
When you decrypt a file, Veeam Backup & Replication displays a hint for the password that you must provide.
After you enter a password, Veeam Backup & Replication derives a user key from the password and uses it to
unlock the storage key for the encrypted file.

According to the security best practices, you must change passwords for encrypted jobs regularly. When you
change a password for the job, Veeam Backup & Replication creates a new user key and uses it to encrypt new
restore points in the backup chain.

IMP ORTANT

You must always remember passwords set for jobs or save these passwords in a safe place. If you lose or
forget the password, you can restore data from a backup file by issuing a request to Veeam Backup
Enterprise Manager. For more information, see How Decryption Without Password Works.

Enterprise Manager Keys


In some cases, a password required for data decryption may be lost or forgotten, or a user who knows the
password may leave your organization. As a result, you cannot recover data from backups or tapes encrypted
with this password, and encrypted data becomes unusable.

Veeam Backup & Replication offers you a way to restore encrypted data even if you do not have a password. For
this purpose, Veeam Backup & Replication employs an additional pair of keys in the encryption process —
Enterprise Manager keys.

218 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Enterprise Manager keys is a pair of matching RSA keys: a public key and a private key. The public Enterprise
Manager key is used to encrypt data, while the private Enterprise Manager key is used to decrypt data encrypted
with the public key.

In the encryption process, Enterprise Manager keys perform a role similar to the user key: the public Enterprise
Manager key encrypts storage keys and the private Enterprise Manager key decrypts them. Technically,
Enterprise Manager keys offer an alternative to the user key. When you create an encrypted backup file or
archive encrypted data to tape, Veeam Backup & Replication encrypts storage keys with two types of keys
simultaneously:

• User key

• Public Enterprise Manager key

When you decrypt a file and the password is lost, Veeam Backup & Replication cannot derive the user key from
the password. In this situation, you can send a request to Veeam Backup Enterprise Manager. Veeam Backup
Enterprise Manager will employ the private Enterprise Manager key instead of the user key to unlock storage
keys and decrypt the file content. For more information, see How Decryption Without Password Works.

Enterprise Manager keys take part in the encryption process if the following two conditions are met:

1. If you are using a legacy socket-based license, Enterprise or higher edition is required. Note that
Enterprise Manager keys functionality is included in the Veeam Universal License.

2. You have Veeam Backup Enterprise Manager installed and your backup servers are connected to Veeam
Backup Enterprise Manager.

Enterprise Manager keys make up a pair of matching keys — a keyset. Enterprise Manager keysets are created
and managed on the Veeam Backup Enterprise Manager server. During installation of Veeam Backup Enterprise
Manager, the setup automatically generates a new keyset containing a public Enterprise Manager key and a
private Enterprise Manager key. You can use Veeam Backup Enterprise Manager to create new Enterp rise
Manager keysets, activate them, import and export keysets and specify retention for their lifetime.

219 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The public Enterprise Manager key is made publicly available to backup servers. When you connect backup
servers to Veeam Backup Enterprise Manager, the public Enterprise Manager key is automatically propagated to
these backup servers.

Veeam Backup Enterprise Manager acts as a manager for public Enterprise Manager keys but does not store
these keys. After the public Enterprise Manager key is propagated to the backup server, it is kept in the
configuration database.

Private Enterprise Manager keys, on the contrary, are not distributed anywhere: they are kept only on Veeam
Backup Enterprise Manager.

Backup Server Keys


Eavesdroppers may potentially use Veeam Backup Enterprise Manager to unlock files encrypted with
Veeam Backup & Replication. If eavesdroppers intercept an encrypted file, they may generate a request for file
unlocking and send such request to Veeam Backup Enterprise Manager Administrators. Hav ing received a
response from Veeam Backup Enterprise Manager, eavesdroppers will be able unlock the encrypted file without
a password.

To protect you against the “man-in-the-middle” attack, Veeam Backup & Replication uses backup server keys.
Backup server keys are a pair of RSA keys, public and private, that are generated on the backup server.

• The public backup server key is sent to Veeam Backup Enterprise Manager to which the backup server is
connected, and saved in the Veeam Backup Enterprise Manager configuration database.

• The private backup server key is kept on the backup server in the Veeam Backup & Replication
configuration database.

Backup server keys are used to authenticate the identity of the request sender. When the backup server
generates a request to unlock a file, it adds a signature encrypted with the private backup server key to this
request.

When Veeam Backup Enterprise Manager processes the request, it uses the public backup server key to decrypt
the signature and identify the request sender. If the backup server used for request generation is not added to
Veeam Backup Enterprise Manager, Veeam Backup Enterprise Manager will not find a matching public key in its
database. As a result, Veeam Backup Enterprise Manager will not be able to identify the sender and the storage
key decryption process will fail.

220 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encrypted Objects
The encryption algorithm works at the job level and media pool level. You can enable encryption for the
following objects:

• Backup job

• Backup copy job

• VeeamZIP

• Tape

Backup Job Encryption


Encryption for a backup job is configured in the advanced job settings. You should enable the encryption option
and specify a password to protect data in backup files produced by the backup job.

The backup job processing with encryption enabled includes the following steps:

1. You enable encryption for a backup job and specify a password.

2. Veeam Backup & Replication generates the necessary keys to protect backup data.

3. Veeam Backup & Replication encrypts data blocks in the backup proxy, either the dedicated or default
one, and transfers them to the backup repository already encrypted.

221 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. On the backup repository, encrypted data blocks are stored to a resulting backup file.

Restore of an encrypted backup file includes the following steps:

1. You import a backup file and define a password to decrypt the backup file. If the password has changed
once or several times, you need to specify the password in the following manner:

o If you select a metadata file (VBM) for import, you must specify the latest password that was used to
encrypt files in the backup chain.

o If you select a full backup file (VBK) for import, you must specify the whole set of passwords that
were used to encrypt files in the backup chain.

2. Veeam Backup & Replication uses the provided passwords to generate user keys and unlock the
subsequent keys for backup file decryption.

3. Veeam Backup & Replication retrieves data blocks from the backup file, sends them to the source side and
decrypts them on the backup proxy, either the dedicated or default one.

222 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Job Encryption
Encryption for a backup copy job is configured in the advanced job settings. You should enable the encryption
option and specify a password to protect data in backup files produced by the backup copy job.

The workflow of the encrypted backup copy job depends on the path for data transfer:

• Direct data path

• Over WAN accelerators

Direct Data Path


If you use a direct data path to transfer backups to the target backup repository, the encrypted backup copy job
includes the following steps:

1. You enable encryption for a backup copy job and specify a password.

2. Veeam Backup & Replication generates the necessary keys to protect backup files produced by the backup
copy job.

3. Veeam Backup & Replication encrypts data blocks on the source side and transfers them to the target
backup repository.

4. On the target backup repository, encrypted data blocks are stored to a resulting backup file.

223 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
An encrypted backup copy job may use an encrypted backup file as a source. In this situation,
Veeam Backup & Replication does not perform double encryption. The backup copy job includes the following
steps:

1. Veeam Backup & Replication decrypts data blocks of the encrypted source backup file. For the decryption
process, it uses the storage key and metakeys stored in the configuration database.

2. Veeam Backup & Replication generates the necessary keys to protect backup files produced by the backup
copy job.

3. Veeam Backup & Replication encrypts data blocks on the source side using these keys and transfers
encrypted data blocks to the target backup repository.

4. On the target backup repository, encrypted data blocks are stored to a resulting backup file.

NOTE

Even if encryption is disabled in the backup copy job, Veeam Backup & Replication will decrypt data blocks
of the encrypted source backup files.

The restore process for backups produced by backup copy jobs does not differ from that for backup jobs.

Over WAN Accelerators


WAN accelerators require reading data on the target side to perform such operations as global data
deduplication, backup health check and so on. For this reason, if you use WAN accelerators for backup copy jobs,
the encryption process is performed on the target side.

The backup copy job processing over WAN accelerators includes the following steps:

1. You enable encryption for a backup copy job and specify a password.

2. Veeam Backup & Replication generates necessary keys to protect backup files produced by the backup
copy job.

3. Data blocks are passed to the target backup repository in the unencrypted format.

224 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Received data blocks are encrypted on the target site and stored to a resulting backup file in the target
backup repository.

The restore process in this case does not differ from that for backup jobs. Veeam Backup & Replication retrieves
data blocks from the backup file in the target backup repository, sends them to the source side and decrypts
them on the source side.

When transporting data between WAN accelerators that face external networks, Veeam Backup & Replication
encrypts the network traffic by default. For network traffic encryption, Veeam Backup & Replication uses the
256-bit Advanced Encryption Standard (AES). For more information, see Enabling Network Data Encryption.

225 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
VeeamZIP Encryption
If you want to create an encrypted VeeamZIP file, you should enable the encryption option and specify a
password in VeeamZIP task options.

Data processing during VeeamZIP file creation and restore from a VeeamZIP file does not differ from that of a
backup job.

Tape Encryption
Veeam Backup & Replication supports two types of encryption for tape media:

• Hardware level: library- and driver-managed encryption mechanisms provided by the tape vendor

• Software level: the encryption mechanism provided by Veeam Backup & Replication

Hardware encryption has a higher priority. If hardware encryption is enabled for the tape media,
Veeam Backup & Replication automatically disables its software encryption mechanism for such tape libraries.
The Veeam encryption mechanism can only be used if hardware encryption is disabled at the tape device lev el or
not supported.

To use the Veeam encryption mechanism, you need to enable encryption at the level of media pool. In this case,
Veeam Backup & Replication will encrypt data for all jobs that use tapes from this media pool. Encryption is
supported for both types of tape jobs:

• Backup to tape jobs

226 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• File to tape jobs

Encryption of data on tapes includes the following steps:

1. You enable encryption for a media pool and specify a password.

2. You select the media pool as a target for a backup to tape or file to tape job.

3. Veeam Backup & Replication generates the necessary keys to protect data archived to tape.

4. During the backup to tape or file to tape job, the key is passed to the target side. In case of hardware
encryption, Veeam Backup & Replication passes the key to the tape device, and the tape device uses its
mechanism to encrypt data on tapes. In case of software encryption, Veeam Backup & Replication passes
the keys to the tape server, and encrypts data when it is archived to tape.

Backup to tape jobs allow double encryption. The backup to tape job uses a backup file as a source of data. If the
backup file is encrypted with the initial backup job and the encryption option is enabled for the backup to tape
job, too, the resulting backup file will be encrypted twice. To decrypt such backup file, you will need to
subsequently enter two passwords:

• Password for the initial backup job

227 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Password for the media pool

Restore of encrypted data from tape includes the following steps:

1. You insert tape with encrypted data into the tape drive and perform tape catalogization. The
catalogization operations lets Veeam Backup & Replication understand what data is written to tape.

2. You provide a password to decrypt data archived to tape.

3. Veeam Backup & Replication uses the provided password to generate a user key and unlock the
subsequent keys for data Veeam Backup & Replication retrieves data blocks from encrypted files on tapes
and decrypts them.

228 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Data Encryption Works
Data encryption is performed as part of backup, backup copy or archiving to tape processes. Encryption works at
the source side, before data is transported to the target. Encryption keys are not passed to the target side,
unless you run a backup copy job over WAN accelerators or perform health check for the encrypted backup files.

NOTE

The procedure below describes the encryption process for backup, backup copy jobs and VeeamZIP tasks.
For more information about encrypting data on tapes, see Tape Encryption.

The encryption process includes the following steps:

1. When you create a new job, you enable the encryption option for the job and enter a password to protect
data at the job level.

2. Veeam Backup & Replication generates a user key based on the entered password.

3. When you start an encrypted job, Veeam Backup & Replication creates a storage key and stores this key to
the configuration database.

4. Veeam Backup & Replication creates a session key and a metakey. The metakey is stored to the
configuration database.

5. Veeam Backup & Replication processes job data in the following way:

a. The session key encrypts data blocks in the backup file. The metakey encrypts backup metadata.

b. The storage key encrypts the session key and the metakey.

c. The user key encrypts the storage key.

d. If you use the Veeam Universal License, (or, for legacy-based license, Enterprise or higher edition),
and the backup server is connected to Veeam Backup Enterprise Manager, the Enterprise Manager key
also encrypts the storage key.

229 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Encrypted data blocks are passed to the target. The cryptograms of the public Enterprise Manager key (if
used), user key, storage key, session key and metakey are stored to the resulting file next to encrypted
data blocks.

If you use the Enterprise or Enterprise Plus edition of Veeam Backup & Replication and the backup server
is connected to Veeam Backup Enterprise Manager, Veeam Backup & Replication saves two cryptograms of
the storage key to the resulting file: one encrypted with the user key (c) and one encrypted with the
Enterprise Manager key (d). Saving the cryptogram twice helps Veeam Backup & Replication decrypt the
file even if a password is lost or forgotten. For more information, see How Decryption Without Password
Works.

230 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Data Decryption Works
When you restore data from an encrypted backup file, Veeam Backup & Replication performs data decryption
automatically in the background or requires you to provide a password.

• If encryption keys required to unlock the backup file are available in the Veeam Backup & Replication
configuration database, you do not need to enter the password. Veeam Backup & Replication uses keys
from the database to unlock the backup file. Data decryption is performed in the background, and data
restore does not differ from that from an unencrypted one.

Automatic data decryption is performed if the following conditions are met:

a. You encrypt and decrypt the backup file on the same backup server using the same
Veeam Backup & Replication configuration database.

b. [For backup file] The backup is not removed from the Veeam Backup & Replication console.

• If encryption keys are not available in the Veeam Backup & Replication configuration database, you need
to provide a password to unlock the encrypted file.

Data decryption is performed at the source side, after data is transported back from the target side. As a result,
encryption keys are not passed to the target side, which helps avoid data interception.

NOTE

The procedure below describes the decryption process for backup, backup copy jobs and VeeamZIP tasks.
For more information about decrypting tape data, see Tape Encryption.

The decryption process includes the following steps. Note that steps 1 and 2 are required only if you decrypt the
file on the backup server other than the backup server where the file was encrypted.

1. You import the file to the backup server. Veeam Backup & Replication notifies you that the imported file is
encrypted and requires a password.

2. You specify a password for the imported file. If the password has changed once or several times, you need
to specify the password in the following manner:

o If you select a .vbm file for import, you must specify the latest password that was used to encrypt
files in the backup chain.

o If you select a full backup file for import, you must specify the whole set of passwords that were used
to encrypt files in the backup chain.

3. Veeam Backup & Replication reads the entered password and generates the user key based on this
password. With the user key available, Veeam Backup & Replication performs decryption in the following
way:

a. Veeam Backup & Replication applies the user key to decrypt the storage key.

b. The storage key, in its turn, unlocks underlying session keys and a metakey.

c. Session keys decrypt data blocks in the encrypted file.

After the encrypted file is unlocked, you can work with it as usual.

231 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If you have lost or forgotten a password for an encrypted file, you can issue a request to Veeam Backup
Enterprise Manager and restore data from an encrypted file using Enterprise Manager keys. For more
information, see Enterprise Manager Keys and How Decryption Without Password Works.

232 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Decryption Without Password Works
When you import an encrypted backup file or tape media to the backup server, you need to enter a password to
decrypt data. In some cases, however, a password can be lost or forgotten. Veeam Backup & Replication offers a
way to restore data from encrypted backups or tapes even if a password is not available.

You can restore data from encrypted backups or tapes without a password only if your backup infrastructure
meets the following conditions:

1. You use Veeam Universal License (or a legacy socket-based license, Enterprise or higher edition).

2. The backup servers on which your encrypted data is added to Veeam Backup Enterprise Manager.

3. The backup server on which you generate a request for data decryption is added to Veeam Backup
Enterprise Manager.

If the backup server on which you encrypt data is added to Veeam Backup Enterprise Manager,
Veeam Backup & Replication employs the public Enterprise Manager key in the encryption process. To decrypt
backups or tapes encrypted with the public Enterprise Manager key, you can apply a matching private Enterprise
Manager key, instead of a password. The private Enterprise Manager key unlocks the underlying storage keys
and lets you access the content of an encrypted file.

The restore process is accomplished with the help of two wizards that run on two servers:

1. The E ncryption Key Restore wizard on the backup server.

2. The P a ssword Recovery wizard on the Veeam Backup Enterprise Manager server.

The restore process includes the next steps:

1. You start the E ncryption Key Restore wizard on the backup server to issue a request for data recovery.

2. The E ncryption Key Restore wizard generates a request to Veeam Backup Enterprise Manager. The request
has the format of a text document and contains cryptograms of storage keys that must be decrypted,
together with information about the public Enterprise Manager key that was used to encrypt data. At the
end of the request, the backup server adds a signature encrypted with a private backup server key.

3. You send the request to the Veeam Backup Enterprise Manager Administrator, for example, using email.

4. The Veeam Backup Enterprise Manager Administrator starts the P a ssword Recovery wizard on Veeam
Backup Enterprise Manager and inserts the text of the request to the wizard.

5. Veeam Backup Enterprise Manager finds a matching public backup server key in Veeam Backup Enterprise
Manager configuration database and decrypts the signature with this key.

6. Veeam Backup Enterprise Manager decrypts storage keys with the private Enterprise Manager key
available on Veeam Backup Enterprise Manager, and generates a response in the P a ssword Recovery
wizard. The response has the format of a text document and contains decrypted storage keys.

7. The Veeam Backup Enterprise Manager Administrator sends the response to you, for example, using email.

8. You input the request to the E ncryption Key Restore wizard. Veeam Backup & Replication processes the
response, retrieves the decrypted storage keys and uses them to unlock encrypted backups or tapes and
retrieve their content.

233 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

You can recover data only if Veeam Backup Enterprise Manager has a private Enterprise Manager key
matching the public Enterprise Manager key that was used for data encryption. If a matching private
Enterprise Manager key is not found in the Veeam Backup Enterprise Manager configuration database, the
P a ssword Recovery wizard will fail. In such situation, you can import a necessary private Enterprise
Manager key using the import procedure. For more information, see Exporting and Importing Enterprise
Manager Keys in Veeam Backup Enterprise Manager User Guide.

234 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encryption Best Practices
To guarantee the flawless process of data encryption and decryption, consider the following recommendations.

Password
Consider the following recommendations when you create a password:

1. Use strong passwords that are hard to crack or guess:

o The password must be at least 8 characters long.

o The password must contain uppercase and lowercase characters.

o The password must be a mixture of alphabetic, numeric and punctuation characters.

o The password must significantly differ from the password you used previously.

o The password must not contain any real information related to you, for example, date of birth, your
pet’s name, your logon name and so on.

2. Provide a meaningful hint for the password that will help you recall the password. The hint for the
password is displayed when you import an encrypted file or tape to the backup server and attempt to
unlock it.

3. Keep passwords in the safe place. If you lose or forget your p assword, you will not be able to recover data
from backups or tapes encrypted with this password, unless you use Enterprise Manager keys in the
encryption process.

4. Change passwords for encrypted jobs regularly. Use of different passwords helps increase the encryption
security level.

Data Recovery without Password


If you use Veeam Universal License (or a legacy socket-based license, Enterprise or higher edition), connect
backup servers to Veeam Backup Enterprise Manager. In this case, Veeam Backup & Replication will employ
Enterprise Manager keys in the encryption process, which will let you recover data from encrypted backups and
tapes even if the password is lost or forgotten.

Consider the following recommendations for Enterprise Manager keysets:

1. Create and activate new Enterprise Manager keysets regularly. When you activate a keyset, the public
Enterprise Manager key is automatically propagated to backup servers connected to Veeam Backup
Enterprise Manager and is used for encrypted jobs on these servers.

2. Create backup copies of Enterprise Manager keysets and keep them in a safe place. If your installation of
Veeam Backup Enterprise Manager goes down for some reason, you will lose private Enterprise Manager
keys. As a result, you will not be able to use the Veeam Backup Enterprise Manager functionality to
recover data from backups and tapes without a password.

For more information on data decryption without a password, see Decrypting Data Without Password.

Encryption for Existing Jobs


If you enable encryption for an existing job, except the backup copy job, during the next job session
Veeam Backup & Replication will automatically create a full backup file. The created full backup file and
subsequent incremental backup files in the backup chain will be encrypted with the specified password.

235 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Encryption is not retroactive. If you enable encryption for an existing job, Veeam Backup & Replication does not
encrypt the previous backup chain created by this job. If you want to start a new chain so that the unencrypted
previous chain can be separated from the encrypted new chain, follow this Veeam KB article.

If you change the password for the already encrypted job, during the next job ses sion
Veeam Backup & Replication will create a new incremental backup file. The created backup file and subsequent
backup files in the backup chain will be encrypted with the new password.

NOTE

To unlock a backup encrypted with several passwords, you must decrypt it in the following manner:

• If you import a metadata file (VBM), provide the latest password that was used to encrypt files in
the backup chain.
• If you import a full backup file (VBK), provide the whole set of passwords that were used to encryp t
files in the backup chain.

For more information, see Decrypting Data with Password.

If you change encryption settings for an existing backup copy job, you will need to create an active full backup
manually. For more information, see Creating Active Full Backups.

If you disable encryption for an existing job, except the backup copy job, during the next job session
Veeam Backup & Replication will automatically create a full backup file.

236 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Data from Encrypted Backups
When you restore data from an encrypted backup, Veeam Backup & Replication performs data decryption
automatically in the background or requires you to specify a password.

• If encryption keys required to unlock the backup file are available in the configuration database, you do
not need to specify the password. Veeam Backup & Replication uses keys from the database to unlock the
backup file. Data decryption is performed in the background, and data restore from the encrypted back up
does not differ from that from an unencrypted one.

Automatic backup file decryption is performed if the following conditions are met:

a. You encrypt and decrypt the backup file on the same backup server that uses the same configuration
database.

b. The backup is not removed from the Veeam Backup & Replication console.

• If encryption keys are not available in the configuration database, you can restore data from the encrypted
backup with the following methods:

o You can provide a password or a set of passwords to unlock an encrypted file. For more information,
see Decrypting Data with Password.

o You can use Veeam Backup Enterprise Manager to unlock an encrypted file without a password. For
more information, see Decrypting Data Without Password.

Decrypting Data with Password


To unlock an encrypted file, you must specify a password. The password must be the same as the password that
was used to encrypt the backup file.

To decrypt a backup file:

1. Import an encrypted backup file to the Veeam Backup & Replication console. After the import, the
encrypted backup will appear under the Ba ckups > Disk (encrypted) node in the inventory pane.

2. In the inventory pane, select Disk (encrypted).

3. In the working area, select the imported backup and click Sp ecify Password on the ribbon or right-click the
backup and select Sp ecify password.

4. In the Description field of the Sp ecify Password window, Veeam Backup & Replication displays a hint for
the password that was used to encrypt the backup file. Use the hint to recall the password.

5. In the P a ssword field, enter the password for the backup file.

If you changed the password one or several times while the backup chain was created, you must enter
passwords in the following manner:

• If you select a metadata file (VBM) for import, you must specify the latest password that was used to
encrypt files in the backup chain.

• If you select a full backup file (VBK) for import, you must specify the whole set of passwords that were
used to encrypt files in the backup chain.

If you enter correct passwords, Veeam Backup & Replication will decrypt the backup file. The backup will be
moved under the Ba ckups > Disk ( Imported) node in the inventory pane. You can perform restore operations
with the backup file in a regular manner.

237 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

You can recover data from encrypted backups even if the password is lost. Restoring data without a
password is included in the Veeam Universal License. When using a legacy socket-based license, Enterprise
or higher edition is required. Also, your backup server must be connected to Veeam Backup Enterprise
Manager. For more information, see Decrypting Data Without Password.

Decrypting Data Without Password


If you have lost or forgotten a password, you can unlock an encrypted file with the help of Veeam Backup
Enterprise Manager.

You can restore data without a password only if the following conditions are met:

1. You use Veeam Universal License (or a legacy socket-based license, Enterprise or higher edition).

2. The backup server on which your encrypted data is connected to Veeam Backup Enterprise Manager.

3. The backup server on which you generate a request for data decryption is connected to Veeam Backup
Enterprise Manager.

4. Password loss protection is enabled on Veeam Backup Enterprise Manager (enabled by default). You can
check the configured settings as described in the Managing Encryption Keys section in the Veeam Backup
Enterprise Manager Guide.

IMP ORTANT

Backup servers that you use for data decryption must be connected to the same instance of Veeam Backup
Enterprise Manager. If you connect the backup server to several instances of Veeam Backup Enterprise
Manager, this may cause unexpected behavior, and the decryption process may fail.

The restore process is accomplished with the help of two wizards that run on two servers:

1. The E ncryption Key Restore wizard on the backup server.

2. The P a ssword Recovery wizard on the Veeam Backup Enterprise Manager server.

To restore encrypted data without a password:

1. Create a request for data restore.

2. Process the request in Veeam Backup Enterprise Manager.

238 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Complete the key restore process.

239 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Create Request for Data Restore
This procedure is performed by the Veeam Backup Administrator on the backup server.

1. Import encrypted backup to the Veeam Backup & Replication console.

2. Select the imported backup and click Sp ecify Password on the ribbon or right-click the backup and select
Sp ecify password.

3. In the Sp ecify Password window, click the I ha ve lost the password link.

4. Veeam Backup & Replication will launch the E ncryption Key Restore wizard. At the Request step of the
wizard, review the generated request for data recovery. Use buttons at the bottom of the wizard to copy
the request to the clipboard or save the request to a text file.

5. Send the copied request by email or pass it in any other way to the Veeam Backup Enterprise Manager
Administrator.

240 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

You can close the E ncryption Key Restore wizard on the backup server and start it anew when you receive a
response from the Veeam Backup Enterprise Manager Administrator.

241 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Process Request in Veeam Backup Enterprise Manager
This procedure is performed by the Veeam Backup Enterprise Manager Administrator on the Veeam Backup
Enterprise Manager server.

1. Copy the obtained request to the clipboard.

2. In Veeam Backup Enterprise Manager, go to the Configuration > Key Management section.

3. Click P a ssword Recovery at the top of the section to open the P a ssword Recovery wizard.

4. Paste the request that you have received from the Veeam Backup Administrator. You can use the [Ctrl+V]
key combination or click P a ste at the bottom of the wizard.

5. Follow the next steps of the wizard. At the Response step of the wizard, copy the text displayed in the
wizard to the clipboard.

242 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Send the copied response by email or pass it in any other way to the Veeam Backup Administrator working
on the backup server.

243 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Complete Key Restore Process
This procedure is performed by the Veeam Backup Administrator on the backup server.

1. In Veeam Backup & Replication, get back to the E ncryption Key Restore wizard.

2. Enter the copied response to the text window at the Response step of the E ncryption Key Restore wizard.

3. Follow the next steps of the wizard. At the last step, click Finish. Veeam Backup & Replication will retrieve
the decrypted storage keys from the response, apply them to the encrypted file and unlock the file
content.

244 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Encrypted Data from Tapes
When you restore data from encrypted tapes, Veeam Backup & Replication performs data decryption
automatically in the background or requires you to provide a password.

• If encryption keys required to unlock the tape are available in the Veeam Backup & Replication database,
you do not need to enter the password to decrypt the tape. Veeam Backup & Replication uses keys from
the database to unlock the encrypted tape. Data decryption is performed in the background and data
restore from encrypted tapes does not differ from that from an unencrypted ones.

Automatic tape decryption is performed if the following conditions are met:

o You encrypt and decrypt tapes on the same Veeam backup server.

o The tape is loaded to the tape library and information about this tape is available in the catalog.

o The password specified in the settings of the media pool to which the tape belongs is the same as the
password that was used for tape encryption.

• If encryption keys are not available in the Veeam Backup & Replication database, you can restore data
from encrypted tapes with the following methods:

o You can provide a password or a set of passwords to unlock the encrypted tape. For more information,
see Decrypting Tapes with Password.

o You can use Veeam Backup Enterprise Manager to unlock the encrypted tape without a password. For
more information, see Decrypting Data Without Password.

Decrypting Tapes with Password


When you restore encrypted files or backups from tape, you need to specify a password that was used to
encrypt data archived to tape.

To unlock encrypted tapes:

1. Insert encrypted tapes into the tape library.

2. Catalog the tapes so that Veeam Backup & Replication can read data archived on tape. After you perform
catalogization, encrypted tapes will be displayed under the Med ia > E ncrypted node in the tape library. On
the cataloged tape, Veeam Backup & Replication displays the key icon to mark it as encrypted.

3. In the inventory pane, select the E ncrypted node under Med ia node.

4. In the working area, select the imported tape and click Sp ecify password on the ribbon or right-click the
tape and select Sp ecify password.

5. In the Description field of the Sp ecify Password window, Veeam Backup & Replication displays a hint for
the password that was used to encrypt the tape. Use the hint to recall the password.

6. In the P a ssword field, enter the password for the tape.

7. If the imported tape is a part of a backup set but is not the last tape in this set, perform catalogization
once again.

When Veeam Backup & Replication creates a backup set, it writes catalog data to the last tape in this set.

o If the imported group of tapes contains the last tape in the backup set, Veeam Backup & Replication
retrieves catalog data from the last tape during the initial catalogization process (see point 2 of this
procedure).

245 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o If the imported group of tapes does not contain the last tape in the backup set,
Veeam Backup & Replication needs to additionally catalog files on imported tapes.

If you enter a correct password, Veeam Backup & Replication will decrypt the tape media. The tape will be
moved under the correct media pool in the inventory pane. You can perform restore operations for data archived
to tape as usual.

If you import a backup file from tape and the backup file was encrypted twice, with the initial backup job and
with the backup to tape job, you must sequentially specify two passwords:

1. Password that was used to encrypt tapes in the media pool.

2. Password for the primary backup job.

After you enter the first password, backups from the tape will be moved under the Ba ckup > E ncrypted node in
the inventory pane. You must then enter the second password to decrypt the backup and get access to its
content.

NOTE

You can recover data from encrypted backups even if the password is lost. Restoring data without a
password is included in the Veeam Universal License. When using a legacy socket-based license, Enterprise
or higher edition is required. Also, your backup server must be connected to Veeam Backup Enterprise
Manager. For more information, see Decrypting Data Without Password.

Decrypting Tapes Without Password


If you have lost or forgotten a password, you can unlock encrypted tapes with the help of Veeam Backup
Enterprise Manager.

246 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can restore data from tapes without a password only if your backup infrastructure meets the following
conditions:

1. You use Veeam Universal License (or a legacy socket-based license, Enterprise or higher edition).

2. Veeam backup server on which your encrypted tapes is added to Veeam Backup Enterprise Manager.

3. Veeam backup server on which you generate a request for data decryption is added to Veeam Backup
Enterprise Manager.

The restore process is accomplished with the help of two wizards that run on two servers:

1. The E ncryption Key Restore wizard on the Veeam backup server.

2. The P a ssword Recovery wizard on the Veeam Backup Enterprise Manager server.

To restore encrypted data from tapes without a password:

1. Create a request for data restore.

2. Process the request in Veeam Backup Enterprise Manager.

3. Complete the key restore process.

247 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Create Request for Data Restore
This procedure is performed by the Veeam Backup Administrator on the Veeam backup server.

1. Import encrypted tapes to the Veeam backup server.

2. Select the imported tape and click Sp ecify Password on the ribbon or right-click the tape and select
Sp ecify password.

3. In the Sp ecify Password window, click the I ha ve lost the password link.

4. Veeam Backup & Replication will launch the E ncryption Key Restore wizard. At the Request step of the
wizard, review the generated request for data recovery. Use buttons at the bottom of the wizard to copy
the request to the clipboard or save the request to a text file.

248 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Send the copied request by email or pass it in any other way to the Veeam Backup Enterprise Manager
Administrator.

TIP

You can close the E ncryption Key Restore wizard on the Veeam backup server and start it anew when you
receive a response from the Veeam Backup Enterprise Manager Administrator.

249 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Process Request in Veeam Backup Enterprise Manager
This procedure is performed by the Veeam Backup Enterprise Manager Administrator on the Veeam Backup
Enterprise Manager server.

1. Copy the obtained request to the clipboard.

2. In Veeam Backup Enterprise Manager, go to the Configuration > Settings > Key Management section.

3. Click P a ssword Recovery to open the P a ssword Recovery wizard.

4. Use the [Ctrl+V] key combination to paste the request that you have received from the Veeam Backup
Administrator. You can also use the Imp ort from File link to import the request from a text file.

5. Follow the next steps of the wizard. At the Response step, copy the text displayed in the wizard to the
clipboard.

250 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Send the copied response by email or pass it in any other way to the Veeam Backup Administrator working
on the Veeam backup server.

251 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Complete Key Restore Process
This procedure is performed by the Veeam Backup Administrator on the Veeam backup server.

1. In Veeam Backup & Replication, get back to the E ncryption Key Restore wizard.

2. Enter the copied response to the text window at the Response step of the E ncryption Key Restore wizard.

3. Follow the next steps of the wizard. At the last step, click Finish. Veeam Backup & Replication will retrieve
the decrypted storage keys from the response, apply them to the encrypted tape and unlock the tape
content.

252 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Multi-Factor Authentication
Veeam Backup & Replication supports multi-factor authentication (MFA) for additional user verification. A one-
time password (OTP) generated in the mobile authenticator application is used as a second v erification method.
Combined with login and password credentials, it creates a more secure environment and protects user accounts
from being compromised.

The feature includes:

• Enabling/disabling MFA for all users

• Disabling MFA for service accounts

• Resetting MFA for specific users

Requirements and Limitations


MFA has the following requirements and limitations:

• Only users with the Veeam Backup Administrator role can manage MFA.

• MFA is not supported in the Veeam Backup & Replication Community Edition.

• MFA is not natively supported for Veeam Backup Enterprise Manager. It can be used with a third party
identity provider specified in the SAML authentication settings.

• User groups are not supported. You can enable MFA only for user accounts.

• MFA is not supported for non-interactive connections used by the following applications and backup
infrastructure components:

o Veeam Backup & Replication REST API

o Veeam Backup Enterprise Manager (for communication with the Veeam Backup & Replication server)

o Veeam ONE agent (for communication with the Veeam Backup & Replication server)

o Veeam Backup Validator

To avoid connection issues, you must disable MFA for the accounts used to run these applications and
backup infrastructure components. For more information, see Disabling MFA for Service Accounts.

• MFA is not supported for PowerShell (either interactive logon or non-interactive connections). To use
PowerShell cmdlets with Veeam Backup PowerShell Module or Microsoft Windows PowerShell, run the
Veeam Backup & Replication console or Microsoft Windows PowerShell under the service account with
disabled MFA.

• MFA also must be disabled for the account in the following cases:

o To restore the configuration database properly, run the Veeam Backup & Replication console or
Veeam Backup Configuration Restore application under the service account with disabled MFA.

o To upgrade the remote Veeam Backup & Replication console properly, run it under the service
account with disabled MFA.

• If a service provider (SP) uses Veeam Service Provider Console and wants to use multi-factor
authentication on the SP backup server, they must set up a service account in
Veeam Backup & Replication. For more information, see this Veeam KB article.

253 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Mobile push notifications are not supported. You can get an OTP code only in the mobile authenticator
application.

How MFA Works


Veeam Backup & Replication supports the following scenario for MFA:

o A user logs in to the Veeam Backup & Replication console.

o Veeam Backup & Replication checks if MFA is enabled and configured for the user:

a. MFA is enabled but not configured. The user gets the instruction how to set up MFA.
Veeam Backup & Replication generates a secret key which is used once for the initial setup in the
mobile authenticator application. The hash of the secret key is also saved in the configuration
database.

b. MFA is enabled and configured. Each time the user logs in they should enter a 6-digit confirmation
code generated in the mobile authenticator application. Veeam Backup & Replication checks if the
code is valid and, in case of success, starts a user session.

If there are more than 5 unsuccessful attempts, the user can reopen the console and try to log in
again after waiting for at least one minute. If the problem persists, the backup administrator can
reset MFA by request.

IMP ORTANT

The code confirmation works when there is no time shifting between the mobile authenticator application
and the Veeam Backup & Replication server. Ensure that they are synchronized with the UTC time.
Otherwise, the authentication will fail.

If Veeam Explorers and other applications (except for Veeam Backup PowerShell Module) are started from the
console, they do not require additional authentication.

Enabling MFA
To enable the feature for all users:

1. Log in to the Veeam Backup & Replication console as an administrator.

2. Go to Users and Roles > Security.

254 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Remove user groups from the list if there are any. Leave only specific users.

4. Select the E na ble multi-factor authentication (MFA) check box.

5. Click OK.

Resetting MFA for a Specific User


The backup administrator can reset MFA by user request if they have authentication issues, lose or change a
mobile device with the mobile authentication application, and so on.

To reset MFA for a specific user:

1. Log in to the Veeam Backup & Replication console as an administrator.

2. Go to Users and Roles > Security.

3. Select the user and click Reset MFA. The next time the user logs in they will get the instruction how to
set up MFA.

255 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling MFA
To disable the feature for all users:

1. Log in to the Veeam Backup & Replication console as an administrator.

2. Go to Users and Roles > Security.

3. Clear the E na ble multi-factor authentication (MFA) check box.

4. Click OK.

Disabling MFA for Service Accounts


If you cannot use MFA due to limitations described in section Requirements and Limitations, you can disable this
feature for specific service accounts used to run applications and backup infrastructure components.

To disable the feature for service accounts:

1. Log in to the Veeam Backup & Replication console as an administrator.

2. Go to Users and Roles > Security.

3. Select the service account and click E d it.

4. Select the This is a service account (disables two-factor authentication) check box.

5. Click OK.

256 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Kerberos Authentication
Veeam Backup & Replication supports Kerberos authentication for all components of the backup infrastructure
including Veeam Explorers, Veeam Agents, Veeam Plug -ins, and Veeam Backup Enterprise Manager. You can
build the backup infrastructure in the following environments:

• Kerberos authentication is the primary domain authentication protocol, NTLM is supported for
compatibility. This configuration is used by default starting from Microsoft Windows 2000 Server.

• Kerberos is the only domain authentication protocol, NTLM is disabled (more secure).

NOTE

Kerberos authentication is supported only in Microsoft Active Directory -based environments.

How Kerberos Works


Unlike NTLM, Kerberos uses Ticket Granting Tickets (TGT) issued by the Key Distribution Center (KDC). TGT files
contain a session key, the key's expiration date, and a user's IP address. They are encrypted and have limited
validity period (10 hours by default). This authentication mechanism protect users from man-in-the-middle
(MITM) attacks.

Veeam Backup & Replication supports the standard Kerberos authentication scenario:

1. A client sends a request to the KDC, which is located on a domain controller and uses Microsoft Active
Directory as the account database. The request contains user details and information about the Veeam
service the client wants to access.

2. The KDC verifies the client's request and issues a TGT.

3. The client uses the TGT to send a request to the KDC Ticket Granting Service (TGS) and get a TGS ticket.
The request also contains the Service Principal Name (SPN) of the service.

4. The client uses the TGS ticket to send a request to the server.

5. The server verifies the client's request and provides access to the service for a limited period specified in
the Kerberos configuration.

For more information about Kerberos authentication, see this Microsoft article.

Requirements and Limitations


Kerberos authentication has the following requirements and limitations:

• The client and the server must belong to the same domain, or a trust relationship must exist between
domains.

• All backup infrastructure components must be added to the Veeam Backup & Replication console using
FQDN.

• Veeam backup infrastructure servers must resolve FQDNs.

• FQDN must be used when connecting to the remote Veeam Backup & Replication console.

• The hostname length for all Windows-based backup infrastructure components and VM guest OSes must
not exceed 15 characters.

257 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The maximum time difference between the client and the domain controller must be 5 minutes to protect
the backup infrastructure from relay attacks.

• NFS is supported by Kerberos starting from version 4.1.

• For guest OS processing, consider the following:

o Local accounts do not support Kerberos authentication. To authenticate with Microsoft Windows
guest OS using Kerberos, specify an Active Directory account.

o If you use networkless application-aware guest processing through PowerShell Direct, the guest OS
must still have access to the domain controller. Otherwise, Kerberos authentication will not work.

For SPNs, consider the following aspects:

• Each Veeam service must have two SPNs registered with the Active Directory in the following formats:

o {ServiceName}/{FQDN}, for example, VeeamBackupSvc/vbrserver01.tech.local

o {ServiceName}/{NetBIOSName}, for example, VeeamBackupSvc/VBRSERVER01

• For the following services, SPNs are registered automatically each time they start:

o Veeam Backup Service (VeeamBackupSvc)

o Veeam Backup Enterprise Manager Service (VeeamEnterpriseManagerSvc)

o Veeam Cloud Connect Service (VeeamCloudConnectSvc)

o Veeam Cloud Gateway Service (VeeamGateSvc)

o Veeam CDP Coordinator Service (VeeamCdpSvc)

o Veeam CDP Proxy Service (VeeamCdpProxySvc)

o Veeam Guest Catalog Service (VeeamCatalogSvc)

o Veeam Distribution Service (VeeamDistributionSvc)

o Veeam Mount Service (VeeamMountSvc)

o Veeam Broker Service (VeeamBrokerSvc)

o Veeam Hyper-V Integration Service (VeeamHvIntegrationSvc)

o Veeam Data Mover Service (VeeamTransportSvc)

o Veeam WAN Accelerator Service (VeeamWANSvc)

o Veeam vPower NFS Service (VeeamNFSSvc)

o Veeam Backup VSS Integration Service (VeeamFilesysVssSvc)

o Veeam Installer Service (VeeamDeploySvc)

o Veeam Tape Service (VeeamTapeSvc)

o Veeam Log Shipping Service (VeeamLogShipperSvc)

o Veeam Agent for Microsoft Windows Service (VeeamAgentWindows)

258 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Veeam Guest Helper Service (VeeamGuestHelperSvc)

For services running under the LocalSystem account, SPNs are mapped to the Active Directory
computer objects. For services, running under a dedicated Active Directory service account, SPNs are
mapped to the Active Directory user objects.

Note that If for any reason the SPN registration fails, the service will continue working, but there may
be authentication issues in Kerberos-only environments.

• If you want to register SPN manually, you can use the setspn tool. For more information about manual
SPN registration, see this Microsoft article. To disable automatic SPN registration, contact Veeam
Customer Support.

Note that Veeam Platform Services (AWS, Azure, Google Cloud) and Veeam Explorer Recovery Service
do not need to be registered as they do not have SPNs.

• To communicate with Hyper-V clusters, Veeam Backup & Replication uses the default SPN format for
Veeam Hyper-V Integration Service: {HOST}/{FQDN} as there may be issues with registering SPN
VeeamHvIntegrationSvc/{FQDN} for a cluster account.

• If you want to use another account for running a Veeam service, you must manually remove the existing
SPN from the Active Directory beforehand. Otherwise, the SPN registration with the new account will
fail.

IMP ORTANT

If you use persistent agents for guest OS processing and want to upgrade Ve eam Backup & Replication to
version 12, there may be issues with application-aware processing in a Kerberos-only environment. To
mitigate risks, register SPNs for Guest Helper Service using the following format:
{VeeamGuestHelperSvc}/{FQDN} and {VeeamGuestHelperSvc}/{NetBIOSName}. For more
information, see this Veeam KB article.

Configuring Kerberos Environments


If you use default Microsoft Windows configuration for Kerberos authentication with NTLM fallback, configure
the Network security: LAN Manager Authentication Level security policy setting to send NTLMv2 responses
only. For more information, see this Microsoft article.

NOTE

Using NTLM increases the attack surface of your backup infrastructure. To build a more secure
environment, disable NTLM and leave Kerberos the only domain authentication protocol.

To configure a Kerberos-only environment, perform the following steps:

o E na ble an NTLM audit. Start to collect and analyze NTLM audit events to determine which applications
and services send NTLM requests. Reconfigure or update them to use Kerberos. If an application or
service does not support Kerberos, replace it with an alternative one. For more information about
auditing NTLM usage, see this Microsoft article.

o E na ble Kerberos extended logging mode. By default, Veeam Backup & Replication saves logs only for
failed SPN registrations. It is recommended to collect information about all SPN registrations during
initial Veeam Backup & Replication deployment and NTLM audit troubleshooting. To enable extended
logging for SPNs used for Kerberos authentication between backup infrastructure components, see this
Veeam KB article.

259 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Restrict NTLM traffic. When all applications and services are configured to use Kerberos and there are
no NTLM audit events, apply Network Security: Restric t NTLM Active Directory group policies to restrict
NTLM traffic and authentication. You can also configure exclusions for specific hosts if they still require
NTLM authentication to work properly. For more information about restricting NTLM usage, see this
Microsoft article.

NOTE

To prevent Kerberos environments from Kerberoasting attacks, do the following:

o Make sure that you use strong encryption algorithms allowed for Kerberos. For more information,
see this Microsoft article.
o Prevent Kerberos change password that uses RC4 secret keys. For more information, see this
Microsoft article.

260 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Group Managed Service Accounts
A Group Managed Service Account (gMSA) is the type of domain account configured on the server. It does not
need the administrator to manage the password as this role is performed by the Microsoft Windows operating
system. Randomly generated complex passwords are automatically changed every 30 days which reduce the risk
of brute force and dictionary attacks. For more information about gMSAs, see this Microsoft article.

You can use gMSAs to run guest processing tasks.

NOTE

For application-aware processing, using a gMSA is supported for backups or replicas of VMs that run
Microsoft Active Directory (domain controllers), Microsoft Exchange, Microsoft SQL Server, and Oracle 12c
Release 2 and later. You cannot back up or replicate VMs that run Microsoft SharePoint with the gMSA.

Requirements and Limitations


gMSAs have the following requirements and limitations:

• gMSAs are applicable to Microsoft Windows Server 2012 and later. For more information about operating
system and Microsoft Active Directory requirements, see this Microsoft article.

• gMSAs are not supported for backups of the Linux target machines joined to the Active Directory domain.

• Since gMSAs require a connection to the domain controller, these accounts work only over network.

• If you use gMSAs to manage the restore process of VM guest OS files, consider Requirements and
Limitations.

• If you back up a machine using a gMSA, both the guest interaction proxy and the target machine must
have network access to the domain controllers and be in the same domain to obtain the gMSA password.
On the target machine the gMSA must be added to the Administrators group (local or domain). Domain
Administrator permissions are only required for Microsoft Active Directory backups, for other supported
applications local Administrator permissions are sufficient.

IMP ORTANT

Consider that granting Domain Administrator permissions to gMSAs makes them a potential source
of vulnerability.

Before You Begin


Before you start using gMSAs, configure the domain controller:

1. The domain controller requires a root key to generate gMSA passwords. Ensure that the Key Distribution
Service is enabled on the domain controller and use the following command in Micr osoft Windows
PowerShell to generate a root key:

Add-KdsRootKey -EffectiveImmediately

Wait until the Active Directory replication is finished or force it manually. For more information about
creating KDS root keys, see this Microsoft article.

2. To enable gMSA support in Microsoft Windows PowerShell, use the following commands:

261 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Install-WindowsFeature RSAT-AD-PowerShell,NET-Framework-Features | Out-Nul
l;
Import-Module ServerManager;
Import-Module ActiveDirectory;

Creating gMSA
To create a gMSA, use the New-ADServiceAccount cmdlet on the domain controller. For example:

$gMSAName = 'DOMAIN\gmsa01'
$gMSAGroupName = 'gMSAComputerAccountsGroup'
$gMSADNSHostName = 'gmsa01.srv.local'
New-ADServiceAccount -Name $gMSAName -DNSHostName $gMSADNSHostName -PrincipalsA
llowedToRetrieveManagedPassword $gMSAGroupName -Enabled $True

Consider the following:

• In the DNSHostName parameter, specify the FQDN of the gMSA.

• For the PrincipalsAllowedToRetrieveManagedPassword parameter specify the AD group


containing computer accounts which will use the gMSA. As an alternative, specify computer accounts
separated by comma.

• By default, created gMSAs are shown in the Ma naged Service Accounts container.

For more information about all cmdlet parameters, see this Microsoft article.

NOTE

To provide a more secure environment, use separate gMSAs for critical backup infrastructure components.

To refresh AD group membership after you create a gMSA, it is recommended to reboot machines on which you
plan to install the gMSA.

Installing gMSA
To install a gMSA on the server or the target machine, perform the following steps:

1. Run the Install-ADServiceAccount cmdlet.

Install-ADServiceAccount "DOMAIN\gmsa01$"

2. Ensure that the gMSA was successfully installed.

Test-ADServiceAccount "DOMAIN\gmsa01$"

3. Add the gMSA to the local Ad ministrators group.

Add-LocalGroupMember -Group "Administrators" -Member "DOMAIN\gmsa01$"

262 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

For domain controller VMs, add the gMSA to the domain Administrators group or
BUILTIN\Administrators group on the domain controller.

For guest processing, install the gMSA on the guest OS machine and the guest interaction proxy.

Using gMSA
To run guest processing tasks with the gMSA, do the following:

1. Make sure that the following services run under the LocalSystem account:

o The Veeam Backup Service on the backup server.

o The Veeam Data Mover Service on the guest interaction proxy.

2. Add the gMSA account type to the Credentials Manager. For more information, see Group Managed
Service Accounts.

3. Select the gMSA when specifying guest OS credentials for jobs or policies.

263 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Licensing
To work with Veeam Backup & Replication, you must obtain a license key and install it on the backup server. If
you do not install the license key, the product will operate in the Veeam Backup & Replication Community (free)
Edition. For more information, see Veeam Backup & Replication Community Edition.

Veeam licenses Veeam Backup & Replication in two ways: per instance and per socket.

You can use both instance and socket licenses. For more information, see Merging Licenses.

NOTE

Veeam Backup & Replication consumes licenses only to back up data. Backup restores do not require
licenses. You can restore VMs and data no matter how many available licenses you have or how many VMs
you are restoring.

Socket Licensing
With the socket licensing model, Veeam Backup & Replication is licensed by the number of CPU sockets on
protected hosts. For more information, see Veeam Licensing Policy.

A license is required for every occupied motherboard socket as reported by the hypervisor API.

License is required only for source hosts — hosts on which VMs that you back up or replicate reside. Target hosts
(for replication and migration jobs) do not need to be licensed.

The socket license assignment happens automatically as soon as you start a backup or replication job for VMs on
a specific source host. You can revoke licenses from licensed hosts and re-apply them to other objects if needed.
For more information, see Revoking License.

NOTE

If you use a socket license that was obtained for an earlier version of Veeam Backup & Replication, Veeam
Software adds up to 6 gift (built-in) instances free of charge to your license scope. You can use these
instances to protect any type of supported workloads except VMware and Hyper -V VMs — they are covered
by the licensed CPU sockets on virtualization hosts.

If the number of licensed sockets is less than 6, you can use the number of instances that equals the
number of licensed sockets. For example, if the number of licensed sockets is 5, you can use 5 instances. If
the number of licensed sockets is 100, you can use 6 instances.

Note that starting with Veeam Backup & Replication 12, the gift (built-in) instances are disabled if the
perpetual license support expiration date is reached.

Instance Licensing
Veeam Backup & Replication can be licensed by the number of instances. Instances are units (or tokens) that you
can use to protect your virtual, physical or cloud-based workloads. For more information, see Veeam Licensing
Policy.

You must obtain a license with the total number of instances for workloads that you plan to protect in
Veeam Backup & Replication.

264 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Workloads that have been processed in the past 31 days are considered prote cted. Every protected workload
consumes instances from the license scope. The number of instances that a workload requires depends on the
workload type and product edition.

This licensing model allows you to obtain a license with a certain number of instances without knowing in
advance what types of workloads you plan to protect. When a need arises, you can revoke instances from a
protected workload, and reuse them to protect other workloads regardless of the workload type.

Veeam Backup & Replication keeps track of instances consumed by protected workloads. If the number of
consumed instances exceeds the license limit, Veeam Backup & Replication displays a warning when you open
the Veeam Backup & Replication console. For more information, see Exceeding License Limit.

Consider the following:

• VM templates are regarded as protected VMs and consume license instances.

• VMs and unstructured data sources processed with backup copy and tape jobs are not regarded as
protected VMs and data sources and do not consume license instances. These types of jobs provide an
additional protection level for VMs and unstructured data sources that are already protected with backup
jobs.

• For more information on how Veeam Backup & Replication calculates license instances to consume when
protecting unstructured data sources, see Instance Consumption for Object Storage Backup, File Backup
and File to Tape Jobs.

Capacity Licensing
Veeam Backup & Replication can be licensed by the capacity of protected data. TBs of front-end storage
capacity pack are units that you can use to protect your non-deduplicated and uncompressed front-end source
data in unstructured data sources (file servers, file shares, NAS filers, object storage repositories). For more
information, see Veeam Licensing Policy.

You must obtain a license with the total capacity for source data that you plan to protect in
Veeam Backup & Replication.

Data sources that have been processed in the past 31 days are considered protected. Every protected data
source consumes capacity from the license scope.

This licensing model allows you to obtain a license with a certain license cap acity without knowing in advance
what types of unstructured data sources you plan to protect. When a need arises, you can revoke instance
capacity from a protected data source, and reuse it to protect other data sources regardless of the workload
type.

Veeam Backup & Replication keeps track of capacity consumed by protected data sources. If the number of
consumed capacity exceeds the license limit, Veeam Backup & Replication displays a warning when you open the
Veeam Backup & Replication console. For more information, see Exceeding License Limit.

Consider the following:

• Veeam Backup & Replication rounds the protected amount of data for each unstructured data source down
to 500 GB.

• Capacity license is consumed in 500 GB chunks.

• When your unstructured data sources are protected with file backup to tape or object storage backup to
tape jobs, Veeam backup files are excluded from the capacity consumption calculation. These files have
the following extensions: VAB, VBM, VBK, VIB, VRB, VSB, VLB, VSM, VLM, VOM, VACM, VASM, VSOURCE,
VSOURCETEMP, VSTORE, VSTORETEMP, VSLICE, VBASKET, VLIST, VCACHE, VBLOB, BCO, ADB.

265 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If different data sources are protected by different file backup or object storage backup jobs or by
different file backup to tape or object backup to tape jobs, Veeam Backup & Replication rounds the
protected amount to 500 GB separately for each data source and calculates the number of instances
required to protect each of them. After that, it sums up the total number of license instances to consume
for unstructured data backup or for unstructured data backup to tape.

• If the same data source is protected by more than one unstructured data backup job, to calculate the size
of the protected amount of data Veeam Backup & Replication first sums the size of the source data
protected by all the jobs. After that, it rounds the overall protected amount of data down to 500 GB and
calculates the license capacity to consume for the unstructured data backup.

• Unstructured data sources processed with backup copy and tape jobs are not regarded as protected data
sources and do not consume license instances. These types of jobs provide an additional protection level
for unstructured data sources that are already protected with backup jobs .

• Veeam Backup & Replication calculates the protected amount of data for each data source during every
run of the unstructured data backup job or unstructured data backup to tape job that protects data on this
data source and keeps the result for 30 days. To calculate the license capacity to consume for the data
source protection, Veeam Backup & Replication takes the largest protected amount of data on the data
source within the last 30 days.

If the size of the protected data reduces and does not increase or the data source is removed from the
unstructured data backup job or unstructured data backup to tape job, after 30 days
Veeam Backup & Replication recalculates the protected amount of data and automatically revokes the
excessively consumed license capacity. You can manually revoke the licenses without waiting for 30 days,
as described in the Revoking License section. During the next unstructured data backup job or
unstructured data backup to tape job run, Veeam Backup & Replication will recalculate the license capacity
consumption as of the current date.

• If the same data source is protected by more than one unstructured data backup job, to calculate the size
of the protected amount of data Veeam Backup & Replication first sums the size of the source data
protected by all the jobs. After that, it rounds the overall protected amount of data down to 500 GB and
calculates the license capacity to consume for the unstructured data backup support.

• If a unstructured data backup job protects several file shares residing on the same NAS device (the same
share root or NAS filer), the approach to calculating license consumption depends on how the file shares
are added to the infrastructure:

o If you have added the whole share root (\\root\) to the infrastructure and the file backup job
protects shares \\root\share1 and \\root\share2, Veeam Backup & Replication first sums the
protected amount of both file shares, rounds it down to 500 GB, and then calculates the license
consumption to consume for file backup support.

o If you have separately added shares \\root\share1 and \\root\share2 to the infrastructure and
the file backup job protects both of them, Veeam Backup & Replication first rounds the protected
amount for each file share down to 500 GB, separately calculates the license capacity to consume for
each file share, and then sums the license capacity to calculate the total license capacity to consume
for file backup support.

• Unstructured data backup to an object storage requires a license. Thus, this feature is not supported in the
Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions Comparison.

• Unstructured data restore from an object storage does not require a license. Thus, this feature is
supported in the Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions
Comparison.

266 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Types of Licenses
Veeam Software offers the following types of licenses for Veeam Backup & Replication:

Paid Licenses
• Sub scription license — license that expires at the end of the subscription term. The Subscription license
term is normally 1-3 years from the date of license issue.

• P erpetual license — permanent license. The support and maintenance period included with the license is
specified in months or years. Typically, one year of basic support and maintenance is included with the
Perpetual license.

• Rental license — license with the license expiration date set according to the chosen rental program
(normally 1-12 months from the date of license issue). The Rental license can be automatically upda ted
upon expiration.

Rental licenses are provided to Veeam Cloud & Service Provides (VCSPs) only. For more information, see
the Rental License section in the Veeam Cloud Connect Guide.

Free Licenses
• E valuation license — license used for product evaluation. The Evaluation license is valid for 30 days from
the moment of product download.

• NFR license — license used for product demonstration, training and education. The person to whom the
license is provided agrees that the license is not for resell or commercial use.

• P romo license — license that grants additional instances. You can install it only on top of an existing
Perpetual or Subscription license (primary license). The primary license can have any units (only sockets,
only instances, or both). Number of additional instances and duration of promo period are decided by a
sales representative.

267 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Instance Consumption for Object Storage
Backup, File Backup and File to Tape Jobs
For unstructured data backup and unstructured data backup to tape, there are the following peculiarities in
calculating the number of license instances to consume:

• Veeam Backup & Replication rounds the protected amount of data for each file share or object storage
down to 500 GB.

• One license instance covers 500 GB of the protected amount of data.

• When your unstructured data sources are protected with file backup to tape or object storage backup to
tape jobs, Veeam backup files are excluded from the instance consumption calculation. These files have
the following extensions: VAB, VBM, VBK, VIB, VRB, VSB, VLB, VSM, VLM, VOM, VACM, VASM, VSOURCE,
VSOURCETEMP, VSTORE, VSTORETEMP, VSLICE, VBASKET, VLIST, VCACHE, VBLOB, BCO, ADB .

• If different data sources are protected by different file backup or object storage backup jobs or by
different file backup to tape or object backup to tape jobs, Veeam Backup & Replication rounds the
protected amount to 500 GB separately for each data source and calculates the number of instances
required to protect each of them. After that, it sums up the total number of license instances to consume
for unstructured data backup or for unstructured data backup to tape.

• Veeam Backup & Replication calculates the protected amount of data for each data source during every
run of the unstructured data backup job or unstructured data backup to tape job that protects data on this
data source and keeps the result for 30 days. To calculate the number of license instances to consume for
the data source protection, Veeam Backup & Replication takes the largest protected amount of data on
the data source within the last 30 days.

If the size of the protected data reduces and does not increase or the data source is re moved from the
unstructured data backup job or unstructured data backup to tape job, after 30 days
Veeam Backup & Replication recalculates the protected amount of data and automatically revokes the
excessively consumed license instances. You can manually revoke the licenses without waiting for 30
days, as described in the Revoking License section. During the next unstructured data backup job or
unstructured data backup to tape job run, Veeam Backup & Replication will recalculate the license
instance consumption as of the current date.

• If the same data source is protected by more than one unstructured data backup job, to calculate the size
of the protected amount of data Veeam Backup & Replication first sums the size of the source data
protected by all the jobs. After that, it rounds the overall protected amount of data down to 500 GB and
calculates the number of license instances to consume for the unstructured data backup support.

• If a unstructured data backup job protects several file shares residing on the same NAS device (the same
share root or NAS filer), the approach to calculating license consumption depends on how the file shares
are added to the infrastructure:

o If you have added the whole share root (\\root\) to the infrastructure and the file backup job
protects shares \\root\share1 and \\root\share2, Veeam Backup & Replication first sums the
protected amount of both file shares, rounds it down to 500 GB, and then calculates the number of
license instances to consume for file backup support.

o If you have separately added shares \\root\share1 and \\root\share2 to the infrastructure and
the file backup job protects both of them, Veeam Backup & Replication first rounds the protected
amount for each file share down to 500 GB, separately calculates the number of license instances to
consume for each file share, and then sums the license instances to calculate the total number of
license instances to consume for file backup support.

268 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Unstructured data backup to an object storage requires a license. Thus, this feature is not supported in the
Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions Comparison.

• Unstructured data restore from an object storage does not require a license. Thus, this feature is
supported in the Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions
Comparison.

Examples
Ca se 1

If the protected amount of data for the file share is 499 GB or less, Veeam Backup & Replication rounds it down
to 0 GB. In this case, protection of this file share will not consume license instances.

If the protected amount of data for the file share is 590 GB or 990 GB, Veeam Backup & Replication rounds it
down to 500 GB. In this case, protection of this file share will consume 1 license instance.

Ca se 2

If the protected amount of data for the file share is 1000 GB after rounding, Veeam Backup & Replication
divides this amount by 500 GB to calculate the number of instances to consume:

1000 GB / 500 GB = 2 license instances

Ca se 3

You have 2 file shares File Share 1 (990 GB) and File Share 2 (890 GB) each protected by a separate file backup
job. In this case, Veeam Backup & Replication rounds the protected amount of each file share down to 500 GB,
calculates the number of license instances required to protect each of the file shares. After that, it sums the
calculated number of license instances required to protect the shares:

990 GB ~ 500 GB = 1 license instance

890 GB ~ 500 GB = 1 license instance

1 + 1 = 2 — protection of 2 file shares with separate file backup jobs consumes 2 license instances.

Ca se 4

You have a file share with the protected amount of data 1490 GB. Veeam Backup & Replication runs the file
backup job and after rounding down the amount, it calculates that it will consume 2 license instances for
protecting this file share:

1490 GB ~ 1000 GB = 2 license instances

Two days later, the size of the file share increases to 1510 GB. Veeam Backup & Replication runs the file backup
job and recalculates the number of license instances to consume based on the increased size of the NAS share:

1510 GB ~ 1500 GB = 3 license instances

Two days later, the size of the file share decreases back to 1490 GB and does not increase any more. Although
the protected amount of data decreases, for the next 30 days Veeam Backup & Replication uses value 1510 GB
as a basis to calculate the consumption of license instances.

30 days later, Veeam Backup & Replication runs the file backup job and recalculates the number of instances to
consume taking into account that the largest protected amount of data within the last 30 days is 1490 GB. After
that, protection of the file share starts consuming 2 instances again.

Ca se 5

269 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You have a file share (100 GB) protected by 2 file backup jobs (1 and 2). During the 1st run of job 1,
Veeam Backup & Replication rounds the protected amount down to 500 GB (0 GB) and calculates that the
protection of this file share with job 1 does not consume license instances. After that the file share size incr eases
to 270 GB. During the 1st run of job 2 which is scheduled after the increase of the file share,
Veeam Backup & Replication calculates amount of data protected by all file backup jobs protecting this file
share:

100 GB (run 1 of job 1) + 270 GB (run 1 of job 2) = 370 GB

Veeam Backup & Replication rounds the protected amount down to 500 GB (0 GB) and calculates that the
protection of this file share with backup job 1 and 2 does not consume license instances. After that the file share
size remains 270 GB. During the 2nd run of job 1, Veeam Backup & Replication calculates amount of data
protected by all file backup jobs protecting this file share:

270 GB (run 2 of job 1) + 270 GB (run 1 of job 2) = 540 GB

Veeam Backup & Replication rounds the protected amount down to 500 GB (500 GB) and calculates that the
protection of this file share with backup job 1 and 2 now consumes 1 license instance.

Ca se 6

You have a single NAS device with 2 NFS file shares residing on it: \\root\share1 (490 GB) and
\\root\share2 (600 GB). You have added the root server folder (\\root\) of this NAS device as an NFS file
share to the infrastructure. The file shares \\root\share1 and \\root\share2 are added to one file backup
job. In this case, Veeam Backup & Replication sums the protected amount of both file shares, rounds it down to
500 GB, and then calculates the number of license instances:

490 GB + 600 GB = 1090 GB ~ 1000 GB = 2 — protection of 2 file shares in this case consumes 2 license
instances.

Ca se 7

You have a single NAS device, but you have added 2 of its shared folders \\root\share1 (490 GB) and
\\root\share2 (600 GB) as separate file shares to the inventory. The file shares \\root\share1 and
\\root\share2 are added to one file backup job. In this case, Veeam Backup & Replication first rounds the
protected amount for each file share down to 500 GB, separately calculates the number of license instances to
consume for each file share, and then sums the license instances:

490 GB ~ 0 GB = 0 license instances

600 GB ~ 500 GB = 1 license instance

0 + 1 = 1 — protection of 2 file shares in this case consumes 1 license instance.

270 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Obtaining and Renewing License
You can obtain an Evaluation or paid license for the product when you download the product from the Veeam
website.

Obtaining Paid License


To obtain a paid license, refer to the Veeam Backup & Replication Pricing page.

To obtain a Perpetual Instance license, find a reseller.

Obtaining Evaluation License


To obtain an Evaluation license:

1. Sign in to veeam.com.

2. On the Download Veeam products page, click the product link.

3. In the Get trial key section, click the Request Trial Key link to download the Evaluation license.

Renewing License
To renew your maintenance plan, contact Veeam Renewals Team at [email protected].

If you have a Perpetual or Subscription license, you can also renew your license contract online.

To renew the license:

1. From the main menu, select License.

2. In the License Information window, click Renew.

Veeam Backup & Replication will forward you to the Renewals page of Veeam website, where you can select
your new maintenance plan. When your contract is renewed, you have to update your license.

271 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Note that the Renew option is subject to restrictions. If online renewal is not possible for your account, you will
be redirected to the Renewal Request page. There you will be able to submit a request for Veeam Renewals
Team.

272 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing License
When you install Veeam Backup & Replication, you are asked to specify a path to the license file. If you do not
specify a path to the license file, Veeam Backup & Replication will run in the Veeam Backup & Replication
Community (free) Edition. For more information, see Veeam Backup & Replication Community Edition.

273 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can install or change the license after product installation:

1. From the main menu, select License.

2. In the License Information window, click Install.

3. Browse to the LIC file and click Op en.

274 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Licenses in Veeam Backup Enterprise Manager
If backup servers are connected to Veeam Backup Enterprise Manager, Veeam Backup Enterprise Manager
collects information about all licenses installed on backup servers. When Veeam Backup Enterprise Manager
replicates databases from backup servers, it also synchronizes license data: checks if the license installed on the
backup server coincides with the license installed on the Veeam Backup Enterprise Manager server. If the
licenses do not coincide, the license on the backup server is automatically replaced with the license installed on
the Veeam Backup Enterprise Manager server.

For information on Veeam Backup Enterprise Manager license, see the Licensing section of the Veeam Backup
Enterprise Manager Guide.

275 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Merging Licenses
Merging licenses is an option for customers who have a Perpetual Socket license. If you have a Perpetual Socket
license, and want to also protect, for example, your cloud or physical workloads, or work with Veeam plug -ins,
you can obtain an instance license and merge it with the socket license.

TIP

Merging licenses is a built-in mechanism that allows you to merge two different license types (Socket and
Instance). If you want to merge several licenses of the same type (Socket and Socket, Instance and
Instance) to obtain a single license key file, you can use the merge tool in the Customer Portal. For more
information on merging licenses in the Customer Portal, see this Veeam KB article. For more information on
merge rules and exceptions for the Customer Portal merging process, see the License Key Merge section of
the Veeam Licensing Policy.

Under the merged license, the following workloads will consume a Socket license:

• VMware vSphere and Microsoft Hyper-V VMs

• Application servers protected by Veeam Plug-ins (only for application servers running in VMs of a virtual
infrastructure registered with Veeam Backup & Replication)

• VMs protected by Veeam Agents (only for VMs of a virtual infrastructure registered with
Veeam Backup & Replication)

Other workloads are processed per instance.

License Types Available for Merging


You can merge licenses of the following types:

• Perpetual Socket license and Subscription Instance license

• Perpetual Socket license and Perpetual Instance license

License Packages Available for Merging


You can merge licenses of the following packages:

Ty p e of license E ssentials Ba ckup Suite ONE


Sock et Sock et Sock et Sock et

E ssentials
Instance

Ba ckup
Instance

Suite
Instance

276 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ty p e of license E ssentials Ba ckup Suite ONE
Sock et Sock et Sock et Sock et

ONE
Instance

Support Terms in Merged Licenses


If the licenses that you want to merge have different support expiration date, the merged license will take the
support that expires first.

Merging Licenses
Before you merge licenses, check the following prerequisites:

• The license type and package allow merging.

• The company names are identical in both licenses. Company name check is case sensitive.

To merge licenses, install a new license over the already installed license. For more information, see Installing
License.

IMP ORTANT

If the license types do not allow merging, the newly installed license will replace the previous license.

277 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing License Information
You can view details of the installed license in the License Information window.

To open the License Information window, from the main menu select License.

The following details are available for the current license:

• Sta tus — license status ( Valid , Invalid , Expired , Not Installed , Warning , Error).

• Ty p e — license type ( Perpetual, Subscription, Rental, Evaluation, NFR, Free).

• E d ition — license edition ( Community , Standard , Enterprise, Enterprise Plus).

• Sup port ID — support ID required for contacting Veeam Support.

• Licensed to — name of a person or organization to which the license was issued.

• Cloud Connect Provider — shows if you can use Veeam Backup & Replication to offer cloud repository as a
service and disaster recovery as a service to your customers ( Enterprise, Yes, No). For more information on
Veeam Cloud Connect, see Veeam Cloud Connect Guide.

• P a ckage1 — Veeam license pack: Essentials , Backup , Suite, ONE .

• Sock ets — number of sockets that you can use to protect workloads.

• Instances — number of instances that you can use to protect workloads.

• P romo instances — number of additional instances granted by the Promo license.

• E x piration date — date when the license expires.

278 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Sup port expiration date — date when expires the support and maintenance specified by Veeam Licensing
Policy. Valid for Perpetual Socket and Perpetual Instance licenses.

• P romo expiration date — date when the Promo license expires.

• Tota l instances including promo — number of all available instances, regular and promo added up.

• Ca pacity — protected front end capacity (in TiB) for unstructured data backup.
1
Starting from version 11, the Starter pack license is replaced with Essentials pack. If you were using Starter pack license, you
will need either to agree to update the license during the VBR upgrade to version 11 or to download the Essential pack
license file from Veeam Customer portal and install it manually.

To enable automatic license update, select the Up date license automatically check box. For more information,
see Updating License Automatically.

Viewing Information on Sockets


With socket licenses, Veeam Backup & Replication applies a license to the virtualization host on which the
processed VMs reside.

To view to which objects the license is currently applied, open the Sock ets tab.

For peculiarities of socket licensing, see the Licensing section.

Viewing Information on Instances


With instance licenses, Veeam Backup & Replication applies a license to a protected workload. The number of
license instances that a protected workload consumes dep ends on the workload type and product edition. For
details, see Veeam Licensing Policy.

279 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To view to which objects the license is currently applied, open the Instances tab.

For peculiarities of instance licensing, see the Licensing section.

By default, Veeam Backup & Replication allows Veeam Agents to connect to the Veeam backup server and
consume instances in the license. If you do not want Veeam Agents to consume instances, clear the Allow
unlicensed agents to consume instances check box. For more information on Veeam Agents licensing, see
Veeam Agent Management Guide.

Viewing Information on Capacity


With a capacity license, Veeam Backup & Replication applies the license to protected unstructured data sources.
For details, see Veeam Licensing Policy.

To view which data sources currently consume the license capacity, open the Ca pacity tab.

280 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For peculiarities of capacity licensing, see the Licensing section.

281 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Revoking License
You can revoke licenses from protected workloads or licensed hosts, and re -apply them to other objects that
you plan to protect. License revoking can be helpful, for example, if a licensed host goes out of service or you
do not want to protect some workloads anymore.

NOTE

If you manually revoke license instances allocated for an unstructured data source, the next run of the
unstructured data backup job that protects this data source will trigger the recalculation of the data source
protected size and reallocation of license instances that Veeam Backup & Replication will consume. For
more information, see the Instance Consumption for Object Storage Backup, File Backup and File to Tape
Jobs section.

To revoke a license, do the following:

1. From the main menu, select License.

2. In the License Information window:

o For protected workloads, open the Instances tab and click Ma nage.

o For licensed hosts, open the Sock ets tab and click Ma nage.

3. In the displayed window, select a protected workload or a licensed host and click Revoke.
Veeam Backup & Replication will revoke the license from the selected object, and the license will be freed
for other objects in the backup infrastructure.

The steps to revoke licenses for Veeam Agent machines are slightly different. For more information, see the
Viewing Licensed Veeam Agents and Revoking License section in the Veeam Agent for Microsoft Windows User
Guide.

282 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing License
You can remove the installed license. When you remove a license, Veeam Backup & Replication will switch to the
Veeam Backup & Replication Community Edition. For more information, see Veeam Backup & Replication
Community Edition.

You can also remove a part of merged license. If you do so, Veeam Backup & Replication will operate under the
other part of the merged license. For more information, see Merging Licenses.

To remove a Promo license, remove the license on top of which it was installed.

To remove a license, do the following:

1. From the main menu, select License.

283 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the License Information window, click Remove.

If you have both socket and instance licenses, you will be asked which license you want to remove.

284 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Select the license you want to remove and confirm the removal.

285 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Exceeding License Limit
For Veeam Universal Licenses, Veeam Backup & Replication allows you to protect more workloads than covered
by the number of instances specified in the license. An increase in the number of protected workloads is allowed
throughout the duration of the contract (license key).

The license limit can be exceeded by a number of instances, or a percenta ge of the total number of instances
specified in the license (depends on which number is greater). The exceeding limit varies according to the
license type.

License Type E x ceeding Limit Description

Sock et license Not allowed Workloads that are exceeding the license limit
are not processed.

Veeam Universal Less than 10 instances (or 10% of the All protected workloads are processed normally,
License (VUL) total instance count) Veeam Backup & Replication does not display a
warning message.
License
a utoupdate
E NABLED 10–20 instances (or 10%–20% of the All protected workloads are processed normally.
total instance count)
Once a week when you open the
Veeam Backup & Replication console, a warning
message is displayed notifying that you are out
of compliance with the Veeam Licensing Policy.

More than 20 instances (or 20% of Workloads that are exceeding the license limit
the total instance count) beyond 20 instances (or 20% of the total
instance count) are not processed.

Every time you open the


Veeam Backup & Replication console, a warning
message is displayed notifying that you are out
of compliance with the Veeam Licensing Policy.

Veeam Universal Less than 5 instances (or 5% of the All protected workloads are processed normally,
License (VUL) total instance count) Veeam Backup & Replication does not display a
warning message.
License
a utoupdate
DISABLED 5–10 instances (or 5%–10% of the All protected workloads are processed normally.
total instance count)
Once a week when you open the
Veeam Backup & Replication console, a warning
message is displayed notifying that you are out
of compliance with the Veeam Licensing Policy.

286 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
License Type E x ceeding Limit Description

More than 10 instances (or 10% of Workloads that are exceeding the license limit
the total instance count) beyond 10 instances (or 10% of the total
instance count) are not processed.

Every time you open the


Veeam Backup & Replication console, a warning
message is displayed notifying that you are out
of compliance with the Veeam Licensing Policy.

Rental license See the Rental License section in the Veeam Cloud Connect Guide.

For example, you have a Subscription license with 500 instances to protect your workloads. According to the
table above, you are allowed to use up to 10 instances or 10% of the total instance count (whichever number is
greater) over the license limit. As the number of instances in your license is 500, you are allowed to use
additional 50 instances (50 makes 10% of 500, and 50 is greater than 10). Consider the following:

• Until the license limit is not exceeded by more than 5% of the total instance count (up to 25 instances),
Veeam Backup & Replication processes all protected workloads with no restrictions.

• When the license limit is exceeded by 5%–10% (25 to 50 instances), Veeam Backup & Replication
processes protected workloads, and displays a warning message once a week when you open the
Veeam Backup & Replication console. In the message, Veeam Backup & Replication provides information
on the number of exceeded instances and the number of instances by which the license can be further
exceeded.

• If the license limit is exceeded by more than 10% (50 instances and more), Veeam Backup & Replication
does not process the workloads exceeding the limit, and displays a warning message every time you open
the Veeam Backup & Replication console. In the message, Veeam Backup & Replication provides
information on the number of instances by which the license is exceeded.

When the license limit is exceeded, the logs will include the number of instances necessary to finish the job
successfully.

NOTE

Capacity-based (per-TB) license limit for unstructured data backup cannot be exceeded.

287 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
License Expiration
When the license expires, Veeam Backup & Replication behaves in the following way depending on the license
type:

• Evaluation and NFR licenses: Veeam Backup & Replication will stop processing workloads.

• Paid licenses: Veeam Backup & Replication will switch to the grace period.

• Promo license: Veeam Backup & Replication will remove the granted instances and stop processing
workloads for them. Promo license does not have a grace period. Upon expiration of the primary license,
the promo license will also expire, regardless of its own expiration date.

Perpetual Socket and Perpetual Instance licenses do not expire. However, such licenses have support expiration
date. Veeam Backup & Replication will inform you about the support expiration date.

Grace Period
To ensure a smooth license update and provide sufficient time to install a new license file,
Veeam Backup & Replication offers a grace period. Grace period is available for paid licenses.

During the grace period, you can perform all types of data protection and disaster recovery operations.
However, Veeam Backup & Replication will inform you about the license expiration when you open the
Veeam Backup & Replication console. The license status in the License Information window will appear as
Expired .

You must update your license before the end of the grace period. If you do not update the license,
Veeam Backup & Replication stops processing workloads. All existing jobs fail with the Error status. However,
you will be able to restore machine data from existing backups.

Grace Period Duration


Before the license expires, Veeam Backup & Replication notifies you about soon license expiration.

The number of days for notification and grace period depends on the type of license:

License Type License Expiration Notification Gra ce Period

Sub scription 30 days 30 days

P erpetual n/a
14 days before Support expiration date
Instance

P erpetual n/a
14 days before Support expiration date
Sock et

Rental 7 days 60 days

E valuation 30 days 0 days

288 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
License Type License Expiration Notification Gra ce Period

NFR 30 days 0 days

P romo 7 days n/a

Switching to Veeam Backup & Replication Community Edition


If you do not want to renew your license, you can switch to the free product version named
Veeam Backup & Replication Community (free) Edition. For more information, see Veeam Backup & Replication
Community Edition.

To do so, remove your license. For more information, see Removing License.

Expiration of Merged Licenses


When the merged license expires, Veeam Backup & Replication stops processing workloads after the grace
period.

If you merged licenses with different expiration dates, the merged license will expire on the date that is closer.
For example, if you merged a Perpetual license and a Subscription license, the expiration date will be inhe rited
from the Subscription license.

In such case, you can update your Subscription license or continue using the Perpetual license. To continue using
the Perpetual license, remove the Subscription license. For more information, see Removing License.

289 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating License
To be able to use all data protection and disaster recovery features, you must update your license upon expiry.
There are two methods to update the license in Veeam Backup & Replication:

• Update the license manually.

• Update the license automatically.

NOTE

When updating the license, Veeam Backup & Replication requires internet access to connect to the Veeam
License Update Server. If your network is not connected to the internet, instead of update you can
download a new license file from my.veeam.com and then install it. For more information on license
installation, see Installing License.

290 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating License Manually
You can update the license manually on demand. When you update the license manually,
Veeam Backup & Replication connects to the Veeam License Update Server, downloads a new license from it (if
the license is available) and installs it on the backup server.

IMP ORTANT

To update the license, the backup server in your Veeam Backup & Replication installation must have access
to the Veeam License Update Server (vbr.butler.veeam.com, autolk.veeam.com) using TCP on port 443.

The new license key differs from the previously installed license key in the license expiration dat e or support
expiration date. If you have obtained a license for a greater number of instances, counters in the new license
also display the new number of license instances.

To update the license:

1. From the main menu, select License.

2. In the License Information window, click Up d ate Now.

Statistics on the manual license update process is available under the Sy stem node in the History view. You can
double-click the License key auto-update job to examine session details for the license update operation.

291 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Manual License Update Results
Manual license update can complete with the following results:

• Op eration is successful. A new license key is successfully generated, downloaded and installed on the
backup server or Veeam Backup Enterprise Manager server.

• A new license is not required. The currently installed license key does not need to be updated.

• The Veeam License Update Server has failed to g enerate a new license . Such situation can occur due to
some error on the Veeam License Update Server side.

• Veeam Backup & Replication has received a n invalid answer. Such situation can occur due to connectivity
issues between the Veeam License Update Server and Veeam Backup & Replication.

• Licensing by the contract has been terminated. In such situation, Veeam Backup & Replication
automatically disables automatic license update on the backup server or Veeam Backup Enterprise
Manager server.

292 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating License Automatically
You can instruct Veeam Backup & Replication to automatically update the license installed on the backup server
or Veeam Backup Enterprise Manager server. With automatic license update, you do not need to download and
install the license manually each time when you purchase the license extension. If the automatic update option
is enabled, Veeam Backup & Replication proactively communicates with the Veeam License Update Server to
obtain and install a new license before the current license expires.

Requirements and Limitations for Automatic License Update


• Automatic license update is not available in the Veeam Backup & Replication Community Edition.

• Only licenses that contain a real contract number in the Support ID can be updated with the Up d ate
license key automatically option.

• If you are managing backup servers with Veeam Backup Enterprise Ma nager, all license management tasks
must be performed in the Veeam Backup Enterprise Manager console. Automatic update settings
configured in Veeam Backup Enterprise Manager override automatic update settings configured in
Veeam Backup & Replication.

For example, if the automatic update option is enabled in Veeam Backup Enterprise Manager but disabled
in Veeam Backup & Replication, automatic update will be performed anyway. For more information, see
the Veeam Backup Enterprise Manager User Guide.

NOTE

Veeam Backup & Replication does not automatically update an existing per-VM or socket license that was
obtained for an earlier version of the product to a new instance license.

To overcome this issue, after you upgrade to Veeam Backup & Replication 11, you must obtain in the Veeam
Customer Support Portal a new instance license and install it on the backup server manually.

How Automated License Update Works


To update installed licenses automatically, Veeam Backup & Replication performs the following actions:

1. After you enable automatic license update, Veeam Backup & Replication starts sending requests to the
Veeam License Update Server on the web (autolk.veeam.com) and checks if a new license key is available.
Veeam Backup & Replication sends requests once a week. Communication with the Veeam License Update
Server is performed over the HTTPS protocol.

2. Seven days before the expiration date of the current license, Veeam Backup & Replication starts sending
requests once a day.

3. When a new license key becomes available, Veeam Backup & Replication automatically downloads it and
installs on the backup server or Veeam Backup Enterprise Manager server.

The new license key differs from the previously installed license key in the license expiration date and support
expiration date. If you have obtained a license for a greater number of instances, counters in the new license
also display the new number of license instances.

293 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Automatic License Update Results
Automatic license update can complete with the following results:

• Op eration is successful. A new license key is successfully generated, downloaded and installed on the
backup server or Veeam Backup Enterprise Manager server.

• A new license is not required. The currently installed license key does not need to be updated.

• The Veeam License Update Server has failed to g enerate a new license. Such situation can occur due to
some error on the Veeam License Update Server side.

• Veeam Backup & Replication has received a n invalid answer. Such situation can occur due to connectivity
issues between the Veeam License Update Server and Veeam Backup & Replication.

• Licensing by the contract has been terminated. In such situation, Veeam Backup & Replication
automatically disables automatic license update on the backup server or Veeam Backup Enterprise
Manager server.

Automatic Update Retries


If Veeam Backup & Replication fails to update the license, it displays a notification in the session report and
sends an email notification to users specified in the global email settings (if global email settings are configured
on the backup server). You can resolve the issue, while Veeam Backup & Replication will keep retrying to update
the license.

Veeam Backup & Replication retries to update the license key in the following way:

• If Veeam Backup & Replication fails to establish a connection to the Veeam License Update Server, retry
takes place every 60 min.

• If Veeam Backup & Replication establishes a connection but you are receiving the “General license key
generation error has occurred” message, the retry takes place every 24 hours.

The retry period ends one month after the license expiration date or the support expiration date (whichever is
earlier). The retry period is equal to the number of days in the month of license expiration. For example, if the
license expires in January, the retry period will be 31 day; if the license expires in April, the retry period will be
30 days.

If the retry period is over but the new license has not been installed, the automatic update feature is
automatically disabled.

For more information about error cases, see the License Update Session Data section in the Veeam Backup
Enterprise Manager Guide.

Enabling Automatic License Update


By default, automatic license update is disabled. To enable automatic license update:

1. From the main menu, select License.

294 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the License Information window, select the Up date license automatically (enabled usage reporting)
check box.

During the installation of a Subscription or Rental license, you will see a pop-up dialog window with a
suggestion to enable automatic license update.

Statistics on the automatic license update process is available under the Sy stem node in the History view. You
can double-click the License k ey auto-update job to examine session details for the scheduled or ad -hoc
automatic license update.

NOTE

[For Rental, Subscription, Perpetual licenses] Enabling license auto update activates Automatic License
Usage Reporting.

295 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Automatic License Usage Reporting
When license auto update is enabled for Rental, Subscription, Perpetual licenses, Veeam Backup & Replication
performs automatic license usage reporting.

As part of reporting, Veeam Backup & Replication collects statistics on the current license usage and sends it
periodically to the Veeam License Update Server. The report provides information about the contract ID,
product installation ID, and the maximum number of licensed objects that were manag ed by
Veeam Backup & Replication over the past week (high watermark). The reporting process runs in the background
mode, once a week at a random time and day.

The type of reported objects is defined by the product and the installed license. The report can include
information about VMs, workstations or servers protected with Veeam backup agents, and so on.

The collected data does not include information on the usage of Veeam Backup & Replication by any individual
person identifiable for Veeam, or any data protected by Veeam Backup & Replication.

The collected data allows our back-end system to automatically approve your monthly usage reports as long as
they do not deviate from the high watermark value significantly. This helps to keep our report processing co sts
low, thus allowing us to maintain low rental prices for our solution. Veeam may also use collected data for any
other internal business purposes it deems appropriate, including (but not limited to) evaluation, improvement
and optimization of Veeam licensing models.

By enabling license auto update you agree with collection, transmission and use of the reporting data. You must
not enable license auto update in case you do not agree with such collection, transmission and use.

296 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deployment
This section describes how to install, upgrade, update and uninstall Veeam Backup & Replication and the
Veeam Backup & Replication console, both through UI and using commands for silent deployment.

297 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installation
To start working with Veeam Backup & Replication, you must configure a backup server — install
Veeam Backup & Replication on a machine that meets the system requirements. To do this, you can use the
setup wizard or install the product in the unattended mode.

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

298 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Veeam Backup & Replication
Before you install Veeam Backup & Replication, check prerequisites. Then use the Veea m Backup & Replication
setup wizard to install the product.

Before You Begin


Before you install Veeam Backup & Replication, check the following prerequisites:

• A machine on which you plan to install Veeam Backup & Replication must meet the system requirements.
For more information, see System Requirements.

• Veeam Backup & Replication must not be installed directly on a Hyper-V host. Such installation may lead
to unpredictable system behavior. Instead, create a VM on the host and install
Veeam Backup & Replication on the VM.

• A user account that you plan to use for installation must have sufficient permissions. For more
information, see Permissions.

• Backup infrastructure components communicate with each other over specific ports. These ports must be
open. For more information, see Ports.

• You must remove Veeam Backup & Replication components of versions that are not supported by the
upgrade procedure from the target machine. You may also need to remove earlier versions of other Veeam
products and components.

• Before deploying Veeam Backup & Replication, define where the Veeam Backup & Replication server will
be located. Depending on what kind of protection are you planning to use, the
Veeam Backup & Replication server should be located on the source site or the Disaster Recover y site.

o W hen replication is used: If you plan to use replication , the Veeam Backup & Replication server
should be deployed in the disaster recovery site. In this case, if the production host crashes,
Veeam Backup & Replication will automatically fail over to the replica without any manual operations.
The source backup infrastructure still can be managed with the same Veeam Backup & Replication
server with the help of backup proxies deployed in the source site.

o W hen only backup features are used: If you plan to use Veeam Backup & Replication for backup jobs
only, the backup server should be placed in the production site.

• We strongly recommend that no highly-transactional and business-critical software is deployed on the


same machine as the Veeam backup server. This could be (but not limited to) software such as Active
Directory, Exchange Server or other intensive production databases on the SQL server instance. We
recommend that only Veeam Backup & Replication runs on the b ackup server.

Configuration Database
Before deploying Veeam Backup & Replication, decide which database engine and version you need to use:

• If you do not prepare a database engine in advance, Veeam Backup & Replication will automatically install
PostgreSQL 15.1 locally on the backup server.

299 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Decide if you need the database engine installed on the same server as Veeam Backup & Replication or on
a remote server. Veeam Backup & Replication requires a database engine deployed either locally on the
backup server or remotely.

It is recommended to run the database engine instance locally to eliminate latency issues. However, in
some scenarios a remote instance can be the better choice:

o High Availability. SQL Clustering and Always On Availability Group on external SQL Servers can be
used for high availability of the configuration database. To learn about the configuration details, see
this Veeam KB article.

o Licensing. Some enterprises have dedicated virtual clusters for SQL Servers due to licensing
constraints. In such cases, you can place the Veeam configuration database on an existing instance to
lower the total cost of ownership.

• If you prefer to use an Express Edition of Microsoft SQL Server as your database engine, note that its
usage is limited by 10 GB of configuration database. The Express Edition is enough for evaluation purposes
and not very large environments (<500 VMs). If your infrastructure is large (more than 500 VMs), you may
consider to install a Microsoft SQL Server in advance.

• If Microsoft SQL Server is installed by the previous product version, Veeam Backup & Replication will
connect to the existing configuration database, upgrade it (if necessary) and use it for work.

• If you already have an installed instance of PostgreSQL and want to use it for the configuration database,
ensure that the LocalSystem account is added to your PostgreSQL configuration to successfully run the
installation of Veeam Backup & Replication.

Configuring PostgreSQL Instance


The default PostgreSQL instance is configured to consume a minimum amount of resources, which may not be
enough for Veeam Backup & Replication performance.

When installing Veeam Backup & Replication, you can choose what PostgreSQL instance to use for the
Veeam Backup & Replication configuration database. You can use an already installed PostgreSQL instance or
install a new one.

• If you let the setup install a new PostgreSQL instance, it will be configured automatically.

• If you want to use an already installed PostgreSQL instance, make sure that the instance configuration is
sufficient for the Veeam Backup & Replication performance.

To adjust the configuration of an existing PostgreSQL instance, take the following steps before you install
Veeam Backup & Replication:

1. On a backup server, run the Set-VBRPSQLDatabaseServerLimits cmdlet. The cmdlet generates the
necessary PostgreSQL configuration and saves it to a dump SQL file.

Set-VBRPSQLDatabaseServerLimits -OSType <String> -CPUCount <number of CPU


cores> -RamGb <RAM in GB> -DumpToFile <file path>

For example:

Set-VBRPSQLDatabaseServerLimits -OSType Windows -CPUCount 16 -RamGb 32 -Du


mpToFile "C:\config.sql"

300 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. On the machine with the PostgreSQL instance where you want to deploy the Veeam Backup & Replication
configuration database, use the psql tool to apply the configuration from the dump file.

The tool is located in the PostgreSQL installation folder.

psgl -U <user> -f <file path>

For example:

psgl -U postgres -f "C:\config.sql"

After you apply the configuration from the dump file, all changes will be writte n into the
postgressql.auto.conf file located in the PostgreSQL installation folder. This file is loaded when the
service starts and takes precedence over the default PostgreSQL configuration file.

3. Include the pg_stat_statements library to the PostgreSQL configuration. To add the library, you can
manually edit the shared_preload_libraries option in the postgres.conf file.

Alternatively, you can do it by by executing the SQL code:

a. Check the content of the shared_preload_libraries variable.

SELECT * FROM pg_settings


WHERE name = 'shared_preload_libraries';

b. Add the pg_stat_statements library to the shared preloaded libraries.

▪ If the shared_preload_libraries value is empty, assign pg_stat_statements to the


shared_preload_libraries variable.

ALTER SYSTEM SET shared_preload_libraries = pg_stat_statements;

▪ If the shared_preload_libraries value is not empty, add pg_stat_statements to the


current value separated by comma.

ALTER SYSTEM SET shared_preload_libraries = <existing libraries>, pg


_stat_statements;

4. Restart the PostgreSQL service for the new configuration to take effect.

5. Install the pg_stat_statements extension. The extension is used to analyze the PostgreSQL
performance.

CREATE EXTENSION IF NOT EXISTS "pg_stat_statements";

301 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Related Topics
Planning Infrastructure

302 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Setup Wizard
To start the setup wizard:

1. Download the latest version of the Veeam Backup & Replication installation image from the Download
Veeam Products page.

2. Mount the installation image to the machine on which you plan to install Veeam Backup & Replication or
burn the image file to a flash drive or other removable storage device. If you plan to install
Veeam Backup & Replication on a VM, use built-in tools of the virtualization management software to
mount the installation image to the VM.

To extract the content of the ISO, you can also use the latest versions of utilities that can properly extract
data from ISOs of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun will open a splash screen. If Autorun is not available
or disabled, run the Setup.exe file from the image or disk.

4. In the splash screen, click Install.

IMP ORTANT

It is strongly recommended that you install Veeam Backup & Replication using Autorun or the Setup.exe
file. If you run other installation files from the ISO folders, you may miss some components that need to be
installed, and Veeam Backup & Replication may not work as expected.

303 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At the Select Veeam Backup & Replication Component step of the wizard, select Install
Veeam Backup & Replication.

To open Veeam Help Center from the setup wizard, click View Documentation.

304 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Read and Accept License Agreement
At the License Agreement step of the wizard, read Veeam License Agreement and licensing policy as well as
license agreements of 3rd party components that Veeam incorporates and license agreements of required
software. To accept the license agreements and continue installing Veeam Backup & Replication, click I Accept.

305 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Provide License File
At the License step of the wizard, specify what license you want to install for Veeam Backup & Replication. For
more information, see Licensing.

If a valid license is already installed on the machine, the setup wizard will inform you about it. In this case, you
can skip the P rovide License step and move to the next step of the wizard.

If you do not install a license, the product will operate in the Veeam Backup & Replication Community (free)
Edition. For more information, see Veeam Backup & Replication Community Edition.

To install a license, you have 2 options to choose from:

• Browse your local server or network locations for a license file:

a. Click Browse license file.

b. Select a valid license file for Veeam Backup & Replication.

• Select a license from your account at the Veeam web-site:

a. Click Sig n in with Veeam.

b. Enter your credentials for accessing the Veeam web-site and click Sig n in.

c. Select one of the available licenses and click Install selected license.

To install new licenses automatically when you renew or expand your contract, select the Up date license
a utomatically check box. If you enable the automatic license update, and therefore enable usage reporting, you
will double the number of workloads by which you can exceed your installed license. For more information, see
Exceeding License Limit.

306 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Install Missing Software
At the Sy stem Configuration Check step of the wizard, the setup wizard checks if the required software is
installed on the machine. If some of the required components are missing, the setup will try to install them
automatically. After the components are successfully installed, reboot is required. To reboot the machine, click
Reb oot.

If the setup wizard cannot install some of the required software components automatically, install them
manually and click Retry.

NOTE

If all required software is already installed on the machine, the Sy stem Configuration Check step will be
skipped. For more information on the necessary software, see System Requirements.

307 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Default Installation Settings
At the Rea dy to Install step of the wizard, you can select to install Veeam Backup & Replication with default
installation settings or specify custom installation settings.

• To use the default installation settings, click Install.

• To use custom installation settings, click Customize Settings. The setup wizard will include additional
steps that will let you configure installation settings.

The table below lists the default installation settings.

Setting Default Value Description

Installation folder C:\Program Folder where Veeam Backup & Replication will be
Files\Veeam\Backup and installed.
Replication

Guest catalog C:\VBRCatalog The VBRCatalog folder on a volume with the


folder maximum amount of free space.

The guest catalog folder stores indexing data for VM


guest OS files. Indexing data is required for browsing
and searching for VM guest OS files inside backups
and performing 1-click restore.

Service account LOCAL SYSTEM Account under which the Veeam Backup Service runs.

Da tabase engine PostgreSQL The setup wizard installs PostgreSQL 15.1 as a


database engine locally on the
Veeam Backup & Replication server.

SQL server <host_name>:5432 The local host name and port number to be used by
SQL server.

Da tabase name VeeamBackup The setup deploys the Veeam Backup & Replication
configuration database on the locally installed
instance of PostgreSQL.

Ca talog service 9393 The catalog service port is used by the Veeam Guest
p ort Catalog Service to replicate catalog data from
backup servers to Veeam Backup Enterprise
Manager.

Service port 9392 The service port is used by Veeam Backup Enterprise
Manager to collect data from backup servers. In
addition to it, the Veeam Backup & Replication
console uses this service port to connect to the
backup server.

308 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Setting Default Value Description

Secure connections 9401 The secure connections port is used by the mount
p ort server to communicate with the backup server.

RE ST API service 9419 This service port is used to access the


p ort Veeam Backup & Replication REST API.

Check for updates Automatically Veeam Backup & Replication will check for product
updates weekly. When a new product build is
published on the Veeam update server, a notification
is displayed in the Windows Action Center.

309 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Service Account Settings
The Service Account step of the wizard is available if you have selected to configure installation settings
manually.

You can select an account under which you want to run the Veeam Backup Service:

• LOCAL SYSTEM account (recommended, used by default)

• Custom user account

The user name of the custom account must be specified in the DOMAIN\USERNAME format and have the
following rights and permissions:

• The account must be a member of the Administrators group on the machine where
Veeam Backup & Replication is installed.

• The account must have db_owner rights for the configuration database.

Veeam Backup & Replication automatically grants the Log on as service right to the specified user account.

NOTE

You cannot use a gMSA for running the Veeam Backup Service.

310 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Database Engine and Instance
The Da tabase step of the wizard is available if you have selected to configure installation settings manually.

At this step of the wizard, you can choose a database engine (PostgreSQL or Microsoft SQL Server) for the
Veeam Backup & Replication configuration database, specify a new or existing instance where you want to
deploy the configuration database, and specify the authentication mode.

NOTE

Consider limitations and considerations in Before You Begin.

1. Select one of the following database engines that you want to use for the configuration database:

o PostgreSQL

o Microsoft SQL Server

2. Specify instance settings:

o [For PostgreSQL] You can use an already installed PostgreSQL instance or install a new one.

▪ To install a new PostgreSQL instance, select the Install new instance option. The setup will
install PostgreSQL 15.1 on the Veeam Backup & Replication server and create a database with
the VeeamBackup name.

▪ To use an already installed PostgreSQL instance, select the Use existing instance option. Enter
the instance name in the HOSTNAME:PORT format. In the Da tabase name field, specify a name
for the Veeam Backup & Replication configuration database.

IMP ORTANT
If you use the already installed PostgreSQL instance or make any changes in the machine
hardware, perform the additional configuration of the PostgreSQL instance, as described in
section Before You Begin.

311 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o [For Microsoft SQL Server] You can use an already installed Microsoft SQL Server database only.

i. In the SQL Server instance field, enter the instance name in the HOSTNAME\INSTANCE format or
select an instance from the drop-down list. You can also click Browse to choose a Microsoft SQL
Server on a remote machine.

312 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
ii. In the Da tabase name field, specify a name for the Veeam Backup & Replication configuration
database.

3. Select an authentication mode to connect to the database server instance: Microsoft Windows
authentication or native database server authentication. If you select the native authentication, enter
credentials of the database account.

If a configuration database with the specified name already exists (for example, it was created by a previous
installation of Veeam Backup & Replication), the setup wizard will notify about it. To connect to the detected
database, click Y es . If necessary, Veeam Backup & Replication will automatically upgrade the database to the
latest version.

313 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Perform Configuration Check
At the Configuration Check step of the wizard, the setup checks the Veeam Backup & Replication configuration.

If the check returns errors, solve their causes before continuing the installation. After you solve them, c lick
Retry to check if there are any issues left.

If the check returns warning or information messages, you can continue the installation and address them later.
However, we recommend that you closely investigate warning and information messages: if not pr operly
addressed, their causes may lead to serious problems with further system operation.

To view the details of a certain message, point the cursor to the line with the message. The pop -up box will
display the detailed description.

To copy a list of detected issues with detailed descriptions for further investigation, click Cop y list to clipboard.

314 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Specify Data Locations
The Da ta Locations step is available if you have selected to configure installation settings manually and to
install a new instance of the database server.

At this step of the wizard, you can specify the installation folder and where the write cache and indexing data
must be stored.

1. To change the default installation folder, click Browse next to the Installation path field.

By default, the setup wizard uses the following installation folder: C:\Program Files\Veeam\Backup
and Replication.

Veeam Backup & Replication setup wizard calculates the space available on the selected disk and displays
this information for your convenience.

2. To change the path to the folder where index files will be stored, click Browse next to the Guest file
sy stem catalog field.

By default, the setup wizard creates the VBRCatalog folder on a volume with the maximum amount of free
space, for example: C:\VBRCatalog.

3. [For VMware environments] The instant recovery cache folder stores the write cache for machines that are
started from backups during recovery verification or restore operations. To change the path to the IR
cache folder, click Browse next to the Instant recovery write cache field. Make sure that you have at least
10 GB of free disk space to store the write cache.

By default, the setup wizard creates the IR cache folder on a volume with the maximum amount of free
space, for example: C:\ProgramData\Veeam\Backup\IRCache.

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

315 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Specify Service Ports
The P ort Configuration step of the wizard is available if you have selected to configure installation settings
manually.

At this step of the wizard, you can customize port number values that will be used for communication between
backup infrastructure components. For more information about Veeam Backup & Replication ports, see Ports.

• Ca talog service port. This port is used by the Veeam Guest Catalog Service to replicate catalog data from
backup servers to Veeam Backup Enterprise Manager. By default, port 9393 is used.

• Veeam Backup service port. This port is used by Veeam Backup Enterprise Manager to collect data from
backup servers. In addition to it, the Veeam Backup & Replication console uses this service port to connect
to the backup server. By default, port 9392 is used.

• Secure connections port. This port is used by the mount server to communicate with the backup server. By
default, port 9401 is used.

• RE ST API service port. This port is used to communicate with the Veeam Backup & Replication REST API.
By default, port 9419 is used.

316 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Begin Installation
The Ready to Install step of the wizard is available if you have selected to configure installation settings
manually.

At this step of the wizard, you can review the Veeam Backup & Replication installation settings and start the
installation process:

1. If you want Veeam Backup & Replication to check for product updates weekly, select the Check for
p roduct updates automatically check box. When a new product build is published on the Veeam update
server, a notification will be displayed in the Windows Action Center.

2. Click Install to begin the installation.

3. Wait for the installation process to complete and click Finish to exit the setup wizard.

317 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Veeam Backup & Replication Console
By default, the Veeam Backup & Replication console is installed on the backup server automatically when you
install Veeam Backup & Replication. You do not need to install the console manually.

However, in addition to the default console, you can install the Veeam Backup & Replication console on a
dedicated machine to access the backup server remotely. You can install as many remote consoles as you need.
For more information, see Backup & Replication Console.

Before you install the Veeam Backup & Replication console, check prerequisites. Then use the
Veeam Backup & Replication Console Setup wizard to install the console.

Before You Begin


Before you install the Veeam Backup & Replication console, check the following prerequisites:

• The Veeam Backup & Replication console must be of the same version as Veeam Backup & Replication
installed on the backup server.

• A machine on which you plan to install the Veeam Backup & Replication console must meet the system
requirements. For more information, see System Requirements.

• A user account that you plan to use for installation must have sufficient permissions. For more
information, see Permissions.

• Backup infrastructure components communicate with each other over specific ports. These ports must be
open. For more information, see Ports.

318 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Setup Wizard
To start the setup wizard:

1. Download the latest version of the Veeam Backup & Replication installation image from the Download
Veeam Products page.

2. Mount the installation image to the machine on which you plan to install the Veeam Backup & Replication
console or burn the image file to a flash drive or other removable storage device. If you plan to install the
Veeam Backup & Replication console on a VM, use built-in tools of the virtualization management
software to mount the installation image to the VM.

To extract the content of the ISO, you can also use the latest versions of utilities that can properly extract
data from ISOs of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun will open a splash screen. If Autorun is not available
or disabled, run the Setup.exe file from the image or disk.

4. In the splash screen, click Install.

IMP ORTANT

It is strongly recommended that you install the Veeam Backup & Replication console using Autorun or the
Setup.exe file. If you run other installation files from the ISO folders, you may miss some components that
need to be installed, and the Veeam Backup & Replication console may not work as expected.

319 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At the Select Veeam Backup & Replication Component step of the wizard, select Install
Veeam Backup & Replication Console.

To open Veeam Help Center from the setup wizard, click View Documentation.

320 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Read and Accept License Agreement
At the License Agreement step of the wizard, read Veeam License Agreement and licensing policy as well as
license agreements of 3rd party components that Veeam incorporates and license agreement s of required
software. To accept the license agreements and continue installing the Veeam Backup & Replication console,
click I Accept.

321 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Install Missing Software
At the Sy stem Configuration Check step of the wizard, the setup wizard checks if the required software is
installed on the machine. If some of the required components are missing, the setup will try to install them
automatically. After the components are successfully installed, reboot is required. To reboot the machine, click
Reb oot.

If the setup wizard cannot install some of the required software components automatically, install them
manually and click Retry.

NOTE

If all required software is already installed on the machine, the Sy stem Configuration Check step will be
skipped. For more information on the necessary software, see System Requirements.

322 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Review Default Installation Settings
At the Rea dy to Install step of the wizard, you can select to install the Veeam Backup & Replication console with
default installation settings or specify custom installation settings.

• To use the default installation settings, click Install.

• To use custom installation settings, click Customize Settings. The setup wizard will include additional
steps that will let you configure installation settings.

The table below lists the default installation settings.

Setting Default Value Description

Installation folder C:\Program Folder where the Veeam Backup & Replication
Files\Veeam\Backup and console will be installed.
Replication

323 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Installation Path
The Da ta Locations step is available if you have selected to configure installation settings manually.

At this step of the wizard, you can choose the installation folder for the Veeam Backup & Replication console.

1. On the right of the Installation path field, click Browse.

2. In the Select Folder window, select the installation folder for the product. The default folder is
C:\Program Files\Veeam\Backup and Replication\.

324 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Begin Installation
The Ready to Install step of the wizard is available if you have selected to configure installation settings
manually.

At this step of the wizard, you can review the Veeam Backup & Replication console installation settings and start
the installation process

1. Click Install to begin the installation.

2. Wait for the installation process to complete and click Finish to exit the setup wizard.

325 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Repairing Veeam Backup & Replication
If some of the Veeam Backup & Replication components are damaged, you can try repairing the
Veeam Backup & Replication installation. To repair Veeam Backup & Replication, use the
Veeam Backup & Replication setup wizard. The wizard will re-install the Veeam Backup & Replication
components over the existing installation. It will replace broken or missing files, restore shortcuts and registry
values.

IMP ORTANT

If you have any problems repairing Veeam Backup & Replication, contact Veeam Customer Support.

326 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Setup Wizard
To start the setup wizard, take the following steps:

1. Download a Veeam Backup & Replication installation image from the Veeam Product Downloads page.

The build number of the image file must be the same as your current installation build. You can check the
Veeam Backup & Replication build number in the Programs and Features tool.

2. Mount the installation image to the machine where Veeam Backup & Replication is installed, or burn the
image file to a flash drive or other removable storage device. If you plan to repair
Veeam Backup & Replication on a VM, use built-in tools of the virtualization management software to
mount the image to the VM.

To extract the content of the ISO file, you can also use the latest versions of utilities that can properly
extract data from ISO files of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun opens a splash screen. If Autorun is not available or
disabled, run the Setup.exe file from the image or disk.

4. Click Install.

327 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At this step of the wizard, select Install Veeam Backup & Replication.

To open Veeam Help Center from the wizard, click View Documentation.

328 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Repair Option
At the Ma intenance Mode step of the setup wizard, select the Repair option and click Nex t.

329 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Service Account
At the Service Account step of the wizard, select an account that will be used during the
Veeam Backup & Replication repair.

• LOCAL SYSTEM account (recommended, used by default)

• Another user account


The user name of the custom account must be specified in the DOMAIN\USERNAME format.

330 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Begin Installation
At the Rea dy to Install step of the wizard, click Install to start the repair process.

The setup wizard will re-install the Veeam Backup & Replication components. Wait for the installation process
to complete and click Finish to exit the setup wizard.

331 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Repairing Veeam Backup & Replication Console
If some of the Veeam Backup & Replication console components are damaged, you can try repairing the
Veeam Backup & Replication console installation. To repair the Veeam Backup & Replication console, use the
Veeam Backup & Replication setup wizard. The wizard will re-install the Veeam Backup & Replication console
components over the existing installation. It will replace broken or missing files, restore shortcuts and registry
values.

IMP ORTANT

If you have any problems repairing the Veeam Backup & Replication console, contact Veeam Customer
Support.

To repair the Veeam Backup & Replication console installation, take the following steps:

1. Start the setup wizard

2. Select the Veeam Backup & Replication console as a component to repair

3. Select the Repair option

4. Begin installation

332 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Setup Wizard
To start the setup wizard, take the following steps:

1. Download a Veeam Backup & Replication installation image from the Veeam Product Downloads page.

The build number of the image file must be the same as your current installation build. You can check the
Veeam Backup & Replication console build number in the Programs and Features tool.

2. Mount the installation image to the machine where the Veeam Backup & Replication console is installed,
or burn the image file to a flash drive or other removable storage device. If you plan to repair the
Veeam Backup & Replication console on a VM, use built-in tools of the virtualization management
software to mount the image to the VM.

To extract the content of the ISO file, you can also use the latest versions of utilities that can properly
extract data from ISO files of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun opens a splash screen. If Autorun is not ava ilable or
disabled, run the Setup.exe file from the image or disk.

4. Click Install.

333 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At this step of the wizard, select Install Veeam Backup & Replication Console.

To open Veeam Help Center from the wizard, click View Documentation.

334 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Repair Option
At the Ma intenance Mode step of the setup wizard, select the Repair option and click Nex t.

335 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Begin Installation
At the Rea dy to Install step of the wizard, click Install to start the repair process.

The setup wizard will re-install the Veeam Backup & Replication console components. Wait for the installation
process to complete and click Finish to exit the setup wizard.

336 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Uninstalling Veeam Backup & Replication
To uninstall Veeam Backup & Replication:

1. From the Sta rt menu, select Control Panel > Programs a nd Features.

2. In the programs list, right-click Veeam Backup & Replication and select Uninstall. If you have Veeam
Backup Enterprise Manager installed on this machine, Veeam Backup & Replication will uninstall both
components. Wait for the process to complete.

3. If the program list contains additional Veeam Backup & Replication components, right-click the remaining
components and select Uninstall.

The Veeam Backup & Replication configuration database is not removed during the uninstall process. All
configuration data stored in the database remains as well.

337 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrade and Update
This section describes how to update and upgrade Veeam Backup & Replication, Veeam Backup & Replication
Console, and other backup infrastructure components.

338 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading to Veeam Backup & Replication 12.1
To perform upgrade of Veeam Backup & Replication to version 12.1, you must be running version 10a (build
10.0.1.4854) or later on the supported operating system (refer to the System Requirements section of this
document). For information on upgrade from earlier versions, see this Veeam KB article.

Before you upgrade Veeam Backup & Replication, check prerequisites. Then use the Veeam Backup & Replication
upgrade wizard to install the product.

After you upgrade Veeam Backup & Replication, perform the finalizing steps.

Unattended Upgrade
If you still use the Veeam Backup & Replication upgrade in the unattended mode, as described in Installing
Veeam Backup & Replication in Unattended Mode, consider the following:

1. When upgrading Veeam Backup & Replication in the unattended mode, most of the system checks that are
performed during the manual upgrade are omitted. Therefore, before performing the upgrade in the
unattended mode, make sure that you have checked all the p rerequisites specified in the Upgrade
Checklist. Also ensure that all the components of your infrastructure correspond to the System
Requirements.

2. Install a later version of the product in the unattended mode. You must connect to the configuration
database that was used by the previous product version.

For information on how to install Veeam Backup & Replication in the unattended mode, see Installing
Veeam Backup & Replication in Unattended Mode.

Upgrade Checklist
Use the following checklist to ensure your infrastructure is ready for the Veeam Backup & Replication upgrade.
The built-in configuration check mechanism of the Veeam Backup & Replication Upgrade wizard performs some
of the checks. Still, you can control them manually before starting the upgrade procedure.

Licensing
1. Veeam Backup & Replication 12.1 uses the same license file format introduced with version 10, so you can
use your existing version 10 or 11 license file to install version 12.1. Your support contract must be active as
of the date when the product version you are installing was built.

2. Your support contract must be active as of the date when the product build you are installing was built.
This is determined by the support expiration date in the installed license. If required, you can install a new
license during the upgrade procedure.

3. Are you using Veeam Backup Starter? This edition has been discontinued, so Vee am Backup & Replication
12.1 will not accept such a license file. Download a replacement license file from the Customer Portal
before upgrading.

339 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
System Requirements
1. Check if the backup server to be upgraded is installed on the supported operating system version
according to the System Requirements section. If it is not, create a configuration backup, install
Veeam Backup & Replication 12.1 on the supported OS first, then restore the configuration backup created
earlier. For information on how to perform the migration, see the Migrating Veeam Backup & Replication
to Another Backup Server section.

2. Make sure that other servers that you plan to use as backup infrastructure components meet the system
requirements listed in the System Requirements section of this document. In particular, ensure all backup
infrastructure servers are based on 64-bit operating systems.

3. Make sure that the environment you are going to protect with Veeam Backup & Replication meets the
requirements listed in the Platform Support section of this document.

4. Are you using a hardened repository? If yes, make sure that any Linux server associated with the hardened
repository is configured to use a non-root account. For more information, see this Veeam KB article.

5. Do you have any jobs using the Transform previous backup chains into rollbacks option? This option has
been removed from the product and such jobs are no longer supported. For more information, see this
Veeam KB article.

6. Are you using File to Tape jobs? They have been reengineered for scalability and are no longer free with
Veeam Backup & Replication 12.1. You will have a grace period of 3 months following the upgrade to
Veeam Backup & Replication 12.1 during which your existing jobs will not consume a license. For more
information, see the Instance Consumption for NAS Backup and File to Tape Jobs section.

7. Are you using installations of Veeam Backup & Replication and Veeam Backup for Microsoft 365 on the
same machine? First upgrade Veeam Backup for Microsoft 365, second upgrade
Veeam Backup & Replication.

8. Are you using integration with Veeam Backup for Microsoft Azure? If yes, after upgrade to
Veeam Backup & Replication 12.1, select the existing Microsoft Azure Compute account in the Manage
Cloud Credentials, click Edit, and go through the Microsoft Azure Compute Account to update account
permissions. Otherwise, you can face problems when adding an external repository with backups created
by Veeam Backup for Microsoft Azure 6.0.

9. Are you using Server 2019 based ReFS backup repositories? If yes, avoid upgrading them to Server 2022
and mounting ReFS volumes from Server 2019 to new Server 2022 installations until you read this thread
on Veeam R&D forums. Microsoft has addressed the known regression in the ReFS format upgrade code,
and the fix is now publicly available.

10. Are you using Scale-Out Backup Repositories with immutable performance tier extents? Make sure that all
extents have the same immutability settings.

Integration with Veeam Management and Monitoring


Products
1. Are you using Veea m ONE to monitor your backup infrastructure? If yes, upgrade it first. Veeam ONE
supports monitoring of backup servers version 10a or later.

2. Are you using Veea m Backup Enterprise Manager? If yes, consider the following:

o Imp ortant! Starting with Veeam Backup Enterprise Manager 12, a new port ( port 9405) is used for
certificate communication between Enterprise Manager and Veeam Backup & Replication. Ensure that
your firewalls are configured to take into account this new port to avoid communication issues
between Enterprise Manager and Veeam Backup & Replication.

340 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Start the upgrade procedure with this component. Veeam Backup & Replication should be upgraded
after that. If you have a backup server installed on the same machine, upgrade it immediately after
completing upgrade of the Veeam Backup Enterprise Manager server. Otherwise, the Veeam
Configuration Database Connection Utility (DBConfig) utility will not work properly for
Veeam Backup & Replication.

o From Veeam Backup Enterprise Manager, you cannot edit jobs that are managed by backup servers of
earlier versions as well as Veeam Agent backup jobs, file share backup job s, and backup copy jobs. To
edit settings of such jobs, use the Veeam Backup & Replication console.

3. Are you using Veea m Backup Enterprise Manager server added to Veeam ONE? If yes, first upgrade Veeam
ONE, second upgrade Veeam Backup Enterprise Manager, and third upgrade Veeam Backup & Replication.

4. Are you using Cloud Connect? If yes, check with your Cloud Connect service provider if they have already
upgraded their system to at least the version you are upgrading to.

5. [For upgrade from Veeam Backup & Replication earlier than version 11a build 11.01.1261] Are you using
Veeam Backup & Replication within the infrastructure of Nuta nix Mine version 2.0.1 or earlier? If yes,
upgrade Nutanix Mine to version 3.0, then upgrade Veeam Backup & Replication to version 12 or 12.1.

6. Are you using Veea m Recovery Orchestrator? If yes, note that Veeam Recovery Orchestrator 5.0 is
compatible with Veeam Backup & Replication 11 and 11a, Veeam Recovery Orchestrator 6.0 — with
Veeam Backup & Replication 11a and 12, Veeam Recovery Orchestrator 7.0 — with
Veeam Backup & Replication 12 and 12.1. If necessary, upgrade Veeam Recovery Orchestrator before
upgrading to Veeam Backup & Replication 12.1.

Integration with Veeam Backup for Public Clouds


Are you using Veeam Backup & Replication integrated with Veeam Backup for Public Cloud solutions? The plug -
ins of these products must be aligned with the version of the products. Do not upgrade to Veeam Backup &
Replication 12.1 until you install the matching plug-in versions for Veeam Backup for AWS (version 7), (version
6), and Google Cloud (version 5).

Integration with Veeam Backup for Hypervisors


Are you using Veeam Backup & Replication integrated with Veeam Backup for Hypervisors?

• Veeam Backup for Nutanix AHV: plugin for this product is included into the Veeam Backup & Replication
12.1 package. During the upgrade to version 12.1, the plugin for this product will be automatically
upgraded to the required version.

• Veeam Backup for Red Hat Virtualization: plugin for this product is included into the
Veeam Backup & Replication 12.1 package. During the upgrade to version 12.1, the plugin for this product
will be automatically upgraded to the required version.

341 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup Agents and Enterprise Plug-
Ins
1. Are you using Veea m Agents managed through Veeam Backup & Replication?

o If you use Veeam Agent for Microsoft W indows or Veea m Agent for Linux 4.0, they will stop working
after upgrading to Veeam Backup & Replication 12.1. In this case, we recommend immediately
upgrading Veeam Agent for Microsoft Windows or Veeam Agent for Linux to 6.1. If you use Veeam
Agent for Microsoft Windows or Veeam Agent for Linux 5.0 or later, they will continue working after
upgrading to Veeam Backup & Replication 12.1, but new features implemented in
Veeam Backup & Replication 12.1 will not be supported. In this case, you can upgrade Veeam Agent
for Microsoft Windows or Veeam Agent for Linux to 6.1 later if the support of new features is not
critical for you.

o If you use Veeam Agent for Mac 1.0, it will stop working after upgrading to
Veeam Backup & Replication 12.1. In this case, we recommend immediately upgrading Veeam Agent
for Mac to 2.1. If you use Veeam Agent for Mac 1.0.1, it will continue working after upgrading to
Veeam Backup & Replication 12.1, but new features implemented in Veeam Backup & Replication 12.1
will not be supported. In this case, you can upgrade Veeam Agent for Mac to 2.1 later if the support of
new features is not critical for you.

o If you use Veeam Agent for IBM AIX or Veea m Agent for Oracle Solaris 3.0 or later, they will continue
working after upgrading to Veeam Backup & Replication 12.1, but new features implemented in
Veeam Backup & Replication 12.1 will not be supported. In this case, you can upgrade Veeam Agent
for IBM AIX or Veeam Agent for Oracle Solaris to 4.1 later if the support of new features is not critical
for you.

2. Are you using Veea m Plug-In for Oracle RMAN, Veeam Plug-In for SAP HANA, Veeam Plug-In for SAP on
Ora cle or Veeam Plug-In for Microsoft SQL Server? If yes, you upgrade Veeam Backup & Replication first,
then you can upgrade Veeam Plug-ins.

Storage System Snapshot Integration


1. Make sure your storage systems work on a supported operating system:

o Hua wei: storage arrays of this vendor are not supported for Veeam storage snapshot integration.
Remove the storage arrays from the backup server configuration and use other backup transport
modes instead.

o Cisco HyperFlex: the minimum supported operating system version is v4.0(2x). Upgrade to it or
remove the storage arrays from the backup server configuration.

o HP E 3PAR W SAPI: the minimum supported WSAPI version is 1.5. Upgrade to it or remove the storage
arrays from the backup server configuration.

o HP E Nimble: the minimum supported operating system version is 5.0. Upgrade to it or remove the
storage arrays from the backup server configuration.

o Dell Data Domain: the supported operating system version is 7.3 to 7.12 (6.2 to 7.10 for
Veeam Backup & Replication 12). Upgrade to it or the backup jobs pointed to this repository will fail to
start.

o HP E StoreOnce: the minimum supported operating system version is 3.18.18 for Gen3 and 4.2.3 for
Gen4. Upgrade to it or the backup jobs pointed to this repository will fail to start.

2. Select the secondary destination for IBM HyperSwap configurations explicitly in the backup job.

342 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Other Changes
1. Veeam Backup & Replication 12.1 supports protecting NAS backups with backup to tape jobs. If you have
entire repositories added as sources for backup to tape job s, make sure these repositories contain only
backups that you want to protect with backup to tape jobs.

2. If you use persistent agents for guest OS processing in a Kerberos-only environment, perform the steps
listed in this Veeam KB article.

3. If you use Kerberos authentication for Guest OS processing with persistent guest agent components,
create several Service Principal Names in Active Directory before upgrading to
Veeam Backup & Replication 12.1. For more information, see this Veeam KB article.

4. If you have HPE StoreOnce backup copy jobs where the source backup repository has immutability enabled
and the target backup repository has immutability disabled, backups copied by backup copy jobs will not
be immutable. For immutability to work, make sure both HPE StoreOnce repositories have immutability
enabled.

5. Note that background retention is now applied to daily backups belonging to disabled backup jobs, as well
as to orphaned backups. Background retention is still applied to GFS backups belonging to disabled
backup jobs, as well as to orphaned backups.

6. Make sure there are no replica VMs or replication jobs for VMs running on Windows Server Hyper-V 2008
R2.

Upgrade Process
1. Make sure the latest run for all existing jobs has completed successfully. Rerun the failed jobs.

2. Ensure there are no running jobs, restore sessions, Instant Recovery sessions, and SureBackup jobs. We
recommend that you do not stop running jobs and let them complete successfully.

3. Disable any periodic and backup copy jobs temporarily to prevent them from starting during the upgrade.

4. Disable CDP policies. Otherwise the CDP filter will not be upgraded.

5. Ensure there are no active tasks from standalone (unmounted) agents.

6. Ensure there are no active Veeam Recovery Orchestrator tasks.

7. Perform the configuration backup, as described in the Running Configuration Backups Manually section.

Ensure you have configuration backup encryption enabled, otherwise stored credentials will not be
included in it. For more information, see the Creating Encrypted Configuration Backups section.

Additional Considerations for Upgrade from


Veeam Backup & Replication 10
Do you have backup copy jobs with synthetic GFS full backups? Before the upgrade, make sure that all GFS
candidates (incremental restore points created on days when GFS was scheduled and that are expected to be
transformed into full GFS restore points) are already transformed into GFS restore points. To force the backup
copy job to transform all GFS candidates, you can temporarily decrease the short-term retention to a value less
than the number of restore points between the latest restore point and the most recent GFS candidate and then
wait till all the candidates are transformed.

343 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before Veeam Backup & Replication version 11, Veeam Backup & Replication created GFS candidates on days
when GFS was scheduled and only then transformed them into full GFS restore points according to the short -
term retention. For more information on how restore points were transformed, see the Synthetic Weekly Full
Backups section. Starting from Veeam Backup & Replication version 11, Veeam Backup & Replication creates GFS
restore points according to a new schedule and creates them right on the scheduled da ys. For more information,
see the Changes in GFS Retention section. After the upgrade, Veeam Backup & Replication no longer transforms
previous GFS candidates into full GFS restore points. This means, that all GFS candidates l ose their GFS status,
they become regular incremental restore points and are deleted according to the short-term retention policy.

Additional Considerations for Upgrade from


Veeam Backup & Replication 12
Do you have hardened repositories in the recommended configuration with the SSH Server disabled for added
security? Due to an updated Deployer component, upgrading to 12.1 requires temporarily enabling SSH and
providing single-use credentials with root privileges to install the updated Deployer. If you want to avoid
visiting your data center to enable SSH, consider waiting for the first cumulative patch where we will try to
remove the SSH requirement.

344 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Upgrade Wizard
To start the upgrade wizard, take the following steps:

1. Download the latest version of the Veeam Backup & Replication installation image from the Veeam
Product Downloads page.

2. Mount the installation image to the machine where Veeam Backup & Replication is installed, or burn the
image file to a flash drive or other removable storage device. If you plan to upgrade
Veeam Backup & Replication on a VM, use built-in tools of the virtualization management software to
mount the image to the VM.

To extract the content of the ISO, you can also use the latest versions of utilities that can properly extract
data from ISO files of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun opens a splash screen. If Autorun is not available or
disabled, run the Setup.exe file from the image or disk.

4. Click Up grade.

345 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At this step of the wizard, select Up g rade Veeam Backup & Replication.

To open Veeam Help Center from the upgrade wizard, click View Documentation.

346 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Read and Accept License Agreement
At the License Agreement step of the wizard, read Veeam License Agreement and licensing policy as well as
license agreements of 3rd party components that Veeam incorporates and license agreements of required
software. To accept the license agreements and continue installing Veeam Backup & Replication, click I Accept.

347 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
At the Up g rade step of the wizard, you can review the components that will be upgraded.

To also upgrade the the remote components after the Veeam Backup & Replication server is upgraded, select
the Up d ate remote components automatically check box.

348 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Provide License File
At the License step of the wizard, specify what license you want to install for Veeam Backup & Replication. You
can leave the license file used in the previous version of Veeam Backup & Replication or install a new one.

To install a license, you have 2 options to choose from:

• Browse your local server or network locations for a license file:

a. Click Browse license file.

b. Select a valid license file for Veeam Backup & Replication.

• Select a license from your account at the Veeam web-site:

a. Click Sig n in with Veeam.

b. Enter your credentials for accessing the Veeam web-site and click Sig n in.

c. Select one of the available licenses and click Install selected license.

To install new licenses automatically when you renew or expand your contract, select the Up date license
a utomatically check box. If you enable the automatic license update, and therefore enable usage reporting, you
will double the number of workloads by which you can exceed your installed license. For more information, see
Exceeding License Limit.

349 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Install Missing Software
At the Sy stem Configuration Check step of the wizard, the setup wizard checks if the required software is
installed on the machine. If some of the required components are missing, the setup will try to install them
automatically. After the components are successfully installed, reboot is required. To reboot the machine, click
Reb oot.

If the setup wizard cannot install some of the required software components automatically, install them
manually and click Retry.

NOTE

If all required software is already installed on the machine, the Sy stem Configuration Check step will be
skipped. For more information on the necessary software, see System Requirements.

350 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Service Account Settings
The Service Account step of the wizard is available if you have selected to configure installation settings
manually.

You can select an account under which you want to run the Veeam Backup Service:

• LOCAL SYSTEM account (recommended, used by default)

• Custom user account

The user name of the custom account must be specified in the DOMAIN\USERNAME format and have the
following rights and permissions:

• The account must be a member of the Administrators group on the machine where
Veeam Backup & Replication is installed.

• The account must have db_owner rights for the configuration database.

Veeam Backup & Replication automatically grants the Log on as service right to the specified user account.

NOTE

You cannot use a gMSA for running the Veeam Backup Service.

351 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Database Engine and Instance
At the Da tabase step of the wizard, select the Microsoft SQL server instance and database that were used by the
previous version of Veeam Backup & Replication, and specify the authentication mode.

NOTE

After you upgrade Veeam Backup & Replication, you can migrate its configuration database to PostgreSQL.
For more information, see Migrating Configuration Database to PostgreSQL.

1. Specify instance settings:

o In the SQL Server instance field, enter the instance name in the HOSTNAME\INSTANCE format or
select an instance from the drop-down list. You can also click Browse to choose a Microsoft SQL
Server on a remote machine.

o In the Da tabase name field, specify a name for the Veeam Backup & Replication configuration
database.

2. Select an authentication mode to connect to the database server instance: Microsoft Windows
authentication or native database server authentication. If you select the native authentication, enter
credentials of the database account.

3. If the configuration database is in use by another Veeam Backup & Replication server, the wizard will
notify about it. To continue the installation, click Y es.

4. If the wizard detects a configuration database with the specified name (for example, it was created by a
previous installation of Veeam Backup & Replication), the wizard will notify about it. To connect to the
detected database, click Y es.

Veeam Backup & Replication will automatically upgrade the database to the latest version.

352 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Perform Configuration Check
At the Configuration Check step of the wizard, the setup checks the Veeam Backup & Replication configuration.

If the check returns errors, solve their causes before continuing the upgrade. After you solve them, click Retry
to check if there are any issues left.

If the check returns warning or information messages, you can continue the upgrade and address them later.
However, we recommend that you closely investigate warning and information messages: if not properly
addressed, their causes may lead to serious problems with further system operation.

To view the details of a certain message, point the cursor to the line with the message. The pop -up box will
display the detailed description.

To copy a list of detected issues with detailed descriptions for further investigation, click Cop y list to clipboard.

353 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Begin Upgrade
At the Rea dy to Upgrade step of the wizard, review the upgrade settings and start the upgrade process.

Wait for the installation process to complete and click Finish to exit the wizard.

After Upgrade
After you upgrade Veeam Backup & Replication to version 12, perform the following steps:

1. If you use remote backup consoles, upgrade them to version 12. If you use remote backup consoles version
11a, you can upgrade them to version 12 automatically when connecting to backup server version 12. If you
use remote backup consoles version 10a or 11, upgrade them manually us ing the product ISO file.

2. Download and install the latest available update from the Veeam Updates page.

3. Open the Veeam Backup & Replication console. If necessary, the automated upgrade wizard will
automatically appear, prompting you to upgrade the product components running on remote servers.
Follow the wizard to complete the upgrade process.

4. If some remote servers are unavailable at the time of upgrade, you can run the upgrade wizard at any time
later from the main product menu, or by closing and re-opening the Veeam Backup & Replication console.
Note that the out-of-date product components cannot be used by jobs until they are updated to the
backup server version.

5. Azure compute accounts based on Microsoft Entra ID (formerly Azure Active Directory) user credentials
(created with the Use existing account option selected) are obsolete. Replace these accounts with new
ones to restore workloads to Microsoft Azure and use Azure archive storage or the Microsoft Azure Plug-In
for Veeam Backup & Replication appliance.

354 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. If you use the Virtual Labs functionality, open settings of each Virtual Lab, and click through the wizard to
redeploy each virtual lab with the new proxy appliance version.

7. If you are using Linux servers for your backup infrastructure components, the process of upgrade to
version 12 will automatically deploy the new persistent data mover only to Linux servers with the VMware
Backup Proxy role. To deploy it on other Linux servers, click through the Linux server properties, or use
Set-VBRLinux PowerShell cmdlet to mass-deploy. Until you do this, those Linux servers will continue
using the legacy run-time data mover to avoid issues with backup repository not meeting the persistent
data mover requirements.

8. Enable any scheduled jobs that you have disabled before the upgrade.

Note that immediately after the upgrade, the backup server performance may decrease. This happens due to the
maintenance job that optimizes the configuration database. The process may take up to an hour depending on
the database size.

IMP ORTANT

You must upgrade Veeam components on all remote servers with which the backup server communicates
during data protection and disaster recovery tasks. If you do not upgrade components on remote servers,
Veeam Backup & Replication jobs will fail. For more information, see Server Components Upgrade.

355 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating Veeam Backup & Replication
Apart from major version releases of Veeam Backup & Replication (for example, 12, 12.1), Veeam Software
provides cumulative patches (for example, Cumulative Patch P20230223 for v12 ). Cumulative patches contain
bug fixes, performance enhancements and introduce new features.

NOTE

During the update procedure, Veeam Backup & Replication may recreate Windows Firewall rules with
default settings. If you have manually modified Windows Firewall rules before installing a new cumulative
patch, reapply those modifications after the update.

Prerequisites
Before you install a cumulative patch for Veeam Backup & Replication 12, check the following prerequisites:

• Make sure you have Veeam Backup & Replication 12 (build 12.0.0.1420) of any earlier patch level
installed.

For information on how to upgrade from product version 10a or later, see Upgrading to Veeam Backup &
Replication 12.

• Stop all restore processes in the Veeam Backup & Replication Console.

• Stop all jobs and disable them in the Veeam Backup & Replication Console.

• Close the Veeam Backup & Replication Console for all users.

Performing Update
To install the latest update for Veeam Backup & Replication 12, perform the following steps:

1. Go to this Veeam KB article.

2. In the Download Information section of the Veeam KB article, click DOW NLOAD PATCH.

3. Extract the executable file from the downloaded archive.

4. Run the executable file to launch the update wizard.

5. In the update wizard, click Nex t.

6. Select the Up d ate remote components automatically and click Install.

For information on how to update Veeam Backup & Replication in the unattended mode, see Installing Updates
in Unattended Mode.

After you install updates on the backup server, the first connection to it from a remote
Veeam Backup & Replication console may require running it once as administrator. Elevated privileges are
required to update the Veeam Backup & Replication console binaries.

356 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication Update
Notifications
Veeam Backup & Replication may automatically notify you about updates that must or can be installed to
enhance your work experience with the product. Update notifications eliminate the risk of using out -of-date
components in the backup infrastructure or missing critical updates that can have a negative impact on data
protection and disaster recovery tasks.

After a new build of Veeam Backup & Replication is published on the Veeam update server, the backup console
will display a notification in the Windows Action Center (or an icon in the system tray for earlier Windows
versions). If the update is not installed, this notification will keep appearing once a week as a reminder.

You can also see available updates in the Ma naged Servers > Missing Updates node in the Ba ckup Infrastructure
view.

The update notifications are enabled by default. You can disable notifications by clearing the Check for product
a nd hypervisor updates periodically check box on the General Options > Notifications tab, as described in
section Specifying Other Notification Settings. However, it is recommended that you leave update notifications
enabled not to miss critical updates.

357 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication notifies about new Veeam Backup & Replication product versions and updates, as
well as about hypervisor updates, fixes and patches that should be installed on Microsoft Hyper -V hosts and
off-host backup proxies for correct work of Veeam Backup & Replication with Microsoft Hyper-V.

How Update Notification Works


To check for updates, Veeam Backup & Replication uses a special XML file on the Veeam Update Notification
Server (dev.veeam.com). The XML file contains information about the most up -to-date product version and
updates.

Veeam Backup & Replication downloads an XML file from the Veeam Update Notification Server once a week. It
also collects information about the installed product and updates installed on Hyper -V hosts. The collected
information is compared with the information in the downloaded file. If new product versions and updates are
available, Veeam Backup & Replication informs you about them.

NOTE

Make sure that the backup server is connected to the internet and update notification is enabled in
Veeam Backup & Replication options. In the opposite case, update notification will not function.

Installing Updates
To install a product update, double-click the Veeam Backup & Replication notification in the Windows Action
Center (or an icon in the system tray for earlier Windows versions). Veeam Backup & Replication will open a KB
webpage with the update description and links to the installation archive of the new product version or new
update.

If a Microsoft Hyper-V host or off-host backup proxy added to the backup infrastructure misses important
hypervisor fixes and patches that can potentially affect work of Veeam Backup & Replication,
Veeam Backup & Replication displays a warning icon over the host or off-host proxy in the inventory pane.

To install updates:

1. In the Ba ckup Infrastructure view, select a host or off-host backup proxy and click Missing Updates on the
ribbon.

2. Use the Missing Updates window to manage updates:

o To install an update, click the update link. Veeam Backup & Replication will open a webpage with the
update description and download link.

o To ignore the update, select it in the list and click Dismiss. Veeam Backup & Replication will remove
the update from the list and will not inform you about it anymore. To ignore all updates, click Dismiss
All.

o To bring the list of updates to its initial state, click Re-Check. Veeam Backup & Replication will display
all updates, including those that have been dismissed.

o To copy update list details, click Cop y to Clipboard.

TIP

Beside hypervisor updates, in the Missing Updates list Veeam Backup & Replication displays information
about new Veeam Backup & Replication versions and patches. Click the link in the list, and
Veeam Backup & Replication will open a webpage with the product update description and links to the
installation archive.

358 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
359 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Veeam Backup & Replication Console
To perform upgrade of Veeam Backup & Replication console to version 12.1, you must be running version 10a
(build 10.0.1.4854) or later on the supported operating system (refer to the System Requirements section of
this document). For information on upgrade from earlier versions, see this Veeam KB article.

Use the Veeam Backup & Replication Console Upgrade wizard to install the product.

360 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Start Upgrade Wizard
To start the upgrade wizard, take the following steps:

1. Download the latest version of the Veeam Backup & Replication installation image from the Veeam
Product Downloads page.

2. Mount the installation image to the machine where the Veeam Backup & Replication console is installed,
or burn the image file to a flash drive or other removable storage device. If you plan to upgrade the
Veeam Backup & Replication console on a VM, use built-in tools of the virtualization management
software to mount the image to the VM.

To extract the content of the ISO, you can also use the latest versions of utilities that can properly extract
data from ISO files of large size and can properly work with long file paths.

3. After you mount the image or insert the disk, Autorun opens a splash screen. If Autorun is not available or
disabled, run the Setup.exe file from the image or disk.

4. Click Up grade.

361 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Component
At this step of the wizard, select Up g rade Veeam Backup & Replication Console.

To open Veeam Help Center from the upgrade wizard, click View Documentation.

362 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Read and Accept License Agreement
At the License Agreement step of the wizard, read Veeam License Agreement and licensing policy as well as
license agreements of 3rd party components that Veeam incorporates and license agreements of required
software. To accept the license agreements and continue installing the Veeam Backup & Replication console,
click I Accept.

363 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
At the Up g rade step of the wizard, you can review the components that will be upgraded.

To also upgrade the the remote components after the Veeam Backup & Replication server is upgraded, select
the Up d ate remote components automatically check box.

364 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Install Missing Software
At the Sy stem Configuration Check step of the wizard, the setup wizard checks if the required software is
installed on the machine. If some of the required components are missing, the setup will try to install them
automatically. After the components are successfully installed, reboot is required. To reboot the machine, click
Reb oot.

If the setup wizard cannot install some of the required software components automatically, install them
manually and click Retry.

NOTE

If all required software is already installed on the machine, the Sy stem Configuration Check step will be
skipped. For more information on the necessary software, see System Requirements.

365 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Begin Upgrade
At the Rea dy to Upgrade step of the wizard, click Up grade to start the upgrade process.

Wait for the upgrade process to complete and click Finish to exit the wizard.

366 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Infrastructure Components
Every time you launch the Veeam Backup & Replication console, Veeam Backup & Replication automatically
checks if Veeam Backup & Replication components installed on managed servers are up to date. If a later version
of components is available, Veeam Backup & Replication displays the Comp onents Update window and prompts
you to upgrade components on managed servers. Components upgrade may be necessary, for example, after
you have upgraded Veeam Backup & Replication.

You can manually check if components upgrade is required. To do this, select Up grade from the main menu. If
components on all managed servers are up to date, the menu item will be disabled.

To upgrade components on managed servers:

1. In the Components Update window, select a server and click Details. Veeam Backup & Replication will
display the current and latest available versions for installed components.

2. In the Components Update window, select check boxes next to servers for which you want to upgrade
components and click Ap p ly.

You can update components on every managed server separately. If components insta lled on the server require
upgrade, Veeam Backup & Replication displays a warning icon next to the server.

To update components for a managed server:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Ma naged servers.

367 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the server and click Up g rade on the ribbon. Alternatively, right-click the
selected server and select Up g rade.

368 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Silent Deployment
You can install, upgrade and uninstall Veeam Backup & Replication and the Veeam Backup & Replication console
in the unattended mode with a special XML answer file by using the command line interface. Answer files
contain all the necessary installation, upgrade or uninstallation settings in the proper order and their thorough
description.

You can find the template answer files on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBR and \Setup\Silent\AnswerFiles\VBRConsole folder. This folder
contains the following templates of answer files used for installing, uninstalling, and upgrading
Veeam Backup & Replication:

• VbrAnswerFile_install.xml — for installing Veeam Backup & Replication;

• VbrAnswerFile_uninstall.xml — for uninstalling Veeam Backup & Replication;

• VbrAnswerFile_upgrade.xml — for upgrading Veeam Backup & Replication;

• VbrConsoleAnswerFile_install.xml — for installing the Veeam Backup & Replication console;

• VbrConsoleAnswerFile_uninstall.xml — for uninstalling the Veeam Backup & Replication console;

• VbrConsoleAnswerFile_upgrade.xml — for upgrading the Veeam Backup & Replication console.

369 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Veeam Backup & Replication in Silent
Mode
You can install Veeam Backup & Replication in the unattended mode with a special XML answer file by using the
command line interface. The answer file contains all the necessary installation settings in the proper order and
their thorough description.

Before You Begin


Before starting the installation of Veeam Backup & Replication in the unattended mode with the answer file,
consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended installation is logged on the machine using the
network logon method, the unattended installation will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
installation is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out unused [Optional] parameters. Otherwise,
the installation session will fail.

Installing Veeam Backup & Replication


To install Veeam Backup & Replication in the silent mode with the answer file, take the following steps:

1. Copy the VbrAnswerFile_install.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBR folder. This folder contains the following templates of answer files
used for installing, uninstalling, and upgrading Veeam Backup & Replication:

o VbrAnswerFile_install.xml — for installing Veeam Backup & Replication;

o VbrAnswerFile_uninstall.xml — for uninstalling Veeam Backup & Replication;

o VbrAnswerFile_upgrade.xml — for upgrading Veeam Backup & Replication.

2. Configure installation parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (Vbr) and mode (install) specified in line 2:

<unattendedInstallationConfiguration bundle="Vbr" mode="install" version="


1.0">

3. After you make all the necessary changes in your answer file, start the installation by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your installation command:

370 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileVBRIns
tall.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileVBRInstall.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-installation


validations that do not work under the network logon, which will block the silent installation from
running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains the following parameters:

P a rameter Require Default Description


d?

ACCEPT_EULA Yes Specify 1 to accept the


Veeam license agreement.

ACCEPT_LICENSING_POLICY Yes Specify 1 to accept the


Veeam licensing policy.

ACCEPT_THIRDPARTY_LICEN Yes Specify 1 to accept the


SE S license agreement for 3rd
party components that
Veeam incorporates.

ACCEPT_REQUIRED_SOFTWA Yes Specify 1 to accept all


RE required software license
agreements.

VBR_LICENSE_FILE No Path to the license file on the


machine where you want to
install
Veeam Backup & Replication.
If you do not specify this
parameter (or leave it empty
value),
Veeam Backup & Replication
will be installed using the
current license file. To install
the Community Edition, set
the parameter to to 0.

371 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Require Default Description
d?

VBR_LICENSE_AUTOUPDATE No 1 Specify 1 to enable automatic


license update and usage
reporting. Specify 0 if you
want to update the license
manually. For Community
Edition, NFR and Evaluation
licenses, specify 1. For
licenses without ID
information, specify 0.

VBR_SERVICE_USER No User account under which the


Veeam Backup Service will
run. If you do not specify this
parameter, the service will
run under the LocalSystem
account.

VBR_SERVICE_PASSWORD No Password for the account


under which the Veeam
Backup Service will run.

VBR_SQLSERVER_INSTALL Yes 1 Specify 0 to use an existing


SQL server instance or specify
1 to create a new SQL server
instance.

VBR_SQLSERVER_ENGINE No 1 Specify 0 to use PostgreSQL


engine or specify 1 to use
Microsoft SQL engine. Note
that if you want to create a
new SQL server instance, you
can only choose the
PostgreSQL engine.

VBR_SQLSERVER_SERVER No localhost:5432 SQL server and instance (for


Microsoft SQL) or SQL server
an port (for PostgreSQL)
where the configuration
database will be deployed.
Note that if you want to
create a new SQL instance,
you can only connect to a
local host.

372 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Require Default Description
d?

VBR_SQLSERVER_DATABASE No VeeamBackup Configuration database


name. If you do not specify
this parameter, the default
VeeamBackup name is used.

VBR_SQLSERVER_AUTHENTIC No 0 Authentication mode to


ATION connect to the SQL Server
where the
Veeam Backup & Replication
configuration database is
deployed. Specify 1 to use
the SQL Server
authentication mode or
specify 0 to use the Microsoft
Windows authentication
mode.

VBR_SQLSERVER_USERNAME No LoginID to connect to the


SQL Server in the SQL Server
authentication mode.

VBR_SQLSERVER_PASSWORD No Password to connect to the


SQL Server in the SQL Server
authentication mode.

VBRC_SERVICE_PORT No 9393 TCP port to be used by the


Veeam Guest Catalog Service.
If you do not specify this
parameter, the default 9393
port is used.

VBR_SERVICE_PORT No 9392 TCP port to be used by the


Veeam Backup Service. If you
do not specify this
parameter, the default 9392
port is used. If the specified
port number is already
occupied, the setup will
assign the next available port
number to the component.

VBR_SECURE_CONNECTIONS_ No 9401 TCP port to be used for


P ORT communication between the
mount server and the backup
server. If you do not specify
this parameter, the default
9401 port is used.

373 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Require Default Description
d?

VBR_RESTSERVICE_PORT No 9419 TCP port to be used for


communication with REST
API service. If you do not
specify this parameter, the
default 9419 port is used.

C:\Program Files\Veeam\Backup
INSTALLDIR No and Replication Path to the directory where
Veeam Backup & Replication
will be installed. If you do not
specify this parameter, the
default
%ProgramFiles%\Veeam\B
ackup and Replication
installation path is used.

VM_CATALOGPATH No C:\VBRCatalog Path to the catalog folder


where index files will be
stored. If you do not specify
this parameter, a path is
selected based on the free
space across all available
disks.

C:\ProgramData\Veeam\Backup\I
VBR_IRCACHE No RCache Path to the folder where the
instant recovery cache will be
stored. If you do not specify
this parameter, a path is
selected based on the free
space across all available
disks.

VBR_CHECK_UPDATES No 1 Specify 1 to automatically


check for new product
versions and updates. Specify
0 if you do not want
Veeam Backup & Replication
to check for updates
automatically.

AHV_INSTALL No 0 Specify 1 if you want to


install Nutanix AHV Plug-in
for Veeam Backup &
Replication. Specify 0 if you
do not want to install the
plugin.

374 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Require Default Description
d?

RHV_INSTALL No 0 Specify 1 if you want to


install Red Hat Virtualization
Plug-in for Veeam Backup &
Replication. Specify 0 if you
do not want to install the
plugin.

AW S_INSTALL No 1 Specify 1 if you want to


install AWS Plug-in for
Veeam Backup & Replication.
Specify 0 if you do not want
to install the plugin.

AZURE_INSTALL No 1 Specify 1 if you want to


install Microsoft Azure Plug-
in for Veeam Backup &
Replication. Specify 0 if you
do not want to install the
plugin.

GCP _INSTALL No 1 Specify 1 if you want to


install Google Cloud Plug-in
for Veeam Backup &
Replication. Specify 0 if you
do not want to install the
plugin.

KASTEN_INSTALL No 1 Specify 1 if you want to


install Kasten K10 Plug-in for
Veeam Backup & Replication.
Specify 0 if you do not want
to install the plugin.

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to


reboot the machine where
you install
Veeam Backup & Replication
after the installation finishes.
Specify 0 if you do not want
to reboot the machine.

Note that you must specify "1" in ACCEPT_EULA, ACCEPT_LICENSING_POLICY, ACCEPT_THIRDPARTY_LICENSES


and ACCEPT_REQUIRED_SOFTWARE parameters to proceed with the installation.

375 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installation Result Codes
The installation result is written into the installation log file located at your s elected log folder. It may show one
of the following result codes:

Result Result
Cod e

0 success

1603 install failure

3010 reboot required

3011 logoff required

Installation Error Codes


The installation error codes accompanied by their detailed description are displayed in the command line dialog.
They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the log folder
(by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving installation
results from the scripts or utilities that are used to run the installation. The error message may show one of the
following error codes:

E rror Description
Cod e

0 Installation has been completed successfully.

1 Product is already installed.

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

12 Reboot is required to finalize prerequisites installation.

13 Reboot is required to finalize the product installation.

14 Logoff is required to finalize the product installation.

101 Failed to start the installer.

376 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E rror Description
Cod e

102 Invalid answer file provided.

103 Invalid launch conditions.

104 Failed to initialize setup properties.

105 Failed to validate setup properties.

106 System configuration check detected some issues.

107 Failed to install prerequisites.

108 Failed to install a database server.

109 Failed to install the product.

110 Failed to update the product.

111 Failed to change a service status.

112 Failed to uninstall the product.

113 Unexpected error occurred.

377 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Veeam Backup & Replication Console
in Silent Mode
You can install the Veeam Backup & Replication console in the unattended mode with a special XML answer file
by using the command line interface. The answer file contains all the necessary installation settings in the
proper order and their thorough description.

Before You Begin


Before starting the installation of the Veeam Backup & Replication console in the unattended mode with the
answer file, consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended installation is logged on the machine using the
network logon method, the unattended installation will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
installation is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out unused [Optional] parameters. Otherwise,
the installation session will fail.

Installing Veeam Backup & Replication Console


To install the Veeam Backup & Replication console in the silent mode with the answer file, take the following
steps:

1. Copy the VbrConsoleAnswerFile_install.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBRConsole folder. This folder contains the following templates of
answer files used for installing, uninstalling, and upgrading the Veeam Backup & Replication console:

o VbrConsoleAnswerFile_install.xml — for installing the Veeam Backup & Replication console;

o VbrConsoleAnswerFile_uninstall.xml — for uninstalling the Veeam Backup & Replication


console;

o VbrConsoleAnswerFile_upgrade.xml — for upgrading the Veeam Backup & Replication console.

2. Configure installation parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (VbrConsole) and mode (install) specified in line 2:

<unattendedInstallationConfiguration bundle="VbrConsole" mode="install" ve


rsion="1.0">

3. After you make all the necessary changes in your answer file, start the installation by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your installation command:

378 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileConsol
e.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileConsole.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-installation


validations that do not work under the network logon, which will block the silent installation from
running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains the following parameters:

P a rameter Required? Default Description

ACCEPT_EULA Yes Specify 1 to accept the Veeam license


agreement.

ACCEPT_LICENSING_POLICY Yes Specify 1 to accept the Veeam


licensing policy.

ACCEPT_THIRDPARTY_LICENSES Yes Specify 1 to accept the license


agreement for 3rd party components
that Veeam incorporates.

ACCEPT_REQUIRED_SOFTWARE Yes Specify 1 to accept all required


software license agreements.

C:\Program
INSTALLDIR No Files\Veeam\Backup Path to the directory where the
and Replication Veeam Backup & Replication console
will be installed. If you do not specify
this parameter, the default
%ProgramFiles%\Veeam\Backup
and Replication installation path
is used.

AHV_INSTALL No 0 Specify 1 if you want to install


Nutanix AHV Plug-in for Veeam
Backup & Replication. Specify 0 if you
do not want to install the plugin.

379 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Required? Default Description

RHV_INSTALL No 0 Specify 1 if you want to install Red


Hat Virtualization Plug-in for Veeam
Backup & Replication. Specify 0 if you
do not want to install the plugin.

AW S_INSTALL No 1 Specify 1 if you want to install AWS


Plug-in for Veeam Backup &
Replication. Specify 0 if you do not
want to install the plugin.

AZURE_INSTALL No 1 Specify 1 if you want to install


Microsoft Azure Plug-in for Veeam
Backup & Replication. Specify 0 if you
do not want to install the plugin.

GCP _INSTALL No 1 Specify 1 if you want to install Google


Cloud Plug-in for Veeam Backup &
Replication. Specify 0 if you do not
want to install the plugin.

KASTEN_INSTALL No 1 Specify 1 if you want to install Kasten


K10 Plug-in for Veeam Backup &
Replication. Specify 0 if you do not
want to install the plugin.

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to reboot the


machine where you install
Veeam Backup & Replication after the
installation finishes. Specify 0 if you
do not want to reboot the machine.

Note that you must specify "1" in ACCEPT_EULA, ACCEPT_LICENSING_POLICY, ACCEPT_THIRDPARTY_LICENSES


and ACCEPT_REQUIRED_SOFTWARE parameters to proceed with the installation.

Installation Result Codes


The installation result is written into the installation log file located at your selected log folder. It may show one
of the following result codes:

Result Result
Cod e

0 success

1603 install failure

380 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Result Result
Cod e

3010 reboot required

3011 logoff required

Installation Error Codes


The installation error codes accompanied by their detailed description are displayed in the command line dialog.
They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the log folder
(by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving installation
results from the scripts or utilities that are used to run the installation. The error message may show one of the
following error codes:

E rror Description
Cod e

0 Installation has been completed successfully.

1 Product is already installed.

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

12 Reboot is required to finalize prerequisites installation.

13 Reboot is required to finalize the product installation.

14 Logoff is required to finalize the product installation.

101 Failed to start the installer.

102 Invalid answer file provided.

103 Invalid launch conditions.

104 Failed to initialize setup properties.

105 Failed to validate setup properties.

381 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E rror Description
Cod e

106 System configuration check detected some issues.

107 Failed to install prerequisites.

108 Failed to install a database server.

109 Failed to install the product.

110 Failed to update the product.

111 Failed to change a service status.

112 Failed to uninstall the product.

113 Unexpected error occurred.

382 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Veeam Backup & Replication in
Unattended Mode
NOTE

Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), this installation method is replaced with
Installing Veeam Backup & Replication in Unattended Mode with Answer File.

You can install Veeam Backup & Replication in the unattended mode using the command line interface. The
unattended installation mode does not require user interaction. You can use it to automate the installation
process in large deployments.

IMP ORTANT

When upgrading Veeam Backup & Replication in the unattended mode, most of the system checks that are
performed during the manual upgrade are omitted. Therefore, before performing the upgrade in the
unattended mode, make sure that you have checked all the p rerequisites specified in the Upgrade
Checklist. Also ensure that all the components of your infrastructure correspond to the System
Requirements.

Installation Order
Veeam Backup & Replication components must be installed in the order specified below. The order depends on
the type of server that you plan to deploy: backup server or Veeam Backup Enterprise Manager server.

Backup Server
If you want to deploy the backup server (server running Veeam Backup & Replication), you must install
components in the following order:

1. Veeam Backup Catalog

2. Veeam Backup & Replication Server

3. Veeam Explorers:

o Veeam Explorer for Active Directory

o Veeam Explorer for Exchange

o Veeam Explorer for SharePoint and Veeam Explorer for Microsoft OneDrive for Business

o Veeam Explorer for Microsoft SQL

o [Optional] Veeam Explorer for Microsoft Teams (required for self-service Veeam Backup for Microsoft
365 restores that take place through Cloud Connect Service Provider)

o Veeam Explorer for Oracle

o Veeam Explorer for PostgreSQL

4. [Optional] If you are planning to use the Agent Management feature, install the following components
(depending on the management OS):

o Redistributable package for Veeam Agent for Microsoft Windows

383 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Redistributable package for Veeam Agent for Linux

o Redistributable package for Veeam Agent for Mac

For more information about Veeam Agents, see the Veeam Agent Management Guide.

5. [Optional] If you are planning to use AWS Plug-in for Veeam Backup & Replication, Microsoft Azure Plug-
in for Veeam Backup & Replication or Google Cloud Plug -in for Veeam Backup & Replication, you must
install Veeam cloud plug-ins components.

6. [Optional] If you are planning to use Veeam Backup for Nutanix AHV, you must install Veeam Backup for
Nutanix AHV components.

7. [Optional] If you are planning to use Veeam Backup for RHV, you must install Veeam Backup for RHV
components.

8. [Optional] If you are planning to use Kasten K10 Plug -in for Veeam Backup & Replication, you must install
Kasten K10 Plug-in for Veeam Backup & Replication components.

Veeam Backup & Replication Console


If you want to deploy the Veeam Backup & Replication console, you must install the
Veeam Backup & Replication console component.

Veeam Backup Enterprise Manager Server


If you want to deploy the Veeam Backup Enterprise Manager server (server running Veeam Backup Enterprise
Manager), you must install components in the following order:

1. Veeam Backup Catalog

2. Veeam Backup Enterprise Manager

Veeam Cloud Connect Portal


If you want to deploy Veeam Cloud Connect Portal, you must install components in the following order:

1. Veeam Backup Enterprise Manager

2. Veeam Cloud Connect Portal

Before You Begin


Before you start unattended installation, perform the following steps:

1. [For backup server] Manually install PostgreSQL or Microsoft SQL Server and software components
required for the backup server operation. For more information, see Ba ckup Server in System
Requirements.

2. [For Veeam Explorers] Make sure that the version of a Veeam Explorer that you plan to install matches the
version of the Veeam Backup & Replication console on the target machine.

3. [For Veeam Backup Enterprise Manager server] Manually install PostgreSQL or Microsoft SQL Server and
software components required for the operation of the Veeam Backup Enterprise Manager server. For
more information, see the System Requirements section of the Enterprise Manager User Guide.

4. Download the Veeam Backup & Replication installation image from the Veeam website. You can burn the
downloaded image to a flash drive or mount the image to the target machine using disk image emulation
software.

384 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Log on to the target machine under the account that has the local Administrator permissions on the
machine. For more information, see Permissions.

6. Obtain a license file. The license file is required for Veeam Backup Enterprise Manager installation and is
optional for Veeam Backup & Replication installation. If you do not specify a path to the license file during
Veeam Backup & Replication installation, Veeam Backup & Replication will operate in the Community
Edition mode.

Installation Command-Line Syntax


You can install the following Veeam Backup & Replication components in the unattended mode:

• Veeam Backup Catalog

• Veeam Backup & Replication Server

• Veeam Backup & Replication Console

• Veeam Explorer for Microsoft Active Directory

• Veeam Explorer for Microsoft Exchange

• Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft OneDrive for Business

• Veeam Explorer for Microsoft SQL Server

• Veeam Explorer for Microsoft Teams

• Veeam Explorer for Oracle

• Veeam Explorer for PostgreSQL

• Redistributable Package for Veeam Agent for Linux

• Redistributable Package for Veeam Agent for Mac

• Redistributable Package for Veeam Agent for Microsoft Windows

• Veeam Backup Enterprise Manager

• Veeam Cloud Connect Portal

• Veeam Cloud Plug-Ins

• Veeam Backup for Nutanix AHV

• Veeam Backup for Red Hat Virtualization

• Veeam Plug-in for Kasten K10

Veeam Backup Catalog


To install Veeam Backup Catalog, use a command with the following syntax:

385 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPTEULA="1" ACCEPT
_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1 [
INSTALLDIR="<path_to_installdir >"][VM_CATALOGPATH="<path_to_catalog_shared_fol
der>"][VBRC_SERVICE_USER="<Veeam_Guest_Catalog_Service_account>"][VBRC_SERVICE_
PASSWORD="<Veeam_Guest_Catalog_Service_account_password>"] [VBRC_SERVICE_PORT="
<Veeam_Guest_Catalog_Service_port>"]

The command has the following parameters:

P a ramet Requir
Op tion Description
er ed

Creates an installation log file with the verbose output.

Specify a full path to the log file as the parameter value.


A setup log file created during the previous installation is
*v
/L No cleared.
logfile
Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\Cata
log.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

Installs Veeam Backup Catalog. Specify a full path to the


setup setup file as the parameter value.
/i Yes
file Example: /i
"C:\Veeam\VeeamBackupCatalog64.msi"

Specifies if you want to accept the Veeam license


agreement. Specify 1 to accept the license agreement
ACCEPTEULA 0/1 Yes and proceed with installation.

Example: ACCEPTEULA="1"

Specifies if you want to accept the license agreement for


3rd party components that Veeam incorporates. Specify
ACCEPT_THIRDPARTY_LICE 1 to accept the license agreement and proceed with
0/1 Yes
NSE S installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Specifies if you want to accept the Veeam licensing


policy. Specify 1 to accept the licensing policy and
ACCEPT_LICENSING_POLIC
0/1 Yes proceed with installation.
Y
Example: ACCEPT_LICENSING_POLICY="1"

386 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a ramet Requir
Op tion Description
er ed

Specifies if you want to accept the license agreements


for each of the required software that Veeam will install.
ACCEPT_REQUIRED_SOFTW Specify 1 to accept the license agreements and proceed
0/1 Yes
ARE with installation.

Example: ACCEPT_REQUIRED_SOFTWARE="1"

Installs the component to the specified location.

By default, Veeam Backup & Replication uses the


Backup Catalog subfolder in the C:\Program
INSTALLDIR path No Files\Veeam\Backup and Replication\ folder.

Example: INSTALLDIR="C:\Catalog\"
The component will be installed to the
C:\Catalog\Backup Catalog folder.

Specifies a path to the catalog folder where index files


must be stored.

By default, Veeam Backup & Replication creates the


VBRCatalog folder on a volume with the maximum
VM_CATALOGPATH path No
amount of free space, for example C:\VBRCatalog.

Example: VM_CATALOGPATH="C:\Backup\"
Index files will be stored to the
C:\Backup\VBRCatalog folder.

Specifies a user account under which the Veeam Guest


Catalog Service will run. The account must have full
control NTFS permissions on the VBRCatalog folder
where index files are stored.

If you do not specify this parameter, the Veeam Guest


VBRC_SERVICE_USER user No Catalog Service will run under the LocalSystem account.

Together with the VBRC_SERVICE_USER parameter, you


must specify the VBRC_SERVICE_PASSWORD parameter.

Example:
VBRC_SERVICE_USER="BACKUPSERVER\Administra
tor"

This parameter must be used if you have specified the


VBRC_SERVICE_USER parameter.
VBRC_SERVICE_ passwor
No Specifies a password for the account under which the
P ASSWORD d
Veeam Guest Catalog Service will run.

Example: VBRC_SERVICE_PASSWORD="1234"

387 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a ramet Requir
Op tion Description
er ed

Specifies a TCP port that will be used by the Veeam


Guest Catalog Service. By default, port number 9393 is
VBRC_SERVICE_PORT port No used.

Example: VBRC_SERVICE_PORT="9393"

Example
Suppose you want to install Veeam Backup Catalog with the following configuration:

• No user interaction

• Path to the MSI file: E:\Veeam\VeeamBackupCatalog64.msi

• Installation folder: default

• Catalog folder: default

• Service user account: VEEAM\Administrator

• Service user account password: 1243

• TCP communication port: 9391

The command to install Veeam Backup Catalog with such configuration will have the following parameters:

msiexec.exe /qn /i "E:\Veeam\VeeamBackupCatalog64.msi" ACCEPTEULA="1" ACCEPT_TH


IRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1 VBRC
_SERVICE_USER="VEEAM\Administrator" VBRC_SERVICE_PASSWORD="1234" VBRC_SERVICE_P
ORT="9391"

Veeam Backup & Replication Server


To install the Veeam Backup & Replication server, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1
[INSTALLDIR="<path_to_installdir >"] [VBR_LICENSE_FILE="<path_to_license_file>"
] [VBR_LICENSE_AUTOUPDATE="1"] [VBR_SERVICE_USER="<Veeam_B&R_Service_account>"]
[VBR_SERVICE_PASSWORD="<Veeam_B&R_Service_account_password>"] [VBR_SERVICE_PORT
="<Veeam_B&R_Service_port>"] [VBR_SECURE_CONNECTIONS_PORT="<SSL_port>"] [VBR_SQ
LSERVER_ENGINE = 1][VBR_SQLSERVER_SERVER="<SQL_server>"] [VBR_SQLSERVER_DATABAS
E="<database_name>"][VBR_SQLSERVER_AUTHENTICATION="0"] [VBR_SQLSERVER_USERNAME=
"<SQL_auth_username>"] [VBR_SQLSERVER_PASSWORD="<SQL_auth_password>"] [VBR_IRCA
CHE="<path_to_instant_recovery_cache_folder>"] [VBR_CHECK_UPDATES="1"][VBR_AUTO
_UPGRADE="1"]

388 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

This command does not install the Veeam Backup & Replication console and the Veeam PowerShell
module. To install the Veeam Backup & Replication console, run the command specified in Veeam Backup &
Replication Console. The Veeam PowerShell module will be installed with the Veeam Backup & Replication
console.

The command has the following parameters:

Op tion P a rameter Requir Description


ed

/L *v logfile No Creates an installation log file with the verbose output.


Specify a full path to the log file as the parameter value.
A setup log file created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\Backu
p.txt"

/q n Yes Sets the user interface level to “no”, which means no user
interaction is needed during installation.

/i setup file Yes Installs the Veeam Backup & Replication server. Specify a
full path to the setup file as the parameter value.

Example: /i "E:\Backup\Server.x64.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LI 0/1 Yes Specifies if you want to accept the license agreement for
CE NSES 3rd party components that Veeam incorporates. Specify 1
to accept the license agreement and proceed with
installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

ACCEPT_LICENSING_POLI 0/1 Yes Specifies if you want to accept the Veeam licensing
CY policy. Specify 1 to accept the licensing policy and
proceed with installation.

Example: ACCEPT_LICENSING_POLICY="1"

389 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

ACCEPT_REQUIRED_SOFT 0/1 Yes Specifies if you want to accept the license agreements for
W ARE each of the required software that Veeam will install.
Specify 1 to accept the license agreements and proceed
with installation.

Example: ACCEPT_REQUIRED_SOFTWARE="1"

INSTALLDIR path No Installs the component to the specified location. By


default, Veeam Backup & Replication uses the Backup
subfolder of the C:\Program Files\Veeam\Backup
and Replication\ folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Backup folder.

VBR_LICENSE_FILE license No Specifies a full path to the license file. If you do not
path specify this parameter, Veeam Backup & Replication will
operate in the Community Edition mode.

Example:
VBR_LICENSE_FILE="C:\Users\Administrator\De
sktop\enterprise -
veeam_backup_trial_0_30.lic"

VBR_LICENSE_AUTOUPD 0/1 No Specifies if you want to update the license automatically


ATE (enables usage reporting). If you do not specify this
parameter, the automatic update will be enabled. For
Community Edition and NFR it must be set to 1. For
licenses without license ID information it must be set to
0.

Example: VBR_LICENSE_AUTOUPDATE="1"

VBR_SERVICE_USER user No Specifies the account under which the Veeam Backup
Service will run. The account must have full control NTFS
permissions on the VBRCatalog folder where index files
are stored and the Database owner rights for the
configuration database on the Microsoft SQL Server
where the configuration database is deployed.

If you do not specify this parameter, the Veeam Backup


Service will run under the LocalSystem account.

Together with the VBR_SERVICE_USER parameter, you


must specify the VBR_SERVICE_PASSWORD parameter.

Example:
VBR_SERVICE_USER="BACKUPSERVER\Administrato
r"

390 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBR_SERVICE_PASSWOR password No This parameter must be used if you have specified the
D VBR_SERVICE_USER parameter.

Specifies a password for the account under which the


Veeam Backup Service will run.

Example: VBR_SERVICE_PASSWORD="1234"

VBR_SERVICE_PORT port No Specifies a TCP port that will be used by the Veeam
Backup Service.

By default, the port number 9392 is used.

Example: VBR_SERVICE_PORT="9395"

VBR_SECURE_CONNECTI port No Specifies a port used for communication between the


ONS_PORT mount server and the backup server. By default, port
9401 is used.

Example: VBR_SECURE_CONNECTIONS_PORT="9402"

VBR_SQLSERVER_ENGINE 0/1 No Specifies the SQL engine to be used to deploy the


configuration database.

Specify 0 if you want to use Microsoft SQL Server as your


configuration database. If you do not specify this
parameter, Veeam Backup & Replication will use
PostgreSQL as your configuration database (default value
is 1).

Example: VBR_SQLSERVER_ENGINE="1"

391 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBR_SQLSERVER_SERVER SQL No Depending on the value of parameter


server\inst VBR_SQLSERVER_ENGINE, this parameter has different
ance format and default value:
or
SQL If VBR_SQLSERVER_ENGINE=0,
Server:por VBR_SQLSERVER_SERVER specifies a Microsoft SQL
t server and instance on which the configuration database
will be deployed in the following format: SQL
server\instance. By default,
Veeam Backup & Replication uses
(local)\VEEAMSQL2016 for machines running
Microsoft Windows Server.

If VBR_SQLSERVER_ENGINE=1,
VBR_SQLSERVER_SERVER specifies a PostgreSQL server
and port on which the configuration database will be
deployed in the following format: SQL Server:port.
By default, Veeam Backup & Replication uses
(local):5432 for machines running PostgreSQL.

Examples:
VBR_SQLSERVER_SERVER="BACKUPSERVER\VEEAMSQL
2016_MY"
VBR_SQLSERVER_SERVER="(local):5432"

VBR_SQLSERVER_DATAB database No Specifies a name for the configuration database.


ASE
By default, the configuration database is deployed with
the VeeamBackup name.

Example:
VBR_SQLSERVER_DATABASE="VeeamBackup"

VBR_SQLSERVER_ 0/1 No Specifies if you want to use the SQL Server authentication
AUTHE NTICATION mode to connect to the Microsoft SQL Server where the
Veeam Backup & Replication configuration database is
deployed.

Specify 1 if you want to use the SQL Server


authentication mode. If you do not specify this
parameter, Veeam Backup & Replication will connect to
the Microsoft SQL Server in the Microsoft Windows
authentication mode (default value is 0).

Together with this parameter, you must specify the


following parameters: VBR_SQLSERVER_USERNAME and
VBR_SQLSERVER_PASSWORD.

Example: VBR_SQLSERVER_AUTHENTICATION="1"

392 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBR_SQLSERVER_ user No This parameter must be used if you have specified the
USE RNAME VBR_SQLSERVER_AUTHENTICATION parameter.

Specifies a LoginID to connect to the Microsoft SQL


Server in the SQL Server authentication mode.

Example: VBR_SQLSERVER_USERNAME="sa"

VBR_SQLSERVER_ password No This parameter must be used if you have specified the
P ASSWORD VBR_SQLSERVER_AUTHENTICATION parameter.

Specifies a password to connect to the Microsoft SQL


Server in the SQL Server authentication mode.

Example: VBR_SQLSERVER_PASSWORD="1234"

VBR_IRCACHE path No Specifies the folder to which the instant recovery cache
will be stored. By default, Veeam Backup & Replication
uses the folder on a volume with the maximum amount of
free space, for example,
C:\ProgramData\Veeam\Backup\IRCache\.

Example:
VBR_IRCACHE="C:\ProgramData\Veeam\Backup\IR
Cache2\"

VBR_CHECK_UPDATES 0/1 No Specifies if you want Veeam Backup & Replication to


automatically check for new product versions and
updates and hypervisor updates for Microsoft Hyper-V
hosts.

Specify 0 if you do not want to check for updates. If you


do not specify this parameter,
Veeam Backup & Replication will automatically check for
updates (default value is 1).

Example: VBR_CHECK_UPDATES="0"

VBR_AUTO_UPGRADE 0/1 No Specifies if you want Veeam Backup & Replication to


automatically upgrade existing components in the backup
infrastructure. Veeam Backup & Replication performs
automatic upgrade after the Veeam Backup Service is
started on the backup server.

Specify 1 to enable automatic upgrade. If you do not


specify this parameter, Veeam Backup & Replication will
not automatically upgrade existing components (default
value is 0).

Example: VBR_AUTO_UPGRADE="1"

393 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Example
Suppose you want to install Veeam Backup & Replication with the following configuration:

• Installation log location: C:\logs\log1.txt

• No user interaction

• Path to the MSI file: E:\Backup\Server.x64.msi

• Installation folder: D:\Program Files\Veeam

• License file location: C:\License\veeam_license.lic

• Service user account: VEEAM\Administrator

• Service user account password: 1243

• Service port: default

• TLS port: default

• Configuration database engine and database name: default

The command to install Veeam Backup & Replication with such configuration will have the following
parameters:

msiexec.exe /L*v "C:\logs\log1.txt" /qn /i "E:\Backup\Server.x64.msi" ACCEPT_EU


LA="1" ACCEPT_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED
_SOFTWARE=1 INSTALLDIR="D:\Program Files\Veeam" VBR_LICENSE_FILE="C:\License\ve
eam_license.lic" VBR_SERVICE_USER="VEEAM\Administrator" VBR_SERVICE_PASSWORD="1
234"

Veeam Backup & Replication Console


To install the Veeam Backup & Replication console, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1
[INSTALLDIR="<path_to_installdir >"]

NOTE

This command also installs the Veeam PowerShell module.

394 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Requir Description


er ed

/L *v No Creates an installation log file with the verbose output.


logfile
Specify a full path to the log file as the parameter value.
A setup log file created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\Cons
ole.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs the Veeam Backup & Replication console.


file
Specify a full path to the setup file as the parameter
value.

Example: /i "E:\Backup\Shell.x64.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICE 0/1 Yes Specifies if you want to accept the license agreement for
NSE S 3rd party components that Veeam incorporates. Specify
1 to accept the license agreement and proceed with
installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

ACCEPT_LICENSING_POLIC 0/1 Yes Specifies if you want to accept the Veeam licensing
Y policy. Specify 1 to accept the licensing policy and
proceed with installation.

Example: ACCEPT_LICENSING_POLICY="1"

ACCEPT_REQUIRED_SOFTW 0/1 Yes Specifies if you want to accept the license agreements
ARE for each of the required software that Veeam will install.
Specify 1 to accept the license agreements and proceed
with installation.

Example: ACCEPT_REQUIRED_SOFTWARE="1"

395 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a ramet Requir Description
er ed

INSTALLDIR path No Installs the component to the specified location.

By default, Veeam Backup & Replication uses the


Console subfolder of the C:\Program
Files\Veeam\Backup and Replication\ folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Console folder.

Example
Suppose you want to install the Veeam Backup & Replication console with the following configuration:

• No user interaction

• Path to the MSI file: E:\Backup\Shell.x64.msi

• Installation folder: C:\Backup

The command to install the Veeam Backup & Replication console with such configuration will have the following
parameters:

msiexec.exe /L*v "C:\logs\log1.txt" /qn /i "E:\Backup\Shell.x64.msi" ACCEPT_EUL


A="1" ACCEPT_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_
SOFTWARE=1 INSTALLDIR="C:\Backup\"

Veeam Explorer for Microsoft Active Directory


To install Veeam Explorer for Microsoft Active Directory, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

396 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Requir Description


er ed

/L *v No Creates an installation log file with the verbose output.


logfile
Specify a full path to the log file as the parameter value.
A setup log file created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VEAD
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Microsoft Active Directory.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerforActiveDirect
ory.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICE 0/1 Yes Specifies if you want to accept the license agreement for
NSE S 3rd party components that Veeam incorporates. Specify
1 to accept the license agreement and proceed with
installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for Microsoft Exchange


To install Veeam Explorer for Microsoft Exchange, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

397 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VEX
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Microsoft Exchange.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerforExchange.ms
i"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for Microsoft SharePoint and Veeam Explorer for


Microsoft OneDrive for Business
Veeam Explorer for Microsoft SharePoint is installed together with Veeam Explorer for Microsoft OneDrive for
Business from the same setup file.

To install Veeam Explorer for Microsoft SharePoint and Veeam Explorer for Microsoft OneDrive for Business, use
a command with the following syntax:

398 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP
T_THIRDPARTY_LICENSES="1"

The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v No Creates an installation log file with the verbose output.


logfile
Specify a full path to the log file as the parameter
value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VES
P.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Microsoft SharePoint and


file Veeam Explorer for Microsoft OneDrive for Business.

Specify a full path to the setup file as the parameter


value.
Veeam Backup & Replication installs both Veeam
Explorer for Microsoft SharePoint and Veeam Explorer
for Microsoft OneDrive for Business from the same
setup file.

Example: /i
"C:\Explorers\VeeamExplorerforSharePoint.
msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICE 0/1 Yes Specifies if you want to accept the license agreement
NSE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for Microsoft SQL Server


To install Veeam Explorer for Microsoft SQL Server, use a command with the following syntax:

399 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP
T_THIRDPARTY_LICENSES="1"

The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v No Creates an installation log file with the verbose output.


logfile
Specify a full path to the log file as the parameter
value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VES
QL.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Microsoft SQL Server.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerforSQL.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICE 0/1 Yes Specifies if you want to accept the license agreement
NSE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for Microsoft Teams


To install Veeam Explorer for Microsoft Teams, use a command with the following syntax:

msiexec.exe /L*v "C:\ProgramData\Veeam\Setup\Temp\Logs\VET.txt" /qn /i "F:\Expl


orers\VeeamExplorerForTeams.msi" ACCEPT_EULA="1" ACCEPT_THIRDPARTY_LICENSES="1"

400 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VET
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Microsoft Teams.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerForTeams.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for Oracle


To install Veeam Explorer for Oracle, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

401 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VEO
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for Oracle.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerforOracle.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Explorer for PostgreSQL


To install Veeam Explorer for PostgreSQL, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

402 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VEO
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs Veeam Explorer for PostgreSQL.


file
Specify a full path to the setup file as the parameter
value.

Example: /i
"C:\Explorers\VeeamExplorerforPostgreSQL.
msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Redistributable Package for Veeam Agent for Linux


To install the redistributable package for Veeam Agent for Linux, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

403 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VAL
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs the redistributable package for Veeam Agent


file for Linux.

Specify a full path to the setup file as the parameter


value.

Example: /i "F:\Packages\VALRedist.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Redistributable Package for Veeam Agent for Mac


To install the redistributable package for Veeam Agent for Mac, use a command with the following syntax :

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

404 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VAM
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs the redistributable package for Veeam Agent


file for Mac.

Specify a full path to the setup file as the parameter


value.

Example: /i "F:\Packages\VAMRedist.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Redistributable Package for Veeam Agent for Microsoft Windows


To install the redistributable package for Veeam Agent for Microsoft Windows, use a command with the
following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1"

405 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command has the following parameters:

Op tion P a ramet Require Description


er d

/L *v logfile No Creates an installation log file with the verbose


output.

Specify a full path to the log file as the parameter


value. A setup log file created during the previous
installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\VAW
.txt"

/q n Yes Sets the user interface level to “no”, which means no


user interaction is needed during installation.

/i setup Yes Installs the redistributable package for Veeam Agent


file for Microsoft Windows.

Specify a full path to the setup file as the parameter


value.

Example: /i "F:\Packages\VAWRedist.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement
and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept the license agreement
SE S for 3rd party components that Veeam incorporates.
Specify 1 to accept the license agreement and proceed
with installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

Veeam Backup Enterprise Manager


To install Veeam Backup Enterprise Manager, use a command with the following syntax:

406 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP
T_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1
[INSTALLDIR="<path_to_installdir >"] VBREM_LICENSE_FILE="<path_to_license_file>
" [VBREM_LICENSE_AUTOUPDATE="1"] [VBREM_SERVICE_USER="<Veeam_EM_Service_account
>"][VBREM_SERVICE_PASSWORD="<Veeam_EM_Service_account_password>"] [VBREM_SERVIC
E_PORT="<Veeam_EM_Service_port>"] [VBREM_SQLSERVER_ENGINE=1]
[VBREM_SQLSERVER_SERVER="<SQL_server>"] [VBREM_SQLSERVER_DATABASE="<database_na
me>"][VBREM_SQLSERVER_AUTHENTICATION="0"] [VBREM_SQLSERVER_USERNAME="<SQL_auth_
username>"] [VBREM_SQLSERVER_PASSWORD="<SQL_auth_password>"] [VBREM_TCPPORT="<T
CP_port_for_web_site>"] [VBREM_SSLPORT="<SSL_port_for_web_site>”]>"] [VBREM_THU
MBPRINT="<certificate_hash>"] [VBREM_RESTAPISVC_PORT="<TCP_port_for_RestApi_ser
vice>"] [VBREM_RESTAPISVC_SSLPORT="<SSL_port_for_RestApi_service>"][VBREM_CHECK
_UPDATES="1"]

The command has the following parameters:

Op tion P a rameter Requir Description


ed

/L *v logfile No Creates an installation log file with the verbose output.

Specify a full path to the log file as the parameter value. A


setup log file created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\EM.txt
"

/q n Yes Sets the user interface level to “no”, which means no user
interaction is needed during installation.

/i setup file Yes Installs Veeam Backup Enterprise Manager.

Specify a full path to the setup file as the parameter value.

Example: /i
"C:\Veeam\EnterpriseManager\BackupWeb_x64.ms
i"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement and
proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_ 0/1 Yes Specifies if you want to accept the license agreement for
LICENSES 3rd party components that Veeam incorporates. Specify 1
to accept the license agreement and proceed with
installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

407 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

ACCEPT_LICENSING_PO 0/1 Yes Specifies if you want to accept the Veeam licensing policy.
LICY Specify 1 to accept the licensing policy and proceed with
installation.

Example: ACCEPT_LICENSING_POLICY="1"

ACCEPT_REQUIRED_SO 0/1 Yes Specifies if you want to accept the license agreements for
FTW ARE each of the required software that Veeam will install.
Specify 1 to accept the license agreements and proceed
with installation.

Example: ACCEPT_REQUIRED_SOFTWARE="1"

INSTALLDIR path No Installs the component to the specified location.

By default, Veeam Backup & Replication uses the


Enterprise Manager subfolder of the C:\Program
Files\Veeam\ folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Enterprise Manager folder.

VBRE M_LICENSE_FILE license Yes Specifies a full path to the license file.
path
Example:
VBREM_LICENSE_FILE="C:\Users\Administrator\D
esktop\enterprise -
veeam_backup_trial_0_30.lic"

VBRE M_LICENSE_AUTO 0/1 No Specifies if you want to update the license automatically
UP DATE (enables usage reporting). If you do not specify this
parameter, the automatic update will be enabled. For
Community Edition and NFR it must be set to 1. For licenses
without license ID information it must be set to 0.

Example: VBREM_LICENSE_AUTOUPDATE="1"

408 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBRE M_SERVICE_USER user No Specifies the account under which the Veeam Backup
Enterprise Manager Service will run. The account must have
full control NTFS permissions on the VBRCatalog folder
where index files are stored and the Database owner rights
for the Veeam Backup Enterprise Manager configuration
database on the Microsoft SQL Server that you plan to use.

If you do not specify this parameter, the Veeam Backup


Enterprise Manager Service will run under the LocalSystem
account.

Together with the VBREM_SERVICE_USER parameter, you


must specify the VBREM_SERVICE_PASSWORD parameter.

Example:
VBRC_SERVICE_USER="BACKUPSERVER\Administrato
r"

VBRE M_SERVICE_PASS password No Specifies a password for the account under which the
W ORD Veeam Backup Enterprise Manager Service will run.

Example: VBREM_SERVICE_PASSWORD="1234"

VBRE M_SERVICE_PORT Port No Specifies a TCP port that will be used by the Veeam Backup
Enterprise Manager Service.

By default, the port number 9394 is used.

Example: VBREM_SERVICE_PORT ="9394"

VBRE M_SQLSERVER_EN 0/1 No Specifies the SQL engine to be used to deploy the
GINE configuration database.

Specify 0 if you want to use Microsoft SQL Server as your


configuration database. If you do not specify this
parameter, Veeam Backup & Replication will use
PostgreSQL as your configuration database (default value is
1).

Example: VBREM_SQLSERVER_ENGINE="1"

409 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBRE M_SQLSERVER_SE SQL No Depending on the value of parameter


RVE R server\inst VBREM_SQLSERVER_ENGINE, this parameter has different
ance format and default value:
or
SQL If VBREM_SQLSERVER_ENGINE=0,
Server:por VBREM_SQLSERVER_SERVER specifies a Microsoft SQL
t server and instance on which the configuration database
will be deployed in the following format: SQL
server\instance. By default,
Veeam Backup & Replication uses
(local)\VEEAMSQL2016 for machines running Microsoft
Windows Server.

If VBREM_SQLSERVER_ENGINE=1,
VBREM_SQLSERVER_SERVER specifies a PostgreSQL server
and port on which the configuration database will be
deployed in the following format: SQL Server:port. By
default, Veeam Backup & Replication uses (local):5432
for machines running PostgreSQL.

Examples:
VBREM_SQLSERVER_SERVER="BACKUPSERVER\VEEAMSQ
L2016_MY"
VBREM_SQLSERVER_SERVER="(local):5432"

VBRE M_SQLSERVER_D database No Specifies a name of the Veeam Backup Enterprise Manager
ATABASE database.

By default, the database is deployed with the


VeeamBackupReporting name.

Example:
VBREM_SQLSERVER_DATABASE="VeeamBackupReporti
ng01"

VBRE M_SQLSERVER_ 0/1 No Specifies if you want to use the Microsoft SQL Server
AUTHE NTICATION authentication mode to connect to the Microsoft SQL
Server where the Veeam Backup Enterprise Manager is
deployed.

Set this parameter to 1 if you want to use the SQL Server


authentication mode. If you do not specify this parameter,
Veeam Backup Enterprise Manager will connect to the
Microsoft SQL Server in the Microsoft Windows
authentication mode (default value is 0).

Together with this parameter, you must specify the


following parameters: VBREM_SQLSERVER_USERNAME and
VBREM_SQLSERVER_PASSWORD .

Example: VBREM_SQLSERVER_AUTHENTICATION="1"

410 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBRE M_SQLSERVER_US user No This parameter must be used if you have specified the
E RNAME VBREM_SQLSERVER_AUTHENTICATION parameter.

Specifies a LoginID to connect to the Microsoft SQL Server


in the SQL Server authentication mode.

Example: VBREM_SQLSERVER_USERNAME="sa"

VBRE M_SQLSERVER_PA password No This parameter must be used if you have specified the
SSW ORD VBR_SQLSERVER_AUTHENTICATION parameter.

Specifies a password to connect to the Microsoft SQL


Server in the SQL Server authentication mode.

Example: VBREM_SQLSERVER_USERNAME="1234"

VBRE M_TCPPORT port No Specifies a TCP port that will be used by the Veeam Backup
Enterprise Manager website.

By default, the port number 9080 is used.

Example: VBREM_TCPPORT="9080"

VBRE M_SSLPORT port No Specifies a port that will be used by the Veeam Backup
Enterprise Manager website.

By default, the port number 9443 is used.

Example: VBREM_SSLPORT="9443"

VBRE M_THUMBPRINT hash No Specifies the certificate to be used by Veeam Backup


Enterprise Manager Service and Veeam RESTful API Service.
If this parameter is not specified, a new certificate will be
generated by openssl.exe.

Example:
VBREM_THUMBPRINT="0677d0b8f27caccc966b15d807
b41a101587b488"

VBRE M_RESTAPISVC_P port No Specifies a TCP port that will be used by the Veeam Backup
ORT Enterprise Manager RESTful API Service.

By default, the port number 9399 is used.

Example: VBREM_RESTAPISVC_PORT="9399"

411 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

VBRE M_RESTAPISVC_S port No Specifies a port that will be used by the Veeam RESTful API
SLP ORT Service.

By default, the port number 9398 is used.

Example: VBREM_RESTAPISVC_SSLPORT="9398"

VBRE M_CONFIG_SCHA 0/1 No Specifies if the TLS 1.2 protocol will be used for secure
NNE L communication with the Veeam Backup Enterprise Manager
website.

VBRE M_CHECK_UPDAT 0/1 No Specifies if you want Veeam Backup Enterprise Manager to
ES automatically check for new product versions and updates.

Specify 0 if you do not want to check for updates. If you do


not specify this parameter, Veeam Backup Enterprise
Manager will automatically check for updates (default
value is 1).

Example: VBREM_CHECK_UPDATES="0"

Example
Suppose you want to install Veeam Backup Enterprise Manager with the following settings:

• Installation log location: C:\logs\log1.txt

• No user interaction

• Path to the MSI file: E:\Veeam\EnterpriseManager\BackupWeb_x64.msi

• Installation folder: D:\Program Files\Veeam

• License file location: C:\License\veeam_license.lic

• Service user account: VEEAM\Administrator

• Service user account password: 1243

• Service port: default

• Microsoft SQL Server database: BACKUPSERVER\VEEAMSQL2012_MY

• Database name: VeeamReporting01

• TCP and TLS ports: default

• Certificate: default

• TCP port for RESTful API: 9396

• TLS port for RESTful API: 9397

• No check for updates

412 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command to install Veeam Backup Enterprise Manager with such configuration will have the following
parameters:

msiexec.exe /L*v "C:\logs\log1.txt" /qn /i "E:\Veeam\EnterpriseManager\BackupWe


b_x64.msi" ACCEPT_EULA="1" ACCEPT_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLI
CY=1 ACCEPT_REQUIRED_SOFTWARE=1 INSTALLDIR="D:\Program Files\Veeam" VBREM_LICEN
SE_FILE="C:\License\veeam_license.lic" VBREM_SERVICE_USER="VEEAM\Administrator"
VBREM_SERVICE_PASSWORD="1234" VBREM_SQLSERVER_SERVER="BACKUPSERVER\VEEAMSQL2012
_MY" VBREM_SQLSERVER_DATABASE="VeeamReporting01" VBREM_RESTAPISVC_PORT="9396" V
BREM_CHECK_UPDATES="0"

Veeam Cloud Connect Portal


Veeam Cloud Connect Portal requires Veeam Backup Enterprise Manager of the same version to be installed on
the target machine.

To install Veeam Cloud Connect Portal, use a command with the following syntax:

msiexec.exe [/L*v "<path_to_log>"] /qn /i "<path_to_msi>" ACCEPT_EULA="1" ACCEP


T_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1
[INSTALLDIR="<path_to_installdir >"] VBCP_SSLPORT="<SSL_port">

The command has the following parameters:

Op tion Paramet Requir Description


er ed

/L *v No Creates an installation log file with the verbose output.


logfile Specify a full path to the log file as the parameter value. A
setup log file created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Logs\CloudP
ortal.txt"

/q n Yes Sets the user interface level to “no”, which means no user
interaction is needed during installation.

/i setup Yes Installs the Veeam Cloud Connect Portal. Specify a full
file path to the setup file as the parameter value.

Example: /i "C:\Cloud
portal\BackupCloudPortal_x64.msi"

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam license
agreement. Specify 1 to accept the license agreement and
proceed with installation.

Example: ACCEPT_EULA="1"

413 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion Paramet Requir Description
er ed

ACCEPT_THIRDPARTY_LIC 0/1 Yes Specifies if you want to accept the license agreement for
E NSES 3rd party components that Veeam incorporates. Specify 1
to accept the license agreement and proceed with
installation.

Example: ACCEPT_THIRDPARTY_LICENSES="1"

ACCEPT_LICENSING_POLI 0/1 Yes Specifies if you want to accept the Veeam licensing policy.
CY Specify 1 to accept the licensing policy and proceed with
installation.

Example: ACCEPT_LICENSING_POLICY="1"

ACCEPT_REQUIRED_SOFT 0/1 Yes Specifies if you want to accept the license agreements for
W ARE each of the required software that Veeam will install.
Specify 1 to accept the license agreements and proceed
with installation.

Example: ACCEPT_REQUIRED_SOFTWARE="1"

INSTALLDIR path No Installs the component to the specified location.

By default, Veeam Backup & Replication uses the


CloudPortal subfolder of the C:\Program
Files\Veeam\Backup and Replication\ folder.

Example: INSTALLDIR="C:\Backup\".
The component will be installed to the
C:\Backup\CloudPortal folder

VBCP _SSLPORT port No Specifies a port that will be used by the Veeam Cloud
Connect Portal website.

By default, the port number 6443 is used.

Example: VBREM_SSLPORT="7443"

Example
Suppose you want to install Veeam Cloud Connect Portal with the following configuration:

• No user interaction

• Path to the MSI file: E:\Cloud portal\BackupCloudPortal_x64.msi

• Installation folder: C:\Backup

• TLS port: default

414 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The command to install Veeam Cloud Connect Portal with such configuration will have the following
parameters:

msiexec.exe /qn /L*v "C:\logs\log1.txt" /qn /i "E:\Cloud portal\BackupCloudPort


al_x64.msi" ACCEPT_EULA="1" ACCEPT_THIRDPARTY_LICENSES="1" ACCEPT_LICENSING_POL
ICY=1 ACCEPT_REQUIRED_SOFTWARE=1 INSTALLDIR="C:\Backup\"

Veeam Cloud Plug-Ins


You can install the following cloud plug-ins in the unattended mode:

• AWS Plug-in for Veeam Backup & Replication

• Microsoft Azure Plug-in for Veeam Backup & Replication

• Google Cloud Plug-in for Veeam Backup & Replication

Note that if you want to manage cloud plug-ins in the Veeam Backup & Replication interface, you must install
both the cloud plug-in service and the cloud plug-in UI.

To install cloud plug-ins, use a command with the following syntax:

msiexec /qn /i <msi> ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

The command has the following parameters:

Op tion P a rameter Requi Description


red

/L *v logfile No Creates an installation log file with the


verbose output. Specify a full path to the log
file as the parameter value. A setup log file
created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\L
ogs\Backup.txt"

/q n Yes Sets the user interface level to “no”, which


means no user interaction is needed during
installation.

/i setup file Yes Installs the Veeam Backup & Replication


server. Specify a full path to the setup file as
the parameter value.

Example: /i
"C:\Veeam\Server.x64.msi"

415 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requi Description
red

• AWSPlugin.msi
msi Yes AWSPlugin.msi: Installs the AWS Plug-in for
• AWSPluginUI.msi
Veeam Backup & Replication services.
•
MicrosoftAzurePl AWSPluginUI.msi: Installs the AWS Plug-in
for Veeam Backup & Replication UI.
ugin.msi
• MicrosoftAzurePlugin.msi: Installs the
MicrosoftAzurePl Microsoft Azure Plug-in for Veeam Backup &
Replication services.
uginUI.msi
• GCPPlugin.msi MicrosoftAzurePluginUI.msi: Installs
• GCPPluginUI.msi the Microsoft Azure Plug-in for Veeam Backup
& Replication UI.

GCPPlugin.msi: Installs the Google Cloud


Plug-in for Veeam Backup & Replication
services.

GCPPluginUI.msi: Installs the Google Cloud


Plug-in for Veeam Backup & Replication UI.

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam


license agreement. Specify 1 to accept the
license agreement and proceed with
installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_ 0/1 Yes Specifies if you want to accept the license


LICENSES agreement for 3rd party components that
Veeam incorporates. Specify 1 to accept the
license agreement and proceed with
installation.

Example:
ACCEPT_THIRDPARTY_LICENSES="1"

INSTALLDIR path No Installs the component to the specified


location. By default,
Veeam Backup & Replication uses the Backup
subfolder of the C:\Program
Files\Veeam\Backup and
Replication\ folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Backup folder.

416 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Examples
Installing AWS Plug-in for Veeam Backup & Replication Service and UI
To install the AWS Plug-in for Veeam Backup & Replication service and the AWS Plug -in for Veeam Backup &
Replication UI to Veeam Backup & Replication, perform the following steps:

1. Run the following command to install the AWS Plug-in for Veeam Backup & Replication service.

msiexec /qn /i AWSPlugin.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

2. Run the following command to install the AWS Plug-in for Veeam Backup & Replication UI.

msiexec /qn /i AWSPluginUI.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

Veeam Backup for Nutanix AHV


You can install the Nutanix AHV Plug-in in the unattended mode. Note that if you want to manage AHV VM
backup in the Veeam Backup & Replication console, you must install all the components: the Nutanix AHV Plug -
in service (NutanixAHVPlugin.msi), the Nutanix AHV Plug-in appliance VM image files
(NutanixAHVPluginProxy.msi) and the UI components of Nutanix AHV Plug-in
(NutanixAHVPluginUI.msi).

To install Nutanix AHV Plug-in, use a command with the following syntax:

msiexec /qn /i <msi> ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

The command has the following parameters:

Op tion P a rameter Requi Description


red

/L *v logfile No Creates an installation log file with the


verbose output. Specify a full path to the log
file as the parameter value. A setup log file
created during the previous installation is
cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\L
ogs\Backup.txt"

/q n Yes Sets the user interface level to “no”, which


means no user interaction is needed during
installation.

417 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requi Description
red

/i setup file Yes Installs the Veeam Backup & Replication


server. Specify a full path to the setup file as
the parameter value.

Example: /i
"C:\Veeam\Server.x64.msi"

•
msi Yes NutanixAHVPlugin.msi: Installs the
NutanixAHVPlugi
Nutanix AHV Plug-in services.
n.msi
• NutanixAHVPluginProxy.msi: Installs the
Nutanix AHV Plug-in appliance VM image
NutanixAHVPlugi
files.
nProxy.msi
• NutanixAHVPluginUI.msi: Installs UI
components of the Nutanix AHV Plug-in.
NutanixAHVPlugi
nUI.msi

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam


license agreement. Specify 1 to accept the
license agreement and proceed with
installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_ 0/1 Yes Specifies if you want to accept the license


LICENSES agreement for 3rd party components that
Veeam incorporates. Specify 1 to accept the
license agreement and proceed with
installation.

Example:
ACCEPT_THIRDPARTY_LICENSES="1"

INSTALLDIR path No Installs the component to the specified


location. By default,
Veeam Backup & Replication uses the Backup
subfolder of the C:\Program
Files\Veeam\Backup and
Replication\ folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Backup folder.

418 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Examples
Installing Nutanix AHV Plug-in Service and UI
To install the Nutanix AHV Plug-in service and UI components to Veeam Backup & Replication, perform the
following steps:

1. Run the following command to install the Nutanix AHV Plug -in service.

msiexec /qn /i NutanixAHVPlugin.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EU


LA=1

2. Run the following command to install the Nutanix AHV Plug -in appliance VM image files.

msiexec /qn /i NutanixAHVPluginProxy.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCE


PT_EULA=1

3. Run the following command to install UI components of Nutanix AHV Plug -in.

msiexec /qn /i NutanixAHVPluginUI.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_


EULA=1

Veeam Backup for Red Hat Virtualization


You can install the RHV Plug-in in the unattended mode. Note that if you want to manage RHV VM backup in the
Veeam Backup & Replication console, you must install all the components: the RHV Plug -in service
(RHVPlugin.msi), the RHV Plug-in proxy VM image files (RHVPluginProxy.msi) and the UI components of
RHV Plug-in (RHVPluginUI.msi).

To install RHV Plug-in, use a command with the following syntax:

msiexec /qn /i <msi> ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

The command has the following parameters:

Op tion P a rameter Requir Description


ed

/L *v logfile No Creates an installation log file with the verbose


output. Specify a full path to the log file as the
parameter value. A setup log file created during
the previous installation is cleared.

Example: /L*v
"C:\ProgramData\Veeam\Setup\Temp\Log
s\Backup.txt"

419 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Requir Description
ed

/q n Yes Sets the user interface level to “no”, which


means no user interaction is needed during
installation.

/i setup file Yes Installs the Veeam Backup & Replication server.
Specify a full path to the setup file as the
parameter value.

Example: /i "C:\Veeam\Server.x64.msi"

• RHVPlugin.msi
msi Yes RHVPlugin.msi: Installs the RHV Plug-in
•
services.
RHVPluginPr
oxy.msi RHVPluginProxy.msi: Installs the RHV Plug-
in proxy VM image files.
•
RHVPluginUI. RHVPluginUI.msi: Installs UI components of
msi the RHV Plug-in.

ACCEPT_EULA 0/1 Yes Specifies if you want to accept the Veeam


license agreement. Specify 1 to accept the
license agreement and proceed with installation.

Example: ACCEPT_EULA="1"

ACCEPT_THIRDPARTY_L 0/1 Yes Specifies if you want to accept the license


ICE NSES agreement for 3rd party components that
Veeam incorporates. Specify 1 to accept the
license agreement and proceed with installation.

Example:
ACCEPT_THIRDPARTY_LICENSES="1"

INSTALLDIR path No Installs the component to the specified location.


By default, Veeam Backup & Replication uses the
Backup subfolder of the C:\Program
Files\Veeam\Backup and Replication\
folder.

Example: INSTALLDIR="C:\Backup\"
The component will be installed to the
C:\Backup\Backup folder.

420 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Examples
Installing RHV Plug-in Service and UI
To install the RHV Plug-in service and UI components to Veeam Backup & Replication, perform the following
steps:

1. Run the following command to install the RHV Plug-in service.

msiexec /qn /i RHVPlugin.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

2. Run the following command to install the RHV Plug-in proxy VM image files.

msiexec /qn /i RHVPluginProxy.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA


=1

3. Run the following command to install UI components of RHV Plug -in.

msiexec /qn /i RHVPluginUI.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1

Veeam Plug-in for Kasten K10


You can install the Kasten K10 Plug-in for Veeam Backup & Replication in the unattended mode. Note that if you
want to manage Kasten K10 Plug-in for Veeam Backup & Replication in the Veeam Backup & Replication
interface, you must install both the plug-in service and the plug-in UI.

To install Kasten K10 Plug-in for Veeam Backup & Replication, use a command with the following syntax:

msiexec /qn /i <msi> ACCEPT_EULA=1, ACCEPT_THIRDPARTY_LICENSES=1

The command has the following parameters:

Op tion P a rameter Require Description


d

/q n Yes Sets the user interface level to


“no”, which means no user
interaction is needed during
installation.

/i setup file Yes Installs the


Veeam Backup & Replication
server. Specify a full path to the
setup file as the parameter value.

Example: /i
C:\Veeam\Server.x64.msi

421 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Op tion P a rameter Require Description
d

• VeeamKastenPlugin.msi
msi Yes VeeamKastenPlugin.msi:
•
Installs the Kasten K10 Plug-in
VeeamKastenPluginUI. for Veeam Backup & Replication
msi services.

VeeamKastenPluginUI.msi:
Installs UI components of Kasten
K10 Plug-in for Veeam Backup &
Replication.

ACCEPT_EULA 0/1 Yes Specifies if you want to accept


the Veeam license agreement.
Specify 1 to accept the license
agreement and proceed with
installation.

Example: ACCEPT_EULA=1

ACCEPT_THIRDPARTY_LICEN 0/1 Yes Specifies if you want to accept


SE S the license agreement for 3rd
party components that Veeam
incorporates. Specify 1 to accept
the license agreement and
proceed with installation.

Example:
ACCEPT_THIRDPARTY_LICENS
ES=1

Examples
Installing Kasten K10 Plug-in for Veeam Backup & Replication Service and UI
To install the Kasten K10 Plug-in for Veeam Backup & Replication service and UI components to
Veeam Backup & Replication, perform the following steps:

1. Run the following command to install the Kasten K10 Plug-in for Veeam Backup & Replication service.

msiexec /qn /i VeeamKastenPlugin.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_E


ULA=1

2. Run the following command to install UI components of Kasten K10 Plug -in for Veeam Backup &
Replication.

msiexec /qn /i VeeamKastenPluginUI.msi ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT


_EULA=1

422 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Veeam Backup & Replication in Silent
Mode
You can upgrade Veeam Backup & Replication in the unattended mode with a special XML answer file by using
the command line interface. The answer file contains all the necessary upgrade settings in the proper order and
their thorough description.

Before You Begin


Before starting the upgrade of Veeam Backup & Replication in the unattended mode with the answer file,
consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended upgrade is logged on the machine using the
network logon method, the unattended upgrade will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
upgrade is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out unused [Optional] parameters. Otherwise,
the upgrade session will fail.

Upgrading Veeam Backup & Replication


To upgrade Veeam Backup & Replication in the silent mode with the answer file, take the following steps:

1. Copy the VbrAnswerFile_upgrade.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBR folder. This folder contains the following templates of answer files
used for installing, uninstalling, and upgrading Veeam Backup & Replication:

o VbrAnswerFile_install.xml — for installing Veeam Backup & Replication;

o VbrAnswerFile_uninstall.xml — for uninstalling Veeam Backup & Replication;

o VbrAnswerFile_upgrade.xml — for upgrading Veeam Backup & Replication.

2. Configure upgrade parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (Vbr) and mode (upgrade) specified in line 2:

<unattendedInstallationConfiguration bundle="Vbr" mode="upgrade" version="


1.0">

3. After you make all the necessary changes in your answer file, start the upgrade by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your installation command:

423 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileVBRUpg
rade.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileVBRUpgrade.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-upgrade validations


that do not work under the network logon, which will block the silent upgrade from running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains the following parameters:

P a rameter Required? Default Description

ACCEPT_EULA Yes Specify 1 to accept the Veeam license


agreement.

ACCEPT_LICENSING_POLICY Yes Specify 1 to accept the Veeam licensing policy.

ACCEPT_THIRDPARTY_LICENSES Yes Specify 1 to accept the license agreement for


3rd party components that Veeam
incorporates.

ACCEPT_REQUIRED_SOFTWARE Yes Specify 1 to accept all required software


license agreements.

VBR_LICENSE_FILE No Path to the license file on the machine where


you want to install
Veeam Backup & Replication. If you do not
specify this parameter (or leave it empty
value), Veeam Backup & Replication will be
installed using the current license file. To
install the Community Edition, set the
parameter to to 0.

VBR_LICENSE_AUTOUPDATE No 1 Specify 1 to enable automatic license update


and usage reporting. Specify 0 if you want to
update the license manually. For Community
Edition, NFR and Evaluation licenses, specify 1.
For licenses without ID information, specify 0.

424 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Required? Default Description

VBR_SERVICE_PASSWORD No Password for the account under which the


Veeam Backup Service will run.

VBR_SQLSERVER_PASSWORD No Password to connect to the SQL Server in the


SQL Server authentication mode.

VBR_AUTO_UPGRADE No 0 Specify 1 to automatically upgrade existing


components in the backup infrastructure.
Specify 0 if you do not want
Veeam Backup & Replication to upgrade the
existing components automatically.

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to reboot the machine


where you install Veeam Backup & Replication
after the installation finishes. Specify 0 if you
do not want to reboot the machine.

Note that you must specify "1" in ACCEPT_EULA, ACCEPT_LICENSING_POLICY, ACCEPT_THIRDPARTY_LICENSES


and ACCEPT_REQUIRED_SOFTWARE parameters to proceed with the upgrade.

Upgrade Result Codes


The upgrade result is written into the upgrade log file located at your selected log folder. It may show one of
the following result codes:

Result Result
Cod e

0 success

1603 install failure

3010 reboot required

3011 logoff required

425 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrade Error Codes
The upgrade error codes accompanied by their detailed description are displayed in the command line dialog.
They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the log folder
(by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving upgrade
results from the scripts or utilities that are used to run the upgrade. The error message may show one of the
following error codes:

E rror Description
Cod e

0 Installation has been completed successfully.

1 Product is already installed.

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

12 Reboot is required to finalize prerequisites installation.

13 Reboot is required to finalize the product installation.

14 Logoff is required to finalize the product installation.

101 Failed to start the installer.

102 Invalid answer file provided.

103 Invalid launch conditions.

104 Failed to initialize setup properties.

105 Failed to validate setup properties.

106 System configuration check detected some issues.

107 Failed to install prerequisites.

108 Failed to install a database server.

109 Failed to install the product.

426 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E rror Description
Cod e

110 Failed to update the product.

111 Failed to change a service status.

112 Failed to uninstall the product.

113 Unexpected error occurred.

427 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Veeam Backup & Replication Console
in Silent Mode
You can upgrade the Veeam Backup & Replication console in the unattended mode with a special XML answer
file by using the command line interface. The answer file contains all the necessary upgrade settings in the
proper order and their thorough description.

Before You Begin


Before starting the upgrade of the Veeam Backup & Replication console in the unattended mode with the
answer file, consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended upgrade is logged on the machine using the
network logon method, the unattended upgrade will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
upgrade is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out unused [Optional] parameters. Otherwise,
the upgrade session will fail.

Upgrading Veeam Backup & Replication Console


To upgrade the Veeam Backup & Replication console in the silent mode with the answer file, take the following
steps:

1. Copy the VbrConsoleAnswerFile_upgrade.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBRConsole folder. This folder contains the following templates of
answer files used for installing, uninstalling, and upgrading the Veeam Backup & Replication console:

o VbrConsoleAnswerFile_install.xml — for installing the Veeam Backup & Replication console;

o VbrConsoleAnswerFile_uninstall.xml — for uninstalling the Veeam Backup & Replication


console;

o VbrConsoleAnswerFile_upgrade.xml — for upgrading the Veeam Backup & Replication console.

2. Configure upgrade parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (VbrConsole) and mode (upgrade) specified in line 2:

<unattendedInstallationConfiguration bundle="VbrConsole" mode="upgrade" ve


rsion="1.0">

3. After you make all the necessary changes in your answer file, start the upgrade by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your upgrade command:

428 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileConsol
eUpgrade.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileConsoleUpgrade.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-upgraded


validations that do not work under the network logon, which will block the silent upgrade from
running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains the following parameters:

P a rameter Required? Default Description

ACCEPT_EULA Yes Specify 1 to accept the Veeam license


agreement.

ACCEPT_LICENSING_POLICY Yes Specify 1 to accept the Veeam licensing policy.

ACCEPT_THIRDPARTY_LICENSES Yes Specify 1 to accept the license agreement for


3rd party components that Veeam
incorporates.

ACCEPT_REQUIRED_SOFTWARE Yes Specify 1 to accept all required software


license agreements.

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to reboot the machine


where you upgrade the
Veeam Backup & Replication console after the
upgrade finishes. Specify 0 if you do not want
to reboot the machine.

Note that you must specify "1" in ACCEPT_EULA, ACCEPT_LICENSING_POLICY, ACCEPT_THIRDPARTY_LICENSES


and ACCEPT_REQUIRED_SOFTWARE parameters to proceed with the installation.

429 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrade Result Codes
The upgrade result is written into the installation log file located at your selected log folder. It may show one of
the following result codes:

Result Result
Cod e

0 success

1603 install failure

3010 reboot required

3011 logoff required

Upgrade Error Codes


The upgrade error codes accompanied by their detailed description are displayed in the command line dialog.
They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the log folder
(by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving upgrade
results from the scripts or utilities that are used to run the upgrade. The error message may show one of the
following error codes:

E rror Description
Cod e

0 Installation has been completed successfully.

1 Product is already installed.

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

12 Reboot is required to finalize prerequisites installation.

13 Reboot is required to finalize the product installation.

14 Logoff is required to finalize the product installation.

101 Failed to start the installer.

430 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E rror Description
Cod e

102 Invalid answer file provided.

103 Invalid launch conditions.

104 Failed to initialize setup properties.

105 Failed to validate setup properties.

106 System configuration check detected some issues.

107 Failed to install prerequisites.

108 Failed to install a database server.

109 Failed to install the product.

110 Failed to update the product.

111 Failed to change a service status.

112 Failed to uninstall the product.

113 Unexpected error occurred.

431 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating Veeam Backup & Replication in Silent
Mode
Veeam Backup & Replication updates can be installed in the silent mode.

To install a Veeam Backup & Replication update, perform the following steps:

1. Download the update installation archive and extract the executable file.

2. Install the update on the backup server.

IMP ORTANT!

The script that installs Veeam Backup & Replication updates must be run with elevated privileges (run as
Administrator).

Step 1. Download and Extract Executable File


Download and extract the executable file for update installation:

1. Download the installation archive for the Veeam Backup & Replication update from the Release Notes
page for a certain update/patch. For example, for v12 updates, download the latest patch from this Veeam
KB article.

2. Extract the executable file from the downloaded archive.

3. Save the extracted file locally on the backup server where you plan to install the update, or place it in a
network shared folder.

Alternatively, you can get the update/patch executable file from the Up dates folder on the downloaded ISO
image.

Step 2. Install Update


To install the Veeam Backup & Replication update on the backup server, use the following command syntax:

%patch% [/silent][/noreboot][/log <log_path>][VBR_AUTO_UPGRADE="1"]

The command has the following parameters:

P a ramet Require
Op tion Description
er d

Specifies a path to the update installation file on the backup


server or in a network shared folder.
%p a tch% path Yes
Example:
C:\Temp\VeeamBackup&Replication_11.0.1.1261_2022
0302.exe

432 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a ramet Require
Op tion Description
er d

silent — Yes Sets the user interface level to “no”, which means no user
interaction is needed during installation.

Suppresses reboot if reboot is required during the


noreboot — No
Veeam Backup & Replication update installation.

Specifies a full path to the log file for the


Veeam Backup & Replication update installation.
log path No
Example: C:\Logs\veeam.log

Specifies if you want Veeam Backup & Replication to


automatically upgrade existing components in the backup
infrastructure. Veeam Backup & Replication performs automatic
VBR_AUTO_UPGRA upgrade after the Veeam Backup Service is started on the backup
0/1 No server.
DE
Specify 1 to enable automatic upgrade.

Example: VBR_AUTO_UPGRADE="1"

For example:

You want to install the Veeam Backup & Replication update with the following options:

• Path to the update installation file:


C:\Temp\VeeamBackup&Replication_12.0.0.1420_20230223.exe

• Silent install: enabled

• Noreboot: enabled

• Path to the log file: C:\Logs\veeam.log

• Components auto upgrade: enabled

The command to install the Veeam Backup & Replication update will be the following:

C:\Temp\VeeamBackup&Replication_12.0.0.1420_20230223.exe /silent /noreboot /log C


:\Logs\veeam.log VBR_AUTO_UPGRADE="1"

Installation Results
You can use the last exit code to verify if the installation process has completed successfully.

• In cmd.exe, use the %ERRORLEVEL% variable to check the last exit code.

• In Microsoft Windows PowerShell, use the $LastExitCode variable to check the last exit code.

433 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication does not provide any confirmation about the results of automatic components
upgrade. To check if components have been successfully upgraded, use the Veeam Backup & Replication
console.

434 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Uninstalling Veeam Backup & Replication in
Silent Mode
You can uninstall Veeam Backup & Replication in the unattended mode with a special XML answer file by using
the command line interface. The answer file contains all the necessary uninstallation settings in the proper order
and their thorough description.

Before You Begin


Before starting the uninstallation of Veeam Backup & Replication in the silent mode with the answer file,
consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended uninstallation is logged on the machine using the
network logon method, the unattended uninstallation will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
uninstallation is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out the unused [Optional] parameter.
Otherwise, the uninstallation session will fail.

Uninstalling Veeam Backup & Replication


To uninstall Veeam Backup & Replication in the silent mode with the answer file, take the following steps:

1. Copy the VbrAnswerFile_uninstall.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBR folder. This folder contains the following templates of answer files
used for installing, uninstalling, and upgrading Veeam Backup & Replication:

o VbrAnswerFile_install.xml — for installing Veeam Backup & Replication;

o VbrAnswerFile_uninstall.xml — for uninstalling Veeam Backup & Replication;

o VbrAnswerFile_upgrade.xml — for upgrading Veeam Backup & Replication.

2. Configure uninstallation parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (Vbr) and mode (uninstall) specified in line 2:

<unattendedInstallationConfiguration bundle="Vbr" mode="uninstall" version


="1.0">

3. After you make all the necessary changes in your answer file, start the uninstallation by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your uninstallation command:

435 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileVBRUni
nstall.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileVBRUninstall.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-uninstallation


validations that do not work under the network logon, which will block the silent uninstallation from
running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains only the following parameter:

P a rameter Required? Default Description

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to reboot the machine where


you uninstall Veeam Backup & Replication after the
uninstallation finishes. Specify 0 if you do not want
to reboot the machine.

Uninstallation Result Codes


The uninstallation result is written into the uninstallation log file located at your selected log folder. It may
show one of the following result codes:

Result Result
Cod e

0 success

1603 install failure

3010 reboot required

3011 logoff required

436 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Uninstallation Error Codes
The uninstallation error codes accompanied by their detailed description are displayed in the command line
dialog. They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the
log folder (by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving
uninstallation results from the scripts or utilities that are used to run the uninstallation. The error message may
show one of the following error codes:

E rror Description
Cod e

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

101 Failed to start the installer.

102 Invalid answer file provided.

103 Invalid launch conditions.

112 Failed to uninstall the product.

113 Unexpected error occurred.

437 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Uninstalling Veeam Backup & Replication
Console in Silent Mode
You can uninstall the Veeam Backup & Replication console in the unattended mode with a special XML answer
file by using the command line interface. The answer file contains all the necessary uninstallation settings in the
proper order and their thorough description.

Before You Begin


Before starting the uninstallation of the Veeam Backup & Replication console in the silent mode with the answer
file, consider the following:

• The user account that you use to run the silent installation must be in the local Administrators group on
the machine where the silent installation will run. The silent installation cannot be run under the
LocalSystem and NetworkService accounts.

• If the user account that you use to run the unattended uninstallation is logged on the machine using the
network logon method, the unattended uninstallation will fail. To avoid this, use an additional
/SkipNetworkLogonErrors command line key. For example, it is required when the unattended
uninstallation is started via a remote PowerShell session.

• When configuring the answer file, remove or comment out the unused [Optional] parameter.
Otherwise, the uninstallation session will fail.

Uninstalling Veeam Backup & Replication Console


To uninstall the Veeam Backup & Replication console in the silent mode with the answer file, take the following
steps:

1. Copy the VbrAnswerFile_uninstall.xml file to your local drive.

You can find the template answer file on the Veeam Backup & Replication installation disk in the
\Setup\Silent\AnswerFiles\VBRConsole folder. This folder contains the following templates of
answer files used for installing, uninstalling, and upgrading Veeam Backup & Replication:

o VbrConsoleAnswerFile_install.xml — for installing the Veeam Backup & Replication console;

o VbrConsoleAnswerFile_uninstall.xml — for uninstalling the Veeam Backup & Replication


console;

o VbrConsoleAnswerFile_upgrade.xml — for upgrading the Veeam Backup & Replication console.

2. Configure uninstallation parameters according to your needs. For details, see Configuration Parameters.

Check that the answer file has the correct bundle (VbrConsole) and mode (uninstall) specified in line
2:

<unattendedInstallationConfiguration bundle="VbrConsole" mode="uninstall"


version="1.0">

3. After you make all the necessary changes in your answer file, start the uninstallation by running the
Veeam.Silent.Install.exe file located on the Veeam Backup & Replication installation disk in the
\Setup\Silent folder. Use the following command line keys in your uninstallation command:

438 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
D:\Setup\Silent\Veeam.Silent.Install.exe /AnswerFile E:\MyAnswerFileConsol
eUninstall.xml /SkipNetworkLogonErrors

where:

o /AnswerFile — required key for specifying the path to your custom answer file, for example:
E:\MyAnswerFileConsoleUninstall.xml.

o /SkipNetworkLogonErrors — optional key that allows skipping additional pre-uninstallation


validations that do not work under the network logon, which will block the silent uninstall ation from
running.

o /LogFolder — optional key for specifying the path where the setup should save log files if it is
different from the default path. The default path is: C:\ProgramData\Veeam\Setup\Temp.

Configuration Parameters
The configuration file contains only the following parameter:

P a rameter Required? Default Description

RE BOOT_IF_REQUIRED No 0 Specify 1 if you want to reboot the machine where


you uninstall the Veeam Backup & Replication
console after the uninstallation finishes. Specify 0 if
you do not want to reboot the machine.

Uninstallation Result Codes


The uninstallation result is written into the uninstallation log file located at your selected log folder. It may
show one of the following result codes:

Result Result
Cod e

0 success

1603 install failure

3010 reboot required

3011 logoff required

439 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Uninstallation Error Codes
The uninstallation error codes accompanied by their detailed description are displayed in the command line
dialog. They can also be found in the UnattendedInstallationResult_%DATE%_%TIME%.xml file in the
log folder (by default, C:\ProgramData\Veeam\Setup\Temp). You can use such an XML file for retrieving
uninstallation results from the scripts or utilities that are used to run the uninstallation. The error message may
show one of the following error codes:

E rror Description
Cod e

2 Uninstallation has been completed successfully.

11 Unable to start the setup program, because machine's reboot is pending.

101 Failed to start the installer.

102 Invalid answer file provided.

103 Invalid launch conditions.

112 Failed to uninstall the product.

113 Unexpected error occurred.

440 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Getting Started with
Veeam Backup & Replication
This section describes Veeam Backup & Replication UI and basic concepts.

441 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Logging in to Veeam Backup & Replication
To log in to Veeam Backup & Replication, you must open the Veeam Backup & Replication console and specify
connection settings to access the backup server.

1. To open the Veeam Backup & Replication console, do one of the following:

o Double-click the console icon on the desktop.

o From the Microsoft Windows Sta rt menu, select All P rograms > Veeam > Veeam Backup & Replication
Console.

o Use the Microsoft Windows search to find the Veea m Backup & Replication Console program on the
computer.

2. In the Server field, type the name or IP address of the backup server or select it from the list of recent
connections. By default, the console connects to the backup server installed locally — localhost.

3. In the P ort field, enter the port over which you want to connect to the backup server. The port number is
set at the P ort Configuration step of the setup wizard for Veeam Backup & Replication. By default, port
9392 is used.

4. In the Username and Password fields, enter credentials of the user account that you want to use to
connect to the backup server. The user account must be added to the Local Users group on the backup
server or a group of domain users who have access to the backup server.

You can also select the Use Windows session authentication check box. In this case, you will log in to
Veeam Backup & Replication using the account under which you are currently logged in to Microsoft
Windows.

5. Click Connect.

If multi-factor authentication (MFA) is enabled, after user clicks Connect, they will get the instruction how
to set up MFA or have to enter a 6-digit confirmation code generated in the mobile authenticator
application. For more information, see Multi-Factor Authentication.

To create a shortcut for the connection, click Sa ve shortcut. You can create as many shortcuts as you need.

NOTE

If you create a shortcut for a connection, the credentials for this connection will be stored in the Windows
Credentials Manager. The credentials are saved after the first successful login.

442 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication UI
The user interface of Veeam Backup & Replication is designed to let you quickly find commands that you need
and perform data protection and disaster recovery tasks.

• Main Menu

• Navigation Pane

• Ribbon and Tabs

• Views

• Working Area

• Job Filter

• Footer

• Changing Color Theme

• Restore Points Icons

• Hypervisor Infrastructure Icons

TIP

To open online help, press [F1] in any Veeam Backup & Replication wizard or window. You will be
redirected to the required section of the user guide.

443 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Main Menu
The main menu in Veeam Backup & Replication contains commands related to general application settings. You
can perform the following operations using the main menu:

• Upgrade backup infrastructure components.

• Manage credentials.

• Manage cloud credentials.

• Manage passwords.

• Configure application settings.

• Set up user roles.

• Configure malware detection settings.

• Exclude VMs globally.

• Configure network traffic rules.

• Perform configuration backup and restore.

• Start PuTTy and Microsoft PowerShell consoles, and open a remote desktop connection to the backup
server.

• Change the color theme.

• Work with licenses.

• View Veeam Backup & Replication help and export program logs.

• Exit Veeam Backup & Replication.

444 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Navigation Pane
The navigation pane, located on the left of the window, provides centralized navigation and lets you easily
access Veeam Backup & Replication items organized in views.

The navigation pane consists of two areas:

• The upper pane, or the inventory pane, displays a hierarchy or list of items relevant for a specific view.

Items displayed in the inventory pane differ depending on the active view. For example, in the Ba ckup
Infrastructure view, the inventory pane displays a list of backup infrastructure components —
virtualization servers, backup proxies, backup repositories and so on. In the Inventory view, the inventory
pane displays a list of servers added to the backup infrastructure.

• The lower pane contains a set of buttons that let you switch between views. For more information on
views and how to show/hide a view button, see Views.

445 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ribbon and Tabs
Operation commands in Veeam Backup & Replication are organized in logical groups and displayed under tabs
on the ribbon. The ribbon is displayed at the top of the main application window.

On the ribbon, the following tabs are displayed:

• The Home tab provides quick access to the most common operations. It lets you configure different types
of jobs, perform restore and import operations. This tab is always available, no matter which view is
currently active.

• Other tabs contain commands specific for certain items and appear when these items are selected. For
example, if you open the Home view and select a backup job in the working area, the Job tab containing
buttons for operations with jobs will appear on the ribbon. If you open the Files view and select a file or
folder, the File Tools tab containing buttons for operations with files will appear on the ribbon.

TIP

Commands for operations with items in Veeam Backup & Replication are also available from the shortcut
menu.

You can minimize the ribbon. To do that, right-click the area with buttons on the ribbon and select Minimize the
Rib bon. To restore the ribbon, right-click on the minimized ribbon and clear the Minimize the Ribbon option.

446 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Views
Veeam Backup & Replication displays its items in views. When you click the button of a specific view in the
navigation pane, the view content is displayed in the working area of Veeam Backup & Replication.

Veeam Backup & Replication offers the following views:

• The Home view is intended for work with jobs. It also displays a list of created backups and replicas that
can be used for various restore operations, and provides statistics for recently performed jobs. For more
information about job statistics, see Reporting.

• The Inventory view displays the inventory of the virtual infrastructure. The inventory can be presented
from different perspectives: Computer, Storage, VM Folders, VM Tags and vCloud. You can use this view
to work with VMs, and VM containers or groups.

• The Ba ckup Infrastructure view displays a list of backup infrastructure components: servers, hosts, backup
proxies, backup repositories and so on. You can use this view for backup infrastructure setup — here you
can configure backup infrastructure components that will be used for data protection and disaster
recovery tasks.

• The Ta p e Infrastructure view displays a hierarchy of tape libraries connected to the tape server. You can
use this view to archive data to tapes and restore data from tapes.

• The Cloud Connect Infrastructure view displays components of the Veeam Cloud Connect infrastructure.
This view can be used by SP to manage TLS certificates, configure cloud gateways and create accounts for
users who plan to work with cloud resources.

• The Files view displays a file tree of servers added to the backup infrastructure. You can use this view for
file copying operations.

• [For Veeam Backup & Replication 12.1 (build 12.1.0.2131) and later] The Ana lytics view displays the
following dashboards configured in Veeam ONE for monitoring the backup infrastructure and data
protection operations in the virtual environment: Veeam Threat Center, Veeam Backup & Replication
Overview, and Backup Heatmap. Dashboards in the view are available if you have Veeam ONE integrated
with your Veeam Backup & Replication installation.

• The History view displays statistics on operations performed with Veeam Backup & Replication.

In some situations, some views may not be displayed. Consider the following:

• Right after installation, Veeam Backup & Replication displays only Ba ck up Infrastructure and History
views. To display other views, you must add at least one server or virtualization host to the backup
infrastructure.

• Right after installation, Veeam Backup & Replication does not save changes that you make to the
navigation pane or views: for example, if you resize panes, display or hide specific views. After you restart
the Veeam Backup & Replication console, the main window settings are back to default ones. To save
these settings, you must add at least one server or virtualization host to the backup infrastructure.

• Views can be shown as icons if they do not fit into the pane. To show the views in the full size, drag and
drop the upper border of the pane.

• To display the Cloud Connect Infrastructure view, you must install a valid license that supports the Veeam
Cloud Connect functionality.

• The Ana lytics view is available if you have the Microsoft Edge WebView2 Runtime component installed.
The component is not installed for Microsoft Windows Server 2012 and 2012 R2 due to the version
incompatibility, so the Ana lytics view is not available for the backup server running theses Microsoft
Windows versions.

447 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can hide views that you do not plan to use. For example, if you do not use tapes for data archiving, you can
hide the Ta p e Infrastructure view.

To hide a view:

1. Click the arrow icon ( ) at the bottom of the navigation pane.

2. Click the view in the list.

448 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Working Area
The working area of Veeam Backup & Replication displays a list of items relating to a specific view.

The working area looks different depending on the view that is currently active. For example, if you open the
History view, the working area will display a list of job sessions and restore tasks performed with
Veeam Backup & Replication. If you open the Inventory view, the working area will display a list of VMs that
reside on servers connected to Veeam Backup & Replication.

Every item is described with a set of properties that are presented as column headers. You can click column
headers to sort items by a specific property. For example, to sort VMs by the amount of provisioned storage
space, click the P rovisioned Size header.

To hide or display properties, right-click a column header and, in the opened menu, clear or select check boxes
near property names.

449 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Job Filter
A job filter allows you to filter jobs by different parameters. For example, you can create a filter that will show
only VM backup copy jobs.

Creating Job Filters


To create a filter, do the following:

1. Open the Home view.

2. In the inventory pane, select the Job s node. At the top of the working area, click the filter icon ant then
Ad d new. Alternatively, right-click the Job s node and select Ad d view.

3. In the Ad d View window, specify a filter name. The name must be up to 200 characters long.

4. If you want to show this filter as a subnode of the Job s node in the inventory pane, select the Ad d this
view to the job management tree check box.

5. In the W orkload section, select workloads which jobs must process:

o Ap p lication — Veeam Backup & Replication will show Veeam Plug-in jobs and jobs in which SQL
transaction log backup, Oracle archive log backup or PostreSQL WAL files back up is enabled.

o Cloud VM — Veeam Backup & Replication will show jobs that process VMs stored in clouds.

o File — Veeam Backup & Replication will show jobs that process files.

o Server — Veeam Backup & Replication will show Veeam Agent jobs that process servers. For more
information on processed computer types, see Selecting Protected Computer Type.

o W orkstation — Veeam Backup & Replication will show Veeam Agent jobs that process workstations.
For more information on processed computer types, see Selecting Protected Computer Type.

o VM — Veeam Backup & Replication will show jobs that process VMs.

6. In the Job type section, select job types:

o Ba ckup — backup jobs. For example, VM backup jobs or file backup jobs.

o Ba ckup copy — backup copy jobs. For example, VM backup copy jobs or file backup copy jobs.

o Cop y — copy jobs. For example, file copy jobs.

o Rep lication — replication jobs.

o SureBackup — SureBackup jobs.

o Ta p e — tape jobs. For example, backup to tape jobs or file to tape jobs. For more information, see the
Creating Backup to Tape Jobs and Creating File to Tape Jobs sections in the
Veeam Backup & Replication User Guide.

7. In the La st result section, select statuses with which jobs must finish: Success, Warning or Failed .

Jobs that that have never started are considered as Failed .

8. In the Sta tus section, select states of jobs: Running , Inactive or Disabled .

Backup copy jobs in the Idle state are considered Inactive.

450 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
9. If you want to show jobs with manually set Hig h priority flag, select the Hig h priority job check box. For
more information on job priorities, see Job Priorities.

10. If you want to show jobs that were inactive for some period of time, select the La st run is over N days ago
check box and specify the period in days.

11. If you want to show jobs whose names include specific keywords, select the Job name includes check box
and enter keywords.

To show jobs that include any of the specified keywords, separate these keywords by a semicolon without
a space. For example, if you enter "Backup Job;Daily" , Veeam Backup & Replication will show all jobs that
include "Backup Job" or "Daily" keywords in their names.

NOTE

Only the user who creates filters can access them — that is, other users cannot use these filters.

Editing and Deleting Job Filters


To edit or delete a job filter, do the following:

1. Open the Home view.

2. In the inventory pane, select the Job s node.

3. At the top of the working area, click the filter icon .

4. Hover the mouse over a filter that you want to edit or delete.

5. Click the ellipsis button.

6. Select E d it view or Delete view.

451 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If you have added the filter as a subnode of the Job s node in the inventory pane, you can right-click the subnode
and then click E d it view or Delete view.

452 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Footer
The footer contains the following information, starting from left to right:

• The number of items you selected for further actions or the total number of items in the working area if no
items are selected.

• The backup server which this Veeam Backup & Replication console is connected to. By default, the console
connects to the backup server installed locally — localhost.

• The backup server build number.

TIP

You can also check this installation build number in Ma in Menu > Help > Ab out. Our build numbers
follow a dotted x.x.x.x system appended with a cumulative patch number in the format
PYYYYMMDD. For more information on how to update your installation of
Veeam Backup & Replication to the latest version, see Updating Veeam Backup & Replication 12.

• The information about your license edition and its expiration date.

453 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Changing Color Theme
By default, Veeam Backup & Replication uses a ‘Veeam Green’ color theme for the UI. If necessary, you can
change the color theme. Changing the color theme can be helpful, for example, if you connect to different
backup servers from one remote machine on which the Veeam Backup & Replication console is installed. In this
case, you will be able to easily differentiate with which backup server you are currently working.

To change the color theme for Veeam Backup & Replication:

1. From the main menu, select Color Theme.

2. Choose one of color themes: Grass Green, Veeam Green, Marine Blue, Ocean Graphite.

NOTE

Color theme settings are applicable for a specific combination of a backup server and user account. For
example, the color theme is initially set to the default one. You log on to the Veeam Backup & Replication
console under some user account and change the color theme to Ma rine Blue . If you log on to the same
backup server under the same account next time, the color theme will be set to Ma rine Blue. If you log on
to the same backup server under another account, Veeam Backup & Replication will use the color theme
that was previously set for this account — that is, the default color theme.

454 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore Points Icons
Restore points icons display the information about a current state of a restore point. There are 2 types of icons,
for backup repository restore points and for scale-out backup repository restore points.

Backup Repository Restore Points


The following user interface icons indicate the states of the restore points in all backups.

Icon Sta te

Full restore point

Incremental restore point

Reverse incremental restore point

Missing full restore point

Missing incremental restore point

Missing reverse incremental restore point

Scale-Out Backup Repository Restore Points


The following user interface icons indicate the states of the restore points in the scale-out backup repository.

Icon Sta te

Full restore point; on performance tier only

Full restore point; on performance tier and offloaded to capacity tier

Full restore point; on capacity tier only

Full restore point; on capacity tier and partially downloaded to performance tier

(This can happen when download to the performance tier fails)

Incremental restore point; on performance tier only

Incremental restore point; on performance tier and offloaded to capacity tier

455 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Icon Sta te

Incremental restore point; on capacity tier only

Incremental restore point; on capacity tier and partially downloaded to performance tier

(This can happen when download to the performance tier fails)

Rollback restore point; on performance tier only

Rollback restore point; on performance tier and offloaded to capacity tier

Rollback restore point; on capacity tier only

Rollback restore point; on capacity tier and partially downloaded to performance tier

(This can happen when download to the performance tier fails)

Rollback restore point; on archive tier only

456 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Hypervisor Infrastructure Icons
Hyper-V Icons
These user interface icons represent the hypervisor objects of Hyper-V workloads and servers, added to the
backup infrastructure.

Icon Description

Cluster

Host

Host with no license

(This can happen when you have Per-Socket licensing)

SCVMM

VM

VM in the paused state

VM in the running state

Saved VM

Off-host backup proxy

Tape server

457 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication Services
Veeam Backup & Replication uses the following services:

• Veeam Backup Service is a Windows service that coordinates all operations performed by
Veeam Backup & Replication such as backup, replication, recovery verification and restore tasks. The
Veeam Backup Service runs under the LocalSystem account or account that has the local Administrator
permissions on the backup server.

• Veeam Installer Service installs, updates or removes Veeam services when you add, update or remove
backup infrastructure components. For more details, see Veeam Installer Service.

• Veeam Guest Catalog Service manages guest OS file system indexing for VMs and replicates system index
data files to enable search through guest OS files. Index data is stored in the Veeam Backup Catalog — a
folder on the backup server. The Veeam Guest Catalog Service running on the backup server works in
conjunction with search components installed on Veeam Backup Enterprise Manager and (optionally) a
dedicated Microsoft Search Server.

• Mount Service mounts backups and replicas for file-level access, browsing the VM guest file system and
restoring VM guest OS files and application items to the original location.

458 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Installer Service
The Veeam Installer Service is a Windows or Linux service that manages Veeam components and services in the
following cases:

• When you add, update or remove a physical or virtual machine as a managed server in the
Veeam Backup & Replication console. Depending on the role selected for the server, the Veeam Installer
Service service deploys, updates, and removes required services such as the Veeam Data M over Service,
the Veeam Mount Service, and so on.

For hardened repository, the Veeam Installer Service deploys the Veeam Data Mover Service and Veeam
Immutability Service. For more information, see How Immutability Works.

• When you discover protected machines or perform guest processing tasks for them. The Veeam Installer
Service service deploys, updates, and removes persistent agent components for guest processing tasks.

By default, the service uses port 6160. For more information, see Ports.

NOTE

The Veeam Installer Service also manages public keys of self-signed TLS certificates generated by
Veeam Backup & Replication. These keys are used during deployment and update of the components and
services to verify installation packages and prevent managed servers and protected machines from being
compromised. When Veeam Backup & Replication sends request to update components and services, the
Veeam Installer Service validates the public certificate, the checksum and the digital signature of the
installation package.

Veeam Installer Service for Windows


The service can be installed in one of the following ways:

• Automatic installation by Veeam Backup & Replication when you add a Microsoft Windows machine as a
managed server in the Veeam Backup & Replication console.

• Manual installation by running the VeeamInstallerSvc.msi file located at C:\Program


Files\Veeam\Backup and Replication\Backup\Packages. You can also manually preinstall the
required components located in the same folder for future use. Or you can let the Veeam Installer Service
install the components automatically during the first run of the backup job with enabled guest processing
of this VM by persistent agents. For more information, see Persistent Agent Components.

• Automatic installation by using a logon script.

• Automatic installation using domain group policies.

• Installation by using the standard third-party software distribution tool.

Veeam Installer Service for Linux


The service is installed in the following situations:

• Automatic installation by Veeam Backup & Replication when you add a Linux machine as a managed server
in the Veeam Backup & Replication console.

• Automatic installation by Veeam Backup & Replication when you create a protection group with Linux
machines. For more information, see Protection Groups in the Veeam Agent Management Guide.

459 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• When you manually install persistent agents components on Linux machines. For more information, see
Installing Persistent Agent Components on Linux VMs.

To deploy the Veeam Installer Service on Linux machines, Veeam Backup & Replication uses the SSH connection.
After deployment, the Veeam Installer Service will communicate with backup infrastructure components and
get updates from the backup server without the SSH connection.

460 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam AI Online Assistant
Veeam AI Online Assistant is a chatbot that helps with common issues and questions related to Veeam products.
It is trained on Veeam technical documentation to provide accurate answers. You can communicate with Veeam
chatbot in any language you want and create both simple and complex inquiries.

NOTE

Veeam AI Online Assistant feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131) and later.

IMP ORTANT

Consider the following:

• You must have a paid license and support contract to use Veeam AI Online Assistant. If you have a
Community (free) Edition, NFR or Evaluation license, AI Online Assistant will not be available.
• Only currently installed license is used for authentication. If the license is changed, you must clos e
the chatbot window and open it again.
• We do not recommend to share any confidential information when using Veeam AI Online Assistant
as the queries are sent outside your organization. Veeam takes no responsibility for the accuracy of
the information that chatbot provides.

Limitations of Veeam AI Online Assistant


Veeam AI Online Assistant has the following limitations:

• There is a limit of up to 30 questions per 24 hours for each license. If this limit is reached, Veeam AI Online
Assistant will stop processing further questions. You can continue using it after the 24-hour timeout
expires.

• Veeam AI Online Assistant is not available on Windows 2012. It requires Windows 2012 R2 or later.

• To use Veeam AI Online Assistant, you must have an available internet connection on the server that runs
Veeam Backup & Replication Console.

Using Veeam AI Online Assistant


To start a new conversation:

1. Click Veeam AI Online Assistant button located in the upper right corner of the
Veeam Backup & Replication window.

2. In the chat window, type the question. Consider the following examples:

o How to create a Replication Job?

o Where are Veeam Backup & Replication logs stored?

o How to change license?

o How can I use Veeam Backup & Replication to make sure my VMs are regularly backed up, easily
recovered, and securely stored?

You can move the chat window and position it anywhere within the UI. The window remains open
alongside any wizard.

461 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Click Send button or press E nter to send your question.

4. When you do not need AI Assistant, you can do the following:

o Click Minimize to hide the chatbot window and preserve the conversation in the current session.

o Click P lus or Close button to erase the conversation and its context.

The replies from the Veeam AI Online Assistant are standardized text blocks in Markdown format. At the end of
every answer, the chatbot adds links to relevant Veeam documentation and KB articles. Screenshots and images
are not supported.

If you find the answer to be insufficient, you can add more deta ils. The bot retains the conversation context and
previous questions within a current session, so you do not have to repeat anything.

NOTE

If the AI Online Assistant service becomes overloaded, the question may get canceled.

462 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Resource Scheduling
Veeam Backup & Replication has the built-in mechanism of resource scheduling. Resource scheduling lets
Veeam Backup & Replication automatically define what backup infrastructure resources are required for data
protection and disaster recovery jobs and tasks, select optimal resources and assign them for the jobs and tasks.

Resource scheduling is performed by the Veeam Backup Service running on the backup server. When a job or
task starts, it communicates with the service and informs it about the resources it needs. The service analyzes
job settings, parameters specified for backup infrastructure components, current load on the components, and
automatically allocates optimal resources to the job.

For resource scheduling, Veeam Backup Service uses the following settings and features:

• Limitation of Concurrent Tasks

• Limitation of Read and Write Data Rates for Backup Repositories

• Performance Bottlenecks

463 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitation of Concurrent Tasks
When you start a data protection or disaster recovery job, Veeam Backup & Replication analyzes the list of VMs
added to the job and creates a list of tasks to be processed. Veeam Backup & Replication then defines what
backup infrastructure components must be used for the job, checks what backup infrastructure components are
currently available, and assigns necessary components to process the created job tasks. The task concept differs
depending on the type of the operation and the type of the backup chain being processed.

Backup infrastructure components typically process several tasks at the same time. You can limit the number of
tasks that backup infrastructure components must process concurrently. Task limitation helps you balance the
workload across the backup infrastructure and avoid performance bottlenecks.

Veeam Backup & Replication lets you limit the number of concurrent tasks for the following backup
infrastructure components:

• Backup proxies

• Backup repositories

NOTE

Task limits set for backup infrastructure components influence the job performance. For example, you add
a VM with 6 disks to a job and assign an off-host backup proxy that can process maximum 4 tasks
concurrently for the job. In this case, Veeam Backup & Replication will create 6 tasks (1 task per each VM
disk) and start processing 4 tasks in parallel. The other 2 tasks will be pending.

How Task Limitation Works


Task limiting is performed by the Veeam Backup Service. The Veeam Backup Service is aware of all backup
proxies and backup repositories in the backup infrastructure, and task limitation settings configured for them.

When a job starts, it informs the Veeam Backup Service about the list of tasks created for the job, and backup
infrastructure resources that must be used for the job. The Veeam Backup Service detects the number of tasks
that required backup infrastructure components are currently processing, and analyzes the number of allowed
tasks for these components. If the number of currently processed tasks has reached the allowed limit, the
backup infrastructure component will not start processing a new task until one of the currently running tasks
finishes.

Task Limitation for Backup Proxies


During data protection or disaster recovery jobs, Veeam Backup & Replication creates a separate task per each
disk of every VM added to the job.

We recommend that you define the maximum number of concurrent tasks depending on the number of CPU
cores available on the off-host proxy/Hyper-V host performing the role of the proxy. To calculate the optimum
limit, we recommend that you follow the rule: not more than 2 tasks per 1 CPU core.

464 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To limit the number of concurrent tasks on an off-host backup proxy, you must define the Ma x concurrent tasks
setting for the backup proxy. For onhost backup, you must define the Ta sk limit setting for the source Microsoft
Hyper-V host.

Task Limitation for Backup Repositories


The number of tasks that Veeam Backup & Replication creates during data protection or disaster recovery jobs
depends on the type of backup chains stored on the backup repository:

• For regular backup chains, Veeam Backup & Replication creates 1 task per job.

• For per-machine backup chains, Veeam Backup & Replication creates 1 task per every VM disk (that is, a
disk of a VM added to the job).

Synthetic operations performed in the backup repository (such as synthetic full backup, backup files merge and
transformation) are also regarded as tasks. The number of tasks performed during these operations also
depends on the type of backup chains stored on the backup repository:

• For regular backup chains, Veeam Backup & Replication creates 1 task per job.

• For per-machine backup chains, Veeam Backup & Replication creates 1 task per every VM chain (that is,
every VM added to the job).

We recommend that you define the maximum number of concurrent tasks based on the number of CPU cores
and RAM available on the backup repository. To calculate the optimum limit, follow the rule: not more than 2
tasks per 1 CPU core, not less than 1 GB RAM for each concurrently processed machine disk and not less than 4
GB RAM for each concurrently processed file share. In case of shared folder backup repositories, the same
amount of resources is required for gateway servers.

To limit the number of concurrent tasks in a backup repository, you must enable the Limit maximum concurrent
ta sks to <N> option on the backup repository and define the necessary task limit.

If you use backup repositories for backup copy jobs, you must also consider tasks for read operations.

465 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

When you limit the number of tasks for the backup repository, consider the storage throughput. If the
storage system is not able to keep up with the number of tasks that you have assigned, it will be the
limiting factor. It is recommended that you test components and resources of the backup infrastructure to
define the workload that they can handle.

Task Limitation for Components with Several Roles


One machine can perform several roles. For example, you can assign roles of the off-host backup proxy and
backup repository to the same machine, or use an off-host backup proxy as a gateway server for a shared folder
backup repository. In such situation, you must make sure that the backup infrastructure component is able to
process the cumulative number of tasks specified for different roles.

466 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitation of Read and Write Data Rates for
Backup Repositories
Veeam Backup & Replication can limit the speed with which Veeam Backup & Replication must read and write
data to/from the backup repository. The data read and write speed is controlled with the Limit read and write
d a ta rates to <N> MB/s option that you can enable in backup repository settings.

The Veeam Backup Service is aware of read and write data rate settings configured for all backup repositories in
the backup infrastructure. When a job targeted at a backup repository starts, the Veeam Backup Service informs
the Veeam Data Mover running on this backup repository about the allowed read/write speed set for this
repository so that the Veeam Data Mover can limit the read/write speed to the specified value.

If the backup repository is used by a number of tasks simultaneously, Veeam Backup & Replication splits the
allowed read/write speed rate between these tasks equally. Note that the specified limit defines the allowed
read speed and the allowed write speed at the same time.

For example, you set the Limit read and write data rates to option to 8 MB/s and start two backup jobs. Each job
processes 1 VM with 1 VM disk. In this case, Veeam Backup & Replication will create 2 tasks and target them at
the backup repository. The data write rate will be split between these 2 tasks equally: 4 MB/s for one task and 4
MB/s for the other task.

If at this moment you start some job reading data from the same backup repository, for example, a backup copy
job processing 1 VM with 1 disk, Veeam Backup & Replication will assign the read speed rate equal to 8 MB/s to
this job. If you start 2 backup copy jobs at the same time (each processing 1 VM with 1 disk),
Veeam Backup & Replication will split the read speed rate between these 2 jobs equally: 4 MB/s for one backup
copy job and 4 MB/s for the other backup copy job.

467 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
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. Veeam Backup & Replication provides
advanced statistics about the data flow efficiency and lets you identify bottlenecks in the data transmission
process.

Veeam Backup & Replication processes VM data in cycles. Every cycle includes a number of stages:

1. Reading VM data blocks from the source

2. Processing VM data on the offhost backup proxy

3. Transporting data over the network

4. Writing data to the target

When one data processing cycle is over, the next cycle begins. VM data therefore goes over the “data pipe”.

To evaluate the data pipe efficiency, Veeam Backup & Replication analyzes performance of all components in
the data flow working as the cohesive system, and evaluates key factors on the source and target sites.
Veeam Backup & Replication checks the following points in the data pipe:

1. Source — source disk reader component responsible for retrieving data from the source storage.

2. P roxy — offhost backup proxy component responsible for processing VM data.

3. Source W AN accelerator — WAN accelerator deployed on the source site. Used for backup copy and
replication jobs working through WAN accelerators.

4. Network — network queue writer component responsible for getting processed VM data from the offhost
backup proxy and sending it over the network to the backup repository or another offhost back up proxy.

5. Ta rget W AN Accelerator — WAN accelerator deployed on the target site. Used for backup copy and
replication jobs working through WAN accelerators.

6. Ta rget — target disk writer component (backup storage or replica datastore).

The resource usage level for these points is evaluated in percent. This percent rate defines the amount of time
for which components are busy during the job. An efficient data flow assumes that there is no latency at any
point of the data pipe, and all its components work for approximately equal amount of time.

If any of the components operates inefficiently, there may appear a bottleneck in the data path. The insufficient
component will work 100% of time while the others will be idling, waiting for data to be transferred. As a
result, the whole data flow will slow down to the level of the slowest point in the data path, and the overall
time of data processing will increase.

468 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To identify a bottleneck in the data path, Veeam Backup & Replication detects the component with the
maximum workload: that is, the component that works for the most time of the job. For example, you use a low -
speed storage device as the backup repository. Even if VM data is retrieved from the SAN storage on the source
site and transported over a high-speed link, VM data flow will still be impaired at the backup repository. The
backup repository will be trying to consume transferred data at the rate that exceeds its capacity, and the other
components will stay idle. As a result, the backup repository will be working 100% of job time, while other
components may be employed, for example, for 60% only. In terms of Veeam Backup & Replication, such data
path will be considered insufficient.

The bottleneck statistics for a job is displayed in the job session data . The bottleneck statistics does not
necessarily mean that you have a problem in your backup infrastructure. It informs you about the weakest
component in the data path. However, if you feel that the job performance is low, you may try taking some
measures to get rid of the bottleneck. For example, in the case described above, you can limit the number of
concurrent tasks for the backup repository.

Throttling as Bottleneck
In addition to main points in the data pipe, Veeam Backup & Replication may report throttling as a bottleneck.
This can happen in the following cases:

• If you limit the read and write data rates for a backup repository, a backup repository may become a
bottleneck. Veeam Backup & Replication will report Throttling in the bottleneck statistics.

• If you set up network throttling rules, network may become a bottleneck. Veeam Backup & Replication
will report Throttling in the bottleneck statistics.

469 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Job Priorities
Resources in the backup infrastructure are limited. To make sure that the most crucial jobs are the first to get
free resources to provide the reliable data protection, Veeam Backup & Replication uses the system of priorities
to allocate resources to different jobs.

The resource scheduler within Veeam Backup & Replication uses several stages to prioritize jobs and provide
free resources to them:

1. Ty p e — at the first stage, the resource scheduler identifies the priority of the jobs awaiting free resources
based on their type:

a. Ba ckup restore jobs — these jobs have the highest priority (800) and are the first to get free system
resources.

b. Continuous data protection jobs — these jobs have priority (700).

c. Sna pshotDeleter jobs — these jobs have priority (600).

d. Quick backup jobs — these jobs have priority (500).

e. Hig h priority jobs — jobs with the enabled Hig h p riority option have priority (400). You can enable the
Hig h priority option for the following jobs: backup jobs, replication jobs, agent jobs managed by
backup server, file backup jobs.

NOTE

When the Hig h priority option is enabled for the job, it is marked with a red flag in the list of
jobs under the Job s node in the Home view.

f. Reg ular backup and replication jobs — these jobs have priority (300).

g. Ba ckup copy jobs — these jobs have priority (200). Immediate backup copy jobs have priority (400)
when the related source backup job is a high priority job.

h. Archive jobs — these jobs have the lowest priority (100) and are the last to get free system resources.
These are the jobs that move backups to capacity and archive tiers.

2. P riority — at the second stage, the resource scheduler identifies the priority of the jobs within each type
group from the first stage based on their startup type:

a. Scheduled VSS proxy jobs — the jobs with the configured job schedule and using a VSS proxy have the
highest priority (40) within the group and are the first to get free system resources.

b. Scheduled jobs — the jobs with the configured job schedule have priority (30) within the group.

c. Ma nually started VSS proxy jobs — the manually started jobs using a VSS proxy have priority (20)
within the group.

d. Ma nually started jobs — the manually started jobs have the lowest priority (10) within the group and
are the last to get free system resources.

3. Sta rt time — if the jobs have the same type and priority, resources are first allocated to jobs that were
started earlier with an exception of tape jobs.

470 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The resource scheduler does not take into account the start time for tape jobs. The source job may
start when the tape job is still running. For more information on the priority settings for tape jobs,
see Schedule for Backup to Tape Job.

You can check the job type and priority of a certain job in service logs. For more information on logs, see
Logging.

471 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Veeam Backup & Replication
This section describes basic operations related to Veeam Backup & Replication configuration management.

472 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring General Settings
You can set up general settings for Veeam Backup & Replication. General settings are applied to all jobs, backup
infrastructure components and other objects managed by the backup server.

473 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying I/O Settings
You can specify data processing settings.

Consider the following:

• The E nable storage latency control option is included in the Veeam Universal License. When using a legacy
socket-based license, Enterprise or higher edition is required.

• The Set custom thresholds on individual datastores option is included in the Veeam Universal License.
When using a legacy socket-based license, Enterprise Plus edition is required.

To specify data processing settings:

1. From the main menu, select General Options.

2. Click the I/O Control tab.

3. To control the I/O load on the production storage where VMs reside, select the E na ble storage latency
control check box. When you enable storage latency control, Veeam Backup & Replication monitors
storage read latency on production volumes during data protection and disaster recovery activities. To
monitor the storage latency, Veeam Backup & Replication uses real-time metrics from the hypervisor
where VMs reside. Metrics from the hypervisor are collected every 10 seconds.

Specify two thresholds:

a. In the Stop assigning new tasks to datastore at field, specify the I/O latency limit at which
Veeam Backup & Replication must not assign new tasks targeted at the volume.

b. In the Throttle I/O of existing tasks at field, specify the I/O latency limit at which
Veeam Backup & Replication must decrease the speed of data retrieval or writing to/from the volume.
When the I/O latency for this volume reaches this value, the Veeam Data Mover working with this
volume will slow down data retrieval or writing.

The value in the Stop assigning new tasks to datastore at field cannot be greater than the value in the
Throttle I/O of existing tasks at field.

NOTE

If you enable the storage latency control option, Veeam Backup & Replication starts processing VM disks
residing on the same datastore with a 40-60 second time offset. This offset helps
Veeam Backup & Replication evaluate the current I/O load on the datastore. For example, if you launch a
job processing a VM with two disks, Veeam Backup & Replication will start processing the first VM disk,
wait for 40-60 seconds to evaluate the I/O workload on the datastore, and then start processing the
second VM disk.

Consider this behavior. If you schedule jobs that process multiple VM disks residing on the same datastore
to start at the same time, the jobs performance will degrade.

474 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can set the I/O latency limit for every storage in the virtual infrastructure sep arately.

To set the I/O latency limit for every storage separately:

1. From the main menu, select General Options.

2. Click the I/O Control tab.

3. Click Configure.

4. Click Ad d > Volume, select the necessary volume and click OK to add it to the storage list.

5. Select the added volumes in the list and click E d it.

6. Specify the I/O thresholds for the volumes.

475 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Security Settings
In the Security tab, you can configure the following:

• Backup Server Certificate


Configure a TLS certificate to establish secure communication from backup infrastructure components to
the backup server.

• Linux Hosts Authentication

Enable the fingerprint check for Linux machines to protect connection from man-in-the-middle attacks.

• Cloud Connect

Enable access to the cloud gateway for the Remote Access Console connected to an external network.

• FIPS Compliance

Enable FIPS-compliant operation mode.

• Audit Logs Location


Select a folder for storing audit logs.

Backup Server Certificate


When you configure the Veeam Backup & Replication infrastructure, you can specify what TLS certificate must
be used to establish a secure connection from backup infrastructure components to the backup server.
Veeam Backup & Replication offers the following options for TLS certificates:

• Keep the default self-signed TLS certificate generated by Veeam Backup & Replication at the process of
upgrading to a new version of Veeam Backup & Replication.

• Use Veeam Backup & Replication to generate a new self-signed TLS certificate. To learn more, see
Generating Self-Signed Certificate.

• Select an existing TLS certificate from the certificates store. To learn more, see Importing Certificate from
Certificate Store.

• Import a TLS certificate from a file in the PFX format. To learn more, see Importing Certificate from PFX
Files.

If you plan to use a certificate issued by your own Certificate Authority (CA), make sure that the certificate
meets the requirements. For more information, see Using Certificate Signed by Internal CA.

476 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

If you update the TLS certificate used on the backup server, you must also update info about the certificate
on the following backup infrastructure components:

• For AHV Backup proxies, pass through the E d it Nutanix Proxy wizard. To do this, in the Ba ckup
Infrastructure view, right-click a proxy and select P roperties. In the wizard, click Finish. Also, restart
the Veeam AHV Service.
• For RHV Backup proxies, pass through the E d it Red Hat Virtualization Proxy wizard. To do this, in
the Ba ckup Infrastructure view, right-click a proxy and select P roperties. In the wizard, click Finish.

If you remove the old certificate from the Microsoft Windows certificate store, you must also reconfigure
Veeam Agents added to the Computers with pre-installed agents protection group. To do this, repeat the
configuration step of the Veeam Agent deployment scenario as described in the subsections of the
Deploying Veeam Agents Using Generated Setup Files section. Other protection groups will be
automatically reconfigured during the next rescan operation.

If you do not remove the old certificate from the Microsoft Windows certificate store, all protection groups
will be automatically reconfigured the next time Veeam Agents connect to the backup server.

Generating Self-Signed Certificate


You can use Veeam Backup & Replication to generate a self-signed certificate for authenticating parties in the
Veeam Backup & Replication infrastructure.

To generate TLS certificates, Veeam Backup & Replication employs the RSA Full cryptographic service provider
by Microsoft Windows installed on the backup server. The created TLS certificate is saved to the Shared
certificate store. The following types of users can access the generated TLS certificate:

• User who created the TLS certificate

• LocalSystem user account

• Local Administrators group

If you use a self-signed TLS certificate generated by Veeam Backup & Replication, you do not need to take
additional actions to deploy the TLS certificate on a protected computer. When Veeam Backup & Replication
discovers a protected computer, a matching TLS certificate with a public key is installed on the protected
computer automatically. During discovery, Veeam Installer Service deployed on the protected computer
retrieves the TLS certificate with a public key from the backup server and installs a TLS certificate with a public
key on the protected computer.

NOTE

When you generate a self-signed TLS certificate with Veeam Backup & Replication, you cannot include
several aliases to the certificate and specify a custom value in the Subject field. The Subject field value is
taken from the Veeam Backup & Replication license installed on the Veeam backup server.

IMP ORTANT

If you update the TLS certificate used on the backup server, you must also update info about the certificate
on the specific backup infrastructure components as described in section Backup Server Certificate.

To generate a self-signed TLS certificate:

1. From the main menu, select General Options.

477 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Click the Security tab.

3. In the Security tab, click Install.

4. At the Certificate Type step of the wizard, select Generate new certificate.

5. At the Generate Certificate step of the wizard, specify a friendly name for the created self-signed TLS
certificate.

6. At the Summary step of the wizard, review the certificate properties. Use the Cop y to clipboard link to
copy and save information about the generated TLS certificate. You will be able to use the copied
information to verify the TLS certificate with the certificate thumbprint.

478 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
7. Click Finish. Veeam Backup & Replication will save the generated certificate in the Shared certificate store
on the Veeam backup server.

Importing Certificate from Certificate Store


If the Veeam backup server has been issued a TLS certificate signed by a CA and the TLS certificate is located in
the Microsoft Windows certificate store, you can use this certificate for authenticating parties in the
Veeam Backup & Replication infrastructure.

IMP ORTANT

If you update the TLS certificate used on the backup server, you must also update info about the certificate
on the specific backup infrastructure components as described in section Backup Server Certificate.

To select a certificate from the Microsoft Windows certificate store:

1. From the main menu, select General Options.

2. Click the Security tab.

3. In the Security tab, click Install.

4. At the Certificate Type step of the wizard, choose Select certificate from the Certificate Store.

479 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. At the P ick Certificate step of the wizard, select a TLS certificate that you want to use. You can select only
certificates that contain both a public key and a private key. Certificates without private keys are not
displayed in the list.

6. At the Summary step of the wizard, review the certificate properties.

7. Click Finish to apply the certificate.

Importing Certificate from PFX Files


You can import a TLS certificate in the following situations:

• Your organization uses a TLS certificate signed by a CA and you have a copy of this certificate in a file of
PFX format.

• You have generated a self-signed TLS certificate in the PFX format with a third-party tool and you want to
import it to Veeam Backup & Replication.

NOTE

The TLS certificate must pass validation on the Veeam backup server. Otherwise, you will not be able to
import the TLS certificate.

If a PFX file contains a certificate chain, only the end entity certificate will be imported.

IMP ORTANT

If you update the TLS certificate used on the backup server, you must also update info about the certificate
on the specific backup infrastructure components as described in section Backup Server Certificate.

To import a TLS certificate from a PFX file:

1. From the main menu, select General Options.

2. Click the Security tab.

3. In the Security tab, click Install.

480 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. At the Certificate Type step of the wizard, choose Imp ort certificate from a file.

5. At the Imp ort Certificate step of the wizard, specify a path to the PXF file.

6. If the PFX file is protected with a password, specify the password in the field below.

7. At the Summary step of the wizard, review the certificate properties. Use the Cop y to clipboard link to
copy and save information about the TLS certificate. You can use the copied information on a protected
computer to verify the TLS certificate with the certificate thumbprint.

8. Click Finish to apply the certificate.

Using Certificate Signed by Internal CA


If you want to use a certificate signed by your own Certification Authority (CA), consider the following:

• Make sure that Veeam Backup & Replication server trusts the CA. That means that the Certification
Authority certificate must be added to the Trusted Root Certification Authority store on the
Veeam Backup & Replication server. Also, Certificate Revocation List (CRL) must be accessible from the
Veeam Backup & Replication server.

481 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you use Windows Server Certification Authority, issue a Veeam Backup & Replication certificate based on
the built-in Subordinate Certification Authority template or templates similar to it. You can manage
templates with the Certificate Templates MMC snap-in.

IMP ORTANT

The following certificates are not supported:

• Elliptic Curve Signature (ECC) certificates


• Cryptography API: Next Generation (CNG) certificates

A certificate signed by a CA must meet the following requirements:

• The certificate subject is equal to the fully qualified domain name of the Veeam Backup & Replication
server. For example: vbrserver.domain.local.

• The Sub ject Alternative Name field contains both the FQDN and the NetBIOS name. You can add multiple
DNS entries in the following format: DNS:vbrserver.domain.local,DNS:vbrserver.

• The minimum key size is 2048 bits.

• The following key usage extensions are enabled in the certificate:

o Digital Signature

o Certificate Signing

o Off-line CRL Signing

482 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o CRL Signing (86)

• The P a th Length Constraint parameter in the Ba sic Constraints extension is set to 0.

If you use Windows Server Certification Authority, open the Certificate Templates MMC snap-in and
select the certificate template based on the built-in Subordinate Certification Authority template or
templates similar to it. On the E x tensions tab, enable the Do not a llow subject to issue certificates to
other CAs option.

• The key type in the certificate is set to Exchange.

To start using the signed certificate, you must select it from the certificates store on the
Veeam Backup & Replication server. To learn more, see Importing Certificate from Certificate Store.

483 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Linux Hosts Authentication
In the Linux hosts authentication section of the Veeam Backup & Replication settings, you can specify SSH
fingerprint verification settings for protected Linux machines.

NOTE

Starting from version 12.1 (build 12.1.0.2131), Veeam Backup & Replication uses the SHA-256 hashing
algorithm for verification. If you upgrade from previous versions, SSH fingerprint format will be updated
automatically during next rescan or next connection to the Linux machine through SSH.

You can select one of the following options:

• Ad d all discovered hosts to the list automatically — with this option enabled, Veeam Backup & Replication
allows all Linux servers added to the protection group and all Linux VMs to be connected to the backup
server. Machine fingerprints are added to the Veeam Backup & Replication database and checked every
time when machines establish a connection with the backup server. If SSH fingerprints do not match, the
connection fails.

• Ad d unknown hosts to the list manually — this option provides a more secure environment because only
trusted Linux servers and Linux VMs can connect to the backup server:

o Machines that have already established a connection with the backup server and have their
fingerprints stored in the Veeam Backup & Replication database. You can export the list of trusted
machines to the known_hosts file. To do this, click E x port and specify a path to the folder to save
the file.

o Machines specified in the known_hosts file imported to Veeam Backup & Replication. To import the
known_hosts file, click Imp ort and specify a path to the folder where the file resides.

Veeam Backup & Replication displays the number of trusted machines in the Trusted hosts field.

Untrusted Linux VMs are displayed under the Untrusted node in the Inventory view. Untrusted Linux
servers are displayed under the Una vailable node in the Ba ckup Infrastructure view. These machines
cannot connect to the backup server and download Veeam Agent for Linux installation packages during
discovery. Also, guest OS processing of untrusted VMs will fail.

To start managing an untrusted Linux machine, you need to validate its fingerprint manually in the
Veeam Backup & Replication console. For more details, see Validating Untrusted Hosts.

484 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Validating SSH Fingerprints
When you select the Ad d unknown hosts to the list manually option in Veeam Backup & Replication settings,
you need to validate SSH fingerprints of untrusted Linux servers and Linux VMs manually in the
Veeam Backup & Replication console. For more information about all SSH fingerprint verification options, see
Linux Host Authentication.

Validating Linux VMs


During discovery, Veeam Backup & Replication puts untrusted Linux VMs to the Untrusted node in the Inventory
view. You can validate all untrusted VMs at once or a specific VM:

• To validate all untrusted Linux VMs at once, select the Untrusted node in the inventory pane and click
Trust All on the ribbon. Alternatively, you can right-click the Untrusted node and select Trust all.

485 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• To validate a specific VM, select it in the working area and click Trust on the ribbon. Alternatively, you can
right-click the VM and select Trust.

Validating Linux Servers


If the SSH public key fingerprint of a Linux server is changed, Veeam Backup & Replication puts this machine to
the Una vailable node in the Ba ckup Infrastructure view. To validate the Linux server, do the following:

1. Right-click the Linux server and select P roperties.

2. In the SSH Connection step of the E d it Linux Server wizard, click Ap p ly.

3. In the dialog box, click Y es to confirm that you trust this server.

486 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Click Finish to close the wizard.

Cloud Connect
If you use the Veeam Cloud Connect functionality, you can remotely access the tenant backup server to manage
Veeam Backup & Replication deployed on the tenant side. One of the ways to do this is to use the Remote
Access Console. In case it is installed on a remote machine connected to an external network, you will need to
enable access to the cloud gateway for the Remote Access Console over the internet. For more information, see
Veeam Cloud Connect Guide.

To enable access to the cloud gateway for the Remote Access Console:

1. From the main menu, select General Options.

2. Open the Security tab.

3. In the Cloud Connect section, select the Accept remote console connection requests originating from the
Internet check box.

487 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Click OK.

FIPS Compliance
By default, Veeam backup infrastructure components use platform-provided cryptographic APIs and FIPS-
compliant Veeam Cryptographic Module to meet NIST CMVP cryptographic and security requirements.
Additionally, you can enable FIPS-compliant operation mode. It restricts connections to non-FIPS compliant
platforms and runs self-tests to ensure that encryption modules are valid and work properly.

NOTE

To make your backup infrastructure FIPS-compliant follow vendor recommendations. For more information
on Microsoft Windows Server, see this article.

To enable the FIPS-compliant operation mode:

1. From the main menu on the backup server, select General Options.

2. Open the Security tab.

3. In the FIP S compliance section, select the E nable FIPS-compliant operation mode check box.

4. Click OK.

NOTE

If you use Amazon S3 or Amazon S3 Glacier object repositories in your backup infr astructure and enable
FIPS-compliant operation mode, Veeam Backup & Replication checks if these components are FIPS-
compliant. If some of them are not, the warning will be displayed.

IMP ORTANT

If you have backup infrastructure components based on Linux servers with persistent Veeam Data Movers
and select or clear the E na ble FIPS-compliant operation mode check box, you must open the Edit Linux
Server wizard for each Linux server with the persistent Veeam Data Mover and proceed to the end of the
wizard. This will update server settings. If you do not update the settings, the servers will be unavailable.

488 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Audit Logs Location
Veeam Backup & Replication provides logging of performed activities, such as data protection and disaster
recovery tasks: for example, the list of files restored during File-Level Restore sessions. The results of the audit
of such activities are stored in form of .csv files that are called audit logs. For more information about log files,
see Logging.

In Aud it Logs Location field, you can specify folder where the audit logs will be stored. By default, log files are
stored in the following folder: %ProgramData%\Veeam\Backup\Audit. You can also specify an SMB (CIFS)
folder.

IMP ORTANT

Storing audit logs on WORM tapes is not supported. Storing audit logs on WORM storages is supported
without log compression. This type of storage prevents the data from being deleted or modified. Thus, raw
audit logs cannot be deleted after creating compressed files.

If you use an SMB (CIFS) folder, the service account used for Veeam Backup Service on the machine with
Veeam Backup & Replication must have access to that SMB (CIFS) folder. By default, this is the LocalSystem
account, so you will need to grant write access to the VBR Server Active Directory computer account.

489 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, older audit logs are compressed automatically. To perform this operation, the service account under
which Veeam Backup Service runs must have modify permissions on the target folder. If you do not want to
compress older audit logs, clear the Comp ress older audit logs automatically check box.

490 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Email Notification Settings
You can receive email notifications with results on jobs performed on the backup server.

To receive email notifications, do the following:

• Configure global email notification settings in Veeam Backup & Replication.

• Configure job notification settings.

TIP

To receive email notification about all jobs performed on the backup server in one email, configure email
notification settings in Veeam Backup Enterprise Manager.

Configuring Global Email Notification Settings


To configure global email notification settings:

1. From the main menu, select General Options.

2. Open the E -ma il Settings tab and select the E na ble e-mail notifications check box.

3. Configure mail server.

4. Customize send settings.

Configuring Mail Server


To configure mail server, perform the following steps:

1. In the Ma il Server field, specify the authentication method you want to use. Veeam Backup & Replication
supports the following methods:

o SMTP basic authentication

o Google Gmail OAuth 2.0 authentication

o Microsoft 365 OAuth 2.0 authentication

NOTE

For more secure environments, it is recommended to use OAuth 2.0 authentication. Also, note that
Microsoft and Google consider SMTP basic authentication as an outdated industry standard and plan
to disable it. For more information, see this Microsoft article and this Google article.

2. If you want to use SMTP basic authentication, perform the following steps:

a. In the Ma il server field, select SMTP server from the list.

491 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. In the SMTP server field, enter a full DNS name, or IPv4 or IPv6 address of the SMTP server that will
be used for sending email notifications. Note that you can use IPv6 addresses only if IPv6
communication is enabled as described in section IPv6 Support.

c. To specify user credentials and connection options, click the Ad vanced button:

▪ Specify the port number and connection timeout for the SMTP server.

NOTE

Sending email notifications using Implicit TLS (over port 465) is not supported. For more
information about Implicit TLS, see this RFC section.

▪ To use a secure connection for email operations, select the Connect using SSL check box.

▪ If you need to connect to the SMTP server using a specific account, select the This SMTP server
requires authentication check box and select the necessary credentials from the Log on as list. If
you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the
right to add credentials. For more information, see Managing Credentials.

When you add an SMTP server, Veeam Backup & Replication saves to the configuration database a
thumbprint of the TLS certificate. If the certificate is not trusted, Veeam Backup & Replication displays a
warning. If you trust the certificate, click Continue.

492 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. If you want to use Google Gmail OAuth 2.0 authentication, perform the following steps:

a. In the Ma il server field, select Google Gmail from the list and click the Sig n in with Google button.

b. In the opened web browser window, specify the Google account to connect to the
Veeam Backup & Replication application. Note that you must select Send email on your behalf check
box during configuring access options.

493 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• For security reasons, it is recommended to use a dedicated service account with granular
SendMail permissions.
• To sign in with the Google account, your default web browser must meet Google
requirements. For more information, see this article.
If the authentication is successful, the Token is valid notice will appear. The token is refreshed
automatically. If it was revoked or the Google account password was changed, click the Re-authorize
link to update configuration.

To specify custom authentication options, click the Ad vanced button:

o Select the Use custom application registration settings check box.

o Specify the application client ID and the client secret.

For more information on how to register your custom application, see Registering Application in Google
Cloud Console.

4. If you want to use Microsoft 365 OAuth 2.0 authentication, perform the following steps:

a. In the Ma il server field, select Microsoft 365 from the list and click the Authorize now link.

b. In the opened window, specify your Exchange Online credentials to connect to the
Veeam Backup & Replication application.

NOTE

Consider the following:

• For security reasons, it is recommended to use a dedicated service account with granular
SendMail permissions.
• To sign in with Exchange Online credentials, turn off the Internet Explorer Enhanced
Security Configuration option in Server Manager. For more information, see this article.
If the authentication is successful, the Token is valid notice will appear. The token is refreshed
automatically. If it was revoked or Exchange Online credentials were changed, click the Re-authorize
link to update configuration.

494 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To specify custom authentication option, click the Ad vanced button:

o Select the Use custom application registration settings check box.

o Specify the application client ID and the tenant ID.

NOTE

For custom applications, note that you must select Consent on behalf of your organization check box
during configuring access options.

For more information on how to register your custom application, see Registering Application in Microsoft
Azure Portal.

Customizing Send Settings


To customize send settings, perform the following steps:

1. In the From field, specify an email from which email notifications must be sent. Note that for OAuth 2.0
autnentication, it must be the account you use to connect to the Veeam Backup & Replication application.

2. In the To field, specify the recipient addresses. Use a semicolon to separate multiple addresses. Recipients
specified in this field will receive notification about every job managed by the backup server. You can
leave the field empty if required.

For every particular job, you can specify additional recipients. For more information, see Configuring Job
Notification Settings.

IMP ORTANT
If you specify the same email recipient in both job notification and global notification settings,
Veeam Backup & Replication will send the job notification only.

3. In the Sub ject field, specify a subject for the sent message. You can use the following variables in the
subject:

a. %Time% — completion time

b. %JobName%

c. %JobResult%

d. %ObjectCount% — number of VMs in the job

e. %Issues% — number of VMs in the job that have been processed with the Warning or Failed status

4. In the Send daily reports at field, specify at what time Veeam Backup & Replication will send daily email
reports. Daily reports are generated for different purposes throughout Veeam Backup & Replication:

o Reports about processing results of scale-out repository data. For more information, see Receiving
Scale-Out Backup Repository Reports.

o Reports about processing results of backup copy jobs. For more information, see Notification Settings
in the Creating Backup Copy Jobs for VMs and Physical Machines section.

o Reports about processing results of backup copy jobs for transaction log backups. For more
information about transaction log backups, see Microsoft SQL Server Logs Backup.

o Reports about backups of virtual and physical machines created by Veeam Agent for Microsoft
Windows or Veeam Agent for Linux in the Ma naged by Agent mode.

495 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Reports with statistics for rescan job sessions performed for protection groups of virtual and physical
machines created by Veeam Agent for Microsoft Windows or Veeam Agent for Linux .

o Reports about processing results of backup copy jobs for backups created by Veeam Plug-ins for
Enterprise Applications.

o Reports about active Instant Recovery sessions, that is, sessions that were not finalized. For more
information about Instant Recovery, see Instant Recovery to VMware vSphere and Instant Recovery to
Microsoft Hyper-V.

NOTE

Settings configured for a certain report override global notification settings.

5. In the Notify on group, select the Success, W arning and Fa ilure check boxes to receive email notification if
a job is run successfully, not successfully or with a warning.

6. Select the Sup press notifications until the last retry check box to receive a notification about the final job
status. If you do not enable this option, Veeam Backup & Replication will send one notification per every
job retry.

7. Veeam Backup & Replication allows sending a test email to check if all settings have been configured
correctly. To send a test email, click Test Message .

Registering Application in Google Cloud Console


If you want to use your own web application for email notifications, you need to configure it in the Google Cloud
console. To do this, perform the following steps:

1. Log in to the Google Cloud console under a Google account that has permissions to create applications.

2. Create a new project and enable Gmail API for the project. To do this, open AP Is and services > Library >
Gma il API > Ma nage and click E na ble API.

3. Create OAuth credentials. To do this, perform the following steps:

a. Open AP Is and services > Credentials. Click Create credentials and select OAuth client ID.

b. In the Ap p lication type field, select Desktop app.

c. In the Na me field, specify the name of your OAuth 2.0 client.

d. Click Create to generate the application client ID and the client secret. In the opened window, you can
copy credentials or download them in the JSON format. You can also find them later in the AP Is and
services > Credentials section when editing your OAuth 2.0 client ID.

4. Open AP Is and services > OAuth consent screen and click E d it App. Specify your application name and the
user support email and click Sa ve and continue.

496 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. If your application is in the Testing status, you must specify test users. To do this, at the Test users step of
the E d it App wizard, click Ad d users. To apply changes, click Sa ve and continue. Note that only test users
will have access to the app.

After you finish the registration, specify custom application registration settings when configuring the mail
server for Google Gmail OAuth 2.0 authentication. For more information, see Configuring Mail Server.

NOTE

You can leave your application in the Testing status and do not publish it. In that case, you will receive a
warning message Google hasn't verified this app when connecting to your application. If you want to verify
it, see this Google article.

Registering Application in Microsoft Azure Portal


If you want to use your own web application for email notifications, you need to configure it in the Microsoft
Azure portal. To do this, perform the following steps:

1. Log in to the Microsoft Azure portal under Exchange Online credentials that has permissions to register
Azure AD applications.

2. Register the application. To do this, open Azure Active Directory > Ap p registrations and click New
reg istration:

a. In the Na me field, specify the name of your application.

b. In the Sup ported account types section, select the Accounts in this organizational directory only
option.

497 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. Click Reg ister.

After registration, you can copy application (client) ID and directory (tenant) ID. You can also find these
credentials later in the Overview section of you application properties.

3. Add a platform configuration for your application. To do this, open Authentication > P latform
configurations and click Ad d a platform:

a. Select Mob ile and d esktop applications.

b. Select the MSAL redirect URI generated in the following format: msal<applicationid>://auth.

498 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. Click Configure.

4. Grant the application the Mail.Send permission of Microsoft Graph. This will allow
Veeam Backup & Replication to call the Microsoft Graph API for sending email notifications. To do this,
open AP I p ermissions and click Ad d a permission:

a. Select Microsoft Graph > Ap plication Permissions.

b. Select the Mail.Send permission from the list and click Ad d permissions.

5. Click Grant admin consent for <Your Directory Name>. In the displayed window, click Y es to confirm the
operation.

After you finish the registration, specify custom application registration settings when configuring the mail
server for Microsoft 365 OAuth 2.0 authentication. For more information, see Configuring Mail Server .

499 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Job Notification Settings
To configure job notification settings:

1. Open advanced settings of the job.

2. On the Notifications tab, select the Send email notifications to the following recipients check box.

3. In the field below, enter an email address to which a notification must be sent. You can enter several email
addresses separated with a semicolon.

IMP ORTANT
If you specify the same email recipient in both job notification and global notification settings,
Veeam Backup & Replication will send the job notification only.

4. You can choose to use global notification settings for the job or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for the job, select Use custom notification settings and specify
notification settings as required.

5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

500 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying SNMP Settings
You can receive SNMP traps with results on jobs performed on the backup server. You can use SNMP traps to
feed data to other monitoring systems such as CA Unicenter, BMC Patrol, IBM Tivoli or HPE OpenView. SNMP
traps can be sent to 5 different destinations.

Veeam Backup & Replication supports SNMP versions 1 and 2.

TIP

You can find the list of available SNMP traps in the VeeamBackup.mib file. The backup server stores this
file in the <vbr_installation_folder>\Backup\ folder. The installation folder is specified at the
Program features step of the installation wizard. To interpret the traps incoming from the backup se rver,
import the VeeamBackup.mib file to your recipient systems.

To receive SNMP traps, you must perform the following tasks:

• Configure global SNMP settings.

• Configure SNMP service properties.

• Configure SNMP settings for jobs.

Configuring Global SNMP Settings


To configure global SNMP settings:

1. From the main menu, select Op tions > Event Forwarding.

2. In the SNMP servers window, Click Ad d .

3. In the Receiver field, specify an IPv4 or IPv6 address of the SNMP recipient. Note that you can use IPv6
addresses only if IPv6 communication is enabled as described in section IPv6 Support.

4. In the field on the right, enter the port number to be used.

5. In the Community string field, enter the community identifier.

501 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring SNMP Service Properties
To configure SNMP service properties on recipient systems:

1. Install a standard Microsoft SNMP agent from the Microsoft Windows distribution on the computer.

2. From the Sta rt menu, select Control Panel > Ad ministrative Tools > Services.

3. Double-click SNMP Service to open the SNMP Service Properties window.

4. Click the Tra ps tab.

5. Add the public string to the Community name list and name of the necessary host to the Tra p destinations
list.

6. Click the Security tab.

7. Make sure the Send authentication trap check box is selected.

8. Add the public string to the Accepted community names list.

9. Select the Accept SNMP packets from any host check box.

10. Click OK to save changes.

502 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring SNMP Settings for Jobs
To receive SNMP traps with results of a specific job:

1. Open advanced settings of the job.

2. On the Notifications tab, select the Send SNMP notifications for this job check box.

3. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

503 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Syslog Servers
Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), you can use an external syslog server to
manage events written by Veeam Backup & Replication.

How Integration with Syslog Server Works


When you add the syslog server in the Veeam Backup & Replication console, Veeam Backup & Replication sends
a test event to check if it can communicate with the syslog server. Further, all events
Veeam Backup & Replication writes to Microsoft Windows Event Log will also be sent to the syslog server.

Each event contains a syslog message. The format of the message is defined by RFC 5424. For example:

2023-11-03T13:30:25.182677+01:00 <14> VBRSRV01 Veeam_MP [categoryId=0 instance


Id=110 JobSessionID="58df29d6-a21b-43b2-a397-4c44ed1e05c1" JobID="cd13e656-8be9
-445a-bf9e-513b24293d35" JobType="0" Platform="0" Flags="0" Version="1" Descrip
tion="Backup job 'Backup Job 2' has been started."]

Field Description E x ample

TIMESTAMP Date and time. For more 2023-10-


information about the format, see 23T15:23:23.259882+02:00
RFC 3339.

PRI Message priority. <14>

HOSTNAME Host name of the backup server. VBRSRV01

APP-NAME Name of the application that Veeam_MP


generates events.

STRUCTURED-DATA Event metadata. May include [categoryId=0


message details in the Description instanceId=110
parameter. JobSessionID="58df29d6-
a21b-43b2-a397-
4c44ed1e05c1"
JobID="cd13e656-8be9-
445a-bf9e-513b24293d35"
JobType="0" Platform="0"
Flags="0" Version="1"
Description="Backup job
'Backup Job 2' has been
started."]

MSG Message details. May not be sent Backup job 'Backup Job 2'
if message details are included in has been started.
the STRUCTURED-DATA field.

504 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The structure and the content of the syslog message may vary for different syslog servers. For the full list
of fields that can be sent in a syslog message, see the Syslog Message Format section in RFC 5424.

Requirements and Limitations


Integration with syslog servers has the following requirements and limitations:

• To use functionality, you must have a paid license.

• You can add only one syslog server.

Adding Syslog Server


To add a syslog server, do the following:

1. From the main menu, select Op tions > E vent Forwarding.

2. In the Sy slog servers window, click Ad d .

3. In the Server field, specify the FQDN or IPv4 address of the server. You cannot specify the IPv6 address i n
this field.

4. In the Tra nsport field, specify the transport protocol: TCP, UDP or TLS. Default port numbers are 514 (for
TCP and UDP) and 6514 (for TLS).

5. Click OK.

NOTE

If the syslog server is unavailable, the error message will be displayed.

505 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

If required, you can also configure the following specific parameters on the backup server:

• Add the Unicode byte order mask (BOM) before the MSG field
• [For TCP or TLS connections] Use the octet count prefix as a syslog message delimiter instead of \n
character
• [For TCP connections] Specify custom connection timeout

To configure these parameters, see this Veeam KB article.

506 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Other Notification Settings
You can configure Veeam Backup & Replication to automatically notify you about the following events:

• Low disk space

• Support contract expiration

• New product versions, available updates and patches

Low Disk Space Notification


When you run a job, Veeam Backup & Replication checks disk space in the target backup repository and
production storage. If the disk space is below a specific value, Veeam Backup & Replication will display a
warning message in the job session details.

To specify the disk space threshold:

1. From the main menu, select General Options.

2. Click the Notifications tab.

3. In the Ba ckup storage and P roduction datastores sections, select the W a rn me when free disk space is
b elow <N> % options and specify a desired disk space threshold.

4. In the P roduction datastores section, select the Sk ip VMs when free disk is below <N> % option and
specify a desired disk space threshold. When the threshold is reached, Veeam Backup & Replication will
terminate backup and replication jobs working with production volumes before volume snapshots/VM
checkpoints are taken. Such behaviour helps ensure that production volumes do not run out of space.

Veeam Backup & Replication also terminates jobs if the amount of free space on the volume is below 2 GB.
You can change this threshold limit with registry values. For more information, see this Veeam KB article.

507 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Support Contract Expiration Notification
By default, Veeam Backup & Replication informs email recipients specified in global notification settings about
the support expiration date in every email notification. Veeam Backup & Replication starts sending such
notifications 14 days before the expiration date. Expiration information is also shown on the splash screen and
on the License Information window (to display the License Information window, select Help > License from the
main menu).

To stop receiving notifications about support contract expiration:

1. From the main menu, select General Options.

2. Click the Notifications tab.

3. Clear the E na ble notifications about support contract expiration check box.

New Product Versions and Hypervisor Update Notification


Veeam Backup & Replication automatically checks and notifies you about new product versions and updates
available on the Veeam website and released hypervisor updates. To receive the notificat ions, make sure that
the backup server is connected to the internet. Otherwise, you will not receive the notifications about updates.
For more information on notifications, see Update Notification.

To disable the notifications:

1. From the main menu, select General Options.

2. Click the Notifications tab.

3. Clear the Check for product and hypervisor updates periodically check box.

IMP ORTANT

We recommend you to leave the update notifications enabled. This will help you not to miss critical
updates.

508 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
509 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Session History Settings
You can specify session history settings for jobs performed on the backup server.

1. From the main menu, select General Options.

2. Click the History tab.

3. In the Sessions section, configure how many sessions you want to display in the Sessions list of the History
view:

o Select Show a ll sessions if you want to show all sessions.

o Select Show only last sessions if you want to show a limited number of sessions. In the field, also
specify the total number of sessions that you want to display.

4. In the Session history retention section, configure for how long you want to keep session information in
the database:

o Select Keep all sessions if you do not want to delete sessions.

o Select Keep only last weeks if you want to keep sessions for a limited period of time. In the field, also
specify this period in weeks.

510 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Users and Roles
This section describes how to configure Veeam Backup & Replication users and user groups and how to set up 4-
eyes authorization for sensitive operations.

511 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Users
To perform Veeam Backup & Replication operations, you can add users or user groups and assign to them one of
the following Veeam Backup & Replication roles:

Role Op erations

Veeam Backup Administrator Can perform all administrative activities in Veeam Backup & Replication.
Note that with the Veeam Backup & Replication console, Veeam Backup
Administrator has full access to all files on servers and hosts added to the
backup infrastructure.

Veeam Restore Operator Can perform restore operations using existing backups and replicas.
However, Veeam Restore Operator cannot migrate a recovered VM to the
production environment during Instant Recovery.

Consider the following:

• Restore Operators can restore data from any backups. That enables
them to restore disks and files with specially crafted malicious
content. This opens an opportunity for insider attacks, including but
not limited to privilege escalation leading to the entire system
takeover. Because of this possibility, the Restore Operators role
should be treated as a sensitive role similar to Veeam Backup
Administrators.
• During restore, Veeam Restore Operator can overwrite existing
instances: VMs during VM restore, disks during disk restore and files
during file-level restore.

Veeam Backup Operator Can start and stop existing jobs, export backups, copy backups and create
VeeamZip backups.

Veeam Backup Viewer Has the “read-only” access to Veeam Backup & Replication. Can view a list
of existing jobs and review the job session details.

Veeam Tape Operator Can manage tapes and perform the following operations: library/server
rescan, tape eject, tape export, tape import, tape mark as free, tape move
to media pool, tape erase, tape catalog, tape inventory, set tape password,
tape copy, tape verification, start and stop tape backup jobs.

A role assigned to the user defines the user activity scope: what operations in Veea m Backup & Replication the
user can perform. Role security settings affect the following operations:

• Starting and stopping jobs

• Performing restore operations

You can assign several roles to the same user. For example, if the user must be able to start jobs and perform
restore operations, you can assign the Veeam Backup Operator and Veeam Restore Operator roles to this user.

512 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
Consider the following:

• Built-in administrator accounts (Domain\Administrator and Machine\Administrator) always have full


access to Veeam Backup & Replication, even if you exclude them from all Veeam Backup & Replication
roles. If you delete the Administrators group from the Veeam Backup & Replication roles, the users who
are added to this group will still have access to Veeam Backup & Replication.

NOTE

To protect administrator accounts from being compromised, it is strongly recommended to enable


multi-factor authentication (MFA). In that case, even users with administrator privileges must pass
the additional verification. For more information, see Multi-Factor Authentication.

• The user account under which the Veeam Backup Service runs must have the Veeam Backup Administrator
role. By default, during installation the Veeam Backup Administrator role is assigned to users in the
Administrators group. If you change the default settings, make sure that you assign the Veeam Backup
Ad ministrator role to the necessary user account. It is recommended to assign the Veeam Backup
Ad ministrator role to the user account explicitly rather than the group to which the user belongs.

NOTE

If you enable multi-factor authentication (MFA), note that Veeam Backup & Replication services must
run under the service account with disabled MFA. For more information, see Disabling MFA for
Service Accounts.

Adding Users
To add a user or a user group:

1. From the main menu, select Users and Roles > Security.

2. Click Ad d .

3. In the User or group field, enter a name of a user or user group in the DOMAIN\USERNAME format.

4. From the Role list, select the necessary role to be assigned.

5. Click OK.

To reduce the number of user sessions opened for a long time, you can set the idle timeout to automatically log
off users. To do this, select the E nable a uto logoff after <number> min of inactivity check box and set the
number of minutes.

513 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To use additional user verification, you can enable multi-factor authentication. For more information, see Multi-
Factor Authentication.

514 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Four-Eyes Authorization
Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), you can enable four-eyes authorization to
reduce the risk of accidental actions affecting sensitive data. This functionality uses an additional control
mechanism that requires additional approval to particular operations in Veeam Backup & Replication given by
another user with the Veeam Backup Administrator role.

IMP ORTANT

Before you enable the feature, make sure that you have at least two users (added to a user group or
separate ones) with the Veeam Backup Administrator role assigned.

Veeam Backup & Replication supports four-eyes authorization for the following operations:

• Deleting backup files or snapshots from the disk or configuration database

• Deleting information about unavailable backups from the configuration database

• Removing backup repositories, storage, and service providers from the backup infrastructure

• Performing operations in the Files view:

o Editing, renaming and deleting files

o Overwriting files

o Renaming and deleting folders

• Adding, updating and deleting users or user groups

• Enabling and disabling multi-factor authentication (MFA) for all users and user groups

• Resetting MFA for a specific user

• Enabling, updating and disabling automatic logoff for all users and user groups

Consider that four-eyes authorization cannot protect the backup infrastructure if the
Veeam Backup & Replication server is compromised. To build a more secure environment, follow security
guidelines. For more details, see General Security Considerations and Securing Backup Infrastructure.

How Four-Eyes Authorization Works


Veeam Backup & Replication supports the following scenario for four-eyes authorization:

o A backup administrator tries to delete backup data or remove a machine from the backup infrastructure.

o The request for additional approval is displayed in the Home view, under the P ending approvals node.
All users with the Veeam Backup Administrator role also get email notifications if you configured global
email notification settings. For more information, see Configuring Global Email Notification Settings.

o Another backup administrator approves or rejects the request. If there are multiple requests, the
backup administrator can approve or reject them simultaneously. All users with the Veeam Backup
Administrator role also get email notifications.

NOTE

The backup administrator that created the request can only reject their own requests.

515 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If no backup administrators process the request till the end of the specific time period (7 days by
default), it will be automatically rejected.

All events related to four-eyes authorization are displayed in the History view, under the Authorization Events
node. These events include information about:

• Approved and rejected requests

• Updated four-eyes authorization settings

• Updated settings for users and user groups

• Assigned roles

• Added or deleted users and user groups

516 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
Four-eyes authorization has the following requirements and limitations:

• The functionality is included only in the Veeam Universal License or the Enterprise Plus edition. If the
license expires, you will still be able to process already created requests but not to create new ones.

• If four-eyes authorization is enabled, you cannot perform delete operations using PowerShell cmdlets,
REST API, and Veeam Backup Enterprise Manager.

• If you try to approve or reject the request and the object that you want to delete is blocked by another
operation, for example, by the job session, the operation will not be performed. In this case, you need
to process the request later, when the object will not be blocked.

• Immutable backup files cannot be deleted even with the four-eyes authorization enabled.

Enabling Four-Eyes Authorization


To enable four-eyes authorization, perform the following steps:

• Make sure that you have at least two users (added to a user group or separate ones) with the Veeam
Backup Administrator role assigned.

• From the main menu, select Users and Roles > Authorization.

• Select the Require additional approval for sensitive operations check box.

• Specify the time period during which the requested operation must be approved or rejected (minimum 1
day, maximum — 30).

NOTE

To disable four-eyes authorization, you will also need an additional approval from another backup
administrator.

517 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Credentials
This section describes different types of credential records that Veeam Backup & Replication supports.

518 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Credentials Manager
You can use the Credentials Manager to create and maintain a list of credentials records that you plan to use to
connect to components in the backup infrastructure.

The Credentials Manager lets you create the following types of credentials records:

• Standard account

• Group Managed Service Accounts

• SSH credentials

• SSH private keys

Standard Accounts
You can create a credentials record for an account that you plan to use to connect to a Microsoft Windows
server, Hyper-V server, a VM running Microsoft Windows OS, a storage system and others.

To create a new standard credentials record:

1. From the main menu, select Credentials and Passwords > Da tacenter Credentials.

2. Click Ad d > Standard account.

3. In the Username field, enter a user name for the account that you want to add. You can also click Browse
to select an existing user account.

4. In the P a ssword field, enter a password for the account that you want to add. To view the entered
password, click and hold the eye icon on the right of the field.

519 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. In the Description field, enter a description for the created credentials record. As there can be a number of
similar account names, for example, Administrator, it is recommended that you provide a meaningful
unique description for the credentials record so that you can distinguish it in the list. The description is
shown in brackets, following the user name.

Group Managed Service Accounts


You can add a credentials record for a Group Managed Service Account (gMSA) that you plan to use to run guest
processing tasks. Note that before you add a record you should check requirements and limitations and perform
actions described in section Using Group Managed Service Accounts.

To add a new credentials record with the gMSA:

1. From the main menu, select Credentials and Passwords > Da tacenter Credentials.

2. Click Ad d > Ma naged service account.

3. In the Username field, enter a gMSA that you want to add. Note that the name of the account must be
specified in the following format: DOMAIN\User or [email protected].

520 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Description field, enter a description for the created credentials record. As there can be a number of
similar account names, for example, gmsa01, it is recommended that you provide a meaningful unique
description for the credentials record so that you can distinguish it in the list. The description is shown in
brackets, following the user name.

SSH Credentials
You can create a credentials record for the account that you plan to use to connect to a Linux server or VM
running Linux OS.

To create a new credentials record with a user name and password for a Linux server:

1. From the main menu, select Credentials and Passwords > Da tacenter Credentials.

2. Click Ad d > SSH credentials (Linux account – before Veeam Backup & Replication 12.1 (build 12.1.0.2131)).

3. In the Username field, enter a user name for the account that you plan to add.

4. In the P a ssword field, enter a password for the account that you want to add. To view the entered
password, click and hold the eye icon on the right of the field.

5. In the SSH p ort field, specify the SSH port over which you want to connect to a Linux server. By default,
port 22 is used.

6. If you specify data for a non-root account that does not have root permissions on a Linux server, you can
use the Non-root account section to grant sudo rights to this account.

a. To provide a non-root user with root account privileges, select the E levate account privileges
a utomatically check box.

b. To add the user account to sudoers file, select the Ad d account to the sudoers file check box. In the
Root password field, enter the password for the root account.

If you do not enable this option, you will have to manually add the user account to the sudoers file.

521 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. If you plan to use the account to connect to Linux servers where the sudo command is not available
or fails, you have an option to use the su command instead. To enable the su command, select the
Use "su" if "sudo" fails check box and in the Root password field, enter the password for the root
account.

Veeam Backup & Replication will first try to use the sudo command. If the attempt fails,
Veeam Backup & Replication will use the su command.

7. In the Description field, enter a description for the created credentials record. As there can be a number of
similar account names, for example, Root, it is recommended that you provide a meaningful unique
description for the credentials record so that you can distinguish it in the list. The description is shown in
brackets, following the user name.

IMP ORTANT

Consider the following:

• You can create a separate user account intended for work with Veeam Backup & Replication on a
Linux-based VM, grant root privileges to this account and specify settings of this account in the
Credentials Manager. It is recommended that you avoid additional commands outp ut for this user
(like messages echoed from within ~/.bashrc or command traces before execution) because they may
affect Linux VM processing.
• Cases when root password is required to elevate account rights to root using sudo are no longer
supported.

SSH Private Keys


You can log on to a Linux server or VM running Linux OS using the Identity/Pubkey authentication method. The
Identity/Pubkey authentication method helps protect against malicious applications like keyloggers,
strengthens the security level and simplifies launch of automated tasks.

522 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To use the Identity/Pubkey authentication method, you must generate a pair of keys — a public key and private
key:

• Public key is stored on Linux servers to which you plan to connect from the backup server. The key is kept
in a special authorized_keys file containing a list of public keys.

• Private key is stored on the client machine — backup server. The private key is protected with a
passphrase. Even if the private key is intercepted, the eavesdropper will have to provide the passphrase to
unlock the key and use it.

For authentication on a Linux server, the client must prove that it has the private key matching the public key
stored on the Linux server. To do this, the client generates a cryptogram using the private key and pas ses this
cryptogram to the Linux server. If the client uses the "correct" private key for the cryptogram, the Linux server
can easily decrypt the cryptogram with a matching public key.

Veeam Backup & Replication has the following limitations for the Identity/Pubkey authentication method:

• Veeam Backup & Replication does not support keys that are stored as binary data, for example, in a file of
DER format.

• Veeam Backup & Replication supports only keys whose passphrase is encrypted with algorithms supporte d
by PuTTY:

o AES (Rijndael): 128-bit, 192-bit and 256-bit CBC or CTR (SSH-2 only)

o Blowfish: 128-bit CBC

o Triple-DES: 168-bit CBC

TIP

Veeam Backup & Replication 12 supports PPK file versions 2 and 3.

Veeam Backup & Replication supports the following key algorithms: RSA, DSA, ECDSA, EdDSA (ED25519). For
these algorithms you can use the following key formats:

Key Algorithms

Key Formats
RSA DSA E CDSA E d DSA
( E D25519)

PEM

private

private-openssh

sshcom

PKCS8

523 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Key Algorithms

Key Formats
RSA DSA E CDSA E d DSA
( E D25519)

RDC4716 (private-openssh-new)

IMP ORTANT

If you use VMware VIX/vSphere Web Services,


Veeam Backup & Replication does not support usage of public keys for
guest processing on Linux guest servers.

To add a credentials record using the Identity/Pubkey authentication method, do the following:

1. Generate a pair of keys using a key generation utility, for example, ssh-keygen.

Note that keys generated as ED448 as are not supported.

2. Place the public key on a Linux server. To do this, add the public key to the authorized_keys file in the
.ssh/ directory in the home directory on the Linux server.

3. Place the private key in some folder on the backup server or in a network shared folder .

4. In Veeam Backup & Replication, from the main menu select Credentials and Passwords > Da tacenter
Credentials.

5. Click Ad d > SSH private key (Linux private key – before Veeam Backup & Replication 12.1 (build
12.1.0.2131)).

6. In the Username field, specify a user name for the created credentials record.

7. In the P a ssword field, specify the password for the user account. The password is required in all cases
except when you use root or a user with enabled NOPASSWD:ALL setting in /etc/sudoers .

8. In the P rivate key field, enter a path to the private key or click Browse to select a private key.

9. In the P a ssphrase field, specify a passphrase for the private key on the backup server. To view the entered
passphrase, click and hold the eye icon on the right of the field.

10. In the SSH p ort field, specify a number of the SSH port that you plan to use to connect to a Linux server.
By default, port 22 is used.

11. If you specify data for a non-root account that does not have root permissions on a Linux server, you can
use the Non-root account section to grant sudo rights to this account.

a. To provide a non-root user with root account privileges, select the E levate specified account to root
check box.

b. To add the user account to sudoers file, select the Ad d account to the sudoers file automatically
check box. In the Root password field, enter the password for the root account.

If you do not enable this option, you will have to manually add the user account to the sudoers file.

524 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. When registering a Linux server, you have an option to failover to using the su command for distros
where the sudo command is not available.

To enable the failover, select the Use "su" if "sudo" fails check box and in the Root p assword field,
enter the password for the root account.

12. In the Description field, enter a description for the created credentials record. As there can be a number of
similar account names, for example, Root, it is recommended that you supply a meaningful unique
description for the credentials record so that you can distinguish it in the list. The description is shown in
brackets, following the user name.

IMP ORTANT

Cases when root password is required to elevate account rights to root using sudo are no longer supported.

Editing and Deleting Credentials Records


You can edit or delete credentials records that you have created.

To edit a credentials record:

1. From the main menu, select Credentials and Passwords > Da tacenter Credentials.

2. Select the credentials record in the list and click E d it.

3. If the credentials record is already used for any component in the backup infrastructure,
Veeam Backup & Replication will display a warning. Click Y es to confirm your intention.

4. Edit settings of the credentials record as required.

To delete a credentials record:

1. From the main menu, select Credentials and Passwords > Datacenter Credentials.

525 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Select the credentials record in the list and click Remove. You cannot delete a record that is already used
for any component in the backup infrastructure.

NOTE

The Credentials Manager contains 3 system credentials records:

• A credentials record for the Veeam FLR appliance


• A credentials record for the tenant-side network extension appliance
• A credentials record for Microsoft Azure restore proxy appliance (former Azure proxy)

You cannot delete these credentials records. However, you can edit them: change a password and record
description.

526 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cloud Credentials Manager
You can use the Cloud Credentials Manager to create and maintain a list of credentials records that you plan to
use to connect to cloud services.

The Cloud Credentials Manager lets you create the following types of credentials records:

• Veeam Cloud Connect Accounts

• Access Keys for AWS Users

• Microsoft Azure Storage Accounts

• Microsoft Azure Compute Accounts

• Microsoft Azure Storage Accounts (Entra ID)

• Microsoft Azure Stack Hub Compute Accounts

• Google Cloud Accounts

• Google Cloud Service Accounts

Veeam Cloud Connect Accounts


You can add a credentials record for a tenant account — an account that you plan to use to connect to a service
provider (SP).

Before you add a credentials record, the SP must register a tenant account on the SP Veeam backup server.
Tenants without accounts cannot connect to the SP and use Veeam Cloud Connect resources. For more
information, see the Registering Tenant Accounts section in the Veeam Cloud Connect Guide.

To create a credentials record for a tenant account:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Click Ad d > Veeam Cloud Connect service provider account.

3. In the Username field, enter a user name for the account that the SP has provided to you.

NOTE

If the SP used VMware Cloud Director to allocate replication resources to you, you must enter a user
name for the VMware Cloud Director tenant account in the following format:
Organization\Username. For example: TechCompanyOrg\Administrator.

4. In the P a ssword field, enter a password for the account that the SP has provided to you. To view the
entered password, click and hold the eye icon on the right of the field.

527 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. In the Description field, enter a description for the created credentials record.

Access Keys for AWS Users


You can create a record for credentials that you plan to use to connect to AWS.

To access AWS resources, you can use Identity and Access Management (IAM) user credentials or AWS account
root user credentials. However, AWS recommends that you use the IAM user credentials. For details, see the
AWS Account Root User Credentials vs. IAM User Credentials section in the AWS General Reference. The
permissions that you must provide to the user are listed in section Permissions.

Since Veeam Backup & Replication uses AWS CLI commands to perform operations in AWS, instead of a user
name and password you must specify an AWS access key. AWS access keys are long -term user credentials that
consists of two parts: an access key ID and a secret access key. For details, see the Managing Access Keys for
IAM Users section in the AWS IAM User Guide.

To create a credentials record:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Click Ad d > AW S access key.

3. In the Access key field, enter an access key ID.

4. In the Secret key field, enter a secret access key. To view the entered secret key, click and hold the eye
icon on the right of the field.

5. In the Description field, enter a description for the created credentials record.

IMP ORTANT

It is recommended that the user whose credentials you plan to use to connect to AWS S3 has administrative
permissions — access to all AWS S3 actions and resources.

528 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Azure Storage Accounts (Shared Key)
You can create a credentials record for a Microsoft Azure storage account to connect to the following types of
accounts:

• Azure Blob storage added as an object storage repository, a performance extent or capacity extent of a
scale-out backup repository. Use this option to store data on Azure Blob storage.

• Azure Archive storage added as an archive extent of a scale-out backup repository. Use this option to store
data on Azure Blob storage.

• Azure Blob storage added as an external repository repository. Use this option to copy, import and restore
backups created by Veeam Backup for Microsoft Azure from external to on-premises repositories.

• Microsoft Azure Blob Storage added as a source of unstructured data. Use this option to backups data
located on Azure Blob Storage repository and restore backed -up data.

Storage Accounts Supported Types


The following types of storage accounts are supported.

Storage account Sup ported Sup ported Sup ported access tiers
ty p e services p erformance
tiers

General-purpose Blob (block Standard Hot: to store data that you access frequently.
V2 blobs only)

529 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Storage account Sup ported Sup ported Sup ported access tiers
ty p e services p erformance
tiers

Cool: to store data that you access infrequently.


BlobStorage
Cold: to store data that you access infrequently. Can
be set only for blobs. Supported in Archive Tier object
storage systems.

Archive: to store data that you access rarely. Can be


set only for blobs. Supported in Archive Tier object
storage systems.

Consider the following:


• For Azure Blob storage
Veeam Backup & Replication will use the access
tier that you specified at the Container step of
the New Object Storage wizard.
• For Azure Archive storage
Veeam Backup & Replication will use the access
tier that you specified at the Access Tier step of
the New Object Storage wizard.

General-purpose Blob (block Standard N/A


V1 blobs only)

BlockBlobStorage Blob (block Premium N/A


blobs only)

For more information about the types of storage accounts in Azure, see Microsoft Docs.

IMP ORTANT

Microsoft Azure Blob storage accounts with the hierarchical namespace are not supported.

Adding Microsoft Azure Storage Account


To create a record for a Microsoft Azure storage account:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Click Ad d > Microsoft Azure storage account.

3. In the Account field, enter the storage account name.

4. In the Sha red key field, enter the storage account shared key. To view the entered key, click and hold the
eye icon on the right of the field.

530 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The Allow storage a ccount key access option for Shared Key authorization must be enabled in the
storage account. For more information on how to find this option, see Microsoft Docs.

5. In the Description field, enter an optional description for the credentials record.

TIP

If you do not have a Microsoft Azure storage account, you can create it in the Azure portal, as described in
the Azure Storage Documentation.

Microsoft Azure Storage Accounts (Entra ID)


NOTE

This feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

You can create a credentials record for a Microsoft Azure storage account with Microsoft Entra ID authorization
to connect to the following types of accounts:

• Azure Blob storage added as an object storage repository, a performance extent or capacity extent of a
scale-out backup repository. Use this option to store data on Azure Blob storage.

• Azure Archive storage added as an archive extent of a scale-out backup repository. Use this option to store
data on Azure Blob storage.

• Microsoft Azure Blob storage added as a source of unstructured data. Use this option to backups data
located on Azure Blob Storage repository and restore backed -up data.

To add a Microsoft Azure storage account with Microsoft Entra ID authorization, use the Microsoft Azure
Storage Account (Entra ID) wizard.

531 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before you Begin
Before you add a Microsoft Azure storage account with Microsoft Entra ID authorization to
Veeam Backup & Replication, check the following prerequisites:

• If you plan to use a new Microsoft Entra application to access storage account (at the Account Type step),
consider the following:

o Make sure that you already have a user account in Microsoft Entra ID. This account must have
privileges listed in the Permissions section.

o If you have multiple tenants associated with the Microsoft Entra ID user account that you plan to use
to create a new application, Veeam Backup & Replication will create the application in the home
tenant of the account. As a result, the application will have access only to the subscriptions of the
home tenant, as well as the Azure Compute account will. If you want to use another tenant and its
subscriptions, follow the instructions in this Veeam KB article.

o The created Entra ID application is assigned with the following roles for a stor age account which name
was entered at the Name step of the wizard:

▪ Storage Account Contributor

▪ Storage Blob Data Contributor

▪ Storage Blob Data Owner

For more information on roles, see Microsoft Azure Docs.

You can limit the subscriptions to which Veeam Backup & Replication assigns the privileges as described in
this Veeam KB article.

• If you plan to use an existing Entra ID application to access storage account (at the Account Type step),
consider the following:

o Create an Entra ID application beforehand. For more information on how to create it, see Microsoft
Docs. Note that you do not need to configure redirect URI.

o The Entra ID application must have several role privileges assigned on a storage account. For more
information, see Permissions.

o Only storage accounts from subscriptions that belong to the ap plications tenant can be used.

• On the backup server, you must set the correct time according to the timezone where the backup server is
located. Otherwise, you may not be able to add a Microsoft Entra ID user account to
Veeam Backup & Replication.

• When the internet access is possible only through HTTP/HTTPS proxy, you must configure the proxy
settings for the Local System account or account under which the Veeam Backup Service is running. For
more information, see this Microsoft article.

532 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Microsoft Azure Storage Account (Entra ID) Wizard
To launch the Microsoft Azure Storage Account (Entra ID) wizard, do the following:

1. In the main menu, click Credentials and Passwords > Cloud Credentials.

2. In the Ma nage Cloud Credentials window, click Ad d and select Microsoft Azure storage account (Entra ID).

533 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Account Name
At the Na me step of the wizard, specify an Azure storage account name. From the Reg ion drop-down list, select
a Microsoft Azure region where the storage account is located.

534 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Account Type
At the Account Type step of the wizard, choose whether you want to connect to Microsoft Azure using an
existing or a newly created Entra ID application. In the latter case, Veeam Backup & Replication will create a new
Entra ID application automatically.

535 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Authentication Settings
At the authentication step of the wizard, create a new Entra ID application or specify settings for an existing
Entra ID application.

Creating New Microsoft Entra ID Application


This step applies only if you have selected the Create a new a ccount option at the Account Type step of the
wizard.

Configuring Microsoft Entra Application


When you choose to create a new account, Veeam Backup & Replication registers a new Microsoft Entra
application with a Microsoft Entra tenant. Veeam Backup & Replication will use this application to authenticate
to Microsoft Azure. For more information on Microsoft Entra applications, see Microsoft Docs. To create the
Microsoft Entra application, you must use a single-use verification code that Veeam Backup & Replication
provides you.

At the Authentication step of the wizard, do the following:

1. Click Cop y to clipboard to copy the verification code.

2. Click the https://microsoft.com/devicelogin link.

3. On the Microsoft Azure device authentication page, do the following:

a. Paste the code that you have copied and click Nex t. Note that the code will expire in 15 minutes.

b. Specify a Microsoft Entra ID account that will be used to create an application. Note that the user
name must be specified in the user principal name format (username@domain). The account must
have permissions described in section Permissions.

Veeam Backup & Replication will create Microsoft Entra application in the tenant of the account.

4. Go back to the Ad d Azure Account wizard and check whether any errors occurred during the
authentication process.

NOTE

Consider the following:

• If you have multiple tenants associated with the Microsoft Entra ID user account that you plan to use
to create a new application, Veeam Backup & Replication will create the single-tenant application in
the home tenant of the account. As a result, the application can have access only to resources in the
subscriptions of the home tenant. If you want to use storage account in another tenant
subscriptions, follow the instructions this Veeam KB article.
• The created Entra ID application is assigned with the following roles for a storage account which
name was entered at the Name step of the wizard:
o Storage Account Contributor
o Storage Blob Data Contributor
o Storage Blob Data Owner
For more information on roles, see Microsoft Azure Docs. You can limit the subscriptions to which
Veeam Backup & Replication assigns the privileges as described in this Veeam KB article.

536 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Existing Microsoft Entra ID Application
This step applies only if you have selected the Use the existing account option at the Account Type step of the
wizard.

Configuring Microsoft Entra Application


To use an existing Microsoft Entra application:

1. In the Tena nt ID specify an ID of a tenant (directory) where the Microsoft Entra ID application resides.

2. In the Ap p lication ID field, specify the ID of the necessary application. The Microsoft Entra ID application
must have privileges listed in section Permissions.

3. In the Select authentication type area, choose whether you want to use password-based authentication
(application secret) or certificate-based authentication. Then provide the necessary information.

537 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For more information on how to get tenant and application IDs, secret and certificate, see Microsoft Docs.

538 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Summary step of the wizard, review details of configured settings and click Finish to close the wizard.

Microsoft Azure Compute Accounts


You can use a Microsoft Azure Compute account for the following operations in Veeam Backup & Replication:

• Restore workloads to Microsoft Azure.

• Add Azure archive storage.

• Add a Microsoft Azure Plug-in for Veeam Backup & Replication appliance.

When you add a Microsoft Azure Compute account, Veeam Backup & Replication imports information about
subscriptions and resources associated with this account. During the restore process,
Veeam Backup & Replication accesses these resources and uses them to register new VMs in Microsoft Azure.

To add a Microsoft Azure Compute account, use the Microsoft Azure Compute Account wizard.

Before You Begin


Before you add a Microsoft Azure Compute account to Veeam Backup & Replication, check the following
prerequisites:

• If you plan to use a new Microsoft Entra ID (formerly Azure Active Directory) application to access
Microsoft Azure (at the Account Type step), consider the following:

o Make sure that you already have a user account in Microsoft Entra ID. This account must have
privileges listed in section Permissions.

539 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o If you have multiple tenants associated with the Microsoft Entra ID user account that you plan to use
to create a new application, Veeam Backup & Replication will create the application in the home
tenant of the account. As a result, the application will have access only to the subscriptions of the
home tenant, as well as the Azure Compute account will. If you want to use another tenant and its
subscriptions, follow the instructions in this Veeam KB article.

o The created Microsoft Entra ID application is assigned the Contributor, Key Vault Crypto User and
Storage Queue Data Contributor role privileges for the subscriptions for which the following
conditions are met:

▪ The subscriptions are linked to the home tenant of the Microsoft Entra ID user.

▪ The Microsoft Entra ID user has access to these subscriptions and can assign roles on the
subscription level for the registered application.

You can limit the subscriptions to which Veeam Backup & Replication assigns the privileges as
described in this Veeam KB article. For more information on roles, see Microsoft Azure Docs.

• If you plan to use an existing Microsoft Entra ID (formerly Azure Active Directory) application to access
Microsoft Azure (at the Account Type step), consider the following:

o Make sure that you already have a Microsoft Entra ID application. For more information on how to
create it, see Microsoft Docs. Note that you do not need to configure redirect URI.

o The Microsoft Entra ID application must have privileges listed in section Permissions.

o Only subscriptions that belong to the selected tenant will be added.

• [If you plan to restore Linux workloads using helper appliances] Veeam Backup & Replication uses its
built-in credentials record to work with all helper appliances. For security reasons, we recommended that
you change a password for this account before you set up the helper appliances. Changing credentials is
required only once. For more information, see Changing Credentials for Helper Appliances.

• On the backup server, you must set the correct time according to the timezone where the backup server is
located. Otherwise, you may not be able to add a Microsoft Azure user account to
Veeam Backup & Replication.

• When the internet access is possible only through HTTP/HTTPS proxy, you must configure the proxy
settings for the Local System account or account under which the Veeam Backup Service is running. For
more information, see this Microsoft article.

540 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Microsoft Azure Compute Account Wizard
To launch the Microsoft Azure Compute Account wizard, do the following:

1. In the main menu, click Credentials and Passwords > Cloud Credentials.

2. In the Ma nage Cloud Credentials window, click Ad d and select Microsoft Azure compute a ccount.

541 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Account Name
At the Na me step of the wizard, specify a name under which this credentials record will be shown in the Cloud
Credential Manager.

542 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Deployment Type and Region
To select a deployment type and a region where your Microsoft Azure Compute account is located:

1. At the Dep loyment Type step of the wizard, select Microsoft Azure.

2. From the Reg ion drop-down list, select a Microsoft Azure region.

IMP ORTANT

Veeam Backup & Replication no longer supports Azure Germany since Microsoft closed Microsoft Cloud
Deutschland.

543 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Access Type
At the Account Type step of the wizard, choose whether you want to connect to Microsoft Azure using an
existing or newly created Microsoft Entra ID (formerly Azure Active Directory) application. In the latter case,
Veeam Backup & Replication will create the new Microsoft Entra ID application automatically.

Creating New Entra ID Application


This step applies only if you have selected the Create a new a ccount option at the Account Type step of the
wizard.

Configuring Microsoft Entra ID Application


When you choose to create a new account, Veeam Backup & Replication registers a new Microsoft Entra ID
(formerly Azure Active Directory) application in Microsoft Azure. Veeam Backup & Replication will use this
application to authenticate to Azure. For more information on Microsoft Entra ID applications, see Microsoft
Azure Docs. To create the Microsoft Entra ID application, you must use a single-use verification code that
Veeam Backup & Replication provides you.

At the Account Type step of the wizard, do the following:

1. Click Cop y to clipboard to copy the verification code.

2. Click the https://microsoft.com/devicelogin link.

3. On the Microsoft Azure device authentication page, do the following:

a. Paste the code that you have copied and click Nex t. Note that the code will expire in 15 minutes.

544 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. Specify a Microsoft Entra ID user account that will be used to create an application. Note that the user
name must be specified in the user principal name format (username@domain). The account must
have permissions described in section Permissions.

Veeam Backup & Replication will retrieve information about subscriptions to which the Microsoft
Entra ID user has access and will create Microsoft Entra ID application in the tenant of the account.

4. Back to the Ad d Azure Account wizard, check whether any errors occurred during the authentication
process.

NOTE

Consider the following:

• If you have multiple tenants associated with the Microsoft Entra ID user account that you plan to use
to create a new application, Veeam Backup & Replication will create the application in the home
tenant of the account. As a result, the application will have access only to the subscriptions of the
home tenant, as well as the Azure Compute account will. If you want to use another tenant and its
subscriptions, follow the instructions in this Veeam KB article.
• The created Microsoft Entra ID application is assigned the Contributor, Key Vault Crypto User and
Storage Queue Data Contributor role privileges for the subscriptions for which the following
conditions are met: the subscriptions are linked to the home tenant of the Microsoft Entra ID user;
the Microsoft Entra ID user has access to these subscriptions and can assign roles on the
subscription level for the registered application.
You can limit the subscriptions to which Veeam Backup & Replication assigns the privileges as
described in this Veeam KB article. For more information on roles, see Microsoft Azure Docs.

545 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Enabling Direct Restore of Linux Workloads
To enable direct restore of Linux-based workloads, select the E na ble direct restore of Linux-based computers.
When selected, this check box enables the Helper Appliance step where you will have to configure helper
appliances.

Specifying Existing Entra ID Application


This step applies only if you have selected the Use the existing account option at the Account Type step of the
wizard.

Configuring Microsoft Entra ID Application


To use an existing Microsoft Entra ID (formerly Azure Active Directory) application:

1. In the Tena nt ID specify an ID of a tenant (directory) where the Microsoft Entra ID application resides.

2. In the Ap p lication ID field, specify the ID of the necessary application. The Microsoft Entra ID application
must have privileges listed in section Permissions.

3. In the Select authentication type area, choose whether you want to use password-based authentication
(application secret) or certificate-based authentication. Then provide the necessary information.

For more information on how to get tenant and application IDs, secret and certificate, see Microsoft Docs.

546 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Enabling Direct Restore of Linux Workloads
To enable direct restore of Linux-based workloads, select the E na ble direct restore of Linux-based computers.
When selected, this check box enables the Helper Appliance step where you will have to configure helper
appliances.

547 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Configuring Helper Appliance
This step is available if you have selected E na ble direct restore of Linux-based computers at the Sub scription
step of the wizard.

If you plan to restore Linux workloads to multiple locations, you must configure a helper appliance in each
location.

To configure a helper appliance, do the following:

1. On the right of the Helper appliances list, click Ad d .

2. From the Sub scription list, select a subscription whose resources you want to use to configure the helper
appliance. The subscription list contains all subscriptions that are associated with the Azure Compute
account.

To be displayed in the Sub scription list, a subscription must be created in advance and associated to the
Azure account as described in Microsoft Docs.

3. From the Location list, select a location where you want to configure the helper appliance. Make sure that
you select a geographic region with which at least one storage account of the subscription is associated.

4. From the Storage account list, select a storage account whose resources you want to use to store disks of
the helper appliance.

To be displayed in the Storage account drop-down list, a storage account must be created in advance as
described in Microsoft Docs.

NOTE

You cannot use a storage account with the ZRS or GZRS replication option. For details, see Microsoft
Docs.

5. Click Choose if you do not want Veeam Backup & Replication to create a new resource group and select
the required group.
To be displayed in the Resource group drop-down list, a resource group must be created in advance as
described in Microsoft Docs.

6. From the Virtual network list, select a network to which the helper appliance must be connected.

To be displayed in the Virtual network drop-down list, a virtual network must be created in advance as
described in Microsoft Docs.

7. From the Sub net list, select a subnet for the helper appliance.

To be displayed in the Sub net drop-down list, a subnet must be created in advance as described in
Microsoft Docs.

8. At the SSH p ort field, specify a port over which Veeam Backup & Replication will communicate with the
helper appliance.

9. Click OK.

548 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
After you have configured all the helper appliances, click Ap p ly and wait while Veeam Backup & Replication
deploys the configured helper appliances.

549 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review details of configured settings and click Finish to close the wizard.

Microsoft Azure Stack Hub Compute Accounts


To restore workloads to Microsoft Azure Stack Hub, you must add an Azure Stack Hub Compute account to
Veeam Backup & Replication. When you add an Azure Stack Hub Compute account, Veeam Backup & Replication
imports information about subscriptions and resources associated with this account. During the restore process,
Veeam Backup & Replication accesses these resources and uses them to register new VMs in Azure Stack Hub.

If necessary, you can add different Azure Stack Hub Compute accounts to Veeam Backup & Replication. In this
case, Veeam Backup & Replication will import information about all subscriptions and resources associated with
provided accounts, and you will be able to use these resources for restore.

Information about subscriptions and resources is saved to the Veeam Backup & Replication configuration
database. You can re-import this information at any time.

Prerequisites
Before restoring workloads to Microsoft Azure Stack Hub, consider the following:

• [For restore to Microsoft Azure Stack Hub version 1808 and later] You must configure the backup server
as described in this Veeam KB article.

• Check the Permissions section.

• [If you plan to restore Linux workloads using helper appliances] Veeam Backup & Replication uses its
built-in credentials record to work with all helper appliances. For security reasons, we recommended that
you change a password for this account before you set up the helper appliances. Changing credentials is
required only once. For more information, see Changing Credentials for Helper Appliances.

550 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you plan to use an existing Microsoft Entra ID (formerly Azure Active Directory) application to access
Microsoft Azure (at the Account Type step), only subscriptions that belong to the selected tenant will be
added.

Adding Microsoft Azure Stack Hub Account


To add a Microsoft Azure Stack Hub Compute account, do the following.

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. In the Ma nage Cloud Credentials window, click Ad d and select Microsoft Azure compute a ccount.

3. At the Na me step of the wizard, specify a name under which this credentials record will be shown in the
Cloud Credential Manager.

551 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. At the Dep loyment Type step of the wizard, select Microsoft Azure Stack. In the Azure Stack resource
ma nager endpoint field, specify the virtual IPv4 address of Azure Resource Manager in the following
format: management.<region>.<FQDN>. Note that IPv6 addresses are not supported.

To learn about Azure Stack Hub virtual IP addresses, see Microsoft Docs.

5. The rest of the procedure for adding the Azure Stack account does not differ from the procedure for
adding the Microsoft Azure account. Follow the steps described in Microsoft Azure Compute Account.

Google Cloud Accounts


You can add to the backup infrastructure a credentials record for the Google Cloud account that will be used to
connect to Google Cloud Storage. Veeam Backup & Replication uses these credentials to add a Google Cloud
storage repository to the backup infrastructure as an external repository.

To create a record for a Google Cloud account:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Click Ad d > Google Cloud access key.

3. In the Access Key and Secret key fields, specify the Hash-based Message Authentication Code (HMAC) key
associated with the Google Cloud account. Veeam Backup & Replication will use the HMAC key to
authenticate requests to the Google Cloud Storage. To view the entered key, click and hold the eye icon
on the right of the field. For more information on Google Cloud accounts, see the Google Cloud
documentation.

If you have not created the HMAC key beforehand, you can do one of the following :

o Create the HMAC key in the Google Cloud console, as described in the Google Cloud documentation.

o Create the HMAC key in the Veeam Backup for Google Cloud Platform Web UI, as described in the
Veeam Backup for Google Cloud User Guide.

552 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Description field, enter an optional description for the credentials record.

Google Cloud Platform Service Accounts


You can create a record for credentials that you plan to use to connect to Google Compute Engine within Google
Cloud Platform. This Google Cloud Platform service account is used by Veeam Backup & Replication to perform
direct restore to Google Compute Engine and backup and restore operations available with Google Cloud Plug -
in for Veeam Backup & Replication. For more information on the latter, see the Integration with Veeam Backup
for Google Cloud Platform Guide.

To create a credentials record for a Google Cloud Platform service account:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Click Ad d > Google Cloud Platform service account.

3. At the Ty p e step of the wizard, select if you want to create a new service account automatically or use an
existing service account.

NOTE

If you select Create a new service account, the created service account will be granted the Owner
IAM role with a wide scope of permissions and capabilities. If you want to limit the list of permissions
granted to the service account, create a user-managed service account, as described in the Google
Cloud documentation, with the limited set of permissions:

• For the information on permissions required to restore to Google Compute Engine, see Google
Compute Engine IAM User Permissions.
• For the information on permissions required to deploy GCP Plug -in for
Veeam Backup & Replication, see the Permissions section in the Integration with Veeam
Backup for Google Cloud Platform Guide.

553 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. At the Account step of the wizard, specify credentials required for accessing the service account:

o If you have selected Create a new service account, do the following:

i. Log into your Google Cloud account. Read and accept the Google Terms of Service and the
Google Privacy Policy.

ii. Allow Veeam Backup & Replication to access your Google account. After that,
Veeam Backup & Replication can manage your Identity and Access Management (IAM) policies,
and see, edit, configure and delete your Google Cloud Platform data.

554 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
iii. Return to the wizard and select the project with which you want the created service account to
work.

o If you have selected Use the existing service account , do the following:

i. Download the service account key in the JSON format, created as described in Google Cloud
documentation.

IMP ORTANT

Depending on the scenarios that the service account will be used for, make sure that the
service account meets all requirements and limitations.

For restoring virtual workloads from backups to Google Cloud, consider the requirements
and limitations listed in section Restore to Google Compute Engine.

555 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
ii. At the Account step of the wizard, select the downloaded service account key.

5. At the Summary step of the wizard, review details of the configured account and click Finish to close the
wizard.

Editing and Deleting Credentials Records


You can edit or delete existing cloud credentials records.

Editing Credentials
To edit a credentials record:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Select the credentials record in the list and click E d it.

3. Edit settings of the credentials record as required.

TIP

You can use the Cloud Credentials Manager to change the password for a tenant account provided by the
SP. For more information, see the Changing Password for Tenant Account section in the Veeam Cloud
Connect Guide.

556 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating New Google Service Account
If you created a Google Cloud Platform service account using the Create a new service account option, you may
need to create a new service account instead of the already created one. For example, the service account was
deleted.

To cretae a new service account, do the following:

1. Edit the necessary credential as described in the Editing Credentials section.

2. At the Account step, click the Log In link.

3. In the opened window, log into your Google Cloud account.

4. Back to the Goog le Cloud Platform Service Account wizard, click Finish.

Veeam Backup & Replication will create a new service account and will use it to communicate with Google Cloud
Platform.

Deleting Credentials
To delete a credentials record:

1. From the main menu, select Credentials and Passwords > Cloud Credentials.

2. Select the credentials record in the list and click Remove. You cannot delete a record that is already used
for any component in the backup infrastructure.

557 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Password Manager
You can use the Password Manager to create and maintain a list of passwords that you plan to use for data
encryption. Password management can be helpful in the following situations:

• You want to create new passwords. You can use one password per job or share the same password
between several jobs on the backup server.

• You want to edit an existing password, for example, change its hint, or delete a password.

TIP

Periodical change of passwords is a security best practice. You can create new passwords as often as you
need based on your company security needs and regulatory requirements.

Creating Passwords
You can use the Password Manager to create one or more passwords.

To create a new password:

1. From the main menu, select Credentials and Passwords > E ncryption Passwords. Alternatively, you can use
job properties to create a new password:

a. Open the Home view.

b. In the inventory pane, select Job s .

c. In the working area, right-click the backup or backup copy job and select E d it.

d. At the Storage step of the wizard (for backup job) or Ta rget step of the wizard (for backup copy job),
click Ad vanced.

e. Click the Storage tab.

f. In the E ncryption section of the Ad vanced Settings window, select the E na ble backup file encryption
check box and click the Ma nage passwords link.

Veeam Backup & Replication will open the Password Manager.

2. In the Password Manager, click Ad d .

3. In the Hint field, specify a hint for the created password. It is recommended that you provide a meaningful
hint that will help you recall the password. The password hint is displayed when you import an encrypted
file on the backup server and access this file.

4. In the P a ssword field, enter a password. The recommended minimum for the length of a password is 12
characters.

To view the entered password, click and hold the eye icon on the right of the field.

IMP ORTANT

Always save a copy of the password you create in a secure place. If you lose the password, you will not be
able to restore it.

558 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Passwords
You can edit passwords you have created using the Password Manager.

To edit a password:

1. From the main menu, select Credentials and Passwords > E ncryption Passwords. Alternatively, you can use
job properties to edit the password:

a. Open the Home view.

b. In the inventory pane, select Job s .

c. In the working area, right-click the backup or backup copy job and select E d it.

d. At the Storage step of the wizard (for backup job) or Ta rget step of the wizard (for backup copy job),
click Ad vanced.

e. Click the Storage tab.

f. In the E ncryption section of the Ad vanced Settings window, select the E na ble backup file encryption
check box and click the Ma nage passwords link.
Veeam Backup & Replication will open the Password Manager.

2. In the Password Manager, select the password and click E d it.

3. Edit the password data: hint and password, as required. The recommended minimum for the length of a
password is 12 characters.

After you edit the password, you do not need to perform any other actions. Veeam Backup & Replication will
start using the changed password after a job runs for the next time. Before the job run, the old password is still
used. For more information on which password to use when you restore data, see Restoring Data from
Encrypted Backups.

559 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Passwords
You can delete passwords using the Password Manager.

You cannot remove a password that is currently used by any job on the backup server. To remove such
password, you first need to delete a reference to this password in the job settings.

To delete a password:

1. From the main menu, select Credentials and Passwords > E ncryption Passwords. Alternatively, you can use
job properties to delete passwords:

a. Open the Home view.

b. In the inventory pane, select Job s .

c. In the working area, right-click the backup or backup copy job and select E d it.

d. At the Storage step of the wizard (for backup job) or Ta rget step of the wizard (for backup copy job),
click Ad vanced.

e. Click the Storage tab.

f. In the E ncryption section of the Ad vanced Settings window, select the E na ble backup file encryption
check box and click the Ma nage passwords link.

Veeam Backup & Replication will open the Password Manager.

2. In the Password Manager, select the password and click Remove.

560 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Key Management System Keys
Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), you can encrypt backup files with Key
Management System (KMS) keys based on an asymmetric key encryption algorithm. These keys are managed
and rotated by an external KMS server. This mechanism provides a more secure environment in comparison with
password-based keys which use a symmetric key encryption algorithm and are managed manually by the
administrator.

You can use KMS keys to encrypt backup files on the following encryption levels:

• Job-level encryption:

o Backup and backup copy jobs

o Veeam Agent backup jobs managed by Veeam Backup & Replication

o File backup jobs and object storage backup jobs

o Transaction log backup and backup copy jobs

o VeeamZIP jobs

NOTE

Consider that you can also use KMS keys for the following jobs if you use Veeam Cloud Connect
repositories as target backup storage:

o Backup and backup copy jobs


o Veeam Agent backup jobs managed by Veeam Backup & Replication
o Transaction log backup copy jobs

• Storage-level encryption:

o Backup repositories that store backup files created by:

▪ Veeam Backup for Nutanix AHV

▪ Veeam Backup for RHV

▪ Veeam Backup for Kasten K10

For more information, see Access Permissions.

o Capacity tier repositories

o Media pools and GFS media pools

o External repositories (decryption only)

IMP ORTANT

The following jobs and repositories do not support data encryption with KMS keys:

▪ Configuration backup jobs


▪ Veeam Agent backup jobs managed by Veeam Agents
▪ Backup repositories that store backup files created by Veeam Agents operating in the standalone
mode

561 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How KMS Works
When you add the KMS server in the Veeam Backup & Replication console and start using KMS keys for data
encryption, Veeam Backup & Replication asks the KMS server to generate an asymmetric KMS key for the
required job or repository. Public key is stored in the Veeam Backup & Replication configuration database and
used for data encryption. Private key is stored on the KMS server and us ed for data decryption.

Backup files encrypted with the KMS solution are decrypted automatically when you import them. You need to
decrypt backup files manually only in the following situations:

• You import backup files to a new Veeam Backup & Replication installation that is not connected to the
KMS server yet.

• You use VBK files to import backups. Also, a part of the backup chain is encrypted with the KMS solution,
the other part is encrypted with the password-based keys.

• On a new Veeam Backup & Replication installation, you run separate catalog jobs for tapes encrypted with
the KMS solution and tapes encrypted with password-based keys.

NOTE

If you have lost the KMS server, you can decrypt backup files with Veeam Backup Enter prise Manager. Note
that the encryption password loss protection must be enabled. For more information, see Managing
Encryption Keys in the Veeam Backup Enterprise Manager Guide.

The KMS server rotates KMS keys at a time interval specified in the KMS policies. To get updates from the KMS
server, Veeam Backup & Replication runs a specific system job. During the job session,
Veeam Backup & Replication performs the following steps:

1. Sends a request to the KMS server and gets information about recently rotated KMS keys if there are any.

2. Updates public keys in the Veeam Backup & Replication configuration database.

By default, the Veeam Backup & Replication system job runs every 24 hours. If you want to change the default
time period, contact Veeam Customer Support.

562 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
The KMS solution has the following requirements and limitations:

• Full KMS support is included only in the Veeam Data Platform Advanced or Premium License, or the
Enterprise Plus edition. Data decryption is available for all licenses.

• Veeam Backup & Replication works with the following KMS servers:

o Thales CipherTrust Manager k170v 2.10.0+7973 and later

o Fortanix Data Security Manager KMS 4.20.2274 and later (Public Cloud solution)

o IBM Security Guardium Key Lifecycle Manager (GKLM) 4.1.1.0 and later

NOTE

If you use another KMS server, make sure that it supports:

o Key Management Interoperability Protocol (KMIP) Profile v1.4 or earlier versions. Later
versions of KMIP Profiles are not supported by Veeam Backup & Replication.
o Requirements for a baseline server. For more information, see the Baseline Server section in
the KMIP Profile standard.
o Requirements for an asymmetric key lifecycle server. For more information, see the
Asymmetric Key Lifecycle Server section in the KMIP Profile standard.

• To decrypt data, the KMS server must support:

o Requirements for a basic cryptographic server. For more information, see the Basic Cryptographic
Server section in the KMIP Profile standard.

o SHA-1 hashing algorithm.

o Optimal Asymmetric Encryption Padding (OAEP).

In other cases, Veeam Backup & Replication will retrieve private keys from the KMS server to decrypt
backup files. These keys are not stored in the configuration database and deleted immediately after
decryption.

• [For Cloud Connect] To use the KMS solution in the Veeam Cloud Connect environment, both a service
provider and a tenant must run Veeam Backup & Replication 12.1 (build 12.1.0.2131) or later.

• [For Cloud Connect] If a tenant uses the same KMS server as a service provider, backup files st ored in
the tenant quota cannot be decrypted on the service provider side.

KMS Certificates
The KMS server certificate must meet the following requirements:

• If you use a server certificate in the PEM format, it must contain the -----BEGIN CERTIFICATE-----
header at the beginning of the file and the -----END CERTIFICATE----- footer at the end of the file.

• The Sub ject extension must be equal to the fully qualified domain name (FQDN) of the KMS server. For
example: kms.domain.local.

• The server certificate must have valid CRL distribution points specified in the CRL Distribution Points
extension.

563 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If the Veeam Backup & Replication server does not trust the Certificate Authority (CA) of the server
certificate, it should be added to the Trusted Root Certification Authority store.

The client certificate issued by the KMS administrator for Veeam Backup & Replication must be exportable.

Adding KMS Server


To add a KMS server, do the following:

1. From the main menu, select Credentials and Passwords > Key Management Servers.

2. In the Key Management Servers window, click Ad d .

3. In the Server field, specify the FQDN, IPv4 or IPv6 address of the server. By default, the port number
5696 is used.

4. In the Server certificate field, click Browse and specify a KMS server certificate. You can select one of the
following options:

a. Select an existing certificate from the certificate store. You can specify a KMS server certificate if it is
located in the Microsoft Windows certificate store.

b. Imp ort certificate from a file. You can import a KMS server certificate from a file in the PFX, CER, or
PEM format.

For more information about requirements that a server certificate must meet, see KMS Certificates.

5. In the Client certificate field, click Browse and specify the client certificate issued by the KMS
administrator for Veeam Backup & Replication. You can select one of the following options:

a. Select an existing certificate from the certificate store. You can specify a client certificate issued by
the KMS administrator for Veeam Backup & Replication if it is located in the Microsoft Windows
certificate store.

b. Imp ort certificate from a file. You can import a client certificate from a file in the PFX or CER format.

NOTE

If you use a PEM-encoded file, select the Imp ort certificate from a PEM file option.

c. Imp ort certificate from a PEM file . You can import a client certificate from a PEM-encoded file.
Consider the following:

▪ You must have two separate PEM files for the certificate and private key.

▪ The certificate must contain the -----BEGIN CERTIFICATE----- header at the beginning of
the file and the -----END CERTIFICATE----- footer at the end of the file.

564 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ The private key must be in the PKCS#1 format. Also, it must contain the -----BEGIN RSA
PRIVATE KEY----- header at the beginning of the file and the -----END RSA PRIVATE
KEY----- footer at the end of the file.

For more information about requirements that a client certificate must meet, see KMS Certificates.

6. [Optional] In the Description field, provide the description for future reference.

7. Click OK.

Using KMS Keys


To use KMS keys for data encryption, go to the backup job or storage settings and select the KMS server in the
P a ssword field. Note that If the KMS server is unavailable, the job session will fail.

565 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Locations
To control data migration in the virtual infrastructure, Veeam Backup & Replication introduces a notion of
location. A location defines a geographic region, or country, in which an infrastructure object resides. You can
create a list of locations, and assign to backup infrastructure objects information about locations to which they
belong.

Veeam Backup & Replication allows you to assign information about locations to the following infrastructure
objects:

• Virtual infrastructure objects: SCVMM, clusters and hosts.

• Backup infrastructure objects: backup repositories, external repositories, scale -out backup repositories,
tape libraries and tape vaults.

• Agent management objects: protection groups.

• Veeam Cloud Connect for service providers: cloud repositories and hardware plans.

Information about infrastructure objects location is stored in the Veeam Backup & Replication configuration
database. When VM data in the virtual infrastructure is migrated from one location to another,
Veeam Backup & Replication displays a warning and stores a record about data migration to job or task session
details. In addition to it, Veeam Backup & Replication logs this information to Microsoft Windows event logs. For
example, if you back up VMs from a host that resides in Germany to a backup repository that resides in Australia,
Veeam Backup & Replication will display a warning that VM data changes its location in the backup job wizard,
display information about data migration in the backup job session details and log it to Microsoft Windows event
logs.

566 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication displays information about VM and file share data migration in statistics for the
following types of jobs:

• Backup jobs — Veeam Backup & Replication compares the location of the source host on which VMs are
registered with the location of the target backup repository or cloud repository.

• Backup copy jobs — Veeam Backup & Replication compares the location of the source host with the
location of the target host.

• File backup jobs — Veeam Backup & Replication compares the location of the source file share with the
location of the target backup repository or cloud repository. If the secondary rep ository is specified,
Veeam Backup & Replication compares the location of the source file share with the location of the
secondary target host.

• VeeamZIP tasks (except the cases when you select to store the VeeamZIP file in a local or shared folder) —
Veeam Backup & Replication compares the location of the source host on which VMs are registered with
the location of the target backup repository.

• Replication jobs — Veeam Backup & Replication compares the location of the source host on which VMs are
registered with the location of the target host.

• Replica failback tasks — Veeam Backup & Replication compares the location of the source host with the
location of the host to which the VM is restored.

• File share backup copy tasks — Veeam Backup & Replication compares the location of the source file share
with the location of the target backup repository or target host.

• Entire VM restore tasks — Veeam Backup & Replication compares the location of the source host with the
location of the host to which VMs are restored.

• File share data recovery tasks — Veeam Backup & Replication compares the location of the source file
share with the location of the file share to which files are restored.

• External repository tasks:

o Backup copy jobs: Veeam Backup & Replication compares the location of the source external
repository with the location of the target backup repository.

o Restore to Amazon EC2: Veeam Backup & Replication compares the geographic region of the backed -
up Amazon EC2 instance with the geographic region of the target EC2 instance.

o Restore to Microsoft Azure: Veeam Backup & Replication always displays a warning about VM data
migration when restore to Microsoft Azure is performed from external repositories.

• SureBackup jobs — Veeam Backup & Replication compares the source location with the target location.
The target location is always a host on which the virtual lab is registered. The source location may be one
of the following:

o If a VM is added to the application group, Veeam Backup & Replication compares the host on which
the VM is registered (or was registered at the moment of backup) with the target location.

o If a VM is added to the SureBackup job from the linked job, Veeam Backup & Replication compares the
backup repository on which the backup file resides with the target location.

• Tape tasks:

o Backup to tape jobs: In backup to tape jobs, Veeam Backup & Replication compares the location of the
source job or repository with the location of the tape library in the target media pool. If the med ia
pool spans multiple tape libraries, Veeam Backup & Replication analyzes locations of all libraries in
the media pool.

567 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Vaults: If a tape job exports offline backups to a vault, Veeam Backup & Replication compares the
location of the source job or repository with the location of the vault. I a GFS tape job exports tapes to
multiple vaults, Veeam Backup & Replication analyzes all vaults configured for target media pools of
the GFS tape job.

o Media pools: Veeam Backup & Replication compares locations of all tape libraries added to the media
pool. If the media pool exports tapes to a vault, Veeam Backup & Replication analyzes all vaults
configured for the media pool.

Limitations for Locations


Veeam Backup & Replication does not display a warning about VM data migration for file copy jobs.

568 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating and Assigning Locations to
Infrastructure Objects
You can create a list of locations in Veeam Backup & Replication and assign locations to infrastructure objects. If
you assign a location to root infrastructure host (SCVMM), it will be applied to all child hosts (clusters and HV
Hosts). You can also assign the location to a child host.

To create a location:

1. In the Inventory or Ba ckup Infrastructure view, right-click the infrastructure object and select Loca tion >
Ma nage locations.

2. In the Ma nage Locations window, click Ad d .

3. In the Na me field, enter a name of the location.

To assign a location to an infrastructure object, in the Inventory or Ba ckup Infrastructure view, right-click the
infrastructure object and select Location > <Location name> . If the location is not in the list, select Loca tion >
Ma nage Locations and add the location to the list.

NOTE

When assigning a location to a scale-out backup repository, the location will be global for all extents. If
you add an extent whose location differs from the global location, it will be changed in favor of the
location of the scale-out repository.

569 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
570 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Locations
You can edit a location in the locations list, for example, if you want to change the location name.

To edit a location:

1. In the Inventory or Ba ckup Infrastructure view, right-click the infrastructure object and select Loca tion >
Ma nage locations.

2. In the Ma nage Locations window, select the location and click E d it.

3. In the Na me field, change the location name as required.

571 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Locations
You can delete a location from the locations list, for example, if you no longer host infrastructure objects in this
location.

To delete a location:

1. In the Inventory or Ba ckup Infrastructure view, right-click the infrastructure object and select Loca tion >
Ma nage locations.

2. In the Ma nage Locations window, select the location and click Remove. If the location is currently
assigned to some infrastructure objects, Veeam Backup & Replication will display a warning with the list of
objects that belong to this location. Click Y es to confirm the location deletion.

572 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Exporting and Importing Locations List
You can export and import the list of locations to/from a file of XML format.

The import and export functionality facilitates the process of locations creation and maintenance. For example,
if you need to set up the same list of locations throughout the whole backup infrastructure, you can create a list
of locations on one backup server manually, export this list to an XML file, and then import the list on other
backup servers and machines running the Veeam Backup & Replication console.

TIP

If you delete and recreate a location, Veeam Backup & Replication will create an object with a new ID in the
database and consider it as a new location. Thus, to preserve the uniqueness of the location, use the
location export/import operations.

To export the locations list:

1. In the Inventory or Ba ckup Infrastructure view, right-click an infrastructure object and select Location >
Ma nage locations.

2. In the Ma nage Locations window, click E x port and specify a name of the XML file to which the locations
list must be exported.

To import the locations list:

1. In the Inventory or Ba ckup Infrastructure view, right-click an infrastructure object and select Location >
Ma nage locations.

2. In the Ma nage Locations window, click Imp ort and browse to the XML file from which the locations list
must be imported.

573 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Network Traffic
Data protection requires large amount of data to be transferred through networks. This may cause heavy
network loads. Veeam Backup & Replication offers the following capabilities to manage network traffic and
reduce the load:

• Configuring Network Traffic Rules

• Managing Upload Streams

• Specifying Preferred Networks

• IPv6 Support

574 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Network Traffic Rules
Network traffic rules control traffic transferred between backup infrastructure components. These rules allow
you to do the following:

• Throttle network traffic

• Encrypt transferred data

The rules apply only to traffic sent between the backup infrastructure components, so you do not have to
change your network infrastructure.

How Network Rules Work


Each network rule contains IP address ranges for source and target components. When a job starts,
Veeam Backup & Replication checks the rules against the components involved in the job. If the IP addresses of
the components fall into the IP address ranges of a rule, the rule applies.

For example, 192.168.0.1–192.168.0.255 is the source range, and 172.16.0.1–172.16.0.255 is the target range.
192.168.0.12 is the IP address of one component, and 172.16.0.31 is the IP address of another component. Both
IP addresses fall into the ranges, so the rule will apply.

Note that the rules are reversible. The rule from the example will also apply to the specified components if you
swap the ranges: make 192.168.0.1–192.168.0.255 the target range and 172.16.0.1–172.16.0.255 the source
range.

NOTE

If the configured network rule covers at least one of the connection interfaces to a Veeam agent,
Veeam Backup & Replication applies network traffic throttling even if the traffic is transferred to/from this
Veeam agent through another interface.

TIP

You can define a rule for specific components. For this, specify a single IP address in the source range and
in the target range.

Creating Network Rules


You must create network rules at the backup server level. For details, see Enabling Traffic Throttling and
Enabling Data Encryption. Veeam Backup & Replication also has a predefined rule for traffic transferred
between public networks. For more information, see Adjusting Internet Rule.

After you create or edit network rules, they are applied almost immediately.

TIP

If you created a rule for an off-host backup proxy, you can check whether it applies. For this, open the
Traffic Rules step of the backup proxy wizard. The rule must be in the list of rules.

575 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adjusting Internet Rule
The internet rule is a predefined network rule. This rule manages traffic transferred through public networks —
all IPv4 networks whose IP ranges differ from 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and all IPv6 networks
whose IP ranges differ from fc00::/7. The internet rule also encrypts traffic for such networks. You cannot
delete the internet rule — you can only adjust or turn it off.

Turning Off Rule


To turn off the internet rule, clear the Throttle network traffic to and E ncrypt network traffic check boxes.

Adjusting Rule
To adjust the rule:

1. From the main menu, select Network Traffic Rules.

2. In the Global Network Traffic Rules window, select Internet from the list and click E d it.

3. In the E d it Network Traffic Rule window:

o To disable encryption, clear the E ncrypt network traffic check box.

o To enable network traffic throttling, select the Throttle network traffic to check box. For details, see
Enabling Traffic Throttling.

TIP

You can create custom network traffic rules targeted to public networks as described in section Enabling
Traffic Throttling.

576 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Enabling Traffic Throttling
Traffic throttling setting in a network rule allows you to limit the impact of Veeam Backup & Replication tasks
on network performance. Traffic throttling prevents jobs from utilizing the entire bandwidth available in your
environment and makes sure that other network operations get enough traffic.

When several jobs that fall into the same network rule run simultaneously, Veeam Backup & Replication equally
splits the throttled traffic between them. For example, if two jobs run at a time, each job gets half of the
throttled traffic. Once one job finishes, the other gets the entire ba ndwidth allowed by the rule.

NOTE

Consider the following:

• Traffic can be throttled only if the infrastructure components are located on different servers. For
example, if you use the same server as a backup proxy and a backup repository, traffic throttling
rules do not apply to them.
• It is recommended that you throttle network traffic if you perform off-site backup or replicate VMs
to a DR site over slow WAN links.
• Traffic throttling rules apply to the transfer of virtual disks. At the beginning of the job, you may see
bandwidth usage peaks caused by transferring other VM files.

577 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Infrastructure Components
Traffic can be throttled between the backup infrastructure components on which Veeam Data Movers are
deployed, also capacity tier of the scale-out backup repository and object storage repository. The components
differ depending on a data protection scenario. The following table shows this dependency.

Scenario Comp onents

Backup to a Microsoft Windows or Linux Backup proxy (onhost or offhost) and backup repository
backup repository*

Backup to an SMB share, Dell Data Domain Backup proxy (onhost or offhost) and gateway server.
and HPE StoreOnce*

Backup copy* Source and target backup repositories, gateway servers or WAN
accelerators (if they are involved in the backup copy process).

Replication Source and target backup proxies (onhost or offhost) or WAN


accelerators (if they are involved in the replication process).

Backup to tape* Backup repository and tape server. For more information about
backup to tape jobs, see the Machines Backup to Tape section
in the Veeam Backup & Replication User Guide.

SOBR data offload Gateway server and object storage repository.

* Veeam Backup & Replication throttles traffic between the listed components also if backups are created with Veeam
Agents (Windows, Linux and so on) operating in the standalone or managed mode.
** Veeam Backup & Replication throttles traffic for all object storage repositories. For on -premises object storage
repositories Veeam Backup & Replication uses network rules.

Configuring Traffic Throttling


To configure traffic throttling settings in a rule:

1. From the main menu, select Network Traffic Rules.

2. In the Global Network Traffic Rules window, click Ad d and select an IPv4 or IPv6 rule. Note that you can
add the IPv6 rule only if IPv6 communication is enabled as descried in IPv6 Support.

3. In the Na me field, specify a name for the rule.

4. In the Source IP address range section, specify a range of IP addresses for the backup infrastructure
components on the source site.

5. Specify ranges of IP addresses on the target site:

o To specify IP addresses of the backup infrastructure components, use the Ta rget IP address range
section.

578 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To throttle traffic to public networks, select the All public IP addresses check box. Public networks
are all IPv4 networks whose IP ranges differ from 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and all
IPv6 networks whose IP ranges differ from fc00::/7.

6. Select the Throttle network traffic to check box.

7. In the Throttle network traffic to field, specify the maximum speed that must be used to transfer data
from source to target.

8. If you want to throttle traffic during the restore activities, clear the Never throttle any restore activity
check box.

9. In the section below the Throttle network traffic to field, specify time periods when traffic is throttled:

o Select the All the time option if traffic throttling rules must be applied continuously.

o Select During the specified time periods only and use the diagram below to mark the periods when
the traffic must be throttled or not. Use the Unthrottle to field to increase or decrease the throttling
limit for specific hours and days.

Several Rules with Traffic Throttling


If you create several rules with the same ranges of IP addresses, make sure that time intervals of the rules do
not overlap. For example, to manage network traffic during business and non-business hours, you can create the
rules as shown below. These rules have the same ranges of IP addresses.

• Rule 1. Speed limit: 1 Mbps; time interval: Monday through Friday from 7 AM to 7 PM.

• Rule 2. Speed limit: 10 Mbps; time interval: Saturday through Sunday from 7 AM to 7 PM.

With such rules, Veeam Backup & Replication will limit the speed up to 1 Mbps during business hours and up to
10 Mbps during non-business hours.

579 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If several rules have the same target/source IP address range but different speed limits, the lowest limit is used.
For example, if you configure the following rules:

• Rule 1. Source IP range: 192.168.0.1–192.168.0.30; target IP range: 192.168.0.1–192.168.0.255; speed


limit: 4 Mbps.

• Rule 2. Source IP range: 192.168.0.1–192.168.0.255; target IP range: 192.168.0.1–192.168.0.255; speed


limit: 1 Mbps.

In this case, Veeam Backup & Replication will use the lowest speed limit — 1 Mbps.

The principle of several rules and the lowest speed limit also applies if some rules are created on the
Veeam Backup & Replication side and others on the Veeam Agent for Microsoft Windows side. For more
information on how to throttle traffic by Veeam Agent for Microsoft Windows, see the Veeam Agent
Management Guide and Veeam Agent for Microsoft Windows User Guide.

Enabling Traffic Encryption


By default, Veeam Backup & Replication encrypts network traffic transferred between public networks. For
details, see Adjusting Internet Rule.

Network rules also allow you to encrypt backup data transfer connections between Ve eam Data Movers in
private networks. Network traffic encryption is provided by TLS connection and configured as the part of global
network traffic rules that are set for backup infrastructure components.

NOTE

Veeam Plug-ins for Enterprise Applications do not support traffic encryption.

For more information about supported TLS versions and cipher suites, see Encrypted Communication in the
System Requirements section.

To create a network rule with traffic encryption:

1. From the main menu, select Network Traffic Rules.

2. In the Na me field, specify a name for the rule.

3. In the Global Network Traffic Rules window, click Ad d and select an IPv4 or IPv6 rule. Note that you can
add the IPv6 rule only if the E na ble IPv6 communication check box is selected. For more information, see
IPv6 Support.

4. In the Source IP address range section, specify a range of IP addresses for backup infrastructure
components on the source site.

5. In the Ta rget IP address range section, specify a range of IP addresses for backup infrastructure
components on the target site.

580 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Select the E ncrypt network traffic check box.

NOTE

If encryption is enabled on a backup job level, backup data will be encr ypted before sending. For more
information, see Storage Settings.

Related Topics
Data Encryption

581 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Upload Streams
By default, Veeam Backup & Replication uses multithreaded data transfer for every job session. VM data going
from source to target is transferred over 5 TCP/IP connections. However, if you schedule several jobs to run at
the same time, load on the network may be heavy. If the network capacity is not sufficient to support multiple
data transfer connections, you can disable multithreaded data transfer or change the number of TCP/IP
connections.

To change the number of connections:

1. From the main menu, select Network Traffic Rules.

2. In the Global Network Traffic Rules window, specify new data transfer settings:

o To disable multithreaded data transfer, clear the Use multiple upload streams per job check box.
Veeam Backup & Replication will use only one TCP/IP transfer connection for every job session.

o To change the number of TCP/IP connections, leave the Use multiple upload streams per job check
selected and specify the necessary number of connections in the field on the right.

NOTE

Consider the following:

• Veeam Backup & Replication performs a CRC check for the TCP traffic going between the source and
the target. When you perform backup and replication operations, Veeam Backup & Replication
calculates checksums for data blocks going from the source. On the target, it recalculates
checksums for received data blocks and compares them to the checksums created on the source. If
the CRC check fails, Veeam Backup & Replication automatically re-sends data blocks without any
impact on the job.
• [For Veeam Plug-ins for Enterprise Applications] The multithreaded data transfer setting does not
affect backup jobs created by Veeam Plug-in for Oracle RMAN/SAP HANA/SAP on Oracle. To
configure multiple channels for backup and restore operations for these plug -ins, see the Veeam
Plug-ins for Enterprise Applications Guide.

582 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Preferred Networks
You can choose networks over which Veeam Backup & Replication must transport data when you perform data
protection and disaster recovery tasks. This option can be helpful if you have a non-production network and
want to route data traffic over this network instead of the production one.

Preferred network rule applies only to traffic between the following backup infrastructure compone nts:

• Backup server

• WAN accelerator 1

• Gateway server 2

• Off-host backup proxy***

• Microsoft Hyper-V Server3

• Backup repository

• Log shipping server

• Tape server

• Veeam Agent

• Veeam Plug-ins for Enterprise Applications


1
The rule applies only to traffic between the source and target WAN accelerators.
2
The rule does not apply to traffic between the gateway server and backup repository. For the list of backup repositories
with which the gateway server communicates, see Gateway Server.
3
If you need to specify IP ranges other than ranges received by automatic DNS resolution, you need to use a registry value.
For more information, see this Veeam KB article.

To define networks for data transfer, you must create a list of preferred networks. When
Veeam Backup & Replication needs to transfer data, it uses networks from this list. If a connection over
preferred networks cannot be established for some reason, Veeam Backup & Replication will automatically fail
over to the production network.

To set a network priority list:

1. From the main menu, select Network Traffic Rules.

2. In the Global Network Traffic Rules window, click Networks.

3. In the P referred Networks window, select the P refer the following networks for backup a nd replication
tra ffic check box.

4. Click Ad d and select IPv4 or IPv6 network. Note that you can add the IPv6 network only if the E nable IPv6
communication check box is selected. For more information, see IPv6 Support.

583 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. [For the IPv4 network] Specify a network address and a subnet mask using a CIDR notation and click OK.

6. [For the IPv6 network] Specify a network address and prefix length using a CIDR nota tion and click OK.

7. Repeat steps 4-6 for all networks that you want to add.

584 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IPv6 Support
Veeam Backup & Replication supports IPv6 communication for all backup infrastructure components. The
following options are available:

• IP v4/IPv6 dual stack. This mode is enabled by default for new Veeam Backup & Replication installations.

• IP v4 only. For compatibility, this mode is used by default if you upgrade to Veeam Backup & Replication
12.

NOTE

Temporary IPv6 addresses are not supported for backup infrastructure components and backed -up
machines. For more information about using temporary addresses, see this RFC section.

To manage IPv6 communication, perform the following steps:

1. From the main menu, select Network Traffic Rules.

2. Click Networks.

3. To enable the IPv4/IPv6 dual stack mode, select the E na ble IPv6 communication check box. To enable the
IPv4 only mode, clear the check box.

After you enable IPv6 communication, you can add backup infrastructure components with IPv6 addresses to
the Veeam Backup & Replication console and configure IPv6 networks and traffic rules. You can use any text
representation format of the IPv6 address, although RFC 5952 describes the canonical format as recommended.
For more information, see this RFC section.

Note that if you want to switch back to the IPv4 only mode, you must remove backup infrastructure
components added only with IPv6 addresses from the Veeam Backup & Replication console.

NOTE

If you use the IPv4/IPv6 dual stack mode and there are backup infrastructure components added to the
Veeam Backup & Replication console using FQDN, Microsoft Windows itself determines which source
address and the network protocol (IPv4 or IPv6) will be used for connection between
Veeam Backup & Replication and these components. For more information, see this Microsoft article.

This case is also applied to your backup infrastructure if you use Kerberos authentication. For more
information, see Kerberos Authenticaiton.

585 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Logs
Veeam Backup & Replication provides detailed logging of performed activities, data protection and disaster
recovery tasks.

Logs are stored on the backup server and all servers added to the backup infrastructure:

• On the backup server logs are stored in the following folders:

o Installation and upgrade logs - the %ProgramData%\Veeam\Setup\Temp folder.

o Logs for the Veeam Backup & Replication console and other user specific logs - the
%UserProfile%\AppData\Local\Veeam\Backup folder.

o Logs for jobs, components and services - the %ProgramData%\Veeam\Backup folder.


Veeam Backup & Replication creates separate folders for jobs and also separate log files or folders
for components and services.

o Logs for PowerShell cmdlets - the


%UserProfile%\AppData\Local\Veeam\Backup\VeeamPowerShell.log file.

• On Linux servers, logs are stored in the /var/log/VeeamBackup or /tmp/VeeamBackup directory.

• On Microsoft Windows servers and Hyper-V hosts, logs are stored in the
%ProgramData%\Veeam\Backup folder.

TIP

You can change default log files settings, for example, logs location and size. For more information, see
this Veeam KB article.

To collect log files from the backup server and servers managed by Veeam Backup & Replication, use the E x port
Log s wizard as described in section Exporting Logs.

586 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Exporting Logs
You can use log files to submit a support ticket. It is recommended that you send all log files when submitting a
support ticket to ensure that overall and comprehensive information is provided to Veeam Support Team.

To aggregate all log files in the same location, use the E x port Logs wizard. To launch the wizard, from the main
menu select Help > Support Information.

587 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Select Virtual Infrastructure Scope
At the Scop e step of the wizard, define the scope for logs export. You can export logs for the following objects:

• Specific jobs on the backup server

• Specific objects (VMs, physical machines, CDP clusters, backups)

• Specific components in the backup infrastructure

NOTE

If you export logs from the Veeam Backup & Replication console, the exported logs will be copied to the
machine where the console is installed. The log archive will also contain logs from the console machine.

TIP

To select multiple jobs or objects in one bundle, do one of the following:

• Hold [Ctrl] and click items to add to your selection.


• Hold [Shift] and select a range of items between the currently selected item and the one you click.

588 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Time Interval
At the Da te Range step of the wizard, define the time interval for which logs must be collected. You can select
one of the following options:

• Collect logs for the last N days

• Collect all available logs

589 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Destination Folder
At the Loca tion step of the wizard, specify the destination folder to which the logs will be exported.

In the P a th to folder field, specify a path to an archive with log files that will be created. By default, the archive
is placed to the C:\temp\logs folder on the backup server.

590 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Results
At the E x p ort step of the wizard, Veeam Backup & Replication will collect specified logs and create a log
archive. Wait for the export process to complete, review the results and click the Op en folder link to browse to
exported log files and log package.

TIP

During the log export process, Veeam Backup & Replication locks the console, so you cannot close the
E x port Logs wizard. If you do not want to wait until the log export process completes, you can run another
session of the Veeam Backup & Replication concurrently and continue work with it.

591 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Global VM Exclusions
Global VM exclusion allows you to stop processing VMs even if they are included in jobs. When excluding VMs
globally, you do not need to change job settings. Global exclusion applies to all types of jobs that process VMs
except backup copy jobs and SureBackup jobs. Note that if Veeam Backup & Replication has started to process a
VM at the moment when you exclude the VM from processing, Veeam Backup & Replication finishes processing
and only then excludes the VM.

At any moment, you can enable processing of VMs so that jobs will continue processing the VMs.

IMP ORTANT

Note that you can only exclude VMs from processing. It is not possible for tags or folders.

Excluding VMs from Processing


To exclude VMs globally, do the following:

1. From the main menu, select VM E x clusions.

2. In the VM E x clusions window, click Ad d and select the required platform.

3. In the Ad d Objects window, select VMs that you want to exclude from processing. Click OK.

4. If you want to add a note why a VM is excluded from processing, select a VM from the list and click Note.
In the E d it Note window, enter the note text. Click OK.

Alternatively, you can open the Inventory view and switch to the required view. In the working area, select the
VMs that you want to exclude, right-click one of them and select Disable processing. In the Inventory view, VMs
excluded from processing will be displayed with the icon.

Resuming VM Processing
To resume processing for VMs, do the following:

1. From the main menu, select VM E x clusions.

2. In the VM E x clusions window, select VMs for which you want to resume processing.

3. Click Remove.

592 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you can open the Inventory view and switch to the required view. In the working area, select the
VMs that were excluded from processing, right-click one of them and select Disable processing.

593 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Infrastructure Components
Veeam Backup & Replication is a modular solution that lets you build a scalable backup infrastructure for
environments of different sizes and configuration. The installation package of Veeam Backup & Replication
includes a set of components that you can use to configure the backup infrastructure. Some components are
mandatory and provide core functionality; some components are optional and can be installed to provide
additional functionality for your business and deployment needs.

You can co-install Veeam Backup & Replication components on the same machine, physical or virtual, or you can
set them up separately for a more scalable approach. Some components can be deployed with the help of the
setup file. Other components can be deployed using the Veeam Backup & Replication console.

594 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Server
The backup server is a Windows-based physical or virtual machine on which Veeam Backup & Replication is
installed. It is the core component in the backup infrastructure that fills the role of the “configuration and
control center”. The backup server performs all types of administrative activities:

• Coordinates backup, replication, recovery verification and restore tasks.

• Controls job scheduling and resource allocation.

• Is used to set up and manage backup infrastructure components as well as specify global settings for the
backup infrastructure.

In addition to its primary functions, a newly deployed backup server also performs the role of the default
backup repository, storing backups locally.

595 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup & Replication Console
The Veeam Backup & Replication console is a client-side component that provides access to the backup server.
The console allows you to log in to Veeam Backup & Replication and perform all kinds of data protection and
disaster recovery operations on the backup server.

To connect to the backup server, the Veeam Backup & Replication console uses Simple and Protected GSS-API
Negotiation Mechanism (SPNEGO), the Microsoft Windows built-in authentication mechanism. SPNEGO
supports both NTLM and Kerberos authentication.

NOTE

Using NTLM increases the attack surface of your backup infrastructure. To build a more secure
environment, disable NTLM and leave Kerberos the only domain authentication protocol. For more
information, see Kerberos Authentication.

The console does not have a direct access to the backup infrastructure components and configuration database.
Such data as user credentials, passwords, roles and permissions are stored on the backup server side. User
credentials and passwords are stored in the configuration database encrypted with Data Protection API (DPAPI)
mechanisms. To access the data, the console connects to the backup server and queries this information
periodically during the work session.

To make users work as uninterrupted as possible, the remote console maintains the session for 5 minutes if the
connection is lost. If the connection is re-established within this period, you can continue working without re-
logging to the console.

Backup & Replication Console Deployment


The console is installed locally on the backup server by default. You can also use it in a standalone mode —
install the console on any machine and access Veeam Backup & Replication remotely over the network.

You can install as many remote consoles as you need so that multiple users can access
Veeam Backup & Replication simultaneously. Veeam Backup & Replication prevents concurrent modifications on
the backup server. If several users are working with Veeam Backup & Replication at the same time, the user who
saves the changes first has the priority. Other users will be prompted to reload the wizard or window to get the
most recent information about the changes in the configuration database.

If you have multiple backup servers in the infrastructure, you can connect to any of them from the same
console. For convenience, you can save several shortcuts for these connections.

IMP ORTANT

You cannot use the same console to connect to backup servers with different versions of
Veeam Backup & Replication. Note this if you have more than one backup server in your backup
environment, and these backup servers run different versions of Veeam Backup & Replication. For example,
if one of your backup servers run version 9.5 Update 3, and another backup server runs version 9.5 Update
4, you will need to use 2 separate consoles for connecting to these servers.

The console supports automatic update. Every time you connect to the backup server locally or remotely, the
console checks for updates. If the backup server has updates installed, the console will be updated
automatically.

596 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Consider the following:

• Upgrade to another Veeam Backup & Replication major product version is supported starting from
Veeam Backup & Replication version 11a (build 11.0.1.1261). For example, if your console ha s this version,
you can upgrade it automatically upon connecting to the Veeam backup server version 12 (build
12.0.0.1420). Automatic upgrade is not supported for Preview, Beta or RTM versions of
Veeam Backup & Replication.

• Downgrade of the console is not supported. If the console is of a higher version than the backup server
(for example, you have upgraded the console manually), the connection to the server will fail.

If other Veeam Backup & Replication components, such as Veeam Cloud Connect Portal or Veeam Backup
Enterprise Manager, are installed on the machine where the console runs, these components will also be
upgraded.

Backup & Replication Console Components


When you install a remote console on a machine, Veeam Backup & Replication installs the following
components:

• Veeam Backup PowerShell Module

• Veeam Explorer for Microsoft Active Directory

• Veeam Explorer for Microsoft Exchange

• Veeam Explorer for Microsoft OneDrive for Business

• Veeam Explorer for Microsoft SharePoint

• Veeam Explorer for Microsoft SQL Server

• Veeam Explorer for Microsoft Teams

• Veeam Explorer for Oracle

• Veeam Explorer for PostgreSQL

• Veeam Data Mover Service

• Veeam Explorers Recovery Service

• Veeam Installer Service

• Veeam Mount Service

Backup & Replication Console User Access Rights


To log in to Veeam Backup & Replication using the console, the user must be added to the Local Users group on
the backup server or a group of domain users who have access to the backup server. The user can perform the
scope of operations permitted by his or her role in Veeam Backup & Replication. For more information, see Users
and Roles.

Requirements for Backup & Replication Console


A machine on which you install the Veeam Backup & Replication console must meet the following requirements:

• The machine must meet the system requirements. For more information, see System Requirements.

597 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The remote console can be installed on a Microsoft Windows machine (physical or virtual) .

• If you install the console remotely, you can deploy it behind NAT. However, the backup server must be
outside NAT. The opposite type of deployment is not supported: if the backup server is deployed behind
NAT and the remote console is deployed outside NAT, you will not be able to connect to the backup
server.

Limitations for Backup & Replication Console


The Veeam Backup & Replication console has the following limitations:

• You cannot perform restore from the configuration backup using the remote consol e.

• The machines on which the remote console is installed are not added to the list of managed servers
automatically. For this reason, you cannot perform some operations, for example, import backup files that
reside on the remote console machine or assign roles of backup infrastructure components to this
machine. To perform these operations, you must add the remote console machine as a managed server to
Veeam Backup & Replication. For more information, see Managing Servers.

598 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication Configuration
Database
Veeam Backup & Replication Configuration Database stores data about the backup infrastructure, jobs, sessions
and other configuration data. The database instance can be located on a SQL Server installed eithe r locally (on
the same machine where the backup server is running) or remotely.

Veeam Backup & Replication maintains the configuration database. Veeam Backup & Replication runs the
DatabaseMaintenance system job once a week and when the Veeam Backup Service is restarted. The job updates
the database internal statistics, defragments indexes and clears unused data. For details, see the
Job.DatabaseMaintenance.log file in the %ProgramData%\Veeam\Backup folder.

599 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Configuration Database
You can back up and restore the configuration database that Veeam Backup & Replication uses. If the backup
server fails for some reason, you can re-install the backup server and quickly restore its configuration from the
configuration backup. You can also use configuration backups to apply the configuration of one backup server to
another backup server in the backup infrastructure. During configuration backup, Veeam Backup & Replication
exports data from the configuration database and saves it to a backup file in the backup repository.

NOTE

If you use cloud plug-ins to protect VMs in Google Cloud, AWS and other environments, you can also back
up configurations of cloud backup appliances. To back up the configurations, you must enable encryption
as described in section Creating Encrypted Configuration Backups.

For more information on appliance configuration backup and restore, see the following guides:

• Integration with Google Cloud Plug-in for Veeam Backup & Replication, the Performing
Configuration Backup and Restore section.
• Integration with Veeam Backup for AWS, the Performing Configuration Backup and Restore section.
• Integration with Veeam Backup for Microsoft Azure, the Performing Configuration Backup and
Restore section.

It is recommended that you regularly perform configuration backup for every backup server in the backup
infrastructure. Periodic configuration backups reduce the risk of data loss and minimize the administ rative
overhead if any problem with backup servers occurs.

NOTE

If you have a hardened repository in your backup infrastructure, you must enable data encryption for
configuration backup. Otherwise, you cannot perform configuration backups. For more information, see
Creating Encrypted Configuration Backups.

Do not back up the backup server configuration using backup jobs in Veeam Backup & Replication. For backup,
Veeam Backup & Replication uses VM snapshots. During snapshot creation and commit, the VM freezes for some
time, which can potentially lead to the following consequences:

• Disconnection from the configuration database. For more information, see the Veeam KB1681 article.

• Disconnection from remote Veeam Backup & Replication agents.

• Disconnection from network storage (for example, storage presented through iSCSI) and so on.

For this reason, you must always use the configuration backup functionality to back up and restore configuration
of the backup server.

Creating Configuration Backups


By default, Veeam Backup & Replication creates a configuration backup daily. You can change the schedule or
create a configuration backup manually. You can choose the backup repository in which the configuration
backup must be stored, specify the necessary retention settings. Starting from version 12.1 (build 12.1.0.2131),
Veeam Backup & Replication allows you to create immutable configuration backups.

For more information on managing configuration backup, see the following topics:

• Scheduling Configuration Backups

600 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Configuring Notification Settings for Configuration Backups

• Running Configuration Backups Manually

• Creating Encrypted Configuration Backups

• Creating Immutable Configuration Backups

Configuration Backup Files


When you perform configuration backup, Veeam Backup & Replication retrieves data for the backup server from
the configuration database, writes this data into a set of XML files and archives these XML files to a backup file
of the BCO format.

Veeam Backup & Replication exports information about the following objects:

• Ba ckup infrastructure components and objects: hosts, servers, backup proxies, repositories, WAN
accelerators and jobs, global settings configured on the backup server and so on.

• Ba ckups: backups, replicas and backup copies created on the backup server.

• Sessions: job sessions performed on the backup server.

• Ta p es: tape libraries connected to the backup server.

NOTE

Consider the following:

• If you use custom configuration registry values, note that configuration backup will not apply to
them. You may want to back them up manually.
• The configuration backup job creates a snapshot of the configuration database and retrieves data
required for successful restore from it. If the database size is large, the job may produce significant
load on the Microsoft SQL Server. Make sure that you schedule the configuration backup job for a
period of low operation intensity on the backup server.

Backup Repository Target


The resulting configuration backup file is stored in the \VeeamConfigBackup\%BackupServer% folder on
the default backup repository. However, for security sake, it is recommended that you do not store
configuration backups on the default backup repository or in any other folder on the backup server. In this case,
if the backup server fails, its configuration data will remain, and you will be able to recover the failed backup
server.

When you configure a new backup repository, Veeam Backup & Replication offers you to change the
configuration backup file location from the default backup repository to the new backup repository. Click Y es ,
and Veeam Backup & Replication will automatically change the backup target in the configuration backup job
settings and will use this target in future.

Configuration backups that were created before the target change will remain in the default backup repository.
You can manually copy them to the new backup repository to have all restore points of the configuration backup
in one place.

IMP ORTANT

You cannot store configuration backups in scale-out backup repositories.

601 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Scheduling Configuration Backups
You can instruct Veeam Backup & Replication to perform configuration backup automatically by schedule.

IMP ORTANT

If you plan to migrate configuration data to the database used by another backup server, stop all running
jobs and disable scheduled jobs before creating the configuration backup. In the opposite case, job sessions
may be failing after configuration restore. For more information, see Migrating Configuration Database.

To schedule a configuration backup:

1. From the main menu, select Configuration Backup.

2. Make sure that the E na ble configuration backup to the following repository check box is selected.

3. From the Ba ckup repository list, choose a backup repository on which the configuration backup must be
stored.

4. In the Restore points to keep field, specify the number of restore points that you want to maintain in the
backup repository.

5. Click Schedule next to the P erform backup on field and specify the time schedule according to which the
configuration backup must be created.

6. To create an encrypted backup, select the E na ble configuration backup file encryption check box. From
the P a ssword drop-down list, select a password you want to use for encryption. If you have not created a
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For more
information, see Creating Encrypted Configuration Backups.

Configuring Notification Settings for Configuration Backups


You can configure notifications for the configuration backup:

1. From the main menu, select Configuration Backup.

602 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Click Notifications.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully.

SNMP traps will be sent if you specify global SNMP settings in Veeam Backup & Replication and configure
software on recipient's machine to receive SNMP traps. For more information, see Specifying SNMP
Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications about the job completion status by email. In the field below, specify recipient’s email
address. You can enter several addresses separated by a semicolon.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Configuring Global Email Notification Settings.

5. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for the job, select Use custom notification settings specified below
check box. You can specify the following notification settings:

i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %JobResult%, %JobName%, %Time% (completion time).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive
email notification if the job completes successfully, fails or completes with a warning.

Running Configuration Backups Manually


You can create a configuration backup manually when you need it, for example, if you want to capture a state of
the configuration database at a specific point in time.

IMP ORTANT

If you plan to migrate configuration data to the database used by another backup server, stop all running
jobs and disable scheduled jobs before creating the configuration backup. In the opposite case, job sessions
may be failing after configuration restore. For more information, see Migrating Configuration Database.

603 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To create a configuration backup manually:

1. From the main menu, select Configuration Backup.

2. Make sure that the E na ble configuration backup to the following repository check box is selected.

3. From the Ba ckup repository list, choose a backup repository on which the configuration backup must be
stored.

4. In the Restore points to keep field, specify the number of restore points that you want to maintain in the
backup repository.

5. To create an encrypted backup, select the E na ble backup file encryption check box. From the P a ssword
field, select a password you want to use for encryption. If you have not created a password beforehand,
click Ad d or use the Ma nage passwords link to specify a new password. For more information, see Creating
Encrypted Configuration Backups.

6. Click Ba ckup now.

Veeam Backup & Replication will back up the configuration database and store a new restore point to the
selected backup repository. The resulting configuration backup file (.BCO) is stored in the
\VeeamConfigBackup\%BackupServer% folder on the repository you have selected. The file name contains
the date when the configuration backup was performed.

Creating Encrypted Configuration Backups


Veeam Backup & Replication requires that you encrypt the configuration backup if you have created at least one
password in the Password Manager on the backup server.

When you encrypt jobs or tapes with passwords, Veeam Backup & Replication creates a set of keys that are
employed in the encryption process. Some encryption keys, for example, storage keys and metakeys, are s tored
in the configuration database. If a configuration backup was non-encrypted, data from it could be freely
restored on any backup server. Encryption keys saved to the configuration database and the content of
encrypted files may become accessible for unintended audience.

604 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If the Password Manager contains at least one password, and you do not enable encryption for the configuration
backup, Veeam Backup & Replication disables configuration backup. To enable the configuration backup, you
must enable encryption in the configuration backup job settings.

After you enable the encryption option, Veeam Backup & Replication will create encrypted configuration
backups. Beside encryption keys, the created backups capture credential records specified in the Credenti als
Manager. When you restore data from such backup, you will not have to enter passwords for credentials records
again (unless the passwords for credentials records have changed by the time of restore).

To encrypt the configuration backup:

1. From the main menu, select Configuration Backup.

2. Select the E na ble backup file encryption check box.

3. From the P a ssword field, select a password you want to use for encryption. If you have not created a
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For more
information, see Managing Passwords for Data Encryption.

NOTE

If you enable encryption and use cloud plug-ins to protect VMs in Google Cloud, AWS and other
environments, Veeam Backup & Replication will also create backups for cloud backup appliances. For more
information on appliance configuration backup and restore, see the following guides:

• Integration with Google Cloud Plug-in for Veeam Backup & Replication, the Performing
Configuration Backup and Restore section.
• Integration with Veeam Backup for AWS, the Performing Configuration Backup and Restore section.
• Integration with Veeam Backup for Microsoft Azure, the Performing Configuration Backup and
Restore section.

605 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Immutable Configuration Backups
NOTE

This feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

Veeam Backup & Replication allows you to keep configuration backups on object storage repositories that
support immutability. Immutability makes data temporarily immutable and prohibits deletion of configuration
backups from object storage repositories. Therefore, it protects your data against loss as a result of attacks,
malware activity or any other injurious actions.

IMP ORTANT

The version of Veeam Backup & Replication installed on a backup server for a Service Provider and a tenant
must be 12.1 (build 12.1.0.2131). Otherwise, the configuration backup stored on an object storage
repository will not be immutable.

Retention Policy for Immutable Configuration Backups


By default, object storage repositories keeps the number of restore points that you define in the configuration
backup settings. In case, a total number of restore point exceeds the retention policy settings,
Veeam Backup & Replication deletes the oldest restore point. If you keep configuration backups on immutable
object storage repositories, Veeam Backup & Replication will not delete the older restore points. Instead, it will
mark them as immutable and will keep them on object storage repositories until immutability period passes.

Creating Immutable Configuration Backups


To make configurations backups immutable, perform the following steps:

1. Configure an object storage repository where you will keep configuration backups. For more information,
see Immutability for Object Storage Repositories.

2. From the main menu, select Configuration Backup.

606 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Make sure that the E na ble configuration backup to the following repository check box is selected.

4. From the Ba ckup repository list, choose an object storage repository on which the configuration backup
must be stored.

5. In the Restore points to keep field, specify the number of restore points that you want to maintain in the
object storage repository.

6. To create an encrypted backup, select the E na ble backup file encryption check box. From the P a ssword
field, select a password you want to use for encryption. If you have not created a password beforehand,
click Ad d or use the Ma nage passwords link to specify a new password. For more information, see Creating
Encrypted Configuration Backups.

7. Click Ba ckup now.

Restoring Configuration Database


Restore of the configuration database is helpful in the following situations:

• The configuration database got corrupted and you want to recover data from the configuration backup.

• You want to deploy the configuration database on a new Microsoft SQL Server or PostgreSQL and restore
data from the configuration backup to it.

• You want to roll back the configuration database to a specific point in time.

• You want to restore data to a new configuration database on the same database instance, for example, for
testing purposes.

You can restore a configuration backup on the same backup server where the backup was created or on another
backup server.

607 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you use cloud plug-ins to protect VMs in Google Cloud, AWS and other environments and want to restore
cloud backup server configurations, see the following guides:

• Integration with Google Cloud Plug-in for Veeam Backup & Replication, the Configuration Restore
section.
• Integration with Veeam Backup for AWS, the Configuration Restore section.
• Integration with Veeam Backup for Microsoft Azure, the Configuration Restore section.

Before you start the restore process, check prerequisites. Then use the Veea m Backup & Replication
Configuration Restore wizard to restore the configuration database.

Before You Begin


Before you start the restore process, check the following prerequisites:

• Make sure the user, who initiates the backup configuration restore process, has the Deb ug programs policy
applied. Otherwise, Veeam Backup & Replication returns the Access is Denied error. To learn how to apply
the policy, see this Veeam KB article.

• Multi-factor authentication (MFA) for the user account must be disabled before launching configuration
database restore wizard. To learn how to disable MFA, see Multi-Factor Authentication.

• Stop all jobs that are currently running. During restore of configuration, Veeam Backup & Replication
temporary stops the Veeam Backup Service and jobs.

• Save registry values that you changed or created on the backup server. After restore, you will need to
recreate or change the keys manually because the configuration database does not store them.

• Check the version of the backup server. On the backup server running Veeam Backup & Replication 12.1,
you can restore configuration backups created with the following product versions: 12 (build 12.0.1420),
11a (build 11.0.1.1261), 11 (build 11.0.0.837), and 10a (build 10.0.1.4854).

• Make sure that the certificate chain restored from a configuration backup will successfully pass validation
on the target backup server. This precaution is required if the following conditions are met:

a. You want to restore configuration database of a backup server used in the Veeam Agent management
scenario.

b. The backup server whose configuration database you want to restore uses a custom certificate issued
by a Certificate Authority instead of the default self-signed certificate to ensure a secure connection
in the Veeam Agent management infrastructure.

• If you plan to restore configuration data to the database on another Microsoft SQL Server, make sure the
account for using Veeam Backup & Replication has sufficient permissions. For more information, see
Permissions.

• You can not use Microsoft SQL Server configuration backup created in Veeam Backup & Replication 11 or
earlier to restore the configuration database to PostgreSQL.

• After you run configuration restore for capacity tier, Veeam Backup & Replication will put the capacity tier
extents into the Sealed mode. Rescan the backup infrastructure and then remove the extents from the
Sealed mode.

• If you use a Veeam Backup & Replication server as a Veeam repository, after restore to a new host this
repository will be located in the same file path as it was before the migration.

608 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

You can start configuration restore only from the Veeam Backup & Replication console installed locally on
the backup server. You cannot start configuration restore from the console installed on a remote machine.

609 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Configuration Database Restore Wizard
To launch the Veeam Backup and Replication Configuration Restore wizard, do either one of the following:

• From the main menu of the Veeam Backup & Replication console, select Configuration Backup. In the
Restore section, click Restore.

• In the Sta rt menu of the backup server, click Configuration Restore .

• Use the Veeam.Backup.Configuration.Restore.exe file located in the installation folder on the


backup server. By default, the path to the folder is the following: %PROGRAMFILES%\Veeam\Backup
and Replication\Backup.

• [If the configuration backup is stored on the backup server] In Microsoft Windows Explorer, open the
folder where configuration backups are stored (by default,
Backup\VeeamConfigBackup\<BackupServerName> on the volume with most disk space on the
backup server) and double-click the necessary configuration backup file.

610 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Restore Mode
At the Restore Mode step of the wizard, choose a restore mode that you want to use.

• Select Restore if you want to restore data from the configuration backup to the database used by the
initial backup server.

In the Restore mode, Veeam Backup & Replication retrieves configuration data from the backup and stores
it to the target database. After that, Veeam Backup & Replication performs additional rescan of VM
replicas and backup repositories connected to the backup server, and runs tape library cataloging process.
Rescan helps synchronize potential changes between the backup infrastructure and restored da tabase that
took place from the moment when the configuration backup was created till the present time. As a result,
the target configuration database will contain information about restore points that were created after the
configuration backup was taken, and this information is displayed in the Veeam Backup & Replication
console.

• Select Mig rate if you want to restore data from the configuration backup to the database used by another
backup server.

In the Migrate mode, Veeam Backup & Replication retrieves configuration data from the backup and stores
it to the target database. No rescan operation is performed.

611 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Configuration Backup
At the Configuration Backup step of the wizard, select a configuration backup from which you want to restore
data:

1. From the Ba ckup repository list, select a server or backup repository on which the configuration backup
file is located.

2. Click Browse next to the Ba ckup file field and select the backup file.

If you select to restore configuration data from a backup in a remote backup repository, during restore
Veeam Backup & Replication will first copy the backup file to a temporary folder on the backup server. After you
finish the restore process and close the wizard, Veeam Backup & Replication will automatically delete the
configuration file from the temporary folder.

612 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Configuration Backup Parameters
At the Ba ckup Contents step of the wizard, Veeam Backup & Replication will analyze the content of the selected
backup file and display the following information:

• Ba ckup file: information about configuration backup file itself.

• P roduct: version of Veeam Backup & Replication installed on the initial backup server and configuration
database version.

• Da tabase: information about original database server, database version and compatibility.

• Ca talogs: catalogs storing backup configuration data.

Review the displayed settings and click Nex t.

613 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Password
The P a ssword step of the wizard is available if you have enabled the encryption option in the configuration
backup properties.

Enter the password to decrypt configuration backup data:

1. Check the password hint to recall the password.

2. In the P a ssword field, enter the password to decrypt the configuration backup file.

If you forgot or lost the password, click the I forgot the password link. For more information, see Decrypting
Data Without Password.

NOTE

Restoring configuration data without a password is included in the Veeam Universal License. When using a
legacy socket-based license, Enterprise or higher edition is required.

Also, your backup server must be connected to Veeam Backup Enterprise Manager. Otherwise, you will not
see the I forgot the password link.

614 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Target Database
At the Ta rget Database step of the wizard, specify the target Microsoft SQL Server or PostgreSQL instance to
which configuration data must be restored.

1. In the Da tabase field, select the database engine, PostgreSQL or Microsoft SQL Server.

2. In the Instance field, do one of the following:

o For Microsoft SQL Server, select an instance on which the database is deployed or must be deployed.
In the list of Microsoft SQL Server instances, Veeam Backup & Replication displays all servers from the
network where the backup server resides. To update the list of servers, click Refresh on the right. To
specify an instance manually, use the SERVER_NAME\INSTANCE_NAME format.

o For PostgreSQL, specify an instance on which the database is deployed or must be deployed. Use the
hostname:port format to specify an instance.

3. In the Da tabase name field, specify a name of the database to which configuration data must be restored.

By default, Veeam Backup & Replication uses the default name or port for the target database. If you
specify a name of an existing target database, Veeam Backup & Replication will overwrite this database. If
you specify a name of the database that does not exist, Veeam Backup & Replication will create it on the
specified Microsoft SQL Server or PostgreSQL instance.

NOTE

If a backup repository is located in the backup server, after configuration restore, this repository will
point to the same path as it was before the migration but in a new host. For example, if you keep
backed-up data on the D disk, after migration Veeam Backup & Replication will keep new backups on
the D disk of the new host.

4. In the Authentication section, select the authentication mode to connect to the target database instance:

o For Microsoft SQL Server, select W ind ows authentication or SQL a uthentication mode. If you select
the SQL a uthentication mode, specify credentials that will be used to connect to the target Microsoft
SQL Server instance.

o For PostgreSQL, select W ind ows authentication or Na tive authentication mode. If you select the
Na tive authentication mode, specify credentials that will be used to connect to the target PostgreSQL
instance.

615 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When you restore configuration to an existing database, the configuration restore process will delete the
current state of the database contents and replace it with the restored data. Veeam Backup & Replication will
display a warning. If you want to replace the contents, click Y es to confirm.

If you do not want to lose the current data, restore the configuration to a new database. To do this, click No to
the warning and specify a non-existing database name in the Da tabase name field.

616 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Restore Options
At the Restore Options step of the wizard, specify additional restore options.

1. In the Restore section, select what data you want to restore from the configuration backup.
Veeam Backup & Replication always restores configuration data for backup infrastructure components,
jobs and global settings specified at the level of the backup server. You can additionally restore the
following data:

o Ba ckup and replica catalog: data about all backups and replicas registered on the backup server and
information about tapes to which backups were written and location of these tapes.

o Session history: data about all sessions performed on the backup server.

2. If you plan to use PowerShell on the restored backup server, select the E nable required PowerShell policy
for SCVMM check box. During restore, Veeam Backup & Replication will enable the PowerShell execution
policy and you will not have to enable it manually afterwards. Enabling this option is identical to running
the ‘Set-ExecutionPolicy RemoteSigned' command on the backup server.

3. If you are restoring configuration data to the same database, select the Ba ckup existing database before
configuration restore check box. This option will help you protect the current database from accidental
errors during the restore process. During restore, Veeam Backup & Replication will first back up the
current database using the native tools of Microsoft SQL Server or PostgreSQL. After that,
Veeam Backup & Replication will purge the current database and import data from the configuration
backup to it. In such scenario, if an error occurs during the restore process, you will be able to restore the
current database from the Microsoft SQL backup using Microsoft SQL Management Studio or SQL scripts.
For PostgreSQL, you will be able you will be able to restore the current database from the PostgreSQL
backup using PGadmin or SQL scripts.

The created Microsoft SQL database backup is named by the following pattern:
VeeamBackup<DatabaseName><date>.bak and stored to the default Microsoft SQL backups location, for
example: %ProgramFiles%\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\.

The created PostgreSQL database backup is stored by the following path:


%ProgramData%\Veeam\Backup\Utils\PostgreSQLBackup.

4. Click Restore. Veeam Backup & Replication will stop currently running jobs and
Veeam Backup & Replication services and will restore the database to the specified location.

617 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Review Restore Settings
At the Restore step of the wizard, Veeam Backup & Replication will display the progress on the restore process.
Wait for the restore process to complete and click Nex t.

If you have chosen to restore data in the Migrate mode and the configuration backup file does not meet the
Migrate mode requirements, Veeam Backup & Replication will display a warning and offer you to switch to the
Restore mode. The Restore mode requires more time but guarantees that information about all new restore
points will be available in the restored database.

• To switch to the Restore mode, in the warning window click Y es .

• To carry on data restore in the Mig rate mode, in the warning window click No.

• To stop the restore process, in the warning window click Ca ncel.

For more information, see Migrating Configuration Database.

618 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Check Configuration
[For Veeam Backup & Replication version 12 (12.1 (build 12.1.0.2131)) and later] At the Check Configuration step
of the wizard, Veeam Backup & Replication will analyze the content of the restored database and display issues
which can potentially interfere with Veeam Backup & Replication functionality.

619 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Finalize Restore Process
After the restore process has finished, you may need to perform the following actions to finalize the
configuration database restore:

1. Specify credentials for backup infrastructure objects.

2. Specifying credentials for cloud services.

3. Perform components upgrade.

Specifying Credentials
At the Credentials step of the wizard, Veeam Backup & Replication displays a list of credentials records that
existed on the backup server at the time when the configuration backup was created. If by the time of restore
passwords for credentials records have changed, you can specify new values for these records.

IMP ORTANT

If you have not enabled encryption for configuration backups, Veeam Backup & Replication will not restore
passwords for credentials records. You need to re-enter passwords for all credentials records to make sure
that backup infrastructure components and jobs work in a proper way after you complete configuration
restore.

To edit credentials records:

1. Select a record in the list and click E d it.

2. Edit settings of the record as required.

3. Repeat the procedure for all records in the list.

Specifying Cloud Credentials


At the Cloud Credentials step of the wizard, Veeam Backup & Replication displays a list of cloud credentials
records that existed on the backup server at the time when the configuration backup was created. If by the time
of restore passwords for cloud credentials records have changed, you can specify new values for these records.

620 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Consider the following:

• If you have not enabled encryption for configuration backups, Veeam Backup & Replication will not
restore passwords for cloud credentials records. You need to re-enter passwords for all cloud
credentials records to make sure that cloud services and jobs work in a proper way after you
complete configuration restore.
• You cannot edit credentials of Microsoft Azure Compute accounts and Google Cloud service account
in the configuration restore wizard. You can edit these credentials only after configuration restore in
Cloud Credentials Manager. For details, see Editing and Deleting Credentials Records.
• Veeam Backup & Replication does not restore credentials records of Google Cloud service accounts
that were created automatically using the Cloud Credentials Manager. For details, see Google Cloud
Service Account.

To edit cloud credentials records:

1. Select a record in the list and click E d it.

2. Edit settings of the record as required.

3. Repeat the procedure for all records in the list.

Performing Components Upgrade


After the restore process is complete, Veeam Backup & Replication will check if services on backup
infrastructure components must be upgraded and display a list of outdated components.

To upgrade backup infrastructure components, select check boxes next to the necessary components and click
Nex t. If some component fails to upgrade, you can get back to a previous step of the wizard and repeat the
procedure or close the wizard and upgrade the components manually. For more information, see Server
Components Upgrade.

621 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Synchronize Backups and Tape Libraries
After the configuration database is restored, Veeam Backup & Replication can perform a synchronization
operation for backups and replicas created on the backup server and tape libraries connected to the backup
server.

• The synchronization operation for backups and replicas is performed if you are restoring a database from a
backup created by Veeam Backup & Replication in the Restore mode and you have selected to restore data
from the backup and replica catalog.

• The synchronization operation for tape libraries is performed if you are restoring a database from a backup
created by Veeam Backup & Replication in the Restore mode and you have selected to restore data fr om
the backup and replica catalog.

Wait for the synchronization operation to complete.

622 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Finish Working with Wizard
At the Summary step of the wizard, finalize the process of configuration data restore.

1. Review the restore process results.

2. If you want to start Veeam Backup & Replication after you finish working with the wizard, select the
La unch the Backup & Replication user interface check box.

3. If you want to export the configuration file, click E x port answer file.

4. Click Finish to exit the wizard.

NOTE

Consider the following:

• If you created custom registry values or changed the existing ones on the backup server, you must
recreate or change the registry values again.
• If you restore data from the configuration backup in the Restore mode, all jobs on the backup server
will be disabled after the restore process is complete. You need to enable them manually.

Migrating Veeam Backup & Replication to Another Backup


Server
If you need to migrate Veeam Backup & Replication to another backup server, you can back up its configuration
database, install Veeam Backup & Replication on the target server and restore the configuration data from the
backup. As a result, you will have a new Veeam Backup & Replication server with all settings, jobs and backup
infrastructure elements from the old server.

623 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations and Considerations
Before you migrate the configuration database of Veeam Backup & Replication to another backup server,
consider the following limitations and considerations:

• It is recommended that you use Veeam Backup & Replication tools to create configuration backups and
migrate the configuration database. If you use native Microsoft SQL Server tools, after migration, some
information, such as secure configuration data, may not be accessible.

• This section gives instructions on how to migrate Veeam Backup & Replication together with its
configuration database to another server. If you need to migrate only the configuration database, see
Migrating Configuration Database to Another SQL Server.

• Veeam Backup & Replication supports configuration database migration between different database
engines only within the same Veeam Backup & Replication version.

IMP ORTANT

We strongly recommend using only the configuration database restore process to migrate
Veeam Backup & Replication configuration database to another backup server.

Migrating Veeam Backup & Replication


If you want to migrate Veeam Backup & Replication to another backup server, perform the following steps:

1. Stop running jobs and disable scheduled jobs.

2. Save registry values that you changed or created .

3. Back up the configuration database of Veeam Backup & Replication.

4. Install Veeam Backup & Replication on the target machine.

5. Restore the configuration database from the backup.

6. Finish the configuration.

Step 1. Stop and Disable Jobs


Before you start the migration process, stop all running jobs and disable all scheduled jobs on the source backup
server before you create the configuration backup.

NOTE

Do not start or enable any jobs until the migration of Veeam Backup & Replication is finished. If you start a
job before migration is completed, Veeam Backup & Replication will produce a new restore point in the
chain and update the chain metadata. The created configuration backup will not contain information about
this new restore point. When you migrate data from the configuration backup to the database and start the
job again, Veeam Backup & Replication will fail to synchronize the chain metadata with data in the
database. As a result, the job will fail.

624 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. [Optional] Save registry Values That You Changed or
Created
If you have created new registry values or changed the existing keys on the backup server, you will need to
recreate the keys or change the keys manually after the migration. The configuration database does not store
registry values.

To save registry values, you can use the reg export command or you can use Registry Editor to save keys
manually. For details, see Windows Documentation.

Step 3. Back Up Configuration Database


Back up the configuration database of Veeam Backup & Replication. For instructions, see Running Configuration
Backups Manually.

Step 4. Install Veeam Backup & Replication on Target Machine


Install Veeam Backup & Replication on the machine on which you plan to move your source backup server. The
machine must meet system requirements for a backup server.

During installation, you need to specify a new database name to store the configuration data. You can select a
Microsoft SQL Server instance on the local or remote server. It does not matter whether you select an existing
instance or create a new one. In the next steps of this guide, you will restore the previous configuration data to
the database selected at this step.

For instructions on how to install Veeam Backup & Replication, see Installing Veeam Backup & Replication.

Step 5. Restore Configuration Database from Backup


Use the native feature of Veeam Backup & Replication to restore the configuration database from the backup
created in Step 3.

1. On the target backup server, log in to the Veeam Backup & Replication console. For details, see Logging in
to Veeam Backup & Replication.

2. From the main menu of the Veeam Backup & Replication console, select Configuration Backup.

625 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Restore section, click Restore to launch the Configuration Database Restore wizard.

NOTE

Loss protection disabled warning is safe to ignore if you do not have Veeam Backup Enterprise
Manager installed, your backup server is not registered with Veeam Backup Enterprise Manager
server, or your system administrator chose not to enable loss protection functionality.

626 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. At the Restore Mode step of the wizard, select Mig rate.

Before migrating the configuration backup, Veeam Backup & Replication performs an additional check. If
the configuration backup does not meet the requirements, Veeam Backup & Replication will offer you an
option to switch to the Restore mode.

5. At the Configuration Backup step of the wizard, specify the backup file of the configuration database

a. From the Ba ckup repository drop-down list, select This server.

b. Click Browse to specify the backup file location.

NOTE

This backup file has been created in Step 3. You must copy the backup file to the target
Veeam Backup & Replication server beforehand.

627 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Complete the wizard as described in section Restoring Configuration Database.

Veeam Backup & Replication will rescan VM replicas, backup repositories and tape libraries connected to
the backup server. The database will be updated to include information about new restore points, and
subsequent job sessions will work in a proper way.

Step 6. Finish Configuration


After you restore the configuration backup, finalize the configuration:

• If you created custom registry values or changed the existing ones on the previous backup server, you
must recreate or change the registry values again manually on the target backup server. You can import
saved keys using the reg import command or Registry Editor.

• If you have local repositories, after migration to another machine they may be displayed as empty. In this
case, add them again and remap the jobs.

• Enable your backup jobs and backup copy jobs. Take a closer look at your backup infrastructure to ensure
that everything is working as expected.

• If you use Veeam Backup & Replication to back up storage systems, after migration they will not be added
to the backup infrastructure. In this case, you must re-add them after migration completes. Storage
System Snapshot Integration section in the Veeam Backup & Replication User Guide.

• If you use a hardened repository with immutability, after migration this server will not be available. In this
case, you must specify single-use credentials for this repository again. For more information, see Editing
Settings of Backup Repositories.

• If you use Linux hosts in your backup infrastructure, after migration these hosts and hosts that are
associated with them will not be available. (For example, if you have a Linux host with the backup proxy
role, the backup repositories to which this Linux backup proxy transfer during a backup job will not be
available). In this case, you must open the Edit Linux Server wizard for the necessary Linux host, follow
the steps of the wizard and click Finish.

628 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you have Veeam Agent backup jobs managed by Veeam Agents, update the backup policies aft er the
migration process.

NOTE

If the Veeam Backup & Replication server was added to the Veeam Backup Enterprise Manager or Veeam
ONE infrastructure, you must re-add the backup server after you migrate it to another server.

Migrating Configuration Database to Another SQL Server


It is the best practice to keep the Veeam Backup & Replication application and its configuration database on the
same server to maintain lowest latency and highest performance. However, in some scenarios a remote
Microsoft SQL Server instance can be the better choice:

• High Availability. SQL Clustering and Always On Availability Group on external SQL Servers can be used for
high availability of the configuration database. To learn about the configuration details, see this Veeam KB
article.

• Licensing. Some enterprises have dedicated virtual clusters for SQL Servers due to licensing constraints. In
such cases, you can place the Veeam configuration database on an existing instance to lower the total cost
of ownership.

If you need to migrate the Veeam Backup & Replication configuration database to another SQL server, you can
connect the configuration database to a Microsoft SQL Server instance deployed on another server and restore
the configuration settings from the backup. As a result, you will be able to continue using the same
Veeam Backup & Replication server but it will be connected to a configuration database on another server.

Limitations and Considerations


Before you migrate the configuration database of Veeam Backup & Replication to another SQL server, consider
the following limitations and considerations:

• This section gives instructions on how to migrate a configuration database to another SQL server. If you
need to migrate the Veeam Backup & Replication application itself, see Migrating Veeam Backup &
Replication to Another Backup Server.

• It is recommended that you use Veeam Backup & Replication tools to create configuration backups and
migrate the configuration database. If you use native Microsoft SQL Server tools or others, after
migration, some information, such as secure configuration data, may not be accessible.

• If you are migrating the configuration database to a remote SQL instance tha t uses Windows
Authentication, all services that had access to the remote SQL instance before a migration must have the
these permissions after migration. For more information on permissions, see Permissions.

• If a backup server and a configuration database are located in different AD domains, the AD domain where
the configuration database is located must have a trust relationship with the AD domain to which the
backup server is added.

• When you migrate the configuration database to another SQL server, you must use the Microsoft SQL
Server credentials that have CREATE ANY DATABASE permission on the target Microsoft SQL Server. For
details, see Microsoft Docs. After database creation this account automatically gets the db_owner role and
can perform all operations with the database. If the current account does not have this permission, a
Database Administrator may create an empty database in advance and grant the db_owner role to the
account that will be used for migration of the configuration database.

629 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Veeam Backup Enterprise Manager collects data from backup servers with configuration databases that
run on the same database engine as the Enterprise Manager configuration database. The database engine
used by Veeam Backup Enterprise Manager and all of the Veeam Backup & Replication Servers managed
by this Veeam Backup Enterprise Manager must match. To migrate the Enterprise Manager configuration
database, see Veeam Backup Enterprise Manager Guide.

Migrating Configuration Database


If you want to migrate the configuration database of Veeam Backup & Replication to another SQL server,
perform the following steps:

1. Stop and disable jobs.

2. Back up the configuration database.

3. Restore the configuration database from the backup.

4. [Optional] Reactivate the Enterprise Manager Keyset.

5. Finish the configuration.

Step 1. Stop and Disable Jobs


Before you start the database migration, you must finish all jobs and restore sessions. If the job is scheduled,
you must disable the job. For instructions on how to stop and disable jobs, see Managing Jobs.

NOTE

Do not start or enable any jobs until the migration of Veeam Backup & Replication is finished. If you start a
job before migration is completed, Veeam Backup & Replication will produce a new restore point in the
chain and update the chain metadata. The created configuration backup will not contain information about
this new restore point. When you migrate data from the configuration backup to the database and start the
job again, Veeam Backup & Replication will fail to synchronize the metadata of the backup chain with data
in the database. As a result, the job will fail.

Step 2. Create Configuration Database Backup


To create a configuration database backup manually, perform the following steps:

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

2. Make sure that the E na ble configuration backup to the following repository check box is selected.

3. From the list of repositories, select a backup repository in which the configuration backup must be stor ed.

630 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Click Ba ckup now.

NOTE

Loss protection disabled warning is safe to ignore if you do not have Veeam Backup Enterprise
Manager installed, your backup server is not registered with Veeam Backup Enterprise Manager
server, or your system administrator chose not to enable loss protection functionality.

Step 3. Restore Configuration Database from Backup


To restore the configuration database, perform the following:

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

631 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the Restore section, click Restore.

3. At the Restore Mode step of the Veeam Backup & Replication Configuration Restore wizard, select
Mig rate.

4. Complete the wizard as described in section Restoring Configuration Database.

632 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. [Optional] Reactivate Enterprise Manager Keyset
After you migrate the Veeam Backup & Replication configuration database to another server, Veeam Backup
Enterprise Manager still sees the Veeam Backup & Replication server. However, you may need to reactivate
encryption keys.

If you use the Data Encryption feature to encrypt backups and your Veeam Backup & Replication server is added
to the Veeam Backup Enterprise Manager infrastructure, then you must reactivate the Enterprise Manager
keyset.

To reactivate the Enterprise Manager key, perform the following steps:

1. In the Veeam Backup Enterprise Manager web console, open the Settings section of the Configuration
view.

2. Open the Key Management tab.

3. In the Ma naged keys section, select the necessary keyset and click Activate.

For detailed instructions, see the Activating Enterprise Manager Keyset section in the Veeam Backup Enterprise
Manager Guide.

Step 5. Finish Configuration


After restoring the configuration database from the backup, finalize the configuration:

• Configure all necessary settings to ensure that you have a working configuration database backup. You
can now perform a backup of your new configuration database in the Configuration Backup Settings
window.

Reschedule your configuration database backup. Also, check if you can see the Loss protection enabled
label.

• If you have local repositories, after migration to another VM they may be displayed as empty. In this case,
add them again and remap the jobs.

• Enable your backup jobs and backup copy jobs. Take a closer look at your backup infrastructure to ensure
that everything is working as expected.

Migrating Configuration Database to PostgreSQL Server


If you need to migrate the Veeam Backup & Replication configuration database from Microsoft SQL Server to
PostgreSQL, you need to create a new configuration backup and restore it on the PostgreSQL instance. As a
result, you will be able to continue using the same Veeam Backup & Replication server but it will be connected
to a configuration database on PostgreSQL instead of Microsoft SQL Server.

Limitations and Considerations


Before you migrate the configuration database of Veeam Backup & Replication to PostgreSQL, consider the
following limitations and considerations:

• This section gives instructions on how to migrate a configuration database to PostgreSQL. If you need to
migrate the Veeam Backup & Replication application itself, see Migrating Veeam Backup & Replication to
Another Backup Server.

• If you want to migrate configuration database from PostgreSQL to another SQL server, see Migrating
Configuration Database to Another SQL Server.

633 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• It is recommended that you use Veeam Backup & Replication tools to create configuration backups and
migrate the configuration database.

• If a backup server and a configuration database are located in different AD domains, the AD domain where
the configuration database is located must have a trust relationship with the AD domain to which the
backup server is added.

• Veeam Backup & Replication supports configuration database migration between different database
engines only within the same Veeam Backup & Replication version.

• Veeam Backup Enterprise Manager collects data from backup servers with configuration databas es that
run on the same database engine as the Enterprise Manager configuration database. The database engine
used by Veeam Backup Enterprise Manager and all of the Veeam Backup & Replication Servers managed
by this Veeam Backup Enterprise Manager must match. To migrate the Enterprise Manager configuration
database, see Veeam Backup Enterprise Manager Guide.

• PostgreSQL standard system database named template1 must have UTF-8 encoding.

Migrating Configuration Database


If you want to migrate the configuration database of Veeam Backup & Replication to another PostgreSQL,
perform the following steps:

1. Stop and disable jobs.

2. Back up the configuration database.

3. Restore the configuration database from the backup.

4. [Optional] Reactivate the Enterprise Manager Keyset.

5. Finish the configuration.

Step 1. Stop and Disable Jobs


Before you start the database migration, you must finish all jobs and restore sessions. If the job is scheduled,
you must disable the job. For instructions on how to stop and disable jobs, see Managing Jobs.

NOTE

Do not start or enable any jobs until the migration of Veeam Backup & Replication is finished. If you start a
job before migration is completed, Veeam Backup & Replication will produce a new restore point in the
chain and update the chain metadata. The created configuration backup will not contain information about
this new restore point. When you migrate data from the configuration backup to the database and start the
job again, Veeam Backup & Replication will fail to synchronize the metadata of the backup chain with data
in the database. As a result, the job will fail.

Step 2. Create Configuration Database Backup


To create a configuration database backup manually, perform the following steps:

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

2. Make sure that the E na ble configuration backup to the following repository check box is selected.

3. From the list of repositories, select a backup repository in which the configuration backup must be stored.

634 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Click Ba ckup now.

NOTE

Loss protection disabled warning is safe to ignore if you do not have Veeam Backup Enterprise
Manager installed, your backup server is not registered with Veeam Backup Enterprise Manager
server, or your system administrator chose not to enable loss protection functionality.

Step 3. Restore Configuration Database from Backup


To restore the configuration database, perform the following:

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

635 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the Restore section, click Restore.

3. At the Restore Mode step of the Veeam Backup & Replication Configuration Restore wizard, select
Mig rate.

4. Complete the wizard as described in section Restoring Configuration Database. On the Ta rget Database
tab of the configuration restore wizard, select PostgreSQL as the database engine.

636 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

After the restore process, make sure that PostgreSQL target instance is configured according to the
recommended hardware resources values. You can modify settings of PostgreSQL target instance using the
Set-VBRPSQLDatabaseServerLimits cmdlet. For more information, see Veeam PowerShell Reference.

NOTE

After you complete the restore process, Veeam Backup & Replication will connect to the database you
specified as a target.

Step 4. [Optional] Reactivate Enterprise Manager Keyset


After you migrate the Veeam Backup & Replication configuration database to another server, Veeam Backup
Enterprise Manager still sees the Veeam Backup & Replication server. However, you may need to reactivate
encryption keys.

If you use the Data Encryption feature to encrypt backups and your Veeam Backup & Replication server is added
to the Veeam Backup Enterprise Manager infrastructure, then you must reactivate the Enterprise Manager
keyset.

To reactivate the Enterprise Manager key, perform the following steps:

1. In the Veeam Backup Enterprise Manager web console, open the Settings section of the Configuration
view.

2. Open the Key Management tab.

3. In the Ma naged keys section, select the necessary keyset and click Activate.

For detailed instructions, see the Activating Enterprise Manager Keyset section in the Veeam Backup Enterprise
Manager Guide.

Step 5. Finish Configuration


After restoring the configuration database from the backup, finalize the configuration:

• Configure all necessary settings to ensure that you have a working configuration database backup. You
can now perform a backup of your new configuration database in the Configuration Backup Settings
window.

Reschedule your configuration database backup. Also, check if you can see the Loss protection enabled
label.

• If you have local repositories, after migration to another VM they may be displayed as empty. In this case,
add them again and remap the jobs.

• Enable your backup jobs and backup copy jobs. Take a closer look at your backup infrastructure to ensure
that everything is working as expected.

Automating Configuration Database Restore


If you want to automate the process of the configuration database restore, you can do it using the
Veeam.Backup.Configuration.UnattandedRestore.exe file in Veeam Backup & Replication 12.1 or the
config.cfg file in Veeam Backup & Replication 12.

637 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations and Considerations
Before you start the restore process, check the prerequisites.

Restoring Configuration Database in


Veeam Backup & Replication 12.1
To restore Veeam Backup & Replication configuration database using the
Veeam.Backup.Configuration.UnattendedRestore.exe file, perform the following steps:

1. Generate Configuration File.

2. Specify Restore Settings.

3. Restore Configuration Database.

Step 1. Generate Configuration File


To generate the configuration file, do the following:

1. Open the command prompt.

2. Change the directory to the directory where the


Veeam.Backup.Configuration.UnattendedRestore.exe file is stored. By default, C:\Program
Files\Veeam\Backup and Replication\Backup.

cd "C:\Program Files\Veeam\Backup and Replication\Backup"

3. Use the following command to generate the configuration file. In the generate parameter, specify the
path where the configuration file will be saved.

Veeam.Backup.Configuration.UnattendedRestore.exe /generate:C:\backup\unatt
ended.xml

Alternatively, you can complete the configuration restore wizard and click E x port answer file on the Summary
step of the wizard. In this case, the configuration file will contain parameters you specified during the restore
process.

Step 2. Specify Restore Settings


After you execute the command, the configuration file will be generated with default preferences by the path
you specified. You can manually edit the file to specify the necessary para meters.

Step 3. Restore Configuration Database


To restore the configuration database, do the following:

1. Open the command prompt.

2. Change the directory to the directory where the


Veeam.Backup.Configuration.UnattendedRestore.exe file is stored. By default, C:\Program
Files\Veeam\Backup and Replication\Backup.

638 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
cd "C:\Program Files\Veeam\Backup and Replication\Backup"

3. Use the following command to restore the configuration file. In the file parameter, specify the path
where the configuration file is stored.

Veeam.Backup.Configuration.UnattendedRestore.exe /file:C:\backup\unattende
d.xml

Veeam Backup & Replication will use the preferences specified in the unattended.xml file to perform the
configuration database restore.

The path to the log file is


%ProgramData%\Veeam\Backup\Utils\Util.VeeamBackupConfiguration.UnattendedRestore.lo
g.

Configuration File Parameters

P a rameter Description Required

CONFIGURATION_FILE Specifies a full path to the configuration backup file. Yes

Supported values:

• For local backup files:


C:\Backup\VeeamConfigBackup\VM\VM_2022-
12-04_13-01-38.bco.

• For network backup files:


\\VM\Backups\VM_2022-12-04_13-01-
38.bco.

• For repository backup files:


VeeamConfigBackup\VM\VM_2022-12-04_13-
01-38.bco.

RE P OSITORY_NAME Specifies Veeam Backup & Replication repository name No


where the configuration backup file is stored. If you do
not specify this parameter, empty name will be used.

Supported values: String.

BACKUP_PASSWORD Specifies the password to decrypt the configuration No


backup file.

Supported values: String.

NE TW ORK_USER Specifies the user account for the network share. No

Supported values: domain\username.

639 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required

NE TW ORK_PASSWORD Specifies the password for the network share. No

Supported values: String.

SQLSERVER_ENGINE Specifies the database engine. No

Supported values: mssql or postgresql.

Default: postgresql.

DATABASE_SERVER Specifies the database server and instance on which the Yes
configuration database will be deployed.

Supported values:

• Microsoft SQL Server:


MSSQLSERVER\DBINSTANCE:PORT.

• PostgreSQL Server: POSTGRESQLSERVER:PORT.

SQLSERVER_DATABASE Specifies the name for the configuration database. No

Supported values: String.

Default: VeeamBackup.

SQLSERVER_AUTHENTICATION Specifies the authentication mode to connect to the No


database server where the Veeam Backup & Replication
configuration database will be deployed.

Supported values:

• Windows authentication: 0.

• SQL native authentication: 1.

Default: 0.

VBR_SQLSERVER_USERNAME Specifies a LoginID to connect to the SQL server in the No


native authentication mode

Supported values: String.

Note: The parameter is required if the


SQLSERVER_AUTHENTICATION parameter value is 1.

640 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required

VBR_SQLSERVER_PASSWORD Specifies a password to connect to the SQL server in the No


native authentication mode.

Supported values: String.

Note: The parameter is required if you specify the


VBR_SQLSERVER_USERNAME parameter.

P G_DUMP_PATH Specifies a path to the pg_dump.exe file. No

Supported values: String.

RE STORE_BACKUPS Defines that Veeam Backup & Replication will restore No


backup and replica restore points catalog.

Supported values:

• No: 0.

• Yes: 1.

Default: 1.

RE STORE_SESSIONS Defines that Veeam Backup & Replication will restore No


sessions history.

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

E NABLE_POWERSHELL_POLICY Defines that PowerShell execution policy will be set to No


work for SCVMM.

Supported values:

• No: 0.

• Yes: 1.

Default: 1.

641 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required

BACKUP_EXISTING_DATABASE Defines that the current database will be backed up. No

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

SE RVICES_AUTOSTART Defines that Veeam Backup & Replication will start No


automatically after the migration.

Supported values:

• No: 0.

• Yes: 1.

Default: 1.

CRE ATE_NEW_DATABASE Defines that the new database will be created if it does No
not exist.

Supported values:

• No: 0.

• Yes: 1.

Default: 1.

USE _EXISTING_DATABASE Defines that Veeam Backup & Replication will use an No
existing database if it is not empty.

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

USE _LOCKED_DATABASE Defines that Veeam Backup & Replication will use an No
existing database owned by another backup server.

Supported values:

• No: 0.

• Yes: 1.

Default: 1.

642 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required

OVE RWRITE_EXISTING_DATABASE Defines that the new database will overwrite the existing No
one.

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

STOP _PROCESSES Defines that Veeam Backup & Replication will terminate No
all running backup server processes.

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

SW ITCH_TO_RESTORE_MODE Defines that the configuration restore will switch to the No


restore mode if enabled backup jobs are found.

Supported values:

• No: 0.

• Yes: 1.

• Cancel: 2.

Default: 2.

RE TRY_COUNT Specifies the amount of retries that configuration restore No


should perform.

Supported values: Int32.

Default: 3.

ACCEPT_FOUND_DATABASE_ISSUES Defines that the configuration restore will proceed if No


database issues are found.

Supported values:

• No: 0.

• Yes: 1.

Default: 0.

643 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required

CRE DENTIALS Specify this parameter if you want to update stored No


passwords during the configuration restore. If you do not
specify this parameter, passwords will not be updated

Supported values: user=password;{hint}.

P RIVATE_KEYS Specify this parameter if you want to update stored No


private keys during the configuration restore. If you do
not specify this parameter, private keys will not be
updated.

Supported values:
user=privatekey;password;{hint}.

HOSTS Forces target server components upgrade if necessary. If No


you do not specify this parameter, all hosts will be
upgraded.

Note: If you specify only several hosts out of all hosts in


your backup infrastructure, only these hosts will be
upgraded. Do not specify this parameter if you want to
upgrade all hosts.

Supported values: DNS name\IP address.

Restoring Configuration Database in


Veeam Backup & Replication 12
To restore Veeam Backup & Replication configuration database using the config.cfg file, perform the
following steps:

1. Generate Configuration File.

2. Complete Configuration Restore wizard.

3. Restore Configuration Database.

Step 1. Generate Configuration File


To generate the configuration file, do the following:

1. Open the command prompt.

2. Change the directory to the directory where the Veeam.Backup.Configuration.Restore.exe file is


stored. By default, C:\Program Files\Veeam\Backup and Replication\Backup.

cd "C:\Program Files\Veeam\Backup and Replication\Backup"

3. Use the following command to generate the configuration file. In the genconfig parameter, specify the
path where the configuration file will be saved.

644 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam.Backup.Configuration.Restore.exe /genconfig:C:\config.cfg

When you perform the command, the configuration restore wizard will appear.

Step 2. Complete Configuration Restore Wizard


Complete the configuration restore wizard.

After you complete the configuration restore wizard, the configuration file will be generated by the path you
specified in the genconfig parameter. The configuration file will contain all the preferences you specified in
the configuration restore wizard. You can also edit it manually later.

Step 3. Restore Configuration Database


To restore the configuration database, do the following:

1. Open the command prompt.

2. Change the directory to the directory where the Veeam.Backup.Configuration.Restore.exe file is


stored. By default, C:\Program Files\Veeam\Backup and Replication\Backup.

cd "C:\Program Files\Veeam\Backup and Replication\Backup"

3. Use the following command to restore the configuration file. In the config parameter, specify the path
where the configuration file will be saved.

Veeam.Backup.Configuration.Restore.exe /config:C:\config.cfg

Veeam Backup & Replication will use the preferences you specified in the config.cfg file to perform the
configuration database restore.

The path to the log file is


%ProgramData%\Veeam\Backup\Utils\Util.VeeamBackupConfiguration.Restore.log.

Configuration File Parameters

P a rameter Description

RestoreMode Specifies the configuration restore mode. Accepts values:


Restore or Migrate.

Default: Restore.

FileMode Specifies the configuration backup file path type. Accepts


values: Local or Network.

Default: Local.

645 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description

ConfigurationFile Specifies the full path to the configuration backup file.

ConfigurationFilePassword Specifies the password to decrypt the configuration backup


file.

Da tabaseType Specifies the target database engine. Accepts values:


Microsoft SQL or PostgreSQL.

Default: PostgreSQL.

Da tabaseName Specifies the target database name to use for the


configuration restore.

Default: VeeamBackup.

Da tabaseServer Specifies the database server instance.

For Microsoft SQL, use the localhost\instanceName


format.

For PostgreSQL, use the localhost\instancePort


format.

UseWindowsAuthentication Defines that Veeam Backup & Replication will use Windows
authentication to perform the configuration restore. Accepts
values: True or False.

Default: True.

Note: This parameter is required if you do not use the SQL


Server authentication.

SqlUser Specifies the user name for the SQL Server authentication.

SqlPassword Specifies the password for the SQL Server authentication.

P g DumpPath Specifies the path to the PostgreSQL pg_dump utility.

RestoreBackups Defines that Veeam Backup & Replication will restore backup
and replica restore points catalog. Accepts values: True or
False.

Default: False.

646 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description

RestoreSessions Defines that Veeam Backup & Replication will restore session
history. Accepts values: True or False.

Default: False.

E na blePowerShellPolicy Defines that Veeam Backup & Replication will enable


PowerShell execution policy setting required for SCVMM.
Accepts values: True or False.

Default: False.

Ba ckupExistingDb Defines that Veeam Backup & Replication will back up


existing database before performing the configuration
restore. Accepts values: True or False.

Default: False.

La unchVbrConsole Defines that Veeam Backup & Replication will launch the
console after the configuration restore is complete. Accepts
values: True or False.

Default: False.

CreateDbIfNotExists Defines that Veeam Backup & Replication will create a new
database if selected database does not exist. Accepts values:
Yes or No.

Default: Yes.

Note: The parameter value No will terminate the


configuration restore if the selected database does not exist.

P roceedWithUnsupportedDb Defines that Veeam Backup & Replication will proceed the
configuration restore with the selected database even if it
has unknown type. Accepts values: Yes or No.

Default: No.

Note: The parameter value Yes will terminate the


configuration restore if the selected database has unknown
type.

647 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description

UseLockedDb Defines that Veeam Backup & Replication will proceed the
configuration restore with the selected database even if it is
owned by another backup server. Accepts values: Yes or No.

Default: Yes.

Note: The parameter value No will terminate the


configuration restore if the selected database is owned by
another backup server.

UseVbrDb Defines that Veeam Backup & Replication will overwrite


existing database even if it is Veeam Backup & Replication
configuration database. Accepts values: Yes or No.

Default: Yes.

Note: The parameter value No will terminate the


configuration restore if the existing database is
Veeam Backup & Replication configuration database.

SwitchRestoreMode Defines that Veeam Backup & Replication will switch to the
configuration restore mode if one or more enabled backup
jobs are found. Accepts values: Yes, No or Cancel.

Default: Cancel.

Note: The parameter value Cancel will terminate the


configuration restore if enabled backup jobs are found.

648 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup PowerShell Module
Veeam Backup P owerShell is an extension for Microsoft Windows PowerShell that adds a set of cmdlets to allow
users to perform backup, replication and recovery tasks through the command -line interface of PowerShell or
run custom scripts to fully automate operation of Veeam Backup & Replication. For more information on the
Veeam Backup PowerShell module, see the Getting Started section of Veeam PowerShell Reference.

649 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Virtualization Servers and Hosts
You can add the following types of servers and hosts to the backup infrastructure:

• Microsoft Hyper-V Server

• Microsoft SMB3 Server

• Microsoft Windows Server

• Linux Server

NOTE

We recommend that only one instance of a server or host is present in the backup infrastructure at a time.
Do not add the same server or host multiple times, for example, by a DNS name and IP address, this can
cause unexpected behavior.

You can add physical machines and VMs to the backup infrastructure and assign different roles to them. The
table below describes which roles can be assigned to the different types of servers.

Server Type Source Host Ta rget Host Off-Host Backup Ba ckup


P roxy Rep ository

Microsoft Hyper-V Server

(standalone Microsoft Hyper-V (not


host, SCVMM or Hyper-V recommended)
cluster)

Microsoft SMB3 server

Microsoft Windows server

Linux server

650 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

You can also add the following servers:

• VMware vSphere servers. For more information on how to add servers, see the Adding
VMware vSphere Servers section in the Veeam Backup & Replication User Guide for
VMware vSphere.
• Veeam Backup for AWS servers. For more information on how to add servers, see the Deployment
and Configuration section in the Integration with Veeam Backup for AWS Guide.
• Veeam Backup for Microsoft Azure servers. For more information on how to add servers, see the
Deployment and Configuration section in the Integration with Veeam Backup for Microsoft Azure
Guide.
• Veeam Backup for Google Cloud servers. For more information on how to add servers, see the
Deployment and Configuration section in the Integration with Veeam Backup for Google Cloud
Guide.
• Nutanix AHV clusters. For more information on how to add AHV clusters, see the Deployment
section in the Veeam Backup for Nutanix AHV User Guide.
• Kasten K10 instances. For more information on how to add K10 instances, see the Deployment and
Configuration section in the Kasten K10 Integration Guide.

Related Topics
• Veeam Data Movers

• Rescanning Servers

• Editing Server Settings

• Removing Servers

651 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Microsoft Hyper-V Servers
You must add to the backup infrastructure Microsoft Hyper-V hosts that you plan to use as source and target for
backup, replication and other activities.

You can connect standalone Hyper-V hosts, Hyper-V clusters or SCVMM servers. If a Hyper-V host is a part of a
cluster or SCVMM, it is recommended that you add to the backup infrastructure a cluster or SCVMM, not a
standalone Hyper-V host. If you plan to migrate VMs between hosts in the cluster or SCVMM, you will not have
to reconfigure jobs in Veeam Backup & Replication. Veeam Backup & Replication will automatically locate
migrated VMs and continue processing them as usual. If you migrate VMs between standalone hosts that are not
a part of one cluster or SCVMM server registered in Veeam Backup & Replication, you will have to reconfigure
jobs to include the migrated VMs. After that, Veeam Backup & Replication will create full backups for these
VMs. If you do not reconfigure the jobs, they will fail.

Before you add a Microsoft Hyper-V server, check prerequisites. Then use the New Hy per-V Server wizard to add
the server.

NOTE

If you add a Hyper-V host to a cluster that is already added to your backup infrastructure,
Veeam Backup & Replication may not display this Hyper-V host in the list of managed servers. To display
the Hyper-V host and make it accessible from the Veeam Backup & Replication console, do the following:

• If the Hyper-V host is added to a cluster that is managed by SCVMM, right-click the SCVMM server,
select P roperties and go through the steps of the E d it Hyper-V Server wizard.
• If the Hyper-V host is added to a cluster that is not managed by SCVMM, right-click the cluster and
select Rescan.

To ensure that all Veeam Backup & Replication components on the Hyper-V host are up to date, right-click
the Hyper-V host, select P roperties and go through the steps of the E d it Hyper-V Server wizard.

Before You Begin


Before you add a Microsoft Hyper-V server to the backup infrastructure, check the following prerequisites :

• Check permissions required to add the server. For more information, see Permissions.

• Make sure that you do not add to the backup infrastructure Hyper-V hosts or clusters managed by an
SCVMM server if this SCVMM server is already added to the backup infrastructure.

• File and printer sharing must be enabled in network connection settings of the added Microsoft Hyper -V
host. On every connected Microsoft Hyper-V host, Veeam Backup & Replication deploys a set of
components:

o Veeam Installer Service

o Veeam Data Mover

o Veeam Hyper-V Integration Service

If file and printer sharing is not enabled on the host, Veeam Backup & Replication will fail to deploy these
components.

• [For SCVMM] SCVMM Admin UI must be installed on the backup server. Otherwise, you will not be able to
add SCVMM servers to the backup infrastructure.

SCVMM console version must match the management server version.

652 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Make sure that the NETBIOS name of the Microsoft Hyper-V Server is successfully resolved.

• If you get the " Invalid Credentials " error when adding a Hyper-V host using a local account, see this
Veeam KB article.

• Veeam Backup & Replication ignores the SCVMM maintenance mode on Hyper-V hosts and Hyper-V
cluster nodes. That is, Veeam Backup & Replication continues all data protection activities and allows
launching new ones.

653 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Hyper-V Server Wizard
To launch the New Hyper-V Server wizard, do one of the following:

• Open the Ba ckup Infrastructure view. In the inventory pane, select the Ma naged Servers node and click
Ad d Server on the ribbon or right-click the Ma naged Servers node and select Ad d Server. In the Add Server
window, click Microsoft Hyper-V > Hy per-V.

• Open the Inventory or Files view. In the inventory pane select the Microsoft Hyper-V node and click Ad d
Server on the ribbon. You can also right-click the Microsoft Hyper-V node and select Ad d Server.

654 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Server Name or Address
At the Na me step of the wizard, specify an address and description for the Microsoft Hyper -V server.

1. Enter a full DNS name, or IPv4 or IPv6 address of the Microsoft Hyper -V server. Note that you can use
IPv6 addresses only if IPv6 communication is enabled as described in section IPv6 Support.

2. Provide a description for future reference. The default description contains information about the user
who added the server, date and time when the server was added.

655 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Choose Server Type
At the Ty p e step of the wizard, select the type of server that you want to add.

• Select Microsoft System Center Virtual Machine Manager if you want to add SCVMM that manages several
Microsoft Hyper-V hosts. Veeam Backup & Replication will pull information about Microsoft Hyper-V hosts
and clusters managed by SCVMM and add them to the list of servers as a part of the SCVMM hierarchy.

• Select Microsoft Hyper-V cluster if you want to add a Microsoft Hyper-V cluster not managed by SCVMM.

• Select Microsoft Hyper-V server if you want to add a standalone Microsoft Hyper-V host that is not a part
of the Microsoft Hyper-V cluster and is not managed by SCVMM.

NOTE

If a Hyper-V host is a part of a cluster or SCVMM, it is recommended that you add to the backup
infrastructure a cluster or SCVMM, not a standalone Hyper-V host. If you plan to migrate VMs between
hosts in the cluster or SCVMM, you will not have to reconfigure jobs in Veeam Backup & Replication.
Veeam Backup & Replication will automatically locate migrated VMs and continue processing them as
usual. If you migrate VMs between standalone hosts that are not a part of one cluster or SCVMM server
registered in Veeam Backup & Replication, you will have to reconfigure jobs to include the migrated VMs.
After that, Veeam Backup & Replication will create full backups for these VMs. If you do not reconfigure
the jobs, they will fail.

656 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Credentials
At the Credentials step of the wizard, specify credentials for the Microsoft Hyper-V server.

1. From the Credentials list, select credentials for the account that has administrator privileges on the
Microsoft Hyper-V server. If you have not set up credentials beforehand, click the Ma nage a ccounts link or
click Ad d on the right to add the credentials. For more information, see Managing Credentials.

Veeam Backup & Replication will use the provided credentials to deploy the following components on
every added server:

o Veeam Installer Service

o Veeam Data Mover

o Veeam Hyper-V Integration Service

If you are adding SCVMM, the same credentials will be applied to all Microsoft Hyper -V hosts managed by
SCVMM. If some Microsoft Hyper-V hosts use their own credentials different from those you have
provided, Veeam Backup & Replication will fail to deploy components on these hosts. You will have to
specify credentials for such Microsoft Hyper-V hosts separately.

After you connect SCVMM, expand it in the inventory pane to see the list of managed Microsoft Hyper -V
hosts. Right-click the host, select P roperties and use the E d it Hyper-V Server wizard to specify the
credentials for this host.

2. To customize network ports used by Veeam Backup & Replication components, click P orts. By default,
Veeam Backup & Replication components use the following ports:

o Veeam Installer Service: port 6160

o Veeam Data Mover: port 6162

657 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Veeam Hyper-V Integration Service: port 6163

If necessary, adjust port numbers.

3. In the Da ta transfer options section of the Network Settings window, specify connection settings for file
copy operations. Provide a range of ports that will be used as transmission channels between the source
host and target host (one port per task). By default, Veeam Backup & Replication uses port range 2500-
3300. If the virtual environment is not large and data traffic will not be significant, you can specify a
smaller range of ports, for example, 2500-2509 to run 10 concurrent jobs at the same time.

4. [For Microsoft Hyper-V host deployed outside NAT] In the P referred TCP connection role section select
the Run server on this side check box. In the NAT scenario, the outside client cannot initiate a connection
to the server on the NAT network. As a result, services that require initiation of the connection from
outside can be disrupted. With this option selected, you will be able to overcome this limitation and
initiate a "server-client" connection — that is, a connection in the direction of the Microsoft Hyper-V host.

The option applies if the Hyper-V host also performs the role of the onhost backup proxy.

658 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Review Components
At the Ap p ly step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and what components will be installed.

1. If you add SCVMM or a Microsoft Hyper-V cluster, Veeam Backup & Replication will check every managed
Microsoft Hyper-V host to install or update the components. If you do not plan to use some Microsoft
Hyper-V hosts for data protection operations, you can clear check boxes next to these hosts in the list.
Veeam Backup & Replication will not deploy or update its components on excluded hosts, although such
hosts will be available in the SCVMM hierarchy.

If necessary, you can instruct Veeam Backup & Replication to install components on hosts that were
initially excluded later. To do this, open the Ba ckup Infrastructure view, in the inventory pane select the
added SCVMM or Microsoft Hyper-V cluster. In the working area right-click the Microsoft Hyper-V host
and select P roperties.

2. If you add a standalone Microsoft Hyper-V host, in the Ma x concurrent tasks field specify the number of
tasks that the Microsoft Hyper-V host must handle in parallel. If this value is exceeded,
Veeam Backup & Replication will not start a new task against the Microsoft Hyper-V host until one of
current tasks is finished.

Veeam Backup & Replication creates one task per every VM disk. By default, the Ma x concurrent tasks
value is set to 4.

Limiting the number of concurrent tasks may be necessary if you plan to work in the on-host backup mode
(where the Microsoft Hyper-V host performs the role of the default backup proxy) and want to balance
the workload in the backup infrastructure.

659 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The Ma x concurrent tasks field is displayed only for standalone Microsoft Hyp er-V hosts. To limit the
number of concurrent tasks for hosts managed by SCVMM or Microsoft Hyper -V cluster, you need to set
this value in settings of each Microsoft Hyper-V host in the SCVMM hierarchy or cluster separately. To do
this, open the Ba ckup Infrastructure view, in the inventory pane select the added SCVMM or Microsoft
Hyper-V cluster, in the working area right-click the Microsoft Hyper-V host and select P roperties.

660 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Results step of the wizard, complete the procedure of Microsoft Hyper-V server adding.

1. Review details of the Microsoft Hyper-V server.

2. Click Nex t, then click Finish to exit the wizard.

661 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Settings for Connected Volumes
After you add a Microsoft Hyper-V host to the backup infrastructure, you can configure the following settings
for the host:

• Enable or disable changed block tracking.

• Specify volume-specific settings.

• Enable or disable failover to a software VSS provider.

Before you specify settings for a Microsoft Hyper-V host, you must rescan volumes of the added host. During
volume rescan, Veeam Backup & Replication retrieves information about disks and volumes that are currently
connected to the Microsoft Hyper-V host and writes this information to the configuration database.

Veeam Backup & Replication automatically performs volume rescan every 4 hours. You can also start volume
rescan manually:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the host and click Rescan on the ribbon. Alternatively, you can right-click the
host and select Rescan.

Changed Block Tracking Settings


By default, Veeam Backup & Replication uses changed block tracking for processing Microsoft Hyper-V VMs. You
can disable changed block tracking, for example, for testing purposes.

Change block tracking is enabled and disabled at the level of the Microsoft Hyper-V host.

IMP ORTANT

The Disable changed b lock tracking for this host option does not affect changed block tracking on
Microsoft Hyper-V Server 2016 and later. In this case, you can disable change block tracking at the job
level. For more information on how to disable it, see Hyper-V Settings.

To disable changed block tracking:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the host and click Ma nage Volumes on the ribbon. Alternatively, you can right-
click the host and select Ma nage Volumes.

662 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ma nage Volumes window, select the Disable changed b lock tracking for this host check box.

Volume-Specific Settings
You can define volume-specific settings for a Microsoft Hyper-V host: select what VSS provider must be used for
snapshot creation and specify the maximum number of concurrent snapshots that must exist for the volume.

To specify volume-specific settings:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the host and click Ma nage Volumes on the ribbon. Alternatively, you can right-
click the host and select Ma nage Volumes.

4. Select the volume in the list and click E d it.

5. [For Microsoft Hyper-V 2012 R2 and earlier] To take a VSS snapshot of a specific volume,
Veeam Backup & Replication uses one of VSS providers available for this volume. To explicitly define what
VSS provider must be used for the volume, select the VSS provider from the VSS p rovider list. If a VSS
provider is not set explicitly, Veeam Backup & Replication will scan the list of available VSS providers and
select the most appropriate one automatically.

663 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. [For Microsoft Hyper-V 2012 R2 and earlier] You can simultaneously store 4 snapshots of one volume. To
change this number, specify the Ma x snapshots value. It is not recommended that you increase the
number of snapshots for slow storage. Many snapshots existing at the same time may cause VM
processing failures.

[For Microsoft Hyper-V Server 2016 and later] You can simultaneously store 4 VM checkpoints on one
volume. To change this number, specify the Ma x snapshots value. Note that this limitation works only for
checkpoints created during Veeam Backup & Replication data protection tasks.

VSS Provider Failover Settings


If you have selected to use a hardware VSS provider, Veeam Backup & Replication uses the specified hardware
VSS provider for volume snapshot creation. If the hardware VSS provider does not manage to create a volume
snapshot for some reason, Veeam Backup & Replication automatically fails over to a software VSS provider.

By default, the failover option is enabled. To disable failover to a softwar e VSS provider:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the host and click Ma nage Volumes on the ribbon. Alternatively, you can right-
click the host and select Ma nage Volumes.

664 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ma nage Volumes window, clear the Fa ilover to Software VSS Provider if Hardware VSS Provider
fa ils, or is not available check box.

665 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Microsoft SMB3 Servers
Veeam Backup & Replication supports Microsoft Hyper-V VMs whose disks reside on Microsoft SMB3 file shares
and lets you perform backup, replication and file copy operations for such VMs.

To work with VMs residing on Microsoft SMB3 shared folders, you must add to the backup infrastructure the
following components:

• Microsoft Hyper-V host on which VMs are registered.

• Microsoft SMB3 server or cluster hosting shared folders with VM disks.

If you do not add a Microsoft SMB3 server or cluster to the backup infrastructure, Veeam Backup & Replication
will not be able to use the changed block tracking mechanism to process such VMs.

If the SMB3 server host has several assigned roles (for example, if the host is a Hyper -V server and an SMB3
server for another Hyper-V host), Veeam Backup & Replication will not be able to use the changed block
tracking mechanism and latency control (I/O control).

NOTE

If VMs whose disks reside on SMB3 shared folders are registered on Microsoft Hyper -V Server 2016 or
later, adding a Microsoft SMB3 server is not required. Note, however, that if you do not add the Microsoft
SMB3 server, you will not be able to specify the Ma x snapshots and latency control settings for SMB3
shared folders.

Before you add a Microsoft SMB3 server or cluster, check prerequisites. Then use the New SMB3 Server wizard
to add the server or cluster.

Before You Begin


Before you add a Microsoft SMB3 server or cluster to the backup infrastructure, check the following
prerequisites:

• Microsoft SMB3 servers must run Microsoft Windows Server 2012 or later. Veeam Backup & Replication
supports only these types of Microsoft SMB3 servers.

• Microsoft SMB3 shared folders must be properly configured. For a full list of requirements for Microsoft
SMB3 shared folders, see the Requirements and supported configurations section at Microsoft Docs.

• VMs must not reside on hidden shared folders or default shared folders such as C$ or D$. When rescanning
Microsoft SMB3 file shared folders, Veeam Backup & Replication skips these types of folders.

• [For Veeam Cloud Connect Replication scenario] You cannot use Microsoft SMB3 shared folder as a
storage for VM replicas.

• To read/write data from/to an SMB3 share, Veeam Backup & Replication uses the account that you provide
when adding the Microsoft SMB3 server or cluster. Make sure that this account has Full Control
permissions in the security settings for SMB3 shares configured on the scale-out file server.

666 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New SMB3 Server Wizard
To launch the New SMB3 Server wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ma naged Servers node and select Ad d Server. Alternatively, you can
click Ad d Server on the ribbon.

3. In the Ad d Server window, click Microsoft Hyper-V > SMB3.

667 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Server Name or Address
At the Na me step of the wizard, specify an address and description for the Microsoft SMB3 server or cluster.

1. Enter a full DNS name or IP address of the Microsoft SMB3 server or cluster.

2. Provide a description for future reference. The default description contains information about the user
who added the server, date and time when the server was added.

668 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Server Type
At the Ty p e step of the wizard, select what type of Microsoft SMB3 server you want to add.

• Select Clustered file server if you want to add a Microsoft SMB3 cluster to the backup infrastructure.
Veeam Backup & Replication supports high availability and scale-out Microsoft SMB3 clusters.

• Select Sta ndalone file server if you want to add a standalone Microsoft SMB3 server to the backup
infrastructure.

669 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Credentials
At the Credentials step of the wizard, specify credentials for the Microsoft SMB3 server or cluster.

1. From the Credentials list, select credentials for the account that has administrator privileges on the
Microsoft SMB3 server or cluster. If you have not set up credentials beforehand, click the Ma nage
a ccounts link or click Ad d on the right to add the credentials. For more information, see Managing
Credentials.

o For domain user accounts, the user name must be specified in the DOMAIN\USERNAME format.

o For local user accounts, the user name must be specified in the HOSTNAME\USERNAME format.

Veeam Backup & Replication will use the provided credentials to deploy the following components on the
Microsoft SMB3 server or cluster nodes:

o Veeam Installer Service

o Veeam Data Mover

o Veeam Hyper-V Integration Service

2. To customize network ports used by Veeam Backup & Replication components, click P orts. By default,
Veeam Backup & Replication components use the following ports:

o Veeam Installer Service: port 6160

o Veeam Data Mover: port 6162

o Veeam Hyper-V Integration Service: port 6163

If necessary, adjust port numbers.

670 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Da ta transfer options section of the Network Settings window, specify connection settings for file
copy operations. Provide a range of ports that will be used as transmission channels between the source
server and target server (one port per task). By default, Veeam Backup & Replication uses port range
2500-3300. If the virtual environment is not large and data traffic will not be significant, you can specify
a smaller range of ports, for example, 2500-2509 to run 10 concurrent jobs at the same time.

4. [For Microsoft SMB3 server or cluster deployed outside NAT] In the P referred TCP connection role section
select the Run server on this side check box. In the NAT scenario, the outside client cannot initiate a
connection to the server on the NAT network. As a result, services that require initiation of the connection
from outside can be disrupted. With this option selected, you will be able to overcome this limitation and
initiate a ‘server-client’ connection — that is, a connection in the direction of the Microsoft SMB3 server or
cluster.

The option applies if the server or cluster also performs the role of the onhost backup proxy.

671 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Review Components
At the Ap p ly step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and what components will be installed.

1. Review the components.

2. Click Ap p ly to add the Microsoft SMB3 server or cluster to the backup infrastructure.

672 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Result step of the wizard, complete the procedure of Microsoft SMB3 server or cluster adding.

1. Review details of the Microsoft SMB3 server or cluster.

2. Click Nex t, then click Finish to exit the wizard.

673 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Configure SMB3 Shares
After you have added a Microsoft SMB3 server, you can configure the following settings for shared folders
hosted on this server:

• Enable or disable changed block tracking

• Define the number of concurrent snapshots for a shared folder

Before you specify settings for a Microsoft SMB3 server, you must rescan shared folders on this server. During
shared folders rescan, Veeam Backup & Replication retrieves information about shared folders that are currently
hosted on a Microsoft SMB3 server, updates the list of shared folders and writes this information to the
configuration database.

Veeam Backup & Replication automatically rescans the list of shared folders every 4 hours. You can also start
shared folders rescan manually:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the Microsoft SMB3 server and click Rescan on the ribbon. Alternatively, you
can right-click the Microsoft SMB3 server and select Rescan.

Changed Block Tracking Settings


By default, Veeam Backup & Replication uses changed block tracking for processing all VMs that reside on
shared folders hosted by a Microsoft SMB3 server. You can disable changed block tracking, for example, for
testing purposes.

Change block tracking is enabled and disabled at the level of the Microsoft Hyper -V host.

IMP ORTANT

The Disable changed b lock tracking for this host setting does not apply to VMs that are registered on
Microsoft Hyper-V Server 2016 and later.

To disable changed block tracking:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the Microsoft SMB3 server and click Sha red Folders on the ribbon.
Alternatively, you can right-click the Microsoft SMB3 server and select Sha red Folders.

674 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ma nage Volumes window, select the Disable changed b lock tracking for this host check box.

Shared Folder Settings


You can specify the maximum number of concurrent Hyper-V snapshots that must exist for a shared folder
hosted by a Microsoft SMB3 server.

To specify shared folder settings:

1. Open the Ba ckup Infrastructure view.

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

3. Select the necessary Microsoft SMB3 server in the working area and click Ma nage Volumes on the ribbon.
Alternatively, you can right-click the necessary Microsoft SMB3 server in the working area and select
Ma nage Volumes.

4. Select the necessary shared folder in the list and click E d it.

5. By default, jobs working with the same shared folder can take up to 4 snapshots of a folder
simultaneously. If necessary, you can increase or decrease the number of snapshots that can exist at the
same time. It is not recommended to increase the number of snapshots for slow storage: a great number
of snapshots existing at the same time may cause VM processing failures.

NOTE

For VMs hosted on Microsoft Hyper-V Server 2016 and later, the Sna pshots value defines the maximum
number of checkpoints that may be retained for a processed VM. The setting is specified at the level of a
shared folder in which VM disks reside.

675 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
676 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Microsoft Windows Servers
You must add to the backup infrastructure Microsoft Windows servers that you plan to use as backup
infrastructure components and servers that you plan to use for various types of restore operations.

Before you add a Microsoft Windows server, check prerequisites. Then use the New W indows Server wizard to
add the server.

Before You Begin


Before you add a Microsoft Windows server to the backup infrastructure, check network connection settings of
this server.

• Check permissions required to add the server. For more information, see Permissions.

• File and printer sharing must be enabled in network connection settings of the added Microsoft Windows
server. On every connected Microsoft Windows server, Veeam Backup & Replication deploys two
components:

o Veeam Installer Service

o Veeam Data Mover

If file and printer sharing is not enabled, Veeam Backup & Replication will fail to deploy these
components.

• If you plan to use PowerShell Direct, Microsoft PowerShell 2.0 or later must be installed on the added
server. For more information, see Microsoft Docs.

677 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Windows Server Wizard
To launch the New W indows Server wizard, do one of the following:

• Open the Ba ckup Infrastructure or Files view, in the inventory pane select the Microsoft Windows node
and click Ad d Server on the ribbon.

• Open the Ba ckup Infrastructure view. In the inventory pane, select the Ma naged Servers node and click
Ad d Server on the ribbon or right-click the Ma naged Servers node and select Ad d Server. In the Add Server
window, select Microsoft Windows.

678 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Server Name or Address
At the Na me step of the wizard, specify an address and description for the Microsoft Windows server.

1. Enter a full DNS name, or IPv4 or IPv6 address of the Microsoft Windows server. Note that you can use
IPv6 addresses only if IPv6 communication is enabled as described in section IPv6 Support.

2. Provide a description for future reference. The default description contains information about the user
who added the server, date and time when the server was added.

679 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Credentials
At the Credentials step of the wizard, specify credentials for the Microsoft Windows server.

1. From the Credentials list, select credentials for the account that has privileges described in section
Permissions.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add the credentials. For more information, see Managing Credentials.

Veeam Backup & Replication will use the provided credentials to deploy its components on the added
server.

2. To customize network ports used by Veeam Backup & Replication components, click P orts. For default
ports used by the Veeam Backup & Replication components, see Ports.

If necessary, adjust the port numbers.

3. In the Da ta transfer options section of the Network Settings window, specify connection settings for file
copy operations. Provide a range of ports that will be used as transmission channels between the source
server and target server (one port per task). By default, Veeam Backup & Replication uses port range
2500-3300.

If the virtual environment is not large and data traffic will not be significant, you can specify a smaller
range of ports, for example, 2500-2509 to run 10 concurrent tasks at the same time. Note that
Veeam Backup & Replication processes each VM disk as a separate task.

680 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. [For Microsoft Windows server deployed outside NAT] In the P referred TCP connection role section select
the Run server on this side check box. In the NAT scenario, the outside client cannot initiate a connection
to the server on the NAT network. As a result, services that require initiation of the connection from
outside can be disrupted. With this option selected, you will be able to overcome this limitation and
initiate a "server-client" connection — that is, a connection in the direction of the Microsoft Windows
server.

The option applies if one of the following roles is assigned to the server: source VMware backup proxy in
backup or replication scenarios, source repository in the backup copy scenario.

681 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
At the Review step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and what components will be installed.

1. Review the components.

2. Click Ap p ly to add the Microsoft Windows server to the backup infrastructure.

682 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all the required
components. Click Nex t to complete the adding of the server.

683 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of Microsoft Windows server adding.

1. Review details of the Microsoft Windows server.

2. Click Nex t, then click Finish to exit the wizard.

684 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Linux Servers
You must add to the backup infrastructure Linux servers that you plan to use as backup repositories and servers
that you plan to use for various types of restore operations.

Before you add a Linux server, check prerequisites. Then use the New Linux Server wizard to add the server.

Before You Begin


Before you add a Linux server to the Veeam Backup & Replication infrastructure, check the required permissions
and the following prerequisites.

Linux Firewalls
When you add a Linux server to the backup infrastructure, Veeam Backup & Replication automatically opens
ports used by the Veeam Data Mover on the Linux server. Generally, Veeam Backup & Replication automatically
open ports for most of popular firewalls (iptables, ufw, firewall-cmd). However, if for some reason the ports are
not opened, you can open the ports manually. You can also specify these ports at the SSH Connection step of
the New Linux Server wizard. Note that ports are opened dynamically: if 10 concurrent jobs are running,
Veeam Backup & Replication opens ports 2500-2509.

If you use the firewalld tool, you can configure firewall rules to open ports only in necessary zones. By
default, Veeam Backup & Replication opens ports in all active firewalld zones. If your firewall is configured
for different zones, and you want to minimize security holes, you can configure Veeam Backup & Replication to
open the ports only for certain zones. To do this, perform the following:

1. On the helper host or target Linux host, create the /etc/VeeamNetConfig file and define the following
parameter:

FirewalldZones=zone_name_1, zone_name_2

where zone_name_1, zone_name_2 is a list of zone names where the ports must be open.
Veeam Backup & Replication will skip the zones that are not in this list.

2. [Only for helper host] If you select a Linux host that is already added to the Veeam Backup & Replication
infrastructure, you should also add required zones to the
/opt/veeam/transport/VeeamTransportConfig file.

FirewalldZones=zone_name_1, zone_name_2

NOTE

Veeam Backup & Replication opens the port 2500 in all zones even if you have specified the required
zones in configuration files.

TLS Connection
Since Veeam Backup & Replication version 12, Linux servers use the TLS connection. You can disable the TLS
connection with a registry value for the servers that do not support the TLS connection. For m ore information,
contact Veeam Customer Support.

685 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Linux Server Wizard
To launch the New Linux Server wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ma naged Servers node and select Ad d Server. Alternatively, you can
click Ad d Server on the ribbon.

3. In the Ad d Server window, select Linux.

686 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Server Name or Address
At the Na me step of the wizard, specify an address and description for the Linux server.

1. Enter a full DNS name,or IPv4 or IPv6 address of the Linux server. Note that you can use IPv6 addresses
only if IPv6 communication is enabled as described in section IPv6 Support.

2. Provide a description for future reference. The default description contains information about the user
who added the server, date and time when the server was added.

687 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Credentials and SSH Settings
At the SSH Connection step of the wizard, specify credentials for the Linux server and additional SSH connection
settings.

1. From the Credentials list, select credentials for the account that has permissions described in section
Permissions. You can select a credentials record that uses the password authentication method or
credentials record that uses the Identity/Pubkey authentication method.

NOTE

The account you selected must have the home directory created on the Linux server.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add the credentials. For more information, see Managing Credentials.

To add a Linux server that you want to use as a hardened repository, click Ad d and select Sing le-use
credentials for hardened repository. For more information about preparing a Linux server and setting up
credentials, see Adding Hardened Repository.

NOTE

If you add a Linux server with single-use credentials, consider the following:

• The folder with the repository must be accessible for accounts with user permissions (and not
only root).
• SSH connection is necessary only for the deployment and upgrade of Veeam Data Mover, or
transport service. The transport service will be used to communicate with backup
infrastructure components without the SSH connection. For security purposes, after you
added the Linux server, you can disable SSH connection for the user account you use to
connect to the Linux server. If you can work with the server from the console, disable SSH
connection for the server itself.

688 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. To configure SSH settings, click Ad vanced. This option becomes available after you have entered your
credentials. In the SSH Settings window:

a. In the Service console connection section, specify an SSH timeout. By default, the SSH timeout is set
to 20000 ms. If a task targeted at the Linux server is inactive after the specified timeout,
Veeam Backup & Replication will automatically terminate the task.

b. In the Da ta transfer options section, specify connection settings for file copy operations. Provide a
range of ports that will be used as transmission channels between the source host and target host
(one port per task). By default, Veeam Backup & Replication uses port range 2500-3300. If the virtual
environment is not large and data traffic will not be significant, you can specify a smaller range of
ports, for example, 2500-2509 to run 10 concurrent tasks at the same time.

Port 6162 is opened by default. It is a port used by Veeam Data Mover.

NOTE

If you want to open these ports only for certain firewalld zones, you can specify the required
zones in the configuration files. For instructions, see the Before You Begin section.

c. [For Linux server deployed outside NAT] In the P referred TCP connection role section, select the Run
server on this side check box. In the NAT scenario, the outside client cannot initiate a connection to
the server on the NAT network. As a result, services that require initiation of the connection from
outside can be disrupted. With this option selected, you will be able to overcome this limitation and
initiate a ‘server-client’ connection — that is, a connection in the direction of the Linux server.

The option applies if one of the following roles is assigned to the server: source VMware backup proxy
in backup or replication scenarios, source repository in the backup copy scenario.

You can also change the SSH port over which you want to connect to the Linux server. For this, click the
Ma nage accounts link and edit the account used to connect to the Linux server.

689 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. When you add a Linux server, Veeam Backup & Replication saves a fingerprint of the Linux host SSH key to
the configuration database. During every subsequent connection to the server,
Veeam Backup & Replication uses the saved fingerprint to verify the server identity and avoid the man-in-
the-middle attack.

To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint:

o If you trust the server and want to connect to it, click Y es .

o If you do not trust the server, click No. Veeam Backup & Replication will display an error message, and
you will not be able to connect to the server.

NOTE

When you update an SSH key on a server, this server becomes unavailable in the
Veeam Backup & Replication console. To make the server available again, acknowledge the new SSH
key at the SSH Connection step of the Edit Server wizard.

690 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
At the Review step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and what components will be installed.

1. Review the components.

2. Click Ap p ly to add the Linux server to the backup infrastructure.

691 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all the required
components. Click Nex t to complete the adding of the server.

692 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of Linux server adding.

1. Review details of the Linux server.

2. Click Nex t, then click Finish to exit the wizard.

693 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Rescanning Servers
In some cases, you may need to rescan hosts or servers in the backup infrastructure. The rescan operation may
be required if you have added or removed new disks and volumes to/from the host or server and want to display
actual information in Veeam Backup & Replication. During the rescan operation, Veeam Backup & Replication
retrieves information about disks and volumes that are currently connected to a host or server and stores this
information to the configuration database.

Veeam Backup & Replication automatically performs a rescan operation every 4 hours. You can also start the
rescan operation manually:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the server or host and click Rescan on the ribbon. Alternatively, you can right-
click the server or host and select Rescan.

694 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Server Settings
To edit settings of a server in the backup infrastructure:

1. Open the Ba ckup Infrastructure view.

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

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

4. You will follow the same steps as you have followed when adding the server. Edit server settings as
required.

695 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Servers
If you do not plan to use some server anymore, you can remove it from the backup infrastructure.

You cannot remove a server that has any dependencies. For example, you cannot remove a server that is
referenced by a backup or replication job, performs the role of a off-host backup proxy or backup repository. To
remove such server, you will need to delete all referencing jobs and roles first.

When you remove a server that is used as a target host or backup repository, backup files and replica files are
not removed from disk. You can easily import these files later to Veeam Backup & Replication if needed. To
remove a server from the backup infrastructure:

1. Open the Ba ckup Infrastructure view.

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

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

696 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
General-Purpose Backup Proxies
A general-purpose backup proxy is a component that operates as a data mover. The backup proxy processes jobs
and delivers backup and restore traffic.

General-purpose backup proxies can be used for the following operations:

• Unstructured Data Backup. In this case, proxies transfer data between an unstructured data source and a
backup repository.

• Veeam Agent and storage system snapshot integration. In this case, proxies transfer data between a
storage system and a backup repository. For more information on Veeam Agent Integration, see the
Storage Snapshots Support section in the Veeam Agent Management Guide.

General-Purpose Backup Proxy Deployment


By default, the role of the general-purpose backup proxy is assigned to the backup server itself. However, this
option is sufficient only for small installations where all components are located in the same network segment.
For larger installations with larger workload, assign the role of a backup proxy to a dedicated server, as
described in the Adding General-Purpose Backup Proxies section.

To optimize performance of several concurrent tasks, you can use several backup proxies. In this case,
Veeam Backup & Replication will distribute the backup or restore workload between available backup proxies on
per-task basis, taking into account proxy connectivity and their current load.

To minimize the network load during backup, locate the backup proxy closer to the source file share or storage
in the computer network: at the best they should be one hop away from each other.

Backup Proxy Services and Components


General-purpose backup proxies run light-weight services that take a few seconds to deploy. Deployment is
fully automated. Veeam Backup & Replication installs the following components and services:

• Veeam Backup VSS Integration is a service that manages Microsoft VSS snapshots. Used for file backup.

• Veeam VSS Hardware Snapshot Provider is a service that extends Microsoft VSS and enables backups from
storage snapshots. Used for Veeam Agents.

• Veeam Installer Service is an auxiliary service that is installed and started on any Windows server once it is
added to the list of managed servers in the Veeam Backup & Replication console. This service analyzes the
system, installs and upgrades necessary components and services depending on the role selected for the
server.

Requirements for General-Purpose Backup Proxy


Before you add a backup proxy to the inventory of the virtual infrastructure, check the following prerequisites:

• The backup proxy meets system requirements.

• The backup proxy for file backup and Veeam agent and storage system snapshot integration is a Microsoft
Windows-managed server. For object storage backup, you can also use linux proxy servers.

• [For Veeam Agent and Storage System Snapshot Integration] Check limitations listed in the Storage
Support section in the Veeam Agent Management Guide.

697 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding General-Purpose Backup Proxies
You must add to the backup infrastructure one or more backup proxies that you plan to use for moving backup
data in the unstructured data backup or Veeam Agent and storage system snapshot integration.

698 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Proxy Wizard
To launch the New Backup Proxy wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Proxies node and select Ad d proxy. Alternatively, you can
click Ad d Proxy on the ribbon.

3. In the Ad d Backup Proxy window, select General-purpose backup proxy.

699 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Choose Microsoft Windows Server
At the Server step of the wizard, specify server settings for the backup proxy.

1. From the Choose server list, select a Linux (for object storage backup only) or Microsoft Windows server
that you want to use as a backup proxy.

The list of servers contains only those managed servers that are added to the backup infrastructure. If the
server is not added to the backup infrastructure yet, you can click Ad d New to open the New W indows
Server or New Linux Server wizard. For more information, see the Adding Microsoft Windows Servers and
Adding Linux Servers sections.

2. In the P roxy description field, provide a description for future reference. The default description contains
information about the user who added the backup proxy, date and time when the backup proxy was
added.

3. In the Ma x concurrent tasks field, specify the number of tasks that the backup proxy can process in
parallel.

If the number of parallel tasks reaches this value, the backup proxy will not start a new task until one of
current tasks completes. Veeam Backup & Replication creates one task per every source file share. The
recommended number of concurrent tasks is calculated automatically based on the amount of available
resources. Backup proxies with multi-core CPUs can handle more concurrent tasks.

For example, for a 4-core CPU, it is recommended that you specify a maximum of 8 concurrent tasks, for
an 8-core CPU — 16 concurrent tasks. When defining the number of concurrent tasks, keep in mind
network traffic throughput in the infrastructure.

700 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Configure Traffic Rules
At the Tra ffic Rules step of the wizard, configure network traffic rules. These rules help you throttle and encrypt
traffic transferred between backup infrastructure components. For more information, see Configuring Network
Traffic Rules.

The list of network traffic rules contains only rules applied to the backup proxy: its IP address falls into the IP
range configured for the rule.

To view settings configured for the rule:

1. Select the rule in the list.

2. Click View. The View Network Traffic Rule window will display settings configured for the rule.

To modify network traffic settings:

1. Click the Ma nage network traffic rules link.

2. The Global Network Traffic Rules window will display the full list of all existing global network traffic
rules.

3. Select the rule that you want to modify and click E d it. For more information on how to configure network
traffic rules, see Configuring Network Traffic Rules.

701 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components to Install
At the Review step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and click Ap p ly to start installation of missing components.

702 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply Backup Proxy Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components. Click Nex t to complete the procedure of the backup proxy role assignment to the server.

703 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup proxy and click Finish to exit the wizard.

704 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Off-Host Backup Proxies
An off-host backup proxy is a component required for off-host backup mode. You can deploy an off-host backup
proxy to remove unwanted overhead on the production Hyper-V host. In this case, the off-host backup proxy
will retrieve VM data from the source datastore, process it and transfer it to the destination. For more
information, see Off-Host Backup.

Off-Host Backup Proxy Deployment


When you assign the role of an off-host backup proxy to the selected machine, Veeam Backup & Replication
automatically installs on it light-weight components and services required for backup proxy functioning. Unlike
the backup server, backup proxies do not require a dedicated SQL database — all settings are stored centrally,
within the configuration database used by Veeam Backup & Replication.

NOTE

Versions of a Microsoft Hyper-V host and off-host backup proxy must coincide. For more information, see
System Requirements.

Off-Host Backup Proxy Services


To enable a Hyper-V host or a Windows machine to act as an off-host backup proxy,
Veeam Backup & Replication installs the following services on it:

• Veeam Installer Service is an auxiliary service that is installed and started on any Windows (or Hyper -V)
server once it is added to the list of managed servers in the Veeam Backup & Replication console. This
service analyzes the system, installs and upgrades necessary components and services.

• Veeam Data Mover is a component that performs data processing tasks on behalf of
Veeam Backup & Replication, such as retrieving source VM data, performing data deduplication and
compression, and storing backed-up data on the target storage.

• Veeam Hyper-V Integration Service is responsible for communicating with the VSS framework during
backup, replication and other jobs, and performing recovery tasks. The service also deploys a driver that
handles changed block tracking for Hyper-V.

General Requirements for Off-Host Backup Proxy


A machine performing the role of an off-host backup proxy must meet the following requirements:

• The machine must meet the system requirements. For more information, see System Requirements.

• The role of an off-host backup proxy can be assigned only to a physical machine.

For evaluation and testing purposes, you can assign the off-host backup proxy role to a VM. To do this,
you must enable the Hyper-V role on this VM (use nested virtualization). For more information, see
Nesting Hyper-V with VMware Workstation 8 and ESXi 5 or How to Install Hyper-V on a Virtual Machine in
Hyper-V articles. However, it is not recommended that you use virtualized off-host backup proxies in the
production environment.

• Before assigning the role of the off-host backup proxy to a machine, you must first add a Microsoft Hyper-
V server to the backup infrastructure.

705 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Off-Host Backup Proxy and CSV (SAN)
Storage
If you back up VMs located on a CSV (SAN) storage, a machine performing the role of an off -host backup proxy
must meet the following requirements:

• If you plan to perform off-host backup for a Microsoft Hyper-V cluster with CSV, you must deploy an off-
host backup proxy on a host that is not a part of the cluster. If the off-host backup proxy is deployed on a
node of the cluster, the cluster will fail during VM data processing.

• The source Microsoft Hyper-V host and the off-host backup proxy must be connected to the shared
storage through a SAN configuration. Make sure that the off-host backup proxy has read access to the
storage LUNs.

• If you back up or replicate VMs whose disks reside on a CSV with Data Deduplication enabled, make sure
that the versions of a Microsoft Hyper-V host and off-host backup proxy coincide and the Data
Deduplication option is enabled on this off-host backup proxy. Otherwise, off-host backup will fail.

• To create and manage volume shadow copies on the shared storage, you must install and properly
configure a VSS hardware provider that supports transportable shadow copies on the off -host proxy and
each production Microsoft Hyper-V host. Typically, when configuring a VSS hardware provider, you need
to specify a server controlling the LUN and disk array credentials to provide access to the array.

The VSS hardware provider is usually distributed as a part of client components supplied by the storage
vendor. Any VSS hardware provider certified by Microsoft is supported. Some storage vendors may require
additional software and licensing to work with transportable shadow copies.

Requirements for Off-Host Backup Proxy and SMB Shared


Storage
If you back up VMs located on an SMB shared storage, a machine performing the role of an off -host backup
proxy must meet the following requirements in addition to the general requirements listed earlier in this
section:

• The off-host backup proxy must have read access to the SMB shared storage.

• The LocalSystem account of the off-host backup proxy must have read access permissions on the
Microsoft SMB3 file share.

• The off-host backup proxy must be located in the same domain where the Microsoft SMB3 server resides.
Alternatively, the domain where the Microsoft SMB3 server resides must be trusted by the domain in
which the off-host backup proxy is located.

Limitations of Off-Host Backup Proxy


Do not use an off-host backup proxy to back up a VM with the VHD Set feature enabled. Otherwise, a backup job
protecting such a VM will fail.

706 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Off-Host Backup Proxies
You can configure one or more off-host backup proxies in the backup infrastructure.

Before you add an off-host backup proxy, check prerequisites. Then use the New Hyper-V Off-Host Backup
P roxy wizard to add the off-host backup proxy.

707 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Hyper-V Off-Host Backup Proxy Wizard
To launch the New Hyper-V Off-Host Backup Proxy wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Proxies node and select Ad d Proxy. Alternatively, you can
click Ad d Proxy on the ribbon.

3. In the Ad d Backup Proxy window, select Hy p er-V off-host backup proxy.

708 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Choose Server
At the Server step of the wizard, specify server settings for the off-host backup proxy.

1. From the Choose server list, select a Microsoft Windows server to which you want to assign the off-host
backup proxy role. If the server is not added to the backup infrastructure yet, you can click Ad d New to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the P roxy description field, provide a description for future reference. The default description contains
information about the user who added the off-host backup proxy, date and time when the off-host backup
proxy was added.

3. In the Connected volumes field, specify from which volumes the off-host backup proxy must be able to
retrieve VM data. By default, Veeam Backup & Replication automatically detects all volumes accessible by
the off-host backup proxy.

You can set up the list of volumes manually if you want the off-host backup proxy to work with specific
volumes. Click Choose on the right of the Connected volumes field, choose Ma nual selection and add
volumes from which the off-host backup proxy must be able to retrieve VM data.

4. In the Ma x concurrent tasks field, specify the number of tasks that the off-host backup proxy must handle
in parallel. If this value is exceeded, the off-host backup proxy will not start a new task until one of
current tasks is finishes.

Veeam Backup & Replication creates one task per every VM disk. The recommended number of concurrent
tasks is calculated automatically based on available resources. Off-host backup proxies with multi-core
CPUs can handle more concurrent tasks. For example, for a 4-core CPU, it is recommended to specify
maximum 8 concurrent tasks, for an 8-core CPU — 16 concurrent tasks. When defining the number of
concurrent tasks, consider network traffic throughput in the virtual infrastructure.

709 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Configure Traffic Rules
At the Tra ffic Rules step of the wizard, configure network traffic rules. These rules help you throttle and encrypt
traffic transferred between backup infrastructure components. For more information, see Configuring Network
Traffic Rules.

The list of network traffic rules contains only the rules that are applicable to the off -host backup proxy. The rule
is applied to the off-host backup proxy if the IP address of the off-host backup proxy falls into an IP range of
the rule.

To view rule settings:

1. Select the rule in the list.

2. Click View on the right of the rule list.

You can open global network traffic settings and modify them directly from the New Hyper-V Off-Host P roxy
wizard. To do this, click the Ma nage network traffic rules link at the bottom of the wizard.

710 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
At the Review step of the wizard, review what Veeam Backup & Replication components are already installed on
the off-host backup proxy and what components will be installed.

1. Review the components.

2. Click Nex t to add the off-host backup proxy.

711 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Ap p ly step of the wizard, complete the procedure of off-host backup proxy configuration.

1. Review details of the off-host backup proxy.

2. Click Nex t, then click Finish to exit the wizard.

712 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Backup Proxy Settings
You can edit settings of off-host backup proxies you have configured.

To edit off-host backup proxy settings:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the off-host backup proxy and click E d it Proxy on the ribbon or right-click the
off-host backup proxy and select P roperties.

4. Edit off-host backup proxy settings as required.

713 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling and Removing Backup Proxies
You can temporarily disable an off-host backup proxy or remove it from the backup infrastructure.

Disabling Backup Proxies


When you disable an off-host backup proxy, Veeam Backup & Replication does not use this off-host backup
proxy for any jobs configured on the backup server. Off-host backup proxy disabling can be helpful if you
instruct Veeam Backup & Replication to automatically select off-host backup proxies for jobs and do not want
Veeam Backup & Replication to use specific off-host backup proxies.

To disable an off-host backup proxy:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the off-host backup proxy and click Disable Proxy on the ribbon or right-click
the off-host backup proxy and select Disable proxy.

You can enable a disabled off-host backup proxy at any time:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the off-host backup proxy and click Disable Proxy on the ribbon once again or
right-click the off-host backup proxy and select Disable proxy.

Removing Backup Proxies


You can permanently remove an off-host backup proxy from the backup infrastructure. When you remove an
off-host backup proxy, Veeam Backup & Replication unassigns the off-host backup proxy role from the server,
and this server is no longer used as an off-host backup proxy. The actual server remains in the backup
infrastructure.

You cannot remove an off-host backup proxy that is explicitly selected in any backup or replication job. To
remove such off-host backup proxy, you first need to delete a reference to this off-host backup proxy in the job
settings.

To remove a backup proxy:

1. Open the Ba ckup Infrastructure view.

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

714 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the off-host backup proxy and click Remove Proxy on the ribbon or right-click
the off-host backup proxy and select Remove.

715 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Advanced Options for Off-Host
Backup Proxies
When you configure a backup or replication job, you can instruct Veeam Backup & Replication to automatically
assign an off-host backup proxy to the job. To select an appropriate off-host backup proxy,
Veeam Backup & Replication uses a static topology scheme — a scheme of available connections in the backup
infrastructure. The static topology scheme is updated once in 4 hours, when Veeam Backup & Replication
performs automatic rescan of backup infrastructure components.

In some situations, the static topology scheme may not be enough. In some storage systems (for example, iSCSI
SAN), the hardware VSS provider configures connections to volume snapshots on the fly. When a volume
snapshot is created, the hardware VSS provider automatically creates a new target for the volume snapshot or
enables a connection to the volume snapshot for the off-host backup proxy.

In such case, the mechanism of automatic off-host backup proxy detection will not work properly. To overcome
this situation, you can manually present volumes to the off-host backup proxy and assign the necessary off-host
backup proxy to the job.

Presenting Volumes to Off-Host Backup Proxies


To present volumes to an off-host backup proxy:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the off-host backup proxy and click E d it Proxy on the ribbon or right-click the
off-host backup proxy and select P roperties.

4. At the Server step of the wizard, click Choose next to the Connected volumes field.

716 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. In the Connected Volumes window, choose Ma nual selection and click P op ulate.
Veeam Backup & Replication will display a list of volumes accessible by the off-host backup proxy.

6. If the off-host backup proxy has access to a volume but the volume is not in the list, you can add it
manually. To do that, click Ad d and select the necessary volume.

Assigning Off-Host Backup Proxies to Jobs


If the automatic proxy detection mechanism does not work correctly, you can manually assign an off -host
backup proxy to a job.

1. Open the Home view.

2. In the inventory pane, select the Job s node.

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

717 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. At the Storage step of the wizard, click Choose next to the Ba ckup proxy field.

5. Select the Use the following backup proxy servers only check box.

6. Select check boxes next to off-host backup proxies you want to use for the job.

718 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When you start the configured job, Veeam Backup & Replication will check the topology scheme of connections
for off-host backup proxies that you have selected in the list and choose one of them for the job. If none of
these backup proxies can be used for the job and you have selected the Fa ilover to on-host backup mode if no
suitable off-host proxies available check box, Veeam Backup & Replication will fail over to the on-host backup
mode. If you have not enabled the failover option, the job will fail.

719 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cache Repositories
A cache repository is a storage location where Veeam Backup & Replication keeps temporary cached metadata
for the data backed up by the file backup jobs and object storage backup jobs. For more information about the
cache repository, see the Backup Infrastructure for Unstructured Data Backup section.

720 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Repositories
A backup repository is a storage location where Veeam keeps backup files and metadata for replicated VMs. To
configure a backup repository, you can use the following storage types:

• Direct attached storage. You can add virtual and physical servers as backup repositories:

o Microsoft Windows server

o Linux server

o Hardened Repository

• Network attached storage. You can add the following network shares as backup repositories:

o SMB (CIFS) share

o NFS share

• Ded uplicating storage appliances. You can add the following deduplicating storage appliances as backup
repositories:

o Dell Data Domain

o ExaGrid

o Fujitsu ETERNUS CS800

o HPE StoreOnce

o Infinidat InfiniGuard

o Quantum DXi

• Ob ject storage . You can use cloud storage services as backup repositories. For details, see Object Storage
Repository.

NOTE

Consider the following:

• Do not configure multiple backup repositories pointing to the same location or using the same path.
• Do not configure multiple backup repositories with "nested" paths (when one repository path is a
sub-path of another repository), for example:
/mnt/repo/backups/
/mnt/repo/backups/production/

Related Topics
• Scale-Out Backup Repository

• External Repository

721 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Windows Server
You can use a Microsoft Windows server with local or directly attached storage as a backup repository. The
storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), or iSCSI/FC SAN LUN
in case the server is connected into the SAN fabric.

Microsoft Windows Repository Deployment


To communicate with a Microsoft Windows-based repository, Veeam Backup & Replication uses two Data
Movers that are responsible for data processing and transfer:

• Veeam Data Mover on a off-host backup proxy

• Veeam Data Mover on the Microsoft Windows repository

When any job addresses the backup repository, Veeam Data Mover on the off -host backup proxy establishes a
connection with Veeam Data Mover on the backup repository, enabling efficient data transfer ov er LAN or WAN.

The Data Mover is installed automatically when you add a server to Veeam Backup & Replication as a managed
server.

Requirements for Microsoft Windows Server Based


Repositories
A machine performing the role of a repository must meet the following requirements:

• The role of the repository can be assigned to a Microsoft Windows machine (physical or virtual). The
machine must meet the system requirements. For more information, see System Requirements.

• You must add the machine to the Veeam Backup & Replication console as a managed server.

• If you want to use Fast Clone in the Microsoft Windows backup repository, the machine must also meet
requirements listed in section Fast Clone.

Adding Microsoft Windows Repositories


This section describes how to add a Microsoft Windows server as a backup repository.

To add a backup repository, use the New Backup Repository wizard.

722 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Direct Attached Storage > Microsoft W indows.

723 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Backup Repository Name and Description
At the Na me step of the wizard, specify a name and description for the backup repository:

1. In the Na me field, specify a name for the backup repository.

2. In the Description field, provide a description for future reference.

724 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Server or Shared Folder Settings
To configure settings for a Microsoft Windows server:

1. From the Rep ository server list, select a Microsoft Windows server that you want to use as a backup
repository. The Rep ository server list contains only those servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, you can click Ad d New on the
right to open the New W indows Server wizard.

2. Click P op ulate to see a list of disks connected to the server, their capacity and free space.

725 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Backup Repository Settings
At the Rep ository step of the wizard, configure general repository settings including path to the repository
folder and load control, and also advanced repository settings.

Configuring General Repository Settings


To configure general repository settings:

1. In the Loca tion section, specify a path to the folder where backup files must be stored. Click P op ulate to
check capacity and available free space in the selected location.

2. Use the Loa d control section to limit the number of concurrent tasks and data ingestion rate for the
backup repository. These settings will help you control the load on the backup repository and prevent
possible timeouts of storage I/O operations.

o Select the Limit maximum concurrent tasks check box and specify the maximum allowed number of
concurrent tasks for the backup repository. If this value is exceeded, Veeam Backup & Replication will
not start a new task until one of current tasks finishes. For more information, see Limiting the Number
of Concurrent Tasks.

NOTE

It is not recommended that you disable the Limit maximum concurrent tasks to N option for
backup repositories with per-machine backup chains. In case of per-machine backup chains,
synthetic operations (synthetic full backup, backup files merge and transformation) work in
parallel for every workload in the backup. The number of parallel operations is limited by the
number of concurrent tasks that can be performed on the backup repository. If you disable the
Limit maximum concurrent tasks to N option (which results in using an unlimited number of
slots), the load on the backup repository may be high.

o Select the Limit read a nd write data rates to check box and specify the maximum rate to restrict the
total speed of reading and writing data to the backup repository disk. For more information, see
Limiting Combined Data Rate for Backup Repositories.

NOTE

The Limit read and write data rates to settings does not apply to health checks performed as
part of backup and backup copy jobs. Even if you limit read/write rate for a backup repository,
the health check will consume resources of the backup repository regardless of this setting.
Consider this limitation when configuring basic and health check schedules for backup and
backup copy jobs.

726 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Advanced Repository Settings
To configure advanced repository settings:

1. Click Ad vanced.

2. For storage systems using a fixed block size, select the Align backup file data blocks check box.
Veeam Backup & Replication will align VM data saved to a backup file at a 4 KB block boundary.

3. When you enable compression for a backup job, Veeam Backup & Replication compresses VM data at the
source side and then transports it to the target side. Writing compressed data to a deduplicating storage
appliance results in poor deduplication ratios as the number of matching blocks decreases. To overcome
this situation, select the Decompress backup data blocks before storing check box. If data compression is
enabled for a job, Veeam Backup & Replication will compress VM data on the source side, transport it to
the target side, decompress VM data on the target side and write raw VM data to the storage device to
achieve a higher deduplication ratio.

NOTE

Veeam Backup & Replication does not compress VM data if encryption is enabled for a job and the
Decompress backup data blocks before storing check box is selected in the settings of the target
backup repository. Therefore, in the job statistics, you may observe a higher amount of transferred
data (the Tra nsferred counter) as compared to a job for which encryption is disabled. For more
information on job statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the
Ba ckup Size column) is larger than the original VM size (the Orig inal Size column). For more
information on backup properties, see Viewing Backup Properties.

727 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Select the This repository is backed by rotated drives check box if you plan to use a backup repository with
rotated drives. For more information on how to configure rotated drives, see Configuring Backup
Repositories with Rotated Drives.

5. To create a separate backup file for every machine in the job, make sure that the Use per-machine backup
files check box is selected. If you clear the check box, Veeam Backup & Replication will create single-file
backups. For more information on the backup chain formats and their limitations, see Backup Chain
Formats.

NOTE

Changing of the Use p er-machine backup files setting after the repository was already created does
not take any effect. To change backup chain format, follow the instructions provided in Upgrading
Backup Chain Formats.

728 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore.

1. From the Mount Server list, select a server that you want to use as a mount server. The mount server is
required for file-level and application items restore. During the restore process,
Veeam Backup & Replication will mount the VM disks from the backup file residing in the backup
repository to the mount server. As a result, VM data will not have travel over the network, which will
reduce the load on the network and speed up the restore process. For more information, see Mount
Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder that will be used for writing cache during
mount operations.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

729 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Properties and Components
At the Review step of the wizard, review details of the backup repository and specify importing settings.

1. Review the backup repository settings and list of components that will be installed on the backup
repository server.

2. If the backup repository contains backups that were previously created by Veeam Backup & Replication,
select the Sea rch the repository for existing backups a nd import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and display
them in the Veeam Backup & Replication console under the Imported > Backups node.

3. If the backup repository contains guest file system index files that were previously created by
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be
imported with backup files, and you will be able to search for guest OS files inside imported backups.

730 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Backup Repository Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the backup repository to the backup
infrastructure.

731 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup repository. Then click Finish to exit the
wizard.

732 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Linux Server
You can add a Linux server with local, directly attached storage or mounted NFS as a backup repository. The
storage can be a local disk, directly attached disk-based storage (such as a USB hard drive), NFS share, or
iSCSI/FC SAN LUN in case the server is connected into the SAN fabric.

A Linux repository with single-use credentials and the immutability feature provides additional protection for
your backup files. For more information, see Hardened Repository.

Linux Backup Repository Deployment


To communicate with a Linux-based repository, Veeam Backup & Replication uses two Veeam Data Movers that
are responsible for data processing and transfer:

• Veeam Data Mover on the backup proxy

• Veeam Data Mover on the Linux backup repository

For more information about Veeam Data Movers communication with a Linux -based server, see Veeam Data
Movers.

Veeam Data Mover establishes a connection with the source-side Data Mover on the backup proxy, enabling
efficient data transfer over LAN or WAN.

Requirements for Linux Backup Repositories


A machine performing the role of a repository must meet the following requirements:

• The role of the repository can be assigned to a Linux machine (physical or virtual). The machine must meet
the system requirements. For more information, see System Requirements.

• You must add the machine to the Veeam Backup & Replication console as a managed server.

• If Veeam Data Mover is non-persistent, Veeam Backup & Replication uses the SSH protocol to
communicate with Linux backup repositories and requires the SCP utility in Linux repositories. Make sure
that the SSH daemon is properly configured and SCP utility is available on the Linux host.

• If you want to use Fast Clone in the Linux backup repository, the machine must also meet requirements
listed in section Fast Clone.

733 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can place both repositories (hardened and standard) on one Linux server only if you used single -use
credentials when adding the host. Standard repository is a repository added with persistent credentials and
disabled immutability. For more hardened repository limitations, see Requirements and Limitations.

Adding Linux Repositories


This section describes how to add a Linux server as a backup repository.

To add a backup repository, use the New Backup Repository wizard.

734 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Direct Attached Storage > Linux.

735 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Backup Repository Name and Description
At the Na me step of the wizard, specify a name and description for the backup repository:

1. In the Na me field, specify a name for the backup repository.

2. In the Description field, provide a description for future reference.

736 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Server Settings
To configure settings for a Linux server:

1. From the Rep ository server list, select the Linux server that you want to use as a backup repository.

The Rep ository server list contains only those servers that are added to the backup infrastructure. If the
server is not added to the backup infrastructure yet, you can click Ad d New on the right to open the New
Linux Server wizard.

NOTE

Note that you cannot add ExaGrid, Quantum DXi, Fujitsu ETERNUS CS800 and Infinidat InfiniGuard
servers as Linux backup repositories. These servers are integrated with Veeam Backup & Replication,
and thus must be added as deduplicating storage appliances.

2. Click P op ulate to see a list of disks connected to the server, their capacity and free space.

737 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Backup Repository Settings
At the Rep ository step of the wizard, configure general repository settings including path to the repository
folder and load control, and also advanced repository settings.

Configuring General Repository Settings


To configure general repository settings:

1. In the Loca tion section, specify a path to the folder where backup files must be stored. Click P op ulate to
check capacity and available free space in the selected location.

2. Select the Use fast cloning on XFS volumes check box to enable copy-on-write functionality. In terms of
Veeam Backup & Replication, this functionality is known as Fast Clone. For more information, see Fast
Clone.

3. Use the Loa d control section to limit the number of concurrent tasks and data ingestion rate for the
backup repository. These settings will help you control the load on the backup repository and prevent possible
timeouts of storage I/O operations.

• Select the Limit maximum concurrent tasks check box and specify the maximum allowed number of
concurrent tasks for the backup repository. If this value is exceeded, Veeam Backup & Replication
will not start a new task until one of current tasks finishes. For more information, see Limiting the
Number of Concurrent Tasks.

NOTE

It is not recommended that you disable the Limit maximum concurrent tasks to N option for backup
repositories with per-machine backup chains. In case of per-machine backup chains, synthetic
operations (synthetic full backup, backup files merge and transformation) work in parallel for every
workload in the backup. The number of parallel operations is limited by the number of concurrent
tasks that can be performed on the backup repository. If you disable the Limit maximum concurrent
ta sks to N option (which results in using an unlimited number of slots), the load on the backup
repository may be high.

• Select the Limit read a nd write data rate to check box and specify the maximum rate to restrict the
total speed of reading and writing data to the backup repository disk. For more information, see
Limiting Combined Data Rate for Backup Repositories.

NOTE

The Limit read and write data rate to settings does not apply to health checks performed as part of
backup and backup copy jobs. Even if you limit read/write rate for a backup repository, the health
check will consume resources of the backup repository regardless of this setting. Consider this
limitation when configuring basic and health check schedules for backup and backup copy jobs.

738 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Advanced Repository Settings
To configure advanced repository settings:

1. Click Ad vanced.

2. For storage systems using a fixed block size, select the Align backup file data blocks check box.
Veeam Backup & Replication will align VM data saved to a backup file at a 4 KB block boundary.

3. When you enable compression for a backup job, Veeam Backup & Replication compresses VM data at the
source side and then transports it to the target side. Writing compressed data to a deduplicating storage
appliance results in poor deduplication ratios as the number of matching blocks decreases. To overcome
this situation, select the Decompress backup data blocks before storing check box. If data compression is
enabled for a job, Veeam Backup & Replication will compress VM data on the source side, transport it to
the target side, decompress VM data on the target side and write raw VM data to the storage device to
achieve a higher deduplication ratio.

NOTE

Veeam Backup & Replication does not compress VM data if encryption is enabled for a job and the
Decompress backup data blocks before storing check box is selected in the settings of the target
backup repository. Therefore, in the job statistics, you may observe a higher amount of transferred
data (the Tra nsferred counter) as compared to a job for which encryption is disabled. For more
information on job statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the
Ba ckup Size column) is larger than the original VM size (the Orig inal Size column). For more
information on backup properties, see Viewing Backup Properties.

739 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Select the This repository is backed by rotated drives check box if you plan to use a backup repository with
rotated drives. For more information on how to configure rotated drives, see Configuring Backup
Repositories with Rotated Drives.

5. To create a separate backup file for every machine in the job, make sure that the Use per-machine backup
files check box is selected. If you clear the check box, Veeam Backup & Replication will create single-file
backups. For more information on the backup chain formats and their limitations, see Backup Chain
Formats.

NOTE

Changing of the Use p er-machine backup files setting after the repository was already created does
not take any effect. To change backup chain format, follow the instructions provided in Upgrading
Backup Chain Formats.

740 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore.

1. From the Mount Server list, select a server that you want to use as a mount server. The mount server is
required for file-level and application items restore. During the restore process,
Veeam Backup & Replication will mount the VM disks from the backup file residing in the ba ckup
repository to the mount server. As a result, VM data will not have travel over the network, which will
reduce the load on the network and speed up the restore process. For more information, see Mount
Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder that will be used for writing cache during
mount operations.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

741 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Properties and Components
At the Review step of the wizard, review details of the backup repository and specify importing settings.

1. Review the backup repository settings and list of components that will be installed on the backup
repository server.

2. If the backup repository contains backups that were previously created by Veeam Backup & Replication,
select the Sea rch the repository for existing backups a nd import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and display
them in the Veeam Backup & Replication console under the Imported > Backups node.

3. If the backup repository contains guest file system index files that were previously created by
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be
imported with backup files, and you will be able to search for guest OS files inside imported backups.

742 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Backup Repository Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the backup repository to the backup
infrastructure.

743 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup repository. Then click Finish to exit the
wizard.

744 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Hardened Repository
To protect your backup files from loss as a result of malware activity or unplanned actions, you can add to your
backup infrastructure a hardened repository based on a Linux server. The hardened repository supports the
following features:

• Immutability: when you add a hardened repository, you specify the time period while backup files must be
immutable. During this period, backup files stored in this repository cannot be modified or deleted.

• Sing le-use credentials: credentials that are used only once to deploy Veeam Data Mover, or transport
service, while adding the Linux server to the backup infrastructure. These credentials are not stored in the
backup infrastructure. Even if the Veeam Backup & Replication server is compromised, the attacker cannot
get the credentials and connect to the hardened repository.

NOTE

For security reasons, you cannot assign other roles to the hardened repository.

About Hardened Repository


In the hardened repository, you can store the following backups created by backup and backup copy jobs:

• Image-level virtual machine backups and backup copies (VMware, Hyper-V, Cloud Director, Nutanix AHV,
RHV)

• Physical machine backups and backup copies (Microsoft Windows, Linux, MacOS, AIX, Solaris)

• Cloud machine backup copies (Microsoft Azure, AWS, Google Cloud Platform)

• Unstructured data backups (file backups and object storage backups) and their backup copies

• Application-aware processing log backups and backup copies (Microsoft SQL transaction log files, Oracle
archived log files, PostgreSQL WAL files)

• Enterprise application backups and backup copies (SAP HANA, Oracle RMAN, SAP on Oracle, Microsoft SQL
Server)

Also, backups created by VeeamZIP, Copy Backup jobs, Move Backup jobs, and Export Backup jobs are
supported.

In This Section
• How Immutability Works

• Hardened Repository as Performance Extent

How Immutability Works


Immutability is managed by the Veeam Data Mover Service (veeamtransport) and the Veeam Immutability
Service (veeamimmureposvc). After installation, the Veeam Data Mover Service runs as a non-root user. It
communicates with the backup server, gets information about the immutability time period, and forwards it to
the Veeam Immutability Service that manages immutability attributes.

745 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

For communication between the backup server and the hardened repository, the Veeam Data Mover
Service uses port 6160. For communication between the backup server and other backup infrastructure
components, it uses the default port 6162. For more information, see Ports.

The Veeam Immutability Service runs with root permissions as a child process of the Veeam Data Mover Service.
It checks file immutability attributes every 20 minutes, calculates the time until a file needs to be immutable,
and sets or removes the immutable attribute.

Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), the Veeam Immutability Service also
performs timeshift detection. The mechanism works in the following way:

1. After the Veeam Immutability Service starts, it creates the /etc/veeam/immureposvc/timeLog file.
The file is updated every 10 minutes and contains the following information:

o systemTime - current UTC value (Unix timestamp)

o moveTime - timeshift value based on comparison between two metrics:

▪ difference between current and previous UTC values

▪ the value of the check interval (in seconds)

For example, the value of the check interval is 600 seconds (10 minutes). The previous UTC value is
1699367670, the current UTC value is 1699368270. The difference between current and previous
UTC values also equals 600 seconds. As two metrics have the same value, the current value of the
moveTime parameter will not change.

o hwTime - current RTC value (Unix timestamp)

o accelerationTime - timeshift value based on comparison between two metrics:

▪ difference between current and previous RTC values

▪ difference between current and previous UTC values

2. If the value of the moveTime or accelerationTime parameter exceeds 86400 seconds (24 hours),
retention operations will be blocked with the warning in the backup job session.

NOTE

Consider the following:

• To detect timeshift more precisely, RTC should be set to UTC.


• If RTC is disabled, the accelerationTime parameter value will be ignored. The Veeam
Immutability Service will check only the moveTime parameter.
• If you shut down the repository for more than 24 hours, retention operations also will be blocked.
• If retention operations are blocked, the Veeam Immutability Service will not set or remove the
immutable attribute for existing and new backup files.

To get back to the normal operation mode, you will need to access the hardened repository under the user
account with root privileges and perform the necessary operations. For more information, see this Veeam KB
article.

The described hardened repository architecture prevents backup files from being deleted or modified by a
potential attacker even if they somehow exploit the Veeam Data Mover Service or compromise the NTP server.
For more details, see Protect against Ransomware with Immutable Backups.

746 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam services required for the hardened repository are deployed and updated by the Veeam Installer Service
for Linux (veeamdeploymentsvc). For more information on how the service works, see Veeam Installer
Service.

Immutability for Image-Level VM and Physical Machine


Backups
For image-level VM backups and physical machine backups, immutability works in the following way:

1. For each backup file, Veeam Backup & Replication creates a.veeam.N.lock file that contain information
about the immutability time period. Also, the xattr attribute with immutable time period is set on each
backup file. These files are stored on the hardened repository.

2. Backup files become immutable for the configured time period (minimum 7 days, maximum — 9999). The
immutability period is set according to the following:

o The count of the immutability period starts from the moment the last restore point in the active
backup chain is created. For example:

▪ The full backup file of the active chain was created on January 12. The first increment was
created on January 13. The second and last increment was created on January 14.

▪ The immutability period is set for 10 days and will be automatically extended for all backup files
in the active chain. If there are several chains in the backup, Veeam Backup & Replication does
not extend the immutability for inactive chains.

▪ Full and incremental backup files will be immutable until January 24: the date of the last restore
point creation (January 14) + 10 days.

o The immutability flag is set on the file only when the current backup session is completed.

NOTE

For image-level VM backups, consider the following:

• If you use per-machine backup with single metadata file or per-machine backup with
separate metadata files format for storing backups and the restore point was incomplete,
the immutability flag will be set only on successfully created backup files.
• If you use single-file backup format for storing backups and the restore point was
incomplete, the immutability flag will not be set on the backup file.

For more information about backup chain formats, see Backup Chain Formats.

o If you increase the immutability period in repository settings, a new value will be applied for the
active and next chains.

o If you decrease the immutability period and a new value for the next restore point is less than the
previous one, it will be applied for the next incremental backups in the active chain and for the next
chains. For example:

▪ The immutability period is set for 20 days. The full backup file of the active chain was created
on November 1. The first increment was created on November 2. The second increment was
created on November 3. Full and incremental backup files will be immutable until November
23: the date of the last restore point creation (November 3) + 20 days.

747 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ If you decrease the immutability period to 7 days on November 4, all previous backup files in
the active chain will be immutable until November 23. The next incremental backup in the
active chain will be immutable until November 11: the date of the last restore point creation
(November 4) + 7 days.

o If you decrease the immutability period and a new value for the next restore point is greater than
the previous one, it will be applied for all backup files in the active chain and in the next chains. For
example:

▪ The immutability period is set for 20 days. The full backup file of the active chain was
created on November 1. The first increment was created on November 2. The second
increment was created on November 3. Full and incremental backup files will be immutable
until November 23: the date of the last restore point creation (November 3) + 20 days.

▪ If you decrease the immutability period to 7 days on November 22, all backup files in the
active chain will be immutable until November 29: the date of the last restore point
creation (November 22) + 7 days.

o If you use GFS retention policy, see Retention Scenarios.

▪ When the immutability time period expires, the immutability service makes backup files mutable
again so they can be deleted or modified.

Immutability for Application-Aware Processing Log


Backups
For application-aware processing log backups, immutability works in the following way:

1. For each log backup file, Veeam Backup & Replication creates a.veeam.N.lock file that contain
information about immutability time period. These files are stored on the hardened repository.

2. Log backup files become immutable for the configured time period (minimum 7 days, maximum —
9999). The immutability period is set according to the following:

o Newly created log backup files are being updated several times according to the interval
settings. Thus, the count of the immutability period starts and the immutability flag is set on the
file only when the log backup job finished writing any data to the VLB file.

o The immutability period is not extended for log backup files in the active chain. If there are
several chains in the backup, Veeam Backup & Replication also does not extend the immutability
for old chains.

IMP ORTANT

If the immutability period is expired for log backup files in the active chain, these files become
mutable and may be potentially removed. In this case, the application restore may fail as the
log backup chain became incomplete. To mitigate risks, make sure that the immutability period
covers all backups in the active backup chain.

o If you increase the immutability period in repository settings, a new value will be applied for all
log backup files created after the last successful image-level VM backup or physical machine
backup. If you decrease the immutability period, a new value will be applied only for the next log
backup files.

o If you use GFS retention policy, see Retention Scenarios.

o When the immutability time period expires, the immutability service makes backup files mutable
again so they can be deleted or modified.

748 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Immutability for Other Backups
For information on how immutability works for unstructured data backups and enterprise application backups,
see the following sections:

• Unstructured Data Backups in Immutable Repositories

• Veeam Plug-in for Oracle RMAN

• Veeam Plug-in for SAP HANA

• Veeam Plug-in for SAP on Oracle

• Veeam Plug-in for Microsoft SQL Server

Retention Scenarios
Consider the following retention scenarios:

• An immutability retention overrides a job retention: if the job retention period is shorter than the
immutability period, Veeam Backup & Replication does not delete backup files when the retention
period is over, but only when the immutability period expires.

• Veeam Backup & Replication compares the immutability period of the backup repository and the GFS
backup file lifetime, and sets an immutability period for full backup files with GFS retention policy as
equal to the longest of these periods. For example: the backup repository immutability period is 10
days; the GFS backup file lifetime is 3 years; the backup file will be immutable for 3 years; the
increments from this full backup file will be immutable for 10 days from the moment of the last
increment creation.

• The immutability period for backup files produced with VeeamZIP or Export Backup jobs is set
according to the following:

o [With enabled retention period] Veeam Backup & Replication compares the immutability period
of the backup repository and the retention period, and sets an immutability period for backup
files with retention period as equal to the longest of these periods. For example: the backup
repository immutability period is 1 month; the VeeamZIP or Export Backup backup file lifetime is
7 years; the backup file will be immutable for 7 years.

NOTE

If a hardened repository is a part of a scale-out backup repository with the capacity tier added
and the move policy enabled and is used as a target for VeeamZIP or Export Backup jobs,
Veeam Backup & Replication ignores the VeeamZIP or Export Backup retention period. The
immutability time period for VeeamZIP or Export Backup backup files equals the period
specified in the setting of a hardened repository.

o [With disabled retention period] Veeam Backup & Replication ignores the VeeamZIP or Export
Backup retention period. The immutability time period for VeeamZIP or Export Backup backup
files equals the period specified in the setting of a hardened repository.

Hardened Repository as Performance Extent


You can add a hardened repository to your scale-out backup repository as a performance extent. For more
information, see Scale-Out Backup Repository and Add Performance Extents.

749 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Immutability Limitations
Avoid mixing mutable and immutable extents within one scale-out backup repository.

If your scale-out backup repository includes hardened repositories and deduplicating storage applia nces with
enabled immutability (StoreOnce, Dell Data Domain), consider the following:

• Starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131), the immutability time period must be
the same on all extents added to this scale-out repository. If you want to change the immutability period
on any extent, a new value will be applied to all extents.

• If you want to upgrade to Veeam Backup & Replication 12.1 (build 12.1.0.2131), before starting the
operation, you must specify the same immutability period for all extents added to this scale-out
repository.

Using Hardened Repository in Capacity Tier


If you use the capacity tier with move option, note that having a hardened repository as a performance extent
will affect the capacity tier behavior. You will not be able to move immutable backup files, because they cannot
be deleted from the performance extent. Veeam Backup & Replication will copy such backup files to the
capacity tier. When the immutability time period is over, Veeam Backup & Replication will delete these files
from the performance extent. For more information on copy and move policies, s ee Copying Backups to Capacity
Tier and Moving Backups to Capacity Tier.

If a hardened repository is a part of a scale-out backup repository with the capacity tier added and the move
policy enabled, Veeam Backup & Replication ignores the GFS retention policy. The immutability time period for
full backup files equals the period specified in the setting of a hardened repository.

Evacuating Immutable Backups


If you evacuate your backups from an immutable performance extent, Veeam Backup & Replication will copy
them instead of moving. When the immutability time period is over, you will need to delete these files manually.
If the target extent is also immutable, the immutability of the target extent will apply to copied backup files.
For more information on evacuating backups, see Evacuating Backups from Extents.

When you evacuate backups to the hardened Linux extent, the immutability period of the full chain will be
chosen as maximum between the following values:

• The immutability period determined for the original chain.

• The time of creation of the last restore point in the chain plus the immutability period determined for the
target extent.

Requirements and Limitations


For the hardened repository, consider the following requirements and limitations.

Linux Server
• The role of the hardened repository can be assigned to a Linux machine with local or remotely attached
block storage. The machine must meet system requirements for backup repositories. The Linux
distribution must be 64-bit due to Veeam Data Mover requirements.

750 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

To reduce the attack surface, use a physical machine with local storage. For RAID configuration,
recommendations are the following:

• [For the operating system] RAID 1 on SSDs with at least 100 GB disk space should be used.
• [For backup data] RAID 6/60 with write-back cache should be used. At least one disk must be
configured for the drive roaming.
• Internal disk cache must be disabled.
• RAID stripe size should be 128 or 256 KB.

• The Linux machine file system must support immutable files and extended attributes modified by the
chattr and setxattr commands. We recommend using XFS for performance and space efficiency reasons
(block cloning support).

• As the hardened repository requires the block storage, you cannot use the following storage types:

o NFS share or a Linux machine with the mounted NFS volume

o ⁠A Linux machine with the mounted SMB (CIFS) volume

• You must add the Linux machine to the Veeam Backup & Replication console as a managed server. The
hardened repository cannot be shared between different Veeam Backup & Replication servers.

• The Linux machine should have redundant network connection.

Repository
• To store backup files in a repository, use only a forward incremental backup method with enabled active
full backup or synthetic full backup. Once a backup file becomes immutable, it can be merged or
deleted only when the immutability time period expires. For this reason, you cannot select a reverse or
a forever forward incremental backup method.

• For importing a backup, use VBK backup files. Metadata files of a backup chain (.VBM) cannot be
immutable because they are updated on every job pass.

Immutability Feature
• To use the immutability feature for backup copy jobs, enable the GFS retention policy. For more
information, see Long-Term Retention Policy (GFS).

• Do not use the immutability feature for a Nutanix Mine infrastructure. As Mine repositories contain thin-
provisioned disks, there may be the case when Veeam Backup & Replication uses full storage capacity of
a repository and cannot delete backup files from the file system.

Preparing Ubuntu Linux Server as Hardened Repository


This section includes security considerations for installing and configuring the Linux server that will be used as a
hardened repository. Recommendations are based on Security Technical Implementation Guides (STIGs) created
and maintained by the Defense Information Systems Agency (DISA) for Ubuntu 20.04 LTS. For more
information, see DISA STIGs Document Library.

751 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Installing Ubuntu Linux Server
To install Ubuntu 20.04 LTS, download the server install image from the Ubuntu Releases page. For more
information on the installer and options of the installation wizard, see the official Canonical guide.

Installation
During installation process, consider the following Veeam recommendations:

1. Before you boot the installer, enable UEFI secure boot to prevent unsigned Linux kernel modules from
being loaded.

2. In the GRUB menu, select the Boot and Install with the HWE kernel option to support the latest hardware.

3. At the welcome screen of the installation wizard, select the language for the installer and the default
language for the installed system. For troubleshooting purposes, it is recommended to select the English
language.

4. At the Installer update available step of the installation wizard, select the Continue without updating
option.

5. At the Key board configuration step of the installation wizard, set up the keyboard layout used in your
backup infrastructure.

6. At the Network connections step of the installation wizard, do the following:

o If you have several network interface cards, create a bond to provide the network fa ilover in case of
connection issues. For the bond mode, select one of the following options:

▪ balance-rr (if you use EtherChannel without LACP)

▪ 802.3ad (if you use EtherChannel with LACP)

752 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ active-backup (for other configurations)

Example:

o If you have only one network interface card and cannot create a bond, assign the static IP address
to the network interface to reduce the risk of connection issues, for example, with the DHCP server.

▪ At the Configure proxy step of the installation wizard, specify the proxy server if required.

▪ At the Configure Ubuntu archive mirror step of the installation wizard, leave the default mirror address.

▪ At the Storage configuration step of the installation wizard, follow recommendations from CIS
Benchmarks for Ubuntu Linux 20.04 LTS STIG for partitioning.

For the operating system, use the ext4 file system. Example:

753 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For the backup data, use the XFS file system. Example:

NOTE

To be compliant with DISA STIG UBTU-20-010414, you do not need to enable disk encryption for the
operating system. To protect data in backups, use Veeam Backup & Replication built-in encryption
instead. For more information, see Storage Settings.

After you add partitions for all disks, click Continue in the Confirm destructive action window to apply
changes. Note that all data on the disks will be deleted.

10. At the P rofile setup step of the installation wizard, specify a hostname and a user account that you will
use to connect to the Linux server. Consider that by default it will have sudo permissions. After you add
a hardened repository to the backup infrastructure, you must remove this user account from the sudo
group. For more information, see Post-Installation.

11. At the SSH Setup step of the installation wizard, select the Install OpenSSH server check box. The
OpenSSH server is required to be compliant with DISA STIG UBTU-20-010042 and for deployment and
upgrade of Veeam Data Mover.

12. At the Fea tured Server Snaps step of the installation wizard, do not install any additional packages.
Click Done to start the installation process.

After the installation finishes, remove the installation media and reboot the system.

Post-Installation
For post-installation, consider the following Veeam recommendations:

• To be compliant with DISA STIG UBTU-20-010009, set a password for GRUB. To configure the setting
manually, do the following:

• Create a password using the grub-mkpasswd-pbkdf2 command:

grub-mkpasswd-pbkdf2
Enter password:
Reenter password:
PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.C0F70D240A8BC5
C1BC4E1303EC4F040957C1AF1BB8E99EED573133D3A017BE9B2BB48E52577A141B3A695
2527A9D1BEF13E2BB29978DA71F2D867EBB03545021.C4E81CAE7B464E78B15DF0A578B
63BAB3A0CB180C311AFA5A85F6245800D11D40B37B817C3F30348EE603AF725B7E09B98
A291114B0206D[…]

• Add a user name and a password hash at the end of the /etc/grub.d/40_custom file:

754 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
set superusers="root"
password_pbkdf2 root grub.pbkdf2.sha512.10000.C0F70D240A8BC5F[…]

c. To disable asking for credentials after rebooting the system and require them only when editing
boot menu entries, open the /etc/grub.d/10_linux file and add the --unrestricted
parameter to the CLASS variable:

CLASS="--class gnu-linux --class gnu --class os --unrestricted"

d. Update the GRUB configuration:

sudo update-grub

• To be compliant with DISA STIG UBTU-20-010455, disable all wireless network adapters, as described
in this DISA STIG article.

• If you do not use the proxy server and the Linux server has outgoing HTTP internet access allowed, limit
outgoing HTTP traffic to the Ubuntu servers only or use an internal Ubuntu mirror. To receive Linux
security updates, there must be the access to the Linux distribution security update servers.

• For the separate directory that you created for the backup data, allow access only for the user account
you created during the installation. Use the following commands:

o To assign the directory's owner:

chown -R owner:group <dir_path>

Both owner and group must be the user account you created during the installation.

o To allow access to the directory only for its owner and the root account:

chmod 700 <dir_path>

• To be compliant with DISA STIG UBTU-20-010012, you must have only two users:

o The root account. Note that by default the root account has a blank password and cannot be
used for connection.

o The user account you created during the installation. This account will be used to connect to the
Linux server and deploy required Veeam Backup & Replication components including persistent
Veeam Data Mover, or transport service. For more information about Veeam Data Movers, see
this section.

By default, the user account you created during the installation is the member of the sudo group and
has enough privileges to deploy and install required Veeam Backup & Replication components. In
that case, when you add a Linux server as a hardened repository to the backup infrastructure and
specify single-use credentials, you do not need to enter the password for the root account. After the
repository is added, you must remove the user account from the sudo group to make it a non-root
account. To do this, perform the following steps:

o Allow the user account to reboot and shutdown the operating system:

755 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
sudo bash -c "echo 'user1 ALL = (root) NOEXEC: /usr/sbin/reboot' >> /et
c/sudoers"
sudo bash -c "echo 'user1 ALL = (root) NOEXEC: /usr/sbin/shutdown' >> /
etc/sudoers"

o Remove the user account from the sudo group:

sudo deluser user1 sudo

Note that the next time you log in with this user account, it will lose sudo permissions. if you
need to execute commands as a privileged user, you must boot the operating system into the
single user mode.

Configuring DISA STIG Compliance for Ubuntu Linux Server


The Linux server based on Ubuntu 20.04 LTS can be configured according to the following DISA STIGs . Settings
can be applied manually or using the automatic configuration script provided by Veeam. For more information
about the script, see this Veeam page.

DISA STIG ID Description How to apply

UBTU-20-010000 The Ubuntu operating system Not applicable. A hardened


must provision temporary user repository does not use temporary
accounts with an expiration time user accounts.
of 72 hours or less.

UBTU-20-010002 The Ubuntu operating system Not applicable. The operating


must enable the graphical user system is installed without GUI.
logon banner to display the
Standard Mandatory DoD Notice
and Consent Banner before
granting local access to the
system via a graphical user logon.

UBTU-20-010003 The Ubuntu operating system Not applicable.The operating


must display the Standard system is installed without GUI.
Mandatory DoD Notice and
Consent Banner before granting
local access to the system via a
graphical user logon.

UBTU-20-010004 The Ubuntu operating system Not applicable.The operating


must retain a user's session lock system is installed without GUI.
until that user reestablishes
access using established
identification and authentication
procedures.

756 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010005 The Ubuntu operating system To configure the setting manually,


must allow users to directly see this DISA STIG article.
initiate a session lock for all
connection types. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010006 The Ubuntu operating system Not applicable. A hardened


must map the authenticated repository uses only a root
identity to the user or group account and a non-root account
account for PKI-based with reduced permissions.
authentication.

UBTU-20-010007 The Ubuntu operating system To configure the setting manually,


must enforce 24 hours/1 day as see this DISA STIG article.
the minimum password lifetime.
Passwords for new users must This setting is also included to the
have a 24 hours/1 day minimum automatic configuration script
password lifetime restriction. provided by Veeam.

UBTU-20-010008 The Ubuntu operating system To configure the setting manually,


must enforce a 60-day maximum see this DISA STIG article.
password lifetime restriction.
Passwords for new users must This setting is also included to the
have a 60-day maximum automatic configuration script
password lifetime restriction. provided by Veeam.

UBTU-20-010010 The Ubuntu operating system Not applicable. A hardened


must uniquely identify interactive repository uses only a root
users. account and a non-root account
with reduced permissions.

UBTU-20-010013 The Ubuntu operating system To configure the setting manually,


must automatically terminate a see this DISA STIG article.
user session after inactivity
timeouts have expired. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010014 The Ubuntu operating system To configure the setting manually,


must require users to see this DISA STIG article.
reauthenticate for privilege
escalation or when changing roles. This setting is also included to the
automatic configuration script
provided by Veeam.

757 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010016 The Ubuntu operating system To configure the setting manually,


default filesystem permissions see this DISA STIG article.
must be defined in such a way that
all authenticated users can read This setting is also included to the
and modify only their own files. automatic configuration script
provided by Veeam.

UBTU-20-010033 The Ubuntu operating system Not applicable. A hardened


must implement smart card logins repository uses only a root
for multifactor authentication for account and a non-root account
local and network access to with reduced permissions.
privileged and non-privileged
accounts.

UBTU-20-010035 The Ubuntu operating system To configure the setting manually,


must use strong authenticators in see this DISA STIG article.
establishing nonlocal maintenance
and diagnostic sessions. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010036 The Ubuntu operating system To configure the setting manually,


must immediately terminate all see this DISA STIG article.
network connections associated
with SSH traffic after a period of This setting is also included to the
inactivity. automatic configuration script
provided by Veeam.

UBTU-20-010037 The Ubuntu operating system To configure the setting manually,


must immediately terminate all see this DISA STIG article.
network connections associated
with SSH traffic at the end of the This setting is also included to the
session or after 10 minutes of automatic configuration script
inactivity. provided by Veeam.

UBTU-20-010038 The Ubuntu operating system To configure the setting manually,


must display the Standard see this DISA STIG article.
Mandatory DoD Notice and
Consent Banner before granting This setting is also included to the
any local or remote connection to automatic configuration script
the system. provided by Veeam. A consent
banner includes the following
text: "WARNING: Unauthorized
access to this system is forbidden
and will be prosecuted by law. By
accessing this system, you agree
that your actions may be
monitored if unauthorized usage is
suspected".

758 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010043 The Ubuntu operating system To configure the setting manually,


must configure the SSH daemon see this DISA STIG article.
to use Message Authentication
Codes (MACs) employing FIPS This setting is also included to the
140-2 approved cryptographic automatic configuration script
hashes to prevent the provided by Veeam.
unauthorized disclosure of
information and/or detect changes
to information during
transmission.

UBTU-20-010044 The Ubuntu operating system Not applicable. SSH connection is


must configure the SSH daemon necessary only for the deployment
to use FIPS 140-2 approved and upgrade of Veeam Data Mover
ciphers to prevent the and can be disabled after you add
unauthorized disclosure of the hardened repository to the
information and/or detect changes backup infrastructure.
to information during
transmission.

UBTU-20-010047 The Ubuntu operating system To configure the setting manually,


must not allow unattended or see this DISA STIG article.
automatic login via SSH.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010048 The Ubuntu operating system To configure the setting manually,


must be configured so that see this DISA STIG article.
remote X connections are
disabled, unless to fulfill This setting is also included to the
documented and validated mission automatic configuration script
requirements. provided by Veeam.

UBTU-20-010049 The Ubuntu operating system SSH To configure the setting manually,
daemon must prevent remote see this DISA STIG article.
hosts from connecting to the
proxy display. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010050 The Ubuntu operating system To configure the setting manually,


must enforce password see this DISA STIG article.
complexity by requiring that at
least one upper-case character be This setting is also included to the
used. automatic configuration script
provided by Veeam.

759 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010051 The Ubuntu operating system To configure the setting manually,


must enforce password see this DISA STIG article.
complexity by requiring that at
least one lower-case character be This setting is also included to the
used. automatic configuration script
provided by Veeam.

UBTU-20-010052 The Ubuntu operating system To configure the setting manually,


must enforce password see this DISA STIG article.
complexity by requiring that at
least one numeric character be This setting is also included to the
used. automatic configuration script
provided by Veeam.

UBTU-20-010053 The Ubuntu operating system To configure the setting manually,


must require the change of at see this DISA STIG article.
least 8 characters when
passwords are changed. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010054 The Ubuntu operating system To configure the setting manually,


must enforce a minimum 15- see this DISA STIG article.
character password length.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010055 The Ubuntu operating system To configure the setting manually,


must enforce password see this DISA STIG article.
complexity by requiring that at
least one special character be This setting is also included to the
used. automatic configuration script
provided by Veeam.

UBTU-20-010056 The Ubuntu operating system To configure the setting manually,


must prevent the use of dictionary see this DISA STIG article.
words for passwords.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010057 The Ubuntu operating system To configure the setting manually,


must be configured so that when see this DISA STIG article.
passwords are changed or new
passwords are established, This setting is also included to the
pwquality must be used. automatic configuration script
provided by Veeam.

760 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010060 The Ubuntu operating system, for Not applicable. A hardened


PKI-based authentication, must repository does not use PKI-based
validate certificates by authentication.
constructing a certification path
(which includes status
information) to an accepted trust
anchor.

UBTU-20-010063 The Ubuntu operating system Not applicable. A hardened


must implement multifactor repository does not use remote
authentication for remote access access to privileged accounts.
to privileged accounts in such a
way that one of the factors is
provided by a device separate
from the system gaining access.

UBTU-20-010064 The Ubuntu operating system Not applicable. A hardened


must accept Personal Identity repository does not use interactive
Verification (PIV) credentials. users and smart cards.

UBTU-20-010065 The Ubuntu operating system Not applicable. A hardened


must electronically verify Personal repository does not use interactive
Identity Verification (PIV) users and smart cards.
credentials.

UBTU-20-010066 The Ubuntu operating system for Not applicable. A hardened


PKI-based authentication, must repository does not use interactive
implement a local cache of users and smart cards.
revocation data in case of the
inability to access revocation
information via the network.

UBTU-20-010070 The Ubuntu operating system To configure the setting manually,


must prohibit password reuse for a see this DISA STIG article.
minimum of five generations.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010072 The Ubuntu operating system To configure the setting manually,


must automatically lock an see this DISA STIG article.
account until the locked account is
released by an administrator when This setting is also included to the
three unsuccessful logon attempts automatic configuration script
have been made. provided by Veeam.

761 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010074 The Ubuntu operating system To configure the setting manually,


must be configured so that the see this DISA STIG article.
script which runs each 30 days or
less to check file integrity is the This setting is also included to the
default one. automatic configuration script
provided by Veeam.

UBTU-20-010075 The Ubuntu operating system To configure the setting manually,


must enforce a delay of at least 4 see this DISA STIG article.
seconds between logon prompts
following a failed logon attempt. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010100 The Ubuntu operating system To configure the setting manually,


must generate audit records for all see this DISA STIG article.
account creations, modifications,
disabling, and termination events This setting is also included to the
that affect /etc/passwd. automatic configuration script
provided by Veeam.

UBTU-20-010101 The Ubuntu operating system To configure the setting manually,


must generate audit records for all see this DISA STIG article.
account creations, modifications,
disabling, and termination events This setting is also included to the
that affect /etc/group. automatic configuration script
provided by Veeam.

UBTU-20-010102 The Ubuntu operating system To configure the setting manually,


must generate audit records for all see this DISA STIG article.
account creations, modifications,
disabling, and termination events This setting is also included to the
that affect /etc/shadow. automatic configuration script
provided by Veeam.

UBTU-20-010103 The Ubuntu operating system To configure the setting manually,


must generate audit records for all see this DISA STIG article.
account creations, modifications,
disabling, and termination events This setting is also included to the
that affect /etc/gshadow. automatic configuration script
provided by Veeam.

UBTU-20-010104 The Ubuntu operating system To configure the setting manually,


must generate audit records for all see this DISA STIG article.
account creations, modifications,
disabling, and termination events This setting is also included to the
that affect /etc/opasswd. automatic configuration script
provided by Veeam.

762 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010117 The Ubuntu operating system To configure the setting manually,


must alert the ISSO and SA (at a see this DISA STIG article.
minimum) in the event of an audit
processing failure.

UBTU-20-010118 The Ubuntu operating system To configure the setting manually,


must shut down by default upon see this DISA STIG article.
audit failure (unless availability is
an overriding concern). This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010122 The Ubuntu operating system To configure the setting manually,


must be configured so that audit see this DISA STIG article.
log files are not read or write-
accessible by unauthorized users. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010123 The Ubuntu operating system To configure the setting manually,


must be configured to permit only see this DISA STIG article.
authorized users ownership of the
audit log files. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010124 The Ubuntu operating system To configure the setting manually,


must permit only authorized see this DISA STIG article.
groups ownership of the audit log
files. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010128 The Ubuntu operating system To configure the setting manually,


must be configured so that the see this DISA STIG article.
audit log directory is not write-
accessible by unauthorized users. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010133 The Ubuntu operating system To configure the setting manually,


must be configured so that audit see this DISA STIG article.
configuration files are not write-
accessible by unauthorized users. This setting is also included to the
automatic configuration script
provided by Veeam.

763 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010134 The Ubuntu operating system To configure the setting manually,


must permit only authorized see this DISA STIG article.
accounts to own the audit
configuration files. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010135 The Ubuntu operating system To configure the setting manually,


must permit only authorized see this DISA STIG article.
groups to own the audit
configuration files. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010136 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the su command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010137 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chfn command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010138 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the mount command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010139 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the umount command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010140 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the ssh-agent command. This setting is also included to the
automatic configuration script
provided by Veeam.

764 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010141 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the ssh-keysign command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010142 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
any use of the setxattr, fsetxattr,
lsetxattr, removexattr, This setting is also included to the
fremovexattr, and lremovexattr automatic configuration script
system calls. provided by Veeam.

UBTU-20-010148 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chown, fchown, fchownat, and This setting is also included to the
lchown system calls. automatic configuration script
provided by Veeam.

UBTU-20-010152 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chmod, fchmod, and fchmodat This setting is also included to the
system calls. automatic configuration script
provided by Veeam.

UBTU-20-010155 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the creat, open, openat, This setting is also included to the
open_by_handle_at, truncate, and automatic configuration script
ftruncate system calls. provided by Veeam.

UBTU-20-010161 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the sudo command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010162 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the sudoedit command. This setting is also included to the
automatic configuration script
provided by Veeam.

765 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010163 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chsh command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010164 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the newgrp command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010165 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chcon command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010166 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the apparmor_parser command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010167 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the setfacl command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010168 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chacl command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010169 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the use and modification of the
tallylog file. This setting is also included to the
automatic configuration script
provided by Veeam.

766 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010170 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the use and modification of faillog
file. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010171 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the use and modification of the
lastlog file. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010172 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the passwd command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010173 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the unix_update command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010174 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the gpasswd command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010175 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the chage command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010176 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the usermod command. This setting is also included to the
automatic configuration script
provided by Veeam.

767 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010177 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the crontab command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010178 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the pam_timestamp_check This setting is also included to the
command. automatic configuration script
provided by Veeam.

UBTU-20-010179 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the init_module and finit_module This setting is also included to the
syscalls. automatic configuration script
provided by Veeam.

UBTU-20-010181 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
successful/unsuccessful uses of
the delete_module syscall. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010182 The Ubuntu operating system To configure the setting manually,


must produce audit records and see this DISA STIG article.
reports containing information to
establish when, where, what type, This setting is also included to the
the source, and the outcome for automatic configuration script
all DoD-defined auditable events provided by Veeam.
and actions in near real time.

UBTU-20-010198 The Ubuntu operating system To configure the setting manually,


must initiate session audits at see this DISA STIG article.
system start-up.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010199 The Ubuntu operating system To configure the setting manually,


must configure audit tools with a see this DISA STIG article.
mode of 0755 or less permissive.
This setting is also included to the
automatic configuration script
provided by Veeam.

768 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010200 The Ubuntu operating system To configure the setting manually,


must configure audit tools to be see this DISA STIG article.
owned by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010201 The Ubuntu operating system To configure the setting manually,


must configure the audit tools to see this DISA STIG article.
be group-owned by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010205 The Ubuntu operating system To configure the setting manually,


must use cryptographic see this DISA STIG article.
mechanisms to protect the
integrity of audit tools. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010211 The Ubuntu operating system To configure the setting manually,


must prevent all software from see this DISA STIG article.
executing at higher privilege
levels than users executing the This setting is also included to the
software and the audit system automatic configuration script
must be configured to audit the provided by Veeam.
execution of privileged functions.

UBTU-20-010215 The Ubuntu operating system To configure the setting manually,


must allocate audit record storage see this DISA STIG article.
capacity to store at least one
weeks' worth of audit records,
when audit records are not
immediately sent to a central
audit record storage facility.

UBTU-20-010216 The Ubuntu operating system Applicable if the infrastructure


audit event multiplexor must be have such components. To
configured to off-load audit logs configure the setting manually,
onto a different system or storage see this DISA STIG article.
media from the system being
audited.

769 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010217 The Ubuntu operating system To configure the setting manually,


must immediately notify the SA see this DISA STIG article.
and ISSO (at a minimum) when
allocated audit record storage
volume reaches 75% of the
repository maximum audit record
storage capacity.

UBTU-20-010230 The Ubuntu operating system To configure the setting manually,


must record time stamps for audit see this DISA STIG article.
records that can be mapped to
Coordinated Universal Time (UTC) This setting is also included to the
or Greenwich Mean Time (GMT). automatic configuration script
provided by Veeam.

UBTU-20-010244 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
privileged activities, nonlocal
maintenance, diagnostic sessions This setting is also included to the
and other system-level access. automatic configuration script
provided by Veeam.

UBTU-20-010267 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
any successful/unsuccessful use of
unlink, unlinkat, rename, This setting is also included to the
renameat, and rmdir system calls. automatic configuration script
provided by Veeam.

UBTU-20-010277 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the /var/log/wtmp file.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010278 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the /var/run/utmp file.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010279 The Ubuntu operating system To configure the setting manually,


must generate audit records for see this DISA STIG article.
the /var/log/btmp file.
This setting is also included to the
automatic configuration script
provided by Veeam.

770 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010296 The Ubuntu operating system To configure the setting manually,


must generate audit records when see this DISA STIG article.
successful/unsuccessful attempts
to use modprobe command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010297 The Ubuntu operating system To configure the setting manually,


must generate audit records when see this DISA STIG article.
successful/unsuccessful attempts
to use the kmod command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010298 The Ubuntu operating system To configure the setting manually,


must generate audit records when see this DISA STIG article.
successful/unsuccessful attempts
to use the fdisk command. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010300 The Ubuntu operating system To configure the setting manually,


must have a crontab script running see this DISA STIG article.
weekly to offload audit events of
standalone systems.

UBTU-20-010400 The Ubuntu operating system To configure the setting manually,


must limit the number of see this DISA STIG article.
concurrent sessions to ten for all
accounts and/or account types. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010403 The Ubuntu operating system To configure the setting manually,


must monitor remote access see this DISA STIG article.
methods.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010404 The Ubuntu operating system To configure the setting manually,


must encrypt all stored passwords see this DISA STIG article.
with a FIPS 140-2 approved
cryptographic hashing algorithm. This setting is also included to the
automatic configuration script
provided by Veeam.

771 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010405 The Ubuntu operating system To configure the setting manually,


must not have the telnet package see this DISA STIG article.
installed.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010406 The Ubuntu operating system To configure the setting manually,


must not have the rsh-server see this DISA STIG article
package installed.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010407 The Ubuntu operating system To configure the setting manually,


must be configured to prohibit or see this DISA STIG article.
restrict the use of functions,
ports, protocols, and/or services, This setting is also included to the
as defined in the PPSM CAL and automatic configuration script
vulnerability assessments. provided by Veeam.

UBTU-20-010408 The Ubuntu operating system To configure the setting manually,


must prevent direct login into the see this DISA STIG article.
root account.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010409 The Ubuntu operating system Not applicable. A hardened


must disable account identifiers repository uses only a root
(individuals, groups, roles, and account and a non-root account
devices) after 35 days of with reduced permissions.
inactivity.

UBTU-20-010410 The Ubuntu operating system Not applicable. A hardened


must automatically remove or repository uses only a root
disable emergency accounts after account and a non-root account
72 hours. with reduced permissions.

UBTU-20-010411 The Ubuntu operating system To configure the setting manually,


must set a sticky bit on all public see this DISA STIG article.
directories to prevent
unauthorized and unintended This setting is also included to the
information transferred via shared automatic configuration script
system resources. provided by Veeam.

772 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010412 The Ubuntu operating system To configure the setting manually,


must be configured to use TCP see this DISA STIG article.
syncookies.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010413 The Ubuntu operating system To configure the setting manually,


must disable kernel core dumps so see this DISA STIG article.
that it can fail to a secure state if
system initialization fails, This setting is also included to the
shutdown fails or aborts fail. automatic configuration script
provided by Veeam.

UBTU-20-010415 The Ubuntu operating system Not applicable. A hardened


must deploy Endpoint Security for repository must not have any third
Linux Threat Prevention (ENSLTP). party software installed.

UBTU-20-010416 The Ubuntu operating system To configure the setting manually,


must generate error messages see this DISA STIG article.
that provide information
necessary for corrective actions This setting is also included to the
without revealing information that automatic configuration script
could be exploited by adversaries. provided by Veeam.

UBTU-20-010417 The Ubuntu operating system To configure the setting manually,


must configure the /var/log see this DISA STIG article.
directory to be group-owned by
syslog. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010418 The Ubuntu operating system To configure the setting manually,


must configure the /var/log see this DISA STIG article.
directory to be owned by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010419 The Ubuntu operating system To configure the setting manually,


must configure the /var/log see this DISA STIG article.
directory to have mode "0755" or
less permissive. This setting is also included to the
automatic configuration script
provided by Veeam.

773 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010420 The Ubuntu operating system To configure the setting manually,


must configure the see this DISA STIG article.
/var/log/syslog file to be group-
owned by adm. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010421 The Ubuntu operating system To configure the setting manually,


must configure /var/log/syslog see this DISA STIG article.
file to be owned by syslog.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010422 The Ubuntu operating system To configure the setting manually,


must configure /var/log/syslog see this DISA STIG article.
file with mode 0640 or less
permissive. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010423 The Ubuntu operating system To configure the setting manually,


must have directories that contain see this DISA STIG article.
system commands set to a mode
of 0755 or less permissive. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010424 The Ubuntu operating system To configure the setting manually,


must have directories that contain see this DISA STIG article.
system commands owned by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010425 The Ubuntu operating system To configure the setting manually,


must have directories that contain see this DISA STIG article.
system commands group-owned
by root. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010426 The Ubuntu operating system To configure the setting manually,


library files must have mode 0755 see this DISA STIG article.
or less permissive.
This setting is also included to the
automatic configuration script
provided by Veeam.

774 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010427 The Ubuntu operating system To configure the setting manually,


library directories must have mode see this DISA STIG article.
0755 or less permissive.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010428 The Ubuntu operating system To configure the setting manually,


library files must be owned by see this DISA STIG article.
root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010429 The Ubuntu operating system To configure the setting manually,


library directories must be owned see this DISA STIG article.
by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010430 The Ubuntu operating system To configure the setting manually,


library files must be group-owned see this DISA STIG article.
by root or a system account.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010431 The Ubuntu operating system To configure the setting manually,


library directories must be group- see this DISA STIG article.
owned by root.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010432 The Ubuntu operating system To configure the setting manually,


must be configured to preserve see this DISA STIG article.
log records from failure events.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010433 The Ubuntu operating system To configure the setting manually,


must have an application firewall see this DISA STIG article.
installed in order to control
remote access methods. This setting is also included to the
automatic configuration script
provided by Veeam.

775 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010434 The Ubuntu operating system To configure the setting manually,


must enable and run the see this DISA STIG article.
uncomplicated firewall (ufw).
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010435 The Ubuntu operating system To configure the setting manually,


must, for networked systems, see this DISA STIG article. Note
compare internal information that you must set the "-R" flag in
system clocks at least every 24 the /etc/defaults/chrony
hours with a server which is file.
synchronized to one of the
redundant United States Naval This setting is also included to the
Observatory (USNO) time servers, automatic configuration script
or a time server designated for the provided by Veeam.
appropriate DoD network
(NIPRNet/SIPRNet), and/or the
Global Positioning System (GPS).

UBTU-20-010436 The Ubuntu operating system Not applicable. A hardened


must synchronize internal repository uses additional
information system clocks to the parameter to be compliant with
authoritative time source when STIG UBTU-20-010435.
the time difference is greater than
one second.

UBTU-20-010437 The Ubuntu operating system To configure the setting manually,


must notify designated personnel see this DISA STIG article.
if baseline configurations are
changed in an unauthorized
manner. The file integrity tool
must notify the System
Administrator when changes to
the baseline configuration or
anomalies in the operating system
are detected.

UBTU-20-010438 The Ubuntu operating system's To configure the setting manually,


Advance Package Tool (APT) must see this DISA STIG article.
be configured to prevent the
installation of patches, service This setting is also included to the
packs, device drivers, or Ubuntu automatic configuration script
operating system components provided by Veeam.
without verification they have
been digitally signed using a
certificate that is recognized and
approved by the organization.

776 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010439 The Ubuntu operating system To configure the setting manually,


must be configured to use see this DISA STIG article.
AppArmor.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010440 The Ubuntu operating system Not applicable. A hardened


must allow the use of a temporary repository uses only a root
password for system logons with account and a non-root account
an immediate change to a with reduced permissions.
permanent password.

UBTU-20-010441 The Ubuntu operating system Not applicable.


must be configured such that
Pluggable Authentication Module
(PAM) prohibits the use of cached
authentications after one day.

UBTU-20-010442 The Ubuntu operating system Not applicable.


must implement NIST FIPS-
validated cryptography to protect
classified information and for the
following: to provision digital
signatures, to generate
cryptographic hashes, and to
protect unclassified information
requiring confidentiality and
cryptographic protection in
accordance with applicable federal
laws, Executive Orders, directives,
policies, regulations, and
standards.

UBTU-20-010443 The Ubuntu operating system Not applicable. A hardened


must only allow the use of DoD repository does not use smart card
PKI-established certificate authentication.
authorities for verification of the
establishment of protected
sessions.

UBTU-20-010444 Ubuntu operating system must To protect data in backups, use


implement cryptographic Veeam Backup & Replication built-
mechanisms to prevent in encryption. For more
unauthorized modification of all information, see Storage Settings.
information at rest.

777 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010445 Ubuntu operating system must To protect data in backups, use


implement cryptographic Veeam Backup & Replication built-
mechanisms to prevent in encryption. For more
unauthorized disclosure of all information, see Storage Settings.
information at rest.

UBTU-20-010446 The Ubuntu operating system Not applicable.


must configure the uncomplicated
firewall to rate-limit impacted
network interfaces.

UBTU-20-010447 The Ubuntu operating system To configure the setting manually,


must implement non-executable see this DISA STIG article.
data to protect its memory from
unauthorized code execution.

UBTU-20-010448 The Ubuntu operating system To configure the setting manually,


must implement address space see this DISA STIG article.
layout randomization to protect
its memory from unauthorized This setting is also included to the
code execution. automatic configuration script
provided by Veeam.

UBTU-20-010449 The Ubuntu operating system To configure the setting manually,


must be configured so that see this DISA STIG article.
Advance Package Tool (APT)
removes all software components This setting is also included to the
after updated versions have been automatic configuration script
installed. provided by Veeam.

UBTU-20-010450 The Ubuntu operating system To configure the setting manually,


must use a file integrity tool to see this DISA STIG article.
verify correct operation of all
security functions. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010451 The Ubuntu operating system To configure the setting manually,


must notify designated personnel see this DISA STIG article.
if baseline configurations are
changed in an unauthorized This setting is also included to the
manner. The file integrity tool automatic configuration script
must notify the System provided by Veeam.
Administrator when changes to
the baseline configuration or
anomalies in the operation of any
security functions are discovered.

778 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010453 The Ubuntu operating system To configure the setting manually,


must display the date and time of see this DISA STIG article.
the last successful account logon
upon logon. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010454 The Ubuntu operating system To configure the setting manually,


must have an application firewall see this DISA STIG article.
enabled.
This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010456 The Ubuntu operating system To configure the setting manually,


must have system commands set see this DISA STIG article.
to a mode of 0755 or less
permissive. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010457 The Ubuntu operating system To configure the setting manually,


must have system commands see this DISA STIG article.
owned by root or a system
account. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010458 The Ubuntu operating system To configure the setting manually,


must have system commands see this DISA STIG article.
group-owned by root or a system
account. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010459 The Ubuntu operating system Not applicable. The operating


must disable the x86 system is installed without GUI.
[Ctrl+Alt+Delete] key combination
if a graphical user interface is
installed.

UBTU-20-010460 The Ubuntu operating system To configure the setting manually,


must disable the x86 see this DISA STIG article.
[Ctrl+Alt+Delete] key
combination. This setting is also included to the
automatic configuration script
provided by Veeam.

779 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
DISA STIG ID Description How to apply

UBTU-20-010462 The Ubuntu operating system To configure the setting manually,


must not have accounts see this DISA STIG article.
configured with blank or null
passwords. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010463 The Ubuntu operating system To configure the setting manually,


must not allow accounts see this DISA STIG article.
configured with blank or null
passwords. This setting is also included to the
automatic configuration script
provided by Veeam.

UBTU-20-010461 The Ubuntu operating system To configure the setting manually,


must disable automatic mounting see this DISA STIG article.
of Universal Serial Bus (USB) mass
storage driver. This setting is also included to the
automatic configuration script
provided by Veeam.

Adding Hardened Repositories


This section describes how to add a hardened repository as a backup repository.

Before you begin, check requirements and limitations and prepare a Linux server. Then use the New Ba ckup
Rep ository wizard to add the hardened repository:

1. Launch the New Backup Repository wizard.

2. Specify the hardened repository name and description.

3. Specify a Linux server.

4. Configure hardened repository settings.

5. Specify mount server settings.

6. Review and apply settings.

If you upgrade to Veeam Backup & Replication 12 and have Linux backup repositories with enabled Ma k e recent
b a ckups immutable for check box, see Upgrading Linux Repository to Hardened Repository.

780 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, perform the following steps:

1. Open the Ba ckup Infrastructure view. In the inventory pane, right-click the Ba ckup Repositories node and
select Ad d Backup Repository. Alternatively, you can click Ad d Repository on the ribbon.

2. In the Ad d Backup Repository window, select Direct attached storage > Linux ( Hardened Repository).

781 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Hardened Repository Name and Description
At the Na me step of the wizard, specify a name and description for the repository. The default description
contains information about the user who added the repository, date and time when the repository was added.

782 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Linux Server
From the Rep ository server list, select a Linux server that you want to use as a hardened repository. Click
P op ulate to see a list of disks connected to the server, their capacity and free space.

The Rep ository server list contains only those servers that are added to the backup infrastructure. If the server is
not added to the backup infrastructure yet, click Ad d New on the right and follow the wizard:

1. At the Na me step of the wizard, specify a full DNS name or IP address and description of the Linux server.
The default description contains information about the user who added the server, date and time when
the server was added.

2. At the SSH Connection step of the wizard, specify single-use credentials to connect to the Linux server
and deploy Veeam Data Mover. Note that Veeam Backup & Replication does not store these credentials in
the configuration database.

NOTE

The user account you specified must be a non-root account. Also, it must have the home directory
created on the Linux server.

783 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The E levate a ccount privileges automatically check box is used by default. If you did not add the user
account to the sudoers file, select the Use "su" if "sudo" fails check box and enter the password for the
root account. For more information on these check boxes, see Linux Accounts (User Name and Password).

IMP ORTANT

If you added the user account to the sudoers file, you do not need to select the Use " su" if "sudo"
fa ils check box and specify the root password. But after the server is added, you must remove the
user account from the file.

If you want to change default SSH settings, click Ad vanced. For more details, see Step 3. Specify
Credentials and SSH Settings in the New Linux Server wizard.

3. At the Review step of the wizard, review what Veeam Backup & Replication components are already
installed on the server and what components will be installed. Click Ap p ly to add the Linux server to the
backup infrastructure.

4. At the Summary step of the wizard, review details of the Linux server and click Finish to exit the wizard.

784 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Hardened Repository Settings
At the Rep ository step of the wizard, specify path and repository settings:

1. In the Loca tion section, specify a path to the directory that you created to store immutable backups when
preparing Linux server. Click P op ulate to check capacity and available free space in the selected location.

2. Select the Use fast cloning on XFS volumes check box to enable copy-on-write functionality. For more
information, see Fast Clone.

3. Specify the immutability period.

4. Specify load control settings to limit the number of concurrent tasks and prevent possible timeouts of
storage I/O operations. For more details, see Configure Backup Repository Settings.

5. If you want to configure additional settings for the repository, click Ad vanced. For more details, see
Configure Backup Repository Settings.

785 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore. For more details, see Specify Mount Server Settings.

786 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review and Apply Settings
At the Review step of the wizard, review the hardened repository settings and list of components that will be
installed.

If the backup repository contains backups that were previously created by Veeam Backup & Replication, select
the Sea rch the repository for existing backups and import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and display them in
the Veeam Backup & Replication console under the Imp orted > Ba ckups node.

If the backup repository contains guest file system index files that were previously created by
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be imported
with backup files, and you will be able to search for guest OS files inside imported backups.

Click Ap p ly and wait for Veeam Backup & Replication to install and configure all required components. At the
Summary step of the wizard, review details of the added hardened repository and click Finish to exit the wizard.

To maximize the repository security and protect your data from different attacks, after the deployment of
Veeam Data Mover, change file permissions for authentication certificates, so that only the user account you
specified to connect to the Linux server and the root account can read the certificate files. Use the following
commands:

chown owner:group /opt/veeam/transport/certs


chmod 700 /opt/veeam/transport/certs

Note that both owner and group must be the user account you specified to connect to the Linux server. You
can also use chmod 770 to add same permissions to the group.

787 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

SSH connection is necessary only for the deployment of Veeam Data Mover. For security purposes, after
you add the hardened repository, disable SSH connection for the user account you use to connect to the
Linux server. If you can work with the server from the console, disable SSH connection for the server itself.

Managing Hardened Repository

Updating Hardened Repository Components


If you use Veeam Backup & Replication 12 prior cumulative patch P20230718 and want to update hardened
repository components or remove a hardened repository from the backup infrastructure, make sure that the SSH
connection is enabled. Consider that you also need to specify single-use credentials you use to connect to the
Linux server and deploy Veeam Data Mover.

IMP ORTANT

The SSH connection is also required for updating hardened repository components in the following
situations:

• If you upgrade from Veeam Backup & Replication 11a or earlier versions to
Veeam Backup & Replication 12 including versions with installed cumulative patches.
• If you upgrade from any previous Veeam Backup & Replication version to
Veeam Backup & Replication 12.1 (build 12.1.0.2131).

If you need to specify single-use credentials for multiple hardened repositories, you can use the
Comp onents Update window or the Set-VBRLinux cmdlet.

If you update Veeam Backup & Replication 12 to any cumulative patch, the SSH connection is not required for
updating hardened repository components. For more information about cumulative patches, see this Veeam KB
article.

Upgrading Linux Repository to Hardened Repository


If you upgrade to Veeam Backup & Replication 12, all Linux backup repositories with enabled Ma k e recent
b a ckups immutable for check box will be automatically converted to hardened repositories. Note that if these
repositories were added with persistent credentials, they will be automatically converted to single -use
credentials.

NOTE

If a Linux backup repository with enabled Ma k e recent backups immutable for check box was added with
root credentials, the upgrade process will be interrupted. To continue it, you must specify a user account
with non-root permissions for this repository. For more information, see this Veeam KB article.

Migrating Linux Repository to Hardened Repository


If you have a Linux server added to the backup infrastructure as a backup repository and want to use it as a
hardened repository, perform the following steps:

1. On the Linux server, change permissions for the directory where backups are stored. Both owner and
group must be the account with non-root permissions you use to connect to the Linux server.

788 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
chown -R owner:group <dir_path>

2. Go to the Veeam Backup & Replication console and perform the following steps:

a. Open the Ba ckup Infrastructure view and select Ma naged Servers in the navigation pane. Right-click
the Linux server, select P roperties, go to the SSH Connection step of the wizard, and specify the
account with non-root permissions you use to connect to the Linux server. Note that these credentials
must be single-use.

b. Remove backup files stored on the Linux repository from the backup configuration. To do this, go to
the Ba ckups > Disk node and select the backup file. Hold [Ctrl] and right-click the file. Then click
Remove from configuration.

c. Add the same Linux server to the backup infrastructure as a hardened repository using the New
Ba ckup Repository wizard. At the Review step of the wizard, select the Sea rch the repository for
ex isting backups and import them automatically check box to detect existing backup files and display
them in the Veeam Backup & Replication console under the Imported > Backups node. For more
information, see Adding Hardened Repositories.

NOTE

If you work with encrypted backups, you need to decrypt them after importing. For more
information, see How Data Decryption Works.

789 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
d. Go to the Job s node and edit the job associated with the Linux repository. At the Storage step of the
wizard, select the hardened repository from the Ba ckup repository list.

Click Ma p backup and specify imported backups from the previous step.

Finish the wizard to apply changes.

790 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
e. Open the Ba ckup Infrastructure view and remove the Linux backup repository from the backup
infrastructure.

791 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
SMB (CIFS) Share
You can use SMB (CIFS) shares as backup repositories.

SMB Backup Repository Deployment


To communicate with an SMB backup repository, Veeam Backup & Replication uses two Veeam Data Movers that
are responsible for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the gateway server

An SMB share cannot host Veeam Data Movers. For this reason, to communicate with the SMB share, you need
to deploy a gateway server. Veeam Backup & Replication will automatically deploy a Veeam Data Mover on this
gateway server. For more information on gateway server requirements and limitations, see Gateway Server.

When any job addresses the SMB backup repository, Veeam Data Mover on the gateway server establishes a
connection with Veeam Data Mover on the off-host backup proxy, enabling efficient data transfer over LAN or
WAN.

If you plan to move VM data to an off-site SMB repository over a WAN link, it is recommended that you deploy
an additional gateway server in the remote site, closer to the SMB repository.

Requirements for SMB Backup Repositories


The role of an SMB repository can be assigned to a Microsoft Windows machine (physical or virtual). The
machine must meet the system requirements. For more information, see System Requirements.

Adding SMB (CIFS) Repositories


This section describes how to add an SMB (CIFS) share as a backup repository.

To add a backup repository, use the New Backup Repository wizard.

792 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Network Attached Storage > SMB Share.

793 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Backup Repository Name and Description
At the Na me step of the wizard, specify a name and description for the backup repository:

1. In the Na me field, specify a name for the backup repository.

2. In the Description field, provide a description for future reference.

794 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Shared Folder Settings
To configure settings for an SMB share:

1. In the Sha red folder field, specify a UNC path to the SMB shared folder that you want to use as a backup
repository. If you use the IPv6 address, specify the path in a literal format, for example, \\[1080--8-800-
200c-417a.ipv6-literal.net]\folder. For more information, see RFC 2732. Note that you can use IPv6
addresses only if IPv6 communication is enabled as described in section IPv6 Support.

2. If you must specify user credentials to access the shared folder, select the This share requires access
credentials check box. From the Credentials list, select a credentials record for a user account that has
read and write permissions on the shared folder. Note that the username must be in the down-level logon
name format. For example, DOMAIN\username or HOSTNAME\username.

If you have not set up credentials beforehand, click the Ma nage accounts link at the bottom of the list or
click Ad d on the right to add the credentials. For more information, see Managing Credentials.

3. In the Ga teway server field, specify settings for the gateway server:

o If you want Veeam Backup & Replication to select a gateway server automatically, leave Automatic
selection.

o If you want to select servers that can be used as gateway servers explicitly, click Choose next to the
Ga teway server field. In the Ga teway Server window, click Use the following gateway servers only and
select servers. The servers must have a direct access to the SMB share and must be located as close to
the SMB share as possible. Veeam Backup & Replication will choose the most suitable server.

For more information on the gateway servers, their requirements and limitations, and how they are
selected, see Gateway Server.

795 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Backup Repository Settings
At the Rep ository step of the wizard, configure general repository settings including path to the repository
folder and load control, and also advanced repository settings.

Configuring General Repository Settings


To configure general repository settings:

1. In the Loca tion section, specify a path to the folder where backup files must be stored. Click P op ulate to
check capacity and available free space in the selected location.

2. Use the Loa d control section to limit the number of concurrent tasks and data ingestion rate for the
backup repository. These settings will help you control the load on the backup repository and prevent possible
timeouts of storage I/O operations.

• Select the Limit maximum concurrent tasks check box and specify the maximum allowed number of
concurrent tasks for the backup repository. If this value is exceeded, Veeam Backup & Replication
will not start a new task until one of current tasks finishes. For more information, see Limiting the
Number of Concurrent Tasks.

NOTE

It is not recommended that you disable the Limit maximum concurrent tasks to N option for backup
repositories with per-machine backup chains. In case of per-machine backup chains, synthetic
operations (synthetic full backup, backup files merge and transformation) work in parallel for every
workload in the backup. The number of parallel operations is limited by the number of concurrent
tasks that can be performed on the backup repository. If you disable the Limit maximum concurrent
ta sks to N option (which results in using an unlimited number of slots), the load on the backup
repository may be high.

• Select the Limit read a nd write data rate to check box and specify the maximum rate to restrict the
total speed of reading and writing data to the backup repository disk. For more information, see
Limiting Combined Data Rate for Backup Repositories.

NOTE

The Limit read and write data rate to settings does not apply to health checks performed as part of
backup and backup copy jobs. Even if you limit read/write rate for a backup repository, the health
check will consume resources of the backup repository regardless of this setting. Consider this
limitation when configuring basic and health check schedules for backup and backup copy jobs.

796 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Advanced Repository Settings
To configure advanced repository settings:

1. Click Ad vanced.

2. For storage systems using a fixed block size, select the Align backup file data blocks check box.
Veeam Backup & Replication will align VM data saved to a backup file at a 4 KB block boundary.

3. When you enable compression for a backup job, Veeam Backup & Replication compresses VM data at the
source side and then transports it to the target side. Writing compressed data to a deduplicating storage
appliance results in poor deduplication ratios as the number of matching blocks decreases. To overcome
this situation, select the Decompress backup data blocks before storing check box. If data compression is
enabled for a job, Veeam Backup & Replication will compress VM data on the source side, transport it to
the target side, decompress VM data on the target side and write raw VM data to the storage device to
achieve a higher deduplication ratio.

NOTE

Veeam Backup & Replication does not compress VM data if encryption is enabled for a job and the
Decompress backup data blocks before storing check box is selected in the settings of the target
backup repository. Therefore, in the job statistics, you may observe a higher amount of transferred
data (the Tra nsferred counter) as compared to a job for which encryption is disabled. For more
information on job statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the
Ba ckup Size column) is larger than the original VM size (the Orig inal Size column). For more
information on backup properties, see Viewing Backup Properties.

797 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Select the This repository is backed by rotated drives check box if you plan to use a backup repository with
rotated drives. For more information on how to configure rotated drives, see Configuring Backup
Repositories with Rotated Drives.

5. To create a separate backup file for every machine in the job, make sure that the Use per-machine backup
files check box is selected. If you clear the check box, Veeam Backup & Replication will create single-file
backups. For more information on the backup chain formats and their limitations, see Backup Chain
Formats.

NOTE

Changing of the Use p er-machine backup files setting after the repository was already created does
not take any effect. To change backup chain format, follow the instructions provided in Upgrading
Backup Chain Formats.

798 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore.

1. From the Mount Server list, select a server that you want to use as a mount server. The mount server is
required for file-level and application items restore. During the restore process,
Veeam Backup & Replication will mount the VM disks from the backup file residing in the ba ckup
repository to the mount server. As a result, VM data will not have travel over the network, which will
reduce the load on the network and speed up the restore process. For more information, see Mount
Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder that will be used for writing cache during
mount operations.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

799 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Properties and Components
At the Review step of the wizard, review details of the backup repository and specify importing settings.

1. Review the backup repository settings and list of components that will be installed on the backup
repository server.

2. If the backup repository contains backups that were previously created by Veeam Backup & Replication,
select the Sea rch the repository for existing backups a nd import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and display
them in the Veeam Backup & Replication console under the Imported > Backups node.

3. If the backup repository contains guest file system index files that were previously created b y
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be
imported with backup files, and you will be able to search for guest OS files inside imported backups.

800 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Backup Repository Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the backup repository to the backup
infrastructure.

801 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup repository. Then click Finish to exit the
wizard.

802 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NFS Share
You can use NFS shares as backup repositories.

NFS Backup Repository Deployment


To communicate with an NFS backup repository, Veeam Backup & Replication uses two Veeam Data Movers that
are responsible for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the gateway server

NOTE

Windows-based gateway servers cannot be used for NFS shares with k rb5i and k rb5p support.

An NFS share cannot host Veeam Data Movers. For this reason, to communicate with the NFS share, you need to
deploy a gateway server. Veeam Backup & Replication will automatically deploy a Veeam Data Mover on this
gateway server. For more information, see Gateway Server.

When any job addresses the NFS backup repository, Veeam Data Mover on the gateway server establishes a
connection with Veeam Data Mover on the off-host backup proxy, enabling efficient data transfer over LAN or
WAN.

If you plan to move VM data to an off-site NFS repository over a WAN link, it is recommended that you deploy
an additional gateway server in the remote site, closer to the NFS repository.

Requirements and Limitations for NFS Backup Repositories


A machine performing the role of an NFS repository must meet the following requirements:

• The machine must meet the system requirements. For more information, see System Requirements.

• The role of the NFS repository can be assigned to a Microsoft Windows or Linux machine (physical or
virtual) or to NAS storage supporting NFS protocol.

• The NFS repository must present read and write access rights to the gateway.

Note that Veeam Backup & Replication does not support multipathing for NFS repository.

803 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Gateway Server
A machine performing the role of a gateway server for communication with the NFS backup repository must
meet the following requirements:

• The role of the gateway server can be assigned to a Microsoft Windows or Linux machine (physical or
virtual). The machine must meet the system requirements. For more information, see System
Requirements.

• You must add the machine to the Veeam Backup & Replication console as a managed server.

• [For automatic gateway selection] The backup server must have read and write access in the NFS
repository.

• [For automatic gateway selection] If you configure automatic gateway selection for NFS repository,
Veeam Backup & Replication may use the same machines as gateways for the repository and as proxies for
backup jobs. Make sure that the backup proxies meet the following requirements:

o If you explicitly choose backup proxies for backup jobs, provide read and write access rights to all
proxies chosen for backup jobs that are targeted to the NFS repository.

o If you configure automatic proxy selection for backup jobs, provide read and write acces s rights to all
proxies in the Veeam Backup & Replication infrastructure.

o If backup jobs that are targeted to the NFS repository use Linux proxies, check that the NFS client
package is installed on the Linux proxy server.

Requirements and Limitations for Linux Gateway Server


In addition to the general requirements, the Linux gateway server must meet the following requirements:

• The Linux gateway server must have NFS client package installed.

• The credentials to authenticate with the Linux gateway server must have root or elevated to root
permission.

• Veeam Backup & Replication uses the highest NFS protocol version supported by the gateway and the
repository.

Note that the suffix indicating the NFS version in the NFS share properties may not be displayed correctly,
this is a known issue.

TIP

If the NFS protocol version has changed (for example, if you updated the NFS share), click through the E dit
Ba ckup Repository wizard to update the information in Veeam Backup & Replication.

Adding NFS Repositories


This section describes how to add an NFS share as a backup repository.

To add a backup repository, use the New Backup Repository wizard.

804 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Network Attached Storage > NFS Share.

805 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Backup Repository Name and Description
At the Na me step of the wizard, specify a name and description for the backup repository:

1. In the Na me field, specify a name for the backup repository.

2. In the Description field, provide a description for future reference.

806 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Shared Folder Settings
To configure settings for an NFS share:

1. In the Sha red folder field, specify a path to the NFS shared folder that you want to use a s a backup
repository. You can specify the path using an IPv4 or IPv6 address. Note that you can use IPv6 addresses
only if IPv6 communication is enabled as described in section IPv6 Support.

2. In the Ga teway server field, specify which gateway server you want to use:

o If you want Veeam Backup & Replication to select a gateway server automatically, leave Automatic
selection.

o If you want to select servers that can be used as gateway servers explicitly, click Choose next to the
Ga teway server field. In the Ga teway Server window, click Use the following gateway servers only and
select servers. The servers must have a direct access to the NFS share and must be located as close to
the NFS share as possible. Veeam Backup & Replication will choose the most suitable server.

For more information on the gateway servers, their requirements and limitations, and how they are
selected, see Gateway Server.

807 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Backup Repository Settings
At the Rep ository step of the wizard, configure general repository settings including path to the repository
folder and load control, and also advanced repository settings.

Configuring General Repository Settings


To configure general repository settings:

1. In the Loca tion section, specify a path to the folder where backup files must be stored. Click P op ulate to
check capacity and available free space in the selected location.

2. Use the Loa d control section to limit the number of concurrent tasks and data ingestion rate for the
backup repository. These settings will help you control the load on the backup repository and prevent possible
timeouts of storage I/O operations.

• Select the Limit maximum concurrent tasks check box and specify the maximum allowed number of
concurrent tasks for the backup repository. If this value is exceeded, Veeam Backup & Replication
will not start a new task until one of current tasks finishes. For more information, see Limiting the
Number of Concurrent Tasks.

NOTE

It is not recommended that you disable the Limit maximum concurrent tasks to N option for backup
repositories with per-machine backup chains. In case of per-machine backup chains, synthetic
operations (synthetic full backup, backup files merge and transformation) work in parallel for every
workload in the backup. The number of parallel operations is limited by the number of concurrent
tasks that can be performed on the backup repository. If you disable the Limit maximum concurrent
ta sks to N option (which results in using an unlimited number of slots), the load on the backup
repository may be high.

• Select the Limit read a nd write data rate to check box and specify the maximum rate to restrict the
total speed of reading and writing data to the backup repository disk. For more information, see
Limiting Combined Data Rate for Backup Repositories.

NOTE

The Limit read and write data rate to settings does not apply to health checks performed as part of
backup and backup copy jobs. Even if you limit read/write rate for a backup repository, the health
check will consume resources of the backup repository regardless of this setting. Consider this
limitation when configuring basic and health check schedules for backup and backup copy jobs.

808 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Advanced Repository Settings
To configure advanced repository settings:

1. Click Ad vanced.

2. For storage systems using a fixed block size, select the Align backup file data blocks check box.
Veeam Backup & Replication will align VM data saved to a backup file at a 4 KB block boundary.

3. When you enable compression for a backup job, Veeam Backup & Replication compresses VM data at the
source side and then transports it to the target side. Writing compressed data to a deduplicating storage
appliance results in poor deduplication ratios as the number of matching blocks decreases. To overcome
this situation, select the Decompress backup data blocks before storing check box. If data compression is
enabled for a job, Veeam Backup & Replication will compress VM data on the source side, transport it to
the target side, decompress VM data on the target side and write raw VM data to the storage device to
achieve a higher deduplication ratio.

NOTE

Veeam Backup & Replication does not compress VM data if encryption is enabled for a job and the
Decompress backup data blocks before storing check box is selected in the settings of the target
backup repository. Therefore, in the job statistics, you may observe a higher amount of transferred
data (the Tra nsferred counter) as compared to a job for which encryption is disabled. For more
information on job statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the
Ba ckup Size column) is larger than the original VM size (the Orig inal Size column). For more
information on backup properties, see Viewing Backup Properties.

4. The This repository is backed by rotated hard drives option is disabled for NFS repositories. For more
information, see Configuring Backup Repositories with Rotated Drives.

809 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. To create a separate backup file for every machine in the job, make sure that the Use per-machine backup
files check box is selected. If you clear the check box, Veeam Backup & Replication will create single-file
backups. For more information on the backup chain formats and their limitations, see Backup Chain
Formats.

NOTE

Changing of the Use p er-machine backup files setting after the repository was already created does
not take any effect. To change backup chain format, follow the instructions provided in Upgrading
Backup Chain Formats.

810 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore.

1. From the Mount Server list, select a server that you want to use as a mount server. The mount server is
required for file-level and application items restore. During the restore process,
Veeam Backup & Replication will mount the VM disks from the backup file residing in the backup
repository to the mount server. As a result, VM data will not have travel over the network, which will
reduce the load on the network and speed up the restore process. For more information, see Mount
Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder that will be used for writing cache during
mount operations.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

811 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Properties and Components
At the Review step of the wizard, review details of the backup repository and specify importing settings.

1. Review the backup repository settings and list of components that will be installed on the backup
repository server.

2. If the backup repository contains backups that were previously created by Veeam Backup & Replication,
select the Sea rch the repository for existing backups a nd import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and disp lay
them in the Veeam Backup & Replication console under the Imported > Backups node.

3. If the backup repository contains guest file system index files that were previously created by
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be
imported with backup files, and you will be able to search for guest OS files inside imported backups.

812 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Backup Repository Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the backup repository to the backup
infrastructure.

813 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup repository. Then click Finish to exit the
wizard.

814 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deduplicating Storage Appliances
You can add deduplicating storage appliances as backup repositories.

In This Section
• Dell Data Domain

• ExaGrid

• HPE StoreOnce

• Quantum DXi

• Fujitsu ETERNUS CS800

• Infinidat InfiniGuard

Dell Data Domain


You can use Dell Data Domain storage systems with Data Domain Boost (DD Boost) as backup repositories.

To support the DD Boost technology, Veeam Backup & Replication leverages the following Dell Data Domain
components:

• DD Boost library. The DD Boost library is a component of the Dell Data Domain system. The DD Boost
library is embedded into the Veeam Data Mover setup. When you add a Microsoft Windows server to the
backup infrastructure, the DD Boost Library is automatically installed on the added server together with
Veeam Data Mover.

• DD Boost server. The DD Boost server is a target-side component. The DD Boost server runs on the OS of
the Dell Data Domain storage system.

Backup Infrastructure
To communicate with Dell Data Domain, Veeam Backup & Replication uses two Veeam Data Movers that are
responsible for data processing and transfer:

• Veeam Data Mover on the backup proxy

• Veeam Data Mover on the gateway server

The Dell Data Domain storage cannot host Veeam Data Mover. For this reason, to communicate with the Dell
Data Domain storage, you need to deploy a gateway server. Veeam Backup & Replication will automatically
deploy Veeam Data Mover on this gateway server. For more information, see Gateway Server.

815 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When any job addresses the backup repository, Veeam Data Mover on the gateway server establishes a
connection with Veeam Data Mover on the backup proxy, enabling efficient data transf er over LAN or WAN.

You define what gateway server to use when you assign a backup repository role to Dell Data Domain. You can
define the gateway server explicitly or instruct Veeam Backup & Replication to select it automatically.

IMP ORTANT

For Dell Data Domain storage systems working over Fibre Channel, you must explicitly define the gateway
server that will communicate with Dell Data Domain. As a gateway server, you must use a Microsoft
Windows server that is added to the backup infrastructure and has access to Dell Data Domain over Fibre
Channel.

Supported Protocols
Veeam Backup & Replication supports Dell Data Domain storage systems working over the following protocols:

• TCP/IP protocol: Veeam Backup & Replication communicates with the Dell Data Domain server by sending
commands over the network.

• Fibre Channel protocol: Veeam Backup & Replication communicates with the Dell Data Domain Fibre
Channel server by sending SCSI commands over Fibre Channel.

Considerations and Limitations for Dell Data Domain


General
If you plan to use Dell Data Domain as a backup repository, consider the following:

• We strongly recommend that you follow recommendations from this list and also recommendations from
this Veeam KB article.

• Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection.
You can disable the TLS connection with a registry value for the deduplicating storage appliances that do not
support the TLS connection. For more information, see this Veeam KB article.

• Use of Dell Data Domain with DD Boost does not guarantee improvement of job performance. It reduces
the load on the network and improves the network throughput.

816 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• NFS services must be enabled on Dell Data Domain. Otherwise, Veeam Backup & Replication will not be
able to access the storage system.

• Do not enable encryption for the jobs targeted at the deduplication storage appliance. Encryption has a
negative effect on the deduplication ratio. For more information, see Data Encryption.

Encryption can also affect the backup size: the size of a backup can be larger than the size of the original
VM. When you enable encryption, set data processing block size to 4 MB, and leave decompression on
target and block alignment enabled (enabled by default), the size of the backup increases by 1 MB for
each 4 MB data block. This is because Veeam Backup & Replication reads blocks of 4 MB, encrypts them,
adds 16 KB metadata to each data block and then aligns data blocks. This results in that each 4 MB data
block on the source becomes 5 MB block on the target.

• When you create a backup job targeted at an Dell Data Domain backup repository,
Veeam Backup & Replication will offer you to switch to optimized job settings and use the 4 MB size of
data block for workload data processing (the Storage optimization setting). It is recommended that you
use optimized job settings. Large data blocks produce a smaller metadata table that requires less memory
and CPU resources to process. For more information on storage optimization, see Data Compression and
Deduplication.

• Dell Data Domain does not support the reverse incremental backup method.

• You cannot use Dell Data Domain backup repositories as sources or targets for file copy jobs.

• The length of forward incremental and forever forward incremental backup chains (chains that contain one
full backup and a set of subsequent incremental backups) cannot be greater than 120 restore points. To
overcome this limitation, schedule full backups (active or synthetic) to split the backup chain into shorter
series. For example, to perform backups at 15-minute intervals 24 hours a day, you must schedule
synthetic fulls every day. In this scenario, intervals immediately after midnight may be skipped due to
duration of synthetic processing. For more information, see How Synthetic Full Backup Works.

• If you connect to an Dell Data Domain backup repository over Fibre Channel, you must explicitly define a
gateway server to communicate with Dell Data Domain. As a gateway server, you must use a Microsoft
Windows server that is added to the backup infrastructure and has access to the Dell Data Domain backup
repository over Fibre Channel.

• During backup repository rescan, Veeam Backup & Replication detects if the hard stream limit is set for a
storage unit, and displays this information in backup repository rescan statistics. If the hard stream limit is
exceeded when Veeam Backup & Replication runs tasks against the backup repository,
Veeam Backup & Replication will fail to create new I/O streams.

Immutability
This feature is available starting from Veeam Backup & Replication version 12.1 (build 12.1.0.2131).

If you plan to enable immutability for the Dell Data Domain deduplicating storage appliance, consider
information in this section. To learn more about Dell Data Domain immutability, see Dell Data Domain
Supported Features - Retention Lock.

• Veeam Backup & Replication supports only the compliance mode of Dell Data Domain retention lock. For
more information on retention lock, see Dell Technologies Article.

• Automatic retention lock must be disabled.

817 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The duration of the immutability period (the Make recent backups immutable setting) as well as the
duration of the long-term retention period (the Keep certain backups longer for archival purposes setting)
configured in Veeam Backup & Replication must lie in the range between the minimum and maximum
retention periods configured in Dell Data Domain. The minimum and maximum values are included into
the range.

If the immutability period configured in Veeam Backup & Replication lies outside the range configured in
Dell Data Domain, Veeam Backup & Replication does not allow you to proceed to the next step until the
value is changed.

If the long-term retention period configured in Veeam Backup & Replication is greater than the maximum
retention period configured in Dell Data Domain, Veeam Backup & Replication keeps backups immutable
for the period configured in the Veeam Backup & Replication settings but resets the expiration of the
backup immutability flag during each job run. While the actual number of days that the backup must be
kept immutable is greater than the maximum, Veeam Backup & Replication sets the expiration period
equal to the maximum.

If some operations, for example, evacuate or move, try to set the immutability period less than the
minimum period configured in Dell Data Domain, Veeam Backup & Replication sets the expiration period
for the immutability flag equal to the minimum retention period.

• Immutability is supported only for forward incremental backup chains. Once a backup file becomes
immutable, it can be merged or deleted only when the immutability time period expires.

• To use the immutability feature for backup copy jobs, enable the GFS retention policy . For more
information, see Long-Term Retention Policy (GFS) for Backup Copy Jobs.

Dell Data Domain Immutability and Veeam Agents

For more information on how immutability works with Veeam Agents, see the Backup to Deduplicating Storage
Appliances section in the Veeam Agent Management Guide.

Dell Data Domain Supported Features


The DD Boost technology offers a set of features for ad vanced data processing. Veeam Backup & Replication
supports the following features:

• Distributed Segment Processing

• Advanced Load Balancing and Link Failover

• Virtual Synthetics

• In-Flight Data Encryption

• Per Storage Unit Streams

• Retention Lock

In addition to these technologies, Veeam Backup & Replication supports in-flight data encryption and per
storage unit streams.

NOTE

You cannot configure Managed File Replication using Veeam Backup & Replication. However, you can
import and map backups replicated between Data Domain storage systems to backup, backup copy or
replication jobs, or perform restore operations from such backups.

818 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Distributed Segment Processing
Distributed Segment Processing lets Dell Data Domain "distribute" the deduplication process and perform a part
of data deduplication operations on the gateway server side.

Without Distributed Segment Processing, Dell Data Domain performs deduplication on the Dell Data Domain
storage system. The gateway server sends unfiltered data blocks to Dell Data Domain over the network. Data
segmentation, filtering and compression operations are performed on the target side, before data is written to
disk.

With Distributed Segment Processing, operations on data segmenta tion, filtering and compression are
performed on the gateway server side. The gateway server sends only unique data blocks to Dell Data Domain.
As a result, the load on the network reduces and the network throughput improves.

Advanced Load Balancing and Link Failover


Advanced Load Balancing and Link Failover allow you to balance data transfer load and route VM data traffic to
a working link in case of network outage problems.

Without Advanced Load Balancing, every gateway server connects to Data Domain on a dedicated Ethernet link.
Such configuration does not provide an ability to balance the data transfer load across the links. If a network
error occurs during the data transfer process, the backup job fails and needs to be restarted.

Advanced Load Balancing allows you to aggregate several Ethernet links into one interface group. As a result,
Dell Data Domain automatically balances the traffic load coming from several gateway servers united in one
group. If some link in the group goes down, Dell Data Domain a utomatically performs link failover, and the
backup traffic is routed to a working link.

Virtual Synthetics
Veeam Backup & Replication supports Virtual Synthetic Fulls by Dell Data Domain. Virtual Synthetic Fulls let you
synthesize a full backup on the target backup storage without physically copying data from source volumes. To
construct a full backup file, Dell Data Domain uses pointers to existing data segments on the target backup
storage. Virtual Synthetic Fulls reduce the workload on the network and b ackup infrastructure components and
increase the backup job performance.

In-Flight Data Encryption


Veeam Backup & Replication supports in-flight encryption introduced in Dell Data Domain Boost 3.0. If
necessary, you can enable data encryption at the backup repository level. Veeam Backup & Replication will
leverage the Dell Data Domain technology to encrypt data transported between the DD Boost library and Data
Domain system.

Per Storage Unit Streams


Veeam Backup & Replication supports per storage unit streams on Dell Data Domain. The maximum number of
parallel tasks that can be targeted at the backup repository (the Limit maximum concurrent tasks to N setting) is
applied to the storage unit, not the whole Dell Data Domain system.

Retention Lock
[This feature is available starting from Veeam Backup & Replication version 12.1 (build 12.1.0.2131).]

819 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Together with Data Domain Retention Lock, Veeam Backup & Replication allows you to prohibit deletion of data
from the Dell Data Domain deduplicating storage appliances by making that data temporarily immutable. This is
required for improved security: immutability protects your data from loss as a result of malware activity or
unplanned actions.

You can enable the immutability feature and specify the immutable period when adding or editing the Dell Data
Domain backup repository. For more information, see Configure Backup Repository Settings. Once imposed,
immutability prohibits deletion of data from the deduplicating storage appliance until the immutability
expiration date comes. Note that if you enable immutability and Veeam Backup & Replication does not start a
new backup chain and still continues the chain, the whole backup chain is marked as immutable. Once you
disable immutability, newly created backups are not marked as immutable.

In many respects, Dell Data Domain with enabled immutability works similarly to the hardened repository. For
more information on how repositories with immutability operate as a part of a scale-out backup repository, see
Hardened Repository as Performance Extent. For more information on how retention periods set in jobs and in
the deduplicating storage appliance correlate, see Retention Scenarios.

Accelerated Restore of Entire VM


To speed up entire VM restore on Dell Data Domain, Veeam Backup & Replication uses the mechanism of
sequential data reading from backups and parallel VM disks restore.

Dell Data Domain storage systems are optimized for sequential I/O operations. However, data blocks of VM
disks in backup files are stored not sequentially, but in the random order. If data blocks of VM disks are read at
random, the restore performance from backups on Dell Data Domain degrades.

To accelerate the restore process, Veeam Backup & Replication creates a map of data blocks in backup files. It
uses the created map to read data blocks of VM disks from backup files sequentially, as they res ide on disk.
Veeam Backup & Replication writes data blocks to target in the order in which they come from the target Veeam
Data Mover, restoring several VM disks in parallel.

This accelerated restore mechanism is enabled by default, and is used for the entire VM restore scenario.

NOTE

To further accelerate the process of entire VM restore, Veeam Backup & Replication reads VM data from
Dell Data Domain in multiple threads.

How Accelerated Restore Works


Entire VM restore from backups on Dell Data Domain is performed in the following way:

1. Veeam Backup & Replication opens all backup files in the backup chain, reads metadata from these backup
files and caches this metadata on the backup proxy that is assigned for the restore task.

2. Veeam Backup & Replication uses the cached metadata to build a map of data blocks. The map contains
references to VM data blocks, sorted by VM disks.

3. Every VM disks is processed in a separate task. For every task, Veeam Backup & Replication starts a
separate Veeam Data Mover on the backup proxy.

Veeam Data Movers read data blocks of VM disks from the backup repository sequentially, as these blocks
reside on disk, and put read data blocks to the buffer on the backup proxy.

820 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Data blocks are written to target in the order in which they come from the target Veeam Data Mover.

Backup Proxy for Accelerated Restore


Veeam Backup & Replication restores all disks of a VM through one backup proxy. In Microsoft Hyper -V
environments, the role of a backup proxy is assigned to the target Microsoft Hyper-V host — host to which the
VM is restored.

For every VM disk, Veeam Backup & Replication starts a separate Veeam Data Mover on the backup proxy. For
example, if you restore a VM with 10 disks, Veeam Backup & Replication starts 10 Veeam Data Movers on the
backup proxy.

The backup proxy assigned for the entire VM restore task must have enough RAM resources to be able to restore
VM disks in parallel. For every VM disk, 200 MB of RAM is required. The total amount of required RAM resources
is calculated by the following formula:

Total amount of RAM = Number of VM disks * 200 MB

Before starting the restore process, Veeam Backup & Replication checks the amount of RAM resources on the
backup proxy. If the backup proxy does not have enough RAM resources, Veeam Backup & Replication displays a
warning in the job session details and automatically fails over to a regular VM disks processing mode (data of
VM disks is read at random and VM disks are restored sequentially).

Limitations for Accelerated Restore


The accelerated restore of entire VM has the following limitations:

• Accelerated restore works on Dell Data Domain systems with DD Boost.

• If you restore a VM with dynamically expanding disks, the restore process may be slow.

• If Dell Data Domain is added as an extent to a scale-out backup repository, you must set the backup file
placement policy to Locality. If the backup file placement policy is set to Performance, parallel VM disk
restore will be disabled.

821 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
ExaGrid
You can use ExaGrid appliances as backup repositories.

Adaptive Deduplication
ExaGrid uses adaptive deduplication. Data deduplication is performed on the target storage system. After VM
data is written to disk, ExaGrid analyses bytes in the newly transferred data portions. ExaGrid compares versions
of data over time and stores only the differences to disk.

ExaGrid deduplicates data at the storage level. Identical data is detected throughout the whole storage system,
which increases the deduplication ratio.

Backup Infrastructure
To communicate with ExaGrid, Veeam Backup & Replication uses two Veeam Data Movers that are responsible
for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the ExaGrid appliance

ExaGrid does not host Veeam Data Mover permanently. When any task addresses an ExaGrid storage,
Veeam Backup & Replication deploys and starts the Veeam Data Mover on the ExaGrid appliance.

Veeam Data Mover establishes a connection with Veeam Data Mover on the off -host backup proxy, enabling
efficient data transfer over LAN or WAN.

Requirements and Recommendations for ExaGrid


To perform backup to ExaGrid appliances, it is recommended to configure backup repositories and jobs in the
following way:

Ba ckup repositories

On the ExaGrid side, do the following:

1. Create a new ExaGrid user account or update an existing one:

o Use only lower case symbols for the ExaGrid user name.

822 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Make sure that the ExaGrid user has the Backup Only role or another role with higher permissions.

2. Create a share on the ExaGrid appliance:

o The share must be located in the home directory of the user you set up in the previous step.

o Enable the E x a Grid-Veeam Accelerated Data Mover transport option for the created share.

o Leave default compression and deduplication settings for the share.

For more information, see the ExaGrid documentation.

3. Verify that the user account is added to the Veeam User Access Policy.

On the Veeam Backup & Replication side, do the following:

1. Add credentials for the ExaGrid user account you created in the previous steps:

o When you add ExaGrid servers to the Veeam backup infrastructure, and you use the UPN format for an
Active Directory account user name (for example, [email protected]), make sure you enter the
user name in lowercase letters only.

o Do not select E levate a ccount privileges automatically check box when setting up credentials for
authentication to the Exagrid appliance.

For more information, see Linux accounts.

2. Add the ExaGrid appliance as a managed server using the created credentials. For more information, see
Adding Linux Servers.

3. Configure an ExaGrid backup repository:

o When adding the repository, make sure the path to the share contains the user home directory.

o Set the Limit maximum concurrent tasks to N option to 10 tasks. This limit can be tuned up or down
with assistance from ExaGrid Customer Support.

Ba ckup Jobs

Configure backup job settings in the following way:

1. Use the forward incremental backup method.

2. Enable synthetic full backups and schedule them to run on a weekly basis.

3. Enable active full backups and schedule them to run on a monthly basis.

NOTE

Consider the following:

• Do not create multiple backup repositories directed at the same folder/path on the same device.
• We recommend against enabling encryption for the jobs targeted at the deduplication storage
appliance. Encryption has a negative effect on the deduplication ratio. For more information, see
Data Encryption.

• Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS
connection. You can disable the TLS connection with a registry value for the deduplicating storage
appliances that do not support the TLS connection. For more information, see this Veeam KB article.

For more information and recommendations on working with ExaGrid, see this Veeam KB article.

823 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
HPE StoreOnce
You can use HPE StoreOnce storage appliances as backup repositories.

To work with HPE StoreOnce, Veeam Backup & Replication leverages the HPE StoreOnce Catalyst technology
and two HPE StoreOnce components:

• HP E StoreOnce Catalyst agent. The HPE StoreOnce Catalyst agent is a component of the HPE StoreOnce
Catalyst software. The HPE StoreOnce Catalyst agent is embedded into the Veeam Data Mover setup.
When you add a Microsoft Windows server to the backup infrastructure, the HPE StoreOnce Catalyst agent
is automatically installed on the added server together with Veeam Data Mover.

• HP E StoreOnce appliance. The HPE StoreOnce appliance is an HPE StoreOnce storage system on which
Catalyst stores are created.

Backup Infrastructure
To communicate with HPE StoreOnce, Veeam Backup & Replication uses two Data Movers that are responsible
for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the gateway server

The HPE StoreOnce storage cannot host Veeam Data Mover. For this reason, to communicate with the HPE
StoreOnce storage, you need to deploy a gateway server. Veeam Backup & Replication will automatically deploy
Veeam Data Mover on this gateway server. For more information, see Gateway Server. For communicating with
the HPE StoreOnce storage appliances, the gateway server must run a 64-bit Microsoft Windows version.

When any job addresses the backup repository, Veeam Data Mover on the gateway server establishes a
connection with Veeam Data Mover on the off-host backup proxy, enabling efficient data transfer over LAN or
WAN.

The gateway server is selected when you assign a backup repository role to the HPE StoreOnce appliance. You
can define the gateway server explicitly or instruct Veeam Backup & Replication to select it automatically.

824 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

For work with HPE StoreOnce, Veeam Backup & Replication uses the Catalyst agent installed on the
gateway server. If you want to reduce the load on the network between the source and target side, assign
the gateway server role to a machine on the source side, closer to the off-host backup proxy.

Supported Protocols
Veeam Backup & Replication supports HPE StoreOnce storage systems working over the following protocols:

• TCP/IP protocol: Veeam Backup & Replication communicates with the HPE StoreOnce appliance by
sending commands over the LAN.

• Fibre Channel protocol: Veeam Backup & Replication communicates with the HPE StoreOnce appliance by
sending SCSI commands over Fibre Channel.

Data processing over Fibre Channel (FC) connectivity enables local area network-free backup to HP
StoreOnce, eliminates the load from backup activities and increases availability of LAN resources to
production workloads.

Considerations and Limitations for HPE StoreOnce


General
If you plan to use HPE StoreOnce as a backup repository for jobs other than file backup jobs, object storage
backup jobs and Veeam Plug-in for Enterprise Application jobs, consider the following recommendations and
limitations. These requirements and limitations apply only if you use HP E StoreOnce in the integration mode,
not the shared folder mode.

• Check that HPE StoreOnce that you plan to use is supported. For more information, see Backup Target.

• A Catalyst Store cannot be added to multiple backup servers.

• Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection.
You can disable the TLS connection with a registry value for the deduplicating storage appliances that do not
support the TLS connection. For more information, see this Veeam KB article.

• When you create a job targeted at HPE StoreOnce, Veeam Backup & Replication will offer you to switch to
optimized job settings and use the 4 MB size of data block for VM data processing. It is recommended that
you use optimized job settings. Large data blocks produce a smaller metadata table that requires less
memory and CPU resources to process.

• The HPE StoreOnce backup repository usually works in the Use per-machine backup files mode. For more
information, see Backup Chain Formats. Note that there are cases when the HPE StoreOnce backup
repository can store per-machine backups and non per-machine backups. For example, when backups are
evacuated to this repository from other extents in a SOBR. For more information, see Evacuating Backups
from Performance Extents. Note that restore from such backups can last longer than from per-machine
backups.

• We recommend against enabling encryption for the jobs targeted at the deduplication storage appliance.
Encryption has a negative effect on the deduplication ratio. For more information, see Data Encryption.

• HPE StoreOnce does not support the reverse incremental backup method.

• For backup jobs, HPE StoreOnce does not support the forever forward incremental backup method. When
creating a backup job, you must enable synthetic or active full backups. For more information on how to
enable such backups, see Backup Settings.

825 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The HPE StoreOnce backup repository does not support the Defragment and compact full backup file
option.

• You cannot perfom quick migration for Microsoft Hyper-V VMs started with Instant Recovery from the
backup that resides in the HPE StoreOnce backup repository.

• You cannot use HPE StoreOnce backup repositories as sources or targets for file copy jobs.

• You cannot copy backup files (VBK, VIB and VRB) manually to the HPE StoreOnce backup repository. To
copy such files, use backup copy jobs or evacuate backups if you use a scale-out backup repository.

• You cannot use the HPE StoreOnce backup repository as a cloud repository hosted behind a Cloud Connect
Gateway server.

• To optimize data transfer between two HPE StoreOnce repositories, use backup copy jobs for HPE
StoreOnce repositories. For more information on how to create jobs and recommendations for them, see
Creating Backup Copy Jobs for HPE StoreOnce Repositories.

• You can use HPE Cloud Bank Storage only as a target for backup copy jobs for HPE StoreOnce repositories.
Veeam Backup & Replication supports HPE Cloud Bank Storage for HPE StoreOnce software version 4.3.2
or later.

• Veeam Backup & Replication supports fixed block chunking functionality for HPE StoreOnce software
version 4.3.2 or later. To be able to use this functionality in Veeam Backup & Replication, check that the
Align backup file data blocks option is enabled in the repository settings.

• HPE StoreOnce has a limit on the number of concurrently opened files. Due to this limit, the maximum
length of backup chains (chains that contain one full backup and a set of subsequent incremental backups)
on HPE StoreOnce is also limited and depends on the particular storage model. For more information, see
the following table.

Table — Storage models and number of restore points

826 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Storage model Ma x imum number of restore points per backup chain

VSA

VSA Gen3 7

7 to 14 (for version 4.1.1 varies depending on the amount of available


VSA Gen4
memory)

P roliant Gen7

6200 14 (per node)

P roliant Gen8

2700 7

2900 14

4500 14

4700 14

4900 28

6500 28 (per node)

P roliant Gen9

3100 7

3500 14

5100 21

5500 35

6600 42 (per node)

P roliant Gen10

827 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3620 14

3640 14

5200 28

5250 28

5650 42

P roliant Gen10 Plus

3660 21

5260 28

5660 42

For more information and recommendations on working with HPE StoreOnce, see this Veeam KB article.

HPE StoreOnce and Unstructured Data Backup


If you plan to use HPE StoreOnce storage appliances for unstructured data backup, consider the following
recommendations for optimal performance:

• A StoreOnce system can have multiple Catalyst stores, and large backup loads (exceeding 1PB) should be
spread across more than one Catalyst store on the same StoreOnce system.

• Do not include Catalyst stores in a SOBR intended for unstructured data backups. This will reduce the
global deduplication of the StoreOnce system.

HPE StoreOnce and Veeam Plug-ins for Enterprise Applications


If you plan to use HPE StoreOnce as a backup repository for Veeam Plug -in for Oracle RMAN or Veeam Plug-in
for SAP HANA, the total number of stored files (data and metadata) must not exceed 3,000,000 per Catalyst
store. If necessary, multiple Catalyst stores may be created on the same StoreOnce system.

HPE StoreOnce and Immutability


If you plan to enable immutability for the HPE StoreOnce deduplicating storage appliance, consider the
following recommendations and limitations:

• HPE StoreOnce software version must be 4.3.2 or later.

• Dual Authorization must be enabled on HPE StoreOnce. For more information on Dual Authorization, see
HPE Support Center.

• [For Veeam Backup & Replication versions prior to 12.1 (build 12.1.0.2131)] The Ma x imum ISV Controlled
Da ta Retention setting must be set to 365000 on HPE StoreOnce. For more information, see HPE Support
Center.

828 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] Check that the Ma x imum ISV
Controlled Data Retention setting in HPE StoreOnce is greater than each of the following settings
configured in Veeam Backup & Replication:

o The immutability period (the Make recent backups immutable for setting).

o The long-term retention period (the Keep certain backups longer for archival purposes setting).

If a period configured in Veeam Backup & Replication is greater than the Ma x imum ISV Controlled Data
Retention setting, Veeam Backup & Replication keeps backups immutable for the period configured in the
Veeam Backup & Replication settings but resets the expiration of the backup immutability flag during each
job run. While the actual number of days that the backup must be kept immutable is greater than
Ma x imum ISV Controlled Data Retention, Veeam Backup & Replication sets the expiration period equal to
Ma x imum ISV Controlled Data Retention.

• [For Veeam Backup & Replication versions prior to 12.1 (build 12.1.0.2131)] HPE StoreOnce immutability
cannot be used for backup copy jobs for HPE StoreOnce repositories. Even if the target HPE StoreOnce
supports immutability, the copied backups are not immutable.

• To use the immutability feature for regular backup copy jobs (without HPE Catalyst Copy), enable the GFS
retention policy. For more information, see Long-Term Retention Policy (GFS) for Backup Copy Jobs.

• Immutability applies only if you use HPE StoreOnce in the integration mode, not the shared folder mode.

• Immutability is supported only for forward incremental backup chains. Once a backup file becomes
immutable, it can be merged or deleted only when the immutability time period expires.

HPE StoreOnce Immutability and Veeam Agents

For more information on how immutability works with Veeam Agents, see the Backup to Deduplicating Storage
Appliances section in the Veeam Agent Management Guide.

Several Backup Repositories on HPE StoreOnce


You can configure several backup repositories on one HPE StoreOnce appliance and associate them with
different gateway servers.

Consider the following:

• If you configure several backup repositories on HPE StoreOnce and add them as extents to a scale-out
backup repository, make sure that all backup files from one backup chain are stored on one extent. If
backup files from one backup chain are stored to different extents, the performance of transformation
processes will be lower. For more information about transformation performance, see this Veeam blog
post.

• HPE StoreOnce has a limit on the number of opened files that applies to the whole appliance. Tasks
targeted at different backup repositories on HPE StoreOnce and run in parallel will equally share this limit.

• For HPE StoreOnce working over Fibre Channel, there is a limitation on the number of connections from
one host. If you connect several backup repositories to one gateway, backup repositories will compete for
connections.

• Deduplication on HPE StoreOnce works within the limits of one object store.

• If your VMs contain similar data, it is recommended to create backup repositories on a single HPE
StoreOnce Catalyst Store. This minimizes backup job duration and reduces disk space used for backups.
For details, see this Veeam KB article.

829 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Operational Modes
Depending on the storage configuration and type of the backup target, HPE StoreOnce can work in the
following modes:

• Source-side deduplication

• Target-side deduplication

• Shared folder mode

Source-Side Data Deduplication


HPE StoreOnce performs source-side deduplication if the backup target meets the following requirements:

• You have a Catalyst license installed on HPE StoreOnce.

• You use a Catalyst store as a backup repository.

• The Catalyst store is configured to work in the Low Bandwidth mode (Primary Transfer Policy).

• The HPE StoreOnce Catalyst is added to the backup repository as a deduplicating storage appliance, not as
a shared folder.

To deduplicate data on the source side, HPE StoreOnce uses the HPE StoreOnce Catalyst agent. The HPE
StoreOnce Catalyst agent is a component of the HPE StoreOnce Catalyst software. It is installed on the gateway
server communicating with the HPE StoreOnce appliance.

HPE StoreOnce deduplicates data on the source side, before writing it to target:

1. During the backup job session, HPE StoreOnce analyzes data incoming to the HPE StoreOnce appliance in
chunks and computes a hash value for every data chunk. Hash values are stored in a n index on disk.

2. The HPE StoreOnce Catalyst agent calculates hash values for data chunks in a new data flow and sends
these hash values to target.

3. HPE StoreOnce identifies which data blocks are already saved on disk and communicates this information
to the HPE StoreOnce Catalyst agent. The HPE StoreOnce Catalyst agent sends only unique data blocks to
target.

As a result, the load on the network reduces, the backup job performance improves, and you can save on disk
space.

Target-Side Data Deduplication


HPE StoreOnce performs target-side deduplication if the backup target is configured in the following way:

• For a Catalyst store:

o The Catalyst store works in the High Bandwidth mode (Primary Transfer Policy is set to High
Bandwidth).

830 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o The Catalyst license is installed on the HPE StoreOnce (required).

o The Catalyst store is added to the backup repository as a deduplicating storage appliance, not as a
shared folder.

• For an SMB (CIFS) store:

o The Catalyst license is not required.

o The SMB (CIFS) store is added as a shared folder backup repository to the backup infrastructure.

For more information about working with SMB (CIFS) stores, see Shared Folder Mode.

HPE StoreOnce deduplicates data on the target side, after the data is transported to HPE StoreOnce:

1. HPE StoreOnce analyzes data incoming to the HPE StoreOnce appliance in chunks and creates a hash value
for every data chunk. Hash values are stored in an index on the target side.

2. HPE StoreOnce analyzes VM data transported to target and replaces identical data chunks with references
to data chunks that are already saved on disk.

As a result, only new data chunks are written to disk, which helps save on disk space.

Shared Folder Mode


If you do not have an HPE StoreOnce Catalyst license, you can add the HPE StoreOnce appliance as a shared
folder backup repository. In this mode, HPE StoreOnce will perform target-side deduplication.

If you work with HPE StoreOnce in the shared folder mode, the performance of backup jobs and transformation
processes is lower (in comparison with the integration mode, when HPE StoreOnce is added as a deduplicating
storage appliance).

HPE StoreOnce Supported Features


The HPE StoreOnce Catalyst technology offers a set of features for advanced data processing.
Veeam Backup & Replication supports the following features.

Synthetic Full Backups


HPE StoreOnce Catalyst improves synthetic full backup file creation and transformation performance. When
Veeam Backup & Replication creates or transforms a synthetic full backup, HPE StoreOnce does not physically
copy data between the existing backup chain and the target full backup file. Instead, it performs a metadata -
only operation — updates pointers to existing data blocks on the storage device. As a result, the operation
completes much faster. This mechanism helps improve performance of primary backup jobs and backup copy
jobs that are scheduled to create periodic archive full backups (GFS).

831 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Accelerated Data Recovery
Integration with HPE StoreOnce improves data recovery performance for different restore scenarios: Instant
Recovery, file-level recovery and application items recovery with Veeam Explorers.

WAN-based Catalyst Store Support


Veeam Backup & Replication provides advanced support for WAN-based HPE Catalyst stores. If a WAN
connection to HPE StoreOnce is weak, you can instruct Veeam Backup & Replication to compress VM data and
calculate checksums for data blocks going from the source side to HPE StoreOnce.

HPE StoreOnce Replication


HPE StoreOnce replication improves copying data between two HPE StoreOnce backup repositories. For more
information on copying, see Creating Backup Copy Jobs for HPE StoreOnce Repositories.

Independent Software Vendor (ISV) Controlled Data


Immutability (ISV-DI)
Together with HPE StoreOnce Independent Software Vendor (ISV) Controlled Data Immutability (ISV-DI),
Veeam Backup & Replication allows you to prohibit deletion of data from the HPE StoreOnce deduplicating
storage appliances by making that data temporarily immutable. This is required for improved security:
immutability protects your data from loss as a result of malware activity or unplanned actions.

You can enable the immutability feature and specify the immutable period when adding or editing the HPE
StoreOnce backup repository. For more information, see Configure Backup Repository Settings. Once imposed,
immutability prohibits deletion of data from the deduplicating storage appliance until the immutability
expiration date comes. Note that if you enable immutability and Veeam Backup & Replication does not start a
new backup chain and still continues the chain, the whole backup chain is marked as immutable. Once you
disable immutability, newly created backups are not marked as immutable.

In many respects, HPE StoreOnce with enabled immutability works similarly to the hardened repository. For
more information on how repositories with immutability operate as a part of a scale-out backup repository, see
Hardened Repository as Performance Extent. For more information on how retention periods set in jobs and in
the deduplicating storage appliance correlate, see Retention Scenarios.

Fixed Block Chunking


Together with fixed block chunking, Veeam Backup & Replication improves performance when creating
incremental and synthetic full backup files. Fixed block chunking improves performance up to 4 -5 times
compared to variable chunking,

Veeam Backup & Replication supports fixed block chunking functionality for HPE StoreOnce software version
4.3.2 or later. To be able to use this functionality in Veeam Backup & Replication, check that the Align backup
file data blocks option is enabled in the repository settings.

Fixed block chunking is supported for the following types of backups:

• Backups of VMware vSphere virtual machines created by Veeam Backup & Replication

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

• Backups of virtual and physical machines created by Veeam Agent for Microsoft Windows, Veeam Agent
for Linux, Veeam Agent for Oracle Solaris or Veeam Agent for IBM AIX

832 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

• Backups of RHV VMs created by Veeam Backup for RHV

For more information on issue that can occur, see this Veeam KB article.

Cloud Bank Storage


Veeam Backup & Replication supports using HPE Cloud Bank Storage — an extension of HPE StoreOnce Catalyst
that uses external object storage to store backup data. It is possible to use HPE Cloud Bank Storage as a target
for backup copy jobs for HPE StoreOnce repositories. This helps to reduce long-term retention costs.

Veeam Backup & Replication supports HPE Cloud Bank Storage for HPE StoreOnce software version 4.3.2 or
later.

Quantum DXi
You can use Quantum DXi appliances as backup repositories.

Quantum DXi Deduplication


Quantum DXi appliances use Quantum’s patented data deduplication technology. During backup data transfer,
Quantum analyses blocks in a data stream. Instead of copying redundant data blocks Quantum uses reference
pointers to existing blocks on the storage device.

Backup Infrastructure
To communicate with Quantum DXi, Veeam Backup & Replication uses two Veeam Data Movers that are
responsible for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the Quantum DXi appliance

Quantum DXi does not host the Veeam Data Mover permanently. When any task addresses a Quantum DXi
storage, Veeam Backup & Replication deploys and starts Veeam Data Mover on the Quantum DXi system.

Veeam Data Mover establishes a connection with Veeam Data Mover on the off -host backup proxy, enabling
efficient data transfer over LAN or WAN.

833 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection.
You can disable the TLS connection with a registry value for the deduplicating storage appliances that do
not support the TLS connection. For more information, see this Veeam KB article.

For more information and recommendations on working with Quantum DXi, see this Veeam KB article.

Backup Repository Configuration


Configure Quantum DXi backup repositories in the following way:

1. Create at least one share on each Quantum DXi appliance. Enable VDMS (Veeam Data Mover Service) for
the created share. Leave default compression and deduplication settings for the share. For m ore
information, see Quantum DXi documentation.

NOTE

When adding credentials for Quantum DXi, use only lower case symbols for the user name.

2. Configure Quantum DXi backup repositories and point them at the created shares on each Quantum DXi
appliance. Set the Limit maximum concurrent tasks to N option to 10 tasks. This limit can be tuned up or
down with assistance from Quantum DXi Customer Support.

When you add Quantum DXi servers to the Veeam backup infrastructure, make sure that you use the UPN
format for an Active Directory account user name (for example, [email protected]), and enter the
user name in lowercase letters only.

Backup Job Configuration


For the backup jobs, use the forward incremental backup method. We recommend that you enable synthetic full
and schedule them to run on a weekly basis. Also, enable active full backups and schedule them to run on a
monthly basis. For more information, see Backup Settings. We recommend that you do not enable encryption
for the jobs targeted at the deduplication storage appliance. Encryption has a negative effect on the
deduplication ratio. For more information, see Data Encryption.

Fujitsu ETERNUS CS800


You can use Fujitsu ETERNUS CS800 deduplicating storage appliances as backup repositories.

Fujitsu ETERNUS CS800 Deduplication


Fujitsu ETERNUS CS800 appliances use Fujitsu ETERNUS CS800 data deduplication technology. During backup
data transfer, Fujitsu analyses blocks in a data stream. Instead of copying redundant data blocks Fujitsu uses
reference pointers to existing blocks on the storage device.

Backup Infrastructure
To communicate with the Fujitsu appliance, Veeam Backup & Replication uses two Veeam Data Movers that are
responsible for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

834 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Veeam Data Mover on the Fujitsu appliance

Fujitsu does not host the Veeam Data Mover permanently. When any task addresses a Fujitsu storage,
Veeam Backup & Replication deploys and starts Veeam Data Mover on the Fujitsu system.

Veeam Data Mover establishes a connection with Veeam Data Mover on the off -host backup proxy, enabling
efficient data transfer over LAN or WAN.

NOTE

Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection.
You can disable the TLS connection with a registry value for the deduplicating storage a ppliances that do
not support the TLS connection. For more information, see this Veeam KB article.

Backup Repository Configuration


Configure Fujitsu backup repositories in the following way:

1. Create at least one share on each Fujitsu appliance. Enable VDMS (Veeam Data Mover Service) for the
created share. Leave default compression and deduplication settings for the share.

NOTE

When adding credentials for Fujitsu, use only lower case symbols for the user name.

2. Configure Fujitsu backup repositories and point them at the created shares on each Fujitsu appliance. Set
the Limit maximum concurrent tasks to N option to 10 tasks. This limit can be tuned up or down with
assistance from Fujitsu Customer Support.

When you add Fujitsu servers to the Veeam backup infrastructure, make sure that you use the UPN format
for an Active Directory account user name (for example, [email protected]), and enter the user name
in lowercase letters only.

Backup Job Configuration


For the backup jobs, use the forward incremental backup method. We recommend that you enable synthetic full
and schedule them to run on a weekly basis. Also, enable active full backups and schedule them to run on a
monthly basis. For more information, see Backup Settings. We recommend that you do not enable encryption
for the jobs targeted at the deduplication storage appliance. Encryption has a negative effect on the
deduplication ratio. For more information, see Data Encryption.

835 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Infinidat InfiniGuard
You can use Infinidat InfiniGuard appliances as backup repositories.

Infinidat InfiniGuard Deduplication


Infinidat InfiniGuard appliances use Infinidat InfiniGuard data deduplication technology. During backup data
transfer, Infinidat InfiniGuard analyses blocks in a data stream. Instead of copying redundant data blocks
Infinidat InfiniGuard uses reference pointers to existing blocks on the storage device.

Backup Infrastructure
To communicate with Infinidat Infiniguard, Veeam Backup & Replication uses two Veeam Data Movers that are
responsible for data processing and transfer:

• Veeam Data Mover on the off-host backup proxy

• Veeam Data Mover on the Infinidat InfiniGuard appliance

Infinidat InfiniGuard does not host the Veeam Data Mover permanently. When any task addresses a Infinidat
InfiniGuard storage, Veeam Backup & Replication deploys and starts Veeam Data Mover on the Infinidat
InfiniGuard system.

Veeam Data Mover establishes a connection with Veeam Data Mover on the off-host backup proxy, enabling
efficient data transfer over LAN or WAN.

NOTE

Since Veeam Backup & Replication version 12, deduplicating storage appliances use the TLS connection.
You can disable the TLS connection with a registry value for the deduplicating storage appliances that do
not support the TLS connection. For more information, see this Veeam KB article.

Backup Repository Configuration


Configure Infinidat InfiniGuard backup repositories in the following way:

1. Create at least one share on each Infinidat InfiniGuard appliance. E nable VDMS (Veeam Data Mover
Service) for the created share. Leave default compression and deduplication settings for the share.

836 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

When adding credentials for Infinidat InfiniGuard, use only lower case symbols for the user name.

2. Configure Infinidat InfiniGuard backup repositories and point them at the created shares on each Infinidat
InfiniGuard appliance. Set the Limit maximum concurrent tasks to N option to 10 tasks. This limit can be
tuned up or down with assistance from Infinidat InfiniGuard Customer Support.

When you add Infinidat InfiniGuard servers to the Veeam backup infrastructure, make sure that you use
the UPN format for an Active Directory account user name (for example, [email protected]), and
enter the user name in lowercase letters only.

Backup Job Configuration


For the backup jobs, use the forward incremental backup method. We recommend that you enable synthetic full
and schedule them to run on a weekly basis. Also, enable active full backups and schedule them to run on a
monthly basis. For more information, see Backup Settings. We recommend that you do not enable encryption
for the jobs targeted at the deduplication storage appliance. Encryption has a negative effect on the
deduplication ratio. For more information, see Data Encryption.

Adding Deduplicating Storage Appliances


This section describes how to add a deduplicating storage appliance as a backup repository.

Before you add a backup repository, check prerequisites. Then use the New Backup Repository wizard to add the
backup repository.

Before You Begin


Before you configure a backup repository, check the following prerequisites.

Dell Data Domain


• Dell Data Domain must meet software and hardware requirements. For more information, see System
Requirements.

• The DD Boost license must be installed on the Dell Data Domain system, DD Boost must be enabled and
configured.

• The gateway server that you plan to use for work with Dell Data Domain must be added to the backup
infrastructure.

If the Dell Data Domain storage system does not meet these requirements, you can add it as a SMB (CIFS)
folder. In this case, Veeam Backup & Replication will not use the DD Boost technology to work with Dell Data
Domain. For more information, see Dell Data Domain.

ExaGrid
• ExaGrid must meet software and hardware requirements. For more information, see System Requirements.

• To use ExaGrid as a backup repository, you must configure an ExaGrid share in ExaGrid Manager. For more
information on how to configure the share and repository settings, see ExaGrid.

837 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
HPE StoreOnce
• HPE StoreOnce must meet software and hardware requirements. For more information, see System
Requirements.

• The HPE StoreOnce Catalyst license must be installed on the HPE StoreOnce system.

• You must use a Catalyst store as a backup target.

• The gateway server that you plan to use for work with HPE StoreOnce system must be added to the
backup infrastructure.

• The client account that you plan to use to connect to HPE StoreOnce must have acces s permissions on the
Catalyst store where backup data will be kept.

If the HPE StoreOnce storage system does not meet these requirements, you can add it as a shared folder. In
this case, Veeam Backup & Replication will perform target-side deduplication. For more information, see HPE
StoreOnce.

Quantum DXi
• Quantum DXi must meet software and hardware requirements. For more information, see System
Requirements.

• To use Quantum DXi as a backup repository, you must configure a Quantum DXi share. For more
information, see Quantum DXi.

Fujitsu ETERNUS CS800


• Fujitsu ETERNUS CS800 must meet software requirements. For more information, see System
Requirements.

• To use Fujitsu ETERNUS CS800 as a backup repository, you must configure a Fujitsu share. For more
information, see Fujitsu ETERNUS CS800.

Infinidat InfiniGuard
• Infinidat InfiniGuard must meet software requirements. For more information, see System Requirements.

• To use Infinidat InfiniGuard as a backup repository, you must configure a Infinidat InfiniGuard share. For
more information, see Infinidat InfiniGuard.

Storage Appliances and Tapes


Storage appliances that are used to store backup data in filer (CIFS/NFS) or block device mode (iSCSI/FC/SAS)
are not supported if the backup data is offloaded to tapes and is no longer stored directly on the filer/block
device (Hierarchical Storage Management with Tape tier).

To offload data to tapes, make sure that:

• All of the backup data is stored on the appliance altogether (that is, all of the backup chains are stored on
the appliance as a whole and not scattered across multiple devices) and only copies are stored on tapes.

• These appliances emulate a tape system (VTL) as an access protocol for.

838 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ded uplicating Storage Appliance and the type of the backup
repository you want to add.

839 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Backup Repository Name and Description
At the Na me step of the wizard, specify a name and description for the backup repository:

1. In the Na me field, specify a name for the backup repository.

2. In the Description field, provide a description for future reference.

840 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Server Settings
Options that you can specify at the Server step of the wizard depend on the type of backup repository you are
adding.

Dell Data Domain


To configure settings for Dell Data Domain:

1. Specify connection settings for Dell Data Domain:

o If Dell Data Domain works over TCP, in the Ty p e in Data Domain server name field enter a full DNS
name, or IPv4 or IPv6 address of the Dell Data Domain server. Note that you can use IPv6 addresses
only if IPv6 communication is enabled as described in section IPv6 Support.

o If Dell Data Domain works over Fibre Channel, select the Use Fibre Channel (FC) connectivity check
box. In the Ty p e in Data Domain server name field, enter a name of the Data Domain Fibre Channel
server. To get the Data Domain Fibre Channel server name, in Data Domain System Manag er open the
Da ta Management > DD Boost > Fib re Channel tab.

2. In the Credentials field, specify credentials of the user account to connect to the Dell Data Domain server
or Dell Data Domain Fibre Channel server. If you have not set up credentials beforeha nd, click the Ma nage
a ccounts link at the bottom of the list or click Ad d on the right to add the credentials. For more
information, see Managing Credentials.
To connect to the Dell Data Domain server, you must use credentials for the DD Boost User. To specify the
DD Boost User account settings, in Data Domain System Manager, open the Da ta Management > DD Boost
Settings tab.

3. To use in-flight encryption between the backup proxy and Dell Data Domain, select the E nable DDBoost
encryption check box and choose the encryption level — Medium or High.

4. In the Ga teway server field, specify which gateway server you want to use:

o If you want Veeam Backup & Replication to select a gateway server automatically, leave Automatic
selection.

o If you want to select servers that can be used as gateway servers explicitly, click Choose next to the
Ga teway server field. In the Ga teway Server window, click Use the following gateway servers only and
select servers. The servers must have a direct access to the Dell Data Domain appliance and must be
located as close to the appliance as possible. Veeam Backup & Replication will choose the most
suitable server.

For more information on the gateway servers, their requirements and limitations, and how they are
selected, see Gateway Server.

IMP ORTANT

If you connect to Dell Data Domain over Fibre Channel, you must explicitly define the gateway servers to
communicate with Dell Data Domain. The servers you select must be added to the backup infrastructure
and must have access to the Dell Data Domain appliance over Fibre Channel.

841 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
ExaGrid, Quantum DXi, Fujitsu ETERNUS CS800 and Infinidat InfiniGuard
To configure settings for ExaGrid, Quantum DXi, Fujitsu ETERNUS CS800 or Infinidat InfiniGuard deduplicating
appliance:

1. From the Rep ository server list, select an appliance that you want to use as a backup repository. The
Rep ository server list contains only those servers that are added to the backup infrastructure. If the server
is not added to the backup infrastructure yet, you can click Ad d New to open the New Linux Server wizard.
For more information, see Managing Servers.

842 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Click P op ulate to see the appliance capacity and available free sp ace.

HPE StoreOnce Deduplicating Appliance


To configure settings for HPE StoreOnce:

1. In the Ty p e in HPE StoreOnce server name field, enter a full DNS name, or IPv4 or IPv6 address of the HPE
StoreOnce appliance. Note that you can use IPv6 addresses only if IPv6 communication is enabled as
described in section IPv6 Support.

2. If HPE StoreOnce works over Fibre Channel, select the Use Fibre Channel (FC) connectivity check box.

3. In the Credentials field, specify credentials of the client account to connect to the HPE StoreOnce
appliance. If you have not set up credentials beforehand, click the Ma nage accounts link at the bottom of
the list or click Ad d on the right to add the credentials. For more information, see Managing Credentials.

The client account that you plan to use to connect to HPE StoreOnce must have access per missions on a
Catalyst store where backup data will be kept. To check the client account permissions, in the HPE
StoreOnce management console, select the Catalyst store and open the P ermissions tab for it.

4. In the Ga teway server field, specify which gateway server you want to use:

o If you want Veeam Backup & Replication to select a gateway server automatically, leave Automatic
selection.

o If you want to select servers that can be used as gateway servers explicitly, click Choose next to the
Ga teway server field. In the Ga teway Server window, click Use the following gateway servers only and
select servers. The servers must have a direct access to the HPE StoreOnce appliance and must be
located as close to the appliance as possible. Veeam Backup & Replication will choose the most
suitable server.

For more information on the gateway servers, their requirements and limitations, and how they are
selected, see Gateway Server.

843 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

If you connect to HPE StoreOnce over Fibre Channel, you must explicitly define the gateway servers
to communicate with HPE StoreOnce appliance. The servers you select must be added to the backup
infrastructure and must have access to the HPE StoreOnce appliance over Fibre Channel.

5. If a WAN connection between the gateway server and the HPE StoreOnce appliance is weak, select the
Ga teway server and StoreOnce are connected over WAN check box. Veeam Backup & Replication will
compress VM data transported from the gateway server to the HPE StoreOnce a ppliance, and calculate
checksums for data blocks going from the gateway server to the HPE StoreOnce appliance.

844 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Configure Backup Repository Settings
At the Rep ository step of the wizard, configure general repository settings including path to the repository
folder and load control, and also advanced repository settings.

Configuring General Repository Settings


To configure general repository settings:

1. In the Loca tion section, specify a path to the folder where backup files must be stored. Click P op ulate to
check capacity and available free space in the selected location.

845 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. [For HPE StoreOnce or Dell Data Domain with immutability] To prohibit deletion of blocks of data from
the backup repository, select the Ma k e recent backups immutable for check box and specify the
immutability period. For more information on limitations and considerations for HPE StoreOnce with
immutability, see HPE StoreOnce and Immutability. For more information on limitations and
considerations for Dell Data Domain with immutability, see Dell Data Domain.

3. [For ExaGrid, Quantum DXi, Fujitsu ETERNUS CS800 and Infinidat InfiniGuard] Select the Use fast cloning
on XFS volumes check box to enable copy-on-write functionality. In terms of Veeam Backup & Replication,
this functionality is known as Fast Clone. For more information, see Fast Clone.

4. Use the Loa d control section to limit the number of concurrent tasks and data ingestion rate for the
backup repository. These settings will help you control the load on the backup repository and prevent possible
timeouts of storage I/O operations.

• Select the Limit maximum concurrent tasks check box and specify the maximum allowed number of
concurrent tasks for the backup repository. If this value is exceeded, Veeam Backup & Replication
will not start a new task until one of current tasks finishes. For more information, see Limiting the
Number of Concurrent Tasks.

NOTE

It is not recommended that you disable the Limit maximum concurrent tasks to N option for backup
repositories with per-machine backup chains. In case of per-machine backup chains, synthetic
operations (synthetic full backup, backup files merge and transformation) work in parallel for every
workload in the backup. The number of parallel operations is limited by the number of concurrent
tasks that can be performed on the backup repository. If you disable the Limit maximum concurrent
ta sks to N option (which results in using an unlimited number of slots), the load on the backup
repository may be high.

• Select the Limit read a nd write data rate to check box and specify the maximum rate to restrict the
total speed of reading and writing data to the backup repository disk. For more information, see
Limiting Combined Data Rate for Backup Repositories.

846 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The Limit read and write data rate to settings does not apply to health checks performed as part of
backup and backup copy jobs. Even if you limit read/write rate for a backup repository, the health
check will consume resources of the backup repository regardless of this setting. Consider this
limitation when configuring basic and health check schedules for backup and backup copy jobs.

Configuring Advanced Repository Settings


To configure advanced repository settings:

1. Click Ad vanced.

2. Use the Align backup file data b locks option to align VM data saved to a backup file at a 4 KB block
boundary. The value of the setting depends on the type of backup repository you are adding. For more
information, see Preconfigured Advanced Settings.

3. When you enable compression for a backup job, Veeam Backup & Replication compresses VM data at the
source side and then transports it to the target side. Writing compressed data to a deduplicating storage
appliance results in poor deduplication ratios as the number of matching blocks decreases. To overcome
this situation, select the Decompress backup data blocks before storing check box. If data compression is
enabled for a job, Veeam Backup & Replication will compress VM data on the source side, transport it to
the target side, decompress VM data on the target side and write raw VM data to the storage device to
achieve a higher deduplication ratio.

NOTE

Veeam Backup & Replication does not compress VM data if encryption is enabled for a job and the
Decompress backup data blocks before storing check box is selected in the settings of the target
backup repository. Therefore, in the job statistics, you may observe a higher amount of transferred
data (the Tra nsferred counter) as compared to a job for which encryption is disabled. For more
information on job statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the
Ba ckup Size column) is larger than the original VM size (the Orig inal Size column). For more
information on backup properties, see Viewing Backup Properties.

4. Deduplicating storage appliances do not support rotated drives. The This repository is backed by rotated
ha rd drives check box is disabled for all types of deduplicating storage appliances.

5. To create a separate backup file for every machine in the job, make sure that the Use per-machine backup
files check box is selected. If you clear the check box, Veeam Backup & Replication will create single-file
backups. For more information on the backup chain formats and their limitations, see Backup Chain
Formats.

NOTE

Changing of the Use p er-machine backup files setting after the repository was already created does
not take any effect. To change backup chain format, follow the instructions provided in Upgrading
Backup Chain Formats.

847 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Preconfigured Advanced Settings
Depending on the type of deduplicating storage appliance you use, Veeam Backup & Replication automatically
sets advanced settings to the following ones:

Dell Data Domain

• The Align backup file data blocks option is disabled and cannot be changed.

• The Decompress backup data blocks before storing option is enabled.

• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled.

ExaGrid
• The Align backup file data blocks option is disabled and must not be changed.

• The Decompress backup data blocks before storing option is enabled.

• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled.

• Limit max concurrent tasks is equal to 10 (recommended).

Quantum DXi

• The Align backup file data blocks option is disabled and must not be changed.

• The Decompress backup data blocks before storing option is enabled.

848 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled.

Fujitsu ETERNUS CS800


• The Align backup file data blocks option is enabled.

• The Decompress backup data blocks before storing option is enabled.

• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled.

Infinidat InfiniGuard
• The Align backup file data blocks option is enabled.

• The Decompress backup data blocks before storing option is enabled.

• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled.

HPE StoreOnce
• The Align backup file data blocks option is enabled and cannot be changed if E nforce fixed block chunking
is enabled on the HPE StoreOnce. In other cases, the option is disabled and must not be changed.

• The Decompress backup data blocks before storing option is enabled.

• The This repository is backed by rotated hard drives option is disabled and cannot be changed.

• The Use per-machine backup files option is enabled and cannot be changed.

849 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings
At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for file -level
and application items restore.

1. From the Mount Server list, select a server that you want to use as a mount server. The mount server is
required for file-level and application items restore. During the restore process,
Veeam Backup & Replication will mount the VM disks from the backup file residing in the back up
repository to the mount server. As a result, VM data will not have travel over the network, which will
reduce the load on the network and speed up the restore process. For more information, see Mount
Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder that will be used for writing cache during
mount operations.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

850 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Properties and Components
At the Review step of the wizard, review details of the backup repository and specify importing settings.

1. Review the backup repository settings and list of components that will be installed on the backup
repository server.

2. If the backup repository contains backups that were previously created by Veeam Backup & Replication,
select the Sea rch the repository for existing backups a nd import them automatically check box.
Veeam Backup & Replication will scan the backup repository to detect existing backup files and display
them in the Veeam Backup & Replication console under the Imported > Backups node.

3. If the backup repository contains guest file system index files that were previously created by
Veeam Backup & Replication, select the Imp ort guest file system index check box. Index files will be
imported with backup files, and you will be able to search for guest OS files inside imported backups.

851 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Backup Repository Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the backup repository to the backup
infrastructure.

852 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review details of the added backup repository. Then click Finish to exit the
wizard.

853 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Repositories with Rotated Drives
A backup repository can use rotated drives. Rotated drives can be detachable USB or eSATA hard drives. This
scenario can be helpful if you want to store backups on several external hard drives that you plan to regularly
move between different locations.

To use rotated drives, you must enable the This repository is backed by rotated hard drives option in the
advanced settings of the backup repository. When this option is enabled, Veeam Backup & Replication
recognizes the backup target as a backup repository with rotated drives and uses a specific algorithm to make
sure that the backup chain created on these drives is not broken.

Limitations for Backup Repositories with Rotated Drives


Backup repositories with rotated drives have the following limitations:

• On one managed server, you must create only one repository with rotated drives.

• You cannot store archive full backups (GFS backups) created with backup jobs or backup copy jobs in
backup repositories with rotated drives.

• You cannot rescan backup repositories with rotated drives.

• NFS backup repositories do not support rotated drives. If you enab le the This repository is backed by
rotated hard drives setting on the repository, Veeam Backup & Replication will ignore this setting.

• Scale-out backup repositories do not support rotated drives. If you enable the This repository is backed by
rotated hard drives setting on an extent, Veeam Backup & Replication will ignore this setting and will work
with such repository as with a standard extent.

• Repositories with rotated drives are not supported as archive repositories for NAS backup.

• Backup files stored on backup repositories with rotated drives are not subject for independent retention
policies. These backup files will not be deleted by the retention job.

In This Section
• How Repository with Rotated Drives Works

• Adding Backup Repositories with Rotated Drives

How Repository with Rotated Drives Works


You can use Microsoft Windows server or Linux server or SMB (CIFS) share as a backup repository with rotated
drives.

Microsoft Windows Backup Repository


Veeam Backup & Replication performs backup jobs and backup copy jobs targeted at a backup repository with
rotated drives in different ways.

854 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

When you specify retention settings for a backup job or a backup copy job targeted at a backup repository
with rotated drives, you must define the total number of restore points that you want to retain on all
drives in the set. You can specify retention in days or restore points. For example, if you set retention to 14
restore points, the job will keep the total of 14 restore points across all drives.

Backup Jobs
Backup jobs are performed in the following way:

1. During the first and subsequent runs of the job, Veeam Backup & Replication creates a regular backup
chain on the currently attached drive.

2. When the drives are swapped, the behavior depends on how you have configured the repository:

o If you have chosen to continue an existing backup chain, Veeam Backup & Replication starts the
backup chain anew. Veeam Backup & Replication creates a new full backup file on the drive, and this
full backup is used as a starting point for subsequent incremental backups until the drives are
swapped again.

o If you have chosen to delete the backups existing on the drive (all backups or backups created by a
specific job), Veeam Backup & Replication deletes the existing backup chains. Then
Veeam Backup & Replication starts the backup chain anew.

3. [For external drives attached to Microsoft Windows servers] Veeam Backup & Replication checks the
retention policy set for the job. If some backup files in the backup chain are outdated,
Veeam Backup & Replication removes them from the backup chain.

Backup Copy Jobs


Backup copy jobs are performed in the following way:

1. During the first and subsequent runs of the job, Veeam Backup & Replication creates a regular backup
chain on the currently attached drive.

2. When the drives are swapped, the behavior depends on how you have configured the repository:

o If you have chosen to continue an existing backup chain, the following applies:

855 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ If the attached drive is empty, Veeam Backup & Replication creates a full backup on it.

▪ If there is a backup chain on the drive, Veeam Backup & Replication checks whether this backup
chain is consistent. The consistent backup chain must contain a full backup and all incremental
backups that have been produced by the job. This requirement applies to all types of backup
chains: forever forward incremental and forward incremental. If the chain is consistent,
Veeam Backup & Replication creates a new incremental backup and adds it to the backup chain.
The latest incremental backup existing in the backup chain is used as a starting point for the new
incremental backup. If the chain is not consistent, Veeam Backup & Replication starts the backup
chain anew. It creates a new full backup file on the drive, and this full backup is used as a
starting point for subsequent incremental backups.

o If you have chosen to delete the backups existing on the drive (all backups or backups created by a
specific job), Veeam Backup & Replication deletes the existing backup chains. Then
Veeam Backup & Replication starts the backup chain anew.

3. [For external drives attached to Microsoft Windows servers] Veeam Backup & Replication checks the
retention policy set for the job. If some backup files in the backup chain are outdated,
Veeam Backup & Replication removes them from the backup chain.

Drive Detection
Drive letters for external drives may change when you add new volumes or storage hardware such as CD -ROM
on the server. In Microsoft Windows backup repositories, Veeam Backup & Replication can keep track of drives
and detect them even if the drive letter changes.

To detect a drive correctly, Veeam Backup & Replication must have a record about it in the configuration
database. Consider the following requirements:

• When you insert a drive for the first time, the drive is not registered in the configuration database. Such
drive must have the same letter as the one specified in the P a th to folder field in backup repository
settings. For more information, see Configuring Path and Load Control Settings.

If the drive has some other letter, Veeam Backup & Replication will not be able to detect and use it.

• When you insert a drive that has already been used and has some restore points on it, the drive is already
registered in the configuration database. Veeam Backup & Replication will be able to detect and use it,
even if the drive letter changes.

856 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If the drive letter of the already used drive changes and a job has not run yet, you cannot cha nge the
option that controls the behavior when rotated drives are swapped . To change the behavior, change the
drive letter back to the original one and change the option that controls the behavior, then change the
drive letter as required.

Linux and Shared Folder Backup Repository


If you use a Linux server or SMB (CIFS) share as a backup repository with rotated drives,
Veeam Backup & Replication employs a “cropped” mechanism of retention with rotated drives.
Veeam Backup & Replication keeps information only about the latest backup chain in the configuration
database. Information about previous backup chains is removed from the database. For this reason, the
retention policy set for the job may not work as expected.

1. During the first and subsequent runs of the job, Veeam Backup & Replication creates a regular backup
chain on the currently attached drive.

2. When the drives are swapped, the behavior depends on how you have configured the repository:

o If you have chosen to continue an existing backup chain, Veeam Backup & Replication starts the
backup chain anew. Veeam Backup & Replication creates a new full backup file on the drive, and this
full backup is used as a starting point for subsequent incremental backups until the drives are
swapped again.

o If you have chosen to delete the backups existing on the drive (all backups or backups created by a
specific job), Veeam Backup & Replication deletes the existing backup chains. Then
Veeam Backup & Replication starts the backup chain anew.

Veeam Backup & Replication starts a new backup chain on the drive. It removes the information from the
configuration database about the restore points from previous backup chains. Backup files related to these
previous restore points are not deleted, they remain on disk. This happens because
Veeam Backup & Replication applies the retention policy only to the current backup chain, not to previous
backup chains.

857 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deploying Backup Repositories with Rotated Drives
To deploy a backup repository with rotated drives, do the following:

1. Attach one of external drives from the set to a Microsoft Windows or Linux server. The server must be
added to the backup infrastructure. For more information on how to add a server, see Virtualization
Servers and Hosts.

You can also attach the external hard drive to the backup server itself. In this case, the VM traffic will path
through the backup server, which will produce additional workload on it.

2. Use the New Backup Repository wizard to add a direct attached storage. For more information, see Adding
Backup Repositories. Pay attention to the following settings:

a. At the Server step of the wizard, select the server to which the drive is attached.

b. At the Rep ository step of the wizard, in the P a th to folder field, specify a path to the folder where
backup files must be stored.

IMP ORTANT

Later, when you attach another external hard drive to the server for the first time, this drive
must have the same drive letter as specified in the P a th to folder field. For more information,
see Drive Detection.

c. Click the Ad vanced button. In the Storage Compatibility Settings window, select the This repository is
b a cked by rotated hard drives check box and choose how Veeam Backup & Replication will behave
when a drive is swapped:

▪ Continue an existing backup chain if present. Select this option to continue the backup chain
found on the drive.

858 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ Delete backups belonging to this job . Select this option to delete all backups created by the
currently running job.

▪ Delete all backups on the drive . Select this option to delete all backups created by
Veeam Backup & Replication and stored on the drive in the repository folder. Note that
Veeam Backup & Replication will delete all backups, even backups created by other jobs.

d. Configure other settings of the backup repository as required and finish working with the wizard.

859 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Object Storage Repositories
An object storage repository is a repository intended for long -term data storage and based on either a cloud
solution or S3 compatible on-premises storage solutions.

Starting from Veeam Backup & Replication version 12, to keep backups in object storage repositories, you no
longer need to add this repository as a part of the scale-out backup repository. Instead, you can backup directly
to object storage repositories. In this case, Veeam Backup & Replication will move all backups to object storage
and will retain them here according to the retention policy.

Veeam Backup & Replication supports the following types of object storage repositories:

• Amazon S3, Amazon S3 Glacier and AWS Snowball Edge

• S3 compatible, S3 compatible with data archiving

• Google Cloud

• IBM Cloud

• Wasabi Cloud Storage

• Microsoft Azure Blob, Azure Archive Storage and Azure Data Box

You can use object storage repositories as target repositories in the following ways:

• As target repositories for backup jobs and backup copy jobs.

TIP

You can also use object storage repositories as a source location from which backup copy jobs will
copy restore points.

• As target repositories for file backup jobs.

IMP ORTANT

You cannot keep backups created by file backup jobs in object storage repositories if they are added
as performance extents of the scale-out backup repository.

• As target repositories for backups of VMware Cloud Director virtual machines created by
Veeam Backup & Replication.

• As target repositories for backups of virtual and physical machines created by Veeam Agent for Microsoft
Windows or Veeam Agent for Linux.

• As target repositories for backups of macOS physical machines created by Veeam Agent for Mac.

• As target repositories for backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix
AHV.

• As target repositories for backups of RHV VMs created by Veeam Backup for RHV.

• As target repositories for backups of applications running on Kubernetes persistent volumes created by
Kasten K10 Plug-in for Veeam Backup & Replication.

860 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

You can keep backups of Kasten application in object storage repositories only in case they are used
as the capacity or archive extents of a scale-out backup repository. You cannot back up Kasten
application directly to backup object storage repositories or in case they are used as performance
extents of a scale-out backup repository.

• As target repositories for backups of configuration database created by Veeam Backup & Replication.

You can also use object storage repositories as the following parts of the scale-out backup repository:

• As a part of Performance Tier. Performance tier allows to quickly access the stored data. For more
information, see Performance Tier.

• As a part of Capacity Tier. Capacity tier of scale-out backup repository allows to offload existing backup
data directly to cloud-based object storage. For more information, see Capacity Tier.

• As a part of Archive Tier. Archive tier of scale-out backup repository allows to transport infrequently
accessed data from the capacity tier for archive storage. For more information, see Archive Tier.

Object Storage Repository Deployment


To communicate with an object storage repository, Veeam Backup & Replication uses an on-host or off-host
backup proxy to transfer data and a mount server to process guest OS applications and perform item recovery.

Depending on the type of a job, the on-host or off-host backup proxy connects to the object storage repository
using one of the following options:

• Directly — in this case, the on-host or off-host backup proxy transfers data directly to object storage. To
process data, Veeam Data Mover will run on the on-host or off-host backup proxy to process data.

• Using a gateway server — in this case, the on-host or off-host backup proxy transfers data to the object
storage repository through a gateway server. To process data, two Veeam Data Movers are used: the
source Veeam Data Mover that runs on the on-host or off-host backup proxy and the target Veeam Data
Mover that runs on the gateway server.

Considerations and Limitations


This section lists considerations and known limitations for object storage repositories.

General Considerations and Limitations


Consider the following limitations for object storage repositories:

• Make sure to open required ports to communicate with object storage repositories in advance. Consider
that a backup server and a gateway server must have internet access to verify that the certificates
installed on object storage repositories are valid. For more details, see Ports.

• If you use default network security configuration for helper appliances, make sure that they are compliant
with your internal security policies.

• You can add an object storage repository to a second backup server using credentials with the read -only
access permissions that allows you to perform data recovery options. If you use credentia ls with full-
access permissions, it will lead to unpredictable behavior and data loss.

861 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Consider the following:

• This option works for object storage repositories if they meet the following requirements:
o You plan to add these object storage repositories as a capacity or archive extent of a
scale-out backup repository.
o The object storage repositories do not have data encryption enabled.
You will not be able to add object storage repositories using credentials with read -only
permissions if encryption enabled on these repositories.
• You can use this option for direct backup object storage repositories added either as a
standalone repository or a performance extent of a scale-out backup repository.

• Object storage gateway appliances that are used to store backup data in filer (CIFS/NFS) or block device
mode (iSCSI/FC/SAS) are not supported if the backup data is offloaded to object storage and is no longer
stored directly on the appliance.

Such gateway appliances are only supported in the following cases:

o All of the backup data is stored on the appliance altogether (that is, all of the backup chains are
stored on the appliance as a whole and not scattered across multiple devices) and only additional
copies of the backup data are transported to object storage.

o These appliances emulate a tape system (VTL) as an access protocol for Veeam Backup & Replication.

o Data in object storage bucket/container must be managed solely by Veeam Backup & Replication,
including retention and data management. Enabling lifecycle rules is not supported, and may result in
backup and restore failures.

o Multi-factor authentication (MFA) is not supported for object storage repositories.

• Use one bucket per scale-out backup repository to reduce metadata. Creating folders for multiple scale-
out backup repositories within a bucket slows down processing, as metadata operations within the object
storage are handled per bucket.

• If a backup chain contains backup files that are marked as corrupted by Health Check, then such corrupted
files, as well as all subsequent files that go after the corrupted one are never offloaded. In such a scenario,
offload is only possible starting from the full backup file that succeeds the backup chain with corrupted
backups.

• For optimal processing, we recommend to set the default block size to 1MB in the storage settings of a
backup job. Larger block size can lead to multiple times larger incremental backups, while smaller block
sizes will create extra IO pressure on the object storage.

• Different object storage repositories mapped to the same cloud folder can be used for storing both the
capacity tier backups and the unstructured data backups.

IMP ORTANT

Consider the following:

• The same object storage repository (mapped to the same cloud folder) must not be used
across multiple Veeam Backup & Replication servers for the same purposes as it leads to
unpredictable system behavior and data loss.
• For the same reason, two object storage repositories mapped to the same cloud folder must
not be added to different scale-out backup repositories within one
Veeam Backup & Replication server.

862 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Within a scale-out backup repository, the mount server of a performance extent will act as a gateway
server of the capacity extent if all of the following is true:

a. You use SMB share/NFS share/deduplicating storage appliances as performance extents of y our scale-
out backup repository.

b. You have chosen Automatic selection for the gateway server at the Specify Shared Folder Settings
step of the New b ackup repository wizard.

c. For the object storage that you use as the capacity extent, you have not selected to connect to object
storage using a gateway server at the Account step of the New Object Repository wizard.

• The backup proxy that processes backup data must meet the following requirements:

o It must be an on-premises server as close as possible to a backup server.

o It must have access to the cloud storage that you use as an object storage repository.

• You cannot switch an object storage repository to Sealed Mode and to Maintenance Mode unless it is an
extent of a scale-out backup repository.

Considerations and Limitations for Direct Backup to Object


Storage
• Reverse incremental backup method is not supported.

• Synthetic full backup method is not supported.

• Compact full backup file option is not supported.

• You cannot use direct backup object storage repositories for backups of applications running on
Kubernetes persistent volumes created by Kasten K10 Plug -in for Veeam Backup & Replication.

• You cannot use direct backup object storage repositories to keep backups created with Veeam Plug-ins for
Enterprise Applications.

• You cannot use Amazon Glacier Storage and Azure Archive Storage as direct backup repositories.

• You cannot use direct backup object storage repositories to keep backups created with Veeam Agent for
Oracle Solaris and Veeam Agent for IBM AIX.

NOTE

Note that you can use direct backup object storage repositories to keep backups created with backup
copy jobs for Veeam Agent for IBM AIX and Veeam Agent for Oracle Solaris.

Limitations for Amazon, Wasabi Cloud Storage, S3 Compatible


and S3 Compatible with Data Archiving Object Storage
• Make sure that you add an S3-compatible object storage device fully compatible with the AWS S3
operations and AWS S3 Signature Version 4 standard.

• [For Amazon S3] Only the Standard , Standard -IA and One Zone-IA storage classes are supported. For more
information about Amazon S3 storage classes, see AWS Documentation.

• S3 compatible storage systems with the eventual data consistency model are not supported.

863 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• You cannot add as performance extents one Wasabi bucket as an S3 Compatible Object Storage and
another Wasabi bucket as a Wasabi Cloud Object Storage to the same type of tier (either performance tier
or capacity tier) of a scale-out backup repository.

• To be able to work with S3 compatible with Data Archiving object storage, you must enable the SOSAPI
functionality. For more information, see Working with Veeam Smart Object Storage API (SOSAPI).

Limitations for Microsoft Azure Object Storage


• [For Microsoft Azure Blob storage] Veeam Backup & Replication supports specific types of storage
accounts and tiers. For more information, see Microsoft Azure Storage Accounts.

• [For Microsoft Azure Blob storage] Veeam Backup & Replication does not support Azure Germany since
Microsoft closed Microsoft Cloud Deutschland.

• Veeam Backup & Replication supports the Versioning feature for Microsoft Azure object storage
repositories for which immutability is enabled.

• [For Microsoft Azure Archive storage] Microsoft Azure has certain limits (quotas) on maximum amount of
resources used. The quotas depend on the type of proxies you have selected. If you exhaust a quota, you
will be unable to use Microsoft Azure Archive storage. For more information about Microsoft Azure
quotas, see Microsoft Docs.

• [For Microsoft Azure Blob storage] Veeam Backup & Replication does not support soft delete for blobs.

• Veeam Backup & Replication performs operations only on a blob level. You cannot create Azure containers
or storage accounts from the backup infrastructure.

• Veeam Backup & Replication does not support object-level immutability and default immutability policies
assigned to Azure storage accounts. You must set immutability for an Azure container where backed -up
objects will reside. For more information, see Microsoft Docs.

Limitations for Google Cloud Object Storage


Currently, Veeam Backup & Replication does not support the Object Versioning and Bucket Lock features for
Google Cloud object storage.

IMP ORTANT

Enabling either any or both of these features on the bucket may result in unpredictable system behavior
and data loss, as well as in extra costs for storing objects that have been removed by the retention policy.
For more information, see Object Versioning and Bucket Lock.

Limitations for IBM Cloud Object Storage


• For IBM Cloud Object Storage on-premise, Veeam Backup & Replication supports versions starting from
3.15.0.44.

• Veeam Backup & Replication is supported on all IBM Cloud Object Storage (COS) deployment models. This
includes on-premise, public cloud, and hybrid models. For the IBM public cloud, the following storage
classes are supported: Standard, Vault, Cold Vault and Smart Tier.

• Veeam Backup & Replication does not support Archive and Accelerated Archive storage classes in the IBM
public cloud.

864 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations for Immutability
For more information, see the Immutability Considerations and Limitations section.

Health Check for Object Storage Repositories


You can instruct Veeam Backup & Replication to periodically perform a health check for the latest restore point
in the backup chain. An automatic health check can help you verify that VM data blocks are present in the object
storage repository and check the integrity of these blocks. It helps you a void a situation where a restore point
gets corrupted, making all dependent restore points corrupted, too. The health check helps ensure that the
restore point is consistent, and you will be able to restore data from this restore point.

During a health check, Veeam Backup & Replication performs a cyclic redundancy check (CRC) for metadata and
a hash check for VM data blocks in the backup file to verify their integrity. If during the health check
Veeam Backup & Replication detects corrupted data blocks in the latest restore point in the backup chain, it will
start the health check retry. During the health check retry, Veeam Backup & Replication will transport valid data
blocks from the source volume to the object storage repository. After the health check retry completes, the
transported data blocks are moved immediately to the latest backup in the backup chain.

NOTE

The health check retry will start only if the backups job meets the necessary requirements. Otherwise,
Veeam Backup & Replication will add healthy blocks to a new backup file after the next job run.

To allow Veeam Backup & Replication perform the health check of data blocks located in the object storage
repository, you must:

• Configure a proxy appliance located in the object storage at the Mount server step of the New Object
Rep ository wizard.

• Enable the health check when you configure a backup job and define its schedule. For more information,
see Specifying Health Check Settings.

By default, the health check is performed on the last Friday of every month. You can change the schedule
and run the health check weekly or monthly on specific days.

NOTE

Consider the following:

• If you perform health check for encrypted backup files, Veeam Backup & Replication will pass
encryption keys to the regular backup repository or cloud repository. For more information on
encryption, see Data Encryption.
• If you use Veeam Agent to back up machines and store their backups in object storage repositories,
you can also perform the health check for Veeam Agent backups. For more information, see the
Health Check for Object Storage section of the User Guide for Veeam Agent that you use to back up
data.

How Health Check Works


The health check is performed in the following way:

1. The health check starts according to the schedule.

865 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• The health check runs only after all jobs and operations that process a backup are completed
(for example, a backup job, a restore job, synthetic operations with backups and so on). If
some of these activities are started, the health check stops.
• If a health check session does not complete until the next scheduled run, this session will stop
and a new session will start according to the schedule.
• The health check skips verification of already processed data, however
Veeam Backup & Replication verifies the metadata of backup files that did not change
between health check sessions.

2. Veeam Backup & Replication performs CRC values check for backup metadata, verifies that blocks of data
are present in the object storage repository and checks their integrity.

During the health check, Veeam Backup & Replication verifies the latest restore point in the backup chain
(restore point created by the current backup job session — the session during which the health check is
performed). If the latest restore point in the backup chain is incomplete, Veeam Backup & Replication
checks the restore point preceding the latest restore point.

3. If the health check does not detect data corruption, the backup job session completes in a regular way. If
the health check detects corrupted data, Veeam Backup & Replication starts the health check retry
process.

Depending on the revealed data corruption, Veeam Backup & Replication performs the following actions:

o If the health check has detected corrupted backup metadata, Veeam Backup & Replication marks the
whole backup chain as corrupted in the configuration database. In this case, you must detach the
corrupted backup from the source job and you run a backup job again to create a new backup chain.

o If the health check detects corrupted blocks of data, Veeam Backup & Replication performs the health
check retry and attempts to repair the corrupted data blocks.

Health Check Retry Mode


If the health check detects corrupted data, the backup job will switch to the Retry mode and will start the
health check retry process. During the health check retry, Veeam Backup & Replication transports necessary
data blocks of the whole VM image from the source volume and saves transported data blocks to the latest
backup file in the object storage repository.

If Veeam Backup & Replication does not perform the health check retry, you must retry the job manually. In this
case, Veeam Backup & Replication produces a new backup file with healthy data blocks. You can use this backup
file to restore from the latest restore point.

For scheduled jobs, the number of health check retries is equal to the number of job retries specified in the job
settings. For jobs started manually, Veeam Backup & Replication performs 1 health check retry.

866 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

To allow Veeam Backup & Replication add the repaired data blocks to the latest restore point after
completing the health check, the backup job must meet the following requirements:

• The backup job must not be disabled.


• You must schedule the backups job to run automatically. For more information, see the Schedule
step of the New Backup Job wizard.
• The target object storage is not set to the Maintenance mode.
• Backup window settings must allow a backup job to run after the health check completes.

If the backup job does not meet these requirements, Veeam Backup & Replication will add the repaired
data blocks to a new restore point, created during a next run of the backup job.

Object Storage Repository Structure


After backups are moved to an object storage repository, Veeam Backup & Replication creates and maintains the
following structure of directories.

Directory Description

Veeam/Backup/ Standard folders created by Veeam Backup & Replication.

Rep ository_folder_name Contains information on the repository name and the repository ID.

Clients Contains backups.

Client catalogue Contains information on solutions that create backups to this repository.

Ba ckup catalogue Contains backup ID.

CloudStg Contains data blocks.

867 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Directory Description

MetaData Contains metadata and checkpoints.

Сonfig Contains information on the object storage repository infrastructure.

Owner Contains information on a repository owner.

Rep ository Contains information on a repository.

Immutability for Object Storage Repositories


Veeam Backup & Replication allows you to prohibit deletion of data from the object storage repository by
making that data temporarily immutable. It is done for increased security: immutability protects your data
against loss as a result of attacks, malware activity or any other injurious actions.

You can enable immutability for data stored in the following types of object storage repositories:

• Amazon S3

• S3-compatible

• Microsoft Azure Storage

• IBM Cloud Object Storage

• Wasabi Cloud Object Storage

After you enable immutability, Veeam Backup & Replication will prohibit data deletion from object storage
repositories until the immutability expiration date comes.

You will not be able to perform the following operations with the immutable data stored on object storage
repositories:

• Manual removal of data, as described in section Deleting Backups from Object Storage.

• Removal of data by the retention policy, as described in section Retention Policy.

• Removal of data using any cloud service provider tools.

• Removal of data by the cloud service provider technical support department.

• Removal of data by the Remove deleted items data after option, as described in section Maintenance
Settings.

868 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Consider the following:

• If retention policy for backups with GFS flags, backups created by VeeamZIP jobs and exported
backup files exceeds immutability settings, Veeam Backup & Replication applies retention that is
defined for these types of backups. Immutability settings defined for an object storage repository
are ignored.
• If you add an object storage repository as an extent of the performance tier, immutability depends
on the scale-out backups repository configuration. For more information, see Immutability for
Performance Tier.

Considerations and Limitations


For more information, see Considerations and Limitations.

Enabling Immutability
To enable immutability, you must do the following:

1. Configure the following settings when you create an S3 bucket or Azure container:

o Ama zon S3 Storage, S3 Compatible, IBM Cloud, Wasabi C loud — You must enable the Object Lock and
Versioning features on your S3 bucket when you create the bucket.

IMP ORTANT

Note that most vendors allow enabling Object Lock only at the moment of creating the bucket.

For more information on enabling the Object Lock and Versioning features, see these Amazon articles:
Creating a bucket, Using S3 Object Lock and Enabling versioning on buckets.

o Azure Storage — You must enable support for version-level WORM on the container and enable blob
versioning for your storage account when you create a storage account.

For more information on enabling version-level WORM for a container, see Microsoft Docs.

For more information on blob versioning for a storage account, see Microsoft Docs.

IMP ORTANT

When you create the storage account, by default the version-level immutability support option
is enabled. You must disable it, otherwise immutability will not be applied for your Azure object
storage. For more information, see Microsoft Docs.

2. Enable the immutability option when you add an object storage repository to the backup infrastructure at
the Container step (for Azure object storage repository) or Buck et step (for Amazon S3 or S3 compatible
object storage repositories) of the new Object Storage Repository wizard.

Considerations and Limitations


This section lists considerations and known limitations for object storage repositories.

869 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
General Considerations and Limitations
Consider the following immutability limitations:

• The maximum immutability period you can set in the Veeam Backup & Replication UI is 90 days. If you
want to set immutability to a longer period, use one of the following Veeam PowerShell cmdlets: Set-
VBRAmazonS3CompatibleRepository, Add-VBRAmazonS3CompatibleRepository, Set-
VBRAzureBlobRepository.

• Immutable data is preserved as described in Block Generation.

Amazon S3 Immutability Limitations


Consider the following immutability limitations for Amazon S3:

• After you have created an S3 bucket with Object Lock enabled, check that the default retention is
disabled.

The default retention may result in an unpredictable system behavior and data loss. However, note that
Veeam Backup & Replication will use Compliance object lock mode for each uploaded ob ject. For more
information on the retention modes, see AWS documentation. For more information on how to disable
retention settings for S3 bucket, see AWS documentation. For more information on how to disable
retention settings for Azure container, see Microsoft Docs.

• Versioning and Object Lock must NOT be enabled or disabled on buckets that have been added to
Veeam Backup & Replication as it may lead to unpredictable system behavior and data loss.

• [Amazon S3] If you plan to use the immutability feature with the existing S3 bucket containing backups
created by 9.5 Update 4, keep in mind that both Versioning and Object Lock must be enabled on the
bucket simultaneously and immediately before enabling the immutability feature. Any other approach will
lead to backup offload failures and inability to correctly interact with backups in the bucket.

Azure Blob Storage Immutability Limitations


Consider the following immutability limitations for Azure Blob storage:

• Make sure that the Azure Blob storage settings meet the following requirements: when you configure an
Azure storage account and an Azure container:

o When you create a storage account, make sure you enable versioning for blobs.

o When you create a storage account, do NOT enable version-level immutability. By default, this option
is enabled and you must disable it. For more information, see Microsoft Docs.

o When you create a container, you must enable version-level immutability. For more information, see
Microsoft Docs.

• The default immutability policies are not supported.

• [Azure Blob Storage] Do NOT enable immutability for already existing containers in the Azure portal.
Otherwise, Veeam Backup & Replication will not be able to process these containers properly and it may
result in data loss.

• Version-level immutability support for Azure storage accounts is not supported.

870 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Block Generation
To reduce I/O operations and associated costs, Veeam Backup & Replication will automatically add 10 days to
the immutability expiration date. This period is called Block Generation. You do not have to configure it, t he
Block Generation setting is applied automatically. For example, if you set your immutability period to 30 days
for your object storage repository, Veeam Backup & Replication will add 10 days to specific objects to reduce I/O
operations with the data blocks over time. Thus, you will have immutability set for 30 days + 10 days of Block
Generation set for data blocks in your object storage repositories.

How Block Generation Works


When the first data block (a full backup) arrives, its immutability period by default is set to 30 + 10 = 40 days.
The first full backup starts its generation, that will be appended with the incremental backups. All the
incremental backups within the generation (that is, within the 10-days period) will have the same immutability
expiration date as the full backup. For instance, a data block that was offloaded on day 9 will have the same
immutability expiration date as a data block offloaded on day 1. Thus we ensure that the immutability period for
all the data blocks within a generation is no less than 30 days.

To maintain the backup consistency, Veeam Backup & Replication can extend immutability expiration for all data
blocks in all backup chains (both active and inactive) and assign these blocks to a new generation. For example,
within one forward incremental backup chain, a full backup file can not be removed before an incremental
backup file. On the other hand, an incremental backup file makes no sense without relevant full backup file. So
the immutability period is extended for all data blocks in the backup chain.

With 10 days of immutability automatically added, it means there is no need to extend the immutability period
for the incremental backups in forward chain and for the unchanged blocks of current full backups in reverse
chain offloaded within those 10 days. On the 11th day, though, the immutability period will have to be extended
(to ensure that the immutability period for all the data blocks within a generation is no less than 30 days).

NOTE

Consider the following:

• For data blocks located in object storage repositories, Veeam Backup & Replication extends
immutability period for every data block of every backup file in the whole backup chains, even in
inactive part.
• Veeam Backup & Replication will not extended immutability for the data blocks that are not used in
any existing backup files.

Adding Object Storage Repositories


You can add the following types of object storage repositories:

• S3 Compatible Object Storage, S3 Compatible Object Storage with Data Archiving

• Amazon S3 Object Storage, Amazon S3 Glacier Storage and AWS Snowball Edge

• Google Cloud Object Storage

• IBM Cloud Object Storage

• Microsoft Azure Object Storage, Microsoft Azure Archive Storage and Data Box

• Wasabi Cloud Object Storage

• Working with Veeam Smart Object Storage API (SOSAPI)

871 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding S3 Compatible Object Storage
Before you add an S3 compatible object storage and S3 compatible object storage with data archiving, check
prerequisites. After that, use the New Object Storage Repository wizard.

Adding S3 Compatible Object Storage


This section describes how to add S3 compatible object storage to the backup infrastructure.

To add S3 compatible object storage, use the New Ob ject Storage Repository wizard.

872 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > S3 Compatible > S3 Compatible.

873 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

874 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. In the Service point field, specify an endpoint address and a port number of your S3 compatible object
storage.

2. In the Reg ion field, specify a region.

3. From the Credentials drop-down list, select user credentials to access your S3 compatible object storage.

If you already have a credentials record that was configured in advance, select it from the drop -down list.
Otherwise, click Ad d and provide your access and secret keys, as described in section Access Keys for AWS
Users. You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

4. Next to the Connection mode field, click Choose and specify how Veeam Backup & Replication will access
the object storage repository:

o Direct — select this option if you want Veeam Backup & Replication to use a proxy server to transfer
data from processed VM or file share to object storage repositories.

NOTE

Consider the following:

• Make sure that a proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

o Through gateway server — select this option if you want Veeam Backup & Replication to use a
gateway server to transfer data from processed VM or file share to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your Veeam Backup & Replication
infrastructure and has internet connection. Note that you must add the server to the
Veeam Backup & Replication infrastructure beforehand. Before you add the server, check the
following Considerations and Limitations. For more information on how to add a server, see
Virtualization Servers and Hosts.

NOTE

By default, if Veeam Agent stores data in S3 compatible objects storage repositories, it transfers
data using a gateway server. If you want Veeam Agent to access repositories directly or using
specific credentials, you must specify the Access Permissions settings.

875 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
876 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify the bucket and folder where you will store data, and define storage
limits and immutability settings that Veeam Backup & Replication will apply to data in the object storage.

1. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

Note that you must create the bucket where you want to store your backup data beforehand.

2. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

4. Select the Ma k e recent backups immutable for check box to prohibit deletion of blocks of data from object
storage. Specify the immutability period. For more information, see Immutability.

Note that the maximum immutability period you can set in the Veeam Backup & Replication UI is 90 days.
If you want to set immutability to a longer period, use the Set-VBRAmazonS3CompatibleRepository
cmdlet.

877 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations and configure a helper appliance. The helper appliance is a temporary host that
Veeam Backup & Replication deploys on your S3 compatible storage to perform a health check of backup files
and apply retention to unstructured data backup files. For more information, see Health Check for Object
Storage Repositories and Helper Appliance in Unstructured Data Backup. After Veeam Backup & Replication
completes these operations, it removes the helper appliance from the S3 compatible storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

5. To specify the helper appliance settings, click Configure. From the Ma naged server drop-down list,
select a server that you want to use as the helper appliance.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

878 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
879 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported backups.

880 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

881 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding S3 Compatible with Data Archiving Object Storage

This section describes how to add S3 compatible object storage with data archiving to the backup infrastructure.
You can only use this repository as an archive extent of the scale-out backup repository. For more information,
see Archive Tier.

To add S3 compatible object storage with data archiving, use the New Ob ject Storage Repository wizard.

882 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > S3 Compatible > S3 Compatible with Data
Archiving.

883 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

884 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection and archiver appliance settings. An archiver appliance
is an auxiliary machine that transfers data from S3 compatible object storage to S3 compatible object storage
with data archive. By default, this role is assigned to the backup server. You can assign the role of an archiver
appliance to any Windows-based or Linux-based machine added to your Veeam Backup & Replication
infrastructure. For information on how to add a server, see Adding Microsoft Windows Servers and Adding Linux
Servers.

1. In the Service point field, specify an endpoint address and a port number of your S3 compatible object
storage with data archive.

2. In the Reg ion field, specify a region.

3. From the Credentials drop-down list, select user credentials to access your S3 compatible object storage
with data archive.

If you already have a credentials record that was configured in advance, select it from the drop -down list.
Otherwise, click Ad d and provide your access and secret keys, as described in Access Keys for AWS Users.
You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

4. From the Archiver appliance drop-down, select the archiver appliance. Click Ad d New to add a new
archiver appliance to your backup infrastructure. For information on how to add a server, see Adding
Microsoft Windows Servers and Adding Linux Servers.

885 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify the bucket and folder where you will store data, and define storage
limits and immutability settings that Veeam Backup & Replication will apply to data in the object storage.

1. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

Note that you must create the bucket where you want to store your backup data beforehand.

2. In the Folder field, enter a cloud folder name to which you want to map your S3 compatible object storage
with data archive. Alternatively, click Browse and either select an existing folder or click New Folder.

3. To prohibit deletion of blocks of data from S3 compatible object storage with data archive, select the
Ma k e backups immutable for the entire duration of their r etention policy check box. The immutability
period will be equal to the retention period (if any) of the data blocks. All the types of files that are
eligible for archive storage can be made immutable. For more information on the immutability feature and
the retention policy for each file type, see Immutability for Archive Tier.

Keep in mind that to use immutability, you must enable the Object Lock and Versioning features on your
S3 bucket at the time when you create the bucket. For more information, see Preparing to Use
Immutability.

886 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Amazon S3 Object Storage, Amazon S3 Glacier Storage and AWS


Snowball Edge
Before you add an Amazon S3 storage, Amazon Glacier or Amazon Snowball Edge to the backup infrastructure,
check prerequisites. After that, use the New Object Storage Repository wizard.

Adding Amazon S3 Storage

This section describes how to add Amazon S3 object storage to the backup infrastructure. For information on
Amazon S3 object storage, see AWS Documentation.

To add Amazon S3 object storage, use the New Object Storage Repository wizard.

887 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Amazon S3 > Amazon S3.

888 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

889 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. From the Credentials drop-down list, select user credentials to access your Amazon S3 object storage.

If you already have a credentials record that was configured in advance, select it from the drop -down list.
Otherwise, click Ad d and provide your access and secret keys, as described in section Access Keys for AWS
Users. You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

The user account must have permissions listed in section Permissions.

2. From the AW S region drop-down list, select the AWS region where the Amazon S3 bucket is located.

3. Next to the Connection mode field, click Choose and specify how a VMware backup proxy will transfer
data to the object storage repository:

o Direct — select this option if you want a backup proxy to transfer data from the processed machines or
file shares directly to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• If Veeam Agent stores data in other than S3 compatible objects storage repositories, it
does not use a backup proxy and transfers data directly to object storage repositor ies.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

890 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer op erations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

891 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify Amazon S3 bucket and folder that will be used to store data:

1. From the Da ta center region drop-down list, select a region.

2. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

IMP ORTANT

You must create the bucket where you want to store your backup data beforehand. When you create
a bucket, consider Amazon bucket naming rules. It is not recommended that you use dots (.) in the
bucket name. For more information on bucket naming rules, see AWS Documentation.

If the FIPS-compliant operation mode is enabled and the bucket you want to add is non-FIPS compliant,
the warning will be displayed. For more information, see FIPS Compliance.

3. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

IMP ORTANT

Veeam Backup & Replication supports specific storage classes. For more information, see
Considerations and Limitations.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

4. Select the Ma k e recent backups immutable for check box to prohibit deletion of blocks of data from object
storage. Specify the immutability period. For more information, see Immutability.

Note that the maximum immutability period you can set in the Veeam Backup & Replication UI is 90 days.
If you want to set immutability to a longer period, use the Set-VBRAmazonS3Repository cmdlet.

5. If you plan to access your backup data in an infrequent manner, select the Use infrequent access storage
cla ss check box to mark each block as Standard IA ( Standard Infrequent Access ).

6. To enable Amazon S3 One Zone-Infrequent Access , select the Store backups in a single availability zone
only check box. For more information, see AWS Documentation.

IMP ORTANT

If you enable this option and plan to use this object storage as a performance or capacity tier, do not
target to this repository any jobs that constantly send backup data to this storage: scheduled regular
backup and backup copy jobs that run without GFS, jobs with transactions logs enabled, jobs created
by Veeam Enterprise Plug-ins. Otherwise, it will result in higher costs.

892 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
893 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations, and configure a helper appliance. The helper appliance is a temporary EC2 instance that
Veeam Backup & Replication deploys on your S3 storage to perform a health check of backup files and apply
retention to unstructured data backup files. For more information, see Health Check for Object Storage
Repositories and Helper Appliance in Unstructured Data Backup. After Veeam Backup & Replication completes
these operations, it removes the helper appliance from the S3 storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

894 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

Configuring Helper Appliance


To configure the helper appliance, at the Mount Server step, click Configure and in the Helper Appliance
Settings window, specify the following settings:

1. From the E C2 instance type drop-down list, select the EC2 instance type for the helper appliance.
The EC2 instance type affects the speed and the cost of the operations that the helper appliance
applies to backup files. For information on instance types, see AWS Documentation.

2. From the Ama zon VPC drop-down list, select the Amazon VPC where Veeam Backup & Replication
will launch the EC2 instance. For information on the Amazon VPC, see AWS Documentation.

To be able to select the necessary VPC from the drop -down list, you must create it beforehand as
described in the AWS Documentation.

3. From the Sub net drop-down list, select the subnet where the helper appliance will reside. For
information on the subnets for Amazon VPC, see AWS Documentation.

To be able to select the necessary subnet from the drop -down list, you must create it beforehand as
described in the AWS Documentation.

4. From the Security g roup drop-down list, select a security group that will be associated with the
helper appliance. For information on security groups for Amazon VPC, see AWS Documentation.

To be able to select the necessary security group from the drop -down list, you must create it
beforehand as described in the AWS Documentation.

5. In the Red irector port field, specify the TCP port that Veeam Backup & Replication will use to route
requests between the helper appliance and backup infrastructure components.

6. Click OK.

895 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

896 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported backups.

897 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

898 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Amazon S3 Glacier Storage

Veeam Backup & Replication uses Amazon S3 Glacier object storage with Amazon S3 service. For more
information about Amazon S3 storage classes that you can use for this object storage repository, see AWS
Documentation.

NOTE

Veeam Backup & Replication does not create or use any S3 Glacier vaults in your AWS environment. Glacier
vaults is an archive storage solution independent from AWS. It uses storage containers named vaults
(opposed to S3 buckets) and its own set of APIs to upload and retrieve data.

Amazon S3 Glacier storage uses S3 APIs to manage data. It also uses S3 storage as a repository for
metadata of the Glacier-stored objects. Veeam Backup & Replication assigns the added storage class to
backups stored in the repository. That is why the archived backups remain in Amazon S3 and cannot be
accessed directly through the Amazon S3 service.

You can only use this repository as an archive extent of the scale-out backup repository. For more information,
see Archive Tier.

To add Amazon S3 Glacier object storage, use the New Ob ject Storage Repository wizard.

899 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Amazon S3 > Amazon S3 Glacier.

900 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for the new object storage
repository and to provide a description for future reference.

901 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. From the Credentials drop-down list, select user credentials to access your Amazon S3 object storage.

If you already have a credentials record that was configured in advance, select it from the drop-down list.
Otherwise, click Ad d and provide your access and secret keys, as described in section Access Keys for AWS
Users. You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

The user account must have permissions listed in section Permissions.

2. From the AW S region drop-down list, select the geographical location of the Amazon datacenter.

3. To specify how Veeam Backup & Replication will access the object storage repository, click Choose and in
the Connection mode window specify the following settings:

o Direct — select this option if you want Veeam Backup & Replication to use a proxy server to transfer
data from processed VM or file share to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

NOTE

The gateway server should have direct connection to AWS service endpoints. HTTP(S) proxy
servers are not supported. For more information, see Ports.

902 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

903 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify Amazon S3 bucket and folder that will be used to store data:

1. From the Da ta center drop-down list, the AWS region where the Amazon S3 bucket is located.

2. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

IMP ORTANT

You must create the bucket where you want to store your backup data beforehand. When you create
a bucket, consider Amazon bucket naming rules. It is not recommended that you use dots (.) in the
bucket name. For more information on bucket naming rules, see AWS Documentation.

If the FIPS-compliant operation mode is enabled and the bucket you want to add is non-FIPS compliant,
the warning will be displayed. For more information, see FIPS Compliance.

3. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

4. To prohibit deletion of blocks of data from object storage, select the Ma ke backups immutable for the
entire duration of their retention policy check box. The immutability period will be equal to the retention
period (if any) of the data blocks. All the types of files that are eligible for archive storage can be made
immutable. For more information on the immutability feature and the retention policy for each file type,
see Immutability for Archive Tier.

Keep in mind that to use immutability, you must enable the Object Lock and Versioning features on your
S3 bucket at the time when you create the bucket. For more information, see Preparing to Use
Immutability.

904 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Object Storage Class Settings

At the Storage Class step of the wizards, specify a storage class that you want assign to data blocks that you
keep in Amazon S3 Glacier object storage. For more information on Amazon S3 archive storage classes, see AWS
Documentation.

• Select the Deep Archive option to assign the Amazon S3 Glacier Deep Archive storage class to data blocks.
Use this option if you want to keep data for more than 7 years and do not plan to access it.

Note that to get data from this type of a backup, you must first retrieve data from Archive Tier. For more
information, see Restore from Archive Tier.

• Select the Flexible retrieval option to assign the Amazon S3 Glacier Flexible Retrieval storage class to data
blocks. Use this option if you want to access data in infrequent manner.

Note that to get data from this type of a backup, you must first retrieve data from Archive Tier. For more
information, see Restore from Archive Tier.

• Select the Instant retrieval option to assign the Amazon S3 Glacier Instant Retrieval storage class to data
blocks. Use this option if you plan to access your backup data immediately. In this case, you do not need to
retrieve data from Archive Tier and can immediately initiate any type of the data recovery operation.

905 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Archiver Appliance

At the Archiver Appliance step of the wizard, you can specify the archiver appliance settings. An archiver
appliance is an auxiliary instance that is necessary for transferring the data from Amazon S3 to Amazon S3
Glacier. For more information, see the Archiver Appliance section.

You can specify archiver appliance in one of the following ways:

• Use the default settings. In that case, Veeam Backup & Replication will select the necessary settings from
those available in your account, or will create for you new settings for the EC2 instance type, Amazon VPC,
subnet, security group and redirector port.

• Specify the settings manually:

a. Click Customize.

b. From the E C2 instance type drop-down list, select the instance type for the proxy appliance. The EC2
instance type affects the speed and the cost of transferring the backup files to the Archive Tier of a
scale-out backup repository. For information on instance types, see AWS Documentation.

c. From the Ama zon VPC drop-down list, select the Amazon VPC where Veeam Backup & Replication will
launch the target instance. For information on the Amazon VPC, see AWS Documentation. For details
on the EC2 instant types used by Veeam Backup & Replication, see this Veeam KB article.

d. From the Sub net drop-down list, select the subnet for the proxy appliance.

e. From the Security group drop-down list, select a security group that will be associated with the proxy
appliance. For information on security groups for Amazon VPC, see AWS Documentation.

f. In the Red irector port field, specify the TCP port that Veeam Backup & Replication will use to route
requests between the proxy appliance and backup infrastructure components.

g. Click OK.

906 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding AWS Snowball Edge Storage

AWS Snowball Edge is a physical device which you can request for a short period of time from Amazon. You can
temporarily attach it to the backup infrastructure and use as an object storage repository. For more information
about ordering AWS Snowball Edge and preparing to use it, see this Amazon article.

This device may become useful when you need to offload a significant number of backup files occupying storage
space on your extents, as offloading data to the AWS Snowball Edge device is much faster than transferring the
same amount of data directly to Amazon object storage. Once you have offloaded backups to AWS Snowball
Edge, you need to ship the device back to Amazon for further data synchronization with your storage account,
as described in section Seeding Backups to AWS Snowball Edge Storage.

To add AWS Snowball Edge storage, do the following:

1. Check prerequisites.

2. Launch the New Object Storage Repository wizard.

3. Specify object storage name.

4. Specify object storage account.

5. Specify object storage settings.

6. Finish working with the wizard.

907 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin

Before you add AWS Snowball Edge storage to the backup infrastructure, check the following prerequisites:

• To maintain the device performance, be sure to select 1 MB or 4 MB as the storage optimization option
when you configure a backup job. For more information on the optimization, see Storage Optimization.

• When you configure a scale-out backup repository with AWS Snowball Edge storage or performance tier in
a scale-out backup repository, it is recommended to only use the copy policy. This way you keep copy of
the data on your local storage which helps you reduce the risk of data loss if the device is damaged during
shipping. It will also ensure that the backup data is available for restore operations while AWS Snowball
Edge storage is in shipment.

• For information on FIPS status of AWS Snowball Edge storage, see Amazon official updates.

• You can add only AWS Snowball Edge storage to a scale-out backup repository.

908 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Amazon S3 > AW S Snowball EdgeS3.

909 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

TIP

Set the maximum number of concurrent task to a reasonable number to avoid overloading if you plan to
upload significant amount of backup chains to the device.

910 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. In the Service point field, specify a service point address of your AWS Snowball Edge device and define a
port.

To get information on the IP address that must be used as a service point, see the AWS Snowball Edge
Developer Guide.

To get information on the port you must specify, see the AWS Snowball Edge Developer Guide. By default,
the 8443 port is used.

1. In the Reg ion field, type "snow".

2. From the Credentials drop-down list, select user credentials to access your AWS Snowball Edge storage.

If you already have a credentials record that was configured in advance, select it from the drop -down list.
Otherwise, click Ad d and provide your access and secret keys, as described in section Access Keys for AWS
Users. You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

3. To specify how Veeam Backup & Replication will access the object storage repository, click Choose and in
the Connection mode window specify the following settings:

o Direct — select this option if you want Veeam Backup & Replication to use a proxy server to transfer
data from processed VM or file share to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide

o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositor ies. From
the Na me list, select gateway servers that you want to use for data transfer operations.

NOTE

The gateway server should have direct connection to AWS service endpoints. HTTP(S) proxy
servers are not supported. For more information, see Ports.

911 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

912 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify Amazon S3 bucket and folder that will be used to store data:

1. From the Bucket drop-down list, select a bucket.

Make sure that the bucket where you want to store your backup data was created in advance.

2. In the Folder field, select a cloud folder to which you want to map your object storage repository.

To select a folder, click Browse and either select an existing folder or create a new one by clicking New
Fold er.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

913 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Google Cloud Object Storage


For more information about Google Cloud object storage, see this Google article.

Before you add a Google Cloud object storage to the backup infrastructure, check prerequisites. After that, use
the New Ob ject Repository wizard.

914 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Google Cloud Storage.

915 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

916 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify Google Cloud credentials and connection settings that
Veeam Backup & Replication will use to transfer data to the object storage repository.

1. From the Credentials drop-down list, select user credentials to access your Google Cloud object storage.

If you already have a credentials record that was configured in advance, select it from the drop -down list.
Otherwise, click Add and provide your access and secret keys, as described in section Cloud Credentials
Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a credentials record.

The user account must have permissions listed in section Permissions.

2. Next to the Connection mode field, click Choose and specify how Veeam Backup & Replication will access
the object storage repository:

o Direct — select this option if you want Veeam Backup & Replication to use a proxy server to transfer
data from processed VM or file share to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Agent necessary permissions. For more information on
how to configure permissions for Veeam Agent, see the Permissions section in the Veeam
Agent Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

917 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

918 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify the bucket and folder that will be used to store data:

1. From the Da ta center region drop-down list, select a region.

2. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

Note that you must create the bucket where you want to store your backup data beforehand.

3. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

5. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

919 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Object Storage Class Settings

At the Storage Class step of the wizards, specify a storage class that you want assign to data blocks that you
keep in Google Cloud object storage. For more information on Google Cloud object storage classes, see Google
Documentation.

• Select the Sta ndard option to assign the Standard storage class to data blocks. Use this option if you plan
to access your data frequently and store it for a short period of time.

• Select the Nea rline option to assign the Nearline storage class to data blocks. Use this option if you want
to access data rarely (for example, once in a month or less) and plan to store data minimum 30 days.

• Select the Cold line option to assign the Coldline storage class to data blocks. Use this option if you plan to
access data rarely (for example, once a quarter) and plan to store data minimum 90 days.

920 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations, and configure a helper appliance. The helper appliance is a temporary VM instance that
Veeam Backup & Replication deploys in Google Compute Engine to perform a health check of backup files and
apply retention to unstructured data backup files. For more information, see Health Check for Object Storage
Repositories and Helper Appliance in Unstructured Data Backup. After Veeam Backup & Replication completes
these operations, it removes the helper appliance from the Google Cloud object storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

Configuring Helper Appliance


To configure the helper appliance, at the Mount Server step, click Configure and in the Ad vanced Settings
window, specify the following settings:

1. From the Account drop-down list, select a credentials record to access your Google Cloud object
storage. Veeam Backup & Replication will use this credentials record to connect to Google Compute
Engine within Google Cloud Platform and create the helper appliance.

If you have not added the credentials record beforehand, click Ma nage cloud accounts or Ad d to add
the necessary service account. For more information, see Google Cloud Platform Service Account.

2. Next to the Helper appliance field, click Configure. In the Ap p liance Settings window, specify the
following settings:

a. From the Ma chine type drop-down list, select the machine type for the helper appliance. The
machine type affects the speed and the cost of the operations that the helper appliance applies
to backup files. For information on instance types, see Google Cloud documentation.

b. From the VP C drop-down list, select a VPC network where a helper appliance will be launched.
For more information on VPC networks, see Google Cloud documentation.

To be able to select the necessary VPC from the drop -down list, you must create it beforehand
as described in the Google Cloud documentation..

921 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. From the Sub net drop-down list, select a subnet where a helper appliance will reside. For more
information on subnets, see Google Cloud documentation.

To be able to select the subnet from the drop-down list, you must create it beforehand as
described in the Google Cloud documentation.

d. In the Red irector port field, specify the TCP port that Veeam Backup & Replication will use to
route requests between the helper appliance and backup infrastructure components.

922 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported backups.

923 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

924 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding IBM Cloud Object Storage


For more information about IBM Cloud object storage, see this IBM article.

Before you add an IBM Cloud object storage to the backup infrastructure, check prerequisites. After that, use
the New Ob ject Storage Repository wizard.

925 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > IBM Cloud Object Storage.

926 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

927 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. In the Service point field, specify a service point address of your IBM cloud object storage.

2. In the Reg ion field, specify a region.

3. From the Credentials drop-down list, select user credentials to access your IBM cloud object storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

4. To specify how Veeam Backup & Replication will access the object storage repository, click Choose and in
the Connection mode window specify the following settings:

o Direct — select this option if you want Veeam Backup & Replication to use a proxy server to transfer
data from processed VM or file share to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

928 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

929 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify the bucket and folder that will be used to store data:

1. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

Note that you must create the bucket where you want to store your backup data beforehand.

2. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

4. Select the Ma k e recent backups immutable for check box to prohibit deletion of blocks of data from object
storage. Specify the immutability period. For more information, see Immutability.

930 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations, and configure a helper appliance. The helper appliance is a temporary host that
Veeam Backup & Replication deploys on your IBM Cloud object storage to perform a health check of backup files
and apply retention to unstructured data backup files. For more information, see Health Check for Object
Storage Repositories and Helper Appliance in Unstructured Data Backup.. After Veeam Backup & Replication
completes these operations, it removes the helper appliance from the IBM Cloud object storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

5. To specify the helper appliance settings, click Configure. From the Ma naged server drop-down list,
select a server that you want to use as the helper appliance.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

931 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3.

932 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported b ackups.

933 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

934 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Microsoft Azure Blob Storage, Microsoft Azure Archive Storage and
Microsoft Azure Data Box
Before you add a Microsoft Azure Blob storage, Azure Archive storage or Azure Data Box to the backup
infrastructure, check prerequisites. After that, use the New Object Storage Repository wizard.

Adding Azure Blob Storage

This section describes how to add Microsoft Azure Blob storage to the backup infrastructure. For more
information about Microsoft Azure Blob storage, see Microsoft Docs.

To add Microsoft Azure Blob storage, use the New Object Storage Repository wizard.

935 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Microsoft Azure Storage > Azure Blob
Storage.

936 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

937 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. From the Credentials drop-down list, select user credentials to access your Azure Blob storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, add the credentials record using either your account name and a shared key or
specify Microsoft Azure Entra ID storage account. You can also click the Ma nage cloud accounts link to
add, edit or remove a credentials record.

IMP ORTANT

Keep in mind that in case you add a new Microsoft Azure Entra ID storage account, it takes from 30
to 60 seconds to propagate it on the Microsoft Azure side.

2. From the Reg ion drop-down list, select an Azure region.

IMP ORTANT

Veeam Backup & Replication does not support Azure Germany since Microsoft closed Microsoft Cloud
Deutschland.

3. Next to the Connection mode field, click Choose and specify how a VMware backup proxy will transfer
data to the object storage repository:

o Direct — select this option if you want a backup proxy to transfer data from the processed machines or
file shares directly to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Access permissions are granted to Veeam Agents using shared access signatures (SAS).
For more information on how Veeam Agent works in direct connection with object
storage repositories, see the Access Permissions section in the Veeam Agent
Management Guide.

938 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to ob ject storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

939 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Container step of the wizard, specify the container, the folder that will be used to store data and select
an access tier in which Veeam Backup & Replication will keep blobs. For more information on access tiers, see
Microsoft Docs.

1. From the Container drop-down list, select a container.

Make sure that the container where you want to store your backup data was created in advance.

NOTE

The default Root container is not supported. For more information about this container, see
Microsoft Docs.

2. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

4. Select the Ma k e recent backups immutable for check box to prohibit deletion of blocks of data from object
storage. Specify the immutability period. For more information, see Immutability.

Note that the maximum immutability period you can set in the Veeam Backup & Replication UI is 90 days.
If you want to set immutability to a longer period, use the Set-VBRAzureBlobRepository cmdlet.

5. If you plan to access your backup data infrequently, select the Use Cool Tier (may result in higher cost)
check box. Veeam Backup & Replication will keep blobs in cool access tier.

IMP ORTANT

Consider the following:

• If you do not use this option, Veeam Backup & Replication will use the access tier that you
have set up for the storage account.
• If you enable this option and plan to use this object storage as a performance or capacity tier,
do not target to this repository any jobs that constantly send backup data to this storage:
scheduled regular backup and backup copy jobs that run without GFS, jobs with transactions
logs enabled, jobs created by Veeam Enterprise Plug-ins. Otherwise, it will result in higher
costs.

940 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
941 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations, and configure a helper appliance. The helper appliance is a temporary host that
Veeam Backup & Replication deploys on your Microsoft Azure Blob storage to perform a health check of backup
files and apply retention to unstructured data backup files. For more information, see Health Check for Object
Storage Repositories and Helper Appliance in Unstructured Data Backup. After Veeam Backup & Replication
completes these operations, it removes the helper appliance from the Microsoft Azure Blob storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

Configuring Helper Appliance


To configure the helper appliance, at the Mount Server step, click Configure and in the Helper Appliance
Settings window, specify the following settings:

1. From the Sub scription drop-down list, select your Microsoft Azure subscription credentials.

If you have not set up credentials beforehand, click Ad d . You will be prompted to the Specify
Microsoft Azure Compute Account Name wizard. Follow the wizard to add your account. Before
adding your Microsoft Azure account, check the prerequisites.

2. From the Size drop-down list, select the size of the helper appliance.

3. From the Resource group drop-down list, select a resource group that will be associated with the
helper appliance.

To be able to select the necessary resource group from the drop -down list, you must create it
beforehand as described in the Microsoft Docs.

4. From the Virtual network drop-down list, select a network to which the helper appliance must be
connected.

To be able to select the necessary network from the drop -down list, you must create it beforehand
as described in the Microsoft Docs.

942 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. From the Sub net drop-down list, select a subnet for the helper appliance.

To be able to select the necessary subnet from the drop-down list, you must create it beforehand as
described in the Microsoft Docs.

6. In the Red irector port field, specify the port that Veeam Backup & Replication will use to route
requests between the helper appliance and backup infrastructure components.

943 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported backups.

944 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

945 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Azure Archive Storage

This section describes how to add Microsoft Azure Archive Storage storage to the backup infrastructure. You can
only use this repository as an archive extent of the scale-out backup repository. For more information, see
Archive Tier. For more information about Azure Archive Storage, see Microsoft Docs.

To add Microsoft Azure Blob storage, use the New Object Storage Repository wizard.

946 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Microsoft Azure Storage > Azure Archive
Storage.

947 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

948 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. From the Credentials drop-down list, select user credentials to access your Azure Archive Storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and the credentials record using either your account name and a
shared key or specify Microsoft Azure Entra ID storage account. You can also click the Ma nage cloud
a ccounts link to add, edit or remove a credentials record.

The user account must have permissions listed in section Permissions.

IMP ORTANT

Consider the following:

• Keep in mind that in case you add a new Microsoft Azure Entra ID storage account, it takes
from 30 to 60 seconds to propagate it on the Microsoft Azure side.
• Veeam Backup & Replication archive tier feature does not support Microsoft Azure Stack Hub
Compute accounts.

2. From the Reg ion drop-down list, select the Azure region.

3. Next to the Connection mode field, click Choose and specify how a VMware backup proxy will transfer
data to the object storage repository:

o Direct — select this option if you want a backup proxy to transfer data from the processed machines or
file shares directly to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Access permissions are granted to Veeam Agents using shared access signatures (SAS).
For more information on how Veeam Agent works in direct connection with object
storage repositories, see the Access Permissions section in the Veeam Agent
Management Guide.

949 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure befor ehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

950 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Container step of the wizard, specify the container and folder that will be used to store data:

1. From the Container drop-down list, select a container.

Make sure that the container where you want to store your backup data was created in advance.

2. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

3. Select the Ma k e backups immutable for the entire d uration of their retention policy check box to prohibit
deletion of blocks of data from object storage. The immutability period will be equal to the retention
period (if any) of the data blocks. All the types of files that are eligible for archive storage can be made
immutable. For more information on the immutability feature and the retention policy for each file type,
see Immutability for Archive Tier.

951 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Access Tier Settings

At the Access Tier Settings step of the wizard, specify an Azure Storage access tier that will be assigned to
blocks in Azure Archive Storage. For more information on Azure Storage access tiers, see Microsoft Docs.

• Select the Archive option to assign the archive access tier to data blocks. Use this option if you plan to
access your data rarely and store it minimum 180 days.

• Select the Cold option to assign the cool access tier to data blocks. Use this option if you plan to access
your data frequently and store it minimum 30 days.

952 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Archiver Appliance

At the Archiver Appliance step of the wizard, you can specify archiver appliance settings. An archiver appliance
is an auxiliary instance that is necessary to transfer data from Azure Blob storage to Azure Archive Storage. For
more information, see the Archiver Appliance section.

To configure and set up an archiver appliance, you must add a Microsoft Azure account to
Veeam Backup & Replication. For that, do the following:

1. From the Sub scription drop-down list, select your Microsoft Azure subscription credentials. If you have
not set up credentials beforehand, click Ad d . You will be prompted to the Adding Microsoft Azure
Compute Accounts wizard. Follow the wizard to add your account. Before adding your Microsoft Azure
account, check the prerequisites.

2. You can use the default settings or customize the helper appliance. To specify helper appliance settings,
click Customize and in the Help er Appliance Settings window, specify the following settings:

a. From the Size drop-down list, select the size of the appliance. For details on the proxy types used by
Veeam Backup & Replication, see this Veeam KB article.

b. From the Resource group drop-down list, select a resource group that will be associated with the
proxy appliance.

c. From the Virtual network drop-down list, select a network to which the helper appliance must be
connected.

d. From the Sub net drop-down list, select the subnet for the proxy appliance.

e. In the Red irector port field, specify the port that Veeam Backup & Replication will use to route
requests between the proxy appliance and backup infrastructure components.

f. Click OK.

953 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Azure Data Box Storage

Azure Data Box is a physical device which you can request for a short period of time from Microsoft. You can
temporarily attach it to the backup infrastructure and use it as an object storage. For more information about
ordering Azure Data Box and preparing to use it, see Microsoft Docs.

This device may become useful when you need to offload a significant number of backup files occupying storage
space on your extents, as offloading data to the Azure Data Box device is much faster than transferring the same
amount of data directly to Azure object storage. Once you have offloaded backups to Azure Data Box, you need
to ship the device back to Microsoft for further data synchronization with your Azure storage account, as
described in section Seeding Backups to Azure Blob Storage.

General Considerations and Limitations


Consider the following:

• Veeam Backup & Replication supports only those Azure Data Box devices that are capable of reading and
writing data using REST API.

• The Azure Data Box disk type is not supported.

• Direct data copy to the archive tier from Azure Data Box is not supported. When you place your order, do
not enable Cop y to archive option on the Da ta destination step.

954 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• When you configure a scale-out backup repository with Azure Data Box as the capacity extent, it is
recommended to only use the copy policy. This way you keep copy of the data on your local storage which
helps you reduce the risk of data loss if the device is damaged during shipping. It will also ensure that the
backup data is available for restore operations while Azure Data Box is in shipment.

• You cannot offload immutable data to the Azure Data Box device.

• You can add only one Azure Data Box device to a scale-out backup repository.

For information about other limitations for Microsoft Azure Data Box storage, see Microsoft Docs.

To add Microsoft Azure Blob storage, use the New Object Storage Repository wizard.

Before You Begin


Before you add Microsoft Azure Data Box to the backup infrastructure, complete the following steps:

• Configure Name Resolutions

• Download and Install SSL Certificate

Configuring Name Resolutions


To resolve a DNS name of your Azure Data Box device, make sure to add the following DNS addresses to the
HOST file that is located on both the Veeam Backup & Replication server and the gateway server (if any
additional gateway server is used):

• <ip_address> <mydataboxno>.microsoftdatabox.com

• <ip_address> <storageaccountname>.blob.<mydataboxno>.microsoftdatabox.com

For more information on how to learn the values for <ip_address> , <mydataboxno> and <storageaccountname> ,
see Microsoft Docs.

As an <ip_address> , use any of the IP-addresses listed under the Da ta N section. You can also use the address
specified under the MGMT section, but due to its slow connection rate (limited to 1 GbE), using such an address
is not recommended.

955 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The following is an example of the HOST file.

NOTE

Consider the following:

• Make sure to configure name resolutions on each server that may be used as a gateway.
• Alternatively, you can create a microsoftdatabox.com DNS zone with corresponding records on your
DNS server if you prefer not to modify the HOST file.

Downloading and Installing SSL Certificate


To establish a secure connection to the Azure Data Box device, make sure to download and import an SSL
certificate and install it on both the Veeam Backup & Replication server and the gateway server (if any additional
gateway server is used).

For more information on how to download an SSL certificate, see Microsoft Docs.

When installing a certificate, do the following:

1. In the Certificate Import Wizard dialog, select Local Machine.

2. In the Certificate Store step, select P lace all certificates in the following store and click Browse.

956 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Select Trusted Root Certification Authorities.

Configuring registry settings


For information how to configure registry settings for Microsoft Azure Data Box device, see this Veeam KB
article.

Sizing Gateway Server


Consider that Veeam Backup & Replication supports Azure Data Box devices that are capable of reading/writing
data using REST API only; the Azure Data Box Disk type is not supported.

As with any other object storage, REST API performance depends on scale. As Azure Data Box is a single
endpoint, the individual throughput of this REST API may be limited. The block size used in
Veeam Backup & Replication capacity tier for object storage offload matches that of the source job. The default
object size will be a compressed 1 MB block, resulting in objects of around 512 KB in size.

The speed of data offload to Azure Data Box devices may reach about 300 MB/s. To achieve this speed, we
recommend using a separate gateway server with 8 CPU cores.

957 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > Microsoft Azure Storage > Azure Data Box.

958 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

TIP

Set the maximum number of concurrent task to a reasonable number to avoid overloading if you plan to
upload significant amount of backup chains to the device.

959 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. In the Service endpoint field, specify a service endpoint address of your Azure Data Box device.

2. From the Credentials drop-down list, select user credentials to access your Azure Data Box storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

For more information on where to find connection parameters of your Azure Data Box device, see Getting
Data Box Connection Parameters.

3. Next to the Connection mode field, click Choose and specify how a VMware backup proxy will transfer
data to the object storage repository:

o Direct — select this option if you want a backup proxy to transfer data from the processed machines or
file shares directly to object storage repositories.

NOTE

Consider the following:

• Make sure that the backup proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.

960 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand.
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

Getting Data Box Connection Parameters


To find connection parameters of your Azure Data Box device, do the following:

1. Open the Microsoft Azure Data Box portal.

2. In the navigation pane, click Connect and Copy.

3. Under the Access Settings column of the storage account that you want to use, click RE ST and in the
Access storage a ccount and upload data dialog, copy the following:

a. Under Storage Account Name, copy the Azure storage account name.

b. Under Key , copy the storage account key.

961 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. Under Blob Service Endpoint, copy the service endpoint address that starts exactly after the blob
word.

For example, if the complete service endpoint address is


https://qadataboxstoracc03.blob.ZTS18510049.microsoftdatabox.com , then you will need to copy
everything that starts from ZTS only. That is, ZTS18510049.microsoftdatabox.com . Make sure not to
copy the last slash ("/") symbol.

962 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Container step of the wizard, specify the container and folder that will be used to store data:

1. From the Container drop-down list, select a container.

To create a container, use Microsoft Azure Storage Explorer. For more information on how to connect to
the Azure Data Box device using Microsoft Azure Storage Explorer, see Microsoft Docs.

2. In the Select Folder field, select a cloud folder to which you want to map your object storage repository.

To select a folder, click Browse and either select an existing folder or create a new one by clicking New
Fold er.

963 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Adding Wasabi Cloud Object Storage


This section describes how to add Wasabi Cloud object storage to the backup infrastructure. For more
information about Wasabi Cloud object storage, see this Wasabi article.

Before you add a Wasabi Cloud object storage to the backup infrastructure, check prerequisites. After that, use
the New Ob ject Repository wizard.

964 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Repository Wizard

To launch the New Object Storage Repository wizard, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Repositories node and select Ad d Backup Repository.
Alternatively, you can click Ad d Repository on the ribbon.

3. In the Ad d Backup Repository window, select Ob ject storage > W asabi Cloud Storage.

965 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Object Storage Name

At the Na me step of the wizard, use the Na me and Description fields to enter a name for a new object storage
repository and to provide a description for future reference.

If you want to limit the maximum number of tasks that can be processed at once, select the Limit concurrent
ta sks to N check box.

966 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Account

At the Account step of the wizard, specify the connection settings:

1. In the Reg ion field, the region is specified by default.

2. From the Credentials drop-down list, select user credentials to access your Wasabi cloud object storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

3. Next to the Connection mode field, click Choose and specify how a VMware backup proxy will transfer
data to the object storage repository:

o Direct — select this option if you want a backup proxy to transfer data from the processed machines or
file shares directly to object storage repositories.

NOTE

Consider the following:

• Make sure that the proxy server that you plan to use, meets the following System
Requirements.
• You must locate your proxy server as close as possible to the backup source host.
• Veeam Agent transfers data to the object storage repositories without a proxy server.
Make sure that you grant Veeam Backup & Replication and Veeam Agent necessary
permissions. For more information on how to configure permissions within
Veeam Backup & Replication, see Access Permissions. For more information on how to
configure permissions for Veeam Agent, see the Permissions section in the Veeam Agent
Management Guide. For more information on how Veeam Agent works in direct
connection with object storage repositories, see the Access Permissions section in the
Veeam Agent Management Guide.

967 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Through gateway server — select this option if you want Veeam Backup & Replication to use gateway
servers to transfer data from processed machines or file shares to object storage repositories. From
the Na me list, select gateway servers that you want to use for data transfer operations.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. You
can choose any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. Note that you must add the server to the backup infrastructure beforehand .
Before you add the server, check the following Considerations and Limitations. For more information
on how to add a server, see Virtualization Servers and Hosts.

968 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Object Storage Settings

At the Buck et step of the wizard, specify the bucket and folder that will be used to store data:

1. In the Buck et field, enter a name of the bucket or click Browse to get the necessary bucket.

Note that you must create the bucket where you want to store your backup data beforehand.

2. In the Folder field, enter a cloud folder name to which you want to map your object storage repository.
Alternatively, click Browse and either select an existing folder or click New Folder.

3. Select the Limit object storage consumption to check box to define a soft limit that can be exceeded
temporarily for your object storage consumption. Provide the value in TB or PB.

4. Select the Ma k e recent backups immutable for check box to prohibit deletion of blocks of data from object
storage. Specify the immutability period. For more information, see Immutability.

969 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Mount Server Settings

At the Mount Server step of the wizard, specify settings for the mount server that you plan to use for restore
operations, and configure a helper appliance. The helper appliance is a temporary host that
Veeam Backup & Replication deploys on your Wasabi Cloud object storage storage to perform a health check of
backup files and apply retention to unstructured data backup files. For more information, see Health Check for
Object Storage Repositories and Helper Appliance in Unstructured Data Backup. After
Veeam Backup & Replication completes these operations, it removes the helper appliance from the Wasabi
Cloud object storage storage.

IMP ORTANT

Consider the following:

• If you do not configure a helper appliance, Veeam Backup & Replication will use local resources to
perform the health check and apply retention to NAS backup files. It will consume more cloud
resources and can result in additional costs.
• To perform the health check, you must enable this option when you configure a backup job. For
more information, see Health Check for Backup Files.

Specifying Mount Server Settings


To specify the mount server settings, do the following:

1. From the Mount Server drop-down list, select a server that you want to use as a mount server.
Veeam Backup & Replication uses this server during restore operations to mount VM disks directly from
objects located in object storage repositories. For more information, see Mount Server.

The Mount Server list contains only Microsoft Windows servers that are added to the backup
infrastructure. If the server is not added to the backup infrastructure yet, click Ad d New on the right to
open the New W indows Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Instant recovery write cache folder field, specify a folder to keep cache that is created during mount
operations.

5. To specify the helper appliance settings, click Configure. From the Ma naged server drop-down list,
select a server that you want to use as the helper appliance.

IMP ORTANT

vPower NFS settings are not applicable in Microsoft Hyper-V environments.

970 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3.

971 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Review Components

At the Review step of the wizard, review what components will be processed on the mount server server and
their status.

If the backup repository contains backups, select the Sea rch the repository for existing backups and import
them automatically check box. Veeam Backup & Replication will scan the backup repository to detect existing
backup files and display them in the Veeam Backup & Replication console under the Ba ckups > Ob ject Storage
( Imported) node.

If the backup repository contains guest file system index files, select the Imp ort guest file system index data to
the catalog check box. Veeam Backup & Replication will import index files together with backup files, and you
will be able to search for guest OS files inside imported backups.

972 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Apply Settings

At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to complete saving your settings to the
configuration database and create backup infrastructure objects.

973 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard

At the Summary step of the wizard, review details of the newly created object storage repository and click
Finish.

Working with Veeam Smart Object Storage API (SOSAPI)


Veeam Backup & Replication offers Veeam Smart Object Storage application programming interface (SOSAPI)
functionality to interact with S3 compatible object storage repositories. Object storage vendors can leverage
SOSAPI to decrease impact on the production environment, significantly improve recovery point objective (RPO)
and optimize the interaction between object storage and Veeam Backup & Replication. SOSAPI relies on Amazon
S3 API protocol, uses its authorization mechanisms and existing S3 API calls. This approach does not require to
set up a complex network infrastructure - there is no need to create additional ports, firewall rules or install any
plug-ins. Instead, vendors need to handle the API requests to interact with S3 compatible object storage
repositories.

Among others, SOSAPI functionality suggests taking advantage of the following options:

• Ca pacity reports
Veeam Backup & Replication sends a warning if space capacity of an object storage repository reaches its
limits. Also, you can check the amount of free space available in the object storage repository using
Veeam Backup & Replication UI. For more information, see Editing Settings of Backup Repositories.

• E nha nced scale-out backup repository placement policy


In case you use multiple extents within the scale-out backup repository, Veeam Backup & Replication will
select the best extent to keep the evenly.

• Loa d balancing on smart entity level

A vendor can implement internal load balancing for SOSAPI-enabled repositories.

974 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
This option allows to define that Veeam Backup & Replication will be able to perform read and write task
with the necessary repositories using a set of vendor-defined IP addresses instead of only one endpoint
address.

NOTE

Load balancing is not supported for one type of tier (performance tier or capacity tier) if a scale -out
backup repository contains more than one SOSAPI-enabled object storage repository within this tier.

Working with SOSAPI


To start working with SOSAPI, vendors must add to their object storage infrastructure a set of XML
configuration files. Veeam Backup & Replication will automatically enable SOSAPI functionality supported by
the vendor and provide corresponding capabilities to customers. After you add the S3 compatible ob ject storage
repositories with SOSAPI functionality to the backup infrastructure, it will show up as the S3-integrated type in
working area.

Managing Object Storage Repositories


You can manage your object storage repositories in various ways: edit settings of an object storage repository,
switch it to the maintenance or the Sealed mode or remove an object storage repository.

Editing Settings of Object Storage Repository


After you have added an object storage repository, you may want to edit its settings.

To edit object storage settings, do the following:

1. Open the Ba ckup Infrastructure view.

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

975 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select an object storage repository and click E d it Repository on the ribbon or right-
click an object storage repository and select P roperties.

4. Follow the steps of the E d it Object Storage Repository wizard and edit settings as required.

Note that some settings cannot be modified and will remain disabled while being edited.

Removing Object Storage Repository


You can remove any object storage repository from the application scope if you no longer need it.

Consider the following:

• An object storage repository cannot be removed if it is part of a scale-out backup repository.


To remove such a repository, you must first exclude an object storage repository from the scale -out
backup repository configuration. For more information, see Removing Performance Extents from Scale-
Out Repositories and Excluding Capacity Tier from Scale-Out Repositories.

• An object storage repository cannot be removed if backups located in this repository was imported, as
described in section Importing Backups.

To remove such a repository, you must first detach object storage, as described in section Detaching
Object Storage.

• When an object storage repository is being removed from the environment, the data remains completely
unaffected.

To learn how to remove data, see Removing Backups from Object Storage Repository.

To remove an object storage repository, do the following:

1. Open the Ba ckup Infrastructure view.

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

976 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select an object storage repository and click Remove Repository on the ribbon or
right-click an object storage repository and select Remove.

Managing Object Storage Backups


You can manage your object storage backups in various ways: import, detach or remove object storage backups
or seed them to Azure Data Box or AWS Snowball Edge storage devices.

Importing Object Storage Backups


In case a disaster strikes and your Veeam Backup & Replication with a scale-out backup repository becomes
unavailable, you can import into another Veeam Backup & Replication infrastructure backups located in object
storage repositories added as performance, capacity or archive extents of the scale -out backup repository. Once
you add the necessary object storage repositories in Veeam Backup & Replication infrastructure, you can import
backups and they will become available for data recovery operations.

NOTE

You do not need to import backups located in performance extents and standalone object storage
repositories.

Consider the following:

• The Import Backups option is available only if the object storage is not a part of the scale -out backup
repository.

• Before you start importing backups, make sure to add the object storage repository that stores data you
want to import.

• If you have imported backups from the object storage repository, you will not be able to select this
repository as a capacity extent at the Add Capacity Tier and as an archive extent at the Add Archive Tier
steps.

• The Import Backups option is applicable only to the Capacity Tier backups and Archive Tier backups. It
does not support the unstructured data backups.

977 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To import backups, do the following:

1. Launch the Import wizard.

2. Specify password.

3. Wait for import.

4. Finish working with the wizard.

978 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Import Wizard

To launch the Imp ort Backup wizard, open the Ba ckup Infrastructure view and in the inventory pane select the
Ba ckup Repositories node. In the preview pane, select necessary object storage and select Imp ort Backups.
Alternatively, right-click necessary object storage and select Imp ort backups.

979 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Password

This step is only available when importing encrypted backups.

At the P a ssword step of the wizard, in the P a ssword field, specify the password that was used to encrypt data
during offload or copy sessions.

980 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Wait for Import

At the Imp ort step of the wizard, wait until Veeam Backup & Replication prepares a temporary database to
which information about backups will be added upon import.

981 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Finish Working with Wizard

At the Summary step of the wizard:

1. Review details of the import operation.

2. Click Finish to run a Configuration Database Resynchronize session.

During this session, all existing backups will be imported into the Veeam Backup & Replication console.

Viewing Imported Backups


To view imported backups, do the following:

1. Open the Home view.

2. In the navigation pane, select the Ba ckups > Capacity Tier (Imported) or Archive Tier (Imported) node.

982 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the preview pane, review imported backups.

Detaching Object Storage Backups


You can detach imported object storage after you have finished working with it. After object storage is
detached, the imported backups become unavailable.

To detach imported object storage, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the navigation pane, select the Ba ckup Repositories node.

983 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the preview pane, select object storage the backups of which have been imported and click Detach
Rep ository on the toolbar or right-click object storage and select Detach Repository.

Seeding Backups to Azure Blob Storage


Seeding backups is an operation which can help in case you would like to keep backups in object storage
repositories and need to transfer backups in bulk to object storage. In this case, you can utilize the capabilities
of the Azure Data Box device that will help you to transfer data from the local backup repository to Azure Blob
storage and synchronize with the storage. Azure Data Box is a physical storage device that emulates a cloud
storage endpoint and serves as an intermediate between the local backup repository and Azure Blob storage.
With the help of Azure Data Box you will not need to create a full backup file and transfer it through the
network which might result in the . Instead, you will transport all necessary data using Azure Data Box .

To seed data to Azure Blob storage, you need to order Azure Data Box from Microsoft, connect to it, copy
backups from the local repository and ship it back to Microsoft. After the backup data is uploaded to your Azure
Blob storage, you can perform initial sync and store your backups in Azure Blob storage later on.

For more information on ordering Azure Data Box, see Azure Storage Documentation.

NOTE

Before you seed backups to Azure Blob Storage, make sure to review considerations and limitations.

To seed backups to Azure Blob Storage do the following:

1. Set up Azure Data Box.

2. Add Azure Data Box to the backup infrastructure and then offload the data .

3. Prepare Azure Data Box for shipping.

4. Synchronize the seeded data.

984 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Setting up Azure Data Box
Before you add Azure Data Box to Veeam Backup & Replication, you need to set up the storage:

1. Install Azure Data Box. For more information, see Azure Storage Documentation.

2. Connect to Azure Data Box through REST APIs. For more information, see Azure Storage Documentation.

After you perform the steps in the Azure Storage Documentation, you will have a storage account name,
access key, and blob service endpoint that you can use to addAzure Data Box to the backup infrastructure.

Adding Azure Data Box and Offloading the Data


To offload backups to Azure Data Box, do the following:

1. Add Azure Data Box as an Azure Data Box storage.

2. Add Azure Data Box storage as a standalone object storage repository, the capacity tier or performance
tier in a scale-out backup repository.

IMP ORTANT

When you configure a scale-out backup repository with Azure Blob storage as the capacity extent,
make sure to select the Cop y backups to object storage as soon as they are created check box as
described in section Add Capacity Tier. In this case, you will keep copy of the data on your local
storage which will help you to reduce the risk of data loss if the device is damaged during shipping. It
will also ensure that the backup data is available for restore operations while Azure Blob storage is in
shipment.

If you use the other type of backup repository, make sure to keep a copy of your backup in your local
storage.

3. Press and hold the [Ctrl] key, right-click the scale-out backup repository from the previous step and select
Run tiering job now.

Preparing Azure Data Box for Shipping


After you have completed moving backup data to the Azure Data Box, you need to ship this device back to
Microsoft so that this data can be synchronized with your Azure storage account.

Before shipping Azure Data Box back to Microsoft, do the following:

1. Put an object storage repository that is associated with Azure Data Box into the Maintenance mode, as
described in section Switching to Maintenance Mode.

2. Perform the steps described in Microsoft Docs.

After shipping the device, wait for Microsoft to receive it and copy your data into your Azure storage account.
You will be notified of successful data upload to your Azure storage account.

Synchronizing the Seeded Data


To connect Veeam Backup & Replication to your Azure storage account, do the following:

1. Add an Azure Blob storage, as described in section Adding Azure Blob Storage.

985 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Edit settings of the object storage repository or scale-out backup repository used for offloading the data,
and change your Azure Data Box object storage to the Azure Blob storage that you have created in the
previous step.

3. Enable importing backups from Azure Blob storage and wait for the synchronization to complete.

4. Remove Azure Data Box object storage from the backup infrastructure, as described in section Removing
Object Storage Repository.

NOTE

Keep in mind that if you delete individual VMs from your backup in the period between mailing Azure Data
Box and adding Azure Blob Storage, you may need to run Active Full instead of Incremental job after the
final Azure synchronization. To avoid this, do not delete any VMs manually and disabl e the Retention Policy
for Deleted Items option in the job settings for that period. After successful synchronization, you can re -
enable this option and work as usual.

Seeding Backups to Amazon S3 Storage


Seeding backups is an operation which can be helpful in case you would like to start using object storage
repositories and need to transfer a bulk amount of data to object storage. In this case, you can utilize the
capabilities of the AWS Snowball Edge device that will help you to transfer data from the l ocal backup
repository to Amazon S3 storage and synchronize with the storage. AWS Snowball Edge is a physical storage
device that emulates a cloud storage endpoint and serves as an intermediate between the local backup
repository and Amazon S3 storage. With the help of AWS Snowball Edge you will not need to create a full
backup file and transfer it through the internet which can result in high load on the network. Instead you will
transport all necessary data using AWS Snowball Edge.

To seed data to Amazon S3 storage, you need to order AWS Snowball Edge from AWS, connect to it, copy
backups from the local repository and ship it back to AWS. After the backup data is uploaded to your Amazon S3
storage, you can perform initial sync and store your backups in Amazon S3 storage later on.

For more information on AWS Snowball Edge, see AWS Documentation.

NOTE

Before you seed backups to AWS Snowball Edge, make sure to review considerations and limitations.

To seed backups to AWS Snowball Edge do the following:

1. Set up AWS Snowball Edge.

2. Add AWS Snowball Edge to the backup infrastructure and then offload the data .

3. Prepare AWS Snowball Edge for shipping.

4. Synchronize the seeded data.

Setting up AWS Snowball Edge Device


Before you add AWS Snowball Edge to Veeam Backup & Replication, you need to order the device, connect it to
your local network, download and install the Snowball edge client and configure the device. For detailed
instructions on these steps, see AWS Documentation.

After that, you will have a service point address, access key and a secret key that you can use to add AWS
Snowball Edge to the backup infrastructure.

986 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding AWS Snowball Edge and Offloading the Data
To offload backups to AWS Snowball Edge, do the following:

1. Add AWS Snowball Edge as AWS Snowball Edge Storage.

2. Add AWS Snowball Edge as a standalone object storage repository, the capacity tier or performance tier in
a scale-out backup repository.

IMP ORTANT

When you configure a scale-out backup repository with AWS Snowball Edge as the capacity extent,
make sure to select the Cop y backups to object storage as soon as they are created check box as
described in section Add Capacity Tier. In this case, you will keep copy of the data on your local
storage which will help you to reduce the risk of data loss if the device is damaged during shipping. It
will also ensure that the backup data is available for restore operations while AWS Snowball Edge is
in shipment.

If you use the other type of backup repository, make sure to keep a copy of your backup in your local
storage.

3. Press and hold the [Ctrl] key, right-click the scale-out backup repository from the previous step and select
Run tiering job now.

Preparing AWS Snowball Edge for Shipping


After you have completed moving backup data to the AWS Snowball Edge device, you need to ship this device
back to Amazon so that this data can be synchronized with your Amazon S3 storag e.

Before shipping AWS Snowball Edge back to AWS, do the following:

1. Put an object storage repository that is associated with AWS Snowball Edge into the Maintenance mode,
as described in section Switching to Maintenance Mode.

2. Power off AWS Snowball Edge. For more information, see AWS Documentation.

3. Ship AWS Snowball Edge back to AWS. For more information, see AWS Documentation.

After mailing the device, wait until it is accepted by AWS and notification of successful data upload to your
storage account is received (if you subscribed for such notification).

Synchronizing the Seeded Data


To connect Veeam Backup & Replication to your Amazon S3 storage account, do the following:

1. Add an Amazon S3 storage, as described in section Adding Amazon S3 Storage. At the Specify Object
Storage Settings step, select the same bucket and folder that you have selected for your AWS Snowball
Edge device.

2. Edit settings of the object storage repository or scale-out backup repository used for offloading the data,
and change your AWS Snowball Edge object storage to the Amazon S3 storage that you have created in
the previous step.

3. Enable importing backups from Amazon S3 storage and wait for the synchronization to complete.

4. Remove the AWS Snowball Edge object storage from the backup infrastructure, as described in section
Removing Object Storage Repository.

987 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Make sure that Versioning and Object Lock are not enabled on the used S3 bucket.

988 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Backup Repositories
You can manage your backup repositories and data stored in them in various ways: edit settings of the backup
repositories, set up access permissions, rescan backup repositories or remove backup repositories.

In This Section
• Editing Settings of Backup Repositories

• Access Permissions

• Rescanning Backup Repositories

• Removing Backup Repositories

• Fast Clone

Editing Settings of Backup Repositories


You can edit settings of backup repositories that you have added to the backup infrastructure.

NOTE

When editing backup repository settings, you cannot change the selected repository server. Therefore, the
Rep ository server field at the Server step is grayed out.

TIP

The following column headers show information on the repository storage settings:

• The Ca pacity column header — specifies a full size of a storage location where you keep your
backups.
• The Free column header — specifies the amount of free space on a storage location. It considers a
size of all data that is already added to this storage location without using
Veeam Backup & Replication. For example, if the storage location capacity is 100 GB, and you added
to this location data that occupies 50 GB, the Free column header will display 50 GB.
• The Used Space column header — specifies the amount of space occupied by backups created by
Veeam Backup & Replication. Note that it does not consider data compression and deduplication
that is not performed by means of Veeam Backup & Replication. For example, if
Veeam Backup & Replication creates a backup that occupies 10 GB, and a size of this backup
decreases to 9 GB after compression or deduplication performed by a storage appliance, the Used
Space column header will display 10 GB.
• The Membership column header — specifies a scale-out backup repository to which repositories are
added as performance extents. This column is hidden by default. To display it, right-click any
column header and select Membership from the drop-down menu.

To edit settings of a backup repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the Ba ckup Repositories node.

3. In the working area, select the backup repository and click E d it Repository on the ribbon or right-click the
backup repository and select P roperties.

989 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Edit the backup repository settings as required. Note that you cannot change the selected repository
server and path to the folder used for storing backups.

Access Permissions
If you want to store in the backup repository backups of virtual and physical machines created by
Veeam Backup & Replication additional solutions, for example, Veeam Agent for Microsoft Windows, Veeam
Agent for Linux, Veeam Plug-ins for Enterprise Applications and so on, you must set up access permissions to
backup repositories.

Access permissions are granted to security principals such as users and AD groups by the backup administrator
who works with Veeam Backup & Replication. Users with granted access permissions can target backup jobs
created by additional solutions at this backup repository and perform restore from backups located in this
backup repository.

NOTE

If you plan to create backups in a Veeam backup repository with Veeam Agent backup jobs configured in
Veeam Backup & Replication, you do not need to grant access permissions on the backup repository to
users. In the Veeam Agent management scenario, to establish a connection between the ba ckup server and
protected computers, Veeam Backup & Replication uses a TLS certificate. To learn more, see the
Configuring Security Settings section in the Veeam Agent Management Guide.

If you plan to create backups in a Veeam backup repository with Veeam Backup for Nutanix AHV, you do
not need to grant access permissions when configuring repositories, you must do that when configuring
Nutanix AHV backup appliances.

Right after installation, access permissions on the default backup repository are set to Allow to everyone for
testing and evaluation purposes. If necessary, you can change these settings.

After you create a new backup repository, access permissions on this repository are set to Deny to everyone . To
allow users to store backups in the backup repository, you must grant users with access permissions to this
repository.

990 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Permissions of Backup Repositories
To grant access permissions to a security principal:

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

2. In the inventory pane, click one of the following nodes:

o The Ba ckup Repositories node — if you want to grant access permissions on a regular backup
repository.

o The Sca le-out Repositories node — if you want to grant access permissions on a scale-out backup
repository.

3. In the working area, select the necessary backup repository and click Set Access Permissions on the ribbon
or right-click the backup repository and select Access permissions. If you do not see the Set Access
P ermissions button on the ribbon or the Access permissions command is not available in the shortcut
menu, press and hold the [Ctrl] key, right-click the backup repository and select Access permissions.

4. In the Sta ndalone applications window, specify to whom you want to grant access permissions on this
backup repository:

o Allow to everyone — select this option if you want all users to be able to store backups in this backup
repository. Setting access permissions to Everyone is equal to granting access rights to the Everyone
Microsoft Windows group ( Anonymous users are excluded). Note, however, this scenario is
recommended for demo environments only.

o Allow to the following accounts or groups only — select this option if you want only specific users to
be able to store backups in this backup repository. Click Ad d to add the necessary users and groups to
the list.

5. [For Veeam Backup for Nutanix AHV and Veeam Agents operating in the standalone mode ] To encrypt
backup files, select the E ncrypt backups stored in this repository check box and choose the necessary
password from the field below. If you have not specified a password beforehand, click Ad d on the right or
the Ma nage passwords link to add a new password.

991 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you want to encrypt backup files created by Veeam Agents operating in the managed mode, you
must configure encryption in the backup job settings. For example, to learn how to encrypt backup
files created by managed Veeam Agent for Microsoft Windows, see the Storage Settings section in
the Veeam Agent Management Guide.

Veeam Backup & Replication encrypts files at the backup repository side using its built-in encryption
mechanism in the following way:

Ba ckup Repository Rep ository-level Encryption

Microsoft Windows/Linux-based repository If you select the E ncrypt backups stored in this
rep ository check box, backup data will be
encrypted after being uploaded to the backup
NFS file share repository.

SMB (CIFS) file share

NAS file share

External repository

Object storage repository

Object storage repository added as Performance


or Archive Tier

Object storage repository added as Capacity Tier If you use capacity tier encryption and select the
E ncrypt backups stored in this repository check
box, already encrypted backup data will be
encrypted again before being uploaded to the
capacity tier.

Deduplicating storage appliance If you use deduplicating storage appliance


encryption and select the E ncrypt backups stored
in this repository check box, backup data will be
encrypted twice: after being uploaded to the
deduplicating storage appliance and again by the
deduplicating storage appliance itself.

Note that data encryption has a negative effect on


the deduplication ratio. If you want to achieve a
higher deduplication ratio, use only deduplicating
storage appliance encryption. For more details,
see Data Encryption and Deduplication.

992 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Permissions for S3 Compatible Object Storage
If you plan to use S3 compatible object storage as an object storage repository, you must set up access
permissions to the object storage. These permissions are used if you keep in object storage repositories backups
created by Veeam Agent or by Veeam Cloud Connect tenant. For more information, see Backup to Object
Storage in the Veeam Agent Management Guide and Backup to Object Storage in the Veeam Cloud Connect
Guide.

To manage permissions for S3 compatible object storage, perform the following:

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

2. In the inventory pane, click the Ba ckup Repositories node.

3. In the working area, select the necessary S3 compatible backup repository and click Set Access
P ermissions on the ribbon or right-click the backup repository and select Access permissions. If you do not
see the Set Access P ermissions button on the ribbon or the Access p ermissions command is not available
in the shortcut menu, press and hold the [Ctrl] key, right-click the backup repository and select Access
p ermissions.

4. On the Security tab, specify how Veeam Agent or a SP will access an S3 compatible object storage
repository:

o Ag ents share credentials to object storage repository — use this option if you want directly access the
S3 compatible object storage repository. In this case, Veeam Agent will use credentials that you
specified when added the S3 compatible object storage repository to the backup infrastructure.

993 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

This option is not secure since Veeam Backup & Replication will have access permissions on the
bucket where you keep your folders with backups.

o P rovided by the backup server — use this option if you want to access the S3 compatible object
storage repository through a gateway server.

o P rovided by IAM/STS object storage capabilities — use this option if you want directly access the S3
compatible object storage repository. In this case, Veeam Backup & Replication will create service
tokens that Veeam Agent or a SP will use to access the S3 compatible object storage repository.

To specify credentials, do the following:

i. In the Id entity and access management (IAM) endpoint field, specify the endpoint of your S3
compatible object storage repository.

ii. In the Security token service (STS) endpoint field, specify the security token.

Rescanning Backup Repositories


You can rescan a backup repository configured in the backup infrastructure. Backup repository rescan may be
required, for example, if you have archived backups from a backup repository to tape and deleted backup files in
the backup repository. Or you have copied backups to the backup repository manually and want to work with
them in Veeam Backup & Replication.

994 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
During the rescan operation, Veeam Backup & Replication gathers information about backups that are currently
available in the backup repository and updates the list of backups in the configuration database. After the
rescan operation, backups that were not in this configuration database will be shown on the Home view in the
Ba ckups > Disk (Imported) node. If backups are encrypted, they will be shown in the Ba ckups > Disk (Encrypted)
node.

IMP ORTANT

Consider the following:

• It is recommended that you stop or disable all jobs before performing the
rescan.Veeam Backup & Replication skips from scanning backups created by active jobs.
• Veeam Backup & Replication will not be able to import backups automatically while performing a
rescan if VBM files are not available. In this case you will have to import backups manually using the
VBK files. For more information, see Importing Backups Manually.

To rescan a backup repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the Ba ckup Repositories node.

3. In the working area, select the backup repository and click Rescan Repository on the ribbon or right-click
the backup repository and select Rescan repository.

TIP

By default, Veeam Backup & Replication skips from rescan files whose paths contain $RECYCLE.BIN or
.Trash-<digits> . You can exclude other file paths with a registry value. For more information, contact
Veeam Customer Support.

Removing Backup Repositories


You can permanently remove a backup repository from the backup infrastructure. When you remove a backup
repository, Veeam Backup & Replication unassigns the backup repository role from the server and this server is
no longer used as a backup repository. The actual server remains in the backup infrastructure.

995 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication does not remove backup files and other data stored in the backup repository. You
can re-connect the backup repository at any time and import backups from this backup repository to
Veeam Backup & Replication.

You cannot remove a backup repository that is used by any job. To remove such backup repository, you first
need to delete a reference to this backup repository in the job settings.

To remove a backup repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the Ba ckup Repositories node.

3. In the working area, select the backup repository and click Remove Repository on the ribbon or right-click
the backup repository and select Remove.

Fast Clone
Fast Clone is the Veeam Backup & Replication technology that helps create quick file copies. Fast Clone
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 & Replication references existing data blocks on volumes instead of
copying data blocks between files. Data blocks are copied only when files are modified.

Veeam Backup & Replication supports Fast Clone for the following types of backup repositories:

• Linux server

• Microsoft Windows server

• SMB share

• ExaGrid

• Quantum DXi

• Fujitsu ETERNUS CS800

• Infinidat InfiniGuard

996 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Depending on the repository type, Fast Clone uses different technologies and has different requirements and
limitations. For more information, see Fast Clone for Deduplicating Storage Appliances, Fast Clone for Linux
Repositories and Fast Clone for Microsoft Windows and SMB Repositories.

Fast Clone requires that the starting and ending file offsets are aligned to cluster boundaries. For this reason,
Veeam Backup & Replication automatically enables the Alig n backup file data blocks option for backup
repositories that support Fast Clone.

Veeam Backup & Replication uses Fast Clone for the following operations:

• In b a ckup jobs: to merge backup files, create synthetic full backups (including GFS backups), transform
reverse incremental backups and compact full backup files.

• In b a ckup copy jobs: to merge backup files, create GFS backups (synthetic method) and compact full
backup files.

• To migrate (evacuate) backups between performance extents.

• To migrate (evacuate) Veeam Cloud Connect tenant backups between performance extents.

• To rebalance SOBR extents.

• To move backups to another repository.

• To copy backups to another repository.

• To export backups into standalone .VBK files.

• To upgrade the backup chain format for backup copies created in the periodic copy mode.

997 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When Veeam Backup & Replication performs an operation with Fast Clone, it reports this information to the
session details of this operation.

Fast Clone for Deduplicating Storage Appliances


For deduplicating storage appliances (ExaGrid, Quantum DXi and so on), Fast Clone is based on the reflink
technology and must be supported by vendors.

Fast Clone for Linux Repositories


For Linux backup repositories, Fast Clone is based on the reflink technology.

Requirements for Linux Repositories


To use Fast Clone, Veeam Backup & Replication requires that Linux backup repositories meet the following
conditions:

• File system is XFS.

• The Linux distribution is supported. For more information, see Backup Repository (XFS integration).

• The Linux kernel supports reflinks.

• Cyclic redundancy check (CRC) is enabled.

• The minimum supported data block size is 1 KB. The maximum supported block size is 4KB.

998 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring a Linux Repository
To configure a Linux backup repository for work with Fast Clone, perform the following steps:

1. Format the disk where backups will be stored using the following XFS volume format string:

mkfs.xfs -b size=4096 -m reflink=1,crc=1 /dev/sda1

Consider that:

o size=4096 sets file system block size to 4096 bytes.

o reflink=1 enables reflinking for the XFS instance (disabled by default).

o crc=1 enables checksums, required for reflink=1 (enabled by default).

2. Mount the disk to a specific directory:

mkdir /backups
mount /dev/sda1 /backups

3. Run the following command to ensure that the disk is properly configured:

df -hT

4. To permanently mount the disk, add the entry to the /etc/fstab configuration file. It is recommended
to use the UUID to specify the disk.

# <file system> <mount point> <type> <options> <dump> <pass>


UUID=<UUID> /backups xfs defaults 0 0

To get the UUID, run the following command:

blkid /dev/sda1

Limitations
After you have moved backup chains to a Linux backup repository with Fast Clone support, you must create
active full backups for these chains to activate Fast Clone. You can also schedule the backup file compact
operation instead of active full backup.

Fast Clone for Microsoft Windows and SMB Repositories


For Microsoft Windows and SMB backup repositories, Fast Clone is based on block cloning technology of
Microsoft. For more information on block cloning, see Microsoft Docs.

By default, Veeam Backup & Replication uses Fast Clone for all Microsoft Windows and SMB backup repositories
that meet the requirements. You can disable this option with a registry value. For more information, contact
Veeam Customer Support.

999 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Microsoft Windows and SMB Repositories
Microsoft Windows Backup Repository

To use Fast Clone, Veeam Backup & Replication requires that Microsoft Windows backup repositories meet the
following conditions:

• OS is Microsoft Windows Server 2016 (or later) or Microsoft Windows 10 Pro for Workstations (or later).

• File system is ReFS 3.1 (or later).

NOTE

All ReFS supported configurations must use Windows Server Catalog certified hardware. For other
requirements, limitations and known issues, see this Veeam KB article.

Sha red Folder Backup Repository

To use Fast Clone, Veeam Backup & Replication requires that SMB backup repositories support
FSCTL_DUPLICATE_EXTENTS_TO_FILE and FSCTL_SET_INTEGRITY_INFORMATION. SMB shares configured on
Microsoft Windows machines must also support the SMB 3.1.1 protocol and the ReFS 3.1 (or later) file system.

Depending on the type of the performed job, Veeam Backup & Replication also imposes the following
requirements on backup infrastructure components.

Ty p e of Job Requirements to backup infrastructure components

Ba ckup job Protocol: SMB 3.1.1

OS: Microsoft Windows Server 2016 (or later) or Microsoft Windows 10 Pro for
Workstations (or later) on the following backup infrastructure components:

• If a gateway is selected manually: Gateway server.


• If a gateway is selected automatically:
[For forward incremental chains] Mount server associated with the backup
repository, or backup server.
[For reverse incremental chains] Fast clone is supported if the source host
runs Microsoft Hyper-V Server 2016 (or later). For earlier versions of
hypervisor, fast clone is not supported.

Ba ckup copy job Protocol: SMB 3.1.1

OS: Microsoft Windows Server 2016 (or later) or Microsoft Wind ows 10 Pro for
Workstations (or later) on the following backup infrastructure components:
• If a gateway is selected manually: Gateway server.
• If a gateway is selected automatically:
[For direct data transport path] Mount server associated with the backup
repository, or backup server.
[For data transport path over WAN accelerators] Microsoft Windows
Server 2016 (or later) or Microsoft Windows 10 Pro for Workstations (or
later) on the target WAN accelerator.

1000 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations
The following limitations apply when Veeam Backup & Replication uses Fast Clone for Microsoft Windows or
SMB backup repositories:

• Veeam Backup & Replication does not use Fast Clone for backup repositories configured with
Veeam Backup & Replication 9.5 or an earlier version. After upgrade, such backup repositories will work as
backup repositories without Fast Clone support. To leverag e Fast Clone, edit settings of such backup
repositories and complete the E d it Backup Repository wizard without changing settings.

• After you have enabled Fast Clone for existing repositories as described in the previous parag raph or have
manually moved backup chains to backup repositories with Fast Clone support, you must create active full
backups for backup chains stored in / moved to the repositories to activate Fast Clone. You can also
schedule the backup file compact operation instead of performing active full backup.

• Due to Microsoft limitations, the source and destination files must be stored on the same ReFS volume.
For more information, see Restrictions and Remarks at Microsoft Docs.

If you add a backup repository with Fast Clone support as an extent to a scale-out backup repository,
make sure that you enable the Data Locality placement policy for this scale-out backup repository. If
backup files are stored on different extents, Fast Clone will not be used.

• Veeam Backup & Replication automatically aligns data blocks at a 4KB or 64 KB block boundary depending
on the volume configuration or SMB share used storage.

We recommend that you use ReFS volume formatted with 64 KB cluster size to provide better
performance with large data volumes.

• When you copy data from a ReFS volume to another location, the file system downloads cloned data
blocks. For this reason, copied data occupy more space in the target location than it used to occupy in the
source location. This can happen, for example, if you evacuate an extent that supports block cloning from
a scale-out backup repository and migrate VM backup data to another extent: copied data will require
more space than it originally took.

• If you plan to assign the role of a backup repository to Microsoft Windows Server 2016 version 1709 (or
later) or Microsoft Windows 10 Pro for Workstations (or later), consider the following limitations:

o Fast Clone and Windows data deduplication cannot be used simultaneously. Thus, if you target a
backup job to a repository supporting Fast Clone and enable Windows data deduplication, the Fast
Clone technology will not be used for this job.

o If you target a backup job to an SMB (CIFS) ReFS repository and enable Windows data deduplication,
the job will fail. Veeam Backup & Replication does not support such scenario.

1001 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
External Repositories
An external repository is a read-only repository. You can use Veeam Backup & Replication to copy, import and
restore backups created by Veeam Backup for AWS, Veeam Backup for Microsoft Azure and Veeam Backup for
Google Cloud from external to on-premises repositories. This way, you can perform data migration between
cloud, on-premises and virtual infrastructures.

Veeam Backup & Replication supports the following types of external repositories:

• Amazon S3 (with Standard storage class assigned)

• Azure Blob (Hot and Cool access tier)

• Google Cloud Platform (with Standard storage class assigned)

To start working with backups created by Veeam Backup for AWS, Veeam Backup for Microsoft Azure and
Veeam Backup for Google Cloud, you must add a repository that contains backups of Amazon EC2 instances,
Azure VMs or Google Cloud Platform VMs to the Veeam Backup & Replication infrastructure as an external
repository. After that, you can perform the following operations:

• Copy backups to on-premises repositories.

• Restore EC2 instances, Azure VMs and Google Cloud Platform VMs to AWS.

• Restore Azure VMs, EC2 instances and Google Cloud Platform VMs to Microsoft Azure .

• Restore Google Cloud Platform instances, EC2 instances and Azure VMs to Google Cloud.

• Restore guest OS files and folders.

• Export disks of EC2 instances, Azure VMs and Google Cloud Platform VMs .

• Govern retention policies.

• Perform Instant Recovery to VMware vSphere.

• Perform Instant Recovery to Microsoft Hyper-V.

NOTE

Consider the following:

• During the process of copying backups, or restore to Amazon EC2 or Microsoft Azure, data of EC2
instances and Azure VMs may migrate from one geographic location to another. In this case,
Veeam Backup & Replication displays a warning and stores a record about data migration to job or
task session details. For more information, see Locations.
• You cannot use an external repository as a target for backup or backup copy jobs.

1002 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How External Repository Works
Continue with this section to learn more on how external repositories work.

Ownership
Ownership defines what entity can own an Amazon S3, Azure Blob or Google Cloud storage repository at a time.

How Does Taking Ownership Occur


After Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam Backup for Google Cloud has
finished its initial backup job session, it becomes the rightful owner of both a storage repository and backup files
in that repository.

Taking ownership of such a repository along with its backup files by the Veeam Backup & Replication client
consists of the following consecutive steps:

• Step 1. Taking ownership of a repository.

Reclaiming ownership of a repository occurs every time a client adds object storage as an external
repository to the Veeam Backup & Replication console.

• Step 2. Taking ownership of backup files in the repository.

Becoming an owner of backup files in object storage is only possible after Veeam Backup for AWS, Veeam
Backup for Microsoft Azure or Veeam Backup for Google Cloud launches the backup job session which is
referring to backups you are trying to take ownership of (for example, backup files that are located in the
repository you have added at the step one).

During its session, Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam Backup for
Google Cloud verifies the owner of a repository and if it finds out that the owner has been changed, it
changes the owner of each backup file in that repository by creating a new checkpoint that refers to a new
rightful owner. Such a checkpoint will be used during subsequent sessions of a backup job to repeat owner
verification.

It is possible, however, that after you add an external repository, you never launch the associated backup job
again. In such a scenario, Veeam Backup & Replication will not be able to manage retention policies, but you will
still be able to restore external repository data, remove backups from external repositories and perform backup
copy.

Taking Ownership by Another Veeam Backup & Replication


Client
Ownership of a repository along with its backup files can only be granted to one Veeam Backup & Replication
client at a time.

Therefore, if a client A adds an external repository that has previously been added by the client B, the client B
completely loses its ownership privileges.

Losing privileges means that the client B will no longer be able to manage retention policies. All the previously
created backup copy jobs and restore sessions will be failing.

Ownership, however, can easily be reclaimed by re-adding the same object storage anew.

1003 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cache
Veeam Backup & Replication caches data that is being retrieved from external repositories every time a backup
copy job or restore session is performed.

Such an approach helps not only to reduce the number of cost-expensive operations incurred by AWS, Microsoft
Azure or Google Cloud Platform, but also decrease the amount of traffic being sent over the network.

Consider the following:

• Cache is created on a gateway server while the following activities are being processed:

o Backup copy jobs.

o Restore sessions.

• Cache is not created upon the addition of an external repository to the Veeam Backup & Replication
console.

• Cache consists of metadata of blocks being retrieved from external repositories.

• Cache is written to:

o On a Windows-based gateway server: C:\ProgramData\Veeam\ExternalCache

o On a Linux-based gateway server: /var/veeam/ExternalCache

• Cache is reused and updated during each subsequent execution of a backup copy job or restore session.

• Cache size limit is 10GB. Once reached, Veeam will purge obsolete cache by 20% preserving most
frequently used parts. Purging is done by the maintenance job.

• Cache is removed in the following cases:

o An external repository has been removed from the Veeam Backup & Replication console.

o The gateway server has been changed in the settings of the external repository configuration.

o The backup file has been removed from the external repository.

o During the maintenance job session.

• Cache can be removed manually without affecting the backup infrastructure in any negative way.

Encryption
Backups that reside in Amazon S3 buckets, Azure Blob storage and Google Cloud storage can be encrypted by
Veeam Backup for AWS, Veeam Backup for Microsoft Azure and Veeam Backup for Google Cloud. Moreover,
password for such encrypted backups may change on a daily basis. For example, there is a backup chain in
Amazon S3 bucket that consists of 10 restore points, each of which was encrypted with different password.
Therefore, there are 10 different passwords in total that have been used.

To be able to decrypt each restore point in such a backup chain without having to provide each previously used
password separately, Veeam Backup & Replication implements the ability of backward hierarchical decryption.

Backward hierarchical decryption requires you to provide only the latest password so that all the previously
created restore points can be decrypted as well. For example, there are three restore points: A, B, and C. The
point A was encrypted with password 1, B with password 2, and C with password 3. Therefore, you will only
need to know the password of the C point to decrypt points C, B, and A.

1004 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you plan to perform data recovery operations with encrypted backups, you must provide a p assword for these
backups in the E x ternal Repository wizard:

• [For Veeam Backup for AWS] At the Encryption step of the wizard.

• [For Veeam Backup for Microsoft Azure] At the Encryption step of the wizard.

• [For Google Cloud Platform] At the Bucket step of the wizard.

Managing Retention Policy


A retention policy is set in the backup policy settings of Veeam Backup for AWS, Veeam Backup for Microsoft
Azure and Veeam Backup for Google Cloud and defines the number of restore points to keep in repositories.

Retention policies are initially managed by Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam
Backup for Google Cloud until a Veeam Backup & Replication client reclaims ownership of a repository and all
the backup files in such a repository.

Once ownership is reclaimed, Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam Backup for
Google Cloud ceases to govern retention policies and the Veeam Backup & Replication client becomes
responsible for removing obsolete restore points from repositories.

The restore points that fall under the retention policy will be removed upon the next successful session of the
maintenance job.

When a Veeam Backup & Replication client removes an external repository from its scope, it relinquishes its
ownership which then goes directly to Veeam Backup for AWS, Veeam Backup for Microsoft Azure or Veeam
Backup for Google Cloud until another Veeam Backup & Replication client reclaims it anew and so forth.

IMP ORTANT

A retention policy can only be applied by the Veeam Backup & Replication client that is the rightful owner
of an Amazon S3 object storage repository and its backup files.

Maintenance Job
The maintenance job is a system job that is executed automatically every 24 hours.

The maintenance job does the following:

• Purges obsolete restore points that fall under the retention policy.

To be able to purge obsolete restore points from external repositories due to the retention policy
threshold, a Veeam Backup & Replication client must be the owner of a repository and its backup files.

• Purges cache by 20% of the size limit. By default, the size limit is 10GB.

• Saves its session results to the configuration database.

The session results can be found in the History view under the Sy stem node.

1005 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding External Repositories
You can add the following types of external repositories:

• External Amazon S3 Storage

• External Azure Blob Storage

• External Google Cloud Storage

Adding External Amazon S3 Storage


To add an Amazon S3 storage as an external repository, do the following:

1. Launch the New External Repository wizard.

2. Specify the repository name and description.

3. Specify the cloud account.

4. Specify cloud storage details.

5. Wait for the repository to be added to the infrastructure.

6. Finish working with the wizard.

NOTE

If you added the Veeam Backup for AWS appliance to the Veeam Backup & Replication infrastructure and
want to deploy a new S3 repository, see instructions in the Adding S3 Repositories section in the
Integration with Veeam Backup for AWS Guide.

1006 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New External Repository Wizard
To launch the New Backup Repository wizard, do one of the following:

• Open the Ba ckup Infrastructure view. In the inventory pane select the E x ternal Repositories node and click
Connect to Repository on the ribbon. At the Connect to External Repository window, select Veeam Backup
for AWS.

• Open the Ba ckup Infrastructure view. In the inventory pane right-click the E x ternal Repositories node and
select Connect to... At the Connect to External Repository window, select Veea m Backup for AWS.

1007 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify External Repository Name
At the Na me step of the wizard, specify a name and description for the external repository.

1008 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Cloud Repository Account
At the Account step of the wizard, specify Amazon S3 connection settings:

1. From the Credentials drop-down list, select user credentials to access an Amazon S3 bucket with Amazon
EC2 instance backups.

If you have not set up credentials beforehand in the Cloud Credentials Manager, click the Ma nage cloud
a ccounts link or click Ad d on the right to add the necessary credentials.

2. From the Da ta center region drop-down list, select the AWS region where the Amazon S3 bucket is
located: Global, GovCloud (US) , or China .

3. From the Ga teway server drop-down list, select a gateway server that will be used to access the Amazon
S3 bucket. We recommend that you use a gateway server, for example, if your organization has NAT or
different types of firewalls and your access to the internet is limited.

The gateway server caches data when you copy backups or perform restore operations. The gateway
server helps you decrease the amount of traffic being sent over the network and reduce data transfer
costs. For more information on caching data, see Cache.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. If the
Veeam Backup & Replication server resides in a region that differs from the Amazon region where your
Amazon S3 bucket resides, choose a server that is located close to the bucket. You can choose any
Microsoft Windows or Linux server that is added to your Veeam Backup & Replication infrastructure and
has internet connection. Note that the server must be added to the infrastructure before hand. For more
information on how to add a server, see the Adding Microsoft Windows Servers and Adding Linux Servers
sections.

NOTE

Consider the following:

• On the gateway server, Veeam Backup & Replication deploys Veeam Data Mover that handles
traffic sent when you work with external repository data. If Veeam Data Mover becomes
outdated, you must upgrade it as described in section Upgrading External Repositories.
• If you choose not to use a gateway server, make sure that all scale-out repository extents
have direct internet access.

1009 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1010 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Cloud Storage Details
At the Buck et step of the wizard, specify an Amazon S3 bucket and folder where Amazon EC2 instance backups
reside:

1. From the Da ta center region drop-down list, select an AWS region where the Amazon S3 bucket is located.

2. From the Bucket drop-down list, select the necessary Amazon S3 bucket where EC2 instance backups
reside.

3. Click Browse to select a folder in the Amazon S3 bucket where EC2 instance backups reside.

If you do not see the required folder, make sure that the repository you are trying to add is created on the
Veeam Backup for AWS server.

NOTE

Consider the following:

• Only Standard storage class is supported.


• If another Veeam Backup & Replication client has already added the same folder, you will be
prompted whether to reclaim ownership of such a folder. For more information about ownership,
see Ownership.

1011 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Configure Encryption
At the E ncryption step of the wizard, provide a key for decryption:

• If data in the external repository is encrypted with a key management service (KMS) customer master key
(CMK), Veeam Backup & Replication shows the used key. In this case, Veeam Backup & Replication will
automatically decrypt the backups.

• If data in the external repository is encrypted with a password, select E nable backup file encryption and
then click P erform Veeam encryption with the following password. From the drop-down list, select the
password that must be used to decrypt the data. If the password is correct, Veeam Backup & Replication
will automatically decrypt the backups.

If you have not added the password beforehand, click the Ma nage passwords link or the Ad d button to
add the necessary password. For more information on adding passwords, see Creating Passwords.

If you do not specify the decryption password, you can do it later. For more information, see Viewing
External Repository Data.

For more information on how backups are encrypted, see the S3 Repository Encryption section in the Veeam
Backup for AWS User Guide.

1012 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Apply Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the external repository to the backup
infrastructure.

1013 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard
At the Summary step of the wizard, review the external repository settings and click Finish.

Adding External Azure Blob Storage


To add an Microsoft Azure Blob storage as an external repository, do the following:

1. Launch the New External Repository wizard.

2. Specify the repository name.

3. Specify the cloud account.

4. Select the Azure Blob container.

5. Wait for the repository to be added to the infrastructure.

6. Finish working with the wizard.

NOTE

If you added the Veeam Backup for Microsoft Azure appliance to the Veeam Backup & Replication
infrastructure and want to deploy a new Microsoft Azure Blob storage, see instructions in the Adding
Microsoft Azure Blob Storage section in the Integration with Veeam Backup for Microsoft Azure Guide.

1014 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New External Repository Wizard
To launch the New External Repository wizard, do one of the following:

• Open the Ba ckup Infrastructure view. In the inventory pane select the E x ternal Repositories node and click
Connect to Repository on the ribbon. At the Connect to External Repository window, select Veeam Backup
for Microsoft Azure.

• Open the Ba ckup Infrastructure view. In the inventory pane right-click the E x ternal Repositories node and
select Connect to... At the Connect to External Repository window, select Veea m Backup for Microsoft
Azure.

1015 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify External Repository Name
At the Na me step of the wizard, specify a name and description for the external repository.

1016 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Cloud Repository Account
At the Account step of the wizard, specify settings for an account which will be used to connect to Azure Blob
storage:

1. From the Credentials drop-down list, select user credentials to access your Azure Blob storage.

If you have not set up credentials beforehand in the Cloud Credentials Manager, click the Ma nage cloud
a ccounts link or click Ad d on the right to add the necessary credentials.

2. From the Reg ion drop-down list, select the region type.

3. From the Ga teway server drop-down list, select a gateway server that will be used to access Azure Blob
storage. We recommend that you use a gateway server, for example, if your organization has NAT or
different types of firewalls and your access to the internet is limited.

The gateway server caches data when you copy backups or perform restore operations. The gateway
server helps you decrease the amount of traffic being sent over the network and reduce data transfer
costs. For more information on caching data, see Cache.

By default, the role of a gateway server is assigned to the Veeam Backup & Replication server. If the
Veeam Backup & Replication server resides in a region that differs from the Azure region where your Blob
storage resides, choose a server that is located close to the storage. You can choose any Microsoft
Windows or Linux server that is added to your Veeam Backup & Replication infrastructure and has internet
connection. Note that the server must be added to the infrastructure beforehand. For more information on
how to add a server, see the Adding Microsoft Windows Servers and Adding Linux Servers sections.

NOTE

Consider the following:

• On the gateway server, Veeam Backup & Replication deploys Veeam Data Mover that handles
traffic sent when you work with external repository data. If Veeam Data Mover becomes
outdated, you must upgrade it as described in section Upgrading External Repositories.
• If you choose not to use a gateway server, make sure that all scale-out repository extents
have direct internet access.

1017 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1018 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Azure Blob Container
At the Container step of the wizard, specify Azure Blob storage container settings:

1. From the Container drop-down list, select a container that contains backups created by Veeam Backup for
Microsoft Azure.

2. Click Browse to select a folder that contains backups created by Veeam Backup for Microsoft Azure.

If you do not see the required folder, make sure that the repository you are trying to add is created on the
Veeam Backup for Microsoft Azure server.

NOTE

Consider the following:

• Only Hot and Cool access tiers are supported.


• If another Veeam Backup & Replication client has already added the same folder, you will be
prompted whether to reclaim ownership of such a folder. For more information about ownership,
see Ownership.

1019 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Configure Encryption
At the E ncryption step of the wizard, provide a key for decryption:

• If data in the external repository is encrypted with a Key Vault key, Veeam Backup & Replication shows the
used Key Vault and encryption key. In this case, Veeam Backup & Replication will automatically decrypt
the backups.

• If data in the external repository is encrypted with a password, select E nable backup file encryption and
then click P erform Veeam encryption with the following password. From the drop-down list, select the
password that must be used to decrypt the data. If the password is correct, Veeam Backup & Replication
will automatically decrypt the backups.

If you have not added the password beforehand, click the Ma nage passwords link or the Ad d button to
add the necessary password. For more information on adding passwords, see Creating Passwords.

If you do not specify the decryption password, you can do it later. For more information, see Viewing
External Repository Data.

1020 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Apply Settings
At the Ap p ly step of the wizard, wait for Veeam Backup & Replication to install and configure all required
components. Then click Nex t to complete the procedure of adding the external repository to the backup
infrastructure.

1021 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard
At the Summary step of the wizard, review the repository configuration settings and click Finish.

Adding External Google Cloud Storage


To add an external Google Cloud storage repository to the backup infrastructure, do the following:

1. Launch the New External Repository wizard.

2. Specify the repository name.

3. Specify the cloud account.

4. Specify cloud storage details.

5. Apply settings.

6. Finish working with the wizard.

NOTE

If you added the Google Cloud Platform appliance to the Veeam Backup & Replication infrastructure and
want to deploy a new Cloud Storage Repository, see instructions in the Adding Standard Backup Repository
section in the Integration with Google Cloud Platform Guide.

1022 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New External Repository Wizard
To launch the New External Repository wizard, do one of the following:

• Open the Ba ckup Infrastructure view. In the inventory pane select the E x ternal Repositories node and click
Connect to Repository on the ribbon. At the Connect to External Repository window, select Veeam Backup
for Google Cloud.

• Open the Ba ckup Infrastructure view. In the inventory pane right-click the E x ternal Repositories node and
select Connect to... At the Connect to External Repository window, select Veea m Backup for Google
Cloud.

1023 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify External Repository Name
At the Na me step of the wizard, specify a name and description for the external repository.

1. In the Na me field, enter a name for the external repository.

2. In the Description field, enter an optional description.

The default description contains information about the user who added the external repository, date and
time when the external repository was added.

1024 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Cloud Repository Account
At the Account step of the wizard, specify Google Cloud connection settings:

1. From the Credentials drop-down list, select user credentials to access a storage bucket with the backups.

If you have not set up credentials beforehand, click the Ma nage cloud accounts link or click Ad d on the
right and add the necessary credentials, as described in section Google Cloud Accounts .

2. From the Ga teway server drop-down list, select a server that will be used to access the Google Cloud
storage.

You can select any Microsoft Windows or Linux server that is added to your backup infrastructure and has
internet connection. You may want to use a gateway server, for example, if your organization has NAT or
different types of firewalls and your access to the internet is limited. For more information on how to add
such a server to your environment, see Adding Microsoft Windows Servers and Adding Linux Servers. By
default, the role of a gateway server is assigned to the machine where Veeam Backup & Replication is
installed.

On the gateway server, Veeam Backup & Replication deploys Veeam Data Mover. Veeam Data Mover is
responsible for handling ingress/egress requests that are sent to/from the gateway server when you work
with the external repository data in Veeam Backup & Replication. If Veeam Data Mover becomes outdated,
you must upgrade it as described in section Upgrading External Repositories.

Gateway servers store cached data. For more information, see Cache.

1025 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Cloud Storage Details
At the Buck et step of the wizard, specify a Google Cloud bucket and folder where Google Cloud instance
backups reside:

1. From the Da ta center region drop-down list, select a region.

2. Next to the Buck et field, click Browse and select a bucket.

3. In the Select Folder field, select a cloud folder where the data will be stored. To do it, click Browse and
select an existing folder.

4. If the folder contains encrypted backups, select the Use this password for encrypted backups check box
and provide a password. If you skip this step for encrypted backups, Veeam Backup & Replication will add
such backups to the E x ternal Repository (Encrypted) node. For more information, see Viewing External
Repository Data.

For more information about encryption, see Encryption.

NOTE

Consider the following:

• Only Standard storage class is supported.


• If another Veeam Backup & Replication client has already added the same folder, you will be
prompted whether to reclaim ownership of such a folder. For more information about ownership,
see Ownership.

1026 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply Settings
At the Ap p ly step of the wizard, wait until Veeam Backup & Replication applies settings and completes adding
the external repository. Then click Nex t.

1027 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review the external repository settings and click Finish.

1028 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing External Repositories
You can manage your external repositories in various ways: rescan external repositories to synchronize their
state with the state of an object storage, upgrade external repositories by uploading a new version of Veeam
Data Mover to the gateway server, edit settings of the external repositories, or remove the external
repositories. For more information about these options, see the following sections.

Viewing External Repository Data


After you add an external repository to the backup infrastructure, you can view backups in E x ternal Repository
and E x ternal Repository (Encrypted) nodes of the Ba ckups node in the Home view.

• In the E x ternal Repository node, Veeam Backup & Replication displays:

o Amazon EC2 instance backups that were decrypted at the Bucket step of the New E xternal Repository
wizard.

o Microsoft Azure VMs that were decrypted at the Container step of the New E xternal Repository
wizard.

o Google Cloud Platform VM instances that were decrypted at the Bucket step of the New External
Rep ository wizard.

• In the E x ternal Repository (Encrypted) node, Veeam Backup & Replication displays:

o EC2 instance backups that were encrypted by Veeam Backup for AWS.

o Microsoft Azure VMs that were encrypted by Veeam Backup for Microsoft Azure.

o Google Cloud Platform VM instances that were encrypted by Veeam Backup for Google Cloud.

To decrypt backups, select a backup policy that created the backups you want to decrypt, click Sp ecify
P a ssword on the ribbon, provide a password and click OK.

1029 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Rescanning External Repositories
To synchronize the state of an external repository with the state of an object storage (Amazon S3, Azure Blob or
Google Cloud Storage), you can use the rescan feature. During rescan, Veeam Backup & Replication fetches
newly created restore points and other required metadata.

Consider the following:

• Rescan is done automatically in the following cases:

o After you add an external repository to the backup infrastructure.

o Every 24 hours.

o After a backup chain is modified in the object storage. For example, if a restore point is added or
deleted.

• Rescan session results are saved to the configuration database and can be found in the History view under
the Sy stem node.

To rescan external repositories manually:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click E x ternal Repositories.

3. Select a repository you want to rescan and click Rescan on the ribbon menu or right-click a repository and
select Rescan.

If you have more than one external repository added to the scope, you may want to rescan all the repositori es
altogether. For that, right-click the root E x ternal Repositories node in the navigation pane and select Rescan.

Upgrading External Repositories


When you upgrade an external repository, a new version of Veeam Data Mover is uploaded to the gateway
server. Veeam Data Mover is responsible for handling ingress/egress requests that are sent to/from the gateway
server during working with the external repository data in Veeam Backup & Replication.

1030 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upload of Veeam Data Mover is done directly to a gateway server which you specify at the Account step of the
New E xternal Repository wizard.

To upgrade an external repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click E x ternal Repositories.

3. Select a repository you want to upgrade and click Up grade on the ribbon menu or right-click a repository
and select Up g rade.

Editing Settings of External Repositories


To edit settings of an external repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click E x ternal Repositories.

3. In the working area, select an external repository and click E d it Repository on the ribbon or right-click the
external repository and select P roperties.

1031 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Follow the steps of the E d it External Repository wizard and edit settings as required.

Note that some settings cannot be modified and will remain disabled during editing.

Removing External Repositories


You can remove an external repository from the backup infrastructure.

When you remove an external repository, Veeam Backup & Replication does the following:

• Relinquishes ownership.

• Removes associated external repository records from the configuration database.

• Removes associated cache from the gateway server.

To remove an external repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click E x ternal Repositories.

1032 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select an external repository and click Remove Repository on the ribbon or right-click
the external repository and select Remove.

1033 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Scale-Out Backup Repositories
A scale-out backup repository is a repository system with horizontal scaling support for multi-tier storage of
data. A scale-out backup repository consists of one or more backup repositories or object storage repositories
called performance tier, and can be expanded with object storage repositories for long -term and archive
storage: capacity tier and archive tier. All the storage devices and systems inside the scale -out backup
repository are joined into a system, with their capacities summarized.

NOTE

Consider the following:

• Scale-out backup repository is included in the Veeam Universal License. When using a legacy socket -
based license, Enterprise or higher edition is required.
• If you configure a scale-out backup repository and then downgrade to the Standard license, you will
not be able to run jobs targeted at the scale-out backup repository. However, you will be able to
perform restore from the scale-out backup repository.

This feature provides the following benefits:

• It provides a convenient way of managing the backup storage.

• A scale-out backup repository can be expanded at any moment: if the extents of your scale -out backup
repository run out of space, you can add a new extent to the existing scale-out backup repository. For
example, if backup data grows and the backup repository reaches the storage limit, you can add a new
storage system to the scale-out backup repository. The free space on this storage system will be added to
the capacity of the scale-out backup repository. As a result, you will not have to move backups to a
backup repository of a larger size.

• It supports any backup target supported by Veeam: Windows or Linux servers with local or DAS storage,
network shares, deduplicating storage appliances. All the features of any storage device or system are
preserved.

• It allows you to set up granular performance policy. For more information, see Backup File Placement.

• It provides practically unlimited cloud-based storage capacity: you can instruct


Veeam Backup & Replication to offload data from extents to the cloud for long -term storage. For details,
see Capacity Tier.

A scale-out backup repository can comprise different tiers, or logical levels of storage.

• Performance tier is the level used for the fast access to the data. It consists of one or more backup
repositories or object storage repositories called performance extents.

For more information, see Performance Tier.

1034 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Capacity tier is an additional level for storing data that needs to be accessed less frequently. However, you
still can restore your data directly from it. The capacity tier consists of cloud -based or on-premises object
storage repositories called capacity extent.

For more information, see Capacity Tier.

• Archive tier is an additional level for archive storage of infrequently accessed data. Applicable data can be
transported either from the capacity or archive tier. For restore from the archive tier, data must undergo
preparation process.

For more information, see Archive Tier.

A scale-out backup repository can be used for the following types of jobs and tasks:

• Backup jobs

• Backup copy jobs

You can copy backups that reside in scale-out backup repositories and store backup copies in scale-out
backup repositories.

• Veeam backups for Amazon and Microsoft Azure (via backup copy jobs)

• VeeamZIP tasks

• Backup jobs created by Veeam Agent for Linux 2.0 or later

• Backup jobs created by Veeam Agent for Unix 2.0 or later

• Backup jobs created by Veeam Agent for Microsoft Windows 2.0 or later

• Backup jobs created by Veeam Agent for Mac

• Unstructured data backup jobs (file backup jobs and object storage backup jobs)

• Backup jobs created by Veeam Backup for Nutanix AHV

Backup files stored in the scale-out repository can be used for all types of restores, replication from backup and
backup copy jobs. You can verify such backups with SureBackup jobs . The scale-out backup repository can be
used as a staging backup repository for restore from tape media. Files restored from the tape media are placed
to the extents according to data placement policy configured for the scale-out backup repository. For more
information, see Backup File Placement.

To deploy a scale-out backup repository, you must configure one or more backup repositories or object storage
repositories and add them to a scale-out backup repository as extents. You can use the following types of
repositories:

• Microsoft Windows backup repositories

• Linux backup repositories

• SMB (CIFS) shared folders

• NFS shared folders

• Deduplicating storage appliances

• Object Storage Repository

1035 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations for Scale-Out Backup Repositories
Scale-out backup repositories have the following limitations:

• You cannot use a scale-out backup repository as a target for the following types of jobs:

o Configuration backup job

o Replication jobs (including replica seeding)

o Veeam Agent backup jobs created by Veeam Agent for Microsoft Windows 1.5 or earlier

o Veeam Agent backup jobs created by Veeam Agent for Linux 1.0 Update 1 or earlier

• You cannot add a backup repository as an extent to the scale-out backup repository if any job of
unsupported type is targeted at this backup repository or if the backup repository contains data produced
by jobs of unsupported types (for example, replica metadata). To add such backup repository as an extent,
you must first target unsupported jobs to another backup repository and remove the job data from the
backup repository in question.

• Scale-out backup repositories do not support rotated drives. If you enable the This repository is backed by
rotated hard drives setting on an extent, Veeam Backup & Replication will ignore this setting and will work
with such repository as with a standard extent.

• If a backup repository is added as an extent to the scale-out backup repository, you cannot use it as a
regular backup repository. You cannot target jobs to this backup repository. Instead, you have to target
jobs to the configured scale-out backup repository.

• You cannot add a scale-out backup repository as an extent to another scale-out backup repository.

• You cannot add a backup repository as an extent if this backup repository is already added as an extent to
another scale-out backup repository.

• You cannot add a backup repository as an extent if this backup repository is already used as a backup
destination by VMware Cloud Director organizations.

• You cannot add a backup repository in which some activity is being p erformed (for example, a backup job
or restore task) as an extent to the scale-out backup repository.

• You cannot use scale-out backup repository to keep configuration backups.

• You cannot assign the role of a cache repository for file backup or object storage backup to a scale-out
backup repository and its extents. To learn more about the cache repository, see the Backup Infrastructure
for Unstructured Data Backup section.

• You can add only one type of object storage repositories as performance extents of one scale -out backup
repository. For example, if the first extent is an Amazon S3 object storage repository, the second extent
must also be an Amazon S3 object storage repository.

• You can add only one AWS Snowball Edge storage and Azure Data Box device to a scale -out backup
repository.

• You cannot use the backup repository and the direct object storage repository for the same performance
tier.

• Data located in object storage repositories is organized into a separate backup chain for every machine in a
job.

• We do not recommend adding more than 16 extents to one tier within one scale-out backup repository,
otherwise you might have performance issues.

1036 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you use immutability and have several extents in your performance tier, you must enable it for all
extents within this tier. You cannot use mixed configuration and have only one extent with immutability
enabled.

• If you apply the Forget or Remove from disk options to a missing restore point in a scale-out backup
repository, the backup file associated with the missing restore point will be deleted from capacity tier and
archive tier on the next offload and archiving job run.

• If you use Enterprise edition of Veeam Backup & Replication, you can create two scale-out backup
repositories.

• [For Enterprise edition of Veeam Backup & Replication] For each scale-out backup repository, you can
have either backup repositories or object storage repositories added as a performance extent or a capacity
extent. You can have 2 active, and 1 inactive (that is, put to the Maintenance mode) performance or
capacity extents. You can add inactive extents, for example, if any of active extents has no free space, and
you want to evacuate backup data from it.

• [For Enterprise edition of Veeam Backup & Replication] If you add four performance extents and do not
put any of them to the Maintenance mode, the jobs targeted at the scale-out backup repository will fail.

• Veeam Universal License and Enterprise Plus editions have no limitations on the number of scale-out
backup repositories or performance extents and capacity extents.

• If you want to use the Extract utility to work with backup files located on any of the extents of your scale -
out backup repository, make sure that incremental and full backup files are located on the same extent.

• You can use the Veeam Backup Validator utility only for backups stored in the performance tier which
consists of backup repositories (except object storage repositories). Make sure that incremental and full
backup files are located on the same extent.

• If you want to add an object storage repository added as a capacity or performance extent to another
backup server, you must switch this object storage repository to the Maintenance mode on the initial
server. Note that the secondary server will request the ownership over the object storage repository. After
you change the ownership, the backup jobs (except for the offload job to capacity tier) will fail on the
primary backup server.

• To let Veeam Backup & Replication automatically import backups during rescan of a scale-out backup
repository, names of VBM files and paths to VBM files (starting from the backup repository root to VBM
files, not including the root itself) must contain only allowed characters:

o Alphanumeric characters: a-zA-Z0-9

o Special characters: _-.+=@^

Names of VBM file and paths to VBM files must not contain spaces.

If a name of a VBM file or a path to a VBM file contains prohibited characters, Veeam Backup & Replication
will fail to import such backup during rescan of the scale-out backup repository. To import such backup,
you can replace prohibited characters with the underscore character, for example: C:\My
Repository\Backup_Job\Backup_Job.vbm. You do not need to rename the actual backup files.

• Veeam Backup & Replication does not split one backup file across multiple extents.

• If a repository is used as a cloud repository, you cannot add it as an extent of a scale -out backup
repository. For more information, see Veeam Cloud Connect.

• [For Nutanix AHV VM backups] Due to specifics of backup jobs for AHV VMs, Veeam Backup for Nutanix
AHV always creates a separate backup chain for each VM added to a backup job. Thus, even if you clear the
Use per-machine backup files check box in the advanced settings of a scale-out backup repository,
backups of multiple AHV VMs are not stored in a single backup file.

1037 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Immutability for Scale-Out Backup Repositories
Veeam Backup & Replication allows you to prohibit deletion of data from object storage repositories added as
the extents of the scale-out backup repository by making that data temporarily immutable. It is done for
increased security: immutability protects your data against loss as a result of attacks, malware activity or other
injurious actions.

You can enable the immutability feature for any tier of scale-out backup repository.

To learn how immutability works with performance tier of the scale-out backup repository, see Immutability for
Performance Tier.

To learn how immutability works with capacity tier of the scale-out backup repository, see Immutability for
Capacity Tier.

To learn how immutability works with archive tier of the scale-out backup repository, see Immutability for
Archive Tier.

NOTE

Before you use an object storage repository as an immutable extent, you must configure immutability for
this object storage beforehand. For more information, see Enabling Immutability for object storage
repositories.

1038 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Performance Tier
Performance tier of a scale-out backup repository is the level used for fast access to the data.

The performance tier of a scale-out backup repository can comprise one or more performance extents. A
performance extent is a backup repository or an object storage repository added to the scale -out backup
repository. The list of the performance extents is displayed at the Add Performance Extents step of the New
Sca le-out Backup Repository wizard.

After you add a backup repository or an object storage repository to the scale -out backup repository, they no
longer exist as individual backup repositories.

When a backup repository or an object storage repository is added as a performance extent, some of its original
settings are kept, and some are not. The following settings are kept, or inherited:

• Number of tasks that can be performed simultaneously

• Read and write data rate limit

• Data decompression settings

• Block alignment settings

• Connection mode (using gateway server or direct)

• Object storage consumption (for object storage repositories)

The following settings are not inherited:

• Rotated drive settings. Rotated drive settings are ignored and cannot be configured at the level of the
scale-out backup repository.

• Per-machine backup file settings. Per-machine settings can be configured at the level of the scale-out
backup repository.

Limitations for Performance Tier


Consider the following limitations for performance tier:

• The same limitations that are specific for certain types of backup repositories apply to the performance
extents. For example, if you add Dell Data Domain as a performance extent to the scale -out backup
repository, you will not be able to create a backup chain longer than 120 points in this scale -out backup
repository.

• The performance extents of the scale-out backup repository should be located in the same site.
Technically, you can add to the scale-out backup repository the performance extents that reside in
different sites. However, in this case Veeam Backup & Replication will have to access VM backup files on
storage devices in different locations, and the backup performance will degrade.

• You cannot use object storage of different providers in the same type of tier. For example, you cannot add
and use Amazon S3 storage and Microsoft Azure Blob storage to one capacity extent.

• You can add only one type of object storage repositories as performa nce extents of one scale-out backup
repository. For example, if a first extent is an Amazon S3 object storage repository, the second extent
must also be an Amazon S3 object storage repository.

• You cannot use the backup repository and the direct object storage repository for the same performance
tier.

1039 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Data located in object storage repositories is organized into a separate backup chain for every machine in a
job.

• If you use immutability and have several extents in your performance tier, you must enabl e it for all
extents within this tier. You cannot use mixed configuration and have only one extent with immutability
enabled.

• You cannot add as performance extents one Wasabi bucket as an S3 Compatible Object Storage and
another Wasabi bucket as a Wasabi Cloud Object Storage to the same type of tier (either performance tier
or capacity tier) of a scale-out backup repository.

• You cannot use the same object storage repository as a performance extent and as a capacity extent.

Performance Tier Extent Structure


If your performance tier consists of object storage repositories, Veeam Backup & Replication creates and
maintains the following structure of directories after backups are moved to the performance tier extents.

Directory Description

Veeam/Backup/ Standard folders created by Veeam Backup & Replication.

Rep ository_folder_name Contains information on the repository name and the repository ID.

Clients Contains backups.

Client catalogue Contains information on solutions that create backups to this repository.

Ba ckup catalogue Contains backup ID.

CloudStg Contains data blocks.

MetaData Contains metadata and checkpoints.

1040 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Directory Description

Сonfig Contains information on the object storage repository infrastructure.

Owner Contains information on a repository owner.

Rep ository Contains information on a repository.

Backup File Placement for Performance Tier


Veeam Backup & Replication stores backup files on all performance extents of the scale-out backup repository.

When you configure a scale-out backup repository, you must set the backup file placement policy for backup
repositories. The backup file placement policy describes how backup files are distributed between extents. You
can choose one of the following policies:

• Data locality

• Performance

You can also select an extent for backup file placement, which has its nuances if you set the Performance policy
for the scale-out backup repository:

• Extent Selection

• Extent Selection for Backup Repositories with Performance Policy

• Extent Selection for Object Storage Repositories Added as Performance Extents

Keep in mind that at the beginning of a job, Veeam Backup & Replication retrieves the actual free space on a
scale-out backup repository and estimates the size of a restore point to be created. Then the estimated restore
point size is subtracted from the actual free space to determine the estimated free space. This estimated free
space is then used by all further concurrently running jobs targeted at the same scale-out backup repository. For
details, see Backup Size Estimation.

If you do not select the Strict placement policy enforcement check box when you specify backup placement
policy for a scale-out backup repository, the backup file placement policy will not apply. If the necessary extent
is not accessible, Veeam Backup & Replication will disregard the policy limitations and attempt to place the
backup file to the extent that has enough free space for the backup file.

For example, you have set the Performance policy for the scale-out backup repository and specified that full
backup files must be stored on Extent 1 and incremental backup files must be stored on Extent 2. If before an
incremental backup job session Extent 2 goes offline, the new incremental backup file will be placed to Extent 1.

NOTE

Veeam Backup & Replication places backups of Microsoft SQL transaction logs, Oracle archived logs and
PostgreSQL WAL files to the extent configured for storing incremental backup files. If such extent is not
accessible, Veeam Backup & Replication will attempt to place log backups to any other extent that has
enough free space.

1041 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Locality
If you set the Data locality policy for a scale-out backup repository, all backup files that belong to the same
backup chain are stored on the same extent of the scale-out backup repository.

The Data locality policy does not put any limitations to backup chains. A new backup chain can be stored on the
same extent or another extent. For example, if you create an active full backup, Veeam Backup & Replication
may store the full backup file to another extent, and all dependent incremental backup files will be stored
together with this full backup file.

NOTE

If you use a deduplicating storage appliance as an extent to the scale-out backup repository,
Veeam Backup & Replication will attempt to place a new full backup (active or synthetic) to the extent
where the full backup from the previous backup chain resides. Such behavior will help increase the data
deduplication ratio. However, if you use ExaGrid appliances as extents of scale -out backup repository,
Veeam Backup & Replication will place a new backup to the extent with the highest storage capacity.

TIP

If you plan to use Fast Clone on performance extents with volumes formatted with ReFS or XFS, select
Data locality .

Performance
If you set the Performance policy for a scale-out backup repository, full backup files and incremental backup
files that belong to the same backup chain are stored on different extents of the scale -out backup repository. If
necessary, you can explicitly specify on which extents full backup files and incremental backup files must be
stored.

The Performance policy can improve performance of transformation processes if you use raw data devices as
extents. When Veeam Backup & Replication performs transformation, it needs to access a number of backup
files in the backup repository. If these files are located on different storage devices, the I/O load on the devices
hosting backup files will be lower.

1042 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you set the Performance policy, you must make sure that the network connection between extents is fast and
reliable. You must also make sure all extents are online when the backup job, backup copy job or a restore task
starts. If any extent hosting backup files in the current backup chain is not available, the backup chain will be
broken, and Veeam Backup & Replication will not be able to complete the task. To avoid data loss in this
situation, you can enable the P erform full backup when required extent is offline option for the scale-out
backup repository. With this option enabled, Veeam Backup & Replication will create a full backup instead of
incremental backup if some files are missing from the backup chain.

Extent Selection
To select an extent for backup file placement, Veeam Backup & Replication checks the following conditions:

1. Availability of extents on which backup files reside. If some extent with backup files from the current
backup chain is not accessible, Veeam Backup & Replication will trigger a full backup instead of
incremental (if this option is enabled). For more information, see Adding Backup Repository Extents.

2. Backup placement policy set for the scale-out backup repository.

3. Load control settings — maximum number of tasks that the extent can process simultaneously.

IMP ORTANT

If a Services Provider uses an extent as a cloud repository, Veeam Backup & Replication compares the
percentage of active tasks over the extent task limit and selects the extent with the least load over
the extent. For example, if the A extent tasks limit is 5 tasks, and currently 3 tasks are active, and the
B extent tasks limit is 30 tasks, and 10 tasks are currently running, Veeam Backup & Replication
selects the B extent. If there are several extents with equal percentage values,
Veeam Backup & Replication checks a disc space and selects the best suitable extent b ased on this
check. For example, if there are extents with the same percentage of running tasks,
Veeam Backup & Replication compares their disk space and selects the extent with the least disk
space occupied.

4. Amount of free space available on the extent — the backup file is placed to the extent with the most
amount of free space.

5. Availability of files from the current backup chain — extents that host incremental backup files from the
current backup chain (or current VM) have a higher priority than ex tents that do not host such files.

Extent Selection for Backup Repositories with Performance Policy


If you set the Performance policy for the scale-out backup repository, Veeam Backup & Replication always
stores full backup files and incremental backup files that belong to the same backup chain on different extents.
To choose the extent to which a backup file can be stored, Veeam Backup & Replication applies this policy and
policies mentioned above.

For example, a scale-out backup repository has 2 extents that have 100 GB and 200 GB of free space. You set
the Performance policy for the scale-out backup repository and define that all types of backup files (full and
incremental) can be placed on both extents.

When a backup job runs, Veeam Backup & Replication picks the target extent in the following manner:

1. During the first job session, Veeam Backup & Replication checks to which extent a full backup file can be
stored. As both extents can host the full backup file, Veeam Backup & Replication checks which extent has
more free space, and picks the extent that has 200 GB of free space.

1043 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. During incremental job session, Veeam Backup & Replication checks to which extent an incremental
backup file can be stored. As both extents can host the incremental backup file,
Veeam Backup & Replication picks the extent that does not store the full backup file — the extent that has
100 GB of free space.

Extent Selection for Object Storage Repositories Added as Performance Extents


If you add an object storage repository as a performance extent, neither data locality nor performance policies
are applied to these extents. Instead, Veeam Backup & Replication uses multiple conditions to distributes data
between extents. Data distribution depends on whether it is the first move or a subsequent move of a backup
chain.

To select an extent for backup file placement, Veeam Backup & Replication checks the following conditions:

1. During the first job session, Veeam Backup & Replication checks availability of extents. In case, an extent
is set to Sealed or Maintenance mode, these extents will be skipped from backup file pla cement.

2. After that, Veeam Backup & Replication checks the amount of backup chains in available extents and
selects the extent with a minimal amount of backup chains.

3. If some extents have storage space limitations, Veeam Backup & Replication calculates the average
storage of the backup chains located in all extents and select the extent that contains a minimum amount
of backup chains. If all extents have the same number of backup chains, Veeam Backup & Replication
selects the extent that has more free space.

4. During subsequent job sessions, Veeam Backup & Replication moves backup chains to the extent that was
specified before.

NOTE

If an extent is set to Sealed mode or Maintenance mode, Veeam Backup & Replication will not move
a backup chain to this extent. In this case, a new extent is selected and Veeam Backup & Replication
follows the same algorithm as during the first job session. The backup chain located in an unavailable
extent will be moved again to another extent. Veeam Backup & Replication will remove backup
chains from the unavailable extents according to retention policy.

Backup Size Estimation


At the beginning of a job, Veeam Backup & Replication retrieves the actual free space on a scale-out backup
repository and estimates the size of a restore point to be created. Then the estimated restore point size is
subtracted from the actual free space to determine the estimated free space. This estimated free space is then
used by all further concurrently running jobs targeted at the same scale-out backup repository.

Veeam Backup & Replication assumes that the following amount of space is required for backup files:

• The size of the first full backup file is equal to 50% of source VM data.

• The size of further full backup files is equal to 100% of the previous full backup file size.

• The size of the first incremental backup file is equal to 10% of the previous full backup file size.

• The size of further incremental backup files in the backup chain is equal to 100% of the previous
incremental backup file size.

In case of reverse incremental backup chains, during incremental job sessions Veeam Backup & Replication
allocates 10% of the previous full backup file size on the extent where a rollback file is placed and
additional 10% on the extent where the full backup file resides.

1044 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
This mechanism is also applied to backup files created by backup copy jobs.

NOTE

Consider the following:

• On every extent of a scale-out backup repository, Veeam Backup & Replication reserves 1% of
storage space to guarantee correct update of backup metadata files (VBM) and success of merge
operations.
• Make sure that you have enough free space on the extent where the full backup file resides.
Veeam Backup & Replication requires 10% of the size of the full backup file to perform merge
operations in the backup chain. If the disk space is low, merge operations may fail.
• The actual free space value is only captured at the start of a job targeted at the scale -out backup
repository while no other jobs actively use the same scale-out backup repository. For more
information, see the Veeam KB2282 article.

Immutability for Performance Tier


Veeam Backup & Replication allows you to prohibit deletion of data from the repositories added as a
performance extent by making that data temporarily immutable. It is done for increased security: immutability
protects your data from loss as a result of attacks, malware activity or any other injurious actions.

You can enable immutability for the following types of repositories:

• Amazon, S3-compatible and Azure object storage repositories. For more information, see Immutability for
Object Storage Repositories.

• Hardened Repository. For more information, see Hardened Repository.

• HPE StoreOnce. For more information, see Immutability for HPE StoreOnce.

The immutable data within the performance extent cannot be subject to the following operations:

• Manual removal of data, as described in section Deleting Backups from Object Storage.

• Removal of data by the retention policy, as described in section Retention Policy.

• Removal of data using any cloud service provider tools.

• Removal of data by the cloud service provider technical support department.

• Removal of data by the Remove deleted items data after option, as described in section Maintenance
Settings.

Immutability for Backup Object Storage Repositories Added as


Performance Extents
Immutability settings for the following types of backups files depends on a configuration of a scale -out backups
repository:

• Backups with GFS flags.

• Backups created by VeeamZIP jobs.

• Exported backup files.

1045 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Consider the following scenarios:

• If retention policy configured for these backup files exceeds immutability settings,
Veeam Backup & Replication applies retention that is defined for these types of backups. Immutability
settings defined for an object storage repository are ignored.

• If you do not add a capacity tier or archive tier to your scale-out backup repository,
Veeam Backup & Replication follows retention policy configured for these files in case it exceeds
immutability settings. Immutability settings defined for an object storage repository are ignored.

• If you add a capacity tier to your scale-out backup repository and select move backups to capacity tier,
immutability is set according to the object storage repository settings. Retention policy for these backups
files is ignored. Note that data blocks are deleted from the performance tier once the immutability period
for the performance tier ends.

Block Generation
To reduce I/O operations and associated costs, Veeam Backup & Replication will automatically add 10 days to
the immutability expiration date. This period is called Block Generation. You do not have to configure it, the
Block Generation setting is applied automatically. For example, if you set your immutability period to 30 days
for your object storage repository, Veeam Backup & Replication will add 10 days to specific objects to reduce I/O
operations with the data blocks over time. Thus, you will have immutability set for 30 days + 10 days of Block
Generation set for data blocks in your object storage repositories.

How Block Generation Works


When the first data block (a full backup) arrives, its immutability period by def ault is set to 30 + 10 = 40 days.
The first full backup starts its generation, that will be appended with the incremental backups. All the
incremental backups within the generation (that is, within the 10-days period) will have the same immutability
expiration date as the full backup. For instance, a data block that was offloaded on day 9 will have the same
immutability expiration date as a data block offloaded on day 1. Thus we ensure that the immutability period for
all the data blocks within a generation is no less than 30 days.

To maintain the backup consistency, Veeam Backup & Replication can extend immutability expiration for all data
blocks in the backup chain and assign these blocks to a new generation.

For example, within one forward incremental backup chain, a full backup file can not be removed before an
incremental backup file. On the other hand, an incremental backup file makes no sense without relevant full
backup file. So the immutability period is extended for all data blocks in the backup chain.

With 10 days of immutability automatically added, it means there is no need to extend the immutability period
for the incremental backups in forward chain and for the unchanged blocks of current full backups in reverse
chain offloaded within those 10 days. On the 11th day, though, the immutability period will have to be extended
(to ensure that the immutability period for all the data blocks within a generation is no less than 30 days).

NOTE

Consider the following:

• For data blocks located in object storage repositories, Veeam Backup & Replication extends
immutability period for every data block of every backup file in the whole backup chains, even in
inactive part.
• Veeam Backup & Replication will not extended immutability for the data blocks that a re not used in
any exiting backup files.

1046 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Transferring Backups to Performance Tier
Prior to Veeam Backup & Replication version 12, it was possible to keep data only on object storage repositories
added as capacity extents of scale-out backup repository. Starting from Veeam Backup & Replication version 12,
it is possible to add an object storage repository as a performance extent and back up data directly to this
extent.

In case, you have an object storage repository that is added as a capacity extent and wa nt to use it as a
performance extent, you might want to transfer existing backup from the capacity extent to the performance
extent.

To do this, you must perform the followings steps:

1. Add a new object storage repository to the backup infrastructure.

2. Download a necessary backup chain to the existing backup repository added as a performance extent. For
more information, see Downloading Data from Capacity Tier.

3. Move backups from the backup repository to a new object storage repository. For more information, see
Moving Backups.

4. Add the object storage as a performance extent to a new scale-out backup repository.

Removing Performance Extents from Scale-Out Repositories


You can remove a performance extent from the scale-out backup repository, for example, if you do not want to
store backup files on the underlying storage anymore. When you remove a performance extent,
Veeam Backup & Replication puts the relevant backup repository to the Maintenance mode and unassigns the
performance extent role from it. The backup repository ceases to exist as a part of the scale -out backup
repository and becomes an individual backup repository.

If the performance extent contains backup files, it is strongly recommended that you perform the following
actions before you remove the extent:

1. Put the performance extent to the Maintenance mode.

2. Evacuate backups from the extent. For more information, see Evacuating Backups from Performance
Extents.

In this case, backup files will be moved to other performance extents of the scale -out backup repository, and
the backup chain will remain consistent. If you do not evacuate backups from the performance extent, the
backup chain may get broken as some restore points will be missing from it.

To remove a performance extent from the scale-out backup repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Sca le-out Repositories.

3. In the working area, select the scale-out backup repository and click E d it Scale-out Repository on the
ribbon or right-click the scale-out backup repository and select P roperties.

4. Move to the P erformance tier step of the wizard.

5. In the E x tents list, select the performance extent and click Remove.

If the performance extent contains backup files, Veeam Backup & Replication will suggest evacuating them. To
evacuate files, click No, close the wizard and evacuate backup files. For more information, see Evacuating
Backups from Performance Extents.

1047 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you do not want to evacuate the backup files, click Y es and proceed with the wizard.

1048 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Capacity Tier
Capacity tier is an additional tier of storage that can be attached to a scale-out backup repository. Data from the
scale-out backup repository performance extents can be transported to the capacity tier for long -term storage.

This feature is most useful in the following cases:

• You are running out of storage space.

• Your organization policies allow you to store only a certain amount of data on your extents, while the
outdated data should be stored elsewhere.

• You seek to store data on several sites to ensure its safety in case of a disaster.

With capacity tier, you can perform the following operations:

• Move inactive backup chains to capacity extents, as described in section Moving Backups to Capacity Tier
and Manually Moving Backups to Capacity Tier.

• Copy new backup files as soon as these files are created, as described in section Copying Backups to
Capacity Tier.

• Download data that was moved from capacity extents back to the performance extents, as described in
section Downloading Data from Capacity Tier.

• Restore your data. For more information, see Restore from Capacity Tier. In particular, you can promptly
restore data from the capacity tier in case of disaster without creating a scale-out backup repository anew.
For more information about this feature, see Importing Object Storage Backups.

The capacity tier consists of multiple capacity extents. The capacity extent can be either a cloud -based object
storage repository or on-premises object storage repository, such as:

• S3-compatible object storage repository

• Amazon S3

• AWS Snowball Edge

• Microsoft Azure Blob storage

• Microsoft Azure Data Box

• IBM Cloud Object Storage

• Google Cloud Object Storage

• Wasabi Cloud Object Storage

Before an object storage repository can be configured as the capacity extent, it must be adde d to
Veeam Backup & Replication. For more information, see Adding Object Storage Repositories.

The capacity extents are displayed in the scale-out backup repository wizard, on the Capacity Tier step.

For information on configuring capacity tier and synchronizing capacity tier data, see Add Capacity Tier.

1049 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations for Capacity Tier
Consider the following limitations for capacity tier:

• You can add only one type of object storage repository as a capacity extent. For example, if your first
added Microsoft Azure Blob object storage as a capacity extent, you cannot add Amazon S3 object storage
as a second capacity extent.

• You cannot add more than one instance of Azure Databox or Snowball Edge AWS object storage repository
as a capacity extent.

• Before you start using the capacity tier, make sure to check the pricing plans of your cloud storage
provider to avoid additional costs for offloading and downloading backup data.

• Downloading or restoring data from capacity tier does not reuse the existing blocks present on
performance tier if performance tier consists of object storage repositories.

• Full restore points downloaded from capacity tier to ReFS or XFS performance extents do not use Fast
Clone.

• If you use immutability and have several extents in your capacity tier, you must enable it for all extents
within this tier. You cannot use mixed configuration and have only one extent with immutability enabled.

• You cannot use the same object storage repository as a performance extent and as a capacity extent.

Capacity Extent Structure


When data is transferred to the capacity extent, Veeam Backup & Replication creates and maintains the
following structure of directories:

Directory Description Misc

< b ucket_name> or A bucket or container name. N/A


< container_name> Buckets and containers must be created in advance.

Veeam/Archive/ Standard folders created by


Veeam Backup & Replication.

1050 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Directory Description Misc

< FolderName> A repository folder that you create when adding a new
capacity extent.

< Ba ckup_id> Contains objects in a backup. These folders are


automatically removed
during data removal.
< Index_Id> An identifier of an object in a backup.

• If a backup was created using the per-machine


method, then each VM will be placed to its own
directory.
• If a backup was created as a single-file backup,
then all the VMs will be placed to a unique
directory.

Checkpoints Contains meta information about the state of


offloaded backup chains. Such meta information is
updated upon each successful offload session.

Da ta.v2 Contains data blocks and metadata related to these


blocks.

internalCheckpoints Auxilliary checkpoints. Contain information on backup


files and metadata.

ob js Contains meta information and other auxiliary data.

Backup File Placement for Capacity Tier


Data distribution between capacity extents depends on whether it is the first move or a subsequent move of a
backup chain. To select an extent for backup file placement, Veeam Backup & Replication checks the following
conditions:

1. During the first job session, Veeam Backup & Replication checks availability of extents. In case, an extent
is set to Sealed or Maintenance mode, these extents will be skipped from backup file placement.

2. After that, Veeam Backup & Replication checks the amount of backup chains in available extents and
selects the extent with a minimal amount of backup chains.

3. If some extents have storage space limitations, Veeam Backup & Replication calculates the average
storage of the backup chains located in all extents and select the extent that contains a minimum amount
of backup chains. If all extents have the same number of backup chains, Veeam Backup & Replication
selects the extent that has more free space.

4. During subsequent job sessions, Veeam Backup & Replication moves backup chains to the extent that was
specified before.

1051 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If an extent is set to Sealed mode or Maintenance mode, Veeam Backup & Replication will not move
a backup chain to this extent. In this case, a new extent is selected and Veeam Backup & Replication
follows the same algorithm as during the first job session. The backup chain located in an unavailable
extent will be moved again to another extent. Veeam Backup & Replication will remove backup
chains from the unavailable extents according to retention policy.

Immutability for Capacity Tier


Veeam Backup & Replication allows you to prohibit deletion of data from capacity extents by making that data
temporarily immutable. It is done for increased security: immutability protects your data from loss as a result of
attacks, malware activity or any other injurious actions.

You can enable immutability for data stored in Amazon, S3-compatible and Azure object storage repositories
used as capacity extents of the scale-out backup repository. After you enable immutability,
Veeam Backup & Replication will prohibit data deletion from capacity tier until the immutability expiration date
comes.

Backups are immutable only during the immutability period set in the object storage repository settings even if
their retention policy allows for longer storage. Immutability retention policy ignores retention policies set for
the following types of backups:

• Backups with GFS flags

• Backups created by VeeamZIP jobs

• Exported backup files

The immutable data within the capacity extents cannot be subject to the following operations:

• Manual removal of data, as described in section Removing Backups from Capacity Tier.

• Removal of data by the retention policy, as described in section Retention Policy.

• Removal of data using any cloud service provider tools.

• Removal of data by the cloud service provider technical support department.

• Removal of data by the Remove deleted items data after option, as described in section Maintenance
Settings.

TIP

There are two ways to migrate your data from a mutable bucket to an immutable one. For more
information, see section Migrating Data Between Different Buckets.

Enabling Immutability
To enable immutability, you must do the following:

1. Configure the necessary settings when you create an S3 bucket or an Azure container.

For more information, see Preparing to Use Immutability.

1052 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Enable the immutability option when you add an object storage repository to the backup infrastructure at
the Container step (for Azure object storage repository) or Buck et step (for Amazon S3 or S3 compatible
object storage repositories) of the new Ob ject Storage Repository wizard.

Block Generation
To reduce I/O operations and associated costs, Veeam Backup & Replication will automatically add 10 days to
the immutability expiration date. This period is called Block Generation. You do not have to configure i t, the
Block Generation setting is applied automatically.

For example, if you set your immutability period to 30 days, Veeam Backup & Replication will add 10 days to
specific objects to reduce I/O operations with the storage over time. This will not change the retention and their
effective immutability. It is a background optimization. Thus, if you need 30 days immutability period, set the
period to 30 days.

How Block Generation Works


Block Generation works in the following way. When the first data block (a full backup) arrives, its immutability
period is set to 30 + 10 = 40 days. The first full backup starts its generation, that will be appended with the
incremental backups. All the incremental backups within the generation (that is, within the 10 -days period) will
have the same immutability expiration date as the full backup. For instance, a data block that was offloaded on
day 9 will have the same immutability expiration date as a data block offloaded on day 1. Thus we ensure that
the immutability period for all the data blocks within a generation is no less than 30 days.

Consider this example: within one forward incremental backup chain, a full backup file can not be removed
before an incremental backup file. On the other hand, an incremental backup file makes no sense without
relevant full backup file. So the immutability period is extended for all data blocks in the backup chain.

The Block Generation period was introduced in order to reduce the number of requests to the capacity tier,
thereby saving traffic and reducing costs that might be incurred by your storage provider. With 10 days of
immutability automatically added, it means there is no need to extend the immutability period for the
incremental backups in forward chain and for the unchanged blocks of current full backups in reverse chain
offloaded within those 10 days. On the 11th day, though, the immutability period will have to be extended (to
ensure that the immutability period for all the data blocks within a generation is no less than 30 days).

The immutable blocks of data may be reused during the offload. Veeam Backup & Replication continues to keep
reused or dependent blocks of data locked by continuously assigning them to new generations, thereby
extending their immutability expiration period. This is valid both for forward and reverse incremental backup
chains.

The extension of immutability works differently in different cases:

Forward incremental backup chain


• New full backup file in the new generation:

o Immutability is extended for the data blocks that are being reused from the old backup chain.

o Immutability is set anew for the new blocks of the new full backup file.

• New incremental backup file in the new generation:

o Immutability is extended for all the data blocks from the current ba ckup chain.

o Immutability is set anew for the new blocks of the latest incremental backup file.

1053 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Reverse incremental backup chain
• New full backup file in the new generation:

o Immutability is extended for the data blocks that are being reused from the previous full backup file.

o Immutability is set anew for the new blocks of the new full backup file.

• Current full backup file in the new generation:

o Immutability is extended for all the data blocks of this full backup file that are already stored in t he
capacity tier.

o Immutability is set anew for the new blocks of this full backup file.

Encryption for Capacity Tier


Veeam Backup & Replication allows you to encrypt offloaded data. This helps you protect the data from an
unauthorized access.

You can enable data encryption in the following ways:

• When you create a backup or backup copy job

• When you add a capacity tier extent to your scale-out backup repository

To get benefits of both encryption levels, you can use job-level and capacity tier encryption within the same
object storage. Both encryption levels allow you to keep your data from an unauthorized access, but capacity
tier encryption allows you to encrypt backup chain metadata and restore points.

Job-level Encryption
Before data is offloaded to capacity tier, Veeam Backup & Replication checks if encryption is enabled in the job
settings. If encryption is enabled, data encrypted by the job is not decrypted or decompressed. It is offloaded to
capacity tier as is.

Capacity Tier Encryption


With the E ncrypt data uploaded to object storage setting selected, the entire collection of blocks along with the
metadata will be encrypted while being offloaded regardless of the jobs’ encryption settings . If you have both
job-level and capacity tier encryption enabled, already encrypted backup data will be encrypted again before
being uploaded to capacity tier.

If capacity tier encryption has been disabled, backup data encrypted by the job settings will be uploaded
unmodified to capacity tier.

NOTE

Consider the following:

• Make sure you enable encryption when you add a capacity tier extent. Otherwise, unencrypted
backups, offloaded to capacity tier, may be reused for synthetic backup creation.
• If you enable encryption after you have already offloaded data to capacity tier,
Veeam Backup & Replication will not encrypt previously offloaded backup chains.

1054 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Health Check for Capacity Tier
NOTE

This feature is available starting from Veeam Backup & Replication 12.1 (build 12.1.0.2131).

A health check is an operation that allows to ensure that the restore point is consistent, and you will be able to
restore data from this restore point. For data located in the capacity tier, Veeam Backup & Replication offers a
special health check mechanism that differs from the standard health check in the following ways:

• The health check for capacity tier verifies metadata for the whole backup, not just the latest restore point.

• The health check for capacity tier verifies that data blocks are present on capacity extents of a scale -out
backup repository. It does not read data from data blocks. Instead, it lists data blocks to make sure all
blocks in the object storage are available for rebuilding every restore point in the backup chain.

If some blocks are missing, Veeam Backup & Replication marks these blocks and restore points associated with
them as corrupted. It will prevent Veeam Backup & Replication from reusing the corrupted blocks in certain
operations. Instead, Veeam Backup & Replication will upload these blocks to the capacity extent again during
the offload session.

If health check detects metadata corruption, Veeam Backup & Replication will mark all backup chain as
corrupted. In this case, you will not be able to restore from this backup chain and Veeam Backup & Replication
will prevent all offload sessions for the corrupted backup chain. To add a new backup chain to the capacity tier,
you must either delete the corrupted backup chain from capacity tier or detach the backup from a backup job.

NOTE

By default, Veeam Backup & Replication uses local resources to perform the health check. The type of the
local resource depends on the connection mode of the object storage repository added as a capacity
extent:

• For direct connection mode — Veeam Backup & Replication will use a mount server to perform the
health check.
• For gateway server connection mode — Veeam Backup & Replication will use a gateway server to
perform the health check.

1055 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, the health check runs monthly every last Saturday and runs during the offload session after backup
cleanup completes. You can change the schedule and run the health check weekly or monthly on specific days in
the scale-out backup repository settings.

How Health Check for Capacity Tier Works


Veeam Backup & Replication performs the health check of a backup in the following way:

1. Veeam Backup & Replication starts the health check of the whole backup during the first offload session
on the scheduled date. Veeam Backup & Replication checks if the metadata of the backup is consistent and
no metadata is missing. Veeam Backup & Replication also checks if all data blocks for every restore point
are available on the capacity extent. Veeam Backup & Replication does not read data from data blocks.

2. If Veeam Backup & Replication does not find any corrupted data, the health check completes successfully.

If Veeam Backup & Replication detects corrupted data, the health check completes with an error.
Depending on the detected data inconsistency, Veeam Backup & Replication behaves in one of the
following ways:

o If the health check detects corrupted metadata, the offload session fails. Veeam Backup & Replication
will mark all backup chain as corrupted and prevents all offload sessions for the corrupted backup
chain. To add a new backup chain to the capacity tier, you must either delete the corrupted backup
chain from capacity tier or detach the backup from a backup job.

o If the health check detects missing data blocks, Veeam Backup & Replication marks these blocks and
restore points associated with them as corrupted. Veeam Backup & Replication will upload these
blocks to the capacity extent again during the offload session.

You can view the health check result in the restore point statistics. If the health check finds corrupted
data, it will display information on it, as well as list all restore points that share the corrupted data blocks.

1056 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

For immutable backups, Veeam Backup & Replication performs the health check only for valid restore
points according to the retention policy. Immutable data associated with removed restore points can still
remain in the repository depending on the immutability period, but Veeam Backup & Replication will not
perform the health check for such data.

Managing Capacity Tier


You can manage your capacity tier and the offloaded data in the following ways:

• Download previously offloaded data from the capacity extent back to the performance extents.

• Migrate data to another capacity tier.

• Reduce the number of cost-based operations incurred by your cloud storage provider and decrease the
amount of traffic being sent over the network when moving or copying data to the capacity tier. For more
information, see Indexes.

• Configure the retention policy.

• Exclude the capacity extents from the scale-out backup repository scope.

Data Transfer
Veeam Backup & Replication allows you to transfer data to and from capacity extents, as well as move data from
capacity extents to archive extents.

You can perform the following data transfer operations:

• Copy policy: the backups are copied to capacity extents automatically.

• Move policy: the inactive backup chains can be transferred to the capacity extents.

• Previously offloaded data can also be downloaded from the capacity tier back to the performance extents.

To manage data transfer to and from capacity extents, Veeam Backup & Replication uses system sessions.

The following types of backup files can be moved or copied to capacity extents:

• Regular backups (except transaction logs)

• Veeam backups for Amazon, Google and Microsoft Azure (using backup copy jobs)

• Backups created with Veeam Agent for Microsoft Windows, Veeam Agent for Linux, Veeam Agent for Unix
or Veeam Agent for Mac

• Backups created with Veeam Plug-ins for Enterprise Applications (Oracle RMAN, SAP HANA, SAP on
Oracle)

• Backups created with Veeam Backup for Nutanix AHV

• Backups created with Veeam Backup for Red Hat Virtualization

• Backups created with VeeamZIP jobs

• Backups exported by K10 policies

• Exported backup files

1057 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Orphaned backups

NOTE

Consider the following:

• Imported backups can be copied or moved to capacity extents only manually.


• You can move only inactive backup chains to capacity extents.

In This Section
• Copying Backups to Capacity Tier

• Moving Backups to Capacity Tier

• Manually Moving Backups to Capacity Tier

• Downloading Data from Capacity Tier

• Viewing Capacity Tier Sessions Statistics

Copying Backups to Capacity Tier


Veeam Backup & Replication allows you to copy backups from the performance extents of your scale-out backup
repository to capacity extents as soon as these backups are created.

To enable data copy, make sure to select the Cop y backups to object storage as soon as they are created option,
as described in section Add Capacity Tier.

To copy data to capacity extents, Veeam Backup & Replication performs the following steps:

1. Veeam Backup & Replication verifies that performance extents are available and are not in the
Maintenance mode.

2. After a backup (or backup copy) job that is targeted to capacity extents of a scale-out backup repository
finishes, Veeam Backup & Replication initiates a copy session.

A complete name of each copy session consists of the backup (or backup copy) job name plus the Offload
postfix. That is, if your backup (or backup copy) job name is Amazon, the copy session name will be
Amazon Offload .

3. During a copy session, Veeam Backup & Replication extracts data blocks and metadata from each new
backup file (.VBK, .VIB, .VRB) or data blocks created on performance extents and copies these blocks and
metadata to capacity extents.

Backup files with metadata are created as described in section Moving Backups to Capacity Tier.

Having such replica gives you the ability to quickly restore data as of the latest state in case of trouble with any
backup files, any unexpected failure of any of your performance extents, or even of the entire scale -out backup
repository, as described in section Restore Scenarios.

Combining Copy and Move Operations


You can combine both the Cop y backups to object storage as soon as they are created option and the Move
b a ckups to object storage as they age out of the operational restores window option. In such a scenario, a copy
session will be copying newly created backups right upon creation.

1058 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Once the backup chain becomes inactive (for example, sealed) and exceeds the operational restore window,
data blocks will be removed from each associated backup file in such an inactive backup chain and only
metadata will be preserved. Such a behavior mimics data movement, but instead of moving data that was
already copied, Veeam Backup & Replication purges associated data blocks from the performance extents,
thereby saving traffic and reducing costs that may be incurred by your storage provider for performing
read/write operations.

The following figure shows an example in which both options are enabled, suggesting that each backup file has
been copied to object storage upon its creation.

The backup chain on the left becomes inactive after a new full backup file is created and consists of one .VBK
file and five .VIB files. Since only the first four backup files (represented as grey blocks) in this inac tive backup
chain exceed the operational restore window, Veeam Backup & Replication removes blocks of data from these
four files only and leaves the other two .VIB files (created on Thursday and Friday ) as they are until the
operational restore window moves forward, and so on.

After copy is complete, the new Ca pacity Tier node appears in the Home view, under the Ba ckups node and
shows backups that have been copied to the capacity extent.

NOTE

The copy is not performed during prohibited hours specified in the scale-out backup repository backup
window configuration. You can configure the backup window at the Add Capacity Tier step of the New
Sca le-out Backup Repository wizard.

Moving Backups to Capacity Tier


To collect backup files that belong to inactive backup chains from the performance extents and move them to
the capacity tier, Veeam Backup & Replication uses an offload session which is executed automatically every 4
hours.

To enable data movement, make sure to select the Move backups to object storage as they age out of the
op erational restores window option, as described in the Add Capacity Tier section.

A complete name of each offload session is built up of the scale-out backup repository name plus the Offload
postfix. That is, if your scale-out backup repository name is Amazon, the offload session name will be Amazon
Offload .

The offload session manages the following:

• Validation Process

• Data Transfer

1059 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Validation Process
Before your data can safely be moved to the capacity tier, Veeam Backup & Replication performs the following
mandatory verifications and required actions:

• Verifies whether data that is about to be moved belongs to an inactive backup chain.

For more information, see Backup Chain Detection.

• Verifies whether performance extents are available and have not been put into the Maintenance mode.

IMP ORTANT

Veeam Backup & Replication does not offload data from Linux-based performance extents that have
internet access through HTTP(S) proxy. All Linux-based performance extents configured in your
scale-out backup repository must have direct access to the internet.

• Verifies whether the capacity extents have not been put into the Maintenance or the Sealed mode.

For more information, see Switching to Maintenance Mode and Switching to Sealed Mode.

• Verifies whether configuration parameters that define how and when inactive backup chains must be
moved to capacity extents are met.

Such parameters are configured as described in section Add Capacity Tier.

• Synchronizes the backup chain state between the performance and capacity extents to maintain retention
policies.

For more information, see Retention Policy.

Data Transfer
After the validation process is complete, the SOBR Offload session collects backup files that have passed
verification. Such verified backup files are collected from all the performance extents added to a scale -out
backup repository.

The performance extent A has an inactive backup chain consisting of one VBK file and three VIB files, that is,
four restore points in total. Each of these files comprises metadata and the actual blocks of data. During the
offload session, Veeam Backup & Replication will collect the actual blocks of data from all the back up files (VBK
and VIB) and offload these blocks to the object storage repository.

Each offloaded block may be of different size, which is defined during configuring storage optimization. The
offloaded blocks are placed to the blocks directory in your capacity extents.

Such approach will be applied to all inactive backup chains that satisfy validation criteria.

After offload is complete, the new Ca pacity Tier node appears in the Home view, under the Ba ckups node and
shows backups that have been moved to capacity extents.

NOTE

The offload is not performed during prohibited hours specified in the scale-out backup repository backup
window configuration. You can configure the backup window at the Add Capacity Tier step of the New
Scale-out Backup Repository wizard.

1060 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Offload Session Statistics
The offload session results are saved to the configuration database and available for viewing, as described in
section Viewing Offload Job Session Results.

Backup Chain Detection


Veeam Backup & Replication will transfer to capacity extents only those restore points that belong to inactive
backup chains. To ensure a backup chain is inactive, Veeam Backup & Replication verifies its state. This does not
apply to the copy policy: all newly created restore points are copied immediately.

When a backup job runs for the first time, Veeam Backup & Replication creates an initial full backup file. It
contains complete information about the VMs that are being backed up. With each subsequent backup job
session, new incremental backup files are created. They contain only the changes that have occurred since the
last backup session.

For forward incremental backup method, the active backup chain is the one that has not yet been sealed with a
new full backup file.

To transform an active backup chain into inactive, a new active full (or synthetic full) backup file must be
created for this chain. This can be done either manually, as described in section Performing Active Full Backup.
Else, you can configure a schedule according to which new active or synthetic full backups will be created
automatically, as described in sections Active Full Backup and Synthetic Full Backup.

Once a new full backup file is created and the offload session is being executed, Veeam Backup & Replication
collects all the restore points (full and incremental) that were created prior to the latest active full, verifies that
they belong to an inactive chain, and prepares them to be moved to capacity extents. This process is called
detect. For more information, see Moving Backups to Capacity Tier.

The same applies to backup chains created by backup copy jobs. Veeam Backup & Replication will transfer to
capacity extents only those restore points that belong to an inactive backup copy chain. Note that if you enable
backup copy GFS, Veeam Backup & Replication implements the forward incremental retention policy. If you
disable backup copy GFS, Veeam Backup & Replication implements the forever forward incremental retention
policy.

Note that Veeam Backup & Replication will not transfer to the capacity tier the corrupted restore points and the
files dependent on those. For more information on the corrupted restore points, see Health Check for Backup
Files.

The same applies to the backup chains created with the reverse-incremental method. In this case, all the .VRB
files starting from the third restore point will be considered inactive automatically. Thus, you do not need to
create an active full (nor synthetic full) backup manually unless you want to offload all the restore points
including the most recent .VBK file and the first two .VRB files.

Consider the following examples:

• Four VRB files are inactive and can be offloaded:

1061 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Six VRB files and a VBK file belong to an inactive chain and can be offloaded:

NOTE

A full backup file and the first two incremental backup files (that is, two .VRB files that immediately follow
the most recent .VBK file) will not be offloaded until another full backup file is created successfully.

The structure of the backup chains can be different. That depends on whether your backups were created using
the per-machine method (for more information, see Backup Chain Formats) or as a single-file backup, with all
VMs placed into a single file. The type of the backup chain structure does not a ffect the offload process.

For more information on how Veeam Backup & Replication creates and manages backup chains, see Backup
Chain.

Manually Moving Backups to Capacity Tier

The Move to capacity tier option allows you to manually offload selected backup files to capacity extents.

Consider that backup files you want to offload must belong to an inactive backup chain. For more information,
see Backup Chain Detection.

To move backup data to capacity tier, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups > Disk node (for backup repositories) or Ba ckup > Ob ject Storage
(for object storage repositories) node.

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

4. In the P roperties window, right-click a backup file that you want to offload and select Move to capacity
tier.

Alternatively, you can use the Move to capacity tier control at the bottom.

5. Select the necessary backup file and specify the offload options:

o This backup a nd its dependencies — to offload the selected incremental backup file (VIB) and all
increments related to it.

o This backup — to offload the selected full backup file (VBK) only.

1062 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o This backup a nd all dependent increments — to offload the selected full backup file (VBK) along with
its increments.

Downloading Data from Capacity Tier


In Veeam Backup & Replication, you can manually download offloaded backups back to the performance
extents.

You can download one backup at a time using the Cop y to Performance Tier option, or get all offloaded backups
in bulk using the Download feature. For more information, see Downloading Single Backup Chain and
Downloading All Backups.

For more information, see How Downloading from Capacity Tier Works.

Downloading Single Backup Chain


To download previously offloaded backup data back to the performance extents, one backup at a time, do the
following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Ba ckups > Capacity Tier node.

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

4. In the P roperties window, right-click an offloaded backup file and select Cop y to performance tier.

Alternatively, you can use the Cop y to performance tier control at the bottom.

5. Select either of the following options:

o For VIB/VBK backup files:

1063 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ This backup a nd all dependent increments — to copy the selected backup along with its
increments.

o For VBK backup files:

▪ This backup — to copy the full backup only.

▪ This backup a nd all dependent increments — to copy the selected backup along with its
increments.

NOTE

To remove copied blocks from the performance extents, use the Move to capacity tier option, as described
in section Moving Inactive Backup Chains to Capacity Tier.

Downloading All Backups


To download all offloaded backups back to the performance extents, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups > Capacity Tier node.

3. On the ribbon, click Download or in the working area, right-click a backup job and select Download.

o If the latest backup chain is already present on your performance extent, you will be asked if you wish
to download all other backup files. Click Y es if you wish to do so or No to cancel the download.

o If the latest backup chain is not on your performance extent yet, you will be asked which backup files
you want to download. Click All Backups to download all backup files or La test Only to download just
the latest backup chain.

NOTE

To remove downloaded data from the performance extents, use the Move to capacity tier option, as
described in section Moving Inactive Backup Chains to Capacity Tier.

1064 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
How Downloading from Capacity Tier Works

To download data from the capacity extent back to the performance extents, Veeam Backup & Replication uses
the SOBR Download job.

The SOBR Download job is triggered right after you select the Cop y to performance tier option; it collects
offloaded blocks of data from capacity extents and copies them back to the performance extents. For more
information, see Downloading from Capacity Tier.

Consider the following:

• Veeam Backup & Replication copies all data blocks directly from object storage repositories added as
extents to capacity tier.

• If a performance extent is unable to accommodate copied data due to lack of free storage space,
Veeam Backup & Replication will find another extent in the associated scale-out backup repository that
has sufficient storage capacity to receive the data. If your scale-out backup repository has no performance
extents other than the one running out of space, the copy will not be possible.

• If you have removed any of the performance extents from a scale-out backup repository without
evacuating backup files with metadata, the copy will not be possible until the files with metadata are
downloaded back to the performance extents in the course of the rescan process. For more information on
the rescan process, see Rescanning Scale-Out Repositories.

Backup files with metadata are created as described in section Moving Inactive Backup Chains to Capacity
Tier.

• The SOBR download session results are saved to the configuration database and available for viewing, as
described in section Viewing Download Job Session Results.

Viewing Capacity Tier Sessions Statistics

Veeam Backup & Replication allows you to perform the following actions:

• View Offload Session Results.

• View Copy Session Results.

1065 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• View Download Session Results.

Viewing Offload Session Results


To review offload session results, do the following:

1. Open the History view.

2. In the inventory pane, select the Storage management node.

3. In the working area, right-click an offload session and select Sta tistics.

For more information, see Moving Inactive Backup Chains to Capacity Tier.

Veeam Backup & Replication displays offload job session statistics for the following counters:

• The Job progress bar shows percentage of the offload session completion.

• The Summary box shows general information about the offload session:

o Duration — duration of the offload session.

o P rocessing rate — average speed of VM data processing. This counter is a ratio between the amount of
data that has actually been read and the offload session duration.

o Bottleneck — bottleneck in the data transmission process. To learn more about bottlenecks, see
Performance Bottlenecks.

• The Da ta box shows information about processed data:

o P rocessed — total size of all VM disks processed by the offload session.

o Rea d — the amount of data read from from the performance tier to the capacity tier.

o Tra nsferred — the amount of data transferred from performance tier to capacity tier.

• The Sta tus box shows information about the job results. This box informs how many tasks have completed
with the Success, Warning and Error statuses (1 task per 1 VM).

• The pane in the lower-left corner shows a list of objects processed by the offload session.

1066 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The pane in the lower-right corner shows a list of operations performed during the session. To see a list of
operations for a specific object, click the object in the pane on the left. To see a list of operations for the
whole offload session, click anywhere on the blank area in the left pane.

Viewing Copy Session Results


To review copy session results, do the following:

1. Open the History view.

2. In the inventory pane, select the Storage management node.

3. In the working area, right-click a copy session and select Sta tistics.

For more information, see Copying Backups to Capacity Tier.

Veeam Backup & Replication displays offload job session statistics for the following counters:

• The Job progress bar shows percentage of the copy session completion.

• The Summary box shows general information about the copy session:

o Duration — duration of the copy session.

o P rocessing rate — average speed of VM data processing. This counter is a ratio between the amount of
data that has actually been read and the offload session duration.

o Bottleneck — bottleneck in the data transmission process. To learn more about bottlenecks, see
Performance Bottlenecks.

• The Da ta box shows information about processed data:

o P rocessed — total size of all VM disks processed by the copy session.

1067 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o Rea d — the amount of data read from the extents.

o Tra nsferred — the amount of data transferred from the performance tier to the capacity tier.

• The Sta tus box shows information about the copy results. This box informs how many tasks have be en
completed with the Success, Warning and Error statuses (1 task per 1 VM).

• The pane in the lower-left corner shows a list of objects processed by the copy session.

• The pane in the lower-right corner shows a list of operations performed during the session. To see a list of
operations for a specific object, click the object in the pane on the left. To see a list of operations for the
whole copy session, click anywhere on the blank area in the left pane.

Viewing Download Session Results


To review SOBR Download job session results, do the following:

1. Open the History view.

2. In the inventory pane, select the Storage management node.

3. In the working area, right-click a SOBR Download session and select Sta tistics.

For more information, see How Downloading Data from Capacity Tier Works.

Veeam Backup & Replication displays SOBR Download job session statistics for the following counters:

• The Job progress bar shows percentage of the job completion.

• The Summary box shows general information about the job session:

o Duration — duration of the job session.

o P rocessing rate — average speed of data processing. This counter is a ratio between the amount of
data that has actually been read and the job session duration.

o Bottleneck — bottleneck in the data transmission process. To learn more about bottlenecks, see
Performance Bottlenecks.

1068 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The Da ta box shows information about processed data:

o P rocessed — total size of data blocks being downloaded from object storage repository plus blocks (if
any) being taken from the extents of your scale-out backup repository.

o Rea d — the amount of data read from both the object storage repository and extents of your scale-out
backup repository.

o Tra nsferred — the amount of data downloaded from object storage.

• The Sta tus box shows information about the job results. This box informs how many tasks have completed
with the Success, Warning and Error statuses.

• The pane in the lower-left corner shows a list of objects processed by the job.

• The pane in the lower-right corner shows a list of operations performed during the session. To see a list of
operations for a specific object, click the object in the pane on the left. To see a list of operations for the
whole job session, click anywhere on the blank area in the left pane.

Migrating Data
If necessary, you can migrate data between several capacity tiers or within one capacity tier.

Migrating Data To Another Capacity Tier


You can migrate your data between different object storage repositories. After that, you can add a new object
storage repository as a capacity extent instead of the previous repository.

The migration option may be useful if you want, for example, switch your provider.

You can migrate your data under the following scenarios:

• Migrating data between different cloud providers — use this scenario to migrate data from one type of
object storage provider to another. For example, to migrate data the Amazon S3 object storage repository
to the Azure Blob storage or any other storage provider.

• Migrating data between different buckets — use this scenario to migrate data between different buckets
of the same cloud provider.

IMP ORTANT

Consider the following:

• Migrating data between object storage repositories is available only at the capacity tier. Archive tier
does not support such scenarios.
• Migrating data from mutable to immutable capacity extents is not supported.

Migrating Data Between Different Cloud Providers


To migrate data located in an object storage repository between different cloud providers, do the following:

1. Download data from an object storage repository back to the performance extents, as described in section
Downloading Data from Capacity Tier.

2. Add a new object storage repository to the Veeam Backup & Replication environment, as described in
section Adding Object Storage Repositories.

3. Change an object storage repository to a new one that you have created at the previous step, as described
in section Add Capacity Tier.

1069 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Copy or move your data to a new object storage repository, as described in section Moving to Capacity
Tier.

Migrating Data Between Different Buckets


To migrate data located in an object storage repository between different buckets of the same cloud provider,
do the following:

1. Use any available 3rd-party tool to copy cloud data to a different bucket of your cloud storage.

2. Add a new object storage repository to the Veeam Backup & Replication environment, as described in
section Adding Object Storage Repositories.

3. Change the capacity extent to a new one that you have created at the previous step, as described in
section Add Capacity Tier.

4. Synchronize your data, as described in section Synchronizing Capacity Tier Data.

TIP

If you do not want to use the 3rd-party tool to copy cloud data, you can evacuate data from the capacity
extent to performance extent. After that, you can offload data from the performance extent to another
capacity tier.

Migrating Data Within One Capacity Tier


You can migrate your data between different extents of the same capacity tier.

To do this, perform the following steps:

1. Set the necessary extent to the Maintenance mode. For more information, see Switching to Maintenance
Mode.

2. Evacuate backups from the extent. For more information, see Evacuating Backups from Extents.

Indexes
IMP ORTANT

Starting from Veeam Backup & Replication version 12 indexes are no longer used. Indexes will be removed
after the first offload session.

To reduce the number of cost-based operations incurred by your cloud storage provider and to decrease the
amount of traffic being sent over the network when moving or copying data to object storage,
Veeam Backup & Replication uses indexes.

Index behavior has the following peculiarities:

• Indexes are created (or updated) during each offload or copy session and consist of hash values of blocks
that are being transferred to the capacity tier. These hashes are retrieved from meta information of your
backup files (VBK, VIB, or VRB).

• Indexes are stored in the ArchiveIndex directory that is located on the Performance Tier.
On each subsequent offload/copy session, Veeam Backup & Replication reuses these indexes to verify
whether new blocks that are about to be transferred to the capacity tier have not been offloaded earlier.
Verification is done by comparing existing indexes hashes with that of a block being transferred.

1070 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• If backups are created using the per-machine method, indexes are built per backup chain and cannot have
any cross references to any other backup chains. If all VM data is backed up to a single storage, indexes
are built for the whole backup.

• Indexes are updated every time a backup chain is modified.

For example, some data may have been removed due to the retention policy threshold, or you may have
removed it manually. Both scenarios will modify your indexes upon the next successful offload or copy
session to maintain consistency.

• Corrupted indexes can be rebuilt by using the Rescan feature, as described in section Rescanning Scale-
Out Repositories.

Once an index is rebuilt, Veeam Backup & Replication will have to wait for 24 hours before it can offload
any data again. This is necessary to comply with the eventual consistency model of S3 compatible object
storage repositories.

ArchiveIndex Directory Structure


When Veeam Backup & Replication creates indexes, it also creates and maintains the following directory
structure on each extent.

Directory Description

ArchiveIndex The root directory for keeping indexes.

< b ackup_id> Contains objects in a backup file.

< ob jects_in_backup_id> An identifier of an object in a backup file.


• If a backup was created using the per-machine method, then each VM will be
placed to its own directory.
• If a backup was created as a single-file backup, then all the VMs will be
placed to a unique directory.

stg _index Contains indexes of offloaded backup files (VBK, VIB, or VRB).

ind ex_data.vbk Contains meta information on hash values stored in index files.

Retention Policy
Retention policy defines the number of restore points to keep on your performance extents and capacity extents
is configured at the Specify Backup Storage Settings step of the New Backup Job wizard.

You can manage retention policies to remove obsolete restore points both from the performance extents and
the capacity tier.

1071 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
The restore points that fall under the retention policy will be removed both from the performance and capacity
extents in the following manner:

• An earliest restore point will be removed from the backup chain on the associated extent.

• Data blocks that correspond to the restore point that is being removed will be purged from the capacity
extent upon the next offload or copy session.

Make sure that the capacity extent has not been put into the Maintenance mode, as this mode prevents
synchronization of the state of the backup chain in the performance tier with that of the capacity tier.

For more information about the move and copy offload sessions, see Moving Inactive Backup Chains to
Capacity Tier and Copying Backups to Capacity Tier.

• Immutable blocks of data are removed after the immutability period is over.
When a retention policy encounters immutable copied/moved blocks of data, it removes such blocks from
the associated backup files on the extents only, informing Veeam Backup & Replication that these blocks
no longer exist and must be removed from the capacity tier once mutable.

For more information about immutability, see Immutability.

Excluding Capacity Extent from Scale-Out Repositories


You can exclude a capacity extent from the scale-out backup repository scope, for example, if you no longer
want to use any third party services to store your data.

Consider that after you exclude an object storage repository that is being used as a capacity extent and is storing
offloaded backup data, Veeam Backup & Replication automatically puts the excluded object storage repository
into the Maintenance mode. Once a repository is in the Maintenance mode, you will not be able to restore your
data from it. To switch back to normal, you will have to re-add that repository as a capacity extent and
synchronize existing backup chains with your performance extents. After the synchronization is complete, the
existing backups will become available as Imported. For more information, see Synchronizing Capacity Tier Data.

NOTE

If you have an archive extent in the same scale-out backup repository, it will also switch to the
Maintenance mode when you exclude a capacity extent. Note that this is not applied if you use the same
object storage repository by the same provider for performance, capacity and archive tiers, for example, by
Amazon S3. In this case, after removing a capacity extent from capacity tier the performance and archive
tiers will remain in a scale-out backup repository.

To exclude a capacity extent from the scale-out backup repository scope, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Sca le-out Repositories.

3. In the working area, select a scale-out backup repository and click E d it Scale-out Repository on the ribbon,
or right-click a scale-out backup repository and select P roperties.

4. Move to the Ca pacity tier step of the wizard.

1072 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Clear the E x tend scale-out backup repository capacity with object storage check box.

If you have data on the object storage, you will be asked to confirm the action in the pop-up dialog. After
that, the object storage repository will be immediately put into the Maintenance mode.

Restore from Capacity Tier


You can restore your data directly from the capacity tier back to production servers or to Microsoft Azure,
Amazon EC2 or Google cloud platforms. Capacity tier data recovery does not differ from that of a standard
backup data recovery and can be performed by using any of the following methods:

• Instant Recovery to VMware vSphere

• Instant Recovery to Microsoft Hyper-V

• Entire VM Restore

• VM Files Restore

• Guest OS File Restore

• Disk Export

• Application Items Restore

• Exporting Backups

Data recovery can also be done directly to Amazon EC2, Microsoft Azure or Google as described in sections
Restore to Amazon EC2, Restore to Microsoft Azure and Restore to Google Compute Engine.

1073 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

To increase the speed of restore to Microsoft Azure, make sure that the following requirements are met:

• To restore data, use Azure restore proxy appliances.


• Azure restore proxy appliances must be located in the same Azure region, where you keep backups
and Azure VMs created from backups.

Restore Scenarios
This section explains possible restore scenarios from the capacity tier.

Unavailability of Backup Files


If one of the offloaded backup files becomes unavailable on any of the extents in a scale -out backup repository,
you can restore it by doing the following:

1. Rescan a scale-out backup repository.

For more information on how to rescan a scale-out backup repository, see Rescanning Scale-Out
Repositories.

2. Copy data from the capacity tier to the performance tier.

For more information on how to copy data, see Copying to Performance Tier.

NOTE

The performance or capacity extents must not be in the Maintenance mode.

Unavailability of Extents
A performance extent in a scale-out backup repository may become unavailable or be in the Maintenance mode.
To restore data in such case, you can use any method described in section Data Recovery.

For example, you are restoring a virtual machine consisting of three data blocks, of which two blocks reside on
the Extent 1 and another required block is stored on the Extent 2 which is unavailable. In such scenario,
Veeam Backup & Replication gets two blocks from the Extent 1 and another required block from the capacity
tier.

Unavailability of Scale-Out Backup Repository


To restore data if the entire scale-out backup repository is unavailable, you can use any method described in
section Data Recovery.

1074 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If the entire scale-out backup repository becomes unavailable, Veeam Backup & Replication restores data from
the capacity tier only.

For example, both performance extents that store required backup files to restore a virtual ma chine are not
available. In such a scenario, Veeam Backup & Replication restores data from the capacity tier only.

Unavailability of Backup Server


To get access to backups in the capacity tier in case the entire configuration of the backup server becomes
corrupted and your scale-out backup repositories are no longer available, you can:

• Restore the configuration of the backup server from the configuration backup, as described in section
Configuration Backup and Restore.

• Import backups from the capacity tier, as described in section Importing Backups.

1075 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Archive Tier
Archive tier is an additional tier of storage that can be attached to a scale-out backup repository. You can
transport data to the archive tier for archive storage from the following extents:

• From performance extents that consist of Amazon S3, Microsoft Azure or S3 compatible with data
archiving object storage repositories.

• From capacity extents.

Storing archived data in the archive tier is cheaper than in the capacity tier. However, restoring data from the
archive tier is longer and more expensive compared to the capacity tier. Data must be prepared for restore from
the archive tier.

This feature is most useful in the following cases:

• You have a lot of rarely (no more than once a quarter) accessed data that has to be stored in an archive.

• You want to save costs and space on storing archived data.

The following types of backup files are suitable for archive storage:

• Backup files with GFS flags

• VeeamZIP backup files

• Exported backup files

• Orphaned backups with GFS flags

• Backups with GFS flags created by Veeam Backup for Red Hat Virtualization

• Backups exported by K10 policies

The archive tier consists of a single archive extent. One of the following cloud-based object storage repositories
providing "cold" data storage can be added as the archive extent:

• Amazon S3 Glacier

• Microsoft Azure Archive Storage

Before an object storage repository can be configured as the archive extent, it must be added to
Veeam Backup & Replication backup infrastructure. For more information, see Adding Amazon S3 Glacier
Storage or Adding Azure Archive Storage.

You can add the archive extent to your scale-out backup repository and configure its settings on the Add
Archive Tier step of the New Scale-out Backup Repository wizard.

Limitations for Archive Tier


The archive tier has the following limitations:

• For archive extents you must use the same object storage provider, that you use for the tier (either the
performance tier, or the capacity tier) from which data moves to the archive tier:

o If data moves from the performance tier to the archive tier, the object storage on these tiers must be
of the same provider. However, in this scale-out backup repository configuration you can use any
object storage provider for the capacity tier. For example, you can use Amazon S3 object storage as a
performance extent, Google object storage as a capacity extent and Amazon S3 Glacier as an archive
extent.

1076 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o If data moves from the capacity tier to the archive tier, the object storage on these tiers must be of
the same provider. However, in this scale-out backup repository configuration you can use any object
storage provider for the performance tier. For example, you can use S3 compatible object storage as a
performance extent, Microsoft Azure Blob as a capacity extent and Microsoft Azure Archive as an
archive extent.

For more information on configuring performance extents, see Add Performance Extents.

For more information on configuring capacity extents, see Add Capacity Tier.

• Migrating data to another archive tier is not supported.

• Imported backups cannot be offloaded to archive tier.

• You cannot use object storage of different providers in the same type of tier. For example, you cannot add
and use Amazon S3 storage and Microsoft Azure Blob storage to one archive extent.

• Incremental backup files cannot be stored in the archive tier.

• Microsoft Azure Archive Storage with the archive access tier does not support Azure accounts with the
following redundancy options: zone-redundant storage (ZRS), geo-redundant storage (GZRS) and read-
access geo-zone-redundant storage (RA-GZRS). For more information, see Microsoft Docs.

• If you use immutability and have several extents in your archive tier, you must enable it for all extents
within this tier. You cannot use mixed configuration and have only one extent with immutability enabled.

Archive Extent Structure


When data is transferred to the archive extent, Veeam Backup & Replication creates and maintains the following
structure of directories:

Directory Description Misc

< b ucket_name> or A bucket or container name. N/A


< container_name> Buckets and containers must be created in advance.

Veeam/LongTerm/ Standard folders created by


Veeam Backup & Replication.

1077 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Directory Description Misc

< repository_folder_name> A repository folder that you create when adding a


new archive extent.

< b ackup_id> Contains objects in a backup. These folders are


automatically removed
during data removal.
< ob jects_in_backup_id> An identifier of an object in a backup.

Ind exDescr Contains size of a backup.

Blob Store Contains data blobs created by the archiving


session, as described in section Archive Tier Data
Transfer.

Checkpoints Contains meta information about the state of


archived backup chains. Such meta information is
updated upon each successful archiving session.

Ob jects Contains meta information and other auxiliary data.

Storages Contains a replicated version of archived backup


files with metadata.

Immutability for Archive Tier


Veeam Backup & Replication allows you to prohibit deletion of data from the archive extent by making that data
temporarily immutable. It is done for increased security: immutability protects your data from loss as a result of
attacks, malware activity or any other injurious actions.

You can enable immutability for data stored in Amazon, S3-compatible and Azure object storage repositories
used as archive extents of the scale-out backup repository. After you enable immutability,
Veeam Backup & Replication will prohibit data deletion from the archive tier until the immutability expiration
date comes.

When you enable immutability for the archive tier, keep in mind that only the settings of the Amazon S3 Glacier
repository will be taken into account. The settings of the capacity tier repository and of the original data blocks
will be ignored.

For Amazon S3 Glacier and Azure Archive Storage, all the types of files that are suitable for archive storage can
be made immutable:

• Backup files with GFS flags assigned: in case GFS retention is extended in the backup job or backup copy
job settings, the immutability period for existing backup files will be prolonged at the end of the archiving
session. For more information about GFS retention policy, see Long-Term Retention Policy (GFS).

• VeeamZIP backup files with specified retention (deletion date). For more information, see Creating
VeeamZIP Backups.

1078 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Exported backup files with specified retention (deletion date). For more information, see Exporting
Backups.

The immutability period of a backup file will be equal to its retention period at the moment of archiving. If the
retention period is not specified for VeeamZIP backup files or exported backup files, such files will not be made
immutable.

Enabling Immutability
To enable immutability, you must do the following:

1. Configure the necessary settings when you create an S3 bucket or an Azure container.

For more information, see Preparing to Use Immutability.

2. Enable the immutability option when you add an object storage repository to the backup infrastructure at
the Container step (for Azure object storage repository) or Buck et step (for Amazon S3 or S3 compatible
object storage repositories) of the new Ob ject Storage Repository wizard.

Managing Archive Tier


You can manage your archive tier and the archived data in the following ways:

• Move outdated backups from the capacity extent or the performance extent to the archive extent.

• Delete outdated backup files.

• Exclude the archive extent from the scale-out backup repository scope.

Archive Tier Data Transfer


You can move outdated backup files from the capacity tier or performance tier to the archive tier. After that, the
transported files are deleted from the capacity tier or performance tier. They can stay in the performance tier or
be deleted from there depending on the data transfer policy of the scale-out backup repository:

• In case the copy policy is selected (the outdated backup files are copied from the performance tier to the
capacity tier), the original file stays in the performance tier.

• In case the move policy is selected (the outdated backup files are transferred from the performance tier to
the capacity tier), the original file disappears from the performance tier.

• In case you transfer data from the performance tier to the archive tier, the original file disappears from the
performance tier.

Da ta transfer P erformance tier Ca pacity tier Archive tier


p olicy

Copy Original file (nothing) Copy of the file

Move (nothing) (nothing) The transferred file

Without capacity (nothing) (nothing) The transferred file


tier

1079 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Archiver Appliances
Data transfer from the capacity extent or the performance extent to the archive extent is done through archiver
appliances — temporary virtual machines. The template for all the archiver appliances is set up at the Archiver
Ap p liance step of the Adding Amazon S3 Glacier or Adding Azure Archive Storage wizard.

You can set up the size of the virtual machine and cloud resources where the archiver appliance will be created.
You can specify the archiver appliance settings manually, or use the default settings.

After the archiving job is finished, all the archiver appliances are automatically deleted. If the job ends
prematurely, the archiver appliances will be deleted as well. Also, any archiver appliance can be deleted if there
are no more tasks for it.

Archiving Job
The process of moving backup files from the performance or capacity tier to the archive tier is called an
archiving job. The archiving job takes place in a separate job session. The archiving job launches periodically,
under the same default schedule as the offload job from the performance tier to the capacity tier.

New backup files are offloaded to the archive tier and outdated ones are cleaned up during the same archiving
session. You can archive backup files if they meet all the following conditions:

• The type of backup file is appropriate. For details, see Archive Tier.

• [For the capacity tier] Backup files are offloaded to the capacity tier.

• Backup files have not been archived yet.

• Backup files belong to inactive backup chains.

• Backup files have been created N days ago according to Archive backup files older than N days setting of
the Add Archive Tier step of the wizard.

NOTE

If you set the value in the Archive backup files older than N days field to 0, the backup files will be
moved to the archive tier during the nearest archiving session, and will no longer participate in the
capacity tier data deduplication.

• If you have selected the Archive backups only if the remaining retention time is above minimal storage
p eriod check box of the Add Archive Tier step of the wizard:

a. for Amazon S3 Glacier storage: only backup files with retention period no less than 90 days.

b. for Microsoft Azure Archive storage: only backup files with retention period no less than 180 days.

Backup files that meet all the following conditions will be cleaned up:

• Backup files that do not have original files on the performance tier.

• Backup files with expired or unspecified immutability period. For more information, see Immutability for
Archive Tier.

After the archiving job is completed, the transported files are deleted from the performance or capacity tier. For
capacity tier, it happens during the next offload to capacity tier session.

1080 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Cleanup Tasks
Cleanup tasks exist within archiving jobs. They are launched if there are only outdated backup files to delete
during a certain job session, and no new backup files are to be offloaded to the archive tier.

Cleanup tasks do not require archiver appliances.

Excluding Archive Extent from Scale-Out Backup Repository


You can exclude an archive extent from the scale-out backup repository scope, for example, if you no longer
want to use any third party services to store your data.

Consider that after you exclude an object storage repository that is being used as an archive extent and is
storing archived backup data, Veeam Backup & Replication automatically puts the excluded object storage
repository into the Maintenance mode. Once a repository is in the Maintenance mode, you will not be able to
restore your data from it. To switch back to normal, you will have to re-add that repository as an archive extent
and synchronize existing backup chains with data in this scale-out backup repository. After the synchronization
is complete, the existing backups will become available as Imported.

To exclude an archive extent from the scale-out backup repository scope, do the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Sca le-out Repositories.

3. In the working area, select a scale-out backup repository and click E d it Scale-out Repository on the ribbon,
or right-click a scale-out backup repository and select P roperties.

4. Move to the Archive tier step of the wizard.

5. Clear the Archive GFS full backups to object storage check box.

You will be asked to confirm the action in the pop-up dialog. After that, the object storage repository will
be immediately put into the Maintenance mode.

1081 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore from Archive Tier
You can restore data from the archive storage. To do so, you have to receive a temporary access to the data first.
Thus, the process of restore from the archive tier consists of two consecutive parts:

1. Data retrieval

2. Restoring retrieved data

Data Retrieval
Data retrieval is the process of receiving temporary access to archived data, so that it can be restored.

The process of retrieving data from the archive tier takes course in a separate retrieval job session. It is
completed when a restore point is available for reading and restore. For information on how to launch the
retrieval job, see Retrieving Backup Files.

When the retrieval job is complete, the retrieved data will be available for a limited period of time, during which
you can restore it. However, you can extend the availability period.

NOTE

If you launch restore job when retrieval job is not over yet, the restore job will be pending until the
retrieval job is complete.

Retrieval cost varies depending on the desired speed of the process and on the targeted period of the data
accessibility. See below the options for different vendors.

Retrieval Options for Amazon S3 Glacier


Amazon provides the following options for data retrieval. The indicated time is approximate. For more
information, see AWS Documentation.

• Expedited: the most expensive method. Retrieval takes 1-5 minutes.

NOTE

This option is not available if you assign the Amazon S3 Glacier Deep Archive storage class to data
blocks.

• Standard accelerated: retrieval time is faster than the standard option and allows to retrieve a group of
object. Note that it will result in additional costs.

• Standard: retrieval time 3-5 hours for Amazon S3 Glacier and within 12 hours for Amazon S3 Glacier Deep
Archive.

• Bulk: the least expensive method. Retrieval time within 5-12 hours for Amazon S3 Glacier and within 48
hours for Amazon S3 Glacier Deep Archive.

Expiration of the Retrieved Data for Amazon S3 Glacier


Estimated time of data expiration is calculated from the moment of the data retrieval launch. Required number
of days is added to that moment.

However, during the retrieval job Veeam Backup & Replication constantly requests the S3 API to move the
expiration time forward, until the job is completed and all the data blocks are ready.

1082 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For more information on calculating the estimated expiration time, see AWS Documentation.

For information on how to extend the expiration time, see Extending Expiration Time.

Retrieval Options for Azure Archive Storage


Azure provides the following options for data retrieval. The indicated time is approximate. For more
information, see Microsoft Docs.

• High Priority: most expensive method. Retrieval may take less than one hour.

• Standard Priority: least expensive method. Retrieval takes up to 15 hours.

Expiration of the Retrieved Data for Azure Archive Storage


Unlike Amazon S3 Glacier, Azure API does not temporarily change the storage class of a backup file from Archive
Tier to Hot. Instead, a temporary copy of a backup file is created in Hot storage class. Since the deletion of this
temporary copy is managed by Veeam Backup & Replication, the expiration time is quite accurate (within ten
minutes, which is the frequency of the deletion process).

For information on how to extend the expiration time, see Extending Expiration Time.

Retrieving Backup Files


To start the retrieval of archived backup files, use the Retrieve Backup wizard.

1083 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Retrieve Backup Wizard

To launch the retrieval job, do one of the following:

• Open the Home view. In the inventory pane select Archive Tier. In the working area, select the backup job
whose files you want to retrieve and click P roperties on the ribbon. In the Ba ckup Properties window, click
on Retrieve.

• Open the Home view. In the inventory pane select Archive Tier. In the working area, select the VM whose
guest OS files you want to restore and on the ribbon select the necessary type of restore. Proceed to the
Select Restore Point step of the wizard. If this restore point has not been retrieved yet, you will be
prompted to launch the Retrieve Backup wizard.

1084 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Retrieval Mode

At the Retrieval Mode step of the wizard, select the desired retrieval option. For information on the retrieval
modes for different archive storage options, see Data Retrieval.

1085 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Availability Period

At the Ava ilability Period step of the wizard, select the desired availability period of the retrieved backup files.
During that period you will be able to restore the data.

If you want to receive a notification that the availability period is about to end, select the Send a notification
ema il N hours before the published data expires check box and choose the desired time for the notification.

TIP

You will be able to extend that period if necessary. For information on how to extend backup files
availability, see Extending Data Availability.

1086 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Finish Working with Wizard

At the Summary step of the wizard, review the retrieval settings. Click Finish to exit the wizard.

Extending Data Availability


The availability period of the retrieved data can be prolonged:

• Manually. If the retrieval job still continues at the moment of manual extension, the new extension tim e is
automatically added to the job.

• Automatically. This happens in cases when the expiration time is close, but the restore process still
continues.

At the Select Availability Period step of the Retrieve Backup wizard, you can request a notification that the data
availability is about to expire. If you extend the expiration time, the notification will be postponed according to
the expiration time.

To extend the availability period, do the following:

• Open the Home view. In the inventory pane select Da ta Retrieval. In the working area, select the retrieved
backup file whose availability period you want to extend, and click E x tend Availability on the ribbon. You
will be prompted to select the number of days you want to add to the availability expiration time.

1087 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane select Archive Tier. In the working area, select the backup job
for whose retrieved files you want to extend availability and click P roperties on the ribbon. In the Ba ckup
P roperties window, click on E x tend Availability P eriod. You will be prompted to select the number of days
you want to add to current expiration time.

Restoring Retrieved Data


You can restore your data directly from the archive tier back to production servers or to Microsoft Azure,
Amazon EC2 or Google Compute Engine platforms. The retrieved data recovery does not differ from standard
backup data recovery and can be performed by using any of the methods documented in the Data Recovery
section.

1088 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Scale-Out Backup Repositories
Before you add a scale-out backup repository, check prerequisites. Then use the New Scale-out Backup
Rep ository wizard to configure the scale-out backup repository.

Before You Begin


Before you add a scale-out backup repository to the backup infrastructure, check the following prerequisites:

• Backup repositories that you plan to add as performance extents to the scale-out backup repository must
be added to the backup infrastructure. For more information, see Adding Backup Repositories.

• You must check limitations for scale-out backup repositories. For more information, see Limitations for
Scale-Out Backup Repositories.

• An object storage repository cannot be added as part of two or more different scale -out backup
repositories at the same time.

• If the selected object storage contains offloaded backup data, you will be offered to synchronize this data
with your performance extents.

For more information, see Synchronizing Capacity Tier Data.

• Object storage that contains imported backups cannot be added as a capacity extent.

For more information, see Importing Object Storage Backups.

• You cannot add the same object storage repository as the performance extent and capacity extent.

• You cannot use object storage of different providers in the same type of tier. For example, you cannot add
and use Amazon S3 storage and Microsoft Azure Blob storage to one performance extent.

• You cannot use the object storage repository and the backup repositories in performance tier
simultaneously.

1089 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Scale-Out Backup Repository Wizard
To launch the New Scale-out Backup Repository wizard, do one of the following:

• Open the Ba ckup Infrastructure view. In the inventory pane select Sca le-out Repositories and click Ad d
Sca le-out Repository on the ribbon.

• Open the Ba ckup Infrastructure view. In the inventory pane right-click Sca le-out Repositories and select
Ad d Scale-out Backup Repository.

1090 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Scale-Out Backup Repository Name
At the Na me step of the wizard, specify a name and description for the scale-out backup repository.

1. In the Na me field, specify a name for the scale-out backup repository.

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

1091 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Add Performance Extents
At the P erformance Tier step of the wizard, specify which backup repositories or object storage repositories you
want to add as performance extents, and configure options for the scale-out backup repository.

1. On the right of the E x tents list, click Ad d .

2. In the E x tents window, select check boxes next to backup repositories or object storage repositories that
you want to add as performance extents.

3. Click OK.

4. At the lower right corner of the E x tents list, click Ad vanced.

5. Specify advanced options for the scale-out backup repository:

a. If you want to create a separate backup chain for every machine in the job, check that the Use p er-
ma chine backup files check box is selected . With this option enabled, during one backup job session
Veeam Backup & Replication will produce a number of backup files — one per every machine, and will
write these files to the backup repository in multiple streams simultaneously. It is recommended that
you enable this option to achieve better storage and compute resource utilization, especially if you
use as a backup repository a deduplicating storage appliance that supports multiple write streams.

NOTE

For object storage repositories that you add as performance extents, this option is selected by
default and you cannot disable it.

1092 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. To preserve the consistency of backup chains in the scale-out backup repository, select the P erform
full backup when required extent is offline check box. If an extent that contains previous restore
points from the current backup chain gets offline, the backup chain will be broken.
Veeam Backup & Replication will not be able to add a new incremental backup file. With this option
enabled, Veeam Backup & Replication will create a full backup file instead of an incremental backup
file. If you enable this option, you must make sure that you have enough free space in the scale -out
backup repository to host a full backup file.

1093 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If a backup repository that you add as a performance extent is already used by jobs of supported type or there
are backups pointing at the backup repository (for example, independent backups created by VeeamZIP),
Veeam Backup & Replication will offer you to update a link to the backup repository in the job properties. Click
Y es to update the link and target the jobs and backups at the scale-out backup repository. If you click No, you
will not be able to pass to the next steps of the wizard.

1094 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Backup Placement Policy
[This step is not available if you use object storage repositories as performance extents. For more information
on how backup file placement policy works for performance extents configured of objects storage repositories,
see Backup File Placement]

At the P olicy step of the wizard, specify how you want to store backup files on performance extents of the
scale-out backup repository.

1. Set the backup file placement policy for the scale-out backup repository:

o Select Da ta locality if you want to store backup files that belong to the same backup chain together.
In this case, a full backup file and subsequent incremental backup files will be stored to the same
performance extent of the scale-out backup repository. The new backup chain may be stored to the
same performance extent or to another performance extent (unless you use a deduplicating storage
appliance as a performance extent).

o Select P erformance if you want to store full and incremental backup files to different performance
extents of the scale-out backup repository. If you set the Performance policy, you must make sure
that the network connection is fast and reliable so that Veeam Backup & Replication can access all
backup files from the backup chain.

For more information, see Backup File Placement.

2. If you select the P erformance policy, you can restrict which types of backup files can be stored on a
specific performance extent. For example, if you have added three performance extents to the scale-out
backup repository, you may want to store full backup files on one extent and incremental backup files —
on the other two extents.

a. Click Customize.

b. In the Ba ckup Placement Settings window, select a performance extent and click E d it.

c. Select a check box next to the type of backup files that you want to store on the extent: Full backup
files or Incremental backup files. By default, Veeam Backup & Replication can store both full and
incremental backup files on the same extent.

3. If you select the Strict placement policy enforcement check box, Veeam Backup & Replication will not
create a backup if it violates the backup placement policy and may result in that a backup job will fail.

NOTE

This option is not available if you either rebalance extents of your scale-out backup repositories or
evacuate data from scale-out backup repositories.

1095 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1096 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Add Capacity Tier
Before you add a capacity tier, check the prerequisites.

At the Ca pacity Tier step of the wizard, select object storage repositories that you want to add as capacity
extents. Then specify when to move and copy data.

TIP

If you already have a scale-out backup repository in your backup infrastructure and you want to add
capacity tier, select the scale-out backup repository, click E d it Scale-out Repository on the ribbon or right-
click the scale-out backup repository and select P roperties. In the E d it Scale-out Backup Repository wizard
go to the Ca pacity Tier step and proceed with the steps below.

To configure capacity tier, do the following:

1. Select the E x tend scale-out backup repository capacity with object storage check box.

2. To select the object storage repositories to which you want to offload your data, click Choose.

3. In the Ca pacity Tier Extents window select the check box in front of the necessary object storage
repositories.

Make sure that these repositories are added to the backup infrastructure in advance. In case object storage
repositories are not added, click Ad d and follow the steps of the Adding Object Storage Repository wizard.

3. Click W indow and specify when it is allowed or prohibited to move or copy data to object storage.

4. Select the Cop y backups to object storage as soon as they are created check box to copy new backups as
soon as they are created, as described in section Copying Backups to Capacity Tier.

When selecting this option, you will be asked whether to copy all backup files that you may already have
on any of the performance extents, or only those that have been created recently.

If you select La test, only backup files that belong to the last active backup chain will be copied from each
of the performance extents. If you select All, Veeam Backup & Replication will copy all backup files that
belong to all backup chains located on any of the specified extents.

5. Select the Move backups to object storage as they age out of the operational restores window check box
to move inactive backup chains to the capacity extent, as described in section Moving Backups to Capacity
Tier.

In the Move backup files older than X days field, specify the operational restore window to define a period
after which inactive backup chains on your performance extents will be considered outdated and,
therefore, should be moved to the capacity extent. Consider that "0" is an acceptable value, which you
can specify to offload inactive backup chains on the same day they are created.

To override behavior of moving old backups, click Override, select the Move oldest backup files sooner if
sca le-out backup repository is reaching capacity check box and define a threshold in percent to force data
transfer if a scale-out backup repository has reached the specified threshold.

6. To offload data encrypted, select E ncrypt data uploaded to object storage and provide a strong password.
With this option selected, the entire collection of blocks along with the metadata will be encrypted while
being offloaded.

If you have not created the password beforehand, click Ad d or use the Ma nage passwords link to specify a
new password.

7. [For Veeam Backup & Replication 12.1 (build 12.1.0.2131)] If you want to specify a schedule for a health
check, click the Monthly link and define the schedule settings. For more information, see Health Check for
Capacity Tier.

1097 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

You can combine both the Cop y backups to object storage as soon as they are created option and the Move
b a ckups to object storage as they age out of the operational restores window option, as described in
section Copying Backups to Capacity Tier.

Synchronizing Capacity Tier Data


When you add as a capacity extent an object storage repository that contains offloaded backup data, you will be
prompted to synchronize this data with the performance extents in the scale-out backup repository.

Consider the following:

• An object storage repository can only be added as a capacity extent after existing data (if any) is
synchronized.

• During synchronization, Veeam Backup & Replication downloads backup files with metadata located in
object storage to the performance extents that are part of the scale-out backup repository that is being
added.

These files are created as described in section Moving Backups to Capacity Tier.

• Extents to which backup data is going to be downloaded (synchronized), will be selected automatically,
depending on the available resources.

• The actual data blocks will not be downloaded and will continue to remain in object s torage.

• When synchronizing encrypted storage, make sure to provide the same exact password with which the
data was encrypted.

1098 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
After the synchronization is complete, the associated backup files located in object storage will become
available as Imported and will be displayed in the Home view, under the Ob ject Storage (Imported) node in the
inventory pane.

1099 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Add Archive Tier
At the Archive Tier step of the wizard, select an object storage repository that you want to add as an archive
extent and specify data move settings.

TIP

If you have a compatible type of a repository configured as a capacity extent, you can add an archive extent
to the existing scale-out backup repository. To do so, select the scale-out backup repository, click E d it
Sca le-out Repository on the ribbon or right-click the scale-out backup repository and select P roperties. In
the E d it Scale-out Backup Repository wizard go to the Archive Tier step and proceed with the steps below.

Consider the following:

• The Archive Tier step of the wizard will appear only if you have a compatible type of repository configured
as a capacity extent or a performance tier. For more information, see Limitations for Archive Tier.

• You can add only one archive extent per scale-out backup repository.

To configure the archive extent, do the following:

1. Select the Archive GFS full backups to object storage check box. In the drop-down list, select one of
available object storage repositories or click Ad d to add a new one.

2. In the Archive GFS backups older than N days field, specify the operational restore window to define a
period after which inactive backup chains on your capacity extent will be considered outdated and,
therefore, should be moved to the archive extent. Consider that "0" is an acceptable value, which you can
specify to archive inactive backup chains on the same day they are created.

You can use the default storage settings or specify them manually. For that, click Storage.

• Select the Store archived backups as standalone fulls check box to forbid reuse of the data blocks.

• Select the Archive backups only if the remaining retention time is above minimal storage period check box
to specify which data blocks can be transported to the archive tier.

1100 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
When you add as an archive extent an object storage repository that contains archived backup data, you will be
prompted to synchronize existing backup chains with data in this scale-out backup repository. After the
synchronization is complete, the existing backups will become available as Imported and will be displayed in the
Home view, under the Archive Tier (Imported) node in the inventory pane.

1101 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of scale-out backup repository configuration.

Wait for the scale-out backup repository to be added to the backup infrastructure. The process may take some
time.

1. Review details of the scale-out backup repository.

2. Click Finish to exit the wizard.

1102 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Scale-Out Backup Repositories
You can manage your scale-out backup repositories and the data there in various ways: edit settings of the
scale-out backup repository, rescan scale-out backup repositories automatically or manually, discover on which
performance extent of the scale-out backup repository a particular backup file is stored, extend scale-out
backup repository or remove certain performance extents from it, perform service actions or remove the scale -
out backup repository.

Editing Settings of Scale-Out Backup Repositories


You can edit settings of the scale-out backup repository, for example, if you want to change the backup file
placement policy or specify other advanced settings for the backup repository.

Consider the following:

• If you enable or disable the Use p er-machine backup file option, Veeam Backup & Replication will apply
new settings after a new full backup file is created.

• If you enable or disable the P erform full backup when required extent is offline option,
Veeam Backup & Replication will apply the new settings starting from the next session of the job targeted
at this scale-out backup repository.

• If you change the backup file placement policy settings, Veeam Backup & Replication will apply the new
settings starting from the next session of the job targeted at this scale-out backup repository.

To change the scale-out backup repository settings:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Sca le-out Repositories.

3. In the working area, select the scale-out repository and click E d it Scale-out Repository on the ribbon or
right-click the scale-out backup repository and select P roperties.

4. Follow the steps of the E d it Scale-out Backup Repository wizard and edit settings as required.

1103 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Rescanning Scale-Out Repositories
Veeam Backup & Replication periodically rescans scale-out backup repositories. During the rescan process, it
gets the following information:

• State of every performance extent added to the scale-out backup repository: online or offline.

• Status of Veeam Data Movers on extents: up-to-date or outdated.

• Space available in the scale-out backup repository.

The rescan operation is performed automatically by a rescan process that works permanently in the background.
The process is started every 24 hours. It can be also started when a new task session starts , and the Veeam
Backup Service requires information about the infrastructure to be refreshed.

In addition to the automated rescan process, you can manually start rescan of the scale -out backup repository.
Backup repository rescan may be helpful, for example, if you want to discover backup files that were manually
relocated from one performance extent to another one.

Consider the following:

• Information about backup files location is updated only if you perform manual rescan of scale -out backup
repositories.

• Veeam Backup & Replication rescans scale-out backup repositories when you perform backup files import.

• Veeam Backup & Replication does not rescan extents that are set into the Maintenance mode.

• To successfully rediscover relocated backups files created by backup copy jobs, make sure to disable these
jobs manually prior to rescanning.

For more information, see Disabling and Removing Jobs.

To start the rescan process:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane select Sca le-out Repositories.

1104 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the scale-out repository and click Rescan Repository on the ribbon or right-
click the scale-out backup repository and select Rescan.

Checking Rescan Sessions Reports


If necessary, you can view a history of all rescan reports that Veeam Backup & Replication ran for scale-out
backup repositories (both automatic and manual).

To do it, perform the following steps:

1. Open the History view.

2. In the inventory pane, select Sta tistics.

1105 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the necessary task session and click Sta tistics on the ribbon. You can also right-
click the necessary session and select Sta tistics.

Discovering Backups in Scale-Out Backup Repositories


To discover on which performance extent of the scale-out backup repository a particular backup file is stored,
you can examine the job session statistics or check the backup properties.

To view the job session statistics:

1. Open the Home view.

2. In the inventory pane, click Ba ck up under Job s .

3. In the working area, right-click the job and select Sta tistics.

1106 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the bottom left pane of the window, click the VM name. In the Action pane, locate the message: Using
N scale-out repository extent.

To view the backup properties:

1. Open the Home view.

2. In the inventory pane, select Disk under Ba ckups.

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

1107 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Veeam Backup & Replication will display the extent where the backup file resides in the headline of the
Ba ckup Properties window. To see the path to the backup file, right-click the job and select Cop y path.

Backup State Indicators


Restore points icons help you understand current state of a restore point in a scale-out backup repository.

For more information on icons and what they indicate, see Restore Points Icons.

Extending Scale-Out Repositories


You can add a backup repository or an object storage repository as a performance extent or a capacity extent to
the scale-out backup repository at any time. For example, the scale-out backup repository may run low on
space, and you will need to add storage capacity to it.

Extending Performance Tier


To extend the performance tier, perform the following steps:

1. Check the limitations for performance tier.

2. Open the Ba ckup Infrastructure view.

3. In the inventory pane, click Sca le-out Repositories.

4. In the working area, select the scale-out repository and click E d it Scale-out Repository on the ribbon or
right-click the backup repository and select P roperties.

5. Move to the P erformance tier step of the wizard.

1108 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Click Ad d .

7. In the E x tents window, select a check box next to the backup repository that you want to add as a
performance extent to the scale-out backup repository.

If a backup repository that you add as a performance extent is already used by jobs of supported type or
there are backups pointing at the backup repository (for example, independent backups created by
VeeamZIP), Veeam Backup & Replication will offer you to update a link to the backup repository in the job
properties. Click Y es to update the link and target the jobs and backups at the scale-out backup
repository. If you click No, you will not be able to pass to the next steps of the wizard.

8. Pass through the next wizard steps and finish working with the wizard. The new performance extent will
be added to the scale-out backup repository.

NOTE

After you add a backup repository to the scale-out backup repository as a performance extent, you will not
be able to use it as an individual backup repository.

Extending Capacity Tier


To extend the capacity tier, perform the following steps:

1. Check the limitations for capacity tier.

2. Open the Ba ckup Infrastructure view.

3. In the inventory pane, click Sca le-out Repositories.

4. In the working area, select the scale-out repository and click E d it Scale-out Repository on the ribbon or
right-click the backup repository and select P roperties.

5. Move to the Ca pacity tier step of the wizard.

1109 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Click Choose.

7. In the Ca pacity Tier Extents window, select a check box next to the backup repository that you want to
add as a capacity extent to the scale-out backup repository.

8. If a backup repository that you add as a capacity extent is already used by jobs of supported type or there
are backups pointing at the backup repository (for example, independent backups created by VeeamZIP),
Veeam Backup & Replication will offer you to update a link to the backup repository in the job properties.
Click Y es to update the link and target the jobs and backups at the scale-out backup repository. If you click
No, you will not be able to pass to the next steps of the wizard.

9. Pass through the next wizard steps and finish working with the wizard. The new capacity extent will be
added to the scale-out backup repository.

Service Actions with Scale-Out Backup Repositories


In some cases, you may want to perform service actions with scale-out backup repository extents. For example,
you need to upgrade the repository server and add more memory to it. Or you want to replace a storage device
backing the extent and need to relocate backup files.

You can perform the following service actions with extents of a scale-out backup repositories:

• Switch to Sealed Mode.

• Switch to Maintenance mode.

• Evacuate backups from extents.

Switching to Sealed Mode


Veeam Backup & Replication allows you to put any of the scale-out backup repository extents into the Sealed
mode.

1110 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Sealing up scale-out backup repository extents allows you to gradually remove data located on these extents by
applying a retention policy. You can use this feature to gracefully stop using some of your extents and exclude
them from the scale-out backup repository configuration.

After the extent is sealed, no further data is saved to the extent, and only read operations such as restore,
merge and remove are allowed.

Backup jobs that are targeted to a scale-out backup repository with the sealed extents that store active backup
chains are forced to create a new active full backup on the next run. Veeam Backup & Replication saves the new
active full to another available extent in the scale-out backup repository scope and forms a new active backup
chain. To select an extent where to keep the new active full, Veeam Backup & Replication compares available
resources of all extents and selects the best suitable extent.

NOTE

Consider the following:

• If you create backup jobs with the help of another Veeam backup solution (for example, Veeam
Agent), you will have to trigger active full backup job manually.
• If you use the per-machine backup chain format for backed-up data, the active full is forced for only
for machines which backups have active chains on the sealed extents.

Considerations and Limitations


Consider the following limitations:

• All restore points that exceed the specified retention period will be continuously removed from the sealed
extents on each subsequent backup session.

• When you put an extent into the Sealed mode, Veeam Backup & Replication restricts any further data
transfer to the extent. For more information on operation restrictions, see Sealed Mode Restrictions.

• All restore points that exceed the specified retention period will be continuously removed from the sealed
extent, as described in section Retention Policy.

• An object storage repository can be put into Sealed mode only if it is a member of the scale-out backup
repository.

If an object storage repository was not added as part of any of your scale-out backup repositories, the Seal
E x tent option will not be available.

• An extent can be put into both the Maintenance and the Sealed modes at the same time.
When both modes are applied, the Maintenance mode overrides Sealed mode.

To put an extent into the Sealed mode:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the scale-out backup repository under the Sca le-out Repositories node.

3. In the working area, select the extent and click Sea l extent on the ribbon or right-click the extent and
select Sea l extent.

1111 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To remove the extent from the Sealed mode, select the extent and click Sea led on the ribbon or right-click the
extent and select Sea led.

Sealed Mode Restrictions


The following table lists restrictions that are imposed right after the extent is put into Sealed mode.

Activity Restriction Level

Moving backups to object storage Restricted

Copying backups to object storage Restricted

Moving backups to capacity tier (manual operation) Restricted

Downloading data from object storage Allowed

Copying backups to performance tier (manual operation) Allowed

Moving backups to to performance tier (manual operation) Allowed

Restoring data from backup files residing on object storage Allowed

Exporting as .VBK file from backup files residing on object storage Allowed

Removing backups from configuration Allowed

1112 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Activity Restriction Level

Retention policies Allowed

Removing backups or VMs created with the per-machine method Allowed

Removing a VM from a single storage Allowed

Scale-out backup repository rescan Allowed

Evacuating backups Allowed

Switching to Maintenance Mode

Maintenance Mode
Veeam Backup & Replication allows you to put any of the scale-out backup repository extents into the
Maintenance mode. You can use this mode if you need to perform service actions, such as upgrading an extent
or installing a patch on it. Putting an extent into the Maintenance mode is mandatory to evacuate backups, as
described in section Evacuating Backups from Extents.

When you switch to the Maintenance mode, Veeam Backup & Replication launches the Repository Maintenance
job. The Repository Maintenance job checks the status of jobs and tasks targeted at the extent and puts the
extent to one of the following modes:

• If no tasks using the extent are currently running, the job puts the extent to the Maintenance mode
immediately.

• If the extent is busy with any task, for example, a backup job, the job puts the extent to the Maintenance
pending state and waits for the task to complete. When the task is complete, the extent is put to the
Maintenance mode.

Considerations and Limitations


Consider the following limitations:

• When you put an extent into the Maintenance mode, Veeam Backup & Replication restricts any further
data transfer to the extent and allows only operations listed in section Maintenance mode restrictions.

• An extent can be put into both the Maintenance and the Sealed modes at the same time. When both
modes are applied, Maintenance mode restrictions override restrictions of Sealed mode.

• You cannot restore VM data from backup files residing on the extent. You also cannot restore VM data
from backup files residing on other extents if a part of the backup chain resides on the extent in the
Maintenance mode.

• If an extent contains a part of an active backup chain on it, do NOT put this extent into the Maintenance
mode. Otherwise, the backup job targeted to the scale-out backup repository will fail. To avoid this, create
a full backup manually.

1113 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Putting Extent to Maintenance Mode
To put an extent into the Maintenance mode:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the scale-out backup repository under Sca le-out Repositories.

3. In the working area, select the extent and click Ma intenance Mode on the ribbon or right-click the extent
and select Ma intenance mode.

To remove the extent from the Maintenance mode, select the extent and click Ma intenance Mode on the ribbon
or right-click the extent and select Ma intenance mode once again.

Maintenance Mode Restrictions


The following table lists restrictions that are imposed right after the object storage repository is put into
Maintenance mode.

Activity Restriction Level

Moving to object storage. Restricted

Copying to object storage. Restricted

Downloading from object storage. Restricted

Moving to capacity tier (manual operation). Restricted

Copy to performance tier (manual operation). Restricted

1114 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Activity Restriction Level

Restore from offloaded backups. Restricted

Export as .vbk from offloaded backups. Restricted

Removal of backups or VMs created with the per-machine method. Restricted

Scale-out backup repository rescan. Allowed

Removal of backups from configuration. Allowed

Evacuation of storage along with indexes from on-premise extents. Allowed

Evacuating Backups from Extents


If you want to remove an extent from a scale-out backup repository, you first need to evacuate backups from
this extent. When you evacuate backups, Veeam Backup & Replication moves backup files from the necessary
extent to other extents within the same scale-out backup repository.

You can evacuate data from the following types of extents:

• Performance extents consisting of backup repositories

• Performance extents consisting of direct object storage repositories

• Capacity extents

How Evacuating Backups from Extents Works


Depending on the type of the extent, Veeam Backup & Replication applies different scenario to distribute data
between extents during evacuation.

Evacuation from Performance Extents Consisting of Backup Repositories


This scenario applies to data evacuation from performance extents consisting of backup repositories.

When Veeam Backup & Replication selects the target extent for evacuated files, it attempts to follow the
backup placement policy specified for remaining extents. For example, you have 3 extents in the scale -out
backup repository with the following backup file placement settings:

• On Extent 1, full backup files are stored.

• On Performance Extents 2 and 3, incremental backup files are stored.

If you evacuate backup files from Performance Extent 2, Veeam Backup & Replication will relocate them to
Performance Extent 3.

1115 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Evacuation from Capacity Extents and Object Storage Repositories Added as
Performance Extents
This scenario applies to data evacuation from performance extents consisting of direct object storage
repositories and capacity extents.

When Veeam Backup & Replication selects the target extent for evacuated files, it uses multiple conditions to
distributes data between extents. Data distribution depends on whether it is the first move or a subsequent
move of a backup chain.

To select an extent for backup file placement, Veeam Backup & Replication checks the following conditions:

1. During the first job session, Veeam Backup & Replication checks availability of extents. In case, an extent
is set to Sealed or Maintenance mode, these extents will be skipped from backup file placement.

2. After that, Veeam Backup & Replication checks the amount of backup chains in available extents and
selects the extent with a minimal amount of backup chains.

3. If some extents have storage space limitations, Veeam Backup & Replication calculates the average
storage of the backup chains located in all extents and select the extent that contains a minimum amount
of backup chains. If all extents have the same number of backup chains, Veeam Backup & Replication
selects the extent that has more free space.

4. During subsequent job sessions, Veeam Backup & Replication moves backup chains to the extent that was
specified before.

NOTE

If an extent is set to Sealed mode or Maintenance mode, Veeam Backup & Replication will not move
a backup chain to this extent. In this case, a new extent is selected and Veeam Backup & Replication
follows the same algorithm as during the first job session. The backup chain located in an unavailable
extent will be moved again to another extent. Veeam Backup & Replication will remove backup
chains from the unavailable extents according to retention policy.

Considerations and Limitations


Before you start the backups evacuation, consider the following:

• If performance extents consist of repositories with Fast Clone enabled, Veeam Backup & Replication
selects the target extent depending on the whether it contains data blocks that can be reused. In the
process of evacuation, Veeam Backup & Replication creates a new backup file in the target extent using
these data blocks. Therefore, evacuated backups do not occupy all space in the target performance
extent.

• For performance extents that consist of object storage repositories, Veeam Backup & Replication selects
the target performance extent as described in section Extent Selection for Object Storage Repositories
Added as Performance Extents.

• If immutability is enabled on the source extent, during evacuation the data blocks are copied to the target
extent. The data blocks are removed only when immutability expires.

NOTE

The data blocks are not removed after immutability expires, if you evacuated these data blocks from
object storage repositories added as performance extents of a scale-out backup repository. When the
immutability time period is over, you will need to delete these files manually.

1116 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you evacuate your backups from a hardened repository that is added as a performance extent,
Veeam Backup & Replication will copy these backups instead of moving. For more information, see
Hardened Repository as Performance Extent.

• You cannot evacuate data between backups repositories and direct backup object storage repositories.

Evacuating Backups from Extents


Before you evacuate backups from the extent, you must put it into the Maintenance mode. For more
information, see Switching to Maintenance Mode.

TIP

If you want to gracefully stop using some of your extents and exclude them from a scale -out backup
repository configuration, consider using the Sealed mode instead of evacuating backups.

To evacuate backup files from an extent:

1. [Recommended] Stop and disable jobs targeted at the extent from which you plan to evacuate backups.

2. Open the Ba ckup Infrastructure view.

3. In the inventory pane, select the scale-out backup repository under Sca le-out Repositories.

4. In the working area, select the extent and click Ma intenance Mode on the ribbon. Alternatively, you can
right-click the extent and select Ma intenance mode.

5. Select the extent and click E vacuate Backups on the ribbon. Alternatively, you can right-click the extent
and select E va cuate backups.

6. If you have disabled jobs, enable them.

7. After you evacuate backups, you can proceed to removing the extent from the scale -out backup
repository. For more information, see Removing Performance Extents from Scale-Out Repositories.

1117 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Monitoring Evacuating Backups
To monitor backups evacuation, do the following:

1. Open the History view.

2. In the inventory pane, click Sy stem.

3. In the working area, select the evacuation session and click Sta tistics on the ribbon or right-click the
evacuation session and select Sta tistics.

Stopping Evacuating Backups


You can stop the ongoing evacuation process.

Evacuation cannot be stopped immediately. If you stop evacuation in the middle of moving a large backup file,
Veeam Backup & Replication requires additional time to complete the process. Backup files that were not moved
to a new extent remain on the current extent.

To stop backups evacuation, do the following:

1. Open the History view.

2. In the inventory pane, click Sy stem.

1118 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the evacuation session and click Stop session on the ribbon or right-click the
evacuation session and select Stop session.

Receiving Scale-Out Backup Repository Reports


Veeam Backup & Replication is capable of sending reports that contain information about processing results of
your scale-out backup repositories data.

Consider the following:

• Reports are sent only after you have enabled and configured email notifications, as described in section
Configuring Global Email Notification Settings.

• Reports are sent daily at time specified in global notification settings.

• Reports are sent for all notification types selected in global notification settings, such as Success, Warning
and Failure.

• The title of a report is built up of " Scale-out Backup Repository " + a repository name. That said, if your
scale-out backup repository name is Amazon, then the report title will be Scale-out Backup Repository
Amazon.

Each report is divided into sections and contains the following information:

• P erformance Tier (upper-left) section:

o Used Space. Shows the used disk space of your scale-out backup repository.

o Ca pacity. Shows the total storage capacity of your scale-out backup repository.

• Ca pacity Tier (upper-right) section:

o Used Space. Shows the occupied storage space in your object storage repository.

o Sp a ce Limit. Shows the space limit (if any). A space limit is specified when adding a new object
storage repository, as described in section Adding Object Storage Repositories.

1119 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• P erformance Tier (middle) section:

o E x tent. Shows extents of a scale-out backup repository.

o Ca pacity. Shows the total storage capacities of your performance extents.

o Used Space. Shows the amount of disk space used on your extents.

o Sta tus. Shows the status of each extent, as described in section Description of Report Statuses.

• Ca pacity Tier (lower) section:

o E x tent. Shows the name of the capacity extent.

o Sp a ce Limit. Shows the space limit (if any).

o Used Space. Shows the occupied storage space in your capacity extent.

o Sta tus. Shows the status of the capacity extent, as described in section Description of Report
Statuses.

If an automatic offload job session exits with any status other than Success, you will see the
associated status message in this field. For more information about the offload job, see Moving
Inactive Backup Chains to Object Storage.

Description of Report Statuses


The following table lists possible combinations of Warning and Error messages shown under the Sta tus column
of a report.

If none of the conditions listed in the E x tent state column is true, then the report status will be shown as
Success.

E x tent type E x tent state Sta tus message Rep ort type

P erformance Maintenance mode Maintenance Warning


tier mode

Threshold limit exceeded. Threshold is specified in the Reaching Warning


Ba ckup storage section, as described in section capacity
Specifying Other Notification Settings.

Unavailable Offline Error

Ca pacity tier Maintenance mode Maintenance Warning


mode

Space limit exceeded. Space limit is specified when Out of capacity Error
adding a new object storage repository, as described
in section Adding Object Storage Repositories.

Unavailable Offline Error

1120 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
E x tent type E x tent state Sta tus message Rep ort type

Threshold limit exceeded. Threshold is specified in the Reaching Warning


Ba ckup storage section, as described in section capacity
Specifying Other Notification Settings.

Report Examples
Success Reports
The following figure shows an example of a report consisting of two performance extents ( Backup Volume 01
and Backup Volume 02); both share 253.3 GB of storage capacity, of which 52.4 GB is occupied.

Both extents have OK status, which means that neither extent was put into the Maintenance mode, nor has any
of these performance extents exceeded the allowed threshold limit.

This report also includes the Ca pacity Tier section consisting of a capacity extent with no Sp a ce Limit applied.
This capacity extent stores 29.6 GB of data and has the OK status.

Warning Reports
The figure below demonstrates a report with the Warning status.

1121 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
As per example, the Backup Volume 01 performance extent has been put into the Maintenance mode, and the
Backup Volume 02 performance extent has exceeded the allowed threshold both of which have caused a report
to be generated with the Warning status.

Error Reports
In the figure below a report has been generated with the Error status caused by the Amazon S3 Object Storage
performance extent which has exceeded its allowed space limit.

Removing Backups from Capacity or Archive Tier


To remove moved or copied backups from capacity or archive extent, use the Delete from d isk feature, as
described in section Deleting Backups from Object Storage Repositories.

1122 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Consider the following:

• When removing offloaded backup files from the backup chain that was created with the per -machine
method, the associated blocks of data will be removed from the capacity or archive extent altogether.

For more information about per-machine backups, see Backup Chain Formats.

• When removing offloaded backup files from the backup chain that was created as a single -file backup file,
then nothing will be removed until either of the following occurs:

o All the VMs were removed from the backup.

o The backup itself was removed.

• Immutable backups cannot be removed.


For more information, see Immutability.

• If the capacity or archive extent has been put into the Maintenance mode, the removal of data from such a
repository is not possible until the extent is removed from the Maintenance mode.

For more information, see Switching to Maintenance Mode.

• During data removal, the entire folder structure starting from the repository folder ( <backup_id>) will
be completely purged.

For more information on how Veeam Backup & Replication stores data in the capacity extent, see Capacity
Extent Structure.

• If backup files with metadata that are located on your extents have been removed locally in any way other
than by using the Deleting from Disk feature, Veeam Backup & Replication will not be able to synchronize
the backup chain state with that of the capacity or archive extent. Therefore, the offloaded blocks of data
will continue to remain in cloud storage. To remove such blocks, use your cloud platform abilities.

Rebalancing Extents of Scale-Out Backup Repositories


To maintain Backup File Placement policies and distribute backup data between performance extents evenly,
you can use a rebalance. It can be useful if one of the performance extents of your scale-out backup repository
contains more data than the other extents.

You can use the rebalance to distribute data within extents according to this policy in the following cases:

• To maintain the current placements policy. If data within performance extents is not distributed according
to the placement policy and some extent contains more backups than the others, you can rebalance these
extents.

• To change the placement policies. If you have switched from one type of policy to another, for example
from Data locality policy to Performance placement policy, the rebalance will help to distribute data
according to a new policy.

After you start the rebalance, Veeam Backup & Replication will scan performance extents and backup files
located on these extents. In case some backup chain does not meet the backup placement policy,
Veeam Backup & Replication will check all available performance extents, analyze their total space and amount
of free space and will evaluate the best way to distribute data between extents. After that,
Veeam Backup & Replication will move backup chains from the source extent to a new extent.

Depending on the mechanisms that are used to store data on extents, Veeam Backup & Replication chooses one
of the following algorithm to perform the rebalance:

• Common rebalance — Veeam Backup & Replication uses this type of the rebalance, if a scale-out backup
repository contains at least one extent that uses the data deduplication or block cloning technologies.

1123 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Deduplication rebalance — Veeam Backup & Replication uses this type of the rebalance, if all extents of a
scale-out backup repository use the data deduplication, block cloning technologies and applies the data
locality placement policy.

Considerations and Limitations


Before you start the rebalance, consider the following:

• The rebalance option is not supported for object storage repositories added as performance extents of the
scale-out backup repository.

• If you use the ReFS Microsoft Windows file system or XFS Linux file system as performance extents,
Veeam Backup & Replication will apply Data Deduplication to backup files.

• Veeam Backup & Replication skips from rebalance immutable backups located on immutable extents and
hardened repositories added as extents of the scale-out backup repository.

• Veeam Backup & Replication does not rebalance the following types of extents:

o Capacity tier extents.

o Archive extents.

o Performance extents that are set to the Maintenance mode.

• Before you perform the rebalance, you must stop all activities (for example, backup jobs, restore
operations and so on) that are related to the scale-out backup repository.

• You must stop the backup jobs created by Veeam Plug -in for Microsoft SQL Server or Veeam Plug-in for
Oracle RMAN.

How Rebalance of Scale-Out Backup Repositories Works


After you start a rebalance, Veeam Backup & Replication performs the following steps:

1. The rebalance session starts.

2. Veeam Backup & Replication gets a list of available extents.

3. All available extents are set to the Maintenance mode.

4. Veeam Backup & Replication checks extents configuration and selects the best algorithm to perform the
rebalance.

5. Veeam Backup & Replication checks if data is distributed across extents according to the placement policy.
If at least one backup files does not meet the placement policy, the whole chain on the extents is marked
as a violator.

6. Veeam Backup & Replication checks the capacity of every extent, prioritize them according to the
placement policy and optimal free space.

7. Veeam Backup & Replication chooses the preferred extent to keep data.

8. Veeam Backup & Replication starts to evacuate data from the current extents and distribute it to the
preferred extent.

9. After the data is distributed, extents are removed from the Maintenance mode.

1124 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Rebalancing Extents of Scale-Out Backup Repositories
To start a rebalance session, you must press and hold the [Ctrl] key on your keyboard while you right -click the
necessary scale-out backup repository and select Reb alance. After that Veeam Backup & Replication will start a
session that will show details on how data is moved from one performance extent to another performance
extent.

TIP

If you want to exclude a specific performance extent from rebalance, set to the Maintenance mode.

Removing Scale-Out Backup Repositories


You can remove a scale-out backup repository at any time. When you remove a scale-out backup repository,
Veeam Backup & Replication unassigns the extent role from all the backup repositories configured into it, and
they become individual backup repositories. Backup files are not removed from the backup repositories — they
remain on the disk or an object storage repository.

You cannot remove a scale-out backup repository if at least one job is targeted at it. First, you must move all
backup files to the new backup repository and then retarget the jobs. For details, see this Veeam KB article.

To remove a scale-out backup repository:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click Sca le-out Repositories.

1125 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the scale-out repository and click Remove Repository on the ribbon or right-
click the backup repository and select Remove.

1126 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Guest Interaction Proxies
The guest interaction proxy is a backup infrastructure component that sits between the backup server and
processed VM. This component is needed if the backup or replication jobs perform the following processing of
VMs:

• Application-aware processing

• Guest file system indexing

• Transaction logs processing

To interact with the VM guest OS, Veeam Backup & Replication needs either to install non-persistent runtime
components or use (if necessary, install) persistent agent components in each VM. The task of deploying these
components in a VM is performed by the guest interaction proxy. For more information on the components, see
Non-Persistent Runtime Components and Persistent Agent Components.

NOTE

The guest interaction proxy functionality is included in the Veeam Universal License. When using a legacy
socket-based license, Enterprise or higher edition is required.

The guest interaction proxy allows you to communicate with the VM guest OS even if the backup server and
processed VM run in different networks.

IMP ORTANT

The guest interaction proxy deploys the non-persistent runtime components or persistent agent
components only in Microsoft Windows VMs. In VMs with another guest OS, the non-persistent runtime
components or persistent agent components are deployed by the backup server.

Guest Interaction Proxy Deployment


You can use multiple guest interaction proxies to improve performance. Multiple guest interaction proxies will
deploy non-persistent runtime components or persistent agent components in VMs faster compared to the
same operation performed by one guest interaction proxy.

In a backup infrastructure with multiple remote sites, you can deploy a guest interaction proxy in each site. This
can reduce load on the backup server and produce less traffic between the backup server and remote site.

1127 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Guest Interaction Proxy
A machine performing the role of a guest interaction proxy must meet the following requirements:

• The role of a guest interaction proxy can be assigned to a Microsoft Windows server (physical or virtual).

• You must add the machine to the Veeam Backup & Replication console as a managed server.

• Guest interaction proxy must have a LAN connection to the VM that will be backed up or replicated.

• If you plan to use PowerShell Direct connection to back up VMs that reside on Hyper -V Server 2016 (or
later) and run Microsoft Windows 10 (or later) or Microsoft Windows Server 2016 (or later), the guest
interaction proxy must have Microsoft PowerShell 2.0 (or later) installed.

The guest interaction proxy role can be performed by any machine that meets the requirements, including off-
host backup proxy, backup repository, WAN accelerator, Microsoft Hyper -V host or backup server.

Guest Interaction Proxy Selection


When you add a Microsoft Windows machine to the backup infrastructure, Veeam Backup & Replication deploys
Veeam Data Mover on it. Veeam Data Mover includes the components responsible for deployment of non-
persistent runtime components or persistent agent components during guest OS interaction.

To assign a guest interaction proxy for the job, you must select a Microsoft Windows machine that will perform
the role of the guest interaction proxy at the Guest Processing step of the backup or replication job wizard. You
can assign the guest interaction proxy manually, or let Veeam Backup & Replication do it automatically.
Veeam Backup & Replication uses the following priority rules to select the guest interaction proxy:

1. A machine in the same network as the protected VM that does not perform the backup server role.

2. A machine in the same network as the protected VM that performs the backup server role.

3. A machine in another network that does not perform the backup server role.

4. A machine in another network that performs the backup server role.

1128 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If Veeam Backup & Replication finds several available machines of equal priority, it selects the less loaded
machine. The load is defined by the number of tasks that the machine already performs.

Failover from Guest Interaction Proxy to Backup Server


If the guest interaction proxy fails to connect to a Microsoft Windows VM, the guest interaction proxy will not
be able to access the VM and deploy non-persistent runtime components or persistent agent components in it.
In this case, the backup server will take over the role of guest interaction proxy and deploy the non-persistent
runtime components or persistent agent components in the VM.

1129 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Gateway Servers
A gateway server is an auxiliary backup infrastructure component that “bridges” the backup server and backup
repository. It can also "bridge" a source backup repository and a target backup repository in case of backup copy
jobs. The gateway server is required if you deploy the following types of backup repositories in the backup
infrastructure:

• Shared folder backup repositories

• Dell Data Domain deduplicating storage appliance

• HPE StoreOnce deduplicating storage appliance

• Object storage repository

Such backup repositories cannot host Veeam Data Movers — Veeam components that establish a connection
between a backup proxy and backup repository (in case of backup jobs) or between backup repositories (in case
of backup copy jobs). To overcome this limitation, Veeam Backup & Replication uses gateway servers.

In the backup infrastructure, a gateway server hosts the target Veeam Data Mover. Veeam Backup & Replication
establishes a connection between the source Veeam Data Mover and target Veeam Data Mover, and transports
data from/to backup repositories through gateway servers.

For more information on using gateway servers in backup copy jobs, see Backup Copy Architecture.

Requirements and Limitations for Gateway Servers


Consider the following:

• The gateway server can run on a Microsoft Windows or Linux machine or Microsoft Hyper -V host that is
added to the backup infrastructure as a managed server. The machine must meet the system
requirements. For more information, see System Requirements.

• The role of a gateway server for Dell Data Domain, HPE StoreOnce storage appliances or SMB repositories
must be assigned to a Microsoft Windows machine.

• The role of a gateway server for NFS or object storage repositories can be assigned to a Microsoft
Windows or Linux machine.

• The machine must have access to the backup repository — shared folder, Dell Data Domain or HPE
StoreOnce.

1130 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• For deduplicating storage appliances working over Fibre Channel, you must explicitly select at least one
gateway server that will communicate with the appliance over Fibre Channel connection.

• For HPE StoreOnce deduplicating storage appliances, you must assign the role of a gateway server to a
64-bit machine.

• If connection to the gateway server is lost during the job run, the job fails. Veeam Backup & Replication
selects a new available gateway server when the job starts next time.

Gateway Server Deployment


To configure a gateway server, you must first add a machine that you plan to use as a gateway server to the
backup infrastructure using the New W indows Server or New Linux Server wizard. For more information, see
Adding Microsoft Windows Servers or Adding Linux Servers.

After that, you must go through the New Backup Repository wizard and define gateway server settings. For
more information, see Adding Backup Repositories. You can select a gateway server explicitly or instruct
Veeam Backup & Replication to select it automatically.

If you plan to select gateway servers explicitly, these servers must be located as close to the backup repository
as possible. However, if you use a deduplicating storage appliance with source-side data deduplication, it is
reasonable to assign the roles of gateway servers to machines that are located closer to the backup proxy. This
will help you reduce the amount of traffic traveling over the network. For more informa tion, see Dell Data
Domain and HPE StoreOnce.

Gateway Selection
Whenever possible, Veeam Backup & Replication distributes the backup workload between multiple available
gateway servers. This helps optimize performance of multiple concurrent tasks. Veeam Backup & Replication
assigns a separate gateway server for each task, based on gateway server connectivity and their current load. If
the number of tasks is greater than the number of available gateway servers, Veeam Backup & Replication uses
one gateway server for multiple tasks.

Veeam Backup & Replication uses one gateway server for the whole job if the Use per-machine backup files
option is disabled for the repository to which the job is targeted at. For more information on this option, see
Backup Chain Formats.

You can select gateway servers explicitly or instruct Veeam Backup & Replication to select them automatically.
For more information on which backup infrastructure components Veeam Backup & Replication uses as gateway
servers during automatic selection, see the Automatic Selection section.

Manual Gateway Selection


If you select gateway servers explicitly, Veeam Backup & Replication uses only the selected servers and
performs all operations on them. Veeam Backup & Replication analyzes the gateway server connectivity and
their current task load, and picks the most suitable gateway server for the next task.

IMP ORTANT

If you select only one gateway server explicitly and it is not accessible, the job will fail.

1131 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Automatic Gateway Selection
If you instruct Veeam Backup & Replication to select gateway servers
automatically, Veeam Backup & Replication uses the backup infrastructure components described in the
following table. Note that principles described in the Gateway Selection section also apply. If the primary
selection gateway server is not accessible, Veeam Backup & Replication fails over to the next available option.

Ty p e of job Comp onent used as gateway server Comp onent used as gateway server for
sy nthetic operations

Ba ckup job / File Backup proxy (onhost or offhost) Synthetic operations are performed on the
b a ckup job mount server associated with the backup
repository. If the mount server is not
accessible, Veeam Backup & Replication fails
over to the backup server.

Ba ckup copy job / For backup copy and file copy jobs, the Synthetic operations are performed on the
File backup copy selected gateway depends on the type mount server associated with the backup
job of the source backup repository: repository. If the mount server is not
accessible, Veeam Backup & Replication fails
• Direct attached repository. The
over to the backup server.
mount server associated with the
backup repository is used as the These rules are applied to the direct data
path and processing over WAN accelerators.
gateway server. If the mount File backup copy job does not support WAN
server is not accessible, accelerators.
Veeam Backup & Replication fails
over to the backup server.
• Object storage repository with
the direct connection mode. The
source backup repository is used
as the gateway server.
• Backup repository with the
gateway server connection. The
gateway of the source backup
repository is used.
• Hardened repository. The mount
server associated with this
repository is used as the gateway
server.

For backup copy jobs that work over


WAN accelerators, the role of a
gateway server is assigned to source or
target WAN accelerator (depending on
the shared folder backup repository
location). File backup copy job does not
support WAN accelerators.

1132 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ty p e of job Comp onent used as gateway server Comp onent used as gateway server for
sy nthetic operations

Ta p e job If there is a direct connection between Synthetic operations are performed on the
a backup repository and tape device, mount server associated with the backup
the role of a gateway server is assigned repository. If the mount server is not
to the tape server. accessible, Veeam Backup & Replication fails
over to the backup server.
Otherwise, the role of a gateway server
is assigned to the backup server.

Veeam Agent Mount server associated with the Synthetic operations are performed on the
b a ckup job backup repository. If the mount server mount server associated with the backup
is not accessible, repository. If the mount server is not
Veeam Backup & Replication fails over accessible, Veeam Backup & Replication fails
to the backup server. over to the backup server.

Ba ckup job created Backup server. —


b y Veeam Plug-in
for Oracle
RMAN/SAP
HANA/SAP on
Ora cle/Microsoft
SQL Server/DB2

Restore operations Backup proxy used for a restore —


operation*.

Rep lication from Target backup proxy assigned for a —


b a ckup replication operation*.

Rep ository rescan Mount server associated with the —


backup repository.

1133 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ty p e of job Comp onent used as gateway server Comp onent used as gateway server for
sy nthetic operations

Move and copy If you copy or move backups to an —


op erations object storage repository with the
direct connection mode, the selected
gateway depends on the type of the
source backup repository:
• Direct attached repository. The
source backup repository is used
as the gateway server.**
• Non-direct attached repository.
The gateway of the source
backup repository is used.
• Object storage repository with
the direct connection mode. The
mount server associated with the
source backup repository is used
as the gateway server. If the
mount server is not accessible,
Veeam Backup & Replication fails
over to the backup server.
• Object storage repository with
the gateway server connection.
The gateway of the source
backup repository is used.

If you copy or move backups to other


non-direct attached backup repository,
the role of the gateway server is
assigned to mount server. If mount
server is not accessible,
Veeam Backup & Replication fails over
to the backup server.

Hea lth check Mount server associated with the —


op eration backup repository.

* [For repositories for which Linux gateway servers cannot be used — Dell Data Domain, HPE StoreOnce and SMB]: If the
backup proxy is a Linux machine, the role of the gateway server is assigned to the mount server associated with the backup
repository. If the mount server is not accessible, Veeam Backup & Replication fails over to the backup server.
**[For hardened repository]: The role of the gateway server is assigned to the mount server.

Related Topics
• Scale-Out Backup Repository

• Specifying Server or Shared Folder Settings

1134 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Mount Servers
The mount server is a server required for restores that work with guest OS files and application items. To access
files or items stored in a backup file, Veeam Backup & Replication mounts the content of the backup to the
mount server. Only after the content is mounted, Veeam Backup & Replication can get files and copy them to
the restore destination.

The mount server is required if you perform the following operations:

• Guest OS file restore

• Application items restore

• Secure restore

• Instant file share recovery

• Restore of specific objects from file backup and object storage backup

To reduce the load on the network and speed up the restore process, the mount server must be located in the
same site as the backup repository where backup files are stored. In this case, you will be able t o keep the traffic
in one site. If the mount server is located in some other site, the data will travel across the network between the
sites.

NOTE

In some scenarios, Veeam Backup & Replication can mount content of backups to machines other than
mount servers. For more information, see Restore Scenarios and Mount Points.

Mount Server Deployment


The mount server is created for every backup repository and is associated with it. When you configure a backup
repository, you specify to which server you want to assign the role of the mount server.

You can assign the mount server role to any 64-bit Microsoft Windows machine added to the backup
infrastructure. This machine and the backup repository must be located as close to each other as possible. If you
have several sites, we recommend you configure at least one mount server in each site.

By default, Veeam Backup & Replication suggests assigning the mount server role to the following
infrastructure components depending on the OS of the backup repository:

• For Microsoft Windows backup repositories, Veeam Backup & Replication suggests the backup repository
itself.

1135 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• For Linux, shared folder backup repositories and deduplicating storage appliances,
Veeam Backup & Replication suggests the backup server.

NOTE

Consider the following:

• For scale-out backup repositories, you must specify the mount server for every extent.
• For cloud repositories and hosts that store replicas or backups from storage snapshots, the mount
server role is assigned to the backup server. For such repositories, you cannot assign the mount
server role to a different machine.

Mount Server Services and Components


Mount servers run light-weight services that take a few seconds to deploy. Deployment is fully automated.
Veeam Backup & Replication installs the following services:

• Veeam Mount Service mounts backups and replicas for file-level access, browsing the guest file system
and restoring guest OS files and application items.

• Veeam Data Mover handles traffic.

• Veeam vPower NFS Service (if you enable it when configuring the mount server).

Requirements for Mount Servers


A machine that performs the role of a mount server must meet the following requirements:

• The machine must meet the system requirements. For more information, see System Requirements.

• The mount server must have access to the backup repository with which it is associated and to the original
VM (the VM to which you restore files or application items).

1136 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Data Mover Service
Veeam Data Mover performs data processing tasks on behalf of Veeam Backup & Replication, such as retrieving
source machine data, performing data deduplication and compression, and storing backed -up data on the target
storage.

Veeam Data Mover can be persistent or non-persistent:

• For Microsoft Windows servers, Veeam Data Movers are persistent, that is, Veeam Data Mover is uploaded
and installed on a server only once.

Veeam Backup & Replication automatically installs Veeam Data Mover when you add a Microsoft Windows
server to the backup infrastructure.

• For Linux servers, Veeam Data Movers can be persistent or non-persistent:

o Non-persistent Veeam Data Mover is uploaded and removed each time Veeam Backup & Replication
addresses a server.

o For Veeam Data Mover to be persistent, you must specify an account with root or equivalent to root
permissions when adding a Linux server. Persistent Veeam Data Movers are required for hardened
repositories. For other backup infrastructure components based on Linux servers, Veeam Data Movers
can be persistent or non-persistent.

If you do not want to provide root or equivalent to root permissions, specify an account with non-root
permissions. In this case, Veeam Data Movers will be non-persistent. Veeam Backup & Replication will
upload and start Veeam Data Movers through the SSH connection when Veeam Backup & Replication
addresses the server.

Requirements and Limitations for Veeam Data Movers


Before you use Veeam Data Movers, consider the following requirements and limitations:

• For Microsoft Hyper-V and Microsoft Windows servers:

o File and printer sharing must be enabled in network connection settings of the added server.

o Make sure the user account that you use to add a Microsoft Windows server is in the local
administrators group on the server being added.

• For Linux servers:

o Linux server version must be 64-bit. For more information, see System Requirements. Note that Perl
is required only for non-persistent Veeam Data Movers. Check the full list of required Perl modules in
this Veeam KB article.

o Veeam Backup & Replication does not install Veeam Data Movers on deduplicating storage appliances
based on Linux.

o Make sure the user account that you use to add a Linux server has required permissions:

▪ If you want to use persistent Veeam Data Movers, the user account specified for the server must
have root or elevated to root permission. Otherwise, Veeam Data Movers will be non-persistent,
that is, the Linux server will not host Veeam Data Movers permanently.

▪ For hardened repository, when you add a Linux server with single-use credentials, the user
account must still have elevated to root permission in order for Veeam Data Movers to be
persistent. For more information, see Step 3. Specify Linux Server.

1137 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

If Veeam Data Mover on a Linux server fails for some reason, you can re-install it manually. For more
information, see this Veeam KB article.

1138 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
WAN Accelerators
WAN accelerators are dedicated components that Veeam Backup & Replication uses for WAN acceleration. WAN
accelerators are responsible for global data caching and data deduplication.

Technically, WAN accelerators add a new layer in the backup infrastructure — between Veeam Data Movers on
the source side and the Veeam Data Mover on the target side.

WAN Accelerators Deployment


To enable WAN acceleration and data deduplication technologies, you must deploy a pair of WAN accelerators in
your backup infrastructure.

• One WAN accelerator is deployed on the source site, closer to the source backup repository or source host.

• The other WAN accelerator is deployed on the target site, closer to the target backup repository or target
host.

On each WAN accelerator Veeam Backup & Replication creates the VeeamWAN folder containing the following
data:

• The VeeamWAN folder on the source WAN accelerator stores files with digests required for deduplication.
For more information, see How WAN Acceleration Works.

• The VeeamWAN folder on the target WAN accelerator stores global cache data.

NOTE

Global cache is not used if both WAN accelerators in the pair (the source one and the target one)
operate in the Hig h bandwidth mode.

To learn how to add a WAN accelerator to the Veeam Backup & Replication infrastructure, see Adding WAN
Accelerators.

1139 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Recommendations for WAN Accelerators
You should not assign one source WAN accelerator to several jobs to remote locations that you plan to run
simultaneously. The source WAN accelerator requires a lot of CPU and RAM resources, and does not process
multiple tasks in parallel. As an alternative, you can create one job to the remote location for all VMs you plan
to process over one source WAN accelerator.

The target WAN accelerator, however, can be assigned to several jobs to remote locations.

1140 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
WAN Global Cache
From the technical point of view, the global cache is a folder on the target WAN accelerator. By default, global
cache data is stored in the VeeamWAN folder on the disk with the most amount of space available. However, you
can define any folder of your choice when you configure the target WAN accelerator.

NOTE

Global cache is not used if both WAN accelerators in the pair (the source one and the target one) operate in
the Hig h bandwidth mode .

By default, the size of the global cache is 100 GB. You can increase the size or decrease it if necessary. The more
space you allocate, the more repeating data blocks will be written to the global cache and the more efficient
WAN acceleration will be. It is recommended that you allocate at least 40 GB to the global ca che storage.

The global cache size is specified per source WAN accelerator. That is, if you plan to use one target WAN
accelerator with several source WAN accelerators, the specified amount of space will be allocated for every
source WAN accelerator that will be working with the target WAN accelerator and the size of the global cache
will increase proportionally. For more information, see WAN Accelerator Sizing.

The WAN global cache is a “library” that holds data blocks repeatedly going from the source side to the target
side. The global cache is populated at the first cycle of a job to the remote location. The priority is given to data
blocks of Windows-based OSes, other OSes like Linux/Unix, and Microsoft Exchange Server.

Veeam Backup & Replication constantly maintains the global cache in the actual state. To do that, it
continuously monitors data blocks going over WAN and data blocks in the global cache.

• If some new data block is constantly sent over WAN, it is added to the global cache.

• If some data block in the global cache is not sent over WAN and are not re-used for some period of time, it
is removed from the global cache to make room for new data blocks.

Veeam Backup & Replication also performs periodic consistency checks. If some data block in the global cache
gets corrupted, Veeam Backup & Replication removes it from the global cache.

The efficiency of the WAN acceleration increases with every new backup copy interval in the backup copy job.
During the first backup copy interval in the backup copy job, the WAN acceleration level is minimal.
Veeam Backup & Replication populates the global cache. With every new job cycle, Veeam Backup & Replication
updates the global cache to include the most “popular” data blocks and the WAN acceleration efficiency
increases.

NOTE

You can populate the global cache before you run the job to the remote location for the first time. In this
case, Veeam Backup & Replication will use the global cache starting from the first session of the job to the
remote location, and the WAN traffic will be minimal. For more information, see Population of Global
Cache.

Many to One WAN Acceleration


The WAN global cache can be used by several source WAN accelerators simultaneous ly. For example, if you have
several remote/branch offices, you can configure several source WAN accelerators in remote sites and one
target WAN accelerator in the head office.

1141 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
In this case, the global cache will hold cache data for separate source WAN accelerators. The cache data for
every source WAN accelerator will be stored in a dedicated subfolder in the global cache folder.

When one target WAN accelerator is used by several source WAN accelerators, Veeam Backup & Replication can
copy data blocks between global cache of these WAN accelerators. This mechanism works if there are no
matching backups of VMs in the target backup repository, but matching data is available in cache of other WAN
accelerators.

For example, you have two backup copy jobs: Job 1 and Job 2. The Job 1 uses the source WAN accelerator Source
1 and the target WAN accelerator Target 3. The Job 2 uses the source WAN accelerator Source 2 and the same
target WAN accelerator Target 3. In the global cache folder, Veeam Backup & Replication will store data for 2
WAN accelerators: Source 1 and Source 2.

• Job 1 processes a VM running Microsoft Windows Server 2008 R2, and it has been running for some time.
In the global cache, there is already data for this type of OS.

• Job 2 also processes a VM running Microsoft Windows Server 2008 R2. When you start Job 2 for the first
time, there is no data for this type of OS in the global cache for Source 2 WAN accelerator. In such
situation, Veeam Backup & Replication will copy the necessary data block from the Source 1 cache to the
Source 2 cache and will not transport this data block over WAN.

NOTE

Beside using global cache of other WAN accelerator, Veeam Backup & Replication also utilizes backup files
residing in the backup repository. For example, if the backup repository contains a backup file created by a
backup job and the backup copy job starts copying a backup of a VM of the same type,
Veeam Backup & Replication will populate global cache on the WAN accelerator from the backup fil e not to
transfer redundant data over WAN.

Manual Population of Global Cache


You can manually pre-populate the global cache to avoid the situation where the cache remains empty. As a
result, by the time a job to the remote location starts, the global cache will contain data blocks that can be used
for data deduplication.

Manual population of the global cache can be helpful in the following scenarios:

• First run of a job to the remote location. When you run a first session of a job to the remote location, the
global cache is empty, and the whole amount of VM data needs to be transferred over WAN. It is
recommended that you manually populate the global cache before you start a job to the remote location
for the first time.

1142 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Global cache corruption. If the global cache gets corrupted for some reason, Veeam Backup & Replication
needs to perform at least one session of the job to the remote location to replace corrupted data blocks
with valid data blocks. In this situation, you can clean the global cache and manually populate it with valid
data before the job to the remote location begins.

IMP ORTANT

Veeam Backup & Replication does not use encrypted backups for manual global cache population.

Limitations for Manual Population of Global Cache


The manually performed global cache population task has the following limitations:

• Veeam Backup & Replication does not use encrypted backups for global cache population.

• Veeam Backup & Replication writes only data blocks for Windows-based OSes to the default cache. Data
blocks for other OSes like Linux/Unix and application data blocks are not written to the cache.

• You can start the global cache population task for the target WAN accelerator that is not currently used by
any job to the remote location.

• If the global cache population task is currently running, the target WAN accelerator is locked. You cannot
start any job to the remote location by using this target WAN accelerator.

• [For global cache corruption scenario] You must clean the global cache before you popul ate it with valid
data.

• [Veeam Cloud Connect] Veeam Backup & Replication does not use tenant backups to populate global
cache on the service provider side.

How Manual Population of Global Cache Works


Global cache population is a manual operation performed by the user. When you run the global cache
population task, Veeam Backup & Replication creates a ‘default cache’ on the target WAN accelerator. The
default cache is used as a basic, universal cache for every new job to the remote location.

To populate the default cache, Veeam Backup & Replication uses backup files stored in backup repositories as a
source of data.

The procedure of global cache population includes the following steps:

1. The user manually starts the global cache population tasks and selects backup repositories from which
data blocks should be retrieved.

2. Veeam Backup & Replication scans backup repositories and makes up a list of OSes whose data blocks are
available in backup files.

3. Veeam Backup & Replication copies data blocks from backup repositories and populates the default cache
with these data blocks.

1143 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
When a job to the remote location starts, Veeam Backup & Replication renames the default cache to a folder for
the source WAN accelerator engaged in the job. As a result, Veea m Backup & Replication can use data blocks in
this folder for deduplication starting from the very first session of the job to the remote location.

In many-to-one WAN accelerator deployment scenarios, the global cache may have folders for other source
WAN accelerators, and these folders may contain data blocks for some OSes. If the global cache already contains
some data, the procedure of global cache population includes the following steps:

1. The user manually starts the global cache population tasks and selects backup repositories from which
data blocks should be retrieved.

2. Veeam Backup & Replication scans backup repositories and makes up a list of OSes whose data blocks are
available in backup files.

3. Veeam Backup & Replication scans folders for other source WAN accelerators in the global cache and
makes up a list of OSes whose data blocks are available there.

4. The list of OSes in the global cache is compared to the list of OSes in backup repositories. This way,
Veeam Backup & Replication detects data blocks for which OSes are missing in the global cache.

5. In the global cache, Veeam Backup & Replication detects a folder with the maximum amount of data. This
folder is used as a basis for the default cache.

6. Veeam Backup & Replication copies data blocks only for missing OSes from backup repositories and
populates the default cache with these blocks. Data blocks for OSes available in folders for other source
WAN accelerators are not copied to the default cache during the population task.
Veeam Backup & Replication copies these data blocks on the fly, when a job to the remote location runs.
For more information, see Many to One WAN Acceleration.

1144 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Manually Populating Global Cache
To manually populate the global cache:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select the W AN Accelerators node.

3. In the working area, right-click the target WAN accelerator and select P op ulate cache.

If the selected WAN accelerator is not assigned as a target WAN accelerator to any job to the remote
location, Veeam Backup & Replication will display a warning.

4. In the Source Backup Repositories window, select backup repositories from which OS data blocks must be
retrieved.

It is strongly recommended that you select backup repositories on the same site where the target WAN
accelerator is located. In the opposite case, the traffic will travel between sites, which will increase load
on the network.

5. Click OK.

Clearing Global Cache


You can clear the global cache on the target WAN accelerator. It is recommended that you clear the global cache
in the following situations:

• Global cache is corrupted.

• Global cache contains data that is no longer needed. This situation may occur, for example, if you have
decided to fully switch to the Hig h bandwidth mode that does not use the global cache data.

In such cases, it is recommended that you clear the global cache and populate it anew before you start jobs to
remote locations processing new types of VMs.

To clear the global cache:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, click W AN Accelerators.

1145 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click the target WAN accelerator and select Clear cache.

IMP ORTANT

Consider the following:

• Before you clear the global cache, make sure that you do not have any running jobs that use this
target WAN accelerator. When the global cache is cleared, Veeam Backup & Replication will restart
the Veeam WAN Accelerator Service, and running jobs will comp lete with the Failed status.
• When you clear the global cache, you also clear all digest data stored at this WAN accelerator.

1146 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
WAN Accelerator Sizing
To ensure correct work of remote jobs over WAN accelerators, you must provide enough free space for service
data on source and target WAN accelerators.

When configuring WAN accelerators, note that there can be situations when WAN acceleration switches from
the Hig h bandwidth mode to the Low b andwidth mode : for example, the link to the remote location changes
and you decide to disable the Hig h bandwidth mode for one of the accelerators in the pair. If you disable the
Hig h bandwidth mode and start a job which utilizes this WAN accelerator, Veeam Backup & Replication deletes
digest data that was used in the Hig h bandwidth mode and recreates it for the Low b andwidth mode. Besides,
Veeam Backup & Replication will also use the global cache at the target WAN accelerator.

To avoid problems caused by the lack of free space when switching from the Hig h bandwidth mode to the Low
b a ndwidth mode, we recommend that you configure WAN accelerators as if you planned to use them in the Low
b a ndwidth mode.

Source WAN Accelerator


When you run a remote job over WAN accelerators, Veeam Backup & Replication analyses data blocks going to
target and calculates digests for these data blocks. Digests data is stored on the source WAN accelerator, in the
VeeamWAN folder on the disk that you select when you configure the WAN accelerator.

You must make sure that there is enough disk space on the source WAN accelerator to store digest data.

The amount of disk space required for a source WAN accelerator operating in the Low b andwidth mode is
calculated by the following formula:

Digest Size = 2% of Provisioned VM Size

1147 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For example, if you plan to process 10 VMs whose provisioned size is 2 TB, you must allocate 40 GB of disk
space for digest data on the source WAN accelerator operating in the Low b andwidth mode.

The amount of disk space required for a source WAN accelerator operating in the Hig h bandwidth mode is
calculated by the following formula:

Digest Size = 1% of Provisioned VM Size

For example, if you plan to process 10 VMs whose provisioned size is 2 TB, you must allocate 20 GB of disk
space for digest data on the source WAN accelerator operating in the Hig h bandwidth mode.

You can increase the throughput by adjusting the number of upload streams. To learn how to configure them on
the source WAN accelerator, see the Choose Server step of the New W AN Accelerator wizard.

Target WAN Accelerator


You must make sure that you provide enough free space for the following data on the target WAN accelerator:

• Global cache data

• Digest data

NOTE

For the target WAN accelerator operating in the Hig h bandwidth mode only, you must provide enough free
space to generate digest data. Global cache data is not used in the Hig h bandwidth mode.

When you enable the Hig h bandwidth mode for an existing WAN accelerator, Veeam Backup & Replication
does not automatically remove the global cache that was previously used for acceleration. If you are
planning to use the Hig h bandwidth mode for WAN acceleration and you do not need the global cache
anymore, you can free the disk space by manually removing the cache. If you are planning to use WAN
acceleration in the Low b andwidth mode in the future, we recommend that you keep the global cache. You
can disable the Hig h bandwidth mode and switch back to the Low b andwidth mode at any time.

1148 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Global Cache Data
Global cache is stored on the target WAN accelerator, in the VeeamWAN folder on the disk that you select when
you configure the WAN accelerator. The size of global cache is specified in the properties of the target WAN
accelerator.

You must provide enough free space for global cache data. It is recommended that you provide 10 GB per every
type of OS on VMs that you plan to process. By default, Veeam Backup & Replication allocates 100 GB for the
global cache size.

For example, you want to process the following VMs:

• 1 VM that runs Microsoft Windows 7

• 3 VMs that run Microsoft Windows Server 2008 R2

• 2 VMs that run Microsoft Windows Server 2012 R2

There are 3 types of OSes so you must allocate 30 GB for the global cache on the target WAN accelerator.

NOTE

Global cache is stored only on the target WAN accelerator. You do not have to provide space for global
cache on the source WAN accelerator.

Digest Data
In some cases, Veeam Backup & Replication may require more space on the target WAN accelerator than
specified in the WAN accelerator properties. This can happen if digest data on the source WAN accel erator is
missing or cannot be used. For example:

• You have performed the Clear Cache operation on the source WAN accelerator and it no longer contains
digest data. For more information, see Clearing Global Cache.

1149 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Veeam Backup & Replication has attempted to resume operation of backup data transfer, but the backup
file was not prepared for the operation in a proper way. The digest data must be recalculated.

In such situations, the target WAN accelerator calculates digest data on its own, which requires additional space.
After the digest data is calculated, the target WAN accelerator transfers it to the source WAN accelerator. After
the transfer, the copy of the digest data is removed from the target WAN accelerator.

For safety reasons, it is recommended that you provide the following amount of space for digest data on the
target WAN accelerator:

The amount of disk space required for digest data at a target WAN accelerator operating in the Low b andwidth
mod e is calculated by the following formula:

Digest Size = 2% of Provisioned VM Size

The amount of disk space required for digest data at a target WAN accelerator operating in the Hig h bandwidth
mod e is calculated by the following formula:

Digest Size = 1% of Provisioned VM Size

This amount of space is required for digest data recalculation. If you do not provide this amount of space and a
situation where Veeam Backup & Replication needs to recalculate digest data occurs, the job to the remote
location will work in the limited mode. Veeam Backup & Replication will not deduplicate data against the
previous restore points copied to target. For more information, see Global Data Deduplication.

IMP ORTANT

When you specify the global cache size for a target WAN accelerator, you do not allocate any space for
storing digest data. To let Veeam Backup & Replication recalculate digest data, you must make sure that
necessary amount of free space is available on the target WAN accelerator (in addition to the space
allocated for the global cache).

For example:

• You have allocated 100 GB for global cache on the target WAN accelerator operating in the Low
b a ndwidth mode.

• Provisioned size of VMs to be processed is 2 TB.

In this case, the needed amount of free disk space for the global cache on the target WAN accelerator is:

100 GB + 40 GB = 140 GB

Many-to-One WAN Acceleration Scenario


Global cache size is calculated per 1 source WAN accelerator working with the target WAN accelerator. If you
plan to use several source WAN accelerators with 1 target WAN accelerator, you must increase the size of the
global cache proportionally. The cache data for every source WAN accelerator will be stored in a dedicated
subfolder in the global cache folder of the target WAN accelerator. The global cache size is calculated by the
following formula:

1150 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Total Global Cache Size = (# of Source WAN Accelerators) * (Size of Global Cach
e Configured in Target WAN Accelerator Properties)
Total Free Disk Space to Provide = Total Global Cache Size + Digest Size

For example:

• You have 4 source WAN accelerators in the source side working with 1 target WAN accelerator in the
disaster recovery (DR) site.

• The global cache size configured in properties of the target WAN accelerator is 100 GB.

• The size of VMs to be processed is 2 TB.

In this case, the needed amount of free disk space for the global cache and digests on the target WAN
accelerator is:

4*100 GB + 40 GB = 440 GB

NOTE

For more information and recommendations on WAN accelerator cache sizing, see this Veeam KB article.

1151 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding WAN Accelerators
To add a WAN accelerator, you must assign the WAN accelerator role to a Microsoft Windows server added to
the backup infrastructure.

You must deploy a pair of WAN accelerators: one WAN accelerator on each side of the WAN link.

Before you add a WAN accelerator, check prerequisites. Then use the New W AN Accelerator wizard to add a
WAN accelerator.

Before You Begin


Before you add a WAN accelerator, check the following prerequisites:

• The machine that will operate as a WAN accelerator must meet the system requirements. For more
information, see System Requirements.

• You must assign the WAN accelerator role to a Microsoft Windows server (physical or virtual). The WAN
accelerator role can be assigned to backup proxies and Microsoft Windows backup repositories already
configured in the backup infrastructure.

• You must use 64-bit Microsoft Windows machines as WAN accelerators. Veeam Backup & Replication does
not support 32-bit versions of Microsoft Windows used as WAN accelerators.

• WAN acceleration operations are resource-consuming. When assigning the WAN accelerator role, consider
available CPU and memory resources of the Microsoft Windows server. It is recommended that you assign
the WAN accelerator role to servers with 8 GB RAM and more.

• The machine must have enough free disk space to store digests or global cache data. For more
information, see WAN Accelerator Sizing.

• You must add the machine to the Veeam Backup & Replication console as a managed server before adding
it as a WAN accelerator.

1152 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New WAN Accelerator Wizard
To launch the New W AN Accelerator wizard, do either of the following:

• Open the Ba ckup Infrastructure view, in the inventory pane select W AN Accelerators and click Ad d WAN
Accelerator on the ribbon.

• Open the Ba ckup Infrastructure view, in the inventory pane right-click W AN Accelerators and select Ad d
W AN Accelerator.

1153 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Choose Server
At the Server step of the wizard, select a Microsoft Windows server that you plan to use as a WAN accelerator
and define port and connection settings for this server.

1. From the Choose server list, select a Microsoft Windows server added to the backup infrastructure. If the
server is not added to the backup infrastructure yet, you can click Ad d New to open the New W indows
Server wizard. For more information, see Adding Microsoft Windows Servers.

2. In the Description field, provide a description for future reference.

It is recommended that you describe the added WAN accelerator as the source or target one. When you
create a job to the remote location, this hint will be displayed in brackets next to the WAN accelerator
name, which will help you choose the necessary WAN accelerator to be used on the source or target side.

3. In the Tra ffic port field, specify the number of the port over which WAN accelerators must communicate
with each other. By default, port 6165 is used.

4. In the Streams field, specify the number of connections that must be used to transmit data between WAN
accelerators. By default, 5 connections are used.

This setting applies only to the source WAN accelerator. The greater is the number of streams, the more
bandwidth resources Veeam Backup & Replication will use. A great number of streams engage more CPU
and memory resources of the source WAN accelerator.

If the link has low latency and high bandwidth, the default setting (5 streams) may be enough to fully
saturate it. If the link is still not saturated, the number of streams may be increased. Tests show that with
high latency links, link speed x1.5 is a good best practice for estimating the number of streams required.
Below is an example benchmark on a 10 Mbit/s WAN link with 100 milliseconds of latency.

Throughput
Link (Mbit/s) La tency (ms) P a cket Loss Streams
( Mbps)

10 100 0 3 3.5

10 100 0 10 7.5

10 100 0 15 10

10 100 0 20 10

Increasing the number of streams to more than required for fully saturating the link will slow down data
transfers, as the data transfer will wait for all streams to initialize and stabilize before starting to transfer
any data.

TIP

To test different scenarios in the lab before deploying WAN acceleration, you can use a WAN
emulator (such as WANem).

1154 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
5. If your network bandwidth is more than 100 Mbps, we recommend that you use the Hig h bandwidth mode
option. This mode provides significant bandwidth savings comparable to the direct mode on WAN links
under 1 Gbps.

To use the Hig h bandwidth mode, enable the option for WAN accelerators at both sites of the data
transfer: the source one and the target one. If the Hig h bandwidth mode is enabled for the target WAN
accelerator, different source accelerators can parallelly interact with it in different modes, depending on
the mode selected for each source WAN accelerator.

When you enable the Hig h bandwidth mode for an existing pair of WAN accelerators,
Veeam Backup & Replication does not automatically remove the global cache that was previously used for
acceleration. If you are planning to use only the Hig h bandwidth mode for WAN acceleration and you do
not need the global cache anymore, you can free the disk space by manually removing the cache. If you
are planning to use WAN acceleration in the Low b andwidth mode in the future, we recommend that you
keep the global cache. You can disable the Hig h bandwidth mode at any time.

1155 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Define Cache Location and Size
At the Ca che step of the wizard, define settings for the folder where service files and global cache data will be
stored.

NOTE

If both WAN accelerators (the source one and the target one) work in the Hig h bandwidth mode, WAN
acceleration does not use the global cache. But note that you can disable the Hig h bandwidth mode and
switch back to the Low b andwidth mode at any time, which will require to use the global cache. To provide
correct operation of WAN accelerators, we recommend that you allocate enough disk space for the global
cache folder when adding a new WAN accelerator, no matter if the Hig h bandwidth mode is enabled for it
or not.

1. In the Folder field, specify a path to the folder in which service files (for source and target WAN
accelerators) and global cache data (for target WAN accelerator) must be stored. When selecting a folder
on the target WAN accelerator, make sure that there is enough sp ace for storing global cache data.

2. [For target WAN accelerator] In the Ca che size field, specify the size for the global cache. The global cache
size is specified per source WAN accelerator. If you plan to use one target WAN accelerator with several
source WAN accelerators, the specified amount of space will be allocated to every source WAN accelerator
and the size of the global cache will increase proportionally. For more information, see WAN Accelerator
Sizing.

IMP ORTANT

Do not nest the global cache folder deep in the file tree. During WAN acceleration operations,
Veeam Backup & Replication generates service files with long file names. Placing such files to a folder of
significant depth may cause problems on the NTFS file system.

1156 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components
Veeam Backup & Replication installs the following components on the server used as a WAN accelerator:

• Veeam Data Mover

• Veeam WAN Accelerator Service

At the Review step of the wizard, review what components are already installed on the server and what
components will be installed.

1. Review the components.

2. Click Nex t to install the components on the server.

1157 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply WAN Accelerator Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components. Click Nex t to complete the procedure of creating the WAN accelerator and adding it to the backup
infrastructure.

1158 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review details of the added WAN accelerator and click Finish to exit the
wizard.

1159 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing WAN Accelerators
You can permanently remove a WAN accelerator from the backup infrastructure. When you remove a WAN
accelerator, Veeam Backup & Replication unassigns the WAN accelerator role from the server, and this server is
no longer used as a WAN accelerator. The server itself remains in the backup infrastructure.

To remove a WAN accelerator:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select W AN a ccelerators.

3. In the working area, select the WAN accelerator and click Remove WAN Accelerator on the ribbon or right-
click the WAN accelerator and select Remove.

1160 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
WAN Acceleration
WAN acceleration is a Veeam technology that optimizes data transfer to remote locations. It is specific for off-
site backup copy jobs and replication jobs.

To enable WAN acceleration and data deduplication technologies, you must deploy a pair of WAN accelerators in
your backup infrastructure. For more information, see WAN Accelerators.

NOTE

WAN acceleration is included in the Veeam Universal License. When using a legacy socket-based license,
the Enterprise or Enterprise Plus editions of Veeam Backup & Replication are required.

Off-site backup copy and replication always involve moving large volumes of data between remote sites. The
most common problems that backup administrators encounter during off-site backup and replication are
insufficient network bandwidth to support VM data traffic and transmission of redundant data. To solve these
problems, Veeam Backup & Replication offers the WAN acceleration technology that combines:

• Network traffic compression

• Multistreaming upload

• Global data deduplication

• Variable block size deduplication

These technologies help optimize the data transfer and reduce the amount of data going over WAN.

High Bandwidth Mode


Starting with Veeam Backup & Replication 10, Veeam WAN acceleration introduces the Hig h bandwidth mode.
We recommend using it for WAN connections faster than 100 Mbps. If compared with the Low bandwidth mode,
it does not leverage the global cache, but utilizes a faster compression method, optimized digests processing
and an alternative deduplication mechanism. As a result, the new mode provides better performance and higher
speed of data transfer.

Note that to use the Hig h bandwidth mode, you must enable this option for WAN accelerators at both sites of
the data transfer: the source and the target. If the target WAN accelerator has the Hig h bandwidth mode
enabled, different source accelerators can parallelly interact with it in different modes, depending on the mode
selected for each source WAN accelerator.

How WAN Acceleration Works


When you create a job to the remote location, you can select to use WAN acceleration in its properties.

The procedure of data copying with WAN acceleration enabled is performed in the following way:

1. [For backup copy job] Veeam Backup & Replication decompresses the backup file to analyze its content.

2. The Veeam WAN Accelerator Service on the source WAN accelerator analyzes data blocks of the file to be
transferred and creates a file with digests for these data blocks. The created file with digests is stored to
the VeeamWAN folder on the source WAN accelerator.

1161 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Veeam Backup & Replication compresses the backup file data (for backup copy) or VM data (for
replication) and copies it to the target side.

At this point, Veeam Backup & Replication can perform deduplication within the VM itself — that is,
deduplicate identical data blocks in every VM disk.

4. During the data transfer process, the Veeam WAN Accelerator Service on the target WAN accelerator
populates the global cache storage with data blocks from the copied file.

5. During the next job cycle, the Veeam WAN Accelerator Service on the source WAN accelerator analyzes
data blocks in the file that must be transferred this time and creates digests for these data blocks.

6. The Veeam WAN Accelerator Service compares the created digests with the digests that have been
previously stored to the VeeamWAN folder on the source WAN accelerator. If duplicate data blocks are
found, the actual data block in the backup file is not copied over WAN. Instead, it is taken from the global
cache and written to the restore point in the backup copy folder or on the target data volume.

7. Additionally, Veeam Backup & Replication analyzes restore points that have been previously copied to the
target side. If duplicates are found, Veeam Backup & Replication does not copy such blocks over WAN but
takes them from the previously copied restore points.

As a result, Veeam Backup & Replication copies only new data blocks to the target side and uses data blocks
that are already stored in the global cache or in restore points in the target backup repository.

If the target WAN accelerator is used by several jobs, the target backup repository may already contain data
blocks of the necessary VM type. In this situation, Veeam Backup & Replication will copy the required data
blocks to the global cache before the copying process starts and use these data blocks further on. For more
information, see Many to One WAN Acceleration.

If WAN acceleration is performed in the Hig h bandwidth mode, the procedure of data transfer with WAN
acceleration has the following peculiarities:

• Global cache is not used. Thus, the target WAN accelerator does not need extra disk space to store the
global cache folder.

• Deduplication is performed only by using previous restore points for the processed VM on the target
repository. Therefore, Veeam Backup & Replication performs less deduplication operations and saves
resources and time for data processing.

• The data chunk size used by the Changed Block Tracking mechanism during deduplication is smaller if
compared with the Low b andwidth mode. This reduces the size of redundant data to transfer.

1162 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Global Data Deduplication
The goal of WAN acceleration is to send less data over the network. To reduce the amount of data going over
WAN, Veeam Backup & Replication uses the global data deduplication mechanism.

1. When you first run a job to the remote location, Veeam Backup & Replication analyzes data blocks going
over WAN.

2. With every new cycle of a job to the remote location, Veeam Backup & Replication uses the data
redundancy algorithm to find duplicate data blocks in copied files. Veeam Backup & Replication analyzes
data blocks in files on the source side and compares them with those that have been previously
transferred over WAN. If an identical data block is found, Veeam Backup & Replication deduplicates it.

As a result, only unique data blocks go over WAN. Data blocks that have already been sent are not sent. This
way, Veeam Backup & Replication eliminates transfer of redundant data over WAN.

Veeam Backup & Replication uses three sources for data deduplication:

• VM disks. Veeam Backup & Replication analyses data blocks within the same VM disk. If identical blocks
are found, duplicates are eliminated.
For example, in case of a virtualized Microsoft Exchange server, the same email is typically stored in
sender’s Outbox folder and recipient’s Inbox folder, which results in duplicate data blocks. When a job to
the remote location runs, Veeam Backup & Replication detects such VM data blocks and performs
deduplication.

• Previous restore points for the processed VM on the target repository. Veeam Backup & Replication
analyses data in the restore point that is about to be copied and the restore points that are already stored
on the target side. If an identical block is found on the target side, Veeam Backup & Replication eliminates
the redundant data block in the copied restore point.

• Global cache. Veeam Backup & Replication creates a global cache holding data blocks that repeatedly go
over WAN. In a new job session, Veeam Backup & Replication analyzes data blocks to be sent and
compares them with data blocks stored in the global cache. If an identical data block is already available in
the global cache, its duplicate on the source side is eliminated and not sent over WAN.

NOTE

Consider the following:

• Veeam Backup & Replication deduplicates data blocks within one VM disk and in restore points for
one VM only. Deduplication between VM disks and restore points of different VMs is performed
indirectly, using the global cache. For more information, see WAN Global Cache.
• Global data deduplication and deduplication within the same VM disk are not used if both WAN
accelerators in the pair (the source one and the target one) operate in the Hig h bandwidth mode.

Data Block Verification


During the VM copy process, Veeam Backup & Replication performs a CRC check for the VM traffic going
between the source and target WAN accelerators. The CRC check helps ensure that the correct VM data goes to
the target side and no corrupted data blocks are written to the global cache or to backup files in the target
backup repository.

The check is performed in the following way:

1. Before sending a data block to the target side, Veeam Backup & Replication calculates a checksum for the
copied data block.

1163 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Once the data block is copied over WAN and before it is written to the global cache or to the target
backup repository, Veeam Backup & Replication recalculates the checksum for this data block on the
target side.

3. The source and target checksums are compared. If the checksums do not coincide, the target WAN
accelerator sends a request to the source WAN accelerator for the correct data block. The source WAN
accelerator re-sends the necessary data blocks to the target WAN accelerator as is and the re -sent data
block is written to the global cache or to the backup file in the target backup repository on the fly.

Data Transport on WAN Disconnect


If you replicate VMs over WAN accelerators, and a WAN connection drops for short periods of time (less than 30
minutes), Veeam Backup & Replication transparently handles disconnect issues. It automatically resumes the
data transport process from the point when the connection was lost. The resume on disconnect capability
improves the reliability of off-site replication, reduces the backup window and minimizes the load on the WAN
link.

If a WAN connection is lost for more than 30 minutes, Veeam Backup & Replication still does not finish the job
with a failed status. After a WAN connection is resumed, Veeam Backup & Replication starts a new data transfer
cycle. Data transported with every new transport cycle is written to a new working snapshot of a VM replica. As
the WAN connection may drop several times, Veeam Backup & Replication can create a number of working
snapshots.

Not to keep long snapshot chains, Veeam Backup & Replication merges earlier snapshots and maintains only two
working snapshots for the VM replica. When all VM data is transferred to the target host, the two working
snapshots are also merged to create one fully functional VM restore point.

If the WAN link is weak and drops constantly, Veeam Backup & Replication may fail to transport VM data by the
time a new replication job session starts. In this case, during a new replication job session
Veeam Backup & Replication attempts to transfer VM data that have changed since the last replication job
session and VM data that were not transferred during the previous replication job session.

1164 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Log Shipping Servers
Log shipping servers are dedicated components that Veeam Backup & Replication uses for backup of Microsoft
SQL Server transaction logs, PostgreSQL WAL files and Oracle archive logs. For more information, see Microsoft
SQL Server Logs Backup, PostgreSQL WAL Files Backup and Oracle Logs Backup.

1165 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Tape Servers
Tape servers are dedicated components responsible for transferring data between data source and tape device.
For more information, see the Veeam Backup & Replication User Guide.

1166 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NDMP Servers
If your NAS device supports the NDMP protocol, you can back up data from it to tape. To do this, you need to
add the NAS device as an NDMP server. For more information, see the Veeam Backup & Replication User Guide.

1167 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup Enterprise Manager
Veeam Backup Enterprise Manager is an optional component intended for distributed enterprise environments
with multiple backup servers. Veeam Backup Enterprise Manager federates backup serv ers and offers a
consolidated view of these servers through a web browser interface. You can centrally control and manage all
jobs through a single "pane of glass", edit and clone jobs, monitor job state and get reporting data across all
backup servers. Veeam Backup Enterprise Manager also enables you to search for VM guest OS files in all
current and archived backups across your backup infrastructure, and restore these files in one click.

Veeam Backup Enterprise Manager Deployment


Veeam Backup Enterprise Manager can be installed on a physical or virtual machine. You can deploy it on the
backup server or use a dedicated machine.

Veeam Backup Enterprise Manager Services and Components


Veeam Backup Enterprise Manager uses the following services and components:

• Veeam Backup Enterprise Manager Service coordinates all operations of Veeam Backup Enterprise
Manager, aggregates data from multiple backup servers and provides control over these servers.

• Veeam Backup Enterprise Manager Configuration Database is used by Veeam Backup Enterprise Manager
for storing data. The database instance can be located on a SQL Server installed either locally (on the
same machine as Veeam Backup Enterprise Manager Server) or remotely.

• Veeam Guest Catalog Service replicates and consolidates VM guest OS file system indexing data from
backup servers added to Veeam Backup Enterprise Manager. Index data is stored in Veeam Backup
Enterprise Manager Catalog (a folder on the Veeam Backup Enterprise Manager Server) and is used to
search for VM guest OS files in backups created by Veeam Backup & Replication.

1168 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup
Veeam Backup & Replication produces image-level backups of VMs. It treats VMs as objects, not as a set of files.
When you back up VMs, Veeam Backup & Replication copies a VM image as a whole, at a block level. Image-level
backups can be used for different types of restore, including Instant Recovery, entire VM restore, VM file
recovery, file-level recovery and so on.

The backup technology is typically used for VMs with lower RTOs. When the primary VM fails, you need some
time to restore VM data from a compressed and deduplicated backup file.

1169 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
About Backup
Veeam Backup & Replication is built for virtual environments. It operates at the virtualization layer and uses an
image-based approach for VM backup.

Veeam Backup & Replication does not install agent software inside the VM guest OS to retrieve VM data. To
back up VMs, Veeam Backup & Replication leverages Microsoft VSS snapshot and checkpoint capabilities. When
you back up a VM, Veeam Backup & Replication instructs Microsoft Hyper-V to create a cohesive point-in-time
copy of a VM. Veeam Backup & Replication uses this point-in-time copy as a source of data for backup.

Veeam Backup & Replication copies VM data from the source volume at a block level. It retrieves VM data,
compresses and deduplicates it, and stores in backup files in the backup repository in Veeam proprietary format.

In Veeam Backup & Replication, backup is a job-driven process. To perform backup, you need to configure
backup jobs. A backup job is a configuration unit of the backup activity. The backup job defines when, what, how
and where to back up. One backup job can be used to process one or several VMs. You can instruct
Veeam Backup & Replication to run jobs automatically by schedule or start them manually.

The first backup job session always produces a full backup of the VM image. Subsequent backup job sessions are
incremental — Veeam Backup & Replication copies only those data blocks that have changed since the last
backup job session. To keep track of changed data blocks, Veeam Backup & Replication uses different
approaches. For more information, see Changed Block Tracking.

1170 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
How Backup Works
Veeam Backup & Replication performs VM backup in the following way:

1. When a new backup job session starts, Veeam Backup & Replication starts the Veeam Backup Manager
process on the backup server. Veeam Backup Manager reads job settings from the configuration database
and creates a list of VM tasks to process. For every disk of VMs added to the job,
Veeam Backup & Replication creates a new task.

2. Veeam Backup Manager connects to the Veeam Backup Service. The Veeam Backup Service includes a
resource scheduling component that manages all tasks and resources in the backup infrastructure. The
resource scheduler checks what backup infrastructure resources are available, and assigns backup proxies
and backup repositories to process job tasks.

3. Veeam Backup Manager establishes a connection with Veeam Data Movers on the target backup repository
and backup proxy (off-host or Hyper-V host that performs the role of the backup proxy), and sets a
number of rules for data transfer, such as network traffic throttling rules and so on.

4. Veeam Data Movers on the backup proxy and backup repository establish a connection with each other for
data transfer.

5. Veeam Backup Manager queries information about VMs and virtualization hosts from Microsoft Hyper -V.

6. If application-aware image processing is enabled for the job, Veeam Backup & Replication connects to VM
guest OSes, deploys non-persistent runtime components or, if necessary, persistent agent components on
VM guest OSes and performs in-guest processing tasks.

7. Veeam Backup & Replication requests Microsoft Hyper-V VSS to create a cohesive point-in-time copy of a
VM. Microsoft Hyper-V VSS creates a volume snapshot or VM checkpoint, depending on the hypervisor
version.

8. The source Veeam Data Mover reads the VM data from the volume snapshot or VM checkpoint and
transfers the data to the backup repository in one of transport modes. During incremental job sessions,
the source Veeam Data Mover uses CBT to retrieve only those data blocks that have changed since the
previous job session. If CBT is not available, the source Veeam Data Mover interacts with the target Veeam
Data Mover on the backup repository to obtain backup metadata, and uses this metadata to detect blocks
that have changed since the previous job session.

While transporting VM data, the source Veeam Data Mover performs additional processing. It filters out
zero data blocks, blocks of swap files and blocks of excluded VM guest OS files. The source Veeam Data
Mover compresses VM data and transports it to the target Veeam Data Mover.

Veeam Backup & Replication performs a cyclic redundancy check (CRC) for the TCP traffic going between
the source and the target. It calculates and compares checksums for data blocks going from the source
and data blocks received on the target. If the CRC check fails, Veeam Backup & Replication automatically
re-sends data blocks without any impact on the job.

1171 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
9. After the backup proxy finishes reading VM data, Veeam Backup & Replication requests Microsoft Hyper-V
VSS to perform cleanup operations.

1172 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Infrastructure for Backup
Veeam Backup & Replication uses the following components for the backup process:

• One or more source hosts with associated volumes

• [Optional] Off-host backup proxy

• Backup repository

• [Optional] One or more guest interaction proxies

• [For shared folder backup repository] Gateway server

All backup infrastructure components that are engaged in the job make up a data pipe. The source host and
backup repository produce two terminal points for the data flow. Veeam Backup & Replication processes VM
data in multiple cycles, moving VM data over the data pipe block by block.

Veeam Backup & Replication collects VM data, transforms and transports it to target with the help of Veeam
Data Movers. Veeam Backup & Replication uses two-service architecture — one Veeam Data Mover controls
interaction with the source host, and the other one controls interaction with the backup repository. Veeam Data
Movers communicate with each other and maintain a stable connection.

When a new backup session starts, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication deploys non-persistent runtime components or, if necessary, persistent
agent components on VM guest OSes using the guest interaction proxy (for Microsoft Windows VMs) or
backup server (for VMs with other OSes).

2. The target-side Veeam Data Mover obtains job instructions and communicates with the source-side Veeam
Data Mover to begin data collection.

3. The source-side Veeam Data Mover copies VM data from the volume shadow copy or VM checkpoint.
During incremental job runs, the source-side Veeam Data Mover retrieves only those data blocks that have
changed since the previous job session.
While copying, the source-side Veeam Data Mover performs additional data processing. It filters out zero
data blocks, blocks of swap files and blocks of excluded VM guest OS files, compresses and deduplicates
VM data blocks and moves them to the target-side Veeam Data Mover.

4. The target-side Veeam Data Mover deduplicates similar blocks of data on the target side and writes the
result to the backup file in the backup repository.

1173 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
On-Site Backup
When you back up to a Microsoft Windows or Linux backup repository in the local site,
Veeam Backup & Replication starts the target-side Veeam Data Mover on the Microsoft Windows or Linux
repository. The source-side Veeam Data Mover can be hosted on the source host or on a dedicated off -host
backup proxy, depending on the backup mode you use (on-host or off-host). VM data is sent from the source
host to the backup repository over the LAN.

To back up to a shared folder backup repository in the local site, you need to deploy a gateway server that has
access to the shared folder backup repository. You can assign the role of a gateway server to the backup server
itself or any Microsoft Windows machine added to the backup infrastructure. In this scenario,
Veeam Backup & Replication starts the target-side Veeam Data Mover on the gateway server. The source-side
Veeam Data Mover can be hosted on the source host or on a dedicated off-host backup proxy, depending on the
backup mode you use (on-host or off-host).

1174 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you choose to back up VMs to a shared folder backup repository and do not specify a gateway server
explicitly, Veeam Backup & Replication starts the source-side and target-side Veeam Data Movers on the backup
proxy. In the on-host backup scenario, Veeam Data Movers are started on the source Microsoft Hyper -V host. In
the off-host backup scenario, Veeam Data Movers are started on the off-host backup proxy.

Off-Site Backup
The common requirement for off-site backup is that one Veeam Data Mover runs in the production site, closer to
the source volume, and the other Veeam Data Mover runs in the remote target site, closer to the backup
repository. During backup, Veeam Data Movers maintain a stable connection, which allows for uninterrupted
operation over WAN or slow links.

If you choose to back up to a Microsoft Windows or Linux repository in the remote site,
Veeam Backup & Replication starts the target-side Veeam Data Mover on the Microsoft Windows or Linux
repository. The source-side Veeam Data Mover can be hosted on the source host or on a dedicated off -host
backup proxy, depending on the backup mode you use (on-host or off-host). VM data is sent from the source to
the backup repository over the WAN.

1175 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you choose to back up to a shared folder backup repository in the on-host mode, you must deploy a gateway
server in the remote site and point the shared folder backup repository at this gateway server. In this scenario,
Veeam Backup & Replication starts the target-side Veeam Data Mover on the gateway server. The source-side
Veeam Data Mover can be hosted on the source host or on a dedicated off-host backup proxy in the source site,
depending on the backup mode you use (on-host or off-host).

1176 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup of VMs on Local Storage and CSV
For backup of VMs on local storage and CSV, Veeam Backup & Replication leverages the Microsoft VSS
framework and Microsoft Hyper-V VSS components. Veeam Backup & Replication acts as a Microsoft VSS
requestor and communicates with the Microsoft VSS framework. It obtains information about available
Microsoft VSS components from Microsoft VSS, prescribes what components Microsoft VSS must use, identifies
volumes where VM files are located, and triggers the Microsoft VSS coordinator to create volume snapshots.

Before a snapshot of a volume is created, VMs on the volume must be quiesced: there must remain no
incomplete transactions, open files and so on. Veeam Backup & Replication uses three methods to prepare
Microsoft Hyper-V VMs for backup:

• Online backup (also known as Child VM Snapshot method) — native Microsoft Hyper-V mechanism that
allows you to create an application-consistent image of running VMs without any downtime.

• Offline backup (also known as Saved State method) — native Microsoft Hyper-V mechanism that requires
some VM downtime. To quiesce guest OS operations for a VM, Microsoft Hyper -V brings the VM to the
save state (hibernates it).

Offline backup is not applicable to VMs registered on Microsoft Hyper-V Server 2016 or later.

• Crash-consistent backup — Veeam’s proprietary mechanism that allows you to create a crash-consistent
VM backup. During crash-consistent backup, VMs are not brought to the saved state.

Whenever possible, Veeam Backup & Replication uses online backup to quiesce VMs. If online backup cannot be
performed, Veeam Backup & Replication employs one of the other two methods to prepare a VM for backup.

• If online backup cannot be performed, Veeam Backup & Replication fails over to the crash-consistent
backup.

• If you do not want to produce a crash-consistent backup, you can instruct Veeam Backup & Replication to
use the offline backup method.

NOTE

Veeam Backup & Replication does not fail over to the crash-consistent backup mode if you enable
application-aware processing for a job and enable the Require successful processing option. In such
situation, if application-aware processing fails, Veeam Backup & Replication will terminate the job with the
Error status.

Online Backup
Online backup is the recommended backup method for Microsoft Hyper-V VMs. This type of backup requires no
downtime. VMs remain running for the whole period of backup, and users can access them without any
interruption.

Online backup can be performed if Microsoft Hyper-V VMs meets a number of requirements. For more
information, see Microsoft Hyper-V documentation.

The procedure of online backup depends on the Microsoft Hyper-V Server version:

• Microsoft Hyper-V Server 2008 R2 and 2012

• Microsoft Hyper-V Server 2012 R2

• Microsoft Hyper-V Server 2016 and later

1177 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Hyper-V Server 2008 R2 and 2012
For online backup of VMs on Microsoft Hyper-V Server 2008 R2 and 2012, Veeam Backup & Replication uses a
native Microsoft Hyper-V approach. To quiesce VM data, Microsoft Hyper-V employs two Microsoft VSS
frameworks that work at two different levels and communicate with each other:

• Microsoft VSS framework inside the VM guest OS. This framework is responsible for quiescing data of
Microsoft VSS-aware applications inside the VM and creating a snapshot inside the VM guest OS. This
snapshot is known as internal snapshot.

• Microsoft VSS framework at the Microsoft Hyper-V host level. This framework is responsible for creating a
snapshot of a volume on which VM disks are located. This snapshot is known as external snapshot.

Online backup for VMs on Microsoft Hyper-V Server 2008 R2 and 2012 is performed in the following way:

1. Veeam Backup & Replication interacts with the Microsoft Hyper-V host VSS Service and requests backup of
a specific VM.

2. The Microsoft VSS Writer on the Microsoft Hyper-V host passes the request to the Microsoft Hyper-V
Integration Components (HV-IC) installed inside the VM guest OS.

3. The HV-IC acts as a VSS Requestor for the framework inside the VM. It communicates with this framework
and requests backup of Microsoft VSS-aware applications running on the VM.

4. VSS Writers for Microsoft VSS-aware applications on the VM are instructed to quiesce application data.

5. After the applications are quiesced, the framework inside the VM takes an internal snapshot using a
Microsoft VSS software provider in the VM guest OS.

6. The VM returns from the read-only state to the read-write state, and operations inside the VM are
resumed. The created snapshot is passed to the HV-IC.

7. The HV-IC notifies the hypervisor that the VM is ready for backup.

8. The Microsoft Hyper-V host VSS provider takes a snapshot of a volume on which VM disks are located
(external snapshot). After that, Microsoft VSS triggers the auto-recovery process. For more information,
see Auto-Recovery.

9. The volume snapshot is presented to Veeam Backup & Replication. Veeam Backup & Replication reads VM
data from the volume snapshot in one of two backup modes — on-host backup or off-host backup.

1178 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
10. After the backup is complete, the volume snapshot is deleted.

Auto-Recovery
Internal and external snapshots are taken one after another, with a little time difference. During this time
interval, the VM on the volume is not frozen — its applications and OS are working as usual. For this reason,
when the external snapshot is created, there may remain unfinished application transactions inside the VM, and
this data can be lost during backup.

To make sure the VM data is consistent at the moment of backup, Microsoft Hyper-V VSS Writer performs
additional processing inside the created external snapshot. This process is also known as auto-recovery.

Auto-recovery is performed after a volume snapshot is taken. The auto-recovery process is performed in the
following way:

1. Right after the snapshot of a volume is taken, Microsoft Hyper-V host VSS allows the Microsoft Hyper-V
host VSS Writer time to update data inside the external snapshot, before it is permanently put to the read -
only state.

2. The volume snapshot is temporarily mounted to the Microsoft Hyper-V host as a new volume with the
read-write access.

3. The Microsoft Hyper-V host VSS Writer rolls back a VM on the external snapshot to the state of the
internal snapshot. All changes that took place after the internal snapshot was taken are discarded. This
way, VM data inside the external snapshot is brought to a completely consistent state.

At the same time, the internal snapshot inside the VM guest OS is deleted.

As a result, you have a VM on the production volume, and a consistent volume snapshot that
Veeam Backup & Replication can use for backup.

NOTE

Auto-recovery may take up to several minutes.

1179 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Hyper-V Server 2012 R2
For backup of VMs on Microsoft Hyper-V Server 2012 R2, Microsoft VSS uses backup and auto-recovery
checkpoints.

To quiesce VM data, Veeam Backup & Replication leverages two Microsoft VSS frameworks that work at two
different levels and communicate with each other:

• Microsoft VSS framework inside the VM guest OS. This framework is responsible for quiescing data of
Microsoft VSS-aware applications inside the VM and creating a snapshot inside the VM guest OS.

• Microsoft VSS framework at the Microsoft Hyper-V host level. This framework is responsible for creating a
snapshot of a volume on which VM disks are located.

Online backup for VMs on Microsoft Hyper-V 2012 R2 is performed in the following way:

1. Veeam Backup & Replication interacts with the Microsoft Hyper-V host VSS Service and requests backup of
a specific VM.

2. The Microsoft VSS Writer on the Microsoft Hyper-V host passes the request to the Microsoft Hyper-V
Integration Components (HV-IC) installed inside the VM guest OS.

3. The HV-IC acts as a VSS Requestor for the framework inside the VM. It communicates with this framework
and requests backup of Microsoft VSS-aware applications running on the VM.

4. VSS Writers for Microsoft VSS-aware applications on the VM are instructed to quiesce application data.

5. After the applications are quiesced, Microsoft Hyper-V VSS takes a backup checkpoint of the VM. Every
virtual disk of a VM receives a temporary file named as vm_disk_name_GUID.avhdx. For example, the
name of the received file can be: disk_1_A1C3FDA5-5DFE-4001-A6D7-EBE18195A85C.avhdx. All
new writes that occur to the VM until the volume snapshot is taken are redirected to this file.

6. Right after taking the backup checkpoint, Microsoft Hyper-V VSS takes another auxiliary checkpoint —
auto-recovery checkpoint. Every virtual disk of a VM receives a temporary file named as vm_disk_name-
AutoRecovery.avhdx. For example, the name of the received file can be: disk_1-
AutoRecovery.avhdx. The auto-recovery checkpoint helps make sure that VM data is consistent during
backup.

The auto-recovery checkpoint does not depend on the backup checkpoint — it is taken independently in a
new checkpoint chain.

7. The framework inside the VM takes an internal snapshot using a Microsoft Hyper-V Integration Services
Shadow Copy provider in the VM guest OS.

8. The created internal snapshot is passed to the HV-IC.

9. The HV-IC notifies the hypervisor that the VM is ready for backup.

10. Microsoft Hyper-V VSS performs auto-recovery — it mounts the auto-recovery checkpoint to the VM, rolls
back data on the VM to the consistent state.

11. The Microsoft Hyper-V host VSS provider takes a snapshot of a volume on which VM disks are located
(external snapshot).

12. The auto-recovery checkpoint is merged with the original VM.

13. The volume snapshot is presented to Veeam Backup & Replication. Veeam Backup & Replication reads VM
data from the volume snapshot in one of two backup modes — on-host backup or off-host backup.

14. After the backup is complete, the volume snapshot is deleted, and the backup checkpoint is merged with
the original VM.

1180 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Hyper-V Server 2016 and Later
Online backup of VMs on Microsoft Hyper-V 2016 and later relies on production checkpoints.

Production checkpoints are point-in-time images of VMs. When producing production checkpoints, Microsoft
Hyper-V does not put VMs to the saved state. Instead, it quiesces data on VMs with the help of the Microsoft
VSS technology (for Microsoft Windows VMs) or file system freeze (for Linux VMs). The resulting checkpoints
are application-consistent, so you can recover VMs without any data loss.

Veeam Backup & Replication performs online backup with the help of production checkpoints only if the
following conditions are met:

• VM configuration version is upgraded to 8.x.

• VMs are deployed on Microsoft Hyper-V Server 2016 or later.

• [For Microsoft Hyper-V clusters] All hosts in the cluster are upgraded to Microsoft Hyper-V Server 2016 or
later and the cluster functional level is upgraded.

Online backup is performed in the following way:

1. Veeam Backup & Replication requests a production checkpoint of a specific VM.

2. Microsoft Hyper-V Virtual Machine Management Service (for Microsoft Windows VMs) or file system
freeze (for Linux VMs) brings data on the VM guest OS to a consistent state.

3. Microsoft Hyper-V Virtual Machine Management Service creates a production checkpoint for the VM.
Every virtual disk of a VM receives a temporary AVHDX file. All new writes are redirected to temporary
AVHDX files.

4. Further activities depend on the backup mode:

o In the onhost backup mode, Veeam Backup & Replication takes a VM checkpoint and reads data from
the base disk. After the VM processing completes, the production checkpoint is merged with the
original VM.

1181 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o In the offhost backup mode, the Microsoft Hyper-V host VSS provider takes a snapshot of a volume on
which VM disks are located. The volume snapshot is mounted to the offhost backup proxy and
presented to Veeam Backup & Replication. Veeam Backup & Replication reads VM data from a base
disk on the volume snapshot. After the VM processing completes, the production checkpoint is
merged with the original VM. When all VMs in the group for which the volume snapshot is created are
processed, Veeam Backup & Replication triggers volume snapshot deletion.

Offline Backup
Offline backup (or saved state backup) is a native Microsoft Hyper-V approach to quiesce VMs before taking a
volume snapshot. This type of backup requires some downtime of a VM. When a VM is backed up, the Microsoft
Hyper-V VSS Writer forces the VM into the saved state (hibernates it) to create a stable system image.

NOTE

Offline backup is not applicable to VMs registered on Microsoft Hyper-V Server 2016 or later.

Offline backup is performed in the following way:

1. Veeam Backup & Replication interacts with the Microsoft Hyper-V host VSS Services and requests backup
of a specific VM.

2. The Microsoft Hyper-V host VSS Writer forces a VM into the saved state for several seconds. The VM OS
hibernates, and the content of the system memory and CPU is written to a dump file.

3. The Hyper-V host VSS provider takes a snapshot of a volume on which VM disks are located. The VM
returns to the normal state.

4. The volume snapshot is presented to Veeam Backup & Replication. Veeam Backup & Replication reads VM
data from the volume snapshot in one of two backup modes — on-host backup or off-host backup. After
the backup is complete, the volume snapshot is deleted.

1182 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
In the production environment, offline backup may be inappropriate. It implies VM downtime and does not
produce transactionally consistent backups and replicas as data on the VM is not quiesced before a volume
snapshot is taken. As an alternative to offline backup, Veeam Backup & Replication offers the crash-consistent
backup method for those cases when online backup cannot be used, and offline backup is inappropriate.

Crash-Consistent Backup
Crash-consistent backup is Veeam’s proprietary method of creating crash-consistent VM images. A crash-
consistent image can be compared to the state of a VM that has been manually reset. Unlike offline backup,
crash-consistent backup does not require any downtime of a VM.

IMP ORTANT

Crash-consistent backup does not preserve data integrity of open files of transactional applications on the
VM guest OS and may result in data loss.

The procedure of crash-consistent backup depends on the Microsoft Hyper-V Server version:

• Microsoft Hyper-V Server 2012 R2 and earlier

• Microsoft Hyper-V Server 2016 and later

Microsoft Hyper-V Server 2012 R2 and Earlier


Crash-consistent backup is performed in the following way:

1. Veeam Backup & Replication interacts with the Hyper-V host VSS Services and requests backup of a
specific VM.

2. The Hyper-V host VSS Writer notifies the VSS provider that volume snapshots can be taken.

3. The Hyper-V host VSS provider creates a snapshot of the requested volume.

1183 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. The volume snapshot is presented to Veeam Backup & Replication. Veeam Backup & Replication reads VM
files from the volume snapshot using one of two backup modes — on-host backup or off-host backup.
After the backup is completed, the snapshot is deleted.

Microsoft Hyper-V Server 2016 and Later


Crash-consistent backup of VMs on Microsoft Hyper-V 2016 and later versions relies on standard checkpoints.
Crash-consistent backup is performed in the following way:

1. Veeam Backup & Replication requests a standard checkpoint of a specific VM.

2. Further activities depend on the backup mode:

o In the onhost backup mode, Veeam Backup & Replication reads data from VM disks in the read-only
state. After the VM processing completes, the standard checkpoint is merged with the orig inal VM.

1184 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o In the offhost backup mode, the Microsoft Hyper-V host VSS provider takes a snapshot of a volume on
which VM disks are located.

The volume snapshot is mounted to the offhost backup proxy and presented to
Veeam Backup & Replication. Veeam Backup & Replication reads VM data from the volume snapshot.
After the backup job completes, the volume snapshot and checkpoint are deleted.

Backup Modes
Veeam Backup & Replication offers two modes for processing VM data — on-host backup and off-host backup.
The difference between the two modes lies in the location where VM data is processed.

On-Host Backup
During on-host backup, VM data is processed on the source Microsoft Hyper-V host where VMs that you want to
back up or replicate reside. All processing operations are performed directly on the source host that performs
the role of the backup proxy. For this reason, on-host backup may result in high CPU usage and network
overhead on the host system.

NOTE

The procedure below describes the backup process for Microsoft Hyper -V Server 2012 R2 and earlier. For
more information about backup of VMs registered on Microsoft Hyper-V 2016 and later versions, see
Online Backup and Crash-Consistent Backup.

The on-host backup process is performed in the following way:

1. Veeam Backup & Replication triggers a snapshot of the necessary volume.

2. Veeam Data Mover on the host uses the created volume snapshot to retrieve VM data; it processes the VM
data and copies it to the destination.

1185 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. After the backup process is complete, the volume snapshot is deleted.

Assigning Role of On-Host Backup Proxy in CSV


The role of the backup proxy is assigned to a Microsoft Hyper-V host in CSV by the following rules:

• If you back up or replicate VMs whose disks are located on a CSV in Microsoft Hyper -V Server 2012 or 2012
R2, and Microsoft CSV Software Shadow Copy Provider is used for snapshot creating,
Veeam Backup & Replication assigns the role of an on-host backup proxy to the host owning the CSV. If
VM disks are located on different CSV's, Veeam Backup & Replication may use several on-host backup
proxies, which are the required hosts owning CSV's.

• In case you perform backup or replication of VMs whose disks are located on a CSV in Microsoft Hyper -V
2008 R2, and a VSS software or hardware provider is used for snapshot creation,
Veeam Backup & Replication assigns the role of an on-host backup proxy to the host on which the
processed VM is registered.

Off-Host Backup
In the off-host backup mode, backup processing is shifted from the source Microsoft Hyper -V host to a
dedicated machine — an off-host backup proxy.

The off-host backup proxy acts as a “data mover”. Veeam Data Mover running on the off-host backup proxy
retrieves VM data from the source volume, processes it and transfers data to the destination. This type of
backup does not impose load on the source host. As resource intensive data processing operations are
performed on the off-host backup proxy, production hosts remain unaffected.

To perform off-host backup, Veeam Backup & Replication uses transportable shadow copies. The transportable
shadow copy technology lets the backup application create a snapshot of a data volume on which VM disks are
located, and import, or mount, this snapshot onto another server in the same subsystem (SAN) for backup and
other purposes. The transport process is accomplished in a few minutes, regardless of the amount of the data.
The process is performed at the SAN storage layer so it does not impact host CPU usage or network
performance. For more information about transportable shadow copies, see Microsoft Docs.

To perform off-host backup, the backup infrastructure must meet the following requirements:

• You must configure an off-host backup proxy. For more information, see Off-Host Backup Proxy.

1186 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• In the properties of a backup or replication job, you must select the off-host backup method and off-host
backup proxy that you want to use. If necessary, you can point the job to a specific off -host backup proxy.
For more information, see Configuring Advanced Options for Off-Host Backup Proxies.

The off-host backup process is performed in the following way:

1. Veeam Backup & Replication triggers a snapshot of the necessary volume on the Microsoft Hyper -V host.

2. The created snapshot is detached from the host and mounted to the off-host backup proxy.

3. Veeam Data Mover running on the off-host backup proxy uses the mounted volume snapshot as a data
source. It retrieves VM data from the volume snapshot, processes it and transports data to the destination.

4. After the backup process is complete, the snapshot is dismounted from the off -host backup proxy and
deleted on the storage system.

IMP ORTANT

If you plan to perform off-host backup for a Microsoft Hyper-V cluster with CSV, make sure you deploy an
off-host backup proxy on a host that is NOT a part of a Hyper-V cluster.
When a volume snapshot is created, this snapshot has the same LUN signature a s the original volume.
Microsoft Cluster Services do not support LUNs with duplicate signatures and partition layout. For this
reason, volume snapshots must be transported to an off-host backup proxy outside the cluster. If the off-
host backup proxy is deployed on a node of a Microsoft Hyper-V cluster, a duplicate LUN signature will be
generated, and the cluster will fail during backup or replication.

Helpful Resources
• List of tested VSS hardware providers for DPM

• Links to resources and documentation from some of storage vendors:

o HPE Support Center

o DELL PowerVault

The VSS hardware provider for Dell PowerVault can be found on the Resource CD.

1187 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o DELL Equal Logic

The VSS hardware provider is a part of Host Integration Tool (HIT/Microsoft).

To get detailed information, contact your storage vendor.

Choosing VSS Provider (Microsoft Hyper-V Server 2012 R2 and


Earlier)
Before you configure backup jobs, it is recommended that you decide what VSS provider will be used to create
and maintain volume shadow copies.

By default, Veeam Backup & Replication automatically selects a VSS provider on every volume. Every 4 hours it
rescans all Microsoft Hyper-V hosts added to the backup infrastructure and updates information about
connected volumes. Veeam Backup & Replication also collects information about software and hardware VSS
providers available on every volume.

If hardware providers are available, Veeam Backup & Replication selects a hardware provider to create volume
shadow copies on a volume. If no hardware providers are installed, Veeam Backup & Replication selects the VSS
system software provider. If necessary, however, you can assign a VSS provider on every volume manually.

If both software and hardware providers are available for a volume, it is recommended that you select a
hardware provider. Although software providers are generally applicable to a wider range of storage platforms,
they have a number of limitations:

• Software providers do not support transportable volume shadow copies and cannot be used for off -host
backup.

• By default, jobs working with the same volume can take up to 4 snapshots of a volume simultaneously. If
necessary, the number of snapshots can be increased.

• Hardware providers operate at the storage system controller level. Software providers operate at the
software level, between the file system and the volume manager, and can cause a significant performance
overhead on the source host.

• [For Microsoft Windows Server 2008 R2] Hardware providers can work with several snapshots
simultaneously. That is, if you have several jobs that work with the same volume, you can run them in
parallel. If you use a software provider, Veeam Backup & Replication serializes VM processing. You will not
be able to start several jobs working with the same volume simultaneously. The volume on which VM disks
reside remains locked by one job for the whole period of data processing. After the job completes, the
volume becomes accessible for other jobs.

If a hardware provider is used to take a snapshot in such case, the CSV stays in the redirected mode while
the snapshot is taken. After a volume shadow copy is created, the CSV resumes direct I/O.

• [For Microsoft Windows Server 2008 R2] Software providers are not suitable for backup on CSVs — a
significant backup window is required to back up VMs that reside on the same volume but are re gistered
on different hosts. When a cluster node initiates a snapshot on a CSV, the CSV is switched to the Backup in
Progress , Redirected Access mode.
If a software provider is used to take a snapshot, the CSV stays in the redirected mode until the backup
process completes. If large virtual disks are processed, backup time can be significant.

1188 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup of VMs on Microsoft SMB3
Microsoft Hyper-V provides the ability to store VM files on SMB3 file shares. Veeam Backup & Replication works
with both standalone and clustered SMB3 servers. It supports VMs whose VM disks are located on SMB3 shares
and lets you perform backup, replication and file copy operations for such VMs without taking VMs offline.

The procedure of backup depends on the Microsoft Hyper-V Server version:

• Microsoft Hyper-V Server 2012 R2 and earlier

• Microsoft Hyper-V Server 2016

Microsoft Hyper-V Server 2012 R2 and Earlier


In general, VM quiescence and backup or replication of VMs on SMB3 shares is similar to backup or replication of
VMs hosted on local storage and CSV. However, SMB3 brings in some specifics.

If you want to work with SMB3 shares in Veeam Backup & Replication, the backup infrastructure must meet the
following requirements:

• SMB3 shares must be properly configured. For a full list of requirements for SMB3 shares, see the
Requirements and supported configurations section at Microsoft Docs.

• An SMB3 server or SMB3 cluster hosting the necessary file shares must be added to the backup
infrastructure. Otherwise Veeam Backup & Replication will not be able to use changed block tracking for
VMs residing on SMB3 shares.

• VMs must not be located on hidden shares or default shares like C$ or D$. When rescanning SMB v3 file
shares, Veeam Backup & Replication skips these types of shares.

Microsoft Hyper-V Server 2016 and Later


For backup of VMs registered on Microsoft Hyper-V Server 2016 and later versions, Veeam Backup & Replication
uses a new mechanism based on production checkpoints. For more information, see Backup of VMs on Microsoft
Hyper-V Server 2016.

If you plan to process VMs whose disks reside on SMB3 shared folders registered on Microsoft Hyper -V Server
2016 or later, it is not obligatory to add the SMB3 server to the backup infrastructure. However, if you do not
add the SMB3 server, you will not be able to specify the Ma x snapshots and latency control settings for SMB3
shared folders.

The mentioned above applies for SMB3 shares running on Microsoft Windows or any other non-Windows based
SMB3 source.

For more information, see Adding Microsoft SMB3 Servers.

Backup Process (Microsoft Hyper-V 2012 R2 and Earlier)


For backup and replication of VMs that reside on SMB3 shares, Veeam Backup & Replication uses a native Hyper-
V approach utilizing the Microsoft VSS framework. Veeam Backup & Replication acts as a VSS requestor: it
communicates with the VSS framework and triggers a shadow copy of the necessary file share. The Microsoft
VSS components create a file share shadow copy and present it to Veeam Backup & Replication that uses this
shadow copy as a source for backup.

1189 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
To properly quiesce VMs on SMB3 shares, Microsoft Hyper-V uses three VSS frameworks. These frameworks
work at the level of the Hyper-V host and at the level of the SMB3 file server and communicate with each other:

• VSS framework on the Microsoft Hyper-V host (Hyper-V Host VSS). When Veeam Backup & Replication
starts the backup or replication process, it communicates directly with the VSS framework on the
Microsoft Hyper-V host where VMs are registered. The Hyper-V host VSS Service initiates creation of the
file share shadow copy, freezes VM application writes and passes the request for shadow copy to the VSS
for SMB File Shares framework. After the shadow copy is created, the Microsoft Hyper -V host VSS Service
returns a path to the shadow copy to Veeam Backup & Replication.

• VSS for SMB File Shares. This framework is Microsoft’s extension to its VSS framework. VSS for SMB File
Shares provides application-consistent shadow copies of VMs on SMB3 network shares. To work with
shadow copies of file shares, VSS for SMB File Shares uses two components:

o File Share Shadow Copy Provider is a VSS provider for SMB3. The File Share Shadow Copy Provider is
invoked on the Microsoft Hyper-V host where VMs are registered. The provider uses VSS APIs to
interact with the VSS requestor, File Share Shadow Copy Agent and request creation of file shares
shadow copies.

o File Share Shadow Copy Agent is a VSS requestor for SMB3. The File Share Shadow Copy Agent is
invoked on the SMB3 file server. The agent interacts with the local VSS framework on the SMB3 file
server to create a shadow copy of the requested file share.

• Loca l VSS framework on the SMB3 file server. This framework is responsible creating a shadow copy of the
volume on which the file share is located, and exposing the shadow copy as a file share on the SMB3
server.

Backup of VMs on SMB3 shares is performed in the following way:

1. Veeam Backup & Replication interacts with the Microsoft Hyper-V host VSS Service and requests a shadow
copy of the necessary file share.

2. The Hyper-V host VSS Service sends a request to create a shadow copy to the Microsoft Hyper -V host VSS
Writer. The Microsoft Hyper-V host VSS Writer flushes buffers and holds application writes on VMs.

3. The Microsoft Hyper-V host VSS Service sends a request for shadow copy creation to the File Share
Shadow Copy Provider invoked on the Hyper-V host.

4. The File Share Shadow Copy Provider relays the request to the File Share Shadow Copy Agent invoked on
the SMB3 file server hosting the necessary file share.

5. The File Share Shadow Copy Agent triggers a request for shadow copy creation to the local VSS on the
SMB3 file server.

6. The local VSS on the SMB3 file server uses the necessary shadow copy provider to cr eate a shadow copy of
the volume on which the necessary file share is located. The shadow copy is exposed as a file share on the
SMB3 server. After that, application writes on VMs located on the original file share are resumed.

1190 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
7. The File Share Shadow Copy Agent returns a path to the shadow copy to the File Share Shadow Copy
Provider.

8. The File Share Shadow Copy Provider communicates this information to the Microsoft Hyper -V host VSS
Service.

9. Veeam Backup & Replication retrieves information about the shadow copy properties from the Microsoft
Hyper-V host VSS Service.

10. Veeam Backup & Replication uses the created shadow copy as a source for backup. After backup is
complete, the file share shadow copy is deleted.

For more information, see Microsoft Docs.

Backup Modes (Microsoft Hyper-V 2012 R2 and Earlier)


Veeam Backup & Replication offers two modes for processing VMs on SMB3 shares: on-host backup and off-host
backup.

On-Host Backup
On-host backup of VMs on SMB3 shares is similar to on-host backup of VMs on local storage and CSV. During
on-host backup, Microsoft VSS components, File Share Shadow Copy Provider and Veeam Data Mover are
invoked on the source host. The File Share Shadow Copy Agent is invoked on the SMB3 server. As a result, all
data processing is accomplished directly on the source Microsoft Hyper-V host and on the SMB3 server.

The on-host backup process includes the following steps:

1. Veeam Backup & Replication triggers a shadow copy of the necessary file share. Microsoft VSS
components invoked on the source host and SMB3 server create a shadow copy of the volume on which
the requested file share is located, and expose the shadow copy as a file share on the SMB3 server.

2. Veeam Data Mover on the source host accesses the shadow copy file share exposed on the SMB3 server.
Veeam Backup & Replication retrieves VM data from the shadow copy, processes it and copies data to the
destination.

1191 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. After the backup process is complete, the shadow copy is deleted.

Off-Host Backup
In general, off-host backup for VMs on SMB3 shares is similar to off-host backup of VMs on local storage or CSV.
During off-host backup, Microsoft VSS processing operations are shifted from the sour ce host to a dedicated
machine — off-host backup proxy. Veeam Data Mover is deployed on the off-host backup proxy, instead of the
source host.

If you want to perform off-host backup, the backup infrastructure must meet the following requirements:

• You must configure an off-host backup proxy. For more information, see Off-Host Backup Proxy.

• In the properties of a backup or replication job, you must select the off-host backup method and off-host
backup proxy that you want to use. If necessary, you can point the job to a specific off -host backup proxy.
For more information, see Configuring Advanced Options for Off-Host Backup Proxies.

• The LocalSystem account of the off-host backup proxy must have read access permissions on the SMB3
file share.

• The off-host backup proxy must reside in the same domain where the SMB3 server resides. Alternatively,
the domain where the SMB3 server resides must trust the domain where the off-host backup proxy resides
— that is, the off-host backup proxy must be located in a trusted domain.

The off-host backup process is performed in the following way:

1. Veeam Backup & Replication triggers a shadow copy of the necessary file share. Microsoft VSS
components invoked on the source host and SMB3 server create a shadow copy of the volume on which
the requested file share is located, and expose the shadow copy as a file share on the SMB3 server.

2. Veeam Data Mover on the off-host backup proxy accesses the shadow copy on the SMB3 server. It
retrieves VM data from the shadow copy, processes it and copies data to the destination.

1192 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. After the backup process is complete, the shadow copy is deleted.

1193 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Chain
Backup chain is a sequence of backup files created by jobs. The backup chain provides the ability to recover data.

The backup chain consists of the first full backup file, incremental backup files, metadata files and some
additional files. Full and incremental backup files correspond to restore points of backed -up VM. You can think
of restore points as of "snapshots" of VM data at specific points in time. Restore points let you roll bac k VMs to
the necessary state.

The type of backup files and how Veeam Backup & Replication orders them in the backup chain depend on the
chosen backup method. For more information, see Backup Methods.

The amount of backup chains for backed-up VMs depend on the chosen backup chain format. For more
information, see Backup Chain Formats.

Backup Files
Veeam Backup & Replication creates and maintains the following types of backup files:

• VBK — full backup files that store copies of full VM images.

• VIB or VRB — incremental backup files that store incremental changes of VM images.

• VBM — backup metadata files that 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.

In addition to these file types, Veeam Backup & Replication can create the following files in the backup
repository:

• VSB — virtual synthetic backup files used for generation of virtual full backups on tapes. For more
information, see the Virtual Full Backup section in the Veeam Backup & Replication User Guide.

• VLB, VSM and VLM — files that store Microsoft SQL Server transaction log data. For more information, see
Microsoft SQL Server Logs Backup.

• VLB, VOM and VLM — files that store Oracle archived log data. For more information, see Oracle Log
Backup.

• VLB, VPM and VLM — files that store PostreSQL WAL files. For more information, see PostgreSQL Log
Backup.

All backup files created by the backup job reside in a dedicated job folder in the backup repository. For example,
if you create a backup job with the DC Backup name, Veeam Backup & Replication will create the DC Backup
folder on the target backup repository and store all backup files produced with this job in this folder.

Rolling Back VMs


To roll back a VM to a specific point in time, you need a chain of backup files: a full backup file plus a set of
incremental backup files dependent on this 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 this reason, you must not delete separate backup files from
the backup repository manually. Instead, you must specify retention policy settings that will let you maintain
the desired number of backup files in the backup repository.

1194 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Methods
Veeam Backup & Replication provides the following methods for creating backup chains:

• Forever forward incremental (FFI)

When the forever forward incremental (FFI) backup method is used, Veeam Backup & Replication creates a
backup chain that consists of the first full backup file (VBK) and a set of forward incremental backup files
(VIBs) following it.

This backup method helps you save space on the backup storage because Veeam Backup & Replication
stores only one full backup file and removes incremental backup files once the retention period is
exceeded. To meet retention policy settings, Veeam Backup & Replication injects data of an incremental
file into the full backup file before deleting the increment. Such transformations can lead to the
fragmentation of the full backup file, and you have to schedule the compact of full backup file operation.
This operation produces additional I/O load on the backup storage. Overall, the FFI method produces the
moderate I/O impact on the backup storage compared to other backup methods.

Restore to the earliest restore point from backup files created using the FFI method is the fastest
compared to other methods because the first available restore point is always a full backup. Restore to
other restore points can be compared by speed with FI method.

For more information on the FFI backup method and how it works, see Forever Forward Incremental
Backup.

• Forward incremental (FI)

When the forward incremental (FI) backup method is used, Veeam Backup & Replication 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 can be created using synthetic full and active full method. By
doing regular full backups, the backup chain is split into shorter series. This lowers the chances of losing
the backup chain completely and makes this backup method the most reliable.

This backup method requires more storage space than other methods because the backup chains contains
multiple full backup files and sometimes Veeam Backup & Replication stores more restore points than
specified in the retention policy settings due to the specifics of the FI retention policy. For more
information on how backups are retained, see Forward Incremental Backup Retention Policy.

The FI backup method produces the lowest I/O impact on the backup storage. However, the impact on the
backup storage increases on days when synthetic full backups are scheduled, and impact on the
production storage increases on days when active full backups are scheduled.

Restore from backup files created using the FI method is the most optimal in time compared to other
methods (in cases when you you do not restore to the earliest or latest restore point). That is because the
backup chain is usually divided into short series of full backup files and incremental files and the
aggregation of the desired restore point does not take long time.

1195 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For more information on the FI backup method and how it works, see Forward Incremental Backup.

• Reverse incremental (RI)

When the reverse incremental (RI) backup method is used, Veeam Backup & Replication creates a backup
chain that consists of the full backup file (VBK) and a set of reverse incremental backup files (VRBs)
preceding it.

This backup method helps you save space on the backup storage because Veeam Backup & Replication
stores only one full backup file (if you do not schedule periodic full backups) and removes incremental
backup files once the retention period is exceeded. For more information on how backups are retained, see
Reverse Incremental Backup.

The RI method produces the heaviest I/O impact on the backup storage compared to other backup
methods. That is because during backup, Veeam Backup & Replication injects changed data blocks into the
full backup file and also creates reverse incremental backup files. Such transformations can lead to the
fragmentation of the full backup file, and you have to schedule the compact of full backup file operation.
This operation produces additional I/O load on the backup storage.

Restore to the latest restore point from backup files created using the RI method is the fastest compared
to other methods because the most recent restore point is always a full backup, and it gets updated after
every backup cycle. Restore to earlier restore points is slower than for other backup methods.

For more information on the RI backup method and how it works, see Reverse Incremental Backup.

Forever Forward Incremental Backup


The forever forward incremental backup method produces a backup chain that consists of the first full backup
file (VBK) and a set of forward incremental backup files (VIB) following it.

Veeam Backup & Replication creates a forever forward incremental backup chain in the following way:

1. During the first session of a backup job, Veeam Backup & Replication creates a full backup file in the
backup repository.

2. During subsequent backup job sessions, Veeam Backup & Replication copies only VM data blocks that have
changed since the last backup job session (full or incremental) and saves these blocks as an incremental
backup file in the backup chain.

1196 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. After adding a new restore point to the backup chain, Veeam Backup & Replication checks the retention
policy for the job. If Veeam Backup & Replication detects an outdated restore point, it transforms the
backup chain to make room for the most recent restore point. For more information, see Forever Forward
Incremental Backup Retention Policy.

To use the forever forward incremental backup method, you must select the following options in the backup job
settings:

1. Select the I ncremental backup mode.

2. Do not enable synthetic full backups and active full backups. If you enable synthetic and active full
backups, Veeam Backup & Replication will produce a forward incremental backup chain.

Forward Incremental Backup


The forward incremental backup method produces a backup chain that consists of the first full backup file (VBK)
and a set of forward incremental backup files (VIB) following it. Additionally, the forward incremental backup
chain contains synthetic full and active full backup files that “split” the backup chain into shorter series.

Veeam Backup & Replication creates a forward incremental backup chain in the following way:

1. During the first backup job session, Veeam Backup & Replication creates a full backup file in the backup
repository.

2. During subsequent backup job sessions, Veeam Backup & Replication copies only VM data blocks that have
changed since the last backup job session (full or incremental) and saves these blocks as an increm ental
backup file in the backup chain.

3. On a day when the synthetic full or active full backup is scheduled, Veeam Backup & Replication 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.

1197 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. After adding a new restore point to the backup chain, Veeam Backup & Replication checks the retention
policy set for the job. If Veeam Backup & Replication detects an outdated restore point, it attempts to
remove this point from the backup chain. For more information, see Retention for Forward Incremental
Backup.

The forward incremental backup with synthetic full backup enabled is a default method for backup chain
creation. To use the forward incremental backup method, you can leave the default settings or select the
following options in the backup job settings:

1. Select the Incremental backup mode.

2. Enable synthetic full backups and active full backups. If the synthetic full backup and active full backups
are not enabled, Veeam Backup & Replication will produce a forever forward incremental backup chain.

Reverse Incremental Backup


The reverse incremental backup method produces a backup chain that consists of the last full backup file (VBK)
and a set of reverse incremental backup files (VRB) preceding it.

Veeam Backup & Replication creates a reverse incremental backup chain in the following way:

1. During the first backup job session, Veeam Backup & Replication creates a full backup file in the backup
repository.

2. During subsequent backup job sessions, Veeam Backup & Replication copies only VM data blocks that have
changed since the last backup job session. Veeam Backup & Replication “injects” copied data blocks into
the full backup file to rebuild it to the most recent state of the VM. Additionally,
Veeam Backup & Replication creates a reverse incremental backup file containing data blocks that are
replaced when the full backup file is rebuilt, and add s this reverse incremental backup file before the full
backup file in the backup chain.

1198 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. After adding a new restore point to the backup chain, Veeam Backup & Replication checks the retention
policy set for the job. If Veeam Backup & Replication detects an outdated restore point, it removes this
point from the backup chain. For more information, see Retention for Reverse Incremental Backup.

As a result, the most recent restore point in the backup chain is always a full backup, and it gets updated after
every successful backup job session.

The reverse incremental backup method lets you immediately restore a VM to the most recent state without
extra processing because the most recent restore point is a full backup file. If you need to restore a VM to a
particular point in time, Veeam Backup & Replication applies the required VRB files to the VBK file to get to the
required restore point.

To use the reverse incremental backup method, you must select the Reverse incremental option in the backup
job settings.

Switching Between Backup Methods


You can easily switch between backup methods. Veeam Backup & Replication does not transform the previously
created chain. Instead, it creates a new backup chain next to the existing one in the following manner:

• If you switch from the reverse incremental method to the forever forward incremental or forward
incremental method, Veeam Backup & Replication creates a set of incremental backup files next to the
reverse incremental chain. The full backup file in the reverse incremental chain is used as a starting point
for incremental backup files.

• If you switch from the forever forward incremental or forward incremental method to the reverse
incremental method, Veeam Backup & Replication first creates a full backup file next to incremental
backup files. During every new job session, Veeam Backup & Replication transforms this full backup file
and adds reverse incremental backup files to the backup chain.

1199 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you switch from the forever forward incremental method to the forward incremental method,
Veeam Backup & Replication creates synthetic full backups according to the specified schedule. Old
backup chain is deleted when the number of restore points in the new chain reach the retention limit.

• If you switch from the forward incremental method to the forever forward incremental method, synthetic
full backups are no longer created. When the number of restore points created since the last full backup
reaches the retention limit, the old backup chain is deleted. Thereafter, with each restore point creation
the earliest increment file will merge with the full backup file.

For more information on which settings are required for each method, see the following sections: Forever
Forward Incremental Backup, Forward Incremental Backup and Reverse Incremental Backup.

Backup Chain Formats


When you add repositories to the backup infrastructure, you can configure how many backup files
Veeam Backup & Replication creates for the protected workloads. The type of the created backup files depends
on the selected backup method.

Veeam Backup & Replication provides the following backup chain formats:

• P er-machine backup with separate metadata files (default format starting from
Veeam Backup & Replication version 12)

Veeam Backup & Replication creates one metadata file for each workload in a job. During a job session,
Veeam Backup & Replication creates one backup file for each workload. Compared to other formats, this
format allows managing individual workloads, for example, moving backups to other jobs or creating full
backups.

• P er-machine backup with single metadata file (legacy format starting from Veeam Backup & Replication
version 12)

Veeam Backup & Replication creates one metadata file for all workloads in a job. During a job session,
Veeam Backup & Replication creates one backup file for each workload.

• Sing le-file backup

Veeam Backup & Replication creates one metadata file for all workloads in a job. During a job session,
Veeam Backup & Replication creates one backup file for all workloads.

The backup chain format depends on the Use per-machine backup files option in the backup repository settings
and also the version of Veeam Backup & Replication when the repository was added. You can find the details
further in this section.

1200 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

1201 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For backup copy jobs, consider the following:

o New backup copy jobs always create per-machine backup files with separate metadata files.
o Backup copy jobs created in the previous versions of Veeam Backup & Replication continue to
create backups in the specified formats: single-file backups if the Use per-machine backup files
option was disabled or per-machine backups with single metadata file if the option was enabled.
You can upgrade the backup chain format as described in section Upgrading Backup Chain
Formats.
NOTE

In the Veeam Backup & Replication guide, we use "per-machine backups" when information relates to
both per-machine backups, with single and separate metadata files. If information relates to one
backup chain format only, we name it explicitly — per-machine backup with single metadata file or
per-machine with separate metadata files.

Per-Machine Backup with Separate Metadata Files

The per-machine backup with separate metadata files format is the default option for new repositories
since Veeam Backup & Replication version 12. When you create a repository, check that the Use per-
ma chine backup files option is selected in the repository settings.

When per-machine backup with separate metadata files format is used, a backup job writes data in a
separate stream for each workload. Veeam Backup & Replication saves data of each workload into a
separate backup file and also creates a separate metadata file (.VBM) for each workload.
Veeam Backup & Replication perceives each backup created during one job session as one restore point.
As a result, each workload has its own independent backup chain.

Such way of storing backups is recommended and makes the environment management more flexible.
Veeam Backup & Replication can perform operations with individual workloads, for example, move a
workload and its backups from one job to another, or launch active full backups for individual
workloads.

When Veeam Backup & Replication needs to remove restore points by retention, it analyzes the backup
chain of an individual workload, not all workloads. For more information on the restore point removal,
see Removal of Restore Points.

Per-Machine Backup with Single Metadata File

The per-machine backup with single metadata file format is legacy since Veeam Backup & Replication
version 12. However, backup repositories created in Veeam Backup & Replication prior to version 12 and

1202 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
for which the Use p er-machine backup files option was enabled still create backups in the per-machine
backup with single metadata file format.

When per-machine backup with single metadata file format is used, a backup job writes data in a
separate stream for each workload. Veeam Backup & Replication saves data of each workload into a
separate backup file. However, Veeam Backup & Replication creates a single metadata file (.VBM) for all
workloads and perceives all backups created during one job session as one restore point.

Such way of storing backups is more efficient than single-file backup format. Compared to per-machine
backup with separate metadata files format, Veeam Backup & Replication cannot perform operations
with individual workloads. These operations include moving backups, launching active full for individual
workloads and so on.

When Veeam Backup & Replication needs to remove earlier restore points by retention policy, it
removes backup files of all workloads created during one job session. Veeam Backup & Replication does
not remove data for separate workloads. In some situations a certain workload can have fewer restore
points than it is specified in retention policy settings. For more information on the restore point
removal, see Removal of Restore Points.

Single-File Backup

This is the default way of storing backup files for Veeam Backup & Replication prior to version 12. The
single-file backups are created in backup repositories for which the Use per-machine backup files option
is not selected.

When single-file backup format is used, a backup job writes workload data to a repository in one write
stream. Veeam Backup & Replication saves data of all workloads into the same backup file and creates
one metadata file (.VBM). Such behavior is not optimal if the target storage device is able to write data
in multiple streams simultaneously. In this situation, the backup repository may become the bottleneck
for the data transfer, even though its resources will not be fully utilized.

1203 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When Veeam Backup & Replication needs to remove earlier restore points by retention policy, it
removes backup files of all workloads created during one job session. Veeam Backup & Replication does
not remove data for separate workloads. In some situations a certain workload can have fewer restore
points than it is specified in retention policy settings. For more information on the restore point
removal, see Removal of Restore Points.

Limitations and Considerations for Per-Machine Backup Files

When planning to use per-machine backup files, consider the following limitations:

• We recommend that you use the Use per-machine backup files option, especially for
deduplicating storage appliances used as a backup repositories. Veeam Backup & Replication will
write machine data to the backup repository in several streams, which will improve the backup job
performance. However, deduplication may be less effective compared to deduplication for single-
file backups. Deduplication works within one backup file. For single-file backups, one backup file
stores data for all machines, that is why data is deduplicated for all machines. Per -machine
backups store data for one machine, that is why data is deduplicated for one machine only.

• [For Veeam Agent backup jobs] Veeam Backup & Replication ignores the Use per-machine backup
files option. The way Veeam Backup & Replication creates backup files depends on the objects
included in the backup job:

o If several Veeam Agent machines are included in the backup job, Veeam Backup & Replication
creates a separate backup file for each machine.

o If failover clusters are included in the backup job, Veeam Backup & Replication creates a
separate backup file for each cluster.

Upgrading Backup Chain Formats

Changing the Use per-machine backup files option for repositories does not affect the way backups are
created. To change the backup chain format, use the following instructions:

• Upgrading Backup Chain Formats for backup jobs.

• Upgrading Backup Chain Formats for backup copy jobs.

Full Backup Methods


Veeam Backup & Replication provides the following methods for creation of full backup files:

• Active Full Backup

When you perform active full backup, Veeam Backup & Replication retrieves VM data from the source
volume where the VM resides, compresses and deduplicates it and writes it to the VBK file in the backup
repository.

• Synthetic Full Backup

When you perform synthetic full backup, Veeam Backup & Replication does not retrieve VM data from the
source volume. Instead, it synthesizes a full backup from data you already have in the backup repository.
Veeam Backup & Replication accesses the previous full backup file and a chain of subsequent incremental
backup files on the backup repository, consolidates VM data from these files and writes consolidated data
into a new full backup file. As a result, the created synthetic full backup file contains the same data you
will have if you create an active full backup.

1204 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

You can perform both active and synthetic full backups. For more information on how to do that, see
Backup Settings.

Active Full Backup


In some cases, you need to regularly create a full backup. For example, your corporate ba ckup 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 & Replication lets you create active full backups.

The active full backup produces a full backup of a VM, just as if you run the backup job for the first time.
Veeam Backup & Replication retrieves data for the whole VM from the source, compresses and deduplicates it
and stores it to the full backup file — VBK.

The active full backup resets a backup chain. All incremental backup files use the latest active full backup file as
a new starting point. A previously used full backup file remains on disk until it is automatically deleted according
to the retention policy.

You can create active full backups manually or schedule a backup job to create active full backups periodically.

• To create an active full backup manually, follow the steps described in section Performing Active Full
Backup.

• To schedule active full backups, specify scheduling settings in the Ad vanced section of a backup job. You
can schedule active full backups to run weekly, for example, every Saturday, or monthly, for example,
every fourth Sunday of a month.

1205 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Active Full Backup Schedule
Veeam Backup & Replication automatically triggers a backup job to create an active full backup, even if a regular
backup job session is not scheduled on this day. The job session is started at the same time when the parent
backup job is scheduled. For example, if you schedule the parent backup job at 12:00 AM Sunday through
Friday, and schedule active full backup on Saturday, Veeam Backup & Replication will start a backup job session
that will produce an active full backup at 12:00 AM on Saturday.

If the parent backup job is not scheduled to run automatically or is disabled, Veeam Backup & Replication will
not perform active full backup.

If a regular backup job is scheduled together with active full backup, Veeam Backup & Replication will produce
only an active full backup that will contain the latest state of the source VM. An incremental backup file that
should have been created by the backup job schedule will not be added to the backup chain.

Veeam Backup & Replication creates an active full backup only once a day on which active full backup is
scheduled (unless you create a full backup manually). If you run the backup job again on the same
day, Veeam Backup & Replication will perform incremental backup in a regular manner.

IMP ORTANT

If you schedule a job to start after another job (initial job), but the initial job does not run on days when the
active full backup is scheduled for the chained job, Veeam Backup & Replication will not create active full
backups.

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.

In terms of data, the synthetic full backup is identical to a regular full backup. Synthetic full backup produces a
VBK file that contains data of the whole VM. The difference between active and synthetic full backup lies in the
way VM data is retrieved:

• When you perform active full backup, Veeam Backup & Replication retrieves VM data from the source
volume where the VM resides, compresses and deduplicates it and writes it to the VBK file in the backup
repository.

• When you perform synthetic full backup, Veeam Backup & Replication does not retrieve VM data from the
source volume. Instead, it synthesizes a full backup from data you already have in the backup repository.
Veeam Backup & Replication accesses the previous full backup file and a chain of subsequent incremental
backup files on the backup repository, consolidates VM data from these files and writes consolidated data
into a new full backup file. As a result, the created synthetic full backup file contains the same data you
have if you create an active full backup.

The synthetic full backup has a number of advantages:

• The synthetic full backup does not use network resources: it is created from backup files you already have
on disk.

• The synthetic full backup produces less load on the production environment: it is synthe sized right on the
backup repository.

Veeam Backup & Replication treats synthetic full backups as regular full backups. As well as any other full
backup file, the synthetic full backup file resets the backup chain. All subsequent incremental backup files u se
the synthetic full backup file as a new starting point. A previously used full backup file remains on disk until it is
automatically deleted according to the retention policy.

1206 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• If you enable both synthetic and active full backups and schedule their creation on the same day, the
synthetic full backup is not created.
• If you schedule a job to start after another job (initial job), but the initial job does not run on days
when the synthetic full backup is scheduled for the chained job, Veeam Backup & Replication will
not create synthetic full backups.
• You cannot enable synthetic full backup for backups located in object storage repositories.

To create synthetic full backups, you must enable the Create synthetic full backups periodically option and
schedule creation of synthetic full backups on specific days.

How Synthetic Full Backup Works


To create a synthetic full backup, Veeam Backup & Replication performs the following steps:

1. On a day when synthetic full backup is scheduled, Veeam Backup & Replication triggers a new backup job
session. During this session, Veeam Backup & Replication first performs incremental backup in a regular
manner and adds a new incremental backup file to the backup chain.

Veeam Backup & Replication retrieves VM data for this incremental backup file from the production
storage. Incremental backup helps Veeam Backup & Replication ensure that the synthetic full backup
includes the latest changes of the source VM in the production environment.

1207 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. At the end of the backup job session, Veeam Data Mover on the backup repository builds a new synthetic
full backup using backup files that are already available in the backup chain, including the newly created
incremental backup file.

3. When the synthetic full backup is created, Veeam Data Mover on the backup repository deletes the
incremental backup file created at the beginning of the job session. As a result, you have a backup chain
that consists of a full backup file, set of incremental backup files and synthetic full backup file.

4. Every next job session creates a new incremental restore point starting from the synthetic full backup
until the day on which synthetic full backup is scheduled. On this day, Veeam Backup & Replication creates
a new synthetic full backup.

Synthetic Full Backup Schedule


Veeam Backup & Replication automatically triggers a backup job session to create a synthetic full backup, even
if a regular backup job session is not scheduled on this day. The job s ession is started at the same time when the
parent backup job is scheduled. For example, if you schedule the parent backup job at 12:00 AM Sunday through
Friday, and schedule synthetic full backup on Saturday, Veeam Backup & Replication will start a backup job
session that will produce a synthetic full backup at 12:00 AM on Saturday.

If a regular backup job is scheduled together with a synthetic full backup, Veeam Backup & Replication will
produce only one backup file — a synthetic full backup that will contain the latest state of the source VM. An
incremental backup file that should have been created by the backup job schedule will not be added to the
backup chain.

If an active full backup is scheduled together with a synthetic full backup, Veeam Backup & Replication will
create only the active full backup.

Veeam Backup & Replication creates a synthetic full backup only once a day on which synthetic full backup is
scheduled. If you run the backup job again on the same day, Veeam Backup & Replication will perform
incremental backup in a regular manner.

Short-Term Retention Policy


Every successful backup job session creates a new restore point that lets you roll back VM data to an earlier
point in time. To control the number of restore points in the backup chain, you must specify retention policy
settings. The retention policy defines how many restore points you want to retain on disk and thus how ‘far’ you
are able to roll back. After the allowed number of restore points is exceeded, Veeam Backup & Replication
applies the retention policy — so it removes the earliest restore point from the backup chain.

1208 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To define the retention policy for a backup job, you must specify the necessary number of restore points or days
in the Retention policy field in the backup job settings. By default, Veeam Backup & Replication keeps restore
points for the last 7 days. In the Storage step of the New Backup Job wizard you can select the following units
of retention policy.

• Restore points: Veeam Backup & Replication keeps the last N restore points, where N is the specified
number of restore points.

• Da y s: Veeam Backup & Replication keeps restore points created during the last N days, where N is the
specified number of days.

The daily retention policy can be helpful if you periodically create off-schedule backups. For example, you
create a daily backup job and you want to store retention points for 14 calendar days. If you select 14
restore points and manually create off-schedule backups, there will be several restore points in one day.
So, you will have retention points for less than 14 days. In this case, you can use the d a ys option.

Consider the following for the daily retention policy:

o The minimum number of retained restore points is 3. This number does not depend on the number of
days set in the retention policy. For example, the retention policy is set to 5 days. You launch the job
after it was stopped for 10 days. Normally, Veeam Backup & Replication will delete all previous
restore points. However, due to the minimum number of retained restore points, you will still have at
least 3 restore points: the newly created restore point and the two previous ones.
You can change the minimum number of retained restore points with a registry value. For more
information, contact Veeam Customer Support.

o If the backup job starts at the end of the day and finishes the next day, Veeam Backup & Replication
assumes that the restore point is created at the moment when the backup job started. However,
Veeam Backup & Replication starts counting retention policy days only after the backup job finishes
processing VMs.

o When determining whether the number of allowed days is exceeded, Veeam Backup & Replication
ignores the day when the daily retention policy is applied.

In fact, Veeam Backup & Replication keeps restore points for the N + 1 days, where N is the number of
days that you specify in the job settings. In this case, Veeam Backup & Replication applies retention
policy after the N+1 days are passed. For example, if you set retention policy to keep restore points
for 6 days, Veeam Backup & Replication will keep restore points for 7 days and will apply the
retention policy on the 8th day. Note that the retention period may be longer depending on the
specified backup method.

o When determining whether the number of allowed days is exceeded, Veeam Backup & Replication
also counts days when the backup job did not create any backups.

When the specified number is exceeded, the earliest restore points will be removed from the backup chain or
merged with the next closest restore point. Veeam Backup & Replication handles restore points in different
ways for forever forward incremental, forward incremental and reverse incremental backup chains:

• Forever Forward Incremental Backup Retention Policy

• Retention for Forward Incremental Backup

• Retention for Reverse Incremental Backup

NOTE

When the specified number of restore points or days is exceeded, Veeam Backup & Replication deletes the
whole backup file, not separate VMs from it. For more information, see Removal of Restore Points.

1209 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Forever Forward Incremental Backup Retention Policy
If the number of days or restore points in forever forward incremental backup chains exceeds retention policy
settings, Veeam Backup & Replication transforms the backup chain to make room for the most recent restore
point. The transformation process is performed in the following way:

1. Veeam Backup & Replication adds a new incremental backup file to the backup chain and detects that the
number of allowed restore points or days is exceeded.

2. Veeam Backup & Replication reuses empty data blocks in the full backup file to include changes of the
incremental backup file that follows the full backup. To do that, Veeam Backup & Replication injects data
blocks from the first incremental backup file in the chain into the full backup file. As a result, the full
backup file ‘moves’ one step forward in the backup chain.

NOTE

If the forever forward incremental backup chain resides on a deduplicating storage appliance,
Veeam Backup & Replication does not reuse empty data blocks of the full backup file. Instead,
Veeam Backup & Replication appends data from the first incremental backup file in the chain to the
full backup file. As a result, the backup chain may consume more disk space on the appliance.

3. The first incremental backup file is removed from the backup chain as redundant. Its data has already been
injected into the full backup file, and the full backup file contains the same data as this incremental
backup file.

1210 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For example, you want to keep 7 restore points in the backup chain. The backup job starts on Sunday and runs
daily. In this case, Veeam Backup & Replication will create the backup chain in the following way:

1. During the first backup job session on Sunday, Veeam Backup & Replication creates the first restore point
— a full backup file.

2. Monday through Saturday Veeam Backup & Replication adds six incremental backup files to the backup
chain.

3. The next Sunday, Veeam Backup & Replication adds a new incremental backup file to the ba ckup chain.

4. Veeam Backup & Replication detects that the number of allowed restore points is exceeded, and starts the
transformation process:

a. Veeam Backup & Replication merges data blocks from the incremental backup file created on Monday
into the full backup file created on Sunday. This way, the full backup file ‘moves’ one step forward —
from Sunday to Monday.

b. The incremental backup created on Monday becomes redundant and is removed from the backup
chain.

As a result, you have a chain of a full backup file as of Monday and six incremental backup files Tuesday through
Sunday.

Forward Incremental Backup Retention Policy


To be able to restore from a forward incremental backup, you need to have a full backup file and a chain of
subsequent incremental backup files on disk. If you delete a full backup file, the whole chain of incremental
backup files will become useless. In a similar manner, if you delete any incremental backup file before the point
to which you want to roll back, you won’t be able to restore VM data (since later incremental backup files
depend on earlier incremental backup files).

1211 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For this reason, if you select forward incremental backup method, in some days there will be more restore
points on disk than specified by retention policy settings. Veeam Backup & Replication will remove the full
backup chain only after the last incremental backup file in the chain becomes outdated.

For example, the retention policy is set to 3 restore points. The first full backup file is created on Sund ay,
incremental backup files are created Monday through Saturday, and the second full backup is created on
Thursday. Although the retention policy is already reached on Wednesday, the first full backup is not deleted.
Without the full backup, backup chain will be useless, leaving you without any restore point at all.
Veeam Backup & Replication will wait for the second full backup file and 2 incremental backup files to be
created, and only then will delete the whole previous chain, which will happen on Satur day.

Reverse Incremental Backup Retention Policy


In case of reverse incremental backup, Veeam Backup & Replication immediately deletes the earliest reverse
incremental backup file as soon as it becomes outdated.

For example, you configure a backup job in the following way:

• The backup job starts on Sunday.

• The backup method is reverse incremental.

• Retention policy is set to 6 restore points.

Veeam Backup & Replication will start the backup job on Sunday. Monday through Friday, it will add new restor e
points to the backup chain and rebuild the full backup file. On Saturday, Veeam Backup & Replication will add a
new restore point and remove the earliest reverse incremental backup file (VRB) from the backup chain.

Retention Policy for Deleted Items


In some situations, after you configure and run backup jobs in Veeam Backup & Replication, you may want to
change something in the virtual infrastructure or in the backup strategy. For example, you may remove some
machines from the virtual infrastructure or move them to another location. You may also exclude some
machines from jobs that have already run for some time.

1212 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Retention policy for deleted items functions differently depending on the Use per-machine backup files option.
For details, see Backup Chain Formats.

• [If per-machine is enabled] When you enable retention policy for deleted items,
Veeam Backup & Replication will remove data for machines that are no longer processed by the backup
job from the backup repository.

• [If per-machine is disabled] When you enable retention policy for deleted items,
Veeam Backup & Replication will remove the data about deleted items from the backup job and
Veeam Backup & Replication database. The stored blocks of deleted machines will remain in the
repository. The stored blocks of deleted machines will be removed only when the restore point retention
limit is reached or by the compact full backup file option.

Retention policy for deleted items data is set at the level of the backup job. You must enable the Remove
d eleted items data after option in backup job settings and specify the period of time for which data for deleted
items must be retained in the backup repository.

Consider the following:

• You must use retention policy for deleted items data carefully. We strongly recommend that you set the
retention policy to 7 days or more to prevent unwanted data loss.

• The Remove deleted items data after option lets you control data of deleted or excluded items. In
addition to it, Veeam Backup & Replication applies general retention policy rules to maintain the necessary
number of restore points in the backup chain. For more information, see Retention Policy.

How Retention Policy for Deleted Items Works


If you enable retention policy for deleted items data in backup job settings, Veeam Backup & Replication
performs the following actions:

1. If all machines in the job are processed with the Success status, at the end of the backup job session
Veeam Backup & Replication gets a list of machines in the backup.

2. For every machine in the backup, Veeam Backup & Replication checks the configuration database and gets
the date of the latest backup job session completed with the Success status.

3. Veeam Backup & Replication checks if any machine in the backup meets the following conditions:

o There are no successful backups for the machine for the last N days.

1213 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o There are no corrupted backups for the machine for the last N days.

Where N is the number of days specified in the Remove deleted items data after N days setting.

4. If both conditions are true for some machine, Veeam Backup & Replication removes data for this machine
from the backup. Note that if per-machine is disabled, it does not free up space in the backup repository.
It marks the space as available to be overwritten, and this space is removed during subsequent job
sessions or the full backup file compact operation.

E x ample 1

You create a backup job for 2 VMs and set the retention policy for deleted items to 5 days . The backup job runs
once a day for 7 times and processes VMs in the following way:

• VM 1 is successfully processed during all job sessions.

• VM 2 is successfully processed during the 1st and 2nd backup job sessions. Before the 3 rd job session, VM 2 is
excluded from the job and is not processed by subsequent job sessions.

During the 8th job session, Veeam Backup & Replication will remove data for VM 2 from backups in the backup
repository since there are no successful and corrupted backups for VM 2 for the last 5 days.

E x ample 2

You create a backup job for 2 machines and set the retention policy for deleted machines to 5 days. The backup
job runs once a day for 7 times and processes machines in the following way:

• VM 1 is successfully processed during all job sessions.

• VM 2 is successfully processed during the 1st and 2nd backup job sessions. Starting from the 3 rd job session,
VM 2 fails to be processed, for example, due power loss while machine data is transported.

During the 8th job session, Veeam Backup & Replication will not remove data for VM 2 from backups in the
backup repository. Even though there are no successfully created backups for VM 2 for the last 5 days,
Veeam Backup & Replication will detect that the configuration database contains information about corrupted
backups for VM 2 for the last 5 days.

Limitations for Retention Policy for Deleted Items


• [Per-machine is disabled] Retention policy for deleted items does not function if you enable synthetic full
backups and active full backup.

[Per-machine is enabled] Retention policy for deleted items functions without limitations.

1214 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Removal of Restore Points
Retention works in different ways for per-machine backup with separate metadata files, single-file backup and
per-machine with single metadata file formats. For more information on backup chain formats, see Backup Chain
Formats.

Retention for Per-Machine Backups with Separate Metadata


Files
When you use the per-machine backup with separate metadata files format, Veeam Backup & Replication
creates a separate backup file for each workload during one session. Veeam Backup & Replication perceives each
backup file created during one job session as one restore point. As a result, each workload has its own backup
chain. When Veeam Backup & Replication needs to remove earlier restore points by retention, it analysis the
backup chain of an individual workload, not all workloads.

Removal of Restore Points from Forward Incremental Chains


In case of a forward incremental backup chain, Veeam Backup & Replication does not remove a restore point
immediately. Instead, Veeam Backup & Replication waits for a new full backup (synthetic or active) to be
created and a new backup chain to be started. As soon as the last incremental restore point in the "old" backup
chain is marked as redundant, Veeam Backup & Replication removes the whole "old" backup chain from the
backup repository. For more information, see Retention for Forward Incremental Backup.

For example, a backup job processes 2 VMs: VM 1 and VM 2. According to the retention policy settings, the
backup chain must contain 3 restore points. The backup job ran 3 times and VMs were processed in the following
way:

• VM 1 was successfully backed up 3 times and has 3 restore points.

• VM 2 was not backed up in 2 job sessions and has 1 valid restore point.

During the 4th job run, Veeam Backup & Replication will create new restore points for VM 1 and VM 2 — full
backups. However, Veeam Backup & Replication will not remove the earliest restore point.
Veeam Backup & Replication will wait until a full backup file and 2 incremental backup files are present in
backup chains of each VM. After that, Veeam Backup & Replication will remove the whole outdated backup
chain from the backup repository. During the 5th job run, Veeam Backup & Replication will create new restore
point for VM 1 and VM 2.

1215 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
During the 6th job run, processing of VM 2 will fail. Veeam Backup & Replication will remove the earliest restore
points only of VM 1 because the number of restore points for VM 1 in the active backup chain equals 3 — a full
backup file and 2 incremental backup files. The number of restore points in the active backup chain of the VM 2
is not sufficient to remove restore points.

During the 7th job run, Veeam Backup & Replication will create restore points for VM 1 and VM 2.
Veeam Backup & Replication will remove the earliest restore points only for VM 2 because a new backup chain is
not started for VM 1 and the number of restore points for VM 2 in the active backup chain equals 3 — a full
backup file and 2 incremental backup files.

Removal of Restore Points from Reverse Incremental Chains


In case of a reverse incremental backup chain, Veeam Backup & Replication immediately removes a redundant
restore point when the allowed number of restore points is exceeded. For more inf ormation, see Retention for
Reverse Incremental Backup.

For example, a backup job processes two VMs: VM 1 and VM 2. According to the retention policy settings, the
backup chain must contain 5 restore points. The backup job ran 5 times and VMs were processed in the following
way:

• VM 1 was successfully backed up 5 times and has 5 valid restore points.

• VM 2 was not backed up in 1 job sessions and has 4 valid restore points.

During the 6th job run, Veeam Backup & Replication will create restore points for VM 1 and VM 2.
Veeam Backup & Replication will remove the earliest restore point of VM 1 because the number of restore points
in the backup chain exceeds 5.

During the 7 th job run, Veeam Backup & Replication will create restore points for VM 1 and VM 2.
Veeam Backup & Replication will remove the earliest restore points of VM 1 and VM 2 because the number of
restore points in the backup chain of each VM exceeds 5.

1216 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Retention for Single-File Backups and Per-Machine Backups
with SIngle Metadata File
When you use the single-file backup chain format, Veeam Backup & Replication creates one backup file for all
workloads during one session. When you use the per-machine backup with single metadata file format,
Veeam Backup & Replication creates a separate backup file for each workload during one session. However,
Veeam Backup & Replication perceives all backup files created during one job session as one restore point.

When Veeam Backup & Replication needs to remove earlier restore points by retention policy, it removes backup
files of all workloads created during one job session. Veeam Backup & Replication does not remove data for
separate VMs. In some situations a certain VM may have fewer restore points than it is specified in retention
policy settings. This can happen if a backup job processes multiple workloads, and some workloads fail to be
processed during some job sessions.

Removal of Restore Points from Forward Incremental Chains


In case of a forward incremental backup chain, Veeam Backup & Replication does not remove a restore point
immediately. Instead, Veeam Backup & Replication waits for a new full backup (synthetic or active) to be
created and a new backup chain to be started. As soon as the last incremental restore point in the "old" backup
chain is marked as redundant, Veeam Backup & Replication removes the whole "old" backup chain from the
backup repository. For more information, see Retention for Incremental Backup.

For example, a backup job processes 2 VMs: VM 1 and VM 2. According to the retention policy settings, the
backup chain must contain 3 restore points. The backup job ran 3 times and VMs were processed in the following
way:

• VM 1 was successfully backed up 3 times and has 3 restore points.

• VM 2 was not backed up in 2 job sessions and has 1 valid restore point.

When Veeam Backup & Replication adds a new restore point to the backup chain, it will not remove the earliest
restore point. Veeam Backup & Replication will wait until a new full backup file and 2 incremental backup files
are added to the backup chain. After that, it will remove the whole outdated backup chain from the backup
repository. Restore points in the new backup chain, at the same time, may contain data for both VMs or for one
VM only: Veeam Backup & Replication regards backup files as restore points, not separate VMs in these files.

Removal of Restore Points from Reverse Incremental Chains


In case of a reverse incremental backup chain, Veeam Backup & Replication immediately removes a redundant
restore point when the allowed number of restore points is exceeded. For more information, see Retention for
Reverse Incremental Backup.

For example, a backup job processes two VMs: VM 1 and VM 2. According to the retention policy settings, the
backup chain must contain 5 restore points. The backup job ran 5 times and VMs were processed in the following
way:

• VM 1 was successfully backed up 5 times and has 5 valid restore points.

1217 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• VM 2 was not backed up in 2 job sessions and has 3 valid restore points.

After that, Veeam Backup & Replication will run a new backup job session in which VM 1 and VM 2 will be
successfully processed. When a new restore point is added to the chain, Veeam Backup & Replication will
remove the earliest restore point because the number of restore points in the backup chain exceeds 5. As a
result, you will have 5 restore points for VM 1 and 3 restore points for VM 2.

Long-Term Retention Policy (GFS)


The long-term or Grandfather-Father-Son (GFS) retention policy allows you to store backup files for long
periods of time — for weeks, months and even years. For this purpose, Veeam Backup & Replication does not
create any special new backup files — it uses backup files created while backup job runs and marks these
backups with specific GFS flags.

To mark a backup file for long-term retention, Veeam Backup & Replication can assign to the file the following
types of GFS flags: weekly (W), monthly (M) and yearly (Y). The types of GFS flags that
Veeam Backup & Replication assigns depend on the configured GFS retention policy settings. Depending on
which flag is assigned to a backup, it will be stored for specified number of weeks, months or years.

IMP ORTANT

Consider the following:

• GFS flags can be assigned only to full backup files created during the time period specified in GFS
policy settings.
• For backups located in object storage repositories, GFS flags are assigned to active full backup files
that match the established GFS policy. If you enable GFS retention policy but do not schedule active
full backups, or the active full backup does not match GFS policy, Veeam Backup & Replication will
generate a synthetic full backup and assign a GFS flag to it.

As soon as Veeam Backup & Replication assigns a GFS flag to a full backup file, this backup file can no longer be
deleted or modified. Also, Veeam Backup & Replication does not apply short-term retention policy settings to
the full backup file — that is, Veeam Backup & Replication ignores the backup file when determining whether
the number of allowed backup files is exceeded. For more information on how GFS flags are assigned, see
Assignment of GFS Flags.

1218 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
When the specified retention period ends, Veeam Backup & Replication unassigns the GFS flag from the full
backup file. If the backup file does not have any other GFS flags assigned, it can be modified and deleted
according to the short-term retention policy. For more information on when Veeam Backup & Replication
removes GFS flags, see Removal of GFS Flags.

Limitations
When planning to use GFS retention policy, consider the following limitations:

• GFS retention policy does not apply to reverse incremental backup chains.

• GFS retention policy applies to forever forward incremental backup chain only if you periodically create
full backups manually or using scheduled scripts. For more information on cmdlets that you can use in
scripts, see the Veeam PowerShell Reference.

• If you store backups with GFS flags in the capacity tier with immutability enabled, the GFS retention policy
is not considered. Immutability period depends on the object storage repository settings.

• As Veeam Backup & Replication does not create new full backup files while applying the GFS retention
policy, you must configure your backup jobs in a way you do not lose any essential data due to an
insufficient number of full backup files. For example, if you configure monthly GFS retention, you need at
least one full backup file per month.

• If a GFS flag is assigned to a full backup file in an active backup chain, Veeam Backup & Replication is not
able to merge data from incremental backup files into the full backup file. For forever forward incremental
backup chain, this means, that the short-term retention policy does not apply.

• Veeam Backup & Replication assigns GFS flags only after you save GFS retention policy settings. This
means that GFS flags are assigned only to those backup files created after the configuration, while backup
files created earlier are not affected and previously assigned flags are not modified.

• You cannot store full backups to which GFS flags are assigned in backup repositories with rotated drives.

• Retention policy for deleted items does not apply to full backup files to which GFS flags are assigned.

Assignment of GFS Flags


When configuring GFS retention policy settings, you can choose a number of GFS flag types that
Veeam Backup & Replication will use to mark backup files for long-term retention. Depending on this number,
Veeam Backup & Replication will apply slightly different algorithms when assigning GFS flags:

• Algorithm for One Flag Type

• Algorithm for Multiple Flag Types

1219 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

When you reconfigure GFS retention policy and save it, the following applies:

• If you change the amount of time for which backups with GFS flags must be kept, the previously
created GFS backups will also be kept according to the new settings.
• If you change the time period when GFS flags must be assigned, the previously assigned GFS flags
are not considered when determining whether new GFS flags must be assigned.

Algorithm for One Flag Type


If you select only one type of GFS flags when configuring retention policy settings for a backup job,
Veeam Backup & Replication assigns the flags depending on the scheduled period. The scheduled period is a
period when a new GFS flag must be assigned and is set according to the following schema: for weekly GFS —
the day selected in the GFS retention policy settings; for monthly GFS — the selected week; for yearly GFS — the
selected month.

Depending on the scheduled period settings, Veeam Backup & Replication performs the following steps as soon
as the job finishes:

• If the job finishes within the period when a new GFS flag must be assigned (the scheduled period),
Veeam Backup & Replication checks whether the backup job has created a full backup file.

o Yes, the full backup has been created: If the GFS flag has already been assigned to another backup file
during the scheduled period, Veeam Backup & Replication does not assign another GFS flag to the
backup file. If the GFS flag has not been assigned, Veeam Backup & Replication assigns it and stops
waiting for the full backup file (removes the waiting flag).

o No, the full backup has not been created: Veeam Backup & Replication waits for a full backup file to
be created (sets the waiting flag).

• If the job finishes outside the scheduled period, Veeam Backup & Replication checks whether the full
backup file is being waited for (check whether the waiting flag is set).

o Yes, the waiting flag is set: Veeam Backup & Replication checks whether the backup job has created a
full backup file.

▪ Yes: Veeam Backup & Replication assigns the GFS flag and stops waiting for the full backup file
(removes the waiting flag).

▪ No: Veeam Backup & Replication does not assign a new GFS flag.

1220 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o No, the waiting flag is not set: Veeam Backup & Replication does not assign a new GFS flag.

Consider the following example. On Monday, you configure GFS policy settings of a backup job in a way weekly
GFS flags must be assigned every Wednesday. In this example, Veeam Backup & Replication will take the
following steps.

1221 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E x ample Description

1. Until Wednesday, Veeam Backup & Replication will not assign any GFS flags because the scheduled period
has not started yet.

2. On Wednesday, the backup job will produce an incremental backup file. Veeam Backup & Replication will
start waiting for a full backup file to be created since the scheduled period is now started.

3. On Thursday, the backup job will produce another incremental backup file, while
Veeam Backup & Replication will still be waiting for a full backup file.

4. On Friday, the backup job will produce a full backup file, and Veeam Backup & Replication will
immediately assign the weekly GFS flag to the backup file.

Algorithm for Multiple Flag Types


If you select multiple types of GFS flags when configuring retention policy settings for a backup job, GFS flags
depend on each other. Yearly flags (high level) depend on monthly flags, monthly flags depend on weekly flags,
weekly flags (low level) do not depend on any flags. This means that Veeam Backup & Replication can only
assign GFS flags of a higher level to backup files with GFS flags of a lower level — this mechanism helps you
save space in the backup repository.

1222 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

The described mechanism does not apply to a situation where you select only two types of GFS flags,
yearly and weekly. If you select these two types and do not select the monthly type,
Veeam Backup & Replication treats the case as if you select only one flag type. This means that flags of
each type are assigned according to the algorithm for one flag type.

Veeam Backup & Replication performs the following steps as soon as the job finishes and performs them for GFS
flags of each level. Note that GFS flags of lower levels are processed before flags of higher levels. In the
described algorithm, the "scheduled period" is the following: for weekly GFS — the day selected in the GFS
retention policy settings; for monthly GFS — the selected week; for yearly GFS — the selected month.

• If the job finishes within the period when a new GFS flag must be assigned, Veeam Backup & Replication
checks whether the flag of a lower level is configured in the job settings.

o Yes, the flag of a lower level is configured: If the GFS flag of a lower level has already been assigned
to the backup file created by the job, Veeam Backup & Replication assigns the GFS flag of the current
level and stops waiting for the flag of the current level to be assig ned (removes the current-level
waiting flag). If the GFS flag of a lower level has not been assigned, Veeam Backup & Replication
checks whether the GFS flag of current level has already been assigned to another backup file during
the scheduled period:

▪ Yes, the GFS flag of the current level has already been assigned: Veeam Backup & Replication
does not assign any GFS flags.

▪ No, the flag has not been assigned: Veeam Backup & Replication waits for the flag of the current
level to be assigned (sets the current-level waiting flag)

o No, the flag of a lower level is not configured: Veeam Backup & Replication checks whether the
backup job has created a full backup file.

▪ Yes: If the GFS flag of current level has already been assigned to another backup file d uring the
scheduled period, Veeam Backup & Replication does not assign the GFS flag of the current level
to the backup file. If the GFS flag has not been assigned, assigns it and stops waiting for the GFS
flag of the current level to be assigned (removes the current-level waiting flag).

▪ No: Veeam Backup & Replication waits for a full backup file to be created (sets the current-level
waiting flag).

• If the job finishes outside the scheduled period, Veeam Backup & Replication checks whether the GFS flag
of current level is being waited for (checks whether the current-level waiting flag is set).

o Yes, the flag of the current level has already been assigned: Veeam Backup & Replication does not
assign any GFS flags.

o No, the flag has not been assigned: Veeam Backup & Replication checks whether the backup job has
created a full backup file.

▪ Yes: Veeam Backup & Replication assigns the flag of the current level and stops waiting for the
GFS flag of the current level to be assigned (removes the current-level waiting flag).

1223 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ No: Veeam Backup & Replication does not assign any GFS flags.

Consider the following example. On Monday, you configure GFS policy settings of a backup job in a way weekly
GFS flags must be assigned every Wednesday and monthly GFS flags must be assigned every first week of a
month. In this example, Veeam Backup & Replication will take the following steps.

1224 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E x ample Description

1. On Monday, the backup job will produce an incremental backup file. Veeam Backup & Replication will start
waiting for a full backup file since the monthly scheduled period is now started.

2. On Tuesday, the backup job will produce a full backup file. Although Veeam Backup & Replication will still
be waiting for a full backup file, the full backup file with weekly GFS flag is required.

3. On Wednesday, the backup job will produce an incremental backup file.

4. On Thursday, the backup job will produce an incremental backup file. Veeam Backup & Replication will
start waiting for a full backup file to assign the weekly GFS flag to it since the weekly scheduled period is
now started.

5. On Friday, the backup job will produce a full backup file. Veeam Backup & Replication will immediately
assign the weekly GFS flag to the backup file. As the weekly GFS flag will have been assigned,
Veeam Backup & Replication will also assign the monthly GFS flag to the backup file.

1225 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removal of GFS Flags
When configuring GFS retention policy settings, you can specify the retention period for each type of GFS flags.
After the specified retention period exceeds, Veeam Backup & Replication removes GFS flags.

The date when Veeam Backup & Replication can remove GFS flag is calculated by the following formulas:

• Weekly: date of GFS flag assignment + N * 7 days

• Monthly: date of GFS flag assignment + N months + 1 day

When calculating the date of GFS flag assignment + N months, Veeam Backup & Replication
increases the month ordinal number by N. If the calculated date does not exist,
Veeam Backup & Replication uses the last date of the calculated month.

• Yearly: date of GFS flag assignment + N years + 1 day

Where, N is the value specified in the Keep weekly/monthly/yearly full backups for field. For more information,
see Configure Long-Term Retention

NOTE

Consider the following:

• Veeam Backup & Replication removes GFS flags only during running backup job sessions. This means
that if the backup job does not run on the calculated date, Veeam Backup & Replication will remove
the GFS flag later during the next job session.
• After you change GFS retention policy settings, the date of GFS flag removal is recalculated for
already created restore points.

Consider the following example. At the beginning of January, you create a backup job whose GFS retention
policy settings are configured to assign monthly GFS flags. You want to keep backup files with monthly flags for
1 month and set the value of the Keep monthly full backups for field to 1. Veeam Backup & Replication will
perform the following steps to assign and remove the flags.

1. Veeam Backup & Replication will assign the monthly GFS flag on 1/31/2019.

2. To calculate the date when the monthly flag must be removed, the following formula is used: date of
GFS flag assignment + 1 month. This means that the flag must be removed on 2/31/2019.
However, this date does not exist since the last date of February is 2/28/2019. That is why
Veeam Backup & Replication will remove the GFS flag on 3/1/2019 (which is 2/28/2019 + 1 day).

Background Retention
In addition to applying a retention policy (short-term retention and long-term retention) within a job session,
Veeam Backup & Replication performs background retention for backups. The background retention aims mostly
at backups that are no longer processed by jobs (orphaned backups shown in the node with the ( Orphaned)
postfix). However, this retention can also be helpful for standard backups, in case backups are created by jobs
without schedule, the job retention has not been yet applied or failed for some reason and so on.

The background retention starts automatically every 24 hours at 00:30, runs in the ba ckground and consists of
the following activities:

• Background basic retention

• Background GFS retention

• Background log retention

1226 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Backup cleanup

• Deleted Agent retention

Limitations
The background retention does not apply to the following backups:

• Backups stored on backup repositories with rotated drives.

• Backups stored in the archive tiers of scale-out backup repositories.

• Backups stored in the capacity tier. For details, see section Considerations.

• Imported backups.

• Unstructured Data Backup.

• Replicas (including CDP replicas).

• VeeamZIP backups.

• Exported backups.

• Copied backups.

• Backups exported by K10 policies.

• Backups created by Veeam Plug-ins for Enterprise Applications.

Considerations
Consider the following:

• Like the job retention, the background retention cannot delete immutable backup files. The background
retention waits until the immutability and retention periods end for these files.

• [For backups linked to jobs] If the retention is set in days, Veeam Backup & Replication leaves at least 3
backup files in a backup chain regardless of the set retention. If the retention is set in restore points,
Veeam Backup & Replication leaves backup files in a backup chain. The minimum number of backup files
left equals the current retention period. You can delete these backup files manually as described in section
Deleting Backups from Disk.

• [For orphaned backups] If the retention is set in days, Veeam Backup & Replication can remove all
outdated backup files in a backup chain. If the retention is set in restore points,
Veeam Backup & Replication leaves backup files in a backup chain. The minimum number of backup files
left equals the current retention period. You can delete these backup files manually as described in section
Deleting Backups from Disk.

• [For backups stored in the capacity tier] Background retention job does not delete capacity tier copies of
backup data directly. However, if background retention removes local copies of backups, they may also be
marked for removal on capacity tier. In such a case, cleanup during the next SOBR offloading session will
remove them from the capacity tier.

• [For backups created with Veeam Agents operating in standalone or managed by Veeam Agent mode] For
backups stored in an object storage repository operating in the direct connection mode, basic retention
and GFS retention do not apply. For non-orphaned backups stored on other repositories, basic retention
does not apply.

1227 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Unlike the job retention, the background retention does not merge data from one backup file to another,
it just deletes files. In case of forever forward incremental and forward incremental backup chains, the
background retention deletes incremental files only after the last increment in the related part of the
backup chain becomes outdated.

• The background retention does not delete backup files if they are locked by other processes. The
retention waits until the backup file is unlocked.

• You can launch the background retention manually as described in section Launching Background
Retention.

Background Basic Retention


Background basic retention process analyzes the retention period set for backup files. In case of orphaned
backups, Veeam Backup & Replication analyzes the retention period that was set in the job which created this
backup. If the retention period has expired, Veeam Backup & Replication removes the backup files.

Background GFS Retention


Background GFS retention process detects backup files with GFS flags and analyzes their retention period. If the
retention period for GFS flags of such backup files has expired, Veeam Backup & Replication removes GFS flags.
Then Veeam Backup & Replication deletes these backup files according to the short-term retention policy, if the
following conditions are met:

• The backup file does not have any other GFS flags assigned.

• The backup file does not have any dependent files.

Background retention job applies to backup files created by all the types of jobs that use GFS. For more
information about GFS retention policy, see Long-Term Retention Policy (GFS).

Background Log Retention


Background log retention detects logs whose related image-level backup was deleted by background retention.
Then Veeam Backup & Replication deletes these log files.

Backup Cleanup
Backup cleanup applies only to orphaned backups. After the whole orphaned backup chain is deleted,
Veeam Backup & Replication also deletes the .VBM file and the folder where the backup chain was stored.

Deleted Agent Retention


Deleted agent retention is a process that detects and deletes outdated backup files according to Veeam Agent
retention policy for outdated backups.

An outdated backup file is a backup file for which no new restore points were created and no new backup job
sessions were started within the last N days, where N is the retention period specified in the Veeam Agent
backup job settings.

For more information, see Retention Policy for Outdated Backups article in the Veeam Agent for Microsoft
Windows User Guide and Maintenance Settings article in the Veeam Agent Management Guide.

1228 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cloud Connect Background Retention
In the Veeam Cloud Connect infrastructure, independent retention is applied to tenant backups on the service
provider side. The background retention job runs automatically in Veeam Backup & Replication on the service
provider backup server according to the same rules as in the regular Veeam backup infrastructure. The service
provider can also launch background retention manually as described in section Launching Background
Retention.

On the tenant side, Veeam Cloud Connect repositories are skipped from processing by the background retention
job launched automatically and manually. For more information, see the Background Retention for Tenant
Backups section in the Veeam Cloud Connect Guide.

1229 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Changed Block Tracking
When Veeam Backup & Replication performs incremental backup, it needs to know what data blocks have
changed since the previous job session. To get the list of changed data blocks, Veeam Backup & Replication uses
the changed block tracking mechanism, or CBT. CBT increases the speed and efficiency of incremental backups.

Veeam Backup & Replication uses CBT for the following operations:

• Backup

• Replication

• Entire VM restore

Veeam Backup & Replication enables CBT. You can disable it either at the host level or at the job level for
troubleshooting purposes. Note that if you choose to run incremental jobs with CBT disabled, the backup
window may increase dramatically, as Veeam Backup & Replication will read all VM data to detect what blocks
have changed since the last job session.

To keep track of changed data blocks, Veeam Backup & Replication uses the following mechanisms:

• [For VMs on Microsoft Hyper-V Servers 2012 R2 and earlier] Veeam proprietary changed block tracking
mechanism (CBT)

• [For VMs on Microsoft Hyper-V Server 2016 and later] Resilient Changed Tracking

Veeam CBT
The CBT mechanism is implemented as a file system filter driver — Veeam CBT driver. The driver is installed on
every Microsoft Hyper-V host added to the backup infrastructure. The driver is activated when the host is first
addressed by a job for which CBT is enabled.

1230 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The Veeam CBT driver keeps track of changed data blocks in virtual disks. Information about changed data
blocks is registered in special CTP files. When a job runs, Veeam Backup & Replication uses CTP files to find out
what data blocks have changed since the last run of the job, and copies only changed data blocks from the disk
image.

CTP files are stored in the C:\ProgramData\Veeam\CtpStore folder on standalone Microsoft Hyper-V hosts
or on every node of the Microsoft Hyper-V cluster. The CtpStore folder contains a set of subfolders — one for
every processed VM, in which the following files are stored:

• CTP files. These files are used by the Veeam CBT driver to keep track of changed data blocks. For every
VHD/VHDX or AVHD/AVHDX file of a VM, there is a separate CTP file.

• notes.txt file. This file contains basic information about the VM such as VM name and ID, and describes
for which VHD/VHDX files changed block tracking is enabled.

If a Microsoft Hyper-V VM is registered as a cluster resource, the Veeam CBT driver operates on al l cluster nodes
that have access to VM disks on the CSV. When a job runs, Veeam Backup & Replication copies CTP files to the
temporary folder on the backup proxy used by the backup job.

• If backup or replication is performed in the on-host backup mode, CTP files are copied to the Microsoft
Hyper-V host performing the role of the on-host backup proxy. For more information, see On-Host
Backup.

• If backup is performed in the off-host backup mode, CTP files are copied to the off-host backup proxy. For
more information, see Off-Host Backup.

IMP ORTANT

If you process VMs on a Microsoft Hyper-V cluster, make sure that all cluster nodes are online. If cluster
nodes are in the Maintenance mode, have the cluster service stopped, are powered off or not accessible,
CBT will not work. For more information about other requirements for VMs on clusters and SMB3 storage,
see this Veeam KB article.

Resilient Changed Tracking


For VMs running on Microsoft Hyper-V Server 2016 or later, Veeam Backup & Replication uses Resilient Change
Tracking, or RCT. RCT is a native Microsoft Hyper-V mechanism for changed block tracking in virtual hard disks
of VMs.

The RCT mechanism is used only if the Microsoft Hyper-V environment meets the following requirements:

• VMs run on Microsoft Hyper-V Server 2016 or later.

• [For Microsoft Hyper-V clusters] All hosts in the cluster are upgraded to Microsoft Hyper-V Server 2016 or
later, and the cluster functional level is upgraded to 2016. If at least one node in a cluster is not upgraded
to Microsoft Hyper-V Server 2016 or later, Veeam Backup & Replication does not use changed block
tracking.

• VM configuration version is upgraded to 8.x.

1231 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For backup and replication with RCT, Veeam Backup & Replication uses the following mechanism:

1. Veeam Backup & Replication triggers Microsoft Hyper-V to create a checkpoint for a processed VM. The
checkpoint is used as a data source for backup and replication.

2. At the end of VM processing, before a checkpoint is merged with the base VM disk, Microsoft Hyper -V
converts the checkpoint to a reference point. The reference point can be thought of as a point-in-time
representation of the VM disk state.

3. When Veeam Backup & Replication performs incremental backup or replication, it creates a new
checkpoint for the VM that is used as a data source. Veeam Backup & Replication queries Microsoft Hyper-
V to get incremental changes between the reference point created during the previous job session and
checkpoint created during the current job session.

4. Veeam Backup & Replication copies only changed data blocks from the created checkpoint and saves them
in an incremental backup file.

To guarantee persistence of CBT data, Microsoft RCT maintains 3 bitmaps with CBT data:

• In-memory bitmap contains the most granular CBT data.

• RCT file contains less granular CBT data than the in-memory bitmap. The RCT file is used if the CBT data in
the in-memory bitmap is not available during normal operational situations, for example, a VM is moved to
another host.

• MRT file has the coarsest granularity level. The MRT file is used if the CBT data in the in-memory bitmap is
not available during abnormal operational situations, for example, power loss or host crash.

RCT and MRT files are created for every VM disk and stored at the VM dis k level.

CBT Reset (Microsoft Hyper-V Server 2012 R2 and Earlier)


In some cases, CBT data may get corrupted — as a result, Veeam Backup & Replication will fail to process VMs
with changed block tracking. To reset CBT data for individual VMs or specific VHD/VHDX files, you can use the
Reset-HvVmChangeTracking PowerShell cmdlet. For more information, see the Veeam PowerShell Reference.

Note that CBT data is reset when you perform product upgrade. When you run a backup job for the first time
after upgrade, Veeam Backup & Replication will not use changed block tracking. Instead, it will scan the VM
image to learn what data blocks have changed.

1232 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Compression and Deduplication
Veeam Backup & Replication provides mechanisms of data compression and deduplication. Data compression
and deduplication let you decrease traffic going over the network and disk space required for storing backup
files and VM replica files.

Data Compression
Data compression decreases the size of created files but affects duration of the backup or replication procedure.
Veeam Backup & Replication allows you to select one of the following compression levels:

• None compression level is recommended if you plan to store backup files and VM replica files on storage
devices that support hardware compression and deduplication. Disabled compression can reduce
performance due to the increased amount of data to be transferred.

• Ded upe-friendly compression level is recommended for some deduplicating storage appliances and when
external WAN accelerators are used.

• Op timal compression level is the recommended compression level. It provides the best ratio between
compression and performance, the lowest backup proxy CPU usage and the fastest restore.

• Hig h compression level provides up to 60% of additional data reduction over the Op timal compression
level at the cost of 2x higher CPU usage and 2x slower restore.

• E x treme compression level provides up to 33% of additional data reduction over the Hig h compression
level at the cost of 5x higher CPU usage.

• [For backup copy job] Auto is the recommended compression level for backup copy jobs. Select this level
to use compression settings of the copied backup files.

NOTE

If encryption is enabled for a job and the Decompress backup data blocks before storing check box is
selected in the settings of the target backup repository, Veeam Backup & Replication does not compress
VM data. Therefore, in the job statistics, you may observe a higher amount of transferred data (the
Tra nsferred counter) as compared to a job for which encryption is disabled. For more information on job
statistics, see Viewing Real-Time Statistics.

In the properties of the backup created with encryption, you may also see that the backup size (the Ba ckup
Size column) is larger than the original VM size (the Original Size column). For more information on backup
properties, see Viewing Backup Properties.

Changing Data Compression Settings


You can change data compression settings for existing jobs. After you change the settings, you will not need to
create new full backups to use new settings. Veeam Backup & Replication will automatically apply the new
compression level to the newly created backup files after you save the settings. Previously created backup files
will not be affected.

1233 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
However, if you use the reverse incremental backup method, the newly created backup files will contain a
mixture of data blocks compressed at different levels. For example, you have a backup job that uses the reverse
incremental backup method and the Optimal level of compression. After several job sessions, you change the
compression level to High. In the reverse incremental backup chains, the full backup file is rebuilt with e very job
session to include new data blocks. As a result, the full backup file will contain a mixture of data blocks: data
blocks compressed at the Optimal level and data blocks compressed at the High level. The same behavior
applies to synthetic full backups: synthetic full backups created after the compression level change will contain
a mixture of data blocks compressed at different levels.

If you want the newly created backup file to contain data blocks compressed at one level, you can create an
active full backup. Veeam Backup & Replication will retrieve data for the whole VM image from the production
infrastructure and compress it at the new compression level. All subsequent backup files in the backup chain
will also use the new compression level.

Deduplication
Data deduplication decreases the size of files. With data deduplication enabled, Veeam Backup & Replication
does not store to the resulting file identical data blocks and space that has been pre -allocated but not used.

We recommend you enable data deduplication if your backup jobs contain several VMs that have a lot of free
space on their logical disks or VMs that have similar data blocks — for example, VMs that were created from the
same template. However, note that data deduplication may decrease job performance.

Veeam Backup & Replication uses Veeam Data Movers to deduplicate VM data:

• Veeam Data Mover in the source side deduplicates VM data at the level of VM disks. Before the source -
side Veeam Data Mover starts processing a VM disk, it obtains digests for the previous restore point in the
backup chain from Veeam Data Mover in the target side. The source-side Veeam Data Mover consolidates
this information with CBT information from the hypervisor and filters VM disk data based on it. If some
data block exists in the previous restore point for this VM, the source-side Veeam Data Mover does not
transport this data block to the target. In addition to it, in case of dynamically expanded disks the source -
side Veeam Data Mover skips unallocated space.

• Veeam Data Mover in the target side deduplicates VM data at the level of the backup file. It processes
data for all VM disks of all VMs in the job. The target-side Veeam Data Mover uses digests to detect
identical data blocks in transported data, and stores only unique data blocks to the resulting backup file.

You can change data deduplication settings for existing jobs. After you change the settings, you will not need to
create new full backups to enable or disable the dedup lication. Veeam Backup & Replication will automatically
apply the change to the newly created backup files after you save the settings. Previously created backup files
will not be affected.

Storage Optimization
To optimize job performance and storage usage, Veeam Backup & Replication allows you to choose the
minimum data block size to process VMs. The optimal data block size depends on the type of storage you select
as a target and the size of your files.

When selecting the data block size, consider the following aspects:

• When reading the VM image, Veeam Backup & Replication "splits" the VM image into blocks of the
selected size. The more data blocks there are, the more time is required to process the VM image.

• [For replication and VMware Cloud Director replication] Veeam Backup & Replication writes information
about every data block to the VM replica metadata stored in the backup repository. The more data blocks
there are, the more metadata is written to the backup repository.

1234 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• [For changed block tracking enabled] During incremental job runs, Veeam Backup & Replication uses CBT
to define changed data blocks in the VM. The larger the size of the found changed data block, the greater
the amount of data that is transferred to the target site.

The incorrectly chosen data block size may decrease the performance. For example, when you deduplicate a
large backup file to small data blocks, Veeam Backup & Replication produces a very large deduplication
metadata table, which can potentially overgrow memory and CPU resources of your backup repository. For large
backup files, it is better to use large data blocks.

Veeam Backup & Replication provides several storage optimization options with different block sizes used. The
following table will help you to choose the optimal option in accordance with the size of your backup files and
the storage type.

Storage optimization Description


op tion

4 MB (former Loca l Recommended for files that are larger than 16 TB.
ta rget (large b locks))
This option will provide the lowest deduplication ratio and the largest size of
incremental files.

1 MB (former Local Recommended for backup and replication to SAN, DAS or local storage.
ta rget)
This option provides the fastest job performance but reduces the deduplication
ratio, because with larger data blocks it is less likely to find identical blocks.

512 KB (former LAN Recommended for backup and replication to NAS, and on-site backup and
ta rget) replication.

This option provides a better deduplication ratio and reduces the size of a file
because of reduced data block sizes.

256 KB (former W AN Recommended if you are planning to use WAN for off-site backup and replication.
ta rget)
This option provides the maximum deduplication ratio and the smallest size of files
that allows you to reduce the amount of traffic over WAN.

Changing Storage Optimization Settings


You can change storage optimization settings for existing jobs. New settings will not have any effect on
previously created files in the chain. They will be applied to new files created after the settings were changed.

For Veeam Backup & Replication to apply the new settings, use the following instructions.

Ba ckup Jobs

To apply new storage optimization settings in backup jobs, you must create an active full backup after you
change storage optimization settings. Veeam Backup & Replication will use the new block size for the active full
backup and subsequent backup files in the backup chain.

Ba ckup Copy Jobs

To change data block size for backup copy jobs, you must perform the following actions:

1. Change data block size in settings of the initial backup job.

1235 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Create an active full backup with the initial backup job.

3. Create an active full backup with the backup copy job.

1236 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Exclusion
When you configure a backup or replication job, you can define what data you want to back up and replicate and
exclude data that you do not need. Data exclusion helps reduce the size of the VM backup or replica and
decrease the load on the network.

You can exclude data at the VM level and at the VM guest OS level.

At the VM level:

• VMs added as part of the container

• VM disks

At the VM guest OS level:

• Swap files on the VM guest OS

• Deleted file blocks on the VM guest OS (BitLooker)

• Files and folders on the VM guest OS

VMs and VM Disks


When you configure a backup or replication job, you can exclude the following objects from processing:

• VMs added as a part of a VM container

• Individual VM disks

VMs as Part of Container


If you want to back up or replicate a VM container that holds several VMs but want to skip some VMs, you can
exclude specific VMs from the job processing. This option will help you reduce the size of the resulting backup
or replica and increase the job performance.

You can define which VMs you want to skip at the Virtual Machines step of the backup or replication job wizard.

1237 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Individual VM Disks
You can choose what VM disks you want to back up or replicate:

• All VM disks

• 0:0 disks (which are commonly the VM system disks)

• Specific IDE, SCSI disks

For example, you may want to back up or replicate only the system disk instead of creating a backup or replica
of a full VM. VM disks exclusion reduces the size of the backup or replica.

You can define which VM disks you want to back up or replicate at the Virtual Machines step of the backup or
replication job wizard. You can specify disk processing settings granularly for every VM in the job or for the
whole VM container. In the latter case, Veeam Backup & Replication will apply the configured rule to all VMs in
this container.

Deleted File Blocks (BitLooker)


Deleted file block exclusion is a technology that reduces backup size and time required to create a backup. As a
rule, file systems do not zero out blocks of permanently deleted files, they only remove informati on about such
files from the file allocation table. This means that the file content still exists on the disk image and enlarges
the backup size. Deleted file blocks exclusion helps avoid copying this unnecessary data or, in Veeam terms,
"dirty" blocks.

By default, deleted file block exclusion is enabled. If you do not want to exclude deleted file blocks from
backups or replicas, you can disable the E x clude deleted file blocks option in the backup or replication job
settings.

NOTE

If you enable or disable the E x clude deleted file blocks setting for the existing job,
Veeam Backup & Replication will apply the new setting from the next job session.

1238 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Deleted File Block Exclusion Works
With this option enabled, Veeam Backup & Replication performs the following operations during the job session:

1. Veeam Backup & Replication accesses the MFT file on the VM guest OS to identify deleted file blocks, and
zeros out these blocks.

2. Veeam Backup & Replication processes and transports data blocks of the VM image in the following
manner:

o If a data block of the VM image contains only the deleted file blocks, Veeam Backup & Replication
does not read this data block from the source volume.

o If a data block of the VM image contains zeroed out blocks and other data,
Veeam Backup & Replication copies this block to the target. Due to data compression, data blocks
that are marked as deleted are compressed, and the size of the resulting backup or replica file
reduces.

Limitations for Deleted File Blocks Exclusion


Deleted file blocks exclusion has the following limitations:

• Veeam Backup & Replication can exclude deleted file blocks only on the VM guest OS with Microsoft
NTFS.

• Veeam Backup & Replication supports both basic and dynamic disks. For the dynamic disks, simple type of
volumes is supported. Spanned, mirrored and striped volumes are not supported.

1239 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Swap Files
You can instruct Veeam Backup & Replication to exclude pagefile.sys and hiberfil.sys files from
backups or replicas of Microsoft Windows VMs. As a result, the size of incremental backups and replicas will be
smaller.

• hiberfil.sys is a system file created by the OS for correct work of the hibernate mode.

• pagefile.sys is a swap file. Swap files are dynamic in nature and can change intensively between job
sessions, even if a VM itself does not change much.

How Swap File Exclusion Works


When you exclude pagefile.sys and hiberfil.sys files, Veeam Backup & Replication performs the
following operations during the job session:

1. Veeam Backup & Replication accesses the MFT file on the VM guest OS to identify data blocks of
pagefile.sys and hiberfil.sys files and zeros them out.

2. Veeam Backup & Replication processes and transports data blocks of the VM image in the following
manner:

o If a data block of the VM image contains only blocks of these files, Veeam Backup & Replication does
not copy this data block to the target.

o If a data block of the VM image contains blocks of these files and other data,
Veeam Backup & Replication copies this block to the target.

Limitations for Swap File Exclusion


Veeam Backup & Replication can exclude blocks of pagefile.sys and hiberfil.sys files only on the VM
guest OS with Microsoft Windows NTFS.

VM Guest OS Files
If you do not want to back up or replicate some files and folders on the VM guest OS, you can exclude them
from the backup or replica. Files exclusion reduces the size of the backup or replica but may affect the job
performance.

You can specify file exclusion settings granularly for every VM in the job or for the whole VM container. In the
latter case, Veeam Backup & Replication will apply the configured rule to all VMs in this container.

To define which VM guest OS files must and must not be processed, you can use the f ollowing options:

• Disable file exclusion.

Veeam Backup & Replication will back up or replicate the whole content of the VM guest file system.

1240 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Exclude specific files and folders from the backup or replica.

Veeam Backup & Replication will back up or replicate all files and folders except the specified ones.

• Include only specific files and folders in the backup or replica.


Veeam Backup & Replication will back up or replicate only the specified files and folders.

Defining File Exclusions and Inclusions


To define a list of exclusions or inclusions, you can use the following methods:

• Specify a full path to a folder on the VM guest OS, for example, C:\Documents\.

• Specify a full path to a file on the VM guest OS, for example: C:\Documents\MyReport.docx.

If a path is not full, Veeam Backup & Replication will expand it to the root directory on the computer
volume and attempt to detect such files on all computer volumes. For example, you have C, D and E disks
on the VM. In the list of exclusions, you specify Document.docx. Veeam Backup & Replication will scan
the whole file system and exclude the following files (if any): C:\Document.docx, D:\Document.docx,
E:\Document.docx. If there is a C:\MyDocuments\Document.docx file, it will not be excluded — this
file is not located in the root directory.

• Use environmental variables, for example, %TEMP%, %windir%.

Environment variables must be defined for the user account that you use to connect to the VM guest OS
and under which the non-persistent runtime components or persistent agent components are started. For
example, you connect to the VM guest OS under the Administrator account. If you want to use the
%windir% variable in the list of exclusions or inclusions, you must make sure that the %windir% variable
is added to the list of user variables for Administrator on the VM guest OS.

• Use file masks. You can use the following characters for masks:

o (*) — a substitution for one or more characters in the file name or path. Can be used for any sequence
of characters (including no characters). For example, *.pdf.

o (?) — a substitution of one character in the file name or path. For example, repor?.pdf.

o (;) — mask separator, for example, report.*;reports.*.

In the table below, mask stands for any sequence of characters.

Ma sk format Affects paths/files

*mask* All paths that contain the given sequence.

mask* If the asterisk character (*) is not specified at the beginning of the
mask, the mask will be applied to all volumes on the VM guest OS,
and Veeam Backup & Replication will include/exclude files and
folders in the root folder on the volume: A:\mask*, B:\mask*,
…, Z:\mask*.

<drive_letter>:\*mask* All paths on the specified volume that contain the given sequence.

1241 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Ma sk format Affects paths/files

*mask1*;*mask2*;*mask3* All paths that contain at least one of the given character sequences:
*mask1* or *mask2* or *mask3*.

Requirements and Limitations for VM Guest OS File Exclusion


VM guest OS files exclusion has the following limitations:

• File exclusion works only on Microsoft Windows NTFS.

• File exclusion is included in the Veeam Universal License. When using a legacy socket-based license,
Enterprise or higher edition is required.

• To exclude VM guest OS files, Veeam Backup & Replication must be able to deploy the non-persistent
runtime components or use (in necessary, deploy) persistent agent components inside the VM. For this
reason, the VM must be running and accessible by an IP address or through the Installer Service on VM,
and credentials for application-aware processing must be valid.

• Veeam Backup & Replication supports both basic and dynamic disks. For the dynamic disks, s imple type of
volumes is supported. Spanned, mirrored and striped volumes are not supported.

• It is not recommended that you use VM guest files exclusion in Microsoft Windows for volumes with
enabled Data Deduplication. If you decide to use VM guest files exclusion for such volumes and set up a
list of inclusions, you must add the System Volume Information folder to the list of inclusions.

Consider the following:

• Be careful when using masks with double wildcard characters. If you specify masks of such ty pe,
Veeam Backup & Replication will exclude all files and paths that contain the given mask. For example, if
you specify the *.doc* mask, Veeam Backup & Replication will exclude files like MyReport.docx,
Report.doc.txt and so on.

• If you use file masks for file exclusion, Veeam Backup & Replication will scan the VM guest file system, and
thus the time of VM disk processing will increase.

1242 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The number of entries in the list of exclusions or inclusions must not exceed a few hundreds. The number
of entries in the list influences the job performance — the more files are included or excluded from the
backup or replica, the more time Veeam Backup & Replication requires to process these files.

• It is recommended that you do not exclude system files without the necessity.
Veeam Backup & Replication does not perform any checks to verify the VM image integrity.

• Exclusion of small files (less than 2 KB in size) is ineffective and will not reduce the size of the backup or
replica significantly.

Exclusion Rules for VMs with Several Volumes


The VM guest file exclusion and inclusion functionality works at the volume level. Consider the following
situations:

Data exclusion
A VM has several volumes: C:\, D:\ and E:\. You want to exclude from the backup the Archive files and
folders that are present at the root folder on all volumes of the VM. If you add the C:\Archive folder to the
list of exclusions, Veeam Backup & Replication will back up the following data:

• Whole content of the C:\ volume except the Archive folder

• Whole content of D:\ and E:\ volumes

To exclude the Archive files and folders from the root folder from all volumes of the VM, you must Archive*
to the list of exclusions.

Data inclusion
A VM has several volumes: C:\, D:\ and E:\. You want to include to the backup only the D:\Documents
folder. If you add the D:\Documents folder to the list of inclusions, Veeam Backup & Replication will back up
the following data:

• D:\Documents folder

• Whole content of C:\ and E:\ volumes

To include only the D:\Documents folder to the backup, you must add the D:\Documents folder to the list of
inclusions and, additionally, exclude unnecessary disks (that contain C:\ and E:\ volumes) at the Virtual
Ma chines step of the wizard. For more information, see Exclude Objects from Backup Job.

How VM Guest OS File Exclusion Works


When you exclude VM guest OS files from the backup or replica, Veeam Backup & Replication performs the
following operations:

1. Veeam Backup & Replication checks the job settings to identify what VM guest OS files must be excluded.

2. Veeam Backup & Replication opens the MFT file from the VM guest file system in the memory cache on
the backup proxy, and marks data blocks of excluded files as deleted.

1243 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. When Veeam Backup & Replication copies VM data to the target, it reads data both from the VM snapshot
and memory cache on the backup proxy. On the target, Veeam Backup & Replication creates a "merged"
version of VM disks that do not contain excluded VM guest OS files. Due to data compression, data blocks
that are marked as deleted are compressed, and the size of the resulting backup or replica file reduces.

During the job session with file exclude, Veeam Backup & Replication makes changes to processed VM disks at
the NTFS level using the cache on the backup proxy. However, these changes are not visible to the CBT
mechanism. For this reason, Veeam Backup & Replication saves information about excluded data blocks in the
backup file and replica metadata. During the next job session with use of CBT, Veeam Backup & Replication
retrieves a list of data blocks that were excluded during the previous job session from the backup file or replica
metadata and analyzes what data needs to be processed during the current job session. To do this,
Veeam Backup & Replication regards the following data:

• Data blocks that are marked as new with CBT

• Data blocks that were excluded during the previous job session

• Data blocks that must be excluded during the current job session

1244 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft Hyper-V Guest Quiescence
When you back up or replicate a running VM, you need to quiesce or ‘freeze’ the VM to bring its file system and
application data to a consistent state. Data quiescence is crucial for highly -transactional applications. It helps
create transactionally consistent backups or replicas and guarantee safety of application data.

To create transactionally consistent backups and replicas for VMs that do not support Microsoft VSS (for
example, Linux VMs), you must enable Microsoft Hyper-V guest quiescence for the job. In this case,
Veeam Backup & Replication will use a native Microsoft Hyper-V approach to quiesce the VM. Microsoft Hyper-V
guest quiescence helps freeze the file system and application data on the VM and create a stable shadow copy
of the volume where VM data resides.

NOTE

To create consistent backups for such VMs, applications should be prepared using special pre -freeze and
post-thaw scripts that you should create and store on the backup server beforehand. When the job starts,
Veeam Backup & Replication will upload these scripts to the appropriate folders on VM guest. For more
information, see Pre-Freeze and Post-Thaw Scripts.

To quiesce the VM, Veeam Backup & Replication can use the following methods:

• Online backup (Microsoft Hyper-V method)

• Offline backup (Microsoft Hyper-V method)

• Crash-consistent backup (Veeam method)

The quiescence method is selected in the following way:

• If a VM meets all requirements for online backup, Veeam Backup & Replication will use the online backup
method.

• If a VM does not meet requirements for online backup, Veeam Backup & Replication will use the offline
backup method. During offline backup a VM is suspended for a short period of time.

If you do not want to suspend the VM, you can instruct Veeam Backup & Replication to create a crash-
consistent backup instead of creating a transactionally consistent backup with the offline backup method.

Microsoft Hyper-V guest quiescence is enabled at the job level for all VMs added to the job. By default, this
option is disabled.

NOTE

Consider the following:

• Offline backup is not applicable to VMs registered on Microsoft Hyper-V Server 2016 or later.
• By default, Veeam Backup & Replication uses application-aware processing when both Microsoft
Hyper-V guest quiescence and application-aware processing are enabled. If some VMs cannot be
quiesced with application-aware processing or it is disabled for specific VMs in the job (the Disable
a p plication processing is set for VMs in the job settings), Veeam Backup & Replication uses Microsoft
Hyper-V guest quiescence to prepare these VMs for backup or replication.

1245 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1246 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Guest Processing
If you back up or replicate running VMs, you can enable guest processing options. Guest processing options are
advanced tasks that help Veeam Backup & Replication to communicate with the VM guest OS. Using guest
processing options, Veeam Backup & Replication creates transactionally consistent backups, replicas, and
catalogs of files and folders on the VM guest OS.

To coordinate guest processing activities, Veeam Backup & Replication deploys non-persistent runtime
components or uses (if necessary, deploys) persistent agent components on the VM guest OS. For more
information, see the Non-Persistent Runtime Components and Persistent Agent Components section. The non-
persistent runtime components run only during guest processing and are stopped immediately after the
processing is finished (depending on the selected option, during the backup job session or after the backup job
finishes).

Veeam Backup & Replication offers the following guest processing options:

Application-Aware Processing
By default, Veeam Backup & Replication does not process application logs and creates a crash-consistent backup
of VMs with applications that use transaction logs for operations. You can create a transactionally consistent
backup - in this case Veeam Backup & Replication will process application logs. In case a disaster strikes,
Veeam Backup & Replication will use backups of logs to perform recovery operations. You can create
transactionally consistent backups and replicas of VMs that run Microsoft Active Directory, Microsoft Exchange,
Microsoft SharePoint, Microsoft SQL Server, Oracle Database or PostgreSQL instances. Transactionally
consistent backups guarantee proper recovery of these applications without data loss. For information on
system requirements for the applications, see System Requirements.

When you define the job settings, you can set up the following application-aware processing settings:

• Transaction logs backup for Microsoft SQL Server, Oracle Database and PostgreSQL Instances — to back up
transaction logs from Microsoft SQL Server, Oracle server and PostgreSQL server.

• Transaction log truncation — to truncate transaction logs on the VM guest OS after the VM is successfully
processed.

• Pre-freeze and post-thaw scripts — to run pre-freeze and post-thaw scripts to quiesce VMs running
applications that do not support Microsoft VSS.

• VM guest OS files exclusion — to exclude or include individual files and folders from or to backup or
replica.

VM Guest File System Indexing


You can set up the backup job to create a catalog of files a nd folders on the VM guest OS. The catalog lets you
search for VM guest OS files and perform 1-click restore in Veeam Backup Enterprise Manager.

If you do not enable this option in the backup job settings, you will still be able to perform 1-click restore from
backups created by the backup job. For more information, see the Preparing for File Browsing and Searching
section in the Enterprise Manager User Guide.

NOTE

If you use Kerberos authentication, consider requirements and limitations described in section Kerberos
Authentication.

1247 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
Consider the following requirements and limitations for guest processing:

• Check that accounts that you plan to use for guest processing have permissions described in section
Permissions.

• [For Oracle databases except Oracle RAC] Check that databases that you want to back up are l isted in the
/etc/oratab file.

• To back up Microsoft SQL transaction logs with Veeam Backup & Replication, you must make sure that the
recovery model is set to Full or Bulk-logged recovery model for required databases on Microsoft SQL
Server VMs. If the recovery model is set to Simple, Veeam Backup & Replication will not detect and
process transaction logs on Microsoft SQL Server VMs.

• Veeam Backup & Replication excludes from application-aware processing Microsoft SQL databases that
are mounted to the Microsoft SQL Server using a remote UNC path. If at least one file of the database is
located on a network shared folder, this database will be backed up in the crash-consistent state. Other
databases on this server will be backed up in the transactionally consistent state. For more information,
see this Veeam KB article.

• Veeam Backup & Replication excludes the master database from guest p rocessing and does not process
transaction logs for it.

If you want to exclude other databases from the transaction log processing workflow, see this Veeam KB
article. Consider that exclusion configured this way will be treated as a global setting.

• Transaction log backups cannot be copied to capacity tier.

• To back up Oracle transaction logs with Veeam Backup & Replication, you must make sure that
ARCHIVELOG is turned on for required databases on Oracle VMs. If ARCHIVELOG is turned off,
Veeam Backup & Replication will not detect and process transaction logs on Oracle VMs.

• Due to Microsoft limitations, you cannot use Microsoft Entra ID (formerly Azure Active Directory)
credentials to perform guest processing on VMs running Microsoft Windows 10 (or later).

• Veeam Backup & Replication supports backup of Microsoft Exchange, SharePoint and SQL Server
databases existing in mount point volumes.

Non-Persistent Runtime Components and Persistent Agent


Components
To perform guest processing tasks, Veeam Backup & Replication must use special components when protecting
VMs. These components can be either non-persistent runtime components or persistent agent components:

• Non-Persistent Runtime Components

• Persistent Agent Components

Non-Persistent Runtime Components


Non-persistent runtime components help to avoid agent-related drawbacks such as pre-installing,
troubleshooting and updating. These components are deployed on every VM added to the job when the job
starts. As soon as the job finishes, the components are removed. This method is used for guest processing by
default.

1248 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To use non-persistent runtime components, do not select the Use persistent guest agent check box when
specifying application-aware processing settings as described in section Application-Aware Processing for VM
backup jobs. Veeam Backup & Replication performs processing of the backup jobs with enabled guest processing
according to the following algorithm.

NOTE

If the Use p ersistent guest agent option is disabled but persistent agent components were previously
installed on the VM, Veeam Backup & Replication may use them for guest processing. To use non-
persistent runtime components, uninstall persistent agent components from protected VMs.

Veeam Backup & Replication deploy the non-persistent runtime components on VMs in two ways:

• For VMs running Microsoft Windows, non-persistent runtime components are deployed using guest
interaction proxies. For more information, see Guest Interaction Proxy. If there are no guest interaction
proxies or guest interaction proxies fail for some reason, Veeam Backup & Replication will deploy non-
persistent runtime components on Microsoft Windows VMs from the backup server.

• For VMs running Linux or Unix operating systems, non-persistent runtime components are deployed from
the backup server.

When you start a job with guest processing tasks enabled, Veeam Backup & Replication performs the following
operations:

1. Veeam Backup & Replication defines the machines that will perform the guest interaction proxy role.

2. Veeam Backup & Replication deploys the non-persistent runtime components on VMs:

o [For Microsoft Windows VMs] The guest interaction proxy connects to VMs and deploys the non-
persistent runtime components on them.

o [For VMs running Linux or Unix] The backup server connects to VMs and deploys the non-persistent
runtime components on them.

1249 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. The job session proceeds as usual.

4. When the job session completes, Veeam Backup & Replication deletes the non-persistent runtime
components on VMs.

If a network connection breaks during the job session, Veeam Backup & Replication makes attempts to re-
establish the connection:

• If a network connection between the backup server/guest interaction proxy and VM guest OS breaks,
Veeam Backup & Replication makes one attempt to reconnect.

• If a network connection between the backup server and guest interaction proxy breaks,
Veeam Backup & Replication makes 10 attempts to reconnect.

If attempts are unsuccessful, guest processing tasks fail. The job proceeds with the scenario defined in the job
settings. For example, if you have instructed a backup job to try application processing but ignore failures,
Veeam Backup & Replication will not perform guest processing tasks but will proceed with the VM backup.

Persistent Agent Components


If you want to perform guest processing in a highly secure way, you can use persistent agent components (Guest
Helper, Log Shipping Service) on protected VMs. Persistent agent components require very limited and clearly
defined ports to communicate with Veeam Backup & Replication. For more information about ports, see Guest
Processing Components.

Prerequisites
To use persistent agent components, you must ensure that the Veeam Installer Service is installed on the guest
VM. For more information, see Veeam Installer Service.

Installing Persistent Agent Components on Microsoft


Windows VMs
For Microsoft Windows VMs, Veeam Backup & Replication deploys persistent agent components using guest
interaction proxies. For more information, see Guest Interaction Proxy. If there are no guest interaction proxies
or guest interaction proxies fail for some reason, Veeam Backup & Replication will deploy persistent agent
components on Microsoft Windows VMs from the backup server.

To use persistent agent components, select the Use persistent guest agent check box when specifying
application-aware processing settings as described in section Application-Aware Processing for VM backup jobs.
Persistent guest agents will be installed by the Installer Service during the first run of the ba ckup job.

1250 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When you select the Use persistent guest agent option, Veeam Backup & Replication performs processing of the
backup jobs with enabled guest processing according to the following algorithm. Persistent agent components
provide closing access to the VM administrative share (ADMIN$) and access to VM over PowerShell Direct.

When you start a job with guest processing tasks enabled, Veeam Backup & Replication performs the following
operations:

1. Veeam Backup & Replication defines the machines that will perform the guest interaction proxy role.

2. The guest interaction proxy connects to VMs and deploys persistent agent components on them.

NOTE

If the account used for guest processing is a local (non-domain) account, the connection may be
blocked by the remote UAC. This is a default security policy in Windows that prevents local user
accounts from being used to remotely connect to a server. In this case, either use the local
administrator account or disable the remote UAC to connect to the persistent agent. For more
information, see this Veeam KB article.

3. The job session proceeds as usual.

1251 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If a network connection breaks during the job session, Veeam Backup & Replication makes attempts to re-
establish the connection:

• If a network connection between the backup server/guest interaction proxy and VM guest OS breaks,
Veeam Backup & Replication makes one attempt to reconnect.

• If a network connection between the backup server and guest interaction proxy breaks,
Veeam Backup & Replication makes 10 attempts to reconnect.

If attempts are unsuccessful, guest processing tasks fail. The job proceeds with the scenario defined in the job
settings. For example, if you have instructed a backup job to try application processing but ignore failures,
Veeam Backup & Replication will not perform guest processing tasks but will proceed with the VM backup.

Installing Persistent Agent Components on Linux VMs


For VMs running Linux operating systems, persistent agent components are deployed manually from the backup
server using Management Agent. In this case, SSH credentials are used only once to deploy the Veeam Installer
Service that installs the Veeam Data Mover Service. These credentials are not stored in the backup
infrastructure. The Veeam Data Mover Service will be used to perform guest processing tasks without the SSH
connection.

NOTE

For more information about Linux operating systems supported by guest processing, see Platform Support.

To install Management Agent, perform the following steps:

1. Open the Inventory view. Select the VM and click Install Management Agent on the ribbon or right-click
the VM and select Install Management Agent.

1252 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. At the Credentials step of the wizard, specify credentials to connect to the VM and deploy Veeam Data
Mover. Specify a user account with root privileges or a non-root user with selected the E levate account
p rivileges automatically check box. If you did not add the user account to the sudoers file, select the Use
" su" if "sudo" fails check box and enter the password for the root account. For more information on these
check boxes, see Linux Accounts (User Name and Password).

3. Apply changes.

When you start a job with guest processing tasks enabled, Veeam Backup & Replication performs the following
operations:

1. The backup server connects to VMs using credentials specified in the backup job settings. For more
information, see Specify Guest Processing Settings.

2. The job session proceeds as usual.

If the transport service connection between the backup server and the VM guest OS fails,
Veeam Backup & Replication tries to use the SSH connection with credentials specified in the backup job
settings.

If all attempts are unsuccessful, guest processing tasks fail. The job proceeds with the scenario defined in the
job settings. For example, if you have instructed a backup job to try application processing but ignore failures,
Veeam Backup & Replication will not perform guest processing tasks but will proceed with the VM backup.

Application-Aware Processing
By default, Veeam Backup & Replication does not process application logs and creates a crash-consistent backup
of VMs with applications that use transaction logs for operations. You can create a transactionally consistent
backup - in this case Veeam Backup & Replication will process application logs. In case a disaster strikes,
Veeam Backup & Replication will use backups of logs to perform recovery operations.

To create transactionally consistent backups or replicas of VMs that run the following applications, you must
enable application-aware processing in job settings:

• Microsoft Active Directory

• Microsoft SQL Server

• Microsoft SharePoint

• Microsoft Exchange

1253 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Oracle

• PostgreSQL

Application-aware processing is the Veeam technology that allows Veeam Backup & Replication to stop
applications running on the VM and create a consistent view of application data on the VM guest OS. After the
application is stopped, Veeam Backup & Replication triggers the VM checkpoint and starts to copy VM data to
the target. Depending on the VM OS, Veeam Backup & Replication utilizes the following technologies to create
transactionally consistent backups:

• For Windows-based VMs, Veeam Backup & Replication uses Microsoft Volume Snapshot Service (Microsoft
VSS). Microsoft VSS ensures that there are no unfinished database transactions or incomplete application
files. For more information, see Microsoft Docs.

• For Linux-based VMs, Veeam Backup & Replication uses the agent that connects to the VM guest OS and
prepares databases and instances for a consistent backup.

Requirements and Limitations


Application-aware processing for Linux-based VMs and Microsoft Windows Server versions is supported by the
following versions of Microsoft Hyper-V (see Microsoft Docs). To use application-aware processing, you must
have Hyper-V Integration Services and the latest updates installed on the VM guest OS. For more information on
supported guest OS versions, see Supported Applications.

IMP ORTANT

If a VM runs an application that does not support Microsoft VSS (there is no VSS writer for this particular
type of application, for example, MySQL), Veeam Backup & Replication will not be able to utilize Microsoft
VSS and application-aware processing for this VM. To process such VMs, you can use Microsoft Hyper-V
guest quiescence with pre-freeze and post-thaw scripts. For more information, see Microsoft Hyper-V
Guest Quiescence and Pre-Freeze and Post-Thaw Scripts.

How Application-Aware Processing Works for Windows-Based


Machines
If you enable application-aware processing in job settings, Veeam Backup & Replication performs the following
operations as a part of the backup or replication process:

1. Veeam Backup & Replication deploys the non-persistent runtime components or, if necessary, persistent
agent components on the VM and detects if the VM runs any of the supported applications.

2. Veeam Backup & Replication collects information about applications installed on VMs — this information is
required for VSS-aware restore.

VSS-aware restore is performed when the VM is started after you restore it from the backup or fail over to
a VM replica.

3. Veeam Backup & Replication prepares applications for VSS-aware restore.

4. Microsoft VSS communicates with applications and quiesces I/O activities at a specific point in time.

5. Microsoft Hyper-V VSS requestor triggers a VM VSS snapshot.

6. Microsoft VSS resumes quiesced I/O activities on the VM guest OS.

7. Veeam Backup & Replication triggers a snapshot for the volume on which the VM is located.

1254 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
8. The job session proceeds as usual.

9. If you have instructed Veeam Backup & Replication to truncate transaction logs,
Veeam Backup & Replication truncates transaction logs on the VM guest OS after the backup or replica are
successfully created.

How Application-Aware Processing Works for PostgreSQL


If you enable application-aware processing in job settings, Veeam Backup & Replication performs the following
operations as a part of the backup or replication process

1. Veeam Backup & Replication installs either non-persistent components or persistent agent components to
the VM guest OS and detects if the VM runs any of the supported applications.

NOTE

By default, Veeam Backup & Replication installs non-persistent components to the VM guest OS, and
uninstalls them after the job completes. You can also install a Linux management agent to the VM
guest OS — in this case, the agent will remain installed on the VM and Veeam Backup & Replication
will use it to access the VM guest OS instead of SSH. For more information, see Persistent Agent
Components.

2. The pgsqlagent agent looks for PostgreSQL instance configuration files. It uses these files to get
information on the PostgreSQL instance settings.

1255 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

By default, configuration files are located in the following directories:

• [For Ubuntu, Debian] — /etc/


• [For RHEL, SLES] — /var/lib/

If you keep configuration file in the custom directories or if you want to exclude some directories
from scan, you can manually create the /etc/veeam/VeeamPostgreSQLAgent.xml file. In this
case, the pgsqlagent agent will use commands from this file. To explicitly include or exclude specific
configuration files from rescan, add the following commands to the
/etc/veeam/VeeamPostgreSQLAgent.xml file:

• ExcludeConfigDirs — use this command to exclude configuration files.


• AddConfigDirs — use this command to include configuration files.

Note that you must embed the commands into the <config /> tag. To specify several directories,
separate them by a comma.

For example: <config


ExcludeConfigDirs="/etc/postgresql/13/cl4/,/etc/postgresql/13/cl6/"
AddConfigDirs="/home/user/pgconfdir/"/>.

This command skips 2 directories and includes 1 custom directory.

3. The pgsqlagent agent returns a list of PostgreSQL configuration files to Veeam Backup & Replication.

4. Veeam Backup & Replication accesses the PostgreSQL VM guest OS over SSH or over management agent.

5. Veeam Backup & Replication connects to the PostgreSQL instance, gets a list of databases added to the
instance and information that is necessary for data recovery operations.

6. The pgsqlagent agent sets the PostgreSQL instance to the ready for a backup state.

7. Agent freezes the VM guest OS and creates a snapshot of the PostgreSQL instance.

8. Veeam Backup & Replication completes a backup of the PostgreSQL instance and resumes stopped
activities on the VM guest OS.

9. Veeam Backup & Replication saves a backup of a machine with a PostgreSQL instance to a backup
repository.

Pre-Freeze and Post-Thaw Scripts


If you back up or replicate VMs running applications that do not support Microsoft VSS, you can instruct
Veeam Backup & Replication to run custom scripts for VMs. For example, the pre-freeze script may quiesce the
file system and application data on the VM guest OS to bring the VM to a consistent state before
Veeam Backup & Replication triggers a VM checkpoint. After the checkpoint is created, the post-thaw script may
bring the VM and applications to their initial state.

You can use pre-freeze and post-thaw scripts for the following types of jobs:

• Backup job

• Replication job

Scripts must be created beforehand. You must specify paths to them in the job settings. Script execution
settings can be configured per VM or per container, depending on the objects included in the job.

1256 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When the job starts, Veeam Backup & Replication uploads scripts to the VM guest OS and executes them under
the account specified in the Guest OS credentials section of the job settings.

• Scripts for Microsoft Windows VMs are uploaded to \\<vmname>\admin$ over the network. Scripts are
executed from the C:\Windows directory. If the network connection fails, PowerShell Direct is used.
Scripts are uploaded to \\<hostname>\ADMIN$\<tempdir> and executed from the
C:\Windows\<tempdir> directory on the host.

PowerShell Direct is used for VMs that reside on Microsoft Hyper-V Server 2016 (or later) and run
Microsoft Windows 10 (or later) or Microsoft Windows Server 2016 (or later). Veeam Backup & Replication
requires Microsoft PowerShell 2.0 (or later) to work over PowerShell Direct.

• Scripts for Linux VMs are uploaded over SSH. Scripts are executed from the /tmp directory. If you use
Renci or Rebex SSH library, and the Elevate account privileges automatically check box is selected for the
user that you have specified in Guest OS credentials, the scripts will first be uploaded to the
/home/<username> and then moved to /tmp.

The script is considered to be executed successfully if "0" is returned.

The default time period for script execution is 10 minutes. If the script fails to execute before the timeout
expires, Veeam Backup & Replication displays an error message in the job session and error or warning messages
issued during script execution.

Supported Script Formats


Pre-freeze and post-thaw scripts can be used for Microsoft Windows and Linux VMs.

• For Microsoft Windows VMs, Veeam Backup & Replication supports scripts in the EXE, BAT, CMD, WSF, JS,
VBS and PS1 file format.

• For Linux VMs, Veeam Backup & Replication supports scripts in the SH file format.

Limitations for Pre-Freeze and Post-Thaw Scripts


Veeam Backup & Replication has the following limitations for pre-freeze and post-thaw scripts:

• You cannot stop a job when the pre-freeze or post-thaw script is executed. If the script hangs up,
Veeam Backup & Replication waits for 10 minutes and terminates the job.

1257 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you want to run several scripts that depend on each other, you must upload them to the VM guest OS
manually. For example, you have script1.bat that sequentially starts script2.bat, script3.bat and
script4.bat. In this case, you must specify a path to script1.bat in the job properties and upload script2.bat,
script3.bat and script4.bat to the VM guest OS.

• You must not use the standard error (STDERR) stream for error output in Linux scripts. Scripts with
STDERR cause failures in Veeam Backup & Replication.

Transaction Log Truncation


If you back up or replicate virtualized database systems that use transaction logs, for example, Microsoft
Exchange or Microsoft SQL Server, you can instruct Veeam Backup & Replication to truncate transaction logs so
that logs do not overflow the storage space on the VM. Veeam Backup & Replication provides the following
options of transaction logs handling:

• Truncate logs

• Do not truncate logs

• Back up logs periodically

Truncate Logs
You can instruct Veeam Backup & Replication to truncate logs after a backup or VM replica is successfully
created. With this option selected, Veeam Backup & Replication behaves in the following way:

• If the job completes successfully, Veeam Backup & Replication produces a backup file or VM replica and
truncates transaction logs on the original VM. As a result, you have the backup file or replica that contains
a VM image at a specific point in time.

In this scenario, you can recover a database to the point in time when the backup file or replica was
created. As transaction logs on the VM are truncated, you cannot use them to get the restored database to
some point in time between job sessions.

• If the backup or replication job fails, Veeam Backup & Replication does not truncate transaction logs on
the VM. In this scenario, you can restore a VM from the most recent backup or replica restore point and
use database system tools to apply transaction logs and get the database system to the necessary point in
time after the restore point.

1258 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Do not Truncate Logs
You can choose not to truncate transaction logs on the VM. This option is recommended if together with
Veeam Backup & Replication you use another backup tool.

For example, you can use Veeam Backup & Replication to create a VM image backup and instruct the native
Microsoft SQL Server log backup job to back up transaction logs. If you trunca te transaction logs with
Veeam Backup & Replication, the chain of transaction logs will be broken, and the Microsoft SQL Server log
backup job will not be able to produce a consistent log backup.

With this option selected, Veeam Backup & Replication produces a backup file or VM replica and does not trigger
transaction log truncation. As a result, you have a backup file or VM replica that contains a VM image captured
at a specific point in time, and transaction logs on the VM. You can use transaction logs to restore the VM to any
point in time between job sessions. To do this, you must recover the VM from the backup file or perform replica
failover and use database system tools to apply transaction logs and get the database system to the necessary
point in time.

Back Up Logs Periodically


This option can be used if you back up Microsoft SQL Server VMs and Oracle VMs.

You can choose to back up logs with Veeam Backup & Replication. For more information, see Microsoft SQL
Server Logs Backup and Oracle Logs Backup.

Support for Database Availability Groups (DAG)


Veeam Backup & Replication supports any configuration of DAGs, in particular, with all databases active on one
node, or with active databases on every node. Transaction logs will be truncated on all DAG members, no matter
whether Veeam Backup & Replication backs up an active or passive database.

For more information and recommendations on Microsoft Exchange Server backup, you can also refer to this
Veeam KB article.

Copy-Only Backup
Some organizations prefer to back up Microsoft SQL Server databases and transaction logs with native Microsoft
SQL Server tools or 3rd party backup tools. To restore database sy stems in a proper way, database
administrators must be sure that they have database backups and a sequence of transaction log backups
associated with these backups at hand.

If you use native Microsoft SQL Server tools or 3rd party backup tools and also want to back up Microsoft SQL
Server VMs with Veeam Backup & Replication, you must enable the P erform copy only option in the job settings.

The P erform copy only option indicates that a chain of database backups is created by native Microsoft SQL
Server means or by a 3rd party tool, and instructs Veeam to preserve this chain (backup history).
Veeam Backup & Replication backs up the Microsoft SQL Server VM using the VSS_BS_COPY method for snapshot
creation. The VSS_BT_COPY method produces a copy-only backup — the backup that is independent of the
existing chain of database backups and does not contain transaction logs data. As a result, the copy -only backup
does not change the log sequence number and transaction log backup time.

IMP ORTANT

Veeam Backup & Replication does not truncate transaction logs after copy-only backup. For this reason, if
you instruct the backup job to perform copy-only backup, you cannot specify transaction log handing
settings for this job.

1259 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
VM Guest OS File Indexing
You can instruct Veeam Backup & Replication to create an index of files and folders on the VM guest OS during
backup. VM guest OS file indexing allows you to search for VM guest OS files inside VM backups and perform 1-
click restore in Veeam Backup Enterprise Manager.

VM guest OS file indexing is enabled at the job level. You can specify granular indexing settings for every VM in
the job.

NOTE

VM guest OS file indexing is optional. If you do not enable this option in the backup job settings, you will
still be able to perform 1-click restore from the backup created by such backup job. For more information,
see the Preparing for File Browsing and Searching section in the Enterprise Manager User Guide.

Note, however, that if you do not enable indexing in the backup job, during 1-click restore from Linux and
other OS backups, Veeam Backup Enterprise Manager will not display symlinks to folders in the file system
browser.

1260 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for VM Guest OS File Indexing
Consider the following requirements for VM guest OS file indexing:

• Veeam Backup & Replication supports file indexing for VMs running Microsoft Windows and Linux OS.

• Linux VMs must have the following tools installed: openssh, gzip and tar.

Veeam Backup Catalog


For VM guest OS file indexing, Veeam Backup & Replication uses the Veeam Guest Catalog Service. In the
backup infrastructure, the Veeam Guest Catalog Service is installed on the Veeam backup server and Veeam
Backup Enterprise Manager server.

• The Veeam Guest Catalog Service on the Veeam backup server works as a local catalog service. It collects
indexing data for backup jobs and stores this data in the Veeam Backup Catalog folder.

By default, the indexing data is stored in the VBRCatalog folder on the backup server.
Veeam Backup & Replication creates the folder on a volume with the maximum amount of free space, for
example, C:\VBRCatalog.

• The Veeam Guest Catalog Service on Veeam Backup Enterprise Manager works as a global, federal catalog
service. It communicates with Veeam Guest Catalog Services on backup servers connected to Veeam
Backup Enterprise Manager and performs the following tasks:

o Replicates indexing data from backup servers to create a global catalog for the whole backup
infrastructure.

On the Veeam Backup Enterprise Manager server, the default folder for storing indexing data (the
VBRCatalog folder) is located on a volume with the maximum amount of free space.

o Maintains indexing data retention.

o Allows you to search for VM guest OS files in current and archived backup files.

How VM Guest OS File Indexing Works


When you run a backup job with the file indexing option enabled, Veeam Backup & Replication performs the
following operations:

1. When the backup job starts, Veeam Backup & Replication connects to the VM whose file system must be
indexed and deploys non-persistent runtime components or connects to (if necessary, deploys) persistent
agent components inside this VM. These components are responsible for coordinating indexing activities
inside the VM.

2. The non-persistent runtime components or persistent agent components start indexing the VM file
system. The indexing procedure is carried out in parallel with the backup procedure. If indexing takes long,
Veeam Backup & Replication will not wait for the indexing procedure to complete. It will start copying VM
data and continue file indexing inside the VM.

3. When file indexing is complete, the non-persistent runtime components or persistent agent components
collect indexing data and write it to the GuestIndexData.zip file. The GuestIndexData.zip file is
stored to a temporary folder on the backup server.

4. When the backup job completes, Veeam Backup & Replication notifies the local Veeam Guest Catalog
Service, and the service saves indexing data in the Veeam Catalog folder on the backup server.

1261 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. During the next catalog replication session, the global Veeam Guest Catalog Service replicates data from
the backup server to the Veeam Catalog folder on the Veeam Backup Enterprise Manager server.

1262 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft SQL Server Log Backup
To protect Microsoft SQL Server VMs, you can instruct the backup job to create image-level VM backups and
periodically back up database transaction logs. If Microsoft SQL Server fails, you can restore the Microsoft SQL
Server VM from the necessary restore point of the image-level backup. After that, you can use Veeam Explorer
for Microsoft SQL Server to apply transaction logs and get databases on the Microsoft SQL Server to the
necessary state between backups.

Transaction Log Backup Jobs


To back up transaction logs, you must create a backup job, add Microsoft SQL Server VMs to it and specify
advanced settings for transaction logs backup in the job settings. The resulting job will comprise two jobs:

• Parent backup job — the backup job that creates an image-level backup of the Microsoft SQL Server VM.
The parent backup job is named <job_name> , for example, DB Backup . You can configure the parent job in
the Veeam Backup & Replication console just like any other backup job.

• Child job — a transaction log backup job. To form a name of the child job, Veeam Backup & Replication
adds a suffix to the name of the parent backup job: <parent_job_name> + SQL Server Transaction Log
Backup , for example, DB Backup SQL Server Transaction Log Backup . Veeam Backup & Replication
automatically creates the child job if it detects a backup job that is scheduled to back up at least one
Microsoft SQL Server VM, and transaction log backup is enabled for this job. Session data of the
transaction log backup job is stored in the configuration database and displayed in the
Veeam Backup & Replication console.

The parent job runs in a regular manner — it starts by schedule or is started manually by the user. The
transaction log backup job is triggered by the parent backup job. This sequence ensures that the VM (and the
database) restore point is present when it comes to transaction log replay.

Sessions of Transaction Log Backup Jobs


The transaction log backup job runs permanently in the background, shipping transaction logs to the backup
repository at a specific time interval (by default, every 15 minutes). A sequence of time intervals between
sessions of the parent backup job makes up a session of the transaction log backup job.

The transaction log backup session starts and stops in the following way:

• The initial session starts when the parent backup job schedule is enabled. After that, the session starts
with every new session of the parent backup job.

• The session ends before the next session of the parent backup job or when this parent backup job is
disabled.

• When the session ends, Veeam Backup & Replication stops the non-persistent runtime components and
uninstalls them from the VM guest OS. When a new session starts, the runtime components are deployed
again.

How Microsoft SQL Server Log Backup Works


To perform transaction log backup, Veeam Backup & Replication installs the Veeam Guest SQL Log Shipper
runtime component on the VM guest OS.

This component runs during the transaction log backup job session and checks the following details:

• Collects information about databases that require transaction log backup.

1263 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Verifies that it is possible to ship logs directly to the backup repository. If it is not possible,
Veeam Backup & Replication uses the log shipping server.

When the transaction log backup job session ends, the component is stopped and removed from the VM guest
OS. When a new session starts, the component is installed on the VM guest OS again.

The transaction log backup is performed in the following way:

1. Veeam Backup & Replication launches the parent backup job by schedule.

2. The parent backup job creates an image-level backup of a Microsoft SQL Server VM and stores it in a
backup repository.

3. A new session of the transaction log backup starts. Veeam Backup & Replication accesses the VM (directly
or through the guest interaction proxy) and installs the runtime components for guest processing,
database information collection and transaction log handing on the VM guest OS.

4. Veeam Backup & Replication detects what databases currently exist on the Microsoft SQL Server and maps
this data with the information kept in the configuration database. This periodic mapping reveals the
databases for which Veeam Backup & Replication must process transaction logs during this time interval.

The runtime component backs up transaction log files and stores them as a *.bak file to a temporary folder
on the VM guest file system. For the information on the temporary folder location, see this Veeam KB
article.

5. Veeam Backup & Replication transports transaction log backup copies from the temporary folder on the
Microsoft SQL Server VM to the backup repository, either directly or through the log shipping server, and
saves them as VLB files. As soon as copies of transaction log backups are saved to the backup repository,
transaction log backups in the temporary folder on the Microsoft SQL Server VM are removed.

The session of the transaction log backup job remains working until the next start of the parent backup job.
When a new session of the parent job starts, the transaction log backup job stops the current session and then
starts a new session, performing steps 1-5.

Transaction logs that for some reason were not processed during the log backup interval remain in the
temporary folder and are processed during the next log backup interval. To detect these remaining logs,
Veeam Backup & Replication enumerates log files in the temporary folder.

NOTE

Backup of Windows Server Failover clusters is not supported, use Veeam Agent managed by
Veeam Backup & Replication instead. For more information, see Failover Cluster Support.

NOTE

If a new session of the transaction log backup starts and the parent backup job has not created a new
restore point yet, the transaction log backup job will remain in the idle state, waiting for a new restore
point to be created.

1264 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Retention for Transaction Log Backups
Transaction log backups are stored in files of the proprietary Veeam format — VLB. Veeam Backup & Replication
keeps transaction log backups together with the VM image-level backup. The target location of VLB files
depend on the type of the backup repository:

• If you store the VM image-level backup in a backup repository, Veeam Backup & Replication writes
transaction log backups to the same folder where files of the image-level backup reside.

• If you store the VM image-level backup in a scale-out backup repository, Veeam Backup & Replication
writes transaction log backups to the extent where the latest incremental backup file of the VM image -
level backup is stored.

Veeam Backup & Replication removes transaction log backups by retention. You can choose one of the following
retention methods:

• Retain logs according to the image-level backup

• Retain logs for the specified number of days

Retain Logs with Image-Level Backup


By default, Veeam Backup & Replication retains transaction log backups together with the image-level backup
of the Microsoft SQL Server VM. Veeam Backup & Replication retains VM backup and log backups according to
the short-term retention configured for VM backups. When Veeam Backup & Replication removes a restore point
of the image-level backup from the backup chain, it also removes a chain of transaction logs relating to this
image-level backup. Note that even if long-term retention is configured for the VM backup,
Veeam Backup & Replication retains transaction log backups according to the short-term retention policy and
deletes them after the short-term retention is exceeded.

1265 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
This method allows you to have both the image-level backup and necessary transaction log backups at hand. If
you need to recover a database to some state, you can restore the Microsoft SQL Database from the necessary
restore point and perform transaction log replay to bring the database to the desired state.

Retain Logs for a Number of Days


You can instruct Veeam Backup & Replication to keep transaction logs only for a specific period of time. This
retention setting can be used, for example, if you want to save on storage space and plan to retain transaction
log backups for the last few days. In this case, you will be able to restore the database only to one of the most
recent states.

If you select this retention method, you must make sure that retention p olicies for the image-level backup and
transaction log backup are consistent. The restore point of the image-level backup must always be preserved. If
a backup of the database itself is missing, you will not be able to perform transaction log replay.

Related Topics
Microsoft SQL Server Transaction Log Settings

Log Shipping Servers


For every Microsoft SQL Server VM whose transaction logs you want to back up, Veeam Backup & Replication
defines how to ship logs to the backup repository. Transaction logs can be shipped in the following ways:

• If it is possible to establish a direct connection between the VM guest OS and backup repository, log files
will be shipped directly from the VM guest OS to the backup repository. This is the optimal method, as it
does not involve additional resources and puts less load on the VM guest OS.

• Otherwise, files will be shipped through log shipping servers. You can instruct
Veeam Backup & Replication to choose a log shipping server automatically from the list of available ones,
or to use a specific server.

Note that if direct connection is possible, files will be always transferred from VM guest to repository
directly (regardless of the configured log shipping server, as this server will not be involved). This
approach helps to optimize performance at file transfer.

1266 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
A log shipping server is a Microsoft Windows server added to the backup infrastructure. You can explicitly define
what servers you want to use for log shipping or instruct Veeam Backup & Replication to automatically choose
an optimal log shipping server. Veeam Backup & Replication chooses the log shipping server based on two
criteria: possible data transfer methods and location of the Microsoft SQL Server VMs and log shipping server.

Data Transfer Methods


Log shipping servers can transport data in two ways:

• Over the network. In this scenario, Veeam Backup & Replication obtains files from the VM guest OS and
transfers them over the network.

To offload the VM guest OS, logs are created one by one (not simultaneously). One log creation request is
issued for every DB.

• Over PowerShell Direct. In this scenario, Veeam Backup & Replication obtains transaction logs from the
VM guest OS over PowerShell Direct, bypassing the network. PowerShell Direct is used for VMs that reside
on Microsoft Hyper-V Server 2016 (or later) and run Microsoft Windows 10 (or later) or Microsoft Windows
Server 2016 (or later). Veeam Backup & Replication requires Microsoft PowerShell 2.0 (or later) to work
over PowerShell Direct.

The default method is log shipping over the network.

Location of Log Shipping Server and VMs


When choosing a log shipping server for the job, Veeam Backup & Replication considers the location of the
Microsoft SQL Server VM and log shipping server. Veeam Backup & Replication uses the following priority rules
to select the log shipping server:

1. Log shipping server is located on the source Microsoft Hyper-V host performing the role of the on-host
backup proxy.

2. Log shipping server and Microsoft SQL Server VM are located in the same network.

3. Log shipping server and Microsoft SQL Server VM are located in different networks (the production
infrastructure is isolated from the backup infrastructure).

That is, when choosing a log shipping server, Veeam Backup & Replication will give the top priority to a
Microsoft Windows VM that is located on the source Microsoft Hyper-V host.

Log shipping servers are assigned per job session. When a new job session starts, Veeam Backup & Replication
detects log shipping servers anew. Veeam Backup & Replication can also re-detect available servers during the
job session. If a log shipping server becomes unavailable for some reason, Veeam Backup & Replication will fail
over to another log shipping server.

IMP ORTANT

If you do not want to use some servers for transaction logs transport, you can manually define what server
Veeam Backup & Replication must use as a log shipping server in the job settings. It is recommended that
you assign the log shipping server role to a number of servers for availability purposes.

1267 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Transaction Log Backup Statistics
You can view the statistics of the transaction log backup job in the History view or in the Home view in
Veeam Backup & Replication.

1268 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
In the statistics window, you can examine the overall statistics for the transaction log backup job, as well as
view per-VM information.

In the upper part of the statistics window, Veeam Backup & Replication displays information about the
transaction log backup job for all VMs included in the parent backup job.

The La st period (all VMs) section contains statistics data for the selected session of the backup job.

In the Da tabases column, you can view the following information:

• Protected — number of databases that were backed up at least once during the last session

• Unprotected — number of databases that failed to be backed up during the last session

• Excluded — databases excluded from processing. Databases may be excluded for the following reasons:

o The database status is Offline.

o The database recovery model is set to Simple.

o The database is read-only.

1269 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o The database was deleted after the latest full backup.

o The AutoClose property is enabled for the database.

o The database was excluded from application-aware processing. For details, see this Veeam KB article.

o The database was excluded from SQL log backup processing. For details, see this Veeam KB article.

o The database belongs to vCenter Server. For details, see this Veeam KB article.

NOTE

Unprotected databases do not comprise Excluded databases, as they have different reasons for being non-
processed.

In the RP O column, you can view the following information:

• SLA value — how many log backup intervals completed in time with successful log backup (calculated as
percentage of total number of intervals).

• Misses — how many intervals were missed (number of intervals).

• Max delay — difference between the configured log backup interval and time actually required for log
backup. If exceeded, a warning is issued.

In the Sta tus column, the following information is displayed (per job): number of VMs processed successfull y,
with warnings or with errors.

The La test session section displays the following information for the latest log processing interval for the
selected VM:

• Duration — duration of log shipment from the VM guest OS to the backup repository since the current log
processing interval has started

• Bottleneck — operation with the greatest duration in the last completed interval. The operation may have
the following bottlenecks:

Display Name Slowing-down Operation

Log backup Saving BAK files to a temporary location on VM guest OS

Network Uploading log files to the log shipping server

Ta rget Saving files to the target repository

• Read — amount of data read from the temporary folder on VM guest OS

• Transferred — amount of data transferred to the target repository

The La st period section displays the following statistics of log backups per VM for the latest session of the
transaction log backup job:

• The RP O column displays statistics on log processing interval

• The Sessions column includes statistics of log backups per VM, calculated based on their status:

o Success — number of intervals when all database logs were backed up successfully

1270 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Warning — number of sequential intervals with failed log processing (if not more than 4 intervals in a
sequence)

o Errors — number of sequential intervals with failed log processing (more than 4 intervals in a
sequence)

• The Duration column includes the following information:

o Average — average duration of log data transfer (through all intervals in the session)

o Max — maximal duration of log data transfer (through all intervals in the session)

o Sync interval — duration of periodic intervals specified for log backup in the parent job settings
(default is 15 min)

• The Log size column displays the following information:

o Average — average amount of data read from the VM guest OS through all intervals

o Max — maximal amount of data read from the VM guest OS over all 15-min intervals

o Total — total amount of data written to the backup repository

NOTE
• Statistics on transaction log processing is updated periodically, simultaneously for the parent
backup job and transaction log backup job.
• For Always On Availability groups, Veeam Backup & Replication collects logs only from one node.
Thus, in reports, the status of database replicas will be the same for all nodes (Protected or
Excluded).

Log Files
At each start of the SQL Server backup job (parent), a new .VLB is created to store log backups in the repository:

• If the Use p er-machine backup files option is selected for the repository, then Veeam Backup & Replication
will create a separate .VLB for each server processed by the job.

• If this option is cleared, then a single .VLB will be created for all servers processed by the job.

For example, if a job processes only one SQL Server, the repository will contain a number of .VLB files for it (a
so-called chain).

1271 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
As described in the section above, during database log backup (child) job session, transaction log backup is
performed by native means of the SQL Server and stored as .BAK file to a temporary folder in the SQL Server VM
guest file system. Then Veeam Backup & Replication copies .BAK file to the current .VLB in the repository. When
the new parent job session starts, another .VLB is created, and the .BAK files that appear after that will be
stored there during the child job session. The resulting chain of .VLBs will look like shown below, depicted for a
single SQL Server VM1:

Total number of all LOG<N>.BAK files stored at the moment in all VLBs is reported as a numb er of restore
p oints for the child job that backs up database logs. So, in the example above, the log backup job for SQL Server
VM1 has created 8 restore points by the moment.

In the Veeam Backup & Replication console this number of restore points for the log backup job can be seen in
the Restore Points column of the preview pane.

Support for Always On Availability Groups


Always On Availability Groups allow you to increase fault tolerance between active and hot-standby databases
without involving shared physical disks, which is quite important for virtualization of Microsoft SQL Servers.
Veeam Backup & Replication supports Always On Availability Groups for virtualized Microsoft SQL Server 2012
or later.

Veeam Backup & Replication supports the following Always On Availability Groups:

• Always On Availability Groups based on Windows Server Failover Cluster.

• Always On Clusterless Availability Groups.

Veeam Backup & Replication does not support Always On Availability Groups based on SQL Server Failover
Cluster Instances.

Image-level Backup of Microsoft SQL Server VMs


During an image-level backup of a Microsoft SQL Server VM, Veeam Backup & Replication requests and analyzes
information about databases that are included in the Always On Availability Groups. Depending on the retrieved
information, Veeam Backup & Replication creates a VSS snapshot with or without COPY_ONLY flag. The
VSS_BS_COPY flag for VSS snapshot is triggered if the VM represents a secondary node for at least one Always
On Availability Group.

Veeam Backup & Replication also detects to what cluster the database belongs. If the backup job does not
include all VMs from the cluster, an information message will be issued.

Retrieved information is saved for further log identification.

1272 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Transaction Log Backup
Transaction log backup can be performed only for those databases that were successfully backed up, either on
the primary or on the secondary node of Always On Availability Group.

The transaction logs processing interval may be the same or may differ through VMs included in Always On
Availability Group. If the interval is different, Veeam Backup & Replication will use minimal value (by default, 15
minutes).

At each log processing interval, Veeam Backup & Replication chooses the Always On Availability Group node for
which transaction logs will be backed up.

Logs are backed up from one node of the Always On Availability Group. To become a subject for a log backup,
the node must meet the following criteria:

• The necessary Veeam Backup & Replication components must be installed on this node and the VM
included in Always On Availability Group must be running. For more information on the necessary
components, see How Microsoft SQL Server Log Backup Works.

• The database backup preferences settings must allow a backup of the node that you want to process. For
example, if you want to back up the primary node, you must not exclude this node from a backup, or
select the Secondary only option in the database backup preferences settings.

• Databases in the Always On Availability Groups for this node were successfully backed up for the last two
processing intervals.

• Veeam Backup & Replication can establish a network connection to the node or PowerShell Direct
connection, if a connection over the network cannot be established. PowerShell Direct is used for VMs
that reside on Microsoft Hyper-V Server 2016 (or later) and run Microsoft Windows 10 (or later) or
Microsoft Windows Server 2016 (or later). Veeam Backup & Replication requires Microsoft PowerShell 2.0
(or later) to work over PowerShell Direct.

NOTE

When you configure a backup job to process Distributed Availability Groups transaction logs, select either
primary or secondary distributed availability group. Otherwise, the log chain of the distributed group
databases may become inconsistent.

When you configure a backup job to back up transaction logs for other Distributed Availability Groups, use
the Perform copy only mode. See Application-Aware Processing to learn more about the copy only mode.
You can also use the exclude feature to prevent Guest-OS database from being processed. See Exclude
Objects from Backup Job to learn more on excluding objects. To read about distributed availability group
limitations, see Configure distributed availability group.

1273 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Oracle Log Backup
Veeam Backup & Replication supports backup of Oracle database archived logs and restore of Oracle databases.

Database archived logs are created by the Oracle system. The Oracle database can run in one of the following
logging modes:

• ARCHIVELOG — logs are saved and can be used for recovery purposes.

• NOARCHIVELOG — no logs are saved. This mode is not recommended as it does not provide proper
disaster recovery.

With ARCHIVELOG mode enabled, the Oracle system stores database archived logs to a certain location on the
VM guest OS, as specified by the database administrator. Veeam Backup & Replication allows you to set up the
following ways of log handling:

• Instruct the backup job to collect log files from the Oracle VM and ship them to the backup repository
where they are stored next to image-level backups of the Oracle VM.

• Skip log processing — log files remain untouched on the Oracle VM and are preserved within the image -
level backup.

If you enable application-aware processing for an Oracle VM, during the job session Veeam Backup & Replication
installs non-persistent runtime components or uses (if necessary, installs) persistent agent components on this
VM to collect information about the database and process archived logs according to job settings. Application-
specific settings are configured at the Guest Processing step of the backup job wizard — you can specify how
logs should be backed up and\or deleted for Oracle databases.

Requirements for Archived Log Backup


• Veeam Backup & Replication supports archived log backup and restore for Oracle Database version 11 and
later. Oracle Database may run on a Microsoft Windows VM or Linux VM.

• Automatic Storage Management (ASM) is supported for Oracle Database 11 and later.

• Oracle Database Express Edition (XE) are supported if running on Microsoft Windows machines only.

Archived Log Backup Jobs


To back up archived logs, you must create a backup job, add Oracle VMs to it and specify advanced settings f or
archived logs backup in the job settings. The resulting job will comprise two jobs:

• Parent backup job — the backup job that creates an image-level backup of the Oracle VM. The parent
backup job is named <job_name>, for example, Daily Job. You can configure the parent job in the
Veeam Backup & Replication console just like any other backup job.

• Child job — an archived log backup job. To form a name of the child job, Veeam Backup & Replication adds
a suffix to the name of the parent backup job: <parent_job_name> + Oracle Redo Log Backup , for example,
Daily Job Oracle Redo Log Backup . Veeam Backup & Replication automatically creates the child job if it
detects a backup job that is scheduled to back up at least one Oracle VM, and archived log backup is
enabled for this job. Session data of the archived log backup job is stored in the configuration database
and displayed in the Veeam Backup & Replication console.

The parent job runs in a regular manner — it starts by schedule or is started manually by the user. The archived
log backup job is triggered by the parent backup job. This sequence ensures that the VM (and the database)
restore point is present when you need to use archived logs to restore the database.

1274 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Sessions of Archived Log Backup Jobs
The archived log backup job runs permanently in the background, shipping archived logs to the backup
repository at a specific time interval (by default, every 15 minutes). A sequence of time intervals between
sessions of the parent backup job makes up a session of the archived log backup job.

The archived log backup session starts and stops in the following way:

• The initial session starts when the parent backup job schedule is enabled. After that, the session starts
with every new session of the parent backup job.

• The session ends before the next session of the parent backup job or when this parent backup job is
disabled.

• When the session ends, Veeam Backup & Replication stops the non-persistent runtime components and
uninstalls them from the VM guest OS. When a new session starts, the runtime components are deployed
again.

How Oracle Archived Log Backup Works


The archived log backup for Oracle VMs is performed in the following way:

1. Veeam Backup & Replication launches the parent backup job by schedule.

2. The parent backup job creates an image-level backup of the Oracle VM and stores this backup to the
backup repository.

3. A new session of the archived log backup starts. Veeam Backup & Replication accesses the VM guest OS to
perform guest processing, collect database information and handle archived log.

If Oracle runs on a Microsoft Windows server, Veeam Backup & Replication accesses the VM guest OS over
a guest interaction proxy. You can instruct Veeam Backup & Replication to select the guest interaction
proxy automatically or assign it explicitly.

By default, Veeam Backup & Replication accesses the VM guest OS over the network:

o For Linux VM guest OS — using SSH.

o For Microsoft Windows VM guest OS — using RPC.

If a network connection cannot be established, Veeam Backup & Replication accesses the VM guest OS
over PowerShell Direct. PowerShell Direct is used for VMs that reside on Microsoft Hyper -V Server 2016
(or later) and run Microsoft Windows 10 (or later) or Microsoft Windows Server 2016 (or later).
Veeam Backup & Replication requires Microsoft PowerShell 2.0 (or later) to work over PowerShell Direct.

4. Veeam Backup & Replication deploys the non-persistent runtime components or uses (if necessary,
deploys) persistent agent components in the VM guest OS. The components scan the Oracle system and
collect information about databases whose logs must be processed, including:

o List of all databases

o Database state — a database is on or off, in which logging mode it runs

o Paths to all database files (configuration logs and so on) and other data required for backup

Veeam Backup & Replication also detects whether it is possible to store logs to the backup repository
through a direct access or a log shipping server is required.

1275 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The non-persistent runtime components or persistent agent components copy archived log files from the
log archive destination (set by the Oracle administrator) to a temporary folder on the VM guest file
system.

5. Veeam Backup & Replication maps information about the Oracle system collected at step 4 with
information kept in the configuration database. This periodic mapping helps reveal databases for which
Veeam Backup & Replication must ship archived logs to the backup repository during this time interval.

6. Veeam Backup & Replication transfers archived log backup files from the temporary location on the Oracle
VM to the backup repository and saves them as VLB files. Veeam Backup & Replication transfers logs
either directly or through the log shipping server. The source-side Veeam Data Mover compresses log data
to be transferred according to its built-in settings. On the backup repository side, data is compressed
according to the parent backup job settings.

Archived logs that for some reason were not processed during the log backup interval remain in the temporary
folder and are processed during the next log backup interval. To detect these remaining logs,
Veeam Backup & Replication enumerates log files in the temporary folder.

NOTE

If a new session of the archived log backup starts and the parent backup job has not created a new restore
point yet, the archived log backup job will remain in the idle state, waiting for a new restore point to be
created.

IMP ORTANT

Before backup, Veeam Backup & Replication shuts down databases in the NOARCHIVELOG mode. For
details, see the Backing Up a Database in NOARCHIVELOG Mode section in the Oracle Database Backup and
Recovery User Guide.

Retention for Archived Log Backup


Archived log backups are stored in files of the proprietary Veeam format — VLB. Veeam Backup & Replication
keeps archived log backups together with the VM imag e-level backup. The target location of VLB files depend
on the type of the backup repository:

• If you store the VM image-level backup in a backup repository, Veeam Backup & Replication writes
archived log backups to the same folder where files of the imag e-level backup reside.

1276 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you store the VM image-level backup in a scale-out backup repository, Veeam Backup & Replication
writes archived log backups to the extent where the latest incremental backup file of the VM image -level
backup is stored.

Veeam Backup & Replication removes archived log backups by retention. You can choose one of the following
retention methods:

• Retain logs according to the image-level backup

• Retain logs for the specified number of days

Retain Logs with Image-Level Backup


By default, Veeam Backup & Replication retains archived log backups together with the related image-level
backup of the Oracle VM. Veeam Backup & Replication retains VM backup and log backups according to the
short-term retention configured for VM backups. When Veeam Backup & Replication removes a restore point of
the image-level backup from the backup chain, it also removes a chain of archived logs relating to this image-
level backup. Note that even if long-term retention is configured for the VM backup,
Veeam Backup & Replication retains archived log backups according to the short-term retention policy and
deletes them after the short-term retention is exceeded.

This method allows you to have both the image-level backup and necessary archived log backups at hand. If you
need to recover a database to some state, you can restore the Oracle VM from the necessary restore point and
use archived logs to bring the database to the desired state.

Retain Logs for a Number of Days


You can instruct Veeam Backup & Replication to keep archived logs only for a specific period of time. This
retention setting can be used, for example, if you want to save on storage space and plan to retain archived log
backups for the last few days. In this case, you will be able to restore the database only to one of the most
recent states.

If you select this retention method, you must make sure that retention policies for the image -level backup and
archived log backup are consistent. The restore point of the image-level backup must always be preserved. If a
backup of the database itself is missing, you will not be able to use archived logs.

1277 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Log Shipping Servers
For every Oracle VM whose archived logs you want to back up, Veeam Backup & Replication defines how to ship
logs to the backup repository. Archived logs can be transported in the following ways:

• Directly from the VM guest OS to the backup repository. This method is recommended — it does not
involve additional resources and puts less load on the VM guest OS.

• Via log shipping servers. If it is not possible to establish a direct connection between the VM guest OS and
backup repository, you can configure Veeam Backup & Replication to use a log shipping server.

A log shipping server is a Microsoft Windows server added to the backup infrastructure. You can explicitly define
what servers you want to use for log shipping or instruct Veeam Backup & Replication to automatically choose
an optimal log shipping server. Veeam Backup & Replication chooses the log shipping server based on two
criteria: possible data transfer methods and location of the Oracle VM and log shipping server.

Data Transfer Methods


Log shipping servers can transport data in two ways:

• Over the network. In this scenario, Veeam Backup & Replication obtains files from the VM guest OS and
transfers them over the network.

• Over PowerShell Direct. In this scenario, Veeam Backup & Replication obtains archived logs from the VM
guest OS over PowerShell Direct, bypassing the network. PowerShell Direct is used for VMs that reside on
Microsoft Hyper-V Server 2016 (or later) and run Microsoft Windows 10 (or later) or Microsoft Windows
Server 2016 (or later). Veeam Backup & Replication requires Microsoft PowerShell 2.0 (or later) to work
over PowerShell Direct.

The default method is log shipping over the network.

Location of Log Shipping Server and VMs


When choosing a log shipping server for the job, Veeam Backup & Replication considers the location of the
Oracle VM and log shipping server. Veeam Backup & Replication uses the following priority rules to select the
log shipping server:

1. Log shipping server is located on the source Microsoft Hyper-V host performing the role of the on-host
backup proxy.

2. Log shipping server and Oracle VM are located in the same network.

3. Log shipping server and Oracle VM are located in different networks (the production infrastructure is
isolated from the backup infrastructure).

That is, when choosing a log shipping server, Veeam Backup & Replication will give the top priority to a VM that
is located on the source Microsoft Hyper-V host.

Log shipping servers are assigned per job session. When a new job session starts, Veeam Backup & Replication
detects log shipping servers anew. Veeam Backup & Replication can also re-detect available servers during the
job session. If a log shipping server becomes unavailable for some reason, Veeam Backup & Replication will fail
over to another log shipping server.

1278 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

If you do not want to use some servers for archived logs transport, you can manually define what server
Veeam Backup & Replication must use as a log shipping server in the job settings. It is recommended that
you assign the log shipping server role to a number of servers for availability purposes.

Archived Log Backup Statistics


You can view the statistics of the archived log backup job in the History view or in the Home view
in Veeam Backup & Replication.

1279 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
In the statistics window, you can examine the overall statistics for the archived log backup job, as well as view
per-VM information.

In the upper part of the statistics window, Veeam Backup & Replication displays information about the log
backup job for all VMs included in the parent backup job.

The La st period (all VMs) section contains statistics data for the selected session of the backup job.

In the Da tabases column, you can view the following information:

• Protected — number of databases that were backed up at least once during the last session.

• Unprotected — number of databases that failed to be backed up during the last session.

• Excluded — databases excluded from processing. Databases may be excluded for the following reasons:
ARCHIVELOG mode is turned off for the database (the database is in NOARCHIVELOG mode), database
was deleted after the latest full backup, or database was added to the list of exclusions.

1280 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Unprotected databases do not comprise E x cluded databases, as they have different reasons for being non-
processed. See also this Veeam KB article for information on processing databases in NOARCHIVE mode.

In the RP O column, you can view the following information:

• SLA — how many log backup intervals completed in time with successful log backup (calculated as
percentage of total number of intervals).

• Misses — how many intervals failed to complete in time with successful log backup (number of intervals).

• Max delay — difference between the configured log backup interval and time actually required for log
backup. If exceeded, a warning is issued.

In the Sta tus column, the following information is displayed (per job): number of VMs processed successfully,
with warnings or with errors.

The La test session section displays the following information for the latest log processing interval for the
selected VM:

• Duration — duration of log shipment from the VM guest OS to the backup repository since the current log
processing interval has started.

• Bottleneck — operation with the greatest duration in the last completed interval. The operation may have
the following bottlenecks:

Display Name Slowing-down Operation

Log backup Saving archived log files to a temporary location on VM guest OS (to work around, see
the Veeam KB article: this Veeam KB article)

Network Uploading log files to the log shipping server

Target Saving files to the target repository

• Read — amount of data read from the temporary folder on VM guest OS

• Transferred — amount of data transferred to the target repository


The La st period section displays the following statistics of log backups per VM for the latest session of the log
backup job:

• The RP O column displays statistics on log processing interval.

• The Sessions column includes statistics of log backups per VM, calculated based on their status:

o Success — number of intervals when all database logs were backed up successfully

o Warning — number of sequential intervals with failed log processing (if not more than 4 intervals in a
sequence)

o Errors — number of sequential intervals with failed log processing (more than 4 intervals in a
sequence)

1281 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• The Duration column includes the following information:

o Average — average duration of log data transfer (through all intervals in the session)

o Maximum — maximal duration of log data transfer (through all intervals in the session)

o Sync interval — duration of periodic intervals specified for log backup in the parent job settings
(default is 15 min)

• The Log size column displays the following information:

o Average — average amount of data read from the VM guest OS through all intervals

o Maximum — maximal amount of data read from the VM guest OS over all 15-min intervals

o Total — total amount of data written to the backup repository

The pane at the bottom shows all actions performed during the job run. To filter out actions with the certain
status, use the E rrors, Warnings and Success buttons.

NOTE

Statistics on archived log processing is updated periodically, simultaneously for the VM backup job (parent)
and archived log backup job (child job).

Log Files
At each start of the Oracle backup job ('parent'), a new .VLB is created to store log backups in the repository:

• If the Use p er-machine backup files option is selected for the repository, then Veeam will create a
separate .VLB for each server processed by the job.

• If this option is cleared, then a single .VLB will be created for all servers processed by the job.

For example, if a job processes only one Oracle server, the repository will contain a number of .VLB files for it (a
so-called chain).

As described in the section above, during database log backup ('child') job session, log archiving is performed by
native means of the Oracle server. Archived logs are stored to a temporary folder on the Oracle VM guest file
system. Then Veeam copies archived log to the current .VLB in the repository. When the new 'parent' job session
starts, another .VLB is created, and the archived log files tha t appear after that will be stored there during the
'child' job session. The resulting chain of .VLBs will look like shown below, depicted for a single Oracle VM1:

Total number of all archived logs files stored at the moment in all VLBs is reported as a numb er of restore points
for the 'child' job that backs up database logs. So, in the example above, the log backup job for Oracle VM1 has
created 8 restore points by the moment.

1282 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
PostgreSQL WAL Files Backup
To protect VMs with PostgreSQL instances, you can instruct the backup job to create image-level VM backups
and periodically back up write ahead log (WAL) files of PostgreSQL instances. Thus, you will create a
transactionally consistent backups of PostgreSQL instances that will contain backups of WAL files . If a
PostgreSQL instance fails, you can use Veeam Explorer for PostgreSQL to apply WAL files and recover
PostgreSQL instances to the necessary state.

Requirements and Limitations


Before you back up WAL files for PostgreSQL instances, consider the following requirements and limitations:

• Veeam Backup & Replication supports log backup and restore for PostgreSQL version 12, 13, 14, 15, 16
(PostgreSQL version 12, 13, 14, 15 - for version 12).

• Veeam Backup & Replication supports only backup of PostgreSQL instances configured on Linux -based
VMs.

• Veeam Backup & Replication does not support backup of PostgreSQL clusters.

• Veeam Backup & Replication does not support backup of individual PostgreSQL databases.

• Veeam Backup & Replication does not support high availability cluster configurations and replication
setups of PostgreSQL servers.

• Set the archive_mode parameter to the on mode in PostgreSQL instances.

• The archive_command parameter must not contain any values in PostgreSQL instances.

• Set the wal_level parameter to replica or logical in PostgreSQL instances.

• The temporary folder that keeps logs must have enough space and be accessible from Linux guest OS.

• To perform guest processing for PostgreSQL instances on Linux servers, make sure that the /tmp directory
is mounted with the exec option. Otherwise, you will get an error with the permission denial.

Related Topics
• WAL Files PostgreSQL Backup Jobs

• How PostgreSQL WAL Files Backup Works

• Retention for PostgreSQL WAL Files

• Log Shipping Servers

• WAL Files Backup Statistics

• Creating Backup Jobs

WAL Files PostgreSQL Backup Jobs


To maintain data consistency and integrity, Veeam Backup & Replication makes a backup of write ahead log
(WAL) files for PostrgreSQL instances. Veeam Backup & Replication uses these log files to recover PostrgreSQL
instances and bring it to the necessary consistent state.

1283 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To back up WAL files, you must create a backup job, add PostrgreSQL VM to it and specify advanced settings for
WAL files in the job settings. The resulting job will consist of two jobs:

• Parent backup job — the job that creates an image-level backup of PostrgreSQL VMs. You specify a parent
backup job name when you define settings for a backup job, for example, Daily DB Job . For more
information. see Step 2. Specify Job Name and Description. For more information on how image-level
backup of PostrgreSQL VMs works, see Application-Aware Processing.

• Child job — the job that creates a backup of WAL files. To form a name of the child job,
Veeam Backup & Replication adds a suffix to the name of the parent backup job: <parent_job_name> +
PostrgreSQL Log Backup , for example, Daily Job PostrgreSQL Log Backup . When
Veeam Backup & Replication detects a backup job that contains at least one PostrgreSQL VM, it
automatically creates the child job to back up WAL files. Veeam Backup & Replication keeps session data
of the child job in the configuration database and displays it in the console. For more information on how
the job creates a backup of WAL files, see How PostgreSQL WAL Files Backup Works.

The parent job runs in a regular manner — it starts by schedule or is started manually by the user. The child job is
triggered by the parent backup job. This sequence ensures that the VM (and the instances) restore point is
present when you need to use WAL files to restore the database.

Sessions of Archived Log Backup Jobs


The child backup job runs permanently in the background, shipping WAL files to the backup repository at a
specific time interval (by default, every 15 minutes). A sequence of time intervals between sessions of the
parent backup job makes up a session of the child backup job.

The child backup session starts and stops in the following way:

• The initial session starts when the parent backup job schedule is enabled. After that, the session starts
with every new session of the parent backup job.

• The session ends before the next session of the parent backup job or when this parent backup job is
disabled.

• When the session ends, Veeam Backup & Replication stops the non-persistent runtime components and
uninstalls them from the VM guest OS. When a new session starts, the runtime components are deployed
again.

How PostgreSQL WAL Files Backup Works


To maintain integrity and data consistency, Veeam Backup & Replication makes a backup of write ahead log
(WAL) files that contain PostgreSQL instance logs. Veeam Backup & Replication uses these log files for instance
recovery operations.

To back up WAL files, you must enable application-aware processing for PostgreSQL VMs. After this, during the
job session Veeam Backup & Replication installs non-persistent runtime components or uses (if necessary,
installs) persistent agent components on this VM to collect information about the instance and process WAL
files according to job settings. For more information on how to configure application-specific settings for
PostgreSQL WAL files backup, see PostgreSQL WAL Settings step of the backup job wizard — you can specify
how logs should be backed up and\or deleted for PostgreSQL instances.

The WAL files backup for PostgreSQL VMs is performed in the following way:

1. Veeam Backup & Replication launches the parent backup job by schedule.

2. The parent backup job creates an image-level backup of the PostgreSQL VM and stores this backup to the
backup repository.

1284 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. A child job starts to back up WALs: Veeam Backup & Replication accesses the PostgreSQL VM guest OS
over SSH. By default, Veeam Backup & Replication installs non-persistent components to the VM guest
OS, and Veeam Backup & Replication will uninstall them after the job completes. You can also install a
Linux management agent to the VM guest OS — in this case, the agent will remain installed on the VM and
Veeam Backup & Replication will use it to access the VM guest OS. For more information, see Persistent
Agent Components.

4. Veeam Backup & Replication scans the PostgreSQL system and gets information that is necessary to back
up backup and restore a PostgreSQL instance.

o List of all databases added to the instance.

o The instance state — if the instance is on or off, in which logging mode it runs.

o Paths to all Instance files (configuration logs and so on) and other da ta required for backup.

4. The non-persistent runtime components or persistent agent components copy WALs from the log archive
destination (set in guest processing settings of a job) to a temporary directory on the VM guest file
system.

5. Veeam Backup & Replication maps information about the PostgreSQL system collected at the step 4 with
information kept in the configuration database. This periodic mapping helps to reveal instances for which
Veeam Backup & Replication must ship WALs to the backup repository during this time interval.

6. Veeam Backup & Replication transfers WALs from the temporary location on the PostgreSQL VM to the
backup repository and saves them as VLB files. Veeam Backup & Replication transfers WALs either directly
or through the log shipping server. The source-side Veeam Data Mover compresses log data to be
transferred according to its built-in settings. On the backup repository side, data is compressed according
to the parent backup job settings.

7. Veeam Backup & Replication deletes WALs from the temporary directory on the VM guest file system.

IMP ORTANT

Consider the following:

• Veeam Backup & Replication removes from a temporary folder only backed -up WALs. The
WALs that were not backed up during the log backup interval remain in the temporary folder.
Veeam Backup & Replication will process these logs during the next log backup interval.
• If a new session of the WALs backup starts and the parent backup job has not created a new
restore point yet, the WALs backup job will remain in the idle state, waiting for a new restore
point to be created.

Retention for PostgreSQL WAL Files


Veeam Backup & Replication stores WAL files in the proprietary Veeam format — .VLB and keep them together
with the VM image-level backup. For more information on the backup files, see Backup Chain.

The target location where Veeam Backup & Replication keeps .VLB files depends on the type of repository
where you store VM image-level backup files:

• If it is the backup repository, Veeam Backup & Replication writes WAL files to the same folder where the
VM image-level backup files reside.

• If it is the scale-out backup repository, Veeam Backup & Replication writes WAL files to the extent where
the latest incremental backup file of the VM image-level backup resides.

Note that Veeam Backup & Replication does not store .VLB files in capacity or archive extents added to
the scale-out backup repository.

1285 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication removes WAL files by retention. You can choose one of the following retention
methods:

• Retain WAL files according to the image-level backup

• Retain WAL files for the specified number of days

Retain Logs with Image-Level Backup


By default, Veeam Backup & Replication retains WAL files together with image-level backup of a PostgreSQL
VM. Veeam Backup & Replication retains VM backup and log backups according to the short-term retention
configured for VM backups. When Veeam Backup & Replication removes a restore point of the image-level
backup from a backup chain, it also removes a chain of WAL files that relates to this image-level backup.

NOTE

If you configure a long-term retention, Veeam Backup & Replication will retains WAL files according to the
short-term retention policy and will delete them after the short-term retention is exceeded.

This method allows you to have both the image-level backup and necessary WAL files at hand. If you need to
recover a PostgreSQL instance to a specific state, you can restore the PostgreSQL VM from the necessary restore
point and use WAL files to bring the database to the necessary state.

Retain WAL Files for a Number of Days


You can instruct Veeam Backup & Replication to keep WAL files only for a specific period of time. You can use
this option, if you want to save storage space and plan to retain WAL files for the last few days. In this case, you
will be able to restore a PostgreSQL instance only to one of the most recent states.

If you select this retention method, you must make sure that retention policies for the ima ge-level backup and
archived log backup are consistent. The restore point of the image-level backup must always be preserved. If a
backup of the PostgreSQL instance itself is missing, you will not be able to use WAL files for recovery.

1286 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
WAL Files
At each start of the parent PostgreSQL backup job, Veeam Backup & Replication creates a new .VLB to store log
backups in the repository:

• If you select the Use p er-machine backup files option for the repository, Veeam Backup & Replication will
create a separate .VLB for each server processed by the job.

• If you do not use the Use per-machine backup files option, Veeam Backup & Replication will create a
single .VLB for all servers processed by the job.

For example, if a job processes only one PostgreSQL server, the repository will contain a number of .VLB files for
it (a so-called chain).

Veeam Backup & Replication comprises native means of the PostgreSQL server to archive WAL files. During the
WAL files backup job, PostgreSQL server stores the files in a temporary folder on the PostgreSQL VM guest file
system. After the parent backup job completes, Veeam Backup & Replication copies WAL files to .VLB and stores
them in a backup repository. When a new WAL files job session starts, PostgreSQL server creates new WAL files
and keep them in the temporary folder. As a result, for a single PostgreSQL VM the job creates a chain of .VLBs
that are located in a backup repository together with .VBK and .VIB files. A total number of all WAL files stored
in .VLB sets a number of restore points. A single .VLB file can have several WAL files, and, therefore, several
restore points. For example. 1 .VLB can have 10 restore points.

Log Shipping Servers


For every PostgreSQL VM whose WAL files you want to back up, Veeam Backup & Replication defines how to
ship logs to the backup repository. WAL files can be tra nsported in the following ways:

• Directly from the VM guest OS to the backup repository. This method is recommended — it does not
involve additional resources and puts less load on the VM guest OS.

• Via log shipping servers. If it is not possible to establish a direct connection between the VM guest OS and
backup repository, you can configure Veeam Backup & Replication to use a log shipping server.

A log shipping server is a Linux server added to the backup infrastructure. You can explicitly define what servers
you want to use for log shipping or instruct Veeam Backup & Replication to automatically choose an optimal log
shipping server. Depending on the possible data transfer methods and location of the PostgreSQL VM and the
log shipping server, Veeam Backup & Replication chooses the log shipping server.

Data Transfer Methods


Log shipping servers can transport data in two ways:

• Over the network. In this scenario, Veeam Backup & Replication obtains files from the VM guest OS and
transfers them over the network. This is a default method that uses log shipping servers.

1287 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Over PowerShell Direct. In this scenario, Veeam Backup & Replication obtains WAL files from the VM guest
OS over PowerShell Direct, bypassing the network. PowerShell Direct is used for VMs that reside on
Microsoft Hyper-V Server 2016 (or later) and run Microsoft Windows 10 (or later) or Microsoft Windows
Server 2016 (or later). Veeam Backup & Replication requires Microsoft PowerShell 2.0 (or later) to work
over PowerShell Direct.

Location of Log Shipping Server and VMs


When choosing a log shipping server for the job, Veeam Backup & Replication considers the location of the
PostgreSQL VM and log shipping server. Veeam Backup & Replication uses the following priority rules to select
the log shipping server:

1. The log shipping server is located on the source Microsoft Hyper-V host performing the role of the on-
host backup proxy.

2. The log shipping server and PostgreSQL VM are located in the same network.

3. The log shipping server and PostgreSQL VM are located in different networks (the production
infrastructure is isolated from the backup infrastructure).

That is, when choosing a log shipping server, Veeam Backup & Replication will give the top priority to a VM that
is located on the source Microsoft Hyper-V host.

Veeam Backup & Replication assigns log shipping servers per job session. When a new job session starts,
Veeam Backup & Replication detects a new log shipping servers. Veeam Backup & Replication can also re-detect
available servers during the job session. If the log shipping server becomes unavailable for some reason,
Veeam Backup & Replication will fail over to another log shipping server.

IMP ORTANT

If you do not want to use some servers for WAL files transport, you can manually define what server
Veeam Backup & Replication must use as a log shipping server in the job settings. It is recommended that
you assign the log shipping server role to a number of servers for availability purposes.

1288 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
WAL Files Backup Statistics
You can view the statistics of the WAL files backup job in the History view or in the Home view
in Veeam Backup & Replication.

In the statistics window, you can examine the overall statistics for WAL files, as well as view per -VM
information.

In the upper part of the statistics window, Veeam Backup & Replication displays information about the WAL files
backup job for all VMs included in the parent backup job.

The La st period (all VMs) section contains statistics data for the selected session of the backup job.

In the Da tabases column, you can view the following information:

• Protected — number of instances that were backed up at least once during the last session.

• Unprotected — number of instances that failed to be backed up during the last session.

• Excluded — instances excluded from processing. Instances may be excluded for the following reasons:
ARCHIVELOG mode is turned off for the database (the database is in NOARCHIVELOG mode), database
was deleted after the latest full backup, or database was added to the list of exclusions.

NOTE

Unprotected instances do not comprise E x cluded instances, as they have different reasons for being non-
processed. See also this Veeam KB article for information on processing instances in NOARCHIVE mode.

In the RP O column, you can view the following information:

• SLA — how many log backup intervals completed in time with successful log backup (calculated as
percentage of total number of intervals).

• Misses — how many intervals failed to complete in time with successful log backup (number of intervals).

• Max delay — difference between the configured log backup interval and time actually required for log
backup. If exceeded, a warning is issued.

In the Sta tus column, the following information is displayed (per job): number of VMs processed successfully,
with warnings or with errors.

The La test session section displays the following information for the latest log processing interval for the
selected VM:

• Duration — duration of log shipment from the VM guest OS to the backup repository since the current log
processing interval has started.

• Bottleneck — operation with the greatest duration in the last completed interval. The operation may have
the following bottlenecks:

Display Name Slowing-down Operation

Log backup Saving archived log files to a temporary location on VM guest OS (to work around, see
the Veeam KB article: this Veeam KB article)

Network Uploading log files to the log shipping server

1289 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Display Name Slowing-down Operation

Target Saving files to the target repository

• Read — amount of data read from the temporary folder on VM guest OS

• Transferred — amount of data transferred to the target repository

The La st period section displays the following statistics of log backups for every VM for the latest session of the
log backup job:

• The RP O column displays statistics on log processing interval.

• The Sessions column includes statistics of log backups per VM, calculated based on their status:

o Success — number of intervals when all database logs were backed up successfully

o Warning — number of sequential intervals with failed log processing (if not more than 4 intervals in a
sequence)

o Errors — number of sequential intervals with failed log processing (more than 4 intervals in a
sequence)

• The Duration column includes the following information:

o Average — average duration of log data transfer (through all intervals in the session)

o Maximum — maximal duration of log data transfer (through all intervals in the session)

o Sync interval — duration of periodic intervals specified for log backup in the parent job settings
(default is 15 min)

• The Log size column displays the following information:

o Average — average amount of data read from the VM guest OS through all intervals

o Maximum — maximal amount of data read from the VM guest OS over all 15-min intervals

o Total — total amount of data written to the backup repository

The pane below shows all actions performed during the job run. To filter out actions with the certain status, use
the E rrors, W arnings and Success buttons.

NOTE

Statistics on WAL files processing is updated periodically, simultaneously for the VM backup job (parent)
and WAL files backup job (child job).

1290 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Job Scheduling
You can start backup jobs manually or schedule them to start automatically at specific time.
Veeam Backup & Replication lets you configure the following settings for the job:

• Scheduling settings

• Job retry settings

• Backup window settings

Automatic Startup Schedule


To run a job periodically without user intervention, you can schedule the job to start automatically. The Veeam
Backup Service running on the backup server continuously checks configuration settings of all jobs configured
on the backup server, and starts them according to their schedule.

Veeam Backup & Replication lets you configure the following scheduling settings for jobs:

• You can schedule jobs to run at specific time every day or on selected days

• You can schedule jobs to run periodically at specific time intervals

• You can schedule jobs to run continuously

• You can chain jobs

Jobs Started at Specific Time


You can schedule jobs to start at specific time daily, on specific week days or monthly on selected days.

This type of schedule requires that you define the exact time when the job must be started. For example, you
can configure the job to start daily at 10:00 PM or every first Sunday of the month at 12:00 AM.

Jobs Started at Specific Time Intervals


You can schedule jobs to start periodically throughout a day at a specific time interval. The time interval
between job sessions can be defined in minutes or hours. For example, you can configure a job to start every 30
minutes or every 2 hours.

For periodically run jobs, reference time is midnight (12:00 AM). Veeam Backup & Replication always starts
counting defined intervals from 12:00 AM, and the first job session will start at 12:00 AM. For example, if you
configure a job to run with a 4-hour interval, the job will start at 12:00 AM, 4:00 AM, 8:00 AM, 12:00 PM, 4:00
PM and so on.

1291 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If necessary, you can specify an offset for periodically run jobs. The offset is an exact time within an hour when
the job must start. For example, you can configure the job to start with a 4-hour interval and specify offset
equal to 15 minutes. In this case, the job will start at 12:15 AM, 4:15 AM, 8:15 AM, 12:15 PM, 4:15 PM and so on.

If a session of a periodically run job does not fit into the specified time interval and overlaps the next planned
job session, Veeam Backup & Replication starts the next backup job session at the nearest scheduled interval.
For example, you set up a job to run with a 4-hour interval. The first job session starts at 12:00 AM, takes 5
hours and completes at 5:00 AM. In this case, Veeam Backup & Replication will start a new job session at 8:00
AM.

Jobs Run Continuously


You can schedule the job to run continuously — that is, in a non-stop manner. A new session of a continuously
running job starts as soon as the previous job session completes. Continuously run jobs can help you implement
near-continuous data protection (near-CDP) for the most critical applications installed on VMs.

Chained Jobs
In the common practice, data protection jobs configured in the virtual environment start one after another:
when job A finishes, job B starts and so on. You can create a chain of jobs using scheduling settings. To do this,
you must define the start time for the first job in the chain. For other jobs in the chain, you must select the After
this job option and choose the preceding job from the list.

Job chaining is not limited to jobs of specific type only. You can create a chain of jobs of different types. For
example, you can:

1. Set a backup job as the first job in the chain.

2. Configure a SureBackup job and chain with the backup job. In this case, Veeam Backup & Replication will
automatically verify a backup file created by the backup job after the backup job completes.

1292 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• When you start the initial job manually, Veeam Backup & Replication does not start chained jobs in
the Disabled state. If at least one job chained directly to the initial job is in the Enabled state,
Veeam Backup & Replication offers you to start the chained jobs as well. Click Y es to start the whole
job chain or No to start only the first job in the chain.
• If you start the initial job manually and chain another job while the initial job is running, the chained
job will start when the initial job completes.
• If you schedule active or synthetic full backups for the chained job, but the initial job does not run
on these days, the active and synthetic full backups will not be created for the chained job.
• If a job in the chain fails or is canceled by a user, Veeam Backup & Replication still starts the next
chained jobs. Note that if the failed or canceled job was started by a schedule,
Veeam Backup & Replication will start the chained job only after all job retries.

Recommendations on Job Chaining

You should use job chaining wisely. Job chaining removes guesswork from job scheduling but has a number of
drawbacks:

• You cannot predict precisely how much time the initial job will require and when jobs chained to it will
start. Depending on the situation, the job schedule may shift, and some operations may even not be
performed as planned.

For example, you configure 2 jobs:

o Job 1 is scheduled to start at 10:00 PM daily and typically takes 1 hour.

o Job 2 is scheduled to start after Job 1 daily. Synthetic full backup is scheduled on Saturday.

Imagine that Job 1 starts on Saturday and runs for 2.5 hours instead of 1 hour. Job 2 will then start after
midnight on Sunday, and the synthetic full backup planned on Saturday will not be created.

• Errors in job sessions may cause the job schedule to shift. For example, if the initial job in the chain fails,
Veeam Backup & Replication will attempt to retry it, and the schedule for chained jobs will shift.

• Load on backup infrastructure resources may be not balanced. Some slots on backup proxies and backup
repositories may be available but will not be used since jobs are queued to run one by one. And if you use
a backup repository that supports multiple I/O streams, its resources will not be used efficiently.

Instead of job chaining, you can balance the load on backup infrastructure components. To do this, you must
limit the number of concurrent tasks on backup proxies and backup repositories. For more inf ormation, see
Limiting the Number of Concurrent Tasks.

Job Retry
You can instruct Veeam Backup & Replication to retry a job several times if the initial job run fails. By default,
Veeam Backup & Replication automatically retries a failed job for 3 times within one job session. You can specify
a custom number of retries in the job settings.

1293 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication launches a retry for a job only if the previous job session failed, and one or several
VMs in the job were not processed. Veeam Backup & Replication does not perform the retry if a job session has
finished with the Success or Warning status. During the job retry, Veeam Backup & Replication processes only
failed VMs.

The way Veeam Backup & Replication performs the retry differs depending on the backup chain format of the
backup chain.

IMP ORTANT

Veeam Backup & Replication does not perform automatic retry for jobs that were started or stopped
manually.

Job Retry for Per-Machine Backups


During one job session, Veeam Backup & Replication creates multiple backup files: one backup file for each VM
in the job. If some VMs are not processed during a job run, Veeam Backup & Replication creates backup files only
for those VMs that are successfully processed.

During a job retry, Veeam Backup & Replication attempts to process failed VMs. If processing of failed VMs
succeeds, Veeam Backup & Replication creates new backup files and writes data of the processed VMs to these
files. If processing fails during all job retries, Veeam Backup & Replication processes the failed VMs during the
next job sessions and writes VM data to the backup files created by the current job session.

For example, you have configured a job for 2 VMs: VM 1 and VM 2. The job uses the forward incremental
method.

During the first job session, Veeam Backup & Replication successfully processes VM 1 and creates a full backup
file for it. VM 2 is not processed during all 3 job retries. On the next job session, Veeam Backup & Replication
attempts to process the VMs. If processing succeeds, Veeam Backup & Replication creates an incremental
backup for VM 1 and a full backup for VM 2. As a result, you have 3 backups:

• Full and incremental backups containing VM 1 data .

• Full backup containing VM 2 data .

Job Retry for Single-File Backups


During one job session, Veeam Backup & Replication creates one backup file for all VMs in the job. If some VMs
are not processed during the first job run, Veeam Backup & Replication creates a backup file containing data for
those VMs that are successfully processed.

During a job retry, Veeam Backup & Replication attempts to process failed VMs. If processing of failed VMs
succeeds, Veeam Backup & Replication writes data of the processed VMs to the backup file that is created at the
initial job run. If processing fails during all job retries, Veeam Backup & Replication processes the failed VMs
during the next job sessions and writes VM data to the backup file created by the current job session.

For example, you have configured a job for 2 VMs: VM 1 and VM 2. The job uses the forward incremental
method.

1294 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
During the first job session, Veeam Backup & Replication successfully processes VM 1 and creates a full backup
file for it. VM 2 is not processed during all 3 job retries. In this case, Veeam Backup & Replication attempts to
process the failed VM 2 within the next job session. Data for VM 2 is written to the backup file created within
this job session, which is an incremental backup. As a result, you have 2 files:

• Full backup file containing a full restore point for VM 1.

• Incremental backup file containing a full restore point for VM 2 and an incremental restore point for VM 1.

Backup Window
If necessary, you can specify a backup window for jobs. The backup window is a period of time on weekdays
when jobs are permitted to run. If the job exceeds the allowed window, Veeam Backup & Replication will
automatically stop this job. Also, if a job is in progress and enters the denied window,
Veeam Backup & Replication will stop it immediately and reschedule according to the schedule settings.

The backup window can be helpful if you do not want data protection jobs to produce unwanted overhead for
the production environment or do not want jobs to overlap production hours. In this case, you can define the
time interval during which the job must not run.

IMP ORTANT

The backup window affects only the data transport process and health check operations. Other
transformation processes can be performed in the target repository outside the backup window. Linked
jobs that process Microsoft SQL transaction logs and Oracle archived logs are not affected by the backup
window settings.

1295 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Window for Periodically Run Jobs
If you define the backup window for a job that runs periodically at specific time intervals,
Veeam Backup & Replication will immediately start the job after the denied window is over. All subsequent
backup job sessions will be performed according to specified scheduling settings.

For example, you have configured a job to run with a 4-hour interval with an offset of 15 minutes. The allowed
backup window for the job is 7:00 PM to 8:00 AM. Veeam Backup & Replication will run this job in the following
way:

1. The first job session will start at 12:15 AM (since midnight is a reference time for periodically run jobs).

2. The next job session will start at 4:15 AM.

3. The job session at 8:15 AM will not be performed as it falls into the denied period of the backup window.

4. The next job session will start immediately after the denied period is over: at 7:15 PM.

5. After that, Veeam Backup & Replication will run the job by the defined schedule: at 8:15 PM, 12:15 AM and
so on.

Manual Start of Backup Jobs


You can start jobs manually if you need to capture VM data at a specific point in time and do not want to re -
configure job scheduling settings. For example, you can start a job to create a VM backup before you install new
software on a VM or enable a new feature.

When you start the job manually, Veeam Backup & Replication runs a regular job session that produces a new
restore point in the backup chain in the backup repository.

1296 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To start and stop jobs configured on the backup server, you can use the Sta rt and Stop buttons on the ribbon or
the commands in the shortcut menu.

Manual Stop of Backup Jobs


You can stop job execution at any moment of time. For example, you can stop a job if the job processes several
VMs but the workload appears to be greater than you expected. Or you can stop the job if there is not enough
time to finish the job session.

You can stop a job in 2 ways:

• You can stop the job immediately. In this scenario, Veeam Backup & Replication terminates the job session
and does not create a new restore point for VMs that are currently processed.

• You can stop the job gracefully. In this scenario, Veeam Backup & Replication creates a restore point for
the VMs that are currently processed and then terminates the job session.

Immediate Stop of Jobs


Immediate job stop terminates the job session instantly. The job finishes with the following results:

• VMs that Veeam Backup & Replication has succeeded to process by the time you stop the job will have
new restore points.

• VMs that Veeam Backup & Replication is currently processing and VMs that Veeam Backup & Replication
has not started to process will not have new restore points.

When you stop a job session immediately, Veeam Backup & Replication performs the following operations:

1. If a checkpoint for a VM has already been created, Veeam Backup & Replication instructs Microsoft Hyper-
V to remove the checkpoint.

2. Veeam Backup & Replication terminates all job processes and tasks. The job is finished with the Failed
error.

1297 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
All restore points created with the previous job sessions remain untouched. You can use them for restore
operations.

Graceful Stop of Jobs


Graceful job stop instructs Veeam Backup & Replication that it must create restore points for VMs that are
currently being processed, and then terminate the job. The job finishes with the following results:

• VMs that Veeam Backup & Replication has succeeded to process and VMs that are being processed will
have new restore points.

• VMs that Veeam Backup & Replication has not started to process will not have new restore points.

You can use graceful job stop for the following types of jobs:

• Backup jobs

• Replication jobs

You cannot use graceful job stop for the following types of jobs:

• File copy jobs

• Backup copy jobs

• Restore operations

VMs added to the job are processed in the order defined in job settings. Information about VMs that have
already been processed and VMs that are being processed is displayed in job details.

If you stop the job gracefully before Veeam Backup & Replication starts processing the first VM in the job, the
job will be finished with the Failed error. You will see the message Operation was canceled by user in job details.

1298 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Immutability for Backup Files
Veeam Backup & Replication allows you to prohibit deletion of data from backup repositories by making that
data temporarily immutable. It is done for increased security: immutability protects your data against loss as a
result of attacks, malware activity or any other injurious actions.

You can enable the immutability feature for the following types of backup repositories:

• Dell Data Domain. For more information, see Immutability for Dell Data Domain.

• Hardened repository. For more information, see Hardened Repository.

• HPE StoreOnce. For more information, see Immutability for HPE StoreOnce.

• Object storage repository. For more information, see Immutability for Object Storage Repositories.

• Scale-out backup repository. For more information, see Immutability for Scale-out Backup Repository.

1299 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Health Check for Backup Files
You can instruct Veeam Backup & Replication to periodically perform a health check for the latest restore point
in the backup chain. During the health check, Veeam Backup & Replication performs a cyclic redundancy check
(CRC) for metadata and a hash check for VM data blocks in the backup file to verify their integrity. The health
check helps make sure that the restore point is consistent, and you will be able to restore data from this restore
point.

The health check can be performed for all types of backup chains:

• Forever forward incremental

• Forward incremental

• Reverse incremental backup chains

To run the health check periodically, you must enable the P erform backup files health check option in the
backup job settings and define the health check schedule. By default, the health check is performed at 5:00 on
the last Saturday of every month (at 22:00 on the last Friday of every month- for version 12). You can change
the schedule and run the health check weekly or monthly on specific days.

Verification Content
The health check always verifies only the latest restore point in the backup chain. In case of forever forward
incremental and forward incremental backup chains, if the latest restore point is incomplete, the health check
verifies the restore point preceding the latest one.

1300 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Note that the health check procedure verifies not the latest backup file in the backup chain, but the latest
restore point for a VM. The latest restore point corresponds to the state of the VM at the date and time when
the latest backup file for this VM was created. Data blocks that are required to "compose" the VM latest state
are typically spread out across several backup files in the backup chain. Therefore, to verify the latest state of
the VM, Veeam Backup & Replication must open several backup files in the backup chain and read data blocks
from these backup files. For this reason, the health check procedure may take long.

The health check verifies only those virtual disks of a VM that are available in the latest restore point. For
example, you added a VM with 3 virtual disks to a backup job. The VM was backed up Sunday through Tuesday.
On Wednesday, you removed 1 virtual disk, and Veeam Backup & Replication run the health check for the VM.
During the health check, Veeam Backup & Replication will verify only the 2 remaining virtual disks.

The health check verifies only those VMs that are available in the latest restore point. For example, you added 2
VMs to a backup job and ran the job several times. The health check verified 2 VMs. If you remove 1 VM from the
backup job, the next scheduled health check run will verify the latest unverified restore point for the removed
VM, and the latest restore point for the remaining VM. In future, the health check will verify only the restore
point for the remaining VM in the job.

Limitations for Health Check


Consider the following limitations for the health check:

• For data blocks located in the capacity tier, the health check works as described in the Health Check for
Capacity Tier section.

• [For per-machine backup chains] If you add a new VM to an existing backup job that has been run for some
time, Veeam Backup & Replication will perform the health check for it during the next incremental backup
job session for the added VM.

• Linux immutable repositories do not support repair. If the health check detects corrupted data,
Veeam Backup & Replication marks the restore point as corrupted in the configuration database and
finishes the health check session. In that case, you need to perform the active full backup for this backup
chain. Otherwise, Veeam Backup & Replication will finish every backup job session creating subsequent
incremental restore points with the Error status.

How Health Check Works


When Veeam Backup & Replication saves a new restore point to the backup repository, it calculates CRC values
for backup metadata and hash values for data blocks of VM disk in the backup file, and s aves these values in the
metadata of the backup file, together with VM data. During the health check session,
Veeam Backup & Replication uses these values to make sure that a verified restore point is consistent.

1301 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you perform health check for encrypted backup files, Veeam Backup & Replication will pass encryption
keys to the regular backup repository or cloud repository. For more information on encryption, see Data
Encryption.

Veeam Backup & Replication uses different mechanisms of health check for different types of backup chains:

• Forever forward incremental and forward incremental backup chains

• Reverse incremental backup chains

Forever Forward Incremental and Forward Incremental Backup Chains

The health check for forward incremental backup chains is performed in the following way:

1. The health check starts according to the schedule. Depending on the stor age type of the repository, the
health check procedure can be performed on different infrastructure components:

o For direct attached storage — on the repository itself.

o For network attached storage — on the gateway server.

o For deduplicating storage appliances — on the gateway server.

NOTE

Consider the following:

• The gateway server placement may influence the time needed for the health check procedure
when using network attached storage and deduplicating storage appliances as repositories. As
the health check is performed on the gateway server, we recommend to locate gateway
servers as close to the backup repository as possible.
• The health check runs only after all jobs and operations that process a backup are completed
(for example, a backup job, a restore job, synthetic operations with backups and so on). If
some of these activities are started, the health check stops.
• If a health check session does not complete until the next scheduled run, this session will stop
and a new session will start according to the schedule.
• If you add new VMs to a backup job which block data has been processed by the health check,
the health check will verify only block data of new VMs and will skip backups of previously
added VMs.

2. The health check calculates CRC values for backup metadata and hash values for VM disks data blocks in
the backup file and compares them with the CRC and hash values that are already stored in the backup
file.

During the health check, Veeam Backup & Replication verifies the latest restore point in the backup chain
(restore point created by the last backup job session). If the latest restore point in the backup chain is
incomplete, Veeam Backup & Replication checks the restore point preceding the latest one.

3. If the health check does not detect data corruption, the backup job session completes in a regular way.

If the health check detects corrupted data, Veeam Backup & Replication completes the backup job with
the Error status and starts the health check retry process. The health check retry starts as a separate
backup job session.

1302 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Depending on the revealed data corruption, Veeam Backup & Replication performs the following actions:

o If the health check has detected corrupted backup meta data in the full backup file,
Veeam Backup & Replication marks the backup chain starting from this full restore point as corrupted
in the configuration database. During the health check retry, Veeam Backup & Replication transports
data blocks of the whole VM image from the source volume, creates a new full backup file in the
backup repository and saves transported data blocks to it.

o If the health check has detected corrupted backup metadata in the incremental backup file,
Veeam Backup & Replication removes information about this incremental restore point and
subsequent incremental restore points from the configuration database. During the health check
retry, Veeam Backup & Replication transports new incremental data relative to the latest valid restore
point in the backup chain from the source volume, creates a new incremental backup file in the
backup repository and saves transported data blocks to it.

o If the health check has detected corrupted VM disk blocks in the full or incremental backup file,
Veeam Backup & Replication marks the restore point that includes the corrupted data blocks and
subsequent incremental restore points as corrupted in the configuration database. During the health
check retry, Veeam Backup & Replication transports data blocks from the source volume. In addition,
Veeam Backup & Replication transports data blocks that have changed since the backup job session
that has triggered the health check. Veeam Backup & Replication stores these data blocks to the
latest restore point that has been created by the current backup job session (session that has
triggered the health check retry).

Reverse Incremental Backup Chains

In case of reverse incremental backup chains, the health check always verifies only the latest restore point in the
backup chain, which is always a full backup file.

The health check is performed in the following way:

1. The health check starts according to the schedule. Depending on the storage type of the repository, the
health check procedure can be performed on different infrastructure components:

o For direct attached storage — on the repository itself.

o For network attached storage — on the gateway server.

o For deduplicating storage appliances — on the gateway server.

1303 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Veeam Backup & Replication verifies the full backup file. It calculates CRC values for backup metadata and
hash values for VM disks data blocks in the full backup file, and compares them with the CRC and hash
values that are already stored in the full backup file.

3. If the health check does not detect data corruption, the backup job session completes in a regular way.

If the health check detects corrupted data, Veeam Backup & Replication completes the backup job with
the Error status and starts the health check retry process. The health check retry starts as a separate
backup job session.

Depending on the revealed data corruption, Veeam Backup & Replication performs the following actions:

o If the health check has detected corrupted backup metadata in the full backup file ,
Veeam Backup & Replication marks the whole backup chain (full backup file and preceding reverse
incremental backup files) as corrupted in the configuration database. During the health check retry,
Veeam Backup & Replication transports data blocks of the whole VM image from the source datastore,
creates a new full backup file in the backup repository and saves transported data blocks to it.

o If the health check has detected corrupted VM disk blocks in the full backup file,
Veeam Backup & Replication marks the full backup file and preceding reverse incremental backup files
as corrupted in the configuration database. During the health check retry,
Veeam Backup & Replication transports data blocks from the source datastore. In addition,
Veeam Backup & Replication transports data blocks that have changed since the backup job session
that has triggered the health check. Veeam Backup & Replication stores these data blocks to the
existing full backup file in the backup repository. Corrupted data blocks that have b een replaced with
data blocks from the source datastore are stored to an existing reverse incremental backup file
preceding the full backup file.

Health Check Retry Mode


If the health check detects corrupted data, the backup job will switch to the Retry mode and will start the
health check retry process. During the health check retry, Veeam Backup & Replication transports data blocks of
the whole VM image from the source volume, creates a new full backup file in the object storage repository and
saves transported data blocks to it.

If Veeam Backup & Replication fails to fix the corrupted data during all health check retries, you must retry the
job manually. In this case, Veeam Backup & Replication will transport the required data blocks from the source
volume, to fix the latest restore point. If the latest restore point in the backup chain is incomplete,
Veeam Backup & Replication will attempt to fix the restore point preceding the latest one.

1304 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For scheduled jobs, the number of health check retries is equal to the number of job retries specified in the job
settings. For jobs started manually, Veeam Backup & Replication performs 1 health check retry.

IMP ORTANT

To allow Veeam Backup & Replication add the repaired data blocks to the latest restore point after
completing the health check, the backup job must meet the following requirements:

• You must schedule the backups job to run automatically. For more information, see the Schedule
step of the New Backup Job wizard.
• The target object storage is not set to the Maintenance mode.
• Backup window settings must allow a backup job to run after the health check completes.

If the backup job does not meet these requirements, Veeam Backup & Replication will add the repaired
data blocks to a new restore point, created during a next run of the backup job.

1305 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Compact of Full Backup File
Veeam Backup & Replication allows you to defragment the full backup file, which increases the reading and
writing speed from and to the file. To compact the full backup file periodically, you must enable the Defragment
a nd compact full backup file option in the backup job settings and define the compact operation schedule. By
default, the compact operation is performed on the last Saturday of every month. You ca n change the compact
operation schedule and instruct Veeam Backup & Replication to perform it weekly or monthly on specific days.

Limitations for Full Backup File Compact


The full backup file compact has the following limitations:

• The Defragment and compact full backup file option works for forever forward incremental or reverse
incremental backup chains. For this reason, you must not schedule active or synthetic full backups.

Although you do not schedule active full backups for forever forward incremental or reverse incremental
backup chains, full backups can be created. For example, you can create them manually or
Veeam Backup & Replication can create them during the health check. On the day when active full backups
are triggered, Veeam Backup & Replication does not create compact full backups.
Veeam Backup & Replication will create them on another day during the backup job session.

• Veeam Backup & Replication does not compact full backup files that have been offloaded to cloud -based
object storage. For more information, see Capacity Tier.

• The backup repository must have enough space to store a file of the full backup size. During the compact
process, Veeam Backup & Replication creates auxiliary files that exist in the backup repository until the
end of the compact operation.

• [For per-machine backup chains] If you add a new VM to an existing backup job that has been run for some
time, Veeam Backup & Replication will perform the compact full operation for it during the next
incremental backup job session for the added VM.

• If you change the block size in backup job settings, Veeam Backup & Replication does not change the
block size in the compacted backup file till the next full backup. However, if you change compression
settings in backup job settings, during the next compact file operation Veeam Backup & Replication
changes the compression level for the compacted backup file.

1306 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removal of Deleted VMs Data
During the compact operation, Veeam Backup & Replication does not copy all data blocks from the VBK file to
the newly created file. It copies only data blocks of VMs whose information is stored in the configuration
database. For example, if the VM is removed from the backup job, its data is not copied to the new full bac kup
file. This approach helps reduce the size of the full backup file and remove unnecessary data from it.

VM Data Take Out


If the full backup file contains data for a VM that has only one restore point and this restore point is older than 7
days, during the compact operation Veeam Backup & Replication will extract data for this VM from the full
backup file and write this data to a separate full backup file. Such backup will be displayed under the Ba ckups >
Disk (Imported) node in the Home view.

The mechanism works if the following conditions are met:

• The Remove deleted VMs data option is not enabled in the backup job settings.

• The Use per-machine backup files option is not enabled in backup repository settings.

1307 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Move
Veeam Backup & Replication allows you to move all backups of a backup job to another repository or to move
specific workloads and their backups to another job.

Moving backups to another repository can be helpful if you are running out of free space on a repository and
want to move all backups created by a backup job to another repository, target the backup job to this repository
and continue the backup chain.

Moving workloads and their backups to another backup job can be helpful if you want to separate one backup
job into multiple backup jobs, or you want to change backup settings for specific workloads. Also, you want to
continue the existing backup chains for the workloads.

How Moving to Another Repository Works


The following steps show a common* algorithm of how Veeam Backup & Replication moves backups to another
repository and targets the job to this repository:

1. Disables the backup job.

2. Copies backup files to a new location.

3. Targets the backup job to the new location.

4. Deletes source backup files.

5. After the successful move, Veeam Backup & Replication enables the backup job. The enabled backup job
continues the backup chain for the existing and moved backups.

*Nuances are described further in this section.

How Moving to Another Job Works


The following steps show a common* algorithm of how Veeam Backup & Replication moves backups to another
job:

1. Disables the source and target jobs.

2. [For Veeam Backup & Replication versions prior to 12.1 (build 12.1.0.2131)] Copies backup files of selected
workloads to the repository where the target job saves backups.

3. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] Veeam Backup & Replication
behaves in different ways depending on whether backups are moved within one repository:

o If within one repository without immutability, Veeam Backup & Replication invokes the native move
method of the file system. This applies if the repository is Windows, Linux, CIFS, NFS, deduplicating
storage appliance or scale-out backup repository of one of the listed types.

o In other cases, Veeam Backup & Replication copies backup files of selected workloads to the
repository where the target job saves backups.

4. Excludes the selected workloads from being processed by the source job.

5. Includes the selected workloads to be processed by the target job.

6. After the successful move, Veeam Backup & Replication enables the source and target jobs. The target
backup job continues the backup chain for the existing and moved backups.
*Nuances are described further in this section.

1308 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements and Limitations
This section describes requirements and limitations for different types of jobs and different types of repositories
where backups can be stored.

Common Considerations
Consider the following:

• You can move individual workloads and their backups only if backups are per-machine backups with
separate metadata files and only to repositories with the Use p er-machine backup files check box enabled.

• You can move backups between repositories with the Use per-machine backup files check box selected
and not selected. However, the move operation does not change the backup chain format (single-file
backup, per-machine backup with single metadata file or per-machine backup with separate metadata
files). The job will continue the backup chain of the original backup chain format. If you want to change
the backup chain format of the chain, use the detach from job operation. For more information, see
Upgrading Backup Chain Formats.

[For moving to object storage repositories] You can move only per-machine backups with separate
metadata files.

• After you move workloads and their backups between jobs, you must adjust the gues t processing settings
for the moved workloads. After move, Veeam Backup & Replication uses the default guest processing
setting. For more information on guest processing settings, see Guest Processing.

• You cannot move a workload and its backups to a job that already processes this workload.

• You cannot move backups of workloads after they were migrated between standalone Hyper -V hosts that
are not a part of one cluster or SCVMM server registered in Veeam Backup & Replication. That is because
Veeam Backup & Replication considers the migrated workload as new and the "old" workload as deleted.
To create backups of the migrated workload in another repository, add the migrated workload to the
dedicated backup job. After that, Veeam Backup & Replication will create full backups for these
workloads.

• You cannot move backups from encrypted jobs to unencrypted jobs and vice versa.

• You cannot move backups imported without the metadata (.VBM) file.

• You cannot launch the restore operation for backups being moved at the moment.

• You cannot move backups from an HPE StoreOnce repository used as a target for backup copy for HPE
StoreOnce repositories.

• You cannot move backups created by backup copy jobs in the legacy periodic copy mode. To move
backups, you first need to upgrade the backup format as described in section Upgrading Backup Chain
Formats.

• After you move backups between backup copy jobs, Veeam Backup & Replication does not include and
exclude workloads from the backup copy jobs. You should do that manually.

• You cannot move backups created by Veeam plug-ins for Enterprise applications, Veeam Cloud Plug-ins
(Veeam Backup for AWS, Veeam Backup for Google Cloud, Veeam Backup for Microsoft Azure), Veeam
Backup for Nutanix AHV, Veeam Backup for RHV and Kasten K10.

• You cannot move backups created in Veeam Cloud Connect repositories. For more information on Veeam
Cloud Connect repositories, see the Cloud Repository section in the Veeam Cloud Connect Guide.

1309 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• To use the move to another repository functionality and move backups to an object storage repository,
check that defragment and compact full backup file, reverse incremental backup method and synthetic
full backup are disabled for the job. As an alternative, you can use the move to another job functionality
and move backups to a job already targeted to an object storage repository.

• Before moving workloads and their backups to a deduplicating storage appliance,


Veeam Backup & Replication checks whether such move can damage the backup chain. If so,
Veeam Backup & Replication prohibits the move operation. After Veeam Backup & Replication completes
the move operation, it checks that the target backup job is configured correctly. However, you must
change the settings manually. You can find which backup settings need to be changed in the move session
or in this Veeam KB article. For more information on how to view session statistics, see Viewing Job
Session Results.

• You can move VMware Cloud Director backups of a whole job or individual vApps. You cannot move
backups of VMs.

• If you move workloads and their backups between jobs linked to the same tape job, the tape job continues
to create incremental backups within the existing backup chain. Otherwise, the tape job will create an
active full backup for the moved workloads.

Backup Jobs with Linked Backup Copy Jobs


If you move workloads and their backups from a backup job which is linked to a backup copy job, the following
applies:

• If the source and target backup jobs are linked to backup copy jobs, Veeam Backup & Replication also
moves backups and workloads between backup copy jobs. Note that Veeam Backup & Replication
performs move only if each backup job is linked to one backup copy job only. For example, Backup Job 1
processes VM1 and VM2 and is linked to Backup Copy Job 1. Backup Job 2 processes VM3 and VM4 and is
linked to Backup Copy Job 2. You move VM1 and its backups to the Backup Job 2.
Veeam Backup & Replication will also move the VM1 and its backups from Backup Copy Job 1 to Backup
Copy Job 2. As a result, Backup Job 2 and Backup Copy Job 2 will process VM3, VM4 and VM1.
If a backup job is linked to multiple backup copy jobs, you need to move workloads and backups between
the backup copy jobs manually. To do that, use the move to another job operation as described in section
Moving Backups. If you do not move workloads between backup copy jobs, the backup copy job linked to
the target backup job will create active full backup copies for the moved workloads.

• If the source backup job is still in progress, the move operation fails.

• Before moving backup copies, Veeam Backup & Replication waits till the source move backup process
finishes successfully. Only then, Veeam Backup & Replication disables the linked backup copy job and
moves backup copies.

Log Backups
If you move workloads and their backups from a backup job for which log backup is configured, the following
applies:

• Veeam Backup & Replication moves log backups along with workloads.

• Veeam Backup & Replication disables the log backup jobs gracefully before moving log backups .

• [For SQL server Always On availability groups] You cannot move individual nodes from a job.

• [For Oracle Data Guard] You must move all servers from the job. If you move only one server, application
item restore stops working. To repair the application item restore functionality, you will need to move the
server back to the original job.

1310 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• If guest processing is disabled in the target job, log backups are moved, however they will not be
processed by the target job. To process log backups, make sure that guest processing is enabled for the
target job as described in section Specify Guest Processing Settings.

Backups with GFS Flags


If you move backups from a backup or backup copy job where long -term (GFS) retention is configured, the
following applies:

• When you move all backups to another repository, Veeam Backup & Replication preserves all backups with
GFS flags.

• When you move a workload and its backups to another job, Veeam Backup & Replication starts to retain
backups according to the settings configured in the target job. Veeam Backup & Replication deletes all
GFS backups that do not comply with the retention policy in the target job. For example, if yearly backups
are not configured in the target job, Veeam Backup & Replication will remove them after the move
operation finishes.

Agent Backups
For more information on moving Veeam Agent backups, see the Moving Backups section in the Veeam Agent
Management Guide.

Immutable Repositories
If you move workloads and their backups from a repository for which immutability is ena bled, the following
applies:

• During the move operation, Veeam Backup & Replication copies the whole backup chain. After the move
operation finishes, original backups stored in the immutable repository are moved to the node with the
( Orphaned) postfix. Other original backups are deleted.

• Veeam Backup & Replication retains backups moved to the ( Orphaned) node according to the retention
period specified in the job from which the backups were moved. If the retention period is shorter than the
immutability period specified in the repository settings where the backups were stored,
Veeam Backup & Replication sets the retention period as equal to the immutability period.

If the retention period is set in days, Veeam Backup & Replication deletes a backup after its retention
period ends. If the retention period is set in restore points, Veeam Backup & Replication does not delete
backups. You can delete these backups manually after the retention period ends.

Scale-Out Backup Repositories


If you move workloads and their backups from a scale-out backup repository, the following applies:

• Veeam Backup & Replication moves backups only from the performance tier. If you want to move data
from the capacity tier, you first need to download it to the performance tier. For more information, see
Downloading Data from Capacity Tier.

• Backups stored in the capacity and archive tiers are moved to the node with the ( Orphaned) postfix. The
backups are retained according to the retention settings of the job from which the backups were moved. If
the retention period is set in days, the Veeam Backup & Replication retains the backups according to the
configured retention and deletes the backups from the repository after the retention period ends. If the
retention period is set in restore points, Veeam Backup & Replication leaves backup files in a backup chain.
The minimum number of backup files left equals the current retention period. You can delete these
backup files manually as described in section Deleting Backups from Disk.

1311 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Veeam Backup & Replication does not move backups from extents in the Maintenance mode. These
backups are deleted once the extents exit the Maintenance mode.

1312 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Resume on Disconnect
Veeam Backup & Replication can handle a situation of an unstable network during backup, backup copy and
replication jobs. If a network connection drops for a short period of time during the data transport process,
Veeam Backup & Replication automatically resumes the dropped network connection. The data transfer process
starts from the point when the connection was lost. The resume on disconnect capability improves the reliability
of remote data transfer, reduces the backup window and minimizes the network load.

Veeam Backup & Replication automatically re-establishes a connection between the following backup
infrastructure components engaged in the data transfer process:

• Backup server

• Source and target Microsoft Hyper-V hosts

• Off-host backup proxy

• Backup repository

Resume on disconnect works only for dropped network connections. Veeam Backup & Replication attempts to
resume the connection with an interval of 15 seconds during 30 minutes. If the problem has any other nature,
Veeam Backup & Replication retries the job in a regular manner.

Veeam Backup & Replication does not create a new restore point on resume: VM data is written to the same
restore point that was created for the current job session. When resuming the data transfer process,
Veeam Backup & Replication regards VM disks, not the whole VM.

For example, a VM has two disks: disk A and disk B. Before the connection dropped,
Veeam Backup & Replication managed to transfer 20 GB of disk A and did not start transferring disk B. After the
connection is re-established, Veeam Backup & Replication will start transferring the data for disk A from the 20
GB point; data of the whole disk B will be transferred anew.

1313 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Backup Jobs
To back up VMs, you must configure a backup job. The backup job defines how, where and when to back up VM
data. One job can be used to process one or more VMs. Jobs can be started manually or scheduled to run
automatically at a specific time.

Before you create a backup job, check prerequisites. Then use the New Backup Job wizard to configure the
backup job.

1314 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you create a backup job, check the following prerequisites:

• Check requirements and limitations in the VMs section in Platform Support.

• Backup infrastructure components that will take part in the backup process must be added to the backup
infrastructure and properly configured. These include Microsoft Hyper-V hosts on which VMs are located
and backup repository. If you want to perform backup in the off-host backup mode, the off-host backup
proxy must also be added to the backup infrastructure and properly configured.

• The backup repository must have enough free space to store created backup files. To receive alerts about
low space in the backup repository, configure global notification settings. For more information, see
Specifying Other Notification Settings.

• If you plan to enable guest processing for the job, check Guest Processing Requirements and Limitations.

• If you plan to map a backup job to a backup file that already exists in the backup repository, you must
perform the rescan operations for this backup repository. Otherwise, Veeam Backup & Replication will not
be able to recognize backup files in the backup repository. For more information, see Rescanning Backup
Repositories.

• If you plan to configure a secondary destination for the backup job, you can create a backup copy job or
backup to tape job beforehand. The backup copy job or backup to tape job can have an empty source, that
is, can be not linked to any backup job. For more information, see the Creating Backup Copy Jobs and
Creating Backup to Tape Jobs sections in the Veeam Backup & Replication User Guide.

• If you plan to use pre-job and post-job scripts and pre-freeze and post-thaw scripts, you must create
scripts before you configure the backup job.

• If you plan to periodically perform maintenance operations with backup files, consider the following
limitations: Health Check for Backup Files, Retention Policy for Deleted VMs, Compact of Full Backup File.

• [For Dell Data Domain backup repository] The length of forward incremental and forever forward
incremental backup chains that contain one full backup and a set of subsequent incremental backups
cannot be greater than 60 restore points. To overcome this limitation, schedule full backups (active or
synthetic) to split the backup chain into shorter series. For example, to perform backups at 30 -minute
intervals, 24 hours a day, you must schedule synthetic fulls every day. In this scenario, intervals
immediately after midnight may be skipped due to the duration of synthetic processing. For more
information, see How Synthetic Full Backup Works.

• If Microsoft Hyper-V Server 2016 or later is added along with hosts of lower versions to the same cluster,
Veeam Backup & Replication will not use new mechanisms (for example, online backup with checkpoints
and RCT for change block tracking) for VMs in this cluster. The new mechanisms will be used only after
you perform the following actions:

o Upgrade all nodes in the cluster to Microsoft Hyper-V Server 2016 or later

o Upgrade the cluster functional level

o Upgrade VM configuration version to 8.x

• Dynamic disks and FAT/FAT32 disks can be backed up only with disabled application-aware processing.

• If you plan to migrate VMs between hosts in the cluster or SCVMM, you will not have to reconfigure jobs
in Veeam Backup & Replication. Veeam Backup & Replication will automatically locate migrated VMs and
continue processing them as usual. If you migrate VMs between standalone hosts that are not a part of one
cluster or SCVMM server registered in Veeam Backup & Replication, you will have to reconfigure jobs to include
the migrated VMs. After that, Veeam Backup & Replication will create full backups for these VMs. If you do not
reconfigure the jobs, they will fail.

1315 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Job Wizard
To launch the New Backup Job wizard, do one of the following:

• On the Home tab, click Ba ckup Job > Virtual machine > Microsoft Hyper-V.

• Open the Home view. In the inventory pane, right-click Job s and select Ba ckup > Virtual machine >
Microsoft Hyper-V.

• Open the Inventory view, in the working area select the VMs, click Ad d to Backup on the ribbon and select
New job or right-click the VMs and select Ad d to Backup Job > New job. Veeam Backup & Replication will
start the New Backup Job wizard and add the VMs to this job. You can add other VMs to the job later on,
when you pass through the wizard steps.

• You can quickly add the VMs to an already existing job. To do this, open the Inventory view, in the working
area select the VMs and click Ad d to Backup > name of the job on the ribbon or right-click the VMs and
select Ad d to Backup Job > name of the job .

1316 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Na me step of the wizard, specify a name and description for the backup job.

1. In the Na me field, enter a name for the backup job.

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

3. Select the Hig h priority check box if you want the resource scheduler of Veeam Backup & Replication to
prioritize this job higher than other similar jobs and to allocate resources to it in the first place. For more
information on job priorities, see Job Priorities.

TIP

In the UI, jobs with the Hig h priority option enabled will be marked with a special flag ( ).

1317 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select VMs to Back Up
At the Virtual Machines step of the wizard, select VMs and VM containers (Hyper-V hosts, clusters, SCVMM,
SCVMM tags, SCVMM host groups, VM groups, or volumes) that you want to back up.

Jobs with VM containers are dynamic in their nature. If a new VM is added to the container in the virtual
infrastructure after the backup job is created, Veeam Backup & Replication will automatically update the job
settings to include the added VM.

1. Click Ad d .

2. Use the toolbar at the top right corner of the window to switch between views: Hosts and Clusters, Hosts
a nd Volumes, VMs and Tags, VM Groups.

Note that VMs can be arranged in VM groups only on Microsoft Hyper-V hosts version 2016 or later.

3. Select the VM or VM container in the list and click Ad d .

To quickly find the necessary object, you can use the search field at the bottom of the Ad d Objects window.

1. Click the button to the left of the search field and select the necessary type of object to search for:
Everything , Folder, Host Group , SCVMM, Cluster, Host or Virtual machine.

2. Enter the object name or a part of it in the search field.

3. Click the Sta rt search button on the right or press [Enter] on the keyboard.

The initial size of VMs and VM containers added to the backup job is displayed in the Size column in the list. The
total size of objects is displayed in the Tota l size field. Use the Recalculate button to refresh the total size value
after you add a new object to the job.

1318 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Exclude Objects from Backup Job
After you have added VMs and VM containers to the job, you can specify which objects you want to exclude
from the backup. You can exclude the following types of objects:

• VMs from VM containers

• Specific VM disks

To exclude VMs from a VM container:

1. At the Virtual Machines step of the wizard, click E x clusions.

2. Click the VMs tab.

3. Click Ad d .

4. Use the toolbar at the top right corner of the window to switch between views: Hosts and Clusters, Hosts
a nd Volumes, VMs and Tags, VM Groups.

Note that VMs can be arranged in VM groups only on Microsoft Hyper-V hosts version 2016 or later.

5. In the displayed tree, select the object and click Ad d . Use the Show full hierarchy check box to display the
hierarchy of all Microsoft Hyper-V Servers added to the backup infrastructure.

6. Click OK.

NOTE

Volumes on the dynamic disks must not be split. Spanned, striped and other types of split volumes cannot
be excluded.

To exclude VM disks from a backup:

1. At the Virtual Machines step of the wizard, click E x clusions.

2. Click the Disks tab.

3. Select the VM in the list and click E d it. If you want to exclude disks of a VM added as a part of the
container, click Ad d to include the VM in the list as a standalone object.

4. Choose disks that you want to back up. You can choose to process all disks, 0:0 disks (typically, system
disks) or add to the list custom IDE or SCSI disks.

1319 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you exclude disks from a backup and enable application-aware processing, Microsoft VSS framework will
still process the disks and volumes on which the disks are located.

1320 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Define VM Backup Order
You can define the order in which the backup job must process VMs. Setting VM order can be helpful, for
example, if you add some mission-critical VMs to the job and want the job to process them first. You can set
these VMs first in list to ensure that their processing fits the backup window.

VMs inside a VM container are processed at random. To ensure that VMs are processed in the defined order, you
must add them as standalone VMs, not as a part of the VM container.

To define VM backup order:

1. At the Virtual Machines step of the wizard, select a VM or VM container.

2. Use the Up and Down buttons on the right to move the VM or VM container up or down in the list.

NOTE

VMs may be processed in a different order. For example, if backup infrastructure resources for a VM that is
higher on the priority list are not available, and resources for a VM that is lower on the list are available,
Veeam Backup & Replication will start processing the VM that is lower on the list first.

If you enable the Allow processing of multiple VMs with a single volume snapshot option in the Advanced
Backup settings, VMs may also be processed in a different order. This option unites VMs added to the job in
several groups, and the defined VM order may be broken.

1321 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Backup Storage Settings
At the Storage step of the wizard, select backup infrastructure components for the job — backup proxy and
backup repository, and define backup storage settings.

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

o If you choose the On-host backup mode, the source Microsoft Hyper-V host will perform the roles of
the source host and backup proxy. In this mode, Veeam Data Mover runs directly on the source host,
which helps streamline data retrieval operations but puts additional load on the host.

If the job processes a VM whose disks are located on the CSV and Microsoft CSV Software Shadow
Copy Provider is used for snapshot creating, the Microsoft Hyper-V host owning the CSV will be used
as the on-host backup proxy.

o If you choose the Off-host backup mode, Veeam Data Mover will be started on a dedicated off-host
backup proxy. In this mode, all backup processing operations are shifted to the off -host backup proxy
from the source host.

By default, if the off-host backup mode is selected for the job but no off-host backup proxies are
available when the job starts, Veeam Backup & Replication will automatically fail over to the on-host
backup mode. To disable failover, clear the Fa ilover to on-host backup mode if no suitable off-host
p roxies available check box. If you disable this option, you must check off-host backup proxies before
the job starts. The job will not be able to start if off-host backup proxies are not available or are not
configured properly.

To perform off-host backup, Veeam Backup & Replication analyzes the current load on off-host
backup proxies and proxy settings (such as the number of allowed tasks, connectivity to the source
volumes) to select an appropriate off-host backup proxy for the job. You can also explicitly point out
what off-host backup proxies the job must use. To do this, select the Use the following backup proxy
servers only check box and choose one or several off-host backup proxies from the list. It is
recommended that you select at least two off-host backup proxies to ensure that the backup job
starts if one of the backup proxies fails or loses its connectivity to the source volumes.

2. From the Ba ckup repository list, select a backup repository where the created backup files must be stored.
When you select a backup repository, Veeam Backup & Replication automatically checks how much free
space is available in the backup repository.

NOTE

Consider the following:

• If you change the repository after the job has already run, Veeam Backup & Replication
suggests you to move the existing backups to the new repository. If you want to move the
backups, check limitation and considerations in Moving Backups.
• If you select an object storage repository or a scale-out backup repository which performance
tier consists of object storage repositories, Veeam Backup & Replication will not provide the
amount of free space in this repository since its capacity is constantly expanding.

3. You can map the job to a specific backup stored in the backup repository. Backup job mapping can be
helpful if you have moved backup files to a new backup repository and want to point the job to existing
backups in this new backup repository. You can also use backup job mapping if the configuration database
got corrupted and you need to reconfigure backup jobs.

To map the job to a backup, click the Ma p backup link and select the backup in the backup repository.
Backups can be easily identified by job names. To find the backup, you can also use the search field at the
bottom of the window.

1322 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Retention Policy field, specify retention policy settings for restore points:

o If you want to keep the last N restore points, select restore points from the drop-down list. Then
specify the number of restore points.

o If you want to keep all restore points created during the last N days, select days from the drop-down
list. Then specify the number of days.

When the specified number is exceeded, the earliest restore point is removed from the backup chain or
merged with the next closest restore point. For more information, see Short-Term Retention Policy.

5. If you want to archive backup files created by the backup job to a secondary destination (backup
repository or tape), select the Configure secondary destination for this job check box. With this option
enabled, the New Backup Job wizard will include an additional step — Secondary Target. At the Secondary
Ta rget step of the wizard, you can link the backup job to the backup copy job or backup to tape backup
job.

You can enable this option only if a backup copy job or backup to tape job is already configured on the
backup server.

1323 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Configure Long-Term Retention
If you want to ignore the short-term retention policy for some full backups and store them for long -term
archiving, you can configure GFS retention policy settings for the backup job. For more information on GFS and
its limitations, see Long-Term Retention Policy (GFS).

1. At the Storage step of the wizard, select the Keep some periodic full backups longer for archival purposes
check box.

2. Click Configure.

3. In the Configure GFS window, do the following:

o If you want to create weekly restore points, select the Keep weekly full backups for check box. Then
specify the number of weeks during which you want to prevent restore points from being modified
and deleted.

From the If multiple full backups exist, use the one from drop-down list, select a week day when
Veeam Backup & Replication must assign the weekly GFS flag to a full restore point.

o If you want to create monthly restore points, select the Keep monthly full backups for check box.
Then specify the number of months during which you want to prevent restore points from being
modified and deleted.

From the Use weekly full backup for the following week of a month drop-down list, select a week
when Veeam Backup & Replication must assign the monthly GFS flag to a full restore point. A week
equals 7 calendar days; for example, the first week of May is days 1–7, and the last week of May is
days 25–31.

o If you want to create yearly restore points, select the Keep y early full backups for check box. Then
specify the number of years during which you want to prevent restore points from being modified and
deleted.

From the Use monthly full backup for the following month drop-down list, select a month when
Veeam Backup & Replication must assign the yearly GFS flag to a full restore point.

o If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

NOTE

If you select to assign multiple types of GFS flags, the flags begin to depend on each other. For more
information on this dependency, see Assignment of Multiple GFS Flags.

1324 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1325 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Advanced Backup Settings
At the Storage step of the wizard, you can specify the advanced settings for the backup job:

• Backup settings

• Maintenance settings

• Storage settings

• Notification settings

• Hyper-V settings

• Script settings

TIP

After you specify necessary settings for the backup job, you can save them as default settings. To do this,
click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create a new
backup job, Veeam Backup & Replication will automatically apply the default settings to the new job.

Backup Settings
To specify settings for a backup chain created by the backup job:

1. At the Storage step of the wizard, click Ad vanced.

2. On the Ba ckup tab, select the backup method that you want to use to create the backup chain in the
backup repository:

o To create a reverse incremental backup chain, select Reverse Incremental.

IMP ORTANT

Consider the following:

• Dell Data Domain and HPE StoreOnce do not support the reverse incremental backup
method.
• Direct backup to object storage repositories does not support the reverse incremental
backup method.

o To create an incremental backup chain, select Incremental and enable synthetic full or active full
backups, or both (see items 3-4).

o To create a forever forward incremental backup chain, select Incremental. Also, check that synthetic
full and active full backups are disabled (see items 3-4).

For more information, see Backup Methods.

3. You can select to periodically create synthetic full backups if you choose the incremental backup method.
Select the Create synthetic full backups periodically on check box and click Configure to schedule
synthetic full backups on the necessary days of the week.

1326 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Consider the following:

• For backup jobs created in Veeam Backup & Replication version prior to 11, you could enable
the Tra nsform previous backup chains into rollbacks option. Starting from
Veeam Backup & Replication version 11, this option was deprecated and the feature could no
longer be selected in new jobs. However, jobs that were already using this feature will
continue to do so after upgrading to Veeam Backup & Replication 11. Starting from
Veeam Backup & Replication 12, this feature is fully deprecated, and the presence of any jobs
still using this feature blocks the upgrade to Veeam Backup & Replication 12. For more details,
see this Veeam KB article.
• Direct backup to object storage repositories does not support synthetic full backup method.

4. You can select to periodically create active full backups with any backup mode enabled. Select the Create
a ctive full backups p eriodically on check box and click Configure to define scheduling settings.

Before you schedule periodic full backups, you must make sure that you have enough free space in the
backup repository. As an alternative, you can create active full backups manually when needed. For more
information, see Active Full Backup.

5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

IMP ORTANT

Consider the following:

• If you schedule the active full backup and synthetic full backup on the same day,
Veeam Backup & Replication will perform only active full backup. Synthetic full backup will be
skipped.
• If you schedule a job to start after another job (initial job), but the initial job does not run on
days when the synthetic or active full backup is scheduled for the chained job,
Veeam Backup & Replication will not create active or synthetic full backups. For more
information on the job schedule options, see Define Job Schedule.

1327 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Maintenance Settings
You can instruct Veeam Backup & Replication to periodically perform the health check for the latest restore
point in the backup chain and maintenance operations to make sure that the backup chain remains valid and
consistent.

To specify the health check and maintenance settings, at the Storage step of the New Backup Job wizard, click
Ad vanced and click the Ma intenance tab.

Specifying Health Check Settings


To specify health check settings for the backup job:

1. In the Storage-level corruption guard section, select the P erform backup files health check check box and
specify the time schedule for the health check. By default, if the health check is enabled, it is performed
monthly at 5:00 AM every last Saturday (at 10:00 PM every last Friday- for version 12).

2. To specify the health check schedule, click the Configure link.

3. In the Schedule Settings window, specify whether you want to perform the health check monthly or
weekly and specify the schedule settings.

Specifying Backup File Maintenance


To specify maintenance settings for the backup job:

1. To specify retention period for deleted VMs, select the Remove deleted items data after check box and
specify the number of days for which you want to keep backup data for deleted VMs.

NOTE

Consider the following:

• If a VM is no longer available (for example, it was deleted or excluded from the job),
Veeam Backup & Replication will keep its data in the backup repository for the period that you
have specified. When this period is over, data of the deleted VM will be r emoved from the
backup repository.
• By default, the retention period for deleted VM data is 14 days. It is strongly recommended
that you set the retention period to 3 days or more to prevent unwanted data loss. For more
information, see Retention Policy for Deleted VMs.

2. To periodically compact a full backup, select the Defragment and compact full backup file check box.

IMP ORTANT

Consider the following:

• Direct backup to object storage repositories does not support the Defragment and compact
full backup file option.
• The HPE StoreOnce backup repository does not support the Defragment and compact full
b a ckup file option

3. To specify the schedule for the compact operation, click the Configure link.

4. In the Schedule Settings window, specify whether you want to compact a full backup monthly or weekly
and specify the schedule settings.

1328 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

IMP ORTANT

If you schedule periodic full backups, the Remove deleted items data after and Defragment and compact
full backup file check boxes do not apply.

Storage Settings
To specify storage settings for the backup job:

1. At the Storage step of the wizard, click Ad vanced.

2. Click the Storage tab.

3. By default, Veeam Backup & Replication deduplicates VM data before storing it in the backup repository.
Data deduplication provides a smaller size of the backup file but may reduce the backup job performance.
For more information on data deduplication, see Deduplication.

To disable data deduplication, clear the E na ble inline data deduplication check box. If you disable this
option, you also change the workflow of incremental backup. If Changed Block Tracking is enabled for the
job, Veeam Backup & Replication will save all data blocks marked by CBT as new to the destination storage
without performing an additional check or using Veeam’s filtering mechanism. This will result in faster
incremental backup. For more information, see Changed Block Tracking.

NOTE

The option that allows you to enable or disable data deduplication is not available for an object storage
repository due to its underlying functionality. The backup to object storage applies various improvements
to optimize storage consumption and make the backup process faster.

If you have selected such a repository at the Storage step of the wizard, the E nable inline data
d ed uplication check box will not be displayed.

1329 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. By default, Veeam Backup & Replication checks the NTFS MFT file on VMs with Microsoft Windows OS to
identify data blocks of the hiberfil.sys file (file used for the hibernate mode) and pagefile.sys file
(swap file), and excludes these data blocks from processing. The swap file is dynamic in nature and
changes intensively between backup job sessions, even if the VM itself does not change much. Processing
of service files reduces the job performance and increases the size of incremental backup files.

If you want to include data blocks of the hiberfil.sys file and pagefile.sys file to the backup, clear the
E x clude swap file blocks check box. For more information, see Swap Files.

5. By default, Veeam Backup & Replication does not copy deleted file blocks ("dirty" blocks on the VM guest
OS) to the target location. This option lets you reduce the size of backup files and increase the job
performance. If you want to include dirty data blocks to the backup, clear the E x clude deleted file blocks
check box. For more information, see Deleted File Blocks.

6. From the Compression level 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. In the Storage optimization section, select block size that will be used to process VMs. For more
information on the data blocks sizes and how they affect performance, see Storage Optimization.

8. To encrypt the content of backup files, select the E na ble backup file encryption check box. In the
P a ssword field, select a password that you want to use for encryption. If you have not created the
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For more
information, see Managing Passwords for Data Encryption.

If the backup server is not connected to Veeam Backup Enterprise Manager, you will not be able to restore
data from encrypted backups in case you lose the password. Veeam Backup & Replication will display a
warning about it. For more information, see Decrypting Data Without Password.

9. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

NOTE

If you enable encryption for an existing backup job, during the next job session
Veeam Backup & Replication will create a full backup file. The created full backup file and subsequent
incremental backup files in the backup chain will be encrypted with the specified password.

Encryption is not retroactive. If you enable encryption for an existing job, Veeam Backup & Replication
does not encrypt the previous backup chain created by this job. If you want to start a new chain so that the
unencrypted previous chain can be separated from the encrypted new chain, see this Veeam KB article.

1330 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Notification Settings
To specify notification settings for the backup job:

1. At the Storage step of the wizard, click Ad vanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully.

SNMP traps will be sent if you specify global SNMP settings in Veeam Backup & Replication and configure
software on recipient's machine to receive SNMP traps. For more information, see Specifying SNMP
Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications about the job completion status by email. In the field below, specify recipient’s email
address. You can enter several addresses separated by a semicolon.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Configuring Global Email Notification Settings.

5. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for the job, select Use custom notification settings specified below
check box. You can specify the following notification settings:

i. In the Subject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %VmCount% (number of
VMs in the job) and %Issues% (number of VMs in the job that have been processed with the
Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive
email notification if the job completes successfully, fails or completes with a warning.

1331 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
iii. Select the Sup press notifications until the last retry check box to receive a notification about
the final job status. If you do not enable this option, Veeam Backup & Replication will send
one notification per every job retry.

6. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Hyper-V Settings
To specify Hyper-V settings for the backup job:

1. At the Storage step of the wizard, click Ad vanced.

2. Click the Hyper-V tab.

3. In the Guest quiescence section, specify which backup method must be used to prepare the VM guest OS
for backup.

Typically, it is recommended that you use Veeam's application-aware processing that leverages the
Microsoft VSS framework to prepare the VM guest OS for backup. If application-aware processing cannot
be used for some reason, select the E na ble Hyper-V guest quiescence check box.
Veeam Backup & Replication will select the backup method in the following way:

o If a VM meets all requirements for online backup, Veeam Backup & Replication will use the online
backup method.

o If a VM does not meet requirements for online backup, Veeam Backup & Replication will use the
offline backup method. Note that during offline backup a VM is suspended for a short period of time.

The selected backup method applies to all VMs in the job. However, if you enable application-aware
processing for VMs, the application-aware processing settings will have higher priority than the selected
backup method.

1332 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

For VMs on Microsoft Hyper-V Server 2016 and later, consider the following:

• Offline backup cannot be used.


• If you enable Hyper-V guest quiescence and leave application-aware processing disabled in
the job, Veeam Backup & Replication performs backup using the VSS_BT_FULL method. This
method backs up databases and transaction logs and then truncates the transaction logs. For
more information on backup methods, see this Microsoft Documentation.
You can change the backup method to VSS_BT_COPY with a registry value. For more
information, contact Veeam Customer Support.

4. If you do not want to suspend VMs in the job, select the Ta k e crash consistent backup instead of
suspending VM check box. In this case, Veeam Backup & Replication will create a crash-consistent backup
of a VM.

5. In the Cha nged block tracking section, specify if CBT must be used for VM backup. By default, this option
is enabled. CBT dramatically reduces load on the production environment and time required to perform
incremental backups.

6. If you have added several VMs to the job, select the Allow processing of multiple VMs with a single
volume snapshot check box. This option helps reduce snapshot workload in the Microsoft Hyper -V
environment. When the job starts, Veeam Backup & Replication will group VMs and trigger Microsoft
Hyper-V to create one volume snapshot for a group of VMs, instead of creating a volume snapshot per
each processed VM.

Veeam Backup & Replication can create a single volume snapshot for a group of VMs that meet the
following requirements:

o VMs must be located on the same host.

o Volumes on which VM files reside must use the same VSS provider for snapshot creation.

o The number of VMs in the group is limited: for a software VSS provider — 4 VMs, for a hardware VSS
provider — 8 VMs.

o Veeam Backup & Replication groups VMs based on the method of snapshot creation that is used for
backup: transactionally consistent (VSS) or crash-consistent.

For example, you add to the job 2 VMs that are registered on the same host. VM1 resides on volume C:\
and VM2 resides on volume D:\. Both VMs use Microsoft Software Shadow Copy Provider. In this
situation, Veeam Backup & Replication will create a single snapshot for these VMs.

NOTE

The Allow processing of multiple VMs with a single volume snapshot option is not applicable to VMs
registered on Microsoft Hyper-V Server 2016 and later that are processed in the onhost backup
mode.

1333 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
7. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Script Settings
To specify script settings for the backup job:

1. At the Storage step of the wizard, click Ad vanced.

2. Click the Scripts tab.

3. If you want to execute custom scripts before and after the backup job, select the Run the following script
b efore the job and Run the following script after the job check boxes and click Browse to choose
executable files from a local folder on the backup server. The scripts are executed on the backup server.

You can select to execute pre- and post-backup actions after a number of backup sessions or on specific
week days.

o If you select the Run scripts every <N> backup session option, specify the number of the backup job
sessions after which the scripts must be executed.

o If you select the Run scripts on the selected days only option, click Da y s and specify week days on
which the scripts must be executed.

NOTE

Consider the following:

• Custom scripts that you define in the advanced job settings relate to the backup job itself, not the
VM quiescence process. To add pre-freeze and post-thaw scripts for VM image quiescence, use the
Guest Processing step of the wizard.
• If you select the Run scripts on the selected days only option, Veeam Backup & Replication executes
scripts only once on each selected day — when the job runs for the first time. During subsequent job
runs, scripts are not executed.
• To run the script, Veeam Backup & Replication uses the Service Account under which the Veeam
Backup Service is running.

1334 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1335 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Secondary Target
The Secondary Target step of the wizard is available if you have enabled the Configure secondary destination for
this job option at the Storage step of the wizard.

At the Secondary Target step of the wizard, you can link the backup job to a backup to tape or backup copy job.
As a result, the backup job will be used as a source for the backup to tape or backup copy job. Backup files
created by the backup job will be archived to tape or copied to the secondary backup repository according to the
secondary jobs schedule. For more information, see the Linking Backup Jobs to Backup Copy Jobs and Linking
Backup Jobs to Backup to Tape Jobs sections in the Veeam Backup & Replication User Guide.

The backup to tape job or backup copy job must be configured beforehand. You can create these jobs with an
empty source. When you link the backup job to these jobs, Veeam Backup & Replication will automatically
update the linked jobs to define the backup job as a source for these jobs.

To link jobs:

1. Click Ad d .

2. From the jobs list, select a backup to tape or backup copy job that must be linked to the backup job. You
can link several jobs to the backup job, for example, one backup to tape job and one backup copy job. To
quickly find the job, use the search field at the bottom of the wizard.

1336 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Specify Guest Processing Settings
At the Guest Processing step of the wizard, you can enable the following settings:

• E na ble application-aware processing — to create a transactionally consistent backup of VMs running VSS-
aware applications. The transactionally consistent backup guarantees proper recovery of applications on
VMs without data loss. For details on application-aware processing settings, see Application-Aware
Processing.

• E na ble guest file system indexing — to create a catalog of files located on the guest OS. The catalog
allows you to browse, search and perform 1-click restores of individual files. For more information, see the
Preparing for File Browsing and Searching section in the Enterprise Manager User Guide. For details on
guest OS file indexing settings, see VM Guest OS File Indexing.

• Guest interaction proxy — to specify interaction proxy settings that Veeam Backup & Replication will use
to install non-persistent runtime components or use (if necessary, install) persistent agent components in
each VM.

• Guest OS credentials — that allow Veeam Backup & Replication connect to the VM guest OS.

To specify interaction proxy settings and credentials, do the following:

1. [Only for Microsoft Windows VMs] To connect a backup server to processed VM guest OS, specify the
guest interaction proxy. On the right of the Guest interaction proxy field, click Choose and select one of
the following:

o Leave Automatic selection to let Veeam Backup & Replication automatically select the guest
interaction proxy.

o Select Use the selected guest interaction proxy servers only to explicitly define which servers will
perform the guest interaction proxy role. The list of servers contains Microsoft Windows servers
added to the backup infrastructure.

NOTE

The guest interaction proxy functionality is included in the Veeam Universal License. If you use the
legacy socket-based license, you will require Enterprise or higher edition.

2. To specify a user account that will be used to that to connect to the VM guest OS, from the Guest OS
credentials drop-down list, select a user account that has enough permissions. For more information on
the permissions and requirements for the user account, see Permissions for Guest Processing.

If you install persistent agent components for VMs running Linux operating systems, select Use
management agent credentials from the list. For more information, see Installing Persistent Agent
Components on Linux VMs.

NOTE

Management Agent credentials have root or elevated to root permissions. If you do not want to
perform guest processing tasks under the account with such privileges, you can specify a non-root
user account. This account or custom credentials added for specific VMs will also be used for SSH
connection or networkless guest processing over PowerShell Direct if a network connection over
transport service fails.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add credentials. For more information on adding credentials, see the Credentials Manager section.

1337 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, Veeam Backup & Replication uses the Log on as a batch job policy to connect to guest OS. If
the connection fails, Veeam Backup & Replication switches to Interactive Logon.

NOTE

If you use Kerberos authentication, consider requirements and limitations described in section
Kerberos Authentication.

2. By default, Veeam Backup & Replication uses the same credentials for all VMs in the job. If some VM
requires a different user account, click Credentials and enter custom credentials for the VM.

3. To check if Veeam Backup & Replication can communicate with VMs added to the job, click Test Now.
Veeam Backup & Replication will use the specified credentials to connect to all VMs in the list.

Application-Aware Processing
To create transactionally consistent backups of VMs, you must enable application-aware processing.
Application-aware processing allows you to define the method to process applications, application logs and
select if you want to use the persistent agent.

To enable application-aware processing, at the Guest Processing step of the wizard select the E na ble
a p plication-aware processing check box and click Ap p lications.

After that, define general application-aware processing settings:

1. In the Ap p lication-Aware Processing Options window, select the VM and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM to the list
as a standalone object. To do this, click Ad d and choose the VM whose settings you want to customize.
Then select the VM in the list and define the necessary settings.

2. To specify the behavior scenario for application-aware processing, on the General tab, in the Ap p lications
section do one of the following:

o If you want Veeam Backup & Replication to stop the backup process when an error occurs during
application-aware processing, select Require successful processing.

o If you want to continue the backup process when an error occurs during application-aware processing,
select Try application processing, but ignore failures . This option guarantees completion of the
backup job. In this case, Veeam Backup & Replication will create a crash consistent backup instead of
transactionally consistent backup.

1338 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

If application-aware processing fails, the backup job will not process SQL transaction logs until
Veeam Backup & Replication creates a new image-level backup of the Microsoft SQL Server VM.

o If you do not want to enable application-aware processing for the VM, select Disable application
p rocessing.

3. If you want Veeam Backup & Replication to process application logs or create copy-only backups, in the
VSS Settings section do one of the following:

o [For Microsoft Exchange and Microsoft SQL VMs] If you want Veeam Backup & Replication to process
application logs, select P rocess transaction logs with this job and specify settings on the SQL tab. For
more information, see Microsoft SQL Server Transaction Log Settings.

NOTE

[For Microsoft Exchange VMs] If you select this option, Veeam Backup & Replication will back
up the Exchange database and its logs. The non-persistent runtime components or persistent
components that run on the VM guest OS will wait for a backup job to complete successfully.
After that, they will trigger truncation of transaction logs on a Microsoft Exchange server. If the
backup job fails, the logs on this server will remain untouched.

o [For Microsoft Exchange and Microsoft SQL VMs] If you use a third -party tool backup tool to perform
VM guest level backup, and this tool maintains consistency of the database state, select P erform copy
only . Veeam Backup & Replication will create a copy-only backup for the selected VM. The copy-only
backup preserves the chain of full or differential backup files and transaction logs on the VM. For
more information, see Microsoft Docs.

Note that if you select this option, the SQL tab will not be available in the P rocessing Settings
window.

o [For Oracle VMs and PostgreSQL VMs] You must specify settings for application log handling on the
Ora cle and P ostgreSQL tabs of the VM P rocessing Settings window. For more information, see Oracle
Archived Log Settings and PostgreSQL WAL Files Settings.

4. If you want Veeam Backup & Replication to use persistent guest agents on each protected VM for
application-aware processing, select the P ersistent guest agent check box.

For more information, see Persistent Agent Components.

IMP ORTANT

If both Microsoft SQL Server and Oracle Server are installed on one VM, and this VM is processed by a job
with log backup enabled for both applications, Veeam Backup & Replication will back up only Oracle
transaction logs. Microsoft SQL Server transaction logs will not be processed.

1339 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Microsoft SQL Server Transaction Log Settings
To create a transactionally consistent backups of SQL VM, you must enable application-aware processing and
define settings of transaction logs processing.

Enabling Application-Aware Processing


Before configuring transaction logs processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the SQL VM and click E d it.

By default, the P rocessing Settings window will display the General tab. In the VSS Settings section, select
P rocess transaction logs wit h this job. For more information, see VSS settings.

Specifying Transaction Logs Settings


To define how Veeam Backup & Replication will process transaction logs on this VM, specify the following
settings:

1. In the P rocessing Settings window, click the SQL tab.

2. Specify how transaction logs must be processed. You can select one of the following options:

o Select Truncate logs to truncate transaction logs after successful backup. The non-persistent runtime
components or persistent components running on the VM guest OS will wait for the backup to
complete successfully and then truncate transaction logs. If the job does not manage to back up the
Microsoft SQL Server VM, the logs will remain untouched on the VM guest OS until the next start of
the non-persistent runtime components or persistent components.

1340 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If the account specified at the Guest Processing step does not have enough rights,
Veeam Backup & Replication tries to truncate logs using the local SYSTEM account for Microsoft
SQL Server 2008 and 2008 R2. For other Microsoft SQL Server versions,
Veeam Backup & Replication uses NT AUTHORITY\SYSTEM account.

Make sure that these accounts have permissions listed in section Permissions for Guest
Processing.

o Select Do not truncate logs to preserve transaction logs. When the backup job completes,
Veeam Backup & Replication will not truncate transaction logs on the Microsoft SQL Server VM.

It is recommended that you enable this option for databases that use the Simple recovery model. If
you enable this option for databases that use the Full or Bulk-logged recovery model, transaction logs
on the VM guest OS may grow large and consume all disk space. In this case, the database
administrators must take care of transaction logs themselves.

o Select Ba ckup logs periodically to back up transaction logs with Veeam Backup & Replication.
Veeam Backup & Replication will periodically copy transaction logs to the backup repository and store
them together with the image-level backup of the Microsoft SQL Server VM. During the backup job
session, transaction logs on the VM guest OS will be truncated.

For more information, see Microsoft SQL Server Log Backup.

If you have selected to back up transaction logs with Veeam Backup & Replication, you must specify settings for
transaction log backup:

1. In the Ba ckup logs every <N> minutes field, specify the frequency for transaction log backup. By default,
transaction logs are backed up every 15 minutes. The maximum log backup interval is 480 minutes.

2. In the Retain log backups section, specify retention policy for transaction logs stored in the backup
repository.

o Select Until the corresponding image-level backup is deleted to apply the same retention policy for
image-level backups and transaction log backups.

o Select Keep only last <N> days of log backups to keep transaction logs for a specific number of days.
By default, transaction logs are kept for 15 days. If you select this option, you must make sure that
retention for transaction logs is not greater than retention for the image-level backups. For more
information, see Retention for Transaction Log Backups.

3. In the Log shipping servers section, click Choose to select what log shipping server you want to use to
transport transaction logs:

o Select Automatic selection if you want Veeam Backup & Replication to choose an optimal log shipping
server automatically. If the optimal shipping server is busy, Veeam Backup & Replication will direct
the data flow to another shipping server not to lose da ta and to comply with RPO. The process of
transaction logs shipment does not require a dedicated server — Veeam Backup & Replication can use
any Microsoft Windows server added to the backup infrastructure.

o To define a log shipping server explicitly, select Use the specified servers only and select check boxes
next to servers that you want to use as log shipping servers. The server list includes all Microsoft
Windows servers added to the backup infrastructure.

Make sure that you select a server that is not engaged in other resource-consuming tasks. For
example, you may want not to use a server that performs the WAN accelerator role as a log shipping
server. For load balance and high availability purposes, it is recommended that you select at least 2
log shipping servers.

1341 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Veeam Backup & Replication automatically excludes its configuration database from application-aware
processing during backup if the database is hosted without using SQL Server Always On Availability Group.
Transaction logs for the configuration database are not backed up. If the Veeam Backup & Replication
configuration database is hosted using SQL Server Always On Availability Group, you should manually
exclude this database from application-aware processing during backup as described in this Veeam KB
article. Otherwise, job processing will fail with the following error: Failed to freeze guest over network,
wait timeout.

Oracle Archived Log Settings


To create a transactionally consistent backups of a VM where Oracle Database is deployed, you must you must
enable application-aware processing and define how Veeam Backup & Replication> will process archived redo
logs on this VM.

Enabling Application-Aware Processing


Before configuring transaction logs processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the Oracle VM and click E d it.

Specifying Archive Redo Logs Settings


1. In the VM P rocessing Settings window, click the Ora cle tab.

1342 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the Sp ecify Oracle account with SYSDBA privileges section, specify a user account that
Veeam Backup & Replication will use to connect to the Oracle database. The account must have privileges
for the Oracle database listed in section Permissions for Guest Processing.

You can select Use guest credentials in the list of user accounts. In this case, Veeam Backup & Replication
will use the account specified at the Guest Processing step of the wizard to access the VM guest OS and
connect to the Oracle database.

NOTE

[For Windows-based machines] Make sure that you add the %ORACLE_HOME%\bin variable to the
environmental path variable on the machine with your Oracle database.

3. In the Archived logs section, specify how Veeam Backup & Replication must process archived redo logs on
the Oracle VM:

o Select Do not d elete archived logs if you want Veeam Backup & Replication to preserve archived logs
on the VM guest OS. When the backup job completes, the non-persistent runtime components or
persistent components will not delete archived logs.

It is recommended that you select this option for databases in the NOARCHIVELOG mode. If the
database is in the ARCHIVELOG mode, archived logs on the VM guest OS may grow large and consume
all disk space. In this case, database administrators must take care of archived logs themselves.

o Select Delete logs older than < N> hours or Delete logs over <N> GB if you want
Veeam Backup & Replication to delete archived logs that are older than <N> hours or larger than <N>
GB. The log size threshold refers not to the total size of all logs for all databases, but to the log size
of each database on the selected Oracle VM.

When the parent backup job (job creating an image-level backup) runs, Veeam Backup & Replication
will wait for the backup to complete successfully, and then trigger archived logs deletion on the
Oracle VM over Oracle Call Interface (OCI). If the primary job does not manage to back up the Oracle
VM, the logs will remain untouched on the VM guest OS until the next start of the non-persistent
runtime components or persistent components.

4. To back up Oracle archived logs with Veeam Backup & Replication, select the Ba ckup log every <N>
minutes check box and specify the frequency for archived log backup. By default, archived logs are backed
up every 15 minutes. The maximum log backup interval is 480 minutes.

5. In the Retain log backups section, specify retention policy for archived logs stored in the backup
repository:

o Select Until the corresponding image-level backup is deleted to apply the same retention policy for
image-level backups and archived log backups.

o Select Keep only last <n> days to keep archived logs for a specific number of days. By default,
archived logs are kept for 15 days. If you select this option, you must make sure that retention for
archived logs is not greater than retention for the image-level backups. For more information, see
Retention for Archived Log Backups.

6. In the Log shipping servers section, click Choose to select what log shipping server you want to use to
transport archived logs:

o Select Automatic selection if you want Veeam Backup & Replication to select an optimal log shipping
server automatically. The process of archived logs shipment does not require a dedicated server —
Veeam Backup & Replication can use any Microsoft Windows server added to the backup
infrastructure.

1343 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Use the specified servers only to define a log shipping server explicitly. In the Log Shipping
Servers window, select check boxes next to servers that you want to use as log shipping servers. The
server list includes all Microsoft Windows servers added to the backup infrastructure.

Make sure that you select a server that is not engaged in other resource-consuming tasks. For
example, you may want not to use a server that performs the WAN accelerator role as a log shipping
server. For load balance and high availability purposes, it is recommended that y ou select at least 2
log shipping servers.

PostgreSQL WAL Files Settings


To create a transactionally consistent backups of PostgreSQL VM, you must enable application-aware processing
and define settings of WAL files processing.

Enabling Application-Aware Processing


Before configuring WAL files processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the PostgreSQL VM and click E d it.

Specifying WAL Files Settings


To define how Veeam Backup & Replication will process WAL files on this VM, do the following:

1. In the P rocessing Settings window, click the P ostgreSQL tab.

1344 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. From the Sp ecify PostgreSQL account with superuser privileges drop-down list, select a user account that
Veeam Backup & Replication will use to connect to the PostgreSQL instance. The account must have must
have privileges described in section Permissions. If you have not set up credentials beforehand, click the
Ma nage accounts link or click Ad d on the right to add credentials.

By default, the Use guest credentials option is selected in the list. With this option selected,
Veeam Backup & Replication will connect to the PostgreSQL instance under the account In this case,
Veeam Backup & Replication will use the account specified at the Guest Processing step of the wizard to
access the VM guest OS and connect to the PostgreSQL instance.

Note that if you plan to select the Sy stem user without password file (peer) authentication method at the
step 3 of this procedure, you can add a user account in the Credentials Manager without specifying the
password for the account.

3. In the Sp ecifies user is section, specify how the user will authenticate against the PostgreSQL instance:

o Select Da tabase user with password if the account that you specified at the step 2 is a PostgreSQL
account, and you entered the password for this account in the Credentials Manager.

o Select Da tabase user with password file (.pgpass) if the password for the account that you specified
at the step 2 is defined in the .pgpass configuration file on the PostgreSQL VM. For more
information about the password file, see PostgreSQL documentation.

o Select Sy stem user without password file (peer) if you want Veeam Backup & Replication to use the
peer authentication method. In this case, Veeam Backup & Replication will use the OS account as the
PostgreSQL account. For more information about the peer authentication method, see PostgreSQL
documentation.

IMP ORTANT

If you have added a new PostgreSQL account and want to use it with the peer authentication
method, make sure that you have added this account as a Linux user with sufficient permissions.

4. To back up PostgreSQL WAL files with Veeam Backup & Replication, select the Ba ck up log every <N>
minutes check box and specify the frequency for WAL files backup. By default, WAL files are backed up
every 15 minutes. The maximum log backup interval is 480 minutes.

5. In the Retain log backups section, specify retention policy for WAL files stored in the backup repository:

o Select Until the corresponding image-level backup is deleted to apply the same retention policy for
both image-level backups and WAL files backups.

o Select Keep only last <n> days to keep WAL files for a specific number of days. By default, WAL files
are kept for 15 days. If you select this option, you must make sure that retention for WAL files is not
greater than retention for the image-level backups. For more information, see Retention for
PostgreSQL WAL Files.

6. In the Temp orary location for archive logs (Staging location for archive logs - for version 12) section
specify a path to the storage location, where you want to keep WAL files.

7. In the Log shipping servers section, click Choose to select what log shipping server you want to use to
transport WAL files:

o Select Automatic selection if you want Veeam Backup & Replication to select an optimal log shipping
server automatically. The process of WAL files shipment does not require a dedicated server —
Veeam Backup & Replication can use any Microsoft Windows server added to the backup
infrastructure.

1345 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Use the specified servers only to define a log shipping server explicitly. In the Log Shipping
Servers window, select check boxes next to servers that you want to use as log shipping servers. The
server list includes all Microsoft Windows servers added to the backup infrastructure.

Make sure that you select a server that is not used by other resource-consuming tasks. For example,
you may want not to use a server that performs the WAN accelerator role as a log shipping server. For
load balance and high availability purposes, it is recommended that you select at least 2 log shipping
servers.

VM Guest OS File Exclusion


If you do not want to back up specific files and folders on the VM guest OS, you can exclude them from the
backup.

NOTE

VM guest OS file exclusion functionality is included in the Veeam Universal License. When using a legacy
socket-based license, Enterprise or higher edition is required.

To define what files and folders must be excluded:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the VM and click E d it.

To define custom settings for a VM added as part of a VM container, you must include the VM in the list as
a standalone object. To do this, click Ad d and choose a VM whose settings you want to customize. Then
select the VM in the list and define the necessary settings.

4. Click the E x clusions tab and specify what files must be excluded from the backup:

o Select E x clude the following files a nd folders to remove the individual files and folders from the
backup.

o Select Include only the following files and folders to leave only the specified files and folders in the
backup.

1346 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Click Ad d and specify what files and folders you want to include or exclude. To form the list of exclusions
or inclusions, you can use full paths to files and folders, environmental variables and file masks with the
asterisk (*) and question mark (?) characters. For more information, see VM Guest OS Files.

NOTE

When you choose files to be included or excluded, consider requirements and limitations that are listed in
section Requirements and Limitations for VM Guest OS File Exclusion.

6. Click OK.

7. Repeat steps 5-6 for every file or folder that you want to exclude or include.

NOTE

Volumes on the dynamic disks must not be split. Spanned, striped and other types of split volumes cannot
be excluded.

Pre-Freeze and Post-Thaw Scripts


If you plan to back up VMs running applications that do not support VSS, you can specify what scripts
Veeam Backup & Replication must use to quiesce the VM. The pre-freeze script quiesces the VM file system and
application data to bring the VM to a consistent state before Veeam Backup & Replication triggers a VM
snapshot. After the VM snapshot is created, the post-thaw script brings the VM and applications to their initial
state.

To specify pre-freeze and post-thaw scripts for the job:

1. At the Guest Processing step, click Ap p lications.

2. In the displayed list, select the VM and click E d it.

3. Click the Scripts tab.

4. In the Script processing mode section, specify the scenario for scripts execution:

o Select Require successful script execution if you want Veeam Backup & Replication to stop the backup
process if the script fails.

1347 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Ig nore script execution failures if you want to continue the backup process even if script errors
occur.

o Select Disable script execution if you do not want to run scripts for the VM.

5. In the W indows scripts section, specify paths to pre-freeze and post-thaw scripts for Microsoft Windows
VMs. For the list of supported script formats, see Pre-Freeze and Post-Thaw Scripts.

6. In the Linux scripts section, specify paths to pre-freeze and post-thaw scripts for Linux VMs. For the list of
supported script formats, see Pre-Freeze and Post-Thaw Scripts.

If you have added to the job a VM container with Microsoft Windows and Linux VMs, you can select to
execute both Microsoft Windows and Linux scripts for the VM container. When the job starts,
Veeam Backup & Replication will automatically determine what OS type is installed on the VM and use
correct scripts to quiesce this VM.

TIP

Beside pre-freeze and post-thaw scripts for VM quiescence, you can instruct Veeam Backup & Replication
to run custom scripts before the job starts and after the job completes. For more information, see Script
Settings.

VM Guest OS File Indexing


To specify VM guest OS indexing options for a VM:

1. At the Guest Processing step of the wizard, click Ind exing.

2. Select a VM in the list and click E d it > W indows indexing or Linux indexing.

3. Specify the indexing scope:

o Select Disable indexing if you do not want to index guest OS files of the VM.

o Select Ind ex everything if you want to index all VM guest OS files.

1348 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Ind ex everything except if you want to index all VM guest OS files except those defined in the
list. By default, system folders are excluded from indexing. You can add or delete folders using the
Ad d and Remove buttons on the right. You can also use system environment variables to form the list,
for example: %windir%, %ProgramFiles% and %Temp%.

To reset the list of folders to its initial state, click Default.

o Select Ind ex only following folders to define folders that you want to index. You can add or delete
folders to index using the Ad d and Remove buttons on the right. You can also use system
environment variables to form the list, for example: %windir%, %ProgramFiles% and %Temp%.

NOTE

[For Linux VMs] To perform guest OS file indexing, Veeam Backup & Replication requires several utilities to
be installed on the Linux VM: openssh, gzip and tar. If these utilities are not found,
Veeam Backup & Replication will prompt you to deploy them on the VM guest OS.

1349 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Define Job Schedule
At the Schedule step of the wizard, select to run the backup job manually or schedule the job to run on a regular
basis.

To specify the job schedule:

1. Select the Run the job automatically check box. If this check box is not selected, you will have to start the
job manually to create the VM backup.

2. Define scheduling settings for the job:

o To run the job at specific time daily, on defined week days or with specific periodicity, select Da ily at
this time. Use the fields on the right to configure the necessary schedule.

o To run the job once a month on specific days, select Monthly at this time. Use the fields on the right
to configure the necessary schedule.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for
example, related to daylight saving time transition).

o To run the job repeatedly throughout a day with a specific time interval, select P eriodically every. In
the field on the right, select the necessary time unit: Hours or Minutes. Click Schedule and use the
time table to define the permitted time window for the job. In the Sta rt time within an hour field,
specify the exact time when the job must start.

A repeatedly run job is started by the following rules:

▪ Veeam Backup & Replication always starts counting defined intervals from 12:00 AM. For
example, if you configure to run a job with a 4-hour interval, the job will start at 12:00 AM, 4:00
AM, 8:00 AM, 12:00 PM, 4:00 PM and so on.

▪ If you define permitted hours for the job, after the denied interval is over,
Veeam Backup & Replication will immediately start the job and then run the job by the defined
schedule.

For example, you have configured a job to run with a 2-hour interval and defined permitted hours
from 9:00 AM to 5:00 PM. According to the rules above, the job will first run at 9:00 AM, when the
denied period is over. After that, the job will run at 10:00 AM, 12:00 PM, 2:00 PM and 4:00 PM.

o To run the job continuously, select the P eriodically every option and choose Continuously from the
list on the right. A new backup job session will start as soon as the previous backup job session
finishes.

o To chain jobs, use the After this job field. In the common practice, jobs start one after another: when
job A finishes, job B starts and so on. If you want to create a chain of jobs, you must define the time
schedule for the first job in the chain. For the rest of the jobs in the chain, select the After this job
op tion and choose the preceding job from the list.

Note that chained jobs have some drawbacks and limitations. For more information, see Chained Jobs.

3. In the Automatic retry section, define whether Veeam Backup & Replication must attempt to run the
backup job again if the job fails for some reason. During a job retry, Veeam Backup & Replication processes
failed VMs only. Enter the number of attempts to run the job and define time intervals between them. If
you select continuous backup, Veeam Backup & Replication will retry the job for the defined number of
times without any time intervals between the job sessions.

1350 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ba ckup window section, define the time interval within which the backup job must complete. The
backup window prevents the job from overlapping with production hours and ensures that the job does
not provide unwanted overhead on the production environment. To set up a backup window for the job:

a. Select the Terminate job if it exceeds allowed backup window check box and click W ind ow.

b. In the Time P eriods window, define the allowed hours and prohibited hours for backup. If the job
exceeds the allowed window, it will be automatically terminated.

NOTE

The After this job function will only start a job if the first job in the chain is started automatically by
schedule. If the first job is started manually, jobs chained to it will not be started.

1351 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of backup job configuration.

1. Review details of the backup job.

2. Select the Run the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

1352 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Performing Active Full Backup
You can create an ad-hoc full backup — active full backup, and add it to the backup chain in the backup
repository. The active full backup resets the backup chain. All subsequent incremental backups use the active
full backup as a starting point. The previously used full backup will remain in the backup repository until it is
removed from the backup chain according to the retention policy.

Performing Active Full Backup for All Workloads


To perform active full backup for all workloads in 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, you can
right-click the job and select Active Full.

Performing Active Full Backup for Individual Workloads


To perform active full backup for individual workloads:

1. Open real-time statistics or sessions results of the job.

2. Select workloads for which you want to perform active full backup.

3. Right-click one of the selected workloads and click Active Full. Note that you will be able to launch active
full backup for other workloads in the job only after active full finishes for the selected workloads.

IMP ORTANT

You can perform active full backup for individual workloads only if their backups are per-machine with
separate metadata files.

1353 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1354 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Quick Backup
Quick backup lets you perform on-demand incremental backup for VMs. You can use quick backup if you want to
produce an additional restore point for one or more VMs in a backup job and do not want to configure a new job
or modify the existing one. Quick backup can be run for both incremental and reverse incremental backup
chains.

Quick backup is an incremental backup task: Veeam Backup & Replication copies only changed data for selected
VMs and saves this data to a new restore point in the backup chain. Similar to incremental backup, quick backup
can only be run for VMs that have been successfully backed up at least once and has a full restore point. If there
is no full restore point for a VM, quick backup cannot be performed.

To perform quick backup, Veeam Backup & Replication uses an existing backup job. When you start a quick
backup task for a VM, Veeam Backup & Replication verifies that a backup job processing this VM exists on the
backup server. If such job is detected, Veeam Backup & Replication triggers a job and creates an incremental
restore point for the VM. If a backup job for the VM does not exist, quick backup is terminated.

You can run quick backup for one VM or more VMs at once. If you start quick backup for several VMs and these
VMs are processed by different backup jobs, Veeam Backup & Replication triggers a set of backup jobs. Each
triggered job creates a separate restore point and stores this restore point in a correct backup chain.

In some cases, a VM may be processed by several backup jobs on the backup server. In this case,
Veeam Backup & Replication starts the job that has created the most recent restore point for the VM.

For example, VM01 is processed by 2 jobs:

• Backup job 1 created the most recent restore point on Monday

• Backup job 2 created the most recent restore point on Tuesday

When you start quick backup for VM01, Veeam Backup & Replication will trigger Backup job 2 to create a new
incremental restore point.

NOTE

If the quick backup task overlaps the scheduled backup job, the backup job waits for the quick backup task
to complete.

1355 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Retention Policy for Quick Backups
When you perform quick backup, Veeam Backup & Replication creates a single VM incremental restore point.
Unlike a regular incremental restore point that contains data for all VMs in a job, single VM incremental restore
point contains data only for a specific VM.

A single VM restore point is not regarded as full-fledged restore point in the backup chain. From the retention
policy perspective, single VM restore point is grouped with a regular restore point following it. When
Veeam Backup & Replication needs to delete a single VM restore point by retention, it waits for the next regular
restore point to expire — that is, Veeam Backup & Replication increases the retention by one restore point for
some time. After the next regular restore point expires, Veeam Backup & Replication deletes two restore points
at once.

If the backup chain is stored in a repository with the Use per-machine backup files option enabled, the retention
increases in a different way. As a rule, the retention increases by the number of VMs from this chain for which
quick backup was performed. This applies to the reverse incremental and forward incremental backup chains.

1356 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Performing Quick Backup
You can create an ad-hoc incremental backup for one or more VMs — quick backup, and add it to the backup
chain in the backup repository. Quick backup can be helpful if you want to produce an additional restore point
for one or more VMs in the backup job and do not want to configure a new job or modify the existing one.

Quick backup can be performed for VMs that meet the following requirements:

• A backup job processing the VM exists on the backup server.

• A full backup file for the VM exists in the backup repository configured in the backup infrastructure.

To perform quick backup:

1. Open the Inventory view.

2. In the infrastructure tree, select a host or VM container (Hyper-V host, cluster, SCVMM, SCVMM tag,
SCVMM host group, VM group, or volume) in which the VMs that you want to back up reside.

3. In the working area, select the VMs and click Quick Backup on the ribbon. You can also right-click the VMs
and select Quick Backup.

Veeam Backup & Replication will trigger a backup job to create a new incremental restore point for
selected VMs. Details of a running quick backup task are displayed in the job session window.

1357 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Importing Backups Manually
You may need to import backups to Veeam Backup & Replication in the following situations:

• The backup server has failed and you have restored it in a new location. You want to restore VM data from
backups created by the backup server that has failed.

• You want to restore VM data from backups created on another backup server.

• You want to restore VM data from backups in the backup repository that is not added to the backup
infrastructure (for example, if you removed it earlier).

• You want to restore VM data from VeeamZIP files created on your backup server or another backup server.

The imported backup becomes available in the Veeam Backup & Replication console. You can use any restore
operation to recover VM data from this backup.

Considerations and Limitations


Before you import a backup, consider the following:

• In the Veeam Backup & Replication console, you can import backups from the following types of
repositories: Microsoft Windows servers, Linux servers, HPE StoreOnce and Dell Data Domain
deduplicating storage appliances. To import files from other types of repositories, use the Import-
VBRbackup cmdlet as described in the Veeam PowerShell Reference.

• The server from which you plan to import backups must be added to the backup infrastructure. Otherwise,
you will not be able to access backup files.

• To be able to restore VM data from previous backup restore points, make sure that you have all required
incremental backup files (forward or reverse) in the same folder where the full backup file resides.

• You can import backups created by a later version of Veeam Backup & Replication, however, restore
operations for this backup will not be available.

Importing Backups Manually


To import a backup to the Veeam Backup & Replication console:

1. On the Home tab, click Imp ort Backup.

2. From the Computer list, select the server on which the backup you want to import is stored.

3. Click Browse and select the necessary VBM or VBK file. If you select the VBM file, the import process will
be notably faster. It is recommended that you select the VBK file only if the VBM file is not available.

4. By default, index data of the VM guest OS file system is not imported with the backup to speed up the
import process. If you want to import index data, select the Imp ort guest file system index check box.

5. Click OK to import the backup. The imported backup will be displayed in the Home view, under the
Ba ckups > Imported node in the inventory pane. Backups are imported using the original name of the
backup job with the _imported suffix appended.

1358 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
TIP

If you need to import all backups stored on a server, assign a backup repository role to it and enab le import
at the Review step of the wizard. If the repository is already added to the backup infrastructure, you can
rescan it. Veeam Backup & Replication will automatically import backups. For more information, see
Rescanning Backup Repositories.

Note that Veeam Backup & Replication will not be able to import backups if VBM files are not available. In
this case you will have to import backups manually using the VBK files.

1359 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Importing Encrypted Backups
You can import backups that were encrypted on this backup server or on another backup server.

To import an encrypted backup file:

1. On the Home tab, click Imp ort Backup.

2. From the Computer list, select the host on which the backup you want to import is stored.

3. Click Browse and select the VBM or VBK file.

4. Click OK. The encrypted backup will appear under the Ba ckups > Disk (encrypted) node in the inventory
pane.

5. In the working area, select the imported backup and click Sp ecify Password on the ribbon or right-click the
backup and select Sp ecify password.

6. In the P a ssword field, enter the password for the backup file.

If you changed the password one or several times while the backup chain was created, you must enter
passwords in the following manner:

o If you select a VBM file for import, you must specify the latest password that was used to encrypt files
in the backup chain.

o If you select a VBK file for import, you must specify the whole set of passwords tha t were used to
encrypt files in the backup chain.

If you enter correct passwords, Veeam Backup & Replication will decrypt the backup file. The backup will be
moved under the Ba ckups > Disk ( Imported) node in the inventory pane.

NOTE

You can recover data from encrypted backups even if the password is lost. Restoring data without a
password is included in the Veeam Universal License. When using a legacy socket-based license, Enterprise
or higher edition is required. Also, your backup server must be connected to Veeam Backup Enterprise
Manager. For more information, see Decrypting Data Without Password.

1360 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Importing Transaction Logs
You cannot import transaction log backups without VM backups (as there will be no restore point to which the
transaction logs can be applied).

To import a VM backup with transaction log backups, do either of the following:

• Import a backup metadata file (VBM). In this case, Veeam Backup & Replication will automatically import
the database backup and log backups.

• Import a full backup file (VBK). In this case, Veeam Backup & Replication will browse to required log
backups and import them, too.

1361 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Importing Backup Files from Scale-Out Backup
Repositories
You cannot import a backup directly from the scale-out backup repository. When you perform backup import,
you cannot browse through all extent of the scale-out backup repository. Veeam Backup & Replication lets you
browse only through individual extents.

To import a backup from the scale-out backup repository, you must place backup files from all extents to one
staging folder. The staging folder can reside on any server added to the backup infrastructure. After that, you
can import the backup as usual.

TIP

If you need to import all backups stored in a scale-out backup repository, rescan the repository. In this
case, you do not need to place files in one folder, Veeam Backup & Replication will import backups
automatically. For more information, see Rescanning Backup Repositories.

1362 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Backups
You can perform the following operations with backups:

• View backup properties.

• Upgrade Backup Chain Formats.

• Move backups.

• Copy backups.

• Export backups.

• Detach a backup from a job.

• Delete a backup from disk.

• Delete backups from object storage repositories.

• Delete backups from scale-out backup repositories.

• Remove missing restore points.

1363 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Backup Properties
You can view summary information about created backups. The summary information provides the following
data:

• Available restore points.

• Date of restore points creation.

• Compression and deduplication ratios.

• Data size (amount of data before compression and deduplication), backup size (actual, physical amount of
data stored in the repository after compression and deduplication), original size (size of the selected VM)
and total size (sum of all the original sizes displayed in Ob jects).

• GFS retention policy applied to restore points (W — weekly; M — monthly; Y — yearly).

• Backup retention date. This column is available for backups created by VeeamZIP, export backup or copy
backup and with the retention period specified.

In the Ba ckup Properties window, you can see different icons whose meaning is described in section Backup
State Indicators.

To view summary information for backups:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

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

4. To see the list of available restore points, select the required object from the Ob jects list.

1364 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Backup Chain Formats
Veeam Backup & Replication supports the following ways to store backup files: per-machine backup with
separate metadata files, per-machine backup with single metadata file and single-file backup. For more
information, see Backup Chain Formats.

Changing the Use per-machine backup files option for existing backup repositories or moving backups to other
repositories does not change the backup chain format. To change the format, follow the instructions in this
section.

NOTE

Consider the following:

• Change the backup chain format only for backups created successfully.
• Before changing the backup chain format, Veeam Backup & Replication disables the job to which the
backups belong. After the change, the job stays disabled, you need to enable it manually.
• You must disable log backup jobs manually before changing the format.
• [For backups stored on repositories with immutability enabled] You can upgrade backups from per -
machine backup with single metadata file to per-machine backup with separate metadata files.
Other upgrades are not possible.
• You can stop an upgrade session only for the backups for which the session has not started. If the
session has started, Veeam Backup & Replication continues the upgrade to avoid backup corruption.

Per-Machine Backup with Single Metadata File to Per-Machine


with Separate Metadata Files
To change the backup chain format from per-machine with single metadata file to per-machine with separate
metadata files, use the upgrade functionality:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary jobs. Note that the selected jobs must be targeted to the same
repository.

4. Right-click one of the selected jobs and click Up grade backup chain format. Alternatively, click Up grade
Ba ckup Chain Format on the ribbon.

1365 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication will generate new metadata files for the existing backups. After the upgrade, the
job will continue the backup chain and will create per-machine backups with separate metadata files.

Other Formats
To change the backup chain format, you must detach the existing backup chain from the job and then target the
job to the required repository:

1. Detach backups from the job for whose backups you want to change the backup chain format. For more
information, see Detaching Backups from Jobs.

2. Make sure that the job is targeted to a repository with the necessary state of the Use per-machine backup
files check box. You can edit job settings or repository settings.

The selected check box is for per-machine backups with separate metadata files, the cleared check box is
for single-file backups. You cannot upgrade the backup chain to the per-machine backup with single
metadata file as this format is obsolete since Veeam Backup & Replication version 12.

3. To create backup files of the required backup chain format, launch the job. The job will create active full
backups.

Related Topics
Changing Backup Chain Formats for Backup Copy Jobs

1366 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Moving Backups
Veeam Backup & Replication allows you to move all backups of a backup job to another repository or to move
specific workloads and their backups to another job.

Moving Backups to Another Repository


For information on the move operation, how it works and its limitations, see Backup Move.

To move backups to another repository and target a job to this repository, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary job.

4. Right-click the job and select Move backup. Alternatively, click Move Backup on the ribbon.

5. In the Move Backup to Another Location window, select the repository to which you want to move
backups.

Veeam Backup & Replication will reconfigure and target the backup job to the selected repository.

6. Click OK.

Alternatively, you can change the repository in the job settings.

Moving Backups to Another Job


For information on the move operation, how it works and its limitations, see Backup Move.

1367 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To move backups to another job:

7. Open the Home view.

8. In the inventory pane, select the Ba ckups node.

9. In the working area, expand the necessary backup job and select workloads.

NOTE

You can move individual workloads and their backups only if backups are per-machine with separate
metadata files for each workload.

10. Right-click one of the selected workloads and click Move backup. Alternatively, click Move Backup on the
ribbon.

11. In the Move Backup to Another Job window, select the backup job to which you want to move backups.

Veeam Backup & Replication will include workloads into the selected job and exclude workloads from the
original job. Backups of the selected workloads will be moved to the repository to which the selected job
is targeted.

12. Click OK.

Managing Failed Activities


If the move operation fails, Veeam Backup & Replication assigns the User action required status to it. In this
case, you need to decide how to finish the operation: retry the move operation for failed workloads, cancel all
changes or move failed workloads but detach their backups. If you detach failed backups, the target job creates
active full backups for failed workloads and continues backup chains for other workloads. The detached backups
are shown in a node with the ( Orphaned) postfix in the inventory pane.

1368 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The original job will still be in the disabled state until you finalize the failed move operation.

To finalize the move operation:

1. Open the Home view.

2. In the inventory pane, select the La st 24 Hours node.

3. Right-click the failed move session and select the required action. Alternatively, select the required action
on the ribbon.

1369 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Copying Backups
Copying backups can be helpful if you want to copy backups of a workload or backup job to another repository,
local or shared folder. Veeam Backup & Replication copies the whole backup chain. If you want to convert a
specific restore point into a single VBK file, use backup export. For more information, see Exporting Backups.

When Veeam Backup & Replication performs the copy operation, it disables the job, copies files to the target
location and then enables the job. After the copy operation finishes, the copied backups are shown in a node
with the ( E xported) postfix in the inventory pane.

NOTE

This section is about one-time copy operation. If you want to copy backups on a schedule, create a backup
copy job. For more information, see Backup Copy.

Requirements and Limitations


Consider the following:

• The copy operation does not change backup chain format (single-file backup, per-machine with single
metadata file or per-machine with separate metadata files). If you copy backups between repositories with
and without the Use p er-machine backup files check box enabled, backups preserve their formats.

• If you copy backups from a scale-out backup repository and some backups are stored on extents in the
Maintenance mode, such backups are not copied.

• Veeam Backup & Replication copies backups only from the performance tier of the scale-out backup
repository. If you want to copy data from the capacity tier, you first must download it to the performance
tier. For more information, see Downloading Data from Capacity Tier.

• You cannot copy backups stored in Veeam Cloud Connect repositories. For more information on Veeam
Cloud Connect repositories, see the Cloud Repository section in the Veeam Cloud Connect Guide.

• [For VMware Cloud Director] You can copy backups of a whole job or individual vApps. You cannot move
backups of VMs.

• You cannot copy backups created by a backup job managed by Veeam Agent (backup policy).

• You cannot copy backups created by Veeam plug-ins for Enterprise applications, Veeam Cloud Plug-ins
(Veeam Backup for AWS, Veeam Backup for Google Cloud, Veeam Backup for Microsoft Azure), and Kasten
K10.

Copying Backups
To copy backups, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary job or workload. Note that you can copy backups of an individual
workload only if its backups are per-machine backups with separate metadata files.

4. Right-click the job and select Cop y backup. Alternatively, click Cop y Backup on the ribbon.

5. In the Cop y Backup to Another Location window, choose where you want to copy backups — to a
repository or to a local or shared folder.

1370 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. If you want to delete the copied backups after a specific time period, select the Delete this backup
a utomatically in check box and specify the time period.

Backups that fall out of the specified retention policy will be removed automatically. If you do not specify
the time period for deletion, copies will be stored until you remove them manually.

7. Click OK.

Managing Failed Activities


If the copy operation fails, Veeam Backup & Replication assigns the User action required status to it. In this case,
you need to decide how to finish the operation: retry the copy operation for failed backups, skip the failed
backups or cancel all changes.

NOTE

The original job will still be in the disabled state until you finalize the failed copy operation.

To finalize the copy operation:

8. Open the Home view.

9. In the inventory pane, select the La st 24 Hours node.

1371 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
10. Right-click the failed copy session and select the required action. Alternatively, select the required action
on the ribbon.

1372 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Exporting Backups
Exporting backups allows you to synthesize a complete and independent full backup file out of selected restore
points that are located in your backup repositories. That is, you can transform any incremental or reverse -
incremental backup chain (i.e all dependent .VBK, .VIB or .VRB files) into a full backup file and specify new
retention policy settings for it. This option can be useful for legal hold and archiving purposes in case you want
to prevent specific restore points from being deleted according to retention policy of the primary backup job. It
also allows you to provide a specific restore point on a removable media.

TIP

Exporting backups allows you to export only a full backup file. If you want to export the whole backup
chain, use the copy backup feature. For more information, see Copying Backups.

Export applies to Full, Incremental and Reverse-incremental restore points located in:

• Backup repositories.

• Object storage repositories.

• Scale-out backup repositories.

• Backup repositories of cloud service providers and their tenants.

Consider the following:

• Once export is complete, exported backup files will be displayed under the Ba ckups > Disk (Exported)
node.

• [For scale-out backup repositories] Backup files exported to the capacity tier will be displayed under the
Ba ckups > Capacity Tier (Exported) node. Backup files located in the archive tier will first be exported to
the capacity tier, then archived according to the archiving policy and displayed under the Ba ckups >
Archive Tier (Exported) node.

• [For scale-out backup repositories] If you export backup files from a capacity tier to the same scale -out
backup repository, Veeam Backup & Replication will synthesize backup files in the capacity tier. If you
export backups to another scale-out backup repository, Veeam Backup & Replication will synthesize
backup files in the performance tier.

• If a restore point that is being exported resides on the tenant side, a new full backup file will also be
exported to the same repository (on the tenant side) from which the source restore point is being taken.

• If a tenant initiates export of a restore point that resides in the subtenant directory, a new full backup file
will be exported to the tenant directory.

• If you select a backup job consisting of multiple virtual machines, Veeam will synthesize a separate full
backup file per each machine.

• Export session results are saved to the configuration database and available for viewing, as described in
section Viewing Session Statistics.

Performing Export
To export data, do the following:

1. Launch the Export Backup wizard.

2. Select restore points to export.

1373 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Specify a destination.

4. Specify an export reason.

5. Finish working with the wizard.

1374 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Export Backup Wizard
To launch the E x port Backup wizard, do either of the following:

• On the Home tab, click E x port Backup.

• In the Home view under the Ba ckups > Disks node, select a VM you want to transform into a full backup
file and click E x port backup.

1375 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Restore Points to Export
At the Restore P oint step of the wizard, do the following:

1. Click Ad d to select a VM, the restore points of which you want to transform into full backup files.

2. In the Ba ckups Browser dialog, select a backup job or virtual machine.

When selecting a backup job consisting of multiple machines, then each machine will be exported as an
independent full backup file.

3. In the Ba ckups to export list, select a VM and click P oint to choose a restore point that you want to
transform into a full backup file.

1376 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Destination
At the Ta rget step of the wizard, do the following:

1. In the E x port restore point to area, choose whether you want to export restore points to a backup
repository or to a local or shared folder.

2. If prompted, in the Credentials window, specify credentials of the user account to access the target
location.

3. To automatically delete the exported files after the specified period of time, select the Delete exported
b a ckup file a utomatically check box and specify the period. The exported files will be removed at
12:00:00 AM on the next day after the retention period ends.

1377 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Export Reason
At the Rea son step of the wizard, provide the reason for restore.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1378 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Summary step of the wizard, review summary information, click Finish and wait until the restore session,
which is described in section Viewing Session Statistics, is complete.

Viewing Session Statistics


Once you invoke the export procedure, Veeam shows the Restore Session progress dialog that informs you of
the current export status.

You can close the dialog by clicking the Close button in the lower-right corner and let Veeam perform export in
the background.

As each export session saves its results to the configuration database, you can review them at any time.

To review the export session results, do the following:

1. In the inventory pane, go to the History view and select the Restore > E xport node.

2. In the working area, double-click a machine for which you want to review the session results or right-click
a machine and select Sta tistics.

The Restore Session dialog contains the following tabs:

• The Rea son tab — shows you the reason of export you may have provided at the Specify Export Reason
step of the wizard.

1379 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The P a rameters tab — shows you the date when the exported backup files will be removed due to the
retention policy you may have configured at the Select Restore Points to Export step of the wizard. In this
tab you can also find a backup name and Date/time of a restore point that was synthesized into a full
backup file.

• The Log tab — shows you the actual export progress.

Canceling Session
To cancel a session, open the Restore Session dialog, as described in steps 1–2 above, and click Ca ncel restore
ta sk in the upper-right corner of the dialog.

1380 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Detaching Backups from Jobs
If you want to detach backups from a job, you can use the Detach from job operation.

When you detach backups from a job, the job stops processing these backup files. During the next run, the job
will start a new backup chain, that is, will create active full backups.

The detached backup files remain in the backup repository and also in the Veeam Backup & Replication console.
Veeam Backup & Replication shows the detached backups in the inventory pane in the node with the ( Orphaned)
postfix. These backups are retained according to the background retention process. For more information, see
Background Retention.

To detach backups from a job:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, right-click the necessary backup and select Detach from job. Alternatively, click
Delete from > Job on the ribbon.

1381 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Backups from Configuration
If you want to remove records about backups from the Veeam Backup & Replication console and configuration
database, you can use the Remove from configuration operation.

When you remove a backup from the configuration, backup files remain in the backup repository. You can import
the backup to Veeam Backup & Replication at any time later and restore data from it.

When you remove an encrypted backup from configuration, Veeam Backup & Replication removes encryption
keys from the configuration database. If you import such backup on the same backup server or another backup
server, you will have to specify the password or unlock the backup with Veeam Backup Enterprise Manager. For
more information, see Importing Encrypted Backups.

To remove a backup from the configuration:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, press the [Ctrl] key, right-click the backup that you want to remove and select
Remove from configuration.

NOTE

Removing backups from configuration is designed for experienced users only. Consider Deleting Backups
from Disk or Detaching Backups from Jobs instead.

1382 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Backups from Disk
The Delete from disk operation is needed if you want to remove records about backups from the
Veeam Backup & Replication console and configuration database. This option allows you to delete the following
type of data:

• Backup files from the backup repository

• Separate VMs from backups

When you delete backup files from a disk, Veeam Backup & Replication deletes the whole chain from the backup
repository. Thus, on the next run of the backup job, Veeam Backup & Replication will create full backups for
VMs included in the job.

Consider the following:

• Do not delete backup files from the backup repository manually. Use the Delete from disk option instead.
If you delete backup files manually, subsequent ba ckup or replication job sessions will fail.

• If the per-machine functionality is enabled, you can perform the Delete from disk operation for separate
VMs in the backup. If you delete backup files for one VM, on the next run of the backup job
Veeam Backup & Replication will create a full backup for VMs whose backup files are deleted. For all other
VMs, Veeam Backup & Replication will create increments.

To learn more about per-machine backup files, see Per-Machine Backup Files

• When you delete a separate VMs from a backup and if the per-machine functionality is enabled for this
VM, Veeam Backup & Replication behaves differently:

o [If per-machine is enabled] Veeam Backup & Replication deletes backup files of the selected VMs.

On the next run of the job, Veeam Backup & Replication will create full backups for VMs whose
backup files were deleted. For all other VMs, Veeam Backup & Replication will create increments.

o [If per-machine is disabled] Veeam Backup & Replication only marks data block that belong to the
deleted VMs as empty — the size of backup files does not change. However,
Veeam Backup & Replication will use these data blocks during such operations as merging backup
files. To reduce the size of full backup files in forever forward incremental and reverse incremental
backup chains, you can compact full backup files. In forward incremental backup chains, files with
block marked as empty will be deleted by retention.

On the next run of the job, Veeam Backup & Replication will create full backups for VMs whose
backup files were deleted. Note that full backups of these VMs will be stored in an incremental file.
For all other VMs, Veeam Backup & Replication will create incremental backups.

• If you use the scale-out backup repository, keep in mind that the Delete from disk operation will remove
the backups not only from the performance tier, but also from the capacity and archive tier. If you want to
remove backups from the performance tier only, you should move those backups to the capacity tier
instead. For details, see Moving to Capacity Tier.

Deleting Backups
To delete backup files from the backup repository, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups or Rep licas.

3. In the working area, select the backup and click Delete from > Disk on the ribbon. You can also right-click
the backup and select Delete from disk.

1383 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. To remove backups with GFS flags (weekly, monthly and yearly), select the Remove GFS full backups
check box and click Y es .

Deleting VMs from Backups


To delete a VM from a backup, do the following:

1. Open the Home view.

2. In the inventory pane, select Ba ckups or Rep licas.

3. In the working area, expand the necessary backup, select the VM you want to delete and click Delete from
> Disk on the ribbon. You can also right-click the backup and select Delete from disk.

4. To remove backups with GFS flags (weekly, monthly and yearly), select the Remove GFS full backups
check box and click Y es .

1384 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Backups from Object Storage
Repositories
This section describes, how to delete backups from object storage repositories. To know how to delete backups
from an object storage repository added as an extent of the scale-out backup repository, see Deleting Backups
from Scale-Out Backup Repositories.

To delete a backup from object storage repositories, do the following:

1. Open the Home view.

2. In the inventory pane, navigate to the Ba ckups > Ob ject Storage node.

3. In the working area, select a backup or VM and click Delete from Disk on the ribbon. Alternatively, you can
right-click a backup and select Delete from disk.

1385 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Backups from Scale-Out Backup
Repositories
To delete a backup from an scale-out backup repositories, do the following:

1. Open the Home view.

2. In the inventory pane, navigate to the Ba ckups and select one of the following node:

o Select the Ob ject Storage node if you want to delete a backup from the object storage repository
added as a performance extent.

IMP ORTANT

Keep in mind that the Delete from disk operation will remove the backups not only from the
performance tier, but also from the capacity and archive tier. If you want to remove backups
from the performance tier only, you should move those backups to the capacity tier instead. For
details, see Moving to Capacity Tier.

o Select the Ca pacity Tier node if you want to delete a backup from the capacity tier.

o Select the Archive Tier node if you want to delete backups from the archive tier.

3. In the working area, select a backup or VM and click Delete from Disk on the ribbon. Alternatively, you can
right-click a backup and select Delete from disk.

1386 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Missing Restore Points
In some cases, one or more restore points in the backup chain may be inaccessible. This can happen, for
example, if the backup repository is put to the Maintenance mode (for scale-out backup repositories), the
backup repository is not available or some backup file is missing in the backup chain. Backup chains that contain
missing restore points get corrupted — you cannot perform backup or restore VM data from the missing restore
point, and restore points that depend on the missing restore point.

You can perform two operations with missing restore points:

• Forget — you can remove records about missing restore points from the configuration database.
Veeam Backup & Replication will “forget” about missing restore points and will not display them in the
console. The actual backup files will remain on disk (if backup files are still available).

• Remove — you can remove records about missing restore points from the configuration database and
delete backup files from disk (if backup files are still available).

NOTE

Consider the following:

• The Forget and Remove from d isk options are available only for restore points that are missing from
the backup chain or points that depend on missing ones. If the restore point is available in the
backup chain and does not depend on a missing restore point, you will not be able to use the Forget
and Remove from disk options for it.
• You can manually update information about missing restore points. For this, disable a backup job
and rescan the backup repository that is the target for the job. For more information, see Disabling
and Removing Jobs and Rescanning Backup Repositories.
Manual update can be required because Veeam Backup & Replication requires some time to update
information in the configuration database for restore points that were removed from a backup chain
or became inaccessible. That is why such restore points may not be displayed in the console as
missing restore points.
• Veeam Backup & Replication does not track missing restore points in backups that reside in the
cloud repository.
• If you apply the Forget or Remove from disk options to a missing restore point in a scale-out backup
repository, the backup file associated with the missing restore point will be deleted from capacity
tier and archive tier on the next offload and archiving job run.

To remove records about missing restore points from the configuration database:

1. Open the Home view.

2. In the inventory pane, select Disk under Ba ckups.

3. In the working area, select the backup and click P roperties on the ribbon or right-click the backup and
select P roperties.

4. In the Ba ckup Properties window, right-click the missing restore point and select Forget.

o To remove only the selected restore point and restore points that depend on it (that is, a part of the
backup chain starting from this restore point), select This a nd dependent backups.

1387 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To remove all missing restore points, select All unavailable backups.

To remove missing restore points from the configuration database and disk:

1. Open the Home view.

2. In the inventory pane, click Disk under Ba ckups.

3. In the working area, select the backup and click P roperties on the ribbon or right-click the backup and
select P roperties.

4. In the Ba ckup Properties window, right-click the missing restore point and select Remove from disk.

o To remove only the selected restore point and restore points that depend on it (that is, a part of the
backup chain starting from this restore point), select This a nd dependent backups.

1388 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To remove all missing restore points, select All unavailable backups.

1389 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Launching Background Retention
Veeam Backup & Replication launches background retention every 24 hours at 00:30. If you need to free up disk
space from outdated backups earlier, you can launch the background retention manually.

To launch the background retention outside its automatic schedule, do the following:

1. Open the Home view.

2. In the inventory pane, right-click the Ba ckups node.

3. Select Ap p ly retention now or click Ap p ly Retention on the ribbon.

1390 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling Background Retention
You can manually disable background retention, which is launched every 24 hours at 00:30. You can enable
disabled background retention at any time.

If you turn off background retention, you will receive a daily email report reminding you that it is disabled.
Veeam Backup & Replication will send these reports only after you have enabled and configured email
notifications, as described in the section Configuring Global Email Notification Settings.

If background retention is turned off while backup jobs are still enabled, auxiliary data cannot be cleaned from
object storage repositories. This can decrease backup job performance over time.

NOTE

Disabling background retention feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131) and later.

To disable background retention:

1. Open the Home view.

2. In the inventory pane, right-click the Ba ckups node.

3. Select Disable retention or click Disable Retention on the ribbon.

To enable a disabled background retention, select Ba ckups node and click Disable Retention on the ribbon once
again. Alternatively, you can right-click the Ba ckups node and select Disable retention.

1391 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Backup Jobs
To view all jobs configured on the backup server, open the Home view and select the Job s node in the inventory
pane. The list of available jobs is displayed in the working area. You can edit job properties, start and stop jobs,
restart failed jobs, clone jobs, view job statistics and delete unnecessary jobs.

1392 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Job Settings
You can edit configured jobs at any moment. For example, you may want to change scheduling settings for the
job or add some VMs to the job.

To edit job settings:

1. Open the Home view.

2. In the inventory pane, select Job s .

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

You will follow the same steps as you have followed when creating the job and can change job settings as
required.

1393 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cloning Jobs
You can create new jobs by means of job cloning. Job cloning allows you to create an exact copy of any job with
the same job settings. Configuration information of the created job copy are written to the configuration
database that stores information of the original job.

To create multiple jobs with similar settings, you can configure a set of jobs that will be used as ‘job templates’.
You can then clone these 'job templates' and edit settings of cloned jobs as required.

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.

When cloning job, Veeam Backup & Replication can change some job settings so that cloned jobs do not hinder
original jobs.

• If the original job is scheduled to run automatically, Veeam Backup & Replication disables the cloned job.
To enable the cloned job, select it in the job list and click Disable on the ribbon or right-click the job and
select Disable.

• If the original job is configured to use a secondary target, the cloned job is created without the secondary
target settings.

To clone a job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the job and click Clone on the ribbon or right-click the job and select Clone.

4. After a job is cloned, you can edit all its settings, including the job name.

NOTE

Consider the following:

• [For Veeam Backup & Replication 12.1 (build 12.1.0.2131) and later] The job cloning functionality is
available for all types of licenses.
• [For Veeam Backup & Replication before 12.1 (build 12.1.0.2131)] The job cloning functionality is
included in the Veeam Universal License. When using a legacy socket-based license, Enterprise or
higher edition is required.

1394 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1395 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling and Deleting Jobs
You can temporary disable scheduled jobs. The disabled job is paused for some period of time and is not run by
the specified schedule. You can enable a disabled job at any time. You can also permanently delete a job from
Veeam Backup & Replication and from the configuration database.

Disabling Job
To disable a job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the job and click Disable on the ribbon or right-click the job and select Disable.

To enable a disabled job, select it in the list and click Disable on the ribbon once again.

Deleting Job
To remove a job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the job and click Delete on the ribbon or right-click the job and select Delete.

After the job is deleted, the backups created by this job are displayed under the Ba ckups > Disk ( Orphaned)
node. If the backup files created by this job were also stored in capacity tier or archive tier, they will also be
displayed under the Ba ck ups > Ob ject Storage (Orphaned) or Ba ckups > Archive (Orphaned) nodes.

1396 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Starting and Stopping Jobs
You can start job manually, for example, if you want to create a n additional restore point for a VM backup or
replica and do not want to change the job schedule. You can also stop a job, for example, if VM processing is
about to take long, and you do not want the job to produce workload on the production environment during
business hours.

Starting Jobs
To start a job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job and click Sta rt on the ribbon or right-click the job and select
Sta rt.

Stopping Jobs
You can stop a job in one of the following ways:

• Stop job immediately. In this case, Veeam Backup & Replication will produce a new restore point only for
those VMs that have already been processed by the time you stop the job.

• Stop job after current VM. In this case, Veeam Backup & Replication will produce a new restore point only
for those VMs that have already been processed and for VMs that are being processed at the moment.

To stop a job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job and click Stop on the ribbon or right-click the job and select
Stop . In the displayed window, click Immediately.

To stop the job after the current VM:

1. Open the Home view.

2. In the inventory pane, click Job s .

1397 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click the job and select Stop . In the displayed window, click Gra cefully.

1398 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Starting and Stopping Transaction Log Backup
Jobs
If you create a backup job and instruct it to ship transaction logs, the backup job comprises 2 jobs:

1. A parent backup job creating an image-level backup of the VM on which the database runs. This job is
named as a regular backup job, for example: Daily Job .

2. A transaction log backup job responsible for shipping transaction logs to the backup repository. This job is
named by the following pattern:

o For MS SQL: <job_name> SQL Server Transaction Log Backup . For example, Daily Job SQL Server
Transaction Log Backup .

o For Oracle: <job_name> Oracle Redo Log Backup . For example, Daily Job Oracle Redo Log Backup .

The transaction log backup job is created automatically by Veeam Backup & Replication if it detects that you
have added to the backup job at least one Microsoft SQL Server or Oracle VM, enabled application-aware
processing and instructed Veeam Backup & Replication to back up transaction logs periodically.

Starting Transaction Log Backup Jobs


A parent backup job is started manually when you click Sta rt on the toolbar, or automatically by schedule. The
transaction log backup job is initially started when you enable schedule for the parent backup job. The
transaction log backup works continuously in the background. A new session of the transaction log bac kup job
starts every time the parent backup job is launched.

Stopping Transaction Log Backup Jobs


You can stop transaction log processing in one of the following ways:

• Disable transaction log shipping

• Disable the parent backup job

If you want the backup job to create image-level backups of the VM but do not want it to ship transaction logs
anymore, you can disable transaction log backup in the backup job settings.

To disable transaction log shipping:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job and click E d it on the ribbon or right-click the backup job and
select E d it.

4. Pass to the Guest Processing step of the wizard and click Ap p lications.

5. In the Ap p lication-Aware Processing Options window, select the VM and click E d it.

6. On the SQL or Ora cle tab of the VM P rocessing Settings window, disable transaction log backup.

7. Click Finish to save the job settings.

1399 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If you do not want to create image-level backups of the VM and back up database transaction logs, you can
disable scheduling for the parent backup job. Veeam Backup & Replication will instruct the transaction log
backup job to complete log processing for all VMs added to the parent backup job, and will switch the parent
backup job to the non-scheduled mode. The parent backup job will no longer be started automatically by
schedule — you will have to run it manually.

To disable scheduling for the parent backup job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job and click E d it on the ribbon. Alternatively, you can right-click
the backup job and select E d it.

4. Pass to the Schedule step of the wizard and clear the Run the job automatically check box.

5. Click Finish to save the job settings.

Alternatively, you can disable the parent backup job:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the backup job and click Disable on the ribbon or right-click the job and select
Disable.

To re-activate transaction log processing for all VMs in the parent backup job, select the job in the list and click
Disable on the ribbon once again.

1400 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Retrying Jobs
The retry option is necessary if a job fails and you want to retry this operation again. When you perform a retry,
Veeam Backup & Replication restarts the operation only for the failed workloads added to the job and does not
process VMs that have been processed successfully. As a result, the retry operation takes less time compared to
running the job for all workloads.

Retrying Job for All Failed Workloads


To perform retry for all workloads in 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 Retry on the ribbon. Alternatively, you can right-
click the job and select Retry.

Retrying Job for Individual Workloads


To perform retry for individual workloads:

1. Open real-time statistics or sessions results of the job.

2. Select failed workloads for which you want to perform retry.

3. Right-click one of the selected workloads and click Retry. Note that you will be able to launch retry for
other workloads in the job only after retry finishes for the selected workloads.

IMP ORTANT

You can perform retry for individual workloads only if their backups are per-machine with separate
metadata files.

1401 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1402 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Reconfiguring Jobs with Microsoft SQL Server
VMs
In some situations, you may need to reconfigure a backup job that processes a Microsoft SQL Server VMs and
ships transaction logs. For example, you may want to create a separate backup job to process the vir tualized
database, and delete the VM running the database from the previously created job.

When you configure a new job, mind the restriction on transaction logs shipping. By default, the new backup job
that processes the VM will not ship transaction logs if transaction logs for this VM have been shipped for the
last 7 days by another backup job on the same backup server.

You can overcome this restriction with registry values. For more information, contact Veeam Customer Support.

1403 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Targeting Jobs to Another Repository
Veeam Backup & Replication offers you two ways to target a job to another repository:

• You can use the move to another repository operation as described in section Moving Backups to Another
Repository. In this case, Veeam Backup & Replication moves all backups to a new repository and
reconfigures the job automatically to target to the new location.

• You can edit job settings and select a new repository at the Storage step of the wizard. In this case,
Veeam Backup & Replication will prompt you to choose whether you want to move all the existing
backups to the new repository or just start a new backup chain on the new repository. If you start a new
backup chain, the previously created backups are detached from the job and put into the node with the
( Orphaned) postfix.

For more information on how the move to another repository operation works and its considerations, see
Moving Backups.

1404 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Reporting
When you run a job, Veeam Backup & Replication saves the job statistics and operation data to the configuration
database. You can view real-time statistics for any performed job and generate reports with statistics data for
any job or separate job session.

1405 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Real-Time Statistics
To view real-time statistics for a job, do one of the following:

• Open the Home view, in the inventory pane select one of the following nodes: Job s, Last 24 hours or
Running. In the working area, right-click the job and select Statistics.

• Open the Home view, in the inventory pane select one of the following nodes: Job s, Last 24 hours or
Running. In the working area, double-click the running job.

The real-time statistics provides detailed data on job sessions: job p rogress, duration, processing rate,
performance bottlenecks, amount of processed data, read and transferred data and details of the session
performance, for example, warnings and errors that have occurred in the process of operation.

In addition to overall job statistics, the real-time statistics provides information on each object processed with
the job. To view the processing progress for a specific object, select it in the list on the left.

TIP

Consider the following:

• To collapse and expand the real-time statistics window, use Hid e Details and Show Details buttons
at the bottom left corner of the window.
• To switch between the job sessions backward and forward, use left and right arrow keys on the
keyboard.

Statistics Counters
Veeam Backup & Replication displays jobs statistics for the following counters:

• The Job progress bar shows percentage of the job completion.

• The Summary box shows general information about the job:

o Duration — time from the job start till the current moment or job end.

o P rocessing rate — average speed of VM data processing. This counter is a ratio between the amount of
data that has actually been read and the time it took to process the data. Note that only the data
transfer time is used for the calculation, and the job's runtime is irrelevant.

o Bottleneck — bottleneck in the data transmission process. To learn about job bottlenecks, see
Detecting Performance Bottlenecks.

• The Da ta box shows information about processed VM data:

o P rocessed — total size of all VM disks processed by the job.

1406 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o Rea d — amount of data read from the volume by the source-side Data Mover prior to applying
compression and deduplication. For incremental job runs, the value of this counter is typically lower
than the value of the P rocessed counter. Veeam Backup & Replication reads only data blocks that
have changed since the last job session, processes and copies these data blocks to the target.

o Tra nsferred — amount of data transferred from the source-side Veeam Data Mover to the target-side
Veeam Data Mover after applying compression and deduplication. This counter does not directly
indicate the size of the resulting files. Depending on the backup infrastructure and job settings,
Veeam Backup & Replication can perform additional activities with data: deduplicate data,
decompress data prior to writing the file to disk and so on. The activities can impact the size of the
resulting file.

• The Sta tus box shows information about the job results. This box informs how many tasks have compl eted
with the Success, Warning and Error statuses (1 task per 1 VM).

• The pane at the lower left corner shows a list of objects included in the job.

• The pane at the lower right corner shows a list of operations performed during the job. To see a list of
operations for a specific object included in the job, click the object in the pane on the left. To see a list of
operations for the whole job, click anywhere on the blank area in the left pane.

Colored Graph
To visualize the data transfer process, Veeam Backup & Replication displays a colored graph in the real-time
statistics window:

• The green area defines the amount of data read from source.

• The brown area defines the amount of data transported to target.

• The horizontal line defines the current data processing speed.

If the job session is still being performed, you can click the graph to view data rate for the last 5 minutes or the
whole processing period. If the job session has already ended, the graph will display information for the whole
processing period only.

1407 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
The colored graph is displayed only for the currently running job session or the latest job session. If you open
real-time statistics for past sessions other than the latest one, the colored graph will not be displayed.

1408 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Job Session Results
You can view detailed statistics on every job session.

To view statistics for a selected job session, do either of the following:

• Open the History view. In the inventory pane select Job s. In the working area, double-click the necessary
job session.

• Open the History view. In the inventory pane select Job s. In the working area, right-click the necessary job
session and select Sta tistics.

TIP

To switch between past job sessions, use left and right arrow keys on the keyboard.

1409 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Job and Job Session Reports
You can generate reports with details about all sessions of a job or a single session only.

Job Report
The job report contains data on all sessions initiated for a specific job, that is, job history. The report shows data
for all sessions stored in the configuration database.

To generate a job report:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary job and click Rep ort on the ribbon. You can also right-click the
job and select Rep ort.

For more information on counters in the report, see Report Counters.

TIP

Generated reports are stored in the C:\Users\<username>\AppData\Local\Temp folder.

Session Report
To generate a report for a single session:

1. Open the History view.

2. In the inventory pane, select Job s .

3. In the working area, select the necessary session and click Rep ort on the ribbon. You can also right-click
the necessary session and select Rep ort.

Report Counters
Veeam Backup & Replication displays the following counters in reports:

• The Success, W arning and E rror counters show how many workloads were processed with the Success,
Warning and Error statuses.

• The Sta rt time and E nd time counters show when the job started and completed.

1410 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• The Duration counter shows time from the job start till the current moment or job end.

• The Tota l size counter shows provisioned size (the maximum configured size) of all workload disks in the
job.

• The Da ta read counter shows the amount of data read from the volume before compression and
deduplication. The value of this counter is typically lower than the value of the Tota l size counter.
Veeam Backup & Replication reads only data blocks that have changed since the last job session, processes
and copies these data blocks to the target.

• The Tra nsferred counter shows the amount of data transferred from the source side to the target side
after applying compression and source-side deduplication. This counter does not directly indicate the size
of the resulting files. Depending on the backup infrastructure and job settings,
Veeam Backup & Replication can perform additional activities with data: perform target-side
deduplication, decompress data prior to writing the file to disk and so on. The activities can impact the
size of the resulting file.

• The Ba ckup size counter shows the resulting backup file size.

• The Ded upe counter shows the deduplication level.

• The Compression counter shows the compression level.

In the Details section, you can see similar counters for each workload processed by the job.

1411 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Replication
Replication is a technology that helps you protect mission-critical Microsoft Hyper-V virtual machines. When
you replicate a VM, Veeam Backup & Replication creates an exact copy of the VM in the native Microsoft Hyper-
V format on the target host. Veeam Backup & Replication maintains this copy in sync with the source VM.
Replication provides minimum recovery time objective (RTO) in case a disaster strikes because VM replicas are in
a ready-to-start state.

Data Replication
To replicate VMs, Veeam Backup & Replication leverages Microsoft VSS snapshot and checkpoint capabilities.
When you replicate a VM, Veeam Backup & Replication instructs Microsoft Hyper-V to create a cohesive point-
in-time copy of a VM. Veeam Backup & Replication uses this point-in-time copy as a source of data for
replication.

During the first replication cycle, Veeam Backup & Replication copies data of the source VM running on the
source host, and creates its full replica on the target host. Unlike backup files, replica virtual disks are stored
decompressed in their native format. All subsequent replication cycles are incremental.
Veeam Backup & Replication copies only those data blocks that have changed since the last replication job
session. To keep track of changed data blocks, Veeam Backup & Replication uses different approaches. For more
information, see Changed Block Tracking.

Veeam Backup & Replication lets you perform on-site replication for high availability scenarios and remote (off-
site) replication for disaster recovery scenarios. To facilitate replication over the WAN or slow connections,
Veeam Backup & Replication optimizes traffic transmission. It filters out unnecessary data blocks such as
duplicate data blocks, zero data blocks, blocks of swap files and blocks of exclud ed VM guest OS files, and
compresses replica traffic. Veeam Backup & Replication also allows you to use WAN accelerators and apply
network throttling rules to prevent replication jobs from consuming the entire network bandwidth.

To replicate a VM, you need to configure required backup infrastructure components and create a replication
job.

Recovery
If a disaster strikes and the production VM stops working properly, you can fail over to its replica.

When you fail over to a replica, the replica takes over the role of the source VM. After your source VM is
repaired, you can fail back to it and transfer all changes that occurred to replica to the source VM. If your source
VM cannot be repaired, you can perform permanent failover, that is, permanently switch from the source VM to
the VM replica and use this replica as the source VM. For more information, see Failover and Failback for
Replication.

1412 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Considerations and Limitations
Replication has the following requirements and limitations:

• [For VMs with VHD disks] If you change the size of VM disks on the source VM, Veeam Backup & Replication
will delete all available restore points on the VM replica during the next replication job session.

• [For VMs with VHDX disks] If you change the size of VM disks on the source VM, Veeam Backup & Replication
resets changed block tracking (CBT).

• Disks that were deleted from the source VM configuration are not automatically deleted from the target
Hyper-V host storage.

• Off-host replication scenario is possible only for VMs located on a SAN storage with hardware VSS provider.

• Replication of VMs with disabled checkpoints is not supported.

• You cannot replicate VMs with shared VHDX and VHDS disks.

• Due to Microsoft limitations, you cannot use Microsoft Entra ID (formerly Azure Active Directory) credentials
to perform application-aware processing on VMs running Microsoft Windows 10 (or later).

• If a job is unable to complete within 21 days period, it will be stopped with the Failed status.

1413 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Infrastructure for Replication
Veeam Backup & Replication uses the following components for the replication process:

• Backup server

• Source and target hosts

• [Optional] Off-host backup proxy

• [For snapshot replica] Backup repository

• [Optional] WAN accelerators

Backup Server
During the replication process, the backup server coordinates replication tasks, controls resource allocation and
replica job scheduling. The backup server runs the Veeam Backup Service that coordinates all replication
operations.

For more information on the backup server, see Backup Server.

Source and Target Hosts


The source host is the host where VMs that you plan to replicate are located. The target host is the host where
VM replicas will be created and maintained in the ready-to-start state.

The role of a target host can be assigned to a standalone Microsoft Hyp er-V host or Microsoft Hyper-V cluster. If
you assign a cluster as a target, the replication process becomes more sustainable — the replication process will
not fail if there is at least one available host in the cluster.

To replicate data from and to hosts, they must be first added to the Veeam Backup & Replication infrastructure.
For more information on how to add Microsoft Hyper-V to the backup infrastructure, see the Adding Microsoft
Hyper-V Servers section.

Off-Host Backup Proxies


An off-host backup proxy collects, transforms and transports VM data during the replication process. For more
information on off-host backup proxies, requirements and limitations for them, see Off-Host Backup Proxy.

1414 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
You can use one backup proxy, however, we recommend you to use at least two backup proxies to ensure that
the job will be performed if one of backup proxies fails or loses its connectivity to the source storage. For more
information on how assign the role of a backup proxy, see Adding Off-Host Backup Proxies. For more
information on how to assign proxies to a replication job, see Specify Data Transfer Settings.

Backup Repository
The backup repository is a component required for the snapshot replica. For more information on replica types,
see VM Replica Types.

The backup repository stores replica metadata that contains information on the read data blocks (such as
checksums and digests). Metadata is required when Veeam Backup & Replication performs incremental
replication or if you fail back from a VM replica to the source VM in the original location using quick rollback.
Veeam Backup & Replication uses metadata to quickly detect changed data blocks between two replica states.

The backup repository must be deployed in the source site, as close to the source host as possible.

For more information, see Backup Repository.

WAN Accelerators
WAN accelerators are optional components in the backup infrastructure for replication. You can use WAN
accelerators if you replicate VMs over a slow connection or over WAN.

In the replication process, WAN accelerators are responsible for global data caching. To use WAN acceleration,
you must deploy two WAN accelerators in the following manner:

• The source WAN accelerator must be deployed in the source side, close to the source host or off -host
backup proxy.

• The target WAN accelerator must be deployed in the target side, close to the target host.

For more information, see WAN Acceleration.

1415 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Replication Scenarios
Veeam Backup & Replication supports a number of replication scenarios. Depending on the scenario you are
planning to use, different backup infrastructure components will be involved in the replication process. For
more information on the components, see Backup Infrastructure for Replication.

• On-host replication. Use this scenario if you want the source Microsoft Hyper-V host to process VM data.
This can result in high CPU usage and network overhead on the host system.

• Off-host replication. Use this scenario if the load on the source Microsoft Hyper-V is high and you want to
shift VM data processing to a dedicated machine — an off-host backup proxy.

Both these scenarios can be used when the source and target hosts are located in the same site (on-site
replication) and in different sites (off-site replication). In both scenarios, you can replicate VM data directly
(between hosts, or off-host proxy and target host) or over a pair of WAN accelerators.

NOTE

With off-site replication, you can also use technologies that help reduce the amount of replication traffic
and streamline replica configuration: replica seeding and mapping, network mapping and re-IP rules.

On-Host Replication
The on-host replication scenario requires the following backup infrastructure components:

• Source host. The source host runs the source Veeam Data Mover. Note that this can cause additional
overhead on the source host.

• Target host. The target host runs the target Veeam Data Mover.

• [For snapshot replica] Backup repository for storing replica metadata.

• [Optional] A pair of WAN accelerators at each end of the WAN link. Use WAN accelerators if the
connection between the hosts is slow.

o Source WAN accelerator must be deployed near the source host. The source WAN accelerator must
have access to the backup server, source host or off-host backup proxy and target WAN accelerator.

o Target WAN accelerator must be deployed near the target host. The target WAN accelerator must
have access to the backup server, source WAN accelerator and target host.

NOTE

Replication over WAN accelerators is supported only for snapshot replicas.

1416 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
During on-host replication, all the necessary data transformations (such as data compression and block filtering)
are performed on the source host.

Off-Host Replication
The off-host replication scenario requires the following backup infrastructure components:

• Source host.

• Off-host backup proxy. The off-host backup proxy must be deployed in the source site and must have
access to the source host and the target host. The off-host backup proxy runs the source Veeam Data
Mover.

• Target host. The target host runs Veeam Data Mover.

• [For snapshot replica] Backup repository for storing replica metadata.

• [Optional] A pair of WAN accelerators at each end of the WAN link. Use WAN accelerators if the
connection between the hosts is slow.

o Source WAN accelerator must be deployed near the source host. The source WAN accelerator must
have access to the backup server, source host or off-host backup proxy and target WAN accelerator.

o Target WAN accelerator must be deployed near the target host. The target WAN accelerator must
have access to the backup server, source WAN accelerator and target host.

NOTE

Replication over WAN accelerators is supported only for snapshot replicas.

1417 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
During off-host replication, all the necessary data transformations (such as data compression and block
filtering) are performed on off-host backup proxy, which helps reduce unwanted overhead on the source host.

1418 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
How Replication Works
Veeam Backup & Replication performs VM replication in the following way:

1. When a new replication job session starts, Veeam Backup & Replication reads job settings from the
configuration database and creates a list of VMs to process. For every disk of a VM added to the job,
Veeam Backup & Replication creates a new task.

2. Veeam Backup & Replication checks what backup infrastructure resources are available, and assigns
backup proxies and backup repositories to process the tasks. Then Veeam Backup & Replication
establishes a connection with source proxy (on-host or off-host), target host and the backup repository,
and sets a number of rules for data transfer, such as network traffic throttling rules and so on.

3. The source proxy (on-host or off-host) establishes a connection with the target host and backup
repository.

4. Veeam Backup & Replication queries information about VMs and virtualization hosts from Microsoft
Hyper-V.

5. If application-aware image processing is enabled for the job, Veeam Backup & Replication connects to VM
guest OSes, deploys non-persistent runtime components or uses (if necessary, deploys) persistent agent
components on VM guest OSes and performs in-guest processing tasks.

6. Veeam Backup & Replication requests Microsoft Hyper-V VSS to create a cohesive point-in-time copy of a
VM. Microsoft Hyper-V VSS creates a volume snapshot or VM checkpoint, depending on the hypervisor
version.

7. The source backup proxy reads the VM data from the volume snapshot or VM checkpoint and copies it.
During incremental job sessions, the source proxy uses changed block tracking (CBT) to retrieve only those
data blocks that have changed since the previous job session. If CBT is not available, the source proxy
interacts with the backup repository to obtain replica metadata, and uses this metadata to detect blocks
that have changed since the previous job session.

While copying VM data, the source proxy performs additional processing. It filters out zero data blocks,
blocks of swap files and blocks of excluded VM guest OS files. The source proxy compresses VM data and
transports it to the target host.

8. The target host decompresses VM data and writes the result to the destination datastore.

9. After the backup proxy finishes reading VM data, Veeam Backup & Replication requests Microsoft Hyper-V
VSS to delete the volume snapshot or VM checkpoint.

1419 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication can resume the replication process if data transfer was not finished, for example, if
the replication job did not finish within the allowed backup window or the network connection failed. On the
next run, Veeam Backup & Replication will continue data transfer for those disks for which
Veeam Backup & Replication has started data processing and created snapshots during the current run.

1420 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Replication Chain
For every VM replica, Veeam Backup & Replication creates a replication chain that consists of restore points.
Veeam Backup & Replication utilizes Microsoft Hyper-V checkpoint capabilities to create and manage replica
restore points.

Veeam Backup & Replication creates a restore point during every replication job session. During the first
replication job session, Veeam Backup & Replication creates a copy of the source VM on the target host. During
every subsequent replication job session, it adds a new checkpoint to the replication chain for the VM replica.
Blocks of data that have changed since the last job run are written to the checkpoint differencing disk, and the
checkpoint differencing disk acts as a restore point. You can view a replication chain created for a VM using
Hyper-V Manager.

You can specify how many restore points you want to store in the replication chain. For this, configure retention
policy settings for the replication job. For more information, see Specify Replication Job Settings.

VM replica restore points are stored in a native Microsoft Hyper-V format next to replica virtual disk files, which
allows Veeam Backup & Replication to accelerate failover operations. To fail over to the necessary point of the
VM replica, Veeam Backup & Replication does not need to apply rollback files. Instead, it uses a native Microsoft
Hyper-V mechanism of applying the checkpoint.

IMP ORTANT

We recommend you against switching restore points for replicas and powering on replicas using Hyper -V
Manager. This may disrupt further replication operations in Veeam Backup & Replication or cause loss of
important data. Instead, use Veeam Backup & Replication to perform failover operations. For more
information on how to fail over to a VM replica, see Failover.

1421 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
VM Replica Types
Veeam Backup & Replication automatically selects what type of VM replica must be created.
Veeam Backup & Replication supports two methods for creating VM replicas:

• Snapshot replica

• Legacy replica

Which type of replica Veeam Backup & Replication uses depends on the following criteria:

• Version of the source Microsoft Hyper-V host

• Version of the target Microsoft Hyper-V host

For more information, see the compatibility table in the Supported Platforms for VM Replica Types section.

Supported Platforms for VM Replica Types


Veeam Backup & Replication automatically selects which type of VM replica to create depending on the versions
of the source and target Microsoft Hyper-V hosts.

New Replication Jobs


If you replicate data between Windows Server Hyper-V 2008 R2 hosts, Veeam Backup & Replication creates
legacy replicas. Note that replication from backups is not supported in this case.

If you replicate data between hosts of later versions, Veeam Backup & Replication creates snapshot replicas.
Note that target VM configuration must be equal or higher than source VM configuration.

For example:

• You configure a replication job with a Microsoft Hyper-V 2008 R2 host used as a source and a Microsoft
Hyper-V 2008 R2 host used as a target. VM data is retrieved from the production storage. In this case, the
replication job will produce a legacy replica.

• You configure a replication job with a Microsoft Hyper-V 2012 R2 host used as a source and a Microsoft
Hyper-V 2016 host used as a target. VM data is retrieved from the production storage. In this case, the
replication job will produce a snapshot replica.

Existing Replication Jobs


After you upgrade Veeam Backup & Replication, legacy replication jobs remain as they are. They do not change
their type to snapshot replication jobs.

After you upgrade Veeam Backup & Replication, replication jobs work as usual. However, if you have legacy
replication jobs that use Microsoft Hyper-V Server 2012 host and later as a target, and these jobs were created
by Veeam Backup & Replication earlier than 9.0, you will not be able to edit these jobs.

Legacy replication jobs can use only the virtual infrastructure as a source of data. Replication from backup is not
supported for legacy replication jobs.

Snapshot Replica
To create snapshot replicas, Veeam Backup & Replication uses Hyper-V VM snapshot capabilities.

1422 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Snapshot replica in many respects is similar to forward incremental backup. During the first run of a replication
job, Veeam Backup & Replication copies the VM running on the source Hyper-V host and creates its full replica
on the target host. The replica is stored decompressed, in a native Hyper -V format.

All subsequent replication jobs are incremental. Veeam Backup & Replication copies only those data blocks that
have changed since the last replication cycle. To keep track of changed data blocks for Hyper-V VMs,
Veeam Backup & Replication uses its proprietary changed block tracking mechanism or resilient changed
tracking (RCT). For more information, see Changed Block Tracking.

For each new incremental run of the replication job, Veeam Backup & Replication triggers a regular snapshot of
the replica. Blocks of data that have changed since the last job run are written to AVHD(X) files. Thus, the
created replica snapshot acts as a new restore point.

As a result, for every replicated VM, Veeam Backup & Replication produces a full replica and a chain of
snapshots, or restore points. The latest snapshot in the chain mirrors the state of the source VM. If the source
VM fails for any reason, you can temporary or permanently fail over to the latest restore point or to an earlier
point in time.

Veeam Backup & Replication creates and maintains the following types of replica files:

• Full VM replica (a set of VM configuration files and virtual disks).

• Replica restore points (VM snapshot files).

• Replica metadata (VBK file) that store VM replica digests. Veeam Backup & Replication uses this file to
quickly detect changed blocks of data between two replica states. For more inf ormation, see Changed
Block Tracking.

The full VM replica along with its restore points is stored in a dedicated folder in the target datastore. Replica
metadata files are stored in a backup repository.

NOTE

Virtual disks of snapshot VM replicas are always dynamically expand.

Legacy Replica
For legacy replicas, Veeam Backup & Replication uses an approach that is similar to reverse incremental backup.

During the first run of a replication job, Veeam Backup & Replication copies the VM running on the source host
and creates its full replica on the target host. The replica is stored decompressed, in a native Hyper -V format.

All subsequent replication jobs are incremental. Veeam Backup & Replication copies only those data blocks that
have changed since the last replication cycle. To keep track of changed data blocks for Hyper -V VMs,
Veeam Backup & Replication uses its proprietary changed block tracking mechanism.

At every incremental job run, Veeam Backup & Replication “injects” changes into the replica to rebuild it to the
most recent state of the source VM. It also creates a rollback file to store data blocks that were replaced when
the full replica was rebuilt.

As a result, for every replicated VM, Veeam Backup & Replication produces a full replica and a chain of rollback
files. The replica mirrors the latest state of the source VM, while rollback files serve as restore points. If you
need to restore a replica to a particular point in time, Veeam Backup & Replication will apply the required
rollback files to get you to that point in time.

Veeam Backup & Replication creates and maintains the following types of replica files:

• Full VM replica (a set of VM configuration files and virtual disks)

• VRB — replica rollback files

1423 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• VBK — file that stores hash data describing the current state of a VM replica on the target host

All files of a legacy replica are stored in a dedicated folder on the target volume.

Limitations for Legacy Replicas


The following limitations apply to the legacy replicas:

• Legacy replicas can use only the virtual infrastructure as a source of data. Replication from backup is not
supported for legacy VM replicas.

• You cannot clone a legacy replication job that replicates a VM from the source Microsoft Hyper -V Server
2008 R2 host to the target Microsoft Hyper-V Server 2012 host or later using the
Veeam Backup & Replication console or Veeam Backup Enterprise Manager web UI.

1424 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Replica Seeding and Mapping
Replica seeding and mapping are technologies that help reduce the amount of traffic sent over a network. With
these technologies, Veeam Backup & Replication do not have to transfer all of VM data from the source host to
the target host across the sites during the first session of a replication job (during the initial re plication).

You can use seeding and mapping in the following scenarios:

• Seeding

Configure replica seeding if, in a backup repository located in the disaster recovery (DR) site, you have
backups of VMs that you plan to replicate. During replication, Veeam Backup & Replication will restore
VMs from these backups and will synchronize the state of the restored VMs with the latest state of the
source VMs. Then Veeam Backup & Replication will use these restored VMs as replicas.

For more information on how to create backups that can be used as "seeds" for replica, see Creating
Replica Seeds.

• Ma pping

Configure replica mapping if, on the host in the DR site, you have ready -to-use copies of the source VMs.
These can be restored VMs or replicas created by other replication jobs. Veeam Backup & Replication will
synchronize the state of these ready-to-use VMs with the latest state of the source VMs and will use these
VMs as replicas. You can also use replica mapping if you need to reconfigure or recreate replication jobs,
for example, split one replication job into several jobs.

You can also configure both replica seeding and replica mapping in the same replication job. For example, if a
replication job includes 2 VMs, you can use seeding for one VM and map the other VM to an existing VM.

IMP ORTANT

If seeding or mapping is enabled in a replication job, all VMs in the job must be covered with seeding or
mapping. If a VM neither has a seed, nor is mapped to an existing VM, it will be skipped from processing.

Algorithm for Seeding


Replica seeding includes the following steps:

1. As a preparatory step for replica seeding, you need to create a backup of a VM that you plan to replicate.
For more information on how to create a backup that will be used as a "seed" for replica, see Creating
Replica Seeds.

2. When you create a replication job, you should point it to a backup repository in the DR site. During the
initial synchronization, Veeam Backup & Replication accesses the backup repository where the replica seed
is located, and restores the VM from the backup. The restored VM is registered on the target host in the
DR site. Files of the restored VM are placed to the location you specify as the replica destination stor age.

Virtual disks of a replica are restored from the backup as dynamically expanding.

3. Veeam Backup & Replication synchronizes the restored VM with the latest state of the source VM.

After successful synchronization, in the Home view in the Veeam Backup & Replication console, under
Rep licas node you will see a VM replica with two restore points. One point will contain the state of the VM
from the backup file; the other point will contain the latest state of the source VM you want to replicate.

1425 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. During incremental synchronization, Veeam Backup & Replication transfers only incremental changes in a
regular manner.

Replica seeding dramatically reduces traffic sent over WAN or slow connections because
Veeam Backup & Replication does not send the full contents of the VM image. Instead, it transmits only
differential data blocks.

TIP

If you add new VMs to an already existing replication job, you can enable replica seeding settings for these
VMs. In this case, the newly added VMs will be seeded from the selected backups at the next pass of the
replication job. VMs that have already been processed by the job by the time you add new VMs will be
processed in a regular manner.

Algorithm for Mapping


Replication to a mapped VM is performed in the following way:

1. During the first run, the replication job calculates the differences between the source and mapped VM.
Instead of copying and transferring all data of the source VM, the replication job transfers only
incremental changes to synchronize the state of the mapped VM with the state of the source VM.

After successful synchronization, in the Home view of Veeam Backup & Replication, under Rep licas node
you will see a VM replica with 2 restore points:

o One restore point will contain the latest state of the mapped VM.

o The other restore point will contain the latest state of the source VM on the source host.

1426 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. All subsequent runs of the replication job will be performed in a regular manner:
Veeam Backup & Replication will transfer only incremental changes to the target host.

Replica Mapping for VMs with Checkpoints


[For legacy replicas] The legacy VM replica to which you map the source VM must not have any checkpoints.
Otherwise, replica mapping will not work.

[For snapshot replicas] If a snapshot replica to which you map the source VM has any checkpoints that were
created by Veeam Backup & Replication, for example, with a replication job run on another backup server,
Veeam Backup & Replication will identify these checkpoints as valid restore points for the VM rep lica and,
additionally, will create one new restore point during the first run of the replication job. For example, if a VM
replica on the target host has 3 checkpoints created by Veeam Backup & Replication, after the first run of the
replication job, you will have a VM replica with 4 valid restore points.

If a snapshot replica to which you map the source VM has any checkpoints that were created outside
Veeam Backup & Replication, for example, triggered manually by the user, Veeam Backup & Replication will not
identify them as valid restore points. During the first run of the replication job, Veeam Backup & Replication will
create 2 new restore points as described in the procedure above.

For example, if a VM replica has 2 checkpoints created in Hyper-V Manager, after the first run of the replication
job, you will have a VM replica with 2 restore points. 2 checkpoints created in Hyper -V Manager will remain in
the checkpoint chain. However, you will not be able to see these checkpoints in the Veeam Backup & Replication
console and will not be able to use these checkpoints for failover and failback operations.

1427 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Replica from Backup
Disaster recovery plans often require that you back up and replicate the same VM for disaster recovery (DR) and
high availability (HA) purposes. As a rule, this doubles the workload on the virtual infrastructure: two VM
snapshots need to be created independently from one another, and VM data need to be transferred from the
production site twice.

To minimize the use of compute, storage and network resources, you can use the replica from backup option.
You can use this option in both on-site and off-site replication scenarios.

When you perform replication from backup, Veeam Backup & Replication does not address hosts and storage in
the production environment to read VM data. As a source of data, Veeam Backup & Replication uses a backup
chain that already exists in a backup repository. As a result, Veeam Backup & Replication creates only one
snapshot and transfers VM data only once. Veeam Backup & Replication retrieves VM data only while a backup
or backup copy job is running. The replication job re-uses retrieved data to build VM replica restore points.

Differences between Seeding and Replica from Backup


Although replica from backup may resemble replica seeding, there is difference between these options:

• Replica seeding uses a backup file only during the first run of a replication job. To further build VM replica
restore points, the replication job addresses the production environment and reads VM data from the
source storage.

• Replica from backup uses a backup chain in a backup repository as the only source of data. When building
a new VM replica restore point, Veeam Backup & Replication always reads data from the latest restore
point in the backup chain, either full or incremental. The backup chain in the backup repository may be
created by a backup job or a backup copy job.

Requirements and Limitations for Replica from Backup


Consider the following requirements and limitations:

• You can perform replication only from backups of Microsoft Hyper-V virtual machines created with
Veeam Backup & Replication.

• Replica from backup is not supported if you replicate data between Windows Server Hyper -V 2008 R2
hosts.

• Replica from backup processes disks sequentially, not in parallel.

• Replica from backup can use the following backups only:

o Backups that backup jobs or backup copy jobs create. These jobs must be configured on the same
backup server where you configure the replication job.

o Backups to which backup jobs or backup copy jobs are mapped. These jobs must be configured on the
same backup server where you configure the replication job.

• The jobs mentioned in the previous list items must run periodically and produce new restore points.
Otherwise, the replication job will have no data to retrieve and replicas will be in an outdated state.

• Replica from backup cannot use imported backups. However, there may be a situation when you need to
use backups created on another backup server. In this case, use the instructions provided in Using Backups
Created on Crashed Backup Server. Note that the backup server from which you import backups must not
operate anymore, otherwise replica from backup may behave in an unexpected way.

1428 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• [For backups stored on scale-out backup repositories] Replica from backup ignores backups stored in a tier
other than the performance tier.

How Replica from Backup Works


Replica from backup is performed along with a regular replication job. When you set up a replication job, you
define a backup repository with VM backups as a source of data. If the backups for this VM are available in
different backup repositories, you can select several backup repositories as a source. In this case,
Veeam Backup & Replication will look for the latest VM restore point across these backup repositories.

For example, you configure two backup jobs that process the same VM, and target these jobs at two different
backup repositories. The backup jobs create the following backup files:

• Backup job 1 creates 2 restore points in Backup repository 1: full backup file on Sunday and incremental
backup file on Tuesday.

• Backup Job 2 creates 1 restore point in Backup repository 2: full backup file on Monday.
The replication job is configured to retrieve VM data from backups and is scheduled to run daily. In this case, the
replication job retrieves VM data from backups in the following way:

1. On Sunday, the replication job retrieves VM data from the full backup file in Backup repository 1.

2. On Monday, the replication job retrieves VM data from the full backup file in Backup repository 2.

3. On Tuesday, the replication job retrieves VM data from the incremental backup file in Backup repository 1.

4. Till next Sunday, the replication job does not retrieve any VM data because backup files are not created.

In some cases, a new restore point in the backup repository may not be created by the time a replication job
starts. In this case, Veeam Backup & Replication displays a warning notifying that the latest restore point has
already been replicated. The replication job session finishes with the Warning status.

In some cases, Veeam Backup & Replication can resume the replication process if data transfer was not finished,
for example, because of the network disconnection. On the next run, Veeam Backup & Replication will continue
data transfer for those disks for which Veeam Backup & Replication has started data processing and created
snapshots during the current run.

1429 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

When you replicate a VM over a production network, Veeam Backup & Replication retrieves VM data as of
the latest VM state. When you replicate a VM from backup, Veeam Backup & Replication retrieves VM data
as of the point in time when the backup was created. The VM replica restore point has the same timestamp
as a VM backup restore point, not the time when the replica job session is run.

Using Backups Created on Crashed Backup Server


There may be a situation when you created backups on one backup server, the server crashed and you want to
use these backups for replica from backup on another backup server.

Veeam Backup & Replication considers backups created on other backup servers as imported backups. Replica
from backups cannot use imported backups, that is why you need to perform the following steps to use backups
created on the crashed server:

1. Import the backups to the backup server where you create the replication job. You have several options:

o You can connect the repository where the backups are stored to the backup server and then rescan
the repository.

o You can copy backups to a backup repository already added to the backup server and then rescan the
repository.

o You can copy backups to a backup repository already added to the backup server. Then edit repository
settings and select the Search the repository for existing backups and import them automatically
check box at the Review step of the wizard.

2. Create a new backup job or a backup copy job and map the imported backups to it. For more information
on how to map backups, see Specify Backup Storage Settings.

After you map a backup to a job, Veeam Backup & Replication stops considering the backup as imported.

3. Create a replication job. In the job settings, specify that you want to use backups as a data source and
select the backup repository where the imported backups reside. For more information, see Specify Data
Source.

IMP ORTANT

Consider the following:

• The backup job or backup copy job to which you map the imported backup file must run periodically
and produce new restore points. Otherwise, the replication job will have no data to retrieve and
replicas will be in an outdated state.
• No other running backup servers must use the imported backups.

1430 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Replication Jobs
To create VM replicas, you must configure a replication job. The replication job defines how, where and when to
replicate VM data. One job can be used to process one VM or multiple VMs.

To create a replication job, use the New Replication Job wizard.

1431 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you create a replication job, check the following prerequisites:

• Check requirements and limitations in the Requirements and Limitations and VMs sections.

• Host and target Microsoft Hyper-V hosts that you select for the replication process must be compatible.
For more information, see Supported Platforms for VM Replica Types.

• Backup infrastructure components that will take part in the replication process must be added to the
backup infrastructure and properly configured. These include source and target Microsoft Hyper -V hosts
and backup repository for storing replica metadata. If you want to perform backup in the off -host backup
mode, the off-host backup proxy must also be added and properly configured.

The backup server must be able to resolve short names and connect to source and target virtualization
hosts.

• The target volume must have enough free space to store disks of replicated VMs. To receive alerts about
low space on the target volume, configure global notification settings. For more information, see
Specifying Other Notification Settings.

• If you plan to replicate VMs using WAN accelerators, source and target WAN accelerators must be added
to the backup infrastructure and properly configured. For more information, see Adding WAN
Accelerators.

• If you plan to replicate VMs using WAN accelerators, it is recommended that you pre-populate the global
cache on the target WAN accelerator before you start the replication job. Global cache population helps
reduce the amount of traffic transferred over WAN. For more information, see Populating Global Cache.

• If you plan to replicate VMs from the backup, the backup job that you plan to use as the source must be
configured beforehand. For more information, see Replica from Backup.

• If you plan to use pre-job, post-job, pre-freeze or post-thaw scripts, you must create scripts before you
configure the replication job. For the supported script format, see Pre-Freeze and Post-Thaw Scripts.

1432 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Replication Job Wizard
To run the New Replication Job wizard, do one of the following:

• On the Home view. On the ribbon, click Rep lication Job > Virtual machine > Microsoft Hyper-V.

• Open the Home view. In the inventory pane right-click the Job s node and select Rep lication > Virtual
ma chine > Microsoft Hyper-V.

• Open the Inventory view. In the working area, select VMs that you want to replicate and right-click one of
them. Select Ad d to replication job > New job if you want to create a new replication job, or Ad d to
rep lication job > <Job Name> if you want to add VMs to an existing replication job.

1433 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Job step of the wizard, specify a job name and description, and configure advanced settings for the
replication job.

1. In the Na me field, enter a name for the replication job.

2. In the Description field, provide a description for future reference.

3. If a network between your production and disaster recovery (DR) sites has low bandwidth, and you want
to reduce the amount of traffic sent during the first run of the replication job, select the Rep lica seeding
( for low bandwidth DR sites) check box.

When selected, this check box enables the Seeding step where you will have to configure replica seeding
and mapping. For more information on seeding and mapping, see Replica Seeding and Mapping.

4. If your DR site networks do not match your production site networks, select the Network remapping (for
DR sites with different virtual networks) check box.

When selected, this check box enables the Network step where you will have to configure a network
mapping table.

5. If the IP addressing scheme in your production site differs from the scheme in the DR site, select the
Rep lica re-IP (for DR sites with different IP addressing scheme) check box.

When selected, this check box enables the Re-IP step where you will have to configure replica re-IP rules.

6. If you want the resource scheduler of Veeam Backup & Replication to prioritize this job higher than other
similar jobs and to allocate resources to it in the first place, select the Hig h priority check box. For more
information on job priorities, see Job Priorities.

TIP

In the UI, jobs with the Hig h priority option enabled will be marked with a special flag ( ).

1434 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1435 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select VMs to Replicate
At the Virtual Machines step of the wizard, select VMs and VM containers (Hyper-V hosts, clusters, SCVMM,
SCVMM tags, SCVMM host groups, VM groups, or volumes) that you want to replicate:

1. Click Ad d .

2. In the Ad d Object window, select the necessary VMs or VM containers and click Ad d . If you select VM
containers and add new VMs to this container in future, Veeam Backup & Replication will update
replication job settings automatically to include these VMs.

You can use the toolbar at the top right corner of the window to switch between views. Depending on the
view you select, some objects may not be available. For example, if you select the VMs a nd Tags view, no
hosts or clusters will be displayed in the tree. Note that VM Groups view is applicable for Microsoft Hyper-
V hosts version 2016 or later.

To quickly find the necessary VMs, you can use the search field at the bottom of the Ad d Object window. If
you want to switch between types of VMs you want to search through, use the button to the left of the
search field.

The total size of objects added to the job is displayed in the Tota l size field. Use the Recalculate button to
refresh the total size value after you add a new object to the job.

1436 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Data Source
You can select a data source from which Veeam Backup & Replication will read VM data:

1. At the Virtual Machines step of the wizard, click Source.

2. In the Source Repositories window, select one of the following options:

o From production storage. In this case, Veeam Backup & Replication will retrieve VM data from
datastores connected to the source Microsoft Hyper-V host.

o From backup files. In this case, Veeam Backup & Replication will read VM data from the backup chain
already existing in the selected backup repository. This option can be used in the replica from backup
scenario. For more information, see Replica from Backup.

1437 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Exclude Objects from Replication Job
After you have added VMs and VM containers to the replication job, you can specify which objects you want to
exclude from replicas. You can exclude the following types of objects:

• VMs or VM containers

• VM disks

Excluding VMs or VM Containers


To exclude VMs from a VM container:

1. At the Virtual Machines step of the wizard, click E x clusions.

2. In the E x clusions window, check that the VMs tab is selected and click Ad d .

3. In the Ad d Objects window, select VMs or VM containers that you want to exclude from being replicated
and click Ad d .

You can use the toolbar at the top right corner of the window to switch between views. Depending on the
view you select, some objects may not be available. For example, if you select the VMs a nd Templates
view, no resource pools, hosts or clusters will be displayed in the tree.

You can use the toolbar at the top right corner of the window to switch between views. Depending on the
view you select, some objects may not be available. For example, if you select the VMs a nd Tags view, no
hosts or clusters will be displayed in the tree. Note that VM Groups view is applicable for Microsoft Hyper-
V hosts version 2016 or later.

You can also use the Show full hierarchy check box to display the hierarchy of all Hyper-V Servers added
to the Veeam Backup & Replication infrastructure.

4. Click OK.

1438 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Excluding Disks
To exclude VM disks:

1. At the Virtual Machines step of the wizard, click E x clusions.

2. In the E x clusions window, do the following:

a. Switch to the Disk s tab.

b. If you want to exclude disks of VMs that are added as a part of containers, click Ad d . In the Ad d
Ob jects window, select the necessary VMs and click Ad d . Veeam Backup & Replication will include
these VMs in the list as standalone objects.

c. In the Disks to process list, select VMs or VM containers whose disks you want to exclude.

d. Click E d it.

3. In the Select Disks window, select disks that you want to replicate: all disks, 0:0 disks (as a rule, system
disks) or specific IDE or SCSI. Disks that you do not select will be excluded from processing. Click OK.

4. In the E x clusions window, click OK.

NOTE

If you exclude disks from being replicated and enable application-aware processing, Microsoft VSS
framework will still process the disks and volumes on which the disks are located.

1439 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify VM Replication Order
At the Virtual Machines step of the wizard, click Up and Down to change the processing order. VMs at the top of
the list have a higher priority and will be processed first.

Setting VM order can be helpful, for example, if you have added some mission-critical VMs to the job and want
the job to process them first. You can set these VMs first in list to ensure that their processing fits the backup
window.

NOTE

Consider the following:

• VMs inside a VM container are processed at random. To ensure that VMs are proce ssed in the
defined order, you must add them as standalone VMs, not as a part of containers.
• The processing order may differ from the order that you have defined. For example, if resources of a
VM that is higher in the priority are not available, and resources of a VM that is lower in the priority
are available, Veeam Backup & Replication will process the VM with the lower priority first.
If you enable the Allow processing of multiple VMs with a single volume snapshot option in the
Advanced Replica Settings, VMs may also be processed in a different order. This option unites VMs
added to the job in several groups, and the defined VM order may be broken.

1440 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Replica Destination
At the Destination step of the wizard, select a destination for replicas:

1. Next to the Host or cluster field, click Choose and select a host or cluster where replicas must be
registered. If you select a cluster as a target, the replication process will become more sustainable — the
replication process will not fail if there is at least one available host in the cluster.

2. Next to the P a th field, click Choose and specify a path to the folder where VM replica files must be stored.
By default, Veeam Backup & Replication stores VM replica files to the C:\Replicas folder (if you have
selected a Microsoft Hyper-V host as a target) or on a CSV with the maximum amount of free space (if you
have selected a Microsoft Hyper-V cluster as a target).

You can specify the following folders:

a. An existing folder on a host.

b. A new folder on a host. To do this, in the Select Folder window, select a location where the folder
must be created. Click New Folder and specify a folder name.

c. A Microsoft SMB3 shared folder. To do this, in the search field at the bottom of the Select Folder
window, enter a path to the Microsoft SMB3 shared folder. The path must be specified in the UNC
format, for example: \\172.16.11.38\Share01.

The host or cluster you specify in the Host or cluster field must have access to the Microsoft SMB3
shared folder. If you are using Microsoft SCVMM 2012 or Microsoft SCVMM 2012 R2, the server
hosting the Microsoft SMB3 share must be registered in Microsoft SCVMM as a storage device. For
more information, see Microsoft Docs.

If you have selected to replicate multiple VMs and want to place individual replicas to other folders:

a. Click the P ick VM folder for selected replicas link.

b. In the Choose VM Files Location window, click Ad d.

c. In the Ad d Objects window, select the necessary VMs and click Ad d .

d. In the Choose VM Files Location window, select the necessary VMs in the Files Location list. At the
bottom of the window, click P a th.

e. In the Select Folder window, select the necessary folder or create a new one. Click OK.

f. In the Choose VM Files Location window, click OK.

3. If you want to store replica configuration files and disk files in different locations:

a. Click the P ick path for selected virtual disks link.

b. In the Choose VM Files Location window, click Ad d.

c. In the Ad d Objects window, select the necessary VMs and click Ad d .

d. In the Choose VM Files Location window, expand the necessary VMs in the Files location list, and
select the necessary files. At the bottom of the window, click P a th.

e. In the Select Folder window, select the destination for the selected type of files. Click OK.

f. In the Choose VM Files Location window, click OK.

1441 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• After a replication job finishes, you can change the target location for replica files. However, the
target will be changed only for newly added files — new replica files if you change the path and new
VMs if you change the host. The target for "old" files will not be changed.
To change the location for "old" files, disable the replication job, change the target location and
remove the replicas from the configuration. Then migrate the replicas to the specified location,
register the migrated VMs and map the replication job to these VMs. Alternatively, you can remove
replicas and start the job. The replica files will be created anew.
• Disks added to the source VM after the job has already run are replicated to a <GUID> subfolder in
the selected destination. This helps avoid confusion with identically named disks of other machines.
If you want to place new disks to the selected destination without the subfolder, specify the disk
destination explicitly using the P ick path for selected virtual disks option.

1442 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Create Network Map Table
The Network step of the wizard is available if you have selected the Network remapping option at the Job step
of the wizard.

At the Network step of the wizard, configure a network mapping table. This table maps networks in the
production site to networks in the disaster recovery (DR) site. When the job starts, Veeam Backup & Replication
will check the network mapping table. Then Veeam Backup & Replication will update replica configuration files
to replace the production networks with the specified networks in the DR site. As a result, you will not have to
re-configure network settings manually.

To add a row to a network mapping table:

1. Click Ad d .

2. In the Network Mapping window, click Browse next to the Source network field.

3. In the Select Network window, select the production network to which the source VMs are connected and
click OK.

4. In the Network Mapping window, click Browse next to the Ta rget network field.

5. In the Select Network window, select a network in the DR site to which replicas will be connected and
click OK.

6. If you use VLAN IDs for networking, select the VLAN ID check box and specify VLAN IDs of the source and
target networks.

NOTE

For the source and target network, VLAN ID set to 0 refers to different values:

• For the source network, 0 refers to any VLAN including the disabled ones.
• For the target network, 0 means VLAN is disabled.

1443 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1444 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Configure Re-IP Rules
The Re-IP step of the wizard is available if you have selected the Rep lica re-IP option at the Job step of the
wizard. This step applies only to VMs with Microsoft Windows OSes.

At the Re-IP step of the wizard, configure re-IP rules. These rules map IPs in the production site to IPs in the
disaster recovery (DR) site. When you perform failover, Veeam Backup & Replication will check the configured
re-IP rules and will change replica IPs if the rules apply. VM replicas will get new IP add resses according to the
network masks specified in the rules, so that you will be able to reach replicas in the DR site.

To configure a re-IP rule:

1. Click Ad d and select whether you want to configure an IPv4 or IPv6 rule. Note that you can use IPv6
addresses only if IPv6 communication is enabled as described in section IPv6 Support.

2. In the Source VM section, specify an IP numbering scheme used in the production site.

To facilitate the configuration, Veeam Backup & Replication detects an IP address and subnet mask for the
backup server and pre-populates values in the Source VM section.

3. In the Ta rget VM section, specify an IP address, subnet mask and default gateway that will be used for
replicas in the DR site. If required, specify the DNS server addresses. For the IPv4 rules, you can also
specify WINS server addresses.

4. In the Description field, provide a description.

5. Click OK.

NOTE

Consider the following:

• You can specify static IPs or IP ranges. Do not use 0 to specify IP address ranges. In
Veeam Backup & Replication, value 172.16.17.0 means a regular IP address 172.16.17.0, not an IP
address range. To specify a range, use the asterisk character (*).
• Replica re-IP works only if you perform replica failover using Veeam Backup & Replication. If you
power on a VM replica in some other way, for example, manually using Hyper -V Manager, re-IP rules
will not be applied to it.
• The backup server OS must support mounting of the system disks of VMs that will be replicated.

1445 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1446 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Specify Replication Job Settings
At the Job Settings step of the wizard, specify a backup repository for storing replica metadata, replica name
and number of restore points to keep:

1. From the Rep ository for replica metadata list, select a backup repository that will store metadata for VM
replicas.

This setting must be specified only for snapshot replicas. Legacy replicas do not use a backup repository
for storing metadata. For more information, see VM Replica Types.

IMP ORTANT

Consider the following:

• You cannot store VM replica metadata on deduplicating storage appliances. During replication
jobs, Veeam Backup & Replication frequently reads and writes small portions of metadata
from/to the backup repository. Frequent access to metadata causes low performance of
deduplicating storage appliances, which may result in low performance of replication jobs.
• You cannot store replica metadata in a scale-out backup repository.

2. In the Rep lica name suffix field, enter a suffix that will be added to the source VM names. To register a VM
replica on the target host, Veeam Backup & Replication appends the specified suffix to the name of the
source VMs.

3. In the Restore points to keep field, specify the number of restore points that the replication job must
maintain. Due to Microsoft Hyper-V restrictions on the number of VM snapshots, the maximum number of
restore points for snapshot replicas is limited to 47. When the specified number is exceeded,
Veeam Backup & Replication removes the earliest restore points.

1447 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Specify Advanced Replica Settings
At the Job settings step of the wizard, you can specify the following settings for the replication job:

• Traffic settings

• Notifications settings

• Hyper-V settings

• Script settings

TIP

After you specify the necessary settings for the replication job, you can save them as default settings. To
do this, click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create
a new replication job, Veeam Backup & Replication will automatically apply the default settings to the new
job.

Traffic Settings
You can optimize data traffic sent over network by specifying which data you want to replicate, data
compression level and optimize the job performance and storage usage:

1. At the Job Settings step of the wizard, click Ad vanced.

2. In the Ad vanced Settings window, check that the Tra ffic tab is selected.

3. [For Microsoft Windows NTFS] By default, Veeam Backup & Replication excludes data blocks of the
hiberfil.sys and pagefile.sys system files from replicas. For more information on how
Veeam Backup & Replication excludes data blocks of these system files, see Swap Files.

If you want to include data blocks of the hiberfil.sys and pagefile.sys system files into replicas,
clear the E x clude swap file blocks check box. Note that including these files into replicas will increase
their size.

4. By default, Veeam Backup & Replication does not copy deleted file blocks ("dirty" blocks on the VM guest
OS) to the target location. For more information, see Deleted File Blocks.

If you want to include dirty data blocks into VM replicas, clear the E x clude d eleted file blocks check box.
Note that including these files into replicas will increase their size.

5. From the Compression level list, select a compression level for VM replicas. For more information on data
compression and compressions levels, see Data Compression.

6. In the Storage optimization section, select block size that will be used to process VMs. For more
information on the data blocks sizes and how they affect performance, see Storage Optimization.

1448 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
7. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Notification Settings
To specify notification settings for the replication job:

1. At the Job Settings step of the wizard, click Ad vanced.

2. In the Ad vanced Settings window, click the Notifications tab.

3. To receive SNMP traps when the job completes successfully, select the Send SNMP notifications for this
job check box.

SNMP traps will be sent if you configure global SNMP settings in Veeam Backup & Replication and
configure software on recipient machine to receive SNMP traps. For more information, see Specifying
SNMP Settings.

4. To receive notifications by email in case of job failure, success or warning, select the Send email
notifications to the following recipients check box. Then configure notification settings:

a. Check that you have configured global email notification settings as described in section Configuring
Global Email Notification Settings.

b. In the text field, specify a recipient email address. If you want to specify multiple addresses, separate
them by a semicolon.

c. To use global notification settings, select Use global notification settings.

d. To specify a custom notification subject and redefine at which time notifications must be sent, select
Use custom notification settings specified below. Then specify the following settings:

1449 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %JobResult%, %JobName%, %ObjectCount% (number of VMs in the job),
%Issues% (number of VMs in the job that have been processed with the Warning or Failed
status) and %Time% (completion time).

ii. Select the Notify on success, Notify on error or Notify on warning check boxes to receive an
email notification if the job gets the Warning , Success or Error status.

iii. Select the Sup press notifications until the last retry check box to receive the notification
about the final job status. If you do not enable this option, Veeam Backup & Replication will
send one notification per every job retry.

5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Hyper-V Settings
To specify Hyper-V settings for the replication job:

1. At the Job Settings step of the wizard, click Ad vanced.

2. In the Ad vanced Settings window, click the Hy p er-V tab.

3. In the Guest quiescence section, do the following:

a. If VMs added to the replication job do not support Microsoft VSS framework or you want to use native
Microsoft Hyper-V method for guest quiescence, select the E nable Hyper-V guest quiescence check
box.

Veeam Backup & Replication will select the quiescence method in the following way:

1450 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ If a VM meets all requirements for online backup, Veeam Backup & Replication will use the
online backup method. For more information on the method, its requirements and limitations,
see Online Backup.

▪ If a VM does not meet requirements for online backup, Veeam Backup & Replication will use the
offline backup method. Note that during offline backup a VM is suspended for a short period of
time. For more information the method, its requirements and limitations, see Offline Backup.

NOTE

We recommend you to enable also application-aware processing. If it is enabled for the job,
Veeam Backup & Replication first attempts to use the application-aware processing to prepare
VMs for replication. If Veeam Backup & Replication manages to quiesce all VMs in the job with
application-aware processing, it does not use Microsoft Hyper-V guest quiescence. If some VMs
cannot be quiesced with application-aware processing, Veeam Backup & Replication uses
Microsoft Hyper-V guest quiescence.

b. If you do not want to suspend VMs, select the Ta k e crash consistent backup instead of suspending VM
check box. In this case, Veeam Backup & Replication will create crash-consistent VM replicas.

4. In the Cha nged block tracking section, specify if you want to use changed block tracking (CBT) for VM
replication. For more information on CBT, see Changed Block Tracking.

5. If you have added several VMs to the job, select the Allow processing of multiple VMs with a single
volume snapshot check box. This option helps reduce snapshot workload in the Microsoft Hyper -V
environment. When the job starts, Veeam Backup & Replication will group VMs and trigger Microsoft
Hyper-V to create one volume snapshot for a group of VMs, instead of creating a volume snapshot per
each processed VM.

Veeam Backup & Replication can create a single volume snapshot for a group of VMs that meet the
following requirements:

o VMs must be located on the same host.

o Volumes on which VM files reside must use the same VSS provider for snapshot creation.

o The number of VMs in the group is limited: for VSS software provider — 4 VMs, for VSS hardware
provider — 8 VMs.

o Veeam Backup & Replication groups VMs based on the method of snapshot creation that is used for
replication: transactionally consistent (VSS) or crash-consistent.

For example, you add to the job two VMs that are registered on the same host. VM1 resides on volume
C:\ and VM2 resides on volume D:\. Both VMs use Microsoft Software Shadow Copy Provider. In this
situation, Veeam Backup & Replication will create a single snapshot for these VMs.

6. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

NOTE

The Allow processing of multiple VMs with a single volume snapshot option is not applicable to VMs
registered on Microsoft Hyper-V Server 2016 and later that are processed in the onhost backup mode.

1451 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Script Settings
To specify script settings for the replication job:

1. At the Job Settings step of the wizard, click Ad vanced.

2. In the Ad vanced Settings window, click the Scripts tab.

3. If you want to execute custom scripts before or after the replication job, select the Run the following
script before the job or Run the following script after the job check boxes. Click Browse to choose
executable files from a local folder on the backup server. The scripts will be executed on the backup
server.

4. Configure when to execute pre- and post-replication scripts:

o To execute scripts after a number of job sessions, select the Run scripts every... backup session option
and then specify the number of the replication job sessions.

o To execute scripts on specific week days, select the Run scripts on selected days only option. Click
Da y s and specify week days on which scripts must be executed.

1452 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• Custom scripts that you define in the advanced job settings relate to the job itself, not the VM
quiescence process. To add pre-freeze and post-thaw scripts for VM image quiescence, use the
Guest Processing step of the wizard.
• If you select the Run scripts on the selected days only option, Veeam Backup & Replication executes
scripts only once on each selected day — when the job runs for the first time. During subsequent job
runs, scripts are not executed.
• To run the script, Veeam Backup & Replication uses the Service Account under which the Veeam
Backup Service is running.

1453 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Specify Data Transfer Settings
At the Da ta Transfer step of the wizard, select backup infrastructure components that must be used for the
replication process and choose a path for VM data transfer:

1. Specify which backup proxies you want to use:

o If you want Veeam Backup & Replication to use off-host backup proxies for the replication, leave the
Off-host backup mode selected. In this mode, all data processing operations are moved to the off -
host backup proxy from the source host.

By default, Veeam Backup & Replication selects the off-host backup proxies automatically.
Veeam Backup & Replication analyzes the current load on off-host backup proxies and proxy settings
(such as the number of allowed tasks, connectivity to the source volumes) and selects the most
appropriate proxy. You can explicitly select which off-host backup proxies the job must use. To do
this, click Choose. In the Ba ckup Proxy window, select the Use the following backup proxy servers
only check box and choose one or multiple off-host backup proxies from the list. We recommend you
select at least two off-host backup proxies to ensure that the replication job starts if one of the
proxies fails or loses its connectivity to the source volumes.

By default, if there are no off-host backup proxies available when the job starts,
Veeam Backup & Replication automatically fails over to the on-host backup mode. To disable failover,
in the Ba ckup Proxy window, clear the Fa ilover to on-host backup mode if no suitable off-host proxies
a vailable check box. If you disable this option, you must check off-host backup proxies in the backup
infrastructure before the job starts. The job will not be able to start if off-host backup proxies are not
available or not configured properly.

o If you want to use the Microsoft Hyper-V host as the source host and backup proxy, click Choose and
select On-host backup in the Ba ckup Proxy window. In this mode, all data processing operation are
performed directly on the source host, which helps streamline data retrieval operations but puts
additional load on the host.

If the job processes a VM whose disks are located on the CSV and Microsoft CSV Software Shadow
Copy Provider is used for snapshot creation, the Microsoft Hyper-V host that owns the CSV will be
used as the on-host backup proxy.

2. Select a path for VM data transfer:

o If you replicate data over the LAN or fast connections, select Direct. In this case,
Veeam Backup & Replication transfers data directly from the on-host/off-host backup proxy to the
target volume.

o If you have a weak WAN link, select Through built-in WAN a ccelerators. In this case,
Veeam Backup & Replication transfers data using the selected WAN accelerators. From the Source
W AN a ccelerator list, select the WAN accelerator configured in the source site. From the Ta rget WAN
a ccelerator list, select the WAN accelerator configured in the target site.

For more information on where backup infrastructure components must be placed, see Replication
Scenarios.

1454 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

You should not assign one source WAN accelerator to several replication jobs that you plan to run
simultaneously. The source WAN accelerator requires a lot of CPU and RAM resources, and does not
process multiple replication tasks in parallel. As an alternative, you can create one replication job for
all VMs you plan to process over one source WAN accelerator.

The target WAN accelerator, however, can be assigned to several replication jobs. For more
information, see Adding WAN Accelerators.

1455 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 13. Define Seeding and Mapping Settings
The Seeding step is available if you have selected the Rep lica seeding check box at the Job step of the wizard.

At the Seeding step of the wizard, configure replica seeding and mapping. Seeding and mapping help reduce the
amount of traffic sent during the initial replica synchronization. For more information on when to use seeding
and mapping, see Replica Seeding and Mapping.

If you use replica seeding or mapping, make sure that you select correct backup infrastructure components for
the job: source-side backup repository for metadata and backup proxies. It is recommended that you explicitly
assign backup proxies in the production site and disaster recovery (DR) site. For more information, see Specify
Data Transfer Settings.

IMP ORTANT

If the Rep lica seeding check box is enabled in a replication job, all VMs in the job must be covered with
seeding or mapping. If a VM is neither has a seed, nor is mapped to an existing VM, it will be skipped from
processing.

Configuring Replica Seeding


To configure replica seeding:

1. Make sure that you have backups of replicated VMs in a backup repository in the DR site. If you do not
have the backups, create them as described in section Creating Replica Seeds.

IMP ORTANT

Consider the following:

• Backups must be created by Veeam Backup & Replication.


• Backups must not reside in a scale-out backup repository.

2. In the Initial seeding section, select the Get seed from the following backup repository check box.

3. From the list of available backup repositories, select the repository where your replica seeds are stored.

NOTE

If a VM has a seed and is mapped to an existing replica, replication will be performed using replica mapping
because mapping has a higher priority.

Configuring Replica Mapping


To configure replica mapping:

1. Select the Ma p replicas to existing VMs check box.

2. If you want Veeam Backup & Replication to scan the DR site to detect existing copies of VMs that you plan
to replicate, click Detect.

If any matches are found, Veeam Backup & Replication will populate the mapping table. If
Veeam Backup & Replication does not find a match, you can map a VM to its copy manually.

3. If you want to map a VM manually, select a source VM from the list, click E d it and select the copy of this
VM on the target host in the DR site.

1456 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If there is no existing VM replica in the DR site, you can restore a VM from the backup and map it to the source
VM.

To remove a mapping association, select a VM in the list and click Remove.

NOTE

The mapping list does not display VMs added to the list of exclusions. For more information, see Exclude
Objects from Replication Job.

1457 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 14. Specify Guest Processing Settings
At the Guest Processing step of the wizard, enable guest OS processing that allows you to create transactionally
consistent replicas, exclude files from processing, and use pre-freeze and post-thaw scripts. For more
information on guest OS processing, see the Guest Processing section.

To enable guest OS processing:

1. Select E na ble application-aware processing.

2. If you have added Microsoft Windows VMs to the job, specify which guest interaction proxy
Veeam Backup & Replication can use to perform different guest processing tasks:

o If you want Veeam Backup & Replication to select the guest interaction proxy automatically, leave
Automatic selection on the Guest interaction proxy field.

o If you want to explicitly specify which servers will perform the guest interaction proxy role, click
Choose. In the Guest Interaction Proxy window, click P refer the following guest interaction proxy
server, and select the necessary proxies.

For more information on the guest interaction proxy,requirements and limitations for it, see Guest
Interaction Proxy.

3. From the Guest OS credentials list, select a user account that has enough permissions. For more
information on the permissions and requirements for the user account, see Permissions for Guest
Processing.

Veeam Backup & Replication will use the account to connect to guest OSes and deploy the non-persistent
runtime components or use (if necessary, deploy) persistent agent. For more information on gues t agent
and non-persistent components, see Non-Persistent Runtime Components and Persistent Agent
Components.

If you have not set up credentials beforehand, click the Ma nage accounts link or click the Ad d button to
add credentials. For more information on adding credentials, see the Credentials Manager section.

4. To specify other credentials for individual VMs, click Credentials. Then select the necessary VM and set
user credentials for it.

5. To check whether Veeam Backup & Replication can connect to VMs using the specified guest OS
credentials and can deploy the non-persistent runtime components or connect to persistent agent
components on the guest OSes, click Test Now.

After you have enabled guest OS processing, configure the following guest processing options:

• Application-aware processing

• Microsoft SQL Server transaction log settings

• Oracle archived log settings

• VM guest OS file exclusion

1458 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Pre-freeze and post-thaw scripts

Application-Aware Processing
Application-aware processing helps create transactionally consistent replicas. The transactionally consistent
replicas guarantee proper recovery of applications without data loss. For more information on application-aware
processing, see Application-Aware Processing.

To configure general application-aware processing settings and specify whether Veeam Backup & Replication
processes transaction logs or creates copy-only replicas:

1. At the Guest Processing step of the wizard, check that you have selected the E nable application-aware
p rocessing check box and configured guest OS credentials.

2. At the Guest Processing step of the wizard, click Ap p lications.

3. In the Ap p lication-Aware Processing Options window, select workloads for which you want to configure
application-aware processing, and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

4. On the General tab, in the Ap p lications section, specify the behavior scenario for application-aware
processing:

o Select Require successful processing if you want Veeam Backup & Replication to stop the replication
process if any error occurs during application-aware processing.

o Select Try application processing, but ignore failures if you want to continue the replication process
even if an error occurs during application-aware processing. This option guarantees that replication
will continue working. However, the resulting replica will be crash consistent, not transactionally
consistent.

1459 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Disable application processing if you want to disable application-aware processing for the
workload.

5. [For Microsoft Exchange and Microsoft SQL Server] In the VSS Settings section, specify if
Veeam Backup & Replication must process transaction logs or create copy-only replicas:

a. Select P rocess transaction logs with this job if you want Veeam Backup & Replication to process
transaction logs.

[For Microsoft Exchange VMs] With this option selected, the non-persistent runtime components or
persistent components running on the VM guest OS will wait for replication to complete successfully
and then trigger truncation of transaction logs. If the replication job fails, the logs will remain
untouched on the VM guest OS until the next start of the non-persistent runtime components or
persistent components.

[For Microsoft SQL Server] You will need to configure how to process transaction logs.

TIP

To configure log processing for Oracle and PostgreSQL databases, switch to the Oracle and
PostrgeSQL tabs.

b. Select P erform copy only if you use another tool to perform guest level processing, and this tool
maintains consistency of the database state. Veeam Backup & Replication will create a copy-only
replica for the selected VMs. The copy only replica preserves the chain of full and differential files and
transaction logs on the VM. For more information, see Microsoft Docs.

6. [For Microsoft Windows VMs] In the P ersistent guest agent section, select the Use persistent guest agent
check box to use for application-aware processing persistent guest agents on each protected VM.

By default, Veeam Backup & Replication uses non-persistent runtime components.


Veeam Backup & Replication deploys runtime components on each protected VM when the replication job
starts, and removes the runtime components as soon as the replication job finishes.

For more information on guest agent and non-persistent components, see Non-Persistent Runtime
Components and Persistent Agent Components.

1460 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
[For Linux VMs] To use persistent guest agents, you must install Management Agent on protected VMs.
For more information, see Persistent Agent Components.

Microsoft SQL Server Transaction Log Settings


The SQL tab is available for VMs that run Microsoft SQL Server and if you have selected P rocess transaction logs
with this job when configuring application-aware processing.

To create transactionally consistent backups of an Microsoft SQL Servers, you must check that application-
aware processing is enabled and then specify settings of transacrion log processing.

Enabling Application-Aware Processing


Before configuring transaction log processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the Microsoft SQL Sever and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

4. In the P rocessing Settings window, on the General tab, check that Require successful processing or Try
a p plication processing, but ignore failures option is selected in the Ap p lications area.

1461 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Specifying Transaction Log Settings
In the P rocessing Settings window, switch to the SQL tab and specify how transaction logs must be processed:

• If you want Veeam Backup & Replication to trigger truncation of transaction logs only after the job
completes successfully, select Truncate logs.

In this case, the non-persistent runtime components or persistent components will wait for replication to
complete and then trigger truncation of transaction logs. If the replication job fails, the logs will remain
untouched on the VM guest OS until the next start of the non-persistent runtime components or
persistent components.

o If you do not want Veeam Backup & Replication to truncate logs at all, select Do not truncate logs.

This option is recommended if you are using another backup tool to perform VM guest-level backup or
replication, and this tool maintains consistency of the database state. In such scenario,
Veeam Backup & Replication will not trigger transaction log truncation. After you fail over to the
necessary restore point of the VM replica, you will be able to apply transaction logs to get the database
system to the necessary point in time between replication job sessions.

Oracle Archived Log Settings


The Ora cle tab applies to VMs that run Oracle.

To create transactionally consistent backups of an Oracle server, you must check that application-aware
processing is enabled and then specify settings of archive log processing.

1462 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Enabling Application-Aware Processing
Before configuring archive log processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the Oracle server and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

4. In the P rocessing Settings window, on the General tab, check that Require successful processing or Try
a p plication processing, but ignore failures option is selected in the Ap p lications area.

Specifying Archive Log Settings


To configure how Veeam Backup & Replication must process archive logs of an Oracle server:

1. In the P rocessing Settings window, switch to the Ora cle tab.

2. From the Sp ecify Oracle account with SYSDBA privileges drop-down list, select a user account that
Veeam Backup & Replication will use to connect to the Oracle databases. The account that you plan to use
must have privileges described in section Permissions.

You can select Use guest credentials from the list of user accounts. In this case,
Veeam Backup & Replication will use the account specified at the Guest Processing step of the wizard to
access the VM guest OS and connect to the Oracle databases.

3. In the Archived logs section, specify how to process archived logs:

o If you want to preserve archived logs on the VM guest OS, select Do not delete archived logs. When
the replication job completes, the non-persistent runtime components or persistent components will
not truncate transaction logs.

It is recommended that you select this option for databases where the ARCHIVELOG mode is turned
off. If the ARCHIVELOG mode is turned on, archived logs may grow large and cons ume all disk space.

o If you want to delete archived logs older than <N> hours, select Delete logs older than <N> hours and
specify the number of hours.

1463 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o If you want to delete archived logs larger than <N> GB, select Delete logs over <N> GB and specify
the size. The specified size refers to the log size of each database, not all databases on the selected
Oracle server.

The non-persistent runtime components or persistent components running on the VM guest OS will wait
for the replication job to complete successfully and then trigger transaction logs truncation using Oracle
Call Interface (OCI). If the job does not manage to replicate the Oracle VM, the logs will remain untouched
on the VM guest OS until the next start of the non-persistent runtime components or persistent
components.

Postgre SQL Settings


The P ostgreSQL tab applies to VMs that run PostgreSQL.

To create transactionally consistent backups of a PostgreSQL VM, you must check that application-aware
processing is enabled and then specify settings of WAL files processing.

Enabling Application-Aware Processing


Before configuring WAL files processing, check that application-aware processing is enabled:

1. At the Guest Processing step of the wizard, select the E nable application-aware processing check box.

2. Click Ap p lications.

3. In the displayed list, select the PostgreSQL VM and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

1464 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the P rocessing Settings window, on the General tab, check that Require successful processing or Try
a p plication processing, but ignore failures option is selected in the Ap p lications area.

Specifying WAL Files Settings


To define how Veeam Backup & Replication will process WAL files on this VM, do the following:

1. In the P rocessing Settings window, click the P ostgreSQL tab.

2. From the Sp ecify PostgreSQL account with superuser privileges drop-down list, select a user account that
Veeam Backup & Replication will use to connect to the PostgreSQL instance. The account must have
privileges described in section Permissions. You can select Use guest credentials from the list of user
accounts. In this case, Veeam Backup & Replication will use the account specified at the Guest Processing
step of the wizard to access the VM guest OS and connect to the PostgreSQL instance.

If you have not set up credentials beforehand, click the Ma nage accounts link or click the Ad d button to
add credentials. Note that if you select the Sy stem user without password file (peer) option in the The
sp ecified user is area, you can add a user account without specifying a password.

3. In the The specified user is section, specify how the user selected in the Sp ecify PostgreSQL account with
sup eruser privileges drop-down list will authenticate against the PostgreSQL instance:

o Select Da tabase user with password if the account is a PostgreSQL account, and you entered the
password for this account in the Credentials Manager.

o Select Da tabase user with password file (.pgpass) if the password for the account is defined in the
.pgpass configuration file on the PostgreSQL server. For more information about the password file,
see PostgreSQL documentation.

1465 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Sy stem user without password file (peer) if you want Veeam Backup & Replication to use the
peer authentication method. In this case, Veeam Backup & Replication will apply the OS account as
the PostgreSQL account.

VM Guest OS File Exclusion


These settings apply only to Microsoft Windows workloads.

To exclude guest OS files and folders from being replicated:

1. At the Guest Processing step of the wizard, check that you have selected the E nable application-aware
p rocessing check box and configured guest OS credentials.

2. In the Ap p lication-Aware Processing Options list, select workloads for which you want to exclude files and
folders and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

3. In the P rocessing Settings window, switch to the E x clusions tab and specify whether you want to exclude
or include files and folders:

o To remove individual files and folders from replicas, select E x clude the following files and folders and
click Ad d .

o To include only the specified files and folders in replicas, select Include only the following files and
folders and click Ad d .

4. In the Sp ecify Folder window, specify which files and folders you want to include or exclude. For the
methods that you can use to specify the list of exclusions or inclusions, see VM Guest OS Files.

1466 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

When you select files to be included or excluded, consider requirements and limitations that are listed in
section Requirements and Limitations for VM Guest OS File Exclusion.

Pre-Freeze and Post-Thaw Scripts


If you plan to replicate VMs running applications that do not support VSS, you can instruct
Veeam Backup & Replication to run custom pre-freeze and post-thaw scripts for these VMs. The pre-freeze
script quiesces the VM file system and application data to bring the VM to a consistent state before
Veeam Backup & Replication triggers a VM snapshot. After the VM snapshot is created, the post-thaw script
brings the VM and applications to their initial state.

To specify pre-freeze and post-thaw scripts:

1. At the Guest Processing step of the wizard, check that you have selected the E nable application-aware
p rocessing check box and configured guest OS credentials.

1. At the Guest Processing step of the wizard, click Ap p lications.

2. In the Ap p lication-Aware Processing Options list, select workloads for which you want to configure
scripts, and click E d it.

To define custom settings for a VM added as a part of a VM container, you must include the VM in the list
as a standalone object. To do this, click Ad d and choose the necessary VM. Then select the VM in the list
and define the necessary settings.

2. Click the Scripts tab.

1467 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Script processing mode section, select a scenario for script execution:

o Select Require successful script execution if you want Veeam Backup & Replication to stop the
replication process if scripts fail.

o Select Ig nore script execution failures if you want to continue the replication process even if script
errors occur.

o Select Disable script execution if you do not want to run scripts for the VM.

5. In the W indows scripts section, specify paths to scripts for Microsoft Windows VMs. For the list of
supported script formats, see Pre-Freeze and Post-Thaw Scripts.

6. In the Linux scripts section, specify paths to scripts for Linux VMs. For the list of supported script formats,
see Pre-Freeze and Post-Thaw Scripts.

If you plan to replicate a VM container with Microsoft Windows and Linux VMs, you can select to execute
both Microsoft Windows and Linux scripts. When replication starts, Veeam Backup & Replication will
automatically determine which OS type is installed on the VM and use the correct scripts for this VM.

TIP

Beside pre-freeze and post-thaw scripts for VM quiescence, you can instruct Veeam Backup & Replication
to run custom scripts before the job starts and after the job completes. For more information, see
Advanced Settings.

1468 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 15. Define Job Schedule
At the Schedule step of the wizard, select to run the replication job manually or schedule the job to run on a
regular basis:

1. To run the replication job automatically, select the Run the job automatically check box. If you do not
select this check box, you will have to start the job manually.

2. Define scheduling settings for the job:

o To run the job at specific time daily, on weekdays or with specific periodicity, select Da ily at this time.
In the fields on the right of the check box, specify the time and required days.

o To run the job once a month on specific days, select Monthly at this time. In the fields on the right of
the check box, specify the necessary days.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for
example, related to daylight saving time transition).

o To run the job repeatedly throughout a day with a set time interval, do the following:

i. Select P eriodically every. In the field on the right, select the necessary time unit: Hours or
Minutes.

ii. If you want to specify the permitted time window for the job, click Schedule. In the Time Periods
window, specify the schedule.

If you want to shift the schedule, specify the offset in the Sta rt time within a n hour field. For
example, you schedule the prohibited hours from 08:00 AM to 10:00 AM, and set the offset
value to 25. The schedule will be shifted forward, and the prohibited hours will be from 8:00
AM and to 10:25 AM.

A repeatedly run job is started by the following rules:

▪ Veeam Backup & Replication always starts counting defined intervals from 12:00 AM. For
example, if you configure to run a job with a 4-hour interval, the job will start at 12:00 AM, 4:00
AM, 8:00 AM, 12:00 PM, 4:00 PM and so on.

▪ If you define permitted hours for the job, after the denied interval is over,
Veeam Backup & Replication will immediately start the job and then run the job by the defined
schedule.

For example, you have configured a job to run with a 2-hour interval and defined permitted hours
from 9:00 AM to 5:00 PM. According to the rules above, the job will first run at 9:00 AM, when the
denied period is over. After that, the job will run at 10:00 AM, 12:00 PM, 2:00 PM and 4:00 PM.

o To run the job continuously, select the P eriodically every option and choose Continuously from the
list on the right.

o To chain jobs, use the After this job field. For the first job in the chain, you must specify an automatic
time schedule, otherwise the chained jobs will not be started. For the chained jobs, select the After
this job option and choose the preceding job from the list. For more information on job chaining and
recommendations for it, see Chained Jobs.

1469 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Automatic retry section, select the Retry failed VMs processing if Veeam Backup & Replication must
attempt to run the job again for VMs whose processing failed for some reason. Enter the number of
attempts to run the job and define time spans between them.

If you select continuous schedule for the job, Veeam Backup & Replication will retry the job for the
defined number of times without any time intervals between the job sessions.

4. In the Ba ckup window section, specify a time interval within which the job must be completed. The backup
window prevents the job from overlapping with production hours and ensures the job does not provide
unwanted overhead on your production environment.

To set up a backup window for the job:

a. Select the Terminate job if it exceeds allowed backup window check box and click W ind ow.

b. In the Time P eriods window, define the allowed hours and prohibited hours for VM replication. If the
job exceeds the allowed window, the job will be automatically terminated.

1470 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 16. Finish Working with Wizard
At the Summary step of the wizard, review details of the replication job. If you want to start the job right after
you close the wizard, select the Run the job when I click Finish check box, otherwise leave the check box
unselected. Then click Finish to close the wizard.

1471 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Replica Seeds
To use replica seeding in a replication job, you must have backups of replicated VMs in a backup repository in
the disaster recovery (DR) site. These backups are known as replica seeds. For more information on seeding and
when to use it, see Replica Seeding and Mapping.

If you do not have replica seeds in the DR site, do the following:

1. Create a backup of VMs that you plan to replicate as described in section Creating Backup Jobs. As the
target repository for this job, select a backup repository in the production site. Then run the job.

If you already have backups containing the necessary VMs, there is no need to configure and run a new
backup job. For seeding, you can use any existing backups created by Veeam Backup & Replication. The
backup must include VBK and VBM files. If you have a full backup and a chain of forward increments, you
can use VIB files together with the VBK and VBM files. In this case, Veeam Backup & Replication will
restore VMs from the seed to the latest available restore point.

2. Copy the backup from the backup repository in the production site to a backup repository in the DR site.

You can move the backup using a file copy job or any other appropriate method, for example, copy the
backup to a removable storage device, ship the device to the DR site and copy backups to the backup
repository in the DR site.

If you do not have a backup repository in the DR site, you need to create the repository as described in
section Backup Repository.

IMP ORTANT

You cannot copy backups to a scale-out backup repository in the DR site.

3. After the backup is copied to the backup repository in the DR site, perform rescan of this backup
repository as described in section Rescanning Backup Repositories. Otherwise,
Veeam Backup & Replication will not be able to detect the copied backup.

1472 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Replicas
To view all created replicas, open the Home view and navigate to the Rep licas node. The
working area displays the full list of the created replicas. Here, you can view replica
properties and delete replicas from the configuration database or disk.

1473 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Replica Properties
You can view summary information about created replicas. The summary information provides the following
data:

• Available restore points

• Date of restore points creation

• Data size and replica status

To view replica properties:

1. Open the Home view.

2. In the inventory pane, select Rep licas.

3. In the working area, right-click the necessary replica and select P roperties. Alternatively, select P roperties
on the ribbon.

1474 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Rescanning Replicas
You may need to perform replica rescan in the following cases:

• After you delete restore points for one or more replicas.

• After you restore the configuration database, and the session results show that some hosts us ed to
register replicas were unavailable during the session.

To check whether any errors occurred during the database restore session, open the Home view and select
Sy stem in the inventory pane. In the working area, right-click the Configuration Database Resynchronize
job and select Sta tistics.

During the rescan process, Veeam Backup & Replication gathers information on replicas that are currently
available in backup repositories and updates the list of replicas in the configuration database.

To rescan replicas, do the following:

1. Open the Home view.

2. In the inventory pane, right-click the Rep licas node and select Rescan Replicas.

1475 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Replicas from Configuration
When you remove replicas from the configuration, Veeam Backup & Replication removes records about the
replicas from the configuration database, stops showing the replicas in Veeam Backup & Replication console and
also stops synchronizing their state with the state of the source VMs. However, the actual replicas remain on
hosts.

To remove records about replicas from the Veeam Backup & Replication console and configuration database:

1. Open the Home view.

2. In the inventory pane, click the Rep licas node.

3. In the working area, select replicas in the Ready state and click Remove from > Configuration on the
ribbon. Alternatively, right-click one of the selected replicas and select Remove from configuration.

NOTE

Consider the following:

• The Remove from configuration operation can be performed only for VM replicas in the Ready state.
If the VM replica is in the Failover or Failback state, this option is disabled.

• When you perform the Remove from configuration operation for a VM that is replicated as a
standalone object, Veeam Backup & Replication removes this VM from the initial replication job.
When you perform the Remove from configuration operation for a VM that is replicated as part of a
VM container (Hyper-V host, cluster, SCVMM, SCVMM tag, SCVMM host group, VM g roup, or
volume), Veeam Backup & Replication adds this VM to the list of exclusions in the initial replication
job. For more information, see Exclude Objects from Replication Job.

1476 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting Replicas from Disk
When you delete replicas from disks, Veeam Backup & Replication removes the replicas not only from the
Veeam Backup & Replication console and configuration database, but also from host storage.

NOTE

Consider the following:

• You can delete records only about replicas that are in the Ready state.
• Do not delete replica files from the destination storage manually, use the Delete from disk option
instead. If you delete replica files manually, subsequent replication sessions will fail.
• Unlike the Remove from configuration operation, the Delete from disk operation does not remove
the processed workload from the initial replication job.

To delete replica files from disks:

1. Open the Home view.

2. In the inventory pane, click the Rep licas node.

3. In the working area, select the necessary replica and click Remove from > Disk on the ribbon. As an
alternative, right-click the replica and select Delete from disk.

1477 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Replication Jobs
To view all created replication jobs, open the Home view and navigate to the Job s > Replication node. The
working area displays the full list of the created replication jobs. Here, you can manage the jobs: retry, edit,
clone, disable and delete jobs.

In This Section
• Retrying Replication Jobs

• Editing Replication Jobs

• Cloning Replication Jobs

• Disabling and Deleting Replication Jobs

1478 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Retrying Replication Jobs
The retry option is necessary when a replication job fails and you want to retry this operation again. When you
perform a retry, Veeam Backup & Replication restarts the operation only for the failed workloads added to the
job and does not process VMs that have been processed successfully. As a result, the retry operation takes less
time compared to running the job for all workloads.

To retry a failed replication job:

1. Open the Home view.

2. In the inventory pane, navigate to the Job s > Replication node.

3. In the working area, select the necessary replication job and select Retry on the ribbon. Alternatively, you
can right-click the necessary replication job and select Retry.

1479 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Replication Jobs
You can edit configured jobs at any moment. For example, you may want to change schedul ing settings for the
job or add some VMs to the job.

To edit a replication job:

1. Open the Home view.

2. In the inventory pane, navigate to the Job s > Replication node.

3. In the working area, select the necessary replication job and select E d it on the ribbon. Alternatively, you
can right-click the necessary replication job and select E d it.

4. Follow the instructions provided in Creating Replication Jobs.

1480 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Cloning Replication Jobs
You can create new jobs by means of job cloning. Job cloning allows you to create an exact copy of any job with
the same job settings and edit settings of cloned jobs as required.

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 clone a job:

1. Open the Home view.

2. In the inventory pane, select the Job s > Replication node.

3. In the working area, select the job and click Clone on the ribbon or right-click the job and select Clone.

4. After a job is cloned, you can edit all its settings, including the job name.

1481 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling and Deleting Replication Jobs
You can temporary disable scheduled jobs. The disabled job is paused for some period of time and is not run by
the specified schedule. You can enable a disabled job at any time. You can also permanently delete a job from
Veeam Backup & Replication and from the configuration database.

Disabling Jobs
To disable a replication job:

1. Open the Home view.

2. In the inventory pane, navigate to the Job s > Replication node.

3. In the working area, select the necessary policy and select Dis able on the ribbon. Alternatively, you can
right-click the necessary policy and select Disable.

To enable a disabled replication job, select it and click Disable on the ribbon once again.

Deleting Jobs
To delete a replication job:

1. Open the Home view.

2. In the inventory pane, navigate to the Job s > Replication node.

3. In the working area, select the necessary replication job and select Delete on the ribbon. Alternatively,
you can right-click the necessary replication job and select Delete.

NOTE

Veeam Backup & Replication allows you to delete only stopped replication jobs.

1482 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
After you delete the job, the replicas created by this job are displayed under the Rep licas node. If you want to
remove replicas from the Veeam Backup & Replication console and configuration database but keep them on
hosts, follow the instructions provided in Removing Replicas from Configuration. If you want to remove replicas
not only from Veeam Backup & Replication, but also from host storage, follow the steps in Deleting Replicas
from Disk.

1483 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failover and Failback for Replication
Failover and failback operations help you ensure that your business will function even if a disaster strikes your
production site. Failover is a process of switching from the VM on the source host to its VM replica on a host in
the disaster recovery site. Failback is a process of returning from the VM replica to the source VM.

Veeam Backup & Replication provides the following failover and failback operations:

• P erform failover

When you perform failover, you shift all processes from the source VM in the production site to the VM
replica in the disaster recovery site. During failover, changes made on the VM replica are not reflected on
the source VM.

Failover is an intermediate step that needs to be finalized: you can undo failover, perform permanent
failover or perform failback.

For more information on how failover is performed, see Failover.

• P erform planned failover

When you perform planned failover, you shift all processes from the source VM to its replica. During
failover, changes made on the VM replica are not reflected on the source VM.

Planned failover is helpful when you know that the source VM is about to go of fline, for example, you plan
to perform datacenter maintenance, and you want to proactively switch the workload to the replica. The
procedure is designed to transfer the current workload, that is why it does not suggest to select a restore
point.

For more information on how planned failover is performed, see Planned Failover.

• Create failover plan


When you create a failover plan, you define the order in which Veeam Backup & Replication must perform
failover for VMs, and an interval of time for which Veeam Backup & Replication must wait before starting
the failover operation for the next VM in the list.

For more information on failover plans, see Failover Plan.

• P erform permanent failover

When you perform permanent failover, you permanently switch from the source VM to a VM replica and
use this replica as the source VM. You can use this scenario if the source VM and VM replica are located in
the same site and are nearly equal in terms of resources. Otherwise, perform failback.

For more information on how permanent failover is performed, see Permanent Failover.

• Und o failover
When you undo failover, you shift all processes back to the source VM and discard all changes made to the
VM replica while it was running.

You can use the undo failover scenario if you have failed over to the VM replica for testing and
troubleshooting purposes, and you do not need to synchronize the source VM state with the current state
of the replica.

For more information on how failover undo is performed, see Failover Undo.

• P erform failback

When you perform failback, you shift all processes back to the source VM and send to the source VM all
changes that took place while the VM replica was running. During failover, changes made on the source
VM are not sent to the VM replica.

1484 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If the source host is not available, you can recover a VM with the same configuration as the source VM and
switch to it. For more information on how failback is performed, see Failback.

When you perform failback, changes are only sent to the source/recovered VM but not published. You
must test whether the source/recovered VM works with these changes. Depending on the test results, you
can do the following:

o Commit failback. When you commit failback, you confirm that changes on the source/recovered VM
work as expected and you want to get back to the source VM.

For more information on how failback commit is performed, see Failback Commit.

o Und o failback. When you undo failback, you confirm that changes on the source/recovered VM are not
working as expected and you want to discard them, and then to get back to the VM replica.

For more information on how failback undo is performed, see Failback Undo.

Veeam Backup & Replication supports failover and failback operations for one VM and for several VMs. In case
one or several hosts fail, you can use batch processing to restore operations with minimum downtime.

1485 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The following scheme can help you decide at which moment which operations are preferable.

1486 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failover Plans
A failover plan helps you perform failover for dependent VMs one by one, as a group. To do this automatically,
you can prepare a failover plan.

In the failover plan, you define the order in which VMs must be processed and an interval of time for which
Veeam Backup & Replication must wait before starting the failover operation for the next VM in the list. The
failover plan helps ensure that some VMs, such as a DNS server, are already running at the time the dependent
VMs start.

IMP ORTANT

The failover plan must be created in advance.

In case the primary VM group goes offline, you can start the failover plan manually. When you start the plan,
you can choose to fail over to the latest state or select the point in time to which VM replicas must be started.
Veeam Backup & Replication will look for the closest restore points to this point in time and use them to start
VM replicas. The source VMs will not be powered off.

The failover process is performed in the following way:

1. For each VM, Veeam Backup & Replication detects its replica. The VMs whose replicas are already in the
Failover or Failback state are skipped from processing.

2. The replica VMs are started in the order they appear in the failover plan within the set time intervals.

Limitations for Failover Plans


The maximum number of VMs that can be started simultaneously when you run a failover plan is 10. If you have
added more VMs to the failover plan and scheduled them to start simultaneously, Veeam Backup & Replication
will wait for the first VMs in the list to fail over and then start the failover operation for subsequent VMs. This
limitation helps reduce the workload on the production infrastructure and backup server.

For example, if you have added 14 VMs to the failover plan and scheduled them to start at the same time,
Veeam Backup & Replication will start the failover operation for the first 10 VMs in the list. After the 1 st VM is
processed, Veeam Backup & Replication will start the failover operation for the 11th VM in the list, then for the
12th VM and so on.

1487 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Finalizing Failover Plans
Failover is a temporary intermediate step that needs to be finalized. You can finalize group failover in the same
ways as regular failover: undo failover, perform permanent failover or failback.

When you perform failback or permanent failover, you need to process each VM individually. For more
information, see Performing Failback and Performing Permanent Failover. When you undo failover, you can
process the whole group. For more information, see Undoing Failover by Failover Plans.

Creating Failover Plans


To create a failover plan, use the New Failover Plan wizard.

Before You Begin


Before you create a failover plan, check the following prerequisites:

• [If you plan to select VMs from replication jobs] VMs that you plan to include in the failover plan must be
successfully replicated at least once.

• [If you plan to select VMs from replication jobs] VM replicas must be in the Ready state.

• If you plan to use pre-failover and post-failover scripts for the failover plan, you must create scripts
before you configure the failover plan.

1488 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Failover Plan Wizard
To launch the New Failover Plan wizard, do one of the following:

• On the Home tab, click Fa ilover Plan and select Microsoft Hyper-V.

• Open the Home view. In the working area, select VMs that you want to add to a failover plan. On the
ribbon, click Ad d to Failover Plan > New failover plan if you want to create a new failover plan, or Ad d to
Fa ilover Plan > <Plan Name> if you want to add VMs to an existing failover plan.

• Open the Home view. In the working area, select VMs that you want to add to a failover plan and right-
click one of them. Select Ad d to failover plan > New failover plan if you want to create a new failover plan,
or Ad d to failover plan > <Plan Name> if you want to add VMs to an existing failover plan.

1489 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Failover Plan Name and Description
At the General step of the wizard, specify a name and description for the failover plan.

If you want to execute custom scripts before or after the failover plan, select the P re-failover script and P ost-
fa ilover script check boxes and click Browse to choose executable files. For example, you may want stop some
applications on production VMs before the failover plan starts or send an email to backup administrators after
the failover plan finishes.

The scripts will be executed on the backup server. Veeam Backup & Replication supports the script files in the
following formats: BAT, CMD, EXE and PS1.

1490 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select VMs
At the Virtual Machines step of the wizard, select VMs that you want to add to the failover plan. You can add
separate VMs and whole VM containers (Hyper-V hosts, clusters, SCVMM, SCVMM tags, SCVMM host groups,
VM groups, or volumes).

To add VMs and VM containers:

1. Click Ad d VM.

2. Select where to browse for VMs and VM containers:

o From infrastructure — browse the virtual environment and select VMs or VM containers. If you choose
a VM container, Veeam Backup & Replication will expand it to a plain VM list.

o From replicas — browse existing replication jobs and select all VMs or specific VMs from replication
jobs.

To quickly find the necessary VMs or VM containers, you can use the search fields.

NOTE

A source from which you add a VM to a failover plan does not affect whether you fail over to the latest or
specific restore point. It is the command that you select when starting a failover plan that defines the
restore point. For more information, see Running Failover Plans.

1491 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Define VM Failover Order
At the Virtual Machines step of the wizard, click Up and Down to change the processing order. VMs at the top of
the list have a higher priority and will be started first. If some VMs provide environment for other dependent
VMs, make sure that they are started first.

1492 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Set Time Delay
After you have set the order for VMs in the failover plan, you need to set a time delay for VMs. The delay time
defines for how long Veeam Backup & Replication must wait before starting the failover operation for the next
VM in the list. You can use time delays to make sure that some VMs are already running at the moment
dependent VMs start.

For example, you have added 2 VMs to the failover plan and set a time delay to 60 seconds for the first VM in
the list. Veeam Backup & Replication will perform failover in the following manner: Veeam Backup & Replication
will start the failover operation for the first VM in the list, then wait for 60 seconds and start the failover
operation for the second VM in the list.

NOTE

Time delays can be specified for all VMs in the list except the last one. If you do not specify time delays,
VMs will be started simultaneously.

To set the time delay for a VM:

1. Select it and click Set Delay on the right or double-click the VM in the list.

2. Enter the time interval that you consider sufficient for this VM to boot.

1493 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review details for the configured failover plan and click Finish to create the
plan.

Running Failover Plans


You have the following options to run a failover plan:

• You can fail over to latest restore points of VM replicas.


In this case, Veeam Backup & Replication searches for the latest restore point of VM replicas across all
replication jobs configured on the backup server. For example, you have 2 jobs that replicate the same VM:
Job 1 has created the most recent point at 2:00 AM and Job 2 has created the most recent restore point at
3:00 AM. When you run the failover plan using the Sta rt command, Veeam Backup & Replication will pick
the restore point created at 3:00 AM with Job 2.

• You can fail over to specific restore points of VM replicas.

Failing Over to Latest Restore Points


To fail over to the latest restore points of VM replicas:

1. Open the Home view.

2. Expand the Rep licas node.

3. Select Fa ilover Plans.

4. In the working area, right-click the failover plan and select Sta rt.

1494 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Failing Over to Specific Restore Points
To fail over to specific restore points of VM replicas:

1. Open the Home view.

2. Expand the Rep licas node.

3. Select Fa ilover Plans.

4. In the working area, right-click the failover plan and select Sta rt to.

5. In the displayed window, select the backup date and time. Veeam Backup & Replication will find the
closest restore point prior to the entered value for each VM and will fail over to it.

Undoing Failover by Failover Plans


You can undo failover for all VMs added to the failover plan at once. When you undo failover, you switch the
workload back to source VMs and discard all changes that were made to VM replicas during failover. If som e of
the VMs were already failed back, for example manually by the user, they are skipped from processing.

Veeam Backup & Replication starts the failover undo operation for a group of 5 VMs at the same time. The time
interval between the operation starts is 10 seconds. For example, if you have added 10 VMs to the failover plan,
Veeam Backup & Replication will undo failover for the first 5 VMs in the list, then will wait for 10 seconds and
undo failover for the remaining 5 VMs in the list. Time intervals between the operation starts help
Veeam Backup & Replication reduce the workload on the production environment and the backup server.

To undo failover by a failover plan:

1. Open the Home view.

2. Expand the Rep licas node.

3. Select Fa ilover Plans.

4. In the working area, right-click the failover plan and select Und o.

1495 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. In the displayed dialog box, click Y es to confirm the operation.

1496 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failover
Failover is a process when Veeam Backup & Replication switches processes from the source VM in the
production site to its VM replica in the disaster recovery site. During failover, Veeam Backup & Replication
recovers the VM replica to the required restore point and shifts all I/O processes from the source VM to its
replica. As a result, you have a fully functional VM within a couple of seconds, and your users can access services
and applications with minimum disruption.

You can fail over to replicas not only when a disaster strikes the production site, but also to test replicas for
recoverability. You can perform failover while the source VM is running. After all the necessary tests, you can
undo failover and get back to the normal mode of operation. If the source VMs and VM replicas are located in
the same network, consider temporary disconnecting the source VMs from the network to avoid IP address or
machine name conflicts.

IMP ORTANT

Use Veeam Backup & Replication to perform failover operations. Avoid powering on a replica manually —
this may disrupt further replication operations or cause loss of important data.

Veeam Backup & Replication performs the failover process for snapshot VM replicas and legacy VM replicas in
different ways.

Snapshot VM Replicas
The failover operation for snapshot VM replicas is performed in the following way:

1. Veeam Backup & Replication rolls back the VM replica to the required restore point. To do this,
Veeam Backup & Replication applies the necessary snapshot from the replica chain to the VM replica.

2. Veeam Backup & Replication powers on the VM replica. The state of the VM replica is changed from Ready
to Failover.

If you perform failover for testing or DR simulation purposes, and the source VM still exists and is running,
the source VM remains powered on.

NOTE

Veeam Backup & Replication stops all replication activities for the source VM until its replica is
returned to the Ready state.

3. All changes made to the VM replica while it is running in the Failover state are written to the differencing
disk (AVHD/AVHDX) of the snapshot, or restore point, to which you have selected to roll back.

1497 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Legacy VM Replicas
The failover operation for legacy VM replicas is performed in the following way:

1. To protect the VM replica from altering, Veeam Backup & Replication takes a protective snapshot for the
VM replica.

2. Veeam Backup & Replication rolls back the VM replica to the required restore point.

3. Veeam Backup & Replication powers on the VM replica. The state of the VM replica is changed from Ready
to Failover.

NOTE

Veeam Backup & Replication stops all replication activities for the source VM until its replica is
returned to the Ready state.

4. All changes made to the VM replica while it is running in the Failover state are written to the differencing
disk of the created protective snapshot.

Finalizing Failover
Failover is an intermediate step that needs to be finalized. You can use one of the following operations:

• Undo failover.

• Perform permanent failover.

• Perform failback.

Performing Failover
For more information on failover, see Failover and Failover and Failback for Replication.

To perform failover, use the Hy p er-V Failover wizard.

Before You Begin


Before you fail over to a VM replica, check the following prerequisites:

• The failover operation can be performed for VMs that have been successfully replicated at least once.

• VM replicas must be in the Ready state.

1498 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Failover Wizard
To launch the Fa ilover wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from replica > Entire replica > Failover to a
rep lica.

• Open the Home view. In the inventory pane select Rep licas. In the working area, select the necessary
replica and click Fa ilover Now on the ribbon.

• Open the Home view. In the inventory pane select Rep licas. In the working area, right-click the necessary
replica and select Fa ilover Now.

1499 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VMs
At the Virtual Machines step of the wizard, you can modify a list of VMs from which you fail over. To add VMs or
VM containers, click Ad d > From infrastructure if you want to add VMs from the virtual infrastructure, or Ad d >
From replicas if you want to add VMs from existing replicas. Then select the necessary VMs or VM containers. If
you select VM containers, Veeam Backup & Replication will expand them to a plain VM list.

NOTE

Make sure that VMs you select from the virtual environment have been successfully replicated at least
once.

1500 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
By default, Veeam Backup & Replication uses the latest valid restore point of the VM replica. However, you can
fail over to an earlier state of the VM. If you have chosen to perform failover for several VMs, you can select the
necessary restore point for every VM in the list.

To select a restore point for a VM:

1. In the Virtual machines to failover list, select the necessary VM and click P oint.

2. In the Restore Points window, select the necessary restore point.

1501 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Failover Reason
At the Rea son step of the wizard, enter a reason for failing over to the replicas. The information you provide will
be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1502 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Summary step of the wizard, review details of the failover task and click Finish to exit the wizard. When
the failover process is complete, the VM replicas will be started on the target host.

What You Do Next


Failover is an intermediate step that needs to be finalized. You can finalize failover in the following ways:

• Perform permanent failover.

• Undo failover.

• Perform failback.

1503 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Permanent Failover
Permanent failover is one of the ways to finalize failover. When you perform permanent failover, you
permanently switch from the source VM to its replica. As a result of permanent failover, the VM replica stops
acting as a replica and starts acting as the production VM.

NOTE

We recommend you to perform permanent failover only if the source VM and its replica are located in the
same site and are nearly equal in terms of resources. In this case, users will not experience any latency in
ongoing operations. Otherwise, perform failback.

The permanent failover operation is performed in the following way:

1. Veeam Backup & Replication removes snapshots (restore points) of the VM replica from the snapshot
chain and deletes associated files from the volume. Changes that were written to the snapshot
differencing disk are committed to the VM replica disk files to bring the VM replica to the most recent
state.

2. Veeam Backup & Replication removes the VM replica from the list of replicas in the
Veeam Backup & Replication console.

3. To protect the VM replica from corruption after permanent failover is complete,


Veeam Backup & Replication reconfigures the current replication job by adding the source VM to the list of
exclusions. Note that other jobs are not modified automatically. When the replication job starts, the
source VM is skipped from processing. As a result, no data is written to the working VM replica.

Performing Permanent Failover


For more information on permanent failover, see Permanent Failover and Failover and Failback for Replication.

To perform permanent failover, do one of the following:

• Open the Home view. In the inventory pane navigate to the Rep licas > Active node. In the working area,
select the necessary replica and click P ermanent Failover on the ribbon.

1504 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane navigate to the Rep licas > Active node. In the working area,
right-click the necessary replica and select P ermanent failover.

1505 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Planned Failover
Planned failover is a process when you manually launch switching from a primary VM to its replica with
minimum interrupting in operation. Planned failover is helpful when you know that your primary VMs are about
to go offline and you need to proactively switch the workload from source VMs to their replicas. You can use the
planned failover, for example, if you plan to perform datacenter migration, maintenance or software upgrade of
the primary VMs. You can also perform planned failover if you have noticed some signs of the approaching
disaster.

As the procedure is designed to transfer the current workload to the replica, it does not suggest selecting a
restore point to switch.

When you start the planned failover, Veeam Backup & Replication performs the following operations:

1. The failover process triggers the replication job to perform an incremental replication run and copy the
un-replicated changes to the replica.

2. The VM is powered off.

3. The failover process triggers the replication job to perform another incremental replication run and copy
the portion of last-minute changes to the replica. The replica becomes fully synchronized with the source
VM.

4. The VM is failed over to its replica.

5. The VM replica is powered on.

During the planned failover, Veeam Backup & Replication creates two helper restore points (steps 1 and 3) that
are not deleted afterwards. You can see these restore points in the list of restore points for the VM. You can use
the restore points later to roll back to the necessary VM replica state.

NOTE :

During planned failover, Veeam Backup & Replication always retrieves VM data from the production
infrastructure, even if the replication job uses the backup as a data source. This approach helps
Veeam Backup & Replication synchronize the VM replica to the latest state of the production VM.

Finalizing Planned Failover


When your primary host is online again, you can switch back to it. You can finalize planned failover in the same
ways as regular failover: undo failover, perform permanent failover or failback .

1506 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations for Planned Failover
Planned failover has the following limitations:

• If you start planned failover for several VMs that are replicated with one replication job, these VMs will be
processed one by one, not in parallel.

• Each planned failover task for each VM is processed as a separate replica job session. If a backup proxy is
not available and the session has to wait for resources, job sessions for other VMs in the same task cannot
be started before the current session is finished.

• The user account under which you launch the planned failover operation must have the Veeam Backup
Administrator role or Veeam Backup Operator and Veeam Restore Operator roles in
Veeam Backup & Replication. For more information, see Users and Roles.

Performing Planned Failover


For more information on planned failover, see Planned Failover and Failover and Failback for Replication.

To perform planned failover, use the P lanned Failover wizard.

Before You Begin


Before you perform planned failover, check the following prerequisites:

• VMs for which you plan to perform planned failover must be successfully replicated at least once.

• VM replicas must be in the Ready state.

1507 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Planned Failover Wizard
To launch the VMware P lanned Failover wizard, do one of the following:

• On the Home tab, click Restore and select Microsoft Hyper-V > Restore from replica > Entire replica >
P la nned failover to a replica.

• Open the Home view, expand the Rep licas node. In the working area, select one or more VMs and click
P la nned Failover on the ribbon. You can also right-click one of the selected VMs and click P lanned
Fa ilover.

• Open the Inventory view. In the working area, select one or more VMs and right-click one of the selected
VMs and click Restore > P lanned Failover.

1508 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VMs
At the Virtual Machines step of the wizard, you can modify a list of VMs from which you fail over. To add VMs or
VM containers, click Ad d > From infrastructure if you want to add VMs from the virtual infrastructure, or Ad d >
From replicas if you want to add VMs from existing replicas. Then select the necessary VMs or VM containers. If
you select VM containers, Veeam Backup & Replication will expand them to a plain VM list.

1509 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Failover Reason
At the Rea son step of the wizard, enter a reason for failing over to the replicas. The information you provide will
be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1510 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Finish Working with Wizard
At the Summary step of the wizard, review details of the failover task and click Finish to start the failover
process. Once planned failover is complete, VM replicas will be started on the target host.

What You Do Next


Planned failover is an intermediate step that needs to be finalized. You can finalize failov er in the following
ways:

• Perform permanent failover.

• Undo failover.

• Perform failback.

1511 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Failover Undo
Failover undo is one of the ways to finalize failover. When you undo failover, you switch back from a VM replica
to the source VM. Veeam Backup & Replication discards all changes made to the VM replica while it was in the
Failover state. You can use the undo failover scenario if you have failed over to the VM replica for testing and
troubleshooting purposes and want to get back to the normal operation mode.

The failover undo operation is performed in the following way:

1. Veeam Backup & Replication reverts the VM replica to its pre-failover state. To do this,
Veeam Backup & Replication powers off the VM replica and gets it back to the state of the latest snapshot
in the snapshot chain. Changes that were written to the snapshot differencing disk while the VM replica
was in the Failover state are discarded.

2. The state of the VM replica gets back to Ready , and Veeam Backup & Replication resumes replication
activities for the source VM on the source host.

Undoing Failover
For more information on failover undo, see Failover Undo and Failover and Failback for Replication.

To undo failover:

1. Open the Home view.

2. In the inventory pane, navigate to the Rep licas > Active node.

3. In the working area, select the necessary replica and click Und o Failover on the ribbon. As an alternative,
right-click one of the selected replicas and click Und o failover.

4. In the displayed window, do the following:

a. If you want to force failover undo, select the Force undo failover check box.

When you force failover undo, Veeam Backup & Replication attempts to perform the failover undo
operation in a regular way. If the host on which the VM replica resides is unavailable,
Veeam Backup & Replication changes the VM replica state to Ready in the configuration database and
console. This helps avoid failure of the failover undo operation.

1512 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. Click Y es.

1513 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failback
Failback is one of the ways to finalize failover. When you perform failback, you switch back to the production
VM from a VM replica, shift I/O processes from the disaster recovery site to the production site.
Veeam Backup & Replication also sends all change made to the VM replica while it was in the Failover state to
the production VM. However, note that these changes are only sent to the production VM but not published.

Veeam Backup & Replication provides you the following options to perform failback:

• You can fail back to the source VM in the original location.

• You can fail back to a VM already recovered to a new location. This VM must be recovered before you
perform failback. For example, you can recover the VM from a backup.

• You can fail back to a VM recovered from a replica to a new location, or to any location but with different
settings. The VM will be recovered from the replica during the failback process.

The first two options help you decrease recovery time and the use of the network traffic be cause
Veeam Backup & Replication needs to transfer only differences between the source/recovered VM and VM
replica. For the third option, Veeam Backup & Replication needs to transfer the whole VM data, including its
configuration and virtual disk content. Use the third option if there is no way to use the source VM or restore it
from a backup.

The process of failing back to the source VM or an already recovered VM differs from the process of failing back
to a VM recovered from a replica:

• How failback to the source VM and already recovered VM works.

• How failback to a VM recovered from a replica works.

How Failback to Source VM or Already Recovered VM Works


If you fail back to the source VM or an already recovered VM, Veeam Backup & Replicationperforms the
following operations:

1. If the source VM is running, Veeam Backup & Replication powers it off.

2. Veeam Backup & Replication calculates the difference between disks of the source VM and disks of the VM
replica in the Failover state. Difference calculation helps Veeam Backup & Replication understand what
data needs to be transported to the source VM to synchronize it with the VM replica.

3. Veeam Backup & Replication transports changed data to the source VM.

4. Veeam Backup & Replication powers off the VM replica. The VM replica remains powered off until you
commit failback or undo failback.

5. Veeam Backup & Replication creates a failback protective snapshot for the VM replica. The snapshot acts
as a new restore point and saves the pre-failback state of the VM replica. You can use this snapshot to
return to the pre-failback state of the VM replica afterwards.

6. Veeam Backup & Replication calculates the difference between the VM replica and the source VM once
again and transports changed data to the source VM. A new synchronization cycle lets
Veeam Backup & Replication copy a portion of last-minute changes made on the VM replica while the
failback process was being performed.

7. The state of the VM replica is changed from Failover to Failback . Veeam Backup & Replication temporarily
puts replication activities for the source VM on hold.

1514 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
8. If you failback to the source VM restored in a new location, Veeam Backup & Replication updates the ID of
the source VM in the Veeam Backup & Replication configuration database. The ID of the source VM is
replaced with the ID of the restored VM.

9. If you have selected to power on the source VM after failback, Veeam Backup & Replication powers on the
restored source VM on the target host.

How Failback to VM Recovered from Replica Works


If you fail back to a VM recovered from a replica, Veeam Backup & Replication performs the following
operations:

1. Veeam Backup & Replication transports all VM replica files and stores them on the volume in the
production site.

2. Veeam Backup & Replication registers a new VM on the production host.

3. If you have selected to power on the production VM after failback, Veeam Backup & Replication powers on
the restored VM on the production host.

Finalizing Failback
Failback is an intermediate step that needs to be finalized. If the production VM works as expected and you
want to get back to it, commit failback. If the VM does not work as expected, undo fail back.

Supported Platforms for Replica Failback

Failback to Original Location


You can fail back to an existing VM in original location from the target host of any version: 2008 R2 -2022.

1515 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failback to New Location
If you fail back to an entirely new location or to a new VM in the original location, the version of the target host
must be equal to or later than the version of the source host:

Source/Target Ta rget 2008 Ta rget 2012-2022 (the Target OS version must be higher than Source
R2 OS version)

Source 2008 R2 ✓ ✓

Source 2012- ✕ ✓
2022

IMP ORTANT

Consider the following exception: you can fail back from the source 2016 host to the target 2012 R2 host
only if a VM replica configuration is lower than 8.0.

Quick Rollback
If you fail back from a VM replica to the source VM in the original location, you can instruct
Veeam Backup & Replication to perform quick rollback. Quick rollback significantly reduces the failback time and
has little impact on the production environment.

During failback with the quick rollback option enabled, Veeam Backup & Replication does not calculate digests
for entire VM replica disks to get the difference between the source VM and VM replica. Instead, it queries CBT
to get information about disk sectors that have changed, and calculates digests only for these disk sectors. As a
result, digest calculation is performed much faster. After that, Veeam Backup & Replication performs failback in
a regular way: transport changed blocks to the source VM, powers off the VM replica and synchronizes the
source VM with the VM replica once again.

It is recommended that you use quick rollback if you fail back to the source VM after a problem that has
occurred at the level of the guest OS of the VM replica — for example, there has been an application error or a
user has accidentally deleted a file on the VM replica guest OS. Do not use quick rollback if the problem has
occurred at the VM hardware level, storage level or due to a power loss.

Requirements for Quick Rollback


To perform quick rollback, make sure that the following requirements are met:

• You must perform failback to the source VM in the original location.

• The VM replica must be created with the Use changed block tracking data option enabled.

Limitations for Quick Rollback


The following limitations apply to quick rollback:

• After you fail back to the source VM with quick rollback, the CBT on the source VM is reset. During the
subsequent replication job session, Veeam Backup & Replication will read data of the entire original VM.

1516 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Quick rollback is not supported if the source VM is also replicated using Hyper -V native replication
mechanisms.

Performing Failback
For more information on failback, see Failback and Failover and Failback for Replication.

To switch back to the source VM, use the Fa ilback wizard.

Before You Begin


Before you perform failback, check the following prerequisites:

• VMs for which you plan to perform failback must be successfully replicated at least once.

• VM replicas must be in the Failover state.

• On non-Microsoft Windows SMB3 storage, for example, Tintri, Veeam Backup & Replication may display
the " Failed to disable integrity bit on disk N " warning during VM restore. You can ignore this warning for
non-Microsoft Windows SMB3 storage.

• You must check the platform compatibility matrix. For more information, see Supported Platforms for
Replica Failback.

1517 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Failback Wizard
To launch the Fa ilback wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from replica > Entire replica > Failback to
p roduction.

• Open the Home view. In the inventory pane navigate to the Rep licas > Active node. In the working area,
select the necessary replica and click Fa ilback to Production on the ribbon.

• Open the Home view. In the inventory pane navigate to the Rep licas > Active node. In the working area,
right-click the necessary replica and select Fa ilback to production.

1518 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VM Replicas to Fail Back
At the Rep lica step of the wizard, select replicas from which you want to fail back.

To update the list of replicas that are ready for failback (replicas in the Failover state), click P op ulate.

1519 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Failback Destination
At the Destination step of the wizard, select a failback destination and backup proxies for data transfer during
failback:

1. Select a destination for failback. Veeam Backup & Replication supports the following options:

o Fa ilback to the original VM — select this option if you want to fail back to the source VMs that reside
on the source hosts. Veeam Backup & Replication will synchronize the state of the source VMs with
the current state of their replicas to apply any changes that occurred to the VM replicas while running
in the DR site.

If you select this option, you will proceed to the Summary step of the wizard.

o Fa ilback to the original VM restored in a different location — select this option if the source VMs have
already been recovered to a new location, and you want to switch to the recovered VMs from their
replicas. Veeam Backup & Replication will synchronize the state of the recovered VMs with the current
state of the VM replicas to apply any changes that occurred to the replicas while running in the DR
site.

If you select this option, you will proceed to the Target VM step of the wizard.

o Fa ilback to the specified location — select this option if you want to recover VMs from replicas. You
can recover VMs to a new location, or to any location but with different settings (such as network
settings, virtual disk type, configuration file path and so on). Select this option if there is no way to
fail back to the source VM or an already recovered VM.

If you select this option, the wizard will include additional steps.

If you select one of the first two options, Veeam Backup & Replication will send to the source/recovered
VMs only differences between the existing virtual disks. Veeam Backup & Replication will not send replica
configuration changes such as different IP address or network settings (if replica Re -IP and network
mapping were applied), new hardware or virtual disks added while the replicas were in the Failover state.

If you select Fa ilback to the specified location, Veeam Backup & Replication will send to the specified
location whole VM data, including VM configurations and virtual disk content.

1520 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. [For failback to the source VMs] If you want to fasten failback, and the source VMs had proble ms at the
guest OS level, select the Quick rollback check box. For more information on quick rollback, its
requirements and limitations, see Quick Rollback.

1521 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Target Host
The Host step is available if you have selected the Fa ilback to the specified location option at the Destination
step.

To specify a target host:

1. To specify a host where the recovered VMs will be registered, select the necessary VMs and click Host. In
the Select Server window, select a standalone or clustered host.

To quickly find the necessary hosts, you can use the search field at the top of the window.

2. If you choose to register a restored VM on a host that is a part of a Micros oft Hyper-V failover cluster, you
can register it as a cluster resource. To do this, select a VM in the list and click Resource. In the Cluster
Resource Settings section, choose Reg ister VM as a cluster resource. In this case, if the target host is
brought offline or fails for any reason, the VM will fail over to another node in the cluster.

1522 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Target Datastore
The Da tastore step is available if you have selected the Fa ilback to the specified location option at the
Destination step.

When restoring a VM from a replica, you can place an entire VM to a particular location or choose to store
configuration files and disk files of a restored VM in different locations:

1. If all VM files must be stored in one location, select the necessary VMs in the list.

2. If configuration and disk files of a VM should be placed to different locations, expand the VM in the list,
select the necessary files.

3. Click P a th.

4. In the Select Folder window, select a folder.

You can specify the following folders:

a. An existing folder on a host.

b. A new folder on a host. To do this, in the Select Folder window, select a location where the folder
must be created. Click New Folder and specify a folder name.

c. A Microsoft SMB3 shared folder. To do this, in the search field at the bottom of the Select Folder
window, enter a path to the Microsoft SMB3 shared folder. The path must be specified in the UNC
format, for example: \\172.16.11.38\Share01.

The host or cluster where you plan to register VMs must have access to the to the Microsoft SMB3
shared folder. If you are using Microsoft SCVMM 2012 or Microsoft SCVMM 2012 R2, the server
hosting the Microsoft SMB3 share must be registered in Microsoft SCVMM as a storage device. For
more information, see Microsoft Docs.

1523 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Target Network
The Network step is available if you have selected the Fa ilback to the specified location option at the
Destination step. This step applies if you fail back to VMs recovered to new locations, and if networks in those
locations differ from networks in the disaster recovery (DR) site.

At the Network step of the wizard create a network mapping table. This table maps networks in the DR site to
networks in the site where the recovered VMs will reside. Veeam Backup & Replication will use the network
mapping table to update configuration files of VMs on the fly, during the failback process.

To change networks to which the restored VMs will be connected:

1. In the Network connections list, select the necessary VMs and click Network.

If VMs are connected to multiple networks, select networks which you want to map.

2. In the list of available networks, select a network to which the recovered VMs will be connected.

If you do not want to connect the recovered VMs to any virtual network, select the necessary VMs and click
Disconnect.

1524 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify VM Name and VM UUID Handling
The Na me step is available if you have selected the Fa ilback to the specified location option at the Destination
step.

When restoring VMs from replicas, Veeam Backup & Replication uses source VM names and creates new VM
UUIDs. You can change names of the restored VMs, for example, if you restore a VM to its original location, you
want to change its name to avoid confusion. You can also choose to preserve the existing VM UUID, for example,
if the source VM no longer exists.

Changing VM Names
To change VM names:

1. Select one or more VMs in the list and click Na me.

2. In the Cha nge Name section, enter a new name or specify a change name rule by adding a prefix and suffix
to the regular VM name.

As an alternative, you can change VM names directly in the list: select a VM, click the New na me field and enter
the name to be assigned to the restored VM.

Changing UUID Settings


To change VM identification settings:

1. Select one or more VMs in the list and click VM UUID.

2. In the BIOS UUID Settings window, choose one of the following options:

o Select P reserve existing VM ID if the source VM was decommissioned, so the restored VM will be used
in place of the source one.

1525 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Select Generate new VM ID if you perform VM recovery to clone the source VM. Use this option to
avoid VM UUID conflicts in cases when the source VM and its duplicate will operate in parallel in the
same location.

1526 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Map Replicas to Restored VMs
The Ta rget VM step is available if you have selected the Fa ilback to the original VM restored in a different
loca tion option at the Destination step.

At the Ta rget VM step of the wizard, specify to which VMs you want to fail back from replicas. These VMs must
be already restored from backups in the required location.

1527 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Review Summary and Finish Working with Wizard
At the Summary step of the wizard, review the configured failback settings and click Finish.

If you want to power on the production VMs right after the switch to production operation is performed, select
the P ower on target VM after restoring check box.

What You Do Next


Failback is an intermediate step that needs to be finalized. You can finalize failback in the following ways:

• Commit failback.

• Undo failback.

1528 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failback Commit
Failback commit is one of the ways to finalize failback. When you commit failback, you confirm that the VM to
which you failed back (the production VM) and also changes sent to it during failback work as expected. After
the commit operation, Veeam Backup & Replication resumes replication activities for the production VM.

The failback commit operation is performed in the following way:

1. Veeam Backup & Replication changes the state of the replica from Failback to Ready .

2. Further operations depend on whether you have failed back to the source VM or recovered VM:

o If you have failed back to a VM recovered from a b ackup or replica, Veeam Backup & Replication
reconfigures all existing jobs where the source VM is present and adds the source VM to the list of
exclusions. The recovered VM takes the role of the source VM and is included into all jobs instead of
the excluded VM. When the replication job starts, Veeam Backup & Replication processes the
recovered VM instead of the former source VM.

o If you have failed back to the source VM, the replication job is not reconfigured. When the replication
job starts, Veeam Backup & Replication still processes the source VM.

During failback commit, the failback protective snapshot that saves the pre-failback state of a VM replica is not
deleted. Veeam Backup & Replication uses this snapshot as an additional restore point for VM replica. With the
pre-failback snapshot, Veeam Backup & Replication needs to transfer fewer changes and therefore puts less
load on the network when replication activities are resumed.

Committing Failback
For more information on failback commit, see Failback Commit and Failover and Failback for Replication.

To commit failback:

1. Open the Home view.

2. In the inventory pane, navigate to the Rep licas > Active node.

1529 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the necessary replica and click Commit Failback on the ribbon. As an
alternative, you can right-click the replica and select Commit failback.

1530 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Failback Undo
Failback undo is one of the ways to finalize failback. When you undo failback, you confirm that the VM to which
you failed back (the production VM) and changes sent to it during failback work in a wrong way and you want to
get back to the replica.

The failback undo operation is performed in the following way:

1. Veeam Backup & Replication deletes the protective failback snapshot on the VM replica.

2. Veeam Backup & Replication powers on the VM replica and changes the VM replica state from Failback to
Failover.

Undoing Failback
For more information on failback undo, see Failback Undo and Failover and Failback for Replication.

To undo failback:

1. Open the Home view.

2. In the inventory pane, navigate to the Rep licas > Active node.

1531 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the necessary replica and click Und o Failback on the ribbon. Alternatively, you
can right-click the necessary replica and select Und o Failback.

1532 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Backup
With Veeam Backup & Replication you can easily back up and restore unstructured data: content of various file
shares and object storage repositories.

NOTE

The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131).

1533 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Infrastructure for Unstructured
Data Backup
To protect your unstructured data, you can use your existing Veeam Backup & Replication infrastructure. To do
so, configure the following components:

• Unstructured Data Source:

o File shares

o Object storage

• General-purpose backup proxies

• Cache repository

• Storage repositories

For system requirements for unstructured data backup components, see the System Requirements section.

NOTE

Backup of the content of file shares and object storage repositories is not supported by Veeam Cloud
Connect.

To learn how backup components interact during the unstructured data backup, see the How Unstructured Data
Backup Works section.

Unstructured Data Source


Unstructured data supported as a source for backup by Veeam Backup & Replication includes:

• File shares

• Object storage

1534 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
File Shares
A file share is a storage device or data source available to multiple hosts through a computer network.

For supported file shares, requirements and limitations, see the Platform Support section.

File backup jobs in Veeam Backup & Replication can read data from the following sources:

• SMB (CIFS) path

• NFS path

• Path to the storage snapshot folder

• VSS snapshot

NOTE

Consider the following limitations:

• Reading from VSS snapshots on SMB shares is available only under certain conditions, listed in this
Veeam KB article.
• Reading from VSS snapshots on DFS shares is not supported.
• Names of NTFS Alternate Data Streams (ADS) may be unencrypted if both the file being backed up
and its ADS are empty.

To learn how to add file shares to the inventory of the virtual infrastructure, see the Adding Unstructured Data
Source section.

Object Storage
An object storage is storage based on either a cloud solution or an S3 compatible on-premise storage solution.

For supported object storage, requirements and limitations, see the Platform Support section.

To learn how to add object storage as a source for backup to the inventory of the virtual infrastructure, se e the
Adding Object Storage section.

General-Purpose Backup Proxies


A general-purpose backup proxy is an architecture component that sits between the unstructured data source
and other components of the backup infrastructure. The backup proxy operates as a data mover that transfers
data between the data source and the backup repository. The backup proxy processes jobs and delivers backup
and restore traffic.

For more information on general-purpose backup proxies, their requirements, limitations and deployment, see
the General-Purpose Backup Proxies section.

After you configure the backup proxy, choose it to process the backup traffic from unstructured data sources, as
described in the Adding NFS File Share, Adding SMB File Share, Adding S3 Compatible Object Storage, Adding
Amazon S3 Object Storage, and Adding Microsoft Azure Blob Storage sections.

1535 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Cache Repository
A cache repository is a storage location where Veeam Backup & Replication keeps temporary metadata and uses
it to reduce the load on the data source during the backup procedure. The cache repos itory keeps track of all
objects that have changed between each backup session. This allows performing incremental backups from the
unstructured data source fast and efficiently. If you store your unstructured data backups on an object storage
repository, the cache repository also stores active metadata. For more information, see the Data Structure in
Backup, Archive and Secondary Repositories and Unstructured Data Backups in Object Storage Repositories
sections.

You can assign the role of a cache repository to a simple backup repository added to the
Veeam Backup & Replication infrastructure. To assign this role, select the backup repository as a cache
repository when adding an unstructured data source.

To minimize the network load during backup, locate the cache repository closer to the backup proxy in the
computer network: at the best, they should be located on one machine.

Storage Repositories
A b a ckup repository is a main storage location where Veeam Backup & Replication keeps all versions of backed
up files for the configured period and metadata files. Backups stored in the backup repository can be used to
quickly restore the entire file share to the state as of a sp ecific restore point.

[Optional] If you want to retain specific files for a longer period of time, you can use cheaper devices for archive
purposes. To enable file archiving, configure Veeam Backup & Replication to move backup files and metadata
files from the backup repository to an a rchive repository. By default, usage of the archive repository is disabled
and, after the retention period for the backup repository is over, backup files are deleted.

[Optional] If you want to store a copy of the unstructured data backup in a different repository, you can
configure a secondary repository where Veeam Backup & Replication will copy all backups created in the backup
repository. The secondary repository can have its own retention policy and encryption settings. By default, no
secondary repository is configured.

The table below describes which roles can be assigned to different storage types.

Secondary
Storage Type Ba ckup Repository Archive Repository
Rep ository

Microsoft Windows server

Linux server

Hardened linux server

SMB (CIFS) share 1

NFS share

Dell Data Domain with Data Domain


Boost (DDBoost) license

1536 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Secondary
Storage Type Ba ckup Repository Archive Repository
Rep ository

ExaGrid

HPE StoreOnce with Catalyst license 2

Quantum DXi

Fujitsu ETERNUS CS800

Infinidat InfiniGuard

Scale-out backup repository (SOBR) 3, 4

Object storage repository 5

Repository with rotated drives

Veeam Cloud Connect repository

1
If you use a Dell PowerScale (formerly Isilon) storage system in the CIF S Share Access mode, make sure that you have
assigned your service account to the built-in Bac kupAdmin role within PowerScale. Otherwise, the access to the share will be
denied.
2
If you plan to use HPE StoreOnce storage appliances, consider the following recommendation s for optimal performance:
• A StoreOnce system can have multiple Catalyst stores, and large backup loads (exceeding 1PB) should be spread
across more than one Catalyst store on the same StoreOnce system.
• Do not include Catalyst stores in a SOBR intended for unstructured data backups. This will reduce the global
deduplication of the StoreOnce system.
3
An object storage repository added as a capacity tier in a scale-out backup repository cannot be used for storing
unstructured data backups. To archive unstructured data backup files to an object storage repository, assign the object
storage repository as an archive repository when you create a file backup job.
4
SOBR consisting of object storage repositories cannot be used as a target backup repository for file backup jobs.
5
Consider the following limitations:
• Amazon S3 Glacier and Azure Blob Storage Archive Tier are not supported for unstructured data backup.
• Amazon S3 Snowball Edge and Azure Databox are not supported as archive repositories for unstructured data backup,
but you can use them as backup repositories, secondary repositories, or targets for copying file share backups.
You can create two object storage repositories pointing to the same cloud folder/bucket and use these repositories for
storing both unstructured data backups and Capacity Tier backups at the same time: one object storage repository will be
used to store unstructured data backups, the other one – to store virtual and physical machine backups as a capacity tier in a
single SOBR. However, these object storage repositories (mapped to the same cloud folder) must not be used across
multiple Veeam Backup & Replication servers for the same purposes as it leads to unpredictable system behavior and
inevitable data loss.

1537 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deployment of Backup, Archive and Secondary Repositories
To use a storage, which is already added to the Veeam Backup & Replication Backup Infrastructure, to store
unstructured data backups, define it as a target storage when creating a file backup job or an object storage
backup job:

• Configure the backup repository at the Ba ckup Repository step of the wizard when creating file backup
jobs and object storage backup jobs.

• Configure the backup repository at the Archive Repository step of the wizard when creating file backup
jobs and object storage backup jobs.

• Configure the backup repository at the Secondary Target step of the wizard when creating file backup jobs
and object storage backup jobs.

If the required storage is not added as a backup repository in your Veeam Backup & Replication Backup
Infrastructure, add it as described in the Backup Repositories section.

1538 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Unstructured Data Source
You must add sources of unstructured data, which you plan to protect with the unstructured data backup, to the
inventory of the virtual infrastructure.

You can add the following types to the inventory of your virtual infrastructure:

• Windows-managed or Linux-managed file server

• File shares

o SMB file share

o NFS file share

• Enterprise NAS system as a NAS filer

• Object storage

Adding File Server


Before you add a Windows- or Linux-managed server as a file server to the inventory of the virtual
infrastructure, consider the following:

• This server must meet requirements listed in the Platform Support section.

• You must have this server added in Ba ckup Infrastructure.


For more information on how to add servers, see the Adding Microsoft Windows Servers and Adding Linux
Servers section.

• If you plan to use a dedicated cache repository, make sure it is added in Ba ckup Infrastructure.

• Data from managed servers is transferred directly to the repository without a proxy server.

1539 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New File Server Wizard
To launch the New File Server wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the Unstructured Data (File Shares – for version 12) node and select
Ad d unstructured data source (Add file share – for version 12).

o Select the Unstructured Data (File Shares – for version 12) node and click Ad d Data Source (Add File
Sha re – for version 12) on the ribbon.

o Select the Unstructured Data (File Shares – for version 12) node and click Ad d Data Source (Add File
Sha re – for version 12) in the working area.

3. In the Ad d Unstructured Data Source (Add File Share – for version 12) window, click File server.

1540 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Add Managed Server
At the File Server step of the wizard, choose the server, which you want to use as a file share server. Select it
from the Ma naged Server drop-down list.

NOTE

If you plan not only to back up the Linux-managed file server, but also to restore files to it, use an account
with root access when adding the server to the backup infrastructure.

If the drop-down list does not display the required server, you must add it to the backup infra structure. To add
the server, do the following:

1. Click Ad d New.

2. Select Microsoft Windows Server or Linux Server.

3. Add a new Windows or Linux server to the backup infrastructure as described in the Adding Microsoft
Windows Servers and Adding Linux Servers sections.

4. Select the newly added server from the Ma naged Server drop-down list.

1541 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify File Server Processing Settings
At the P rocessing step of the wizard, define file server processing settings:

1. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located as close to the source file share as possible.

If you change the cache repository for an existing file server whose backups are stored in the object
storage, Veeam Backup & Replication will prompt you to either attach migrated metadata, copy metadata
from the previous cache repository, or download metadata manually from the archive repository. For more
information on storing unstructured data backups in the object storage and changing the cache repository,
see the Unstructured Data Backups in Object Storage Repositories section.

2. Use the Ba ckup I/O control slider to define how fast the backup proxy can read data from the source file
server. This setting is based on the number of parallel threads that can be used by the proxy configured
for processing the file server. If resources of your file server are limited, it is recommended that you select
the Lower impact option. If your file server is powerful enough, select the Fa ster backup option.

3. Click Nex t to save the configured settings.

1542 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Review Components to Install
At the Review step of the wizard, review what Veeam Backup & Replication components are already installed on
the server and click Ap p ly to start installation of missing components.

1543 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply File Share Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components. Click Nex t to complete the procedure of the file share role assignment to the managed file server.

1544 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review details of the added file server and click Finish to exit the wizard.

1545 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Settings for Connected Volumes
NOTE

This feature is available for Windows-based servers only.

Before you specify settings for a managed server added as a file server, you must rescan its volumes. During
volume rescan, Veeam Backup & Replication retrieves information about disks and volumes that are currently
connected to the server and writes this information to the configuration database.

Veeam Backup & Replication automatically performs volume rescan every 4 hours. You can also start volume
rescan manually:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, select the server and click Rescan on the ribbon. Alternatively, you can right-click the
host and select Rescan.

After you add a managed server as a file server to the inventory of the virtual infrastructure, you can configure
the following settings for it:

• Specify volume-specific settings.

• Enable or disable failover to direct backup if a snapshot is not available.

Volume-Specific Settings
You can define volume-specific settings for the file server: select what VSS provider must be used for snapshot
creation and specify the maximum number of concurrent snapshots that must exist for the volume.

To specify volume-specific settings:

1. Open the Inventory view.

2. In the inventory pane, select Unstructured Data – File Servers.

3. In the working area, select the server and click Ma nage Volumes on the ribbon. Alternatively, you can
right-click the managed server and select Ma nage volumes.

4. Select the volume in the list and click E d it.

5. Specify VSS provider settings for the volume:

o To take a VSS snapshot of a specific volume, Veeam Backup & Replication uses one of VSS providers
available for this volume. To explicitly define what VSS provider must be used for the volume, select
the VSS provider from the VSS p rovider list.

o You can simultaneously store 4 snapshots of one volume. To change this number, specify the Ma x
sna pshots value. It is not recommended that you increase the number of snapshots for a slow storage.
Many snapshots existing at the same time may cause VM processing failures.

1546 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Click OK to save the changes.

Failover to Direct Backup Settings


If snapshots for volumes are not available, Veeam Backup & Replication may automatically fail over to direct
backup.

By default, the failover option is enabled. To disable failover to direct backup:

1. Open the Inventory view.

2. In the inventory pane, select Unstructured Data – File Servers.

3. In the working area, select the server and click Ma nage Volumes on the ribbon. Alternatively, you can
right-click the managed server and select Ma nage volumes.

4. In the Ma nage Volumes window, clear the Fa ilover to direct backup if a snapshot is not available check
box.

IMP ORTANT

We do not recommend to clear the Fa ilover to direct backup if a snapshot is not available check box, as it
may result in the file backup job failure if a snapshot is not available for the volume.

1547 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding File Share
You can add NFS and SMB file shares as a source of unstructured data available for protection by
Veeam Backup & Replication.

Adding SMB File Share


Before you add an SMB file share to the inventory of the virtual infrastructure, consider the following:

• The file share meets requirements listed in the Platform Support section.

• If you plan to use a dedicated proxy server or cache repository, make sure these components are added in
Ba ckup Infrastructure.

1548 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New File Share Wizard

To launch the New File Share wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the File Shares node and select Ad d File Share.

o Select the File Shares node and click Ad d File Share on the ribbon.

o Select the File Shares node and click Ad d File Share in the working area.

3. In the Ad d File Share window, click SMB share.

1549 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Path to SMB File Share and Access Credentials

At the SMB File Share step of the wizard, specify access settings for the SMB file share:

1. In the SMB server of file share field, specify the path to an SMB file share in the \\server\folder format.
You can specify the IPv4 or IPv6 address of the server. Note that you can use IPv6 addresses only if IPv6
communication is enabled as described in the IPv6 Support section.

You can also click Browse and select the shared folder from the list of available network shares.

You can add the root server folder in the \\server format to protect all SMB file shares residing on this
server. After that, create a single file backup job to protect the added server, as described in the Creating
File Backup Jobs section. Then all SMB file shares added on this server will be automatically processed
with the file backup job and protected. If you previously had several separate non-root shared folders
residing on the same server and want to switch to using a single root shared folder to cover the same
shares, you do not have to run full backups to update data of protected shares. Instead, you can convert
existing backups and update existing file backup jobs to protect single root shared f olders comprising all
other non-root shared folders residing on the same server. To learn more about the conversion, see the
Converting Backups from Non-Root to Root Shared Folders section. Perform the conversion with extreme
caution.

2. If you must specify user credentials to access the shared folder, select the This share requires access
credentials check box. From the Credentials drop-down list, select a credentials record for a user account
that has Full Control permissions on the shared folder.

To access the SMB share, you must use an account that meets either of the following requirements:

o If you only plan to back up the share, you can use an account with read-only permissions.

o If you plan not only to back up the share, but also to restore files to it, use an account with read/write
permissions.

NOTE

Accessing the SMB file share with credentials in the User Principal Name format ( [email protected] )
is not supported.

If you have not set up credentials beforehand, click the Ma nage accounts link at the bottom of the list or
click Ad d on the right to add the credentials. For more information, see the Managing Credentials section.

NOTE

If the This share requires access credentials check box is not selected, Veeam Backup & Replication
uses the computer account of the proxy server to access the file share.

1550 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1551 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Advanced SMB File Share Settings

You can instruct Veeam Backup & Replication to back up data from Microsoft VSS snapshots or native storage
snapshots. During backup jobs, Veeam Backup & Replication will read data of shared files and folders from
snapshots, which speeds up backup operations and improves RPOs.

To define if Veeam Backup & Replication will use snapshots for backups:

1. At the SMB File Share step of the wizard, click Ad vanced.

2. In the Ad vanced window, select one of the following options:

o To ignore the snapshot functionality, select Ba ck up directly from the file share.

Veeam Backup & Replication will ignore locked files and folders. When creating a backup job, you can
configure notifications to list files and folders that are skipped during the backup procedure. For more
information see the Notification Settings section.

o To back up files from Microsoft VSS snapshots, select Ba ckup from a Microsoft VSS snapshot.

If you select this option, make sure that the file share and the backup proxy used for the file backup
job support SMB protocol version 3.0 or later.

o To back up files from the native storage snapshot, select Ba ckup from a storage snapshot at the
following path and specify the path in the \\server\snapshotfolder\snapshotname format to the
snapshot stored on the SMB file share. You can specify the IPv4 or IPv6 address of the server. Note
that you can use IPv6 addresses only if IPv6 communication is enabled as described in the IPv6
Support section.

If you select this option, you can additionally use custom scripts written by you, for example, to
create a snapshot before the backup and remove it after the backup. You can define these scripts
when creating a new file backup job, as described in the Script Settings section.

NOTE

Consider that Veeam Backup & Replication does not take snapshots itself, but it can use a snapshot
taken by the storage system.

File backup jobs do not trigger the storage snapshot creation and deletion automatically. You can
specify the folder where the storage snapshot is stored. In this case file backup jobs can access this
folder and read data from the storage snapshot.

1552 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Select Fa ilover to direct backup if snapshot is not available if you want Veeam Backup & Replication to
read data for backup directly from the file share when the snapshot is unavailable. If you do not select the
option and the snapshot is unavailable, the file backup job will stop with a failure.

1553 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify File Share Processing Settings

At the P rocessing step of the wizard, do the following:

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

2. In the Ba ckup Proxy window, select proxy servers:

o If you select All p roxies, Veeam Backup & Replication will use all available backup proxies for file
backup. The number of proxies in use defines the number of data threads that transfer data from the
file share to the backup repository. The more data transfer threads Veeam Backup & Replication uses,
the higher is the data transfer speed.

If the file share is used as a source for a file to tape backup job, the tape server utilized for this job is
added as yet another backup proxy when creating a file to tape backup job. This backup proxy has the
highest priority over all others and is used by default if it has access rights to the file share. For details
on file to tape backup jobs, see the File Backup to Tape section in the Veeam Backup & Replication
User Guide.

o If you select Use the selected backup proxies only, you can explicitly specify backup proxies that
Veeam Backup & Replication must use for file backup.

It is recommended that you select at least two backup proxies to ensure that the backup jobs start
even if one of the proxies fails or loses its connectivity to the source file share. The more proxies you
select, the more data transfer threads Veeam Backup & Replication will use for backup jobs, thus
improving performance.

Even if the file share is used as a source for file to tape backup jobs, Veeam Backup & Replication will
use only proxies selected in the list to process the backup data traffic.

1554 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located in the close proximity to the source file share and backup proxies.

If you change the cache repository for an existing file share whose backups are stored in object storage,
Veeam Backup & Replication will prompt you to either attach migrated metadata, copy metadata from the
previous cache repository, or download metadata manually from the archive repository. For more
information on storing NAS backups in the object storage and changing the cache repository, see the
Unstructured Data Backups in Object Storage Repositories section.

4. Use the Ba ckup I/O control slider to define how fast all proxies can read data from the source file share.
This setting is based on the number of parallel threads that can be used by all the proxies configured for
processing the file share. If resources of your NAS device are limited, it is recommended that you select
the Lower impact option. If your NAS device is powerful enough, select the Fa ster backup option.

5. Click Ap p ly to save the configured settings.

1555 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply File Share Settings

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the SMB file share to the backup infrastructure. Click Nex t to proceed.

1556 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard

At the Summary step of the wizard, review details of the added SMB share and click Finish to exit the wizard.

Adding NFS File Share


Before you add an NFS file share to the inventory of the virtual infrastructure, consider the following:

• The file share meets requirements listed in Platform Support.

• If you plan to use a dedicated backup proxy server or cache repository, make sure these components are
added in Backup Infrastructure.

1557 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New File Share Wizard

To launch the New File Share wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the File Shares node and select Ad d File Share.

o Select the File Shares node and click Ad d File Share on the ribbon.

o Select the File Shares node and click Ad d File Share in the working area.

3. In the Ad d File Share window, click NFS share.

1558 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Path to NFS File Share

At the NFS File Share step of the wizard, specify the path to an NFS file share in the server:/folder format.

You can add the root server folder in the server:/format to protect all NFS file shares residing on this server. You
can specify the IPv4 or IPv6 address of the server. Note that you can use IPv6 addresses only if IPv6
communication is enabled as described in the IPv6 Support section.

After that, create a single file backup job to protect the added server, as described in the Creating File Backup
Jobs section. Then all NFS file shares added on this server will be automatically processed with the file backup
job and protected. If you previously had several separate non-root shared folders residing on the same server
and want to switch to using a single root shared folder to cover the same shares, you do not have to run full
backups to update data of protected shares. Instead, you can convert existing backups and update ex isting file
backup jobs to protect single root shared folders comprising all other non-root shared folders residing on the
same server. To learn more about the conversion, see the Converting Backups from Non-Root to Root Shared
Folders section. Perform the conversion with extreme caution.

1559 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Advanced NFS File Share Settings

You can instruct Veeam Backup & Replication to back up data from native storage snapshots. During backup
jobs, Veeam Backup & Replication will read data of shared files and folders from snapshots, which speeds up
backup operations and improves RPOs.

To define if Veeam Backup & Replication will use snapshots for backups:

1. At the NFS File Share step of the wizard, click Ad vanced.

2. In the Ad vanced window, select one of the following options:

o To ignore the snapshot functionality, select Ba ck up directly from the file share.
Veeam Backup & Replication will ignore locked files and folders. When creating a backup job, you can
configure notifications to list files and folders that are skipped during the backup procedure. For more
information see the Notification Settings section.

o To back up files from the native storage snapshot, select Ba ckup from a storage snapshot at the
following path and specify the path in the server:/snapshotfolder/snapshotname format to the
snapshot stored on the NFS file share. You can specify the IPv4 or IPv6 address of the server. Note
that you can use IPv6 addresses only if IPv6 communication is enabled as described in section t he
IPv6 Support section.

If you select this option, you can additionally use custom scripts written by you, for example, to
create a snapshot before the backup and remove it after the backup. You can define these scripts
when creating a new file backup job, as described in the Script Settings section.

NOTE

Consider that Veeam Backup & Replication does not take snapshots itself, but it can use a snapshot
taken by the storage system.

File backup jobs do not trigger the storage snapshot creation and deletion automatically. You can
specify the folder where the storage snapshot is stored. In this case file backup jobs can access this
folder and read data from the storage snapshot.

1560 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Select Fa ilover to direct backup if a snapshot is not available if you want Veeam Backup & Replication to
read data for backup directly from the file share when the snapshot is unavailable. If you do not select the
option and the snapshot is unavailable, the file backup job will stop with a failure.

1561 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify File Share Processing Settings

At the P rocessing step of the wizard, do the following:

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

2. In the Ba ckup Proxy window, select proxy servers:

o If you select All p roxies, Veeam Backup & Replication will use all available backup proxies for file
backup. The number of proxies in use defines the number of data threads that transfer data from the
file share to the backup repository. The more data transfer threads Veeam Backup & Replication uses,
the higher is the data transfer speed.

If the file share is used as a source for a file to tape backup job, the tape server utilized for this job is
added as yet another backup proxy when creating a file to tape backup job. This backup proxy has the
highest priority over all others and is used by default if it has access rights to the file share. For details
on file to tape backup jobs, see the File Backup to Tape section in the Veeam Backup & Replication
User Guide.

o If you select Use the selected backup proxies only, you can explicitly specify backup proxies that
Veeam Backup & Replication must use for file backup.

It is recommended that you select at least two backup proxies to ensure that the backup jobs start
even if one of the proxies fails or loses its connectivity to the source file share. The more proxies you
select, the more data transfer threads Veeam Backup & Replication will use for backup jobs, thus
improving performance.

Even if the file share is used as a source for file to tape backup jobs, Veeam Backup & Replication will
use only proxies selected in the list to process the backup data traffic.

1562 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located as close to the source file share as possible.

If you change the cache repository for an existing file share whose backups are stored in object storage,
Veeam Backup & Replication will prompt you to either attach migrated metadata, copy metadata from the
previous cache repository, or download metadata manually from the archive repository. For more
information on storing NAS backups in the object storage and changing the cache repository, see the
Unstructured Data Backups in Object Storage Repositories section.

4. Use the Ba ckup I/O control slider to define how fast all proxies can read data from the source file share.
This setting is based on the number of parallel threads that can be used by all the proxies configured for
processing the file share. If resources of your NAS device are limited, it is recommended that you select
the Lower impact option. If your NAS device is powerful enough, select the Fa ster backup option.

5. Click Ap p ly to save the configured settings.

1563 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Apply File Share Settings

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the NFS file share to the backup infrastructure. Click Nex t to proceed.

1564 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard

At the Summary step of the wizard, review details of the added NFS share and click Finish to exit the wizard.

Adding Enterprise Storage System as NAS Filer


Before you add an enterprise storage system as a NAS filer to the inventory of the virtual infrastructure,
consider the following:

• The NAS device meets requirements listed in section Platform Support.

• If you plan to use a dedicated backup proxy or cache repository, make sure these components are added in
Backup Infrastructure.

• When a storage virtual machine (SVM) has both the NFS and SMB protocols enabled, but the SVM does
not export any NFS shares, file backup jobs configured to protect NFS file shares on that SVM fail. To fix
this, either disable the NFS protocol on the SVM, or disable NFS protocol for the storage in
Veeam Backup & Replication. You can do the latter by clearing the NFS check box at the NAS Filer step of
the wizards described in the Adding NetApp Data ONTAP, Adding Lenovo ThinkSystem DM Series, Adding
Dell PowerScale (formerly Isilon) or Adding Nutanix Files Storage sections.

• When a storage virtual machine (SVM) has both the NFS and SMB protocols enabled, but the SVM does
not export any NFS shares, file backup jobs reading from that SVM fail. To fix this, eithe r disable the NFS
protocol on the SVM, or disable NFS protocol for the storage in Veeam Backup & Replication. You can do
the latter by clearing the NFS check box at the NAS Filer step of the Editing NetApp Data ONTAP, Editing
Lenovo ThinkSystem DM Series, Editing Dell PowerScale (formerly Isilon) or Editing Nutanix Files Storage
wizard.

1565 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New NAS Filer Wizard
To launch the New NAS Filer wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the Unstructured Data (File Shares – for version 12) node and select
Ad d unstructured data source (Add File Share – for version 12).

o Select the Unstructured Data (File Shares – for version 12) node and click Ad d Data Source (Add File
Sha re – for version 12) on the ribbon.

o Select the Unstructured Data (File Shares – for version 12) node and click Ad d Data Source (Add File
Sha re – for version 12) in the working area.

3. In the Ad d Unstructured Data Source window, click NAS filer.

1566 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select NAS Device
At the NAS Filer step of the wizard, choose the NAS device, which you want to use as a NAS filer where
protected file shares reside.

1. Select the required NAS device from the Select NAS filer drop-down list.

If the drop-down list does not display the required device, you must add it to the storage infrastructure.
To add the NAS device, click Ad d New and follow the instructions described in the Adding NetApp Data
ONTAP, Adding Lenovo ThinkSystem DM Series, Adding Dell PowerScale, or Adding Nutanix Files Storage
sections, depending on the type of the storage system you use.

2. If you must specify user credentials to access the storage system, select the Use the following account to
a ccess the NAS filer check box. From the Credentials drop-down list, select a credentials record for a user
account that has Full Control permissions on the storage system.

[For Nutanix Files Storage] When adding a Nutanix Files Storage as a NAS filer, use credentials of an AD
user account with administrator privileges added as a file server admin or backup admin. Otherwise,
Veeam Backup & Replication cannot access SMB file shares.

If you have not set up credentials beforehand, click the Ma nage accounts link at the bottom of the list or
click Ad d on the right to add the credentials. For more information, see Managing Credentials.

Integration with Dell PowerScale (formerly Isilon)


To provide proper integration of Veeam Backup & Replication with Dell PowerScale (formerly Isilon) to
implement the NAS backup functionality, consider the following:

• The Dell PowerScale system must be licensed for SnapshotIQ. Otherwise NAS integration will not work.

1567 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The PowerScale service account is used to add the Dell PowerScale system to
Veeam Backup & Replication, as described in the Adding Dell PowerScale section in the Storage System
Snapshot Integration Guide. This account is used only for registering the storage system in the backup
infrastructure and further storage rescans. You cannot use it for NAS file share backup and restore.

• We recommend that you create a custom Veea mStorageIntegration role to group all necessary privileges.
This role must be created in the System access zone. For more information on access zones, see the Dell
documentation.

Add the following privileges to the Veea mStorageIntegration role:

P rivilege ID Rea d Comments


Only

ISI_PRIV_LOGIN_PAPI True Used to log in to the Platform API and the web administration
interface.

ISI_PRIV_AUTH True Used to configure external authentication providers, including


root-level accounts.

ISI_PRIV_DEVICES True Used to create new roles and assign privileges.

ISI_PRIV_JOB_ENGINE False Used for array Change File Tracking report scheduling for
R/W changelist API call.

ISI_PRIV_NETWORK True Used to configure network interfaces.

ISI_PRIV_NFS R/W False Used to update export rules.

ISI_PRIV_SMB True Used to configure the SMB server.

ISI_PRIV_SNAPSHOT False Used to schedule, take, and view snapshots.


R/W

For more information on privileges, see the PowerScale documentation.

You can use the following command to check privileges added to the Veea mStorageIntegration role:

isi auth roles view VeeamStorageIntegration

Make sure that you make the service account to be used for NAS integration a member of the
VeeamStorageIntegration role.

• To enable backup and restore of SMB file shares, additionally do the following:

o Grant minimum read access to SMB file shares for the account that will be used for NAS integration.
That will allow backing up SMB file shares.

1568 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Grant "run as root" access to SMB file shares for the account that will be used for NAS integration.
That will allow restoring SMB file shares.

Consider that the PowerScale BackupAdmin role is not enough for backup and restore. It is mainly used for
SMB access and enables backup and restore of files from /ifs. It does not propagate down to subfolders
and therefore cannot be used to backup anything, but the system access zone.

1569 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify File Share Processing Settings
At the P rocessing step of the wizard, define NAS filer processing settings:

1. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located as close to the NAS filer as possible.

NOTE

Consider that you cannot use a Linux-based server as a cache repository to process content of the
protected shares on enterprise storage systems if you enable the Use native changed files tracking
option.

If you change the cache repository for an NAS filer whose backups are stored in the object storage,
Veeam Backup & Replication will prompt you to either attach migrated metadata, copy metadata from the
previous cache repository, or download metadata manually from the archive repository. For more
information on storing file backups in the object storage and changing the cache repository, see the
Unstructured Data Backups in Object Storage Repositories section.

2. Use the Ba ckup I/O control slider to define how fast the backup proxy can read data from the source NAS
filer. This setting is based on the number of parallel threads that can be used by the proxy configured for
processing the file shares on the NAS filer. If resources of your storage system are limited, it is
recommended that you select the Lower impact option. If your storage system is powerful enough, select
the Fa ster backup option.

3. [For Dell PowerScale (formerly Isilon) and Nutanix Files] Select the Use native changed files tracking
check box if you want to use the file change tracking technology provided by the storage system
manufacturer.

4. Click Nex t to save the configure settings.

1570 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Apply File Share Settings
At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components. Click Nex t to complete the procedure of adding the storage system as a NAS filer.

1571 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Summary step of the wizard, review details of the storage system added as a NAS filer and click Finish to
ex it the wizard.

Adding Object Storage


You can add various object storage repositories as a source of unstructured data available for protection by
Veeam Backup & Replication.

NOTE

The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131).

Adding S3 Compatible Object Storage


Before you add an S3 compatible object storage to the inventory of the virtual infrastructure, consider the
following:

• The object storage meets requirements and limitations listed in the Platform Support section.

• If you plan to use dedicated proxy servers, make sure these components are added in the Backup
Infrastructure.

1572 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Wizard

To launch the New Object Storage wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the Unstructured Data node and select Ad d unstructured data
source.

o Select the Unstructured Data node and click Ad d Data Source on the ribbon.

o Select the Unstructured Data node and click Ad d Data Source in the working area.

o If at least one object storage is added as the unstructured data source, open the Ob ject Storage node,
right-click empty-space in the working area and click Ad d object storage. Alternatively, you can right-
click the Ob ject Storage node, and click Ad d object storage.

3. In the Ad d Unstructured Data Source window, select Ob ject storage > S3 Compatible.

1573 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Account Settings

At the Account step of the wizard, specify a friendly name and connection settings of your object storage:

1. In the Friendly name field, specify a name you want to assign to your object storage. This name will
display in the list of you object storage repositories in the inventory of the virtual infrastructure.

2. In the Service point field, specify a service point address of your object storage.

3. From the Credentials drop-down list, select user credentials to access your S3 compatible object storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

4. In the Reg ion field, specify a region.

1574 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Processing Settings

At the P rocessing step of the wizard, do the following:

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

2. In the Ba ckup Proxy window, select proxy servers:

o If you select All p roxies, Veeam Backup & Replication will use all available backup proxies for the
object storage backup. The number of proxies in use defines the number of data threads that transfer
data from the object storage to the backup repository. The more data transfer threads
Veeam Backup & Replication uses, the higher is the data transfer speed.

If the object storage is used as a source for an object to tape backup job, the tape server utilized for
this job is added as yet another backup proxy when creating an object to tape backup job. This backup
proxy has the highest priority over all others and is used by default if it has access rights to the object
storage. For details on object to tape backup jobs, see the Object Storage Backup to Tape section in
the Veeam Backup & Replication User Guide.

o If you select Use the selected backup proxies only, you can explicitly specify backup proxies that
Veeam Backup & Replication must use for the object storage backup.

It is recommended that you select at least two backup proxies to ensure that the backup jobs start
even if one of the proxies fails or loses its connectivity to the source object storage. The more proxies
you select, the more data transfer threads Veeam Backup & Replication will use for backup jobs, thus
improving performance.

Even if the object storage is used as a source for object to tape backup jobs,
Veeam Backup & Replication will use only proxies selected in the list to process the backup data
traffic.

1575 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located in the close proximity to the source object storage and backup
proxies.

If you change the cache repository for an existing object storage whose backups are stored in another
object storage, Veeam Backup & Replication will prompt you to either attach migrated metadata, copy
metadata from the previous cache repository, or download metadata manually from the archive
repository. For more information, see the Unstructured Data Backups in Object Storage Repositories
section.

4. Use the Ba ckup I/O control slider to define how fast all proxies can read data from the source object
storage. This setting is based on the number of parallel threads that can be used by all the proxies
configured for processing the object storage. If resources of your object stora ge source are limited, it is
recommended that you select the Lower impact option. If your object storage source is powerful enough,
select the Fa ster backup option.

5. Click Ap p ly to save the configured settings.

1576 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Apply Object Storage Settings

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the object storage to the inventory of the virtual infrastructure. Click Nex t to proceed.

1577 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the added object storage and click Finish to exit the
wizard.

Adding Amazon S3 Object Storage


Before you add an Amazon S3 object storage to the inventory of the virtual infrastructure, consider the
following:

• The object storage meets requirements and limitations listed in the Platform Support section.

• If you plan to use dedicated proxy servers, make sure these components are added in the Backup
Infrastructure.

1578 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Wizard

To launch the New Object Storage wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the Unstructured Data node and select Ad d unstructured data
source.

o Select the Unstructured Data node and click Ad d Data Source on the ribbon.

o Select the Unstructured Data node and click Ad d Data Source in the working area.

o If at least one object storage is added as the unstructured data source, open the Ob ject Storage node,
right-click empty-space in the working area and click Ad d object storage. Alternatively, you can right-
click the Ob ject Storage node, and click Ad d object storage.

3. In the Ad d Unstructured Data Source window, select Ob ject storage > Ama zon S3.

1579 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Account Settings

At the Account step of the wizard, specify a friendly name and connection settings of your object storage:

1. In the Friendly name field, specify a name you want to assign to your object storage. This name will
display in the list of you object storage repositories in the inventory of the virtual infrastructure.

2. From the Credentials drop-down list, select user credentials to access your Amazon S3 object storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

3. From the AW S region drop-down list, select the AWS region where the Amazon S3 bucket is located.

4. From the Da ta center region drop-down list, select a region.

1580 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Processing Settings

At the P rocessing step of the wizard, do the following:

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

2. In the Ba ckup Proxy window, select proxy servers:

o If you select All p roxies, Veeam Backup & Replication will use all available backup proxies for the
object storage backup. The number of proxies in use defines the number of data threads that transfer
data from the object storage to the backup repository. The more data transfer threads
Veeam Backup & Replication uses, the higher is the data transfer speed.

If the object storage is used as a source for an object to tape backup job, the tape server utilized for
this job is added as yet another backup proxy when creating an object to tape backup job. This backup
proxy has the highest priority over all others and is used by default if it has access rights to the object
storage. For details on object to tape backup jobs, see the Object Storage Backup to Tape section in
the Veeam Backup & Replication User Guide.

o If you select Use the selected backup proxies only, you can explicitly specify backup proxies that
Veeam Backup & Replication must use for the object storage backup.

It is recommended that you select at least two backup proxies to ensure that the backup jobs start
even if one of the proxies fails or loses its connectivity to the source object storage. The more proxies
you select, the more data transfer threads Veeam Backup & Replication will use for backup jobs, thus
improving performance.

Even if the object storage is used as a source for object to tape backup jobs,
Veeam Backup & Replication will use only proxies selected in the list to process the backup data
traffic.

1581 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located in the close proximity to the source object storage and backup
proxies.

If you change the cache repository for an existing object storage whose backups are stored in another
object storage, Veeam Backup & Replication will prompt you to either attach migrated metadata, copy
metadata from the previous cache repository, or download metadata manually from the archive
repository. For more information, see the Unstructured Data Backups in Object Storage Repositories
section.

4. Use the Ba ckup I/O control slider to define how fast all proxies can read data from the source object
storage. This setting is based on the number of parallel threads that can be used by all the proxies
configured for processing the object storage. If resources of your object storage source are limited, it is
recommended that you select the Lower impact option. If your object storage source is powerful enough,
select the Fa ster backup option.

5. Click Ap p ly to save the configured settings.

1582 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Apply Object Storage Settings

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the object storage to the inventory of the virtual infrastructure. Click Nex t to proceed.

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the object storage to the backup infrastructure. Click Nex t to proceed.

1583 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the added object storage and click Finish to exit the
wizard.

Adding Microsoft Azure Blob Storage


Before you add a Microsoft Azure Blob storage to the inventory of the virtual infrastructure, consider the
following:

• The object storage meets requirements and limitations listed in the Platform Support section.

• If you plan to use dedicated proxy servers, make sure these components are added in the Backup
Infrastructure.

1584 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Wizard

To launch the New Object Storage wizard:

1. Open the Inventory view.

2. Do one of the following:

o In the inventory pane, right-click the Unstructured Data node and select Ad d unstructured data
source.

o Select the Unstructured Data node and click Ad d Data Source on the ribbon.

o Select the Unstructured Data node and click Ad d Data Source in the working area.

o If at least one object storage is added as the unstructured data source, open the Ob ject Storage node,
right-click empty-space in the working area and click Ad d object storage. Alternatively, you can right-
click the Ob ject Storage node, and click Ad d object storage.

3. In the Ad d Unstructured Data Source window, select Ob ject storage > Microsoft Azure Blob Storage.

1585 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Account Settings

At the Account step of the wizard, specify a friendly name and connection settings of your object storage:

1. In the Friendly name field, specify a name you want to assign to your object storage. This name will
display in the list of you object storage repositories in the inventory of the virtual infrastructure.

2. From the Credentials drop-down list, select user credentials to access your Microsoft Azure Blob storage.

If you already have a credentials record that was configured in advance, select such a record from the
drop-down list. Otherwise, click Ad d and provide your access and secret keys, as described in section
Cloud Credentials Manager. You can also click the Ma nage cloud accounts link to add, edit or remove a
credentials record.

3. From the Reg ion drop-down list, select an Azure region.

1586 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Object Storage Processing Settings

At the P rocessing step of the wizard, do the following:

1. Click Choose next to the Ba ckup proxy field to select a backup proxy.

2. In the Ba ckup Proxy window, select proxy servers:

o If you select All p roxies, Veeam Backup & Replication will use all available backup proxies for the
object storage backup. The number of proxies in use defines the number of data threads that transfer
data from the object storage to the backup repository. The more data transfer threads
Veeam Backup & Replication uses, the higher is the data transfer speed.

If the object storage is used as a source for an object to tape backup job, the tape server utilized for
this job is added as yet another backup proxy when creating an object to tape backup job. This backup
proxy has the highest priority over all others and is used by default if it has access rights to t he object
storage. For details on object to tape backup jobs, see the Object Storage Backup to Tape section in
the Veeam Backup & Replication User Guide.

o If you select Use the selected backup proxies only, you can explicitly specify backup proxies that
Veeam Backup & Replication must use for the object storage backup.

It is recommended that you select at least two backup proxies to ensure that the backup jobs start
even if one of the proxies fails or loses its connectivity to the source object storage. The more proxies
you select, the more data transfer threads Veeam Backup & Replication will use for backup jobs, thus
improving performance.

Even if the object storage is used as a source for object to tape backup jobs,
Veeam Backup & Replication will use only proxies selected in the list to process the backup data
traffic.

1587 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. From the Ca che repository drop-down list, select a cache repository where temporary cache files must be
stored. This repository must be located in the close proximity to the source object storage and backup
proxies.

If you change the cache repository for an existing object storage whose backups are stored in another
object storage, Veeam Backup & Replication will prompt you to either attach migrated metadata, copy
metadata from the previous cache repository, or download metadata manually from the archive
repository. For more information, see the Unstructured Data Backups in Object Storage Repositories
section.

4. Use the Ba ckup I/O control slider to define how fast all proxies can read data from the source object
storage. This setting is based on the number of parallel threads that can be used by all the proxies
configured for processing the object storage. If resources of your object storage source are limited, it is
recommended that you select the Lower impact option. If your object storage source is powerful enough,
select the Fa ster backup option.

5. Click Ap p ly to save the configured settings.

1588 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Apply Object Storage Settings

At the Ap p ly step of the wizard, wait till Veeam Backup & Replication installs and configures all required
components and adds the object storage to the inventory of the virtual infrastructure. Click Nex t to proceed.

1589 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review details of the added object storage and click Finish to exit the
wizard.

1590 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Unstructured Data Backup Works
Veeam Backup & Replication performs backup of unstructured data to the backup storage in the following way:

1. When a new backup job session starts, Veeam Backup & Replication assigns a backup proxy to process the
unstructured data.

2. The backup proxy enumerates files and folders on the file share or object storage repository and creates a
cyclic redundancy check (CRC) tree.

3. The backup proxy transfers the CRC tree to the cache repository.

4. The cache repository saves the CRC tree.

When the cache repository receives a new CRC tree structure from the proxy, it compares it with the CRC
tree created during the previous run of the backup session. If any source files or folders have changed
since the previous backup session run, the cache repository instructs the backup proxy to start reading
changed data from the source file share or object storage repository.

5. The backup proxy reads new data from the source file share or object storage repository.

6. The backup proxy creates data packages and transfers them to the target backup repository.

Data packages comprise backup data files (each 64 MB in size) and metadata files that contain names and
versions of backup files and allocation of data in backup files.

7. Veeam Backup & Replication checks file versions in the backup repository against retention settings and
moves backup data from the backup repository to the archive repository if necessary.

1591 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Structure in Backup, Archive and Secondary
Repositories
Backup, archive and secondary repositories store file and object storage backups as objects in VBLOB files (up to
64 MB each) of unstructured data. They also store metadata about the original objects on unstructured data
sources and their structure.

When you run the file backup job or object storage backup for the first time, Veeam Backup & Replication
creates a full backup for objects on the data source. During subsequent backup job sessions,
Veeam Backup & Replication copies only objects that have changed since the last backup job session.

Although the file backup job or object storage backup job first creates a full backup and afterwards incremental
backups, Veeam Backup & Replication does not create a separate file for each backup job run as it does during
VM backup. Instead of this, it consistently creates multiple VBLOB files accompanied by metadata files that
track all the changes on the unstructured data source.

Veeam Backup & Replication uses the following structure for storing the file backup data and object storage
backup data in the backup repository:

Fold er/File Description

Ba cku Folder in the repository that


p is dedicated to store
backups.

1592 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Fold er/File Description

< unstructur Folder that contains all data


ed _ backed up by a specific file
d a ta_backup backup job or object storage
_ backup job. Data for each
job > job will be placed to its own
directory.

< unstructure XML metadata file that


d_ describes the entire backup
d a ta_backup_ file for a specific file backup
job >.vstore job or object storage backup
job.

< unstructure Copy of the XML metadata


d_ file that describes the entire
d a ta_backup_ backup file for a specific file
job>.vstoreco backup job or object storage
py backup job.

< g uid_x> Folder that contains all data


for a single source. Data for
each source will be placed
to its own directory.

< g uid_x>.vsource XML metadata file that


describes the single source
object.

< g uid_x>.vsourcec Copy of the XML metadata


op y file that describes the single
source object.

1593 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Fold er/File Description

meta Folder with binary metadata


files that describe the
content of the backup.

If backup files are stored on


an object storage
repository, this folder is
missing from the repository
itself and is instead stored
on the cache repository
specified for the selected
backup repository.

If backup files are stored on


a scale-out backup
repository, this folder on
each performance extent
contains metadata for data
stored on the same extent
of the scale-out backup
repository. For more
information, see
Unstructured Data Backups
in Scale-Out Repositories.

If the repository where you


store backups is immutable,
this folder and files in it do
not have the immutability
lock and may be updated at
every backup job run.

.vindex Binary metadata that


describes backup files
(names and versions).

.vslice Binary metadata that


describes allocation of data
in VBLOB backup files.

1594 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Fold er/File Description

metabackup Folder with a replica of


binary metadata files.

If backup files are stored on


a scale-out backup
repository, this folder on
each performance extent
contains replica of metadata
stored on other extents of
the scale-out backup
repository. For more
information, see
Unstructured Data Backups
in Scale-Out Repositories.

metalock Folder with XML data files


that describe immutable
metadata replica.

This folder exists only for


backups in immutable
repositories.

.vsourc XML metadata file that


e describes a single
immutable metadata
replica.

d a ta Folder with binary data.

<guid_y 1 GB basket that stores


> VBLOB backup files.

1595 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Fold er/File Description

.vblo By default, a classic 64 MB


b file that stores data from
the file share backup or
object storage backup.

If necessary, you can


convert NAS backup data
files into the single file
basket format
recommended for storing
data on HPE StoreOnce
storage appliances. For
more information, see
description of the
Convert-
VBRNASBackupStorageFo
rmat cmdlet in the Veeam
PowerShell Reference.

1596 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Backup Retention Scenarios
There can be a number of backup retention scenarios depending on the configuration of backup and archive
repositories. Below you can find example cases that illustrate file and object storage backup retention with
different settings.

Ca se 1

Only 1 file version is created. The file does not change.

File version 1 always remains in the backup repository and is not moved to the archive repository even if this
behavior is enabled and configured in the retention policy settings.

Ca se 2

Retention for the backup repository is set to 5 days. No archive repository is configured. The file changes once a
day. The backup is performed once a day.

On day 6, file version 6 is added to the backup repository, file version 1 is deleted by retention.

Ca se 3

Retention for the backup repository is set to 3 days. The file changes every hour. The backup is performed 2
times a day.

On day 4, versions 7 and 8 are added to the backup repository, file versions 1 and 2 added to the backup
repository on day 1 are deleted by retention.

Ca se 4

Retention for the backup repository is set to 3 days. The file changes once a day.

1597 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
On day 3, the source file is deleted from the source share, the backup repository considers file version created
on this day as deleted.

On day 4, the backup repository still detects the file as deleted, file version 1 is deleted from the backup
repository by retention.

On day 5, the backup repository still detects the file as deleted, file version 2 is deleted from the backup
repository by retention.

Thus, no file versions are stored in the backup repository for this file any longer.

Ca se 5

Retention for the backup repository is set to 5 days. The archive repository is enabled with default settings. The
file changes every day. The backup is performed once a day.

1598 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
On day 6, file version 6 is added to the backup repository, file version 1 is moved to the archive repository by
retention.

Ca se 6

Retention for the backup repository is set to 3 days. The archive repository is enabled with DOCX files to be
excluded from archiving. The files change once a day. The backup is performed once a day.

On day 4, file versions created on day 1 are removed from the backup repository. File version 1 for DOCX file is
deleted, file version 1 for XLSX file (non-DOCX) is moved to the archive repository.

Ca se 7

Retention for the backup repository is set to 4 days. The archive repository is enabled and configured to keep 3
versions of active files and 2 versions of deleted files.

1599 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
On day 8, file version 8 is added to the backup repository, file version 4 is moved from the backup repository to
the archive repository to keep file versions for 4 days, file version 1 is deleted from the archive repository to
keep 3 file versions of the active file (versions 2, 3, 4).

On day 9, the file is removed from the source, file version 9 (denoting the missing file) is added to the backup
repository, file version 5 is moved from the backup repository to the archive repository, file versions 2 and 3 are
deleted from the archive repository to keep 2 file versions of the deleted file (versions 4 and 5).

On day 10 and 11, file versions 6 and 7 are successively moved from the backup repository to the archive
repository. File versions 4 and 5 are deleted from the archive repository.

1600 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
On day 12, file version 8 (the last file version) is moved from the backup repository to the archive repository, file
version 6 is deleted from the archive repository. After that, versions 7 and 8 are stored in the archive repository
further on.

Ca se 8

Retention for the backup repository which is a hardened repository is set to 30 days, the immutability for it is
set to 14 days. The file changes once a day.

On day 3, the source file is deleted from the source share, the backup repository considers the file version
created on this day as deleted.

According to retention settings, Veeam Backup & Replication will keep all file versions for 30 days. After that, it
will start marking them for deletion. On day 31, file version 1 is marked for deletion from the backup repository
by retention, but as the repository is immutable it will still keep this file version.

1601 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
On day 32, file version 2 is marked for deletion from the backup repository by retention, but as the repository is
immutable it will keep this file version as well.

On day 45, when the immutability lock is released after 14 days (14 days of immutability configured for the
repository), file version 1 is deleted from the backup repository. File version 2 is marked for deletion, but is still
immutable.

Finally, on day 46, the immutability lock is released for file version 2 and it is deleted from the backup
repository.

Thus, no file versions are stored in the backup repository for this file any longer.

Ca se 9

Retention for the backup repository which is an immutable object storage is set to 30 days, the immutability for
it is set to 14 days, 10 days of immutability are added automatically as a Block Generation period described in
the File Backups in Immutable Repositories section. The file changes once a day.

On day 3, the source file is deleted from the source share, the backup repository considers file version created
on this day as deleted.

1602 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
According to retention settings, Veeam Backup & Replication will keep all file versions for 30 days. After that, it
will start marking them for deletion. On day 31, file version 1 is marked for deletion from the backup repository
by retention, but as the repository is immutable it will still keep this file version.

On day 32, file version 2 is marked for deletion from the backup repository by retention, b ut as the repository is
immutable it will keep this file version as well.

On day 55, when the immutability lock is released after 24 days (14 days of the immutability period configured
for the repository plus 10 days of the Block Generation period), file version 1 is deleted from the backup
repository. File version 2 is marked for deletion, but is still immutable.

Finally, on day 56, the immutability lock is released for file version 2 and it is deleted from the backup
repository.

Thus, no file versions are stored in the backup repository for this file any longer.

1603 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Backups in Object Storage
Repositories
How Unstructured Data Backup to Object Storage Repository
Works
You can select an object storage repository added in your backup infra structure as a backup repository for
storing unstructured data backups.

For unstructured data backups stored on non-object storage repositories, Veeam Backup & Replication stores
active metadata, metadata copy, and the data itself all next to each other on the repository, as described in the
Data Structure in Backup, Archive and Secondary Repositories section.

The main peculiarity of storing unstructured data backups in an object storage repository is keeping active
metadata in the cache repository. This metadata is actively used during backup, restore, merge, transform, or
health check operations. All the changes of the active metadata is then replicated to the metadata replica that is
stored on the repository next to the data.

The metadata replica is self-sufficient: if anything happens to the source unstructured data and the cache
repository, you still will be able to restore data from the backup stored in the object storage repository.

Types of Connection to Object Storage Repository


Depending on your infrastructure and the activity type, the source general-purpose backup proxy can connect to
the object repository through one of the connection types:

• Direct. In this mode, the general-purpose backup proxy writes directly to the object storage. This
connection type is used, for example, for backup and restore sessions when your target object storage
repository is located in your local infrastructure.

1604 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Through gateway servers. In this mode, the backup server automatically selects the most suitable gateway
server from the preconfigured list. This connection type is used, for example, for backup copy sessions
when the source backup is stored on an SMB or NFS share, or if the target object storage repository is a
cloud repository.

The connection type is configured at the Account step of the New Object Storage Repository wizard.

Helper Appliance in Unstructured Data Backup


Unstructured data is forever forward incremental and it does not create periodic full backups. To avoid
constantly downloading data to and uploading data from the cloud object storage for performing transform and
health check operations, you can configure a helper appliance. To learn how to configure the helper appliance,
see the Mount Server step in Adding S3 Compatible Object Storage, Adding Amazon S3 Storage, Adding Google
Cloud Object Storage, Adding IBM Cloud Object Storage, Adding Azure Blob Storage, Adding Wasabi Cloud
Object Storage.

1605 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Changing Cache Repository
If your unstructured data source is protected with an unstructured data backup job that backs up data to an
object storage and you decide to change the cache repository for this data source, Veeam Backup & Replication
will prompt you to:

• Atta ch manually migrated data. You can manually copy metadata from the old cache repository to a new
one. After that, when changing the cache repository for the unstructured data source, click Atta ch in the
displayed window.

• Cop y metadata from the previous cache repository. If you click Cop y when changing the cache repository
for the unstructured data source, Veeam Backup & Replication will automatically copy all metadata from
the old cache repository to a new one.

• Download metadata from the archive repository. If the old cache repository is not available, you can click
Download when changing the cache repository for the unstructured data source to automatically
download all metadata to a new cache repository.

1606 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Backups in Immutable
Repositories
All the data stored in immutable repositories cannot be changed or deleted until the immutability period expires
and the immutability lock for the data is released. The only exception is active metadata for backups stored in
immutable hardened repositories and immutable deduplicating storage appliances (HPE StoreOnce and Dell
Data Domain).

For more information on the structure of unstructured backup data in backup repositories, see the Data
Structure in Backup, Archive and Secondary Repositories section.

How Immutability for Unstructured Backup Works


Immutability settings configured for a repository where you store unstructured data backups are applied to the
whole backup of the unstructured data source, that is to all backup files protecting this source. Thus, the
immutability configured for the repository starts its countdown for the backup files when
Veeam Backup & Replication marks some old file versions and their data blocks for deletion according to the
retention settings configured in the backup job. Files and data blocks are deleted from the backup repository
when the immutability lock is released for them.

TIP

You can quickly roll back an unstructured data backup stored on an immutable backup repository to a point
in time state by using the Sync-VBRNASBackupState PowerShell cmdlet.

Unstructured Data Backups in Hardened Repositories and Immutable Deduplicating


Storage Appliances
The period of the immutability lock for unstructured data backups in hardened repositories and immutable
deduplicating storage appliances (HPE StoreOnce and Dell Data Domain) is defined by the immutability settings
of those backup repositories.

For an example of how this mechanism works, see Ca se 8 in the Unstructured Data Backup Retention Scenarios
section. For more information on hardened repositories and on how to configure them, see the Hardened
Repository section. For more information on how to configure immutability for HPE StoreOnce, see the HPE
StoreOnce section, for Dell Data Domain — the Dell Data Domain section.

File Backups in Immutable Object Storage Repositories


For general information on the immutability feature for object storage repositories in
Veeam Backup & Replication and on how to configure it, see the Immutability for Object Storage Repositories
section.

Apart from the immutability period set for each object storage repository, Veeam Backup & Replication
automatically adds up to 10 days to the immutability expiration date to reduce I/O operations and associated
costs. This period is called Block Generation. You do not have to configure it, the Block Generation setting is
applied automatically. For example, if you set your immutability period to 14 days for your object storage
repository, Veeam Backup & Replication adds 10 days to specific objects to reduce I/O operations with the data
blocks over time. Thus, you will have immutability set to 14 days plus 10 days of Block Generation set for data
blocks in your object storage repositories, so the actual immutability period will equal to 24 days.

For an example of how this mechanism works, see Ca se 9 in the Unstructured Data Backup Retention Scenarios
section. For more information, see the Block Generation section for object storage repositories.

1607 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

We strongly recommend the following configuration for storing unstructured data backups in immutable
object storage repositories:

• Set the retention period for the immutable object storage repository up to 14 days.
• Configure file backup jobs or object storage backup jobs that use the immutable object storage
repository to run not more than once per day.

Otherwise, the unstructured data backup may consume too much storage space.

These settings are critical for cloud object storage repositories where the cost of the disk space consumed
for storing file versions may be very high.

Metadata of Unstructured Data Backups in Immutable Storage


Repositories
When creating unstructured data backups in the backup repository, Veeam Backup & Replication creates two
sets of metadata: active metadata and the metadata replica. Metadata replica is always stored in the backup
repository next to the data. As for the active metadata, it can be stored on different infrastructure components
depending on the type of the backup repository used to store backups:

• If you store your backups in a ha rdened repository or d eduplicating storage appliance (HPE StoreOnce or
Dell Data Domain), the active metadata is stored on the immutable repository alongside with the locked
metadata replica and locked backup data.

• If you store your backups in an ob ject storage repository, the active metadata is stored on the cache
repository.

Data in immutable repositories is temporarily locked and cannot be changed or removed till the immutability
period ends. The metadata replica that is stored next to the data is also immutable and cannot be changed. But
the active metadata does not have the immutability lock. So it changes actively during every backup session and
keeps the up-to-date state of the unstructured data backup. Thus, it can be used by
Veeam Backup & Replication to track changes in the unstructured data backup.

Once in 30 days (if the job runs once a day or once in several days) or as the metadata replica chain reaches 30
generations (if the job runs several times a day), Veeam Backup & Replication uses metadata replica files created
during this period to generate a new locked metadata flat file.

After the immutability period for the metadata replica files, which were already transformed into the metadata
flat file, ends, Veeam Backup & Replication removes them from the object storage repository.

The schemas below show examples of creating a locked metadata flat file for a job that runs once every day.
After 30 generations of metadata replica files are created (that is after 30 days), Veeam Backup & Replication
uses them to generate a new metadata flat file. The older metadata replica files that comprised it are marked for
deletion and can be deleted based on the retention and immutability settings of the repository.

1608 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Metadata in Hardened Repositories and Immutable Deduplicating Storage Appliances
If unstructured data backups are stored in an immutable hardened repository or deduplicating storage appliance
(HPE StoreOnce or Dell Data Domain), the active metadata is stored on the immutable repository alongside with
the locked metadata replica and locked backup data.

1609 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Metadata in Immutable Object Storage Repositories
If unstructured data backups are stored in an immutable object storage such as Amazon S3, Microsoft Azure
Storage, IBM Cloud Object Storage, Wasabi Cloud Object Storage, or S3-compatible object storage, the active
metadata is stored on the cache repository.

1610 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Backups in Scale-Out
Repositories
If you use a scale-out backup repository as a backup repository for storing unstructured data ba ckups, by default
Veeam Backup & Replication evenly distributes backup data among all the performance extents added to this
repository. The backup data is accompanied by the metadata files. To provide an opportunity to restore data
written to extents remaining available in case one or two of other extents are unavailable,
Veeam Backup & Replication triplicates metadata when writing it to extents. Thus, every extent keeps metadata
for data stored on this extent (in folder meta) and replica of metadata for data stored on adjacent extents (in
folder metabackup). Even if two of three adjacent extents are lost, you can restore backup data stored on the
third extent.

NOTE

Consider the following when storing unstructured data backups on a scale-out backup repository:

• The metadata redundancy approach protects against two extents out of three being completely lost.
• The metadata redundancy approach allows protecting metadata, not data.
• The backup file placement policy set for the scale-out backup repository, as described in section
Backup File Placement, is ignored.

1611 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Scale-Out Repository with Extents in Metadata
and Data Roles
When you use a standalone repository for storing unstructured data backups, it stores both data and metadata.
But when you plan to use a scale-out repository, you can configure its performance extents to act as data
extents or as metadata extents. Thus, you can store metadata separate from the backup data.

NOTE

We strongly recommend differentiating metadata and data roles for extents, when you plan to create a
scale-out backup repository that will consist of a fast SSD storage and slow deduplicating storage
appliances (Dell Data Domain, ExaGrid, HPE StoreOnce, Quantum DXi). In this case, you can set the
metadata role to the SSD storage and the data role to deduplicating storage appliances.

Most often, when performing restore, merge, transform operations, Veeam Backup & Replication interacts with
metadata rather than with the backup data. Obviously, processing metadata stored on the SSD is faster and
more efficient than accessing large data arrays stored on a slow storage.

IMP ORTANT

Consider the following when assigning roles to extents in a scale-out backup repository:

• An extent with the metadata role can be used for storing metadata for unstructured data backup
jobs only. However, extents with the data role can be used by any job.
• Make sure that you assign both roles to extents in a scale-out repository. If an extent with one of
the roles is missing, Veeam Backup & Replication cannot store backups on this scale-out repository.
NOTE

If the data role is assigned to an extent, Veeam Backup & Replication will also copy replica of metadata to
this extent to provide the metadata redundancy. While the original metadata is available,
Veeam Backup & Replication does not use the replica of metadata on data extents. If by some reason
metadata stored on metadata extents is corrupted or lost, to restore it Veeam Backup & Replication will
use the replica of metadata stored on data extents.

To assign the metadata or data role to extents in a scale-out backup repository, use the Set-
VBRRepositoryExtent cmdlet, as described in the Veeam PowerShell Reference. If previously the role was
not assigned to the extents for unstructured data backup or you changed the assigned role, during the next run
of the file backup job or object storage backup job that writes backups to this scale -out repository,
Veeam Backup & Replication will move metadata to the metadata extent, data — to the data extents.

For example, if you already have an existing backup and want to move its metadata to a specific extent that will
operate as a metadata only extent, do the following:

1. Make sure that your license allows using a scale-out backup repository with object storage support. For
more information, see Viewing License Information and Veeam Backup & Replication Feature Comparison.

2. Create a scale-out backup repository with the following extents: one extent that currently stores the
backup (its data and metadata), another extent that will store metadata of the backup. Usually, it is a fast
storage, for example, SSD-based. Let us assume that these extents are named “Backup Repository 1” and
"NAS Backup Repository on SSD".

3. Run the Set-VBRRepositoryExtent cmdlet to assign the data role to the “Backup Repository 1” extent
and the metadata role to the "File Backup Repository on SSD" extent.

1612 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Set-VBRRepositoryExtent –Extent “File Backup Repository on SSD” -Metadata
Set-VBRRepositoryExtent –Extent “Backup Repository 1” –Data

For more information, see the Veeam PowerShell Reference.

4. Run the file backup job and make sure that the metadata of the backup was moved to the metadata
extent: the backup job session displays a line notifying of that.

To view the roles of the extents in a scale-out backup repository, do either of the following:

• Check the role of each extent (the Role column) in the list of extents under the certain scale-out
repository in the Ba ckup Infrastructure view.

• Run the Get-VBRRepositoryExtent cmdlet, as described in the Veeam PowerShell Reference.

1613 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
File Backup Integration with Storage Systems
There are two approaches in backing up file shares residing on enterprise NAS storage systems .

Integration with Storage System as NFS or SMB File Share


Server
You can add the storage system as a root folder of the server where NFS or SMB file shares reside. The
procedure of configuring the file share protection in this case will consist of the following steps:

1. Add the storage system as an NFS file share to the inventory, as described in section Adding NFS File
Share, or as an SMB fie share, as described in section Adding SMB File Share. As a file share path, specify
the root server folder.

When adding the storage system in this way, you cannot configure what containers, volumes or file shares
will be available for further protection. Therefore, to configure them, you must carefully configure
inclusion/exclusion settings when creating a file backup job.

Consider that servers accessed by NFS (with file shares and folders within them) and servers accessed by
SMB (with file shares and folders within them) are added to the inventory separately . For example, if the
storage system IP address is 173.25.136.64, add an NFS share for this server by specifying its root folder as
173.25.136.64:/, and add an SMB share for this server by specifying its root folder as
\\173.25.136.64.

NOTE

If you add a root server folder as a source for protection, hidden and admin file shares are skipped
from processing by default. You can enable their processing with registry values. For more
information, contact Veeam Customer Support.

2. Create a file backup job, as described in section Creating File Backup Jobs. As a source to protect, you can
select the following entities:

o whole server

o file share residing on the server

o separate folders within the share

To protect all file shares residing on one server, you must add to the file backup job both NFS and SMB
shares previously added to the inventory.

3. Configure what files and folders must be included in or excluded from processing b y the file backup job.
For more information on how to include/exclude files and folders from processing, see Select Files and
Folders to Back Up.

Integration with Storage System as NAS Filer


You can add the storage system as a NAS filer. This option is preferable if you want to leverage the backup from
storage snapshots technology. For more information, see the NAS File Share Backup from Storage Snapshots
section in the Storage System Snapshot Integration Guide.

1614 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

If you used to protect NFS and SMB file shares residing on the enterprise storage system and added as file
shares in inventory, and now you want to protect them using benefits of NAS filer, you can convert backups
created for existing SMB or NFS shares into the format of NAS filer shares. For more information, see
Converting Backups from SMB or NFS Shares to NAS Filer Shares.

The procedure of configuring the file share protection in this case will consist of the following steps:

1. Depending on the type of the NAS system you use, add the storage system to the backup infrastructure,
as described in the Adding NetApp Data ONTAP, Adding Lenovo ThinkSystem DM Series, Adding Dell
PowerScale, or Adding Nutanix Files Storage sections in the Storage System Snapshot Integration Guide.

Depending on storage settings, the IP address for accessing the storage system can differ from one used
for accessing it as a server where file shares reside. You can also use the DNS name of the server.

When adding the storage system, make sure that you do not forget to perform the following steps:

a. Enable the NAS filer role for the added storage system.

b. Specify what protocols the storage should use as a NAS filer: NFS or SMB. Only file shares using the
selected protocols will be displayed when you add the storage as a NAS filer and thus available for
protection.

c. Select storage volumes to analyze for the presence of newly added file shares. You can either
configure Veeam Backup & Replication to analyze all storage volumes, or exclude some volumes from
processing, or specify only certain volumes that will be processed. Only file shares on the selected
storage volumes will be displayed when you add the storage as a NAS filer and thus available for
protection.

At this step, you must carefully consider what file shares on what volumes must be protected and through
what protocols. Limiting the number of volumes reduces the storage load.

NOTE

Hidden and admin file shares on storage systems added as NAS filers are skipped from processing by
default. You can enable their processing with a registry value. For more information, contact Veeam
Customer Support.

2. Add the configured storage system as a NAS filer to the inventory, as described in section Adding
Enterprise NAS System Share.

3. Create a file backup job, as described in section Creating File Backup Jobs. As a source to protect, you can
select the following entities:

o whole storage

o container (for Dell PowerScale — access zone, for NetApp Data ONTAP — SVM, for Nutanix Files
Storage — not applied)

o volume

o file share

You cannot specify separate folders within file shares. Therefore, to configure files and folders to be
protected, you must properly configure inclusion/exclusion settings.

4. Configure what files and folders must be included in or excluded from processing by the file backup job.
For more information on how to include/exclude files and folders from processing, see Select Files and
Folders to Back Up.

1615 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Backup Jobs for Protecting
Unstructured Data
Depending on the source of the unstructured data, use one of the following backup job types to protect it:

• File backup jobs

• Object storage backup jobs

1616 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating File Backup Jobs
To protect files and folders on the file share, configure a file backup job. The backup job defines how, where and
when to back up data from the file share. One job can be used to protect one or more file shares. Jobs can be
started manually or scheduled to run automatically at a specific time.

File backup jobs are used to protect the following sources of unstructured data:

• File servers (Windows and Linux)

• File shares (NFS and SMB (CIFS)

• Enterprise storage systems added as NAS filers

Before you create a file backup job, check prerequisites.

Before You Begin


Before you create a file backup job, check the following prerequisites:

• Backup infrastructure components that will take part in the file backup process must be added to the
backup infrastructure and properly configured. These include source file shares to back up, backup
proxies, and all repositories, including cache, backup and archive repositories. For more information, see
the Backup Infrastructure for Unstructured Data Backup section.

• The target backup repository must have enough free space to store created backup files. If you want to
receive notifications on the repository running low on free space, configure global notification settings as
described in the Specifying Other Notification Settings section.

• Make sure that repositories intended to store file share backups are not configured to store files in the
WORM status. Otherwise, the backup jobs will fail when Veeam Backup & Replication cannot update the
backup metadata files.

• If you plan to map a file backup job to a backup that already exists in the backup repository, you must
perform the rescan operation for this backup repository. Otherwise, Veeam Backup & Replication will not
be able to recognize backup files in the backup repository.

For more information on how to rescan backup repositories, see the Rescanning Backup Repositories
section.

• If you plan to use pre-job and post-job scripts, you must create scripts before you configure the file
backup job.

• Antivirus software may significantly slow down file backup jobs. To improve performance, we recommend
you exclude the c:\Program Files (x86)\Veeam\Backup Transport\x64\VeeamAgent.exe process from the
antivirus scan on machines running the file backup proxy and backup repository roles. Keep in mind that it
can weaken the security of these machines.

1617 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New File Backup Job Wizard
To launch the New File Backup Job wizard, do one of the following:

• On the Home tab, click Ba ckup Job > File Share.

• Open the Home view. Right-click in the working area, and select Ba ckup > File share.

• Open the Home view. In the inventory pane, right-click the Job s node and select Ba ckup > File share.

• You can quickly add the file share to an already existing job. Open the Inventory view. Under the
Unstructured Data (File Shares – for version 12) node in the inventory pane, select File Shares. In the
working area, right-click the file share you want to back up and select Ad d to backup job > name of the
job .

1618 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Na me step of the wizard, specify a name and description for the file backup job.

1. In the Na me field, enter a name for the file backup job.

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

3. Select the Hig h priority check box if you want the resource scheduler of Veeam Backup & Replication to
prioritize this job higher than other similar jobs and to allocate resources to it in the first place. For more
information on job priorities, see the Job Priorities section.

TIP

In the UI, jobs with the Hig h priority option enabled will be marked with a special flag ( ).

1619 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Files and Folders to Back Up
At the Ob jects step of the wizard, select files and folders that you want to back up.

1. Click Ad d .

2. From the Server list, select a file share on which the necessary files or folders reside.

NOTE

If you plan to protect file shares residing on the enterprise storage system, you can choose between
two different approaches. For more information, see the File Backup Integration with Storage
Systems section.

3. In the Ob jects tree, select folders you want to back up.

NOTE

If you select a NAS filer from the Server list, but the Ob jects tree is empty, make sure that the
storage system rescan was performed and finished. For more information about the storage system
rescan process, see the Storage Discovery Process section in the Storage System Snapshot
Integration Guide.

To select multiple folders, hold [Ctrl] and click necessary folders. Although different folders of the same
share form separate records in the table, they will be processed by one job task.

Consider the following:

o Hard links in file shares are protected with content included.

o Symbolic links in file shares are protected as links, without the content they refer to.

1620 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you add a folder to the job, all the folder contents will be processed.

If necessary, you can choose only specific files from the added folder.

Including Objects
To filter objects that you want to back up, you can specify the object name or extension mask to include into
processing.

1. Select an object in the Ob jects list and click Filters.

2. In the Include and exclude masks window, use the Include masks section to include objects.

3. Click Ad d

4. In the Files by mask window, specify the value associated with the object. For example:

▪ To backup only PDF files, enter *.PDF in the E x tension field and click OK.

▪ To backup all files with name sa les_report.xlsx, enter sales_report.xlsx in the E x tension
field and click OK.

1621 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Click OK.

Excluding Objects
NOTE

\.snapshot and \~snapshot are added to exclude masks by default.

To filter objects that you do not want to back up, you can specify the path or file mask to exclude from
processing.

1. Select an object in the Ob jects list and click Filters.

2. In the Include and exclude masks window, use the E x clude masks field to exclude objects.

3. Click Ad d .

4. Depending on the way you want to exclude objects, select one of the following:

o To exclude objects by path, select Ob jects by path and in the Ob ject by path window, specify a path to
the objects that you want to exclude.

NOTE

Wildcards are not supported.

1622 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To exclude objects by file mask, click Files by mask and in the Files by mask window, specify the name
mask or exact file name that you want to exclude.

For example:

o To exclude PDF files from processing, select the Files by mask option, enter *.PDF in the E x tension
field and click OK.

o To exclude all files with name p ricelist.xlsx from processing, select the Files by mask option, enter
pricelist.xlsx in the E x tension field and click OK.

o To exclude folder 2016 from processing, select the Ob ject by path option, enter the full path to it in
the P a th field and click OK. For example, for an NFS file share this path looks like:
QA04:/NFS04/Documents/2016, for an SMB file share — \\fileserv05\Documents\2016).

Alternatively, you can specify a relative path to the folder or file to exclude. In case of the NAS filer,
this is the only option to specify a path to exclude. For example, to exclude folders ca ll_records
(where call records are located) from all file shares residing on the NAS filer, in the P a th field of the
Ob ject by path window, specify /call_records (this mask will exclude the ca ll_records folder from
processing for all NFS file shares on this NAS filer) and \call_records (this mask will exclude the
ca ll_records folder from processing for all SMB file shares on this NAS filer) and click OK.

You can exclude a whole file share from processing. For example, you add the \\Server\ SMB server
to the file backup job, but you want to exclude the \\Server\Sharing file share from processing.
To exclude this file share from processing, in the P a th field of the Ob ject by path window, enter the
\\Server\Sharing path and click OK. The job will back up all file shares that
Veeam Backup & Replication detects on this server, but will skip the excluded file share.

NOTE

Consider the following:

• Include and exclude masks are case sensitive.


• You cannot exclude a whole file share from processing if the storage system, where file shares
reside, is added to Veeam Backup & Replication as a NAS filer.
As a workaround, you can edit the storage in Storage Infrastructure and exclude the volumes on the
NAS Filer step, as described in the Adding NetApp Data ONTAP, Adding Lenovo ThinkSystem DM
Series, Adding Dell PowerScale, or Adding Nutanix Files Storage sections, depending on the type of
the storage system you use.
• You cannot use mask with * to specify folders to exclude from processing. For example, mask
QA04:/NFS04/Documents/201* will not work.
• You cannot mix different exclusion options, for example, you cannot use a mask to exclude files with
certain extensions from the specific folder. For example, QA04:/NFS04/Documents/2016/*.xlsx
will not work.

1623 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Exporting and Importing Filters
If necessary, you can export and import your masks :

• To export a mask to a file, click the E x port these filters link. In the E x port to file window, specify a path to
the necessary XML file. Click OK.

• To import existing masks from a file, click the Imp ort existing list link. In the Imp ort masks from file
window, specify a path to the necessary XML file. Click OK.

1624 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Backup Repository Settings
At the Ba ckup Repository step of the wizard, define the primary backup repository where the file backup job
must store backup files, and settings for moving files and folders to this repository. To learn what storage types
you can assign the role of the backup repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

NOTE

Consider that if you use the option of limiting the number of file versions to keep configured in File Version
Settings, Veeam Backup & Replication first applies those file-version retention settings and only after that
applies time-based retention settings specified at this step.

1. From the Ba ckup repository drop-down list, select a repository where backup files must be stored. When
you select a backup repository, Veeam Backup & Replication automatically checks the amount of free
space left. Make sure that you have enough free space to store backups.

2. You can map the job to a specific backup stored in the backup repository. Backup job mapping allows you
to move backup files to a new backup repository and to point the job to existing backups on this new
backup repository. You can also use backup job mapping if the configuration database got corrupted and
you need to reconfigure backup job settings.

To map the job to a backup, click the Ma p backup link. In the opened Select Backup window, select a
backup in the backup repository. Backups can be easily identified by job names. To find the backup, you
can also use the search field at the bottom of the window.

3. Use the Keep all file versions for the last field to specify how long copies of all recent file versions in the
selected file share must be kept in the backup repository. You can restore the entire file share to any
restore point within the period specified in this setting.

If, for example, Keep all file versions for the last is set to 30 days, the backup repository will store all file
versions that appeared at the file share during the last 30 days. At the scheduled time on the 31st day, the
file backup job first backs up new file versions and saves them to the backup repository. Right after that,
file versions older than 30 days (created on the 1st day) are either deleted from the backup repository or
moved to the archive repository. File versions are moved to the archive repository, if at the Archive
Repository step of the wizard you enable the Archive file versions to the following archive repository
check box and configure the archive retention.

1625 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you need to keep a copy of the backups in another repository, select the Configure secondary
d estinations for this job check box. That enables the Secondary Target step of the wizard.

1626 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Advanced Backup Settings
At the Ba ckup Repository step of the wizard, specify advanced settings for the file backup job:

• File version settings

• ACL handling settings

• Storage settings

• Maintenance settings

• Script settings

• Notification settings

TIP

After you specify necessary settings for the backup job, you can save them as default settings. To do this,
click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create a new
backup job, Veeam Backup & Replication will automatically apply the default settings to the new job.

File Version Settings


To configure how many file versions to keep for protected files, do the following:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the File Versions tab, specify to what file versions the settings should apply:

o Select Keep all file versions to keep all file versions for the time period specified in the main window
at the Storage step.

o Select Limit the number of archived file versions only to limit archived file versions to the numbers
specified below.

o Select Limit the number of both recent and archived file versions to limit recent and archived file
versions to the numbers specified below.

3. After you choose what file versions to keep, specify how many file versions to keep:

o Select Active file versions limit to keep the specified number of versions for files currently existing in
the source file share. Specify how many file versions to store.

o Select Deleted file versions limit to keep the specified number of versions for files deleted from the
source file share. Specify how many file versions to store.

1627 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

ACL Handling Settings


To specify how the backup job will process permissions and attributes:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the ACL Handling tab, specify how the backup job will process permissions and attributes:

o Select Fold er-level only (recommended) to back up permissions and attributes from folders only. The
restored files will inherit permissions from the target folder.

o Select Files and folders (slower) to back up permissions and attributes from both folders and
individual files. This option can significantly reduce the backup performance.

3. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

NOTE

Consider that Veeam Backup & Replication does not collect ACL handling settings of the source file share
root folder, so you cannot restore them. Before restoring an entire file share, you will have to specify
required ACL handling settings for the root folder of the target file share.

1628 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Storage Settings
To specify advanced storage settings for the file backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the Storage tab, specify data reduction and encryption settings:

o From the Compression level list, select a compression level for the backup: None, Dedupe-
friendly , Optimal, High or Extreme.

o To encrypt the content of backup files, select the E na ble backup file encryption check box. In the
P a ssword field, select a password that you want to use for encryption. If you have not created the
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For
more information, see the Password Manager section.

If the backup server is not connected to Veeam Backup Enterprise Manager and does not have the
Veeam Universal License or a legacy socket-based Enterprise or Enterprise Plus license installed, you
will not be able to restore data from encrypted backups in case you lose the password.
Veeam Backup & Replication will display a warning about it. For more information, see the Decrypting
Data Without Password section.

1629 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• If you enable encryption for an existing backup job, during the next job session
Veeam Backup & Replication will back up all the files of the file share to a new backup
file irrespective of whether they changed or not. The created backup files and
subsequent backup files will be encrypted with the specified password.
• If you enable encryption for an existing job, Veeam Backup & Replication does not
encrypt the previous backup chain created by this job.
• You can also use KMS keys for encryption. For more information, see the Key
Management System Keys section.

3. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Maintenance Settings
You can instruct Veeam Backup & Replication to periodically perform a health check for the backup. The health
check helps make sure that the backup is consistent, and you will be able to restore data from it.

During the health check, Veeam Backup & Replication performs a CRC check for metadata and a hash check for
data blocks in the file share backup files to verify their integrity. For more information, see the Performing
Health Check and Repair for Unstructured Data Backups section.

To configure the health-check settings for the backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the Ma intenance tab, select P erform backup files health check to enable the health check option. It
allows ensuring that all data and metadata is backed up correctly.

1630 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Click Configure and specify the time schedule for the health check.

4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Script Settings
You can configure custom scripts to run before or after the file backup job. For example, you can configure
scripts to take a VSS snapshot before running the job and to delete it after completing the job.

To specify script settings for the backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. Click the Scripts tab.

3. If you want to execute custom scripts, select the Run the following script before the job and Run the
following script after the job check boxes and click Browse to choose executable files from a local folder
on the backup server. The scripts are executed on the backup server.

You can select to execute pre- and post-backup actions after a number of backup sessions or on specific
week days.

o If you select the Run scripts every <N> backup session option, specify the number of the backup job
sessions after which the scripts must be executed.

o If you select the Run scripts on the selected days only option, click Da y s and specify week days on
which the scripts must be executed.

1631 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Notification Settings
To specify notification settings for the backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully.

SNMP traps will be sent if you specify global SNMP settings in Veea m Backup & Replication and configure
software on recipient's machine to receive SNMP traps. For more information, see Specifying SNMP
Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications about the job completion status by email. In the field below, specify recipient’s email
address. You can enter several addresses separated by a semicolon.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Configuring Global Email Notification Settings.

5. You can choose to use global notification settings or specify custom notification settings:

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for the job, select Use custom notification settings specified
b elow. You can specify the following notification settings:

1632 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %ObjectCount% (number of
file shares in the job) and %Issues% (number of files shares in the job that have finished with
the Warning or Failed status).

ii. Select the Notify on success, Notify on warning, and Notify on error check boxes to receive
email notification if the job completes successfully, completes with a warning or fails.

iii. Select the Sup press notifications until the last retry check box to receive a notification about the
final job status. If you do not enable this option, Veeam Backup & Replication will send one
notification per every job retry.

6. Specify severity options if required:

o Select the Ma k e file or folder processing issues result in a job warning to receive a warning at the end
of the job processing session if any issues with file or folder processing occur.

o Select the Ma k e file or folder attribute's processing issues result in a job warning to receive a warning
at the end of the job processing session if any issues with processing of file or folder attributes occur.

7. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

1633 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Archive Repository Settings
At the Archive Repository step of the wizard, define the archive repository, where the file backup job must store
backup files, and settings for moving files and folders to this repository. To learn what storage types you can
assign the role of the archive repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

1. If you need to keep versions of some files for a longer time after they are moved from the backup
repository, you can configure archiving options to move file versions to a cheaper archive storage, for
example, an object storage.

To use the archive repository, select the Archive file versions to the following archive repository check
box.

2. From the drop-down list below, select the storage to be used as a repository to store archived files and
folders.

By default, all files deleted from the backup repository will be moved to the archive repository. If you do
not need all the files in the archive, you can choose what files to keep.

3. If you need to keep the copy of the data stored in the backup repository also in the archive repository,
select the Archive recent file versions check box.

NOTE

The copy mode in NAS backup requires a license. Thus, this feature is not supported in the
Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions Comparison.

4. To specify the number of months or years during which backup files must be retained, select the Archive
p revious file versions for check box and specify the period.

This setting denotes a time period starting from the creation of the backup files in the backup repository,
not from the moment when the file versions are moved from the backup repository to the archive
repository.

5. To specify what files must be archived or excluded from the archive, do the following:

a. Click Choose to open the File Archive Settings window.

b. Under Files to archive, specify what files must be archived:

▪ All files — select this option to archive all files moved from the backup repository to the archive
repository.

▪ All files except the following extensions — select this option to exclude files with certain
extensions from the selection to be archived. Specify extensions for files to exclude from the
selection. Files with the specified extensions will not be copied from the backup repository to
the archive repository.

1634 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ Files with the following extensions only — select this option to archive files with certain
extensions only. Specify extensions for files to archive. Files with these extensions will be copied
from the backup repository to the archive repository.

1635 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Secondary Repository Settings
At the Secondary Target step of the wizard, you can specify a secondary repository that will be used to store
additional copies of backup files from the backup storage for redundancy. To learn what storage types you can
assign the role of the secondary repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

If you add a secondary repository, Veeam Backup & Replication will create a separate job for backup copy to it.
The data copy process will start automatically after each primary job runs.

NOTE

This step is available, if you select the Configure secondary destinations for this job check box at the
Backup Repository step of the wizard.

To add a secondary repository:

1. Click Ad d .

2. From the list of existing repositories, select a repository that will keep additional copy of the backup files.
You can add several secondary repositories for copying files of the primary backup job. To quickly find t he
repository, use the search field at the bottom of the wizard.

3. By default, retention and encryption settings for the secondary target repository are inherited from the
primary job. To customize them, select the necessary repository in the Secondary repositories list and click
E d it.

o To enable custom retention settings:

i. Select Use custom retention policy.

ii. Specify how long all versions of each file will be kept in the secondary repository.

1636 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To specify encryption settings different from those of the primary repository:

i. Select Use custom data encryption settings.

ii. In the P a ssword field, select a password that you want to use for encryption. If you have not
created the password beforehand, click Ad d or use the Ma nage passwords link to specify a new
password. For more information, see Managing Passwords for Data Encryption.

If the backup server is not connected to Veeam Backup Enterprise Manager and does not have
the Veeam Universal License or a legacy socket-based Enterprise or Enterprise Plus license
installed, you will not be able to restore data from encrypted backups in case you lose the
password. Veeam Backup & Replication will display a warning about it. For more information,
see Decrypting Data Without Password.

o Configure time intervals at which the data can be copied to the secondary repository.

▪ If you select the Any time (continuously) option, Veeam Backup & Replication will copy backup
files to the secondary repository as soon as the primary file backup job completes.

▪ If you want to specify time periods when it is permitted to start copying backup files to the
secondary repository, select the During the following time periods only option and configure
allowed and prohibited hours. These periods do not work as the backup window, so they will not
cause the file backup copy to fail.

1637 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Define Job Schedule
At the Schedule step of the wizard, select to run the backup job manually or schedule the job to run on a regular
basis.

To specify the job schedule:

1. Select the Run the job automatically check box. If this check box is not selected, you will have to start the
job manually to create the file share backup.

2. Define scheduling settings for the job:

o To run the job at specific time daily, on defined week days or with specific periodicity, select Da ily at
this time. Use the fields on the right to configure the necessary schedule.

o To run the job once a month on specific days, select Monthly at this time. Use the fields on the right
to configure the necessary schedule.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for
example, related to daylight saving time transition).

o To run the job repeatedly throughout a day with a specific time interval, select P eriodically every. In
the field on the right, select the necessary time unit: Hours or Minutes. Click Schedule and use the
time table to define the permitted time window for the job. In the Sta rt time within an hour field,
specify the exact time when the job must start.

A repeatedly run job is started by the following rules:

▪ Veeam Backup & Replication always starts counting defined intervals from 12:00 AM. For
example, if you configure to run a job with a 4-hour interval, the job will start at 12:00 AM, 4:00
AM, 8:00 AM, 12:00 PM, 4:00 PM and so on.

▪ If you define permitted hours for the job, after the denied interval is over,
Veeam Backup & Replication will immediately start the job and then run the job by the defined
schedule.

For example, you have configured a job to run with a 2-hour interval and defined permitted hours
from 9:00 AM to 5:00 PM. According to the rules above, the job will first run at 9:00 AM, when the
denied period is over. After that, the job will run at 10:00 AM, 12:00 PM, 2:00 PM and 4:00 PM.

o To run the job continuously, select the P eriodically every option and choose Continuously from the
list on the right. A new backup job session will start as soon as the previous backup job session
finishes.

o To chain jobs, use the After this job field. In the common practice, jobs start one after another: when
job A finishes, job B starts and so on. If you want to create a chain of jobs, you must define the time
schedule for the first job in the chain. For the rest of the jobs in the chain, select the After this job
op tion and choose the preceding job from the list.

3. In the Automatic retry section, define whether Veeam Backup & Replication must attempt to run the
backup job again if the job fails for some reason. During a job retry, Veeam Backup & Replication processes
failed file shares only. Enter the number of attempts to run the job and define time intervals between
them. If you select continuous backup, Veeam Backup & Replication will retry the job for the defined
number of times without any time intervals between the job runs.

1638 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ba ckup window section, define the time interval within which the backup job must complete. The
backup window prevents the job from overlapping with production hours and ensures that the job does
not provide unwanted overhead on the production environment. To set up a backup window for the job:

a. Select the Terminate job if it exceeds allowed backup window check box and click W ind ow.

b. In the Time P eriods window, define the allowed hours and prohibited hours for backup. If the job
exceeds the allowed window, it will be automatically terminated.

NOTE

The After this job function will automatically start a job if the first job in the chain is started automatically
by schedule. If you start the first job manually, Veeam Backup & Replication will display a notification. You
will be able to choose whether Veeam Backup & Replication must start the chained job as well.

1639 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of backup job configuration.

1. Review details of the backup job.

2. If you want to start the job right after you finish working with the wizard, select the Run the job when I
click Finish check box.

3. Click Finish to close the wizard.

1640 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Object Storage Backup Jobs
NOTE

The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131).

To protect an object storage repository, configure an object storage backup job. The backup job defines how,
where and when to back up data from the object storage. One job can be used to protect one or more object
storage repositories. Jobs can be started manually or scheduled to run automatically at a specific time.

Object storage backup jobs are used to protect the following sources of unstructured data:

• S3 compatible object storage

• Amazon S3 object storage

• Microsoft Azure Blob storage

Before you create an object storage backup job, check prerequisites.

Before You Begin


This section contains information that you should consider before you create an object storage backup job.

General Considerations
Before you create an object storage backup job, consider the following:

• The object storage backup feature is available starting from Veeam Backup & Replication 12.1 (build
12.1.0.2131).

• Consider limitations listed in the Platform Support section.

• The account that you use to add Amazon S3 and S3 Compatible object storage as unstructured sources and
back up data from them must be able to perform the actions listed in the Permissions section.

• Backup infrastructure components that will take part in the object storage backup process must be added
to the backup infrastructure and properly configured. These include objects storage sources to back up,
backup proxies, and all repositories, including cache, backup, archive, and secondary repositories. For
more information, see the Backup Infrastructure for Unstructured Data Backup section.

• The target backup repository must have enough free space to store created backup files. If you want to
receive notifications on the repository running low on free space, configure global notification settings as
described in the Specifying Other Notification Settings section.

• Make sure that repositories intended to store object storage backups are not configured to store files in
the Write Once Read Many (WORM) status. Otherwise, the backup jobs will fail when
Veeam Backup & Replication cannot update the backup metadata files.

• If you plan to map an object storage backup job to a backup that already exists in the backup repository,
you must perform the rescan operation for this backup repository. Otherwise, Veeam Backup & Replication
will not be able to recognize backup files in the backup repository.

For more information on how to rescan backup repositories, see the Rescanning Backup Repositories
section.

1641 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you plan to use pre-job and post-job scripts, you must create scripts before you configure the object
storage backup job.

• Antivirus software may significantly slow down object storage backup jobs. To improve performance, we
recommend you exclude the c:\Program Files (x86)\Veeam\Backup
Transport\x64\VeeamAgent.exe process from the antivirus scan on machines running the object
storage backup proxy and backup repository roles. Keep in mind that it can weaken the security of these
machines.

• If the object content and modification time are not changed, Veeam Backup & Replication will back up
only attributes of this object.

• Veeam Backup & Replication does not back up version history of objects.

Limitations for Microsoft Azure Blob Storage


Before you create an object storage backup job, consider the following limitations for Microsoft Azure Blob
storage:

• Veeam Backup & Replication does not back up encrypted objects with the custom user key.

• Veeam Backup & Replication does not support the following backup options if you add the source
Microsoft Azure Blob storage using the Microsoft Azure storage account with Microsoft Entra ID
authorization:

o Backup of ACL for Azure containers.

o Backup of hierarchical namespace.

Limitations for Amazon S3 Storage


Before you create an object storage backup job, consider the following limitations for Amazon S3 storag e:

• Veeam Backup & Replication does not back up encrypted objects with the custom user key.

• Veeam Backup & Replication does not support backup of the data blocks with the Amazon S3 Glacier
Flexible Retrieval and Amazon S3 Glacier Deep Archive and storage classes.

1642 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Object Storage Backup Job Wizard
To launch the New Object Storage Backup Job wizard, do one of the following:

• On the Home tab, click Ba ckup Job > Ob ject Storage .

• Open the Home view. Right-click in the working area, and select Ba ckup > Ob ject storage.

• Open the Home view. In the inventory pane, right-click the Job s node and select Ba ckup > Ob ject storage.

You can quickly add an object storage source to an already existing job. Open the Inventory view. Under the
Unstructured Data node in the inventory pane, select Ob ject Storage. In the working area, right-click the object
storage source you want to back up and select Ad d to backup job > name of the job .

1643 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Na me step of the wizard, specify a name and description for the object storage backup job.

1. In the Na me field, enter a name for the object storage backup job.

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

3. Select the Hig h priority check box if you want the resource scheduler of Veeam Backup & Replication to
prioritize this job higher than other similar jobs and to allocate resources to it in the first place. For more
information on job priorities, see Job Priorities.

TIP

In the UI, jobs with the Hig h priority option enabled will be marked with a special flag ( ).

1644 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Objects to Back Up
At the Ob jects step of the wizard, select objects that you want to back up..

1. Click Ad d .

2. From the Ob ject Storage drop-down list, select an object storage on which the necessary objects reside.

This drop-down lists contains all object storage added to the inventory, as described in the Adding Object
Storage section.

3. In the Ob jects tree, select objects you want to back up.

To select multiple objects, hold [Ctrl] and click necessary folders.

4. If you specify a path to a bucket or container or prefix, all the contents will be processed.

If necessary, you can choose only specific objects from the added prefix.

Including Objects
To filter objects that you want to back up, you can specify the object name and extension masks.

1. Select an object in the Ob jects list and click Filters.

2. In the Include and exclude masks window, use Include masks field to include objects or prefixes.

3. Click Ad d .

4. In the Include object by tag window, specify the tag name and value associated with the object or prefix.

5. Click OK.

1645 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Excluding Objects

To filter objects that you do not want to back up, you can
specify the objects by a path or by a tag.
1. Select an object in the Ob jects list and click Ad vanced.

2. In the Include and exclude masks window, use the E x clude masks field to exclude objects.

3. Click Ad d .

4. Depending on the way you want to exclude objects, select one of the following:

o To exclude objects by path, click Ob jects by path... and in the E x clude objects by path window,
specify a path to the objects that you want to exclude.

NOTE

Wildcards are not supported.

o To exclude objects by tag, click Ob jects by tag... and in the E x clude objects by tag window specify the
tag name and value associated with the object or prefix.

Exporting and Importing Filters


If necessary, you can export and import your masks :

• To export a mask to a file, click the E x port these filters link. In the E x port to file window, specify a path to
the necessary XML file. Click OK.

• To import existing masks from a file, click the Imp ort existing list link. In the Imp ort masks from file
window, specify a path to the necessary XML file. Click OK.

1646 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Backup Repository Settings
At the Ba ckup Repository step of the wizard, define the primary backup repository, where the object storage
backup job must store objects, and settings for moving objects to this repository. To learn what storage types
you can assign the role of the backup repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

NOTE

Consider that if you use the option of limiting the number of object versions to keep configured in Object
Version Settings, Veeam Backup & Replication first applies those object-version retention settings and only
after that applies time-based retention settings specified at this step.

1. From the Ba ckup repository drop-down list, select a repository where backup files must be stored. When
you select a backup repository, Veeam Backup & Replication automatically checks the amount of free
space left. Make sure that you have enough free space to store backups.

2. You can map the job to a specific backup stored in the backup repository. Backup job mapping allows you
to move backup files to a new backup repository and to point the job to existing backups on this new
backup repository. You can also use backup job mapping if the configuration databas e got corrupted and
you need to reconfigure backup job settings.

To map the job to a backup, click the Ma p backup link. In the opened Select Backup window, select a
backup in the backup repository. Backups can be easily identified by job names. To find the backup, you
can also use the search field at the bottom of the window.

3. Use the Keep all versions for the last field to specify how long copies of all recent object versions from the
selected object storage bucket or container must be kept in the backup repository. You can restore the
entire bucket or container to any restore point within the period specified in this setting.

If, for example, Keep all versions for the last is set to 30 days, the backup repository will store all object
versions that appeared in the object storage bucket or container during the last 30 days. At the scheduled
time on the 31st day, the object storage backup job first backs up new object versions and saves them to
the backup repository. Right after that, object versions older than 30 days (created on the 1st day) are
either deleted from the backup repository or moved to the archive repository. Object versions are moved
to the archive repository, if at the Archive Repository step of the wizard you enable the Archive file
versions to the following archive repository check box and configure the archive retention.

1647 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you need to keep a copy of backups in another repository, select the Configure secondary destinations
for this job check box. That enables the Secondary Target step of the wizard.

1648 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Advanced Backup Settings
At the Ba ckup Repository step of the wizard, specify advanced settings for the object storage backup job:

• Object version settings

• Storage settings

• Maintenance settings

• Script settings

• Notification settings

TIP

After you specify necessary settings for the backup job, you can save them as default settings. To do this,
click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create a new
backup job, Veeam Backup & Replication will automatically apply the default settings to the new job.

Object Version Settings


To configure how many versions to keep for protected objects, do the following:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the Ob ject versions tab, specify to what object versions the settings should apply:

o Select Keep all versions to keep all object versions for the time period specified at the Backup
Repository step.

o Select Limit the number of archived versions only to limit archived versions to the numbers specified
below.

o Select Limit the number of both recent and archived versions to limit recent and archived versions to
the numbers specified below.

3. After you choose what object versions to keep, specify how many file versions to keep:

o Select Active versions limit to keep the specified number of versions for objects currently existing in
the object storage source. Specify how many object versions to store.

o Select Deleted versions limit to keep the specified number of versions for objects deleted from the
object storage source. Specify how many object versions to store.

1649 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users ad ded to the backup server.

Storage Settings
To specify advanced storage settings for the object storage backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the Storage tab, specify data reduction and encryption settings:

o From the Compression level list, select a compression level for the backup: None, Dedupe-
friendly , Optimal, High or Extreme.

o To encrypt the content of backup files, select the E na ble backup file encryption check box. In the
P a ssword field, select a password that you want to use for encryption. If you have not created the
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For
more information, see the Password Manager section.

If the backup server is not connected to Veeam Backup Enterprise Manager and does not have the
Veeam Universal License or a legacy socket-based Enterprise or Enterprise Plus license installed, you
will not be able to restore data from encrypted backups in case you los e the password.
Veeam Backup & Replication will display a warning about it. For more information, see the Decrypting
Data Without Password section.

1650 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• If you enable encryption for an existing backup job, during the next job session
Veeam Backup & Replication will back up all the files of the file share to a new backup
file irrespective of whether they changed or not. The created backup files and
subsequent backup files will be encrypted with the specified password.
• If you enable encryption for an existing job, Veeam Backup & Replication does not
encrypt the previous backup chain created by this job.
• You can also use KMS keys for encryption. For more information, see the Key
Management System Keys section.

3. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the b ackup server.

Maintenance Settings
You can instruct Veeam Backup & Replication to periodically perform a health check for the backup. The health
check ensures that the backup is consistent, and you will be able to restore data from it.

During the health check, Veeam Backup & Replication performs a CRC check for metadata and a hash check for
data blocks in the object storage backup files to verify their integrity. For more information, see the Performing
Health Check and Repair for Unstructured Data Backups section.

To configure the health-check settings for backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. On the Ma intenance tab, select P erform backup files health check to enable the health check option. It
ensures that all data and metadata is backed up correctly.

1651 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Click Configure and specify the time schedule for the health check.

4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Script Settings
You can configure custom scripts to run before or after the object storage backup job.

To specify script settings for the the object storage backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. Click the Scripts tab.

3. If you want to execute custom scripts, select the Run the following script before the job and Run the
following script after the job check boxes and click Browse to choose executable files from a local folder
on the backup server. The scripts are executed on the backup server.

You can select to execute pre- and post-backup actions after a number of backup sessions or on specific
week days.

o If you select the Run scripts every <N> backup session option, specify the number of the backup job
sessions after which the scripts must be executed.

o If you select the Run scripts on the selected days only option, click Da y s and specify week days on
which the scripts must be executed.

1652 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Notification Settings
To specify notification settings for the the object storage backup job:

1. At the Ba ckup Repository step of the wizard, click Ad vanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully.

SNMP traps will be sent if you specify global SNMP settings in Veeam Backup & Replication and configure
software on recipient's machine to receive SNMP traps. For more information, see the Specifying SNMP
Settings section.

4. Select the Send email notifications to the following recipients check box if you want to receive
notifications about the job completion status by email. In the field below, specify recipient’s email
address. You can enter several addresses separated by a semicolon.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication. For more information, see the Configuring Global Email Notification Settings
section.

5. You can choose to use global notification settings or specify custom notification settings:

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see the Configuring Global Email Notification Settings section.

1653 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To configure a custom notification for the job, select Use custom notification settings specified
b elow. You can specify the following notification settings:

i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %ObjectCount% (number of
objects in the job) and %Issues% (number of objects in the job that have finished with the
Warning or Failed status).

ii. Select the Notify on success, Notify on warning, and Notify on error check boxes to receive
email notification if the job completes successfully, completes with a warning or fails.

iii. Select the Sup press notifications unt il the last retry check box to receive a notification about the
final job status. If you do not enable this option, Veeam Backup & Replication will send one
notification per every job retry.

6. Specify severity options if required:

o Select the Ma k e object processing issues result in a job warning to receive a warning at the end of the
job processing session if any issues with object processing occur.

o Select the Ma k e object attribute processing issues result in a job warning to receive a warning at the
end of the job processing session if any issues with processing of object attributes occur.

7. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

1654 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Archive Repository Settings
At the Archive Repository step of the wizard, define the archive repository, where the object storage backup job
must store backup files, and settings for moving files and folders to this repository. To learn what storage types
you can assign the role of the archive repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

1. If you need to keep versions of some objects for a longer time after they are moved from the backup
repository, you can configure archiving options to move object versions to a cheaper archive storage, for
example, an object storage.

To use the archive repository, select the Archive object versions to the following repository check box.

2. From the drop-down list below, select the storage to be used as a repository to store archived objects.

By default, all objects deleted from the backup repository will be moved to the archive repository. If you
do not need all the objects in the archive, you can choose what objects to keep.

3. If you need to keep the copy of the data stored in the backup repository also in the archive repository,
select the Archive recent object versions check box.

NOTE

The copy mode in object storage backup requires a license. Thus, this featur e is not supported in the
Veeam Backup & Replication Community (free) Edition. For details, see Veeam Editions Comparison.

4. To specify the number of months or years during which backup files must be retained, select the Archive
p revious object versions for check box and specify the period.

This setting denotes a time period starting from the creation of the backup files in the backup repository,
not from the moment when the object versions are moved from the backup repository to the archive
repository.

5. To specify what objects must be archived or excluded from the archive, do the following:

a. Click Choose to open the File Archive Settings window.

b. Under Files to archive, specify what objects must be archived:

▪ All files — select this option to archive all objects moved from the backup repository to the
archive repository.

▪ All files except the following extensions — select this option to exclude objects with certain
extensions from the selection to be archived. Specify extensions for objects to exclude from the
selection. Objects with the specified extensions will not be copied from the backup repository to
the archive repository.

1655 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ Files with the following extensions only — select this option to archive objects with certain
extensions only. Specify extensions for objects to archive. Objects with these extensions will be
copied from the backup repository to the archive repository.

1656 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Secondary Repository Settings
At the Secondary Target step of the wizard, you can specify a secondary repository that will be used to store
additional copies of backup files from the backup storage for redundancy. To learn what storage types you can
assign the role of the secondary repository to, see Storage Repositories in the Ba ckup Infrastructure for
Unstructured Data Backup section.

If you add a secondary repository, Veeam Backup & Replication will create a separate job for backup copy to it.
The data copy process will start automatically after each primary object storage backup job runs.

NOTE

This step is available, if you select the Configure secondary destinations for this job check box at the
Backup Repository step of the wizard.

To add a secondary repository:

1. Click Ad d .

2. From the list of existing repositories, select a repository that will keep additional copy of the backup files.
You can add several secondary repositories for copying files of the primary backup job. To quickly find the
repository, use the search field at the bottom of the wizard.

3. By default, retention and encryption settings for the secondary target repository are inherited from the
primary job. To customize them, select the necessary repository in the Secondary repositories list and click
E d it.

o To enable custom retention settings:

i. Select Use custom retention policy.

ii. Specify how long all versions of each file will be kept in the secondary repository.

1657 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To specify encryption settings different from those of the primary repository:

i. Select Use custom data encryption settings.

ii. In the P a ssword field, select a password that you want to use for encryption. If you have not
created the password beforehand, click Ad d or use the Ma nage passwords link to specify a new
password. For more information, see the Password Manager section.

If the backup server is not connected to Veeam Backup Enterprise Manager and does not have
the Veeam Universal License or a legacy socket-based Enterprise or Enterprise Plus license
installed, you will not be able to restore data from encrypted backups in case you lose the
password. Veeam Backup & Replication will display a warning about it. For more information,
see the Decrypting Data Without Password section.

o Configure time intervals at which the data can be copied to the secondary repository.

▪ If you select the Any time (continuously) option, Veeam Backup & Replication will copy backup
files to the secondary repository as soon as the primary object storage backup job completes.

▪ If you want to specify time periods when it is permitted to start copying backup files to the
secondary repository, select the During the following time periods only option and configure
allowed and prohibited hours. These periods do not work as the backup window, so they will not
cause the file backup copy to fail.

1658 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Define Job Schedule
At the Schedule step of the wizard, select to run the object storage backup job manually or schedule the object
storage backup job to run on a regular basis.

To specify the object storage backup job schedule:

1. Select the Run the job automatically check box. If this check box is not selected, you will have to start the
job manually to create the object storage backup.

2. Define scheduling settings for the job:

o To run the job at specific time daily, on defined week days or with specific periodicity, select Da ily at
this time. Use the fields on the right to configure the necessary schedule.

o To run the job once a month on specific days, select Monthly at this time. Use the fields on the right
to configure the necessary schedule.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for
example, related to daylight saving time transition).

o To run the job repeatedly throughout a day with a specific time interval, select P eriodically every. In
the field on the right, select the necessary time unit: Hours or Minutes. Click Schedule and use the
time table to define the permitted time window for the job. In the Sta rt time within an hour field,
specify the exact time when the job must start.

A repeatedly run job is started by the following rules:

▪ Veeam Backup & Replication always starts counting defined intervals from 12:00 AM. For
example, if you configure to run a job with a 4-hour interval, the job will start at 12:00 AM, 4:00
AM, 8:00 AM, 12:00 PM, 4:00 PM and so on.

▪ If you define permitted hours for the job, after the denied interval is over,
Veeam Backup & Replication will immediately start the job and then run the job by the defined
schedule.

For example, you have configured a job to run with a 2-hour interval and defined permitted hours
from 9:00 AM to 5:00 PM. According to the rules above, the job will first run at 9:00 AM, when the
denied period is over. After that, the job will run at 10:00 AM, 12:00 PM, 2:00 PM and 4:00 PM.

o To run the job continuously, select the P eriodically every option and choose Continuously from the
list on the right. A new backup job session will start as soon as the previous backup job session
finishes.

o To chain jobs, use the After this job field. In the common practice, jobs start one after another: when
job A finishes, job B starts and so on. If you want to create a chain of jobs, you must define the time
schedule for the first job in the chain. For the rest of the jobs in the chain, select the After this job
op tion and choose the preceding job from the list.

3. In the Automatic retry section, define whether Veeam Backup & Replication must attempt to run the
backup job again if the job fails for some reason. During a job retry, Veeam Backup & Replication processes
failed object storage sources only. Enter the number of attempts to run the job and define time intervals
between them. If you select continuous backup, Veeam Backup & Replication will retry the job for the
defined number of times without any time intervals between the job runs.

1659 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Ba ckup window section, define the time interval within which the backup job must complete. The
backup window prevents the job from overlapping with production hours and ensures that the job does
not provide unwanted overhead on the production environment. To set up a backup window for the job:

a. Select the Terminate job outside of the backup window check box and click W ind ow.

b. In the W indow window, define the allowed hours and prohibited hours for backup. If the job exceeds
the allowed window, it will be automatically terminated.

NOTE

The After this job function will automatically start a job if the first job in the chain is started automatically
by schedule. If you start the first job manually, Veeam Backup & Replication will display a notification. You
will be able to choose whether Veeam Backup & Replication must start the chained job as well.

1660 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of object storage backup job configuration.

1. Review details of the object storage backup job.

2. If you want to start the job right after you finish working with the wizard, select the Run the job when I
click Finish check box.

3. Click Finish to close the wizard.

1661 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Unstructured Data Backups
You can perform the following operations with backups:

• View unstructured data backup properties.

• Copy unstructured data backups to another location.

• Start a new backup chain for an unstructured data backup job .

• Perform the health check and repair operations for unstructured data backups .

• Convert backups from SMB or NFS shares to NAS filer shares.

• Convert backups from non-root to root shared folders.

• Update the source file share path for backup jobs with a secondary target.

1662 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Unstructured Data Backup Properties
You can view summary information about the unstructured data backup. The summary information provides the
following data:

• Name and path to the backup repository that stores backup files.

• Name and path to the archive repository that stores archived backup data.

• Path to the backup source and its original size.

• Available restore points: date of their creation, their type (Ba ckup or Archive) and status.

For the Ba ckup type, the table shows all restore points stored in the backup repository. You can restore
the unstructured data to the state as of any of these points. To lea rn how to restore the file share data,
see File Share Data Recovery, to restore object storage data — Object Storage Data Recovery.

For the Archive type, the table shows only a single record. The time stamp of this record denotes the date
and time of the restore point, which was created in the backup repository and files of which were the
latest to be moved to the archive repository according to retention settings. To learn how to restore files
from the archive, see the Restoring Backup Files from Archive Repository sections for the file share data
recovery and the object storage data recovery.

To view summary information for backups:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

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

4. To see the list of available restore points, select the required object from the Ob jects list.

1663 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Copying Unstructured Data Backups
Copying backups can be helpful if you want to copy file share backups to a repository or local or shared folder.
Veeam Backup & Replication copies the whole backup chain.

When Veeam Backup & Replication performs the copy operation, it disables the job, copies files to the target
location and then enables the job. After the copy operation finishes, the copied backups are shown in a node
with the ( E xported) postfix in the inventory pane.

NOTE

This section is about one-time copy operation. If you want to copy backups on a schedule, create a backup
copy job. For more information, see Backup Copy.

Copying Backups
To copy file share backups, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary job.

4. Right-click the job and select Cop y backup. Alternatively, click Cop y Backup on the ribbon.

5. In the Cop y Backup to Another Location window, choose a repository to which you want to copy backups.

6. [For archive backups] If you also want to copy archive backups to another archive repository, select the
Cop y the associated archive check box. From the drop-down list, select the necessary repository.

7. Click OK.

After the copy process finishes, the copied backups are shown in the Disk (Exported) node in the inventory pane.

NOTE

Consider the following:

• If you copy backups from a scale-out backup repository and some backups are stored on extents in
the Maintenance mode, such backups are not copied.
• Veeam Backup & Replication copies backups only from the performance tier of the scale-out backup
repository. If you want to copy data from the capacity tier, you first need to download it to the
performance tier. For more information, see Downloading Data from Capacity Tier.

1664 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Starting New Backup Chain
You can start a new backup chain for the unstructured data backup job. Veeam Backup & Replication then
creates a new active full backup that starts the new chain for the entire protected file share or bucket. All
existing backup files are moved to the Disk (Orphaned) node under the Ba ckups node in the
Veeam Backup & Replication Console. Data files are stored to the same folder in the backup repository. The data
files for the new backup chain are stored to a new separate folder in the backup repository.

To start a new backup chain:

1. Open the Home view.

2. In the inventory pane, select Job s > Ba ckup.

3. In the working area, select a job of the File Backup or Ob ject Storage Backup type, press and hold the
[Ctrl] key, right-click the job and select Sta rt new backup.

1665 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Performing Health Check and Repair for
Unstructured Data Backups
In this section you will learn how to perform:

• Health check for file share backup files

• Repair of file share backup files

Health Check for File Share Backup Files


You can manually perform a health check for the backup chain. During the health check,
Veeam Backup & Replication performs a CRC check for metadata and a hash check for data blocks in backup files
to verify their integrity. The health check helps make sure that the restore point is consistent, and you will be
able to restore data from this restore point.

To run the health check:

1. Open the Home view.

2. In the inventory pane, select Job s/1 > Ba ckup.

3. In the working area, select a job of the File Backup or Ob ject Storage Backup type and click Run Health
Check on the ribbon or right-click the job and select Run health check.

To run the health check periodically, you must enable the P erform backup files health check option in the
backup job settings and define the health check schedule. By default, the health check is performed on the last
Friday of every month. You can change the schedule and run the health check weekly or monthly on specific
days. To learn how to configure periodic health check, see Maintenance Settings.

IMP ORTANT

If you store your file backups on public cloud object storage repositories, running the health check
operations may result in constantly downloading and uploading data to and from the storage, which may
lead to higher costs. To avoid this, use helper appliances, configured for the repositories within the public
clouds. For more information, see the Object Storage as NAS Backup Repository section.

1666 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Repair of File Share Backup Files
If during the health check Veeam Backup & Replication detects some inconsistency in the file share backup files,
you can run the backup repair procedure to fix the issues.

To run the backup repair:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select a job of the File Backup type, right-click the job and select Rep air backup.

1667 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Converting Backups from SMB or NFS Shares to
NAS Filer Shares
You can use enterprise storage systems integrated with Veeam Backup & Replication both to host simple SMB or
NFS shares and to act as NAS filer shares.

NOTE

You cannot convert backups stored on a root server or shares from the root server.

To use all the advantages of NAS filer shares, for example the native file change tracking technology, you can
convert backups created for existing SMB or NFS shares into the format of NAS filer shares. After that you can
continue to protect the file shares as NAS filer shares by running existing file backup jobs and by using existing
backup files. Perform the conversion with extreme caution.

To convert SMB or NFS shares into NAS filer shares, do the following:

1. Disable file backup jobs protecting SMB or NFS shares, for which you want to convert backups. To do that,
right-click the required job in the Job s node of the inventory pane in the Home view and select Disable.
Alternatively, you can click Disable on the ribbon.

2. Make sure that you have created NAS filer, which corresponds to existing SMB or NFS shares, added to the
Veeam Backup & Replication inventory. The NAS filer and these shares must reside on the same storage
system. The correspondence of the shares must be full except for the host name.

3. Run the Convert-VBRNASBackupSANFormat PowerShell cmdlet to convert the format of the file share
backup to provide support of NAS filer shares.

$nasbackup = Get-VBRNASBackup -name "File Backup Job 1"


$netapp = Get-NetAppHost -name "pdc-ontap-1"
$netapp_filer = Get-VBRNASServer -SANEntity $netapp
Convert-VBRNASBackupSANFormat -Backup $nasbackup -Server $netapp_filer

For more information, see the description of the Convert-VBRNASBackupSANFormat cmdlet in the
Veeam PowerShell Reference.

As a result, the backup will be moved from Ba ckups > Disk node to Ba ck ups > Disk (Orphaned) node in the
inventory pane of the Home view.

At this step, you can check if the cmdlet has correctly converted the backup. To do that, check if backup
object names in the Disk (Orphaned) node have changed and now show the path to the NAS filer share. If
object names have not changed and show the path to the SMB or NFS share as before, continuing the
conversion process can lead to the unwanted result. For example, when you enable the backup job for the
converted backup, it will back up the NAS filer share not with an incremental run, but with a full run
instead, which may lead to extra costs.

4. Use the Edit File Backup Job wizard to edit the file backup job that protects the file shares:

a. At the Files and Folders step of the wizard, remove the existing SMB and NFS shares from the job and
add NAS filer shares instead.

b. At the Backup Repository step of the wizard, map the job to the backup that was converted at step 2.

5. Enable file backup jobs protecting file shares, for which you converted backups. To do that, right -click the
required job from the Job s node of the inventory pane in the Home view and clear selection of Disable.
Alternatively, you can click Disable on the ribbon.

1668 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication supports conversion of backups created by backup copy jobs. To continue the old
backup chain created by the backup copy job, do the following:

1. Disable file backup jobs protecting SMB or NFS shares, for which you want to convert backups. To do that,
right-click the required job in the Job s node of the inventory pane in the Home view and select Disable.
Alternatively, you can click Disable on the ribbon.

2. Make sure that you have created NAS filer, which corresponds to existing SMB or NFS shares, added to the
Veeam Backup & Replication inventory. The NAS filer and these shares must reside on the same storage
system. The correspondence of the shares must be full except for the host name.

3. Run the Convert-VBRNASBackupSANFormat PowerShell cmdlet to convert the format of the file share
backup to provide support of NAS filer shares.

$backup_copy = Get-VBRNASBackup -name "File Backup Job 1 (Copy)"


$netapp = Get-NetAppHost -name "pdc-ontap-1"
$netapp_filer = Get-VBRNASServer -SANEntity $netapp
Convert-VBRNASBackupSANFormat -Backup $backup_copy -Server $netapp_filer

For more information, see the description of the Convert-VBRNASBackupSANFormat cmdlet in the
Veeam PowerShell Reference.

4. Use the Edit File Backup Job wizard to remove the secondary target storage for the file backup job that
protects the file shares:

a. At the Secondary Target step of the wizard, remove the required repository selected as a secondary
target for the file backup job.

b. Go through all the wizard steps without running the job. Click Finish.

5. Use the Edit File Backup Job wizard to add the secondary target storage back for the file backup job that
protects the file shares:

a. At the Secondary Target step of the wizard, add the required repository as a secondary target for the
file backup job.

b. Go through all the wizard steps. Click Finish.

6. Enable file backup jobs protecting file shares, for which you converted backups. To do that, right -click the
required job from the Job s node of the inventory pane in the Home view and clear selection of Dis able.
Alternatively, you can click Disable on the ribbon.

File share backup copy will automatically map to the file backup copy job. After that, the backup copy job
will back up new points of the main file backup job if they were created.

1669 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Converting Backups from Non-Root to Root
Shared Folders
Veeam Backup & Replication allows adding a server root folder as a source for file backup jobs. In this case, all
changes to separate shared folders residing on this server will be reflected in the file backup job whe re the root
shared folder of this server is added. You can even add shared root folders using different protocols to one file
backup job and thus protect all file shares that are or will be added on the server.

If you previously had several separate non-root shared folders residing on the same server and want to switch to
using a single root shared folder to cover the same shares, you do not have to run full backups to update data of
protected shares. Instead, you can convert existing backups and update existing file backup jobs to protect
single root shared folders comprising all other non-root shared folders residing on the same server. Perform the
conversion with extreme caution.

To convert backups from non-root to root shared folders, do the following:

1. Disable file backup jobs protecting file shares, for which you want to convert backups. To do that, right -
click the required job in the Job s node of the inventory pane in the Home view and select Disable.
Alternatively, you can click Disable on the ribbon.

2. Make sure that your backup infrastructure has a root share (for example, NFS or SMB) added for the whole
server or storage system where existing non-root shares reside. These shares must reside on the same
server or storage system. The correspondence of the shares must be full except for the host name.

3. Run the Convert-VBRNASBackupRootFormat PowerShell cmdlet to convert backups created by one


file backup job for separate non-root shared folders residing on the same server into the backup created
for the server single root folder with all the non-root shared folders of the same type under it. For more
information, see the description of the Convert-VBRNASBackupRootFormat cmdlet in the Veeam
PowerShell Reference.

As a result, the backup will be moved from Ba ckups > Disk node to Ba ck ups > Disk (Orphaned) node in the
inventory pane of the Home view.

At this step, you can check if the cmdlet has correctly converted the backup. To do that, check if backup
object names in the Disk (Orphaned) node have changed and now show the path to the server root folder.
If object names have not changed and show the paths to multiple separate non-root shared folders as
before, continuing the conversion process can lead to the unwanted result. For example, when you enable
the backup job for the converted backup, it will back up all shared folders under root folder not with an
incremental run, but with a full run instead, which may lead to extra costs.

4. Use the Edit File Backup Job wizard to edit the file backup job that protects the file shares:

a. At the Files and Folders step of the wizard, remove the existing non-root shared folders from the job
and add the server root folder instead.

b. At the Backup Repository step of the wizard, map the job to the backup that was converted at step 2.

5. Enable file backup jobs protecting file shares, for which you converted backups. To do that, right-click the
required job from the Job s node of the inventory pane in the Home view and clear selection Disable.
Alternatively, you can click Disable on the ribbon.

1670 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Updating Source File Share Path for Backup Jobs
with Secondary Target
Veeam Backup & Replication does not support auto mapping of the source file share path for the file backup
copy when updating the source file share path for the main file backup job.

For example, you have a File Backup job protecting the file share located at \\shared_server\documents. It
has an associated backup copy job - File Backup ( Copy) 1. The file backups are stored in the ma in_storage
repository, the file backup copies are stored in the cop y _storage repository. Then, you decide to update the
protected file share name to \\share_server_new\documents.

To correctly update the file backup job protecting this file share, do the following:

1. Add a new file share \\share_server_new\documents in the inventory, as described in section Adding
File Share. Do not remove the old file share from the inventory yet as it is associated with the old file
backup job.

2. Update the path to the source file share for the file backup.

$nasbackup = Get-VBRNASBackup -Name "File Backup"


$sourceserver = Get-VBRNASServer -Backup $nasbackup
$targetserver = Get-VBRNASServer -Name "\\share_server_new\documents"
Update-VBRNasBackupPath -Backup $nasbackup -SourceNASServer $sourceserver
-TargetNASServer $targetserver

As a result, the backup will be moved from the Ba ckups - Disk to Ba ckups - Disk (Orphaned).

3. Update the path to the source file share for the file backup copy.

$nasbackup = Get-VBRNASBackup -Name "File Backup (Copy) 1"


$sourceserver = Get-VBRNASServer -Backup $nasbackup
$targetserver = Get-VBRNASServer -Name "\\share_server_new\documents"
Update-VBRNasBackupPath -Backup $nasbackup -SourceNASServer $sourceserver
-TargetNASServer $targetserver

As a result, the backup copy will be moved from Ba ckups - Disk (Copy) to Ba ckups - Disk (Orphaned).

4. Edit settings of the File Backup job defining file backup properties:

a. Remove the old protected file share at \\shared_server\documents and add the new file share at
\\share_server_new\documents, as described in sections Select Files and Folders to Back Up of
Creating File Backup Jobs.

b. Map the file backup job to the File Backup backup converted at step 2, as described in step 4 of the
Creating File Backup Jobs procedure.

c. Remove the secondary target repository added at step 7 of Creating File Backup Jobs procedure.

d. Ensure that the Run the job when I click Finish check box is not selected when you close the wizard, as
described in step 9 of the Creating File Backup Jobs procedure.

5. Edit settings of the File Backup job defining file backup copy properties:

a. Enable creation of the file backup copy by selecting the Configure secondary destinations for this job
check box, as described in step 4 of the Creating File Backup Jobs procedure.

1671 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
b. Add the cop y_storage repository for storing backup copies, as described in step 7 of the Creating File
Backup Jobs procedure.

Veeam Backup & Replication will automatically map the existing file backup copy, which was
previously located in Ba ckups - Disk (Orphaned), to the file backup job.

c. Ensure that the Run the job when I click Finish check box is selected when you close the wizard, as
described in step 9 of the Creating File Backup Jobs procedure.

As a result, if the job and its backups are updated correctly, the first session of the updated job will create not a
full backup, but an incremental one.

1672 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Unstructured Data Recovery
Veeam Backup & Replication offers the following types of recovery:

File share data recovery — to restore data previously backed up with file backup jobs.

Object storage data recovery — to restore data previously backed up with object storage backup jobs.

Related Topics
Data Recovery

1673 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
File Share Data Recovery
You can restore data previously backed up with file backup jobs. You can restore the following data:

• SMB file share files and folders

• NFS file share files and folders

• Files and folders of a managed Microsoft Windows server

• Files and folders of a managed Linux server

Veeam Backup & Replication offers several recovery options for different recovery scenarios:

• Instant file share recovery allows you to publish a point-in-time file share state to instantly access all
protected files.

• Restore of the entire file share allows you to recover all files and folders of the file share to one of the
restore points.

• Rollback to a point in time allows you to restore only changed files to one of the restore points.

• Restore of files and folders allows you to select files and folders to restore to one of the restore points.

• Restore of files from an archive repository allows you to select archived files to restore to one of the
restore points.

Instant File Share Recovery


The instant file share recovery feature works in 2 modes depending on the type of the file share:

• For NFS file shares, you can use this feature to publish a point-in-time file share state to enable users to
instantly access all protected files in the read-only mode.

• For SMB file shares, you can use this feature to publish a point-in-time file share state to enable users to
add, update, remove files in the mounted file share. The updated file share may be then migrated to the
production server.

Performing Instant File Share Recovery


Before you perform instant file share recovery, check prerequisites.

Before You Begin

Before you perform instant file share recovery, consider the following:

• NFS file shares recovered with instant recovery are available in the read -only mode.

• Files larger than 1 GB are not available for update in file shares recovered with instant recovery.

• You cannot rename folders in file shares recovered with instant recovery.

1674 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Instant File Share Recovery Wizard

To launch the Instant File Share Recovery wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > File Share. In the Restore from File Backup window, click
Instant file share recovery.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the file share that you want to restore. In the Ba ckup tab on the ribbon, click Instant Recovery.

o Right-click the file share that you want to restore and select Instant file share recovery.

You can perform the instant file share recovery by using a backup copy. Backup copies created in the
secondary repositories are represented in the Ba ckups > Disk (Copy) node in the inventory pane. If the
secondary repository is an object storage repository, backup copies created in it are represented in the
Ba ckups > Ob ject Storage (Copy) node in the inventory pane.

1675 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select File Share to Restore

At the File Shares step of the wizard, select the file share for which you want to perform instant recovery:

1. Click Ad d .

2. In the Ba ckups Browser window, expand the necessary backup job to select the required file share to
restore.

To quickly find a file share, you can use the search field at the bottom of the window.

1. Enter a file share name or a part of it in the search field.

2. Press [Enter] to start the search.

Alternatively, you can use the File shares to publish search field to quickly search the required file share and add
it to the list of file shares to publish.

1676 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Mount Server Settings

At the Mount Servers step of the wizard, specify mount server settings for published file shares.

• If you select the Automatic selection option, Veeam Backup & Replication will automatically choose the
mount server where to restore file shares. The job will use the mount server from the repository where the
backup files reside. For scale-out backup repositories, Veeam Backup & Replication will use the least
occupied mount server.

• If you select the Ma nual selection option, you can specify which mount server to use to individually
publish each file share:

a. In the Mount servers list, select a file share for which you want to assign a mount server.

b. Click E d it. Alternatively you can double-click the required file share in the list.

c. In the Select mount server window, select a mount server to use to publish the chosen file share.

To quickly find a mount server, you can use the search field at the bottom of the window.

d. Click OK to confirm selection.

NOTE

Consider that data on the mounted file share may be available to the users added to the Administrators
group on this mount server.

1677 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Access Permissions

After you specify file shares and mount servers, Veeam Backup & Replication validates them. If
Veeam Backup & Replication detects missing security descriptors on the file shares, it adds the Access
P ermissions step to the wizard. At this step you can specify the owner account and permissions for the file
share.

1. From the File shares list, select a file share for which you want to specify an owner account and
permissions.

2. Click Set Owner and specify the owner account for the file share.

3. Click P ermissions and configure access permissions for the file share. The following options are available:

o Deny to everyone

o Allow to everyone

o Allow to the following accounts or groups only

Use Ad d and Remove buttons to configure accounts and groups to which you want to grant
permissions for accessing the file share.

1678 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Reason for Recovery

At the Rea son step of the wizard, specify the reason for performing instant file share recovery. You can leave
the field blank.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1679 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard

At the Summary step of the wizard, review the instant file share recovery settings and click Finish.
Veeam Backup & Replication will publish the file share to the specified mount servers.

Migrating File Share to Production


NOTE

Migration to production is supported for backups of SMB file shares only.

After you recover an SMB file share as described in section Performing Instant File Share Recovery, you can
update the content of the mounted file share. After that, you can keep all the changes by migrating the
mounted file share to production.

1680 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Migrate to Production Wizard

To launch the Mig rate to Production wizard, open the Home view. In the inventory pane, select Instant
Recovery. In the working area, select the necessary published file share and do one of the following:

• In the Instant Recovery tab on the ribbon, click Mig rate to Production.

• Right-click the file share that you want to migrate and select Mig rate to Production.

1681 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Define Destination for Migration

At the Destination step of the wizard, specify the location where you want to migrate the selected file share to.

• Select Orig inal location to migrate data to the location where it resided originally. This type of migration is
only possible if the original device is connected to Veeam Backup & Replication and powered on.

• Select This server to migrate data to another location:

a. In the This server field, select a file share where files must be migrated to. You can select any file
share added to the backup inventory. If the required file share is missing in the drop -down list, click
Ad d and add a new file share to Veeam Backup & Replication. For more information on how to add a
new file share, see File Share.

b. In the P a th to folder field, specify a path to the folder on the selected file share where files must be
migrated to.

To select a specific folder on the file share to migrate files to, click Browse. In the Select Folder
window, select the target location for the file share.

If you want to restore the file share to a new folder, click New Folder at the bottom of the window,
enter the folder name and click OK to confirm the new folder creation.

1682 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Restore Options

At the Restore Options step of the wizard, specify overwrite options in case the file with the same name already
exists in the destination:

• If you want to overwrite the existing files only if they are older than the restored files, select the Rep lace
old er files only option .

• If you want to restore the whole file share and overwrite the existing files with the restored files, select
the Restore anyway (overwrites the existing file) option.

1683 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Switchover Options

During migration to production, Veeam Backup & Replication moves to the production site not only content of
the initial file share, but also incremental changes made by users in the mounted file share. When incr emental
changes are being moved, the mounted share is not available to users. We call this stage a switchover. The
switchover may take some time, so ensure you properly plan when it is performed.

At the Switchover step of the wizard, specify file share switchover options:

• If you want Veeam Backup & Replication to perform the switchover automatically once the entire file
share is migrated, select the Automatic option.

• If you want to perform the switchover manually after the entire file share is migrated, select the Ma nual
option.

To launch the switchover manually, open the Home view. In the inventory pane, select Instant Recovery.
In the working area, select the necessary published file share and do one of the following:

o In the Instant Recovery tab on the ribbon, click Switchover Now.

o Right-click the file share that you want to switch over to production and select Switchover now.

• If you want Veeam Backup & Replication to perform the switchover at a certain moment, select the
Scheduled at option and specify when you want it to be done.

Before the scheduled switchover starts, you can edit the switchover time. To edit it, open the Home view.
In the inventory pane, select Instant Recovery. In the working area, select the necessary published file
share and do one of the following:

o In the Instant Recovery tab on the ribbon, click E d it Switchover.

o Right-click the file share that you want to update the switchover time for and select E d it switchover.

1684 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Summary step of the wizard, review the migration to production settings and click Finish.
Veeam Backup & Replication will migrate the selected file share to the specified production destination.

Stopping File Share Publishing


If you do not need the published share any more, you can stop the file share publishing. To do that, open the
Home view. In the inventory pane, select Instant Recovery. In the working area, select the necessary published
file share and do one of the following:

• In the Instant Recovery tab on the ribbon, click Stop Publishing.

• Right-click the file share that you want to unmount and select Stop publishing.

Restoring Entire File Share


You can restore the entire file share from the backup to a specific restore point. That can be helpful, for
example, if your file share device gets out of order and you need to restore the entire file share to the original or
other location.

NOTE

If the Archive recent file versions option is selected (the copy mode is enabled) at the Archive Repository
step of the file backup job wizard, you may restore an entire file share from the archive repository. You can
do that only for restore points that are stored in the archive repository and have the Cop ied label in backup
properties.

If this option is not selected (the copy mode is disabled), the restore of the entire file share or even whole
folders from the archive repository is not supported.

1685 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before you restore an entire file share, check prerequisites.

Before You Begin


Before you restore the entire file share, consider the following:

• You can restore files and folders of the file share from a backup that has at least one successfully created
restore point.

• The file share on which you plan to save restored files and folders must be added to the backup
infrastructure.

• During the backup of an SMB file share, Veeam Backup & Replication does not collect ACL for the root
shared folder. Therefore, if you restore the entire file share, ACL of the root folder is not restored. To
solve this issue, prepare a folder with the required permissions before running the entire file share restore.
During the restore, use this folder as a target root folder for the restored share.

1686 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch File Restore Wizard
To launch the File Restore wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > File Share. In the Restore from File Backup window, click
Restore entire share.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the file share that you want to restore. In the Ba ckup tab on the ribbon, click E ntire share.

o Right-click the file share that you want to restore and select E ntire file share.

You can restore the file share to the state as of a specific restore point by using a backup copy. Backup
copies created in the secondary repositories are represented in the Ba ckups > Disk (Copy) node in the
inventory pane. If the secondary repository is an object storage repository, backup copies created in it are
represented in the Ba ckups > Ob ject Storage (Copy) node in the inventory pane.

1687 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select File Share to Restore
At the File Shares step of the wizard, select the file share that you want to restore:

1. Click Ad d .

2. In the Ba ckups Browser window, select the file backup job and a file share in it that you want to restore.
Click OK.

3. In the File shares table, choose the file share to select a restore point to restore to. Click P oint.

4. In the Select Restore Point window, select the restore point to which you want to restore the file share. To
select the required restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the left pane of the Select Restore
P oint window, select the date when the required restore point was created. The list of restore points
in the right pane displays restore points created on the selected date. Select the point to which you
want to restore the file share.

In the Files in backup tree, you can see what folders and files are covered by the selected restore point
and the date when each of them was modified.

Click OK.

To quickly find a file share, you can use the search field at the top of the window. Enter a file share name or a
part of it in the search field and press [Enter].

To exclude the file share from the restore process, select the file share in the table and click Remove.

1688 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Destination for Data Restore
At the Destination step of the wizard, specify the location where you want to restore the file share.

• Select Orig inal location to restore data to the location where it resided originally. This type of restore is
only possible if the original device is connected to Veeam Backup & Replication and powered on.

• Select This server to restore data to another location:

a. In the This s erver field, select a file share to restore files to. You can select any file share added to the
backup inventory. If the required file share is missing in the drop -down list, click Ad d and add a new
file share to Veeam Backup & Replication. For more information on how to add a new file share, see
File Share.

b. In the P a th to folder field, specify a path to the folder on the selected file share to restore files to.

To select a specific folder on the file share to restore files to, click Browse. In the Select Folder
window, select the target location for the file share.

If you want to restore the file share to a new folder, click New Folder at the bottom of the window,
enter the folder name and click OK to confirm the new folder creation.

c. Select P reserve folder hierarchy to keep the folder hierarchy of the original file share in the new
location.

1689 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Restore Options
At the Restore Options step of the wizard, specify overwrite options in case the file with the same name already
exists in the target folder:

• Sk ip restoring (keeps the existing file). Select this option if you do not want to overwrite the existing file
with the restored one.

• Rep lace older files only (use if a share was reverted to a storage snapshot) . Select this option if you want
to overwrite the existing file only if it is older than the restored file.

• Rep lace newer files only ( use to discard unwanted contents changes) . Select this option if you want to
overwrite the existing file only if the restored file is older than the source share file.

• Restore anyway (overwrites the existing file). Select this option if you want to overwrite the existing file
with the restored file in all cases.

Select the Restore permissions and security attributes check box if you want the restored files to keep their
original ownership and security permissions. If you do not select this check box, Veeam Backup & Replication
will change security settings. The user account under which the Veeam Backup Service runs will be set as the
owner of the restored objects. Access permissions will be inherited from the target folder to which the objects
are restored.

NOTE

Consider that Veeam Backup & Replication does not collect ACL handling settings of the source file share
root folder, so you cannot restore them. Before restoring an entire file share, you will have to specify
required ACL handling settings for the root folder of the ta rget file share.

1690 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard
At the Summary step of the wizard, review the file share restore settings and click Finish.
Veeam Backup & Replication will restore the file share to the specified location.

Rolling Back to a Point in Time


You can roll back changes made to files and folders on the file share to a specific restore point that is older than
the current file share state. This option can be useful, for example, when the original file share was attacked by
ransomware. In this case you can roll back all the files that were changed by the ransomware to the state before
the attack.

Before you roll back the file share to a point in time, check prerequisites.

Before You Begin


Before you restore files and folders to a point in time, consider that you can restore files and folders of the file
share from a backup that has at least one successfully created restore point.

1691 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch File Restore Wizard
To launch the File Restore wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > File Share. In the Restore from File Backup window, click
Rollback to a point in time.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the file share backup whose files you want to restore. In the Ba ckup tab on the ribbon, click
Rollback to a point in time.

o Right-click the file share backup whose files you want to restore and select Restore > Rollback to a
p oint in time.

You can roll back the file share to a point in time by using a backup copy. Backup copies created in the
secondary repositories are represented in the Ba ckups > Disk (Copy) node in the inventory pane. If the
secondary repository is an object storage repository, backup copies created in it are represented in the
Ba ckups > Ob ject Storage (Copy) node in the inventory pane.

1692 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Object to Restore
At the File Shares step of the wizard, select the file share, whose files you want to roll back:

1. Click Ad d .

2. In the Ba ckups Browser window, select the file backup job and a file share in it, whose files you want to
roll back. Click OK.

3. In the File shares table, choose the file share to select a restore point to roll back to. Click P oint.

4. In the Select Restore Point window, select the restore point to which you want to roll back the files. To
select the required restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the right pane of the Restore
p oints window, select the date when the required restore point was created. The list of restore points
on the left pane displays restore points created on the selected date. Select the point to which you
want to roll back the files to.

In the Files in backup tree, you can see what folders and files are covered by the selected restore point
and the date when each of them was modified.

Click OK.

To quickly find a file share, you can use the search field at the top of the window. Enter a file share name or a
part of it in the search field and press [Enter].

To exclude the file share from the rollback process, select the file share in the table and click Remove.

1693 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Finish Working with Wizard
At the Summary step of the wizard, review the file share restore settings and click Finish.
Veeam Backup & Replication will restore the files to the specified point in time.

Restoring Specific Files and Folders


You can restore specific files and folders to the original or a new location. This option can be useful, for
example, if you need to get an older version of some files and folders from the backup.

When you restore specific files, you can extract file versions not only from the backup repository, but also from
the archive repository. For more information, see Restoring Backup Files from Archive Repository.

NOTE

Consider that from the archive repository you can restore files only. Restore of whole folders from t he
long-term repository is not supported.

Besides, you can restore multiple versions of the same file.

Before you restore specific files and folders, check prerequisites.

Before You Begin


Before you restore files and folders from the backup, consider the following:

• You can restore files and folders from a backup that has at least one created restore point, even if it is
incomplete.

1694 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The file share on which you plan to save restored files and folders must be added to the backup
infrastructure.

1695 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch File Restore Wizard
To launch the File Restore wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > File Share. In the Restore from File Backup window, click
Restore individual files and folders.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the file share backup whose files you want to restore. In the Ba ckup tab on the ribbon, click Files
a nd folders.

o Right-click the file share backup whose files you want to restore and select Restore > Files and
folders.

In this case, you will pass directly to the Backup Browser.

You can restore files and folders from a backup copy. Backup copies created in the secondary repositories
are represented in the Ba ckups > Disk (Copy) node in the inventory pane. If the secondary repository is an
object storage repository, backup copies created in it are represented in the Ba ckups > Ob ject Storage
( Copy) node in the inventory pane.

1696 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Object to Restore
At the Ba ckup step of the wizard, select the file share backup whose files you want to restore:

1. In the Ob ject to restore list, expand the necessary backup job.

2. Select the file share.

To quickly find a file share, you can use the search field at the bottom of the window.

1. Enter a file share name or a part of it in the search field.

2. Click the Sta rt search button on the right or press [Enter].

1697 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Verify Object Restore Settings
At the Summary step of the wizard, review selected restore object and click Browse to switch to the Backup
Browser step and select files and folders to restore.

1698 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Files and Folders to Restore
In the Ba ckup Browser, select files and folders to restore. Backup browser has three representations of restore
points. You can select one of the following options in the Restore Point group on the ribbon to display file
versions:

• La test — the Ba ckup Browser shows the latest versions of files and folders on the file share.

• All Time — the Ba ckup Browser shows all files and folders ever backed up by the backup job. This option
retrieves file versions stored both in the backup and archive repositories. This representation additionally
shows how many file versions of each file are stored in the backup and the date when the latest file
version was created.

After you select this option:

o If you restore a whole folder, you will be prompted to the Select Restore Point to Use step to select a
restore point to restore files from.

NOTE

Consider that during file-level restore you cannot restore whole folders from the archive
restore points. If the files are already moved to the archive repository, you have to restore them
one by one.

o If you restore a single file, you will be prompted to the Select File Version to Restore step to select a
file version to restore the file from.

• Selected — the Ba ckup Browser shows versions of files and folders backed up as of the certain restore
point. Select the restore point in the list on the right of the Selected option on the ribbon.

You can use the search field at the top of the working area to search for specific files and folders.

NOTE

To keep the operation of the Backup Server stable, the number of retrieved search result records is limited
to 1000. Therefore, if you work with backup folders that store large volumes of data, it is recommended to
narrow the search criteria to fit into the limitation.

You can restore files and folders to their original location or a new location.

Restoring Files to Original Location


To restore files and folders to the original location, in the Veeam Backup browser right-click a file or folder and
select one of the following commands:

• To overwrite the original file on the file share with the file restored from the backup, select Restore >
Overwrite.

• To save the file restored from the backup next to the original file, select Restore > Keep.
Veeam Backup & Replication will add the _RESTORED_YYYYMMDD_HHMMSS suffix to the original file
name and store the restored file in the same folder where the original file res ides.

1699 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you may use similar options under Restore in the ribbon.

Saving Files to New Location


To save files and folders to a new location, right-click the necessary file or folder and select Cop y to.
Alternatively, you may use the Cop y to option in the ribbon.

If you restore files and folders to a new location, you will be prompted to the Specify Destination for File
Restore step to specify a new destination.

1700 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Comparing Backup File and Folder Versions to Production
Objects
NOTE

The compare with production feature does not work if you select the All Time option at the Home tab of
the Ba ckup Browser.

You can compare backup versions of specific files and folders with their production sources. To compare them,
do the following:

1. Select a folder in the file tree in the left pane or folder or file in the right pane. You can use [Ctrl] to select
multiple objects in the right pane.

2. Right-click the selected objects and select Compare — Compare. Alternatively, click Compare with
P roduction on the ribbon.

After the comparison, files and folders will have the following comparison states in the Item State column:
changed , unchanged , deleted , comparing , or failed to compare. The states are updated when you turn off and
then turn on the comparison mode, and when you start restoring changes of files and folders. Note that when
comparing symbolic links, Veeam Backup & Replication compares attributes of the links, not the attributes of
files and folders which the symbolic link points to.

TIP

To show only changed files and folders (in the changed and deleted states), perform the compare
operation, right-click any area in the Veeam Backup browser and select Compare > Show changes only or
click Show Changes Only on the ribbon. To show all files and folders, click the Show changes only option
once again.

To switch off the comparison states, select an item in the comparison state and click Compare > Compare
or click Compare with Production on the ribbon. Note that if you switch off comparison for child files and
folders, comparison for parent folders will also be switched off.

Restoring Changed Files and Folders


After you run the compare with production session, you can restore the changed and deleted objects. To restore
them to the original location, in the Veeam Backup browser right-click a file or folder with Cha nged or Deleted
item state and select one of the following commands:

• To overwrite the original object on the object storage with the object restored from the backup, select
Restore changed and deleted > Overwrite.

• To save the object restored from the backup next to the original object, select Restore changed and
d eleted > Keep.
Veeam Backup & Replication will add the _RESTORED_YYYYMMDD_HHMMSS suffix to the original object
name and store the restored object in the same folder where the original object resides.

1701 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you may use similar options under Restore Changes in the ribbon.

You can view which attributes were changed for files and folders:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and select Compare > Compare attributes or click Compare
Attributes on the ribbon.

In the Compare Attributes window, Veeam Backup & Replication shows changed attributes. If you want to show
all attributes, click the Show unchanged attributes check box at the top right corner. Note that
Veeam Backup & Replication shows attributes maximum for 500 files and folders and shows attributes for the
selected files and folders, not for the nested files.

1702 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Restore Mode
The Restore Mode step is required if you use the All Time option at the Select Files and Folders to Restore step
and the selected folders have more than one restore point.

Choose to what point you want to restore files and folders:

• To restore the folder to the latest available restore point, select La test state.

• To select a specific restore point, select E a rlier restore point.

Choosing this option will open the Restore Point step.

1703 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Restore Point
The Restore Point step is required if you use the All Time option at the Select Files and Folders to Restore step,
the selected folders have more than one restore point, and you select the E a rlier restore point option at the
Restore Mode step.

At the Restore P oint step of the wizard, select the point in time to restore folders to. To select the required
restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the left pane of the Restore points
window, select the date when the required restore point was created. The list of restore points in the
right pane displays restore points created on the selected date. Select the point to which you want to
restore the files and folders.

In the Files in backup tree, you can see what folders and files are covered by the selected restore point and the
date when files and folders were modified.

1704 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Select File Version to Restore
The File Version step is required if you use the All Time option at the Select Files and Folders to Restore step
and the selected files have more than one file version.

If at the Backup Browser step you have selected to keep original objects, select one or more versions to restore.
You can restore files both from the backup repository and archive repository. To select several file versions, hold
[Ctrl] and select multiple records in the table. Restore of multiple file versions can be helpful, for example,
when you need to search for a specific version of the file, but you do not know for sure which one contains
required changes.

If at the Backup Browser step you have selected to overwrite original objects, you can select only one version to
restore.

1705 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Destination for File Restore
The Destination step is required if you choose the Cop y To option at the Select Files and Folders to Restore step.
Specify the destination where the restored files must be stored:

1. In the Restore files and folders to field, select a file share to which the files must be restored. All file
shares added to the inventory of Veeam Backup & Replication are available. If the required file share is
missing in the drop-down list, click Ad d and add a new file share to Veeam Backup & Replication.

For more information on how to add a new file share, see Adding File Share.

2. In the P a th to folder field, specify a path to the folder on the selected file share where files must be
restored.

To create a dedicated folder for restored files, click Browse. In the Select Folder window, select the target
location for the file share.

If you want to restore the file share to a new folder, click New Folder at the bottom of the window.
Confirm the new folder creation.

1706 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Finish Working with Wizard
At the Summary step of the wizard, review the file restore settings and click Finish.

Restoring Backup Files from Archive Repository


You can restore any file from the archive repository to the state of any file version stored in the archive.
Depending on the circumstances, such a restore can require different actions.

NOTE

Consider that from the archive repository you can restore files only. Restore of whole folders from the
long-term repository is not supported.

Regular Restore from Archive


To perform a regular restore from the archive repository when you have all required backup data stored both in
the backup repository and archive repository, follow the instructions given in Restoring Specific Files and
Folders. Consider that to restore data from the archive repository, you must select the All Time option for
selecting files and folders to restore.

Emergency Restore from Archive


There can be different situations where backups are not available in the backup repository: for example, backup
files are broken or deleted from the backup repository, backup configuration files are removed from the
configuration, archive repository is added into backup infrastructure of another backup server, or backup archive
is moved from one archive repository to another one. In these cases, you can restore specific files from the
backup archive.

1707 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
To restore files from the archive repository, for example, from an object storage:

1. If necessary, add the storage that keeps the required archive to the backup infrastructure as described in
section Adding Backup Repositories.

2. Rescan the added archive repository as described in section Rescanning Backup Repositories.

3. Download metadata for the archive backup:

a. Locate the required file backup archive under Ba ckups - Object Storage (Imported) node in the Home
view.

b. Right-click the file backup and select Download backup metadata.

c. From the drop-down list, select a backup repository to store the downloaded metadata of files
archive and click OK.

4. Restore files from the archive backup as described in section Restoring Specific Files and Folders.

1708 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Object Storage Data Recovery
You can restore data previously backed up with object storage backup jobs. You can restore the following data:

• Whole buckets or containers of object storage repositories.

• Objects of the certain restore point.

• Multiple objects versions.

Veeam Backup & Replication offers several recovery options for different recovery scenarios:

• Restore of the entire bucket allows you to restore a whole object storage bucket or container to one of the
restore points.

• Rollback to a point in time allows you to restore only changed objects to one of the restore points.

• Restore of individual objects allows you to select objects to restore to one of the restore points.

• Restoring Objects from Archive Repository allows you to select archived objects to restore to one of the
restore points.

Restoring Entire Bucket or Container


You can restore an entire object storage bucket or container from the backup to a specific restore point. That
can be helpful, for example, if your object storage data gets corrupted or unavailable and you need to restore
the entire bucket or container to the original or other location.

NOTE

If the Archive recent object versions option is selected (the copy mode is enabled) at the Archive
Repository step of the object storage backup job wizard, you may restore an entire bucket or container
from the archive repository. You can do that only for restore points that are stored in the archive repository
and have the Cop ied label in backup properties.

If this option is not selected (the copy mode is disabled), the restore of the entire bucket or container from
the archive repository is not supported.

Before you restore a bucket or container, check prerequisites.

Before You Begin


Before you restore the entire bucket or container, consider the following:

• You can restore the bucket or container from a backup that has at least one successfully created restore
point.

• The object storage where you plan to save the restored bucket or container must be added to the backup
infrastructure.

• Veeam Backup & Replication does not support restore of tags if you restore data from Microsoft Azure
Blob storage to Amazon S3 object storage and S3 compatible object storage.

• Veeam Backup & Replication does not support Instant recovery of data previously backed up with object
storage backup jobs.

1709 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• [For Microsoft Azure Blob storage] Veeam Backup & Replication does not support the following restore
scenarios if you change the Azure Storage access tier of blocks to the archive access tier:

o Restore data to the original location or to another location with the overwrite option.

o Restore individual objects or versions with the overwrite option.

• The target location where you want to restore the bucket or container has the following limitations:

o You can restore backups of Amazon S3 and s3 compatible only to a new bucket located either in
Amazon S3 or S3 compatible object storage.

o You can restore backups of Microsoft Azure Blob Storage only to a new container in Microsoft Azure
Blob Storage.

TIP

If you want to restore these objects, you must change the access tier to hot, cool or cold access tiers. If you
do not want to restore these objects, you need to remove them from your Azure container.

1710 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Bucket Restore Wizard
To launch the Bucket Restore wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > Ob ject Storage. In the Restore from Object Storage Backup
window, click Restore entire b uckets.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the buckets or containers that you want to restore. In the Ba ckup tab on the ribbon, click E ntire
Buck et.

o Right-click the the buckets or containers that you want to restore and select Restore entire bucket.

You can restore the bucket or container to the state as of a specific restore point by using a backup copy.
Backup copies created in the secondary repositories are represented in the Ba ckups > Disk ( Copy) node in
the inventory pane. If the secondary repository is an object storage repository, backup copies created in it
are represented in the Ba ckups > Ob ject Storage (Copy) node in the inventory pane.

1711 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Buckets to Restore
At the Buck ets step of the wizard, select the buckets or containers that you want to restore:

1. Click Ad d .

2. In the Ba ckups Browser window, select the object storage backup job and a bucket or container in it that
you want to restore. You can select multiple buckets or containers by holding [Ctrl] and clicking the
required buckets or containers. Click OK.

3. In the Buck ets table, choose the bucket or container to select a point to restore to. Click P oint.

4. In the Select Restore Point window, select the restore point to which you want to restore the bucket or
container. To select the required restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the left pane of the Select Restore
P oint window, select the date when the required restore point was created. The list of restore points
in the right pane displays restore points created on the selected date. Select the point to which you
want to restore the bucket or container.

In the Files in backup tree, you can see what prefixes and objects are covered by the selected restore point
and the date when each of them was modified.

Click OK.

To quickly find a bucket or container, you can use the search field at the top of the window. Enter a bucket or
container name or a part of it in the search field and press [Enter].

To exclude the bucket or container from the restore process, select the bucket or container in the table and click
Remove.

1712 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Destination for Bucket or Container Restore
At the Destination step of the wizard, specify the location where you want to restore the bucket or container.

• Select Orig inal location to restore data to the location where it resided originally. This type of restore is
only possible if the original device is connected to Veeam Backup & Replication and powered on.

• Select New b ucket to create a new bucket or container and restore the backed -up bucket or container
content to it. You can restore only a single bucket or container to a new bucket or container.

NOTE

The target location where you want to restore the bucket or container has the following limitations:

• You can restore backups of Amazon S3 and s3 compatible only to a new bucket located either
in Amazon S3 or S3 compatible object storage.
• You can restore backups of Microsoft Azure Blob Storage only to a new container in Microsoft
Azure Blob Storage.

• Select This location to restore data to another location:

a. In the This location field, select a location to restore objects to. You can select any object storage
added to the backup inventory. If the required location is missing in the drop -down list, click Ad d and
add a new location to Veeam Backup & Replication. For more information, see the Adding
Unstructured Data Source section.

b. In the P a th field, specify a path to the prefix in the selected location to restore objects to.

To select a specific prefix, click Browse. In the Select Folder window, select the target location for the
bucket or container content.

1713 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Create New Bucket or Container
The New Bucket step is available if you select the New b ucket option at the Destination step.

At the New Bucket step of the wizard, create a new bucket or container where you want to restore the bucket or
container.

1. From the Ob ject storage drop-down list, select an object storage where you want to create a new bucket
or container. If the required object storage is missing in the drop-down list, click Ad d and add a new object
storage to the Veeam Backup & Replication inventory. For more information, see the Adding Object
Storage section.

NOTE

The target bucket or container where you want to restore the data has the following limitations:

• You can restore backups of Amazon S3 and s3 compatible only to a new bucket located either
in Amazon S3 or S3 compatible object storage.
• You can restore backups of Microsoft Azure Blob Storage only to a new container in Microsoft
Azure Blob Storage.

2. In the Buck et name, specify the name for the bucket or container following bucket or container naming
rules for the selected object storage.

1714 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Restore Options
The Restore Options step is available if you select either the Original location option or the This location option
at the Destination step.

At the Restore Options step of the wizard, specify overwrite options in case the bucket or container with the
same name already exists in the target location:

• Sk ip restoring (keeps the existing object). Select this option if you do not want to overwrite the existing
objects with the restored objects.

• Rep lace older objects only ( use if a bucket was reverted to a snapshot) . Select this option if you want to
overwrite the existing objects only if they are older than the restored objects.

• Rep lace newer objects only (use to discard unwanted contents changes). Select this option if you want to
overwrite the existing objects only if the restored objects are older than the source objects.

• Restore anyway (overwrites existing objects). Select this option if you want to overwrite the existing
objects with the restored objects in all cases.

Select the Overwrite current b ucket a ttributes with a ttributes from the backup check box if you want the target
bucket or container to inherit attributes from the restored bucket or container.

NOTE

Note that you can select this check box only when restoring to original location.

1715 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review the bucket or container restore settings and click Finish.
Veeam Backup & Replication will restore the bucket or container to the specified location.

Rolling Back to a Point in Time


You can roll back changes made to data in object storage buckets or containers to a specific restore point that is
older than the current buckets or container state. This option can be useful, for example, when the original
bucket or container was attacked by ransomware. In this case you can roll back all the data that was changed by
the ransomware to the state before the attack.

Before you roll back the buckets or containers to a point in time, check prerequisites.

Before You Begin


Before you restore buckets or containers to a point in time, consider that you can restore buckets or containers
from a backup that has at least one successfully created restore point.

1716 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Bucket Rollback to a Point in Time Wizard
To launch the Bucket Rollback to a Point in Time wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > Ob ject Storage. In the Restore from Object Storage Backup
window, click Rollback buckets to a point in time.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the bucket or container that you want to restore. In the Ba ckup tab on the ribbon, click Rollback
Buck et.

o Right-click the object storage that you want to restore and select Rollback b ucket to a point in time.

You can roll back the bucket or container to the state as of a specific restore point by using a backup copy.
Backup copies created in the secondary repositories are represented in the Ba ckups > Disk ( Copy) node in
the inventory pane. If the secondary repository is an object storage repository, backup copies created in it
are represented in the Ba ckups > Ob ject Storage (Copy) node in the inventory pane.

1717 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Buckets to Restore
At the Buck ets step of the wizard, select the buckets or containers that you want to roll back:

1. Click Ad d .

2. In the Ba ckups Browser window, select the object storage backup job and a bucket or container in it that
you want to restore. You can select multiple buckets or containers by holding [Ctrl] and clicking the
required buckets or containers. Click OK.

3. In the File shares table, select the bucket or container to select a restore point to rollback to. Click P oint.

4. In the Select Restore Point window, choose the restore point to roll back the bucket or container to. To
select the required restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the left pane of the Restore points
window, select the date when the required restore point was created. The list of restore points on the
right pane displays restore points created on the selected date. Select the point to which you want to
roll back the bucket or container.

In the Files in backup tree, you can see what prefixes and objects are covered by the selected restore point
and the date when each of them was modified.

Click OK.

To quickly find a bucket or container, you can use the search field at the top of the window. Enter a bucket or
container name or a part of it in the search field and press [Enter].

To exclude the bucket or container from the restore process, select the bucket or container in the table and click
Remove.

1718 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Finish Working with Wizard
At the Summary step of the wizard, review the bucket or container rollback settings and click Finish.
Veeam Backup & Replication will roll back the bucket to the restore point.

Restoring Individual Objects or Versions


You can restore individual objects from the bucket or container backups to the original or a new location. This
option can be useful, for example, if you need to get an older version of some objects from the backup.

When you restore specific objects, you can extract object versions not only from the backup repository, but also
from the archive repository. For more information, see the Restoring Objects from Archive Repository section.

NOTE

Consider that from the archive repository you can restore objects only. Restore of prefixes from the long -
term repository is not supported.

Besides, you can restore multiple versions of the same object.

Before you restore specific objects, check prerequisites. Then use the Ob jects or Versions Restore wizard to
restore objects or their specific versions.

1. Launch the Objects or Versions Restore wizard.

2. Select an object to restore.

3. Verify object restore settings.

4. Select objects to restore.

5. Select a restore mode.

1719 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Select a restore point.

7. Select an object version to restore.

8. Specify the destination for object restore.

9. Finish working with the wizard.

Before You Begin


Before you restore objects from the backup, consider the following:

• You can restore objects from a backup that has at least one created restore point, even if it is incomplete.

• The object storage on which you plan to save restored objects must be added to the backup infrastructure.

1720 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Object Restore Wizard
To launch the Ob jects or Versions Restore wizard, do one of the following:

• In the Home tab on the ribbon, click Restore > Ob ject Storage. In the Restore from Object Storage Backup
window, click Restore individual objects or their specific versions.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and do one of the following:

o Click the bucket or container that you want to restore. In the Ba ckup tab on the ribbon, click Ob jects
or Versions.

o Right-click the object storage that you want to restore and select Restore individual objects or
versions.

You can restore objects from a backup copy. Backup copies created in the secondary repositories are
represented in the Ba ckups > Disk (Copy) node in the inventory pane. If the secondary repository is an
object storage repository, backup copies created in it are represented in the Ba ckups > Ob ject Storage
( Copy) node in the inventory pane.

1721 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Object to Restore
At the Ba ckup step of the wizard, select the bucket or container you want to restore:

1. In the Ob ject to restore list, expand the necessary backup job.

2. Select the bucket or container.

To quickly find a bucket or container, you can use the search field at the bottom of the window.

1. Enter a bucket or container name or a part of it in the search field.

2. Click the Sta rt search button on the right or press [Enter].

1722 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Verify Object Restore Settings
At the Summary step of the wizard, review the selected bucket or container and click Browse to switch to the
Backup Browser step and select objects to restore.

1723 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Objects to Restore
In the Ba ckup Browser, select objects and prefixes to restore. Backup browser has three representations of
restore points. You can select one of the following options in the Restore point group on the ribbon to display
object versions:

• La test — the Ba ckup Browser shows the latest versions of objects and prefixes in the bucket or container.

• All Time — the Ba ckup Browser shows all objects and prefixes ever backed up by the backup job. This
option retrieves object versions stored both in the backup and archive repositor ies. This representation
additionally shows how many object versions of each object are stored in the backup and the date when
the latest object version was created.

After you select this option:

o If you restore a whole prefix, you will be prompted to the Select Restore Mode step to select a restore
mode and restore point to restore objects from.

NOTE

Consider that during object-level restore you cannot restore whole prefixes from the archive
restore points. If objects and prefixes are already moved to the archive repository, you have to
restore only objects one by one.

o If you restore a single object, you will be prompted to the Select Object Version to Restore step to
select a object version to restore the object from.

• Selected — the Ba ckup Browser shows versions of objects and prefixes backed up as of the certain restore
point. Select the restore point in the list on the right of the Selected option on the ribbon.

You can use the search field at the top of the working area to search for specific objects and prefixes.

NOTE

To keep the operation of the Backup Server stable, the number of retrieved search result records is limited
to 1000. Therefore, if you work with backup prefixes that store large volumes of data, it is recommended
to narrow the search criteria to fit into the limitation.

You can restore objects and prefixes to their original location or a new location.

Restoring Objects and Prefixes to Original Location


To restore objects and prefixes to the original location, in the Veeam Backup browser right-click an object or
prefix and select one of the following commands:

• To overwrite the original object in the object storage with the object restored from the backup, select
Restore > Overwrite.

• To save the object restored from the backup next to the original object, select Restore > Keep.
Veeam Backup & Replication will add the _RESTORED_YYYYMMDD_HHMMSS suffix to the original object
name and store the restored object in the same prefix where the original object resides.

1724 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you may use similar options under Restore in the ribbon.

Saving Objects and Prefixes to New Location


To save objects and prefixes to a new location, right-click the necessary object or prefix and select Cop y
to. Alternatively, you may use the Cop y to option in the ribbon.

If you restore objects and prefixes to a new location, you will be prompted to the Specify Destination for Object
Restore step to specify a new destination.

Comparing Backup Object and Prefix Versions to Production


Objects and Prefixes
IMP ORTANT

Running the operations of the compare with production feature for backups of object storage requires
sending HEAD and GET requests to the storage. That may lead to additional costs.

1725 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The compare with production feature does not work if you select the All Time option at the Home tab of
the Ba ckup Browser.

You can compare backup versions of specific objects and prefixes with their production sources. To compare
them, do the following:

1. Select an object or prefix in the items tree in the left pane or object in the right pane. You can use [Ctrl] to
select multiple objects and prefixes in the right pane.

2. Click Compare with Production on the ribbon. Alternatively, you can right-click the necessary object or
prefix and select Compare > Compare.

After the comparison, objects will have the following comparison states in the Item State column: changed ,
unchanged , deleted , comparing , or failed to compare. The states are updated when you turn off and then turn
on the comparison mode, and when you start restoring changes of objects. Note that when comparing symbolic
links, Veeam Backup & Replication compares attributes of the links, not the attributes of objects which the
symbolic link points to.

TIP

Consider the following:

• To show only changed objects (in the changed and deleted states), perform the compare operation,
right-click any area in the Veeam Backup browser and select Compare > Show changes only or click
Show Changes Only on the ribbon.
• To switch off the comparison states, select an object in the comparison state and click Compare >
Compare or click Comp are with P roduction on the ribbon. Note that if you switch off comparison for
child objects, comparison for parent objects will also be switched off.

Restoring Changed Objects and Prefixes


After you filter the changed objects and prefixes, you can restore them. To restore changed and deleted objects
and prefixes to the original location, in the Veeam Backup browser right-click an object or prefix with Cha nged
or Deleted item state and select one of the following commands:

• To overwrite the original object or prefix on the object storage with the object restored from the backup,
select Restore changed and deleted > Overwrite.

• To save the object or prefix restored from the backup next to the original object, select Restore changed
a nd deleted > Keep.

Veeam Backup & Replication will add the _RESTORED_YYYYMMDD_HHMMSS suffix to the original object
and prefix name and store the restored object and prefix where the original object and prefix resides.

1726 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you may use similar options under the Restore changes group in the ribbon.

You can also compare attributes of the changed and deleted objects and prefixes against objects and prefixes in
the source object storage. To compare them, do the following:

1. Select a prefix in the items tree in the left pane or an object and the prefix in the right pane. You can use
[Ctrl] to select multiple objects and prefixes in the right pane.

2. Right-click one of the selected items and select Compare > Compare attributes or click Comp are
Attributes on the ribbon. Alternatively, you can right-click one of the selected items and select Compare >
Compare or click Comp are with P roduction on the ribbon.

In the Compare Attributes window, Veeam Backup & Replication shows changed attributes. If you want to show
all attributes, click the Show unchanged attributes check box at the top right corner. Note that
Veeam Backup & Replication shows attributes maximum for 500 objects and prefixes and shows attributes for
the selected objects, not for the nested objects.

1727 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Restore Mode
The Restore Mode step is required if you use the All Time option at the Select Objects to Restore step and the
selected prefixes have more than one restore point.

Choose to what point you want to restore prefixes:

• To restore the prefixes to the latest available restore point, select La test state.

• To select a specific restore point, select E a rlier restore point.

Choosing this option will open the Restore Point step.

1728 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Restore Point
The Restore Point step is required if you use the All Time option at the Select Objects to Restore step, the
selected prefixes have more than one restore point, and you select the E a rlier restore point option at the
Restore Mode step.

At the Restore P oint step of the wizard, select the point in time to restore prefixes to. To select the required
restore point, do one of the following:

o Use the Restore point slider.

o Click the date link under the Restore point slider. In the calendar in the left pane of the Restore points
window, select the date when the required restore point was created. The list of restore points in the
right pane displays restore points created on the selected date. Select the point to which you want to
restore the objects and prefixes.

In the Files in backup tree, you can see what objects and prefixes are covered by the selected restore point and
the date when object and prefixes were modified.

1729 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Select Object Version to Restore
The Ob ject Version step is required if you use the All Time option at the Select Objects to Restore step and the
selected objects have more than one object version.

Select one or more versions to restore. You can restore objects both from the backup repository and archive
repository. To select several object versions, hold [Ctrl] and select multiple records in the table. Restore of
multiple object versions can be helpful, for example, when you need to search for a specific version of the
object, but you do not know for sure which one contains required changes.

1730 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Destination for Object Restore
The Destination step is required if you choose the Cop y To option at the Select Objects to Restore step. Specify
the destination where the restored objects must be stored:

1. In the Restore to field, select an unstructured data storage to which the objects must be restored. All
unstructured data sources added to the inventory of Veeam Backup & Replication are available. If the
required object storage is missing in the drop-down list, click Ad d and add the necessary object storage to
Veeam Backup & Replication, as described in the Adding Unstructured Data Source section.

2. In the P a th field, specify a bucket or container in the selected object storage or a path to the prefix in the
selected object storage where objects must be restored.

To select a dedicated prefix for restored objects, click Browse. In the Select Folder window, select the
target location.

1731 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Finish Working with Wizard
At the Summary step of the wizard, review the object restore settings and click Finish.

Restoring Objects from Archive Repository


You can restore any object from the archive repository to the state of any object version stored in the archive.
Depending on the circumstances, such a restore can require different actions.

NOTE

Consider that from the archive repository you can restore objects only. Restore of whole prefixes from the
long-term repository is not supported.

Regular Restore from Archive


To perform a regular restore from the archive repository when you have all required backup data stored both in
the backup repository and archive repository, follow the instructions given in the Restoring Individual Objects or
Versions section. Consider that to restore data from the archive repository, you must select the All Time option
for selecting objects to restore.

Emergency Restore from Archive


There can be different situations where backups are not available in the backup repository: for example, backed -
up objects are corrupted or deleted from the backup repository, backup configuration files are removed from
the configuration, archive repository is added into backup infrastructure of another backup server, or backup
archive is moved from one archive repository to another one. In these cases, you can restore specific objects
from the backup archive.

1732 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To restore objects from the archive repository, for example, from an object storage:

1. If necessary, add the storage that keeps the required archive to the backup infrastructure as described in
section Adding Backup Repositories.

2. Rescan the added archive repository as described in section Rescanning Backup Repositories.

3. Download metadata for the archive backup:

a. Locate the required object backup archive under Ba ck ups - Object Storage (Imported) node in the
Home view.

b. Right-click the object backup and select Download backup metadata.

1733 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. From the drop-down list, select a backup repository to store the downloaded metadata of objects
archive and click OK.

4. Restore objects from the archive backup as described in the Restoring Individual Objects or Versions
section.

1734 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
VeeamZIP
With Veeam Backup & Replication, you can quickly perform backup of one or several VMs with VeeamZIP.

VeeamZIP is similar to a full VM backup. The VeeamZIP job always produces a full backup file (VBK) that acts as
an independent restore point. You can store the backup file in a backup repository, in a local folder on the
backup server or in a network share.

IMP ORTANT

Consider the following:

• Veeam Backup & Replication does not enforce backup repository throttling rules during VeeamZIP
jobs.
• You cannot use a Veeam Cloud Connect repository as a target for VeeamZIP jobs.

Backup files produced with VeeamZIP jobs are displayed in the Home view, under the Ba ckups > Disk (Exported)
node.

When you perform backup with VeeamZIP, you do not have to configure a backup job and schedule it. Instead,
you can start the backup process for selected VMs immediately. This type of a backup requires minimum
settings — you should only select the backup destination, choose the necessary compression level and enable or
disable encryption and application-aware processing if necessary. For more information, see Creating VeeamZIP
Backups.

To view the progress or results of the VeeamZIP job session, you can use the History view. For more information,
see Viewing Real-Time Statistics.

To restore VM data from VeeamZIP backups, you can right-click it in the Home view and select the necessary
restore option. You can also double-click the necessary VeeamZIP backup file on the machine where
Veeam Backup & Replication is installed.

1735 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating VeeamZIP Backups
You can quickly back up running and powered off VMs with VeeamZIP. VeeamZIP can be helpful if you want to
create an ad-hoc backup for VMs, archive VMs before decommissioning and so on. You can create VeeamZIP
backups for one or more VMs.

TIP

Veeam Backup & Replication keeps settings of the latest VeeamZIP task. To quickly create VeeamZIP
backups with the same settings and store backups in the same location, right-click the necessary VM and
select VeeamZIP to.

To create VeeamZIP backups:

1. Open the Inventory view. In the infrastructure tree, select a host or VM container (Hyper-V host, cluster,
SCVMM, SCVMM tag, SCVMM host group, VM group, or volume) in which the VMs that you want to back
up reside.

2. In the working area, select the VMs and click Veea mZIP > VeeamZIP on the ribbon or right-click the VMs
and select VeeamZIP.

To quickly find the necessary VMs, type the VM name or a part of it in the search field at the top of the
working area and click the Sta rt search button on the right or press [Enter] on the keyboard.

3. In the opened VeeamZIP <N> VM window:

a. In the Destination section, specify a location in which you want to store VeeamZIP backups.

▪ To store VeeamZIP backups in a backup repository, select Ba ckup repository and choose the
necessary backup repository from the list. In this case, VeeamZIP backups will be saved to the
VeeamZIP subfolder of the folder where the backup repository stores backups. You can check
this folder at the Configure Backup Repository Settings step of the backup repository wizard.

1736 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ To store VeeamZIP backups in a local folder on the backup server, select Local or shared folder,
click Browse on the right and select a folder in which VeeamZIP backups must be stored.

▪ To store VeeamZIP backups in a shared folder, select Loca l or shared folder and type in the UNC
name of the shared folder in the field below. Keep in mind that the UNC name always starts with
two back slashes (\\).

If the shared folder requires authentication, select the necessary credentials from the
Credentials list. If you have not set up credentials beforehand, click the Ma nage accounts link or
click Ad d on the right to add necessary credentials. For more information, see Managing
Credentials.

b. If you want to specify retention settings for the created VeeamZIP backups, select the Delete this
b a ckup automatically check box. From the drop-down list, select the retention period. The VeeamZIP
backup file will be removed at 12:00:00 AM on the next day after the retention period ends.

[For hardened repository] Veeam Backup & Replication sets an immutability period for backup files
with retention period as equal to the longest of these periods. For more information, see Retention
Scenarios.

If you do not want to delete VeeamZIP backups, leave the Delete this backup automatically check box
unselected.

c. To encrypt VeeamZIP backups, select the E na ble backup file encryption check box. From the
P a ssword list, select a password that you want to use for encryption. If you have not created a
password beforehand, click Ad d or use the Ma nage passwords link to specify a new password. For
more information, see Managing Passwords for Data Encryption.

d. From the Compression level list, select a compression level for created backups.

e. By default, Veeam Backup & Replication uses native Microsoft Hyper-V quiescing mechanisms to
create a transactionally consistent image of VMs. You can disable VM quiescence. To do this, select
the Disable guest quiescence check box. In this case, Veeam Backup & Replication will create a crash-
consistent VM backup.

1737 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
f. Click OK. The VeeamZIP task will start immediately. Veeam Backup & Replication will create a full
backup file (VBK) and store it in the specified location. The VM name, date and time of the file
creation are appended to the file name so you can easily find the necessary backups afterwards.

4. As the job runs, you can track the job performance in the real-time mode. To see the job results once it
completes, open the History view, expand the Job s node and click Ba ckup. Then double-click the job
session in the list.

1738 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing VeeamZIP Backups
Managing for VeeamZIP backups is practically the same as for regular backups. You can view backup properties,
copy, move or delete backups from disk. For more information, see the following sections:

• Viewing Backup Properties

• Moving Backups

• Copying Backups

• Deleting Backups from Disk

You can restore your data directly from the VeeamZIP backups back to production servers. VeeamZIP data
recovery does not differ from that of a standard backup data recovery and can be performed by using any of the
following methods:

• Perform Instant Recovery to VMware vSphere.

• Perform Instant Recovery to Microsoft Hyper-V.

• Restore Entire VM.

• Restore VM Files.

• Restore Guest Files.

• Restore to Amazon EC2.

• Restore to Microsoft Azure.

• Restore to Google CE.

1739 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy
The main backup purpose is to protect your data against disasters and virtual or physical machine failures.
However, having just one backup does not provide the necessary level of safety. The primary backup may get
destroyed together with production data, and you will have no backups from which you can restore data.

To build a successful data protection and disaster recovery plan, it is recommended that you follow the 3-2-1
rule:

• 3: You must have at least three copies of your data: the original production data and two backups.

• 2: You must use at least two different types of media to store the copies of your data, for example, local
disk and cloud.

• 1: You must keep at least one backup off-site, for example, in the cloud or in a remote site.

Thus, you must have at least two backups and they must be in different locations. If a disaster takes out your
production data and local backup, you can still recover from your off-site backup.

To help you adopt the 3-2-1 rule, Veeam Backup & Replication offers backup copy capabilities. Backup copy
allows you to create several instances of the same backup data in different locations, whether on-site or off-
site. Backup copies have the same format as those created by backup jobs and you can recover your data from
them when you need it.

Backup copy is a job-driven process. Veeam Backup & Replication fully automates the backup copy process and
lets you specify retention settings to maintain the desired number of restore points, as well as full backups for
archival purposes.

1740 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
About Backup Copy
With backup copy, you can create several instances of the same backup file 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. The backup copy file has the same format as the primary
backup, so you can restore necessary data directly from it in case of a disaster.

Veeam Backup & Replication supports backup copy for the following types of backups:

• Backups of VMware vSphere or VMware Cloud Director virtual machines created by


Veeam Backup & Replication

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

• Backups of virtual and physical machines created by Veeam Agent for Microsoft Windows, Veeam Agent
for Linux, Veeam Agent for Mac, Veeam Agent for Oracle Solaris or Veeam Agent for IBM AIX

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

• Backups of Oracle, SAP HANA and Microsoft SQL Server databases created by Veeam Plug-ins for
Enterprise Applications

• Backups stored in an HPE StoreOnce backup repository

• File share backups created by Veeam Backup & Replication

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure

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

• Backups created by Veeam Backup for RHV

• Backups exported by K10 policies

IMP ORTANT

Consider the following for copying backups created by Veeam Backup for AWS, Veeam Backup for
Microsoft Azure or Veeam Backup for Google Cloud:

• You can copy such backups from external repositories but not to them.
• When copying backups from external repositories, consider that there can be a situation when new
restore points were not copied. In this case, make sure the source chain for the backup copy job was
not recreated. If it was recreated (all restore points have been deleted and created anew), you must
create a new backup copy job with a new chain of backups.

When the backup copying process starts, Veeam Backup & Replication accesses backup files in the source
backup repository, retrieves data blocks for a specific machine from the backup file, copies them to the target
backup repository, and composes copied blocks into a backup file in the target backup repository. The backup
copying process does not affect virtual and physical infrastructure resources, does not require creation of
additional VM checkpoints or VSS snapshots and does not produce load on machines whose backups are copied.

Backup copy is a job-driven process. To copy backups, you need to configure backup copy jobs. The backup copy
job defines when, what, how and where to copy. For more information on how to create backup copy jobs, see
Creating Backup Copy Jobs for VMs and Physical Machines. Note that to copy file share backups, you need to
configure a file backup job, not the backup copy job. For more information, see Creating File Backup Jobs.

1741 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

You can not use backups created by a backup copy job as a source for another backup copy job.

1742 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
How Backup Copy Works
Veeam Backup & Replication performs backup copy in the following way:

1. [For VM backup copy jobs only] Veeam Backup & Replication connects to Microsoft Hyper-V hosts to
gather information about VMs whose restore points you want to copy.

2. For backup copying process, Veeam Backup & Replication starts two Veeam Data Movers — source Veeam
Data Mover and target Veeam Data Mover. Veeam Data Movers location depends on the backup repository
type and data transport path. For more information, see Backup Copy Architecture.

3. The first backup copy run always produces a full backup file. Veeam Backup & Replication copies data
blocks that are necessary to build a full backup of a machine as of the most recent state.

Veeam Backup & Replication can copy data blocks from one or more backup files in the backup chain in the
source backup repository.

o If the backup chain is created in the reverse incremental backup method, Veeam Backup & Replication
copies data blocks of the latest full backup.

o If the backup chain is created in the forward or forever forward incremental backup method,
Veeam Backup & Replication copies data blocks from the first full backup and a set of incremental
backups.

To minimize the amount of traffic going over the network, you can set Veeam Backup & Replication to use
WAN accelerator, data compression and deduplication technologies.

4. Veeam Backup & Replication transfers copied data to the target backup repository and writes all copied
data blocks to the full backup file.

o New backup copy jobs always work in per-machine mode. In per-machine mode, data of every
machine in the job is stored to separate backup files in the target backup repository.

o Backup copy jobs created in the previous versions of Veeam Backup & Replication continue to create
backup files in the specified formats: single-file backups if the Use per-machine backup files option
was disabled or per-machine backups with single metadata file if the option was enabled. You can
upgrade the backup chain format as described in section Upgrading Backup Chain Formats.

5. During every next backup copy run, when a new restore point appears in the source backup repository,
Veeam Backup & Replication copies incremental changes from this most recent restore point and transfers
them to the target backup repository. Veeam Backup & Replication writes the copied data blocks to the
incremental backup file in the target backup repository, that is, Veeam Backup & Replication creates a new
restore point in the forever forward incremental backup chain.

To retain the desired number of restore points, Veeam Backup & Replication uses a retention policy. For
more information, see Short-Term Retention Policy.

1743 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you want to store some restore points for longer periods (for weeks, months or years) and enable long -
term retention policy (GFS retention policy), Veeam Backup & Replication creates a forward incremental
backup chain. For more information on GFS retention policy, see Long-Term Retention Policy (GFS).

In some cases, the source backup job and backup copy job may overlap. This situation can occur if the source
backup job needs to transform the source backup chain.

If a specific task in the backup copy job locks the source backup chain to read data from it, and the source
backup job that needs to write data to this backup chain starts at this moment (for example, for reverse
incremental backup), the task in the backup copy job is put on hold. The backup copy job can continue
processing other tasks that use other sources (for example, backup files created by other backup jobs). After the
source backup job releases the backup chain, the backup copy job resumes processing machines in this backup
chain.

1744 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Architecture
To transport data from the source backup repository to the target backup repository, the backup copy job uses
one of the following paths:

• Direct transport path

• Transport path over WAN accelerators

Direct Transport Path


Veeam Backup & Replication transports data directly from the source backup repository to the target backup
repository. This type of data transport is recommended for copying backups to on-site backup repositories or
off-site backup repositories over fast connections.

When Veeam Backup & Replication transports data over the direct data path, it uses Veeam Data Movers on the
following backup infrastructure components:

• Microsoft Windows and Linux repositories. Veeam Backup & Replication uses the source Veeam Data
Mover on the source backup repository and target Veeam Data Mover on the target backup repository.

• Sha red folder backup repository. If you have instructed Veeam Backup & Replication to automatically
select the gateway server, Veeam Backup & Replication will use Veeam Data Movers deployed on mount
servers associated with backup repositories. In case mount servers cannot be used for some reason,
Veeam Backup & Replication will fail over to the backup server.

If you have explicitly defined the gateway server, Veeam Backup & Replication will use the source Veeam
Data Mover on the gateway server in the source site and target Veeam Data Mover on the gateway server
on the target site.

1745 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Transport Path over WAN Accelerators
Veeam Backup & Replication transports data through a pair of WAN accelerators: one deployed on the source
side and the other one deployed on the target side. WAN accelerators remove redundant blocks before
transferring data and thus significantly reduce the amount of traffic going over the network. This type of data
transport is recommended for copying backups off-site over slow connections or WAN.

IMP ORTANT

The WAN acceleration technology is included in the Veeam Universal License. When using a legacy socket -
based license, the Enterprise Plus edition is required. For more information, see WAN Acceleration.

When Veeam Backup & Replication transports data using WAN accelerators, it uses Veeam Data Movers on the
following backup infrastructure components:

• Microsoft Windows and Linux repositories. Veeam Backup & Replication uses the source Veeam Data
Mover on the source backup repository and target Veeam Data Mover on the target backup repository.

• Sha red folder backup repository. If you have instructed Veeam Backup & Replication to automatically
select the gateway server, Veeam Backup & Replication will use Veeam Data Mover deployed on the
source and target WAN accelerator. If you have explicitly defined the gateway server,
Veeam Backup & Replication will use the source Veeam Data Mover on the gateway server in the source
site and target Veeam Data Mover on the gateway server on the target site.

1746 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Modes
Veeam Backup & Replication offers two backup copy modes:

• Immediate copy
In the immediate copy mode, Veeam Backup & Replication copies restore points as soon as they appear in
a source backup repository. Veeam Backup & Replication copies only restore points created by source
backup jobs (backup jobs that you select when configuring a backup copy job).
Veeam Backup & Replication can also copy transaction log backups if you enable this capability in job
settings.

The immediate copy mode is supported for the following backup types:

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

o Backups created by Veeam Agent for Microsoft Windows, Veeam Agent for Linux or Veeam Ag ent for
Mac operating in the managed mode

o Backups created by Veeam Plug-ins for Enterprise Applications (Oracle RMAN, SAP HANA, SAP on
Oracle)

• P eriodic copy

In the periodic copy mode, Veeam Backup & Replication copies the latest source restore point according to
schedule specified in backup copy job settings. Veeam Backup & Replication copies only restore points
created by source backup jobs (backup jobs that you select when configuring a backup copy job).

The periodic copy mode is supported for the following backup types:

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

o Backups created by Veeam Agent for Microsoft Windows, Veeam Agent for Linux or Veeam Agent for
Mac operating in the standalone or managed mode

For the managed mode, backups created by both backup jobs managed by the backup server and jobs
managed by Veeam Agent are supported.

o Backups created by Veeam Agent for Oracle Solaris

o Backups created by Veeam Backup for Nutanix AHV

o Backups created by Veeam Backup for AWS

o Backups created by Veeam Backup for Microsoft Azure

o Backups created by Google Cloud Platform

o Backups exported by K10 policies

NOTE

Periodic backup copy jobs created in Veeam Backup & Replication 11 or earlier became legacy periodic
backup copy jobs in Veeam Backup & Replication 12. Legacy periodic backup copy jobs are fully operational,
but you can only edit them and cannot create new ones. You can upgrade backup files of a legacy periodic
backup copy job to the per-machine backup files using mapping. For more information, see Upgrading
Backup Chain Formats.

1747 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Changing Backup Copy Modes
Veeam Backup & Replication allows you to change the selected backup copy mode by editing backup copy job
settings.

IMP ORTANT

The periodic copy mode does not support processing of transaction log backups. Processing of transaction
log backups must be turned off before changing the immediate copy mode to the periodic copy mode.

If you want to change the selected backup copy mode for a backup copy job created in earlier versions of
Veeam Backup & Replication, it must have the per-machine backup with separate metadata files format. If a
backup copy job has the per-machine backup with single metadata file format, you must upgrade its backup
chain format to per-machine with separate metadata files or detach backups to start a new backup chain. For
more information, see Upgrading Backup Chain Formats.

1748 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Intervals
A backup copy interval is a time span in which a backup copy job must copy a restore point from the source
backup repository to the target backup repository.

IMP ORTANT

There are no more backup copy intervals in new backup copy jobs. You can use backup copy intervals only
in backup copy jobs created in Veeam Backup & Replication 11 or earlier.

NOTE

Veeam Backup & Replication uses backup copy intervals only in the periodic copy mode.

The backup copy interval affects the restore point selection process. For more information, see Restore Point
Selection.

At the beginning of a new interval, Veeam Backup & Replication checks if a new restore point is available in the
source backup repository:

• If a new restore point is found, the backup copy job starts the synchronization process and copies the
latest restore point to the target backup repository.

• If a new restore point is not found or is locked by the source backup job, the backup copy job enters the
Idle state.

By default, the backup copy interval is set to 1 day. You can change this interval when configuring a backup copy
job and set the interval in minutes or hours. Note that if you specify a too short backup copy interval or change
the interval, some issues can occur. For details, see Issues with Backup Copy Intervals.

Minutely and Hourly Backup Copy Intervals


The first minutely and hourly intervals start when the backup copy job runs for the first time. Each subsequent
backup copy interval starts after the period that you specified in the backup copy job settings.

For example, if you set the backup copy interval to 4 hours and start the backup copy job at 12:00 AM,
Veeam Backup & Replication will start new backup copy intervals at 12:00 AM, 4:00 AM, 8:00 AM and so on.

Daily Backup Copy Intervals


The daily backup intervals start every day at the time specified in the backup copy job settings.

For example, if you set the backup copy interval to 1 day and instruct Veeam Backup & Replication to start new
intervals at 12:00 PM, Veeam Backup & Replication will start new backup copy intervals at 12:00 PM daily.

In some cases, the start time of the backup copy job and backup copy interval may differ.

1749 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
For example, you configure a backup copy job and set the start time of the backup copy interval to 12:00 PM.
You also specify that the job must start right after the wizard is closed, and you close the wizard at 12:00 AM. In
this case, the first backup copy interval will start immediately and will run for a shorter period of time — for 12
hours instead of one day. All subsequent backup copy intervals will start as defined by back up copy job
schedule.

Issues with Backup Copy Intervals


Being a scheduled activity, the backup copy job may fail to run as expected. Veeam Backup & Replication
automatically handles some issues that can occur with the backup copy job.

Short Backup Copy Intervals


In some cases, Veeam Backup & Replication may fail to transport the restore point within the backup copy
interval of the backup copy job. This can happen, for example, if the backup copy interval is too short and is not
sufficient for the amount of data to be copied.

Veeam Backup & Replication handles this situation differently for the first and subsequent backup copy
intervals.

• The first backup copy interval always produces a full backup file — the starting point in the backup chain.
If Veeam Backup & Replication fails to copy data for the full backup file during the first backup copy
interval, it marks the job session as finished with the Warning status. During the next backup copy
interval, Veeam Backup & Replication attempts to copy data for the full backup file in the following
manner:

a. When a new backup copy interval begins, the restore point that was previously copied no longer
corresponds to the restore point selection rules. That is, the time of the restore point creation falls
out of the search scope. For this reason, Veeam Backup & Replication waits for a new restore point to
appear in the source backup repository.

b. When a new restore point appears in the source backup repository, Veeam Backup & Replication
detects what data blocks still need to be copied to make up a full backup file in the target backup
repository, and copies these data blocks.

This process continues until there is a full backup file in the target backup repository.

• At subsequent backup copy intervals, Veeam Backup & Replication copies incremental restore points. If
Veeam Backup & Replication fails to transport an incremental restore point, it marks the synchronization
task as failed. Veeam Backup & Replication waits for the expiration of the backup copy interval; after that,
Veeam Backup & Replication marks the job session as finished with the Error status.

Veeam Backup & Replication does not mark the backup copy job session with the Error status if the source
backup job has not started during the backup copy interval of the backup copy job (that is, the backup copy job
has nothing to copy to the target backup repository).

Change of the Backup Copy Interval Start Time


If you have selected to run a backup copy job with a daily backup copy interval, you must define the start time
of the backup copy interval. However, you may want to change the start time afterwards. After the start time
change, Veeam Backup & Replication behaves in the following manner:

1. Veeam Backup & Replication finishes the current backup copy interval running according to the 'old' start
time value as usual.

1750 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. After the current backup copy interval is over, Veeam Backup & Replication immediately starts the backup
copy interval, not waiting for the 'new' start time point to come. At that, Veeam Backup & Replication
“stretches” the started interval: the interval lasts for the time remaining till the new start time plus the
time of the backup copy interval itself.

3. All subsequent backup copy intervals are created and started in a regular manner by the new schedule.

For example, when you first created a backup copy job, you set a daily backup copy interval with the start time
at 8 AM. After that, you changed the start time to 10 AM. In this case, Veeam Backup & Replication will first
finish the backup copy interval that is currently running — that is, the backup copy interval that was started at 8
AM — as usual. After that, it will immediately start a new backup copy interval. This interval will run for 26 hours
— from 8 AM of the current day until 10 AM of the next day. All subsequent backup copy intervals will be
started at 10 AM every day.

The first backup copy interval that is run after the start time change is typically longer than a regular one. This
happens because of the backup copy interval “stretch” mentioned above. To start the synchronization process
right away, you can use the Sy nc Now option after you change the start time value. In this case,
Veeam Backup & Replication will behave in the following manner:

1. When you start the synchronization process manually, Veeam Backup & Replication forcibly finishes the
current backup copy interval and begins a new backup copy interval according to the new start time value.
This backup copy interval lasts until a new backup copy interval by the new schedule must be started.

2. All subsequent backup copy intervals are created and started in a regular manner.

As a result, the first backup copy interval after the start time change will begin immediately.

For example, when you first created a backup copy job, you set a daily backup copy interval with the start time
at 8 AM. After that, you changed the start time to 10 AM. On the start time change, you started the manual
synchronization process at 1 PM. In this case, Veeam Backup & Replication will finish the current backup copy
interval — that is, the backup copy interval that was started at 8 AM — immediately at 1 PM. After that, it will
start a new backup copy interval. This interval will run for 21 hours — from 1 PM of the current day until 10 AM
of the next day. All subsequent backup copy intervals will be started at 10 AM every day.

1751 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore Point Selection
Veeam Backup & Replication always copies the most recent restore points, even if a backup copy job runs for the
first time and source backup repositories already contain chains of restore points.

In the immediate copy mode, backup copy job copies the recent complete restore point created by a source
backup job on the first run. On the next runs, Veeam Backup & Replication copies the oldest source restore
points until there are no restore points left.

In the periodic copy mode, backup copy job starts according to schedule. Backup copy job copies the recent
complete restore point created by a source backup job on the first run. On the next runs backup copy job
continues to copy the recent complete restore points.

If there are no restore points considered as recent, Veeam Backup & Replication does not copy data from source
backup repositories. Instead, it waits for new restore points to appear. Only after that,
Veeam Backup & Replication copies the most recent data blocks to the target repository.

In the periodic copy mode, you can also specify the search scope for restore points. For more information, see
Select Machines to Process.

Limitations for Restore Points Selection


The following limitations apply when Veeam Backup & Replication selects restore points that must be copied to
the target repository:

• Veeam Backup & Replication does not copy restore points from the target backup repository.

• Veeam Backup & Replication does not copy restore points from imported backups.

• Veeam Backup & Replication does not copy restore points that have already been copied by the same
backup copy job to the target backup repository.

• Veeam Backup & Replication does not copy incomplete restore points.

• Veeam Backup & Replication does not copy restore points that are locked by the backup transformation
process (merge, transform).

• A backup copy job does not copy a restore point if its data block size differs from the data block size of
restore points that the job has already copied to the target backup repository. To copy restore points with
the changed block size, you need to create active full backups. For details, see Change Storage
Optimization Settings for Backup Copy Job.

For example, if you have changed the block size for restore points in the source backup job (the Storage
op timization option in the Storage Settings), Veeam Backup & Replication will not copy newly created
restore points and will display the Restore point is located in backup file with different block size
message.

1752 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Transformation Processes
Veeam Backup & Replication can perform additional transformations in the target backup repository after the
backup copying task or at the end of the backup copy interval. Transformation processes are the following:

• Ba ckup chain transformation

When a new restore point is copied to the target backup repository, Veeam Backup & Replication checks
the retention policy settings for the backup copy job. If the limit in restore points is exceeded,
Veeam Backup & Replication does the following:

o If only short-term retention policy is enabled, Veeam Backup & Replication transforms the backup
chain to make room for a new restore point. For more information, see Short-Term Retention Policy.

o If long-term retention policy is enabled, Veeam Backup & Replication removes unnecessary restore
points. Veeam Backup & Replication removes restore points in a way similar to the one described in
section Forward Incremental Backup Retention Policy.

For more information on retention policies, see Retention Policy for Backup Copy Jobs.

After the transformation process, Veeam Backup & Replication can perform additional operations: remove
data of deleted workloads from the backup chain and compact a full backup file.

• Removal of deleted items

In the backup copy job settings, you can specify after which period you want to delete data of deleted
workloads from backups created by backup copy jobs. After the period ends, Veeam Backup & Replication
checks the list of workloads included in the job and removes data of deleted workloads from the backup
chain in the target backup repository. For more information on how data is deleted and which limitations
apply, see Deleted Items Retention. For more information on how to configure the deleted items
retention, see Specifying Advanced Settings.

• Full backup file compact

In the backup copy job settings, you can select to periodically comp act a full backup file to reduce its size
and increase the speed of read and write operations. For more information, see Compact of Full Backup
File.

NOTE

If backup copy job processes the per-machine backup files, transformation processes will be performed for
each object individually.

1753 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Window
A backup copy window is a period of time when a backup copy job is allowed to transport data between source
and target repositories.

By default, the backup copy window is configured to allow data transfer at any time. If you do not want the
backup copy job to overlap the production hours, you can reduce the backup copy window and specify
"prohibited" hours.

During the prohibited hours Veeam Backup & Replication cannot transfer data between source and target
repositories. Other aspects of how Veeam Backup & Replication behaves during the prohibited hours and backup
copy window depend on the selected backup copy mode. For more information, see Backup Copy Window and
Prohibited Hours in Immediate Copy Mode and Backup Copy Window and Prohibited Hours in Periodic Copy
Mode.

NOTE

During the prohibited hours, Veeam Backup & Replication stops only data transferring operations.
Transformation processes in the target repository are still performed. For more information, see
Transformation Processes.

Backup Copy Window and Prohibited Hours in Immediate Copy


Mode
When the prohibited hours start, Veeam Backup & Replication stops backup copy job sessions during which data
transfer was not finished and assigns Failed to the session statuses. During the prohibited hours,
Veeam Backup & Replication does not start new backup copy job sessions.

When the backup copy window starts, Veeam Backup & Replication transfers all restore points that were not
transferred and creates as many incremental backup files as were omitted.

Backup Copy Window and Prohibited Hours in Periodic Copy


Mode
Backup copy job can not start during prohibited hours. If a prohibited time interval starts and backup copy job is
still processing, it will cause backup copy job to stop.

1754 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Retention Policy for Backup Copy Jobs
The retention policy of a backup copy job defines for how long Veeam Backup & Replication must retain copied
restore points in the target backup repository. The retention policy of a backup copy job does not depend on
retention policy of the source backup job. The backup copy job has its own retention policy settings.

Veeam Backup & Replication offers two retention policy schemes for backup copy jobs:

• Short-Term Retention Policy

• GFS Retention Policy (Weekly, Monthly, Yearly)

Also, there is a separate retention policy for machines that has been removed from the infrastructure. For
details, see Deleted Items Retention.

Short-Term Retention Policy


The short-term retention policy allows to retain restore points created by backup copy jobs for a specified
number of days or until the number of restore points reaches the specified number in the retention settings.

During the first backup copy session, Veeam Backup & Replication creates the first restore point — a full backup.
The next backup copy sessions add incremental backups to the backup chain. As a result, the regular backup
cycle produces a chain of a full backup and set of incremental backups in the target backup repository. When the
retention policy is exceeded, Veeam Backup & Replication removes the earliest restore points from backup
chains in the target backup repositories.

Since Veeam Backup & Replication creates forever forward incremental backup chains while backup copy jobs
run, Veeam Backup & Replication applies the forever forward incremental retention policy to remove restore
points and maintain the desired number of restore points.

When configuring short-term retention policy settings for a backup copy job, you have two options:

• Specify the number of restore points.


Veeam Backup & Replication keeps the last N restore points, where N is the number of restore points that
you specify in the settings. The minimum number that you can specify is 2.

• Specify the number of days.

Veeam Backup & Replication keeps restore points created during the last N days, where N is the number of
days that you specify in the settings.

Consider the following for the daily retention policy:

o The minimum number of retained restore points is 3. This number does not depend on the number of
days set in the retention policy. For example, the retention policy is set to 5 days. You launch the job
after it was stopped for 10 days. Normally, Veeam Backup & Replication would delete all previous
restore points. However, due to the minimum number of retained restore points, you will still have at
least 3 restore points: the newly created restore point and the two previous ones.

You can change the minimum number of retained restore points with a registry value. For more
information, contact Veeam Customer Support.

o If the backup job starts at the end of the day and finishes the next day, Veeam Backup & Replication
assumes that the restore point is created at the moment when the backup job started. However,
Veeam Backup & Replication starts counting retention policy days only after the backup job finishes
processing workloads.

1755 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o When determining whether the number of allowed days is exceeded, Veeam Backup & Replication
ignores the day when the daily retention policy runs. In fact, Veeam Backup & Replication keeps
restore points for the N + 1 days, where N is the number of days that you specify in the settings.

o When determining whether the number of allowed days is exceeded, Veeam Backup & Replication
also counts days when the backup job did not create any backups.

NOTE

If you want to create full backups periodically (weekly, monthly, yearly), enable the GFS retention policy. If
you do not enable the GFS retention, the regular backup copy cycles will create only incremental backups.

IMP ORTANT

This section describes how the short-term retention policy functions when the GFS retention policy is
disabled. If you enable the GFS retention policy, consider the following:

• The backup copy chain will contain more restore points than you have specified in the short-term
retention policy.
• With enabled GFS retention policy, Veeam Backup & Replication applies the forward-incremental
retention policy to the backup copy chain.

For details, see GFS Retention Policy.

Example
The regular backup cycle is based on the short-term retention policy scheme. When you specify retention policy
settings, you define how many restore points you want to retain in the backup chain in the target backup
repository.

For example, you have selected to retain 7 restore points. The backup copy runs once a day and starts on
Sunday.

1. Veeam Backup & Replication creates a full backup on Sunday and add 6 incremental backups Monday
through Saturday.

1756 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. On Sunday, Veeam Backup & Replication creates another increment. As a result, there will be 8 restore
points, which exceeds the retention policy. Thus, the oldest increment is merged to the full backup.

After the oldest increment is merged to the full backup, Veeam Backup & Replication removes the
increment as it is no longer needed.

Related Topics
Long-Term Retention Policy (GFS)

Long-Term Retention Policy (GFS)


The long-term or Grandfather-Father-Son (GFS) retention policy allows you to store VM backups for long
periods of time — for weeks, months and years. For this purpose, Veeam Backup & Replication creates synthetic
or active full backup files and marks them with GFS flags. These GFS flags can be of three types: weekly,
monthly or yearly. Depending on which flag is assigned to the full backup, it will be stored for specified number
of weeks, months or years.

The GFS retention also helps you to mitigate risks that the short-term retention policy has, such as large number
of subsequent incremental backups. Large number of subsequent incremental backups can increase recovery
time, because Veeam Backup & Replication has to read data through the whole backup chain. Also, one
corrupted increment can make the whole chain useless. When you configure the GFS retention,
Veeam Backup & Replication creates weekly/monthly/yearly full backups, so instead of one backup chain
consisting of one full backup and incremental backups, you will have several backup chains.

GFS backups are always full backup files that contain data of the whole machine image as of a specific date. GFS
is a tiered retention policy and it uses a number of cycles to retain backups for different periods of time:

• Weekly backup cycle

• Monthly backup cycle

• Yearly backup cycle

1757 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
In the GFS retention policy, weekly backups are known as ‘sons’, monthly backups are known as ‘fathers’ and
yearly backups are known as ‘grandfathers’. Weekly, monthly and yearly backups are also called archive
backups.

NOTE

GFS retention policy functions in combination with short-term retention policy. After you enable the GFS
retention, the backup chain switches from the forever-forward incremental policy to forward incremental
policy. Thus, the increments are no longer merged to the full backup file.

If you enable only yearly full backups without monthly and weekly backups, this can result in a large
number of increments in a backup chain. To avoid this, it is recommended to enable an additional weekly
GFS cycle. Weekly GFS cycle will update the backup chain every week which will allow
Veeam Backup & Replication to remove excessive increment files.

Related Topics
• How GFS Retention Works

• Limitations and Considerations for GFS Cycles

How GFS Retention Works


To understand how GFS retention works, see the following sections:

• Backup Copy GFS Methods

• Backup Copy GFS Cycles

• Backup Chain for GFS Backups

• Limitations and Considerations for GFS Retention Policy

Backup Copy GFS Methods

You can instruct Veeam Backup & Replication to create archive full backups with the following methods:

• Synthetic full method — Veeam Backup & Replication synthesizes archive full backups using restore points
in the target backup repository.

• Active full method — Veeam Backup & Replication copies data for archive full backups from the source
backup repository.

1758 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Synthetic Full Method for Archive Backups
The synthetic full backup is the default method to create archive full backups. Veeam Backup & Replication does
not copy data for archive full backups from the source backup repository. It synthesizes archive full backups
from backup files that are already stored in the target backup repository. This approach helps reduce load on
the network and production environment.

NOTE

The synthetic full method is not recommended if you use a deduplication storage appliance as a target
backup repository. Performing a synthetic full backup in such repositories requires additional time and
resources to download and decompress backup data blocks.

This recommendation does not apply to HPE StoreOnce, Dell Data Domain and ExaGrid:

• HPE StoreOnce and Dell Data Domain use virtual synthetics. Veeam Backup & Replication creates
archive full backups by virtually synthesizing data blocks from existing backup files.
• ExaGrid uses adaptive deduplication. Veeam Backup & Replication creates archive full backups from
existing backup files that are stored in complete form in ExaGrid high-speed cache.

Active Full Method for Archive Backups


You can instruct Veeam Backup & Replication to create archive full backups (backups retained by the GFS
scheme) with the active full backup method. The active full backup method is recommended if you use a
deduplicating storage appliance as the target backup repository. Active full backup helps improve the backup
copy job performance and reduce the load on the target backup repository.

By default, Veeam Backup & Replication uses the synthetic backup method to create archive full backups.
However, synthesizing archive full backups can cause problems with storage performance on deduplicating
storage appliances. Deduplicating storage appliances are optimized for sequential data access. The synthetic
backup creation, however, takes random I/O operations — Veeam Backup & Replication reads data from existing
backup files and writes data to the synthesized archive full backup file. As a result, the storage performance can
degrade.

In addition, backups reside in the target backup repository in the deduplicated and compressed state. Before
creating synthetic full backups, Veeam Backup & Replication needs to download and decompress data blocks of
backups, which requires additional time and resources.

1759 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• The active full backup method does not always copy the most recent restore point from the source
backup repository. If the recent restore point is not created by the time the GFS task must start,
Veeam Backup & Replication copies the latest available restore point from the source backup
repository.
• If Veeam Backup & Replication does not manage to transfer the restore point according to backup
copy schedule, Veeam Backup & Replication will finalize the transfer anyway.

Backup Copy GFS Cycles

When you configure the GFS schedule in the backup copy job settings, you specify for how long archive backups
must be stored and on which day certain GFS backup must be created. You can configure the GFS schedule in
the settings of a backup copy job. For details, see Backup Copy Job: Define Backup Copy Target.

1760 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
There are separate schedules for weekly, monthly and yearly full cycles. For details on settings of the GFS
retention, see the following table.

GFS Backup Option Description

W eekly GFS cycle If you want to create weekly full backups, select the Keep weekly full backups for
check box. Then, specify the number of weeks during which the weekly backup must
be stored on the target repository. During this period the weekly backup cannot be
deleted or modified.

Veeam Backup & Replication creates a weekly full backup on the specified day of the
week. On this day, creation of a weekly full backup starts as soon as the backup copy
interval starts.

Monthly GFS cycle To create monthly restore points, you can select the Keep monthly full backups for
check box. Then, specify the number of months during which the monthly backup
must be stored on the target repository. During this period the monthly backup
cannot be deleted or modified.

Veeam Backup & Replication creates monthly full backups according to a schedule
that depends on whether the weekly cycle is enabled or disabled:
• If weekly backups are enabled, Veeam Backup & Replication uses the weekly
backup schedule and adds a monthly flag to the weekly backup.
• If weekly backups are disabled, Veeam Backup & Replication creates monthly
full backups on the first day of the selected week. You can select First,
Second, Third, Fourth or La st week of a month. If you select First, monthly
backups are created on the first day of each month. If you select La st,
monthly backups are created on different dates depending on the number of
days in a month:
o For 31 days: 25th of the month.
o For 30 days: 24th of the month.
o For 29 days: 23rd of the month.
o For 28 days: 22nd of the month.

If the first day of the current week has already passed and you select the
first week for the monthly full backup cycle,
Veeam Backup & Replication creates a monthly full backup even if it is
not the first day of the current week.
If you enable the monthly GFS cycle and select the first week that has
already passed, Veeam Backup & Replication will create a monthly full
backup only in the next month. Monthly full backup for the current
month will not be created.

1761 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
GFS Backup Option Description

Y ea rly GFS cycle If you want to create yearly restore points, select the Keep y early full backups for
check box. Then, specify the number of years during which the yearly backup must
be stored on the target repository. During this period the yearly backup cannot be
deleted or modified.

Veeam Backup & Replication creates yearly full backups according to a schedule that
depends on whether the monthly cycle is enabled or disabled:
• If monthly backups are enabled, Veeam Backup & Replication uses the
monthly backup schedule and adds a yearly flag to the monthly backup.
• If monthly backups are disabled, Veeam Backup & Replication creates yearly
full backups on the first day of the selected month.
If the first day of the current month has already passed and you select the
current month for the yearly full backup cycle, Veeam Backup & Replication
creates a yearly full backup even if it is not the first day of the current month.
If you enable the yearly GFS cycle and select the month that has already
passed, Veeam Backup & Replication will create a yearly full backup only in
the next year. Yearly full backup for the current year will not be created.

TIP

If you want to save this set of settings as the default one, click Sa ve as default.
When you create a new job, the saved settings will be offered as the default. This
also applies to all users added to the backup server.

Backup Chain for GFS Backups


GFS retention creates yearly, monthly and weekly full backups and functions in a combination with the short -
term retention. Short-term retention policy cannot delete or merge these GFS full backups.
Veeam Backup & Replication removes GFS backups only after the specified retention period for
yearly/monthly/weekly backup is exceeded. Thus, the backup chain may contain more restore points than
specified in the short-term retention policy.

When you enable the GFS retention, Veeam Backup & Replication no longer merges increments to full backups
because GFS full backups cannot be modified. Thus, the short-term retention policy counts retention points only
in the active backup chain not in the whole combination of backup chains.

NOTE

Veeam Backup & Replication removes GFS backup files only during running backup copy job sessions. This
means that if the backup copy job does not run on the expected retention date,
Veeam Backup & Replication will remove the GFS backup file later during the next job session.

1762 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Multiple GFS Flags
If you schedule a monthly and/or yearly full backup on the same day when the weekly full backup is scheduled,
Veeam Backup & Replication creates only one archive full backup. The created backup will be mark ed at the
same time as weekly, monthly and yearly GFS backup. In the Veeam Backup & Replication console, you will see
all GFS flags assigned to the backup.

The full backup can be marked as weekly, monthly and/or yearly. When transforming weekly, monthly and
yearly backup chains, Veeam Backup & Replication checks flags set for the full backup file. If the full backup file
belongs to some other retention policy tier and must be retained in the target backup repository, such backup
file will not be removed.

Checking Which Restore Point Has GFS Flag


To check whether a restore point has a GFS flag, you can open the backup properties in the
Veeam Backup & Replication console. Weekly, monthly, yearly backups have " W ", " M" and/or " Y" flag in the
Retention column. For instructions, see Viewing Backup Properties.

Limitations and Considerations for GFS Cycles


Before configuring the GFS retention policy for a backup copy job, consider the following limitations and
considerations:

• General Settings

• Periodic Copy Mode

• Changes in GFS Retention After Upgrading from Veeam Backup & Replication 10 to version 12

1763 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
General Settings
Consider the following for general settings of a backup copy job:

• You cannot enable GFS retention settings if you use a backup repository with rotated drives as the target
backup repository.

• [For yearly GFS cycle] If you enable only the yearly GFS cycle, you can encounter the case when there is
one full backup and a large number of increments for the whole year. To avoid this case, it is
recommended to enable an additional weekly GFS cycle. Weekly GFS cycle will update the backup chain
every week which will allow removing excessive increment files.

• If for some reason the GFS synthetic full was not created in the scheduled day,
Veeam Backup & Replication will create the synthetic GFS full after the next run of the backup copy job.

• If it is the day when the GFS full backup must be created and there were no new backup files since the last
run of the backup copy, Veeam Backup & Replication will create the GFS full backup from the latest
available backup chain.

• GFS full backups cannot be merged or deleted by short-term retention. However, regular (R) full backups
can be merged and removed by short-term retention if GFS is disabled.

• [For immediate copy mode] If the backup copy job was not run when the GFS full backup must be created,
the GFS full backup will not be created on this day.

Periodic Copy Mode


If you want to use the periodic copy mode, consider the following:

• If Veeam Backup & Replication does not manage to transfer the restore point according to backup copy
schedule, Veeam Backup & Replication will finalize the transfer anyway.

• Veeam Backup & Replication creates a GFS full backup even if the GFS full backup creation is scheduled
when the backup copy scheduled run is not finished. On the day when the GFS full backup must be
created, Veeam Backup & Replication shows a warning that the current backup copy scheduled run will be
completed. The way Veeam Backup & Replication behaves further depends on the selected backup copy
GFS method:

o In case of the synthetic full method, Veeam Backup & Replication first copies data for an incremental
backup from the source backup repository and then, on the target backup repository, synthesizes the
GFS full backup using this data and data of the already stored backup files.

o In case of the active full method, Veeam Backup & Replication copies data for the GFS full backup
from the source backup repository and creates the GFS full backup on the target backup repository.

Changes in GFS Retention After Upgrading from Veeam


Backup & Replication 10 to version 12
In Veeam Backup & Replication version 12, the backup copy GFS retention settings are different from the
settings in version 10.

IMP ORTANT

If you run an upgrade from version 10 to version 12 when the GFS retention policy is disabled,
Veeam Backup & Replication will delete all GFS storages created before.

1764 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you upgrade to Veeam Backup & Replication 12, all GFS retention settings of existing backup copy jobs are
automatically switched to the new format with minimal changes:

• W eekly GFS retention: If in version 10 the GFS setting was to keep 5 weekly backups, in version 12 the
setting is changed to keep weekly backups for 5 weeks.

• Monthly GFS retention: If in version 10 the monthly GFS schedule was set to a period between the 1st
Monday and 2nd Sunday, in version 12 the monthly GFS settings is changed to First week .

If the monthly GFS schedule was set to a period between the 3rd Monday and last Sunday, in version 12
the monthly GFS settings is changed to Last week .

• Y ea rly GFS retention: If the yearly GFS schedule was set to a certain day of the month, in version 12 the
schedule is set to the first day of the specified month.

If in version 10 the yearly GFS schedule was set to the first-fourth Monday-Sunday of the year, in version
12 the schedule is changed to the first day of January.

If the yearly GFS schedule was set to the last Monday-Sunday of the year, in version 12 the schedule is set
to the first day of December.

• Qua rterly GFS retention: Since Veeam Backup & Replication version 11, quarterly GFS retention policy
option is deprecated.

If in version 10 the quarterly GFS policy was enabled, in version 12 three additional months are added to
the monthly GFS policy to compensate the quarterly full backups.

If in version 10, the GFS policy was set to X monthly backups and Y quarterly backups. Then, in version 12,
the retention policy is switched to store monthly backups for (X + 3Y) months.

IMP ORTANT

[For synthetic method] Before the upgrade to Veeam Backup & Replication 12 or later, make sure that all
GFS candidates (incremental restore points created on days when GFS was scheduled and that are
expected to be transformed into full GFS restore points) are already transformed into GFS restore points.
To force the backup copy job to transform all GFS candidates, you can temporarily decrease the short -term
retention to a value less than the number of restore points between the latest restore point and the most
recent GFS candidate and then wait till all the candidates are transformed.

Before Veeam Backup & Replication version 11, Veeam Backup & Replication created GFS candidates on
days when GFS was scheduled and only then transformed them into full GFS res tore points according to
the short-term retention. For more information on how restore points were transformed, see Synthetic
Weekly Full Backups. Starting from Veeam Backup & Replication version 11, Veeam Backup & Replication
creates GFS restore points according to a new schedule and creates them right on the scheduled days.
After the upgrade, Veeam Backup & Replication no longer transforms previous GFS candidates into full GFS
restore points. This means, that all GFS candidates lose their GFS status, they become regular incremental
restore points and are deleted according to the short-term retention policy.

Deleted Items Retention


After you configure a backup copy job, you may want to change something in the virtual infrastructure. For
example, you may remove some virtual or physical machines or move VMs to another location. You may also
exclude VMs from the backup copy job that has already run for some time.

1765 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
By default, when you remove a machine protected by Veeam Backup & Replication from the virtual
infrastructure, exclude a machine from the backup copy job or stop protecting a machine with Veeam Agent, the
copied data still remains in backup files in the target backup repository. To avoid keeping redundant data on
disk, you can enable the Remove deleted items data after option in the backup copy job settings. With this
option enabled, at the end of every synchronization cycle Veeam Backup & Replication will remove data for
deleted machines from backup files in the target backup repository.

Veeam Backup & Replication removes data for deleted machine only if two conditions are met:

1. Veeam Backup & Replication has not created a valid restore points for the deleted machine for the number
of days specified in the Remove deleted items data after field.

2. The backup chain in the target backup repository does not contain any successful incremental restore
points for the deleted machine.

This approach helps ensure that data for deleted machines can be saved by the GFS retention.

For example:

• The retention for the backup copy job is set to 7.

• The retention period for deleted machine is set to 3 days.

The backup copy job has created 3 successful restore p oints — a full backup and two incremental backups.
During the next 4 days, no successful restore points were created. At the next synchronization cycle,
Veeam Backup & Replication will not remove data for the deleted machine from the target backup repository as
the backup chain contains successful incremental restore points for this machine.

1766 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

Consider the following:

• The deleted items retention applies only to regular backup chains. Veeam Backup & Replication does
not remove data for deleted machines from weekly, monthly and yearly backups.
• [For single-file backups] When Veeam Backup & Replication removes data for deleted machines
from regular backup chains, it does not free up space in the backup repository. It marks the space as
available to be overwritten, and this space is overwritten during subsequent job sessions or the
backup file compact operation.
• When Veeam Backup & Replication removes data for deleted machines from per-machine backup
chains, it does not mark the space as available but deletes backup files since they contain data for 1
machine only.

Veeam Backup & Replication does not analyze the reason for which the machine has not been processed during
the backup copy session. For example, a VM may be regarded as deleted if Veeam Backup & Replication has
failed to obtain data for the VM from the virtual infrastructure, the VM has failed to be processed in time during
the backup copy session and so on.

For this reason, you must be careful when specifying the retention period for deleted machines. If the retention
period is too short, Veeam Backup & Replication may remove from the backup chain restore points that you still
require.

For example, a backup copy job is configured to process 2 VMs and has the following settings:

• The backup copy starts once a day.

• The retention for the backup copy job is set to 2.

• The retention period for deleted VMs is set to 1 day.

The backup copy job runs in the following way:

1. On Sunday, the backup copy job creates a full backup for 2 VMs – VM1 and VM2.

2. On Monday, the backup copy job creates an incremental backup for VM1. The backup copy job does not
manage to process VM2 in time.

3. On Tuesday, the backup copy job creates an incremental backup for VM1. The backup copy job does not
manage to process VM2 in time.

4. At the end of the backup copy job session on Tuesday, Veeam Backup & Replication transforms the backup
chain and detects deleted VMs. Veeam Backup & Replication regards VM2 as a deleted VM — the deleted
VMs retention is set to 1 day, and after transformation, there are no valid restore points for this VM in the
backup chain.

As a result, after the backup copy session on Tuesday backup files in the target backup re pository will not
contain data for VM2.

1767 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Health Check for Backup Files
You can instruct Veeam Backup & Replication to periodically perform a health check for the latest restore point
or backup file in the backup chain. The health check helps Veeam Backup & Replication make sure that further
restore will be possible.

The health check starts as soon as a backup copy job starts. The health check verifies restore points (full backup
files or related full and incremental backup files). Only the latest restore p oints are verified. On the day when
the health check is scheduled, Veeam Backup & Replication performs the health check only once, even if the
backup copy job runs several times.

NOTE

Consider the following:

• The health check process differs for backup files stored in the HPE StoreOnce repository. For more
information, see Health Check for Backup Files Stored on HPE StoreOnce.
• If you perform the health check for the encrypted backup files, Veeam Backup & Replication will
pass encryption keys to the regular backup repository or cloud repository. For more information on
encryption, see Data Encryption.
• If the backup copy job uses WAN accelerators, Veeam Backup & Replication attempts to find data
blocks in the global cache not to transfer data over the network. For more information, see WAN
Acceleration.

How Health Check Works


Veeam Backup & Replication performs the health check in the following way:

1. As soon as a restore point is saved to the backup repository, Veeam Backup & Replication calculates CRC
values for backup metadata and hash values for data blocks of a disk in the backup file and saves these
values in the metadata of the backup file, together with copied data.

2. On the day when the health check is scheduled, Veeam Backup & Replication performs the following
actions:

a. Veeam Backup & Replication performs the health check for the latest restore point in the backup
chain. If the latest restore point in the backup chain is incomplete, Veeam Backup & Replication
checks the restore point preceding the latest one.

Veeam Backup & Replication calculates CRC values for backup metadata and hash values for disk s
data blocks in the backup file and compares them with the CRC and hash values that are already
stored in the backup file.

1768 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. If the health check detects corrupted data blocks, together with data blocks for the new restore point,
Veeam Backup & Replication transports valid data blocks for the corrupted restore point. The valid
data blocks are stored to the new incremental restore point created by this backup copy session. As a
result, the backup chain gets “fixed”, and you get a possibility to restore data from restore points
following the corrupted restore point.

Health Check for Backup Files Stored on HPE StoreOnce


The health check starts as soon as a backup copy job transfers backup files to the target repository. The health
check verifies backup files, not restore points, and only those backup files transferred during the current job
session.

Veeam Backup & Replication performs the health check in the following way:

1. As soon as a backup file is transferred to the target repository, Veeam Backup & Replication calls the HPE
StoreOnce internal method that calculates checksums for data blocks of this backup file.

The checksum calculation requires the rehydration of the verified data. This may lower the performance
on the target repository especially during the first backup copy session. During this session, the health
check verifies all backup files in source backup chains.

2. Veeam Backup & Replication compares the calculated checksums and the checksums already stored in the
backup file.

3. If the health check detects corrupted data blocks, Veeam Backup & Replication deletes the backup file
from the target repository. On the next backup copy job session, Veeam Backup & Replication transfers
and performs the health check for this file again.

1769 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Compact of Full Backup File
The backup copy job constantly transforms the full backup file in the backup chain to meet retention policy
settings. The transformation process, however, has a side effect. In the long run, the full backup file grows large
and gets fragmented. The file data occurs to be written to non-contiguous clusters on disk, and operations of
reading and writing data from and to the backup file slow down.

To resolve the fragmentation problem, you can instruct Veeam Backup & Replication to compact the full backup
file periodically. During the file compact operation, Veeam Backup & Replication creates a new full backup file in
the target repository: it copies existing data blocks from the old backup file, rearranges and stores them close to
each other. As a result, the full backup file gets defragmented, its size reduces and the speed of reading and
writing from and to the file increases.

To compact the full backup file periodically, you must enable the Defragment and compact full backup file
option in the backup copy job settings and define the compact operation schedule. By default, the compact
operation is performed on the last Sunday of every month. You can change the compact operation schedule and
instruct Veeam Backup & Replication to perform it weekly or monthly on specific days.

1770 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Copy Job Mapping
Backup copy job mapping helps you reduce the amount of data transferred over network and decrease the load
on WAN accelerators or slow connections. You can also use mapping to upgrade f rom legacy backup chain
formats to per-machine backup with separate metadata files format. For more information, see Backup Chain
Formats.

[For legacy periodic backup copy job] If you use the target backup repository also as a target for other backup
copy or backup jobs, you can already have a backup of machines that you want to copy. In this case, you can map
the backup copy job to this backup.

A backup copy job mapped to a backup is performed in the following way:

1. Veeam Backup & Replication accesses a backup to which you map the backup copy job. The backup may
have any number of restore points in the chain. This backup chain will be used as a seed for the further
backup copying process.

2. During subsequent backup copy sessions, Veeam Backup & Replication copies restore points in a regular
manner. It copies only incremental changes and stores them as new restore points next to the seed backup
chain.

A mapped backup copy job does not store copied restore points in a dedicated folder in the target backup
repository. Instead, it stores restore points to the same folder where the "seed" backup chain resides.

Creating Seed for Backup Copy Job


Backup copy jobs have limitations for backups that can be used as seeds. The limitations are listed in section
Map Backup File.

To create a seed for the primary backup copy job, do the following:

1. Create a backup copy job. Add jobs or repositories whose restore points you want to copy to this backup
copy job. Target the backup copy job to some backup repository on the source side. This backup repository
will be used as an intermediate one.

2. Run the backup copy job to create a full backup file (VBK) in the intermediate backup repository.

3. Transfer the created VBK file and VBM file from the intermediate backup repository to the target backup
repository.

4. Perform repository rescan to populate the target backup repository.

If the initial backup file was encrypted, you must enter a password to unlock the full backup file.
Otherwise, Veeam Backup & Replication will not display the full backup file in the list of backups in the
backup repository. For more information, see Importing Encrypted Backups.

1771 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
5. Remap the backup copy job to the full backup file that you have created and transferred to the target
backup repository.

As a result, Veeam Backup & Replication will use the full backup file as a seed. When a new restore point for the
machine is available in the source backup repository, Veeam Backup & Replication will copy the restore point to
the target backup repository and store it next to the full backup seed.

Specifying Backup Copy Interval for Periodic Copy Mode


When you configure a backup copy job, make sure that its backup copy interval covers the whole chain of
restore points in the backup repository from which you plan to copy backups. The length of the backup copy
interval has an impact on the algorithm of restore point selection. Veeam Backup & Replication copies only
restore points that match the following criterion:

Time of restore point creation >= current time – backup copy interval

That is, if you have a backup chain whose earliest restore point is 1 week old, you need to set the backup copy
interval to 1 week. If you set the backup copy interval to a smaller time interval, for example, 1 day, all restore
points that are older than 1 day will fall out of the search scope, and Veeam Backup & Replication will not
transfer such restore points. For more information, see Restore Point Selection.

1772 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Active Full Backup Copies
You can manually create an ad-hoc full backup for the backup copy job — active full backup copy, and add it to
the backup chain in the target backup repository. To do this, you can use the Active Full button on the ribbon or
the Active Full command from the shortcut menu.

Active full backup copy can be helpful if you want to change backup copy job settings, for example, enable or
disable encryption. Veeam Backup & Replication will apply new settings starting from this full backup.

Veeam Backup & Replication treats archive full backups created with the active full backup method as regular
backups and applies regular retention policy rules to maintain the necessary number of restore points.

Retention Policy for Active Full Backups


If you create active full backups for backup copy jobs, Veeam Backup & Replication applies to the backup chain
retention rules of the forward incremental backup method. Veeam Backup & Replication waits until the number
of restore points in the new backup chain is equal to the retention policy setting, and then removes the previous
backup chain on the whole. For more information, see Retention for Forward Incremental Backup.

1773 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Automatic Job Retries
Veeam Backup & Replication automatically retries several operations that are performed within a backup copy
job session.

Job Tasks Retry


By default, Veeam Backup & Replication automatically retries a failed backup copy task 5 times within one
backup copy job session. A new task is started immediately after the previous one.

The backup copy task is retried only if the previous task has failed and a restore point has not been copied to the
target backup repository. Veeam Backup & Replication does not perform a retry if a task has finished with the
Success or the Warning status.

The backup copy task is retried during the same backup copy session only. If a restore point fails to be copied
during all retries in the current backup copy session, Veeam Backup & Replication marks the current task as
failed. [For the legacy periodic mode] After that, Veeam Backup & Replication performs the necessary
transformation processes and starts a new backup copy session.

A backup copy job can process several machines. If only some machines are successful ly processed by the
backup copy task, Veeam Backup & Replication creates a restore point holding data for these machines in the
target backup repository. Veeam Backup & Replication will attempt to process restore points for all machines
during the next backup copy session.

NOTE

Some errors from WAN accelerators can block backup copy job retries. For example, if there is no space in
the global cache on the target WAN accelerator, Veeam Backup & Replication puts backup copy operations
on hold and waits for the expiration of the backup copy session.

Transformation Retry
After the backup copying task, Veeam Backup & Replication may perform a number of additional transformation
processes in the target backup repository. These processes include the backup chain transformation, removing
of deleted machines from restore points and compacting a full backup file. For more information, see
Transformation Processes.

Veeam Backup & Replication may fail to perform transformation: for example, if the backup file in the target
backup repository is locked by the file-level restore session. By default, Veeam Backup & Replication
automatically retries transformation processes for 5 times. The first interval between retries is 1 minute; the
interval doubles with every new attempt. If all retries of transformation processes fail,
Veeam Backup & Replication does the following:

• [For the immediate copy mode] Stops the job with the Fail status and waits for the new job session.

• [For the periodic copy mode] Stops the job with the Fail status and waits for the job to retry according to
schedule.

• [For the legacy periodic copy mode] Puts the job to the idle state and waits for the new backup copy
interval to begin.

Virtual Infrastructure Access Retry


At the beginning of every backup copy session, Veeam Backup & Replication accesses the virtual infrastructure
to make up a list of machines processed by the job.

1774 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication may fail to access the virtual infrastructure for some reason: for example, in case
the Hyper-V host is not responding. By default, Veeam Backup & Replication automatically retries access
operations for 5 times with a 5 minute interval.

1775 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Backup Copy Jobs for VMs and
Physical Machines
To copy backups to a secondary location, you must configure a backup copy job. The backup copy job defines
how, where and when to copy backups. One backup copy job can be used to process one or multiple machines.
Machines included in the job are processed in parallel. If a machine included in the backup copy job has multiple
disks, disks are processed sequentially, one after another.

NOTE

If you want to copy backups between HPE StoreOnce repositories, follow the instructions listed in section
Creating Backup Copy Jobs for HPE StoreOnce Repositories.

If you want to copy file share backups, follow the instructions listed in section Creating File Backup Jobs.

Before you create a job, check prerequisites. Then use the New Backup Copy Job wizard to configure the backup
copy job.

1776 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you create a backup copy job, check the following prerequisites:

• Backup infrastructure components that will take part in the backup copy process must be added to the
backup infrastructure. This include target backup repository to which backups must be copied. For more
information on adding components, see Backup Infrastructure Components.

• If you plan to use pre-job and post-job scripts, you must create scripts before you configure the backup
copy job.

• If you plan to copy backups to an HPE StoreOnce repository, check limitations and requirements for it.

• If you plan to use WAN accelerators, check that you use the Enterprise Plus edition of
Veeam Backup & Replication and that target and source WAN accelerators are added to the backup
infrastructure. For more information, see Adding WAN Accelerators.

• If you plan to migrate VMs between hosts in the cluster or SCVMM, you will not have to reconfigure jobs
in Veeam Backup & Replication. Veeam Backup & Replication will automatically locate migrated VMs and
continue processing them as usual. If you migrate VMs between standalone hosts that are not a part of one
cluster or SCVMM server registered in Veeam Backup & Replication, you will have to reconfigure jobs to include
the migrated VMs. After that, Veeam Backup & Replication will create full backups for these VMs. If you do not
reconfigure the jobs, they will fail.

1777 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Copy Job Wizard
To run the New Backup Copy Job wizard:

• If you don't have application plug-ins backups, do one of the following:

o On the Home tab click Ba ckup Copy.

o Open the Home view, in the inventory pane right-click Job s or right-click anywhere in the working
area, and click Ba ckup Copy.

• If you have application plug-ins backups, do one of the following:

o On the Home tab, click Ba ckup Copy and click Image-level backup copy or Ap p lication backup copy.

o Open the Home view, in the inventory pane right-click Job s or right-click anywhere in the working
area, click Ba ckup Copy and click Image-level backup copy or Ap plication backup copy.

1778 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Copy Mode
At the Job step of the wizard, specify basic settings for the backup copy job:

1. In the Na me field, specify a name for the job.

2. In the Description field, provide a description for the job.

The default description contains information on a user who created the job, date and time when the job
was created.

3. Select a backup copy mode. Note that after you finish configuring the backup copy job, you will not be
able to change the selected mode. For more information on copy modes and backup types supported in
each mode, see Backup Copy Modes.

o Select Immediate copy to copy new restore points and, if required, log backups as soon as they
appear.

o Select P eriodic copy to copy the most recent restore points.

1779 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Workloads to Process
At the Ob jects step of the wizard, select workloads whose restore points you want to copy to the target backup
repository:

1. Click Ad d .

2. Select a type of a source from which you want to copy restore points:

o From jobs. You will see existing backup jobs. Veeam Backup & Replication will copy restore points
created by the selected backup jobs.

[For the periodic copy mode] Note that if multiple jobs process one workload, Veeam Backup &
Replication copies only restore points created by the first job in the Ob jects to process list.

o From repositories. You will see all backup repositories in the backup infrastructure.
Veeam Backup & Replication will copy restore points stored on the selected backup repositories.

If you select repositories as sources, and target new jobs to the repositories in future,
Veeam Backup & Replication will update backup copy job settings automatically to include these jobs
to be copied.

o From backups. You will browse for workloads in existing backups. Veeam Backup & Replication will
search for restore points of the selected workloads in all backups of backup jobs created on the
external repositories and will copy the most recent restore points. You can limit the search scope by
selecting only specific backup policies for the backup copy job.

This source is only available for backup copy jobs that process backups of Amazon EC2 instances,
Microsoft Azure and Google Cloud.

NOTE

You can use From backups source only if you have an external repository added to the backup
infrastructure and have at least one backup file stored in it.

3. In the Ad d Objects window, select the necessary sources or workloads.

4. Click Ad d .

5. [For the immediate copy mode] If you have configured processing of transaction log backups in the source
backup jobs, and want to copy these log backups to the target repository, select the Include database
tra nsaction log backups check box.

NOTE

If you delete the source backup job after creating the backup copy job, backup files will become orphaned.
The orphaned backup files are displayed under the Ba ckups > Disk (Orphaned) node. If the orphaned
backup files were also stored in capacity tier or archive tier, they will also be displayed under the Backups >
Ob ject Storage (Orphaned) or Ba ckups > Archive (Orphaned) nodes. The orphaned backup files can not be
processed by any job.

1780 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

When you copy Veeam Agent backup jobs that process clusters with shared disks, the network traffic will
be higher compared to the traffic sent when Veeam Agent backup jobs run. This is because Veeam Agent
backup jobs send data of shared disks only with the owner node and then, within the target storage, clone
this data to other nodes; whereas backup copy jobs send data as it is stored on the storage — each node
with the cloned data.

As an alternative, you can create a backup copy job with an empty source — that is, do not add any workloads at
this step of the wizard. In this case, you need to configure a secondary destination for the source backup job and
link it to the created backup copy job. For more information, see Linking Backup Jobs to Backup Copy Jobs.

NOTE

Even if Use p er-machine backup files option is disabled in a repository that you are planning to use as the
target, backup copy job will always create per-machine backup files in the backup repository.

1781 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Exclude Objects from Backup Copy Job
This option is available only for virtual machines.

To specify which objects you want to exclude from the backup copy job:

1. At the Ob jects step of the wizard, click E x clusions.

2. In the E x clusions window, click Ad d .

If you have added repositories as sources of restore points, you can exclude individual VMs or backup jobs
from processing. To exclude individual VMs, click Ad d > VMs . To exclude individual jobs, click Ad d > Job s.

3. In the Ad d Objects window, select objects that you want to exclude.

When you exclude VMs, you can use the Show full hierarchy check box to display the hierarchy of all hosts
added to Veeam Backup & Replication.

4. Click Ad d .

5. Click OK.

1782 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Define Processing Order
IMP ORTANT

This functionality is available only when editing legacy periodic backup copy job created in
Veeam Backup & Replication 11 or earlier.

You can define the order in which the backup copy job must process workloads. Configuring workload order can
be helpful, if you want the backup copy job to process mission-critical workloads first. For this, put these
workloads higher in the list to ensure that their processing fits the backup window.

Workloads inside a container are processed at random. To ensure that workloads are processed in the defined
order, you must add them as standalone workloads, not as part of the container.

To define workload processing order:

1. At the Ob jects step of the wizard, select a workload whose order you want to change.

2. Use the Up and Down buttons on the right to move the workload up or down in the list.

1783 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Target Repository and Retention
Settings
At the Ta rget step of the wizard, define a target backup repository and configure retention policy:

1. From the Ba ckup repository list, select a backup repository where copied backups must be stored.

2. In the Retention Policy field, configure the short-term retention policy for restore points:

o If you want to keep the last <N> restore points, select restore points from the drop-down list and
specify the number of restore points.

o If you want to keep all restore points created during the last <N> days, select days from the drop-
down list and specify the number of days.

When the specified number is exceeded, the earliest restore point will be removed from the backup chain
or will be merged with the next closest restore point. For more information on how
Veeam Backup & Replication retains the desired number of restore points, see Short-Term Retention
Policy.

NOTE

If you enable the GFS retention, the short-term retention policy will not be able to delete and merge
the GFS backup files. Thus, the backup copy chain will have more restore points than specified in the
short-term retention policy.

3. If you want to create weekly, monthly and yearly full backups, you can configure long -term retention
policy (GFS retention policy). GFS full backups will not be deleted or modified until the specified retention
period expires. For more information on the GFS retention policy and its limitations, see Long-Term
Retention Policy (GFS).

To configure GFS retention policy, do the following:

a. Select the Keep certain full backups longer for archival purposes check box.

b. Click Configure.

c. In the Configure GFS window, select the necessary GFS backup options. You can configure
Veeam Backup & Replication to create weekly, monthly and yearly restore points. For details on
settings of the GFS retention, see Backup Copy GFS Cycles.

NOTE

Before you implement the GFS retention policy, see Limitations and Considerations.

4. [For the periodic copy mode] You can define a way to create weekly, monthly and yearly full backups:

o Synthetic Full Method: With this method, during the GFS backup copy creation,
Veeam Backup & Replication does not copy data from the source backup repository but synthesizes
full backups from backup files that are already stored in the target backup repository. This approach
helps to reduce load on the network and production environment.

The synthetic full method is used by default. To use this method, leave the Rea d the entire restore
p oint from source instead of synthesizing it from increments option unselected.

1784 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o Active Full Method: With this method, Veeam Backup & Replication copies data for archive full
backups from the source backup repository. This method decreases load on the target repository but
increases load on the network and production environment.

To use this method, select the Rea d the entire restore point from source instead of synthesizing it
from increments option.

NOTE

Backup copy job with restore point-based retention policy does not support partial vApp active full
backups. That is, vApp backups within which active full backup was created only for individual VMs. For
more information, see Performing Active Full Backup.

1785 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Map Backup File
If the target backup repository already stores a backup of workloads that you want to copy, you can map the
backup copy job to this backup.

The backup copy job will use the backup as a seed. As a result, Veeam Backup & Replication will transfer less
data over network. For more information, see Mapping Backup Copy Jobs.

To map the backup copy job to a backup:

1. At the Ta rget step of the wizard, click the Ma p backup link.

2. In the Select Backup window, select a backup that contains restore points of workloads that you want to
copy.

Limitations for Mapping


When mapping a backup copy job, consider the following limitations:

• If a backup that you plan to use as a seed is encrypted, you must enable encryption for the backup copy
job. The password that you use for the backup copy job can differ from the password used for the initial
job.

• The following limitations apply to a backup that can be used as a seed:

o You can map the backup copy job created in Veeam Backup & Replication 11 only to a backup file
created in Veeam Backup & Replication 11. In this case, a backup file will not be upgraded to the per -
machine backup file.

o You can map the backup copy job created in Veeam Backup & Replication 12 only to a backup created
by a backup copy job. Legacy backup copy job can be mapped to backups created by both backup job
and backup copy job.

o You can map the backup copy job created in Veeam Backup & Replication 12 only to the per-machine
backup file. If you map it to the non per-machine backup file, this file will be upgraded to the per-
machine backup file. Old version of the backup file will become orphaned.

o [For the legacy periodic copy mode] If you map the backup copy job to a backup created by a backup
job, this backup must be created with the incremental backup method only, that is, forever forward or
forward incremental.

1786 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o [For the legacy periodic copy mode] You can map a Veeam Agent backup copy job only to a backup
created by backup copy job that processes backups created by Veeam Agent operating in the
standalone mode.

1787 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Advanced Settings
At the Ta rget step of the wizard, you can specify the following settings for the backup copy job:

• Maintenance settings

• Storage settings

• RPO Monitor settings

• Notification settings

• Script settings

• Advanced settings

TIP

After you specify advanced settings for the backup copy job, you can save them as default settings. For
this, click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create a
new backup copy job, Veeam Backup & Replication will automatically apply the default settings to the new
job.

Maintenance Settings
To specify settings for backup files stored in the target backup repository:

1. At the Ta rget step of the wizard, click Ad vanced.

2. If you want to periodically perform a health check of the most recent restore point in the backup chain,
select the P erform backup files health check check box. To specify the schedule for the health check, click
Configure.

By default, the health check is performed on the last Saturday of every month. For more information on
the health check, see Health Check.

3. Select the Remove deleted items data after check box and specify the retention policy settings for deleted
workloads.

By default, the deleted item retention period is 30 days. It is recommended that you set the retention
period to 3 days or more to prevent unwanted data loss. For more information on the retention policy and
its limitations, see Deleted Items Retention.

4. To periodically compact a full backup, select the Defragment and compact full backup file check box. To
specify the schedule for the compacting operation, click Configure.

By default, the compact operation is disabled. For more information on compact of full backup files, see
Compact of Full Backup File.

5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

1788 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

When enabling the Defragment and compact full backup file option, consider the following:

• The Defragment and compact full backup file option can be enabled only if GFS retention
policy is disabled.
• The target backup repository must have enough space to store a file of the full backup size.
During the compact process, Veeam Backup & Replication creates an auxiliary VBK file that
exists in the backup repository until the end of the compact operation.
• [For the legacy periodic backup copy job] If you do not want to copy data for workloads that
have only one restore point in the full backup file and this restore point is older than 7 days,
check that the following conditions are met: Remove deleted items data is disabled; Use per-
ma chine backup files is disabled in the settings of the target backup repository.
Veeam Backup & Replication will extract data for such workloads from the full backup file and
write this data to a separate backup file. The file will be displayed under the Ba ckups > Disk
( Imported) node in the Home view.

Storage Settings
To specify compression, deduplication and encryption settings for backup files stored in the target backup
repository, do the following:

1. At the Ta rget step of the wizard, click Ad vanced.

2. Click the Storage tab.

3. In the Da ta reduction section, specify data compression and deduplication settings:

o By default, Veeam Backup & Replication performs deduplication before storing copied data in the
target backup repository. To disable data deduplication, clear the E na ble inline data deduplication
check box.

For more information on deduplication, see Deduplication.

o From the Compression level list, select a compression level.

For more information on data compression levels, see Data Compression.

1789 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the E ncryption section, specify encryption settings:

o To encrypt the backup file created by the backup copy job, select the E na ble backup file encryption
check box.

o From the P a ssword field, select a password that you want to use to encrypt the backup file. If you
have not created a password beforehand, click Ad d or use the Ma nage passwords link to specify a new
password. For more information, see Managing Passwords for Data Encryption.

5. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

NOTE

When specifying encryption settings, consider the following:

• If you enable encryption for an existing backup copy job, Veeam Backup & Replication applies
new settings only starting from the next active full backup (created manually or by the GFS
schedule). The active full backup file and subsequent incremental backup files in the backup
chain will be encrypted with the specified password.
Note that if you disable the Read the entire restore point from source backup instead of
synthesizing it from increments option in the backup copy job, you will have synthetic full
backups, not active full backups. For details, see Defining Backup Copy Target.
• Encryption is not retroactive. If you enable encryption for an existing job,
Veeam Backup & Replication does not encrypt the previous backup chain created with this job.
If you want to start a new chain so that the unencrypted previous chain can be separated from
the encrypted new chain, follow the scenario described in this Veeam KB article.

RPO Monitor Settings


You can instruct a backup copy job to display a warning if a newly created restore point or transaction log is not
copied within the desired recovery point objective (RPO). The RPO is counted down from the moment when the
source backup job finishes and is ready to be copied.

To mark a job with the Warning status when the RPO is exceeded, do the following:

1. At the Ta rget step of the wizard, click Ad vanced.

1790 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Click the RP O Monitor tab.

3. Select the Alert me if newly created backup is not copied within check box.

4. In the fields on the right, specify the desired RPO in minutes, hours or days. If you specify days, RPO
monitor will consider calendar days instead of the 24 hours period.

5. If you have enabled copying of log backups, select the Alert me if newly created log backup is not copied
within check box.

6. In the fields on the right, specify the desired RPO in minutes, hours or days.

7. Click Sa ve as default if you want to save this set of RPO settings as the default one. When you create a
new job, the saved settings will be offered as the default. This also applies to all users added to the
backup server.

Notification Settings
To specify notification settings for the backup copy job:

1. At the Ta rget step of the wizard, click Ad vanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when the job
completes successfully. In the periodic copy mode, you will receive notifications when the entire backup
copy job finishes. In the immediate copy mode — when copying of each source backup job finishes.

SNMP traps will be sent if you specify global SNMP settings in Veeam Backup & Replication and configure
software on the recipient workload to receive SNMP traps. For more information, see Specifying SNMP
Settings.

1791 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. Select the Send email notifications to the following recipients check box if you want to receive
notifications by email in case of job failure or success. In the field below, specify the recipient email
address. You can enter several addresses separated by a semicolon.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication.

o Veeam Backup & Replication sends notifications when copying of each source backup job finishes. For
example, if your backup copy job contains two source backup jobs, you will receive two emails.

o [For the legacy periodic copy mode] Veeam Backup & Replication sends a consolidated email
notification once for the specified backup copy interval. Even if the synchronization process is started
several times within the interval, for example, due to job retries, only one email notification will be
sent.

For more information on how to configure global notification settings, see Configuring Global Email
Notification Settings.

5. In the Send daily summary at field, specify when you want to send notifications about backup copy jobs
that process log backups. Veeam Backup & Replication sends a consolidated report once a day at the
specified time.

6. You can choose to use global notification settings or specify custom notification settings.

o To receive a typical notification for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server. For more information, see Configuring Global Email Notification Settings.

o To configure a custom notification for a job, select Use custom notification settings specified below.
You can specify the following notification settings:

i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName% (the backup copy job name and source
backup job name in the CopyJobName\SourceJobName format), %JobResult%,
%ObjectCount% (number of workloads in the job) and %Issues% (number of workloads in the
job that have been processed with the Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive
email notification if data processing completes successfully, completes with a warning or
fails.

7. [For the immediate copy mode] Select when you want to receive notifications, Immediately after each
cop ied backup option or Da ily as a summary.

1792 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
8. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Scripts Settings
To specify script settings for the backup copy job:

1. At the Ta rget step of the wizard, click Ad vanced.

2. Click the Scripts tab.

3. Select the Run the following script before the job and Run the following script after the job check boxes
to execute custom scripts before and after the backup copy job. Note that in the immediate copy mode,
scripts are executed for every source backup job.

Then click Browse and select executable files from a local folder on the backup server. The scripts will be
executed on the backup server after the transformation processes are completed on the target repository

4. You can change how often the scripts must be executed:

o To run the scripts after a specific number of backup copy sessions, select Run scripts every... backup
session option and specify the number of sessions.

o To run the scripts on specific days, select the Run scripts on selected days only option and click the
Da y s button to specify week days.

NOTE

If you select the Run scripts on the selected days only option, Veeam Backup & Replication
executes scripts only once on each selected day — when the job runs for the first time. During
subsequent job runs, scripts are not executed.

1793 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Advanced
If a new restore point is not yet created, you can process the most recent restore point instead of waiting. To do
so, select the P rocess the most recent restore p oint instead of waiting check box.

NOTE

This option is available only in the periodic backup copy job.

1794 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Data Path Settings
The Da ta Transfer step of the wizard is available only if you copy backups of virtual or physical machines created
by Veeam Backup & Replication or Veeam Agents.

At this step of the wizard, you can select how Veeam Backup & Replication will transport backed up data —
directly or through WAN accelerators. By default, during the backup copy job Veeam Backup & Replication
transports data directly from the source backup repository to target backup repository. This type of transport is
recommended if you plan to copy backup files over high-speed connections.

If you plan to copy backup files over WAN or slow connections, it is recommended that you configure source and
target WAN accelerators in the backup infrastructure and copy backups through these WAN accelerators. For
more information, see WAN Acceleration.

To use WAN acceleration for the backup copy job:

1. At the Da ta Transfer step of the wizard, select the Through built-in W AN accelerators option.

2. From the Source WAN accelerator list, select a WAN accelerator configured in the source site.

3. From the Ta rget WAN accelerator list, select a WAN accelerator configured in the target site.

Requirements and Limitations for WAN Accelerators


• You must not assign one source WAN accelerator to several backup copy jobs that you plan to run
simultaneously.

The source WAN accelerator requires a lot of CPU and RAM resources and does not process multiple
backup copy tasks in parallel. As an alternative, you can create one backup copy job for all workloads you
plan to process over one source WAN accelerator. The target WAN accelerator, however, can be assigned
to several backup copy jobs.

• [For WAN accelerators with the high bandwidth mode disabled] It is recommended that you pre-populate
the global cache on the target WAN accelerator before you start the backup copy job. Global cache
population helps reduce the amount of traffic transferred over WAN. For more information, see Populating
Global Cache.

• You cannot use WAN accelerators for backup copy jobs that copy backups of Amazon EC2 instances.

1795 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Define Backup Copy Window
At the Schedule step of the wizard, you can define a time span in which the b ackup copy job will transport data
between source and target backup repositories. For more information, see Backup Copy Window.

To define a backup window for the periodic backup copy job:

1. Select the Run the job automatically check box.

2. Select the required backup window option.

o Da ily at this time. You can specify the time and select the days option from the drop -down list on
which the backup copy job will run: E veryday, On weekdays or On these days. If you select On these
d a ys option, click Da ys to specify them.

o Monthly at this time. You can specify the time and select the day options from the drop -down lists on
which the backup copy job will run. Click Months to specify months on which the backup copy job will
run.

o P eriodically every. You can select the time options from the drop-down list or click Schedule to select
the desired time area. Use the P ermitted and Denied options to mark the selected time segments. Use
Sta rt time within an hour option to specify minutes.

o After this job. If you choose this option, select the job from the drop-down list after which the backup
copy job will start.

3. To configure the backup copy job automatic retries, select the Retry failed items processing check box and
specify the amount of retries and time intervals between them.

4. Select the Terminate job if it exceeds allowed backup window check box if you want the job to terminate
itself to prevent performance impact during production hours. Click W indow to select the desired backup
window time area. Use the P ermitted and Denied options to mark the selected time segments.

To define a backup window for the immediate backup copy job:

1. Select when the job can transfer data:

o Any time

o During the following time periods only

1796 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. If you selected the During the following time periods only option, specify the required backup window
option. Use the E na ble and Disable options to mark the selected time segments as allowed or prohibited
for the backup copy job.

1797 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of backup copy job configuration:

1. Review details of the backup copy job.

2. Select the E na ble the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

1798 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Backup Copy Jobs for HPE
StoreOnce Repositories
To copy backup files between HPE StoreOnce backup repositories, you must configure a backup copy job for
HPE StoreOnce repositories.

Unlike other backup copy jobs, the backup copy job for HPE StoreOnce mirrors data from the source repository.
This backup copy job copies backup files as they are stored in the source repository, without any transformation.
To copy the backup files, Veeam Backup & Replication uses the HPE StoreOnce Catalyst Copy technology.

The backup copy job copies only backup files created by backup jobs and other backup copy jobs. The backup
files must be of the following types:

• Backup files of VMware vSphere and Microsoft Hyper-V VMs created by Veeam Backup & Replication. Log
backup files are not copied.

• Physical machine backup files created by Veeam Agent backup jobs managed by the backup server.

• Backup files of Nutanix AHV VMs created by Veeam Backup for Nutanix AHV.

• Backup files of RHV VMs created by Veeam Backup for RHV.

• Backups copied to an HPE StoreOnce repository by other backup copy jobs (regular backup copy jobs and
backup copy jobs for HPE StoreOnce repositories).

IMP ORTANT

Consider the following limitations:

• The backup jobs must be configured on the same backup server where you configure the backup
copy job for HPE StoreOnce repositories. Backups created by jobs configured on other backup
servers are not copied.
• The backup copy jobs for HPE StoreOnce repositories do not copy imported backups.
• To copy backups created by other backup copy jobs (regular backup copy jobs), you must enable the
GFS retention for these backup copy jobs. For more information on how to enable the GFS retention,
see Specify Target Repository and Retention Settings.

When the backup copy job for HPE StoreOnce runs for the first time, it copies all existing backup files. Then the
backup copy job starts each time a new backup file appears in the source repository. In case of a removed
backup file, the backup copy job waits 21 days since the backup file creation and after rem oves the backup file
from the target repository. If 21 days have already passed at the moment of removal, the backup copy job
removes the backup file immediately. You can change this day limit in the backup copy job settings. For more
information, see Maintenance Settings.

Before creating a job, check prerequisites and limitations. Then use the New Backup Copy Job wizard to
configure the backup copy job.

1799 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you create a backup copy job for HPE StoreOnce backup repository, check the following requirements:

• The minimum supported software versions of HPE StoreOnce are the following:

o For the third generation, the minimum version is 3.18.18.

o For the fourth generation, the minimum version is 4.2.3.

• Make sure that all backup infrastructure components that take part in the backup copy process are added
to the backup infrastructure. These components include the source and target repositories between which
data is copied. For more information on how to add a backup repository, see Adding Backup Repositories.

• Check that repositories between which you plan to copy data have a direct connection to each other. This
is required because Veeam Backup & Replication uses the HPE StoreOnce Catalyst Copy technology to
copy backup files.

This direct connection must be of the same type as the connection that you select when adding the target
HPE StoreOnce. For example, if you connected the target HPE StoreOnce repository over Fibre Channel,
you must connect the source HPE StoreOnce to the target HPE StoreOnce over Fibre Channel.

• HPE StoreOnce repositories connected over Fibre Channel require the two-way connection. Zone the
source initiator World Wide Names (WWNs) with the destination target WWNs, and zone the destination
initiator WWNs with the source target WWNs.

• If you plan to use pre-job and post-job scripts, you must create scripts before you configure the backup
copy job.

• [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] If source backup repository has
backup immutability disabled while the target repository is immutable, backup copy job will work in non-
immutable mode.

• If source and target HPE StoreOnce backup repositories are configured with different block chunking
algorithm, backup copy job will copy the data without changing the block sizes.

1800 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Backup Copy Job Wizard
To run the New Backup Copy Job wizard, do one of the following:

• On the Home tab, click Ba ckup Copy and click Storage copy.

• Open the Home view, in the inventory pane right-click Job s or right-click anywhere in the working area,
click Ba ckup Copy and click Storage copy.

1801 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Job step of the wizard, specify name and description for the backup copy job:

1. In the Na me field, enter a name for the job.

2. In the Description field, enter a description for the job. The default description contains information about
the user who created the job, date and time when the job was created.

1802 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Source and Target Repositories
At the Storage Mapping step of the wizard, select a source repository from which you want to copy backups and
a target repository where you want to store the copies.

1. Click Ad d to open the Ad d Repository window.

2. From the Source backup repository list, select a backup repository from which you want to copy backup
files. The unsupported backup repositories are not shown in the list.

3. From the Ta rget backup repository list, select a backup repository where you want to store the copies. The
unsupported backup repositories are not shown in the list.

IMP ORTANT

Veeam Backup & Replication does not copy all types of backups. For the list of supported backup types,
see Creating Backup Copy Jobs for HPE StoreOnce Repositories.

Requirements and Limitations for Source and Target


Repositories
When you create backup copy jobs, check the following prerequisites and limitations for the source and target
repositories:

• The source and target backup repositories must be HPE StoreOnce backup repositories or scal e-out
backup repositories that consist of HPE StoreOnce repositories only.

• [For scale-out backup repositories] The file placement policy must be Data locality. For more information,
see Data locality.

• Within one backup copy job, you can use each repository as a source only once.

• You must not create the same pairs of source and target repositories, even in different backup copy jobs.

1803 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Data Flow
When you create backup copy jobs, check that you do not create loops in data flow across all backup copy jobs.
This means that data copied from one repository must not be copied to it again. The following image shows
backup copy jobs configured correctly (without loops) and incorrectly (with loops).

1804 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Advanced Settings
At the Storage Mapping step of the wizard, you can specify the following settings for the backup copy job:

• Maintenance Settings

• Notification Settings

• Script Settings

TIP

After you specify necessary settings for the backup copy job, you can save them as default settings. To do
this, click Sa ve as Default at the bottom left corner of the Ad vanced Settings window. When you create a
new backup copy job, Veeam Backup & Replication will automatically apply the default settings to the new
job.

Maintenance Settings
In the maintenance settings, you can configure whether to perform a health check and after which period delete
from the target HPE StoreOnce repository files deleted from the source repository. Note that the health check
may lower the performance of the target repository. For details, see Health Check for Backup Files.

1. At the Storage Mapping step of the wizard, click Ad vanced.

2. To disable the health check, clear the P erform backup files health check check box. By default the health
check is enabled.

3. In the Keep secondary copies for additional field, specify after which period delete files from the target
repository after they were deleted from the source repository.

The backup copy job waits the specified number of days since the backup file creation and after deletes
the backup file from the target repository. If the specified number of days has already passed at the
moment of deletion, the backup copy job deletes the backup file immediately.

4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

IMP ORTANT

Veeam Backup & Replication does not perform the health check for encrypted and compressed backup
files.

1805 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Notification Settings
To specify notification settings for the backup copy job:

1. At the Storage Mapping step of the wizard, click Ad vanced.

2. Click the Notifications tab.

3. Select the Send SNMP notifications for this job check box if you want to receive SNMP traps when data
from each source repository is copied.

SNMP traps will be sent if you specify global SNMP settings in Veeam Backup & Replication and configure
software on the recipient machine to receive SNMP traps. For more information, see Specifying SNMP
Settings.

4. Select the Send email notifications to the following recipients check box if you want to receive email
notifications when copying data of each source repository finishes with Success, Warning or Failed status.

Email notifications will be sent if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Configuring Global Email Notification Settings.

5. You can choose whether to use global notification settings or specify custom notification settings.

o To receive typical notifications for the job, select Use global notification settings. In this case,
Veeam Backup & Replication will apply to the job global email notification settings specified for the
backup server.

o To configure custom notifications, select Use custom notification settings specified below. You can
specify the following notification settings:

i. In the Sub ject field, specify a notification subject. You can use the following variables in the
subject: %Time% (completion time), %JobName%, %JobResult%, %VmCount% (number of
machines in the job) and %Issues% (number of machines in the job that have been processed
with the Warning or Failed status).

ii. Select the Notify on success, Notify on warning and Notify on error check boxes to receive
email notifications if data processing completes successfully, fails or completes with a
warning.

1806 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Script Settings
To specify script settings for the backup copy job:

1. At the Storage Mapping step of the wizard, click Ad vanced.

2. Click the Scripts tab.

3. Select the Run the following script before the job and Run the following script after the job check boxes
to execute custom scripts before and after copying data of each source repository finishes.

Then click Browse and select executable files from a local folder on the backup server. The scripts are
executed on the backup server after the transformation processes are completed on the target repository.

4. You can change how often the scripts must be executed:

o To run scripts after a specific number of backup copy sessions, select Run scripts every... backup
session option and specify the number of sessions.

o To run scripts on specific days, select the Run scripts on selected days only option and click the Da y s
button to specify week days.

NOTE

If you select the Run scripts on the selected days only option, Veeam Backup & Replication
executes scripts only once on each selected day — when the job runs for the first time. During
subsequent job runs, scripts are not executed.

1807 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1808 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Define Backup Copy Window
At the Schedule step of the wizard, you can define a time span in which the backup copy job will transport data
between source and target backup repositories. For more information, see Backup Copy Window.

To define a 'prohibited' period for the backup copy job:

1. Select the During the following time p eriods only option.

2. In the schedule box, select the desired time area.

3. Use the E na bled and Disabled options to mark the selected time segments as allowed or prohibited for the
backup copy job.

1809 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of backup copy job configuration:

1. Review details of the backup copy job.

2. Select the E na ble the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

1810 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Backup Copy Jobs for Veeam
Plug-ins
To create copies of Veeam Plug-in backups of Oracle, SAP HANA and Microsoft SQL Server databases, you must
configure a backup copy job. For more details, see the following sections of the Veeam Plug -ins for Enterprise
Applications Guide:

• Backup Copy for Oracle RMAN Backups

• Backup Copy for SAP on Oracle Backups

• Backup Copy for SAP HANA Backups

• Backup Copy for Microsoft SQL Server Backups

1811 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Linking Backup Jobs to Backup Copy Jobs
You can link backup jobs to backup copy jobs. This option lets you create a secondary target for the backup job
and store backups created by the backup job in the secondary backup repository.

When you link a backup job to the backup copy job, Veeam Backup & Replication automatically updates
properties of the backup copy job and adds to it the backup job as a source of data. During every backup copy
session, the backup copy job checks the source backup repository for new restore points. As soon as a backup
job session is finished and a new restore point appears in the source backup repository, the backup copy job
automatically copies this restore point to the target backup repository.

You can link a backup job to an existing backup copy job using the Ba ckup Job wizard. To link jobs:

1. Open the backup job settings for editing. For more information, see Editing Job Settings.

2. Navigate to the Storage step.

3. Select the Configure secondary destination for this job check box.

4. At the Secondary Target step of the wizard, click Ad d and choose a backup copy job to which the backup
job must be linked. The backup copy job must be already configured on the backup server.

1812 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Backups
To view all backups created by backup copy jobs, open the Home view and select the Ba ck ups > Disk (Copy)
node in the inventory pane. The list of available backups is displayed in the working area. You can view backup
properties, remove unnecessary backups and remove missing restore points.

1813 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Viewing Backup Properties
You can view summary information about backups created by backup copy jobs. The summary information
provides the following data: available restore points, date of restore points creation, compres sion and
deduplication ratios, data size and backup size.

NOTE

Da ta Size represents the size of a backup file before compression and deduplication. Ba ckup Size
represents the size of a backup file after compression and deduplication.

In the summary information, Veeam Backup & Replication displays data about restore points created by the
short-term retention scheme and archive restore points created by the GFS retention scheme (if GFS retention is
enabled). Archive restore points are marked with the following letters:

• R — full backups created with the short-term retention scheme or active full backups

• W — weekly backups

• M — monthly backups

• Y — yearly backups

In the summary information, you can also see the following icons:

Icon Sta te

Full restore point

Incremental restore point

Reverse incremental restore point

Missing full restore point

Missing incremental restore point

To view summary information for a backup copy:

1. Open the Home view.

2. In the inventory pane, select Ba ckups > Disk (copy).

1814 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click the backup copy and select P roperties.

1815 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Upgrading Backup Chain Formats
Veeam Backup & Replication supports the following ways to store backup files: per-machine backup with
separate metadata files, per-machine backup with single metadata file and single-file backup. For more
information, see Backup Chain Formats.

Changing the Use per-machine backup files option for existing backup repositories or moving backups to other
repositories does not change the backup chain format. To change the format, follow the instructions in this
section.

NOTE

Consider the following:

• Before upgrading the backup chain format of backup copy backups, upgrade the backup chain
format of source backups first.
• [For immediate copy mode] If the backup chain is mixed, consists of single-file backups and per-
machine backups with single metadata file, and the last part is per-machine backups with single
metadata file, you cannot change the backup chain format. You need to wait until the backup chain
becomes per-machine.
• Before upgrading the backup chain format, Veeam Backup & Replication disables the job to which
the backups belong. After the upgrade, the job stays disabled, you need to enable it manually.
• You must disable log backup jobs manually before changing the format.
• [For format upgrade using mapping] During the upgrade, Veeam Backup & Replication synthesizes
full backups in the per-machine backup with separate metadata files format using the existing
backup (the source for mapping). That is why you need enough space on the repository to store full
backups. After the successful change operation, the backup used as the source for mapping is placed
to the node with the (Orphaned) postfix. After the successful upgrade, you can delete this orphaned
backup.
• [For periodic copy mode] You can not upgrade the backup chain format of Windows agent failover
cluster backups.
• You can stop an upgrade session only for the backups for which the session has not started. If the
session has started, Veeam Backup & Replication continues the upgrade to avoid backup corruption.

Immediate Copy Mode: Per-Machine Backup with Single


Metadata File to Per-Machine with Separate Metadata Files
To upgrade the backup chain format from per-machine backup with single metadata file to per-machine backup
with separate metadata files, use the upgrade functionality:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary backup copy jobs. Note that the selected jobs must be targeted
to the same repository.

4. Right-click one of the selected jobs and click Up grade backup chain format. Alternatively, click Up grade
Ba ckup Chain Format on the ribbon.

1816 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication will generate new metadata files for the existing backups. After the upgrade, the
job will continue the backup chain and will create per-machine backups with separate metadata files.

Immediate Copy Mode: Single-File Backup to Per-Machine


with Separate Metadata Files
To upgrade the backup chain format from single-file backup to per-machine backup with separate metadata
files, do the following:

1. Detach backups from the backup copy job for whose backups you want to change the backup chain
format. For more information, see Detaching Backups from Jobs.

2. Edit the backup copy job from which you have detached backups.

3. At the Ta rget step of the wizard, map the backup copy job to the detached backups as described in section
Map Backup File.

Alternatively, you can create a new backup copy job as described in subsection Periodic Copy Mode.

Veeam Backup & Replication will start a new backup chain in the required format and will retain the detached
backups according to the background retention. For more information on when the background retention
applies, its limitations and considerations, see Background Retention.

Periodic Copy Mode


To upgrade the backup chain format for the periodic copy mode, do the following:

1. Create a new backup copy job.

2. At the Ob jects step of the wizard, select the same sources as in the backup copy job whose backups you
want to upgrade. Note that you can also add other sources.

3. At the Ta rget step of the wizard, select the backup repository where the backups whose format you want
to change are stored.

4. At the Ta rget step of the wizard, map the backup copy job to the backups as described in section Map
Backup File.

1817 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication will start a new backup chain in the required format and will place the backups
used for mapping to the orphaned node and retain them according to the background retention. For more
information on when the background retention applies, its limitations and considerations, see Background
Retention.

1818 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Moving Backups
Veeam Backup & Replication allows you to move all backups of a backup copy job to another repository or to
move specific workloads and their backups to another backup copy job.

Moving Backups to Another Repository


For information on the move operation, how it works and its limitations, see Backup Move.

To move backups to another repository and target a job to this repository, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary job.

4. Right-click the job and select Move backup. Alternatively, click Move Backup on the ribbon.

5. In the Move Backup to Another Location window, select the repository to which you want to move
backups.

Veeam Backup & Replication will reconfigure and target the backup job to the selected repository.

6. Click OK.

Alternatively, you can change the repository in the job settings.

Moving Backups to Another Job


For information on the move operation, how it works and its limitations, see Backup Move.

1819 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
To move backups to another job:

7. Open the Home view.

8. In the inventory pane, select the Ba ckups node.

9. In the working area, expand the necessary backup job and select workloads.

NOTE

You can move individual workloads and their backups only if backups are per-machine with separate
metadata files for each workload.

10. Right-click one of the selected workloads and click Move backup. Alternatively, click Move Backup on the
ribbon.

11. In the Move Backup to Another Job window, select the backup job to which you want to move backups.

Veeam Backup & Replication will include workloads into the selected job and exclude workloads from the
original job. Backups of the selected workloads will be moved to the repository to which the selected job
is targeted.

12. Click OK.

Managing Failed Activities


If the move operation fails, Veeam Backup & Replication assigns the User action required status to it. In this
case, you need to decide how to finish the operation: retry the move operation for failed workloads, cancel all
changes or move failed workloads but detach their backups. If you detach failed backups, the target job creates
active full backups for failed workloads and continues backup chains for other workloads. The detached backups
are shown in a node with the ( Orphaned) postfix in the inventory pane.

1820 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The original job will still be in the disabled state until you finalize the failed move operation.

To finalize the move operation:

1. Open the Home view.

2. In the inventory pane, select the La st 24 Hours node.

3. Right-click the failed move session and select the required action. Alternatively, select the required action
on the ribbon.

1821 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Copying Backups
Copying backups can be helpful if you want to copy backups of a workload or backup job to another repository,
local or shared folder. Veeam Backup & Replication copies the whole backup chain. If you want to convert a
specific restore point into a single VBK file, use backup export. For more information, see Exporting Backups.

When Veeam Backup & Replication performs the copy operation, it disables the job, copies files to the target
location and then enables the job. After the copy operation finishes, the copied backups are shown in a node
with the ( E xported) postfix in the inventory pane.

NOTE

This section is about one-time copy operation. If you want to copy backups on a schedule, create a backup
copy job. For more information, see Backup Copy.

Requirements and Limitations


Consider the following:

• The copy operation does not change backup chain format (single-file backup, per-machine with single
metadata file or per-machine with separate metadata files). If you copy backups between repositories with
and without the Use p er-machine backup files check box enabled, backups preserve their formats.

• If you copy backups from a scale-out backup repository and some backups are stored on extents in the
Maintenance mode, such backups are not copied.

• Veeam Backup & Replication copies backups only from the performance tier of the scale-out backup
repository. If you want to copy data from the capacity tier, you first must download it to the performance
tier. For more information, see Downloading Data from Capacity Tier.

• You cannot copy backups stored in Veeam Cloud Connect repositories. For more information on Veeam
Cloud Connect repositories, see the Cloud Repository section in the Veeam Cloud Connect Guide.

• [For VMware Cloud Director] You can copy backups of a whole job or individual vApps. You cannot move
backups of VMs.

• You cannot copy backups created by a backup job managed by Veeam Agent (back up policy).

• You cannot copy backups created by Veeam plug-ins for Enterprise applications, Veeam Cloud Plug-ins
(Veeam Backup for AWS, Veeam Backup for Google Cloud, Veeam Backup for Microsoft Azure), and Kasten
K10.

Copying Backups
To copy backups, do the following:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, select the necessary job or workload. Note that you can copy backups of an individual
workload only if its backups are per-machine backups with separate metadata files.

4. Right-click the job and select Cop y backup. Alternatively, click Cop y Backup on the ribbon.

5. In the Cop y Backup to Another Location window, choose where you want to copy backups — to a
repository or to a local or shared folder.

1822 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. If you want to delete the copied backups after a specific time period, select the Delete this backup
a utomatically in check box and specify the time period.

Backups that fall out of the specified retention policy will be removed automatically. If you do not specify
the time period for deletion, copies will be stored until you remove them manually.

7. Click OK.

Managing Failed Activities


If the copy operation fails, Veeam Backup & Replication assigns the User action required status to it. In this case,
you need to decide how to finish the operation: retry the copy operation for failed backups, skip the failed
backups or cancel all changes.

NOTE

The original job will still be in the disabled state until you finalize the failed copy operation.

To finalize the copy operation:

8. Open the Home view.

9. In the inventory pane, select the La st 24 Hours node.

1823 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
10. Right-click the failed copy session and select the required action. Alternatively, select the required action
on the ribbon.

1824 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Backups
You can detach backups from backup copy jobs, permanently delete backups from the target backup
repositories or remove records about backups from the Veeam Backup & Replication console and configuration
database using the Remove from configuration operation.

Detaching from Job


When you detach backup copies from a backup job, the job stops processing these backup files. During the next
run, the job will start a new backup chain, that is, will create active full backups.

Veeam Backup & Replication detaches the whole backup chain including GFS backups. The detached backup files
remain in the backup repository and also in the Veeam Backup & Replication console.
Veeam Backup & Replication shows the detached backups in the inventory pane in the node with the ( Orphaned)
postfix. These backups are retained according to the background retention process. For more information, see
Background Retention.

To detach backups from a backup copy job:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, right-click the backup copy and select Detach from job. Alternatively, click Remove
from > Job on the ribbon.

1825 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Deleting from Disk
When you use the Delete from d isk option, you delete records about backup copies from the
Veeam Backup & Replication console and configuration database, and delete backup files from the target
backup repository. This option can be used for the whole backup copy or for some workloads in the backup
copy.

To permanently remove backup copies from the target backup repository:

1. Open the Home view.

2. In the inventory pane, select Ba ckups.

3. In the working area, right-click the backup copy or a workload in the backup copy and select Delete from
d isk.

4. To remove all weekly, monthly, quarterly and yearly backups from disk, select the Include archived full
b a ckups check box and click Y es .

Removing Backups from Configuration


IMP ORTANT

Removing backups from configuration is designed for experienced users only. Consider using Detach from
job or Delete from disk operations.

When you remove a backup from the configuration, backup files remain in the backup repository. You can import
the backup to Veeam Backup & Replication at any time later and restore data from it.

When you remove an encrypted backup from configuration, Veeam Backup & Replication removes encryption
keys from the configuration database. If you import such backup on the same backup server or another backup
server, you will have to specify the password or unlock the backup with Veeam Backup Enterprise Manager. For
more information, see Importing Encrypted Backups.

1826 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To remove a backup from the configuration:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups node.

3. In the working area, press the [Ctrl] key, right-click the backup that you want to remove and select
Remove from configuration.

1827 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Removing Missing Restore Points
In some cases, one or more restore points in the backup chain may be inaccessible. This can happen, for
example, if the backup repository is put to the Maintenance mode (for scale-out backup repositories), the
backup repository is not available or some backup file is missing in the backup chain. Backup chains that contain
missing restore points get corrupted — you cannot perform backup copy or restore data from the missing restore
point, and restore points that depend on the missing restore point.

You can perform the following with missing restore points:

• Forget — you can remove records about missing restore points from the configuration database.
Veeam Backup & Replication will ignore the missing restore points and will not display them in the
console. The backup files will remain on disk (if backup files are still available).

• Remove — you can remove records about missing restore points from the Veeam Backup & Replication
console and configuration database, and delete backup files from disk (if backup files are still available).

NOTE

Consider the following:

• The Forget and Remove from d isk options are available only for restore points that are missing from
the backup chain or that depend on missing ones.
• You can manually update information about missing restore points. For this, disable a backup copy
job and rescan the backup repository that is the target for the backup copy job. For more
information, see Disabling and Removing Jobs and Rescanning Backup Repositories.
Manual update can be required because Veeam Backup & Replication requires some time to update
information in the configuration database for restore points that were removed from a backup chain
or became inaccessible. That is why such restore points may not be displayed in the console as
missing restore points.

To remove records about missing restore points from the configuration database:

1. Open the Home view.

2. In the inventory pane, select Disk (copy) under Ba ckups.

3. In the working area, select the backup and click P roperties on the ribbon or right-click the backup and
select P roperties.

4. In the Ba ckup Properties window, right-click the missing restore point and select Forget.

o To remove only the selected restore point and restore points that depend on it (that is, a part of the
backup chain starting from this restore point), select This a nd dependent backups.

1828 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To remove all missing restore points, select All unavailable backups.

To remove missing restore points from the configuration database and disk:

1. Open the Home view.

2. In the inventory pane, click Disk (copy) under Ba ckups.

3. In the working area, select the backup and click P roperties on the ribbon or right-click the backup and
select P roperties.

4. In the Ba ckup Properties window, right-click the missing restore point and select Remove from disk.

o To remove only the selected restore point and restore points that depend on it (that is , a part of the
backup chain starting from this restore point), select This a nd dependent backups.

1829 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o To remove all missing restore points, select All unavailable backups.

1830 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Backup Copy Jobs
To view all configured jobs, open the Home view and select the Job s > Ba ckup Copy node in the inventory pane.
The list of available jobs is displayed in the working area. You can edit job properties, start and stop jobs, and
delete unnecessary jobs.

1831 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing Backup Copy Job Settings
You can edit backup copy job settings after you create it. For example, you may want to change scheduling
settings for the job or add some machines to the job.

To edit job settings:

1. Open the Home view.

2. In the inventory pane, select Job s > Ba ckup Copy.

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

You will follow the same steps as you have followed when creating the job and can change job settings as
required.

Related Topics
• Creating Backup Copy Jobs for VMs and Physical Machines

• Creating Backup Copy Jobs for HPE StoreOnce Repositories

• Creating Backup Copy Jobs for Oracle and SAP HANA Databases

Disabling GFS Scheme


If you disable the Keep certain full backups longer for archival purposes option, and you already have archive
full backups in the target backup repository, Veeam Backup & Replication will offer you to remove existing
archive full backups.

• Click Y es to remove archive full backups from the target backup repository. Archive full backups will be
removed during the next retention cycle (next backup copy session). The backup copy job will not create
archive full backups.

• Click No to keep archive full backups in the target backup repository. Archive full backups will be
displayed under the Ba ck ups > Disk (Imported) node in the Veeam Backup & Replication console. The
backup copy job will not create archive full backups.

NOTE

If you disable the Keep certain full backups longer for archival purposes option and enable it again later,
archive full backups that remained on disk will not be linked to the backup copy job. They will still be
displayed under the Ba ck ups > Disk (Imported) node in the Veeam Backup & Replication console.

1832 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1833 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Starting and Stopping Backup Copy Jobs
Manual start can be helpful if the backup copy job was disabled for some time and restore points were not
copied to the target repository. This procedure differs for the periodic and immediate copy modes. You can also
manually stop the periodic backup copy job. For more information, see the following sections:

• Starting Jobs in Immediate Copy Mode

• Starting Jobs in Periodic Copy Mode

• Stopping Jobs in Periodic Copy Mode

NOTE

The immediate backup copy job can only be disabled and can not be stopped.

Starting Jobs in Immediate Copy Mode


To start the backup copy job manually:

1. Open the Home view.

2. In the inventory pane, select the Ba ckup Copy node.

3. In the working area, select the backup copy job and click Sy nc now on the ribbon or right-click the backup
copy job and select Sy nc now.

4. In the opened window, do the following:

o If you want to copy all restore points created by the source jobs but that were not copied since the
last backup copy job session, click All.

o If you want to copy only the latest restore point for each source job, click La test.

1834 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Starting Jobs in Periodic Copy Mode
To start the backup copy job manually:

1. Open the Home view.

2. In the inventory pane, select the Ba ckup Copy node under Job s.

3. In the working area, select the backup copy job and click Sta rt on the ribbon or right-click the backup copy
job and select Sta rt.

Stopping Jobs in Periodic Copy Mode


To stop the backup copy job manually:

1. Open the Home view.

2. In the inventory pane, select the Ba ckup Copy node under Job s.

1835 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the backup copy job and click Stop on the ribbon or right-click the backup copy
job and select Stop .

1836 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Active Full Backups
You can manually create an ad-hoc full backup — active full backup, and add it to the backup chain in the target
backup repository. Active full backup can be helpful if you want to change backup copy job settings, for
example, enable or disable encryption. Veeam Backup & Replication will apply new settings starting from this
full backup.

To create an active full backup manually:

1. Open the Home view.

2. In the inventory pane, select the Ba ckup Copy node under Job s.

3. In the working area, select the backup copy job and click Active full on the ribbon or right-click the backup
copy job and select Active full. Veeam Backup & Replication will start a new backup copy session, copy
data from the source backup repository and save it in a full backup file in the target backup repository.

1837 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disabling and Deleting Backup Copy Jobs
You can temporarily disable backup copy jobs. The disabled job is paused for some period of time and is not run
by the specified schedule. You can enable a disabled job at any time. You can also permanently delete a job from
Veeam Backup & Replication and from the configuration database.

Disabling Job
To disable a job:

1. Open the Home view.

2. In the inventory pane, select Job s > Backup Copy.

3. In the working area, select the job and click Disable on the ribbon or right-click the job and select Disable.

To enable a disabled job, select the job in the list and click Disable once again.

Deleting Job
To delete a job:

1. Open the Home view.

2. In the inventory pane, select Job s > Backup Copy.

3. In the working area, select the job, click Delete on the ribbon or right-click the job and select Delete.

NOTE

If you want to delete an active backup copy job, you must first stop the synchronization process. To
do this, disable the backup job. After the job is disabled, you can delete it.

1838 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
After the job is deleted, the backups created by this job are displayed under the Ba ckups > Disk ( Orphaned)
node. If the backup files created by this job were also stored in an object storage repository, they will also be
displayed under the Ba ck ups > Ob ject Storage (Orphaned) node.

1839 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Reporting
The process of performing reporting operations for backup copy jobs is the same as described in the Backup:
Reporting section. However, the process differs for immediate backup copy jobs created in
Veeam Backup & Replication 11 the following way:

• Viewing real-time statistics

You can view real-time statistics for the whole job if you select the job in the working area of the Job s
node. The whole job report shows general information about the job itself and child jobs — tasks that copy
backup jobs added as sources to the backup copy job. You can also view real-time statistics for an
individual child job if you select the child job in the working area of the La st 24 Hours or Running node.
This statistics shows detailed information about the selected child job including the processed VMs.

• Viewing job session results

You select and view session results for a child job.

• Viewing job reports

The job report shows results for the last job run and does not provide details on child jobs. If you want to
get reports once a child job finishes, configure notifications. For more information, see Notification
Settings.

• Viewing session reports


You can view session reports only if you configured notifications for a job. In this case, you g et reports
once a child job finishes. For more information, see Notification Settings.

1840 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
File Copy
You can copy and move files and folders between servers and hosts added to the backup infrastructure. For file
copying operations, Veeam Backup & Replication offers a Windows Explorer-like user interface familiar to a
Microsoft Windows user. You can copy files manually or schedule file copy jobs to run automatically by the
defined schedule.

The file copy functionality is not intended for creating backups of VM guest OS files. Use backup jobs to create
VM image-level backups instead.

1841 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating File Copy Jobs
To schedule a copying process for files and folders, you must configure a file copy job. You can run the file copy
job immediately after its creation, schedule or save the job.

File copy jobs let you copy files between the following backup infrastructure objects:

• Virtualization hosts

• Microsoft Windows servers

• Linux servers

• ExaGrid storage appliances used as backup repositories

• Quantum DXi

• Fujitsu ETERNUS CS800

• Infinidat InfiniGuard

Before you configure a file copy job, check prerequisites. Then use the New File Copy Job wizard to create a job.

1842 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you configure a file copy job, check the following prerequisites:

Backup infrastructure components that will take part in the file copying process must be added to the backup
infrastructure and properly configured. These include a source and target host or server between which files and
folders will be copied.

Consider the following limitations:

• File copy is not supported for Unix systems, for example, Solaris, FreeBSD and AIX.

• Veeam Backup & Replication does not preserve the Access Control List (ACL) settings for copied guest OS
folders. The ACL settings are preserved for files only.

TIP

You can restore the ACL settings for recovered guest OS files and folders using Guest OS File Restore.

1843 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New File Copy Job Wizard
To launch the New File Copy Job wizard, do either of the following:

• On the Home tab, click Cop y Job > File.

• Open the Files view, in the working area right-click the necessary files and folders and select Ad d to File
Cop y Job > New job. Veeam Backup & Replication will start the New File Copy Job wizard and add selected
files and folders to this job. You can add other files and folders to the job later on, when you pass through
the wizard steps.

You can add files and folders to already existing jobs. To do this, open the Files view, in the working area right-
click necessary objects and select Ad d to File Copy Job > Name of the job.

1844 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Na me step of the wizard, enter a name and description of the created job.

1. In the Na me field, enter a name for the file copy job.

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

1845 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Files and Folders to Be Copied
At the Source step of the wizard, select files and folders that you want to copy.

To select files and folders that you want to copy:

1. Click Ad d to open the Select File or Folder window.

2. From the Server list, choose a host or server on which files or folders that you want to copy reside.

3. Select files or folders that must be copied. The selected items will be added to the list.

IMP ORTANT

If the list contains files/folders with the same names and extensions, Veeam Backup & Replication copies
only one instance of a file/folder. This limitation applies even if you add files/folders from different hosts
or servers. To avoid this limitation, you can rename files/folders on the source or add parent folders to the
list.

To remove a file or folder from the list, select it and click Remove.

1846 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Destination for Copying
At the Destination step of the wizard, select a destination to which files or folders must be copied.

1. From the Server list, select the target host or server.

2. Click Details on the right of the Server field to view or edit server properties.

3. Click Browse next to the P a th to folder field and select a folder where copied items must be stored. To
create a dedicated folder for copied files or folders, use the New Folder button at the bottom of the Select
Fold er window.

IMP ORTANT

If the target folder already contains files/folders with the same names and extensions as the files/folder
that must be copied, Veeam Backup & Replication will replace files/folders in the target folder with new
files/folders.

1847 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Define Job Schedule
At the Schedule step of the wizard, you can select to run the file copy job manually or schedule the job to run on
a regular basis.

To specify the job schedule:

1. Select the Run the job automatically check box. If this check box is not selected, you will have to start the
job manually to copy files or folders.

2. Define scheduling settings for the job:

o To run the job at specific time daily, on defined week days or with specific periodicity, select Da ily at
this time. Use the fields on the right to configure the necessary schedule.

o To run the job once a month on specific days, select Monthly at this time. Use the fields on the right
to configure the necessary schedule.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for example,
related to daylight saving time transition).

o To run the job repeatedly throughout a day with a set time interval, select P eriodically every. In the
field on the right, select the necessary time unit: Hours or Minutes. Click Schedule and use the time
table to define the permitted time window for the job. In the Sta rt time within an hour field, specify
the exact time when the job must start.

A repeatedly run job is started by the following rules:

▪ Veeam Backup & Replication always starts counting defined intervals from 12:00 AM. For
example, if you configure to run a job with a 4-hour interval, the job will start at 12:00 AM, 4:00
AM, 8:00 AM, 12:00 PM, 4:00 PM and so on.

▪ If you define permitted hours for the job, after the denied interval is over,
Veeam Backup & Replication will immediately start the job and then run the job by the defined
schedule.

For example, you have configured a job to run with a 2-hour interval and defined permitted hours
from 9:00 AM to 5:00 PM. According to the rules above, the job will first run at 9:00 AM, when the
denied period is over. After that, the job will run at 10:00 AM, 12:00 PM, 2:00 PM and 4:00 PM.

o To run the job continuously, select the P eriodically every option and choose Continuously from the
list on the right.

1848 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o To chain jobs, use the After this job field. In the common practice, jobs start one after another: when
job A finishes, job B starts and so on. If you want to create a chain of jobs, you should define the time
schedule for the first job in the chain. For the rest of the jobs in the chain, at the Schedule step of the
wizard, select the After this job option and choose the preceding job from the list.

1849 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of file copy job configuration.

1. Review details for the created file copy job.

2. Select the Run the job when I click Finish check box if you want to start the job right after you finish
working with the wizard.

3. Click Finish to close the wizard.

1850 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Copying Files and Folders Manually
You can manually copy and move files and folders between servers and hosts added to the backup
infrastructure.

Veeam Backup & Replication lets you copy files manually between the following backup infrastructure objects:

• Virtualization hosts

• Microsoft Windows servers

• Linux servers

• Deduplicating storage appliances used as backup repositories

IMP ORTANT

You cannot copy backup files (VBK, VIB and VRB) to HPE StoreOnce storage appliances used as backup
repositories. To copy such files, use backup copy jobs.

To copy files and folders:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the source server or host.

3. Right-click files and folders that you want to copy and select Cop y.

4. In the inventory pane, expand the file tree of the target server or host.

5. Right-click a destination folder and select P a ste.

You can also use a drag-n-drop operation to copy files and folders between the source and target hosts or
servers.

1851 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Folders
You can create, rename and delete folders in the Files view of Veeam Backup & Replication.

To create a folder:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the necessary server or host.

3. In the working area, right-click anywhere on the blank area and select New Folder.

To rename a folder:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the necessary server or host.

3. In the working area, select the folder and click Rename on the ribbon or right-click the folder and select
Rena me.

4. Enter a new name for the folder and press [Enter] on the key board.

To remove a folder:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the necessary server or host.

3. In the working area, select the folder and click Delete on the ribbon or right-click the folder and select
Delete.

1852 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Editing and Deleting Files
You can edit files and delete them in the Files view of Veeam Backup & Replication. For example, you may want
to delete from the storage files of unused VMs.

To edit a file:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the necessary server or host.

3. In the working area, select the file and click E d it on the ribbon or right-click the folder and select E d it.

4. Veeam Backup & Replication will open the selected file in the editor. Edit the file as required a nd click
Sa ve on the file editor toolbar or press [Ctrl+S] on the keyboard.

To delete a file:

1. Open the Files view.

2. In the inventory pane, expand the file tree of the necessary server or host.

3. In the working area, select the file and click Delete on the ribbon or right-click the folder and select
Delete.

1853 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Recovery Verification
Veeam Backup & Replication offers the SureBackup technology that lets you verify recoverability of VM backups
and scan them for malware.

IMP ORTANT

The recovery verification functionality is included in the Veeam Universal License.

When using a legacy socket-based license, Enterprise or higher edition is required. If you use the Standard
edition, you can manually verify VM backups with Instant Recovery. For more information, see Manual
Recovery Verification.

1854 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
SureBackup
SureBackup is the Veeam technology that allows you to test machines backups and check if you can recover data
from them. You can verify any restore point of a backed -up machine.

1855 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How SureBackup Works
For SureBackup, Veeam Backup & Replication uses a regular image-based backup. SureBackup job can operate in
two different recovery verification modes:

• Full recoverability testing. Veeam Backup & Replication runs machines in an isolated environment directly
from backup and performs tests against live applications.This mode ensures recoverability of your
production workloads in a disaster recovery event.

• [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] Ba ckup verification a nd
content scan only. Veeam Backup & Replication performs backup integrity check and its content analysis
to detect traces of malware or any other unwanted or sensitive data. These tests do no require setting up
a virtual lab or an application group.

Full Recoverability Testing


During the full recoverability testing, Veeam Backup & Replication performs the following actions:

1. If the SureBackup job is configured to perform malware scan, Veeam Backup & Replication scans data of
the machines from the application group and the machine under verification with antivirus software and
the specified YARA rule.

2. Veeam Backup & Replication publishes the machines from the application group and the machine under
verification in the isolated environment — virtual lab. Machines are started directly from compressed and
deduplicated backup files that reside in the backup repository. To achieve this,
Veeam Backup & Replication utilizes Instant Recovery to Microsoft Hyper-V.

3. Veeam Backup & Replication performs a number of tests against the machines in the application group and
the machine under verification: heartbeat test, ping test and application test.

4. If the SureBackup job is configured to validate backup files, Veeam Backup & Replication performs a cyclic
redundancy check for the backup file from which the machine under verification is started and, optionally,
for backup files from which the machines in the application group are started. The backup file validation is
performed after all verification tests are complete.

5. When the recovery verification process is over, Veeam Backup & Replication unpublishes machines and
creates a report on their state. The report is sent to the backup administrator by email.

During verification, a backed-up machine image remains in read-only state. All changes that take place when the
machine is running are written to the differencing disk (AVHD/AVHDX file), created for the recovered machine.
When the recovery verification process is complete, the changes are discarded.

To perform recovery verification, you need to create the following objects:

1. Application group. During recovery verification, the verified machine may need to be started with a group
of machines on which it is dependent. The application group enables full functionality of applications
running inside the machine and lets you run these applications just like in the production environment.

1856 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Virtual lab. The virtual lab is the isolated virtual environment in which the verified machine and machines
from the application group are started and tested.

3. SureBackup job. The SureBackup job is a task to perform recovery verification. You can run the SureBackup
job manually or schedule it to run automatically by schedule.

Backup verification and content scan only


During the backup verification and content scan, Veeam Backup & Replication performs the following actions:

1. If the SureBackup job is configured to perform malware scan, Veeam Backup & Replication scans data of
the machines from the linked job with antivirus software and the specified YARA rule.

2. If the SureBackup job is configured to validate backup files, Veeam Backup & Replication performs a cyclic
redundancy check for the backup file from which the machine under verification is started. The b ackup file
validation is performed after all verification tests are complete.

3. When the recovery verification process is over, Veeam Backup & Replication creates a report on the
machines' state. The report is sent to the backup administrator by email.

During verification, a backed-up machine image remains in read-only state. All changes that take place when the
machine is running are written to the differencing disk (AVHD/AVHDX file), created for the recovered machine.
When the recovery verification process is complete, the changes are discarded.

1857 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Backup Recovery Verification Tests
To verify machines with a SureBackup job in Full recoverability testing mode, you can instruct
Veeam Backup & Replication to run the following backup recovery verification tests:

• Predefined tests

• Custom verification scripts

When running a SureBackup job in Ba ckup verification and content scan only mode, you can only instruct
Veeam Backup & Replication to perform backup integrity check.

Predefined Tests
Veeam Backup & Replication can verify machines with the following predefined tests:

• Hea rtbeat test. When the machine starts, Veeam Backup & Replication performs a heartbeat test. It waits
for a heartbeat signal from Hyper-V Integration Services installed inside the machine to determine that
the machine guest OS is running. If the signal comes regularly at specific time intervals , the test is passed.

• P ing test. Veeam Backup & Replication sends ping requests to the machine from the backup server and
checks if the machine can respond to them. If the machine responds to ping requests, the test is passed.

Veeam Backup & Replication uses two algorithms for detecting the IP addresses of a Hyper-V machine:

o Veeam Backup & Replication communicates with Hyper-V Integration Services installed inside the
machine guest OS to detect the machine IP address.

o Veeam Backup & Replication uses a special module in the proxy appliance to check the IP addresses of
the machine started in the isolated network. This algorithm is used, for example, if the machine does
not have Hyper-V Integration Services installed.

• Ap p lication test. Veeam Backup & Replication waits for applications inside the machine to start and runs a
script against these applications. Veeam Backup & Replication uses two types of predefined scripts:

o For DNS servers, domain controllers, Global Catalog servers, mail servers and web servers,
Veeam Backup & Replication uses a script that probes an application-specific port. For example, to
verify a domain controller, Veeam Backup & Replication probes port 389 for a response. If the
response is received, the test is passed.

o For Microsoft SQL Server, Veeam Backup & Replication uses a script that attempts to connect to
instances and databases on the Microsoft SQL Server. For more information, see Microsoft SQL Server
Checker Script.

NOTE

To run the heartbeat test, you must have Hyper-V Integration Services installed inside the machine. If
Hyper-V Integration Services are not installed, this test will be skipped.

1858 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
You can run verification tests for machines added to the application group or processed with a linked
SureBackup job. Settings for verification tests can be specified and customized in the application group or
SureBackup job settings.

Custom Verification Scripts


Veeam Backup & Replication can verify VMs with the following custom verification scripts:

• Microsoft SQL Server Checker script

• Backup file validation

IMP ORTANT

Consider the following:

• Do not pass sensitive information using script arguments in a user interface.


• If you use the Microsoft SQL Server authentication mode, you may need to specify credentials of the
account to connect to the machine on which Microsoft SQL Server is installed. To do this, use the
Credentials tab in the application group or SureBackup job settings.
• You can not use domain credentials for the script execution if you have Veeam Backup & Replication
deployed in Microsoft Azure and it is managed by Microsoft Intune. Use local credentials for
Microsoft SQL Server instead.
• During the major version upgrade procedure (for example, from version 11 to version
12), Veeam Backup & Replication may replace the SQL checker script with the default one. If you
have manually modified the SQL checker script before upgrading to a new version, reapply those
modifications after the update.

Microsoft SQL Server Checker Script


If you need to verify a virtualized Microsoft SQL Server, you can instruct Veeam Backup & Replication to run the
Microsoft SQL Server Checker script against it during the SureBackup job. The script sequentially performs the
following operations:

1. Connects to Microsoft SQL Server instances.

2. Enumerates databases on these instances.

1859 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Employs the USE SQL statement to connect to databases and check their availability.

The script is located on the backup server in the Veeam Backup & Replication product folder. The path by
default: C:\Program Files\Veeam\Backup and
Replication\Backup\Veeam.Backup.SqlChecker.vbs.

Credentials for Script Execution


To execute the script, Veeam Backup & Replication connects to Microsoft SQL Server. By default,
Veeam Backup & Replication uses the account under which the Veeam Backup Service is running. If you need to
run the script under another account, you can specify credentials for this account. The script supports the
following authentication methods:

• Microsoft Windows authentication mode. To use it, you must specify credentials for the account on the
Credentials tab in the application group or SureBackup job settings.

• SQL Server authentication mode. To use it, you must pass credentials of the account to the script. You can
pass credentials the following ways:

o By running the Microsoft SQL Server Checker Script from the PowerShell. To do it, use the following
command in the PowerShell console:

cscript C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Back


up.SqlChecker.vbs <sql server[\instance]> <username> <password>

You can find the results of a script execution in the log file by the following path:
%programdata%\Veeam\Backup\<name of the job>\<VM name>_SQLChecker.log. If
necessary, you can change the log file location. To do this, specify a new path in the PowerShell
command:

cscript C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Back


up.SqlChecker.vbs [C:\Logs] <sql server[\instance]> <username> <passwor
d>

o By modifying credentials in the Veeam.Backup.SqlChecker.vbs file. The script is located on the


backup server in the Veeam Backup & Replication product folder. The default path: C:\Program
Files\Veeam\Backup and Replication\Backup\Veeam.Backup.SqlChecker.vbs.

Da tabase Exclusion

By default, Veeam Backup & Replication verifies all databases on all instances of Microsoft SQL Server.
However, you can exclude specific databases from verifica tion. For example, vCenter Server database. To
exclude an instance or a database, you must open the script in the text editor and edit the Settings section in
the following way:

• To exclude a specific databases, uncomment the gDBsToExclude.Push "dbname" line in the script and
specify the names of a database that you want to exclude. To exclude several databases, specify a
separate line for each database.

gDBsToExclude.Push "dbname1"
gDBsToExclude.Push "dbname2"

• To exclude a specific instance, uncomment the gInstancesToExclude.Push "instancename" line in


the script and specify the name of an instance that you want to exclude. To exclude several instances,
specify a separate line for each instance.

1860 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
gInstancesToExclude.Push "instancename1"
gInstancesToExclude.Push "instancename2"

• To exclude the default instance, uncomment the gInstancesToExclude.Push "MSSQLSERVER" line.

IMP ORTANT

Instance and database names are case sensitive.

Log ging

To define whether the script has completed successfully or not, Veeam Backup & Replication publishes the
following return codes in the SureBackup job session statistics:

• 0 — test is passed successfully.

• 1 — you use a wrong syntax for the script command.

• 2 — Veeam Backup & Replication is unable to connect to Microsoft SQL Server.

• 3 — all instances are excluded from the check.

• 4 — error occurred while Veeam Backup & Replication was getting the list of databases.

• 5 — unknown error.

• 6 — one or more databases are not accessible.

Results of script execution are written to the log file located by the following path:
%programdata%\Veeam\Backup\<name of the job>\<VM name>_SQLChecker.log. If necessary, you
can change the log file location. To do this, pass a new path to the log file in the %log_path% argument in the
application group or SureBackup job settings.

Backup File Validation


In addition to recovery verification tests, Veeam Backup & Replication allows you to perform backup file
validation. For backup file validation, Veeam Backup & Replication performs a CRC check for backup files of
machines verified by the SureBackup job. You can also validate backup files for machines from the application
group with this test.

To validate the backup file, Veeam Backup & Replication uses the checksum algorithm. When
Veeam Backup & Replication creates a backup file for a machine, it calculates a checksum for every data block in
the backup file and stores this data in the backup file, together with machine data. During the backup file
validation test, Veeam Backup & Replication decompresses the backup file, recalculates checksums for data
blocks in the decompressed backup file and compares them with initial checksum values. If the results match,
the test is passed.

The backup file validation test is started after recovery verification tests. As soon as
Veeam Backup & Replication completes all "live" verification for all machines in the SureBackup job, it
unpublishes machines and starts the backup file validation test.

1861 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
The result of the backup file validation test impacts the state of the SureBackup job session. If the verification
tests are completed successfully but the backup validation is not passed, Veeam Backup & Replication marks the
SureBackup job session with the Failed status.

1862 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Application Group
In most cases, a machine works not alone but in cooperation with other services and components. To verify such
machine, you first need to start all services and components on which this machine is dependent. To this aim,
Veeam Backup & Replication uses the application group.

The application group creates the “surroundings” for the verified machine. The application group contains one
or several machines on which the verified machine is dependent. These machines run applications and services
that must be started to enable fully functional work of the verified machine. Typically, the application group
contains at least a domain controller, DNS server and DHCP server.

When you set up an application group, you specify a role of every machine, its boot priority and boot delay.
Additionally, you can specify what tests must be performed to verify machines in the application group.

When a SureBackup job is launched, Veeam Backup & Replication first starts in the virtual lab machines from the
application group in the required order and performs necessary tests against them. This way,
Veeam Backup & Replication creates the necessary environment for the verified machine. Only after all
machines from the application group are started and tested, Veeam Backup & Replication starts the verified
machine in the virtual lab.

For example, if you want to verify a Microsoft Exchange Server, you need to test its functionality in cooperation
with the domain controller and DNS server. Subsequently, you must add to the application group a virtualized
domain controller and DNS server. When Veeam Backup & Replication runs a SureBackup job, it will first start
and verify the domain controller and DNS server in the virtual lab to make verification of the Microsoft Exchange
Server possible.

Creating Application Group


Before you create an application group, check prerequisites. Then use the New Ap plication Group wizard to
create an application group.

Before You Begin


Before you create and start a recovery verification job, check the following prerequisites:

• A valid license for Enterprise edition of Veeam Backup & Replication must be installed on the backup
server.

• All applications and services on which verified VMs are dependent must be virtual ized in your
environment.

• If you plan to scan VMs data for malware, check requirements and limitations.

• If you plan to verify VMs with a ping test, the firewall on tested VMs must allow ping requests.

• If you plan to verify VMs with a heartbeat test, Hyper-V Integration Services must be installed in tested
VMs.

• To open a console of a verified VM, you must have the RDP client version 7.0 and later installed on the
backup server. The RDP client is pre-installed on Microsoft Windows 7 OS and later.

Consider that you cannot add to application groups VMs from backups created with backup copy jobs and
backups stored in Cloud Connect backup repositories.

1863 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Application Group Wizard
To launch the New Application Group wizard, do one of the following:

• Open the Ba ckup Infrastructure view, in the inventory pane select SureBackup. In the working area, click
Ad d Application Group.

• Open the Ba ckup Infrastructure view, in the inventory pane select Ap p lication Groups under SureBackup
and click Ad d App Group.

• Open the Ba ckup Infrastructure view, in the inventory pane right-click Ap p lication Groups under
SureBackup and select Ad d App Group.

1864 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Application Group Name and Description
At the Na me step of the wizard, specify a name and description for the application group.

1. In the Na me field, enter a name for the application group.

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

1865 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Add Machines to Application Group
At the Ma chines step of the wizard, add machines to the created application group.

To add machines to the application group:

1. Click Ad d and select From backups, From replicas or From storage snapshots.

2. In the displayed window, expand the job or storage snapshot, select the machine and click Ad d .

3. Machines in the list are specified in the order of their boot priority. To move a machine up and down in the
list, select it and click Move Up or Move Down.

IMP ORTANT

If you are planning to use Microsoft Hyper-V platform, Veeam Backup & Replication supports only
machines added from backups.

To remove a machine from the list, select it and click Remove.

1866 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Recovery Verification Options and Tests
You must specify verification options for every machine in the application group:

• Select a role that a VM performs

• Configure startup settings

• Select tests that must be performed for the VM

• Specify credentials for running the verification script

To specify recovery verification options:

1. At the Ma chines step of the wizard, select a machine in the list.

2. Click E d it on the right.

3. Use the Verification Options window to specify verification options.

Role Settings
On the Role tab, select the role that the VM performs. Veeam Backup & Replication offers the following
predefined roles for VMs:

• DNS Server

• Domain Controller (Authoritative Restore). In the Authoritative Restore mode,


Veeam Backup & Replication starts a domain controller in the virtual lab and marks it as being
authoritative to its replication partners. When other domain controllers (replication partners) are started
in the virtual lab, they replicate data from the domain controller started in the Authoritative Restore
mode.

• Domain Controller (Non-Authoritative Restore). In the Non-Authoritative Restore mode,


Veeam Backup & Replication restores a domain controller in the virtual lab and marks it as being non-
authoritative to its replication partners. Non-authoritative domain controllers then replicate data from a
domain controller started in the Authoritative Restore mode.

• Global Catalog

• Mail Server

• SQL Server

• Veeam Backup for Microsoft 365 (machine on which Veeam Backup for Microsoft 365 is installed)

• Web Server

VM roles are described in XML files stored in the %ProgramFiles%\Veeam\Backup and


Replication\Backup\SbRoles folder on the backup server. You can add your own roles. To do this, you need to
create a new XML file and specify role and test scripts settings in it. For more information, see Creating XML
files with VM Roles Description.

After you select a role for the VM, Veeam Backup & Replication will automatically configure startup options and
assign predefined test scripts for the chosen role. You can use these settings or specify custom settings on the
Sta rtup Options and Test Scripts tabs.

To verify VMs that perform roles other than those specified in the list, you will have to manually configure
startup options and specify test scripts that must be run for these VMs.

1867 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
IMP ORTANT

If you want to add several domain controllers to the application group, you must assign the Doma in
Controller (Authoritative Restore) role to the first domain controller started in the virtual lab. Other
domain controllers must have the Doma in Controller (Non-Authoritative Restore) role.

Startup Settings
To specify VM startup settings:

1. Click the Sta rtup Options tab.

2. In the Memory section, specify the amount of memory that you want to pre-allocate to the VM on the
system boot. The amount of pre-allocated memory is defined in percent. The percentage rate is calculated
based on the system memory level available for the production VM. For example, if 1024 MB of RAM is
allocated to the VM in the production and you specify 80% as a memory rate, 820 Mb of RAM will be
allocated to the verified VM on startup.

Veeam Backup & Replication does not allow you to change VM CPU manually, it does this automatically. If
the VM has more CPU than the host can provide, Veeam Backup & Replication scales down the CPU of the
VM.

3. In the Sta rtup time section, specify the allowed boot time for the VM and timeout to initialize applications
on the VM.

Be careful when specifying the Ma x imum allowed boot time value. Typically, a VM started by a
SureBackup job requires more time to boot than a VM started in the production environment. If a VM is
not initialized within the specified interval of time, the recovery verification process fails with the timeout
error. If such error occurs, you need to increase the Ma x imum allowed boot time value and start the job
again.

4. In the Boot verification section, specify when the VM must be considered to have been booted
successfully:

o VM heartbeat is present. If you select this option, Veeam Backup & Replication will perform a
heartbeat test for the verified VM.

o VM responds to ping on any network interface. If you select this option, Veeam Backup & Replication
will perform a ping test for the verified VM.

1868 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Automatically disable Windows Firewall. If you select this option, Veeam Backup & Replication will
disable Windows Firewall for the the verified VM.

If you enable both heartbeat test and ping test options, Veeam Backup & Replication will require that both
tests are completed successfully.

IMP ORTANT

To be able to perform the heartbeat test, Veeam Backup & Replication requires Hyper-V Integration
Services to be installed in verified VM. If Hyper-V Integration Services are not installed, the VM will be
started but the test will not be performed.

Test Script Settings


When you select a VM role, Veeam Backup & Replication automatically assigns a predefined script that must be
run to verify applications inside the VM. If you want to verify a VM that has some other role not listed on the
Role tab, do the following:

1. Click the Test Scripts tab.

2. Click Ad d .

3. In the Test Scripts window, select Use the following test script.

4. In the Na me field, specify a name for the script.

5. In the P a th field, define a path to an executable script file that should be run to verify the VM.

o If you have your own custom script, define a path to it in the P a th field.

o If you do not have a custom script, you can use a standard utility by Veeam,
Veeam.Backup.ConnectionTester.exe , that probes application communication ports. The utility is
located in the installation folder of Veeam Backup & Replication: %ProgramFiles%\Veeam\Backup
and Replication\Backup\Veeam.Backup.ConnectionTester.exe . Specify this path in the P a th field.

6. In the Arg uments field, specify an IP address of the verified VM and the port that you want to probe (if the
selected test probes the port). You can use the %vm_ip% variable to define the VM IP address or the
%vm_fqdn% variable to define the VM fully qualified domain name.
For Microsoft SQL Server, you can also specify a path to the log file in the %log_path% argument. For
more information, see Backup Recovery Verification Tests.

1869 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
7. Click OK to add the configured test.

To edit test settings, select the test in the list and click E d it. To delete a test, select it in the list and click
Remove.

IMP ORTANT

Do not pass sensitive information using script arguments in a user interface.

NOTE

If a VM performs several roles and runs a number of applications, you can verify their work by adding
several verification scripts. It is recommended that you specify the maximum startup timeout value and
allocate the greatest amount of memory for such VMs.

Credentials Settings
By default, to run the verification script Veeam Backup & Replication uses the account under which the Veeam
Backup Service is running. If you need to run the script under some other account, you can specify credentials
for this account in the application group settings.

1. Click the Credentials tab.

1870 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. From the Credentials list, select credentials for the account under which you want to run the script.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add the credentials. For more information, see Managing Credentials.

1871 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Review the Application Group Settings and Finish Working with
Wizard
At the Summary step of the wizard, complete the procedure of application group configuration.

1. Review details of the application group.

2. Click Finish to save the application group settings and close the wizard.

1872 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Virtual Lab
The virtual lab is an isolated virtual environment in which Veeam Backup & Replication verifies VMs. In the
virtual lab, Veeam Backup & Replication starts VMs from the application group and the verified VM. The virtual
lab is used not only for the SureBackup verification procedure, but also for U-AIR, On-Demand Sandbox and
staged restore.

The virtual lab itself does not require that you provision extra resources for it. However, VMs running in the
virtual lab consume CPU and memory resources of the Hyper-V host where the virtual lab is deployed. All VM
changes that take place during recovery verification are written to the differencing disk (AVHD/AVHDX file)
which Veeam Backup & Replication creates for the recovered VM. When the recovery verification process is
complete, the changes are discarded.

The virtual lab is fully fenced off from the production environment. The network configuration of the virtual lab
mirrors the network configuration of the production environment. For example, if verified VMs and VMs from
the application group are located in two logical networks in the production environment, the virtual lab will also
have two networks. The networks in the virtual lab will be mapped to necessary production networks.

VMs in isolated networks have the same IP addresses as in the production network. This lets VMs in the virtual
lab function just as if they function in the production environment.

Proxy Appliance
To enable communication between the production environment and isolated networks in the virtual lab,
Veeam Backup & Replication uses a proxy appliance. The proxy appliance is an auxiliary Linux -based VM that is
deployed on the Hyper-V host where the virtual lab is created. The proxy appliance VM is assigned an IP address
from the production network and placed to the dedicated virtual lab folder on the Hyper-V host.

The proxy appliance is connected to the production network and to the isolated network, so that it has visibility
of the production environment and virtual lab. In essence, the proxy applia nce acts as a gateway between the
two networks — it routes requests from the production environment to VMs in the virtual lab.

To connect to isolated networks, the proxy appliance uses network adapters. Veeam Backup & Replication adds
to the proxy appliance one network adapter per every isolated network. For example, if there are two networks
in the virtual lab, Veeam Backup & Replication will add two network adapters to the proxy appliance. The
network adapter gets an IP address from the isolated network. Typically, this IP address is the same as the IP
address of the default gateway in the production network.

1873 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The proxy appliance is an optional component for recovery verification. Technically, you can create a virtual lab
without the proxy appliance. However, in this case, you will not be able to perform automatic recovery
verification of VMs. VMs will be started from backups in the virtual lab; you will have to access them using the
VM console and perform necessary tests manually.

IP Masquerading
To let the traffic into the virtual lab, Veeam Backup & Replication uses masquerade IP addressing.

Every VM in the virtual lab has a masquerade IP address, along with the IP address from the production network.
The masquerade IP address resembles the IP address in the production network. For example, if the IP address
of a VM is 172.16.1.13, the masquerade IP address may be 172.18.1.13.

The masquerade IP address is an "entry point" to the VM in the virtual lab from the production environment.
When you want to access a specific VM in the virtual lab, Veeam Backup & Replication addresses it by its
masquerade IP address.

The rules that route requests to VMs in the virtual lab are specified in the routing table on the server from which
you want to access VMs in the virtual lab. The routing table can be updated on the following servers:

• Ba ckup server. Veeam Backup & Replication automatically creates the necessary static routes in the
routing table on the backup server at the moment you launch a SureBackup job and
Veeam Backup & Replication starts the virtual lab.

1874 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Client machine. If you want to provide your users with access to VMs in the virtual lab, you need to
manually update routing tables on their machines and add new static routes. For more information, see
Static IP Mapping.

The added static route destines the masquerade network traffic to the proxy appliance. The proxy appliance acts
as a NAT device: it resolves the masquerade IP address, replaces it with “real” IP address of the VM from the
production network and then directs the request to the necessary VM in the virtual lab. The static route is non-
persistent: when you power off the virtual lab, the route is removed from the routing table on the backup server
or client machine.

For example, when trying to access a VM with IP address 172.16.10.10 in the isolated network,
Veeam Backup & Replication sends a request to the masquerade IP address 172.18.10.10. According to the
routing rule added to the IP routing table, all requests a re first sent to the next hop — the proxy appliance. The
proxy appliance performs address translation, substitutes the masquerade IP address with the IP address in the
isolated network, and forwards the request to the necessary VM in the isolated network — in this example, to
172.16.10.10.

Static IP Mapping
Sometimes it is necessary to provide many clients with access to a restored VM, which is especially the case for
user-directed application item-level recovery. For example, you may want to provide users with access to the
Microsoft Exchange Server started in the virtual lab using web -based access (like Outlook Web Access).
Technically, you may update the routing table on every client machine; however, this will demand a lot of
administrative effort.

For such situations, Veeam Backup & Replication lets you get access to a VM in the virtual lab directly from the
production environment. To access a VM in the virtual lab, you must reserve a static IP address in the pool of
production IP addresses and map this IP address to the IP address of a VM in the virtual lab.

1875 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The static IP address is assigned to the proxy appliance network adapter connected to the production network.
IP traffic directed to the specified static IP address is routed by the proxy appliance to the VM in the isolated
network.

For example, for a VM with IP address 192.168.1.20 in the isolated network, you can reserve IP address
192.168.1.99 (a free IP address from the production network). As a result, you will be able to use IP address
192.168.1.99 to access the VM in the virtual lab from the production side.

You can also register an alias record in the production DNS server for the reserved IP address. For example, you
can register backup.exchange.local as an alias for the IP address 192.168.1.99, and users will be able to access
Microsoft Exchange Server by this alias.

Virtual Lab Configuration


For SureBackup recovery verification, Veeam Backup & Replication offers two types of the virtual lab
configuration:

• Basic single-host virtual lab

• Advanced single-host virtual lab

Basic Single-Host Virtual Labs


The basic single-host virtual lab can be used if all VMs that you want to verify, VMs from the application group
and the backup server are connected to the same network.

For the basic single-host virtual lab, Veeam Backup & Replication creates one virtual network that is mapped to
the necesary production network. Veeam Backup & Replication adds a new virtual switch for the virtual lab. The
added virtual switch is only used by VMs started in the virtual lab. There is no routing outside the virtual lab to
other networks.

1876 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication automatically configures all settings for the basic single-host virtual lab. The proxy
appliance is also created and configured automatically on the Hyper-V host where the virtual lab is created.

Advanced Single-Host Virtual Labs


The advanced single-host virtual lab can be used if VMs that you want to verify and VMs from the application
group are connected to different networks.

In the advanced single-host virtual lab, Veeam Backup & Replication creates several virtual networks for the
virtual lab. The number of virtual networks corresponds to the number of production networks to which veri fied
VMs are connected. Networks in the virtual lab are mapped to production networks.

Veeam Backup & Replication adds a new virtual switch for every network in the virtual lab. For example, if you
have two networks in the production environment, Veeam Backup & Replication will create two networks in the
virtual lab and add two virtual switches for every network on the Hyper-V host. The added virtual switches are
only used by the VMs started in the virtual lab. There is no routing outside the virtual lab to other networks.

When you create an advanced single-host virtual lab, Veeam Backup & Replication configures basic settings for
networks that are created in the virtual lab. You need to review these settings and manually adjust them.

Creating Virtual Lab


Before you create a new virtual lab, check prerequisites. Then use the New Virtual Lab wizard to create a virtual
lab.

1877 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you create a virtual lab, check the following prerequisites:

• A valid license for Enterprise edition of Veeam Backup & Replication must be installed on the backup
server.

• You can configure a virtual lab on the following types of hosts:

o Microsoft Windows Server 2022 with the Hyper-V role enabled

o Microsoft Windows Server 2019 with the Hyper-V role enabled

o Microsoft Hyper-V Server 2019

o Microsoft Windows Server 2016 with the Hyper-V role enabled

o Microsoft Hyper-V Server 2016

o Microsoft Windows Server 2012 R2 with the Hyper-V role enabled

o Microsoft Hyper-V Server 2012 R2

o Microsoft Windows Server 2012 with the Hyper-V role enabled

o Microsoft Hyper-V Server 2012

o Microsoft Windows 10 with the Hyper-V role enabled

o Microsoft Windows 11 with the Hyper-V role enabled

NOTE

Starting from Veeam Backup & Replication 12, you can verify VMware vSphere backups and Veeam Agent
backups using Hyper-V virtual lab. To learn about SureBackup limitations for Veeam Agent backups, see
Veeam Agent Management Guide.

1878 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Virtual Lab Wizard
To launch the New Virtual Lab wizard, do one of the following:

• Open the Ba ckup Infrastructure view, in the inventory pane select SureBackup. In the working area, click
Ad d Virtual Lab > Hy per-V.

• Open the Ba ckup Infrastructure view, in the inventory pane select Virtual Labs under SureBackup and click
Ad d Virtual Lab > Microsoft Hyper-V.

• Open the Ba ckup Infrastructure view, in the inventory pane right-click Virtual Labs under SureBackup and
select Ad d Virtual Lab > Microsoft Hyper-V.

1879 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Virtual Lab Name and Description
At the Na me step of the wizard, specify a name and description for the virtual lab.

1. In the Na me field, enter a name for the virtual lab.

2. In the Description field, provide a description for future reference. The default description contains
information about the user who created the virtual lab, date and time when the lab was created.

1880 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Host
At the Destination step of the wizard, select a Microsoft Hyper-V host on which the virtual lab must be created.

1. Click Choose next to the Host field to select a Microsoft Hyper-V host. You can select a standalone Hyper-
V host or host being a part of the Hyper-V cluster.

2. For every new virtual lab, Veeam Backup & Replication creates a dedicated folder on the host, by default,
C:\VeeamVirtualLabs\. To specify another folder, click Choose next to the P a th field and select the
necessary folder.

To the virtual lab folder, Veeam Backup & Replication copies files of the proxy appliance. The folder is also used
as a mount point for VMs started in the virtual lab. In this folder, Veeam Backup & Replication “publishes”
virtual disk and configuration files of verified VMs and VMs from the application group. These files are visible to
the user as having the size of original VM files.

Veeam Backup & Replication emulates the presence of VM files in the virtual lab folder. The virtual disks
themselves are still located in the backup file in the backup repository. All VM changes that take place during
recovery verification are written to the differencing disk (AVHD/AVHDX file) which Veeam Backup & Replication
creates for the recovered VM. When the recovery verification process is complete, the changes are discarded.
For more information, see How SureBackup Works.

1881 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Set Up Proxy Appliance
At the P roxy step of the wizard, configure the proxy appliance settings.

1. Select the Use p roxy appliance in this virtual lab check box to enable automatic recovery verification of
VMs. The proxy appliance acts as a gateway that provides access from the backup server to VMs in the
virtual lab. If you do not select this check box, during recovery verification Veeam Backup & Replication
will only start VMs in the virtual lab and perform the heartbeat test for VMs. You will have to manually
test VMs or perform manual item-level restore using the VM console.

2. By default, the proxy appliance uses the virtual lab name that you have specified at the Na me step of the
wizard. If you want to change a name of the proxy appliance, click E d it and specify the necessary name.

3. Click Configure and select a production network in which the proxy appliance will be created. Select IPv4
or IPv6 or use both. Specify an IP address for the proxy appliance in the production network and settings
of the DNS server to be used. You can choose to automatically obtain an IP address and DNS server
settings or set them manually.

IMP ORTANT

If you assign to the proxy appliance an IP address from the same network where the backup server is
located, Veeam Backup & Replication will automatically add a new route to the routing table on the backup
server. If you assign to the proxy appliance an IP address from a different network, you will have to
manually add a new route to the routing table on the router in the production network. If you do not add a
new route, tests and application scripts will fail and you will not be able to access VMs in isolated
networks.
When Veeam Backup & Replication starts a virtual lab, it verifies if the proxy appliance is available by
sending a ping request to it. If the corresponding route is not added to the routing table, the SureBackup
job will fail.

4. If you want to let VMs in the virtual lab access the internet, select the Allow p roxy appliance to act as
internet proxy for virtual machines in this lab check box. In the P ort field, specify a port for HTTP traffic.
By default, port 8080 is used. In the P roduction proxy field, you can optionally specify an IP address or a
fully qualified domain name of an Internet-facing proxy server that VMs must use to access the Internet.

5. Adjust proxy settings in the Internet options on every VM that you plan to start in the virtua l lab. To do
this, on the VM open Internet Options > Connections > LAN Settings > P roxy server and specify the IP
address of the proxy appliance on the isolated network and port number.

NOTE

When you allow the proxy appliance to act as an internet proxy, you enable the HTTP(S) internet access for
VMs in the virtual lab. The proxy appliance does not proxy other protocols (such as ICMP protocol used for
ping tests) for VMs in the virtual lab.

1882 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1883 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Networking Mode
At the Networking step of the wizard, select the type of network settings configuration.
Veeam Backup & Replication offers two networking modes for the virtual lab:

• Ba sic single-host. This networking mode is recommended if all VMs that you plan to verify, VMs from the
application group and the backup server are located in the same production network. In this case,
Veeam Backup & Replication will automatically define all networking settings for the virtual lab.

• Ad vanced single -host. This networking mode is recommended if VMs that you plan to verify and/or VMs
from the application group are located in different networks. In this case, you will have to manually define
settings for isolated networks in the virtual lab.

If this option is selected, the New Virtual Lab wizard will include additional steps for customizing network
settings.

1884 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Isolated Networks
The Isolated Networks step of the wizard is available if you have selected the advanced networking option at
the Networking step of the wizard.

At the Isolated Networks step of the wizard, you must create isolated networks to which verified VMs and VMs
from the application group will be connected and map these networks to production networks where original
VMs are located.

You can configure two types of mapping rules:

• Mapping rules for networks without VLANs

• Mapping rules for networks with VLANs

Mapping Rules for Networks Without VLANs


To add a network:

1. Click Ad d .

2. From the P roduction network list, select a production network in which VMs from the application group
and/or verified VMs reside.

3. In the Isolated network field, specify a name for an isolated network that must be mapped to this
production network. You can specify a new name to create a new isolated network or select the existing
isolated network from the drop-down list.

4. In the VLAN ID field, enter an ID for the created isolated network.

NOTE

You can map several production networks to the same isolated network. The production networks that you
plan to map must have the same network masks and pools of IP addresses.

Mapping Rules for Networks with VLANs


If you use VLANs in your production network, you can create several isolated networks and ma p them to
different VLANs. As a result, the networking scheme in the virtual lab will resemble the networking scheme in
your production environment.

1885 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To create mapping rules for a network with several VLANs:

1. Click Ad d .

2. From the P roduction network list, select a production network in which the VLAN you want to map is
created.

3. In the VLAN ID field below, specify an ID of the VLAN in the production network.

4. In the Isolated network field, specify a name for an isolated network that you want to map to the VLAN.
You can specify a new name to create a new isolated network or select the existing isolated network from
the drop-down list.

5. In the VLAN ID field, enter an ID for this isolated network.

6. Repeat steps 1-5 for every VLAN in your production network.

For example, you have 3 VLANs in your production networks: VLAN 100, VLAN 200 and VLAN 300. In this case,
you can create 3 isolated networks and map them to VLANs in the following way:

• Isolated network 1 is mapped to VLAN 100

• Isolated network 2 is mapped to VLAN 200

• Isolated network 3 is mapped to VLAN 300

In the virtual lab, Veeam Backup & Replication will create 3 isolated networks and 3 virtual switches for these
networks and connect VMs to corresponding virtual switches. VMs in the virtual lab will function as they
function in the production environment.

1886 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Network Settings
The Network Settings step of the wizard is available if you have selected the advanced networking option at the
Networking step of the wizard.

At the Network Settings step of the wizard, you must specify settings for every created isolated network and
define how production networks map to isolated networks in the virtual lab.

Communication between production networks and isolated networks is carried out through network adapters
that are added to the proxy appliance. A new network adapter must be added for every isolated network. If you
are planning to use IPv4 and IPv6 in your virtual lab, you must create a vNIC for each p rotocol.

To add a network adapter for an isolated network:

1. At the Network Settings step of the wizard, click Ad d .

2. If you have both IPv4 and IPv6 enabled, select the required IP address.

3. Select a network to which the network adapter must be connected. Specify an IP address that the proxy
appliance must have in the isolated network and a subnet mask or prefix length of this isolated network.
For IPv6, specify a prefix length instead of a subnet mask. Typically, the IP address for the proxy appliance
coincides with the IP address of the gateway in the corresponding production network.

4. After you specify the IP address, Veeam Backup & Replication will automatically configure a masquerade
IP address for accessing VMs in the virtual lab from the production network. You can change the
masquerade network IP address if necessary.

5. Select the E na ble DHCP service on this interface check box if you need to dynamically assign IP addresses
for machines. The assigned IP addresses belong to the current isolated network.

6. Click the DNS Servers button and specify settings of a virtualized DNS server if necessary. Click OK.

7. To enable communication between isolated networks, select the Route network traffic b etween vNICs
check box. Make sure that the IP address of the proxy appliance in the isolated network matches the IP
address of the gateway in the production network.

IMP ORTANT

Consider the following:

• You cannot assign more than one vNIC to a single isolated network for each protocol.
• Network addresses specified for different vNIC adapters must belong to different networks. For
example, if the first network adapter has the 192.168.0.1 IP address and the network mask is
255.255.255.0, and the second one — 192.168.0.2 and the network mask is 255.255.255.0, such
configuration will not work. In this situation, you need to assign to the second adapter an IP address
from a different network, for example, 172.16.0.1.
• If you assign more than 1 network adapter (or IP address) to one production VM,
Veeam Backup & Replication will apply the predefined tests only to one of these IP addresses. For
more information on the predefined tests, see Predefined tests.

1887 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
1888 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Static IP Mapping Rules
The Sta tic Mapping step of the wizard is available if you have selected the advanced networking option at the
Networking step of the wizard.

At the Sta tic Mapping step of the wizard, you can specify static IP address mapping rules to make VMs in the
virtual lab accessible from any machine in the production network.

To add a new rule:

1. Select the Define static IP address mapping check box.

2. Click Ad d .

3. If you have both IPv4 and IPv6 enabled, select the required address mapping.

4. In the IP Address Mapping window, specify settings of a new rule:

a. From the P roduction network drop-down list, select a production network in which a VM from the
application group or verified VM resides.

b. In the Isolated IP field, specify an IP address of the VM in the production network.

c. In the Access IP field, specify an IP address in the production network that you want to use to access
the VM in the virtual lab. You must use an IP address that is not allocated to any machine yet.

NOTE

It is recommended that you assign an access IP from the same subnet where the proxy appliance resides. In
the opposite case, you will have to configure routing rules for the access IP manually.

For example, the DNS server you plan to start in the virtual lab has IP address 172.17.53.2 in the production
network. To set static mapping for the DNS server:

1. In the Isolated IP field, you need to define its production IP address — 172.17.53.2.

2. In the Access IP field, you need to define any unallocated IP address from the production network, for
example, 172.17.53.162.

After a virtual lab is created and VMs are started in the virtual lab, you will be able to access the DNS server in
the virtual lab from the production environment using IP address 172.17.53.162.

1889 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Apply Parameters
At the Rea dy to Apply step of the wizard, complete the procedure of virtual lab configuration.

1. Review details of the virtual lab.

2. Click Ap p ly to create the virtual lab.

3. At the last step of the wizard, click Finish to exit the wizard.

Connecting to Existing Virtual Lab


You can connect an existing virtual lab and use this virtual lab for recovery verification. For example, you can
connect to a virtual lab that has been created on another backup server.

To connect to a virtual lab:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Virtual Labs under SureBackup and click Connect Virtual Lab > Hyper-V on
the ribbon or right-click Virtual Labs and select Connect Virtual Lab > Hyper-V.

1890 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Select the virtual lab and click Connect. To quickly find a virtual lab, use the search field at the bottom of
the Select Virtual Lab window: enter a virtual lab name or a part of it in the field below and pres s [Enter]
on the keyboard.

Editing and Deleting Virtual Labs


You can edit settings of a virtual lab or delete the virtual lab.

Always use Veeam Backup & Replication to modify or delete a virtual lab. If you change lab settings or delete
any of its components from outside, for example, in Hyper-V Manager, the lab will be corrupted and its
component such as the created virtual switch will remain in the virtual infrastructure.

To edit settings of a virtual lab:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Virtual Labs under SureBackup.

3. In the working area, select a virtual lab and click E d it Virtual Lab on the ribbon or right-click the virtual lab
and select P roperties.

4. Edit virtual lab settings as required.

To remove a virtual lab:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, select Virtual Labs under SureBackup.

3. In the working area, select a virtual lab and click Remove Virtual Lab on the ribbon or right-click the
virtual lab and select Delete.

1891 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to remove virtual lab objects from the virtual environment, in the displayed window select the
Remove virtual lab objects from host check box. If you do not select this option,
Veeam Backup & Replication will disconnect the virtual lab from the backup server. You will be able to
connect to this virtual lab later.

1892 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
SureBackup Job
A SureBackup job is a task for recovery verification. The SureBackup job can run in two different modes: Full
recoverability testing and Ba ckup verification and content scan only.

In the Full recoverability testing mode, the SureBackup job aggregates all settings and policies of the recovery
verification task such as application group and virtual lab to be used, machine backups that must be verified in
the virtual lab, and so on. It runs machines in an isolated environment directly from backup and performs tests
against live applications.This mode ensures recoverability of your production workloads in a disaster recovery
event.

[For Veeam Backup & Replication version 12 (12.1 (build 12.1.0.2131)) and later] In the Ba ckup verification and
content scan only mode, the SureBackup job performs only backup integrity check and its content analysis to
detect traces of malware or any other unwanted or sensitive data. These tests do no require setting up a virtual
lab or an application group.

You can run the SureBackup job manually or schedule it to run automatically.

When a SureBackup job runs in the Full recoverability testing mode, Veeam Backup & Replication first creates an
environment for recovery verification:

1. Veeam Backup & Replication starts the virtual lab.

2. In the virtual lab, Veeam Backup & Replication starts machines from the application group in the required
order. Machines from the application group remain running until verified machines (machines from the
linked job) are booted from backups and tested.

If Veeam Backup & Replication does not find a valid restore point for any of machines from the application
group, the SureBackup job fails.

3. When the virtual lab is ready, Veeam Backup & Replication starts verified machines to the necessary
restore point and, depending on the job settings, verifies them one by one or creates several streams and
verifies a number of machines simultaneously.

If Veeam Backup & Replication does not find a valid restore point for any of verified machines, verification
of this machine fails, but the job continues to run.

By default, you can start and test up to three machines at the same time. You can also increase the number of
machines to be started and tested simultaneously. Keep in mind that if these machines are resource demanding,
performance of the SureBackup job as well as performance of the Hyper -V host on which the virtual lab resides
may decrease.

Once the verification process is complete, machines from the application group are powered off. Optionally, you
can leave machines from the application group running to perform manual verification or enable user -directed
application item-level recovery.

In some cases, the SureBackup job schedule may overlap the schedule of the backup job linked to it. The backup
file may be locked by the backup job and the SureBackup job will be unable to verify such backup. In this
situation, Veeam Backup & Replication will not start the SureBackup job until the backup job is over.

To overcome the situation of job overlapping, you may chain the backup and SureBackup jobs or define the
timeout period for the SureBackup job. For more information, see Specifying Job Schedule.

SureBackup Job Processing


SureBackup job processing depends on the verification mode, Full recoverability testing mode or Ba ckup
verification and content scan only mode.

1893 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Full recoverability testing
The recovery verification process in Full recoverability testing mode includes the following steps:

1. Getting virtual lab configuration. Veeam Backup & Replication gets information about configuration of the
virtual lab where verified VMs must be started.

2. Sta rting proxy appliance VM . Veeam Backup & Replication starts the proxy appliance. The proxy appliance
is used as a gateway that provides access to the virtual lab.

3. Configuring network routes. Veeam Backup & Replication adds to the routing table on the backup server
new routes for the networks created in the virtual lab.

4. P erforming malware scan. If the recovery verification process includes malware scan and YARA rule scan,
Veeam Backup & Replication scans VM data with antivirus software and the YARA rule.

After the malware and the YARA scan, Veeam Backup & Replication runs recovery verification tests for this
VM.

Veeam Backup & Replication verifies VMs sequentially — one after another. For example, when the
malware scan and recovery verification tests for VM A complete, Veeam Backup & Replication verifies VM
B, and so on.

5. P reparing application group. In the virtual lab, Veeam Backup & Replication starts VMs from the
application group in the specified order and performs necessary tests for them.

6. P erforming verification tasks. In the virtual lab, Veeam Backup & Replication starts verified VMs and
performs necessary tests for them.

7. P erforming heartbeat test . Veeam Backup & Replication checks whether the Hyper-V Integration Services
heartbeat signal is coming from the VM or not. If the VM has no Hyper-V Integration Services, the test is
not performed and a notification is written to the job session details.

8. Running p ing tests. Veeam Backup & Replication checks if the VM responds to the ping requests or not. If
the VM has no network adapters or mapped networks for them, the ping test is not performed and a
notification is written to the job session details.

9. Ap p lication initialization. Veeam Backup & Replication waits for the applications installed in the VM, for
example, Microsoft SQL Server, to start. The application initialization period is defined in settings of the
SureBackup job and by default is equal to 120 sec.

Depending on the software installed in a VM, the application initialization process may require more time
than specified in the job settings. If applications installed in a VM are not initialized within the specified
period of time, test scripts can be completed with errors. If such error situation occurs, you will need to
increase the Application initialization timeout value and start the job once again.

10. Running test scripts. Veeam Backup & Replication runs scripts to test whether the application installed in
the VM is working correctly or not. If there are no network adapters on the VM or mapped networks for
them, Veeam Backup & Replication skips tests that use the %vm_ip% and %vm_fqdn% variables as the IP
address and FQDM of the VM cannot be determined.

Test results are written to the job session details. To define whether the script is completed success fully
or not, Veeam Backup & Replication uses return codes. If the return code is equal to 0, the script is
considered to complete successfully. Other values in the return code mean that the script failed.

11. P owering off. After all tests were performed, Veeam Backup & Replication powers off the verified VM and
unregisters it on the Hyper-V host.

12. Running backup integrity check. After a VM was verified and powered off, Veeam Backup & Replication
runs a CRC check to verify the VM backup at the file level and make sure that this file is not corrupted.

13. Stopping virtual lab engine. Veeam Backup & Replication powers off the proxy appliance in the virtual lab.

1894 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
14. Deleting network routes. Veeam Backup & Replication deletes added network routes from the routing
table on the backup server.

Stabilization Algorithm
To be able to perform tests for a verified VM without errors, Veeam Backup & Replication needs to know that
the VM is ready for testing. To determine this, Veeam Backup & Replication waits for the VM to reach a
stabilization point: that is, waits for the VM to boot completely and report it is ready for tests. After the
stabilization point has been established, Veeam Backup & Replication can start performing heartbeat tests, ping
tests and running test scripts against the VM.

Veeam Backup & Replication establishes the stabilization point with the help of VMware parameters that it gets
from the VM. Depending on the VM configuration, it uses one of three algorithms to do that:

• Sta bilization by IP. This algorithm is used if the VM has network adapters and there are mapped networks
for these network adapters. In this case, Veeam Backup & Replication waits for an IP address of the VM for
mapped networks that is sent by Hyper-V Integration Services running in the VM or by the Hyper-V host
through the proxy appliance. The sent IP address must be valid and must not change for a specific period
of time. For more information, see Recovery Verification Tests.

• Sta bilization by heartbeat. This algorithm is used if the VM has Hyper-V Integration Services installed but
there are no network adapters and mapped networks for them. In this case, Veeam Backup & Replication
waits for a heartbeat signal from Hyper-V Integration Services installed inside the VM.

• Hy b rid heartbeat/IP algorithm. Veeam Backup & Replication uses both the heartbeat signal (if available)
and an IP of the VM to stabilize the VM boot process.

• Sta bilization by Maximum allowed b oot time. This algorithm is used if the VM has neither Hyper-V
Integration Services installed, nor network adapters and mapped networks for them. In this case,
Veeam Backup & Replication waits for the time specified in the Ma x imum allowed boot time field, which is
considered to be a stabilization period for the VM. Once this time interval is exceeded,
Veeam Backup & Replication considers that the VM runs successfully and it is ready for testing.

When the stabilization point has been established, Veeam Backup & Replication runs ping, heartbeat tests and
performs test scripts against the verified VM.

The stabilization process cannot exceed the time specified in the Ma x imum allowed boot time field. For this
reason, you should be careful when specifying this value. Typically, a VM started by a SureBackup job requires
more time to boot than a VM started in the production environment. If the stabilization point cannot be
determined within the Ma x imum allowed boot time, the recovery verification process is finished with the
timeout error. When such an error occurs, you need to increase the Ma x imum allowed boot time value and start
the job again.

Backup verification and content scan only


[For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] The recovery verification process
includes the following steps:

1. P erforming malware scan. If the recovery verification process includes malware scan and YARA rule scan,
Veeam Backup & Replication scans VM data with antivirus software and the YARA rule.

After the malware and the YARA scan, Veeam Backup & Replication registers the VM on the selected ESXi
host and runs recovery verification tests for this VM.

Veeam Backup & Replication verifies VMs sequentially — one after another. For example, when the
malware scan and recovery verification tests for VM A complete, Veeam Backup & Replication verifies VM
B, and so on.

1895 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Running backup integrity check. Veeam Backup & Replication runs a CRC check to verify the VM backup at
the file level and make sure that this file is not corrupted.

Creating SureBackup Job


To create a new SureBackup job, use the New SureBackup Job wizard.

Before You Begin


Before you create and start a recovery verification job, check the following prerequisites:

• A valid Veeam Universal License of Veeam Backup & Replication must be installed on the backup server.
When using a legacy socket-based license, Enterprise or higher edition is required.

• All applications and services on which verified machines are dependent must be virtualized in your
environment.

• You must create or connect a virtual lab. For more information, see sections Creating Virtual Lab and
Connecting to Existing Virtual Lab.

• If you plan to scan machine data for malware, check requirements and limitations.

• If you plan to verify machines with a ping test, the firewall on tested machines must allow ping requests.

• If you plan to verify machines with a heartbeat test, Hyper-V Integration Services must be installed in
tested machines.

• To open a console of a verified machine, you must have the RDP client version 7.0 and later installed on
the backup server. The RDP client is pre-installed on Microsoft Windows 7 OS and later.

Consider the following limitations:

• You cannot link to SureBackup job machines from backups created by backup copy jobs and backups
stored in cloud backup repositories.

• The source backup job has a higher priority than the SureBackup job. If the source backup job starts when
the SureBackup job is running, and this job is about to modify the restore point from which the VM is
started, Veeam Backup & Replication automatically powers off VMs in the virtual lab and completes the
SureBackup job.

1896 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New SureBackup Job Wizard
To launch the New SureBackup Job wizard, do either of the following:

• Open the Home view. On the Home tab, click SureBackup Job on the ribbon.

• Open the Home view. In the inventory pane, right-click SureBackup under Job s and select SureBackup.

You can use this method if you already have at least one SureBackup job. If there are no SureBackup jobs,
the SureBackup node will not be displayed in the inventory pane. In this case, you can right-click Job s in
the inventory pane and select SureBackup.

1897 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Job Name and Description
At the Na me step of the wizard, specify a name, description and verification mode for the SureBackup job.

1. In the Na me field, enter a name for the SureBackup job.

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

3. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] Select the verification mode,
Full recoverability testing or Ba ckup verification a nd content scan only.

1898 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Virtual Lab
Selecting virtual lab is available only for SureBackup job working in Full recoverability testing mode.

At the Virtual Lab step of the wizard, select a virtual lab that you want to use for recovery verification.

[For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] If you do not have a virtual lab, click
Ad d New and complete the New Virtual Lab wizard to create a new virtual lab.

1. From the Virtual Lab list, select a virtual lab. The list contains all virtual labs that are created or connected
to the backup server.

2. In the Virtual lab info section, review information about the selected virtual lab.

1899 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Application Group
Selecting application group is available only for SureBackup job working in Full recoverability testing mode.

At the Ap p lication Group step of the wizard, select an application group that you want to use for recovery
verification.

You can select an application group or skip this step. If the application group is not selected, you must link at
least one backup job to the SureBackup job at the Linked Jobs step of the wizard. In this case, when the
SureBackup job starts, Veeam Backup & Replication will only run machines from the linked job in the virtual lab
and verify these machines.

To select an application group:

1. From the Ap p lication group list, select an application group. The list contains all application groups that
are created on the backup server.

2. In the Ap p lication group info list, refer to the Source Status column to make sure that backups and
replicas for machines in the application group are created.

3. To leave machines from the application group running after the SureBackup job finishes, select the Keep
the a pplication group running after the job completes check box. With this option enabled, the lab will not
be powered off when the SureBackup job completes, and you will be able to perform application item -
level restore (U-AIR) and manually test machines started in the virtual lab.

1900 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Link Backup Job
At the Link ed Jobs step of the wizard, select backup jobs with machines that you want to verify with the created
SureBackup job.

You can link a backup job to the SureBackup job or skip this step. If you do not link a backup job, in Full
recoverability testing mode Veeam Backup & Replication will only start machines from the application group in
the virtual lab and verify them. You have an option not to link a backup job to the SureBackup job only if you
have selected an application group at the Application Group step of the wizard.

Linking Backup Job in Veeam Backup & Replication 12.1


To link a backup job to the SureBackup job:

1. [For full recoverability testing mode] Select the Test backups of the following backup jobs check box.

2. Click Ad d .

3. In the Select Jobs window, select backup jobs.

4. In the P rocess simultaneously up to … machines field, specify the maximum number of machines (from a
linked job) that can be started at the same time. For example, if you select to start three machines at the
same time, Veeam Backup & Replication will create three streams — one stream per every verified
machine. All three machines will be tested together. But if you select to start one machine, then only one
machine will been tested and powered off, and the next machine will be started in the available stream. In
Full recoverability testing mode, after all machines are verified, machines from the application group will
be powered off or will be left running (if the Keep the application group running after the job completes
option has been enabled at the Application Group step of the wizard).

5. Select P rocess only randomly selected ... machines during each run check box and specify the maximum
number of machines you want to randomly test.

To exclude objects from the SureBackup job, perform the following steps:

1. Click E x clusions.

2. In the Ad d Objects window, select objects that you want to exclude.

You can select the Show full hierarchy check box to display the hierarchy of all hosts added to
Veeam Backup & Replication.

3. Click Ad d .

4. Click OK.

1901 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
To remove a backup or replication job from the list, select it and click Remove.

Linking Backup Job in Veeam Backup & Replication 12


To link a backup job to the SureBackup job:

1. Select the Link jobs check box.

2. Click Ad d .

3. In the Select Jobs window, select backup and replication jobs.

4. In the P rocess simultaneously up to … machines field, specify the maximum number of machines (from a
linked job) that can be started at the same time. For example, if you select to start three machines at the
same time, Veeam Backup & Replication will create three streams — one stream per every verified
machine. All three machines will be tested together. But if you select to start one machine, then only one
machine will been tested and powered off, and the next machine will be started in the available stream.
After all machines are verified, machines from the application group will be powered off or will be left
running (if the Keep the application group running after the job completes option has been enabled at the
Application Group step of the wizard).

1902 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To remove a backup or replication job from the list, select it and click Remove.

1903 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Recovery Verification Options and Tests
Specifying recovery verification options and tests is available only for SureBackup job working in Full
recoverability testing mode.

You must specify verification options for every machine from the jobs linked to the SureBackup job:

• Select a role that a machine performs

• Configure VM startup settings

• Select tests that must be performed for the VM

• Specify credentials for running the verification script

If all machines in the linked job perform the same role, you can specify startup options and test settings for the
whole job in bulk. If machines have different roles, you can granularly specify startup options and test settings
for each machine in the job.

• To specify startup options and select tests for the whole job, select the job in the list and click E d it on the
right.

• To specify startup options and select tests for every machine in the job separately, select the job in the list
and click Ad vanced on the right. Click Ad d and select the necessary machine in the Ad d Objects window.
Select the added machine in the list, click E d it and specify settings as described below.

IMP ORTANT

If you specify startup options and tests individually for a machine, Veeam Backup & Replication will apply
these options and tests only. Options and tests specified at the level of the SureBackup job will be ignored
for this machine.

Role Settings
On the Role tab, select the role that the machine performs. Veeam Backup & Replication offers the following
predefined roles for machines:

• DNS Server

• Domain Controller (Authoritative Restore). In the Authoritative Restore mode,


Veeam Backup & Replication starts a domain controller in the virtual lab and marks it as being
authoritative to its replication partners. When other domain controllers (replication partners) are started
in the virtual lab, they replicate data from the domain controller started in the Authoritative Restore
mode.

• Domain Controller (Non-Authoritative Restore). In the Non-Authoritative Restore mode,


Veeam Backup & Replication restores a domain controller in the virtual lab and marks it as being non-
authoritative to its replication partners. Non-authoritative domain controllers then replicate data from a
domain controller started in the Authoritative Restore mode.

• Global Catalog

• Mail Server

• SQL Server

• Veeam Backup for Microsoft 365 (machine on which Veeam Backup for Microsoft 365 is installed)

• Web Server

1904 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Machine roles are described in XML files stored in the %ProgramFiles%\Veeam\Backup and
Replication\Backup\SbRoles folder on the backup server. You can add your own roles. To do this, you need to
create a new XML file and specify role and test scripts settings in it. For more information, see Creating XML
files with Machine Roles Description.

After you select the necessary role, Veeam Backup & Replication will automatically configure startup options
and provide predefined test scripts applicable for the chosen role. You can use these settings or specify custom
ones on the Sta rtup Options and Test Scripts tabs.

To verify machines that perform roles other than those specified in the list, you will have to manually configure
startup options and specify test scripts to be run against these machines.

VM Startup Settings
To specify VM startup settings:

1. Click the Sta rtup Options tab.

2. In the Memory section, specify the amount of memory that you want to pre-allocate to the VM on the
system boot. The amount of pre-allocated memory is defined in percent. The percentage rate is calculated
based on the system memory level available for the production VM. For example, if 1024 MB of RAM is
allocated to the VM in the production and you specify 80% as a memory rate, 820 MB of RAM will be
allocated to the verified VM on startup.

Veeam Backup & Replication does not allow you to change VM CPU manually, it d oes this automatically. If
the VM has more CPU than the host can provide, Veeam Backup & Replication scales down the CPU of the
VM.

3. In the Sta rtup time section, specify the allowed boot time for the VM and timeout to initialize applications
on the VM.

Be careful when specifying the Ma x imum allowed boot time value. Typically, a VM started by a
SureBackup job requires more time to boot than a VM started in the production environment. If a VM is
not initialized within the specified interval of time, the recovery verification process fails with the timeout
error. If such error occurs, you need to increase the Ma x imum allowed boot time value and start the job
again.

4. In the Boot verification section, specify when the VM is considered to be successfully booted:

o VM heartbeat is present. If you select this option, Veeam Backup & Replication will perform a
heartbeat test for the verified VM.

1905 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o VM responds to ping on any network interface. If you select this option, Veeam Backup & Replication
will perform a ping test for the verified VM.

o Automatically disable Windows Firewall. If you select this option, Veeam Backup & Replication will
disable Windows Firewall for the the verified VM.

If you enable both options, Veeam Backup & Replication will require that both tests are completed
successfully: heartbeat test and ping test.

NOTE

Veeam Backup & Replication performs a heartbeat test for machines that have Hyper-V Integration
Services installed. If Hyper-V Integration Services are not installed, the machine will be started but tests
will not be performed.

Test Script Settings


When you select a machine role, Veeam Backup & Replication automatically assigns a predefined script that
must be run to verify applications inside the machine. If you want to verify a machine that has some other role
not listed in the Role tab, do the following:

1. Click the Test Scripts tab.

2. Click Ad d .

3. In the Test Scripts window, select Use the following test script.

4. In the Na me field, specify a name for the script.

5. In the P a th field, define a path to an executable script file that should be run to verify the machine. You
can do one of the following:

o If you have your own custom script, define a path to it in the P a th field.

o If you do not have a custom script, you can use Veeam’s standard utility,
Veeam.Backup.ConnectionTester.exe, that probes application communication ports. The utility
is located in the installation folder of Veeam Backup & Replication:
%ProgramFiles%\Veeam\Backup and
Replication\Backup\Veeam.Backup.ConnectionTester.exe. Specify this path in the P a th
field.

1906 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. In the Arg uments field, specify an IP address of the verified machine and the port that you want to probe
(if the selected test probes the port). You can use the %vm_ip% variable to define the machine IP address
or the %vm_fqdn% variable to define the machine FQDN.

For Microsoft SQL Server, you can also specify a path to the log file in the %log_path% argument. For
more information, see Backup Recovery Verification Tests.

7. Click OK to add the configured test.

To edit test settings, select the test in the list and click E d it. To delete a test, select it in the list and click
Remove.

IMP ORTANT

Do not pass sensitive information using script arguments in a user interface.

NOTE

If a VM performs several roles and runs a number of applications, you can verify their work by adding
several verification scripts. It is recommended that you specify the maximum startup timeout value and
allocate the greatest amount of memory for such VMs.

Credentials Settings
In the Credentials tab, specify credentials to authenticate in the machine where you need to run the script.

1. Click the Credentials tab.

1907 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
2. From the Credentials list, select credentials for the account under which you want to run the script.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add the credentials. For more information, see Managing Credentials.

1908 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Additional Job Settings
On the Settings step of the wizard, specify additional settings for the SureBackup job.

Specifying Additional Job Settings in


Veeam Backup & Replication 12.1
1. If you want Veeam Backup & Replication to scan VM data with antivirus software, select the Sca n backup
content with an antivirus software check box. For more information, see Secure Restore.

o If you want the antivirus software to continue scanning VM data after the first malware is found,
select the Continue scanning remaining files after the first occurrence check box. For information on
how to view results of the malware scan, see Viewing Recovery Verification Job Statistics.

o [For full recoverability testing mode] If you do not want to scan VMs from the application group,
select the Sk ip application group machines from malware scan check box. In this case, the antivirus
will only scan VMs from linked jobs.

Veeam Backup & Replication scans VM data with antivirus before running verification tests. Consid er that
the SureBackup job may take considerable time to complete if you are verifying backups of large sized
VMs.

2. If you want Veeam Backup & Replication to scan VM data with YARA rule, select the Sca n backup content
with the following YARA rule check box and select the YARA rule from the drop-down list. For YARA rules
to appear, they should be placed in the folder by the following path: %Program
Files%\Veeam\Backup and Replication\Backup\YaraRules. Veeam Backup & Replication
accepts only .yar and .yara extension.

1909 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. If you want to validate the backup file with a CRC check and make sure that the file is not corrupted, select
the P erform backup integrity check check box. If you selected Full recoverability testing mode at the
Na me step of the wizard, you can optionally exclude VMs being a part of the application group from this
test. To do this, select the Sk ip integrity check for application group machines' backup check box. For
more information, see Recovery Verification Tests.

NOTE

If you enable the Keep the application group running after the job completes option at the Ap p lication
Group step of the wizard, the Sk ip validation for application group VMs option will be automatically
enabled.

To configure notifications settings, click Configure and specify notification settings:

1. If you want to receive SNMP notifications, select the Send SNMP notifications for this job check box.

SNMP notifications will be sent only if you configure global SNMP settings in Veeam Backup & Replication
and on recipient’s computer. For more information, see Specifying SNMP Settings.

2. If you want to receive notifications by email, select the Send email notifications to the following recipients
check box. In the field below, specify recipient’s email address. You can enter several addresses separated
by a semicolon.

Email notifications will be sent only if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Specifying Email Notification Settings.

3. If you want to receive notifications only if the job finishes with specific states, select the required check
boxes. For example, Notify on warning and Notify on error. If you want to receive all notifications, select
all the check boxes.

1910 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup server.

Specifying Additional Job Settings in


Veeam Backup & Replication 12
1. If you want to validate the backup file with a CRC check and make sure that the file is not corrupted, select
the Va lidate entire virtual disk contents check box. You can optionally exclude VMs being a part of the
application group from this test. To do this, select the Sk ip validation for application group VMs check
box. For more information, see Recovery Verification Tests.

2. If you want Veeam Backup & Replication to scan VM data with antivirus software, select the Sca n the
selected restore p oint for malware check box. For more information, see Secure Restore.

o if you want the antivirus software to continue scanning VM data after the first malware is found,
select the Sca n the entire image check box. For information on how to view results of the malware
scan, see Viewing Recovery Verification Job Statistics.

1911 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
o If you do not want to scan VMs from the application group, select the Sk ip application group machines
from malware scan check box. In this case, the antivirus will only scan VMs from linked jobs.

Veeam Backup & Replication scans VM data with antivirus before running verification tests. Consider that
the SureBackup job may take considerable time to complete if you are verifying backups of large sized
VMs.

NOTE

If you enable the Keep the application group running after the job completes option at the Ap p lication
Group step of the wizard, the Sk ip validation for application group VMs option will be automatically
enabled.

To configure notifications settings, click Configure and specify notification settings:

1. If you want to receive SNMP notifications, select the Send SNMP notifications for this job check box.

SNMP notifications will be sent only if you configure global SNMP settings in Veeam Backup & Replication
and on recipient’s computer. For more information, see Specifying SNMP Settings.

2. If you want to receive notifications by email, select the Send email notifications to the following recipients
check box. In the field below, specify recipient’s email address. You can enter several addresses separated
by a semicolon.

Email notifications will be sent only if you configure global email notification settings in
Veeam Backup & Replication. For more information, see Specifying Email Notification Settings.

3. If you want to receive notifications only if the job finishes with specific states, select the required check
boxes. For example, Notify on warning and Notify on error. If you want to receive all notifications, select
all the check boxes.

1912 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. If you want to save this set of settings as the default one, click Sa ve as default. When you create a new
job, the saved settings will be offered as the default. This also applies to all users added to the backup
server.

1913 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Job Schedule
At the Schedule step of the wizard, select to manually run the SureBackup job or schedule the job at specific
time, for example, after the corresponding backup job completes. Keep in mind that SureBackup job will be
stopped during synthetic operations (synthetic full backup, backup files merge and transformation) against the
source backup chain, health check and replication session even if SureBackup job is scheduled to run.

1. To define a job schedule, select the Run the job automatically check box. If this check box is not selected,
you will have to manually start the job to perform recovery verification.

2. Choose the necessary schedule option for the job:

o Da ily at to start the job at specific time every day, on week days or on specific days.

o Monthly at to start the job once a month on the specified day.

NOTE

When you configure the job schedule, keep in mind possible date and time changes (for
example, related to daylight saving time transition).

o After this job to chain the job. Typically, a SureBackup job should run after the linked backup job
completes. In this case, the SureBackup job will verify the VM backup created by the corresponding
job.

To create a chain of jobs, you must define the time schedule for the first job in the chain. For the rest
of the jobs in the chain, at the Schedule step of the wizard, select the After this job option and choose
the preceding job from the list.

3. In some cases, the linked backup job may not complete until the SureBackup job starts. If
Veeam Backup & Replication finds out that the linked job is still running, the SureBackup job will fail to
start. To overcome this situation, select the If some linked backup jobs are still running, wait up to check
box and specify the necessary time period in the field on the right. If the linked job is still running,
Veeam Backup & Replication will wait for the defined period of time and check the linked job after this
period elapses.

o If the linked job is finished within the specified period, the SureBackup job will start.

o If the linked job is still running, the SureBackup job will not start.

1914 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Review Job Summary and Finish Working with Wizard
At the Summary step of the wizard, complete the procedure of SureBackup job configuration.

1. Review details of the SureBackup job.

2. If you want to start the job right after you finish working with the wizard, select the Run the job when I
click Finish check box.

3. Click Finish to save the SureBackup job settings and close the wizard.

Starting and Stopping SureBackup Job


You can instruct the SureBackup job to verify the latest restore point of a VM backup or select a specific restore
point to which the VM from the backup must be started.

To start a VM from the latest restore point:

1. Open the Home view.

2. In the inventory pane, click SureBackup under Job s.

3. In the working area, select the SureBackup job and click Sta rt on the ribbon. You can also right-click the
SureBackup job and select Sta rt. Veeam Backup & Replication will start, verify and perform necessary tests
for VMs from the latest restore point.

To start VMs from a specific point in time:

1. Open the Home view.

2. In the inventory pane, select SureBackup under Job s.

3. In the working area, select the SureBackup job and click Sta rt to on the ribbon. You can also right-click the
SureBackup job and select Sta rt to.

1915 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the Restore Point window, select an approximate date of the restore point creation.
Veeam Backup & Replication will pick the most recent restore point prior to this time and start, verify and
perform necessary tests for VMs from this restore point.

To stop a running SureBackup job session:

1. Open the Home view.

2. In the inventory pane, select SureBackup under Job s.

1916 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the SureBackup job and click Stop on the ribbon. You can also right-click the
SureBackup job and select Stop .

Viewing Recovery Verification Job Statistics


You can monitor how tests for verified VMs are performed while a recovery verification job is running.

To see the status of VM tests:

1. Open the Home view.

2. In the inventory pane, select SureBackup under Job s.

3. In the working area, right-click a recovery verification job and select Sta tistics. You can also double-click
the job in the list.

The job session window displays statistics for all VMs that are started during the SureBackup job: VMs from the
application group in the specified order and VMs from linked jobs. For your convenience, these VMs are marked
with different icons.

After the verified VM is powered on, its name is displayed as a hyperlink. You can click the link to open the VM
console to see what is happening inside the VM or perform manual testing.

If some VM fails to be verified automatically, you can start it manually when this VM is powered off. To start a
VM, right-click the VM in the list and select Sta rt. If the application group has already been powered off by that
time, it will be started again. After that, you can open the VM console and perform verification and testing
manually.

1917 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you enabled content analysis at the Settings step of the SureBackup job wizard, you can view the detailed
logging of the scan process. To view logs, click the Sca n Log button that will appear at the bottom of the job
session window after the scan is complete.

Creating SureBackup Session Reports


You can generate HTML reports with statistics on the SureBackup job. A report contains detailed data on job
sessions: job status, start and end time, details of the session performance, status of verified VMs and test
results. You can generate a report for the whole SureBackup job or a specific job session/sessions.

The SureBackup job report contains data on all sessions initiated for a specific job. To generate a SureBackup job
report:

1. Open the Home view.

2. In the inventory pane, select Job s .

3. In the working area, select the SureBackup job and click Rep ort on the ribbon. You can also right-click the
SureBackup job and select Rep ort.

The session report contains data on a single job session. To generate a session report:

1. Open the History view.

2. In the inventory pane, select Job s .

1918 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, select the session and click Rep ort on the ribbon. You can also right-click the session
and select Rep ort.

1919 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
XML Files with Machine Roles Description
Machine roles that you can assign to verified machines and machines from the application group are describ ed in
XML files. These XML files are stored in the %ProgramFiles%\Veeam\Backup and
Replication\Backup\SbRoles folder on the backup server.

To add a new role, you must create a new XML file and save it to the SbRoles subfolder on the backup server. Do
not save the XML file on the machine where the Veeam Backup & Replication console is installed — this will not
affect the list of roles in Veeam Backup & Replication.

XML files describing machine roles have the following structure:

<SbRoleOptions>
<Role>
<SbRole>
<Id>4CDC7CC4-A906-4de2-979B-E5F74C44832F</Id>
<Name>Web Server</Name>
</SbRole>
</Role>
<Options>
<SbVerificationOptions>
<ActualMemoryPercent>100</ActualMemoryPercent>
<MaxBootTimeoutSec>300</MaxBootTimeoutSec>
<AppInitDelaySec>120</AppInitDelaySec>
<TestScripts>
<TestScripts>
<TestScript>
<Name>Web Server</Name>
<Type>Predefined</Type>
<TestScriptFilePath>Veeam.Backup.ConnectionTester.exe</TestScriptFi
lePath>
<Arguments>%vm_ip% 80</Arguments>
</TestScript>
</TestScripts>
</TestScripts>
<HeartbeatEnabled>True</HeartbeatEnabled>
<DisableWinFirewall>True</DisableWinFirewall>
<PingEnabled>True</PingEnabled>
</SbVerificationOptions>
</Options>
</SbRoleOptions>

The XML file with the role description contains the following tags and parameters:

Ta g Required/ Description
Op tional

< Sb RoleOptions> Required Encapsulates the machine role file.

< Role> Required Parent tag for a role assigned to a machine. <SbRole>, <Id> and
<Name> are children of this tag.

< Sb Role> Required Encapsulates basic information for a machine role: ID and name.

1920 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ta g Required/ Description
Op tional

< Id> Required Unique identifier of a machine role.

< Na me> Required Name of a machine role. The machine role name is displayed in
the roles list on the Role tab.

< Op tions> Required Parent tag for startup and test script options to be used for the
defined role. <SbVerificationOptions>,
<ActualMemoryPercent>, <MaxBootTimeoutSec>,
<AppInitDelaySec>, <TestScripts>, <Name>, <Type>,
<TestScriptFilePath>, <Arguments>, <HeartbeatEnabled>,
<PingEnabled > are children of this tag.

< Sb VerificationOptions> Required Encapsulates options data for a machine role.

< ActualMemoryPercent> Optional Percent of the original memory level that must be pre-allocated
to a verified machine on the system boot.

< MaxBootTimeoutSec> Optional Maximum allowed time to boot a machine.

< Ap pInitDelaySec> Optional Duration of time for which Veeam Backup & Replication must
wait after the machine is successfully booted in the virtual lab.
After this time elapses, Veeam Backup & Replication will run
test scripts. Time is specified in seconds.

< TestScripts> Optional Encapsulates test script data for a machine role.

< Na me> Optional Name of a machine role. The machine role name is displayed on
the Test Scripts tab.

< Ty pe> Optional Type of the test script: Predefined or Custom.

< TestScriptFilePath> Optional Path to an executable file of the test script to be performed. The
path can be absolute or relative.

1921 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Ta g Required/ Description
Op tional

< Arguments> Optional Arguments to be passed to the script. You can use the following
variables:
• %vm_ip% — IP address of a verified machine.
or
%vm_fqdn% — a fully qualified domain name of a verified
machine.
• %log_path% — path to a log file to which verification
results are stored.

< HeartbeatEnabled> Required Must a heartbeat test be enabled for this machine role: True or
False.

< DisableWinFirewall> Required Must a firewall be disabled for this machine role: True or False.

< P ingEnabled> Required Must a ping test be enabled for this machine role: True or False.

1922 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Manual Recovery Verification
Beside automatic recovery verification, you can perform manual verification of machine backups. Manual
verification can be performed with all editions of Veeam Backup & Replication.

Boot Test
To perform a machine boot test, perform Instant Recovery for the verified machine. Power on the machine but
do not connect the machine to the production network to avoid conflicts with the original machine.

Application Test
To perform an application test:

1. Create an isolated network.

2. Perform Instant Recovery to restore the verified machine. At the Network step of the wizard, select to
connect the machine to the created isolated network.

The same procedure must be performed for all machines that run applications on which the verified machine is
dependent such as domain controller and DNS. All machines must be connected to the same isolated network
and started in the correct order: for example, DNS > domain controller > verified machine.

1923 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
On-Demand Sandbox
If you need to perform tests for production VMs, you can use an On-Demand Sandbox TM. The On-Demand
Sandbox is an isolated virtual environment where you can start one or more VMs from backups. You can use the
On-Demand Sandbox to perform the following tasks:

• Troubleshoot problems with VMs

• Test software patches and upgrades

• Install new software and so on

The On-Demand Sandbox uses a virtual lab — an isolated environment that is fully fenced off from the
production environment. To start a VM in the virtual lab, Veeam Backup & Replication uses Instant Recovery to
Microsoft Hyper-V. When you finish working with the On-Demand Sandbox, Veeam Backup & Replication
unpublishes the VM and powers off the virtual lab.

To create the On-Demand Sandbox, you must configure the following objects:

• Virtual lab in which VMs will be started. For more information, see Virtual Lab.

• Application group. The application group must include all VMs that you want to start in the On-Demand
Sandbox. This can be one VM or a group of VMs that work together. For more information, see Application
Group.

• SureBackup job. The virtual lab and application group must be linked to this job. For more information, see
SureBackup Job.

1924 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring On-Demand Sandbox
To configure the On-Demand Sandbox, perform the following steps:

1. Configure a virtual lab in which you plan to start VMs. For more information, see Creating Virtual Lab.

2. Configure an application group. The application group must contain all VMs that you plan to start in the
On-Demand Sandbox and all VMs on which these VMs are dependent. For more information, see Creating
Application Group.

3. Configure a SureBackup job:

a. Launch the New SureBackup Job wizard.

b. At the Virtual Lab step of the wizard, select the configured virtual lab.

c. At the Ap p lication Group step of the wizard, select the configured application group.

d. Select the Keep the application group running a fter the job completes check box.

e. Configure other job settings as required and save the job settings.

To start VMs in the On-Demand Sandbox, run the SureBackup job:

1. Open the Home view.

2. In the inventory pane, select SureBackup.

3. In the working area, right-click the configured SureBackup job and select Sta rt or Sta rt to.

1925 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication will start the virtual lab and power on VMs from the application group in the virtual
lab. You will be able to connect to VMs and perform tests for them.

1926 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Recovery
Veeam Backup & Replication offers the following types of recovery:

• VM recovery — to restore entire VMs to different data protection environments: to VMware vSphere,
Hyper-V, Amazon EC2 and so on.

• Disk recovery — to recover and export disks.

• Item recovery — to recover VM files, guest OS files and folders, and application items.

• Veeam Data Integration API — to get the backup content using the iSCSI or FUSE protocol and analyze
data stored in this backup.

• Secure restore — to scan data with antivirus software before restoring it to the production environment.

NOTE

Veeam Backup & Replication provides backward compatibility: backups created with previous product
versions can be restored with later product versions. However, backups created with later product versions
cannot be restored with previous product versions.

1927 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
VM Recovery
VM recovery includes the following methods:

• Instant Recovery to VMware vSphere — to instantly recover workloads (VMs, EC2 instances, physical
servers and so on) directly from compressed and deduplicated ba ckup files as VMware vSphere VMs. When
you perform Instant Recovery, Veeam Backup & Replication mounts recovered VM images to a host
directly from backups stored on backup repositories.

Instant Recovery helps improve recovery time objectives (RTO), minimize disruption and downtime of
production workloads. However, Instant Recovery provides for VMs “temporary spares” with limited I/O
performance. To provide the recovered VMs full I/O performance, you must finalize Instant Recovery —
migrate the recovered VMs to production environment. If you do not want to migrate the recovered VM,
you can stop publishing it. This removes the recovered VM.

Use Instant Recovery for tier 1 VMs with little tolerance for business interruption and downtime. Besides
disaster recovery matters, Instant Recovery can also be used for testing purposes.

• Instant Recovery to Microsoft Hyper-V — to instantly recover workloads directly from compressed and
deduplicated backup files as Microsoft Hyper-V VMs. In many respects, this method is similar to Instant
Recovery to VMware vSphere.

• Instant Recovery to Nutanix AHV — to instantly recover workloads directly from compressed and
deduplicated backup files as Nutanix AHV VMs. Note that to restore to Nutanix AHV, you must install
Nutanix AHV Plug-in on the backup server. For more information, see the Installation section in the Veeam
Backup for Nutanix AHV User Guide.

• Entire VM restore — to recover entire VMs. When you recover VMs, you extract VM images from backups
to the production storage. Entire VM restore takes more resources and time to complete than Instant
Recovery but recovers VMs with full I/O performance. You also do not need to perform additional steps to
finalize the recovery process.

Use entire VM restore for VMs that require full I/O performance as soon as they are recovered and that
tolerate some downtime.

• Staged restore — to run executable scripts for VMs before recovering them to the production
environment. Staged restore is a part of entire VM restore.

Use this option when you need to make sure that recovered VMs do not contain any personal or sensitive
data.

• Restore to Microsoft Azure — to restore workloads of different data protection environments as Microsoft
Azure VMs.

• Restore to Amazon EC2 — to restore workloads of different data protection environments as EC2
instances.

• Restore to Google Compute Engine (GCE) — to restore workloads of different data protection
environments as Google VM instances.

1928 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Instant Recovery to VMware vSphere
With Instant Recovery to VMware vSphere, you can immediately recover different workloads (VMs, EC2
instances, physical servers and so on) as VMware vSphere VMs. Instant Recovery to VMware vSphere can be
helpful, for example, if you want to migrate your infrastructure from one environment to another, or you want
to recover your infrastructure in a matter of minutes but with limited performance.

During recovery, Veeam Backup & Replication runs workloads directly from compressed and deduplicated
backup files. This helps improve recovery time objectives (RTO), minimize disruption and downtime of
production workloads. The workloads are recovered in a matter of minutes .

When you perform Instant Recovery, Veeam Backup & Replication mounts workload images to a host directly
from backups stored on backup repositories. This means that Veeam Backup & Replication creates fully
functioning “temporary spares” with limited I/O performance. To provide full I/O performance, you must
migrate these "temporary spares" to the production site. For more information, see Migration of Recovered VMs
to Production Site.

Besides disaster recovery matters, Instant Recovery can also be used for testing purposes. Instead of extracting
workload images to production storage to perform regular disaster recovery (DR) testing, you can run a
workload directly from a backup file, boot it and make sure the guest OS and applications are functioning
properly. For more information, see Finalizing Instant Recovery to VMware vSphere.

Instant Recovery supports bulk processing so you can immediately recover multiple workloads at once. If you
perform Instant Recovery for several workloads, Veeam Backup & Replication uses the resource scheduling
mechanism to allocate and use optimal resources required for Instant Recovery. For details, see Resource
Scheduling.

Supported Backup Types


You can recover workloads from the following types of backups:

• Backups of VMware vSphere virtual machines created by Veeam Backup & Replication
You can also recover VMware vSphere VM data directly from storage snapshots.

• Backups of VMware Cloud Director virtual machines created by Veeam Backup & Replication

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

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

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure

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

• Backups of RHV VMs created by Veeam Backup for RHV

How Instant Recovery Works


When Instant Recovery is performed, Veeam Backup & Replication uses the Veeam vPower technology to mount
a workload image to an ESXi host directly from a compressed and deduplicated backup file. Since there is no
need to extract the workload from the backup file and copy it to production storage, you can perform recovery
from any restore point in a matter of minutes.

1929 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The image of the workload remains in read-only state to avoid unexpected modifications. By default, all changes
to virtual disks that take place while a recovered VM is running are logged to auxiliary redo log files residing on
the NFS server (backup server or backup repository). These changes are discarded as soon as the recovered VM
is removed, or merged if you migrate the VM to the production site.

To improve I/O performance for a recovered VM, you can redirect VM changes to a spe cific datastore that is
closer to the host where the VM resides. In this case, Veeam Backup & Replication will trigger a snapshot and
will put it to the Veeam IR directory on the selected datastore, together with metadata files holding changes to
the VM image.

Migration of Recovered VMs to Production Site


To migrate the recovered VMs to the production storage, you can use one of the following relocation methods:

• Use Storage vMotion to quickly migrate the recovered VM to the production storage without any
downtime. In this case, original VM data will be pulled from the NFS datastore to the production storage
and consolidated with VM changes while the VM is still running. Storage vMotion, however, can only be
used if you select to keep VM changes on the NFS datastore without redirecting them. Note that to use
Storage vMotion, you need an appropriate VMware license.

• Use Quick Migration. In this case, Veeam Backup & Replication will perform a two-stage migration
procedure — instead of pulling data from the vPower NFS datastore, it will recover the VM from the
backup file on the production server, then move all changes and consolidate them with the VM data.

For more information on the relocation methods, see Quick Migration. For more information on how to launch
the migration for workloads recovered with Instant Recovery, see Finalizing Instant Recovery to
VMware vSphere.

Performing Instant Recovery to VMware vSphere


With Instant Recovery, you can recover different workloads from backups and register them as VMware vSphere
VMs. For the list of backups that you can use for recovery, see Supported Backup Types.

To perform Instant Recovery to VMware vSphere, use the Instant Recovery to VMware wizard.

NOTE

If you want to recover workloads as Hyper-V VMs, see Performing Instant Recovery to Hyper-V.

Before You Begin


Before you perform Instant Recovery, consider the following:

• Prerequisites for Instant Recovery from storage snapshots are listed in the Instant Recovery from Storage
Snapshots section in the Storage System Snapshot Integration Guide.

• You can recover a workload from a backup that has at least one successfully created restore point.

• If you recover a workload to the production network, make sure that the original workload is powered off.

• Restore of CSV (Cluster Shared Volumes) is not supported. Cluster disks used as CSV are automatically
excluded from restore.

• When you restore workloads other than VMware vSphere VMs, Veeam Backup & Replication assigns to the
restored VMs the highest VM hardware version supported by the ESXi host to which you restore the
workloads. For more information on ESXi hosts and compatible virtual machine hardware versions, see this
VMware KB article.

1930 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Consider the following for Linux workloads:

o We strongly recommend having dracut and mkinitrd installed on workloads that will be restored.
Otherwise, they may not boot after restore.

o Open the /etc/fstab/ file and check that all filesystems are mounted using UUID. If any filesystems
are mounted using block device name, the restored VM may not boot.

• If you want to scan recovered VM data for viruses, check the secure restore requirements and limitations.

• You must provide enough free disk space in vPower NFS datastore. The minimum amount of free space
must equal the RAM capacity of the recovered VM plus 200MB. For example, if the recovered VM has 32
GB of virtual RAM, 32.2 GB of free space is required.

By default, vPower NFS datastore is located in the IRCache folder on a volume with the maximum
amount of free space, for example, C:\ProgramData\Veeam\Backup\IRCache. The vPower NFS
datastore is not used when you select to redirect virtual disk updates to a VMware vSphere datastore
when configuring the job.

• [For Veeam Agents] Restore of 4K native drives is not supported. For more information on
VMware vSphere limitations, see this VMware KB article.

• [For Veeam Quick Migration with Smart Switch] In addition to the disk space mentioned above, you need
to provide more disk space in vPower NFS datastore. The minimum amount of free space must equal the
RAM capacity of the recovered VM.

• [For Nutanix AHV VMs] Instantly recoverd VM will have default virtual hardware settings: 2 CPU cores,
4GB RAM and one network adapter. If you want to change the default settings, turn off the VM and set
the required virtual resources. Note that you must not switch off the instant recovery session be fore
turning off the VM.

1931 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Instant Recovery Wizard
To launch the Instant Recovery to VMware wizard, do one of the following:

• On the Home tab, click Restore and select one of the following:

o VMwa re vSphere > Restore from backup > E ntire VM restore > Instant recovery > Instant recovery to
VMwa re vSphere — if you want to recover VMware vSphere VMs from a VM backup created by
Veeam Backup & Replication.

o VMwa re Cloud Director > Restore from backup > VM restore > E ntire VM restore > Instant recovery >
Instant recovery to VMware vSphere — if you want to recover VMware Cloud Director VMs from a VM
backup created by Veeam Backup & Replication.

o Microsoft Hyper-V > Restore from backup > E ntire VM restore > Instant recovery > Instant recovery to
VMwa re vSphere — if you want to recover Hyper-V VMs from a VM backup created by
Veeam Backup & Replication.

o Ag ent > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere — if you
want to recover physical machines from a backup created by Veeam Agent for Microsoft Windows or
Veeam Agent for Linux.

o AW S > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere — if you want
to recover EC2 instances from a backup created by Veeam Backup for AWS.

o Azure IaaS backup > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere
— if you want to recover Azure VMs from a backup created by Veeam Backup for Microsoft Azure.

o GCE backup > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere — if
you want to recover VM instances from a backup created by Veeam Backup for Google Cloud.

o Nuta nix backup > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere —
if you want to recover VMs from backups created by Veeam Backup for Nutanix AHV.

o RHV P roxy > E ntire machine restore > Instant recovery > Instant recovery to VMware vSphere — if you
want to recover VMs from backups created by Veeam Backup for RHV.

1932 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup, select workloads that you want to recover and click Instant Recovery > VMware vSphere on the
ribbon. Alternatively, you can right-click one of the selected workloads and select Instant recovery >
VMwa re vSphere.

1933 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workloads
At the Ma chines step of the wizard, select one or multiple workloads that you want to recover:

1. Click Ad d .

2. In the Ba ckup Browser window, do the following:

a. [For VMware vSphere VMs and VMware Cloud Director VMs] Select where to browse for VMs:

▪ From infrastructure — browse the environment and select VMs or VM containers (hosts, clusters,
folders, resource pools, VirtualApps, datastores or tags) to recover. If you select a VM container,
Veeam Backup & Replication will expand it to a plain VM list.

When you add a VM to the list, Veeam Backup & Replication displays information about the most
recent restore point in the Restore p oint column. If no restore point is available for the added
VM, Veeam Backup & Replication displays a warning next to this VM.

▪ From backup — browse existing backups and select virtual machines.

b. [For other workloads] In the list of backup jobs, expand a job and select workloads.

c. Click Ad d .

1934 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
By default, Veeam Backup & Replication uses the latest valid restore point to recover workloads. You can
recover a workload to an earlier state, if necessary:

1. In the Ma chines to restore list, select a workload.

2. Click P oint on the right.

3. In the Restore Points window, select a restore point from which you want to recover the workload.

1935 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Restore Mode
This step is available only if you recover VMware vSphere VMs or VMware Cloud Director VMs.

At the Restore Mode step of the wizard, specify a destination for VM recovery and whether you want to recover
VM tags:

1. Select a destination for recover:

o Restore to the original location — select this option if you want to recover VMs with their initial
settings and to their original location. If this option is selected, you will pass directly to the Reason
step of the wizard.

IMP ORTANT

If you recover a VM with the original settings, and the original VM still exists in the virtual
infrastructure, the original VM will be removed.

o Restore to a new location, or with different settings — select this option if you want to recover VMs to
a new location, or to any location but with different settings (such as VM location, network settings,
format of recovered virtual disks and so on). If this option is selected, the Instant Recovery to VMware
wizard will include additional steps for customizing VM settings.

2. If you want to recover tags that were assigned to the original VMs and assign them to the recovered VMs,
select the Restore VM tags check box. Veeam Backup & Replication will recover the VMs with original tags
if the following conditions are met:

a. You recover VMs to their original location.

b. The original VM tags are available on the source vCenter Server.

1936 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Destination for Restored VMs
Specify a destination where the recovered VMs will reside. The destination settings differ depending on the
number of workloads that you recover:

• Specifying Destination for One VM

• Specifying Destination for Multiple VMs

Specifying Destination for One VM

The Destination step of the wizard is available if you recover one workload and recover it to a new location or
with different settings.

At this step of the wizard, you configure destination settings such as the recovered VM name, target host, VM
folder and so on. For workloads other than VMware vSphere VMs and VMware Cloud Director VMs, you must
also configure a network mapping table. This table maps networks in the original site to networks in the target
site. When the job starts, Veeam Backup & Replication will check the network mapping table. Then
Veeam Backup & Replication will update VM configuration files to replace the original networks with the
specified networks in the target site. As a result, you will not have to re-configure network settings manually.

To specify the destination and network mapping settings for a recovered VM:

1. In the Restored VM name field, specify a name under which the workload will be recovered.

2. In the Host field, specify a host on which the VM will run.

3. In the VM folder field, specify a folder to which the recovered VM files will be placed.

4. In the Resource pool list, select a resource pool to which the VM will be placed.

5. [For workloads other than VMware vSphere VMs and VMware Cloud Director VMs] In the Networks
section, configure the network mapping table. To configure one row of the table, select a network in
the list and click Choose. The Select Network window displays all networks to which the target host
or cluster is connected. In the list of networks, select a network to which the recovered VM will be
connected instead of the original network.

1937 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Click the Ad vanced button and choose whether to preserve the BIOS UUID or generate a new BIOS
UUID. By default, the BIOS UUID is preserved.

We recommend that you select to generate a new BIOS UUID for the recovered VM to prevent
conflicts if the original workload still resides in the production environment. The BIOS UUID change
is not required if the original VM no longer exists, for example, it was deleted.

Specifying Destination for Multiple VMs

The following steps are available if you recover multiple workloads and recover the m to a new location or with
different settings.

If you recover multiple workloads, specify the following settings for the destination:

1. At the Host step of the wizard, select a target host.

2. At the Folder step of the wizard, specify VM settings.

3. [For workloads other than VMware vSphere VMs and VMware Cloud Director VMs] At the Network step of
the wizard, specify network settings.

Selecting Target Host


At the Host step of the wizard, specify a target host and resource pool for recovered VMs:

1. In the list, select the necessary VMs and click the Host button.

2. From the virtual environment, select a standalone or clustered host where the selected VMs will be
registered.

3. Select one or multiple VMs and click the P ool button.

1938 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the list, select a resource pool where the selected VMs will be stored.

Specifying VM Settings
For each recovered VM, you can change a VM name, BIOS UUID and folder where VM files must be stored. By
default, the BIOS UUID is preserved.

We recommend that you specify a new name and generate a new BIOS UUID to prevent conflicts if the original
workload still resides in the production environment. The name and BIOS UUID change is not required if the
original workload no longer exists, for example, it was permanently deleted.

To specify a folder:

1. In the VM settings list, select the necessary VM. If you want to specify a folder for multiple VMs,
select VMs that will be recovered to the same host.

2. Click the Folder button.

3. Select a folder where VM files must be stored.

To change a recovered VM name and BIOS UUID:

1. In the VM settings list, select one VM.

2. Click the Customize button.

3. In the VM Settings window, do the following:

a. In the Set name to field, specify a new VM name.

b. To add a prefix and suffix to the name specified in the Set name to field, select Ad d prefix and
Ad d suffix check boxes.

1939 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
c. In the BIOS UUID section, specify whether to preserve or generate a new BIOS UUID.

Specifying Network Settings


This step is available if you recover workloads other than VMware vSphere VMs and VMware Cloud Director
VMs.

At the Network step of the wizard, configure a network mapping table. This table maps networks in the original
site to networks in the target site (site where VMs will be recovered). When the job starts,
Veeam Backup & Replication will check the network mapping table. Then Veeam Backup & Replication will
update VM configuration files to replace the original networks with the specified networks in the target site. As
a result, you will not have to re-configure network settings manually.

To change networks to which the recovered VMs will be connected:

1. In the list, select one or multiple workloads and click the Network button.

If a workload is connected to multiple networks, you can select a network to map and click Network.

2. The Select Network window displays all networks to which the target host or cluster is connected. In
the list, select a network to which the recovered VM will be connected after recover.

1940 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
If you do not want to connect a recovered VM to any virtual network, select the original workload and click
Disconnected.

1941 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Destination for Virtual Disk Updates
This step is available if you recover workloads to a new location or with different settings.

At the Da tastore step of the wizard, you can select where to store redo logs when a VM is running from a
backup. Redo logs are auxiliary files used to keep changes that take place while the recovered VM runs.

By default, redo logs are stored on the vPower NFS server. You can store redo logs on any datastore in the
virtual environment if necessary. Redirecting redo logs improves recovery performance but makes Storage
vMotion not possible for ESXi 5.5. As soon as a recovery verification job completes, Veeam Backup & Replication
deletes redo logs.

To redirect redo logs:

1. Select the Red irect write cache check box.

2. Click Choose and select a datastore from the list.

IMP ORTANT

If the size of recovered VM disks is greater than 2 TB, you must not place redo logs on a VSAN data store.
Otherwise, Veeam Backup & Replication will fail to create a snapshot for the recovered VMs. For more
information, see VMware Docs.

1942 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Configure Helper Appliance
This step is available if you recover workloads with Linux OS, recover them to a new location or with different
settings, and VIX API is not available. However, this step is not available if you r ecover VMware vSphere VMs
from storage snapshots.

Veeam Backup & Replication recovers Linux machines to a standalone host using a helper appliance. The helper
appliance is an auxiliary Linux-based VM registered by Veeam Backup & Replication. The appliance is quite small
— around 150 MB. It requires the same amount of RAM as the VM being restored and takes around 10 seconds to
boot.

To configure the helper appliance:

1. [For multiple machines] In the Network list, expand a host and select one machine.

2. Click the Configure button.

3. In the Network Settings window, select a network for the helper appliance.

a. Click the Browse button near the P roduction network field.

b. In the Select Network window, Veeam Backup & Replication shows a list of networks to which the
target host is connected. In this list, select a network to which the helper appliance must be
connected.

Consider that the backup server and the mount server must have access to the helper appliance over
the network.

4. Specify IP addressing settings for the helper appliance and DNS server:

a. Click Configure.

b. Switch to the IP v4 or IP v6 tab depending on which addresses you want to configure. Note that you
can use IPv6 addresses only if IPv6 communication is enabled as described in section IPv6 Support.

c. Select the E na ble IPv4/IPv6 interface check box.

d. Configure IP settings for the helper appliance:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain an IP address automatically option selected.

▪ To manually assign a specific IP address to the helper appliance, click Use the following IP
a d dress and specify the IP address settings.

e. Configure IP settings for the DNS server:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain DNS server address automatically option selected.

▪ To manually assign a specific IP address to the DNS server, click Use the following DNS server
a d dress and specify preferred and alternate addresses.

1943 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
f. Click OK.

1944 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Secure Restore Settings
This step is available if you recover workloads with Microsoft Windows OS and recover them to a new location or
with different settings.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a s can
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o P roceed to recovery but d isable VM network adapters — if you want to restore VMs with disabled
network adapters (NICs).

o Ab ort VM recovery — if you want to cancel the restore session.

6. Select the Continue scanning all remaining files after the first occurrence (Scan the entire image – for
version 12 (build 12.0.0.1420)) check box if you want to continue scanning VM data after the first malware
is found. For information on how to view results of the malware scan, see Viewing Malware Scan Results.

1945 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for performing Instant Recovery. The information you provide
will be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1946 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Verify Instant Recovery Settings
At the Summary step of the wizard, specify additional settings for Instant Recovery:

1. If you recover production workloads that have failed and want to recover them with initial network
settings, select the Connect VMs to network check box.

If you recover workloads for testing disaster recovery while the original workloads are still running, leave
this check box unselected. Before you power on the recovered VMs, you must disconnect them from the
production network and connect to a non-production network to avoid conflicts.

2. To start the VMs right after recovery, select the P ower on target VMs after restoring check box. If you
recover the workloads to the production network, make sure that the original workloads are powered off.

3. Check settings that you have specified for Instant Recovery and click Finish.

4. Check that the publishing process has started and click Close.

What You Do Next


Finalizing Instant Recovery to VMware vSphere

Finalizing Instant Recovery to VMware vSphere


After the VMs have been successfully recovered, you must finalize the process. For this, test the rec overed VMs
and decide whether to migrate them to production environment or stop publishing.

• Testing recovered VMs

• Migrating recovered VMs

• Stop publishing recovered VMs

1947 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Testing Recovered VMs
To test the recovered VMs before you migrate them to production, you can launch VMware Remote Console
software from the Veeam Backup & Replication console.

IMP ORTANT

Before you launch VMware Remote Console, make sure that this software is installed on the machine
where the Veeam Backup & Replication console runs.

To open a VM console in Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

3. In the working area, right-click a VM and select Op en VM console.

Migrating Recovered VMs


If the VMs were recovered successfully, you can migrate them to the production environment.

To migrate a recovered VM to the production environment:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

3. In the working area, right-click a VM and select Mig rate to production. Veeam Backup & Replication will
launch the Quick Migration wizard. For more information on requirements and limitations for quick
migration, see Migrating VMs.

During migration, Veeam Backup & Replication will recover the VM from the backup file and additionally
move all changes that were made while the VM was running from the backup in the Instant Recovery
mode.

1948 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If you have launched Instant Recovery to a different location and you want to protect the recovered VM after
migration finishes, you need to add the recovered VM to a backup job manually. If you have launched Instant
Recovery to the original location, your actions depend on the method used for migration and whether the
Delete source VM files upon successful migration check box is enabled in the migration wizard. For more
information, see Finish Working with the Quick Migration Wizard.

Stop Publishing Recovered VMs


If your tests have failed, you can stop publishing the recovered VMs. This will remove the recovered VMs from
the host that you selected as the destination for recovery. Note that all changes made in the recovered VMs will
be lost.

IMP ORTANT

[For restore to original location] Both the recovered and original VMs are removed if you stop publishing
the recovered VM. This is because during restore to the original location, Veeam Backup & Replication
removes the original VM.

To stop publishing a recovered VM:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

1949 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click a VM and select Stop publishing.

Quick Migration
Quick Migration is a way to finalize Instant Recovery to VMware vSphere. Quick Migration allows you to migrate
recovered VMs between ESXi hosts and datastores. Veeam Backup & Replication supports migration of VMs in
any state with minimum disruption to business operations.

When you perform Quick Migration, Veeam Backup & Replication analyzes your virtual environment, its
configuration, the state of VMs and selects the most appropriate VM relocation method:

• vMotion a nd Storage vMotion


vMotion and Storage vMotion are native migration mechanisms of VMware vCenter.
Veeam Backup & Replication uses these methods whenever it is possible.

• Veeam Quick Migration

Veeam Quick Migration is the Veeam Backup & Replication proprietary technology.
Veeam Backup & Replication uses this method when VMware vCenter methods cannot be used. For
example, if your VMware vSphere license does not provide support for vMotion and Storage vMotion, or
you need to migrate VMs from one standalone ESXi host to another.

Veeam Quick Migration supports two modes of VM migration:

o Sma rtSwitch

With SmartSwitch, Veeam Backup & Replication suspends a VM, then moves the VM configuration file
and copies changes made to the VM disk after snapshot creation to the target host. After the
migration is completed, the VM is resumed on the target host.

o ColdMigration

With ColdMigration, Veeam Backup & Replication stops the VM, then copies changes made to the VM
disk after snapshot creation to the new host. After, the VM is started on the target host.

1950 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Quick Migration of VMs
Migration of a VM using the Veeam Quick Migration method includes the following steps:

1. Veeam Backup & Replication copies VM configuration file (.VMX) to the target host and registers the VM.

2. Veeam Backup & Replication triggers a VM snapshot creation and copies VM disk content to the new
destination.

3. Veeam Backup & Replication uses different modes when moving the VM between hosts with compatible
and non-compatible CPUs.

o If you move a VM between two hosts with compatible CPUs, Veeam Backup & Replication uses the
SmartSwitch mode.

o If you move a VM between two hosts with non-compatible CPUs or VM RAM is more than 8 GB,
Veeam Backup & Replication uses the ColdMigration mode.

Quick Migration Architecture


Quick Migration architecture in a VMware vSphere environment comprises the following components:

• Source host and target host with associated datastores

• One or two backup proxy servers

Similar to the backup architecture, Quick Migration uses two-service architecture: the source-side Veeam Data
Mover interacts with the source host, and the target-side Veeam Data Mover interacts with the target host. To
perform on-site migration, you can deploy one backup proxy for data processing and transfe r. This backup proxy
must have access to the source host and to the target host at the same time. In this scenario, the source -side
Veeam Data Mover and the target-side Veeam Data Mover are started on the same backup proxy.

The common requirement for off-site migration is that one Veeam Data Mover runs in the production site (closer
to the source host and datastore), and the other Veeam Data Mover runs in the remote target site (closer to the
target host and datastore). During backup, Veeam Data Movers ma intain a stable connection, which allows for
uninterrupted operation over WAN or slow links.

1951 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For off-site migration, you need to deploy at least one local backup proxy in each site: a source backup proxy in
the production site, and a target backup proxy in the remote target site.

Migrating VMs
Quick migration is not job-driven: it cannot be saved as a job or scheduled to run later.
Veeam Backup & Replication will start relocating VMs immediately after you finish working with the Quick
Mig ration wizard.

NOTE

Quick Migration is used only to finalize Instant Recovery to VMware vSphere.

Before you start quick migration, check prerequisites. Then use the Quick Migration wizard to migrate VMs.

Before You Begin


Before you perform quick migration, check the following prerequisites and limitations:

• Backup infrastructure components that will take part in quick migration must be added to the backup
infrastructure and properly configured. These include the source and target ESXi hosts.

• The target datastore must have enough free space to store disks of the VMs that you plan to migrate. To
receive alerts about low space on the target datastore, configure global notification settings. For more
information, see Specifying Other Notification Settings.

• If you want to use VMware vSphere vMotion to relocate VMs between hosts and VMware vSphere Storage
vMotion to relocate VM disks between datastores, make sure that you have a VMwa re vSphere license
covering these features.

• If you use tags to categorize virtual infrastructure objects, check limitations for VM tags. For more
information, see VM Tags.

Encryption
Veeam Backup & Replication does not keep encryption settings if a VM is migrated with VMware vMotion. After
the migration process is finished, you will need to enable encryption for the migrated VM manually.

1952 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Instant Recovery
When you restore a VM using Instant Recovery, Veeam Backup & Replication starts the VM directly from a
compressed and deduplicated backup file. To finalize recovery of a VM, you still need to move it to a new
location. Moving the VM with VMware Storage vMotion or hot replication may require a lot of time and
resources, or it may cause loss of valuable data.

Veeam Quick Migration was designed to complement Instant Recovery. Instead of pulling data from vPower NFS
datastore, Quick Migration registers the VM on the target host, restores the VM contents from the backup file
located in the backup repository and synchronizes the VM restored from backup with the running VM.

For more information, see Instant Recovery to VMware vSphere.

NOTE

Virtual appliance (HotAdd) transport mode cannot be used if the role of the backup proxy and mount
server or backup repository where the backup file is stored are assigned to the same VM.

1953 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Quick Migration Wizard

As Quick Migration is a way to finalize Instant Recovery to VMware vSphere, its launch is described in section
Finalizing Instant Recovery to VMware vSphere.

1954 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VMs to Relocate

At the Virtual Machines step of the wizard, select the VMs and VM containers that you want to relocate:

1. Click Ad d .

2. Use the toolbar at the top right corner of the window to switch between views: Hosts and Clusters, VMs
a nd Templates, Datastores and VMs and Tags. Depending on the view you select, some objects may not be
available. For example, if you select the VMs a nd Templates view, no resource pools, hosts or clusters will
be displayed in the tree.

3. Select the necessary object and click Ad d .

To quickly find the necessary object, you can use the search field at the bottom of the Ad d Objects window.

1. Click the button to the left of the search field and select the necessary type of object to search for:
Everything , Folder, Cluster, Host, Resource pool, VirtualApp or Virtual machine.

2. Enter the object name or a part of it in the search field.

3. Click the Sta rt search button on the right or press [Enter] on the keyboard.

1955 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify VM Destination

At the Destination step of the wizard, select the destination to which the selected VMs must be relocated:

1. Click Choose next to the Host or cluster field and select an ESXi host or cluster where the relocated VM
must be registered.

2. If all or majority of relocated VMs must belong to the same resource pool, click Choose next to the
Resource pool field and select the target resource pool.

If you want to place relocated VMs to different resource pools:

a. Click the P ick resource pool for selected VMs link.

b. In the Choose Resource P ool window, click Ad d VM on the right and select the VMs.

c. Select the added VM in the VM resource pool list and click Resource Pool at the bottom of the
window.

d. From the list of available resource pools, select the target resource pool.

3. If all or majority of relocated VMs must be placed to the same folder, click Choose and select the folder.

If you want to place relocated VMs to different folders:

a. Click the P ick VM folder for selected VMs link.

b. In the Choose Folder window, click Ad d VM on the right and select the VMs.

c. Select the added VM in the VM folder list and click VM Folder at the bottom of the window.

d. From the list of available folders, select the target folder.

The VM folder section is disabled if you selected a standalone ESXi host as a target for VM relocation.

4. If all or majority of relocated VMs must be stored on the same datastore, click Choose and select the
datastore. Veeam Backup & Replication displays only those datastores that are accessible by the selected
ESXi host. If you have chosen to relocate VMs to a cluster, Veeam Backup & Replication will display only
shared datastores.

IMP ORTANT

If you migrate VMs to the same datastore cluster that is used as the destination for redirecting
virtual disk updates (the Datastore step of the Instant Recovery to VMware wizard), you must enable
the Force Veeam transport usage check box at the Transfer step of the Quick Migration wizard.
Veeam Backup & Replication will use Veeam Quick Migration instead of Storage vMotion. This will
help to prevent data loss due to a bug in VMware Storage vMotion. If you do not enable the Force
Veeam transport usage check box, your relocated VM may be deleted.

If you want to place relocated VMs to different datastores:

a. Click the P ick datastore for selected virtual disks link.

b. In the Choose VM Files Location window, click Ad d VM on the right and select the VM that must be
placed on datastores.

c. Select the added VM in the Files location list and click Da tastore at the bottom of the window.

d. From the list of available datastores, select the target datastore.

You can also place the configuration file and individual disk files of a VM to different datastores:

a. Add a VM to the Files location list, expand the VM and select the required files.

1956 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
b. Click Da tastore at the bottom of the window and choose the destination for the files.

5. By default, Veeam Backup & Replication saves disks of relocated VMs in the thin format. If necessary, you
can change the disk format. For example, if the original VM uses thick disks, you can change the disk
format of the relocated VM to thin provisioned and save on disk space required to store VM data.

Disk format change is available only for VMs using virtual hardware version 7 or later.

To change VM disk format:

a. Click the P ick datastore for selected virtual disks link.

b. In the Choose VM Files Location window, click Ad d VM on the right and select the VM whose disk
format you want to change.

c. Select the added VM in the list and click Disk type at the bottom of the window.

d. In the Disk Type Settings section, choose the format that will be used to restore VM disk files: same as
the source disk, thin or thick.

1957 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Infrastructure Components for Data Transfer

At the Tra nsfer step of the wizard, assign infrastructure components to relocate the VMs:

1. In the Da ta transfer section, select backup proxies that must be used to transfer VM data from source to
target.

If you plan to migrate VMs within one site, the same backup proxy can act as the source backup proxy and
target backup proxy. For off-site migration, you must deploy at least one backup proxy in each site to
establish a stable connection across the sites for data transfer.

Click Choose next to the Source proxy and Target proxy fields to select backup proxies for migration. In
the Ba ckup P roxy window, you can choose automatic proxy selection or assign proxies explicitly.

o If you choose Automatic selection, Veeam Backup & Replication will detect backup proxies that have
access to the source datastore and will automatically assign optimal proxy resources for processing
VM data.

During migration, VMs are processed one by one. Before processing a new VM in the VM list,
Veeam Backup & Replication checks available backup proxies. If more than one backup proxy is
available, Veeam Backup & Replication analyzes transport modes that the backup proxies can use for
data retrieval and the current workload on the backup proxies to select the most appropriate resource
for VM processing.

o If you choose Use the selected backup proxy servers only, you can explicitly select backup proxies
that must be used to perform migration.

2. Select which migration mechanism to use: VMware vMotion or Veeam Quick Migration.
Veeam Backup & Replication can use VMware vMotion only if your VMware license covers this
functionality.

o If you want to use VMware vMotion to relocate the VMs, leave the Force Veeam transport usage
check box not selected. Veeam Backup & Replication will attempt to use the VMware vMotion
mechanism to migrate the selected VMs. If VMware vMotion cannot be used for some reason (for
example, if using it can cause data loss or if you do not have a VMware vSphere license for this
functionality), Veeam Backup & Replication will fail over to its native migration mechanism.

o If you do not want to use VMware vMotion, select the Force Veeam transport usage check box.
Veeam Backup & Replication will use its native migration mechanism.

IMP ORTANT

If you use a native Veeam mechanism to relocate a VM, Veeam Backup & Replication suspends the initial
VM on the source ESXi host (SmartSwitch) or powers off the initial VM (cold switch) for a short period of
time during quick migration. For more information, see Quick Migration.

1958 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1959 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Finish Working with Wizard

At the Rea dy step of the wizard, your actions differ depending on the method you have chosen to use for
migration.

If VMware vMotion is used for migration, review details and click Finish. In this case, all existing jobs to which
the source VM is added will switch to the VM on the target host (target VM). The backup chains will be
continued, thus, the next job sessions for the VM will be incremental.

If Veeam Quick Migration is used, you must also choose whether you want to delete files of the VM for which
the migration was launched after Veeam Backup & Replication receives a heartbeat signal from the VM on the
target host (target VM):

• If you want to delete the VM for which the migration was launched (source VM; for Instant Recovery, this
is the VM created during Instant Recovery but before finalization), leave the Delete source VM files upon
successful migration check box selected. All jobs to which the VM is added will switch to the target VM.
The backup chains will be continued, thus, the next job sessions for the VM will be incremental.

If the heartbeat signal is not received from the target VM, the source VM will not be deleted and the
target VM will not be added to any jobs. To protect the target VM, you must add it to a backup job
manually.

• If you want to leave the VM for which the migration was launched (source VM; for Instant Recovery, this is
the VM created during Instant Recovery but before finalization), clear the selection of the Delete source
VM files upon successful migration check box. In this case, the source VM will not be deleted. All jobs to
which the source VM is added will still process this VM and continue existing backup chains. To protect the
target VM, you must add it to a backup job manually.

During Veeam Quick Migration, Veeam Backup & Replication names the VMs according to the following
patterns:

• Source VM: source_vm_name at the start of migration; source_vm_name_migrated at the end of


migration.

• Ta rget VM: source_vm_name_GUID at the start of migration; source_vm_name at the end of migration.

NOTE

The Delete source VM files upon successful migration option applies if the following conditions are met:

• VMware vMotion is not used.


• VMs are powered on before migration.
• VMware Tools are installed on VMs.

1960 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
1961 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Instant Recovery to Microsoft Hyper-V
With Instant Recovery to Microsoft Hyper-V, you can immediately recover different workloads (VMs, EC2
instances, physical servers and so on) as Microsoft Hyper-V VMs. Instant Recovery to Microsoft Hyper-V can be
helpful, for example, if you want to migrate your infrastructure from one environment to another, or you want
to recover your infrastructure in a matter of minutes but with limited performance.

During recovery, Veeam Backup & Replication runs workloads directly from compressed and deduplicated
backup files. This helps improve recovery time objectives (RTO), minimize disruption and downtime of
production workloads. The workloads are recovered in a matter of minutes.

When you perform Instant Recovery, Veeam Backup & Replication creates dummy VMs and mounts to VMs
workload disks directly from backups stored on backup repositories. These dummy VMs have limited I/O
performance. To provide full I/O performance, you must migrate the VMs to the production site. For more
information, see Migration of Recovered VMs to Production Site.

Besides disaster recovery matters, Instant Recovery can also be used for testing purposes. Instead of extracting
workloads to production storage to perform regular disaster recovery (DR) testing, you can run a workload
directly from a backup file, boot it and make sure the guest OS and applications are functioning properly. For
more information, see Finalizing Instant Recovery to Microsoft Hyper-V.

Instant Recovery supports bulk processing so you can immediately recover multiple workloads at once. If you
perform Instant Recovery for several workloads, Veeam Backup & Replication uses the resource scheduling
mechanism to allocate and use optimal resources required for Instant Recovery. For details, see Resource
Scheduling.

Supported Backup Types


You can recover workloads from the following types of backups:

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

• Backups of VMware vSphere virtual machines created by Veeam Backup & Replication

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

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure

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

• Backups of RHV VMs created by Veeam Backup for RHV

How Instant Recovery Works


Instant Recovery is performed in the following way:

1. Veeam Backup & Replication reads the workload configuration from the backup file in the backup
repository and creates a dummy VM with empty disks on the target host. The created VM has the same
settings as the workload in the backup file. If you select to preallocate disk space for the recovered VMs,
Veeam Backup & Replication preallocates disk space at the beginning of the Instant Recovery process.

1962 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Veeam Backup & Replication initiates creation of a protective snapshot for the dummy VM and the VM is
started. If the Instant Recovery process fails for some reason, the protective snapshot guarantees that no
data is lost.

3. On the backup repository and on the target host, Veeam Backup & Replication starts a pair of Veeam Data
Movers that are used to mount the VM disks from the backup file to the dummy VM.

4. On the target host, Veeam Backup & Replication starts a proprietary Veeam driver. The driver redirects
requests to the file system of the recovered VM (for example, when a user accesses some application) and
reads necessary data from the backup file in the backup repository using the pair of Veeam Data Movers
that maintain the disk mount.

Migration of Recovered VMs to Production Site


When you begin the migration process, Veeam Backup & Replication starts one more pair of Veeam Data Movers
— one Veeam Data Mover on the backup repository and one on the target host. This pair of Veeam Data Movers
copies data of the recovered VM from the backup repository to the target host in the background, and populates
disks of the VM started on the target host.

The driver on the target host knows which data has already been recovered permanently and does not redirect
requests to such data, reading it directly from the disks of the recovered VM. Thus, performance of the instantly
recovered VM will increase as more of the data is copied. When the VM is recovered completely, all Veeam Data
Movers are stopped.

Performing Instant Recovery to Microsoft Hyper-V


With Instant Recovery, you can recover different workloads from backups and register them as Microsoft Hyper-
V VMs. For the list of backups that you can use for recovery, see Supported Backup Types.

To perform Instant Recovery, use the Instant Recovery wizard.

NOTE

If you want to recover workloads as VMware vSphere VMs, see Performing Instant Recovery to
VMware vSphere.

1963 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin
Before you perform Instant Recovery to Microsoft Hyper-V, consider the following:

• You must add the Hyper-V target host to which you want to recover machines to your backup
infrastructure.

• The following configuration is not supported:

o The storage I/O balancing is enabled on a Hyper-V host. Starting from Microsoft Windows Server
2012, I/O balancing is enabled by default.

o The backup repository role is assigned to a VM on this Hyper-V host. The backup from which you
recover is stored on this repository.

o You plan to recover a VM to this Hyper-V host or SureBackup is targeted to this host.

For information on how to recover with such configuration, see this Veeam KB article.

• Make sure that the Disable changed block tracking for this host option is not selected for a host to which
you plan to recover a workload. If this option is selected for the host, the driver required for work of
Instant Recovery will be disabled. For more information, see Configuring Connected Volumes.

• You can recover a workload from a backup that has at least one successfully created restore point.

• If you recover a workload to the production network, make sure that the original workload is powered off
to avoid conflicts.

• Consider the following for Linux workloads:

o We strongly recommend having dracut and mkinitrd installed on workloads that will be restored.
Otherwise, they may not boot after restore.

o Open the /etc/fstab/ file and check that all file systems are mounted using UUID. If any
filesystems are mounted using block device name, the restored VM may not boot.

• [If you recover Hyper-V VMs] The version of the target host on which a VM is recovered must be the same
or later than the version of the source host where the original VM was registered.

For example, you can restore a VM from the host that runs Microsoft Windows Server 2016 to the target
host that runs Microsoft Windows Server 2016 (including version 1809), Microsoft Windows Server 2019
or later.

The Hyper-V role must be enabled on both source and target hosts.

• If you want to scan recovered VM data for viruses, check the secure restore requirements and limitations.

• On non-Microsoft Windows SMB3 storage, for example, Tintri, Veeam Backup & Replication may display
the " Failed to disable integrity bit on disk N" warning during the restore process. You can ignore this
warning for non-Microsoft Windows SMB3 storage.

• The recovered VM will have the same MAC address as the original workload. Therefore, if you recover the
workload to the same Hyper-V host where the original workload is running, a MAC address conflict may
occur. To overcome this situation, power off the original workload before you start the recovery process.

• [For Nutanix AHV VMs] The recovered VM will not be connected to a network. You must connect to the
network manually.

• [For Nutanix AHV VMs, Amazon EC2 instances and Microsoft Azure virtual machines] Instantly recovered
VM will have default virtual hardware settings: 2 CPU cores, 4GB RAM and one network adapter. If you
want to change the default settings, turn off the VM and set the required virtual resources. Note that you
must not switch off the instant recovery session before turning off the VM.

1964 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Instant Recovery Wizard
To launch the Instant Recovery to Hyper-V wizard, do one of the following:

• On the Home tab, click Restore and select one of the following:

o Microsoft Hyper-V > Restore from backup > E ntire VM restore > Instant recovery > Instant Recovery
to Microsoft Hyper-V — if you want to recover Hyper-V VMs from a VM backup created by
Veeam Backup & Replication.

o VMwa re vSphere > Restore from backup > E ntire VM restore > Instant recovery to Microsoft Hyper-V
— if you want to recover VMware vSphere VMs from a VM backup created by
Veeam Backup & Replication.

o Ag ent > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V — if you
want to recover physical machines from a backup created by Veeam Agent for Microsoft Windows or
Veeam Agent for Linux.

o AW S E C2 backup > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V
— if you want to recover EC2 instances from a backup created by Veeam Backup for AWS.

o Azure IaaS > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V — if
you want to recover Azure VMs from a backup created by Veeam Backup for Microsoft Azure.

o GCE backup > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V — if
you want to recover VM instances from a backup created by Veeam Backup for Google Cloud.

o Nuta nix backup > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V —
if you want to recover VMs from backups created by Veeam Backup for Nutanix AHV.

o RHV P roxy > E ntire machine restore > Instant recovery > Instant recovery to Microsoft Hyper-V — if
you want to recover VMs from backups created by Veeam Backup for RHV.

1965 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup, select workloads that you want to recover and click Instant Recovery > Microsoft Hyper-V on the
ribbon. Alternatively, you can right-click one of the selected workloads and select Instant recovery >
Microsoft Hyper-V.

1966 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workloads
At the Ma chines step of the wizard, select workloads that you want to recover:

1. Click Ad d .

2. In the Ba ckup Browser window, do the following:

a. [For Hyper-V, VMware vSphere VMs and VMware Cloud Director VMs] You can browse for necessary
VMs using one of the following way:

▪ From infrastructure — use this option to browse the virtual environment and select VMs or VM
containers to recover. If you choose a VM container, Veeam Backup & Replication will expand it
to a plain VM list.

▪ From backup — browse existing backups and select VMs under backup jobs.

b. [For other workloads] In the list of backup jobs, expand a job and select workloads.

c. Click Ad d .

1967 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
By default, Veeam Backup & Replication uses the latest valid restore points to recover the workloads. You can
recover a workload to an earlier state, if necessary. If you have chosen to recover multiple workloads, you can
select a restore point for each workload in the list.

To select a restore point:

1. In the Ma chines to restore list, select a workload.

2. Click P oint on the right.

3. In the Restore Points window, select a restore point from which you want to recover the workload.

1968 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Recovery Mode
This step is available only if you recover Hyper-V VMs.

At the Recovery Mode step of the wizard, choose the necessary restore mode:

• Select Restore to the original location if you want to recover VMs with initial settings and to original
location. If this option is selected, you will pass directly to the Reason step of the wizard.

• Select Restore to a new location, or with different settings if you want to recover VMs to a different
location and with different settings (such as location, network settings and so on). If this option is
selected, the Instant Recovery to Hyper-V wizard will include additional steps for customizing VM
settings.

IMP ORTANT

If you recover a VM to the original location, consider the following:

• If the original VM still exists in the virtual infrastructure, the VM and its disks will be removed. Make
sure that other VMs in the virtual environment do not use these disks.
• The VM settings contain the ID of the VM group to which the machine belongs. To recover the VM to
the original VM group, you must not delete the original VM group or change the hierarchy of its
parent VM groups.

1969 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Target Host
This step is available if you recover workloads to a new location or with different settings.

At the Host step of the wizard, specify a target Hyper-V host or a Hyper-V cluster where you want to locate the
recovered VMs:

1. In the VM location list, select the necessary VMs and click Host.

2. In the Select Server window, select a standalone host or cluster where the selected VM will be registered.

3. If you have selected a Hyper-V cluster, you can specify the cluster resource settings. Click Resource and
select one of the following options in the Cluster Resource Settings window:

o Reg ister VM as a cluster resource — if you want to assign a cluster role to the recovered VM.

o Do not register VM as a cluster resource — if you do not want to assign a cluster role to the recovered
VM.

IMP ORTANT

You cannot recover workloads to a Microsoft Hyper-V 2008 R2 Cluster due to Microsoft limitations. You
can recover workloads to Microsoft Hyper-V 2012 Failover Cluster or Microsoft Hyper-V 2012 R2 Failover
Cluster.

If you need to recover a workload to a Microsoft Hyper-V 2008 R2 Cluster, you can use the following
workaround:

1. Recover the workload to any node of the cluster.


2. Configure the recovered VM as highly available. For more information, see Microsoft Docs.

1970 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Target Datastore
This step is available if you recover workloads to a new location or with different settings.

At the Da tastore step of the wizard, specify a path to the folder where VM configuration files and disks will be
stored:

1. In the Files location list, select the workloads that will be recovered to the same host and click P a th.
Alternatively, you can expand a workload in the list and select individual files. Use this method if you want
to place configuration and disk files to different locations.

2. In the Select Folder window, do one of the following:

o Select an existing folder where VM files will be stored.

o Create a new folder by clicking New Folder at the bottom of the window.

o Type a path to an SMB3 shared folder in the search field at the bottom of the Select Folder window.
The path must be specified in the UNC format, for example: \\172.16.11.38\Share01.

IMP ORTANT

The host or cluster on which you register VMs must have access to the specified SMB3 shared
folder. If you are using SCVMM 2012 or later, the server hosting the Microsoft SMB3 shared
folder must be registered in SCVMM as a storage device. For more information, see Microsoft
Docs.

3. Check that the Allocate required disk space before migration check box is selected if you want to
preallocate disk space required for the recovered VM. Otherwise, clear the check box.

1971 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Network Mapping
This step is available if you recover workloads to a new location or with different settings.

At the Network step of the wizard, configure a network mapping table. This table maps networks in the original
site to networks in the target site (site where VMs will be recovered). When the job star ts,
Veeam Backup & Replication will check the network mapping table. Then Veeam Backup & Replication will
update VM configuration files to replace the original networks with the specified networks in the target site. As
a result, you will not have to re-configure network settings manually.

To specify network mapping settings:

1. In the Network connections list, select the necessary workloads and click Network.

If a workload is connected to multiple networks, expand the workload, select a network to map and click
Network.

2. In the Select Network window, select a network to which the selected workload must be connected after
recovery.

If you do not want to connect the recovered VM to any virtual network, select the original workload in the list
and click Disconnect.

1972 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Change VM Name and UUID
This step is available if you recover workloads to a new location or with different settings.

At the Na me step of the wizard, specify names under which VMs will be recovered and select whether you want
to preserve VM UUIDs or change them. By default, Veeam Backup & Replication preserves the original names
and UUIDs.

NOTE

We recommend that you specify a new name and generate a new UUID for a VM to prevent conflicts if the
original workload still resides in the production environment. The name and UUID change is not required if
the original workload no longer exists, for example, it was permanently deleted.

Changing Names
To change a VM name:

1. In the Virtual machines list, select the necessary workloads and click Na me.

2. In the Cha nge Name section, enter a new name explicitly or specify a change name rule by adding a pre fix
or suffix to the original workload name.

Alternatively, you can change a VM name directly in the Virtual machines list. To do this, click the New Name
field and enter the name to be assigned to the recovered VM.

Changing UUIDs
To change VM identification settings:

1. Select the necessary workloads in the list and click Sy stem UUID.

1973 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the BIOS UUID Settings window, select to generate a new UUID.

1974 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Configure Helper Appliance
This step is available if you recover workloads with Linux OS and recover them to a new location or with
different settings.

Veeam Backup & Replication recovers Linux machines using a helper appliance. The helper appliance is an
auxiliary Linux-based VM registered by Veeam Backup & Replication. The appliance is quite small — around 100
MB. It requires 1024 MB RAM and takes around 10 seconds to boot.

At the Help er Appliance step of the wizard, configure the helper appliance network settings:

1. [For multiple machines] In the Network list, expand a host and select one machine for which you want to
configure the helper appliance.

2. Click the Configure button.

3. In the Network Settings window, select a network for the helper appliance.

a. Click the Browse button to the right of the P roduction network field.

b. In the Select Network window, Veeam Backup & Replication shows a list of networks to which the
target host is connected. In this list, select a network to which the helper appliance must be
connected. Click OK.
Consider that the backup server and the mount server must have access to the helper appliance over
the network.

c. In the VLAN ID field, specify an ID of a VLAN where the helper appliance will reside.

The 0 value means that the VLAN is not set.

4. Specify IP addressing settings for the helper appliance and DNS ser ver:

a. Click Configure.

b. Switch to the IP v4 or IP v6 tab depending on which addresses you want to configure. Note that you
can use IPv6 addresses only if IPv6 communication is enabled as described in section IPv6 Support.

c. Select the E na ble IPv4/IPv6 interface check box.

d. Configure IP settings for the helper appliance:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain an IP address automatically option selected.

▪ To manually assign a specific IP address to the helper appliance, click Use the following IP
a d dress and specify the IP address settings.

e. Configure IP settings for the DNS server:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain DNS server address automatically option selected.

▪ To manually assign a specific IP address to the DNS server, click Use the following DNS server
a d dress and specify preferred and alternate addresses.

1975 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
f. Click OK.

1976 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Specify Secure Restore Settings
This step is available if you recover workloads with Microsoft Windows OS and recover them to a new location or
with different settings.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o P roceed with recovery but disable network adapters — if you want to restore the VM with disabled
network adapters (NICs).

o Ab ort VM recovery — if you want to cancel the restore session.

6. Select the Sca n the entire image check box if you want to continue the VM data scan after the first
malware is found. For information on how to view results of the malware scan, see Viewing Malware Scan
Results.

1977 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for performing Instant Recovery of the workloads. The
information you provide will be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

1978 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Verify Instant VM Recovery Settings
At the Summary step of the wizard, check settings of Instant Recovery and click Finish. If you want to start the
recovered VMs on the target host, select the P ower on target VM after restoring check box.

What You Do Next


Finalizing Instant Recovery to Microsoft Hyper-V

Finalizing Instant Recovery to Microsoft Hyper-V


After the VMs have been successfully recovered, you must finalize the process. For this, test the recovered VMs
and decide whether to migrate them to production environment or stop publishing.

Testing Recovered VMs


To test the recovered VMs before you migrate them to production, you can launch VM consoles from
Veeam Backup & Replication or open the consoles in the Hyper-V client.

To launch a VM console from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

1979 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click a VM and select Op en VM console.

If the test fails, you can stop publishing the recovered VMs. For details, see Stop Publishing Recovered VMs.

Migrating Recovered VMs


When Veeam Backup & Replication migrates VMs, it transfers VM disks data to the production storage that you
have selected as a destination for the recovered VMs.

NOTE

[If you recover Hyper-V VMs] After the migration is finished, and if the selected destination differs from
the original location, the original VMs still exist. If you do not need them, you must manually remove them
in the Hyper-V client.

To migrate a recovered VM to production:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

1980 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click a VM and select Mig rate to production.

Stop Publishing Recovered VMs


If you have ensured that the VM is working and you do not need it anymore, or your tests have failed, you can
stop publishing the recovered VMs. This will remove the recovered VMs from the storage that you selected as
the destination for recovery. Note that all changes made in the recovered VMs will be lost.

IMP ORTANT

[For Hyper-V VM restore to original location] Both the recovered and original VMs are removed if you stop
publishing the recovered VM. This is because during restore to the original location,
Veeam Backup & Replication removes the original VM.

To remove a recovered VM:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

1981 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the working area, right-click a VM and select Stop publishing.

1982 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Instant Recovery to Nutanix AHV
With Instant Recovery to Nutanix AHV, you can immediately recover different workloads as Nutanix AHV VMs.
You can use Instant Recovery to Nutanix AHV to migrate the entire infrastructure or individual VMs to a Nutanix
AHV cluster.

IMP ORTANT

To restore to Nutanix AHV, you must install Nutanix AHV Plug-in on the backup server. To learn more, see
the Installation section in the Veeam Backup for Nutanix AHV User Guide.

The procedure of restore to Nutanix AHV practically does not differ from the procedure described in the
Performing Instant Recovery of Workloads to Nutanix AHV section in the Veeam Backup for Nutanix AHV User
Guide.

1983 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Entire VM Restore
With Veeam Backup & Replication, you can restore an entire VM from a backup file to the latest state or to a
previous point in time if the original VM fails.

Entire VM restore requires that VM image is fully extracted to the production storage.
Veeam Backup & Replication copies the VM data from the backup repository to the selected storage, registers
the VM on the chosen Hyper-V host and, if necessary, powers it on.

A VM can be restored to its original location or to a new location. When you restore a VM to its original location,
Veeam Backup & Replication powers off the original VM and deletes it before the restore. This type of restore
ensures the quickest recovery and minimizes the number of mistakes which can be potentially caused by
changes in VM settings.

When you restore a VM to a new location, you can specify new VM settings such as the new VM name, the host
and volume where the VM will reside and network properties. Veeam Backup & Replication will change the VM
configuration file and store the VM data to the location of your choice.

NOTE

If a VM has several VM disks, Veeam Backup & Replication restores VM disks in parallel.

Quick Rollback
When you restore a full VM to the original location, you can instruct Veeam Backup & Replication to perform
quick rollback — incremental data restore. Instead of restoring an entire VM from a backup file,
Veeam Backup & Replication will recover only those data blocks that are necessary to revert the VM to an earlier
point in time. Quick rollback significantly reduces the recovery time and has little impact on the production
environment.

For quick rollback, Veeam Backup & Replication uses the changed block tracking technology.
Veeam Backup & Replication gets information about the current VM state and compares it with the CBT
information in the backup file. This way, Veeam Backup & Replication detects what data blocks must be
transported back to the production volume to rebuild the VM to the necessary point in time.

It is recommended that you use quick rollback if you restore a VM after a problem that has occurred at the level
of the VM guest OS — for example, there has been an application error or a user has accidentally deleted a file
on the VM guest OS. Do not use quick rollback if the problem has occurred at the VM hardware level, storage
level or due to a power loss.

Requirements for Quick Rollback


To perform quick rollback, make sure that the following requirements are met:

• VM must be restored to its original location.

• The backup file from which you plan to restore a VM must be created with the Use changed block tracking
d a ta option enabled.

1984 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Limitations for Quick Rollback
Quick rollback has the following limitations:

• [For Microsoft Hyper-V 2016 and later] You cannot run two restore sessions with quick rollback
subsequently. After you restore a VM with quick rollback, the CBT on the original VM is reset. You must
run at least one incremental backup job session to be able to perform quick rollback again.

• Quick rollback is not supported if the original VM is replicated using Hyper -V native replication
mechanisms.

• Use quick rollback and VM guest OS file exclusion wisely. If you exclude specific files and folders from the
VM guest OS during backup and use quick rollback to restore the VM or VM disk from such backup,
Veeam Backup & Replication will restore only the content of the backup file. The excluded data will not be
restored. For example, if you exclude C:\Folder from the backup, data in this folder will not be backed up
and will not be available in the resulting backup file. After some time, data in C:\Folder may change but
the folder will still not be backed up (since the job excludes this folder). For this reason, when you
perform quick rollback, Veeam Backup & Replication will restore all data that have changed except the
excluded C:\Folder.

Restoring Entire VMs


To restore an entire VM, use the Full VM Restore wizard.

Before You Begin


Before you restore a VM from a backup, consider the following:

• You can restore a VM from a backup that has at least one successfully created restore point.

• If you back up a VM with vRDM disks, Veeam Backup & Replication converts the disks into VMDK files.
Thus, when you restore a VM with a vRDM disk, Veeam Backup & Replication restores this disk as a VMDK
file. If you want to preserve the vRDM format for restored disks, use Quick Rollback. For more
information, see Quick Rollback.

• Check requirements and limitations in the VMs section in Platform Support.

• If you restore a VM to its original location and the original VM is still running, Veeam Backup & Replication
powers off the original VM and deletes it before the restore.

• If you want to scan VM data for viruses, check the secure restore requirements and limitations.

• If you want to run an executable script for a VM, check the staged restore requirements and limitations.

• On non-Microsoft Windows SMB3 storage, for example, Tintri, Veeam Backup & Replication may display
the " Failed to disable integrity bit on disk N " warning during VM restore. You can ignore this warning for
non-Microsoft Windows SMB3 storage.

• The restored VM will have the same MAC address as the original VM. Therefore, if you restore the VM to
the same Hyper-V host where the original VM is running, a MAC address conflict may occur. To overcome
this situation, power off the original VM before you start the restore process.

• The version of the target host on which the VM is restored must be the same or later than the version of
the source host where the original VM was registered.

For example, you can restore a VM from the host that runs Microsoft Windows Server 2016 to the target
host that runs Microsoft Windows Server 2016 (including version 1809), Microsoft Windows Server 2019
or later.

1985 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
The Hyper-V role must be enabled on both source and target hosts.

1986 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Full VM Restore Wizard
To launch the Full VM Restore wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from backup > E ntire VM restore > E ntire
VM restore.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup and select the machine that you want to restore and click E ntire VM on the ribbon. Alternatively,
right-click the machine that you want to restore and select Restore entire VM.

• Double-click the VBK or VBM file (for example, in Microsoft Windows Explorer). In the displayed window,
select the VM and click Restore > E ntire VM.

You can use this option if you perform restore on the backup server. You cannot use this option if you
perform restore remotely over the Veeam Backup & Replication console.

1987 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VMs
At the Virtual Machines step of the wizard, select one or several VMs that you want to restore.

To select VMs:

1. Click Ad d VM.

2. Select where to browse for VMs:

o From infrastructure — browse the virtual environment and select VMs or VM containers (Hyper-V
hosts, clusters, SCVMM, SCVMM tags, SCVMM host groups, VM groups, or volumes) to restore. If you
choose a VM container, Veeam Backup & Replication will expand it to a plain VM list.

o From backup — browse existing backups and select VMs under backup jobs.

1988 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
By default, Veeam Backup & Replication uses the latest valid restore point. However, you can restore the VM to
an earlier state. If you have chosen to restore several VMs, you can select the necessary restore point for every
VM in the list.

To select a restore point for a VM:

1. In the Virtual machines to restore list, select a VM.

2. Click P oint on the right.

3. In the Restore Points window, select a restore point from which you want to restore the VM.

1989 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Restore Mode
At the Restore Mode step of the wizard, choose the necessary restore mode:

1. Choose a restore mode:

o Select Restore to original location if you want to restore VMs with their initial settings and to their
original location. If this option is selected, you will immediately pass to the Reason step of the wizard.

During restore to the original location, Veeam Backup & Replication deletes the original VMs and
restores VMs with the original identifiers. This means that after the restore finishes, you do not need
to update jobs which process the original VMs.

o Select Restore to a new location, or with different settings if you want to restore VMs to a different
location or with different settings (such as VM location, network settings and so on). If this option is
selected, the Full VM Restore wizard will include additional steps for customizing VMs settings.

If you restore VMs to the same host and select to preserve VM UUIDs, you do not need to update
existing jobs which process the original/recovered VMs, the jobs will still be working. If you configure
restore in another way and want to process the restored VMs, you must edit existing jobs or create
new jobs to process the recovered VMs.

o Select Sta ged restore if you want to run an executable script for VMs before recovering them to the
production environment. If this option is selected, the Full VM Restore wizard will include an
additional step for customizing staged restore settings.

If you restore VMs to the same host and select to preserve VM UUIDs, you do not need to update
existing jobs which process the original/recovered VMs, the jobs will still be working. If you configure
restore in another way and want to process the restored VMs, you must edit existing jobs or create
new jobs to process the recovered VMs.

IMP ORTANT

If you recover a machine to the original location, consider that the VM settings contain the ID of the
VM group to which the machine belongs. To restore the machine to the original VM group, you must
not delete the original VM group or change the hierarchy of its parent VM groups.

2. [For VM restore to the original location] Select the Quick rollback check box if you want to perform
incremental restore for the VM. Veeam Backup & Replication will use CBT to get data blocks that are
necessary to revert the VM to an earlier point in time, and will restore only these data blocks from the
backup. Quick restore significantly reduces the restore time and has little impact on the production
environment.

It is recommended that you enable this option if you restore a VM after a problem that occurred at the
level of the VM guest OS: for example, there has been an application error or a user has accidentally
deleted a file on the VM guest OS. Do not enable this option if the problem has occurred at the VM
hardware level, storage level or due to a power loss.

1990 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For more information on quick rollback, its requirements and limitations, see Quick Rollback.

1991 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Target Host
The Host step of the wizard is available if you have chosen to change the location and settings for the restored
VM.

To specify a target host:

1. Select the necessary VMs in the VM location list and click Host.

2. Choose a standalone or clustered host where the selected VMs must be registered.

If you choose to register the restored VM on a host being a part of a Hyper -V failover cluster, you can specify
additional failover settings.

1. Select a VM in the list and click Resource.

2. Select the Reg ister VM as a cluster resource option if the restored VM must be configured as a cluster
resource. In this case, if the target host is brought offline or fails for any reason, the VM will fail over to
another node in the cluster.

1992 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Target Datastore
The Da tastore step of the wizard is available if you have chosen to change the location and settings for
recovered VMs.

At the Da tastore step of the wizard, specify a path to the folder where VM configuration files and disks will be
stored:

1. Select the necessary workloads in the Files location list and click P a th. Alternatively, you can expand a
workload in the list and select individual files. Use this method if you want to place configuration and disk
files to different locations.

2. In the Select Folder window, do one of the following:

o Select an existing folder where VM files will be stored.

o Create a new folder by clicking New Folder at the bottom of the window.

o Type a path to an SMB3 shared folder in the search field at the bottom of the Select Folder window.
The path must be specified in the UNC format, for example: \\172.16.11.38\Share01.

IMP ORTANT

The host or cluster on which you register VMs must have access to the specified SMB3 shared
folder. If you are using SCVMM 2012 or later, the server hosting the Microsoft SMB3 shared
folder must be registered in SCVMM as a storage device. For more information, see Microsoft
Docs.

1993 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Network Mapping
The Network step of the wizard is available if you have chosen to change the location and settings for recovered
VMs.

If you plan to restore a VM to a new location, for example, another site with a different set of networks, you can
map source site networks to target site networks. Veeam Backup & Replication will use the network mapping
table to update configuration files of VMs on the fly, during the restore process.

To change networks to which restored VMs will be connected:

1. Select a VM in the list and click Network. To apply changes in bulk, select several VMs in the list and click
Network.

If a VM is connected to multiple networks, expand the VM, select the network to map and click Network.

2. The Select Network section displays all networks to which the target host or cluster is connected. From
the list of available networks, choose a network to which the selected VM must have access upon restore.

If you do not want to connect the restored VM to any virtual network, select the VM in the list and click
Disconnected.

1994 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Change VM Name and UUID
The Na me step of the wizard is available if you have chosen to change the location and settings for recovered
VMs.

At the Na me step of the wizard, specify names under which VMs will be recovered and select whether you want
to preserve VM UUIDs or change them. By default, Veeam Backup & Replication preserves the original names
and UUIDs.

NOTE

We recommend that you specify a new name and generate a new UUID for a VM to prevent conflicts if the
original workload still resides in the production environment. The name and UUID change is not required if
the original workload no longer exists, for example, it was permanently deleted.

Changing Names
To change a VM name:

1. In the Virtual machines list, select the necessary VMs and click Na me.

2. In the Cha nge Name section, enter a new name explicitly or specify a change name rule by adding a prefix
or suffix to the original workload name.

Alternatively, you can change a VM name directly in the Virtual machines list. To do this, click the New Name
field and enter the name to be assigned to the recovered VM.

Changing UUIDs
To change VM identification settings:

1. Select the necessary VMs in the list and click VM UUID.

1995 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the BIOS UUID Settings window, select to generate a new UUID.

1996 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Secure Restore Settings
This step is available if you restore Microsoft Windows VMs.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o P roceed with recovery but disable network adapters. Select this action if you want to restore the
machine with disabled network adapters (NICs).

o Ab ort VM recovery. Select this action if you want to cancel the restore session.

6. Select the Continue scanning all remaining files after the first occurrence (Scan the entire image – for
version 12 (build 12.0.0.1420)) check box if you want to continue machine scan after the first malware is
found. For information on how to view results of the malware scan, see Viewing Malware Scan Results.

1997 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Specify Staged Restore Settings
The Staged Restore step of the wizard is available if you have chosen the Staged restore option at the Restore
Mode step of the wizard.

Staged restore to run an executable script for VMs before restoring them to the production environment. For
more information, see Staged Restore.

To specify staged restore settings:

1. From the Virtual lab list, select a virtual lab that will be used to start VMs. The list contains all virtual labs
that are created or connected to the backup server.

2. From the Ap p lication group list, select an application group if script execution requires other VMs to be
powered on. In the virtual lab during staged restore, Veeam Backup & Replication will start VMs from the
selected application group in the required order. The Ap p lication group list contains all application groups
that are created on the backup server. For more information, see Application Group.

3. On the right of the Script field, click Browse to choose the script from a local folder on the backup server.

4. From the Credentials list, select credentials for the account that has administrator privileges on VMs for
which you want to run the script. If you have not set up credentials beforehand, click the Ma nage accounts
link or click Ad d on the right of the Credentials field to add the credentials. For more information, see
Managing Credentials.

VM Startup Settings
If you want to start VMs after recovery, perform the following steps:

1. Click Ad vanced.

1998 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. In the Memory section, specify the amount of memory that you want to pre-allocate to a VM when it
starts. The amount of pre-allocated memory is defined in percent. The percentage rate is calculated based
on the system memory level available for the production VM. For example, if 4096 MB of RAM is
allocated to the VM in the production environment and you specify 50% as a memory rate, 2048 MB of
RAM will be allocated to the VM on startup.

3. In the Sta rtup time section, specify the allowed boot time for the VM and timeout to initialize applications
on the VM.

Be careful when specifying the Ma x imum allowed boot time value. Typically, a VM started in a virtual lab
requires more time to boot than a VM started in the production environment. If an application fails to be
initialized within the specified interval of time, the recovery process fails with the timeout error. If such
error occurs, you need to increase the Ma ximum allowed boot time value and perform VM restore again.

1999 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 11. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for restoring the selected VMs. The information you provide
will be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2000 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 12. Verify Restore Settings
At the Summary step of the wizard, check restore settings and click Finish. If you want to start the recovered
VMs on the target host, select the P ower on VM after restoring check box.

2001 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Staged Restore
Staged restore allows you to run an executable script for VMs before recovering them to the production
environment. Staged restore is a part of the entire VM restore operations. To perform staged restore, you must
select the Sta ged Restore mode in the Full VM Restore wizard and specify staged restore settings.

Staged restore can help you ensure that recovered VMs do not contain any personal or sensitive data. For
example, you can instruct Veeam Backup & Replication to run a Windows PowerShell script that removes Active
Directory users:

$UserName = "John.Smith"
$ADUser = Get-ADUser -Filter 'Name -like $UserName'
if (!$ADUser)
{
[Environment]::Exit(1)
}
Remove-ADUser -Identity $UserName -Confirm:$false

NOTE

The staged restore functionality is included in the Veeam Universal License. When using a legacy socket -
based license, Enterprise or higher edition is required.

Requirements and Limitations for Staged Restore


Before you perform staged restore, check the following prerequisites:

• You must have a preconfigured virtual lab in your backup infrastructure. For more information, see Virtual
Lab.

• Scripts that you plan to run must reside in a local folder on a backup server.

• If you plan to perform staged restore for several VMs within one restore session, make sure these VMs run
OS of the same type: either Microsoft Windows or Linux. In the current version of
Veeam Backup & Replication, you cannot specify credentials and scripts for each VM individually.

How Staged Restore Works


For staged restore, Veeam Backup & Replication uses a preconfigured virtual lab, an executable script located on
the backup server, and credentials to connect to VMs and run the script. Veeam Backup & Replication performs
staged restore in the following way:

1. In the virtual lab, Veeam Backup & Replication starts VMs directly from compressed and deduplicated
backup files that reside in the backup repository. To achieve this, Veeam Backup & Replication uses Instant
Recovery to Microsoft Hyper-V.

If you use an application group to run a script, Veeam Backup & Replication first starts VMs from the
application group in the required order.

2. Veeam Backup & Replication copies the script from the backup server to VMs that you plan to restore.

To connect to VMs, Veeam Backup & Replication uses credentials specified in staged restore settings.

2002 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Veeam Backup & Replication runs the copied script on every VM.

To run the script, Veeam Backup & Replication uses the same technology as for pre-freeze and post-thaw
scripts. For more information, see Pre-Freeze and Post-Thaw Scripts.

4. Veeam Backup & Replication writes all VM changes that take place during script execution to the
differencing disk (AVHD/AVHDX file).

Veeam Backup & Replication stores differencing disks on the Hyper-V host where the virtual lab is created.

5. After the script execution is complete, Veeam Backup & Replication makes a safe shutdown of VMs in the
virtual lab.

6. Veeam Backup & Replication restores VMs in a changed state to the production environment.

2003 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore to Microsoft Azure
Veeam Backup & Replication allows you to restore different workloads (VMs, Google VM instances, physical
servers and so on) from backups to Microsoft Azure.

You can use Veeam Backup & Replication to complete the following tasks:

• Restore workloads from Veeam backups to Microsoft Azure.

• Migrate workloads from the on-premises infrastructure to the cloud.

• Create a test environment in the cloud for troubleshooting, testing patches and updates and so on.

Supported Backup Types


You can restore workloads from the following types of backups:

• Backups of Microsoft Windows and Linux VMs created by Veeam Backup & Replication.

• Backups of Microsoft Windows machines created by Veeam Agent for Microsoft Windows. Backups must
be created at the entire machine level or volume level.

• Backups of Linux machines created by Veeam Agent for Linux. Backups must be created at the entire
machine level or volume level.

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure.

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

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

• Backups of RHV VMs created by Veeam Backup for RHV.

You can restore a workload to the latest restore point or any previous restore point in the backup chain.

Veeam Backup & Replication employs the Microsoft Azure Resource Manager deployment model.
Veeam Backup & Replication supports batch restore — you can launch the restore process for several VMs at a
time.

IMP ORTANT

The Classic deployment model is deprecated. Thus, you cannot add Classic Azure accounts. You can restore
VMs in the Classic model only if you have added the Classic Azure account before upgrading to
Veeam Backup & Replication 9.5 Update 4.

2004 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Generation 2 VM Support
By default, Veeam Backup & Replication restores workloads as Generation 1 VMs. Veeam Backup & Replication
also offers experimental support for Generation 2 VMs within restore to Microsoft Azure feature.

Generation 2 VMs are virtual machines with advanced functionality. For more information about Generation 2
VMs, see Microsoft Docs. For more information about Microsoft Azure support for Generation 2 VMs, see
Microsoft Docs.

To learn how to enable Generation 2 VM support, see this Veeam KB article. To learn Generation 2 VM support
limitations, see Limitations for Restore to Microsoft Azure.

Limitations for Restore to Microsoft Azure


When planning to restore workloads to Microsoft Azure, consider the following general limitations:

• Veeam Backup & Replication supports restore to Microsoft Azure for the following workloads:

o Microsoft Windows workloads that run Windows Server 2008/Windows Vista and later.

o Linux workloads (see the Supported Distributions & Versions section in Microsoft Docs).

IMP ORTANT

We strongly recommend having dracut and mkinitrd installed on Linux machines that will be
restored to Azure. Otherwise, they may not boot after restore.

• If you use a cloud-init-based Linux distribution, we recommend that you use SSH keys on these
distributions. If you use a password, it is blocked after restore for security reasons. To reset the password
on the restored VM, you need to use the VMAccess extension. For more information, see Microsoft Docs.

• When you select a storage account whose resources you want to use to store disks of the restored
workload, consider the following:

o Storage accounts with the zone-redundant storage (ZRS), geo-zone-redundant storage (GZRS) and
geo-redundant storage (GRS) replication options are not supported. However, read -access geo-
redundant storage (RA-GRS) option is supported. For details on replication options, see Microsoft
Docs.

o If you plan to use a premium storage account and want to store unmanaged disks there, the restore
speed for such disks will be limited to 30 MB/s (approximately).

• When you select a geographic region to which you want to restore workloads, consider that some regions
are access restricted to support specific customer scenarios. For example, VMs cannot be created ther e. To
be able to perform different actions in those regions, create a support request in the Azure portal.

For the full list of access-restricted regions, see Microsoft Docs. The regions are marked with an asterisk *.

• [Azure VMs] Microsoft has strict rules for naming Azure resources. For naming rules that your VM names
must correspond to, see Microsoft Docs: the Resource name rules and Resolve errors for reserved resource
names articles.

• [Azure VMs] Veeam Backup & Replication does not support restore of Azure Ultra Disks.

2005 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• [Azure VMs] Consider the following limitations for disk sizes:

o [Unmanaged VM disks] Veeam Backup & Replication supports restoring of disks equal to or less than
4093 GB. This is due to the following reasons: VM disks can increase in size up to 2 GB because of
conversion during the restore process; Azure supports disk up to 4095 GB. For more information on
all disk sizes that Azure supports, see Microsoft Docs.

o [Managed VM disks] Veeam Backup & Replication supports restoring disks equal or less than 4093 GB
for OS disks and equal to or less than 32765 GB for other disks. During the restore process, VM disks
can increase in size up to 2 GB because of conversion. For more information on all managed disk sizes
that Azure supports, see Microsoft Docs. For more information on OS disk size that Azure supports,
see Microsoft Docs. Note that supported disk sizes for Azure and Veeam Backup & Replication differ.

IMP ORTANT

The price of a restored VM disk can become higher because of the increase in disk size during the
restore process. For more information on pricing, see Managed Disks pricing and Unmanaged Disk
and Page Blob pricing.

• [Azure Stack VMs] Veeam Backup & Replication supports restoring of managed and unmanaged disks
equal to or less than 1021 GB. This is due to the following reasons: VM disks can increase in size up to 2 GB
because of conversion during the restore process; Azure Stack supports disk up to 1023 GB. For more
information on all disk sizes that Azure supports, see Microsoft Docs.

You can change the maximum supported size for unmanaged VM disks with a registry value. For more
information, contact Veeam Customer Support.

IMP ORTANT

The price of a restored VM disk can become higher because of the increase in disk size during the
restore process. For more information on pricing, see Azure Stack Hub Pricing.

• If the system disk of an initial workload uses the GPT partitioning scheme, the number of partitions on the
disk cannot exceed 4. During restore such disk will be converted to a disk with the MBR partitioning
scheme.

• Veeam Backup & Replication does not support restoring of disks whose logical sector size is 4096 bytes.
Contents of such disks will be unreadable in Microsoft Azure.

• The restore to Microsoft Azure functionality does not support the Azure Hybrid Use Benefit program.

• [For restore from backups created by Veeam Agent for Microsoft Windows] Workloads from a backup that
contains a failover cluster are restored as separate VMs, not as a cluster. Shared cluster disks of these VMs
are restored as regular disks.

Requirements and Limitations for Generation 2 VM Support


Before enabling Generation 2 VM support, consider the following requirements and limitations:

• When you select VM sizes at the Specify VM Size step of the Restore to Azure wizard, make sure that the
selected size is compatible with Generation 2 VMs.

• Generation 2 VMs support only managed disks. Thus, you will need to select the managed storage type
from the Storage type list at the Specify VM Size step of the Restore to Azure wizard.

• Make sure that OSes of backed-up workloads that you plan to restore have UEFI boot. Otherwise, the
restored VMs may be unbootable.

2006 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
How Restore to Microsoft Azure Works
The restore process differs for Microsoft Windows and Linux workloads.

NOTE

Consider the following:

• If you added the Veeam Backup for Microsoft Azure appliance to the Veeam Backup & Replication
infrastructure and you plan to restore Microsoft Azure VMs from restore points that were created
using the appliance, the restore works as described in the Performing VM Restore section in Veeam
Backup for Microsoft Azure User Guide.
• [If you restore from backups created by products other than Veeam Backup for Microsoft Azure] By
default, during restore, Veeam Backup & Replication creates Generation 1 VMs. Such VMs support
only Basic Input/Output System (BIOS) firmware interface. If you restore workloads with Unified
Extensible Firmware Interface (UEFI), Veeam Backup & Replication converts UEFI into the BIOS
firmware interface.
For information on Generation 2 VM support, see Generation 2 VM Support.

Restore of Microsoft Windows Workloads


To restore a Microsoft Windows workload, Veeam Backup & Replication performs the following steps:

1. If you use an Azure restore proxy appliance (former Azure proxy) for restore, Veeam Backup & Replication
powers on the Azure restore proxy appliance. For more information about the Azure restore proxy
appliance, see Managing Azure Restore Proxy Appliances.

2. Veeam Backup & Replication converts disks of a backed-up workload to the VHD format and uploads
converted disks to Blob storage in Microsoft Azure.

3. Veeam Backup & Replication mounts uploaded disks to the backup server.

4. Veeam Backup & Replication enables storage controller drivers needed to boot the VM in Microsoft Azure.

5. Veeam Backup & Replication enables remote desktop connections on the restored VM.

6. Veeam Backup & Replication configures Windows Firewall rules to allow incoming remote desktop
connections.

7. Veeam Backup & Replication prepares Microsoft Azure agent installation on the restored VM. Installation
will start after the VM will be powered on.

8. Veeam Backup & Replication unmounts the uploaded disks from the backup server.

9. If you use an Azure restore proxy appliance for restore, Veeam Backup & Replication powers off the Azure
restore proxy appliance after a timeout.

2007 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
10. Veeam Backup & Replication registers a Microsoft Azure VM with the prepared workloa d disks. After the
registration process is complete, the Microsoft Azure VM is powered on immediately. Then the Microsoft
Azure agent is installed on the VM.

Restore of Linux Workloads


For restore of Linux workloads, Veeam Backup & Replication uses a helper appliance. The helper appliance is a
Linux-based VM in Microsoft Azure registered by Veeam Backup & Replication. During the restore process,
Veeam Backup & Replication mounts disks of a backed-up workload to the helper appliance to prepare disks for
restore. For more information, see Managing Helper Appliances.

To restore a Linux workload, Veeam Backup & Replication performs the following steps:

1. If you use an Azure restore proxy appliance (former Azure proxy) for restore, Veeam Backup & Replication
powers on the Azure restore proxy appliance. For more information about the Azure restore proxy
appliance, see Managing Azure Restore Proxy Appliances.

2. Veeam Backup & Replication converts disks of a backed-up workload to the VHD format and uploads
converted disks to Blob storage in Microsoft Azure.

3. Veeam Backup & Replication mounts uploaded disks to the helper appliance that resides in the location to
which you restore the Linux workload.

4. Veeam Backup & Replication starts the helper appliance with mounted disks.

5. Veeam Backup & Replication makes configuration changes needed for the VM to boot in Microsoft Azure.

6. Veeam Backup & Replication unmounts prepared disks from the helper appliance and powers off the
helper appliance.

7. If you use an Azure restore proxy appliance for restore, Veeam Backup & Replication powers off the Azure
restore proxy appliance after a timeout.

2008 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
8. Veeam Backup & Replication registers a Microsoft Azure VM with the prepared workload disks. After the
registration process is complete, the VM is powered on immediately.

Configuring Components and Accounts for Restore


Before you restore workloads, you must first add an account to be used for restore and then configure the
required components:

1. Add a restore account:

o Add a Microsoft Azure Compute account if you want to restore workloads to Microsoft Azure.

o Add a Microsoft Azure Stack Hub Compute account if you want to restore workloads to Azure Stack
Hub.

These accounts must have specific built-in Azure roles (the roles are listed in the sections about adding
the accounts). If you do not want to use built-in roles, you can create a custom role with granular
permissions. For more information, see Creating Custom Role for Azure Account.

2. [For restore of Linux workloads] Configure helper appliances in Microsoft Azure.

NOTE

[If you have not changed default credentials for helper appliance] Before you configure the helper
appliances, we recommend you to change the default credentials used during the helper appliance
deployment. For more information on how to do this, see Changing Credentials for Helper
Appliances.

3. [For restore process speed-up] Configure an Azure restore proxy appliance.

NOTE

If you added the Veeam Backup for Microsoft Azure appliance to the Veeam Backup & Replication
infrastructure and you plan to restore VMs from restore points that were created using the appliance, you
do not need to configure the helper appliance and Azure restore proxy appliance (former Azure proxy).
Also, restore to Microsoft Azure works as described in the Performing VM Restore section in Veeam Backup
for Microsoft Azure User Guide.

2009 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Creating Custom Role for Azure and Azure Stack Hub Accounts
Granular permissions differ depending on whether you create an Azure Stack Hub account, or Azure Compute
account using a new Microsoft Entra ID (formerly Azure Active Directory) application, or Azure Compute account
using an existing Microsoft Entra ID application.

NOTE

This section describes permissions required for Veeam Backup & Replication to perform tasks. If you need
to perform other tasks, for example create virtual networks, add the required permissions for those tasks
manually.

Instead of granular permissions, you can use built-in roles. For more information, see Permissions.

Permissions for Azure Compute Account (Existing Application)


If you plan to add an Azure Compute account using an existing Microsoft Entra ID (formerly Azure Active
Directory) application (select the Use the existing account option at the Access Type step of the wizard), and
you do not want to use built-in Azure roles, you can create a custom role with granular permissions:

1. In the Azure Portal, go to subscription properties and open Access control (IAM).

2. Create a custom role from a JSON file as described in Microsoft Docs. Use the following JSON. In the
a ssignableScopes field, specify your subscription ID.

JSON — P ermissions for Existing Application

2010 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
{
"properties": {
"roleName": "
Veeam Restore Operat
or",
"description"
: "Permissions neede
d for an application
for an Azure Compute
Account",
"assignableSc
opes": [
"/subscri
ptions/your_subscrip
tion_ID_here"
],
"permissions"
: [
{
"acti
ons": [
"
Microsoft.Storage/st
orageAccounts/listke
ys/action",
"
Microsoft.Storage/st
orageAccounts/read",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/delet
e",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/read"
,
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/write
",
"
Microsoft.Network/lo
cations/checkDnsName
Availability/read",
"
Microsoft.Network/vi
rtualNetworks/read",
"
Microsoft.Network/vi
rtualNetworks/subnet
s/join/action",
"
Microsoft.Network/pu
blicIPAddresses/read
",
"
Microsoft.Network/pu

2011 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
blicIPAddresses/writ
e",
"
Microsoft.Network/pu
blicIPAddresses/dele
te",
"
Microsoft.Network/pu
blicIPAddresses/join
/action",
"
Microsoft.Network/ne
tworkInterfaces/read
",
"
Microsoft.Network/ne
tworkInterfaces/writ
e",
"
Microsoft.Network/ne
tworkInterfaces/dele
te",
"
Microsoft.Network/ne
tworkInterfaces/join
/action",
"
Microsoft.Network/ne
tworkSecurityGroups/
read",
"
Microsoft.Network/ne
tworkSecurityGroups/
write",
"
Microsoft.Network/ne
tworkSecurityGroups/
delete",
"
Microsoft.Network/ne
tworkSecurityGroups/
join/action",
"
Microsoft.Compute/lo
cations/vmSizes/read
",
"
Microsoft.Compute/lo
cations/usages/read"
,
"
Microsoft.Compute/vi
rtualMachines/read",
"
Microsoft.Compute/vi
rtualMachines/write"
,
"
Microsoft.Compute/vi

2012 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
rtualMachines/delete
",
"
Microsoft.Compute/vi
rtualMachines/start/
action",
"
Microsoft.Compute/vi
rtualMachines/deallo
cate/action",
"
Microsoft.Compute/vi
rtualMachines/instan
ceView/read",
"
Microsoft.Compute/vi
rtualMachines/extens
ions/read",
"
Microsoft.Compute/vi
rtualMachines/extens
ions/write",
"
Microsoft.Compute/vi
rtualMachines/conver
tToManagedDisks/acti
on",
"
Microsoft.Compute/di
sks/read",
"
Microsoft.Compute/di
sks/write",
"
Microsoft.Compute/di
sks/beginGetAccess/a
ction",
"
Microsoft.Compute/di
sks/delete",
"
Microsoft.Compute/di
sks/endGetAccess/act
ion",
"
Microsoft.Resources/
checkResourceName/ac
tion",
"
Microsoft.Resources/
subscriptions/resour
ceGroups/read",
"
Microsoft.Resources/
subscriptions/resour
ceGroups/write",
"
Microsoft.Resources/
subscriptions/locati
ons/read",

2013 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
"
Microsoft.Marketplac
e/offerTypes/publish
ers/offers/plans/agr
eements/read",
"
Microsoft.Marketplac
e/offerTypes/publish
ers/offers/plans/agr
eements/write"
],
"notA
ctions": [],
"data
Actions": [
"
Microsoft.KeyVault/v
aults/keys/encrypt/a
ction",
"
Microsoft.KeyVault/v
aults/keys/decrypt/a
ction",
"
Microsoft.KeyVault/v
aults/keys/read",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/messa
ges/delete",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/messa
ges/read",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/messa
ges/write",
"
Microsoft.Storage/st
orageAccounts/queueS
ervices/queues/messa
ges/process/action"
],
"notD
ataActions": []
}
]
}
}

3. Assign the created role to the required Microsoft Entra ID application. For details, see the Manage access
to Azure resources using RBAC and the Azure portal section in the RBAC for Azure resources
documentation.

4. At the Account Type step of the Microsoft Azure Compute Account wizard, select Use existing account.

2014 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
5. At the Subscription step of the wizard, specify the Azure Microsoft Entra ID application with the assigned
role.

Permissions for Azure Compute Account (New Application)


If you plan to add an Azure Compute account using a new Microsoft Entra ID (formerly Azure Active Directory)
application (select the Create a new a ccount option at the Subscription step of the wizard), and you do not want
to use built-in Azure roles, you can create a custom role with granular permissions:

1. In the Azure Portal, go to subscription properties and open Access control (IAM).

2. Create a custom role from a JSON file as described in Microsoft Docs. Use the following JSON. In the
a ssignableScopes field, specify your subscription ID.

JSON — P ermissions for New Application

2015 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
{
"properties": {
"roleName": "
Veeam Register Azure
Compute Account usin
g new Microsoft Entr
a ID application",
"description"
: "Permissions neede
d for a user to add
an Azure Compute Acc
ount based on new Mi
crosoft Entra ID app
lication",
"assignableSc
opes": [
"/subscri
ptions/00000000-0000
-0000-0000-000000000
000"
],
"permissions"
: [
{
"acti
ons": [
"
Microsoft.Authorizat
ion/roleDefinitions/
read",
"
Microsoft.Authorizat
ion/roleAssignments/
read",
"
Microsoft.Authorizat
ion/roleAssignments/
write"
],
"notA
ctions": [],
"data
Actions": [],
"notD
ataActions": []
}
]
}
}

3. Assign the created role to the required Microsoft Entra ID user. For details, see the Manage access to
Azure resources using RBAC and the Azure portal section in the RBAC for Azure resources documentation.

4. At the Account Type step of the Microsoft Azure Compute Account wizard, select Create a new account.

5. At the Sub scription step, configure the account as described in section Creating New Microsoft Entra ID
Application. On the Microsoft Azure device authentication page, specify an Microsoft Entra ID user
account with the assigned role.

2016 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The described permissions are required for assigning a role on the subscription level for the registered
application. Also, privileges to register applications are required. For more information, see Permissions.

Permissions for Azure Stack Hub Compute Account (Existing


Application)
If you plan to add an Azure Stack Hub account using an existing Microsoft Entra ID application (select the Use
the existing account option at the Subscription step of the wizard), and you do not want to use built-in Azure
roles, you can create a custom role with granular permissions:

1. In the Azure Stack Hub management portal, go to subscription properties and open Access control (IAM).

2. Create a custom role from a JSON file as described in Microsoft Docs. Use the following JSON. In the
a ssignableScopes field, specify your subscription ID.

JSON — P ermissions for Existing Application

2017 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
{
"properties": {
"roleName": "
Veeam Restore Operat
or",
"description"
: "Permissions neede
d for an application
for an Azure Compute
Account",
"assignableSc
opes": [
"/subscri
ptions/your_subscrip
tion_ID_here"
],
"permissions"
: [
{
"acti
ons": [
"
Microsoft.Storage/st
orageAccounts/listke
ys/action",
"
Microsoft.Storage/st
orageAccounts/read",
"
Microsoft.Network/lo
cations/checkDnsName
Availability/read",
"
Microsoft.Network/vi
rtualNetworks/read",
"
Microsoft.Network/vi
rtualNetworks/subnet
s/join/action",
"
Microsoft.Network/pu
blicIPAddresses/read
",
"
Microsoft.Network/pu
blicIPAddresses/writ
e",
"
Microsoft.Network/pu
blicIPAddresses/dele
te",
"
Microsoft.Network/pu
blicIPAddresses/join
/action",
"
Microsoft.Network/ne
tworkInterfaces/read
",

2018 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
"
Microsoft.Network/ne
tworkInterfaces/writ
e",
"
Microsoft.Network/ne
tworkInterfaces/dele
te",
"
Microsoft.Network/ne
tworkInterfaces/join
/action",
"
Microsoft.Network/ne
tworkSecurityGroups/
read",
"
Microsoft.Network/ne
tworkSecurityGroups/
write",
"
Microsoft.Network/ne
tworkSecurityGroups/
delete",
"
Microsoft.Network/ne
tworkSecurityGroups/
join/action",
"
Microsoft.Compute/lo
cations/vmSizes/read
",
"
Microsoft.Compute/lo
cations/usages/read"
,
"
Microsoft.Compute/vi
rtualMachines/read",
"
Microsoft.Compute/vi
rtualMachines/write"
,
"
Microsoft.Compute/vi
rtualMachines/delete
",
"
Microsoft.Compute/vi
rtualMachines/start/
action",
"
Microsoft.Compute/vi
rtualMachines/deallo
cate/action",
"
Microsoft.Compute/vi
rtualMachines/extens
ions/read",

2019 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
"
Microsoft.Compute/vi
rtualMachines/extens
ions/write",
"
Microsoft.Resources/
checkResourceName/ac
tion",
"
Microsoft.Resources/
subscriptions/resour
ceGroups/read",
"
Microsoft.Resources/
subscriptions/resour
ceGroups/write",
"
Microsoft.Resources/
subscriptions/locati
ons/read"
],
"notA
ctions": [],
"data
Actions": [],
"notD
ataActions": []
}
]
}
}

3. Assign the created role to the required Microsoft Entra ID application. For details, see the Manage access
to Azure resources using RBAC and the Azure portal section in the RBAC for Azure resources
documentation.

4. At the Account Type step of the Microsoft Azure Compute Account wizard, select Use existing account.

5. At the Subscription step of the wizard, specify the Microsoft Entra ID application with the assigned role.

Permissions for Azure Stack Hub Compute Account (New


Application)
If you plan to add an Azure Stack Hub account using a new Microsoft Entra ID (formerl y Azure Active Directory)
application (select the Create a new a ccount option at the Subscription step of the wizard), and you do not want
to use built-in Azure roles, you can create a custom role with granular permissions:

1. In the Azure Stack Hub management portal, go to subscription properties and open Access control (IAM).

2. Create a custom role from a JSON file as described in Microsoft Docs. Use the following JSON. In the
a ssignableScopes field, specify your subscription ID.

JSON — P ermissions for New Application

2020 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
{
"properties": {
"roleName": "
Veeam Register Azure
Compute Account usin
g new Microsoft Entr
a ID application",
"description"
: "Permissions neede
d for a user to add
an Azure Compute Acc
ount based on new Mi
crosoft Entra ID app
lication",
"assignableSc
opes": [
"/subscri
ptions/00000000-0000
-0000-0000-000000000
000"
],
"permissions"
: [
{
"acti
ons": [
"
Microsoft.Authorizat
ion/roleDefinitions/
read",
"
Microsoft.Authorizat
ion/roleAssignments/
read",
"
Microsoft.Authorizat
ion/roleAssignments/
write"
],
"notA
ctions": [],
"data
Actions": [],
"notD
ataActions": []
}
]
}
}

3. Assign the created role to the required Microsoft Entra ID user. For details, see the Manage access to
Azure resources using RBAC and the Azure portal section in the RBAC for Azure resources documentation.

4. At the Account Type step of the Microsoft Azure Compute Account wizard, select Create a new account.

5. At the Sub scription step, configure the account as described in section Creating New Microsoft Entra ID
Application. On the Microsoft Azure device authentication page, specify an Microsoft Entra ID user
account with the assigned role.

2021 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

The described permissions are required for assigning a role on the subscription level for the registered
application. Also, privileges to register applications are required. For more information, see Permissions.

Managing Helper Appliances


Helper appliances are Linux-based VMs in Microsoft Azure registered by Veeam Backup & Replication. Helper
appliances are required to restore Linux workloads to Microsoft Azure. During the restore process,
Veeam Backup & Replication mounts disks of a backed-up workload to a helper appliance to prepare disks for
restore.

To instruct Veeam Backup & Replication to deploy helper appliances, you must configure them as described in
section Configuring Helper Appliances. When deploying the helper appliance, Veeam Backup & Replication
analyzes the VM sizes available in the restore region and selects the cheapest and smallest size suitable for
using the helper appliance.

Helper appliances are persistent. After the restore process finishes, helper appliances get powered off and
remain in Microsoft Azure. The appliances remain in the powered off state until you start a new restore process.
Note that Microsoft Azure will bill you for storing helper appliances disks in the storage account. To remove a
helper appliance, follow the instruction provided in Removing Helper Appliances.

Configuring Helper Appliances

Before you configure helper appliances, consider the following:

• Veeam Backup & Replication uses its built-in credentials record to work with all helper appliances. For
security reasons, we recommended that you change a password for this account before you set up the
helper appliances. Changing credentials is required only once. For more information, see Changing
Credentials for Helper Appliances.

• If you plan to restore Linux workloads to different locations, you must configure a helper appliance in each
location to which workloads will be restored.

Helper appliances are configured when you add a Microsoft Azure compute or Microsoft Azure Stack account.
For more information, see the Helper Appliance step description in the Microsoft Azure Compute Accounts or
Microsoft Azure Stack Hub Compute Accounts section.

Changing Credentials for Helper Appliances

By default, Veeam Backup & Replication uses its built-in credentials record to work with all helper appliances in
Microsoft Azure and Azure Stack Hub. You can find this credential record in the credentials manger in the
Veeam Backup & Replication console: the root account with "Azure helper appliance credentials" in the
Description column.

For security reasons, we recommend you to change the password for this credentials record before you set up
helper appliances.

IMP ORTANT

When you change the password in the built-in credentials record, you must re-deploy all existing helper
appliances in Microsoft Azure and Azure Stack Hub. To redeploy appliances, you must remove all
configured appliances and then configure them once again.

2022 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
To change the password in the credentials record for the helper appliances:

1. From the main menu, select Credentials and Passwords > Datacenter Credentials.

2. In the Ma nage Credentials window, click the built-in credentials record for the helper appliances.

3. Click E d it.

4. In the P a ssword field, specify a new password.

5. Click OK to save changes.

Removing Helper Appliances


If you no longer need to restore Linux workloads to Azure or Azure Stack Hub, you can remove helper
appliances:

1. From the main menu, select Ma nage Cloud Credentials.

2. In the accounts list, select the Azure account and click E d it.

3. Pass to the Helper Appliance step of the Microsoft Azure Compute Account wizard.

4. In the Helper appliances list, select the helper appliance and click Remove.

IMP ORTANT

Do not clear the E na ble restore of Linux-based computers check box at the Sub scription step of the wizard
before removing helper appliances. If you clear the check box, the Microsoft Azure Compute Account
wizard will not display the Helper Appliance step. Helper appliances themselves will remain in Microsoft
Azure. Clear the E nable restore of Linux-based computers check box only after you remove the helper
appliances.

You can remove all helper appliances using the Deploy-VBRAzureLinuxRestoreAppliance PowerShell
cmdlet.

2023 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Managing Azure Restore Proxy Appliances
Azure restore proxy appliances (former Azure proxies) are Windows-based VMs over which
Veeam Backup & Replication transports VM disk data to Blob storage. Veeam Backup & Replication uses Azure
restore proxy appliances during restore of Windows-based and Linux-based workloads.

Azure restore proxy appliances help speed up the restore process especially if you restore workloads to a di stant
location or the network connection is slow. Veeam components installed on an Azure restore proxy appliance
compress and deduplicate disk data, which helps reduce network traffic.

Although Azure restore proxy appliances are optional, we recommend you to configure them. Azure restore
proxy appliances do not require a lot of resources but can significantly improve restore performance. Configure
an Azure restore proxy appliance in a location to which you plan to restore workloads or close to this location. If
you plan to restore workloads to different locations, configure at least one Azure restore proxy appliance in
each location.

The process of Azure restore proxy appliance deployment takes some time. We recommend you to configure the
Azure restore proxy appliance in advance, before you start the restore process. To configure an Azure restore
proxy appliance, use the New Azure Restore Proxy Appliance wizard as described in section Configuring Azure
Restore Proxy Appliances. Veeam Backup & Replication will deploy a Microsoft Windows Server machine in
Microsoft Azure and will assign the role of the Azure restore proxy appliance to this machine. You can then
instruct Veeam Backup & Replication to use the Azure restore proxy appliance for restore tasks.

The Azure restore proxy appliance is persistent. After the restore process finishes, the Azure restore proxy
appliance gets powered off and remains in Microsoft Azure. The Azure restore proxy appliance remains in the
powered off state until a new restore process is started. Note that Microsoft Azure will bill you for storing Azure
restore proxy appliance disks in the storage account. To remove an Azure restore proxy appliance, follow the
instruction provided in Removing Azure Restore Proxy Appliances.

Configuring Azure Restore Proxy Appliances


To configure an Azure restore proxy appliance, use the New Azure Restore Proxy Appliance wizard.

2024 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Before You Begin

Before you configure an Azure restore proxy applia nce, check the following prerequisites:

• You must add information about your Microsoft Azure Compute account or Microsoft Azure Stack Hub
Compute account to Veeam Backup & Replication. For more information, see Adding Microsoft Azure
Compute Accounts or Adding Azure Stack Hub Compute Accounts.

• You must configure the following objects in Microsoft Azure beforehand:

o Storage account whose resources will be used to deploy the Azure restore proxy appliance.

o Networks to which you plan to connect the Azure restore proxy appliance.

For storage accounts and network configuration, you must use the same deployment model that you plan
to use for Azure restore proxy appliance creation.

IMP ORTANT

When you deploy Azure restore proxy appliance for Azure Stack Hub, make sure that Windows Server 2019
is available in Azure marketplace.

2025 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch New Azure Restore Proxy Appliance Wizard

To launch the New Azure Restore Proxy Appliance wizard, do one of the following:

1. Open the Ba ckup Infrastructure view.

2. In the inventory pane, right-click the Ba ckup Proxies node and select Ad d Proxy. Alternatively, you can
click Ad d Proxy on the ribbon.

3. In the Ad d Backup Proxy window, select Azure proxy appliance.

2026 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Azure Restore Proxy Appliance Name

At the Na me step of the wizard, specify a name and description for the Azure restore proxy appliance:

1. In the Na me field, specify a name for the Azure restore proxy appliance. The name must meet the
following requirements:

o The name must not be longer than 15 characters.

o The name must contain only alphanumeric characters and hyphens.

o The name must start with a letter and end with a letter or number.

o The name must not contain only numeric characters.

o The name must not contain special characters: `!@#$%^&*()+=_[]{}\;:.'",<>/?.

2. In the Description field, provide a description for the Azure restore proxy appliance.

3. At the Ma x concurrent tasks field, specify the number of tasks that the Azure restore proxy appliance must
handle in parallel. If the Ma x concurrent tasks value is exceeded, the Azure restore proxy appliance will
not start a new task until one of current tasks finishes.

Veeam Backup & Replication creates one task per one workload disk. By default, Azure restore proxy
appliance handles 4 concurrent tasks.

2027 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Credentials and Transport Port

At the Credentials step of the wizard, specify credentials of the local administrator account on the Azure restore
proxy appliance and define the transport port:

1. From the Credentials list, select credentials of a user that will be assigned the Local Administrator
permissions on the Azure restore proxy appliance.

If you have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right to
add the credentials. For more information, see Managing Credentials.

IMP ORTANT

Consider the following:

• You cannot use reserved names such as 'administrator', 'admin', 'user', 'abc@123', 'P@$$w0rd'
and so on as a user name and password of the local administrator account.
• You must specify the user name without a domain or Microsoft Azure machine name.
• The password must be at least 8 characters long, and must contain at least 1 uppercase
character, 1 lowercase character, 1 numeric character and 1 special character.

2. In the Tra ffic port field, specify a port over which Veeam Backup & Replication will control components
installed on the Azure restore proxy appliance and transport workload disks data to Blob storage. The port
must be accessible from the backup server and backup repository that stores backups.

2028 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Subscription and Location

At the Sub scription step of the wizard, select a subscription and location for the Azure restore proxy appliance:

1. From the Sub scription list, select a subscription whose resources you want to use to deploy the Azure
restore proxy appliance. The subscription list contains all subscriptions associated with Azure or Azure
Stack Hub Compute accounts that you added to Veeam Backup & Replication.

2. From the Locations list, select a geographic region to which you want to place the Azure restore proxy
appliance. Make sure that you select a geographic region with which at least one storage account of the
subscription is associated.

2029 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select VM Size

At the VM size step of the wizard, you can select the size for the Azure restore proxy appliance VM and specify
which storage account you want to use to deploy the Azure restore proxy appliance VM:

1. From the Size list, select the size for the Azure restore proxy appliance.

The default size is Standard_F4s_v2. If Standard_F4s_v2 is not available, we recommend that you select a
similar compute optimized VM size of the previous generation — F-series. For example, Standard_F4,
Standard_F4s . These sizes are sufficient to transport VM disks data to Blob storage. If necessary, you can
select a greater size for the Azure restore proxy appliance.

NOTE

Azure restore proxy appliance VMs created in Veeam Backup & Replication version prior 10a have
smaller sizes — Basic_A2. We recommend you to change sizes of such proxies to the sizes listed in this
point. This will enhance the performance of restore to Azure.

You can change VM sizes in Microsoft Azure Portal or deploy new proxies with the required sizes in
the Veeam Backup & Replication.

2. From the Storage account list, select a storage account where Veeam Backup & Replication will store
components required for Azure restore proxy appliance deployment. After restore, the components will
be removed from the storage account.
[For Azure Stack Hub] Veeam Backup & Replication will store disks of the Azure restore proxy appliance in
the selected storage account. The storage account must be compatible with the VM size you select.

The list of storage accounts will contain only general purpose storage accounts. Blob storage accounts will
not be displayed in the list of subscriptions. For more information about account types, see Microsoft
Docs.

NOTE

You cannot use a storage account with the ZRS or GZRS replication option for the Azure restore
proxy appliance. For details, see Microsoft Docs.

TIP

Microsoft Azure subscriptions have default limits on the number of CPU cores. Make sure that the
VM size you select does not exceed limits of the subscription.

2030 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2031 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Resource Group

At the Resource Group step of the wizard, you specify the resource group to which the Azure restore proxy
appliance must be placed and configure DNS name label:

1. You can place the Azure restore proxy appliance to an existing or new resource group:

o Select P la ce VM into the existing resource group to place the Azure restore proxy appliance to an
existing resource group. From the drop-down list, select the necessary resource group.

o Select Create a new resource group to create a dedicated resource group for the Azure restore proxy
appliance. In the Na me field, enter a name for the new resource group. The resource group name can
be up to 64 characters long and can contain only alphanumeric, underscore and hyphen characters.

For the new resource group, Veeam Backup & Replication automatically creates a network security
group, dynamic public IP and network interface.

2. In the DNS name label field, enter a name of the dynamic public IP. The DNS name label can be up to 80
characters long, and can contain only alphanumeric, dash and underscore characters. For more
information, see Microsoft Docs.

TIP

Microsoft Azure subscriptions have default limits on the number of resource groups. If you decide to create
a new resource group, make sure that you do not exceed limits of the subscription.

2032 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Select Virtual Network

At the Network step of the wizard, you select to which network and subnet the Azure restore proxy appliance
will be connected.

IMP ORTANT

If you want to restore from backups in an on-premises object storage repository, the selected virtual
network must have access to the source object storage repository. To provide access to object storage
repositories, you can use VPN or Azure ExpressRoute. For more information, see this Veeam KB article.

2033 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Start Deployment

At the Ap p ly step of the wizard, Veeam Backup & Replication deploys the Azure restore proxy appliance with
the specified settings. You can view the deployment progress in the real-time mode. When the configuration
process is over, click Nex t. At the Summary step of the wizard, click Finish to close the wizard.

TIP

The Azure restore proxy appliance deployment may take several minutes. You can close the New Azure
Restore Proxy Appliance wizard and continue working with Veeam Backup & Replication while the helper
appliance is being deployed. To view the deployment progress, open the History view, in the inventory
pane select Sy stem, and double-click the task of the helper appliance deployment in the working area.

Removing Azure Restore Proxy Appliances

Veeam Backup & Replication does not provide a possibility to edit settings of deployed Azure restore proxy
appliances. If you want to change Azure restore proxy appliance configuration, r emove the Azure restore proxy
appliance and create a new Azure restore proxy appliance.

To remove an Azure restore proxy appliance, do the following:

1. Open the Ba ckup Infrastructure view.

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

3. In the working area, right-click the Azure restore proxy appliance and select Remove.

IMP ORTANT

If you want to remove an Azure or an Azure Stack Hub Compute account from Veeam Backup & Replication,
you must remove all Azure restore proxy appliances first.

2034 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring to Microsoft Azure
Before you restore workloads to Microsoft Azure, you must configure an account to be used for restore and
required components. For more information, see Configuring Components and Accounts for Restore. Then use
the Restore to Azure wizard to restore the workloads.

NOTE

If you added the Veeam Backup for Microsoft Azure appliance to the Veeam Backup & Replication
infrastructure and you plan to restore Microsoft Azure VMs from restore points that were created using the
appliance, the steps of the restore wizard differ from the steps described in this guide. For more
information, see the Restoring to Microsoft Azure section in the Integration with Veeam Backup for
Microsoft Azure Guide.

Before You Begin


Before you begin restore to Microsoft Azure, check the following prerequisites:

• Check limitations listed in section Limitations for Restore to Microsoft Azure.

• You must create a backup of the workload that you want to restore in Microsoft Azure. For the list of
supported backups, see Restore to Microsoft Azure.

• A backup chain from which you plan to restore a workload must reside in a backup repository added to the
backup infrastructure. You can also import a backup to the Veeam Backup & Replication console. For more
information, see Importing Backups.

• You must configure the following objects in Microsoft Azure beforehand:

o Storage account whose resources you plan to use to store disks of the restored workload.

o Networks to which you plan to connect the restored workload.

• Make sure that you configured all the required components and accounts in Veeam Backup & Replication
as described in section Configuring Components and Accounts for Restore.

2035 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• [For speeding up restore from Capacity Tier] It is strongly recommended to use Azure restore proxy
appliance when you restore from backups residing on a Capacity Tier. For more information on Azure
restore proxy appliances, see Managing Microsoft Azure Restore Proxy Appliances.

• You must set up correct time on the backup server. Otherwise you may not be able to add a Microsoft
Azure Compute account or Microsoft Azure Stack Hub Compute account to Veeam Backup & Replication,
or the restore process may fail.

2036 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Restore to Azure Wizard
To launch the Restore to Azure wizard, do one of the following:

• On the Home tab, click Restore and select the type of backups from which you want to restore:

o VMware vSphere

o VMware Cloud Director

o Microsoft Hyper-V

o Agent

o AWS

o GCE backup

o Nutanix backup

o RHV Proxy

In the displayed window, click E ntire VM restore > Restore to public cloud > Restore to Microsoft Azure.

• Open the Home view. In the inventory pane, click Ba ckups. In the working area, expand the necessary
backup, select workloads that you want to restore and click Restore to Microsoft Azure on the ribbon.
Alternatively, you can right-click one of the workloads that you want to restore and select Restore to
Microsoft Azure.

• Double-click a full backup file (VBK) or backup metadata file (VBM) in a file browser.
Veeam Backup & Replication will start its console. In the Ba ckup P roperties window, select the necessary
workload and click Restore > Restore to Microsoft Azure.

2037 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workloads and Restore Points
At the Ma chine step of the wizard, specify workloads that you want to restore and specify restore points to
which you want to restore the workloads. By default, Veeam Backup & Replication restores workloads to the
latest valid restore point in the backup chain.

Selecting Workloads
To select workloads to restore:

1. On the right of the Ma chine list, click Ad d .

2. In the Ba ckup Browser window, expand the necessary backup, select workloads and click Ad d .

Selecting Restore Points


To select a restore point for a workload, do the following:

1. In the Ma chine list, select a workload.

2. Click P oint on the right.

2038 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Restore Points window, select a restore point to which you want to restore the workload.

2039 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Subscription and Location
At the Sub scription step of the wizard, select a subscription, location for the restored workloads and define how
workload data must be transported to Microsoft Azure or Azure Stack Hub:

1. From the Sub scription list, select a subscription whose resources you want to use. The subscription list
contains all subscriptions associated with the Azure compute or Azure Stack Hub Compute accounts that
you have added to Veeam Backup & Replication.

2. From the Locations list, select a geographic region to which you want to place the restored workloads.
Make sure that you select a geographic region with which at least one storage account of the subscriptions
is associated.

3. If you are restoring the workloads to a distant location and want to speed up the restore process, select
the Use a p roxy appliance check box. From the drop-down list, select an Azure restore proxy appliance.

It is recommended that you configure the Azure restore proxy appliance in the same location to which you
plan to restore the workload. For more information, see Managing Azure Restore Proxy Appliances.

IMP ORTANT

[For restore of Linux workloads] You must have a preconfigured helper appliance in the location to which
you restore Linux workloads. If the appliance is not configured, Veeam Backup & Replication will display
the Microsoft Azure Compute Account wizard so that you can configure the appliance in the selected
location.

2040 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Names and Tags
At the Na me step of the wizard, you can specify new names for the restored workloads and assign tags to them.
By default, Veeam Backup & Replication restores workloads with their original names.

Specifying New Names


To define a new name for a workload:

1. In the Ma chines to restore list, select a workload and click VM Na me.

2. In the Cha nge Name window, enter a new name explicitly or specify a change name rule — add a prefix and
suffix to the original workload name.

Adding Tags
To add a tag for the restored workloads:

1. In the Ma chines to restore list, select a workload and click Ta g s.

2. In the Ta g s window, click Ad d .

2041 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Microsoft Azure VM Tag window, specify the tag name and its value.

2042 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify VM Size and Disks
At the VM Size step of the wizard, you can select VM sizes, storage accounts where to store disks of the restored
workloads, select disks to restore and change their type. By default, Veeam Backup & Replication selects the
smallest size that can support the number of disks for the restored workload and restores all workload disks.

Selecting VM Size and Storage Account


To select a size and storage account:

1. In the Azure VM Configuration list, select a workload and click E d it.

2. From the Size list, select a size for the restored workload.

Make sure that you select the right workload size that corresponds to the initial workload configuration.
The size affects the number of CPU cores, memory and disk resources that will be allocated to the
restored workload. For more information, see Microsoft Docs.

3. From the Storage type list, select the disk type. Note the limitations for disk sizes in Limitations for
Restore to Microsoft Azure.

4. From the Storage account list, select a storage account whose resources you want to use to store disks of
the restored workload. The storage account must be compatible with the workload size you select. Note
the limitations for storage accounts in Limitations for Restore to Microsoft Azure.

The list of storage accounts contains only general purpose storage accounts. Blob storage accounts are
not be displayed in the list of subscriptions. For more information about account types, see Microsoft
Docs.

If you select a premium storage account, make sure that the restored workload size is compatible with the
selected account.

NOTE

Microsoft Azure subscriptions have default limits on the number of CPU cores. Make sure that the restored
workload size that you select does not exceed limits of the subscription.

2043 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Selecting Disks to Restore and Changing Their Types
You can restore all disks or specific disks of a workload. You can also change disk types of the restored disks if
you have selected the managed storage type.

To select specific disks and change their type, do the following:

1. In the Azure VM Configuration list, select a workload and click Disks.

2. In the Disks to restore window, check that check boxes next to disks that you want to restore are selected.
Clear check boxes next to disks that you do not want to restore.

3. [For managed storage type] Select a disk and click Disk Type. In the Select Azure VM Disk Type window,
select the necessary type. For more information on disk types, see Microsoft Docs.

IMP ORTANT

The selected disk type must be compatible with the selected workload size.

2044 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2045 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify VM Name and Resource Group
At the Resource Group step of the wizard, you can select resource groups for the restored workloads for them.
By default, Veeam Backup & Replication creates a new resource group for the restored workloads and places
them to it.

To change a resource group to which a workload will be restored:

1. In the Resource group list, select a workload and click Group.

2. In the VM Resource Group window, select the necessary option for the workload:

o Select P la ce VM into the existing resource group if you want to place the workload to an existing
resource group. Then from the drop-down list, select the necessary resource group.

o Select Create a new resource group if you want to create a dedicated resource group for the restored
workload. In the Na me field, enter a name for the new resource group.

In the new resource group, Veeam Backup & Replication automatically creates a network security
group, a dynamic public IP and network interface.

NOTE

Microsoft Azure subscriptions have default limits on the number of resource groups. If you decide to create
a new resource group, make sure that you do not exceed limits of the subscription.

2046 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Configure Network Settings
At the Network step of the wizard, select to which networks and subnets the restored workloads will be
connected. By default, Veeam Backup & Replication creates a new security group for the restored workloads.

Configuring Network
To define network settings for a workload, do the following:

1. In the Virtual network list, select a workload and click Network.

2. From the Virtual network drop-down list, select a network to which the workload must be connected.

3. From the Sub net drop-down list, select a subnet for the workload.

4. In the P ub lic IP field, specify whether to assign a public IP to the workload. You have two options:

o Assign (restored VM will be accessible from the Internet). The public IP will be assigned to the
restored workload. For security reasons, make sure traffic filtration rules are properly configured in
the security group.

o Do not assign (more secure). The public IP will not be assigned. You can assign a public IP later in the
settings of the restored workload.

NOTE

Veeam Backup & Replication can connect a workload only to one virtual network. If necessary, you can
manually configure additional network connections in Microsoft Azure after the workload is restored.

2047 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Configuring Security Group
To change a security group to which a workload will be restored:

1. From the Virtual network list, select a workload and click Group.

2. Select the network security group from the Network security group list.

If you leave the Empty value, Veeam Backup & Replication will create a new network security group.

2048 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Secure Restore Settings
This step is available if you restore Microsoft Windows workloads.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o Ab ort VM recovery. Select this action if you want Veeam Backup & Replication to cancel the restore
session.

o P roceed recovery b ut connect VM to a different network. Select this action if you want to restore the
workload to a different Microsoft Azure virtual network.

Click the Click to change link to select the virtual network.

6. Select the Continue scanning all remaining files after the first occurrence (Scan entire VM for virus threats
– for version 12 (build 12.0.0.1420)) check box if you want to continue workload scan after the first
malware is found. For information on how to view results of the malware scan, see Viewing Malware Scan
Results.

2049 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for restoring the workload. The information you provide will be
saved in the session history in Veeam Backup & Replication, and you can view it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2050 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Verify Restore Settings
At the Rea dy to Restore step of the wizard, check the specified settings and click Finish. If you want to start the
Azure VM right after restore, select the P ower on VM after restoring check box.

You can trace the restore process in the Restore Session window. If you need to cancel the workload restore,
click the Ca ncel restore task link.

2051 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore to Amazon EC2
Veeam Backup & Replication allows you to restore different workloads (VMs, Google VM instances, physical
servers and so on) to Amazon Elastic Compute Cloud (Amazon EC2) as EC2 instances. An EC2 instance is a virtual
machine in Amazon EC2 with a preconfigured combination of computing resources.

You can use Veeam Backup & Replication to perform the following operations:

• Restore workloads to Amazon EC2 from backups.

• Migrate workloads from the on-premises infrastructure to the cloud.

• Create a test environment in the cloud for troubleshooting, testing patches and updates, and so on.

Supported Backup Types


You can restore workloads from the following types of backups:

• Backups of VMware vSphere or VMware Cloud Director virtual machines created by


Veeam Backup & Replication.

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication.

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

Backups must be created at the entire machine level or volume level.

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure.

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

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV.

• Backups of RHV VMs created by Veeam Backup for RHV.

Helper Appliances
Helper appliance is an auxiliary Linux-based EC2 instance. It is used to upload backed-up data to Amazon EC2.
Veeam Backup & Replication automatically deploys the helper appliance in Amazon EC2 only for the duration of
the restore process and removes it immediately after that.

Depending on the type of backups you are restoring from and their location, the helper appliance may be
required or optional. The helper appliance is required when you restore from:

• Backups of EC2 instances that are stored in external repositories.

• Backups of virtual and physical machines that are stored in object storage repositories.

The helper appliance is optional when you restore from backups of virtual and physical machines stored in
backup repositories, or backups of EC2 instances copied to backup repositories with backup copy jobs. It is
recommended, however, to use the helper appliance in scenarios where it is optional, as the helper appliance
can significantly improve restore performance. You can specify the helper appliance settings at the Helper
Appliance step of the Restore to Amazon EC2 wizard.

2052 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Helper Appliance
When configuring a helper appliance, consider the following:

• If you want to restore from backups in an on-premises object storage repository, the helper appliance
machine must have access to the source object storage repository. To provide access to object storage
repositories, you can use VPN or AWS Direct Connect.

• To upload one machine disk to Amazon EC2, the helper appliance requires 1 GB RAM. Make sure that the
type of EC2 instance selected for the helper appliance offers enough memory resources to upload all
machine disks. Otherwise, the restore process may fail.

• A subnet and security group that you select for the helper appliance must meet the following
requirements:

o Auto-assignment of public IPv4 addresses must be enabled in the subnet. For more information on
how to enable this option, see the AWS Documentation.

o The subnet route table must contain a default route to an active AWS internet gateway. For more
information on internet gateways and how to create route tables, see the AWS Documentation.

o The subnet must have no network access control lists (ACLs) or a network ACL that allows inbound
and outbound traffic on the ports listed in section Ports.

o The security group must allow inbound and outbound traffic on the ports listed in section Ports.

How Restore to Amazon EC2 Works


The workflow of the restore process depends on whether the helper appliance is used or not. For more
information on the helper appliance, see Helper Appliance.

NOTE

If you added the Veeam Backup for AWS appliance to the Veeam Backup & Replication infrastructure and
you plan to restore Amazon EC2 instances from restore points that were created using the appliance, you
do not need to configure the helper appliance. Also, restore to Amazon EC2 works as described in t he
Entire EC2 Instance Restore section in the Veeam Backup for AWS User Guide.

Restoring to Amazon EC2 with Helper Appliance


If a helper appliance is required or you selected to use it for restore to Amazon EC2,
Veeam Backup & Replication performs the following operations:

1. Veeam Backup & Replication creates a helper appliance in Amazon EC2.

During the restore process, the helper appliance communicates with backup infrastructure components
over the SSH protocol and the network redirector that is deployed on the helper appliance.

2. For every disk of a backed-up workload, Veeam Backup & Replication creates an empty EBS volume in
Amazon EC2.

3. Veeam Backup & Replication hot-adds empty disks to the helper appliance and restores backed -up data to
the EBS volumes.

4. [For backups of EC2 instances] Veeam Backup & Replication creates a target instance in Amazon EC2.

2053 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. [For backups of EC2 instances] Veeam Backup & Replication detaches the EBS volumes from the helper
appliance and attaches them to the target instance.

6. [For backups of other workloads] Veeam Backup & Replication requests Amazon to create snapshots of
the attached EBS volumes. The snapshots are created in Amazon S3.

7. [For backups of other workloads] Veeam Backup & Replication requests Amazon to use the VM Import
functionality to import a VM from EBS volume snapshots to Amazon EC2.

8. [For backups of other workloads] After the restore process is complete, Veeam Backup & Replication
removes the snapshots created in Amazon S3.

9. Veeam Backup & Replication removes helper appliance from Amazon EC2.

Restoring to Amazon EC2 without Helper Appliance


If you selected not to use a helper appliance for restore to Amazon EC2, Veeam Backup & Replication performs
the following operations:

1. Veeam Backup & Replication uploads disks of a backed-up workload to Amazon S3.

In Amazon S3, the uploaded disks are stored to the temporary bucket in the RAW for mat.

2. Veeam Backup & Replication imports the backed-up data from the temporary bucket in Amazon S3 to EBS
volumes in Amazon EC2.

3. Veeam Backup & Replication creates a target instance in Amazon EC2 and attaches the EBS volumes to it.

4. After the import process is complete, Veeam Backup & Replication removes the temporary bucket from
Amazon S3.

AWS IAM User Permissions


To restore to Amazon EC2, it is recommended that the IAM user whose credentials you plan to use to connect to
AWS has administrative permissions — access to all AWS actions and resources.

If you do not want to provide full access to AWS, you can grant to the IAM user a minimal set of permissions that
will be sufficient for restore. To do that, create the following policy in the JSON format and attach it to the IAM
user.

NOTE

The ec2: CreateRole permission is required if you want to perform restore without helper appliances.
This permission is used to create a service role named vmimport required for import to Amazon EC2. If you
plan to restore workloads using helper appliances, you can omit the ec2: CreateRole permission.
However, restore without helper appliances will fail.

{
"Version": "2012-10-17",
"Statement": [{
"Action": [
"ec2:DescribeInstances",
"ec2:DescribeInstanceTypes",
"ec2:RunInstances",
"ec2:TerminateInstances",
"ec2:StartInstances",
"ec2:StopInstances",

2054 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
"ec2:ModifyInstanceAttribute",
"ec2:DescribeImages",
"ec2:ImportImage",
"ec2:DeregisterImage",
"ec2:DescribeVolumes",
"ec2:CreateVolume",
"ec2:ModifyVolume",
"ec2:ImportVolume",
"ec2:DeleteVolume",
"ec2:AttachVolume",
"ec2:DetachVolume",
"ec2:GetEbsEncryptionByDefault",
"ec2:CreateSnapshot",
"ec2:DescribeSnapshots",
"ec2:DeleteSnapshot",
"ec2:DescribeSubnets",
"ec2:DescribeNetworkInterfaces",
"ec2:DescribeSecurityGroups",
"ec2:DescribeKeyPairs",
"ec2:CreateKeyPair",
"ec2:DeleteKeyPair",
"ec2:DescribeAvailabilityZones",
"ec2:DescribeVpcs",
"ec2:DescribeConversionTasks",
"ec2:DescribeImportImageTasks",
"ec2:DescribeVolumesModifications",
"ec2:CancelImportTask",
"ec2:CancelConversionTask",
"ec2:CreateTags",
"ec2:DescribeAccountAttributes",
"ec2:DescribeDhcpOptions",
"ec2:DescribeVpcAttribute",
"iam:GetRole",
"iam:CreateRole",
"iam:PutRolePolicy",
"iam:DeleteRolePolicy",
"s3:CreateBucket",
"s3:ListBucket",
"s3:ListAllMyBuckets",
"s3:DeleteBucket",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetBucketLocation",
"s3:PutLifeCycleConfiguration",
"s3:GetObject",
"s3:RestoreObject",
"s3:AbortMultiPartUpload",
"s3:ListBucketMultiPartUploads",
"s3:ListMultipartUploadParts"
],
"Effect": "Allow",
"Resource": "*"
}]
}

Alternatively, you can attach the created policy to the IAM group or role to which the IAM user is assigned.

For information on how to create and attach a policy to an IAM user, see the Creating IAM Policies and Adding
and Removing IAM Identity Permissions sections in the AWS IAM User Guide.

2055 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring to Amazon EC2
To restore workloads to Amazon EC2, use the Restore to Amazon E C2 wizard.

NOTE

If you added the Veeam Backup for AWS appliance to the Veeam Backup & Replication infrastructure and
you plan to restore Amazon EC2 instances from restore points that were created using the appliance, the
steps of the restore wizard differ from the steps described in this guide. For more information, see the
Restoring to Amazon section in the Integration with Veeam Backup for AWS Guide.

Before You Begin


Before you restore workloads to Amazon EC2, consider the following requirements and limitations:

• Check whether a helper appliance must be configured for restore. For more information, see Helper
Appliances.

• Make sure that a user whose credentials you plan to use to connect to AWS has permissions to restore to
Amazon EC2. For more information, see AWS IAM User Permissions.

• You must have a backup of the workload that you plan to restore to Amazon EC2.

• The backup server and repositories with workload backup files must have access to the internet.

If backup files are located on deduplicating storage appliances or shared folder repositories, the internet
connection is required for gateway servers that communicate with these repositories.

• If you use a cloud-init-based Linux distribution, we recommend that you use SSH keys on these
distributions. If you use a password, it is blocked after restore for security reasons. To reset the password
on the restored instance, use the technologies described in AWS Documentation.

• If you restore workloads other than EC2 instances, check the supported OS, EC2 instance and file system
types in the AWS Documentation.

• Check that the logical sector size of disks that you plan to restore is less than 4096 bytes. Contents of
disks whose logical sector size is 4096 bytes will be unreadable in Amazon EC2.

• [For restore of EC2 instances without helper appliance] If you restore workloads with more than five disks,
check that the Limit maximum concurrent tasks option of the repository where the backups are stored is
equal or less than the limit of the AWS ImportVolume service for concurrent tasks.
Veeam Backup & Replication uses this service during the restore. For more information on the limit, see
AWS Documentation.

• If you plan to assign AWS tags to the restored EC2 instance, check limitations for tags in the AWS
Documentation.

• [For Veeam Backup & Replication server located in Amazon EC2] If you restore workloads from a backup
stored in an object storage repository, we recommend using Private IPs to increase the transfer speed. For
more information, see this Veeam KB article.

2056 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Restore to Amazon EC2 Wizard
To begin the restore process, do one of the following.

• On the Home tab, click Restore and select the type of backups from which you want to restore:

o VMware vSphere

o VMware Cloud Director

o Microsoft Hyper-V

o Agent

o AWS

o Azure IaaS backup

o GCE backup

o Nutanix AHV

o RHV Proxy

In the displayed window, click E ntire VM restore > Restore to public cloud > Restore to Amazon EC2.

• Open the Home view. In the inventory pane, click Ba ckups. In the working area, expand the necessary
backup, select workloads that you want to restore and click Restore to Amazon EC2 on the ribbon.
Alternatively, you can right-click one of the workload that you want to restore and select Restore to
Ama zon EC2.

• Double-click a full backup file (VBK) or backup metadata file (VBM) in a file browser.
Veeam Backup & Replication will start its console. In the Ba ckup P roperties window, select the necessary
workload and click Restore > Restore to Amazon EC2.

2057 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workloads and Restore Points
At the Ma chine step of the wizard, specify workloads that you plan to restore and restore points to which you
want to restore the workloads. By default, Veeam Backup & Replication restores workloads to the latest valid
restore point in the backup chain.

Selecting Workloads
To select workloads to restore:

1. On the right of the Ma chine list, click Ad d .

2. In the Ba ckup Browser window, expand the necessary backup, select the workloads and click Ad d .

Selecting Restore Point


To select a restore point for a workload:

1. In the Ma chine list, select a workload.

2. Click P oint on the right.

2058 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Restore Points window, select a restore point to which you want to restore the workload.

2059 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Credentials and Region Settings
At the Account step of the wizard, specify AWS user credentials and region:

1. From the AW S account list, select credentials of a user account that will be used to connect to AWS. This
user account must have permissions listed in section AWS IAM User Permissions.

When you add AWS user credentials, Veeam Backup & Replication imports information about resources
associated with this user. During the restore process, Veeam Backup & Replication accesses these
resources and uses them to create a target instance in Amazon EC2.

If you have not set up credentials beforehand in the Cloud Credentials Manager, click the Ma nage
a ccounts link or click Ad d on the right to add the necessary credentials.

2. From the AW S region list, select the AWS region in which Veeam Backup & Replication will restore
workloads as Amazon EC2 instances.

3. From the Da tacenter region list, select the geographic region where Veeam Backup & Replication will
restore the workloads.

2060 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Name and Tags
At the Na me step of the wizard, you can specify names and manage AWS tags for the restored workloads. By
default, Veeam Backup & Replication uses the original workload names and adds the Orig inal name and Restore
sta rt time tags.

Specifying New Name


To define a new name for a workload that will be restored:

1. In the Ma chines to restore list, select a workload and click VM na me.

2. In the Cha nge Name window, enter a new name explicitly or specify a change name rule — add a prefix and
suffix to the original workload name.

Managing AWS Tags


You can use AWS tags to categorize instances in Amazon EC2. A tag is a label with metadata that includes two
properties: a key and a value. For more information on AWS tags, see the AWS Documentation.

You can modify or delete these tags, or add new ones.

NOTE

If you restore a workload from backups of an Amazon EC2 instance, Veeam Backup & Replication displays
tags that were assigned to this instance. You can modify or delete these tags as well.

2061 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Adding Tag
To add a new tag:

1. In the Ma chines to restore list, select a workload and click Ta g s.

2. In the Ta g s window, click Ad d .

3. In the E C2 VM Tag window, specify the Key and Va lue properties.

Note that you cannot add the tag with the Name key. Veeam Backup & Replication uses the Name tag to
set the name for the restored EC2 instance in Amazon EC2.

Modifying Tag
To modify a tag:

1. In the Ma chines to restore list, select a workload and click Ta g s.

2. In the Ta g s window, select the necessary tag and click E d it.

3. In the E C2 VM Tag window, edit the Key or Va lue properties.

Deleting Tag
To delete a tag:

1. In the Ma chines to restore list, select a workload and click Ta g s.

2. In the Ta g s window, select the necessary tag and click Remove.

2062 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Instance Type and Disks
At the Instance Type step of the wizard, you can configure the instance type for the restored workload, se lect
which disks to restore and change their type. By default, Veeam Backup & Replication restores all disks as
Amazon Elastic Block Store (EBS) volumes of the General Purpose SSD type. For information on types of EBS
volumes, see the AWS Documentation.

Selecting Instance Type


You can select the amount of computing resources that AWS will provision for your restored workload — an
Amazon EC2 instance type. Each instance type offers a unique combination of CPU, memory, storage, and
networking resources.

To select an instance type for a workload that will be restored:

1. In the Virtual machines list, select a workload and click E d it.

2. From the E C2 instance type list, select the instance type for the restored workload.

Make sure that you select the right instance type that corresponds to the initial workload configuration.
For information on instance types, see Amazon EC2 Instance Types.

If you restore an EC2 instance from backups created by Veeam Backup for AWS,
Veeam Backup & Replication will identify the type of a backed-up instance and select it by default.

3. From the OS license list, select the license policy that AWS will apply for software on the restored
workload:

o [For Linux workloads] The Bring Your Own License (BYOL) policy is used.

o [For Microsoft Windows workloads] Select one of the following license policies:

▪ P rovided by Amazon AWS . Select this option if you want to obtain licenses for Microsoft
software from AWS.

2063 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
▪ Bring Your Own License ( BYOL). Select this option if you want to use your existing licenses for
Microsoft software.

For more information on Microsoft software licensing in AWS, see Microsoft Licensing on AWS.

Selecting Workload Disks to Restore and Changing Their


Types
You can restore all disks or specific disks of a workload. You can also change disk types of the restored disks.

To select specific disks and change their type, do the following:

1. In the Virtual machines list, select a workload and click Disks.

2. In the Disks To Restore window, make sure that check boxes next to disks that you want to restore are
selected. Clear check boxes next to disks that you do not want to restore.

3. Select a disk whose type you want to change and click Disk type.

4. In the Select EC2 Disk Type window, choose the disk type.

If you selected the P rovisioned IOPS SSD (IO1) type, you can also specify the maximum number of
input/output operations per second (IOPS) for the volume. For more information on IOPS, see the AWS
Documentation.

TIP

For your convenience, Veeam Backup & Replication uses the AWS Simple Monthly Calculator tools to
estimate an approximate price per month for using a selected instance. The estimated price is calculated
based on the instance type, license policy and disk configuration.

2064 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2065 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Configure Network Settings
At the Network step of the wizard, you can select to which Amazon Virtual Private Cloud (Amazon VPC) the
restored workload must be connected. You can also specify a subnet, and a security group — a virtual firewall for
the restored EC2 instance. For more information on Amazon VPC, see the AWS Documentation.

To configure network settings for the restored workload, do the following:

1. From the Ama zon VPC list, select the Amazon VPC where the restored workload will be launched.

2. From the Sub net list, select the subnet for the restored workload.

3. From the Security group list, select a security group that will be associated with your restored workload.

4. From the P ub lic IP address list, select one of the following:

o Assign (restored VM will be accessible from the Internet) — if you want to assign a public IP to the
restored workload. For security reasons, make sure traffic filtration rules are properly configured in
the security group.

o Do not assign (more secure) — if you do not want to assign a public IP.

2066 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Secure Restore Settings
This step is available if you restore Microsoft Windows-based workloads.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o Ab ort VM recovery. Select this action if you want to cancel the restore session.

o P roceed with recovery but connect the VM to a different network . Select this action if you want to
restore the workload to a different AWS security group.

Click the Click to change link to select the security group.

6. Select the Continue scanning all remaining files after the first occurrence (Scan the entire image – for
version 12 (build 12.0.0.1420)) check box if you want to continue workload scan after the first malware is
found. For information on how to view results of the malware scan, see Viewing Malware Scan Results.

2067 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Configure Helper Appliance
At the Help er Appliance step of the wizard, you can specify helper appliance settings. A helper appliance is an
auxiliary Linux-based instance used to upload disks of a backed-up workload to Amazon EC2. For more
information on the helper appliance and requirements for it, see Helper Appliance.

To specify helper appliance settings, do the following:

1. Select the Use the helper appliance check box.

2. Click Customize.

3. From the E C2 instance type list, select the instance type for the helper appliance.

4. From the Sub net list, select the subnet for the helper appliance.

5. From the Security group list, select a security group that will be associated with the helper appliance.

6. In the Red irector port field, specify the port that Veeam Backup & Replication will use to route requests
between the helper appliance and backup infrastructure components.

2068 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for restoring the workload. The information you provide will be
saved in the session history in Veeam Backup & Replication, and you can view it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2069 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Verify Restore Settings
At the Summary step of the wizard, check the specified settings and click Finish. If you want to start the EC2
instance right after restore, select the P ower on VM after restoring check box.

After the wizard closes, you can track the restore process in the Restore Session window. If you need to cancel
the workload restore, click the Ca ncel restore task link.

2070 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore to Google Compute Engine
Veeam Backup & Replication allows you to restore different workloads (VMs, Google VM instances, physical
servers and so on) to Google Compute Engine as VM instances. A VM instance is a virtual machine in Google
Compute Engine with a preconfigured combination of computing resources.

You can use Veeam Backup & Replication to perform the following operations:

• Restore machines to Google Compute Engine from backups.

• Migrate machines from the on-premises infrastructure to the cloud.

• Create a test environment in the cloud for troubleshooting, testing patches and updates, and so on.

Supported Backup Types


You can restore machines from the backups of the following types:

• Backups of VMware vSphere or VMware Cloud Director VMs created by Veeam Backup & Replication.

• Backups of Microsoft Hyper-V VMs created by Veeam Backup & Replication.

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

Backups must be created at the entire machine level or volume level.

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

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

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

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

• Backups of RHV VMs created by Veeam Backup for RHV.

Helper Appliances
Helper appliance is an auxiliary Linux-based VM instance. It is used to upload backed-up data to Google
Compute Engine. Veeam Backup & Replication automatically deploys the helper appliance in Google Compute
Engine only for the duration of the restore process and removes it immediately after that.

Depending on the type of backups you are restoring from and their location, the helper appliance may be
required or optional. The helper appliance is required when you restore from:

• Backups of Google Compute Engine VM instances that are stored in external repositories.

• Backups of virtual and physical machines that are stored in object storage repositories.

The helper appliance is optional when you restore from backups of virtual and physical machines stored in
backup repositories, or backups of Google Compute Engine virtual machines copied to backup repositories with
backup copy jobs. It is recommended, however, to use the helper appliance in scenarios where it is optional, as
the helper appliance may significantly improve restore performance. You can specify the helper appliance
settings at the Helper Appliance step of the Restore to Google Compute Engine wizard.

2071 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Requirements for Helper Appliance
When configuring a helper appliance, consider the following:

• If you want to restore from backups in an on-premise object storage repository, the helper appliance
machine must have access to the source object storage repository. To provide access to object storage
repositories, you can use VPN or Google Dedicated Interconnect. For more information, see the Google
Cloud documentation.

• To upload one machine disk to Google Compute Engine, the helper appliance requires 1 GB RAM. Make
sure that the type of Google Compute Engine instance selected for the helper appliance offers enough
memory resources to upload all machine disks. Otherwise, the restore process may fail.

• The VPC route table must contain a route from the IP address of the Veeam Backup & Replication server to
an active Google Cloud internet gateway. For more information on internet gateways and how to create
route tables, see the Google Cloud documentation.

How Restore to Google Compute Engine Works


The workflow of the restore process depends on whether the helper appliance is used or not. For more
information on the helper appliance, see Helper Appliance.

NOTE

If you add the Google Compute Engine appliance to the Veeam Backup & Replication infrastructure and
plan to restore Google Compute Engine virtual machines from restore points that were created using the
appliance, you do not need to configure the helper appliance. Also, restore to Google Compute Engine
works as described in the Performing Instance Restore section in the Veeam Backup for Google Cloud User
Guide.

Restoring to Google Compute Engine with Helper Appliance


If the helper appliance is used for restore to Google Compute Engine, Veeam Backup & Replication performs the
following operations:

1. Veeam Backup & Replication creates a helper appliance in Google Compute Engine.

During the restore process, the helper appliance communicates with backup infrastructure components
over the SSH protocol and the network redirector that is deployed on the helper appliance.

2. For every disk of a backed-up workload, Veeam Backup & Replication creates a disk in Google Compute
Engine.

3. Veeam Backup & Replication hot-adds empty disks to the helper appliance and restores back ed-up data to
the disks.

4. Veeam Backup & Replication creates a target instance in Google Compute Engine.

5. Veeam Backup & Replication detaches the disks from the helper appliance and attaches them to the target
instance.

6. After the restore process is complete, Veeam Backup & Replication removes the helper appliance from
Google Compute Engine.

2072 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring to Google Compute Engine without Helper
Appliance
If the helper appliance is not used for restore to Google Compute Engine, Veeam Backup & Replication performs
the following operations:

1. Veeam Backup & Replication uploads disks of a backed-up workload to Google Cloud Storage bucket.

In Google Cloud Storage bucket, the uploaded disks are stored to the temporary bucket in the RAW
format.

2. Veeam Backup & Replication imports the backed-up data from the temporary bucket in Google Cloud
Storage to disks in Google Compute Engine.

3. Veeam Backup & Replication creates a target instance in Google Compute Engine and attaches disks to the
target instance.

4. After the import process is complete, Veeam Backup & Replication removes the temporary bucket from
Google Cloud Storage.

Google Compute Engine IAM User Permissions


To enable restore of workloads to Google Compute Engine, do the following:

1. Grant the following roles to the IAM user whose credentials you plan to use to connect to Google
Compute Engine:

o Compute Admin role (roles/compute.admin)

To avoid granting the Compute Admin role to the IAM user Compute Engine service account for
security reasons, you can create a custom role with the following Compute Engine IAM permissions
and grant it instead:

2073 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
compute.addresses.list
compute.disks.create
compute.disks.delete
compute.disks.get
compute.disks.use
compute.disks.useReadOnly
compute.firewalls.create
compute.firewalls.delete
compute.firewalls.list
compute.globalOperations.get
compute.images.create
compute.images.delete
compute.images.get
compute.images.useReadOnly
compute.instances.attachDisk
compute.instances.create
compute.instances.delete
compute.instances.detachDisk
compute.instances.get
compute.instances.getGuestAttributes
compute.instances.list
compute.instances.setLabels
compute.instances.setMetadata
compute.instances.setTags
compute.instances.stop
compute.machineTypes.list
compute.networks.get
compute.networks.list
compute.networks.updatePolicy
compute.projects.get
compute.regions.list
compute.subnetworks.get
compute.subnetworks.list
compute.subnetworks.use
compute.subnetworks.useExternalIp
compute.zoneOperations.get
compute.zones.get
compute.zones.list

o Cloud Build Editor role (roles/cloudbuild.builds.editor)

o Project IAM Admin role (roles/resourcemanager.projectIamAdmin)

o Storage Admin role (roles/storage.admin)

o Storage HMAC Key Admin (roles/storage.hmacKeyAdmin)

o Viewer role (roles/viewer)

For more information, see the Prerequisites for importing and exporting VM images section in the Google
Cloud documentation.

2. Make sure that the Cloud Build API is enabled. Then grant the following roles to the Cloud Build service
account in Google Compute Engine:

o Compute Admin role (roles/compute.admin)

To avoid granting the Compute Admin role to the Cloud Build service account for security reasons,
you can use the custom role that you created for the IAM user Compute Engine service account and
grant it instead.

2074 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o Service Account Token Creator role (roles/iam.serviceAccountTokenCreator)

o Service Account User role (roles/iam.serviceAccountUser)

o [Optional: to export or import images that use shared VPCs] Compute Network User role
(roles/compute.networkUser)

For more information, see the Prerequisites for importing and exporting VM images section in the Google
Cloud documentation.

Restoring to Google Compute Engine


To restore workloads to Google Compute Engine, use the Restore to Google Compute Engine wizard.

NOTE

If you add the Google Compute Engine appliance to the Veeam Backup & Replication infrastructure and
plan to restore Google Compute Engine virtual machines from restore points that were created using the
appliance, you do not need to configure the helper appliance. Also, restore to Google Compute Engine
works as described in the Performing Instance Restore section in the Veeam Backup for Google Cloud User
Guide.

Before You Begin


Before you restore workloads to Google Compute Engine, consider the following requirements and limitations:

• Check whether a helper appliance must be configured for restore. For more information, see Helper
Appliances.

• The backup server and repositories with workload backup files must have access to the internet.
If backup files are located on deduplicating storage appliances or shared folder repositories, the internet
connection is required for gateway servers that communicate with these repositories.

• If you use a cloud-init-based Linux distribution, we recommend that you use SSH keys on these
distributions. If you use a password, it is blocked after restore for security reasons. To reset the password
on the restored VM, use the technologies described in Google Cloud Documentation.

• You must have a backup of the workload that you plan to restore to Google Compute Engine.

• Make sure that the Cloud Build API is enabled. For more information on enabling the Cloud Build API and
other requirements for importing virtual disks into Google Compute Engine, see the Google Cloud
Documentation.

• Make sure the IAM service account that you plan to use to restore workloads to Google Compute Engine
has permissions to restore to Google Compute Engine. For more information, see Google Compute Engine
IAM User Permissions.

• If you restore workloads from backups of virtual and physical machines (non-Google Compute Engine
virtual machines), check the supported operating systems and their differences from standard images in
the Google Cloud documentation.

• Check that the logical sector size of disks that you plan to restore is less than 4096 bytes. Contents of
disks whose logical sector size is 4096 bytes will be unreadable in Google Compute Engine.

• If you plan to assign Google labels to the restored workload, check limitations for labels in the Google
Cloud documentation.

2075 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Restore to Google Compute Engine Wizard
To begin the restore process, do one of the following.

• On the Home tab, click Restore and select the type of backups from which you want to restore:

o VMware vSphere

o VMware Cloud Director

o Microsoft Hyper-V

o Agent

o AWS

o Azure IaaS backup

o GCE backup

o Nutanix AHV

o RHV Proxy

In the displayed window, click E ntire VM restore > Restore to public cloud > Restore to Google Compute
E ng ine.

• Open the Home view. In the inventory pane, click Ba ckups. In the working area, expand the necessary
backup, select workloads that you want to restore and click Restore to Google CE on the ribbon.
Alternatively, you can right-click one of the workloads that you want to restore and select Restore to
Goog le CE.

• Double-click a full backup file (VBK) or backup metadata file (VBM) in a file browser.
Veeam Backup & Replication will start its console. In the Ba ckup P roperties window, select the necessary
workload and click Restore > Restore to Google CE.

2076 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workloads and Restore Points
At the Virtual Machines step of the wizard, specify the workload that you plan to restore and specify a restore
point to which you want to restore the workload. By default, Veeam Backup & Replication restores workloads to
the latest valid restore point in the backup chain.

Selecting Workloads
To select workloads to restore:

1. On the right of the Virtual machines to restore list, click Ad d .

2. In the Ba ckup Browser window, expand the necessary backup, select workloads and click Ad d .

Selecting Restore Points


To select a restore point, for a workload do the following:

1. In the Virtual machines to restore list, select a workload.

2. Click P oint on the right.

2077 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. In the Restore Points window, select a restore point to which you want to restore the workload.

2078 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Specify Credentials and Datacenter Settings
At the Account step of the wizard, specify a Google Cloud Platform service account, datacenter and availability
zone to use for restore:

1. From the Google Cloud Platform service account list, select user credentials to connect to Google
Compute Engine.

When you add credentials of the Google Cloud Platform service account, Veeam Backup & Replication
imports information about resources associated with this service account. During the restore process,
Veeam Backup & Replication accesses these resources and uses them to create a target VM instance in
Google Compute Engine.

If you have not set up credentials beforehand in the Cloud Credentials Manager, click the Ma nage
a ccounts link or click Ad d on the right to add the necessary credentials, as described in section Google
Cloud Platform Service Accounts.

2. From the Da tacenter list, select the Google Cloud datacenter where Veeam Backup & Replication will
restore your workload as a VM instance.

3. From the Zone list, select the availability zone inside the Google Cloud datacenter where the restored
workload will reside.

If you restore a Google Compute Engine VM instance from a backup created by Veeam Backup for Google Cloud
to the same Google Cloud region where the instance is placed, after you click Nex t, the wizard will offer you to
use region settings associated with this instance.

2079 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Name and Labels
At the Na me step of the wizard, you can specify names and manage Google labels for the restored workloads.
By default, Veeam Backup & Replication uses original workload names.

Specifying New Name


To define a new name for a restored workload:

1. In the Instances list, select a workload and click VM Na me.

2. In the Set name to field of the Cha nge Name window, enter a new name for the restored workload.

Managing Google Cloud Labels


You can use Google Cloud labels to categorize instances in Google Compute Engine. A label is a tag with
metadata that includes two properties: a key and a value. For more information on Google Cloud labels their
format and limitations, see the Google Cloud documentation.

Adding Label
To add a new label:

1. In the Instances list, select a workload and click La b els.

2. In the La b els window, click Ad d .

3. In the GCE Instance Label window, specify the Key and Va lue properties.

2080 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Modifying Label
To modify a label:

1. In the Instances list, select a workload and click La b els.

2. In the La b els window, select the required label and click E d it.

3. In the GCE Instance Label window, edit the Key or Va lue properties.

Deleting Label
To delete a label:

1. In the Instances list, select a workload and click La b els.

2. In the La b els window, select the required label and click Remove.

2081 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Instance Type and Disks
At the Instance Type step of the wizard, select instance types and disk types for the restored workloads. By
default, Veeam Backup & Replication restores all disks as Google Compute Engine disks of the Balanced
persistent disk type. For information on types of Google Compute Engine disk s, see the Google Cloud
documentation.

Selecting Instance Type


You can select the amount of computing resources that Google Compute Engine will provision for your restored
workload — a Google Compute Engine instance type. Each instance type offers a unique combination of CPU and
memory resources.

To select an instance type for a workload:

1. In the Instances list, select a workload and click E d it.

2. From the Ma chine type list, select the instance type for the restored workload.

Make sure that you select the right instance type that corresponds to the initial workload configuration.
For the information on instance types, see Google Cloud Documentation.

Note that if you restore a Google Compute Engine instance from the backup created by Veeam Backup for
Google Cloud, Veeam Backup & Replication will identify the type of a backed-up instance and select it by
default.

3. From the OS license list, select an option that will define what license Google Compute Engine will use for
the OS on the restored workload:

o P rovided by GCE — the OS license will be provided by Google Compute Engine.

o Bring Your Own License ( BYOL) — the OS license will be restored from the backup. For more
information, see Google Cloud documentation.

2082 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Selecting Disk Type
You can restore all disks or specific disks of a workload. You can also change disk types of the restored disks.

To select workload disks for restore:

1. In the Virtual machines list, select a workload and click Disks.

2. In the Disks To Restore window, make sure that check boxes next to disks that you want to restore are
selected. Clear check boxes next to disks that you do not want to restore.

3. Select a disk whose type you want to change and click Disk type.

4. In the Select EC2 Disk Type window, choose the disk type.

2083 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Select Google VPC
At the Network step of the wizard, you can select to which Google Virtual Private Cloud (Google VPC) network
the workload must be connected after restore. You can also specify a subnet. For the information on Google
VPC, see the Google Cloud documentation.

To define network settings for the restored workload, do the following:

1. From the VP C list, select the VPC where the restored workload will be launched.

2. From the Sub net list, select an IP address range for the selected VPC.

3. From the P ub lic IP address list, select one of the following:

o Assign (restored VM will be accessible from the Internet) — if you want to assign a public IP to the
restored workload. For security reasons, make sure firewall rules are properly configured in the target
VPC.

o Do not assign (more secure) — if you do not want to assign a public IP.

2084 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Secure Restore Settings
This step is available if you restore Microsoft Windows workloa ds.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Select which action Veeam Backup & Replication will take if scan finds a virus threat:

o Ab ort VM recovery. Select this action if you want to cancel the restore session.

o P roceed with recovery but connect the VM to a different network . Select this action if you want to
restore the workload to a different Google Cloud network.

Click the Click to change link to specify the VPC and subnet for this network.

2085 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
6. Select the Continue scanning all remaining files after the first occurrence (Scan the entire image – for
version 12 (build 12.0.0.1420)) check box if you want to continue workload scan after the first malware is
found. For information on how to view results of the malware scan, see Viewing Malware Scan Results.

2086 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Configure Helper Appliance
At the Help er Appliance Settings step of the wizard, you can specify helper appliance settings. A helper
appliance is an auxiliary Linux-based instance used to upload disks of a backed-up workload to Google Compute
Engine. For more information on the helper appliance and requirements for it, see Helper Appliances.

To specify helper appliance settings, do the following:

1. Select the Use the helper appliance check box.

2. Click Customize.

3. From the Ma chine type list, select the instance type for the helper appliance.

4. From the VP C list, select the VPC network for the helper appliance.

5. From the Sub net list, select the subnet for the helper appliance.

6. In the Red irector port field, specify the port that Veeam Backup & Replication will use to route requests
between the helper appliance and backup infrastructure components.

2087 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 9. Specify Restore Reason
At the Rea son step of the wizard, enter a reason for restoring the workload. The information y ou provide will be
saved in the session history in Veeam Backup & Replication, and you can view it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2088 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 10. Verify Restore Settings
At the Rea dy to Restore step of the wizard, check the specified settings and click Finish. If you want to start the
VM instance right after restore, select the P ower on VM after restoring check box.

You can track the restore process in the Restore Session window. If you need to cancel the workload restore,
click the Ca ncel restore task link.

2089 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disk Recovery
Disk recovery includes the following methods:

• Disk export — to convert disks of different workloads (EC2 instances, Microsoft Azure VMs and so on) in
the VMDK, VHD or VHDX formats. Then you can export these disks to the backup infrastructure or place
them on a datastore connected to an ESXi host (for VMDK disk format only).

Use disk export to convert disks to the VMDK, VHD or VHDX formats.

• Disk publishing — to get the backup content without restoring all disks from a backup. After you publish a
disk, you can browse its content, perform antivirus scan and other testing.

2090 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Disk Export
Veeam Backup & Replication allows you to export disks, that is, restore disks from backups of physical or virtual
machines and convert them to the VMDK, VHD or VHDX formats.

During disk export, Veeam Backup & Replication creates the following files that can be used b y VMware vSphere
and Microsoft Hyper-V VMs:

• When you export a disk in the VMDK format, Veeam Backup & Replication creates a pair of files that make
up the VM virtual disk: a descriptor file and file with the virtual disk content.

• When you export a disk in the VHD/VHDX format, Veeam Backup & Replication creates a file of the VHD or
VHDX format.

You can save the exported disks to any server added to the backup infrastructure or place disks on a datastore
connected to a host.

Veeam Backup & Replication supports batch disk export. For example, if you choose to export 2 disks,
Veeam Backup & Replication will convert them to 2 virtual disks and store these disks in the specified location.

Supported Backup Types


You can restore disks from the following backups:

• Backups of VMware vSphere virtual machines created by Veeam Backup & Replication

• Backups of VMware Cloud Director virtual machines created by Veeam Backup & Replication

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

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

• Backups of EC2 instances created by Veeam Backup for AWS

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

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

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

• Backups of RHV VMs created by Veeam Backup for RHV

• Backups exported by K10 policies

Exporting Disks
You can export disks of different workloads from backups and convert disks to the VMDK, VHD or VHDX format.
For the list of backups that you can use for export, see Supported Backup Types.

To export disks, use the E x port Disk wizard.

2091 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Export Disk Wizard
To launch the E x port Disk wizard, do one of the following:

• On the Home tab, click Restore and select one of the following:

o VMwa re vSphere > Restore from backup > Disk Restore > E xport disk — to export disks of VMware
vSphere VMs from a VM backup created by Veeam Backup & Replication.

o VMwa re Cloud Director > Restore from backup > VM restore > Disk Restore > E xport disk — to export
disks of VMware Cloud Director VMs from a VM backup created by Veeam Backup & Replication.

o Microsoft Hyper-V > Restore from backup > E ntire VM restore > E xport disk — to export disks of
Hyper-V VMs from a VM backup created by Veeam Backup & Replication.

o Ag ent > Disk Restore > E x port disk — to export disks of physical machines and virtual machines from
backups created by Veeam Agent for Microsoft Windows, Veeam Agent for Linux or Veeam Agent for
Mac.

o AW S > Ama zon EC2 > E ntire machine restore > E x port disk — to export disks of EC2 instances from
backups created by Veeam Backup for AWS.

o Azure IaaS backup> E ntire machine restore > E xport disk — to export disks of Azure VMs from backups
created by Veeam Backup for Microsoft Azure.

o GCE backup > E ntire machine restore > E xport disk — to export disks of VM instances from backups
created by Veeam Backup for Google Cloud.

o Nuta nix backup > E ntire machine restore > E x port disk — to export disks of VMs from backups created
by Veeam Backup for Nutanix AHV.

o RHV P roxy > E ntire machine restore > E x port d isk — to export disks of VMs from backups created by
Veeam Backup for RHV.

o K10 b ackup > E x port d isk — to export disks of VMs whose backups were exported by K10 policies.

2092 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane, click Ba ckups. In the working area, expand the necessary
backup, select a workload whose disks you want to export and click E x p ort Disks on the ribbon.
Alternatively, you can right-click the workload and select E x port content as virtual disks.

2093 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Backup
At the Ba ckup step of the wizard, expand a backup and select the workload whose disks you want to export.

2094 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
At the Restore P oint step of the wizard, select the restore point from which you want to restore disks. By
default, Veeam Backup & Replication restores disks to the latest state. However, you can restore disks to an
earlier state.

2095 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Disks
At the Disks step of the wizard, select check boxes next to the disks that you want to export.

2096 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Select Destination and Disk Format
At the Ta rget step of the wizard, select the destination for disk export and format in which you want to save the
resulting virtual disks:

1. From the Server list, select a server on which the resulting virtual disks must be saved. If you plan to save
the disks to a datastore, select a host to which this datastore is connected.

NOTE

Consider the following:

• If you select to export the resulting virtual disk to an ESXi datastore, you can save the virtual
disk in the VMDK format only. Other options are disabled.
• If you export disks as VMDK to a vSAN datastore, disk are exported according to the storage
policy set on the datastore.
• If you export disks as VMDK to a place other than an ESXi datastore, disks are exported as
thick provision lazy zeroed.

2. In the P a th to folder field, specify a datastore or folder on the server where the virtual disks must be
placed.

3. Select the export format for the disks:

o VMDK — select this option if you want to save the resulting virtual disk in the VMware VMDK format.
This is the only available option if you export disks to an ESXi datastore.

o VHD — select this option if you want to save the resulting virtual disk in the Microsoft Hyper -V VHD
format.

o VHDX — select this option if you want to save the resulting virtual disk in the Microsoft Hyper -V
VHDX format (supported by Microsoft Windows Server 2012 or later).

4. [For disks exported as VMDK to an ESXi datastore] Click the P ick proxy to use link to select backup proxies
over which disk data must be transported to the target datastore. You can assign backup proxies explicitly
or instruct Veeam Backup & Replication to automatically select backup proxies.

2097 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. From the Disk Type drop-down list, select a disk type for the exported disks.

2098 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Secure Restore Settings
This step is available if you export disks of Microsoft Windows workloads.

You can instruct Veeam Backup & Replication to scan machine data with antivirus software and YARA rules
before restoring the machine to the production environment.

To specify secure restore settings:

1. To use antivirus software as a scan engine, select the Sca n the restore point with an antivirus engine check
box. For more information on antivirus scan, see Antivirus Scan (Secure Restore).

2. [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] To use a YARA rule as a scan
engine, select the Sca n the restore point with the following YARA rule check box and choose a YARA rule
from the drop-down list.

For a YARA rule to appear in the drop-down list, it must be placed in the YaraRules folder in the
Veeam Backup & Replication product folder. For more information, see YARA Scan for Scan Backup.

TIP

To copy the path to the folder with YARA rules, click Cop y YARA rules location to clipboard.

5. Specify how Veeam Backup & Replication must behave after the first malware threat is found: continue or
abort disk recovery.

6. Select the Continue scanning all remaining files after the first occurrence (Scan the entire image – for
version 12 (build 12.0.0.1420)) check box if you want to continue the disk scan after the first virus threat is
detected. For information on how to view results of the malware scan, see Viewing Malware Scan Results.

2099 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Specify Export Reason
At the Rea son step of the wizard, enter a reason for disk export.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2100 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finish Working with Wizard
At the Summary step of the wizard, review the configured settings and click Finish.

2101 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Disk Publishing (Data Integration API)
NOTE

Publishing disks from UI is available starting from Veeam Backup & Replication version 12.1 (build
12.1.0.2131).

Disk publishing allows you to save time by getting backup content of one or multiple disks instead of all disks
from a backup. This technology gives read-only access to data and helps if you want to analyze data of your
backup. For example, look for specific documents or usage patterns, or perform antivirus scan of backe d-up
data.

You can publish a disk from different types of backups. The disk can have a Microsoft Windows file system or
Linux, Unix or other file system. For the full list of supported file systems, see Platform Support. To present the
backed-up disk to the target server, disk publishing uses the iSCSI protocol for Windows file systems or the
FUSE protocol for other OSes. After the publishing, the target server can access the backup content using the
iSCSI initiator or FUSE protocol, and read the necessary data from the disk.

Supported Backup Types


You can publish disks from the following types of backups:

• Backups of VMware vSphere virtual machines created by Veeam Backup & Replication

• Backups of Microsoft Hyper-V virtual machines created by Veeam Backup & Replication

• Backups of VMware Cloud Director virtual machines created by Veeam Backup & Replication

• Backups of RHV VMs created by Veeam Backup for RHV

• Backups of machines running Microsoft Windows created by Veeam Agent for Microsoft Windows

• Backups of machines running Linux created by Veeam Agent for Linux

• Backups of machines running Oracle Solaris created by Veeam Agent for Oracle Solaris

• Backups of machines running IBM AIX created by Veeam Agent for IBM AIX

• Backups of machines running macOS created by Veeam Agent for Mac

• Backups of Nutanix AHV virtual machines created by Veeam Backup for Nutanix AHV

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

• Backups of Microsoft Azure virtual machines created by Veeam Backup for Microsoft Azure

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

• Backups exported by K10 policies

NOTE

You cannot publish disks from replicas using UI. To do that, use the Publish-VBRBackupContent cmdlet.

2102 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Considerations and Limitations
Disk publishing has the following requirements and limitations:

• The necessary ports must be opened on the target server. For more information, see Ports.

• The file system of a workload whose disks you plan to restore must be supported. For details, see the File-
Level Restore.

• To restore disks that have file system other than Microsoft Windows, you can use only a Linux -based
server as the target server.

• The 32-bit version of a Linux-based server is not supported as the target server.

• The target server must support the file system of the disk that you plan to publish.

• A servers on which a hardened repository is configured cannot be used as the target server.

• Disk publishing is not available for Linux, Unix, macOS (and other) workload backups stored on Veeam
Cloud Connect Repositories. For more information on Veeam Cloud Connect repositories, see the Cloud
Repository section in the Veeam Cloud Connect Guide.

• Basic disks, Linux LVM (Logical Volume Manager) and ZFS pools can be published. Encrypted, RAID1 and
mirrored LVM volumes are not supported.

• RAID disks publish for Linux workloads is not supported.

• The target server must support the same ReFS version or later than the version used on the workload from
which you plan to restore files. For more information on which OSes support which ReFS, see ReFS
versions and compatibility matrix.

• If data deduplication is enabled for some disks in a backup, data deduplication must be enabled on the
target server.

• You cannot publish disks from a backup created in the reverse incremental mode if the backup job is being
performed. If the backup is created in the incremental backup mode and the backup job is being
performed, you can publish disks from any available restore point.

• You can publish disks from Novell Storage Services (NSS) file system. The target host must differ from the
backed-up workload.

• Mounting of LVM snapshots is not supported. LVM snapshots are skipped from processing.

• You can publish disks with ZFS FS if the zfsutils-linux package is installed on the specified target
host. The zfs-fuse package is not supported.

• If you want to publish a Btrfs disk and select the original server as the target server, the mount of the
Btrfs disk will fail. The issue occurs due to restriction of mounting two Btrfs disks with identical IDs to the
same machine. To avoid this issue, use another target server. However, note that Btrfs disks can be
restored for backups created by Veeam Agent for Linux. During the backup process, Veeam Agent for
Linux changes disk IDs in the backup file.

How Publishing Works for Microsoft Windows File Systems


After you start the publishing session for disks with Microsoft Windows file system, the following applies:

1. Veeam Backup & Replication connects to the backup repository where the backup locates and to the
mount server associated with this repository.

2103 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2. Veeam Backup & Replication starts the following agents and services in the infrastructure:

o The repository agent. This agent runs on the backup repository or on the gateway server associated
with this repository.

o The mount agent. This agent runs on the mount server. The agent configures the iSCSI Target Server
on the mount server and triggers the repository agent to read the backup data.

o Veeam Installer Service. This service is installed and runs on the target server and remains on it after
the publishing finishes.

3. Veeam Backup & Replication accesses the target server and configures the iSCSI initiator on this server.

4. After Veeam Backup & Replication adds the target server to the iSCSI Target Server settings, the target
server can access disk content. The disk content is available in the C:\VeeamFLR\ folder on the target
server. Note that disk data is read-only.

After that, you can browse the disks and perform data analysis operations with them. The published disks are
available while the mount server is up and running. Even if you turn off the backup server, you will be able to
access the published disks.

After you finish working with the disks, you should stop publishing them as described in Managing Published
Disks.

How Publishing Works for Linux, Unix and Other File Systems
After you start the publishing session for disks with Linux, Unix or other file syste m, the following applies:

1. Veeam Backup & Replication connects to the backup repository where the backup locates and to the
mount server associated with this repository.

2. Veeam Backup & Replication starts the following agents in the infrastructure:

o The repository agent. This agent runs on the backup repository or on the gateway server associated
with this repository.

o A temporary agent. This agent runs on the target server and is removed after the publishing session
finishes.

3. Veeam Backup & Replication uses the FUSE protocol to publish the content of the backup automatically.

The published disk images are available in the /tmp/Veeam.Mount.Disks location. The disk content is
available in the /tmp/Veeam.Mount.FS location. Note that disk data is read-only.

After that, you can browse the disks and perform data analysis operations with them.

After you finish working with the disks, you should stop mounting them as described in Managing Published
Disks.

Mount Modes
When you publish disks with Microsoft Windows file system from the UI, Veeam Backup & Replication
automatically configures the iSCSI session and gives the target server (iSCSI initiator) access to the published
disks. To manually start the iSCSI session from any server that has access to the iSCSI Target Server, you can use
the Publish-VBRBackupContent cmdlet.

2104 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Publishing Disks
To publish a disk, use the P ub lish Disks wizard.

2105 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Wizard
To launch the P ub lish Disks wizard, do one of the following:

• On the Home tab, click Restore and select one of the following:

o VMwa re vSphere > Restore from backup > Disk Restore > P ublish disk — to publish a disk of a VMware
vSphere VM from a backup created by Veeam Backup & Replication.

o VMwa re Cloud Director > Restore from backup > VM restore > Disk Restore > P ublish disk — to publish
a disk of a VMware Cloud Director VM from a backup created by Veeam Backup & Replication.

o Microsoft Hyper-V > Restore from backup > E ntire VM restore > P ublish disk — to publish a disk of a
Hyper-V VM from a backup created by Veeam Backup & Replication.

o Ag ent > Disk Restore > P ub lish d isk — to publish a disk of a physical machine or a virtual machine from
a backup created by Veeam Agents.

o AW S > Ama zon EC2 > E ntire machine restore > P ub lish d isk — to publish a disk of an EC2 instance
from a backup created by Veeam Backup for AWS.

o Azure IaaS backup> E ntire machine restore > P ublish disk — to publish a disk of an Azure VM from a
backup created by Veeam Backup for Microsoft Azure.

o GCE backup > E ntire machine restore > P ublish disk — to publish a disk of a VM instance from a backup
created by Veeam Backup for Google Cloud.

o Nuta nix backup > E ntire machine restore > P ub lish d isk — to publish a disk of a VM from a backup
created by Veeam Backup for Nutanix AHV.

o RHV P roxy > E ntire machine restore > P ub lish disk — to publish disks of VMs from backups created by
Veeam Backup for RHV.

o K10 b ackup > P ub lish disk — to publish disks of VMs whose backups were exported by K10 policies.

2106 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the Home view. In the inventory pane, click Ba ckups. In the working area, expand the necessary
backup, select a workload whose disks you want to publish and click P ub lish Disks on the ribbon.
Alternatively, you can right-click the workload and select P ub lish disks.

2107 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select Workload
At the Ma chine step of the wizard, expand a backup and select a workload whose disks you want to publish.

2108 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
At the Restore P oint step of the wizard, select a restore point from which you want to publish disks.

2109 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select Disks
At the Disks step of the wizard, select a check box next to the disks that you want to publish.

2110 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Target Server
At the Ta rget step of the wizard, select a server that will have access to disk content — for Microsoft Windows
file system a Microsoft Windows server; for Linux, Unix or other file system a Linux -based server. You can select
one of the following types of servers:

• A server added to the backup infrastructure.

• A temporary server. In this case, select Specify a different host from the drop-down list. In the Ta rget
Server window, specify a server name or IP and credentials to the server.

• The original server if you publish disks from a backup created by Veeam Agent for Microsoft Windows or
Veeam Agent for Linux. In this case, select Original server from the drop-down list.

If prompted, specify credentials for the target server.

2111 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Reason
At the Rea son step of the wizard, enter a reason for publishing disks.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2112 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Finish Working with Wizard
At the Summary step of the wizard, review the configured settings and click Finish.

What You Do Next


Depending on the file system of the disk, go to the following locations on the target server to browse disk
content:

• [Microsoft Windows file systems] Go to C:\VeeamFLR\ folder.

• [Linux, Unix and other file systems] Go to the /tmp/Veeam.Mount.Disks location to browse disk
images. Go to the /tmp/Veeam.Mount.FS location to browse disk content.

Managing Published Disks


After you started a publishing session, you can check details on this session or stop it.

Viewing Statistics on Publishing Session


To view publishing session statistics, do one of the following:

• Open the Home view. In the inventory pane, select Instant Recovery. In the working area, select the
necessary publishing session and click P roperties on the ribbon. Alternatively, right-click the session and
P roperties.

• Open the Home view. In the inventory pane select La st 24 hours. In the working area, double-click the
necessary publishing session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

2113 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the History view. In the inventory pane select Restore. In the working area, double-click the
necessary mount session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

The publishing statistics provides the following data:

• At the top of the Restore Session window, Veeam Backup & Replication shows general session statistics. It
includes a name of the workload whose disk you want to publish, a name of the backup server which
initiated the publishing session, a user name of the account under which the session was started, session
status, and duration details.

• The Rea son tab shows the reason for the publishing session.

• The P a rameters tab shows information about the target server, the machine whose disks you publish and
the restore point selected for publishing.

• The Log tab shows the list of operations performed during the session.

Stopping Publishing Session


To stop a publishing session, do one of the following:

• Open the Home view. In the inventory pane select Instant Recovery. In the working area, select the
necessary publishing session and click Stop P ublishing on the ribbon. Alternatively, right-click the session
and Stop Publishing.

• Open the Home view. In the inventory pane select La st 24 hours. In the working area, select the necessary
publishing session and click Stop Publishing on the ribbon. Alternatively, right-click the session and Stop
P ub lishing.

2114 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
• Open the History view. In the inventory pane select Restore. In the working area, select the necessary
publishing session, double-click it. In the Restore Session window, click Ca ncel restore task.

2115 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Item Recovery
Item recovery includes the following methods:

• VM files restore — to restore VM files (.XML, .VMCX and so on) without restoring the entire VM.

• Guest OS file restore — to restore individual guest OS files from Windows, Linux, Mac and other guest OS
file systems. You can restore files and folders directly from a regular image -level backup or replica.

• Application items restore — to restore items from different applications such as Microsoft Active Directory,
Microsoft SQL Server and so on. Application items are recovered directly from VM backups and replicas. To
recover application items, Veeam Backup & Replication uses the capabilities of Veeam Backup Explorers.

2116 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
VM Files Restore
You can restore specific VM files (.XML, .VMCX, .VMRS, .VMGS, .VHD, .VHDX) if any of these files are deleted or
the volume is corrupted. This option provides a great alternative to entire VM restore, for example, when your
VM configuration file is missing and you need to restore it. Instead of restoring the whole VM image to the
production storage, you can restore a specific VM file only.

When you perform VM file restore, VM files are restored directly from regular image-level backups, without
prior de-staging of VM images from backups. VM files can be restored to the original VM location or to a new
location. The restored .VHD and .VHDX disk files preserve the original disk types (fixed or dynamic).

NOTE

If you recover a .VMCX file and further import a VM from it to Microsoft Hyper -V, the VM will be registered
under the Veeam Recovery Checkpoint-(<GUID>) name. After import, you can rename the VM if required.

Restoring VM Files
To restore VM files from a backup, use the Hy p er-V Restore wizard.

Before You Begin


Before you restore VM files, check the following prerequisites:

• You can restore VM files from a backup that has at least one successfully created restore point.

• The server on which you plan to save restored VM files must be added to the backup infrastructure.

2117 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Hyper-V Restore Wizard
To launch the Restore wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from backup > E ntire VM restore > VM files
restore (VSV, BIN, XML).

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup, click the VM whose files you want to restore and click VM Files on the ribbon. Alternatively, you
can right-click the VM whose files you want to restore and select Restore VM files.

In this case, you will pass to the Restore Point step of the wizard.

• Double-click the VBK or VBM file (for example, in Microsoft Windows Explorer). In the displayed window,
select the VM and click Restore > VM files. In this case, you will pass to the Restore Point step of the
wizard.

You can use this option if you perform restore on the backup server. You cannot use this option if you
perform restore remotely over the Veeam Backup & Replication console.

2118 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VM
At the Virtual Machine step of the wizard, select the VM whose files you want to restore:

1. In the Virtual machine list, expand the necessary backup.

2. Select the VM.

2119 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point
At the Restore P oint step of the wizard, select the restore point from which you want to restore the VM files.

2120 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Select VM Files and Destination
At the Restore Destination step of the wizard, select the VM files you want to restore and destination where the
restored files must be stored.

1. From the Server list, select where to store VM files: on a Microsoft Hyper-V host, on the backup server or
on a Microsoft Windows or Linux server added to the backup infrastructure. Use the Details button to view
or change connection settings of the target host or server.

2. In the P a th to folder section, specify a path to the folder on the selected host where files must be
restored.

To create a new folder for restored files, click Browse. In the Select Folder window, select the target
location for VM files and click New Folder at the bottom of the window.

3. In the VM files to restore section, select check boxes next to files that you want to restore.

2121 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Restore Reason
At the Restore Reason step of the wizard, enter a reason for restoring VM files. The information you provide will
be saved in the session history and you can reference it later.

2122 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finish Working with Wizard
At the Summary step of the wizard, check details for the restore task and click Finish to start VM files restore.

2123 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Guest OS File Restore
With guest OS file restore, you can recover individual guest OS files and folders from backups (Microsoft
Windows and other file systems), replicas (Microsoft Windows file systems), Nutanix AHV snapshots and so on.
When restoring files or folders, you do not need to extract the VM image to a staging location or star t the VM
prior to restore. You can restore files and folders directly from a regular image -level backup or replica to the
necessary point in time.

Using the following methods, you can restore files from different guest OS file systems:

• Restore from Microsoft Windows File Systems (FAT, NTFS or ReFS)


This method helps you restore files from Microsoft Windows VMs with NTFS, FAT and ReFS file systems.

• Restore from Linux, Unix and Other File Systems (multi-OS guest OS file restore)

This method helps you restore files from Linux, Solaris, BSD, Unix and Mac machines.

Note that this method supports recovery of files and folders only. Recovery of other file system objects
such as pipes is not supported.

• Restore from Other File Systems

This method helps you restore files from file systems that other methods from the list do not support.

Restore from Microsoft Windows File Systems (FAT, NTFS or


ReFS)
The restore from FAT, NTFS and ReFS method helps you restore files from backups or replicas of Microsoft
Windows workloads with NTFS, FAT and ReFS file systems. For the full list of supported file systems, see
Platform Support.

You can restore files to the original or new location, restore changes and permissions, work with the restored
files using Microsoft Windows File Explorer or launch application item restore for the files. For more
information, see Finalize Restore.

How Restore Works


During the guest OS file restore, Veeam Backup & Replication performs the following operations:

1. Veeam Backup & Replication creates a mount point under the C:\VeeamFLR\<vmname> folder and
mounts VM disks from the backup or replica to it. For more information on which machines
Veeam Backup & Replication creates mount points, see Restore Scenarios and Mount Points.

If a workload has ReFS disks, Veeam Backup & Replication uses virtual hard disk (VHD) mount to access
the content of all disks. If a workloads does not have ReFS disks, Veeam Backup & Replication uses a
separate program — Virtual Disk Driver (VDK) that is provided with the product. Workload disks are not
physically extracted from the backup file or workload replica. Veeam Backup & Replication emulates their
presence on the backup server or Veeam Backup & Replication console. The backup file or workload
replica itself remains in the read-only state.

2. Veeam Backup & Replication launches the Veeam Backup browser on the Veeam Backup & Replication
console. The Veeam Backup browser shows the content of disks mounted to the machine where the
mount point is created.

You can browse the VM guest file system in the Veeam Backup browser and r estore files or folders to the
original or new location.

2124 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. Depending on which restore command you use, the operations differ:

o If you restore to the original location, select the Restore > Keep or Restore > Overwrite command.

The machine where the mount point is created connects to the workload over network or PowerShell
Direct if a connection over the network cannot be established.

o If you restore permissions, select the Restore > P ermissions only command.

The machine where the mount point is created connects to the workload over network.

o If you restore files to a new workload, select the Restore to > Keep or Restore to > Overwrite
command.

The machine where the mount point is created connects to the workload over network or PowerShell
Direct if a connection over the network cannot be established.

o If you restore files to the Veeam Backup & Replication console or a shared folder, select the Cop y to
command.

The machine where the mount point is created connects to the Veeam Backup & Replication console
over network. If you recover files to a shared folder, the Veeam Backup & Replication console also
connects to this folder over network.

o If you restore changes, select the Restore changed only command.

During the comparison, Veeam Backup & Replication connects to the original workload over network
and installs Veeam Installer Service. If the service is already installed on the workload,
Veeam Backup & Replication upgrades it to the required version. Note that after the comparison or
restore is finished, the service is still installed on the workload.

When restore is launched, the machine where the mount point is created connects to the workload
over network.

PowerShell Direct is used for VMs that reside on Microsoft Hyper-V Server 2016 (or later) and run
Microsoft Windows 10 (or later) or Microsoft Windows Server 2016 (or later). Veeam Backup & Replication
requires Microsoft PowerShell 2.0 (or later) to work over PowerShell Direct.

4. When the restore process is finished or the Veeam Backup browser is closed by timeout,
Veeam Backup & Replication removes all the created mount points.

2125 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When you perform guest OS file restore, you can also open files in Microsoft Windows explorer to view file
content. In this case, Veeam Backup & Replication creates an additional mount point on the
Veeam Backup & Replication console. For more information on how to view file content, see Working with
Microsoft Windows File Explorer.

Mount Points and Restore Scenarios


Veeam Backup & Replication creates mount points on different machines depending on a restore scenario you
use.

Restoring Files from Backups


When you restore files from backups that reside in the backup repository, Veeam Backup & Replication creates a
mount point on the following machines:

• Mount server associated with the backup repository on which the backup file resides.
Veeam Backup & Replication uses this mount point when the restore process starts and allows you to
browse the VM file system and restore files.

• Veeam Backup & Replication console. Veeam Backup & Replication uses this mount point only for the
mount to console functionality, that is, while you use Microsoft Windows File Explorer to view files and
folders of the backed-up VM. For more information, see Open Files in Microsoft Windows Explorer.

2126 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Backup files on HPE StoreOnce are locked exclusively by a restore task. For this reason,
Veeam Backup & Replication uses only one mount point on the backup server or
Veeam Backup & Replication console machine for backups on HPE StoreOnce.

Restoring Files from Replicas


When you restore files from a VM or CDP replica, Veeam Backup & Replication creates a mount point on the
following machines:

• Backup server. Veeam Backup & Replication uses this mount point while the restore process and allows
you to browse the VM file system and restore files.

• Veeam Backup & Replication console. Veeam Backup & Replication uses this mount point only for the
mount to console functionality, that is, while you use Microsoft Windows File Explorer to view files and
folders of the VM replica. For more information, see Open Files in Microsoft Windows Explorer. If you also
restore files to the console or a shared folder (use the Cop y to command) while the mount to console
functionality is enabled, Veeam Backup & Replication uses the same mount point for restore. If you launch
other restores, Veeam Backup & Replication uses the backup server as a mount point.

Restoring Files for Veeam Explorers


If you have launched guest OS file restore and then launch application items restore from the Veeam Backup
browser, Veeam Backup & Replication uses additional restore points apart from the the mount points described
in the subsections above:

• If you restore Microsoft Active Directory or Microsoft Exchange items, Veeam Backup & Replication
creates an additional mount point on the Veeam Backup & Replication console. However, if during guest
OS file restore the mount point was already created on a machine where the Veeam Backup & Replication
console is installed, an additional point is not created.

• If you restore Microsoft SharePoint items, Veeam Backup & Replication creates an additional mount point
on a staging Microsoft SQL Server.

• If you restore Microsoft SQL Server items, Veeam Backup & Replication creates two additional mount
points: one on a staging Microsoft SQL Server and the other one on the target VM to which you restore the
application items.

• If you restore Oracle server items, Veeam Backup & Replication creates two additional mount points: one
on a staging Oracle server and the other one on the target VM to which you restore the application items.

2127 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• If you restore PostgreSQL server items, Veeam Backup & Replication creates two additional mount points:
one on a staging PostgreSQL server and the other one on the target VM to which you restore the
application items.

To create mount points on Linux and Windows machines, Veeam Backup & Replication uses different methods:

• To create a mount point on Microsoft Windows machines, Veeam Backup & Replication uses the iSCSI
protocol. The remote machine or staging server acts as an iSCSI initiator. The machine on which the Veeam
Explorer runs acts as an iSCSI target. The iSCSI mount point is non-persistent — it is created only for
duration of the restore process.

• To create a mount point on Linux VMs (for Oracle and PostgreSQL running on Linux),
Veeam Backup & Replication uses FUSE.

Restoring Files from Veeam Backup Enterprise Manager


When you restore files from Veeam Backup Enterprise Manager, Veeam Backup & Replication creates a mount
point on the mount server associated with the backup repository on which the backup file resides.
Veeam Backup & Replication uses this mount point when the restore process starts and allows you to browse
the VM file system and then restore files.

Restoring Files from Nutanix AHV Snapshots


To learn how Veeam Backup & Replication performs guest OS file restore from backup snapshots, user
snapshots and persistent disk snapshots created by AHV Backup Proxy and which mount points are used, see the
Performing File-Level Restore section of the Veeam Backup for Nutanix AHV User Guide.

Restoring Files from Amazon EC2 Instances


To perform guest OS file restore for EC2 instances, Veeam Backup & Replication utilizes the functionality of
AWS Plug-in for Veeam Backup & Replication. To learn more how restore is performed, see the Performing File-
Level Restore section of the Veeam Backup for AWS User Guide.

2128 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Files from Microsoft Azure VMs
To perform guest OS file restore for Microsoft Azure VMs, Veeam Backup & Replication utilizes the functionality
of Microsoft Azure Plug-in for Veeam Backup & Replication. To learn how restore is performed, see the
Performing File-Level Recovery section of the Veeam Backup for Microsoft Azure User Guide.

Restoring Files from Google Cloud VMs


To perform guest OS file restore for Google Cloud VMs, Veeam Backup & Replication utilizes the functionality of
Google Cloud Plug-in for Veeam Backup & Replication. To learn how restore is performed, see the Performing
File-Level Recovery section of the Veeam Backup for Google Cloud User Guide.

Considerations and Limitations


Before you restore VM guest OS files, check the following considerations and limitations.

Licensing
Restore changes functionality is included in the Veeam Universal License. When using a legacy socket-based
license, the Enterprise or Enterprise Plus editions of Veeam Backup & Replication are required.

Infrastructure Components
• You can restore files from the file systems listed in section Platform Support.

• The account that you use to start the Veeam Backup & Replication console and to connect to the backup
server must have permissions and privileges described in section Veeam Backup & Replication Console
Permissions.

• You can restore files from basic disks and dynamic disks (including simple, mirrored and striped volumes).

• [For restore to another VM, to original location, or permissions only] If the target VM uses the gMSA
account and you restore files from a backup, you must also install this account on the mount server
associated with the backup repository on which the backup resides. If you restore from a replica, you must
install the gMSA account on the backup server.

• [For restore to original location] VM guest OS must be accessible from the backup server over the
network, or over PowerShell Direct (for VMs that reside on Microsoft Hyper -V Server 2016 or later).

Source for Data Recovery


• See limitations in the VM section.

• You can restore VM guest OS files from a backup that has at least one successfully created restore point.

• You cannot restore files from a backup created in the reverse incremental mode if the backup job is being
performed. If the backup is created in the incremental backup mode and the backup job is being
performed, you can restore files from any available restore point.

• You cannot restore pipes and other file system objects. Guest OS file restore supports recovery of files and
folders only.

• You cannot restore guest OS files encrypted with Windows EFS.

• You cannot restore and browse guest OS files on disks encrypted by BitLocker.

2129 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Processing of reparse points is supported only for NTFS. Note that reparse points with reparse tag values
other than IO_REPARSE_TAG_MOUNT_P OINT, IO_REPARSE_TAG_SYMLINK and IO_REPARSE_TAG_DEDUP
may be processed and restored incorrectly.

• [For restore to original location] You cannot restore VM guest OS files if you have excluded the system
disk from the VM backup used for restore and the volume GUID of the system disk was changed after the
VM backup creation.

• [For comparison functionality and restore of permissions only] Check that VMware Tools are installed on
the original machine and the machine is accessible over the network.

• You cannot use the comparison functionality if the Group Managed Service Account (gMSA) account is
used for the VM whose files you plan to restore.

• The comparison functionality is not available for backups created by Veeam Backup for RHV, for backups
exported with K10 policies and for backups stored in external repositories (for example, backups created
by Veeam Backup for AWS, Veeam Backup for Microsoft Azure and so on).

• [For permission restore] Permissions can be restored only for files and folders that are still present on the
original VMs. If files and folders are missing, restore fails.

• The comparison functionality uses Veeam Deployer Service. This service is a 32-bit service. During the
comparison, the service converts some 64-bit objects in 32-bit objects. That is why such objects are shown
as deleted in the Veeam Backup browser, for example, some objects in the Windows folder.

Target for Data Recovery


• [For restore to original location] Hyper-V Integration Services must be installed on the target VM.
Application-aware processing must be supported for the Microsoft Windows OS of the original
machine. If this is not possible, you can use 1-click file-level restore or copy files to the selected
folder and then move them to their original location.

• [For restore to another VM] You can restore items only to Microsoft Windows-based VMs. You can
select a VM only within the same virtual infrastructure where the original VM r esides. For example, if
the original VM resides in VMware vSphere, you can select a VM that resides in VMware vSphere
only.

• [For permission restore] Veeam Backup & Replication restores only permissions. Attributes such as
Read-only, Encrypted and so on are not restored.

ReFS
• The machine on which a mount point is created (for example, the mount server) must run Microsoft
Windows Server 2012 or later.

• The machine on which a mount point is created must support the same ReFS version or later than
the version used on the VM from which you plan to restore files. For more information on which
OSes support which ReFS, see ReFS versions and compatibility matrix.

To learn in which scenarios on which machines mount points are created, see Mount Points and Restore
Scenarios.

2130 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Data Deduplication
If you plan to restore files from a VM running Microsoft Windows Server 2012 or later and data deduplication is
enabled for some VM volumes, consider the following:

• The machine on which a mount point is created (for example, the mount server) must run Microsoft
Windows Server 2012 or later.

• The machine on which a mount point is created must run Microsoft Windows Server of the same
version or later than the guest OS of a VM from which you plan to restore files.

• Data deduplication must be enabled on the machine on which a mount point is created.

To learn in which scenarios on which machines mount points can be created, see Mount Points and Restore
Scenarios.

Restoring VM Guest OS Files (FAT, NTFS or ReFS)


To restore VM guest OS files and folders, use the File Level Restore wizard.

2131 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch File Level Restore Wizard

To launch the File Level Restore wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from backup or Restore from replica >
Guest files restore > Microsoft Windows.

• Open the Home view. In the inventory pane, select Ba ckups or Replicas. In the working area, expand the
necessary backup, click the VM whose files you want to restore and click Guest files > Microsoft W indows
on the ribbon. Alternatively, right-click the VM whose files you want to restore and select Restore g uest
files > Microsoft Windows.

• Double-click the VBK or VBM file (for example, in Microsoft Windows Explorer). In the displayed window,
select the VM and click Restore > Guest files (Microsoft W indows).

You can use this option if you perform restore on the backup server. You cannot use this option if you
perform restore remotely over the Veeam Backup & Replication console.

2132 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VM

At the Ma chine step of the wizard, select the VM whose guest OS files you want to restore:

1. In the Ma chine list, expand the necessary backup.

2. Select the VM.

2133 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point

At the Restore P oint step of the wizard, select the restore point from which you want to restore the VM guest
OS files.

2134 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Restore Reason

At the Rea son step of the wizard, enter a reason for restoring VM guest OS files. The information you provide
will be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2135 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Verify Restore Settings

At the Summary step of the wizard, check details of the restore task and click Browse to close the wizard and
open Veeam Backup browser.

2136 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Finalize Restore

After you close the wizard, Veeam Backup & Replication opens the Veeam Backup browser with the file system
tree of the restored VM.

You can perform the following operations in the Veeam Backup browser:

• Compare files and folders from a backup with the original files and folders (the Comp are command).

• Restore only changed files and folders to the original location (the Restore changed only command).

• Copy files and folders to the Veeam Backup & Replication console or network shared folder (the Cop y to
command).

• Restore files and folders to another machine in the virtual infrastructure (the Restore to command.

• Restore files and folders to the original location (the Restore command).

• Restore permissions only (the P ermissions only command.

• Launch application item restore (the Ap p lication items command).

• Open files in Microsoft Windows File Explorer.

After you finish restoring files, close the Veeam Backup browser.

NOTE

Consider the following:

• To use the restore and comparison functionality, check Requirements and Limitations.
• In the Veeam Backup browser, names of the restored VM hard disks may differ from the original
ones.
• Folder symbolic links are displayed under the icon.
• When restoring symbolic links to the original location or to another machine,
Veeam Backup & Replication restores only links, not the content they point to.
• Hard links are displayed and restored as files.

Comparing Files and Folders


When Veeam Backup & Replication compares files, it compares their attributes. When
Veeam Backup & Replication compares folders, it compares folder attributes, and also folder and file attributes
inside the folder recursively. Once a file or folder with changed attributes is found, Veeam Backup & Replication
stops comparing items and marks the folder as changed. If you further br owse the folder in the compared state,
Veeam Backup & Replication continues comparing non-compared files and folders. Veeam Backup & Replication
compares the following attributes: Date Created, Date Modified, Size (only for files), Read -Only, Hidden,
Archive, NTFS Encryption.

To compare files and folders from a backup with the files and folders stored in the original location:

1. Select the necessary files and folders in the file system tree or in the details pane on the right. You can
also select disks. In this case, Veeam Backup & Replication will compare files and folders stored on the
disks.

2. Right-click one of the selected items and select Compare > Compare. Alternatively, click Compare with
P roduction on the ribbon.

2137 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
3. If prompted, in the Credentials window, specify user credentials to access the original location.

After the comparison, files and folders will have the following comparison states in the Item State column:
changed , unchanged , deleted , pending , or failed to compare. The states are updated when you turn off and then
turn on the comparison mode, and when you start restoring changes of files and folders. Note that when
comparing symbolic links, Veeam Backup & Replication compares attributes of the links, not the attributes of
files and folders which the symbolic link points to.

For files and folders in the comparison states, Veeam Backup & Replication provides other restore operations
than for files and folders in the non-comparison state. For example, you can restore only changed files and
folders. For more information, see Restoring Changed Files and Folders.

TIP

To show only changed files and folders (in the changed and deleted states), right-click any area in the
Veeam Backup browser and select Comp are > Show changes only. Alternatively, click Show Changes Only
on the ribbon. Note that in this case the search field becomes unavailable. To show all files and folders,
click the Show changes only or Show Changes Only option once again.

To switch off the comparison states, select an item in the comparison state, click Compare > Compare.
Alternatively, click Compare with Production on the ribbon. Note that if you switch off comparison for child
files and folders, comparison for parent folders will also be switched off.

You can view which attributes were changed for files and folders:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and select Compare > Compare attributes. Alternatively, click
Compare Attributes on the ribbon.

2138 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
In the Compare Attributes window, Veeam Backup & Replication shows changed attributes. If you want to show
all attributes, click the Show unchanged attributes check box at the top right corner. Note that
Veeam Backup & Replication shows attributes maximum for 500 files and folders and shows attributes for the
selected files and folders, not for the nested files.

Restoring Changed Files and Folders


To restore only changed files and folders to the original location, do the following:

3. Select the necessary files and folders in the file system tree or in the details pane on the right. Note that
at least one file or folder must be in a comparison state. Files and folders in the non-comparison state,
Veeam Backup & Replication will compare automatically.

4. Right-click one of the selected items and select one of the following:

o To overwrite the original files and folders with the ones restored from the backup, select Restore
cha nged only > Overwrite.

o To save the files and folders restored from the backup next to the original ones, select Restore
cha nged only > Keep.

Veeam Backup & Replication will add the RESTORED_YYYYMMDD_HHMMSS postfix to the original
names and store the restored items in the same folder where the original items reside.

Alternatively, you can select the same commands on the ribbon.

2139 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
If you want to restore entire files and folders to the original location, see Restoring to Original Location.

Saving Files and Folders to New Location


To copy files and folders to the VM where the Veeam Backup & Replication console is installed or to a network
shared folder:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and click Cop y to. Alternatively, click Cop y to on the ribbon.

3. In the Choose Folder window, select the necessary destination:

o To recover files and folders to a folder on the VM where the Veeam Backup & Replication console is
installed, click Browse to find the necessary folder.

o To recover files and folders to a network shared folder, enter a path to the destination folder in the
Choose folder field.

4. In the Choose Folder window, choose whether to preserve original NTFS permissions or not:

o To keep the original ownership and security permissions for the restored items, select the P reserve
p ermissions a nd ownership check box.

Veeam Backup & Replication will copy selected files and folders along with associated Access Control
Lists, preserving granular access settings.

o If you do not want to preserve the original ownership and access settings for the restored items, leave
the P reserve permissions and ownership check box not selected.

Veeam Backup & Replication will change security settings: the user who launched the
Veeam Backup & Replication console will be set as the owner of the restored item, while access
permissions will be inherited from the folder to which the restored item is copied.

5. If prompted, in the Credentials window, specify user credentials to access the destination location.

2140 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Consider the following:

• The copy to operation does not use the comparison states and copies all selected files and folders.
• When copying symbolic links, Veeam Backup & Replication copies the content which the links point
to.

Restoring Files and Folders to Another VM


This functionality is available for backups of Microsoft Hyper-V VMs created by Veeam Backup & Replication.
Note that files and folders that you plan to restore must be in the non-comparison state.

To restore files and folders to a new location over the network or without the network, do the following:

5. Select the necessary files and folders in the file system tree or in the details pane on the right.

6. Right-click one of the selected items and select one of the following:

o If you want to overwrite files and folders with identical names in the target location, select Restore to
> Overwrite.

o If you want to keep files and folders with identical names in the target location, select Restore to >
Keep.

If there are items with identical names, Veeam Backup & Replication will add the
RESTORED_YYYYMMDD_HHMMSS postfix to the original names and store the restored items in the
target location.

Alternatively, you can select the same commands on the ribbon.

7. In the Select Virtual Machine window, select the target workload.

8. In the Credentials window, provide credentials to connect to the target workloa d.

2141 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
9. [For backups other than created by Veeam Agent for Linux] In the Choose Directory window, specify a
folder where items will be restored.

Restoring Files and Folders to Original Location


To restore files and folders to the original location, do the following:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and select one of the following:

o To overwrite the original files and folders with the ones restored from the backup, select Restore >
Overwrite.

o To save the restored files and folders next to the original ones, select Restore > Keep.

Veeam Backup & Replication will add the RESTORED_YYYYMMDD_HHMMSS postfix to the original
names and store the restored items in the same folder where the original items reside.

2142 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you can select the same commands on the ribbon.

Restoring Permissions
This functionality is available for files and folders in the non-comparison state.

To restore permissions for files and folders, do the following:

2. Select the necessary files and folders in the file system tree or in the details pane on the right.

3. Right-click one of the selected items and select Restore > P ermissions only. Alternatively, you can select
Restore > P ermissions only on the ribbon.

2143 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Launching Veeam Explorers
If you are restoring guest OS files from VMs where the supported applications (Microsoft Active Directory,
Oracle and so on) are installed, you can also launch application item restore directly from the Veeam Backup
browser. To restore application items, Veeam Backup & Replication uses special tools called Veeam Explorers.

To launch application item restore, do the following:

1. On the ribbon, switch to the Home tab.

2. Click Ap p lication Items and select the required application.

3. In the opened Veeam Explorer, perform the necessary operations. For more information on Veeam
Explorers, see the Veeam Explorers User Guide.

Working with Microsoft Windows File Explorer


You can use Microsoft Windows File Explorer to work with restored files and folders:

1. On the ribbon of the Veeam Backup browser, switch to the Home tab and click Mount to Console to mount
the VM disks to the Veeam Backup & Replication console.

2. To open Microsoft Windows File Explorer, do the following:

o Click Op en in Explorer on the Veeam Backup browser ribbon or right-click the necessary folder and
select E x plorer.

o Click File Explorer in the Sta rt menu of the VM where Veeam Backup & Replication console is
installed. Browse to the C:\VeeamFLR\<vmname>\<volume n> folder where the VM disks are
mounted and find the necessary files.

NOTE

The Mount to Console button is not available if the mount point is already created on the
Veeam Backup & Replication console.

2144 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
It is recommended that you use Microsoft Windows File Explorer only to view file content, not to restore files.
For guest OS file restore, use Veeam Backup browser. This browser has the following advantages:

1. You can browse the VM guest OS file system ignoring the file system ACL settings.

2. You can preserve permissions and ownership during file-level restore.

If you open the VM file system in Microsoft Windows Explorer, these capabilities are not available. For more
information, see Microsoft Docs.

Closing Veeam Backup Browser


You can browse VM guest OS files only while the Veeam Backup browser is open. After the Veeam Backup
browser is closed, Veeam Backup & Replication unmounts VM disks from the VM where the
Veeam Backup & Replication console is installed and from the mount server (if you have restored VM guest OS
files to the original location).

It is recommended that you close the Veeam Backup browser after you have finished restoring VM guest OS
files. When the Veeam Backup browser is open, the backup file whose VM guest OS file system is displayed in
the browser is locked in the backup repository. As a result, some scheduled operations that use this backup file
may fail.

Veeam Backup & Replication checks if there is any activity in the Veeam Backup browser with an interval of 5
minutes. If the user or Veeam Backup & Replication components and services do not perform any actions for 30
minutes, Veeam Backup & Replication displays a warning that the Veeam Backup b rowser is to be closed in 5
minutes.

After the warning is displayed, you can perform one of the following actions:

• You can close the Veeam Backup browser manually.

• You can click Ca ncel to postpone the close operation. In this case, the Veeam Backup browser will remain
open for 5 minutes. After this period expires, Veeam Backup & Replication will display the warning again.

• You can perform no action at all. In this case, the Veeam Backup browser will close automatically in 5
minutes.

Restore from Linux, Unix and Other File Systems


The method of restore from Linux, Unix and other file systems helps you restore files from backups of Linux,
Solaris, BSD, Unix and Mac workloads. For the list of supported OSes and file systems, see Platform Support.

You can restore files to the original or new location, access restored files using FTP or launch application item
restore for the files. For more information, see Finalize Restore.

How Restore Works


When you perform guest OS file restore, Veeam Backup & Replication provides the following options for
mounting VM disks from the backup:

• Mounting disks to a helper host. As a helper host, you can select the target host where you want to
restore files from the backup or any other Linux server. We recommend you to specify the same server to
which you want to restore the files. This will improve the performance.

• Mounting disks to a helper appliance. The helper appliance is a helper VM running a stripped down Linux
kernel that has minimal set of components. The appliance is quite small — around 50 MB. It requires 2048
MB RAM and 2 CPU.

2145 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
When you perform guest OS file restore, Veeam Backup & Replication performs the following operations:

1. [If you have selected to mount disks to helper appliance] Veeam Backup & Replication deploys the helper
appliance on the Microsoft Hyper-V host in the virtual infrastructure.

2. Veeam Backup & Replication mounts disks of a VM from the backup to the helper host or helper appliance.
The backup file itself remains in the read-only state in the backup repository or volume.

3. Veeam Backup & Replication launches the Veeam Backup browser where mounted VM disks are dis played.
You can browse the VM guest file system in the Veeam Backup browser and restore files or folders to the
original VM or to another location. Also, you can enable an FTP server on the virtual appliance and allow
VM owners to restore files themselves.

4. The operations differ depending on which restore command you use:

o The Restore or Restore to command to restore files to the original location or to another Microsoft
Hyper-V VM.

If you have installed the Linux Management Agent, the helper host or helper appliance connects to
the VM to which you restore files (target VM) using this agent and restores files. This is the preferred
way of connection.

If the backup server fails to connect to the Management Agent, the backup s erver connects to the
target VM over SSH. Then Veeam Backup & Replication deploys on the VM a temporary agent which
performs restore.

NOTE

If you use the Restore to command and the target machine is a member of a protection group
for pre-installed Veeam Agents, the backup server connects to the target machine and performs
restore using SSH protocol.

o The Cop y to command to restore files to a new location.

The helper host or helper appliance connects to the VM to which you restore files (target VM) over
SSH. Then Veeam Backup & Replication deploys on the VM the agent which performs restore.

5. When you close the Veeam Backup browser or it is closed by timeout, Veeam Backup & Replication
unmounts the content of the backup file from the helper host or helper appliance.

6. [If you have selected to mount disks to helper appliance] Veeam Backup & Replication unregisters the
helper appliance on the Microsoft Hyper-V host.

Considerations and Limitations


Before you restore VM guest OS files, check the following considerations and limitations.

Infrastructure Components
• Check the supported file systems. For details, see the File-Level Restore section.

• [For source and target VM] Veeam Backup & Replication uses the ICMP ping command to define whether
a VM is available over network. If the VM must be available over the network, check that ICMP protocol is
enabled on the VM.

• Veeam Backup & Replication must have access to the guest OS of the target VM to deploy a coordination
process. The coordination process performs a number of administrative actions on the target VM guest OS,
for example, collects information about mount points.

2146 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The mount server, helper host and helper appliance, must have access over the network to a VM w hose
files you restore and to Hyper-V host where the VM resides.

• You can restore from Novell Storage Services (NSS) file system only if you use FUSE. When using FUSE,
the helper host must differ from the backed-up VM.

Helper Host
If you mount disks to a helper host, consider the following:

• You can restore from ZFS using the helper host option if the zfsutils-linux package is installed on the
specified helper host. The package zfs-fuse package is not supported.

• The helper host OS kernel must support the file system that you plan to mount on this host. Otherwise,
the mount will be refused and in rare cases it may cause kernel panic.

• For the helper host option, mounting of LVM snapshots is not supported. Thus, LVM snapshots are
skipped from processing.

• [For backups created by Veeam Agent for Linux] The original machine cannot be used as the helper host
for the 32-bit versions of the Linux-based OSes. However, for VM backups, you can still use the original
VM as the helper host for the 32-bit versions of the Linux-based OSes.

• If you want to restore files from a Btrfs disk and select the original host as a helper host, the mount of the
Btrfs disk will fail. The issue occurs due to restriction of mounting two Btrfs disks with identical IDs to the
same machine. To avoid this issue, use the helper appliance option or a different Linux -based server that
supports Btrfs. However, note that Btrfs disks can be restored for backups created by Veeam Agent for
Linux. During the backup process, Veeam Agent for Linux changes disk IDs in the backup file.

• Hardened repositories cannot be selected as helper hosts.

Source for Data Recovery


• You can restore VM guest OS files from a backup that has at least one successfully created restore point.

• You can restore files whose names are written in all locales in the UTF-8 encoding. If the encoding is other
than UTF-8, you can restore only files whose names are written in the English locale.

• The multi-OS guest OS file restore wizard does not support restore of deduplicated volumes (for example,
Microsoft Windows volumes with data deduplication enabled).

• You cannot restore files from a backup created in the reverse incremental mode if the backup job is being
performed. If the backup is created in the incremental backup mode and the backup job is being
performed, you can restore files from any available restore point.

• [For backups of BSD, macOS and Solaris VMs] You cannot restore files directly to the original location. Use
the Cop y to option instead.

• [For backups of Linux workloads] You can restore files from basic disks, Linux LVM (Logical Volume
Manager) and ZFS pools. Encrypted, RAID1 and mirrored LVM volumes are not supported.

• [For backups of Linux workloads] RAID mounts and restores a re not supported.

• [If you restore from backups with guest file system indexing disabled] To properly show the file system
tree in the Veeam Backup browser, check that the /etc/fstab file lists disk UUIDs or labels. Disks listed
using device names are shown outside the file system tree as separate disks.

2147 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Target for Data Recovery
• If you plan to restore VM guest OS files to their original location or to another Microsoft Hyper -V
VM, Hyper-V Integration Services must be installed on the target VM.

• [For restore to a new location] You can restore items only to Linux-based VMs. BSD, macOS and
Solaris VMs are not supported.

• Veeam Backup & Replication uses the SSH protocol to communicate with the target Linux VM and
requires the SCP utility on the target VM. Make sure that the SSH daemon is properly configured and
SCP utility is available on the target VM.

• [For restore to a new location] Veeam Backup & Replication can restore ACL for recovered VM guest
OS files. To let Veeam Backup & Replication detect the target Linux system architecture and kernel
version, the following utilities must be present in the minimal configuration of the system: arch and
uname.

• [For Veeam Backup & Replication version 12.1 (build 12.1.0.2131) and later] For backups created by
Veeam Agents, you can use the Restore to (restore to a new location) command only if the target
computer is available over the network. This applies to backups created by Veeam Agent for Linux,
Veeam Agent for IBM AIX or Veeam Agent for Oracle Solaris.

Linux Firewalls in Helper Host and Target for Data


Recovery
If you want to use the helper host option or if you want to restore files to a new location on another Linux VM,
consider the following.

Veeam Backup & Replication automatically opens ports used for the restore process on the helper host and on
the target Linux VM. Generally, Veeam Backup & Replication automatically opens ports for most popular
firewalls (iptables, ufw, firewall-cmd). However, if for some reason the ports are not opened, you can open the
ports manually. You can also specify these ports at the SSH Connection step of the New Linux Server wizard.
Note that ports are opened dynamically: if 10 concurrent jobs are running, Veeam Backup & Replication opens
ports 2500-2509.

If you use the firewalld tool, you can configure firewall rules to open ports only in necessary zones. By
default, Veeam Backup & Replication opens ports in all active firewalld zones. If your firewall is configured
for different zones, and you want to minimize security holes, you can configure Veeam Backup & Replication to
open the ports only for certain zones. To do this, perform the following:

• On the helper host or target Linux host, create the /etc/VeeamNetConfig file and define the
following parameter:

FirewalldZones=zone_name_1, zone_name_2

where zone_name_1, zone_name_2 is a list of zone names where the ports must be open.
Veeam Backup & Replication will skip the zones that are not in this list.

• [Only for helper host] If you select a Linux host that is already added to the
Veeam Backup & Replication infrastructure, you should also add required zones to the
/opt/veeam/transport/VeeamTransportConfig file.

FirewalldZones=zone_name_1, zone_name_2

2148 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NOTE

Veeam Backup & Replication opens the port 2500 in all zones even if you have specified the required
zones in configuration files.

Restoring VM Guest OS Files (Multi-OS)


To restore VM guest OS files and folders from Linux or Unix-based machines, use the Guest File Restore wizard.

2149 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Launch Guest File Restore Wizard

To launch the Guest File Restore wizard, do one of the following:

• On the Home tab, click Restore > Microsoft Hyper-V > Restore from backup > Guest files restore > Linux
a nd other.

• Open the Home view. In the inventory pane, select Ba ckups. In the working area, expand the necessary
backup, click the VM whose files you want to restore and click Guest files > Linux and other on the ribbon.
Alternatively, right-click the VM whose files you want to restore and select Restore guest files > Linux and
other.

• Double-click the VBK or VBM file (for example, in Microsoft Windows Explorer). In the displayed window,
select the VM and click Restore > Guest files (Linux and other).

You can use this option if you perform restore on the backup server. You cannot use this option if you
perform restore remotely over the Veeam Backup & Replication console.

2150 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Select VM

At the Virtual Machine step of the wizard, select the VM whose guest OS files you want to restore:

1. In the Virtual machine list, expand the necessary backup.

2. Select the VM.

2151 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Select Restore Point

At the Restore P oint step of the wizard, select the restore point from which you want to restore the VM guest
OS files.

2152 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Specify Helper Host

At the Help er Host step of the wizard, you can select a machine that will be used as a helper host.
Veeam Backup & Replication will mount disks of a machine from the backup to the selected helper host.
Alternatively, you can choose to configure a new helper appliance where Veeam Backup & Replication will
mount VM disks. For details on helper hosts and appliances, see Restore from Linux, Unix and Other File
Systems.

To specify the helper host, do the following:

1. From the Linux server list, select one of the following options:

o < Hostname> (original host) — to specify the original Linux server as the helper host. This option is
available starting from Veeam Backup & Replication version 12.1 (build 12.1.0.2131).

o < Hostname> — to specify a Linux server as the helper host. The wizard displays all Linux serve rs
added to the Veeam Backup & Replication infrastructure.

o Sp ecify a different host — to specify a Linux server that is not added to the
Veeam Backup & Replication infrastructure.

o Use a temporary helper appliance — to use a temporary helper appliance. If you select this option, the
wizard will include a step for configuring the helper appliance.

2. [For < Hostname> ( original host) option; optional] In the Host credentials window, specify credentials for
the original Linux server.

3. [For the Sp ecify different host option] In the Linux Server window, specify the helper host name and
connection setting:

a. At the Host name field, specify the IPv4 or IPv6 address or the host name of the Linux server which
will be used as a helper host. Note that you can use IPv6 addresses only if IPv6 communication is
enabled as described in section IPv6 Support.

b. From the Credentials list, select an account that will be used to connect to the helper host. If you
haven't added the account before, click the Ad d button on the right of the Credentials list and follow
the instructions described in section Linux Accounts.

c. If you want to change the default SSH settings, click Ad vanced and configure SSH settings as
described in section Specify Credentials and SSH Settings.

2153 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
d. Click OK to save the helper host settings.

2154 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 5. Specify Location for Helper Appliance

The Helper Appliance step of the wizard is available only if you have selected the Use a temporary helper
a p pliance option at the Specify Helper Host step.

Select a Microsoft Hyper-V host for placing a helper appliance:

1. At the bottom of the window, click Customize.

2. In the Host field, select the Microsoft Hyper-V host on which the helper appliance will be registered.

3. Select a network for the helper appliance:

a. On the right of the Network field, click Choose.

In the Select Network window, Veeam Backup & Replication will display a list of networks to which
the specified host is connected.

b. From the Networks list, select a network to which the helper appliance must be connected and click
OK.

Consider that the backup server and the mount server must have access to the helper appliance over
the network.

4. If you use VLAN IDs, in the VLAN ID field specify the correct VLAN ID of the network where the helper
appliance must reside.

5. Specify IP addressing settings for the helper appliance and DNS server:

a. Click Configure.

b. Switch to the IP v4 or IP v6 tab depending on which addresses you want to configure. Note that you
can use IPv6 addresses only if IPv6 communication is enabled as described in section IPv6 Support.

c. Configure IP settings for the helper appliance:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain an IP address automatically option selected.

▪ To manually assign a specific IP address to the helper appliance, click Use the following IP
a d dress and specify the IP address settings.

d. Configure IP settings for the DNS server:

▪ If you use a DHCP server in the network and want to obtain the IP address automatically, leave
the Ob tain DNS server address automatically option selected.

▪ To manually assign a specific IP address to the DNS server, click Use the following DNS server
a d dress and specify preferred and alternate addresses.

e. Click OK.

2155 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. To enable FTP access to the restored file system, select the E nable FTP server on appliance check box. As
a result, users will be able to access the helper appliance over FTP, browse the file system of the restored
VM and download necessary files on their own.

2156 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 6. Specify Restore Reason

At the Rea son step of the wizard, enter a reason for restoring VM guest OS files. The information you provide
will be saved in the session history and you can reference it later.

TIP

If you do not want to show this page, select the Do not show me this page again check box. If you further
will want to return this page, follow the instructions described in this Veeam KB article.

2157 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 7. Verify Restore Settings

At the Summary step of the wizard, review the restore settings and click Browse to open Veeam Backup
browser.

If you have selected to mount disks to a helper appliance, it may take about 10 -40 seconds to boot the helper
appliance and open the browser.

2158 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 8. Finalize Restore

After the wizard is closed, Veeam Backup & Replication opens the Veeam Backup browser displaying the file
system tree of the restored VM.

You can perform the following operations in the Veeam Backup browser:

• Restore files to the original location (the Restore command)

• [For Hyper-V, Veeam Agent for Linux] Restore files to a new location (the Restore to command)

• Restore files to a new location over the network (the Cop y to command)

• Access files over FTP

• Access helper appliance logs

NOTE

You can browse the VM guest OS files and access restored files on the FTP only while the Veeam Backup
browser with the restored files is open. After the Veeam Backup browser is closed, the VM disks will be
unmounted from the helper appliance, and the helper appliance will be deleted from the Hyper -V host.

Restoring Files to Original Location


To restore files and folders to the original location, do the following:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and select one of the following:

o To overwrite the original files and folders with the ones restored from the backup, select Restore >
Overwrite.

o To save the restored files and folders next to the original ones, select Restore > Keep.

Veeam Backup & Replication will add the RESTORED_YYYYMMDD_HHMMSS postfix to the original
names and store the restored items in the same folder where the original items reside.

2159 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you can select the same commands on the ribbon.

If you restore files from disks that were not mounted to the file sy stem, Veeam Backup & Replication asks for a
target directory where to restore the selected files. In this case, file restore to the original location is not
possible.

To restore files to the original location, Veeam Backup & Replication can use the following:

• The account for VM guest OS access specified in the backup job settings.

• The account specified for the original server used as the helper host.

• The credentials specified in the Protection Group.

If the account does not have sufficient rights to access the target VM, you will be prompted to enter credentials.
In the Credentials window , specify a user account to access the destination location (server or shared folder).

In some cases, you may remove the original VM and restore it from the backup by the time of guest OS file
restore. If you then attempt to restore VM guest OS files to the original location, Veeam Backup & Replication
will not be able to find the original VM by its reference ID, and display a warning. Click OK and browse to the
target VM in the virtual infrastructure to which you want to restore VM guest OS files.

2160 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Files and Folders to New Location
You can restore files and folders to a new machine of the same platform over the network or without the
network. This functionality is available for backups of Microsoft Hyper-V VMs created by
Veeam Backup & Replication and backups of computers created by Veeam Agent for Linux, Veeam Agent for
IBM AIX or Veeam Agent for Oracle Solaris. Restore from backups created by Veea m Agents is available starting
from Veeam Backup & Replication version 12.1 (build 12.1.0.2131).

To restore files and folders to a new location over the network or without the network, do the following:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected items and select one of the following:

o If you want to overwrite files and folders with identical names in the target location, select Restore to
> Overwrite.

o If you want to keep files and folders with identical names in the target location, select Restore to >
Keep.

If there are items with identical names, Veeam Backup & Replication will add the
RESTORED_YYYYMMDD_HHMMSS postfix to the original names and store the restored items in the
target location.

Alternatively, you can select the same commands on the ribbon.

3. In the Select Virtual Machine window, select the target workload.

4. In the Credentials window, provide credentials to connect to the target workload.

5. [For backups other than created by Veeam Agent for Linux] In the Choose Directory window, specify a
folder where items will be restored.

2161 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Saving Files and Folders to New Location Over Network
You can restore files and folders to components of the Veeam Backup & Replication infrastructure available over
the network.

To save files and folders to a new location over the network:

1. Select the necessary files and folders in the file system tree or in the details pane on the right.

2. Right-click one of the selected files or folders and select Cop y to.

3. In the Select Destination window, select the necessary destination:

o To recover files to a server already added to the Veeam Backup & Replication infrastructure, select the
server from the Server drop-down list and then specify the path to a folder where files will be
recovered.

o To recover files to a Linux server that is not added to the Veeam Backup & Replication infrastructure,
select Sp ecify a different host from the Server drop-down list and follow the steps of the wizard to
add a Linux server that will be used as a target host. The server will be added ad -hoc. Then specify
the path to a folder where files will be recovered.

The server you add ad-hoc will not appear in the list of managed hosts in
Veeam Backup & Replication: its purpose is to host the files that you recover. It will only remain
visible in the Veeam Backup browser until all currently active file-level restore sessions are
completed.

IMP ORTANT

Only Linux servers can be added ad-hoc.

o To recover files to a shared folder, specify a path to the destination folder in the P a th to folder field.

4. If you want to preserve original permissions and ownership for recovered files, select the P reserve
p ermissions a nd ownership check box in the Select Destination window.

IMP ORTANT

To restore original permissions and ownership settings, the user account you have specified must
have privileges to change the owner on the selected server or shared folder.

2162 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
5. If prompted, in the Credentials window, specify settings of the user account to access the destination
location.

Accessing Files over FTP


If you have chosen to enable FTP server on the helper appliance, the restored file system will also be available
over FTP at ftp://<FLR_appliance_IP_address> . Other users in the same network can access the helper appliance
to restore the files they need.

Accessing the appliance over FTP requires credentials. Use the Guest OS helper appliance credentials specified
in managed credentials. If the password has not been updated, refer this Veeam KB article.

NOTE

[For restore from storage snapshots] You can browse to the VM guest OS files and access restored files on
the FTP only while the Veeam Backup browser is open. After the Veeam Backup browser is closed,
Veeam Backup & Replication will unmount VM disks from the helper appliance, remove the helper
appliance and unmount the storage snapshot from the ESXi host (unless this storage snapshot is used by
other restore operations).

2163 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Accessing Helper Appliance Logs
If you need to access logs of the helper appliance, click Sup port Logs on the Veeam Backup browser ribbon.
Veeam Backup & Replication will show the Log node under the file system tree. To hide this node, click Sup port
Log s once again.

Restore from Other File Systems


You can restore file systems other than those listed in section Guest OS File Restore. For this purpose, use the
Instant Recovery to Microsoft Hyper-V technology.

To restore files and folders, do the following:

1. Use Instant Recovery to publish the VM from the backup file on the Microsoft Hyper-V host in the virtual
infrastructure. Do not start the recovered VM.

2. Mount the disks of the restored VM to any VM that can read the file system of the original VM.

3. Restore files or folders using native file management tools.

2164 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Alternatively, you can mount the VM disks to a Microsoft Windows VM and use file management tools.

Viewing File Restore Session Statistics


You can view statistics about performed guest OS file restore sessions.

To view the restore session statistics, do one of the following:

• Open the Home view, in the inventory pane select La st 24 hours. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

• Open the History view, in the inventory pane select Restore. In the working area, double-click the
necessary restore session. Alternatively, you can select the session and click Sta tistics on the ribbon or
right-click the session and select Sta tistics.

The file restore statistics provides detailed data on file restore sessions:

• At the top of the Restore Session window, Veeam Backup & Replication shows general session statistics: a
name of the machine whose guest OS files are restored during the session, a user name of the account
under which the session was started, session status and duration details.

• The Sta tistics tab shows detailed information about the files restored during the session.

• The Rea son tab shows the reason for the guest OS file restore that was specified at the Rea son step of the
File Level Restore wizard.

• The P a rameters tab shows information about the restore point selected for the guest OS file restore at the
Restore Point step of the File Level Restore wizard.

2165 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• The Log tab shows a list of operations performed during the session.

2166 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Application Item Restore
Veeam Backup & Replication provides auxiliary tools called Veeam Explorers that allow you to restore
application items directly from backups or replicas. These backups and replicas must be created with the
enabled application-aware processing option.

You can restore items of the following applications:

• Microsoft Active Directory

• Microsoft SQL Server

• Oracle

• PostgreSQL

• Microsoft Exchange

• Microsoft SharePoint

• Microsoft OneDrive for Business

• Microsoft Teams

Veeam Explorers are distributed as part of Veeam Backup & Replication, and you do not need to install them
separately. You also do not need to purchase any additional license to use Veeam Explorers. For more general
information, see the Veeam Explorers Overview section of the Veeam Explorers User Guide.

Restoring Microsoft Active Directory Items


To restore Microsoft Active Directory items from a backup or replica, Veeam Backup & Replication uses Veeam
Explorer for Microsoft Active Directory.

IMP ORTANT

Before you restore Microsoft Active Directory items, check requirements and limitations listed in the
Planning and Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements
is that the backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft Active Directory from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft Active Directory on the ribbon. Alternatively, right-click the machine or VM replica and select
Restore application items > Microsoft Active Directory objects.

2167 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the opened Microsoft Active Directory Object Restore wizard, select a restore point from which you
want to restore application items.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft Active Directory. In this explorer, you
can browse, search, restore application items and so on. The detailed information is provided in the Veeam
Explorer for Microsoft Active Directory main section of the Veeam Backup Explorers User Guide. For example:

• Information about viewing and searching objects in the backup file is in the Browsing, Searching and
Viewing Items section.

• Information about adding a database manually is in the Adding Standalone Databases section.

• Information about restoring process is in the Data Restore section.

2168 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Microsoft SQL Server Items
To restore databases from a backup or replica of a Microsoft SQL Server, Veeam Backup & Replication uses
Veeam Explorer for Microsoft SQL Server.

IMP ORTANT

Before you restore Microsoft SQL databases, check requirements and limitations listed in the Planning and
Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that the
backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft SQL Server from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft SQL Server on the ribbon. Alternatively, right-click the machine or VM replica and select
Restore application items > Microsoft SQL Server databases.

4. In the opened Microsoft SQL Server Database Restore wizard, select a restore point from which you want
to restore databases.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft SQL Server. In this explorer, you can
view, restore databases and so on. The detailed information is provided in the Veeam Explorer for Microsoft SQL
Server main section of the Veeam Backup Explorers User Guide. For example:

• Information about database is in the Viewing Database Information section.

• Information about restoring process is in the Data Restore section.

2169 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Information about adding a database manually is in the Adding Standalone Databases section.

Restoring Oracle Items


To restore databases from a backup or replica of an Oracle system, Veeam Backup & Replication uses Veeam
Explorer for Oracle.

IMP ORTANT

Before you restore Oracle databases, check requirements and limitations listed in the Planning and
Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that the
backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Oracle from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Ora cle on the ribbon. Alternatively, right-click the machine or VM replica and select Restore application
items > Oracle databases.

2170 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the opened Ora cle Database Restore wizard, select a restore point from which you want to restore
databases.

Then Veeam Backup & Replication opens Veeam Explorer for Oracle. In this explorer, you can view, restore
databases and so on. The detailed information is provided in the Veeam Explorer for Oracle main section of the
Veeam Backup Explorers User Guide. For example:

• Information about database is in the Viewing Database Information section. Oracle databases cannot be
added manually.

• Information about restoring process is in the Data Restore section.

2171 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring PostgreSQL Items
To restore instances from a backup or replica of an PostgreSQL system, Veeam Backup & Replication uses Veeam
Explorer for PostgreSQL.

IMP ORTANT

Before you restore PostgreSQL instances, check requirements and limitations listed in the Planning and
Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that the
backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for PostgreSQL from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> P ostgreSQL on the ribbon. Alternatively, right-click the machine or VM replica and select Restore
a p plication items > P ostgreSQL instances.

4. In the opened P ostgreSQL Server Database Restore wizard, select a restore point from which you want to
restore instances.

5. Specify the restore reason.

Then Veeam Backup & Replication opens Veeam Explorer for PostgreSQL. In this explorer, you can view, restore
instances and so on. The detailed information is provided in the Veeam Explorer for PostgreSQL main section of
the Veeam Backup Explorers User Guide. For example:

• Information about the data restore process is in the Data Restore section.

• Information about the instances publishing is in the Data Publishing section.

2172 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Microsoft Exchange Items
To restore Microsoft Exchange items from a backup or replica of a Microsoft Exchange Server,
Veeam Backup & Replication uses Veeam Explorer for Microsoft Exchange.

IMP ORTANT

Before you restore Microsoft Exchange items, check requirements and limitations listed in the Planning and
Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that the
backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft Exchange from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft Exchange on the ribbon. Alternatively, right-click the machine or VM replica and select
Restore application items > Microsoft Exchange Online mailbox items.

4. In the opened Microsoft Exchange Item Level Restore wizard, select a restore point from which you want
to restore application items.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft Exchange. In this explorer, you can view,
browse, restore Microsoft Exchange items and so on. The detailed information is provided in the Veeam Explorer
for Microsoft Exchange main section of the Veeam Backup Explorers User Guide. For example:

• Information about viewing and searching objects in the backup file is in the Browsing, Searching and
Viewing Items section.

• Information about adding a database manually is in the Standalone Databases Management section.

2173 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Information about restoring process is in the Data Restore section.

Restoring Microsoft SharePoint Items


To restore Microsoft SharePoint items from a backup or replica of a Microsoft SharePoint Server,
Veeam Backup & Replication uses Veeam Explorer for Microsoft SharePoint.

IMP ORTANT

Before you restore Microsoft SharePoint items, check requirements and limitations listed in the Planning
and Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that
the backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft SharePoint from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft SharePoint on the ribbon. Alternatively, right-click the machine or VM replica and select
Restore application items > Microsoft SharePoint online content .

2174 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the opened Microsoft SharePoint Item Restore wizard, select a restore point from which you want to
restore application items.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft SharePoint. In this explorer, you can
view, search, restore Microsoft SharePoint items and so on. The detailed information is provided in the Veeam
Explorer for Microsoft SharePoint main section of the Veeam Backup Explorers User Guide. For example:

• Information about viewing and searching objects in the backup file is in the Browsing, Searching and
Viewing Items section.

• Information about adding a database manually is in the Standalone Databases Management section.

• Information about restoring process is in the Restore from Veeam Backup & Replication Backups section.

2175 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restoring Microsoft OneDrive for Business Items
To restore Microsoft OneDrive for Business data from a backup or replica of a Veeam Backup for Microsoft 365
server, Veeam Backup & Replication uses Veeam Explorer for Microsoft OneDrive for Business.

IMP ORTANT

Before you restore Microsoft OneDrive for Business data, check requirements and limitations listed in the
Planning and Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements
is that the backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft OneDrive for Business from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft OneDrive for Business on the ribbon. Alternatively, right-click the machine or VM replica and
select Restore application items > Microsoft OneDrive for Business files.

4. In the opened Microsoft OneDrive for Business Files wizard, select a restore point from which you want to
restore application items.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft OneDrive for Business. In this explorer,
you can browse, view, restore Microsoft OneDrive for Business da ta and so on. The detailed information is
provided in the Veeam Explorer for Microsoft OneDrive for Business main section of the Veeam Backup
Explorers User Guide. For example:

• Information about viewing and searching objects in the backup file is in the Browsing, Searching and
Viewing Items section.

• Information about adding a database manually is in the Standalone Databases Management section.

2176 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
• Information about restoring process is in the Restoring Microsoft OneDrive Data section.

Restoring Microsoft Teams Items


To restore Microsoft Teams data from a backup or replica of a Veeam Backup for Microsoft 365 server,
Veeam Backup & Replication uses Veeam Explorer for Microsoft Teams.

IMP ORTANT

Before you restore Microsoft Teams data, check requirements and limitations listed in the Planning and
Preparation section in the Veeam Backup Explorers User Guide. One of the main requirements is that the
backup or replica must be created with application-aware processing enabled.

To launch Veeam Explorer for Microsoft Teams from Veeam Backup & Replication:

1. Open the Home view.

2. In the inventory pane, select the Ba ckups or Rep licas node.

3. In the working area, select the necessary machine in the backup or VM replica and click Ap p lication Items
> Microsoft Teams on the ribbon. Alternatively, right-click the machine or VM replica and select Restore
a p plication items > Microsoft Teams.

2177 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
4. In the opened Microsoft Teams Files Restore wizard, select a restore point from which you want to restore
data.

Then Veeam Backup & Replication opens Veeam Explorer for Microsoft Teams. In this explorer, you can browse,
view, restore Microsoft Teams data and so on. The detailed information is provided in the Veeam Explorer for
Microsoft Teams main section of the Veeam Backup Explorers User Guide. For example:

• Information about viewing and searching objects in the backup file is in the Browsing, Searching and
Viewing Items section.

• Information about adding a database manually is in the Standalone Databases section.

• Information about restoring process is in the Data Restore section.

2178 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Tape Devices Support
Veeam provides native tape support that is fully integrated into Veeam Backup & Replication. You can
administer all operations on tapes from your Veeam console.

For more information, see the Tape Device Support Guide.

2179 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Storage System Snapshot Integration
To build the data protection and disaster recovery strategy, you can use capabilities of storage systems that
host VM disks. Veeam Backup & Replication integrates with storage systems and offers advanced functionality
that helps you decrease impact from backup and replication operations on the production environment and
significantly improve RPOs.

For more information, see the Storage System Snapshot Integration Guide.

2180 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup for AWS
Veeam Backup & Replication allows you to create and manage data protection and restore tasks for Amazon
Elastic Compute Cloud (Amazon EC2) environments. For this, Veeam Backup & Replication uses a AWS Plug-in
for Veeam Backup & Replication component. This component extends Veeam Backup & Replication functionality
and provides access to Veeam Backup for AWS from the Veeam Backup & Replication console. For more
information, see the Integration with Veeam Backup for AWS Guide.

2181 | Veeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup for
Microsoft Azure
Veeam Backup & Replication allows you to create and manage data protection and restore tasks for Microsoft
Azure environments. For this, Veeam Backup & Replication uses a Microsoft Azure Plug-in for Veeam Backup &
Replication component. This component extends Veeam Backup & Replication functionality and provides access
to Veeam Backup for Microsoft Azure from the Veeam Backup & Replication console. For more information, see
the Integration with Veeam Backup for Microsoft Azure Guide.

2182 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup for
Google Cloud
Veeam Backup & Replication allows you to create and manage data protection and restore tasks for Google
Cloud environments. For this, Veeam Backup & Replication uses a Google Cloud Plug-in for Veeam Backup &
Replication component. This component extends Veeam Backup & Replication functionality and provides access
to Veeam Backup for Google Cloud from the Veeam Backup & Replication console. For more information, see
the Integration with Veeam Backup for Google Cloud Guide.

2183 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup for
Nutanix AHV
Veeam Backup & Replication allows you to manage data protection and restore tasks for Nutanix AHV
environments. For this, Veeam Backup & Replication uses an additional component: Veeam Backup for Nutanix
AHV.

Veeam Backup for Nutanix AHV extends Veeam Backup & Replication functionality and allows you to back up
and restore Nutanix AHV VMs. For more information, see the Veeam Backup for Nutanix AHV User Guide.

2184 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Integration with Veeam Backup for Red
Hat Virtualization
Veeam Backup & Replication allows you to manage data protection and restore tasks for Red Hat Virtualization
(RHV) hosts. For this, Veeam Backup & Replication uses an additional component: Veeam Backup for RHV.

Veeam Backup for RHV extends Veeam Backup & Replication functionality and allows you to back up and restore
RHV VMs. For more information, see the Veeam Backup for RHV User Guide.

2185 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Agent Management
To back up physical machines running Windows, Linux, Unix or macOS operating systems,
Veeam Backup & Replication uses backup agents installed on each computer. Veeam Backup & Replication
operates as a centralized control center for deploying and managing Veeam Agent for Microsoft Windows,
Veeam Agent for Linux, Veeam Agent for IBM AIX, Veeam Ag ent for Oracle Solaris and Veeam Agent for Mac
(Veeam Agents).

For more information about Veeam Agents, see the Veeam Agent Management Guide.

2186 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Cloud Connect
If you want to store your data in the cloud, you can connect to the service provider and write VM backups to
cloud repositories or create VM replicas on cloud hosts.

For more information about Veeam Cloud Connect, see the Veeam Cloud Connect Guide.

2187 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication Utilities
You can use the following Veeam Backup & Replication utilities to perform advanced administration tasks in
your backup infrastructure:

• Extract.exe Utility

• Veeam.Backup.DBConfig.exe Utility

• Veeam Backup Validator

• Veeam Backup Configuration Tool

2188 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Extract Utility
Veeam Backup & Replication comes with an extract utility that can be used to recover machines from backup
files. The extract utility does not require any interaction with Veeam Backup & Replication and can be used as an
independent tool on Linux and Microsoft Windows machines.

The extract utility can be helpful, for example, if it is written to the tape next to machine backup files. In this
case, you get a possibility to recover machines from backups at any moment of time even if backups are
removed from Veeam Backup & Replication or Veeam Backup & Replication is not installed.

IMP ORTANT

If you want to use the extract utility to work with backup files located on any of the extents of your scale -
out backup repository, make sure that incremental and full back up files are located on the same extent.

The extract utility can be used in two interfaces:

• Graphic user interface (GUI)

• Command-line interface working in the interactive and regular mode

The extract utility is located in the installation folder of Veeam Backup & Replication, by default:
%PROGRAMFILES%\Veeam\Backup and Replication\Backup. The folder contains two files for the extract
utility:

• Veeam.Backup.Extractor.exe — utility working in GUI (can be used on Microsoft Windows machines


only)

• extract.exe — utility working in the command-line interface, a version for Microsoft Windows

2189 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Extract Utility in GUI
To restore machine data in the extract utility GUI:

1. Run the Veeam.Backup.Extractor.exe file from the installation folder of


Veeam Backup & Replication.

2. In the Ba ckup file field, specify a path to the backup file from which you want to restore machine data.

3. If the backup file is encrypted, the extract utility will require y ou to provide a password to unlock the
backup file.

4. In the Ta rget folder field, specify a path to the destination folder where machine data must be restored.

5. From the Ma chines list, select machines whose data you want to restore.

6. Click E x tract. Machine data will be restored to the specified folder.

IMP ORTANT

If you restore machine data in the extract utility GUI, consider the following:

• The extract utility can be started on Microsoft Windows machines only.


• If you plan to start the extract utility on the machine other than the backup server, make sure that
you copy the Veeam.Backup.Extractor.exe file together with the extract.exe file from the
product installation folder and store these files to the same fold er on the destination machine. In
the opposite case, the extract utility will fail to start.

2190 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Extract Utility in Interactive Mode
To start the extract utility in the interactive mode, run the extract.exe file from the product installation
folder).

You will have to sequentially enter the following arguments:

1. A path to the backup file from which the machine must be restored. After you enter the path, the extract
utility will display a list of all machines included in the backup and their description.

2. A name of the machine that you want to restore. If there is more than one machine with the specified
name in the backup, you will be asked to specify the host on which the backed -up machine resides. If you
want to restore all machines from the backup, press [Enter] on the keyboard.

3. If the backup was encrypted, password that was used to encrypt the backup file.

4. An output directory to which machines must be restored. If you want to restore machines to the current
directory, press [Enter] on the keyboard.

5. The operation confirmation. Press [Y] on the keyboard to restore a machine to the directory you specified.
If you want to abort the operation, press [Enter] on the keyboard.

2191 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Extract Utility from Command Line
To run the extract utility from the command line, do one of the following:

• In the command line, change the current directory to the directory where the extract utility is located.

• Add the directory where the extract utility is located to the PATH variable.

Then you can perform the following actions:

• Run the extract utility in the interactive mode

• Display help information for the utility usage

• Display the list of all VMs in the backup file

• Getting encryption status of a backup file

• Restore all or selected VMs from the backup

Running Extract Utility in Interactive Mode


This command runs the extract utility in the interactive mode.

Syntax

extract.exe [-password backupkey] [pathtobackup]

Parameters

P a rameter Description Required/Optional

p a ssword Password for the encrypted backup file. Required for


encrypted backup
files

p a thtobackup Path to the backup file from which machines must be restored. Optional

Example
This command validates an encrypted backup file.

extract.exe -password "standard 1" "C:/Backup/Single/Backup Job Single Storage


D2022-10-03T132735_1E50.vbk"

2192 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Displaying Help Information for Utility Usage
This command prints all variants of the extract utility usage along with required and optional parameters.

Syntax

extract.exe -help

Displaying List of Machines in Backup


This command displays the list of all machines in the backup file from which you want to perform restore.

Syntax

extract.exe -dir [-vm vmname] [-host hostname] [-password backupkey] pathtoback


up

Parameters

P a rameter Description Required/Optional

Name of the machine that you want to restore. Use this


vm Optional
parameter to filter machines in the backup.

Name of the host on which the initial machine resides.


Specify this parameter to filter machines that have the
host same name but reside on different hosts. Optional
Note: This parameter must be specified if the vm
parameter is used.

Required for encrypted


p a ssword Password for the encrypted backup file.
backup files

Path to the backup file from which the machine must be


p a thtobackup Required
restored.

Getting Encryption Status of Backup File


This command gets the encryption status of the backup file: encrypted or not encrypted.

2193 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Syntax

extract.exe –getEncryptionStatus pathtobackup

Parameters

P a rameter Description Required/Optional

p a thtobackup Path to the backup file from which the machine must be restored. Required

Restoring VMs from Backup


This command restores data for all machines or for the selected machine from the backup file.

Syntax

extract.exe -restore [-vm vmname] [-host hostname] [-password backupkey] pathto


backup [outputdir] [-log]

Parameters

P a rameter Description Required/Optional

Name of the machine that you want to restore. Use this


parameter to filter machines in the backup. If you want to
vm Optional
restore all machines from the backup file, do not specify this
parameter.

Name of the host on which the initial machine resides. Specify


this parameter to filter machines that have the same name but
host reside on different hosts. Optional
Note: This parameter must be specified if the vm parameter is
used.

Path to the backup file from which the machine must be


p a thtobackup Required
restored.

Required for
p a ssword Password for the encrypted backup file. encrypted backup
files

2194 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required/Optional

Path to the directory to which machine data must be restored.


outp utdir If this parameter is not specified, the machine will be restored Optional
to the current directory.

SwitchParameter. Enables log creation. The log file will be


log Optional
created in the current directory.

Example
This command restores winsrv29 machine from an encrypted backup file to the C:/Backup directory.

extract.exe -restore -vm winsrv29 -password "standard 1" "C:/Backup/Single/Bac


kup Job Single StorageD2022-10-03T132735_1E50.vbk" C:/backup

2195 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Configuration Database Connection
Utility
Veeam Backup & Replication comes with the Veeam.Backup.DBConfig.exe utility that allows you to manage
connection settings for Veeam Backup & Replication and Veeam Backup Enterprise Manager configuration
database. Using this utility, you can:

• Connect to a different database on the same or another Microsoft SQL Server or PostgreSQL instance. If
you specify a database that does not exist yet, it will be created on the selected server.

• Change authentication method for database connection. Possible methods are Microsoft Windows
authentication and Microsoft SQL Server or PostgreSQL native authentication.

NOTE

Consider the following:

• The Veeam.Backup.DBConfig.exe utility supports only connection to configuration databases of


the current version.
• The Veeam.Backup.DBConfig.exe utility is shared between Veeam Backup & Replication and
Veeam Backup Enterprise Manager. If they are installed on the same machine, make sure these
products are of the same version.

2196 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Veeam.Backup.DBConfig.exe Utility
You can launch the Veeam.Backup.DBConfig.exe utility from the Sta rt menu by clicking Configuration
Da tabase Connection Settings.

Alternatively, you can use the Veeam.Backup.DBConfig.exe file located in the installation folder. By
default, the path to the folder is the following: %PROGRAMFILES%\Common Files\Veeam\Backup and
Replication\DBConfig

To run the utility, you must have administrative rights on the local machine, as long as the utility makes changes
to the registry. If prompted at the launch, choose Run a s administrator.

To manage connection settings for Veeam Backup & Replication or Veeam Backup Enterprise Manager
configuration database, use the launched Veeam Backup & Replication Configuration Database Connection
Settings wizard.

2197 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 1. Select Product
At the P roduct step of the wizard, select the database whose settings you want to configure.

The utility detects what server is installed on the local machine (backup server, Veeam Backup Enterprise
Manager server or both) and displays available products for your choice. If Veeam Backup Enterprise Manager is
not installed on the local machine, you will only have an opportunity to change Veeam Backup & Replication
database settings (and vice versa). In this case, the P roduct step of the wizard will be skipped.

2198 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 2. Specify Connection Settings
At the Connection Settings step of the wizard, provide the connection settings for the selected database.

For Microsoft SQL Server:

1. Specify the Microsoft SQL Server database engine.

2. Specify an instance and a database name to which you want the Veeam Backup & Replication installation
to connect in localhost\instanceName format.

Both local and remote Microsoft SQL Server instances are supported. Instances available on the network
are shown in the Instance name list. If necessary, click Refresh to get the latest information.

If a database with the specified name does not exist on the selected instance, it will be created anew.

NOTE

If you change the database to which Veeam Backup & Replication must be connected, make sure that
the database to which Veeam Backup & Replication is currently connected is available. If not, you
must stop the Veeam Backup Service on the machine where Veeam Backup & Replication is installed.

3. Select the authentication method that will be used for da tabase connection.

o If you plan to use the Microsoft Windows authentication, consider that the current service account
will be used (that is, the account under which the Veeam Backup Service is running).

o If you plan to use the Microsoft SQL Server native authentication, provide a login name and a
password. To view the entered password, click and hold the eye icon on the right of the P a ssword
field.

IMP ORTANT

When you migrate the configuration database to another server, you must use the Microsoft SQL Server
credentials that have CREATE ANY DATABASE permission on the target Microsoft SQL Server. For details,
see Microsoft Docs.

After database creation this account automatically gets a db_owner role and can perform all operations
with the database. If the current account does not have this permission, a Database Administrator may
create an empty database in advance and grant the db_owner role to the account that will be used for
migration of the configuration database.

2199 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
For PostgreSQL:

1. Specify the PostgreSQL database engine.

2. Specify an instance and a database name to which you want the Veeam Backup & Replication installation
to connect in localhost:instancePort format.

Both local and remote PostgreSQL instances are supported. If a database with the specifie d name does not
exist on the selected PostgreSQL instance, it will be created anew.

NOTE

If you change the database to which Veeam Backup & Replication must be connected, make sure that
the database to which Veeam Backup & Replication is currently connected is available. If not, you
must stop the Veeam Backup Service on the machine where Veeam Backup & Replication is installed.

3. Select the authentication method that will be used for database connection:

o If you plan to use the Microsoft Windows authentication, consider that the current service account
will be used (that is, the account under which the Veeam Backup Service is running).

2200 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
o If you plan to use the PostgreSQL native authentication, provide a login name and a password. To
view the entered password, click and hold the eye icon on the right of the P a ssword field.

2201 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 3. Apply Connection Settings
Before proceeding, the utility validates the specified settings to make sure that the user account has enough
privileges to access the database.

• If you have selected the Microsoft Windows authentication method, the utility will check the privileges of
the current user account (that is, the account under which the utility is running) to connect to specified
Microsoft SQL Server.

• If you have selected the Microsoft SQL Server or the PostgreSQL native authentication method, the utility
will check the privileges of the account you have specified.

To ensure that these accounts (as well as the account under which the Veeam Backup Service is r unning) have
sufficient privileges for database access, you can contact your database administrator. Refer to the list of
required permissions for Veeam Backup & Replication for detailed information.

For the new settings to be applied, the utility needs to stop Veeam Backup & Replication services and jobs that
are currently running. Before proceeding to the Ap p ly step, you must confirm the operation. After you confirm
the operation by clicking Y es , Veeam Backup & Replication will force services and jobs to stop, and will apply
database connection settings. For example, if you are configuring Veeam Backup & Replication database
settings, the following prompt will be displayed.

2202 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Wait for the operation to complete and click Nex t to proceed to the Summary step of the wizard. Previously
stopped services will be started again at this moment.

2203 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Step 4. Finish Working with Wizard
At the Summary step of the wizard, view the information about the changes in database connection settings. I f
you were configuring Veeam Backup & Replication database settings and you want the Veeam backup
management console to be opened automatically after you finish working with the wizard, select the Sta rt the
p roduct automatically check box.

NOTE

The Sta rt the product automatically option is not available for Veeam Backup Enterprise Manager.

2204 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup Validator
Veeam Backup Validator is an utility that verifies the integrity of a backup file without extracting VM data.
Veeam Backup Validator is a command-prompt CRC check utility that tests a backup at the file level. You may
need this utility to check whether backup files were damaged: for example, after hardware failures occurred in a
backup storage side or if backup files were transferred over network .

For integrity validation, Veeam Backup Validator uses the checksum algorithm. When
Veeam Backup & Replication creates a backup of a VM, it calculates a checksum for every data block in the
backup file and attaches these checksums to data blocks. Veeam Ba ckup Validator recalculates checksums for
data blocks and compares them against the initial checksum values. If the results match, the backup file is
viable.

2205 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Veeam Backup Validator
Veeam Backup Validator is located on the backup server in the installation folder of Veeam Backup & Replication
— by default, %ProgramFiles%\Veeam\Backup and
Replication\Backup\Veeam.Backup.Validator.exe. If the default path was changed, you can find the
actual path in the following registry value: [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and
Replication] CorePath.

To run the utility, open the command prompt on the backup server and change the current folder to the folder
where Veeam Backup Validator is located.

IMP ORTANT

Consider the following:

• To run Veeam Backup Validator, you must use an account with administrative rights on the local
machine. Also, you must disable multi-factor authentication (MFA) for this account. For more
information, see Disabling MFA for Service Accounts.
• You cannot use Veeam Backup Validator to verify integrity of NAS backups.
• You cannot use Veeam Backup Validator to verify integrity of backups created in Veeam Cloud
Connect repositories. For more information on Veeam Cloud Connect repositories, see the Cloud
Repository section in the Veeam Cloud Connect Guide.
• The cloud provider can verify integrity of tenant backups only by using the /file parameter and only
if the backup is not encrypted. They cannot verify encrypted backups and they cannot verify backups
by using other parameters.
• [For backups stored in scale-out backup repositories] Veeam Backup Validator can validate only
backups stored in the performance tier which consists of backup repositories (except object storage
repositories). Make sure that incremental and full backup files are located on the same extent.

Syntax
Veeam Backup Validator provides parameter sets that allow you to:

• Display Veeam Backup Validator help information.

Veeam.Backup.Validator /?

• Validate integrity of the content of all VMs or selected VMs in the specified backup.

Veeam.Backup.Validator.exe /backup:backupname|backupid [/vmname:vmname] [/


point:pointid] [/date:pointdate] [/time:pointtime] [/silence] [/skip] [/re
port:reportpath [/format:xml|html]]

• Validate integrity of the VM content in the specified backup file.

Veeam.Backup.Validator.exe /file:backupfile{1..*} [/username:username /pas


sword:password] [/vmname:vmname]
[/silence] [/skip] [/report:reportpath [/format:xml|html]]

2206 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Parameters

P a rameter Description Required/Optio P a ramet Notes


na l er Ty pe

/b a ckup: Specifies a Required String Consider the following:


b a ckupname| name or an
• For a backup copy job in the
b a ckupID ID* of a
backup or immediate mode, you must specify
backup copy the name of its child job — task
job that you that copies backup job added as a
want to
source to the backup copy job. For
validate.
example, if the "My Copy" backup
copy job copies "Daily Backup"
backup job, then you must set the
parameter value to "My Copy\Daily
Backup".
If you want to validate the whole
backup copy job, you must run the
utility for each child job.
• To validate per-machine backups
with separate metadata files, you
must specify the child backup
name — backup of a specific VM.
To get the child backup name, use
the following PowerShell
commands:

$backup = Get-VBRBackup -N
ame "<backup_name>"
$child_backups = $backup.F
indChildBackups()
$first_child_backup_name =
$child_backups[0].Name

2207 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required/Optio P a ramet Notes
na l er Ty pe

/file:backupfile{1 Specifies a Required String Consider the following:


..*} backup file
• To validate an incremental backup
(VBM, VBK,
VIB, VRB) to file, you must specify the whole
be validated. backup chain starting from the VBK
file up to the required incremental
file. Each backup file must be
specified using a separate /file
parameter.
• If the file is located on a network
share, make sure you specify a full
path, for example:
\\172.16.16.198\TestShare\
Empty VM encryptedD2017-
09-22T172639.vbk.
• Mapped network drives are not
supported. For example, you
cannot specify z:
\\172.16.16.198\TestShare.

/username: To access files Required for String If you want to validate files located on
username on network network share different shares, make sure this account
/p a ssword: shares. has access rights to all these shares.
p a ssword Specifies
account
credentials
that the utility
uses to access
network
shares.

/vmname:vmna Specifies a Optional String If not specified, Veeam Backup Validator


me name of the will check all VMs in the backup file.
VM in the
backup file to
be validated.

2208 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required/Optio P a ramet Notes
na l er Ty pe

/p oint:pointID Specifies an Optional String If not specified, Veeam Backup Validator


ID* of the will verify the latest restore point, that is,
restore point all backup files the restore point consists
to be of.
validated.

Note: You
must provide
this parameter
after the
/backup
parameter.

To get the
restore point
ID, run the
Get-
VBRRestorePo
int cmdlet and
retrieve the
PointID
property.

/d a te:pointdate Specifies the Optional Date Make sure to specify the date in the same
date when the format as used on the Veeam Backup
validated server. For example:
restore point
• For the mm/dd/yyyy format,
was created.
specify 08.30.2012.
• For the dd/mm/yyyy format,
specify 30.08.2012.

/time:pointtime Specifies the Optional Time —


approximate
time when the
validated
restore point
was created.

/silence Defines Optional Boolean —


whether to
run validation
in the silence
mode.

2209 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
P a rameter Description Required/Optio P a ramet Notes
na l er Ty pe

/sk ip Defines Optional Boolean In the vmname parameter, list all VMs
whether to that you want to skip.
skip from
processing
VMs listed in
the vmname
parameter.

/report: Specifies a full Optional String Consider the following:


rep ortpath path of a file
• You must specify the full file path,
[/format:xml| where you
html] want to store for example,
a report on "C:\temp\validator-
validation report.html".
results. The
• Supported report formats are
utility will
generate a HTML and XML.
report on
validation
results and
store it at the
specified
path.

* You can get IDs of backup jobs and restore points from the Veeam Backup & Replication database using scripts or
Management Studio.

Example 1
This command validates the winsrv29 VM in the incremental backup file and writes the results in the
report.html file.

Veeam.Backup.Validator.exe /file:"C:\Backup\Backup Job Single Storage\Backup J


ob Single StorageD2022-10-03T132735_1E50.vbk" /file:"C:\Backup\Backup Job Sing
le Storage\Backup Job Single StorageD2022-10-28T122338_3EE4.vib" /vmname:winsr
v29 /report:"C:\report.html"

2210 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Example 2
This command validates the exch01 VM in the Exchange Backup Job file.

Veeam.Backup.Validator /backup:"Exchange Backup Job" /vmname:exch01

2211 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Example 3
This command validates all VMs in the Exchange Backup Job file created on December 18, 2018 around
12:00 AM.

Veeam.Backup.Validator /backup:"Exchange Backup Job"/date:12.18.2018 /time:12:


00

2212 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
2213 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup Configuration Tool
Veeam Backup & Replication comes with the Veeam.Backup.Configuration.Tool.exe utility that allows
you to manage BCO files. BCO files are backup files that contain backups of configuration databases.
Veeam Backup & Replication creates these files when it performs configuration backup. For more information on
configuration backup, see Configuration Backup and Restore.

You can use the Veeam Backup Configuration tool in the following scenarios:

• You do not have information on the BCO file version, parameters and attributes. In this case, you can use
the tool to get details on the BCO file version.

• Veeam Backup & Replication is not able to restore a configuration database using a specific BCO file. In
this case, you can use the tool to check if the BCO file is corrupted. The Veeam Backup Configuration tool
will perform the cyclic redundancy check (CRC) and will verify that the encrypted file is decrypted
properly.

• You do not have information on the specific configuration database. In this case, you can get details on its
version and also use the tool to back up this database.

• Your backup server is no longer available, but your configuration database is still up and running. You can
use the tool to create a backup of the configuration database and migrate this database to another backup
server. In this case, the tool produces the same configuration backup, as Veeam Backup & Replication
creates when you run the configuration backup job.

NOTE

If you back up the configuration database using the Veeam Backup Configuration tool, you will not
be able to choose the backup repository in which the configuration backup must be stored and the
necessary retention settings. Veeam Backup & Replication will keep last 10 restore points of the
configuration backup in the default backup repository. If you want to change these setting, see the
Scheduling Configuration Backups section.

2214 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Using Veeam Backup Configuration Tool
The Veeam Backup Configuration tool is located on the backup server in the installation folder of
Veeam Backup & Replication. The default path is %ProgramFiles%\Veeam\Backup and
Replication\Backup\Veeam.Backup.Configuration.Tool.exe. If the default path was changed, you
can find the actual path in the following registry value: [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam
Backup and Replication] CorePath.

To run the tool, open the command prompt on the backup server and change the current folder to the folder
where Veeam Backup Configuration tool is located.

IMP ORTANT

To run the Veeam Backup Configuration tool, you must use an account with administrative rights on the
local machine.

Syntax
The Veeam Backup Configuration tool provides parameter sets that allow y ou to:

• Display help information for the Veeam Backup Configuration tool.

Veeam.Backup.Configuration.Tool /?

• Analyze a configuration backup file.

Veeam.Backup.Configuration.Tool /file:value /analyzefile

• Check whether a configuration backup is not corrupted.

Veeam.Backup.Configuration.Tool /file:value /checkfile

• Analyze a configuration database.

Veeam.Backup.Configuration.Tool /analyzedatabase [/servername:value] [/ins


tancename:value] [/serverport:value] [/initialcatalog:value] [/login:value
][/password:value]

• Back up a configuration database.

Veeam.Backup.Configuration.Tool /file:value /backupdatabase [/servername:v


alue][/instancename:value] [/serverport:value] [/initialcatalog:value] [/l
ogin:value] [/password:value] [/cryptfile]

2215 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Parameters

P a rameter Description

/file:value Specifies a path to the configuration backup file.

/a nalyzefile Analyzes a configuration backup file.

/checkfile Checks whether the configuration backup is not


corrupted.

/a nalyzedatabase Analyzes a configuration database.

/b a ckupdatabase Backs up a configuration database.

/d a tabaseengine Specifies a database engine

/servername:value Specifies a name of a SQL server.

/instancename:value Specifies a name of a SQL instance.

/serverport:value Specifies a port number of a SQL server. The tool will


use this port to access the SQL server.

/initialcatalog:value Specifies a name of a SQL database.

/log in:value Specifies a username that the tool will use to


authenticate against a SQL server.

/p a ssword:value Specifies a password that the tool will use to


authenticate against a SQL server.

/cryptfile Defines that the tool will encrypt a configuration


backup file.

/verbose Enables verbose output mode.

2216 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Examples
Example 1
This example shows how to analyze the 193022052014.bco configuration backup file. After you start the
command, the command prompt will return the output.

Veeam.Backup.Configuration.Tool.exe /file:"c:\my files\193022052014.bco"


/analyzefile /verbose

Example 2
This example shows how to analyze the 193022052014.bco configuration backup file and back up the
configuration database. The command will contain the following settings of the configuration database:

• The configuration database is located at the WIN2008R2 SQL server.

• The name of the SQL instance is VeeamSql2008.

• The name of the SQL database is VeeamBackup.

Veeam.Backup.Configuration.Tool.exe /file:c:\backups\091323052014.bco
/backupdatabase /servername:WIN2008R2 /instancename:VeeamSql2008
/initialcatalog:VeeamBackup

2217 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Veeam Backup & Replication Events
This section provides information about events written by Veeam Backup & Replication to Microsoft Windows
Event Log on the backup server.

• General

• License

• Security

• Servers and Hosts

• Repositories

• Proxy Server

• WAN Accelerator

• Jobs

• NAS Backup

• Restore

• SureBackup

• Tape

• Agents

2218 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
General
The following table lists Veeam Backup & Replication events related to the general settings.

E vent Message Summary Message Details Severity


ID

31000 General options modified Backup server general options have been Info, Warning,
changed. Error

31100 Network traffic rules Backup server global network traffic rules have Info, Warning,
updated been changed. Error

31500 Configuration backup job Configuration job has been modified. Info, Warning,
updated Error

40100 Shell started The Veeam Backup & Replication console has Info
been launched.

40101 Shell closed The Veeam Backup & Replication console has Info
been closed.

40300 Logs export session finished Support logs export has been completed. Result: Info
<State>.

40400 Global exclusions added <N> objects have been added into the global Info
exclusions list.

40500 Global exclusions deleted <N> objects have been removed from the global Info
exclusions list.

40600 Global exclusions changed Global exclusions list has been modified. Info

40700 Configuration backup Configuration backup has been completed. Info


session finished Result: <State>.

40800 Configuration restore Configuration restore has been performed. Info


session finished

40900 Location added Location <Location name> has been added. Info

40901 Location modified Location <Location name> has been modified. Info

2219 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

40902 Location removed Location <Location name> has been removed. Info

40903 Object location changed Object location has been changed. Info

2220 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
License
The following table lists Veeam Backup & Replication events related to the product license usage.

E vent Message Message Details Severity


ID Summary

24010 License installed <License type> License key for Veeam Backup & Replication Info
<Edition> has been installed.

24020 License expiring <License type> License key for Veeam Backup & Replication Warning
<Edition> is about to expire in <N> days.

24022 License <License type> Evaluation license key for Warning


evaluation Veeam Backup & Replication <Edition> is about to expire in <N>
expiring days.

24030 License expired <License type> License key for Veeam Backup & Replication Error
<Edition> has expired.

24040 License support Support contract for Veeam Backup & Replication is about to Warning
expiring expire in <N> days.

24050 License support Support contract for Veeam Backup & Replication has expired. Error
expired Contact Veeam sales representative to renew your support
contract.

24060 License exceeded License exceeded. Error

24070 License grace License grace period entered. Info


period entered

24080 Part of merged <License type> license that was a part of the merged Info
license deleted Veeam Backup & Replication license has been removed.

41300 License report Product license consumption report was created by <Initiator Info
name>.

41301 License auto Update license automatically was <Enabled/Disabled> by Info


update <Initiator name>.

41302 License Allow unlicensed agent to consume instances was Info


unlicensed agent <Enabled/Disabled> by <Initiator name>.

2221 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Message Details Severity
ID Summary

41303 License revoke License revocation was initiated for objects <Object names> by Info
<Initiator name>.

41304 License remove License removal was initiated for objects <Object names> by Info
<Initiator name>.

41305 License assign <License mode> license was assigned to objects <Object Info
names> by <Initiator name>.

2222 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Security
The following table lists Veeam Backup & Replication events related to security.

E vent Message Summary Message Details Severity


ID

25300 Credentials record Credentials <Credentials> have been added. Info,


added Warning,
Error

25400 Credentials record Credentials <Credentials> have been updated. Info,


updated Warning,
Error

25500 Credentials record Credentials <Credentials> have been deleted. Info,


deleted Warning,
Error

31210 User or group failed to Failed to add a user or a group: <User name/Group Info
add name>.

31600 Password added to the Encryption password <Password ID> has been added. Info,
password manager Warning,
Error

31700 Password stored in the Encryption password <Password ID> has been Info,
password manager changed. Warning,
changed Error

31800 Encryption password Encryption password <Password ID> has been deleted. Info,
deleted Warning,
Error

31900 SSH credentials SSH options for credentials <Credentials> have been Info,
updated updated. Warning,
Error

40200 Global MFA enabled Multi-factor authentication has been enabled by Info
<Initiator name>.

40201 Global MFA disabled Multi-factor authentication has been disabled by Info
<Initiator name>.

40202 MFA reset user token Multi-factor authentication token has been reset for Info
<User name> by <Initiator name>.

2223 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

40203 User MFA enabled Multi-factor authentication has been disabled for <User Info
name> by <Initiator name>.

40204 User MFA disabled Multi-factor authentication token has been disabled for Info
<User name> by <Initiator name>.

40205 Invalid MFA code Invalid MFA code has been entered for <User name>. Info

40206 User blocked <User name> has been locked out by entering too many Info
invalid MFA codes.

40903 Object location Object location has been changed. Info


changed

41600 Malware activity Potential malware activity <Activity name> has been Warning
detected detected for <Restore point ID> <Machine name>
by <User name>. Rule name: <Rule name>.

41610 Malware detection Malware detection event has been resolved for Info
event resolved <Restore point ID> by <User name>. False
positive: <State>.

42200 Malware detection Malware detection session has been started. Info
session started

42210 Malware detection Malware detection session has been finished with Info,
session finished <State>. Warning,
Error

42220 Restore point marked Restore point has been marked as infected by <User Info
as infected name>.

42230 Restore point marked Restore point has been marked as clean by <User Info
as clean name>.

42260 Objects added to the <N> objects have been added to the malware exclusions Info
malware exclusions list list.

42270 Objects removed from <N> objects have been removed from the malware Info
the malware exclusions exclusions list.
list

2224 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

42280 Malware exclusions list Malware exclusions list has been modified. Info
modified

42290 Malware detection Malware detection settings have been changed. Info
settings changed

42300 KMS added KMS server <Host name> has been added. Info

42301 KMS deleted KMS server <Host name> has been deleted. Info

42302 KMS updated KMS server <Host name> settings has been changed. Info

42400 Four-eyes authorization Four-eyes authorization has been enabled by Info


enabled <Initiator name>.

42401 Four-eyes authorization Four-eyes authorization has been disabled by Info


disabled <Initiator name>.

42402 Four-eyes authorization <Operation name> has been initiated by <Initiator Info
request initiated name> and requires an additional approval.

42403 Four-eyes authorization <Operation name> initiated by <Initiator name> Info


request approved has been approved by <User name>.

42404 Four-eyes authorization <Operation name> initiated by <Initiator name> Info


request rejected has been rejected by <User name>.

42405 Four-eyes authorization <Operation name> initiated by <Initiator name> Info


request expired has expired while waiting for additional approval and was
auto-rejected.

42500 KMS key rotation KMS key rotation has been completed with <State>. Info
finished

2225 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Servers and Hosts
The following table lists Veeam Backup & Replication events related to virtualization servers and hosts.

E vent Message Summary Message Details Severity


ID

25600 Host added New hypervisor host has been added. Info, Warning,
Error

25700 Host deleted Hypervisor host has been deleted. Info, Warning,
Error

25800 Host updated Hypervisor host has been updated. Info, Warning,
Error

28300 Host added Host <Host name> (<Host type>) has been created. Info, Warning,
Error

28400 Host updated Host <Host name> (<Host type>) has been Info, Warning,
modified. Error

28500 Host deleted Host <Host name> (<Host type>) has been deleted. Info, Warning,
Error

32900 Component installed Component <Component name> on host <Host Info, Warning,
or updated name> has been installed or upgraded. Error

41400 Storage added Storage <Host name> has been created. Info

41401 Storage modified Storage <Host name> has been modified. Info

41402 Storage deleted Storage <Host name> has been deleted. Info

2226 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Repositories
The following table lists Veeam Backup & Replication events related to repositories: backup repositories, scale-
out repositories and so on.

E vent Message Summary Message Details Severity


ID

21220 Repository server Connection to backup repository <Repository Info


established connection name> has been restored.

21224 Repository server lost Backup server has lost connection to backup Error
connection repository <Repository name>.

26500 Maintenance mode of Extent <ID> Maintenance mode has been changed. Info
scale-out backup New mode is <New status>.
repository changed

28000 Repository created Backup repository <Repository name> Info


(<Repository type>) has been created.

28100 Repository modified Backup repository <Repository name> Info


(<Repository type>) has been modified.

28200 Repository deleted Backup repository <Repository name> Info


(<Repository type>) has been deleted.

29700 Object storage repository Object storage repository <Repository name> has Info
created been created.

29800 Object storage repository Object storage repository <Repository name> has Info
modified been modified.

29900 Object storage repository Object storage repository <Repository name> has Info
deleted been deleted.

30000 Scale-out backup Scale-out backup repository <Repository name> Info


repository created has been created.

30100 Scale-out backup Scale-out backup repository <Repository name> Info


repository modified has been modified.

30200 Scale-out backup Scale-out backup repository <Repository name> Info


repository deleted has been deleted.

2227 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

32000 External repository External repository <Repository name> Info


created (<Repository type>) has been created.

32100 External repository External repository <Repository name> Info


modified (<Repository type>) has been modified.

32200 External repository External repository <Repository name> Info


deleted (<Repository type>) has been deleted.

40002 Management session The storage management session for repository Info,
finished <Repository name> has finished: <State>. Warning,
Error
Repository name: <Repository name>

Job type: <Offload/Archiving/Download>

Session result: <Successful/Warning/Failed>

2228 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Proxy Server
The following table lists Veeam Backup & Replication events related to backup proxy servers.

E vent Message Summary Message Details Severity


ID

21210 Proxy server established Connection to backup proxy <Proxy name> has been Info
connection restored.

21214 Proxy server lost connection Backup server has lost connection to backup proxy Error
<Proxy name>.

27700 Backup proxy created Backup proxy <Proxy name> (<Proxy type>) has Info
been created.

27800 Backup proxy modified Backup proxy <Proxy name> (<Proxy type>) has Info
been modified.

27900 Backup proxy deleted Backup proxy <Proxy name> (<Proxy type>) has Info
been deleted.

2229 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
WAN Accelerator
The following table lists Veeam Backup & Replication events related to WAN accelerators.

E vent Message Summary Message Details Severity


ID

21230 WAN accelerator established Connection to WAN accelerator <WAN name> has Info
connection been restored.

21234 WAN accelerator lost Backup server has lost connection to WAN Error
connection accelerator <WAN name>.

27100 WAN accelerator created WAN accelerator <WAN name> has been created. Info

27200 WAN accelerator modified WAN Accelerator <WAN name> has been modified. Info

27300 WAN accelerator deleted WAN Accelerator <WAN name> has been deleted. Info

33000 WAN accelerator cache Cache of WAN accelerator <WAN name> has been Info
populated populated.

33001 WAN accelerator cache cleared Cache of WAN accelerator <WAN name> has been Info
cleared.

2230 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Jobs
The following table lists Veeam Backup & Replication events related to the Veeam Backup & Replication jobs
(including backup, replication, backup copy and file copy).

E vent Message Summary Message Details Severity Source


ID

110 Backup job started <Job type> job <Job Info Backup
name> has been
started.

150 Backup task finished VM <Task name> task Info Backup, Replication,
has finished with SureBackup
<State>.

190 Backup job finished The <Job type> job Info, Backup
<Job name> has Warning,
finished with Error
<State>.

410 Backup copy job started <Job type> job <Job Info Backup copy
name> has been
started.

450 Backup copy task finished VM <Task name> task Info, Backup copy
has finished with Warning,
<State>. Error

490 Backup copy job finished The <Job type> job Info, Backup copy
<Job name> has Warning,
finished with Error
<State>.

510 File copy job started <Job type> job <Job Info File copy
name> has been
started.

590 File copy job finished The <Job type> job Info, File copy
<Job name> has Warning,
finished with Error
<State>.

710 Veeam Agent backup job Agent Backup job Info Veeam Agent backup
started <Job name> has been
started.

2231 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity Source
ID

790 Veeam Agent backup job Agent Backup job Info, Veeam Agent backup
finished <Job name> finished Warning,
with <State>. Job Error
details:
<Description>.

810 Rescan job started (Veeam Rescan job <Job Info Rescan job (Veeam Agent)
Agent) name> has been
started.

890 Rescan job finished (Veeam Rescan job <Job Info, Rescan job (Veeam Agent)
Agent) name> has been Warning,
finished with Error
<State>. Job details:
<Description>.

10010 Restore point created VM <VM name> Info


restore point has been
created.

10050 Restore point removed Restore point for VM Info


<VM name> has been
removed according to
the configured
retention policy.

10090 Restore point updated VM <VM name> Info


restore point has been
modified.

23050 Job modified Job <Job name> has Info,


been modified. Warning,
Error

23090 Job deleted The <Job type> job Info Backup, Replication, Backup
<Job name> has been copy
deleted.

23110 Job objects added <N> objects have been Info Backup, Replication, Backup
created for <Job copy
name>.

2232 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity Source
ID

32120 Job objects deleted <N> objects have been Info Backup, Replication, Backup
deleted for <Job copy
name>.

23130 Job objects modified <N> objects have been Info Backup, Replication, Backup
modified for <Job copy
name>.

23410 Second destination job <Job name> job has Info Backup copy
assigned been assigned as
secondary destination
for <N> jobs.

23420 Second destination job <Job name> job has Info Backup copy
removed been removed as
secondary destination
for <N> jobs.

25900 Failover plan created New failover plan has Info Replication
been created.

26000 Failover plan updated Failover plan has been Info Replication
updated.

26100 Failover plan deleted Failover plan has been Info Replication
deleted.

26600 Failover plan started Failover plan was Info Replication


started.

26700 Failover plan stopped Failover plan was Info Replication


stopped.

40002 Offload/Download/Archiving The storage Info, Offload/Download/Archiving


job finished management session Warning, job
for repository Error
<Repository name>
has finished: <State>.

41200 Detach job Detach backup from Info Backup move/copy


job <Source name>
has been initiated by
<Initiator name>.

2233 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity Source
ID

41201 Copy backup Copy backups from Info Backup copy


<Source name> to
<Target name> has
been initiated by
<Initiator name>.

41202 Move backup Move backups from Info Backup move


<Source name> to
<Target name> has
been initiated by
<Initiator name>.

2234 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
NAS Backup
The following table lists Veeam Backup & Replication events related to NAS backup functionality.

E vent Message Summary Message Details Severity


ID

151 Task finished Source <Task name> task has finished with <State> state. Info

451 Copy task finished Source <Source name> task has finished with <State> Info
state.

600 Migration job started <Job type> job has been started by user Info
<Domain>\<User name>.

601 Migration switchover <Job type> switchover job has been started by user Info
job started <Domain>\<User name>.

610 Migration job finished <Job type> job finished with <State>. Info

28900 File share created File share <Server name> (<Server type>) has been Info
created.

28910 File share modified File share <Server name> (<Server type>) has been Info
modified.

28920 File share deleted File share <Server name> (<Server type>) has been Info
deleted.

28930 File server created File server <Server name> has been created. Info

28940 File server modified File server <Server name> has been modified. Info

28950 File server deleted File server <Server name> has been deleted. Info

41000 NAS backup download NAS backup metadata download has been started for backup Info
meta started <Backup name> by <User name>.

41001 NAS backup download NAS backup metadata download for backup <Backup Info
meta finished name> has been finished. Result: <State>.

2235 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Restore
The following table lists Veeam Backup & Replication events related to data recovery.

E vent Message Summary Message Details Severity


ID

210 Restore session started Restore session has been initiated by <User Info
name>.

251 Restore HV task Restore for <Object name> has finished with Info, Warning,
finished <State> state Error

290 Restore session finished The restore session has finished with <State> Info, Warning,
state. Error

40210 Restore session started <Session type> session has been initiated by Info
(new) <Initiator name>.

40290 Restore session finished The <Session type> session has finished with Info, Warning,
(new) <State> state + info. Error

41500 Restore point mounted Backup has been mounted. MountID: <ID>. Info

41510 Restore point Backup has been unmounted. MountID: <ID>. Info
unmounted

2236 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
SureBackup
The following table lists Veeam Backup & Replication events related to SureBackup functionality.

E vent Message Summary Message Details Severity


ID

310 SureBackup job started <Job type> job <Job name> has been Info
started.

360 SureBackup HV verification VM <VM name> verification task has finished Info, Warning,
task finished with <State> state. Error

361 SureBackup HV validation VM <VM name> validation task has finished Info, Warning,
task finished with <State> state. Error

390 SureBackup job finished The <Job type> job <Job name> has finished Info, Warning,
with <State> state. Error

23210 SureBackup job created The SureBackup job <Job name> has been Info
created.

23220 SureBackup job modified The SureBackup job <Job name> has been Info
modified.

23230 SureBackup job deleted The SureBackup job <Job name> has been Info
deleted.

23310 SureBackup objects added <N> objects have been created for <Job Info
name>.

23320 SureBackup objects deleted <N> objects have been deleted from <Job Info
name>.

30300 Application group added Application group <Group name> has been Info
added.

30400 Application group modified Application group <Group name> has been Info
modified.

30500 Application group deleted Application group <Group name> has been Info
deleted.

30600 Virtual lab created Virtual lab <Lab name> has been created. Info

2237 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

30700 Virtual lab modified Virtual lab <Lab name> has been modified. Info

30800 Virtual lab deleted Virtual lab <Lab name> has been deleted. Info

2238 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Tape
The following table lists Veeam Backup & Replication events related to tape archiving.

E vent Message Summary Message Details Severity


ID

114 Tape backup job started <Job type> job <Job name> has been started. Info

115 Tape erase job started <Job type> job <Job name> has been started. Info

116 Tape inventory job started <Job type> job <Job name> has been started. Info

117 Tape catalog job started <Job type> job <Job name> has been started. Info

118 Tape verification job <Job type> job <Job name> has been started. Info
started

119 Tape export job started <Job type> job <Job name> has been started. Info

120 Tape copy job started <Job type> job <Job name> has been started. Info

121 Tape eject job started <Job type> job <Job name> has been started. Info

122 Tape mark as free job <Job type> job <Job name> has been started. Info
started

123 Tape move to media pool <Job type> job <Job name> has been started. Info
job started

124 Tape delete from library <Job type> job <Job name> has been started. Info
job started

125 Tape libraries discover job <Job type> job <Job name> has been started. Info
started

126 Tape import job started <Job type> job <Job name> has been started. Info

194 Tape backup job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

2239 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

195 Tape erase job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

196 Tape inventory job <Job type> job <Job name> has finished with Info, Warning,
finished <State> state. Error

197 Tape catalog job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

198 Tape verification job <Job type> job <Job name> has finished with Info, Warning,
finished <State> state. Error

199 Tape export job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

200 Tape copy job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

203 Tape eject job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

204 Tape mark as free job <Job type> job <Job name> has finished with Info, Warning,
finished <State> state. Error

205 Tape move to media pool <Job type> job <Job name> has finished with Info, Warning,
job finished <State> state. Error

206 Tape delete from library <Job type> job <Job name> has finished with Info, Warning,
job finished <State> state. Error

207 Tape libraries discover job <Job type> job <Job name> has finished with Info, Warning,
finished <State> state. Error

208 Tape import job finished <Job type> job <Job name> has finished with Info, Warning,
<State> state. Error

10014 Tape restore point created VM <Task name> restore point has been Info
offloaded to the tape <Barcode>.

20114 Tape updated Tape <Barcode> has been renamed. Info

2240 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

23440 Tape backup job created <Job type> <Job name> has been created. Info

23450 Tape backup job modified <Job type> <Job name> has been modified. Info

23490 Tape backup job deleted <Job type> <Job name> has been deleted. Info

23610 Tape media pool created Tape media pool <Object name> has been Info
created.

23611 Tape media vault created Media vault <Object name> has been created. Info

23612 Tape medium created Tape medium <Object name> has been created. Info

23620 Tape media pool modified Tape media pool <Object name> has been Info
modified.

23621 Tape media vault modified Media vault <Object name> has been modified. Info

23622 Tape medium modified Tape medium <Object name> has been modified. Info

23623 Tape library modified Tape library <Object name> has been modified. Info

23630 Tape media pool deleted Tape media pool <Object name> has been Info
deleted.

23631 Tape media vault deleted Media vault <Object name> has been deleted. Info

23632 Tape medium deleted Tape medium <Object name> has been deleted. Info

23633 Tape library deleted Tape library <Object name> has been deleted. Info

28600 Tape server created Tape server <Server name> has been created. Info

28650 NDMP server added NDMP server <Server name> has been created. Info

28700 Tape server modified Tape server <Server name> has been modified. Info

28750 NDMP server modified NDMP server <Server name> has been modified. Info

2241 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

28800 Tape server deleted Tape server <Server name> has been deleted. Info

2242 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
Agents
The following table lists Veeam Backup & Replication events related to agent management.

E vent Message Summary Message Details Severity


ID

10010 Restore point VM <VM name> restore point has been created. Info
created

10050 Restore point Restore point for VM <VM name> has been removed according Info
removed to the configured retention policy.

23010 Job created The <Job type> job <Job name> has been created. Info

23050 Job modified The <Job type> job <Job name> has been modified. Info,
Warning,
Error

23090 Job deleted The <Job type> job <Job name> has been deleted. Info

29100 Protection group Protection group <Group name> has been added. Info
added

29110 Protection group Protection group <Group name> has been modified. Info
modified

29120 Protection group Protection group <Group name> has been deleted. Info
deleted

29130 Protection group Protection group <Group name> scope has been increased. Info
items added

29140 Protection group Protection group <Group name> scope has been modified. Info
items modified

29150 Protection group Protection group <Group name> scope has been decreased. Info
items removed

36011 EP recovery token Recovery token has been created. Token ID: <ID>, Access list: Info
created <Access list>, Initiator: <Initiator name>, Expiration
Date UTC: <Date>.

2243 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V
E vent Message Summary Message Details Severity
ID

36012 EP recovery token Recovery token has been updated. Token ID: <ID>, Access list: Info
update <Access list>, Initiator: <Initiator name>, Expiration
Date UTC: <Date>.

36013 EP recovery token Recovery token has been removed. Token ID: <ID>, Access list: Info
removed <Access list>, Initiator: <Initiator name>.

36014 EP recovery token Recovery token has been authenticated. Token ID: <ID>, Info
authenticate Access list: <Access list>, Client: <Client>.

36021 EP plugin data Application Backup Policy for <Job name> has been started. Info
policy started

36022 EP plugin data Application Backup Policy job <Job name> finished with Info,
policy finished <Success/Warning/Failed>. Warning,
Error

36023 EP plugin data Backup of <Database path> with <Job name> policy has Info
policy task started been started. Initiator: <Initiator name>.

36024 EP plugin data Backup of <Database path> with <Job name> policy has Info
policy task been completed.
finished

36025 EP plugin log Application Log Policy for <Job name> has been started. Info
policy started

36026 EP plugin log Application Log Policy job <Job name> finished with Info,
policy finished <Success/Warning/Failed>. Warning,
Error

2244 | V eeam Backup & Replication | User Guide for Microsoft Hyper-V

You might also like