<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rsync on Linux Café</title>
    <link>https://mrtomlinux.org/tags/rsync/</link>
    <description>Recent content in Rsync on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 09 Jun 2026 09:07:15 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/rsync/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming rsync: My Backup Scripts and the Quest for Consistent Snapshot Rotation</title>
      <link>https://mrtomlinux.org/post/2026-06-09-taming-rsync-my-backup-scripts-and-the-quest-/</link>
      <pubDate>Tue, 09 Jun 2026 09:07:15 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-09-taming-rsync-my-backup-scripts-and-the-quest-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-backup-scripts&#34;&gt;Introduction to Backup Scripts&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been running my own homelab for years, and I&amp;rsquo;ve learned the hard way that a solid backup strategy is crucial. After trying out various backup tools in 2025, I kept coming back to &lt;code&gt;rsync&lt;/code&gt; due to its flexibility and reliability. This year, I&amp;rsquo;ve been focused on fine-tuning my backup scripts to achieve consistent snapshot rotation. Don&amp;rsquo;t bother with overly complex backup solutions - &lt;code&gt;rsync&lt;/code&gt; is a powerful tool that can get the job done.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
