Technical сommunity program
Run by users, for users
Start FREE on-demand training
Hi Folks, A new version of kasten came out 5.5.7 so I wanted to take a look. For this I decided to pull out my old desktop and use rancher desktop. I also updated my k3s version in Rancher Desktop to 1.25.7After installing I wanted to create a token as is the method now for access if using token authentication but got and error:Error This was a classic example of the kubectl binary being too far behind:So then I tried to update it but none of the methods would work. I will admit you can get confused when you hop around operating systems and different ways of install kubeclusters. I reliased that I had also installed kubectl on this desktop by leveraging chocolatey. So time to upgrade. Ok looks good:version I can now create a token: Token
We had some problems with restoring VMs in the last time.After some research we found that the Proxy on Linux has a problem with the assignments of physical volumes. It seems that there are PVs of target machines are preserved in the LVM archive files of the proxy… This is causing problems at restore time – leaving the restored VMs unbootable.I have double checked the Veeam documentation about prerequisites (https://helpcenter.veeam.com/docs/backup/vsphere/backup_proxy_requirements.html?ver=110) and found no hint that LVM is a problem with Linux proxy.The problem occurred with Suse Linux only, we are in the process to check if there is the same problem with RedHat Linux. To visualize the problem, I will show it from the Veeam Proxy perspective and from the target VMs perspective. Veeam ProxyList the physical volumes with pvs. One device is not found…Grep for the UUID of the missing volume in the directory /etc/lvm/archiveIn this case the UUID is found in three files. At these three occ
Hello Veeamers, my name is Christian Eromosele, a System Administrator, and I live in Germany. I'm very much excited to be here as a community leader.As a community, we all have a shared interest in topic/cause, and I believe that we can accomplish great things by working together, and engaging more actively.I encourage everyone of us to introduce ourselves and share a little bit about themselves. It's important that we get to know ourselves so that we can better collaborate, organise events and even support one another.In addition, I'd like to suggest that we all actively participate in this group by sharing our ideas, insights, and experiences. Whether it's by asking questions, sharing resources, or engaging in discussions, we all have something valuable to contribute. By doing so, we can move this group forward and make a positive impact.Thank you all for being here, and I look forward to more active participation from every one of you!
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
Rickatron & @Madi.Cristil are back at it this week catching everyone up on a solid block of content and some special department news. Watch the recap here:The Linksvia @Michael Melter via @SteveF via @JMeixner Special Department Newsvia @safiya → Updated new badge!via @Cragdoo @MicoolPaul and @Ian Sanderson via @michaelcade Veeam Backup for AWS plug-in has been updated!Tune in to an exclusive Twitter event for Veeam Backup for Microsoft 365See this important KB for an update to Veeam ONE V12Who’s NewBig thanks to @safiya for producing a new Who’s New format! We welcomed +295 new members this week and the coolest usernames are: @Lightworm @capnhowyoudo @Network Admins @SUPPORT SCRIBA @Helper @LuvsVeeam @Network AdminsAnd the best part, a new selection - Alfred’s pick! Congratulations @Backup → you are Alfred’s pick this week!
Hello there! Recently I installed a new VEM server and when I tried to establish connection with my VBR servers i get this message below:I had ever test communication on 9392 and 9405 TCP ports and it works fine.Any idea about this?
Prior to upgrading to Veeam V12, ensure that, "Transform previous backup chains into rollbacks" is not enabled in your environment. If it is, the upgrade will fail as per KB4390: Feature Deprecation: "Transform previous backup chains into rollbacks" (veeam.com)I just wanted to point out a slight caveat when checking our environment. If you decide to check each job setting and disable the option, bear in mind, if you have a snapshot job with storage integration, it may still show as enabled. Normally a snapshot job looks like as follows without an option to select the backup chain option: However, running the PowerShell command:Get-VBRJob | where {$_.BackupTargetOptions.TransformIncrementsToSyntethic -eq $True}returns the following: This can be easily sorted by running:Set-VBRJobAdvancedBackupOptions -Job "Job Name" -TransformIncrementsToSyntetic $false
Hi Folks, Folks with automation. Github rsa host key was leaked so they replaced it just in case. https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
Hey everyone, Was browsing the R&D forums (I know, I’m a traitor!), and discovered this post from Gostev announcing the end of VeeamPN!https://forums.veeam.com/post467237.html#p467237 This caught me by surprise as I felt like more noise would’ve been made around it, maybe I was one of the only people that used it, but I remember once dealing with a managed network that was refusing to integrate additional routes to perform SureReplica at a remote site, so I used VeeamPN to create a tunnel between the sites and create my own route that way! 😆 So long VeeamPN, you were awesome. 🍻
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?
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.
