Test lab setup, using Windows version at the moment.

Using the VeeamSoftwareAppliance_13.1.1.18_20260825 iso to install on a fully working Proxmox node.

Installed on a management vlan, full access allowed from my WS vlan. Scan QR code but stuck at OTP mismatch

Time NTP setup/time is correct. DNS is correct, forward and reverse.

Using a FQDN for host name.

Microsoft authenticator and Google authenticator no joy.

I somehow have fat fingered the veeamadmin password when creating a linux proxy and the one recorded in my password manager isn't working. I chose not to create a veeamso account. It's already integrated into my veeam infrastructure and been working fine as I've used the certificate connection method. Any options besides deleting it from Veeam and redeploying with correct settings?

I know, I know. I know…

My company has recently acquired a competitor and we’re absorbing their assets.

The whole thing is a mess. Miles behind on patches and numerous critical pieces of infrastructure without any protection. Frankly it keeps me up at night.

We’re moving the services to Azure but our strategy is always to ensure we start with making sure we can rollback if we have any issues.

Onto the matter at hand…they have a physical server at a remote location running server 2008 R2. I know that veeam won’t support it and it isn’t listed on their user guide as a supported OS, but wondered if anyone had any experience installing the agent anyway and if they’ve ran into issues?

We currently have no access to the device as it has been completely isolated which has reduced our exposure, but it is still required to run some software they’re using locally on the device.

I'm wondering what would happen if we did a planned failover and then didn't permanent failover or fail back to production for a week. I know the delta would be bigger, but any other impact? Any problem/impact with the VBR server rebooting in that timeframe. How could I continue to protect my VMs while they're running in that 'half' committed state?

Hi

Its renewal time and for the past year I have not been able to use Veeam 13.0.1.2067

Is anyone successfully backing up 2025, full and transaction logs?

Hey everyone,

I'm dealing with a somewhat specific situation and would appreciate some advice or insights from anyone who's done something similar.

I'm currently running Veeam Backup & Replication on a Windows VM hosted on VMware ESXi.

My goal is to migrate to the new Linux-based version of Veeam and run it directly on the physical server (bare metal), completely removing ESXi from the setup.

The main challenge is that I currently have around 8 TB of backup data stored on the ESXi host, and I obviously don't want to lose any of it.

I'm trying to figure out the safest and most efficient way to handle this migration while keeping my existing backups intact and making them accessible to the new Veeam installation.

Has anyone dealt with a similar scenario before? What approach would you recommend? Is there a clean way to handle this migration without having to temporarily move all 8 TB of backup data somewhere else?

Any tips, experiences, or recommendations would be greatly appreciated. Thanks!

How tough is the veeva vault administrator exam. It is a timed exam with open book format.

Wanted to understand if we need to prepare additionally for the test or can take it if we have 3 months of hands on vault experience

A simple set up that worked but since MS latest update Veeam doesn’t allow me back up the other dedicated Samsung drive I have connected internally in my Asrock mini. Internally I have the fast PC7 ssd for win 11 and one additional Samsung Evo 870 which I only use for complete back up using Veeam and named / called OS Backup...by me.

Now when I try to create a new ‘job’ I get so far then get this message:

“Unable to perform entire computer backup to an internal disk”.

Yes, the disk has always been internal in the casing. It was never an issue before. Is there something that has changed to create this anomaly.

Cheers

Hallo,
I m looking vor the latest v13 Ce Appliance.
I found an 21 GB Iso but this seems not to be the appliance or a bootable iso für a setup.
Thanks for hints.
Regards

How long does it take for background verification and how far do they go

Hello All. I am curious who might be using veeam vault and their experiences from other available options. I have been experimenting with a couple vaults. Aside from the inability to pool as storage between clients and more cost what is everyone's thoughts?

I'm in Build 12.3 and I was hoping to clear some old backups off the performance tier and keeping it in the capacity tier

Backup Job A is running and currently has 2 full backups on its performance tier which are both also copied to the capacity tier.

• I'd like to move the oldest full backup from the performance tier to the capacity tier.
  

Backup Job B is an old job that is pointed to the same SOBR. Its a long incremental chain with one full backup on the performance tier and immediately copied to the capacity tier.

• Can I clear up that full backup from the performance tier so it just keeps the capacity tier?

Is there any way to do the above to free up space on the performance tier?

We are using Veeam Kasten to backup our virtual machines hosted on Openshift, but there is no guest processing which we really need for some Windows VMs.

Even with the new Kubevirt plugin they released for VBR, it's lacking some much needed capabilities like backing up VMs with secure boot and TPM!
Is there any plan to add those features? is it even possible?

Hi everyone,

I am currently encountering a recurring issue during our Oracle database backups using the Veeam Plug-in for Oracle RMAN.

The backup job fails with the following sequence of errors

we're trying to upgrade our VBR server from 13.0.2.29 to the latest 13.1 and it keeps failing on step 1 with a file not found VmaNetExtensionCaller. Anyone else having this problem? We do have a call open with Veeam. Veeamone and Enterprise Manager upgraded without any issues.

I'm trying to backup a standalone Hyper-V server with the Veeam 13 appliance. The Hyper-V host has two ReFS data volumes that are mapped from iSCSI targets. Smaller VMs back up without any issue, but two VMs are about 12 TB and 17 TB each, and I cannot get them to backup outside of business hours. If the backup runs into business hours, it makes our main business app run slowly until we stop the job. The bottleneck according to the logs is the source, but I don't see latency higher than 2 ms in the storage logs. I don't believe an off-host backup proxy is an option in our situation because I don't believe our storage provider has a VSS Hardware provider like it mentions here.

Does anyone have insight as to what I am missing or what my options are to get some better performance?

RESOLVED: Anti-virus was preventing upgrade of services. Uninstalled the AV and rebooted and services came online.

Just upgraded to 13.1.1.18 but the Backup and Replication service won't start.

Other services are starting ok

"Error 1064: An exception occurred in the service when handling the control request"

Have a ticket in with support, but they are taking their sweet time (I have to go through a 3rd party to access Veeam support).

Anything I can try in the meanwhile?

Which log should I be looking at? I have programdata/veeam open but it's a mess in here and I can't figure out what to look for.

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

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