stridemat

I still use it and like the added piece of mind with only a little inconvenience.

Thanks. I found it earlier and on a test all seems to be working.

Thanks. I am using usenet so will have to see if I can find this setting in SAB.

Hi, so I’m trying to get it so new media stays on the cache drive (media share) for a period of time, say 7 days in this example, but all other data in other shares moves from cache to array once a night - normal mover behaviour. I’m trying to avoid spinning up disks for recently added media that gets watched a few times. I have used the following settings. Will this work as desired?

That worked. Thank you.

Container is still working great (apart from the icon), but I was hoping it wasn’t the first sign of the container no longer being supported moving forward. Thanks for you work

Is this container still being supported?

Looks like the fix will be in the final build (it seems to be in rc7). Seems like a support headache though?

Looks like I'm waiting until a .1 or .2 release then

Im having the same. Any ideas?

Agreed. Much better than running in docker from a resilience point of view.

Is there likely to be a fix in the short term with this or is it a more fundamental change?

This fixed it for me!

Anyone know why when trying to use Borg installed via the plugin (along with other dependencies) I get the following error: root@Tower:~# borg Traceback (most recent call last): File "/usr/lib64/python3.9/site-packages/borg/archiver.py", line 41, in <module> from .archive import Archive, ArchiveChecker, ArchiveRecreater, Statistics, is_special File "/usr/lib64/python3.9/site-packages/borg/archive.py", line 20, in <module> from . import xattr File "/usr/lib64/python3.9/site-packages/borg/xattr.py", line 9, in <module> from ctypes import CDLL, create_string_buffer, c_ssize_t, c_size_t, c_char_p, c_int, c_uint32, get_errno File "/usr/lib64/python3.9/ctypes/__init__.py", line 8, in <module> from _ctypes import Union, Structure, Array ImportError: libffi.so.7: cannot open shared object file: No such file or directory

Is the above post from sdub the accepted way of making Unraid the target for backups without altering the base Unraid install?

So have resolved. Posting here for others in the future. Crontab text as follows to call specific config files. Obviously change the paths / file names as required: 0 2 * * 1 borgmatic -c /etc/borgmatic.d/UnraidBackup.yaml prune create -v 1 --stats 2>&1 0 4 * * * borgmatic -c /etc/borgmatic.d/DocsBackup.yaml prune create -v 1 --stats 2>&1 0 6 15 * * borgmatic check -v 1 2>&1

Hi all, So I have managed to get a two config set up going how I want manually (yay) but cannot work out how to auto start each one on a different schedule using cron. Ideally they would run on different schedules due to the nature of what each one is backing up and how often it changes. Pease can someone point me in the right direction?

With the recent demise of Nerdpack I am looking to use this container for my Borg usage. Though I am having trouble trying to configure. A few questions which I hope someone could answer: It is possible to 'reuse' existing repositories from Borg installed via Nerdpack? Or am I better just starting again? My existing repo is located /mnt/disks/WD_Elements_2620/UnraidBackup (I also have another repo at the following location /mnt/disks/WD_Elements_2620/DocsBackup. I have read this thread and can see the links as to how to have multiple repo's etc.) Config page from the Docker tab below. The Borg Repo path takes you to the location of both repos, meaning that I need to specify the specific repo each time. Config .yaml file text. This looks ok to me, albeit appreciating that I am backing up my CA Back up folder. Once I get this working I plan to use Borg for all rather the CA Backup: location: - /mnt/user/backups repositories: - /mnt/borg-repository/UnraidBackup - ssh://[email protected]/mnt/mydisk/UnraidBackup one_file_system: true files_cache: mtime,size patterns: - '- [Tt]rash' - '- [Cc]ache' exclude_if_present: - .nobackup - .NOBACKUP storage: encryption_passphrase: "NOTMYPASSWORD" compression: lz4 ssh_command: ssh -i /root/.ssh/id_rsa archive_name_format: 'backup-{now}' retention: keep_weekly: 4 consistency: checks: - repository - archives prefix: 'backup-' hooks: before_backup: - echo "Starting Unraid backup." after_backup: - echo "Finished Unraid backup." on_error: - echo "Error during Unraid backup." Assuming I can use existing repo's, then how could I dryrun. This seems to kick out an error however I try it: borg create --list --dry-run /mnt/borg-repository/UnraidBackup ~/UnraidBackup Anything else that I could be doing?

Any guidance on how to install each of the below once I do eventually upgrade to 6.11.x? Noted that it looks like Perl won’t be required. Most concerned about Borg and maintaining settings etc.

Me too.

Yeah I’m having the same issues as set out above. Rolling back fixed the error and also the proxy connections started working again.

Yes it seems to be an issue arising in 6.10.0. Knew I should have held on. Updating permissions seemed to work.

Any more thoughts on what may have caused this? I’m having the same issue. What’s to stop it happening again? Looking at my system it chewed through 50GB of bandwidth over the last few hours trying to download and redownload files that were no longer importing.

Pastebin links if easier: - Libvert log: https://pastebin.com/q5brknKN - Syslog: https://pastebin.com/qCzZHEq6 - VM XML: https://pastebin.com/eHDK5Nd5

You could always try something like https://parsec.app. Have a gaming VM hosted on Unraid and then a light weight client elsewhere in the house on the network.