<?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 ads' corner</title><link>https://andreas.scherbaum.la/tags/backup/</link><description>Recent content in Backup on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/backup/index.xml" rel="self" type="application/rss+xml"/><item><title>Long timeouts in restic and resticprofile when using restic-server</title><link>https://andreas.scherbaum.la/post/2026-10-21_long-timeouts-in-restic-and-resticprofile-when-using-restic-server/</link><pubDate>Wed, 21 Oct 2026 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2026-10-21_long-timeouts-in-restic-and-resticprofile-when-using-restic-server/</guid><description>&lt;p&gt;At home I have a &lt;a href="https://github.com/Restic-Server/"&gt;restic-server&lt;/a&gt; running, which serves as one of the backup destinations for backups (among several other destinations). Over time I found that there is a small problem in this setup: when I am traveling, the backup kicks off - and needs a long time to finish when the repository is not available. The backup process runs into long timeouts, and on top of that, restic keeps the laptop from going to sleep.&lt;/p&gt;</description></item><item><title>Chemnitzer Linux-Tage 2025 - Rückblick</title><link>https://andreas.scherbaum.la/post/2025-04-09_chemnitzer-linux-tage-2025-rueckblick/</link><pubDate>Wed, 09 Apr 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-04-09_chemnitzer-linux-tage-2025-rueckblick/</guid><description>&lt;p&gt;Die &lt;a href="https://chemnitzer.linux-tage.de/2025/de/"&gt;Chemnitzer Linux-Tage 2025&lt;/a&gt; sind vorbei, wieder einmal Zeit für einen Rückblick.&lt;/p&gt;&#10;&lt;p&gt;Wie seit vielen Jahren waren wir wieder auf den Chemnitzer Linux-Tagen. Dieses Mal waren wir alle drei mehr mit eingespannt, Vorträge, Kinderparadies organisieren, Workshops, Lightning Talks, Organisationsteam &amp;hellip;&lt;/p&gt;&#10;&lt;p&gt;Passend zur &lt;a href="https://chemnitz2025.de/"&gt;Kulturhauptstadt Chemnitz 2025&lt;/a&gt; stand Jahr die Veranstaltung unter dem Motto &amp;ldquo;the Culture of Open Source&amp;rdquo;.&lt;/p&gt;&#10;&lt;p&gt;Das Logo bzw. die drei Logos wurden von &lt;em&gt;Sebastian Pettke&lt;/em&gt; erstellt. Sind schön geworden, gab es außerdem als &lt;a href="https://mastodon.social/@ascherbaum/114268258932971130"&gt;Klemmbausteine&lt;/a&gt; zu kaufen.&lt;/p&gt;</description></item><item><title>PostgreSQL Berlin October 2024 Meetup</title><link>https://andreas.scherbaum.la/post/2024-10-11_postgresql-berlin-october-2024-meetup/</link><pubDate>Fri, 11 Oct 2024 04:36:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-10-11_postgresql-berlin-october-2024-meetup/</guid><description>&lt;p&gt;On October 9th, 2024, we had the &lt;em&gt;PostgreSQL&lt;/em&gt; October Meetup in &lt;em&gt;Berlin&lt;/em&gt;. &lt;em&gt;Amazon&lt;/em&gt; hosted it, and sponsored the Meetup in their office in the &lt;em&gt;Brüderstraße&lt;/em&gt;, in &lt;em&gt;Berlin Mitte&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Clear Docker build cache</title><link>https://andreas.scherbaum.la/post/2024-08-30_clear-docker-build-cache/</link><pubDate>Fri, 30 Aug 2024 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-30_clear-docker-build-cache/</guid><description>&lt;p&gt;I have this one &lt;em&gt;Docker&lt;/em&gt; image, which I need every 2-3 months to run a task in an outdated piece of software, which is no longer supported on modern systems. That works fine, but after a while I figured that &lt;em&gt;Docker&lt;/em&gt; is keeping all the build layers, even though I remove the images and containers. Worst, sometimes I update the build for the &lt;em&gt;Docker&lt;/em&gt;file, and the entire image needs to be rebuild. Still &lt;em&gt;Docker&lt;/em&gt; caches all the previous build layers as well.&lt;/p&gt;&#10;&lt;p&gt;Removing the build layers is not obvious, there is no specific &lt;em&gt;Docker&lt;/em&gt; command.&lt;/p&gt;</description></item><item><title>Remove files from a restic backup (using resticprofile)</title><link>https://andreas.scherbaum.la/post/2024-08-15_remove-files-from-a-restic-backup-using-resticprofile/</link><pubDate>Thu, 15 Aug 2024 16:19:43 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-08-15_remove-files-from-a-restic-backup-using-resticprofile/</guid><description>&lt;p&gt;Sometimes files end up in a backup where they don&amp;rsquo;t belong. It happens. While I&amp;rsquo;m a big advocate of having backups, sometimes entries need to be removed from a backup. This is easy to do in &lt;em&gt;Restic&lt;/em&gt;, using &lt;em&gt;resticprofile&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>QNAP: exclude files and directories from rsync</title><link>https://andreas.scherbaum.la/post/2023-03-14_qnap-exclude-files-and-directories-from-rsync/</link><pubDate>Tue, 14 Mar 2023 17:06:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-03-14_qnap-exclude-files-and-directories-from-rsync/</guid><description>&lt;p&gt;I&amp;rsquo;m moving files from one QNAP system to another, and I&amp;rsquo;m using &lt;a href="https://rsync.samba.org/"&gt;rsync&lt;/a&gt; for this. It&amp;rsquo;s preinstalled on a QNAP system. So far, so good.&lt;/p&gt;&#10;&lt;p&gt;To sync entire shared volumes, I want to exclude the &lt;code&gt;@Recently-Snapshot&lt;/code&gt; and &lt;code&gt;@Recycle&lt;/code&gt; entries - I don&amp;rsquo;t want to sync the trash bin and I also don&amp;rsquo;t want to sync entire snapshots.&lt;/p&gt;&#10;&lt;p&gt;The usual approach when using &lt;code&gt;rsync&lt;/code&gt; is to just use the &lt;code&gt;--exclude&lt;/code&gt; option.&lt;/p&gt;</description></item><item><title>PGSQL Phriday #002 Summary: PostgreSQL Backup and Restore</title><link>https://andreas.scherbaum.la/post/2022-11-08_pgsql-phriday-002-summary-postgresql-backup-and-restore/</link><pubDate>Tue, 08 Nov 2022 23:45:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2022-11-08_pgsql-phriday-002-summary-postgresql-backup-and-restore/</guid><description>&lt;p&gt;Last week for &amp;ldquo;PGSQL Phriday&amp;rdquo; &lt;a href="https://andreas.scherbaum.la/post/2022-10-31_pgsql-phriday-002-postgresql-backup-and-restore/"&gt;I posted the following task&lt;/a&gt;:&lt;/p&gt;&#10;&lt;p&gt;Describe how you do backups for your &lt;em&gt;PostgreSQL&lt;/em&gt; databases.&lt;/p&gt;&#10;&lt;p&gt;And I added a bonus question: Is &lt;code&gt;pg_dump&lt;/code&gt; a backup tool?&lt;/p&gt;</description></item><item><title>PGSQL Phriday #002: PostgreSQL Backup and Restore</title><link>https://andreas.scherbaum.la/post/2022-10-31_pgsql-phriday-002-postgresql-backup-and-restore/</link><pubDate>Mon, 31 Oct 2022 14:59:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2022-10-31_pgsql-phriday-002-postgresql-backup-and-restore/</guid><description>&lt;p&gt;Thanks to Ryan Booz we now have the &lt;a href="https://www.softwareandbooz.com/introducing-psql-phriday/"&gt;#PGSQLPhriday blogging series&lt;/a&gt;. The second edition is about &lt;a href="https://xkcd.com/1718/"&gt;backups&lt;/a&gt;. And of course also about restore.&lt;/p&gt;</description></item><item><title>PGSQL Phriday #001: Two truths and a lie</title><link>https://andreas.scherbaum.la/post/2022-10-07_pgsql-phriday-001-two-truths-and-a-lie/</link><pubDate>Fri, 07 Oct 2022 18:42:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2022-10-07_pgsql-phriday-001-two-truths-and-a-lie/</guid><description>&lt;p&gt;Uh, what is this &lt;a href="https://andreas.scherbaum.la/tags/pgsqlphriday"&gt;#PGSQLPhriday&lt;/a&gt; thing about? Everyone is writing blog posts about this today &amp;hellip; For details, please read the &lt;a href="https://www.softwareandbooz.com/pgsql-phriday-001-invite/"&gt;introduction from Ryan Booz&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;This month&amp;rsquo;s topic: pick your three favorite or most important best pratices for #PostgreSQL. Tell them in a form that two are true, one is a lie. See if you can spot which one is true and which one is false. The resolution is at the end of this blog posting.&lt;/p&gt;</description></item><item><title>Changes to the public schema in PostgreSQL 15 and how to handle upgrades</title><link>https://andreas.scherbaum.la/post/2022-08-30_changes-to-the-public-schema-in-postgresql-15-and-how-to-handle-upgrades/</link><pubDate>Tue, 30 Aug 2022 16:26:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2022-08-30_changes-to-the-public-schema-in-postgresql-15-and-how-to-handle-upgrades/</guid><description>&lt;p&gt;In September 2021, a patch for the upcoming &lt;em&gt;PostgreSQL&lt;/em&gt; version 15 was &lt;a href="https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b073c3ccd06e4cb845e121387a43faa8c68a7b62"&gt;committed&lt;/a&gt; which introduces a visible change for users: the &lt;code&gt;CREATE&lt;/code&gt; privilege for the &lt;code&gt;public&lt;/code&gt; schema is no longer set by default. This is a recommendation from &lt;a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1058"&gt;CVE-2018-1058&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;What does that mean for the average (non-superuser) user?&lt;/p&gt;</description></item><item><title>ctid and other PostgreSQL table internals</title><link>https://andreas.scherbaum.la/post/2022-06-28_ctid-and-other-postgresql-table-internals/</link><pubDate>Tue, 28 Jun 2022 16:36:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2022-06-28_ctid-and-other-postgresql-table-internals/</guid><description>&lt;p&gt;While attending a conference (yay) the discussion turned to system columns, and especially &lt;code&gt;ctid&lt;/code&gt;. This was in context of backups, and the physical position of data on disk. The question was if that can be used to determine if an incremental backup is required, and if it is enough to just copy that field where the &lt;code&gt;ctid&lt;/code&gt; points to. Not quite, but I’d like to use this question to describe the &lt;a href="https://www.postgresql.org/docs/current/ddl-system-columns.html"&gt;system columns&lt;/a&gt; more in detail.&lt;/p&gt;</description></item><item><title>PostgreSQL Upgrades are hard</title><link>https://andreas.scherbaum.la/post/2022-06-22_postgresql-upgrades-are-hard/</link><pubDate>Wed, 22 Jun 2022 14:38:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2022-06-22_postgresql-upgrades-are-hard/</guid><description>&lt;p&gt;Together with &lt;a href="https://postgresql.life/post/laetitia_avrot/"&gt;Lætitia Avrot&lt;/a&gt; and &lt;a href="https://postgresql.life/post/nikolay_samokhvalov/"&gt;Nikolay Samokhvalov&lt;/a&gt; I was invited to participate in a &lt;a href="https://app.hopin.com/events/postgres-vision/expo/773371"&gt;Community Panel&lt;/a&gt; (&lt;a href="https://www.youtube.com/watch?v=kgO_ms0o22E"&gt;YouTube video&lt;/a&gt;) about &lt;em&gt;PostgreSQL Upgradability&lt;/em&gt; at &lt;a href="https://www.postgresvision.com/"&gt;Postgres Vision 2022&lt;/a&gt;. The panel was moderated by &lt;a href="https://postgresql.life/post/bruce_momjian/"&gt;Bruce Momjian&lt;/a&gt; and initiated and organized by &lt;a href="https://postgresql.life/post/jimmy_angelakos/"&gt;Jimmy Angelakos&lt;/a&gt;. Bruce did talk with each of us before, which helped a lot to guide the discussion in the right direction. The recording of the &lt;a href="https://vyruss.org/blog/postgresql-community-panel-upgradability-postgres-vision-2022.html"&gt;panel discussion&lt;/a&gt; is available on the Postgres Vision website.&lt;/p&gt;&#10;&lt;p&gt;During this panel each of us provided examples for how easy or complicated &lt;em&gt;PostgreSQL&lt;/em&gt; upgrades still are.&lt;/p&gt;</description></item><item><title>GSoC 2021 completed</title><link>https://andreas.scherbaum.la/post/2021-09-02_gsoc-2021-completed/</link><pubDate>Thu, 02 Sep 2021 00:06:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2021-09-02_gsoc-2021-completed/</guid><description>&lt;p&gt;The &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code 2021&lt;/a&gt; (&lt;em&gt;GSoC&lt;/em&gt;) for the &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL Project&lt;/a&gt; is wrapped up. The timeline this year was shortened to half, compared to previous years. That’s good, because smaller projects can be worked on, and students have a chance to cope with a changing environment at home and university. On the other hand, the shorter time doesn’t allow diving into more complex projects. Nevertheless, with the help of all mentors, six students successfully concluded their projects.&lt;/p&gt;</description></item><item><title>Delete directories recursive on Hetzner Storage Box</title><link>https://andreas.scherbaum.la/post/2021-07-09_delete-directories-recursive-on-hetzner-storage-box/</link><pubDate>Fri, 09 Jul 2021 20:25:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2021-07-09_delete-directories-recursive-on-hetzner-storage-box/</guid><description>&lt;p&gt;Among other external solutions, I store some data on &lt;a href="https://www.hetzner.com/storage/storage-box"&gt;Storage Boxes&lt;/a&gt; from &lt;em&gt;Hetzner&lt;/em&gt;. The Storage Box allows you to have sub-accounts, so for every server and system storing data there, I use a separate account. For each sub-account, one can select a subdirectory where the data is stored, and the sub-account then can only see this data. The Admin account can see all data, and see all directories.&lt;/p&gt;</description></item><item><title>PostgreSQL Project @ GSoC 2021</title><link>https://andreas.scherbaum.la/post/2021-05-20_postgresql-project-gsoc-2021/</link><pubDate>Thu, 20 May 2021 15:25:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2021-05-20_postgresql-project-gsoc-2021/</guid><description>&lt;p&gt;Wow! The &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL Project&lt;/a&gt; got all 7 proposals accepted into &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code 2021&lt;/a&gt; (&lt;em&gt;GSoC&lt;/em&gt;)!&lt;/p&gt;&#10;&lt;p&gt;This year &lt;em&gt;Google&lt;/em&gt; changed the &lt;a href="https://summerofcode.withgoogle.com/how-it-works/"&gt;participation terms&lt;/a&gt; a bit, and cut the time for the students in half. This is supposed to help students who can’t work full-time from home, especially in light of the global pandemic situation. It also means smaller projects, which are easier to handle even for students new to the project.&lt;/p&gt;</description></item><item><title>Restic backup</title><link>https://andreas.scherbaum.la/post/2020-12-27_restic-backup/</link><pubDate>Sun, 27 Dec 2020 23:47:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-12-27_restic-backup/</guid><description>&lt;p&gt;Was asked quite a few times how I do my backups with &lt;em&gt;Restic&lt;/em&gt;.&lt;/p&gt;&#10;&lt;p&gt;For more than 10 years I was using &amp;ldquo;&lt;a href="https://github.com/andreasscherbaum/duplicity-backup"&gt;Duplicity&lt;/a&gt;&amp;rdquo; for backups, but in 2019 I changed to &lt;a href="https://restic.net/"&gt;Restic&lt;/a&gt;. The main reason for the change was that &lt;em&gt;Duplicity&lt;/em&gt; still can&amp;rsquo;t handle &amp;ldquo;Big Data&amp;rdquo;, as in: larger directories. In 2009 someone opened an &lt;a href="https://bugs.launchpad.net/duplicity/+bug/385495"&gt;issue&lt;/a&gt; on the &lt;em&gt;Duplicity&lt;/em&gt; bugtracker, and this problem still exists as of today. For about two years I was shifting around the problem, excluding files, trying to make the sigfile smaller. But at some point I decided that it is enough and I need to change the tool.&lt;/p&gt;</description></item><item><title>Google Summer of Code 2020 - Intermediate status update</title><link>https://andreas.scherbaum.la/post/2020-08-21_google-summer-of-code-2020-intermediate-status-update/</link><pubDate>Fri, 21 Aug 2020 22:43:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-08-21_google-summer-of-code-2020-intermediate-status-update/</guid><description>&lt;p&gt;The three &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL&lt;/a&gt; projects for this year’s &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code&lt;/a&gt; are on track, and &lt;a href="https://andreas.scherbaum.la/post/2020-06-18_google-summer-of-code-2020-started/"&gt;making good progress&lt;/a&gt;. All projects expect to finish on time.&lt;/p&gt;&#10;&lt;h2 id="performance-farm"&gt;Performance Farm&lt;/h2&gt;&#10;&lt;p&gt;The data gathering for performance farm members is completed, as well as the new implementation for the &lt;em&gt;JSON&lt;/em&gt; data transfer. The project iteratively updated it’s goals, and adjusted for newly identified UI issues.&lt;/p&gt;&#10;&lt;p&gt;Current work centers around making the website more pretty and useful, as well as reducing the number of used &lt;em&gt;JavaScript&lt;/em&gt; libraries. The next step is presenting the work to the &lt;em&gt;PostgreSQL&lt;/em&gt; Community for broader feedback.&lt;/p&gt;</description></item><item><title>Monitor additional details in Telegraf with the "Exec" input filter</title><link>https://andreas.scherbaum.la/post/2020-06-25_monitor-additional-details-in-telegraf-with-the-exec-input-filter/</link><pubDate>Thu, 25 Jun 2020 01:14:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2020-06-25_monitor-additional-details-in-telegraf-with-the-exec-input-filter/</guid><description>&lt;p&gt;After &lt;a href="https://andreas.scherbaum.la/post/2020-06-24_install-telegraf-using-ansible/"&gt;installing Telegraf&lt;/a&gt; and hooking up everything into &lt;a href="https://www.influxdata.com/products/influxdb-overview/"&gt;InfluxDB&lt;/a&gt;, I was missing the status of my backups. Every system here creates encrypted backups every night, and stores them on a central NAS, and off-site. But I want to know statistics about the backups, and see if something is not working.&lt;/p&gt;&#10;&lt;p&gt;I&amp;rsquo;m using &lt;a href="https://restic.net/"&gt;Restic&lt;/a&gt; for the backups (will blog about this another time). However &lt;em&gt;Telegraf&lt;/em&gt; does not support &lt;em&gt;Restic&lt;/em&gt; directly, I need a few workarounds. This blog post however is not directly about monitoring the backups, but about how to write your own plugin for &lt;em&gt;Telegraf&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Restic upgrade on Debian Buster</title><link>https://andreas.scherbaum.la/post/2020-03-27_restic-upgrade-on-debian-buster/</link><pubDate>Fri, 27 Mar 2020 21:29:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-03-27_restic-upgrade-on-debian-buster/</guid><description>&lt;p&gt;A while ago I switched backups from &lt;a href="https://duplicity.gitlab.io//"&gt;Duplicity&lt;/a&gt; to &lt;a href="https://restic.net/"&gt;Restic&lt;/a&gt;. About time: I was using &lt;em&gt;Duplicity&lt;/em&gt; for many years (I think I started using it around 2010, long before &lt;em&gt;Restic&lt;/em&gt; became available) and it served me well. But recently I ran into more and more issues, especially with archives getting larger and larger. There is an 11 years old open bug in the Duplicity bugtracker, which describes a &lt;a href="https://bugs.launchpad.net/duplicity/+bug/385495"&gt;showstopper for backing up larger archives&lt;/a&gt;. And it doesn&amp;rsquo;t look like this will be solved anytime soon. Therefore it was time for something new.&lt;/p&gt;&#10;&lt;p&gt;Since I&amp;rsquo;m rolling out my backups with &lt;a href="https://andreas.scherbaum.la/categories/ansible"&gt;Ansible&lt;/a&gt;, it was relatively easy to create a set of scripts for &lt;em&gt;Restic&lt;/em&gt; which use almost the same infrastructure as the old Duplicity backups. That works as expected on all our laptops. But the &lt;a href="https://andreas.scherbaum.la/categories/raspberry-pi"&gt;Raspberry Pi&lt;/a&gt;, which does the fileserver backups, seem to had a problem. Backups took way longer than before, jumped from 30-60 minutes (depending on the amount of changes) to constantly around 10 hours.&lt;/p&gt;</description></item><item><title>Ansible: Just mount an existing filesystem</title><link>https://andreas.scherbaum.la/post/2019-12-09_ansible-just-mount-an-existing-filesystem/</link><pubDate>Mon, 09 Dec 2019 01:04:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2019-12-09_ansible-just-mount-an-existing-filesystem/</guid><description>&lt;p&gt;There is no easy way to &amp;ldquo;just mount&amp;rdquo; an existing filesystem in &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt;, using the &lt;a href="https://docs.ansible.com/ansible/latest/modules/mount_module.html"&gt;mount&lt;/a&gt; module. I just want to mount an already defined mount point, and don&amp;rsquo;t really care about all the configuration here.&lt;/p&gt;</description></item><item><title>How to reset your KDE (without deleting everything else)</title><link>https://andreas.scherbaum.la/post/2016-09-29_how-to-reset-your-kde-without-deleting-everything-else/</link><pubDate>Thu, 29 Sep 2016 01:44:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2016-09-29_how-to-reset-your-kde-without-deleting-everything-else/</guid><description>&lt;p&gt;I&amp;rsquo;m a (more or less) happy &lt;a href="https://www.kde.org/"&gt;KDE&lt;/a&gt; user, ever since the &lt;em&gt;KDE&lt;/em&gt; 3 days. Before that, I used &lt;a href="https://www.fvwm.org/"&gt;fvwm2&lt;/a&gt; for a long time, but that is a different story. It also happens that I never really reinstalled my home directory - the oldest files I can find are from 1997, and that is pretty much when I switched from an old &lt;a href="https://www.slackware.com/"&gt;Slackware&lt;/a&gt; system with self-compiled updates, to something with a more &lt;a href="https://www.debian.org/"&gt;modern distribution&lt;/a&gt;. That means, that all the time from 1997 to today, I carry the same &lt;code&gt;/home/ads&lt;/code&gt; across my computers. The home directory grew from a few MB to 133 GB today (maybe I should clean it up, but then again it&amp;rsquo;s cheaper to buy a bigger harddisk).&lt;/p&gt;&#10;&lt;p&gt;It also means, that I never deleted my &lt;em&gt;KDE&lt;/em&gt; config, even when upgrading to &lt;em&gt;KDE&lt;/em&gt; 4 or &lt;em&gt;Plasma&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>How I do backup of my mobile devices</title><link>https://andreas.scherbaum.la/post/2013-09-14_how-i-do-backup-of-my-mobile-devices/</link><pubDate>Sat, 14 Sep 2013 21:44:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2013-09-14_how-i-do-backup-of-my-mobile-devices/</guid><description>&lt;p&gt;Recently I was asked how I do backups of my mobile devices. The discussion started when I told that I &amp;ldquo;survived&amp;rdquo; a bricked device without data loss.&lt;/p&gt;&#10;&lt;p&gt;Disclaimer: I work (well, was working, before we got spinned of into a &lt;a href="https://en.wikipedia.org/w/index.php?title=GoPivotal&amp;amp;redirect=no"&gt;subsidiary&lt;/a&gt;) for &lt;a href="https://en.wikipedia.org/wiki/EMC_Corporation"&gt;EMC&lt;/a&gt;. Part of &lt;em&gt;EMCs&lt;/em&gt; portfolio is &amp;ldquo;backup&amp;rdquo; and for sure I learned a lot from my employer. All my own devices and servers are backed up, some of them multiple times. Backups, devices and communication is encrypted. I&amp;rsquo;m not using public services (&lt;em&gt;Dropbox&lt;/em&gt;, &lt;em&gt;Google Drive&lt;/em&gt;, &amp;hellip;) for the backups.&lt;/p&gt;</description></item><item><title>Die Wolke hat es schon wieder getan</title><link>https://andreas.scherbaum.la/post/2009-12-22_die-wolke-hat-es-schon-wieder-getan/</link><pubDate>Tue, 22 Dec 2009 22:51:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2009-12-22_die-wolke-hat-es-schon-wieder-getan/</guid><description>&lt;p&gt;Einen Anbieter zentralisierter Dienste habe ich in meinem letzten &lt;a href="https://andreas.scherbaum.la/post/2009-11-25_probleme-in-der-wolke-aka-backup-in-the-cloud/"&gt;Posting über Probleme&lt;/a&gt; mit genau diesen Diensten übersehen: &lt;a href="https://de.wikipedia.org/wiki/Research_In_Motion"&gt;RIM&lt;/a&gt; - &lt;em&gt;Research in Motion&lt;/em&gt;. Die Firma, die den &lt;a href="https://de.wikipedia.org/wiki/BlackBerry"&gt;BlackBerry&lt;/a&gt; herstellt, jenes Gerät, dass &lt;a href="https://www.welt.de/politik/article3075971/Barack-Obama-darf-seinen-Blackberry-behalten.html"&gt;Zugang zu den eigenen E-Mails von überallher&lt;/a&gt; verspricht.&lt;/p&gt;&#10;&lt;p&gt;Um dies zu gewährleisten, hat sich &lt;em&gt;RIM&lt;/em&gt; quasi unentbehrlich gemacht: die Kommunikation des &lt;em&gt;BlackBerry&lt;/em&gt; läuft über Server von &lt;em&gt;RIM&lt;/em&gt;, die Nachrichten werden dort passend aufbereitet und auf das Gerät geschoben (Push, statt dem sonst üblichen Abrufen/Pollen der Nachrichten).&lt;/p&gt;</description></item><item><title>Probleme in der Wolke (aka: Backup in the Cloud)</title><link>https://andreas.scherbaum.la/post/2009-11-25_probleme-in-der-wolke-aka-backup-in-the-cloud/</link><pubDate>Wed, 25 Nov 2009 20:16:18 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2009-11-25_probleme-in-der-wolke-aka-backup-in-the-cloud/</guid><description>&lt;p&gt;Als langjähriger Palm-Anwender hat es mich sehr gefreut, vor einiger Zeit die Ankündigungen zum &lt;em&gt;Palm Pre&lt;/em&gt; zu lesen. Ein neues Gerät, die Optik sah gut aus und außerdem sollte ein &lt;em&gt;Linux&lt;/em&gt; drunter laufen. Was will man mehr?&lt;/p&gt;</description></item><item><title>sudo: sorry, you must have a tty to run sudo</title><link>https://andreas.scherbaum.la/post/2009-10-19_sudo-sorry-you-must-have-a-tty-to-run-sudo/</link><pubDate>Mon, 19 Oct 2009 13:16:12 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2009-10-19_sudo-sorry-you-must-have-a-tty-to-run-sudo/</guid><description>&lt;p&gt;It took me a while to find out, why this backup script would not start. Finally, I found this error message: &lt;code&gt;sudo: sorry, you must have a tty to run sudo&lt;/code&gt;. The sudo call is required to execute &lt;code&gt;clustat&lt;/code&gt; and find out, which machine is the current master.&lt;/p&gt;&#10;&lt;p&gt;&lt;code&gt;sudo&lt;/code&gt; is configured to execute &lt;code&gt;clustat&lt;/code&gt; without password and works fine on the command line - so what&amp;rsquo;s wrong here?&lt;/p&gt;</description></item><item><title>PostgreSQL Schulung</title><link>https://andreas.scherbaum.la/post/2008-05-06_postgresql-schulung/</link><pubDate>Tue, 06 May 2008 10:12:41 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2008-05-06_postgresql-schulung/</guid><description>&lt;p&gt;Die &lt;a href="https://web.archive.org/web/20090130004136/https://www.opensourceschool.de/"&gt;Open Source School&lt;/a&gt; hat neben einigen anderen Lehrgängen auch eine &lt;a href="https://web.archive.org/web/20080503182603/https://www.opensourceschool.de/index.php?id=15&amp;amp;tx_ttproducts_pi1%5BbackPID%5D=13&amp;amp;tx_ttproducts_pi1%5Bproduct%5D=13&amp;amp;cHash=32e23a3a3c"&gt;Schulung für PostgreSQL&lt;/a&gt; im Programm. Dieses Posting hier nicht nicht ganz uneigennützig, wenn man sich anschaut, wer diese Schulung halten wird ;-)&lt;/p&gt;</description></item><item><title>f* MySQL</title><link>https://andreas.scherbaum.la/post/2007-02-03_f-mysql/</link><pubDate>Sat, 03 Feb 2007 11:06:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2007-02-03_f-mysql/</guid><description>&lt;p&gt;Today I woke up because the Nagios used by our ISP sent me a SMS: something does not work well on one of the association servers. According to the SMS, the webserver was not responding. Ok, the webserver is &lt;a href="https://andreas.scherbaum.la/post/2006-12-05_there-is-no-spoonmmmmmauto_increment/"&gt;never&lt;/a&gt; the cause of the problem, something else is going wrong.&lt;/p&gt;</description></item><item><title>Linux Installation kopieren</title><link>https://andreas.scherbaum.la/post/2006-12-01_linux-installation-kopieren/</link><pubDate>Fri, 01 Dec 2006 14:05:07 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2006-12-01_linux-installation-kopieren/</guid><description>&lt;p&gt;Wenn man eine &lt;em&gt;Linux&lt;/em&gt; Installation von einer Platte auf eine andere kopieren möchte, kann dies mit einigen einfachen Schritten erfolgen. Die SuSE &lt;a href="https://de.opensuse.org/"&gt;Supportdatenbank&lt;/a&gt; hat dafür einen netten &lt;a href="https://de.opensuse.org/SDB:SuSE_Linux_umkopieren"&gt;Eintrag&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Backups ... properly</title><link>https://andreas.scherbaum.la/post/2006-08-09_backups-...-properly/</link><pubDate>Wed, 09 Aug 2006 15:29:52 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2006-08-09_backups-...-properly/</guid><description>&lt;p&gt;Today I found this little script which does backups on a server:&lt;/p&gt;</description></item></channel></rss>