Blogs and Podcasts

There are so many data-breach incidents reported by news media day after day in Japan. Ransomware incidents seem to be increasing as well, although we do not hear about them as often as data-breach incidents. Maybe they have become so common and no longer considered newsworthy.Having said that, there was a new incident just reported on October 7th and it appears to be a special case. The first report was about Ibaraki Prefecture municipal office and municipal police websites closure due to IDCF Cloud service outage. The IDCF Cloud is run by Softbank subsidiary IDC Frontier, which then announced that a part of their system was compromised. Later, more details were announced that IDCF Cloud’s East Japan Region 1 was down due to a ransomware attack, which impacted 495 organizations throughout Japan.According to public information on the IDC Frontier website, IDCF Cloud service’s East Japan Region 1 uses VMware ESXi / vCenter, suggesting the ransomware targeted that specific deployment, th

During a recent Veeam Agent for Windows deployment project, we found an interesting issue involving VSS, SQL Writer, and old SQL Server references left behind after an incomplete removal or previous intervention.The scenario looked simple at first: a new backup project using VBR, Windows servers, and workstations protected by Veeam Agent. The agent deployment was successful, the jobs were configured, and everything was going according to plan.However, two specific servers started failing during the snapshot stage.At first, it looked like another common VSS issue. But after a deeper investigation, we found that the root cause was related to old SQL Server references pointing to files that no longer existed on the server. The environmentThe environment included: VBR; Veeam Agent for Windows; Windows Server 2025; Servers with SQL-related components; Jobs configured for protection through Veeam Agent. An important detail in this scenario is that the job was not initially configured

This week will take a small break from Wasabi related things and check out replication for Proxmox VE.  Check out blog #6 below.Blog - Veeam 13.1 and Proxmox VE – Native Replication is Here Veeam 13.1 and Proxmox VE – Native Replication is Here The post-Broadcom VMware licensing situation has driven a real migration toward alternative hypervisors, and Proxmox VE has been one of the biggest beneficiaries. Veeam has clearly been watching these trends, because version 13.1 delivers something Proxmox users have been waiting for: native VM replication.This is not just a backup story anymore. Proxmox is now a first-class citizen in Veeam’s disaster recovery capabilities. What’s New for Proxmox in 13.1?  Veeam already had Proxmox VE support for backup and recovery. Version 13.1 extends this with: Native VM replication — create Proxmox VM replicas for near-instant failover Instant Recovery — spin up VMs directly from backup storage without waiting for a full restore Unified management — ma

Every environment has a system that everyone knows is old, but nobody can simply turn off.During a new Veeam Data Platform 13 deployment, I reached one of those systems: an Oracle 10g database running in a Solaris zone. It held almost 48 TiB of data and supported core applications and services used across a worldwide company.The customer knew it needed to be modernized. They also estimated that replacing or migrating the applications and databases around it would cost millions of dollars. That project wasn’t going to happen before we needed a reliable backup.The backup job wouldn’t completeMy initial plan was to protect the Oracle workload as part of the new Veeam deployment. The jobs failed, so I started troubleshooting them like any other failed backup.Eventually, the support requirements gave me the answer. The Veeam Plug-In for Oracle RMAN supports Oracle Database 11g Release 2 and newer; Oracle 10g isn’t listed. Solaris 10 is listed as a supported operating system for the standalo

Today was release the Veeam Backup & Replication. The process of upgrading or updating a Veeam Software Appliance (VSA) is straightforward and performed via the web interface. One of the advantages of using the VSA is that you do not need to manually manage packages and dependencies within the operating system, as the appliance itself handles the update lifecycle.Despite how easy it is, I will show you here how to perform the upgrade procedure. Navigation and Checking for Updates Access the Host Management Console interface of your Veeam Software Appliance. In the left-hand menu, click the Updates button.This screen will show available updates; you can select the Veeam Backup & Replication option and click the Install Updates Now button. Configuration Check and Details Now we need to check some details and look if it have any compatability issues:Installation Process The wizard will take over and automatically begin downloading and applying the packages. A progress bar displayi

Hello Veeam community! 😊VDC recently added a new capability to send events from the Control Plane and Microsoft 365 to SIEM platforms (with Entra ID coming soon as well).Today, it supports Splunk and CrowdStrike, but there is also a 3rd connector that opens the door to many more possibilities: the Generic Webhook connector. 🤩And of course… that gave some ideas, right? As a big Grafana fan, I started wondering: could we use this webhook to send VDC events into Grafana and build a dedicated dashboard?So, et voilà guys… I built it in my lab. 😄I used my usual monitoring stack: Telegraf → InfluxDB → GrafanaThe full setup, configuration, and all the steps are available in my latest blog article: https://home.point4.fr/monitoring-vdc-using-grafana/And just to give you a small preview, here is what the final dashboard looks like.Of course, I’m also sharing the Grafana JSON dashboard file, so you don’t have to start from scratch. 😉Hope you enjoy it!❤️ to this community. 

IntroductionCloud is not always the most cost-effective solution for every workload.We recently worked with a customer who was experiencing increasing costs in Microsoft Azure. The customer was running approximately 40 virtual machines (VMs) in Azure, and as the environment continued to grow, so did the monthly operational costs.The primary goal of the project was straightforward:Reduce the customer's infrastructure costs without compromising availability, security, backup, or future scalability.After evaluating several alternatives, we concluded that moving the workloads from Azure to a dedicated on-premises environment hosted in our data center provided the best long-term financial outcome.Evaluating the OptionsWe looked at several possible solutions: Continue hosting the environment in Azure Host the infrastructure with a third-party provider Rent rack space in a data center, including power and cooling Deploy the infrastructure at the customer's own location After comparing t

 I ran into a situation recently where one of our VSPC servers stopped working after a Windows patch update. The portal was dead. I went ahead and upgraded to VSPC 9.2 and that brought everything back online. Except the April license usage report never got generated. It was stuck. I could not finalize it or submit it. If you are using VCSP /w rental licensing, you know that the report has to go to Veeam every month. A missing one is not something you can just ignore (Not for lack of trying 😊). I opened a support case and Veeam Support gave me a procedure to regenerate the report. It worked. I am documenting it here because I could not find this written up anywhere and I know other providers might encounter something similar. Step 1. Back up the VSPC SQL database.Take a fresh backup of the VSPC database first. Veeam covers this in KB1471. If the SQL work later goes bad you want something clean to restore. Step 2. Update the configuration overrides file.Open this file on your VSPC serve

 Heads up: this plug-in is upcoming and not GA. What's shown is a pre-release build and may change before it ships. If you want to get ahead of it, reach out to your Everpure team.I recorded a quick walkthrough of the upcoming Everpure (formerly Pure Storage) plug-in for Veeam Backup & Replication 13.1. It does two things: it supports 13.1 on both Windows and the Linux-based Veeam Software Appliance (VSA), and it takes advantage of the Fusion fleet-wide management built into every Everpure array. I focused on the VSA.What's in the demo:Install on the VSA. In Host Management, go to Logs and Services > Components and add the plug-in bundle. A Windows executable covers Windows installs. Hardened by design. The VSA's Security Officer role keeps separation of duties. Pair that with SafeMode and MFA on the array for layered security. Backup from storage snapshots, on by default. As long as your proxies can reach the storage over iSCSI, NFS or Fibre Channel, jobs process VMs with stora

Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and then zip the files into a single large Zip file. 2) Create an IIS server website with all update files needed for the VSA. Then we can easily hand-carry the Zip files from the internet-connected Windows computer to the IIS server in the OT/dark site/closed environment with you pre

Here's a short one from the field that might save you some troubleshooting time. The setupWe had an unmanaged Oracle RMAN plug-in on SUSE Linux. It ran fine for a long time under VBR 13.0.2 and earlier with the matching plug-in version. We upgraded VBR to 13.1.1.18 and then updated the plug-in. The 13.1 plug-in also needs a new OpenSSL package, so we installed that and checked it as well. Everything looked clean. The problemAfter the upgrade, the RMAN backups failed. The plug-in could no longer talk to the backup server properly.Nothing in the upgrade documentation suggested any further step was needed, so we opened a support case. What changed under the hoodWe compared the plug-in's veeam_config.xml from before and after the upgrade:The stored VBR fingerprint changed from a 40-character value (SHA-1 length) to a 64-character value (SHA-256 length). The encrypted passwords (VBR user and Oracle DB credentials) are stored in a different format afterwards.So the ciphers and hashing behind

🖱️ Your mouse cursor disappears inside the Veeam Backup & Replication console?You are not alone. Some customers since yesterday, several constellations, all on the current 13.1.1.18. Veeam Support sees the same across versions and suspects Edge / WebView2.What worked for us:✅ Update Edge, taskkill /F /IM msedgewebview2.exe and restart the console. Cursor back.If you cannot update or wait yet:🛠️ Registry: HKCU\Software\Microsoft\Avalon.Graphics → DisableHWAcceleration (REG_DWORD) = 1, restart the console. That switches off WPF hardware acceleration for the whole user profile, so test first.🧯 Or work in the Web UI (if possible).Open a support case if it hits you. Volume helps root cause analysis.🔗 R&D Thread: https://forums.veeam.com/viewtopic.php?p=575041 

With the Veeam Software Appliance and the Veeam Infrastructure Appliance, update distribution is fundamentally changing. The Veeam Appliances automatically install certain updates to ensure security and operational continuity. This represents a massive increase in security and compliance. What is updated?Operating system and security updates are installed centrally and automatically, cannot be deselected, and are mandatory for both appliances. Security updates for Veeam Backup & Replication are also installed automatically and without user intervention to ensure security.Both appliances can also optionally install feature and bug fix updates automatically, provided this is enabled in the configuration. Major updates (e.g., V14.0), minor releases (e.g., 13.x), and private fixes are optional by default.Here is a simplified overview:Mandatory updatesVeeam cumulative & security updates (e.g., 13.0.x) Operating system security updatesOptional updatesMinor product updates (e.g., 13.x

Now we move on to blog #5 and this time I am discussing the 3-2-1-1-0 rule using Veeam & Wasabi.Blog post - Building a 3-2-1-1-0 Backup Strategy with Veeam 13.1 and Wasabi Building a 3-2-1-1-0 Backup Strategy with Veeam 13.1 and Wasabi The classic 3-2-1 backup rule has been the gold standard in data protection for years: 3 copies of data, on 2 different media types, with 1 offsite copy. It is solid advice, but the ransomware landscape has pushed the industry toward a stronger version: 3-2-1-1-0.Let’s break down what that means and how to implement it practically with Veeam 13.1 and Wasabi. The 3-2-1-1-0 Rule Explained 3 — Maintain at least three copies of your data 2 — Store copies on at least two different types of media 1 — Keep at least one copy offsite 1 — Keep at least one copy offline, air-gapped, or immutable 0 — Zero errors after automated backup verification  The additions to the classic rule — the second “1” and the “0” — reflect the reality of modern threats. Ran

An Introduction to RDMA for S3 One of the biggest challenges customers and partners bring to me is how to get their backups written to object storage faster. That challenge is only magnified when they’re pushing hundreds of terabytes of backup data into their object storage repositories every day. In most cases the bottleneck isn’t the disks, especially if the object storage is backed by SSD/flash. The culprit is most likely the TCP/IP network stack used to move data from the backup server to the object storage target. Every object written over HTTPS pays a TCP/IP penalty in CPU cycles, memory copies, and latency, and those penalties really become apparent when high volumes of backup data are being transferred during the backup window.When we started our object storage journey with Veeam Backup & Replication (VBR) v9.5.4 back in early 2019, we expected object storage to become the predominant platform for secondary storage and it has. Adoption of object storage repositories has cli