Recently active topics

🚀 Exciting news for Service Providers!Veeam Service Provider Console (VSPC) v9 just dropped, and it comes packed with some really cool new features. Over the past few days, I’ve been digging into one in particular—REST API proxying—and wanted to share what I’ve discovered, plus a small demo script that shows just how powerful this feature can be. So, what’s REST API proxying?Simply put, VSPC can now use a single API token to authenticate itself and then proxy requests to all your remotely managed Veeam products. That means you can manage everything from one central console without juggling multiple keys or credentials. A note on securityBecause a single API key can reach all your servers, it’s super important to keep it safe. Treat it like gold. 😄 When you create an API key, you can also enable “read-only access.” This applies not only to calls against VSPC itself but also to all proxied requests to your Veeam servers. If you’re just pulling information (like in my demo), enabling re

If you’ve ever had to deal with the pain that comes after deploying the Veeam Virtual Appliance (VSA) v13 with the following error message as discussed in the KB4648. Then I have got you covered.As you can see, below is the error message (Authentication failed). You will get when you use the “veeamso” or the “veeamadmin” account to login In this guide, I have detailed the steps to Fix Authentication failed: Invalid credential after installing VSA. The fix requires downloading a small Linux Live ISO such as the Ubuntu Live Server or Debian Live from this link. You could also use the ISO with the generic image with (Unabhängig davon, welche ISO verwendet wurde).download,, upload and attach as CD/DVD. To fix this, boot from a Linux live ISO and mount the Veeam appliance disk to access and edit the /etc/sssd/sssd.conf file. To proceed, hit the Enter button on your keyboard.Feel free to have the right settings that works for your environment entered. You can see the image below for similar

Backup Job using Storage Snapshot Unable to Find Ontap SnapMirror Relationship for Secondary Target. Backup finished with Warning: Cannot find any relevant ONTAP SnapMirror and SnapVault relationships   Storage Replication between the Source and Target destinations is working. I was looking at the job log and saw that Veeam was able to identify Primary SnapProtections.   There were lines showing WARNING: Replication of all disk snapshots of vm asdasdfasf is not possible for ‘Snapshot Replication’. Thanks again for your input as to possible reasons why this is happening.  

V13 - The environment described in this architecture is one main datacenter containing 1,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of used storage space. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will target a local Pure Storage FlashBlade\\S 100object storage array and a secondary copy will be sent to Veeam Data Cloud Vault. The Veeam Infrastructure Appliance that host the proxy/gateway server(s) are installed in VMs and use the virtual appliance (hot add) backup method.

Greetings friends! I have seen this question popping up since VSA was released. How do we monitor VSA, or any other hardened appliance? There is a clear announcement about support for things like this, bear this in mind before you continue. Grafana Dashboard for Veeam Software Appliance (Unofficial + unsupported)When you finish this article, if you follow all the steps, you should have something similar to this. It might be different according to your environment, number of days you select, etc.Dashboard – SummaryUptime and Latest Data Collection – Two main widgets that will show us if everything is alright. Appliance Information Table – Another great set of information, including Hostname, version, RAM, etc. SWAP is dynamic, if you have anything more than 0% colors will change. CPU Usage – Always good to keep a good track of the CPU usage, the query is granular and shows the effort and pressure per Core RAM Usage – Bit simple, just showing the % of RAM used. Query can be modified to s

ciao! Non so come siano le vostre esperienze ma tutte le volte che, da cliente o consulente, ho avuto a che fare con le appliance di deduplica mi è sembrato che sia… masochismo 😂Scherzi a parte, visti i costi e i problemi che finiscono per creare spesso, credo che certi hardware siano molto spinti dai vendor proprio perché costano molto le licenze. Che è quello su cui fanno margine. Che ne pensate?https://blog.tinivelli.com/beware-of-dedupe-appliances-63630a8d437f

Ciao a tutti,domani si svolgerà l’ultimo (credo) evento ufficiale Veeam Italia in presenza di questo 2025.https://go.veeam.com/veeam-unplugged-italySpero che qualcuno di voi sia presente, approfittiamone per un pò di sano networking, e portiamo avanti la nostra splendida Community VUG Italia! 💚

I need to migrate multiple VMs from the old vCenter to the new one and want to keep the existing Veeam backup chain. Is there an easier method than the Veeam VM Migrator Utility?

IntroductionMITRE ATT&CK v18, released in October 2025, introduces a major change in detection guidance. Two new objects, Detection Strategies and Analytics, replace the old single-sentence detection notes with structured, behavior-focused logic.In previous versions, detection tips were just short text inside each technique. Detection Strategies describe what behavior to look for, and Analytics show how to detect it on specific platforms. Each Analytic then guides you to relevant Log Sources and Data Components. What This Means for DefendersThis modular structure reflects how attacks develop not as individual warning messages, but as a chain of observable behaviors. Defenders can now track detection logic across different levels, systems, and data sources. The new detection model provides a clearer link between techniques, behaviors, and the necessary telemetry to identify them. Let’s look at the Detection Strategy DET0088 “Backup Software Discovery via CLI, Registry, and Process I

Hi Veeam Community,I’m running into a critical issue with my backups and need help.Error Details:Unable to apply retention policy: failed to delete backup filesError: Failed to call RPC function 'FcIsExists': The specified network name is no longer available.Environment:Veeam Backup & Replication: v12.3.2.3617 Backup Repository: NAS OS: Windows 10What I’ve tried:Deleted ~300GB of old backup files to free up space. Verified repository free space. Restarted Veeam services and checked network connectivity.Despite this, all backups are failing. The error seems tied to retention policy cleanup and possibly network access to the NAS.

Good afternoon, all!My customer is at the very front edge of a complete virtualization refresh - hardware, software, virtualization platform, the whole picture.We’re currently using Veeam B&R and VeeamONE to support our VMware stack, with an onsite performance layer and a cloud storage tier for long-term archiving.If we moved to Hyper-V or Nutanix, would we be able to retain our VMware-based backups for file and data recovery or would we need to repatriate and convert?Thanks!

Hello everyone, I am sharing the migration of the Enterprise Manager database from Microsoft SQL to PostgreSQL.https://www.veeam.com/kb4409Part 1: Back up the Current Veeam Backup Enterprise Manager Database    Open an Administrative Command Prompt cmdcd  "C:\Program Files\Veeam\Backup and Replication\Enterprise Manager"Using the Enterprise Manager Database Migration Utility, create a Backup of the current Veeam Backup Enterprise Manager database.https://helpcenter.veeam.com/docs/backup/em/em_db_migration.html?ver=120Veeam.EM.DB.Migration.exe /file:"C:\Temp\BEMConf.emco" /backupemdatabase /encryptionpassword:1l0v3KB5 /encryptionhint:bestpasseverPart 2: Restore the Enterprise Manager Database Backup to PostgreSQL    Using the Enterprise Manager Database Migration Utility, restore the backup created in Step 3 to the destination PostgreSQL server.Veeam.EM.DB.Migration.exe /file:"C:\Temp\BEMConf.emco" /restoreemdatabase /encryptionpassword:1l0v3KB5 /servername:localhost /initialcatalog:Vee

One of our client  needs to transfer their VBM 365 backup data from the current S3 bucket in their AWS backup account to a new S3 bucket in a different AWS account for security and compliance reasons. This operation should be seamless, ensuring no disruption to the current backup configurations. It must retain all historical backup data and restore points, resuming the backup operation from where it left off before the migration to the new S3 repository. Is it possible to achieve this, by adding new s3 bucket to VMS65 And then pointing to new repository? or using a Backup copy job then removing the old S3 bucket ? 

Dear Veeam Experts,One of our customers is facing an issue with the MSSQL plugin backup failing. Upon verification, I noticed that the backup data is being written successfully, but the job fails with the error “Starting Retention Policy Task.”In this setup, the retention policy is configured for 6 days per backup file. However, I observed that some files are not expiring as per the defined retention policy.Kindly help us with the steps or guidance to resolve this issue.Best regards,G Venkata Sai Kumar

​I’ve been using Veeam with IBM storage snapshots for quite a while now, and it’s been excellent. The integration works smoothly and gives you a lot of flexibility in how you want to configure things. One option is to let Veeam handle the snapshot orchestration and leave snapshots behind for a set amount of time. The other is to use IBM’s Safeguarded Copy feature, which gives you immutable snapshots controlled directly by the SAN. Because this is policy based and includes SAN Replication Policies, I opted for this option to have my production data in a second site, with Safeguarded copies there as well.Each snapshot can be browsed in Veeam, where you can see the virtual machines inside, and even use them for SureBackup jobs or lab environments that mirror production. Having snapshots that are only a few minutes behind production means your test or DEV environments are never out of sync. The ability to snapshot a PB of data ever hour is also quite impressive as a 1 hour backup window is

Hi there:After months of thinking, I took the step to switch my lab to Proxmox,I’ve been a Vmware «guy» for many years, but I knew the time came to give it a try, after many companies switching to it.I decided to re-use the hardware I had from previous projects, to see the capabilities and «how tiny» the setup could be.Here we go:The hardware Im using is the following3 x Zima Board – 8GB RAM, Intel Celeron 4 Core 3 x SSD 240GB (OS) 3 x SSD 480GB (Storage) 1 x Managed 1Gbps 8p Switch (HPE Office Connect) Ethernet cablesThis hardware was laying around in my lab from previous projects,and now looks super cool!The electrical consumption is very low.Im monitoring it, but for now, 10W each node….. xDFew more pictures here:Cheers.https://lfconsulting.org/building-a-lab-with-proxmox-part-1-hw

Hi all,  Maybe I’m not understanding how the Backup Server calculation at https://www.veeam.com/calculators/simple/vbr/server is supposed to work, but seems to give inexplicable results. 1000 Workloads with 500 workloads per job (2 jobs) == 36 cores, 80 GB RAM 99999 Workloads with 500 workloads per job (300 jobs) = 12 cores, 24 GB RAMLess extreme examples produce similar results, seems like we end up with kind of strange requirements no matter what values are added.

Parceiros tem acesso ao “Partner Coffee” com informações extremamente valiosas como as citações abaixo:  HA Veeam V13Obs: suporta de físico para virtual e vice-versa Scan com a V13 IVR para Azure:  Imutabilidade para GCPPerdi a tela, mas clientes de GCP vão ficar muito interessadosPorém encontrei na documentaçãoAbout Hardened Repository - User Guide  Até a próxima! 

I get the error “30.10.2025 09:52:47 Error    [veeam-infra.infra.local] Failed to synchronize update settings. Error: Cannot provide with host's certificates - PhysicalHost does not exist for host 'veeam-infra.infra.local'                             b4634265-9228-4a5e-9d95-2c12313e89c6”This server has already removed from veeam configuration. Powershell-command “get-vbrserver” does not return this server… How do I fix this? 

My Journey in Enterprise Data Protection and Veeam AdvocacyWith over two decades of experience in the technology sector, spanning mid-sized organizations to large enterprises, I’ve cultivated a deep expertise in IT infrastructure—particularly in data protection. While data protection has always been part of my toolkit, it was within the enterprise space that I truly honed it as a core focus. In 2019, our organization introduced Veeam as part of a strategic initiative to unify our data protection and Tier 3 storage teams. I was selected for a special project team to support this integration, marking a pivotal moment in our modernization efforts.Transitioning into the enterprise environment presented a steep learning curve, especially when managing protection at scale. I began in operations, where data protection was one of many responsibilities. In 2014, I formally joined the dedicated Data Protection Services (DPS) team. At the time, our approach relied heavily on storage replication a

Dear Community, Recently, I encountered an issue while running a scheduled backup job using Veeam Agent for Microsoft Windows. The backup failed with the error "Failed to create VSS snapshot."Successfully resolved the issue, and I’d like to share the steps I took in case they help. Solution That Worked:Simply by restarting the VSS (Volume Shadow Copy) service, which might have become unstable or stuck. Here’s what I did:Opened an Command Prompt (Run as Administrator)Ran the following commands:net stop vss net start vss You can also restart these services in services.msc:Volume Shadow Copy Microsoft Software Shadow Copy Provider That’s it! After this, I re-ran the backup job and it completed successfully without any errors. As a Veeam Community member, I truly appreciate the robustness of Veeam tools this issue highlighted the importance of VSS for reliable backups, and I hope this article helps others facing the same error; feel free to reply or DM me if you need further help happy to

Hi Community, I’m facing an issue where Veeam ONE Reporting Service (VeeamRSS.exe) cannot communicate with Veeam ONE Monitoring Service (VeeamDCS.exe). The error message states:  The Monitoring service appears to be stopped or inaccessible. Has anyone encountered this before? What could cause the Monitoring service to become unavailable? Any insights or best practices to resolve this would be greatly appreciated. Kindly note that support case already been open for this.