Discussion Boards

hi,we have upgraded vbr and vem from version 13.0.x to 13.1.x. however after upgrade we got error accessing veeam backup infra {unable to connect to backup infastructure,please contact your service provider}follwoing error while connecting using tenat veeam data protection.note: we are using vsa based vbr and vem 

Is VBR support to backup and restore to Tencent Cloud?

Additional Details: Issue Description: Our offsite Azure Blob backup job is failing with a REST API 409 Conflict: SnapshotsPresent error when Veeam attempts to delete or clear the metadata lock files located in the .../Metadata/Lock/create.checkpoint/ directory. Steps Performed Before Opening Case & Why: 1. Disabled Azure Blob Soft Delete (In Azure Portal): Disabled Blob and Container Soft Delete and permanent delete for soft deleted items to stop a 7-day duplicate billing loop caused by Azure trapping Veeam's deleted files at premium rates. 2. Enabled Cool Tier Option (In Veeam 12 Console): Edited our repository properties in the Veeam 12 app and checked the box "Use cool blob storage tier" to migrate our data footprint from the premium Hot tier to the cheaper Cool tier, aimed at lowering our permanent monthly storage bill. 3. Inspected Blobs via Azure Portal: Navigated directly to the target metadata folder (try, lock, and declare blobs) to check for active snapshots. The Azure U

Hello everyone,I have a question regarding MFA in Veeam Host Management.During the initial installation, I enabled MFA on the default veeamadmin account. However, my goal is to use veeamadmin only as a break-glass account and instead create separate admin accounts with MFA enabled.The issue I’m facing is the following:When I enable MFA on another admin account, either:the verification code is sent to the veeamadmin account, or the MFA validation fails completely.This prevents me from properly configuring MFA for individual admin users.Has anyone encountered this behavior?Is there a recommended way to configure MFA for multiple admin accounts while keeping veeamadmin as a fallback account?Thanks in advance for your help.

Hello Everyone,I am currently planning a migration of an existing Veeam Backup & Replication v12 (Windows-based) environment to a new Veeam Backup & Replication v13 Software Appliance deployment and would appreciate guidance from anyone who has completed a similar migration.Migration RequirementsThe objective is to migrate the existing environment while maintaining backup and replication operations with minimal disruption. Key requirements include:Migration of existing backup jobs, backup copy jobs, replication jobs, and related configurations.Migration of backup repositories and historical backup data from the existing repositories to the new repository infrastructure.Migration of Veeam Backup & Replication components, configurations, and associated resources.Maintaining replication operations between the Production (DC) and Disaster Recovery (DR) sites throughout and after the migration.Ensuring backup chains, retention policies, and restore capabilities remain intact.Min

SummaryAfter upgrading VBR on Windows from 13.0.1.180 to 13.1.1.18, Veeam Explorer for Microsoft Active Directory can no longer browse AD content from a backup. The same file opens correctly in 13.0.1.x Explorers.Symptoms (13.1.1.18)- The database loads and the object count is correct, but the domain tree collapses within about a second.- With "Advanced Features" enabled, the tree shows only six identical "Integrated DNS" nodes. No Users and Computers, GPOs or Configuration partition.- An LDAP search (&(objectCategory=person)(objectClass=user)) returns no results.Test material- A Windows Server 2022 DC, backed up as a Proxmox VM. I extracted the Windows\NTDS folder from the backup.- esentutl /mh reports Clean Shutdown, Log Required 0-0, with a valid checksum.- The same file mounts with dsamain and is fully readable in ADUC (localhost:10389).What I tested1. Same VBR server VM, restored on a separate host from a backup taken the day before the upgrade (Explorer build 13.0.1.180): the

We are a vmware shop, being priced out.  Many factors pushing us toward Hyper-V.I understand that in the early days ReFS was bug-ridden in multiple aspects.Going forward with Windows 2025 CORE Hyper-V, with VM’s of Windows2022, RHEL 9, and a few linux-based OVA deployments, what is the community recommendation for the format of the iSCSI LUNs that the VM’s run from?  there will be sizes from a couple hundred GB to all the way to 6TB, and in a special case 20TB.Our Veeam Repos are XFS, so not a factor here.Thank you kindly

I currently have one job running once at the end of day and a backup copy job pushing it to AWS after it’s don.  Is there a way to backup more than once a day but only have the backup copy job run on the last backup job of the day?  This is to make sure we don’t lose a whole day’s worth of work if something goes wrong.

Hi,i am using Community Edition of Backup and Replication.  In special i have been using a script to start Veeam ZIP to get a standalone full Backup. This has been working flawless for quite a while.There has been Issues with Powershell in the past, so i have to start the batch explizit with the “new” powershell version. But this was about a year ago.So i got a running Version of Backup an Replication (13.0.2.29) then i upgraded to 13.1.1.18 and Veeam ZIP stopped working with the following Error Message:  Error: Unable to cast object of type 'Veeam.Backup.Core.CFreeVmBackupTarget' to type 'Veeam.Backup.Core.CVmBackupTarget'.I searched the Internet and have been finding very few users with the same problem. One of them provided two solutions: Revert back to functional version, or contact Support and get a hotfix to makle changes on DLL.i do not want to revert back, because i think this is a greate Problem which has to be adressed by the support generally.I filed a case by the Veeam Supp

We are looking to migrate our 10 vm’s, currently on VMware, to Hyper-V. The host has to be stripped down to bare metal before installing the new hypervisor on it. The plan is to spin up a temporary server on a loaner machine, and migrate our critical VMs to the temp server to continue running our operations during the migration. My question is, how does one take a copy of the critical VM’s, and put them on the temp server if the temp server does not have Veeam or VMware? The temp server will have Hyper-V. Thank you.

Hi Guys,I’m rolling Veeam SQL plugin out across lots of different SQL servers in my org. Is there a protection group equivalent ? If not, how does Veeam help me to keep on top of where they are installed, and more importantly auto upgrade them when Veeam is upgraded ? On top of that how do the permissions work, in terms of local admin on all SQL servers to perform the Plugin install/upgrade ?ThanksPhil

Title: Worker VM is deleted immediately – Cloud‑Init never runs – Proxmox Plug‑In Worker Bug?Description:I am using Veeam Backup & Replication 13.x together with the Veeam Proxmox VE Plug‑In (version 3.x). The Worker Test always fails. The worker VM is created, receives a static IP (e.g. 192.168.0.28), but is deleted again after a few seconds — before Cloud‑Init or SSH ever start.Symptoms: Worker VM is created successfully Static IP is injected by the Veeam Proxmox Proxy VM boots for a few seconds Cloud‑Init does not execute SSH never comes up Veeam aborts the worker initialization VM is deleted immediately Hookscript never runs (no stop event) No logs appear on Proxmox because the VM is removed too early Storage situation:My worker storage is an LVM‑Thin pool (Data01):Codelvmthin: Data01 thinpool Data01 vgname Data01 content rootdir,images nodes pve02This storage type does not support ISO images or snippets. Cloud‑Init ISO cannot be created properly on

EnvironmentVBR 13.1.1.18 (incl. patch 20260812), all-in-one backup server on Windows 11 Enterprise (build 26200) Upgraded 2026-10-13 with the full 13.1.1.18 ISO from 13.1 (I believe 13.1.0.411) Config DB on local SQL Express (VEEAMSQL2016). Veeam ONE 13.1 installed on the same machine (test only) Repositories in folders on a local iSCSI volume (Synology LUN) + Azure Blob immutable SymptomSince the upgrade, Rescan of the backup server fails:  "Disks and volumes discovery failed Error: No connection could be made because the target machine actively refused it"  "Microsoft Windows server discovery failed" (same error)Nothing listens on 6162 although VeeamTransportSvc shows "Running". Installer Service on 6160 works.What the logs show (Svc.VeeamTransport.log, identical in Svc.VeeamFilesysVssIntegration.log and Svc.VeeamNFS.log)  Searching server certificate thumbprint in registry    New thumbprint found in registry: <thumbprint>    Certificates found: 1    Modifying export policy to

AI adoption, cyber risk, regulatory scrutiny, and data growth are changing how organizations protect and manage their information. We want to understand how these trends affect your business and which issues matter most to you. The Veeam Customer Pulse Survey 2026–2027  is an opportunity to share what your organization is experiencing and which issues you believe will have the greatest impact in the year ahead. Your responses will help inform future research, industry insights, and innovation priorities. 

Hi everyone,I am currently encountering a recurring issue during our Oracle database backups  using the Veeam Plug-in for Oracle RMAN. The backup job fails with the following sequence of errors 

Hello Veeam Community and Product Team,As a Data Recovery specialist, I frequently deal with the aftermath of modern ransomware attacks that partially encrypt backup files, as well as severe storage media failures.To better protect our mutual customers, I would like to ask: is it appropriate to discuss the internal structure of Veeam Backup files in this community? Specifically, I am interested in proposing architectural improvements such as embedding additional recovery context directly into the data block headers. This would enable the extraction of all surviving data even in the event of a 100% metadata (Metabank/Snapshot Slot) loss.Could you clarify if such technical discussions and feature requests regarding file format resilience are welcome here? Or are discussions involving deep binary layout analysis or file structure forensics generally subject to moderation due to EULA restrictions?I am asking to ensure I follow the correct channels for sharing feedback that could genuinely

Hello Veeam Community and R&D team,As a Data Recovery engineer, I regularly encounter cases of VBK/VIB/VRB archive corruption due to storage failures or ransomware attacks.When dealing with partially encrypted files or read errors, native Veeam tools often simply throw an error and abort, without attempting to extract any surviving data. To address this, I began reverse-engineering the binary structure of Veeam files and am developing custom software for their recovery.During this process, I identified the following key structural groups:Header SnapShotSlot 0 and SnapShotSlot 1 (SSS0, SSS1) Metabanks + DataBlocksThe Header contains basic info and is easy to recover. The SnapShotSlot contains critical data required to begin parsing Metabanks. This block can also be reconstructed, but only after successfully analyzing the Metabanks themselves. Next comes the Metabank table (CRC32, file offset, size). Its loss is fatal, as without it, a parser has no knowledge of the physical location

please dear Veeam support team, can you confirm if it is currently possible to replicate HPE VM Essentials Morpheus environments with Veeam

hi,i have downgraded to vbr 13.0.3.63 after trying to upgrade to 13.1.x using vbr vm snapshot. i have vbr console installed on jump server and i am using veeam vsa appliance. after the revert, i have also downloaded console from vbr vsa which i am trying to connect but sign in button is unresponsive,i have found som related logs on remote server related to console and launcher<Util.ClientLauncher.log>[22.07.2026 10:33:32] <01> Info     Connection was cancelled.[22.07.2026 10:33:32] <06> Error    Cannot access a disposed object.[22.07.2026 10:33:32] <06> Error    Object name: 'System.Net.HttpListener'.[22.07.2026 10:33:32] <06> Error       (System.ObjectDisposedException)[22.07.2026 10:33:32] <06> Error       at System.Net.HttpListener.Stop()[22.07.2026 10:33:32] <06> Error       at Veeam.Backup.Identity.Client.LoopbackHttpListener.Dispose()[22.07.2026 10:33:32] <06> Error       at Veeam.Backup.Identity.Client.AuthorizationCodeFlowExecutor

Hello everyone,I updated a VBR console to v13, but after the update, I was unable to connect to the console and received the following message:“Failed to connect to the backup server: Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins’ is denied”I noticed that when I launch the console using “Run as administrator,” I can access it without any issues. I checked the Registry Editor, and the permissions are correct.What’s surprising is that I haven’t encountered this error with other customers who have upgraded to v13.I don’t know how to resolve this issue. Do you have any ideas, or have you also experienced this problem?Thanks in advance  Bonjour tout le monde,J'ai passé une console VBR en v13, cependant après cette mise à jour je ne parvenais plus à me connecter à la console avec le message suivant:"Failed to connect to the backup server: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins' is

We remote into the Veeam server to do our choirs, but since we upgraded to 13.1 we have a problem. We can’t use PowerShell 5 since because of the requirements of Veeam. Remoting into the Veeam server using a PowerShell.7 configuration fails with “ParentContainsErrorRecordException: Exception calling "ImportByDll" with "1" argument(s): "Dependency resolution failed for component C:\ProgramFiles\Veeam\Backup and Replication\Console\Veeam.Backup.PowerShell.dll with error code -2147450750. Detailed error:Hostpolicy must be initialized and corehost_main must have been called before callingcorehost_resolve_component_dependencies. “If I do a $psversiontable in the session it says PSVersion=7.6.3What I do:Enter-PSSession -computername veamserver -ConfigurationName “PowerShell.7” -Credential $mycredimport-module Veeam.Backup.PowerShell

Hi guys, Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process -  The upgrade failed and did not allow us to retry at all. Certain options were greyed out - Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. -   In the end, we were forced to back out of out upgrade.Has anyone seen this before? ShaunB.

Hi All,I have upgraded VEM and VBR using host Management updater service from 13.0.x to 13.1.x,however after that when I opened vbr console it started upgrade of proxies server but only gives message ' Appliance OS needs upgrade'. I then go to host management of proxies deployed using infra appliance and started upgrade but it updated packages etc ...but vbr still says os need upgrade and proxies go to out of date and unavailable..i then downloaded and attached newer 13.1.x iso ti vm to upgrade and after upgrade to newer rockey linux completed, proxies are back..is there any thing i am doing wrong that updater service not upgrading os and is this iso method is ok for production..