Recently active topics

Cześć wszystkim,Bare Metal Recovery z Veeam Agent for Microsoft Windows wykonywałem już wiele razy: po awarii dysku, przy wymianie sprzętu, podczas migracji i oczywiście w testach odtwarzania. Sam mechanizm nie jest więc nowy. W VBR 13.1 zmieniło się to, kto musi siedzieć przy odtwarzanym serwerze i skąd prowadzimy całą operację.Od premiery 13.1 korzystałem z Remote Bare Metal Recovery już wielokrotnie, głównie podczas wdrożeń i testów procedur recovery. W rozproszonych środowiskach ma to sporo sensu. Jeżeli serwer stoi w oddziale i ma kontroler zdalnego zarządzania, na przykład iDRAC, iLO lub iBMC, mogę zdalnie podłączyć ISO i poprowadzić odtwarzanie. Bez takiej konsoli wystarczy ktoś na miejscu, kto uruchomi komputer z przygotowanego nośnika.🖥️ Co dokładnie doszło w VBR 13.1?Po uruchomieniu Veeam Recovery Environment komputer rejestruje się w VBR jako recovery appliance. Widzę go wtedy w nowej sekcji w Web UI: Protection Groups > Remote Bare Metal Recovery, sprawdzam (sześciocyfr

Well, another week and another blog as we are at #9 of 10 today.  This blog focuses on Universal CDP and its fitment in to v13.  Check out the link below and the blog.Universal CDP in v13: Where It Fits Universal CDP in v13: Where It Fits Introduction Continuous data protection gets attention because it promises extremely tight recovery points, but that does not mean it belongs everywhere. Universal CDP in Veeam v13 should be evaluated as a targeted design choice for workloads where small amounts of data loss carry outsized business impact.That framing is important in production. CDP is not a replacement for every backup or replication workflow. It is an additional protection method that changes how teams think about network paths, storage performance, and the operational meaning of recovery success. Match CDP to Real Recovery Needs The strongest CDP use cases are the ones where recovery point objectives are already difficult to meet with conventional periodic jobs. Systems with freque

Hello,I did my Veeam 12 (VMCE) exam in September 2025 and passed it.Now when I would like to do VMCE+, I understood that I do not have to do the VBR Training, only Veeam One and Orchestrator.But do I have to do the complete Exam, including VBR?Best regrards,Michael

With all the new Veeam Releases rolling out in the past few weeks, a lot of partners already reached out with questions. With Veeam Service Provider Console 9.3 and Veeam Cloud Connect 13.1 at the core of your MSP platform, the entire stack is due for an upgrade and it's crucial that the upgrades are performed in the correct order to make sure you keep visibility and stay operational at all times.This guide walks through what’s new in Veeam Service Provider Console (VSPC) v9.3 and Veeam Cloud Connect (VCC) v13.1, and gives you a practical, step-by-step path for upgrading your hosted infrastructure and your customers’ remote installations.Enjoy and if you find any mistakes or have comments, let me know!https://blog.sddc.be/2026/08/17/upgrading-your-veeamsp-stack-to-13-1/  

Napisałem ostatnio artykuł o tym, co zwykle ogranicza prędkość odtwarzania z backupu, a że piszę na swoim blogu głównie dla odbiorcy mniej zorientowanego więc to raczej tekst nie dla Was. Pomyślałem jednak, że przy okazji zapytam zacne grono inżynierów, o Wasze doświadczenia i dam od razu małą prowokacyjną ankietę 😉Artykuł: https://anty.expert/co-naprawde-ogranicza-szybkosc-odtwarzania-z-backupu/W ankiecie nie ma wielokrotnego wyboru, więc typujcie, gdzie boli najbardziej.Macie swoje typy, to śmiało pod wpisem komentujcie!

Querida Comunidad como saben VDP 13.1 llego con mas de 70 novedades!!! Es por eso que continuando un poco con nuestro primer encuentro me puse a ordenarlos en un TOP 20. Están ordenados según tres criterios — cuánta gente se ve beneficiada, cuánto reduce un riesgo concreto y cuánto pesa en la realidad del mercado latinoamericano.EL PODIO01   Criptografía post-cuántica (híbrida FIPS + PQC)   SEGURIDADVeeam suma cifrado post-cuántico alineado a los estándares NIST FIPS 203, 204 y 205 en el intercambio de claves, manteniendo AES para el dato. La traducción: existe un ataque que consiste en robarte datos cifrados hoy y esperar años hasta poder abrirlos. El backup, que es el dato que más tiempo vive en tu organización, es su blanco perfecto. Esto es cambiar la cerradura antes de que vendan la ganzúa.02   Recuperación automatizada del bosque de Active Directory   IDENTIDADUn asistente guiado recupera un forest completo, simple o multidominio, porque los metadatos del bosque ya se capturan du

 Excited to share a new project with the Veeam community: MoovIf you run Veeam and you're staring down a move off VMware, you already know the awkward part: the backups are right there, your target hypervisor is ready, but getting the workloads across is still slow, manual, and one VM at a time.Moov closes that gap. It uses your Veeam Backup & Replication restore points as the source and brings VMs up directly on KVM platforms, Proxmox VE, oVirt / OLVM / RHV, and HPE VM Essentials, without ever touching the source vSphere environment during the migration.It's open to the community on GitHub (VeeamHub), currently in beta.https://github.com/VeeamHub/moovWhy another migration tool? Full-restore workflows work, but at scale is complex: extended downtime windows, manual VirtIO driver injection, and moving machines serially while you make some manual tasks. Moov was built for the fleet case, hundreds of VMs, in waves, with the boring parts automated.Three ideas drive it:- Veeam is the si

Greetings. On a Veeam 12.3 install, whether there be an NFS or SBM datastore, and even while trying to hold the [CTRL] key and right-clicking on any datastore, the “Access Permissions...” menu does not show up, nor is there a ribbon icon visible for “Set Access Permissions” option.The logged in user into Veeam is a Veeam Backup Administrator. This option is visible on any other Veeam servers tested.What would be the cause for this effect? Thanks in advance.

Hello, Veeam Community! In this newsletter, I'll be sharing some awesome content on the latest version of Veeam v13.1. Authors focused on topics like appliance-based architecture, upgrade planning, changes to the web UI and RBAC, monitoring, and real-world migration considerations.  It also delves deeply into cyber resilience topics such as immutability, secure restore, ransomware-aware backup design and malware detection concepts, offering hands-on guidance on replication, recovery validation, configuration restoration and troubleshooting. Alongside the technical content, the newsletter features insights from the community on blogging, collaboration and operational best practices, making it a valuable resource for backup administrators, architects and engineers preparing for modernised Veeam deployments. Here are some external resources for your reference:Veeam Data Platform latest release: https://www.veeam.com/products/veeam-data-platform/latest-release.html Veeam Backup & Repli

Recently, I was involved in a production support case where a Veeam software appliance deployed on physical hardware failed to boot after an unexpected power interruption.The system dropped directly into:“You are in emergency mode. Cannot open access to console, the root account is locked.”At this point, many administrators assume the appliance is corrupted or that Veeam needs to be reinstalled. In this case, the backup administrator had already reinstalled VBR once, and the issue happened again.  This is not a Veeam software issue. The problem occurs at the Linux storage layer, specifically with LVM and XFS.The Veeam appliance is built on LVM logical volumes formatted with XFS. During boot, Linux must detect storage, activate LVM volume groups, and mount all filesystems defined in /etc/fstab before any services start.If any of these steps fail, the system enters emergency mode to protect itself. This is a safety mechanism, not a catastrophic failure.Understanding this boot sequence ma

Hola a tod@s En esta oportunidad les traigo un post sobre las novedades de Veeam Recovery Orchestrator 13.1 (VRO), el componente de la edición Premium de Veeam Data Platform que se encarga de orquestar la recuperación ante desastres. VRO permite armar planes de recovery, probarlos de forma automática y programada, verificar que los restore points estén limpios y ejecutar la recuperación a escala, todo sin esperar a que ocurra un incidente real para descubrir si el plan funciona. En esta entrega vamos a repasar qué trae de nuevo esta versión 13.1 que salio hace poco del horno. El foco de esta versión está en Cleanroom recovery. Con acceso de solo lectura a los repositorios de backup, los planes Cleanroom ahora se conectan directamente a los targets de backup, incluidos los backups importados, y se mantienen al día sin depender de la infraestructura de producción. Esto da un entorno aislado para validar que la recuperación está lista o para investigar un compromiso, sin tocar ni depender

Hola a tod@s En esta oportunidad, les traigo un post sobre las novedades de Veeam ONE 13.1, la nueva versión de la solución de monitoreo, alertas y reporting de Veeam. Veeam ONE es la pieza de observabilidad dentro de las ediciones Advanced y Premium de Veeam Data Platform, y se encarga de darnos visibilidad de extremo a extremo sobre nuestra infraestructura de backup, virtualización y nube. En esta entrega, vamos a repasar qué trae de nuevo Veeam ONE 13.1. Veeam ONE 13.1 continúa la estrategia de observabilidad que Veeam inició con la versión 13, apoyándose en su plataforma modernizada. Esta versión se construye sobre tres grandes ejes: mayor cobertura de hipervisores y plataformas de nube, un framework completo de gestión de identidad y accesos de nivel empresarial (SSO, RBAC y MFA), y un Web Client considerablemente ampliado que trae la gestión de licencias, los diagnósticos inteligentes y la visibilidad de alarmas en contexto directamente al flujo de trabajo del operador. La versió

Often when looking at Best Practices guides, software documentation, or even during education, I see and hear the answer “It depends.” This is probably my least favorite answer, as someone who likes to understand why something is right or wrong. While it does “depend,” it makes it very tough for people starting out to understand the “why” in many cases. One thing that is not going to be the same for every Veeam user is how the jobs are created. Over the years, Veeam has made some fantastic changes and for most environments, Per-Machine backups are the way to go, the minimal savings you get do not compare to the performance and portability of this mode.  Additionally, with this mode you can often add a HUGE amount of VM’s to a job and just forget about it. I know of people who have 1 job. That is the definition of an easy button!Today I want to discuss some reasons that myself and others have gone the other direction to separate jobs.  While I keep my jobs as large as I can for the perf

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar

Hi everyone,Another week, another little project. 😀I’ve been spending some of my spare time practicing and experimenting with Codex again, and last weekend’s result is AgentBridge. The idea came from something that has bothered me for a while when working with Veeam Agent management in v13 VSA:VBR does a great job managing Agents once a machine is under management — but starting from V13, onboarding Windows machines in non-domain environments is no longer as straightforward as simply pushing via username and password. Linux certification also require SSH-based preparation and manual steps before they can be added cleanly.For one or two machines, that’s fine. But once you start dealing with more hosts, it quickly becomes painful.So I built AgentBridge.It’s a small open-source tool focused specifically on that initial bootstrap and enrollment process.You run AgentBridge as a single application on Windows, Linux, or macOS, open its local Web UI, connect it to your VBR 13.1 server, and us

  Met alle nieuwe Veeam Releases die de afgelopen weken zijn uitgebracht, heb ik al veel vragen gekregen van partners. Veeam Service Provider Console 9.3 en Veeam Cloud Connect 13.1 vormen de kern van uw MSP-platform, dus de gehele stack is toe aan een upgrade. Het is bij deze cruciaal dat de upgrades in de juiste volgorde worden uitgevoerd om ervoor te zorgen dat u altijd het overzicht behoudt alsook operationeel blijft!Deze gids beschrijft de nieuwigheden in Veeam Service Provider Console (VSPC) v9.3 en Veeam Cloud Connect (VCC) v13.1 en gaat stapsgewijs door de upgrade van uw gehoste VSPC/VCC en VBR stack alsook de remote klanten/sites.Veel leesplezier en laat het zeker weten als er fouten staan of u opmerkingen heeft!https://blog.sddc.be/2026/08/17/upgrading-your-veeamsp-stack-to-13-1/Had hem ook in VUG BeLux gepost in het Engels, maar het is gezellig om natuurlijk conversaties in het NL te hebben hier!

Hi everyone! Hope this will be helpful. The idea of the scheme was to imagine everything that could require troubleshooting and put that on the scheme. v13.1 with lots of improvements and new workloads is in progress. Attached you can find both .jpg and .pdf formats, in second one you can put any word in search and find it on the scheme if it exists there. Created in Miro, handmade with lots of user guide research :)

other possible Topic-name: When a PostgreSQL Shows Up That Isn't Yours - A field report on a new AAP warning after the upgrade to 13.1 — including the workaround Veeam Support cleared me to publish.  The symptomAfter upgrading a customers environment (doesn’t matter if VBR on Windows or VSA) to 13.1, a previously clean job started completing with a warning: a VM backup of (in this example) an Exchange server with Application-Aware Processing (AAP) enabled. Exchange processing itself was fine. The warning referred to a PostgreSQL instance that isn't really in access of the customer: an embedded component of (in this case) Trellix/McAfee Email Security running on the same guest OS.The customer told me: Vendor-managed, no credentials, no supported way to administer it.So Veeam can't authenticate against it — and flags that with a warning. The same job ran clean on the previous version.  What changedSupport's original answer was (and i have the confirmation to do this post about it): With

A greeting to allI have deployed a POC of OLVM 4 host Hypervisor version 4.5.4-1.0.31.el8, to replace Vmware infrastructure.I am successfully testing the Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization 4.1. I enclose a fairly comprehensive guide with the ste by steps of configurationWith ISO version 12.1.2.172 the Ovirt KVM plug-in is already installed.for those who do not have latest version of VBR installed download and install the pluginDownload plug inhttps://www.veeam.com/it/products/downloads.html?ad=top-sub-menuVeeam Backup for Oracle Linux Virtualization Manager and Red Hat VirtualizationPerform the following Operations   Architecture OverviewArchitecture Overview - Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization • Virtualization managerVirtualization manager is a Linux-based physical or virtual machine that manages oVirt resources such as VMs, hosts, clusters, storage domains and networks. • Backup serverA backu

As many of us know, there is a migration path from Windows to VSA Appliance for VBR.  Recently, this week I migrated another of our sites, but due to forgetting to remove the Windows VBK server from Enterprise Manager after I did the migration I could not enable some licensing checkboxes in the VSA.  I opened a support ticket and worked with them to use PowerShell on the VSA to remove the link to VEM.CAVEAT - Please ensure to have a configuration backup and snapshots of your Veeam infrastructure for rollback, just in case.After doing this, I thought it would make for an interesting blog post to help others with this type of issue, so see the link below to my blog and the blog post itself.  Enjoy.Blog - How to Remove Enterprise Manager Link after VSA Migration from Windows How to Remove Enterprise Manager Link after VSA Migration from Windows Introduction Veeam has a migration strategy for moving your Windows deployment to the new VSA Appliance by following KB4800. During this process w

 Original article: What's New in Veeam 13.1 for HPE Solutions - CloudnRoll #VeeamCommunityChallenge This article summarizes Veeam v13.1 and related release updates specifically relevant to the HPE and Veeam partnership, organized by product area: Veeam Backup & Replication, Veeam ONE, Veeam Recovery Orchestrator, Veeam Service Provider Console, and Veeam Kasten.This article includes the features and integrations that are clearly related to HPE solutions in the supplied release materials.The focus is on new HPE integrations, HPE platform support, and HPE-related feature enhancements that improve protection, recovery, observability, service provider operations, and protection for cloud-native applications.SummaryIn the v13.1 release and related release updates, Veeam significantly expands support for many HPE customers´ scenarios.In Veeam Backup & Replication v13.1, the most notable additions include native support and enhanced usability for HPE Morpheus VM Essentials, as well as

Hi, we have a Fast LTA with 5 Silent Bricks. We plan to remove them weekly, and have one brick only in the system. We want to have weekly backups rotating offsite for one month (thatswhy 5 bricks). Whats the best strategy? Currently we have one volume and one S3 share per brick, and 5 backup copy jobs, they are running on first saturday, second saturday and so on, copy of the latest backups to the brick for the current week.But what happens if there are only 4 saturdays? I have no other scheduling options to get 5 weeks. How would you implement this? Thanks.Rene

Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra

Following up on the introduction post earlier this year, version 0.5.0 of the Veeam Backup & Replication integration for Home Assistant is now available.This is a big one. The main focus of this release is to add Veeam Backup & Replication 13.1 support, but it also adds monitoring templates for backup infrastructure, High Availability clusters, licensing, and a new set of automations and dashboards. VBR 13.1 supportThe integration now supports the VBR 13.1 REST API (1.3-rev2), including the new: Proxmox VE jobs Nutanix AHV jobs There is nothing special to configure. Once connected to a 13.1 server, these workloads show up automatically alongside your existing Veeam jobs. Automatic API version detectionThe integration can now automatically determine the newest API revision supported by your VBR server. This means you can leave the integration set to Auto and let it move to newer API revisions as you upgrade VBR and the integration.If you prefer to control API version changes y

For those in & around the Kansas City area, we're having an in-person VUG event Thursday, 24 September at 1230p. Mark this date down.More details will follow soon. Keep an eye on this page & Linked In. Let me know if you have any questions. Hope to see you there!