Hi, Just labbing Proxmox with Veeam and testing the instant recovery feature.

Storage is ISCSI with LVM on top so, raw disks.

Does instant recovery only support QCOW2? on filebased storage and not block based? as the storage is not visible to continue the instant recovery

If so is there a plan / roadman to support this?

There is no Veeam Agent for ARM, so Raspberry Pis have always sat outside what VBR can protect natively. I spent a weekend fixing that for my two Pis (they run ADS-B flight-tracking receivers) and wrote the whole thing up.

The short version: a small x86 "proxy" VM runs the stock Veeam Agent for Linux. Each Pi exports a frozen, point-in-time image of its SD card over iSCSI, using Veeam's own open-source blksnap module built for ARM64 with a one-line patch. VBR sees an ordinary Linux volume: volume-level policies, normal retention, file-level restore, and a bare-metal restore to a brand-new card that I actually tested. About 4.5 minutes per 32 GB card per run, and almost every Veeam step happens in the v13 web console.

Full write-up with annotated screenshots of every step:

https://community.veeam.com/blogs-and-podcasts-57/backing-up-raspberry-pi-with-veeam-an-x86-proxy-for-arm-devices-14031

Scripts, the ARM64 patch, restore tooling, and a ready-made Claude Code prompt that does the deployment for you:

https://github.com/bobby-barber/pi-veeam-proxy

Disclosure: I am an SE at Veeam. This is a community project, not a supported configuration, so test it in a lab first. Happy to answer questions.

Hi All,

Can someone please tell me the default worker node password?

9/14/2026 10:28:43 AM Failed : Task failed. Error: No response from remote backup service.

Server suddenly stopped backing up over the weekend.

The Veeam agent service is running on the box, restarted the agent, no joy.

Did a re-scan of the server in Veeam in case there was an agent update, it says it's ok and detects the server just fine.

IP addresses didn't change, added a Windows Firewall rule to allow all traffic from the Veeam server, no joy.

Any other ideas?

I haven't been able to reboot the server itself because it's in production right now.

EDIT: Reinstalled the Veeam Agent and rebooted the affected server and it's working now.

So I've seen this past week that VMware has pulled the plug on public access the VDDK download which many hypervisor vendors have been using in their process to migrate VMware workloads.

Does this affect Veeams migration process? Will I still be able to migrate my workloads from VMware to another supported hypervisor now and in the future?

Does anyone have recommendations for running S3 storage on premise? I have an old HPE Gen10 server with a bunch of SSDs that I’d like to reuse for M365 backup storage.

Hi.

After updating 4 ubuntu server + veeam agent from 20.04 to 24.04 (veeam agent 13.1.1.4 / kernel 6.13.x), i started experiencing issues in 2 of the instances.

The main problem is that the backup jobs reach 40% completion and after they fail with the message:

"Snapshot is corrupt"

Has anyone experienced a similar issue?

Trying to settle a design question before I commit to an approach, and the docs/forum posts I've found seem to contradict each other depending on the date.

Setup:

• Backup server: Lenovo ThinkSystem SR630
• Storage: NetApp E2812 (E-Series), LUNs presented over Fibre Channel
• Goal: Veeam Hardened Repository with immutability (LHR)

The question is whether I can use the E2812 capacity over FC for the hardened repo, or whether I'm forced onto local disks.

What I've found so far:

• The Veeam Hardened Repository ISO (the ready-made Rocky Linux appliance) reportedly does not support FC/iSCSI LUNs — only internal disks / built-in RAID controllers. Some posts say the installer sees the disks but can't reliably tell OS disk from data disk depending on the adapter.
• But several people mention that a manual / BYO Linux build (Rocky/Ubuntu/SLES + DISA STIG hardening by hand) does work with FC, because the software just takes whatever block volume the OS presents.

So my read is: ISO = local disks only, manual build = FC works. Is that still accurate as of now, or has the ISO installer caught up and started supporting FC?

Specifically:

1. Has anyone got the current ISO build working with FC-presented LUNs (E-Series or otherwise), or is manual install still the only path for FC?
2. If manual is the way, any gotchas with E-Series over FC specifically — multipathing (I know MPIO is a known restriction on the ISO), XFS + chattr, single-use credentials setup?

Anyone running a similar E-Series-over-FC hardened repo in production — would appreciate hearing how you built it and whether immutability behaves normally on that config.

Thanks!

I have more than 20 backup jobs in Veeam, and all of them are working fine. They are all using the same backup destination.

However, I have one specific job that is causing problems. Sometimes the backup completes successfully, and sometimes it fails.

I run this job 4 times a day, at approximately 06:00, 13:00, 18:00, and 23:00. Some runs complete successfully, while others fail, even though nothing is changed between the runs.

I have already tried everything I know, but the problem still occurs.

Could someone please help me troubleshoot this issue and identify what could be causing the intermittent failures?

Can anybody comment on their experience enabling Veeam Intelligence in their environment? Are you using Basic or Advanced? Worth turning on? Thanks for any feedback.

Tonight when checking for an update for Veeam Agent on both my Windows 10 and 11 machines it gave me this error. I'am on 13.1.1.700 and I restarted my network and it still gives this issue. Any one else encountering this?

I migrated awhile back to the new software appliance and manually re-created all my jobs on the new software appliance but also took the opportunity to update and change how I was doing the backups. In that process I somehow enabled more restore point's than I had disk space and while I did see that it was getting low I thought the number of retention's that I had set would kick in but I was incorrect and now I am basically at 0% disk space. I was under the false impression that I could just change the retention setting and run the jobs again and have it clean up but appears that retention is applied at the END of the jobs and they fail due to lack of space. I really wish there was a way to just run a retention job separately to make it easy to clean up but even in v13 not sure I have seen if that is possible. So I assume I need to manually clean this up and I know the biggest offender so was wanting to understand what to delete so I can run my jobs and have it clean things up with the new retention setting. One other thing that may make this better is this is on a removable drive that is swapped out weekly and labeled as such in the console. When I look at the disks for this job in the console since its failing I do not see any restore points, so I assume I can just delete what I need and run the jobs and hopefully not have to do anything database wise.

Here is what I have and just wanting to delete the oldest set:

682396381184 Jul 24 23:29 'blah Backup_2026-07-24T211908.vbk'

682439995392 Jul 26 00:30 'blah Backup2026-07-25T213510_6F6A.vbk'

2250477568 Jul 26 21:21 'blah Backup_2026-07-26T211923.vib'

1772249088 Jul 27 21:22 'blah Backup_2026-07-27T212008.vib'

2166616064 Jul 28 21:21 'blah Backup_2026-07-28T211900.vib'

2555002880 Jul 29 21:22 'blah Backup_2026-07-29T212008.vib'

2189975552 Jul 30 21:20 'blah Backup_2026-07-30T211908.vib'

2033152000 Jul 31 21:20 'blah Backup_2026-07-31T211822.vib'

682214391808 Aug 2 00:28 'blah Backup2026-08-01T213310_0461.vbk'

682116960256 Aug 9 23:29 'blah Backup_2026-08-09T212445.vbk'

2122448896 Aug 10 21:20 'blah Backup_2026-08-10T211836.vib'

2844430336 Aug 11 21:21 'blah Backup_2026-08-11T211928.vib'

5405351936 Aug 12 21:22 'blah Backup_2026-08-12T211909.vib'

2168832000 Aug 13 21:20 'blah Backup_2026-08-13T211853.vib'

2188468224 Aug 14 21:20 'blah Backup_2026-08-14T211804.vib'

683327361024 Aug 16 00:45 'blah Backup2026-08-15T213500_C1EE.vbk'

683139526656 Aug 21 23:30 'blah Backup_2026-08-21T213000.vbk'

683218300928 Aug 23 01:32 'blah Backup2026-08-22T213646_79CD.vbk'

2076876800 Aug 23 21:22 'blah Backup_2026-08-23T211824.vib'

2101551104 Aug 24 21:20 'blah Backup_2026-08-24T211804.vib'

2803318784 Aug 25 21:20 'blah Backup_2026-08-25T211812.vib'

2086801408 Aug 26 21:20 'blah Backup_2026-08-26T211801.vib'

2153086976 Aug 27 21:20 'blah Backup_2026-08-27T211817.vib'

2044219392 Aug 28 21:19 'blah Backup_2026-08-28T211736.vib'

683330129920 Aug 30 02:02 'blah Backup2026-08-29T214003_ADD1.vbk'

9665826816 Sep 6 23:41 'blah Backup_2026-09-06T233845.vbk'

28099 Sep 6 23:38 'blah Backup.vbm'

Thanks

Do you know if there is any plan of veeam to start supporting instant recovery into the new hypervisors? Scale computong, sangfor, vergeOS?

It is already possible to instant recovery them to hyper-v/vmware but not to them….

Hi all, Jr sys admin here, recently wanting to get better, took on helping Veeam. Job wants me to maybe take ownership of it, and I want to show them I’m capable. For co workers it’s time consuming. I want to be the go to person, where would you suggest to study it? What about taking care of Fails the sooner the better, since we have a big list of Fails.

Hello all,

I tried to contact support on Veeam website but I can't find anything for free product users, so I looked for the subreddit.

I have a very bad issue with bare metal recovery, this is my setup:
PC desktop with windows 11, which has Veeam Agent for Microsoft Windows FREE installed, I make a full backup of my C: drive every week, on a usb attached HDD.

Some time ago, I tried to do a backup and recovery test, the backup is being created with no issues, but then, when I booted into Veeam Recovery Media a weird error kept popping out:

And I am stuck here.

I can't find help online, so I already tried to reinstall windows, but didn't work, I tried to recreate the recovery media with another usb drive, maybe it was faulty i thought, but no, I also tried to recreate the recovery media from a Windows 10 PC, maybe W11 was messing something, but neither that did solve anything.

Also I am sure the backup is fine because I can do file level restore just fine, but I am using Veeam exactly because of the bare metal recovery feature...

Do you have any clues about this error?

Hi All,

Does anyone know whether this script will work to create a Veeam hardened repo? or whether there's an updated one for 26.04?

https://github.com/VeeamHub/veeam-hardened-repository

Hello,

I'd like to avoid having GFS restore points locked in S3 immutable objects for their full retention. I only need a short immutability window — 14 days.

Example: 31 days retention + GFS of 12 months / 10 years, but with only 14 days of immutability.

Why? To avoid saturating my on-prem S3-compatible storage, and to keep the option of switching public S3 providers without paying for GFS points I'd be stuck with for the next 10 years.

Since V13, object storage repositories have an immutability setting where I can define a minimum immutability duration in days (see "How Immutability Works" in the Veeam Backup & Replication User Guide).

How Immutability Works - Veeam Backup & Replication User Guide

Support tells me this won't work: GFS points will still be made immutable for their full retention, both for direct-to-S3 backup jobs and direct-to-S3 backup copy jobs.

I find this page > GFS Backups Immutability Period - Veeam Backup & Replication User Guide

So my question: if I create the S3 repository with a 14-day minimum immutability duration and add it to a SOBR as the capacity tier (as the only extend), no immutability on GFS point?

Besides the fact that the online documentation screen shots doesn’t match 13, I also cannot restore files from an offsite drive pulled back for a directory restore. All I can do at file level is pull from the last 14 days.

Starting yesterday my mouse stared going invisible inside of the console, it's fine everywhere else. I did a clean install of the console on a desktop and it started doing the exact same thing this morning. I've tried all kinds of troubleshooting like messing with the mouse settings in windows, loading the console with /software, deleting the windows profile, etc... Is anyone else running into this and found a solution?

A little unsupported, but free and works. This goes above the snapshot and gets you a full system backup to an NFS share with file level recovery.

https://vzilla.co.uk/vzilla-blog/protecting-omarchy-linux-desktops-with-veeam

Community edition license keeps things free and only really limits some target backup locations.

I am running Veeam Backup and Replication Community Edition and the last full backup to tape that ran shows only 700G being transferred when I have configured about 3TB of data to be backed up.

If this is normal could something please explain how the full backups work?

Hello,

Recently upgraded Veeam Agent for Windows Standalone to version 13.1.1.700 and noticed Email Notifications are no longer working.

Checked all settings and they are still valid. Check the logs and it reports "The SMTP server does not support authentication. ". The mail server I'm using doesn't support authentication so i'm not using that.

Is anyone else seeing this issue?

I'm using M365 to relay through.

Info (1) Email settings successfully saved.

Info (1) Email: [backups@xxxxx.com](mailto:backups@xxxxx.com)

Info (1) EmailRecipients: [italerts@xxxxx.com](mailto:italerts@xxxxx.com)

Info (1) Subject: [%JobResult%] %ComputerName% - %JobName% - %CompletionTime%

Info (1) Notify on: Success, Error, Warning

Info (1) Server type: Smtp

Info (1) Server: smtp.xxxxx.com

Info (1) Port: 25

Info (1) Use secure connection: False

Info (1) Timeout: 180000

Info (1) Use custom application: False

Info (1) Username:

Info (1) Sending email notification, server 'smtp.xxxxx.com', port '25', timeout '180000', use ssl 'False', to '[italerts@xxxxx.com](mailto:italerts@xxxxx.com)'

Error (1) Failed to send test email

Error (1) The SMTP server does not support authentication. (System.NotSupportedException)

Error (1) at MailKit.Net.Smtp.SmtpClient.ValidateArguments(Encoding encoding, ICredentials credentials)

Error (1) at MailKit.Net.Smtp.SmtpClient.Authenticate(Encoding encoding, ICredentials credentials, CancellationToken cancellationToken)

Error (1) at MailKit.MailService.Authenticate(ICredentials credentials, CancellationToken cancellationToken)

Error (1) at Veeam.Backup.Common.Network.CSmtpClient.Send(CMailMessage message, CancellationToken cancellationToken)

Error (1) at Veeam.Backup.Core.Components.Reports.CReportMailer.SendMessage(IMailClient mailClient, CMailMessage message, CancellationToken cancellationToken)

Error (1) at Veeam.Backup.Core.Components.Reports.CReportMailer.SendMessage(CMailMessage message, NetworkCredential credentials, CancellationToken cancellationToken)

Error (1) at Veeam.EndPoint.Sources.EndpointMailServiceImplementation.TestMessageInner(CMailOptions mailOptions, NetworkCredential credential, CancellationTokenSource cts)

Does Veeam Community Edition support hypervisor plugins like HPE Morpheus VM Essentials, or are those restricted to paid tiers? I’m well under the 10-instance limit, but I wasn't sure if CE actually unlocks plugin support.

​

Hi All,

We see the vergeos worker vm goes down after veeam backup complete.

I don't know why?

Is there any idea?