Discussion Boards

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? 

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

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% 

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.  

TLDR;set up a linux server as a veeam repository on a proxmox server for local VBR proxmox proxy target? I searched around the community for a bit, so if I missed a good post can you point me at it? We stood up a new site last year and I initially deployed Hyper-V server to run a DC and a file share server at the remote site/branch. Using Hyper-V and Veeam I was happily surprised that Veeam deploys a proxy to back up Hyper-V (mostly was using vmware).I had a local disk attached to the Hyper-V server which acted as a Veeam backup repository. This as a pretty awesome surprise how easily and fast the Veeam backups and restores happened on the Hyper-V server using a USB 3 external hard drive.So Veeam would run jobs to hopefully back up the Hyper-V servers locally and then I would run a disk copy job to pull those backups back to the main site periodically for just in case scenarios, and would also copy the disk copy jobs to a rotating offlin

Hey Veeamers – I just completed the Veeam Data Platform: Monitor, Manage, Analyze (Veeam ONE) training, and this release is packed with power! If you haven’t explored 12.3 yet, you're missing out. This version elevates visibility, analytics, and proactive monitoring to a new level.  Veeam has a reputation for robust data protection, and Veeam ONE 12.3 expands on that with smarter insights, deeper automation, and cleaner, more intuitive dashboards. After the Essentials training, I’m even more excited about its capabilities in real-world environments. What Makes Veeam ONE 12.3 So Exciting?- Next-Level Monitoring & Reporting: From backup job health to infrastructure performance, Veeam ONE provides even more actionable intelligence. The updated alarms and dashboards enhance efficiency by addressing issues before they arise. - Automation that Actually Helps: The remediation actions in 12.3 are seamless. You can observe Veeam ONE diagno

Hello everyone,We are a cloud backup provider and I would like to clarify some doubts before migrating to version 13.We currently use version 12 in the latest available build and will soon migrate to version 13, however my question is:After the update, is it possible to restore the settings in the VSA?And will all Cloud Connect configurations be done in the VSA or in the Veeam Infrastructure Appliance?

How can I import information from a Nutanix platform into the Veeam calculator (https://www.veeam.com/calculators), given that the platform is only compatible with RVTools?I am working on a Nutanix AHV environment with around 660 virtual machines, and I need to perform a proper sizing for my infrastructure.  The Nutanix Collector XLSX file is not compatible with the RVTools format required.  

I was deploying Veeam Backup & Replication v13 in my lab and reviewing the Security & Compliance Analyzer when I noticed a new requirement that I hadn’t seen before: “Credential Guard should be enabled.” I also checked Product KB 4252, but this setting is referenced there but can’t enable it.Can anyone clarify where “Credential Guard” can be enabled for VBR, and whether there is any official documentation from Veeam that covers this requirement?  

I have a single VBR server, using a Data Domain as a repo, and it’s running on VMware. We are migrating from VMware to Nutanix AHV. We’ve already migrated a couple hundred VMs already, and now I’m getting down to needing to move the Veeam server.Doing the migration results in some downtime - the migration process requires that new NIC drivers, etc be installed on the VM. I can easily set the services to manual for that duration, and then restart them when it’s done. BUT … is that the best way to do this? I considered installing a new VBR server natively on Nutanix, and then (somehow) migrating all jobs, etc to it. But the problem is, I only have 1 repo, and I know that multiple VR servers shouldn’t share the same repo. Don’t wanna risk corrupting anything.Has anyone else done this? (migrate a VBR server from one hypervisor to another) If so, what did you do? What should I look out for. Any advice appreciated.

Hello,I noticed something very peculiar. We use the Infrastructure Appliance v13.0.1.1071 for VMware Proxies and hardened repositories. The Backup Server is a Windows box running same version.Every night, we get an eMail saying that check for updates was successful for the Windows Backupserver but failed for all the appliances.When we enable the WebGUI on the appliances and login to their WebGUI’s on port 10433, we go to “Updates” which will say that the last check failed. But when we click on “Check for updates” it works fine. Updates are found, downloaded and installed. All good.So what’s the difference between the automatic daily checks and clicking on “check for updates” on each appliance? We never see the firewall dropping outbound traffic from the appliances around the time the automated daily update checks are done. And the Veeam backup Server (Windows) is the only one, every day, which has no problems checking for updates.The fact that manu

I have two file shares: one for backing up my jobs and one for immutable backups. They are both backing up the same virtual machines. However, my immutable backups keep failing. The immutable repository also shows as Unavailable under Managed Servers.The error I’m getting is: ‘Failed to make the backup file immutable after applying the retention policy: Read-only file system. Unable to open file [.veeam.635.lock] in directory [/BACKUPS/"job_name"] — Error: Read-only file system (POSIX).’

Hello,We’ve recently had to move away from Direct SAN backups as we currently have an open ticket with HPE Nimble regarding an issue affecting that transport mode.In the meantime, we’ve configured Veeam to use HotAdd transport, which is working well for the majority of our environment.However, one specific VM refuses to back up via HotAdd.Environment Summary vSphere environment Backup proxy is a VM within the same cluster HotAdd transport mode (Automatic selection) Fallback to network mode disabled (initially) Veeam account used: adminaccount@vsphere.local (member of vsphere.local\Administrators, inherited from Global Permissions) No snapshot or consolidation warnings on the VM All hosts in cluster have access to the same datastores Problem VM Details VM ha

We’re in the process of migrating from VMWare to Nutanix and have a brand new Veeam installation and repo and we’re testing the backup configurations right now. What we’re seeing is that there is a 60 day expiration on the snapshots Veeam creates during a backup in Nutanix and it doesn’t clean any of them up following the backup. It just keeps stacking snapshots every time it runs and we need it to run daily. In the end we’ll have nearly 300 servers in this environment some of them absolutely massive. Is there a configuration I’m somehow missing here? 

Hi all,I am currently encountering an issue when backing up a very large NAS.Each file share is over 100 TB, and there are more than 3 backup jobs. The backup process has been running for 140 hours and is still only around 10-15% complete.We are currently backing up from a Nutanix file share and using the “Backup directly from file share” method in Veeam. I have split the proxy into two. The first proxy uses the VBR server itself, and the second proxy uses a VM from Nutanix.Is there another way to make the file share backup process faster? Or has anyone else experienced something similar? Because at this point, the backup process will not meet the RPO.  

Hi,I needed to open a support case, however, when clicked on “Open a case” button I was presented with https://www.veeam.com/upgrade.html?return_url=https%3A%2F%2Fmy.veeam.com page requesting additional details to upgrade my profile. Filled out the form, clicked on “Upgrade profile” button - the page basically just refreshes with my data in it, doesn’t proceed further. Tried several times, also in a different browser.Thank you!