News, guidelines and various community projects
Recently active
Please help, We are trying to backup large number of laptops, ± 400 using 1 proxy server to backup to S3 type of storage. We are experiencing performance issues. Laptops are using wi fi to connect to the cooperate network. We used a CSV file to configure protection group and our backup are scheduled during working hours. Please advise on the way forward for the best practice or recommendations.
I have a migration from Veeam on Windows to Veeam on Linux, and I need to make sure there are no problems after the migration
I'm getting in my own way right now.I've set up an organization in Veeam M365. I want to edit it, but when I go to the connection settings, I'm asked for the application ID and a certificate.Which certificate should I select here? Veeam only suggests three options:1. Self-Service Patch Certificate2. Restful API3. (without friendly name) I didn’t have to specify a certificate during setup; I just followed the wizard.How can i choose the correct certificate?Maybe I'm just being stupid today.
I hear it all the time: my customers are looking for a backup solution they can set and forget, basically run itself. This article will focus on that - every backup solution needs to be monitored and troubleshoot issues. “Set it and forget it.”It sounds like the dream.You deploy your backup platform, configure your jobs, see everything turn green… and move on to the next project.No noise.No issues.No need to touch it.Until something goes wrong. The Illusion of “Everything Is Fine”In a lot of environments, backups quietly run in the background.Jobs complete Reports look clean Storage is filling (as expected… mostly)So naturally, attention shifts elsewhere.That’s the trap.Because backup environments don’t usually fail loudly at first.They drift. What “Set It and Forget It” Actually Looks Like Over TimeIt doesn’t break on Day 1.It slowly turns into:Jobs that run longer than they used to Warnings that get ignored (“it’s just a warning”) Storage growing faster than expected New workloads ad
Air-gapping your backups sounds simple in theory:“Just isolate them so nothing can touch them.”But in practice?That’s where things get tricky.Because the moment you start locking things down too aggressively, you risk:Breaking backup jobs Slowing down restores Creating operational headaches Or worse—making recovery harder when you actually need itI’ve seen environments go too far:Backups fully isolated… but unusable Processes so manual they never get tested Security so tight it blocks recovery workflowsThat’s not resilience. That’s friction.So let’s talk about how to air-gap Veeam the right way—without breaking operations. First: What “Air-Gap” Actually MeansAir-gap doesn’t have to mean physically unplugged (although it can).In modern environments, it usually means:Logical isolation Controlled access Separation from production riskThe goal isn’t to make backups unreachable.The goal is to make them untouchable by attackers—while still usable by you. The Core PrincipleBackups should be e
Hi since upgrading my PVe to version 9.1 and the VBR to 13, the backup performance have degraded a lot. We have 1 worker per pve host, storage is Ceph. Did someone encounter this issue?
Hi,I am going over DR scenarios and have a query on improving our procedure.We have two sitesPrimary site Hosts all production servers (5x physical & 30ish virtual) Hosts the VSA virtual server Primary & immutable storage repositories Secondary DR Site Off-site storage repository 2x spare physical servers for use in DR scenarioBoth sites connected via VPN. Everything on Hyper-V Now my query - lets say the primary site is destroyed. We want to restore everything to the secondary site.First step I can’t login to Veeam console because it was hosted in the primary site. Therefore current procedure is to setup a new instance of VSA and import a backup of the config. Not a difficult task but it takes time which I’d rather not have to spend during an emergency scenario.Is there a better way? Does it make sense to replicate our VSA virtual machine to the secondary site? Maybe high availability? Or should we be hosting the VSA virtual machine at the secondary DR site with a proxy server
TL,DRIf a VMware VM has Virtualization Based Security (VBS) enabled, SureBackup can fail with “Invalid change tracker error code” during snapshot creation. The underlying cause is that SureBackup, by default, modifies the VMX and disables Virtual Hardware Assisted Virtualization (VHV) by setting vhv.enable to false, but VBS requires VHV. The fix is documented in KB4003: SureBackup for VM With VBS Enabled Fails With “Invalid change tracker error code” and boils down to creating a registry value on the Veeam Backup Server so SureBackup stops flipping vhv.enable. The symptomA SureBackup job in one of our customer environments tests multiple VMs, and suddenly one VM consistently fails with:An error occurred while taking a snapshot: Invalid change tracker error code:[25.02.2026 16:47:34.391] <17> Info (3) [SureBackup] [SQL 2022] [RegisterVm] > VmRef = vm-469403[25.02.2026 16:47:34.391] <17> Error (3) [SVmWareCtkHelper] Failed to disable CTK on VM, Ref: VmRef
Are there anything besides the tape that need to be preserved before removing the old tape library? What are the steps to add the new tape library?https://helpcenter.veeam.com/docs/backup/vsphere/connecting_tape_devices.html?ver=120Following this the drive will automatically appear and how about the media? If the tapes are added to the tape library they will automatically appear in the media.Last step will be to create a Tape job
Currently you can only restrict the Server-Scope for File-Restore not for the whole application. So whenever you want to give an user any role more privledged than “Restore-Operator”, you cannot fully restrict the scope of servers he see in the Jobs or Server Tab...
After upgrading to Veeam 13 on Windows, I am unable to login with UI console. Access throw WEB conole works.
Hi All,As I checked the release notes for the Veeam Agent for Linux that supported most of Oracle Linux 8 versions but when I tried to install the agent I’ve got this error below :2/18/2024 3:24:09 PM Failed [172.17.2.207] Failed to install veeam-6.1.0.1498-1.el8.x86_64.rpm, veeam-libs-6.1.0.1498-1.x86_64.rpm and veeamsnap-6.1.0.1498-1.noarch.rpm packages: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command 0:08:012/18/2024 3:32:10 PM Failed [172.17.2.207] Failed to install Veeam Agent for Linux: error: open of kernel-uek-devel-5.15.0-3.60.5.1.el8uek.x86_64 failed: No such file or directory Failed to invoke rpc command Can somebody let me know why I’ve got this as what I am looking for is using Oracle RMAN backup via Veeam Backup and Replication using Agent and Oracle Plugin Appreciate your help Thanks
Normal circumstances this week! I’m happy to host @Madi.Cristil for this week’s recap where we cover a full block of content categories this week. Watch this week’s episode here: Featured Contentvia @Andreas Buhlmann via @Nico Losschaert 👀Welcome Back! 👀via @matheusgiovanini Vanguard Blog Spotlight - Petr BouškaThis week’s Vanguard Blog Spotlight comes from @Samuraj with a recent post: Veeam ONE Reporting Service did not start due to missing certificate. Special Department Newsvia VUG South Africa (2x!)via @Madi.Cristil - Congratulations @Mohamed Ali, @matheusgiovanini and @wolff.mateus Be sure to join this amazing upcoming Veeam 100 Show featuring @stevennew, @Rin, @Madi.Cristil and @safiya Who's NewThank you @safiya for prepping the Who’s New this week! We are pleased to welcome +151 new members. The coolest usernam@Began, @GrzECHO, @DoctorA and @tigerlinux. Alfred’s pick is @BlueyBoy → you have a badge coming your way. Have a great weekend everyone!
Veeam Community Hackathon banner. Alfred is sitting in the middle of a desk. He is about to press the run button with his paw. Binary code and a slider are shown on the left of Alfred. In the middle, the word Hackathon is shown with arrowed lines pointing to icons and text describing several aspects of the Hackathon: Development, Brainstorm, Time, Presenting, Goal, Teamwork, and Community.🚀 Join the 4th Annual Veeam Community Hackathon (2026)!We’re excited to announce that the Veeam Community Hackathon 2026 kicks off on October 7, 2026 at 15:00 CEST / 9:00 AM EST — and registrations are now open! 👉 Sign up here: https://my.veeamhackathon.com⏳ Sign-ups close on September 30, 23:59 CEST / 5:59 PM EST 🌍 What is it about?This is a global, community-driven event where teams of 12–18 participants collaborate to build innovative solutions that enhance and complement existing Veeam products.💡 Your mission:Create something that makes life easier for end users — whether that’s a dashboard, t
Is Surebackups Virtual Lab on the to do list to work with Proxmox?
Hi teamI am tasked with implementing new repositories and I have to move backups and backup copy created by AHV. It seems that moving AHV backups is not supported with VEEAM move feature.I wonder what the best options are here and what I need to be aware off?The existing repo are configured to not use per machine-machine backup files.The old repos will be decommissioned once all data has been migratedMuch appreciated
Question : What is the process to retrieving configuration backup from the Veeam Software Appliance [VSA] default repository and restoring them to a different VSA? for context looking at the bash shell of the VSA. the configuration backup files are stored inside following volume./var/lib/backup/VeeamConfigBackup/<servername>/Example:
With this post I want to highlight the community again as we held our 1st in-person Veeam User Group event in Cologne yesterday. This was a curious one for us, because it was the first time we rotated and went way north in Germany and leave our sweet South and Southwest spot. However, it turned out we almost had 60 in-person attendees and only 4 no show attendees which is a huge success and the biggest success in our eyes. This means the Veeam community is really working, people love to attend the VUGs and get together. We couldn’t be more proud !A HUGE THANK YOU to our sponsor Scality who made sure we can have such an amazing venue, food, catering, a barista (!) and drinks throughout the day. A simple amazing effort which we highly appreciate ! Furthermore a huge thank you to Veeam, especially to everyone who supports the Veeam Usergroup behind the scenes. We also had a massive representation from the german Veeam100 people which is always a blessing to see !Special thanks also go out
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 a folder structure based on GUIDs. If you've ever opened your S3 bucket or Azure container and looked inside, you'll see something like this:Veeam/Back
hi While running a demo for a customer i was trying to add a new Org into my VBO serverWe come across this error message around config Exchange Web Services (EWS), I’ve personal not seen this message before when adding an new ORG. However this the 1st time I’ve tried adding an org into version VBO 8.3, for context i’m using Modern authentication. Error messageproduct version
When running self-hosted applications in a homelab or on-premises environment, HTTPS is often the first thing to fall through the cracks. Self-signed certificates trigger browser warnings, and public certificate authorities like Let's Encrypt require your services to be internet-accessible. The solution? Run your own internal Certificate Authority.However, this is not a difficult problem to solve. Just setup an internal PKI using Step CA running as a rootless Podman container, then extend it to issue certificates for services on your network. In this first part, we'll focus entirely on getting Step CA up and running — initializing the CA, configuring automated certificate issuance, and setting up a systemd timer to handle renewals without any manual intervention.Create a new podman network for step-capodman network create ca-servicespodman network lsCreate a CA volume and Quadlet (quadlets are the preferred method for starting Podman containers:podman volume create step-camkdir -p ~/.c
With the High Availability feature in Veeam Software Appliance 13.0.1, Veeam provides a neat way to make the backup server highly available. In this blog post I’ll briefly show how to configure HA, which prerequisites must be met, and what alternatives exist if HA cannot be used. Intro - The Basics The feature itself reduces downtime of the backup server in the Veeam Software Appliance. In general, two nodes are required; they can synchronize even across relatively high latencies. A manual switchover is possible, and a major advantage is automatic updates for both nodes. The goal is to offer fast disaster recovery without the need to keep a dedicated standby backup server, and then finally to restore the configuration backup. (https://helpcenter.veeam.com/docs/vbr/userguide/high_availability_hiw.html?ver=13) Requirements The following components are required for this feature: Two Veeam Software Appliances At minimum, Veeam Data Platform — Premium licensing (the package that includes
In the final article of this three-part series, we’ll explore how proactive operations with Veeam can help organizations reduce downtime and enhance data protection.By the time you reach this point, things feel different.You’re no longer chasing failures.You’re no longer guessing recovery times.You’re not constantly reacting to alerts.Instead, your Veeam environment starts to feel… predictable.That’s the goal.But scaling proactive operations isn’t just doing the same things on a bigger environment.It’s about operating with intention, consistency, and confidence—no matter how large things get.This is what that actually looks like in practice. 1. Health Is Measured, Not AssumedAt scale, you don’t rely on “it looks fine.”You rely on metrics and trends.What you know at any given time:Job success and warning rates Backup window utilization Repository performance and latency Growth trends across all storage tiersThe difference:You’re not asking:“Are backups okay?”You already know.Because you
First of all — a big thank you to everyone who shared their stories. The quality, honesty, and real-life moments behind them made this campaign something special. It’s clear backups really do save the day 💚After counting all the votes and engagement across platforms, here are our winners 👇1st place – (Community vote- 30 votes) @Mohamed Ali with The Night Everything Burned - And the Christmas Miracle That Saved 18TB - World Backup Day — $150 gift card 2nd place –(LinkedIn love- 215 likes ) @matheusgiovanini with 50TB Encrypted Over Carnival — How Instant Recovery Saved a $1M Operation - World Backup Day — $100 gift card 3rd place - (Community Hub engagement- 17 likes) @wolff.mateus with World Backup Day 2026 and the Day After an Attack - $50 gift card Congrats to the winners — and honestly, to everyone who participated. Every story was a great reminder of why what we do matters.Let’s keep celebrating the real heroes behind the scenes… backups 💚
Microsoft BitLocker Administration and Monitoring (MBAM) and Advanced Group Policy Management (AGPM), both part of the Microsoft Desktop Optimization Pack (MDOP), have officially reached end of support as of 14 April 2026 (today). From this point forward, Microsoft will no longer provide security updates, bug fixes, or compatibility assurances for these tools, similar to the lifecycle outcome observed with Microsoft Deployment Toolkit (MDT).Organizations that continue to rely on MBAM and AGPM must now assess risk exposure, validate operational dependencies, and define a transition strategy toward supported alternatives to maintain security, compliance, and long-term manageability.To help you transition away from MBAM and AGPM, I have outlined practical and supported alternatives in the following guides. These articles provide a deeper dive into modern solutions and implementation approaches you can adopt moving forward.https://techdirectarchive.com/2026/04/14/agmp-extended-support-ends
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.