Solved

Hi, I would like to upgrade our cluster to 1.26. But getting following messages on aggregatedapis-svc: 1 warnings.go:70] snapshot.storage.k8s.io/v1beta1 VolumeSnapshot is deprecated; use snapshot.storage.k8s.io/v1 VolumeSnapshot Upgrade K10 to 6.0.12 with helm charts, but still getting this. Does K10 support 1.26? If so, what is going wrong here? Regards

Hello guys,One of my customer has encounter the following error message in a backup job.I never saw this message before. The Veeam version is 11 last patch.It’s a linux repository.I asked to my customer to open a support case, but in parallel maybe one of you has already meet this one ?!

Ok, I had a test server which I used to test out Windows Agent backups.I’ve now built a more robust server to handle veeam (community edition as we only have a few servers), when I try to backup the same server, I get:I’ve removed the backup jobs, and uninstalled the agent both using the old server and manually going into Add/Remove programs, yet the same problem exists. I’ve also added the registry key:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication AgentDiscoveryIgnoreOwnership DWORD=1Still no joy.  When I go into the registry editor on the machine in question, I can see why Veeam is having a problem.  The values in BackupServerIPAddress, JobSettings, and VBRServerName are all pointing to the wrong server. I’m loathed to start deleting this key.  What do I do to ensure this server I wish to backup now has the correct agent installed?RegardsIan

HI Community, I am currently using Veaam v12 B&R community edition.I have tried to add a service provider for ekco.I have followed steps from https://www.ek.co/publications/using-veeam-cloud-connect/Once I add veeam.cloudhelix.io and the username and password I get the below error.Is the issue down to the fact I am on community edition V12 or is it an issue from ekco’s side?(I have already logged a ticket with ekco support to see what their response will be) 

My question is, if we are excluding SQL data volumes from the original backup job, can we still do full SQL backups and transaction logs using application-aware processing?For some background, in our current state my team is backing up our Windows SQL VMs using a Backup job, then use a Backup Copy job to get those offsite. Since the team has historically ran SQL Agent jobs to do daily full and hourly log backups for each DB they decided to exclude any volumes storing SQL data from the Veeam Backup job. I see the reasoning and I suppose this works, but I’d like to shift to including Veeam on SQL backups so we can easily get those offsite using the existing backup copy jobs.Finally, a sort of related question, if we can use Veeam and the SQL agent jobs in tandem, which one should truncate those? In my testing I’ve had to set the SQL Agent job to copy only mode for things to work, but I feel like setting Veeam to copy only mode should work as well, but I must be missing something since I

Hello to all,As I configure a testing Job with Multiple VMs with the same OS, I can see that there is no difference in the deduplication rate in Report when I run the VM itself alone or in the Group.One more point to ask:The VMs in the Backup Copy Job are all started at the same time when the job starts.Is this how it should be or they need to be run one at a time?

Hello,I am using kasten-io with an S3 bucket with MinIO. For a long time I have wanted to view the backups and see if they are actually being saved in the S3 bucket.Is there a way to see the differential of backups that I have in the mini?In the Kasten-io dashboard, is there a way to see what restore point exists to import it to the destination? Thanks in advance.

I’m very new to Veeam. We use VMware vSphere. I need to be able to backup an entire VM, and be able to restore just individual files from that backup. I thought that doing a “VMware Backup” type of job, with “Guest File Processing” enabled would allow me to do that (i.e., restore just one file from drive E:, as an example). But when I try “Restore Guest Files” on that VM, , I get “Unable to mount disk: unsupported disk type” when it goes to Browse. Have I totally misunderstood what type of backup job I need to be doing, to be able to do an individual file restore of a Windows VM? What type of backup do I need to be doing then, to accomplish what I need? This type of backup looks like I can only restore the entire VM, like a bare metal recovery. Which is good, and I might need that, but I definitely need to be able to restore individual files. Do I need to make a backup job of type “Windows Computer”? I won’t need to push the Agent, because the VM is always connected.Sorry for the newb

my goal isI use veeam to back up my vmware vm machine to a NAS, and then I back up the backup files from nas to aws s3. Then I can directly read the files from s3 and restore the vm machine in aws.But I am currently encountering a problem. The backup from veeam to nas and then from nas to aws s3 goes smoothly, but my veeam cannot read the files backed up by nas in aws s3. Please tell me how to set it correctly.

I am currently developing a DR solution.  I currently have the backup on the source side exporting snapshots.  On the destination side, I have an import job configured to restore workloads with exclusions of certain objects.Issue:I run the the import job for the 1st time today (within 24 hour clock). K10 imports the snapshot from the external S3 target. Then restores the workloadsAfter some testing, I wipe out all the restored workloads, including the namespace to reset the destination for another test.When I re-run the import job:K10 imports the restore point The job marks as complete Without restoring any workloads Question:How can I re-run the import job multiple times to fully test my DR solution?

Hello,I have an issue with my Kasten Multi-Cluster setup recently. When I try to add a secondary cluster, I have this error message : ERROR: API server connection failed (cluster_name: lab)  -> ServiceAccount credentials appear to be invalid    -> the server has asked for the client to provide credentials (post selfsubjectaccessreviews.authorization.k8s.io)  I able to see the cluster in the multi-cluster interface but the secondary cluster is in error 500  I checked logs in pod logging-svc and I noted this line : {"File"=>"kasten.io/k10/kio/multicluster/multicluster_proxy.go", "Function"=>"kasten.io/k10/kio/multicluster.serveHTTPHelper", "Level"=>"error", "Line"=>120, "Message"=>"Could not authenticate request for secondary cluster", "Time"=>"2023-11-13T10:52:24.666972037Z", "clusterName"=>"lab", "cluster_name"=>"0567e4fd-4c4f-45df-ac5c-b18b6abf9385", "error"=>{"message"=>"Cluster ID not found", "function"=>"kasten.io/k10/kio/multicluster.Authenti

Hello,We had 13 Backup Jobs that were all started in the same time period from 21:00 to 22:00.VBR server had 32 GB of RAM and 10 cores. It was a VM.All Backup Jobs were with single VM inside of it.Was this good approach or it was too much for our VBR Server to handle.We didn’t have any off-host Proxies and VBR Server and 60% of VMs were on the same Hyper-V host.It was acting then as only proxy for those jobs as I can assume.What would be the better approach on this?I’m still trying to grasp Veeam with his technologies as best I can..

I’m using Veeam Community (free) license, and I want to use swapped external hard drives as offsite backup for my locally hosted repository.  But when I try to create a pruning Backup Copy job, it keeps saying I need Backup and Replication Enterprise Plus.  The descriptions I’ve read make it sound easy, but they’re all vague about what sort of license is required.  It’s like they are conflating “community” as a forum and as a license?  I absolutely cannot upgrade to a paid license.What am I missing?

Me again with new topic 😁At the moment our VBR Server is located on the Hyper-V Host where are also the 50% of VMs that we are backing up. Without Using Off-Host proxies I can guess that all load will come to Hyper-V host which is hosting VMs and VBR also.I guess that data movers from source VM and VBR are run on the Hyper-V host itself.What would be the best practice for placement of VBR?Is it good idea then to isolate it from the VMs that we are backing up or?I can host it on some Hyper-V Host which doesn’t have productive VMs or anyAlso then our off-host backup proxy should be physical machine or somewhere where we also dont have anything?

Hello Forum,I have question about few things so that I make the change as smooth as possible.The plan is to create everything from scratch because our current configuration is really awful and time for change has come.  Current Situation is like this:VBR V11 on Hyper-V VM Subscription: Enterprise Plus Instances: 20 (13 used) Inventory: 1 Hyper-V Cluster  2 Standalone Hosts Now I need to remove everything from this server and to transfer the license to the new one Questions:How to transfer the license? How to properly remove Inventory so that I don’t have problem when adding it to a new V12 VBR server? I know that few folks had problems when attempting to add the hosts to new VBR, something stuck on the old VBR etc. I will not do a configuration backup because I want everything from scratch. Please feel free to write any other recommendations that I need to take care off.I did it one year ago but I would need the help from Veeam Legends to do it the propper way this time 😁

What does Orphaned and Imported indicate next to Disk in Veeam Backup and Replication under Home tab? 

Hello. The question concerns the display of repository capacity in the Veeam user interface:In the EMC DD console, the capacity is displayed in TiB and is equal to 166.7 TiB. In the Veeam UI, after adding EMC DD as a repository, the same capacity is displayed, but with the TB label.If the size of repository is displayed in TB, then it should be approximately 182.5 TB.Is this a Veeam UI error?  

Hello everyone.Am not sure if this is the write place to ask this..I forgot the encryption password i have set for my veeam backups, and i want to access the veeamBackup database to get the encrypted password and decrypt it as the online manual says. But as soon as i login to the database with sql server studio with the windows authentication settings, the Veeambackup is not accessible. The sa user is not active. This manual here ‘How to install Veeam Backup and Replication 11 Community Edition with a dedicated SQL Server | Veeam Community Resource Hub’ is exactly the same as my setup, but as soon as i get to the part there i am suppose to open the database VeeamBackup to see the tables etc, i get an error ‘The database VeeamBackup is not accessible’. Also added a screenshot below to show it.Any help on what am i doing wrong?Thank you  

hi everyone I tryd install kasten in openshift 4.11(kubernetes 1.24.6) using helmKasten version is 6.0.9customer environment is airgapinstall option is ================helm install k10 k10-4.5.14.tgz --namespace kasten-io \--set scc.create=true \                                                                                                            --set route.enabled=true \                                                                                                       --set route.tls.enabled=true \                                   --set auth.openshift.enabled=true \                               --set auth.openshift.serviceAccount=k10-dex-sa \--set auth.openshift.clientSecret=${DEX_TOKEN} \                           --set auth.openshift.dashboardURL=https://k10-route-kasten-io.${APPS_BASE_DOMAIN}/k10/ \  --set auth.openshift.openshiftURL=https://${API_BASE_DOMAIN}:6443 \                       --set auth.openshift.insecureCA=true \                                            

hello,I would like to know, can we use backup copy to SOBR repository as a target ? Thank You

Hello, Thanks,My question is about Veeam catching memory errors during the backup itself.Sure, sometimes ECC can catch that.For example, Let’s say Veeam:Reads a sector from disk into memory. Whilst that sector is in memory, the memory is corrupted. Veeam writes that corrupted sector to the backup file.A Health check would not catch that.Does Veeam have a way to catch that, by re-reading the source sector again or some other mechanism?Thanks much,David   

Hello,  I try to install Veeam Agent for Linux on my debian 11but i have two errors that involve failure of Veeam Agent for linux installation 20/09/2023 09:41:17 Failed [172.16.0.18] Failed to install veeam_6.0.0.1060_amd64.deb and blksnap_6.0.0.1060_all.deb packages: E: Impossible de trouver le paquet linux-headers-5.10.0-18-amd64 E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » Failed to invoke rpc command  0:00:14 20/09/2023 09:41:32 Failed [172.16.0.18] Failed to install Veeam Agent for Linux: E: Impossible de trouver le paquet linux-headers-5.10.0-18-amd64 E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » E: Impossible de trouver de paquet correspondant à l'expression rationnelle « linux-headers-5.10.0-18-amd64 » Failed to invoke rpc command   my config

Hello, I will need to migrate my Veeam Backup & Replication (v12) installation to a new server because my current server is 2012 R2 and it’s not supported anymore as you know.My new server (virtual) will be a Windows 2016 and I want to migrate my Veeam B&R install the proper way in order to avoid loosing any “block change tracking” or things like that and have my backups and replications running the same as before on the new server because I have around 25 TB of data to backup and replicate and if Veeam needs to re-read the entire volume (instead of “change blocks”) that would be 48+ hours lost! 😵 Thank you!!

So I’m am basically a day or two away from taking the time and going through and disabling the backup cache across all of my customers, it causes way too many problems. But thought I’d try asking here as a last resort since Veeam’s support seems useless as usual and my R&D forum posts aren’t getting any responses. I have had various cache related issues, especially since the ridiculously buggy V12 update, but here this past week it’s been especially bad. I have about 20 computers, that I know of right now, which are failing to upload the backup cache to the VCC server. As such these computers have not been backing up. At first I thought maybe they just needed some time to catch up or something, but it’s been over a week now and they’re not even modifying the files in the VCC repository. (Side note, yes, I did go look at the files, because it’s useful, even though Veeam says there’s no reason I should ever need to look at the files.)Seems there’s numerous different errors and behavi

Per opportuna conoscenza di tutti.È stata riscontrata una vulnerabilità in Veeam ONE che permette a utenti non autorizzati di ottenere informazioni sul database SQL server a cui è collegato .  Versioni colpite: Veeam ONE 11, 11a, 12Severità: CriticaQui trovate l'articolo completo.Quindi.... Aggiornate