Community

Back in 2020, long before AI assistants were writing PowerShell for us ;) — — — — ( ;) )I sat down and built a small script to solve a problem I kept running into in the field: setting up a dedicated vCenter server role with exactly the cumulative privileges Veeam Backup & Replication needs. Doing it by hand through the vSphere Client meant clicking through dozens of privileges, and it was far too easy to miss one.Six years and 36 commits later, the script is still alive and kicking and I'm happy to share that it has just been updated to support Veeam Backup & Replication v13.What's new The latest update brings the script fully up to date, thank you ​@haslund !VBR v13 cumulative permissions, based on the official Veeam Help Center recommendations PowerShell 5.1 and 7.x support with module-based PowerCLI loading Compatibility with the new VCF.PowerCLI meta-module as well as the legacy VMware.PowerCLI Hardened error handling and guaranteed vCenter session cleanup Resilient per-pr

How to back up company data on a QNAP NAS? What are my options?

 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

 We changed the IP address of a NAS used as a CIFS/SMB backup repository. The repository was originally configured using a UNC path with a hardcoded IP address and is now showing as Unavailable because the old IP is no longer reachable.Veaam ver 12.3.2Current situation:Repository type: CIFS/SMB Old repository path: \\192.168.0.8\NAS New repository path: \\192.168.0.81\NAS\Backups Repository is not listed under Get-VBRServer; it is only visible via Get-VBRBackupRepository, so KB1905 (managed server rename) does not apply. A new repository was added using the updated NAS path. When attempting to map existing backups to the new repository, Veeam requests moving the backup files from the old repository. This operation cannot proceed because the old repository path is no longer accessible. Creating a new backup chain is currently not an option due to storage constraints.Looking for the supported and safest approach to transition the existing backup chains and jobs to the new NAS repository

7/27/2026 9:50:42 AM Failed : Failed to perform post-processing: Cannot find the backup file < XXXX_XXXXX>This is a copy job, I have rescanned the repo and as well tried initiating full backup for this VM at source, still the error exists with copy job.The copy job is immutable and can find new .vbk file created .Kindly advise.

Around 2019 and 2020, there were many rumors suggesting that the Backup professional's role was nearing its end. I have to admit, that was somewhat concerning. The technology market was undergoing a rapid transformation driven by the expansion of cloud computing, and it seemed that everything would eventually be absorbed by the native services offered by major cloud providers.Despite those predictions, the demand never went away. The future appeared uncertain, but the following years revealed a very different reality. Many organizations migrated their environments to the cloud and later realized that bringing part of their infrastructure back on-premises made sense, whether to reduce costs, improve financial predictability, or gain greater control over their operations.In the past, backup professionals were closely associated with physical servers and traditional data centers. As cloud adoption accelerated, many believed that specialized data protection tools would gradually lose relev

Amazon S3 is so common today that it is easy to forget that, at one point, it was a fairly new idea. AWS launched the S3 service in 2006and essentially made modern cloud object storage mainstream. Not a traditional file system, not a block device, but a simple approach: store data as objects, access them via API, add metadata, and that’s it.That idea has since become a de facto standard.Today we talk about Amazon S3, Azure Blob Storage, Google Cloud Storage, and many other object storage solutions. Technically, these are not all identical systems, but the principle is similar: data is stored as objects, accessed through APIs and HTTPS, and designed for massive scalability.The big difference compared to the traditional on-premises world is this: in the public cloud, the service provider builds the platform for many customers, many workloads, and almost unlimited growth. As data volumes grow, the platform also grows in the background. Hardware, lifecycle management, scaling, redundancy,

We usually explain backup with dry slides — so I wanted to try something different.I built an interactive web experience that follows a single file: invoice_2026.pdf, living on an accounting server. We pull it out of production, carry it through 7 dimensions of the Veeam universe, and bring it back alive from a ransomware disaster.Every dimension is clickable and live:🖼️ Dimension 1 — Snapshot: watch Application-Aware Processing + the VSS steps play out in front of you 🛣️ Dimension 2 — Proxy & Transport: pick between Direct SAN / Hot-Add / NBD, and see block-by-block why CBT reads 1 TB in minutes ⛓️ Dimension 3 — Chain: build the VBK / VIB / VBM chain yourself and run a live forever-forward merge 📦 Dimension 4 — SOBR: drag the slider and watch a backup filter down from Performance → Capacity → Archive ☠️ Dimension 5 — Black Hole: launch a ransomware attack and see Hardened Repository immutability make the difference, live 🔄 Dimension 6 — Restore: try Instant / File-Level / Full

Community,Wasabi has made a MCP (Model Context Protocol) server available to access stand-alone accounts as well as control accounts. Toolsets include: S3, IAM, and WACM (Wasabi Account Control Manager).All of the details are available here - https://wasabi.com/cloud-object-storage/mcp-for-aiNow you can utilize natural language queries to see practically anything you’d want to know about your account settings, utilization, and users. I can imagine easily integrating these tools into a support agent at your favorite MSP… 

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

My answer to the contest :  The Incident Commander Challenge | Veeam Community Resource Hub Every SysAdmin has a toolbox.Some fill it with SSDs, bootable USB sticks, PowerShell scripts, recovery ISOs and enough adapters to connect almost anything to everything.Mine contains most of them too.But after more than two decades of experience in IT, more specifically in designing backup and recovery solutions, I've learned something surprising:The most valuable tool in my Veeam toolbox isn't something I can buy.It's the ability to stay calm.To be honest, being a senior and having experience, helps 🤣😎When a customer calls because production is down, backups are failing, storage has disappeared or ransomware has entered the environment, nobody cares how many certifications you have or how expensive your laptop was.They want one thing!Someone who brings order into chaos.That is what an Incident Commander really does.So what's inside my toolbox?🔹 A recovery-first mindsetI never start with "Wha

Hello,I’m currently testing Veeam v13 using the appliance‑based deployment and love the infrastructure. I have few issues, so not sure if the appliances are limitation to those issues.So far I have the following components installed: VBR (appliance) Hardened Repository  (appliance) Proxy  (appliance) Enterprise manager  (appliance) VeeamOne (windows server - non domain joined)  First issueVeeam ONE is installed on a Windows Server, but I’m unable to add the VBR server to it.The error I receive is: “Veeam Analytics Service on the remote server is not running.” I attempted also a manual installation of the Analytics Service, and I can confirm that the service is running on the VBR sidevia manual installation or via VeeamOne installation.Data collection access is allowed, and all components are within the same L2 segment, so there are no firewall issues.Second issueI am not able to add EM to VeeamOne, it provides me that account does not have premissions. (Tried with veeamadmin wi

  Preface:A while ago I was asked by an enterprise customer from Europe to design a Veeam backup solution for their Microsoft Azure environment. The setup was a classic Hub-and-Spoke architecture, and the goal was clear: leave the on-premises vSphere platform behind and run all workloads in Azure instead. Before any of that would happen, the customer wanted a proper backup design in place — built on Veeam Backup for Microsoft Azure (VBAzure) — so the new cloud workloads would be protected from day one.The migration itself was not part of my engagement. My job was the design and, more relevant for this post, a deployment checklist the team could work through step by step to stand up VBAzure in a private, hub-and-spoke Azure environment. I have done a fair number of on-prem Veeam designs over the years, but a “cloud-first, private-networking-only” VBAzure deployment has a few specifics that are easy to miss if you only know the classic VBR world — private endpoints, DNS zones, worker pla

Hi All, Would it be possible to replace or update the OpenSSL component only on the Veeam Agent for Windows [v13.0.3.1220] due to the Critical bug below, or is it better to wait until Veeam released the latest update ? Recommended Action: Download and install patches as instructedDescription:A heap buffer overflow from converting large OCTET STRINGs to hex on 32 bit OpenSSL may crash or allow code execution; caused by 32 bit multiplication overflow; affects non FIPS OpenSSL 3.x on 32 bit systems.Affected Products:OpenSSLCVE IDs:CVE-2026-31789Vendor Information:https://www.openssl.org/news/vulnerabilities.htmlVendor Patch Download:https://wiki.openssl.org/index.php/Binaries Thank you,

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

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,

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.

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

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