Community

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 it

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 from the server I want to backup, because a di

Building a Veeam DR Runbook You Can Actually Use During an Incident Most Veeam environments are fine right up until someone asks the question that matters:“If the backup server is gone at 2 AM, what exactly do we do next?”That is where a lot of teams realize they have working jobs, hardened repositories, immutability, maybe even SureBackup, but not a real disaster recovery procedure. They have platform settings. They do not have a document another engineer can pick up and run under pressure.That is what a DR runbook is for.A runbook is not architecture documentation, and it is not a generic best-practices guide. It is an operational procedure for a specific failure. It should tell the person holding it what to do, in what order, how to verify each step, when to escalate, and what success looks like before they move on.If it cannot do that, it is not finished. What a runbook actually covers A Veeam runbook should be built around real failure scenarios, not around product features.At min

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…regards   MACH0NE 

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 used):Veeam Service Provider Console (VSPC) Update first! The console must always be on the latest version to properly manage older or upgraded tenants and Cloud Connect infrastructure. (Includes its Web UI, Server, and Collectors.) Veeam Cloud Connect (VBR for SP) Update your Cloud Connect server next. This keeps

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. The self-paced training of what I have learnt so far includes but not limited to these; Deploying and

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 as the Veeam downloads are clearly not fit for purpose. Many thanks,LGH.

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. Possibly a glitch

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):  

Migrating VBR from SQL Server to PostgreSQL on Windows This migration is not a live database conversion.Veeam handles it through a configuration backup and restore cycle. You back up the existing VBR configuration, then restore it in Migrate mode to a PostgreSQL instance. The server stays in place. Jobs, infrastructure, schedules, credentials, and settings come across. The change is under the hood: VBR stops using SQL Server and starts using PostgreSQL instead.That matters now for two reasons. PostgreSQL became the default database for new VBR installs, and it is the only supported database option for the Linux Software Appliance. If the end goal is the appliance, or if the only reason SQL Server still exists in the environment is to satisfy VBR, this is the path that gets you off that dependency. When you need to do it, and when you can wait There is one case where this is not optional: moving to the Linux Software Appliance. That platform is PostgreSQL-only, so a Windows VBR server s

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 = Microsoft OLE DB Driver 19 for SQL Server Description = Write on "C:\ProgramData\Veeam\Endpoint\SqlLogBackup\{18aa4e5f-9ef9-45f8-ad9a-

(running Veeam 13, Community/Free edition on Win 11).I did a bunch of migrations and updates a month ago. Before doing so I set aside the existing Veeam backups, so I have them. When I try to import a backup for one server from it (just to browse and retrieve a couple files) it tells me "Path contains invalid symbols...",. But it doesn’t. I have a path with no special characters or trailing spaces or anything like that. The message isn’t any more specific.I’ve tried mounting the file share where it exists as a mapped drive and a network location. I would copy it into the local machine to try that, but there isn’t room.Also, the import dialog says “Specify a backup to import. You can import backups from a backup repository or any managed server.” but the dropdown menu only lists the local machine and my two hyper-V hosts, not the repository (which is on a network share).Thanks.

As a fan of the Veeam Data Integration API, I have been spending time with a related but separate topic: Database Publish (referred to as Data Publishing in the Veeam documentation). The goal was to make backed-up databases available to another system for analysis, without permanently restoring them or affecting production.What is Data Publishing?Data Publishing is a feature in Veeam Backup & Replication that has been available for Microsoft SQL and Oracle for a while and was later extended to PostgreSQL and MongoDB. The mechanics are straightforward: Veeam mounts the backup data read-only, attaches the database files to the target engine, and keeps a write cache for any changes made during the session. When the session ends, the write cache is discarded. The source backup is untouched. The result is a database accessible via standard database protocols. You can connect to it, run queries, inspect schema and data, and then walk away and grab a coffee. No permanent restore, no impac

Port conflicts in your Veeam environment? There’s a registry key for that.In this month’s Regkey of the Month, we look at how you can customize the network ports used by Veeam Backup & Replication through registry settings.Why would you do this?✔ Avoid port conflicts with other applications✔ Align with strict firewall or security policies✔ Gain more control over agent deployments and infrastructure communicationUnderstanding these lesser-known registry options can save hours of troubleshooting in complex environments.If you manage or architect Veeam environments, this one is worth a read.https://integriservices.blogspot.com/2026/03/regkey-of-month-march.html

Microsoft 365 (M365) has become indispensable in everyday office life: emails, documents, Teams chats, SharePoint – everything in one place, all in the cloud. But many admins rely too much on the idea that “everything is somehow secure.” That’s a mistake!  Why should you back up Microsoft 365 services at all?The well-known Shared Responsibility Model states: Microsoft provides the infrastructure, but you are responsible for backing up and restoring your own data.In short: Microsoft protects against infrastructure, network, and hardware failures and takes care of maintaining the Microsoft architecture and software. However, Microsoft is not responsible for accidental deletions, ransomware, viruses, malicious colleagues with a “delete finger,” or improper data handling!What about the good old Recycle Bin feature – isn’t that enough protection?Many people rely on the idea that deleted files simply end up in the recycle bin and can be restored at any time. That sounds reassuring at first—b

We use AWS VTL for backing up some of our larger SMB file shares (mainly AWS FSx for Windows) that run into a few terabytes each.When running a tape backup job we’d run a powershell script to check there were at least 10 free tapes before starting each job (there’s around four or five chained jobs).The script worked fine on VBR v12, but always returns “TooManyRequests” on v13.I have found various “retry” scripts, but the VBR commands ALWAYS return “TooManyRequests” so never complete.Is there now an alternative method to auto load blank tapes that didn’t exist in v12?Our script that worked in v12:# Get Library$NOVA_Tape_Library = Get-VBRTapeLibrary -Name "Novasol Gateway-VTL V3"# Get Number of Free Tapes$NOVA_Free_Tapes = (Get-VBRTapeMediaPool -Name "Free").medium | where {$_.LibraryId -eq $NOVA_Tape_Library.Id}# if number of free tapes < 10 import tapes and format for use?if ($NOVA_Free_Tapes.length -lt 10) { write-host "Import Tapes" Import-VBRTapeMedium -Library $NOVA_Tape_L

Hi teamA hardened repo using the VEEAM Hardened ISO experienced a power cycle and upon reboot its out of band interface lit up like a x-mas tree.Upon further investigation it appeared that the virtual disk was just gone. A message indicated that RAID6 detected foreign configuration.Been working with vendor and they have asked to install storcli on to the server.Would this be possible, being a hardened repo? They have a non-recommended method alternative too.Can’t believe that a power cycle did this and not sure what the root cause is but would be good if we could get it back. Otherwise will have to rebuild and sync primary backups againcheers

Hello,i would like to ask, if somebody is not experiencing that issue, that big environments have issue with SSL connection? we have all in one boxes - VBR, VEM and postgresql is on the same machine at the end of postgresql.conf #------------------------------------------------------------------------------# CUSTOMIZED OPTIONS#------------------------------------------------------------------------------# Add settings for extensions heressl = onssl_cert_file = 'backup_server.crt'ssl_key_file = 'backup_server.key'ssl_ca_file = 'backup_root.crt' in svc_veeambackup.log we see[02.03.2026 11:40:10.307]    <35>   Error (3)    0: Breaking connector[02.03.2026 11:40:10.307]    <35> Warning (3)    Failed to obtain connection: [Failed to connect to [::1]:5432]. Attempt 1 of 20. in pg_hba.conf is preferred connextion via ssl# IPv4 local connections:hostssl    all             all             127.0.0.1/32            scram-sha-256host    all             all             127.0.0.1/32      

System Center Virtual Machine Manager (VMM) centralizes and simplifies datacenter management by providing a single platform to configure, monitor, and control virtualization hosts, networking, storage, and deployment resources. Thereby, enabling administrators to efficiently provision and manage virtual machines and services across private clouds. Before integrating SCVMM with VRO, you must install the VMM Console on the VRO server. Else, the integration will fail. Note that, this article is a continuation of the following:Note: A Hyper-V cluster can be added to the Veeam infrastructure and is ready to serve as a source and target for backups, replication, and other operations. Note that adding SCVMM servers to Veeam Backup & Replication is not required. You can read more about SCVMM support by Veeam from here. Adding Microsoft Hyper-V or Cluster to VROBut to allow Orchestrator to connect to an SCVMM server, you must first install the SCVMM console on the machine that runs Orchestr