<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Browser-Based Backup on Catalogic Software</title><link>https://www.catalogicsoftware.com/blog/tags/browser-based-backup/</link><description>Recent content in Browser-Based Backup on Catalogic Software</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 10 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.catalogicsoftware.com/blog/tags/browser-based-backup/index.xml" rel="self" type="application/rss+xml"/><item><title>NDMP Backup in 2026: The Protocol Isn’t the Problem. Your Management Layer Is.</title><link>https://www.catalogicsoftware.com/blog/ndmp-backup-in-2026-the-protocol-isnt-the-problem-your-management-layer-is/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/ndmp-backup-in-2026-the-protocol-isnt-the-problem-your-management-layer-is/</guid><description>&lt;p&gt;There’s a narrative floating around that NDMP is dead. That it’s a legacy protocol clinging to relevance while modern API-based approaches have moved on. Right? And I get the appeal of that story. It’s clean. It’s simple. But if you’re actually running a large NAS estate in production, you know it’s not that straightforward.&lt;/p&gt;
&lt;p&gt;NDMP backup still protects the majority of enterprise NAS data. Not because people haven’t heard of the alternatives, but because ripping out a backup protocol that’s wired into your filer infrastructure is a project nobody wants to fund when the current approach works. The real pain, for most teams we talk to, isn’t the protocol itself. It’s everything around it: the legacy GUIs, the CLI-only configuration, the two-console shuffle just to troubleshoot a single failed job.&lt;/p&gt;</description></item></channel></rss>