gamerayers

This looks awesome, and I'm looking forward to following it. Any chance you can make it easy to migrate from Borgmatic directly to this? I find Borgmatic works great, but the learning curve for starting it was extremely difficult. It also only has a log file for monitoring. This would be very nice to monitor. Keep up the good work!

I'm looking for some help. I would like to setup borgmatic to backup my immich stuff nightly. Data volume for immich is about 2tb. If I do a daily and keep 2 dailies, does that mean I need about 4tb or does it only include incremental information between the 2 version? Ideally, I would like to backup daily to my own moving drive backup from my SSD, and then would like to backup weekly to my sister's TrueNas. This is the information I have from Immich, but I don't know how to translate that to my server and borgmatic. Backup Script | ImmichBackup Script | ImmichBorg is a feature-rich deduplicating archiving software with built-in versioning. We provide a template bash script that can be run daily/weekly as a cron job to back up your files and database. We... The location I have mapped for /mnt/user is /mnt/user and the location of immich is /mnt/user/immich. Would this be correct for the config.yaml? location: source_directories: - /boot - /mnt/user/appdata - /mnt/user/immich repositories: - /mnt/borg-repository - truenas.tailscale.net/backup:/mnt/disks/borg_remote/repo one_file_system: true files_cache: mtime,size patterns: - '- [Tt]rash' - '- [Cc]ache' exclude_if_present: - .nobackup - .NOBACKUP storage: encryption_passphrase: "MYREPOPASSWORD" compression: none ssh_command: ssh -i /root/.ssh/id_rsa archive_name_format: 'backup-{now}' retention: keep_hourly: 0 keep_daily: 2 keep_weekly: 1 keep_monthly: 0 keep_yearly: 0 prefix: 'backup-' consistency: checks: - repository - archives prefix: 'backup-' hooks: before_backup: - echo "Starting a backup." after_backup: - echo "Finished a backup." on_error: - echo "Error during prune/create/check."Then I need to put this in the crontab? to have it created daily and checked on Wednesday? But not sure how to tell it to do weekly to my sisters? Or does this just always do the same to my sister as it does here? 0 1 * * * borgmatic prune create -v 1 --stats 2>&1 0 6 * * 3 borgmatic check -v 1 2>&1

Yep all fixed. Thanks for the help. And agreed, super weird.

OK, so that is super interesting. I was able to do all of that, and as soon as I erased the plugin configuration it was clear nothing was running on port 80 anymore. Time to try to reset the nginx to use port 80. Fingers crossed.

I did in a docker, trying to add a sidecar, but I removed that since it wasn't working. I think I attempted to do the cert early on, but then realized that I needed to change the name to be the name of my domain on tailscale and I wasn't ready to do that. Would it be advisable to delete the plugin and try again? or do you think that it would leave me in the same situation with port 80 taken?

SuperMicro-tailscale-diag-20240301-223355.zip

I installed the tailscale plugin and when I restart it appears that nginx won't start now due to something on port 80. If I turned off the tailscale plugin, it seems to work fine. I switched to port 81, but the redirect from port 80 to 443 then doesn't work correctly. I'm curious if there is a good way to fix this. Has anybody else run into this? It appears to be exclusive to the tailscale plugin causing the issues. FYI, the nginx won't start on port 80 for the management terminal. I already have it set to https, so it should be using 443, but the http port for redirect to https is port 80. When I do a: lsof -i :80 | grep LISTEN I get tailscale 1045 root 34u IPv6 481363296 0t0 TCP [x:x:x::x:x]:http (LISTEN) tailscale 1045 root 35u IPv4 481382452 0t0 TCP x.x.x.x:http (LISTEN) Basically showing that it is tailscale that has that port opened and why nginx can't open it for management-redirect.

I installed the tailscale plugin and when I restart it appears that nginx won't start now due to something on port 80. If I turned off the tailscale plugin, it seems to work fine. I switched to port 81, but the redirect from port 80 to 443 then doesn't work correctly. I'm curious if there is a good way to fix this. Has anybody else run into this? It appears to be exclusive to the tailscale plugin causing the issues.