Veeam Support Knowledge Base

Challenge

If a Virtual Machine's MoRef is changed due to migration to new vCenter / inventory change in vCenter, you would receive the error "Object "vmname" is not found". Please see KB1299 for more details.

This utility is designed to assist in re-mapping the MoRef ID's of the Virtual Machines you are backing up and/or replicating using Veeam Backup & Replication, so that backup incremental chains remain intact, after an inventory change in VMware vSphere vCenter. Do not run any jobs before using the migration tool otherwise, the migration process won't be possible.

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.

This tool cannot fix jobs targeting a Cloud Connect repository. You must perform and Active Full backup.

Important! If you are migrating to a 6.5U2 VCSA, VMware has a new migration utility, which could preserve existing VM MoRef IDs:
https://blogs.vmware.com/vsphere/2016/09/vcenter-server-migration-tool-vsphere-6-0-update-2m.html
https://blogs.vmware.com/vsphere/2017/01/vcenter-server-appliance-6-5-migration-walkthrough.html
This VMware utility only works for a 5.5 VC to a 6.5U2 VCSA!

Cause

Veeam Backup & Replication tracks Virtual Machines in its jobs by a Managed Object Reference ID (MoRef), which will change when moved to another vCenter, or removed and re-added to inventory.

Solution

Please download this bundle: tool and instructions.
Before using this tool, it is highly recommend to take a configuration backup of your VeeamBackup database.

Note:

The utility will work only with a source vCenter migration. If Replication target vCenter is changed, you will need to manually map source VMs to their replicas.
If for some reason you have already added the new vCenter or ran any jobs which will have added new Ref-IDs to the database, you can roll the Veeam Backup & Replication database back using the Configuration Restore function.

If you use the VMware provided VCSA Migration tool, you will need to remove and re-add VMs to jobs manually through the new VCSA after adding it to Veeam.

VMware highly recommends migrating to a VCSA, as they are phasing out the Windows based vCenter.
https://blogs.vmware.com/vsphere/2017/08/farewell-vcenter-server-windows.html

More Information

MD5 checksum for the archive: 23934878fe5082a0e5f0481e76bfffde

Challenge

You may notice SureBackup job performance degaradation and higher space utilization after upgrading to Veeam Backup & Replication 9.5 U4.

Cause

Upgrade to Veeam Backup & Replication 9.5 U4 has changed the default location for redo logs for verified VMs impacting original Virtual Lab configuration. Originally redo logs (auxiliary files used to keep changes that take place when VMs run in the virtual lab) were stored on a datastore in the virtual environment specified in the Virtual Lab wizard, but in Veeam Backup & Replication 9.5 U4 redo logs are stored on the vPower NFS server by default.

Solution

The hotfix provided here is intended for customers with Virtual Labs existing prior to the update. The hotfix will revert the changes made in U4 and forces SureBackup VM's redo logs to be written to the datastore which was chosen in the Virtual Lab settings. As an alternative you may choose to create new Virtual Lab(s) and reconfigure existing SureBackup jobs to use the newly configured Virtual Lab and remove the old Virtual Lab.

Ensure that all jobs are in a stopped state.
Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
Rename the Veeam.Backup.Model.dll file to Veeam.Backup.Model.dll_backup
Replace the files listed in the previous step with those found in the hotfix package
Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )

More Information

[[DOWNLOAD|DOWNLOAD PRIVATE FIX|https://storage.veeam.com/Fix_159335_89a18468cf.zip]]
MD5 for Veeam.Backup.Model.dll: 8fe3a782a42094b248a3321af1f9d54f
SHA256 for Veeam.Backup.Model.dll: deaaaff1d42d30e41fc19d9f9dba6efebc0e2c0277aa0c7992076760868f7fbf

Challenge

After updating Veeam to 9.5 Update 4, backups of VMs from ESXi 5.0 and 5.1 licensed with VMware Essentials licensing starts to fail with the following error: "VDDK error: 16064 (The host is not licensed for this feature)"

Cause

Regression in the VMware VDDK 5.5.5 specific to vSphere ESXi 5.0 or 5.1 hosts which are licensed with the VMware Essentials license.

Solution

Veeam is currently in the process of developing a hotfix for this issue. As a workaround, applying an Evaluation License on the hosts, will allow backups to resume normally until a hotfix that brings back an earlier VDDK version is created.

Challenge

You are looking for an official information on Azure Data Box support in Veeam Backup & Replication.

Cause

This article guides you through all the requirements you need to meet in order to leverage Azure Data Box features in Veeam Backup & Replication U4.

Solution

Please complete all the steps to successfully add Azure Data Box into Veeam Backup & Replication:

NOTE: Please make sure that your Azure Data Box device supports data upload over REST API.

1. Ensure Azure Data Box server DNS name is resolved on Veeam Backup Server and Veeam Gateway server either globally in your organization over you DNS servers or individually on the servers over hosts files:

<mydataboxno>.microsoftdatabox.com;
blob.<mydataboxno>.microsoftdatabox.com;
<storageaccountname>.blob.<mydataboxno>.microsoftdatabox.com

where <mydataboxno> and <storageaccountname> could be found in Azure Data Box web UI (please follow this link for more infromation)

2. Please download Azure Databox SSL certificate and import on Veeam Backup Server and Veeam Backup Gateway Sever as described in this link

3. Please open C:\Program Files\Veeam\Backup and Replication\Backup\AzureStorageRegions.xml, find Azure Region you’re not going to use (Azure Government, for instance), modify BlobEndpoint property, as shown below, and specify any display name in the Name property (Azure Databox, for instance):

<Region Id="AzureGovernmentCloud" Name="Azure Databox" Type="Government">
<BlobEndpoint>.blob.mydataboxno.microsoftdatabox.com</BlobEndpoint>
</Region>

4. Please add registry key on Veeam Backup Server:

Name: ObjectStorageCRLCheckMode
Type: DWORD.
Value: 3
Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\

5. Restart Veeam Backup Service on Veeam Backup Server.

Challenge

After upgrading to Veeam Backup & Replication U4, Veeam vPower NFS datastore location might be changed, because in Update 4 the disk with the biggest capacity is selected by default.

Cause

This is a known issue in the Veeam Backup & Replication U4.

Solution

Please update the path to Veeam vPower NFS datastore manually in the Backup repository wizard for each reposiotry. Feel free to refer to our helpcenter for more information.

Challenge

Product Information:

Company name: FAST LTA AG
Product Family: Silent Brick System VTL
Status: Veeam Ready - Tape
Classification Description: Tape solution where available hardware features have been tested to work with Veeam.

Solution

Product Details:

Model number: Silent Brick VTL
Library Firmware Version 2.15.0.10
Drive firmware version: Virtual drives, Library Version 2.15.0.10
Driver for tape drive: IBM Ultrium
Driver for media changer: Adic Scalar 1000 or (Veeam Option: Use native SCSI commands instead of Windows driver)
Media type tested: Silent Brick

General product family overview:
Simplify your backup with Silent Bricks. On-premise storage appliances with integrated data protection for all NAS and VTL requirements. Media replication and rotation. Online, offline and off-site, with support for air gap environments. All in one system. The Silent Brick System is based on modular and transportable storage units called 'Silent Bricks' where each Silent Brick consists of 12 Disks. Depending on the Silent Brick Type these disks may be HDD (Silent Brick ) or SSD ( Silent Brick FLASH ). Virtual Tape Library implementation based on highly secured and transportable storage containers holding 12 HDDs each with a redundancy of 4 physical disks per virtual tape. Although the VTL is disk based it features real offline and offsite capabilities, encryption and compression.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1922

Vendor recommended configuration:

Vendor Settings:

Set tape block size to 1MB in registry prior to tape init / deletion
Set drive block size to 1MB in Veeam prior to tape init / deletion
If used via iSCSI set iSCSI max transfer length to 1MB prior to tape init / deletion
Enable ‘use native scsi commands’ on the Media Changer in Veeam in order to improve overall tape handling.

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TS-x77XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TS-2477XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 20 – 1TB SATA HDD
Storage configuration: RAID6, no SSD caching
Firmware version: 4.3.5.0760
Connection protocol and speed: SMB 10GbE
Additional support: All models and configurations of TS-2477XU with specifications equivalent or greater than the above

General product family overview:

Powered by AMD’s powerful Ryzen™ processor, the TS-2477XU-RP is capable of boosting virtual machine performance with up to 8 cores/16 threads and Turbo Core up to 4.1 GHz. Four PCIe Gen.3 slots provide expandability to provide more potential applications and functionality for the TS-2477XU-RP. The TS-2477XU-RP also features a redundant power supply to ensure maximum system uptime.

Veeam testing configuration:

Note: The following settings were used by the vendor to meet Veeam Ready testing requirements and should not be considered best practices. Additional changes or settings may be needed to meet the storage efficiency or performance needs for each environment. For each setting, reference links are provided for further clarification.

Veeam Build Number: 9.5.0.1922

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder (CIFS)
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

No array deduplication used in testing
No array compression used in testing
Jumbo frames used in testing (MTU=9000)

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TS-x83XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TS-1683XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 16 – 1TB SATA HDD
Storage configuration: RAID6 configured, no SSD caching
Firmware version: 4.3.6.0805
Connection protocol and speed: SMB, 10 GbE
Additional support: All models and configurations of TS-1683XU with specifications equivalent or greater than the above

General product family overview: The Intel® Xeon® E based TS-1683XU-RP enterprise NAS with up to 64GB DDR4 ECC (Error Correcting Code) memory delivers server-grade performance with dependable reliability. It features Mellanox® ConnectX®-4 Lx 10GbE controllers that not only fulfill bandwidth-demanding applications but also support iSER to offload CPU workloads with boosted virtualization performance, while PCIe expansion allows for installing graphics cards to empower video surveillance, virtualization and AI applications.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1922

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder (CIFS)
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

No Array deduplication used in testing
No array compression used in testing
Jumbo frames used in testing (MTU=9000)

Challenge

Product Information:

Company name: QNAP Systems, Inc.
Product Family: TVS-x72XU
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

Solution

Product Details:

Model number: TVS-1672XU
Storage Category: RAID Storage Array
Drive quantity, size, type: 16 – 1TB SATA HDD
Storage configuration: RAID6 configured, no SSD caching
Firmware version: 4.4.0.0767
Connection protocol and speed: SMB, 10 GbE
Additional support: All models and configurations of TVS-1672XU with specifications equivalent or greater than the above

General product family overview:

Designed for diversified business IT environments, the TVS-1672XU-RP features an 8th generation Intel® Core™ processor, Mellanox® ConnectX®-4 Lx 10GbE controller, and PCIe expansion for 25GbE / 40GbE connectivity to boost intensive large file sharing, heavily-loaded backups, or virtualization applications. PCIe expandability also allows for installing graphics cards to empower AI workflows and video transcoding, and the 4K HDMI 2.0 output can display surveillance videos on a monitor or TV to improve surveillance management. The TVS-1672XU-RP also features a redundant power supply to ensure maximum system uptime.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1922

Job Settings:

Deduplication:	Enabled (Default)
Compression:	Optimal (Default)
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	Shared Folder (CIFS)
Align backup file blocks:	Disabled (Default)
Decompress before storing:	Disabled (Default)
Per-VM Backup Files:	Disabled (Default)

Vendor recommended configuration:

Hardware Settings:

No Array deduplication used in testing
No array compression used in testing
Jumbo frames used in testing (MTU=9000)

Challenge

After installing Veeam Backup & Replication 9.5 Update 4, Hyper-V backup without application-aware processing may fail with the error "The system cannot find the file specified".

Cause

This issue is caused by the snapshot path in the VM 's configuration being different from the actual path on a file system in terms of symbols capitalization. You can confirm this by comparing paths in bold in the Task.<VM NAME>.<VM UUID>.log file:

[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <snapshots>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <data_root type="string">C:\Temp\<VM name></data_root>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: <size type="integer">0</size>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </list>
[22.01.2019 19:39:09] <28> Info [AP] (65e8) output: </snapshots>

[22.01.2019 19:39:09] <11> Info [AP] (65e8) command: 'file2text\n\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml\n2097152\n'
[22.01.2019 19:39:10] <10> Info [ReconnectableSocket] Stop confirmation was sent on [c1d84e94-b09b-4039-a8dc-4973e12934fc].
[22.01.2019 19:39:10] <23> Error [AP] (65e8) error: The system cannot find the file specified.
[22.01.2019 19:39:10] <23> Error Failed to open file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\temp\<VM NAME>\Snapshots\<VM UUID>.xml] in readonly mode.

Solution

There are two methods for correcting this issue depending on your preference:

1. Change snapshot path in VM configuration manually:

Connect to the Hyper-V host and go to VM Configuration of VM in question;
Go to Checkpoints tab and choose ‘Browse…’ underneath the snapshot path;
Update the path.

2. Install a hotfix for Veeam Backup & Replication 9.5 Update 4 (build 9.5.4.2615):

Ensure that all jobs are in a stopped state.
Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
Rename the Veeam.Backup.Core.dll file to Veeam.Backup.Core.dll_backup
Replace the files listed in the previous step with those found in the hotfix package
Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )

More Information

[[DOWNLOAD|DOWNLOAD PRIVATE FIX|https://storage.veeam.com/Fix_159310_2015be7f9e.zip]]
MD5 for Veeam.Backup.Core.dll: a0d5b70a85f9b5086d297bf2267d8bb5

Should you have any questions, contact Veeam Support.

Challenge

When trying to add a Linux server to the Veeam Backup & Replication console, you get the following error:

Failed to login to "xxx.xx.xx.x" by SSH, port 22, user "root"
elevateToRoot False, autoSudo False
User authentication failed

However, it is possible to log on to this server with the same credentials using an SSH client.

Cause

The configuration of your SSH server does not allow using tunnelled clear text passwords.

Solution

Open the SSHD config file (usually, /etc/ssh/sshd_config) on the Linux server.
Find the PasswordAuthentication parameter and set its value to “yes”.
Restart SSHD on the Linux server (usually, /etc/init.d/sshd restart).
Try adding the server to the console again.

More Information

Another solution is to use the Identity/Pubkey authentication method.
https://helpcenter.veeam.com/docs/backup/vsphere/credentials_manager_linux_pubkey.html?ver=95u4

Challenge

After installing Veeam Backup & Replication 9.5 Update 4, Hyper-V backup without application-aware processing may fail with the error "The system cannot find the file specified".

Cause

Solution

There are two methods for correcting this issue depending on your preference:

1. Change snapshot path in VM configuration manually:

Connect to the Hyper-V host and go to VM Configuration of VM in question;
Go to Checkpoints tab and choose ‘Browse…’ underneath the snapshot path;
Update the path.

2. Install a hotfix for Veeam Backup & Replication 9.5 Update 4 (build 9.5.4.2615):

Ensure that all jobs are in a stopped state.
Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
Rename the Veeam.Backup.Core.dll file to Veeam.Backup.Core.dll_backup
Replace the files listed in the previous step with those found in the hotfix package
Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )

More Information

Challenge

To configure Linux guests and repositories to work with Veeam Backup and Replication and utilize our software’s features.

Cause

There are several requirements that must be met, by a Linux OS, in order for us to effectively utilize all of our features and make sure they run consistently. On top of that we require root permissions to launch several modules. If these settings are not in place, then we won’t be able to properly write to and recover the system.

Solution

Authentication Methods

Linux servers registered with Veeam Backup & Replication infrastructure must use Password or Certificate-based authentication methods. At this time we do not support any other forms of authentication like biometrics, smart cards, etc.

Bash

We require Bash to be installed as shell on the Linux environment. At the time we do not support any other command shell. This is usually the default shell set in place by most Linux distributions.

"sudo"

Important Note: accounts using "sudo" must be in the "/etc/sudoers" file and have the ‘nopasswd’ setting put into the "/etc/sudoers" file.

In order to launch our script we require the "sudo" command to be able to launch from the credentials we are given at the time of setup. "sudo" is a command that allows us to make administrator level (root) changes and executions in the Linux environment.

One of the primary reasons that we use "sudo" is to make sure that we can access the /tmp folder and launch a script from it. There are many other ways you can launch scripts from the "/tmp" folder but "sudo" is the most consistent way across multiple distribution’s to do it. This also allows us to complete the operation without having change user permissions so the user doesn’t have to modify them afterword’s to get them back to their original configuration, as well as we will be able to relinquish root privileges on the fly.

Perl

Many Linux distributions come with Perl pre-installed but this does not mean that it has all the Perl modules that are required for us to utilize the server in a backup and restore function and once all of the correct modules are install we must be able to launch these modules as needed. Some systems are setup with software called SELinux. This software will make it so that only certain modules can be launched from SSH. The Linux distribution must allow us to launch all of these modules from "SSH" at any amount at a time.

Here is a list of the modules that we require for Veeam to work properly with a Linux install:

Constant
Carp
Cwd
Data::Dumper
Encode
Encode::Alias
Encode::Config
Encode::Encoding
Encode::MIME::Name
Exporter
Exporter::Heavy
File::Path
File::Spec
File::Spec::Unix
File::Temp
List::Util
Scalar::Util
SOAP-Lite
Socket
Storable
Threads

You can find out which modules are installed by running:

perldoc -q installed

One of the most widely used Linux distribution’s currently is CentOS 6/7 and in this distribution the "Data::Dumper Perl" module is not installed by default.

SSH

SSH is a program for logging into a remote machine and for executing commands on a remote machine. This is software that we use to log in to a Linux environment. Most systems have this software installed by default but if the Veeam server is having issues logging into a Linux environment you should check if SSH is installed.

The configuration of your SSH install must allow using tunneled clear text passwords. Info on how to do this can be found on this KB: http://www.veeam.com/kb1512

SCP

SCP copies files between hosts on a network. It uses SSH for data transfer, and uses the same authentication and provides the same security as SSH. We use this software as our file mover on Linux. It is common for Centos core to not include this SCP module in the default install.

"mlocate", "gzip" and "tar"

"mlocate" is a new implementation of locate, a tool to find files anywhere in the file system based on their name, using a fixed pattern or a regular expression. We utilize "mlocate" to locate files on a Linux system.

"gzip" and "tar" are archive tools very much like WinZip. We use these to compress and decompress files going to and from the server.

All of these files and their required configurations must be installed on the Linux environment prior to its usage with Veeam Backup and Replication to fully use all of our features.

More Information

http://www.veeam.com/kb2007 merged

Challenge

Release Notes for Pure Storage Plug-In for Veeam Backup & Replication 1.1.40

Cause

Please confirm that you are running version 9.5.0.1536 or later prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console.

Solution

This update features the following enhancements:

Added support for volume snapshots created as part of a Pure Storage Protection Group.

This update also resolves most common support issues including the following:

The default HTTP timeout value was Increased from 5 to 60 seconds to make the plug-in more resilient to network issues.
vVol volumes are no longer displayed in the list of volumes.

More Information

[[DOWNLOAD|DOWNLOAD UPDATE|https://www.veeam.com/download_add_packs/vmware-esx-backup/purestorage/]]

MD5 checksum for PureStoragePlugin_1.1.40.zip is 8b88b326613cd1658d46b17050dfc6fb

Challenge

To configure Linux guests and repositories to work with Veeam Backup and Replication and utilize our software’s features.

Cause

Solution

Authentication Methods

Bash

We require Bash to be installed as shell on the Linux environment. At the time we do not support any other command shell. This is usually the default shell set in place by most Linux distributions.

"sudo"

Perl

Constant
Carp
Cwd
Data::Dumper
Encode
Encode::Alias
Encode::Config
Encode::Encoding
Encode::MIME::Name
Exporter
Exporter::Heavy
File::Path
File::Spec
File::Spec::Unix
File::Temp
List::Util
Scalar::Util
SOAP-Lite
Socket
Storable
Threads

You can find out which modules are installed by running:

perldoc -q installed

One of the most widely used Linux distribution’s currently is CentOS 6/7 and in this distribution the "Data::Dumper Perl" module is not installed by default.

SSH

SCP

"mlocate", "gzip" and "tar"

More Information

http://www.veeam.com/kb2007 merged

Challenge

You need to remove an existing Veeam Backup and Replication (VBR), Veeam Agent for Windows (VAW) or Veeam Agent for Linux (VAL) license from Veeam Backup and Replication (VBR) or Enterprise Manager (EM).

Cause

A license has to be removed from VBR/EM.

Solution

NOTE: Starting from Veeam Backup & Replication Update 4 it is no longer possible to remove a license from Enterprise manager or delete individual product sections (vbr,vaw,val) from the license.

In order to determine which section of this article to use, you must know if Enterprise Manager is controlling the licenses within Veeam Backup & Replication. If you are unsure, attempting to change the license file within Veeam Backup & Replication will tell you. If it allows you to click the Install button within the license section without a message about Enterprise Manager then Enterprise Manager is not in use.

If licenses are managed by Enterprise Manager:

NOTE: Only for versions prior 9.5 Update 4

Open an administrative command prompt.
Navigate to the EM installation folder (default path in the example below):
```
cd C:\Program Files\Veeam\Backup and Replication\Enterprise Manager
```

Remove the license by running

Veeam.Backup.EnterpriseService.exe -removelicense [vaw, val]

After running this command, restart Veeam Backup Enterprise Manager service so that the license information is updated in the UI.

If licenses are managed by Veeam Backup & Replication

Open an administrative command prompt.
Navigate to the VBR installation folder (default path in the example below):
```
cd C:\Program Files\Veeam\Backup and Replication\Backup
```

Remove the license by running

Veeam.Backup.Manager.exe -removelicense [all, vbr, vaw, val]

More Information

Note: These commands can also be run from PowerShell.

Note: specify the desired parameter without brackets.

Example commands:

To remove the Veeam Agent for Windows license from Veeam Enterprise Manager:
```
Veeam.Backup.EnterpriseService.exe -removelicense vaw
```
To remove Veeam Agent for Linux from Veeam Backup & Replication:
```
Veeam.Backup.Manager.exe -removelicense val
```

If no parameter is specified, all existing licenses will be removed.

Challenge

This KB article is to create merged licenses that are for Veeam Backup & Replication v9.5 Update 3a and earlier. For Veeam Backup & Replication 9.5 Update 4, please follow this guide: https://www.veeam.com/kb2879

This KB only applies to versions Veeam Backup & Replication v9.5 U3a and earlier, Veeam ONE v9.5 Update 3a and earlier, and Veeam Agents v2.

A license file installed to your Veeam software replaces the information from the previous license. A merged license file allows for increased socket capacity by combining licenses from multiple Support IDs.

Please note that the merged license key will use the earliest support expiration date of all product keys.

Solution

NOTE! Licenses can be merged only when they have the same:

Account Name
Product Name and Edition
Product Version
Licensing Terms
License Administrator
They must all be Active on Support.

Your License Administrator may obtain a merged license file by following the steps below.

Log on to the Veeam My Account dashboard and go to License management >> Production Licenses (https://my.veeam.com/#/licenses/production)
In the Action column for the appropriate product, select Merge
From this page, select each of the boxes to the left of all the individual licenses you would like to merge
In the box that appears below, select the appropriate version of the key for your software and whether you would like to download the license directly or have a copy of the key emailed to your License Administrator email.

More Information

Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.

Challenge

This KB article is to create merged licenses for Veeam Backup & Replication 9.5 Update 4 and later only. If you require a merged license for v9.5 Update 3a or earlier, OR IF YOU HAVE ONLY PERPETUAL LICENSING, please follow this guide: https://www.veeam.com/kb1718

This KB only applies to versions Veeam Backup & Replication v9.5 U4 and later, and Veeam Agents v3.

This article describes the process of merging Veeam licenses.

Cause

A license file installed in your Veeam software replaces the information from the previous license. A merged license file allows for increased socket capacity by combining licenses from multiple Support IDs.

Please note that the merged license key will use the earliest support expiration date of all product keys.

Important: Only License Administrators can merge licenses.

Solution

NOTE! Licenses can be merged only if the following terms match:

Perpetual License Keys

•   First name, Last name, Email, Company for Perpetual License Keys
•   Edition
•   License Type
•   Product name

Subscription License Keys

•   Licensee company, Licensee e-mail, Licensee first name, Licensee last name
•   Edition
•   License Type

Your License Administrator may obtain a merged license file by following the steps below.

1.   Log on to the Veeam My Account dashboard and go to License management >> Production Licenses(U4) (https://my.veeam.com/#/licenses/u4-licenses)

2.   If you are managing multiple accounts, please select the account you are performing the merge for. Once you have made the selection all the products under the account will be visible.
User-added image

3. To start the merge process, please use the License merge link:
User-added image

4. Now you can select the Products and the contracts you want to merge. You can select several compatible product licenses to merge into one license file.
User-added image

5. After you have selected the contracts you want to merge, you will have to click the Preview button to view the new licenses information.
User-added image

6. After you have verified the information’s of the page you will have to use the “Merge Licenses” button to finalize the merge process.

More Information

1.   To revert the License Key merge operation, Customers may choose “Cancel merge” to destroy the merged license and revert to original product License Keys.
2.   License Key split option on the Customer portal is available to selected Customers only. All contract split operations require opening a licensing support case at https://my.veeam.com.
3.   Please note that the license auto-update feature does NOT correctly update merged licenses created on the license management portal. If you have enabled auto-update, disable it before installing a merged license from the license management portal.
4.   More info about the merge policy here.

Challenge

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

Cause

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

Red Hat Enterprise Linux version	VAL build number	Kernel supported up to
7.x	3.0.0.865	3.10.0-957.5.1
6.x	3.0.0.865	2.6.32-754.9.1

Challenge

Product Information:

Company name: Oracle Inc, America
Product Family: Oracle ZFS Storage Appliance
Status: Veeam Ready - Repository
Classification Description: Verified backup storage that supports all Veeam backup and restore features.

*This Veeam Ready test was performed with storage having a configuration that includes SSD/Flash. As such, this classification only applies to similar configurations in which the same amount or more SSD drives are used. The use of non-SSD drives may negatively impact performance.

Solution

Product Details:

Model number: ZS5-4
Storage Category: Hybrid Storage
Drive quantity, size, type: 80 - 7200 RPM 8TB HDD | 4 - 200GB SSD Write Cache | 2 - 3.2TB SSD Meta Device
Storage configuration: ZFS RAID single parity, narrow stripes w/ 4 write cache SSDs in mirrored profile w/ 2 meta device SSDs in striped profile (for deduplication)
Firmware version: OS 8.8.x
Connection protocol and speed: SMB/CIFS, ISCSI, or NFS | 10GbE
Additional support: All models and configurations of ZFS Storage Appliance models with specifications equivalent or greater than the above

General product family overview:

Oracle ZFS Storage Appliance is a powerful multi-protocol, multi-purpose, enterprise class storage solution that provides the flexibility for both primary and backup storage. Features such as variable compression, data deduplication, and large (1M) block sizes enables efficient, high throughput data storage for backup environments.

Veeam testing configuration:

Veeam Build Number: 9.5.0.1922

Job Settings:

Deduplication:	Disabled
Compression:	None
Storage Optimization:	Local Target (Default)

Repository Settings:

Repository Type:	iSCSI: Windows \| NFS: Linux \| SMB/CIFS: Shared Folder
Align backup file blocks:	Enabled
Decompress before storing:	Enabled
Per-VM Backup Files:	Enabled

Vendor recommended configuration:

Hardware Settings:

Array deduplication used in testing – yes
Array compression used in testing – yes (LZ4)
Jumbo frames used in testing (MTU=9000)

Challenge

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.This tool cannot fix jobs targeting a Cloud Connect repository. You must perform and Active Full backup.

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

Cause

Solution

Challenge

Product Information:

Solution

Product Details:

Veeam testing configuration:

Vendor recommended configuration:

Challenge

Product Information:

Solution

Product Details:

Veeam testing configuration:

Job Settings:

Repository Settings:

Vendor recommended configuration:

Challenge

Product Information:

Solution

Product Details:

Veeam testing configuration:

Job Settings:

Repository Settings:

Vendor recommended configuration:

Challenge

Product Information:

Solution

Product Details:

Veeam testing configuration:

Job Settings:

Repository Settings:

Vendor recommended configuration:

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

More Information

Challenge

Cause

Solution

If licenses are managed by Enterprise Manager:

If licenses are managed by Veeam Backup & Replication

More Information

Challenge

Solution

Please note that this utility is provided as a courtesy, and is not supported by Veeam Technical Support. Use at your own risk.

This tool cannot fix jobs targeting a Cloud Connect repository. You must perform and Active Full backup.