VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
After a power failure a VM on vSphere 8 couldn’t be started. But that’s no problem as we have backups…As I tried to restore the VM the following errors occured: 10.04.2024 07:59:45 Error Restore job failed Error: Invoke failed. Agent: 'e247ee60-7820-47f4-b1b1-ad507aed6146', Command: 'DataTransfer.RestoreText', parameters: {(EStringArray) Links[]=[veeamfs:0:ebc7d8da-8aa5-4be0-b937-8a278d664dc7 (67)/summary.xml@nfs41://192.168.200.10:/Backup/ETS_2/ETSD2023-10-21T050434_A040.vbk](EBoolean) Option.Remote=false; } As I have no idea what’s up I kindly ask you to point me in the right direction… Regards,Joerg
if i restore snapshot into new namespace it works.But if i delete that namespace and restore from K10/Applications/Removed then i will always get error: cause: cause: cause: cause: cause: message: "Specified 1 replicas and only 0 are ready: could not get StatefulSet{Namespace: rumburak-novy, Name: my-postgresql}: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline" fields: - name: statefulset value: my-postgresql file: kasten.io/k10/kio/kube/workload/workload.go:47 function: kasten.io/k10/kio/kube/workload.WaitForWorkloadReady linenumber: 47 message: Statefulset not in ready state fields: - name: namespace value: rumburak-novy - name: name value: my-postgresql file: kasten.io/k10/kio/exec/phases/phase/restore_app.go:773 function: kasten.io/k10/kio/
Hello,I try to have acces to the K10 dashboard outside my k8s cluster labs,I try the loadbalancer option but I can’t have an external ip (always in pending)kubectl get svc gateway-ext --namespace kasten-io -o wideNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTORgateway-ext LoadBalancer 10.97.236.105 <pending> 80:32244/TCP 52s service=gateway All my pods in kasten-io are running:kubectl get pods -n kasten-ioNAME READY STATUS RESTARTS AGEaggregatedapis-svc-58ff985f69-lbksl 1/1 Running 0 21sauth-svc-8899c7bfc-g2b7h 1/1 Running 0 22scatalog-svc-5d4fd45787-wb5wx 2/2 Running 0 22scontrollermanager-svc-57dfb767b4-lw5hf 1/1 Running 0 22scrypto-svc-576b9b56d6-b57bl 4/4 Running 0 22sdashboardbff-svc-7fb956f4dc-pjvtb 2/2 Running 0 22sexecutor-svc-76c6857
We have Veeam pushing a couple of Nutanix clusters. Jobs are split between the clusters and Nutanix is replicating between the two clusters so if one goes down…Issue that we’re seeing is when Veeam is backing up a server, snaps are being created to do the backup. Replication between the two Nutanix clusters is seeing the snap and replicating it to the second node. Since the snap doesn’t have a retention set, Nutanix is setting the snaps for 60 day retention. When we’re starting to deal with file servers north of 20tb, this becomes and issue. Is there anyway to force Veeam to set a short retention on snaps or is this something Nutanix should address?Thanks in advance.
I have already install kasten on top openshift, but there are 3 pods that cannot running with an error notification crashloopbackoffaggregatedapis-svc frontend-svc state-svc any solutions to solve this issue ?thank you
I keep getting the following error from K10 dashboard, it’s stopping me from restoring/ or doing anything on the dashboard:I am on 6.5.4, I have NOT updated, I’ve even reinstalled it, at the same version and it keeps popping up,
hi,I’m trying to do migration from openshift to eks, there were some steps that i have already passed such as backup, export and import to destination cluster on eks, but when I tried to do restore to eksi got an error issue “Cluster does not support restoring DeploymentConfigs”, I tried to use transnform set to change some parameters on deploymentconfigs but it still didn’t work any solution for this issue ? Cluster does not support restoring DeploymentConfig
Hi,I have deployed kasten10 on OpenShift 4.13 as an operator. After that I created a route. However, i still cannot access the k10 dashboard. Regards,MLX
Hi,I have an instance of Kasten K10 on the free license, and need to use Generic Volume backup.I have already requested and received a Generic Volume Backup key from support and updated my helm installation to include the key.I have also configured Kanister sidecar injection, and the sidecar containers are injected correctly.However, if I try to run a backup of the application used for testing, I run into this error message:{ "message":"Failed to backup data to Kopia API server", "function":"kasten.io/k10/kio/kanister/function.(*backupDataToServerFunc).Exec", "linenumber":155, "file":"kasten.io/k10/kio/kanister/function/backup_data_to_server.go:155", "cause": { "message":"Failed to establish connection to Kopia API server", "function":"kasten.io/k10/kio/kanister/function.backupDataToServer", "linenumber":218, "file":"kasten.io/k10/kio/kanister/function/backup_data_to_server.go:218", "cause": { "message":"Failed while waiting for Kopia API server to start", "function":"kasten.i
Hi Team,We are using Kasten (6.5.5) and wanted to test its DR feature to backup & restore our stateful workloads between two clusters, to ensure we’re well prepared for infrastructure failures. We’re using AWS S3 bucket as our external storage, with a custom `path` in YAML manifest:kind: ProfileapiVersion: config.kio.kasten.io/v1alpha1metadata: name: s3 namespace: kasten-iospec: locationSpec: type: ObjectStore objectStore: name: kasten-backups-xxxx objectStoreType: S3 pathType: Directory path: "kasten/cluster1/backups"This ensures that all our backups are placed in `kasten/cluster1/backups` prefix in S3 and the DR backups in `kasten/cluster1/backups/<cluster-id>`. The same profile was deployed in the target cluster.However, when performing the DR process and installing k10restore job in the target cluster, we’ve got an error stating that there is no artifacts under specified prefix in S3. Upon further investigation, we’ve discovered, that restore
I’ve installed and configured the Veeam MS SQL agent on a MS SQL Server 2022 instance. During the DB backup setup, I can’t select object based repository or my SOBR. What is the best way to transition MS SQL backups to S3? Replication jobs only allow VMs. The Backup Copy and Copy Job only show local repositories.
Running VBR v12.0. Created a backup job. Ran the job and got an error so went back in and try to edit the job. I got the error below. First time, I encountered this error. The backup log just showed the same information. I have a similar job running in our “staging” VBR but not having any error. The backup job is a storage snapshot and does handle SQL transaction logging. I saw in the Veeam’s Forum the same error message but this was for a backup copy job. What do you think is happening here?
I've been using Veeam Agent for Windows for a bit, and have successfully used backups to restore individual files. I wanted to upgrade my NVME system drive to a larger one, so I figured I would try using the restore.I made sure my Windows 10 was up to date, updated Veeam to the latest version, created a new recovery ISO, and created a fresh backup. I then swapped in the new NVME and booted from a recovery USB. I stepped through the wizard, selected system volumes only (there is a data SSD I don’t need to restore); I did not use the Manual restore.After it copied everything to the new drive I rebooted, and then was stuck in a boot loop which ultimately ended in a recovery environment. Looking through the manual, there is a note about driver injection, so I tried again and disabled driver injection, still stuck in a loop. I put the original NVME back in and started looking for answers - any insight appreciated.
We're getting a fairly large number (~1K/week) of "OpenSSL SSLv3 large heartbeat response - possible ssl heartbleed attempt" IDS alerts and blocked connections from our Meraki firewall for ESXi-Veeam traffic.The alerts look like this:Time Type Source Network Destination Disposition Action Details Mar 25 2:59:25 IDS Alert <ESXi IP>:902 <network name> VeeamDRS Meraki Network OS Blocked SERVER-OTHER OpenSSL SSLv3 large heartbeat response - possible ssl heartbleed attempt Most of the alerts for OpenSSLv3, with a few for TLSv1.1 and TLSv1. The following table summarizes alerts over a 2-week period.Most prevalent threatsThreat Occurrences SERVER-OTHER OpenSSL SSLv3 large heartbeat response - possible ssl heartbleed attempt 1547 SERVER-OTHER OpenSSL SSLv3 large heartbeat response - possible ssl heartbleed attempt 324 SERVER-OTHER OpenSSL SSLv3 large heartbeat response - possible ssl heartbleed attempt 301 SERVER-OTHER
I have been having issues with the local file server/storage which is a Synology device running their latest up to date OS.I recently enabled SMB multichannel and Asyncronous read on the Synology. Unfortunately, my backups have started failing across multiple devices: 4/1/2024 12:32:10 PM :: Error: The network is busy. Asynchronous request operation has failed. [readsize = 4202496] [offset = 8585379840] Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{04776693-5fd2-4b58-8adb-2a31e1e3d68e}]. CHMOD mask: [255]. Agent failed to process method {DataTransfer.RestoreText} While I understand I can disable the feature and NOT have SMB multichannel on, it’s been great and beneficial. I’d much prefer I was able to support and take advantage here. Is this something I can address in some way? This is using the Veeam agent.
I encountered the above error when using a new Windows server. I'm certain that communication between servers is normal, and the ports are open. I've successfully added several servers of the same type without any error. And I've tried the following:Disabling the firewall and antivirus software. Adding a new account with administrator privileges. Using the IP address instead of the DNS name. Checking the registry or services to ensure they don't affect the relevant services. However, this issue still persists.My server is not within a domain, and this server is not a virtual machine
Hello Veeam Community,I am reaching out with a concern regarding our Veeam version 12.1, as we are consistently receiving malware detection alerts on our VMs. The notifications specifically indicate:Potential malware activity detected: Too many files have had their names changed since the last backup; ensure they were not encrypted by ransomware. Potential malware activity detected: *.ttt (TeslaCrypt 3.0): 40 instances. Potential malware activity detected: *..txt: 2 instances.I have conducted thorough scans on both the VM and the backup, and no malicious activity was found. Could you please provide insights or guidance on whether this is a matter of concern, and if there are additional steps I should take to address this issue?Your assistance in resolving this matter is highly appreciated. Thank you in advance for your support.
With the recent VMWare licensing consolidation and Broadcom moving to a subscription/core model, it has caused many SMBs to explore new options for a hypervisor. (such a shame.. pouring one out for my years of VMWare experience.) XCP-NG and ProxMox keep coming up in various communities. I personally have tested both and they perform really well. My only issue with them is that currently there is no native Veeam integration for the two platforms. Are there any plans for Veeam to support XCP-NG and/or ProxMox?
Un buen saludo buena gente. Tengo una consulta, actualmente me encuentro implementando un Protection Group con Windows Server. Dispongo de una red de backup (aislada de la de producción), y estoy presentando los servidores físicos por esta red de backup, el problema radica en que cuando ejecuto job se queda varado en los pasos iniciales, validando los logs se evidencia que se va por la red de producción e intenta comunicarse con la de backup evidentemente sin éxito La consulta es, ¿existe manera de configurar en Windows o en el agente que todo el trafico se vaya por la red de almacenamiento?
Hi,Anyone can help with this error from a physical server backup?“10:30:32 Calculating digests Error: Could not find file 'C:\Windows\TEMP\tmp171E.tmp'. Could not find file 'C:\Windows\TEMP\tmp171E.tmp'. “
Any can help to solve this error please?“2024/3/27 11:04:52 :: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. “It is from a backup job of a physical server.
Dees Latest Version (Version-12.1) of Veeam Backup and Replication supports backup and recovery of IBM Spectrum Scale GPFS file system. Please guide.
Hi all,i was testing and studying the FileServer Backup. Reading the guide from “Top to bottom” :-) under Requirements and Limitations for File Shares i see"To support the VSS for SMB File Shares feature, make sure that requirements listed in this Veeam KB article 3099 are met."Link at the kb https://www.veeam.com/kb3099Under Requirements of that Kb it says "The Veeam Backup Server and the Windows File Server hosting the SMB Share must be joined to the same Active Directory domain."? Is this real? I cannot use vss on fileserver that are not in the domain of the VBR Server?The guide is for the V12Thanks for helps.
We have Kasten K10 on installed via operator on multiple clusters. All of the K10 instances seem to have excessive amounts of helm revision when viewed with helm history k10 Is this normal behavior? We seem to be getting ~200 revisions per hour.
Hi Community,i would like to give a suggestion for maybe a future release.When moving a backup to another repository, the job occupies all free task asap. Other jobs on that server will be delayed until the Move-Jop is finished.I suggest a dialog where one can limit the tasks the Move-Job is using, so the normal backup routine is not on full hold.What are your thoughts on this?
Already have an account? Login
Enter your username or 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.
