Blogs and Podcasts

Yet another opportunity to highlight the importance of backing up data – whether business or personal – is that the backup system must be an integral part of the IT infrastructure, not just an afterthought.I have written this post in Italian to raise awareness among Italian companies once again.https://blog.luvisi.it/world-backup-day-5d09dc597519 ​@Madi.Cristil ​@safiya 

This article is geared towards the "backup admin" and how no one really wants that job, but someone has to do it. In my current role, in addition to my other responsibilities, I serve as the backup admin in our lab environment. Although it's not as stressful as past backup admin positions, I still need to standardize and have things in order in the event of a restore or server outage.Let’s be honest—nobody gets into backup and recovery because they’re chasing excitement.But somehow, backup environments still manage to create plenty of it:Failed jobs at 2AM Storage filling up unexpectedly Restore requests turning into investigations That one job that’s been “warning” for… way too long That’s not the kind of excitement you want. In Day 2 operations, the goal shifts. You’re no longer just getting backups running—you’re trying to make the entire system predictable, repeatable, and honestly… boring.Because in data protection:Boring means reliable.    Reliable means recoverable.    Recoverab

31.3 is “Backup Day” Why?Because next day is first of April? 😊 So, tidying up could resolve into unwanted deletion of your data, which could lead into surprise, after you find out that and this is not just as a joke😊It’s nightmare …In nowadays we are trying to keep our platforms, environments most resilient as possible from ransomware attacks.BUTWhat is worse than ransomware attack?Are you really prepared to cover all scenarios?Sometimes it could be even bug of your nightmare in vendors software/firmware, which is not the thing that you never think about.ANDCombination with ransomware attack? Admins have no clue what is correct.What happened?Customer found out that has infected VMs – all Windows and Linux/Unix Systems. Production was stopped. It did not take longer, and he discovered that ALL VMs are affected. NOW was time to find out, when it happened.They figured out that best date and time to restore them is 7 days back. It was disaster for customer to lose last seven days.Backup

  As long as backups are running, logs are about as popular as a dashcam: you see them, you know they’re there—and you hope you’ll never really need them. But the moment a job fails, a service stops unexpectedly, or the software “just starts acting weird,” logs become the only reliable witness. They show what happened, when it happened, how other components reacted — and often why something was triggered in the first place. In troubleshooting, a complete and properly retained log history often determines whether you can narrow down an outage or error within minutes— or whether you end up relying on assumptions, screenshots, and “it didn’t feel like it was like this before” statements. That’s why in this article we’ll look at: how to collect Veeam logs correctly (support-ready), which levers you have for retention and storage consumption (Windows registry keys, GUI settings, VEM, Best Practices), and how simple housekeeping can prevent a full log partition from slowing down operations .

Recently, ​@Madi.Cristil created a post asking members of the Veeam Community who have been "heroes" in performing their backup duties to share their stories. If you haven't yet seen her post, you can read it below:https://community.veeam.com/discussion-boards-66/backup-heroes-wanted-join-the-world-backup-day-contest-2026-12918?postid=90737#post90737World Backup Day is coming and, like they've done the past few years, Veeam is asking for the Community to share posts about how Veeam Data Platform has been used to meet a need at your organization, or even home!  My story isn't too extravagant, but it did meet a crucial need at my organization.We had an employee get terminated a while back for potentially suspect activity with a vendor. Upon being informed of this activity, senior administrators were tasked to look into any network accounts which could have access to our environment. After meticulously skimming through our Active Directory environment, we came across a couple accounts whi

  Three management modes at a glance.  Mode Managed In Best Fit Reality Check Standalone Local server Isolated hosts or segments without VBR reachability Easy to forget until restore day VBR-managed VBR console Most internal infrastructure teams Best default when central visibility matters VSPC-managed VSPC via tenant VBR Service provider and multi-tenant designs Adds tenant visibility and service-provider controls  Linux boxes still end up doing a lot of the jobs nobody wants to virtualize.File servers. Monitoring nodes. Database hosts. NTP servers. Application servers that got built once and never moved again. They are everywhere in Veeam environments, but the Linux Agent still gets less attention than the Windows one. That matters, because some of the things that are easy to gloss over on Windows become real design choices on Linux.This is the part that actually

Last week I attended my first RSAC in San Francisco. To say it was a great experience would be the understatement of the year.The conference is enormous, and you can tell just by walking around downtown as the streets were filled with people sporting their RSAC badges. I quietly slipped mine off whenever I ventured outside the convention center. Wearing it felt like broadcasting to the city: "I'm from out of town — please rob, scam, or at least aggressively inconvenience me." Better to blend in with the local hipster cyclists. More on that later.AI Everywhere (And I Mean Everywhere)AI dominated the conference floor. Nearly every booth referenced it, the street advertisements were themed around it, and by day two I half-expected to find an AI-powered fixture in the restroom. (In some parts of North America they call it a "restroom" — in Toronto we say "washroom." My theory is that in some locations companies work their employees so hard that the restroom is the only place they can hide

I recently wrote a blog about VSA HA Clustering, which you can find below (link to my site is below as well).Veeam VSA HA Cluster Setup With the release of Veeam Backup & Replication 13 there is a new feature that you can use to set up two nodes in an HA Cluster configuration for high availability.  I am going to outline the process below and keep in mind that you will need to have a VDP Premium license in order to do this as that is a hard requirement.  Now let’s look at HA Clustering with Veeam VSA.Configuring a Veeam VSA HA ClusterThe HA cluster configuration process involves two major phases: enabling the HA feature on both nodes via the Host Management Console, and then assembling the cluster through the Veeam Backup & Replication Console.Enable High Availability on Both Nodes via MGMT UIBefore the cluster can be assembled, the HA capability must be enabled on each Veeam Software Appliance independently through the Host Management Console (Web interface on port 10443).Acce

 Microsoft’s position on your Microsoft 365 data has not really changed: they keep the service running, but they do not give you backup in the way most admins mean it.Yes, deleted data may hang around for a while. Exchange has retention behavior. SharePoint and OneDrive have versioning. Teams data can still exist in awkward places even after it disappears from the user view. None of that gives you a real backup timeline, a clean point-in-time restore, or a recovery workflow you would want to bet an outage on.That is the gap Veeam Backup for Microsoft 365 fills, and v8 is not just another incremental release. The architecture changed enough that you need to think about deployment differently than you did in v7. Start with the big change: v8 is built around PostgreSQL If you are coming from v7, the first thing to understand is that SQLite is gone from the design that mattered before.Older builds used SQLite for the configuration database and for per-proxy cache data. In v8, that moves in

It was a holiday weekend here in Brazil, Carnival, and I was off when I got the call around noon.A client had been hit by a ransomware attack.The entry point was a phishing email that compromised a workstation. From there, the attacker managed to move laterally, reach Active Directory, and eventually gain access to the entire environment.By the time I was involved, most of the damage was already done.Around 50TB of Windows-based VMs were encrypted. Production was down.The environment did have antivirus in place, but it wasn’t properly configured to stop that kind of behavior. In the end, it wasn’t enough.  At that moment, the biggest challenge wasn’t just restoring the environment, it was figuring out when it had actually been compromised. Without that, choosing a restore point becomes a risk.You might bring everything back… already infected.That’s where Veeam Software made all the difference. It wasn’t a straight path, each restore point helped us understand how far the compromise had

In this article, I'll take you through five different restore scenarios I've tested in my lab, and you should do the same.You’ve got green checkmarks.Your jobs are running.Storage looks fine.Everything seems good.But here’s the uncomfortable truth I’ve learned the hard way:A successful backup job does not mean a successful recovery.Day 2 operations is where this really hits. This is the phase where you stop asking “Did it back up?” and start asking:“Can I actually get my data back when it matters?”If you’re not actively testing restores, you’re running on assumptions—and assumptions don’t survive outages, corruption, or ransomware.Here are five restore scenarios you should be testing regularly (but most people don’t). 1. Full VM Restore (The “Everything Is Gone” Scenario)This is the big one.The “we lost the entire server” moment.It sounds obvious, but a lot of environments never test a full VM restore end-to-end.What to validate:Can you restore to the original location? Can you restore

 We recently completed an upgrade of Veeam Service Provider Console (VSPC) from version 8.1 to version 9.1 in a large-scale, multi-tenant service provider environment. From an infrastructure standpoint, the upgrade was uneventful in the best possible way. All core services came online cleanly, communication between components remained stable, and backup operations continued without disruption. Pre and post-upgrade validation confirmed that the platform was operating as expected. During routine post-upgrade review, particularly within the Managed Computers section, we observed that a subset of endpoints had management agent upgrades that were not completing successfully. After reviewing task logs across multiple tenants, it became clear that these were not platform-related issues, but conditions specific to individual endpoints that surfaced during the agent upgrade cycle. Given the scale and diversity typical in service provider environments, sharing these observations may be useful fo

I want to introduce you to another community project I worked on: The Veeam Data Platform Content Pack for Graylog. Graylog is a Security Information and Event Management (SIEM) solution that enables the efficient collection, search, analysis, and alerting of various types of machine-generated data. More details about their products can be found on the official website.Content Pack DescriptionThe first version of the Content Pack enables the visualization of security-relevant events transmitted by Veeam Backup & Replication via Syslog. In addition to a pre-configured Dashboard, further information is extracted from the Syslog data, which allows the ingested data to be analyzed further. For more details about the Content Pack, see README.md on GitHub.Download & Install the Content Pack The following steps describe how to download and install the Content Pack.DownloadDownload the Content Pack from GitHub. Graylog Upload & InstallationAfter downloading, log in to the Graylog w

OverviewIn this post, I’ll walk through a practical, step-by-step job configuration (from the lab) with real-world best practices to help you get it right from Day 1.Configuring backup jobs in Veeam is where your data protection strategy truly comes to life. A properly configured job ensures your data is not just backed up—but recoverable, efficient, and aligned with business requirements. Why Job Configuration MattersIt’s easy to click through a wizard and create a backup job—but misconfigured jobs can lead to: Failed recoveries Poor performance Storage inefficiencies Gaps in protection Key takeaway: A successful job ≠ a recoverable backup. Step 1: Choose the Right Job TypeStart by identifying what you’re protecting: Virtual Machines (VMware / Hyper-V / Scale Computing / HPE VM Essentials) Physical systems (agent-based backups) Cloud workloads   Step 2: Select Your WorkloadsDuring the “Objects” step:Best practices: Group similar systems (e.g., production, dev, test) Avoid

For years, the Veeam Health Check Report has been a trusted resource for assessing configuration drift, security posture, and operational gaps across Veeam Backup & Replication (VBR) environments. But as cyber‑resilience expectations evolve, organizations require continuous insight—not periodic manual reports.Note: This is a lab environment and was setup with error for this purpose of this blog.  Why Automate the Health Check?The traditional Health Check tool delivers exceptional detail, but it remains a point‑in‑time assessment. Modern resilience requirements—CPS 234, ASD Essential Eight, ISM, NIST frameworks—expect continuous monitoring, not periodic snapshots.Integrating this logic directly into Veeam ONE Intelligence would:Eliminate manual execution of the standalone Health Check tool Provide continuous diagnostic, configuration, and compliance insights Enable proactive remediation aligned with cyber‑resilience best practices Support automated reporting to leadership, auditors,

Sizing Veeam environments has always been a mix of experience, assumptions, and spreadsheets. But that just changed. With the new Scenario Builder, Veeam takes a big leap forward, making multi-site sizing clearer, smarter, and far more predictable—turning complex design decisions into a structured, repeatable process.          RESULTS !!!!  😎📊  To wrap it up, the Scenario Builder turns sizing from assumptions into facts. By modeling real workloads, data flows, and site-to-site constraints, it delivers a clear, defensible, and repeatable design for Veeam deployments. Instead of guessing, you end up with a sizing you can explain, justify, and trust—ready for production from day one.  

 Veeam Community Hub | World Backup Day 2026 Contest Entry | Working in the managed services space teaches you pretty quickly that good architecture isn't about optimizing IOPS or storage densities. It's about keeping a business alive when things go wrong. That mindset proved its worth late last year during one of the most stressful weekends my team has ever worked.Our NOC woke me up at 3 AM on a Saturday. Medium-sized regional manufacturing client, three facilities running around the clock, roughly 200 VMs, about 80TB of production data. The client's IT Director was already on the bridge call. A ransomware strain had bypassed their endpoint protection and moved laterally. By the time the anomalies were flagged, the payload had encrypted their core ERP system, SQL databases, and primary file servers. All three production lines were stopped.The threat actors left a ransom note demanding Bitcoin. They also claimed they had successfully deleted every backup repository.The IT Director aske

 Every backup admin eventually gets the same question: how do you know the backup will really work when you need it?A successful backup job only tells you the data made it to the repository. It does not prove the VM will boot, the services will start, or the application will behave the way it should. That is the gap SureBackup is meant to close.SureBackup boots VMs directly from backup files inside an isolated virtual lab, runs health checks and application tests, and gives you a result that means something. Instead of assuming a restore point is good because the job was green, you can verify that the workload actually comes up and responds. What SureBackup is really doing Under the hood, SureBackup uses the vPower NFS service to present the backup files to an ESXi host as a datastore. VMs are then registered and powered on straight from those backup files. Nothing gets fully extracted first, and the original backup chain is not modified.Any writes generated during the verification ses

So, I have recently deployed Veeam in my lab.My Jobs are configured. Backups are running. Everything looks… green.Cool.Now comes the part most people skip—and regret later.Because here’s the reality:Day 1 is the best time to break your backup environment on purpose.If something’s going to fail, you want it to fail now—not during an outage when everyone’s watching.Let’s walk through what you should actually test immediately after setup so you know your backups work when it matters. 1. Test a Full VM Restore (Don’t Skip This)What most people do:Assume backups = recoverable.What you should do:Actually restore a VM.Test:Perform a full VM restore to a test location Power it on Verify OS boots and services startWhat you’re validating:Backup integrity Restore process works end-to-end You’re not missing dependenciesIf you’ve never restored a VM, your backup strategy is still theoretical. 2. Test Instant Recovery This is your fastest path to uptime.Test:Use Instant Recovery to start a VM from b

A lot of service providers running Cloud Connect either never deployed it, stood it up once and barely touched it again, or still treat it like an optional extra. That is a mistake. Once you understand what it actually handles, it stops looking optional and starts looking like the management layer you should have put in place earlier.VSPC sits above Veeam Backup & Replication and gives you one place to manage tenant onboarding, license distribution, usage reporting, billing data, and day-to-day monitoring across the customer environments you support. Without it, you end up doing too much by hand and logging into too many individual systems just to answer routine operational questions.This article walks through a production VSPC deployment: how to think about the architecture, how to onboard tenants in the right order, how the Pulse integration changes license management, what usage reporting looks like when you need billing data every month, which dashboards actually matter, and wh

Today my fourth book announcement went live for the Mastering Veeam Backup & Replication series.  You can pre-order now.  Note the publishing date says May 11th but that will be moved up to April as that is what we are shooting for.Announcement - Amazon.com: Mastering Veeam Backup & Replication: Architect and deploy a resilient Veeam 13 backup platform with proven best practices: 9781806388899: Chris Childerhose, Rick Vanover: BooksGetting excited now. 

The Skill Your Team Is Probably MissingHere's something worth sitting with: most IT teams are great at backup. They know retention policies, job scheduling, repository sizing, all of it. But recovery orchestration is a different skill set, and it's one that's genuinely underrepresented on most teams.The VRO Essentials course is designed to change that. It covers application grouping and dependencies — a topic that sounds straightforward until you're dealing with a three-tier application where App, Web, and DB servers need to come back online in the right sequence, with the right network configuration, pointed at the right infrastructure. Get that wrong during a real incident and your "successful" recovery is actually still broken. The course also covers monitoring, testing strategy, and a tips-and-tricks module full of practical guidance: how to optimize for performance, time-saving strategies when building recovery plans, and how to troubleshoot the most common issues customers run in

I recently went through the Veeam Recovery Orchestrator Essentials course in Veeam University Pro and I will post some of my impressions on the course and about why recovery orchestration is essential to any data resilience plan.When I was growing up, my dad used to take me to see the symphony and I always thought the conductor had the easiest job in the whole symphony. He just waved his baton during the whole concert! But then I realized that it only looks easy because of all the preparation done before the concert. All the hours, days, weeks of preparation and practice made the performance look easy.It’s exactly the same way with recovery orchestration. As my friend Scott says in his post about Disaster Recovery at 4AM, no one wants to be doing the planning and thinking at the time of DR. If things can be planned and tested beforehand, at the time of DR, you look as calm as the conductor of a symphony.Today I’m going to post an overview of the course. In other posts in the next few d

In this article, I will talk about Recovering Fast after a Ransomware attack using Veeam. I have tested this in my lab and educated my customers on every demo on the importance of having this all-in place. You would be amazed at the responses I get and how unimportant backups seem to everyone until they're neededRansomware doesn’t give you time to think.One minute everything’s running fine. The next, files are encrypted, systems are offline, and someone is asking how long recovery will take.That’s the moment where your backup strategy stops being theory—and becomes reality.If you want to recover fast, you need more than backups. You need a recovery plan that actually works under pressure.Let’s walk through what that looks like using Veeam. Step 1: Contain the Damage (Immediately)Before you recover anything, stop the spread.What to do:Isolate infected systems from the network Disable compromised accounts Shut down affected workloads if neededWhy it matters:If ransomware is still active,

Happy Friday, dear community!  I hope you all had a great week, and here's a veeamazing selection of reading materials for you! As you are probably aware, over the last three weeks, we have announced the new classes of 2026 for all three community programms at Veeam. This February Vanguard Newsletter reflects the announcement of the new Veeam Vanguard Class, and also features content from our new Vanguard members. 🤓 I am excited to see how many insightful articles reflecting product updates have been shared over the last month, and I am already looking forward to the next one, which will follow soon! We will soon have the updated Veeam100 Directory up and running, where you will be able to view the profiles of all members of each of our community programms, such as the Veeam Vanguards, Legends and VeeaMVPs. ​@AndreTheGiant - Malware detection methods in Veeam Backup & Replication 13 - https://vinfrastructure.it/2026/02/malware-detection-methods-in-veeam-backup-replication-13/ ​@be