Community

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. 

Hi All, I have a VBR 12.3.2 server running in AWS as an EC2 instance.  Use Windows agent on other EC2s to back them up to an S3 scale-out repository.  The backups work as expected.  I am able to do file level restores with no problems.  When I try to do a restore to EC2 (create a new EC2) I get the following error “Unable to import the instance from an encrypted volume snapshot” when I click Next on the Reason screen.  I do have it set up to use a helper appliance.  Do you have any thoughts on how to get this working?  The volumes of EC2 that are backed up are encrypted with an AWS-managed key (aws/ebs).  But shouldn’t it be pulling from S3 for the restore? Thanks for any help you can provide.Scott

Query related a IAM user and IAM role:  Suppose if any customer has a Multiple AWS Accounts  with Control Tower Environment AWS setup, approx. 50+ account and want to take a backup of instance and DB backup using veeam backup for aws appliance,  is it possible using single IAM user and single IAM role to take backup of all workload of this separate account .  Require a IAM role permissions for Control Tower Environment AWS setup, In veeam documentation it is not available. 

If you have not upgraded your Promox node yet due to dependencies on Veeam Backup and Replication (VBR). The wait is over as Proxmox Virtual Environment (PVE) 9.0 is now fully supported. It is packed with powerful new capabilities for modern virtualisation and software-defined data centres. Whether you are running a home lab or managing enterprise-scale clusters, this release is a game-changer.Recently, I created some blogposts on how to setup Proxmox VE and also how to Backup and Restore Proxmox VE virtual machines with Veeam.So I had wanted to upgrade to Proxmox 9.0. But because this was not supported by Veeam yet, I ended up protecting the VMs only running on Proxmox 8-3-1.Now, with the release of the new Veeam Plug-in for Proxmox VE v12.1.5.17 It now support for Proxmox Virtual Environment versions 9.0 For what’s New in Proxmox 9.0 and other details not discussed extensively in this guide, please visit the following link. Update Proxmox VETo update Proxmox VE, you can use either th

Additional Details: Veeam Agent for Linux backup job fails with the following errors:[error] Failed to create volume snapshot[error] Failed to take volume snapshot[error] Failed to perform backup [error]Veeam snapshot kernel module not foundSystem informationSO: SUSE Linux Enterprise Server 12 SP4Kernel: Linux version 4.12.14-95.32-defaultkernel-default: kernel-default-devel-4.12.14-95.24.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.32.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.128.1.x86_64dkms version: dkms-2.6.1-9.1.noarchveeamsnap: veeamsnap-kmp-default 6.3.2.1207_k4.12.14_94.41VBR Console: 12.3.2.3617VAL: v6.3.2.1207I read ready the list of compatibility with extended Linux distributions of veeamsnap and blksnap https://www.veeam.com/kb2804 couldn´t see the compatibility for a 4.12.14-95.24 or 32 or 128 also on rpm veeam repository I don't see a version(*)After to installed manually veeamsnap-kmp-default-6.3.2.1207_k4.12.14_94.41-sles12.4.x86_64.rpm and cons

Hi,A newbie here with using Veeam for Oracle RMAN backups.I am trying to understand/visualize whether the RMAN retention and Veeam Immutability are independent of each other or are they related in some way.We run our backups on the Oracle DB server using shell scripts and cron and using a RMAN catalog.We have set  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 35 days.We do RMAN delete obsolete as well.The Veeam Immutability is 7 days.Does Veeam delete the backup files if they are 7 days old or does it delete the files if RMAN fails to delete them after 35 days? Or does Veeam do nothing unless we uses the force-delete?Kinda hoping someone has a presentation of some sort to show how this works. Have read thru the documentation and can’t find any that explains this. Or maybe it is explained more clearly/visually in any Veeam documentation and I just can’t find it.Any reply will be much appreciated. Thanks in advice. 

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

Hello Community!  I am new to Veeam (last used 7 years ago, so might as well be new). Here is my current setup:  I have two Mini PC’s running Proxmox as the “Compute”.They are connected over 10GB  to a different server running TrueNAS, via iSCSI.So the VM “Data” does not actually reside on the Proxmox machine, it just acts as the compute side. Now, I have installed Veeam on a Barebones Windows machine.  I configured the Veeam software to connect to the Proxmox servers (success) and it installed the proxy’s.First backup tested was successful, but the others failed.They show “succeeded” but with “Warnings” and no actual data has been backed up.“disk scsi0 has been skipped due to unsupported storage type” I find this odd since the storage type on the successful backup is the same as the other VM’s I am running, (Three Ubuntu VM’s & Home Assistant OS). Any insight would be appreciated!

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.

I’m testing several On-Prem S3 Object Backups ( Backing up Object Storage in 12.1) no matter which of the 4 systems I try I get the attached error. All of the systems have “buckets” that Veeam 12.1 has written to, and they have data in them, and are set as repo’s in VBR that I am using for this test. Suggestions? Error is attached - I get it on all of them. 

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?

I am having trouble accessing the remaining 3 workstations I don't know where they are I only have 4 workstations here. I am here at the VBR.

 👋 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 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

I have VBR installed in Site-B to backup VM under hyper-v and vmware in Site-A.Connection from Site-B to Site-A using ipsec vpn site to site with 2 internet link for redundant.The VPN have same policy for both connections. When the link use primary link then the VBR can backup the VM but if the primary link and connection switched to the backup link then i got error only for Vmware when using backup proxy.I try to ping from the backup proxy in Site-A then the proxy is able to reach HS-W2019.This error mean the backup proxy is not able to connect to the HS-W2K19 on port 2503? Error: Failed to connect to the endpoint [HS-W2K19:2503]. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 

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

Hello,i was trying to register linux server, but certificate file exists.I have deleted /opt/Veeambut still is echo about “File exists” Do you have any hints, where could be located for redhat? I have checked all logs, but cannot find even on VBR or linux itself. Its Veeam 12

Hi, I have a protection group of 8 windows machines.  The machines were added to the protection group using their host names.  The machines get their ip from a DHCP server.  I see that one of the machines, originally with ip 192.168.1.151, is not 192.168.1.155 and is not being backed up.  Is there a way to update the protection group for the new ip?  Unfortunately, I cannot revert back to the original ip because that ip is now being used by another machine (that’s not part of the protection group).