Community

Veeam Backup & Replication v13 has arrived with significant improvements in security, performance, and data governance. I recently performed the upgrade from version 12.3, and in this article I share the entire process, from preparation to post-upgrade validation, following the official Veeam documentation. The goal is to present a practical, real-world experience while highlighting what’s new in this anticipated release. Preparing for the UpgradeBefore starting the upgrade, I followed Veeam’s recommended best practices to ensure a smooth and safe process. This included: Checking system compatibility, supported OS, storage repositories, hypervisors, and all backup infrastructure components. Ensuring no backup jobs were running. Updating the Guest Catalog and cleaning up old sessions. Performing a Configuration Backup, which stores all settings from the Veeam server. Creating a server backup or snapshot as an additional safety measure—especially recommended for production en

Happy Monday, Veeam Community! I am pleased to bring you another Vanguard Newsletter, which includes all the amazing content that our heroes published during August. Take a look at the range of topics available in this newsletter and make sure you find time to read it, as it contains lots of practical information, whether you're planning an upgrade to v13.1 or managing any other Veeam product. This newsletter edition is packed with practical insights, fresh updates, and hands-on guidance around Veeam Data Platform 13.1. Whether you’re planning an upgrade, exploring the new Veeam Software Appliance, strengthening your cyber resilience strategy, or simply keeping up with the latest platform enhancements, this month’s articles are designed to help you move from “what’s new” to “what’s next”.A big focus this month is on real-world adoption: upgrade walkthroughs, migration tips, lessons learned, and troubleshooting guidance to help make the move to Veeam Backup & Replication 13.1 smooth

Since we added Linux Repositories to our Veeam Backup environment in my post from last week, why not add some Linux Proxies as well? I will show you how in this post. And trust me…this one will be far less painful. But adding Repositories wasn’t so bad, was it? 😏 System RequirementsThe first thing you need to do is check what OS's, hardware, and software are supported. Supported Linux OS's are exactly the same as with Repositories and are listed below:Linux Proxy RequirementsAs far as hardware goes, your server should have a minimum 2-core CPU, plus 1 core per 2 concurrent tasks (take note, this is a peformance enhancement since v12, up from 1 core per 1 concurrent task); and minimum 2GB RAM, plus 500MB per concurrent task. But for best performance and to run multiple Jobs and tasks, you should have much more Cores and RAM than the minimum. As with the Veeam Repository, look to the Veeam Best Practice Guide for actual Proxy sizing guidelines.The remaining requirements depend on the Ba

Previous versions (12.3 and 13.0) can be found here A new version & improved scheme is alive!Reworked a lot to make visibility better, added some extra information, fixed some small mistakes I did with plugin and app backups, decreased possible confusion in several places. Important Notes about using the scheme:You can search for text in PDF version. But not through the images (logos of workloads) though. That’s limitation of PDF. I can share Miro link if needed, where all alts are there. Scheme requires just few minutes (don't spend more!) to get familiar with it and once you have an issue or just a question about something you don't remember or never knew how it works - first start with it to see general workflow and relationships before digging into the guide.

With the Veeam Software Appliance and the Veeam Infrastructure Appliance, update distribution is fundamentally changing. The Veeam Appliances automatically install certain updates to ensure security and operational continuity. This represents a massive increase in security and compliance. What is updated?Operating system and security updates are installed centrally and automatically, cannot be deselected, and are mandatory for both appliances. Security updates for Veeam Backup & Replication are also installed automatically and without user intervention to ensure security.Both appliances can also optionally install feature and bug fix updates automatically, provided this is enabled in the configuration. Major updates (e.g., V14.0), minor releases (e.g., 13.x), and private fixes are optional by default.Here is a simplified overview:Mandatory updatesVeeam cumulative & security updates (e.g., 13.0.x) Operating system security updatesOptional updatesMinor product updates (e.g., 13.x

I’ve been setting up some reporting for users in Veeam one and this is a great feature if you want to quickly determine the cost of your backups for each VM or Job.  It’s also a great way to see what each job is costing per repository.  Warning…. with current storage prices, this my shock you!!!! I did however find it wasn’t as straight forward as just adding the price of the repository and clicking run. There is also quite a few options you can choose to make the reporting tailored to those who are intended to receive them.     The first think you will want to do is select the time frame for your report. In my case I selected as far as my retention was to get the full cost.  You can use the “Last” radio button and change weeks to years.    For the multipliers if you have different types of storage make sure to click configure to set it individually.    You can select a repo with multiple extents and apply multipliers for each as well   Multipliers are based off of the price included i

Status: 02.09.2026Tested with: Veeam Backup & Replication 13.1 and NetApp ONTAP Plug-in 2.0.14Spoiler: Yes, coexistence works. But randomly clicking around is not a good idea. Anyone who has known me for a while knows that I started in IT as a System Engineer back in 2005 — and since then, NetApp systems have regularly crossed my path. Or maybe I crossed theirs. Depending on perspective.Over the years, I have built, configured, troubleshot, and occasionally lovingly cursed at NetApp systems in small, medium-sized, and very large environments. I had the chance to gain field experience worldwide, later trained people on NetApp while still implementing them in costumer projects, and was also involved with the topic strategically as a Head Architect and Product Manager/Director.Long story short: I have a certain historical affinity for NetApp systems. Even though I no longer deploy them on a daily basis, my inner storage heart still gives a little twitch whenever snapmirror, igroup, Fl

I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate

Key Takeaways from the El Segundo Zero Day Resilience WorkshopCyber resilience is not proven with a static Disaster Recovery plan. It is tested in advance through training and practice. It is proven in the moments when operations fail and an organization can respond with speed, clarity, and confidence.I recently had the opportunity to help host a Veeam Zero Day Resilience Workshop in El Segundo, California, where IT and security leaders from education, health, manufacturing, marketing, and public services came together to share how they would respond to a fast-moving cyberattack. The viewpoints from CISOs, CTOs, security analysts, system administrators, IT directors, and more enabled valuable discussions from many angles on how to prepare in advance to successfully counter a cyberattack.If a Veeam-sponsored security workshop is available in your area, I would highly recommend attending for the insight provided. Here are the highlights and key takeaways.Workshop Keynote Highlights69% of

Hello Community, Sharing an update that Veeam announced about production license distribution. This will matter for anyone who handles orders or helps customers access their license files. What’s changingStarting December 4, 2025, production license files will no longer be sent as attachments in order confirmation emails.This includes purchases through the online store, public marketplaces, and distributor marketplaces.Going forward, the designated license administrator for the customer will need to download the production license directly from the My Account portal under Production Licenses.Trial and NFR licenses are not affected. Why this matters• Improves security and keeps license access tied to the right admins• Makes it easier for customers to retrieve licenses in one place• Partners need to make sure the correct customer license admin is specified on every order or the customer may not see their license in the portal Figured this would be helpful for the community since many of

Hi. We followed the Veeam documentation to install the IBM AIX agent in "pre-installed agent" mode, but we later realized it could also work within an "individual computer" protection group. We believe the latter approach is better because the pre-installed agent method requires manually triggering synchronization on the AIX host or waiting up to six hours for it to occur. I found a Veeam article explaining how to migrate between protection group types, which I’ve included at the end of this message.The agent—version 13—has just been installed; we used the XML file provided by the Veeam console, and the connection was successful. Since we prefer the "individual computer" method, and I believe moving it avoids the need to revert to standalone mode (allowing everything to be managed from the console), could you please confirm that this procedure works as expected? I’d like to proceed with this change.Here is the link:https://helpcenter.veeam.com/docs/vbr/userguide/agents_protected_comput

IntroductionThis week I upgraded our internal lab/PoC environment from Veeam 12.3.2 to 13.1. I'd like to share my experience with this upgrade — what worked well, what you should prepare for, and a few things that aren't immediately obvious from the release notes.Here's an overview of our lab/PoC environment:Enterprise Manager (Windows Server 2022) Backup Server (Windows Server 2022) ONE Monitoring (Windows Server 2022) 2x Backup Repositorys, Performance Tier (Windows Server 2022 / HPE ProLiant DL380 Gen10) 2x Backup Repositorys, Performance Tier, used for Backup Copy (Ubuntu Server 24.04 LTS / HPE ProLiant DL380 Gen10)On the virtualization side, we run a full VMware Cloud Foundation 5.1 stack, including the Enterprise Manager integration (Veeam plugin) in VMware Cloud Director.Storage integration is not currently in use, and neither are Veeam backup agents — so this is a pure virtualization backup environment.This setup essentially mirrors our production environments, which made it a

Hi everyone. I have a question: I want to upgrade from Veeam 12.3.2.4854 to Veeam 13.0.3.63. However, I have an immutable repository running on RHEL 10.2; as you know, the SSH port is disabled. Since the new version needs to be applied to the components on the immutable repository, is it necessary to enable port 22, or can the upgrade proceed even with that port disabled? I hope that makes sense.

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