Community

Hello Veeam Team and Community,I’d like to clarify something about partner and certification requirements.If my company plans to: Provide managed services to customers who use Veeam Data Platform (for backup and recovery management), and Also act as a reseller of Veeam licenses (via authorized distributor), do we need to hold any specific Veeam certification (e.g. VMSP, VMTSP, VMCE) or reach a certain partner tier in the ProPartner program?Or is being a registered ProPartner and sourcing licenses from an authorized distributor sufficient?Appreciate your guidance so we can ensure full compliance with Veeam’s partner requirements.

Hello,VeeamONE till version 12 was using connection from VeeamONE to VBR on port 2805 to connect to Veeam Agent on VBR.In Veeam ONE 13 connection was exchanged from VBR to VeeamONE on port 2805, even VBR is on version 12.x.We had enabled only connection from central domain, where is located Veeam ONE, to customer domain, where VBR is located.So during adding VBR into Veeam ONE, Veeam Analytics Service (previously Veeam Agent) was installed, but connection timed out. Adding VBR failed due no response from Veeam Analytics Service - status “Failed to install”. Is not possible to download logs to troubleshoot as echo is not providing port number. On helpcenter is described VO → VBR connection only, even for Linux VBR. Once connection from VBR to VO was allowed, data update was successful.Finally, result is installed and Healthy. 

Current LAB setup(all settings inherited from previous host): HypervHostB with a private switch 2 virtual machines on this private switch VM1 - ClientPC with windows 10 iso installedVM2 - PrimaryDC (Veeam restored from HypervHostA to HypervHostB - Session Type is Full VM Restore) - this server has roles(ad fs mgmt, dhcp, dns and gpo repectively)    - has 2 vm switches, Data: ip 192.168.50.1, subnet 255.255.255.0, gw - 192.168.50.150, preferred dns:192.168.60.240(DC2) and secondary dns:192.168.50.1                         Voice: 20.20.20.5 subnet:same, gw:20.20.20.1, dns1:PDC, dns2:DC2Observation:1.VM2 fired up nicely, AD components such as aduc, domains and trusts, gpo etc all open fine, able to logon with my local and domain AD accounts successfully 2. Fired up VM1, VM1 picked up IP via dhcp successfully, showing domain name schools.local on VM net adapter3. Both vm1 and vm2 can successfully ping each other via ip and dns name, nslookup works as well.4. vm1 is listed in dns on vm2Chec

QNAP QuObjects application is free and certificated for objects with immutability, which means you can use it as object storage within Veeam for a backup repository that supports their immutability feature.QNAT QuObjects Requirements: 1.Log on to the NAS as an administrator.2.Select App Center. 3.Click the Search icon on the App Center page. 4.Enter QuObjects and select the QuObjects and click Install. 5.Click Open after Installation is completed. 6.Ensure turn on Server Connection on the QuObjects S3 Compatible Object Service page and select User Management. 7.Click Add User on the User Management page. 8.Select a user on the Add an Authorized User page and click Add. 9.Click the Add key icon on the User Management page. 10.Ensure QuObjects creates an access key for the user and select Storage Space. 11.Click Create on the Storage Space page. 12.Enter the storage space name in the Folder Name field on the Create Storage Space page, select the user and click Create. 13.Select the new c

We are running a VMWare environment.We created a new iSCSI datastore for some of our VMs due to the previous Fastclass Fibrechannel datastore having issues.All of our VMs are running well on this new datastore but every Veeam backup job fails for VMs housed on it. All backups for VMs running on other datastores are fine. The VMs show up in Veeam and are able to be added to jobs and show their file sizes, but fail when the job is run.Any ideas? I’ve pasted the typical error message below that we get, with some of our info redacted. Note that some of the files do actually back up, namely the smaller files like the .vmx, .vmxf, and .nvram, but the .vmdk file seems to be where the error occurs. 10/1/2025 3:18:59 PM :: Processing ******** Error: Failed to open VDDK disk [[***NAME OF ISCSI DATASTORE***] ***NAMEOFVM***.vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [***VMWare HOST IP***];Port: 443;Login: [***USERNAME***];VMX Spec: [moref=9];Snapshot mor: [9-snapsho

Hi Everyone,Earlier today, during the delivery of the Veeam Backup & Replication v12.3: Configure, Manage, and Recover course, I felt compelled to write this article because I've noticed that most students, when they need to create a repository, only think about capacity and forget to consider throughput. Failure to properly configure the required throughput will certainly lead to several problems. Furthermore, the vast majority consider using only RAID 5, without a hot spare disk.In this article, I will make regular updates.https://pulia.com.br/backup-repositories-repositorio-em-bloco-das/ After reading this article, you'll understand that buying an Object First box is the best option to have a repository. Enjoy reading it! have a great week.

 Active Full Backup and Synthetic Full Backup in Veeam essentially serve the same purpose: creating a full backup file containing the data of the entire virtual machine (VM). However, they differ significantly in how they do this and, consequently, their impact on the system.Here are the definitions and differences between these two backup types:What is Active Full Backup?Active Full is the traditional full backup method.Data Source: Reads data directly from the source data store where the virtual machine (VM) is located. Process: Veeam Backup & Replication retrieves all VM data from the source, compresses and deduplicates it, then writes it to the backup repository as a new .vbk (full backup) file. Areas of Influence: Production Environment (Source): The load on the source datastore and VM where the VM is located will be high because all the data needs to be read. Network Resources: Network bandwidth is intensive as all data must be transferred from the source datastore to the ba

This is a great day Community!At VeeamON in San Diego back in April, Anton shared how Veeam is looking to add more hypervisor support to their product. Late last year, they began answering customers’ call to do so by implementing support for Proxmox. In more recent months, Veeam announced support for both Scale Computing SC/Hypercore and HPE on VM Essentials. But, that’s not all….Some of us in the Veeam100 Community were approached about a month ago to test out a Veeam Plugin for XCP-ng. Based on our testing & feedback Veeam has been hard at it getting the Plugin updated, and just today released a new Public Beta ripe for you all to test out! That’s pretty amazing considering something else pretty significant was released a couple weeks ago (has anyone heard about the Veeam Software Appliance on v13??? 😉 )For testing instructions, download link, and password go to the following Forums post by Anton Gostev:https://forums.veeam.com/kvm-rhv-olvm-pve-schc-f62/veeam-plug-in-for-xcp-ng-

Hey all, we’ve got a new installment in our RegKey of the Month series up now! This month’s spotlight: the Classified Stripe banner in Veeam Backup & Replication.Why it matters: if you run multiple VBR servers (prod, test, branch, DR, etc.), a visual cue (e.g. “PROD – do not touch”) helps avoid costly mistakes. The post covers: how to implement it via registry keys in Windows deployments how to achieve the exact same result on the Veeam Software Appliance v13 (yes — even though there is no registry in VSA, we map the settings into config files) tooling tips, color code guidance, and gotchas Curious? Read the full deep dive here ➡️ https://integriservices.blogspot.com/2025/09/regkey-of-month-october.htmlVSA v13 ? No problem for Regkey-man ! 

Proxmox VE 9 introduces external QCOW2 snapshots on thick-provisioned LVM volumes over SAN (including FC and iSCSI). There is already an updated plugin, that supports not only this version but also those specific snapshots.​@Iams3le already gave insight about the installation of the new plugin: Veeam Plug-in for Proxmox VE v12.1.5.17 update to Support Proxmox VE 9.0 | Veeam Community Resource HubNow, using a shared FC (or iSCSI) SAN is possible just like we did with VMware - while still being able to generate nice Veeam backups of the VMs on the LUNs: Plug-in for Proxmox VE v12.1.5.17 -> shared LVM? - R&D Forums Here's the breakdown:QCOW2 is required for snapshot functionality on SAN LUNs. Snapshots are implemented as external overlays (not internal QCOW2 snapshots). Each snapshot creates a new logical volume to store delta data. This allows rollback and versioning, even on raw block devices like FC LUNs.[TUTORIAL] - Inside Proxmox VE 9 SAN Snapshot Support | Proxmox Support For

The IdeaWhen the weather is bad on weekends, I listen to music and vacuum, and then I can become creative. This weekend, an unusual idea came to my mind:What if Monopoly was not about money and hotels but backups and recovery? And when I get creative, the idea doesn’t let me go; I start doing stuff. Here is the result:BackupOpolyA playful way to explore Veeam’s ecosystem, while still keeping the fun and strategy of the classic board game. The player tokens would be a tape cartridge, a notebook, a server, and more. I sketched a board design in Excel (Drawing with Excel relaxes me).Design for the game boardAnd then I put together some basic rules. Here's what came out of it.ObjectiveBuild the strongest data protection environment by acquiring Veeam products, storage systems, and advanced features. Collect VUL licenses, charge opponents when using your technologies, and avoid penalties for ransomware or audit. The last player not bankrupt wins.Instead of dollars, players pay and earn Veea

I’d like to share my current backup infrastructure and get feedback on best practices when using Synology NAS with iSCSI LUNs as Veeam repositories.🔹 Current Setup Main Site Backup Jobs → Repository on Synology NAS (connected via iSCSI LUN to VM). Secondary Site Backup Copy Jobs → Repository on Synology NAS (iSCSI LUN). Immutable Backups Another Synology NAS configured as a Hardened Repository (WORM / immutability). Backup Jobs First Backup is Full Backup, then after then we do incrementals and Synthetic Full Backups on Fridatys. Disks are configured as ReFS with 64KB block sizes since that was recommended when I was configuring this. Aprox 2 years agoAny recommnedations would help. 

I tested the new VSA 13 with SAML implementation and thought I'd share the process in the form of this little step by step guide.  This guide provides instructions to configure Entra ID SAML integration for SSO access to VBR with version 13  As requirements, you need an Entra ID account with one of the following permissions: "Cloud Application Administrator" or "Global Administrator" for creating a new enterprise application.  You also need a working Veeam version 13 installation.   First, configure the Entra ID application:  Access Entra ID (https://entra.microsoft.com) and navigate to Enterprise apps and create a new application.   Search in the gallery for "Microsoft Entra SAML Toolkit" and select the app  You can specify a name, I choose "Veeam 13 SAML" and then click on create  In the newly created application, navigate to Single sign-on and select SAML.   We now need some information from our VBR.  Open "Users and Roles" settings  Navigate to "Identity Provider" and enable SAML a

So I’ve been trying to restore a VM to my Proxmox cluster and I keep getting an error `Failed to reach the hypervisor. Error output: can’t open ‘ssh-public-key-string’ - File name too Long`. I tried recreating the workers, testing the connections and rechecking all the configs I can think of and I can’t get past this point. Every host is configured with IP and ‘root’ credentials. Each is available and the workers start up seemingly fine. Running ‘Veeam Backup and Replication 12 Build : 12.3.2.3617` on Windows Server 2022 Standard

This topic is for Lucho ​@JailBreak and others who want to easily install OpenShift virtualization. 🚀 Red Hat simplified OpenShift Virtualization setup with a more intuitive and faster installation experience in the Developer Preview of OpenShift 4.19, coming soon in tech preview, 🌐 making it easier in isolated environments and ⚡ speeding up deployment. The highlights its ⭐ key benefits, the new 🖥️ UI, 🆓 registration-free installs, and a 📘 quick start guide.We’ve made deploying OpenShift Virtualization easier and faster, enabling quicker adoption with: UI-driven configuration: simple guided wizard with best practices. Pre-installed operators: ready from day one. Registry-free installs: work seamlessly in air-gapped environments. Proven Red Hat technology: built on Agent-Based and Assisted Installers. 🤓Now, let’s go through the steps of this updated installation flow. In this example, we’ll demonstrate how to deploy a compact OpenShift cluster in a small test setup using thr

Hey everyone! Happy Friday 😃I had a quick question regarding Per-VM Backup chains. If I remember rightly, I think I read somewhere that in V12 it would be enabled by default. Are Per-VM backup chains now best practice? Anything to be aware of when transitioning to them on already existing backup jobs that do not utilise Per-VM backup jobs currently?Thank you!

I am running a daily configuration backup, as I should. :-) It is saving to my default repository, which in my case is a locally attached drive on my VBR server. (in fact, I had to do a configuration restore once, so I know that process works).But I just realized I don’t have a tape job, that copies the configuration backup to tape, in case of full on disaster and the building burns down to slag. And I guess I am drawing a blank, because I am a bit unsure how to set that up.Do I just need  to do a Tape job, choose a “Files” backup, go to my VBR server, and choose the “VeeamConfigBackup” folder? What about the “VBRCatalog” folder? Anything else I need?A better way to do this? Obviously I would want this run every day, so it goes onto a tape every day, and once a week, we send all tapes that are FULL offsite for storage.Sorry if these seem like stupid questions.

Hello all, I don't know if this is the right place to ask for help but we have been running into a brick wall for 2 days now. We have only recently gotten back into using Veeam and we succesfully rolled out VSPC to a VM in our DC. We also have another VM in our DC running VBR (neither of these servers are part of a domain), first we had this installed without Cloud Connect purely to mess around a bit. But after that stage we decided to up the license to include Cloud Connect. The VBR obviously had the management agent from VSPC installed and everything was working as intended.However when we wanted to connect the newly added Cloud Connect service via VSPC we ran into an issue where we would go to Configuration > Catalog > Veeam Cloud Connect > Servers > New. We would then enter all the correct information, we will get a pop up stating we need to take ownership of the already installed agent. Which sounds reasonable but after that we just get a prompt saying “Access Denied”.

Resolving SQL Backup Error - Code 0x80040e14 (Dispatch error #3092) / failed: 112(There is not enough space on the disk.) IssueBackup operation fails with the following error:Failed to perform internal backup                                                               Code = 0x80040e14Code meaning = Dispatch error #3092/ failed: 112(There is not enough space on the disk.)Source = Microsoft SQL Server Native Client 11.0 Root CauseThis error typically occurs due to insufficient space for temporary transaction log (T-log) files during SQL backup operations. Resolution Steps1. Verify Transaction Log File SizeContact the SQL DB Team to check the size of the transaction log file. Confirm the required space for temporary log storage. 2. Check Drive AvailabilityIf lacks sufficient space, proceed to request a new temporary disk. 3. Request Disk AdditionAdd a new temporary disk to the server. Disk size should be based on SQL DB Team's recommendation plus 10 GB buffer. 4. Configure SqlTempLogPa

Hi everybody,I am not yet an expert on Veeam B&R but today something happened that is driving me crazy.I have a server on which I have installed Veeam B&R CE and two Windows 10 PCs on which I have installed Veeam Agent CE. I directly configured the two Agents (PC1 and PC2) to back up to the Veeam B&R repository on the server. Connecting to the B&R console on the server I noticed that only one Agent appeared in the Physical Infrastructure in Unmanaged.I repeated the procedure many times and I noticed that appears only the name of the first PC that is connected to the server.Until recently, the names of both PCs were shown in Physical Infrastructure!How is it possible?

 👋 Hello friends!This is my first post here, and I wanted to take this chance to reach out to any partners in this space—whether you’re a VCSP or Reseller, brand new or a seasoned Veeam pro. If you’re looking to level up your marketing game, I’ve got great news for you!The Veeam Marketing Center (VMC) is our FREE, all-in-one tool designed to help you become a true marketing expert. With VMC, you get access to ready-to-launch campaigns, customizable assets, and step-by-step guidance to help you attract more leads and grow your business. And the best part? You don’t have to do it alone!I’m Dante Barreto, your Channel Marketing Concierge for AMER, and I’m here to make things easy and fun. Want a personalized training? Need help executing a campaign? Just have a question about marketing with Veeam? I’m your guy!Interested in getting started?Comment below, send me a DM, or connect with me to schedule your own 1:1 VMC walkthrough. Let’s make you a Veeam marketing superstar!🌎 Not in AMER?No

I keep getting the error when with the Windows Backup Agent:“Veeam Endpoint Backup is already running for user *MyUsernameImCurrentlyLoggetInWith* “When I try to edit the job currently running. But no other users are logged in or accessing the app. I have tried deleting the job. Now I can’t make a new one. Rebooting, of course. Shutting down the App and the Service. Uninstalling and reinstalling. Resetting the DB. Deleting the config folders in ProgramData and Windows Program Files. And I keep getting the error. Like something is still left on the machine, with a setting that is causing he fault. Ideas?? How do I completely remove everything from the Veeam Agent from the machine and start over?  

Earlier this year, I kicked off a series on HPE storage platforms and their integrations with Veeam Backup & Replication. We started with the HPE Alletra Storage MP B10000 and then looked at Veeam Ready – Appliance Hardened storage servers as secure backup repositories. I paused the series for a while to let some important HPE announcements catch up with the story I was telling and to complete more hands-on validation. Now is the right time to pick things back up with the HPE Alletra Storage MP X10000, the next natural step in the conversation. This blog is not a deep dive into every feature of the X10000 — instead, it’s about where it fits into a Veeam-powered backup architecture, why it matters, and how it supports cyber resilience at enterprise scale. The X10000 is HPE’s flagship object storage platform, built to manage unstructured data at scale with an all-flash, disaggregated architecture. Independent scaling of capacity and performance, powered by NVMe drives and 100 Gb Ethe