Recently active topics

My journey with Veeam began in 2020, right in the middle of the pandemic, a time filled with uncertainty, challenges, and a lot of learning. Troubleshooting and analysis weren’t easy at first, but something quickly stood out to me: the Veeam Community.A space where experienced professionals shared knowledge generously and newcomers like me could grow by learning from real-world experiences. I started quietly, absorbing everything I could, and eventually felt the desire to give back. Helping others who faced the same difficulties I once did became a natural part of my routine.One moment that really moved my story forward was when Christian invited me to write posts for his blog. That opportunity boosted my confidence, helped me grow faster, and brought me closer to community members I deeply admired, including the Veeam 100, which slowly became a personal dream.Coming from the outskirts of Belo Horizonte, I’ve always valued every step of my journey. Some people doubted me along the way,

Hi All,If we keep our Veeam VBR on V12.3.2.4165 and we upgrade the Veeam backup for AWS appliance from V9 to V10 what has integration with this VBR. Will that break the integration. Is there only integration with VBR V13?I did request this question in a case and got the following answer backRegarding Veeam Backup for AWS, upgrading from version 9.1.0.45 to version 10 will not impact integration with VBR 12.3.2.4165. There are no documented version dependencies or incompatibilities between these specific versions.However on a Reddit forum I found a topic where customers told that the upgrade did break the connection with there VBR on V12.3.2.4165Veeam Backup for AWS 10 : r/VeeamOr is there a newer version of the plugin that repairs this connection if it gets broken.Counting on your experienceThanks,Benny

I try to migrate my vmware VM to hyper-v using veeam and i always got ‘failed to modify disks”. Anyone know how to fix this? 

Object First OOTBI (Out-of-the-Box Immutability) is a purpose-built, secure, and immutable backup storage solution engineered specifically for Veeam Backup & Replication. By combining storage performance, immutability, and simplicity, OOTBI helps IT teams achieve reliable data protection while reducing operational overhead.Also, OOTBI eliminates the complexity associated with traditional backup storage by offering an appliance that you can deploy, configure, and integrate with Veeam in minutes. Below are some article relating to Object First OOTBI.Steps to configure Object First OOTBI Appliance | Veeam Community Resource Hub Enable Honeypot on Object First | Veeam Community Resource Hub  Steps to integrate OOTBI with Veeam Backup and Replication and Perform Backup and Restore | Veeam Community Resource Hub Comparing OOTBI by ObjectFirst to VHR | Veeam Community Resource Hub Object First Appliance Setup and Remote Connection Options | Veeam Community Resource HubRole-Based Access Co

Customer has Wasabi for M365 backups -- needs to migrate to on-premise S3-compatible storage -- what is the best and fastest (if not the same) options do I have

V13 - The environment described in this architecture consists of 500 VMs that require traditional Veeam replication to an offsite datacenter. Each VM has an average of 200 GB of storage space. RPO is 12 hours, requiring replication to occur twice a day, completing within an 8-hour window. The inter-site link is 1gb/s.  This deployment will not share proxy resources with any existing backup tasks. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup/replication method.

V13 - The environment described in this architecture consists of 100 VMs that require traditional Veeam replication to an offsite datacenter. Each VM has an average of 200 GB of storage space. RPO is 12 hours, requiring replication to occur twice a day, completing within an 8-hour window. The inter-site link is 1gb/s.  This deployment will not share proxy resources with any existing backup tasks. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup/replication method.

Hi everybody, currently we’re working with a customer who has build already 5yrs of retention with AvePoint. Migrating the backupchain from one to another product is in most cases not possible. Is anybody aware of the existence of ‘standby’ licenses where the customer pays less but has the ability to restore for a certain period without adding new points ? This gives him then the time to build op the retention on Veeam Backup for M365. It would be nice if we could create here a list of products / vendors who have such and option. (mostly not public available on their website) Then we can already now during onboarding what route we have to go.

I have been using BackBlaze for cloud storage for about 5 years with Veeam12. I am now moving to Veeam 13 and want to attach to a new bucket. I created the bucket and attached to BB using a new application key. The problem I am having is when I got to ‘Select Folder’ I can see the bucket but cannot list any folders under the bucket. Since I cannot list the folders I cannot select a folder which means I cannot continue. There are no errors generated. Any ideas aside from open a support ticket?

Good day, I have a PVE 9.0.18 in my NUC, using local storage only. Yesterday I updated the VBR and Plugin to the very lastest versions. But..Well, the Proxmox plugin still isn’t working for me… it’s really strange: I configured and tested the worker successfully;I added a Windows VM (same subnet as the VBR, no firewall) to a jobIf I run the credentials test, it fails because the VM is powered off (??)The backup, even crash-consistent, also failsFor the credential test, I guess the error in the log is: “”aiting for file C:\ProgramData\Veeam\Backup\Plugins\PVE\Backup\PVE-Win_c1c3bce9-32d8-419d-b31a-6a63f6c6d2de\8fa94a5b-e558-4d50-bb67-241ff316ecab\PVE-Win.log to be unlocked”for failed backup (hot add mode)“Failed to await the Backup task 444dd208-68ee-498c-aa5a-8282d85b2369: Veeam.Communication.TypeProvider.Invoke.RpcCallException: Failed to perform backup: Failed to prepare disks for backup” what am I doing wrong?

Hi everyone,I believe I’ve encountered a bug in Kasten K10 version 8.0.6. When creating a backup policy using a preset that includes block mode export, I noticed that the system automatically forces "Export snapshot references only", even though the preset explicitly specifies full volume export and a PersistentVolume (PV) is present.To test this, I created a policy that should export the full volume. However, once applied, the policy is transformed into "Export snapshot references only", and even after removing the policy, the export behavior remains unchanged.Has anyone else experienced this issue?Thanks in advance!

 Nuovi rilasci oggi in casa Veeam.  Da oggi è Generally Available (GA) la versione 13.0.1.180 di Veeam Backup & Replication, che include il supporto per le versioni Windows Server.Oltre a VBR, oggi sono state rilasciate anche le nuove versioni della suite:Veeam Recovery Orchestrator (VRO) v13.0.0.1005 Veeam ONE v13.0.1.5924 Veeam Service Provider Console v9.1.0.30636 Veeam Agent per Windows e per Linux v13.0.1.120 e molto altro ancora🔗 Guarda la pagina ufficiale e scarica le ultime versioni: https://tinyurl.com/2y2z2ygfNota: I documenti "What's new" e le Release Notes non sono ancora online.È ora di entrare in laboratorio per testare gli aggiornamenti! 🚀 

Are your Veeam Backups failing because your VMs live in DMZs or tightly firewalled networks? You're not alone! In large-scale, secure environments, traditional network-based Guest Processing often hits a wall (literally!). But there's a simple, yet powerful, fix you might not know about: Changing the order of Veeam's Guest Processing Methods.We're diving deep into the Why and How of prioritizing networkless processing for both VMware vSphere and Microsoft Hyper-V. This quick configuration change ensures Veeam always tries the most suitable, hypervisor-channel-based communication first, bypassing those tricky network barriers and keeping your backups successful.https://integriservices.blogspot.com/2025/11/regkey-of-month-november.html

Good evening, wonderful community!I'm not very active anymore, but you’ve always stayed close to my heart. To my fellow Windows users: I revisited some code, updated a topic from last year and completely rebuilt it for the 2025 version.I'm talking about: https://community.veeam.com/blogs-and-podcasts-57/direct-to-windows-object-storage-on-premise-with-minio-6055Are you still looking to test direct-to-Object Storage in an on-prem Windows Server environment? Well…This time, I used a simple internal setup, used purely for testing and educational purposes, yet fully on-prem and Windows compatible:Proxmox VE 8.4 Veeam Backup & Replication 12.3.2.3617 MinIO Server Community Edition 2025Note: as before, this setup is intended strictly for internal testing and educational use.Prepare your Object Storage Windows ServerI set up and updated a Windows Server 2025 for MinIO Community, keeping it in a Workgroup.This time, the VM had a single disk with 100GB allocated for both the OS and data.The

Hello Valued Partners, I hope everyone is doing well in terms of health as well as wealth. I wanted to take a moment to discuss a crucial aspect of our work that often gets overlooked but is incredibly important—regular software patching. As you know, software patches are updates designed to fix bugs, improve performance, and address security vulnerabilities in our systems. When we neglect regular patching, we leave our systems exposed to potential threats, which can compromise our data integrity and the overall security of our network. “Veeam is always committed to share the security patches within the defined timelines.” Regular software patching helps us stay ahead of cyber threats by addressing known vulnerabilities before they can be exploited. This proactive approach not only protects our sensitive information but also ensures smooth and efficient operation of our software applications. Additionally, staying up-to-date with patches can enhance the functionality and features of ou

Hi folks, as of today, V13.0.1 for Veeam Backup & Replication is generally available! This release also supports Windows Server versions of VBR.In addition, Veeam Recovery Orchestrator (VRO) v13.0.0 and some other products like Veeam ONE v13.0.1 and Veeam Service Provider Console v9.1 have also been released today. So I went into my lab and just started the upgrade procedure from my Veeam Recovery Orchestrator Environment / VRO 7.2.1 → 13.0.0.See the steps below and hopefully no issues… Download the binaries from: Discover the Latest Version of Veeam Solutions. And make sure you have a backup of your current installation 😀 Step-by-step in Screenshots: If nothing special mentioned, it’s in my case a Next, Next, Finish process... Goodbye old icons?                         oops, let’s see… I just copied the mentioned warning in the clipboard: Mostly deprecated features (within VBR), wh

Hi all,We have been using veeam backup and replication for some time with no issues, test restores work every time. Our licence on B&R shows enterprise plus, and the package shows as essentials. We have always renewed through an MSP.They have just quoted for renewal and i noticed the price had doubled and they had moved to monthly billing, so i queried it and was told they were offering a different package now called ‘Data platform advanced’ - hence the higher pricing.I am a bit confused about what actual licence we need to carry on as we are with the software which we are happy with? On the actual software the licence says ‘Edition enterprise plus, package essentials’When logging into veeam the licences say we currently have ‘Veeam Data Platform Essentials Universal’  And our MSP want to sell us ‘Data platforms advanced’ Are ‘edition enterprise plus, package essentials’ and ‘veeam data platform essentials universal’ the same thing?If i accept the MSP ofer of ‘data platforms advanc

Hey everyone,Let’s kick this off by highlighting that as of this moment, Microsoft SQL Server 2025 has not yet been validated for the Veeam Data Platform, as it was only made GA yesterday the 18th November 2025, so the information I’m providing here is in preparation for the inevitable support when it’s passed through Veeam’s QA.Microsoft have now released Microsoft SQL Server 2025 and in reviewing the changes, I stumbled upon some insights that I thought would be worth highlighting to those still using Microsoft SQL Server to power their Veeam Data Platform installations.Starting with Microsoft SQL Server 2025 Standard Edition, Microsoft are making two key changes that will impact scalability; an increased CPU core count, and increased maximum RAM limits. Now they are:CPU Socket Count: This is unchanged and still a maximum of 4x CPU Sockets. If you’re finding idle cores a lot with your SQL Server instance, make sure this isn’t your limit! CPU Core Count: This is increasing 50% from a

V13 - The environment described in this architecture consists of one main datacenter containing 10,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will target a local Veeam Hardened Repository  and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.

V13 - The environment described in this architecture consists of one main datacenter containing 5,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will target a local Veeam Hardened Repository  and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.

V13 - The environment described in this architecture consists of one main datacenter containing 1,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will target a local Veeam Hardened Repository  and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.