Join discussions around Veeam community projects, Veeam events, industry and technology news
Recently active
Happy Friday Community 😻We're back. And this one might be our most controversial debate yet.There are two kinds of Veeam administrators. Those who would never join their backup infrastructure to Active Directory. And those who think running it any other way is unnecessary complexity.Both are convinced they're right.Debate Statement Joining your Veeam backup infrastructure (VBR server, proxies, repositories, Enterprise Manager, etc.) to Active Directory is a security mistake. ( thank you @DChiavari for this one 😎) If your backup infrastructure is the last line of defense, why should it trust the very identity platform attackers are most likely to compromise?A workgroup or isolated environment can reduce the attack surface, limit lateral movement, and keep backups operational even when Active Directory is offline. But is the extra security worth the operational overhead? Or are we solving a problem that good security practices already address?What I'm looking for this round Forget ven
Hello awesome community! A huge thank you to everyone who participated, shared their votes, and helped make this challenge a success!As promised, the three most-voted articles will each receive a surprise prize. We’ll be reaching out to the winners directly with details on how to claim their prize.And now, the moment we’ve been waiting for…Congratulations to our winners! @lucasmagnum @matheusgiovanini @wolff.mateus Your contributions clearly resonated with the community — well deserved!Thank you again to everyone who took part. Keep sharing, keep contributing, and keep making the Veeam Community awesome! 💚
What’s in YOUR Veeam Toolbox? Now YOU get to decide!A huge thank you to everyone who shared their Veeam tips for our SysAdmin Day contest! We’ve got some great entries, and now it’s over to the community to choose the winners. Check out the submissions and vote for your favorite tip — the one you’d want in your toolbox when things go sideways!Voting is open until August 17.Who will become our next Incident Commander? Let the voting begin! 😻@wolff.mateus , @coolsport00 , @matheusgiovanini , @Nico Losschaert , @eblack , @lucasmagnum , @Stabz Good luck to all of you !
Happy Tuesday, Veeam Community!Last month brought so many fantastic articles to the Community Hub that I'm sure @safiya had a tough time narrowing them down to just six finalists—and I'm sure the community had an equally tough time choosing a winner! 😄A huge thank you to everyone who wrote, read, and voted. Your contributions are what make this community so special.And now, it's time to celebrate our Blog of the Month July 2026 winner...Congratulations, @falkob !
What's in Your Veeam Toolbox?Every incident has a commander. The person everyone turns to when things don't go as planned. The one who knows exactly which workflow to follow, which Veeam feature to use, and how to get everything back on track.This SysAdmin Day, we're celebrating the knowledge and experience that make all the difference when it matters most. We want to know: what's the one Veeam tip that's always in your toolbox?Every year, on the last Friday of July, we celebrate System Administrator Appreciation Day (SysAdmin Day)—a day dedicated to the people who keep everything running behind the scenes.Whether it's recovering from a ransomware attack, fixing a backup job before anyone notices, or somehow making yesterday's "urgent" request disappear before the morning coffee kicks in, sysadmins are the ones who keep IT moving.Every sysadmin has those little tricks they've picked up over the years. The shortcut that saves time, the workflow they've perfected, or the Veeam feature th
We are back!Episode 1 sparked some strong input, but also a bit too much alignment 😄So this time, we decided to make it harder.I asked @ddomask to help me shape a statement that would force a real split — not an obvious answer.Debate Statement “Tape is dead — stop living in the past and use a real archival solution like Object Storage or dedicated deduplication appliances.”Tape had it's heyday, but so did IRC. True data resilience requires a modern solution, and you can only get that with a vendor-supported archiving service / appliances, and you can get both on the cheap without having to spend a fortune on hardware and maintenance. Your data will always be safe with one of these more modern options.What I’m looking for this roundNo theory. No safe answers.I want:Where tape still wins in practice Where modern solutions fall short in real environments The trade-offs you’ve had to make at scaleDon’t aim to agree — aim to challenge the statement with real-world experience.New here? Q
Another debate, another reminder of why I love this format. Thank you to everyone who took part in Episode 2 of our Oxford Style Debate. It was great to see so many well-reasoned arguments, different viewpoints, and real-world experiences shared throughout the discussion.This month's statement was:"Tape is dead — stop living in the past and use a real archival solution like Object Storage or dedicated deduplication appliances."To help select this month's winners, I invited @Mildur from Product Management to review the discussion and share his perspective.A huge thank you to Fabian for sharing his expertise and helping identify the most insightful arguments from both sides of the debate.Winner Against “Tape is dead” - @matheusgiovanini '’matheusgiovanini made the strongest case against the statement by sharing a real recovery scenario from his own experience. In his mentioned case, the backup server, repositories, and storage replication were all compromised, and offline tape was the
Good day Community,Back from vacation straight into the big guns — so here it goes 🙂Has anyone started looking at Veeam Intelligent ResOps for Microsoft 365 yet?It feels like an interesting shift — less about backup in the traditional sense and more about adding context and intelligence around M365 resilience decisions.Curious how it’s being seen so far:Does it feel like a real step toward “resilience intelligence,” or more like an extension of existing reporting? Is it actually changing how teams prioritize or make decisions, or is it still mostly visibility on top of what we already had? And does it feel meaningfully different compared to what others are doing in the space?Would be great to hear some early thoughts from people already exploring it.Best, Madi
We know AI is becoming a normal part of how people create content, and lately we’ve been seeing more of it show up in the Community Hub.That said, posts that are mostly AI-generated don’t really add the kind of value this community is built on—especially when that same information can be created by anyone using the same tools.What we’re really looking for is your experience: real-world scenarios, hands-on demos, lessons learned, and practical insights from what you’re actually doing day to day. That’s what makes the community useful and interesting for everyone.Also, content that is primarily AI-generated won’t be considered as part of the criteria for becoming a Legend or Vanguard.So if you’re sharing, try to lead with your own voice and perspective—that’s the part that really matters.
Hey Community, I received a few messages from community members asking how to get notifications when there is a new content published (in this case we talked about “Blogs and Podcasts” category). I thought I would do a quick post about it. First, there is a possibility to subscribe to every category at Community Hub Let’s say, you would like to subscribe to “Blogs and Podcasts” category. To do so, you have to push ‘SUBSCRIBE’ button at the right side as shown at the screenshot below: Once it’s done - you will start receiving notifications about new topics created!Again, you can get subscribed to any category: whether it’s Discussion boards or News. You can also manage notification settings at your profile.If you experience any issues with notifications - please let me know!
Happy Monday, Veeam Community! 😊Thank you all for voting once again! It looks like we have a winner for this edition! 🎉Congratulations, @kciolek ! Your blog, “Lab: Veeam 13.1 in the Real World: ‘Why Now’ Customers Should Upgrade?”, received 15 votes from our community members.A well-deserved congratulations — and your badge is on its way! Thanks again to everyone who took the time to read, vote, and support our community bloggers. See you next month!
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.
Hi,i am using Community Edition of Backup and Replication. In special i have been using a script to start Veeam ZIP to get a standalone full Backup. This has been working flawless for quite a while.There has been Issues with Powershell in the past, so i have to start the batch explizit with the “new” powershell version. But this was about a year ago.So i got a running Version of Backup an Replication (13.0.2.29) then i upgraded to 13.1.1.18 and Veeam ZIP stopped working with the following Error Message: Error: Unable to cast object of type 'Veeam.Backup.Core.CFreeVmBackupTarget' to type 'Veeam.Backup.Core.CVmBackupTarget'.I searched the Internet and have been finding very few users with the same problem. One of them provided two solutions: Revert back to functional version, or contact Support and get a hotfix to makle changes on DLL.i do not want to revert back, because i think this is a greate Problem which has to be adressed by the support generally.I filed a case by the Veeam Supp
After a failed Veeam backup, a Hyper-V VM (ADCC130HP01) was left with multiple nested Veeam Recovery Checkpoints that cannot be removed.Current situation:4 Recovery Checkpoints are chained together. The oldest Recovery Checkpoint dates back to 06/08/2026. The VM is still running normally. The VM disks currently point to the base VHDX files. Multiple AVHDX files still exist on disk.When attempting to delete the checkpoints from Hyper-V Manager, I receive the following error:"Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Virtual machine failed to generate VHD tree."When attempting removal via PowerShell, I receive:"Cannot delete a checkpoint subtree that contains a recovery checkpoint."I have already tried:Deleting checkpoints from Hyper-V Manager. Deleting checkpoints using PowerShell. Attempting manual merge operations.Has anyone experienced a similar issue and successfully removed these orphaned/chained Veeam Recovery Checkpoints without rebuilding the VM or risking dat
Hi guys, Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process - The upgrade failed and did not allow us to retry at all. Certain options were greyed out - Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. - In the end, we were forced to back out of out upgrade.Has anyone seen this before? ShaunB.
I'm using Veeam Backup & Replication Community Edition 13.1.1.18 in a home lab with Veeam Agent for Microsoft Windows 13.1.1.700.I'm seeing extremely poor performance with physical Windows Agent jobs configured as:Server -> Managed by backup server -> Veeam backup repositoryThe problem reproduces on multiple physical Windows PCs.The same machines perform normally when configured as:Server -> Managed by agent -> Shared folderThe difference is enormous.Example managed-by-backup-server test:- Destination was a LOCAL NVMe repository on the VBR server- Approximately 49 GB read- Approximately 30 GB transferred- Duration: approximately 4 hours 16 minutes- Average processing rate: approximately 3 MB/s- Veeam reported Network as approximately 99% of the bottleneckThe transfer frequently drops into the hundreds of KB/s or even tens of KB/s, with occasional short bursts of normal/high throughput.I specifically tested a local NVMe repository to eliminate the NAS/SMB repository path
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/
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
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
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
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.
I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.
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)
I just want to confirm if my understanding is correct.Lets say my veeam managed oracle rman plugin backup has this configuration:control_file_record set to 30 days.rman retention is set to 30daysveeam retention is set to 30 days.I also send the veeam backup to that offsite location, with retention period of 1 year.If I want to restore my database to 1 year ago, and rman and veeam repository already deleted the metadata, so is this the step:copy the backup from offsite back to repository (.vab, .vasm, .vacm) (should I replace the .vacm?) rescan the repository, then it will show under DISK (IMPORTED), will I be able to restore the control file to 1 yr ago now? Or do I need to run --remap backup first ? will the RMAN channel for this old backup files be different from the current one?thanks
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
