Solved

Hello!I’m currently running VBR CE v11.0.0 on Windows Server 2012 R2.  We are only backing up a total of 4 VMs.My initial task was to move a couple of the backups to a new backup repository.  But, the ‘move’ functionality apparently isn’t available in v11.  Rather than try to upgrade our current instance of Veeam, I’d like to just install a the newest version of VBR CE on a new instance of Windows Server.My question is: Keeping in mind the difference in versions, should I be able to take a backup of the DB config and import it to the new Veeam install as suggested here?  If the difference in versions is an issue, what’s the best way forward?Once I have a new instance up-and-running, the ability to move the backups to new repositories should be available, I believe.Please let me know if I can provide additional information.Thanks!

Does anyone know when is the new immutable installable ISO release date? I’m currently waiting for it to deploy our new VHR.

Per la maggior parte della mia vita lavorativa sono stato un end user. E facevo un po’ di tutto, reti, gigolò, sistemi, cabaret, backup, imitazioni, sicurezza.Dal 2011 nell’azienda dove lavoravo abbiamo preso l’allora stravolgente firewall PaloAltoNetworks, e solo tre anni dopo Veeam. Ho sempre pensato che sicurezza e backup fossero molto vicini come topic: li avrei messi sotto il reparto “Protezione dei dati”.Nel 2016 cambiai azienda e per fortuna c’erano sia PAN sia Veeam, e la mia idea si è rafforzata anche perché sappiamo come si è evoluta la storia di sicurezza e backup. Nel 2019 poco prima di andare via fui uno dei primi clienti italiani a implementare Cortex XDR di PAN (già dal 2018 avevo messo in piedi quello che allora si chiamava TRAPS, sistema innovativo di protezione dei client e non solo).Oggi finalmente si celebra ufficialmente il matrimoniohttps://www.veeam.com/company/press-release/veeam-announces-a-new-integration-with-palo-alto-networks-to-streamline-security-operatio

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? 

Hello,I have a very old running setup of ESXI 5.0.0 and ESXI 5.1.0 Hosts with 10 VMs (Win Server 2008R2, Suse enterprise 12, Win Server 2016 and windows 7 Pro.). The setup also includes an Equallogic storage.Is it possible to migrate the existing VMs to a new Host server with ESXI 8.0 ? 

Hello Kasten has been successfully creating backups for volumes and configs but recently export jobs failing for all policies with error message “client rate limiter Wait returned an error: context deadline exceeded": cause: message: "client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline" file: github.com/kanisterio/kanister@v0.0.0-20240828182737-b6d930f12c93/pkg/kube/pod.go function: github.com/kanisterio/kanister/pkg/kube.WaitForPodReady linenumber: 412 message: Pod did not transition into running state. Timeout:15m0s Namespace:kasten-io, Name:copy-vol-data-7d5hj file: github.com/kanisterio/kanister@v0.0.0-20240828182737-b6d930f12c93/pkg/kube/pod_controller.go function: github.com/kanisterio/kani

If you set your S3 repos gateway server to direct mode, I would have expected the entity getting in touch with backup data to do the offload.In direct to object jobs it works just like that. Proxy will do the upload with a primary job. Repo will do the upload with a backup copy job. But with SOBR offloading to capacity tier it seems to be the VBR server doing the offload for all S3 buckets in direct mode.Can someone confirm this observation?Would be another reason to always have GW servers specified for each and every S3 repo.

Hi All, Can we create like backup copy from Kasten exported data?I know we can set only one export location to the snapshot action? But what if the requirements we need more than one copy on different storage for the application backup? Also, how can we delete the local snapshot created by Kasten on OCS CSI storage for example and how can we see this data from openshift side not Kasten dashboard?  Thank you 

I did a research for consistent PostgreSQL backups with Kasten K10 and found:https://docs.kasten.io/latest/kanister/postgresql/install_app_cons.htmlApplication Consistent PostgreSQL BackupYou described there to use a Kanister pre-hook (“pg_start_backup”) and post-hook (“pg_stop_backup”). Afaik, that alone will not create a consistent backup. You also need any generated archived WAL file between. Archiving must be enabled (archive_mode=on), archived WAL files must be backuped too, therefore. I did not find anything about how to backup archived WAL files. How will you handle them? Thanks, Markus

I have a backup failure showing error: Failed to open VDDK disk [[vsanDatastore] be123456677777777/vm1vmdk] ( is read-only mode - [true] )Logon attempt with parameters [VC/ESX: [dc1.nm.org];Port: 443;Login: [;VMX Spec: [moref=vm-1104];Snapshot mor: [snapshot-253990;Transports: [nbd];Read Only: [true]] failed because of the following errors:Failed to open disk for read.Failed to upload disk 'vddkConnSpec>'Agent failed to process method {DataTransfer.SyncDisk}. It was working only when selecting nbdssl transport mode . i know it is using network over ssl .Can someone advise why it is working only nbdssl and what is it doing in the background?

We would like to ensure that all backups from October 1, 2024, through October 4, 2024, are retained without expiring and remain accessible throughout the year if needed.. How can we achieve this?

I got a Problem when I install Katen.I install Kasten instance by Kaster(Free) operator on the Openshift 4.12.31.Then I got this issue. ↓ I describe the pod and got this events.↓ This is my k10 instance yaml This is my k10 service status  What can I do to resolve this problem...?HELPPPPPPPPPPPP~!

Hi, I am using Veeam backup and replication 12 (free edition).I am trying to import a .vbk encrypted file, which is stored on a remote NAS (QNAP).I am accessing this NAS through SMB protocol.I wrote the (correct) encryption key, and after I get this error:Failed to import backup Error: access denied, failed to open storage for read access. Storage [filename.vbk] I also tried to configure access permission to that repository (NAS) with "everyone" allowed, but I got same error. Any suggestion? Thank you.Full error (from file Util.BackgroundOperation.log) is [25.09.2024 09:46:51.335] <14> Error                  [AP] (db9320fe) error: Accesso negato[25.09.2024 09:46:51.335] <14> Error          Failed to open file [\\nas-xxx.domain.com\Veeam\serverD2020-10-04T082748_CB05.vbk] in readonly mode.[25.09.2024 09:46:51.335] <14> Error          --tr:Error code: 0x00000005[25.09.2024 09:46:51.335] <14> Error          --tr:Failed to detect version of the storage [\\nas-xxx.do

We have multiple backup servers and run a configuration backup on them daily. I’m looking for suggestions on how to keep these config backups safe ?I originally had a script that emailed these to a mailbox to keep “air-gapped”, but the size of the file became too large.  Perhaps there’s a way of reducing these, but I suspect the size will creep up again making them too big. Currently the config backup for Site A goes to Site B and visa versa, but i want something better. Yes, I  could have a scheduled task to copy them elsewhere. Any other thoughts / suggestions. TIA 

We are using Veeam Backup & Replication(V12)  to take backup of Virtual Machines with Application-aware processing.Some of the virtual machines have SQL Server Databases.We take backup to Disk and Tape.Is it possible to restore SQL Server Database directly from Tape?If yesIs it possible to restore to different virtual machine? 

We have initiated vm instant recovery and migrated to production . The issue is that we have completed the Migration from vCenter instead of the Veeam console, we just wanted to confirm that we are able to hit stop publishing in the Veeam console without impacting the restored and migrated VM.Please advise.

A little while ago we purchased an additional SAS storage enclosure for our existing Linux Hardened Repository server. Due to the number of disks, and also because we only have a Host Bus Adaptor rather than a hardware RAID card, we attempted to set this up as 5 md-raid6 arrays of 12 drives each, combined into a single volume using LVM.While initially this seemed to be working, after a little bit we have been getting tons of I/O errors. We exhausted all possible troubleshooting steps in collaboration with Veeam support, but it just seems like this is a wrong setup for a Veeam repository.I recently discovered the concept of “XFS on ZFS”, i.e. the idea of being able to set up a ZFS ZPOOL - which would replace the md-raid and LVM parts mentioned above - and then format this with the XFS filesystem. Apparently this is not a new idea either, as I found it was mentioned briefly in a Veeam webinar at https://www.veeam.com/resources/videos/build-secure-repositories-17144.html?rwty.Does anyone

Hi, I notice that when I backup the same machine with different jobs (each job contains the same machine) via Agent that B&R stores the backup copies under different directories and hence multiple copies of that machines backup up are saved.  Is there a way to get around this so only one copy is saved? Thanks

Hi all … greetingsI am deployed an Ubuntu Immutable Repo and its utilization is high. Meanwhile I have a spare QNAP NAS TVS-h1688X, I am thinking if I can use it to expand the immutable repo capacity.Having checked the spec, the QNAP NAS support iSCSI and CIFS, might I use either protocol connect to the Immutable Repo for expansion? Will the immutability maintained because it is controlled at the OS level? Alternatively, leverage of QuObjects make the NAS become S3 compatible storage connecting to the VM host, and add both storage into SOBR, is workable too?

Hello Team,I’m receiving error trying to update from K10 7.0.7 to 7.0.8. Environment k8s and the storage CSI used is Longhorn.The StorageClass is already true to allowExpansion.So anyone can help?

Please assist with errorProcessing  Error: Unhandled exception was thrown during licensing process    

Need some clarification. On this scenario i have a windows server that run an app and i want to backup the whole server (in case we ever need to restore it i can just dump it on a vm) but i want to make this whole backup daily and immutable. For what i understand there is a set number of days for immutability but not sure how does this work for daily backups.  Whats the correct settings to do on this case?  Are these backups like whole backup every day or its incremental only? Thanks.

Hey,I have configured Linux Rocky 8.10 with kernel 4.18.0-533.16.1.e18_10.x86_64 to the Hardened Repo. However, I encountered an issue when trying to add this server to Veeam. The problem is with the Installer Service, and I receive either an exit code 1 or a timeout when connecting to Rocky via SSH. I have already turned off all firewalls and allowed all traffic. My question is whether version 8.10 is supported.I can connect to the repository via SSH using the command line from Veeam server. Veeam version 12.2.0.334 Here gave info that Rocky 8  is supported..https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_limitations.html?ver=120

I asked this in the Veeam forums, I figure I ask here as well: I have Veeam B&R server1, with a SOBR repo, the capacity extend going to Azure. i have a Veeam B&R server 2, with a SOBR repo, with the capacity tier going to Wasabi.What is the best way of getting the backups going to Azure on Veeam server 1 to Wasabi on Veeam server 2? Goal is to eventually decommission server 1.I can recreate the backup and backup copy jobs on server 2, so then point forward, it will use Wasabi. But how will I get the existing historical backups in Azure on server 1 to Wasabi on Veeam server 2?

GuysI am migrating my VMs from an old cluster to a new one. NO problem so far - 7 out of 8 VMs moved. Veeam continues to back them up. Great stuff.The last one has a large VHDX drive - 4TbWhat will happen when the backup job tries to back that up whilst Hyper-V manager is moving the machine? With the old (1Gb) NICs in the source cluster this might take a while to copy (7h ish).Does the backup job just fail (becasue the machine won’t quiesce, or perhaps because there is already a snapshot created by the move process) or will it get stuck in some horrible sort of a loop and eat up all the storage on the cluster with checkpoint files?I ask because, back in the day (when I was new to Veeam), I did try to backup a machine that was the target of DFS-R and the results weren’t pretty. I realise this is a different scenario but I just want to be sure! B.