<?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 Linux Security</title><link>https://linuxtransfer.com/tags/backup/</link><description>Recent content in Backup on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2026 09:22:18 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/backup/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Extract a Single File from a Borg Backup Archive Without Recreating the Entire Directory Tree</title><link>https://linuxtransfer.com/post/2026-09-12-how-to-extract-a-single-file-from-a-borg-back/</link><pubDate>Sat, 12 Sep 2026 09:22:18 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-09-12-how-to-extract-a-single-file-from-a-borg-back/</guid><description>&lt;h2 id="extracting-a-single-file-from-a-borg-archive-without-recreating-the-entire-directory-tree">Extracting a Single File from a Borg Archive Without Recreating the Entire Directory Tree&lt;/h2>
&lt;p>When a backup archive grows to several terabytes, restoring a single configuration file or a database dump can feel like pulling a needle from a haystack. Borg’s default &lt;code>extract&lt;/code> command rebuilds the whole directory tree, which is wasteful when you only need one file. The following guide shows how to pull a single file efficiently, keeps metadata intact, and keeps your system secure.&lt;/p></description></item></channel></rss>