Blogs and Podcasts

 Veeam Software Appliance ConfigurationWhen the VM or physical server has booted, you’ll need to be able to get to the console From there, press Tab till you land on Accept and hit Enter to accept the EULAEnter a hostname and press Enter on NextOn the adapters screen you likely have just the one, VBR should be a VM, press Enter on StaticIf you are deploying this on a physical server and want network redundancy look at the configuration of the backup repository in section 2.9.3, its the same hereEnter the IPv4 address, subnet mask, then add DNS, comma separated and press Enter on ApplyHere when selecting the adapter, you should see the assigned IP address belowYou can also run a ping test to verify the IP address is reachableWhen you are happy thats reachable, press Enter on NextIf you want to change the NTP server press Enter on EditEnter the NTP server and press EnterYou can optionally add more with the Add button, or press Enter on Next when you are doneWe then need to set password r

Veeam Software Appliance Deployment - ISOFor deployments on physical hardware or other hypervisors we will need the ISOTo get this head here and click Download on the Veeam Software Appliance 13 section, you will need a valid Veeam login for thisThen select the Bootable ISO and click DownloadThe VM will need to be specced with whats listed in the overview, the VM compatibility is Rocky Linux and the ISO will need to be mounted to the server, if this is a physical server ensure you burn it with Rufus in DD mode else it will fail to installWhen you boot the server, you will see this screen, press Enter on Veeam Backup & ReplicationThen press Enter on InstallClick Yes hereAnd the system will automatically install everything Veeam Software Appliance Deployment - OVAFor deployments in a VMware environment we can install this directly with an OVA template downloaded from Veeam’s websiteTo get this head here and click Download on the Veeam Software Appliance 13 section, you will need a va

Hello my dear Veeam community !Just wanted to share a new article I posted on my blog: “how to recover SharePoint quickly and keep downtime a minimum” using Veeam Data Cloud.The idea is to dig into clever recovery strategies for large-scale SharePoint sites, break down Veeam Data Cloud MBS vs Graph-based backups, and show how using both can help you hit your RTO targets and stay compliant.Here it is : https://home.point4.fr/microsoft-365-rapid-tb-sharepoint-recovery-minimal-downtime-strategies-2/I hope you’ll like ! 🙂

Veeam Data Platform 13 is finally here and fully releasedTo kick things of in my new series of VDP 13 articles, we have the ultimate upgrade guide covering all the major components you will have in your environmentThis guide will cover the upgrade only, keeping VBR/VEM on Windows, I will cover migrating to Linux in a separate article when the process is available to everyoneThe minimum requirements for each component for upgrade isVeeam ONE 12.0.0 VEM 12.3.1 VBR 12.3.1 VRO 7.2.1 Veeam Console 12.3.1Here are some snippets from my article, linked at the bottomVeeam ONE VRO VEM VBR Veeam Hardened Repository Veeam Remote ConsolesI hope this helps anyone looking to upgrade to the latest version and take advantage of all the new featureshttps://blog.leaha.co.uk/2025/11/22/veeam-data-platform-13-ultimate-upgrade-guide/

I had the pleasure to sit down with ​@Geoff Burke to do a Podcast where we talk all things backup and also about my books.  Check it out below.From Help Desk To Architect: Building A Career In Backup, Community, And Resilience

Happy Thursday Community! Thought I'd share another Linux process today – how to resize a Linux volume used as a Veeam Repository in Linux OS, specifically increasing its size. This also is in reference to using an array as your Volume-backed storage. Logical Volume Manager (LVM) processes won't be discussed. Additionally, though there is a process to decrease Volume sizes as well, I also won't be discussing that process either. When wanting to decrease Volume size, I highly recommend creating a new Volume of the desired size, then copy your data to it to prevent potential data corruption.As most of you probably know, increasing Volume sizes within Windows is pretty straight forward → increase LUN storage on your array, then rescan your disks in Windows Disk Manager, then Extend the Volume. It takes a minimal amount of time to perform. Within Linux, there are a few more tasks needing to be performed than in Windows to get your Volume size increased. I'll share exactly what those steps

I’m really happy to share with the Veeam Community another Open Source Project “vScan Vulnerability Scanner” vScan DashboardThis is an Open-Source project created as a Security scanning tool that integrates with Veeam Backup & Replication to perform vulnerability assessments on backup data without needing a full restore. It leverages Veeam Data Integration API to mount backup content directly to Linux servers and scan them using open-source security tools Trivy and Grype.Why is this solution created? In the event of a disaster or security incident, when the Veeam Admin or the Security Team needs to recover a server (whether it's the latest or a previous copy), they need to know what vulnerabilities exist in that Veeam Backup.While Veeam can detect malware, ransomware, IoC, etc, it doesn't detect vulnerabilities. For example, Consider these scenarios: What if a Veeam Admin restores a backup that contains a vulnerable version of OpenSSL? What if they restore an image with vulnerabili

There could potentially be bug in the RTM v13 release for those that have access to it and are MSPs.  After upgrading a test box in my environment, the API/Web Services are not starting for me.I updated from 12.3.2 version and now have a case open.  I know ​@Cragdoo tested in his homelab too and found the same problem.  So wanted to make everyone aware unless you are doing a new install in which case I heard from someone else that it works fine.  I am going to test a new install myself and see if it is just the upgrade which has the problem.I will post an update to this thread once I get more details from Support and possible fixes, etc.

Happy New Year, everyone! Wishing you a successful and resilient 2026!Kicking off the year strong, we continue our “Regkey of the Month” series with a deep dive into a powerful but often overlooked configuration in Veeam Backup & Replication.This month’s focus: optimizing SQL transaction log backups using the SqlTempLogPath registry key.Many environments run into performance bottlenecks or storage issues during SQL log backups simply because Veeam uses a default staging location that isn’t always ideal — especially on servers with small system drives or slower disks. This can lead to:✔ Disk space exhaustion✔ Slower backup performance✔ Backup jobs impacting production workloadsIn the blogpost, I walk you through:What SqlTempLogPath actually does Why the default behavior might be hurting your backups Real-world deployment tips Best practices for choosing the right path Supported environments and gotchas to avoid Read the full Regkey breakdown here

Considering hypervisor choice was a big topic for 2025, I wanted to spend a bit of time right before year end trying the new Windows Admin Center for myself. My main focus was host on-boarding and role based access.With the Windows Admin Center Virtualization Mode preview the idea is to provide a better centralized hypervisor management experience for organizations. Looking to migrate, perhaps from other hypervisor platforms, where, perhaps, this type of tooling has historically been more mature.InstallationFor testing I used Windows Server 2025 (en-us), (2 CPU, 8GB RAM, 100GB disk). This was a completely clean install, the machine was domain joined to the same domain as the Hyper-V nodes I was accessing, but this shouldn’t matter.I installed in order:VC++ Redistributable https://aka.ms/vc14/vc_redist.x64.exe WAC vMode Preview https://aka.ms/WACDownloadvModeI used the custom setup option:Network access: Remote access. Use machine name or FQDN to access Windows Admin Center on other dev

If you’ve been following this series of articles, you know by now that Veeam’s support for syslog allows you to leverage Microsoft Sentinel and many other solutions that support syslog to monitor your Veeam environment for operational and security events. Getting the data in is the easy part. The hard part is how to filter and query your Veeam event data for important information that you can quickly and effectively act on.The previous entry in this series walked through a simple example of the hard part, demonstrating how to set up an analytics rule in Microsoft Sentinel to scan Veeam events for a specific configuration change (four-eyes authorization disabled, event ID 42401) that could signal a compromised server. It’s easy enough, but that’s only one rule. Veeam emits hundreds of events, so the task of building your own rule sets that are all properly categorized and prioritized can be daunting given the breadth and scope of events that Veeam produces. Even if you build a rule set

 I am sharing the procedure for performing an in-place upgrade of the VBR 12 infrastructure to version 13, including an analysis of the potential warnings identified during the configuration check.Here you will find links to the official documentation for further information.Check this Veeam docUpgrading to Veeam Backup & Replication 13 on Windows - Veeam Backup & Replication User GuideCheck PrerequisiteUpgrade Checklist - Veeam Backup & Replication User Guide Download last ISODiscover the Latest Version of Veeam SolutionsMount ISO and launch setupFirst step is upgrade EMSecond step upgrade VBR serverLet us analyse the following warnings returned by the configuration check“The following feature are no longer available in the product” The following features are no longer available in the productRestore point–based retention Existing jobs continue to work. Fix: for new jobs use Retention by days or GFS. Reversed incremental Existing jobs remain operational. Fix: migrate to

As described in the title, I would like to explain in this blog post why a Veeam Hardened Repo and Object First is a great combination.A Veeam Hardened Repository and an Object First appliance each offer specific advantages for backups and restores, security, etc., but they also have their weaknesses. From a technical and cyber security perspective, combining both approaches offers a significantly stronger, more resilient backup architecture than either concept alone.I work on a lot of Veeam projects for SMEs, SMBs, and enterprise customers. I see the combination of the two products as being more suitable for the SMEs and SMBs sectors. In the enterprise sector, due to the larger amounts of data and faster restores, other products are used, but I don’t want to go into those here, as this post is about Hardened Repositories and Object First.  Why different/multiple technologies?The first point I would mention here is media or storage technology break.A media or technology break in backup

 PREAMBLE: In this period I'm trying to write my articles using the STAR model (Situation, Task, Action, Result) to make sure they're technically accurate and clear.I'll never get tired to say this: protecting company data is the most important thing for any business, and we need to go beyond traditional virtual machines or transactional databases to include unstructured data on NAS infrastructures.1. SituationOur customer wants a strong and permanent backup system for a lot of unstructured data:Data Source: NetApp ONTAP (version 9.14.1P5). Data involved: There's about 11 TB spread across 25 NFS shares. Critical info: We've got Oracle database dumps (done with RMAN) and PostgreSQL (via script). Final destination: The backup had to be efficient, and the backup copy had to be replicated to Azure Blob Storage (not immediatly but the solution had to be natively prepared).2. TaskTo do this, our job was to come up with a high-performance backup solution using Veeam Backup & Replication v

Hi! As HPE and Veeam deepen their strategic partnership, I´m back in the Veeam Community and wrote about the integration of Veeam with the HPE Alletra MP B10000 using HPE GreenLake.HPE Alletra MP is a cloud-native, modular, disaggregated storage platform that delivers multi-protocol support and enables high-performance NVMe hardware with software-defined capabilities.On the other hand, GreenLake is HPE's cloud platform with advanced AIOps capabilities in monitoring, automating, and managing IT infrastructure, cloud resources, workloads, and applications across hybrid and multi-cloud environments.The post is long, and it was not possible to upload all the content to a single topic. Therefore, I am sharing the link:https://cloudnroll.com/2025/12/28/integrating-veeam-with-hpe-alletra-mp-b10000-and-greenlake/ 

So I’ve spent plenty of time living in vCenter, managing VMware clusters like most of us have. But as I started digging into KVM-based hypervisors, it honestly felt a little backwards at first…different tools, different terms. Once you step through it though, a lot of the same core concepts are there. I put this together to help connect the dots if you’re used to VMware and starting to take a look at KVM.While KVM itself is a standardized kernel module, not all KVM-based hypervisors are created equal. Vendors and open-source communities may customize their KVM implementations with unique management layers, storage integrations, and performance tuning. For VMware administrators exploring alternatives, this blog focuses on the foundational KVM components that most directly compare to the vSphere stack. The goal is to simplify that comparison and help you build a clear mental map between platforms.As virtualization strategies evolve and organizations explore alternatives beyond VMware, it

Hi All, In early December, I set myself the challenge of writing a blog post every day and putting together an Advent-style calendar covering topics ranging from security and automation to a few features I genuinely enjoy.It was an ambitious goal, but I’m happy to say I completed it. I’ve been sharing each post on LinkedIn daily, but I wanted to post the full collection here as well for anyone who isn’t connected with me there.If you’d like to read along, please feel free to share. I hope you enjoy it. Advent Calendar Day 24: Thank You and Looking Ahead | Homelabpro Blog

I'm creating some labs on AWS and today I'll share the Veeam part with you. Lab Details:VBR:Instance size: c5.2xlarge  Availability Zone: us-east-1f  Architecture: AMD64  Total memory: 16384 MB  Network: Up to 10 GigabitJobs created:EC2 EFS FSx VPC First, why not use Marketplace?As many already know, taxes in Brazil are massive.Because of this, I usually don't use Marketplace, since the taxes are even higher through Marketplaces. (Until 40%)So I prefer to deploy Veeam traditionally on EC2.Here are some steps:Upload the Veeam .ISO on an S3 Create an EC2 (will be our EC2) Use TNTdrive to mount the S3 for EC2 Install V13  Using CLI AWS to upload de .ISO: "C:\Users\user\lab\VeeamBackup&Replication_13.0.1.180_20251130.iso" s3://vbr001/vbr/ --cli-connect-timeout 6000Don’t forguet to use (--cli-connect-timeout 6000)Otherwise our upload will be fail, because the .ISO are more than 16 GB. How to connect EC2 with S3 (using TNTdrive )After EC2 and S3 are created.Download the TNT drive or anot

Hey guys,I hope you are fine and ready for the end‑of‑year holidays.I wanted to share an issue I encountered this morning while integrating VDC Vault on a VBR server running on 2012R2. Yes, I know, the OS is no longer supported — a redesign project is planned soon. To quickly improve backup security, we set up a Vault. Unfortunately, during the integration I received the following message: I didn’t see any specific prerequisites in the Veeam documentation regarding the operating system for integrating VDC Vault.After going through several pages, I found this in the Help Center: Make sure you have WebView2 Runtime installed on your backup server.Once it was installed, we were able to complete the configuration and create our backup copy job.Cheers !

Hi Community,If you are going to take the Veeam Backup & Replication v13.0.1 ILT course, then it's important that you take the recommended free courses.Check my blog for ways to access the recommended free courses.https://pulia.com.br/veeam-backup-replication-v13-0-1-course-experience-recommendations/Hope that help your learning!

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