Community

This is the second time my Veeam 13 console cannot connect and shows the error below.The first time I faced this issue, I reinstalled VBR and it worked normally. However, now that I am facing it for the second time, I feel there might be a bug in this version.After checking the Veeam services, I found that there are three services that cannot start:Veeam Backup Server RESTful API Service Veeam Explorers Recovery Service Veeam Web ServiceHas anyone else experienced the same issue?   

Community,Wasabi has made a MCP (Model Context Protocol) server available to access stand-alone accounts as well as control accounts. Toolsets include: S3, IAM, and WACM (Wasabi Account Control Manager).All of the details are available here - https://wasabi.com/cloud-object-storage/mcp-for-aiNow you can utilize natural language queries to see practically anything you’d want to know about your account settings, utilization, and users. I can imagine easily integrating these tools into a support agent at your favorite MSP… 

After my previous articles on backup security and object storage on-prem, today, we'll examine the best practices for using them with Veeam.Here Why go with on-premises object storage and here The choice of storage explained my ideas about a new generation storage as a backup repository.So we'll check out the best configuration for creating a backup job and explain why we chose it.Object Storage as the main repository in Veeam v12.3.As we all know, since version 12, it's been possible to use an object storage repository as a primary destination for backups. This makes the architecture simpler and offers greater flexibility.When you're getting started with object storage as a repository, it's important to remember the backup block size (block size) that's used for writing.The size you choose in the 'Storage Optimization' tab, configuring a backup job, affects how the data is divided and stored.How do we calculate the space we need for our repository?I started using a calculation tool re

Hello,We are using VSA v13 (linux) and we use powerstrore is there still a integration with Powerstrore, like on v12 windows. There was a installer but this oviously does not work.Even tried it installing on the BR console no luck there

In today’s digital world, data security is a top priority for organizations. Veeam Backup & Replication has evolved to meet these needs, and one of its key innovations is the Veeam Hardened Repository ISO—a solution designed to protect backup repositories from ransomware and other cyber threats.What Is the Veeam Hardened Repository ISO?The Veeam Hardened Repository ISO is a Linux-based solution that secures backup data by making it immutable. This ensures that data cannot be modified, deleted, or encrypted by unauthorized parties, even in the event of a ransomware attack. The repository allows organizations to set a retention period during which backups remain secure and unaltered.Key Features:Immutability and Retention Locks: Ensures backups are safe from external modifications. Ransomware Protection: Protects backups from being encrypted or deleted by ransomware. Linux-based Security: Utilizes Linux’s built-in security features for enhanced protection. Enhanced Data Availability:

Having updated to Proxmox VE 9.0 below. There is a need to upgrade from  Veeam Plug-in for Proxmox VE build 12.1.3.217 to plug-In build number 12.1.5.17 to support it.The Proxmox VE Plug-in integrates the backup server with the Proxmox VE server and enables worker deployment. From version 12.3.1 and above, you do not have to manually install this plugin.You can download the Plugin for Proxmox VE directly from the referenced link, or navigate to the release Information for Veeam Plug-in for Proxmox VE v12.1.5.17 in the following KB article.To see the current version of the Veeam Backup for Proxmox plugin that you are currently using. Please launch the Control Panel or Windows Settings as you wish. As you can see, we are currently using the version 12.1.3.217 As you can see below, this meets the requirement for the Veeam Plug-in for Proxmox VE build 12.1.3.217 which can be determined via the steps below.You can check the build number in the Veeam Backup & Replication Console’s Main M

I’m playing with the VHR ISO and wonder how we can add a second LVM volume to the VHR.We do this for RHEL and Ubuntu builds so I’m interested if we can do this with VHR.The sort of scenario would be where you add another bunch of disks or disk shelf into a physical server (and possibly controller) so we can have a physically separate second set of storage rather than buy a new server.Some use cases:You also might want to separate remote site backups onto separate Repo’s for specific regulatory or governance requirements Getting the most value from the physical hardware

Hi all,I’ve been trying to troubleshoot an issue I’ve been having with the Veeam Windows Agent for a few weeks now, and I’m still stumped. I will try to provide as many relevant details as possible, please correct me if any of this is incorrect.I’ve been using this Veeam product for around 10 months. My use case is that I want to have a secure, offline backup of my laptop’s main SSD. So once a month, I connect a 2TB external HDD (Seagate, NTFS) to one of my laptop’s USB 3.0 ports, and run a volume level backup of just the SSD (this is the drive the OS is installed on). The laptop is running Windows 10 and the latest version of the Veeam Agent.Until recently, everything worked flawlessly. The issue began when I noticed the HDD was quickly filling up, and I realised that I had not specified how long Veeam should keep backups for, so all incremental backups were being stored. So, I edited the job and set that setting to 8 days - reading the online manual, this would mean that since the ex

When creating a backup job with VMs in a ovirt cluster, you are not allowed to select all VMs associated to that cluster.  You have to individually select each one for that job.  This is not ideal if your VM inventory changes and you are not aware.  Why can’t ovirt we have the same function as VMW cluster backups.

We are reviewing our Veeam Backup for Microsoft Azure design to optimise Azure storage costs while maintaining best practices. Currently, our Azure VM backups are stored in GRS storage accounts, with daily backups (31-day retention), monthly backups, yearly backups in a separate GRS repository, and hourly snapshots. We also have a 125TB Veeam Data Vault subscription and use Backup Copy Jobs to maintain an immutable offsite copy of all backups. Given that we already have a secondary immutable copy in Veeam Data Vault, we are questioning whether GRS is still providing sufficient additional value to justify the extra cost compared to LRS.We are considering creating new LRS-based repositories and directing future backups there while leaving existing backups in the current GRS repositories until they age out naturally. Is this the recommended approach, and would restores continue to work from the existing GRS repositories during the transition? Also, if we retain GRS, can someone explain th

Hello Im very new to Veeam and i installed on a server Veeam Backup and Replication. Now i get this error message: (it never worked)  I read that the API Service needs to be started, but this is not working and an error occurs.  Also its not possible do uninstall the Veeam Software with the Error → Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. It is the adiminstrator user. The new Update i was able to install but also after this update from march i get the same error message. Does anyone have a idea how i can fix this issue?

Hi all, I'm stuck on this and hoping someone has faced it before.Setup: On-prem VBR 12.3.2 (10.91.5.243). In Azure there's a Veeam Backup for Azure appliance v6 with private IP only (no public IP allowed by the customer). Connected via IPSec site-to-site VPN. I need to register the appliance in the VBR console to do a failback of an Azure VM back to on-prem vSphere.What I've tried:Add Server wizard -> Veeam cloud-native backup appliance -> connect to existing appliance, using the appliance private IP -> fails Test-NetConnection to the appliance IP on 443 shows True, but I later noticed the latency is <1ms and there's an ARP entry for it on our LAN. So I think my tests were reaching some local device, not the appliance in Azure Browser from the VBR server to the appliance IP gets redirected to :4343 and refused (Veeam support told me 4343 is not even a Veeam port) Checked proxy on the VBR server (winhttp, IE settings, env variables). All clean, no interception Veeam support

 1) In the beginning there was the password…… and of course it was created by humans—so it was often simply “1234”, “<first name><birth year>”, or “password”.“password”: A password as secure, useful, and brave as an umbrella in a hurricane — but hey, it worked for logging in. You logged in, everything was fine, and back then life didn’t yet have password policies—and luckily, at the start there also weren’t worldwide automated attacks via the internet.Then password security policies were introduced step by step—but let’s be honest: humanity is lazy and most people’s memory isn’t that great. So “password” turned into:At least 1 uppercase letter: Password At least 1 numeric character: Password1 At least 15 characters: Password1234567 At least 1 special character: Password1234567!What an evolution. Ah, humans are as simple as they are brilliantly constructed. One of the newer developments is the passphrase, which actually helps. The idea is to combine several words that are ea

I try to use Veeam13 appliance version, and need help can/how i can mount the iscsi drive to the veeam13?

Hello , We are planning to migrate our infrastructure from an on-premises Hyper-V environment to Microsoft Azure. Our current environment consists of: Hyper-V virtual machines protected by Veeam Backup & Replication.The Veeam Backup & Replication server is currently running as a Hyper-V virtual machine. A NAS device is used as the backup repository, which will also be decommissioned as part of the migration. We would like your guidance on the following: Does Veeam offer a cloud-hosted or SaaS-based backup management solution that can replace our on-premises Veeam Backup & Replication server? If such a solution is available, can it manage and protect Azure virtual machines while providing the same or similar functionality as Veeam Backup & Replication? ​​​​​​​If a cloud-hosted Veeam solution is not available, what is the recommended architecture for customers migrating entirely to Azure? Additionally, regarding our backup repository: We plan to decommission our existing

I am back with blog 3 in my series and this one looks at the v13 Web UI and what you should test first after implementation.Blog - Veeam v13 Web UI: 5 Things to Test First Veeam v13 Web UI: 5 Things to Test First Introduction A new web-based management experience is not just a visual change. It shifts how backup administrators reach the platform, how they review workloads, and how quickly they can respond when they need to restore something under pressure.That is why the first production tests should focus on routine operator behavior rather than feature exploration. The question is not whether the interface looks modern. The question is whether the most common backup and recovery tasks are clear, fast, and dependable in the browser. 1. Test the Login Path Start with the most basic workflow: sign in from the workstation or jump host that administrators actually use. This confirms network reachability, certificate trust, browser compatibility, and whether the access path feels consisten

 Recently, a customer asked me about Microsoft’s changes to throttling and service limits. In the past, they had used the multi-app registration approach and now wanted to clean it up. They also asked for clarification on how to handle backup settings and optimizations going forward.Regarding backup throttling and the EWS → Graph API transition, I have already published two blog posts — feel free to check them out:Microsoft EWS is dead. Long live… Graph?„Dr. Backup and the Quest for the Holy Backup Performance Stream: Mastering the Latest Microsoft Throttling Changes (March 1, 2026) with Veeam Backup for Microsoft 365 v8.4 and VDC M365Now, let’s focus on cleanup first—because multi-app registration no longer provides any performance benefits (see KB4821). Removing it is possible in both on-prem and VDC environments, but the steps differ slightly.  Step 1: Identify the App Registration IDs You Want to Remove In VDC Backup Service you can find them here:Veeam Data Cloud –> Microsoft 3

Hi All,I’m wondering if there is a more widespread issue with Veeam Backup for Microsoft 365?A customer has recently noticed the processing speed for their M365 jobs is grinding to a halt and not finishing at all. They have tried many things including provisioning a physical server with SSD but the job processing rate remains very low.Are there any suggestions to improve this? They are on the latest version and only noticed the issue within the last few weeks.Setup - One Server, One organisation. 4 jobs to process - Mailboxes, SharePoint, OneDrive and Teams.Using one account for all jobs. Any guidance would be appreciated. Thanks, Peter.

Hi,We are just moving customers away from VMWare to HyperV and I have got a problem at one site.I have added a Ubuntu 24 server as a backup proxy onto the DRHost. I then added it in Veeam, and I can see it in the list of Backup Proxies, but I am unable to select it when trying to set it up in the available proxies in the job.It isn’t greyed out, and it went through the setup pretty much okay. I did get this message:veeam cannot find nfs mount tools on the linux machineI am not sure if I need that though, sorry, not an expert on this bit.At the moment the server is not in the box of available proxies.Can anyone help?

Hi everyone,I have been testing Veeam Backup with Proxmox and overall I think the integration is a good and important step. The Veeam Backup Worker concept also looks promising and works reasonably well so far.However, compared to VMware-based jobs, the current Proxmox implementation feels less flexible in a few areas. I would like to share some feedback and also check whether I may have missed something in the configuration.The main points are:No backup encryption option visible In the Proxmox backup job settings, I currently do not see an option to enable backup encryption. This is something I consider important, especially when backups are stored on shared repositories, offloaded, or handled as part of a broader security concept. Is encryption currently not supported for Proxmox backup jobs, or is it configured somewhere else? No job chaining / “start after another job” option For Proxmox backup jobs, it looks like I have to configure a fixed schedule, for example a specific daily s

Dear Experts,I'm validating Veeam Backup for a client.I would like to back up VMs on Nutanix AHV.I created a backup worker by referring to the following documents.https://helpcenter.veeam.com/docs/vbr/userguide/ahv_workers_add.html?ver=13So, I have some questions.Our customer wants to synchronize the time of this WORKER with their NTP server.Q1) Is it possible for Veeam's WORKER to synchronize their time with their NTP server?Q2) Could you please tell me how to synchronize the Veeam worker with their NTP server?I apologize for asking such a very basic question, but could you please tell me?Kind Regards,Hideki

I am a first time Veeam customer trying to set up a new test environment using a trial license in hopes to purchase it. I have one physical HPE server that is running the Veeam VSA installed from the latest ISO file.  This is the only backup repository.  I have a second physical HPE server that is running Windows Server 2022.  This has a tape drive connected to it.  This also is the windows mount server.  I also have a laptop that I’m using just for management purposes with the console installed. I have a third physical server with Hyper-V on it.  I was having no issues backing it up but I created a new virtual machine with 2 large disks for testing and pointed it at the VSA iso file and during install chose the Veeam Enterprise Manager option.  I am not totally certain but believe this is what broke backups for me.  Now when I try to backup any of the virtual machines on this Hyper-V server I get an error “Unable to detect the VBR BIOS UUID. This error likely appears because the Veeam

I setup Veeam Agent 13.0.3.1220 on a new windows 11 pro computer and have been unable to get it to complete a backup task. I restarted the VSS services with no change. It’s backing up to a synology nas file share. Here are the backup details.  Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{43dab221-71ff-43cf-8389-49fcb4151cd9}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{43dab221-71ff-43cf-8389-49fcb4151cd9}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [

Hello,I need some recommendations or ideas for my backup-to-tape design.I need to back up VMs to tape with the following retention requirements:Daily retention: 365 days Monthly retention: 12 months Yearly retention: 3 yearsAssuming I have enough tape cartridges available, what would be the best way to design the media pools?My initial idea is:Create one job with a media pool for daily backups. Create 12 jobs with 12 separate media pools for monthly full backups. Create 3 jobs with 3 separate media pools for yearly full backups.However, I think this approach may make restorations more complicated. For example, if I need to restore data from April 5, would I need to mount the April monthly tape as well as all daily tapes required to reconstruct the backup chain from January 1 to April 5? Am I understanding this correctly?Therefore, I am considering a different approach:Combine the monthly and daily backups into the same backup chain. Each media pool would contain one full backup followe