<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backup on Daniel McDonough</title><link>https://dev.daniel-mcdonough.com/tags/backup/</link><description>Recent content in Backup on Daniel McDonough</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Daniel McDonough</copyright><lastBuildDate>Wed, 13 May 2026 13:10:39 -0400</lastBuildDate><atom:link href="https://dev.daniel-mcdonough.com/tags/backup/index.xml" rel="self" type="application/rss+xml"/><item><title>Veeam Restores on Proxmox local-zfs</title><link>https://dev.daniel-mcdonough.com/posts/veeam-restores-on-proxmox-local-zfs/</link><pubDate>Wed, 13 May 2026 13:10:39 -0400</pubDate><guid>https://dev.daniel-mcdonough.com/posts/veeam-restores-on-proxmox-local-zfs/</guid><description>&lt;p>During some disaster recovery work, I deployed a Proxmox cluster to rapidly restore VMs from Veeam but ran into a restore target issue.&lt;/p>
&lt;p>Veeam&amp;rsquo;s Proxmox plugin can back up VMs running on &lt;code>local-zfs&lt;/code> just fine. Restoring them is the problem: Veeam won&amp;rsquo;t use a ZFS pool as a restore target. It needs Directory-type storage. ZFS storage types create zvols for each disk and restoring directly would obviously lead to complexities, especially when trying to export from Veeam as QCOWs.&lt;/p></description></item></channel></rss>