Community

I have a problem with a baremetal restore with veaam freeware.Destination is a M2 hard disk.After complete restore and a reboot.. blue screen with this message:“Your device ran into a problem and needs to restart.Wie will restart for you.Stop code: INACCESSIBLE BOOT DEVICE. I have done a fresh installation of windows 11 (and kubuntu) without any problem so i think that my new M2 do not have hardware problem. A restore on a sata drive it’s OK (no problem) The dimension of the original drive and M2 is the same (256 giga).So how can i restore my drive? It is possible?Thank you…. 

I’ve been a long-time critic of Veeam’s lack of functionality and overall clunkiness compared to other software, mainly Acronis, but I am always looking for what situations any product might be best suited for, so I’m curious what everyone’s favorite things about Veeam are, especially if you migrated an environment to using Veeam from any other product, what product was it and what made Veeam the better choice?

Hi Community,In anticipation of #VeeamON2025, ​@Dynamic , ​@lukas.k, and I recorded a video where we share the story of how we met, our friendship,beer, our passion for #Veeam, and all the exciting developments in the IT-Universe and our lives since we first met at #VeeamON2024.We are excited to continue our journey and hope to meet as many of you as possible in person in San Diego this year.  

Good afternoon, just thought I’d ask the question alongside speaking with our FW MSP and Veeam themselves…I’m trailing Wasabi right now. So far, a backup copy job running for a couple of my smaller VMs is not even completing, and the speed is showing a 6MB/s doing its initial seed.I have a 1Gbps leased line and the VCC jobs for the same VM’s run at around 110MB/s. I very much doubt this is the difference between great value cloud object storage and a VCC partners inhouse infrastructure, but I suppose I need to ask now before I waste more time on this…Any insights? There is nothing on the Veeam server throttling this, the FW MSP has been asked and has said all wasabi endpoints are not subject to inspection so I am starting to wonder.TIA!

I have a physical Zabbix server, which I’ve added to a Veeam Protection Group in order to back it up. I'm backing it up using the "Linux Agent" backup type. Recently, during the backup process, the Zabbix agent on that server becomes unreachable.While the backup job is running, I receive continuous Telegram alerts indicating that all hosts in the infrastructure are unreachable. However, there are no actual issues in the environment — everything is functioning normally.When I check the Zabbix server itself during the backup, the zabbix_agentd service appears to be active (running). Once the backup job finishes, the agent becomes reachable again and everything returns to normal.I’ve been unable to find a solution to this issue anywhere. I would really appreciate any help or guidance on how to resolve this problem.Thank you in advance!

Our current VM farm is backed to a local Linux Immutable Repo and then BCJ to another Linux Immutable Repo in DR site. Both site are L2 connected with metro cluster formed on storage level.VBR server is installed on VM farm. What if: the production site is down, my VBR server is rebooted on DR site; while my primary backup repo and production VM farm is gone. During this period, I will leverage of resources on DR site and backup is still required before failback to production. I have to stop all existing backup policy and create new backup policy because backup path is changed?The initial backup during that moment will be incremental or full? (wondering because all backup file are there, but there are no LUN level replication before)Will the map backup function can help?

We need to have the earliest restore points, how can I safely delete the old restore points so that we can retain the last x restore points? Where can I have the old restore points automatically deleted?For backup jobFor Replication job 

Hi everyone,I’m currently in the process of setting up the Veeam Data Platform for the first time, and while the installation seemed to go smoothly at first, I’ve started running into some challenges during the configuration stage. I’m finding myself a little stuck when it comes to integrating Veeam with some of my existing backup solutions. I’m unsure if there’s a best practice or recommended approach for ensuring everything works seamlessly together.Additionally, as I work through the setup, I feel like I might be overlooking some important configuration settings that could be crucial for optimizing the platform’s performance. Are there any key steps or specific settings that I should pay closer attention to during the configuration process?Lastly, I’m curious if anyone here has faced similar challenges during their first deployment of the platform. What are some of the common issues that new users tend to run into, and how did you go about troubleshooting them?Thanks in advance!

I am starting a new blog series on interesting PowerShell commands for anything Veeam related.  I usually find useful information whether it be searching or via Support cases.The first one comes from a support case I worked on with Veeam for VB365 and a repository sync issue. This command allows you to change the owner (move) a repository from one proxy to another or to a proxy pool.You can check it out here - https://just-virtualization.tech/2025/04/01/powershell-tips-for-veeam-vb365-v8-1/ PowerShell Tips for Veeam – VB365 v8.1 I hope this blog post will be one of many that show the power of PowerShell when used with any of the Veeam product lines. Today, I will discuss a very cool feature that Support showed me: It allows you to move a VB365 repository from a single proxy to a proxy pool. While working on a support case with a repository that was not synchronizing, I got that fixed with Veeam Support’s help.During the process, we had to put the repository on a single proxy server as

Hi everyone,I have two Veeam proxy servers that max out their RAM (20GB) once or twice a week for about an hour. I’m trying to find out which jobs are running on the proxy at the time of the spike. I know the affected VM's name but need to identify the specific job running when memory usage is high.Proxy details:VMware VM With 20GB RAM (recently added 4GB, but still seeing spike)OS WindowsMax concurrent tasks: 16Is there a way to track this from the proxy server or within Veeam Backup & Replication? Any insights would be appreciated

Hey community, This week, I encountered an issue with AIX agent backups. I have several AIX servers running versions 7.2 and 7.3. The backup jobs start, but there's a significant delay before they actually begin—when they start at all. When they do, the throughput is extremely low, and some jobs run for over 20 hours. The most severe issues seem to occur on AIX 7.3.  To troubleshoot, I tried: Uninstalling and reinstalling the Veeam Agent Creating a new protection group to ensure fresh package deployment and a new XML file However, the issue persists.When the job starts, it returns the path to the log file, and upon reviewing the logs, I found that:Path/var/log/veeam/Backup/JOB-Backup/Session_20250402_160020_\{311f3273-44bf-476e-93ab-7e8f9a943b07\}/Agent.Source.logLog[02.04.2025 16:02:46.438] <53084711> fb | Estimation:[02.04.2025 16:02:46.438] <53084711> fb | Backup stats:[02.04.2025 16:02:46.438] <53084711> fb | Total counts: files [607165], dirs [60021], links[959

I'm in the process of migrating our hosts and VMs from vCenter 7 to 8, maintaining the same EVC and cluster layout. During this migration, I understand there is a risk of breaking the backup chains due to potential new MOREF IDs. Is there a way to preserve the backup chains? Our jobs are mapped using vSphere Tags.I will be carrying out this migration without powering off any VMs or hosts, and I want to ensure the backup chains continue without issues.If I go to each job and remap or re-browse the VM objects by tags, will this preserve the backup chain and retention? If the backup chain isn't preserved and a new full backup is required, will the retention policy continue from where it left off?

Veeam Backup & Replication version 12.3.1.1139 was recently released on March 19, 2025. This introduces some critical security patches, new features, and performance enhancements. This update strengthens system security and improves reliability, making it essential for all users to upgrade promptly. Please, see what others are saying about this and the release overview.https://community.veeam.com/cyber-security-space-95/cve-2025-23120-a-vulnerability-allowing-remote-code-execution-rce-by-authenticated-domain-users-10000 https://community.veeam.com/blogs-and-podcasts-57/veeam-backup-replication-version-12-3-1-1139-march-2025-release-overview-10008  Here is a guide on how to upgrade to Veeam 12.3.0 in order to use the Part 1 solution of this guidehttps://community.veeam.com/blogs-and-podcasts-57/step-by-step-guide-to-upgrading-veeam-backup-replication-to-version-12-3-9771Note: When using the Veeam Backup & Replication 12.3 deployment embedded within Veeam Recovery Orchestrator 7.

We've experienced backup corruption due to an unforeseen circumstance. I'm familiar with the scheduled health check and its flexibility, and I perform daily checks.The backup is not file share one.As I understand it, the health check is a diagnostic tool, not a repair function.My question is: Do we have any repair capabilities to recover from corrupted backups and interruptions? Are there any repair utilities for addressing unique error messages?  

Hi, I googled a lot, but couldn't find anything suitable. I have a test VM in a VMware Workstation17. I back up this VM (Win11 with TPM) with Veeam Agent for Windows (newest version). I would now like to bring this VM to the vCenter. What is the best way to do this? Do I have to install a Native Keyprovider in vCenter first? Or can I create a new VM Win11 in vCenter without disk, then attach the vmdk disk file?Thanks for your help!GreetingsNovell2

One of our customers recently renewed **Veeam Backup & Replication (VBR)** in December, but is now evaluating a migration of their **58 VMware host** infrastructure to **OpenShift Virtualization (OCP-V)**. We know that to back up workloads on OCP-V, **Veeam requires Kasten K10**, however, **there is no direct conversion strategy** between VBR and Kasten, which poses a challenge in licensing continuity.Veeam currently suggests purchasing **Kasten as a standalone solution**, without considering the prior investment in VBR. This opens the possibility for the customer to explore other solutions such as **Trilio, Veritas, or other backup vendors** with native integration into Kubernetes environments.The key question is: **Is Veeam willing to sustain VBR without offering a transition path to Kasten, risking customer non-renewal? Or, on the contrary, should you design a strategy that allows you to ensure recurring business of between 42 and 58 nodes with Kasten?**This case highlights the

I recently started playing around with Power Automate after a team member asked me to share the status of a daily backup job in a Teams chat. I tried to use Teams' "Get Channel Email" function, however it appears the organization has blocked that functionality. Perhaps they don't want channels filled with emails, and prefer us to use native alerting interfaces. I was left with the only option of using Power Automate, or "Workflows" in teams. I started with a simple template to forward emails to a chat, filtered it by subject line of that job's email report, and saved the workflow. This made me wonder what else Power Automate could be used for. Given my renewed goal to participate actively in the Veeam Community, I decided to start there. The Goals:Receive all notifications from the Veeam Community into a chat within Microsoft Teams Trim the content down to include only the user, and the message preview Removing the image at the top of each email Removing "Hi Tommy O'Shea," Removing a

 One of our customers is using Sophos Central with MDR (Managed Detection and Response) and recently added the "Back-up and Recovery" integration pack. This is an additional function that must be licensed accordingly!This means that it is now also possible to monitor and react to certain events within VBR using the Sophos Managed Service.Sean Simpson published the article Veeam Sophos Integration in the community in fall 2024. Among other things, this article deals with the advantages that are available with this solution.In this blog post, I will now look at the step-by-step deployment and show possible messages via email or from the Sophos Central Dashboard to give you an overview of the product.Under Veeam Backup & Replication integration, Sophos Central provides information on the scope and requirements. At Veeam, there is a corresponding white paper in the Resource Library under Sophos and Veeam Integration.  Licensing & activation by https://central.sophos.com/manage/over

We are running MSSQL Plugin on a Multi instance Windows Host and have setup the Full and Logs backups for the DB in different instances, Jobs seem to be working fine, but on the VBR console I see the jobs running and in the backup log I see the DBs but the “jobs” don't show different Instance names, there are 4 instances being backed up on this server. any help would be appreciated  

Hello Veeam Community,there is a problem to connect to our SP Console.When i use the URL we configured with our Cloud-Gateways vcc.xxxx.de and i validate the Certificate from the SP i get the Error: Connection to Cloud Provider cannot be established.Has anyone some ideas to solve this Problem?Thanks for help! 

Hello, Working for an MSP with a large amount of customers running B&R 12 (12.1, 12.2, and 12.3), all of our customer’s individual backup servers are having their available storage space taken up by a log text file in the below folder:C:\ProgramData\Veeam\ErrorMonitoring\veeam_error_log.txtThe file is consistently updated each minute with error messages pertaining to failed connection attempts, despite their being no issues with any jobs failing due to similar reasons: [2025-03-19 10:01:10] Errors detected in Veeam log: [2025-03-19 10:01:10] Error detected: 2024-09-23 18:41:13.3469 [ERROR ] 4908 [__10] TmBsCpJobsMonitor: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond; [2025-03-19 10:01:10] Error detected: 2024-09-23 18:41:13.3781 [ERROR ] 4908 [__10] DefaultCollector: System.Net.Sockets.SocketException (0x80004005): A connection attempt failed beca