Solved

Hello, We have K10 6.5 running with CSI storage provided by Dell Isilon CSI drivers. We have 4 storageClasses with this driver (csi-isilon.dellemc.com), each using different Isilon clusters and path. To match this, we have 4 VolumeSnapshotClasses with the same driver, but with different parameters. Using the Snapshot option from K8s (Openshift) is working ok.Kasten is not using the correct VolumeSnapShotClass for snpashotting the PersistentVolumes created on each storageClass.Here I provide 2 storageClasses and VolumeSnapshotClasses : StorageClass “isilon-infra”allowVolumeExpansion: trueapiVersion: storage.k8s.io/v1kind: StorageClassmetadata: annotations: k10.kasten.io/revalidated-at: '{"Status":"Failed","LastUpdateTime":"2024-01-16T16:11:47Z","Errors":["Failed to validate the storage class within the time period."]}' creationTimestamp: "2024-01-16T13:46:33Z" labels: vs.ch/dellcsi: vrai name: isilon-infra resourceVersion: "1207671684" uid: 7337136e-7f93-4bf5-ba94-9d888

The Veeam backup server operates on a 1-gigabit network, while the VMware proxy server and the data domain storage are on 10-gigabit networks. Despite this, the backup speed is consistently reaching only 270 to 300 Mb/s per second. Is there something overlooked in this setup? Additionally, would incorporating a WAN accelerator result in any performance improvements for the copy job over the WAN link?

Hi team:I have a question about the backup to tape:I have a job that backs up vm to tape which works, however when the tape is full, it asks for a new one to continue and continues without problems. The issue happens when doing a restore since it asks for 2 tapes and my unit has 1 tape. If I have only one drive, how can I make the job detect that the tape is almost full and request a new one? Regards,

Hi Team,We’re using Kasten installed in our Kubernetes cluster via Helm Chart (version 6.5.1)We’re using Blueprints to back up applications' data either by spinning up Kanister pods (KubeTask function) or using KubeExec and targeting the kanister-sidecar container (if the data cannot be backed up remotely, e.g., using pgdump). The sidecar injection is done automatically by mutating admission webhook.This works fine until we need to back up a service such as minio. There isn’t a built-in Kanister image for minio in https://github.com/orgs/kanisterio/packages?repo_name=kanister which we could use; we can’t solely use the minio image (for remote `mc cp` between blueprint pod and target minio) since it’s lacking kando/restic binaries for uploading the backup to external storage. We can’t use the sidecar injection either because it’s lacking (to our surprise) tools such as tar, scp or rsync.We would like to know if it’s possible to change the default image (gcr.io/kasten-images/kanister-too

After upgrading from V5 to V6 FREE Agent, my backup speeds significantly dropped. From 232 MB/s down to 15 MB/s. V5V6 

I’m using Veeam Agent 6 (free).I had to do a fresh install of my computer and did a file level restore to get my most important files back. Afterwards, I started a new backup chain.I still have the backup from my old computer, which is 1 x .vbk  and 22 x .vib files. I’d like to keep just the latest restore point, synthetically merge it into a full backup (.vbk) and discard the old restore points. This will likely save 40 % of the space that the old chain currently occupies.I know that Veeam Agent can do that with an active backup job and VBR can import old backups and I can manually trigger it. I hope I can do it with Veeam Agent and an old backup, too, somehow. How?

Hi all,A user formatted his laptop as revenge to his company, but a valid endpoint backup was taken using Endpoint agent backup for workstation to a dedicated S3 object storage bucket.So we’re out of meta-data but should have 7 valid backup points in Object Storage. Now I want to get FLR from this backup with minimum effort, so I was thinking of adding the Repo in an Existing VBR 12.1 and import the backups from there.Attaching the bucket: no problemSyncing the repo: no problemImporting backups from the bucket: problem :-( I get the message: Failed to synchronize Object Storage <Object Name> Folder does not exist.Anybody tried this before ? Another path could be to install the Endpoint agent on a donor machine and try to connect from to the repo and perform restores… 

hello everyone,I have already made a sizing of tape consumption using https://calculator.veeam.com/vbr/ & https://rps.dewin.me/rpc/ withTotal Data :109 TB & backup policy daily : 6, weekly : 4, Monthly: 12so i want to know that, how many tape cartridges LTO9 do i need for a month ?is it right if i use formulain the first month :Full (120/18 = 7) + Incremental (30/18=2) + 3 weeks (180/19=10) + 1 month(60/18=3) = 22 Tape Catridges LTO 9in the second month :Full (120/18 = 7) + Incremental (30/18=2) + 3 weeks (180/19=10) + 1 month(60/18=3) = 22 Tape Catridges LTO 9 so for 2 month I need 44 Tape catridges LTO 9 

Hi team:I have a question about the next:I have a windows server that contains certain files that I want to backup to veeam.I have already done it with the veeam agent and I have no problems. However, I want to copy the same files to tape.I have read the information about File - to - tape option but how do I apply it without in my case I have a single tape drive which is already backing up VMs.Regards, 

I’ve read agent based backups ae limited to maximum of 999 restore points per job. Does NAS file share backup have a maximum number ?

Hi Everyone, I was hoping for some advice on an issue I’ve found after upgrading to V6 of Veeam Agent for Windows free edition on Win 10 22H2.I’m not sure why but until I upgraded from V5 to V6 my backups were running fine every evening and completing without any issues, since the upgrade to V6 the backup starts but either sits at 0% 14% or 18% and regardless of how long the PC is left running it never seems to get past this point. I’ve disabled throttling in the menus in the hope this was slowing the backups down but its had no effect on them.The total “full backup” size is around 1Tb split across a Sata M.2 boot drive and a regular old 1Tb spinning disk, I’m running Kaspersky AV for reference. The only change I’ve made is the upgrade from 5-6 is is possible to downgrade back to 5 to test if this is a veeam issue on the PC or will that force a new backup ?Any advice would be appreciated as I’m at a loss as to why the backups have just started taking so long.*Edit* I’d also like to men

I have a 5 TB file share on Windows. Should I back this up using agent backup or File Share backup? I  have a backup copy job to send backups offsite. Currently doing file share backup with retention time set to 4 years. I think the agent based backup would take up more repo disk space (multiple vbk files)?

I am trying to do agent based backup of a Windows file share cluster. However when the job is set as "Failover cluster" job mode I can only select the entire volume to backup.I want to select particular folders on the shared drive to backup. Is this possible ? 

I did an agent based backup of a windows computer and the “servers” license count increased by 1 instance. I deleted the backup data but it the server still shows up in the license report.How do I release it ?

Please help with adding a Hyper-V host. Veeam 11. New Hyper-V Server > Credentials: Added Domain User to Administrators Group on Hyper-V Host. Veeam B&R and Hyper-V Host on same domain. Window Firewall Off:Windows Firewall On: RANT:Hours in, this is frustrating that Veeam doesn’t nip this in the bud and does not rely on MS technology (Ports, WMI...etc) to install, and shifts responsibility onto the customer and offers unhelpful dialog boxes and similar push back in forums. 

We have our main prometheus deployment and would like to use that instance also for the kasten needs.I’ve seen in the chart that kasten allows for the use of an external prometheus and grafana.Are there any specific configurations to do for kasten, are there anu compatibility matrixes to be aware of?Is the external prometheus supported (we have kasten support active), will kasten loose any feature by using the external prometheus?Thanks

Are there any plans for a Meetup this year? Virtual or In-Person Cheers Mark

Hello,With Veeam Backup & Replication Community Edition 11, On one of the backup jobs, when it starts, I encounter the following error:Failed to perform health check Error: Agent: Failed to process method {NasMaster.TransformMeta}: Unexpected meta file size 348160. Expected size: 356352. The source is an NFS share stored on a NetApp storage, and the destination is a Synology NAS. I have other jobs that use the same sources and the same destination, and they do not encounter this error.The job is responsible for backing up user files such as Office documents, PDFs, etc. When it runs, no files are open or currently being modified.I tried performing a job check as instructed on this page https://helpcenter.veeam.com/archive/backup/110/vsphere/health_check_nas_backup.html, but I encounter the same error. Thank's for advance.Philippe

Has anyone experienced this issue after performing the Veeam v12.1 upgrade? Unable to connect to guest OS for guest processing. Cannot find Linux guest credentials.  Our Veeam environment is configured to utilize vSphere backup tags (which includes both Windows and Linux VMs).After the upgrade to v12.1 our backup jobs that included Linux VMs didn’t backup.We have opened up a support call, and in the meantime have a work around.  If we would specify each Linux VM along with the backup tags within the backup job, the Linux VM does backup.

I have 6 months of daily restore points, a monthly VBK and daily VIBs for each month. I have the backup job configured to keep 180 days of backups. However, when I do an FLR, it only displays from 11/1/23 forward, just 60 restore points. I feel like the repository needs to be rescanned but I can't see how to do that. (I use Veeam B&R for our corporate backup system, so I am familiar with this, but I don't see how to do it in the free version). I also tried right-clicking the actual VBK or VIB I want to use and then "Open", but it just opens the FLR window, showing only the last 60 restore points.This behavior exists on multiple PCs where I use Veeam Agent for Windows.  This product isn’t much use if I can’t restore my data.I opened a case (#07068715) over a week ago and it was auto-closed because no one was available to look at it.Does anyone know how I can access my restore points? Thanks.

Good day,I have been enthusiastically using "Veeam Agent for Microsoft Windows" for some time.Now I have the problem that when I have activated my new Premium VPN from https://hide.me "Veeam Agent for Microsoft Windows FREE" unfortunately aborts with an error message when creating a backup!What exactly do I have to set or allow in the VPN app so that the backup still work with VPN enabled?My system data & backup-media:-Windows 11 Pro 23H2-Veeam Agent for Microsoft Windows 6.1.0.349 - Free Edition-Backup-medium: External 2.5-inch hard disk Many thanks for any helpful answers! 

In primul rand salut si La multi ani! Avem un mediu de Veeam Backup for Microsoft 365 exclusiv pentru backup de Exchange. Repository-urile au retentie de 32 de zile. Dupa cum stiti, cand ruleaza retentia nu se elibereaza de pe disc spatiul alocat deja pentru repository. Astfel, dupa ce trec 32 de zile din 2024, folderul “2023” de pe discul repository ar trebui sa nu mai contina date deloc, dar va continua sa ocupe pe disc spatiul alocat la momentul actual. Intrebarea mea este cum pot elibera de pe disc spatiul acela, alocat deja pentru 2023? Stiu ca pot face shrink la repository.adb dar am nevoie temporar de spatiu liber pe disc inca odata cat repository-ul, plus ca trebuie sa fac asta cu serviciile de Veeam oprite (adica backup-ul nu va rula in acel timp). Din experientele anterioare, dureaza undeva la 60 de ore. Pot sterge folderul “2023” din repository dupa 32 de zile? Sunt alte variante?  Multumesc, Dragos

Hey there. I use Community edition for my home lab and photo archive backup proposals. VBR is installed on my PC, it was added to Veeam as a File Server, some folders were added to the job, and everything was fine until I added these folders to sync with my Nextcloud (real files are always on device).Now I faced this error:08.01.2024 22:43:43 :: Unable to backup \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12\Pict\Filmscan. Incorrect function.Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy12\Pict\Filmscan].There are job logs from C:\ProgramData\Veeam\Backup.Does anybody knows, how to resolve it? 

Hello Veeam Gods,Newbie here, looking for some advice on system design… I’m hoping I’m in the right place, but let me know if I’m not.Here’s the stack:DC1:3x ESXi Physical Hosts1x VCenter Physical Server1x Win22 100TB StorageNon-Prod Nimble System with 40TB storageAll on 25GB backbone LINK: 100gb fiber connection DC1 --> DC2. Separate buildings, power, generators, WAN etc. DC2:3x ESXi Physical Hosts (same spec as DC1)1x Veeam Physical Server with VBR + Explorers removed1x 600TB Ubuntu hardened Immutable StorageAll on 25GB backbone WAN:2 x 2GB redundant WAN connections (1 into each site but HA across the two, redundant firewalls too)Wasabi Buckets for Offsite S3 storage. The Plan (that I’d like guidance on):Run Production in DC1Use CDP to DC2 for near-real-time failoverBackup Production in DC1 to the 100TB Storage in DC1 (store short term backups - sub hourly)Copy Job to DC2 600TB Ubuntu Immutable (store short and longer term backups - sub hourly, hourly, daily, weekly, monthly)Copy

Dear,We have setup Kasten with OIDC integration with our Keycloak instance.We can login in Kasten with our keycloak credentials, however, given that the Access Token has a lifetime of 5 minutes we are loged out from kasten after 5 minutes, like if the Refresh Token is not used. We have configured Kasten like this:data:  provider-url: {{ $providerUrl | b64enc }}  redirect-url: {{ $clusterUrlTrimmed | b64enc }}  logout-url:   {{ $logoutUrl   | b64enc }}  client-id:    {{ .Values.identityProvider.clientID | b64enc }}  client-secret: {{ .Values.identityProvider.clientSecret | b64enc }}  scopes: {{ .Values.identityProvider.scopes | b64enc }}  usernameClaim: {{ .Values.identityProvider.usernameClaim | b64enc }}  usernamePrefix: {{ .Values.identityProvider.usernamePrefix | b64enc }}  groupClaim: {{ .Values.identityProvider.groupClaim | b64enc }} I don’t know if this is the expected behaviour.