<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hashicorp on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hashicorp/</link>
    <description>Recent content in Hashicorp on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hashicorp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Consul Backup and Recovery: Built-In Snapshot vs consul-backinator vs consul-snapshot</title>
      <link>https://www.pistack.xyz/posts/2026-05-19-self-hosted-consul-backup-recovery-snapshot-backinator-daemon-guide/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-19-self-hosted-consul-backup-recovery-snapshot-backinator-daemon-guide/</guid>
      <description>&lt;p&gt;Consul has become the go-to solution for service discovery, health checking, and distributed key-value storage across dynamic infrastructure. But as your Consul clusters grow to manage hundreds of services and thousands of KV entries, a robust backup and recovery strategy becomes critical. A corrupted Consul state can take down your entire service mesh in seconds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
