Community

Can we restore guest file level if the backup source is from tape? Or we must restore entire VM to the disk and then doing the FLR from disk?

Apologies if this is a frequently asked question, I’m very new to the topic of managing backup infrastructure.I’m currently facing the following issue:Server 1 is currently powered off and defective. According to users, there are important files that need to be extracted in some way. Server 1 was not centrally managed and instead had a standalone instance of Veeam Agent to run backups and copy backup files to NAS 1 NAS 1 holds a single full backup of Server 1 and is not managed via Veeam as a repository etc. NAS 1 and Server 1 are physically located at an external location with a very slow internet connection; this was the reason why the standalone agent approach was chosen in the first place Server 2 will host the restored files from the backup in the future and is managed centrallyWhat would be the best way to go about this restore process? My biggest issue is that I know how to restore files from existing centrally managed devices in our inventory but I have no idea what’s the “righ

Hello Guys, These days Im started to experience a lot of problems with Veeam, every now and then the Veeam Backup and Replication Application and the whole server gets stuck and i could not do anything until i restart it, even some backup jobs started to fail. When i restart it goes fine for a while and then it does it again, and for the jobs a sometimes i see that the service Veeam installer service is stuck so i have to delete it and try the job again and sometimes it works.Did anyone experience this kind of issues lately? I’m having hard time dealing with this and i will be happy with any kind of support.Note:  i started to experience this issue after upgrading to 13 Version.Thank you.

I am new with veeam and i build up a software appliance V13 on proxmox VE 9.1.4The appliance is running well and i can also use the veeam console from another PC to connect.The console i installed from the community iso last version.But now i have the problem with License of community version.Where can i find the license File for the community version of veeam?Downöoad or use of online licensing?Must i send a mail to become from veeam  the license file for community version.Without the license file for community version i can not test and learn more about veeam.Do you have a link for me to solve the problem?I hope you have a answer for a new beginner on veeam.

The other night, I had a weird dream. It wasn't one of those confusing dreams, but a clear vision of what our lives as backup administrators would be like in a few months. In the dream, Veeam's recent acquisitions — Securiti AI, Coveware and Object First — were no longer just logos on a slide, but a single living organism. The previews at the Veeam 100 Summit in Prague last November got me fired up to work even more. In the midst of all this confusion, I tried to bring some order, and this is what I 'saw' in my dream.(generated with Nano Banana)The evolution of the species: beyond simple recoveryRecently, us backup administrators have been talked a lot about recovery. "How secure are my backups?" How quickly can I get back online?" So, over the next few months, we'll be asking ourselves: "What am I recovering and where's the rest of it?"The deal with Securiti AI is going to change the game for Veeam. They're already top-notch when it comes to keeping data safe (backups and all), but th

Dear community, Let me take this opportunity to wish you a happy new year and all the best for 2026. 🎉 I hope that your year has got off to a great start, and I have a fantastic selection of Veeamazing content for you from the Veeam Vanguards. Scroll down to see the content that our Veeam experts published in December. 🤓 ​@AndrePulia  - What would prevent migrating from Veeam v12.3 to Veeam v13 - https://pulia.com.br/what-would-prevent-migrating-from-veeam-v12-3-to-veeam-v13/ Block Repository – DAS Using Internal Disks – Part II - https://pulia.com.br/block-repository-das-using-internal-disks-part-ii/ What does a SOBR have in common with a wardrobe? - https://pulia.com.br/what-does-a-sobr-have-in-common-with-a-wardrobe-2/  Veeam Backup & Replication v13.0.1 – Course experience recommendations - https://pulia.com.br/veeam-backup-replication-v13-0-1-course-experience-recommendations/​@AndreTheGiant  - Veeam beta support for HPE VM Essentials - https://vinfrastructure.it/2025/12/vee

VSPC from version 9.0 offers new option how to connect directly VBR and EM (not only via cloud gateways), which is via port 9999/tcp from VBR/VEM → VSPC I have added my Windows VBR, where is installed VEM as well Management Agent could run under local System account or under service account Server is after installation of management agent appeared twice as VBR and VEM is installed on this VM. In License section is option to enable “”License Auto Update”Is not working, because VEM is managing license for VBR So for VEM is needed to skip pushing of license and let to handover this action to VSPC.Is it done over registry key - reboot is required. SkipLicensePush Type: REG_DWORD   Default value: 0   Description: prevents Enterprise manager from pushing the license to B&R server ([HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup Reporting])  After reboot of that server could be enabled License Auto Update 

Hello, everyone!! Today is a special day. I passed the VMCE exam. I want to thank the group for the tips and questions; they were fundamental for me. 💚🤗

I have a veeam V13 appliance under Proxmox VE 9.1I want use a smb share under Qnap NAS. The QNAP is not in a domain.The shares are working on windows PC and servers with the credentials.The same creditentials i use for connect to the share under the veeam console V13But when i want to use it as repository SMB share. I become this  Have anybody a solution to solve this. 

The ProblemLast week we were troubleshooting a Veeam Backup & Replication environment, where jobs were slowing down since some time.Looking at the jobs, the backup performance itself was quite good, but the processing of some VMs took longer then expected.The task log of those VMs showed that "Collecting disk files location data" was the cause; for some VMs it lasted 20 minutes, others were waiting for several hours.I first suspected a vCenter problem, as the debug logs showed timeouts and an unsupported API, but after patching and some restarts the problems persisted.The ResolutionDoing some research I’ve stumbled over an R&D forums digest from @Gostev from the year 2018 (Veeam Community Forums digest at that time ). And this one brought us in the right direction as Anton mentioned disk fragmentation as a pausible cause for this issue.I’ve opened up a Veeam support case just to be sure, before approaching the storage team, but later on our customer discovered some left-over s

15.01.2026 10:42:19.819]    <45> [000P]   Error (3)       at Veeam.Backup.VssProvider.CVssControl.WaitIndexComplete(IIndexingSession indexingSession, IStopSessionSync sessControl)[15.01.2026 10:42:19.819]    <45> [000P]   Error (3)       at Veeam.Backup.VssProvider.CVssControl.Index(IStopSessionSync sessControl, Guid jobId, String[] includeFolders, String[] excludeFolders, String outputDir)[15.01.2026 10:42:19.819]    <45> [000P]   Error (3)    Failed to call RPC function 'Vss.IndexGetState': Error code: 0x80004005. Failed to invoke func [IndexGetState]: Unspecified error. Could not copy host file [C:\Windows\TEMP\ifd4615.tmp] to guest [C:\Users\SXXXX\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00]. Could not check if guest [vm-1716606] file [C:\Users\SVCACC~2\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00] exists. Could not get item info [C:\Users\SXXXXX\AppData\Local\Temp\31acb312-7db4-4fb0-bee8-f9e3ab42bc00] in the guest [vm-1716606]. Could not in

Using Veeam Backup and Repliaction 12, and running a file backup, receiving the following error, “Error: Failed to connect to agent: ‘VeeamServerName’, EP ‘VeeamServer IP Address:2502’. The message received was  unexpected or badly formatted.

Backup made simple. Backup becomes child’s play with new Backup Agent — a fully managed, offsite backup solution built for Bare Metal servers based on Veeam Service Provider Console.In just minutes, you can automate daily incremental backups, and start to monitor everything from a centralized dashboard.⚡ Setup in under 10 minutes, and let daily automated backups run🔐 Incremental, encrypted and immutable retention💰 Free licence for the Agent — pay only for Object Storage (0,007 €/GiB/month exl. tax)Be safe with the simple, reliable, and predictable backup layer that doesn’t bloat your budget. https://www.ovhcloud.com/en-ie/storage-solutions/backup-agent/  Please reach out to me if you want to discuss more about this new product! I need feedback to drive and build our strategy around product based on Veeam Service Provider Console.

The database simply freezes and Veeam needs to be restarted. We discovered that disabling Offload for the current Service Provider completely stops the problem from occurring. VBR RAM/CPU resources remain without overload.The database loses communication, and as a solution, we need to restart the postgres service. Veeam Version 12.3.2.4165 PostgreSQL Version 15.14-1 We have implemented these changes so far: Set-VBRPSQLDatabaseServerLimitshttps://helpcenter.veeam.com/archive/backup/120/powershell/set-vbrpsqldatabaseserverlimits.html AV & FirewallRunning & Installing PostgreSQL On Native Windows - PostgreSQL wiki We discovered that disabling Offload for the current Service Provider completely stops the problem from occurring. Has anyone else experienced a similar problem? I still don't understand why Offload locks the database.I'm looking at the database level, searching for Buffer Maxwritten Clean alerts and the like. The workloads sent to the Service Provider are Always-On and

I wanted to let you know that the Hitachi Vantara Universal Storage API (USAPI) plugin that supports Veeam Backup & Replication V13 servers running on both Linux and Windows is generally available and posted on the Veeam downloads page (Veeam KB4191). This new plugin also supports immutable snapshots and works with Hitachi Vantara’s VSP One High End enterprise storage system.Here is the link to last year’s white paper on Hitachi Vantara and Veeam integration as a reminder of the plugin’s capabilities before this release.And here is a link to the hitachivantara.community.com blog I posted: https://community.hitachivantara.com/discussion/accelerating-cyber-resilience-whats-new-in-hitachi-vantara-veeam-usapi-plug-in-v22

Upgrading Veeam Backup & Replication v13 often fails during the "Component update" phase with the error “unable to deploy the Veeam Deployer service due to SSH credentials not specified”. Veeam generates Single-Use Credentials as temporary, ephemeral credentials to securely deploy and upgrade VHR components. Veeam requires Single-Use Credentials to meet modern security and compliance expectations. As mentioned above, this is because of the unavailable Single-Use Credentials (SUCs) at the time of the upgrade as shown below. Note: You cannot perform this upgrade over the ribbon or right-clicking on the VHR in the working area of the console. This will not work. This is similar to navigating to the main menu (hamburger menu) and selecting update (update components). This will also not work because we are yet to specify the SH credential. The FixTo fix this, we will have to navigate to the Backup Infrastructure, select the server and click on “Edit Server”. Here is a link to the origin

 Since a lot of blogposts have been written on this topic and various issues resolved, I will share the link to my blogpost “Upgrade Path and In-Place Upgrade for VBR v13 and Known Fixes”. The article walks through upgrading Veeam Backup & Replication (VBR) to version 13 (13.0.1) with a focus on real‑world experience, known issues, and practical fixes during the process. It’s based on both official guidance and community feedback.Key Sections & Takeaways 1. Pre‑Upgrade Checks Port Requirement: VBR v13’s REST/Web UI requires port 443; if it’s in use by another app, the VBR services will fail to bind and won’t start. 2. Supported In‑Place Upgrade Path You can only perform an in‑place upgrade to v13.0.1 from v12.3.1 (build 12.3.1.1139) or later. Older versions need to upgrade to an intermediate supported release first. A helpful upgrade path table shows recommended steps from older VBR versions up to v13.0.1. 3. Hardware & OS Requirements 64‑bit OS support (Windows Server 20

Hi All, Job type on Prod is forever forward incremental on Disk -  ReFS formatDR has a repo in XFS formatI’m setting up a new Veeam environment and using Cloud Connect to copy backups from Prod site to DR (single tenant / one client).On the Cloud Connect side, the XFS repository is assigned 100TB and the actual storage usage is only around 56TB.However, the Backup Copy Jobs keep reporting that the cloud repository quota is filling up / quota exceeded, even though there should be plenty of space available.As a workaround, I increased the tenant quota on cloud connect server from 100TB to 150TB, and after that the copy jobs started working normally again and has used like 130TB. But this doesn’t make sense because: The physical repo capacity is still 100TB Actual used space is still ~56TB Yet Veeam has used 130TB of space Has anyone seen this before? Thanks!

After Part 1 Pi-Hole and Part 2 DuckDNS, Now, Let´s install WireGuard - Part 3!to be full set,We are going to use this command, its awesome and prepared for raspberry pi, but also work with many distros and platforms, making the deployment super easy and smooth!Follow the screenshots!sudo curl -L https://install.pivpn.io | bashAs you can see here, we must select WireGuard!!Port! I leave the default one, to be opened later on in our router.Super Important! the script detected we have deployed in the same machine Pi-Hole, so say yes and continue.here, Important step, select DNS as shown, to be able to call our service via DuckDNS Subdomain and not Public IP Address!!Done!Now our server is full setup with PiHole, DuckDNS and Wireguard.Now we need a few adjustments in PiHole and create users in WireGuard.Important!The Server has not a fixed IP Address, I do assign an IP address on my DHCP, if you want to do so, please setup a fix IP address into the machine.Open your port on the router to

What happened to the Status column when viewing a backup job’s statistics?  After upgrading to version 13, I no longer see this column.  If a backup object fails, the job shows failed however you have to view each backup object in the job to see which one failed.  Prior to v.13, the status column would show which object failed. Was this intended in v.13 or am I missing it somewhere?  

I get this errors on one of my clients VBR. Fails when running the copy job to our Qnap NAS running Quts Hero, Immutable setup with Quobjects. When it fails we don’t have several copy jobs running at the same time.Any ideas of what i can try next to solve this?  

Hello!Following up on my previous post about V13 for Windows, I wanted to dive into something I mentioned there: the storage integration angle. Specifically, how Pure Storage's Fusion integration with Veeam changes the game for customers managing multiple FlashArrays.If you're running Pure Storage, this is relevant now. If you're evaluating storage platforms, this is worth understanding as a differentiator.The Problem: Single-Array Management at ScaleIf you're already using the Pure Storage FlashArray plug-in for Veeam, you know the value: snapshot-based backup orchestration, instant recovery from metadata-driven snapshots, offloading backup burden from ESXi hosts. It works.But the plug-in has always operated at the individual array level. You configure each FlashArray in Veeam, set up your jobs, manage your snapshots, all per array.For two or three arrays? Fine. For a significant fleet (dozens of arrays across multiple sites)? Operational overhead compounds fast.What Changes with Fusi

Moving nearly 360TB of backups is always interesting, but it becomes much more challenging when object lock and immutability are enabled and the repositories live in different cities. I wanted to share how I executed a large migration using only Veeam capabilities, while keeping performance high and the customer’s WAN usage low. Project background Our customer needed to migrate over 360TB of backups off an object storage platform that was being decommissioned. Both the source and target object repositories were located in separate datacenters in different cities, each reachable over the internet. It is worth noting that with object storage object re-use, the object storage usage was around 360TB, but the actual amount of restorable backup data was over 590TB. Key constraints:The customer did not want to use their limited internet bandwidth for such a large data move. Both source and target object repositories had object lock and immutability enabled, which ruled out many traditional ob

Hello Community!The Veeam Software Appliance grabbed all the headlines when V13 dropped, and rightfully so. But here's the thing: the Windows installable version received substantial upgrades that address real operational challenges. If you're running Veeam on Windows and thinking about when/how to adopt VSA, here's why your next move should be upgrading to V13 for Windows first.Why V13 Is DifferentEvery major version brings new features. Table stakes. V13 is different because it fundamentally modernizes the platform architecture in ways that affect your security posture, operational efficiency, and future flexibility.The case for adoption comes down to four things:Security debt reduction – RPC, WMI, and NTLM are attack vectors that have been exploited repeatedly. V13 eliminates them. Performance gains without hardware spend – 2x agent throughput and 30% CPU reduction from BLAKE3 hashing means you're unlocking capacity you already own. Operational complexity reduction – Fewer ports, si