<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tar on Michael’s Domain</title><link>https://jeltsch.org/en/tags/tar/</link><description>Recent content in Tar on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/tar/index.xml" rel="self" type="application/rss+xml"/><item><title>BackupPC and Macs</title><link>https://jeltsch.org/en/backuppc_and_macs/</link><pubDate>Wed, 13 Apr 2016 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/backuppc_and_macs/</guid><description>&lt;p&gt;I myself have been using the backup software 
 &lt;a href="http://backuppc.sourceforge.net/" target="_blank" rel="noopener noreferrer nofollow"&gt;BackupPC&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 for almost a decade, and I started to backup our lab computers to a central backup server about two years ago. BackupPC supports deduplication and therefore much data can be stored on a couple of 2 TB drives.BackupPC supports many protocols (smb, ftp, tar/rsync via ssh), but we mostly use rsync via ssh. The data is not encrypted before the backup. Strangely not even the upcoming version 4 will support pre-egression encryption. However, we store the backup on an encrypted volume. That way it is at least protected if the backup server is stolen. And during transit, the data is protected by ssh. However, the system is not 
 &lt;a href="https://en.wikipedia.org/wiki/Trust_no_one_%28Internet_security%29" target="_blank" rel="noopener noreferrer nofollow"&gt;TNO&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 (&amp;ldquo;trust no-one&amp;rdquo;), since I (as the backupc administrator) can access the files. When using Linux, one feasible method would be to encrypt the user&amp;rsquo;s home directory using 
 &lt;a href="http://ecryptfs.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;eCryptFS&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 (which is an inbuilt option when creating users on 
 &lt;a href="http://www.ubuntu.com/" target="_blank" rel="noopener noreferrer nofollow"&gt;Ubuntu&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
) and then backup the /home/.ecryptfs directory instead of the users home directory. However, recovery would be much more of a problem. You would be able to browse the diectory structure and files of the backup, but the filenames would be meaningless since they are also encrypted in the process.There is one peculiarity in backing up Mac OSX machines: BackupPC normally connects as root via ssh into the client computer and executes the rsync backup command. In order to make this possible on university-managed Mac OSX computers, we had to create a dedicated user (&amp;ldquo;backuppc&amp;rdquo;) on the client machines and allow for this user the execution of rsync with root privileges, which is done by adding this line in the /etc/sudoers file:&lt;code&gt;backuppc ALL=NOPASSWD: /usr/bin/rsync&lt;/code&gt;. Then we have to change the ssh/rsync command for the Mac client on the backuppc server changing &amp;ldquo;root&amp;rdquo; into &amp;ldquo;backuppc&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Disk dumps (dd) and copying over the network (netcat)</title><link>https://jeltsch.org/en/disk_dumps_dd_and_copying_over_the_network_netcat/</link><pubDate>Tue, 16 Feb 2010 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/disk_dumps_dd_and_copying_over_the_network_netcat/</guid><description>&lt;p&gt;On the receiving machine (disk sda MUST be unmounted, e.g. by booting from a live CD or USB stick):&lt;code&gt;netcat -l -p 4778 | dd of=/dev/sda&lt;/code&gt;On the sending machine (disk sdb MUST be unmounted, e.g. by booting from a live CD or USB stick):&lt;code&gt;dd if=/dev/sdb | netcat 192.168.0.4 4778&lt;/code&gt;(-l listen; -p port)To copy a directory over the network, enter the directory and execute on the sending machine:&lt;code&gt;tar -cz . | nc -q 10 -l -p 45454&lt;/code&gt;On the receiving machine, create the directory, enter it and execute:&lt;code&gt;nc -w 10 192.168.0.11 45454 | tar -xz&lt;/code&gt;BTW: If you want to see the progress of a disk dump (how much was already copied in what time at what average speed), you can use (in newer versions of dd) the status option. I guess this might not work for network copying, but I have not tried… &lt;code&gt;dd if=/dev/sdb of=/target status=progress&lt;/code&gt;&lt;/p&gt;</description></item><item><title>tar copying via ssh</title><link>https://jeltsch.org/en/tar_copying_via_ssh/</link><pubDate>Fri, 26 Sep 2008 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/tar_copying_via_ssh/</guid><description>&lt;p&gt;&lt;code&gt;tar czv sourcepath | ssh -l username 192.168.0.5 tar xz -C targetpath&lt;/code&gt;&lt;/p&gt;</description></item><item><title>Sequence trace files in tar archives (Staden)</title><link>https://jeltsch.org/en/sequence_trace_files_in_tar_archives_staden/</link><pubDate>Thu, 05 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/sequence_trace_files_in_tar_archives_staden/</guid><description>&lt;p&gt;I want to store all sequence traces of a sequencing project (using Staden) in one file. You can do that if you simply tar all the *.ztr files: &lt;code&gt;tar -cvf ./test.tar *.ztr&lt;/code&gt; Then you have to specify in gap4 &lt;code&gt;Options -&amp;gt; Configure menus -&amp;gt; Expert&lt;/code&gt; And then you need to specify &lt;code&gt;Options -&amp;gt; Trace file location -&amp;gt; TAR=./test.tar&lt;/code&gt;&lt;/p&gt;</description></item><item><title>How to back up hidden files</title><link>https://jeltsch.org/en/how_to_back_up_hidden_files/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_back_up_hidden_files/</guid><description>&lt;p&gt;&lt;code&gt;tar cvf backupfile.tar .[a-zA-Z0-9]*&lt;/code&gt;Any better ideas? This command requires that the dot is followed by an alphanumerical character. Which is usually the case for the hidden files in the user&amp;rsquo;s home folder.&lt;/p&gt;</description></item><item><title>Backup your home directory using tar</title><link>https://jeltsch.org/en/backup_your_home_directory_using_tar/</link><pubDate>Thu, 16 Nov 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/backup_your_home_directory_using_tar/</guid><description>&lt;p&gt;As root go to /home directory and execute the command:&lt;code&gt;tar -czvf pathto/archive.tar.gz username&lt;/code&gt;&lt;/p&gt;</description></item></channel></rss>