Solved

I have already enter the password in Manage server but that did not resolve the issue

I’m experienced with Kubernetes but new to K10. I’m deploying it on my cluster via the K10 Helm chart. I’m running into a problem with the Ingress settings. I’m using cert-manager to provision a TLS cert via Let’s Encrypt, which I do regularly. Something is wrong with the Ingress resource generated by the Helm chart that means the http01 solver of cert-manager does not complete successfully.This is the relevant part of my values for the Helm chart: global: ingress: create: true urlPath: "" #url path for k10 gatewayingress: create: true tls: enabled: true secretName: ingress-tls class: public host: backup.mydomain.com urlPath: "" #url path for k10 gateway pathType: ImplementationSpecific annotations: cert-manager.io/cluster-issuer: letsencrypt-prodCert remains unprovisioned:$ kubectl get certNAME READY SECRET AGEingress-tls False ingress-tls 25mThe generated Ingress resource:$ kubectl get ing k10-ingress -o yamlapiVersion: networking.k8s.io/

 When I create a backup job and enable GFS retention, are the GFS backups automatically included in the secondary backup Copy jobs or do I need to configure GFS retention separately for the secondary Backup Copy jobs?

Backup Jobs not doing Storage Snapshot using vSAN.We have a VBR in Azure (AVS). The VMs are on volumes in vSAN. So the backup job finishes successfully. However, instead of doing a storage snapshot, the job does hot-add. The job has been configured to use storage snapshot. Since the VM snapshot is not removed right away, consolidation takes longer which affect the application running on the servers.   

I am not seeing any option to export the jobs. Am I missing something here? I dont want to use Configuration backup option just to export job configuration. There has to be a simple way to export the jobs or an enhancement should be raised to include this in future releases.  

If the Veeam Management Agent for a client is removed (stop managing) from the SPC, the option should be present for the Management Agent to first uninstall the Windows Backup Agent and delete all configuration from disk first (full cleanup for customer leaving). At present the Management Agent is removed but the associated Veeam Windows Backup Agent is left behind, orphaned (and in the case of a locked UI, inaccessible to the user) and then requires manual uninstallation.

Are full backups always created during daily tape jobs, or does it depend on the specific backup configuration?

Today Veeam updated the VB365 v8 page with an update to a new patch version - 8.0.3.1044 - KB4656: Release Information for Veeam Backup for Microsoft 365 8 Cumulative PatchesI downloaded and tried to run the installer and received the following error, so wanted to know if anyone else has tried this latest ISO?  I am not in Production just yet with this so just working through updating and have opened a case with Veeam too.If anyone has got this and fixed it let me know.  I will post back once Support gets back to me.

Adding hyper v host fails with "invalid credentials" or "spedified host is not a hyper v server"

 I have a question about backup job configuration when using S3 repository with immuability enabled.In the job retention if I set only 14 days without GFS, it means Forever incremental mode for me.If I click next I don’t have any error or warning to enable GFS like I could have with a Hardened repository.I remember on object, we only copy new blocks not files. Once immutability expires, unused/expires blocks are just deleted, but it’s not really clear for me.More intrigant Veeam is in capacity to “Merge” the files … and apply the retention ...The immutability works if I tried to delete the files 

My organization uses VMWare ESXi to manage all of our virtual machines.  We do not have the correct license to be able to do simple “copy” backups of our virtual machines (according to the error messages that I get when I attempt those).  We are having to run backups from the VEEAM agents, but, the last time that I had an issue and needed to restore, it was a pain in the a$$.  I’m assuming that this is because of the way that we are using the agents, but I really don’t know any better way.Would it be possible for someone to point me to or help me out with a step-by-step for the best practices for backing up our virtual machines?  How should my VM hard drives be set up to allow for the quickest possible backup/restore?

Hi there,currently i’m migrating a customers Veeam Backup for Microsoft 365 from local disk Storage to S3 (Wasabi). Doing this via the Script method from KB3067: How to Migrate Backup Data Between Repositories for Veeam Backup for Microsoft 365 and this works for me pretty well on another customers environment in the past. On the actual customers environment, i get Warnings regarding the Users Achive Mailbox:09.10.2024 07:08:36 :: Moving archive mailbox USERNAME completed with warning: archive mailbox USERNAME is not found in repositoryI have the info from my colleague, that this customer has no active archive function on many users (not all), so the warning is for sure correct.But as it’s currently in migration phase and not yet completed (will take a few days), i’m not sure if this will end up with problems after the migration (i.e. in a restore)? For sure, we will test some restores (with focus on those users with warnings).The script from KB3067 is not in support by Support, so con

How should data backups be structured in order to make most efficient use of Veeam Data Platform VUL licenses when backing up NAS File Shares? Suppose I have a NetApp filer with 10 volumes each with 300GB, would creating separate jobs for each volume consume 0 licenses because the data is rounded down to 0 for each one? Would it be different if all volumes were backed up in the same job? Does the total data get summed together anyways no matter the job distribution because the NetApp is added as a NAS Filer instead of each share being manually added?The docs here https://helpcenter.veeam.com/docs/backup/vsphere/nas_licensing.html?ver=120 don’t seem to clearly outline this case and how the licensing works for this.

So i been running V community for a year now backing up some vms and i just got a license to do immutable backups of a BareMetal server to a linux hardened repo. So i setup the repo with 7 days immutability and the backup with 7 days retention period. Setup Synthetic Full backups on Fridays and backup is running everyday.on the first Friday it did a full backup of server (like 1tb or so) then every day i guess its incremental since its only a few gigs. Now came this Friday and was a few gigs too. Wasn't supposed to delete it and create a whole full backup?Should i change retention from 7 days (to match repo immutability period) to keep 1-2 restore points instead? very confused  on this scenario on what im supposed to be seeing on the logs. What's the best course of action for this type of backup? 

Hi Guys,Amidst all my reading, prior experience with earlier versions of Veeam, Buexec, other related apps, trials and errors, its never too much or late to learn in the field of IT, especially from the experts, “Knowledge is never constant, only dynamic”. It has been a while, was so busy, Veeam is working like a charm. Note case below for a HYPER-V environment:Veeam BR 12 is at location A running fine Same BR 12 is at B doing nothing lol Location A is at HQ, fast bandwidth Location A & B are linked via WAN over “not so fast connection” Cloud backup was/is already used as offsite DR where important VMs/files are being backed up ( i came to this place and observed this)How can i use/setup Location B as a DR site/failover/redundancy?Can i also use location B to mirror exactly what is in Location A, if so, what is the process/best method?Your EXPERT GUIDANCE would be greatly appreciated as usual  

I’m trying to set up the Veeam SQL Agent and have it up and running on my SQL server, but when I try to backup a DB I get the following error:[ERROR]  Failed to backup database model. Error:  Error code: 0x80070005 Access denied. You must be logged in as a Windows administrator to create a virtual device. Failed to start VDI backup.I’m logged in as a domain administrator on the SQL server and am running the backup using a domain admin credential as well.  So I’m not sure why this is failing.

Hey there Community -I know in VMCA exam’s past, there was a limit to the amount of vCPUs you could use for VMware VM Proxies due to a “stop” concern (forgot the exact issue). Is this still a problem, and if so...do you know where the documentation is which discusses this? I can’t seem to find anything in the Guides or BP Guide. I think I do have it somewhere in a previous VMCA class “handbook”. I’ll post back the statement(s) when I find it.Thanks.

Hey guys I have problem with new version of vm when I am running job to get data power store and thought the 10/25 that connected to datastore ,the problem each time it's 5 minutes for running job. 

ciao a tutti, siamo di nuovo alle prese con lo spostamento di un server veeam su una macchina che, a differenza della attuale, sta fuori dal dominio come da migliori pratiche. Insomma il seguito di quanto discusso qui assunto che è cosa saggia disabilitare MFA prima di fare l’ultimo backup della configurazione e procedere, mi trovo davanti a un altro dubbio.Sul server vecchio che si chiama SRVVEEAM01, era stato tolto il gruppo di amministratori veeam “BUILTIN\Administrators” ed erano rimasti solo utenze di dominio.Dovrebbe essere sufficiente reinserirlo? Anche perché diversamente non saprei come fare. Il nuovo server si chiama SRVVEEAM, ma non è possibile inserire in veeam amministratori col nome del server che verrà, ovvero SRVVEEAM\Administrator.ho trovato questo articolo dove addirittura tirano fuori dal dominio il server, senza migrarlo. Cosa un filo azzardata a mio avviso. Però dice purtroppoAdd the VBR local admin as a Veeam Backup Administrator (BUILTIN\Administrators group is n

Hello, Thanks, cannot install VBR 12.1The server was running VBR 11.x, ran great for years, thanks Veeam! When I tried to upgrade to latest VBR, as downloaded from website The upgrade failed, complained about Veeam Agent for Linux. I tried to install again, and now there was no option to upgrade, just to install. So I clicked install and got error message I did a manual uninstall as perhttps://forums.veeam.com/veeam-backup-replication-f2/how-to-uninstall-v12-community-edition-completely-t89675.htmlhttps://forums.veeam.com/veeam-backup-replication-f2/trouble-installing-uninstalling-veeam-backup-replication-t49674.html But still, get the same error message as shown above.Here is the complete install log fromC:\ProgramData\Veeam\Setup\Temp\VbrSuite_26_05_2024_11_10_54.log[26.05.2024 10:32:34][INFO] Configuration file: G:\Setup\VBRSettings.xml[26.05.2024 10:32:34][INFO] Engine is starting...[26.05.2024 10:32:34][INFO] Creating wizard instance...[26.05.2024 10:32:34][INFO] Initializing engi

We have enabled malware scanning,  and We got a warning that some of the servers has some potential malware detection.Specifically "Onion Links". I enabled inline entropyI took a look a the full logs of the scan on mount server C:\ProgramData\Veeam\Backup\Malware_Detection_Logs , and only the logs for windows machine appear here,  however, as confirmed by Veaam's support, scanning backups for Linux machines are not supported at this time. So Linux VM logs are missing. When you click the malware detection event, there's nothing nor paths in the details.I equally checked c:\VBRCatalog\Index\Machines\Affected-Linux-VM\ransonwareidx , but i still cannot identify what files or path-to-Files.How can i scan our Linux machines to determine the paths to the files of the Onion links malware detected? I would like to identify what files are being flagged as malware so i can "mark clean" if need be.Any help regarding this please and thank you

Hi,I have upgrade k10 this morning and i have this error on one container:Failed to pull image "gcr.io/kasten-images/admin:7.0.8": rpc error: code = NotFound desc = failed to pull and unpack image "gcr.io/kasten-images/admin:7.0.8": failed to resolve reference "gcr.io/kasten-images/admin:7.0.8": gcr.io/kasten-images/admin:7.0.8: not foundIf i check the repo, this image is missing : 

VDRO ver 7.1, Failover failing unable to find Distributed Virtual Portgroup. We are no longer using DVPG in our environment but instead use logical switches in NSX-T. Building the recovery location shows that the Orchestrator can see the Logical switches but actual failover looks for DVPG instead of using the logical switches as defined in the recovery location.[Error] The Distributed Virtual Portgroup prod-10.111 was not found on the DatacenterDCDataCenter.Network Mapping shows the source network mapped to the target logical switch. BackupNetwork (ESDDataCenter) to prod-10.111 (vDS_NSX_Compute) What am I missing here? Why is VDRO looking for DVPG instead of the logical switch? This is causing the VM not to power on and not be connected to the network. Thanks again for your ideas.

Hello everyone,Veeam Inline Entrophy analysis feature checks if any encryption has started on VMs. Does this feature additionally perform text analysis with onion links and AI/ML? In other words, is it enough to scan the backup it received to perform these analyses or should the guest index file be open in the relevant backup job and the credentials of the machine should be entered?

customer on veeam v12.2. They have storeonce at both sites and S3 at site2.With backup copy at storage level (catalyst), Veeam controls the copy via the storeonce appliances performing the replication.If I choose image-level backup copy, this gives options for VMs and repos to copy. We also have “data transfer” for Direct. When it says direct is this storeonce to storeonce like storage level copy or does data go via another route?I need to know if there are considerable differences. thanks