Technical сommunity program
Run by users, for users
Start FREE on-demand training
Some time ago K10 went bananas and I had to disable it entirely. I have 20TB used on snapshots, it just keeps growing. I got to delete restore points, yet nothing happens. I’m now stuck with a small army of FCD’s I cannot delete manually or expand or do anything with. Where do I get rid of all these snapshots K10 created? I’ve deleted EVERY single restore point for each backed up application. This was backing up ~2TB, now I’m filling up my SAN at a rate of 5TB/day if I don’t disable the policy. I cannot find anything using all the documented commands via kubectl. Latest version K10, vsphere 7x etc. Do you have some tool that use the VDDK api to delete orphaned or all snapshots? I’m getting close to kicking K10 out.
Hello, Just getting into Veeam. Trying to install VeeamOne agent on my Veeam B&R box from my standalone VeeamOne server. However, it keeps failing out. I’ve tried unloading any anti-virus, disabling firewall. I’m running it using administrator credentials. It is not domain joined so it does not have any odd security policies. I’m using ComputerName\Administrator for the installation account. I looked at errors 1639 and 1708 but it provided little help. has anyone seen this or know a workaround?=== Verbose logging started: 3/24/2023 15:57:11 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\OneAgent\Veeam.One.Agent.Deployment.Service.exe ===MSI (c) (20:A0) [15:57:11:775]: Resetting cached policy valuesMSI (c) (20:A0) [15:57:11:775]: Machine policy value 'Debug' is 0MSI (c) (20:A0) [15:57:11:775]: ******* RunEngine: ******* Product: C:\Windows\OneAgent\OneAgent.x64.msi ******* Action: ******* CommandLine: **********MSI (c) (20:A0) [1
Trying to get K10 working with linkerd service mesh in a test cluster.Prior to deploying linkerd, k10 is working ok doing csi snapshots (Rook Ceph provider) and mysql logical backups (using the kanister example) with backups going to a minio cluster living in its own namespace.I have mesh enabled on the k10, minio and vaultwarden namespaces (testing using vaultwarden as I know it quite well and it uses a database). mysql logical backup is temporarily disabled. Unfortunately, k10 export fails:k10 appears to come up fine - no errors - all pods communication with each other - ui works fine vaultwarden works fine backup csi snapshot works fine backup export to minio fails with error (clip below)status: state: Failed startTime: 2023-02-28T09:58:27Z endTime: 2023-02-28T09:59:26Z restorePoint: name: "" result: name: "" error: cause: '{"cause":{"cause":{"cause":{"message":"Failed to exec command in pod: Internal error occurred: error executing command in container: failed t
HI all, So I am currently looking at rolling out VSPC to clients. but i don’t want the banner saying it is unsecure,. then client need to click and proceed,. for testing purposes i got SSL cert from zeroSSL and uploaded to the local computer personal store,. but this isn’t showing within my VSPC server can anyone confirm that SSL is the wrong certificate,. as I have read on Veaam documentation that a TLS is required? if TLS is required is their anyone that can recommend a temp free one like zerossl? thanks
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!
This week @Madi.Cristil and Rick are back in normal settings, sort of, but have a great stack of content to share as well as a solid list of special department news. See this week’s episode here:The Linksvia @jorge.delacruz via @Iams3le via @Martin Weber Special Department Newsvia @safiya - a new badge is added!via Rickatron via Rickatron - v12 Upgrade Center updatedvia @joachimeberhard in the Veeam R&D Forums: Happy about V12 performance improvements - R&D Forums (veeam.com)via @Gostev in the Veeam R&D Forums: V12 Top Issues Tracker[V12] Top issues tracker - R&D Forums (veeam.com)Also note that the Veeam Backup for AWS Plug-in is ready for download from My Account and the Marketplace listing was updated last week!
Recently, the threat actors behind Qakbot have been very active again. A significant number of attacks were noticed the previous time.Their most recent attack chain is detailed below:Malware spam campaigns are still the primary entrance point for Qakbot. To maximize the chance that recipients would respond to or interact with the message, they are faking email threads of well known companies for their spam communications.Both active Qakbot botnets are now using HTML smuggling again to provide the first attack load after briefly switching to OneNote files (see my recent post about a similar attack vector https://community.veeam.com/cyber-security-space-95/microsoft-onenote-files-used-to-distribute-emotet-malware-4451). Over the past year, many campaigns have employed this strategy of email spoofing.The Obama botnet presently deceives users into opening the connected payload, which is concealed as a base64-encoded string, by posing as a Onedrive mail. The BB botnet, on the other hand, m
Bonjour tout le monde,Je vous remercie par avance pour toute l'aide que vous m'apportez régulièrement.Comme toujours, j'ai besoin de votre aide pour migrer vers la version 12 de Veeam. Actuellement, nous utilisons la version 11, mais le support a expiré il y a deux ans. J'aimerais savoir s'il est nécessaire de renouveler le support et comment procéder pour effectuer la migration vers la version 12.Merci d'avance pour votre aide.Cordialement.
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
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.
