Recently active topics

Hi everyone,I’m using the Veeam community edition to backup some data to WORM tapes (I have an HP Ultrium LTO-4 1840 tape drive with HP LTO-4 WORM tapes). Unfortunately, I’m getting the following error when the backup job starts: “There is an old MTF block on tape. Cannot write a new one” after which the job fails before backing up any data.  The WORM tapes are all brand new/sealed, so are completely blank and the write-protect toggle/switch on the tapes are all set to off. I created a WORM Media Pool and selected ‘Do not create, always continue using current media set’ for the Media Set.On first-time insertion, the tapes were inventoried and added to the WORM media pool (Veeam successfully recognizes the tapes as WORM capable) so all looks good.However I’ve tried 3 brand new tapes so far and they’ve all failed with the same error above, although the same backup job works perfectly on normal RW tapes, so I’m not sure if I need to do anything extra in Veeam to get WORM tapes working?I’v

We’re setting up the Veeam Software Appliance (VSA). We got an error when we tried to connect to our storage device, "Failed to get certificate from: https://xxx.xxxxxx.xxx:5392." technical support has advised us to “ensure that the cipher suite 'TLS_RSA_WITH_AES_256_CBC_SHA256' is enabled on the Veeam appliance.”The command “openssl version -d” returns “OPENSSLDIR: "/etc/pki/tls".” When I try to edit openssl.conf in that folder, I get an error, “E45: 'readonly' option is set”. How can I enable the cipher?Thanks for reading.

IntroIn a previous article I wrote about the type of storage a customer can use and write their backup to.Some days ago, a user in the Veeam Community asked why, according to Veeam's calculator, S3 object storage is no longer more efficient in terms of space (with immutability and GFS) than storage using XFS/ReFS technology.After answering, I decided to explore the topic further by putting myself in the shoes of a customer who has to make a choice in terms of the costs associated with the space used. That's why I want to tell you what happened with a customer.When I start a new backup infrastructure project, there always comes a time when I have to decide what type of storage repository to use. When I submit a plan to the customer, I often hear them say: Why should I spend more and use more space than requested?It usually happens when the storage budget is already tight, immutability is mandatory, and you are stuck in the middle between security, costs, and unrealistic expectations.Sit

Veeam Backup and Replication v12.3.2 (Free)VMWare ESXi 8.0 (Free) Hello Community! I’m hoping someone here can help me.I have successfully  backed up a physical Windows server using Veeam agent. Created a recovery media to use for restore into a VM. I have created the VM with similar CPU/RAM/Disk as the physical server. Powered on VM and booted it using the recovery media. During the restoration, the process fails with these error messages (see below). I tried looking for the logs in C:\ProgramData\Veeam\Backup but there were so many in there so I couldn’t which one to look for. If anyone has an idea on how I can resolve this issue, please let me know. If you need logs, please tell me which one to look for.Thank you very much! Error Message 1 Error Message 2 

Dear Community, What could be the issue while upgrading VONE to the latest version?   

Dear community,  Applications are now open for the 2026 Veeam Vanguard class. Any Veeam enthusiast publishing Veeam-related content (e.g. articles, video guides, speaking at Veeam events, podcasts) can apply to become a Veeam Vanguard. There's an article I published on the Veeam Executive Blog (https://www.veeam.com/blog/veeam-vanguard-2026-applications.html) containing a link to the application form at the top of the page, labelled "APPLY NOW", so you can't miss it! After clicking, you will be redirected to the form that every candidate needs to fill out. If you have someone in mind to nominate, it's not enough to just nominate them; even nominees need to answer the questions that are crucial for us when evaluating all applications during Q1. The application process remains open until 9 January 2026, and the new class for the following year will be announced at the beginning of March 2026. Good luck to all applicants, and please share this update with your amazing community so that ev

I created this guide a two months ago when VBR 13.0 was release, but only in portuguese in my blog, so I thought I could translate and post here too. :)With the new version 13 of Veeam Backup & Replication, in addition to the new Linux version, new features have also emerged. One of them is the ability to perform Instant Recovery directly to Azure. In previous versions, it was only possible to perform Instant Recovery to vSphere, Hyper-V, or Nutanix, but now we can also restore backups using the Instant Recovery process to Azure. Prerequisites and Limitations Creating the Helper Appliance Template Running Instant Recovery Prerequisites and Limitations As always, there are a few prerequisites for IR to Azure to function correctly. These are:The types of backups supported by IR for Azure are: vSphere backups; Hyper-V backups; Backups of VMs or Physical Machines created with Veeam Agent for Windows or Linux; Nutanix Backups EC2 backups created by Veeam Backup for AWS Azure VM bac

What’s the root password on the VSA?

I was asked this week what some of the prompts we are seeing in the field for Veeam Intelligence are. Many people, including myself, have demonstrated asking how-to questions and responding in their native languages.So I wanted to put out there…What questions have you asked Veeam Intelligence on premises and in Veeam Data Cloud? Let me know what you asked and what kind of response you received. You might make it in my next blog post 😉

Hey there, we need Offsite-Backups of our Unstructured Data. Since the Backup Files are roughly 3,5 TB in Size, its impossible to get that Data to the Site directly due to slow Internet Connections. So i first configured a Secondary Target NAS for the Backup Job Onsite to get that Backup Copy onto it. I then moved that NAS to the Offsite Location, changed it’s IP and added it back into Veeam as a new Repository. Did a Rescan of that new Repo and Veeam found the Backup Data and added it. I now added that new Repo to the secondary Target in the Veeam File Backup Job and removed the first one (which was the same NAS with the Onsite IP which is now invalid). I then restarted the actual Backup Job. It created some data, finished teh Job and the new Backup Copy Job started. But here’s the problem: It completely ignores the Backup Copy already in existence on that (now) Offsite NAS and instead starts creating a whole new Backup Copy. This is absolutely inacceptable. How can i tell Veeam, that

Attempts to back up a Wallix Access Manager virtual machine recently deployed at a customer's site on HyperV result in the following error:Processing Acces Manager V5 Error: VHDx:CVhdxDisk.InitialValidation: Incorrect bitmap entry type (PAYLOAD_BLOCK_ZERO): See [MS-VHDX-v1.00-20160128] specification section 3.4.1.2. Agent failed to process method {VHDX.GetDiskInformation}.I edit the virtual disk to made a conversion from vhdx to vhdx from Hyper-v panel, but it doesn’t work.Do you have any ideas on how to fix this problem?Many thanks,Morgan

Hi, I was using Veeam v12 on my server to backup my virtual machine on Windows Server. I got hacked with a Kraken v1.3 ransomware virus and all my files were encrypted. Most of the files on my backup drive also got encrypted, but the biggest and main backup of around 700GB seems to still have it's original extension. (the smaller files which i believe were incremental backups, are all encrypted) I setup a new server and installed Veeam v13. I tried to do a backup import of the main backup file, but then i receive an error:2025/12/10 10:14:39 Failed : Failed to import backup Error: Storage version [1390707963] is not supported for read-only access. Failed to open storage for read access. Storage: [cPanel_Server.a0c28163-3b23-47d4-a1e9-1f056bfD2025-11-27T230013_CC92.vbk]. 2025/12/10 10:14:39 Failed : Background operation job failed Error: Storage version [1390707963] is not supported for read-only access. Failed to open storage for read access. Storage: [cPanel_Server.a0c28163-3b23-47d4-

 Ever had your backups fail? I sure have! But it’s all part of the fun & games of learning exactly how these systems work.Recently I spun up another instance of Veeam Backup for Microsoft Azure, and as part of my security mindset, I configured some elements of hardening to my infrastructure. Well, I missed a setting that I’m going to share with you today. Worker Job Completed with Error So, I had Veeam Backup for Microsoft Azure working, my daily snapshot job was also running fine, but it was the daily backup that wasn’t working. Some of the key terms I could pick out from the logs were ‘Worker: <Resource Name> (IP Address:Port): job completed with error’, ‘Error: This request is not authorised to perform this operation’, ‘Status 403’, and ‘ErrorCode AuthorizationFailure’ were the error messages I was being greeted with. Dissecting the Errors The key hint here was the job task ‘Backing up <VM Name> to Backup Repository. Followed by the worker not being authorised.Within

I first of all installed Veeam v12.3 on an external drive then i uninstalled it. I then tried to install it on the hard drive of my PC, but this error popped up. I did some research and discovered it could be because of the last installation residues that could still be running in my PC. So i went on checking all the possible places where these residues could be (task anager, register,...) but still after trying to install it the same error pops up. So what can be the problem with this installation?  

In this post, I analyse the issues involved in backing up a VDI environment in a VMware vSphere environment with TPM enabled. The VMs being backed up are Windows 11 with Microsoft Office 365 licences.The configuration of Veeam for backing up encrypted VMs requires this architectural prerequisites:The backup proxy must be working in the Virtual appliance or Network transport mode: The backup proxy working in the Virtual appliance transport mode must be deployed on an encrypted VM. The backup proxy working in the Network transport mode uses the NBD protocol by default. If you want to use NBDSSL, select the Enable host to proxy traffic encryption in Network mode (NBDSSL) check box in the Transport Mode window. Note that traffic encryption puts more stress on the CPU of an ESXi host and can decrease performance. With this proxy configuration, we can perform consistent backups.For VM restoration, consider the following:If possible, use the "entire VM restore" option to the original locatio

In Veeam13 how we can move existing job to other repository?I try to edit the job and change the repository then when click next i got this prompt.In earlier version as i remember there are option to move or create new. 

Hello - I am running Veaam Backup and Replication V.12 and am attempting to configure email notifications using Microsoft 365 modern authentication. I authorized the connection via the MSFT 365 signin dialogue and when complete I can see the indicator that the token is valid, but when I send a test email I get a general exception error message (see screenshot). The error doesn’t give allot to go on, has anyone else seen this and can recommend a solution?  

Last week I had to troubleshoot a backup job that was using a brand new proxy and repository server. No other job was using these components. Nonetheless just 4 VMs were processed at the same time. All other VMs showed status “Pending”. As additional information, “Resource not ready: Active snapshots limit reached for datastore” was shown too in active job log.After a short investigation we found out, all VMs were located on just one VMFS datastore. Fortunately there is a rather simple solution for this limitation. You can create a registry key on VBR server to increase the limit of active snapshots per datastore:HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\MaxSnapshotsPerDatastore For more details see this forum posts:https://forums.veeam.com/vmware-vsphere-f24/active-snapshots-limit-reached-for-datastore-t19711.htmlNice detail: The change enters into force immediately – even the job is currently running!Keep in mind, this is a global setting!  

Hello,I’ve just installed Veeam B&R and VeeamOne (both version 13) on one physical Windows Server 2025.Was it mistake? Because I cannot configure and start Veeam Intelligent Diagnostics.The reason (not confirmed yet) is Veeam Analytics service.Description here: Veeam Intelligent Diagnostics - Veeam ONE User GuideI need two instances of this service, in Server mode for VeeamOne and in Client mode for B&R.Or VID can work without Veeam Analytics service, because this is within ONE physical server?I hope, someone has solved this already...Best regards,Tom

Hello,When using VDC Calcultor for Azure VM workloads, for a snapshot size of ~64.4 TB there is an associated snapshot cost (~$3,297) with a Bronze policy (1 per day for 7 days), I am missing clarity on how this cost is applied over time.More specifically, could you please clarify:1. Is this snapshot cost:- calculated per month,- per year,- or is it a cumulative cost based on retention (number of snapshots × retention duration)?2. Does the displayed cost already account for the 7‑day snapshot retention, or is it the cost of a single snapshot instance? Thank you for your clarificationBR

Disclaimer:I actually wanted to publish this post earlier, but I had a small health issue that delayed my plans a bit. In this post, I mainly want to share a few brief thoughts. There are already so many incredibly good and informative blog posts about the recent Veeam 100 Summit in Prague. Therefore, I will focus less on technical details (which cannot be fully shared anyway) and instead provide some impressions from my personal perspective and perception What is the V100 Summit?The Veeam 100 Summit takes place once a year and is now hosted at different locations on a rotating basis. This year, it was held in Prague – a truly beautiful city! Veeam invites all Veeam Vanguards, Veeam Legends, and VeeaMVPs to come together, network, and exchange ideas on the latest topics. In addition, a lot of information is shared that is not public, giving us, as members of this exclusive group, the opportunity to actively contribute to the development of Veeam products. Arrival:Luckily, my hometown o

HI..I create user account for myself in Enterprise Managerbut when i logon using my account why i got error ‘Cannot find backed up machines where the user belongs to Local Administrators group’ 

Recently, we discussed how to Upgrade from Any SQL Server Edition to SQL Server 2025. Here is also how to how to upgrade Microsoft SQL Server 2019 to 2022Before thinking of upgrading or installing SQL Server 2025, kindly refer to the following article “SQL Server 2025 Upgrade Requirements and Compatibility”. Not not deploy yet in Production. Even though Microsoft SQL Server 2025 is not yet officially supported by the Veeam Data Platform, this blog post is still important for several reasons: Early Awareness for IT Teams: With new releases, Microsoft SQL Server releases often trigger planning discussions long before official support is announced. This guide helps administrators understand what will eventually be required, reducing surprises when support arrives.Preparation for Future Upgrades: Many organisations operate on strict upgrade cycles. Even without official validation today, they need to forecast impacts, budget for upgrades, and prepare migration paths. This post gives them a