Blogs and Podcasts

When performing an Instant VM Recovery from VMware backup of RHEL VM to Nutanix AHV. The RHEL VM failed to boot up. Please follow the steps to install the VirtIO drivers into the RHEL VM. Not all Linux VMs require this process, in most cases this isn't necessary.  Initiated IVMR from VMware Backup of RHEL VM to AHV.Instant VM Recovery Process2. Noticed the RHEL VM did not boot up see screen below.EFI Boot Failure ScreenI went into RHEL VM and followed the steps in this Nutanix KB article link below to add VirtIO drivers. I then rebooted the VM. I took another incremental backup. Caution, please make sure you have a good backup before proceeding.https://portal.nutanix.com/page/documents/kbs/details?targetId=kA032000000TTizCAG  root@linux# dracut --add-drivers "virtio_scsi virtio_pci" -f -v /boot/initramfs-`uname -r`.img `uname -r`I reran the Instant VM Recovery with the latest incremental point and the VM booted. I then migrated VM over to production. It was completed successfully.Migra

Hello Team, Can anyone help, am trying to upgrade VeeamOne env from 12.0.0.2498 to VeeamONE_12.0.1.2591_20230314, am unable to upgrade as it shows license is invalid. Could you please help path to download trial license for VeeamONE_12.0.1.2591_20230314.  

Every year, more companies migrate their backup architecture to object storage. The promise is well-known: scalability, predictable cost, and an extra layer of resilience against ransomware. But with so many providers available, one of them has been gaining significant traction — Wasabi Hot Cloud Storage. Wasabi's value proposition is refreshingly simple: S3-compatible storage, high performance, no cold tiers, predictable pricing, and full support for Object Lock, enabling true immutable backups. In this article, I share the full experience of building a protection scenario using Veeam Agent Standalone + Wasabi, walking through:creating a bucket configuring permissions integrating Veeam with Wasabi running the first backup validating immutability restoring a full machine into a hypervisor performing granular file-level recovery And I’d like to leave a special thanks to the Wasabi team, who generously provided a trial environment that made all these tests, and ultimately this article, p

On September 26, 2024, Pure Storage and Rubrik announced a partnership “to arm global customers with a proven reference architecture to ensure uptime and a path forward in the face of growing cyber threats”.  And while the press releases, blogs, data sheets and even the white paper (see Resources) have all the right Cyber Resilience key buzz words, there is nothing new, or that interesting, from a product integration and solution perspective.What was announced?“a three-layered defense strategy” which includes:Layer 1 - Rapid Recovery – recovery from Pure Storage FlashArray storage snapshots, using Pure’s recovery tools Layer 2 - Data Security – separately, from Rubrik with their Secure Vault appliance and from Pure with FlashArray SafeMode-enabled immutable storage snapshots Layer 3 - Archival Location – long-term retention on Pure Storage FlashBlade object storage How does that compare?Pure Storage and Veeam have more valuable and deeper storage snapshot integration and solutions that

WebLAPS is a web-based solution for managing Microsoft Local Administrator Password Solution (LAPS). Below are some articles that have been previously shared with the community on Windows LAPS. Also, ​@Michael Melter discussed LAPS as mentioned in the article below, and I recommend you take a look at it for added knowledge which is not covered in this article.  WebLAPS could be used to implement just-in-time administration (JITA) approach recommended by MS when accounts of system administrators are added to privileged groups for defined period of time and automatically removed after. Please refer to the official documentation for more information. Also, here is how to configure Windows LAPS with Microsoft Intune as well. This article targets users that are still using the legacy Microsoft LAPS and not the Windows LAPS. Microsoft recommends that customers begin planning on how to migrate their Windows LAPS-capable systems from using legacy Microsoft LAPS. Microsoft LAPS product is depre

Are you planning to build Veeam 13 environment on appliances only? Veeam 13 offers backup environment via appliances. VBR and VEM via VSA appliance and proxy with gateway servers via VIA appliance. Hmm, probably you need to consider windows component in backup environment. Of course if you are planning functionality of backup environment like:FLR for Windows Server Application backup  Guest Interaction Proxy (gMSA) Item-level Restore  FLR for Windows ServerIt is needed to define Windows “Mount Server” for repository for usecases:VMware replication job with Re-IP rules Instant Recovery of  Microsoft Windows workloads Instant Disk Recovery for Microsoft Windows workloads Application item restore Secure restore for workloads with ReFS volumes Scan Backup for workloads with ReFS volumes SureBackup Guest OS file restore for Microsoft Windows workloads with ReFS volumes, or from workloads with data deduplication enabled for some volumes  Guest Interaction Proxy Based on KB you can use:appli

 Upgrading Veeam ONE from version 12 to version 13 introduces significant architectural and security improvements, including changes to authentication and communication methods. Version 13 moves away from legacy protocols such as NTLM and WMI in favor of more secure and modern approaches like Kerberos and gRPC as discussed below.Note: There is a strong business and technical need to upgrade to Veeam ONE v13 in order to leverage Veeam Intelligence, enhanced analytics, and next-generation dashboard capabilities that improve visibility, reporting, and operational decision-making as shown below. For the detailed blogpost, please see https://techdirectarchive.com/2026/05/26/how-to-upgrade-veeam-one-from-v12-to-v13/The guide highlights the upgrade best practices, and important lessons learned from real-world upgrade scenarios to help ensure a smooth and stable transition to Veeam ONE v13 in your own environment.If you are upgrading an isolated (workgroup-based) environment, this architectura

With the release of Veeam Software Appliance and JeOS, deployment processes have become significantly more streamlined. In Europe, the prevalence of multiple languages naturally results in a variety of keyboard layouts, such as Azerty for French users, Qwertz for German users, and a Danish variant of Qwerty to accommodate specific characters like Å, Æ, and Ø. However, the rapid installation process does not provide the opportunity to configure keyboard settings during setup.There is, however, an effective solution. JeOS is an optimised and secure edition of Rocky Linux, and its installation is managed through an automated kickstart script. Settings such as keyboard layout, timezone, timesource, and network configuration are all specified within this script. To ensure every installation includes your preferred configurations, you can update or remaster the ISO and integrate these settings directly. For this purpose, I have developed a custom script, ksmod.py, which is available at https

 Importantly, administrators are responsible for enabling and configuring the fencing mechanism after cluster deployment. Without the fencing configuration, node remediation and VM restarts will not happen as expected. In virtualized environments, high availability (HA) is essential to keep workloads running even when a node fails. In OpenShift Virtualization, HA leverages Kubernetes-native mechanisms combined with OpenShift’s self-healing infrastructure.A key element is fencing, the process of isolating a failed node to prevent issues like split-brain—a scenario where nodes lose communication but continue running independently, causing data inconsistencies and conflicts.When a node goes down, restarting virtual machines (VMs) happens in three phases: Failure detection – Identifying that a node has stopped responding. Fencing – Ensuring the failed node is safely isolated with no active workloads. Remediation – Restarting affected VMs on a healthy node. Through this approach, OpenSh

In this article, we’ll explore why backup validation matters and how you can validate backup integrity using Veeam Backup & Replication.A question I always ask customers. Do you test your backups? The answer I get is I don’t have the time or the resources. So, how do you know if the backup is good? Well, it's successful. A successful backup isn't always effective and should be tested periodically. Veeam can help validate the backups.Backups are often considered the last line of defense in any data protection strategy. However, a backup that cannot be restored is effectively useless. Many organizations invest heavily in backup infrastructure but overlook one critical aspect: backup validation.With modern cyber threats, ransomware attacks, and increasing data volumes, verifying the integrity of backups is essential. Fortunately, Veeam provides built-in mechanisms to ensure that backups are not only created successfully but can also be restored when needed. Why Backup Validation Matte

Cloud adoption continues to increase as organisations are either taking their first steps into the cloud, or progressing their IT strategies, whether it’s a full cloud migration, multi-cloud or delivering a hybrid architecture.A great workload to leverage the cloud has been as a backup repository. By using the cloud, we can meet multiple improvements to our 3-2-1-1-0 minimum strategy for backups. In case you aren’t familiar with the 3-2-1-1-0 strategy, it is:3 copies of data, across 2 different backup media types, 1 of which must be off-site to the production environment, 1 backup at least must be offline or “immutable”, with 0 backup validation errors. Security BoundariesOne threat that the 3-2-1-1-0 strategy doesn’t cover explicitly is the concept of security boundaries. It is entirely possible to achieve all 3-2-1-1-0 objectives purely within your own environment, or exclusively within a single cloud, but there are problems with either approach, as we’ll look into now. Internally Ma

OverviewI was recently working with a customer on migrating some Rocky Linux VMs running on vSphere hosts to some Hyper-V hosts using Veeam Backup and Replication.  After the migration to Hyper VM, the customer received the following error when the VM tried to boot. The issue is that the VM can’t boot in Hyper-V because it is having trouble finding the boot image and mounting the root file system. On further inspection, it was discovered that the Linux VM was missing the required Hyper-V drivers.  Windows-based VMs do not run into this issue as they already have the required drivers available at boot. Before Veeam can boot a migrated Rocky Linux VM in Hyper-V, the Rocky OS needs to have the proper Hyper-V drivers installed in the intramfs.img. Once the Hyper-V drivers are added to the initramfs.img the VM can boot and function correctly in the Hyper-V environment.    This issue can be fixed after the VM is migrated by booting it to a Live CD and then adding the drivers. Veeam KB 2669—h

VMware Tools is a set of services and modules that enable several features in VMware products for better management of guests operating systems and seamless user interactions with them. VMware Tools has the ability to pass messages from the host operating system to the guest operating system. Therefore, VMware Tools is a suite of utilities that enhances the performance of the virtual machine guest operating system and improves the management of the virtual machine. Without VMware Tools installed in your guest operating system, guest performance lacks important functionality. Installing VMware Tools improves these issues low video resolution, inadequate color depth, incorrect display of network speed, restricted movement of the mouse, inability to copy and paste and drag and drop files, missing sound, and provides the ability to take quiesced snapshots of the guest OS, and synchronises the time in the guest operating system with the time on the host Impacted ProductVMware Tools for Wind

Hi, How can I add backup repository (Linux hardened) to Veeam office 365 backup?

VM networking was much simpler. In VMware, there is a lot of planning when managing the network. You create virtual switches per host and assign properties like MTU size, VLAN, etc and pair those with physical NICs. You setup VMkernel NICs with specific roles to control host traffic. With Scale computing, you set a native VLAN on the physical switches and use standard VLAN Trunking to the host. You assign an IP on the management network which uses the default VLAN and then tag VMs on their virtual NICs directly, skipping all the complex concepts of a vSwitch. A separate Linux bridge with different physical NICs or a subinterface with a VLAN is used for the cluster backplane used for storage and inter-node cluster communication depending on how many NICs the host has. If a VM needs to be on multiple networks, you can assign one NIC with a certain VLAN, and another NIC with a different VLAN. You can also choose not to tag at the port and let the guest OS setup VLAN tagging, similar to as

Alt Text: Header Image with the text “In the Lab With: Veeam”, subheading “Breaking the Consolidaiton/Merge Stalemate For VMware vSphere & Microsoft Hyper-V”Have you ever seen a snapshot/checkpoint fail to merge? Maybe VMware vSphere was telling you that a virtual machine required consolidation, or Microsoft Hyper-V reported that the checkpoint couldn’t be merged. Whatever the reason, it’s a painful situation.Or should I say, it’s a painful situation, ONCE you notice! And IF you don’t, you have a disaster approaching. Why Snapshots/Checkpoints are bad in the long-term If you need bringing up to speed as to why we don’t like snapshots/checkpoints sticking around, here’s the non-exhaustive, good to know key points:Snapshots/Checkpoints make the original virtual disk a read-only file, and all changes from the snapshot/checkpoint creation point forwards are saved to a ‘delta’ virtual disk. This will consume more storage space. Snapshots/Checkpoints cause increased IO penalties, reducin

I recently started playing around with Power Automate after a team member asked me to share the status of a daily backup job in a Teams chat. I tried to use Teams' "Get Channel Email" function, however it appears the organization has blocked that functionality. Perhaps they don't want channels filled with emails, and prefer us to use native alerting interfaces. I was left with the only option of using Power Automate, or "Workflows" in teams. I started with a simple template to forward emails to a chat, filtered it by subject line of that job's email report, and saved the workflow. This made me wonder what else Power Automate could be used for. Given my renewed goal to participate actively in the Veeam Community, I decided to start there. The Goals:Receive all notifications from the Veeam Community into a chat within Microsoft Teams Trim the content down to include only the user, and the message preview Removing the image at the top of each email Removing "Hi Tommy O'Shea," Removing a

Hi thereToday, I want to share with you all a technology/partner that caught my eye at VeeamOn 2025 in San Diego, CA.Have you ever wondered how to «enforce» or «protect» your Veeam Windows Setup, with local / presented Storage, without modifying or adding Appliances/devices to your Infrastructure?Here is where Blocky comes into Play.The Only Ransomware Protection That Runs on the Veeam Windows Server.Blocky installs and runs directly on Windows-based Veeam Backup & Replication (VBR) servers—securing backup jobs at the source without requiring added hardware, Linux, or infrastructure changes.Blocky hardens the Windows VBR against ransomware threats by transforming the ReFS and NTFS volumes into a zero-trust, Write Once Read Many (WORM) volume.This creates robust ransomware protection for Veeam backup volumes without disrupting operations.Another important aspect is that the learning curve is relatively easy to learn/manage.No extra Hardware/tech needed, and no modifications (or big

HPE has released a new Tech Brief outlining how Veeam Backup & Replication protects HPE VM Essentials environments. This document provides key details on Veeam’s agent-based backup approach and how it integrates with HPE VM Essentials to ensure secure data protection.📄 Read the full Tech Brief here: HPE Tech Brief - Using Veeam to Protect HPE VM EssentialsThe Tech Brief covers:✅ How Veeam Backup & Replication secures HPE VM Essentials workloads✅ Functional testing conducted by HPE and Veeam engineers✅ The role of Veeam Agents in protecting HPE VM Essentials VMs✅ Automating backup tasks using Veeam Protection GroupsIf you’re working with HPE VM Essentials or selling it to customers, this resource provides an overview of how Veeam fits into the environment. Check it out for the full breakdown.For more background on HPE VM Essentials and how Veeam protects it, check out these related blog posts:📌 Navigating HPE VM Essentials Part 1: What is it and how to protect it with Veeam📌

When it comes to sizing a new Backup environment or just new repository server, one metric that is always asked is the daily change rate. You can also see in the most popular - unofficial - Veeam sizer:https://rps.dewin.me/ https://rps.dewin.me/rpc/      Even with VeeamONE it was not simple to get this information easily for VMs and physical machines. This gap was closed with the version v11a of Veeam ONE. The previous report named VM Change Rate History was replaced by the new Data Change Rate History. Fortunately not just the name changed, it also gets some new features!What's new in report configurationIncludes Agent backups. Now these job-types are supported: VM Backup Replication Agent Backup   You can select the base of change rate calculation: Data transferred or read.   What's new in the report itselfIncludes a nice graph for change rate history - for VM and agent data. Includes daily change rate. In Summary In detail - per machine   This is a great help for siz

Hi everyone!I had a case during this week, and I wanted to share my experience / workaround with y’all.I wanted to export a backup to an external drive, the VBR was a virtual machine, and no access to the Hypervisor to plug the USB and push it to the vm.Now you may think, mount it somewhere and share it over the network as a shared folder…I did, and was not working, some windows stuff that we were not allowed to share any unit, and was driving us crazy!We did some research, and remembered that there was a way to share / mount remote USB Devices over the Network! now, time to give it a shot!The idea is very straight forward, a Server machine, where the USB Devices is located at, and a client, to mount the remote resource as “local”.The tool name is VIRTUALHEREUSB SERVER(Local USB Drive)→NETWORK→USB CLIENT“Remotely mounted USB Drive”You simply download the Server and client, and execute them in the decided machines, couple of easy configs, and you are good to go, let me show you some scr

Or: How to renovate your backup house without setting the roof on fire  Some customers have already taken a good look at the new Veeam v13.x release and its features, but for various reasons they are still running VBR v12.3. And honestly, there is nothing wrong with that. It is actually pretty normal in the IT Business.We all know the situation: A vendor releases a new major version. You nod approvingly, read through the first feature lists, maybe watch a webinar or two, and then think: “Yes, we’ll do that. Soon. Very soon. After the change freeze. After vacation. After the audit. When we have time again.” The problem is: At some point, “soon” needs to become an actual date.According to the Veeam Product Lifecycle Matrix, Veeam Backup & Replication v12 currently reaches the end of support and security fixes in February 2027. In plain English:From March 2027 onward, no production environment should still be running on v12.Unsupported and unpatched software solutions are unpopular fo

In my continuation from my first blog post which can be found here - Cybersecurity Month - Blog #1 I now present blog #2 which deals with the same Synology C2 Object Storage but this time using it with Veeam B&R for offiste.Synology C2 Object Storage with Veeam Backup Synology C2 Object Storage with Veeam Backup This will be my second article in the continuation of Cyber Security Month. This one uses Synology C2 Object Storage with Veeam Backup & Replication as a target repository. I have tested many providers over the years with Veeam, and this one is just as easy to set up as most of the other S3-compatible storage vendors.You first launch your Veeam Console, go under Backup Infrastructure, and click on Backup Repositories. From here, you will add a new repository, which must be S3 Compatible. The screenshots below show the process of adding the Synology C2 Object Storage to my Veeam Console.S3 Compatibility – adding using Veeam Console wizard –Configuration of the S3 Object

As a backup professional, I often present alongside partners, addressing key concerns in data protection. One of the most frequent questions I encounter is: How can we determine if there’s an issue with a backup or if it’s infected? This is where I highlight a standout feature of Veeam—Secure Restore—demonstrating its critical role in maintaining data integrity.What is Veeam Secure Restore?Veeam Secure Restore allows organizations to scan restore points using antivirus software and YARA rules before restoring them to the production environment. This proactive approach ensures that data is not only recoverable but also safe from potential threats.Supported OperationsSecure Restore is available for a range of operations, including:Instant Recovery Instant Disk Recovery Virtual Disks Restore Entire VM Restore Restores to Microsoft Azure Restores to Amazon EC2 Restores to Google Compute Engine Disk ExportImportant ConsiderationsPlatform Limitation: Secure Restore is only available for Micr

 Why this guide? A while back, a customer asked me for a simple step-by-step guide for restoring the Veeam Backup & Replication configuration onto a newly deployed Veeam Software Appliance. This write-up is the result. It has been a little while since then (as you can tell from the version used, 13.0.1) - but since I haven't found a similar step-by-step guide here in the Community Hub yet, this one is for you. I am well aware that most of the steps here are self-explanatory for all of us, and that most of you could get through this configuration blindfolded. My customer, however, asked for a truly foolproof guide - something to provide a rough direction in a worst-case scenario. That said, should it ever come to that, we will of course be supporting them anyway...And finally, the customer also receives a checklist to document the individual steps - you will find it at the end of this guide.  VBR / Veeam Backup Server Configuration Restore  If the entire Veeam VBR intelligence is no