News, guidelines and various community projects
Recently active
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
Всем привет,Наш файл резервной копии 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, целы — нули, стандартные индексные структуры
HiLast week, we renewed the certificate on vCenter and since then CDP has been failing. The CDP jobs showed the messages similar toWarning : Restore point creation completed with warnings. (Failed to create restore point 02 November 2026 08:00:18 (attempt 1 out of 3)) Error: The remote certificate was rejected by the provided RemoteCertificateValidationCallback If I disable the CDP job and then re-enable again, I get the messageFailed : Enabling CDP completed with errors Error: The remote certificate was rejected by the provided RemoteCertificateValidationCallbackAndFailed : Failed to enable Continuous Data Protection: Could not establish trust relationship for the SSL/TLS secure channel with authority All replication jobs and backup jobs appear to be running fine. If I go through the properties of the vCenter host, I am never prompted for a certificate and the host discovery completes with no errors. I have the option “Add all discovered hosts to the list automatically” enabled under
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
Congratulations @Marcel.K ! Your article NFS Repository Performance Revisited: Hidden NFS Mount Tuning in Veeam earned the most community votes, making you the BOM September 2026 winner. Well deserved! 👏
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.
🤖Disclosure: this post was created in conjunction with GrokBot; everything has been tested and verified.I wanted to find an alternative to StarWind and Quadstore for lab testing of VTL and found Holo VTL (https://github.com/Holo-VTL/Holo), an open-source virtual tape library that runs on a Linux VM.Here's how I got it working with VBR in my lab (note that there are some issues with the current main branch, which I have fixed in a fork and raised an MR on, see below for the fixed fork).What you needA Linux VM running Holo, with a second blank disk for the storage pool. Holo only lists whole disks that have no partitions and no mounted filesystem, so if the pool wizard shows no disks, add a raw disk to the VM and refresh the page (or reboot). VBR v12 or later (the Linux tape server needs it). I used the Veeam Software Appliance. Network access from VBR to the Holo VM on TCP 22, 6162 and 2500-3300Create the storage poolIn the Holo UI, create a pool on the blank disk.Create the virtual li
Hi Community, During the projects I have been working on, or in the VMCA classes I teach, I use drawio.com to make diagrams. It is a simple and free tool to use. However, the Veeam icons are not always up to date on it. So, to improve the quality, quantity and standard of the Veeam icons, I share many other formats with you.So, you can use drawio as a diagram tool and the Veeam icons in SVG format. Once drawio is open, you just need to copy and paste the desired icons into the drawio window.For those who use Visio, I’ll attach the visio stencils as well.
SAML single sign-on in Veeam Backup & Replication v13 lets your identity provider handle authentication while Veeam keeps control of authorization. Users sign in with their corporate identity, MFA and Conditional Access policies apply upstream, and Veeam stops being one more place that stores passwords.The setup is simple. The part that trips people up is group mapping, and it comes down to which Microsoft Entra ID license you have.The mental modelKeep this sequence in mind for both setup and troubleshooting:Trust. Veeam trusts Entra ID as the identity provider through exchanged SAML metadata and the signing certificate. Assertion. After the user authenticates, Entra ID sends a signed SAML assertion containing claims about that user. Identity mapping. Veeam matches a claim (the user's UPN or a group claim) to a user or group in Users & Roles. Authorization. Veeam applies the role assigned to that user or group.Entra ID proves who the user is. Veeam decides what they can do.Step
During the upgrade of Veeam Backup & Replication to version 13.0.2.29, I encountered the following warning during the Configuration Check phase:Trusted hosts hardeningYour remote host trust option is set to Manual. After the upgrade, open a backup console and make sure all your backup infrastructure servers are trusted. At first glance, this message may seem concerning, but it is important to note that it is not a blocking issue and does not prevent the upgrade from completing successfully.Why Does This Warning Appear?Starting with recent Veeam releases, the platform has introduced additional security controls to strengthen communication between backup infrastructure components.In my environment, the Remote Host Trust policy was configured as Manual. This means that Veeam does not automatically trust remote infrastructure servers such as:Backup Repositories Backup Proxies Mount Servers WAN Accelerators Other managed Linux or Windows hostsBecause the trust relationship must be verif
For years, we have heard the same prediction: tape is dead.Earlier this year, I had the opportunity to take part in a Veeam Oxford Style Debate around the statement “Tape Is Dead”. The discussion brought up strong arguments on both sides, especially around object storage, immutability, cloud and modern archive solutions. But from my experience working with backup environments, I still believe tape has a place in a modern data protection strategy.Disk storage became faster and more capable, object storage became more accessible, immutable repositories became an important part of ransomware protection, and cloud changed the way organizations think about long-term retention.And yet, tape is still here.Veeam Data Platform 13.1 gave me another reason to revisit that discussion. The platform continues to evolve around new virtualization technologies, storage integrations, security and archive capabilities, while tape is still part of that evolution.So instead of looking at tape as an old tec
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
@Rick Vanover and I are back with another Community Recap, and we have quite the mix this week!Who are you gonna call when it comes to the new Security Officer? What happens when Enterprise Manager seems to have its own sense of time? Where did that SAML group claim go? And if you’ve been wondering what Veeam iResOps actually is, we’ve got you covered there too.Plenty of great community content to get through, a few things to learn, and, as always, some thoughts from Rick and me along the way.Come catch up with us! Featured Contentvia @Andreas Buhlmann via @fabian.papenfuss via @Chris.McDonald Vanguard Blog SpotlightThis week VBS comes from @zamaan.ali , and he’s taking a newly launched Veeam concept, iResOps, and trying to explain it in a really simple way. We know we can recover. But do we know exactly what we need to recover? I think that’s where the conversation around iResOps gets really exciting!Special Department News: On Demand VeeamON Virtual Event 2026 until December 18
The failure that wasn't a failure Every backup admin knows the drills for a dead array: a controller dies, a BBU gives up, a broken drive corrupts a stripe, you rebuilt, restore and move on. What almost broke us at two independent customer sites was none of those. It was worse, because nothing was actually “dead”. The symptom: not down, just uselessly slow Two of our customers are running fully independent 2-node HCI clusters using a 3rd party HCI solution inside VMware VMs on ESX 8. As usual, the storage-VMs are consuming all the local storage on the nodes and - while mirroring via LAN - give it back to both hosts via iSCSI. Many HCI vendors go down this path.Both clusters ran flawlessly and fast for 7+ (!) years with roughly 40 VMs on top of each cluster.Goal was, to have them distributed and fully redundant between two fire zones on the campus.But suddenly and within two weeks, those two customers independently reported major outages for their systems to us. The systems never went
With my colleague @zzsoka we have developed a procedure the inject needed variables for initial configuration of the Veeam appliances and now we would like to share it with you. When you deploy Linux appliances at scale, cloud‑init is usually the go‑to mechanism for injecting instance‑specific configuration (IP, hostname, NTP, credentials, etc.) at boot time. However, the Veeam Software Appliance used here does not ship with cloud‑init currently, so we need another way to achieve the same result: build one customized ISO and then let vSphere guest variables drive per‑VM configuration.This post walks through how I achieved that using:- a customized Kickstart file,- a customized GRUB configuration,- VMware guestinfo / OVF properties as the source of truth for variables, and- a small shell script that dynamically extracts and uses `vmware-rpctool` (even though open‑vm‑tools is not installed in the installer environment), cleans up after itself, and hands configuration over to the post‑i
The Ingram Micro Technology caravan was built with a modular design in mind. It was originally built to showcase our product portfolio, with its original design focused on IoT devices and integration. Over time, it evolved and was converted into a mobile datacentre to showcase the Whole ecosystem.It now features an 18RU rack inside and has previously featured HPE routing and switching solutions. As technology changes, so does the caravan, and it continues to evolve to showcase different technologies and use cases. My Latest ChangeRecently, it has gone through its most significant change yet, moving away from the Broadcom VMware hypervisor and now showcasing HPE Morpheus VM Essentials (VME) as its primary hypervisor.As part of the migration, I used Veeam Data Platform (VDP) to back up workloads from VMware and restore (transform) them into HPE VME.I was fortunate to start this project just as the production release of VDP 13.1 became available. Migration ExperienceThis didn't come witho
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.