Unanswered questions

Hi Veeam Community,I’m running into a critical issue with my backups and need help.Error Details:Unable to apply retention policy: failed to delete backup filesError: Failed to call RPC function 'FcIsExists': The specified network name is no longer available.Environment:Veeam Backup & Replication: v12.3.2.3617 Backup Repository: NAS OS: Windows 10What I’ve tried:Deleted ~300GB of old backup files to free up space. Verified repository free space. Restarted Veeam services and checked network connectivity.Despite this, all backups are failing. The error seems tied to retention policy cleanup and possibly network access to the NAS.

Good afternoon, all!My customer is at the very front edge of a complete virtualization refresh - hardware, software, virtualization platform, the whole picture.We’re currently using Veeam B&R and VeeamONE to support our VMware stack, with an onsite performance layer and a cloud storage tier for long-term archiving.If we moved to Hyper-V or Nutanix, would we be able to retain our VMware-based backups for file and data recovery or would we need to repatriate and convert?Thanks!

One of our client  needs to transfer their VBM 365 backup data from the current S3 bucket in their AWS backup account to a new S3 bucket in a different AWS account for security and compliance reasons. This operation should be seamless, ensuring no disruption to the current backup configurations. It must retain all historical backup data and restore points, resuming the backup operation from where it left off before the migration to the new S3 repository. Is it possible to achieve this, by adding new s3 bucket to VMS65 And then pointing to new repository? or using a Backup copy job then removing the old S3 bucket ? 

Dear Veeam Experts,One of our customers is facing an issue with the MSSQL plugin backup failing. Upon verification, I noticed that the backup data is being written successfully, but the job fails with the error “Starting Retention Policy Task.”In this setup, the retention policy is configured for 6 days per backup file. However, I observed that some files are not expiring as per the defined retention policy.Kindly help us with the steps or guidance to resolve this issue.Best regards,G Venkata Sai Kumar

I get the error “30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'                             b4634265-9228-4a5e-9d95-2c12313e89c6”This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… How do I fix this? 

Hi Community, I’m facing an issue where Veeam ONE Reporting Service (VeeamRSS.exe) cannot communicate with Veeam ONE Monitoring Service (VeeamDCS.exe). The error message states:  The Monitoring service appears to be stopped or inaccessible. Has anyone encountered this before? What could cause the Monitoring service to become unavailable? Any insights or best practices to resolve this would be greatly appreciated. Kindly note that support case already been open for this.  

Hello everyone, I am trying to connect the Veeam software appliance and my NAS via iSCSI. It won't work directly, so I installed Veeam Infrastructure Server, where I tried to connect the NAS, but I have no idea how to connect it there. I looked through the documentation, but couldn't find anything. Could you please advise me?Thank you in advance.

Fresh v13 build for VBR, EM and Veeam ONE.Veeam ONE is installed on windows 2025 with a seperate win2025 SQL server.Install is all good but when running the Veeam ONE client and I click ADD SERVER to add the VBR server, this opens a web interface to veeam one. Once logged in, I get this:infrastructure is missing and I can click review data sources, when I click this I get error “failed to add the virtual infrastructure. The user account does not have the required permissions”.The user does have permissions, local admin, in the veeam administrators group as well. In the top corner of the web UI it also shows the user then underneath “restricted permissions user”.Very odd…..anyone see this?

We have recently inherited a Kasten system and we are trying to (1) understand how Kasten works and (2) figure out why some of our applications are non-compliant. One issue that we are currently investigating is why one application in particular always fail due to timeout. We are trying to backup a namespace with a couple of PVC:s (using CSI:s - Ceph RBD and Ceph FS). The total backup size is approximately 1.5 TiB.When we first noticed an issue with this application, we saw that the backup failed due to timeout (10h). We then increased the timeout (to 24h) and the next backup worked! (It took 11h.) However, all subsequent backups have failed due to timeout. We have been troubleshooting this for quite some time now but have been unable to find anything conclusive. The worst part is probably that we don’t really understand where in the Kasten deployment to look for relevant logs. Any help figuring out the particular issue or general information about best practices w.r.t. troubleshooting

Hi All,Are there any issues getting reported with Veeam support portal?Seem to not allow me to login, presented with an error message:This page isn’t workingmy.veeam.com redirected you too many times.Try deleting your cookies.ERR_TOO_MANY_REDIRECTS Even after deleting my cookies, tried from 4 different browsers, 2 different laptops 2 different internet connections.Seem like something is not right at Veeam's end.ThanksArtik 

Backup Job using Storage Snapshot Unable to Find Ontap SnapMirror Relationship for Secondary Target. Backup finished with Warning: Cannot find any relevant ONTAP SnapMirror and SnapVault relationships   Storage Replication between the Source and Target destinations is working. I was looking at the job log and saw that Veeam was able to identify Primary SnapProtections.   There were lines showing WARNING: Replication of all disk snapshots of vm asdasdfasf is not possible for ‘Snapshot Replication’. Thanks again for your input as to possible reasons why this is happening.  

Hi all,I've written and tested a PowerShell script to harden a standalone Windows Server 2025 machine running Veeam Backup & Replication, based on the CIS Benchmarks (Level 1 & 2). I’m sharing it here in case it helps others — feedback is welcome!What the Script DoesThis script configures the server securely without breaking core Veeam functionality. It includes: Account Policies: Max password age, complexity, and lockout thresholds (CIS 1.1.x, 1.2.x) Guest & Anonymous Access: Disabled for better baseline security Audit Policy: Enabled for all major categories (CIS 17.x) Unneeded Services: Disabled (safe defaults — e.g., Print Spooler, Xbox services) Windows Defender: Hardened settings with MAPS Advanced, PUA protection, etc. Firewall Configuration: Enables Windows Firewall with a default deny-inbound policy Allows Veeam ports: TCP 6160–6162, 445 (SMB), 135–139 (RPC) Blocks inbound RDP (port 3389) entirely (as this is often a target surface) SMB Pr

Hi,I have installed an agent 6.3.2.1207 on Oracle Linux 7.9, Kernel 5.4.17-2136 el7 uek.Backup failed with cannot load module veeamsnap.veeamsnap module was installed but cannot be loaded. Maybe due to kernel incompatibility. I cannot find useful information on howto get this running, on this Linux Version with that kernel.Can anyone help? Rene

Hi Veeam team,I recently upgraded our Veeam Backup & Replication server to version 12.3.2.3617 on a Hyper-V host (not ideal, I know). The upgrade failed. Upon reviewing, the VBR has been upgraded, but the console won't connect. An attempt to upgrade console will end up in the following error “Unable to update the backup console because the following products are installed on this server: Veeam Backup and Replication Server”Checking the logs, it says:[04.07.2025 05:09:16][INFO] Installing Veeam Backup & Replication Console[04.07.2025 05:10:52][ERROR] Fatal error during installation. Steps I’ve already tried: Rebooted the Hyper-V host Force-stopped all Veeam services and processes Tried installing console via both GUI and from ISO Verified version mismatch (Console still on 12.3.1.1139, Server is 12.3.2.3617) Confirmed no backup jobs are running Still stuck in a loop where the console can’t connect or be upgraded, even after a clean reboot. Would really appreciate guidanc

Attempting to configure Veeam Recovery Orchestrator to test backup images scheduled by a predecessor. Errors running the tests generally stating the resources can’t be tested for viability because they reside on another system or vlan. Unable to find appropriate configuration documentation via resources that are known and available. Any references appreciated.  

Wondering if anyone has done this before where we need to failover an Org in vCloud Direcotor to a target vCloud Director as a DR.  This would need to failover in a specific order as well has have some time delays between failovers.   And ofcourse failback to finish it up.   I have 28 sub-tenants that need this functionality.  Any help would be appreciated.   I just finished standing up the Veeam Orchestrator to see if that will work at all, it doesn’t look promising based on the documentation I’ve read so far.   Currently we need to failover manually from the Replicas Ready view.   A typical failover today would be 1. failover the fw 2. failover dc and check time upon powerup 3.  failover other dependencies like sql or rdsgateway, then the remaining vms behind the dependencies or that don’t have one.

Hi, I’m trying to make room in my backup repository for new backups.  My previous retention was set to 90 days and the oldest backup is from 45 days ago.  I changed the retention to 30 days, thinking that Veeam will then delete the backups between 31 and 45 days ago to make room, but it’s not doing that.  Is there a way to prompt it to do that?  I’ve tried to rescan the repository and also re-running the Backup Job, but neither seems to work.  Thank you!

Hallo zusammen,ich stehe vor einem sehr hartnäckigen Problem mit einem Veeam Agent Job (Managed by VBR), das alle Standard-Workarounds überdauert hat. Ich bitte um Hilfe, falls jemand diese spezielle Kombination von Fehlern schon einmal gesehen hat.Umgebung: Veeam Backup & Replication Version: 12.3.1.1139 Betroffener Job-Typ: Windows Agent Backup (Managed by VBR) für einen Windows Client PC. Problem: Der Job schließt mit der folgenden Warnung ab und wechselt in den Warnstatus: Collecting recovery media files Details: Windows recovery image file not found Faktenlage (Was wir wissen): OS-Ursache: Das Windows Recovery Environment (WinRE) ist auf dem betroffenen PC dauerhaft defekt/nicht existent. Der Befehl reagentc /info meldet trotz erfolgreicher Ausführung von reagentc /enable und DISM /RestoreHealth weiterhin: WinRE-Status: Disabled. Eine WinRE-Partition existiert physisch nicht auf dem PC. Fehlgeschlagene Deaktivierung über GUI: Die Option zur Deaktivierung der Recovery M

Hola a todos:Tengo una consulta, tengo un VBR al cual le agregué un repositorio de BlackBlaze. Todo bien con ello, la pregunta pasa por lo siguiente: Si en caso de que se dañe el servidor VBR y no tenga como recuperar las configuraciones de los jobs, puedo volver a unirme a ese repositorio in perder los backups en él? Obviamente estarían como huérfanos, pero si se podria? Saludos,

I'm trying to add a PVE host to a Veeam virtual machine, but there's no storage space to choose in the snapshot storage, and I can't even see the PVE local storage.it alson failed to rescan pve hostI confirmed that my network is connectedBut the storage space is visible on the add proxy sideHas anyone encountered this issue before? 

Ciao a tutti, la cosa era stata già discussa qui: con, fra i commenti, anche il link a una ottima guida per i cluster SQL tramite Agent.Mi piacerebbe condividere un po’ le esperienze visto che al momento non ne ho molte, e il tema non sembra trattato spessissimo. Soprattutto mancano le trattazioni riguardo al restore che non è banale e richiede attività manuali di ricostruzione del cluster, e quindi competenze nei cluster stessi.Da quello che ho visto finora, capita che si parta con l’approccio sbagliato ovvero di fare un Protection Group come “individual computers”, mentre è obbligatorio crearlo come “Ms. ActiveDir. Objects”.Una mia osservazione è che, ogni volta si tratta una VM come una macchina fisica, si rinuncia ai benefici della virtualizzazione e il restore diventa molto più laborioso e gli RTO più lontani.Trasformare i tradizionali cluster con dischi condivisi in quelli moderni senza storage condiviso sarebbe una mossa molto utile a mio avviso. Certo comporta un lavoro da una

Hi,I would like to backup with Veeam backup and replication 12 my new physical NAS with TrueNas Core.How can I proceed ?Do I need to add my TrueNas like an “unstructured data source” ?If so, what option should I choose in next window? File server, File share or NAS filer ?Thanks for your helpRegards,

Hi Community,Recently i install Veeam Agent on Windows Server 2008 R2 via VBR 12 Inventory and got an error  Failed to Verify C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll Signature I found this page https://www.veeam.com/kb4677 and explain 2 possible causesAntivirus Block → Root and Intermediate CA is missingTo confim the issue we look at C:\ProgramData\Veeam\Backup\Svc.VeeamInstaller.log and gotFailed to verify file using the Authenticode provider. Verification status: A certificate chain could not be built to a trusted root authority. (-2146762486), last error: A certificate chain could not be built to a trusted root authority. All are pointing to Certificate Issue, so i install all CA listed on Veeam here https://helpcenter.veeam.com/docs/backup/vsphere/trusted_root_certificates.html?ver=120.After installing all CA still got same issue here. Are i missing something here? Any insight would be appreciated! 

Hi All, I have a VBR 12.3.2 server running in AWS as an EC2 instance.  Use Windows agent on other EC2s to back them up to an S3 scale-out repository.  The backups work as expected.  I am able to do file level restores with no problems.  When I try to do a restore to EC2 (create a new EC2) I get the following error “Unable to import the instance from an encrypted volume snapshot” when I click Next on the Reason screen.  I do have it set up to use a helper appliance.  Do you have any thoughts on how to get this working?  The volumes of EC2 that are backed up are encrypted with an AWS-managed key (aws/ebs).  But shouldn’t it be pulling from S3 for the restore? Thanks for any help you can provide.Scott

once i try to install VeeamBackup&Replication the setup refuse to complete it just once started it gives  that The error "unknown exception occurred vmaGetpropertiesFromRegistry"and close the setup and refuse to continue i am sure that happes related to uncorrect uninstalled veeam application is that mean i look for another application ?