Solved

Hi,we have Veeam Backup and Replication v13, Community Edition, Build 2067 on Microsoft Windows Server 2019 with Hyper-V.When I try to add a Veeam Data Cloud Vault from the Austria East Region I get the following error:The error occurs during authorization of the backup server after I login using Microsoft, including MFA and after I answer the question if I want to stay signed in (Yes or No has the same effect).If I add the same VDCV Repo on another installation of Veeam (different customer, paid version) it works.I installed the Veeam Console on the only VM of the server and I got the same error.AI suggested to check the version of a specific DLL, which is 2067.I installed a trial license, same error.I disabled all security filtering on the firewall temporarily and checked the logs.Any ideas, how this can be fixed? Thanks a lot for your help!Thomas

Buonasera (o notte 😄) a tutti, vorrei avere consigli su che strategia adottare. Voglio backuppare tutto il mio sistema, circa 550GB, nel seguente modo: ogni mese avere un full backup, ed ogni tot fare un backup incrementale (max 3 per mese, lo faccio manualmente quando capita). Ogni fine mese sposterei il backup su un HDD esterno. Purtroppo non ho molto storage a disposizione, quindi i primi giorni del mese successivo, vorrei che il vecchio full + tutti gli incrementali, che ho già passato sul disco, vengano “cancellati” e venga creato un nuovo active con cui seguirò tutta la procedura. Qui sorge la prima domanda: nelle opzioni di Veeam vedo solo riferimenti al numero di giorni e non al numero di restore points. Posso inserire 4 come valore, per contenere il full backup + i tre incrementali oppure è sbagliato? E se per caso facessi 5 backup in tutto, la policy non rischierebbe di cancellare anche il full iniziale oppure essendo questo appunto un full non verrebbe intaccato?Come second

What are the essential ports required for windows agent based backup in veeam between windows server and backup server ( windows ) , the protection group is already existing and few servers backups are running successfully, new servers are being added to protection group and agent installation / rescan is getting failed 

I am trying to add a Microsoft Azure Stack Hub account to Veeam Backup & Replication v13, but I do not see any option to add Azure Stack Hub under Cloud Infrastructure or Add Server.I also could not find any official Veeam v13 documentation related to Azure Stack Hub integration or support.Has anyone successfully configured Azure Stack Hub with Veeam v13?Is Azure Stack Hub still supported in version 13, or has the feature been removed/changed?Any guidance or documentation would be appreciated.

Hi Fellow CommunityI am getting so frustrated with failed backup. The report says the following: Task “VM-Win11 Machine” has been rescheduled.Failed to create VM recovery checkpoint (mode: Crash consistent) Details: Failed to create VM (ID: a7a09a79-7b58-4963-a815-27c15590db59) recovery checkpoint. Job failed ('Checkpoint operation for 'Attendance Machine' failed. (Virtual machine ID A7A09A79-7B58-4963-A815-27C15590DB59)'). Error code: '32768'.Retrying snapshot creation attempt (Failed to create production checkpoint.)Task has been rescheduledQueued for processing at 7/6/2024 7:57:00 AMUnable to allocate processing resources. Error: Failed to create production checkpoint.Processing finished with errors at 7/6/2024 7:57:05 AMProcessing finished with errors at 7/6/2024 7:57:10 AM regardsRohit

Hi, hoping someone can point me in the right direct with getting started with Kasten please, as this is almost surely a user error on my part, but I cant figure out whatLike the title says, I have deployed Kasten in a K8S cluster, currently not really doing much until Kasten is setup, however when generating the token to log in to the WebUI, the page just refreshes and I cant log inThis is running on a vSphere Kubernetes cluster, which isnt anything fancy, just K8S with PSA enabledThe K8S release is 1.33, and its a FIPS cluster, if that makes any difference, I would have gone with 1.35 non FIPS, however 1.33 was the latest the primer said 8.5.8 would install onFor the steps I have taken to deploy it, I ran the following once getting logged into my K8S clusterA default storage class needed setting, from some issues I had before, so the below was run on my preferred storage classkubectl patch storageclass vsan-esa-auto-raid-policy-latebinding \  -p '{"metadata": {"annotations": {"storage

Can someone please help me with VMCE information. I am looking for both the paths and roadmaps,  and all involved information associated with it. Also, any  links for practice questions that would be helpful. TIA.

What are the drawbacks or disadvantages of using Veeam Agent for Microsoft Windows when performing backups to NAS storage? This includes considerations regarding storage, network speed, and reliability.

Hi everyone, has anyone tried using OMV 8 (Debian 13.4) as a Linux backup repository for Veeam VBR v13? I checked the official documentation for VBR v13 compatibility, but it currently only lists support from 11.0 up to 13.1. Would I be safe to proceed with the OMV 7 to 8 upgrade?

When I try to restore from HV guest using “Copy To” option, choose a folder and the “OK” button is greyed out. I used to use this function all the time on this server before I upgraded to 13.01. Any ideas?

 In my Azure Local node the backup job always error for only one node with below error (node 03).If i scan the hyper-v cluster then all nodes is up to date. But after the job is run then this 03 node always back to  

Receiving error message “invalid system configuration detected”. Checked the logs under C:\ProgramData\Veeam\Setup\Temp\ but not finding anything. The logs end with Vmacheck upgrade.

Hi Veeam Community  I’m unable to run any backups on Veeam Agent for Windows (6.3.1.1074, free edition). While my setup was working previously, I now get the error “Failed to create VSS snapshot” when attempting to run a backup.My destination is an SMB share on a local Windows Server (Server 2022 OS). Other devices on my network (In identical configurations, “Entire Computer”) are able to back up to that share successfully, it’s just this one machine that’s failing.I have tried the following and it only kept the backups successfull without any warnings for 2-3 days and then reoccursRan the following commands:net stop vss net start vss You can also restart these services in services.msc: Volume Shadow Copy Microsoft Software Shadow Copy ProvideWhen running the vssadmin list writers command I see that this writer times out and others show no errorsAny assistance with this issue would be greatly appreciated

While installing Veeam Backup & Replication v13.0.0.4967 from the ISO (Rocky Linux–based appliance), the installer stops mid-way with an “An unknown error has occurred” message from Anaconda.The traceback points to dnf/base.py related to remote package selection or repository fetching.This occurred during the “Downloading packages” stage. Who else has run into this error? Another error, you could run into is this “Appliance Installation Stuck on "Configuring addons" and the following KB addresses what to do correctly.

root@charon:/home/amonra# apt-get install blksnap veeamReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneE: Unable to locate package blksnapE: Unable to locate package veeamroot@charon:/home/amonra# So clearly I need to do something before I can install. The manual didn’t say where the repository was.

I am trying to update Veeam Community Edition to the current version as recommended by KB4743.  Unfortunately, each time I attempt to run the upgrade I get a "Modify" option instead of "Upgrade".   I have check the Veeam KBs as well as looked though the Veeam Community for an answer - any help on this would be appreciated.  

Hello community,After upgrading a Veeam Backup & Replication environment from version 12 to version 13, we started experiencing some unexpected behavior related to remote script execution, user permissions, and MFA. I’d like to check if anyone else has faced a similar situation. EnvironmentVeeam Backup & Replication recently upgraded from v12 to v13 Monitoring solution relies on PowerShell scripts executed remotely Use of Operator role / custom non‑Administrator users Scripts used for status collection and integration with external monitoring tools Issue 1 – Remote Script ExecutionAfter the upgrade to Veeam v13, scripts no longer work when executed remotely unless the user is a Veeam Backup Administrator.Before (v12): ✅ Scripts worked with Operator or custom roles After (v13): ❌ Scripts only work when executed by a Backup Administrator ❌ Direct impact on monitoring (scripts no longer return data) Error MessageWhen attempting to run PowerShell commands using a non‑administrator

Anyone can help me to understand about this picture?When the tape retention is over then backup day 1 will be removed and this mean 1st full backup wlll be removed. Then how we can restore the VM to the Monday? Isn’t restoring the incremental need the last full backup? 

I have to replace a SCSI tape drive with SAS to upgrade to Veeam 12.   I have to replace the OS on the Veeam server to upgrade to 13. I am still on Veeam 11.  I have HP Z840 workstation that is on Windows 10 Hyper-V.   I am moving VMs from VMWare 6 to this workstation.   I have so far installed our children’s minecraft servers on Ubuntu 24.04 as virtual machines.    I setup for file level backups.   I want to backup each VM in E:\Hyper-V separately.   Each VM has its own folder and VM structure in this directory.   E:\VMBackups has a script that removes and replaces each of these VMs.# Import the Hyper-V moduleImport-Module Hyper-V# Define parameters$BackupDriveLetter = "E" # Change to your backup drive$VMHost = "localhost" # Change if backing up from a different host$VMNames = @("Bedrock2404_10.10.10.3", "Bedrock2404_10.10.10.4", "Bedrock2404_10.10.10.5", "Java2404_10.10.10.6", "Java2404_10.10.10.7", "PaperMC_10.10.10.8" ) # List of VMs to back upRemove-Item -Path

https://www.veeam.com/calculators/mapsVery neat feature, but a question comes up while testing a few scenarios: Why does remote console need connection to non-hardened repositories, but not the hardened one here? The ports tell about “file restore”, but I’m not sure on the source of this, as I don't see this in the ports list (Note: I’m aware this list is suspect, we’re working on it but point is more what is the source that we need Remote Console => repo connections for file restore?) If you're talking about mounting to console, I can understand but doesn’t hardened repository need this also?  

I am currently migrating my backup repository.Previously, I used a Linux Hardened Repository for primary backups, but I have now switched to an ExaGrid backup appliance. The primary backup to the new ExaGrid device has been successfully completed.Now, I want to reuse the backup data stored in the old Linux repository as a secondary target using the Backup CopyBefore: Primary (Linux Repository only)After: Primary (ExaGrid) --> Backup Copy --> Secondary (Linux Repository)However, when I try to select the existing Linux repository and use the "Map Backup" option in the Backup Copy job settings, it fails to recognize the existing backup data. I have already deleted the original backup job from the Linux repository, and the data is currently showing as Disk (Orphaned)The Veeam version is 12.3.2, and the backup source is a vSphere VM. My questions are:Is it impossible to reuse backup data created by a regular "Backup Job" for a "Backup Copy Job" via the Map Backup feature? Is there an

I have backup job to create full backup to the disk then to tape. Total full backup no more than 2TB but why veeam use 2 tape catridge to backup this?Each catridge have 10.9TB and one only one catridge should be enough. 

Hi,Today I upgrade in my homelab (with NFR license) from Veam 12.3 to 13. I have 3 Proxmox node and three Proxmox backup job, Everything was running fine before the upgrade. Now with 13 I discovered that Proxmox is missing, when I click “add new server” and virtualization platform Proxmox is not there. Proxmox plug in is installed version 13.3.1.7 No idea what has happened with the upgrade. The upgrade process ran without an issue. Any idea? What I already did is uninstall the Veeam Proxmox plug-in and reinstalled installed after a restart of each step.

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

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.