Security
Scalability
REST API
General
Backup
REST API
GET /api/v1/virtualMachines/policies?VirtualMachineId=<VirtualMachineId>
To install updates, follow the steps described in the Veeam Backup for AWS User Guide.
After installing the patch, your build version will be 7.1.0.8.
Security
General
username@domain
Private Network Deployment
Backup
Restore
Workers
To install updates, follow the steps described in the Veeam Backup for Microsoft Azure User Guide.
After installing the patch, the build number will be 6.0.1.267.
Security
General
Backup
Reporting
This KB article lists all versions of Veeam Data Cloud and their respective release information and build numbers.
For more information Veeam Data Cloud, visit:
Version | Build Number | Release Date |
Veeam Data Cloud for Microsoft 365 1.5 Releases | ||
Veeam Data Cloud for Microsoft 365 1.5.1 | 1.5.1 | 2024-03-14 |
What's New
Resolved Issues
|
||
Veeam Data Cloud for Microsoft 365 1.5.0 | 1.5.0 | 2024-02-28 |
What's New
Resolved Issues
|
A Windows Agent Backup or Windows Agent Policy type job within Veeam Backup & Replication fails with either of the following errors.
A Veeam Agent Backup operating in Managed by backup server fails with the error:
Error: Managed session has failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <vbr_ip>:10005
A Veeam Agent Policy fails to deploy with the following error:
Failed to send backup job configuration to <machine> Error: Failed to update backup job Managed by agent job ID: <job_id_guid>. Managed by agent job name: <job_name>. Invalid job configuration. Connection problems. Exception has been thrown by the target of an invocation. Failed to establish connection: no valid IP addresses were found. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <vbr_ip>:10005
This article is regarding Veeam Agent for Microsoft Windows deployments that are managed by Veeam Backup & Replication and use the port 10005. Other nearby ports are used for similar purposes:
While firewalls blocking port communication remains the most common cause of support cases, Veeam Support has seen a marked increase in the number of cases caused by the Cloud Agent of Qualys vulnerability scanner, as it shares many of the same default ports:
"During an unauthenticated scan using the Qualys scanner, the Cloud Agent will return its Correlation ID to [the] scanner over one of the Agent Scan Merge ports (10001, 10002, 10003, 10004, 10005)."
The ports used by the Agent Scan Merge can be customized: Agent Correlation Identifier.
These errors occur when the Windows machine where Veeam Agent for Microsoft Windows is installed cannot reach the Veeam Backup Service on the Veeam Backup Server over port 10005.
This may occur if:
If you are facing a situation where another product is using port 10005, and that third-party software cannot be adjusted to use a different port, Veeam Backup & Replication can be configured to listen on a different port for communication from managed Veeam Agent for Microsoft Windows deployments.
Changing the port that managed Veeam Agent for Microsoft Windows deployments use to communicate with Veeam Backup & Replication will cause them to lose contact with Veeam Backup & Replication until their configuration is updated to make them aware of the port change.
"C:\Program Files\Veeam\Endpoint Backup\Veeam.Agent.Configurator.exe" -setVBRsettings /p:"<protection_group_name>.xml"or
<?xml version="1.0"?><ConnectionParams ConnectionPoint="VBR.domain.tld" Port="10005"><IpAddresses>10.0.0.115</IpAddresses></ConnectionParams>
Create the following registry value on the Veeam Backup Server.
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: EndPointServerSslPort
Value Type: DWORD (32-Bit) Value
Value Data(Dec): 10005 (Default)
This KB article lists all versions of Veeam Service Provider Console and their respective build numbers.
For more information on downloading the latest version of Veeam Service Provider Console, visit:
Version | Build Number | Release Date | Release Notes |
Veeam Service Provider Console 8 Releases | |||
Veeam Service Provider Console 8 CP1 | 8.0.0.18054 | 2024-03-04 | KB4509 |
Veeam Service Provider Console 8 | 8.0.0.16877 | 2023-12-05 | |
Veeam Service Provider Console 7 Releases | |||
Veeam Service Provider Console 7 P20230531 | 7.0.0.14271 | 2023-06-05 | KB4441 |
Veeam Service Provider Console 7 P20230321 | 7.0.0.13157 | 2023-03-21 | |
Veeam Service Provider Console 7 GA | 7.0.0.12777 | 2023-01-30 | |
Veeam Service Provider Console 6 Releases | |||
Veeam Service Provider Console 6 Patch 1 | 6.0.0.8787 | 2022-02-02 | KB4277 |
Veeam Service Provider Console 6 GA | 6.0.0.7739 | 2021-09-27 | PDF KB4212 |
Veeam Service Provider Console 5 Releases | |||
Veeam Service Provider Console 5 Patch 4 | 5.0.0.7151 | 2021-10-12 | KB4223 |
Veeam Service Provider Console 5 Patch 3 | 5.0.0.6959 | 2021-05-22 | KB4163 |
Veeam Service Provider Console 5 Patch 2 | 5.0.0.6883 | 2021-03-25 | KB4127 |
Veeam Service Provider Console 5 Patch 1 | 5.0.0.6838 | 2021-03-03 | KB4116 |
Veeam Service Provider Console 5 GA | 5.0.0.6726 | 2021-02-24 | PDF KB4111 |
Veeam Service Provider Console 4 Releases | |||
Veeam Service Provider Console 4 Patch 2 | 4.0.0.4914 | 2020-07-23 | KB3237 |
Veeam Service Provider Console 4 Patch 1 | 4.0.0.4911 | 2020-07-03 | KB3211 |
Veeam Service Provider Console 4 GA | 4.0.0.4877 | 2020-03-31 | PDF KB3040 |
Veeam Availability Console 3 Releases | |||
Veeam Availability Console 3 Patch 4 | 3.0.0.2795 | 2020-01-23 | KB3036 |
Veeam Availability Console 3 Patch 3 | 3.0.0.2762 | 2019-09-20 | KB3003 |
Veeam Availability Console 3 Patch 2 | 3.0.0.2725 | 2019-06-17 | KB2960 |
Veeam Availability Console 3 Patch 1 | 3.0.0.2703 | 2019-04-11 | KB2934 |
Veeam Availability Console 3 GA | 3.0.0.2647 | 2019-03-28 | |
Veeam Availability Console 2 Update 1 Releases | |||
Veeam Availability Console 2 U1 Patch 1913 | 2.0.2.1913 | 2018-12-21 | KB2835 |
Veeam Availability Console 2 U1 Patch 1850 | 2.0.2.1850 | 2018-11-15 | KB2795 |
Veeam Availability Console 2 U1 Patch 1824 | 2.0.2.1824 | 2018-10-05 | KB2781 |
Veeam Availability Console 2 U1 Patch 1817 | 2.0.2.1817 | 2018-08-30 | KB2715 |
Veeam Availability Console 2 U1 Patch 1807 | 2.0.2.1807 | 2018-07-30 | KB2694 |
Veeam Availability Console 2 U1 GA | 2.0.2.1750 | 2018-06-19 | |
Veeam Availability Console 2 Releases | |||
Veeam Availability Console 2 Cumulative Patch 1376 | 2.0.1.1376 | 2017-12-21 | KB2418 |
Veeam Availability Console 2 GA | 2.0.1.1319 | 2017-11-14 | |
Veeam Managed Backup Portal 1 Releases | |||
Veeam Managed Backup Portal 1 | 1.0.0.295 | 2016-03-24 | - |
instance name
and region
to match the virtual network you plan to use for the storage account, public IP address name,
and the availability zone
. It is assumed if you're using Azure ExpressRoute that you have configured this prior.Configure now
. You'll need to generate a certificate using PowerShell for your connection. Specify an address pool, select IKEv2
and OpenVPN (SSL)
as your tunnel type, and for authentication type, choose Azure certificate
, uploading the root certificate contents.public network access
is disabled. If you need to access Azure Blob from another resource without using a private endpoint, for example, to see container contents in the Azure Portal you will need to choose enabled for selected virtual networks and IP addresses
instead.name
and network interface name.
blob.
integrate with DNS zone
.DNS configuration
, you should be able to see a private link entry that points to the specific IP address. This is required to support Azure Archive Tier as Veeam Backup & Replication Azure Proxy Appliances are deployed dynamically.Add your Azure object storage account to Veeam Backup & Replication.
This article documents how to configure Veeam Backup & Replication to use Google Cloud Private Access to connect to a GCS bucket instead of the public IPs for Scale-Out Backup Repository offload to Capacity Tier or Archive Tier or to connect to an Object Storage Repository in Veeam Backup & Replication 12 or newer.
Connectivity from on-premises to private access can be accomplished via Cloud VPN or Direct/Partner Interconnects to Google Cloud, and Private Access enabled on the VPC Subnet.
Note: Backup repository servers located in GCE need to be on a VPC Subnet where Private Access is enabled.
Add the Google Cloud Oject Storage to Veeam Backup & Replication.
If the Gateway server assigned with the Object Storage Repository settings has a restricted internet connection, that machine cannot perform Certificate Renovation List (CRL) checks. In such a scenario, disable certificate revocation checks by creating the following setting on the machine assigned as the Gateway server within the Object Storage Repository settings.
Note: This setting will disable TLS revocation checks for all interactions with Object Storage performed by the machine where the registry value is created.
ObjectStorageTlsRevocationCheck=0