Blogs and Podcasts

Backups without notifications are like monitoring without alerting: you can live with it—until the day you can’t.Veeam Backup & Replication (VBR) and Veeam Backup Enterprise Manager (VEM) can send automated emails, for example when an event is triggered, like:Job success/warning/failure  Infrastructure warnings Licensing/support notificationsThe goal: you find out about problems as soon as they happen.(And yes: “no news” are also news—but only if you’re sure your email delivery is actually working.) Veeam Doku: E-Mail-Settings & Notifications (VBR v13)https://helpcenter.veeam.com/docs/vbr/userguide/pve_email_settings.html?ver=13VEM Doku: Email-Settings & Notification (v13)https://helpcenter.veeam.com/docs/vbr/em/notifications_ms365.html?ver=13 “Can’t I just enter an SMTP server + username/password and be done with it?” For several years, that was actually the only way—and of course it can still work today. This classic approach is called SMTP server (basic authentication).V

In Part 1, we talked about the difference between reactive and proactive Veeam operations.But knowing the difference is the easy part. The real question is:How do you actually make the transition—without overhauling everything at once?Because most environments can’t just stop and rebuild.They have to evolve.This is how you do it—step by step, without creating more chaos in the process. Step 1: Get Visibility (You Can’t Fix What You Can’t See)Before you change anything, you need a clear picture of where you are.Start with:Job success vs warning vs failure rates Backup job durations (are they increasing?) Repository capacity and growth rate Restore success history (if any exists)The goal:Understand your baseline.Not what you think is happening—what’s actually happening.Proactive operations start with awareness. Step 2: Clean Up the NoiseMost reactive environments have one thing in common:Too many alerts. Too many warnings. Too much noise.Do this next:Review all current warnings Fix what

 Introduction: A Journey That Started with 3-2-1-1-0Five years ago, I published my first Veeam community post about the 3-2-1-1-0 golden backup rule. That post marked the beginning of my journey as a Veeam Legend.Back then, the rule was already considered best practice. Today, it is still relevant — but no longer sufficient on its own.The threat landscape has evolved. So our backup strategies need to follow.The Foundation Still MattersThe 3-2-1-1-0 rule remains the baseline:3 copies of your data 2 different media types 1 offsite copy 1 immutable or air-gapped copy 0 errors (verified recoverability)✔️ This model protects against hardware failure✔️ It addresses human error✔️ It covers traditional disaster scenariosBut here’s the reality:⚠️ Attackers now design their operations specifically to break this model.What Changed? (And Why It Matters)1. Backups Are the First TargetModern ransomware attacks:Target backup servers first Delete or corrupt backup chains Exploit APIs and credentialsBa

 In a recent customer project, I was allowed to perform a new installation of the Veeam Recovery Orchestrator (VRO). The installation itself was initially completely inconspicuous – but on a German-language Windows Server operating system, which later turned out to be a decisive factor.Immediately after the installation, we authorized the local administrator group within the Onboarding-Wizard to access the VRO system. So far, so good. Or so we thought! The result: No user who was a member of the local administrators group was able to log on to the VRO system.  Error: Access denied for the user 'User-within-local-Administrators-Group': the provided credentials are invalid or the user has insufficient privileges.This meant that we were locked out immediately after installation.   Troubleshooting: A look behind the scenesAfter a short analysis, it was clear: We won't get anywhere with the web UI at this point. So we decided without further ado to take a targeted look at VRO's SQL database

Hello, veeamazing community,I am back with another Veeam Vanguard Newsletter packed with tons of great content! Go and check yourself what articles published our veeamazing Vanguards during the month of March!  Across these articles and videos, the authors cover a broad set of Veeam platform operations, security, and community themes: from urgent Veeam Backup & Replication (VBR) patching and remediation of critical CVEs (including guidance to update promptly) to platform upgrade and maintenance tasks such as upgrading embedded PostgreSQL and step-by-step Veeam v13 suite upgrades (Veeam ONE, Enterprise Manager, Recovery Orchestrator, and VBR). Several posts dive into v13 architecture and hardening, including Veeam Software Appliance / VSA customization via config files (instead of Windows registry), port customization concepts, and High Availability with VSA HA cluster setup plus Veeam ONE monitoring using alarms/dashboards and REST API automation. The list also includes practical h

You might have missed it but this week Mr. Cloud Connect published a blog about setting up a test KMS server! Exactly a Month ago I was thinking the same thing and found it to be a world of pain. At the time I tried PyKMIP and Cosmian but had major issues. Then I tried vibe coding a KMS DIY server with my buddy Claude (well at times buddy at others arch enemy!!). I got to the point where Veeam accepted the KMS server but then the job would fail. ​@LDelloca did what folks at his level simply do, forked the old PyKMIP and added the bits and pieces needed! He is not known as Mr. Cloud Connect for nothing, see his blog here: https://www.virtualtothecore.com/fixing-pykmip-for-veeam-integration/My home lab is not big so I try to do everything in containers and for this I looked at his forked github repo and with the help of claude containerized it. THIS IS NOT MEANT FOR PRODUCTION! Just for Lab Learning! Clone Luca’s repo on your podman host: git clone https://github.com/dellock6/pykmip-veea

 1. Two Backup Methods, One Recovery Console Veeam provides two distinct methods for backing up Oracle databases. The first is image-level backup with application-aware processing, where VBR takes a VM-level or agent-level backup and handles Oracle archived redo logs as a guest processing subtask. The second is the Veeam Plug-in for Oracle RMAN, which integrates directly with Oracle's native Recovery Manager and sends backup data to a Veeam repository through the RMAN SBT (System Backup to Tape) interface.Both methods feed into the same recovery tool: Veeam Explorer for Oracle. Explorer can restore databases from either backup type through a single interface. The key difference is what each method captures and what recovery options each enables.  Capability Image-Level Backup RMAN Plug-in Backup scope Entire VM or volume (includes OS, Oracle binaries, database) Database only (data files, control files, archived logs) Point-in-time restore

It was Christmas Eve. Most people were wrapping gifts, winding down, and logging off early. But for one of our clients  a construction company with decades of project data, intellectual property, and live customer records, that night would become one of the most terrifying in the company's history. A double-encryption ransomware attack had just taken down every system. Completely dark. Several other construction companies across the region were affected by the same attack that night. What made this attack different wasn't just its timing. The attackers were sophisticated. They didn't just encrypt the production environment they deleted the on-site Veeam Backup & Replication server, wiped the local backup copies, and went after the cloud backup repository too. I was a deliberate, calculated attempt to leave no recovery path. They almost succeeded. When the Call Came InAs a managed service provider, we know that data emergencies don't respect holidays. The moment we received the aler

   Recently a customer asked me: “Is it actually a problem if I add a branch office with ESXi hosts that are managed by a vCenter to Veeam as standalone hosts instead of adding the vCenter? What impact does that have?” The short answer: Yes, it can have noticeable impact — functionally, operationally, and also in terms of backup consistency when VMs are moving (with vMotion). Best practice in general is to add the vCenter as the management instance in Veeam, not the individual ESXi hosts.  Okay, but why?  What is vCenter — and why is it more than “just” a GUI?  vCenter Server is the central management instance for VMware vSphere environments. It centrally manages objects such as clusters, hosts, VMs, folders, resource pools, tags, roles/permissions, HA/DRS, and many automation features. For backup solutions, vCenter is important because it provides a stable, always up-to-date inventory and object referencing ID (keyword: MoRef).  Moe? Like that bartender from The Simpsons?  Äh no — tha

1. This Is Not Troubleshooting Troubleshooting is what you do when a job fails and you want to fix it. Forensics is what you do when a job has been failing for three weeks and nobody noticed, a VM dropped out of protection and nobody caught it, or a ransomware event hit and you need to prove your last clean restore point. The question is not "how do I fix this job." The question is "what exactly happened, when did it start, what was affected, and can I prove it."Forensics requires a different mindset than break-fix. You are not looking for the current error. You are reconstructing a timeline. You need session history, task-level detail, bottleneck data, and alarm records across a window of days or weeks. VBR stores all of this. The trick is knowing where to look and how to correlate it. 2. Where the Logs Live VBR keeps two categories of evidence: the configuration database (PostgreSQL in v13, formerly SQL Server Express) and the file system logs. Database (Session and Task Records) Eve

 When a full restore is the wrong move When SQL breaks, the first request is usually narrower than “restore the VM.” More often it is “get this database back to before the bad change” or “show me what was in last night’s backup.” That is the sort of job Veeam Explorer for Microsoft SQL Server handles well.It opens a SQL-aware view into a Veeam Backup & Replication restore point and lets you pick the recovery method that fits the problem in front of you: restore a database, recover to a specific time, roll back to just before a bad transaction, publish a database from backup, run instant recovery, or export schema and data without rebuilding an entire machine.If the backup captured SQL correctly, the workflow is familiar whether the source came from a VM backup, Veeam Agent for Windows, or the Veeam Plug-in for Microsoft SQL Server. You can launch the Explorer from the VBR console, from the Windows Start menu, or through PowerShell. Opening the tool is easy. The part that matters is

This is the first article in a multi-part series on From Reactive to Proactive: Running Veeam Like a Platform. In the next article, we'll look at the step-by-step process for completing this. Most Veeam environments don’t start out broken.They start out reactive.Something fails → you fix it.A job warns → you investigate it.Storage fills up → you scramble to add more.And for a while, that works.Until it doesn’t.Because as your environment grows, reactive operations turn into:Constant firefighting Unpredictable performance Unclear recovery expectationsAt some point, you realize:You’re not running a backup tool anymore.You’re running a data protection platform.And platforms need to be operated differently. What “Reactive” Actually Looks LikeMost teams don’t realize they’re reactive—it just feels normal.You check failures after they happen You deal with warnings when they pile up You only look at performance when it’s slow You test restores when someone asksNothing is technically “wrong.”B

  Veeam participated in HPE Tech Jam Orlando 2026 as a Silver Sponsor, reinforcing its strategic alliance with HPE and underscoring its joint commitment to advancing innovation in cyber resilience and data protection.The Veeam team delivered a special breakout session titled “Securing Your Hybrid Cloud with Veeam and HPE”. The session demonstrated how the Veeam Data Platform integrates seamlessly with HPE Private Cloud and storage solutions to protect hybrid environments, covering virtual, physical, and containerized workloads.Attendees of this session explored the expanding HPE and Veeam partnership, which included new support for HPE Morpheus VM Essentials Software and V13 enhancements across backup, recovery, and management.The session also emphasized advanced threat detection, secure recovery, and intelligence-driven insights, enabling organizations to respond to cyberattacks with greater confidence. In addition, the recent acquisition of Securiti AI accelerated the integration of

In recent months, Veeam has been making a series of changes to its certifications. We have changes in the certification model and in the format of the courses and teaching methods. I'll discuss the main changes and alterations on this topic here. Retired CertificationsThe Veeam certification path has always consisted of two levels of knowledge. These are:VMCE (Veeam Certified Engineer) – a technical level focused on operationsVMCA (Veeam Certified Architect) – an advanced level focused on architecture design and project implementationFrom the beginning, this model was very well received by the market and widely adopted. Its success is largely due to the absence of an entry-level (foundation) certification. As a result, the certification exams have always been considered highly challenging; however, the knowledge gained has consistently delivered significant value, enabling rapid career growth and professional development.However, with continuous technological advancements and the evolu

 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 ScenarioIn a virtualization environment made up of multiple clusters, a ransomware attack impacted the environment and made a number of virtual servers unavailable. Fortunately (or thanks to good judgment), only one cluster was affected. ContainmentIn parallel, the entire security team immediately began working to understand the incident a

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 containment—but recovery was where the real difference showed.Instead of panic, we executed a clean re

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 Veeam kb2645. Note: Exiting skips finalization steps that initialize IdentityService config, DB schemas, certs, and token dirs, leaving services “running” but incomplete leaves VBR unusable. Ensures you get the wizard that displays the completion of the upgrade.Veeam

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 Veeam Backup & Replication Version 12.1 and earlier. From Version 12.2 onwards, the checkpoint removal is an independent task and can be processed in the background contineously.Separating the removal task from the backup job was a good update to help reduce the object storage loads.Even if you receive th

 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 layout options: per-VM backup chains (one backup file chain per VM) and per-job backup chains (one backup file chain for the entire

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 expectIf you haven’t tested restores, you’re still guessing.What you should be testing:Full VM restores File-level recovery Application item restores (SQL, AD, email) Instant Recovery performance

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 Veeam VSA HA Cluster provides redundancy for your Veeam Backup & Replication environment by pairing a primary and secondary node. If the primary node fails, the secondary automatically takes over, maintainin

  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 containment measures. All impacted systems were powered off to prevent further propagation.At that point, a **war room** was established, and we moved into a structured incident response process:-Detection & Analysis-Containment-

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 protected VM’s data changes. Therefore, if the checkpoint is left there for a longer period, the size may become large enough to negatively impact the performance of th

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.Core services were unreachable.Critical systems were effectively offline.And the worst part?We didn’t imme

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?).