Best way to maintain backups? - Newbie

[GMahal]

So, I ran a check. Output is below.

[/share/Download/rclone-v1.65.2-linux-amd64] # ./rclone check /share/Multimedia/Music/ backup/backup: -P -L --log-file / share/Users/xxx/rclonelog.txt
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Errors: 90092 (retrying may help)
Checks: 116386 / 116386, 100%
Elapsed time: 4h1m16.5s

I uploaded the log to Mega as it was too big to post.

15.13 MB file on MEGA

Can anyone help me out?

[kapitainsky]

What is the output of

rclone config redacted

Your log file indicates that you do not use any remote as you do not have any config.

NOTICE: Config file "/root/.config/rclone/rclone.conf" not found - using defaults

In addition

@GMahal

./rclone check /share/Multimedia/Music/ backup/backup:

It looks like you are are comparing two local folders and not any mega remote.

What was your original command to copy things to mega?

[GMahal]

Thanks, I'm back on track! User error.

I guess my config file was not persistent after rebooting the NAS?

Maybe something with my installation/how I was running the program?? Maybe the command I was using as well?

Since there isn't QNAP specific installation instructions, I did my best by following the basic Linux installation instructions.

Anyway, hopefully I have picked up enough troubleshooting tips here to get by for now.

Thanks again for the help.

[karlh (Karl)]

You can also manually specifiy your config file within the command using:

--config=/location/to/rclone.conf

source

This will fix any loss of configures after restarts.

Also, you are using rclone in a way I have not seen What is this about

backup/backup:

I would setup remote named, say, mega and use:

rclone copy /local/dir/ mega:dirname/

Also, if thumbs are causing problem try excluding

--exclude "@*"

source

When playing around with new commands, please do a dry-run

--dry-run

Bw,

[jwink3101 (Justin Winokur)]

@kapitainsky

For proper solution use something designed for the job. There are many free and paid options available. For open source I would recommend to look at restic /rustic or kopia .

If you really like the full-file nature of rclone (and the pros/cons that go with it) and you're willing to test something in beta, I wrote a tool called dfb. From the readme:

The dfb backup tool utilizes rclone to create full-file, append-only backups that allow easy restoration to any point in time. Files are uploaded with dates appended to their names and deletes are noted with a delete marker. The design focuses on simplicity, easy understanding, and restoration without special tools. It prioritizes full-file backups stored natively on the remote, continuous rollback capability, straightforward backups and restores, and support for append-only storage. To accomplish this, it sacrifices some efficiency and advanced features. It may not be the the most efficient, advanced, fast, featurefull, sexy, or sophisticated backup tool these are great tradeoffs for peace-of-mind with backups!

On the storage backend, you see all files, natively*, in their respective folders. Except every file has a tag with the date on it. ^{*Unless a reference or a delete}

[GMahal]

Thanks for the suggestions, I may check those out as time permits. I am actually still in the process of the initial copy up to Mega.

Btw, I think I figured out what was going on over here. I use a QNAP NAS and since I didn't see any QNAP specific installation instructions, I experimented with the generic Linux installation instructions. After Fetching and Unpacking, is the Copy Binary section

sudo cp rclone /usr/bin/
sudo chown root:root /usr/bin/rclone
sudo chmod 755 /usr/bin/rclone

It appears that this copy to /usr/bin is not persistent after the NAS is rebooted.

I have to re-copy rclone to /usr/bin after a reboot as well as re-create the remote.