Solved

Hello Kasten Support ! We’ve got an error while trying to perform a Kasten DR restore that prevent Kasten catalog to be restored. Here is the configuration:Openshift 4.10  Kasten v5.0.2 (we have to upgrade it after restore) installed by Helm chart (Openshift Operator cannot be upgraded to v5.5.8 because of Openshift version) NFS Storage through PVCWe followed the documentation and:Install a Fresh K10 instance (with scc.create=true) Created the NFS Location Profile (which is valid and reachable) Created the k10-dr-secret with the correct passphrase Run a k10-restore application with the cluster-id and the location profileThe k10-restore instance failed with the following error:{"File":"kasten.io/k10/kio/tools/restorectl/servicescaler/utils.go","Function":"kasten.io/k10/kio/tools/restorectl/servicescaler.waitForHealthyService.func1","Line":73,"cluster_name":"XXXXXX-XXXXXX-XXXXXXX-XXXXXX-XXXXXXXX","error":"Get \"http://XXX.XXX.XXX.XXX:8000/v0/healthz\": context deadline exceeded","hostnam

Hi there, We would like to backup some large PVC (+ 5To) running with vSAN CSI.Snapshot running great but export in block mode run during 10 hours and stop at the end due to timeout limit.Our backup target is a MInio service hosted on Synology NAS with 10Gbps link and SSD caching. Performance tests are OK.We see some traffic on network card about 40Mo/s first time running export and then about 1-3Mo/s only for the other tries.“k10kopia” process only use about 30% CPU process during export. I already try to increase IOPS limits on vSAN profile without success. At this moment we can only backup lowest PVC size (500Mo to 10Go) without any issue.I can’t see any logs about k10kopia so i’m totally lost :( Thank you for your help ! 

Hello, Trying to restore a machine.Created a Veeam recovery iso. Boot the ISO Click “Bare Metal Recovery” Click “Network Storage” Click “Shared Folder” Type in “\\192.168.1.21\veeam2” and the username and password Click “Next” Now, see the “Specify a backup to restore from” the problem is that the file dialog box shows no files, states “No Items”Note: From other window machines, no problem accessing the share.c:\data>net use r: \\192.168.1.21\veeam2 /user:veeamserver02 "GXJMHxzv"The command completed successfully.c:\data>dir r: Volume in drive R is veeam2 Volume Serial Number is 311F-579B Directory of R:\01/13/2021  02:24 PM    <DIR>          .04/11/2023  10:58 AM    <DIR>          ..07/08/2021  11:18 AM    <DIR>          repository               0 File(s)              0 bytes               3 Dir(s)  623,201,038,336 bytes freeNote: From command line of Veeam recovery, cannot use `net use` without errorPlease see screenshots.   Thanks,David 

Hi, We have just upgraded our Kasten K10 multi-cluster environment to 5.5.8, and now some clusters say they don’t have license.For upgrading we used this guide:Upgrading — K10 5.5.8 documentation (kasten.io)New License Management feature:License Management — K10 5.5.8 documentation (kasten.io)All our clusters have less then 5 nodes individually, and previously all were counted individually from their 5 free local license pool. So everything was fine up until now. But after upgrading, now all the secondary clusters display the “default” 5 node starter-license (starter-4f1842c0-0745-41a5-aaa7-a01d748b1c30) as Duplicate, so they don’t contribute to the global mc pool, and also don’t have valid local license either (probably because of the “Duplicate” status).Does this mean that the licensing terms have also changed by this version? And now we have to count licenses globally (in a multi-cluster scenario), and not Per Cluster?(These clusters are for different small tenants actually, so they

Hi, After deploying and configuring Kasten 5.5.6 with an Azure location profile I created a basic policy and ran it: all is fine until the very last step which is failing. During the “exporting metadata” step the following exception is raised- cause: cause: cause: file: kasten.io/k10/kio/exec/phases/phase/migrate.go:796 function: kasten.io/k10/kio/exec/phases/phase.getMigrationString linenumber: 796 message: Invalid token reference file: kasten.io/k10/kio/exec/phases/phase/migrate.go:772 function: kasten.io/k10/kio/exec/phases/phase.getMigrationData linenumber: 772 message: Failed to get migration string file: kasten.io/k10/kio/exec/phases/phase/migrate.go:100 function: kasten.io/k10/kio/exec/phases/phase.(*migrateSendPhase).Run linenumber: 100 message: Failed to get migration data message: Job failed to be executed Which direction should I be looking into?

Hello,The question is in the tittle :)How do you perform the 3-2-1 golden Rules with Veeam for Microsoft Azure?I read this blogspot https://micoolpaul.com/2021/04/19/veeam-achieving-3-2-1-1-0-protection-for-cloud-native-workloads/ (thanks @MicoolPaul ) but I have some questions !Do you keep all your backup datas in Azure or use another repository for your copy?To be able to make backup copy an VBR must be deploy right ? Where do place you VBR server OnPremise on Azure? If we want to transfer backup data located in the Azure block to another S3 compatible storage, will transaction fees be applied?thanks in advance

Latest VBR 12 build installed on a workgroup server running Windows Server 2022.vSphere 7U3k.When trying to restore a file from a backed up vSphere VM, I get the following errors in the Backup Browser:  After the last error the Backup Browser closes.

Trying to upgrade to V12 I get this in one of the steps. Attached is the picture with the error. I can’t upgrade those servers as of now. I suppose I should stay on V11.RegardsO

For v12, it seems that only Azure or S3 (Glacier) are supported as Archive Tiers for SOBR.  I would like to use Google (archive buckets) but I don’t get the option to choose it as an archive tier.   Is this possible?  If not, will it be supported in an upcoming version(s?)   what about other cloud storage like Wasabe/S3 compatible? Thanks.

Hi All,I’m a Veeam newbie, doing some development work with the rest API. Using the REST api endpoint: /api/query?type=BackupJobSession I can get a list of backup job sessions. Within that I get the link to get the JobReference information. That's all fine, but what I need to get is the job log data:  Is this information available via the api? Thanks,Tim.

hello, thanks, first time poster,problem: `rclone copy` will run before the job completes.$JobObject = Get-VBRComputerBackupJob | where {$_.Name -eq "ABP_EN10"}# start job but do not wait until job completesStart-VBRComputerBackupJob $JobObject# rclone will not find any new files, as the job has not completed yetrclone copy .....how can i have the equivalent of$JobObject = Get-VBRComputerBackupJob | where {$_.Name -eq "ABP_EN10"}# run job, wait until completedRunWait-VBRComputerBackupJob $JobObject# now, rclone will find new filesrclone copy .....   

I’m not sure what’s going on, the drop down menu for Export Location Profile isn’t working eventhough my username is part of the k10-admin and k10-config-view group and was part of k10-basic. Under kube:admin, I can choose the location profile. Am I missing something? Thanks .  

Hi Team, Do we have an architecture document for K10? I’m looking something similar to what Red Hat did for their RHACS. Each rectangles are pods in the namespace.e.g.  

Hello,I am hoping someone can help.I created the object storage and backup repository but i am not able to select it. 

I am currently running Veeam 11 on Server 2012. I would like to migrate to Server 2019. I’ve tested a couple boxes doing in place upgrades and it didn’t go smooth. So, I  would like to spin up a new Server 2019 box and migrate Veeam. I’ve read the below article, and actually had to utilize it during my Veeam 11 upgrade to restore my config. My question is, how to I migrate since my repositories are on the Veeam 11 box? I have 3 disks on that machine with multiple repositories. When I go to perform the restore, those repositories are not yet on the new machine. What is the best technique for doing so? This is in VMWare, should i just add the old vmdks to the new machine? Is there a better method? I would love to shrink the vmdks in the process if possible. The backup database is much smaller than the vmdks. 

I am trying to deploy K10s but without success, I only need the Grafana Pod to start but it hangsNAME                                    READY   STATUS                  RESTARTS       AGEaggregatedapis-svc-64c55c6979-5gswn     1/1     Running                 0              81mauth-svc-79c7944dcb-mlfsh               1/1     Running                 0              81mcatalog-svc-6548c9f45d-sczm8            2/2     Running                 0              81mcontrollermanager-svc-cd748cdff-dsrnn   1/1     Running                 0              81mcrypto-svc-5846c467dc-ddqtn             4/4     Running                 0              81mdashboardbff-svc-5d4857cdf7-npldc       2/2     Running                 0              81mexecutor-svc-6fddc58f98-l6v9f           2/2     Running                 0              81mexecutor-svc-6fddc58f98-smfrk           2/2     Running                 0              81mexecutor-svc-6fddc58f98-zt8lv           2/2     Running                 0              81mfro

In an agent job for a WSFC (fileserver role) we see a warning after having switched over to the secondary node. Each job run now finishes with a warning that CBT table has changed.As with VM backups I expected the warning to disappear in the next cycle - but it didn’t. How can I reset the CBT for an agent backup (not hypervisor based CBT but Veeam CBT driver here)?

Hi, since an unattend shutdown of our server, our B&R can't established connection to our (only) linux vm.Of course this stuff worked before.When i tried to connect through ssh for the first time after the shutdown, it says that fingerprint key of the host changed. I bassicaly remove the old fingerprint in my local known-hosts file.- I checked sshd logs in the timeframe i tried to login through B&R console and this shows :sshd[10137]: Unable to negotiate with 192.168.0.216 port 52062: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]sshd[10139]: Unable to negotiate with 192.168.0.216 port 52063: no matching host key type found. Their offer: ssh-rsa,ssh-dss [preauth]- I tried to allow diffie-hellman-group1-sha1 and ssh-rsa in ssh_config file of my server. But it doesn't change anything. ❌- I tried with different user, it doesn't change anything. ❌- I reinstall ssh-server, it doesn't change anything. ❌- On B&R console i removed and add h

Ich möchte einen physikalischen Windows Server (ohne Hyper-V) mit Veeam B&R V12 sichern. Die Installation von Veeam B&R ist geglückt und funktioniert. Aber leider kann ich nur die Festplatten direkt sichern. Eine Installation des Veeam Agent für Windows ist nicht möglich, da er offenbar den Server weder über seinen DNS FQDN, noch über seine IP Adresse ansprechen kann. Auch eine manuelle installation gelingt nicht, da er nicht auf das Verzeichniss "\ADMIN$" zugreifen kann. Gibt es hierfür eine bekannte Lösung oder "Best Practice"?

need to activate the SureBackup feature on Acropolis AHV from Nutanix.

Hi, I’ve been struggling to understand from the documentation where and how the snapshots are stored if you don’t have a CSI driver that doesn’t support the volumeSnapShotClass. I have two sample workloads that I was able to snapshot and restore (Fig 1.). It was mentioned on another thread that it uses FCD, but I don’t see any new volumes either in my vSphere environment.The application below (credits to Google) doesn’t have any PVC. From my understanding if it doesn’t have a PVC then it would not need a VolumeSnapShotClass.[Fig 1] My environment:I’m running OCP 4.10 with ODF using vSphere as my underlying infrastructure. By default the OCP installer for a vSphere environment will create thin and thin-csi using Vmware CSI and vCP respectively. Is it using one of the PVCs in the kasten-io namespace?  

Dear Community,I’m running Veeam Backup & Replication Community Edition 9.5 and replicating offsite to a Cloud vendor. I upgraded it to Version 12 to get bug & security fixed. Upon reaching version 12 I came to know that the Cloud vendor does not support version 12, they only support 11a.Now the I have tried to downgrade it to 11a but the Database is locked to Version 12 and is not usable.I’m looking to rebuild on Version 11a and archiving backups. is this possible? Below are some queries and answers you might want to read. What is the exact upgrade and downgrade versions?                Upgrade (Current) Version: Veeam Backup & Replication 12 (12.0.0.1420 P20230223)                Downgrade Version: Veeam Backup & Replication 11a (11.0.1.1261 P20230227)•  What Veaam components are being used?                Veeam Backup & Replication Community Edition package•  OS details on which Veaam is installed.                Microsoft Windows Server 2012 R2 Standard•  SQL/ D

Hello,I have a k8s cluster running on top on VMWare infrastructure.VMWare CSI (csi.vsphere.vmware.com) is installed and is working correctly.I have installed too the volumesnapshotclass with the controller on top of csi.vsphere.vmware.com CSI driver as described here: https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/docs/book/features/volume_snapshot.mdThe volumesnapshotclass  is working well; I can snapshot PVC and restore them as well without problem.But Kasten refuses to use the volumesnapshotclass.For instance, running preflight tool:$ ./k10tools primer csi-cluster-checkCSI Capabilities Check:  Skipping, K10 does not use CSI snapshots for vSphereIs it possible to say to Kasten: I know I am in a vSphere environment, but please just use volumesnapshotclass to backup the PVC?Many thanks for your help

I recently updated a client from Veeam 11, I think .816 to the latest version available. Everything went as usual as I do these quite often but this one is throwing a pop up that states, "unable to upgrade plug-ins under the current user, please open the console under an account with administrative privilege's:" when I launch Veeam. I am logged in as a local administrator account and have updated this client in the past with no issues.I just click on okay and it opens up like normal. I also checked for any updates to the managed machine and there is upgrade option. This is a stand alone Veeam system with no remote components.I don't think it's going to impact the functionality but will know more after tonight's job run.Appreciate any feedback!Thanks,Poettone!

Hi, we have a strange issue where if we boot to VEEAM recovery media created in server 2016 or Server 2019 we can see the recovery EXT HDD but it shows as needing to be formatted and unreadable, we are currently using Western Digital My Passports formatted with REFS. Thanks in advance