Community

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

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.

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! 

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

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?

 It's already 3 weeks after my first journey to this summit in Prague. I was on several summits, but this is completely different. Everybody knows each other very close after an year or who was first time, they knew few months virtually from community. like me. And now was the time, when we met together and everybody was happy to met me personally like we have been seen previously. It was was nice talk with everybody from community. Of course, was really great to meet Veeam management and to talk with them about my design and requirements and what could be improved and how. For me was like Christmas time, like a family meeting during Christmas.If we look on box, on swag pack, it was like Xmas gift :) Lot of nice merches. The meetings were very fruitful for me, what we can use for resilience data now and what is comi

Virtualization technology has become an integral part of modern IT infrastructures. It provides incredible flexibility, scalability, and cost-efficiency to businesses of all sizes.Since several hypervisor platforms have gained significant traction in recent years, including Proxmox VE, XCP-ng, and Nutanix AHV etc. As business needs continue to evolve, the choice of virtualization platform must remain equally adaptive. Thereby, aligning performance, scalability, and management capabilities with changing organizational and technological demandsMigrating from one hypervisor to another is a complex process that requires careful planning and evaluation. Organizations must consider factors such as application dependencies, migration timelines, workload criticality, and the potential business impact of application downtime. PrerequisiteIf you fail to install the VirtIO drivers as recommended, you may also encounter issues s

The Veeam Software Appliance v13 brings a new level of simplicity, security, and efficiency to modern data-protection workflows. Built on a hardened Linux foundation and designed for fast, consistent deployments, the VSA is an excellent option for organizations seeking a streamlined, appliance-based approach to Veeam Backup & Replication.In this guide, I provide a practical overview of how to configure the Veeam Software Appliance v13 and highlight the main features that make this version stand out. Why VSA v13 Is a Major Step ForwardSecurity by DesignVSA v13 was built with a strong security focus from the very first boot. It includes: A minimal Linux operating system, drastically reducing the attack surface SELinux in strict mode, providing advanced policy enforcement SSH disabled by default, preventing unnecessary access paths With these

My journey with Veeam began in 2020, right in the middle of the pandemic, a time filled with uncertainty, challenges, and a lot of learning. Troubleshooting and analysis weren’t easy at first, but something quickly stood out to me: the Veeam Community.A space where experienced professionals shared knowledge generously and newcomers like me could grow by learning from real-world experiences. I started quietly, absorbing everything I could, and eventually felt the desire to give back. Helping others who faced the same difficulties I once did became a natural part of my routine.One moment that really moved my story forward was when Christian invited me to write posts for his blog. That opportunity boosted my confidence, helped me grow faster, and brought me closer to community members I deeply admired, including the Veeam 100, which slowly became a personal dream.Coming from the

Dear Community Members,We are currently running Veeam Backup & Replication v12.3.2.4165 and considering an upgrade to v13.Our environment includes GCP workloads and a GCP appliance integrated with VBR. Will the GCP appliance remain fully compatible and function as expected after upgrading to v13? 

Hi all,I've written and tested a PowerShell script to harden a standalone Windows Server 2025 machine running Veeam Backup & Replication, based on the CIS Benchmarks (Level 1 & 2). I’m sharing it here in case it helps others — feedback is welcome!What the Script DoesThis script configures the server securely without breaking core Veeam functionality. It includes: Account Policies: Max password age, complexity, and lockout thresholds (CIS 1.1.x, 1.2.x) Guest & Anonymous Access: Disabled for better baseline security Audit Policy: Enabled for all major categories (CIS 17.x) Unneeded Services: Disabled (safe defaults — e.g., Print Spooler, Xbox services) Windows Defender: Hardened settings with MAPS Advanced, PUA protection, etc.

Hi All,If we keep our Veeam VBR on V12.3.2.4165 and we upgrade the Veeam backup for AWS appliance from V9 to V10 what has integration with this VBR. Will that break the integration. Is there only integration with VBR V13?I did request this question in a case and got the following answer backRegarding Veeam Backup for AWS, upgrading from version 9.1.0.45 to version 10 will not impact integration with VBR 12.3.2.4165. There are no documented version dependencies or incompatibilities between these specific versions.However on a Reddit forum I found a topic where customers told that the upgrade did break the connection with there VBR on V12.3.2.4165Veeam Backup for AWS 10 : r/VeeamOr is there a newer version of the plugin that repairs this connection if it gets broken.Cou

Customer has Wasabi for M365 backups -- needs to migrate to on-premise S3-compatible storage -- what is the best and fastest (if not the same) options do I have

I try to migrate my vmware VM to hyper-v using veeam and i always got ‘failed to modify disks”. Anyone know how to fix this? 

Object First OOTBI (Out-of-the-Box Immutability) is a purpose-built, secure, and immutable backup storage solution engineered specifically for Veeam Backup & Replication. By combining storage performance, immutability, and simplicity, OOTBI helps IT teams achieve reliable data protection while reducing operational overhead.Also, OOTBI eliminates the complexity associated with traditional backup storage by offering an appliance that you can deploy, configure, and integrate with Veeam in minutes. Below are some article relating to Object First OOTBI.Steps to configure Object First OOTBI Appliance | Veeam Community Resource Hub Enable Honeypot on Object Fir

Hi everybody, currently we’re working with a customer who has build already 5yrs of retention with AvePoint. Migrating the backupchain from one to another product is in most cases not possible. Is anybody aware of the existence of ‘standby’ licenses where the customer pays less but has the ability to restore for a certain period without adding new points ? This gives him then the time to build op the retention on Veeam Backup for M365. It would be nice if we could create here a list of products / vendors who have such and option. (mostly not public available on their website) Then we can already now during onboarding what route we have to go.

I have been using BackBlaze for cloud storage for about 5 years with Veeam12. I am now moving to Veeam 13 and want to attach to a new bucket. I created the bucket and attached to BB using a new application key. The problem I am having is when I got to ‘Select Folder’ I can see the bucket but cannot list any folders under the bucket. Since I cannot list the folders I cannot select a folder which means I cannot continue. There are no errors generated. Any ideas aside from open a support ticket?