<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Storage on The Home Lab</title><link>https://adamazl.github.io/homelab/tags/storage/</link><description>Recent content in Storage on The Home Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 00:37:20 +1300</lastBuildDate><atom:link href="https://adamazl.github.io/homelab/tags/storage/index.xml" rel="self" type="application/rss+xml"/><item><title>Immich: Your Self-Hosted Google Photos Replacement</title><link>https://adamazl.github.io/homelab/posts/immich-self-hosted-google-photos/</link><pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/immich-self-hosted-google-photos/</guid><description>&lt;h2 id="why-you-need-this"&gt;Why You Need This&lt;/h2&gt;
&lt;p&gt;Let me paint you a picture. You&amp;rsquo;ve got 80,000 photos scattered across your phone, your partner&amp;rsquo;s phone, and three old laptops. They&amp;rsquo;re on Google Photos — until Google changes their storage policy again, or you get locked out of your account, or you just get tired of feeding a trillion-dollar company your entire family&amp;rsquo;s memories.&lt;/p&gt;
&lt;p&gt;Or maybe you&amp;rsquo;re already off Google and your photos are just&amp;hellip; sitting in a folder on your NAS. Perfectly preserved, completely unsearchable, impossible to share.&lt;/p&gt;</description></item><item><title>Automated Backups with Proxmox Backup Server</title><link>https://adamazl.github.io/homelab/posts/proxmox-backup-server/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/proxmox-backup-server/</guid><description>&lt;h2 id="the-problem-with-ad-hoc-backups"&gt;The Problem with Ad-hoc Backups&lt;/h2&gt;
&lt;p&gt;Proxmox VE has built-in backup functionality — you can snapshot a VM to a directory or NFS share on a schedule. But it stores full backups each time, space grows fast, and restoring requires the whole archive. Proxmox Backup Server (PBS) solves all three problems.&lt;/p&gt;
&lt;p&gt;PBS is a dedicated backup server that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stores backups with &lt;strong&gt;client-side deduplication and compression&lt;/strong&gt; (typically 50–80% space savings)&lt;/li&gt;
&lt;li&gt;Does &lt;strong&gt;incremental backups&lt;/strong&gt; — only changed chunks are uploaded&lt;/li&gt;
&lt;li&gt;Supports &lt;strong&gt;instant verification&lt;/strong&gt; by recalculating checksums&lt;/li&gt;
&lt;li&gt;Has &lt;strong&gt;pruning policies&lt;/strong&gt; — keep 7 daily, 4 weekly, 12 monthly backups automatically&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="architecture"&gt;Architecture&lt;/h2&gt;
&lt;p&gt;PBS is a separate Debian-based appliance. It does not run inside Proxmox VE. You have a few options:&lt;/p&gt;</description></item><item><title>ZFS for Homelabbers: Pools, Datasets, and Snapshots</title><link>https://adamazl.github.io/homelab/posts/zfs-storage-pools/</link><pubDate>Sat, 24 Jan 2026 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/zfs-storage-pools/</guid><description>&lt;h2 id="what-makes-zfs-different"&gt;What Makes ZFS Different?&lt;/h2&gt;
&lt;p&gt;ZFS is not just a filesystem — it&amp;rsquo;s a combined volume manager and filesystem. Everything from disk management to RAID to snapshots to checksumming is handled in one stack. This matters because:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Every block is checksummed.&lt;/strong&gt; Silent data corruption (bit rot) is detected and, with redundancy, automatically corrected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Snapshots are instant and cheap.&lt;/strong&gt; A snapshot is just a pointer — it consumes no space until you delete data that the snapshot still references.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Copy-on-write semantics.&lt;/strong&gt; Writes never overwrite existing data. Torn writes (partial writes during power failure) cannot corrupt the filesystem.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Compression is transparent.&lt;/strong&gt; Enable it on a dataset and the CPU handles compression/decompression invisibly.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;ZFS does not protect against drive failure any better than hardware RAID — it has the same RAIDZ fault tolerance. What it protects against is &lt;em&gt;silent&lt;/em&gt; corruption, which hardware RAID controllers can silently propagate.&lt;/p&gt;</description></item><item><title>Building a Home NAS with TrueNAS Scale</title><link>https://adamazl.github.io/homelab/posts/truenas-scale-setup/</link><pubDate>Sat, 10 Jan 2026 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/truenas-scale-setup/</guid><description>&lt;h2 id="why-truenas-scale"&gt;Why TrueNAS Scale?&lt;/h2&gt;
&lt;p&gt;TrueNAS Scale is a Debian-based NAS operating system built around ZFS. The &amp;ldquo;Scale&amp;rdquo; version adds Linux containers (Docker/Kubernetes) on top of the traditional NAS features, so your storage box can also run apps like Jellyfin or Nextcloud alongside your shares.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s free, open-source, and the ZFS integration is first-class. Data integrity checks, snapshots, and replication are all built in and accessible through the web UI.&lt;/p&gt;
&lt;h2 id="hardware-recommendations"&gt;Hardware Recommendations&lt;/h2&gt;
&lt;p&gt;ZFS is memory-hungry and loves ECC RAM. For a home NAS:&lt;/p&gt;</description></item></channel></rss>