Single production datacenter backup copy to Veeam Data Cloud Vault - 5,000 VMs
Recently active
We've experienced backup corruption due to an unforeseen circumstance. I'm familiar with the scheduled health check and its flexibility, and I perform daily checks. The backup is not file share one. As I understand it, the health check is a diagnostic tool, not a repair function. My question is: Do we have any repair capabilities to recover from corrupted backups and interruptions? Are there any repair utilities for addressing unique error messages?
Hi everyone, I have two Veeam proxy servers that max out their RAM (20GB) once or twice a week for about an hour. I’m trying to find out which jobs are running on the proxy at the time of the spike. I know the affected VM's name but need to identify the specific job running when memory usage is high. Proxy details:VMware VM With 20GB RAM (recently added 4GB, but still seeing spike)OS WindowsMax concurrent tasks: 16 Is there a way to track this from the proxy server or within Veeam Backup & Replication? Any insights would be appreciated
Hi, I googled a lot, but couldn't find anything suitable. I have a test VM in a VMware Workstation17. I back up this VM (Win11 with TPM) with Veeam Agent for Windows (newest version). I would now like to bring this VM to the vCenter. What is the best way to do this? Do I have to install a Native Keyprovider in vCenter first? Or can I create a new VM Win11 in vCenter without disk, then attach the vmdk disk file?Thanks for your help!GreetingsNovell2
Hello,For one of the applications, kasten backup policy is failing during export metadata phase. Error:- Failed to export collection Failed to add repository artifact for collections Unable to lock repo artifact Error while attempting to acquire lock resource conflict
One of our customers recently renewed **Veeam Backup & Replication (VBR)** in December, but is now evaluating a migration of their **58 VMware host** infrastructure to **OpenShift Virtualization (OCP-V)**. We know that to back up workloads on OCP-V, **Veeam requires Kasten K10**, however, **there is no direct conversion strategy** between VBR and Kasten, which poses a challenge in licensing continuity. Veeam currently suggests purchasing **Kasten as a standalone solution**, without considering the prior investment in VBR. This opens the possibility for the customer to explore other solutions such as **Trilio, Veritas, or other backup vendors** with native integration into Kubernetes environments. The key question is: **Is Veeam willing to sustain VBR without offering a transition path to Kasten, risking customer non-renewal? Or, on the contrary, should you design a strategy that allows you to ensure recurring business of between 42 and 58 nodes with Kasten?** This case highlights the i
Hello, We are using Veeam Backup & Replication 12.3.0.310, integrated with Veeam Backup for AWS 8.1.0.7. Our environment is monitored using Zabbix, and we have developed PowerShell scripts for this purpose. However, we are facing difficulties retrieving information about jobs running in AWS from our Veeam Backup & Replication server. While we can successfully monitor all on-premises jobs, we are unable to list the jobs running in AWS. The integration is properly configured, and we can access information about the AWS-hosted servers, but the jobs themselves are not visible. Is it possible to retrieve this information using PowerShell? Thank you!
I used Agent to back up a Linux virtual machine on the UIS platform, and I found that the Data Size of the full backup in Disk was inconsistent with the size scanned in the backup task Status. See the screenshot.
Hi all,I tried to do backup of my elasticsaerch database and I have standard blueprint object which goes with that backup process apiVersion: cr.kanister.io/v1alpha1kind: Blueprintmetadata: name: elasticsearch-custom-blueprint namespace: kasten-ioactions: backup: outputArtifacts: esBackup: # Capture the kopia snapshot information for subsequent actions # The information includes the kopia snapshot ID which is essential for restore and delete to succeed # `kopiaOutput` is the name provided to kando using `--output-name` flag kopiaSnapshot: "{{ .Phases.backupToStore.Output.kopiaOutput }}" phases: - func: KubeTask name: backupToStore objects: esMasterCredSecret: kind: Secret name: "elasticsearch-es-elastic-user" namespace: "{{ .StatefulSet.Namespace }}" args: namespace: "{{ .StatefulSet.Namespace }}" image: "ghcr.io/kanisterio/es-sidecar:0.112.0" command: - bash - -o - errexit - -o - pipefail - -c - | host_name="{{ .Object.spec.serviceName }}.{{ .StatefulSet.Namespace }}.svc.cluster.local
K10 7.5.4 kubernetes version v1.29.8-eks-47985ba I’m interested in moving my velero backups over to Kasten, but so far its been quite unreliable and very inconsistent experience for me, debugging has been a huge hussle due to the fact that the logs almost never points at an issue properly, but i’m fully open to the possibility that this is a skill issue on my side… so please enlighten me. Additionally the kubernetes is using a private cloud environment that is similar to AWS itself. I have a local pypi server, with 25gb of data in total, a local object storage (aws s3 like) that seem to be consistent in being able to back up so far, compressed to 14gb after upload all good… even restore worked once. as part of my effort to migrate into kasten i tried to backup to s3 too in addition to my local object storage. i made two attempts in total, both resulted in the following errors : kubectl get --raw /apis/actions.kio.kasten.io/v1alpha1/namespaces/tlv-infra/exportactions/scheduled-sdzjhs8vx
Hello, I want to run backup job, which was already working. It was (dont know how) interrupted, but when I run job manually or with scheduler automatically. Actual version: 8.1.0.3503 Starting job: M365 backup...[03.03.2025 11:52:52.261] 8 (1) Error: The job is already running.[03.03.2025 11:52:52.261] 8 (1) Type: System.ServiceModel.FaultException[03.03.2025 11:52:52.261] 8 (1) Stack:[03.03.2025 11:52:52.481] 1 (1) Error: The job is already running.[03.03.2025 11:52:52.481] 1 (1) Type: System.ServiceModel.FaultException[03.03.2025 11:52:52.481] 1 (1) Stack:[03.03.2025 11:52:52.481] 1 (1) at Veeam.SPP.Communication.TypeProvider.InvokeResult.ThrowIfError(Boolean enableRpcErrors)[03.03.2025 11:52:52.481] 1 (1) at Veeam.SPP.Communication.TypeProvider.InvokeResult.GetResultOrException(Boolean enableRpcErrors)[03.03.2025 11:52:52.481] 1 (1) at Veeam.SPP.Communication.TypeProvider._RemoteProxy.Invoke_TReturn_WithParameters[TReturn](InvokeArg invokeArg, String methodName, Object[] parameters)
64 likes
58 likes
50 likes
28 likes
20 likes
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
