<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>RPi on kenops</title><link>https://www.kenops.io/tags/rpi/</link><description>Recent content in RPi on kenops</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 13 Jun 2017 06:56:17 +0000</lastBuildDate><atom:link href="https://www.kenops.io/tags/rpi/index.xml" rel="self" type="application/rss+xml"/><item><title>Raspberry Pi backup using fsarchiver and other tricks</title><link>https://www.kenops.io/posts/raspberry-pi-backup-using-fsarchiver-and-other-tricks/</link><pubDate>Tue, 13 Jun 2017 06:56:17 +0000</pubDate><guid>https://www.kenops.io/posts/raspberry-pi-backup-using-fsarchiver-and-other-tricks/</guid><description>&lt;p&gt;&lt;img loading="lazy" src="http://makezine.com/wp-content/uploads/2016/02/Raspberry-Pi-3-small.gif"&gt;So I ran into a few issues using the dd image backup I referenced prior Raspberry Pi 3 SDCard backup&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The Image is very large even though the data was not.  For example on a 32GB SD card I was getting a 12GB file.  I only have 3GB of data! so that was a bummer.&lt;/li&gt;
&lt;li&gt;When it comes time to recover, I have to expand the gz image file to a full 32GB to then image it onto another SD device.  There&amp;rsquo;s tricks around this I&amp;rsquo;m sure but still.&lt;/li&gt;
&lt;li&gt;Since dd was reading 100% of the SD card (/dev/mmcblk0) even with compression it took a LONG time to create the image.  20 minutes or so.  Since I&amp;rsquo;m backing up a live system this was a real issue.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;I did manage to figure out how to create a partial image if your partition sizes were smaller than the actual device - This seemed to work but it still was storing 6.6GB of data which was over double what I actually had:&lt;/p&gt;</description></item></channel></rss>