Community

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

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

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

(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

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 respo

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

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 connec

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.

My recent blog post was about installing the plug-in on a Windows server; this blog will go through the installation on a Veeam v13 software appliance.I recently deployed the Veeam Plug-in for HPE Morpheus VM Essentials version 13 (RTM) on my lab Veeam software appliance, which is running v13.0.1. Once tested, I'll have it available to demonstrate to my customers.Veeam has introduced a dedicated plug‑in that enables image‑level backup and restore for virtual machines running on HPE VM Essentials. This integration brings VM Essentials into the same unified protection workflow as VMware, Hyper‑V, and other supported hypervisors. The plug‑in is not bundled with the main Veeam Backup & Replication installer, so it must be added separately. What the Veeam Plug‑in for HPE VM Essentials DoesThe plug‑in extends Veeam Backup & Replication to understand and interact with HPE VM Essentials resources. Without it, Veeam cannot discover

Sometime last year, ​@ertelle1 created the below blogpost where she stated Veeam Recovery Ochestrator now supports Microsoft Hyper-V “Veeam Recovery Orchestrator 7.2 - Available Now!”With the current opportunity available to some of us as documented below, I have decided to create various articles to reinforce my knowledge.Since the Orchestrator server must be connected to the SCVMM servers or Hyper-V Cluster (which I no longer have in my lab) enviionrment. I will be showing you guys the steps to

A question I ask in all of my customer demos is, " Do you have a 3-2-1 backup strategy and most of the time, I get the answer yes. Other times, the answer is what is that? I’ll take that opportunity to educate them on what it is and how to protect themselves. In this article, I’ll go through what the 3-2-1 backup strategy is and how to implement the 3-2-1-1-0 strategy. IntroductionYou've probably heard the 3-2-1 rule a hundred times. Keep 3 copies of your data, on 2 different media types, with 1 copy offsite. It's been the gold standard of backup strategy for years — and for good reason.But the threat landscape has changed. Ransomware doesn't just encrypt your production data anymore; it hunts for your backups too. That's why the industry evolved the rule to 3-2-1-1-0, and if you're running Veeam in your environment, you're actually in a great position to implement every digit of it.In this post, I

 I am sharing with the community the procedure I followed to resolve the failure of the Application Aware backup  post-installation of Sentinel One. Exception procedure S1 VSS SafeBOOt Tamper ProtectionOpen Administrative CMD cd "C:\Program Files\SentinelOne\Sentinel Agent your-version"sentinelctl unprotect -k "<passphrase>"sentinelctl config -p agent.vssConfig.enableResearchDataCollectorVssWriter -v false -k""PASSPHRASE"sentinelctl config -p agent.vssConfig.vssProtection -v falsesentinelctl config -p agent.vssSnapshots -v false

Veeam Data Cloud (VDC) is Veeam’s cloud-delivered backup platform designed to simplify how partners deliver backup services. It removes the need to manage the underlying infrastructure while providing protection for Microsoft 365, Entra ID, Microsoft Azure workloads, Salesforce, and secure storage through Veeam Data Cloud Vault.If you’re a VCSP partner looking to explore VDC, getting started is fairly straightforward.The primary license administrator of the VCSP partner account (with an active rental agreement) can register the business for Veeam Data Cloud through VCSP Pulse.Steps to access Veeam Data Cloud in VCSP Pulse Log in to the ProPartner Portal and navigate to VCSP Pulse. In the top menu, go to Licenses and Subscriptions. Click Veeam Data Cloud Subscriptions.

Modern businesses today generate an extraordinary volume of operational data ranging from performance and capacity trends to risks and anomalies. When it comes to data protection, the data is there, and organizations need to use it to reduce risk and improve recovery readiness. This is where Veeam ONE, a component of Veeam Data Platform, comes into play. If you are already familiar, it’s no secret that Veeam ONE collects and stores data about virtual and backup environments. What’s important is Veeam ONE’s ability to transform this data into clear and actionable insights. Through its vast number of reports, you gain structured documentation of what is happening in your backup environment and why.  This helps bring to light any risks, issues and trends so you can plan and make decisions accordingly.  Veeam One’s HTML-5 based reporting engine provides maximum flexibility, allowing you to reorder columns and filter data sets based on your organization’s requirements. Different t

Hi,we are planning to use the Veeam Data Cloud for Salesforce Backup. We need to keep backups for 2 years. What, if we decide to switch the backup-partner. For example Salesforce native backup? We cancle our subscription. Fair-Use-Policy will delete the backups after 30 days, correct? What options do we have, to keep  the backups as long as our requirements are? The same question would be, if we decide to use veeam backup for m365 in the data cloud. Here we would have onedrive files, with a retention time of 2-10 years.  We do not plan to quit anything, but we need a valid exit strategie if we decide to use a cloud product.