Blogs and Podcasts

Snapshots and VeeamI have been a long time fan of storage snapshots. With the hot topic of immutability, having immutability on the source of the data means that even Veeam and Veeam Service accounts can’t modify the snapshots. If you follow storage and security best practices, you will be in a great spot for your production storage , and have additional immutable storage elsewhere for Veeam backups on a repository.But wait, storage snapshots are not just a feature that can be accessed from the SAN itself. When integrated with Veeam Backup & Replication, they become fast, flexible recovery points directly visible in the Veeam console. Using IBM FlashSystem as an example, here’s how snapshot-based workflows add real value without adding complexity. Backup and Recovery from Storage SnapshotsWith Storage Snapshot integration, Veeam can trigger application-aware storage snapshots and use them as the backup source. Instead of reading from produc

 Nutanix changed how they version their Prism Central product so older versions of VBN plugin might fail to discover clusters. It occurs in versions of PC greater than 7.3. We caught it early, so version 9 should work just fine. Once this issue is addressed, we will update the forums post below.https://forums.veeam.com/nutanix-ahv-f51/prism-central-7-3-t101443.html

The special-purpose .local top-level domain (TLD) is not designed for use in the global Domain Name System (DNS). Rather, multicast DNS (mDNS) uses it to resolve hostnames to IP addresses within small networks, eliminating the need for a dedicated DNS server. Specifically, mDNS operates on the local network link and uses the .local TLD for this purpose. When an mDNS client needs to resolve a hostname that ends with .local, it sends queries to the mDNS IPv4 link-local multicast address 224.0.0.251 or its IPv6 equivalent ff02::fb.Top 5 reasons why it is a bad ideaLet’s dive into why using the .local top-level domain (TLD) can lead to a handful of issues.Standards Compliance: The Internet Engineering Task Force (IETF) reserves the .local TLD for mDNS in RFC 6762. If you use it in another context or within a traditional unicast DNS context, you may face non-compliant behavior and conflicts. Compatibility Issu

IntroductionTo enable monitoring of your Veeam Software Appliance (VSA) with VeeamONE, the Veeam Analytics Service needs to be deployed on the VSA.The Veeam Analytics service not only enables communication with Veeam Backup & Replication servers to collect data but also allows to send remediation commands.Since the VSA is secure by design (hardened Linux-based OS, DISA STIG compliance, automated patching…) and that it enforces Zero Trust principles with role-based access control

Synergy ensures one keyboard, one mouse, multiple computers, no cables, no switches, just seamless control over your network. Cleaner desks, smarter workflows, and true cross-platform productivityFor more information, please take a look at this detailed blogpost “ Why Software KVMs such as Synergy is replacing Hardware KVMs”

Recently, the below Post was created on “Microsoft SQL Server 2025 + Veeam Data Platform = Improved Scalability”​​​.As stated and I quote, ... Microsoft SQL Server 2025 has not yet been validated for the Veeam Data Platform, as it was only made GA on the 18th November 2025, so the information I’m providing here is in preparation for the inevitable support when it’s passed through Veeam’s QA To reiterate, at this time, SQL Server 2025 is not supported yet. This support is inevitabl

Every year, more companies migrate their backup architecture to object storage. The promise is well-known: scalability, predictable cost, and an extra layer of resilience against ransomware. But with so many providers available, one of them has been gaining significant traction — Wasabi Hot Cloud Storage. Wasabi's value proposition is refreshingly simple: S3-compatible storage, high performance, no cold tiers, predictable pricing, and full support for Object Lock, enabling true immutable backups. In this article, I share the full experience of building a protection scenario using Veeam Agent Standalone + Wasabi, walking through:creating a bucket configuring permissions integrating Veeam with Wasabi running the first backup validating immutability restoring a full machine into a hypervisor performing granular file-level recovery

My colleague ​@rfsantos  and I were experiencing some disk space issues using Windows Agents with Protection Groups on two Always On nodes.Due to the heavy load on the disks, even after creating exclusions on low-criticality disks, the full backup was exceeding 20 TB, and the incr about 3 TB. Veeam Agents will always need to back up the images to initiate the child backup (Transaction Log).We deployed the SQL Plugin on both hosts to optimize disk space provisioned by our Pure Storage repository. We separated the jobs between standalone databases and Always On databases.This way, we monitored backup growth separately. Use cases (Not all possible):- When databases are large in our example. The cluster exceeds 15 TB;- You have more DBAs than backup administrators. DBAs have full

If you are using the Veeam plugin for Nutanix AHV. Please do not upgrade to Nutanix AOS 7.5 release. We have encountered some serious compatibility issues in our testing. Once it is validated we will update the forums post below. https://forums.veeam.com/nutanix-ahv-f51/aos-7-5-t101416.html This has been fixed with a patch for PC 7.5.0.1. Please see release notes below. It identifies the fix on page 12😀. Thanks,Pete

Want to know to optimize cloud storage costs while maintaining immutability for your backups? In the december edition of my Regkey of the month series, I dive deeper in Block Generation I explain what it actually does, why it matters, and how a simple registry tweak can dramatically impact storage I/O and costs (sometimes for better — sometimes for worse).If you work with object-storage backups (AWS S3, IBM Cloud, on-prem S3-compatible systems…), this one’s a must-read before messing around with default settings.Check out the full post here on my blog: Advanced Object Storage I/O Optimization: Fine-Tuning Veeam Block GenerationLet me know if you like it, es

Hi Everyone, I have started a new podcast! To get things rolling I asked former Veeam Legend/Vanguard, current Veeam MVP and all around data protection superstar Michael Paul to come and teach me Entra ID and how to back it up properly with Veeam! https://www.buzzsprout.com/2545760/episodes/18306636 

A couple of days ago I started to implement an idea that I had for a long time. Wouldn’t it be cool to have an awesome-like list that has a bunch of links but with a built in search functionality. That way, you can add a lot of links and still keep it useful. The result of this experiment can be found here:https://tdewin.github.io/veeamdex/All processing is done in the browser (that is why it can be hosted on github). Even this community is linked. But what I personally like the most is that you can do “deep queries”. It doesn’t do anything but it prepares the links that support it for instant search. For example, deepq q=object storage, prepares google links that can search in the selected sites. This is handy i

With my colleague ​@zzsoka  we have developed a procedure the inject needed variables for initial configuration of the Veeam appliances and now we would like to share it with you. When you deploy Linux appliances at scale, cloud‑init is usually the go‑to mechanism for injecting instance‑specific configuration (IP, hostname, NTP, credentials, etc.) at boot time. However, the Veeam Software Appliance used here does not ship with cloud‑init currently, so we need another way to achieve the same result: build one customized ISO and then let vSphere guest variables drive per‑VM configuration.This post walks through how I achieved that using:- a customized Kickstart file,- a customized GRUB configuration,- VMware guestinfo / OVF properties as the source of truth for variables,

Happy Friday, Veeam community! I am here with another packed Veeam Vanguard Newsletter including all content published by Vanguards during the last month. It´s a looong list full of great content, so make yourself comfortable and enjoy reading! 😎 ​@AndrePulia - My Veeam 100 Summit Experience - https://pulia.com.br/my-veeam-100-summit-experience/@AndreTheGiant - Linux versions supported by Veeam Backup & Replication 13 (November 2025) -

With the High Availability feature in Veeam Software Appliance 13.0.1, Veeam provides a neat way to make the backup server highly available. In this blog post I’ll briefly show how to configure HA, which prerequisites must be met, and what alternatives exist if HA cannot be used. Intro - The Basics The feature itself reduces downtime of the backup server in the Veeam Software Appliance. In general, two nodes are required; they can synchronize even across relatively high latencies. A manual switchover is possible, and a major advantage is automatic updates for both nodes. The goal is to offer fast disaster recovery without the need to keep a dedicated standby backup server, and then finally to restore the configuration backup. 

Hi Community, good day! In my article, you will find information about some conditions that may prevent upgrading from version 12.3 to version 13, such as:Unsupported OS for the VBR server; Unsupported SQL Server version; Unsupported .NET version; Old components still registered (Cloud Connect, Enterprise Manager, Console, Agent, Plug-ins); Legacy license type, and more.Here a small table that can be used as a reference to organize the upgrade process in the best possible way; keep in mind that this is just a small example based on a very simplistic scenario.  Build a table like below:ScenarioVBR 12.3 on Windows Server 2016 SQL Server 2016 VMware ESXi 7.0 U1 Windows Server 2016 ReFS repository 

This is my first blog, I’m a Team Lead and Sr. Solutions Architect for the Data Protection Practice at a Veeam partner. I work in their Solutions Lab where I provide pre-sales support and product demos for several data protection products including Veeam and Data Domain. I’ve created several Veeam demos with different use cases.  Steps to Integrate Data Domain 6410 with Veeam Data Platform v13 The PowerProtect Data Domain is a purpose-built backup appliance from Dell for cyber resilience in on-premises and multicloud environments. It combines high-performance, efficient, and secure data services with the Data Domain Platform to provide fast recovery and robust protection against threats Please follow the steps below to integrate the PowerProtect Data Domain 6410 with VBR. Prepare the Data Domain 6410Ensure the DD Boost license is enabled on the Data Domain system

Recently my colleague Claudio Fortuna published a new Best practices guide for Veeam Recovery Orchestrator, here  https://bp.veeam.com/vro/ Although considered a team effort, I can say Claudio is the main driver and author so thanks for his effort. It breaks a bit with the traditional best practices as it is more a knowledge base then a complete best practices. At the same time it does include a lot of interesting things like Clean room best practices which Claudio pioneered in the first place.But next to this release, the solutions architect teams has also updated the theme of the best practices in general. This has been a major overall so hopefully you like it. It does feature a dark mode. For the light mode, we have opted for a blue contrast color to enhance accessibility. Because of this complete overall, you might have to do hard refresh on the best practices like the 

 Veeam Backup and Replication v13 is now in the wild, and for service providers running Cloud Connect this is not just another point upgrade. It is a major platform refresh that touches the core backup server, gateways, explorers, agents, and the tenant facing control plane. With v13 bringing stronger security defaults, modernized components, and several legacy features finally retired, VCSP partners should plan their upgrades early so tenant adoption is smooth from day one.I recently upgraded my Cloud Connect environment from 12.3 to v13. In this post I will walk through the upgrade flow exactly as the wizard presents it, with short practical notes at each stage. The focus is simple. What to verify, why Veeam is asking for it, and how to avoid tenant impact while moving your Cloud Connect stack cleanly onto v13. Preparing for the upgradeBefore starting the upgrade, there are a few best practice steps you should complete a

Protecting modern workloads requires efficiency, security, and rapid recovery. HPE StoreOnce plays an important role in the Veeam ecosystem as a purpose-built backup appliance that delivers high performance, global deduplication, and immutability for enterprise environments. While HPE Storage Servers have long been popular with Veeam architects, StoreOnce remains a strong option for customers who want a scalable appliance with aggressive data reduction for a Veeam repository. This blog takes a practical look at how StoreOnce fits into a Veeam-powered data protection strategy. We’ll explore how it supports the 3-2-1-1-0 best-practice model, how Catalyst integration and source-side deduplication reduce infrastructure load, and how Catalyst Copy and Cloud Bank Storage extend protection off-site and into the cloud. We’ll also examine immutability

I have been working on a case with Veeam Support to do with HA Clustering and not being able to enable it due to this warning -HA Cluster warning about local repositoryIt turns out somehow I tried to enable HA and then in one of my SOBRs added a capacity tier which was the cause of this.  The recommended solution -Remove the Capacity Tier (Wasabi in my case) from any SOBRs - I only had one in this case with a Capacity/Archive Tier. Enable HA Clustering which now works Add the Capacity Tier back to the SOBRs as neededWhile not the most ideal solution it works.  I asked them to check KBs or Help pages to see if this is mentioned and if not get this added as a note or something so users are aware.  Lots of testing so it was good to find this one and get a solution.

Last month I was blessed to have been able to attend my 6th Veeam100 Summit. Since I started 1st attending in 2018 (2020 was a no-go, and 2021 was a hybrid event), the venue has been held in Prague, CZ, with the exception of last year where it was held in Berlin. Though I enjoyed Berlin last year since I'd never been, I was really looking forward to getting back to Prague. It's such a beautiful city and there is certainly no shortage of places to see & go. But of course, the main excitement for me was to be able to meet up with fellow Veeam100 Community members and be given the opportunity to chat with various Veeam Product Managers.Like most years I've attended the Summit, I arrived in PRG on Sunday. Sadly, the weather wasn't too great (rainy), but no matter. First day arrivals are typically reserved for getting my bearings straight so to speak  getting to my room, cleaning up, and meeting up with other Community attendees for a late lunch/early dinner and catch up

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.

So it's been a few weeks after my return from yet another excellent Veeam100 Summit in Prague. This marks my 3rd visit to Prague, and I'm not getting tired of the city at all. On the contrary, I keep discovering new things to do and visit new places. This was no different this year.First of all I must thank Rick Vanover, Madalina Cristil, Nikola Pejková, Safiya Mohamed, and everyone at Veeam for creating such a unique event. Nowhere else in the Industry do you have such access to Product Management and can ask questions and provide feedback. I have seen Veeam grow from somewhat of an underdog over 10 years ago to the market leader it is today, and this is still true today.This summit was definitely focused on the release of version 13 (I think the biggest release yet, the amount of features is mindboggling) and Veeam's acquisition of

Hi everyone,Earlier this year, I was honored to achieve the Veeam Legend status. I knew this was a great recognition, but I didn't realize it would open the door to such an incredible experience: The V100 Summit in Prague.Walking into the venue, I wondered: What will it be like to meet the people I’ve only known as avatars in the forums? It felt like meeting old friends instantly. The barrier between "experts" and "newcomers" just didn't exist.I am especially grateful that I was able to share this experience with my friends ​@lukas.k  and ​@Dynamic. They were the ones who encouraged me to try and get into the V100 program in the first place. Being there together with them made the whole trip even more special.My Absolute Highlight: The AMA Session While the deep dives were great, there was one specific moment that stood out above everything else: The AMA (As