News, guidelines and various community projects
Recently active
Hi,I’m working with MongoDB backups, and everything was going well until the restoration part.I was able to test all the restore options except: Restoring multiple collections to a point in time Publishing the instance I’m not sure why these two aren’t working. Has anyone faced the same issue before?
I’m facing an Active Directory security audit, and the account used for the backup job generate a discussion.If i’m correct the account used must me member of builtin\administrator group, and the security team do not like at all that the password is set as never expire.i’ve already implemented that the account cannot be used for interactive login, but it is not considered “enough”So i’m trying to echange my posture without breaking the restore functionality, and i’m evaluating several option:The Veeam Server in in a workgroup and in a segmented network.1) do not do application aware and use only the vmware tools.it seem that the backup of AD is done in a correct wayPS C:\Windows\system32> repadmin /showbackupRepadmin: running command /showbackup against full DC localhostLoc.USN Originating DSA Org.USN Org.Time/Date Ver Attribute======= =============== ========= ============= === =========DC=DomainDnsZones,DC=intrane
Today, I built a new Veeam environment using Veeam Backup & Replication 13.1 with oVirt KVM Plugin 13.8.0.395.When deploying the OLVM worker, the worker deployment completed successfully. However, the worker's network was not working afterward:Veeam could not retrieve the worker's IP address information. The worker could not be pinged from the Veeam server. The worker appeared to be deployed successfully in OLVM, but there was no functional network connectivity.To troubleshoot, I downgraded the environment to:Veeam Backup & Replication 13.0.3.63 oVirt KVM Plugin 13.7.3.63After the downgrade, I redeployed the OLVM worker using the same OLVM/network configuration, and everything worked as expected. The worker obtained an IP address, Veeam was able to detect it, and network connectivity was working normally.This makes me suspect there may be a compatibility issue or regression in Veeam 13.1 / oVirt Plugin 13.8.0.395 related to OLVM worker networking.
The proof is in the pudding! Yesterday, the September episode of the Veeam 100 Show aired: Proof, Not Hope: Validating Recovery with Veeam SureBackup. Thank you to @NicBackup for joining, and to @Rin for co-hosting 🤗If you missed the show or want to rewatch, catch it below ⬇ Overview:How do you know your backups will recover when you need them most? Join us for a quick look at Veeam SureBackup and how it automatically validates backup recoverability in an isolated lab environment. We'll walk through the fundamentals, build a SureBackup lab live, and demonstrate connecting directly to a machine running from backup. What you'll learn:Verify backup recoverability with automated SureBackup testing. Build and launch a SureBackup virtual lab in a live demo. Connect to and validate a workload running directly from backup.📖 Read Nico’s blog on Veeam Surebackup: https://nicostein.com/proof-not-hope-validating-recovery-with-veeam-surebackup/
Veeam Data Cloud (VDC) is Veeam’s cloud-delivered backup platform designed to simplify how partners deliver backup services. It removes the need to manage the underlying infrastructure while providing protection for Microsoft 365, Entra ID, Microsoft Azure workloads, Salesforce, and secure storage through Veeam Data Cloud Vault.If you’re a VCSP partner looking to explore VDC, getting started is fairly straightforward.The primary license administrator of the VCSP partner account (with an active rental agreement) can register the business for Veeam Data Cloud through VCSP Pulse.Steps to access Veeam Data Cloud in VCSP Pulse Log in to the ProPartner Portal and navigate to VCSP Pulse. In the top menu, go to Licenses and Subscriptions. Click Veeam Data Cloud Subscriptions. If your organisation hasn’t yet accepted the updated VCSP Terms & Conditions for Veeam Data Cloud, you’ll see a banner message indicating that the terms must be accepted before proceeding.To resolve this: Click th
Hi everyone,I am surprised that I could not find anything regarding this topic.Here is the situation :I have no issue adding a vCenter server in the console.But when Veeam does the volume discovery, I get the warning in the title. In the screenshot it show up for two hosts actually.The ESXi hosts belong to the same datacenter under that same vCenter.Weirdly, as you can see in the screenshot, the next steps is successful.I tried to edit the vCenter object to see if it would prompt me to accept an untrusted certificate, but nothing appears.Also I tried to edit the properties of the ESXi objects but still no prompt to accept certificates.Does anyone have an idea about what is happening and how to fix this issue ?Best regards
I’m really pleased that one of my feature requests got implemented by Veeam.Out in the field with customers, or in our own demo lab, we keep running into stumbling blocks or things we’d wish worked differently. Veeam’s R&D Forum is where you can submit feature requests like that. Veeam employees look at them directly there, evaluate them, and work on them. My feature requestI submitted a feature request in the Veeam R&D Forum: an option to skip the update check when adding Managed Servers (Veeam appliances).Feature request – Veeam Managed Servers – Option to skip update check The problemWhen you add a new Veeam Infrastructure Appliance as a Managed Server in V13, the appliance checks whether updates are available for it. On a standard installation with internet access, you barely notice this.On a dark site, or when internet access and firewall rules haven’t been configured yet, it’s a different story. For dark sites you should use a local offline repo, and in other environments
Hi Everyone, I installed Veeam 13.1 on Windows Server 2022 without joining an AD domain and in an environment without internet access. I used IP addresses when adding the PVE9.2, but when I deployed the workers, the installation failed with the error “Veeam Updater is unavailable.” Later, I set up DNS forward and reverse lookups for the PVE and worker IPs, but the same error persisted. I unchecked the “Check for updates online” option for the workers.Does Veeam require an internet connection for the worker to install packages? Translated with DeepL.com (free version)
VMs Living Inside Kubernetes: What Veeam v13.1's New KubeVirt Proxy Is and Why You Should CareIf you come from the traditional virtualization world, the first time you heard about "running virtual machines inside Kubernetes" it probably sounded like an architect's joke. Wasn't Kubernetes supposed to replace VMs? And now VMs run on top of Kubernetes?Well, yes. And not only does it work: it's becoming one of the most popular landing spots for organizations rethinking their virtualization platform. With the announcement of the KubeVirt Proxy in Veeam Backup & Replication v13.1, Veeam just made an important move on that board. In this post I'll walk you through what KubeVirt is, what exactly Veeam announced, and why it matters even if you don't have a single Kubernetes cluster in your data center today.First things first: what is KubeVirt?KubeVirt is an open source project (originally created by Red Hat and donated to the CNCF) that lets you run traditional virtual machines as first-cl
Blog #2 for my new series is out. Check below.Blog - Veeam 13.1 Platform Expansion – OpenShift, XenServer, XCP-ng, and Cloud Appliances Veeam 13.1 Platform Expansion – OpenShift, XenServer, XCP-ng, and Cloud Appliances The headline features in Veeam 13.1 — the VSA, Universal CDP, Proxmox replication — get most of the attention. But the platform expansion work in this release is equally significant for organizations running infrastructure that falls outside the traditional VMware-centric model. OpenShift Virtualization, Citrix XenServer, Vates XCP-ng, and continued cloud appliance improvements each address real gaps in Veeam’s platform coverage.Let’s go through each one and what it actually means for the people running these platforms. Red Hat OpenShift Virtualization This is arguably the most strategically interesting addition in the platform expansion category. OpenShift Virtualization — formerly known as KubeVirt — lets organizations run virtual machines inside Kubernetes clusters o
The previous guide in this series got SAML SSO working between a Veeam Backup & Replication 13.1 appliance and Active Directory Federation Services. This guide adds a second factor to that login: a time-based one-time (TOTP) code from any MFA/2FA authenticator app, and optionally a passkey.The appliance does not need to know that MFA exists. It receives the same SAML assertion as before, from the same identity provider, with the same claims. Everything the previous guide configured on the appliance stays exactly as it was: the same relying party trusts, the same three claim rules, the same external users and groups. All the work happens at AD FS, and that is the right place for it, because authentication is what AD FS is for.Unfortunately native Microsoft AD FS cannot do this on its own. That is why all kinds of services exists, to name a few Okta, EntraID or CISCO DUO.Out of the box ADFS supports Azure MFA (EntraID) and certificate authentication as additional factors, but our goa
Well, I finished my previous blog series on 13.1 and have now started another series of 10 blogs (1 per week) on both 13.1 and Wasabi. Some will be Veeam, some Wasabi and some Veeam + Wasabi. So enjoy this series as some might seem like my previous ones, but they are much different with more detail.Blog #1 - Veeam 13.1 Universal CDP – Continuous Data Protection Beyond VMware Veeam 13.1 Universal CDP – Continuous Data Protection Beyond VMware Continuous Data Protection has been one of Veeam’s most powerful — and most narrowly scoped — features for years. Until 13.1, CDP was exclusively a VMware vSphere capability. That changes with Universal CDP, which extends near-zero RPO protection to a broader set of workloads.This is a genuinely significant architectural shift. Let’s work through what it means, what the current limitations are, and how to incorporate it into your DR strategy realistically. What is Continuous Data Protection? Before covering what’s new, it’s worth being precise ab
This week @Madi.Cristil is wrapping the LATAM run and we are happy to bring a solid recap video. You can watch this week’s episode here: Featured Contentvia @vnikiforov via @matheusgiovanini via @fabian.papenfuss Vanguard Blog Spotlight - Didier Van HoyeThis week’s Vanguard blog spotlight is @WorkingHardInIT with Veeam Application Backup Repository (ABR) in v13.1 for network devices - Working Hard In ITWorking Hard In ITSpecial Department Newsvia VUG Francevia Women and Allies and Tech groupvia VUG New Zealandvia @Madi.Cristil Who’s NewThank you @safiya for prepping this week’s Who’s New! We are pleased to welcome +112 new members. The coolest usernames are @Switz, @fredohouse, @Imads and @G-rant001! Alfred’s pick is @PC Planet → You have a badge coming your way. Have a great weekend everyone!
Veeam Backup & Replication v13 has arrived with significant improvements in security, performance, and data governance. I recently performed the upgrade from version 12.3, and in this article I share the entire process, from preparation to post-upgrade validation, following the official Veeam documentation. The goal is to present a practical, real-world experience while highlighting what’s new in this anticipated release. Preparing for the UpgradeBefore starting the upgrade, I followed Veeam’s recommended best practices to ensure a smooth and safe process. This included: Checking system compatibility, supported OS, storage repositories, hypervisors, and all backup infrastructure components. Ensuring no backup jobs were running. Updating the Guest Catalog and cleaning up old sessions. Performing a Configuration Backup, which stores all settings from the Veeam server. Creating a server backup or snapshot as an additional safety measure—especially recommended for production en
Happy Monday, Veeam Community! I am pleased to bring you another Vanguard Newsletter, which includes all the amazing content that our heroes published during August. Take a look at the range of topics available in this newsletter and make sure you find time to read it, as it contains lots of practical information, whether you're planning an upgrade to v13.1 or managing any other Veeam product. This newsletter edition is packed with practical insights, fresh updates, and hands-on guidance around Veeam Data Platform 13.1. Whether you’re planning an upgrade, exploring the new Veeam Software Appliance, strengthening your cyber resilience strategy, or simply keeping up with the latest platform enhancements, this month’s articles are designed to help you move from “what’s new” to “what’s next”.A big focus this month is on real-world adoption: upgrade walkthroughs, migration tips, lessons learned, and troubleshooting guidance to help make the move to Veeam Backup & Replication 13.1 smooth
Since we added Linux Repositories to our Veeam Backup environment in my post from last week, why not add some Linux Proxies as well? I will show you how in this post. And trust me…this one will be far less painful. But adding Repositories wasn’t so bad, was it? 😏 System RequirementsThe first thing you need to do is check what OS's, hardware, and software are supported. Supported Linux OS's are exactly the same as with Repositories and are listed below:Linux Proxy RequirementsAs far as hardware goes, your server should have a minimum 2-core CPU, plus 1 core per 2 concurrent tasks (take note, this is a peformance enhancement since v12, up from 1 core per 1 concurrent task); and minimum 2GB RAM, plus 500MB per concurrent task. But for best performance and to run multiple Jobs and tasks, you should have much more Cores and RAM than the minimum. As with the Veeam Repository, look to the Veeam Best Practice Guide for actual Proxy sizing guidelines.The remaining requirements depend on the Ba
Previous versions (12.3 and 13.0) can be found here A new version & improved scheme is alive!Reworked a lot to make visibility better, added some extra information, fixed some small mistakes I did with plugin and app backups, decreased possible confusion in several places. Important Notes about using the scheme:You can search for text in PDF version. But not through the images (logos of workloads) though. That’s limitation of PDF. I can share Miro link if needed, where all alts are there. Scheme requires just few minutes (don't spend more!) to get familiar with it and once you have an issue or just a question about something you don't remember or never knew how it works - first start with it to see general workflow and relationships before digging into the guide.
I’ve been setting up some reporting for users in Veeam one and this is a great feature if you want to quickly determine the cost of your backups for each VM or Job. It’s also a great way to see what each job is costing per repository. Warning…. with current storage prices, this my shock you!!!! I did however find it wasn’t as straight forward as just adding the price of the repository and clicking run. There is also quite a few options you can choose to make the reporting tailored to those who are intended to receive them. The first think you will want to do is select the time frame for your report. In my case I selected as far as my retention was to get the full cost. You can use the “Last” radio button and change weeks to years. For the multipliers if you have different types of storage make sure to click configure to set it individually. You can select a repo with multiple extents and apply multipliers for each as well Multipliers are based off of the price included i
Status: 02.09.2026Tested with: Veeam Backup & Replication 13.1 and NetApp ONTAP Plug-in 2.0.14Spoiler: Yes, coexistence works. But randomly clicking around is not a good idea. Anyone who has known me for a while knows that I started in IT as a System Engineer back in 2005 — and since then, NetApp systems have regularly crossed my path. Or maybe I crossed theirs. Depending on perspective.Over the years, I have built, configured, troubleshot, and occasionally lovingly cursed at NetApp systems in small, medium-sized, and very large environments. I had the chance to gain field experience worldwide, later trained people on NetApp while still implementing them in costumer projects, and was also involved with the topic strategically as a Head Architect and Product Manager/Director.Long story short: I have a certain historical affinity for NetApp systems. Even though I no longer deploy them on a daily basis, my inner storage heart still gives a little twitch whenever snapmirror, igroup, Fl
I am in need of some assistance from the community with Veeam Backup & Replication. I upgraded the server to 13.0.1.2067. No errors were thrown during the upgrade, logs don’t show any red flags that stick out; however the service hangs when attempting to access the localhost database server.Here is what I see:When the Veeam console is run, the “Specify backup server” page appears:After the localhost database is selected, the next window appears: The console goes no further than this, and the system doesn’t show any signs of activity. All services show as running on the server:I also tried updating .NET 8 dependencies to newer versions in case these were what may be causing the issue, but there was no change in results. I have attempted to upgrade this application twice with little success. As of now, I may need to revert back to the older version and try again, which may lead me back to here.Has anyone else encountered this when upgrading to 13.0.1.2067? If so, how was it remediate
Key Takeaways from the El Segundo Zero Day Resilience WorkshopCyber resilience is not proven with a static Disaster Recovery plan. It is tested in advance through training and practice. It is proven in the moments when operations fail and an organization can respond with speed, clarity, and confidence.I recently had the opportunity to help host a Veeam Zero Day Resilience Workshop in El Segundo, California, where IT and security leaders from education, health, manufacturing, marketing, and public services came together to share how they would respond to a fast-moving cyberattack. The viewpoints from CISOs, CTOs, security analysts, system administrators, IT directors, and more enabled valuable discussions from many angles on how to prepare in advance to successfully counter a cyberattack.If a Veeam-sponsored security workshop is available in your area, I would highly recommend attending for the insight provided. Here are the highlights and key takeaways.Workshop Keynote Highlights69% of
Hello Community, Sharing an update that Veeam announced about production license distribution. This will matter for anyone who handles orders or helps customers access their license files. What’s changingStarting December 4, 2025, production license files will no longer be sent as attachments in order confirmation emails.This includes purchases through the online store, public marketplaces, and distributor marketplaces.Going forward, the designated license administrator for the customer will need to download the production license directly from the My Account portal under Production Licenses.Trial and NFR licenses are not affected. Why this matters• Improves security and keeps license access tied to the right admins• Makes it easier for customers to retrieve licenses in one place• Partners need to make sure the correct customer license admin is specified on every order or the customer may not see their license in the portal Figured this would be helpful for the community since many of
Hi. We followed the Veeam documentation to install the IBM AIX agent in "pre-installed agent" mode, but we later realized it could also work within an "individual computer" protection group. We believe the latter approach is better because the pre-installed agent method requires manually triggering synchronization on the AIX host or waiting up to six hours for it to occur. I found a Veeam article explaining how to migrate between protection group types, which I’ve included at the end of this message.The agent—version 13—has just been installed; we used the XML file provided by the Veeam console, and the connection was successful. Since we prefer the "individual computer" method, and I believe moving it avoids the need to revert to standalone mode (allowing everything to be managed from the console), could you please confirm that this procedure works as expected? I’d like to proceed with this change.Here is the link:https://helpcenter.veeam.com/docs/vbr/userguide/agents_protected_comput
It’s getting very busy… and it’s not going to slow down! @Madi.Cristil is in VeeamON Tour mode (I’ll be soon!) in Latin America but we found a time to get the recap recorded. You can view this week’s episode here: Featured Contentvia @kciolek via @Scott via @Chris.Childerhose Vanguard Blog Spotlight - Zamaan AliThis week’s Vanguard Blog spotlight comes from @zamaan.ali - Veeam Data Cloud Vault vs Vault Archive – which one should you use? – Zamaan's Tech BlogsSpecial Department NewsVeeam User Group USA - Los Angeles: Veeam User Group Ecuador - Quito:Veeam User Group France - Montpellier:Who’s NewWe are pleased to welcome +153 new members to the Veeam Community! The coolest usernames are @iSendin, @dairycowz, @ArtZil and @goveeam. Alfred’s pick is @coolcarl1999 → You have a badge coming your way. Have a great weekend everyone!
Hi everyone. I have a question: I want to upgrade from Veeam 12.3.2.4854 to Veeam 13.0.3.63. However, I have an immutable repository running on RHEL 10.2; as you know, the SSH port is disabled. Since the new version needs to be applied to the components on the immutable repository, is it necessary to enable port 22, or can the upgrade proceed even with that port disabled? I hope that makes sense.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.