<?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 jtagcat&#39;s tail</title>
    <link>https://tail.jtag.cat/tags/backup/</link>
    <description>Recent content in Backup on jtagcat&#39;s tail</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 03 Oct 2023 16:18:19 +0000</lastBuildDate><atom:link href="https://tail.jtag.cat/tags/backup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>zfs-freeze: External atomic backups</title>
      <link>https://tail.jtag.cat/zfs-freeze/</link>
      <pubDate>Tue, 03 Oct 2023 16:18:19 +0000</pubDate>
      
      <guid>https://tail.jtag.cat/zfs-freeze/</guid>
      <description>&lt;p&gt;I use &lt;a href=&#34;https://docs.oracle.com/cd/E18752_01/html/819-5461/gbchx.html&#34;&gt;&lt;code&gt;zfs-send&lt;/code&gt;&lt;/a&gt; for backups, but not all destinations&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; support it. Backing up live systems is problematic — while non-atomic &lt;strong&gt;ordered&lt;/strong&gt; rollbacks are business as usual, segmented backups lead to corrupted databases and broken restores.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://12factor.net&#34;&gt;Twelve-Factor Apps&lt;/a&gt; included: even if state isn&amp;rsquo;t derived from multiple sources, references can still break. For example, when blob storage is backed up a minute before the database, the restored application could hold a broken reference to an image, which doesn&amp;rsquo;t exist.&lt;/p&gt;

      [...]</description>
    </item>
    
  </channel>
</rss>
