Community

We are planning to upgrade Veeam Backup & Replication from v12 to v13, and I understand that PostgreSQL will be upgraded from version 15 to version 17 during the upgrade process.After completing our validation, including backup and restore tests, we would like to uninstall PostgreSQL 15 from the VBR server.Could anyone share the recommended procedure for safely removing PostgreSQL 15 after the upgrade? Are there any prerequisites or checks that should be performed before uninstalling it?Thank you in advance for your help.

Using YARA rules in the backup environment With the rise of cyber threats, particularly ransomware attacks, simply performing backups and restores is no longer sufficient. Restoring data without ensuring it is free of threats can lead to re-infection of the environment.Starting with version 12.1, Veeam Backup & Replication (VBR) has integrated native support for YARA rules into its Malware Detection ecosystem. This combination enables data integrity validation both before and during recovery processes. What are YARA rules?YARA (Yet Another Recursive Acronym) is an open-source tool widely adopted in incident response to identify and classify malicious artifacts.Unlike approaches based solely on the closed signatures of traditional antivirus software, YARA operates using customizable rules:Pattern-based signatures: Identification via specific strings, byte sequences, hashes, or file structures. Conditional logic: Precise rule definition to determine whether a file is malicious or ano

Ever since I discovered the Magic Ports port-mapping tool, I've had the idea of creating a solution where you simply provide a list of systems (ESXi, vCenter, Veeam Backup & Replication, Veeam Repository, etc.) and assign their roles. From that alone, the tool automatically generates both a graphical and textual representation of the relationships and TCP/IP communication between them. Those relationships are automatically scraped from the Veeam documentation and stored in a SQLite database.I also created an interactive explorer that lets you navigate and better understand the relationships between the many Veeam roles.Building on my previous experience generating Draw.io diagrams with Python, I started developing this tool. After overcoming quite a few setbacks, I finally decided to publish this proof of concept (PoC).The project is still incomplete and currently supports only Veeam Backup & Replication v12, so it isn't fully up to date yet. However, I think it's mature enough

The StartThis series of blogs, which I will try update weekly, is about me getting to understand Kubernetes and is for someone like me coming from a level of zero dot 1, a true beginner. If you have been working with containers and know something about it, you will most probably be bored with these blogs although you might also learn something new. Luckily in this Veeam Community we have some very high-level resources that I am sure will deliver some interesting insights, and ​@Geoff Burke  has kindly agreed to moderate my journey before I take you down the wrong rabbit hole too far.Please comment and discuss freely so everybody can learn what seems to me at present a confusing technology, but don’t try proving your prowess - this is for us that do not know to learn by taking baby steps helped along the way by you.I will be writing down my understanding while doing some basic courses, reading what AI has to say about what I still don’t understand – and spending my evenings watching You

When ransomware hits, the pressure to restore starts almost immediately. People want systems back, and every minute of downtime hurts. The recovery team is expected to move fast. That pressure is real, but moving too fast is how bad recovery decisions get made.My rule is simple: do not reconnect a restored workload to production until the recovery point has been validated in isolation.The newest restore point is not automatically the right one. Encryption may be the first visible sign of an attack, but the attacker could have been in the environment for days or weeks. A successful backup tells us that Veeam captured the data. It does not tell us whether the workload is safe to reconnect.Start with the incident timeline. Work with the security team to identify when the compromise may have started and select a candidate restore point from before that window. For Windows workloads, Veeam Secure Restore can then scan the restore point with Veeam Threat Hunter, supported antivirus software,

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

The Veeam Configuration Backup is one of those features that may not receive much attention until the day it is actually needed.It protects the configuration of the Veeam Backup & Replication server, including jobs, repositories, proxies, credentials, infrastructure settings, security information, restore sessions, and catalog data.This becomes especially important in environments that use tape.If the Veeam Backup & Replication server needs to be rebuilt and there is no valid Configuration Backup available, additional recovery steps may be required. In a tape environment, for example, it may be necessary to inventory and catalog the tapes again before their contents can be properly identified.During a recent troubleshooting scenario, I encountered an issue where the Veeam Configuration Backup failed every time it was executed.At the same time, the Users and Roles section of the Veeam console was not loading correctly.In this article, I will describe the symptoms, the precaution

Hi everyone,We're currently using the new Veeam Backup & Replication v13 Appliance and have a question regarding post-backup automation.In our previous Windows-based Veeam installation, we had a scheduled task that would automatically shut down the backup server after the backup job had completed successfully. This worked well for our 3-2-1 backup strategy, as the backup server only needed to be online during the backup window.After migrating to the v13 Appliance, we can't seem to find a similar option or supported method to automatically power off the appliance once all backup jobs have finished.Has anyone implemented this on the v13 Appliance? Is there a built-in feature, or is there a recommended approach for scheduling an automatic shutdown after all backup jobs have completed?Any suggestions or best practices would be appreciated.

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

Well, even being on vacation the series must continue, so I present to you blog #5 in my series around v13.  You can read it below as well as on my blog site via the link.Blog - How I’d Monitor Veeam v13 in the First Week How I’d Monitor Veeam v13 in the First Week Introduction The first week after a rollout is where a backup platform proves whether it is stable under normal production load. A single successful backup window is a good sign, but it is not enough to establish confidence in a newly upgraded or newly deployed v13 environment.Early monitoring should focus on patterns. Repeated warnings, creeping runtimes, repository latency, or noisy alerts often tell a more useful story than one obvious failure. The goal is to establish what normal looks like before the environment becomes busy enough to hide drift. Watch Job Trends, Not Just Failures The most important view in the first week is the trend line across scheduled jobs. Administrators should look for backups that complete more

If I had to share just one tip this #SysAdminDay, it wouldn't be a Veeam feature or a PowerShell script.It would be this:Know the environment you're protecting.It may sound simple, but it's one of the biggest lessons I've learned after working on many projects and handling several incidents over the past few years.Many people see a backup administrator's job as checking whether backup jobs completed successfully. Of course that's important, but in my opinion, that's only the tip of the iceberg.Long before an incident happens, the basics need to be done right. Healthy backups, a solid 3-2-1-1-0 strategy, monitoring, restore testing, up-to-date systems, security features, and good governance. Those are the foundations that give us confidence that, when the bad day comes, we have a real chance of recovering the environment.But there's something that becomes even more valuable when everything starts going wrong.Knowing the customer's environment.When an incident happens, customers panic. A

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

Hello everyone, I am looking to schedule daily backup jobs and copy jobs reports using powershell in veeam backup server. Could you please provide me the suitable script for reports as per jobname, server, latest backup run time, status. Backup version is 13.0

On of the large risks in IT isn’t just Ransomware, hardware faults, or even disaster recovery events.What happens when the person who knows how everything works quits? In many organizations, especially smaller ones, the Veeam Admin is not just responsible for dealing with backups and restores all day. Some of the tasks us Administrators do are:Windows Server Administrators Virtualization Administrators Storage Administrators Security Administrators Network Administrators Domain Administrators Cloud Administrators Disaster RecoveryYou get the point, we wear many hats, and have a lot of access and knowledge. Here are a few things you need to do in the case someone who is responsible for these items do. 1. Change Every password  they knew.Veeam Service accounts, Repositories, Hypervisors, OS’s, Storage, Tape libraries, Storage arrays, Switches, Firewalls, Server management, Cloud accounts, Enterprise applications, Encryption passwords…. The list goes on and on, but you don’t know what was

From Veeam 12 to Veeam 13: Building a Future-Proof Backup & Recovery PlatformIn the coming period, we will take an important step in further strengthening our digital resilience. Our current Veeam 12 environment will be migrated to Veeam 13, based on the new Virtual Appliance architecture. At the same time, we will replace our existing, technically end-of-life backup hardware with a completely new infrastructure.For VNOG (Veiligheidsregio Noord- en Oost-Gelderland), cyber resilience is essential because our services directly support public safety and crisis response, where continuity really matters. VNOG is a regional public safety organisation responsible for fire and rescue services, we provide essential fire-fighting services and assistance in the event of accidents, disasters and crises to the 870,000 citizens of North and East Gelderland in the Netherlands.The new design is distributed across two data centres. Within our vSAN environment, which hosts approximately 180 Windows

Veeam Backup and Replication v13 on Windows includes an option to define a custom mirror repository. But what repository should you actually mirror? Is this option even intended for the windows based installation, cause it feels like the offical repos only host updates for the software appliance.

I’ve been going through an AWS course recently, and while reading about S3 versioning, I was wondering how many times people look at versioning, backup, and disaster recovery thinking they solve the same problem.It’s a very common way to think about them, but once you start breaking it down, it becomes clear they operate at completely different layers.They all fall under the broader idea of data protection, but mixing them up usually becomes obvious when something actually goes wrong.Versioning (AWS S3 Versioning)This is the most immediate layer. I think in AWS, S3 Versioning answers a simple question: “Can I recover a previous version of this object?”If something gets overwritten or deleted, S3 keeps older versions so you can roll back.It’s fast, simple, and very effective for small mistakes — an accidental overwrite, a bad update, or a quick rollback.But it’s still operating inside the same system. Same bucket, same environment, same trust boundary.So it works well for object-level r

 I got this number wrong on my first pass, so this post is partly a correction to myself. While fact checking a storage economics piece, I pulled the Block Generation figure from the unstructured data immutability page: up to 10 days added on object storage. Then I found the dedicated Block Generation page giving 30 for some providers. Same user guide, different answers, and a 20 day spread between the documented values. That seemed worth running all the way down. Short version: the feature is smart, the savings are real, and it's often missing from the capacity math I see.What Block Generation actually is Immutability on object storage is enforced object by object, and that creates a scale problem. A typical daily incremental reuses most of the blocks already sitting in the bucket. Veeam has walked through the math on the R&D Forums: at an ordinary daily change rate, nearly every block in a new restore point already exists in storage, so going back and pushing each one's lock forw

 Original post: Veeam Plug-in for HPE Morpheus VM Essentials Explained - CloudnRoll Veeam and HPE are further strengthening their partnership, with many new features and integrations expected in 2026.Veeam introduced a new native integration plug-in for HPE Morpheus VM Essentials (VME). It´s currently in beta version, with general availability anticipated shortly. This new plug-in provides hypervisor-based image-level backup for virtual machines (VMs) running on HPE Morpheus VM Essentials, ensuring secure and reliable protection for a wide range of workloads.Next, the architecture of the Veeam Plug-in for HPE Morpheus VM Essentials, the installation steps, and the backup/restore configuration process are presented. Architecture The architecture of the Veeam plug-in for HPE Morpheus VM Essentials (VME), shown in the previous figure, consists of two key componentsThe plug-in module deploys natively on the Veeam Backup & Replication server without requiring a separate virtual applianc

It is hard to imagine modern IT environments without snapshots. They are quick to create, can be automated, and ideally to restore very fast to an earlier state. So it is no surprise that in day-to-day operations you often hear the sentence: “We have a snapshot — so we have a backup.” But is that really true?The short answer is: usually no. The slightly longer answer:A snapshot can be a very valuable recovery point. But only through independence from the production system, defined retention, copies to another medium, protection against manipulation, and reliable recoverability does it become a resilient backup concept. So, what actually is a backup? A backup is a separate, recoverable copy of production data, systems, or applications. Its purpose is to restore a defined state after data loss, corruption, user error, attacks, or infrastructure failures.What matters is not only that data from an earlier point in time exists “somehow”. A backup should primarily fulfill the following chara

Hi Community,Does anyone know the best way to backup the Nutanix Prism Centarl VM? Thank you!

Hi everyone,I have a question about using the proxy appliance as an internet proxy for VMs running inside a Veeam Virtual Lab.I enabled the internet access feature and configured HTTPS traffic on port 443. On a VM within the isolated network, I then configured the isolated-network IP address of the proxy appliance and the corresponding port as a proxy server in the web browser.However, internet access is not working.While troubleshooting, I started wondering how DNS resolution is supposed to work in this scenario. Typically, the VM sends DNS queries to an internal DNS server. If the requested hostname cannot be resolved locally, the DNS server forwards the query to an external DNS forwarder.Since the proxy appliance only proxies the web traffic, how are DNS queries from the isolated environment handled? Does the internal DNS server require a separate route or masquerading rule for external DNS resolution, or is DNS resolution handled by the proxy appliance as part of the proxy connecti

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

Hi everyone,I’d like to share a community project I have been working on: VBR Installer for Aliyun. https://github.com/Coku2015/VBR_Installer_for_Aliyun/The project provides a browser-based wizard for deploying a Veeam Software Appliance into your own Alibaba Cloud account. I created it to explore a more repeatable deployment workflow for Veeam users who operate workloads on Alibaba Cloud.The installer currently supports:VeeamSoftwareAppliance_13.0.2.29_20260617.ovaIt runs on Windows and macOS and requires Python 3.12+, QEMU (qemu-img), Git, and Alibaba Cloud CLI 3.3 or later.I have published a introduction and walkthrough here:https://blog.backupnext.cloud/en/2026/07/Veeam-Installer-for-Aliyun-launch/I would be very interested in feedback from the community.Thanks, and I hope this project is useful.