Blogs and Podcasts

Today while I was working in the Veeam Windows Console for v13 I hit a strange error when copying a job error message to the clipboard.  It let me paste but the error noted is just a minor annoyance.  I have reported this and you can read it below and on my blog.  Once confirmed I will update things on the community and my blog post.Veeam Console – Possible BUG – Copying to Clipboard Veeam Console – Possible BUG – Copying to Clipboard I have been using Veeam v13 more frequently lately, particularly the VSA and the Windows Console application. Today, I encountered an unusual issue with the Console application while copying an error message from a job to the clipboard for investigation. The message below appeared, but I was still able to paste the clipboard contents regardless.Copy to Clipboard Error (Potential Bug?)I have posted this in the Veeam 100 thread (not everyone will see this, as it is a special section of the Forums) as a possible bug, which you can see here if you have access

​ Oracle Retention for RMAN and Veeam Plugin Backup   When it comes to RMAN, Veeam acts as a storage location utilized by the Oracle SBT interface. Therefore, it is RMAN retention settings that are utilized to manage the backups generated when using the Veeam Plugin backup protection.Typical retention for application aware backup will focus on the most recent restore points and mark backups to be pruned per familiar Veeam retention policies and retention methods.With Oracle, an incremental strategy employs a combination of incremental level 0, incremental level 1 and incremental level 1 with cumulative incremental or stand alone full. Each of these backup types dictate what data RMAN will identify and capture to create backup sets.Data captured during any one of these types can be manipulated as desired by the user. Typically, an incremental level 0 backup will capture all files necessary to restore and recover a database including the Initialization or SPFILE, Control File, all databa

The Veeam SAP HANA Plugin is an SAP-certified backup tool that connects directly to SAP HANA through the Backint interface and lets you store transaction-consistent database backups and log files in Veeam backup repositories. It acts as an intermediary between the SAP HANA server and Veeam, compresses the backups, transfers them to the Veeam repository via Data Mover, and allows backup and restore operations using native SAP tools such as SAP HANA Studio, Cockpit, and HDBSQL.As the plug-in only establishes the interface to Veeam, all further configuration is carried out via SAP, and SAP administrators are free to configure this as they wish.Installing the plugin is quite simple, but there are a few things to consider beforehand. Preparations / Basic InformationOS and HANA VersionThe OS and SAP HANA version must be compatible with the currently used Veeam version.https://helpcenter.veeam.com/docs/backup/plugins/system_requirements_saphana_64.html?ver=120 Firewall RulesFirewall rules mus

With the release of Veeam Software Appliance and JeOS, deployment processes have become significantly more streamlined. In Europe, the prevalence of multiple languages naturally results in a variety of keyboard layouts, such as Azerty for French users, Qwertz for German users, and a Danish variant of Qwerty to accommodate specific characters like Å, Æ, and Ø. However, the rapid installation process does not provide the opportunity to configure keyboard settings during setup.There is, however, an effective solution. JeOS is an optimised and secure edition of Rocky Linux, and its installation is managed through an automated kickstart script. Settings such as keyboard layout, timezone, timesource, and network configuration are all specified within this script. To ensure every installation includes your preferred configurations, you can update or remaster the ISO and integrate these settings directly. For this purpose, I have developed a custom script, ksmod.py, which is available at https

​In the first part of this three part blogpost we’ve discussed why to use gMSAs to achieve application consistency before backing up our workloads with Veeam Backup and Replication (VBR).In this part I will show you, how easy it can be implemented with VBR and how the process differs from the official manual.  (1) Ensure your forest schema is updated to (at least) Windows 2012 (Version 56+)First, check your version of the forest schema and increase it, if needed, beforehand. You might well go all the way up to the maximum possible level for your most legacy domain controller. Check for compatibility with other domain related services like Exchange servers etc. first, to make sure you don’t break other things. (2) Make sure you have created a KDS root keyThe KDS root key is a crucial component of the Microsoft Group Key Distribution Service (KdsSvc). It is used to generate group keys that are distributed within an Active Directory environment. This root key is essential for creating gro

After four years away from Veeam (now a Pure Storage Principal Technologist), v13 represents the evolution I always hoped to see. This isn't just another release. v13 is Veeam's comprehensive answer to modern infrastructure challenges. Key Transformations:Web UI Revolution: Complete backup management in-browser, eliminating dedicated management workstations Security-First Foundation: STIG-compliant hardened Linux with enforced MFA and dual admin model from deployment Hybrid Infrastructure Ready: Modern foundation while maintaining full backward compatibility Appliance Simplicity: OVA deployment with wizard-driven hardening, without being stuck In The Box.The Linux foundation isn't just OS modernization it is in reality an infrastructure alignment; strongly catering to security-conscious hybrid environments. Having seen customer challenges from both the backup and storage sides, v13 addresses every major adoption barrier I encountered as a SE.Bottom Line: This is Veeam's strategic reset

A previous post (https://community.veeam.com/blogs-and-podcasts-57/veeamsoftwareappliance-on-fedora-42-11241) covered how to set up the software appliance on a Fedora 42 host, including network configuration for direct bridging. This post provides information on setting up a Veeam Hardened Repository.While this documentation is intended for lab use, it may also be relevant for SMB customers seeking guidance on configuring an all-in-one appliance. Security considerations were not a primary focus, so additional safety measures may be necessary. For instance, it may be advisable not to bridge the host itself to prevent external access after installation.First, install virt-install to quickly set up new virtual machines.sudo dnf install virt-install -yIf you want the disks on another drive set (eg /dev/sdb mounted to /mnt/backup), we can create a subdirectory for the user on it and add as a pool. sudo mkdir /mnt/backup/$USERsudo chown $USER:$USER /mnt/backup/$USERmkdir /mnt/backup/$USER/da

Recently I installed Fedora 42 using Gnome Boxes, which serves as a lightweight graphical interface for KVM/QEMU, comparable to VMware Workstation.Since Gnome Boxes functions primarily as a front-end for KVM, it is possible to leverage virsh for automation purposes, making it particularly suitable for laboratory environments. For graphical access, users may utilize either virt-viewer or the Boxes GUI.These commands are generally compatible with other KVM-based platforms such as Proxmox, although networking configurations may vary. This setup is recommended for home lab use; it should not be deployed in production environments unless its appropriateness has been thoroughly evaluated, and you know exactly what you are doing Setting up networkFirst, set up a bridged network. This step is optional, and much of the configuration can be skipped if it is not performed. With this setup, VBR will be accessible on the network (think VBR HA for example)Use nmcli to display your current network ad

Greetings, friends! I want to share with you the new Grafana Dashboard for Veeam Backup & Replication, no Enterprise Manager is needed, and it uses 100% VBR API.Small note: For those familiar with the data protection scene, you might recall that we’ve already got a Grafana Dashboard dedicated to the Veeam Enterprise Manager API since 2020. Grafana Dashboard for Veeam Backup & Replication API When you finish this article, if you follow all the steps, you should have something similar to this. It might be different according to your environment, number of days you select, protected workloads, jobs, etc.Dashboard – SummaryJob Historical Information – The very first graph. The most important one in my opinion. Grouped by 24 hours, get to know the status of your policies per day, on a range in time. Job Historical Information Table – Very similar to the previous panel, but this time with more details about job name, status, date, etc. Job Historical Information Duration – Very simil

 Extracted from the original blog at wcithipster.com on Nov 25 Written By Zane AllynAs a Veeam Vanguard and a longtime backup enthusiast with more than six years of experience working at Veeam. Today, I’m beyond excited to share an early look at Veeam Backup & Replication v13. This release introduces two major enhancements: a fully Linux-based backup server and an HTTPS-based web console. These updates are not just features; they’re milestones that reflect years of community feedback.This sneak peek is based on alpha code, so things may change before the final release. That said, there’s plenty here to get excited about. Let’s get into it.A Fully Linux-Based Backup Server: No Windows NeededOne of the most significant changes in v13 is the move to a fully Linux-based backup server. For years, Veeam relied on Windows to power its core services. With v13, that dependency is gone. Instead, you’ll deploy the server using an OVA file, making the process faster, more secure, and platform-

Hello, Veeam community! Summer may be over, but the good things remain, such as the Veeam Vanguard Newsletter! I am happy to share with you the August one, which is packed with a variety of Veeam-related topics that anyone can relate to. 🤓 Take a look for yourself below and delve deeper into the following: ​@AndreTheGiant  - VMware vSphere versions supported by Veeam Backup & Replication (July 2025) - https://vinfrastructure.it/2025/08/vmware-vsphere-versions-supported-by-veeam-backup-replication-july-2025/ Veeam Backup & Replication Plug-in for Scale Computing HyperCore - https://vinfrastructure.it/2025/08/veeam-backup-replication/ Why could be a wrong idea using a dedup appliance as primary repository in Veeam? - https://vinfrastructure.it/2025/08/why-could-be-wrong-idea-using-a-dedup-appliance-as-primary-repository-in-veeam/​@WorkingHardInIT - The rejuvenated push for excellence by Veeam for Hyper-V customers - https://blog.workinghardinit.work/2025/08/04/the-rejuvenated-pu

I shared with the Community last week how to get XCP-ng up and running. If you missed it, you can go review this Part 1 post. Here in Part 2 I'm going to discuss how you should begin setting up your XCP-ng environment to be centrally managed by Xen Orchestra (XO), then move on to discuss features in XO you should be interested in knowing about & configuring if you're looking at this hypervisor to transition to away from VMware. Add Users and XCP-NG Hosts  Adding UsersAfter creating your Xen Orchestra (XO) server, the first thing you should do is configure your user base. As shared in my Part1 post, take note of the default username/password needed to login to XO after the XO installation completes. In my test environment, I only use local users, but XO does provide the ability to configure your environment for LDAP/S, e.g. using Open LDAP or Active Directory. If you want to create local users, it's as easy as navigating to Settings > Users in XO, providing a username, role (only

I am deploying the new v13 VSA using the OVA method in my lab VMware environment today and discovered when deploying you could see an SSL warning for the OVA like this -SSL Warning and Ignore option There is a fix for this but it requires that you install two CA certificates from Entrust to the vCenter Trusted Root Store which can be done from the WebUI.  Once those are installed to your vCenter then deploying the OVA will not give you the SSL warning and show a valid certificate.CA Certificates to install -Entrust CA Certificates to install in Trusted Root Store on vCenterAfter that when deploying OVA no more warning and valid certificate -Trusted Certificate for OVA deployment of VSAHopefully this helps those that are keen on testing things in your lab environments.

I have been working with VONE 13 since it dropped yesterday and after upgrading my homelab server I found a bug within the Alarms Overview dashboard in the WebUI.  After checking with Jorge in the forums it was noted that if you assign a location to any components this causes the bug.  You need to have no locations and this will be addressed in the next release.Forum Post - (3) Possible Bug - VONE - Alarms Overview screen - R&D ForumsBug -VONE Bug on Alarms Overview screen when Locations assigned Fixed when no locations set -Alarm overview showing alarms now 

Hi everyone,Veeam Community Hackathon banner for 2025. Alfred is sitting in the middle behind a desk. He is about to press a button with the text "RUN" on it. Binary code and a slider are shown on the left of Alfred. In the middle, the word “Hackathon” is shown with arrowed lines pointing to icons and text describing several aspects of the Hackathon: Development, Brainstorm, Time, Presenting, Goal, Teamwork, and Community.We are doing a 3rd Annual Veeam Community Hackathon! Dec. 8, 9 AM ET/15:00 CEST to Dec. 13, 9 AM ET/15:00 CEST Yes, you are reading this correctly, ​@JonahMay and ​I (@mkevenaar)  are organizing the 3rd Annual Veeam Community Hackathon. Just like last year, ​@jos.maliepaard and ​@Mayhem are assisting us again. Just like previous years, teams will be working together to enhance one of the Veeam products. Just like last year, teams geographical location will determent the team they will join. New this year is that the teams will decide their own leader! And yes, this ye

Recently, I migrated our SAP HANA environment to use the Veeam backup plugin, replacing the old Commvault plugin. The process had a few challenges that I want to share for anyone doing something similar. The ProblemAfter uninstalling the Commvault plugin, I noticed that some old configurations were still on the system. This was preventing the Veeam HANA Plugin from being applied correctly. The issues were mainly caused by old configuration files and symbolic links that needed to be adjusted manually.!-->!--> How I Solved It1. Removing other plugin completelyIn SAP HANA, I used specific commands to unregister the old backint and make sure nothing was left behind. 2. Adjusting configuration filesSome Backint files needed to be renamed or edited to make room for Veeam.Examplemv hdbbackint hdbbackint.old !-->!--> 3. Setting Up VeeamOnce everything was ready, I ran the SapBackintConfigTool to register the databases in Veeam:SapBackintConfigTool --wizard During the wizard, I prov

With the latest releases coming out today I took the time to upgrade my Veeam ONE server to v13 to see some of the new features and enhancements which are great.  Nice to see how they have refined things and having the Postgres DB for reporting makes things so much faster!See my blog here and below - https://just-virtualization.tech/2025/09/03/upgrading-to-veeam-one-13-0-what-you-need-to-know/ Upgrading to Veeam ONE 13.0: What You Need to KnowToday, Veeam released some major updates to the product lineup, which include –Veeam Software Appliance v13 – ISO or OVA – https://www.veeam.com/veeam_backup_13_whats_new__wn.pdf Veeam ONE v13 – https://www.veeam.com/veeam_one_13_whats_new_wn.pdf Veeam Service Provider Console v9 – https://www.veeam.com/veeam_console_9_0_whats_new_wn.pdfThe latest release of Veeam ONE, version 13.0, is now generally available, introducing numerous new features and enhancements that promise to enhance your data protection and reporting capabilities. Whether you’re

Hi Everyone, Just sharing another great event here in Brazil, The Veeam ON Tour!It was time to refresh our knowledge, make new friends and also, meeting another Harley Davidson bikers!! :-)Below: Beth, Jean, Matheus and I, all of us are  VUG Brazil Leaders.We were beside the OOBTI booth, here the OOBTI Team.  It was amazing!!!

Hi All,What is the best resolution to pull Agent backup job reports configured with GFS from VAC integration with REST API or Swagger not using Veeam ONE. Thanks,

Well some good news for those that are fans of my previous three books, today I was able to get my hands on something that will allow me to start the outline and process for the fourth book on v13.  Looking forward to delivering a fresh new take of Veeam v13 with the new appliance model and the JeOS ISO servers.I will also be covering the AI pieces as well that have been put in to the latest releases along with the new VONE v13.  I will see about the Windows version upgrade path and depending how long that takes might skip it from the book and just go with the appliance since this to me is the future.So hold on to your hats and hopefully I can aim to get this out early 2026.  If there are specific topics anyone wants to see covered feel free to post them here or DM me if you like. 😎

Dear Community, If you're a Veeam Cloud & Service Provider (VCSP), support workflows is a routine part of daily operations. Traditionally, raising support tickets with Veeam support involved a manual, time consuming process, collecting logs from tenant VBR servers or Agents, navigating remote access restrictions, and uploading everything to the my.veeam.com portal for investigation. This added unnecessary delays, especially when dealing with restricted environments or needing approvals. With the Veeam Service Provider Console (VSPC), the entire process is streamlined. You can now open tickets directly from the VSPC portal, whether for your own infrastructure or tenant or a reseller and automatically attach the relevant logs. It’s a great improvement and significantly saves time creating support tickets and collecting the required log information. It also speeds up the investigation for Veeam Support Engineers, as they already have the logs from the beginning and don’t need to reque

Recently I had to configure a backup on a physical Linux server that stores over half a petabyte of traffic fine images collected from speed cameras on federal highways in Brazil.   The catch: this server runs critical client applications, and any migration to another server is extremely sensitive and requires careful planning before taking action. At the moment, a full migration wasn’t feasible.Due to the urgency of the demand, it was necessary to implement a backup solution immediately, but the server cannot go down for even one minute. Any downtime would mean fines not being recorded, resulting in immediate financial loss.  The Challenge of Backing Up a Mission-Critical Environment The client required backup implementation for compliance reasons. I use Veeam Agent for Linux, configuring the backup job at the volume level. To avoid impacting main traffic, I limited the throughput to 50 Mbps using Veeam’s throttling feature.     Everything seemed well planned, until I ran the first ba

More and more companies are depending totally of their ICT infrastructure (on-premises, private cloud, hybrid cloud, public cloud) …Ransomware and hackers are more popular than ever…Therefore one of the most important things is that the company has a solid backup strategy, so we can fall back at those in case of disaster or being impacted by ransomware or hackers.You can find very often the 3-2-1 rule. I suggest every customer or company to even go a step further : apply the 3-2-1-1-0 rule !3 : Maintain at least 3 copies of your data By three copies, I mean that in addition to your primary data, you should also have at least two more backups.Why?The chance that something is going wrong with 3 devices at the same time is a lot smaller than with 2 devices, especially when the primary backup is often situated close to the primary data. In case of a disaster the primary data and primary backup could be gone. The secondary backup is often situated somewhere else and could be the solution in

We've got a new blog post! This month, we're diving into the art of fine-tuning Veeam VBR for on-prem object storage. In this post we show how to optimize performance for Scale-Out Backup Repositories (SOBR) with a Capacity Tier, specifically addressing the challenges of using on-premises S3-compatible appliances. This with the registry key “S3ConcurrentTaskLimit”Click here to read the full blog post and learn more about Veeam registry keys! 

 Upgrading from 12.3.0.310 to 12.3.2.3617 stopped at the database check with “Failed to connect to PostgreSQL server localhost:5432.” The fix was to map the exact Windows identity that launched setup in pg_ident.conf, restart PostgreSQL, and rerun the installer. No reinstall needed. Environment Single VBR on Windows Server 2022 with multiple NICs for LAN and storage Local workgroup admin account Embedded PostgreSQL 15 for the configuration database What I saw During the Configuration Check I got:Failed to connect to PostgreSQL server localhost:5432.An existing connection was forcibly closed by the remote hostDaily jobs were fine, which told me services already had access. The installer, running under my current login, did not.What I checked first Live installer logI tailed the newest SuiteEngine log to see exactly where setup stalled:Get-Content -Wait (Get-ChildItem 'C:\ProgramData\Veeam\Setup\Temp\SuiteEngine_*' -File | Sort-Object LastWriteTime -Descending | Select-Object -Expan