<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Clonezilla - vo.rs</title><link>https://vo.rs/tags/clonezilla/</link><description>Latest from the Clonezilla desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Thu, 25 Jul 2024 08:45:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/clonezilla/" rel="self" type="application/rss+xml"/><item><title>Bare-Metal Restore: Rehearsing the Recovery You Dread</title><link>https://vo.rs/story/bare-metal-restore-rehearsing-the-recovery-you-dread/</link><description>&lt;p&gt;Every backup strategy I have ever written about on this site — Borg, Restic, Kopia, the whole &lt;a href="https://vo.rs/story/the-3-2-1-rule-actually-implemented-at-home/"&gt;3-2-1 discipline&lt;/a&gt; — answers the question &amp;ldquo;can I get my files back.&amp;rdquo; None of them, by themselves, answer a harder question: if the machine itself is gone, cratered motherboard, stolen chassis, a fire that took the whole rack, how long until a replacement box is running the same services again, and does anyone actually know the steps. That is bare-metal restore, and it is the drill almost nobody rehearses, because rehearsing it means deliberately wrecking a working system to prove you can bring it back.&lt;/p&gt;</description><pubDate>Thu, 25 Jul 2024 08:45:00 +0000</pubDate></item></channel></rss>