However, when you then run this bash script as a cron task, for some reason it is looking for the config file at "/.config/rclone/nf" a quick fix was to copy the "nf" file to this folder. When you create the "nf" file from a shell prompt (or SSH connection) with the command "rclone config" it is stored at "/root/.config/rclone/nf" (you can check this by running the command "rclone config file"). (see my github site for examples)Ģ9-02-2020: I've noticed that since upgrading to FreeNAS v11.3 that this script was no longer working. This shows the stats, and for "sync" a list of files Copied (new), Copied (replaced existing), and Deleted - as well as any errors/notices for "cryptcheck" it only lists errors or notices. Update(1): The log file rclone produces is not user friendly, therefore this script will also create a more user friendly log (to use as the email body). Note: The rclone config file saved via the CLI is different to the one used in the FreeNAS GUI, so its safe to update this configuration file via rclone config without affecting anything you have configured in the FreeNAS GUI. Why? Freenas (v11.1 onwards) now supports rclone nativetly and also has GUI entries for Cloudsync, however there is no option to use additional parameters within the GUI, thus I have adapted a script to be run instead via a cron job. Script was adapted from the one posted in the FreeNAS community forums by Martin Aspeli: The script is available from my GitHub site. Can easily be adapted for other cloud providers. A script to run rclone on the FreeNAS server to backup NAS data to Backblaze B2 cloud storage.
0 kommentar(er)
