Solved

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 ;)​

Hi,I have installed the testlicence of veeam o365 Version 7. Exporting single items from a mailbox works fine, but export the hole mailbox of a user ends up with: unable to read beyond of the end of the stream. How can I solve this?

Hi all,I’ve trawled the KB’s and internet on this but I've added a Wasabi Object storage to my Backup and Recovery console version 11.0.1.1261 to add as a cloud backup location and it doesn’t show when i go to do either a backup or a backup copy. In a lot of other posts it says i have to add it under a “scale out” repository but i don’t have the “scale out” option on there. It currently shows under my “backup repositories” as an S3-compatible type with all my other “windows” type backup locations but it doesn’t show me the location when i go to add it as a destination in the backup.I did have this issue when setting up Office 365 backup but found i had to create the object storage and then a local storage pointing TO the Wasabi one and that worked but creating a local one in Backup and Recovery doesn’t give me the option to point it to the Object one like it did in Office 365 either.Any ideas would be great.ThanksIan 

Hi I have looked around but apart from the Kanister repo I have not been able to find a location with a bunch of blueprint examples for various different applications. It would be nice if people could also submit their own. Does such a repo exist anywhere? I have had some new users ask about this as well. There are the ones on the kasten-io site but some of those don’t work anymore. In one case the container name has now changed in the helm chart. 

Hey everyone, Has anyone ever seen Veeam throttling bandwidth with the RMAN plugin? I’m working with a really beefy Veeam environment at the moment. Source data is all on flash, 40GbE networking available, high performance RAID controller + 4x RAID 60 repositories in a SOBR. Backups are flying for most workloads, VMware, Agent, NAS etc, but RMAN is letting me down. For example, a Veeam Agent using an unoptimised network path via the firewall can still do over 200MBps (Firewall is the bottleneck here), but RMAN is doing 5-7MBps and it’s on an L2 network with no firewalls involved. Testing with iperf can get 6-8Gbps easily without tuning between the hosts and the backup repositories, one test with iperf between the backup repositories was giving 26Gbps, so the network really is moving quick.When I’m going through the Veeam logs I’m finding things like this: plugin_co| [8b43] >> : Invoke: Network.UpdateThrottling\n{ (EInt32) KbpsReadBandwidth = 0\n (EInt32) KbpsWriteBandwidth

Hi All,This is my first post on this site.I have been asked to backup a database on one of our servers before setting it up to be decommissioned. The DB needs to be retained for 40 years and before I can archive off the DB I need to ensure that we are able to access it. I am very  new to veeam and wondered if anyone knows how I can backup just the DB and not the VM? Any help would be greatly appreciated.

Hello support, We’ve tried to upgrade Kasten from 5.0.10 to 5.5.2 as suggested by the Setting interface page. When applying the commandhelm repo update && \    helm get values k10 --output yaml --namespace=kasten-io > k10_val.yaml && \    helm upgrade k10 kasten/k10 --namespace=kasten-io -f k10_val.yaml --version=5.5.2 The upgrade throw the following error:Error: UPGRADE FAILED: cannot patch "crypto-svc" with kind Deployment: Deployment.apps "crypto-svc" is invalid: spec.template.spec.containers[3].image: Required value When looking at the helm manifest using the command “helm get manifest k10”, we saw that the garbagecollector-svc introduced in 5.0.11 didn’t have an image: We’ve tried to perform an upgrade to 5.0.11 and to 5.5.1 to try escaping from this issue, we even perform another upgrade to 5.0.10 to regenerate the manifests but none of these solutions worked. Can you please help? Thank you very much in advance !