Veeam Data Platform v13 Upgrade Center
Top technical сommunity program
Run by users, for users
Start on-demand training
Hi Everyone, Happy friday!I need to get involved with Kubernetes/Containers, I’m asking you guys because you can give me a more assertive answer, I know that there are a lot of content online, but I don’t know which one is better to start my learning. Could you please give me a road map to start from the begging and became a master on it?THANK YOU!
Política de Uso Justo da Veeam Data Cloud: O que você precisa saberA Veeam oferece armazenamento ilimitado para proteger seus dados, mas com responsabilidades. Entenda os limites e evite custos extras.Alocação de Dados por Usuário: Microsoft 365: 100 GB por usuário licenciado Microsoft Entra ID: 15 GB por usuário licenciado Salesforce: 5 GB por usuário licenciado Uso Excessivo:Ultrapassar 300% da alocação mensal pode resultar em cobranças adicionais.Cobranças Adicionais:Se o uso exceder os limites, a Veeam pode cobrar por armazenamento extra ou pacotes adicionais.Notificações:Você será avisado antes de ultrapassar os limites para ajustar o uso.Uso Responsável:Utilize os serviços para backup legítimo; abusos podem levar à suspensão da conta.Para mais detalhes, acesse a Política de Uso Justo da Veeam Data Cloud: https://www.veeam.com/legal/veeam-data-cloud-fair-use.html#:~:text=This%20means%20that%20You%20have,for%20additional%20storage%20costs%20incurred.
Hi all,I want to update Veeam Agent for Windows from 6.3.2.1205 to 6.3.2.1302. The in place upgrade doesnt’t work: Will my backup job settings be safe when I uninstall the current installed agent and reinstall the new version of Veeam Agent for Windows?Kind Regards
Because of the new v11-feature of immutable backups on XFS filesystem, I am looking for real-world experiences with XFS as Repository.I just read through this forum entry:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.htmland the closing experience of user ferrus:https://forums.veeam.com/veeam-backup-replication-f2/v10-xfs-all-there-is-to-know-t65222-30.html#p388579 Sounds very good to me so far. I can remember first implementations of ReFS Block Cloning. Lets say, it does not work that fine at the beginning.Would you share some of your experiences with XFS as Veeam Repository? I would be interested in:stability performance (over time) needs for troubleshooting administrative effortThanks!
This week @Rick Vanover is on a well deserverd vacation but I have special guests, @Scott and @CMF ! We are discussing Block Repository - DAS Using Internal Disks, how to Veeam Recovery Orchestrator - Planned Failover, Veeam ONE V13 with a Veeam VBR V13 and so much more! Featured Content via @AndrePulia via @Dynamic via @PeteSteven Vanguard Blog Spotlight @benharmer : https://benharmer.blog/2025/10/13/automating-deployments-with-vbr-v13/Special Department News Have a great weekend everyone!Madi
Hi all,looking for real-world guidance on NIC sizing for a Linux Hardened Repository.Context (VBR 12.x or 13.x ; Linux appliance vs Windows?): Repository: Linux Hardened Repo (XFS, immutability). Repo server NIC options: either 2×10/25GbE or 4×10/25GbE. Backup server/proxies can also be 2×10/25GbE or 4×10/25GbE. Primary storage for the VMware workloads will be either 32G FC (Direct SAN from proxies) or 10/25GbE iSCSI. Single site, LAN backups (no WAN in the data path). Goal: Max throughput and resilience without adding complexity that doesn’t pay off.Has anyone measured a meaningful improvement going from 2×25GbE to 4×25GbE on a single Linux repo?What actually worked (or didn’t) in your environments — “wish-I-knew” lessons appreciated :-)
I am working on a scenario where the customer is using Data Domain on premises, offload to Vault, then archive tier. When I clear the checkbox for ReFS/XFS, the repository usage calculations disappear. When I check the box again, the calculations appear. All other settings remain the same. Not direct to objectCapacity Tier, Vault, Copy, MoveMove period = 7Archive Move is 60 daysImmutability in Perf and Capacity tiers is 56 days.
If you have not upgraded your Promox node yet due to dependencies on Veeam Backup and Replication (VBR). The wait is over as Proxmox Virtual Environment (PVE) 9.0 is now fully supported. It is packed with powerful new capabilities for modern virtualisation and software-defined data centres. Whether you are running a home lab or managing enterprise-scale clusters, this release is a game-changer.Recently, I created some blogposts on how to setup Proxmox VE and also how to Backup and Restore Proxmox VE virtual machines with Veeam.So I had wanted to upgrade to Proxmox 9.0. But because this was not supported by Veeam yet, I ended up protecting the VMs only running on Proxmox 8-3-1.Now, with the release of the new Veeam Plug-in for Proxmox VE v12.1.5.17 It now support for Proxmox Virtual Environment versions 9.0 For what’s New in Proxmox 9.0 and other details not discussed extensively in this guide, please visit the following link. Update Proxmox VETo update Proxmox VE, you can use either th
Importantly, administrators are responsible for enabling and configuring the fencing mechanism after cluster deployment. Without the fencing configuration, node remediation and VM restarts will not happen as expected. In virtualized environments, high availability (HA) is essential to keep workloads running even when a node fails. In OpenShift Virtualization, HA leverages Kubernetes-native mechanisms combined with OpenShift’s self-healing infrastructure.A key element is fencing, the process of isolating a failed node to prevent issues like split-brain—a scenario where nodes lose communication but continue running independently, causing data inconsistencies and conflicts.When a node goes down, restarting virtual machines (VMs) happens in three phases: Failure detection – Identifying that a node has stopped responding. Fencing – Ensuring the failed node is safely isolated with no active workloads. Remediation – Restarting affected VMs on a healthy node. Through this approach, OpenSh
Guys, I need to choose a technology to further my studies. Honestly, I don't know if I should focus on more traditional hypervisors, or consider something a little different like containers, clouds, etc., or even, of these traditional ones, which would be more interesting to focus on? We're seeing vSphere being migrated to KVM, Proxmox, Nutanix, and others. Which of these hypervisors that are being used instead of ESXi do you think will take off?This is a personal question for you. I know no one has a crystal ball, but your experience certainly counts.Thanks for your help, I’ll appreciate that!
Already have an account? Login
Enter your 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.
