Community

I recently wrote a blog about VSA HA Clustering, which you can find below (link to my site is below as well).Veeam VSA HA Cluster Setup With the release of Veeam Backup & Replication 13 there is a new feature that you can use to set up two nodes in an HA Cluster configuration for high availability.  I am going to outline the process below and keep in mind that you will need to have a VDP Premium license in order to do this as that is a hard requirement.  Now let’s look at HA Clustering with Veeam VSA.Configuring a Veeam VSA HA ClusterThe HA cluster configuration process involves two major phases: enabling the HA feature on both nodes via the Host Management Console, and then assembling the cluster through the Veeam Backup & Replication Console.

  Microsoft's position on your 365 data is the same as Salesforce's: they keep the service running, you keep the data safe. Deleted items come back from the recycle bin for 93 days if you are lucky. After that, they are gone. Retention policies are not backup, they were designed for compliance, not recovery. Veeam Backup for Microsoft 365 v8 is the current answer to this problem, and v8 is a significant architectural shift from v7. This article covers what changed in v8, how to deploy it, how to configure jobs for all four workloads, and how the Explorers work when you actually need to recover something. What Microsoft Does Not Cover Exchange Online retention policies keep deleted items in a recoverable state temporarily. SharePoint and OneDrive versioning he

HiI am planning to deploy Veeam Backup & Replication v13 using the Veeam Infrastructure Appliance with a Hardened Repository configuration.My question is about capacity expansion during production operation.If the backup storage becomes insufficient after the appliance has been deployed and is already in use,is it a supported operation to add an additional virtual disk to the appliance VM and expand the backup storage capacity (for example, extending the repository storage)?Specifically, I would like to understand:Whether adding a new virtual disk to the Veeam Infrastructure Appliance VM is officially supportedWhether this applies to a Hardened Repository configurationIf there are any restrictions, best practices, or unsupported scenarios we should be aware ofThe goal is to increase backup capacity without redeploying the appliance.If there is any official documentation or guidance from Veeam regarding this sce

Hi all, Sorry if this has been covered, I couldn’t find it in the search. I have a HyperV host and I want to use VAW to backup the D drive containing the HyperV VM files.  I have 2 USB disks I plan to rotate.  I’ve read the guides and I have registered both the USB disks as storage devices.  Last night it failed and I am suspecting it was due to the drive letter not being assigned when it got reconnected.  In theory, am I OK to simply leave one disk plugged in and VAW will do the backup to that disk, if there is a drive letter assigned?   Thanks.  

Hi, I tried using Veeam Agent for Windows on my 2025 Server to backup a D drive.  The backup destination was a couple of USB disks which I registered with VAW and I wanted to use the disks on rotation.  That backup job failed with some problem about VAW insisting on using the same USB disk each time, plus my colleague convinced me to use the community version of Veeam Backup & Replication, so I started again. I’ve installed VBR, created a repository using one of the USB disks and did my first backup.  All ok.  Then I re-ran the job 5 mins later with the same USB disk still plugged in, so no disk change/no rotation, as I wanted to see if it created the VIB file.  Nope!  I got this: Processing New Backup_Job_1 Error: Update of the storage [E:\Backups\SRV02\New SRV02.c5c62b19-d1f0-4e8e-864d-3da8e38f3D2026-03-30T222815_7C96.vib] is not supported. Storage version: [0]. Failed to open storage for read/write access. Storage: [E:\Backups\SRV02\Ne

Every time I try to open a case in my Veeam portal, I get a permission error that I can’t:Which is odd as I am the admin for our license, and I can’t raise a ticket to say I can’t raise a ticket as it always goes back to this error. Can’t use phone support as you need a case number from raising a case. Could someone from Veeam help sort this out? RegadsDamien

Hi Team,I am getting this warning during a Veeam Agent backup: Warning: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instance XYZ. The backup completes successfully and application aware processing is enabled, but the SQL logs are not truncating. Any idea what could cause this or what I should check next? Thanks.  

How we can make exclusion for virus warning when backup m365 using VBO? 

It was a holiday weekend here in Brazil, Carnival, and I was off when I got the call around noon.A client had been hit by a ransomware attack.The entry point was a phishing email that compromised a workstation. From there, the attacker managed to move laterally, reach Active Directory, and eventually gain access to the entire environment.By the time I was involved, most of the damage was already done.Around 50TB of Windows-based VMs were encrypted. Production was down.The environment did have antivirus in place, but it wasn’t properly configured to stop that kind of behavior. In the end, it wasn’t enough.  At that moment, the biggest challenge wasn’t just restor

Hello everyone,I am currently configuring Veeam Backup for Microsoft 365 (VBM365) for our company, and I have a question about the disk cache to optimise performance.According to the documentation, the standard installation does not allow the cache to be stored on another drive on the VBM365 server (it is located by default in the local PostgreSQL database on the C drive or on a dedicated PostgreSQL server). However, I would like to avoid deploying an additional PostgreSQL server for simplicity and maintenance reasons. My question:Does anybody use a dedicated cache disk on the VBM365 server? If so, how did you configure it (custom path, script, etc.)? Have you encountered any limitations or performance issues? I would appreciate your feedback or alternative solutions (without external PostgreSQL).Thank you in advance for your advice!Morgan

In this article, I'll take you through five different restore scenarios I've tested in my lab, and you should do the same.You’ve got green checkmarks.Your jobs are running.Storage looks fine.Everything seems good.But here’s the uncomfortable truth I’ve learned the hard way:A successful backup job does not mean a successful recovery.Day 2 operations is where this really hits. This is the phase where you stop asking “Did it back up?” and start asking:“Can I actually get my data back when it matters?”If you’re not actively testing restores, you’re running on assumptions—and assumptions don’t survive outages, corruption, or ransomware.Here are five restore scenarios you should be testing regularly (but most people don’t). 1. Full VM Restore (The “Everything Is Gone” Scenario)This is the big one.The “we lost the entire server” moment.

Repost of topic on the RND forums, but figured to share this here as well: Sharing this tidbit here as there are quite a few topics on how to do session reporting on all job types including the plugin-based Hypervisors (aka PlatformBackups, for example Proxmox, Nutanix, HPE Morpheus, etc)Normally you would pass a CJob object from Get-VBRJob to Get-VBRSession -Job, but regrettably this will currently error with many job types:Get-VBRSession: Cannot bind parameter 'Job'. Cannot convert value "Veeam.Backup.Core.CBackupJob" to type "Veeam.Backup.PowerShell.Infos.VBRJob". Error: "The given key 'VmbApiPolicyTempJob' was not present in the dictionary."However, we can do a little magic trick with Get-V

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.

I was wondering if someone could help with an issue I’m having in Veeam agent for windows, I get the following error when trying to restore files from a volume backup stored on a network share. I’m using the agent in free mode.Backup sync failed[computer_name] Failed to connect to installer service[computer_name] Failed to connect to installer service[computer_name] Failed to discover installer serviceA security package specific error occurredConnect failed (RpcBindingSetAuthInfoExW)Please can you help me resolve this?

Introduction Veeam Backup and Replication v13.0.1 supports a direct in-place upgrade from v12.3.1 build 12.3.1.1139 or later on Windows. The installer runs a hard configuration check before the upgrade proceeds and will stop on several specific conditions. This post summarizes the full upgrade process -- blockers, deprecated features, platform changes, component order, wizard walkthrough, and known post-upgrade issues -- based on the official Veeam documentation and confirmed community experience. Full article with expanded tables and PowerShell references at anystackarchitect.com.Supported Upgrade Path Direct in-place upgrade to v13.0.1 requires v12.3.1 build 12.3.1.1139 or later. See KB4763 for the official version requirement. If below that build, update to v12.3.1 first (KB4696), then upgrade to v13. 

Not sure how useful this will be for anyone else, but should you need to parse through your logs on all gateway servers for S3 errors returned during Veeam operations with Object Storage, this script is for you.Script requires ripgrep to be installed on the Backup Server: https://github.com/BurntSushi/ripgrep?tab=readme-ov-file#installationIf you cannot install / use chocolately in your environment, download the ripgrep binary appropriate for your OS, and edit the script as noted in comment [2]. What it does:Collect all Object Storage Repsositories Get Ids for all assigned gateways Collect all gateways with Get-VBRServer cmdlet to create array of gateways Iterate over each gateway and do the following: Export logs JUST for that ga

We are currently using Amazon S3 Standard as the Capacity Tier and S3 Glacier as the Archive Tier for offsite backups in the AWS region.We are now looking to implement Capacity Tier replication to another AWS region.Backup configuration:Daily incremental backups and weekly synthetic full backups Backups are retained in the Capacity Tier for 15 days After 15 days, weekly backups are moved to the Archive Tier (Glacier)Please advise on the best approach to configure replication of backup data between AWS regions for capacity tier

Hi Team, We are updating VBR from version 12.3.2.4165 to 12.3.2.4465 and we VAL and RMAN which are in version 6.3.2.1207 and 12.3.1.1139 My Question is after the VBR upgrade will RMAN and Linux agent backup works with existing version or do we need to update agents as well immediately 

I already have a ticket open on this, but while Im waiting does anyone have any suggestions on things to try. Unfortunately, to make things complicated this only started happening after we upgraded to V13 and also upgraded the firmware on our exagrids. We are using storage integrated backups with Pure. I have not updated the Storage Array plugin yet. I have rescanned everything I could possibly rescan and all backups still sit at 0% 

 We recently completed an upgrade of Veeam Service Provider Console (VSPC) from version 8.1 to version 9.1 in a large-scale, multi-tenant service provider environment. From an infrastructure standpoint, the upgrade was uneventful in the best possible way. All core services came online cleanly, communication between components remained stable, and backup operations continued without disruption. Pre and post-upgrade validation confirmed that the platform was operating as expected. During routine post-upgrade review, particularly within the Managed Computers section, we observed that a subset of endpoints had management agent upgrades that were not completing successfully. After reviewing task logs across multiple tenants, it became clear that these were not platform-related issues, but conditions specific to individual endpoints that surfaced during the agent upgrade cycle. Given the scale and diversity typical in service

Dear AllGreetings!!!I fany one face this issue please let me know.Server Error in Veeam one - One or more critical product files have been modified. Please roll back the changes, or reinstall the product.After login into Web console of Veeam One i am getting this error message.Running Version is : 13.0.1.6168 

I am trying to restore Ubuntu VM to Azure but never got any success. We had issue with ver 12.3 where it never create helper appliance for the region so we upgraded to ver 13. It now try to create helper appliance but never complete succesfully. When restore process starts, it creates helper appliance in Azure with status running but never get pass that stage. Internet access is restricted to outbound access to windows update, azure & Veeam.I even tried restoring the Azure environment where we have ipsec tunnel but not luck, still fail with same error.