<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Data Safety on SILO</title>
    <link>https://silo.pgsty.com/tags/data-safety/</link>
    <description>Recent content in Data Safety on SILO</description>
    <generator>Hugo</generator>
    <language>en</language>
    
    
    
      <lastBuildDate>Mon, 09 Nov 2026 12:30:06 +0800</lastBuildDate>
    
    
      <atom:link href="https://silo.pgsty.com/tags/data-safety/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Restored Copies: Expire the Copy, Not the Object</title>
        <link>https://silo.pgsty.com/blog/design/restored-copy-expiry/</link>
        <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/restored-copy-expiry/</guid>
        <description>Why the expiry of a restored copy of a current version hid the object or stripped an older null version, why addressing the exact version is the core repair, and which storage and native-restore safeguards have to ship with it.</description>
      </item>
    <item>
        <title>Multi-Pool Lifecycle Expiry: Decide on the Whole Object</title>
        <link>https://silo.pgsty.com/blog/design/multi-pool-lifecycle-expiry/</link>
        <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/multi-pool-lifecycle-expiry/</guid>
        <description>Why lifecycle rules evaluated on the versions of one pool hide, delete, or resurrect versions stored in another pool, and why a recheck on the merged version list under the object lock is the minimum complete repair.</description>
      </item>
    <item>
        <title>Heal Dry Run Must Not Delete Data</title>
        <link>https://silo.pgsty.com/blog/design/heal-dry-run-safety/</link>
        <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/heal-dry-run-safety/</guid>
        <description>Why an admin heal run as a dry run can still delete a dangling object version when its metadata has no read quorum, why a five-line early return is the right fix for this release, and why the same fix must also carry the dry-run flag to remote nodes during bucket heal.</description>
      </item>
    <item>
        <title>Lifecycle Delete-All Must Stay on One Key</title>
        <link>https://silo.pgsty.com/blog/design/ilm-delete-all-exact-key/</link>
        <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
        
        <guid>https://silo.pgsty.com/blog/design/ilm-delete-all-exact-key/</guid>
        <description>Why a lifecycle or batch &amp;ldquo;delete all versions&amp;rdquo; of one key also deletes every object stored under that key&amp;rsquo;s name, and why purging the key&amp;rsquo;s own versions by ID, under the object lock and after a recheck, is the minimum complete repair.</description>
      </item>
    
  </channel>
</rss>
