Unanswered questions

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.

Back in 2023/24 we setup a DR site with a Ubuntu 24.04.3 LTS to act as our immutable repo for backup copy jobs. I believe this may be out of date now, and the VIA is all the range. The backups on the Ubuntu 24.04.3 LTS copy sit on a separate storage shelf to the OS, is it possible that if we were to migrate to VIA we can retain the backup files or is it a go no go situation?I’ve seen the migration process for Windows Repos to VIA and you can retain backup files, but we’re postponing that for now, we’d rather get all the other components in order.Just wondering if anyone’s managed to do Ubuntu > VIA and keep backups files?Cheers.

Cześć,Jestem w trakcie wdrożenia VB&R 13.x. Powoli sobie z wykonawca to konfigurujemy, ale nachodzą  nie wątpliwości dotyczące obciążenia sieci.Jak dobrze kojarzę to redukcja danych (dalej będę nazywał to deduplikacja) w Veeam działa w ramach jednego JOBa (savesetu). Deduplikacja nie działa na źródle, na kliencie backupu tylko na serwerach proxy więc od klienta do proxy muszą przejść wszystkie dane zaznaczone do backupu, na proxy jest deduplikacja i do storage leci już jakiś ułamek tych danych.Wątpliwość 1: Czy ruch pomiędzy klientem a proxy "nie zabije sieci"?// Fizycznie to te same inerface co produkcja, logicznie jest rozdzielone. Taki backup agentowy klienta, który ma 50 TB (a takich klientów ma z 8) w dyskach to backup typu full może trwać kilka dni. W wypadku rtych klientów mam tak, że każdy jest sam na wykrojonym datastore.Wątpliwość 2: Jakiej deduplikacji można się spodziewać pomiędzy proxy a storage? // Powiedzmy, że na kliencie jest każdy typ danych: 60% dokumentów docx,

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

Buongiorno a tutti: nella console di VEEAM BACKUP & REPLICATION 13 abbiamo un JOB che è rimasto appeso da 43 giorni e quando proviamo  a cancellarlo restituisce il seguente errore:    A qualcuno è già capitato?Come possiamo risolvere?Grazie

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.

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

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

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 

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

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

Hi team,Thank you for building and maintaining the Veeam Calculators.I'm reaching out because a partner re-ran a NAS sizing with the exact same inputs as before and got noticeably different results after the recent update. They need to explain the difference internally before requesting additional resources, so I'd like to understand what changed in the logic.Inputs (identical in both runs)- Source: 40 TB, 4 shares, 1M files, 5% daily change rate- Backup window: 8 hours, retention: 60 dailies (no GFS)- Immutability: enabled, 60 days, block generation 10 days- Storage: Block Storage, compress by 10%- Growth rate: 0%, forecast: 0 years- New in the latest run (Advanced, defaults): network speed 40 Gbps, array max IOPS 400,000, array count 1Previous result- Repository: 264.4 TB- Proxy: 2 cores / 4 GB- Cache repository: 2 cores / 12 GB, cache space 1.0 GB- Repository compute: 2 cores / 8 GB Current result- Repository: 144 TB- Proxy: 1x 8 cores / 16 GB- Cache repository: 6 cores / 16 GB, cac

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

Hallo Community, Ich habe zwei ESX-Hosts mit VmWare (ohne vCenter). Auf denen laufen insgesamt 19 VMs. Mein Problem: 2 von den 19 VMs können von Veeam nicht gesichert werden. Die anderen 17 werden in dem gleichen Backup-Job mit den gleichen Einstellungen gesichert. Ich habe den Veeam Server und auch die zu sichernden Server neugestartet. Leider ohne Erfolg. Den Virenscanner habe ich auf dem Veeam Server versuchsweise auch deaktiviert. Der Veeam Server kann die beiden Server z.B. per Ping erreichen. Gestern habe ich das Update auf Version 13.1.0 installiert. Same Text in english:(Hello Communitiy, I have two ESX-Hosts with VmWare (no vCenter). 19 VMs running on this two Hosts. My Problem is two of 19 VMs cannot be saved by veeam. The other 17 VMs will be saved in the same Backup-Job with the same properties. i have restart the Veeam server and the both target Servers. I deactived the anti-virus for testing but nothing changed. The Veeam server can reach the both VMs with for example pin

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 

veeam 13 agent not available for wndows 10 32 bit workstation. 

bonjour comment peut on créer un media recovery sur une version datacenter 2022 ? merci

Hello, Thanks for the great forum.Lets’ say I have a laptop running VAgent community edition, standalone.On that agent, I create a standalone full backup onto a usb key.The laptop has NOT been connected to my Community Backup and Replication Server.Now, I want to take that standalone full backup from the usb key, plug it into my Veeam Backup and Replication Server and do an instant restore of that full backup.Is that possible.If so, all I need to do is do the import and then do the instant restore?Is there more steps involved?I could not find the answer in Importing Veeam Agent BackupsRestoring Veeam Agent Backup to Hyper-V VMThanks Much, David

Hello,I’m running Veeam Backup & Replication 13.1.1.18 with the Community Edition (free, no paid license and no active maintenance contract). I’m trying to add a Veeam Infrastructure Appliance (VIA) as a Hardened Repository, installed from the latest ISO available, and I’m stuck.SetupVBR 13.1.1.18, Community Edition VIA installed from the most recent ISO Versions shown on the VIA: Veeam Deployment Service: 13.1.1.18 Veeam Updater: 13.1.202.0 Veeam Host Management Console: 13.1.1.9 Problem 1: Add Linux Server wizard fails at the “Apply” stepAfter accepting the server certificate, the wizard gets through “Starting infrastructure item update process”, “Resolving server certificate” and “Configuring the identity service connection information”. It then fails with:Software updates require an active maintenance contract.Failed to save Linux server: Software updates require an active maintenance contract.Problem 2: SSH elevation fails when using single-use credentialsWhen I retry using

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

Is VBR support to backup and restore to Tencent Cloud?

Всем привет,Наш файл резервной копии Veeam Agent был частично зашифрован программой-вымогателем. Процесс шифрования был прерван, и затронута только первая часть файла (1 МБ).Подробности: - Файл: dm-1c2 - 192.168.10.x.vbk, ~630 ГБ - Ошибка при монтировании: "Не удалось создать резервную копию источника монтирования. Версия хранилища [...] не поддерживается для доступа только для чтения" — заголовок некорректен. - vbkview завершается с ошибкой "недопустимое максимальное количество банков слота снимка". - Шифрование резервной копии (пароль репозитория) НЕ было включено. - Файл метаданных .vbm полностью цел и доступен для чтения (XML, версия 2626). - Критические идентификаторы: Идентификатор резервной копии = 508d4cc8-d124-4053-b6fb-b4a5190445c6, Идентификатор задания = d0d61837-77e6-4b8b-8319-fc6a449901db, Имя задания = dm-1c2, Тип задания = 12000 (Агент Veeam). - Шестнадцатеричный анализ подтверждает: все данные, начиная со смещения 1 048 576, целы — нули, стандартные индексные структуры

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

I'm running the latest version of Windows 25H2 version, and Veeam version 13.0.3.1220.  I installed Veeam Agent for Microsoft Windows Free version, and created the USB Recovery Media. I then did a test Bare Metal Restore.  I immediately get the error: Authentication failed, see inner exception.If I use old Recovery media created on an different PC, that is running an older Windows version with an older version of Veeam, the restore process works just fine. I don’t get the Authentication error. I found a post on Reddit, where everyone was having this same problem. One poster said he opened a support ticket with Veeam, and they acknowledged the problem. But I can’t find any information on what Veeam is doing about this very significant bug. Does anyone have an update on this bug? Is Veeam planning a fix, and where can I find a timeline? I’m not updating my Veeam version on the older PC, as I don’t want to introduce the bug on that PC. Thank you.

What are the prerequisites for using Changed Block Tracking (CBT) with VM backups in Veeam Kasten on OpenShift Virtualization 4.21? How can we validate that CBT is enabled and being used during backup operations?If the CSI driver does not provide native CBT support, is there any workaround that combines the CSI driver with KubeVirt, libvirt, or QEMU modifications or configuration changes to enable incremental backups based on changed blocks?