Community

What’s the root password on the VSA?

When we enable MFA, then all users is forced to use MFA. In case we need do execute script by powershell, how we can exclude so the powershell script still can operate normally?

Hi Community,If you are going to take the Veeam Backup & Replication v13.0.1 ILT course, then it's important that you take the recommended free courses.Check my blog for ways to access the recommended free courses.https://pulia.com.br/veeam-backup-replication-v13-0-1-course-experience-recommendations/Hope that help your learning!

Good afternoon everyone,I'm using the latest version, 13, but after restarting my server, I can no longer connect to the console. It shows an SSL error, "see inner exception," but I haven't been able to find them to get more information. Could you please help me?  

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.

Hi Community!!!During my time as a technical trainer and consultant, I constantly tried to draw analogies between the features we have in IT and the things we experience in our daily lives.Today I will draw an analogy between the wardrobe and SOBR.The idea behind using an analogy is to make technical topics easier to understand. Often, when explaining storage tiering, the listener gets confused, so I made a simple analogy with a wardrobe. This makes storage tiering easier to understand.In this analogy, you will have the opportunity to understand performance, capacity, and archive tiering in a very simple way.Check my blog to see the analogy, hope you enjoy it https://pulia.com.br/what-does-a-sobr-have-in-common-with-a-wardrobe/  

Hi Community, During Veeam Agent backup, you may see: Collecting recovery media files. Details: Windows recovery image file not found This means Windows Recovery Environment (WinRE) is missing or disabled. Solution: Work for me this morning.Run on target VM. reagentc /setreimage /path C:\Windows\System32\Recovery; reagentc /enable!--scriptorendfragment-->!--scriptorstartfragment--> Note: If WinRE files or the recovery partition are missing, you can ignore this warning backup is valid.(See diagram below for quick steps.)   

Hi, I’m running the most recent B&R CE version 13.0.1.180 and trying to create a recovery thumb drive.  I have tried multiple USB sticks and keep getting the same error:  Preparing USB disk Error: The system cannot find the path specified.   I know the USB sticks are good as they are new and I have tried multiple batches.  Anyone else experiencing this?

Hello  Can you connect a Veeam Infrastructure Appliance (VHR) hardened repository to Veeam Backup & Replication (VBR) which [(VBR) is running ver 12.3.2]i'm assuming is via SSH,  My question is three-fold is this at all possible?if possible which user account is recommend?Does this require su if sudo fails current user accounts veeamadmin veeamsvccreate new one? how do make new account sudo if veeamsvc where do you find single use password?Are there any KB or blog on todo do this?I know the simple answer is update VBR to version 13, this is work seamlessly.I’m looking at this from a backwards capability point of view . Thanks 

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?  

Hi,we backup our ad users with Veeam and had to restore some of them. So far no problem, the restore succeeded and user was back including the old password.The user could logon into computers, but he wouldn’t get any kerberos tickets. Only after a password change the behavior was completely normal.We couldn’t find any reason for this as only timestamps get changed with the user object. Any ideas why it istn’t working as expected?Thanks and happy holidays

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 pos

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 an

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, a

With Veeam Backup & Replication v13 and its implementation of SAML for authentication, we can use a lot of different IDPs. I already did a guide for entra id which you can find here: https://community.veeam.com/blogs-and-podcasts-57/vbr-v13-saml-implementation-guide-with-entra-id-11560 In my region, entra id is the IDP that is used at most companies. However, it is not recommended to add Veeam to your production active directory domain, so I would also say it is also not really recommended to add your Veeam to your production m365/entra id tenant or generally your main IDP. This guide provides some guidance to set up Veeam with Authentik as an SAML IDP. For those who never heard about Authentik: Authentik is a lightweight, open-source, self-hosted identity provider that offers

Hello everyone,What is the best practice to backup VMs on HPE Simplivity?

Hi,Where do you guys mostly download Yara rules for Veeam from?This GIT looks not maintained for years (files from 2022).  https://github.com/YARA-Rules/rules/archive/refs/heads/master.zipI also used those links but I had some troubles when scanning backup.https://github.com/Neo23x0/signature-base/archive/refs/heads/master.ziphttps://yaraify.abuse.ch/yarahub/yaraify-rules.zip

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 fai

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

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 absolu

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-

 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 AuthorizationFailur

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: