For the past couple of months, I've been plagued by an issue on my Win11 PC of all of my saved sessions with websites on all browsers, steam, discord, etc being signed out and saved passwords cleared. I've narrowed it down to happening when Veeam agent takes a VSS snapshot for my c: full volume backup.
Any idea why and how to stop this from happening?
Hallo Reddit,
ich bin auf ein Problem gestoßen beim Pre-Job Skript von Veeam. Wenn ich hier eine Bedingung rein schreibe. Siehe Bild. Dann gibt er zumindest dank dem Exitcode eine Warnung raus.
Allerdings läuft der Backup Job dann trotzdem durch. Ich möchte dass Veeam dann abbricht mit einer Fehlermeldung und nicht meine Systemplatte belegt. Wenn nichts gemountet ist schreibt Veeam ansonsten alles in den Ordner auf meiner Systemplatte.
Vielleicht könnt ihr mir ja irgendwie helfen.
We have a Hyper-V server (192.168.0.19) with 2 virtual machines that need to be backed up. (60gb and 260gb). separate physical machine running Veeam 12.3 to back them up (192.168.0.5) It backs up to the onsite nas just fine. The offsite nas though is another story.
Recently I moved it to a different offsite location than it was before and replaced the laptop that was acting as the proxy server so now it's synology nas (192.168.4.25) and proxy laptop (windows 11)(192.168.4.15). Main office has a fortigate router and the secondary office has a unifi router if it matters, both with addresses of 192.168.x.1
main office has gigabit internet and secondary office has 50mb/50mb internet however when I run a backup job it won't go above 10 and in fact is usually 5 or lower. The jobs will run for a long time because of this and sometimes the 60gb one will finish but never the 260gb one. errors will either be:
"Failed to pre-process the job Error: The process cannot access the file because it is being used by another process."
or
"Error: An unexpected network error occurred.
Asynchronous request operation has failed. [requestsize = 614400] [offset = 4450836480]"
The jobs default to 192.168.0.19 for proxy server and I can't find the setting to change it.
I've been googling and trying different settings and can't quite seem to find the right combination and now I'm gonna put my hand up and ask for help.
don't be afraid to start with the basics because I could have easily missed something.
Hey everyone - trying to add a Hyper-V cluster using cluster name to newly installed Veeam Backup & Replication built using 'Veeam Software Appliance 13.0.2.29' with default settings and not joined to AD domain. Tried to use the UPN style format and modify the Krb5.conf as per the below KB. DNS is resolving OK.
KB4841: How to Configure krb5.conf for Cross-Domain Hyper-V Cluster Management
TL;DR
TL;DR: Veeam Agent 13.0.3 Bare Metal Recovery on Windows 11 25H2 (Build 26200.8655) instantly fails before writing anything to disk. The backup is detected correctly and disk mapping completes successfully, but the recovery logs show Veeam failing to authenticate with its own local recovery agent: "The Local Security Authority cannot be contacted (System.ComponentModel.Win32Exception)"
Has anyone seen this or found a workaround?
So, I've spent the better part of today troubleshooting this and have narrowed the problem down much further than the generic error message suggests. I'm hoping someone here has seen this before or can point me in the right direction.
The recovery environment appears to function normally.
The backup itself appears to be healthy.
Immediately after pressing Restore, the restore fails in less than one second.
Nothing is written to the SSD.
The GUI reports only:
>
After exporting the recovery logs, I found the following:
[04.07.2026 19:09:45.422] [TlsSocket] Connecting to '[::1]:2500'
[04.07.2026 19:09:45.499] [TlsSocket] Error on authentication
Authentication failed, see inner exception.
(System.Security.Authentication.AuthenticationException)
The Local Security Authority cannot be contacted
(System.ComponentModel.Win32Exception)
Failed to connect to agent 'veeamre-samwn34'
Immediately before the failure:
[TransportService] Connecting to transport service, host 'veeamre-samwn34'
[AgentMngr] Agent has been started
[SocketAgentService] Connecting to agent
[TlsSocket] Connecting to '[::1]:2500'
The logs show that the local recovery agent starts successfully, but the TLS authentication with the local agent fails almost immediately over the loopback interface (::1 / 127.0.0.1).
The full recovery logs are available if anyone would like me to upload them.
Thank you in advance—I really appreciate any ideas.
If someone from Veeam would like additional logs or would like me to test something specific, I'm happy to do so. I've intentionally stopped making changes to the system so it remains in a reproducible state.
Hey everyone,
I'm new to administering veeam br servers and I've been asked to replace our old backup infrastructure to veeam. We've bought two servers with a capacity of 200TB and was wondering if I need to install veeam on both of our servers or only on one ?
If i need to install on both, are they some quirks to be aware of ?
Thanks
Hey everyone!
Has anyone ever created a job where you can backup (not replicate) your server to a different site?
Example: we want to backup a server from our HQ site to our DR Site. We'd be using an Exagrid appliance as our repository.
Hello,
Do I need a separate Veeam Gateway Server if I deploy a Linux Hardened Repository at a remote site connected via a site-to-site (S2S) VPN? Or is the Veeam Gateway only for NFS and SMB, ReFS?
Thank you in advance.
Hi,
we have a bare metal Veeam Backup Server and a Synology NAS that are each connected through dual 10GbE NIC (LAG) to our coreswitch. Our current setup involves the NAS as a SMB repository for Backup copy jobs.
The NAS has a capacity of 110 TB and a full backup consumes around 10 TB. We are struggling to keep our retention policy of 12 monthly restore points due to capacity problems, that's why I wanted to switch from SMB to ReFS in order to utilize fast clone for synthetic fulls.
When asking around, iSCSI with fast clone is always the preferred method. But also with a NAS?
I read in multiple forums that ReFS should not be used on iSCSI on "consumer / prosumer" grade hardware, e. g. a Synology NAS. Is there some truth to it? I'm referring to:
>That means you’re not supposed to format a volume with ReFS as long as it is located on a SAN/NAS device. While reading deeper into the subject, I found out that this sentence might be limited to shared SAN storage.
I did some testing and created the LUN. First thing I noticed is the lower write speed. With SMB, I got around 500 - 600 MB/s, with iSCSI only around 390 MB/s. That wouldn't be huge pain point though, as we'd benefit in terms of storage capacity in comparison to SMB.
So final question - should I stick so SMB or is it safe to migrate to ReFS on Synology iSCSI? The NAS is currently formatted on ext4 and not Btrfs, so this is not an "advanced lun". I can't reformat the NAS because we do not have the spare capacity to copy existing backup copies back and forth.
Hi
I need to find the latest release of Veeam 12 backup and replication and Im getting crazy to find it... all the links that I find on the veeam portal take me to the veeam 13 latest release.
Please could someone bring me a direct link to the downloads for old releases?
thanks
-------------------
EDIT ; https://old.reddit.com/r/Veeam/comments/1teezrg/looking_for_older_version/
We are starting to deploy VEEAM for AWS here and we're curious how others have configured their jobs, especially in larger ENVs with thousands of VMs across multiple accounts.
In our traditional onprem set up we used tagging to place VMs in specific jobs.
So do you just do one job per account or do you have some limits you have for your jobs like no more than 30 or 50? etc? The issue if a backup fails after the retries and you resubmit it's going to submit backups for all of those.....that's ick. Anyway just curious what others are doing.
Hi guys, I am experiencing an issue at the moment where a single 365 mailbox (mail enabled team) is getting stuck on ‘Processing Mailbox’
All other Mailboxes are backing up just fine, and the storage on the mailbox is extremely minimal, so it is extremely unlikely that it’s a timing issue. I have increased the backup window and the amount of parallel runs, which hasn’t helped.
Where can I start to look at what’s causing this to fail? Any other suggestions are appreciated.
Edit: I found an error saying this is a possible Teams chat sync problem, will report back if I find a fix
We currently backup our HyperV VMs (70TB) to an 200TB SOBR comprised of several Linux Immutable Repos. We want to look at instead backing up to AWS S3 IA and then AWS Glacier Deep Archive. We plan to make immutable for 7 days. Retention would be 30 daily, then 8 weekly beyond that, then 12 monthly, then 7 yearly. We are looking at backing up the 30 daily to AWS S3, then everything else to AWS Glacier Deep Archive. But in doing some research was concerned that we would end up being billed for 180 days for the 8 weekly. I appreciate the suggestions. Would be interested in what others do and how jobs are configured.
As title, currently PVE integration only supports Backup operations, not Replication to other PVE Clusters/Hosts. Is VM level Replication on the roadmap? Or is it not something that will be coming at any point ever?
Question probably targetted to people like u/tsmith-co?
Do you have any opinions about .NET software developer position? I've got pretty decent offer from Veeam in Poland in Data Management team and i'm looking for some employee reviews.
What's work culture here? I've heared that in companies of this size there is often big annoying micromanagement which i'm really afraid of since in my current job work culture is great
What about overtime hours? Work-life balance?
General atmosphere? Colleagues and help?
Thank you in advance ;)
My setup is pretty complicated so I will do my best to lay everything out. There are two servers involved: HP Gen8 running ESXI 6.5 free edition and a Gen7 that runs bare-metal windows and is used for Veeam backups.
I bought a HP Gen9 that I plan to migrate everything to Proxmox and ZFS but I ran out of funds putting it together so for the time being that project is on hold.
The main server is a HP DL380P Gen8, it's running ESXI 6.5 free edition. It has internal SFF drives that I split into two different hardware raid configurations; one for VM operating systems and one for a security camera. There is also a 12-bay D2600 enclosure attached to this machine.
There are 3 data stores : 1 datastore for my 3 VM operating systems, 1 datastore for my security camera and 1 very large datastore that is 12x 14TB drives in hardware RAID6. These 12 drives are in a HP D2600 enclosure and plugged into a P822 hardware raid card using a SAS cable.
I wanted one massive drive available for my windows VM but VMWare has an upper limit of 62TB for virtual disks so from my 127TB logical volume I assigned two 62TB disks to my windows fileserver VM and I spanned those disks within windows by creating a dynamic disk. There were 3 or 4TB leftover because I only assigned 124TB of my available 127TB. This ran fine for several years but I started to run out of space with about 11TB free of 124TB. Last month I was trying to be proactive and I remembered those 3-ish TB so within ESXI I added yet another disk to my windows fileserver VM. Within the windows VM I expanded the existing dynamic disk, it grew another ~3TB.
A month went by, everything seemed OK. I intentionally did not run any Veeam backups for a month because I was expecting the disk layout changes to trigger a new active full backup in Veeam. I do not have enough free space on the Gen7 veeam box to hold more than one active full. I usually maintain one full plus 4 weekly deltas. The Gen7 veeam machine has its own 12-bay enclosure and also uses hardware raid (MSA60 and P812).
Yesterday was the day I decided to resume my Veeam backups. I deleted my full backup chain so that I can start over with a new active full today (and then resume weekly deltas going forward) the backup is still running, it's at 12% after about 22 hrs. 16TB processed and 11.4TB transferred. My rough napkin math says that I need 9-10 days total for the active full to complete. I was using the VM normally when suddenly it became unresponsive and now I can't get the VM to start and stay on for more than 5 minutes. The error message from VMWare is below :
2026-06-23T01:20:16.178Z| vmx| I125: [msg.hbacommon.outofspace] There is no more space for virtual disk '/vmfs/volumes/61affab3-0428df4e-d4af-.../REDACTED_VM_NAME_4-000001.vmdk'. You might be able to continue this session by freeing disk space on the relevant volume, and clicking Retry. Click Cancel to terminate this session.
I'm a little bit confused by this and my only assumption is that the veeam snapshot has started to encroach upon the 127TB that I have assigned to this VM. Interestingly it's disk4 that ran out of space and that is one of the original 62TB virtual disks. Disk layout for this VM is as follows :
DISK1 (thin provisioned) : Windows OS
DISK2 (thick provision, lazy zero) : Security Cam (deprecated, I don't record any longer)
DISK3 (thick provision, lazy zero) : 62TB
DISK4 (thick provision, lazy zero) : 62TB
DISK5 (thick provision, lazy zero) : 3.3199999993667006TB
-disk 3,4,5 are physically the same device (12-bay RAID6)
-disk 1 is its own device (internal drives, RAID10)
-disk 2 is its own device (internal drives, RAID-something) - I don't care about this disk and I would even junk it if that meant I could in-place expand my 127TB datastore and get the VM back up and running even temporarily.
I don't know if I should cancel the veeam backup or let it complete. What do y'all think about this predicament? I'm really torn about what my next steps should be. Without my Veeam backup I do not have any other copies of this data.
-on one hand if I'm able to get the backup to complete successfully I will have a safe copy of my data. I can use Veeam to restore between hypervisors vmware>proxmox so maybe once I have a backup I just bite the bullet and buy drives for my Gen9 (which has 15 internal LFF bays BTW). I was thinking I could even reuse some or all of the drives from the Gen8 and put them in the Gen9. 1x RAIDZ2 or a pool consisting of 1 or two RAIDZ or RAIDZ2. The Gen9 has dual 14C/28T CPU and 384GB of LRDIMM so I shouldn't have any issue running a 200+TB ZFS and assigning it all in one chunk to the windows VM. I would probably have to restore in sections : 1. Restore the VM themselves (OS), then setup a new large disk and then manually copy over from veeam to windows VM.
-on the other hand I'm concerned that the Veeam snapshot is going to continue to grow, start chewing into my usable portion of 127TB and start corrupting my data.
I would appreciate any and all ideas, suggestions, recommendations.
Sincerely, a very panicked reddit user.
edit, some spelling mistakes
Hello Veeamers!
We are currently reviewing our object storage strategy and looking to replace AWS S3 with something cheaper and easier to operate (for example, getting rid of those annoying ephemeral instances required for archival tiering).
Today our use case is Veeam only, but we are also considering if having a general purpose S3 platform could provide additional value in the future.
Our shortlist:
• Veeam Data Cloud Vault
• Wasabi
• Backblaze B2
A few questions for those running these solutions in production:
Cheers guys, any experience is appreciated!
how can i use volume GUID as repository for veeam B&R 13? thanks.
use windows letters is insecure.
host hyper-v windows server 2025.
target : iscsi lun on qnap.
Hey all, looking for some opinions from people who’ve actually done this in production.
I’m setting up two Veeam Backup for Proxmox VE servers on a dedicated Dell R740xd2 with 116TB usable RAID60. It’s a single Proxmox host, not part of a cluster, and it’s only used to host the two Veeam servers + their repos.
I know best practice is to run Veeam B&R on bare metal, but we don’t have a 2nd physical server to host the second Veeam B&R — so virtualizing it on this Proxmox host is the realistic option for us.
The host isn’t running any production VMs — but we keep it sized/configured so we could spin up a few critical VMs on it in emergencies (e.g. if both production clusters we back up go down at the same time).
Plan is roughly:
The thing I’m trying to decide is the actual server type for the Veeam repos.
I’ve gone back and forth between:
Right now I’m leaning towards option 3 because:
But part of me still wonders if LXC + LVM passthrough is "good enough" since the box is dedicated and not running production workloads.
A few questions for anyone running similar setups:
Not chasing absolute max performance — bottleneck during backups is the source side anyway. Just want a setup that’s clean, reliable, and won’t bite me in a year.
Appreciate any input 🙏
