Release Notes for HPE XP Plug-In for Veeam Backup & Replication 1.0.66

August 5, 2021, 3:18 pm

≫ Next: Veeam product installer fails with "Failed to execute setup extensions."

≪ Previous: Missing vCenter entries in settings for vCloud Director

KB ID:	4194
Product:	Veeam Backup & Replication 11, Veeam Backup & Replication 10a

Requirements

Before installing HPE XP Plug-In 1.0.66, ensure that you are running Veeam Backup & Replication version 10.0.0.4461 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.

HPE XP Plug-In for Veeam Backup & Replication 1.0.66 supports integration with the following storage systems:

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

Follow detailed instructions on configuring the HPE XP Plug-in and the storage system in the HPE documentation.

Known issues

Mind the following major issues for HPE XP Plug-In for Veeam Backup & Replication 1.0.66. If you experience any issue listed here, contact HPE support directly.

HPE XP Plug-In 1.0.66 does not return information about volumes that are not mounted to a host. To perform a restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.

Freeze-only snapshots are not supported by this plug-in version. If you want to enable VM processing using VMware snapshots, contact Veeam support to change the value of a dedicated registry key.

If you make any changes to host groups/iSCSI targets configuration after at least one restore operation, you must manually restart the Veeam Backup Service. The service restart will refresh the plug-in cache, and the configuration changes will be updated.

After deleting a snapshot, logical device (LDEV) records with the _DEL postfix might remain on the storage until the next storage rescan operation. However, such snapshots can be exported during rescan and displayed in the storage infrastructure UI as regular volumes. To avoid issues, you can manually delete or unexport such snapshots.

If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.

HPE XP Plug-In 1.0.66 does not support backing up of failover clusters using Veeam Agent for Windows.

Veeam Backup Service restart causes subsequent Veeam Agent for Windows job to fail. The issue occurs because the job triggers storage information caching, and it exceeds the VSS freeze timeout.

Download

Download HPE XP Plug-In

MD5: 00f8ad76b59d57903e5b983414404b8f
SHA1: e5fe17bdc3bafb968645bfe21d18c828326f6fae

↧

Veeam product installer fails with "Failed to execute setup extensions."

August 6, 2021, 3:19 pm

≫ Next: Release Notes for Hitachi Plug-In for Veeam Backup & Replication 1.0.66

≪ Previous: Release Notes for HPE XP Plug-In for Veeam Backup & Replication 1.0.66

KB ID:	4195
Product:	Veeam Agent for Microsoft Windows, Veeam ONE, Veeam Backup & Replication, Veeam Service Provider Console

Challenge

When attempting to install or upgrade a Veeam product, the installer fails with the following error:

Failed to execute setup extensions.

Failed to execute setup extensions. example

Cause

This issue is related to security software (antivirus/antimalware) or system hardening on the machine preventing access to or execution of files within the %localappdata%\Temp\ folder.

During the installation process, Veeam installers extract and execute files from the temporary folder.

The issue can be further identified by reviewing the installer log files found in C:\ProgramData\Veeam\Setup.

Log Examples:

Example from BackupSrvLog.log

 
                       Extracting binary 'VmSetupHelpLib.dll' to 'C:\Users\backup\AppData\Local\Temp\a25a751c-1b27-423e-8e46-83be7abbd9f1\VmSetupHelpLib.dll'.
Exception occurred while extracting 'VmSetupHelpLib.dll'. Error code: 32
Exception occurred. Error code: 32
Failed to execute setup extensions. 
                      

Example from VeeamOneAgentSetup.log

 
                       Extracting binary 'Veeam.Setup.OneAgentExtension.dll' to 'C:\Users\backup\AppData\Local\Temp\c530b386-2eda-48d9-940e-71f7f873ac2b\Veeam.Setup.OneAgentExtension.dll'.
Exception occurred while extracting 'Veeam.Setup.OneAgentExtension.dll'. Error code: 5
Exception occurred. Error code: 5
Failed to execute setup extensions. 
                      

Example from VSPC_Server.log

 
                       Extracting binary 'SPPSetupExtensions.dll' to 'C:\Users\backup\AppData\Local\Temp\1f2008f5-c746-42a4-990c-4dc5202e73d5\SPPSetupExtensions.dll'.
Exception occurred while extracting 'SPPSetupExtensions.dll'. Error code: 5
Exception occurred. Error code: 5
Failed to execute setup extensions. 
                      

Solution

If this error occurs while attempting to install a Veeam product, you are advised to review the security software's logs to identify what activity was detected and blocked, and then create appropriate exclusions to prevent installation issues. Alternatively, temporarily disable security software or server hardening until the installation is complete to prevent interactions that may cause the Veeam installer to fail.

Note: Some customers have advised Veeam Support that this issue persists after disabling their third-party security software and that they had to uninstall their security software temporarily.

If neither exclusion, disabling, nor uninstalling third-party security software or server hardening resolves this install issue, collect all logs from %ProgramData%\Veeam\Setup\ and create a Veeam Support case.

More information

Beyond traditional security software, this issue has also been caused by hardening policies configured within File Server Resource Manager.

↧

Release Notes for Hitachi Plug-In for Veeam Backup & Replication 1.0.66

August 9, 2021, 2:19 pm

≫ Next: How to test Exchange Online service connection performance using Microsoft Support and Recovery Assistant

≪ Previous: Veeam product installer fails with "Failed to execute setup extensions."

KB ID:	4191
Product:	Veeam Backup & Replication 11, Veeam Backup & Replication 10a

Requirements

Before installing Hitachi Plug-In, make sure that you are running Veeam Backup & Replication version 10.0.0.4461 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.

Hitachi Plug-In for Veeam Backup & Replication supports integration with the following storage systems:

VSP E590, E790, E990 (93-03-01-60/00 or later),
VSP F350, F370, F700, F900 (88-07-01-x0/00 or later),
VSP G350, G370, G700, G900 (88-07-01-x0/00 or later),
VSP 5000 series (90-05-01-00/00 or later)

Follow detailed instructions on configuring the Hitachi Plug-in and the storage system in the Hitachi Documentation.

Known Issues

The following is a list of known major issues for Hitachi Plug-In for Veeam Backup & Replication. If you experience any issue listed below, contact Hitachi support directly.

Adding Hitachi storage to the Veeam Backup & Replication infrastructure by Service Processor (SVP) IP is not supported but is allowed by this plug-in version. Make sure you are using one of the CTL1/CTL2 IP addresses to add the storage.
Note: This limitation does not apply to VSP 5000 series.
Hitachi Plug-In does not return information about volumes that are not mounted to a host. To perform a restore from snapshots residing on such volumes, mount a volume to a host and perform a rescan in the Veeam Backup & Replication console. For details, see Rescanning Storage Systems.
This plug-in version does not support Freeze-only snapshots. If you want to enable VM processing using VMware snapshots, contact Veeam support to change the value of a dedicated registry key.
If you make any changes to host groups/iSCSI targets configuration after at least one restore operation, you must manually restart the Veeam Backup Service. The service restart will refresh the plug-in cache, and the configuration changes will be updated.
After deleting a snapshot, logical device (LDEV) records with the _DEL suffix may remain on storage until the next storage rescan operation. However, such snapshots can be exported during rescan and displayed in the storage infrastructure UI as regular volumes. To avoid issues, you can manually delete or unexport such snapshots.
If jobs and rescan operations are running in parallel or at the moment when the storage system is processing other tasks, the operations may fail.
Hitachi Plug-In does not support backing up of failover clusters using Veeam Agent for Windows.
Veeam Backup Service restart causes subsequent Veeam Agent for Windows job to fail. The issue occurs because the job triggers storage information caching, and it exceeds the VSS freeze timeout.
Ensure there are at least two FC ports available on the storage; configurations with a single FC port are not supported.

Download Hitachi Plug-In

MD5: 8bc9d3698500e563438f04251b56cfcc
SHA1: f3101cfff56daadffa53d25e9b2e8d921bc21e92

↧

How to test Exchange Online service connection performance using Microsoft Support and Recovery Assistant

August 18, 2021, 3:54 pm

≫ Next: How to temporarily disable Exchange Web Services throttling

≪ Previous: Release Notes for Hitachi Plug-In for Veeam Backup & Replication 1.0.66

↧

How to temporarily disable Exchange Web Services throttling

August 18, 2021, 3:57 pm

≫ Next: Release Notes for Dell EMC PowerMax Plug-In for Veeam Backup & Replication 1.0.84

≪ Previous: How to test Exchange Online service connection performance using Microsoft Support and Recovery Assistant

KB ID:	4198
Product:	Veeam Backup for Microsoft Office 365

Purpose

This article documents how to temporarily disable Exchange Web Services API throttling, potentially improving Exchange backup performance in Veeam Backup for Microsoft Office 365.

Note: Throttling may only be disabled temporarily; this should be sufficient to allow Veeam Backup for Microsoft Office 365 to perform the initial full backup.

Cause

By default, all download requests performed by a backup job interacting with Exchange Web Services API are throttled, impacting backup job performance. It is possible to turn this throttling off in Microsoft 365 admin center temporarily.

Solution

Before disabling EWS Throttling Policy, it is suggested to perform an Exchange Online connection performance test using Microsoft Support and Recovery Assistant tool. If the performance test reports bandwidth speed greater than what is seen in the Veeam Backup for Microsoft Office 365 backup job, it is advisable to temporarily disable EWS Throttling.

How to temporarily disable EWS Throttling Policy

Go to admin.microsoft.com and sign-in with administrator credentials
On the left Navigation panel, expand the Support section and select New service request
If this option is not available, click Show all at the bottom of the Navigation panel.

In the panel that appears on the right side, type EWS into the search box and select the "Increase EWS throttling policy" option from the auto-complete list.

Click the "Run Tests" button to determine the current throttling state:

After the test completes one of three results will be presented:

"The Exchange Web Services are Throttled." with an option to request the throttling be temporarily changed.
After clicking "Update Settings," a confirmation message will be shown.

"The Exchange Web Services are Throttled." with a note advising to create a new service request with Microsoft Support to change the throttling policy.

Throttling is enabled, contact microsoft to request policy change.

"Your Exchange Web Services are not currently throttled." with a note stating when throttling will be reapplied.

More information

More details regarding Exchange Web Services throttling can be found here: EWS throttling in Exchange.

Should you experience any challenges during the completion of this procedure or have questions on EWS throttling, please reach out to Microsoft support.

↧

Release Notes for Dell EMC PowerMax Plug-In for Veeam Backup & Replication 1.0.84

August 25, 2021, 3:22 pm

≫ Next: Microsoft Teams backup fails with the "Object reference not set to an instance of an object" error

≪ Previous: How to temporarily disable Exchange Web Services throttling

KB ID:	4200
Product:	Veeam Backup & Replication 11, Veeam Backup & Replication 10a

Requirements

Before installing Dell EMC PowerMax Plug-In, make sure that you are running Veeam Backup & Replication version 10.0.0.4461 or later. To check the version, open the main menu of the Veeam Backup & Replication console and select Help > About.

Dell EMC PowerMax Plug-In for Veeam Backup & Replication supports integration with the following storage systems:

Dell EMC PowerMax/VMAX All Flash (PowerMax OS/HyperMax OS microcode family 5978 or later)
Unisphere for PowerMax 9.2.1.6 or later

Follow detailed instructions on configuring the Dell EMC PowerMax Plug-in and the storage system in the Dell EMC documentation.

Known Issues

The following is a list of known major issues for Dell EMC PowerMax Plug-In for Veeam Backup & Replication.

Dell EMC PowerMax Plug-In does not support adding two Unisphere servers with the same array(s) as "local". Doing so will cause issues with discovery and can lead to undesirable results.
In large environments, selecting volumes from infrastructure while adding storage to Veeam B&R might take considerable time. In this case, it is recommended to use wildcards in the volume selection dialog to reduce the number of volumes to be scanned.
Export operations may fail when many jobs are triggered in parallel or trigger when the storage system is processing other tasks. As a workaround, create fewer jobs processing a larger number of VMs.
Storage cache overflow may occur in case of a high number of tasks triggered in parallel. As a workaround, perform cache cleanup and contact Dell EMC support for further investigation.
Temporary clone volumes with the -DeletePending suffix created during backup jobs may remain on storage until the next storage rescan operation.
Dell EMC PowerMax Plug-In does not support backing up of failover clusters using Veeam Agent for Windows.

Download Plug-In

MD5: B904CBDB959659AC4CD87B72E204695C

SHA1: B006C381D90F044234B7387FB2AB137CC28AB4C4

↧

Microsoft Teams backup fails with the "Object reference not set to an instance of an object" error

August 26, 2021, 10:54 am

≫ Next: Architecture Guideline for NEC EXPRESSCLUSTER X

≪ Previous: Release Notes for Dell EMC PowerMax Plug-In for Veeam Backup & Replication 1.0.84

KB ID:	4201
Product:	Veeam Backup for Microsoft Office 365
Version:	5c (build 5.0.2.22)

Challenge

Backup of Microsoft Teams in Veeam Backup for Microsoft Office 365 fails with the following error:

Error: Object reference not set to an instance of an object.

Cause

This issue is related to recent changes in Microsoft Graph API response syntax to a specific request that Veeam Backup for Microsoft Office 365 uses to process Microsoft Teams.

Solution

Hotfix Compatibility

This hotfix is only compatible with Veeam Backup for Microsoft Office 365 version 5c (build 5.0.2.22). If that version is not presently installed, you must upgrade before installing the hotfix.
This hotfix resolves only the issue documented on this KB. If a different hotfix is already installed, do not install this hotfix. Contact Veeam Support, and a cumulative hotfix will be created for you.

Hotfix Installation

Stop all Backup Jobs
End all active Restore sessions (if any)
Stop the following Services on the Veeam Backup for Microsoft Office 365 server.
- Veeam Backup for Microsoft Office 365 Service
- Veeam Backup Proxy for Microsoft Office 365 Service
- Veeam Backup for Microsoft Office 365 RESTful API Service
Download the hotfix using the button in the More Information section below.
Extract the contents of the ZIP file to the C:\Temp folder.
Run the following cmdlet in Windows PowerShell using the Administrator mode to remove security locks:

Get-ChildItem -Path "C:\temp\KB4201_20210826\" -Recurse -Force | Unblock-File
On the Veeam Backup for Microsoft Office 365 controller server, find the original Veeam.Graph.Teams.dll and Veeam.Archiver.Source.dll in each of the folders listed below. Rename the original dlls, or move them to another folder, then copy the Veeam.Graph.Teams.dll and Veeam.Archiver.Source.dll from the Hotfix folder to:
- C:\Program Files\Veeam\Backup365
- C:\Program Files\Veeam\Backup365\Packages\Proxy
- C:\Program Files\Veeam\Backup and Replication\Explorers\Teams
On the servers where Veeam Explorer for Microsoft Teams is installed, find the original Veeam.Teams.Restore.dll and Veeam.Graph.Teams.dll in the folder listed below. Rename the original dlls, or move them to another folder, then copy the Veeam.Teams.Restore.dll and Veeam.Graph.Teams.dll from the Hotfix folder to:
- C:\Program Files\Veeam\Backup and Replication\Explorers\Teams
Start the services stopped in Step 3
Upgrade the backup proxy servers using the Veeam Backup for Microsoft Office 365 console.
Run a job that backs up Microsoft Teams data and check whether the issue persists.

If the issue persists after installing the hotfix, please collect log files and open a Veeam Support case.

More information

DOWNLOAD HOTFIX

MD5: F6DFD25CAA83183ED9D67B066410B28C
SHA-1: FEF18123AD14CECB8A2F8E9CD27CCEDDC3154A25

↧

Architecture Guideline for NEC EXPRESSCLUSTER X

August 27, 2021, 7:55 am

≫ Next: Build numbers and versions of Veeam Backup for Microsoft Office 365

≪ Previous: Microsoft Teams backup fails with the "Object reference not set to an instance of an object" error

KB ID:	4202
Product:	Veeam Backup & Replication 11, Veeam Agent for Microsoft Windows 5.0

Solution

NEX EXPRESSCLUSTER X provides an additional layer of abstraction for the cluster. Considering those changes, this requires a specific configuration of Veeam Agent for Microsoft Windows for successful backups and restores.

Please refer to the backup and restore guideline - ExpressCluster® X for Windows Software Integration Guide

↧

Build numbers and versions of Veeam Backup for Microsoft Office 365

September 1, 2021, 2:02 pm

≫ Next: Veeam Backup for Microsoft Office 365 5c cumulative patch KB4187

≪ Previous: Architecture Guideline for NEC EXPRESSCLUSTER X

KB ID:	4106
Product:	Veeam Backup for Microsoft Office 365

This KB article provides a list of all Veeam Backup for Microsoft Office 365 versions and the respective build numbers.

The latest version of Veeam Backup for Microsoft Office 365 can always be found at https://www.veeam.com/download-version.html

The following table lists Veeam Backup for Microsoft Office 365 versions and their build numbers. Also provided is a link to the specific version release notes.

Version	Build Number		Release Date	Release Notes/KB
Version	Console display	Control panel and logs display	Release Date	Release Notes/KB
Veeam Backup for Microsoft Office 365 5c cumulative patch KB4187	5.0.2.42	10.0.4.42	2021-09-01	KB4187
Veeam Backup for Microsoft Office 365 5c	5.0.2.22	10.0.4.22	2021-06-28	KB4181
Veeam Backup for Microsoft Office 365 5b cumulative patch KB4158	5.0.1.252	10.0.3.252	2021-05-31	KB4158
Veeam Backup for Microsoft Office 365 5b cumulative patch KB4135	5.0.1.225	10.0.3.225	2021-04-12	KB4135
Veeam Backup for Microsoft Office 365 5b cumulative patch KB4124	5.0.1.207	10.0.3.207	2021-03-12	KB4124
Veeam Backup for Microsoft Office 365 5b	5.0.1.179	10.0.3.179	2021-02-08	Release notes KB4092
Veeam Backup for Microsoft Office 365 5a	5.0.0.1070	10.0.2.1070	2020-12-14	Release notes KB4082
Veeam Backup for Microsoft Office 365 5.0 Day 0 Update	5.0.0.1063	10.0.2.1063	2020-12-04	Release notes
Veeam Backup for Microsoft Office 365 5.0 GA	5.0.0.1061	10.0.2.1061	2020-12-03	Release notes
Veeam Backup for Microsoft Office 365 4c cumulative patch KB4099	4.0.1.625	10.0.1.625	2021-02-16	KB4099
Veeam Backup for Microsoft Office 365 4c cumulative patch KB4083	4.0.1.612	10.0.1.612	2020-12-24	KB4083
Veeam Backup for Microsoft Office 365 4c cumulative patch KB3222	4.0.1.545	10.0.1.545	2020-07-09	KB3222
Veeam Backup for Microsoft Office 365 4c Day 0 Update	4.0.1.531	10.0.1.531	2020-06-16	KB3145
Veeam Backup for Microsoft Office 365 4b cumulative patch KB3119	4.0.0.2549	9.6.6.2549	2020-03-31	KB3119
Veeam Backup for Microsoft Office 365 4b	4.0.0.2516	9.6.6.2516	2020-01-31	KB3065
Veeam Backup for Microsoft Office 365 4a cumulative patch KB3089	4.0.0.1580	9.6.6.1580	2020-03-10	KB3089
Veeam Backup for Microsoft Office 365 4a	4.0.0.1553	9.6.6.1553	2020-01-21	KB3035
Veeam Backup for Microsoft Office 365 4.0 GA	4.0.0.1345	9.6.6.1345	2019-11-26	Release notes
Veeam Backup for Microsoft Office 365 3.0 GA	3.0.0.422	9.6.5.422	2019-04-02	Release notes
Veeam Backup for Microsoft Office 365 2.0 Cumulative patch KB2809	2.0.0.814	9.6.3.814	2018-12-28	KB2809
Veeam Backup for Microsoft Office 365 2.0 Cumulative patch KB2765	2.0.0.594	9.6.3.594	2018-09-26	KB2765
Veeam Backup for Microsoft Office 365 2.0 GA	2.0.0.567	9.6.3.567	2018-07-24	Release notes
Veeam Backup for Microsoft Office 365 1.5 GA	1.5.0.1099	9.6.0.1099	2017-10-03	Release notes
Veeam Backup for Microsoft Office 365 1.0 Update 1	1.0.0.912	9.5.0.912	2017-01-20	KB2224
Veeam Backup for Microsoft Office 365 1.0 GA	1.0.0.860	9.5.0.860	2016-11-29	Release notes

↧

Veeam Backup for Microsoft Office 365 5c cumulative patch KB4187

September 1, 2021, 1:35 pm

≫ Next: Veeam Agent for Linux support of Red Hat Enterprise Linux

≪ Previous: Build numbers and versions of Veeam Backup for Microsoft Office 365

KB ID:	4187
Product:	Veeam Backup for Microsoft Office 365 5.0

Requirements

Please confirm you are running Veeam Backup for Microsoft Office 365 build 5.0.2.22 prior to installing this cumulative patch KB4187. You can check this under Help and Support > About in Veeam Backup for Microsoft Office 365 console. After upgrading, your build version will change to 5.0.2.42.

As a result of ongoing R&D effort and in response to customer feedback, cumulative patch KB4187 provides a set of bug fixes, the most significant of which are listed below:

Resolved Issues

General

Under certain conditions a proxy may fail with the “Out of Memory” error during backup to an object storage repository.

Backup

Microsoft Teams backup may fail with “Folder processing failed: Team Chat. Restriction contained too many elements” error.
Backup of Team Chat messages created after October 2020 may fail with the “Failed to get TeamsMessagesData folder” error.
Microsoft Teams backup fails with “Object reference not set to an instance of an object” error.
OneDrive backup fails with “Object reference not set to an instance of an object” error if there’re any large OneNote files that are open and being edited during backup.

Restore

In BaaS scenarios, exporting backup data to a local disk on the tenant side fails with the timeout error.
Export operation in Veeam Explorer for Microsoft Exchange may fail with the “Connection to server was unexpectedly closed” error.
For larger Office 365 organizations, some OneDrive accounts may not be displayed in the “Copy OneDrive” wizard

RESTful API

SharePoint site title field is empty if such a site has been added to a backup job explicitly via REST API and the site title has not been explicitly specified.
Removing a group with audit items via REST API doesn't work as expected but reports back response code 200.
In BaaS scenarios with the modern app-only approach, obtaining a token for tenant authentication via REST API fails if a combination of capital and lower-case letters is used to specify the client_id parameter.

Solution

To install the cumulative patch KB4187:

Download VeeamBackupOffice365_5.0.2.42_KB4187.zip
Execute VeeamBackupOffice365_5.0.2.42_KB4187.msp as administrator on the Veeam Backup for Microsoft Office 365 server.
Execute VeeamExplorerForExchange_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft Exchange is installed.
Execute VeeamExplorerForSharePoint_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft SharePoint is installed.
Execute VeeamExplorerForTeams_5.0.2.42_KB4187.msp as administrator on each machine where Veeam Explorer for Microsoft Teams is installed.

If there are any remote proxies in your environment, please update those as described here.

DOWNLOAD PATCH

MD5: 546BD6F775F46C5E3A930B320719EE0B
SHA-1: E17B67AFBEA518CE686B81F75F36EFE02040CE1D

↧

Veeam Agent for Linux support of Red Hat Enterprise Linux

September 8, 2021, 7:35 am

≫ Next: Rescan fails with "Unable to install backup agent: cannot connect to Error: Known agent have the same bios uuid but different connection point ."

≪ Previous: Veeam Backup for Microsoft Office 365 5c cumulative patch KB4187

KB ID:	2804
Version:	Any

This article describes Veeam Agent for Linux support of different kernel versions of Red Hat Enterprise Linux and its derivatives.

Important

Last-minute kernel patches for Red Hat Enterprise Linux and its derivatives may cause Veeam Agent for Linux to go unstable (veeam.com/kb2786).

Veeam Agent for Linux 5.0

RHEL version	Kernel supported up to	VAL build	Comments
8.4	4.18.0-305.17.1.el8_4	5.0.0.4325	Known issue: deployment via Agent Management fails. For packages and instructions please open a support ticket.
8.0-8.3	4.18.0-240.22.1.el8_3	5.0.0.4318	Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.
7.0-7.9	3.10.0-1160.42.2.el7	5.0.0.4318	Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA.
6.0-6.10	2.6.32-754.35.1.el6	5.0.0.4318	Veeam Agents for Linux version 5.0. Shipped with Backup & Replication 11.0 GA. Please note that RHEL6 reached "End of life" and therefore EPEL repository has archived version 6 packages. If you are looking for dkms package (VAL prerequisite), check https://archives.fedoraproject.org/pub/archive/epel/6/ See also https://access.redhat.com/discussions/4768501.

Veeam Agent for Linux 4.0.1

RHEL version	Kernel supported up to	VAL build	Comments
8.3	4.18.0-240.22.1.el8_3	4.0.1.2372	Shipped with Backup & Replication 10.0.1.4854 P20201202. Get packages for standalone installations from veeam.com.
8.0-8.2	4.18.0-193.28.1.el8_2	4.0.1.2365	Veeam Agents for Linux version 4.0.1. Also shipped with Backup & Replication v10a.
7.9	3.10.0-1160.41.1.el7	4.0.1.2372	Shipped with Backup & Replication 10.0.1.4854 P20201202. Get packages for standalone installations from veeam.com.
7.0-7.8	3.10.0-1127.19.1.el7	4.0.1.2365	Veeam Agents for Linux version 4.0.1. Also shipped with Backup & Replication v10a.
6.x	2.6.32-754.35.1.el6	4.0.1.2372	Shipped with Backup & Replication 10.0.1.4854 P20201202. Get packages for standalone installations from veeam.com.

Veeam Agent for Linux 4:

RHEL version	Kernel supported up to	VAL build	Comments
8.0-8.1	4.18.0-147.8.1.el8_1	4.0.0.1961	Veeam Agents for Linux version 4 GA build. Also shipped with Backup & Replication v10 GA.
7.0-7.9	3.10.0-1160.41.1.el7	4.0.0.1961	Veeam Agents for Linux version 4 GA build. Also shipped with Backup & Replication v10 GA.
6.x	2.6.32-754.29.2.el6	4.0.0.1961	Veeam Agents for Linux version 4 GA build. Also shipped with Backup & Replication v10 GA.

Veeam Agent for Linux 3:

RHEL version	Kernel supported up to	VAL build	Comments
8.1	4.18.0-147	3.0.2.1193	For packages and instructions please open a support ticket.
8.0	4.18.0-80.7.2	3.0.2.1185	For standalone installations you can obtain build 3.0.2.1185 from veeam.com. For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.
7.7	3.10.0-1062 or newer	3.0.2.1190	For standalone installations you can obtain build 3.0.2.1190 from repository.veeam.com. For instructions on how to deploy build 3.0.2.1190 on installations managed by Backup & Replication please refer to Veeam Agent Management Guide.
7.0-7.6	3.10.0-957.27.2	3.0.2.1185	For standalone installations you can obtain build 3.0.2.1185 from veeam.com. For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.
6.x	2.6.32-754.18.2	3.0.2.1185	For standalone installations you can obtain build 3.0.2.1185 from veeam.com. For managed installations the build is shipped with Backup & Replication v.9.5 update 4b (9.5.4.2866). For details on Backup & Replication 9.5.4.2866 please refer to kb2970.

↧

Rescan fails with "Unable to install backup agent: cannot connect to Error: Known agent have the same bios uuid but different connection point ."

September 10, 2021, 11:30 am

≫ Next: Veeam Primary Storage Integration processing overview

≪ Previous: Veeam Agent for Linux support of Red Hat Enterprise Linux

KB ID:	4205
Product:	Veeam Agent for Microsoft Windows 5.0, Veeam Agent for Microsoft Windows 4.0, Veeam Agent for Microsoft Windows 3.0.2, Veeam Agent for Microsoft Windows 2.2

Scenario Specific Article

This article documents the solution for two specific scenarios.

If the scenarios listed in the Cause section do not match your situation, please create a support case.

Challenge

During the rescan of a Protection Group, the following error occurs:

 
                 Unable to install backup agent: cannot connect to 192.168.1.55 Error: Known agent SQL-19 have the same bios uuid 59f0f2da-1251-11ec-82a8-0242ac130003 but different connection point 192.168.1.55. 
                

Cause

Scenario 1: Reinstalled OS

The OS was reinstalled on the machine that is displaying this error during rescan.

Scenario 2: Different Machines, Same BIOS UUID

An entirely different machine has been added to the Protection Group. However, those machines have the same BIOS UUID.

The UUID value of a machine can be checked using the following PowerShell cmdlet:

(Get-WmiObject Win32_ComputerSystemProduct).UUID

https://docs.microsoft.com/en-us/windows/win32/cimwin32prov/win32-computersystemproduct

Solution

Scenario 1: Reinstalled OS

To resolve the conflict, remove the old machine's entry from the Protection Group.

Scenario 2: Different Machines, Same BIOS UUID

Each Veeam Agent computer that consumes a license installed in Veeam Backup & Replication must have a unique BIOS UUID.

If different physical machines have the same BIOS UUIDs, contact the hardware vendor to request assistance in ensuring each machine has a unique BIOS UUID.

If Veeam Agent is being used with a VM, please refer to corresponding Hypervisor articles regarding BIOS UUID:

VMware - https://kb.vmware.com/s/article/1002403
Citrix - https://support.citrix.com/article/CTX230618

More information

Unsupported Workaround

Unsupported Wordaround

This workaround is provided as a courtesy and is not supported by Veeam Technical Support.

Use it at your own risk.

If any issue occurs while attempting this workaround, you are advised to restore from a configuration backup to revert the Veeam Backup & Replication server to the last known stable state.

Veeam Technical Support will not assist in the usage or troubleshooting of this tool.

If it is not possible to make the BIOS UUID for a machine uniqe, it is possible to instruct Veeam Agent to use a user specified UUID value from the registry. Use the following PowerShell cmdlets on the machine with the duplicate BIOS UUID.

To enable UUID Failover:

 
                       New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam' -Name EnableSystemUuidFailover -PropertyType DWORD -Value 1

The next command must be modified to place a user-generated UUID where the <UUID> is shown in the command (without carrots).

 
                       New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam' -Name SystemUuid -PropertyType String -Value '<UUID>'

↧

Veeam Primary Storage Integration processing overview

September 13, 2021, 10:55 am

≫ Next: How to Assign Permissions to Service Accounts Used by Veeam Backup for Google Cloud Platform

≪ Previous: Rescan fails with "Unable to install backup agent: cannot connect to Error: Known agent have the same bios uuid but different connection point ."

KB ID:	4206
Product:	Veeam Backup & Replication

Challenge

Customers seeking new storage systems may want to consider Veeams storage integration and special processing and compare systems.

Solution

The table below lists the following Primary Storage processing methods:

Veeam Universal Storage API
Storage Vendors can leverage the Universal Storage API SDK to build their own Storage Snapshot processing integration into Veeam Backup & Replication.
Veeam's own custom storage integrations for storage snapshot processing
Veeam's own custom processing for Hyper-Converged Storage systems and hypervisor storage VM snapshot processing.

Storage	Backup from Storage Snapshots, Veeam Explorer for Storage Snapshots, OnDemand Sandbox for Storage Snapshots	Secondary Snapshot Orchestration
Cisco
Adaptive Solutions for CI (based on Hitachi VSP) ¹
FlashStack (based on Pure Storage FlashArray) ¹
FlexPod (based on NetApp FAS/AFF)		³
HyperFlex	Learn more about: Backup from Cisco HyperFlex
SmartStack (based on HPE Nimble)		³
VersaStack (based on IBM Storwize)
DataCore
SANsymphony ¹
Dell EMC
PowerMax ¹
SC Compellent ¹
Unity, Unity XT
VMAX AllFlash ¹
VNX, VNXe
VxBlock/vBlock (based on Dell EMC PowerMax) ¹
VxBlock/vBlock (based on Dell EMC Unity)
Fujitsu
ETERNUS DX/AF ¹
ETERNUS HX/AX		³
XF	Learn more about: AHV Snapshot processing
Hitachi
VSP E/F/G/5000 ¹
HPE
3PAR		^2,3
Alletra 9000		^2,3
dHCI (based on HPE Nimble)		³
DX-Series	Learn more about: AHV Snapshot processing
Nimble		³
Primera		^2,3
StoreVirtual, HC380
XP8 ¹
Huawei
OceanStor ¹
OceanStor Dorado ¹
IBM
N-Series		³
Spectrum Virtualize
StorWize
FlashSystem
SVC
INFINIDAT
InfiniBox ¹
Inspur
inMerge 1000	Learn more about: AHV Snapshot processing
Lenovo
Storage V-Series
Storwize
ThinkAgile HX	Learn more about: AHV Snapshot processing
ThinkSystem DM		³
Microsoft
Storage Spaces / Storage Spaces Direct	Learn more about: Microsoft Storage
NetApp
AFF		³
Edge		³
FAS		³
FlexArray		³
ONTAP Select		³
SolidFire / HCI ¹
Nutanix
AHV	Learn more about: AHV Snapshot processing
Pure Storage
FA-400 ¹
FlashArray//C ¹
FlashArray//M ¹
FlashArray//X ¹
Tintri
IntelliFlash HD/N/T ¹
VMware
vSAN	Learn more about: Veeam vSAN Integration

¹ Requires a separate plug-in download

² Snapshot creation on Peer Persistent Target

³ Snapshot Replication

↧

How to Assign Permissions to Service Accounts Used by Veeam Backup for Google Cloud Platform

September 13, 2021, 3:44 pm

≫ Next: Veeam Disaster Recovery Orchestrator limitations with VMware Cloud Offerings

≪ Previous: Veeam Primary Storage Integration processing overview

KB ID:	4062
Product:	Veeam Backup for Google Cloud Platform 2.0

Challenge

Veeam Backup for Google Cloud Platform requires a service account in each GCP project where data protection and disaster recovery tasks will be performed. The tasks include the following:

Solution

To apply the necessary permissions to a service account, you can use a script that is automatically generated while adding the project to the Veeam Backup for GCP infrastructure. Download the script and run it under an account that has permissions both to get and set project IAM policies and to create custom IAM roles (for example, it can have the iam.securityAdmin and iam.roleAdmin roles assigned). To learn what permissions and roles are required to create custom roles in IAM, see Google Cloud documentation.

NOTE: You can click Check permissions to ensure that the account now has all the permissions required to perform data protection and disaster recovery tasks for the project. Keep in mind that it may take some time for Google Cloud to apply the changes to the account, and the permission check may display the permissions as missing right after you click Check permissions. To work around the issue, try checking permissions once again in 5–10 minutes.

Alternatively, you can assign the permissions to the service account manually. The permissions are listed below.

Expand each heading below to see specific permissions.

Default Permissions

 
                       compute.disks.addResourcePolicies
compute.disks.get
compute.instances.get
compute.resourcePolicies.create
compute.resourcePolicies.get
compute.resourcePolicies.use
compute.zones.get
serviceusage.services.list 
                      

Backup Permissions

 
                       cloudkms.cryptoKeys.getIamPolicy
cloudkms.cryptoKeys.list
cloudkms.cryptoKeys.setIamPolicy
cloudkms.keyRings.list
compute.addresses.list
compute.disks.createSnapshot
compute.disks.get
compute.disks.list
compute.firewalls.list
compute.globalOperations.get
compute.globalOperations.list
compute.instances.get
compute.instances.list
compute.machineTypes.get
compute.networks.list
compute.projects.get
compute.regionOperations.get
compute.regions.get
compute.regions.list
compute.routes.list
compute.snapshots.create
compute.snapshots.delete
compute.snapshots.get
compute.snapshots.getIamPolicy
compute.snapshots.list
compute.snapshots.setIamPolicy
compute.snapshots.setLabels
compute.subnetworks.list
compute.zoneOperations.get
compute.zones.list
logging.sinks.create
logging.sinks.delete
logging.sinks.get
logging.sinks.list
logging.sinks.update
pubsub.subscriptions.consume
pubsub.subscriptions.create
pubsub.subscriptions.delete
pubsub.subscriptions.get
pubsub.subscriptions.list
pubsub.topics.attachSubscription
pubsub.topics.create
pubsub.topics.delete
pubsub.topics.detachSubscription
pubsub.topics.get
pubsub.topics.getIamPolicy
pubsub.topics.list
pubsub.topics.setIamPolicy
pubsub.topics.update
resourcemanager.projects.get
resourcemanager.projects.getIamPolicy
serviceusage.services.list 
                      

Snapshot Permissions

 
                       cloudkms.cryptoKeys.list
cloudkms.keyRings.list
compute.addresses.list
compute.disks.createSnapshot
compute.disks.get
compute.disks.list
compute.firewalls.list
compute.globalOperations.get
compute.globalOperations.list
compute.instances.get
compute.instances.list
compute.networks.list
compute.regionOperations.get
compute.regions.list
compute.routes.list
compute.snapshots.create
compute.snapshots.delete
compute.snapshots.get
compute.snapshots.list
compute.snapshots.setLabels
compute.subnetworks.list
compute.zoneOperations.get
compute.zones.list
logging.sinks.create
logging.sinks.delete
logging.sinks.get
logging.sinks.list
logging.sinks.update
pubsub.subscriptions.consume
pubsub.subscriptions.create
pubsub.subscriptions.delete
pubsub.subscriptions.get
pubsub.subscriptions.list
pubsub.topics.attachSubscription
pubsub.topics.create
pubsub.topics.delete
pubsub.topics.detachSubscription
pubsub.topics.get
pubsub.topics.getIamPolicy
pubsub.topics.list
pubsub.topics.setIamPolicy
pubsub.topics.update
resourcemanager.projects.get
serviceusage.services.list 
                      

Repository Permissions

 
                       resourcemanager.projects.get
serviceusage.services.list
storage.buckets.get
storage.buckets.list
storage.hmacKeys.create
storage.hmacKeys.get
storage.hmacKeys.list
storage.objects.create
storage.objects.delete
storage.objects.get
storage.objects.list 
                      

Restore Permissions

Note: To allow Veeam Backup for GCP to perform restore to the original location while source VM instances still exist there, you must also add the permission compute.instances.setName. The ability to rename VM instances is currently in pre-GA state. For more information, see Google Cloud documentation.

 
                       cloudkms.cryptoKeys.getIamPolicy
cloudkms.cryptoKeys.list
cloudkms.cryptoKeys.setIamPolicy
cloudkms.keyRings.list
compute.addresses.list
compute.addresses.use
compute.addresses.useInternal
compute.disks.create
compute.disks.delete
compute.disks.get
compute.disks.list
compute.disks.setLabels
compute.disks.use
compute.disks.useReadOnly
compute.firewalls.list
compute.globalOperations.get
compute.globalOperations.list
compute.instances.create
compute.instances.delete
compute.instances.get
compute.instances.list
compute.instances.setDeletionProtection
compute.instances.setLabels
compute.instances.setMachineResources
compute.instances.setMetadata
compute.instances.setMinCpuPlatform
compute.instances.setScheduling
compute.instances.setServiceAccount
compute.instances.setTags
compute.instances.start
compute.instances.stop
compute.instances.updateDisplayDevice
compute.instances.updateNetworkInterface
compute.machineTypes.list
compute.networks.list
compute.projects.get
compute.regionOperations.get
compute.regions.get
compute.regions.list
compute.routes.list
compute.snapshots.create
compute.snapshots.delete
compute.snapshots.get
compute.snapshots.getIamPolicy
compute.snapshots.list
compute.snapshots.setLabels
compute.snapshots.useReadOnly
compute.subnetworks.list
compute.subnetworks.use
compute.subnetworks.useExternalIp
compute.zoneOperations.get
compute.zones.get
compute.zones.list
iam.serviceAccounts.actAs
iam.serviceAccounts.list
resourcemanager.projects.get
serviceusage.services.list 
                      

Worker Permissions

 
                       compute.disks.create
compute.disks.createSnapshot
compute.disks.delete
compute.disks.list
compute.disks.setLabels
compute.disks.use
compute.firewalls.list
compute.globalOperations.get
compute.instances.create
compute.instances.delete
compute.instances.detachDisk
compute.instances.get
compute.instances.list
compute.instances.setLabels
compute.instances.setMetadata
compute.instances.setServiceAccount
compute.instances.setTags
compute.machineTypes.get
compute.networks.list
compute.projects.get
compute.regionOperations.get
compute.regions.get
compute.regions.list
compute.routes.list
compute.snapshots.create
compute.snapshots.delete
compute.snapshots.get
compute.snapshots.getIamPolicy
compute.snapshots.list
compute.snapshots.setIamPolicy
compute.snapshots.setLabels
compute.subnetworks.get
compute.subnetworks.list
compute.subnetworks.use
compute.subnetworks.useExternalIp
compute.zoneOperations.get
compute.zones.get
compute.zones.list
iam.serviceAccounts.actAs
logging.sinks.delete
logging.sinks.get
logging.sinks.list
pubsub.subscriptions.consume
pubsub.subscriptions.create
pubsub.subscriptions.delete
pubsub.subscriptions.get
pubsub.subscriptions.list
pubsub.topics.attachSubscription
pubsub.topics.create
pubsub.topics.delete
pubsub.topics.get
pubsub.topics.list
pubsub.topics.publish
resourcemanager.projects.get
resourcemanager.projects.getIamPolicy
serviceusage.services.list 
                      

↧

Veeam Disaster Recovery Orchestrator limitations with VMware Cloud Offerings

September 14, 2021, 1:13 pm

≫ Next: Veeam Management Pack 9.0 Patch 1 for Microsoft Hyper-V monitoring

≪ Previous: How to Assign Permissions to Service Accounts Used by Veeam Backup for Google Cloud Platform

KB ID:	4207
Product:	Veeam Disaster Recovery Orchestrator

Overview

VMware Cloud Verified offerings exist in various forms. This article highlights specific considerations when working with Veeam Disaster Recovery Orchestrator, Veeam Backup & Replication, and Veeam ONE for disaster recovery orchestration purposes.

Depending on the vendor-specific VMware solution offering some features and permissions are not available. This may mean that it is possible to restore a backup or failover a replica, but other core features of the Veeam Disaster Recovery Orchestrator may be limited or unavailable. This situation may change as features in the table below may become available in the future.

End-to-end networking from source and target environment is required, including DNS and access to the same Active Directory infrastructure across all sites. Veeam ONE needs to be used to configure VM groups.

Limitations

Cloud offering	Regular Replica Plans	Restore Plan	CDP Replica Plan	Storage Plan
Azure VMware Solution (AVS)	ReIP UnavailableReIP Unavailable	ReIP UnavailableReIP Unavailable	Not AvailableNot available due to lack of permissions to install I/O filter driver.	Not AvailableStorage plans require local storage, which is not available in vSphere Cloud offerings.
	Testing Plan UnavailableTesting of orchestration plans is not available.	Testing Plan UnavailableTesting of orchestration plans is not available.
	Network Mapping AVS Version DependantNetwork mapping does not work on some versions of AVS.	Network Mapping AVS Version DependantNetwork mapping does not work on some versions of AVS.
		Instant Recovery UnavailableInstant VM Recovery is unavailable due to a lack of NFS access.
VMware Cloud on AWS (VMC)	ReIP UnavailableReIP Unavailable	ReIP UnavailableReIP Unavailable	Not AvailableNot available due to lack of permissions to install I/O filter driver.	Not AvailableStorage plans require local storage, which is not available in vSphere Cloud offerings.
	Testing Plan UnavailableTesting of orchestration plans is not available.	Testing Plan UnavailableTesting of orchestration plans is not available.
		Instant Recovery UnavailableInstant VM Recovery is unavailable due to a lack of NFS access.
Google Cloud VMware Engine (GCVE)	ReIP UnavailableReIP Unavailable	ReIP UnavailableReIP Unavailable	Not AvailableNot available due to lack of permissions to install I/O filter driver.	Not AvailableStorage plans require local storage, which is not available in vSphere Cloud offerings.
	Testing Plan UnavailableTesting of orchestration plans is not available.	Testing Plan UnavailableTesting of orchestration plans is not available.
	GCVE v1 incompatible with Network MappingNetwork mapping does not work on GCVE v1.	GCVE v1 incompatible with Network MappingNetwork mapping does not work on GCVE v1.
		Instant Recovery UnavailableInstant VM Recovery is unavailable due to a lack of NFS access.
Oracle Cloud VMware Solution (OCVS)	No LimitationsAvailable as there are no permission limitations.	No LimitationsAvailable as there are no permission limitations.	Version DependantMay be available depending on the vSphere version as there are no permission limitations.	Not AvailableStorage plans require local storage, which is not available in vSphere Cloud offerings.
IBM Cloud for VMware Solutions	No LimitationsAvailable as there are no permission limitations.	No LimitationsAvailable as there are no permission limitations.	Version DependantMay be available depending on the vSphere version as there are no permission limitations.	Not AvailableStorage plans require local storage, which is not available in vSphere Cloud offerings.

Lack of support for an individual feature may have to do with limitations around the feature set available for individual VMware Cloud Verified solutions. Learn more about Veeam Backup & Replication support for:

↧

Veeam Management Pack 9.0 Patch 1 for Microsoft Hyper-V monitoring

September 21, 2021, 2:51 pm

≫ Next: Release Information for Veeam Service Provider Console v6

≪ Previous: Veeam Disaster Recovery Orchestrator limitations with VMware Cloud Offerings

KB ID:	4209
Product:	Veeam Management Pack for Microsoft System Center 9.0

Challenge

After upgrading to Veeam Management Pack to version 9.0, Hyper-V hosts disappear partially or entirely from the Hyper-V Servers tab of the Veeam UI. At the same time, Hyper-V infrastructure is displayed in the topology views of the OpsMgr console. Other views (for example, VM views) do not show any information.

Cause

The issue occurs in infrastructures having several management servers in a single monitoring group. In such infrastructures, OpsMgr agents may be reporting to different management servers. Due to recent changes in Veeam Management Pack for System Center version 9.0's Hyper-V monitoring mechanisms, accurate Hyper-V monitoring is possible only if OpsMgr agents installed on Hyper-V hosts report to the management server where the Veeam Virtualization Extension Service is installed.

Solution

The patch contains a fix to allow monitor Hyper-V infrastructure regardless of the OpsMgr agents reporting scheme.

To apply the patch:

On the server where the Veeam Virtualization Extension Service is installed, download Veeam Management Pack 9.0 Patch 1.
Navigate to the folder with the patch and extract patch files from the archive.
Run the exe file as Administrator and follow the instructions of the installer.
After you install the patch, restart the Veeam Virtualization Extension Service.

In case you monitor Hyper-V hosts behind the OpsMgr Gateway using the Remote VES and related OpsMgr agents do not report to a management server where the Veeam Virtualization Extension Service is installed, please follow the following steps:

Log in to the Veeam UI and click Settings.
In the Extensions Service Settings window, set the ServiceProviderMode parameter to a value of True.
After the parameter is enabled, monitoring data from management servers where the Virtualization Extension Service is installed and remote management servers connected using the remote Operations Manager SDK will appear in the OpsMgr console.

To learn how to establish a connection to the remote Operations Manager SDK, see the Veeam MP for Microsoft Hyper-V User Guide, section Installing on Gateway Server.

The option may be used for separating licenses between independent Virtualization Extension Service instances.

To turn the option off, set the value of the ServiceProviderMode parameter back to False.

More information

Should you have any questions, contact Veeam Technical support.

↧

Release Information for Veeam Service Provider Console v6

September 27, 2021, 7:13 am

≫ Next: LTO-9 Support Details for Veeam Backup & Replication 11

≪ Previous: Veeam Management Pack 9.0 Patch 1 for Microsoft Hyper-V monitoring

KB ID:	4212
Product:	Veeam Service Provider Console

Requirements

Please confirm that you are running version 5 (build 5.0.0.6726) or later prior to upgrading. You can check this under Configuration | Support Information in the Veeam Service Provider Console UI. After upgrading, your build number will be 6.0.0.7739

To upgrade from earlier versions, please upgrade to v5 first and then proceed with upgrading to v6.

Download Information

DOWNLOAD VSPC 6

MD5: E4E3B67B5FEE0FE98A4038D6729F147A
SHA-1: 43C060F883AEFDFD6DBFEABEA415ED04F10C5D8B

↧

LTO-9 Support Details for Veeam Backup & Replication 11

September 27, 2021, 7:34 am

≫ Next: Release Information for Veeam Backup & Replication 11a

≪ Previous: Release Information for Veeam Service Provider Console v6

KB ID:	4213
Product:	Veeam Backup & Replication 11

Challenge

Tape Backup jobs and other tape-related tasks in Veeam Backup & Replication may fail for up to 15-30 minutes after a new uninitialized LTO-9 tape is loaded into the Tape Drive.

Tasks will fail with an error similar to:

 
                 Failed to inventory tape in Drive 1. (Server: ..., Library: ..., Drive ID: ...) Error: The device is not ready
Unable to exchange medium in library. The tape device is not ready

This will only occur the first time a new uninitialized LTO-9 tape is inserted into a tape drive.

Log Example

 
                       ERR |The device is not ready.
>>  |Tape error: '21' (The device is not ready.) 
>>  |--tr:Error code: 0x00000015
>>  |--tr:TapeHandle failed to get tape media parameters.
>>  |--tr:Tape initialization FAILED.
>>  |An exception was thrown from thread [3296]. 
                      

Cause

This issue occurs due to the lengthy initialization process for new LTO-9 tapes, which occurs when the tape is inserted into the tape drive for the first time. During this initialization process, optimization occurs, which may take up to 20-120 minutes. While this operation is happening, the tape drive is locked and unavailable until the initialization completes. The duration of unavailability is longer than expected by Veeam Backup & Replication, which causes jobs and tasks to timeout and report a failure.

Solution

As this initialization time with LTO-9 tapes is unavoidable, new uninitialized LTO-9 tapes must be manually moved into the tape drive using native library tools before they are used with Veeam Backup & Replication.

More information

A hotfix is being developed to prevent Tape Backup jobs and other tape-related tasks from failing due to the lengthy inaccessibility period during the initialization of an LTO-9 tape. Instead, the tape jobs and tasks will wait while an uninitialized LTO-9 tape is optimized when first loaded into the tape drive. It should be noted that while this will prevent a Tape Job from failing, it will cause the Tape Backup jobs that attempt to use an uninitialized LTO-9 tape to run for longer than expected.

In the next major release of Veeam Backup & Replication after version 11a, there are plans to implement a solution to automatically trigger initialization when new LTO-9 tapes are inserted into a library managed by Veeam Backup & Replication.

↧

Release Information for Veeam Backup & Replication 11a

September 27, 2021, 1:29 pm

≫ Next: VSPC 5 fails to collect Monthly License Usage Report from VBR v11a

≪ Previous: LTO-9 Support Details for Veeam Backup & Replication 11

KB ID:	4215
Product:	Veeam Backup & Replication 11

Early Availability

Veeam Backup & Replication 11a is currently in the Early Availability stage. This RTM build is fully supported by our Customer Support for production deployments. Until this version becomes generally available in early October, you will only be able to download the bits from this KB article.

Requirements

Please confirm that you are running version 9.5 Update 4b (build 9.5.4.2866) or later before upgrading. You can check this under Help | About in Veeam Backup & Replication console. After upgrading, your build number will be 11.0.1.1261.

What's New

Veeam Backup & Replication v11a is the newer build of version 11 that addresses issues reported by customers on the original build and adds the following new features and enhancements:

Platform support

Microsoft Windows Server 2022 and Microsoft Windows 10 21H1 are now supported as guest OS, Hyper-V host, installation of Veeam Backup & Replication components, and agent-based backup with the Veeam Agent for Microsoft Windows 5.0.1 (included in the update).

NOTE: Please avoid upgrading your existing Server 2019 ReFS backup repositories to Server 2022 until Microsoft address the known regression in the ReFS format upgrade code.
Microsoft Windows 11 support readiness for the same. The official support will require full regression testing of the generally available (GA) build when it becomes available. This article will be updated with a support statement once it happens.
Microsoft Azure Stack HCI version 20H2 supported for host-based Hyper-V VM backup.
RHEL/CentOS 8.4, Ubuntu 21.04, Debian 11, SLES 15 SP3, OpenSUSE Leap 15.3, Fedora 34 distributions supported as guest OS, for the installation of Veeam Backup & Replication components, and agent-based backup with the Veeam Agent for Linux 5.0.1 (included in 11a). For the complete list of supported distributions depending on the component, please refer to the System Requirements section of the Release Notes document.
VMware Cloud Director 10.3 support. In addition, with v11a, you can now deploy Veeam Self-Service Backup Portal in environments with multiple Cloud Director servers.
VMware VMC 15 support, including compatibility of VM restore operations with NSX-T 3.0 networks that use VDS 7.0 instead of N-VDS switches.
VMware vSphere 7.0 U3 readiness based on the pre-release build. The official support will require full regression testing of the generally available (GA) build when it becomes available. This article will be updated with a support statement when completed.

Cloud-native capabilities for AWS, Microsoft Azure, and Google Cloud Platform

v11a relies on the new releases of native, cloud-specific Veeam Backup appliances to deliver the following additional functionality:

Native protection of additional services: Expand native backup and recovery to Amazon Elastic File System (Amazon EFS) systems and Azure SQL Databases.
Lowest cost archive storage: Achieve long-term retention goals for cloud-native backups within budgets. New support for Amazon Simple Storage Service (Amazon S3) Glacier, S3 Glacier Deep Archive, Microsoft Azure Archive Storage, and Google Cloud Archive storage cuts data archival costs by as much as 50X.
Increased security and control: Safeguard encrypted backup data from ransomware and other cyber threats. Integrations with AWS Key Management Service (KMS) and Azure Key Vault, as well as new RBAC functionality, increases security with streamlined control over access authorizations.
Fully integrated Google Cloud Platform (GCP) support: GCP VMs protection is now built directly into the Veeam Backup & Replication console. Further, with V11a, customers can now restore image-level backups created by ANY Veeam product directly to a GCP VM for cloud disaster recovery of any workload. With these additions, Veeam now supports centrally managed cloud-native backups and Direct Restore functionality for all three leading hyperscalers.

Instant Recovery to Nutanix AHV

With the new Veeam Backup for Nutanix AHV v3 included in this update, Veeam expands its patented instant recovery functionality to additional hypervisors. Customers can now instantly recover image-level backups created by ANY Veeam product to a Nutanix AHV VM for instant disaster recovery of any workload - cloud, virtual, or physical. This functionality requires Nutanix AHV 6.0 or later.

Centralized management for IBM AIX and Oracle Solaris protection

Veeam Agents for IBM AIX and Oracle Solaris jobs can now be centrally monitored and managed through the integration with Veeam Backup & Replication protection groups of the “Computers with pre-installed agents” type. In addition, you can now perform file-level recovery from such backups in Veeam Backup Enterprise Manager.

Red Hat® Virtualization (RHV) support readiness

With support for a fourth hypervisor in a supported public beta, Veeam Backup & Replication v11a offers reliable integrated backup for Red Hat Virtualization (RHV) 4.4.7 or later so customers can create efficient backups of RHV VMs utilizing native change block tracking and be prepared for any disaster.

Kasten by Veeam K10 integration readiness

With the new integration released as part of Veeam Backup & Replication v11a, K10 and Veeam customers will be able to leverage existing investments in backup infrastructure. The upcoming Kasten K10 v4.5 will be able to direct backups of Kubernetes clusters that leverage VMware persistent volumes to a Veeam Backup & Replication repository where its lifecycle can be managed and additional Veeam features and capabilities leveraged. This article will be updated with any additional requirements once the integration is validated on the K10 v4.5 GA code.

Other Enhancements

Veeam Continuous Data Protect (CDP): improved performance and reduced CPU usage, added better monitoring and reporting for replication conveyor issues, added compatibility with a number of VMware Virtual Volumes (vVOLs) implementations, removed existing limitations on maximum I/O journal size for VMware vVOLs and VMware vSAN target storage.
Improved health check performance: storage-level corruption guard functionality will now also use the advanced data fetcher technology, which should significantly improve its performance on enterprise-grade backup storage hardware.
Elliptic curve cryptography: in addition to data encryption, elliptic curve based keys are now supported for registering Linux servers with Veeam Backup & Replication using the SSH public key authentication method.
Restore directly from Capacity Tier: when a restore process is initiated from backups stored in the Capacity Tier (using the Backups > Object Storage node), we will no longer read matching data blocks from the Performance Tier and instead use solely the data from object storage. This capability can be useful for performing periodic non-disruptive restore tests directly from the cloud without putting your Performance Tier into maintenance mode.
Object storage compatibility: to help object storage devices with limited scalability, you can again enable your backup jobs to use the 8MB block size to reduce the number of objects created. To make this option visible, create the UIShowLegacyBlockSize (DWORD, 1) registry value under the 'HKLM\SOFTWARE\Veeam\Veeam Backup and Replication' key on the backup server. Keep in mind that this option significantly increases incremental backups size and requires an active full backup to be activated.
External repositories: backup server will now detect the presence of new restore points as they appear, instead of having to wait for daily and/or manual rescan to be performed, thus addressing various inconsistencies in the user interface.
Microsoft Azure authentication library: we have switched from ADAL to the recommended and more secure Microsoft Authentication Library. Microsoft plans to discontinue ADAL support entirely in mid-2022.
Microsoft SCVMM: we added the infrastructure caching service to improve the performance of SCVMM-integrated jobs and user interface operations in large Hyper-V environments registered with Veeam via SCVMM server.
VMware vSAN integration: the task scheduler now uses the dedicated threshold of a maximum number of open VM snapshots per vSAN datastores, with the default limit of 32 snapshots. You can control this setting with the VSANMaxSnapshotsNum (DWORD) registry value under the 'HKLM\SOFTWARE\Veeam\Veeam Backup and Replication' key on the backup server.

Licensing

Veeam Backup Enterprise Manager: centralized license management functionality now supports earlier backup server versions (starting from V10).
Rental licensing: Automatic submission of the license usage report was changed from the 11th to the 6th day of the month to better align with the current VCSP program requirements.

Resolved Issues

More Information Soon

As to not delay the Early Availability phase while we're collecting the complete list, this section is a work in progress.

Version 11a includes over 2000 minor enhancements and fixes based on our customers feedback, most significant of which are listed below. It also includes fixes from all cumulative patches for the original V11 release.

Backup performance: addressed a few issues which have caused reduced backup performance with on some backup repositories following V11 upgrade.
Rotated drives: backup jobs targeted at backup repositories with rotated drives should now longer show an error when drives are rotated.
Dell EMC Data Domain integration: DDBoost library was updated to version 7.0.0.22 to address a memory leak; corrected block alignment setting for compressed backups; dropped DDOS 6.1 support (DDOS 6.2 is now the minimum required version).
Dell EMC Unity integration: addressed the issue caused by a recently changed output of one of the Unity API thus enabling support for Unity 5.1 without having to install the corresponding hot fix from Dell EMC.
Windows 10 Enterprise LTSC versions (versions 1507, 1607 and 1809) should no longer be refused as an unsupported OS for installing backup infrastructure components and backup agent.
Tape: users with the Tape Operators role are now allowed to move tapes to a vault.

Download Information

Download 11a RTM ISO

Early Availability Release

↧

VSPC 5 fails to collect Monthly License Usage Report from VBR v11a

September 27, 2021, 1:33 pm

≫ Next: Veeam Explorer for Oracle restore fails with: "You have new mail in /var/spool/mail/root"

≪ Previous: Release Information for Veeam Backup & Replication 11a

KB ID:	4210
Product:	Veeam Service Provider Console 5.0, Veeam Service Provider Console for the Enterprise 5.0

Challenge

Monthly License Usage Report cannot be collected from Veeam Backup & Replication servers running version 11a.

Cause

The Veeam Backup & Replication version 11a license usage data is incompatible with Veeam Service Provider Console (VSPC) v5.

Solution

To resolve this upgrade to VSPC v6 when possible.

Alternatively, the compatibility fix on this article may be installed for VSPC v5 to allow it to collect license usage data from Veeam Backup & Replication 11a.

VSPC v5 Compatibility Fix Installation Instructions:

Ensure VSPC v5 patch 3 (build 5.0.0.6959) is already installed before proceeding.

Download the compatibility fix to the VSPC server
Stop  the following services on the VSPC server:
- Veeam Agent Routing Service
- Veeam Management Portal Service
Replace the files in the folders below with the files found inside the fix:
- C:\Program Files\Veeam\Availability Console\ApplicationServer
- C:\Program Files\Veeam\Availability Console\ApplicationServer\AgentSource
Start the following services on the VSPC server:
- Veeam Agent Routing Service
- Veeam Management Portal Service

Download Information

Download Fix

MD5: 13010569177B4238330D8BBCDB18E57B
SHA-1: EC9F3465FF0AA73654C99BD82E307EE346E246D9

↧

Requirements

Known issues

Download

Challenge

Cause

Solution

More information

Requirements

Known Issues

Purpose

Cause

Solution

How to temporarily disable EWS Throttling Policy

More information

Requirements

Known Issues

Challenge

Cause

Solution

More information

Solution

Requirements

Resolved Issues

General

Backup

Restore

RESTful API

Solution

Veeam Agent for Linux 5.0

Veeam Agent for Linux 4.0.1

Veeam Agent for Linux 4:

Veeam Agent for Linux 3:

Challenge

Cause

Scenario 1: Reinstalled OS

Scenario 2: Different Machines, Same BIOS UUID

Solution

Scenario 1: Reinstalled OS

Scenario 2: Different Machines, Same BIOS UUID

More information

Challenge

Solution

Challenge

Solution

Overview

Limitations

Challenge

Cause

Solution

More information

Requirements

Download Information

Challenge

Cause

Solution

More information

Requirements

What's New

Platform support

Cloud-native capabilities for AWS, Microsoft Azure, and Google Cloud Platform

Instant Recovery to Nutanix AHV

Centralized management for IBM AIX and Oracle Solaris protection

Red Hat® Virtualization (RHV) support readiness

Kasten by Veeam K10 integration readiness

Other Enhancements

Licensing

Resolved Issues

Download Information

Challenge

Cause

Solution

VSPC v5 Compatibility Fix Installation Instructions:

Download Information

Latest Images