Community

Zero Trust or Bust but Community Trust is a Must! The ransomware avalanche that we have experienced over the last few years has turned most IT people, including Data Protection professionals, into paranoid zero trust fanatics. Everything is viewed through the lens of “beware”. To some this can become overwhelming, after all we humans like to feel safe and comfortable and that requires a trustful environment. So where can we find that comforting trust zone? The community,  that is where!I had the great pleasure of participating in my 4th V100 Summit this November in Prague Czech republic. Veeam is a special company that does something remarkable for its community heroes each year. They bring them together from around the world to share product updates, and gather feedback. Perhaps most importantly they help the community members bond together.I could spend time going over the fantastic sessions and the great content that I was pre

I attended the Veeam Toronto event recently and met some great people there and thought it might be time to join the Community.  Nice to be here and hope to spend some time giving back in the future.  For now, trying to work my way through the Veeam 13 upgrade as it’s the first where I’ve run into a major issue since starting with 9.5.I upgraded VeeamONE, Backup Enterprise, then B&R from 12.3 to 13 yesterday.  I have run into a couple of issues and currently have a support ticket open but thought I would highlight some growing pains here as well as ask if anyone has seen this yet.  The B&R upgrade process went smoothly until I got to the point where I opened the new console.First problem, logged in and console opened fine(after running as Administrator) but I lost access to my Nutanix AHV clusters and backup proxy machines int the backup infrastructure.  I have a mix of AHV and VMware clusters and the VMware side had no issues - my B&R VM and another W

I have three machines, one, an old Windows 10 (22H2 19045.6332) box and two Windows 11 (24H2 26100-6899) boxes.  All are being backed up with nightly incremental and weekly full using the Windows Veeam Agent for Windows Free edition 6.3.2.1302.  Each time a new version of the Agent is released, I install it and create new Recovery Media.Recently, I needed to restore one of the Windows machines, so using Rufus 4.11 and the most recently created Veeam Recovery Media ISO, I created a recovery USB.This USB booted just fine (although it seemed a little slower than other recoveries), but when it got to the initial menu screen, I had no access to either my keyboard or mouse.  I tried re-creating this on both other machines and both had problems; Windows 10 had not network connectivity and the other Windows 11 machine had the same not keyboard, no mouse problem.As I got a warning from Rufus regarding out of date Windows boot files when creating the Win11 USBs, I went ba

Recently, the below Post was created on “Microsoft SQL Server 2025 + Veeam Data Platform = Improved Scalability”​​​.As stated and I quote, ... Microsoft SQL Server 2025 has not yet been validated for the Veeam Data Platform, as it was only made GA on the 18th November 2025, so the information I’m providing here is in preparation for the inevitable support when it’s passed through Veeam’s QA To reiterate, at this time, SQL Server 2025 is not supported yet. This support is inevitabl

Hello, dear community! I am here with another packed newsletter. 🤓 There has been a delay this month as we have been busy planning and executing the Veeam100 Summit at the beginning of the month. In the middle of the month, I was co-organising a local VUG event, so my newsletter have gone slightly out of the standard timing. This one is full of insightful content related to various Veeam products, patches and releases. Take a look for yourself and stay tuned for the November edition, which will be published at the beginning of next month as usual. Veeam Vanguard October Newsletter ​@AndreTheGiant - Veeam beta support for XCP-ng - https://vinfrastructure.

IntroductionThe Veeam Data Platform V13 is now available, and it brings many new features for working with the REST API. With these improvements, it is easier to automate tasks and integrate Veeam into your workflows. Sometimes, it is necessary to check backup data from NAS systems for viruses or similar threats. This helps ensure that the data is safe before being restored or used. Starting with Veeam Backup & Replication 13.0.1, we can trigger an Instant File Share Recovery using the REST API. And why not use a Python script to scan such backup data? There is a Python script for thatThe Python script initiates an Instant File Share Recovery. The backup data is made available to a Windows system, referred to as the mount server. On the Lin

I want to introduce you to another community project I worked on: The Veeam Data Platform Content Pack for Graylog. Graylog is a Security Information and Event Management (SIEM) solution that enables the efficient collection, search, analysis, and alerting of various types of machine-generated data. More details about their products can be found on the official website.Content Pack DescriptionThe first version of the Content Pack enables the visualization of security-relevant events transmitted by Veeam Backup & Replication via Syslog. In addition to a pre-configured Dashboard, further information is extracted from the Syslog data, which allows the ingested data to be analyzed further. For more details about the Content Pack, see

The project announced here became even bigger. However, the Veeam Data Integration API remains the "main actor", except that many new options have now been added, as "my ideas factory" and feedback on a similar script have been incorporated. Let’s look at what’s NEW.📑 SearchThe host2scan parameter scans a selected restore point of the specified host. The repo2scan parameter can display all hosts with supported restore points in the specified Backup Repository. Then select a host and start the scan. NEW Or with repo2scan and the option all to scan the latest restore point for all found and supported host ty

Enabling Multi-Factor Authentication (MFA) or Two-Factor Authentication (2FA) is the best way to protect accounts from password theft or phishing. Therefore it’s recommended to enable such options, when they’re available. Since some time it’s possible to use MFA for Veeam Accounts, which are used to access the my.veeam.com portal or also the Veeam Community 😉Login to your Veeam account at my.veeam.com and click on edit profile in the top right corner.At the bottom of your profile details, you need to click on “Enable MFA”. As a side note, even after enabling MFA this link still states “Enable” instead of “Disable”.

I have a lot of jobs that are getting a new naming convention. The old way to do this was remove from the job from the configuration, modify the folder name on the repository, rename the job, rescan the Repo, then map the back files to the job.   I found there is an updated way to do this and is a welcome feature to save time. To go one step further, it is not recommended to use the remove/rescan method due to the fact the files get new identifiers that cause the restore points to be seen as new data by all tape and cloud storage offload jobs.  To test it, lets create a new job.In my case it’s called “___TEST_NAME_CHANGE” to keep it at the top of my screen.  Next, after running a job, we will click “Disk” on the left to make sure there is a backup on the Repository. It’s similar, but it’s not q

I upgraded my vmware (esxi and vcenter) from v7 to v8. What i do is install esxi8 and vcenter8 then i migrate the vm under v7 to v8.After migrated to v8 i run the existing job and get error, i can see the vm size is 0 in the backup job. Then i remove the exising vm in the backup job and select same vm in vcenter8. The backup job is running but vbr make full backup, likely vbr see this is new vm.How i can retain existing backup chain so when vbr backup same vm but in the different vcenter the vbr will continue by doing incremental backup? 

Dear Community,I would like to ask about the potential impact of Palo Alto XDR installed on our Veeam Backup & Replication v12 infrastructure, specifically on: Veeam Backup Server (Windows 11) Veeam Backup Proxy (Ubuntu) Could you please advise on the following: Does Palo Alto XDR require any exclusions to ensure stable Veeam operations? What specific paths, processes, or services should be excluded on both Windows and Linux components? Are there any known impacts or compatibility considerations when Palo Alto XDR is active on VBR v12? Your guidance would be greatly appreciated to help ensure both security and optimal backup performance.Thank you.

Veeam Data Platform 13 is finally here and fully releasedTo kick things of in my new series of VDP 13 articles, we have the ultimate upgrade guide covering all the major components you will have in your environmentThis guide will cover the upgrade only, keeping VBR/VEM on Windows, I will cover migrating to Linux in a separate article when the process is available to everyoneThe minimum requirements for each component for upgrade isVeeam ONE 12.0.0 VEM 12.3.1 VBR 12.3.1 VRO 7.2.1 Veeam Console 12.3.1Here are some snippets from my article, linked at the bottomVeeam ONE

I understand from our network team, that the SQL agent running on Microsoft SQL 2019 causes the SQL server to lockup or the backups to lockup. Is there a method to configure the backups (data & logs) to prevent that?

Hi thereI have a question around hardened repository. A customer has purchased new hardware to implement a hardened repo and add it to the existing VEEAM setup (latest 12.x).I am trying to determine whether I should suggest to use the VEEAM Hardened ISO. I have downloaded version 2.0.0.8. Or should we stick with using Red Hat and harden that accordingly. My colleagues have done that before and we have the scripts to automate.I am new to the hardened repo game but I would think that using VEEAM iso would be simpler.What are the pro and cons?Also, maybe a silly question but it seems to me that the hardened repo is also built into the V13 virtual appliance ISO. Would it be possible to use v13 hardened repo and connect the repo to a VBR12 setup?Much appreciated.

After a couple of busy weeks with work I was finally able to complete my blog on the V100 Summit in Prague.  Please see below and a link to my blog post where I highlight many of the V100 members.Veeam 100 Summit Recap - Prague 2025  Veeam 100 Summit Recap – Prague 2025 I’d like to first thank Rick Vanover, Madalina Cristil, Nikola Pejková, Safiya Mohamed

HiWe have Fortinet Fortimanager and Fortianalyzer running as VMs. Up until last week, these got backup up absolutely fine. We upgraded these from 7.2.11 to v.7.4.8. Since then, the backups have been marked as suspicous with potential malware activity detected.I’m wondering what is going on. It may just be a coincidence but I don’t believe there is any malware.If I mark the backups as clean, the next backup just gets flagged as suspicious. This only happens on these 2 VMs. All other backups are running fine.  Has anyone come across this sort of issue before? Or am I missing something somewhere?ThanksRoy   

While browsing through Veeam 13 I came across something that truly stuck out: Send me a Daily AI-powered summary of all backup activities!AI-powered summaryNow that is a wish come true! I set the time and impatiently waited in my home lab to see! Sure enough voila!Daily Summary Sometimes it is the little things that make one even more appreciative! 

Hello all, we are looking into SQL Server backup options, we have done a full server and a volume backup also. We see there is a Backup>Application>SQL option, however we cannot see the SQL option in our console….any ideas as we can see Oracle and Mongo available. Thanks in adavance, Tony.

ChallengeWith Hyper-V as well as other hypervisors getting more resonance in the last months for unspoken reasons, we faced several infrastructures running the Azure Local implementation of it.These can easily be backed up by Veeam Backup and Replication. Just like regular Hyper-V clusters. Though, some peculiarities might arise.One of those for us was, that some auto-generated VMs might appear with names like:In one environment, we found >10 of those VMs in the stack. Roles of These VMsAPI Serve

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

VSPC from version 9.0 offers new option how to connect directly VBR and EM (not only via cloud gateways), which is via port 9999/tcp from VBR/VEM → VSPC I have added my Windows VBR, where is installed VEM as well Management Agent could run under local System account or under service account Server is after installation of management agent appeared twice as VBR and VEM is installed on this VM.

Hi everyone,I am delighted to present my first blog post and my first contribution to the Veeam community today. I would be very grateful for any feedback 😊 When working with Veeam Recovery Orchestrator (VRO), you might occasionally run into situations where the system makes decisions that aren’t immediately intuitive. Recently, a partner approached us with a scenario that raised exactly that kind of question: How does VRO choose which backup copy to use when multiple copies exist? Let’s walk through the use case, the unexpected behavior, and what we learned from digging into it. The Scenario In this environment, VRO is running at the disaster recovery site and orchestrating a vSphere-to-vSphere restore plan. The plan uses the following steps:  A backup-to-disk job writes backups to a local backup repository.

Has anyone set up an HA Cluster with Veeam 13 and figured out how to update the SSL for the FQDN that is used when managing a cluster?  When I go to my FQDN the SSL being is used is the Primary Node SSL so the browser shows unsecure.I would have thought this would have been done automagically when setting up the cluster.  Any ideas or thoughts from those that have done this?