Solved

Hello,Ran into this error when building a new K8s kubeadm v1.26.5 cluster.I can install K10 v5.5.2 but all versions higher will fail the ‘gateway’ pod with this error.  Nothing in the logs except this single entry.Looked at the release notes from v5.5.3+ but cannot find any mention that might alert me to the cause.I suspect there is a base image being pulled in that is not compatible with the underlying hardware. Environment:K8s kubeadm Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.5", GitCommit:"890a139214b4de1f01543d15003b5bda71aae9c7", GitTreeState:"clean", BuildDate:"2023-05-17T14:14:46Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"} Kustomize Version: v4.5.7 Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.5", GitCommit:"890a139214b4de1f01543d15003b5bda71aae9c7", GitTreeState:"clean", BuildDate:"2023-05-17T14:08:49Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"} K8s host VMware VMs - compatibility v19

Hi,I have a Dell Data Domain repository for local backups and i want to send some critical VMs backups to the AWS S3, to withstand disasters.So when I tried to create a scale-out using the existing Dell data domain and AWS S3, the interface told me that all tasks that use the Dell data domain will be updated to point to the the scale-out repository.Is there a way to keep the majority of backup jobs pointing to the Dell data domain and choosing some backup jobs to point to the scale-out repository?

Bonjour à tous,J'ai demandé un devis sur la plateforme de partenariat Veeam. Je voulais savoir si ce devis est final.Cordialement

We’ve been testing our Orchestration Plan and after failover to our DR site, the certs on our vCenters were replaced and broke the connections between our DRO and vCenters. Had to refresh the connection so the DRO can take in the new certs. However, when we tried to failback to our primary site, we had the login error to vCenter. The issue was fix when we had to go into the built-in VBR and refresh the connection in VBR itself.  I would tend to think that DRO itself would be able to restore the connections within its built-in VBR and VeeamOne. Let me know what you think or if I’m missing something here. 

Hi team,I’d like to know how to handle multiple export locations.Do we need to keep it at a storage level? Is it supported with NFS storage (where replication is handled at storage level) with different IP addressing? Can we use an import policy pointing to the “DR IP” of the replicated storage NFS volume?Thank you. Mattia

Greetings everyone!I am very new to Veeam, did a few installs & backup/restore already with the software but still I’m way too far from understanding the full structure of the tool.Is Veeam a viable solution to backup vCenter Server Appliance? Currently the organization I joined recently has a nightly backup of the appliance. (doing a research about how Veeam can be a viable solution in long term, so I would greatly appreciate if someone can share their expertise on the matter, thank you!)

I have what I hope is a simple question. What’s the best practice for the a high availabilty SQL server for the VSPC or Veeam ONE configuration database. I see in https://www.veeam.com/kb2301 how to deploy SQL AOAG for VBR and VEM. I’m not sure if this applies to VSPC or Veeam ONE.

Hello guys! It’s the first time I got this error message in one of my backup jobs. I got it in random virtual machines, after a retry the backup is ok.I check the logs:On the VBR I have this:“Error        Failed to construct ClientAgentProtocol. (Veeam.Backup.Common.CRegeneratedTraceException)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.Common.CExceptionUtil.RegenTraceExc(Exception originalExc, String formatString, Object[] args)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.AgentProvider.CClientAgentProtocol..ctor(CBaseAgentService svc, Boolean redirectOutput, Version version, IAgentProtocolLogger logger, IOutputAnalyzer outputAnalyzer)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.AgentProvider.CClientAgentProtocol..ctor(CAutoRef`1 svcRef, Boolean redirectOutput, Version version, IAgentProtocolLogger logger)[27.03.2023 10:06:42.851] <46> Error           at Veeam.Backup.AgentProvider.CProxyAgent.StartClientInter

I'm seeing this error "Failed to process VM: Failed to create MachineMutex" when doing storage snapshot. The first try fails but the 2nd try succeeds and usually the issue comes and goes. Failed to create snapshots on primary storage: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceededFailed to create storage snapshot for datastore abcdef: Failed to wait mutex sandiscover7c39d713-bdbb-40f1-ac8d-af87774de299_b72e5bb7-87e2-4802-9043-2d6a76f9052d: timeout 600 sec exceeded Who has seen this issue and cause/resolve info? 

Hello Guys, is it possible? Storage Spaces Direct for Veeam Server (only one Server NON cluster)Disk whit trww way mirroring?How many disk failure a can have? Thaks a lot

Hello Everyone,Someone asked this question in Nutanix Forum:“We are running asynchronous Protection Domains and also employee Veeam backups of VMs. If we failover to the secondary site and then failback to the primary site, Veeam no longer recognizes the VMs in previously created backup jobs. We have to delete all the old backup jobs and set them up again. This is with ESXi hosts. Is that normal?”Didi anyone face this issue before and how to fix it?

Bonsoir à tous, j’ai un soucis avec de la sauvegarde sur Tape HPE 1/8 G2 Autoloader. Si je lance un jeux de sauvegarde, ça échoue avec l’erreur ci-dessous : Message d’erreur  “Library does not contain any enabled tape drive”  Version de Veeam : 12

Hallo zusammen,ich verwende den Veeam Agent (Windows). Ich bin nicht sehr technikaffin, deshalb habe ich nach einer einfachen Möglichkeit gesucht, meinen Laptop auf einer externen Festplatte zu sichern. Ich habe den Backup-Job nach einer YouTube-Anleitung für den Veeam Agent für Windows konfiguriert. Eine Zeit lang hat es gut funktioniert, aber jetzt bekomme ich Fehlermeldungen. Einige Backups wurden mit der folgenden Warnung beendet:"Der freie Speicherplatz am Sicherungsort [...] wird knapp (13,8 GB frei von 465,8 GB)."Nun wird der Backup-Auftrag aber gar nicht mehr ausgeführt, weil angeblich nicht genug freier Speicherplatz vorhanden ist."19.05.2023 12:41:46 :: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Es steht nicht genug Speicherplatz auf dem Datenträger zur Verfügung Failed to write data to the file [E:\[...]Backup NotebookRG2023-05-19T123800.vbk]. Failed to download disk."Ich k

Hello Everyone,I have a challenge in decreasing the backup window for 60TB Oracle DB which takes 16 hours with transfer rate 1GB/s against Networker which takes only 10 hours.Current configuration VBR v12, Oracle RMAN plugin with 10 channels, Veeam basic compression, SOBR Repo performance mode with 10 NFS shares on Pure storage, gateway server auto.Network speed 40GB with jumpo frame enabled. 

Hello,With Veeam Agent for Microsoft Windows FREE edition, I wonder if there’s a way to test the encryption key? I tried removing job but when restoring it still didn’t ask for password.And, can I re-add job after removing it or add the current jobs to another PC?Thanks

Hard disk 20 (3.5 TB) 1.9 TB read at 41 MB/s [CBT] - Can anyone tell me how long it should take this disk to complete backups? The backup ran for 13:21 hrs and failed to complete due to backup window setting. The backup window for the job is set for 15 hours 5pm - 8am. In addition how can i confirm if  a FULL or Incremental backup is running for a VM that failed backup.Backup type is VMware Image Backup. 

We have a file server that we are going to backup directly to an S3 compatible storage with immutability enabled.We want to put an incremental backup with full synthetic.Is full synthetic already compatible with S3 immutability with direct object storage?What do you recommend for the least resource consuming backup type? Thank you very much.

We are using Kasten K10 v5.5.0, MinIO as S3 storage. Our application (RabbitMQ) is deployed in a AKS cluster in HA with 3 nodes and we backup the snapshot of the PVCs successfully. After reinstalling the application in order to simulate a disaster recovery, we meet the following error during the restore phase, using as restore point the one related to MinIO storage: Restoring Application Components failureIf instead we use the restore point native to the cluster, our restore is successfully. So the problem is only related to the case in which the restore point is the one outside the cluster.We don’t think this issue could be related to some timeout into k10-config configmap because our restore procedure fails just after a minute and those values are greater.  Do you have any idea about this error?Thank you in advance for your support and let me know if you need other details.

Dear Veeam Team,I would like to place a feature request with you. However, I am not sure if this is placed correctly here. If not, please let me know.I noticed that an external export to a Microsoft Azure storage is possible, but what I miss a bit in a productive operation is the access from Kasten K10 to the Azure storage internally via private link and not via public interface.Is there a possibility to extend the dropdown with a self defined URI endpoint for such cases?Regards

I have just built a Server 2019 standard physical server running the latest/current build of Veeam 12. It is not joined to a domain. I am trying to connect it to a Server 2016 standard Hyper-V server, also not joined to the domain. This is a standard 2016 OS with the Hyper-V role installed, not the Hyper-V version.I get the same error commonly reported when I try to connect them: Access denied or timeout expired. Check for local admin privileges. Possible reasons, invalid credentials or host is not a hyper-v server.The credentials I am supplying are in HOST\USER format, and they are definitely correct. If I try to open file explorer to \\HVHOST\C$ from the Veeam server, I am prompted for credentials. Entering the local admin creds in HOST\USER format here also give me an access denied error.I work for an MSP and the manner in which the license was generated does not give me access to support. I’ll try to get a co-worker to contact their support while I see if anyone here can assist me.

Just want to run this by all the Service Provider Gurus here. It seems that for Multi-tenant O365 Veeam no longer wants you to place the console on the Cloud Connect server. Instead you install it separately and have it connected to the VSPC and expose a portal for restores. The old method of having the CC tenants go through the SP in the local VBR server is not seen as the optimal option. This diagram from the BP would suggest this:  Does that sound correct? I have been away from O365 for a bit now and the world is changing.

env:1、vbr11a、vspc6、backup server（win2022） with backup agent success。2、upgrade to vbr12、vspc7。3、backup server（2022） with bakcup agent failed。4、no Capacity/Archive tier，just back up to vbr local disk.5、Only two Servers（vbr + vspc）。

One thing I really miss from other backup products I have managed, more detail displayed about what an active job is doing.  For example, a running Backup for 365 is taking a really long time.  The whole job summary says how many objects it has processed, number of items processed and the data transferred.But it does not show the same details in the actions. It only shows the name of the item and how long it is taking.  It would be really handy to know how many items and how much data has been transferred at the object level. Would help me understand what is going on and would allow me to investigate what changed to prompt a difference in backup times. 

Any idea for this? It’s pure Hyper-V with Azure, not AWS. 1/31/2023 10:06:49 AM Warning Failed to connect to AWS plug-in: Failed to login to platform service: The HTTP resource that matches the request URI 'https://vbr11:9402/api/v1/account/login' is not supported.  

HiWe running an VBR11.0.1.1261 using SOBR with an QNAP as capacity tier. QNAP is supported S3 repository by Veeam and Veeam is partnering with QNAP. Also Immutable option should work as stated in https://www.veeam.com/sys469.After running while this setup we start getting strange errors.  Error deleting multiple items from SOBR invalid URI - which refers to cleanup operations on the S3 repository base on retention policy. VBR runs this operations in regular intervals.  In Veeam One - Data Protection View we get error type [v] (never seen before) and a Knowledge information that stats: S3 object storage added to VBR as repository may face overflow with small metadata file of 0 kb size. Cause: malfunction in object delete algorithm. Resolution - contact support to get a private fix. To get backups to SOBR working again we to delete objects from QNAP using qnap utilities. Now we try to synchronise SOBR with VBR DB but it takes forever. Has somebody came across this situation with AWS S3 o