Challenge

Cause

Solution

ssh -i "<backup server's .pem key>" ubuntu@<Public DNS (IPv4) parameter of the backup server>

<Region Id="me-south-1" Name="Middle East (Bahrain)" Type="Global">
    <Endpoint Type="S3">s3.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="S3">s3.dualstack.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="EC2">ec2.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="IAM">iam.amazonaws.com</Endpoint>
    <Protocol>HTTP</Protocol>
    <Protocol>HTTPS</Protocol>
    <LocationConstraint>me-south-1</LocationConstraint>
    <SignatureVersion>4</SignatureVersion>
  </Region>

sudo systemctl restart veeamawsbackup.service

Challenge

Cause

• Veeam Backup & Replication, version 9.5 and higher.
• Veeam Cloud Connect, version 9.5 and higher.
• Veeam Cloud Connect for Enterprise, version 9.5 and higher.

Solution

https://helpcenter.veeam.com/docs/one/monitor/intelligent_diagnostics.html?ver=95u4

When opening a case based on a VID alarm received in Veeam ONE, please remember to fill the signature UID field with the relevant identifier.

More Information

Challenge

Cause

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

• Support for port binding (iSCSI protocol).

More Information

Challenge

Cause

Before installing this update, make sure you are running Veeam Backup & Replication version 9.5.0.1536 or later.

To check the version, do the following:

1. Open the Veeam Backup & Replication console.
2. In the main menu, click Help and select About.

Solution

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

• 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

Challenge

Cause

Solution

Challenge

Solution

Legend

Single Key Scenarios

* Includes “free” built-in instances (up to 6) to allow evaluation of Veeam Availability Suite (Non-VMs workloads only).

Merged Key Scenarios

Rental keys

Challenge

Cause

What’s New 

• Support for Veeam Backup & Replication v10 compatibility.
• Support for Veeam Cloud Connect v10 compatibility. 

• Veeam Backup for Microsoft Office 365 version 4.0.0.2516 is applicable to:
  • standalone installations of Veeam Backup for Microsoft Office 365
    • version 2.0 (builds 2.0.0.567, 2.0.0.594 and 2.0.0.814)
    • version 3.0 (builds 3.0.0.422 — 3.0.0.480)
    • version 4.0 (build 4.0.0.1345)
    • version 4a (build 4.0.0.1553; see KB3035 for more details)
  • installations on top of Veeam Backup & Replication v10 and Veeam Cloud Connect v10.
• Version 4.0.0.2516 is NOT applicable to installations on top of
  • Veeam Backup & Replication 9.5 Update 4, 4a or 4b
  • Veeam Cloud Connect 9.5 Update 4, 4a or 4b
• Upgrading backup repositories from version 3.0 to 4b may take significant time to complete and the upgrade duration highly depends on the amount and type of backup data in a repository. According to the test results, it may take up to 8 hours in the setup with 1 TB of data in a backup repository. Plan for an appropriate maintenance window when your backup repository that is been upgraded is not available for use. Note that upgrading version 2.0 repositories to 4b requires a bigger maintenance window due to many underlying changes to backup repositories. The upgrade process requires an additional 15% of free space of the current 2.0 repository size and may take up to 17 hours per 1 TB of data in a backup repository. 

Resolved Issues

• Retention jobs do not fully purge the outdated service data, which causes product configuration database growth and impacts product upgrade duration. 

• Adding users with empty Display Names to a backup job fails with the “Value cannot be null” error. 
• Backup of user’s OneDrive fails if the user name has been changed.  
• Backup job containing excluded SharePoint sites with changed URLs fails with the following warning: “Failed to get site collection: {url}. Access denied. You do not have permission to perform this action or access this resource.” 

• Backing up public folders to a repository extended with object storage may fail with the following error: “This id is of the wrong type for this conversion operation (mailbox id vs. public folder id).”
• Adding OpenStack Swift (Stein) S3 Compatible object storage repository with the s3api middleware for S3 REST fails with the “Unable to create folder (name: {0})” error.
• Backup and retention jobs targeted at repositories extended with Amazon S3 object storage may fail with the “Specified argument was out of the range of valid values. Parameter name: count” error.
• If an Azure storage container that is in use with an object storage repository has been deleted, the corresponding backup repository is put into the Invalid state and the backup proxy disk usage is at 100%.
• A repository extended with Azure Blob Storage is still available for use (i.e. it’s not put to an Invalid state) when Azure storage account credentials become invalid. 
• After changing retention period for a repository extended with object storage, backup jobs targeted to this repository stop processing.

Solution

1. Download the ZIP archive: VeeamBackupOffice365_4.0.0.2516.zip.
2. Run the Veeam.Backup365_4.0.0.2516.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Backup for Microsoft Office 365.
3. Run the VeeamExplorerForExchange_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft Exchange. 
4. Run the VeeamExplorerForSharePoint_10.0.0.443.msi from the downloaded ZIP archive and follow the wizard steps to install Veeam Explorer for Microsoft SharePoint. Note that Veeam Explorer for Microsoft OneDrive for Business is distributed in one package with Veeam Explorer for Microsoft SharePoint and will be installed automatically.   

More Information

Challenge

Solution

Legend

Single Key Scenarios

* Includes “free” built-in instances (up to 6) to allow evaluation of Veeam Availability Suite (Non-VMs workloads only).
 

Merged Key Scenarios

Rental keys

Challenge

Cause

What’s New:

• Veeam Backup & Replication v10 compatibility support
• Veeam Cloud Connect v10 compatibility support

New fixes:

• Usage report is not collected from the Veeam Backup Enterprise Manager (EM) unless the report is manually approved in the EM.

• Operators cannot edit or change a cloud repository for a sub-tenant.
• Operators cannot log in to the portal when using local user accounts in Windows. 

• Under certain conditions, information about available restore points cannot be collected from the backup agent. 

• Management agent service fails to start when the computer or Cloud Connect server is renamed.

• Under certain conditions, physical computers are reported as hosted in a cloud.

• Under certain conditions, the alarm assignment is reset to the default scope for a reseller account.
• Under certain conditions, the “Computer without backup” alarm triggers a false-positive alert.
• Backup copy job state reports only on the previous job run, not the latest one.

• The number of managed VMs is reported incorrectly for the socket-based license keys.
• Under certain conditions, tickets triggered by Veeam Availability Console alarms are duplicated in the ConnectWise Manage application.

• $top and $skip filters cannot be applied when using the “GET /v2/backupAgents” endpoint.

• Cloud Connect server with a merged perpetual license key cannot be added to Veeam Availability Console.

Fixes included from previous patches:

• “/v2/tenants” get request does not display the “deleted” status for removed companies. 
• Querying “v2/tenants/{id}” and “/v2/tenants/{id}/backupResources” information may take considerable amount of time. 
• A backup policy cannot be created if there are “space” symbols in the encryption hint. 
• A backup policy cannot be created when “processingEnabled” parameter is set to True, and “Credentials” parameter is used.
• Querying tenant information with SetLinks parameter may take considerable time.
• The vMsBackudUpToCloud counter does not display data about VM and Agent backup copy jobs targeted to a cloud repository.  

• After applying a backup policy to a managed Agent, job scheduling settings are displayed incorrectly in the VAC UI, but the settings pushed to the Agent are correct. 
• Site administrators can select Public IP Addresses belonging to a different site when creating a company. 
• Under certain conditions, “Used Storage” counter may display incorrect data on the “Overview” tab.
• Cloud Copies counter on the Overview dashboard does not return any data.
• Backup agents managed by Veeam Backup & Replication report 0 restore points available in the backup policy drill down view. 

• Management agent installed on a Cloud Connect server is incorrectly displayed on the Backup Agents tab. 
• Under certain conditions management agent restarts every hour. 
• Under certain conditions, management agents fail to upgrade with the following error message “The system cannot find the file specified.”

• Network Extension IP addresses are not filtered by a reseller. Reseller can select IP addresses belonging to unmanaged companies. 
• Reseller can change his or her backup quota to “unlimited” when creating a managed company with “unlimited” quota.

• Only the first 10 000 products are displayed in the mapping area of the plugin. 
• Plugin services may consume excessive memory when there are a lot of tickets created in the ConnectWise Manage application.
• Cloud repository usage is not updated in ConnectWise Manage agreements when there are unknown files (not related to Veeam backups) in the repository. 
• Tickets state synchronization may stop working when triggering a mass-resolve operation in the ConnectWise Manage application. 

• Platform type cannot be detected for old computers and is reported as “Other.”
• Inaccessible computers cannot be located when using CSV and IP discovery rule options.

• Under certain conditions after installing a private hotfix Veeam.MBP.Service fails to connect to the existing database with the following error message ”Cannot change configuration database: Database version is invalid.” 
• Veeam.MBP.Service fails to start when managed backup agents have duplicate IDs (due to cloning operation) in the configuration database.
• Under certain conditions, Veeam.MBP.Service might be consuming excessive memory.
• Under certain conditions, data collection job fails to retrieve information from a Cloud Connect server that has lots of task sessions on cloud gateway servers. This results in displaying these tenants’ companies as deleted in the Veeam Availability Console UI.
• Tenant password changed in Veeam Cloud Connect is not synchronized with Veeam Availability Console.

• “VM without backup” alarm is triggered for VMs that are migrated between vCenter Servers or are re-registered in the virtual infrastructure.

• Under certain conditions, the management agent may connect to VAC server without authentication.

• Computer renaming leads to duplicated values in the Protected Computers report.

• Under certain conditions, usage report for managed Veeam Backup & Replication servers may not be created within first ten days of a month.
• Workstation and server backup counters in the Veeam Cloud Connect usage report are mixed up.
• Under certain conditions License usage report for Veeam Backup & Replication servers is not generated. 

Login

• Portal administrators can log in only when using a full domain name of the Veeam Availability Console server. 
• Users belonging to a domain user group which is added to a Veeam Availability Console security group cannot log in to the portal.
• Users belonging to a nested domain group cannot log in to the portal.

• Office 365 and Gmail SMTP servers are not supported for notifications.  

• Full Access UI mode cannot be applied to a backup agent.  
• When using Select All checkbox on the Managed Backup Agents tab agent settings are applied to all computers of all managed companies regardless of the selected scope in the Company\Reseller filter.  
• Licensing attribute is not updated for managed backup agents which leads to license expiration on the backup agent.    
• Backup agent files are not validated when the installation is performed from a local folder without using a master management agent. This may result in a corrupted installation/upgrade of the backup agent. 

• Under certain conditions, all VMs with a cloud copy which belong to different locations are reported as VMs from the default location in the invoice.

Solution

msiexec /update c:\VAC.ApplicationServer.x64_3.0.0.2795.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACApplicationServerSetup.txt

msiexec /update c:\VAC.WebUI.x64_3.0.0.2795.msp /l*v C:\ProgramData\Veeam\Setup\Temp\VACWebUI.txt

msiexec /update c:\VAC.ConnectorService.x64_1.0.1.616.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorService.txt

msiexec /update c:\VAC.ConnectorWebUI.x64_1.0.1.616.msp /l*v C:\ProgramData\Veeam\Setup\Temp\ConnectorWebUI.txt

More Information

Challenge

• Your VMware vSphere license includes the Storage vMotion feature because in this case, Veeam will finalize Instant VM Recovery using this technology, OR
• You installed Update 4b after the update availability notification in Veeam Backup & Replication™ console in January 2020 (or in December 2019 through the 20191210 distribution package).

• If you upgraded to Update 4b prior to version 20191210 availability, or if you are not sure when you upgraded, please download and install the patch from this KB article.
• If you are running Update 4a (build 9.5.4.2753) or Update 4 (build 9.5.4.2615), please download and install Update 4b 20191210 from KB2970 (or from Veeam web-site).

Solution

1. Download the patch and extract ZIP file to your backup server.
2. Check the current version of Veeam Backup & Replication. It must be 9.5.4.2866 (Update 4b).
3. Make sure that no jobs are running and close the console.
4. Right-click on the installation file and click "Run as administrator".
5. Go through the setup wizard to deploy the patch.

More Information

• Backup to Tape Jobs fail with “Tape Error: 1117” (KB2983)
• Potential data loss during Export Backup retention processing (KB3039)

Challenge

Cause

Solution

More Information

Challenge

This KB article provides a list of all versions of Veeam Backup & Replication and the respective build numbers.

Solution

The following table lists Veeam Backup & Replication versions and their build numbers. Also provided is a link to the specific version release notes.

Challenge

Solution

• Microsoft System Center Virtual Machine Manager 2019 is now supported.
• VMware vCloud Director 9.7 compatibility at the existing Update 4 feature level.
• VMware vSphere 6.7 U2 readiness including support for VMs with virtual hardware version 15. 
• Dell EMC Data Domain using DD OS 6.2 is now supported as the backup repository via both DDBoost and CIFS/NFS protocols. 
• Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903 support as guest VMs, and for the installation of Veeam ONE. 
• VMware vSphere 6.5 U3 and VMware vSphere 6.7 U3 are officially supported with Update 4a. 

• High CPU usage is observed on the Veeam Backup & Replication 9.5 Update 3/3a/4 server after upgrading Veeam ONE to v9.5 Update 4
• Business View grouping expression raises an error “invalid expression” if the length is longer than 25 rows
• Exporting Business View objects in the Veeam ONE Monitor client does not include category names
• Object Properties collection task returns error or warning with “Failed to retrieve empty storage controller list for Hyper-V host” message in the session details
• High load on Veeam ONE SQL Server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances Veeam ONE cannot connect to the database after upgrading Veeam ONE to v9.5 Update 4
• Failed to download clients.xml from the vCenter server after upgrading Veeam ONE to v9.5 Update 4
• Under certain circumstances performance data cannot be collected from SCVMM server and its objects
• Veeam ONE cannot collect data from Veeam Backup Enterprise Manager and its objects
• Veeam ONE tries to connect to already deleted hosts from the monitoring

More Information

Challenge

Cause

Solution

More Information

[[DOWNLOAD|DOWNLOAD NOW|https://www.veeam.com/download_add_packs/virtualization-management-one-solution/old_one_9.5u4/]]
MD5: 9BFC92B616BA040A515B8737C19F7D65
SHA-1: 1E2F9030DE69E388932E9A6B67B8B4616D14739C
SHA-256: 1BD615507AE3F353CDD363B151081FF9B012010693CD4320D204B9545694603A

Should you have any questions, contact Veeam Support.

Challenge

Cause

Solution

1. Download VeeamBackupOffice365_4.0.0.1553.zip
2. Run Veeam.Backup365_4.0.0.1553.msi as administrator on the Veeam Backup for Microsoft Office 365 server.

1. Download VeeamBackupOffice365_4.0.0.1553.zip
2. Run Veeam.Backup365_4.0.0.1553.msi as administrator on the Veeam Backup for Microsoft Office 365 server.
3. Run VeeamExplorerForExchange_4.0.0.1553.msi as administrator on the on each machine where Veeam Explorer for Microsoft Exchange is installed.
4. Run VeeamExplorerForSharePoint_4.0.0.1553.msi as administrator on the on each machine where Veeam Explorer for Microsoft SharePoint is installed.

1. Download VeeamBackupOffice365_2.0.0.567.zip
2. Run Veeam.Backup365_2.0.0.567.msi as administrator on the Veeam Backup for Microsoft Office 365 server.
3. Run VeeamExplorerForExchange_9.6.3.567.msi as administrator on the on each machine where Veeam Explorer for Microsoft Exchange is installed.
4. Run VeeamExplorerForSharePoint_9.6.3.568.msi as administrator on the on each machine where Veeam Explorer for Microsoft SharePoint is installed.
5. Download VeeamBackupOffice365_4.0.0.1553.zip
6. Run Veeam.Backup365_4.0.0.1553.msi as administrator on the Veeam Backup for Microsoft Office 365 server.
7. Run VeeamExplorerForExchange_4.0.0.1553.msi as administrator on the on each machine where Veeam Explorer for Microsoft Exchange is installed.
8. Run VeeamExplorerForSharePoint_4.0.0.1553.msi as administrator on the on each machine where Veeam Explorer for Microsoft SharePoint is installed.

More Information

Challenge

This KB article provides a list of all versions and respective build numbers for the following products:

• Veeam Agent for Windows
• Veeam Agent for Linux
• Veeam Endpoint Backup

Solution

Veeam Agent for Windows

Veeam Agent for Linux

Veeam Endpoint Backup

Challenge

Cause

Solution

**Support for vSphere versions older than vSphere 5.5 was removed starting with Veeam Backup & Replication v10.

More Information

Challenge

Cause

Solution

ssh -i "<backup server's .pem key>" ubuntu@<Public DNS (IPv4) parameter of the backup server>

<Region Id="me-south-1" Name="Middle East (Bahrain)" Type="Global">
    <Endpoint Type="S3">s3.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="S3">s3.dualstack.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="EC2">ec2.me-south-1.amazonaws.com</Endpoint>
    <Endpoint Type="IAM">iam.amazonaws.com</Endpoint>
    <Protocol>HTTP</Protocol>
    <Protocol>HTTPS</Protocol>
    <LocationConstraint>me-south-1</LocationConstraint>
    <SignatureVersion>4</SignatureVersion>
  </Region>

sudo systemctl restart veeamawsbackup.service

Challenge

Cause

Solution

**Support for vSphere versions older than vSphere 5.5 was removed starting with Veeam Backup & Replication v10.

More Information

Challenge

Solution

If you are using Cloud Connect, please consult with your provider to ensure you are on the same, or earlier, version than the provider. A tenant cannot be on a newer version than the provider.

Please see the supported versions and system requirements page in the User Guide for the most up-to-date information prior to upgrading. Links included under More Information at the bottom of this article.

Please refer to the following links for steps and more information on upgrading to 9.0, 9.5, or 10.0:

• Upgrade to 9.0: https://helpcenter.veeam.com/backup/vsphere/upgrade_vbr.html
• Upgrade to 9.5: https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=95
• Upgrade to 10.0: https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=100

The latest Veeam updates:
https://www.veeam.com/updates.html

Old versions of Veeam Backup & Replication can be found here:
https://www.veeam.com/older-versions-download.html

7.x
7.x -> 7.0.0.871 -> 9.0.0.902 -> 9.5.0.1922 -> 10.0.0.4461

1. Install Veeam Backup & Replication 7.0 Patch 4 (7.0.0.871)
2. Install Veeam Backup & Replication 9.0.0.902
3. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
4. Install Veeam Backup & Replication v10 

Refer to above links for steps to upgrade.

8.x
8.x -> 8.0.0.2084 -> 9.0.0.902 -> 9.5.0.1922 -> 10.0.0.4461

1. Veeam Backup & Replication 8.0 Update 3: (8.0.0.2084)
2. Install Veeam Backup & Replication 9.0.0.902
3. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
4. Install Veeam Backup & Replication v10 

Refer to above links for steps to upgrade.

9.0.x
9.0.x > 9.5.0.1922 -> 10.0.0.4461

1. Install Veeam Backup & Replication 9.5 Update 3 9.5.0.1922
2. Install Veeam Backup & Replication v10 

Refer to the above links for steps to upgrade.

 

More Information

Build numbers and version of Veeam Backup & Replication

Veeam Backup & Replication support for VMware vSphere