Community

 Today, March 31, is World Backup Day. This date exists because, even today, I still see many companies continuing to lose critical data. In the vast majority of cases, these losses are not related to a lack of technology, but rather to strategy and process failures, and especially to an underestimation of risk.And these risks are not limited to lost files or servers with software issues. They involve systemic failures in operations, security, and even architecture. Real CaseI will cover a real case I went through recently, where I will share more details not only about the problem, but also about how it was possible to recover from the disaster. The Scenario

It started as a routine alert—unusual login activity flagged by our monitoring system. Within minutes, multiple backup jobs began failing, and that’s when we knew: this wasn’t random—it was targeted.The attacker had gained access using compromised credentials and was attempting something we’ve all seen becoming more common—destroy the backups first before encrypting production systems.But this time, things didn’t go as planned.Our backup environment was built with immutability and zero-trust principles using Veeam Backup & Replication integrated with hardened repositories. Even though the attacker had access to certain systems, they couldn’t modify or delete backup data due to immutable storage policies.While the security team contained the breach, we verified the backup integrity.Everything was intact.A few production workloads were still impacted—some files were encrypted before contain

This blog post was inspired by an excellent article that explores recovery scenarios beyond the typical restoration approaches often covered.In-place upgrades represent the standard and vendor-recommended approach for advancing Veeam Backup & Replication (VBR) to newer releases, ensuring continuity of configuration, and retention of job etc without requiring a full reinstallation. But without a test lab, you are essentially performing a high-wire act. While everyone talks about restoring data during “World Backup Day”, few share stories of how protecting the protector. Veeam’s own configuration backup can literally rescue your Veeam Backup and Replication (VBR) when an upgrade goes sideways. You can take a look at this

When I try to restore from HV guest using “Copy To” option, choose a folder and the “OK” button is greyed out. I used to use this function all the time on this server before I upgraded to 13.01. Any ideas?

Some of Hyper-V VM have Veeam recovery Checkpoint. The backup job is running successfull every day but why seem veeam not delete this checkpoint? I tried to remove this but there no option to delete this checkpoint.   

This is the English version of a selected article from Climb Japan Engineer Blog series. When you use Veeam Backup & Replication to process a backup or backup copy to be saved in the object storage such as Amazon S3, there might be a case where you receive the alert message below.Subject: [Warning] Background checkpoint removal. Backup server: <your Veeam server name>Body text: Failed to remove checkpoints from the backup repository <your repository name>This alert is issued when obsolete checkpoint (i.e. restore point) removal process on the object storage where backup data are stored has been failed.Removal of such checkpoints has been a part of the backup job in

I'm really happy to share with the Veeam Community the release of vScan 2.0, a complete rebuild of the vulnerability scanner for Veeam Backup & Replication.For those who don't know vScan, you can check the original post here: vScan v1 – Vulnerability Assessment in your Veeam BackupsSince the v1 release, I received amazing feedback from the community (thank you all!) and many feature requests. Instead of patching v1, I decided to rebuild the entire application from scratch with a completely new architecture, new features, and addressing all the questions and requests from the community. What Changed from v1 to v2?

 1. Why Job Design Matters Anybody can create a backup job. Open the wizard, add VMs, pick a repository, set a schedule, click finish. The job runs. The question is whether it runs well at scale, whether it makes SureBackup testing practical, whether it handles application consistency correctly, and whether it does not create operational headaches six months from now when the environment has grown.Job design is the difference between a backup environment that runs itself and one that requires constant intervention. Bad job design produces jobs that run too long, compete for proxy and repository resources, break application log chains, make restore operations slow, and make SureBackup configurations a nightmare. This article covers the patterns that work and the anti-patterns that do not. 2. Per-VM Backup Chains vs Per-Job Chains VBR offers two backup file l

The veeam backup version is patched to 13.0.1.2067 after that few proxy servers are not getting updated. Failed to upgrade host components. Error: 'The process cannot access the file because it is being used by another process. Failed to invoke rpc command  (The process cannot access the file because it is being used by another process.) (Failed to invoke rpc command)' (0:00:10) 

I’ve installed Veeam Backup & Recovery 12 on a Windows 11 device (it used to have Veeam installed and was working fine but accidentally got removed, we’re not sure what version).It was used to backup a Esxi Linux VMI’ve setup a computer and a VM backup job but neither complete with a message ‘failed to perform backup policy operation.The only messages I see in the login relates to Disposed or retry are not supported.Some fixes relate to restating the veeam backup service...but i see no backup service and even when i run the MSI, there are no errors after installing as account prompted by default.Any suggestions?Thanks

Hello,Updating the windows console to 13.0.1.2067 is systematically failing with the error “Failed to update the backup console: Failed to deliver update specification to backup server.”I’am using a VSA - current build 13.0.1.2067Even when downloading directly the 13.0.1.2067 ISO, i get the same issueAnyone had the same problem and could fix it ?RgdsJIhad

Immutable backups are one of the best things to happen to data protection.They’ve become the go-to answer for ransomware resilience—and for good reason:Backups can’t be deleted They can’t be modified Attackers can’t encrypt themThat’s a huge win.But here’s the part that doesn’t get said enough:    Immutability is a layer of protection—not a complete strategy.I’ve seen environments check the “immutable” box and assume they’re covered.They’re not.Because when something actually goes wrong, immutability alone doesn’t guarantee you can recover cleanly, quickly, or safely.Let’s talk about what else you actually need. 1. Recovery Testing (Because “Protected” Doesn’t Mean “Recoverable”)You can have perfectly immutable backups that are:Corrupted Incomplete Misconfigured Or just… not usable the way you expect

As a follow-up to my previous blog on the VSA HA Clustering setup, I decided to do a companion blog about using Veeam ONE for monitoring.  Check it out below and link to my blog.Monitoring Your Veeam VSA HA Cluster with Veeam ONE Monitoring Your Veeam VSA HA Cluster with Veeam ONE Getting visibility into your Veeam VSA High Availability (HA) Cluster is critical for ensuring backup continuity. Veeam ONE provides the dashboards, alarms, and reporting you need to stay ahead of issues before they impact your recovery objectives. This post walks through configuring Veeam ONE to effectively monitor your VSA HA Cluster — from initial connection through tuning alarm thresholds and automating the whole thing with PowerShell via the Veeam ONE REST API.What Is the Veeam VSA HA Cluster?The

The copy backup jobs (secondary target) for two of physical server backup jobs are generating two emails per backup instead of one.  For each backup copy job run,  two “Success” emails within minutes:Example:11:05 PM – Success 11:07 PM – Success    Subjects are identical,  EnvironmentProduct: Veeam Backup & Replication 13.0.1.2067 Workload: Veeam Agent for Windows (Physical Servers) Jobs impacted: Physical Servers 7PM Daily Copy to Archive Physical Servers 7PM Daily Copy to Immutable Physical Servers 10PM Daily Copy to Archive Physical Servers 10PM Daily Copy to Immutable

  World Backup Day is often treated as a reminder—a checklist item to verify that backups exist, are recent, and are recoverable. But for those of us working in infrastructure and disaster recovery, it represents something much more concrete: the difference between operational continuity and complete outage. This is not a theoretical discussion. This is a real incident.This is my experienceThe Incident: Ransomware at ScaleRecently, I was involved in managing a critical ransomware attack that impacted a large virtualized environment. After an initial assessment, it became clear that we were dealing with a full-scale ransomware infection.Roughly “150 virtual machines” in a VMware environment were affected. The situation escalated quickly, requiring immediate containmen

Hi everyone, We plan to integrate Veeam Backup and Replication with our SIEM as part of our security hardening. I would like guidance on the best way to forward Veeam logs and events to a SIEM platform. Looking for advice on supported methods, required settings, and any best practices or limitations.

This is the English version of a selected article from Climb Japan Engineer Blog series.-----Veeam Backup & Replication enables the agentless protection of Hyper-V virtual machines. In order to maintain the data integrity of Hyper-V VMs, when you process a Veeam backup, a temporary Hyper-V checkpoint is automatically created and it is then deleted when the data capture is completed.However, in some exceptional situations, e.g. as a result of antivirus software interference, the checkpoint may remain on the protected VM. In that case, you might see the remaining checkpoint named “Veeam Recovery Checkpoint (XXXX)” on the Hyper-V Manager screen as below. The red marked section shows the remaining checkpoint. Note the UI is in Japanese.The Hyper-V checkpoint size may increase as time goes by, because it will reflect the p

While working in a lab with multiple silos, minimal change control, and backup processes in place, not everyone informs the backup administrator of new servers or devices added to the infrastructure that require backups. As the backup administrator, it's my responsibility to ensure that all servers have a reliable backup and can be restored in the event of a disaster. I make that extra effort so that, in situations like the one below, we can get everything back online in a timely manner.It was an early normal Monday morning, and I was reviewing the weekend backups when a Teams call came in from our Network Lead for the lab.When the Network Goes QuietAt first, a few users reported they couldn’t access shared drives.Then applications started timing out.Then monitoring lit up.Within minutes, it was clear:    We weren’t dealing with a slow network.    We were dealing with a broken one.

What could be the issue? Failed to send certificate, but certificate is required for remote agent management Error:

Hi Community,Has anyone successfully reverted Veeam ONE from version 13 to version 12? Are there recommended steps or considerations to avoid issues during the downgrade? Any official guidance or lessons learned would be greatly appreciated.

Was working today doing some tape stuff and when testing my PowerShell script to create GFS pools noticed that when you go into the Advanced settings for the Daily, Weekly, etc. section of the pool properties you see two monthly and no quarterly.I have logged this on the Forums as a potential bug but wanted to give a heads-up as it is just cosmetic, mainly the main page for the retention options shows Quarterly proper (which I thought they were removing?). 

Здравствуйте, я установил новую версию системы резервного копирования на чистую операционную систему. Внутри всё работает нормально, но после перезагрузки в системном журнале Windows появляются ошибки.DCOM не смог установить связь с компьютером 10.10.20.118, используя ни один из настроенных протоколов; запрос был отправлен PID 2bd0 (C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Manager.exe) при активации CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}. svc.V eeamBackup.log   Ошибка (1) в Veeam.Backup.Core.Common.CHost.Get(Guid hostId, IDbMethodsInterceptorBase db) [03.04.2026 16:03:28.224] <37> Ошибка (1) в Veeam.Backup.Core.Common.CHost.Get(Guid hostId) [03.04.2026 16:03:28.224] <37> Ошибка (1) в Veeam.Backup.ResourceScanner.CGateRepoConnectResource.CreateByResourceOptions(CResourceScanInfo info, IDBManager dbManager) [03.04.2026 16:03:28.224] <37> Ошибка (1) в Veeam.Backup.ResourceScanner.SResourceFac

Hi all, I wanted to share the new Veeam Ports MCP server with the community. This gives you the ability to interact with the Veeam Ports underlying database to create rich designs using LLM clients that support MCP, like Claude and VS Code.https://github.com/shapedthought/veeam-ports-mcpTo install in Claude:Install Python Install UV Run: claude mcp add veeam-ports -- uvx veeam-ports-mcp Update your Claude desktop configuration file: