<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Catalogic DPX on Catalogic Software</title><link>https://www.catalogicsoftware.com/blog/tags/catalogic-dpx/</link><description>Recent content in Catalogic DPX on Catalogic Software</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 10 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.catalogicsoftware.com/blog/tags/catalogic-dpx/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Back Up Proxmox VE with Catalogic DPX 4.16</title><link>https://www.catalogicsoftware.com/blog/how-to-back-up-proxmox-ve-with-catalogic-dpx/</link><pubDate>Mon, 10 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/how-to-back-up-proxmox-ve-with-catalogic-dpx/</guid><description>&lt;p&gt;Setting up a reliable Proxmox backup should include more than getting one successful job. You need to know which virtual machines are protected, where their recovery points are stored, and whether you can restore a working VM when it matters.&lt;/p&gt;
&lt;p&gt;This guide walks through that process with Catalogic DPX 4.16. You will add a Proxmox VE cluster to DPX, install the required host plugin, create an agentless backup job to vStor, and test a full virtual machine restore. The instructions reflect the current &lt;a href="https://docs.catalogicsoftware.com/dpx/backup/proxmox-backup/"&gt;DPX 4.16 Proxmox documentation&lt;/a&gt; as of August 10, 2026.&lt;/p&gt;</description></item><item><title>Beyond Proxmox Backup Server: When Do You Need More?</title><link>https://www.catalogicsoftware.com/blog/beyond-proxmox-backup-server-when-do-you-need-more/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/beyond-proxmox-backup-server-when-do-you-need-more/</guid><description>&lt;p&gt;Companies moving to Proxmox VE usually reach backup planning early in the migration. Proxmox is straightforward to run, and its licensing gives teams more freedom in how they build their infrastructure.&lt;/p&gt;
&lt;p&gt;For many environments, Proxmox Backup Server is the right answer. It comes from the same company and plugs straight into Proxmox VE. PBS provides incremental backups, deduplication, encryption, replication, file-level restore from VM and container backups, live restore that starts a VM while its data is copied, and tape support. A Proxmox-only environment with retention measured in weeks or months may have no need for a second product.&lt;/p&gt;</description></item><item><title>Backing up multi-hypervisor environments: challenges, mistakes, and how to get it right</title><link>https://www.catalogicsoftware.com/blog/multi-hypervisor-backup-vmware-hyper-v-proxmox/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/multi-hypervisor-backup-vmware-hyper-v-proxmox/</guid><description>&lt;p&gt;Most IT environments today run more than one hypervisor. A company might have VMware vSphere as its primary platform, Hyper-V running on older Windows Server infrastructure, and one or more additional platforms picked up through growth, acquisitions, shifting infrastructure requirements, or Total Cost of Ownership initiatives. Nutanix AHV, Proxmox VE, OpenStack, and Canonical MicroStack are all common additions to an estate that started somewhere else. The latter is increasingly common, with many organizations actively evaluating or migrating away from VMware as licensing costs and pricing models have changed. That mix of platforms is not unusual. In fact, it is close to the norm for any organization that has evolved organically over the years or gone through mergers and budget cycles.&lt;/p&gt;</description></item><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><item><title>DPX 4.15: Modern NDMP Backup Management, VMware Tags, and Enterprise Encryption</title><link>https://www.catalogicsoftware.com/blog/what-dpx-4-15-actually-delivers/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.catalogicsoftware.com/blog/what-dpx-4-15-actually-delivers/</guid><description>&lt;p&gt;DPX 4.15 is shipping with four areas of meaningful change: full NDMP management in the web interface, VMware backup scoping by vCenter tags, KMIP-compliant key management in &lt;a href="https://www.catalogicsoftware.com/products/vstor/"&gt;vStor&lt;/a&gt;, and cloud archive encryption. None of these are speculative features. They deliver on capabilities that our customers have been asking for, and each one has a clear operational payoff.&lt;/p&gt;
&lt;p&gt;This post walks through what each feature does, why it matters operationally, and where it fits in the broader context of how organizations manage NAS, VMware, and encryption today.&lt;/p&gt;</description></item></channel></rss>