<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <docs>https://blogs.law.harvard.edu/tech/rss</docs>
    <title>Restic on Fuchsbau</title>
    <link>https://this-is-fine.io/tags/restic/</link>
    <description>Recent content in Restic on Fuchsbau</description>
    <image>
      <title>Restic on Fuchsbau</title>
      <link>https://this-is-fine.io/tags/restic/</link>
      <url>https://source.unsplash.com/2000x1322/?fox</url>
    </image>
    <ttl>1440</ttl>
    <generator>Hugo 0.125.4</generator>
    <language>de-DE</language>
    <lastBuildDate>Wed, 20 May 2026 22:26:12 UT</lastBuildDate>
    <atom:link href="https://this-is-fine.io/tags/restic/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Mastodon to snac: A Lighter Fediverse Stack</title>
      <link>https://this-is-fine.io/posts/20260520-mastodon-to-snac/</link>
      <pubDate>Wed, 20 May 2026 10:00:00 UT</pubDate>
      <dc:creator>ff0x</dc:creator>
      <guid>https://this-is-fine.io/posts/20260520-mastodon-to-snac/</guid>
      <description>The lab used to run Mastodon on Kubernetes: PostgreSQL, a Redis-compatible cache, and S3-shaped media storage on top of the usual edge stack. That worked, but it was heavy for a small personal instance — more moving parts than the workload justified.
The fediverse home at this-is-fine.social now runs snac instead: a minimal ActivityPub server in portable C, no database, all state on a single filesystem tree, backed up off-cluster with the same VolSync &#43; restic pattern as other stateful apps.
</description>
      <category domain="https://this-is-fine.io/categories/infrastructure">Infrastructure</category>
      <content:encoded><![CDATA[The lab used to run Mastodon on Kubernetes: PostgreSQL, a Redis-compatible cache, and S3-shaped media storage on top of the usual edge stack. That worked, but it was heavy for a small personal instance — more moving parts than the workload justified.
The fediverse home at this-is-fine.social now runs snac instead: a minimal ActivityPub server in portable C, no database, all state on a single filesystem tree, backed up off-cluster with the same VolSync &#43; restic pattern as other stateful apps.
Why leave Mastodon? The earlier write-up on running Mastodon in the lab listed the real cost:
Layer Mastodon stack Operational weight App Mastodon (web &#43; streaming &#43; sidekiq) Large images, many processes SQL CloudNative-PG Cluster, backups, upgrades Cache Dragonfly (Redis API) Extra Deployment, TLS to cache Media Rook RGW / object storage Buckets, credentials, S3 quirks Edge Gateway API, cert-manager, DNS Still required for federation For a handful of local users and light federation, that is a lot of infrastructure to babysit. Mastodon is excellent software; it is simply bloated relative to “I want a fediverse account on my own domain without running a small SaaS platform.”
What snac changes snac (“Social Networks Are Crap”) is deliberately small:
No PostgreSQL, no Redis, no object store — posts, follows, and media live under one data directory. ActivityPub federation to Mastodon, Pleroma, and friends; optional Mastodon API so many client apps still work. Hard-link–friendly on-disk layout (documented in snac(8)); backups must preserve that (tar/rsync -H). The lab builds a container from images/snac/ (Alpine, snac httpd via a small entrypoint). A PVC mounts at /snac/data; Gateway API and TLS stay the same story as in the Envoy Gateway post.
Internet -&amp;gt; this-is-fine.social (HTTPRoute) -&amp;gt; snac (Deployment, port 8001) PVC: server.json, users/, media/ (one tree) -&amp;gt; VolSync restic -&amp;gt; remote repository Backups without a database dump Stateful Mastodon meant CNPG backups plus optional PVC copies. With snac, the backup surface collapses to the PVC:
Include k8s/templates/volsync/ in the snac app Kustomization (same as VolSync article). Point the Deployment volume at the template’s claimName. Let the restic mover snapshot and push encrypted data to the shared remote repo. Restic sees a consistent filesystem snapshot; there is no separate “media bucket” or SQL dump to coordinate. Restore is “recover the PVC tree, start snac httpd,” respecting hard links on restore.
Account migration (Mastodon -&amp;gt; snac) snac documents a Mastodon-to-snac move in snac(8) (since 2.61). In short:
On the old Mastodon account, export follows, lists, blocks, and bookmarks (CSV). Copy the CSV files into the snac user’s import/ directory and run snac import_csv. Run snac alias to tie the new snac user to the old @user@old.instance handle. On Mastodon, use Move to a different account and point followers at the snac handle. The upstream manual and fedi.tips migration guide are worth reading before you cut traffic — federation moves depend on remote servers cooperating.
Tradeoffs snac is not a drop-in replacement for every Mastodon feature. Lists, moderation tooling, and admin UX are thinner; the web UI is simple by design. For this lab that is acceptable: less software, fewer night pages, same domain on the fediverse.
GitOps layout (Flux overview) is unchanged — only the application bundle under k8s/applications/ swapped from the Mastodon Helm release to a slim snac Deployment. The heavy chart stack can stay retired unless something else needs it.
Further reading: snac README, ActivityPub, prior Mastodon lab stack.
]]></content:encoded>
    </item>
    <item>
      <title>VolSync, Volume Snapshots, and Restic Off-Site Backups</title>
      <link>https://this-is-fine.io/posts/20251121-volsync-restic-backups/</link>
      <pubDate>Fri, 21 Nov 2025 08:00:00 UT</pubDate>
      <dc:creator>ff0x</dc:creator>
      <guid>https://this-is-fine.io/posts/20251121-volsync-restic-backups/</guid>
      <description>Stateful apps need point-in-time copies and a copy off the cluster. The lab uses VolSync with the restic mover: Kubernetes creates a VolumeSnapshot, VolSync runs restic against it, and encrypted data lands in a remote repository. The restic URL and password live in Vault and reach the cluster through External Secrets.
VolSync sits in the middle: you already run the CSI snapshot controller and a storage class that supports snapshots (Rook-Ceph block volumes in the lab). VolSync watches a ReplicationSource, triggers on a schedule, and spins up a short-lived mover job. You get off-site copies without shelling into pods to run restic by hand.
</description>
      <category domain="https://this-is-fine.io/categories/infrastructure">Infrastructure</category>
      <content:encoded><![CDATA[Stateful apps need point-in-time copies and a copy off the cluster. The lab uses VolSync with the restic mover: Kubernetes creates a VolumeSnapshot, VolSync runs restic against it, and encrypted data lands in a remote repository. The restic URL and password live in Vault and reach the cluster through External Secrets.
VolSync sits in the middle: you already run the CSI snapshot controller and a storage class that supports snapshots (Rook-Ceph block volumes in the lab). VolSync watches a ReplicationSource, triggers on a schedule, and spins up a short-lived mover job. You get off-site copies without shelling into pods to run restic by hand.
Building blocks Software Role snapshot-controller CSI snapshot API VolSync ReplicationSource and movers (restic, rsync, &amp;hellip;) restic Encrypted, deduplicated backup format Rook-Ceph Block volumes and snapshot class Data path app PVC -&amp;gt; ReplicationSource (schedule, e.g. @daily) -&amp;gt; VolumeSnapshot (CSI) -&amp;gt; restic mover -&amp;gt; remote repository Retention and prune settings sit on the ReplicationSource. See VolSync restic usage.
GitOps pattern A common Flux app installs the VolSync operator once. Each app includes the shared template and sets dependsOn: volsync. Flux postBuild sets APP, capacity, schedule, and storage class — same mechanism as domains in the GitOps overview. Per-app repository paths append ${APP} at runtime so one leaked credential does not cover every volume.
Opt-in is intentional: not every Deployment needs a PVC backup. Stateless replicas and caches stay out unless you add the template. That keeps mover jobs and repository size predictable.
Example: opt in an app The bundle in k8s/templates/volsync/ ships a PVC, ExternalSecret, ReplicationSource, and ReplicationDestination.
1. Kustomize — include the template beside the workload:
# app/kustomization.yaml resources: - ../../../../../../templates/volsync - deployment.yaml 2. Flux — depend on the operator and substitute variables:
# ks.yaml (Flux Kustomization) spec: dependsOn: - name: volsync postBuild: substitute: APP: my-app VOLSYNC_SCHEDULE: &amp;#34;@daily&amp;#34; VOLSYNC_CAPACITY: 5Gi VOLSYNC_CACHE_CAPACITY: 5Gi VOLSYNC_STORAGECLASS: &amp;#34;${BLOCK_STORAGE_CLASS}&amp;#34; VOLSYNC_SNAPSHOTCLASS: &amp;#34;${BLOCK_STORAGE_CLASS}&amp;#34; 3. Deployment — mount the PVC the template creates (claimName must match APP):
volumes: - name: data persistentVolumeClaim: claimName: my-app Flux renders ${APP} on the ReplicationSource and sets repository: my-app-volsync-secret (restic settings from Vault via ExternalSecret):
apiVersion: volsync.backube/v1alpha1 kind: ReplicationSource metadata: name: &amp;#34;${APP}&amp;#34; spec: sourcePVC: &amp;#34;${APP}&amp;#34; trigger: schedule: &amp;#34;${VOLSYNC_SCHEDULE:-@weekly}&amp;#34; restic: copyMethod: Snapshot repository: &amp;#34;${APP}-volsync-secret&amp;#34; Full field list: ReplicationSource API.
Why snapshots? A snapshot avoids stopping the pod and works well with Ceph’s CSI driver. The mover reads consistent blocks from the snapshot volume instead of the live mount, which matters when the app keeps writing logs or database pages.
Restore is the mirror path: a ReplicationDestination pulls from restic into a target PVC when you need to recover or clone. The lab wraps that in task helpers; semantics follow the VolSync user guide.
]]></content:encoded>
    </item>
  </channel>
</rss>
