Solved

Good morning everyone.Our company has just installed Veeam version 12.To save databases we use the MSSQLRecoveryManager.exe executable.However, we don't understand how to exclude databases that are Offline. Thanks in advance. Claudio

Hi guys my name is Ayanda i am new here so i wanted you to explain how do i reach a point where i will be rewarded badge 

Hi guys, Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process -  The upgrade failed and did not allow us to retry at all. Certain options were greyed out - Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. -   In the end, we were forced to back out of out upgrade.Has anyone seen this before? ShaunB.

Hi everyone. I have a question: I want to upgrade from Veeam 12.3.2.4854 to Veeam 13.0.3.63. However, I have an immutable repository running on RHEL 10.2; as you know, the SSH port is disabled. Since the new version needs to be applied to the components on the immutable repository, is it necessary to enable port 22, or can the upgrade proceed even with that port disabled? I hope that makes sense.

I enabled MFA for login and if I login from veeam server then I asked to enter the MFA every I open the console.If i login from veeam console from my laptop then i’m only asked to enter the MFA when 1st time connect to the server. After that even i already reboot my laptop then i never asked to enter the MFA again.

Hello. I have installed the newly released version 13 of the software appliance. I also have a Synology DS923+ NAS. Both devices are separate and are not added to any domain. Could you please advise me on the safest way to connect this NAS to the newly released appliance? I tried to connect to the SMB share, but I am getting Kerberos errors. I have version 12 installed on Windows Server, and the connection works there. Now I am testing the appliance and encountering connection problems. Thank you in advance for your help.

Hi everyone, i’ve been having this problem for a while now…Email notifications after backup completion are not being sent anymore to the specified email address, but when i test the credentials the email arrives successfully to my email account. I’m using the Veeam Agent 5.0 on a windows server 2012 r2. No veeam B&R is implied, just the agent making backups to a local disk.Additional informations:i recently changed the email server for the email account, before changing it everything was fine and the backup emails arrived, so at a first glance it seemed a problem with the email server; but i made a clean installation of veeam agent 5.0 on another server, using the same credentials, and the emails for the backup job are arriving regularly; so this excludes the fact that it may be a problem of the new email server(and also the fact that the email tests arrive without any problem).So i thought this may be a problem related to some veeam files regarding the old installation, so here’s

I just upgraded Veeam B&R from 12.3 to 13.1 and everything appears to have gone smoothly, with all components being upgraded without issue. The only problem we have is that we are notified each morning with a Software Update Summary email that our Veeam server ‘VBR’ Failed to synchronize update settings. Error: Failed to connect to the Veeam updater service.I was wondering if anyone is familiar with this error and how to resolve? Going through some steps online, I have verified the Veeam Updater service is running, backups are working, SQL connectivity and internet/DNS is working. Tried restarting service as well as a server reboot. Only the scheduled update-settings sync task is failing.My next step was going to be mounting the ISO and trying to repair the program, but wondering if anyone may know how to resolve this before I go that route. Everything else seems to be working just fine, so hoping to avoid a full reinstall. Thanks!

Hi All,I am new the the community and fairly new to Veeam and was wondering if anyone would mind sharing their own opinions and/or pitfalls  experienced using the Inline Entropy Analisis feature?My organization uses Veeam for Vsphere backup and DR and I have been asked to gather information prior to using in production.   I sounds great but from what I’ve read so far it has its limitations. Has anyone experienced any performance issues with backups or any other gotchas?   Have you found the feature useful?  Any feedback would be greatly appreciated.Thank you!

We’re having a major tape library issue with one of our clients. Do you perhaps have any ideas or solutions to suggest?(I’ve already asked the AI about this, but it didn’t help.)In their Veeam Backup & Replication environment, our client originally had four libraries:-    Scalar i3-i6 03255-    Scalar i3-i6 03256-    Scalar i3-i6 305G-    Scalar i3-i6 341G (Offline)I updated the Scalar i3-i6 03256 and Scalar i3-i6 03255 libraries at Quantum’s request following an incident involving one of the drives.Once the update was complete, Veeam took the Scalar i3-i6 03256 library offline and changed the status of the Scalar i3-i6 341G library—which had been offline—to bring it back online. Veeam thus reversed their statuses.I opened a ticket with Veeam Support, but I’m unable to provide them with the log bundles via SFTP (the file is empty every time, even though I verify that it isn’t before closing the connection), and they’re referring me to the standard documentation for tape libraries.

Hello, I need some advices for a new setup with VSA and Proxmox. The setup :1 cluster with 2 Proxmox node with 1 volume for the OS and 1 volume for the storage of the VMThe storage is done with Datacore Sansymphony (HCI solution). 1 VSA + 2 worker + 1 VIA repository for backup + 1 Synology NAS NFS for backup copy  I read Veeam documentation and limitation and I have 2 mainly questions :The Snapshot storage must be file level storage. In my scenario, that mean I need to use the volume available on the same disk as the OS right ? Because the storage used for the VM will be block storage …  For the worker, same issue if I understand it correctly, it must be file-level storage that supports snapshots. That mean I also need to use the same volume right ?How do you usually manage it ?  Finally, for the File system of it, do you use ZFS or XFS or EXT4 ?  Thanks for your answer 

Hi,We have a 2-node Microsoft Hyper-V cluster managed by Veeam Backup & Replication Community Edition.The two nodes are:- BETELGEUSE – works normally- SAIPH – affectedThe problem is that Veeam sees SAIPH as a Hyper-V server, but its Physical Host association appears to be broken.Veeam shows:SAIPH → PhysHostId = 00000000-0000-0000-0000-000000000000and:Get-VBRPhysicalHostdoes not return SAIPH, while BETELGEUSE is returned normally.We verified that:- SAIPH is reachable- VeeamHvIntegrationSvc is installed and RUNNING- WinRM/DNS connectivity to SAIPH works- the Hyper-V host itself is operationalThe impact is that VMs hosted on SAIPH are not being backed up correctly. As a temporary workaround, we moved the VMs from SAIPH to BETELGEUSE using Failover Cluster Manager, and the existing backup jobs then work normally.An important detail: the problem appeared after the network interface cards (NICs) were replaced on SAIPH.We also checked the Veeam PostgreSQL configuration database. The hosts

I want to upgrade my veeam one server and it crashed à stage 3 . every time I need to roll back on backup or snaphot because it uninstalls veeamone services 

Ciao, poco fa sono stato a fare un po’ di facchinaggio spostando dei server da dismettere che facevano parte di un cluster vSAN, quindi belle macchine con parecchio disco on board. Ci ho visto tante belle VSA/VIA nuove fiammanti: installazione tutta automatizzata, aggiornamenti facili, supporto ufficiale a disposizione in caso di problemi, abbondante spazio all’interno. Credo che -dati i prezzi che sento dei normalissimi server- il riciclaggio interno di asset che una volta avremmo venduto ai rottamatori senza patemi diventerà sempre più economicamente importante all’interno delle aziende. E novità come la VSA (che recentemente può montare direttamente anche uno storage esterno dismesso) aiutano molto la fantasia per riuscire a farlo.Che ne pensate? Vi state già scontrando col problema “ammazza quanto costa l’hw, dobbiamo proprio prenderne di nuovo”?

One of my VM is showing  FIB summary.txt issue in backup copy job. I would like to run Active full backup on only this problem VM . But this backup copy job has 20 VMs which i don’t want to run full backup as it will cause issue in wasabi bucket. Copy job goes to wasabi bucket. I know individual full backup can initiated in Backup job, but it is not showing BCJ . Please advise.Ver 12.1.2

Why would my badges not show on my profile? My credly is linked to johan@vmxperts.co.za and my Veeam university is also linked to johan@vmxperts.co.za but I’ve got zero badges showing on my profile.  

I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.Relevant logs:[19.01.2026 21:07:36.194]   <126>   Error (1)    Veeam.Backup.IdentityService.Shared.CSystemAccountProvid

Hi, I’m having trouble implementing an immutable repository using Red Hat 10 with Veeam version 12.3.2. I installed it a few days ago and it was working fine, but today the Veeam server was shut down to fix an issue with an HBA card. Upon restarting, the machine failed to reconnect to the immutable repository, throwing errors such as: "Unexpected socket shutdown, Failed to rescan repository (...) Error Unexpected socket shutdown, host discovery failed," as well as warnings like: "Refresh linux host failed error: Unexpected socket shutdown, failed to rescan repository (...) Unexpected socket shutdown." I’ve run a number of tests: changing the user password to match what is configured in Veeam, disabling the Red Hat firewall, testing connections on ports 6160 and 6162 in both directions, and re-enabling port 22—yet nothing works. Oh, I almost forgot this warning that appears when rescanning the Linux host: "Unable to collect hardware info: Unexpected socket shutdown." It’s really frustra

I would like to install Veeam Backup & Replication Community Edition on a Linux operating system instead of Windows.Could anyone please confirm whether this is supported? If so, kindly share the download link and installation media details.Thanks

Hello,I did my Veeam 12 (VMCE) exam in September 2025 and passed it.Now when I would like to do VMCE+, I understood that I do not have to do the VBR Training, only Veeam One and Orchestrator.But do I have to do the complete Exam, including VBR?Best regrards,Michael

Greetings. On a Veeam 12.3 install, whether there be an NFS or SBM datastore, and even while trying to hold the [CTRL] key and right-clicking on any datastore, the “Access Permissions...” menu does not show up, nor is there a ribbon icon visible for “Set Access Permissions” option.The logged in user into Veeam is a Veeam Backup Administrator. This option is visible on any other Veeam servers tested.What would be the cause for this effect? Thanks in advance.

Unprotected DB from the primary node in SQL AG. Other DBs are being backed up successfully on the same primary server.Configured to run transactional logging periodically but one large DB shows as unprotected. The problem started when the old primary node was switched over to a new server and evicted. After the eviction, it started not backing up the DB(error: Transaction logs from some databases were not backed up for the last 8 intervals).Ran image level backup (the parent job), this was successful but transaction logging still not working. However, the error now shows as (error: SQL Server transaction log backup took longer than desired log backup intervalFailed to upload SQL Server transaction log backup for DB to LogShip server: Repository agent is stoppedSQL Server transaction log backup could not be completed within 10 RPO intervals and will not be retried)This was working before and no changes to any of the Veeam servers so this error is not accurate. Confirmed application-awar

Good day everyone, I would like to know is it possible that I am able to install veeam software or veeam virtual machine just like creating a rhel virtual machine  on windows, fedora or ubuntu. I would like to have one for practise purposes during my program. If possible what do I need. 

I'm doing a full VM restore in Veeam to an HPE VM Essentials host, and I want to understand how the disk provisioning gets decided. Is there a way to force the restored disks to come back as thin-provisioned, or does Veeam just inherit whatever the target VME datastore or storage policy dictates?Trying to work out whether I have any control over this at restore time or if it's entirely determined by the destination.

Hello all,Veeam Backup & Replication Community EditionVersion before Update: 13.0.1.1071After applying the patch for version 13.0.1.2067: When I launch the Veeam Backup & Replication Console on the backup server, I am unable to connect and the following error appears: "Failed to connect to the backup server localhost. Make sure it is online and version is v13 or later".I updated Veeam with the patch and when I launch the full ISO, only the “Modify” option appears, and I could install "Veeam Backup Enterprise Manager".Either the error message mentioned above appears or this one, when I launch the console:"Failed to connect to the backup server: Client update is required but it is linked to a local server installation version. Use a standalone console installation or update your local server first."The Full-ISO contains a Shell.x64.msi, when I run it as admin, I can repair it, but doesnt change anything.Does someone have an idea how to fix that?Thanks in advance!Kind regardsTim