Solved

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

Ich habe eine externe Festplatte, auf der in der Partition 1 das Recovery System und in der Partition 2 die Backup-Daten liegen (Standard Setup)Wie erzeuge ich in der Partition 1 eine aktualisierte Version ohne die Partition 2 zu löschen?Habe ich in den Standard-Optionen des “Create Recovery Media” nicht gefunden. 

Forever Forward Incremental Backup + Backup Copy job Tape Out.With one Forever Forward Incremental Backup job can we configure multiple tape out Backup Copy job with Virtual full option for each day targeting to different media tape group.Primary Job will be one (forever forward incremental backup job) and a separate Backup copy jobs for each day Monday to Sunday.Will it work. And  if we restore tape backup from any one day (Monday group to Sunday group) i hope will it restore the full backup.

Hola, estoy planteando implantar un servidor de veeam 365 en nuestro cloud privado en OVH para hacer backup de los O365 de nuestros clientes y dejarlo en un repositorio de Wasabi, he visto que los datos han de pasar si o si por el proxy, y creo que eso, aunque todos los componentes están en el cloud, me puede ocasionar problemas de transferencia, que opinión os merece? algún consejo? Un millón de gracias

Hello,I am experimenting with VBAR11 in a home lab. The backed-up data itself is not important.Boot into recovery mode via usb key. On the usb key is a .vbk file, no .vbm Use bare metal recovery option, veaam is not able to find the .vbk, if I manually select the .vbk, veeam complains about corrupted .vbm file.So it seems that recovery agent, must have a valid .vbm. but in a disaster recovery situation and the .vbm is corrupt, how do i restore?I do know that VBAR itself, can import .vbk without .vbm, so cannot recovery agent do that same?Second question, using the the recovery boot agent, how do i mount the .vbk?Thanks,Dave

Has anyone ever seen a backup job fail with the error “Full storage not found”? I have no orphaned restore points, repository is good...everything looks perfectly fine. The repository is accessible and I can see the vbms and vbk files in it. I can’t find an answer for this. Full error is below: 1/23/2023 2:50:08 PM :: Failed to pre-process the job Error: One or more errors occurred.  1/23/2023 2:50:10 PM :: Unable to apply retention policy: failed to delete backup files Error: Full storage not found  

I am working to deploy VM365 in an automated way, and was hoping to use the Azure Marketplace offer to deploy it. However, it seems they haven’t updated the offer to include the latest version 7.0. Does anyone here have any idea if that will be done soon? The offer is listed at https://azuremarketplace.microsoft.com/en-us/marketplace/apps/veeam.office365backup.

Hey all, small question: I have seen in the release notes of v5.0 that the free starter license we are using, will be decreased from 10 to 5 nodes. Will this also affect my starter license enabled in my k10 deployment? I am afraid, that I cant backup my 6 nodes cluster after that upgrade anymore. Thanks a lot.  EDIT: Seems like veeam k10 doesnt count the master nodes that cant schedule pods, is this right? 

Hi,we have a customer with 15 different vCenters (each one is different environment)how many vCenters can we connect to one Veeam backup server ? didn’t find any KB on that.each one have it’s own proxy server for backup.

HiI spun up the example used on the K10 documentation page for Postgresql Application Consistent backup but it looks like that blueprint no longer works. https://docs.kasten.io/latest/kanister/postgresql/install_app_cons.htmlOn quick inspection I see this error: message: Failed to create pre-backup Kanister phase - cause: cause: message: "Failed to exec command in pod: container postgres-postgresql is not valid for pod postgres-postgresql-0"but the container deployed by that chart is in fact named postgresqlcontainer nameI have not done a lot with Blueprints yet so will want to dig deeper but I assume my next step is to change this part of the blueprint to represent the right container name? I have also attached the logs.  

Hey Guys,Has anyone performed a patch update? Please tell what can go wrong after that?

Hi Folks, I am back into the wild and wonderful world of Veeam Service Provider Console after a brief sojourn. I wanted to see if there is a quick answer to this and if my old solution perhaps has a better one now.I have a VBR that is connected to the Service Provider and all backup copy jobs are working fine. In VSPC the company is smiling with a happy green Healthy! However, at the VBR level the when pressing the Management Agent icon it complains that is connecting, and can’t connect after rolling through all the gateways. I tried running through the SP properties again but no luck. Is it time to un-install the pesky agent and redeploy? The ClientAgent_error, Communication and ClientAgent logs have things like CloudGate “No such host is known” and “Endpoint Hanshake Failed” and The write operation failed, see inner exception. ---> System.TimeoutException: Could not finish read operation in timely manner.Now could this be that if they have running backups and have used up the Tena

HelloI’m trying to find a solution to a hypothetic scenario: tl;dr is it possible to change/swap the target repository of a Backup Job by the repository of the BackupCopy Job I have 2 datacenter, 1 VBR server, and 2 repository on each site, one for backup job target, and the other one for BackupCopy job targetevery job have a copy job associated with it, and there are a few dozens of jobs running every dayI want to plan the failure of the repository system and being able to continue to do backups, in the case where the issue is hardware or would need multiple days to repair I have no problem with restoring from the copy jobs, all the data is there as intended, but how to restart the service of “backups” during this failure?so is it possible to tell VBR to use the the existing backup copy chains to use as an existing repository (I can’t seem to be able to remap)or is that impossible and I would need a new repository, and so startiing new backup chain ? 

I want to added multiple VCentres spread across trusted domains to one console ( 1 from each Domain)..  At first glance I should be able to add the the second Vcentre Server. Is this as straight forward as it appears?

Hallo Zusammen,aktuell steht wiedermal eine Frage im Raum, wo ich den KB´s von Veeam nicht weiter komme.Wir haben einige Applikationen in Docker überführt und diese Container laufen einer Linux-VM auf dem Hyper-V Cluster. Da einige der Container ihre eigenen Datenbanken zur Verfügung stellen und Veeam B&R sicherlich nicht mit “application-aware processing” in die einzelnen Docker-Container schauen kann, steht die Fragen im Raum: Was geschieht mit den Daten der Container beim Backup der VM durch Veeam? Werden diese inkonsistent?Wir haben uns schon ein kleines Script-geschrieben, welches die Docker-Container vor dem Backup stoppen und anschließen wieder starten soll. Aber dies können wir nicht einsetzen, da die Dienste 24/7 verfügbar sein sollen.Wir sind für alle Vorschläge dankbar! Grüße

If you want to restore a deleted Exchange mailbox (on-prem), you first have to create an empty mailbox within Exchange for the user. This has already been described earlier: https://forums.veeam.com/veeam-backup-replication-f2/restore-deleted-mailbox-with-veeam-explorer-for-exchange-t16174.html Challenge is, while creating a new mailbox you also create a new ID for it. This leads to loosing some functionality (permissions to folders for 3rd parties etc., recurring appointments, etc.). Is there another known way to recover the mailbox including its original ID?I would rather have expected VEXE to create the mailbox for me while recovering - including all metadata.

Primary backup is configured with daily retention 14 days , synthetic on Sunday and GFS (Monthly - First,  Yearly- April) option and target to disk storage.Monthly - 1st of every month Yearly - 1st of April Now Backup to  Tape , above primary backups ,  incremental in incremental media pool , weekly synthetic  backups  to go in weekly media pool, monthly in monthly media pool, yearly in yearly media pool. like wise is this possible with GFS media pool configuration.

When i create a profile/policy for k10 as yaml does this resource have to be in the kasten-io namespace or can they be defined in any namespace? e.g. “my-namespace” apiVersion: config.kio.kasten.io/v1alpha1kind: Profilemetadata: name: sample-profile namespace: my-namespaceapiVersion: config.kio.kasten.io/v1alpha1kind: Policymetadata: name: sample-backup-policy namespace: my-namespaceWhat about the secret necessary for the profile? Can this be definded outside the kasten-io namespace ?Thx in advance ;)​