Solved

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.

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 Expert,I am looking for advice on the best way to protect our Veeam VBR/DB. Our environment is currently set up as follows:Veeam VBR Server: Running as a VM on VMware.Database Server: Running as a separate, dedicated VM (MS SQL).Current Backup: We are currently including both the VBR VM and the DB VM in a standard VMware snapshot-based backup job.Is this considered a "good" or "supported" configuration? I am concerned about:Stun/Freeze: Will the VMware snapshot "stun" cause the VBR server to lose its connection to the remote database during jobs?Consistency: Does a standard VM backup ensure the VBR server and the separate DB VM stay in sync if a restore is needed?Circular Dependency: If our VMware cluster goes down, we lose our backup server.Should I exclude these VMs from our regular backup jobs and rely solely on the Configuration Backup tool, or is there a benefit to using Veeam Agent for these specific servers instead?

Hi,if i create a backup copy job in the Veeam Scenario Builder with VMs, Agents, Plugin, NAS to a XFS Repo i can select 7 Workloads:After I changed the backup copy repo to “direct to object storage” i can max select 6 workloads, cause Oracle Plugin Backup isn’t visible anymore. I choosed V13 inside the Scenario Builder where a Plugin to S3 Backup should work.Is this a bug or where is the problem there? GreetsPeter

Here my configuration for azure blob where i set the immutable duration for 7 days. How we can make sure that we can’t delete any backup files inside this blob?I try connect to azure blob storage then upload new file and then i try to delete and i can deleted the file. Is the immutable not work since i can delete test file what i upload manually?