Recently active topics

Hello Community, We have two DC’s and running Veeam 13 for Backup and Replication of VMware Virtual Infrastructure. In previous versions we have backup server VM running in the secondary DC and replicated to the primary DC. In case of loss of secondary DC, we can recover the VM on the Primary DC by simply powering it ON and then recovering any other VMs. However with Veeam 13 we have observed that the Veeam policy doe snot allow the Veeam Server to be replicated. What should be the recovery steps for the Veeam backup server (we have deployed the Veeam software appliance)?My thoughts:Deploy a new Veeam backup server appliance with same network IP as the previous server. Import the config backup Rescan all the backup components.Is this the right approach or should we deploy the server appliance with a different IP and import the previous backup config? BR,Sudhir 

Are there anything besides the tape that need to be preserved before removing the old tape library? What are the steps to add the new tape library?https://helpcenter.veeam.com/docs/backup/vsphere/connecting_tape_devices.html?ver=120Following this the drive will automatically appear and how about the media? If the tapes are added to the tape library they will automatically appear in the media.Last step will be to create a Tape job

Hi, We are thrilled to announce the general availability of AsBuiltReport.Veeam.VBR 1.0.0 — a comprehensive PowerShell module that generates professional as-built documentation reports for Veeam Backup & Replication (VBR) infrastructure. What is AsBuiltReport.Veeam.VBR?AsBuiltReport.Veeam.VBR is a specialized report generator that plugs into the AsBuiltReport framework to automatically document your VBR environment. It produces multi-format reports (HTML, Word, Text) that capture the complete state of your backup infrastructure—from backup jobs and repositories to proxies, tape libraries integration, cloud gateways, and more. Key FeaturesReport Sections — Comprehensive coverage of all VBR components including backup repositories, jobs, proxies, WAN accelerators, tape integration, and cloud connectivity Diagram Types — Visual representations of your infrastructure, including backup-to-repository flows, proxy routing, and tape library topology Flexible InfoLevel Configuration — Contr

Currently you can only restrict the Server-Scope for File-Restore not for the whole application. So whenever you want to give an user any role more privledged than “Restore-Operator”, you cannot fully restrict the scope of servers he see in the Jobs or Server Tab...

Receiving error message “invalid system configuration detected”. Checked the logs under C:\ProgramData\Veeam\Setup\Temp\ but not finding anything. The logs end with Vmacheck upgrade.

After upgrading to Veeam 13 on Windows, I am unable to login with UI console. Access throw WEB conole works. 

 When working with tape environments, tape backup troubleshooting in Veeam is often more complex than it initially appears. Many professionals associate errors directly with faulty media. However, in real-world scenarios, issues often originate from hardware behavior, environmental conditions, or subtle physical problems.In this article, I will share real troubleshooting cases and, more importantly, explain the reasoning behind each analysis. The goal is to demonstrate how to identify the root cause instead of relying only on error messages. Case 1 – Mechanical obstruction during tape movementScenarioBackup jobs started failing during tape movement operations between slots and drives.Observed symptomsFailures during load and unload operations Errors affecting a specific range of slots Intermittent behavior that initially appeared randomExample error:Unexpected slider block, cartridge is not pushed far enough into the slot(ROB_SLIDER_UNEXPECTED_BLOCK_DURING_INSERT) TroubleshootingManual

Hello Community!This is the first in what will be several posts in the coming weeks discussing what new is coming with this Page and the new Veeam certifications.To start with, since additional content will be required to achieve the new VMCE+ certification, it has been decided upon to add another Page Moderator to the VMCE Study Hall page. With the retirement of the VMCA, it should be no surprise that we are sliding ​@jos.maliepaard  over from the VMCA Study Hall page to help as a Moderator of this page. In doing so, this will allow us to cover all the additional VMCE+ topics and items from a multitude of perspectives. And, with Jos and I being from different locations, we can cover these topics from multiple timezones as well as make learning and collaboration more conducive to multiple regions. Not that it wasn’t already, but responses to questions, etc. should be a bit more timely.So in moving forward, if anyone has any questions or concerns about this Page or its content, you can

Hi All,As I checked the release notes for the Veeam Agent for Linux that supported most of Oracle Linux 8 versions but when I tried to install the agent I’ve got this error below :2/18/2024 3:24:09 PM Failed [172.17.2.207] Failed to install veeam-6.1.0.1498-1.el8.x86_64.rpm, veeam-libs-6.1.0.1498-1.x86_64.rpm and veeamsnap-6.1.0.1498-1.noarch.rpm packages: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command  0:08:012/18/2024 3:32:10 PM Failed [172.17.2.207] Failed to install Veeam Agent for Linux: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command  Can somebody let me know why I’ve got this as what I am looking for is using Oracle RMAN backup via Veeam Backup and Replication using Agent and Oracle Plugin Appreciate your help Thanks

Veeam Community Hackathon banner. Alfred is sitting in the middle of a desk. He is about to press the run button with his paw. Binary code and a slider are shown on the left of Alfred. In the middle, the word Hackathon is shown with arrowed lines pointing to icons and text describing several aspects of the Hackathon: Development, Brainstorm, Time, Presenting, Goal, Teamwork, and Community.🚀 Join the 4th Annual Veeam Community Hackathon (2026)!We’re excited to announce that the Veeam Community Hackathon 2026 kicks off on October 7, 2026 at 15:00 CEST / 9:00 AM EST — and registrations are now open! 👉 Sign up here: https://my.veeamhackathon.com⏳ Sign-ups close on September 30, 23:59 CEST / 5:59 PM EST 🌍 What is it about?This is a global, community-driven event where teams of 12–18 participants collaborate to build innovative solutions that enhance and complement existing Veeam products.💡 Your mission:Create something that makes life easier for end users — whether that’s a dashboard, t

Hi, I’m considering supporting cross-platform recovery on a large production scale /w CC. I’m aware of the limitations presented with this. I’m really interested in hearing about experiences with recovering Prox backups into VM or Hyper-V and accounting for driver removal/install. What was your experience? Were you able to automate the workflow?  What was more problematic, Windows or Linux? What about boot loaders/Grub & Kernel drivers?  Thanks!

TL,DRIf a VMware VM has Virtualization Based Security (VBS) enabled, SureBackup can fail with “Invalid change tracker error code” during snapshot creation. The underlying cause is that SureBackup, by default, modifies the VMX and disables Virtual Hardware Assisted Virtualization (VHV) by setting vhv.enable to false, but VBS requires VHV. The fix is documented in KB4003: SureBackup for VM With VBS Enabled Fails With “Invalid change tracker error code” and boils down to creating a registry value on the Veeam Backup Server so SureBackup stops flipping vhv.enable. The symptomA SureBackup job in one of our customer environments tests multiple VMs, and suddenly one VM consistently fails with:An error occurred while taking a snapshot: Invalid change tracker error code:[25.02.2026 16:47:34.391]    <17>    Info (3)    [SureBackup] [SQL 2022] [RegisterVm] > VmRef = vm-469403[25.02.2026 16:47:34.391]    <17>   Error (3)    [SVmWareCtkHelper] Failed to disable CTK on VM, Ref: VmRef

Orchestrator Embedded VBR Repair Required.Have a ticket opened with Support for a week now but so far we haven’t figured out the cause of the issue. We have tried to refresh the Registry entry below and reset the state in the VAO DB and restarted the Backup Orchestrator Agent but to no avail.  Connection to an external VBR is working as shown above as Healthy. Thanks again for the community’s input/

Hello all,Veeam Backup & Replication Community EditionVersion before Update: 13.0.1.1071After applying the patch for version 13.0.1.2067: When I launch the Veeam Backup & Replication Console on the backup server, I am unable to connect and the following error appears: "Failed to connect to the backup server localhost. Make sure it is online and version is v13 or later".I updated Veeam with the patch and when I launch the full ISO, only the “Modify” option appears, and I could install "Veeam Backup Enterprise Manager".Either the error message mentioned above appears or this one, when I launch the console:"Failed to connect to the backup server: Client update is required but it is linked to a local server installation version. Use a standalone console installation or update your local server first."The Full-ISO contains a Shell.x64.msi, when I run it as admin, I can repair it, but doesnt change anything.Does someone have an idea how to fix that?Thanks in advance!Kind regardsTim

 Microsoft protects its cloud services like any other cloud and service provider worldwide. One of its Quality of Service protection mechanisms is API throttling, which helps prevent overload and ensures service quality for all customers. These limits affect all backup solutions based on the Microsoft Graph API, which naturally aim to achieve maximum backup throughput. Veeam Backup for Microsoft 365 and Veeam Data Cloud (VDC) must also operate within Microsoft’s technological constraints for backup. Since Microsoft recently actively removed the former workaround (multiple app registrations to bypass the limits) as of March 1, 2026, backup vendors are facing new challenges. See: Support Statement – Microsoft 365 Changes to Throttling Enforcement (24.2.2026) In this article, I explain Microsoft’s throttling mechanism, the former workaround using multiple registered applications, the impact of the new Microsoft policy, and I take a look at the future of M365 backup — because Veeam has alr

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!

Hi all,I attach the step by step procedure to perform a PostgreSQL Database upgrade. PostgreSQL: CVE-2025-1094: PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation KB4386: Upgrading the SQL Database Engine Software (Microsoft SQL Server or PostgreSQL) Used by Veeam Backup & Replication Ensure that there are no jobs or restore tasks occurring. Manually Create a Configuration Backup. (Optional) Create a backup of the Configuration Database. Stop and Disable all Jobs Stop all Veeam services on the Veeam Backup Server Upgrade the SQL database software. After the upgrade completes, restart the Veeam Backup ServerPostgreSQL Upgrade ProcedureEnsure all jobs, policies, and tasks are stopped, and those that are scheduled to run are disabled. Stop all Veeam-related services on the Veeam Backup Server. Get-Service Veeam* | Stop-Service -ForceDownload the latest version of PostgreSQL that is compatible with Veeam Backup & Replication.Note: The mo

TL,DRAfter upgrading to Veeam Backup and Replication v13, in one of our customer environments SAP HANA application backups started failing because the plug in tried to reach the repository on TCP 6162 first, timed out, and did not automatically fall back to the classic 2500 to 3300 range in our scenario as it should have done according to documentation.Opening 6162 fixed the connectivity requirement as confirmed by Veeam Support.  Our issueBackups that had been stable on v12 suddenly failed right after moving to v13, specifically SAP HANA application backups using the Veeam Enterprise plug in for SAP HANA. SymptomOur HANA jobs spent a long time “trying to connect” and then died with a timeout. In the logs it was obvious that the plug in was repeatedly attempting to connect to the repository IP on port 6162 and eventually timing out. [27.03.2026 13:17:37.846] <139893376276160> plugin_co|                 IP endpoints: [10.211.102.158:6162; 10.211.102.158:2501].[27.03.2026 13:17:37.

Is Surebackups Virtual Lab on the to do list to work with Proxmox?

Hi teamI am tasked with implementing new repositories and I have to move backups and backup copy created by AHV. It seems that moving AHV backups is not supported with VEEAM move feature.I wonder what the best options are here and what I need to be aware off?The existing repo are configured to not use per machine-machine backup files.The old repos will be decommissioned once all data has been migratedMuch appreciated 

Hi everyone,I’ve been running tests on K10 DR and immutability features for the past 3 weeks. Despite trying many different configurations, I can’t seem to recover a fully functional restore point after restoring Kasten via K10 DR... specifically when I simulate an “unintended deletion of the restore point” before performing the Kasten restoration.Here’s my use case:Create the location profile (with immutability enabled) Enable K10 DR Run a backup policy (In my test, I’m using an etcd-backup policy based on the official Kasten Blueprint: https://docs.kasten.io/latest/kanister/etcd/ocp/install) Run the K10 DR policy Delete all existing restore points from the Kasten UI Completely destroy Kasten Reinstall Kasten Create the location profile pointing to the same S3 Bucket Restore Kasten via "Kasten Restore" (K10 DR) Launch the ETCD restore using the Restore Point, which is now visible again in the Kasten UI after executing "Kasten Restore"(N.B.: Kasten version used in my tests: v8.5.5) Obs

Olá!Se você está configurando ou irá configurar o VAULT e receber este erro:  Você precisa seguir com o procedimento abaixo:https://www.veeam.com/kb4748 Super simples, porém muito importante para as primeiras configurações com VAULT