Community

For years, we have heard the same prediction: tape is dead.Earlier this year, I had the opportunity to take part in a Veeam Oxford Style Debate around the statement “Tape Is Dead”. The discussion brought up strong arguments on both sides, especially around object storage, immutability, cloud and modern archive solutions. But from my experience working with backup environments, I still believe tape has a place in a modern data protection strategy.Disk storage became faster and more capable, object storage became more accessible, immutable repositories became an important part of ransomware protection, and cloud changed the way organizations think about long-term retention.And yet, tape is still here.Veeam Data Platform 13.1 gave me another reason to revisit that discussion. The platform continues to evolve around new virtualization technologies, storage integrations, security and archive capabilities, while tape is still part of that evolution.So instead of looking at tape as an old tec

Well I have reached blog #10 and the final one in my series about v13.  Check it out below and the link to my blog site as well.  I will be thinking about some new blogs and might do some focused ones on Wasabi among other things.  Stay tuned.Blog - Recon Scanner in v13: Why Backup Admins Should Care Recon Scanner in v13: Why Backup Admins Should Care Introduction Backup administrators are increasingly part of the security response path, whether they planned for that role or not. As backup platforms become more central to resilience planning, features like Recon Scanner matter because they can improve visibility into suspicious conditions that affect recoverability.That does not turn the backup team into a SOC. It does, however, mean that backup operations can no longer ignore security telemetry that may influence restore decisions, protection confidence, or the urgency of administrative action. Why It Matters Operationally A backup platform that can surface signs of abnormal behavior

In the dialog where I can add servers there is no ption for Proxmox.I have Veeam Backup & Replication 13.0.2.29 Enterprise Plus Edition.How do I get the option for Proxmox

Is anyone else  waiting for Veeam support for “Azure Database for PostgreSQL Flexible Server Support” ? It’s been GA since November 2021 and replaced the Single Server which was retired in March 2025, so it seems a bit surprising there is no support to back it up using Veeam, and my support ticket indicated there is no ETA for this feature !This seems a big gap in Azure PaaS support to me. I’d also be interested in any work arounds people have in place. Thanks, Graham 

In today’s digital world, data security is a top priority for organizations. Veeam Backup & Replication has evolved to meet these needs, and one of its key innovations is the Veeam Hardened Repository ISO—a solution designed to protect backup repositories from ransomware and other cyber threats.What Is the Veeam Hardened Repository ISO?The Veeam Hardened Repository ISO is a Linux-based solution that secures backup data by making it immutable. This ensures that data cannot be modified, deleted, or encrypted by unauthorized parties, even in the event of a ransomware attack. The repository allows organizations to set a retention period during which backups remain secure and unaltered.Key Features:Immutability and Retention Locks: Ensures backups are safe from external modifications. Ransomware Protection: Protects backups from being encrypted or deleted by ransomware. Linux-based Security: Utilizes Linux’s built-in security features for enhanced protection. Enhanced Data Availability:

The Ingram Micro Technology caravan was built with a modular design in mind. It was originally built to showcase our product portfolio, with its original design focused on IoT devices and integration. Over time, it evolved and was converted into a mobile datacentre to showcase the Whole ecosystem.It now features an 18RU rack inside and has previously featured HPE routing and switching solutions. As technology changes, so does the caravan, and it continues to evolve to showcase different technologies and use cases. My Latest ChangeRecently, it has gone through its most significant change yet, moving away from the Broadcom VMware hypervisor and now showcasing HPE Morpheus VM Essentials (VME) as its primary hypervisor.As part of the migration, I used Veeam Data Platform (VDP) to back up workloads from VMware and restore (transform) them into HPE VME.I was fortunate to start this project just as the production release of VDP 13.1 became available. Migration ExperienceThis didn't come witho

I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.Relevant logs:[19.01.2026 21:07:36.194]   <126>   Error (1)    Veeam.Backup.IdentityService.Shared.CSystemAccountProvid

Hi all,I had a customer who needed a way to obtain Veeam Software Appliance (VAS) updates within a closed OT/dark site/closed environment.However, the challenge was that they lacked Linux experience and would prefer to do everything in native Windows, without using WSL (Windows Subsystem for Linux). If you have no idea what I am talking about, read this section of the Veeam help center: https://helpcenter.veeam.com/docs/vbr/userguide/update_appliance_configure_updates.html?ver=13#setting-up-custom-update-configurationSo my idea was to build/configure two components:1) A PowerShell script that can be run in Windows to download the necessary files from repository.veeam.com to a computer with internet access and then zip the files into a single large Zip file. 2) Create an IIS server website with all update files needed for the VSA. Then we can easily hand-carry the Zip files from the internet-connected Windows computer to the IIS server in the OT/dark site/closed environment with you pre

Hello,A client have a Quantum LTO server connected by DAS cable to a Windows Server that host Veeam Backup Server. Is it possible in this case to migrate VBveeam Backup Server to a VM and keep access to the tape server ?

We have a scenario where the customer has a Tape Library currently connected to Bacula. Due to an issue with Bacula, they are carrying out a reconstruction or recovery process of the existing backups, which they intend to run from Monday to Friday.At the same time, the customer wants to incorporate Veeam Backup & Replication to perform Backup to Tape jobs during the weekends, using the same Tape Library.The question is to determine how feasible and advisable this approach is, considering that both applications would use the same library at different times, and what considerations or limitations should be taken into account to avoid conflicts in the access and control of the tape drives and media.

Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra

Often when looking at Best Practices guides, software documentation, or even during education, I see and hear the answer “It depends.” This is probably my least favorite answer, as someone who likes to understand why something is right or wrong. While it does “depend,” it makes it very tough for people starting out to understand the “why” in many cases. One thing that is not going to be the same for every Veeam user is how the jobs are created. Over the years, Veeam has made some fantastic changes and for most environments, Per-Machine backups are the way to go, the minimal savings you get do not compare to the performance and portability of this mode.  Additionally, with this mode you can often add a HUGE amount of VM’s to a job and just forget about it. I know of people who have 1 job. That is the definition of an easy button!Today I want to discuss some reasons that myself and others have gone the other direction to separate jobs.  While I keep my jobs as large as I can for the perf

'Why Now' initiative around 13.1 Every time a new version of Veeam is released, the same question comes up:Do I really need to upgrade right now?It’s a fair question.If backups are running, jobs are completing successfully, and restores work, it can be difficult to justify changing an environment that seems to be doing exactly what it was built to do.But I think Veeam Data Platform 13.1 changes that conversation.After spending time working with Veeam 13.1 in the lab, I don't look at this release as simply another collection of new features. The bigger story is how Veeam continues to move from traditional backup and recovery toward a much broader cyber resilience platform.Customers today aren't just asking:“Did my backup complete successfully?”They're asking:“If we're hit with ransomware tonight, how quickly can we recover?”“How do I know the restore point I'm using is clean?”“What happens if Active Directory is compromised?”“Are my backup repositories protected from the attack?”“Have w

It would be nice if you could also upgrade a Cloud Connect server from the Service Provider Console.

I have veeam backup server running in primary site with vcenter integration and backup scheduled and running. Now, I am creating another veeam backup server in DR site, and I want to the same vcenter and esxi to be integrate with DR site veeam backup server. kindly clarify the above approach is correct

Well, another week and another blog as we are at #9 of 10 today.  This blog focuses on Universal CDP and its fitment in to v13.  Check out the link below and the blog.Universal CDP in v13: Where It Fits Universal CDP in v13: Where It Fits Introduction Continuous data protection gets attention because it promises extremely tight recovery points, but that does not mean it belongs everywhere. Universal CDP in Veeam v13 should be evaluated as a targeted design choice for workloads where small amounts of data loss carry outsized business impact.That framing is important in production. CDP is not a replacement for every backup or replication workflow. It is an additional protection method that changes how teams think about network paths, storage performance, and the operational meaning of recovery success. Match CDP to Real Recovery Needs The strongest CDP use cases are the ones where recovery point objectives are already difficult to meet with conventional periodic jobs. Systems with freque

Greetings. On a Veeam 12.3 install, whether there be an NFS or SBM datastore, and even while trying to hold the [CTRL] key and right-clicking on any datastore, the “Access Permissions...” menu does not show up, nor is there a ribbon icon visible for “Set Access Permissions” option.The logged in user into Veeam is a Veeam Backup Administrator. This option is visible on any other Veeam servers tested.What would be the cause for this effect? Thanks in advance.

Recently, I was involved in a production support case where a Veeam software appliance deployed on physical hardware failed to boot after an unexpected power interruption.The system dropped directly into:“You are in emergency mode. Cannot open access to console, the root account is locked.”At this point, many administrators assume the appliance is corrupted or that Veeam needs to be reinstalled. In this case, the backup administrator had already reinstalled VBR once, and the issue happened again.  This is not a Veeam software issue. The problem occurs at the Linux storage layer, specifically with LVM and XFS.The Veeam appliance is built on LVM logical volumes formatted with XFS. During boot, Linux must detect storage, activate LVM volume groups, and mount all filesystems defined in /etc/fstab before any services start.If any of these steps fail, the system enters emergency mode to protect itself. This is a safety mechanism, not a catastrophic failure.Understanding this boot sequence ma

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar

Hi everyone,Another week, another little project. 😀I’ve been spending some of my spare time practicing and experimenting with Codex again, and last weekend’s result is AgentBridge. The idea came from something that has bothered me for a while when working with Veeam Agent management in v13 VSA:VBR does a great job managing Agents once a machine is under management — but starting from V13, onboarding Windows machines in non-domain environments is no longer as straightforward as simply pushing via username and password. Linux certification also require SSH-based preparation and manual steps before they can be added cleanly.For one or two machines, that’s fine. But once you start dealing with more hosts, it quickly becomes painful.So I built AgentBridge.It’s a small open-source tool focused specifically on that initial bootstrap and enrollment process.You run AgentBridge as a single application on Windows, Linux, or macOS, open its local Web UI, connect it to your VBR 13.1 server, and us

Hi everyone! Hope this will be helpful. The idea of the scheme was to imagine everything that could require troubleshooting and put that on the scheme. v13.1 with lots of improvements and new workloads is in progress. Attached you can find both .jpg and .pdf formats, in second one you can put any word in search and find it on the scheme if it exists there. Created in Miro, handmade with lots of user guide research :)

other possible Topic-name: When a PostgreSQL Shows Up That Isn't Yours - A field report on a new AAP warning after the upgrade to 13.1 — including the workaround Veeam Support cleared me to publish.  The symptomAfter upgrading a customers environment (doesn’t matter if VBR on Windows or VSA) to 13.1, a previously clean job started completing with a warning: a VM backup of (in this example) an Exchange server with Application-Aware Processing (AAP) enabled. Exchange processing itself was fine. The warning referred to a PostgreSQL instance that isn't really in access of the customer: an embedded component of (in this case) Trellix/McAfee Email Security running on the same guest OS.The customer told me: Vendor-managed, no credentials, no supported way to administer it.So Veeam can't authenticate against it — and flags that with a warning. The same job ran clean on the previous version.  What changedSupport's original answer was (and i have the confirmation to do this post about it): With

A greeting to allI have deployed a POC of OLVM 4 host Hypervisor version 4.5.4-1.0.31.el8, to replace Vmware infrastructure.I am successfully testing the Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization 4.1. I enclose a fairly comprehensive guide with the ste by steps of configurationWith ISO version 12.1.2.172 the Ovirt KVM plug-in is already installed.for those who do not have latest version of VBR installed download and install the pluginDownload plug inhttps://www.veeam.com/it/products/downloads.html?ad=top-sub-menuVeeam Backup for Oracle Linux Virtualization Manager and Red Hat VirtualizationPerform the following Operations   Architecture OverviewArchitecture Overview - Veeam Backup for Oracle Linux Virtualization Manager and Red Hat Virtualization • Virtualization managerVirtualization manager is a Linux-based physical or virtual machine that manages oVirt resources such as VMs, hosts, clusters, storage domains and networks. • Backup serverA backu