Back In Time

From the documentation:

Back In Time is a simple backup solution for Linux desktops. It is based on rsync and uses hard-links to reduce space used for unchanged files. It comes with a Qt5 GUI which will run on both Gnome and KDE based Desktops. Back In Time is written in Python3 and is licensed under GPL2.

Installation

Install backintimeAUR, backintime-cliAUR for a CLI-only version, or backintime-gitAUR for the development version.

Back In Time will automatically install a startup entry in /etc/xdg/autostart. If you want to launch the GUI, then run backintime-qt. If you want to backup files other than your home user files, then consider starting Back In Time with pkexec backintime-qt instead.

Configuration

The configuration can be done entirely via the GUI. It is necessary to modify the following settings:

  • Where to save the snapshot
  • What directories to backup
  • When a backup should be started (manual, every hour, every day, every week, every month)

Troubleshooting

Cannot find snapshots folder

If you see the error message in the status bar that BIT cannot find the snapshots folder although the snapshots are visible in the sidebar and the backup process is working correctly, then you are likely to have leftovers from a previous failed backup cron job. The status bar displays the content of the file ~/.local/share/backintime/worker.message. Thus deleting or renaming this file will remove the error message.

Icons not appearing

The QT5 GUI is mainly aimed at KDE, so it can happen that tray icon is blank and icons on the ui are also missing. An easy fix for this is to install oxygen-icons.

gollark: I don't think it would technically need to do a *full* reverse proxy job, since all it needs to do is look at the Host header (or SNI on HTTPS requests, although that might go away at some point?) and route accordingly, but still.
gollark: I suppose you could install caddy instead of nginx too, but I don't like it.
gollark: ```apache<VirtualHost *:80> ServerName thing1.com ProxyPass "/" "http://192.xxx.xxx.25"</VirtualHost>```seems like something which should work.
gollark: That would probably make your "edge" thing quite busy, since it would effectively be working as... half a reverse proxy.
gollark: So just stick different reverse proxy configurations in each "virtual host", I'm sure apache can do that much.

See also
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.