Community

In this series we will be going over setting up the full Veeam Data Platform suite ready for configuration of each of the services it offers, but what do you get with the different subscription levels of VDPVeeam have information on the feature comparison here, but here is a rough breakdownFoundationFull hypervisor/agent support Instant recovery Backup for Entra Inline ransomware detection Immutability Syslog event forwarding Security Analyzer for VBR SureBackup Cloud VM supportAdvancedEverything in Foundation Veeam Threat Center And Threat Hunter Integrated AV Veeam ONE reporting and monitoring Veeam Enterprise ManagerPremiumEverything in Adv

In this article I'm going to walk you through deploying a SOBR from scratch in my lab environment — not just the wizard clicks, but the design decisions, the gotchas, and the things I wish I'd known the first time I built one at scale.In recent years, before Veeam introduced direct-to-cloud capabilities, SOBR was used for tiering backups to the cloud. It can still be used today and play into the 3-2-1 backup strategy. Another use case for SOBR is when you have multiple nodes for Object First or Exagrid and want Veeam to view them as a single backup repository. For this article, we’ll focus on Object First.The SOBR is one of Veeam's most powerful (and frankly, most underutilized) architectural features. It lets you pool multiple repositories into a single logical target, adds tiered storage with automatic offload to object storage, and makes managing the lifecycle of your backup data dramatically simpler. What is a Scale-Out Backup Repository?

Introduction Veeam Backup and Replication v13.0.1 supports a direct in-place upgrade from v12.3.1 build 12.3.1.1139 or later on Windows. The installer runs a hard configuration check before the upgrade proceeds and will stop on several specific conditions. This post summarizes the full upgrade process -- blockers, deprecated features, platform changes, component order, wizard walkthrough, and known post-upgrade issues -- based on the official Veeam documentation and confirmed community experience. Full article with expanded tables and PowerShell references at anystackarchitect.com.Supported Upgrade Path Direct in-place upgrade to v13.0.1 requires v12.3.1 build 12.3.1.1139 or later. See KB4763 for the official version requirement. If below that build, update to v12.3.1 first (KB4696), then upgrade to v13. 

 Have you ever wondered where we Veeam 100 members are distributed around the world?Based on Veeam 100 Directory | Veeam Community Resource Hub and the public location information I have from our LinkedIn profiles, I sat down and provided a world map that answers exactly the above question, or shows it on the map. In the backend, I use MapGeo and Google Sheets for this. As soon as you press directly on a member or their point on the map, the photo stored from the Veeam 100 Directory (in the Community Hub) opens.For short information such as names, titles and, if applicable, Blog URL just “hover” over the po

The updated NetApp lab-on-demand with Veeam protecting VMware workloads is live. It is based on the Windows VBR 13 version since the USAPI plugin is still in development TBD. The storage snapshot orchestration is still based on the ZAPI API. It provides a fast and easy way to demonstrate Veeam's goodness with NetApp. Immutability is provided by NetApp StorageGRID bucket with S3 object lock. Demonstrate a SQL backup and restore via app aware processing. What's a lab without a migration activity. This lab also includes an instant VM recovery to Hyper-V. The last section of the lab allows you to scan a backup with SureBackup. Since this is a lab, feel free to play around. To access the lab make sure you have a NetApp Support account with “partner” access link below. Once your NetApp account has been created click on the link for the lab link below. There is also a step by step lab guide that is easy to follow. Please use lab wisely so you do not get caught launching a lab and not using

I am creating failover plans in VBR and want to script changing DNS entries to point to new IPs.  I can’t find any documentation about how these scripts run, any parameters that can be passed to them etc.  All I can see is that they run on the VBR server.  Can anyone point me to something?Thanks

Due to some issues with the PostGre SQL database of Veeam B&R CE, I had to uninstall and reinstall Veeam B&R CE. After sucessful installation, I imported the configuration Backup file. Everything worked fine, I had all my Backup Jobs, my Backup Infrastructure and my Physical Infrastcture restored. I was very happy that everything could be restored so easily. But the next day I had some failed Backup jobs in the History. Two servers (no VMs) couldn´t be backuped because of a strange error message:Warning Failed to connect to XXXXXXXX Details: Cannot find package version for component EpAgent package Msi platform X64. OK, it looks like Veeam B&R had some issues to connect with the Agent on this servers. So I uninstalled the Agent on the Server and tried to install the Agent via B&R once again.But it always failed. Veeam B&R can´t install the agent because it can´t find the “EpAgent package Msi platform X64”. It´s no issue fro

 Most Veeam environments are technically solid. The backup jobs run. The hardened repo is configured. Immutability is on. But when someone asks "can you walk me through exactly what happens if the backup server goes down at 2am on a Saturday," the answer is usually a pause followed by "well, we would figure it out."That gap is what this article is about. A DR runbook is not a Veeam config export. It is an operational document that a trained engineer who has never touched your environment can pick up and execute under pressure. This article covers how to build one, what it needs to contain, how to test it, and how to produce the kind of audit ready documentation that satisfies a compliance reviewer or a customer asking for proof of recoverability. 1. What a DR Runbook Actually IsA runbook is a step b

Dear all, this is just a quick guide, but maybe helpful for some of you!I had this behaviour with the latest release from yesterdays ISO, to patch to the latest release… After mounting the ISO and click on Setup.exe I received the following error:Unable to run the installer because files from this ISO are blocked for security reasons. Use the “Unblock” option in the file properties to proceed.  It’s an easy step, but keep in mind, this you have to do on the ISO file itself, not on the Setup.exe file 😉So right-click on the ISO, and choose Unblock under Security. Hit OK/Apply and have fun, while applying your urgent updates! 

After switching from TSM to Veeam, I found myself wasting plenty of hours excluding OFF-Line sql databases from backup.Normally it demands that you start SQL Server Management Studio ( witch takes a war ), identify the correct instance and then exclude the ofline databases in each backup job…..However… I’m notorisly lazy and in a bright moment, I turned to Powershell.The resulth is a script telling me if a database is offline and therefore maybe should be excluded or if a database in online and can be included in backup, and best of all… without starting SQL Server Management Studio. The script is eacy to use, gives a nice overview, you can in / exclude a database on a server in less than 20 sec ( depends on how many instances / databases the script have to scan ), you can chose to exclude Logs and diff backup and only have FULL backup if needed, and at last, - it logs every change make by time and username.Script is free to use…

Why Updates Matter & Why Order Matters Even MoreEvery software product loves a good update – fresh features, performance boosts, and a healthy dose of bug fixes. But in the world of a Software, updates aren’t just a routine chore; they’re a carefully orchestrated symphony. Many customers forget that the sequence of these updates isn’t random. If you ignore dependencies, you risk breaking the finely tuned harmony of your backup and monitoring infrastructure.So, before you hit „update all,“ remember: the right order keeps your environment running smoothly and avoids compatibility headaches. Here’s the recommended update order for Veeam products:Service Provider Tools (if u

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?

Hello All I am reconfiguring my Backups, and trying to achieve disaster recovery, i want to backup local VMs,Microsoft 365 and Entra ID, for that i am using Veeam Backup and replication V13 (VM) Veeam Microsoft 365 for Email, OneDrive and SharePoint. look to add Entra ID but not sure which Veeam product will be best.for repositories i am thinking one local (immutable backup), Azure Blob (immutable backup) now my question is which product i should use for Entra ID backup, what i should use for local immutable backup, is “Object First” devices good? my backup will be under 8 TB, and what i should use for remote backup Azure or i think Veeam have product cloud vault? what will be best.  

Over the last few days I have been working through the Veeam Recovery Orchestrator Essentials training on Veeam University, which is part of the Veeam Data Platform Security Expert learning track.Are you coming from a background mainly focused on Veeam Backup & Replication and Veeam ONE, and want to learn how the Ochestrator fits into the bigger picture. This course is esentially for you. You will love it 😁. Veem Recovery Ochestrator (VRO) essentially closes the loop: backups are created with VBR, monitored with Veeam ONE, and then recovery itself can be automated and documented through the orchestrator.This self-paced course promises to automate runbooks, recovery plans, and compliance reporting, turning backups into testable DR workflows. Currently at 56 after the exam and now at 64% with the next chapter after powering through the marathon Chapter 4, with the exam score below. 

Hi,Is anyone able to assist here? I’m trying to upgrade to Veeam 13, as part of the overall upgrade I have to upgrade V Orc from my current version 7.1 to 7.2. However, all that I can see in the previous versions is:But the pre-req explicitly says:Upgrade to Orchestrator version 7.2.1 is supported from Orchestrator version 7.2 only; upgrade from Orchestrator versions 7.1, 7, 6, 5 and 4 to version 7.2.1 is not supported:To learn how to manually upgrade from Orchestrator version 7.1 to 7.2, see Veeam Recovery Orchestrator 7.2 User Guide.  However, I’m unable to find the 7.2 version I need to upgrade to 7.2.1. Any help would be appreciated

Hi all,It seems that today is vulnerability day! https://www.veeam.com/kb4830https://www.veeam.com/kb4831Let's start planning the updates!

I would like to know from you, gentlemen, if anyone here happens to use this NIST document. It dates back to 2010, but it seems to me to be an excellent source of information. What references have you been using in your projects?   

Malware detection scanned  a suspicious file from backup but the file is actually legit and so I marked it as clean and Exclude. If I modify the same file for testing purposes, will the malware detection flag it as safe, legit file since I marked it Clean and Exclude? Or it will be detected as suspicious again? Thanks. 

Latest Veeam Backup & Replication v13 introduces the Veeam Deployment Kit, a package used to enable certificate-based authentication.Once installed on a target server, Veeam leverages the certificate for authentication instead of the traditional username and password. You can find the complete procedure in this link:👉 https://nolabnoparty.com/en/using-the-veeam-deployment-kit/

I am preparing to update Veeam for Microsoft 365 from 8.1.2.180 to 8.3.0.2201 and I just want to make sure I am all set in case there are any issue after the update. I don’t believe I have any PostgreSQL or NATS setup that I can recall from when I set this up. I suppose if I do it is all default. It also appears there is no config backup option in this program. We do back up this server, but it does hold both V365 and VBR, so not sure if that complicates things from a restore standpoint if there is a problem with the V365 update.I’m probably overthinking it, but it is the first time I will be updating V365 and just want to make sure my jobs and repositories don’t break or need adjustments after the update.The main reason for this update other than the prompt for an update was that we received a one time email last week saying “License update interrupted: License contract has been terminated” even though subscription and user licenses are active as far as we can tell. P

Per KB4821, each organization should use a single backup application per Microsoft term's of use and product documentation. This script automates the steps mentioned in the KB article by identifying organizations that are using multiple backup applications and, if desired, will limit each organization to a single backup application.https://github.com/VeeamHub/powershell/tree/master/VB365-KB4821Please note that additional backup applications are not deleted from Entra ID. They are simply removed from Veeam.The output of the script let’s you see all organizations affected including backup application info and backup applications removed (if any): 

What this migration actually does Veeam used SQL Server as the only configuration database option for years. In v12 they added PostgreSQL support. In v13, PostgreSQL is the default for all new installations, and it is the only supported option for the Linux Software Appliance. If you have an existing VBR server running on SQL Server and want to move to the Linux Appliance - or simply want to drop the SQL Server dependency - this is the process.It is not a live database conversion. Veeam does it through a backup and restore cycle: you create a configuration backup from your existing instance, then restore it to a PostgreSQL instance using the Migrate mode in the Configuration Restore wizard. The VBR server stays on the same machine. All infrastructure, jobs, credentials, schedules, and settings carry over. The only thing that changes is what database engine VBR connects to. 

SQL Transaction Log Backup fails due to temp staging disk full (Veeam Agent for Windows) EnvironmentProduct: Veeam Agent for Microsoft WindowsWorkload: SQL Server databasesBackup Type: SQL Transaction Log Backup (Application-aware processing)Error ReceivedThe following error appears during the SQL transaction log backup job: Log backup job: Backup Job for SQL Server Transaction Log BackupCollected SQL Server transaction logs do not match any existing database backup.Failed to perform internal backup:Code = 0x80040e14Source = Microsoft OLE DB Driver 19 for SQL ServerDescription = Write on "C:\ProgramData\Veeam\Endpoint\SqlLogBackup\{GUID}.bak"failed: 112 (There is not enough space on the disk.)Database hide_name_db        Status    UnprotectedFailed to perform internal backup (hide_name_db): Code = 0x80040e14 Code meaning = IDispatch error #3092 Source =

Dear Community, As we transition to Veeam 13 I may be getting a bit lost on the usage/purpose of the above Appliance.I have deployed the VSA ver 13 as in-house demo to explore the features and usage. I also deployed the Veeam Hardened Repository 2.0.0.8 and I like how it makes things easier.However the Usage of the Veeam Infrastructure Appliance which can also be used to deploy the Linux VHR has other roles/features that may not be clear on how they plug-in to the entire deployment. I am reading this part https://helpcenter.veeam.com/docs/vbr/userguide/linux_infrastructure_appliance_byb.html?ver=13 and I would like to understand which components that we used to integrate and configure in VBR ver 12 can be compared. Hope its clear. Though I