Community

Veeam Data Platform Advanced and Premium Editions give organizations powerful tools to document and report on their environment. This includes gathering data around capacity planning, protection policies, and performance insights. By utilizing this functionality, teams gain visibility into their data protection environment to help maintain security, achieve consistent compliance, and improve operational efficiency.The latest release of the Veeam Data Platform brought major updates to Veeam ONE’s reporting capabilities. By delivering a faster, more interactive experience, reporting within the platform has become more modern, moving away from traditional SQL Server Reporting Services (SSRS) to HTML5-based reporting. You will see this experience with Veeam Data Platform and Veeam Backup for Microsoft 365 reports.This modernization is accompanied by a new PostgreSQL-powered Veeam ONE Reporting Database designed to accelerate large report generation. Reports that used to ta

Greetings friends! Today I want to share something that has been on my mind for a while, and I finally decided to tackle it head-on. If you're running Veeam Backup for Microsoft 365 with object storage (Wasabi, AWS S3, Azure Blob, or any S3-compatible provider), you've probably asked yourself:"How much space is each user actually consuming in my VB365 backup repository?"And if you're like me, exploring the Object Storage, you've also asked:"Wait... who is that GUID? And why is there data from an organization I deleted months ago still sitting there?"Spoiler alert: I found several GB of orphaned backup data that I could safely delete. But more on that little adventure later. Let's go!The Challenge: Understanding What's Really in Your Object StorageHere's the thing. Veeam Backup for Microsoft 365 stores backup data in object storage using

 Veeam 13 offers new option to add as backup component into Veeam infrastructure with service account. If you are missing windows component and you would like to use same method as connection between appliances. Then this method is the right one.Method is described in KB. Let’s go how to achieve that step by step: Deployment kit is downloaded from windows Veeam 13 console. Here looks downloaded package.Installation from PowerShell, locally on windows server.

Over the last decade, ransomware attacks have changed dramatically. What once was a simple malware encrypting user files has evolved into a business-driven cybercrime model. Today, attackers think strategically, move laterally, and aim directly at what truly hurts an organization: its ability to recover. To understand how to defend modern environments, we must first understand hacker thinking. This means looking at attacks from the attacker’s perspective — how they enter, how they move, and how they decide when an attack is successful. More importantly, it means understanding why backup infrastructure has become a primary target, not an afterthought. How Hacker Thinking Has Evolved Over Time In the early days, ransomware attacks were opportunistic. Attackers relied on phishing emails, weak

I’ve been running Veeam v13 in the Home Lab for a few months now. It’s working flawlessly, backup my servers locally and Wasabi immutable storage in the cloud, running replications, and using Sure Backup to verify my backups are actually working.With Version 13 Veeam improved Universal Continuous Data Protection(U-CDP). If you are wondering what even is this, let me quote Veeam here, as it is a pretty good explainer.“Universal continuous data protection (CDP) is a technology that helps you protect mission-critical workloads when data loss for seconds or minutes is unacceptable. Workloads of various types, such as virtual, physical or cloud machines can be replicated to VMware vSphere cluster or host. CDP provides minimum recovery time objective (RTO) in case a disaster strikes because CDP replicas are in a ready-to-start state.”In this post I’m going to walk through setting this up and running CDP. There were some gotchas I ran into my home lab, but at the end i

 Veeam Data Platform v13 is one of the most significant releases in Veeam’s history. It introduces major advancements in security, AI-driven threat detection, cloud recovery, performance, and operational simplicity. Rather than being just another upgrade, v13 positions Veeam as a true cyber-resilience platform, helping organizations detect threats, protect backup data, and recover cleanly and confidently.In this blog, we’ll cover two key areas:What’s new in Veeam v13 and the features worth getting excited about A complete Veeam v13 Adoption Playbook — phases, risks, and best practices for rolling out the new platform What’s New in Veeam Data Platform v13Veeam v13 brings major enhancements across security, cloud recovery, performance, observability, and platform flexibility. Below are the most impactful additions. 1. Security-First De

After my previous articles on backup security and object storage on-prem, today, we'll examine the best practices for using them with Veeam.Here Why go with on-premises object storage and here The choice of storage explained my ideas about a new generation storage as a backup repository.So we'll check out the best configuration for creating a backup job and explain why we chose it.Object Storage as the main repository in Veeam v12.3.As we all know, since version 12, it's been possible to use an object storage repository as a primary destination for backups. This makes the architecture simpler and offers greater flexibility.When you're gett

Veeam Backup Configuration Restore – MS SQL Error & WorkaroundContextDuring a Veeam Backup & Replication configuration restore on a new server, I encountered an error. “XML Parsing: document parsing required too much memory”Source server: MS SQL Standard Edition Destination server: MS SQL Standard Edition (same version)What I triedSame MS SQL Standard Edition → Same error Migrated to MS SQL Express Edition → Same error Switched to PostgreSQL → It worked!This confirmed that the issue was related to MS SQL.Veeam Support RecommendationsVeeam Support provided two options:Option 1: Restore with

Hey folks,A little share that could be helpful. As a reminder, in Veeam v13 we have a 100% Linux Veeam Infrastructure!New Linux Roles• Mount Server• Guest Interaction Proxy• Log Shipping Server• Gateway Server:SMB / NFS StoreOnce DataDomain Object Storage NDMP • WAN Accelerator • vPowerNFS • SMB and NFS components (network share backup) • Agent Distribution ServerWhat a big list! But what happens when you upgrade from Veeam 12?Here’s my situation: many Veeam Linux proxies were already present. After the upgrade, all the components were updated. So let's go ahead and add some of them as a Gateway Server… and what a surprise: no proxy present! 

My SubscriptionsHi everyone, what is the difference between Veeam Data Platform and Veeam Data Platform Advanced?I plan to upgrade our VBR server to v12 from v11. It does have Veeam ONE on it. Orchestrator is on its own server. I assume I want the Veeam Backup & Replication ISO and Veeam ONE ISO. However, I’m wondering what am I missing out if I don’t get the “Advanced” ISO. Thanks!

When Veeam Recovery Orchestrator (VRO for short) is used, it is usually an infrastructure with a VDP Premium license. Alternatively, the use of VDP Advanced and additional 10 instance packs for the Orchestrator would also be possible.In the Orchestrator itself, there are various ways to map recovery plans.In this article, I would like to show a way to first shut down the productive workloads when using replication jobs, transfer the delta data to the DR-site and then boot it up there. This corresponds to a native planned failover within Veeam Backup & Replication (with more options and reporting functionalities).  Replication Jobs in VBR In my lab, I work with various VMware vSphere tags, which map SLAs here (Gold, Silver, Bronze). My replication jobs wi

  Recently, some of us had the privilege of receiving an invitation to participate in the Veeam ONE or Veeam Recovery Orchestrator Essentials training course. I don’t take this opportunity lightly and am genuinely grateful to ​@Federica, ​@NikolaPejkova and to the entire Veeam Team for the chance to learn and grow. I would also like to sincerely thank Tim Myers for the excellent course structure and outstanding delivery. The content was clearly organized, easy to follow, and reinforced with practical on-screen demonstrations. Absolutely amazing! Veeam Recovery Orchestrator (VRO) extends the funct

Service providers can configure the VSPC with SSO SAML authentication. I recently tested this in combination with EntraID for a customer and thought I'd share the process in the form of this step by step guide. You can configure SAML for you as a service provider but also for each customer with their own identity provider.In this guide, I configure for the company "Test Company" an SAML EntraID IDP. First, log in as the Test Company owner account and add a new Single Sign-On provider:  You need for each customer a different URL, in this example I use "https://testcompany.vspc.my.company:1280"

I need to back up my Windows without using the cloud. I mean that the backup should be stored on my own laptop, not in the cloud. When I downloaded Veeam One, its size was about 3.5 GB, which is quite large.

Hi All,I would like to share a scenario i encountered related to the Veeam SQL Plugin communication port and gather feedback from the community.By default, the Veeam SQL Plugin uses port 6791 for communication. In one of our customer environments, this port was already in use by another component (Elastic Agent), which caused a port conflict. As a workaround, we were able to change the SQL Plugin communication port by creating a custom configuration XML file.Workaround ImplementedWe created the following XML file:File name:veeam_common_config.xmlLocation:C:\Program Files\Veeam\Plugins\Microsoft SQLContent of the XML file:XML

Enterprise Manager Self-Service Portal - Server Error. I remember being able to fix this before but can’t remember the particulars. I had to go to IIS, I think application pools.   

Hello guys,Have the following error regarding SureBackup Jobs: Ping is being skipped:  Dedicated physical Hyper-V standalone server in use for only SureBackup tests.Production network is where the actual Hyper-V server is in (aka Production Network), and isolated network is newly created. 

Hi all,I have recently built a new Veeam Backup for Microsoft 365 server (v8.3.0.2201 P20251212) and attached existing Azure Blob storage from a previous server which contains backup data I need to restore from.The issue is the Microsoft 365 tenant was previously named [OLD-TENANT-NAME].onmicrosoft.com and has since been renamed to [NEW-TENANT-NAME].onmicrosoft.com. Both entries share the same Office ID ([OFFICE-ID]) which is causing a duplicate conflict and preventing me from accessing the existing restore points.The error we are seeing is:A duplicate organization Office ID was found in the repository (Office ID: [OFFICE-ID])The old tenant no longer exists in Microsoft 365 as it was renamed. The backup data in the blob storage is tied to the old org entry and we need to remap it to the current tenant so we can perform restores.What we have already tried:Removed the old organisation entry from the Ve

We have replaced are our physical servers and are decommissioning the old servers.  I have two servers that were setup and functioning as proxies in Veeam.  When i go to remove the server, i get a message saying the server can’t be removed because it is still associated with backups.  The backups it indicates are blocking are no longer jobs and the only references to those names i can find are in the Orphaned and Exported Disks section, but there is no option in there showing an association to a server or a way to change anything.I have opened a case with support (02943295) and so far they are suggesting that we will need to manually edit the database records to remove this association.I am curious if any one else has had to manually modify database records just to remove old servers from Veeam Backup and Replication?  This does not seem to make sense and is likely just masking the real issue.

Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and

The project announced here became even bigger. However, the Veeam Data Integration API remains the "main actor", except that many new options have now been added, as "my ideas factory" and feedback on a similar script have been incorporated. Let’s look at what’s NEW.📑 SearchThe host2scan parameter scans a selected restore point of the specified host. The repo2scan parameter can display all hosts with supported restore points in the specified Backup Repository. Then select a host and start the scan. NEW Or with repo2scan and the option all to scan the latest restore point for all found and supported host ty

I have been validating MongoDB full instance restore using Veeam Explorer for MongoDB (VBR v13) and would like to raise a discussion related to file ownership and permissions after restoring.Observed BehaviorWhen restoring a full MongoDB instance to a Linux server, the restored MongoDB data files are owned by the OS user used during the restore process (restore authentication user).As a result:MongoDB service fails to start under the original mongod service account, or The node cannot be cleanly added back to an existing MongoDB replica set Manual post‑restore steps are required (chown / chmod) to revert ownership to the original MongoDB service userThis aligns with current permission requirements documented for MongoDB restore operations, where the restore user m

 Happy Friday, Veeam Community!  I am bringing you another packed newsletter from our Veeam Vanguards heroes who published an incredible amount of a veeamazing content during the last month.  Take a look for yourself and see what topics resonate with your interests. 🤓 ​@AndreTheGiant - Veeam acquires Object First - https://vinfrastructure.it/2026/01/veeam-acquires-object-first/Veeam Backup & Replication 13 patch - https://vinfrastructure.it/2026/01/veeam-backup-replication-13-patch/ Veeam Kasten