<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>D// #13 (Posts about lxc)</title><link>https://alcacer.de/</link><description></description><atom:link href="https://alcacer.de/categories/lxc.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:hello@alcacer.de"&gt;Dorian&lt;/a&gt; </copyright><lastBuildDate>Tue, 25 Nov 2025 17:07:24 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>LXC backup</title><link>https://alcacer.de/posts/lxc-backup/</link><dc:creator>Dorian</dc:creator><description>&lt;div&gt;&lt;div class="w3-panel w3-pale-green"&gt;
&lt;span class="w3-tag w3-green"&gt;Current&lt;/span&gt; 
This solution still works remarkably good.
&lt;/div&gt;

&lt;p&gt;Additionally to a duply-driven approach, we wanted to backup our LXC containers remotely in an archive.&lt;/p&gt;
&lt;p&gt;The following approach was taken from &lt;a href="https://stackoverflow.com/questions/23427129/how-do-i-backup-move-lxc-containers"&gt;stackoverflow&lt;/a&gt; and was tailored to our needs.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://alcacer.de/posts/lxc-backup/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>lxc</category><category>rsync</category><guid>https://alcacer.de/posts/lxc-backup/</guid><pubDate>Tue, 14 Jan 2020 16:00:00 GMT</pubDate></item></channel></rss>