terracotta VS BorgBackup

One can also do raster calculus between two or more COGs with Terracotta: https://github.com/DHI-GRAS/terracotta/issues/221

I am currently working on setting up a web app using leaflet that can display .tif images along with some polygons and add some filters in the web app to better interact with the data. In the process of implementing this, I came to know that I need to use a tile server because I have large amounts of data and the tile server can help to serve the tiles on the web app. Based on my research, I guess these two are the main tools as of now: 1. Geoserver and 2. Terracotta. I am confused between the two. Can anyone suggest which one would be better for my use case and the pros and cons of both if possible? In case there's a different one that's better than the two mentioned above, it would be great if you can share the tool and your experience. Would be helpful.

Terracotta: Serverless GeoTiff Tile Server\ (12 comments)

I started using Nextcloud for file/contact/calendar syncing a few years, and have gradually moved most of my digital life into it. Documents and photos, but also scripts to automatically set some things up for me when I do a fresh install of Linux (I've been playing around with a few different distros lately). The only thing that doesn't live in Nextcloud are some old DVD rips, and that's mostly due to "haven't gotten around to it yet". Besides those, if it's not in Nextcloud, it's not something I care too much about losing if a disk were to fail.

My Nextcloud instance is then backed up to another drive on the same machine plus two off-site locations - an old server I still run at my parents' house, and and external HDD my friend let me plug in to his server. The on- and off-site backups are done using `borg` (https://www.borgbackup.org/), which does reduplication and encryption (with the keys backed up in 1Password).

I've been meaning to set up an automated restore on one of the offsite servers - a script to automatically unpack the latest backup, set up a fresh DB, and make things read-only - firstly to verify that the backups are functional and complete, but also as a backup in case my home server or home internet goes down. I know in _theory_ I've got everything I need in the backups to do a full restore, but I can't recall the last time I actually tried it out...

i use - and recommend - "borgbackup": for example with the "vorta" graphical frontend

* https://www.borgbackup.org/

* https://vorta.borgbase.com/install/windows/

just my 0.02€

I used this many, many years ago but switched to Borg[0] about five years ago. Duplicity required full backups with incremental deltas, which meant my backups ended up using too much disk space. Borg lets you prune older backups at will, because of chunk tracking and deduplication there is no such thing as an incremental backup.

[0] https://www.borgbackup.org/

Currently, I'm auto-backing it up with borg (push mode) through wireguard tunnel to NAS behind ISP's CGNAT. The borg takes care of deduplication in SQL file, so incremental update (even in append-only mode) is very small for PostgreSQL dump.

Borg 2 has been in development for nearly a year and a half [1] and may probably be released early next year, i.e., early 2024 (just a guess, seeing that even RC1 is not yet released and seems to have a lot of work to be done).

Does anyone know how Borg 1.x and 2 would compare to Kopia?

[1]: https://github.com/borgbackup/borg/issues/6602

You could use borgbackup.