Recently active topics

Hi all,I am setting up a multi-VM multi-network restore test environment using Surebackup. Our DNS-server is a physical box so I would like to perform name resolution from within the isolated environments towards that physical box - as the resolved IP-addresses would be running inside the isolated environment as well, this should not form any issues.However, I did not find a (supported) way to customize the routing rules on the lab proxy VM, and eventually the egress NAT-rules (for masquerading the DNS-requests) in case I should add them.Any advice is very welcome.Best regards,Jan

Would like to create a local VUG in Texas.Please let me know how to do this?

Salve a tutti e grazie ai partecipanti !Ringraziamo Object First per l’organizzazione dell’evento.Alleghiamo le presentazioni. 

Full disclosure up front: this one isn't a Veeam post. It's a security post, so I hope it earns its spot here.I've been running qwen2.5:14b locally on an M4 Mac mini, and the first thing I wanted to do with it was attack it. The write-up is a reproducible prompt-injection rig, but the actual story is that I got fooled twice by my own scoring. First a keyword matcher, then an LLM-as-judge, and both failed the same way: they couldn't tell a model repeating payload text from a model obeying it. Measuring the attack turned out to be harder than running it.What actually got through, once I had a scorer I trusted:Blunt "ignore your instructions" and fake delimiters worked every single time. The dumbest attack was the most reliable. Obfuscation (base64, ROT13, reversed text) failed across the board. It wouldn't decode-then-obey. A quiet "(developer note: the real instruction is...)" beat a shouty "[ADMIN OVERRIDE, priority 0]", which got called out and refused. Softer social cues are more per

Preface:After some time, I finally managed to continue working on the hardening script and integrate a number of new ideas.This time my approach was slightly different. Besides improving and restructuring the coding style to make the script easier to read and maintain, I also tried to integrate the recommendations from the Veeam Security & Compliance Analyzer directly into the script. The idea behind this was simple: instead of running multiple scripts separately, the hardening script should already cover the most relevant checks and configurations in a single run.From my perspective, this worked out quite well. However, it is still a good idea to run the original Veeam Security & Compliance Analyzer from time to time. The Analyzer also includes checks that go beyond the operating system itself and look at the broader Veeam environment. Those aspects are intentionally not fully replicated in this script, as the focus here remains primarily on operating system hardening for Veea

A critical vulnerability (CVSS 9.8) has been identified in Cisco Catalyst SD-WAN Manager and is confirmed to be actively exploited in the wild. An unauthenticated remote attacker can gain administrative privileges and fully control the SD-WAN infrastructure via the management API. Given the central role of SD-WAN managers, this represents a severe risk to the entire WAN infrastructure. Affected Systems and Versions Affected Product: Cisco Catalyst SD-WAN Manager (formerly vManage) The vulnerability stems from improper handling of the login endpoint (j_security_check), where specially crafted or encoded requests can bypass authentication.Vulnerable Versions: Prior to 20.9: All versions 20.9.x: Versions prior to 20.9.10.1 20.12.x: Versions prior to 20.12.8.2 20.15.x: Versions prior to 20.15.6.1 20.18.x: Versions prior to 20.18.4.1 26.1.x: Versions prior to 26.1.2.1 26.2.x: Versions prior to 26.2.1 Action Items and Recommendations Priority 1: Apply Security Updates Immediatel

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

Hello Community!This is a reminder to join​@jos.maliepaard and myself as we welcome Veeam Legend & Veeam Technical Trainer ​@Michael Melter and Veeam Vanguard ​@Dynamic as they share their recommendations on how best to study & tackle the newly released VMCE+ exam. The webinar is scheduled for 10am EDT this Thursday, 1 Oct. For further information and registration, please follow the link below.Hope you all can join us!

I created this guide a two months ago when VBR 13.0 was release, but only in portuguese in my blog, so I thought I could translate and post here too. :)With the new version 13 of Veeam Backup & Replication, in addition to the new Linux version, new features have also emerged. One of them is the ability to perform Instant Recovery directly to Azure. In previous versions, it was only possible to perform Instant Recovery to vSphere, Hyper-V, or Nutanix, but now we can also restore backups using the Instant Recovery process to Azure. Prerequisites and Limitations Creating the Helper Appliance Template Running Instant Recovery Prerequisites and Limitations As always, there are a few prerequisites for IR to Azure to function correctly. These are:The types of backups supported by IR for Azure are: vSphere backups; Hyper-V backups; Backups of VMs or Physical Machines created with Veeam Agent for Windows or Linux; Nutanix Backups EC2 backups created by Veeam Backup for AWS Azure VM bac

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

We are looking to migrate our 10 vm’s, currently on VMware, to Hyper-V. The host has to be stripped down to bare metal before installing the new hypervisor on it. The plan is to spin up a temporary server on a loaner machine, and migrate our critical VMs to the temp server to continue running our operations during the migration. My question is, how does one take a copy of the critical VM’s, and put them on the temp server if the temp server does not have Veeam or VMware? The temp server will have Hyper-V. Thank you.

Hi all! There are a million Kubernetes tutorials online, and when you are first embarking on your K8s journey, they all start to blur together. I know this firsthand, because I was in that position a few months ago with no idea where to start. So ​@Geoff Burke and I had the idea to create a "Kubernetes Starter Kit". An ordered path, guiding your journey. You can start at step one with zero Kubernetes knowledge, and finish step seven with a running cluster, your own deployments, and backups protecting them. How to use this guideWork the steps in order. Each one builds on the last, so try not to skip ahead. Time commitment: Plan for 20 to 30 hours total if you're starting from zero. Spread over a few weeks at a couple of hours every night, it should be doable.What you'll take away from this: Explain what Kubernetes is and why it exists, read and write a basic manifest, deploy an app to a real cluster, navigate kubectl without a cheat sheet, and back up a workload with Veeam Kasten. Befor

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

Is anyone else  waiting for Veeam support for “Azure Database for PostgreSQL Flexible Server Support” ? It’s been GA since November 2021 and replaced the Single Server which was retired in March 2025, so it seems a bit surprising there is no support to back it up using Veeam, and my support ticket indicated there is no ETA for this feature !This seems a big gap in Azure PaaS support to me. I’d also be interested in any work arounds people have in place. Thanks, Graham 

I enabled EWS via Veeam Data Cloud - and it created a new enterprise that seems to be needed for this task (we did it manually anyway) - but it stays after completion of the task.Can we delete that?BRStephan

Hi,I am kinda new to Veeam Backup. We do have some remote linux hosts without any internal connection to our local infrastructure.Now, to not use the internet directly, I installed Netbird (just like Tailscale) and connected both, the Veeam Server and the Linux Host. That works, all good.Now when I add the Host as Managed Server, the initial SSH Connection works and the Netbird IP is being used but then everything else is trying the WAN IPs which, of course, is not wanted and also blocked. So the Setup never finishes. Does anyone know what I could do here?ThanksAndreas