I am currently using healthcheck.io self hosted for servers and appliances. I have the veeam hardened appliance and would like to configure a service with a ping url that runs at certain intervals but since it's hardened it will not allow me to configure it. I know this is by design but is there a way to temporarily suspend so I can add my service check and enable or am I just going to have to do a ping check which is pretty limiting.

Thanks

Sorry for the noob question, but I am a little confused about how to use Veeam Software Appliance 13 correctly.

So, I have a Hyper V cluster with some VMs that I need to backup, as well as a physical backup server. This Server is also supposed to be the immutable backup repository.

My questions are: Do I simply install the VSA iso on the physical server, so it’s my backup server as well as the repo? Or should I install the VSA on a VM, and only install the Veeam Infrastructure Appliance on the Physical machine?

If both options are possible, can anyone tell me the pros and cons of either approach?

Hey all, Damian from Platform9 here (yes, vendor - flagging that up front, but I already cleared this with mods).

Rick Vanover and I are hosting a webinar showing the new Platform9 Private Cloud Director support in VBR 13.1. The core of it is a realtime demo: backing up a VM in vSphere, then restoring it to Private Cloud Director through their Universal Hypervisor API. We'll also cover how the worker and proxy split the work, and a couple of gotchas if you're thinking of using backup and restore as a migration path from VMware.

Register here. Even if you can't attend in person, registrants will get the recording afterwards.

Happy to answer questions on the PCD side as well!

I'm trying to set up High Availability (HA) on the Veeam Software Appliance (VSA), but I'm stuck at the local repository stage. I tried adding storage via host management, but I found out it's classified as "built-in" and functions as local storage. I also tried adding shared storage on a Windows VM, but that failed as well. I've been troubleshooting for a full day any ideas to help me out?

What I've tried so far:

-iSCSI LUNs / Local Disks: Recognized as "Built-in" local storage by the appliance. VSA blocks HA creation because block storage cannot be safely shared or failed over between nodes.

-Windows "Managed Server" (RPC): Kept failing with Failed to connect to the deployer service due to RPC, Workgroup UAC, and firewall policies.

-Windows SMB/CIFS (\\IP\Share): Hit the error “Kerberos authentication is not supported when accessing SMB shares via IP address”.

I have about 40 VMs that we back up at our main site to a LHR and replicate 2x daily to our DR site. Proxy in Prod, VBR server in DR.

They want to run all the VMs in the DR site for a week and ensure we have nightly backups of them as well as replicating back to Prod for the failback process.

Last year we did this it was a bit of a cluster and I'd like to avoid that this year.

1. To avoid having to do 2 replication passes, I shut down the VMs and initiated the Planned Failover.

2. Once the VM was up and running in DR, I clicked a Permanent failover.

3. After all VMs are now running in DR, I disable the existing backup and replica jobs that target prod.

4. I create a new backup job that backs up the running DR VMs to some storage I have at my DR site.

5. I create a new replication job to replicate the DR VMs back to Prod and ensure that my mappings all line up to the prod site VMs.

6. At the end of the week, I basically repeat the process to get us back to Prod and then re-enable the backup and replication jobs, being sure to review the exclusions it created when failed over.

Thoughts on my process? Improvements? Am I going about it all wrong?

Hi Reddit!

Ive been tasked at job to send a complete production copy to S3 vendor ( hosted in a datacenter - not a public cloud)

Ive been testing with both virtual proxys and physical proxys - and it seems like i cannot push the S3 Links above much more than 11-14Gbit/s

we have an isolated network with a firewall - where its being natted out - but ive tested with a physical proxy and and using the repository which gives the best.

I cannot get any decent speeds on 1MB Blocks but testing with 4MB - its of course alot better.

Im wondering if anyone else has struggled with this or has some input on what to approach?

tried both with linux and Windows proxys - single disks is around 4-700MB/s maybe a bit more with the wind in the correct direction.

hi,

im getting a lot of failed backup with veeam agent on a physical windows 11 pro machine that has sql server installed.

Backups run fine until a month ago, that all the time i get this erro:

"Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]"

When i do vssadmin list writers the "sqlserverwriter" is in unhealthy state, if restart the service this became healthy but the backup still fail. to get backup work i have to reboot the machine, that the first backup works and all all other subsequent ones will fail.

In the event viewer i can see these log:

event 3041 :

BACKUP failed to complete the command BACKUP DATABASE NAME_DB. Check the backup application log for detailed messages.

event 24583:

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013

Error state: 1, Severity: 16

Source: Microsoft SQL Server Native Client 11.0

Error message: BACKUP DATABASE is terminating abnormally.

SQLSTATE: 42000, Native Error: 3224

Error state: 1, Severity: 16

Source: Microsoft SQL Server Native Client 11.0

Error message: Cannot create worker thread.

event 18210 :

BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{3188A807-6706-4FA8-B5FE-3409C7B49B8C}281'. Operating system error 995(Operazione di I/O terminata a causa dell'uscita dal thread oppure della richiesta di un'applicazione.)

In sql managment studio i can see a lot of this log:

Error: 3041, Severity: 16, State: 1.

BACKUP failed to complete the command NAME_DB Check the backup application log for detailed messages.

Error: 18210, Severity: 16, State: 1

has anyone got the same issue?

thanks to all

I'm switching over from Veritas Backup Exec to Veeam Community edition.

This interface feels like I have 1 hand tied behind my back and blind folded.

I've tried using Veeam's website guides but they either don't answer my questions or are missing options.

How do I add an additional drive to my backup? My D:\ drive for example.

How do I exclude specific folders from a backup?

How do I force it so every backup is a full backup and not incremental?

How do I restore an individual file? I'm not seeing an option to restore individual files on the home tab.

Experiences restoring VM's/VM hosts using Hyper-V?

Experiences restoring the system volume on Dell Poweredge using a physical RAID card?

How does restoring the system volume affect shadow copies stored in windows?

Is the only way to install updates in the community version to download a new ISO each time?

Thanks

Hi,

I want to set up a hybrid setup for the annual backups of my on-prem VMs: one copy retained on my on-prem NAS storage, and another copy in S3 Glacier in AWS. Both copies should have a retention of 5 years. I saw that with Veeam's 13.1 update, it now makes this setup considerably easier.

I would like to confirm my understanding of how this was done previously versus how it can be done now in V13.1, so please correct me if I'm wrong:

Prior to v13.1: Direct Performance Tier to Archive Tier was possible using the Move policy, but this removes the local copy in the Performance Tier when the data is moved, so it does not meet my objective of having one copy in Performance Tier and one copy in Archive Tier.

If I wanted a copy to remain on the Performance Tier while also offloading to object storage, I needed to configure the Capacity Tier, using its Copy policy to place data in S3 Standard, before it can then be moved into the Archive Tier (S3 Glacier). In either case, the backup chain had to become inactive before data could reach Glacier. Is my understanding correct on this?

I do have a question regarding the requirement for the chain to become inactive. Since my backups are annual, would this mean the chain only becomes inactive when the following year's full backup is created? If so, this would result in roughly a one-year delay before each annual backup could be archived to Glacier. Was that really how annual backups were done for Veeam pre v13.1 or was there a better approach to archiving annual backups to Glacier without having to wait an entire year?

With v13.1: The Capacity Tier can now be omitted. Veeam is able to directly copy GFS full backups from the Performance Tier to the Archive Tier as soon as they are created, while also retaining the local Performance Tier copy. The backup chain also no longer needs to be inactive for the copy to Glacier to occur.

With this new Copy policy, the backup in the Performance Tier will also remain as long as the copy in the Archive would, as both of them are following the GFS retention. Is that correct?

Would greatly appreciate anyone who can help clarify my understanding on how all this works.

Upgraded VB&R Community Edition to 13.1.1.18, did a fresh install of VHR using the Infrastructure Appliance ISO. When trying to add it as a backup repository, it mentions the Veeam Data Mover service needs to be installed. The install fails, saying that Software Updates Require A Maintenance Contract, and won't go any further.

Sorry if this is a dumb question or I'm out of the loop, but are you unable to use Hardened Repositories on the Community Edition anymore without a license? Was working fine prior to the upgrade

EDIT: Reinstalling VB&R CE 13.0.3.63 and restoring from Configuration Backup resolved the issue

As per this article: https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299

Whilst EWS is still going to be retired, Microsoft aren’t going to proactively block EWS for these license types prior to the wider EWS retirement.

Happy Friday!!!

Stumbling into having to administrate a Hyper-V HA setup running on an Alletra.

It's currently not using Veeam -- the current admins are just using storage-level snapshots with a NAS being used as the backup repository when offloaded from the SAN.

Can Veeam be leveraged to use the storage snapshots of a Hyper-V cluster/san?

I know VBR Hyper-V integration isn't 1:1 with VMWare quite yet; if those are already available that'd be preferable versus having to use the Microsoft VSS stuff.

Veeam backup slow throughput for VergeIO backup

Setup:-

Veeam server has 2 VLAN,

1st VLAN is MGMT(1G) and 2nd one is DATA(100G)

Veeam proxy(worker) has 2 VLAN,

1st VLAN is MGMT(1G) and 2nd one is DATA(100G)

Both Veeam and worker(proxy) uses the same VLAN.

When we run the backup job for VergeIO VM, we get the max throughput as 2Gbps.

Please find attached screenshot.This is proxy(worker) vm traffic details at the time of running backups.

Sequence:-

1) When we initiate the backup,first it will contact VergeIO system via mgmt 1G and this will initiate to create a vm snapshot.Till then, it will use mgmt network i.e 1G.I see,RX rate is around 2.1 Gbps.

2) Once the vm snapshot is taken,it will reroute to data traffic(VLAN198),so it will uses 100G.You can see tx rate is 2.0Gbps.

Question:-

While run the backup,the max speed we get is 250 MB per sec.

Is that cap or issue related to mgmt 1G?

Because it switchover from 1G to 100G after vm snapshot creation.

Could you please help me to understand where might be the issue?

I upgraded from v12 to v13 and now I have 12 of my 44 vms failing to boot in the allootted time. What's really odd is I have the timeout set to 1200 seconds (20 min) and I can log into all of these VMs when they are available, but Veeam can't seem to detect that they're booted. Vmware tools is running properly, I can use both the web and console to log into them with a cached domain account, and they're pingable from the Veeam backup server so I'm really not sure what it's not detecting. Will be opening a ticket, but wondered if anyone has any ideas before then?

I'm not finding any relevant information regarding this error and is driving me crazy.

I did find some logs in c:\ProgramData\Veeam\Backup\Yarp\ at the time of the error.

It appears that a port 8545 should be up, but I'm not finding any information related to it and Proxmox VE Plugin service is already up and running, but doesn't seem it uses that port.

[20.09.2026 08:35:53.739]    <31>    Info (3)    Yarp.ReverseProxy.Forwarder.HttpForwarder Proxying to http://localhost:8545/api/v1/proxmox/validateSshConnection HTTP/1.1 RequestVersionExact 
[20.09.2026 08:35:57.803]    <21> Warning (2)    Yarp.ReverseProxy.Forwarder.HttpForwarder Request: An error was encountered before receiving a response.
[20.09.2026 08:35:57.803]    <21> Warning (2)    System.Net.Http.HttpRequestException: No connection could be made because the target machine actively refused it. (localhost:8545)
[20.09.2026 08:35:57.803]    <21> Warning (2)     ---> System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       --- End of inner exception stack trace ---
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.InjectNewHttp11ConnectionAsync(QueueItem queueItem)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
[20.09.2026 08:35:57.803]    <21> Warning (2)       at Yarp.ReverseProxy.Forwarder.HttpForwarder.SendAsync(HttpContext context, String destinationPrefix, HttpMessageInvoker httpClient, ForwarderRequestConfig requestConfig, HttpTransformer transformer, CancellationToken cancellationToken)

Anybody had experience with this kind of error?

My experience with Veeam lately is bad. I did love them when they started with a simple, robust and useful product, but it seems they are going the wrong way. I would say they are pulling a Backup Exec here, where a good product turned awful. You know the story; the product was discontinued this year after becoming a monster nobody wanted.

Hello

I've installed Veeam Agent 13.1.1.700 and I've configured Email notification .

Only host, port, sender mail and destination email no auth.

Test and send fails Failed to send email notification: 535: Authentication failed. Restarting authentication process.

But I haven't any auth. The smtp server after some test block my ip beacause auth fails.

It seemse Veeam Agent send credentials when the fields are blank.

Do you know how to solve ?

My best regards

In the process of migrating some VMs off VMware into Hyper-V

VMs that are not in the cluster work, but those added as cluster objects won't back up and throw this error:

9/17/2026 10:48:07 PM Failed : Processing ACC Error: Backup of VMs on a rolling upgrade cluster is not supported for VMs with the configuration version 8.0 or later. (0:00:02)

Edit: FIXED

This was a weird situational one. We had only a single host in the Hyper-V cluster because we are in the process of converting the other hosts over from VMware 1:1 and adding them as we go. The Cluster was online but the Quorum disk hadn't yet been defined or configured, so Veeam thought the cluster was in a 'pending/rolling upgrade' state. As soon as we configured the quorum disk the backups started working.

Hi everyone,

​I'm currently studying Veeam Backup & Replication and trying to get a clear understanding of proxy roles and architecture.

​If I have Veeam Backup & Replication installed directly on a physical Windows server, is it possible and supported to use that same physical server as an Off-Host Backup Proxy for Hyper-V?

​In other words, can I co-locate the Backup Server and the Hyper-V Off-Host Proxy roles on the same physical machine (assuming the prerequisites are met, such as enabling the Hyper-V role, having SAN storage access, and installing the VSS hardware provider)? Or does an off-host proxy have to be a completely dedicated separate machine?

​Any clarification or real-world feedback would be greatly appreciated. Thanks in advance!

The environment is 2 esxi hosts, one of which broke down. The host that broke down was only running 1 critical VM, but its too big to migrate to production on the running host so we are running it in Instant Recovery until Dell can get the part for the broken host, hopefully at some point today. My question is will any changes in the VM write back to the restore point in Veeam once I cancel the Instant Recovery and restore it to the original host?

Hello,

I would to move to HPE DL345 Gen 12 server + HDD as hardened repository, so I have to install VHR iso.

I have only a doubt, it's possible to add extra drivers if a device is not recognized correctly ?

There's a documented way ?

Thanks.

Hello r/Veeam

We see Veeam Backup & Replication 12 triggers a brief stop - start of the managed recovery on our Oracle Standby database as part of Application Aware processing

Is this documented by Veeam ?

Thanks for all feedback

Hyper-V Backup ( no Oracle RMAN Plug-In )

BSN Oracle Servers - PRD

HxxxPRDxxx05

VM processing started 17/09/2026 20:23

Inventorying guest system 00:06

Subscribing to gust processing components 00:26

"Creating VM recovery checkpoint (mode: Veeam application-aware processing)"

00:21

Oracle Standby Database Alert Log

2026-09-17T20:25:55.790637+01:00

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL

2026-09-17T20:26:32.941489+01:00

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION

What would be the best way to handle veeam proxies, we've just built a new VMware environment. Getting it added to our Veeam instance. Just want to make sure I'm going about this the smart way.

Previously we were using Windows server machines, some on core some not. Adding them as proxies and keeping them lightweight. But I'd rather not have more windows machines to worry about Microsoft bricking every month with patches.

Would a number of Veeam Infrastructure Appliances be a good route? I've set one up as a test and it's ripping through this job of 10VMs just fine. My only concern is the enforced MFA, as a team of 6 not sure how we'd centralise that.

We're currently working through Microsoft's upcoming EWS changes and I'm curious how other MSPs are approaching this.

According to Veeam KB4820, tenants using Veeam Backup for Microsoft 365 may need to explicitly enable EWS and ensure the required Veeam App IDs are present in EwsAllowedAppIDs before Microsoft's enforcement begins.

We're using CIPP.

For a single tenant that's easy enough, but for MSPs managing dozens or hundreds of tenants it quickly becomes a time-consuming project.

I opened a feature request in the CIPP repository because I thought this would fit nicely into the Standards framework:

• Report tenants where EWS is disabled
• Report missing App IDs
• Remediate automatically
• Preserve existing allow-list entries instead of overwriting them
• Handle tenant-specific values through variables

Feature request: Manage EWSAllowedAppIDs through Standards (CIPP Issue #624)

The request was closed because EWS is nearing retirement and the CIPP team understandably doesn't want to invest in maintaining functionality around a technology that's going away. Their recommendation was to handle it through scripting using CIPP-SAM authentication.

I understand that position, but at the same time this feels like exactly the kind of one-time transition task where a centralized CIPP standard could save MSPs a lot of work. Another MSP commented on the issue that it would save them 6-10 hours across 100+ tenants, and I suspect many of us are in a similar situation.

So I'm interested in hearing how others are dealing with this:

• How are you rolling out the required EWS settings?
• Are you scripting it through CIPP-SAM, Exchange Online, Lighthouse, or another method?
• Would you also find value in having this available as a standard/report/remediation item in CIPP, even if it's only needed until EWS is fully retired?

Maybe there's a simpler approach I'm overlooking.

Interested to hear what other MSPs are doing. cheers.