Discussion Boards

Hello,we have been used company certificate into VBR console in main menu …but now we have issue with agents managed by VBR8/10/2025 10:44:54 PM :: Error: Managed session has failed: Failed to validate remote certificate  any hints, how to fix that I will appreciatethank you 

Veeam Microsoft 365 Community Edition Corrupt adb.log file corrupt. Does anyone know how to fix corrupt adb.log files? I already submitted a ticket but since its the Community Edition, I doubt I will get assistance.

Hi!We have an ESXi 7 host with some VM on and want to replace it with a new host with ESXi 8.We have Veeam backup & Repliaction Enterprise 12.3 on a standalone server.The backup is going to a NAS, and then out to a cloud backup.I want to migrate all my VM to the new ESXi host but without losing the backupchain.Not sure what method that I should use.Can anyone here please give me som input what path is the best way to go?We rather not start from the beginning with all our backups.

I am creating failover plans in VBR and want to script changing DNS entries to point to new IPs.  I can’t find any documentation about how these scripts run, any parameters that can be passed to them etc.  All I can see is that they run on the VBR server.  Can anyone point me to something?Thanks

Due to some issues with the PostGre SQL database of Veeam B&R CE, I had to uninstall and reinstall Veeam B&R CE. After sucessful installation, I imported the configuration Backup file. Everything worked fine, I had all my Backup Jobs, my Backup Infrastructure and my Physical Infrastcture restored. I was very happy that everything could be restored so easily. But the next day I had some failed Backup jobs in the History. Two servers (no VMs) couldn´t be backuped because of a strange error message:Warning Failed to connect to XXXXXXXX Details: Cannot find package version for component EpAgent package Msi platform X64. OK, it looks like Veeam B&R had some issues to connect with the Agent on this servers. So I uninstalled the Agent on the Server and tried to install the Agent via B&R once again.But it always failed. Veeam B&R can´t install the agent because it can´t find the “EpAgent package Msi platform X64”. It´s no issue fro

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

Hello All I am reconfiguring my Backups, and trying to achieve disaster recovery, i want to backup local VMs,Microsoft 365 and Entra ID, for that i am using Veeam Backup and replication V13 (VM) Veeam Microsoft 365 for Email, OneDrive and SharePoint. look to add Entra ID but not sure which Veeam product will be best.for repositories i am thinking one local (immutable backup), Azure Blob (immutable backup) now my question is which product i should use for Entra ID backup, what i should use for local immutable backup, is “Object First” devices good? my backup will be under 8 TB, and what i should use for remote backup Azure or i think Veeam have product cloud vault? what will be best.  

Hi,Is anyone able to assist here? I’m trying to upgrade to Veeam 13, as part of the overall upgrade I have to upgrade V Orc from my current version 7.1 to 7.2. However, all that I can see in the previous versions is:But the pre-req explicitly says:Upgrade to Orchestrator version 7.2.1 is supported from Orchestrator version 7.2 only; upgrade from Orchestrator versions 7.1, 7, 6, 5 and 4 to version 7.2.1 is not supported:To learn how to manually upgrade from Orchestrator version 7.1 to 7.2, see Veeam Recovery Orchestrator 7.2 User Guide.  However, I’m unable to find the 7.2 version I need to upgrade to 7.2.1. Any help would be appreciated

Hi all,It seems that today is vulnerability day! https://www.veeam.com/kb4830https://www.veeam.com/kb4831Let's start planning the updates!

I would like to know from you, gentlemen, if anyone here happens to use this NIST document. It dates back to 2010, but it seems to me to be an excellent source of information. What references have you been using in your projects?   

Malware detection scanned  a suspicious file from backup but the file is actually legit and so I marked it as clean and Exclude. If I modify the same file for testing purposes, will the malware detection flag it as safe, legit file since I marked it Clean and Exclude? Or it will be detected as suspicious again? Thanks. 

I am preparing to update Veeam for Microsoft 365 from 8.1.2.180 to 8.3.0.2201 and I just want to make sure I am all set in case there are any issue after the update. I don’t believe I have any PostgreSQL or NATS setup that I can recall from when I set this up. I suppose if I do it is all default. It also appears there is no config backup option in this program. We do back up this server, but it does hold both V365 and VBR, so not sure if that complicates things from a restore standpoint if there is a problem with the V365 update.I’m probably overthinking it, but it is the first time I will be updating V365 and just want to make sure my jobs and repositories don’t break or need adjustments after the update.The main reason for this update other than the prompt for an update was that we received a one time email last week saying “License update interrupted: License contract has been terminated” even though subscription and user licenses are active as far as we can tell. P

SQL Transaction Log Backup fails due to temp staging disk full (Veeam Agent for Windows) EnvironmentProduct: Veeam Agent for Microsoft WindowsWorkload: SQL Server databasesBackup Type: SQL Transaction Log Backup (Application-aware processing)Error ReceivedThe following error appears during the SQL transaction log backup job: Log backup job: Backup Job for SQL Server Transaction Log BackupCollected SQL Server transaction logs do not match any existing database backup.Failed to perform internal backup:Code = 0x80040e14Source = Microsoft OLE DB Driver 19 for SQL ServerDescription = Write on "C:\ProgramData\Veeam\Endpoint\SqlLogBackup\{GUID}.bak"failed: 112 (There is not enough space on the disk.)Database hide_name_db        Status    UnprotectedFailed to perform internal backup (hide_name_db): Code = 0x80040e14 Code meaning = IDispatch error #3092 Source =

Dear Community, As we transition to Veeam 13 I may be getting a bit lost on the usage/purpose of the above Appliance.I have deployed the VSA ver 13 as in-house demo to explore the features and usage. I also deployed the Veeam Hardened Repository 2.0.0.8 and I like how it makes things easier.However the Usage of the Veeam Infrastructure Appliance which can also be used to deploy the Linux VHR has other roles/features that may not be clear on how they plug-in to the entire deployment. I am reading this part https://helpcenter.veeam.com/docs/vbr/userguide/linux_infrastructure_appliance_byb.html?ver=13 and I would like to understand which components that we used to integrate and configure in VBR ver 12 can be compared. Hope its clear. Though I

(running Veeam 13, Community/Free edition on Win 11).I did a bunch of migrations and updates a month ago. Before doing so I set aside the existing Veeam backups, so I have them. When I try to import a backup for one server from it (just to browse and retrieve a couple files) it tells me "Path contains invalid symbols...",. But it doesn’t. I have a path with no special characters or trailing spaces or anything like that. The message isn’t any more specific.I’ve tried mounting the file share where it exists as a mapped drive and a network location. I would copy it into the local machine to try that, but there isn’t room.Also, the import dialog says “Specify a backup to import. You can import backups from a backup repository or any managed server.” but the dropdown menu only lists the local machine and my two hyper-V hosts, not the repository (which is on a network share).Thanks.

We use AWS VTL for backing up some of our larger SMB file shares (mainly AWS FSx for Windows) that run into a few terabytes each.When running a tape backup job we’d run a powershell script to check there were at least 10 free tapes before starting each job (there’s around four or five chained jobs).The script worked fine on VBR v12, but always returns “TooManyRequests” on v13.I have found various “retry” scripts, but the VBR commands ALWAYS return “TooManyRequests” so never complete.Is there now an alternative method to auto load blank tapes that didn’t exist in v12?Our script that worked in v12:# Get Library$NOVA_Tape_Library = Get-VBRTapeLibrary -Name "Novasol Gateway-VTL V3"# Get Number of Free Tapes$NOVA_Free_Tapes = (Get-VBRTapeMediaPool -Name "Free").medium | where {$_.LibraryId -eq $NOVA_Tape_Library.Id}# if number of free tapes < 10 import tapes and format for

Hi teamA hardened repo using the VEEAM Hardened ISO experienced a power cycle and upon reboot its out of band interface lit up like a x-mas tree.Upon further investigation it appeared that the virtual disk was just gone. A message indicated that RAID6 detected foreign configuration.Been working with vendor and they have asked to install storcli on to the server.Would this be possible, being a hardened repo? They have a non-recommended method alternative too.Can’t believe that a power cycle did this and not sure what the root cause is but would be good if we could get it back. Otherwise will have to rebuild and sync primary backups againcheers

Hello,i would like to ask, if somebody is not experiencing that issue, that big environments have issue with SSL connection? we have all in one boxes - VBR, VEM and postgresql is on the same machine at the end of postgresql.conf #------------------------------------------------------------------------------# CUSTOMIZED OPTIONS#------------------------------------------------------------------------------# Add settings for extensions heressl = onssl_cert_file = 'backup_server.crt'ssl_key_file = 'backup_server.key'ssl_ca_file = 'backup_root.crt' in svc_veeambackup.log we see[02.03.2026 11:40:10.307]    <35>   Error (3)    0: Breaking connector[02.03.2026 11:40:10.307]    <35> Warning (3)    Failed to obtain connection: [Failed to connect to [::1]:5432]. Attempt 1 of 20. in pg_hba.conf is preferred connextion via ssl# IPv4 local connec

Hi,we are planning to use the Veeam Data Cloud for Salesforce Backup. We need to keep backups for 2 years. What, if we decide to switch the backup-partner. For example Salesforce native backup? We cancle our subscription. Fair-Use-Policy will delete the backups after 30 days, correct? What options do we have, to keep  the backups as long as our requirements are? The same question would be, if we decide to use veeam backup for m365 in the data cloud. Here we would have onedrive files, with a retention time of 2-10 years.  We do not plan to quit anything, but we need a valid exit strategie if we decide to use a cloud product. 

Hi everyone,I am currently reviewing the design of our Veeam Backup & Replication server and would like to follow best practices for disk layout.At the moment our VBR server is a VM with the following specs: 8 vCPU 32 GB RAM Windows Server Local SQL instance Only one virtual disk (C:) which is a VHDX located on HDD storage Currently everything is located on this single disk, including: Veeam installation SQL database Veeam logs Veeam catalog configuration backup Windows OS I am considering adding an additional virtual disk located on SSD storage and moving the Veeam-related components there to improve performance and follow recommended architecture.My questions are:

Hello everyone,For several days now, I have been receiving the following error message during our backup copy job:“Failed to perform backup verification Error: Unable to get block digest: block is not initialized. Skipped arguments: [0]; Agent failed to process method {Signature.FullRecheckBackup}.”I performed a full backup, but unfortunately the same error message appeared again. The copy job does not conflict with the backup job.How can I fix this error?Thanks in advance!Version: Backup & Replication 12, Build: 12.3.2.4165

Hello guys,After a basic restart of the VM I can't no longer access our VBR console.All services are up and running.Any recommendations?

Hi all. Running Windows Server 2019 as a standalone Hyper-V server. The server is in a workgroup.I have installed the community edition of VBR 12, and configured my backup repository.When trying to configure a new Hyper-V backup job, Veeam gives me a message to say that it cannot connect to the ADMIN$ share. However, if I type \\localhost\ADMIN$ into the run box, then the folder does open.I’ve tried setting my host name to localhost, to the server name and to it’s IP address. I’ve also tried with the current logged in credentials, and have tried by enabling the administrator account.Any help would be appreciated.Thanks, and have a great weekend!

I read in the news recently that Veeam has bought Securiti AI, which is going to have a direct impact on its data protection offering. This deal is a game-changer for Veeam's strategy, combining data resilience with data security.But what does Securiti AI do, and why did Veeam decide to buy it?Securiti AI is a big name in the industry, and they focus on Data Security Posture Management (DSPM), privacy and data governance. With a spent about £1.725 billion in total Veeam's big plan is to bring together their data resilience (which they're really good at – backup and recovery) with data security (Securiti AI's thing).So, why's this important for Veeam?I think this purchase is meant to create one command centre where they can use DSPM on data in use and on backup files as well. This means that sensitiv