News, guidelines and various community projects
Recently active
We have an online event coming up for VUG Canada on October 8th with guests @Pybarra and @MatzeB and including NetApp. Check out to registration link below to register. Hope to see many there.Can’t delete this! Better together with Veeam and NetApp
✦ All of this seem over your head? Ask Claude to help. The GitHub repo ships a ready-made prompt that lets Claude Code ask for your addresses, set up SSH, install the proxy and the Pis, and guide you through the Veeam console: Deploy it with Claude Code →There is no Veeam Agent for ARM. There is, however, a way to give the stock Linux agent a frozen, point-in-time image of a Pi's SD card and let it do what it does best. Here is the full build, end to end, almost entirely from the VBR web console.This started as a weekend puzzle and turned into something I would actually run. I have a couple of Raspberry Pi 4s doing real work: one is a fixed ADS-B flight-tracking ground station, the other rides along in an aircraft. They are cheap, they run for months untouched, and when an SD card finally dies you discover how much configuration lived on it. That is exactly the kind of "small but annoying to rebuild" workload people have scattered across labs, shops and edge sites: signage players, sen
After a failed Veeam backup, a Hyper-V VM (ADCC130HP01) was left with multiple nested Veeam Recovery Checkpoints that cannot be removed.Current situation:4 Recovery Checkpoints are chained together. The oldest Recovery Checkpoint dates back to 06/08/2026. The VM is still running normally. The VM disks currently point to the base VHDX files. Multiple AVHDX files still exist on disk.When attempting to delete the checkpoints from Hyper-V Manager, I receive the following error:"Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Virtual machine failed to generate VHD tree."When attempting removal via PowerShell, I receive:"Cannot delete a checkpoint subtree that contains a recovery checkpoint."I have already tried:Deleting checkpoints from Hyper-V Manager. Deleting checkpoints using PowerShell. Attempting manual merge operations.Has anyone experienced a similar issue and successfully removed these orphaned/chained Veeam Recovery Checkpoints without rebuilding the VM or risking dat
Happy Monday, Veeam Community! 😊Thank you all for voting once again! It looks like we have a winner for this edition! 🎉Congratulations, @kciolek ! Your blog, “Lab: Veeam 13.1 in the Real World: ‘Why Now’ Customers Should Upgrade?”, received 15 votes from our community members.A well-deserved congratulations — and your badge is on its way! Thanks again to everyone who took the time to read, vote, and support our community bloggers. See you next month!
IntroductionThis week I upgraded our internal lab/PoC environment from Veeam 12.3.2 to 13.1. I'd like to share my experience with this upgrade — what worked well, what you should prepare for, and a few things that aren't immediately obvious from the release notes.Here's an overview of our lab/PoC environment:Enterprise Manager (Windows Server 2022) Backup Server (Windows Server 2022) ONE Monitoring (Windows Server 2022) 2x Backup Repositorys, Performance Tier (Windows Server 2022 / HPE ProLiant DL380 Gen10) 2x Backup Repositorys, Performance Tier, used for Backup Copy (Ubuntu Server 24.04 LTS / HPE ProLiant DL380 Gen10)On the virtualization side, we run a full VMware Cloud Foundation 5.1 stack, including the Enterprise Manager integration (Veeam plugin) in VMware Cloud Director.Storage integration is not currently in use, and neither are Veeam backup agents — so this is a pure virtualization backup environment.This setup essentially mirrors our production environments, which made it a
For my fourth blog in my new series which covers both Veeam and Wasabi, I wanted to look at setting up Veeam with Wasabi to go over some of the basics.Blog - Getting Started with Veeam and Wasabi – Step by Step Getting Started with Veeam and Wasabi – Step by Step Wasabi is one of the most popular object storage targets for Veeam deployments, and for good reason — no egress fees, predictable pricing, S3-compatible API, and Veeam Ready certification. If you are not already using Wasabi as part of your backup strategy, this guide will walk you through getting it set up. Why Wasabi for Veeam?Before diving into the configuration, let’s quickly cover why Wasabi is worth considering: Veeam Ready certified — validated for both Object Storage and Object Storage with Immutability No egress fees — restoring your data does not cost you extra (looking at you, AWS) No API call fees above a reasonable threshold S3-compatible — works natively with Veeam’s object storage repository type Object
Well, Episode 3 definitely gave us something to argue about! 😄 And yes, I’m a little late announcing the winners — August was a pretty hectic month for me!Thank you to everyone who jumped into the latest Veeam Oxford Style Debate. We had strong opinions, great technical arguments, and plenty of real-world experience from both sides — exactly what I was hoping for when we started this series.This episode statement was:“Joining your Veeam backup infrastructure (VBR server, proxies, repositories, Enterprise Manager, etc.) to Active Directory is a security mistake.”This was @DChiavari challenge to the community, and I invited him back to review the discussion and help select the winners.And his verdict? Well, even he admitted this one wasn’t easy:“This thread contains so many great insights and valid points, I genuinely struggled to pick a clear winner for each side! The initial statement is (intentionally) quite strong, and I'll be the first to admit that the ‘correct’ answer might be
After updating VBR im having an issue with backups from Nutanix.Jobs finish with errors:9/18/2026 8:01:17 AM Failed : ... : No available worker was foundWhile testing worker getting following errors:9/18/2026 4:00:11 AM Succeeded : Testing the worker WORKERNAME9/18/2026 4:00:12 AM Succeeded : Finished searching for uploaded worker VM images9/18/2026 4:00:49 AM Succeeded : The worker VM was deployed successfully (0:00:37)9/18/2026 4:00:51 AM Succeeded : Configuration settings of the WORKERNAME were synchronized successfully (0:00:02)9/18/2026 4:00:53 AM Succeeded : The worker VM was powered on successfully on the host HOSTNAME (0:00:02)9/18/2026 4:01:16 AM Succeeded : The following IP address was successfully obtained: 10.XXX.XXX.XX (0:00:22)9/18/2026 4:01:16 AM Succeeded : Successfully synchronized updater settings of the worker9/18/2026 4:01:18 AM Succeeded : Local bundle available (0:00:01)9/18/2026 4:06:28 AM Warning : Failed to install the local bundle: Cannot access a closed Strea
This week, we’ve switched things up! 😄 @Rick Vanover is off travelling around LATAM for VeeamON Tours, while I’m finally back home and I’ve brought along two special guests, @coolsport00 and @Karolina Basak .We’ve got some really good conversations lined up, a few different perspectives, and hopefully a lot of fun along the way. So let’s get into it! Featured Content via @SloHachi86 via @Chris.Childerhose via @Michael Melter Vanguard Blog Spotlight - Ben Harmer This week’s Vanguard blog spotlight is @benharmer with Migrating to Proxmox just got easier with Veeam 13.1Special Department Newsvia @tkolstad via @MarcoLuvisi and @Andanet via @MarkBoothman and @Ian Sanderson via @coolsport00 Also sharing some pictures from Veeam User Group Ecuador last week and VeeamON Tour Ecuador 2026 , via @Beto Cardenas , @Christian R , @safiya , @JadaScott
I have a lot of jobs that are getting a new naming convention. The old way to do this was remove from the job from the configuration, modify the folder name on the repository, rename the job, rescan the Repo, then map the back files to the job. I found there is an updated way to do this and is a welcome feature to save time. To go one step further, it is not recommended to use the remove/rescan method due to the fact the files get new identifiers that cause the restore points to be seen as new data by all tape and cloud storage offload jobs. To test it, lets create a new job.In my case it’s called “___TEST_NAME_CHANGE” to keep it at the top of my screen. Next, after running a job, we will click “Disk” on the left to make sure there is a backup on the Repository. It’s similar, but it’s not quite the same screen. 😉 Now, return to the Backup page, right click your Backup job, click edit, and lets rename it. On the Backup Job page you can see it’s been renamed. On the Disk page w
During a recent check on a Veeam Backup & Replication server, I noticed that the folder below had grown to several gigabytes:C:\ProgramData\Veeam\Backup\System\CheckpointRemovalThis can become a problem, especially during Veeam upgrades, where the installer often requires more and more free disk space to complete successfully. What is in this folder?The log files stored in this location are related to offload activities.Unfortunately, Veeam does not currently apply any log retention to this folder, so its size can continue to increase over time. Can these files be deleted?Yes, according to Veeam Support, it is possible to manually delete folders older than 14 days from this directory.That means you can safely clean up old content and recover disk space when needed. Why this mattersIf this folder grows unchecked, it may:consume several GB of disk space, create unnecessary pressure on the system volume, and potentially cause issues when performing Veeam upgrades.A quick cleanup may s
💡 The Challenge:Removing a backup proxy in Veeam Backup & Replication across a lot of backup jobs can be pretty annoying and time-consuming.🚀 The Solution:That's why I wanted to share a short PowerShell script that automates this task for you!I personally use it whenever I decommission a backup repository in large, shared Veeam environments - it's a real time-saver.⚠️ Right now, this script is built for the Windows-based Veeam version (12 & 13).A version for the Linux-based appliance is on my roadmap, so stay tuned!👉 You can grab the script here: 🔗 https://github.com/fabpapde/community/blob/main/veeam/veeam-backup-proxy-remove-v1_0.ps1
veeam console on remote server unable to open when click sign in without any error or activity
One of our recent projects focused on modernizing a customer's data protection strategy, replacing a legacy environment with a resilient and recovery-ready architecture.A key success factor was the ability to reuse the existing physical backup server and LTO tape library from the legacy solution, avoiding additional infrastructure investments and making the project financially viable. This approach enabled the customer to modernize its backup platform while protecting previous investments and accelerating adoption. The ChallengeThe customer was operating with a legacy Arcserve backup solution that presented several operational and business risks.The environment faced a high risk of data loss and limited confidence in backup recoverability. Critical workloads lacked adequate backup coverage, creating protection gaps across the infrastructure. Operational management had become increasingly complex due to manual processes, limited visibility, and the challenges associated with maintaining
For anyone in the community preparing for the CISSP exam, there’s a free group mock exam taking place tomorrow, Saturday, September 19, at 3:00 PM Eastern Time. You can take the full practice exam, get domain-by-domain results, and compare notes with other participants afterward.No subscription is required for the event.Registration: CISSP Mock Exam Day
Hi everyone, sharing this, perhaps it might be useful to others, becasue it uses variables it should just bolt on to anyones’ setup witht he appropriate credentials and smtp relay details. $ErrorActionPreference = 'Stop'#region Configuration$Script:EnterpriseServer = 'https://xxxxxxxxxxxxxx:9398'$Script:User = 'xxxxxxxxxxxxxxxx'$Script:Password = 'xxxxxxxxxxxxxxxx'$Script:Cc = 'xxxxxxxxxxx@domain.com'$Script:ContactsPath = 'C:\Active-Scripts\veeam-contacts.csv'$Script:FromAddress = 'sender@domain.com'$Script:SmtpServer = 'xxxxxxxxxxxx’$Script:SmtpPort = 587$Script:SmtpUser = 'xxxxxxxxxxxxxxxxxxxxxx'$Script:SmtpCredential = New-Object System.Management.Automation.PSCredential( $Script:SmtpUser, (ConvertTo-SecureString 'xxxxxxxxxxxxxxxxxxxxxxxxx’ -AsPlainText -Force))#endregionfunction Get-VeeamEmailStyle { @"<style>body { font-family: Segoe UI, Arial, sans-serif; font-size: 10pt;}table { border-col
Why You Should Integrate Veeam with CrowdStrike Bridging the Gap Between Detection and RecoveryI'm in the process of integrating Veeam with CrowdStrike in my lab, which will be available for customer demos. In this first article, I'll talk about "Why you should integrate," and in the next, we'll walk through the configuration steps for the integration.Most organizations today are investing heavily in security tools to detect threats faster than ever. At the same time, they rely on backups to recover when things go wrong.But here’s the uncomfortable truth:Detection and recovery are still often completely disconnected.That gap is exactly why integrating Veeam with CrowdStrike is becoming a critical part of modern cyber resilience strategies. The Problem: Fast Detection, Slow DecisionsCrowdStrike is incredibly effective at identifying:ransomware behavior lateral movement credential abuse suspicious processesIn many cases, it detects threats within minutes.But once an alert fires, the ques
Recently I faced an interesting issue with a Hyper-V VM backup in Veeam. One specific VM suddenly started failing during checkpoint creation, while all the other VMs in the environment continued to be protected normally.What made the case more interesting was that there was nothing obviously wrong with the affected VM. It was powered on, the operating system was accessible and the applications were working normally. From a production perspective, everything looked fine.However, every backup attempt failed with the following error:Failed to create VM recovery checkpoint (mode: Crash consistent)Checkpoint operation for 'SRV-IA-CONATA' failed.Checkpoint operation for 'SRV-IA-CONATA' was cancelled.'SRV-IA-CONATA' could not initiate a checkpoint operation:Incorrect function. (0x80070001).Error code: '32768'.Retrying snapshot creation attempt(Failed to create production checkpoint.)Unable to allocate processing resources.Error: Failed to create production checkpoint. Finding the real problem
Hi All,Unable to install the veeam agent to a windows server, this was working earlier.The service status is as below on the affected VMPS C:\Windows\system32> Get-Service *Veeam* Status Name DisplayName------ ---- -----------Running VeeamDeploySvc Veeam Installer ServiceStopped VeeamEndpointBa... Veeam Agent for Microsoft WindowsRunning VeeamTransportSvc Veeam Data Mover Service We have killed the msi and veeam services, uninstalled the veeam agents from control panel - cannot find the veeam agent for windows in the control panel though, restarted the server, still the status remains same. Kindly advise.
Hi, We are thrilled to announce the general availability of AsBuiltReport.Veeam.VBR 1.0.0 — a comprehensive PowerShell module that generates professional as-built documentation reports for Veeam Backup & Replication (VBR) infrastructure. What is AsBuiltReport.Veeam.VBR?AsBuiltReport.Veeam.VBR is a specialized report generator that plugs into the AsBuiltReport framework to automatically document your VBR environment. It produces multi-format reports (HTML, Word, Text) that capture the complete state of your backup infrastructure—from backup jobs and repositories to proxies, tape libraries integration, cloud gateways, and more. Key FeaturesReport Sections — Comprehensive coverage of all VBR components including backup repositories, jobs, proxies, WAN accelerators, tape integration, and cloud connectivity Diagram Types — Visual representations of your infrastructure, including backup-to-repository flows, proxy routing, and tape library topology Flexible InfoLevel Configuration — Contr
Please help me with this problemFailed to connect to backup server: Server Veeam Backup Server Certificate certifikate is not trusted
For my third blog in my new series which covers both Veeam and Wasabi, I wanted to look at something new in Wasabi called “Covert Copy”. It is very interesting technology and you can read about it below.Blog #3 - Wasabi Covert Copy – The Invisible Air Gap Your Backups Need Wasabi Covert Copy – The Invisible Air Gap Your Backups Need Ransomware attackers have gotten sophisticated. They do not just encrypt your production data anymore — they go after your backups first. If an attacker can find and destroy your backups, your recovery options disappear. That is the threat Wasabi designed Covert Copy to solve, and it is one of the most interesting data protection features to land in cloud storage in a while. What is Covert Copy? Wasabi Covert Copy is a feature of Wasabi Hot Cloud Storage that creates a locked, hidden copy of a selected S3 bucket. The copy is completely invisible to anyone accessing your Wasabi account through normal means — including authenticated users and, critically, a
Hi Community. I am unable to resolve the above referenced issue. This happened after an update to v13. After the install, it worked for 2-3 days. I then started to configure my tape infrastructure and when I finished, I was prompted to reboot the server. Now I can’t get back into the console. Any help would be greatly appreciated.
I'm using Veeam Backup & Replication Community Edition 13.1.1.18 in a home lab with Veeam Agent for Microsoft Windows 13.1.1.700.I'm seeing extremely poor performance with physical Windows Agent jobs configured as:Server -> Managed by backup server -> Veeam backup repositoryThe problem reproduces on multiple physical Windows PCs.The same machines perform normally when configured as:Server -> Managed by agent -> Shared folderThe difference is enormous.Example managed-by-backup-server test:- Destination was a LOCAL NVMe repository on the VBR server- Approximately 49 GB read- Approximately 30 GB transferred- Duration: approximately 4 hours 16 minutes- Average processing rate: approximately 3 MB/s- Veeam reported Network as approximately 99% of the bottleneckThe transfer frequently drops into the hundreds of KB/s or even tens of KB/s, with occasional short bursts of normal/high throughput.I specifically tested a local NVMe repository to eliminate the NAS/SMB repository path
In Japan, when Anthropic announced Claude Mythos in April, there was an enormous urgency in the Japanese government and the news was everywhere on the media. Finance Minister Satsuki Katayama called it “clear and present danger”. Prime Minister Sanae Takaichi commented that “finding vulnerabilities is a race against time” when she directed her team to “come up with concrete measures and implement them”.Three months have passed since then and nobody seems to talk about Claude Mythos on Japanese media anymore. I searched for related news to update myself. On August 27th a couple of major newspapers reported that Japan’s three megabanks finally gained access to Mythos and started evaluating how to use it. That is how the newspaper article is written, if I translate directly. TV and other media didn’t actively report on it, as far as I am aware.I also searched on English media. There were a lot more updates available, including the info about Project Glasswing. The ones that caught my eye
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.