Unanswered questions

I’m trying to backup one of our “workstation” but I am experiencing this error in our VSPC, why is that ?

Hey everyone,As we prepare for the upcoming update that introduces support for Veeam v13 on Windows, I wanted to ask:What migration strategy are you planning to adopt and why ?Will you simply upgrade your existing Veeam Windows server to v13? Or do you plan to migrate to v13 and then transition to the Veeam Software Appliance?So far, I haven't found any official discussion about the migration process from Windows to Linux. Ideally, I'm looking for a solution that allows me to back up and restore my settings during this migration. Personally, for all new projects, I’m planning to propose the new Linux-based appliance, even though some aspects still require optimization and improvement. In cases where migration is possible, I would tend to recommend switching to the appliance for smaller infrastructures as well — mainly to benefit from the native hardening layer and eliminate Windows licensing costs. Smaller companies often have limited time to dedicate to cybersecurity.For larger infras

We currently use Veeam B&R to backup the share’s to a local repo on the backup box. I then created a second job (agent) to backup the drive B:\backups to the clients VSPC repo. It works but when I attempt a restore of the cloud data its a restore of what looks like a database and not browsable files like a restore of the original B&R job produces. Hopping for a more elegant solution that doesn't require a two restores to get client data into a usable form. thanks and sorry for this being one of those out there kind of questions.

Im trying to install kasten using helm and running to this error:clusterroles.rbac.authorization.k8s.io "kasten-admin" already exists I began by trying to install it in a name space with rescrictive policies and that failed as some pods where set to need it. After than I uninstalled the helm chart, tried again with more permissive policies and got this message. I have tried to remove the namespace, remove all CRDs and cluster roles with kasten or k10 in them. Also, when uninstalling the helm chart. I can see that the kasten-admin cluster role is removed, but this message still appears on installation.

Wir wollen, dass bei den auf der VBR verwalteten Backup-Jobs für die Workstations auch der Veeam Backup Agent automatisch ausgerollt wird.Leider funktioniert diese Art der Remote Installation innerhalb einer Domäne nicht. Die interne Windows-Firewall wurde zu Testzwecken abgeschaltet um diese auszuschließen.Gibt es etwas, was speziell beachtet werden sollte bei Windows 11 Workstations ? Danke Torsten 

Veeam server v12.3 installed in VMware virtual machine with Postgresql as VBR database                 48vcpu’s,64 GB Ram,200GB C Drive have 3 windows physical proxy servers with same configuration of below                               32 cores x 2 sockets= 64 logical processors ,256 GB Ram  Repository -HPE storeonce deduplication Appliance with 2 storeonce units  connected over       FC(Fibre channel)   500 TB + 600 TB = 1.1 PB                                                                 we have created catalyst stores of 100 TB +150 +250 on unit-1 / 300+300 TB on unit-2. Vmware infrastructure is like we have 1vcenter contains 112 physical ESXI hosts all are in same network including vbr,proxies,repositories. we have plan of creating 1000 vm jobs ,1vm per 1 job,but as of now we configured 500 vm jobs.                                                       most of the jobs are from 500 jobs are targeted to 2 catalyst store of unit1 250 +unit2 300 TB since past 1.5 months we are faci

This is the data shown in VSPC → Protected Data → Computers → Managed by Backup Server.Maybe I’m missing something obvious./protectedWorkloads/virtualMachines = on-prem virtual machines (vSphere, Hyper-V, AHV, oVirt, Promox)/protectedWorkloads/publicCloud/virtualMachines = cloud virtual machines (AWS, Azure, GCP)/infrastructure/backupAgents = agents managed by console 

The data shown in VSPC for virtual machines includes a field called ‘Platform’. How do I get that information via a REST query? For example, all I get back from /protectedWorkloads/virtualMachines is:instanceUid : 99cef482-482c-96a9-ece8-8414715e2feebackupServerUid : d5beda61-353c-4d6d-8de8-dacc624e38d4organizationUid : 708e82e3-ff60-4bb2-8d71-9c032afe8efbname : hierarchyRef : parentHostRef : objectUid : 4ef89479-7cbd-41c3-861b-18de5ada56aeipAddresses : provisionedSourceSize : 85899345920usedSourceSize : 85919269836totalRestorePointSize : 61589856256latestRestorePointSize : 2263212032restorePoints : 60latestRestorePointDate : 2025-10-07T22:10:18.9900000+00:00jobUid : 2727ab1b-08f8-4741-870a-b275dc6da6f8malwareState : UnverifiedCheers.

Hallo User,ich teste gerade die Installation von Windows Server 2025 und Veeam. Alles läuft super und wie erwartet. Was nicht funktioniert, ist der Datenträger für Bare Metal Recovery. Der Datenträger Bootet problemlos, bleibt dann aber bei einem Commandprompt stehe.VG  Hello User,I'm currently testing the installation of Windows Server 2025 and Veeam. Everything is running great and as expected. What's not working is the Bare Metal Recovery media. The media boots without issues, but then gets stuck at a Command Prompt.Best regards (BR)

Salve.Ho creato un job di backup ad alta priorità per 4 VM di database. Viene effettuato un backup ogni 30 minuti.Vorrei che fossero aperti contemporaneamente gli snapshot su vmware per tutte le macchine, ma non accade e non ho trovato un’opzione adeguata.Esiste un modo per forzare la contemporaneità degli snapshot?Grazie

Hi, I created “Backup Copy” and somehow is working if the Object Type is “Agents For Window Job” but not on “Repository”. Is there something I missed out ?   

Hello.I have three servers: one is EnterpriseManager, the second is VeeamBackup, and the third has the Veeam console installed. When I launch the Veeam console on the backup server, I get the error "failed to load license from backup services." I looked at the logs and see that the client versions match. I see that a connection attempt is being made, but the connection is being closed. I don't understand why. I tried TNC fqdn for the backup server - port 9392, as well as port 9396, and there were no errors..  I changed the names and IP addresses in the logs. I don't think they're needed for analysis. CODElog uploadfiles

Hello community,We are running Kasten K10 v7.5.3 on OpenShift (bare metal) and encountering recurring backup job failures during the CopyVolumeData phase.In the logs, Kasten attempts to pull images from the internal OpenShift image registry and receives multiple 401 Unauthorized responses. Example error:GET https://image-registry.openshift-image-registry.svc:5000/openshift/token?scope=repository:<project>/<component>:pullunexpected status code 401 UnauthorizedOnly certain workloads are affected (those belonging to one project currently in a failed state by design). All other namespaces complete backups successfully.We’ve confirmed:The node hosting the copy-vol-data pod was ready and schedulable during retries.Policy configuration selects only the affected namespace.Storage backend is NFS.Has anyone experienced Kasten backup failures caused by workloads in a failed deployment state or image registry authentication issues?Any advice or workaround (such as excluding failed wor

Hi,I would like to backup with Veeam backup and replication 12 my new physical NAS with TrueNas Core.How can I proceed ?Do I need to add my TrueNas like an “unstructured data source” ?If so, what option should I choose in next window? File server, File share or NAS filer ?Thanks for your helpRegards,

Hi, new install of veeam with a dell poweredge server and powerstore connected via iSCSI. this will be a hardened repo.Has anyone tested the optimal settings for Veeam including immutability against the powerstore so the powerstore can still perform the data reduction tasks? 

Hallo zusammen, bei einem PC taucht folgende Fehlermeldung auf:“30.09.2025 17:02:21 :: Disk 0 layout change detected, resetting changed block tracking for all volumes on this disk”Was kann ich tun, damit die Fehlermeldung nicht mehr kommt?Die Maschine ist “echtes Blech” (keine VM o.ä.)Bin für jede Hilfe dankbar.VG Andreas

We are running a VMWare environment.We created a new iSCSI datastore for some of our VMs due to the previous Fastclass Fibrechannel datastore having issues.All of our VMs are running well on this new datastore but every Veeam backup job fails for VMs housed on it. All backups for VMs running on other datastores are fine. The VMs show up in Veeam and are able to be added to jobs and show their file sizes, but fail when the job is run.Any ideas? I’ve pasted the typical error message below that we get, with some of our info redacted. Note that some of the files do actually back up, namely the smaller files like the .vmx, .vmxf, and .nvram, but the .vmdk file seems to be where the error occurs. 10/1/2025 3:18:59 PM :: Processing ******** Error: Failed to open VDDK disk [[***NAME OF ISCSI DATASTORE***] ***NAMEOFVM***.vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [***VMWare HOST IP***];Port: 443;Login: [***USERNAME***];VMX Spec: [moref=9];Snapshot mor: [9-snapsho

Hello everyone!Veeam 12.3.2.3617, Community Edition, Workstation Backup by veeam agentI’m having an issue with one of my home PCs. When I try to back it up, an error appears.29.09.2025 21:31:17 :: Error: Unable to resend traffic block '15863' because traffic history doesn't contain this block. History low block id '15869'.Failed to upload disk. Skipped arguments: [EmulatedDiskSpec>];Agent failed to process method {DataTransfer.SyncDisk}.Exception from server: There is no traffic block '15863' on the source side.Unable to retrieve next block transmission command. Number of already processed blocks: [25496].Failed to download disk 'bdd448f6-e7b0-4f2b-93b3-6eb675ad51c3'   Backups of two other PCs to the same storage complete without any problems. What could be causing this behavior?I tried replacing the target HDD — it didn’t help; the error can also appear when backing up the SSD (the drive’s health is normal, no errors).I tried different backup types (volume, file-level, entire PC) —

Wenn wir in der Veeam Service Provider Console (VCSP) bei einem Windows Server eines Kunden diese auf “Switch to Managed Mode” umstellen, wird eine Lizenz installiert. Welche Lizenz wird hier genau “gezogen” ?Bisher haben wir für jeden Kunde eigene Lizenzen erstellt, aber diese wird in diesem Fall vermutlich nicht verwendet ?Danke Torsten

Bonjour,Environnement VMware : vSphere Client version 8.0.3.00400Environnement Veeam : Backup & Réplication 12 build: 12.3.2.3617Problématique : Lors de l’execution du job de backup le message d’erreur ci-dessous apparait et empêche la sauvegarde. Traitement MEMREY01 Erreur : Échec de l'ouverture du disque VDDK [[MEMREYME5-VOL1] MEMREY01/MEMREY01_2.vmdk] ( est en mode lecture seule - [true] ) Tentative de connexion avec les paramètres [VC/ESX : [memreyvce01.eurocast.local] ; Port : 443 ; Connexion : [local_vce@vsphere.local] ; Spécification VMX : [moref=vm-1054] ; Instantané mor : [instantané-4606] ; Transports : [nbd] ; Lecture seule : [true]] a échoué en raison des erreurs suivantes : Impossible d'ouvrir le disque en lecture. Echec du téléchargement du disque 'vddkConnSpec>' L'agent n'a pas réussi à traiter la méthode {DataTransfer.SyncDisk}. Disque dur 3 (0 B) Disque dur 2 (0 B) Disque dur 1 (0 B) Disque dur 4 (0 B) Erreur : Échec de l'ouverture du disque VDDK [[M

Hi Community,Recently i install Veeam Agent on Windows Server 2008 R2 via VBR 12 Inventory and got an error  Failed to Verify C:\Windows\Veeam\Backup\Upload\VeeamDeploymentDll.dll Signature I found this page https://www.veeam.com/kb4677 and explain 2 possible causesAntivirus Block → Root and Intermediate CA is missingTo confim the issue we look at C:\ProgramData\Veeam\Backup\Svc.VeeamInstaller.log and gotFailed to verify file using the Authenticode provider. Verification status: A certificate chain could not be built to a trusted root authority. (-2146762486), last error: A certificate chain could not be built to a trusted root authority. All are pointing to Certificate Issue, so i install all CA listed on Veeam here https://helpcenter.veeam.com/docs/backup/vsphere/trusted_root_certificates.html?ver=120.After installing all CA still got same issue here. Are i missing something here? Any insight would be appreciated! 

Two things:GCP” Same inputs for Simple Calc and Scenario builder. Simple told me to use e2-standard-8, SB told me to use e2-highmem-2. REally different. Worker requirements - neither calculator provided any information on worker requirements. Is this something planned for, or it is too difficult?

Hi All, I have a VBR 12.3.2 server running in AWS as an EC2 instance.  Use Windows agent on other EC2s to back them up to an S3 scale-out repository.  The backups work as expected.  I am able to do file level restores with no problems.  When I try to do a restore to EC2 (create a new EC2) I get the following error “Unable to import the instance from an encrypted volume snapshot” when I click Next on the Reason screen.  I do have it set up to use a helper appliance.  Do you have any thoughts on how to get this working?  The volumes of EC2 that are backed up are encrypted with an AWS-managed key (aws/ebs).  But shouldn’t it be pulling from S3 for the restore? Thanks for any help you can provide.Scott

Query related a IAM user and IAM role:  Suppose if any customer has a Multiple AWS Accounts  with Control Tower Environment AWS setup, approx. 50+ account and want to take a backup of instance and DB backup using veeam backup for aws appliance,  is it possible using single IAM user and single IAM role to take backup of all workload of this separate account .  Require a IAM role permissions for Control Tower Environment AWS setup, In veeam documentation it is not available. 

Additional Details: Veeam Agent for Linux backup job fails with the following errors:[error] Failed to create volume snapshot[error] Failed to take volume snapshot[error] Failed to perform backup [error]Veeam snapshot kernel module not foundSystem informationSO: SUSE Linux Enterprise Server 12 SP4Kernel: Linux version 4.12.14-95.32-defaultkernel-default: kernel-default-devel-4.12.14-95.24.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.32.1.x86_64kernel-default: kernel-default-devel-4.12.14-95.128.1.x86_64dkms version: dkms-2.6.1-9.1.noarchveeamsnap: veeamsnap-kmp-default 6.3.2.1207_k4.12.14_94.41VBR Console: 12.3.2.3617VAL: v6.3.2.1207I read ready the list of compatibility with extended Linux distributions of veeamsnap and blksnap https://www.veeam.com/kb2804 couldn´t see the compatibility for a 4.12.14-95.24 or 32 or 128 also on rpm veeam repository I don't see a version(*)After to installed manually veeamsnap-kmp-default-6.3.2.1207_k4.12.14_94.41-sles12.4.x86_64.rpm and cons