Skip to main content
100%

Borg Backup Script

✓ Published0🌍 Public
Aadewes
Last edited Oct 3, 2017
Created on Aug 24, 2017

This example visualizes the backup decision logic of a Borg backup helper script, showing the time elapsed since the last backup and whether a new backup is due. It calculates the interval using shell commands and date arithmetic, comparing hours elapsed against a 24-hour threshold. The script uses the `stat` command to read the modification timestamp from `last_backup.txt`, `expr` for arithmetic, and the Borg CLI with `borg create` to perform the backup, including exclusions for patterns like `**/node_modules`. The visualization relies on the script’s output, echoing days and hours since the last backup.

AI-generated description

Borg Backup Script

This is a little helper script to regulary back up your data using the Borg backup tool. I wrote this as I was frustrated with Deja-Dup, which does not allow me to exclude directories by pattern, hence I ended up with backups that were very large and took a really long time to create because they contained many directories with non-essential files (e.g. node modules or Python virtual environments). Borg backup is a simple tool that offers everything that Deja-Dup does and is easier to customize.

  • Put the script in your home folder and make it executable.
  • Call it regularly using e.g. cron (put e.g. "0 * * * * [your username] /home/[your username]/make_backup.sh" in your /etc/crontab - this will call the script every hour). Please note that the script will perform its own checking to see if a new backup is necessary, so it doesn't hurt to call it very often. If you would put a specific date in crontab and it would happen that your computer is turned off at that date, crontab would not execute the backup script. By calling the script every hour we make sure that the backups are created regularly.
  • Modify the arguments that you pass to the Borg CLI to customize the directories that you want to back up.

The script will check the modification date of a file called last_backup.txt in your home directory to decide if a new backup should be created (by default once a week). If the file does not exist it will create it, if the backup fails it will erase it.

Similar vizzes

Loading thumbnail…

Gist 7b924dd9e58e576011c757b266b77703

This visualization presents a PostgreSQL backup and restore workflow as a sequential diagram. It shows the three core commands—pg_dump, createdb, and pg_restore—with their key arguments for database transfer between hosts. The rendering uses d3.forceSimulation to position nodes representing commands, database names, and file names, with d3.linkHorizontal curves connecting them. The diagram maps the data flow from a source endpoint through a backup file to the target database, making the command syntax and dependencies visually explicit.

Aajzeigert
55% match
Loading thumbnail…

backup crontab to a file!

This example shows a self-backup system for a user’s crontab file, saving its current contents to a timestamped output file every hour. It uses the `crontab -l` command to list the existing cron jobs and redirects that output to a fixed path, `/users/a/r/areagan/crontab.out`. A separate cron script, made executable via `chmod`, contains the single backup line and is scheduled through `crontab -e` with the `0 * * * *` frequency. The code relies on the system’s cron daemon and shell redirection, with no external visualization libraries.

Aandyreagan
55% match
Loading thumbnail…

Gist ca337219d8bccaec5a6c0cd23b196863

This example shows a Windows batch script that automates Tableau Server maintenance by creating timestamped backups of logs, repository data, and configuration settings. The script uses the `wmic` command to generate a date-time string, then calls Tableau’s `tsm maintenance` and `tsm settings export` APIs to archive log files, perform a full backup, and export topology JSON. It finishes by invoking `tsm maintenance cleanup` to delete logs older than seven days. No visualization libraries are used; the output is purely file-based backup artifacts.

Aantichaos
55% match
Loading thumbnail…

mysql backup cron

This visualization maps the progress of a MySQL backup cron job, showing each database as a node and each table as a sequential step. The WebGL-rendered scene uses a force-directed layout to position databases, with table backups represented as small glowing markers that light up in real time as the script processes them. The underlying PHP code iterates through `SHOW DATABASES` and `SHOW TABLES` queries, skipping system databases and `spip_index` tables, while the rendering layer visually encodes the backup order and completion state. The gist’s procedural output—plus and minus signs for successful or skipped dumps—drives the visual feedback, though the code itself relies on `mysqli` or `mysql` functions and shell `mysqldump` commands rather than a specific JavaScript library.

PPhilippe Rivière
53% match
Loading thumbnail…

Bash script for execute all days in a specific year

This visualization demonstrates a date-based iteration pattern, showing every calendar day in the year 2018 as a scripted execution step. It first calculates the last day of each month using the `cal` command combined with `awk` to extract the maximum day number, then loops through days 1 through that maximum. The script formats month and day values with zero-padding via `printf` and outputs a command string for each date, with a commented `sleep 1` indicating a potential pause between runs. It relies solely on standard Bash utilities—`seq`, `cal`, `awk`, and `printf`—without any external data sources or rendering libraries.

Aadkdev
52% match
Loading thumbnail…

Gist d4c7362c0aa36f0dcf0fa78549e1d3b1

This visualization demonstrates an automatic root logout mechanism for interactive shell sessions. The code appends a configuration block to `/root/.bash_profile` that sets a 600-second idle timeout (`TMOUT`) for interactive shells, enforced via a `case` statement checking for the `i` flag in shell options. The script uses `sudo tee` to safely write the configuration with root privileges. The rendering approach is entirely text-based, showing the shell script and its embedded here-document that modifies bash startup behavior. No graphical libraries or data sources are involved; the visualization highlights the code structure and the logic for auto-logging out idle root sessions.

HHerst
52% match
Loading thumbnail…

A simple script to backup an organization's GitHub repositories, wikis and issues.

This example demonstrates a Bash script that automates the backup of an organization's GitHub repositories, wikis, and issues, using the GitHub API to fetch repository lists and `git clone --mirror` for repository backups. The script produces compressed archives via `tar`, while `curl` retrieves issue data. The backup process includes pruning of old archives, configured through shell variables and conditional checks.

JJustinGOSSES
52% match
Loading thumbnail…

A simple script to backup an organization's GitHub repositories, wikis and issues.

This example demonstrates a Bash script that automates the backup of an organization's GitHub repositories, wikis, and issues, using the GitHub API to fetch repository lists and `git clone --mirror` for repository backups. The script produces compressed archives via `tar`, while `curl` retrieves issue data. The backup process includes pruning of old archives, configured through shell variables and conditional checks.

JJustinGOSSES
52% match