News, guidelines and various community projects
Recently active
Or: How to renovate your backup house without setting the roof on fire Some customers have already taken a good look at the new Veeam v13.x release and its features, but for various reasons they are still running VBR v12.3. And honestly, there is nothing wrong with that. It is actually pretty normal in the IT Business.We all know the situation: A vendor releases a new major version. You nod approvingly, read through the first feature lists, maybe watch a webinar or two, and then think: “Yes, we’ll do that. Soon. Very soon. After the change freeze. After vacation. After the audit. When we have time again.” The problem is: At some point, “soon” needs to become an actual date.According to the Veeam Product Lifecycle Matrix, Veeam Backup & Replication v12 currently reaches the end of support and security fixes in February 2027. In plain English:From March 2027 onward, no production environment should still be running on v12.Unsupported and unpatched software solutions are unpopular fo
I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.
🚀 Excited to launch the Veeam for AWS Lounge in the #AWS Community! This is a place to share your experiences, best practices, challenges, and success stories related to Veeam for AWS. Whether you're just getting started or already running production workloads, your insights are welcome.Join us and let's build a great community together! 💚☁️ 👉 Join here:https://builder.aws.com/connect/space/1f69137d-ecc5-38b2-9eed-62d17b9d5cd0/veeam-for-aws-lounge
Oracle RMAN backups using the Veeam Plug-in for Oracle RMAN involve multiple components working together. When something goes wrong, the problem is not always immediately visible from the Veeam console.In this article, I want to share a real troubleshooting case where Veeam Backup & Replication reported the backup session as Success, while RMAN was reporting errors during the backup. At the same time, files were being created on the backup repository, but according to the DBA validation, the data was not being written correctly.During the investigation, the behavior changed after upgrading the plugin: the backup started but remained running for more than 24 hours and would not finish, even after restarting Veeam services.The issue was eventually resolved after a controlled cleanup of the Veeam Plug-in for Oracle RMAN, followed by a clean installation and reconfiguration. The environmentThe environment involved in this incident had:RHEL 7.9 Oracle Database 12.2 Veeam Plug-in for Ora
I just want to confirm if my understanding is correct.Lets say my veeam managed oracle rman plugin backup has this configuration:control_file_record set to 30 days.rman retention is set to 30daysveeam retention is set to 30 days.I also send the veeam backup to that offsite location, with retention period of 1 year.If I want to restore my database to 1 year ago, and rman and veeam repository already deleted the metadata, so is this the step:copy the backup from offsite back to repository (.vab, .vasm, .vacm) (should I replace the .vacm?) rescan the repository, then it will show under DISK (IMPORTED), will I be able to restore the control file to 1 yr ago now? Or do I need to run --remap backup first ? will the RMAN channel for this old backup files be different from the current one?thanks
Hi All, I want to use Veeam 13.1.0.411 for Windows.When I try to add the Veeam Infrastructure Appliance as a handheld repository, it fails.
Veeam Backup & Replication 13.0.2 dropped yesterday — and if you manage a smaller environment where a single Windows Server hosts all the things (Proxy, Mount Service, vPowerNFS, Guest Interaction Proxy, you name it), you may have hit an annoying moment when tried to open the console after upgrading the VBR server. You open up the Veeam Backup & Replication console, enter your server's name, click Connect — and instead of the familiar dashboard, you get this: Failed to connect to the backup server: the connection has been established but client update is required, however this machine is hosting other roles. Make sure these following roles are not in use and uninstall them … The message is accurate: the console client is older than the freshly updated server, and the in-place update mechanism wants you to remove other roles before it allows the console to update itself. In a larger, role-separated architecture that is fine — but in a compact single-server se
Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.
Hi everyone, i’ve been having this problem for a while now…Email notifications after backup completion are not being sent anymore to the specified email address, but when i test the credentials the email arrives successfully to my email account. I’m using the Veeam Agent 5.0 on a windows server 2012 r2. No veeam B&R is implied, just the agent making backups to a local disk.Additional informations:i recently changed the email server for the email account, before changing it everything was fine and the backup emails arrived, so at a first glance it seemed a problem with the email server; but i made a clean installation of veeam agent 5.0 on another server, using the same credentials, and the emails for the backup job are arriving regularly; so this excludes the fact that it may be a problem of the new email server(and also the fact that the email tests arrive without any problem).So i thought this may be a problem related to some veeam files regarding the old installation, so here’s
Hi community, I recently created a Runbook that walks service providers through using V13 and Vault to offer both warm-site DR plus a place to do testing when you don’t have the infrastructure. It includes an overview, deep dive, step by step instructions with videos and interactive demos. It also covers what do to once the data is in Azure and you need to get it back. The Runbook has now been published by Veeam and is available today. Please check it out and let me know what you think! VCSP DRaaS Runbook: Azure Instant Recovery with Veeam
Secure backups have always been important. But over the last few years, the requirements have shifted from “Yes, we should have backups — and ideally a second backup copy in another location and on another medium” to “Hopefully the backup still exists, is reachable, and really cannot be deleted.”Ransomware, compromised admin accounts, supply-chain attacks, and targeted attacks against backup infrastructures have made one thing very clear: a backup is only truly useful if, in the worst-case scenario, it is reliably available, usable, and uncompromised.Terms like WORM, immutability, Hardened Repository, Linux Repository, Veeam Infrastructure Appliance, single-use credentials, certificate-based authentication, Governance Mode, Single Disk, and Multi-Disk installation appear very quickly. But what is actually behind these terms, and what do I need for my use case?With Veeam Backup & Replication 13.1, the topic and the available options have been significantly improved and expanded. Bu
Hi All,I am new the the community and fairly new to Veeam and was wondering if anyone would mind sharing their own opinions and/or pitfalls experienced using the Inline Entropy Analisis feature?My organization uses Veeam for Vsphere backup and DR and I have been asked to gather information prior to using in production. I sounds great but from what I’ve read so far it has its limitations. Has anyone experienced any performance issues with backups or any other gotchas? Have you found the feature useful? Any feedback would be greatly appreciated.Thank you!
We’re having a major tape library issue with one of our clients. Do you perhaps have any ideas or solutions to suggest?(I’ve already asked the AI about this, but it didn’t help.)In their Veeam Backup & Replication environment, our client originally had four libraries:- Scalar i3-i6 03255- Scalar i3-i6 03256- Scalar i3-i6 305G- Scalar i3-i6 341G (Offline)I updated the Scalar i3-i6 03256 and Scalar i3-i6 03255 libraries at Quantum’s request following an incident involving one of the drives.Once the update was complete, Veeam took the Scalar i3-i6 03256 library offline and changed the status of the Scalar i3-i6 341G library—which had been offline—to bring it back online. Veeam thus reversed their statuses.I opened a ticket with Veeam Support, but I’m unable to provide them with the log bundles via SFTP (the file is empty every time, even though I verify that it isn’t before closing the connection), and they’re referring me to the standard documentation for tape libraries.
Hello Veeam Community!I’m thrilled to write my first post here and what better topic than the big news that just dropped? For those who haven’t heard yet, Veeam have officially acquired Object First! 🎉 As someone who’s been working with Object First’s immutable storage solution a few month at G0T0, I can confidently say: this is a game-changer for data protection, and here’s why. 🔍 Why This Acquisition MattersObject First isn’t just another backup appliance—it’s purpose-built for immutability, designed to eliminate ransomware risks and simplify compliance. At G0T0, we’ve been deploying them for our clients, and the results speak for themselves: ✅ True Immutability Out of the BoxNo misconfigurations (the #1 cause of failed restores).Hardware-enforced immutability (not just software-based). ✅ Blazing-Fast DeploymentPre-optimized for Veeam, so setup takes minutes. ✅ Cost-Effective & PredictableNo hidden licensing fees or undesirable maintenance surprises. 🚀 What This Means for the
Hello Community! European summer is officially coming to an end — I honestly can’t believe how quickly it went! I hope you’ve all managed to enjoy some well-deserved time off and come back refreshed. Meanwhile, the Community Hub definitely didn’t go on vacation! It’s been great to see how active everyone has been throughout the summer, with so many interesting contributions coming in.And once again, choosing just six blogs for August’s Blog of the Month was no easy task. I have a feeling I’m not going to make your voting decision any easier either! 😄But I need your help — which one deserves to take the August crown? Here are my top picks for this month and good luck to all of you: @kciolek , @Scott , @Michael Melter , @eprieto , @fabian.papenfuss , @Jean.peres.bkp
Everybody keeps repeating the same headline numbers from the Veeam V13 release notes when it comes to the new Veeam V13 immutability model. 40% less storage, an 8x reduction in retention calls and more than 2x fewer object storage API calls in total. I recently presented this exact topic at our German Veeam Usergroup in Cologne, and the number one question afterwards was basically: “Falko, does it really work like that ?”So instead of trusting the marketing slides, I built a lab, turned on S3 audit logging and counted every single API call myself. I guess most people already know that I love object storage In this blog post I want to walk you through what I did and what the logs actually revealed.Object Storage has quietly become the most important repository type in the whole Veeam world, and the reworked immutability engine in Veeam V13 pushes this even further. With V13, every job type can write directly to object so there are no exceptions and no workarounds. That is a pretty big
Hi,We have a 2-node Microsoft Hyper-V cluster managed by Veeam Backup & Replication Community Edition.The two nodes are:- BETELGEUSE – works normally- SAIPH – affectedThe problem is that Veeam sees SAIPH as a Hyper-V server, but its Physical Host association appears to be broken.Veeam shows:SAIPH → PhysHostId = 00000000-0000-0000-0000-000000000000and:Get-VBRPhysicalHostdoes not return SAIPH, while BETELGEUSE is returned normally.We verified that:- SAIPH is reachable- VeeamHvIntegrationSvc is installed and RUNNING- WinRM/DNS connectivity to SAIPH works- the Hyper-V host itself is operationalThe impact is that VMs hosted on SAIPH are not being backed up correctly. As a temporary workaround, we moved the VMs from SAIPH to BETELGEUSE using Failover Cluster Manager, and the existing backup jobs then work normally.An important detail: the problem appeared after the network interface cards (NICs) were replaced on SAIPH.We also checked the Veeam PostgreSQL configuration database. The hosts
2025-11-06 Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM ParallelsHello,I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.Troubleshooting Steps Completed:I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the setup again.I have confirmed that .NET Framework 4.8.1 or la
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
Hi everyone!I’m sharing what many of my clients ask me every day regarding the S3 protocol, and why it’s the best choice for a backup repository.From a security standpoint, S3 features native immutability rather than an artificially added layer. Unlike applying immutability to file or block storage—where an extra layer is imposed that can degrade performance and increase the likelihood of security vulnerabilities (most notably via administrator access).S3 provides it natively at its core.The S3 (Simple Storage Service) API has become the industry's de facto standard for cloud object storage, thanks to its unmatched scalability, stateless HTTP-based flexibility, and broad ecosystem support.Instead of rigid file structures, S3 flattens data into easily manageable objects inside buckets.While Block, File, and S3 are general-purpose storage protocols used across various use cases, S3 is the only protocol with a native mode designed specifically for the absolute immutable backup storage us
So I managed to get great feedback on my first Blog post here in the Veeam Community, and now that I have access to Claude Code i think it is time to update with my current version of the script. I now call it Get-RepositoryV2.ps1This blog post is an update to the first blog post I did 8 months ago (Part 1 / Version 1): https://community.veeam.com/blogs-and-podcasts-57/veeam-update-repository-mirror-on-iis-windows-server-12327 where the guide on how to set up the IIS and using the download script has not changed.So what changes in the new version 2? Well, I focus a bit on performance and the option to run in batch mode with a nice interface, and still have the option to output into a log file.I had the help of Claude to re-write most of the code, because getting performance means downloading multiple files at the same time.But I also found it nice to have a kind of process bar to see all the download status in parallel, that is why I made a “Live Panel” when downloading.Here are the st
On Feb 5, 2026, Microsoft officially announced that EWS in Exchange Online is being deprecated. Starting Oct 1, 2026, Microsoft will begin turning off EWS usage unless it is explicitly extended via a setting. With a deliberate “Not yet!” (aka OrganizationConfig -EwsEnabled $true), EWS is expected to remain usable until Apr 2027—however, this is not a permanent setting, just a temporary extension. So first…. What exactly is EWS? EWS stands for Exchange Web Services and was built almost 20 years ago. For many years—and up to today—it has been used as an API interface. In general, this interface no longer meets today’s requirements for security, scalability, or reliability, which is why Microsoft developed the Microsoft Graph API.By now, the Microsoft Graph interface provides near-complete functionality parity for most EWS scenarios. Microsoft’s own applications have either already migrated away from EWS or are close to finishing. Many third-party vendors have also already transitioned to
When a Windows server or workstation suddenly consumes system storage, system administrators immediately face the challenge of isolating the cause. Standard built-in Windows diagnostic utilities show high-level storage categories, but they often fail to pinpoint the exact directories, application logs, or recent file system changes responsible for rapid disk growth. Disclosure: SizeTrend provided a complimentary 10-machine Professional license to support this technical evaluation. The analysis below reflects an independent evaluation of the utility’s setup, feature set, and operational value for enterprise environments. Traditional utilities like TreeSize, WinDirStat, and WizTree solve part of this problem by enumerating current file sizes. However, SizeTrend Professional introduces historical disk scan comparison to address a more critical administrative question: “What changed on the file system? SizeTrend vs. Traditional Disk Space ToolsMany Windows administrators already have the
Hey everyone!!😎I'm really excited about all the new features Veeam is bringing in this latest release, and one of them really caught my attention: the new approach to Active Directory Forest Recovery.VBR 13.1 brings some important improvements for Active Directory protection, especially when we think about recovery scenarios after a major failure, corruption, or even a security incident.One of the features I found most interesting is the ability to perform Active Directory Forest Recovery in a more automated and guided way.Active Directory Forest RecoveryIn a traditional recovery scenario, depending on what happened in the environment, the administrator may need to perform several manual steps to rebuild the Active Directory environment.With Veeam 13.1, the idea is to make this process much more structured by using the available backups to help recover the Active Directory forest.This becomes even more important when we think about Disaster Recovery and Cyber Recovery scenarios, espe
I want to upgrade my veeam one server and it crashed à stage 3 . every time I need to roll back on backup or snaphot because it uninstalls veeamone services
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.