Community

NetApp ONTAP S3 with Immutability (ONTAP 9.14 and higher) is currently not (or no longer) supported by Veeam. This means that Veeam backups on a NetApp ONTAP S3 bucket with activated Object Lock (Immutability) are currently not considered “immutable” in the sense of Veeam functionality. The main reason is that ONTAP S3 with activated Object Lock no longer fulfills all the requirements that Veeam needs for immutability.  Veeam currently only lists ONTAP S3 as “not immutable” in its own compatibility directory. The use of Immutability is therefore not officially approved NetApp is working on a solution with the support of Veeam (you may be able to get information via the NetApp Partner Manager).  --> This is ONTAP S3 (on ONTAP machines (FAS/AFF), not a NetApp Storage GRID)! Links to

​@Rick Vanover  announced (thanks Rick!) during today’s Weekly Recap the new #EmpowHerVMCE+ Accelerator, and I can’t describe how proud I am. A lot of people worked on this initiative, but special recognition goes to ​@ertelle1, who first had this idea and whose drive, vision, and collaboration made this happen.I took part in leading the 2023 edition of EmpowHer VMCE+, and I saw firsthand how this program was an opportunity to change trajectories. Participants did not just become better technical professionals, they strengthened their confidence and sense of empowerment. They confidently stepped into the room and proved that they belong in this industry, and that they have a place on the front line.And that

I am not able to replace my Veeam Backup and Replication certificate with a new .pfx. When I try to install the .pfx from the Options->Security->Install menu in the B&R Console it returns an error “Certificate’s Private Key is Empty”. I have verified I created the .pfx correctly using OpenSSL and combining the .cer with the .key. I have verified the .key is in fact a private key and not a public key. I have verified the .pfx key permissions have the appropriate read/write for the Veeam service account to access the key. The .pfx certificate is good with a valid private key. Why can’t it be installed on Veeam Backup and Replication. In order for me to upgrade Veeam B&R from version 12 to version 13 I require a certificate with the Basic Constraints extension. I now have a certificate with Basic Constraints as a .pfx but I cannot install

Hi Community.  I am unable to resolve the above referenced issue.  This happened after an update to v13.  After the install, it worked for 2-3 days. I then started to configure my tape infrastructure and when I finished, I was prompted to reboot the server.  Now I can’t get back into the console.  Any help would be greatly appreciated.

Hello,Updating the windows console to 13.0.1.2067 is systematically failing with the error “Failed to update the backup console: Failed to deliver update specification to backup server.”I’am using a VSA - current build 13.0.1.2067Even when downloading directly the 13.0.1.2067 ISO, i get the same issueAnyone had the same problem and could fix it ?RgdsJIhad

Hi,I noticed that I have two running backup jobs since mid May and it appears they are stalled. From the same job I get success emails each day. It appears the backups job were running fine at the scheduled time. Kind of overlap.Maybe the stalled job are leftovers when I upgrade my VBR to 13. I’m not sure. I shutdown the server twice and the stalled jobs reappears. I can right click on it and press stop, but even after hours nothing happens.How can I get rid of the running instances? I enclose two screenshotsThanks,Edy

 Yesterday, I published an article on #CloudCity about my FinOps journey.Check here: FinOps in Practice: Optimizing Cloud Value with AWS, CloudCheckr, and VeeamI'd like to highlight some key initiatives that helped my team strengthen data protection while improving cost control and reducing expenses associated with backup infrastructure assets. Resilience, Backup & High Availability - by CLOUDCHECKRCloudCheckr identifies risks related to data protection and business continuity, ensuring workloads are prepared for failures, accidental deletions, and downtime.Examples of recommendations:• EBS volumes without snapshots (direct data loss risk)• EBS volumes without recent snapshots (

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.

I recently worked on another project with a major customer where we unfortunately reached the limits of Veeam Backup & Replication’s out-of-the-box features for Scale-Out-Repositories and had to find a workaround. Our ChallengeOur challenge: The customer has over 100 scale-out repositories, each with different permissions depending on the application and operating system. We had to migrate the VBR server to a new Windows Server. However, this also meant that the users created locally on the old server were no longer available. In principle, this wasn’t a problem—we simply recreated the same users on the new server.However, this is where the problem comes in. The SOBR permissions include the old user as “OLDSERVERNAME\USERNAME,” which we then have to replace with “NEWSERVERNAME\USERNAME.” If we didn’t replace these, our Enterprise Plugins would no longer have permissions to write their backups.Unfortunately, there is no function

Hello community, I have a new Vanguard Newsletter full of veeamazing content created by Veeam Vanguards last month to share with you! 🤓 The May edition focuses on hands-on Veeam operations and platform maintenance, including troubleshooting and hardening core backup components (such as tape/LTO diagnostics, repository/SOBR administration and infra naming changes from IP to DNS), as well as a strong emphasis on version management and security patching across Veeam Backup & Replication and Veeam ONE, in order to address vulnerabilities and implement updates.  The newsletter also highlights topics related to cloud/object storage and repository architecture (notably Azure Blob integration, S3 repository abstraction and repository decision frameworks), as well as v13-era capabilities such as Veeam High Availability Cluster and environment visualisation via Interactive Maps. It

Some days your job is just plain fun! No ifs or buts!This morning I had the immense pleasure to talk with 3 pillars of the Veeam Community, Senior Community Manager Nikola Pejkova ​@NikolaPejkova , Mr. Community himself Rick Vanover ​@Rick Vanover  and of course Vanguard/Legend/Object First Ace, author of Mastering Veeam Backup & Replication Chris Childerhose ​@Chris.Childerhose  !This is a conversation that could have lasted all morning, never a dull moment.Also courtesy of a fresh of the press Rickatron quote a potentially fantastic new title for a DR horror movie! I can see it now:  coming soon to a theater near you: “Agents gone wild”! Tune in to find out what it is like to write a book and the fun these three folks had collaborating together on this new edition!  

I finally had some time to wire in the Veeam Ports MCP server into GPT. It works but has a number of steps in the process. If you are like me you watch the token burn in Claude for projects like these.  This started with EdxH’s post on the Veeam Ports MCP server introducing the project & GitHub repo.The repo is @ https://github.com/shapedthought/veeam-ports-mcp. I wanted to see what it took to make that same idea work /w GPT.Claude Desktop can launch a local MCP server /w STDIO. The Veeam Ports MCP repo already shows that path well. GPT expects an MCP endpoint instead. On my end that meant I had to put a bridge and a tunnel in the middle before GPT could make use of the tool correctly.Once that was running, I could describe a VBR v13 layout in plain language and get back firewall rules, topology output, and a Magic Ports import file (yea).The painful part was useful as well. I learned that a topology JSON and a Magic Ports import JSON are not t

Throughout this tape series, I explored installation, troubleshooting, tape cleaning procedures, advanced diagnostics, and real-world operational scenarios involving Veeam tape environments.But there is another side of tape infrastructure that usually only receives attention when something starts going wrong: tape library administration.And many times, the problem is not directly related to the backup job itself.Issues often appear around: media movement firmware inconsistencies robotics communication tape-out operations media rotation hardware lifecycle operational mistakes In enterprise environments, tape infrastructure eventually becomes much more than just a backup target.It becomes an operational platform that requires maintenance, organization, validation, and process consistency.

Hi guys, Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process -  The upgrade failed and did not allow us to retry at all. Certain options were greyed out - Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. -   In the end, we were forced to back out of out upgrade.Has anyone seen this before? ShaunB.

TL;DROn May 14, 2026, the PostgreSQL Global Development Group released security updates for all supported branches (18.4, 17.10, 16.14, 15.18, 14.23), fixing 11 CVEs, several rated CVSS 8.8. If you run VBR on Windows with PostgreSQL as your configuration database, you are affected. Veeam does not auto-update PostgreSQL. You have to do it yourself! Here is what you need to know and what to do about it. Why this matters for VBRSince VBR v12, PostgreSQL has been the default (and recommended) configuration database. VBR v13 GA ships with PostgreSQL 17.6, and the latest cumulative update (13.0.1.2067) bumps it to 17.9.1. Both versions are below the patched 17.10 and therefore vulnerable to all 11 CVEs disclosed on May 14 (PostgreSQL release announcement).If you are still on