snapshots

Way too many snapshots

In this post In this post, we have: FreeBSD 14.1-RELEASE-p5 r730-03 Lots of boring repetitive sections, so skip over that to find what you need This article was written over a couple of days. The zpool in question is 3 pairs of 12TB HDD: [13:44 r730-03 dvl ~/tmp] % zpool status data01 pool: data01 state: ONLINE scan: scrub in progress since Fri Jan 17 05:29:21 2025 22.1T / 26.1T scanned at 200M/s, 19.2T […]

Way too many snapshots Read More »

The backup disk image … sparsebundle could not be accessed (error 19)

I wrote this back when and left it in drafts. Time to publishh. I was getting this message when one of my MacBooks was trying to back via TimeMachine to my FreeBSD ZFS server. “The backup disk image … sparsebundle could not be accessed (error 19)” imeMachine also told me the last backup was on Oct 7. Checking my snapshots: [20:01 r730-03 dvl ~] % zfs list -r -t snapshot data01/timemachine/dvl-air01 NAME USED

The backup disk image … sparsebundle could not be accessed (error 19) Read More »

Loading up an old copy of a PostgreSQL database, zfs snapshots, and sanoid snapshot management

Sometimes you want to go back to a known good state. And you want to do it quickly, without waiting around. In my case, that’s going to be a zfs snapshot. Today I am preparing to test some code changes so that FreshPorts properly creates a new category. See these recent blog posts for details: Welcome to the new category: filesystems Fixing the category creation code In this post: FreeBSD 14.1-RELEASE-p5 postgresql16-server-16.4 dbclone

Loading up an old copy of a PostgreSQL database, zfs snapshots, and sanoid snapshot management Read More »

zfs hold / release

Let’s talk about zfs hold. Based on man zfs-hold: “If a hold exists on a snapshot, attempts to destroy that snapshot by using the zfs destroy command return EBUSY.” Let’s apply that to some FreshPorts snapshots which I don’t want going away: This is your typical FreshPorts website: [15:03 dvl-nginx01 dvl ~] % zfs list NAME USED AVAIL REFER MOUNTPOINT data02 1.13T 565G 96K none data02/freshports 671G 565G 88K none data02/freshports/jailed 326G 565G

zfs hold / release Read More »

Backing up FreeBSD with Bacula via ZFS snapshot

Tonight, while watching an episode of The Great British Bake Off, I configured a new Bacula backup jobs to cover some datasets which were not already backed up. I already have a backup jobs to backup all the jails, but only for datasets which sit right under zroot/jails (for example). This new solution takes a list of datasets, snapshots them, backs them up, then destroys those snapshots. Why backup a snapshot? Consistency. During

Backing up FreeBSD with Bacula via ZFS snapshot Read More »

Bacula – calculating Maximum Volume Bytes and Maximum Volumes based on historical data

I’ve used Bacula since at least January 2004 (so nearly 20 years). I liked it so much I dropped my deployment-in-motion of another tool (if you search lightly, you can find out which one). I liked it so much, I wrote a PostgreSQL backend for it. This post is not for Bacula novices. This post is for those who have already deployed a Bacula instance and are rather familiar with the process. I

Bacula – calculating Maximum Volume Bytes and Maximum Volumes based on historical data Read More »

Moving ZFS filesystems/datasets from one ZFS zpool to another

Now that I’ve filled up data01, I bought some more SSDs and created another zpool. Today, on this snow-is-anticipated Saturday winter morning, I’m going to move some ZFS filesystems/datasets around. Side note: I like the term dataset better than filesystem. man zfs talks about datasets, which can be a file system, a volume, a snapshot, or a bookmark. However, usually when I talk about a filesystem, it might be dataset. It’s a fine

Moving ZFS filesystems/datasets from one ZFS zpool to another Read More »

Wrong recordsize on zfs send | zfs recv filesystems

Over the past few days, I’ve posted a lot about transferring jails from two hosts into one host. One of the steps involves using zfs send | zfs recv to send the files from one host to another. I’m using syncoide for that transfer. A new fileystem’s recordsize defaults to 128K. In my case, that is usually OK, except for some specific datasets. For example: * video * backups * distfiles (tarballs) Here

Wrong recordsize on zfs send | zfs recv filesystems Read More »

Transferring a jail from one host to another

I’ve started merging these two hosts: r710-01 slocum into this one host: r740-01 The goal is to then retire those first two hosts. This post covers the initial bulk copy of all the data from two hosts into the one. In this post: FreeBSD 13.1 Each jail runs on its own zfs filesystem Not covered by this post Creating jails Creating snapshost Detailed usage of syncoid hosts not using zfs The overall process

Transferring a jail from one host to another Read More »

using syncoid to backup ZFS snapshots – home assistant

Copies of data are good. Especially if on a different host. zfs snapshots combined with zfs send | zfs recv make replication of zfs file systems especially easy. I am already using sanoid to manage zfs snapshots. Now I’m going to use syncoid to transfer those snapshots to another host. Both sanoid and syncoid are provided by the sanoid package on FreeBSD. I’m sure any other packaging system does similar. In this post:

using syncoid to backup ZFS snapshots – home assistant Read More »

Scroll to Top