Blogs and Podcasts

With Veeam Backup & Replication v13, we’re not only getting a new version number and plenty of new features — we’re also seeing a deliberate clean-up of the product: some capabilities are now deprecated (no longer available for new configurations), while others have been discontinued (removed completely). That’s not unusual for a major release, but in practice it can affect the areas where environments have “organically” grown over many years: job designs, repository settings, restore habits, and legacy workflows that somehow always worked.So this article is not an upgrade how-to. Instead, it focuses specifically on these features: What changes? What did the feature do? Why might you still run into it operationally? And what’s the modern path forward? I’ll go through each deprecated and discontinued feature, outline the impact, and share practical recommendations—so you don’t find out only when creating a new job or during an actual recovery that: „Wait… this isn’t available anymor

Hi there,After the first part of this topic, now is time to jump into the good stuff, the main thing here is to be notified every time something changes or goes "wrong".Lets follow u the screenshots, from Setup, to Notifications setup, to finally monitor a couple servers and services.As I said before, this is basic "alive" monitoring, not statistics and deep monitoring, there are other cool tools for that, the topic here is first line, quick and easy! lets go:This is my Uptime-Kuma Dashboard, after install, lets go to Settings, click on your name up right, and click settings, under Settings, we will find an easy and clear menu to config the tool, from appearance to proxy, etc. Im going to deep dive into the Notifications menu:Click on Setup Notification Now, let's check it out, in the main menu, at the very bottom, we have the option to monitor TLS certificates and Domains expiracy, this is awesome! Im super happy Im not missing a cert renovation anymore, and no entries into my calenda

Hi Everyone, Last Tuesday I was lucky enough to attend VeeamON in NYC. This time I had to be on the best Burke behavior since I would be at the bar. Before you are shocked, this was the experts bar so no worries about Geoff’s infamously bad bartending skills for those who might have heard about them.I flew into Kennedy airport on an extra early flight to make sure that nothing went wrong. Flights and airports are not immutable unlike good backups so you never know when they will hit you with Delayware or even worse Cancelware! Flying in over the city I saw down below the Verrazzano bridge and it occurred to me that I had never seen it up close. I packed light (Vanguard Backpack!) so took the subway to Bay Ridge station in Brooklyn. Since joining marketing I have changed from the introvert, photo shy personality to a more extravert nature and I am always thinking of that perfect marketing shot (which can then be lowered somewhat in quality by my selfie!).Verrazzano Bridge​​​ Landed and

If the backup jobs fail and show an error message is “Unable to allocate processing resources. Error: Unable to find Hyper-V hosts where VM 'xxxx-xxxx-xxxx-xxxx-xxxx' is registered: Failed to connect to Hyper-V Integration Service on host, port 6163”. I tried to review the settings, and all of them look fine, but the backup jobs failed always. I have run into these issues sometimes, it’s easy to solve, you just need to reboot the Veeam management server or restart the Veeam services of the Veeam management server.

While upgrading to Veeam Backup for Microsoft 365 8.4, you might notice the following message: Connection to PostgreSQL is not encrypted. Enable TLS in PostgreSQL for secure communication.  VB365 checks whether the connection to the PostgreSQL database uses TLS.If TLS is not explicitly enabled, the warning is shown regardless of whether PostgreSQL is local or remote. If the PostgreSQL database is locally hosted on the vb365 server itself, this traffic does not leave the host. But if you have multiple proxies, those proxies also connect to the database, and this traffic leaves the network. So in those scenarios, it might be good to have this traffic encrypted. I will describe here how you can enable this traffic to be encrypted. Step 1 - backup config filesOn all hosts (vb365 server and proxies), back up the following files:C:\ProgramData\Veeam\Backup365\config.xmlC:\ProgramData\Veeam\Backup365\proxy.xmlC:\Program Files\PostgreSQL\<YOUR POSTGRESQL VERSION>\data\postgresql.confC:\P

 I ran into a situation recently where one of our VSPC servers stopped working after a Windows patch update. The portal was dead. I went ahead and upgraded to VSPC 9.2 and that brought everything back online. Except the April license usage report never got generated. It was stuck. I could not finalize it or submit it. If you are using VCSP /w rental licensing, you know that the report has to go to Veeam every month. A missing one is not something you can just ignore (Not for lack of trying 😊). I opened a support case and Veeam Support gave me a procedure to regenerate the report. It worked. I am documenting it here because I could not find this written up anywhere and I know other providers might encounter something similar. Step 1. Back up the VSPC SQL database.Take a fresh backup of the VSPC database first. Veeam covers this in KB1471. If the SQL work later goes bad you want something clean to restore. Step 2. Update the configuration overrides file.Open this file on your VSPC serve

 VBR v13 defaults to PostgreSQL for new installs, so for a lot of environments the question is no longer “Should we care about PostgreSQL?” It is “When do we move, and what do we need to fix after we do?”If you are still running SQL Express, the answer is usually sooner than later. If you are running a licensed SQL Server only because VBR needs it, there is a good chance you are carrying cost and patching overhead you no longer need. And if you already migrated but the console feels slower than it used to, that is usually not because PostgreSQL is a bad fit. It is because the default PostgreSQL settings are conservative and generic, while VBR is not.This is the part people miss. The migration itself is usually the easy piece. The performance conversation starts after the restore, not before it. First question: do you actually need to migrate now? Not every environment needs to sprint into this.If you are on SQL Express and comfortably below the 10 GB limit, there is no emergency. It st

Field Experience — When the Human Link Becomes the Missing LinkBy a cybersecurity consultant, from the field.The Day Everything Stopped… Without a CyberattackImagine the scene.No ransomware. No server failure. No fire in the server room. And yet, an entire company's information system finds itself in total disarray.The cause? Two simultaneous, extended sick leaves. The only two people who made up the internal IT department.This is exactly the scenario I discovered when I arrived at this client's site. A scenario that nobody had anticipated, that nobody had recorded in a risk register, and which nevertheless caused an operational paralysis as severe as a major cyberattack. A Deafening Digital SilenceWithin the first few hours of my assignment, the situation was alarming:No more daily IT infrastructure management: no monitoring, no updates, no ticket handling. Zero visibility on backup status: Are the jobs still running? When did someone last check them? Are the storage media healthy? No

Migration from VMware vSphere to HPE HVM with Veeam As organizations modernize their infrastructure strategies and reduce dependence on legacy virtualization platforms, many are evaluating alternatives to VMware vSphere that preserve operational continuity, performance, and data protection. HPE Morpheus Software VM Essentials, combined with Veeam Backup & Replication, delivers a validated and enterprise‑ready path to migrate workloads with confidence, minimal risk, and a clearly defined rollback strategy. This guide describes migration from VMware vSphere to HPE VM Essentials leveraging Veeam Backup & Replication to move workloads to HVM clusters (HPE’s hypervisor). Fundamental to this joint solution is the Veeam Plug‑In for Morpheus VM Essentials, which provides agentless, host‑level backup and recovery operations for HPE HVM. This plug‑in allows Veeam to work directly with Morpheus infrastructure, ensuring that virtual machines can be seamlessly protected with Veeam after mig

Upgrading Veeam Backup for Microsoft 365 - From 8.3.0.2201 Ver  to Ver  8.4.0.1457

Hi team,Following a Veeam Backup & Replication upgrade to v13 for a client using Hyper-V, we started encountering random failures on backup and replication tasks with this error:Failed to process replication task Error: the socket was closedWe ran through extensive troubleshooting: verified antivirus exclusions, analyzed network traffic, checked firewall rules, validated storage connectivity, etc., but nothing pointed to a clear cause. After several exchanges with Veeam Support, we finally tracked it down.The VBR Windows services had been configured to run under a local service account instead of the built-in Local System account. Once we switched all relevant Veeam services to run under Local System, the random socket errors completely disappeared.I’m not entirely sure if this is tied to stricter authentication, TLS negotiation changes, or other security enhancements introduced in v13, but it’s definitely worth keeping in mind during upgrades or fresh installs.Hope this saves some

If you want to take your Veeam career to the next level, you can rely on Veeam’s education platform, Veeam University Pro.I’ve just enrolled in the Veeam Recovery Orchestrator Essentials course, and here are my first impressions.  There are three tabs on the left side: the Path tab, where you can navigate through the lessons; the Learners tab, where you can see the members; and the Discuss tab, where you can post questions to be answered by the expert team. This means you’ll be assisted by a real person.The platform is easy to use. You simply click on the desired lesson and watch the video. The videos are high quality, and the trainer speaks very clearly.Subtitles and full-screen mode are also available.  You can view and download the transcript.I’m enjoying it so far! I highly recommend taking this training course.After the lesson, you will be asked a question to test your understanding.​@Federica ​@NikolaPejkova 

 Veeam Data Platform v13 is one of the most significant releases in Veeam’s history. It introduces major advancements in security, AI-driven threat detection, cloud recovery, performance, and operational simplicity. Rather than being just another upgrade, v13 positions Veeam as a true cyber-resilience platform, helping organizations detect threats, protect backup data, and recover cleanly and confidently.In this blog, we’ll cover two key areas:What’s new in Veeam v13 and the features worth getting excited about A complete Veeam v13 Adoption Playbook — phases, risks, and best practices for rolling out the new platform What’s New in Veeam Data Platform v13Veeam v13 brings major enhancements across security, cloud recovery, performance, observability, and platform flexibility. Below are the most impactful additions. 1. Security-First DesignAI-Driven Threat DetectionVeeam’s Recon Scanner 3.0 and new Malware Analysis AI Agent provide real-time visibility into suspicious activity — including

I have recently noticed a trend with a few of the service providers that I support. I am having a lot more conversations around Veeam Data Cloud Backup for Salesforce. And it’s not just conversations; it’s demos and POCs that are turning into closed opportunities. I started to do some research on the uptick of attacks against Salesforce. I found that large-scale campaigns over the past 12–18 months have been accelerating, as reported by Security Week. While Salesforce itself is highly secure from a platform standpoint, attackers are no longer trying to come in through the front door.This got me thinking, and I asked myself: why is Salesforce an attractive target for bad actors?Salesforce contains high-value CRM data such as customer data, deals, and PII (names, emails, phone numbers), revenue data (opportunities, pipeline, contracts), business relationships (accounts, contacts, partners), integrated credentials (API keys, tokens, cloud access), and is highly connected via APIs and thir

EnvironmentSource MachineVMware vSphere 8VMwaware vCenter Server 8Microsoft MSSQL 2024 virtual machineTarget MachineMicrosoft Hyper-V 2022 ServerMigration ToolVeeam Data Platform v13Migration Path1. Back up the MSSQL VM2. Perform Instant Recovery of the MSSQL VM to the Hyper-V platform3. Migrate the data to the Hyper-V platform Backup the MSSQL VM Instant VM Recovery and Migration Select Instant recovery > Microsoft Hyper-VSelect the MSSQL VM, click Next.Select the target Hyper-V host, click Next.Select the Database, Click Next.Setup the network connection, click Next.Setup System UUID, click Next.Click Next.Click Next.Click Finish.You can test the MSSQL VM now.You can migrate the MSSQL VM to Hyper-V if there are no any issues.Enter the login credentials for Hyper-V, click OK. You can power on the MSSQL VM on Hyper-V now.Remark: A VMware Tools Error dialog appears indicating that VMware tools has encountered an unrecoverable error. Remember that the source MSSQL VM for this backup h

 Working with tape backup infrastructure is very different from working with disk repositories.When a disk fails, the symptoms are usually more direct. With tape, the same symptom can point to completely different root causes: media degradation, drive instability, robotics issues, firmware problems, SAS connectivity, or even logical inconsistencies.That’s what makes tape troubleshooting difficult.And in many cases, Veeam is only showing the consequence of the problem — not necessarily the root cause itself.This article focuses on advanced tape troubleshooting techniques using ITDT, low-level tape commands, and real-world diagnostics in Veeam environments.The objective here is not to replace vendor support or official troubleshooting procedures. Ideally, these validations should always be performed together with the hardware vendor whenever possible.These tools do not replace vendor support.What they do provide is deeper visibility into tape environments, especially in situations where:

As more organizations move workloads to public cloud platforms, protecting those workloadsbecomes just as critical as protecting on-premises infrastructure. Veeam Backup for PublicCloud is a native, Azure-aware backup product that integrates directly with Microsoft Azurethrough the Veeam Service Provider Console (VSPC) and Veeam Backup & Replication. In this blog, I will walk through the complete, step-by-step process of configuring Azure VMbackups using Veeam Backup for Microsoft Azure from the Veeam Service Provider Console.This guide is written primarily for tenants, end users, and backup administrators who want apractical, hands-on understanding of how Azure backup works inside VSPC. PrerequisitesBefore you begin, make sure the following are in place:Access to the Veeam Service Provider Console (VSPC) with tenant credentials. An active Microsoft Azure subscription. A Global Administrator or Owner role on the Azure subscription — required to create the Microsoft Entra service pr

 Some days ago, I stumbled upon a great feature in the Veeam Calculator.A feature request I’ve had open by Veeam for several years has finally been implemented: a tool to create a port list, view it graphically, and export it –> is now called “Interactive Maps”There are various features, such as a port map, a server planner, and a source-to-target map with predefined Veeam Backup and infrastructure components and workloads.  AccessVeeam Interactive Maps are part of the Veeam Calculator.You can access Veeam Interactive Maps via the standard link for the Calculator, where you’ll find a new button.Link: https://www.veeam.com/calculators Port MapWith Port Map, you can select Veeam components and infrastructure/workloads to view a visual overview where you can click on connections to see which components are communicating with each other. You also receive a list of all required ports that need to be opened at the firewall.Just to see which components or workloads are communicating with e

So you’ve got a new storage system, Congratulation.Your old repository is on life support and needs to be replaced?Your backup data must move to a new location or infrastructure?Someone made a configuration mistake and now the data needs to be migrated, fixed, and possibly migrated back again? Well, welcome to the migration maze. I’ll be your tour guide. Please keep your hands inside the vehicle at all times. Veeam backup data is not a loose collection of files that you can simply copy over casually. It is a rather sensitive construct consisting of backup chains (full/incremental), metadata, retention logic, synthetic fulls, and possibly immutability/object lock — and it is of course out of question, that during the migration, RPO/RTO still need to be met. In this deep dive, we take a look at the most practical and supported ways to get Veeam backup data from one backup repository or SOBR extent to the other— along with pros/cons, limitations, and recommendations for large data volumes

My latest podcast is out and very appropriately I am sitting in Toronto airport all ready for the next IT adventure. In the last few years I have travelled a lot and one figures a few things out, eventually 😀.https://www.buzzsprout.com/2545760/episodes/19147232 Forgot to add music helps you survive the long hours of endless waiting and wondering. I have learned to get work done while being squeezed in a small seat or on minimal sleep, but nevertheless there are times when you just want your mind to wander around its imagination just like you are wandering the world in real life 😃  

Hi all,I attach the step by step procedure to perform a PostgreSQL Database upgrade. PostgreSQL: CVE-2025-1094: PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation KB4386: Upgrading the SQL Database Engine Software (Microsoft SQL Server or PostgreSQL) Used by Veeam Backup & Replication Ensure that there are no jobs or restore tasks occurring. Manually Create a Configuration Backup. (Optional) Create a backup of the Configuration Database. Stop and Disable all Jobs Stop all Veeam services on the Veeam Backup Server Upgrade the SQL database software. After the upgrade completes, restart the Veeam Backup ServerPostgreSQL Upgrade ProcedureEnsure all jobs, policies, and tasks are stopped, and those that are scheduled to run are disabled. Stop all Veeam-related services on the Veeam Backup Server. Get-Service Veeam* | Stop-Service -ForceDownload the latest version of PostgreSQL that is compatible with Veeam Backup & Replication.Note: The mo

Happy Monday, Veeam community!  I am here again with fresh April Vanguard Newsletter packed with tons of veeamazing content from our community heroes! This month’s set clusters around Veeam v13 adoption, cyber‑resilience controls, recoverability/DR orchestration, and practical operational learnings (what breaks, how to fix it, and how to design for it). A smaller thread covers community/career wellbeing and monitoring/observability integrations. ​@Chris.Childerhose - Mastering Veeam Backup Replication V13 Book – Published - https://just-virtualization.tech/posts/mastering-veeam-backup-replication-v13-book-published/ ​@Iams3le - [World Backup Day] V13 Upgrade Failure: Veeam Configuration Backup Saved the Day - https://techdirectarchive.com/2026/04/04/world-backup-day-v13-upgrade-failure-veeam-configuration-backup-saved-the-day/ How to protect Microsoft 365 beyond native limits with VDC [Part 1] - https://techdirectarchive.com/2026/04/29/how-to-protect-microsoft-365-beyond-native-limits-

 Many organizations take comfort in seeing green checkmarks in Veeam Backup & Replication. Backup jobs complete successfully, backup copies are immutable, and the 3-2-1-1-0 rule or even the 3-2-1-2-0 (see From Backup to Cyber Resilience | Veeam Community Resource Hub) is fully implemented.Everything appears to be under control.But there is one critical question that often remains unanswered:Can you actually restore your systems when disaster strikes?This is what I call the Recovery Gap: the difference between having successful backups and having proven recovery readiness.Backup Success vs. Recovery ReadinessA successful backup confirms only one thing:Data was successfully written to storage.What it does not guarantee is that:Virtual machines will boot correctly Applications will start successfully Databases are transactionally consistent Dependencies such as DNS and Active Directory are available Recovery objectives can be achieved within the required timeframeIn other words:Backup

I'm really happy to share with the Veeam Community the release of vScan 2.0, a complete rebuild of the vulnerability scanner for Veeam Backup & Replication.For those who don't know vScan, you can check the original post here: vScan v1 – Vulnerability Assessment in your Veeam BackupsSince the v1 release, I received amazing feedback from the community (thank you all!) and many feature requests. Instead of patching v1, I decided to rebuild the entire application from scratch with a completely new architecture, new features, and addressing all the questions and requests from the community. What Changed from v1 to v2?Everything. Here's a quick comparison:  v1 v2 VBR Connection PowerShell Module REST API (native HTTP) Requires VBR Console Yes No Installer Size ~200MB ~15MB RAM Usage ~400MB ~80MB Antivirus False Positives Frequent (Chromium) None Scanner Engines Trivy, Grype Trivy, Grype, Jadi Vulnerability Tracking Per-scan only Full lifecycle manag

 Microsoft protects its cloud services like any other cloud and service provider worldwide. One of its Quality of Service protection mechanisms is API throttling, which helps prevent overload and ensures service quality for all customers. These limits affect all backup solutions based on the Microsoft Graph API, which naturally aim to achieve maximum backup throughput. Veeam Backup for Microsoft 365 and Veeam Data Cloud (VDC) must also operate within Microsoft’s technological constraints for backup. Since Microsoft recently actively removed the former workaround (multiple app registrations to bypass the limits) as of March 1, 2026, backup vendors are facing new challenges. See: Support Statement – Microsoft 365 Changes to Throttling Enforcement (24.2.2026) In this article, I explain Microsoft’s throttling mechanism, the former workaround using multiple registered applications, the impact of the new Microsoft policy, and I take a look at the future of M365 backup — because Veeam has alr