Community

 This week, we received two interesting questions from a customer regarding backup scheduling and archive retention in Veeam. Since these topics may be useful for others as well, I decided to share the answers in this quick post. Q: Is it possible to configure RDS backups to run every 15 minutes?A: No. The minimum backup frequency supported for Amazon RDS backups is once per hour. Running RDS backups every 15 minutes is not supported.If you need more frequent recovery points, you can configure RDS snapshots with a higher frequency. In the schedule settings, select the "1 per hour" option and adjust the value to the desired number of snapshots per hour (for example, up to four snapshots per hour, resulting in a snapshot every 15 minutes).Specifying Daily Schedule - Veeam Backup for AWS User Guide   Q: Is it possible to run monthly and yearly backups without requiring a daily or weekly backup schedule, sending them directly to an archive bucket?A: No. It is not possible to configure mont

Hi Community, During the projects I have been working on, or in the VMCA classes I teach, I use drawio.com to make diagrams. It is a simple and free tool to use. However, the Veeam icons are not always up to date on it. So, to improve the quality, quantity and standard of the Veeam icons, I share many other formats with you.So, you can use drawio as a diagram tool and the Veeam icons in SVG format. Once drawio is open, you just need to copy and paste the desired icons into the drawio window.For those who use Visio, I’ll attach the visio stencils as well.  

💡 The Challenge:Removing a backup proxy in Veeam Backup & Replication across a lot of backup jobs can be pretty annoying and time-consuming.🚀 The Solution:That's why I wanted to share a short PowerShell script that automates this task for you!I personally use it whenever I decommission a backup repository in large, shared Veeam environments - it's a real time-saver.⚠️ Right now, this script is built for the Windows-based Veeam version (12 & 13).A version for the Linux-based appliance is on my roadmap, so stay tuned!👉 You can grab the script here: 🔗 https://github.com/fabpapde/community/blob/main/veeam/veeam-backup-proxy-remove-v1_0.ps1

Dear Community!Last week, I updated my Veeam environment to version 13.1. After upgading my Veeam One installation, I’m no longer able to connect through the Veeam One Client, but from the WebUI it works fine.I don’t know what is going on and I cannot contact support because I’m currently evaluating Veeam One product to see if it’s fit out needs.Here is what I have from the Veeam.Reporter.log file:03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : -->TryGetWebGrpcCert03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : <--TryGetWebGrpcCert (in 0:00:00.0013216) Thumbprint: <removed for security>03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : -->GetOrCreateCommunicationCert03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService - - - - - : <--GetOrCreateCommunicationCert (in 0:00:00.000948) Cert: [<removed for security>]03.08.26 14:10:08 [INF] 0x

Estou usando a Community Edition e vi que ela é compatível com o Veeam Data Cloud Vault; comprei-a em 23/07, mas até agora não consegui usá-la nem acessar o suporte ao produto. Como não tenho uma licença padrão da Veeam, não consigo falar com o suporte técnico nem abrir um chamado.

Hi everyone,I'm trying to determine whether this is a bug or if I'm missing something in my configuration.EnvironmentVeeam Backup & Replication Community Edition 13 Build: 13.0.2.29 Proxmox VE 9.2.2 2-node Proxmox cluster Shared QCOW2 storage Backup Proxy/Worker successfully deployed HotAdd transport modeProblemAll Windows VMs are backed up successfully.Any Linux/BSD VM fails with: Failed to perform backup.Failed to prepare disks for backup.So far I have reproduced the issue with:Debian 13 (fresh installation) pfSenseWindows Server VMs work without any issues.What I have already testedCreated a brand new Debian VM → same error Manual snapshot from Proxmox → works Snapshot through Proxmox API (pvesh) → works qemu-img check → no corruption Guest Processing disabled Inventory rescanned Worker redeployed VM migrated between nodes Same storage used by both Windows and Linux VMs Windows backup succeeds using the same repository and proxyExample:pvesh create /nodes/nodo2/qemu/108/snapshot

We are a vmware shop, being priced out.  Many factors pushing us toward Hyper-V.I understand that in the early days ReFS was bug-ridden in multiple aspects.Going forward with Windows 2025 CORE Hyper-V, with VM’s of Windows2022, RHEL 9, and a few linux-based OVA deployments, what is the community recommendation for the format of the iSCSI LUNs that the VM’s run from?  there will be sizes from a couple hundred GB to all the way to 6TB, and in a special case 20TB.Our Veeam Repos are XFS, so not a factor here.Thank you kindly

With my colleague ​@zzsoka  we have developed a procedure the inject needed variables for initial configuration of the Veeam appliances and now we would like to share it with you. When you deploy Linux appliances at scale, cloud‑init is usually the go‑to mechanism for injecting instance‑specific configuration (IP, hostname, NTP, credentials, etc.) at boot time. However, the Veeam Software Appliance used here does not ship with cloud‑init currently, so we need another way to achieve the same result: build one customized ISO and then let vSphere guest variables drive per‑VM configuration.This post walks through how I achieved that using:- a customized Kickstart file,- a customized GRUB configuration,- VMware guestinfo / OVF properties as the source of truth for variables, and- a small shell script that dynamically extracts and uses `vmware-rpctool` (even though open‑vm‑tools is not installed in the installer environment), cleans up after itself, and hands configuration over to the post‑i

This is a tough situation I’ve been fighting for a week. Our windows server (2016) on which veeam Backup & Replication 12 was running on broke and we were unable to make it boot again.After much trying, I setup a new Windows Server (2025) and installed Veeam 12 on it. Before installation I installed MSSQL, imported the database from the old server and used that as an existing DB during installation. We don’t have a .bco Backup.This worked pretty well, all our backups were recognized, our configuration was still there, etc. I managed to restore the connection to our VMWare by re-entering the connection password. Now we have a Linux Backup Proxy. I reset the credentials and a connection can be established, but I am getting these errors now (from Util.VolumesHostDiscover.log): [31.07.2026 15:52:41.908]    <24>   Error (3)    Failed to unprotect data: the actual generation 1be493dd-f053-4957-86cf-06d604afcbdd does not match the expected generation ad168c2e-58e4-49d5-aa58-747ee032

Hi all,Me again, I’ve been wanting to create a scanning tool to get detailed information about file systems to aid in the design of Veeam unstructured backups for a while. I created this tool a few years ago but I thought I’d dust it off and with the help of Claude make it something that the community can use. As always I’ve written it in Rust as it provides fast, multi-threaded scanning.https://github.com/shapedthought/fast-walkIt provides file system information in the following files:results-20260801-160000.csv           totals per extensionresults-20260801-160000-age.csv       totals per age bandresults-20260801-160000-size.csv      totals per size bandresults-20260801-160000-hotspots.csv  directories holding the most small filesresults-20260801-160000-largest.csv   the largest files foundIt also provides the information in the terminal:It also allows you to compare scans to get an idea of change rate over time:I’m looking for testing and feedback on different file systems of which

Veeam has officially introduced Veeam Data Cloud Vault Archive, a new capability designed for long-term backup retention (“cold data”) that helps organizations reduce storage costs while maintaining security and compliance.Key Highlights💰 Lower Storage CostsStores infrequently accessed backups in a cost-effective Archive storage tier. Ideal for long-term retention (5, 7, 10+ years).🔒 Enhanced SecurityImmutable backup storage. End-to-end encryption. Protection against ransomware and accidental or malicious deletion.📋 ComplianceHelps organizations meet regulatory and corporate retention requirements. Simplifies long-term data retention for audits and compliance.⚙️ Simplified ManagementFully managed by Veeam. No need to manually configure Azure Archive Storage or lifecycle policies. Seamlessly integrated with Veeam Data Cloud Vault.📦 Best Use CasesLong-term backup retention. Cold data that is rarely accessed but must be preserved. Organizations looking to reduce cloud storage costs wi

A Hands-On Look at the Next Generation of Cyber ResilienceEvery time I get access to a new Veeam BETA release, I have the same routine. I spin it up in the lab, build out a realistic customer environment, and start testing. While new platform support and performance improvements are always exciting, the first area I wanted to explore in Veeam Backup & Replication 13.1 BETA was security.Over the past few years, customer conversations have changed. We still talk about backup jobs, recovery times, and storage, but today almost every discussion includes ransomware, Zero Trust, immutability, and cyber resilience. Customers want to know one thing:"If we get attacked, can we recover?"After spending time with Veeam 13.1 BETA in our CIC lab, it's clear that security continues to be one of the biggest areas of investment. This release doesn't rely on a single feature to stop threats—it layers multiple technologies together to help organizations detect suspicious activity, protect backup data

I am back this week with blog #6 on the v13 series.  This one takes a look at RBAC in v13.  You can check it out below and on my blog site via the link.Blog - Veeam v13 RBAC: A Simple Operational View Veeam v13 RBAC: A Simple Operational View Introduction Role-based access control becomes more valuable as backup environments grow beyond one or two trusted administrators. In production, the purpose of RBAC is not just to reduce risk on paper. It is to let teams delegate routine work safely while preserving control over the settings that define recoverability.That distinction matters because backup access is often granted too broadly for convenience. When everyone can modify jobs, repositories, and restore actions, the environment becomes harder to audit and easier to disrupt by accident. Map Roles to Responsibilities An effective RBAC model starts with real work, not job titles. Backup operators may need to review failed jobs and rerun tasks, while restore administrators may need access

Today was release the Veeam Backup & Replication. The process of upgrading or updating a Veeam Software Appliance (VSA) is straightforward and performed via the web interface. One of the advantages of using the VSA is that you do not need to manually manage packages and dependencies within the operating system, as the appliance itself handles the update lifecycle.Despite how easy it is, I will show you here how to perform the upgrade procedure. Navigation and Checking for Updates Access the Host Management Console interface of your Veeam Software Appliance. In the left-hand menu, click the Updates button.This screen will show available updates; you can select the Veeam Backup & Replication option and click the Install Updates Now button. Configuration Check and Details Now we need to check some details and look if it have any compatability issues:Installation Process The wizard will take over and automatically begin downloading and applying the packages. A progress bar displayi

I wanted to post this for everyone who uses VB365 and PGBouncer with Postgres with the recent upgrade 8.1.2.180.When trying to run this upgrade I ran in to an issue with the following error which was caused by connecting to Postgres via the PBBouncer 6432 port.  I had to stop services, modify the XML files back to 5432 (default PG port) and then run the upgrade.  Once complete I could then revert back to 6432 for PGBouncer and start up the services again.Error seen during upgrade -    

Hello,We have two Veeam Backup & Replication v12 environments:Veeam Data Platform Essentials Veeam Data Platform FoundationBoth environments are isolated from the Internet, and license updates are performed manually rather than automatically.If we upgrade these environments to Veeam Backup & Replication v13, can we continue using the existing license without importing an updated license file, provided that the current license is still valid and has not expired?The following conditions apply:The current license is still within its validity period. No changes will be made to the edition (Essentials or Foundation). No changes will be made to the number of licensed instances or sockets. The environments will remain offline.Under these conditions, is a license file update required when upgrading from v12 to v13?Thank you.

Hello, I’d like to ask about an issue I’m facing.Recently, I configured Veeam Backup & Restore version 13 to back up my Windows SQL Server. The database backup completed successfully, but when I attempted to restore it on a per‑table basis, I noticed that this cannot be done via the plug‑ins. The interface looks like this:Restore interface for MSSQL Server using Plug‑InsAfter that, I checked the Veeam guide and noticed that if I want to perform a per‑table restore, I first need to configure a staging server in Veeam Explorer for MSSQL. However, when I try to add the staging server, I encounter the following error messages:Staging Server cant be added to ControllerDoes anyone know how to fix this? Any suggestions would be greatly appreciated.

Hello everyone,I'm reaching out today because we're experiencing performance issues with our Veeam backups. More specifically, I find that both the incremental backup duration and the Synthetic Full backup duration are extremely long.Here's a quick overview of our current physical infrastructure:Veeam Backup Server running as a virtual machine (connected at 10 Gbps) - 13.0.2.29 Backup Repository: Synology RS2418+ (Intel Atom C3538, 4 GB RAM, no SSD cache, connected at 10 Gbps) Disks: Disk 1: WDC WD80EFAX-68KNBN0 Disk 2: WDC WD80EFAX-68KNBN0 Disk 3: WDC WD80EFAX-68KNBN0 Disk 4: WDC WD80EFAX-68KNBN0 Disk 5: WDC WD80EFPX-68C4ZN0 (recently added, hence the different model) For every backup job, the bottleneck consistently shows "Target".Backup configurationWe currently have two backup jobs:Job 1Selected production servers Incremental backups: Monday to Friday, starting at 7:00 PM Synthetic Full: Saturday (same start time, as it's not possible to schedule a Synthetic Full earlier than t

When managing backup environments, an error message does not always clearly indicate the actual cause of the problem.In this case, several backup jobs protecting Nutanix AHV virtual machines started failing during the same execution window. Although the failures affected different jobs and VMs, the sessions reported the same error:Failed to perform backup:boost::thread_resource_error: Resource temporarily unavailableFailed to upload disk '72f783a8-b305-481a-b4d7-52e3351ac6c0'Agent failed to process method {DataTransfer.SyncDisk}.At first, the messages related to the disk upload and the DataTransfer.SyncDisk method could suggest a storage, network, or data transfer issue.However, after reviewing the affected sessions and the worker configuration, we identified that the failures were associated with insufficient compute resources available to the workers during a period of high concurrency.In this article, I will explain the environment, the investigation process, the worker configuratio

At the beginning of the year, we faced a critical scenario with one of our clients: a ransomware attack directly compromised the company's main file server. The impact on operations was immediate, as multiple departments depended on these spreadsheets and shared files in real time to keep daily processes running.When a crisis of this magnitude happens, the initial instinct of any technical team is to start restoring data as quickly as possible. However, without organization, the work ends up being duplicated, files may become recontaminated, and the time until full recovery only increases. I have been through this before.In this specific scenario, we had two teams working together: our team and the client's internal team. To avoid conflicts in priorities or misaligned actions between the teams that could compromise the restoration window, incident governance was our first step before executing any command.Below, I share the practical workflow that we aligned on to organize the situatio

Hi all,Before I start this post I humbly request that if you like this project and want me to continue to develop this and other projects, to please share, give it a star on GitHub. It really helps with the motivation. I’ve been wanting an easy way to monitor logs from Veeam products in real-time.https://github.com/shapedthought/logwatchBinary download:https://github.com/shapedthought/logwatch/releasesSo I’ve put together just that, logwatch can monitoring all the files in a folder for changes and you can also recursively monitor all the files in sub-directories. If you enable ssh on your VSA v13 (do carefully!), you can then run the following to get all the first level directories:ssh -n user@server "tail -f /var/log/VeeamBackup/*.log" | logwatch --stdinTo monitor recursively:ssh -n user@server "while true; do find /var/log/VeeamBackup -type f -name '*.log' -print0 | xargs -0 -r tail -n0 -F 2>/dev/null; sleep 1; done" | logwatch --stdin -PYou can also use this with the cloud produc

During a recent implementation, I ran into one of those problems that looks simple after you find the cause, but takes much longer to understand while you are still in the middle of it.The request was to configure Application-Aware Processing for a Linux VM running Oracle and protect its archived redo logs every five minutes.The VM backup was working.Oracle was detected by Veeam.The redo log job was showing success.The problem was that it was transferring exactly 0 B.In this article, I will share the full troubleshooting process, including a few parallel issues we found along the way. They were not all responsible for the 0 B behavior, but they still had to be corrected before the environment could be considered healthy. The environmentThe environment included:VBR 12.3; VMware vSphere; Red Hat Enterprise Linux 8; Oracle Database; Application-Aware Processing; archived redo log backups every five minutes; key-based Linux authentication; an Oracle account with SYSDBA privileges; a VM wit

 With the July 2026 security updates, Microsoft will permanently disable the legacy RC4 encryption algorithm in Kerberos authentication, requiring the use of modern encryption standards such as AES128 and AES256.I do not anticipate any significant impact on systems that are properly maintained, but I strongly recommend carrying out a proactive assessment to identify any systems that still use the RC4 algorithm.Potential RisksLegacy applications, older servers, hardware appliances, or service accounts configured only for RC4 authentication may fail to authenticate after Domain Controllers are updated.How to Verify Your EnvironmentMicrosoft provides tools to detect accounts and services still using RC4:Microsoft Learn: Detect and remediate Kerberos RC4 usageDetect and Remediate RC4 Usage in Kerberos | Microsoft LearnHow to manage Kerberos KDC usage of RC4 for service account ticket issuance changes related to CVE-2026-20833 | Microsoft Support Audit RC4 usageDetail about RC4 usage is sto