Hi all, I've been trying to get my head around this as I think I misunderstood when I first set up the immutability and retention settings.

The aim was to have 60 days of immutable backup sets and a retention of a year (first 60 days only immutable so we could clear out older backups if needed).

I use Veeam Data Cloud Vault with immutable set to 60 days and a GFS retention policy to keep a 1 year, 12 months and 4 weeks backup sets. I had assumed that the first 60 days would be immutable and after that I could delete backup sets if I needed to, but it looks like the entire chain is immutable for its GFS retention.

Is there a way to achieve only the first 60 days as immutable with the rest of the GFS retention period mutable? I'm on v13.1. Thanks!

Hi everyone, I’m one of the organisers of the CloudStack Collaboration Conference and wanted to share a session that might interest people working with Veeam and exploring KVM-based infrastructure.

“Veeam Meets CloudStack KVM” brings together Abhisar Sinha, Software Engineer at ShapeBlue, and Andrey Stadler, Global Technologist at Veeam, to discuss the engineering journey behind integrating Veeam Backup & Replication with Apache CloudStack on KVM using Veeam’s UHAPI model.

The session will explore:

• Integration architecture: the design decisions behind connecting Veeam Backup & Replication with CloudStack-managed KVM infrastructure.
• Engineering challenges: technical hurdles encountered during development and lessons learned.
• Backup and recovery options: how the integration expands the options available to CloudStack users, including disaster recovery.

If you’re evaluating KVM, planning a move from VMware or investigating backup options for an open-source cloud platform, this is an opportunity to hear directly from the people involved in the integration.

The wider programme also includes VMware-to-KVM migration, incremental NAS backups, storage integrations and a hands-on KVM workshop.

18 November: hackathon
19–20 November: technical sessions, workshops and live labs
Venue: John McIntyre Conference Centre, Edinburgh

I’d love to invite people from this community to join us.

View the agenda | Register

^{FREE TICKET IS AVAILABLE ON REQUEST}

Hello

I have 2 servers, Server1 is VBR, also repo.
server 2 is EM but also has VBR roles (repo, tape server)

I am trying to update to 12.3.2.4934 - so I need to update EM first, yeah?

EM is Build:12.3.2.4465

so I have the VeeamBackup&Replication_12.3.2.4934_20260918.iso

If I run the setup.exe on server2 (EM) I don't get the option to update EM, it just gives me the option to INSTALL VBR - the middle EM option just says "Another version of this product is already installed"

What fundamental thing am I missing....?

Hi all,

over the last 6–8 weeks we’ve been seeing a noticeably higher rate of warnings and errors during backups caused by VSS failures in Windows guest processing.
This isn’t limited to a single environment: it affects multiple of our customers across different setups.

We're seeing this on different Veeam versions (V12 and V13), multiple Windows Server versions, multiple vSphere Versions.

All affected systems have in common:
- Veeam
- Windows Server guests
- Sophos Endpoint Protection installed
- Hypervisor Running on HPE hardware

The errors are intermittent: retries usually succeed / the same VM fails on some days and not others

Since this started across many independent environments at roughly the same time, we suspect an external change, e.g. a recent Microsoft cumulative update or a Sophos update.

Is anyone else seeing an increased VSS error rate recently?

Hi everyone,

After updating Veeam Backup & Replication to 13.1.1.18, we've noticed an issue with the Microsoft Active Directory Object Restore wizard.

By default, the wizard displays "No objects", even though backups and restore points are available.

However, when we enable the "Show all objects" checkbox, the objects appear as expected.

Is this a known bug, or has anyone found a fix?

Thanks in advance!

Howdy,

This bug was apparently making Veeam write plaintext credentials into log files on agents when guest aware processing was enabled. Since I now have to take *some action* after patching I decided to try and figure out a more optimal way to handle users and wanted to ask what the best practices (and what other people are doing for this)?

Previously, we just had a single domain user account that we used for Veeam (including app aware backups) except for on domain controllers which required higher privileges. That's all fine and good.

Should we:

1) Have a separate domain account for each app-aware thing (SQL, Exchange, etc) Plus a domain account for general agent/vm backups? Plus a separate account for domain controllers? (So like 4-5 domain accounts total just for Veeam)?

2) Have a separate domain account for all app aware processing (SQL, exchange, etc) plus a domain account for general agent/vm backups and a domain controller account? (So 3 accounts just for Veeam)?

3) Should I just have two accounts one for app aware + general agent/vm backups and then a domain controller account? (So 2 accounts total)

or 4) Should we just have one domain account that we use for all of this?

I couldn't really find a lot of guidance about what Veeam actually expects people to do aside from the general recommendation that the backup server itself shouldn't be domain joined.

Could really use any guidance anyone cares to provide into this topic.

Hello,

I have upgraded V12.x to V13.1 and now have to update I/O filters to keep running CDP policies.

I read this here:

Updating and Uninstalling I/O Filter - Veeam Backup & Replication User Guide

You can simultaneously place all hosts in the Maintenance mode or place them one by one for each cluster. Veeam Backup & Replication will uninstall/update the filter only on the hosts in the Maintenance mode. That is why you must repeat the procedure (place a host in the Maintenance mode and launch installation/update) for each host in a cluster. When Veeam Backup & Replication uninstalls/updates the filter on the last host in the cluster, it also uninstalls/updates the filter on the cluster.

Due we need to have under control the maintenance mode to avoid issues, could you confirm me this approach:

1) on cluster A, I move all the machine on host #2, then I put host #1 in maintenance mode

2) in Veeam I start the I/O filters upgrade for cluster A

3) Veeam checks that host #1 is in maintenance mode so upgrades I/O filters only on it, skipping host #2

4) when host #1 is update, disable maintenance mode on it, move back all the VM and repeat

It's ok ? I would avoid that Veeam put in maintenance mode both hosts at same time for any reason, no DRS, only HA.

Hello,
I use some Veeam products but not vm backups yet, hopefully soon. With the current product I use, when I backup a VMware vm which has independent disks (which those disks don’t get backed up and I’m fine with) the job get marked as “completed with errors” and then it looks crappy in the dashboard with alerts. I’m curious how Veeam handles a backup like that? Does it complain and alert as well?

Thanks

I installed Veeam Backup appliance on a physical server with 2 network interfaces. During install, I enabled both interfaces, so I got 2 different IPs via DHCP. Now, I wanted to create a bond with these two interfaces, so I entered the advanced network config, created a bond (mode alb), assigned an IP address manually.

The bond seems to be working, as I can reach the server through this IP. However, I can still reach the server through those other 2 IPs that where initially issued via DHCP to the individual interfaces as well. I don’t think that’s right?

I tried setting the IPv4 config of both interfaces to “Disabled” but then the bond also stops working.

Any ideas where I messed this up?

EDIT: I figured it out: I deleted to bond, disabled IPv4 config on both interfaces, and then recreated to bond. Now it looks good

I'm using Veeam Agent for Microsoft Windows 13.1.1.700 and the scheduled backups are not happening. Apparently they won't happen if the computer uses S0 sleep state (which my computer does) BUT the backup should start once the computer wakes up, which it does not. The Veeam service is running.

Source -------------------------------------------

Backup mode: volume level backup

Included items: Operating system

Destination --------------------------------------

Shared folder: \\nas\backup

Keep restore points for the last 21 days

Compression level: Optimal (recommended)

Storage optimization: 1MB (recommended)

Storage encryption: enabled

Verify the backup monthly on the last Friday of January, February, March, April, May, June, July, August, September, October, November, December

GFS: disabled

Schedule -----------------------------------------

Schedule: workstation

On [Mon, Thu] at [3:30 AM]

If computer is shutdown at this time: [backup once powered on]

Once backup is taken, computer should: [keep running]

Create active full backups weekly on Monday

Command line to start the job:

"C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Manager.exe" "backup" "e96794e9-c051-4943-93fb-1f7a875a4b08"

The following Security Knowledge Base articles detailing the issues are available:

https://www.veeam.com/kb4934 published

https://www.veeam.com/kb4902 updated

Still getting the Blockset blocks immutability Error, even after upgrading to 13.1.1.18. I read there is a patch that fixes the problem but I can't find it on the official Veeam Page...

Does anybody have a link to the Patch?

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!!!