I’m impressed with what restic offers out of the box: encryption,
compression (as pointed out below, no compression yet), support for popular cloud providers – god bless you, the developers (I mean it).
I’m evaluating restic to use for backing up a folder with files that are being rotated – the logs. In this folder I’d have up to 10 files, 1Gb each.
Right now this is solved using a the following script (wrapped in a
watch -n 3 ./backup_logs.sh line):
gcloud auth activate-service-account \ my-service-account@my-project-id..iam.gserviceaccount.com \ --key-file=/path/to/key.json gsutil -m rsync -r -J \ /path/to/logs \ gs://my-bucket
The script is simple enough as is, but that’s the reason I’d like to try and migrate it to restic: I’d like to start small in my endeavour of adopting restic.
Upon initial evaluation, as far as I understand, restic is based on snapshots. Hence, at any particular point in time a snapshot will contain “current situation” in a given folder, e.g. in my case only ten 1Gb files. I’d like to, however, have a continuous (well, maybe once in 30 seconds using
watch -n 30) stream of files to a remote storage.
Am I right that for a particular task at hand restic is not suitable?