Community

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.

I’m getting the below error after upgrading Veeam servers from v12 to the latest release of v13. It’s a windows based install of Veeam, and it is connected to a (dedicated to Veeam only) AD domain.My user has local administrator permissions, Veeam Backup Administrator permissions, and MFA disabled for testing/troubleshooting purposes. The is happening across each of the Veeam v13 servers I have on the domain.It is only happening for mine and one other engineer’s user accounts, but other engineer’s accounts are not affected. We are all in the same AD groups so permissions are the same.I have tried removing Veeam Backup Administrator permissions from my account, rebooting, and re-adding, to no effect.Has anyone seen this before? Any suggestions for what else to check? In the meantime I have a case open with Veeam support, and hoping they can come up with something.

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

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 -

Instantly bucket size is increasing. What could be the issue? What is the best practice to follow here? My concern is GCP storage.

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.

 ...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

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

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

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 ar

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 & Firewall

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 n

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:

We have a few clients that have a single physical server and have a service or application that is already using port 443.  So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used and v13 uses it for the Veeam Web Service.  Assuming we can temporarily disable this service/app to get the upgrade to complete, is there a way once v13 is installed to get the Veeam Web Service to use a different port?

 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

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 sti

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 | bash

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 V

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 repos