<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fileextraction on Linux Security</title><link>https://linuxtransfer.com/tags/fileextraction/</link><description>Recent content in Fileextraction on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 07 Oct 2026 09:05:28 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/fileextraction/index.xml" rel="self" type="application/rss+xml"/><item><title>How to pull a single file from a Borg backup without unpacking the entire archive</title><link>https://linuxtransfer.com/post/2026-10-07-how-to-pull-a-single-file-from-a-borg-backup-/</link><pubDate>Wed, 07 Oct 2026 09:05:28 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-10-07-how-to-pull-a-single-file-from-a-borg-backup-/</guid><description>&lt;h2 id="why-pull-a-single-file-from-a-borg-archive">Why pull a single file from a Borg archive?&lt;/h2>
&lt;p>When a configuration file or a database dump is corrupted, you often need only that one file, not the whole archive. Extracting the entire archive just to get a single file wastes bandwidth, CPU, and disk space—especially when the archive lives on a remote server or in a cloud bucket.&lt;/p>
&lt;p>Because Borg keeps the archive compressed and deduplicated, the cost of pulling a single file is proportional to the file’s size and the number of blocks it occupies. Below is a quick walk‑through for retrieving a single file efficiently, both locally and remotely, and piping the data through other tools for immediate processing or secure transfer.&lt;/p></description></item></channel></rss>