Community

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

I would like to consult your suggestions and recommendations for my case. Please refer to the Veeam infrastructure diagram below. There are two Linux Hardened Repositories in the environment. The customer needs to upgrade the operating system from RHEL 9.7 to a supported version, as RHEL 9.7 will reach end of support soon. ConstraintsThe hardware for the Linux Hardened Repositories was purchased in 2023, and the customer intends to continue using it. The license subscription of RHEL will expire in December 2026. The customer is planning to upgrade to Veeam v13. 

Shared Mailboxes seem to pose a unique challenge for many customers because in VDC a Shared Mailbox can be backed up without consuming a VDC license, as long as the Shared Mailbox meets the following criteria:• It is less than 49.5 GB in size.• It does not have a Microsoft license associated with it.When a Shared Mailbox reaches 49.5 GB in size, Microsoft attaches a license to it. Since at that point it has a Microsoft license, Veeam also requires a VDC license to back it up.Some customers enable Archiving for their Shared Mailboxes. In this case, even if the Shared Mailbox is less than 49.5 GB in size, the Archiving feature requires a Microsoft license. Since at that point it has a Microsoft license, Veeam also requires a VDC license to back it up.Many of our customers have hundreds or even thousands of Shared Mailboxes, but they don’t know how many of those are less than 49.5 GB in size and how many of them have a Microsoft license.We crea

  As part of recently announced initiatives to strengthen the partnership between HPE and Veeam for the year 2026, the Veeam Data Platform is integrating with the latest versions of HPE StoreOnce Catalyst to achieve amazing data storage reduction, remove incremental backup limits, boost restore speeds to new market levels, and reduce total cost of ownership (TCO).One of the big news items in the Enterprise Backup Storage market is undoubtedly the launch of the HPE Alletra MP X10000 for Data Protection, which delivers Backup at AI speed.It is currently the world's fastest backup storage solution, numbers backed up by HPE's rigorous testing and real-world comparisons against publicly available performance metrics from other

For those who joined my online and VeeamON sessions on migrating from VMware to Hyper-V or Proxmox, I promised I would share my cleanup scripts. It took longer than planned to prepare them, but they are now ready.Online session HERE unfortunately there is no video of the VeeamON session that was migrating to Proxmox.When you use Veeam to migrate a Windows virtual machine, the work is not done when the job finishes. Your migrated VM is now running on a new platform, but it still contains old drivers and devices from VMware.These leftovers can cause instability, performance issues, or future

Hello, I have a cluster on my Veeam v13 software appliance I’m looking to configure with CDP, however when i go to install the I/O filter the cluster doesn’t show up. What am I missing. I do have CDP configured on Veeam and another cluster is configured with it. Any ideas? 

Hi everyone,I’ve recently needed to automate some tasks using PowerShell and started looking for study resources online. I found a YouTube video from 2022 and  another one from VeeamON 2020. I know it’s a bit old, but based on what I learned from it, you can still use many of the concepts to understand the basics and how to work with PowerShell.Here is the link and some screenshots for those who would like to learn.      

I installed the Veeam 12.3.2.3617 on a virtual Windows Server 2025 and this has been a very bad experience.  I started to migrate the repository data to the new server, but it has become very unusable.  Now when I look up the issues on the web with Veeam, other people seem to have similar issues when using server 2025 with the repository on a ReFS file system.  At this point, everything is in limbo, meaning that the server randomly hangs when Veeam runs.  30% of the repository has been moved, but I can’t seem to do anything with the server.  Every time we try to access Veeam repository it just hangs.Does anyone have any suggestions other than scrapping the Veeam backup installation completely?thanksMatt