Community

Hi All, In early December, I set myself the challenge of writing a blog post every day and putting together an Advent-style calendar covering topics ranging from security and automation to a few features I genuinely enjoy.It was an ambitious goal, but I’m happy to say I completed it. I’ve been sharing each post on LinkedIn daily, but I wanted to post the full collection here as well for anyone who isn’t connected with me there.If you’d like to read along, please feel free to share. I hope you enjoy it. Advent Calendar Day 24: Thank You and Looking Ahead | Homelabpro Blog

In my home lab I want to experiment with the new Veeam VBR v13 appliance. On one hand to try it out before migrating at the organization I work for, on the other hand because I love to try new things out and thinker with it. So I use the ISO deployment method to deploy on a virtual machine on Proxmox PVE, that is a supported scenario as I read in the documentation. I go through the installation procedure, slightly annoyed that I can’t select a keyboard layout and have to type a difficult password on the wrong layout, but I can manage that 😉. On my first attempt I’ve set a static IP and a simple hostname (not FQDN) and disabled IPv6. I’ve chosen not to create a security officer account, since it’s just me anyways. The option is there to skip, so I assume it’s supported. After completing the process, I can access the host management on port 10443 just fine using IP address or using the hostname(created a DNS record for it). However the normal webUI on port 443 is not responding

I understand from our network team, that the SQL agent running on Microsoft SQL 2019 causes the SQL server to lockup or the backups to lockup. Is there a method to configure the backups (data & logs) to prevent that?

Hi thereI have a question around hardened repository. A customer has purchased new hardware to implement a hardened repo and add it to the existing VEEAM setup (latest 12.x).I am trying to determine whether I should suggest to use the VEEAM Hardened ISO. I have downloaded version 2.0.0.8. Or should we stick with using Red Hat and harden that accordingly. My colleagues have done that before and we have the scripts to automate.I am new to the hardened repo game but I would think that using VEEAM iso would be simpler.What are the pro and cons?Also, maybe a silly question but it seems to me that the hardened repo is also built into the V13 virtual appliance ISO. Would it be possible to use v13 hardened repo and connect the repo to a VBR12 setup?Much appreciated.

Hello all, we are looking into SQL Server backup options, we have done a full server and a volume backup also. We see there is a Backup>Application>SQL option, however we cannot see the SQL option in our console….any ideas as we can see Oracle and Mongo available. Thanks in adavance, Tony.

Hi everyone, I’d like to get some feedback before deploying Veeam v13 in our environment. I’ve been tied up with other projects over the last six months, so I haven’t tested or worked with v13 yet. Our infrastructure is fully virtualized. We currently run two VMs: One VM running Veeam, performing daily jobs to an external Ubuntu hardened repository One physical server running Veeam, backing up everything to its own ReFS-based storage  My questions are: What is the best approach for deploying v13 — on a physical server or a virtual machine? Is it possible to use hardened storage with Veeam on the physical server?  Thanks in advance for the input!

 ...and why you still use the Windows Console! We are now used to having the standard console already present on the VBR server or installing it on a bastion host. Change can be scary, but we want to face it and take a leap into the future.If you're reading this article, probably you're thinking: "Oh, finally I can use Veeam with a web console and I can say goodbye to old Windows components!".Well... not quite. If you remember, in my previous article I wrote about this too.Let me tell you what we are doing: in last weeks we started a new implementation project for our client with Veeam v13 version.After installatio

For those who joined my online and VeeamON sessions on migrating from VMware to Hyper-V or Proxmox, I promised I would share my cleanup scripts. It took longer than planned to prepare them, but they are now ready.Online session HERE unfortunately there is no video of the VeeamON session that was migrating to Proxmox.When you use Veeam to migrate a Windows virtual machine, the work is not done when the job finishes. Your migrated VM is now running on a new platform, but it still contains old drivers and devices from VMware.These leftovers can cause instability, performance issues, or future

I'm creating some labs on AWS and today I'll share the Veeam part with you. Lab Details:VBR:Instance size: c5.2xlarge  Availability Zone: us-east-1f  Architecture: AMD64  Total memory: 16384 MB  Network: Up to 10 GigabitJobs created:EC2 EFS FSx VPC First, why not use Marketplace?As many already know, taxes in Brazil are massive.Because of this, I usually don't use Marketplace, since the taxes are even higher through Marketplaces. (Until 40%)So I prefer to deploy Veeam traditionally on EC2.Here are some steps:Upload the Veeam .ISO on an S3 Create an EC2 (will be our EC2) Use TNTdrive to mount the S3 for EC2 Install V13  Using CLI AWS to upload de .ISO: "C

hi,i try to install veeam  agent (i try with multiple version) on windows server 2025 but when i get to the point of installation it fails.on the log i see “ another installation is in progress” but i don’t have nothing in pending.

Hey guys,I hope you are fine and ready for the end‑of‑year holidays.I wanted to share an issue I encountered this morning while integrating VDC Vault on a VBR server running on 2012R2. Yes, I know, the OS is no longer supported — a redesign project is planned soon. To quickly improve backup security, we set up a Vault. Unfortunately, during the integration I received the following message: I didn’t see any specific prerequisites in the Veeam documentation regarding the operating system for integrating VDC Vault.After going through several pages, I found this in the Help Center: Make sure you have WebView2 Runtime installed on your backup server.Once it was installed, we were able to complete the configuration and create our backup copy job.Cheers !

Hi everyone,I’m studying the v13.0.1 training course in order to delivery its next year, during reading the course material, I found the information that not all functionalities are available on VBR Windows still available on VSA, I’m trying to find a list of those unavailable functionalities, but so far, I couldn’t get a list of them, does anyone know what functionalities are not available on VSA v13?

Anyone can help me to resolve this issue.