Blogs and Podcasts

Hi Community!!!During my time as a technical trainer and consultant, I constantly tried to draw analogies between the features we have in IT and the things we experience in our daily lives.Today I will draw an analogy between the wardrobe and SOBR.The idea behind using an analogy is to make technical topics easier to understand. Often, when explaining storage tiering, the listener gets confused, so I made a simple analogy with a wardrobe. This makes storage tiering easier to understand.In this analogy, you will have the opportunity to understand performance, capacity, and archive tiering in a very simple way.Check my blog to see the analogy, hope you enjoy it https://pulia.com.br/what-does-a-sobr-have-in-common-with-a-wardrobe/  

Last week I had to troubleshoot a backup job that was using a brand new proxy and repository server. No other job was using these components. Nonetheless just 4 VMs were processed at the same time. All other VMs showed status “Pending”. As additional information, “Resource not ready: Active snapshots limit reached for datastore” was shown too in active job log.After a short investigation we found out, all VMs were located on just one VMFS datastore. Fortunately there is a rather simple solution for this limitation. You can create a registry key on VBR server to increase the limit of active snapshots per datastore:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\MaxSnapshotsPerDatastore For more details see this forum posts:https://forums.veeam.com/vmware-vsphere-f24/active-snapshots-limit-reached-for-datastore-t19711.htmlNice detail: The change enters into force immediately – even the job is currently running!Keep in mind, this is a global setting!  

Dear community,  Applications are now open for the 2026 Veeam Vanguard class. Any Veeam enthusiast publishing Veeam-related content (e.g. articles, video guides, speaking at Veeam events, podcasts) can apply to become a Veeam Vanguard. There's an article I published on the Veeam Executive Blog (https://www.veeam.com/blog/veeam-vanguard-2026-applications.html) containing a link to the application form at the top of the page, labelled "APPLY NOW", so you can't miss it! After clicking, you will be redirected to the form that every candidate needs to fill out. If you have someone in mind to nominate, it's not enough to just nominate them; even nominees need to answer the questions that are crucial for us when evaluating all applications during Q1. The application process remains open until 9 January 2026, and the new class for the following year will be announced at the beginning of March 2026. Good luck to all applicants, and please share this update with your amazing community so that ev

With Veeam Backup & Replication v13 and its implementation of SAML for authentication, we can use a lot of different IDPs. I already did a guide for entra id which you can find here: https://community.veeam.com/blogs-and-podcasts-57/vbr-v13-saml-implementation-guide-with-entra-id-11560 In my region, entra id is the IDP that is used at most companies. However, it is not recommended to add Veeam to your production active directory domain, so I would also say it is also not really recommended to add your Veeam to your production m365/entra id tenant or generally your main IDP. This guide provides some guidance to set up Veeam with Authentik as an SAML IDP. For those who never heard about Authentik: Authentik is a lightweight, open-source, self-hosted identity provider that offers SSO, MFA, and SAML/OIDC support for your applications. It’s a great fit for environments that want full control and no licensing costs. In contrast, Entra ID is Microsoft’s cloud-based identity platform with

 Ever had your backups fail? I sure have! But it’s all part of the fun & games of learning exactly how these systems work.Recently I spun up another instance of Veeam Backup for Microsoft Azure, and as part of my security mindset, I configured some elements of hardening to my infrastructure. Well, I missed a setting that I’m going to share with you today. Worker Job Completed with Error So, I had Veeam Backup for Microsoft Azure working, my daily snapshot job was also running fine, but it was the daily backup that wasn’t working. Some of the key terms I could pick out from the logs were ‘Worker: <Resource Name> (IP Address:Port): job completed with error’, ‘Error: This request is not authorised to perform this operation’, ‘Status 403’, and ‘ErrorCode AuthorizationFailure’ were the error messages I was being greeted with. Dissecting the Errors The key hint here was the job task ‘Backing up <VM Name> to Backup Repository. Followed by the worker not being authorised.Within

In this post, I analyse the issues involved in backing up a VDI environment in a VMware vSphere environment with TPM enabled. The VMs being backed up are Windows 11 with Microsoft Office 365 licences.The configuration of Veeam for backing up encrypted VMs requires this architectural prerequisites:The backup proxy must be working in the Virtual appliance or Network transport mode: The backup proxy working in the Virtual appliance transport mode must be deployed on an encrypted VM. The backup proxy working in the Network transport mode uses the NBD protocol by default. If you want to use NBDSSL, select the Enable host to proxy traffic encryption in Network mode (NBDSSL) check box in the Transport Mode window. Note that traffic encryption puts more stress on the CPU of an ESXi host and can decrease performance. With this proxy configuration, we can perform consistent backups.For VM restoration, consider the following:If possible, use the "entire VM restore" option to the original locatio

Disclaimer:I actually wanted to publish this post earlier, but I had a small health issue that delayed my plans a bit. In this post, I mainly want to share a few brief thoughts. There are already so many incredibly good and informative blog posts about the recent Veeam 100 Summit in Prague. Therefore, I will focus less on technical details (which cannot be fully shared anyway) and instead provide some impressions from my personal perspective and perception What is the V100 Summit?The Veeam 100 Summit takes place once a year and is now hosted at different locations on a rotating basis. This year, it was held in Prague – a truly beautiful city! Veeam invites all Veeam Vanguards, Veeam Legends, and VeeaMVPs to come together, network, and exchange ideas on the latest topics. In addition, a lot of information is shared that is not public, giving us, as members of this exclusive group, the opportunity to actively contribute to the development of Veeam products. Arrival:Luckily, my hometown o

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 production disks, Veeam mounts the snapshot to a

 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 Issues: Systems, particularly those running Apple’s Bonjour service, frequently use mD

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 inevitable. SQL Server Express previously had a strict 10 GB per-database limit, which often became a bottleneck in environments with larger workloads. This decision to switch to PostgreSQL as the default database engine was made due to the limitation associated with Microsoft SQL Express edition in terms of scaling (eg max 10 GB Database size). PostgreSQL does not have these limitations and it does not require an expensive licence either as discussed in this article.Regardless of the above, Veeam recommends using Micr

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 And I’d like to leave a special thanks to the Wasabi team, who generously provided a trial environment that made all these tests, and ultimately this article, p

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 access to backup, restore, and reports; The backup administrator cannot directly edit in VBR: However, by easily accessing the plugin on the local machine, we can make various edits; this is the restore edit: Reme

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, especially if you’ve already played with block-generation settings in production. 

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 if you don’t want to type in helpcenter.veeam.com all the time inside of google. Well hopefully you guys like it (and use it). I can see there are still some optimisations to be done, but just wanted to start by sharing and see the feedback.

The newest addition published today is the Veeam Recovery Orchestrator Knowledge Guide: https://bp.veeam.com/vro  This has been authored by EMEA Senior Solutions Architect(s) and reviewed in collaboration with our Product Management teams and many internal contributors to ensure it reflects proven, real-world usage. This will better support better designs, stronger security, and smoother implementations when standard help documentation is not enough.The guides are an excellent way to add value in customer conversations and validate designs. Additional resources:Other Best Practice GuidesVeeam Backup & Replication Best Practice Guide: https://bp.veeam.com/vbr​ Veeam Backup for Microsoft 365 Best Practice Guide: https://bp.veeam.com/vb365​ Veeam Security Best Practices: https://bp.veeam.com/security/​ Veeam Cloud & Service Provider Best Practices: https://bp.veeam.com/sp​ Veeam Cookbooks (task-focused “recipe” guides and videos): https://veeamcookbook.com/​ YouTube Videos: VeeamS

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) - https://vinfrastructure.it/2025/11/linux-versions-supported-by-veeam-backup-replication-13-november-2025/Veeam Backup & Replication 13 is now also for Windows - https://vinfrastructure.it/2025/11/veeam-backup-replication-13-is-now-also-for-windows/ Veeam products lifecycle (November 2025) - https://vinfrastructure.it/2025/11/veeam-products-lifecycle-november-2025/ Deprecated and removed features in Veeam Backup & Replication 13 - https://vinfrastructure.it/2025/11/deprecated-and-removed-features-in-veeam-backup-replication-13/ Security and a

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 Check the full article on my Blog https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/

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  Configure storage units (MTrees) on the Data Domain for Veeam backups Confirm network connectivity (Ethernet or Fibre Chann

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 https://bp.veeam.com/vbr/ . If you don’t do a hard refresh, you might encounter issues with the menu not opening c

 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 across your VBR and Cloud Connect infrastructure. These include: 

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 and dual authorization, highlight the performance gains introduced in Gen4+ systems, and look ahead to what’s coming with Gen5. For Veeam users,