<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Tharre/pkgbuilds/arch-system/borgbackup, branch master</title>
<subtitle>My personal AUR packages.</subtitle>
<id>https://git.th73.ovh/Tharre/pkgbuilds/atom?h=master</id>
<link rel='self' href='https://git.th73.ovh/Tharre/pkgbuilds/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/'/>
<updated>2023-04-25T03:33:37Z</updated>
<entry>
<title>arch-system: backup system updates</title>
<updated>2023-04-25T03:33:37Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2022-01-07T20:35:28Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=051d76ba0e5408cae656d30079816952536cee9b'/>
<id>urn:sha1:051d76ba0e5408cae656d30079816952536cee9b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arch-system: borgbackup: ignore archive already exists error</title>
<updated>2019-06-30T02:11:56Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2019-06-30T01:12:18Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=41750176fc06ba65ff009259e727e0eed0348c39'/>
<id>urn:sha1:41750176fc06ba65ff009259e727e0eed0348c39</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arch-system: borgbackup: use proper ssh timeout</title>
<updated>2019-04-21T17:44:51Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2019-04-21T17:38:23Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=3d3996edaf169424babc8b9da6bde6ea1051d3db'/>
<id>urn:sha1:3d3996edaf169424babc8b9da6bde6ea1051d3db</id>
<content type='text'>
ConnectTimeout merely specifies the TCP timeout, what we really want is
ServerAliceInterval, which makes the client send a null packet every X
seconds.
</content>
</entry>
<entry>
<title>arch-system: borgbackup: use snapshot timestamps</title>
<updated>2019-02-09T15:52:39Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2019-02-09T15:28:37Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=63b0cd2c634e5099e05a6d9843f2cc3c3b6513b7'/>
<id>urn:sha1:63b0cd2c634e5099e05a6d9843f2cc3c3b6513b7</id>
<content type='text'>
Previously, a archive would get the timestamp of the time it was
uploaded, instead of the time when the snapshot was created.

This is problematic, since archives are pruned by this timestamp,
meaning if multiple archives are uploaded together most of them would be
pruned immediately after.
</content>
</entry>
<entry>
<title>arch-system: borgbackup: change repo to rsync.net</title>
<updated>2018-08-07T02:31:22Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-08-07T02:31:22Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=e3b0c959c792f49dbd8b1aec470a27882d948705'/>
<id>urn:sha1:e3b0c959c792f49dbd8b1aec470a27882d948705</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arch-system: borgbackup: better connectivity check</title>
<updated>2018-08-07T02:31:00Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-08-07T01:01:38Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=f90a5be438306e5f92948199b2365c7d1f2f54f7'/>
<id>urn:sha1:f90a5be438306e5f92948199b2365c7d1f2f54f7</id>
<content type='text'>
Instead of trying to execute borg, which would give us a false positive
if borg itself isn't working on the remote, just connect to the server
without executing a command.

We check for 255 because `man 1 ssh` states the following:
    ssh exits with the exit status of the remote command or with 255 if
    an error occured.
</content>
</entry>
<entry>
<title>arch-system: borgbackup: treat rc 1 as a warning</title>
<updated>2018-07-31T19:48:10Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-07-31T19:46:28Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=43219efeeb0357e8c4a671f4784cacbf2decfd81'/>
<id>urn:sha1:43219efeeb0357e8c4a671f4784cacbf2decfd81</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arch-system: borgbackup: --keep-hourly 24 -&gt; 72</title>
<updated>2018-07-16T13:44:16Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-07-16T12:57:17Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=91fa8c46fb87503cc083f12fea1ed2792992ad64'/>
<id>urn:sha1:91fa8c46fb87503cc083f12fea1ed2792992ad64</id>
<content type='text'>
Since borg-prune only keeps the last snapshot of each day with
--keep-daily, it's possible that a file that was accidentally deleted is
only kept for 24h (if the machine is running) before it's purged from
backups. Increase to 72h to give the user a better chance of noticing
this in time.
</content>
</entry>
<entry>
<title>arch-system: borgbackup: notify about upload skip</title>
<updated>2018-07-16T13:43:56Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-07-16T12:56:07Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=2ef726102dbdeb0c5adbec8f3df981758e961314'/>
<id>urn:sha1:2ef726102dbdeb0c5adbec8f3df981758e961314</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arch-system: borgbackup: use correct key with ssh</title>
<updated>2018-06-15T16:12:31Z</updated>
<author>
<name>Tharre</name>
<email>tharre3@gmail.com</email>
</author>
<published>2018-06-15T16:11:40Z</published>
<link rel='alternate' type='text/html' href='https://git.th73.ovh/Tharre/pkgbuilds/commit/?id=82bfa9338a6f3062c88aa5d5fabf488d0e06bab6'/>
<id>urn:sha1:82bfa9338a6f3062c88aa5d5fabf488d0e06bab6</id>
<content type='text'>
</content>
</entry>
</feed>
